I got this working.. and the secret was eliminating the time between the 'define nic' and the 'couple'.. When I did the define nic - I saw messages on the console that it recognized 900 as a QDIO, etc -- but failed to register the IP address and some other messages.
So - I tried logging into the zVM userid and entering: #CP DETACH NIC 900 -- and then: #CP DEFINE NIC 900 TYPE QDIO#CP COUPLE 900 GUESTA MYLAN eth2 came up automatically on Linux and once I did the above on both guests - it worked and I can ping using IP. So - can you 'stack' commands using the vmcp within Linux? I believe the problem is that Linux recognizes the 900 device -- but brings it online using ifcfg-eth2 before it's actually coupled to the lan - which causes it to be inoperable. Doing the couple immediately following seems to work -- so maybe all I needed was to put the vmcp commands in a script so it happened soon enough? Scott p.s. Thanks for the idea about layer2, etc .. you're post did cause me to look at the console -- I don't see what you see, but it did look strange and made me wonder. ;-) On Tue, Aug 11, 2009 at 8:54 AM, Brad Hinson <[email protected]> wrote: > I set this up and was unable to get it working at first, too. As a > test, I destroyed everything then recreated the GuestLAN with the 'eth' > keyword to test layer2. Then I added OPTIONS="layer2=1" and > MACADDR=<<madeupmacaddr>> to ifcfg-ethX. With the GuestLAN in layer2 > mode, I can ping successfully. > > As to why layer3/IP mode isn't working, it could be my setup, but I > noticed this on the console when I brought the nic online with echo 1 > > /sys/bus/...: > > HCPIPN2833E Error 'E00A'X adding IP address 192.168.7.3 for VSWITCH > SYSTEM VSW2. > HCPIPN2833E IP address is already in use on the LAN. > > which is strange because I'm working with 'lan mylan' but a vswitch > (with guests on a different subnet) is complaining about IP address in > use. I should note that I couldn't get this working with either ARP=no > or ARP=yes in ifcfg-ethX, but the error only appeared when I set ARP=yes. > > If my issues are separate, please don't let them cloud your original > issue, but thought I'd share my experience. Can you test a layer2 > GuestLAN to see if that works? Do you see any VSWITCH-related messages > on the console like I did? > > my config: > > RHEL 5.3 > z/VM 5.2, level 0602 > > > -Brad > > Scott Rohling wrote: > >> We want to establish a small private subnet that some guests can use to >> communicate with between themselves, with all ports open... >> >> On guest A: >> >> vmcp define lan mylan type qdio >> vmcp define nic 900 type qdio >> vmcp couple 900 to guesta mylan >> >> We have an ifcfg-eth2 (this is redhat) that gives an address of >> 192.168.7.2 >> using netmask 255.255.255.0 >> eth2 comes up fine - route shows 192.168.7.0 going over eth2 >> Unrestricted LAN 'mylan' for guesta shows up doing a Q LAN >> >> On guest B: >> >> vmcp define nic 900 type qdio >> vmcp couple 900 to guesta mylan >> >> ifcfg-eth2 gives address of 192.168.7.3 using netmask 255.255.255.0 >> eth2 comes up fine - route shows 192168.7.0 going over eth2 >> Q LAN shows 2 users connected to 'mylan' >> >> Everything looks great -- but they can't talk .. pings, etc just >> fail... >> >> What am I forgetting?? I know I've done this before.... aargh! >> >> Any ideas or insight? >> >> Scott >> >> ---------------------------------------------------------------------- >> 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 >> > > -- > Brad Hinson <[email protected]> > Sr. Support Engineer Lead, System z > Red Hat, Inc. > (919) 754-4198 > www.redhat.com/z > > ---------------------------------------------------------------------- > 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
