It would appear that you must indicate each VLAN that the guest is a
member of when you issue the grant command. Otherwise, I get no
connectivity at all. I've tried it both ways now; with and without each
VLAN specified. I have been able to get it to work if I specify each
VLAN in the grant command, but then I run into issues with routing that
I can't explain... Namely the interface that's specified as the default
gateway will return ICMP packets, but the other will not. If I switch
the default gateway over to the other network, it then will return
pings, but the previous interface will not.
I thought perhaps it was necessary to use more than one virtual nic in
order to get more than one VLAN to work at a time. I'm hearing no. Allow
me to include my configuration, perhaps that will help shine a light on
things.
The guest's PROFILE EXEC entry:
DEF NIC 3022 QDIO DEV 3
COUPLE 3022 SYSTEM VSS3000
The VSWITCH configuration:
q vswitch vss3000 accesslist
VSWITCH SYSTEM VSS3000 Type: VSWITCH Connected: 4 Maxconn: INFINITE
PERSISTENT RESTRICTED NONROUTER Accounting: OFF
VLAN Aware Default VLAN: 1234 Default Porttype: Trunk GVRP:
Enabled
State: Ready
IPTimeout: 5 QueueStorage: 8
Portname: UNASSIGNED RDEV: 1D04 Controller: DTCVSW2 VDEV: 1D04
Portname: UNASSIGNED RDEV: 2D04 Controller: DTCVSW1 VDEV: 2D04
BACKUP
Authorized userids:
SLX004 VLAN: 3022 3046 Porttype: Trunk
SYSTEM VLAN: 1234 Porttype: Trunk
Linux ifconfig and routing table:
eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:1D
inet6 addr: fe80::200:0:100:1d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:1201 errors:0 dropped:0 overruns:0 frame:0
TX packets:239 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:591748 (577.8 Kb) TX bytes:18921 (18.4 Kb)
hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:10.0.129.162 Bcast:10.0.129.255
Mask:255.255.255.128
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:8192 Metric:1
RX packets:378411 errors:0 dropped:0 overruns:0 frame:0
TX packets:439161 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:78994236 (75.3 Mb) TX bytes:140773939 (134.2 Mb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2659 (2.5 Kb) TX bytes:2659 (2.5 Kb)
vlan3022 Link encap:Ethernet HWaddr 02:00:00:00:00:1D
inet addr:10.250.32.33 Bcast:10.250.32.255
Mask:255.255.255.0
inet6 addr: fe80::200:0:100:1d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:256 (256.0 b) TX bytes:948 (948.0 b)
vlan3046 Link encap:Ethernet HWaddr 02:00:00:00:00:1D
inet addr:10.254.32.33 Bcast:10.254.32.255
Mask:255.255.255.0
inet6 addr: fe80::200:0:100:1d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1864 (1.8 Kb) TX bytes:468 (468.0 b)
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
10.0.129.128 0.0.0.0 255.255.255.128 U 0 0 0
hsi0
10.250.32.0 0.0.0.0 255.255.255.0 U 0 0 0
vlan3022
10.254.32.0 10.254.32.1 255.255.255.0 UG 0 0 0
vlan3046
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo
0.0.0.0 10.250.32.1 0.0.0.0 UG 0 0 0
vlan3022
With the configuration as it is now, I am able to ping vlan3022, but not
vlan3046 remotely. If I switch it so that vlan3046 is the default
gateway (and modify the routing table for vlan3022), then I am able to
ping vlan3046 but not vlan3022.
Thanks.
Dave
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Marcy Cortes
Sent: Monday, December 15, 2008 8:58 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: SLES10-SP2 Guest on VSWITCH w/2 VLANs
You can do it on one NIC. Your Linux will need to tag the frames.
Don't put a VLAN number in the grant command and DO define it as
porttype trunk. See the "vconfig" command & google "linux vlan
tagging" for how to set up the linux side.
Marcy
"This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."
________________________________
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of KEETON Dave * OR SDC
Sent: Monday, December 15, 2008 8:53 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: [IBMVM] SLES10-SP2 Guest on VSWITCH w/2 VLANs
If I need to access more than one VLAN on a VSWITCH configured for
ETHERNET, do I need to create a separate virtual nic for each VLAN or
can all the VLANs be associated to one adapter, such as eth0? I've been
trying to get the latter configuration to work without any success.
Thanks,
Dave Keeton
