Looking at the output in the exhibit, why is the BGP neighbor not in Established state?
A.
BGP Refresh is not supported.
B.
Multihop is not configured.
C.
The peer address is not reachable.
D.
Authentication is configured.
Click the Exhibit button.
Looking at the output in the exhibit, why is the BGP neighbor not in Established state?
Looking at the output in the exhibit, why is the BGP neighbor not in Established state?
A.
BGP Refresh is not supported.
B.
Multihop is not configured.
C.
The peer address is not reachable.
D.
Authentication is configured.
How do you come to the conclusion that multihop is not configured?
It’s the easy question. Look here http://www.juniper.net/techpubs/software/junos/junos94/swconfig-routing/configuring-an-ebgp-multihop-session.html
It is the key difference between eBGP and iBGP configuration.
Phillip shows the correct configuration As you can see, the EBGP peering is configured to the loopback address of the neighbor 192.168.2.1. So you need multihop to allow the peering to the loopback interface. Setting the TTL 1 keeps it trying other backdoor connections to other routers.