Thing is, there's not an actual OSA card in use here. It's all virtual stuff.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scorch Burnet Sent: Wednesday, March 31, 2004 5:52 PM To: [EMAIL PROTECTED] Subject: Re: Adding QDIO guest lan to server I believe that there can be only one portname per osa card and taht name is case sensitive... I defined the portname when i set up vm. since i only have one osa car (albeit, with 16 addresses) all my linux images including the ones on the vswitch point to that portname Kern, Thomas wrote: >I did switch the second NIC to being E04-E06 and I get the same >messages. > >This is an old TurboLinux distribution and the /etc/chandev.conf was >provided by someone from TurboLinux to get it to talk to the 3172. I do >have plans to migrate to a newer but still unsupported copy of RedHat, >but I must wait on the network/security folks to become available to >review and approve. > >I defined these NICs by hand using 'hcp (or #CP) define nic e00 qdio' >and here are the details from the QUERY NIC DETAILS. hcp q nic details >Adapter 0E00 Type: QDIO Name: UNASSIGNED Devices: 3 > Port 0 MAC: 00-04-AC-00-00-09 LAN: SYSTEM VMLAN00 MFS: 8192 > RX Packets: 0 Discarded: 0 Errors: 0 > TX Packets: 0 Discarded: 0 Errors: 0 > RX Bytes: 0 TX Bytes: 0 > Unassigned Devices: > Device: 0E00 Unit: 000 Role: Unassigned > Device: 0E01 Unit: 001 Role: Unassigned > Device: 0E02 Unit: 002 Role: Unassigned >Adapter 0E04 Type: QDIO Name: UNASSIGNED Devices: 3 > Port 0 MAC: 00-04-AC-00-00-07 LAN: SYSTEM VMLAN02 MFS: 8192 > RX Packets: 0 Discarded: 0 Errors: 0 > TX Packets: 0 Discarded: 0 Errors: 0 > RX Bytes: 0 TX Bytes: 0 > Unassigned Devices: > Device: 0E04 Unit: 000 Role: Unassigned > Device: 0E05 Unit: 001 Role: Unassigned > Device: 0E06 Unit: 002 Role: Unassigned > >/Thomas Kern >/301-903-2211 > > > >>-----Original Message----- >>From: Post, Mark K [mailto:[EMAIL PROTECTED] >>Sent: Wednesday, March 31, 2004 16:38 >>To: [EMAIL PROTECTED] >>Subject: Re: Adding QDIO guest lan to server >> >> >>I see a couple of problems here. The virtual NICs need to have a >>starting address that is on an even boundary. So, >>"qeth2,0xe03,0xe04,0xe05,0,0" is >>invalid. >> >>"chandev=" is something you would put in your parmfile, not in >>/etc/chandev.conf. >> >>How did you define the virtual NICs? If you don't explicitly say >>QDIO, you get a HiperSocket type. (CP Q NIC DETAILS). >> >>Having a real LCS NIC has nothing to do with a GuestLAN virtual NIC. >> >>In every case I've ever seen, the "cause code 0x22 -- try another >>portname" messages you got are a result of the portname specification >>not matching >>what other systems are using. >> >> >>Mark Post >> >>-----Original Message----- >>From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of >>Kern, Thomas >>Sent: Wednesday, March 31, 2004 3:05 PM >>To: [EMAIL PROTECTED] >>Subject: Adding QDIO guest lan to server >> >> >>I am trying to add a QDIO guest lan to replace the IUCV connection >>between a firewall server and a web server. The firewall server has a >>3172 connection >>to the real network. I tried to mimic the configuration from >>another server >>I have that has a claw device to the network and a guest lan >>to our VM based >>services. This new firewall server will eventually have 2 >>guest lans, one >>being to the VM services and the other to its collection of >>linux servers. >> >>When I ipl the firewall server I get nasty messages in the console >>log. Am I doing something wrong with this configuration? Are QDIO >>guest lans incompatible with real LCS devices? >> >>/Thomas Kern >>/301-903-2211 >> >>Console Log: >>qeth: Trying to use card with devnos 0xE04/0xE05/0xE03 >> >>qeth: received an IDX TERMINATE on irq 0x7/0x8 with cause code 0x22 -- >>try another portname >> >>qeth: received an IDX TERMINATE on irq 0x7/0x8 with cause code 0x22 -- >>try another portname >> >>qeth: There were problems in hard-setting up the card. >> >>qeth: Trying to use card with devnos 0xE00/0xE01/0xE02 >> >>qeth: received an IDX TERMINATE on irq 0x9/0xA with cause code 0x22 -- >>try another portname >> >>qeth: received an IDX TERMINATE on irq 0x9/0xA with cause code 0x22 -- >>try another portname >> >>qeth: There were problems in hard-setting up the card. >> >>debug: unregistering qeth_setup >> >>/etc/modules.conf: >>alias eth0 lcs >>alias iucv0 netiucv >>alias iucv1 netiucv >>options netiucv iucv=lnxsss1:lnxsss2 >>alias ctc0 ctc >>options ctc setup='"0,0xf00,0xf01,ctc0"' >>alias eth1 qeth >>alias eth2 qeth >> >>/etc/chandev.conf: >>chandev=noauto,lcs0,0x39eo,0x39e1,0,0,1,1 >>noauto >>add_parms,0x10,0xe00,0xe02,portname:VMLAN00 >>qeth1,0xe00,0xe01,0xe02,0,0 >>add_parms,0x10,0xe03,0xe05,portname:VMLAN02 >>qeth2,0xe03,0xe04,0xe05,0,0 >> >> >>---------------------------------------------------------------------- >>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 >> >>---------------------------------------------------------------------- >>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 >> >> >> > >---------------------------------------------------------------------- >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 > > > ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
