Guest

Preview Tool

Cisco Bug: CSCvu32113 - 1562 MAP does not create or keep adjacency with RAP from Mobility Express WLC

Last Modified

Oct 09, 2020

Products (1)

  • Cisco Aironet 1850 Series Access Points

Known Affected Releases

8.10(112.0) 8.10(121.0) 8.10(138.45)

Description (partial)

Symptom:
This defect refers to the MAPs behaviour when joining a RAP where the RAP is the AP instance of a Mobility Express controller.

If the backhaul is on 5GHz and the 2.4GHz band is disabled, the MAP will lose adjacency and will not come back. Both bands need to be enabled in order for the 5GHz backhaul to stay UP.

Radio Backhaul: 1 [70:B3:17:CF:0F:B1]
Hops to Root: 1
idx State Role   RadioState Cost Uplink Downlink Access ShutDown ChildrenAllowed BlockChildState InterfaceType
2   MAINT UPLINK UP         6566 TRUE   TRUE     FALSE  FALSE    TRUE            ALLOWED         RADIO
Mesh AWPP Radio adjacency info
Flags: Parent(P), Child(C), Neighbor(N), Reachable(R), CapwapUp(W),
       BlackListed(B), Authenticated(A), HTCapable(H), VHTCapable(V)
       OldParent(O)
Address           Cost RawCost LinkCost ReportedCost Snr BCount Ch  Width  Bgn Flags: P O C N R W B A H V Reject reason
70:B3:17:88:D6:F1 6566 8208    8192     16           19  0      149 20 MHz     (T/F): T F F T T T F T T T -
 
If the MAP is connected via the 5GHz and is rebooted, it will not reconnect either unless the Ethernet is reconnected and then disconnected again.

[*04/24/2020 20:13:18.9258] EVENT-MeshControl: GW Reachability timed out, DHCP wait count [9]. Blacklist parent

EVENT-MeshWiredBackhaul[0]: Blacklisting Parent

CRIT-MeshWiredAdj[0][70:B3:17:06:90:A6]: Blacklisting Adjacency due to GW UNREACHABLE

CRIT-MeshWiredAdj[0][70:B3:17:06:90:A6]: Remove as Parent

EVENT-MeshWiredBackhaul[0]: Sending LINK_DOWN to MeshLink


Gateway is reachable and working, no issues at all for RAP.

Same configuration works on 8.10.105.0 either when rebooting MAP or when disabling 2.4GHz.

Conditions:
RAP in Mobility Express mode.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.