Cisco 5508 questions related to changing IP address scheme

Started a new company where there is a Cisco 5508 with 12 APs.  I've always done autonomous AP.  Previous guy had controller siting on outside network in a single WLAN and single SSID.  New design calls for trunking to carry multiple SSIDs and moving all network cables to a chassis switch instead of having a physically separated switch for outside connections

Question - The AP's and 5508 controller have IP addresses that will need to be changed.  Which is done first.  Update all APs, then unplug/power down and move, then re-IP controller?  I'm also assuming all the AP connections have to move into a trunk configuration, too.
LVL 1
finfrockgAsked:
Who is Participating?
 
Dangle79Connect With a Mentor Commented:
Our APs are on our native vlan (10.1.x.x/16) but our controllers are actually on a separate management vlan (10.4.0.x)
The APs are assigned static addresses but when their fresh out of the box they'll pull dhcp to get started, and in either case will always hit DNS to find a controller.
In some configurations people enable telnet to the APs themselves, that'd be why they'd like to keep static addresses on them. For us, we don't, so I couldn't tell you why the decision was made to run static, i wasn't the one who set it up.
Screenshot is from the interface setup on my 5508. We don't use the service port, that's why it's 0.0.0.0, we've got our private 10.1 network and a public vlan defined.
Another thing i forgot to mention, if you're going to use LAG one the controller you'll want to configure a port-channel on the switch. We use a dual link port channel for ours just for redundancy
Capture2.PNG
0
 
Dangle79Commented:
the AP connections do not need to be on a trunk. they tunnel all their traffic back to the controller on their own.

i'm not sure about the order of operations to change the IPs. the lightweight APs will pick up their IP configuration from the controller when they boot up. So you can probably update the AP addresses in the controller first, save that config, then readdress the controller, then plug into your new switch etc then power on.

you WILL however have to trunk the lines from the switch to the WLC though if you will have SSIDs across multiple vlans such as a public access hotspot
0
 
Dangle79Commented:
OH, also make sure you've got an entry in your DNS for cisco-capwap-controller pointing to the controller's management IP

when the APs first boot up they'll grab a DHCP number and resolve the DNS entry to locate a controller to join to. i assume all APs are already in the auth list in the WLC
0
 
finfrockgAuthor Commented:
WLC will betrunked.  APs are in access mode not trunked but do they have to be on native VLAN as WLC or does it not matter?   My APs have static addresses.  Not sure why that was so important.  
I wasn't sure where that static address actually is retained in the controller or WLC.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.