SNMP Alarm Name With PRTG

[phonebooth]

Hi everyone,

We run a fleet of Mitel 3300s and have been trialling PRTG for monitoring them. We use MPA for our 3300s with premium SWA. I'm facing some issues and wondering if anyone has come across the same.

When using mitel ipera3000cat tbl name / 1.3.6.1.4.1.1027.4.1.1.2.2.4.1.8 to obtain the system alarm name, PRTG returns "No response" which causes the sensor to go into a down state. This is because the 3300 doesn't have an active alarm. If the 3300 has an alarm, the sensor pulls the correct alarm name, displays it within PRTG and places the sensor into an "OK" state.

I've contacted PRTG support and they've indicated this is correct behaviour, which makes sense. No alarm, nothing to retrieve, poll fails and displays a "Down" state in PRTG. They've also indicated this is a "very uncommon approach for SNMP".

For those that have products like SolarWinds, Zabbix etc have you managed to get this working? If so, how did you achieve it?

Cheers!

[Dogbreath]

Because it responds with "No Such Instance currently exists at this OID" , Zabbix marks the item as Unsupported, which means that it then demotes its polling interval to 10 minutes. So no, I haven't really "handled" it with Zabbix, as such. I might actually be able use it in this state so long as a 10 minute delay was acceptable.
I trigger on mitelIpera3000AlmLevel and then investigate as needed.

They're not wrong about it being an uncommon approach to implementing an SNMP agent - if anything, I think their response is way too diplomatic :-)

[phonebooth]

Thanks for your response! I was trying to avoid that, but I guess we'll also have to follow the alarm level only approach. I wonder how MarWatch have implemented it for Mitel.