Re: Hipersockets Conundrum Revisited
On Monday, 07/09/2007 at 11:10 AST, Kim Goldenberg <[EMAIL PROTECTED]> wrote: > HOME > xxx.yyy.1.101 HIPER50 Make sure you are using chpid 50 on Linux. 1. CP Q V xxx (where xxx is the vdev of the HiperSocket). Note the SUBCHANNEL number. 2. CP D SCHIB nnn (where nnn is the subchannel number) 3. Look at the chpid number. Does it match? > (There is nothing explicit in routing information, we are using OMPROUTE > on z/OS) You need to display the routing table on z/OS. Since you're not [shouldn't be] running OSPF or RIP on the HiperSocket there will be an INTERFACE statement in omproute's configuration. If there isn't, then it is defaulting and omproute defaults are to be avoided at all costs. Alan Altmark z/VM Development IBM Endicott -- 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
Re: Hipersockets Conundrum Revisited
Alan Altmark wrote: On Monday, 07/09/2007 at 11:10 AST, Kim Goldenberg You need to display the routing table on z/OS. Since you're not [shouldn't be] running OSPF or RIP on the HiperSocket there will be an INTERFACE statement in omproute's configuration. If there isn't, then it is defaulting and omproute defaults are to be avoided at all costs. That was the problem. Just before I read this I, an explicit route was put in, and all works as expected now! Thanks for the hints. Kim -- Kim Goldenberg Systems Programmer I State of NJ - OIT 609-777-3722 [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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
Re: Hipersockets Conundrum Revisited
> > What are the IP addresses and subnet masks on the z/OS HiperSocket > interfaces? > ; *** > ; HIPERSOCKET CHIPID 50 > ; *** > DEVICE IUTIQD50 MPCIPA > LINK HIPER50 IPAQIDIO IUTIQD50 > HOME >zzz.yyy.72.82 OSA2 >xxx.yyy.11.1VLINK1 >xxx.yyy.1.22OSA1 >xxx.yyy.1.13OSA3 >xxx.yyy.1.101 HIPER50 >PRIMARYINTERFACE VLINK1 > (There is nothing explicit in routing information, we are using OMPROUTE > on z/OS) Hmm. This may be the problem. Since your HS link is in the same subnet as the OSA1 and OSA3 links, the routing information is going to be important; you need an explicit route on the z/OS side that points at the hipersocket interface for the portion of the subnet that contains the Linux guests. Can you dump the current routing table on z/OS? Also, the subnet mask is going to be important. What mask are you using for the HIPER50 interface? If it's not a routing problem, I'd have to agree with Alan -- they're not on the same HS chpid. -- 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
Re: Hipersockets Conundrum Revisited
Mark Post wrote: On Fri, Jul 6, 2007 at 2:44 PM, in message <[EMAIL PROTECTED]>, Kim Goldenberg <[EMAIL PROTECTED]> wrote: -snip- ifconfig eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:02 inet addr:xxx.yyy.40.21 Bcast:xxx.yyy.40.255 Mask:255.255.255.0 inet6 addr: fe80::200:0:600:2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12403 errors:0 dropped:0 overruns:0 frame:0 TX packets:7529 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9792252 (9.3 Mb) TX bytes:1988074 (1.8 Mb) hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:xxx.yyy.1.103 Bcast:xxx.yyy.1.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:8192 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:1000 RX bytes:0 (0.0 b) TX bytes:224 (224.0 b) -snip- What is the MTU size specified on the z/OS side of the HiperSockets? -- route A lot of times, it's more meaningful if you issue a "route -n" command so that IP addresses don't get replace with names. Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface xxx.yyy.1.0 * 255.255.255.0 U 0 00 hsi0 xxx.yyy.40.0* 255.255.255.0 U 0 00 eth0 link-local * 255.255.0.0 U 0 00 eth0 loopback* 255.0.0.0 U 0 00 lo default xxx.state.nj.us 0.0.0.0 UG0 00 eth0 What are the IP addresses and subnet masks on the z/OS HiperSocket interfaces? ; *** ; HIPERSOCKET CHIPID 50 ; *** DEVICE IUTIQD50 MPCIPA LINK HIPER50 IPAQIDIO IUTIQD50 . . . HOME zzz.yyy.72.82 OSA2 xxx.yyy.11.1VLINK1 xxx.yyy.1.22OSA1 xxx.yyy.1.13OSA3 xxx.yyy.1.101 HIPER50 PRIMARYINTERFACE VLINK1 . . . (There is nothing explicit in routing information, we are using OMPROUTE on z/OS) . . . START IUTIQD50 -- Kim Goldenberg Systems Programmer I State of NJ - OIT 609-777-3722 [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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
Re: Hipersockets Conundrum Revisited
On Monday, 07/09/2007 at 10:17 AST, Kim Goldenberg <[EMAIL PROTECTED]> wrote: > xxx.yyy.1.0 0.0.0.0 255.255.255.0 U 0 0 0 hsi0 I haven't been following this in detail, but I see two possibilities: 1. The OTHER system is configured INcorrectly. Remember that it is a two-way street; packets have to make their way back to you. 2. One of the two systems is using the wrong HiperSocket chpid. A packet trace on the other system will tell you if the packet is arriving. There's only so much debug you can do with a single system. Alan Altmark z/VM Development IBM Endicott -- 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
Re: Hipersockets Conundrum Revisited
David Boyes wrote: ifconfig eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:02 inet addr:xxx.yyy.40.21 Bcast:xxx.yyy.40.255 Mask:255.255.255.0 hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:xxx.yyy.1.103 Bcast:xxx.yyy.1.255 Mask:255.255.255.0 OK, adapters on separate networks, up and running. Check. xxx.yyy.1.0 * 255.255.255.0 U 0 0 0 hsi0 xxx.yyy.40.0* 255.255.255.0 U 0 0 0 eth0 Implicit routes going out the correct interfaces with the right netmasks. Check. default xxx.state.nj.us 0.0.0.0 UG0 0 0 eth0 Default route goes out the .40 interface. Check. All the basics look good. Are you explicitly specifying the IP address of the other host (xxx.yyy.1.zzz)? If you're using the name, then that probably maps to the .40 address (unless you're really good, and gave the .1.zzz address a different name, which is a Very Good Idea). What does a traceroute to the .1.zzz address show? Sorry. I combined two messages (yours and Mark Post's) into one without answering your question. traceroute -m 10 xxx.yyy.1.101 traceroute to xxx.yyy.1.101 (172.20.1.101), 10 hops max, 40 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * -- Kim Goldenberg Systems Programmer I State of NJ - OIT 609-777-3722 [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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
Re: Hipersockets Conundrum Revisited
David Boyes wrote: All the basics look good. Thanks. Are you explicitly specifying the IP address of the other host (xxx.yyy.1.zzz)? Specifying it where? in the ping? then yes. If you're using the name, then that probably maps to the .40 address (unless you're really good, and gave the .1.zzz address a different name, which is a Very Good Idea). What does a traceroute to the .1.zzz address show? route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface xxx.yyy.1.0 0.0.0.0 255.255.255.0 U 0 00 hsi0 xxx.yyy.40.00.0.0.0 255.255.255.0 U 0 00 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 00 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 xxx.yyy.40.1 0.0.0.0 UG0 00 eth0 Kim -- Kim Goldenberg Systems Programmer I State of NJ - OIT 609-777-3722 [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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
Re: Hipersockets Conundrum Revisited
>>> On Fri, Jul 6, 2007 at 2:44 PM, in message <[EMAIL PROTECTED]>, Kim Goldenberg <[EMAIL PROTECTED]> wrote: -snip- > ifconfig > eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:02 > inet addr:xxx.yyy.40.21 Bcast:xxx.yyy.40.255 Mask:255.255.255.0 > inet6 addr: fe80::200:0:600:2/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:12403 errors:0 dropped:0 overruns:0 frame:0 > TX packets:7529 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:9792252 (9.3 Mb) TX bytes:1988074 (1.8 Mb) > > hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:xxx.yyy.1.103 Bcast:xxx.yyy.1.255 Mask:255.255.255.0 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING NOARP MULTICAST MTU:8192 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:1000 > RX bytes:0 (0.0 b) TX bytes:224 (224.0 b) -snip- What is the MTU size specified on the z/OS side of the HiperSockets? > -- > route A lot of times, it's more meaningful if you issue a "route -n" command so that IP addresses don't get replace with names. > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse > Iface > xxx.yyy.1.0 * 255.255.255.0 U 0 00 hsi0 > xxx.yyy.40.0* 255.255.255.0 U 0 00 eth0 > link-local * 255.255.0.0 U 0 00 eth0 > loopback* 255.0.0.0 U 0 00 lo > default xxx.state.nj.us 0.0.0.0 UG0 00 eth0 What are the IP addresses and subnet masks on the z/OS HiperSocket interfaces? Mark Post -- 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
Re: Hipersockets Conundrum Revisited
> > ifconfig > eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:02 > inet addr:xxx.yyy.40.21 Bcast:xxx.yyy.40.255 > Mask:255.255.255.0 > > hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:xxx.yyy.1.103 Bcast:xxx.yyy.1.255 Mask:255.255.255.0 OK, adapters on separate networks, up and running. Check. > xxx.yyy.1.0 * 255.255.255.0 U 0 0 0 > hsi0 > xxx.yyy.40.0* 255.255.255.0 U 0 0 0 > eth0 Implicit routes going out the correct interfaces with the right netmasks. Check. > default xxx.state.nj.us 0.0.0.0 UG0 0 0 > eth0 Default route goes out the .40 interface. Check. All the basics look good. Are you explicitly specifying the IP address of the other host (xxx.yyy.1.zzz)? If you're using the name, then that probably maps to the .40 address (unless you're really good, and gave the .1.zzz address a different name, which is a Very Good Idea). What does a traceroute to the .1.zzz address show? -- 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
