On Oct 21, 2009, at 3:32 AM, Sivakumar Shanmugasundaram wrote:
All!
Need help in simulating VLAN tagged traffic between two LDOMS. We
tried first with Solaris 10 and PPA formula interface name. We were
able to ping the thus created VLAN interfaces, but we were not able
to 'snoop' and VLAN tags in the packets. 'snoop vlan' is still not
supported in S10.
Next we tried with Nevada. Here the PPA (interface
+vid*1000+instance) did not work at all (obviously). Inside the
LDOM, we were able to create vnet0 instead of say vnet20000 (vid 20)
in Solaris 10. Still, we were not able to see any VLAN tags in the
packets between the LDOMs.
In OpenSolaris the "PPA hack" support for configuring VLANs was
removed, VLANs data-links are now created with dladm(1M) create-vlan.
(pinged through the VLAN interface IP addresses, or did a 'telnet ip')
Where are we going wrong? Are we wrong to assume that we can 'snoop'
the VLAN tags in the packets that flows between two VLAN tagged
network interfaces? Would using two different systems instead of
using two LDOMS make any difference? Thanks a lot.
LDOMs require you to assign the VLANs to the vnets when you create
them using the ldm(1M) add-vnet command. Once you've done this you
should see tagged traffic if you snoop the vnet "physical" data-link
directly from your guest domain. Then you can create configure your
VLANs with the "PPA hack" if you are running a S10 domain, or with
dladm create-vlan if you are running an OpenSolaris domain.
See also the "Using VLAN Tagging With Logical Domains Software" of the
LDOM user guide on docs.sun.com, which has all the details.
[email protected] can also be used for LDOM-specific
questions.
Nicolas.
-Siva
PS: I am not subscribed to this mailing list. Please include me in
your reply.
--
This message posted from opensolaris.org
_______________________________________________
networking-discuss mailing list
[email protected]
--
Nicolas Droux - Solaris Kernel Networking - Sun Microsystems, Inc.
[email protected] - http://blogs.sun.com/droux
_______________________________________________
networking-discuss mailing list
[email protected]
