If the administrative status is down (2), then an interface is excluded.

It leaves only the matching fan names as indicated in the filter string.

It leaves only the matching power supply names as indicated in the filter string.

It filters out loopbacks, nulls, docker veth links and docker0 bridge by default.

If the operational status is notPresent (6), then an interface is excluded.

The filter excludes chassis (3) class from Serial discovery. The chassis (3) are polled with a regular item.

The filter retrieves only existing serial number strings.

The PSU states list for average trigger priority.

The item is used to collect all the SNMP traps unmatched by the other snmptrap items.

MIB: SNMPv2-MIB.

The textual identification of the contact person for the managed node (or: this node), together with the contact information of this person. If no contact information is known, the value is a zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 1d

MIB: SNMPv2-MIB.

The textual description of the entity. This value should include the full name and version identification number of the system's hardware type, software operating-system, and the 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, the third floor).

If the location is unknown, the value is a zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 1h

MIB: SNMPv2-MIB.

The administratively-assigned name for this node. By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is a 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 enterprise's subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining "what kind of box" is being managed.

For example, if the vendor "Flintstones, Inc." was assigned the subtree 1.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: CISCO-IMAGE-MIB

Preprocessing

• Regular expression: CW_VERSION\$(.*?)\$ \1

• Discard unchanged with heartbeat: 1d

MIB: SNMP-FRAMEWORK-MIB::snmpEngineTime.

The number of seconds since the value of the snmpEngineBoots object has had a last change.

When incrementing this object's value would cause it to exceed its maximum, the snmpEngineBoots is incremented as if a re-initialization had occurred,

and this object's value consequently reverts to zero.

The last three attempts returned a timeout. Check the connectivity of a device.

• Cisco Nexus 9000: Unavailable by ICMP ping

• Cisco Nexus 9000: High ICMP ping loss
• Cisco Nexus 9000: Unavailable by ICMP ping

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

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

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

• Cisco Nexus 9000: System name has changed

The record of SNMP Boots has changed in less than 10 minutes. The restart of a device also counts.

SNMP is not available for polling. Check the connectivity of a device and SNMP settings.

You must use CISCO-PROCESS-MIB and its object cpmCPUTotal5minRev from the table called cpmCPUTotalTable, and indexed with cpmCPUTotalPhysicalIndex.

The table cpmCPUTotalTable allows CISCO-PROCESS-MIB to keep the CPU statistics for different physical entities in the router, such as different CPU chips, a group of CPUs, or CPUs in different modules/cards.

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

Preprocessing

• Discard unchanged with heartbeat: 4h

MIB: CISCO-PROCESS-MIB

The object name: cpmCPUTotal5minRev

The MIB object cpmCPUTotal5minRev 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 the CPU with an interval of one minute and five seconds, respectively. These MIBs enable to monitor the trends and plan the capacity of your network. The recommended baseline rising threshold for the cpmCPUTotal5minRev is 90 percent. Depending on the platform, some routers that run at 90 percent, for example, 2500 series can exhibit performance degradation versus a high-end router, for example, the 7500 series, which can operate fine.

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

The discovery of serial numbers of the entities from ENTITY-MIB.

Preprocessing

• Discard unchanged with heartbeat: 4h

MIB: ENTITY-MIB.

The object name: entPhysicalSerialNum.

The vendor-specific serial number string for the physical entity. The preferred value is the serial number string actually printed on the component itself (if present).

Preprocessing

• Discard unchanged with heartbeat: 1d

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

The discovery of metrics for the fan's status from ENTITY-MIB and CISCO-ENTITY-FRU-CONTROL-MIB.

Preprocessing

• Discard unchanged with heartbeat: 4h

MIB: CISCO-ENTITY-FRU-CONTROL-MIB.

The object name: cefcFanTrayOperStatus.

The operational state of the fan or a fan tray.

Possible values:

- unknown (1) - unknown;

- up (2) - powered on;

- down (3) - powered down;

- warning (4) - partial failure; needs replacement as soon as possible.

The fan unit requires immediate attention.

The fan unit requires attention.

• Cisco Nexus 9000: {#SNMPVALUE}: Fan is down

The fan unit requires attention.

• Cisco Nexus 9000: {#SNMPVALUE}: Fan is down

The discovery of ciscoMemoryPoolTable - the table that contains monitoring entries of the memory pool.

For more details see "How to Get Free and Largest Block of Contiguous Memory Using SNMP":

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

Preprocessing

• Discard unchanged with heartbeat: 4h

MIB: CISCO-ENHANCED-MEMPOOL-MIB.

The object name: cempMemPoolFree.

It indicates the number of bytes from the memory pool that are currently unused on the physical entity.

MIB: CISCO-ENHANCED-MEMPOOL-MIB.

The object name: cempMemPoolUsed.

It indicates the number of bytes from the memory pool that are currently in use by applications on the physical entity.

The memory utilization expressed in %.

The system is running out of free memory.

The discovery of interfaces from IF-MIB.

Preprocessing

• Discard unchanged with heartbeat: 4h

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 the necessity to free up the 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 the 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 the 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 the 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 the 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 the 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 the 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 the 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 from n-500,000 to n+499,999.

For the 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), provided the interface is ready to transmit and receive network traffic.

- It should change to dormant (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 when 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 components (typically, hardware).

Preprocessing

• Discard unchanged with heartbeat: 6h

MIB: IF-MIB.

The type of an 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 goes below 80% of the {$IF.ERRORS.WARN:"{#IFNAME}"} threshold.

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

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

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

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

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

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

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

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

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

This trigger expression works as follows:
1. It can be triggered if the operations status is down.
2. Use $IFCONTROL macro with context "{#IFNAME}" to void trigger firing on specific interfaces. Values:
- 0 : Marks an interface as not important. Trigger does not fire when interface is down.
- 1 : Default value to fire the trigger when interface is down
3. change(//net.if.status[{#IFNAME}]) - condition prevents firing of trigger if status did not change. It helps in cases, when interfaces were initially down.
BEWARE, manual close will ceasefire until at least two status changes happens again!

The discovery of interfaces from IF-MIB and EtherLike-MIB. The interfaces that have up (1) operational status are discovered.

Preprocessing

• JavaScript: The text is too long. Please see the template.

• Discard unchanged with heartbeat: 4h

MIB: EtherLike-MIB.

The object name: dot3StatsDuplexStatus.

The current mode of operation of the MAC entity 'unknown' indicates that the current duplex mode could not be determined.

The management control of the duplex mode is accomplished through the MAU MIB.

When the 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 in 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 the 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.

For the reference see: [IEEE 802.3 Std.], 30.3.1.1.32, aDuplexStatus.

Check the autonegotiation settings and cabling.

The discovery of power supplies from ENTITY-MIB and CISCO-ENTITY-FRU-CONTROL-MIB.

Preprocessing

• Discard unchanged with heartbeat: 4h

MIB: CISCO-ENTITY-FRU-CONTROL-MIB.

The object name: cefcFRUPowerOperStatus.

The Operational field-replaceable unit (FRU) Status types.

The valid values are:

- offEnvOther (1): FRU is powered off because of a problem not listed below;

- on (2): FRU is powered on;

- offAdmin (3): administratively off;

- offDenied (4): FRU is powered off because available system power is insufficient;

- offEnvPower (5): FRU is powered off because of a power problem in the FRU. For example, the FRU's power translation (DC-DC converter) or distribution failed;

- offEnvTemp (6): FRU is powered off because of temperature problem;

- offEnvFan (7): FRU is powered off because of fan problems;

- failed (8): FRU is in failed state;

- onButFanFail (9): FRU is on but fan has failed;

- offCooling (10): FRU is powered off because of the system's insufficient cooling capacity;

- offConnectorRating (11): FRU is powered off because of the system's connector rating exceeded;

- onButInlinePowerFail (12): The FRU is on but no inline power is being delivered as the data/inline power component of the FRU has failed.

The PSU requires attention. Compare the current state from operational data with the table below:
- offEnvOther (1): FRU is powered off because of a problem not listed below;
- on (2): FRU is powered on;
- offAdmin (3): administratively off;
- offDenied (4): FRU is powered off because available system power is insufficient;
- offEnvPower (5): FRU is powered off because of a power problem in the FRU. For example, the FRU's power translation (DC-DC converter) or distribution failed;
- offEnvTemp (6): FRU is powered off because of temperature problem;
- offEnvFan (7): FRU is powered off because of fan problems;
- failed (8): FRU is in failed state;
- onButFanFail (9): FRU is on but fan has failed;
- offCooling (10): FRU is powered off because of the system's insufficient cooling capacity;
- offConnectorRating (11): FRU is powered off because of the system's connector rating exceeded;
- onButInlinePowerFail (12): The FRU is on but no inline power is being delivered as the data/inline power component of the FRU has failed.

• Cisco Nexus 9000: {#SNMPVALUE}: PSU is in failed state

The FRU is administratively off.

• Cisco Nexus 9000: {#SNMPVALUE}: PSU is in failed state

The FRU is in a failed state.

The discovery of temperature sensors from CISCO-ENTITY-SENSOR-MIB and ENTITY-MIB. The sensors that have celsius (8) entSensorType are discovered. The scale of gathered values is taken from the entSensorScale and applied in item preprocessing.

Preprocessing

• JavaScript: The text is too long. Please see the template.

• Discard unchanged with heartbeat: 4h

MIB: CISCO-ENTITY-SENSOR-MIB.

The object name: entSensorStatus.

This variable indicates the present operational status of the sensor.

Possible values:

- ok (1): means the agent can read the sensor value;

- unavailable (2): means that the agent presently can not report the sensor value;

- nonoperational (3) means that the agent believes the sensor is broken. The sensor could have a hard failure (e.g., disconnected wire), or a soft failure (e.g., out-of-range, jittery, or wildly fluctuating readings).

MIB: CISCO-ENTITY-SENSOR-MIB.

The object name: entSensorValue.

This variable reports the most recent measurement seen by the sensor.

Preprocessing

• Custom multiplier: {#SENSOR_SCALE}

It means that the agent considers that the sensor is broken. The sensor could have a hard failure (e.g., disconnected wire), or a soft failure (e.g., out-of-range, jittery, or wildly fluctuating readings).

It means that the agent presently can not report the sensor value.

This trigger uses the values of the temperature sensor.

This trigger uses the values of the temperature sensor.

• Cisco Nexus 9000: {#SNMPVALUE}: Temperature is above critical threshold