Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BGP AND MPLS CONFIGURATION GUIDE 2010-10-12 Configuration Manual page 217

Copyright © 2010, Juniper Networks, Inc.
2053 update messages sent, 42785 update messages received
0 00:00:17 since last update message was received
Fields relevant to multiprotocol extensions:
Multi-protocol extensions negotiation:
ip-v4 unicast: sent, received, used
ip-v6 unicast-labeled: sent, received, used
For the graceful restart capability, additional information is presented.
Fields concerning graceful restart attributes that apply to peers as a whole (for all
address families):
Graceful restart negotiation:
Sent restart time is 120 seconds
Sent restart state bit is zero (we are not restarting)
Received restart time is 120 seconds
Received restart state bit is zero (peer is not restarting)
Maximum time for keeping stale paths is 360 seconds
Fields concerning attributes that apply to peers a particular address family:
Peer is capable of preserving forwarding stat(3)
Peer preserved forwarding state during last restart
We have received an end-of-rib marker from the peer
We have sent an end-of-rib marker to the peer
Fields relevant if the peer is currently restarting:
Graceful restart waiting for the session to come back up
Restart-time advertised by the peer is 120 seconds
Remaining time for the peer to come back up is 117 seconds
Remaining time for keeping stale routes from the peer is 357 seconds
Fields relevant during reconvergence after the peer has restarted:
Graceful restart negotiation:
Sent restart time is 120 seconds
Sent restart state bit is zero (we are not restarting)
Received restart time is 120 seconds
Received restart state bit is zero (peer is not restarting)
Maximum time for keeping stale paths is 300 seconds
Remaining time for keeping stale routes from the peer is 297 seconds
For BFD, additional information is presented.
Fields relevant to BFD when BFD is not configured:
BFD is disabled
Fields relevant to BFD when BFD is configured for an IBGP peer:
BFD is enabled but not supported (IBGP neighbor)
Fields relevant to BFD when BFD is configured for a multihop EBGP peer:
BFD is enabled but not supported (multi-hop EBGP neighbor)
Fields relevant to BFD when BFD is configured but the BGP session is not established:
Chapter 2: Monitoring BGP
181