IPv4 Routing Lab: Advanced IGP and BGP

Features (Sections 1.1 and 1.2)

This guide covers the IPv4 Routing lab from the HCIE-Datacom Lab Guide, divided into two
sections: Advanced IGP Features (1.1) and Advanced BGP Features (1.2). The lab configures
OSPF and IS-IS for IGP, enhances OSPF with FRR, BFD, and route filtering, and implements
BGP with routing policies, security features, and ORF. The guide includes step-by-step
configurations, verification commands, core concepts, and quiz answers.

Section 1.1: Advanced IGP Features

Overview

Objectives

• Configure OSPF Fast Reroute (FRR) and Bidirectional Forwarding Detection (BFD)
to speed up OSPF convergence.
• Adjust OSPF interface costs to prioritize higher-bandwidth paths.
• Implement inter-area route filtering to reduce the OSPF Link State Database (LSDB).
• Advertise a default route via IS-IS.

Network Topology

• Devices: PE1, PE2, PE3, PE4, P1, P2.

• Interfaces:
o Interconnection interfaces use IPv4 addresses in the format 10.0.0.Y/30 (e.g.,
[Link]/30).
• Loopback0: Each device has a Loopback0 interface with an IPv4 address 10.0.X.X/32
(e.g., PE1: [Link]/32).
• Routing Protocols:
o OSPF (process ID 1, area 0): PE1, PE2, P1, P2 (Loopback0 and interconnection
interfaces); P1 and PE3 (area 1 for interconnection and PE3’s Loopback0).
o IS-IS (process ID 1, area 49.0001): PE3 (Level-1-2), PE4 (Level-1).
• Tasks:
o Adjust OSPF costs to prefer PE2-to-P1 traffic via PE1.
o Enable OSPF IP FRR on PE2 for a backup route to P1’s Loopback0.
o Enable BFD in OSPF area 0 for faster convergence.
o Filter inter-area routes on P1 to exclude PE3’s Loopback3 from area 0.
o Advertise a default route in IS-IS on PE3.

IP Address Planning
 Loopback0
Device Interconnection Interfaces (IPv4)
IPv4
PE1 [Link]/32 GE0/5/0: [Link]/30 (to PE2), GE0/5/1: [Link]/30 (to P1)
PE2 [Link]/32 GE0/5/0: [Link]/30 (to PE1), GE0/5/1: [Link]/30 (to P2)
PE3 [Link]/32 GE0/5/0: [Link]/30 (to PE4), GE0/5/1: [Link]/30 (to P1)
PE4 [Link]/32 GE0/5/0: [Link]/30 (to PE3)
GE0/5/0: [Link]/30 (to P2), GE0/5/1: [Link]/30 (to PE1), GE0/5/2:
P1 [Link]/32
[Link]/30 (to PE3)
P2 [Link]/32 GE0/5/0: [Link]/30 (to P1), GE0/5/1: [Link]/30 (to PE2)

Simplified Explanation: The network is like a city road system where OSPF and IS-IS are GPS
apps mapping routes. FRR provides a detour for quick rerouting, BFD is a traffic monitor
detecting roadblocks instantly, and route filtering is a gatekeeper controlling which roads are
advertised.

Core Concepts

• OSPF: Link-state IGP using areas (0 and 1) to organize the network.

• IS-IS: Link-state IGP with Level-1 and Level-1-2 routers in area 49.0001.
• FRR: Fast Reroute precomputes backup paths to reduce failover time.
• BFD: Bidirectional Forwarding Detection monitors link status for rapid failure detection.
• OSPF Cost: Metric influencing path selection; lower cost is preferred.
• Inter-Area Filtering: Controls Type-3 LSAs on ABRs to limit routes between areas.
• Default Route: Advertised in IS-IS to simulate a network egress.
• DCN and PnP: Data Communication Network (DCN) and Plug-and-Play (PnP) are
disabled for simplicity.
• Immediate Validation: Ensures configuration changes apply instantly.

Analogy: OSPF is a GPS mapping main roads, IS-IS maps side streets, FRR plans detours, BFD
is a speed camera, and filtering is a toll booth restricting access.

Configuration Roadmap

1. Basic Setup: Configure IPv4 addresses, disable DCN/PnP, set immediate validation.
2. OSPF: Deploy OSPF on PE1, PE2, P1, P2 (area 0), and P1, PE3 (area 1).
3. IS-IS: Configure IS-IS on PE3 (Level-1-2) and PE4 (Level-1).
4. OSPF Cost and FRR: Adjust OSPF cost on PE2-P2 link and enable FRR on PE2.
5. BFD for OSPF: Enable BFD in area 0 and test convergence.
6. Route Limitation: Create Loopback2/3, limit equal-cost routes on P1, and filter PE3’s
Loopback3.
 7. IS-IS Default Route: Advertise default route on PE3.
8. Verification: Check routing tables and test connectivity.

Key Commands

Basic Setup

• system-view immediately: Enable immediate validation.

• undo dcn: Disable DCN globally.
• undo pnp enable: Disable Plug-and-Play.
• interface <type><number>: Enter interface configuration.
• ip address <address> <mask>: Assign IPv4 address (e.g., ip address [Link] 30).
• ping <destination>: Test connectivity.

OSPF

• ospf <process-id> router-id <id>: Start OSPF (e.g., ospf 1 router-id [Link]).
• area <area-id>: Configure OSPF area (e.g., area 0).
• interface <type><number>: Enter interface configuration.
• ospf enable <process-id> area <area-id>: Enable OSPF.
• ospf cost <value>: Set interface cost (e.g., ospf cost 2).
• display ospf peer brief: Verify neighbors.
• display ospf routing: Check routing table.

IS-IS

• isis <process-id>: Start IS-IS process (e.g., isis 1).

• is-level <level>: Set router level (e.g., is-level level-1-2).
• network-entity <net>: Set NET address (e.g., network-entity
49.0001.0000.0000.0003.00).
• interface <type><number>: Enter interface configuration.
• isis enable <process-id>: Enable IS-IS.
• display isis peer: Verify neighbors.
• display isis route: Check routing table.

OSPF FRR

• ospf <process-id>: Enter OSPF process.

• frr: Enable FRR.
• loop-free-alternate: Enable Loop-Free Alternate (LFA) FRR.
• display ospf routing <destination>: Check primary and backup routes.

BFD for OSPF

 • bfd: Enable BFD globally.
• ospf <process-id>: Enter OSPF process.
• bfd all-interfaces enable: Enable BFD for OSPF.
• interface <type><number>: Enter interface configuration.
• ospf bfd enable: Enable BFD on interface.
• ospf bfd min-tx-interval <value> min-rx-interval <value> detect-multiplier <value>: Set
BFD parameters (e.g., 500 500 3).
• display ospf bfd session all: Check BFD session status.

Route Limitation

• interface LoopBack<number>: Create loopback interface.

• ip address <address> <mask>: Assign IP address.
• ospf enable <process-id> area <area-id>: Enable OSPF.
• ospf network-type broadcast: Set interface type to broadcast.
• ospf <process-id>: Enter OSPF process.
• maximum load-balancing <value>: Limit equal-cost routes (e.g., maximum load-
balancing 1).
• ip ip-prefix <name> index <number> permit <prefix> <length>: Create IP prefix list.
• filter ip-prefix <name> export: Filter inter-area routes.
• display ospf routing: Check routing table.

IS-IS Default Route

• isis <process-id>: Enter IS-IS process.

• default-route-advertise: Advertise default route.
• display isis lsdb: Check Link-State Database (LSDB).

Verification

• display ospf routing: Check OSPF routes.

• display isis route: Check IS-IS routes.
• display ospf bfd session <interface>: Check BFD session status.
• tracert <destination>: Trace traffic path.

Configuration Framework

Step 1: Basic Device Configuration

• Tasks:
o Set immediate validation, disable DCN/PnP.
o Configure IPv4 addresses for Loopback0 and interconnection interfaces.
• Example (PE2):
 bash

Copy

system-view immediately

undo dcn

undo pnp enable

interface LoopBack0

ip address [Link] 32

interface GigabitEthernet0/5/0

ip address [Link] 30

interface GigabitEthernet0/5/1

ip address [Link] 30

• Verification:
o Test connectivity: ping [Link] (PE2 to P2; 0% packet loss).

Step 2: Deploy OSPF

• Tasks:
o Configure OSPF (process 1, router ID as Loopback0) on PE1, PE2, P1, P2 (area
0), and P1, PE3 (area 1).
o Enable OSPF on Loopback0 and interconnection interfaces.
• Example (PE2):

bash

Copy

ospf 1 router-id [Link]

area 0

interface LoopBack0
 ospf enable 1 area 0

interface GigabitEthernet0/5/0

ospf enable 1 area 0

interface GigabitEthernet0/5/1

ospf enable 1 area 0

• Verification:
o Check neighbors: display ospf peer brief (PE2 shows Full with PE1, P2).
o Check routes: display ospf routing (PE2 learns [Link]/32, [Link]/32).

Step 3: Deploy IS-IS

• Tasks:
o Configure IS-IS (process 1, area 49.0001) on PE3 (Level-1-2) and PE4 (Level-1).
o Enable IS-IS on relevant interfaces.
• Example (PE3):

bash

Copy

isis 1

is-level level-1-2

network-entity 49.0001.0000.0000.0003.00

interface GigabitEthernet0/5/0

isis enable 1

• Verification:
o Check neighbors: display isis peer (PE3 shows PE4 in Up state).
o Check routes: display isis route (PE3 learns [Link]/32).

Step 4: Adjust OSPF Cost and Enable FRR

• Tasks:
o Set OSPF cost on PE2’s GE0/5/1 (to P2) to 2, preferring PE1 (cost 1).
 Enable OSPF IP FRR on PE2 for a backup route to P1’s Loopback0.
o
• Example (PE2):

bash

Copy

interface GigabitEthernet0/5/1

ospf cost 2

ospf 1

frr

loop-free-alternate

• Verification:
o Check route: display ospf routing [Link] 32 (Primary next-hop [Link] (PE1),
backup [Link] (P2)).

Step 5: Configure BFD for OSPF

• Tasks:
o
Enable BFD globally and for OSPF area 0.
o
Configure BFD on interconnection interfaces (500ms intervals, multiplier 3).
Test BFD failure by filtering packets on PE2’s GE0/5/0.
o
• Example (PE2):

bash

Copy

bfd

ospf 1

bfd all-interfaces enable

interface GigabitEthernet0/5/0

ospf bfd enable

 ospf bfd min-tx-interval 500 min-rx-interval 500 detect-multiplier 3

interface GigabitEthernet0/5/1

ospf bfd enable

ospf bfd min-tx-interval 500 min-rx-interval 500 detect-multiplier 3

acl number 3000

rule 1 permit udp destination-port eq 3784

traffic classifier bfd operator or

if-match acl 3000

traffic behavior bfd

deny

traffic policy bfd

classifier bfd behavior bfd

interface GigabitEthernet0/5/0

traffic-policy bfd inbound

• Verification:
o Check BFD: display ospf bfd session all (GE0/5/0 Down, others Up).
o Check OSPF route: display ospf routing (Route to [Link]/32 via [Link] after
BFD failure).
o Undo policy: undo traffic-policy bfd inbound (Restores neighbor relationship).

Step 6: Configure OSPF Route Limitation

• Tasks:
o Create Loopback2 on PE1, P2 ([Link]/32) and enable OSPF.
o Limit equal-cost routes on P1 to 1.
o Create Loopback3 on PE3 ([Link]/24), set to broadcast, and filter on P1.
• Example (PE1):
 bash

Copy

interface LoopBack2

ip address [Link] 32

ospf enable 1 area 0

• Example (P1):

bash

Copy

ospf 1

maximum load-balancing 1

ip ip-prefix abr_filter index 10 permit [Link] 24

ospf 1

area 1

filter ip-prefix abr_filter export

• Verification:
o Check routes: display ospf routing (P1 shows one route to [Link]/32, no
[Link]/24 in area 0).

Step 7: Advertise IS-IS Default Route

• Tasks:
o Advertise default route in IS-IS on PE3.
• Example (PE3):

bash

Copy

isis 1
 default-route-advertise

• Verification:
o Check LSDB: display isis lsdb (PE3’s LSP includes [Link]/0).

Quiz Answer (1.1.3)

OSPF inter-area routes can be filtered by running the filter ip-prefix ip-prefix-name export
command on an ABR, but intra-area routes cannot be filtered by running the command in
an OSPF area. Why?

Answer: OSPF inter-area routes can be filtered using the filter ip-prefix command on an Area
Border Router (ABR) because it controls Type-3 Link-State Advertisements (LSAs) generated
during inter-area route summarization. Intra-area routes cannot be filtered this way because they
are advertised via Type-1 and Type-2 LSAs, which are flooded within an area and not subject to
ABR filtering.

Explanation:

• Inter-Area Routes: These are advertised as Type-3 LSAs by ABRs (e.g., P1) when
routes from one area (e.g., area 1) are injected into another (e.g., area 0). The filter ip-
prefix export command on the ABR filters these LSAs, preventing specific routes (e.g.,
[Link]/24) from being advertised to area 0.
• Intra-Area Routes: These are advertised via Type-1 (Router) and Type-2 (Network)
LSAs, which are flooded to all routers within the same area (e.g., area 0). OSPF’s link-
state nature ensures all routers in an area maintain an identical LSDB, and the filter ip-
prefix command cannot block these LSAs within an area without breaking OSPF’s
consistency.
• Technical Detail: The filter ip-prefix export command applies to Type-3 LSA generation
at the ABR, not to intra-area flooding of Type-1/Type-2 LSAs, which are mandatory for
OSPF’s Shortest Path First (SPF) calculation.

Simplified Analogy: Inter-area routes are like letters sent between cities, which a post office
(ABR) can filter. Intra-area routes are like local newspapers distributed to every house in a city,
which can’t be selectively blocked without disrupting the entire delivery system.

Section 1.2: Advanced BGP Features

Overview

Objectives
 • Configure BGP routing policies to control route advertisement.
• Implement BGP security with GTSM and authentication.
• Configure Outbound Route Filtering (ORF) to limit received routes.

Network Topology

• Devices: PE1, PE2, PE3, PE4, P1, P2.

• Roles:
o Backbone: P2, PE2, PE4 (AS 65100, OSPF area 0).
o Headquarters: P1 (AS 65003).
o Branches: PE1 (AS 65001), PE3 (AS 65002).
• Interfaces: Same as Section 1.1 for interconnection and Loopback0.
• Loopback1/2: Simulate service networks (OA: 10.1.X.X/32, Finance: 10.2.X.X/32).
• Routing Protocols:
o OSPF: Backbone (P2, PE2, PE4) for IGP.
o BGP:
▪ EBGP: Between P1-P2, PE1-PE2, PE3-PE4.
▪ IBGP: Within AS 65100 (P2 as Route Reflector, PE2/PE4 as clients).
• Tasks:
o Configure OSPF in the backbone.
o Deploy EBGP with GTSM and authentication.
o Configure IBGP with P2 as RR.
o Advertise service routes with community attributes.
o Use routing policies to restrict Loopback2 routes to headquarters.
o Implement ORF to filter unplanned routes.

IP Address Planning

Loopback0 Loopback1 Loopback2

Device Interconnection Interfaces (IPv4)
IPv4 IPv4 IPv4
PE1 [Link]/32 [Link]/32 [Link]/32 GE0/5/0: [Link]/30 (to PE2)
GE0/5/0: [Link]/30 (to PE1), GE0/5/1:
PE2 [Link]/32 - -
[Link]/30 (to P2)
PE3 [Link]/32 [Link]/32 [Link]/32 GE0/5/0: [Link]/30 (to PE4)
GE0/5/0: [Link]/30 (to PE3), GE0/5/1:
PE4 [Link]/32 - -
[Link]/30 (to P2)
P1 [Link]/32 [Link]/32 [Link]/32 GE0/5/0: [Link]/30 (to P2)
GE0/5/0: [Link]/30 (to P1), GE0/5/1:
P2 [Link]/32 - - [Link]/30 (to PE2), GE0/5/2:
[Link]/30 (to PE4)

Simplified Explanation: The backbone is like a highway system (OSPF), BGP is a courier
service delivering addresses between cities (ASes), and routing policies are customs checkpoints
controlling which packages (routes) cross borders.
Core Concepts

• BGP: Border Gateway Protocol for inter-AS routing.

• EBGP: External BGP between different ASes.
• IBGP: Internal BGP within AS 65100, with P2 as Route Reflector.
• GTSM: Generalized TTL Security Mechanism sets TTL to 255 to prevent spoofing.
• BGP Authentication: Uses a password (e.g., Huawei@123) for peer security.
• Community Attribute: Tags routes (e.g., AS:01) for policy application.
• Routing Policy: Controls route advertisement using community and AS-Path filters.
• ORF: Outbound Route Filtering allows P1 to specify which routes P2 sends.
• Route Reflector: Simplifies IBGP peering by reflecting routes.

Analogy: BGP is a global courier, GTSM checks package authenticity, authentication is a

password lock, and ORF is a delivery filter ensuring only requested items are sent.

Configuration Roadmap

1. Basic Setup: Configure IPv4 addresses, disable DCN/PnP, set immediate validation.
2. OSPF: Deploy OSPF in backbone (P2, PE2, PE4).
3. EBGP: Configure EBGP with GTSM and authentication.
4. IBGP: Deploy IBGP with P2 as RR and peer group.
5. Service Routes: Create Loopback1/2 and advertise with community attributes.
6. Routing Policies: Restrict Loopback2 routes to headquarters.
7. ORF: Filter unplanned routes on P1.
8. Verification: Check BGP routing tables and test connectivity.

Key Commands

OSPF

• Same as Section 1.1.

BGP

• bgp <as>: Start BGP process (e.g., bgp 65100).

• router-id <id>: Set router ID (e.g., router-id [Link]).
• peer <ip> as-number <as>: Configure peer (e.g., peer [Link] as-number 65100).
• peer <ip> connect-interface LoopBack0: Set peering source.
• peer <ip> password cipher <password>: Set authentication (e.g., Huawei@123).
• peer <ip> valid-ttl-hops 255: Enable GTSM.
 • group <name> internal: Create peer group (e.g., group BB internal).
• peer <ip> group <name>: Add peer to group.
• ipv4-family unicast: Enter IPv4 unicast address family.
• peer <name> reflect-client: Configure RR client.
• network <prefix> <mask>: Advertise route (e.g., network [Link] 32).
• peer <ip> advertise-community: Enable community attribute.
• ip ip-prefix <name> index <number> permit <prefix> <length>: Create IP prefix list.
• route-policy <name> permit node <number>: Create route policy.
• if-match ip-prefix <name>: Match prefix list.
• apply community <value>: Set community attribute (e.g., 65003:1).
• peer <ip> route-policy <name> export: Apply export policy.
• ip community-filter basic <name> index <number> permit <value>: Create community
filter.
• ip as-path-filter <name> permit <regex>: Create AS-Path filter.
• if-match community-filter <name>: Match community filter.
• if-match as-path-filter <name>: Match AS-Path filter.
• peer <ip> ip-prefix <name> import: Apply ORF prefix list.
• peer <ip> capability-advertise orf ip-prefix send: Enable ORF sending.
• peer <ip> capability-advertise orf ip-prefix receive: Enable ORF receiving.
• display bgp peer: Check peer status.
• display bgp routing-table: Check BGP routes.
• display bgp peer <ip> orf ip-prefix: Check ORF prefixes.

Static Routes

• ip route-static <destination> <mask> <next-hop>: Configure static route (e.g., ip route-

static [Link] 32 [Link]).

Configuration Framework

Step 1: Basic Device Configuration

• Tasks:
o Same as Section 1.1.
• Example (P2):

bash

Copy

system-view immediately

undo dcn
 undo pnp enable

interface LoopBack0

ip address [Link] 32

interface GigabitEthernet0/5/0

ip address [Link] 30

interface GigabitEthernet0/5/1

ip address [Link] 30

interface GigabitEthernet0/5/2

ip address [Link] 30

• Verification:
o Test connectivity: ping [Link] (P2 to PE4; 0% packet loss).

Step 2: Deploy OSPF in Backbone

• Tasks:
o Configure OSPF (process 1, area 0) on P2, PE2, PE4.
• Example (P2):

bash

Copy

ospf 1 router-id [Link]

area 0

interface LoopBack0

ospf enable 1 area 0

interface GigabitEthernet0/5/1

ospf enable 1 area 0

 interface GigabitEthernet0/5/2

ospf enable 1 area 0

• Verification:
o Check neighbors: display ospf peer brief (P2 shows Full with PE2, PE4).
o Check routes: display ospf routing (P2 learns [Link]/32, [Link]/32).

Step 3: Deploy EBGP

• Tasks:
o Configure static routes for Loopback0 reachability.
o Establish EBGP with GTSM (TTL 255) and authentication (Huawei@123).
• Example (P1-P2):

bash

Copy

[P1] ip route-static [Link] 32 [Link]

[P1] undo crypto weak-algorithm disable

[P1] bgp 65003

router-id [Link]

peer [Link] as-number 65100

peer [Link] connect-interface LoopBack0

peer [Link] password cipher Huawei@123

peer [Link] valid-ttl-hops 255

[P2] ip route-static [Link] 32 [Link]

[P2] undo crypto weak-algorithm disable

[P2] bgp 65100

router-id [Link]
 peer [Link] as-number 65003

peer [Link] connect-interface LoopBack0

peer [Link] password cipher Huawei@123

peer [Link] valid-ttl-hops 255

• Verification:
o Check peers: display bgp peer (P2 shows Established with P1).

Step 4: Deploy IBGP

• Tasks:
o Configure IBGP with P2 as RR, PE2/PE4 as clients, using a peer group.
• Example (P2):

bash

Copy

bgp 65100

group BB internal

peer BB connect-interface LoopBack0

peer BB next-hop-local

peer [Link] group BB

peer [Link] group BB

ipv4-family unicast

peer BB reflect-client

• Verification:
o Check peers: display bgp peer (P2 shows Established with PE2, PE4).

Step 5: Advertise Service Routes

• Tasks:
 o Create Loopback1/2 on P1, PE1, PE3.
o Advertise routes via BGP with community attributes for Loopback1.
• Example (P1):

bash

Copy

interface LoopBack1

ip address [Link] 32

interface LoopBack2

ip address [Link] 32

bgp 65003

network [Link] 32

network [Link] 32

peer [Link] advertise-community

ip ip-prefix Com index 10 permit [Link] 32

route-policy Attr permit node 10

if-match ip-prefix Com

apply community 65003:1

route-policy Attr permit node 100

peer [Link] route-policy Attr export

• Verification:
o Check routes: display bgp routing-table (P1 learns [Link]/32, [Link]/32 with
communities).

Step 6: Configure Routing Policies

 • Tasks:
o Restrict Loopback2 routes to P1 using community and AS-Path filters on PE2,
PE4.
• Example (PE2):

bash

Copy

ip community-filter basic OA index 10 permit 65002:1

ip community-filter basic OA index 20 permit 65003:1

ip as-path-filter Finance permit 65002\$

route-policy Finance permit node 10

if-match community-filter OA

route-policy Finance deny node 20

if-match as-path-filter Finance

route-policy Finance permit node 30

bgp 65100

peer [Link] route-policy Finance export

• Verification:
o Check routes: display bgp routing-table (PE1 learns [Link]/32, [Link]/32, not
[Link]/32).

Step 7: Configure ORF

• Tasks:
o Create Loopback3 on PE3 ([Link]/32) and advertise.
o Configure ORF on P1, P2 to filter unplanned routes.
• Example (P1-P2):

bash

Copy
 [P1] ip ip-prefix Branch index 10 permit [Link] 32

[P1] ip ip-prefix Branch index 20 permit [Link] 32

[P1] ip ip-prefix Branch index 30 permit [Link] 32

[P1] ip ip-prefix Branch index 40 permit [Link] 32

[P1] bgp 65003

peer [Link] ip-prefix Branch import

peer [Link] capability-advertise orf ip-prefix send

[P2] bgp 65100

peer [Link] capability-advertise orf ip-prefix receive

• Verification:
o Check ORF: display bgp peer [Link] orf ip-prefix (P2 shows permitted
prefixes).
o Check routes: display bgp routing-table (P1 does not learn [Link]/32).

Quiz Answer (1.2.3)

In addition to ORF, which method can also be used to filter received routes?

Answer: In addition to ORF, route policies with prefix lists or community filters can be used
to filter received BGP routes.

Explanation:

• ORF: Allows a router (e.g., P1) to send a prefix list to its peer (e.g., P2), instructing it to
filter routes before sending, reducing unnecessary route advertisement.
• Route Policy with Prefix List: A router can apply an import route policy (e.g., peer <ip>
route-policy <name> import) with an IP prefix list to filter incoming routes. For example,
P1 could use a route policy to permit only [Link]/32 and deny [Link]/32.
• Community Filter: Routes can be filtered based on community attributes. For instance,
P1 could deny routes with a specific community value (e.g., 65002:1) using a community
filter in a route policy.
 • Comparison: ORF is more efficient as it filters routes at the sender (P2), reducing
bandwidth and processing. Route policies filter routes after receipt, which is less efficient
but more flexible for complex filtering.

Simplified Analogy: ORF is like telling a store to only ship specific items, while a route policy
is like sorting through all delivered packages and keeping only the desired ones.

Additional Explanations
• FRR Benefit: Precomputes backup paths, ensuring sub-second failover.
• BFD Advantage: Detects link failures faster than OSPF’s default timers.
• Route Filtering: Reduces LSDB size, improving scalability.
• BGP Security: GTSM and authentication prevent unauthorized peering.
• ORF Efficiency: Minimizes route advertisements, optimizing resources.

Analogy: The lab is like a logistics network where OSPF/IS-IS map routes, FRR plans detours,
BFD monitors roads, BGP delivers packages securely, and ORF ensures only requested
deliveries arrive.

This guide provides a clear, artifact-free framework for configuring advanced IGP and BGP
features. Let me know if you need specific device configurations, additional verification steps, or
further clarification on any section!