Tom, You can have Guest LANs with z/VM 4.2. They just won't have broadcast capability. You _really_ want to move to Guest LANs, even without that. Really.
Mark Post Really. -----Original Message----- From: Tom Duerbusch [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 1:15 PM To: [EMAIL PROTECTED] Subject: Re: Suse 8 TCP/IP timeouts during boot You are right, in both cases. Stopping the IP device and starting it again worked, at least the first time. I do plan on moving to IUCV. But during the initial testing, I'm keeping the things I have control over, the same as I had in Suse 7. I don't have guest lans support (z/VM 4.2), but I'm converting in 4th quarter to z/VM 4.4 (the last VM release supported on the MP3000). Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 05/28 12:03 PM >>> Tom, I have this exact same problem on one of my SuSE systems that I upgraded to a 2.4.19 kernel. I switched to IUCV instead. If you don't want to go with Guest LANS (and you _really_ should), IUCV is the better way to go than CTC. They're both point to point (which stinks), and IUCV seems to be more reliable when one end or the other drops and comes back up. In the meantime, if you stop and restart the connection on the VM TCP/IP side, it should get you going again. After a few attempts, perhaps. If you're lucky today. Mark Post -----Original Message----- From: Tom Duerbusch [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 12:54 PM To: [EMAIL PROTECTED] Subject: Suse 8 TCP/IP timeouts during boot I'm not sure where to look to debug this problem. I've been testing Suse 8. We have been on Suse 7 for about a year. When I install Suse 8, it connects to VM's TCP/IP machine and runs just fine. This is z/VM 4.2 btw. However, when I cycle Linux, it doesn't connect back to IP. But, if I cycle TCPIP when Linux is up, it connects ok. If I cycle TCPIP when Linux is down, when I boot Linux, it connects ok (first time only) I'm using VCTCA connections. As I've hinted at, I have not had this type of problem with Suse 7. Error messages follows: >From Linux during boot: Setting up network interfaces: lo ..done ctc0 CTC driver Version: 1.55.10.2 with CHANDEV support initialized ctc0: read: ch 09d6 (irq 0009), write: ch 09d7 (irq 000a) proto: 0 IP/Peer: 192.168.99.211 / 205.235.227.74 ..done Starting syslog services..done Starting hotplugging services [ net ]..done Starting hardware scan on boot..done Starting RPC portmap daemon..done Starting SSH daemon..done Mount SMB File System..unused May 28 11:49:08 linux11 kernel: klogd 1.4.1, log source = /proc/kmsg started. May 28 11:49:08 linux11 kernel: Inspecting /boot/System.map-2.4.19-3suse-SMP May 28 11:49:08 linux11 kernel: CTC driver Version: 1.55.10.2 with CHANDEV suppo rt initialized May 28 11:49:08 linux11 kernel: ctc0: read: ch 09d6 (irq 0009), write: ch 09d7 ( irq 000a) proto: 0 May 28 11:49:08 linux11 kernel: ctc0: Timeout during TX init handshake May 28 11:49:08 linux11 kernel: ctc0: TX channel restart May 28 11:49:08 linux11 kernel: ctc0: Timeout during TX init handshake May 28 11:49:08 linux11 kernel: ctc0: TX channel restart May 28 11:49:08 linux11 kernel: ctc0: Timeout during TX init handshake May 28 11:49:08 linux11 kernel: ctc0: TX channel restart May 28 11:49:08 linux11 kernel: ctc0: Timeout during TX init handshake May 28 11:49:08 linux11 kernel: ctc0: TX channel restart May 28 11:49:08 linux11 kernel: ctc0: Timeout during TX init handshake May 28 11:49:08 linux11 kernel: ctc0: TX channel restart May 28 11:49:08 linux11 kernel: ctc0: Timeout during TX init handshake May 28 11:49:08 linux11 kernel: ctc0: TX channel restart >From the console log of TCPIP: 11:47:47 GRAF L01CB LOGON AS LINUX11 USERS = 48 TUBPRD TII0226I THDBUSCH LU PN206261 LDEV 01CB LOGGED ON TO LINUX11 (PF2) TCPIP CTCA 09D7 COUPLED BY LINUX11 09D6 TCPIP CTCA 09D6 COUPLED BY LINUX11 09D7 TCPIP 11:47:58 DTCCTC091E CTCA DEVICE LINUX11: RECEIVED DEVICEEND INTERRUPT O TCPIP PROBABLE CTCA RESTART 11:48:25 TAPE 05A1 ATTACHED TO DYNVM 05A1 BY DYNVM DOSESA2 TAPE 05A1 ATTACHED 11:48:26 TAPE 05A1 GIVEN TO DOSESA2 05A1 BY DYNVM DYNVM 11:48:27 CADT007I (IUCV:DOSESA2,BG) ****** LABEL SYS015 SYS015=5A1 DYNVM *929D002-DT-RESPMT* TUBPRD TII0261I DOS4 LU LS208271 VTAM SESSION TST4PROD(2) STARTING - LOGMODE=D TCPIP 11:48:31 DTCCTC091E CTCA DEVICE LINUX11: RECEIVED DEVICEEND INTERRUPT O TCPIP PROBABLE CTCA RESTART TCPIP 11:48:36 DTCCTC091E CTCA DEVICE LINUX11: RECEIVED DEVICEEND INTERRUPT O TCPIP 11:48:41 DTCCTC091E CTCA DEVICE LINUX11: RECEIVED DEVICEEND INTERRUPT O TCPIP PROBABLE CTCA RESTART DYNVM 11:48:41 CADT031I (IUCV:DOSESA2,BG) *CLOSED* SYS015 SYS015=5A1 3036 DYNVM BLK=12 DYNVM 11:48:41 CADT032I (IUCV:TSTESA4,BG) ASSIGNED BACKUP SYS000=5A8 3057 DOSESA2 TAPE 05A1 GIVEN TO DYNVM 05A1 11:48:42 TAPE 05A1 GIVEN TO DYNVM 05A1 FROM DOSESA2 BY DYNVM 11:48:45 TAPE 05A1 DETACHED DYNVM 05A1 BY DYNVM, TAPE VOLUME(S) NOT UNL TCPIP 11:48:46 DTCCTC091E CTCA DEVICE LINUX11: RECEIVED DEVICEEND INTERRUPT O TCPIP PROBABLE CTCA RESTART TCPIP 11:48:51 DTCCTC091E CTCA DEVICE LINUX11: RECEIVED DEVICEEND INTERRUPT O Some netstat commands: netstat gate VM TCP/IP Netstat Level 420 Known gateways: NetAddress FirstHop Flgs PktSz Subnet Mask Subnet Value Link ---------- -------- ---- ----- ----------- ------------ ------ Default 205.235.227.41 UGS 1500 <none> ETH1 192.168.33.0 <direct> US 1492 <none> MP02 192.168.99.0 <direct> US 1500 <none> LNEWESA4 192.168.99.5 <direct> UHS 1500 HOST LSTLESA2 192.168.99.10 <direct> UHS 1500 HOST LY2KESA2 192.168.99.24 <direct> UHS 1500 HOST LNEWESA4 192.168.99.206 <direct> UHS 1500 HOST LLINUX06 192.168.99.207 <direct> HS 1500 HOST LLINUX07 192.168.99.208 <direct> HS 1500 HOST LLINUX08 192.168.99.209 <direct> HS 1500 HOST LLINUX09 192.168.99.210 <direct> UHS 1500 HOST LLINUX10 192.168.99.211 <direct> UHS 1500 HOST LLINUX11 192.168.99.212 <direct> HS 1500 HOST LLINUX12 192.168.99.213 <direct> HS 1500 HOST LLINUX13 192.168.99.214 <direct> HS 1500 HOST LLINUX14 192.168.99.241 <direct> UHS 1500 HOST LLINUX05 >From "netstat dev" Device LINUX11 Type: CTC Status: Ready Queue size: 0 Address: 09D6 Link LLINUX11 Type: CTC Net number: 0 Multicast Capability: Yes Group Members ----- ------- 224.0.0.1 1 Not having reliable connections after booting is really getting to be a pain. Tom Duerbusch THD Consulting
