Which two events could cause the BGP Active state to appear? (Choose two.)
A. The local router does not have a route to the peer device.
B. The local router failed to establish a TCP connection with the peer device.
C. A firewall is stopping all UDP packets.
D. The BGP configuration is incomplete.
Correct answers are A and B.
If D was the scenario, the router would even never let you commit the configuration.
In the other hand, if a peer is defined but no reacheblitity to it exists, then the BGP session will get installed as Active.
This was tested in my lab: Example:
[edit]
root# show protocols bgp
group iBgp01 {
type internal;
local-address 1.1.1.1;
neighbor 2.2.2.2;
neighbor 4.4.4.4;
}
[edit]
root# run ping 2.2.2.2 rapid
PING 2.2.2.2 (2.2.2.2): 56 data bytes
!!!!!
— 2.2.2.2 ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.745/0.966/1.355/0.207 ms
[edit]
root# run ping 4.4.4.4 rapid
PING 4.4.4.4 (4.4.4.4): 56 data bytes
ping: sendto: No route to host
.ping: sendto: No route to host
.ping: sendto: No route to host
.ping: sendto: No route to host
.ping: sendto: No route to host
.
— 4.4.4.4 ping statistics —
5 packets transmitted, 0 packets received, 100% packet loss
[edit]
root# run show bgp summary
Groups: 1 Peers: 2 Down peers: 1
Table Tot Paths Act Paths Suppressed History Damp State Pending
inet.0 1 1 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped…
2.2.2.2 100 86 78 0 0 34:22 1/1/1/0 0/0/0/0
4.4.4.4 100 0 0 0 0 2:56 Active