Question 600
During an independent network handover at the Glen Ferry branch of Verde Credit Society, the monitored service is warehouse barcode service for clients in 192.168.84.0/24; incident reference is DC-9113. The on-duty analyst documents this symptom before proposing any configuration: A rack switch failure disconnects every instance of a supposedly redundant application because both nodes use that same rack network. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which ongoing operational check is most relevant to recognizing recurrence of this failure?
Answer and explanations
Monitor spine health and per-leaf ECMP next-hop counts. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A rack switch failure disconnects every instance of a supposedly redundant application because both nodes use that same rack network. This alternative addresses a different issue (leaf spine path diversity). The decisive distinction is: Audit physical dependency maps and test per-rack network failure impacts.
This alternative addresses a different issue (data center ecmp hashing). The option would address: Trend path utilization and flow-key distribution across leaf uplinks. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: A rack switch failure disconnects every instance of a supposedly redundant application because both nodes use that same rack network.
Monitor overlay endpoint reachability, VNI mappings and unexpected tenant leakage. This alternative addresses a different issue (overlay versus underlay reachability). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A rack switch failure disconnects every instance of a supposedly redundant application because both nodes use that same rack network. The decisive distinction is: Audit physical dependency maps and test per-rack network failure impacts.
The on-duty analyst documents this symptom before proposing any configuration: A rack switch failure disconnects every instance of a supposedly redundant application because both nodes use that same rack network. That points to this explanation: Audit physical dependency maps and test per-rack network failure impacts.