Configuring vSwitch following a S10U4 (08/07) upgrade

With the release of Solaris 10 8/07 (aka S10U4), support was added to Solaris and the LDoms vSwitch for improved packet processing. The LDoms vSwitch can now program the MAC addresses of each vNet into the physical adapter, instead of configuring the shared physical adapter in promiscuous mode. An bug was introduced when adding this support to the LDoms vSwitch driver. When plumbed as a network device, the new vSwitch fails to program its own MAC address into the adapter, and hence cannot receive any packets destined for it from the external network.

In order to enable networking between the domains and the service domain, the LDoms 1.0 Admin guide (pg 42) recommends users to unplumb the physical adapter; and plumb the vSwitch instead. In order for this to function correctly, the LDoms vSwitch will need to be assigned the same MAC address as that of the physical adapter. This workaround is only necessary when the vSwitch is plumbed as a network device, and enable it to receive packets from the external network. A patch to address this issue is in the works and will be released soon.

The issue is also documented in the LDoms 1.0.1 release notes.

Comments:

I am using Sol10U4, and I find that even if I plumb the vsw0 as the network device, I still need to snoop the underlying bge0 in order for the vsw0 to relay packets from the physical network to the vnet\* in the guest ldom.

Is this related? Or something different?

Posted by Jeff Chan on September 27, 2007 at 12:17 PM EDT #

This the same problem. By snooping the underlying adapter, you are forcing the adapter to switch into promiscuous mode. That causes it to pick up all packets including the ones destined for the vSwitch.

-Narayan

Posted by Narayan Venkat on September 27, 2007 at 03:31 PM EDT #

There is another interesing issue, I think, in connection with your topic.
I've got T2000 with 4 ethernet ports. There are 2 domains - primary and logical. I want to attach one of the ethernet ports directly to logical domain, e100g2 exactly.
e100g0 MAC: 0:14:4f:95:1e:42
so I've created
Vsw: primary-vsw1 [num_clients=1]
mac-addr=0:14:4f:95:1e:42
net-dev=e1000g2
mode=prog,promisc
in the primary domain
and attached this service:
Vnet: sunrise-network1
mac-addr=0:14:4f:fa:a7:36
service: primary-vsw1 @ primary
When I reboot primary domain (together with logical, of course),
everything is ok - domains come up and I can ping logical domain
from external physical network
When I reboot logical domain, after it comes up all the pings and
network connections to it stop working - I cannot access logical domain from ext. network anymore. The only way to solve this problem via rebooting primary domain.

Solaris 10 11/06 patched with 118833-36, 124921-02, 125382-01

Any advice ?

Tnanks.

Posted by sol on September 27, 2007 at 11:05 PM EDT #

The fix for this bug (6530331) is in available in 127111-05, once you have that patch installed there is no requirement for the vSwitch to be assigned the same MAC address as that of the physical adapter in order for guest networking to function correctly.

Posted by Liam Merwick on January 08, 2008 at 10:50 PM EST #

[Trackback] There have been a number of LDoms fixes backported to S10 since Solaris 10 8/07 (S10U4) was released[\*]. They are available in the S10 Sustaining KU, 127111 and can be applied to Solaris 10 8/07 (S10U4) or Solaris 10 11/06 (S10U3). In fact, instead of ...

Posted by Liam Merwick's Weblog on January 08, 2008 at 11:37 PM EST #

united=6
states=6
of america=9=6
666

Posted by tecnesio on August 28, 2008 at 07:33 AM EDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Narayan Venkat

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today