No go on mtu of 32760. ---SB
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Tuesday, March 23, 2004 10:11 PM To: [EMAIL PROTECTED] Subject: Re: CTC between linux & zOS. Well, then try changing the Linux parameters to 32760. You could just try doing it via an ifconfig command first, to see if that makes any difference or not. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Steve Bui Sent: Tuesday, March 23, 2004 11:48 PM To: [EMAIL PROTECTED] Subject: Re: CTC between linux & zOS. Both places (TCPIP profile on zOS and ifcfg-ctc0 on linux) already have mtu of 1500 hardcoded. ---SB > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Post, Mark K > Sent: Tuesday, March 23, 2004 9:23 PM > To: [EMAIL PROTECTED] > Subject: Re: CTC between linux & zOS. > > > I would expect that to be the only two places needed. Are > you asking because one (or both) of them isn't reflecting the change? > > Mark Post > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > Behalf Of [EMAIL PROTECTED] > Sent: Tuesday, March 23, 2004 9:21 PM > To: [EMAIL PROTECTED] > Subject: Re: CTC between linux & zOS. > > > I set both mtu to 1500 in zOS TCPIP and in ifcfg-ctc0. > Where else do you set it? > ---SB > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of > > Post, Mark K > > Sent: Tuesday, March 23, 2004 5:49 PM > > To: [EMAIL PROTECTED] > > Subject: Re: CTC between linux & zOS. > > > > > > Steve, > > > > This caught my eye: > > ActMtu: 32760 > > > > The ifconfig output from your first note showed this: > > UP POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > > > The two values need to match. > > > > > > Mark Post > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of > > Steve Bui > > Sent: Tuesday, March 23, 2004 10:22 AM > > To: [EMAIL PROTECTED] > > Subject: Re: CTC between linux & zOS. > > > > > > I tried both 0 or 1 with no success. > > Netstat dev on zOS shows: > > DevName: CTC3X7 DevType: CTC DevNum: 0B72 > > DevStatus: Ready > > LnkName: CTC37 LnkType: CTC LnkStatus: Ready > > > > NetNum: 1 QueSize: 0 > > BytesIn: 0 BytesOut: 0 > > ActMtu: 32760 > > BSD Routing Parameters: > > MTU Size: 00000 Metric: 00 > > DestAddr: 10.0.3.2 SubnetMask: 255.255.255.0 > > Multicast Specific: > > Multicast Capability: Yes > > Group RefCnt > > ----- ------ > > 224.0.0.1 0000000001 > > ------------------------- > > ---SB > > > > On Monday, 03/22/2004 at 10:18 EST, "Post, Mark K" > <[EMAIL PROTECTED]> > > wrote: > > > Correct me if I'm wrong (I haven't played with MVS TCPIP > definitions > > much), > > > but in this statement: > > > LINK CTC37 CTC 1 CTC3X7 > > > doesn't the "1" say to swap the read channel with the write > > channel? > > > If > > so, > > > I would think that is your problem, since the entry in > chandev.conf > > > ctc0,0x0d33,0x0d32,0,3 says to do exactly the same thing. > The fact > > > that the ifconfig output > > you > > > show lists 5 errors, all of them "carrier" errors would > seem to bear > > this > > > out. > > Also use NETSTAT DEV (onetstat?) on the z/OS side to find > out what the > > status of the CTC. Alan Altmark Sr. Software Engineer IBM z/VM > > Development ---------------------------------------------------------------------- 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
