I just noticed that in my AUTOLOG1 PROFILE EXEC, TCPIP is XAUTOLOGed just before the GRANTS.
Could it be that VSWITCH is not ready until TCPIP is fully logged on, the TCPIP stack built? Do I need a delay in my AUTLOG1 PROFILE EXEC after the XAUTOLOG of TCPIP to make this happen? 'CP XAUTOLOG TCPIP' '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' 'CP XAUTOLOG VLINUX1' 'CP XAUTOLOG VLINUX2' 'CP XAUTOLOG VLINUX3' Mark Pace <[email protected]> Sent by: The IBM z/VM Operating System <[email protected]> 11/01/2010 03:13 PM Please respond to The IBM z/VM Operating System <[email protected]> To [email protected] cc Subject Re: No IPL VSWITCH Connectivity The 2 entries I have in my system config. 1 for layer 2 and 1 for layer 3. Both work at IPL. DEFINE VSWITCH VSWTCH1 RDEV 0600 CONTR * ETH Define VSWITCH VSWTCH3 RDEV 0604 CONTR * IP On Mon, Nov 1, 2010 at 3:07 PM, 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 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' 'CP XAUTOLOG VLINUX1' 'CP XAUTOLOG VLINUX2' 'CP XAUTOLOG VLINUX3' -- Mark D Pace Senior Systems Engineer Mainline Information Systems
