Supported SNMP Notifications (Traps)

Netvisor ONE supports two types of SNMP notifications (a.k.a traps): event-based and message-based traps.

Event-based traps are the traps generated by the SNMP daemon based on specific events when an OID value changes. For example, when there is a change in the link-up-down or a low-disk-space. Message-based traps are triggered based on messages logged in the local logging mechanism. For example, a login-failure Trap is triggered when a login failure message is saved in the /var/log/auth.log log file. Table 1 explains the supported SNMP notifications.

Table: Details of Supported SNMP Notifications

Trap Name	Description	Trap Type	Trigger
link-up-down	Port link is up or down	Event-based	If enabled, SNMP generates a trap when a port is up or down.
default-monitors	Use default SNMP monitoring
physical-sensors	Physical sensors are enabled		If enabled, SNMP generates a trap for physical sensors such as power supplies and fans.
low-disk-space	Monitors for low-disk-space	Event-based	If enabled, SNMP generates a trap if disk space is lower than threshold. SNMP checks the output of the command, storage-pool-show.
low-disk-space-threshold	The threshold value of low-disk-space in percentage	Event-based	SNMP generates the trap with low-disk-space.
system-usage	Monitors memory & CPU usage	Event-based	If enabled, SNMP generates a trap if system-usage[Total CPU-sys + user] space is greater than threshold. SNMP checks the output of the command, system-stats-show. The parameter cpu-total displays the threshold value.
system-usage-threshold	The threshold value of system-usage in percentage	Event-based	SNMP generates the system usage trap.
login-failure	Monitors login failures	Message-based	If enabled, SNMP generates a trap when user login with wrong password.
lacp-status	Monitors LACP enable or disable	Message-based	If enabled, SNMP generates a trap when the LACP state changes from enable to disabled or vice versa.
vport-modified	Monitors vPort modifications	Message-based	If enabled, SNMP generates a trap when vPort modifications occur on the switch.
stp-port-modified	Monitors STP port status	Message-based	If enabled, SNMP generates a trap when STP port state is modified using the command, switch-local stp-port-modify port 1 <block\|edge\|bpdu\|root-guard>
stp-port-state-failed	Monitors STP port state failures	Message-based	If enabled, SNMP generates a trap when STP port state is modified using the command, switch-local stp-port-modify port 128 edge bpdu-guard.
mirror-to-cpu	Monitors mirror-to-cpu configuration	Message-based	If enabled, SNMP generates a trap when created a vflow using the command, vflow-create name mirror scope local action copy-to-cpu and also generates a trap for perror.log.
link-congestion-detected	Monitors congestion drop at port	Message-based	If enabled, SNMP generates a trap indicating a link is congested.
fabric-node-state-changed	Monitors fabric node states	Message-based	If enabled, SNMP generates a trap when the a fabric node changes state.
ospfIfStateChange	Monitors OSPF interface states	Event-based	If enabled, this notification is triggered when interface state changes from DR to Down or vice versa. Originator for this trap is by changing router-id.
ospfNbrStateChange	Monitors OSPF NBR states	Event-based	If enabled, this notification is triggered when neighbor state changes from DR to Down or vice versa. Originator for this trap is designated router on broadcast networks.
bgpEstablished	Monitors BGP NBR state	Event-based	If enabled, this notification is triggered when the BGP FSM enters the ESTABLISHED State. Originator for this trap is to bring up BGP session between two BGP Peers.
bgpBackwardTransition	Monitors BGP NBR state transition	Event-based	If enabled, this notification is triggered when the BGP FSM moves from higher number to lower numbered state. Originator for this trap when BGP state changes from active to idle (higher state to lower state).
stp-new-root	Monitors new STP root	Event-based	If enabled, SNMP generates a trap to monitor a new root for STP.
stp-topology-changed	Monitors STP topology change	Event-based	If enabled, SNMP generates a trap to monitor topology changes for STP.
interface-up-down	Monitors vRouter interfaces	Event-based	If enabled, SNMP generates a trap for an interface with the state up or down.
disable-start-stop	Monitors disable traps for start and stop	Event-based	If enabled, a restart of SNMP service from CLI does not send any traps.
fabric-node-state-changed	Monitors fabric node states	Event-based	If enabled, SNMP generates a trap to monitor fabric node state changes.
system-usage	Monitors memory & CPU usage	Event-based	If enabled, SNMP generates a trap to monitor memory and CPU changes.
vrrp-new-master	Monitors VRRP master changes	Event-based	If enabled, SNMP generates a trap to monitor VRRP master state changes.
ospfv3IfStateChange	Monitors OSPF Interface state changes	Event-based	If enabled, this notification is triggered when interface state changes from DR to Down or vice versa.
ospfv3NbrStateChange	Monitors OSPF neighbor state changes	Event-based	If enabled, this notification is triggered when neighbor state changes from DR to Down or vice versa. Originator for this trap is designated router on broadcast networks.
cluster-tr-diverge	Monitors Cluster Transaction list for divergence	Message-based	If enabled, this notification is triggered when Transaction Diverge message is generated in perror.log.
cert-expiry	Monitors expiry of Switch Certificate	Message-based	If enabled, this notification gets triggered when switch-certificate expiring in xx number of days in /nvOS/log/event.log. You can control value of the number of days by using the cert-expiration-alert-modify <days-before-expiration> command.