— Exhibit —
user@R1> show bgp neighbor 172.10.3.201
Peer: 172.10.3.201+54714 AS 64512 Local: 172.10.3.202+179 AS 64513
Type: External State: Established Flags:
Last State: OpenConfirm Last Event: RecvKeepAlive
Last Error: None
Export: [ export ]
Options:
Local Address: 172.10.3.202 Holdtime: 90 Preference: 170 Local AS: 64513
Local System AS: 0
Number of flaps: 0
Peer ID. 10.247.194.254 Local ID. 10.247.24.6 Active Holdtime: 90
Keepalive Interval: 30 Peer index: 0
BFD. disabled, down
Local Interface: ge-0/0/0.500
NLRI for restart configured on peer: inet-unicast
NLRI advertised by peer: inet-unicast
NLRI for this session: inet-unicast
Peer supports Refresh capability (2)
Restart time configured on the peer: 120
Stale routes from peer are kept for: 300
Restart time requested by this peer: 120
NLRI that peer supports restart for: inet-unicast
NLRI that restart is negotiated for: inet-unicast
NLRI of received end-of-rib markers: inet-unicast
NLRI of all end-of-rib markers sent: inet-unicast
Peer supports 4 byte AS extension (peer-as 64512)
Peer does not support Addpath
Table inet.0 Bit: 30000
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Send state: in sync
Active prefixes: 7
Received prefixes: 7
Accepted prefixes: 7
Suppressed due to damping: 0
Advertised prefixes: 30
Last traffic (seconds): Received 5 Sent 18 Checked 8
Input messages: Total 40 Updates 3 Refreshes 0 Octets 877
Output messages: Total 55 Updates 13 Refreshes 0 Octets 1764
Output Queue[2]: 0
— Exhibit —
A customer reports that BGP graceful restart is not working on R1. After a Routing Engine failover,
R1 did not set the restart state bit in its Open message. The customer provides the BGP neighbor
output shown in the Above. What is causing this problem?
A.
BGP graceful restart is not enabled on R1.
B.
BGP graceful restart is not enabled on the peer device.
C.
The restart duration time is not configured on R1.
D.
The restart duration time is not configured on the peer device.