I've got a test system running SUSE SLES7. The z/VM system is z/VM Version
4 Release 4.0, service level 0301 (64-bit). I have an OSA card on the
machine, connected to a VSWITCH. My guest is also connected to that
VSWITCH. The virtual NIC is defined as a QDIO device:
#cp q nic details
Adapter 0F00 Type: QDIO Name: LINUXSRV Devices: 3
Port 0 MAC: 02-00-00-00-00-00 VSWITCH: SYSTEM LNXSW1 MFS: 8192
RX Packets: 0 Discarded: 0 Errors: 0
TX Packets: 13 Discarded: 0 Errors: 0
RX Bytes: 0 TX Bytes: 848
Connection Name: HALLOLE State: Session Established
Device: 0F00 Unit: 000 Role: CTL-READ
Device: 0F01 Unit: 001 Role: CTL-WRITE
Device: 0F02 Unit: 002 Role: DATA
Unicast IP Addresses:
199.42.190.211 Mask: 255.255.255.0
Multicast IP Addresses:
224.0.0.1 MAC: 01-00-5E-00-00-01
Note the network mask on this: 255.255.255.0. At least this matches what
the GLAN thinks:
#cp q lan details
VSWITCH SYSTEM LNXSW1 Type: VSWITCH Active: 1 MAXCONN: INFINITE
PERSISTENT RESTRICTED NONROUTER MFS: 8192 ACCOUNTING: OFF
State: Ready
CONTROLLER: TCPCTL1 IPTIMEOUT: 5 QUEUESTORAGE: 8
PORTNAME: LINUX390 RDEV: 0040 VDEV: 0040
PORTNAME: UNASSIGNED RDEV: 0053
Authorized userids:
GLPSRV10 VLAN: ANY
GLPSRV11 VLAN: ANY
GLPSRV12 VLAN: ANY
GLPSRV16 VLAN: ANY
SYSTEM VLAN: ANY
Adapter Owner: GLPSRV10 NIC: 0F00 Name: LINUXSRV
Device: 0F02 Unit: 002 Role: DATA
Unicast IP Addresses:
199.42.190.211 Mask: 255.255.255.0
Multicast IP Addresses:
224.0.0.1 MAC: 01-00-5E-00-00-01
My network parameters have it defined as 255.255.255.240:
ifconfig eth0
eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:00
inet addr:199.42.190.211 Mask:255.255.255.240
inet6 addr: fe80::ff:fe00:0/10 Scope:Link
UP RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:352 (352.0 b)
Interrupt:8
This can't be good, so has anyone else seen this? Am I missing some
maintenance on either z/VM or SLES7 to fix it? Is this really a problem?
And so on. I can't be sure myself, because other issues elsewhere in the
network are preventing connecting to the system.
Thanks,
Mark Post
