I was under the impression that z/VM 5.4 allowed you to define a Layer
2 guest LAN and then give z/VM an interface on that guest LAN. Am I
confused? I know that earlier z/VM versions did not support a Layer 2
Guest LAN interface for z/VM, but I thought the restriction had been
lifted in 5.4.
I ask because it really would be a lot more convenient to just let the
VM stack do all the routing, rather than having to set up a Linux
guest with one interface on the Guest LAN that VM is on, and one
interface on the L2 Guest LAN just to route packets between them.
q lan l2lan owner system details
LAN SYSTEM L2LAN Type: QDIO Connected: 2 Maxconn: INFINITE
PERSISTENT UNRESTRICTED ETHERNET Accounting: OFF
IPTimeout: 5
Isolation Status: OFF
Adapter Connections:
Adapter Owner: SOLARIS NIC: 0BC0.P00 Name: UNASSIGNED
RX Packets: 0 Discarded: 0 Errors: 0
TX Packets: 0 Discarded: 159 Errors: 0
RX Bytes: 0 TX Bytes: 0
Device: 0BC0 Unit: 000 Role: DATA-DIAG vPort: 0066 Index: 0066
Options: Ethernet Broadcast
Unicast MAC Addresses:
02-00-00-00-00-04
Multicast MAC Addresses:
01-00-5E-00-00-01
Adapter Owner: TCPIP NIC: 7008.P00 Name: UNASSIGNED
RX Packets: 0 Discarded: 0 Errors: 0
TX Packets: 0 Discarded: 0 Errors: 0
RX Bytes: 0 TX Bytes: 0
Device: 7008 Unit: 000 Role: DATA vPort: 0065 Index: 0065
...I note that the TCPIP L2 NIC doesn't actually have a MAC address,
which seems ominous.
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.0 ETH0 <none>
192.168.130.1 255.255.255.0 HSI0 <none>
192.168.131.1 255.255.255.0 ETH1 <none>
So, did I just have a senior moment, or *should* this work?
Adam
