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:[email protected]] On Behalf Of Berthold
Gunreben
Sent: Tuesday, January 20, 2015 3:24 AM
To: [email protected]
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 <[email protected]<mailto:[email protected]>> wrote:
> ok--here goes...this is what I have so far...tell me where I am all
> wet..
>
> logged on to tcpmaint
> in system dtcparms
> >>
> .**************************************************************
> .* SYSTEM DTCPARMS created by DTCIPWIZ EXEC on 19 Jan 2009
> .* Configuration program run by MAINT at 15:43:10
> .**************************************************************
> :nick.TCPIP :type.server
> :class.stack
> :attach.F800-F803,F900-F903,FC00-FC03,FD00-FD03 >>>
> added this <<<<<<<<<<<<<<<<<<<<<<<
> * * * End of File * * *
> >>
> logged on to maint
> in user direct
> I did /identity tcpip
> >>
> IDENTITY TCPIP WD5JU8QP 128M 256M ABG
> INCLUDE TCPCMSU
> BUILD ON * USING SUBCONFIG TCPIP-1
> * BUILD ON @@member2name USING SUBCONFIG TCPIP-2
> * BUILD ON @@member3name USING SUBCONFIG TCPIP-3
> * BUILD ON @@member4name USING SUBCONFIG TCPIP-4 OPTION QUICKDSP
> SVMSTAT MAXCONN 1024 DIAG98 APPLMON SHARE RELATIVE 3000 IUCV ALLOW
> IUCV ANY PRIORITY IUCV *CCS PRIORITY MSGLIMIT 255 IUCV *VSWITCH
> MSGLIMIT 65535
> NICDEF F800 TYPE QDIO LAN SYSTEM VSW1 >>>> added these
> <<<<<<<<<<<<<<<<<<
> NICDEF F900 TYPE QDIO LAN SYSTEM VSW1 NICDEF FC00 TYPE QDIO LAN
> SYSTEM VSW1 NICDEF FD00 TYPE QDIO LAN SYSTEM VSW1
>
> SUBCONFIG TCPIP-1
> LINK TCPMAINT 491 491 RR
> LINK TCPMAINT 492 492 RR
> LINK TCPMAINT 591 591 RR
> >>>>>
>
>
>
>
>
> From: Michael MacIsaac <[email protected]<mailto:[email protected]>>
> To: [email protected]<mailto:[email protected]>
> Date: 01/19/2015 12:15 PM
> Subject: Re: VSWITCH for z/vm tcpip
> Sent by: Linux on 390 Port
> <[email protected]<mailto:[email protected]>>
>
>
>
> Ron,
>
> You wrote:
> > Found the following that was incorrect...or modified from original
> > 5.4 setup..person that set this up no longer here.
> > :nick.TCPIP :type.server
> > :class.stack
> > :ATTACH.F800-F80F,F900-F90F
>
> Yeah, that last line looks like a mistake - you don't want 32 OSA
> devices attached to the TCP/IP stack. But you've probably already
> fixed that.
>
> The reason to attach the z/VM TCP/IP stack to the VSWITCH is to
> leverage the HA qualities of the VSWITCH with its ability to fail over
> to a second OSA card. Alan is right - if you're going to do this, the
> better model is to put the three COMMAND statements into TCPIP's user
> directory entry. Then you don't need the :attach. tag.
>
> The reason to put COMMAND statements into directory entries is so you
> won't have to worry about maintaining a set of SET VSWITCH GRANT
> statements.
> When
> each virtual machine logs on, it is able to effectively grant access
> to itself.
>
> See section 25.1 of "The Virtualization Cookbook for IBM z/VM 6.3,
> RHEL 6.4, and SLES 11 SP3" on the Web at
> http://www.redbooks.ibm.com/abstracts/sg248147.html
>
> Hope this helps.
>
> -Mike MacIsaac
>
> On Mon, Jan 19, 2015 at 12:47 PM, Alan Altmark
> <[email protected]<mailto:[email protected]>> wrote:
>
> > On Monday, 01/19/2015 at 11:19 EST, Ron Wells
> > <[email protected]<mailto:[email protected]>> wrote:
> > > ok---it is working after I added the ATTACH but I gather this is
> > > F800(example) is running through OSA only not the VSWITCH..
> > > I did find where the old 5.4 had the NICDEF in the USER DIRECT
> > > file The Cook book I am looking at has the steps to set the OSA
> > > addr to the VSWITCH >> BUT questions it shows setting up for
> > > one(1) OSA port using addr of 2100 and
> changing
> > to
> > > virt addr of 600 ?? is that necessary ? Reason I ask it looks
> > > like
> old
> > > setup it was not done that way. the F800 was used on the define.
> > > Next is it says to do a COMMAND SET VSWITCH VSW1 GRANT &USERID
> > > COMMAND DEFINE NIC 600 TYPE QDIO COMMAND COUPLE 600 to SYSTEM
> > > VSW1
> > >
> > > Gather the above are VM commands and have to be performed for each
> > > OSA
> > set
> > > of addresses ??
> > > F800 = 600 F900=601 FC00=602 FD=603
> > >
> > > Am I getting it or way off??
> >
> > I think you're getting way off, and I am having trouble
> > understanding
> your
> > posts and figuring out what you want to do. (The odd formatting
> > doesn't help.) Don't worry about what it was before; what do you
> > want NOW?
> >
> > Start with PROFILE TCPIP. If you need two interfaces, then the
> > profile has them. If it references F800, then you need virtual
> > F800, F801, and F802. It doesn't matter whether it is physical
> > (e.g. A803-A805 attached as F800-F802) or a virtual NIC (DEFINE NIC
> > F800). If there's a second interface defined as 600, then it
> > wants 600-602, again not caring about virtual or real.
> >
> > If you have the COMMAND SET VSWITCH GRANTs in the directory, then
> > you
> have
> > to use the COMMAND DEFINE NIC and COMMAND COUPLE statements instead
> > of NICDEF because NICDEFs are processed before any COMMAND
> > statements, creating an authorization problem.
> >
> > Alan Altmark
> >
> > Senior Managing z/VM and Linux Consultant Lab Services System z
> > Delivery Practice IBM Systems & Technology Group
> > ibm.com/systems/services/labservices
> > office: 607.429.3323
> > mobile; 607.321.7556
> > [email protected]<mailto:[email protected]>
> > IBM Endicott
> >
> > --------------------------------------------------------------------
> > -- For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to [email protected]<mailto:[email protected]> with
> > the message: INFO
> > LINUX-390 or visit
> > http://www.marist.edu/htbin/wlvindex?LINUX-390
> > --------------------------------------------------------------------
> > -- For more information on Linux on System z, visit
> > http://wiki.linuxvm.org/
> >
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [email protected]<mailto:[email protected]> with the
> message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
> ----------------------------------------------------------------------
> Email Disclaimer
> This E-mail contains confidential information belonging to the
> sender, which may be legally privileged information. This
> information is intended only for the use of the individual or entity
> addressed above. If you are not the intended recipient, or an
> employee or agent responsible for delivering it to the intended
> recipient, you are hereby notified that any disclosure, copying,
> distribution, or the taking of any action in reliance on the contents
> of the E-mail or attached files is strictly prohibited.
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [email protected]<mailto:[email protected]> with the
> message: INFO LINUX-390 or
> visit http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
--
----------------------------------------------------------------------
Berthold Gunreben Build Service Team
http://www.suse.de/ Maxfeldstr. 5
SUSE LINUX GmbH D-90409 Nuernberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham
Norton HRB 21284 (AG Nürnberg)
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to
[email protected]<mailto:[email protected]> with the message: INFO
LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit http://wiki.linuxvm.org/
