S/N/K-Series 'debug ip bgp update' output does not match EBGP Peer Updates

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 14823 

Products
S-Series, firmware 8.02.01.0012 and lower
Matrix N-Series DFE, firmware 6.01.01.0020 and higher
K-Series, firmware 8.02.01.0012 and lower 

Changes
From the router configuration CLI, issued the 'debug ip bgp update' command. 

Symptoms
BGP debug update information does not accurately reflect EBGP peer update activity.
Log output can show in excess of 40,000 routes withdrawn, when in fact there are only a few route changes. 

For example, with firmware 7.71.02.0005: 
N7(su)->router
N7(su-router)->configure
N7(su-router-config)->debug ip bgp update
<165>Sep 20 11:19:15 10.20.30.40 BGP[1]Router global: BGP: Update message
received from 24.148.233.137 withdrawn routes: 512
<165>Sep 20 11:19:15 10.20.30.40 BGP[1]Router global: BGP: Update message
received from 24.148.238.105 withdrawn routes: 512
<165>Sep 20 11:19:16 10.20.30.40 BGP[1]Router global: BGP: Update message
received from 24.148.233.137 withdrawn routes: 256
<165>Sep 20 11:19:16 10.20.30.40 Last message repeated 2 times
<165>Sep 20 11:19:16 10.20.30.40 BGP[1]Router global: BGP: Update message
received from 24.148.233.137 withdrawn routes: 42270
<165>Sep 20 11:19:16 10.20.30.40 BGP[1]Router global: BGP: Update message
received from 24.148.233.137 withdrawn routes: 26398
<165>Sep 20 11:19:16 10.20.30.40 BGP[1]Router global: BGP: Update message
received from 24.148.233.137 withdrawn routes: 44830
<165>Sep 20 11:19:16 10.20.30.40 BGP[1]Router global: BGP: Update message
received from 24.148.233.137 withdrawn routes: 512
N7(su-router-config)->exit
N7(su-router)->exit
N7(su)->
This is a display issue only - BGP functions correctly. 

Solution
For the S-Series, upgrade to firmware 8.11.01.0014 or higher.
For the N-Series, not expected to be fixed.
For the K-Series, upgrade to firmware 8.11.03.0005 or higher.
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.