Hi Guys, Sorry for the delay in responding.
It does unwedge itself after about 20 minutes. It seems to wedge once a day for 20 minutes and then recovers. Best Regards, Jason On 5/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On (05/23/07 14:27), Peter Memishian wrote: > > Zone C works fine for about 15-20 hours. After which, it cannot Does it ever recover from the wedged state (e.g., if you wait for 15-20 minutes)? > > connect to any off-subnet addresses. The routing table looks fine and > > still has the correct default route. Zones A and B which are on the > > same subnet as the global zone, don't exhibit this problem at all. > > Neither /var/adm/messages nor dmesg show any errors. > > > > Does anyone have an idea what would cause this? Thank you in advance > > for your help. Any is greatly appreciated. > > Perhaps an instance of 6545032 (which was fixed in b64)? You could check > if this is the case by checking (with DTrace) if the nce_t returned from > ndp_lookup_v4() (via ire_add_v4()) has an nce_state of ND_INITIAL. Could you run the attached nce.d script, and, while it is running, type 'ndd -get /dev/ip ip_ndp_cache_report > /dev/null' in another shell? e.g., # ./nce.d & # ndd -get /dev/ip ip_ndp_cache_report > /dev/null This should give you a list of the nce_t entries, and tell you if you are running into 6545032 (there should be no entries in the ND_INITIAL state). --Sowmini
_______________________________________________ networking-discuss mailing list [email protected]
