Event Types Reference
This page describes the most commonly used built-in event types in NetXMS, and lists all built-in event templates with their parameters at the end (see All Built-in Event Templates). The Event templates view (Configuration perspective) shows the templates as configured on your server, including changes and custom events.
Built-in Events
NetXMS includes a comprehensive set of built-in events. These events have codes below 100000 and cannot be deleted (but can be modified).
Node and Object Status Events
| Event | Severity | Description |
|---|---|---|
|
Critical |
Node is not responding to any polls |
|
Normal |
Node recovered after being down |
|
Minor |
Network interface is down |
|
Normal |
Network interface is back up |
|
Normal |
New interface discovered on a node |
|
Normal |
Interface removed from a node |
|
Major |
Monitored network service is not responding |
|
Normal |
Network service recovered |
|
Critical |
Node is unreachable by the management server because of a network path failure, or, for a node without a primary IP address, because its agent tunnel is disconnected; the reason and the root-cause node or interface are passed in event parameters (see Root Cause Analysis) |
Threshold Events
| Event | Severity | Description |
|---|---|---|
|
Warning |
DCI threshold activated |
|
Normal |
DCI threshold deactivated (value returned to normal) |
|
Minor |
Table DCI threshold activated |
|
Normal |
Table DCI threshold deactivated |
A threshold does not set event severity — it selects which activation and deactivation events to generate, and severity comes from those events' templates. To get different severities for different thresholds, configure the thresholds to generate different events.
Discovery Events
| Event | Severity | Description |
|---|---|---|
|
Normal |
New node added to the system (manually or via discovery) |
|
Normal |
New subnet discovered |
|
Warning |
Duplicate IP address detected |
|
Warning |
MAC address of a node’s own interface changed (see MAC Address Changes on Node Interfaces) |
MAC Address Changes on Node Interfaces
SYS_MAC_ADDR_CHANGED reports a change of the MAC address of an interface that belongs to the node itself.
It does not track MAC addresses learned on switch ports; for those, see Connection History.
The server checks interface MAC addresses during the configuration poll of a node (interval: Objects.ConfigurationPollingInterval, default: 3600 seconds).
A status poll that detects a node restart (system uptime lower than at the previous status poll) runs the same check, unless configuration polls are disabled for the node.
The current MAC address comes from one of two sources:
-
Node that returns an interface list (from the agent or from a network device driver over SNMP or SSH): each interface in the list is matched to an existing interface object by interface index (ifIndex), and the reported MAC address is compared with the stored one.
-
Node without an interface list (for example, a node monitored only by ICMP): the node has a single pseudo-interface for its primary IP address. The server looks up the MAC address of that IP address in the ARP caches of the nodes in the same subnet that have an agent or SNMP and are not unmanaged. The check is skipped when no ARP entry is found.
When the MAC address differs, the server stores the new MAC address on the interface object and generates SYS_MAC_ADDR_CHANGED with the node as the event source.
Event message: MAC address for interface %3 changed from %4 to %5.
| # | Parameter | Description |
|---|---|---|
1 |
|
Interface object ID |
2 |
|
Interface index (ifIndex) |
3 |
|
Interface name |
4 |
|
MAC address before the change |
5 |
|
New MAC address |
The default Event Processing Policy has two rules for this event:
-
Generate alarm when MAC address change detected on interface creates a Warning alarm with key
MAC_ADDRESS_CHANGED_%i_%2(node ID and interface index). A later change on the same interface updates this alarm instead of creating a new one. -
Terminate MAC address change alarms when the interface is deleted terminates that alarm when
SYS_IF_DELETEDis generated for the interface. Deleting an interface object manually does not generateSYS_IF_DELETED, so it does not terminate the alarm.
The interface object keeps only the current MAC address.
Past changes are in the event log: in the Events log of the Logs perspective, filter by event name SYS_MAC_ADDR_CHANGED and, if needed, by source node (see Event Log).
Event log records are kept for Events.LogRetentionTime days (default: 90).
Limitations:
-
A node with interfaces from an interface list must return that list during the poll; otherwise the MAC addresses of its interfaces are not checked.
-
A change that is reverted before the next check is not detected.
-
Interfaces are matched by ifIndex only. An interface that the device re-creates with a new ifIndex appears as
SYS_IF_DELETEDfor the old interface andSYS_IF_ADDEDfor a new one, not as a MAC address change. If the device renumbers its interfaces, an interface object can take over the ifIndex of another port; the poll then reports a MAC address change for that interface object and updates its name. -
A reported all-zero MAC address is ignored.
Inventory Events
Generated by configuration polls of nodes with a native agent; see Hardware and Software Inventory.
| Event | Severity | Description |
|---|---|---|
|
Normal |
New hardware component found on the node |
|
Normal |
Hardware component no longer reported by the node |
|
Normal |
New software package found on the node |
|
Normal |
Version of a software package changed |
|
Normal |
Software package no longer reported by the node |
Agent Events
| Event | Severity | Description |
|---|---|---|
|
Major |
Agent is not responding |
|
Normal |
Agent communication restored |
|
Normal |
Agent tunnel established |
|
Warning |
Agent tunnel closed |
Server Events
| Event | Severity | Description |
|---|---|---|
|
Normal |
NetXMS server has started |
|
Critical |
Database query failed |
|
Major |
SNMP agent on node is not responding |
|
Normal |
SNMP communication restored |
|
Warning |
Event processing policy detected a rule chain loop; the call to the already active chain was skipped |
|
Warning |
An alarm was created in flapping state. Generated on the alarm’s source object with parameters |
|
Normal |
An alarm left flapping state, because no transitions occurred during the flap detection window or the alarm was terminated. Same parameters as |
Event Severity Levels
NetXMS uses five severity levels:
| Severity | Code | Usage |
|---|---|---|
Normal |
0 |
Informational events, recovery events |
Warning |
1 |
Conditions that may require attention |
Minor |
2 |
Issues with limited impact |
Major |
3 |
Significant problems affecting functionality |
Critical |
4 |
Service-affecting conditions requiring immediate action |
Severity is assigned at the event template level.
During processing it can be changed only from NXSL scripts that receive the event object — an EPP rule filtering script or action script (Script page), or the Hook::EventProcessor hook — by calling $event→setSeverity() or assigning $event→severity.
EPP rule actions themselves cannot change event severity (the severity setting in alarm-creation actions applies to the alarm, not the event).
Event Properties
An event in NetXMS is a record with the following properties (some of which can be modified during processing from EPP rule scripts, using NXSL methods on $event):
| Property | Description |
|---|---|
Event ID |
Unique identifier of this event occurrence |
Event Code |
Unique numeric identifier for the event type |
Event Name |
Symbolic name (e.g., |
Severity |
Normal, Warning, Minor, Major, or Critical |
Source |
Object that generated the event (node, interface, etc.) |
Zone |
Zone UIN of the source object |
DCI ID |
Related DCI, for events generated by data collection (thresholds) |
Message |
Human-readable description with parameter substitution |
Parameters |
Array of event-specific values passed at generation time |
Timestamp |
When the event was generated |
Origin |
Where the event originated (system, syslog, SNMP trap, agent, client, etc.) |
Origin Timestamp |
Timestamp supplied by the origin (e.g., when a forwarded syslog message was produced); equals the generation time when not supplied |
Root Event ID |
For correlated events, the ID of the event this one is a consequence of |
Tags |
Optional labels for filtering and categorization |
All Built-in Event Templates
The table lists every built-in event template with its code, default severity, and the description and parameters from the template.
Parameters are available in message templates and actions as %1, %2, and so on, or by name as %<name>.
| Code | Event | Severity | Description and parameters |
|---|---|---|---|
1 |
|
Normal |
Generated when new node object added to the database.
|
2 |
|
Normal |
Generated when new subnet object added to the database.
|
3 |
|
Normal |
Generated when new interface object added to the database. Please note that source of event is node, not an interface itself.
|
4 |
|
Normal |
Generated when interface goes up. Please note that source of event is node, not an interface itself.
|
5 |
|
Minor |
Generated when interface goes down. Please note that source of event is node, not an interface itself.
|
6 |
|
Normal |
Generated when node status changed to normal.
|
7 |
|
Warning |
Generated when node status changed to "Warning".
|
8 |
|
Minor |
Generated when node status changed to "Minor Problem" (informational).
|
9 |
|
Major |
Generated when node status changed to "Major Problem".
|
10 |
|
Critical |
Generated when node status changed to critical.
|
11 |
|
Normal |
Generated when node status changed to unknown.
|
12 |
|
Normal |
Generated when node status changed to unmanaged.
|
13 |
|
Normal |
Generated when node capabilities changed.
|
14 |
|
Major |
Generated when node’s SNMP agent is not responding. No event-specific parameters |
15 |
|
Major |
Generated when node’s native agent is not responding. No event-specific parameters |
16 |
|
Normal |
Generated when interface object deleted from the database. Please note that source of event is node, not an interface itself.
|
17 |
|
Warning |
Generated when threshold value reached for specific data collection item. Parameters are accessible via
|
18 |
|
Normal |
Generated when threshold check is rearmed for specific data collection item. Parameters are accessible via
|
19 |
|
Normal |
Generated when subnet object deleted from the database.
|
20 |
|
Critical |
Generated when one of the system threads hangs or stops unexpectedly.
|
21 |
|
Normal |
Generated when one of the system threads which previously hangs or stops unexpectedly was returned to running state.
|
22 |
|
Warning |
Generated when server is unable to send notification.
|
23 |
|
Warning |
Generated when server detects change of interface’s MAC address.
|
24 |
|
Minor |
Generated when server detects invalid network mask on an interface.
|
25 |
|
Major |
Generated when network service is not responding to management server as expected.
|
26 |
|
Normal |
Generated when network service responds as expected after failure.
|
27 |
|
Warning |
Generated when management server is unable to determine state of the network service due to agent or server-to-agent communication failure.
|
28 |
|
Critical |
Generated when node is not responding to management server. 1) Previous state (1 if node was marked as UNREACHABLE, 0 if it was marked as DOWN) |
29 |
|
Normal |
Generated when communication with the node re-established.
|
30 |
|
Normal |
Generated when all thresholds are rearmed for specific data collection item. Parameters are accessible via
|
31 |
|
Normal |
Generated when connectivity with node’s SNMP agent restored. No event-specific parameters |
32 |
|
Normal |
Generated when connectivity with node’s native agent restored. No event-specific parameters |
33 |
|
Minor |
Generated when server encounters NXSL script execution error. 1) Script name 2) Error text 3) DCI ID if script is DCI related script, or 0 otherwise 4) Related object ID if applicable, or 0 otherwise 5) Context |
34 |
|
Minor |
Default event for condition activation.
|
35 |
|
Normal |
Default event for condition deactivation.
|
36 |
|
Critical |
Generated if connection with backend database engine is lost. No event-specific parameters |
37 |
|
Normal |
Generated when connection with backend database engine restored. No event-specific parameters |
38 |
|
Warning |
Generated when cluster resource moved between nodes.
|
39 |
|
Major |
Generated when cluster resource goes down.
|
40 |
|
Normal |
Generated when cluster resource goes up.
|
41 |
|
Critical |
Generated when cluster goes down. No event-specific parameters |
42 |
|
Normal |
Generated when cluster goes up. No event-specific parameters |
43 |
|
Warning |
Generated when alarm timeout expires.
|
44 |
|
Warning |
Default event for log record match. 1) Policy name 2) Log file name 3) Matching regular expression 4) Matched record 5 .. 9) Reserved 10 .. 99) Substrings extracted by regular expression |
45 |
|
Warning |
Generated when interface goes to unknown state. Please note that source of event is node, not an interface itself.
|
46 |
|
Normal |
Generated when interface administratively disabled. Please note that source of event is node, not an interface itself.
|
47 |
|
Normal |
Generated when interface goes to testing state. Please note that source of event is node, not an interface itself.
|
48 |
|
Major |
Generated when system detects an event storm.
|
49 |
|
Normal |
Generated when system clears event storm condition.
|
50 |
|
Critical |
Generated when system detects loss of network connectivity based on beacon probing.
|
51 |
|
Normal |
Generated when system detects restoration of network connectivity based on beacon probing.
|
52 |
|
Critical |
Generated when SQL query to backend database failed. 1) Query (query) 2) Error message (message) 3) Connection loss indicator (connectionLost) 4) Query hash (hash) |
53 |
|
Minor |
Generated when DCI status changed to UNSUPPORTED. 1) DCI ID (dciId) 2) Metric (metric) 3) Description (description) 4) Origin code (originCode) 5) Origin name (origin) |
54 |
|
Warning |
Generated when DCI status changed to DISABLED. 1) DCI ID (dciId) 2) Metric (metric) 3) Description (description) 4) Origin code (originCode) 5) Origin name (origin) |
55 |
|
Normal |
Generated when DCI status changed to ACTIVE. 1) DCI ID (dciId) 2) Metric (metric) 3) Description (description) 4) Origin code (originCode) 5) Origin name (origin) |
56 |
|
Warning |
Generated when primary IP address changed (usually because of primary name change or DNS change).
|
57 |
|
Normal |
Generated when switch port PAE state changed.
|
58 |
|
Normal |
Generated when switch port backend authentication state changed.
|
59 |
|
Major |
Generated when switch port PAE state changed to FORCE UNAUTHORIZE.
|
60 |
|
Major |
Generated when switch port backend authentication state changed to FAIL.
|
61 |
|
Major |
Generated when switch port backend authentication state changed to TIMEOUT.
|
62 |
|
Major |
Generated when interface goes up but it’s expected state set to DOWN. Please note that source of event is node, not an interface itself.
|
63 |
|
Normal |
Generated when interface goes down and it’s expected state is DOWN. Please note that source of event is node, not an interface itself.
|
64 |
|
Normal |
Generated when node bound to container object by autobind rule.
|
65 |
|
Normal |
Generated when node unbound from container object by autobind rule.
|
66 |
|
Normal |
Generated when template applied to node by autoapply rule.
|
67 |
|
Normal |
Generated when template removed from node by autoapply rule.
|
68 |
|
Critical |
Generated when node is unreachable by management server because of network failure.
|
69 |
|
Minor |
Generated when table threshold is activated.
|
70 |
|
Normal |
Generated when table threshold is deactivated.
|
71 |
|
Normal |
Generated when peer information for interface changes.
|
72 |
|
Normal |
Generated when access point state changes to UP.
|
73 |
|
Major |
Generated when access point state changes to UNPROVISIONED.
|
74 |
|
Critical |
Generated when access point state changes to DOWN.
|
75 |
|
Normal |
Generated when when network mask on interface is corrected.
|
76 |
|
Normal |
Generated when IP address added to interface.
|
77 |
|
Normal |
Generated when IP address deleted from interface.
|
78 |
|
Normal |
Generated when node, cluster, or mobile device entered maintenance mode.
|
79 |
|
Normal |
Generated when node, cluster, or mobile device left maintenance mode.
|
80 |
|
Major |
Generated when LDAP synchronization error occurs.
|
81 |
|
Major |
Generated on status poll if agent reports problem with log file.
|
82 |
|
Major |
Generated on status poll if agent reports local database problem.
|
83 |
|
Normal |
Generated when interface expected state set to UP. Please note that source of event is node, not an interface itself.
|
84 |
|
Normal |
Generated when interface expected state set to DOWN. Please note that source of event is node, not an interface itself.
|
85 |
|
Normal |
Generated when interface expected state set to IGNORE. Please note that source of event is node, not an interface itself.
|
86 |
|
Major |
Generated when server detects routing loop during network path trace. Source of the event is node which routes packet back to already passed hop.
|
87 |
|
Normal |
Generated when new software package is found.
|
88 |
|
Normal |
Generated when software package version change is detected.
|
89 |
|
Normal |
Generated when software package removal is detected.
|
90 |
|
Normal |
Generated when agent policy deployed to node by autodeploy rule. 1) Node ID 2) Node name 3) Policy ID 4) Policy name |
91 |
|
Normal |
Generated when agent policy uninstalled from node by autodeploy rule. 1) Node ID 2) Node name 3) Policy ID 4) Policy name |
92 |
|
Normal |
Generated when unbound agent tunnel is not bound or closed for more than configured threshold.
|
93 |
|
Warning |
Generated when agent ID change detected.
|
94 |
|
Normal |
Generated when agent tunnel is open and bound.
|
95 |
|
Warning |
Generated when agent tunnel is closed.
|
96 |
|
Warning |
Generated when agent ID mismatch detected during tunnel bind.
|
97 |
|
Normal |
Generated when server initialization is completed. |
98 |
|
Normal |
Generated when new hardware component is found.
|
99 |
|
Normal |
Generated when hardware component removal is detected.
|
100 |
|
Warning |
Generated when node is deleted by network discovery de-duplication process.
|
101 |
|
Warning |
Generated when possibly duplicate IP address is detected by network discovery process.
|
102 |
|
Major |
Generated when node is not responding to EtherNet/IP requests. No event-specific parameters |
103 |
|
Normal |
Generated when EtherNet/IP connectivity with the node is restored. No event-specific parameters |
104 |
|
Major |
Generated when background database writer queue size exceeds threshold. No event-specific parameters |
105 |
|
Normal |
Generated when background database writer queue size drops below threshold. No event-specific parameters |
106 |
|
Normal |
Generated when internal housekeeper task starts. No event-specific parameters |
107 |
|
Normal |
Generated when internal housekeeper task completes.
|
108 |
|
Warning |
Generated when licensing problem is detected by extension module.
|
109 |
|
Major |
Generated when system detects an SNMP trap flood.
|
110 |
|
Normal |
|
111 |
|
Normal |
Generated when device geolocation change is detected.
|
112 |
|
Warning |
Generated when new device geolocation is within restricted area.
|
113 |
|
Warning |
Generated when new device geolocation is ouside allowed areas.
|
114 |
|
Normal |
Generated when node added to cluster object by autoadd rule.
|
115 |
|
Normal |
Generated when node removed from cluster object by autoadd rule.
|
116 |
|
Warning |
Generated when new tunnel is replacing existing one and host data mismatch is detected.
|
117 |
|
Warning |
Generated when agent policy within template fails validation.
|
118 |
|
Major |
Generated on agent tunnel setup error. 1) Source IP address (ipAddress) 2) Error message (error) |
119 |
|
Major |
Generated when duplicate MAC address found.
|
120 |
|
Normal |
Generated when business service state changes to operational. No event-specific parameters |
121 |
|
Critical |
Generated when business service state changes to failed. No event-specific parameters |
122 |
|
Major |
Generated when node is unreachable by ICMP. No event-specific parameters |
123 |
|
Normal |
Generated when node start responding to ICMP again No event-specific parameters |
124 |
|
Minor |
Generated when business service state changes to degraded. No event-specific parameters |
125 |
|
Major |
Generated when notification channel fails health check.
|
126 |
|
Normal |
Generated when notification channel passes health check.
|
127 |
|
Warning |
Generated when agent monitored file is changed. 1) Path to changed file |
128 |
|
Warning |
Generated when new file in agent monitored directory is created. 1) Path to new file |
129 |
|
Warning |
Generated when agent monitored file is deleted. 1) Path to deleted file |
130 |
|
Warning |
Generated when there are too many script errors within short time period. No event-specific parameters |
131 |
|
Normal |
Generated when node becomes reachable by SSH. No event-specific parameters |
132 |
|
Major |
Generated when node becomes unreachable by SSH. No event-specific parameters |
133 |
|
Major |
Generated when automatic update of asset management attribute fails.
|
134 |
|
Normal |
Generated when asset is linked with object.
|
135 |
|
Normal |
Generated when asset is unlinked from object.
|
136 |
|
Minor |
Generated when asset cannot be automatically linked with a node because of conflict.
|
137 |
|
Minor |
Generated on any system configuration error.
|
138 |
|
Major |
Generated when node is not responding to Modbus requests. No event-specific parameters |
139 |
|
Normal |
Generated when Modbus connectivity with the node is restored. No event-specific parameters |
140 |
|
Normal |
Generated when system detects interface Spanning Tree state change.
|
141 |
|
Normal |
Generated when system detects interface speed change.
|
142 |
|
Normal |
Generated when access point state changes to UNKNOWN.
|
143 |
|
Normal |
Generated when interface bound to circuit by autobind rule.
|
144 |
|
Normal |
Generated when interface unbound from circuit by autobind rule.
|
145 |
|
Normal |
Generated when new responsible user added to the object.
|
146 |
|
Normal |
Generated when responsible user removed from the object.
|
147 |
|
Normal |
Generated when the responsible user’s record for the object is modified.
|
148 |
|
Warning |
Generated when system detects that interface speed is below maximum.
|
149 |
|
Normal |
Generated when interface status changed to unmanaged.
|
150 |
|
Warning |
Generated when notification channel queue size exceeds configured threshold.
|
151 |
|
Normal |
Generated when a new incident is created.
|
152 |
|
Normal |
Generated when incident state changes.
|
153 |
|
Normal |
Generated when an incident is assigned to a user.
|
154 |
|
Normal |
Generated when an alarm is linked to an incident.
|
155 |
|
Normal |
Generated when an alarm is unlinked from an incident.
|
156 |
|
Warning |
Generated when DNS resolution fails for a hostname-based node and its IP address is cleared.
|
157 |
|
Warning |
Generated when DNS resolves a hostname to an IP address already assigned to another node.
|
158 |
|
Warning |
Generated when device running configuration change is detected during backup.
|
159 |
|
Warning |
Generated when device startup configuration change is detected during backup.
|
160 |
|
Major |
Generated when device replacement is detected during configuration poll.
|
161 |
|
Normal |
Generated when node object deleted from the database.
|
162 |
|
Normal |
Generated when cluster object deleted from the database.
|
163 |
|
Normal |
Generated when sensor object deleted from the database.
|
164 |
|
Normal |
Generated when access point object deleted from the database.
|
165 |
|
Normal |
Generated when object deleted from the database.
|
166 |
|
Normal |
Generated when a MAC address is detected on a switch port.
|
167 |
|
Normal |
Generated when a MAC address disappears from a switch port.
|
168 |
|
Warning |
Generated when a MAC address moves between ports on the same or different switches.
|
169 |
|
Warning |
Generated when server action execution fails.
|
170 |
|
Warning |
Generated when an SNMP trap is dropped because its credentials do not match the expected credentials configured for the source node. Rate-limited to one event per 24 hours per node; the timer is reset when SNMP credentials are changed on the node.
|
171 |
|
Warning |
Generated on server startup when one or more background (online) database upgrade procedures are still pending. Run "nxdbmgr background-upgrade" to complete the upgrade. |
172 |
|
Normal |
Generated when a cluster node wins the HA lease and completes server activation.
|
173 |
|
Normal |
Generated when an AI operator instance records an observation.
|
174 |
|
Major |
Generated when an AI operator instance is disabled after a series of consecutive execution failures.
|
175 |
|
Normal |
Generated when device configuration restore is started.
|
176 |
|
Normal |
Generated when device configuration restore is successfully completed.
|
177 |
|
Major |
Generated when device configuration restore fails.
|
178 |
|
Major |
Generated when traffic analyzer API becomes unreachable or authentication fails.
|
179 |
|
Normal |
Generated when connectivity to traffic analyzer API is restored.
|
180 |
|
Warning |
Generated when observation point state changes.
|
181 |
|
Minor |
Generated when a configuration sync surface fails to push data to the traffic analyzer.
|
182 |
|
Major |
Generated when node becomes unreachable by NETCONF. No event-specific parameters |
183 |
|
Normal |
Generated when node becomes reachable by NETCONF. No event-specific parameters |
184 |
|
Normal |
Generated when agent certificate fingerprint is stored on first TLS tunnel connection to the agent.
|
185 |
|
Major |
Generated when agent certificate does not match fingerprint pinned on the node during TLS tunnel establishment.
|
186 |
|
Warning |
Generated when the event processing policy detects a loop while entering rule chains during event processing. The chain that would be reentered is skipped to break the loop. The event is generated at most once per day for each calling rule.
|
187 |
|
Warning |
Generated when alarm flapping is detected: alarm is created again for the same key after being terminated by event processing policy the configured number of times within detection window. Alarm stays open until no transitions occur during detection window.
|
188 |
|
Normal |
Generated when alarm leaves flapping state: no transitions between active and terminated states occurred during detection window, or alarm was terminated.
|
500 |
|
Normal |
Generated when system receives an SNMP trap without match in trap configuration table 1) SNMP trap OID 2) Trap parameters |
501 |
|
Normal |
Generated when system receives a coldStart SNMP trap 1) SNMP trap OID |
502 |
|
Normal |
Generated when system receives a warmStart SNMP trap 1) SNMP trap OID |
503 |
|
Major |
Generated when system receives a linkDown SNMP trap 1) SNMP trap OID 2) Interface index |
504 |
|
Normal |
Generated when system receives a linkUp SNMP trap 1) SNMP trap OID 2) Interface index |
505 |
|
Warning |
Generated when system receives an authenticationFailure SNMP trap 1) SNMP trap OID |
506 |
|
Warning |
Generated when system receives an egpNeighborLoss SNMP trap 1) SNMP trap OID |
507 |
|
Normal |
Default event for discarded SNMP traps. 1) SNMP trap OID |