I have a cmm micro that quits responding to the public IP address. It was upgraded to 2.1.1 firmware. When the unit is rebooted it comes up for a few minutes maybe an hour and then stops responding to the IP (snmp querie, and cannot be reached by the http interface) . The traffic from the 2 BH’s and the 4 AP’s continue to work. One time it went for several days and then everything drops out (BH’s and AP’s). Once the unit is rebooted again it comes back and the cycle starts over. I have been able to turn off the ethernet port on the ethernet switch that is used as an uplink for the cmm and then turn it on again and some traffic starts to flow from the ap’s and the bh’s for a few seconds and then fails again until the CMM is rebooted. We have switched out the cmm and the new one acts the same. Any ideas on what is happening
You say that it does not respond to a public IP. I assume you mean that you assinged the CMM Micro a public IP address. This issue sounds all too familiar to the same problems that many people are having when assigning their modules public, routable addresses.
Everyone’s fix seems to be to assign the modules private addresses that can’t be reached from the internet. I personally experienced the issue with our APs. The web interface did not lock up, but the modules seemed to reset themselves many many times. I switched back to private addresses and everything was fine.
Hope that helps,
The addresses that we are using are in a private range and they are all nat’d out of the network. on the SM’s we have the ‘public’ access checked so we can get them from the LAN. So we are using the same addresses on the CMM’s we have 5 others that are working flawlessly. This one is probably the heaviest used cmm. Does that have any affect on why it just shuts down?
We are seeing a similar problem. We have a CMM that is passing customer traffic but is not reachable through it’s manamement IP address via ping or WebUI. Our CMM also uses a private IP address for management.The problem seems to clear-up after rebooting the CMM but that’s not a workable solution.
Is there a known bug with the CMM becoming unresponsive? It doesn’t seem the solution to rwardell’s problem was wrapped up in this thread.
Yes, there is a known issue with CMM Micro lockups and a new software package containing the fix is in the process of being created. I do not have a release date at this time.
I just keep requesting time from the CMM Micro and Png it every 1 minute and it never seems to drop out for me anymore.
Canopy_Support wrote: Yes, there is a known issue with CMM Micro lockups and a new software package containing the fix is in the process of being created. I do not have a release date at this time.
Why is not this issue in knowlegde base? We spent a lot of time by finding solution - everything uselessly :(.
The lockup only occurs on the management side and does not stop the flow of traffic. This is a newly identified issue and an article will be posted to the knowledge base soon.