> Glen Gunselman wrote: > >> Hi, > >> > >> > >>>> e1000g1: > >>>> > >> flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> > >> mtu 1500 index 3 > >> > >>>> inet nnn.nnn.nnn.129 netmask fffffff8 > >>>> > >> broadcast nnn.nnn.nnn.135 > >> > >>>> ether 0:21:28:1:5e:99 > >>>> > >> plumb and configure the virtual switch vsw > instead > > of the physical > >> network in the primary ldom. > >> > >> After doing this we often must stop the Guest > LDom, > >> unconfigure all > >> network adapters of the Guest LDom, reattach the > >> network adapters to the > >> Guest LDom and start the Guest LDom again to make > the > >> virtual network > >> adapters work. And if you don't have installed the > >> latest patches for > >> LDoms you must configure the virtual switch with > the > >> mac address of the > >> used physical network adapter. > >> > >> > > > > I gave this a try and it did not work, so I > installed LDoms 1.0.3 but that did not help. > > > > When I try to configure using a mac address i get > the following error: > > > > ifconfig vsw1 nnn.nnn.nnn.129 netmask > 255.255.255.248 broadcast nnn.nnn.nnn.135 ether > 0:21:28:1:5e:99 > > ifconfig: failed setting mac address on vsw1 > > > The mac address for vswitch or vnet can only be > changed > via LDom manager CLIs. > > BTW, you can plumb vsw interface with whatever the > mac address > assigned by LDom manager. Only issue you may need to > pay attention is > to deal with ARP caches on other systems. In general, > the GARP packets > generated during the plumb operation should cause a > flush, otherwise, they > get flushed automatically after a timeout(around > 5mins). > > Once you have vsw interface plumbed, I suggest > verifying the communication > between Guest vnet and vsw. This info will provide an > idea where the > problem could be. If this is found to be working, I > suggest running snoop > on vnet1 and ping from an external system, this will > give additional > data point. > > -Raghuram.
Thanks, I'll give up on trying to set the mac address. As far as ping goes, I see the same pattern when pinging from nnn.nnn.nnn.209: ping to nnn.nnn.nnn.129 (to the control domain works) ping to nnn.nnn.nnn.149 (to the guest fails) snoop -Vd vnet0 shows: 164.113.110.149 -> (broadcast) ETHER Type=0806 (ARP), size = 42 bytes 164.113.110.149 -> (broadcast) ARP C Who is 164.113.110.150, 164.113.110.150 ? ________________________________ 164.113.110.131 -> (broadcast) ETHER Type=0806 (ARP), size = 60 bytes 164.113.110.131 -> (broadcast) ARP C Who is 164.113.110.131, 164.113.110.131 ? Thanks, Glen -- This message posted from opensolaris.org
