Re: Claw Driver problems
Here is a public link for CIP FAQ: http://www.cisco.com/warp/public/458/19.html tom -Original Message- From: Jere Julian [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 24 December 2002 5:43 AM To: [EMAIL PROTECTED] Subject: Re: Claw Driver problems This is true. Unfortunately I was unable to find the info outside of the passworded are of Cisco.com. If someone is interested in specific parts of the CIP FAQ, please let me know. -Jere On Mon, Dec 23, 2002 at 12:29:50PM -0500, Mark Post wrote: > Note that the URL Jere gave requires a userid and password to access. > > Mark (the sometimes aggravated archivist) Post > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of > Jere Julian > Sent: Monday, December 23, 2002 11:17 AM > To: [EMAIL PROTECTED] > Subject: Re: Claw Driver problems > > > On Fri, Dec 20, 2002 at 02:52:41PM -0500, Alan Altmark wrote: > > On Friday, 12/20/2002 at 02:20 EST, Mark Post <[EMAIL PROTECTED]> wrote: > > > Paul, > > > > > > Glad you could jump in here, since you can speak with a whole lot more > > > authority on this than most. I did hear back from my co-worker, and he > > > provided a somewhat different set of definitions that also seem to work: > > > > > > IODEVICE ADDRESS=(1000,128),CUNUMBR=(B000),STADET=Y,UNIT=SCTC > > > CNTLUNIT CUNUMBR=B000,PATH=(B0),UNITADD=((00,128)),UNIT=SCTC > > > > Mark, UNIT=SCTC is needed for ESCON-attached routers. For parallel > > attachment, use UNIT=3088 on CNTLUNIT and UNIT=CTC on IODEVICE. > > > > Alan Altmark > > Sr. Software Engineer > > IBM z/VM Development > ---end quoted text--- > > will generally work as 3172 or SCTC but the oficial answer is SCTC: > http://www.cisco.com/en/US/customer/tech/tk331/tk332/technologies_q_and_a_it > em09186a0080094424.shtml > > -Jere > -- > - >| Jere Julian, RHCE, CCNA Cisco Systems, Inc. ITD - IBM Sustaining | >| mailto:[EMAIL PROTECTED] 7025 Kit Creek Rd, RTP, NC 27709 | > - ---end quoted text--- -- - | Jere Julian, RHCE, CCNA Cisco Systems, Inc. ITD - IBM Sustaining | | mailto:[EMAIL PROTECTED] 7025 Kit Creek Rd, RTP, NC 27709 | -
Re: Claw Driver problems
We have our router defined as a 3172. I just went back and re-read this bit from the Cisco doco that we used to install the device: the 3172 shows that it is a 3088 model (x'1F'). MVS will complain if it has the device defined as a 3172 but receives SENSEID information containing 3088 model 61. Even though MVS complains, it will still vary the device online. The MVS message is: IOS445I Physical device is inconsistent with logical. = I know we had trouble with UNIT=SCTC and managed to get it to work with UNIT=3172. Tom -Original Message- From: Paul Winder [mailto:[EMAIL PROTECTED]] Sent: Friday, 20 December 2002 8:48 PM To: [EMAIL PROTECTED] Subject: Re: Claw Driver problems Tom, The claw driver expects to see the c7000 as a 3088. If you cat /proc/subchannels you should see something like: Device sch. Dev Type/Model CU in use PIM PAM POM LPUM CHPIDs -- 33A4 00103088/61 yes 80 80 FF 80 9FFF 33A5 00113088/61 yes 80 80 FF 80 9FFF The driver expects a CU type of 0x3088 and a CU model of 0x61 At UTS Global our c7000's are genned as: C#9F CHPID PATH=9F,TYPE=CNC,PART=(VM1,REC) * CU9F01 CNTLUNIT PATH=9F,CUNUMBR=9F01,UNITADD=((00,256)), + UNIT=CISCO IODEVICE CUNUMBR=9F01,ADDRESS=(3300,256),UNIT=CISCO Regards Paul Winder
Claw Driver problems
It goes something like this We are testing SUSE Linux S390 7.1 with the 2.4.7 kernel. We have it installed directly in an LPAR. We will install under Z/VM at a later date after we get a "proof of concept" application up and running under Websphere. We have an escon attached Cisco 7200 which is already shared by 3 OS390 Lpars on our 7060-H30 (Multiprise 3000). It's defined in our IOCDS as a 3172, but this works on our OS/390 LPARs. We had tried it as an "SCTC" but couldn't get it to work with OS/390. How has anyone defined your devices to the IOCDS? We are using the Packed driver from UTS. It's the only one that we could find that you could install without recompiling the Kernel (or that's what we thought). Our experience level is high with OS390 and mainframes, but is only at PC level when it comes to Linux. No prior Linux 390 experience. When we install we get: # insmod -f c7000p base0=0x01f6 lhost0=LINUX1 uhost0=CIPL1 lappl0=PACKED uappl0=PACKED Using /lib/modules/kernel/drivers/s390/net/c7000p.o Warning: kernel-module version mismatch /lib/modules/kernel/drivers/s390/net/c7000p.o was compiled for kernel version 2.4.7RBH-tape-c7000-1-SMP while this kernel is version 2.4.7-SuSE-SMP # lsmod ModuleSizeUsed by c7000p 310720(unused) Notes: 1) we had to use -f to force the driver. We informed UTS, but they said that this was okay, that we did indeed have the correct driver. 2) when we load the driver we get these messages in the logs: linux1 kernel: c7000p: c7000p_init: base unit 0x1f6 is not the right type linux1 kernel: c7000p: init_module: error -5 registering base unit 0x1f6 linux1 kernel: c7000p: init_module: module loaded It seems that although we have the addresses (01f6 and 01f7) available to the Linux LPAR, that Linux either can't get to them or they are returning the wrong sense information. # cat /proc/net/cista Global Parms: wr_delay=2, buffsize=8192, nbuffs=40, noauto=0 # ifconfig ci0 ci0: error fetching interface information: Device not found We don't know how to verify that the particular addresses are accessible and what device type is present. They do not appear to be auto detected. thank you very kindly for any reply, tom/gary/darcy 3 MVS dinosaurs Sydney, Aus. (P.S. for Mark Post - I've been having trouble sending email to your address for some reason but see you posting regularly. I figure this message is probably best served to the entire community anyway)
linux/390 support
Please forgive any ignorance in this question, yet another MVS techie dipping a toe into the linux world. We are looking to create a Linux/390 LPAR on an H30 and we are trying to figure out the "support" arrangements for the base operating system. With (MVS, OS/390, Z/OS) we ring up the IBM support center for all operating system related problems as part of the cost of licensing the operating system. What is IBM's arrangement with Linux/390? IBM (Australia) has told us that we do not order Linux via IBM but must order through another site, presumably Red Hat or SUSE. If we have installation problems I assume that support is presumably given through the vendor with whom we purchased Linux. My concern is what happens once we have a production application running on Linux/390 and we have an operating system failure. *) Is there any option for getting support from the IBM support center or IBM Global Services? *) Is there a 24x7 support arrangement involved? *) What are typical costs involved with support for Linux/390? *) What type of support does IBM provide? Level 1 equivalent or more? *) How many out there are running production work on Linux/390? *) Does anyone have any experience or war stories with using linux support particularly in Sev-1 or Sev-2 situation? kindest regards for any responses, Tom Rusnak Sydney, Aus. (This message cross posted between LINUX-390 and IBM-MAIN)
