Solved

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

Posted on 2013-01-18
7
3,236 Views
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.
Fry-Wireless-Issue.docx
0
Comment
Question by:gcdesktop
  • 4
  • 3
7 Comments
 
LVL 28

Expert Comment

by:asavener
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?
0
 
LVL 28

Expert Comment

by:asavener
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.
0
 

Author Comment

by:gcdesktop
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
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
LVL 28

Expert Comment

by:asavener
ID: 38794152
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
 

Author Comment

by:gcdesktop
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.
0
 

Accepted Solution

by:
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.
0
 

Author Closing Comment

by:gcdesktop
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.
0

Featured Post

Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

Question has a verified solution.

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

Suggested Solutions

DECT technology has become a popular standard for wireless voice communication. DECT devices are not likely to be affected by other electronic devices and signals because they operate in a separate frequency-band.
Most of the applications these days are on Cloud. Cloud is ubiquitous with many service providers in the market. Since it has many benefits such as cost reduction, software updates, remote access, disaster recovery and much more.
Internet Business Fax to Email Made Easy - With  eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, f…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

828 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