NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Adding WAC720 to Managed AP List in WC7500
Background 4 x WAC720 Access Points and 1 x WC7500 controller were sourced second hand for a SOHO environment. To ensure starting at a known baseline, the WAC720s were converted back to stand-alone...
Hi Raghu,
Thank you for coming back to me with a couple of suggestions.
Regarding your suggestion B –AP is in standalone mode.
All my previous attempts of moving the APs from standalone to managed mode have followed your suggested steps (as per Netgear documentation). Refer the back ground description in my original post. Note though, when I connected the AP (flashing amber) directly to my PC and Hard Reset the AP, the AP returned to flashing amber (refer Telnet output at end in original post). I could not obtain access to the AP via the web interface. My only option to regain control of the AP was to interrupt the boot process and re-flash the AP and then reconfigure to standalone as per documentation. All the APs were confirmed to operate in standalone mode.
Regarding your suggestion A – AP in Controller managed mode.
Following Discovery and attempting to Add APs to Managed List, I have never been able to move past flashing amber on the AP without re-flashing the AP. Thus, I was never able to confirm that the AP was in Controller managed mode. Note though, both Factory and Standalone discovery options always discovered the APs.
Work-around
An AP (flashing amber) that was in the managed list but failed to connect was hard reset whilst connected to the simple lab network (and consequently the Controller). To my surprise the AP went into constant green and connected to the Controller!
The remaining 3 APs (flashing amber), not in the managed AP list because they were previously deleted from the list, were connected to the simple lab network. Each AP was hard reset on the network and the APs went into constant green. I did not alter the APs configuration as suggested. The Standalone AP wizard found the 3 AP’s and then the APs were added successfully!
It would appear that following the first failed attempt to add standalone APs to the managed list, the APs must be hard reset whilst connected to the network. No AP configuration is performed. The controller is then able to reconnect to the APs which are mentioned in the managed list, or discover the APs as Factory APs and then successfully add the APs to the managed list.
I’ve deployed the APs and Controller to the network proper. All seems to be working well thus far. Thank you for your support.
Hi AudiM
If you have not followed these steps then check the below 2 options which can help you to configure Static IP address, Just mentioned 2 ways depends on the current AP state.
A. AP in Controller managed firmware
- Hard reset the AP by pressing Reset button more than 10 seconds
- After the hard reset, AP will get assigned to default IP 192.168.0.100
- Login to AP using default IP i.e 192.168.0.100 (by configuring laptop with static IP 192.168.0.xx)
username "admin" and password is "password"
4.Configure the static ip address:
IP Address : According to your network
Subnet mask: According to your network
Default Gateway: According to your network
Primary DNS Server -According to your network
- Apply the changes.
- Go to Controller scan for the WAC720 AP by providing AP IP range
- Controller will discover the WAC720 AP and please add the AP to the network.
- Controller will upgrade AP with WC7500 light firmware and will push wc7500 configuration to AP and then Controller will Reboot the AP.
B. AP is in Standalone Mode
- Hard reset the AP by pressing Reset button more than 10 seconds
- After the hard reset, AP will get assigned to default IP 192.168.0.100
- Login to AP using default ip i.e 192.168.0.100 (by configuring laptop with static ip 192.168.0.xx)
username "admin" and password is "password" ( You may need to change the default password)
- Upgrade AP to standalone FW V3.9.1.0 from Maintenance -> upgrade -> Firmware upgrade
- After the upgrade successful login to AP and disable business central enabled option.
- AP will reboot and once it comes back, enable the SNMP option.
7.Configure the static ip address:
IP Address : According to your network
Subnet mask: According to your network
Default Gateway: According to your network
Primary DNS Server -According to your network
- Apply the changes
- Go to Controller scan for the WAC720 AP by providing AP IP range
- Controller will discover the WAC720 AP and please add the AP to the network.
- Controller will upgrade AP with WC7500 light firmware and will push wc7500 configuration to AP and then Controller will Reboot the AP.
Do let us know your feedback once you follow this.
Thanks,
Raghu
Hi Raghu,
Thank you for coming back to me with a couple of suggestions.
Regarding your suggestion B –AP is in standalone mode.
All my previous attempts of moving the APs from standalone to managed mode have followed your suggested steps (as per Netgear documentation). Refer the back ground description in my original post. Note though, when I connected the AP (flashing amber) directly to my PC and Hard Reset the AP, the AP returned to flashing amber (refer Telnet output at end in original post). I could not obtain access to the AP via the web interface. My only option to regain control of the AP was to interrupt the boot process and re-flash the AP and then reconfigure to standalone as per documentation. All the APs were confirmed to operate in standalone mode.
Regarding your suggestion A – AP in Controller managed mode.
Following Discovery and attempting to Add APs to Managed List, I have never been able to move past flashing amber on the AP without re-flashing the AP. Thus, I was never able to confirm that the AP was in Controller managed mode. Note though, both Factory and Standalone discovery options always discovered the APs.
Work-around
An AP (flashing amber) that was in the managed list but failed to connect was hard reset whilst connected to the simple lab network (and consequently the Controller). To my surprise the AP went into constant green and connected to the Controller!
The remaining 3 APs (flashing amber), not in the managed AP list because they were previously deleted from the list, were connected to the simple lab network. Each AP was hard reset on the network and the APs went into constant green. I did not alter the APs configuration as suggested. The Standalone AP wizard found the 3 AP’s and then the APs were added successfully!
It would appear that following the first failed attempt to add standalone APs to the managed list, the APs must be hard reset whilst connected to the network. No AP configuration is performed. The controller is then able to reconnect to the APs which are mentioned in the managed list, or discover the APs as Factory APs and then successfully add the APs to the managed list.
I’ve deployed the APs and Controller to the network proper. All seems to be working well thus far. Thank you for your support.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
