What the exam expects
BGP is the single heaviest HCIP topic: peer states, iBGP rules, next hops, route reflection, path attributes and the selection order, and policy with prefix lists, AS_PATH filters and communities.
Peers and next hops
bgp 100, peer 10.0.12.2 as-number 200 creates a peer. iBGP peers usually use loopbacks: peer 3.3.3.3 connect-interface LoopBack0 on both ends, with an IGP route to each loopback. iBGP does not change the next hop learned from eBGP, so the border router uses peer … next-hop-local. An iBGP-learned route is not passed to another iBGP peer: use a full mesh or a route reflector (peer … reflect-client). display bgp peer shows the state; Established is the goal.
Path selection
Huawei compares, in order: preferred value (local), local preference, locally originated routes, AS_PATH length, origin (IGP, EGP, incomplete), MED, eBGP over iBGP, IGP cost to the next hop, cluster list, router ID and peer address.
Policy
A route-policy is read node by node: if-match selects (ip-prefix, acl, as-path-filter, community-filter), apply changes (local-preference, cost/MED, preferred-value, as-path prepend, community). Apply it per peer with peer … route-policy NAME import|export. Communities are tags (AA:NN) a neighbour can act on; Huawei sends them only with peer … advertise-community. The well-known no-export keeps a route inside the receiving AS.
AS_PATH filters
ip as-path-filter uses regular expressions where _ matches a separator or either end: _100$ is “originated in AS 100”, ^200$ is “AS 200’s own routes”.
Commands at a glance
[R1] bgp 100
[R1-bgp] peer 3.3.3.3 as-number 100
[R1-bgp] peer 3.3.3.3 connect-interface LoopBack0
[R1] route-policy TAG permit node 10
[R1-route-policy] apply community 100:1
[R1-bgp] peer 10.0.12.2 advertise-community
<R1> display bgp routing-table community
Not modelled in the simulator: Confederations, aggregation, dampening, peer groups, authentication and BGP4+ are not modelled.