On Monday, 03/15/2004 at 01:44 EST, "Davis, Larry"
<[EMAIL PROTECTED]> wrote:

> VSWITCH CONTROLLER ON 0C5C 0C5E

Unless you intend to add a VSWITCH CONTROLLER statement for each VSWITCH,
or have to change it when the real address changes, I suggest using the
generic "VSWITCH CONTROLLER" specification (without ON xxxx).

> In the SYSTEM CONFIG file (MAINT CF1 disk) I defined the Virtual Switch
>
> Define VSWITCH SWITCH01 Controller * CONNECT
>
> The real trick was to add some entries to the PROFILE EXEC of AUTOLOG1
or
> OPERATOR to define what real  address CP used to connect to the real
> NETWORK, and who is authorized to connect to the switch. I added these
> entries to the PROFILE EXEC in AUTOLOG1
>
> ADDRESS COMMAND CP 'AUTOLOG TCPIP    IAMANSVM '

Make that "XAUTOLOG TCPIP".    WDNNS passwords.....

> After looking through the documentation, and everyone's help on this
list I
> have established a basic switched network. The DEFINE LAN command in the
> SYSTEM CONFIG file may be a better route. I could define the Real Device
and
> GRANT authorization to the users and eliminate the entries in AUTOLOG1's
> PROFILE EXEC.

That would be my recommendation.  Oh, and be sure to provide a backup
controller virtual machine and a backup OSA.

Alan Altmark
Sr. Software Engineer
IBM z/VM Development

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to