Michael, Yes. The documentation says you're supposed to be able to do what you're trying to do, but I never got it to work. Instead, just have multiple chandev parameters in the file (or in /etc/) like this: chandev=ctc0,0x2002,0x2003 chandev=ctc1,0x2001,0x2002 Mark Post -----Original Message----- From: Michael K Lambert [mailto:mlambe7@lsu.edu] Sent: Friday, January 04, 2002 11:15 AM To: redhat-s390-list@redhat.com Subject: [Redhat-s390-list] multiple CTC device declarations Happy new year to everyone. I've been having trouble establishing multiple CTC connections on a Red Hat image that we installed just prior to the holidays. Previously, I had a working connection (ctc0) between the Red Hat image and an older SuSE installation. However, when I attempted to add a second CTC device (ctc1) between Red Hat and VM tcp/ip, it never worked. On startup ctc1 would appear to initialize, but wouldn't show up when I gave an ifconfig -a command. When I attempted to bring it up with "ifconfig ctc1 up," I received a "ctc1: unknown interface: No such device" message. Suspecting that my parmfile syntax was wrong, I reversed the ctc device network scripts, changing ctc0 to ctc1 and vice-versa. Now the connection with VM tcp/ip comes up, but the SuSE ctc does not. My parmfile reads: target=/boot/ image=/boot/vmlinuz-2.4.9-13.4 parameters="root=/dev/dasdb1 dasd=400-401 iucv=linuxsx root=/dev/dasdb1 noinitrd chandev=ctc0,0x2002,0x2003,ctc1,0x2001,0x2002" Does anyone see any syntatical errors in my chandev statement? Michael Lambert _______________________________________________ Redhat-s390-list mailing list Redhat-s390-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-s390-list
