Question 510
The HPE AOS-CX switching case is: A primary peer shows out-of-sync settings and an operator assumes all secondary configurations are identical automatically. Which TWO choices together provide the targeted remedy and independent validation? (Select TWO.)
Explanation
Correct Answers
The targeted correction for A primary peer shows out-of-sync settings and an operator assumes all secondary configurations are identical automatically is: Remediate VSX state only after checking ISL, keepalive, peer roles and configuration synchronization with a documented change plan. It reduces the risk that blindly reloading both peers can turn a recoverable link issue into a complete campus distribution outage.
A separate operational validation for A primary peer shows out-of-sync settings and an operator assumes all secondary configurations are identical automatically is: A single-peer failover and recovery test confirms consistent active gateway and restored VSX operational health. It proves intended behavior instead of accepting configuration presence alone.
Incorrect Answers
This alternative concerns qos congestion remediation using actual queue telemetry; its associated risk is: Changing priority globally based on one poor call can starve critical classes or fail to address an undersized physical uplink. The observed case A primary peer shows out-of-sync settings and an operator assumes all secondary configurations are identical automatically requires the more specific vsx high availability and recovery action sequencing control. The targeted action is: Remediate VSX state only after checking ISL, keepalive, peer roles and configuration synchronization with a documented change plan.
This alternative concerns vsf membership and conductor recovery plan; its associated risk is: Unplanned zeroization or member readdition can erase interface configuration and extend an access outage. The observed case A primary peer shows out-of-sync settings and an operator assumes all secondary configurations are identical automatically requires the more specific vsx high availability and recovery action sequencing control. The targeted action is: Remediate VSX state only after checking ISL, keepalive, peer roles and configuration synchronization with a documented change plan.
This alternative concerns multicast join and routed multicast fault recovery; its associated risk is: Enabling more multicast flooding without diagnosis can overload unrelated VLANs and still fail inter-subnet delivery. The observed case A primary peer shows out-of-sync settings and an operator assumes all secondary configurations are identical automatically requires the more specific vsx high availability and recovery action sequencing control. The targeted action is: Remediate VSX state only after checking ISL, keepalive, peer roles and configuration synchronization with a documented change plan.