http://defect.opensolaris.org/bz/show_bug.cgi?id=10511
Anurag S. Maskey <Anurag.Maskey at Sun.COM> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ACCEPTED |CAUSEKNOWN
--- Comment #2 from Anurag S. Maskey <Anurag.Maskey at Sun.COM> 2009-08-07
07:31:57 ---
I see the problem. hme0 and hme2 are in the same exclusive priority-group.
hme0 has cable plugged in, but hme2 doesn't.
bash-3.2# dladm show-link
LINK CLASS MTU STATE OVER
hme0 phys 1500 up --
hme1 phys 1500 down --
hme2 phys 1500 down --
hme3 phys 1500 down --
As the links are coming up, hme0 moves to the (online, link up) state, and then
propagates the link up message to the corresponding interface NCU. hme2 moves
to the (offline, link down). Moving to the offline state causes the NCU
priority group check to run for hme2's priority group. (evident in the follow
debug lines)
Aug 6 18:39:46 octagon nwamd[1548]: [ID 331768 daemon.debug] 1:
nwamd_ncu_handle_state_event: changing state for NCU link:hme2 to (offline ,
interface or link is down)
Aug 6 18:39:46 octagon nwamd[1548]: [ID 468884 daemon.debug] 1:
nwamd_ncp_check_priority_group: checking priority group 1
When the priority group is checked, it fails. That's because link:hme0 is
online, but it's corresponding interface:hme0 isn't online yet. It's state
event was just added to the event queue. So, the checking sees this as not
online. hme2 is already offline. So, this priority-group fails and we move on
to the next group.
Why does the Automatic work? The priority check still fails, but because all
NCUs are in the same priority group, no lower priority group NCUs can be
activated and this priority group itself is also not deactivated.
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
