Perhaps there is a solution to my situation but I've yet to come across it. 

Is it possible to create a aggregate link of all e1000 adapters and then add 
VLANs to run across the link? So far I've been able to make it work with 2 
VLANs (default of 0 and one addition) but no more. When I add a 3rd VLAN it 
obtains an address from the DHCP server in the same range as one of the other 
VLANs. 

Here's the scenario: 

The server is OpenSolaris svn_134 with a quad port NIC (aggregated into 1 nic), 
1 administrative NIC, and VirtualBox 3.2.8 installed. The goal is to have 1 
link (the aggregate) with multiple VLANs running across it so that different 
Virtual Machines can access different VLANs by choosing which NIC to bridge 
with.

Any advice, troubleshooting info, or links to relevant docs/sites would be 
immensely helpful.

Thank you!

Commands used to create the links in the configuration below:

1.      Rename all the links: dladm rename-link e1000g0 addin0
2.      Create the aggregate link:      dladm create-aggr -P L2,L3 -l addin0 -l 
addin1 -l addin2 -l addin3 aggr0
3.      Create the first VLAN: dladm create-vlan -l aggr0 -v 101 cls101
3.      Create the second VLAN: dladm create-vlan -l aggr0 -v 103 qa103
4.      Plumb the VLANs and obtain DHCP leases.

Configuration:

v...@vm1:~$ pfexec bash
v...@vm1:~# cat /etc/release
                       OpenSolaris Development snv_134 X86
           Copyright 2010 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                             Assembled 01 March 2010
v...@vm1:~# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 
index 1
        inet 127.0.0.1 netmask ff000000
aggr0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
        inet 192.168.28.7 netmask fffffe00 broadcast 192.168.29.255
        ether 0:15:17:98:66:89
ob0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 3
        inet 192.168.28.10 netmask fffffe00 broadcast 192.168.29.255
        ether 0:30:48:c6:af:90
vboxnet0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 
index 4
        inet 192.168.56.1 netmask ffffff00 broadcast 192.168.56.255
        ether 8:0:27:dc:31:9b
cls101: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 
index 9
        inet 192.168.1.48 netmask ffffff00 broadcast 192.168.1.255
        ether 0:15:17:98:66:89
qa103: flags=201004842<BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 
index 10
        inet 0.0.0.0 netmask 0
        ether 0:15:17:98:66:89
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 
index 1
        inet6 ::1/128
v...@vm1:~# dladm show-link
LINK        CLASS     MTU    STATE    BRIDGE     OVER
addin0      phys      1500   up       --         --
addin1      phys      1500   up       --         --
addin2      phys      1500   up       --         --
addin3      phys      1500   up       --         --
ob0         phys      1500   up       --         --
ob1         phys      1500   unknown  --         --
aggr0       aggr      1500   up       --         addin0 addin1 addin2 addin3
vboxnet0    phys      1500   unknown  --         --
cls101      vlan      1500   up       --         aggr0
qa103       vlan      1500   up       --         aggr0
v...@vm1:~# dladm show-vlan
LINK            VID      OVER         FLAGS
cls101          101      aggr0        -----
qa103           103      aggr0        -----
v...@vm1:~# dladm show-phys
LINK         MEDIA                STATE      SPEED  DUPLEX    DEVICE
addin0       Ethernet             up         1000   full      e1000g0
addin1       Ethernet             up         1000   full      e1000g1
addin2       Ethernet             up         1000   full      e1000g2
addin3       Ethernet             up         1000   full      e1000g3
ob0          Ethernet             up         1000   full      igb0
ob1          Ethernet             unknown    0      half      igb1
vboxnet0     Ethernet             unknown    0      unknown   vboxnet0
-- 
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org

Reply via email to