Click the Exhibit button.
R1 is exporting 2000:FEFE:100::/64 to R2 over the EBGP peering session as shown in the exhibit.
What will R1 use for this route’s protocol next hop when advertising it to R2?
A.
2000:FEFE:89::1
B.
172.16.1.1
C.
10.1.1.1
D.
::FFFF:172.16.1.1
Explanation:
When a BGP router reports itself as the next hop, whether because of an explicit neighbor next-hop-self
configuration or implicitly as a result of participating in an EBGP session, BGP allocates a new in label and
adds an entry to the MPLS forwarding table, creating a label-to-next-hop mapping.
Note: When a BGP router does not report itself as the next hop, whether because of an explicit neighbor nexthop-unchanged configuration or implicitly as a result of a participating in an IBGP session, BGP does not
allocate a new in label. Instead, if the route is advertised as a labeled route, BGP uses the existing out label.
This feature is used mainly on route reflectors.
https://www.juniper.net/techpubs/en_US/junose16.1/topics/concept/mbgp-bgp-next-hop-selfoverview.html
Guys,
Any idea for this answer? I think it should be option D?
1
0
Agreed D
https://www.juniper.net/documentation/en_US/junos/topics/example/bgp-ipv6.html#jd0e608
1
0
yes its D. tested in LAB
1
0
https://tools.ietf.org/html/rfc4291
A proper recursive resolution to a valid Next Hop for IPv6 prefixes requires that BGP Next Hop addresses are represented embedded in IPv6 prefixes. IPv4-Mapped IPv6 addresses represent a transition mechanism in which the IPv4 prefix is automatically and uniquely embedded into the IPv6 address and is an adequate tool for this purpose. These IPv4-mapped IPv6 addresses are defined in [RFC4291] Section 2.5.5.2 to represent the addresses of IPv4 nodes as IPv6 addresses:
| 80 bits | 16 | 32 bits |
+————————————–+————————–+
|0000…………………………0000|FFFF| IPv4 address |
+————————————–+—-+———————+
1
0