VSWG isn't the name of the test vswitch; it's the production one... (could've just yelled this over the cube wall, but this was more fun. ;-) )
-- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 10/21/08 2:55 PM, "Patrick Spinler" <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Marcy Cortes wrote: >> The "simplest" way is really just to go edit the directory entry and log >> it off and back on. Patrick must be using some really horrible >> directory manager! ;) >> > > Heh. Make me do it the easy way. :-) > > Okay, so, here's what I did. > > I added this to my test system's directory: > > COMMAND SET VSWITCH VSWTEST1 GRANT &USERID > COMMAND COUPLE 8C00 TO SYSTEM VSWG > NICDEF 8C00 TYPE QDIO LAN SYSTEM VSWG > > Logged it out and back in again. Went into yast and configured the > second interface. Noted that when running yast over a ssh tunnel, > restarting networking is a really bad deal. Oh, and forgot to configure > the default route, so had to manuall fix that both of these from the > console. Bleah. > > However, now, it's still not recognizing the second ethernet interface. > Any ideas? > > [EMAIL PROTECTED] ~ $ ifconfig -a > eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:2C > ... > lo Link encap:Local Loopback > ... > sit0 Link encap:IPv6-in-IPv4 > > [EMAIL PROTECTED] ~ $ ls /sys/devices/qeth/ > 0.0.8200 0.0.8c00 uevent > > (It shows up in /sys/devices! That's an improvement ...) > > [EMAIL PROTECTED] network $ cat ifcfg-qeth-bus-ccw-0.0.8c00 > BOOTPROTO='dhcp' > BROADCAST='' > ETHTOOL_OPTIONS='' > IPADDR='' > LLADDR='' > MTU='' > NAME='IBM OSA Express Network card (0.0.8c00)' > NETMASK='' > NETWORK='' > REMOTE_IPADDR='' > STARTMODE='auto' > UNIQUE='Kyl7.FOqOuhDmSR4' > USERCONTROL='no' > _nm_name='qeth-bus-ccw-0.0.8c00' > > [EMAIL PROTECTED] network $ dmesg | grep qeth > qeth: loading qeth S/390 OSA-Express driver > qeth: Device 0.0.8200/0.0.8201/0.0.8202 is a Guest LAN QDIO card (level: > V531) > qeth: Hardware IP fragmentation not supported on eth0 > qeth: VLAN enabled > qeth: Multicast enabled > qeth: IPV6 enabled > qeth: Broadcast enabled > qeth: Using SW checksumming on eth0. > qeth: Outbound TSO not supported on eth0 > qeth: received an IDX TERMINATE with cause code 0xf6 > qeth: sense data available on channel 0.0.8c00. > qeth: cstat 0x0 > qeth: irb: 00 c2 60 17 3f c9 90 38 0e 00 10 00 00 80 00 00 > qeth: irb: 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > qeth: sense data: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > qeth: sense data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > qeth: Initialization in hardsetup failed! rc=-5 > qeth: Device 0.0.8200/0.0.8201/0.0.8202 is a Guest LAN QDIO card (level: > V531) > qeth: Hardware IP fragmentation not supported on eth0 > qeth: VLAN enabled > qeth: Multicast enabled > qeth: IPV6 enabled > qeth: Broadcast enabled > qeth: Using SW checksumming on eth0. > qeth: Outbound TSO not supported on eth0 > > > This feels like the old forgetting to specify allowed device numbers for > dasd back in suse 8 days (or current redhat. Ahem. Nudge redhat to get > this fixed) > > Should be setting up some other module.conf parameter or something? > > Oh yes, and the suggested qethon.sh script also doesn't help, at least > not without editing. IT detects that there's already one active deviec, > and helpfully exits without trying to activate a second one. :-( > > Thanks! > - -- Pat > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFI/jOVNObCqA8uBswRAlnYAJ4mEHwFuCjvzcAZDaopKQir2b1QrQCfa4Er > K7vmc4ssYFR7sF6bjiXg/3M= > =2awp > -----END PGP SIGNATURE-----
