> I've got a build 63 T2000 set up with three zones. e1000g0 is plumbed > and addressed in the global zone and is used also by local zones A and > B. Both A and B have no routing/networking issues. e1000g1 is plumbed > but not addressed in the global zone. Local zone C uses e1000g1 for > its networking connectivity. I've added a secondary default route in > the global on the same subnet that local zone C is addressed on. Local > zone C uses that secondary default route as its only default route. > > Zone C works fine for about 15-20 hours. After which, it cannot > 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. -- meem _______________________________________________ networking-discuss mailing list [email protected]
