One member of a data-center port-channel is suspended, and its allowed VLAN list does not match the port-channel. The other member is forwarding. Which state explains the suspended member?
Select an answer to reveal the explanation.
Short Explanation
One lane of a two-lane road is closed because you painted it with different rules than the other lane. The bundle suspended that member for not matching. Nobody shut it on purpose, a port-security violation is a different lockout, and fiber does not have a duplex setting that rewrites a VLAN list.
Full Explanation
A port-channel member is suspended when it is not allowed to join the bundle because its configuration does not match, including a mismatched allowed VLAN list. This member's allowed VLANs differ from the port-channel and the other member is forwarding, so the suspended state is that mismatch. Administratively shut is a different state: an operator disabled the port. A suspended member is not the same display as a port that was shut. Error-disabled is the lockout that follows a violation such as port security. A VLAN mismatch on a bundle does not get reported as a port-security violation. Fiber links do not negotiate duplex the way copper does, and a duplex story would not be how you explain a VLAN list that does not match. Exam caveat: suspended means the member is out of the bundle. Fix the mismatch and let it rejoin. Do not treat it like an error-disabled port that needs a different recovery command. Operational check: compare the member's allowed VLANs with the port-channel, make them match, and confirm the member leaves the suspended state and forwards.