Hi Mike, James,
Thanks for the replies. As per my mail I thought the problem was to do with the
CR 6367840 as both my interfaces are down. For sec reasons I cannpt bring them
up until the servers are configured and the sec checked. Catch 22..
I might put local network together to get it going for the time being.
Just to ensure I tried set address=10.165.20.35 (without the /23) and still it
I will try with the interfaces up and come back to you.,
As always.. Thanks..
----- Original Message -----
From: James Carlson <[EMAIL PROTECTED]>
Date: Monday, October 23, 2006 2:42 pm
Subject: Re: [zones-discuss] Zones and VLAN tagging.
To: Mike Gerdts <[EMAIL PROTECTED]>
Cc: email@example.com, Roshan Perera <[EMAIL PROTECTED]>
> 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 mailing list