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

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,

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;

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:

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

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

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.

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

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

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:

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

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

Re: Hipersockets Conundrum

: 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

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)

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

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 --

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.

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

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