Re: VSWITCH defined VSE TCP/IP fails
On Tuesday, 08/31/2010 at 10:58 EDT, Mark Pace pacemainl...@gmail.com wrote: When did VSE pick up layer 2 support? (d'oh!) You're right, VSE does not yet support layer 2. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH defined VSE TCP/IP fails
It's a limit in the IBM OCO driver. BSI has asked that the driver be updated, but I don't think IBM has committed to it yet. Tony Thigpen -Original Message - From: Alan Altmark Sent: 09/01/2010 10:44 AM On Tuesday, 08/31/2010 at 10:58 EDT, Mark Pace pacemainl...@gmail.com wrote: When did VSE pick up layer 2 support? (d'oh!) You're right, VSE does not yet support layer 2. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH defined VSE TCP/IP fails
Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development 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 privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4) 1) Define the VSWITCH a. define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 b. -and- add the same statement to 'SYSTEM CONFIG' file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2) Granting access to the VSWITCH a. set vswitch vswitchname grant userid b. -and- add Modify VSwitch vswitchname GRAnt userid to 'SYSTEM CONFIG' c. - or - add the set vswitch command in the AUTOLOG1 startup 3) Defining the simulated NICs a. for userid cmd define nic ccuu4 qdio b. -and- add to the directory for userid: NICDEF ccuu4 TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4) Attaching the simulated NIC with couple ccuu4 to system vswitchname (This will need to be performed each time the virtual machine is logged on.) (Don't think I missed anything) Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 7:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development 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 privacy...@ailife.com. _ 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 privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
A couple of things On the DEFINE VSWITCH you only need to specify the 1st address of the triplet. On the NICDEF add LAN SYSTEM switchNameand it will be coupled automatically when you logon. example NICDEF 061C TYPE QDIO DEVICES 3 LAN SYSTEM VSWTCH3 OR SPECIAL 061C QDIO 3 SYSTEM VSWTCH3 On Tue, Aug 31, 2010 at 10:04 AM, Frank M. Ramaekers framaek...@ailife.comwrote: No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook “Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4”) 1) Define the VSWITCH *a. **define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3* b. –and- add the same statement to ‘SYSTEM CONFIG’ file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2) Granting access to the VSWITCH *a. **set vswitch vswitchname grant userid* b. –and- add *Modify VSwitch vswitchname GRAnt userid* to ‘SYSTEM CONFIG’ c. – or – add the *set vswitch* command in the AUTOLOG1 startup 3) Defining the simulated NICs a. *for userid cmd define nic ccuu4 qdio* b. –and- add to the directory for *userid*: NICDEF *ccuu4* TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4) Attaching the simulated NIC with *couple ccuu4 to system vswitchname *(This will need to be performed each time the virtual machine is logged on.) (Don’t think I missed anything) Frank M. Ramaekers Jr. -- *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On Behalf Of *Billy Bingham *Sent:* Tuesday, August 31, 2010 7:51 AM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development 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 privacy...@ailife.com. _ 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
Re: VSWITCH defined VSE TCP/IP fails
1) Yes, but you can have up to 3 triplets (9 address total) 2) Didn't know about the LAN SYSTEM switchname Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Tuesday, August 31, 2010 9:11 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails A couple of things On the DEFINE VSWITCH you only need to specify the 1st address of the triplet. On the NICDEF add LAN SYSTEM switchNameand it will be coupled automatically when you logon. example NICDEF 061C TYPE QDIO DEVICES 3 LAN SYSTEM VSWTCH3 OR SPECIAL 061C QDIO 3 SYSTEM VSWTCH3 On Tue, Aug 31, 2010 at 10:04 AM, Frank M. Ramaekers framaek...@ailife.com wrote: No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4) 1) Define the VSWITCH a. define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 b. -and- add the same statement to 'SYSTEM CONFIG' file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2) Granting access to the VSWITCH a. set vswitch vswitchname grant userid b. -and- add Modify VSwitch vswitchname GRAnt userid to 'SYSTEM CONFIG' c. - or - add the set vswitch command in the AUTOLOG1 startup 3) Defining the simulated NICs a. for userid cmd define nic ccuu4 qdio b. -and- add to the directory for userid: NICDEF ccuu4 TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4) Attaching the simulated NIC with couple ccuu4 to system vswitchname (This will need to be performed each time the virtual machine is logged on.) (Don't think I missed anything) Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 7:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development 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 privacy...@ailife.com
Re: VSWITCH defined VSE TCP/IP fails
What makes this a Layer-3 VSWITCH vs a Layer-2? Thanks, Billy On 31 Aug 2010 at 9:04, Frank M. Ramaekers wrote: No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4) 1)Define the VSWITCH a.define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 b.-and- add the same statement to `SYSTEM CONFIG´file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2)Granting access to the VSWITCH a.set vswitch vswitchname grant userid b.-and- add Modify VSwitch vswitchnameGRAnt userid to `SYSTEM CONFIG´ c.- or - add the set vswitch command in the AUTOLOG1 startup 3)Defining the simulated NICs a.for userid cmd define nic ccuu4 qdio b.-and- add to the directory for userid: NICDEF ccuu4 TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4)Attaching the simulated NIC with couple ccuu4 to system vswitchname (This will need to be performed each time the virtual machine is logged on.) (Don´t think I missed anything) Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 7:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development 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 privacy...@ailife.com. _ 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 privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
The stack has to have this capability. AFAIK, only Linux can do this. Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 9:32 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails What makes this a Layer-3 VSWITCH vs a Layer-2? Thanks, Billy On 31 Aug 2010 at 9:04, Frank M. Ramaekers wrote: No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4) 1)Define the VSWITCH a.define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 b.-and- add the same statement to 'SYSTEM CONFIG'file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2)Granting access to the VSWITCH a.set vswitch vswitchname grant userid b.-and- add Modify VSwitch vswitchnameGRAnt userid to 'SYSTEM CONFIG' c.- or - add the set vswitch command in the AUTOLOG1 startup 3)Defining the simulated NICs a.for userid cmd define nic ccuu4 qdio b.-and- add to the directory for userid: NICDEF ccuu4 TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4)Attaching the simulated NIC with couple ccuu4 to system vswitchname (This will need to be performed each time the virtual machine is logged on.) (Don't think I missed anything) Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 7:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development 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 privacy...@ailife.com. _ 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
Re: VSWITCH defined VSE TCP/IP fails
Learned something today - I didn't realize there could be 2 backup triplets. Sorry for raising the SNR! ;-) On Tue, Aug 31, 2010 at 10:22 AM, Alan Altmark alan_altm...@us.ibm.comwrote: On Tuesday, 08/31/2010 at 10:11 EDT, Mark Pace pacemainl...@gmail.com wrote: A couple of things On the DEFINE VSWITCH you only need to specify the 1st address of the triplet. That's not a triplet. It's a specification of a primary and two backup OSA triplets. E.g. RDEV 1E00 1F00 2000. On the NICDEF add LAN SYSTEM switchNameand it will be coupled automatically when you logon. example NICDEF 061C TYPE QDIO DEVICES 3 LAN SYSTEM VSWTCH3 OR SPECIAL 061C QDIO 3 SYSTEM VSWTCH3 Please use NICDEF instead of SPECIAL. Alan Altmark z/VM Development IBM Endicott -- Mark D Pace Senior Systems Engineer Mainline Information Systems
Re: VSWITCH defined VSE TCP/IP fails
On Tuesday, 08/31/2010 at 10:32 EDT, Billy Bingham billy.bingham...@suddenlink.net wrote: What makes this a Layer-3 VSWITCH vs a Layer-2? If the VSWITCH is defined with the ETHERNET option, it is layer 2. If you let it default to (or specify) the IP option, it is layer 3. Only z/OS is limited to layer 3. Everyone else (with current software) can use layer 2. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH defined VSE TCP/IP fails
When did VSE pick up layer 2 support? On Tue, Aug 31, 2010 at 10:52 AM, Alan Altmark alan_altm...@us.ibm.comwrote: On Tuesday, 08/31/2010 at 10:32 EDT, Billy Bingham billy.bingham...@suddenlink.net wrote: What makes this a Layer-3 VSWITCH vs a Layer-2? If the VSWITCH is defined with the ETHERNET option, it is layer 2. If you let it default to (or specify) the IP option, it is layer 3. Only z/OS is limited to layer 3. Everyone else (with current software) can use layer 2. Alan Altmark z/VM Development IBM Endicott -- Mark D Pace Senior Systems Engineer Mainline Information Systems
Re: VSWITCH defined VSE TCP/IP fails
DEFINE VSWITCH VSWTCH1 RDEV 0600 CONTR * *ETH*-* Layer 2 * Define VSWITCH VSWTCH3 RDEV 0604 CONTR ** IP* -*Layer 3* On Tue, Aug 31, 2010 at 10:31 AM, Billy Bingham billy.bingham...@suddenlink.net wrote: What makes this a Layer-3 VSWITCH vs a Layer-2? Thanks, Billy On 31 Aug 2010 at 9:04, Frank M. Ramaekers wrote: No problem. Originally, I had on z/VSE machine with 3 addresses used for TCP/IP. I wished to move this to a layer-3 VSWITCH for redundancy purposes. (Much of the following was derived from the IBM Redbook “Linux on IBM eserver zSeries and S/390: VSWITCH and VLAN Features of z/VM 4.4”) 1)Define the VSWITCH a.define vswitch vswitchname rdev ccuu1 ccuu2 ccuu3 b.–and- add the same statement to ‘SYSTEM CONFIG’file (Remember ccuu1 ccuu2 ccuu3 represent a set of 3 address to be used) 2)Granting access to the VSWITCH a.set vswitch vswitchname grant userid b.–and- add Modify VSwitch vswitchnameGRAnt userid to ‘SYSTEM CONFIG’ c.– or – add the set vswitch command in the AUTOLOG1 startup 3)Defining the simulated NICs a.for userid cmd define nic ccuu4 qdio b.–and- add to the directory for userid: NICDEF ccuu4 TYPE QDIO DEVICES 3 (a above can be skipped, but the userid would have to be logged off then on) 4)Attaching the simulated NIC with couple ccuu4 to system vswitchname (This will need to be performed each time the virtual machine is logged on.) (Don’t think I missed anything) Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Billy Bingham Sent: Tuesday, August 31, 2010 7:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Frank, Would you be willing to share the steps you used to create the VSWITCH? Thanks, Billy On 30 Aug 2010 at 8:11, Frank M. Ramaekers wrote: Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * NoneMFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL- READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL- WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATAvPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00- 0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIOName: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0ELAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development 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 privacy...@ailife.com. _ 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 privacy...@ailife.com. -- Mark D Pace Senior
Re: VSWITCH defined VSE TCP/IP fails
Thanks, that helpsthe difference between an upCOUPLEd and a COUPLEd VSWITCH: UnCOUPLEd: AR 0015 MAC: 02-00-01-00-00-0E LAN: * None MFS: 8992 COUPLEd (and not yet initialized): AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT ...and initialized: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E VSWITCH: SYSTEM VSWAILT AR 0015 RX Packets: 49 Discarded: 0 Errors: 0 AR 0015 TX Packets: 42 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 2450 TX Bytes: 2884 AR 0015 Connection Name: Session Established AR 0015 Device: 0AA0 Unit: 000 Role: CTL-READ AR 0015 Device: 0AA1 Unit: 001 Role: CTL-WRITE AR 0015 Device: 0AA2 Unit: 002 Role: DATA vPort: 0065 Index: 0065 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 10.1.20.2MAC: 02-00-01-00-00-0E AR 0015 1I40I READY Thanks Alan! Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E LAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development 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 privacy...@ailife.com.
VSWITCH defined VSE TCP/IP fails
The VSWITCH seems to be defined just fine and the NICDEF added to the directory of the z/VSE. From z/VSE: * cp q v aa0-aa2 AR 0015 OSA 0AA0 ON NIC 0AA0 UNIT 000 SUBCHANNEL = 003A AR 0015 0AA0 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA0 MAC 02-00-01-00-00-0E CURRENT AR 0015 0AA0 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA1 ON NIC 0AA0 UNIT 001 SUBCHANNEL = 003B AR 0015 0AA1 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA1 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA2 ON NIC 0AA0 UNIT 002 SUBCHANNEL = 003C AR 0015 0AA2 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA2 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE But when the CSI TCP/IP stack tries to initialize, it receives: G1 0484 0S39I ERROR DURING OSA EXPRESS PROCESSING,REASON=0035 CUU=0AA0,RETCODE=E080 G1 0487 0003: IPL605E Unable to Initialize IJBOSA, return code: 122 G1 0487 0003: IPL609E Unable to initialize OSA Express, Link: AILLAN0 G1 0487 0004: IPL491I OSA-X link AILHIS0 started as 10.1.20.2 G1 0487 0005: IPL491I OSA-X link AILVSW0 started as 192.168.199.2 (The AILVSW0 is a previous defined VSWITCH that is internal only to communicate between VMs. And this has been working for quite some time now.) There is nothing notable on the DTCVSWn consoles. The error message description is less than hepful: REASON = X'0035' The Startlan function failed. This is most likely indicated by RETCODE=E080. Thoughts? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _ 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 privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
Is it a layer 2 or 3 vswitch? VSE and z/OS only support layer3. :( On Fri, Aug 27, 2010 at 3:18 PM, Frank M. Ramaekers framaek...@ailife.comwrote: The VSWITCH seems to be defined just fine and the NICDEF added to the directory of the z/VSE. From z/VSE: * cp q v aa0-aa2 AR 0015 OSA 0AA0 ON NIC 0AA0 UNIT 000 SUBCHANNEL = 003A AR 0015 0AA0 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA0 MAC 02-00-01-00-00-0E CURRENT AR 0015 0AA0 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA1 ON NIC 0AA0 UNIT 001 SUBCHANNEL = 003B AR 0015 0AA1 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA1 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA2 ON NIC 0AA0 UNIT 002 SUBCHANNEL = 003C AR 0015 0AA2 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA2 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE But when the CSI TCP/IP stack tries to initialize, it receives: G1 0484 0S39I ERROR DURING OSA EXPRESS PROCESSING,REASON=0035 CUU=0AA0,RETCODE=E080 G1 0487 0003: IPL605E Unable to Initialize IJBOSA, return code: 122 G1 0487 0003: IPL609E Unable to initialize OSA Express, Link: AILLAN0 G1 0487 0004: IPL491I OSA-X link AILHIS0 started as 10.1.20.2 G1 0487 0005: IPL491I OSA-X link AILVSW0 started as 192.168.199.2 (The AILVSW0 is a previous defined VSWITCH that is internal only to communicate between VMs. And this has been working for quite some time now.) There is nothing notable on the DTCVSWn consoles. The error message description is less than hepful: *REASON = X’0035’ *The Startlan function failed. This is most likely indicated by RETCODE=E080. Thoughts? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _ 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 privacy...@ailife.com. -- Mark D Pace Senior Systems Engineer Mainline Information Systems
Re: VSWITCH defined VSE TCP/IP fails
Layer 3. Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Friday, August 27, 2010 2:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Is it a layer 2 or 3 vswitch? VSE and z/OS only support layer3. :( On Fri, Aug 27, 2010 at 3:18 PM, Frank M. Ramaekers framaek...@ailife.com wrote: The VSWITCH seems to be defined just fine and the NICDEF added to the directory of the z/VSE. From z/VSE: * cp q v aa0-aa2 AR 0015 OSA 0AA0 ON NIC 0AA0 UNIT 000 SUBCHANNEL = 003A AR 0015 0AA0 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA0 MAC 02-00-01-00-00-0E CURRENT AR 0015 0AA0 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA1 ON NIC 0AA0 UNIT 001 SUBCHANNEL = 003B AR 0015 0AA1 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA1 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA2 ON NIC 0AA0 UNIT 002 SUBCHANNEL = 003C AR 0015 0AA2 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA2 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE But when the CSI TCP/IP stack tries to initialize, it receives: G1 0484 0S39I ERROR DURING OSA EXPRESS PROCESSING,REASON=0035 CUU=0AA0,RETCODE=E080 G1 0487 0003: IPL605E Unable to Initialize IJBOSA, return code: 122 G1 0487 0003: IPL609E Unable to initialize OSA Express, Link: AILLAN0 G1 0487 0004: IPL491I OSA-X link AILHIS0 started as 10.1.20.2 G1 0487 0005: IPL491I OSA-X link AILVSW0 started as 192.168.199.2 (The AILVSW0 is a previous defined VSWITCH that is internal only to communicate between VMs. And this has been working for quite some time now.) There is nothing notable on the DTCVSWn consoles. The error message description is less than hepful: REASON = X'0035' The Startlan function failed. This is most likely indicated by RETCODE=E080. Thoughts? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _ 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 privacy...@ailife.com. -- Mark D Pace Senior Systems Engineer Mainline Information Systems _ 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 privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
Did you Grant access to the vswitch? On Fri, Aug 27, 2010 at 3:37 PM, Frank M. Ramaekers framaek...@ailife.comwrote: Layer 3. Frank M. Ramaekers Jr. -- *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On Behalf Of *Mark Pace *Sent:* Friday, August 27, 2010 2:29 PM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: VSWITCH defined VSE TCP/IP fails Is it a layer 2 or 3 vswitch? VSE and z/OS only support layer3. :( On Fri, Aug 27, 2010 at 3:18 PM, Frank M. Ramaekers framaek...@ailife.com wrote: The VSWITCH seems to be defined just fine and the NICDEF added to the directory of the z/VSE. From z/VSE: * cp q v aa0-aa2 AR 0015 OSA 0AA0 ON NIC 0AA0 UNIT 000 SUBCHANNEL = 003A AR 0015 0AA0 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA0 MAC 02-00-01-00-00-0E CURRENT AR 0015 0AA0 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA1 ON NIC 0AA0 UNIT 001 SUBCHANNEL = 003B AR 0015 0AA1 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA1 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA2 ON NIC 0AA0 UNIT 002 SUBCHANNEL = 003C AR 0015 0AA2 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA2 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE But when the CSI TCP/IP stack tries to initialize, it receives: G1 0484 0S39I ERROR DURING OSA EXPRESS PROCESSING,REASON=0035 CUU=0AA0,RETCODE=E080 G1 0487 0003: IPL605E Unable to Initialize IJBOSA, return code: 122 G1 0487 0003: IPL609E Unable to initialize OSA Express, Link: AILLAN0 G1 0487 0004: IPL491I OSA-X link AILHIS0 started as 10.1.20.2 G1 0487 0005: IPL491I OSA-X link AILVSW0 started as 192.168.199.2 (The AILVSW0 is a previous defined VSWITCH that is internal only to communicate between VMs. And this has been working for quite some time now.) There is nothing notable on the DTCVSWn consoles. The error message description is less than hepful: *REASON = X’0035’ *The Startlan function failed. This is most likely indicated by RETCODE=E080. Thoughts? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _ 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 privacy...@ailife.com. -- Mark D Pace Senior Systems Engineer Mainline Information Systems _ 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 privacy...@ailife.com. -- Mark D Pace Senior Systems Engineer Mainline Information Systems
Re: VSWITCH defined VSE TCP/IP fails
Mark, Yep: set vswitch vswailt grant ailtest Command complete Ready; T=0.01/0.01 12:40:23 Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Friday, August 27, 2010 2:45 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Did you Grant access to the vswitch? On Fri, Aug 27, 2010 at 3:37 PM, Frank M. Ramaekers framaek...@ailife.com wrote: Layer 3. Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Friday, August 27, 2010 2:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Is it a layer 2 or 3 vswitch? VSE and z/OS only support layer3. :( On Fri, Aug 27, 2010 at 3:18 PM, Frank M. Ramaekers framaek...@ailife.com wrote: The VSWITCH seems to be defined just fine and the NICDEF added to the directory of the z/VSE. From z/VSE: * cp q v aa0-aa2 AR 0015 OSA 0AA0 ON NIC 0AA0 UNIT 000 SUBCHANNEL = 003A AR 0015 0AA0 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA0 MAC 02-00-01-00-00-0E CURRENT AR 0015 0AA0 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA1 ON NIC 0AA0 UNIT 001 SUBCHANNEL = 003B AR 0015 0AA1 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA1 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA2 ON NIC 0AA0 UNIT 002 SUBCHANNEL = 003C AR 0015 0AA2 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA2 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE But when the CSI TCP/IP stack tries to initialize, it receives: G1 0484 0S39I ERROR DURING OSA EXPRESS PROCESSING,REASON=0035 CUU=0AA0,RETCODE=E080 G1 0487 0003: IPL605E Unable to Initialize IJBOSA, return code: 122 G1 0487 0003: IPL609E Unable to initialize OSA Express, Link: AILLAN0 G1 0487 0004: IPL491I OSA-X link AILHIS0 started as 10.1.20.2 G1 0487 0005: IPL491I OSA-X link AILVSW0 started as 192.168.199.2 (The AILVSW0 is a previous defined VSWITCH that is internal only to communicate between VMs. And this has been working for quite some time now.) There is nothing notable on the DTCVSWn consoles. The error message description is less than hepful: REASON = X'0035' The Startlan function failed. This is most likely indicated by RETCODE=E080. Thoughts? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76701 _ 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 privacy...@ailife.com. -- Mark D Pace Senior Systems Engineer Mainline Information Systems _ 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 privacy...@ailife.com. -- Mark D Pace Senior Systems Engineer Mainline Information Systems _ 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 privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
In the TCPIP job on VSE, did you up the storage for VSWITCH? Tom Duerbusch THD Consulting Frank M. Ramaekers framaek...@ailife.com 8/27/2010 2:49 PM Mark, Yep: set vswitch vswailt grant ailtest Command complete Ready; T=0.01/0.01 12:40:23 Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Friday, August 27, 2010 2:45 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Did you Grant access to the vswitch? On Fri, Aug 27, 2010 at 3:37 PM, Frank M. Ramaekers framaek...@ailife.com wrote: Layer 3. Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Friday, August 27, 2010 2:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails Is it a layer 2 or 3 vswitch? VSE and z/OS only support layer3. :( On Fri, Aug 27, 2010 at 3:18 PM, Frank M. Ramaekers framaek...@ailife.com wrote: The VSWITCH seems to be defined just fine and the NICDEF added to the directory of the z/VSE. From z/VSE: * cp q v aa0-aa2 AR 0015 OSA 0AA0 ON NIC 0AA0 UNIT 000 SUBCHANNEL = 003A AR 0015 0AA0 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA0 MAC 02-00-01-00-00-0E CURRENT AR 0015 0AA0 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA1 ON NIC 0AA0 UNIT 001 SUBCHANNEL = 003B AR 0015 0AA1 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA1 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE AR 0015 OSA 0AA2 ON NIC 0AA0 UNIT 002 SUBCHANNEL = 003C AR 0015 0AA2 DEVTYPE OSA CHPID 03 OSD AR 0015 0AA2 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE But when the CSI TCP/IP stack tries to initialize, it receives: G1 0484 0S39I ERROR DURING OSA EXPRESS PROCESSING,REASON=0035 CUU=0AA0,RETCODE=E080 G1 0487 0003: IPL605E Unable to Initialize IJBOSA, return code: 122 G1 0487 0003: IPL609E Unable to initialize OSA Express, Link: AILLAN0 G1 0487 0004: IPL491I OSA-X link AILHIS0 started as 10.1.20.2 G1 0487 0005: IPL491I OSA-X link AILVSW0 started as 192.168.199.2 (The AILVSW0 is a previous defined VSWITCH that is internal only to communicate between VMs. And this has been working for quite some time now.) There is nothing notable on the DTCVSWn consoles. The error message description is less than hepful: REASON = X’0035’ The Startlan function failed. This is most likely indicated by RETCODE=E080. Thoughts? Frank M. Ramaekers Jr. Systems ProgrammerMCP, MCP+I, MCSE RHCE American Income Life Insurance Co.Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76701 _ 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 privacy...@ailife.com. -- Mark D Pace Senior Systems Engineer Mainline Information Systems _ 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 privacy...@ailife.com. -- Mark D Pace Senior Systems Engineer Mainline Information Systems _ 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 privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
On Friday, 08/27/2010 at 03:18 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: The error message description is less than hepful: REASON = X?0035? The Startlan function failed. This is most likely indicated by RETCODE=E080. The OSA/SF book, which has those error codes in it, says: E080 A LAN connection could not be made, possibly for one of the following reasons: The cable may not be present The LAN may not be functioning The port may have been disabled from the Support Element (SE) of the server This suggests that the NIC is not COUPLEd to the VSWITCH. You need to issue 'cp q v nic aa0 details'. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH defined VSE TCP/IP fails
* cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E LAN: * None MFS: 8992 AR 0015 RX Packets: 0 Discarded: 0 Errors: 0 AR 0015 TX Packets: 0 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 0TX Bytes: 0 AR 0015 Unassigned Devices: AR 0015 Device: 0AA0 Unit: 000 Role: Unassigned AR 0015 Device: 0AA1 Unit: 001 Role: Unassigned AR 0015 Device: 0AA2 Unit: 002 Role: Unassigned But the other one (one without any RDEVs): * cp q v nic a90 details AR 0015 Adapter 0A90.P00 Type: QDIO Name: UNASSIGNED Devices: 9 AR 0015 MAC: 02-00-01-00-00-0B VSWITCH: SYSTEM VSWTMK00 AR 0015 RX Packets: 6 Discarded: 0 Errors: 0 AR 0015 TX Packets: 5 Discarded: 0 Errors: 0 AR 0015 RX Bytes: 277 TX Bytes: 204 AR 0015 Connection Name: Session Established AR 0015 Device: 0A90 Unit: 000 Role: CTL-READ AR 0015 Device: 0A91 Unit: 001 Role: CTL-WRITE AR 0015 Device: 0A92 Unit: 002 Role: DATA vPort: 0085 Index: 0085 AR 0015 Options: IPv4 AR 0015 Unicast IP Addresses: AR 0015 192.168.199.2MAC: 02-00-01-00-00-0B Local AR 0015 Unassigned Devices: AR 0015 Device: 0A93 Unit: 003 Role: Unassigned AR 0015 Device: 0A94 Unit: 004 Role: Unassigned AR 0015 Device: 0A95 Unit: 005 Role: Unassigned AR 0015 Device: 0A96 Unit: 006 Role: Unassigned AR 0015 Device: 0A97 Unit: 007 Role: Unassigned AR 0015 Device: 0A98 Unit: 008 Role: Unassigned These devices were all listed as FREE before I started this. Frank M. Ramaekers Jr. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Friday, August 27, 2010 3:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH defined VSE TCP/IP fails On Friday, 08/27/2010 at 03:18 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: The error message description is less than hepful: REASON = X?0035? The Startlan function failed. This is most likely indicated by RETCODE=E080. The OSA/SF book, which has those error codes in it, says: E080 A LAN connection could not be made, possibly for one of the following reasons: The cable may not be present The LAN may not be functioning The port may have been disabled from the Support Element (SE) of the server This suggests that the NIC is not COUPLEd to the VSWITCH. You need to issue 'cp q v nic aa0 details'. Alan Altmark z/VM Development 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 privacy...@ailife.com.
Re: VSWITCH defined VSE TCP/IP fails
On Friday, 08/27/2010 at 04:28 EDT, Frank M. Ramaekers framaek...@ailife.com wrote: * cp q v nic aa0 details AR 0015 Adapter 0AA0.P00 Type: QDIO Name: UNASSIGNED Devices: 3 AR 0015 MAC: 02-00-01-00-00-0E LAN: * None And there you have it. The adapter is not COUPLED, as indicated by the * None. An uncoupled NIC is the equivalent of an unplugged ethernet cable. Alan Altmark z/VM Development IBM Endicott
