City planning completes InfiniBand initial configuration with an HA subnet-manager pair. What should operators prove?
Select an answer to reveal the explanation.
Short Explanation
UFM telemetry collection status won't prove your HA subnet-manager databases are synced. Partition key consistency across the fabric also doesn't show whether the standby can take over. Prove the city-planning InfiniBand HA pair keeps its subnet-manager databases synchronized.
Full Explanation
When city planning completes InfiniBand initial configuration with an HA subnet-manager pair, operators must prove subnet manager database synchronization across that pair. HA is not two independent boxes; the standby must hold synchronized SM state so promotion preserves fabric management knowledge. Verifying sync confirms the civic pair can fail over without rebuilding fabric state from ignorance. Checking partition key configuration consistency across the InfiniBand fabric fails to prove HA readiness: matching partition keys do not synchronize SM state, and a standby without synced SM databases cannot promote cleanly. Relying on UFM telemetry collection status across the InfiniBand fabric fails to prove HA readiness: telemetry shows fabric health, not whether subnet-manager databases are synchronized so the standby can take over. Assuming Spectrum EVPN route reflectors sync InfiniBand SM databases fails because EVPN RR behavior is Ethernet control-plane sync, not InfiniBand SM database replication. Exam caveat: candidates confuse "partition key consistency" with "HA is synced," or map Ethernet EVPN mechanisms onto IB SM. Operational check: on the city-planning HA pair, confirm SM databases are synchronized, induce a controlled failover, verify the promoted SM retains fabric management continuity, and restore the pair to master/standby with sync healthy.