Link aggregation is currently not supported on vnet interfaces. See RFE 6520538 (vnet should support link aggregation). Please have yourself added to the RFE if you are interested in this feature.
alex. Joakim Berglund wrote: > Yes, that Ive done already. And it works great! > No issues att all. > > But that doesn't handle if you have 2 I/O domains due to redundancy. > > Config: > > # dladm show-aggr > key: 1 (0x0001) policy: L4 address: 0:21:28:1d:1f:70 (auto) > device address speed duplex link > state > nxge0 0:21:28:1d:1f:70 1000 Mbps full up > attached > nxge1 0:21:28:1d:1f:71 1000 Mbps full up > attached > > > VSW > NAME LDOM MAC NET-DEV DEVICE > DEFAULT-VLAN-ID PVID VID MTU MODE > vsw0 primary 00:14:4f:fb:35:53 aggr1 switch at 0 > 78 78 27,48,49 1500 > > VSW > NAME LDOM MAC NET-DEV DEVICE > DEFAULT-VLAN-ID PVID VID MTU MODE > vsw1 secondary 00:14:4f:fa:b6:34 aggr1 switch at 0 > 78 78 27,48,49 1500 > > > NETWORK > NAME SERVICE DEVICE MAC > MODE PVID VID MTU > vnet0 vsw0 at primary network at 0 > 00:14:4f:fa:18:b8 78 1500 > vnet1 vsw1 at secondary network at 1 > 00:14:4f:f8:d9:8b 78 1500 > > > In other words... there is no way to: > > 1) use 802.3ad in the LDOM using vnet0 and vnet1 > 2) construct a vnet "service" consisting of vsw0 and vsw1
