BGP routes low up time in sh ip route

[Swathi K]

Hello All,

Good Day!

Below is the output of sh ip route for BGP routes:

Its showing route learnt time as 1d03h. But but the bgp, track, or interface for primary link didn't flap.( no logs found)

May I know whats the reason for low up time.

B* 0.0.0.0/0 [20/0] via 10.164.22.9, 09:06:18
10.0.0.0/8 is variably subnetted, 5783 subnets, 12 masks
B 10.6.10.0/24 [20/0] via 10.164.22.9, 1d03h
B 10.6.10.16/30 [20/0] via 10.164.22.9, 1d03h
B 10.6.10.20/30 [20/0] via 10.164.22.9, 1d03h
B 10.6.10.251/32 [20/0] via 10.164.22.9, 1d03h

Also please find below outputs.

sh ip bgp summary:

Neighbor        V       AS           MsgRcvd MsgSent      TblVer      InQ OutQ             Up/Down          State/PfxRcd
10.164.22.9   4       65530      246271 245787        12874498   0    0                     11w1d             5827

Interface status :

1#sh track br
Track Type Instance Parameter State Last Change
1 ip route 0.0.0.0 reachability Up 10w6d

#sh ip bgp nei 10.164.22.9
BGP neighbor is 10.164.22.9, remote AS 65530, external link
BGP version 4, remote router ID 10.164.22.9
BGP state = Established, up for 11w1d
Last read 00:00:02, last write 00:00:11, hold time is 90, keepalive interval is 30 seconds
Neighbor sessions:
1 active, is not multisession capable (disabled)
Neighbor capabilities:
Route refresh: advertised and received(new)
Four-octets ASN Capability: advertised and received
Address family IPv4 Unicast: advertised and received
Graceful Restart Capability: received
Remote Restart timer is 120 seconds
Address families advertised by peer:
none
Enhanced Refresh Capability: advertised
Multisession Capability:
Stateful switchover support enabled: NO for session 1
Message statistics:
InQ depth is 0
OutQ depth is 0

Sent Rcvd
Opens: 1 1
Notifications: 0 0
Updates: 340 15089
Keepalives: 245452 231188
Route Refresh: 0 0
Total: 245793 246278
Do log neighbor state changes (via global configuration)
Default minimum time between advertisement runs is 30 seconds

For address family: IPv4 Unicast
Session: 10.164.22.9
BGP table version 12874498, neighbor version 12874498/0
Output queue size : 0
Index 54, Advertise bit 0
54 update-group member
Inbound soft reconfiguration allowed
Slow-peer detection is disabled
Slow-peer split-update-group dynamic is disabled
Sent Rcvd
Prefix activity: ---- ----
Prefixes Current: 7 5827 (Consumes 466160 bytes)

Prefixes Total: 176 70962
Implicit Withdraw: 0 15520
Explicit Withdraw: 169 49615
Used as bestpath: n/a 5826
Used as multipath: n/a 0

Outbound Inbound
Local Policy Denied Prefixes: -------- -------
Bestpath from this peer: 63237 n/a
Total: 63237 0
Number of NLRIs in the update sent: max 47, min 0
Last detected as dynamic slow peer: never
Dynamic slow peer recovered: never
Refresh Epoch: 1
Last Sent Refresh Start-of-rib: never
Last Sent Refresh End-of-rib: never
Last Received Refresh Start-of-rib: never
Last Received Refresh End-of-rib: never
Sent Rcvd
Refresh activity: ---- ----
Refresh Start-of-RIB 0 0
Refresh End-of-RIB 0 0

[MHM Cisco World]

R1#show ip bgp internal <<- share this please

MHM 

[Swathi K]

1#sh ip bgp internal
Time left for bestpath timer: 772 secs
Consistency-checker not enabled
Update generation pool version 401, messages 0, in pool 0, below 00:00:56.760.
Enhanced Refresh EOR Stalepath-time disabled
Enhanced Refresh max-eor-time disabled
Total number of BGP Accepter process: 50, Spawned count: 0
Total number of neighbors: 1
Total number of sessions : 1
Established : 1
OpenConfirm : 0
OpenSent : 0
Active : 0
Connect : 0
Idle : 0
Closing : 0
Uninitialized : 0
Address-family IPv4 Unicast, Mode : RW
Table Versions : Current 12874996 Init 2 RIB 12874996
Start time : 2w1d Time elapsed 5y33w
First Peer up in : 00:04:02.124 Exited Read-Only in : 00:03:43.240
Done with Install in : 00:03:43.240 Last Update-done in : 00:03:43.240
33 updates expanded
L3VPN Tunnel Encapsulated Paths : 0
Slow-peer detection is disabled BGP Nexthop scan:-
penalty: 0, Time since last run: 11w1d, Next due in: none
Max runtime : 24 ms Latest runtime : 16 ms Scan count: 55
BGP General Scan:-
Max runtime : 28 ms Latest runtime : 8 ms Scan count: 0

BGP future scanner version: 2963035
BGP scanner version: 0
Address-family IPv4 Multicast, Mode : RW
Table Versions : Current 1 Init 1 RIB 1
Start time : 2w1d Time elapsed 5y33w
First Peer up in : never Exited Read-Only in : 00:00:10.240
Done with Install in : 00:00:10.240 Last Update-done in : never
0 updates expanded
L3VPN Tunnel Encapsulated Paths : 0
Slow-peer detection is disabled BGP Nexthop scan:-
penalty: 0, Time since last run: never, Next due in: none
Max runtime : 0 ms Latest runtime : 0 ms Scan count: 0
BGP General Scan:-
Max runtime : 4 ms Latest runtime : 0 ms Scan count: 0

BGP future scanner version: 2963038
BGP scanner version: 0
Address-family L2VPN E-VPN, Mode : RW
Table Versions : Current 1 Init 1 RIB 1
Start time : 2w1d Time elapsed 5y33w
First Peer up in : never Exited Read-Only in : 00:00:10.240
Done with Install in : 00:00:10.240 Last Update-done in : never
0 updates expanded
L3VPN Tunnel Encapsulated Paths : 0
Slow-peer detection is disabled BGP Nexthop scan:-
penalty: 0, Time since last run: never, Next due in: none
Max runtime : 0 ms Latest runtime : 0 ms Scan count: 0
BGP General Scan:-
Max runtime : 4 ms Latest runtime : 0 ms Scan count: 0

BGP future scanner version: 2963038
TX VPN optimisation enabled.
Address-family MVPNv4 Unicast, Mode : RW
Table Versions : Current 1 Init 1 RIB 1
Start time : 2w1d Time elapsed 5y33w
First Peer up in : never Exited Read-Only in : 00:00:10.240
Done with Install in : 00:00:10.240 Last Update-done in : never
0 updates expanded
L3VPN Tunnel Encapsulated Paths : 0
Slow-peer detection is disabled BGP Nexthop scan:-
penalty: 0, Time since last run: never, Next due in: none
Max runtime : 0 ms Latest runtime : 0 ms Scan count: 0
BGP General Scan:-
Max runtime : 4 ms Latest runtime : 0 ms Scan count: 0

BGP future scanner version: 2963038
TX VPN optimisation enabled.

[MHM Cisco World]

the Peer UP time is not show us the update happened to BGP table ver. 
this simple example 
first you can see the BGP table ver. is 3 and the prefix update via this ver. is 11.11.11.11 
then I add 111.111.111.111 in R1 and check ver in R2 again 
it now Ver4 and the prefix update is 111.111.111.111
so do
show ip bgp summary 
get ver number 
then 
show ip bgp ipv4 version x
this can give you hint the prefix update with now ver

thanks 

MHM

[balaji.bandi]

the changes come from peer 10.164.22.9 (what is this peer ) - have you checked on this router ?

is this only specific to subnet, or entire routing table have less uptime ?

[Swathi K]

Hello Balaji,

That's managed by SP. Sent them a notification.

Not entire routing table only few routes.

Thanks.

[balaji.bandi]

Only that routes come from SP - may be expected on their routing change table ?

is this a worried  bit or is this causing any issue in the network ?

[paul driver]

Hello
You may need to dig deeper into why these prefixes have churned so as @balaji.bandi suggested move hop by hop towards the advertising rtr ( if applicable)

Choose one of those prefixes in your OP and go investigating!
The below commands should help, < table versions incrementing/ available (best) paths , routes that may be flapping etc... 
sh bgp ipv4 unicast  summary 
sh bgp ipv4 unicast  summary  | in table
sh bgp ipv4 unicast x.x.x. detail
sh ip route x.x.x.x detail
ping x.x.x.x source y.y.y.y
traceroute x.x.x.x numeric