Esteemed colleagues -
I am attempting to bring up SLES9 in an LPAR on an MP3000. I have some
reasonable experience with SLES9 on s390 from many years ago, but my experience
then was with VM, OSA Express, and VSWITCH. So some of this is new to me, and
I'm struggling.
I have the install working (to some degree) with the MP3000 emulated
LCS3174/MPTN arrangement, but I'm having trouble with attempts to bring the
(emulated) 3390 volumes online hanging. The first attempt to `echo 1
>/sys/bus/ccw/devices/0.0.0980/online` blocks and never returns, even though
there are messages from the kernel that indicate the device has been probed (it
lists geometry, etc.). Subsequent attempts return immediately, but the value of
`online` always stays 0. I noticed the kernel task 'regipm' (associated with
the LCS device) constantly chewing all of one CPU (apparently due to a
multicast bug that this SLES9 kernel is just a couple patches short of
including a fix for) and I would like to eliminate this as a potential cause of
the dasd problems (however unlikely). So I thought I'd try with a CTC network,
instead. And this is not working at all.
I am trying to create a CTC network between SLES9 in partition 3 (IZXL) and
VM/ESA V2R4 TCPIP in partition 2 (IZXD). VM has an already-functioning ethernet
IP link via the emulated LCS.
devs (r,w) ip peer
VM: 2331,2330 192.168.176.179 192.168.176.79
Linux: 2320,2321 192.168.176.79 192.168.176.179
SLES9 will configure the CTC but fails to ping its peer, and the install can't
proceed. I'm not sure what I'm missing; it may likely be some EMIF CTC detail.
My incomplete understanding is that 2320/2330 should be either end of one CTC
connecting LPARs 2 and 3, and nothing more need be done to connect them, but
I'm not really sure.
Relevant IOCDF entries for the EMIF CTC definitions -
CHPID PATH=(10),TYPE=CTC,SHARED,PART=((IZOD,IZXD,IZXL),(=))
CHPID PATH=(11),TYPE=CNC,SHARED,PART=((IZOD,IZXD,IZXL),(=))
CNTLUNIT CUNUMBER=232F,PATH=(10),CUADD=2,UNIT=SCTC, X
UNITADD=((00,16))
CNTLUNIT CUNUMBER=233E,PATH=(11),CUADD=3,UNIT=SCTC, X
UNITADD=((00,16))
IODEVICE ADDRESS=(2320,16),UNIT=SCTC,CUNUMBR=(232F), X
UNITADD=00,STADET=Y,PART=(IZXL)
IODEVICE ADDRESS=(2330,16),UNIT=SCTC,CUNUMBR=(233E), X
UNITADD=00,STADET=Y,PART=(IZOD,IZXD)
Relevant data from the VM side -
q ctc
CTCA 0E20 ATTACHED TO TCPIP 0E20
CTCA 0E21 ATTACHED TO TCPIP 0E21
CTCA 2330 ATTACHED TO TCPIP 2330
CTCA 2331 ATTACHED TO TCPIP 2331
Ready; T=0.01/0.01 08:57:53
PROFILE TCPIP (excerpted) -
===== DEVICE UNIT0 LCS E20
===== LINK MPTN2 ETHERNET 2 UNIT0
===== DEVICE IZXL CTC 2330
===== LINK IZXL2320 CTC 1 IZXL /* I've tried this with both CTC 1 and CTC 0 */
===== HOME
===== 192.168.5.78 MPTN2
===== 192.168.176.179 IZXL2320
===== GATEWAY
===== 192.168.0.0 = MPTN1 DEFAULTSIZE 0.0.255.0 0.0.5.0
===== ; IZXL CTC
===== 192.168.176.79 = IZXL2320 1500 HOST
===== START UNIT0
===== START IZXL2320
Linux console log (exerpted) -
Please select the type of your network device:
4) Channel to Channel
Enter your choice (0-10):
4
Loading CTC module:
CTC driver Version: 1.58.2.1 initialized
List of first 10 CTC Channels that were detected:
Device Channel type
0.0.0e20 3088/01
0.0.0e21 3088/01
0.0.2310 3088/1f
0.0.2311 3088/1f
Device address for read channel (0.0.0e20):
0.0.2320
Device address for write channel (0.0.0e21):
0.0.2321
Select protocol number for CTC:
0) Compatibility mode, also for non-Linux peers other
than OS/3909 and z/OS (this is the default mode)
1) Extended mode
3) Compatibility mode with OS/390 and z/OS
Enter your choice (0):
0
ctc0: read: ch-0.0.2320, write: ch-0.0.2321, proto: 0
ctc0 detected.
ctc0 is available, continuing with network setup.
ifconfig ctc0 192.168.176.79 pointopoint 192.168.176.179 mtu 1500
Trying to ping my IP address:
PING 192.168.176.79 (192.168.176.79) 56(84) bytes of data.
64 bytes from 192.168.176.79: icmp_seq=1 ttl=64 time=0.171ms
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
Waiting 6 seconds for connection with remote side.
Waiting 3 seconds for connection with remote side.
Waiting 4 seconds for connection with remote side.
Waiting 5 seconds for connection with remote side.
Waiting 4 seconds for connection with remote side.
Waiting 4 seconds for connection with remote side.
Waiting 3 seconds for connection with remote side.
Waiting 2 seconds for connection with remote side.
Trying to ping the IP address of the peer:
PING 192.168.176.179 (192.168.176.179) 56(84) bytes of data.
10 packets transmitted, 0 received, 100% packet loss, time 9015ms
Warning: The peer address 192.168.176.179 did not ping.
Statistics from ctc0:
tx_carrier_errors: 10
tx_dropped: 10
tx_errors: 10
Do you want to ignore this error and continue anyway?
So... where am I going wrong?
Alternately I wouldn't mind thoughts on what may actually be causing my problem
with the hangs bringing the dasd online, or information leading to a source for
one or more SLES9 s390 service packs.
Thanks!
ok
bear.
--
until further notice
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
