[I've changed the cc line to 'zones-discuss@opensolaris.org', where
issues like this are ordinarily discussed.]

Anand writes:
> We have configured 3 local zones on one of our server and the problem is that ,the local zone's ip get plumbed to different logical interfaces everytime the global zone reboots.

Yes, it does allocate the logical IP interfaces dynamically.

> The local zone tries to get the next available logical interface and depending upon the order the zones comes up it takes up the logical interface.
> Is there any way where we can restrict local zone to use specific logical interface.

Not exactly. If you use an exclusive IP stack instance zone, then you
can have dedicated interfaces, but shared stack zones use logical
interfaces -- which are allocated dynamically.

> Let me know if you my explanation is not clear .

The part that's unclear is why this is a problem. What are you doing
that depends on a logical interface name, and that needs to keep that
name static?

--
James Carlson, Solaris Networking <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677

James Carlson wrote:
>> Let me know if you my explanation is not clear .
>>
>
> The part that's unclear is why this is a problem. What are you doing
> that depends on a logical interface name, and that needs to keep that
> name static?
>

While I can't offer a particular reason, using the zone id for the
logical interface instance would be pretty. Of course, that argument
dies as soon as you ask how to address zones with multiple virtual
interfaces on a single physical NIC.



benr.

Ben Rockwood writes:
> James Carlson wrote:
> >> Let me know if you my explanation is not clear .
> >>
> >
> > The part that's unclear is why this is a problem. What are you doing
> > that depends on a logical interface name, and that needs to keep that
> > name static?
> >
>
> While I can't offer a particular reason, using the zone id for the
> logical interface instance would be pretty.

Maybe. That sounds like something that could be discussed with the
Clearview folks, though I think they're mostly addressing renaming at
the datalink level and not way up at IP's level where logical
interfaces reside.

But what's the "problem" that the original poster was concerned about?
Having more obvious names would be nicer, but you can get the zone
name output in the global zone from ifconfig, so the unobvious names
don't seem to constitute much of a problem ... just rather an
annoyance.

> Of course, that argument
> dies as soon as you ask how to address zones with multiple virtual
> interfaces on a single physical NIC.

You'd need some coherent naming scheme to keep them separate in that
case.

--
James Carlson, Solaris Networking <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677