HPE7-A06 · Question #26
You are troubleshooting a network issue on a VSX cluster. The network was functioning properly yesterday but today the network operations center is receiving alerts. On one of the two VSX members, a…
The correct answer is A. LAGs were disabled because a split-brain condition was detected. In VSX, if the keepalive link goes down and the system detects a possible split-brain condition (both peers thinking they are primary), the secondary switch will bring down all VSX LAGs and report them as "down by feature" to prevent loops. This matches the described condition.
Question
You are troubleshooting a network issue on a VSX cluster. The network was functioning properly yesterday but today the network operations center is receiving alerts. On one of the two VSX members, a ‘show interface brief’ indicated that all VSX LAGs are “down by feature”. What could be the cause of this condition?
Options
- ALAGs were disabled because a split-brain condition was detected.
- BBoth VSX members are configurated as Primary.
- CVSX has detected a firmware version mismatch.
- DVSX-sync is not enabled on the cluster.
How the community answered
(38 responses)- A84% (32)
- B3% (1)
- C3% (1)
- D11% (4)
Explanation
In VSX, if the keepalive link goes down and the system detects a possible split-brain condition (both peers thinking they are primary), the secondary switch will bring down all VSX LAGs and report them as "down by feature" to prevent loops. This matches the described condition.
Topics
Community Discussion
No community discussion yet for this question.