Refer to the exhibit.
The BGP neighbor is not coming up. Which action resolves the issue?
Refer to the exhibit.
The BGP neighbor is not coming up. Which action resolves the issue?
The issue here stems from the BGP neighbor relationship not forming. In the given configuration and exhibit, we can see that R1 defines a BGP neighbor with a remote AS of 100 and the update source as Loopback0. Since the update source is set to a loopback interface and the route to reach 192.168.200.6 is through 192.168.100.1, it implies multiple hops between the BGP peers. BGP by default only permits single-hop eBGP (external BGP) sessions. Therefore, configuring the 'ebgp-multihop 2' command on R1 would allow BGP to form a neighbor relationship even if the peers are more than one hop away. Hence, this action is required to resolve the issue.
A - 192.168.200.6 can be reached via 192.168.100.1, so at least 2 hops needed B - remote RID 0.0.0.0 just tells that there's no TCP connection, and it's given on the pic C - I don't see any route map here D - this has nothing to do w/ the no sync command
Provide answer is correct
Why its A? Anyone?
R1 is part of a different AS number as R2. Considering that the 2 routers are not on the same AS the most logical solution is to enable the ebgp-multihop feature on the BGP configuration of R1.