Hello Eric,
I spent a lot of time to make CTC/ESCON connection operational in my
system. This is my working definition now:
SLES 7.2 with Kernel 2.4.19 May 2002.
CTC between lpar "SYST" and "PROD" (two lpar linux without VM).
ID MSG1='020515 -Configuration LINUX 3 partitions', *
MSG2='2003-03-28 12:07',SYSTEM=(9672,4) *
RESOURCE PARTITION=((SYST,1),(DEVS,2),(PROD,3))
CHPID PATH=(88),SHARED,PARTITION=(DEVS,PROD),TYPE=OSA
CHPID PATH=(98),SHARED,PARTITION=(SYST,DEVS,PROD),TYPE=CTC
CHPID PATH=(99),SHARED,PARTITION=(SYST,DEVS,PROD),TYPE=CNC
CHPID PATH=(9A),SHARED,PARTITION=(SYST,DEVS,PROD),TYPE=CNC
CHPID PATH=(9B),SHARED,PARTITION=(SYST,DEVS,PROD),TYPE=CNC
CNTLUNIT CUNUMBR=0C10,PATH=(98),UNITADD=((00,002)),CUADD=1, *
UNIT=SCTC
CNTLUNIT CUNUMBR=0C20,PATH=(98),UNITADD=((00,002)),CUADD=2, *
UNIT=SCTC
CNTLUNIT CUNUMBR=0C30,PATH=(98),UNITADD=((00,002)),CUADD=3, *
UNIT=SCTC
CNTLUNIT CUNUMBR=0D10,PATH=(99),UNITADD=((00,002)),CUADD=1, *
UNIT=SCTC
CNTLUNIT CUNUMBR=0D20,PATH=(99),UNITADD=((00,002)),CUADD=2, *
UNIT=SCTC
CNTLUNIT CUNUMBR=0D30,PATH=(99),UNITADD=((00,002)),CUADD=3, *
UNIT=SCTC
CNTLUNIT CUNUMBR=A100,PATH=(9A,9B),UNITADD=((00,075)), *
CUADD=1,UNIT=2105
CNTLUNIT CUNUMBR=A200,PATH=(9A,9B),UNITADD=((00,075)), *
CUADD=2,UNIT=2105
CNTLUNIT CUNUMBR=6001,PATH=(88),UNIT=OSA
IODEVICE ADDRESS=(C10,002),UNITADD=00,CUNUMBR=(0C10),STADET=Y,*
PARTITION=(PROD,SYST),UNIT=SCTC
IODEVICE ADDRESS=(C20,002),UNITADD=00,CUNUMBR=(0C20),STADET=Y,*
PARTITION=(DEVS,SYST),UNIT=SCTC
IODEVICE ADDRESS=(C30,002),UNITADD=00,CUNUMBR=(0C30),STADET=Y,*
PARTITION=(DEVS,PROD),UNIT=SCTC
IODEVICE ADDRESS=(D10,002),UNITADD=00,CUNUMBR=(0D10),STADET=Y,*
PARTITION=(PROD,SYST),UNIT=SCTC
IODEVICE ADDRESS=(D20,002),UNITADD=00,CUNUMBR=(0D20),STADET=Y,*
PARTITION=(DEVS,SYST),UNIT=SCTC
IODEVICE ADDRESS=(D30,002),UNITADD=00,CUNUMBR=(0D30),STADET=Y,*
PARTITION=(DEVS,PROD),UNIT=SCTC
IODEVICE ADDRESS=(A100,075),CUNUMBR=(A100),STADET=Y,UNIT=3390B
IODEVICE ADDRESS=(A200,075),CUNUMBR=(A200),STADET=Y,UNIT=3390B
IODEVICE ADDRESS=(600,002),CUNUMBR=(6001),STADET=Y,UNIT=OSA, *
PARTITION=(PROD),UNITADD=00
IODEVICE ADDRESS=(602,002),CUNUMBR=(6001),STADET=Y,UNIT=OSA, *
PARTITION=(DEVS),UNITADD=02
"PROD"
Kernel command line:
dasd=a101,a106-a10a root=/dev/dasda1 noinitrd
/etc/chandev.conf:
ctc0,0x0d30,0x0d31,0,0,0,0
"SYST"
Kernel command line:
dasd=a100 root=/dev/dasda1 noinitrd
/etc/chandev.conf
ctc0,0x0c21,0x0c20,0,0,0,0
Gerard MONTELEONE
Ingenieur Systeme & Reseau
( 04.95.23.68.09 / 06.87.72.70.32
S.I.TE.C zi du Vazzio
20090 AJACCIO Cedex
[EMAIL PROTECTED]
-----Message d'origine-----
De�: Linux on 390 Port [mailto:[EMAIL PROTECTED] De la part de
Eric Bielefeld
Envoy�: mardi 1 avril 2003 21:59
��: [EMAIL PROTECTED]
Objet�: Re: CTC Connection Question
Mark,
Thanks for the list of commands you included. I will definitely check
them all out. I will be spending most of the day tomorrow at our
datacenter, so I can try IPLing Linux again. I am making a change to my
IOCDS tonight. I also discovered that I was using the keyword CTC= in
the Parm Line file. I believe, as you mentioned in your post, that the
correct keyword is CHANDEV=. Before, it just ignored the CTC= keyword,
and asked the question of the devices. I'll let everyone know whether I
am successful tomorrow or not.
Eric
>>> [EMAIL PROTECTED] 03/28/03 05:33PM >>>
Eric,
Sorry for the late reply to this. I'm more than a little behind.
The messages you're getting are indicating that either the CTC driver
didn't
load, or the parameters passed to it are such that it isn't finding the
devices you believe it should be finding.
At times like this, I always tell people to try issuing the necessary
commands manually, since the installation scripts usually hide any error
messages that might be getting issued by the driver.
Hopefully, the initrd for your distribution also includes the "dmesg"
command, since that is frequently very helpful as well.
Once you've gone through the IPL and failed to get a working connection,
see
what these commands generate:
- lsmod (to see if ctc is loaded. It probably will not be loaded. If
it
is, your system may also load "fsm" as well.)
- cat /etc/chandev.conf (to see what the installer put in there.)
- modprobe ctc
You should see something similar to this:
CTC driver Version: 1.51.2.1 with CHANDEV support initialized
ctc0: read: ch 0d00 (irq 0007), write: ch 0d01 (irq 0008) proto: 3
Or, you may get an error message that will tell you something.
- dmesg (to see if there are any other error messages in there.)
Mark Post
-----Original Message-----
From: Eric Bielefeld [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 4:40 PM
To: [EMAIL PROTECTED]
Subject: CTC Connection Question
I've been trying to get my network connected to my LINUX Lpar through a
CTC
connection. I think I have everything defined correctly. I did the
IOCDS
change last week, and put a couple of definitions in my MVS TCPIP
Profile.
I hooked up an Escon cable between 2 chpids. When I IPL Linux, I get
the
following error messages:
ctc0: unknown interface; No such device
SIOCSIFDSTADDR: No such device
ctc0: unknown interface; No such device
I put most of the answers to the networking questions in my PARM.LINE
file.
I still get one question that asks:
Please enter the parameters you need to pass to the channel device
layer:
and then has an example. I reply:
"ctc0,0D00,0D01"
What is going wrong? I've tried several different combinations, and
always
get the 3 messages above. I can send the things I've changed if that is
necessary. I'll be out in the computer room and away from my PC trying
this
again. I will check for replies before I go home. I have to be
somewhere,
so I can't stay very late. I'll be here till 4:45 Central time.
Otherwise,
I'll reply in the morning. Thanks in advance.
Eric Bielefeld
Sr. MVS Systems Programmer
P&H Mining Equipment
Milwaukee, WI
414-671-7849
[EMAIL PROTECTED]
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++
This electronic mail transmission contains information from P & H Mining
Equipment
which is confidential, and is intended only for the use of the proper
addressee.
If you are not the intended recipient, please notify us immediately at
the return
address on this transmission, or by telephone at (414) 671-4400, and
delete this
message and any attachments from your system. Unauthorized use,
copying,
disclosing, distributing, or taking any action in reliance on the
contents of this
transmission is strictly prohibited and may be unlawful.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++
