Wired Intelligent Edge (Campus Switching and Routing)

Requirement:

This article discussed how to enable IPV4 BGP route debugging. 

In the following example, switches Rack2sw1 and Rack2sw2 are configured for BGP routing.

Debugging for IPV4 BGP routing is enabled on switch Rack2sw1. The loopback zero interface on switch Rack2sw2 is deleted and then added. This cause a BGP route CHANGE and ADD message to be sent to the BGP neighbor.
 

Rack2sw1# debug destination session
Rack2sw1# debug ip bgp route
Rack2sw1# show debug

 Debug Logging

  Source IP Selection: Outgoing Interface
  Origin identifier: Outgoing Interface IP
  Destination:
   Session

  Enabled debug types:
   ip bgp route

Rack2sw2(config)# no interface loopback 0
Rack2sw2(config)# interface loopback 0 ip address 2.2.2.2

0000:01:29:57.16 BGP  eRouteCtrl:CHANGE   2.2.2.2          255.255.255.255 gw
   192.168.12.2    BGP      pref 200/0 metric 0/100 vl1 <Int Ext Delete Gateway
   Unicast Resolve>  as 12
0000:01:29:57.36 BGP  eRouteCtrl:rt_close: 1 route proto BGP_12.192.168.12.2+179
   from 192.168.12.2

0000:01:30:02.06 BGP  eRouteCtrl:ADD      2.2.2.2          255.255.255.255 gw
   192.168.12.2    BGP      pref 200/0 metric 0/100 vl1 <Int Ext Gateway ActiveU
   Unicast Resolve>  as 12
0000:01:30:02.26 BGP  eRouteCtrl:rt_close: 1 route proto BGP_12.192.168.12.2+179
   from 192.168.12.2