My configuration is a bit different and I have a second VSWITCH specifying
OSA address "0A0" but is not defined in
my TCPIP configuration. Or TCPIP's directory statement. It is defined in
SYSTEM CONFIG and in Autolog1 profile exec.
"0A0 is not the Primary OSA so maybe that's the reason. Perhaps you could
shed some light on this, how its tied together?
SYSTEM CONFIG:
Rdevice 0A00-0A02 EQID VMTNET Type OSA /* VMT1
VSWITCH2*/
Rdevice 0A10-0A12 EQID VMTNET Type OSA /* Primary VMT1 VSWITCH1*/
USER DIRECT
IDENTITY TCPIPTCPIP
SUBCONFIG TCPIP-1
NICDEF 0A10 TYPE QDIO DEV 3 LAN SYSTEM VSWITCH1
SUBCONFIG TCPIP-2
NICDEF 0A50 TYPE QDIO DEV 3 LAN SYSTEM VSWITCH1
TCPMAINT 198 disk
PROFILE TCPIP
DEVICE DEV@0A10 OSD 0A10 PORTNUMBER 1 NONROUTER
LINK OSAA10 QDIOETHERNET DEV@0A10 PATHMTU MTU 1500 IP VLAN 2422
; (End DEVICE and LINK statements)
HOME
10.59.68.8 255.255.255.0 OSAA10
; (End HOME Address information)
; Network Subnet First Link MTU
; Address MaskHop Name Size
; - --- ---
DEFAULTNET 10.59.68.3 OSAA10 1500
; (End GATEWAY Static Routing information)
START DEV@0A10
; (End START statements)
SYSTEM DTCPARMS Only names primary OSA A10
:nick.TCPIP:type.server
:class.stack
.* :attach.0A10-0A12
AUTOLOG1 PROFILE EXEC:
"PIPE CP XAUTOLOG DTCVSW1"
"PIPE CP XAUTOLOG DTCVSW2"
'CP DEFINE VSWITCH VSWITCH1 CONTR * RDEV 0A10.P1 0A30.P1'
'CP SET VSWITCH VSWITCH1 GRANT TCPIP'
'CP DEFINE VSWITCH VSWITCH2 CONTR * RDEV 0A00 0A20 VLAN AWARE'
'CP SET VSWITCH VSWITCH2 GRANT LXWASMQ1 VLAN 2419'
'CP SET VSWITCH VSWITCH2 GRANT LINUXTST VLAN 2419'
Thanks
Joe
Joseph Vitale
Technology Services Group
Mainframe Operating Systems
Pershing Plaza
95 Christopher Columbus Drive
Floor 14
Jersey City, N.J. 07302
Work 201-395-1509
Cell917-903-0102
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Davis,
Larry (National VM Capability)
Sent: Tuesday, January 20, 2015 10:38 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VSWITCH for z/vm tcpip
You can't have NICDEF's using a VSWITCH with TCPIP and ATTACH: statements in
the DTCPARMS file
NICDEFS are used to connect a virtual device to the user and couple it to the
VSWITCH. The VSWITCH is the only one that touches the Real devices not TCPIP in
this case.
ATTACH: is used when you want TCPIP to own the OSA ports and based on you using
4 OSA triplets I am assuming you want to use a VSWITCH
TCPIP does not change very often so sometimes you have to go with Simple and
understandable from your perspective the Following works for me
SYSTEM CONFIG file (MAINT's CF1 MDISK):
Add the VSWITCH Definition for VSWITCH VSWMZVM This can be whatever makes sense
to you. 0B80 Port 00 and 0E80 Port 00 are the real OSA devices for the VSWITCH
and are owned by the defined controllers on the system.
DEFINE VSWITCH VSWMZVM TYPE QDIO UPLINK RDEV 0B80.P00 0E80.P00 CONNECT,
CONTROLLER * IP VLAN 968 PORTTYPE ACCESS USERBASED NATIVE 1
PROFILE EXEC file (AUTOLOG1's 191 MDISK):
Startup the TCPIP controllers which should already be done in the
default IBM setup
Add Grants for all the users that need access to the VSWITCH in this
case TCPIP
'CP SET VSWITCH VSWMZVM GRANT TCPIP'
Directory of TCPIP:
NICDEF 0800 TYPE QDIO LAN SYSTEM VSWMZVM
System-name TCPIP (TCPMAINT 198 MDISK):
DEVICE and LINK statements in the local system TCPIP file 0800 is the
Virtual device as defined in the TCPIP Directory NICDEF statement
DEVICE OSAD0800 OSD 0800
LINK OSAL0800 QDIOETHERNET OSAD0800
I hope some of this helps
Larry Davis,
VM Capability
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Berthold
Gunreben
Sent: Tuesday, January 20, 2015 3:24 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VSWITCH for z/vm tcpip
Ron,
I would try to check all the parts.
- for me, the user definition looks ok.
- logon as tcpmaint and have a look at system dtcparms. This should
look similar to this:
:nick.TCPIP:type.server
:class.stack
i.e. no dedicated network device.
- make sure that you did grant tcpip access to the vswitch
set vswitch vsw1 grant tcpip
- also add that to system profile to make it persistent
- if you use RACF/VM, you will have to set permissions there
- after logging on tcpip, you can have a look at the vswitch to see if
the connection is ok:
CP Q VSWITCH VSW1 DETAILS
in there, you should have an Adapter Owner: TCPIP
The rest of the configuration is from tcpmaint the files TCPIP DATA and PROFILE
TCPIP
Berthold
On Mon, 19 Jan 2015 14:14:45 -0600
Ron Wells mailto:ron.we...@springleaf.com>>