4A0-114 Nokia Border Gateway Protocol Fundamentals for Services Questions and Answers

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.

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.

A type-2 EVPN route update is used to carry host-specific information.

It includes the MAC address of the host and optionally the associated IP address.

This type of update allows for efficient MAC and IP address learning and advertisement within the EVPN.

Therefore, the type-2 EVPN route update carries a host MAC address and optionally the associated IP address.

References :

Nokia Border Gateway Protocol Fundamentals documentation, Section 11.2 on type-2 EVPN route updates.

Understanding the Network Topology:

Routers are part of different ASes: Router A and Router B are in AS 65540, Router D is in AS 65550, and Router E is in AS 65560.

To allow Router B to exchange traffic with Router D, proper iBGP (internal BGP) configuration is required within AS 65540.

Configuration Requirements:

The configuration on Router A should include:

Enabling IPv6 family for BGP.

Setting the next-hop-self to ensure that the BGP next-hop is reachable.

Specifying the type as internal to denote an iBGP session.

Configuring the neighbor as Router B ' s IPv6 address.

Analyzing Options:

Option A: Missing the type internal configuration.

Option B: Missing the family ipv6 configuration.

Option C: Missing both next-hop-self and type internal configurations.

Option D: Correctly includes all necessary commands:

family ipv6

next-hop-self

type internal

neighbor 2001:DB8:2::2

Conclusion:

Option D provides a complete configuration for Router A to enable traffic exchange between Router B and Router D using iBGP with IPv6.

References

Nokia Border Gateway Protocol (BGP) Fundamentals documentation

Best practices for iBGP and eBGP configurations

IPv6 addressing and BGP configurations in multi-AS environments

Route reflectors (RR) follow specific rules for propagating routes to prevent routing loops and ensure efficient route distribution within an Autonomous System (AS).

Here are the rules that a route reflector follows:

If the best route is received from an eBGP peer, it propagates the route to all iBGP peers.

If the best route is received from an eBGP peer, it propagates the route to all eBGP peers.

If the best route is received from a client, it propagates the route to all iBGP peers, including other clients and non-clients.

If the best route is received from a non-client, it propagates the route to all clients.

The statement " If the best route is received from a client, do not propagate to eBGP peers. " is NOT followed by a route reflector. In fact, if the best route is received from a client, it is propagated to both eBGP and iBGP peers as required.

References :

Nokia Border Gateway Protocol Fundamentals documentation, Section 5.3 on Route Reflector Rules and Propagation.

When a BGP router receives multiple routes for the same destination, it selects the best route based on several attributes in the following order of preference:

Highest local preference : Routes with the highest local preference are preferred.

Shortest AS_PATH : Routes with the shortest AS path are preferred.

Lowest MED : Routes with the lowest MED are preferred.

eBGP over iBGP : Routes learned via eBGP are preferred over iBGP routes.

Lowest IGP metric to BGP next hop .

Given the routes:

Local preference 100, MED 150, AS Path 65300 65200 (eBGP)

Local preference 100, MED 100, AS Path 63200 (iBGP)

Local preference 200, MED 150, AS Path 65400 63200 (iBGP)

Local preference 200, MED 100, AS Path 63700 (eBGP)

Route 4 has the highest local preference (200), the lowest MED (100), and is learned via eBGP. Therefore, it is the best route.

References Nokia Border Gateway Protocol Fundamentals, Chapter on BGP Route Selection Process.

In the given network diagram, RR1 and RR2 are route reflectors within AS 65540. The role of a route reflector is to reduce the number of iBGP peering sessions required within an AS.

Each route reflector (RR1 and RR2) should have the same cluster ID to identify the route reflector cluster they belong to.

RR1 needs to be configured with BGP settings that include its role as a route reflector with appropriate cluster ID and neighbor configurations.

Examining the given options:

Option A : This configuration shows RR1 with a cluster ID, proper BGP setup, and correct neighbors within the AS 65540, which corresponds to the network diagram.

Router bgp 65540 bgp router-id 10.16.10.1 bgp cluster-id 10.16.10.1 neighbor 10.16.10.2 remote-as 65540 neighbor 10.16.10.2 route-reflector-client neighbor 10.16.10.5 remote-as 65540 neighbor 10.16.10.5 route-reflector-client neighbor 10.16.10.6 remote-as 65540 neighbor 10.16.10.6 route-reflector-client

Option B : This option does not match as closely to the network requirements as Option A.

Option C and Option D : Both these options are duplicates and appear similar to Option B, not providing the correct configuration for RR1 as per the network diagram.

Therefore, the correct answer is Option A .

References :

Nokia Border Gateway Protocol Fundamentals documentation, Section 6.4 on Route Reflector configurations and examples.

Understanding the AS Path Traversal:

The question states that an update travels from AS 137000 to AS 135000, passing through both 32-bit and 16-bit AS Paths.

The Autonomous Systems (AS) involved in the diagram are AS 137000, AS 140000, AS 200 (16-bit), and AS 135000.

Analyzing the AS Path:

The update starts at AS 137000.

It then moves to AS 140000.

From AS 140000, it reaches AS 200 (which is a 16-bit AS).

Finally, it reaches AS 135000.

AS Path Seen by AS 200:

When the update reaches AS 200, the AS Path recorded will include all the Autonomous Systems it has traversed so far, in reverse order.

Therefore, the AS Path seen by AS 200 will include AS 137000 and AS 140000, in that order.

Verifying the Answer:

The AS Path seen by AS 200 should show the sequence of ASes the update has traversed before reaching AS 200.

Thus, the correct AS Path is: 137000 140000.

References

Nokia Border Gateway Protocol (BGP) Fundamentals documentation

BGP Path Attributes and AS Path documentation

Standard BGP routing behavior and AS Path recording principles

Router R1 is a route reflector for its clients R2, R5, and R6.

The prefix 192.168.1.0/27 is advertised by Router R3 to Routers R5 and R6.

Router R5 will receive this prefix with a local preference of 200.

Since none of the routers in AS 65540 is configured with " advertise-external, " Router R5 will not advertise the received external route to its internal peers.

The output of " show router bgp routes " on Router R5 will show the prefix 192.168.1.0/27 with a local preference of 200, learned from Router R3.

References

Nokia Border Gateway Protocol Fundamentals documentation

BGP Route Reflector and local preference configuration guidelines as per Nokia ' s documentation

To prevent route advertisement loops in a network using route reflectors, specific attributes are employed.

The key attributes used for loop prevention in BGP are:

MED (Multi-Exit Discriminator) : Used to influence the incoming traffic from neighboring ASes. It is not used for loop prevention.

ORIGIN : Indicates the origin of the route but does not directly prevent loops.

CLUSTER_LIST : Used by route reflectors to prevent loops. When a route reflector propagates a route, it adds its cluster ID to the CLUSTER_LIST. If a route with its own cluster ID is received, it is rejected to prevent loops.

AS_PATH : Records the ASes a route has traversed, preventing loops by rejecting routes containing the local AS number.

Therefore, the CLUSTER_LIST attribute is specifically used by route reflectors to prevent routing loops by keeping track of the clusters a route has passed through.

References :

Nokia Border Gateway Protocol Fundamentals documentation, Section 6.5 on Attributes for Loop Prevention in Route Reflectors.