Hello,
I have been experiencing a strange issue with Prizm ever since I upgrade from v 2.1 to 3.1
Any elements added when I was running 2.1 do not seem to experience this issue.
The issue is as follows. If I add a new element Prizm does not seem to populate the “Managment IP” field found under the Information->General tab. Tasks such as a Software Update that require IP communication seem to fail with a message stating that the element has an invalid IP address. Prizm is able to poll the element and SNMP functions seem to work.
If I go into Define Networks and “Modify Element IP and MAC” and enter the IP that I have assigned in the element Prizm seems to lose SNMP communication with the element. In the Events page I receive messages such as “Failed to Poll Network Element” and “Cannot access element via SNMP, SNMP access denied”. However Prizm still seems to authenticate the element and assign bandwidth parameters etc…
I think this may only be happening with SMs as I have recently added a few new APs and they do not seem to suffer from this problem.
Any thoughts?
Thanks
More annoying behavior from Prizm. As far as we could tell, the automatic discovery typically found the SM in linked mode, in other words, it found them through the AP.
We always had to delete the auto discovery entries and scan for the IP addresses to find the radios in SNMP mode for it to work at all.
As I’ve mentioned in the forums before, we have ditched Prizm for a system that we’re designing ourselves. It makes a few assumptions about how the network is deployed, but we have it refreshing the entire network on a regular cycle by SNMP scanning against the list of APs, collecting customer data from the radios and populating a database, geocoding the physical address that our installers put into the radio at installation, and plotting every radio in our network on a status map with colored dots to signify every client’s status.
It’s still pretty rough right now, but even as is it’s a far sight better than Prizm. At least we’ve got a management interface that responds to a click in under 30 seconds and we’re in close contact with the development team (us!).
rseibel wrote: Hello,
I have been experiencing a strange issue with Prizm ever since I upgrade from v 2.1 to 3.1
Any elements added when I was running 2.1 do not seem to experience this issue.
The issue is as follows. If I add a new element Prizm does not seem to populate the "Managment IP" field found under the Information->General tab. Tasks such as a Software Update that require IP communication seem to fail with a message stating that the element has an invalid IP address. Prizm is able to poll the element and SNMP functions seem to work.
If I go into Define Networks and "Modify Element IP and MAC" and enter the IP that I have assigned in the element Prizm seems to lose SNMP communication with the element. In the Events page I receive messages such as "Failed to Poll Network Element" and "Cannot access element via SNMP, SNMP access denied". However Prizm still seems to authenticate the element and assign bandwidth parameters etc....
I think this may only be happening with SMs as I have recently added a few new APs and they do not seem to suffer from this problem.
Any thoughts?
Thanks
Good to know I'm not the only one experiencing this issue. I've found two workarounds, neither of which are ideal for me but do work.
1) Enter the management IP of the units to be deployed PRIOR to them authenticating with Prizm for the first time. They will communicate happily.
2) Elements that didn't have the IP entered previously and are giving you SNMP errors you will need to delete and rediscover/readd. Make sure you get their management IP entered before they authenticate otherwise you will have to repeat the process.
Digging through the logs it seems that it wants to poll the elements via SNMP on the SNMP proxy port. I have no idea what causes it and I'm sure Moto doesn't either. It was working fine for me before the 3.1 upgrade as well. As I've had a lot of Prizm problems it's possible it happened during the 3.0 upgrade, but I really can't be certain, all I know is it doesn't work as designed. Very, very disappointed. We've got too much invested at this point and are too small to look at anything else so we just have to cope with it.
We ALWAYS program the radios before they leave the shop, with everything but customer specific info. Prizm still finds them linked and we have to delete them and manually scan for them.
Oh, wait…
Did you mean into the radios, or into Prizm?
And we never went to 3.1, we were at 3.0 when I gave up.
cvs wrote: We ALWAYS program the radios before they leave the shop, with everything but customer specific info. Prizm still finds them linked and we have to delete them and manually scan for them.
Oh, wait....
Did you mean into the radios, or into Prizm?
And we never went to 3.1, we were at 3.0 when I gave up.
We program our radios on the bench before deployment as well. I meant entering the IP information into Prizm prior to first authentication.
I have tried your suggestion of entering the IP address into Prizm before the first authentication and it appears to work.
Thanks for the help
We deployed nagios and we are happy with it. We have Prizm put honestly everyone prefers nagios. I believe we can code any features we want.
Prizm is resource hungry and so buggy
We’re using Groundwork community edition as the core of our new management system, which uses nagios at it’s heart. It’s really good stuff. Have a look at http://www.groundworkopensource.com/
Uncheck “Enable SNMP Proxy” in the Subnet portion of Define Networks for your network. I ran into this by accident once and wondered why IP addresses weren’t being assigned. If SNMP proxy is enable I believe all communications go through the AP.
salad wrote: Uncheck "Enable SNMP Proxy" in the Subnet portion of Define Networks for your network. I ran into this by accident once and wondered why IP addresses weren't being assigned. If SNMP proxy is enable I believe all communications go through the AP.
I wish it were that simple for me - that's never actually been enabled in my configuration.
Mine either.
Hi Everyone
Ask Motorola for Case_21605240_SM_Managment_IP_Workaround.zip
They fixed the same issue today on my Prizm Server with this file.
I can’t attach the file. But if someone want a copy let me know.
M. Huber
MMH-Consulting
Mine’s been working on and off lately. Half the time it will work as expected, the other half of the time it won’t work and I will have to delete/re-add the element.