Hi, In the past I had a similar problem but don't really remember if I was still on zVM 4.4 or zVM 5.2. The problem was fixed after applying the latest maintenance to zVM.
Regards, -Jose -----Original Message----- From: Hans Rempel [mailto:[EMAIL PROTECTED] Sent: Monday, August 20, 2007 4:13 PM To: [email protected] Subject: Linux Network problem using VSWITCH I have a default VSWITCH defined and connected to my OSA express card. z/VM 5.2. The following userids are coupled to the VSWITCH. Q vswitch detail output at end of note. TCPIP (142.214.154.50) LINUX02 (142.214.154.42) (SLES10) SLES10 (142.214.154.51) (SLES10) LINUX04 (142.214.154.44) (SELS10) LINWAS (142.214.154.45) (SLES9) Gateway IP is 142.214.154.1 Mask is 255.255.255.128 From LINUX04 I can ping TCPIP but not LINUX02 or SLES10 From TCPIP I can ping all Linux systems From LAN (142.214.195.65-different subnet) I can ping all. Problem: I can not ping from any of the linux guest to any other. My route on linux is a follows: route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 142.214.154.0 * 255.255.255.128 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default 142.214.154.1 0.0.0.0 UG 0 0 0 eth0LinuxSLES10Controller:~ # My IFCONFIG is ifconfig eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:02 inet addr:142.214.154.51 Bcast:142.214.154.127 Mask:255.255.255.128 inet6 addr: fe80::200:0:600:2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:3239 errors:0 dropped:0 overruns:0 frame:0 TX packets:2816 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:724403 (707.4 Kb) TX bytes:572241 (558.8 Kb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:328 errors:0 dropped:0 overruns:0 frame:0 TX packets:328 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:47792 (46.6 Kb) TX bytes:47792 (46.6 Kb) I can't see why this shouldn't work Now here's the scary part: I changed the routes file on LINUX02 to Default 142.214.154.1 255.255.255.128 and recycled the network card. I was then able to ping LINUX04 and I think it worked because it went out to the gateway. I was not able to ping LINUX02 from a different subnet on the LAN so I changed back the route default to 0.0.0.0. By doing this both LINUX04 and LINUX02 can ping each other but I still cannot ping SLES10. Did VSWITCH record/map the IP address to the MAC address or something? Do I need a fix? Any comments/suggested are greatly appreciated. Thanks Hans Rempel q vswitch detail VSWITCH SYSTEM OSALIN1 Type: VSWITCH Connected: 5 Maxconn: INFINITE PERSISTENT RESTRICTED NONROUTER Accounting: OFF VLAN Unaware State: Ready IPTimeout: 5 QueueStorage: 8 Portname: OSATCP2 RDEV: 8003 Controller: DTCVSW2 VDEV: 8003 VSWITCH Connection: RX Packets: 52009 Discarded: 0 Errors: 0 TX Packets: 48246 Discarded: 0 Errors: 0 RX Bytes: 8621914 TX Bytes: 9918226 Device: 8003 Unit: 000 Role: DATA Adapter Owner: LINUX02 NIC: EB00 Name: dontcare RX Packets: 2838 Discarded: 0 Errors: 0 TX Packets: 2430 Discarded: 0 Errors: 0 RX Bytes: 752172 TX Bytes: 319193 Device: EB02 Unit: 002 Role: DATA Options: Broadcast Multicast IPv6 IPv4 VLAN Unicast IP Addresses: 142.214.154.42 MAC: 02-00-00-00-00-03 FE80::200:0:100:3 MAC: 02-00-00-00-00-03 Local Multicast IP Addresses: FF02::1 MAC: 33-33-00-00-00-01 FF02::1:FF00:3 MAC: 33-33-FF-00-00-03 Local Adapter Owner: LINUX04 NIC: EB00 Name: dontcare RX Packets: 7918 Discarded: 0 Errors: 0 TX Packets: 6329 Discarded: 0 Errors: 0 RX Bytes: 2453281 TX Bytes: 2020475 Device: EB02 Unit: 002 Role: DATA Options: Broadcast Multicast IPv6 IPv4 VLAN Unicast IP Addresses: 142.214.154.44 MAC: 02-00-00-00-00-04 FE80::200:0:100:4 MAC: 02-00-00-00-00-04 Local Multicast IP Addresses: FF02::1 MAC: 33-33-00-00-00-01 FF02::1:FF00:4 MAC: 33-33-FF-00-00-04 Local Adapter Owner: LINWAS NIC: EB00 Name: suselin7 RX Packets: 88 Discarded: 0 Errors: 0 TX Packets: 174 Discarded: 0 Errors: 0 RX Bytes: 6971 TX Bytes: 9448 Device: EB02 Unit: 002 Role: DATA Options: Broadcast Multicast IPv6 IPv4 VLAN Unicast IP Addresses: 142.214.154.45 MAC: 02-00-00-00-00-05 Multicast IP Addresses: 224.0.0.1 MAC: 01-00-5E-00-00-01 224.0.0.251 MAC: 01-00-5E-00-00-FB 224.0.1.22 MAC: 01-00-5E-00-01-16 239.255.255.253 MAC: 01-00-5E-7F-FF-FD Adapter Owner: SLES10 NIC: EB00 Name: dontcare RX Packets: 19869 Discarded: 0 Errors: 0 TX Packets: 14273 Discarded: 0 Errors: 0 RX Bytes: 3993106 TX Bytes: 3013578 Device: EB02 Unit: 002 Role: DATA Options: Broadcast Multicast IPv6 IPv4 VLAN Unicast IP Addresses: 142.214.154.51 MAC: 02-00-00-00-00-02 FE80::200:0:600:2 MAC: 02-00-00-00-00-02 Local Multicast IP Addresses:224.0.0.1 MAC: 01-00-5E-00-00-01 FF02::1 MAC: 33-33-00-00-00-01 FF02::12B MAC: 33-33-00-00-01-2B Local FF02::1:FF00:2 MAC: 33-33-FF-00-00-02 Local Adapter Owner: TCPIP NIC: 0600 Name: UNASSIGNED RX Packets: 25287 Discarded: 0 Errors: 0 TX Packets: 21744 Discarded: 0 Errors: 0 RX Bytes: 1935445 TX Bytes: 4066929 Device: 0602 Unit: 002 Role: DATA Options: Broadcast Multicast IPv4 VLAN Unicast IP Addresses: 142.214.154.50 MAC: 02-00-00-00-00-01 Multicast IP Addresses: 224.0.0.1 MAC: 01-00-5E-00-00-01 Ready; T=0.01/0.01 15:52:55 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 Scanned by McAfee SCM1 Scanned by Triple-S SCM1 ----------------------------------------- *************************Attention************************* This electronic message, including any attachments, contains information that may be legally confidential and/or privileged. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error and delete it from your system.
