[zones-discuss] Shared-ip routing and VNI interface

2007-12-03 Thread Paul Van Der Zwan
I'm having a problem figuring out why my ping replies never get sent. I have a Blade 1500 running Solaris 10 08/07 On it I have 2 active local zones, zone1 and zone2, their configs are: # zonecfg -z zone1 export create -b set zonepath=/zones/zone1 set autoboot=false set ip-type=shared add

Re: [zones-discuss] Shared-ip routing and VNI interface

2007-12-03 Thread Chris Zhu
Paul, Have you done zlogin -C zonename, it will initialize the zone environment including the network. Chris Paul Van Der Zwan wrote: I'm having a problem figuring out why my ping replies never get sent. I have a Blade 1500 running Solaris 10 08/07 On it I have 2 active local zones,

Re: [zones-discuss] Shared-ip routing and VNI interface

2007-12-03 Thread James Carlson
Paul Van Der Zwan writes: I'm having a problem figuring out why my ping replies never get sent. There's no way for any of your configured zones to transmit, so they don't. Vni is really not much different from lo0. You cannot transmit packets on vni -- it's just a place to hang a local IP

Re: [zones-discuss] Shared-ip routing and VNI interface

2007-12-03 Thread Paul van der Zwan
On 3 Dec 2007, at 12:49, James Carlson wrote: Paul Van Der Zwan writes: I'm having a problem figuring out why my ping replies never get sent. There's no way for any of your configured zones to transmit, so they don't. Vni is really not much different from lo0. You cannot transmit packets

Re: [zones-discuss] Shared-ip routing and VNI interface

2007-12-03 Thread James Carlson
Paul van der Zwan writes: service address=10.1.1.1 default gateway=192.168.1.254 zone1 on host1 has 192.168.1.1 on bge0 and 10.1.1.1 on vni0 zone1 on host2 has 192.168.1.2 on bge0 and 10.1.1.1 on vni0 That looks like a variant on the original design target for vni, so I'd expect it to work.

Re: [zones-discuss] Shared-ip routing and VNI interface

2007-11-30 Thread sowmini . varadhan
On (11/30/07 08:25), Mike Gerdts wrote: The 10.1.1.100 address must not be reachable. The last time I tried this in Nevada it causes a panic. The last time I tried it on S10 it causes one kernel thread to spin (mpstat will show one CPU at 100% sys). Through bugs.opensolaris.org I opened a