netxms polling fails, no error/notification
-
Hi
I'm having mixed feelings when using netxms as I have several times thought that everything was working , and when I view the data from one node it can be marked as red for whatever reason (one example is that the poll is not supported on that node, or the netxms agent is not functioning properly). I suspect that it might be a user error on my part, but has anyone else experienced this and know how to avoid it? I really need to know if a poll has failed. It should trigger a notification.
-
Hi!
System will generate events in case anything goes wrong with the node - you can handle these events and create alarms, send notifications, etc. Most important events are following:
SYS_NODE_DOWN - entire node is down (NetXMS server cannot communicate using any allowed means)
SYS_NODE_UNREACHABLE - NetXMS server cannot communicate with the node because of intermediate router failure
SYS_NODE_UNMANAGED - someone put node into unmanaged state
SYS_NODE_UNKNOWN - status of the node is unknown
SYS_IF_DOWN - network interface is down
SYS_IF_UNKNOWN - status if network interface is unknown (usually because of disconnected agent)
SYS_IF_DISABLED - network interface was disabled
SYS_SERVICE_DOWN - network service is down
SYS_SERVICE_UNKNOWN - network service state cannot be determined (usually because of agent failure)
SYS_AGENT_UNREACHABLE - NetXMS agent is unreachable
SYS_SNMP_UNREACHABLE - SNMP agent is unreachable
SYS_DCI_UNSUPPORTED - DCI goes to "unsupported" state
SYS_SCRIPT_ERROR - NXSL script execution error
SYS_SMTP_FAILURE - server was unable to sent e-mail notification
SYS_SMS_FAILURE - server was unable to sent SMS notificationBest regards,
Victor -
Hi Victor, and thanks for your answer.
So one or more of these are not enabled in terms of showing a notification when something goes wrong?
I have used netxms for a while and it performs as expected as long as the poll values don't go red and show error. I only discover that something's wrong when I actually view the values manually.
Raymond
@victor said in netxms polling fails, no error/notification:
Hi!
System will generate events in case anything goes wrong with the node - you can handle these events and create alarms, send notifications, etc. Most important events are following:
SYS_NODE_DOWN - entire node is down (NetXMS server cannot communicate using any allowed means)
SYS_NODE_UNREACHABLE - NetXMS server cannot communicate with the node because of intermediate router failure
SYS_NODE_UNMANAGED - someone put node into unmanaged state
SYS_NODE_UNKNOWN - status of the node is unknown
SYS_IF_DOWN - network interface is down
SYS_IF_UNKNOWN - status if network interface is unknown (usually because of disconnected agent)
SYS_IF_DISABLED - network interface was disabled
SYS_SERVICE_DOWN - network service is down
SYS_SERVICE_UNKNOWN - network service state cannot be determined (usually because of agent failure)
SYS_AGENT_UNREACHABLE - NetXMS agent is unreachable
SYS_SNMP_UNREACHABLE - SNMP agent is unreachable
SYS_DCI_UNSUPPORTED - DCI goes to "unsupported" state
SYS_SCRIPT_ERROR - NXSL script execution error
SYS_SMTP_FAILURE - server was unable to sent e-mail notification
SYS_SMS_FAILURE - server was unable to sent SMS notificationBest regards,
Victor
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login