Study guide
8.2 BGP Path Attributes and Route Selection
Nokia Network Routing Specialist I NRS I, 4A0-100
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: OSI and TCP/IP Networking Models
1.1 OSI Reference Model and Layer Functions 1.2 TCP/IP Protocol Stack and Data Encapsulation 1.3 Network Architecture and Device Planes
2 Chapter 2: Ethernet Technology and LAN Switching
2.1 Ethernet Framing and Physical Standards 2.2 Bridging, Switching, and Collision/Broadcast Domains 2.3 VLANs and IEEE 802.1Q Tagging 2.4 Ethernet Redundancy, Spanning Tree, and LAGs
3 Chapter 3: IP Addressing and Subnetting
3.1 IPv4 Addressing Architecture and Classes 3.2 IPv4 Subnetting, CIDR, and VLSM 3.3 IPv6 Addressing Fundamentals 3.4 IP in Homes and Small Businesses
4 Chapter 4: IP Forwarding and Host Resolution
4.1 IPv4 Header Architecture and Packet Forwarding 4.2 Address Resolution Protocol (ARP) and IPv6 Neighbor Discovery 4.3 ICMP and Network Troubleshooting
5 Chapter 5: Nokia Service Router Hardware and Management
5.1 Nokia Service Router Hardware Architecture 5.2 SR OS Classic CLI Navigation and Operations 5.3 Model-Driven CLI (MD-CLI) and Datastore Management 5.4 Boot Process and Configuration Recovery
6 Chapter 6: Routing Fundamentals and Static Routing
6.1 Routing Concepts, RIB vs FIB, and Route Preference 6.2 Static Route Configuration and Next-Hop Resolution 6.3 Dynamic Routing Protocols Overview
7 Chapter 7: Interior Gateway Protocols: OSPF and IS-IS
7.1 OSPF Fundamentals and Adjacency Formation 7.2 OSPF Multi-Area Architecture and LSA Types 7.3 IS-IS Protocol Architecture and Operations
8 Chapter 8: BGP and Internet Architecture
8.1 BGP Architecture and Peering 8.2 BGP Path Attributes and Route Selection 8.3 IBGP Split-Horizon and Scaling Solutions 8.4 Internet Components, Peering, and Transit
9 Chapter 9: MPLS Architecture and Signaling
9.1 MPLS Concepts and Label Operations 9.2 Label Distribution Protocol (LDP) 9.3 RSVP-TE and Traffic Engineering
10 Chapter 10: Nokia VPN Services: Layer 2 and Layer 3
10.1 Nokia Service Architecture and Building Blocks 10.2 Layer 2 Services: VPWS/VLL and VPLS 10.3 Layer 3 Services: IES and VPRN
8.2 BGP Path Attributes and Route Selection
Key Takeaways Explain This Topic AI
Evaluate route eligibility and next-hop resolution before comparing attractive attributes.
LOCAL_PREF prefers higher values within an AS; MED prefers lower values when comparison applies.
AS_PATH length follows earlier policy criteria and does not measure physical delay.
Mandatory attributes apply to relevant advertisements, not every withdrawal-only UPDATE.
A simplified attribute example is not the complete configurable SR OS path-selection algorithm.
Last updated: October 2026
Read what an advertisement says
A BGP route contains more than a destination prefix. Its path attributes describe origin, AS traversal, next-hop information, and policy preferences. This lesson adds detail to the current course's introductory BGP topic; it does not imply that every advanced tie-breaker is a separate published 4A0-100 objective.
Begin with eligibility. A route rejected by import policy or lacking a usable next hop cannot become a usable path merely because it has an attractive AS_PATH. The selected BGP path must also compete appropriately with other route sources in the routing context.
Attribute categories
Category Recognition and propagation Examples
Well-known mandatory Recognized by compliant speakers; required in applicable conventional reachability advertisements ORIGIN, AS_PATH, NEXT_HOP
Well-known discretionary Recognized, included as required by its rules LOCAL_PREF, ATOMIC_AGGREGATE
Optional transitive An unrecognized attribute can be preserved and passed with required flags COMMUNITY, AGGREGATOR
Optional non-transitive An unrecognized attribute is not passed onward MED
“Mandatory” does not mean every UPDATE packet contains all three familiar attributes. An UPDATE can only withdraw routes, and multiprotocol address families carry next-hop information in their applicable structures. Attribute presence and error handling must be interpreted in the message's actual context.
AS_PATH and ORIGIN
AS_PATH records AS traversal. An ordinary external advertisement prepends the sending AS. A receiver normally rejects a path containing its own AS to avoid an interdomain control-plane loop. Explicit features such as confederations or local-AS handling introduce additional rules; the basic model assumes these are absent.
A shorter AS_PATH can be preferred after earlier selection criteria tie. AS prepending repeats an ASN to influence another network's selection. It is a suggestion through attributes, not an instruction that overrides the other network's policies. Fewer AS entries do not guarantee lower delay.
ORIGIN has values IGP, EGP, and INCOMPLETE, ordered 0, 1, and 2 for ordinary comparisons. It describes how a route was introduced into BGP under the originating configuration. “IGP” is not a certificate of route stability, and a route learned through another protocol does not universally acquire a particular ORIGIN without considering export policy and implementation behavior.
NEXT_HOP must resolve
NEXT_HOP identifies where traffic toward the advertised destination should be sent. The BGP peer that delivered an update and the forwarding next hop need not be the same router.
Suppose a border router learns 203.0.113.0/24 externally with next hop 192.0.2.2 and advertises it internally. If an internal peer has no route resolving 192.0.2.2 , the BGP session can be healthy while the path is unusable. The operator can provide suitable next-hop reachability or intentionally rewrite the next hop with a supported policy.
This reachability is recursive: the router resolves the advertised next hop through its routing and, where applicable, tunnel information until it has usable forwarding. A route's presence in a BGP display is not proof that it is active in the main FIB.
LOCAL_PREF and MED
LOCAL_PREF expresses internal preference for an exit. Higher values are preferred; SR OS uses 100 as its ordinary default. It is distributed within the AS, rather than normally advertised to external peers. Confederation behavior is a special case outside the simple model.
If two eligible paths to one prefix have LOCAL_PREF 200 and 100, the first normally wins before AS_PATH length is considered. This can intentionally prefer a longer AS path for business or policy reasons.
MULTI_EXIT_DISC (MED) suggests an entry preference to a neighboring AS. Lower values are preferred when MED is compared. By default, ordinary comparison is between applicable paths from the same neighboring AS; configuration can alter this behavior.
Neither attribute guarantees a particular traffic pattern. Route eligibility, more-specific destination advertisements, policy on other routers, and failures can change actual forwarding. LOCAL_PREF affects a route choice inside the AS; it is not a direct setting for all Internet senders.
A bounded selection example
The following simplified comparison assumes eligible conventional IPv4 BGP paths, equal route preference, no earlier differentiating feature, and ordinary path-selection settings. It illustrates common criteria rather than claiming an exhaustive SR OS algorithm.
- Candidate LOCAL_PREF AS_PATH length ORIGIN
- A 100 2 IGP
- B 100 3 IGP
- C 100 2 INCOMPLETE
LOCAL_PREF ties. Candidate B loses on AS_PATH length. A then beats C on ORIGIN. There is no need to compare their MED or internal next-hop distance after a winner is determined.
With LOCAL_PREF 200 on B instead, B wins the illustrated comparison despite its longer AS path. Always stop at the first applicable criterion that resolves the comparison.
When later criteria are needed, route source, next-hop distance, and identifier tie-breaks can matter. Consult the matching SR OS manual and configured path-selection options. Do not insert a Cisco-specific Weight mnemonic and call it Nokia's complete algorithm.
Verify the selected result
Inspect BGP route details for the prefix, peer, path attributes, and selection reason. Then inspect the main route table. A path selected as BGP's best can still lose to an eligible static route for the exact same prefix.
For a packet, perform longest-prefix match over installed routes afterward. An installed /25 can override an installed /24 for matching destinations regardless of the relative LOCAL_PREF used when each prefix's BGP path was chosen. Keeping these steps distinct avoids a common confusion between BGP path selection and packet forwarding.
Primary references
BGP specification and Nokia SR OS documentation , checked October 20, 2026. Use current release documentation for the full configurable selection procedure.