NTAC:3NS-20

I am trying to configure a new Vswitch that I've not had experience with
previously.  My current vswitch is an access IP VLAN UNAWARE connection.
I had little issue configuring z/VM's TCPIP stack or zLinux instances to
use it.   Now we are attempting to switch to a vswtich that is a
Ethernet Trunk mode Vlan aware connection.  It took a little but z/VM's
TCPIP stack is up and using it.  I learn from that configuration that
particular VLAN that hosts the IP subnet needs to be specified that the
guest level.  Correct me if I'm wrong in that assumption.  Now I've move
on to a zLinux server that is currently connected to the old vswitch.
I'm following instruction from the OSA Implementation guide, z/VM
Connectivity, and Redhat 6 Install guide to try to piece together the
process. 

1. Virtual NIC(8000-8002) attached to guest and access allowed via RACF.
2. Update cio_ignore to allow virtual network devices
3. Use ZNETCONF to configure devices to a particular ETHx
interface...specify as Layer 2 using attribute flag
4.  IFCONFIG interface online with parms after ensuring device is online
4. INSMOD 8021q for VLAN support
5.  Use VCONFIG to assign specific VLAN to ETHx interface
6. IFCONFIG interface with vlan online

At this point, my IFCONFIG looks like this for the interface in
question:

eth2      Link encap:Ethernet  HWaddr 02:00:0E:00:00:11
               inet addr:10.125.3.50  Bcast:10.125.3.255
Mask:255.255.255.0
              inet6 addr: fe80::eff:fe00:11/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:4 errors:0 dropped:0 overruns:0 frame:0
              TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:128 (128.0 b)  TX bytes:2994 (2.9 KiB)

eth2.3796 Link encap:Ethernet  HWaddr 02:00:0E:00:00:11
          inet6 addr: fe80::eff:fe00:11/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:112 (112.0 b)  TX bytes:936 (936.0 b)

Now I'm left with adding a gateway for this interface.  If I use the
"route add default gw" that is specific to ETH2, it kills the other
vswitch network connection at ETH0.  I can recover from my z/VM console
connection
to the guest by taking down ETH2 and bringing ETH0 down/up with a new
route command for it's default gateway.

Is there a cookbook for something like this?  I'm certain I'm missing
some steps along the way?  Can anyone see any errors in my process that
could be the cause of this issue?

All input would be much appreciated. 

----------------------------------------------------------------------
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 more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to