Figure 4-25 Teamed port Information tab
Listed below are the possible status conditions with definitions:
• Available – The team member is functioning normally.
• Not Teamed – The adapter is not part of the team. The most likely cause is adding an adapter
to the team but not applying the change.
• Unknown – The team member's status could not be determined.
• Wire Fault – The member does not have link.
• Not Joined – The member cannot be joined in the team because it has an incompatible setting.
The most likely cause is changing a parameter for a team member using the Local Area
Connection property sheet.
• Degraded (Fast Path) – The team member is not receiving BPDUs, and no other team member
is receiving BPDUs. Because all team members have equal Fast Path status, the team member
is still in use by the team.
• Degraded (Active Path) – The team member cannot reach the Echo Node and no other team
member can reach it. Because all team members have equal Active Path status, the team
member is still in use by the team.
• Degraded (Rx Heartbeat) – The team member is not receiving frames and no other team
member is receiving frames. Because all team members are equal, the team member is still
in use by the team.
• Degraded (Multiple) – The team member has multiple degraded conditions.
• Failed (Active Path) – The member is not receiving replies from the configured Echo Node.
• Failed (Split LAN) – The team member is receiving BPDUs from an inferior Root Bridge.
Teaming has determined that team members are connected to different networks.
• Failed (Fast Path) – The team member is not receiving BPDUs.
• Failed (LACP) – The team member failed to establish a LACP channel.
82 The Mechanics of Teaming for the Advanced User
To Next Page
Loading...
Need help?
General