Re: VM/ESA TCP/IP and VSWITCH
Well I'm guessing it can't. I have the following in my TCPIP PROFILE: DEVICE OSA1LCS600 ; LINKOSA1LNK ETHERNET 0 OSA1 ; ARPAGE 5 ; HOME 10.1.1.93 OSA1LNK ; GATEWAY 10.1.1.1 =OSA1LNK 1500HOST DEFAULTNET=OSA1LNK 15000 ; TRANSLATE ; START OSA1 And I get the following in the TCPIP console log: DTCPRI385I Device OSA1: DTCPRI386I Type: LCS, Status: Not started DTCPRI387I Envelope queue size: 0 DTCPRI388I Address: 0600 I change it to this: DEVICE OSA1OSD600 ; LINKOSA1LNK QDIOETHERNET 0 OSA1 ; ARPAGE 5 ; HOME 10.1.1.93 OSA1LNK ; GATEWAY 10.1.1.1 =OSA1LNK 1500HOST DEFAULTNET=OSA1LNK 15000 ; TRANSLATE ; START OSA1 And I get the following: DTCPRS007E Error encountered in reading PROFILE TCPIP *: DTCPAR123I Line 237: Invalid type field DTCPAR123I Line 239: LINK statement: Invalid type field DTCPAR123I Line 244: Unknown link name in HOME cmd DTCPAR123I Line 247: Unknown link name in GATEWAY cmd DTCPAR123I Line 252: Device not found Line 237 corresponds to my DEVICE statement and line 239 is the LINK statement. 600 - 602 is attached to my TCPIP on the VM/ESA 2.40 guest and I have NICDEF and GRANT for the VMEASA240 guest in z/VM Unless anyone can point out something obivious I'm going to chalk this up to experience. Thanks, Billy On 17 Mar 2010 at 10:13, The IBM z/VM Operating System wrote: Hello, Would VM/ESA running 2nd level under z/VM be able to use the VSWITCH? Thanks, Billy
Re: VM/ESA TCP/IP and VSWITCH
Hi Billy I'm no expert at this, but you've defined your device as a LCS device, not a QDIO. A VSwitch has to be QDIO, so you need to change your device (and link) statements accordingly. For instance, I have DEVICE OSAQDIO OSD 0440 PORTNAME OSA1 PRIROUTER AUTORESTART LINKETH0QDIOETHERNET OSAQDIO1 ane the linkname in the home statement points to ETH0 device 440 is a 'port' into the VSwitch. In your case, your TCPIP is in a 2nd level system, but it still has to be in QDIO mode. If your level of TCP/IP does not support QDIO, you will find out as soon as it tries to process the DEVICE staatement. Mike Hammock - Original Message - From: Billy Bingham To: IBMVM@LISTSERV.UARK.EDU Sent: Friday, March 19, 2010 12:17 PM Subject: Re: VM/ESA TCP/IP and VSWITCH Well I'm guessing it can't. I have the following in my TCPIP PROFILE: DEVICE OSA1LCS600 ; LINKOSA1LNK ETHERNET 0 OSA1 ; ARPAGE 5 ; HOME 10.1.1.93 OSA1LNK ; GATEWAY 10.1.1.1 =OSA1LNK 1500HOST DEFAULTNET=OSA1LNK 15000 ; TRANSLATE ; START OSA1 And I get the following in the TCPIP console log: DTCPRI385I Device OSA1: DTCPRI386I Type: LCS, Status: Not started DTCPRI387I Envelope queue size: 0 DTCPRI388I Address: 0600 I change it to this: DEVICE OSA1OSD600 ; LINKOSA1LNK QDIOETHERNET 0 OSA1 ; ARPAGE 5 ; HOME 10.1.1.93 OSA1LNK ; GATEWAY 10.1.1.1 =OSA1LNK 1500HOST DEFAULTNET=OSA1LNK 15000 ; TRANSLATE ; START OSA1 And I get the following: DTCPRS007E Error encountered in reading PROFILE TCPIP *: DTCPAR123I Line 237: Invalid type field DTCPAR123I Line 239: LINK statement: Invalid type field DTCPAR123I Line 244: Unknown link name in HOME cmd DTCPAR123I Line 247: Unknown link name in GATEWAY cmd DTCPAR123I Line 252: Device not found Line 237 corresponds to my DEVICE statement and line 239 is the LINK statement. 600 - 602 is attached to my TCPIP on the VM/ESA 2.40 guest and I have NICDEF and GRANT for the VMEASA240 guest in z/VM Unless anyone can point out something obivious I'm going to chalk this up to experience. Thanks, Billy On 17 Mar 2010 at 10:13, The IBM z/VM Operating System wrote: Hello, Would VM/ESA running 2nd level under z/VM be able to use the VSWITCH? Thanks, Billy
Re: VM/ESA TCP/IP and VSWITCH
The doc for TCP/IP for VM/ESA FL320 (which ran on VM/ESA 2.4) is still on line. There is no indication of QDIO device support in the Planning manual. Unless is was added after GA. On 03/19/2010 11:17 AM, Billy Bingham wrote: Well I'm guessing it can't. I have the following in my TCPIP PROFILE: DEVICE OSA1LCS600 ; LINKOSA1LNK ETHERNET 0 OSA1 ; ARPAGE 5 ; HOME 10.1.1.93 OSA1LNK ; GATEWAY 10.1.1.1 =OSA1LNK 1500 HOST DEFAULTNET=OSA1LNK 15000 ; TRANSLATE ; START OSA1 And I get the following in the TCPIP console log: DTCPRI385I Device OSA1: DTCPRI386I Type: LCS, Status: Not started DTCPRI387I Envelope queue size: 0 DTCPRI388I Address: 0600 I change it to this: DEVICE OSA1OSD600 ; LINKOSA1LNK QDIOETHERNET 0 OSA1 ; ARPAGE 5 ; HOME 10.1.1.93 OSA1LNK ; GATEWAY 10.1.1.1 =OSA1LNK 1500HOST DEFAULTNET=OSA1LNK 15000 ; TRANSLATE ; START OSA1 And I get the following: DTCPRS007E Error encountered in reading PROFILE TCPIP *: DTCPAR123I Line 237: Invalid type field DTCPAR123I Line 239: LINK statement: Invalid type field DTCPAR123I Line 244: Unknown link name in HOME cmd DTCPAR123I Line 247: Unknown link name in GATEWAY cmd DTCPAR123I Line 252: Device not found Line 237 corresponds to my DEVICE statement and line 239 is the LINK statement. 600 - 602 is attached to my TCPIP on the VM/ESA 2.40 guest and I have NICDEF and GRANT for the VMEASA240 guest in z/VM Unless anyone can point out something obivious I'm going to chalk this up to experience. Thanks, Billy -- Rich Smrcina Phone: 414-491-6001 http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2010 - Apr 9-13, 2010 Covington, KY
Re: VM/ESA TCP/IP and VSWITCH
To use a VSWITCH, the guest must support QDIO, and I'd be surprised if a that old VM/ESA would know about QDIO 2010/3/17 Billy Bingham billy.bingham...@suddenlink.net Hello, Would VM/ESA running 2nd level under z/VM be able to use the VSWITCH? Thanks, Billy -- Kris Buelens, IBM Belgium, VM customer support
Re: VM/ESA TCP/IP and VSWITCH
VM/ESA 2.4 had QDIO support (in fact it was the last release to have that module delivered with source). 2.3 might have had it, but I can't remember. I suspect it would work, but can't try it (no longer have a IPLable 2.4 system). From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: Thursday, March 18, 2010 1:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VM/ESA TCP/IP and VSWITCH To use a VSWITCH, the guest must support QDIO, and I'd be surprised if a that old VM/ESA would know about QDIO
