z/VM 5.2 sl 0602, OSA/IP problem
I'm hoping that there is a fix for this, because a known fix, is easier to fix then changing our network G. I have two LPARs, LPAR0, is the 390 side. z/VM 5.1 IP address 205.235.227.74 Runs mostly VSE guests, IP address 192.168.99.xxx OSA ports 2000 - 2005 LPAR1, is the IFL side. z/VM 5.1 IP address is 192.168.193.3 (this is a supernet 192.168.192/22) Runs mostly zLinux guests, IP address 192.168.193.xxx OSA ports 2010-2015 Both LPARs are using vswitch. Instead of installing z/VM 5.2 in another LPAR, I installed it, second level, under LPAR0. VMTEST on the 390 side z/VM 5.2 IP address 192.168.194.4 (note that this address is covered by the supernet, but LPAR1 isn't using this Class C network). OSA ports 2016-2018. Note all addresses are on the same OSA card, and the same port on the card. If the network types are doing any routing for me, everything should be getting to the same, physical cable. So I'm hoping that any routing problems can be solved on my side. I can ping myself 192.168.194.4. I cannot ping 192.168.194.1, 205.235.227.41, 205.235.227.74, 192.168.3.21 (my PC). And it doesn't seem that anyone can ping me (192.168.194.4). netstat home VM TCP/IP Netstat Level 520 IPv4 Home address entries: Address Subnet Mask Link --- --- -- 192.168.194.4 255.255.255.0QDIO1 IPv6 Home address entries: None Ready; T=0.02/0.04 11:14:00 netstat gate VM TCP/IP Netstat Level 520 Known IPv4 gateways: Subnet Address Subnet Mask FirstHopFlgs PktSz Metric Link -- --- - -- -- Default none 205.235.227.41 UGS 1500 none QDIO1 192.168.194.0 255.255.255.0directUT 1500 none QDIO1 205.235.227.0 255.255.255.0directUS 1500 none QDIO1 Known IPv6 gateways: None Ready; T=0.02/0.04 11:14:16 netstat dev VM TCP/IP Netstat Level 520 Device [EMAIL PROTECTED]Type: OSDStatus: Ready Queue size: 0 CPU: 0 Address: 2016Port name: UNASSIGNED IPv4 Router Type: NonRouter Arp Query Support: Yes Link QDIO1 Type: QDIOETHERNET Net number: 0 BytesIn: 0 BytesOut: 308 Forwarding: Enabled MTU: 1500IPv6: Disabled Broadcast Capability: Yes Multicast Capability: Yes Group Members - --- 224.0.0.1 1 Ready; T=0.02/0.03 11:14:31 The config file: ; -- DEVICE [EMAIL PROTECTED] OSD 2016 LINK QDIO1 QDIOETHERNET [EMAIL PROTECTED] MTU 1500 ; (End DEVICE and LINK statements) ; -- ; -- HOME 192.168.194.4 255.255.255.000 QDIO1 ; (End HOME Address information) ; -- GATEWAY ; Network Subnet First Link MTU
Re: z/VM 5.2 sl 0602, OSA/IP problem
You say /22, but your netmask is set for /24. Tom Duerbusch wrote: I'm hoping that there is a fix for this, because a known fix, is easier to fix then changing our network G. I have two LPARs, LPAR0, is the 390 side. z/VM 5.1 IP address 205.235.227.74 Runs mostly VSE guests, IP address 192.168.99.xxx OSA ports 2000 - 2005 LPAR1, is the IFL side. z/VM 5.1 IP address is 192.168.193.3 (this is a supernet 192.168.192/22) Runs mostly zLinux guests, IP address 192.168.193.xxx OSA ports 2010-2015 Both LPARs are using vswitch. Instead of installing z/VM 5.2 in another LPAR, I installed it, second level, under LPAR0. VMTEST on the 390 side z/VM 5.2 IP address 192.168.194.4 (note that this address is covered by the supernet, but LPAR1 isn't using this Class C network). OSA ports 2016-2018. Note all addresses are on the same OSA card, and the same port on the card. If the network types are doing any routing for me, everything should be getting to the same, physical cable. So I'm hoping that any routing problems can be solved on my side. I can ping myself 192.168.194.4. I cannot ping 192.168.194.1, 205.235.227.41, 205.235.227.74, 192.168.3.21 (my PC). And it doesn't seem that anyone can ping me (192.168.194.4). netstat home VM TCP/IP Netstat Level 520 IPv4 Home address entries: Address Subnet Mask Link --- --- -- 192.168.194.4 255.255.255.0QDIO1 IPv6 Home address entries: None Ready; T=0.02/0.04 11:14:00 netstat gate VM TCP/IP Netstat Level 520 Known IPv4 gateways: Subnet Address Subnet Mask FirstHopFlgs PktSz Metric Link -- --- - -- -- Default none 205.235.227.41 UGS 1500 none QDIO1 192.168.194.0 255.255.255.0directUT 1500 none QDIO1 205.235.227.0 255.255.255.0directUS 1500 none QDIO1 Known IPv6 gateways: None Ready; T=0.02/0.04 11:14:16 netstat dev VM TCP/IP Netstat Level 520 Device [EMAIL PROTECTED]Type: OSDStatus: Ready Queue size: 0 CPU: 0 Address: 2016Port name: UNASSIGNED IPv4 Router Type: NonRouter Arp Query Support: Yes Link QDIO1 Type: QDIOETHERNET Net number: 0 BytesIn: 0 BytesOut: 308 Forwarding: Enabled MTU: 1500IPv6: Disabled Broadcast Capability: Yes Multicast Capability: Yes Group Members - --- 224.0.0.1 1 Ready; T=0.02/0.03 11:14:31 The config file: ; -- DEVICE [EMAIL PROTECTED] OSD 2016 LINK QDIO1 QDIOETHERNET [EMAIL PROTECTED] MTU 1500 ; (End DEVICE and LINK statements) ; -- ; -- HOME 192.168.194.4 255.255.255.000 QDIO1 ; (End HOME Address information) ; -- GATEWAY
Re: z/VM 5.2 sl 0602, OSA/IP problem
Two different systems... LPAR1 is /22. The netmask which I didn't show is: 000.000.003.0 The netmask I did show, which is /24, is for the second level system on LPAR0. I took down LPAR1 last night, and brought up the second level system, now first level. Just to see if the supernet was getting involved and preventing me doing what I wanted. But I had the same problems. Tom Duerbusch THD Consulting [EMAIL PROTECTED] 12/5/2006 10:53 AM You say /22, but your netmask is set for /24. Tom Duerbusch wrote: I'm hoping that there is a fix for this, because a known fix, is easier to fix then changing our network G. I have two LPARs, LPAR0, is the 390 side. z/VM 5.1 IP address 205.235.227.74 Runs mostly VSE guests, IP address 192.168.99.xxx OSA ports 2000 - 2005 LPAR1, is the IFL side. z/VM 5.1 IP address is 192.168.193.3 (this is a supernet 192.168.192/22) Runs mostly zLinux guests, IP address 192.168.193.xxx OSA ports 2010-2015 Both LPARs are using vswitch. Instead of installing z/VM 5.2 in another LPAR, I installed it, second level, under LPAR0. VMTEST on the 390 side z/VM 5.2 IP address 192.168.194.4 (note that this address is covered by the supernet, but LPAR1 isn't using this Class C network). OSA ports 2016-2018. Note all addresses are on the same OSA card, and the same port on the card. If the network types are doing any routing for me, everything should be getting to the same, physical cable. So I'm hoping that any routing problems can be solved on my side. I can ping myself 192.168.194.4. I cannot ping 192.168.194.1, 205.235.227.41, 205.235.227.74, 192.168.3.21 (my PC). And it doesn't seem that anyone can ping me (192.168.194.4). netstat home VM TCP/IP Netstat Level 520 IPv4 Home address entries: Address Subnet Mask Link --- --- -- 192.168.194.4 255.255.255.0QDIO1 IPv6 Home address entries: None Ready; T=0.02/0.04 11:14:00 netstat gate VM TCP/IP Netstat Level 520 Known IPv4 gateways: Subnet Address Subnet Mask FirstHopFlgs PktSz Metric Link -- --- - -- -- Default none 205.235.227.41 UGS 1500 none QDIO1 192.168.194.0 255.255.255.0directUT 1500 none QDIO1 205.235.227.0 255.255.255.0directUS 1500 none QDIO1 Known IPv6 gateways: None Ready; T=0.02/0.04 11:14:16 netstat dev VM TCP/IP Netstat Level 520 Device [EMAIL PROTECTED]Type: OSDStatus: Ready Queue size: 0 CPU: 0 Address: 2016Port name: UNASSIGNED IPv4 Router Type: NonRouter Arp Query Support: Yes Link QDIO1 Type: QDIOETHERNET Net number: 0 BytesIn: 0 BytesOut: 308 Forwarding: Enabled MTU: 1500IPv6: Disabled Broadcast Capability: Yes Multicast Capability: Yes Group Members - --- 224.0.0.1 1 Ready; T=0.02/0.03 11:14:31 The config file: ; -- DEVICE [EMAIL PROTECTED] OSD 2016 LINK QDIO1 QDIOETHERNET [EMAIL PROTECTED] MTU 1500 ; (End DEVICE and LINK statements)
Re: z/VM 5.2 sl 0602, OSA/IP problem
Tom, You have one network device on your system (QDIO1 - 192.168.193.3). Your routing table states that you have a direct connection throught that device to 205.235.227.0/24 which is not on your network. So, you're not on the same network as the default gateway you have configured, which would explain why you cannot PING 205.235.227.41, 205.235.227.74 and 192.168.3.21. As to why you can't PING 192.168.194.1, I'm not sure, is that host up? Is that host actually attached to the same network as QDIO1? Regards, Miguel Delapaz z/VM TCP/IP Development
Re: z/VM 5.2 sl 0602, OSA/IP problem
Pictures and emailarrg! | | | |lpar0 | lpar1 | | z/VM 5.1 (390)| z/VM 5.1 (IFL)| | cua 2000-2002 OSA | cua 2010-2012 OSA | | 205.235.227.74 home | 192.168.193.3 home| | netmask 255.255.255.0 | netmask 255.255.252.0 | | gateway 205.235.227.41| gateway 192.168.192.1 | _ | Guest Machines (VSE) | Guest machines zLinux | | 192.168.99.xxx| 192.168.193.xxx | | using vswitch | using vswitch | _ | VMTEST z/VM 5.2 | | cua 2016-2018 | | 192.168.194.4 home| | netmask 255.255.255.0 | | gateway 192.168.194.1 | _ On the VMTEST system, I don't care what IP address it is. Nor do I care about the netmask or gateway. I was attempting to use some of the unused addresses in my supernet. A little history. When the z/890 was being installed, I asked the network guys for 4 ranges of addresses. 1 set for the IFL side 1 set for the internal lan on the z/890 (between the laptops and Win/XP remote service console) 1 set for our new DS6800 (between the laptops and the Win/XP remote service console) 1 set for the 390 side (for use while we had our 205.235.227.74 network on the MP3000, I needed another set on the z/890 390 side for parallel testing) Instead of 4 separate networks that didn't interfer with each other, they gave me 4 class C networks bundled together as a supernet. I sure didn't need 1000+ IP addresses, but they gave them to me and they worked.So far. I didn't use any of them for the z/890 or for the DS6800. By time they configured the supernet, I had some other addresses for these boxes. Now, for the first time, I'm trying to use some of these extra ip addresses. I thought that the IFL side, that has the supernet, might be intefering with my other use of some addresses in the VMTEST machine. But I took down LPAR1 with the supernet and brought up VMTEST as a first level system in LPAR1. I still couldn't connect. So this implies to me that I don't have a problem, yet, with the supernet stuff. OK I see what you mean about the defaultnet. I changed my statements to: HOME 192.168.194.4 255.255.255.000 QDIO1 ; (End HOME Address information) ; -- |...+1+2+3+4+5+6+7+.. GATEWAY ; Network Subnet First Link MTU ; Address MaskHop Name Size ; - --- --- - 205.235.227 255.255.255.0 = QDIO11500 DEFAULTNET 192.168.194.1 QDIO11500 ; DEFAULTNET 205.235.227.41 QDIO11500 ; (End GATEWAY Static Routing information) ; -- It didn't seem to make any change netstat gate VM TCP/IP Netstat Level 520 Known IPv4 gateways: Subnet Address Subnet Mask FirstHopFlgs PktSz Metric Link -- --- - -- -- Default none 192.168.194.1 UGS 1500 none QDIO1 192.168.194.0 255.255.255.0directUT 1500 none QDIO1 205.235.227.0 255.255.255.0directUS 1500 none QDIO1 Known IPv6 gateways: None Ready; T=0.02/0.03 13:40:21 ping 192.168.194.1 Ping Level 520: Pinging host
