why is the BGP neighbor not in Established state?

— Exhibit —
[edit protocols bgp]
user@router# show
group ext-peer2 {
type external;

peer-as 1;
neighbor 192.168.2.1;
}
[edit protocols bgp]
user@router# run show route 192.168.2.1
inet.0: 9 destinations, 10 routes (7 active, 0 holddown, 2 hidden)
+ = Active Route, – = Last Active, * = Both
192.168.2.1/32 *[Static/5] 00:01:56
> to 172.14.10.1 via ge-0/0/1.0
[edit protocols bgp]
user@router# run show bgp summary
Groups: 1 Peers: 1 Down peers: 1
Table Tot Paths Act Paths Suppressed History Damp State Pending
inet.0 0 0 0 0 0 0
inet6.0 0 0 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped…
192.168.2.1 1 0 0 0 0 14 Idle
— Exhibit —
Click the Exhibit button.

Looking at the output in the exhibit, why is the BGP neighbor not in Established state?

— Exhibit —
[edit protocols bgp]
user@router# show
group ext-peer2 {
type external;

peer-as 1;
neighbor 192.168.2.1;
}
[edit protocols bgp]
user@router# run show route 192.168.2.1
inet.0: 9 destinations, 10 routes (7 active, 0 holddown, 2 hidden)
+ = Active Route, – = Last Active, * = Both
192.168.2.1/32 *[Static/5] 00:01:56
> to 172.14.10.1 via ge-0/0/1.0
[edit protocols bgp]
user@router# run show bgp summary
Groups: 1 Peers: 1 Down peers: 1
Table Tot Paths Act Paths Suppressed History Damp State Pending
inet.0 0 0 0 0 0 0
inet6.0 0 0 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped…
192.168.2.1 1 0 0 0 0 14 Idle
— Exhibit —
Click the Exhibit button.

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.



Leave a Reply 0

Your email address will not be published. Required fields are marked *