Replacing 4402s with 4404 controllers.

Unanswered Question
Jan 9th, 2009

I will be replacing a couple of 4402s with 4404 controllers. I have never worked with this before, so I would appreciate any tips, pointers, or "gotchas" that anyone could offer. There are about 50 existing APs.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Stephen Rodriguez Fri, 01/09/2009 - 07:10

Good thing here, is if you are running LAG, you should be able to upload the current config, and then download to your new controller. If you can do this in a non-live environment, you can then just switch out the two units.

Otherwise, you're best off doing a stare and compare to make sure you have everything configured the same.


Steve Fri, 01/09/2009 - 07:23

2 questions:

1. What is the significance of running LAG. I know this is port aggregation, but what is the significance in this case?

2. What is the versions of code are different? Say 4.0.xx on the 4402 and 4.2.xx on the 4404?

Thanks for the reply.

Stephen Rodriguez Fri, 01/09/2009 - 08:41

LAG just sets all the ports to be the logical channel number, if you don't have LAG enabled, then all the interfaces will remain linked to the port you had them set to previously. Not a huge issue going from a 4402 - 4404.

As for the code, on the download of the config, the WLC should parse and do whatever upgrades/manipulations needed to get the config to what 4.2 would expect. On that note, make sure you can upgrade directly from the 4.0 release you are running to the 4.2 release the 4404 is running, release notes will tell you this.




This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode