Re: Was I confused? L2 Guest LAN, z/VM 5.4
Adam, What does NETSTAT DEV say? Regards, Miguel Delapaz z/VM Development NETSTAT HOME shows the right information (ETH1 is the L2 LAN; ETH0 a Layer 3 QDIO LAN, HSI0 is L3 Hypersockets, and CTC0 is a point-to- point CTC TCPIP link): netstat home VM TCP/IP Netstat Level 540 TCP/IP Server Name: TCPIP IPv4 Home address entries: Address Subnet Mask Link VSWITCH --- --- ----- 192.168.104.1 none CTC0 none 192.168.129.1 255.255.255.0ETH0 none 192.168.130.1 255.255.255.0HSI0 none 192.168.131.1 255.255.255.0ETH1 none So, did I just have a senior moment, or *should* this work? Adam
Re: Was I confused? L2 Guest LAN, z/VM 5.4
On May 15, 2009, at 2:14 PM, Miguel Delapaz wrote: Adam, What does NETSTAT DEV say? Well, *IT* says that my interface there is not working, and TCPIP startup bears this out: Device ETH1Type: OSDStatus: Inactive Queue size: 0 CPU: 0 Address: 7008Port name: UNASSIGNED IPv4 Router Type: PrimaryArp Query Support: No IPv6 Router Type: Primary Link ETH1 Type: QDIOETHERNET Port number: 0 Transport Type: IP Speed: 1 BytesIn: 0 BytesOut: 0 Forwarding: Enabled MTU: 1500IPv6: Configured IPv4 Path MTU Discovery: Disabled Broadcast Capability: Unknown, but previously not available Multicast Capability: Unknown The relevant bit of TCPIP startup is: 14:55:58 DTCOSD066E OSD device ETH1: ToOsd ProcessReadBuffer: Termination failur e code F6 14:55:58 DTCOSD355E OSD device ETH1: Possible LAN transport misconfiguration det ected during OSD device initialization. 14:55:58 DTCOSD082E OSD shutting down: 14:55:58 DTCPRI385IDevice ETH1: 14:55:58 DTCPRI386I Type: OSD, Status: Inoperative 14:55:58 DTCPRI387I Envelope queue size: 0 14:55:58 DTCPRI497I Address: 7008 Port Number: 0 HELP DTCOSD066E doesn't seem to help. Adam
Re: Was I confused? L2 Guest LAN, z/VM 5.4
Adam, Transport Type: IP This says your NIC is defined as Layer 3. 14:55:58 DTCOSD355E OSD device ETH1: Possible LAN transport misconfiguration detected during OSD device initialization. This says you tried to attach a Layer 3 NIC to a Layer 2 LAN (or vice-versa) Regards, Miguel Delapaz z/VM Development
Re: Was I confused? L2 Guest LAN, z/VM 5.4
On May 15, 2009, at 2:29 PM, Miguel Delapaz wrote: Adam, Transport Type: IP This says your NIC is defined as Layer 3. 14:55:58 DTCOSD355E OSD device ETH1: Possible LAN transport misconfiguration detected during OSD device initialization. This says you tried to attach a Layer 3 NIC to a Layer 2 LAN (or vice-versa) Indeed. I defined it to TCPIP with DIRM NICDEF and I don't see any way to specify whether I mean Layer 2 or Layer 3. I just defined it as QDIO. I think my cough syrup is failing me. How do I tell DIRMAINT, no, really, QDIO *ETHERNET* ? Adam
Re: Was I confused? L2 Guest LAN, z/VM 5.4
I defined it to TCPIP with DIRM NICDEF and I don't see any way to specify whether I mean Layer 2 or Layer 3. I just defined it as QDIO. I think my cough syrup is failing me. How do I tell DIRMAINT, no, really, QDIO *ETHERNET* ? Huh...that appears to be an interesting oversight on our part. I've forwarded your note off to the dirmaint developer for verification, but it doesn't look like it's possible at this point. Regards, Miguel Delapaz z/VM Development
Re: Was I confused? L2 Guest LAN, z/VM 5.4
Adam, You don't specify layer 2 or 3 on the NICDEF. You specify it on your DEFINE LAN or DEFINE VSWITCH statement. Dennis O'Brien If I'd only followed CNBC's advice, I'd have $1 million today, provided I'd started with $100 million. -- Jon Stewart From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Adam Thornton Sent: Friday, May 15, 2009 13:00 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Was I confused? L2 Guest LAN, z/VM 5.4 On May 15, 2009, at 2:29 PM, Miguel Delapaz wrote: Adam, Transport Type: IP This says your NIC is defined as Layer 3. 14:55:58 DTCOSD355E OSD device ETH1: Possible LAN transport misconfiguration detected during OSD device initialization. This says you tried to attach a Layer 3 NIC to a Layer 2 LAN (or vice-versa) Indeed. I defined it to TCPIP with DIRM NICDEF and I don't see any way to specify whether I mean Layer 2 or Layer 3. I just defined it as QDIO. I think my cough syrup is failing me. How do I tell DIRMAINT, no, really, QDIO *ETHERNET* ? Adam
Re: Was I confused? L2 Guest LAN, z/VM 5.4
On May 15, 2009, at 3:22 PM, O'Brien, Dennis L wrote: Adam, You don’t specify layer 2 or 3 on the NICDEF. You specify it on your DEFINE LAN or DEFINE VSWITCH statement. Yeah, but I DID that: Here's the L3 LAN: LAN SYSTEM GLAN1Type: QDIOConnected: 1Maxconn: INFINITE PERSISTENT UNRESTRICTED IPAccounting: OFF Here's the L2 LAN: LAN SYSTEM L2LANType: QDIOConnected: 2Maxconn: INFINITE PERSISTENT UNRESTRICTED ETHERNET Accounting: OFF I'm *pretty* sure (but not positive) that the lan definitions predated adding the NICs to TCPIP Adam
Re: Was I confused? L2 Guest LAN, z/VM 5.4
On May 15, 2009, at 3:24 PM, Miguel Delapaz wrote: I defined it to TCPIP with DIRM NICDEF and I don't see any way to specify whether I mean Layer 2 or Layer 3. I just defined it as QDIO. I think my cough syrup is failing me. How do I tell DIRMAINT, no, really, QDIO *ETHERNET* ? Huh...that appears to be an interesting oversight on our part. I've forwarded your note off to the dirmaint developer for verification, but it doesn't look like it's possible at this point. Um, OKthen how do I specify it in the directory entry? I don't mind doing a DIRM GET, editing the damn thing, and then doing a DIRM REPLACE.but what do I edit it *to* ? Adam
Re: Was I confused? L2 Guest LAN, z/VM 5.4
Why are you picking on poor ole DIRMAINT? It's CP that doesn't support it in the NICDEF statement! not DIRMAINT - from the zvm540 planning and admin guide: NICDEF__vdev _TYPE__ _HIPERsockets_ _|_ | | | |_QDIO_| | | | |_DEVices__devs_| | | |_LAN__ _ _ownerid_ __lanname_ _| | | | | |_*___| | | | | | |_SYSTEM__switchnm_| | | | |_CHPID__nn_| | | |_MACID__xx_| David Kreuter Original Message Subject: Re: [IBMVM] Was I confused? L2 Guest LAN, z/VM 5.4 From: Miguel Delapaz migu...@us.ibm.com Date: Fri, May 15, 2009 4:24 pm To: IBMVM@LISTSERV.UARK.EDU I defined it to TCPIP with DIRM NICDEF and I don't see any way to specify whether I mean Layer 2 or Layer 3. I just defined it as QDIO. I think my cough syrup is failing me. How do I tell DIRMAINT, no, really, QDIO *ETHERNET* ? Huh...that appears to be an interesting oversight on our part. I've forwarded your note off to the dirmaint developer for verification, but it doesn't look like it's possible at this point. Regards, Miguel Delapaz z/VM Development
Re: Was I confused? L2 Guest LAN, z/VM 5.4
Perhaps because historically it has been such an easy target? :-) Regards, Richard Schuh Why are you picking on poor ole DIRMAINT? It's CP that doesn't support it in the NICDEF statement! not DIRMAINT -
Re: Was I confused? L2 Guest LAN, z/VM 5.4
*Sigh*...yeah it's Friday...you tell the TCP/IP stack that this is a Layer 2 device by specifying the ETHERNET option on the LINK statement in PROFILE TCPIP Regards, Miguel Delapaz z/VM Development The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 05/15/2009 01:33:27 PM: Adam, You don’t specify layer 2 or 3 on the NICDEF. You specify it on your DEFINE LAN or DEFINE VSWITCH statement. Yeah, but I DID that: Here's the L3 LAN: LAN SYSTEM GLAN1Type: QDIOConnected: 1Maxconn: INFINITE PERSISTENT UNRESTRICTED IPAccounting: OFF Here's the L2 LAN: LAN SYSTEM L2LANType: QDIOConnected: 2Maxconn: INFINITE PERSISTENT UNRESTRICTED ETHERNET Accounting: OFF I'm *pretty* sure (but not positive) that the lan definitions predated adding the NICs to TCPIP Adam
Re: Was I confused? L2 Guest LAN, z/VM 5.4
On May 15, 2009, at 3:36 PM, David Kreuter wrote: Why are you picking on poor ole DIRMAINT? It's CP that doesn't support it in the NICDEF statement! not DIRMAINT - OK, so, look, surely I'm not the first person to want to do this. How do I couple a virtual machine's virtual NIC to a Layer 2 Guest LAN? How do I define a Virtual NIC for a virtual machine that is a Layer 2 device? CP Q V 7000 OSA 7000 ON NIC 7000 UNIT 000 SUBCHANNEL = 7000 DEVTYPE OSA CHPID 00 OSD 7000 MAC 02-00-00-00-00-01 CURRENT 7000 QDIO-ELIGIBLE QIOASSIST NOT AVAILABLE CP Q V 7008 OSA 7008 ON NIC 7008 UNIT 000 SUBCHANNEL = 0006 7008 DEVTYPE OSA CHPID 02 OSD 7008 MAC 02-00-00-00-00-03 CURRENT 7008 QDIO-ELIGIBLE QIOASSIST NOT AVAILABLE They look pretty much the same. Same error here (and I did just try deleting the NIC and then adding it back in case I needed to have the L2 LAN precreated...): 16:41:30 DTCOSD066E OSD device ETH1: ToOsd ProcessReadBuffer: Termination failur e code F6 16:41:30 DTCOSD355E OSD device ETH1: Possible LAN transport misconfiguration det ected during OSD device initialization. 16:41:30 DTCOSD082E OSD shutting down: 16:41:30 DTCPRI385IDevice ETH1: 16:41:30 DTCPRI386I Type: OSD, Status: Inoperative 16:41:30 DTCPRI387I Envelope queue size: 0 16:41:30 DTCPRI497I Address: 7008 Port Number: 0 Adam
Re: Was I confused? L2 Guest LAN, z/VM 5.4
OK, so, look, surely I'm not the first person to want to do this. With the ETHERNET option on the QDIOETHERNET LINK statement (in case you missed my other note) Regards, Miguel Delapaz z/VM Development
Re: Was I confused? L2 Guest LAN, z/VM 5.4
On May 15, 2009, at 4:09 PM, Miguel Delapaz wrote: OK, so, look, surely I'm not the first person to want to do this. With the ETHERNET option on the QDIOETHERNET LINK statement (in case you missed my other note) Yay! Thank you! (Your other note hadn't arrived quite yet.) I now have networking working to my Layer 2 guest. I am thrilled. Adam
