I have no problem do all of my VSWITCH definitions and GRANTs prior to
TCP/IP being initialized:
Define VSwitch VSW1 RDev 0F96 0F99
Define VSwitch VSWAILT RDev 181D 1200
Define VSwitch VSWTMK00 RDev None,
IP Nonrouter,
VLAN Unaware
Modify VSwitch VSW1 GRAnt LINUX000
Modify VSwitch VSWTMK00 GRAnt AILPROD
Modify VSwitch VSWTMK00 GRAnt AILTEST
Modify VSwitch VSWTMK00 GRAnt GLOBE
Modify VSwitch VSWTMK00 GRAnt TCPIP
Modify VSwitch VSWTMK00 GRAnt TMKA
Modify VSwitch VSWTMK00 GRAnt TMKB
Modify VSwitch VSWTMK00 GRAnt TMKC
Modify VSwitch VSWTMK00 GRAnt TMKD
Modify VSwitch VSWTMK00 GRAnt TECH
Modify VSwitch VSWTMK00 GRAnt UA
Modify VSwitch VSWAILT GRAnt AILTEST
Frank M. Ramaekers Jr.
________________________________
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of George Henke/NYLIC
Sent: Monday, November 01, 2010 2:43 PM
To: [email protected]
Subject: Re: No IPL VSWITCH Connectivity
My controllers. DTCVSW1,2 are AUTOLOGed before the GRANTS, but there is
only a 10 sec sleep.
'CP XAUTOLOG GCS'
'CP XAUTOLOG DTCVSW1'
'CP XAUTOLOG DTCVSW2'
'CP SLEEP 10 SEC'
'CP XAUTOLOG NETVIEW'
'CP XAUTOLOG NETSPY'
'CP XAUTOLOG OPERSYMP'
'CP XAUTOLOG RSCSSERV'
'CP XAUTOLOG VTAM'
Also TCPIP IUCVs to VSWITCH.
Does that mean TCPIP is acting as the CONTROLLER and must be up before
the GRANTS?
USER TCPIP TCPIP 128M 256M ABG
INCLUDE TCPCMSU
OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 APPLMON
SHARE RELATIVE 3000
IUCV ALLOW
IUCV ANY PRIORITY
IUCV *CCS PRIORITY MSGLIMIT 255
IUCV *VSWITCH MSGLIMIT 65535
* CHANGE SPECIAL FROM 9104 TO 9108 PER SAM 9/30/09
SPECIAL 9108 QDIO 3 SYSTEM OSALAN
LINK 5VMTCP40 491 491 RR
LINK 5VMTCP40 492 492 RR
LINK TCPMAINT 591 591 RR
LINK TCPMAINT 592 592 RR
LINK TCPMAINT 198 198 RR
MDISK 191 3390 2258 005 540W02 MR RTCPIP WTCPIP MTCPIP
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
_____________________________________________________
This message contains information which is privileged and confidential and is
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any
review, disclosure,
copying, distribution, or use of the contents of this message is strictly
prohibited. If you have
received this in error, please destroy it immediately and notify us at
[email protected].
