To date, thanks all for responding. Below is our production TCPIP PROFILE
<profile>
; Device Statements
; 10.140.1.22
DEVICE LCS0 OSD E000 PORTNAME CHPID00 PORTNUMBER 0 PRIROUTE
LINK ETH0 QDIOETHERNET LCS0
; 10.1.140.24
DEVICE LCS2 OSD E200 PORTNAME CHPID02 PORTNUMBER 0
LINK ETH2 QDIOETHERNET LCS2
; hiper socket definitions
DEVICE HIPERDRV HIPERS F000 PORTNAME HIPERDF0
LINK HIPERLF0 QDIOIP HIPERDRV
DEVICE WARPDRV HIPERS F100 PORTNAME HIPERDF1
LINK HIPERLF1 QDIOIP WARPDRV
; the local host's internet addresses
HOME
10.140.1.22 ETH0
10.140.1.24 ETH2
192.168.140.60 HIPERLF0
192.168.141.60 HIPERLF1
; Routing information (if you are not using the ROUTED server)
GATEWAY
; NETWORK FIRST HOP DRIVER PACKET SIZE SUBN MASK SUBN
VALUE
192.168.140 = HIPERLF0 8192 0
192.168.141.63 = HIPERLF1 8192 HOST
10.140.1.24 = ETH2 1500
HOST
10 = ETH0 1500
0.255.255.0 0.140.1.0
; Default for everything else
DEFAULTNET 10.140.1.254 ETH0 1500 0
TRANSLATE
; The following translate statements are used for remote Hyperchannel
; hosts.
; 193.6.0.1 HCH FF0000001040 HCH1
; 193.6.0.3 HCH FF0000001120 HCH1
; 192.1.1.6 X25ICA 95501234502 X25LA
; Start all the interface
START LCS0
START LCS2
START HIPERDRV
START WARPDRV
</profile>
What I had originally sent in the original post was the OBEYFILE file, so
of course you all wouldn't know that I had the above.
Based on what Alan said, I need to change (in the GATEWAY section)
192.168.141.63 to just 192.168.141 correct?
Can I comment out the TRANSLATE param or will TCPIP fuss because it can't
find it?
Disregarding the WARPDRV/HIPERLF1/192.168.141.x entries, definitions etc,
everything else works, sort of. 8-)
We're using two different OSA cards one for 10.140.1.22 and the other for
10.140.1.24.
We don't get much traffic on .24 We have some applications, some telnet
sessions, etc. coded to use .24 but they always seem to
go to .22. Do I have something coded incorrectly that would cause this?
Thanks again for everyone's help. Every time I think I've got all this
network stuff figured out, I usually dig
myself a deeper hole. Very frustrating.
Steve G.
There's no place like 127.0.0.1
Alan Altmark <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[email protected]>
11/28/2005 08:02 PM
Please respond to Linux on 390 Port
To: [email protected]
cc:
Subject: Re: Linux network problem/question
On Monday, 11/28/2005 at 06:41 EST, "Post, Mark K" <[EMAIL PROTECTED]>
wrote:
> Well, then maybe I should point out that the two IP addresses are indeed
> different, in the third octet:
> 192.168.140.60 HIPERLF0
> 192.168.141.60 HIPERLF1
>
> If the intent was to actually assign the same IP to both interfaces,
> then they either typoed it, or typoed it in sending it to the mailing
> list.
Well, duh. :-) My eye Dr. appointment is Thursday and none too soon!
(Chuckie is off the hook on this one, I'm sorry to say.)
STEVE: You need a route to 141.63 AND you have to have PRIROUTER on your
ETH0/ETH2 interfaces for all this to work.
1) That second line should read:
192.168.141 = HIPERLF1 8192 0
instead of
192.168.141.60 = HIPERLF1 8192 HOST
to fix the existing problem (no route) and (b) not have to add more
entries later when you add more hosts to the Hipersocket. Rule #16: Never
put your own IP address in a Gateway entry.
2) Double-check that the Linux default gateway is 141.60, not 140.60.
3) As an aside, that still leaves:
> 10.140.1.24 = ETH2 1500 HOST
which cannot be correct since 10.140.1.24 is the home address on ETH2
(Rule 16 again). I think it should be
10 = ETH2 1500 0.255.255.0 0.140.1.0
but beware since you now have two routes to the same subnet (ETH0 and
ETH2) and that whole AssortedParms EqualCostMultiPath thing comes into
play.
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
----------------------------------------------------------------------
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
