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
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
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
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
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
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
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
Hipersockets Conundrum Revisited
A week has gone by, I fubared the original install trying to fix it; so I spent a couple of days creating a new install. I have the system installed and almost up to SLES9x SP3. SPident complains about two XFree86-Mesa packages not being up to the SP2 level, but I can't find the update RPMs on the Novell site to download ad update the system. As they should not affect network interfaces, I'm satisfied, event if SPident is not. I will say that I am a bit confused abut YOU showing all these updates, but not selecting them. Many seem either back-level or for products not installed. I once again have installed the OSA adapter (needed for NFS install). I also reinstalled the Hipersockets definition. information follows: eth0 = OSA adapter hsi0 = Hipersockets 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) loLink 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:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:752 (752.0 b) TX bytes:752 (752.0 b) -- route 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 -- uname -a Linux lnxa0001 2.6.5-7.286-s390x #1 SMP Thu May 31 10:12:58 UTC 2007 s390x s390x s390x GNU/Linux xxx.yyy is the same for each adapter above. Any ideas? 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
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
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
Rich Smrcina wrote: So are your OSA devices and Hipersocket devices all on the same network? In other words do they all have a 172.20.1.x address with a netmask of 255.255.255.0? No, Hipersockets on 172.20.1/24 and OSAs on 172.20.40/24 via vswitch. 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
David Kreuter wrote: also check that the MTU sizes match. David Hi Dave - First thing I checked. -- 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
Graft a VM TCPIP stack on the vm lpar to the hipersocket CHPID. See if: 1. it can ping and vice versa with the linux virtual machine 2. see if it can ping and vice versa with one or both of the MVS LPARs. Sometime a wimpy zvm stack machine comes in handy. David -Original Message- From: Linux on 390 Port on behalf of Kim Goldenberg Sent: Mon 7/2/2007 12:13 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Hipersockets Conundrum David Kreuter wrote: also check that the MTU sizes match. David Hi Dave - First thing I checked. -- 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 -- 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
Mark Post wrote: On Fri, Jun 29, 2007 at 3:43 PM, in message [EMAIL PROTECTED], Kim Goldenberg [EMAIL PROTECTED] wrote: We are starting our Linux POC and all has been going well. Until I got to the Hipersockets, that is. -snip- z/OS -- OSA -- network -- OSA -- Linux (on vswitch) Wanted: z/OS -- Hipersockets -- Linux -snip- Any ideas as to why the SLES9x will not talk to z/OS? Any thing I should look for, ask or z/OS network people, etc.? Can the Linux guest ping either of the z/OS systems? Does the Linux guest still have the OSA connection defined as a NIC? If so, what IP address and subnet mask is assigned to it? If it's a 172.20.2.x/24 address, that is most likely your problem (although I would expect that to still work,just not by using the HiperSocket). SLES9x info: lnxa0001:/home/otsgold # uname -a Linux lnxa0001 2.6.5-7.244-s390x #1 SMP Mon Dec 12 18:32:25 UTC 2005 s390x s390x s390x GNU/Linux It wouldn't hurt to make sure you have on all the maintenance for SLES9. Your kernel is not the most current. A better picture of _all_ the network interfaces, with IP addresses, network masks, routing, etc. for the z/OS systems and the Linux guest would be useful. I should learn to wake up before doing radical things. I said to my self Self? that sounds good, go do it! and I did... without a current backup and without enough space on /var, so I am starting over again (it's only a day or two to get back, i hope!). If I still have trouble, I'll make the complete picture and post it for comment. One thought for the future... does z/OS need dynamicxcf or anything like that? I believe that z/OS people set that up on their side. 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
also check that the MTU sizes match. David -Original Message- From: Linux on 390 Port on behalf of Rich Smrcina Sent: Fri 6/29/2007 11:51 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Hipersockets Conundrum So are your OSA devices and Hipersocket devices all on the same network? In other words do they all have a 172.20.1.x address with a netmask of 255.255.255.0? Kim Goldenberg wrote: We are starting our Linux POC and all has been going well. Until I got to the Hipersockets, that is. We are trying to talk to two z/OS LPARs, one development and one production. in our IFL LPAR, z/VM 5.2 RSU 0701 and SLES9x SP3. POC is a Java app that gets messages via MQ Series and reformats into XML and queries a site on the web via https. The initial test worked well with MQ talking over the OSAs out to our internal network and back in the other OSA (why don't we share them? Don't ask!). Now we want to modify that use a Hipersocket interface. Initial: z/OS -- OSA -- network -- OSA -- Linux (on vswitch) Wanted: z/OS -- Hipersockets -- Linux Hipersockets were defined on CHPID 50 (addresses 5000-500F) . xxx.yyy.zzz are the same for all the following addresses: Both z/OS systems are v1.6. and have addresses xxx,yyy,zzz,101 and xxx,yyy,zzz,102 (development and production, respectively) using addresses 500-5002. The z/OS systems can ping each other. I set up the z/VM guest to use 5004-5006 through dedicate statements in the SYSTEM CONFIG and used yast to add configure the interface as xxx.yyy.zzz,103. All indications are that the interface is fine: q osa OSA 2130 ATTACHED TO DTCVSW2 2130 DEVTYPE OSA CHPID F3 OSD OSA 2131 ATTACHED TO DTCVSW2 2131 DEVTYPE OSA CHPID F3 OSD OSA 2132 ATTACHED TO DTCVSW2 2132 DEVTYPE OSA CHPID F3 OSD OSA 5004 ATTACHED TO LINUX001 5000 DEVTYPE HIPER CHPID 50 IQD OSA 5005 ATTACHED TO LINUX001 5001 DEVTYPE HIPER CHPID 50 IQD OSA 5006 ATTACHED TO LINUX001 5002 DEVTYPE HIPER CHPID 50 IQD lnxa0001:/home/otsgold # ifconfig hsi0 hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:172.20.1.103 Bcast:172.20.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:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:1048 (1.0 Kb) SLES9x info: lnxa0001:/home/otsgold # uname -a Linux lnxa0001 2.6.5-7.244-s390x #1 SMP Mon Dec 12 18:32:25 UTC 2005 s390x s390x s390x GNU/Linux Any ideas as to why the SLES9x will not talk to z/OS? Any thing I should look for, ask or z/OS network people, etc.? 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 -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008 -- 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 -- 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
On Fri, Jun 29, 2007 at 3:43 PM, in message [EMAIL PROTECTED], Kim Goldenberg [EMAIL PROTECTED] wrote: We are starting our Linux POC and all has been going well. Until I got to the Hipersockets, that is. -snip- z/OS -- OSA -- network -- OSA -- Linux (on vswitch) Wanted: z/OS -- Hipersockets -- Linux -snip- Any ideas as to why the SLES9x will not talk to z/OS? Any thing I should look for, ask or z/OS network people, etc.? Can the Linux guest ping either of the z/OS systems? Does the Linux guest still have the OSA connection defined as a NIC? If so, what IP address and subnet mask is assigned to it? If it's a 172.20.2.x/24 address, that is most likely your problem (although I would expect that to still work,just not by using the HiperSocket). SLES9x info: lnxa0001:/home/otsgold # uname -a Linux lnxa0001 2.6.5-7.244-s390x #1 SMP Mon Dec 12 18:32:25 UTC 2005 s390x s390x s390x GNU/Linux It wouldn't hurt to make sure you have on all the maintenance for SLES9. Your kernel is not the most current. A better picture of _all_ the network interfaces, with IP addresses, network masks, routing, etc. for the z/OS systems and the Linux guest would be useful. 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
What does your routing table look like? Kim Goldenberg wrote: We are starting our Linux POC and all has been going well. Until I got to the Hipersockets, that is. We are trying to talk to two z/OS LPARs, one development and one production. in our IFL LPAR, z/VM 5.2 RSU 0701 and SLES9x SP3. POC is a Java app that gets messages via MQ Series and reformats into XML and queries a site on the web via https. The initial test worked well with MQ talking over the OSAs out to our internal network and back in the other OSA (why don't we share them? Don't ask!). Now we want to modify that use a Hipersocket interface. Initial: z/OS -- OSA -- network -- OSA -- Linux (on vswitch) Wanted: z/OS -- Hipersockets -- Linux Hipersockets were defined on CHPID 50 (addresses 5000-500F) . xxx.yyy.zzz are the same for all the following addresses: Both z/OS systems are v1.6. and have addresses xxx,yyy,zzz,101 and xxx,yyy,zzz,102 (development and production, respectively) using addresses 500-5002. The z/OS systems can ping each other. I set up the z/VM guest to use 5004-5006 through dedicate statements in the SYSTEM CONFIG and used yast to add configure the interface as xxx.yyy.zzz,103. All indications are that the interface is fine: q osa OSA 2130 ATTACHED TO DTCVSW2 2130 DEVTYPE OSA CHPID F3 OSD OSA 2131 ATTACHED TO DTCVSW2 2131 DEVTYPE OSA CHPID F3 OSD OSA 2132 ATTACHED TO DTCVSW2 2132 DEVTYPE OSA CHPID F3 OSD OSA 5004 ATTACHED TO LINUX001 5000 DEVTYPE HIPER CHPID 50 IQD OSA 5005 ATTACHED TO LINUX001 5001 DEVTYPE HIPER CHPID 50 IQD OSA 5006 ATTACHED TO LINUX001 5002 DEVTYPE HIPER CHPID 50 IQD lnxa0001:/home/otsgold # ifconfig hsi0 hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:172.20.1.103 Bcast:172.20.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:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:1048 (1.0 Kb) SLES9x info: lnxa0001:/home/otsgold # uname -a Linux lnxa0001 2.6.5-7.244-s390x #1 SMP Mon Dec 12 18:32:25 UTC 2005 s390x s390x s390x GNU/Linux Any ideas as to why the SLES9x will not talk to z/OS? Any thing I should look for, ask or z/OS network people, etc.? 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 -- 'in media stat virtus' Virtue's in the middle -- 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
Hipersockets Conundrum
We are starting our Linux POC and all has been going well. Until I got to the Hipersockets, that is. We are trying to talk to two z/OS LPARs, one development and one production. in our IFL LPAR, z/VM 5.2 RSU 0701 and SLES9x SP3. POC is a Java app that gets messages via MQ Series and reformats into XML and queries a site on the web via https. The initial test worked well with MQ talking over the OSAs out to our internal network and back in the other OSA (why don't we share them? Don't ask!). Now we want to modify that use a Hipersocket interface. Initial: z/OS -- OSA -- network -- OSA -- Linux (on vswitch) Wanted: z/OS -- Hipersockets -- Linux Hipersockets were defined on CHPID 50 (addresses 5000-500F) . xxx.yyy.zzz are the same for all the following addresses: Both z/OS systems are v1.6. and have addresses xxx,yyy,zzz,101 and xxx,yyy,zzz,102 (development and production, respectively) using addresses 500-5002. The z/OS systems can ping each other. I set up the z/VM guest to use 5004-5006 through dedicate statements in the SYSTEM CONFIG and used yast to add configure the interface as xxx.yyy.zzz,103. All indications are that the interface is fine: q osa OSA 2130 ATTACHED TO DTCVSW2 2130 DEVTYPE OSA CHPID F3 OSD OSA 2131 ATTACHED TO DTCVSW2 2131 DEVTYPE OSA CHPID F3 OSD OSA 2132 ATTACHED TO DTCVSW2 2132 DEVTYPE OSA CHPID F3 OSD OSA 5004 ATTACHED TO LINUX001 5000 DEVTYPE HIPER CHPID 50 IQD OSA 5005 ATTACHED TO LINUX001 5001 DEVTYPE HIPER CHPID 50 IQD OSA 5006 ATTACHED TO LINUX001 5002 DEVTYPE HIPER CHPID 50 IQD lnxa0001:/home/otsgold # ifconfig hsi0 hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:172.20.1.103 Bcast:172.20.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:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:1048 (1.0 Kb) SLES9x info: lnxa0001:/home/otsgold # uname -a Linux lnxa0001 2.6.5-7.244-s390x #1 SMP Mon Dec 12 18:32:25 UTC 2005 s390x s390x s390x GNU/Linux Any ideas as to why the SLES9x will not talk to z/OS? Any thing I should look for, ask or z/OS network people, etc.? 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
So are your OSA devices and Hipersocket devices all on the same network? In other words do they all have a 172.20.1.x address with a netmask of 255.255.255.0? Kim Goldenberg wrote: We are starting our Linux POC and all has been going well. Until I got to the Hipersockets, that is. We are trying to talk to two z/OS LPARs, one development and one production. in our IFL LPAR, z/VM 5.2 RSU 0701 and SLES9x SP3. POC is a Java app that gets messages via MQ Series and reformats into XML and queries a site on the web via https. The initial test worked well with MQ talking over the OSAs out to our internal network and back in the other OSA (why don't we share them? Don't ask!). Now we want to modify that use a Hipersocket interface. Initial: z/OS -- OSA -- network -- OSA -- Linux (on vswitch) Wanted: z/OS -- Hipersockets -- Linux Hipersockets were defined on CHPID 50 (addresses 5000-500F) . xxx.yyy.zzz are the same for all the following addresses: Both z/OS systems are v1.6. and have addresses xxx,yyy,zzz,101 and xxx,yyy,zzz,102 (development and production, respectively) using addresses 500-5002. The z/OS systems can ping each other. I set up the z/VM guest to use 5004-5006 through dedicate statements in the SYSTEM CONFIG and used yast to add configure the interface as xxx.yyy.zzz,103. All indications are that the interface is fine: q osa OSA 2130 ATTACHED TO DTCVSW2 2130 DEVTYPE OSA CHPID F3 OSD OSA 2131 ATTACHED TO DTCVSW2 2131 DEVTYPE OSA CHPID F3 OSD OSA 2132 ATTACHED TO DTCVSW2 2132 DEVTYPE OSA CHPID F3 OSD OSA 5004 ATTACHED TO LINUX001 5000 DEVTYPE HIPER CHPID 50 IQD OSA 5005 ATTACHED TO LINUX001 5001 DEVTYPE HIPER CHPID 50 IQD OSA 5006 ATTACHED TO LINUX001 5002 DEVTYPE HIPER CHPID 50 IQD lnxa0001:/home/otsgold # ifconfig hsi0 hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:172.20.1.103 Bcast:172.20.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:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:1048 (1.0 Kb) SLES9x info: lnxa0001:/home/otsgold # uname -a Linux lnxa0001 2.6.5-7.244-s390x #1 SMP Mon Dec 12 18:32:25 UTC 2005 s390x s390x s390x GNU/Linux Any ideas as to why the SLES9x will not talk to z/OS? Any thing I should look for, ask or z/OS network people, etc.? 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 -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008 -- 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
