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.


Be aware that the order of the "ldm add-vnet" commands define the order 
of the network adapters in the Guest LDom


HTH

Bernd


Glen Gunselman wrote:
> I have a working guest LDom on a T5220 with one network connection (we call 
> this the management network, it's using e1000g0).  I need to add a second 
> network connection (we are calling this the public network).
>
> 1.  ifconfig shows the physical interface is ready:
>
> ifconfig -a
> ...
> 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
> ...
>
> 2.  I created the virtual switch
>
> ldm add-vsw net-dev=e1000g1 primary-vsw1 primary
>
> 3.  added the guest domain to the virtual network
>
> ldm add-vnet mac-addr=00:ff:00:ff:01:00  vnet2 primary-vsw1 sweetumstest
>
> 4.  I did forget to do the reconfigure reboot of the control domain but have 
> since done that.
>
> After booting the guest domain ifconfig shows vnet1 is UP and RUNNING
>
> ifconfig -a
> ...
> vnet1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
>         inet nnn.nnn.nnn.149 netmask fffffff8 broadcast nnn.nnn.nnn.151
>         ether 0:ff:0:ff:1:0
> ...
>
> and traceroute picks vnet1 but fails:
>
> traceroute nnn.nnn.nnn.209
> traceroute: Warning: Multiple interfaces found; using nnn.nnn.nnn.149 @ vnet1
> traceroute to nnn.nnn.nnn.209 (nnn.nnn.nnn.209), 30 hops max, 40 byte packets
>
> The same traceroute from the control domain succeeds using e1000g1.
>
> I'm no doubt over looking some simple thing but it escapes me today ... 
>
> Thanks,
> Glen
> --
> This message posted from opensolaris.org
> _______________________________________________
> ldoms-discuss mailing list
> ldoms-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
>
>   


-- 
Bernd Schemmer, Frankfurt am Main, Germany
http://home.arcor.de/bnsmb/index.html

M s temprano que tarde el mundo cambiar .
                        Fidel Castro


Reply via email to