A remote operation center is deploying a set of l-BGP and E-BGP connections for multiple IOS- XR platforms using the same template. The l-BGP sessions exchange prefixes with no apparent issues, but…

Question

Exhibit

Options

• AA PASS ALL policy has not been implemented for the l-BGP neighbors.
• BThe next-hop-self command is not implemented on both E-BGP neighbors.
• CThe E-BGP neighbors are not allowed to exchange information due to the customer platforms
• DThe l-BGP neighbors are mistyped and HELLO packets cannot be exchanged successfully

• A
  14% (3)
• B
  5% (1)
• C
  71% (15)
• D
  10% (2)

Explanation

On Cisco IOS XR, eBGP neighbors have a strict requirement for explicit inbound and outbound routing policies. When the same template is used for both iBGP and eBGP, the iBGP sessions may work because IOS XR applies more lenient defaults for iBGP or the template satisfies iBGP requirements. However, eBGP sessions on IOS XR will not exchange routes without explicitly applied route policies for both directions. The 'customer platforms' reference in option C points to the IOS XR platform-specific enforcement that blocks eBGP route exchange without proper policy configuration. Options A and D are incorrect because iBGP is working fine. Option B (next-hop-self) would affect reachability, not the ability to exchange routes entirely.

No community discussion yet for this question.