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
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: 7008
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
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
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
. -- 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
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
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* ?
| | |
| |_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
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 -
*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,
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
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
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
14 matches
Mail list logo
