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
