Controller Based WLANs

Requirement:

How is OSPF flooding debugging enabled?

In the following example the IP address is removed and added from the Loopback 0 interfaces. The first debugging message is the flush message and the second message is the add message.

Rack2sw1# debug destination session
Rack2sw1# debug ip ospf flood
Rack2sw1# show debug

 Debug Logging

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

  Time-stamp: System-Uptime

  Enabled debug types:
   ip ospf flood
 

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

0000:01:15:00.56 OSPF eRouteCtrl:OSPF FLOOD: NGB 2.2.2.2 LIST ADD ACK Vertex
   AEX:2.2.2.2 [2.2.2.2] age 3600 <Flushing> rmx 0 rmx buf 0size 1 (qref 1)
0000:01:15:00.72 OSPF eRouteCtrl:OSPF FLOOD: ngb 2.2.2.2 not ready for Full yet
0000:01:15:00.81 OSPF eRouteCtrl:OSPF FLOOD: state is Full not Loading
0000:01:15:00.88 OSPF eRouteCtrl:OSPF FLOOD: NGB 2.2.2.2 LIST NEXT ACK Vertex
   AEX:2.2.2.2 [2.2.2.2] age 3600 <Flushing> rmx 0 rmx buf 0size 0 (qref 0)

0000:01:15:33.26 OSPF eRouteCtrl:OSPF FLOOD: NGB 2.2.2.2 LIST ADD ACK Vertex
   AEX:2.2.2.2 [2.2.2.2] age 1 <> rmx 0 rmx buf 0size 1 (qref 1)
0000:01:15:33.41 OSPF eRouteCtrl:OSPF FLOOD: ngb 2.2.2.2 not ready for Full yet
0000:01:15:33.50 OSPF eRouteCtrl:OSPF FLOOD: state is Full not Loading
0000:01:15:33.57 OSPF eRouteCtrl:OSPF FLOOD: NGB 2.2.2.2 LIST NEXT ACK Vertex
   AEX:2.2.2.2 [2.2.2.2] age 1 <> rmx 0 rmx buf 0size 0 (qref 0)