A technician replaces a failed Management Module in an MX7000 chassis group. After the technician leaves the site, the administrator reports that the lead chassis is no longer able to communicate…

Question

Options

• AView the health status of the lead Chassis Management Module
• BView the health status of the lead Chassis Management ports
• CView the I/O module topology map from the lead chassis
• DView the topology map from the Group Lead

• A
  4% (2)
• B
  77% (36)
• C
  6% (3)
• D
  13% (6)

Explanation

Viewing the health status of the lead Chassis Management ports in OME-M directly surfaces the physical link state of the inter-chassis cabling - if a cable was reconnected incorrectly after the Management Module swap, the affected port will appear as down or degraded, immediately confirming a cabling fault.

Why the distractors are wrong:

• A (Health of the Chassis Management Module): MM health reflects whether the module itself is functional, not whether its cables are seated or routed correctly - a healthy MM can still have miscabled ports.
• C (I/O module topology map): I/O modules handle the data plane (network switching); this view reveals fabric connectivity, not the out-of-band management plane cabling used for chassis group communication.
• D (Topology map from the Group Lead): The group topology map shows the logical membership and arrangement of chassis in the group, but since the member chassis are already unreachable, this view won't render accurately enough to diagnose cabling - you need port-level detail, not a group-level summary.

Memory tip: Match the plane to the problem - inter-chassis management communication breaks are diagnosed via management port health, not I/O/topology views, which live on the data plane.

No community discussion yet for this question.