Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3520
  • Last Modified:

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

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.
Fry-Wireless-Issue.docx
0
gcdesktop
Asked:
gcdesktop
  • 4
  • 3
1 Solution
 
asavenerCommented:
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?
0
 
asavenerCommented:
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.
0
 
gcdesktopAuthor Commented:
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
0
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

 
asavenerCommented:
OK....

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.
0
 
gcdesktopAuthor Commented:
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.
0
 
gcdesktopAuthor Commented:
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.
0
 
gcdesktopAuthor Commented:
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.
0

Featured Post

Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now