Can someone let me know whether a non global zone can have multiple IP
addresses ? If so can it be serviced by
2 NIC's with IPMP running in the global zone. eg: global IP's are
Zone1 to have x.x.x.10 using ce0 and also service x.x.y.20 using ce0:5
I have asked the same question previously (attached below) without any luck
with VLAN tagging but this time I'm trying to simplify the problem. Then I can
get the VLAN tagging working.
I am at customer and customer keen to have this done.
----- Original Message -----
From: Roshan Perera <[EMAIL PROTECTED]>
Date: Monday, November 6, 2006 11:49 am
Subject: Re: [zones-discuss] Zones and VLAN tagging.
> I have VLAN tagging working OK THanks to the James Carlson, Mike
> Gerdts, Steffen Weiberle in particular.
> Now I have a further question and similar help will be muchly
> I have IPMP in 2 interfaces. eg:
> Global Zone IP address 10.10.10.5 (IPMP real)
> ce0 10.10.10.6 (IPMP test)
> ce1 10.10.10.7 (IPMP test)
> zone1 IP 10.10.10.10
> zone2 IP 10.10.10.20
> Currently I have ce610000 and ce610001 configured for the above
> and working OK with zones IP's fine.
> Now I like the Same IPMP interfaces ce0 and ce1 as above to
> service another IP for global and zones. eg:
> 10.10.20.5 for the global zone
> 10.10.20.10 for the zone1
> 10.10.20.20 for the zone2
> I assume this is possible. I tried couple of shots at it. But
> fails. Can someone kindly help./.
> ----- Original Message -----
> From: Roshan Perera <[EMAIL PROTECTED]>
> Date: Monday, October 23, 2006 5:18 pm
> Subject: Re: [zones-discuss] Zones and VLAN tagging.
> To: James Carlson <[EMAIL PROTECTED]>
> Cc: email@example.com
> > 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
> > 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-
> > [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
> > 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
> > > 442 1677
> > >
> > _______________________________________________
> > zones-discuss mailing list
> > firstname.lastname@example.org
> zones-discuss mailing list
zones-discuss mailing list