Prev: WARNING: Page83 data not standards compliant EMC SYMMETRIX 5771
Next: boot time executables and shared libs
From: thiin_white_duke on 3 Apr 2008 15:30
We have a most interesting problem. When we boot our global zones
some of the non global zones don't come up on the network. We don't
know why. For some reason one or two will, but the third won't and
it's on the same network as the other two. This just started
happening.

We think it might be NIS+ related on the globals, but aren't sure.
Any idea why one or two zones would start their network services but
the other won't?
From: Wolfgang on 3 Apr 2008 18:35
thiin_white_duke(a)yahoo.com schrieb:
> We have a most interesting problem. When we boot our global zones
> some of the non global zones don't come up on the network. We don't
> know why. For some reason one or two will, but the third won't and
> it's on the same network as the other two. This just started
> happening.
>
> We think it might be NIS+ related on the globals, but aren't sure.
> Any idea why one or two zones would start their network services but
> the other won't?

what are the errors exactly, what mean "dont come up on the network"?
have you different subnets on global and local zones?
do you use shared or exlusive IF? Are the zone IF plumbed and up?
Can you do a zlogin?
From: thiin_white_duke on 5 Apr 2008 08:34
Yes, the zones are all on the same subnet. When the zone booted, it
plumbed the interface on the global, but we couldn't ping our or in to
the zone. Yes, we could zlogin to the zone just fine. Somehow we got
one of them working. We refreshed the cache on the global and zone
with nis_cachmgr -i and wound up rebuilding nis+ on the global.
Somewhere, we don't know where, we got one of the zones working. But
then for no apparant reason, one of the zones that was working stopped
working!

I don't understand the interdependency on how the non-global zone
plumbs the interface on the global. If I knew how that all worked I
might have more of a clue on what the problem is. By the way, this
all was working for a while, but just stopped without an real
interference. Which leads to either a corruption of something (don't
know what) or a bug of some sort.

On Apr 3, 6:35 pm, Wolfgang <wtra...(a)AT.web.de> wrote:
> thiin_white_d...(a)yahoo.com schrieb:
>
> > We have a most interesting problem.  When we boot our global zones
> > some of the non global zones don't come up on the network.  We don't
> > know why.  For some reason one or two will, but the third won't and
> > it's on the same network as the other two.  This just started
> > happening.
>
> > We think it might be NIS+ related on the globals, but aren't sure.
> > Any idea why one or two zones would start their network services but
> > the other won't?
>
> what are the errors exactly, what mean "dont come up on the network"?
> have you different subnets on global and local zones?
> do you use shared or exlusive IF? Are the zone IF plumbed and up?
> Can you do a zlogin?

From: Wolfgang on 5 Apr 2008 18:33
thiin_white_duke(a)yahoo.com schrieb:
> Yes, the zones are all on the same subnet. When the zone booted, it
> plumbed the interface on the global, but we couldn't ping our or in to
> the zone. Yes, we could zlogin to the zone just fine. Somehow we got
> one of them working. We refreshed the cache on the global and zone
> with nis_cachmgr -i and wound up rebuilding nis+ on the global.
> Somewhere, we don't know where, we got one of the zones working. But
> then for no apparant reason, one of the zones that was working stopped
> working!
>
> I don't understand the interdependency on how the non-global zone
> plumbs the interface on the global. If I knew how that all worked I
> might have more of a clue on what the problem is. By the way, this
> all was working for a while, but just stopped without an real
> interference. Which leads to either a corruption of something (don't
> know what) or a bug of some sort.
>
> On Apr 3, 6:35 pm, Wolfgang <wtra...(a)AT.web.de> wrote:
>> thiin_white_d...(a)yahoo.com schrieb:
>>
>>> We have a most interesting problem. When we boot our global zones
>>> some of the non global zones don't come up on the network. We don't
>>> know why. For some reason one or two will, but the third won't and
>>> it's on the same network as the other two. This just started
>>> happening.
>>> We think it might be NIS+ related on the globals, but aren't sure.
>>> Any idea why one or two zones would start their network services but
>>> the other won't?
>> what are the errors exactly, what mean "dont come up on the network"?
>> have you different subnets on global and local zones?
>> do you use shared or exlusive IF? Are the zone IF plumbed and up?
>> Can you do a zlogin?
>

We had a similar problem with Zones under Veritas, Bug ID 6633378
which is solved with patch 137050-01, maybe the same reason.
From: Horst Scheuermann on 7 Apr 2008 10:37
thiin_white_duke(a)yahoo.com writes:

> We have a most interesting problem. When we boot our global zones
> some of the non global zones don't come up on the network. We don't
> know why. For some reason one or two will, but the third won't and
> it's on the same network as the other two. This just started
> happening.

> We think it might be NIS+ related on the globals, but aren't sure.
> Any idea why one or two zones would start their network services but
> the other won't?

do these zone use the nic exclusive?
--
Gummileinen nur f�r Gummihunde!
 | 
Pages: 1
Prev: WARNING: Page83 data not standards compliant EMC SYMMETRIX 5771
Next: boot time executables and shared libs