Ignore down(2) administrative status

Filter out loopbacks, nulls, docker veth links and docker0 bridge by default

Ignore notPresent(6)

Item is used to collect all SNMP traps unmatched by other snmptrap items

MIB: SNMPv2-MIB

The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 1d

MIB: SNMPv2-MIB

A textual description of the entity. This value should

include the full name and version identification of the system's hardware type, software operating-system, and

networking software.

Preprocessing

• Discard unchanged with heartbeat: 1d

MIB: ENTITY-MIB

Preprocessing

• Discard unchanged with heartbeat: 1d

MIB: ENTITY-MIB

Preprocessing

• Discard unchanged with heartbeat: 1d

MIB: SNMPv2-MIB

The physical location of this node (e.g., `telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 1h

MIB: SNMPv2-MIB

An administratively-assigned name for this managed node.By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 1h

MIB: SNMPv2-MIB

The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.' was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

Preprocessing

• Discard unchanged with heartbeat: 1h

MIB: SNMPv2-MIB

Preprocessing

• Regular expression: Version (.+), RELEASE \1

• Discard unchanged with heartbeat: 1d

MIB: SNMPv2-MIB

The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

Preprocessing

• Custom multiplier: 0.01

MIB: HOST-RESOURCES-MIB

The amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.

Preprocessing

• Check for not supported value: any error

  ⛔️Custom on fail: Set value to: 0

• Custom multiplier: 0.01

Last three attempts returned timeout. Please check device connectivity.

• Unavailable by ICMP ping

• High ICMP ping loss
• Unavailable by ICMP ping

The device serial number has changed. Acknowledge to close the problem manually.

The name of the system has changed. Acknowledge to close the problem manually.

The description of the operating system has changed. Possible reasons are that the system has been updated or replaced. Acknowledge to close the problem manually.

• System name has changed

Uptime is less than 10 minutes.

SNMP is not available for polling. Please check device connectivity and SNMP settings.

If your IOS device has several CPUs, you must use CISCO-PROCESS-MIB and its object cpmCPUTotal5minRev from the table called cpmCPUTotalTable ,

indexed with cpmCPUTotalIndex .

This table allows CISCO-PROCESS-MIB to keep CPU statistics for different physical entities in the router,

like different CPU chips, group of CPUs, or CPUs in different modules/cards.

In case of a single CPU, cpmCPUTotalTable has only one entry.

MIB: CISCO-PROCESS-MIB

Object name: cpmCPUTotal5minRev

The cpmCPUTotal5minRev MIB object provides a more accurate view of the performance of the router over time than the MIB objects cpmCPUTotal1minRev and cpmCPUTotal5secRev . These MIB objects are not accurate because they look at CPU at one minute and five second intervals, respectively. These MIBs enable you to monitor the trends and plan the capacity of your network. The recommended baseline rising threshold for cpmCPUTotal5minRev is 90 percent. Depending on the platform, some routers that run at 90 percent, for example, 2500s, can exhibit performance degradation versus a high-end router, for example, the 7500 series, which can operate fine.

Reference: http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15215-collect-cpu-util-snmp.html

The CPU utilization is too high. The system might be slow to respond.

MIB: ENTITY-MIB

Object name: entPhysicalSerialNum

Preprocessing

• Discard unchanged with heartbeat: 1d

Device serial number has changed. Acknowledge to close the problem manually.

The table of fan status maintained by the environmental monitor.

MIB: CISCO-ENVMON-MIB

Object name: ciscoEnvMonFanState

Please check the fan unit

Please check the fan unit

• {#SNMPVALUE}: Fan is in critical state

Discovery of ciscoMemoryPoolTable, a table of memory pool monitoring entries.

http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15216-contiguous-memory.html

MIB: CISCO-MEMORY-POOL-MIB

Object name: ciscoMemoryPoolFree

Indicates the number of bytes from the memory pool that are currently unused on the managed device. Note that the sum of ciscoMemoryPoolUsed and ciscoMemoryPoolFree is the total amount of memory in the pool

Reference: http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15216-contiguous-memory.html

MIB: CISCO-MEMORY-POOL-MIB

Object name: ciscoMemoryPoolUsed

Indicates the number of bytes from the memory pool that are currently in use by applications on the managed device.

Reference: http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15216-contiguous-memory.html

Memory utilization in %

The system is running out of free memory.

Discovering interfaces from IF-MIB.

MIB: IF-MIB

The number of inbound packets which were chosen to be discarded

even though no errors had been detected to prevent their being deliverable to a higher-layer protocol.

One possible reason for discarding such a packet could be to free up buffer space.

Discontinuities in the value of this counter can occur at re-initialization of the management system,

and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second:

MIB: IF-MIB

For packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second:

MIB: IF-MIB

The total number of octets received on the interface, including framing characters. This object is a 64-bit version of ifInOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second:

• Custom multiplier: 8

MIB: IF-MIB

The number of outbound packets which were chosen to be discarded

even though no errors had been detected to prevent their being deliverable to a higher-layer protocol.

One possible reason for discarding such a packet could be to free up buffer space.

Discontinuities in the value of this counter can occur at re-initialization of the management system,

and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second:

MIB: IF-MIB

For packet-oriented interfaces, the number of outbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of outbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second:

MIB: IF-MIB

The total number of octets transmitted out of the interface, including framing characters. This object is a 64-bit version of ifOutOctets.Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Preprocessing

• Change per second:

• Custom multiplier: 8

MIB: IF-MIB

An estimate of the interface's current bandwidth in units of 1,000,000 bits per second. If this object reports a value of n' then the speed of the interface is somewhere in the range of n-500,000' to`n+499,999'. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. For a sub-layer which has no concept of bandwidth, this object should be zero.

Preprocessing

• Custom multiplier: 1000000

• Discard unchanged with heartbeat: 1h

MIB: IF-MIB

The current operational state of the interface.

- The testing(3) state indicates that no operational packet scan be passed

- If ifAdminStatus is down(2) then ifOperStatus should be down(2)

- If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic

- It should change todormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection)

- It should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state

- It should remain in the notPresent(6) state if the interface has missing(typically, hardware) components.

Preprocessing

• Discard unchanged with heartbeat: 6h

MIB: IF-MIB

The type of interface.

Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA),

through updating the syntax of the IANAifType textual convention.

Preprocessing

• Discard unchanged with heartbeat: 6h

It recovers when it is below 80% of the {$IF.ERRORS.WARN:"{#IFNAME}"} threshold.

• Interface {#IFNAME}({#IFALIAS}): Link down

The utilization of the network interface is close to its estimated maximum bandwidth.

• Interface {#IFNAME}({#IFALIAS}): Link down

It recovers when it is below 80% of the {$IF.ERRORS.WARN:"{#IFNAME}"} threshold.

• Interface {#IFNAME}({#IFALIAS}): Link down

The utilization of the network interface is close to its estimated maximum bandwidth.

• Interface {#IFNAME}({#IFALIAS}): Link down

This Ethernet connection has transitioned down from its known maximum speed. This might be a sign of autonegotiation issues. Acknowledge to close the problem manually.

• Interface {#IFNAME}({#IFALIAS}): Link down

This trigger expression works as follows:
1. It can be triggered if the operations status is down.
2. {$IFCONTROL:"{#IFNAME}"}=1 - a user can redefine context macro to value - 0. That marks this interface as not important. No new trigger will be fired if this interface is down.

Discovering interfaces from IF-MIB and EtherLike-MIB. Interfaces with up(1) Operational Status are discovered.

MIB: EtherLike-MIB

Object name: dot3StatsDuplexStatus

The current mode of operation of the MAC

entity. 'unknown' indicates that the current

duplex mode could not be determined.

Management control of the duplex mode is

accomplished through the MAU MIB. When

an interface does not support autonegotiation,

or when autonegotiation is not enabled, the

duplex mode is controlled using

ifMauDefaultType. When autonegotiation is

supported and enabled, duplex mode is controlled

using ifMauAutoNegAdvertisedBits. In either

case, the currently operating duplex mode is

reflected both in this object and in ifMauType.

Note that this object provides redundant

information with ifMauType. Normally, redundant

objects are discouraged. However, in this

instance, it allows a management application to

determine the duplex status of an interface

without having to know every possible value of

ifMauType. This was felt to be sufficiently

valuable to justify the redundancy.

Reference: [IEEE 802.3 Std.], 30.3.1.1.32,aDuplexStatus.

Please check autonegotiation settings and cabling

The table of power supply status maintained by the environmental monitor card.

MIB: CISCO-ENVMON-MIB

Object name: ciscoEnvMonSupplyState

Please check the power supply unit for errors

Please check the power supply unit for errors

• {#SNMPVALUE}: Power supply is in critical state

Discovery of ciscoEnvMonTemperatureTable (ciscoEnvMonTemperatureDescr), a table of ambient temperature status

maintained by the environmental monitor.

MIB: CISCO-ENVMON-MIB

Object name: ciscoEnvMonTemperatureState

The current state of the test point being instrumented.

MIB: CISCO-ENVMON-MIB

Object name: ciscoEnvMonTemperatureValue

The current measurement of the test point being instrumented.

This trigger uses temperature sensor state

This trigger uses temperature sensor state

• {#SNMPVALUE}: Temperature is in critical state

This trigger uses temperature sensor values as well as temperature sensor status if available

This trigger uses temperature sensor values as well as temperature sensor status if available

• {#SNMPVALUE}: Temperature is above critical threshold