Monitoring

SNMP Traps

SNMP traps with anynode are automatic notifications sent by anynode to an SNMP monitoring system (e.g., PRTG, Zabbix) whenever specific events or issues occur.

Instead of constantly polling the status, anynode pro actively reports errors, warnings, or critical states (e.g., connection issues, license alerts) directly to the monitoring tool. This saves resources and ensures administrators are immediately informed when something goes wrong.

Windows

Install SNMP Service (if not already installed).

Start and configure the SNMP Service:

Open Windows Services:

Press Win + R and type services.msc

Locate and start the SNMP Service.

Go to the SNMP service properties:

Under the Security tab:

Add the community name public and set access permissions (usually READ ONLY or READ WRITE).

Add the IP addresses of SNMP management systems allowed to receive traps.

Under the Traps tab:

Add the community name public and click Add to list.

Enter the IP addresses of SNMP management systems allowed to receive traps.

Windows services with SNMP service properties and traps settings.

Restart the SNMP service.

Navigate to SNMP Trap below.

Start the SNMP Trap service.

It is recommended to always set the SNMP Trap Service to start automatically. To do this, right-click on the service, select Properties, and under the General tab, change the Startup type to Automatic.

Make sure that both SNMP services are running: SNMP Service and SNMP Trap Service.

Windows services with SNMP Trap service and SNMP Trap properties.

Debian

Install SNMP Trap Service

sudo apt update

sudo apt install snmptrapd

Config file

sudo nano /etc/snmp/snmptrapd.conf

disableAuthorization yes

authCommunity log,execute,net public

snmpTrapdAddr udp:161

In the above example, there are some parameters that may vary from one environment to another:

disableAuthorization value of yes disables authorization when sending traps to the SNMP manager
authCommunity ensures proper communication between peers, so we might have to change public to the proper community group described in the SNMP trap package configuration
snmpTrapdAddr sets the protocol and listening port of the SNMP Trap package

Restart the service after configuration

sudo service snmptrapd restart

List of Traps

All traps are sent with the enterprise set to:

.1.3.6.1.4.1.42303.2 (.iso.org.dod.internet.private.enterprises.te-systems.anynode)

Name:anynodeStateChange

OID: .1.3.6.1.4.1.42303.2.1.5.0

Request Type: TRAP

Description: The trap is sent when the anynode service is loaded or unloaded. The following parameter is sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 1

Bindings: The new anynodeState with OID .1.3.6.1.4.1.42303.2.1.5.0. Refer to anynodeState in the system group for possible values.

Name:networkStateChange

OID: .1.3.6.1.4.1.42303.2.2.2.1.1

Request Type: TRAP

Description: The trap is sent when the state of the network interface used by a node is changed, e.g., if the network cable is unplugged. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 2

Bindings: The node index with OID .1.3.6.1.4.1.42303.2.2.2.1.1. The new network interface state with OID .1.3.6.1.4.1.42303.2.2.2.1.4. Refer to nodeNetworkState in the node group for possible values.

Name:registrationStateChange

OID: .1.3.6.1.4.1.42303.2.2.2.1.1

Request Type: TRAP

Description: The trap is sent when the state of the registration a node uses changes. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 3

Bindings: The node index with OID .1.3.6.1.4.1.42303.2.2.2.1.1. The new state with OID .1.3.6.1.4.1.42303.2.2.2.1.6. Refer to nodeRegistrationState in the node group for possible values.

Name:licenseExpiresWarning

OID: .1.3.6.1.4.1.42303.2.4.2.1.1

Request Type: TRAP

Description: The trap is sent when a limited license is going to expire, and only the amount of days configured via the configuration parameter cfgLicenseExpiresWarning is left. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 4

Bindings: The license index with OID .1.3.6.1.4.1.42303.2.4.2.1.1. The amount of days when the license will expire with OID .1.3.6.1.4.1.42303.2.4.2.1.5. If this value is zero, the license is expired.

Name:licenseExpiresCritical

OID: .1.3.6.1.4.1.42303.2.4.2.1.1

Request Type: TRAP

Description: The trap is sent when a limited license is going to expire, and only the amount of days configured via the configuration parameter cfgLicenseExpiresCritical is left. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 5

Name:certificatesExpiresWarning

OID: .1.3.6.1.4.1.42303.2.5.2.1.1

Request Type: TRAP

Description: The trap is sent when a certificate is going to expire, and only the amount of days configured via the configuration parameter cfgCertificateExpiresWarning is left. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 6

Bindings: The certificate index with OID .1.3.6.1.4.1.42303.2.5.2.1.1. The amount of days when the certificate will expire with OID .1.3.6.1.4.1.42303.2.5.2.1.5. If this value is zero, the certificate is expired.

Name:certificateExpiresCritical

OID: .1.3.6.1.4.1.42303.2.5.2.1.1

Request Type: TRAP

Description: The trap is sent when a certificate is going to expire, and only the amount of days configured via the configuration parameter cfgCertificateExpiresCritical is left. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 7

Name:statisticsCallNoLicense

OID: .1.3.6.1.4.1.42303.2.1.19.0

Request Type: TRAP

Description: The trap is sent when an incoming call cannot be handled because no more licenses are available. The sending of the trap depends on the configuration parameter cfgWarnCallNoLicense. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 8

Bindings: The amount of calls that could not be served with OID .1.3.6.1.4.1.42303.2.1.19.0.

Name:statisticsCallNoRoute

OID: .1.3.6.1.4.1.42303.2.1.20.0

Request Type: TRAP

Description: The trap is sent when an incoming call cannot be handled because no route could be identified. The sending of the trap depends on the configuration parameter cfgWarnCallNoRoute. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 9

Bindings: The amount of calls that could not be served with OID .1.3.6.1.4.1.42303.2.1.20.0.

Name:callHistorySessionsRemoved

OID: .1.3.6.1.4.1.42303.2.6.9.0

Request Type: TRAP

Description: The trap is sent when the amount of sessions in the call history reached the configured maximum and sessions were removed from the call history. The amount of now available entries in the call history can be read from the system MIB by adding the totalSuccessfulSessions and the totalFailedSessions. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 10

Bindings: The configured maximum number of entries/sessions with OID .1.3.6.1.4.1.42303.2.6.9.0. The number of sessions that have been removed with OID .1.3.6.1.4.1.42303.2.1.39.0.

Name:operationalStateChange

OID: .1.3.6.1.4.1.42303.2.2.2.1.1

Request Type: TRAP

Description: The trap is sent when the operational state of the registration used by a node changed. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 11

Bindings: The node index with OID .1.3.6.1.4.1.42303.2.2.2.1.1. The new state with OID .1.3.6.1.4.1.42303.2.2.2.1.33. Refer to nodeOperational in the node group for possible values.

Name:configurationChange

OID: None

Request Type: TRAP

Description: The trap is sent when the anynode configuration is updated (committed).

Generic Type: Enterprise-specific trap

Specific Type: 12

Bindings: None

Name:ldapConnectionStateChange

OID: .1.3.6.1.4.1.42303.2.7.2.1.1

Request Type: TRAP

Description: The trap is sent when the state of an LDAP connection changes to success or error. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 13

Bindings: The LDAP connection index with OID .1.3.6.1.4.1.42303.2.7.2.1.1. The new state with OID .1.3.6.1.4.1.42303.2.7.2.1.10. Refer to ldapConnectionState in the LDAP connection group for possible values.

Name:licenseUpdaterFailed

OID: .1.3.6.1.4.1.42303.2.4.2.1.1

Request Type: TRAP

Description: The trap is sent when the auto updater could not validate an abo license. The license will still be valid for the given amount of days and the auto updater will continue to validate the license. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 14

Name:eventNotifications

OID: Refer to eventObjects group

Request Type: TRAP

Description: The trap is sent when anynode monitor writes an event. Note that only events that match the configured filter are sent. The following parameters are sent with the trap:

Generic Type: Enterprise-specific trap

Specific Type: 15

Bindings: The OIDs listed under The eventObjects group.