Guys,

Yes, the problem seems to be CR 6367840. As long as the IPMP interfaces are in 
FAILED mode non global zones will not boot after configuration.

Have fixed the network and all seems to be fine.

Thanks

Roshan

----- Original Message -----
From: James Carlson <[EMAIL PROTECTED]>
Date: Monday, October 23, 2006 2:41 pm
Subject: Re: [zones-discuss] Zones and VLAN tagging.
To: Mike Gerdts <[EMAIL PROTECTED]>
Cc: Roshan Perera <[EMAIL PROTECTED]>, zones-discuss@opensolaris.org

> Mike Gerdts writes:
> > On 10/23/06, Roshan Perera <[EMAIL PROTECTED]> wrote:
> > > zonecfg:sz44bsdvapdqc02:net> set address=10.165.20.35/23
> > 
> > That should be:
> > 
> > set address=10.165.20.35
> > 
> > You will then need an entry in the global zone's /etc/netmasks to
> > ensure that the netmask is set properly as the zone is booted.
> 
> There's nothing wrong with CIDR notation here.  In fact, I'd recommend
> that users prefer CIDR and shy away from the ancient and feeble
> /etc/netmasks interface.
> 
> See the zonecfg(1M) man page for details.
> 
> That's not the problem the user is seeing.  The problem the user is
> experienced appears to be CR 6367840 -- fixed in Nevada, but not S10.
> 
> -- 
> James Carlson, KISS Network                    
> <[EMAIL PROTECTED]>Sun Microsystems / 1 Network Drive        
> 71.232W   Vox +1 781 442 2084
> MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 
> 442 1677
> 
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to