D-PEMX-DY-23 · Question #74
While servicing an MX7000 chassis a system administrator logs into OME-M and receives a Chassis Mismatch error. What should be the next step taken by the administrator?
The correct answer is D. Force Active/Clear configuration. Force Active/Clear configuration (D) is the correct resolution because a Chassis Mismatch error in OME-M on the MX7000 indicates a configuration conflict between the Lead and Standby Management Modules - forcing the active MM to assert authority and clearing the mismatched…
Question
While servicing an MX7000 chassis a system administrator logs into OME-M and receives a Chassis Mismatch error. What should be the next step taken by the administrator?
Options
- AClear the configuration
- BReset Peer or the Local IOM
- CPerform firmware update
- DForce Active/Clear configuration
How the community answered
(36 responses)- A3% (1)
- B6% (2)
- C11% (4)
- D81% (29)
Explanation
Force Active/Clear configuration (D) is the correct resolution because a Chassis Mismatch error in OME-M on the MX7000 indicates a configuration conflict between the Lead and Standby Management Modules - forcing the active MM to assert authority and clearing the mismatched configuration resolves the inconsistency and restores a clean, authoritative chassis state.
Why the distractors are wrong:
- (A) Clear the configuration is too destructive and non-targeted; it doesn't resolve the authority conflict between modules.
- (B) Reset Peer or Local IOM addresses Input/Output Module problems, not a Management Module configuration mismatch.
- (C) Perform firmware update resolves version incompatibilities, not configuration conflicts - and running updates during an unresolved mismatch can make things worse.
Memory tip: Think of a Chassis Mismatch as two managers disagreeing over who's in charge. "Force Active" is like HR stepping in and saying "the Lead MM wins - everyone else, clear your desk and follow the new rules."
Topics
Community Discussion
No community discussion yet for this question.