Strange logs referring to Bug 11206 About SNMP Monitoring

Summary

In the Exinda logs, a series of strange notices from the process 'mgmt' are found, starting with a log message referring to Bug 11206 and then technical messages following. While this happens, the device does not allow any access (or very slow access) to the Web UI and CLI. This can occur when external SNMP requests are made of the Exinda.

Overview

The Exinda device allows for SNMP traps to be created in order for consolidation of all network alerts from various devices (versus using an independent protocol). It allows to sent SNMP alerts out through email or allows for them to be collected by an external monitor that can poll multiple devices that support SNMP simultaneously. In rare occasions, there could be a failure during these SNMP requests internally in the Exinda, leading to the following error message being shown in the Exinda logs:

"Management messaging violation. Did you query an external monitoring node from an internal monitoring node handler? See bug 11206. One of the involved messages to follow"
Followed by log lines of internal information relating to the error.

While this is occurring, the device can be slow to respond until the polling and attempt at processing the information has ceased. In some cases, the web GUI and the CLI will be completely unresponsive and will not allow any type of access.

Cause

This error is caused by how the Exinda internally handles SNMP requests generated from external sources (such as a SNMP polling program) and the processes involved in not only passing the SNMP request, but gathering the related information, which didn't cooperate with how SNMP was built in the Exinda. This bug is intermittent (eg, it can happen at some times and not at others) depending on the state of the processes, the Exinda firmware and the underlying kernel.

Resolution

In v7.4.0, the way that SNMP is handled has been changed and the internal-external monitoring nodes are no longer required, so this incorrect behaviour will no longer be an issue. Updating to this firmware will fix the problem.

Defect ID

D-02920

Defect URL

https://www4.v1host.com/Exinda/defect.mvc/Summary?oidToken=Defect%3A51154