You need to configure BGP on an HPE Aruba Networking switch using AS 65010. What is required when establishing peering with neighboring devices using eBGP AS 65100?
In the study of BGP (Border Gateway Protocol) for AOS-CX, understanding the differences between Internal BGP (iBGP) and External BGP (eBGP) is fundamental to the ACP-S certification.
eBGP Peering Definition: eBGP occurs when two BGP neighbors reside in different Autonomous Systems. In this scenario, the local switch is in AS 65010 and the neighbor is in AS 65100 .
The "Directly Connected" Requirement: By default, BGP assumes that eBGP neighbors are directly connected (physically connected or on the same subnet). This is because eBGP packets are sent with a Time-to-Live (TTL) of 1 . If the neighbor is more than one hop away (for example, peering via loopback interfaces without additional configuration), the packet will expire before reaching the neighbor, and the session will not establish.
Terminology Note: The term " directory connected " in the question is a common typographical error in exam materials for "directly connected." In the context of eBGP peering, being directly connected is the default requirement to ensure the TTL 1 packet reaches the peer. If you were peering with a non-directly connected device, you would need to manually configure ebgp-multihop.
Analysis of Other Options:
Option A: This is incorrect as it uses a random AS number (65001) that does not match the local or neighbor AS provided in the prompt.
Option B:Route Reflectors are a solution used exclusively in iBGP to solve the split-horizon rule (which dictates that a prefix learned from an iBGP peer cannot be advertised to another iBGP peer). Route reflectors are never used for standard eBGP sessions.
Option D: While AOS-CX requires you to enter the address-family ipv4 unicast context to activate a neighbor, the keyword " internal " is not a valid address-family type in the AOS-CX BGP syntax for this purpose.
Key Practice Tip: When configuring BGP on AOS-CX, always remember that after defining the neighbor x.x.x.x remote-as, you must enter the address-family context and use the neighbor x.x.x.x activate command for the session to transition to the " Established " state.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit