Wireless Access

Can you reset them remote? (there all over the country)

tried via airwave to reprovision/put in another group etc

 

Im new so hopefully this is an easy question. Tried to connect to them with telnet/ssh but no success

 

Thanks!

 

btw a purgeenv seems to get them back online but since I can't physical access them this is a problem

Karin, 

 

Can you provide a little more detail of your setup?  Specifically:

 

- What was involved with the failover test?

- Are these RAPs or CAPs?

- How are the APs discovering the controllers, DNS, DHCP Option 43, ADP?

- What parameters did you attempt to change via Airwave and the like besides AP-Group?

- Assuming you have 2 controllers, are the APs showing up under "show ap database" on either controller?

 

Regards, 

Austin

we shut the port on the core where one of the master controllers was located, then all the aps moved to the other controller

we gave a no shut and everything seemd okey meaning we lost two pings and were still connected to the ap

Then something went wrong because the aps seem to move back to there default controller so we rebooted the master

Then 90% of the aps connected to the default again but 10 cant seem to connect again

 

ap-105

 

were can you see the order of discovering? I think DNS first 

 

tried reprovisioning and import settings (dont know what else to try)

 

4 two master en two local  on the show ap database they apear as "down" with no Flags on one of the controllers on the other there are no aps 

 

Thanks again

Karin,

 

Are the 10 APs in one location or multiple locations? For the APs not reconnecting, can you confirm from DHCP (assuming you are running DHCP) that the APs do have an IP address and is pingable at least?  If remote access to the APs are not enable, you will not be able to get access to them via the network, only via console to see what's happening in the boot process.  Is it possible to access one of the APs via a console cable?

 

-Mike

Aps with status down (no longer associated with controller) are all pingable unlike the rest of the ap's that are functioning correctly (their NOT pingable)

ap's are physically located throughout the country

 

How do you enable remote access?

 

Tomorrow we posible have a man onsight who can access one via the console to see whats happening

 

thanks!

You can enable remote access via the AP System Profile.  However, you may have to reach out to support for additional info on access the CLI.  You can telnet to it but it does not allow any access. I believe there is an escape seq to get access so you can view the configuration parameters.  Console access is probably your best bet.

 

-Mike

Is there anything in common about the 10 APs that didn't come up?  Like, are they all in one site, or are there one or two APs in a bunch of sites that didn't come back?  If there are other APs that are up in the same site, same VLAN and same AP group, then it's mostly likely not a controller discovery or LMS setting issue.

 

Reprovisioning the APs that are down right now isn't going to do anything.  They have to be connected to a controller for that to have an effect.

 

Are the APs connected to a switch that's providing PoE or are you using inline power injectors?  If they are on a switch, try shutting the port down then bring it up after about 30 seconds.  That will power cycle the AP.

Solved. the 10 ap's tried to get a certificate from the controller behind the firewall after a failover occured. so  be aware that udp 8211 has to be added in the firewall from the local controller (vrrp and real addresses) to the ap105's  (and ofcourse the other way around but that was already configured)

 

be aware that communication from ap to local controllers connects on the vrrp address and the replys from the local controllers to the accesspoints origin from the real addresses

You cannot do this remotely. You can SSH into the controller that they were last on and type "show audit-trail" to see if the ip address of the controller was hard coded to something unreachable.