For what it's worth here's the pertinent entry in my chandev.conf: noauto;qeth0,0x0800,0x0801,0x0802;add_parms,0x10,0x0800,0x0802,portname:GL1
If this is the first machine to use the Guest Lan it will be able to set the name, so what you use really doesn't matter. All of the other machines will have to comply. I see that the LAN is restricted, is this machine authorized to use it? (I would have expected a different message, though) On Fri, 2004-04-02 at 11:42, Kern, Thomas wrote: > Swapping the order of qeth-1 and add_parms doesn't change it. > > cat /etc/chandev.conf > chandev=noauto > lcs-1,0x3ad0,0x3ad1,0,3 > qeth-1,0x0e04,0xe05,0x0e06,0,0 > add_parms,0x10,0x0e04,0x0e06,portname:VMLAN01 > > Q NIC DETAILS > Adapter 0E04 Type: QDIO Name: UNASSIGNED Devices: 3 > Port 0 MAC: 00-04-AC-00-00-0B LAN: SYSTEM VMLAN01 MFS: 8192 > RX Packets: 0 Discarded: 0 Errors: 0 > TX Packets: 0 Discarded: 0 Errors: 0 > RX Bytes: 0 TX Bytes: 0 > Connection Name: HALLOLE State: CM_CONNECT > Device: 0E04 Unit: 000 Role: CTL-READ > Device: 0E05 Unit: 001 Role: CTL-WRITE > Device: 0E06 Unit: 002 Role: DATA > > Q LAN VMLAN01 DETAILS > LAN SYSTEM VMLAN01 Type: QDIO Active: 1 MAXCONN: 32 > PERSISTENT RESTRICTED MFS: 8192 ACCOUNTING: ON > Authorized userids: > LNXRHFW LNXRH00 LNXRH01 LNXRH02 LNXRH03 LNXRH04 > LNXRH05 > Adapter Owner: LNXRHFW NIC: 0E04 Name: UNASSIGNED > > cat /proc/chandev > > > > > > chan_type key bitfield > ctc=0x1,escon=0x2,lcs=0x4,osad=0x8,qeth=0x10,claw=0x20 > > > *'s for cu/dev type/models indicate don't cares > > > > cautious_auto_detect: on > > > > persist = 0x00 > > > > use_devno_names: off > > > > Channels enabled for detection > > chan cu cu dev dev max checksum use hw auto > recovery > type type model type model port_no. received stats type > > ============================================================================ > == > 0x02 0x3088 0x1e * * 0 no no > not_operational,no_path,revalidate,device_gone > > 0x20 0x3088 0x61 * * 0 no no > not_operational,no_path,revalidate,device_gone > > 0x08 0x3088 0x62 * * 0 no no > not_operational,no_path,revalidate,device_gone > > 0x10 0x1731 0x05 0x1732 0x05 0 no no > not_operational,no_path,revalidate,device_gone > > 0x10 0x1731 0x01 0x1732 0x01 0 no no > not_operational,no_path,revalidate,device_gone > > 0x04 0x3088 0x60 * * 1 no no > not_operational,no_path,revalidate,device_gone > > 0x06 0x3088 0x1f * * 15 no no > not_operational,no_path,revalidate,device_gone > > 0x05 0x3088 0x08 * * 15 no no > not_operational,no_path,revalidate,device_gone > > 0x04 0x3088 0x01 * * 15 no no > not_operational,no_path,revalidate,device_gone > > > > Registered probe functions > > probefunc shutdownfunc msck_notfunc chan devices devices > > type found active > > =============================================================== > > 0x028a4ffc 0x028a537c 0x028a53f4 0x04 1 1 > > > > Initialised Devices > > read write data read write data chan port dev dev > memory read msck write msck data msck > > irq irq irq devno devno devno type no. ptr name > usage(k) status status status > > ============================================================================ > ========================================= > > 0x0000 0x0001 n/a 0x3ad0 0x3ad1 n/a 0x04 2 0x01d17800 eth0 > 320 good good not applicable > > > > Total device memory usage 320k. > > > > channels detected > > chan cu cu dev dev in > chandev > irq devno type type model type model pim chpids use > reg. > ============================================================================ > === > 0x0000 0x3ad0 0x04 0x3088 0x01 0x0000 0x00 0x80 0x3affffffffffffff yes > yes > 0x0001 0x3ad1 0x04 0x3088 0x01 0x0000 0x00 0x80 0x3affffffffffffff yes > yes > 0x0006 0x0e04 0x10 0x1731 0x01 0x1732 0x01 0x80 0x0200000000000000 no > no > 0x0007 0x0e05 0x10 0x1731 0x01 0x1732 0x01 0x80 0x0200000000000000 no > no > 0x0008 0x0e06 0x10 0x1731 0x01 0x1732 0x01 0x80 0x0200000000000000 no > no > > /Thomas Kern > /301-903-2211 > > > -----Original Message----- > > From: Post, Mark K [mailto:[EMAIL PROTECTED] > > Sent: Friday, April 02, 2004 12:28 > > To: [EMAIL PROTECTED] > > Subject: Re: Adding QDIO guest lan to server > > > > I believe that the order of the cards in /etc/chandev.conf is > > significant. > > I've always seen it coded this way: > > # cat /etc/chandev.conf > > qeth0,0x0f10,0x0f11,0x0f12 > > add_parms,0x010,0x0f10,0x0f12,portname:LINUXSRV > > > > The "qeth" statement first, followed by the add_parms for that device. > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > > Behalf Of Rich > > Smrcina > > Sent: Friday, April 02, 2004 12:20 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Adding QDIO guest lan to server > > > > It indicates that the portname is wrong. Verify the port > > name with Q LAN > > DETAILS. > > ---------------------------------------------------------------------- > 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 -- Rich Smrcina Sr. Systems Engineer DSG eServer & Linux Solutions Milwaukee, WI rsmrcina at wi.rr.com rsmrcina at dsgroup.com Catch the WAVV! Stay for requirements and the free-for-all. Update your zSeries skills in 4 days for a very reasonable price. WAVV 2004 in Chattanooga, TN April 30-May 4, 2004 For details see http://www.wavv.org ---------------------------------------------------------------------- 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
