Just a coda on this problem and a special thank you to both Alan and Sue Farrell who hit the "bull's eye".
Portname in the define VSWITCH was indeed the problem as Sue explains: >If you have defined your VSWITCH exactly like you first mentioned: >define vswitch lnxvsw1 portname lnxvsw1 rdev 9004 >then your problem is the PORTNAME. "rdef 9004" is being treated as >additional portnames. Like Alan said, leave it off. >See the syntax note for DEFINE VSWITCH: >Notes: >(1) You can specify the operands in any order, as long as switchname is >the first operand specified, and portname is the last operand specified, >if applicable. Once the portname was eliminated,, the VSWITCH defniition in SYSTEM CONFIG was honored and VSWITCH came up connected after the IPL without any further action required. Also, since it is in season to express thanks, a special thanks to all the listers for help not only on this problem, but all the problems I encountered upgrading z/VM 5.4. We are now z196 compliant at RSU 1002 Level 1 with a Level 2 maintenance environment that did not exist before. None of which would have been possible without the help of you all. So thank you very much one and all. Alan Altmark <[email protected]> Sent by: The IBM z/VM Operating System <[email protected]> 11/01/2010 03:34 PM Please respond to The IBM z/VM Operating System <[email protected]> To [email protected] cc Subject Re: No IPL VSWITCH Connectivity On Monday, 11/01/2010 at 03:10 EDT, George Henke/NYLIC <[email protected]> wrote: > After IPL we can destroy the VSWITCH: > > det vswitch lnxvsw1 > > Then issue the same commands as in the IPL below and everything connects. > > Why? > > Are there some restrictions, considerations, for defining the VSWITCH at IPL > time? > > SYSTEM CONFIG: > > define vswitch lnxvsw1 portname lnxvsw1 rdev 9004 I suggest that you remove the PORTNAME LNXVSW1. It isn't needed and it can create unnecessary confusion. > AUTOLOG1: PROFILE EXEC: > > 'CP SET VSWITCH LNXVSW1 GRANT VLINUX1' > 'CP SET VSWITCH LNXVSW1 GRANT VLINUX2' > 'CP SET VSWITCH LNXVSW1 GRANT VLINUX3' > 'CP SET VSWITCH LNXVSW1 GRANT VLINUX4' > 'CP SET VSWITCH LNXVSW1 GRANT VLINUX5' > 'CP SLEEP 10 SEC' Why sleep 10 sec? The SET VSWITCH commands take effect immediately. > 'CP XAUTOLOG VLINUX1' > 'CP XAUTOLOG VLINUX2' > 'CP XAUTOLOG VLINUX3' A VSWITCH establishes connectivity to the outside world once the controllers (DTCVSW1/2) are up. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 [email protected] IBM Endicott
