Yes, you should be able to ping Linux from the peer at the other end of the
CTC connection.
If you can ping from the peer (os/390) to your linux system, and you can
ping from the world to os/390, then you have a routing problem.
I set my CTC connections to OS/390 up like this:
world --> 10.5.7.102 (OSA) , OS/390, (CTC) 192.168.23.105 <==> 10.5.23.105
(CTC) ,Linux
Where the linux system is on an entirely different subnet than OS/390, and
OS/390 acts as a router into that subnet.
Note that I have each end of the CTC in different subnets also, I dont know
if this is still required, but it used to be.
The netmask for each end of the CTC is 255.255.255.255, it's a point to
point connection.
Jay Brenneman
Kyle Stewart
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
et> cc:
Sent by: Linux on Subject: Re: URGENT - RH 7.1 (64-bit)
LPAR Install CTC Problems
390 Port
<[EMAIL PROTECTED]
IST.EDU>
02/25/2003 03:13
PM
Please respond to
Linux on 390 Port
Shouldn't I be able to ping the initrd ipl'ed version of Linux via the CTC
from the partner? I have tried configuring this with an OSA card in
passthru mode. Everything (as far as I know) looks good, but we can't
ping,
telnet nor ssh to the Linux image. There must be something more basic that
I am missing here.
Regards,
Kyle Stewart
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Mark Post
Sent: Saturday, February 22, 2003 9:34 AM
To: [EMAIL PROTECTED]
Subject: Re: URGENT - RH 7.1 (64-bit) LPAR Install CTC Problems
The CTC driver was changed at some point to only use the ctc# name. I
don't
know that this was ever documented anywhere, but it certainly made a lot of
existing literature misleading.
You need to make sure that MTU sizes match, yes. That is a typical cause
of
some very odd behavior. Usually not to the extent that you can't do a
ping,
though.
When you talk to your IP networking folks, have them think of the OS/390
system as being a router in this instance, and your Linux/390 system as a
host, since those are the networking roles they're filling.
Mark Post
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Kyle Stewart
Sent: Saturday, February 22, 2003 1:47 AM
To: [EMAIL PROTECTED]
Subject: Re: URGENT - RH 7.1 (64-bit) LPAR Install CTC Problems
Importance: High
Thanks, Vic. That worked great. I can't use "escon0" for the ifconfig. I
have to use ctc0!?!? I still can't get IP up across the link though
OS/390's IP show's the link as ready. The subnet mask from my side is
255.255.255.255, but it is 255.0.0.0 from OS/390. Does my IP guy need to
set me up with a subnet in the gateway instead of as a host? Would MTU
size
differences cause a problem? Thanks for any help.
Regards,
Kyle Stewart
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Vic
Cross
Sent: Friday, February 21, 2003 3:34 PM
To: [EMAIL PROTECTED]
Subject: Re: URGENT - RH 7.1 (64-bit) LPAR Install CTC Problems
Kyle, try "ifconfig -a", or "ifconfig ctc0", this should show your ctc0
device. "ifconfig" (without parameters) only shows active (up) devices.
If ctc0 appears, just issue
"ifconfig ctc0 <ip-address> pointopoint <peer-ip-addr> up"
and things should work.
Cheers,
Vic Cross
On Fri, 21 Feb 2003, Kyle & Lisa Stewart wrote:
> I am installing RH 7.1 on an LPAR. This is our first mainframe Linux
> install. I am trying to use CTC connection to an OS/390 2.10 IP stack to
> get to the world. CTCs & devices look good from OS/390 & its IP.
However,
> on Linux ifconfig only shows the loopback device. I do a cat
/proc/chandev
> and I can see the two devices as in use and reg. Any ideas about this?
>
> Thanks,
> Kyle Stewart
> [EMAIL PROTECTED]
>
