Mark, That would be your problem then. You need to have your VM person verify that TCP/IP is ready to have the CTCs coupled to it, and at what addresses. Then, from the VM console: #cp couple 600 tcpip xxxx #cp couple 601 tcpip yyyy
Mark Post -----Original Message----- From: Dorney, Mark [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 9:37 AM To: [EMAIL PROTECTED] Subject: Re: CTC's Turbolinux 6.5 >From the #cp q v ctc command: CP Q V CTC CTCA 0600 ON DEV FD00 SUBCHANNEL = 000C CTCA 0601 ON DEV FD01 SUBCHANNEL = 000D Not sure what the DEV is at this point but it sure doesn't look like they are coupled to TCPIP... Mark Dorney -----Original Message----- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 17, 2002 4:13 PM To: [EMAIL PROTECTED] Subject: Re: CTC's Turbolinux 6.5 Mark, >From the VM console, issue this command: #cp q v ctc You should see something like this: #cp q v ctc 00: CTCA 0600 3088 COUPLED TO TCPIP 0F01 SUBCHANNEL = 000B 00: CTCA 0601 3088 COUPLED TO TCPIP 0F00 SUBCHANNEL = 000C If you don't, that is your problem. If you do, then after you insmod the ctc module, do this: dmesg | tail You should see some messages about the ctc driver: CTC driver Version: 1.29 initialized channel: 2 Parallel channel found - 0 ESCON channel found ctc0: read dev: 0f00 irq: 000b - write dev: 0f01 irq: 000c Then, do this: ifconfig -a You should see something along these lines: ctc0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-FF-00-00-00-00-00-00-00-00 POINTOPOINT NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Report back what really happens. Mark Post -----Original Message----- From: Dorney, Mark [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 17, 2002 4:59 PM To: [EMAIL PROTECTED] Subject: Re: CTC's Turbolinux 6.5 It's through VM TCP/IP, I tried using ESCON earlier in the day but didn't have any better luck there. I saw that when he finds the ESCON he tries to use escon0 and it looks like he gets an error there. Possibly the channels are configured wrong? The guy who did that part is gone for the day, more tomorrow I guess. Thanks -----Original Message----- From: Steve Shomaker [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 17, 2002 3:56 PM To: [EMAIL PROTECTED] Subject: Re: CTC's Turbolinux 6.5 Mark, Are you using vctc with VM TCP/IP or do you have a network connection directly attached to your Linux image? If you are using vctc, you should have 2 Parallel channels found not 2 Escon channels found. If you are using directly attached, it looks like you chose CTC instead of Escon. At 03:27 PM 4/17/02 -0500, you wrote: >Sorry, might be worthy to note that we running under VM as a guest > > > -----Original Message----- > > From: Dorney, Mark > > Sent: Wednesday, April 17, 2002 3:26 PM > > To: [EMAIL PROTECTED] > > Subject: CTC's Turbolinux 6.5 > > > > First off, serious newbie alert, mainframer thrown into this world for a > > POC. > > > > I'm doing an install from tape, I get to the part where I specify my CTC > > information and I start getting errors (logs are at the end). I believe > > that the hardware is ok since I went through the archives and although I > > couldn't find my specific situation I ran through some other suggestions > > of shutting down the network, rmmod ctc, insmod ctc and restarting the > > network. I tried to manually configure the network by doing an "ifconfig > > ctc0......" and at one point in the day I was able to ping successfully. > > All efforts to duplicate that success have failed. > > > > Here's what I'm getting: > > -------------------------------------------------------------------------- > > > > Please review your selection: > > > > -------------------------------------------------------------------------- > > > > > > > > Hostname : mylinux.state.wi.us > > > > > > > > Gateway IP : 198.150.235.17 > > > > Gateway Device : ctc0 > > > > > > > > Nameserver IP : 198.150.235.21 > > > > Searchlist : state.wi.us > > > > CTC options : ctc=0x600 > > > > > > > > -------------------------------------------------------------------------- > > > > Do you want to use these settings? (y/n)y > > > > y > > > > CTC driver Version: 1.29 initialized > > > > channel: 0 Parallel channel found - 2 ESCON channel found > > > > escon0: read dev: 0600 irq: 000c - write dev: 0601 irq: 000d > > > > SIOCSIFADDR: No such device > > > > ctc0: unknown interface: No such device > > > > SIOCSIFDSTADDR: No such device > > > > ctc0: unknown interface: No such device > > > > SIOCSIFMTU: No such device > > > > SIOCADDRT: No such device > > > > ctc0: error fetching interface information: Device not found > > > > search state.wi.us > > > > Starting portmapper: portmap > > > > Mounting remote filesystems. > > > > Starting system logger: syslogd > > > > Stop network, rmmod ctc, etc reults in ***************** > > > > bash-2.04# rmmod ctc > > rmmod ctc > > bash-2.04# cd /lib/modules/2.2.19/misc > > cd /lib/modules/2.2.19/misc > > bash-2.04# insmod ctc > > insmod ctc > > Using /lib/modules/2.2.19/misc/ctc.o > > bash-2.04# /etc/rc.d/init.d/network start > > /etc/rc.d/init.d/network start > > SIOCSIFADDR: No such device > > ctc0: unknown interface: No such device > > SIOCSIFDSTADDR: No such device > > ctc0: unknown interface: No such device > > SIOCSIFMTU: No such device > > SIOCADDRT: No such device > > ctc0: error fetching interface information: Device not found > > search state.wi.us > > bash-2.04# > > > > Thanks for any help anyone can provide > > > > Mark Dorney > > Steve Shomaker -- Sytek Services, Inc 13896 Skyline Blvd. Woodside, CA 94062 Phn: (650)529-0268 Fax: (650)529-0347
