Guest

Preview Tool

Cisco Bug: CSCta09996 - Sometimes LAP can't join to WLC via alternative port in port redundancy

Last Modified

Jun 30, 2016

Products (1)

  • Cisco 5500 Series Wireless Controllers

Known Affected Releases

4.2(176.0) 4.2(187.0)

Description (partial)

Symptom:

Sometimes LAP can't join to WLC via alternative port in port redundancy environment.

Conditions:

<topology>

Issue is happened port redundancy environment without LAG.

  +---------------+G1/0/1    192.168.0.2(Po1)+-----------------+
  | catalyst-PoE  +--------------------------+                 |
  |               |                          |   WLC 4400      |
  | 192.168.0.254 +--------------------------+                 |
  +---+-----------+G1/0/2    192.168.0.3(Po2)+-----------------+
      |
      |---- LAP1142 (IP is assigned via DHCP)
      |---- LAP1242 (IP is assigned via DHCP)
      |---- LAP1132 (IP is assigned via DHCP)

<reproduce steps>

1) execute shut down on G1/0/2 interface of catalyst. 
    This step is preparing LAPs join to the LWC4402 via 192.168.0.2(Po1)
2) Power on all of LAPS, confirm all LAPs join to LWC4402 via 
    192.168.0.2(Po1)
3) execute "no shut down" on G1/0/2 interface of catalyst..
4) execute "shut down" on G1/0/1 interface of catalyst..

In many cases, one of LAP could not join to WLC4402 via Po2. Console logs indicate that such LAP try to join via old(Po1) ip address(192.168.0.2) of WLC.
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.