Nokia BGP for Internet Routing case studies
Nokia BGP for Internet Routing · Put your knowledge to work in context.
The Nokia BGP for Internet Routing exam validates practical command of BGP as deployed on Nokia Service Router platforms and in internet-scale routing. It suits network engineers, service-provider operations staff, and design or escalation engineers who already understand IP routing and now need to prove they can build sessions, steer traffic with policy, scale an autonomous system, and defend the routing table. The Nokia BGP for Internet Routing case studies are 5 cases and about 2,237 words.
1eBGP Loopback Session Stuck in Active Across a Transit Router
R1 (Nokia SR OS, AS 65010) and R2 (AS 65020) need an eBGP session between loopbacks 10.0.0.1/32 and 10.0.0.2/32, not over a directly connected link. The loopbacks are separated by transit router R3: R1 connects to R3 on 192.0.2.0/30 and R3 connects to R2 on 198.51.100.0/30.
458 words, about 2 min2MED and IGP Cost on Two Unequal ISP Exits
AS 65000's Nokia PE router has two eBGP exits for prefix 203.0.113.0/24. Path A is from ISP-A (AS 64500): next-hop 192.0.2.1, MED 50, AS PATH 64500 64496, local-preference 100, IGP cost to next-hop 10.
446 words, about 2 min3Silent L2 Failure: BGP Timers Versus BFD
AS 65000 uses a Nokia SR OS PE with eBGP to a provider edge over a Layer 2 metro Ethernet service. The BGP neighbor is 192.0.2.1, peer-as 64500, hold-time 180 seconds, keepalive 60 seconds.
440 words, about 2 min4RPKI Invalid Announcement from a New Transit
AS 65000's Nokia SR OS border router receives 198.51.100.0/24 from two eBGP peers. Peer A (AS 64500) sends AS PATH 64500 64496.
462 words, about 2 min5IPv6 NLRI over an IPv4-Only BGP Session
AS 65000's Nokia SR OS PE peers with a customer CE over an IPv4-only link 192.0.2.0/30. The BGP session is Established and IPv4 prefixes are exchanged.
431 words, about 2 min