While troubleshooting EoMPLS configuration problems, which three parameters should an engineer match between the two ends of the pseudowire configurations? (Choose three.)

Question

Options

• AVLAN name
• BXconnect group name
• CEFP subinterface number
• Dpseudowire ID
• EMTU size
• Fcontrol word usage

• A
  13% (5)
• B
  8% (3)
• C
  3% (1)
• D
  77% (30)

Explanation

In EoMPLS, a pseudowire is a point-to-point Layer 2 tunnel between two PE routers, and both endpoints must agree on three key parameters for the pseudowire to come up: the pseudowire ID (D) identifies and binds the two ends together - a mismatch means the routers won't recognize each other as peers; the MTU size (E) must match because both sides must agree on the maximum frame size they'll transport, or the session fails to establish; and control word usage (F) must be consistent since the control word is an optional 4-byte header that both ends must either use or not use, otherwise the receiving end misinterprets the encapsulation.

The distractors are wrong because they are locally significant - the VLAN name (A) is just a local label with no meaning to the remote PE; the Xconnect group name (B) is a local organizational label only; and the EFP subinterface number (C) is a local interface reference, with the pseudowire ID doing the actual remote binding.

Memory tip: Think "PIM C" - Pseudowire ID, MTU, Control word - these three must match or the pseudowire is "PIMC'd" (stuck). Everything else (names, interface numbers) is local and irrelevant to the remote end.

No community discussion yet for this question.