Recommended Posts

Hi Everybody,

I'm having a major issue with my HP Procurve MSM760 access controller and MSM460/MSM410 access points.

This actually seems to be an issue everywhere I have these set up, but this location does it more frequently than others.

Once I boot up the control unit and the AP's provision themselves (there's about 15 of them however only 5 are currently active, a mix of 410's and 460's) the wireless network broadcasts and runs flawlessly as it's supposed to. The problem starts at about 1-2 weeks of uptime. At this point, the access points are still broadcasting the SSID, however they are not allowing DHCP to be passed from the AC. I know DHCP is still working on the controller because I can release access points and have them obtain new IP addresses. Rebooting my POE switches doesn't help either. The only thing that fixes this is a hard reboot of the access controller. I've checked the logs, and nothing unusual. No error messages... at all.

I have 1 MSM760 and 5 MSM710's. This issue happens on all of the access controllers with the exception of one 710 which has had a 2 year uptime (although this one is on a much lower revision of the firmware). I know its not the configuration as it is basically identical to the only MSM710 that works at one of my other locations with the exception of passwords and SSID name.

What gives? Is HP wireless equipment really that crappy? Should I have used Cisco?

Sorry for making it seem like I rushed writing this... mainly because I did. I need to get this fixed today as the Volkswagen Germany CEO is visiting our VW/Audi store next week and his team wants wireless.

Link to comment
https://www.neowin.net/forum/topic/1111335-hp-msm760-major-issues/
Share on other sites

Hi Everybody,

I'm having a major issue with my HP Procurve MSM760 access controller and MSM460/MSM410 access points.

This actually seems to be an issue everywhere I have these set up, but this location does it more frequently than others.

Once I boot up the control unit and the AP's provision themselves (there's about 15 of them however only 5 are currently active, a mix of 410's and 460's) the wireless network broadcasts and runs flawlessly as it's supposed to. The problem starts at about 1-2 weeks of uptime. At this point, the access points are still broadcasting the SSID, however they are not allowing DHCP to be passed from the AC. I know DHCP is still working on the controller because I can release access points and have them obtain new IP addresses. Rebooting my POE switches doesn't help either. The only thing that fixes this is a hard reboot of the access controller. I've checked the logs, and nothing unusual. No error messages... at all.

I have 1 MSM760 and 5 MSM710's. This issue happens on all of the access controllers with the exception of one 710 which has had a 2 year uptime (although this one is on a much lower revision of the firmware). I know its not the configuration as it is basically identical to the only MSM710 that works at one of my other locations with the exception of passwords and SSID name.

What gives? Is HP wireless equipment really that crappy? Should I have used Cisco?

Sorry for making it seem like I rushed writing this... mainly because I did. I need to get this fixed today as the Volkswagen Germany CEO is visiting our VW/Audi store next week and his team wants wireless.

We have a MSM760 and have had nothing but problems with it. Are you on the latest firmware, that's about all I can suggest? We are running 5.7.1.0. There have been numerous firmware updates on the 760. Right now it seems to be running well, but we've only been running for 8 days and our setup is different. Our domain controller does the DHCP for us unless you connect to a guest network which we don't have working totally. (Or if you are set up the same way, we haven't had those issues).

We are thinking about switching with Meraki if we can work out a deal to get rid of our HP stuff. Sooo much easier to set up and troubleshoot issues. And the reports are nice.

I don't have that option... most of my stuff is over a year old or beyond the return policy. I have the 760 assigning DHCP. I have 8 vlans with 24 bit subnets each running there... the two primaries already have 200+ devices each and I doubt it would be able to handle the wireless.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
    • So how did you solve the problem? Disabling Secure Boot isn’t a solution.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!