The Nokia Border Gateway Protocol Fundamentals for Services (4A0-114)

IPv6 BGP Session Requirements : To establish an IPv6 BGP session, the configuration must include the IPv6 addresses of the neighbors and the appropriate family settings.

Option Analysis :

Option A : Incorrect. The configuration does not match typical BGP IPv6 configuration standards for Nokia routers.

Option B : Incorrect. The configuration is incomplete for establishing an IPv6 BGP session.

Option C : Correct. The configuration includes the appropriate neighbor IPv6 address and family settings required to establish an IPv6 BGP session.

Option D : Incorrect. The configuration has errors or missing components needed for a proper IPv6 BGP session.

Conclusion : Option C provides the correct configuration necessary to establish an IPv6 BGP session between router A and router B.

References:

Nokia Border Gateway Protocol Fundamentals

Nokia 7750 SR OS BGP Configuration Guide

A distributed EVPN VPRN service acts as a router for IP packets between customer sites.

It does require two types of interfaces: one towards customer sites (CEs) and another towards the EVPN VPLS for backhaul connectivity.

The configured route target (RT) helps PE routers identify relevant BGP updates.

MP-BGP with the EVPN address family is used to populate the routing table.

Therefore, the statement " It requires two types of interfaces, one towards customer sites and one towards the backhaul VPLS. " is FALSE because the backhaul VPLS reference should instead pertain to VPRN backhaul routing.

References :

Nokia Border Gateway Protocol Fundamentals documentation, Section 9.2 on EVPN VPRN interface requirements and configuration.

Step by Step Comprehensive Detailed Explanation The statement " eBGP peers have to be adjacent to each other " is false. eBGP peers usually are directly connected to ensure reliable and straightforward communication. However, eBGP multihop allows BGP to establish a session with eBGP peers that are not directly connected by setting the multihop parameter.

A. True : BGP peers need IP reachability between them.

B. True : iBGP peers can be non-adjacent.

C. False : eBGP peers do not necessarily have to be directly connected if multihop is configured.

D. True : BGP peers can be configured with different AS numbers.

References Nokia Border Gateway Protocol Fundamentals, Chapter on eBGP and iBGP Configurations.

Ethernet VPN (EVPN) services provide advanced features for layer-2 and layer-3 connectivity among customer sites. Here are key points about EVPN:

A. True : The goal of an EVPN service is to provide layer-2 or layer-3 connectivity among two or more customer sites.

B. False : A local layer-2 EVPN service is not referred to as a backhaul VPLS. Backhaul VPLS is a different service concept used to transport layer-2 traffic over a layer-3 network.

C. True : The same BGP address family (EVPN) can be used to populate the forwarding database of an EVPN VPLS and the route table of an EVPN VPRN.

D. True : EVPN services support signaling for the use of MPLS and VXLAN tunnels.

References Nokia Border Gateway Protocol Fundamentals, Chapter on EVPN Services.

Best Practices for BGP Address Planning:

Proper address planning ensures efficient and reliable BGP operations.

It involves using specific addresses for BGP sessions and advertising appropriate routes.

Analyzing the Options:

A. Advertising external networks into IGP: Not recommended as it can lead to IGP table bloating and instability.

B. Using system addresses for setting up iBGP sessions: This is considered a best practice. System addresses (loopback addresses) are stable and do not change even if the physical interface goes down, ensuring session stability.

C. Exporting the networks associated with the external links of eBGP peers into BGP: This is normal practice but not directly related to address planning best practices.

D. Optimizing BGP route table by exporting IGP routes into BGP: Typically, you would do the opposite (importing BGP routes into IGP selectively).

Conclusion:

Using system addresses (loopback addresses) for setting up iBGP sessions is a widely accepted best practice. It enhances the reliability and stability of the BGP sessions.

References

Nokia Border Gateway Protocol (BGP) Fundamentals documentation

Best practices in BGP design and implementation

Network stability and reliability considerations in BGP configurations

The BGP import policy " north-and-south " on R5 checks the community attribute of incoming routes.

If the community matches " 65200:1 " , it sets the local preference to 20.

Since R1 advertises the prefix 140.100.1.0/24 with a community of " 65200:1 " , R5 will apply the policy action.

Therefore, the prefix ' s local preference is set to 20.

References :

Nokia Border Gateway Protocol Fundamentals documentation, Section 5.2 on BGP policies.

Local Preference Comparison : Local preference is the first criterion BGP uses to select the best path. The higher the local preference, the more preferred the route. Here, the first route has a local preference of 150, while the other two routes have a local preference of 100.

Best Path Selection : Since the first route has the highest local preference (150), it will be preferred over the other two routes regardless of the AS Path length or any other attributes.

RIB-Out : The RIB-Out (Routing Information Base - Outbound) contains the routes selected for advertisement to peers. As only the best path is advertised, only the first route with the highest local preference will be included in the RIB-Out.

References:

Nokia Border Gateway Protocol Fundamentals

RFC 4271 - A Border Gateway Protocol 4 (BGP-4)

IPv6 Link-Local addresses are specific types of addresses used within a single local network segment. Here are key points about IPv6 Link-Local addresses:

A. True : Every physical interface running IPv6 is assigned a Link-Local address automatically.

B. True : Link-Local addresses are only valid for communication within the same broadcast domain (i.e., the local link).

C. True : They all have the same 64-bit subnet prefix ( FE80::/64 ).

The false statement is:

D. False : The interface ID for Link-Local addresses is not derived from the interface’s IPv4 address. Instead, it is typically generated from the interface’s MAC address or using a random number.

References Nokia Border Gateway Protocol Fundamentals, Chapter on IPv6 Addressing.

Full Mesh Requirement : In a BGP network, to ensure that all BGP routers within the same autonomous system (AS) have complete reachability, each router must establish an iBGP session with every other router in the AS.

Calculating the Number of iBGP Sessions :

The formula to calculate the number of iBGP sessions required in a fully meshed configuration is ???? ( ???? −1)2 2 n ( n −1) ​ , where ???? n is the number of routers.

For an autonomous system with 7 routers, we substitute ???? =7 n =7 into the formula.

Applying the Formula :

7(7−1)2=7×62=422=21 27(7−1) ​ = 27×6 ​ = 242 ​ =21

Explanation :

Each of the 7 routers needs to establish a session with every other router, but each session is counted only once. Therefore, we divide the product of the total routers and one less than the total routers by 2 to avoid double-counting.

This results in a total of 21 iBGP sessions.

References:

Nokia Border Gateway Protocol Fundamentals

Standard BGP configuration guidelines and best practices