Problem:1. Why am I seeing PAPI traffic from an AP on a controller when it is provisioned to other controller?
2. I have configured my controller for HA. why I can see PAPI traffic but I do not see the standby GRE tunnel?
Diagnostics:1. We see the PAPI traffic from the AP but no GRE:
(local-5) (config) #show datapath session table 10.1.1.251
Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge Packets Bytes Flags
--------------- --------------- ---- ----- ----- -------- ---- --- --- ----------- ---- --------- --------- ---------------
10.1.1.251 10.1.1.5 17 8211 8211 1/0 0 0 0 1/0 0 2 2856 FCI
10.1.1.251 10.1.1.5 17 8211 8222 1/0 0 0 0 1/0 0 0 0 FYCI
10.1.1.5 10.1.1.251 17 8211 8211 0/0 0 0 0 1/0 0 0 0 FYI
10.1.1.5 10.1.1.251 17 8222 8211 0/0 0 0 0 1/0 0 0 0 FYI
2. We need to verify the ha group membership of the controller:
(local-5) (config) # show ha group-membership
Controller member of HA group:
Also, sometimes the controller would be mapped with incorrect GA group profile.
SolutionWe see that the above controller is not a member of a HA group. We need to make this controller member of correct HA-group.
(local-5) (config) #ha group-membership new
(local-5) (config) #show ha group-membership
Controller member of HA group: new
Once this is done, the AP and controller will negotiate HA parameters and standby GRE tunnel between this controller will come up.
After the controller is mapped to the correct Ha group:
1. PAPI traffic will not show up in datapath anymore.
2. We will start seeing GRE (47) traffic after the correct configuration has been applied:
(local-5) (config) #show datapath session table 10.1.1.251
Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge Packets Bytes Flags
--------------- --------------- ---- ----- ----- -------- ---- --- --- ----------- ---- --------- --------- ---------------
10.1.1.251 10.1.1.5 47 0 0 0/0 0 0 0 1/0 2b 27 2376 FC
10.1.1.5 10.1.1.251 47 0 0 0/0 0 0 0 1/0 2b 27 2376 F