Tom, As you've discovered, there are some oddities about the way ESCON channel definitions work with Linux 2.4. One of those is that you should pass a value of "escon0" to the chandev layer, but the actual device name that gets created is ctc0. I view this as a bug, but haven't pursued it, yet.
Make sure you have your read and write channels cross-connected. This can be done either in the MVS TCP/IP parameters, or via specifying your Linux/390 devices in the opposite order, i.e., if 0C12 connects to 0C30, and 0C13 connects to 0C31, then by specifying ctc0,0x0C31,0x0C30, you will have things correct. Normally if this is done wrong, the error messages that come out are fairly specific, but this looks like a good possibility. One area that you looked at could very well be a problem, but not necessarily of a nature to produce the errors you're seeing. If your MVS system is at 128.101.100.3, and your Linux/390 system is at 128.101.100.7, the CLAW won't know to forward traffic to .7 via .3 unless OROUTED is broadcasting that route. Even then, it's probably not good practice, and the Linux/390 system really should be in a separate subnet. As far as the kernel you are using, just about any of them should work with your current hardware. Mark Post -----Original Message----- From: Thomas Kunz [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 9:56 AM To: [EMAIL PROTECTED] Subject: ESCON CTC between Linux LPAR and MVS LPAR Good Morning - I am trying to install redhat 7.2 linux on a s390 lpar. I downloaded the tapeinrd.img and the tapekrnl.img from ftp.redhat.com in /pub/redhat/linux/7.2/en/s390/images and created a parmfile. The system Boots fine and I get the prompt for a FQDN, etc. and a device type which if I select escon0 and fill in the rest of the IP stuff about virtual IP address and partner IP address I then get a response back that says: No such device escon0 SIOCSIFADDR No such device escon0 unknown interface. I have tried many different combinations when it asks to supply the parameters to pass - i.e. escon,0xc30,0xc3f,0,3 escon0,0xc30,0xc31 escon0,0xc30,0xc31,0,3 We do have escon ctc's defined. On the MVS 2.9 side it looks like this after I start TCPIP : UNIT TYPE STATUS 0C12 SCTC A-BSY 0C13 SCTC A-BSY In the above example if I use ctc0 instead of escon0 it accepts it but I never get a connection - netstat dev on mvs tcpip just shows connecting and not active and I get error messages: IEF196I IOS071I 0C13,34,NETB, MISSING DEVICE END IOS071I 0C13,34,NETB, MISSING DEVICE END 979 EZZ4310I ERROR: CODE=8010002B REPORTED ON DEVICE CTC0DEV. DIAGNOSTIC CODE: 04 EZZ4309I ATTEMPTING TO RECOVER DEVICE CTC0DEV which talk about XID's and VTAM or a channel error. My question(s) - do I have the right tape kernel images downloaded for escon support? Does anyone have a sample of what the parm file should look like regarding the ctc/escon parms? On the MVS side we run OROUTED - what should the bsdrouting parms look like? Do the IP addresses for the linux lpar and the mvs ctc have to be in different networks? I was using 128.101.100.7 for the linux IP address and 128.101.100.6 for the MVS CTC IP address. The MVS side has a CLAW interface to the network and is IP address 128.101.100.3. Is that a conflict? Anyone have a good resource of where to go to understand how this should be setup? Thanks and have a great day! :-) Tom Kunz OIT/PTS Network & AIX Systems Support University of Minnesota 1300 S. 2nd St. Mpls., MN. 55454-1083 Suite 660 Phone: 612-624-8086 Fax: 612-626-1332 Email: [EMAIL PROTECTED] ************************************************************************** This e-mail and its attachments have been scanned for viruses. NDIS/ADCS University of Minnesota **************************************************************************
