-

-

-

-

-

-

-

-

Ignore notPresent(6)

Ignore down(2) administrative status

-

-

-

-

-

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

-

Ignore notPresent(6)

-

-

-

-

-

-

-

-

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

Preprocessing:

- JAVASCRIPT: The text is too long. Please see the template.

Filter:

- {#IFOPERSTATUS} MATCHES_REGEX 1

- {#SNMPVALUE} MATCHES_REGEX `(2

-

-

Discovering interfaces from IF-MIB.

Filter:

- {#IFADMINSTATUS} MATCHES_REGEX {$NET.IF.IFADMINSTATUS.MATCHES}

- {#IFADMINSTATUS} NOT_MATCHES_REGEX {$NET.IF.IFADMINSTATUS.NOT_MATCHES}

- {#IFOPERSTATUS} MATCHES_REGEX {$NET.IF.IFOPERSTATUS.MATCHES}

- {#IFOPERSTATUS} NOT_MATCHES_REGEX {$NET.IF.IFOPERSTATUS.NOT_MATCHES}

- {#IFNAME} MATCHES_REGEX {$NET.IF.IFNAME.MATCHES}

- {#IFNAME} NOT_MATCHES_REGEX {$NET.IF.IFNAME.NOT_MATCHES}

- {#IFDESCR} MATCHES_REGEX {$NET.IF.IFDESCR.MATCHES}

- {#IFDESCR} NOT_MATCHES_REGEX {$NET.IF.IFDESCR.NOT_MATCHES}

- {#IFALIAS} MATCHES_REGEX {$NET.IF.IFALIAS.MATCHES}

- {#IFALIAS} NOT_MATCHES_REGEX {$NET.IF.IFALIAS.NOT_MATCHES}

- {#IFTYPE} MATCHES_REGEX {$NET.IF.IFTYPE.MATCHES}

- {#IFTYPE} NOT_MATCHES_REGEX {$NET.IF.IFTYPE.NOT_MATCHES}

Table of status of all power supplies in the system.

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total CPU utilization (percentage) as of last sampling.

MIB: EXTREME-SYSTEM-MIB

Operational status of a cooling fan.

MIB: EXTREME-SYSTEM-MIB

The speed (RPM) of a cooling fan in the fantray {#SNMPVALUE}

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

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_HEARTBEAT: 12h

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_HEARTBEAT: 12h

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_HEARTBEAT: 12h

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_HEARTBEAT: 12h

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_HEARTBEAT: 12h

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: EXTREME-SYSTEM-MIB

The software revision of the primary image stored in this device.

This string will have a zero length if the revision is unknown, invalid or not present.

This will also be reported in RMON2 probeSoftwareRev if this is the software image currently running in the device.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total amount of free memory in Kbytes in the system.

Preprocessing:

- MULTIPLIER: 1024

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total amount of DRAM in Kbytes in the system.

Preprocessing:

- MULTIPLIER: 1024

Memory utilization in %.

Expression:

MIB: EtherLike-MIB

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.

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.

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

- MULTIPLIER: 8

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

- MULTIPLIER: 8

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

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 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

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

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_HEARTBEAT: 1d

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:

- MULTIPLIER: 1000000

- DISCARD_UNCHANGED_HEARTBEAT: 1h

MIB: EXTREME-SYSTEM-MIB

Status of the power supply {#SNMPVALUE}

MIB: SNMPv2-MIB

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

Preprocessing:

- 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_NOT_SUPPORTED

⛔️ON_FAIL: CUSTOM_VALUE -> 0

- MULTIPLIER: 0.01

Availability of SNMP checks on the host. The value of this item corresponds to availability icons in the host list.

Possible value:

0 - not available

1 - available

2 - unknown

-

-

-

MIB: EXTREME-SYSTEM-MIB

Temperature readings of testpoint: Device

Reference: https://gtacknowledge.extremenetworks.com/articles/Q_A/Does-EXOS-support-temperature-polling-via-SNMP-on-all-nodes-in-a-stack

MIB: EXTREME-SYSTEM-MIB

Temperature status of testpoint: Device

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

Please check the fan unit

System name has changed. Ack to close.

Manual close: YES

Device serial number has changed. Ack to close

Manual close: YES

Firmware version has changed. Ack to close

Manual close: YES

Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.

Manual close: YES

Depends on:

- System name has changed

The system is running out of free memory.

Please check autonegotiation settings and cabling

Manual close: YES

This trigger expression works as follows:

1. Can be triggered if operations status is down.

2. {$IFCONTROL:"{#IFNAME}"}=1 - 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.

3. {TEMPLATE_NAME:METRIC.diff()}=1) - trigger fires only if operational status was up(1) sometime before. (So, do not fire 'ethernal off' interfaces.)

WARNING: if closed manually - won't fire again on next poll, because of .diff.

Recovery expression:

Manual close: YES

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

Recovery expression:

Manual close: YES

Depends on:

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

Recovers when below 80% of {$IF.ERRORS.WARN:"{#IFNAME}"} threshold

Recovery expression:

Manual close: YES

Depends on:

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

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

Recovery expression:

Manual close: YES

Depends on:

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

Please check the power supply unit for errors

Uptime is less than 10 minutes.

Manual close: YES

Depends on:

- No SNMP data collection

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

Depends on:

- Unavailable by ICMP ping

Last three attempts returned timeout. Please check device connectivity.

-

Depends on:

- Unavailable by ICMP ping

-

Depends on:

- High ICMP ping loss

- Unavailable by ICMP ping

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

Recovery expression:

Depends on:

- Device: Temperature is above critical threshold

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

Recovery expression:

-

Recovery expression:

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

Ignore notPresent(6)

Ignore notPresent(6)

Ignore down(2) administrative status

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total CPU utilization (percentage) as of last sampling.

MIB: EXTREME-SYSTEM-MIB

Temperature readings of testpoint: Device

Reference: https://gtacknowledge.extremenetworks.com/articles/Q_A/Does-EXOS-support-temperature-polling-via-SNMP-on-all-nodes-in-a-stack

MIB: EXTREME-SYSTEM-MIB

Temperature status of testpoint: Device

MIB: ENTITY-MIB

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: ENTITY-MIB

Preprocessing

• Discard unchanged with heartbeat: 1d

MIB: EXTREME-SYSTEM-MIB

The software revision of the primary image stored in this device.

This string will have a zero length if the revision is unknown, invalid or not present.

This will also be reported in RMON2 probeSoftwareRev if this is the software image currently running in the device.

Preprocessing

• 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

  ⛔️Custom on fail: Set value to: 0

• Custom multiplier: 0.01

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

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: 12h

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: 12h

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: 12h

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: 12h

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: 12h

Availability of SNMP checks on the host. The value of this item corresponds to availability icons in the host list.

Possible value:

0 - not available

1 - available

2 - unknown

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

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

• Device: Temperature is above critical threshold

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

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

Firmware version has changed. Acknowledge to close the problem manually.

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

• Extreme EXOS: System name has changed

Uptime is less than 10 minutes.

• Extreme EXOS: No SNMP data collection

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

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

• Extreme EXOS: Unavailable by ICMP ping

Last three attempts returned timeout. Please check device connectivity.

• Extreme EXOS: Unavailable by ICMP ping

• Extreme EXOS: High ICMP ping loss
• Extreme EXOS: Unavailable by ICMP ping

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total amount of free memory in Kbytes in the system.

Preprocessing

• Custom multiplier: 1024

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total amount of DRAM in Kbytes in the system.

Preprocessing

• Custom multiplier: 1024

Memory utilization in %.

The system is running out of free memory.

Table of status of all power supplies in the system.

MIB: EXTREME-SYSTEM-MIB

Status of the power supply {#SNMPVALUE}

Please check the power supply unit for errors

MIB: EXTREME-SYSTEM-MIB

Operational status of a cooling fan.

MIB: EXTREME-SYSTEM-MIB

The speed (RPM) of a cooling fan in the fantray {#SNMPVALUE}

Please check the fan unit

Discovering interfaces from IF-MIB.

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.

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 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

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

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 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

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

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: 1d

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

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.3. {TEMPLATE_NAME:METRIC.diff()}=1 - the trigger fires only if the operational status was up to (1) sometime before (so, do not fire for the 'eternal off' interfaces.)WARNING: if closed manually - it will not fire again on the next poll, because of .diff.

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

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

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

Preprocessing

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

MIB: EtherLike-MIB

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

-

-

-

-

-

-

-

-

-

Table of status of all power supplies in the system.

-

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total CPU utlization (percentage) as of last sampling.

MIB: EXTREME-SYSTEM-MIB

Operational status of a cooling fan.

MIB: EXTREME-SYSTEM-MIB

The speed (RPM) of a cooling fan in the fantray {#SNMPVALUE}

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: EXTREME-SYSTEM-MIB

The software revision of the primary image stored in this device.

This string will have a zero length if the revision is unknown, invalid or not present.

This will also be reported in RMON2 probeSoftwareRev if this is the software image currently running in the device.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total amount of free memory in Kbytes in the system.

Preprocessing:

- MULTIPLIER: 1024

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total amount of DRAM in Kbytes in the system.

Preprocessing:

- MULTIPLIER: 1024

Memory utilization in %

Expression:

MIB: EXTREME-SYSTEM-MIB

Status of the power supply {#SNMPVALUE}

MIB: EXTREME-SYSTEM-MIB

Temperature readings of testpoint: Device

Reference: https://gtacknowledge.extremenetworks.com/articles/Q_A/Does-EXOS-support-temperature-polling-via-SNMP-on-all-nodes-in-a-stack

MIB: EXTREME-SYSTEM-MIB

Temperature status of testpoint: Device

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

Please check the fan unit

Device serial number has changed. Ack to close

Manual close: YES

Firmware version has changed. Ack to close

Manual close: YES

Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.

Manual close: YES

The system is running out of free memory.

Please check the power supply unit for errors

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

Recovery expression:

Depends on:

- Device: Temperature is above critical threshold: >{$TEMP_CRIT:""}

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

Recovery expression:

-

Recovery expression:

-

-

-

-

-

-

-

-

-

Table of status of all power supplies in the system.

-

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total CPU utilization (percentage) as of last sampling.

MIB: EXTREME-SYSTEM-MIB

Operational status of a cooling fan.

MIB: EXTREME-SYSTEM-MIB

The speed (RPM) of a cooling fan in the fantray {#SNMPVALUE}

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: ENTITY-MIB

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: EXTREME-SYSTEM-MIB

The software revision of the primary image stored in this device.

This string will have a zero length if the revision is unknown, invalid or not present.

This will also be reported in RMON2 probeSoftwareRev if this is the software image currently running in the device.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1d

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total amount of free memory in Kbytes in the system.

Preprocessing:

- MULTIPLIER: 1024

MIB: EXTREME-SOFTWARE-MONITOR-MIB

Total amount of DRAM in Kbytes in the system.

Preprocessing:

- MULTIPLIER: 1024

Memory utilization in %.

Expression:

MIB: EXTREME-SYSTEM-MIB

Status of the power supply {#SNMPVALUE}

MIB: EXTREME-SYSTEM-MIB

Temperature readings of testpoint: Device

Reference: https://gtacknowledge.extremenetworks.com/articles/Q_A/Does-EXOS-support-temperature-polling-via-SNMP-on-all-nodes-in-a-stack

MIB: EXTREME-SYSTEM-MIB

Temperature status of testpoint: Device

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

Please check the fan unit

Device serial number has changed. Ack to close

Manual close: YES

Firmware version has changed. Ack to close

Manual close: YES

Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.

Manual close: YES

The system is running out of free memory.

Please check the power supply unit for errors

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

Recovery expression:

Depends on:

- Device: Temperature is above critical threshold: >{$TEMP_CRIT:""}

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

Recovery expression:

-

Recovery expression: