cisco wireless ap
hello experts
i have some autonomous Cisco wireless AP, i need update them to lightweight, i did it from remote and successful, but i can't access it after update, neither telnet or ssh, i could only ping it, for the reason of controller located in another subnet, so i have to climb to the roof via ladder connect console to each device configure it connect to controller, that is not convince, for have so many devices.
my question is how i can access it after update.
thank you
i have some autonomous Cisco wireless AP, i need update them to lightweight, i did it from remote and successful, but i can't access it after update, neither telnet or ssh, i could only ping it, for the reason of controller located in another subnet, so i have to climb to the roof via ladder connect console to each device configure it connect to controller, that is not convince, for have so many devices.
my question is how i can access it after update.
thank you
Sandeep Gupta
once you convert AP to lightweight, either you need to re-provision it through controller or you need to console it directly. If not try to do factory reset physically and also check AP port configuration connected to SW, its vlan and dhcp setting it must have controller ip in option 43.
DHCP Option 43 will sort it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hello
could you let me know how to configure DHCP option 43? just add controller IP address to ACSII field? i did try it but doesn't work, AP get IP address from DHCP server but don't know controller IP address to communicate.
for the DNS setting, i did add an A record for CISCO-CAPWAP-CONTROLLER.my
thank you
could you let me know how to configure DHCP option 43? just add controller IP address to ACSII field? i did try it but doesn't work, AP get IP address from DHCP server but don't know controller IP address to communicate.
for the DNS setting, i did add an A record for CISCO-CAPWAP-CONTROLLER.my
thank you
thats fine if you your controller IP as option 43 or dns domain.
to configure option 43, refer:
https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/97066-dhcp-option-43-00.html
to configure option 43, refer:
https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/97066-dhcp-option-43-00.html
DNS is an option but option 43 is the preferred way. I never recommend using DNS.
ASKER
hello
i have all my AP devices upgraded and connected to controller, so i can't test it with DHCP 43 options so i will accept the DNS option as the best solution for this case.
thanks all of yours help.
i have all my AP devices upgraded and connected to controller, so i can't test it with DHCP 43 options so i will accept the DNS option as the best solution for this case.
thanks all of yours help.
ASKER
thank you