Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


HP wireless MSM410 Access points showing not detected after controller reboot.

Posted on 2013-01-18
Medium Priority
Last Modified: 2013-03-02
I have a crazy problem going on and I cannot seem to figure this out. I have 2 HP controllers MSM760’s Teamed and about 194 HP msm410 access points. I currently have 3 VSCs (guest, BYOD, Managed). Yesterday one of the controllers supposedly locked up according to the new guy and he restarted both controllers because they are teamed and that’s what we have done in the past. After they restarted one of our campuses show red X’s on the access points. I can ping the AP’s so they are there but not showing up on the controller. Under controlled access points we have groups set up and each group represents a campus and when I select the group in question (Fry Campus) The first tab is discovered AP’s none of the Aps show up. When I select the configured Aps tab they all Say not detected and have red X’s by them. I CAN ping these Access Points. Now I was over at that campus and decided to plug one of the AP’s into a different port with a different VLAN and to my surprise it showed up on the controller and synchronized like nothing was wrong. Now that to me seems like a VLAN issue but I’ve been through the configs on the campus switches and I took my laptop over and plugged into the port where the AP was at before and I got internet access so I am completely lost. It seems now that the quick fix would be to create a new VLAN for the Access Points and go on but I would rather solve this issue. Any help ideas or simply a shove in the right direction would be greatly appreciated. I can post screen shots if needed.
Question by:gcdesktop
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
LVL 28

Expert Comment

ID: 38793886
Sounds like maybe an interface reset on the AP could be what fixed it.

What happens if you power cycle the AP, shut/no shut the switch port, or just unplug and plug back into the same port?

Is the VLAN firewalled in some way?
LVL 28

Expert Comment

ID: 38793898
I know that we've had problems in the past managing thin clients, because the management console communicates with them via multicast.  Maybe resetting the interface made it rejoin the multicast group.

Author Comment

ID: 38794098
Thanks for the response. Power cycleing the APs do not work I tried that and ive also done shut/no shut on the switchport as well. They do not show up on the controller unless I move them to another VLAN. I know that sounds crazy. We have around 25 Access points at that school and they all messed up at the same time. They are all scattered out around the school in different switches but in the same VLAN. The two that I show up in the controller now were moved to another VLAN but I need to figure out why they do not work in the original VLAN. Thanks I hope im making a little sence
Simplify Your Workload with One Tool

How do you combat today’s intelligent hacker while managing multiple domains and platforms? By simplifying your workload with one tool. With Lunarpages hosting through Plesk Onyx, you can:

Automate SSL generation and installation with two clicks
Experience total server control

LVL 28

Expert Comment

ID: 38794152

So, routing appears to be OK, since you can ping the APs.

The only thing I can think of is that some sort of packet filter or firewall is blocking the management traffic.

Author Comment

ID: 38811586
I'm working with HP on the issue. We don't have anything filtering internal traffic except maybe the controller. Something has screwed up the connection between the controller and access points on the one group but physically they should be able to talk.

Accepted Solution

gcdesktop earned 0 total points
ID: 38926270
The DNS server was not functioning correctly and the DHCP scopes for the VLANS associated with the wireless did not have a secondary address therfore I could ping them by IP but they did not have internet capability. I added our backup DNS server address to the DHCP scopes in question and had imediate resolve. This work around gave us the time needed to solve the DNS issue and provided redundancy.

Author Closing Comment

ID: 38944823
I solved the issue on my own however I did not have enough info to guide the others in the right direction. This turned out to be a server issue and not wireless.

Featured Post

Plesk WordPress Toolkit

Plesk's WordPress Toolkit allows server administrators, resellers and customers to manage their WordPress instances, enabling a variety of development workflows for WordPress admins of all skill levels, from beginners to pros.

See why 2/3 of Plesk servers use it.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Arrow Electronics was searching for a KVM  (Keyboard/Video/Mouse) switch that could display on one single monitor the current status of all units being tested on the rack.
This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
Suggested Courses

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question