Sorry, the main reason I posted this question is because the LDOMs have connectivity issues between them on the SAME VLAN/subnet. RAC pre-install check errors out with "specified network interface doesn't maintain connectivity across cluster nodes". Our Switch people doesn't see any issues on the switch side and they are pointing to LDOM vSwitch.
link aggregation is setup with LACP active with L3 policy. On the control domain plumbing the vsw has no connectivity issues, only in guests. Thanks.
Can you connect to the vsw0 interface on the control domain? I noticed that you haven't assigned a PVID on to the vswitch itself. I had connectivity issues when I set up my vswitches without assigning a pvid.
Also, could you post the specific configurations of vnets for all members of each cluster? I noticed that you assigned different pvids for guest1 and guest2 respectively. What about the other members of each cluster (per your note guest1 and guest2 participate in two separate rac clusters)
Yes, I can connect to the vswitch interface on the control domain. I didn't specify any PVID because my understanding is that PVID will tag any frame with the PVID VLAN by default. basically the PVID for this interface is 1.
Here's the VNET config for the other LDOM in the RAC cluster:
NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw-mgmt 00:14:4f:f9:91:fa igb1 0 switch@0 1 1 1500 on
primary-vsw0 00:14:4f:fa:8e:cf aggr1 1 switch@1 1 1 1501,1601,10,11 1500 on
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet1 primary-vsw-mgmt 0 00:14:4f:fb:65:6d 1
vnetprod primary-vsw0 1 00:14:4f:fa:2b:02 1501
vnethb primary-vsw0 2 00:14:4f:f8:12:c1 10
Thanks for reviewing my configuration.