PEAKFLOW-TMS-MIB

Monitored by Observium
        Peakflow TMS MIB
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Memory Processors Storage
Explore Observium network monitoring
Source file
PEAKFLOW-TMS-MIB
Last revised
Identity
peakflowTmsMIB
Base OID
1.3.6.1.4.1.9694.1.5
Imported Objects
ARBOR-SMI arbornetworksProducts
IF-MIB ifName
IPV6-TC Ipv6Address Ipv6AddressPrefix
SNMPv2-MIB sysName
SNMPv2-SMI Gauge32 Integer32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) TimeTicks Unsigned32
SNMPv2-TC DisplayString TEXTUAL-CONVENTION (no object page)
Net-SNMP examples using the arbor MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'PEAKFLOW-TMS-MIB' -M '/opt/observium/mibs/arbor:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'PEAKFLOW-TMS-MIB::peakflowTmsMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'PEAKFLOW-TMS-MIB' -M '/opt/observium/mibs/arbor:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'PEAKFLOW-TMS-MIB::peakflowTmsMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (42)
1 directly used by Observium
.1.3.6.1.4.1.9694.1.5
.1.3.6.1.4.1.9694.1.5.2
.1.3.6.1.4.1.9694.1.5.2.1
.1.3.6.1.4.1.9694.1.5.2.10
.1.3.6.1.4.1.9694.1.5.2.11
.1.3.6.1.4.1.9694.1.5.2.12
.1.3.6.1.4.1.9694.1.5.2.13
.1.3.6.1.4.1.9694.1.5.2.14
.1.3.6.1.4.1.9694.1.5.2.15
.1.3.6.1.4.1.9694.1.5.2.16
.1.3.6.1.4.1.9694.1.5.2.17
.1.3.6.1.4.1.9694.1.5.2.18
.1.3.6.1.4.1.9694.1.5.2.19
.1.3.6.1.4.1.9694.1.5.2.2
.1.3.6.1.4.1.9694.1.5.2.20
.1.3.6.1.4.1.9694.1.5.2.21
.1.3.6.1.4.1.9694.1.5.2.3
.1.3.6.1.4.1.9694.1.5.2.39
.1.3.6.1.4.1.9694.1.5.2.4
.1.3.6.1.4.1.9694.1.5.2.5
.1.3.6.1.4.1.9694.1.5.2.6
.1.3.6.1.4.1.9694.1.5.2.7
.1.3.6.1.4.1.9694.1.5.2.8
.1.3.6.1.4.1.9694.1.5.2.9
.1.3.6.1.4.1.9694.1.5.3
.1.3.6.1.4.1.9694.1.5.3.0
.1.3.6.1.4.1.9694.1.5.5
.1.3.6.1.4.1.9694.1.5.5.1
.1.3.6.1.4.1.9694.1.5.5.1.1
.1.3.6.1.4.1.9694.1.5.5.1.2
.1.3.6.1.4.1.9694.1.5.5.2
.1.3.6.1.4.1.9694.1.5.5.2.1
.1.3.6.1.4.1.9694.1.5.5.2.2
.1.3.6.1.4.1.9694.1.5.5.2.3
.1.3.6.1.4.1.9694.1.5.5.2.3.1
.1.3.6.1.4.1.9694.1.5.5.2.3.1.1
.1.3.6.1.4.1.9694.1.5.5.2.3.1.2
.1.3.6.1.4.1.9694.1.5.5.2.3.1.3
Unsigned32
.1.3.6.1.4.1.9694.1.5.5.2.3.1.4
.1.3.6.1.4.1.9694.1.5.5.2.3.1.5
.1.3.6.1.4.1.9694.1.5.5.2.3.1.6
Unsigned32
.1.3.6.1.4.1.9694.1.5.5.2.3.1.7
Dependencies (8) 6 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. ARBOR-SMIarbor
  4. IANAifType-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMPv2-MIBrfc
  7. IF-MIBrfc
  8. IPV6-TCrfc
  9. PEAKFLOW-TMS-MIBarborselected
Type Definitions (4)
Integer32
Integer32 range: 0..100
Integer32 range: 1..2147483647
Integer32 range: 0..2147483647
Notifications / Traps (46)
NameOIDDescription
hostFault obsolete
.1.3.6.1.4.1.9694.1.5.3.0.1
Obsolete; replaced by a number of more specific traps.
.1.3.6.1.4.1.9694.1.5.3.0.10
Generated when the nexthop host cannot be contacted
.1.3.6.1.4.1.9694.1.5.3.0.11
Generated when the nexthop host cannot be contacted
.1.3.6.1.4.1.9694.1.5.3.0.12
A mitigation cannot run because of a configuration error
.1.3.6.1.4.1.9694.1.5.3.0.13
A mitigation has been suspended due to some external problem
(nexthop not reachable, BGP down, etc.)
.1.3.6.1.4.1.9694.1.5.3.0.14
A previously-detected mitigation problem has been cleared and
the mitigation is now running
.1.3.6.1.4.1.9694.1.5.3.0.15
Generated when a TMS configuration file cannot be found.
.1.3.6.1.4.1.9694.1.5.3.0.16
Generated when an error in a TMS configuration file
is detected.
.1.3.6.1.4.1.9694.1.5.3.0.17
All configuration problems have been corrected.
.1.3.6.1.4.1.9694.1.5.3.0.18
A hardware device has failed.
.1.3.6.1.4.1.9694.1.5.3.0.19
A hardware device failure has been corrected.
.1.3.6.1.4.1.9694.1.5.3.0.2
The greTunnelDown/greTunnelUp traps are generated when a GRE
tunnel changes state.
.1.3.6.1.4.1.9694.1.5.3.0.20
A hardware sensor is reading an alarm condition.
.1.3.6.1.4.1.9694.1.5.3.0.21
A hardware sensor is no longer reading an alarm condition.
.1.3.6.1.4.1.9694.1.5.3.0.22
A software program has failed.
.1.3.6.1.4.1.9694.1.5.3.0.23
A software program failure has been corrected.
.1.3.6.1.4.1.9694.1.5.3.0.24
The TMS system is experiencing a critical failure.
.1.3.6.1.4.1.9694.1.5.3.0.25
The TMS system is experiencing degraded performance.
.1.3.6.1.4.1.9694.1.5.3.0.26
The TMS system has returned to normal behavior.
.1.3.6.1.4.1.9694.1.5.3.0.27
A filesystem is near capacity.
.1.3.6.1.4.1.9694.1.5.3.0.28
A filesystem is back below capacity alarm threshold.
.1.3.6.1.4.1.9694.1.5.3.0.29
A hardware sensor is in an unknown state.
.1.3.6.1.4.1.9694.1.5.3.0.3
The greTunnelDown/greTunnelUp traps are generated when a GRE
tunnel changes state.
.1.3.6.1.4.1.9694.1.5.3.0.30
Communication with SP host is up.
.1.3.6.1.4.1.9694.1.5.3.0.31
Communication with SP host is down.
.1.3.6.1.4.1.9694.1.5.3.0.32
The TMS system is experiencing an error.
.1.3.6.1.4.1.9694.1.5.3.0.33
A previously-detected automitigation problem has been cleared
and the automitigation BGP announcements have resumed.
.1.3.6.1.4.1.9694.1.5.3.0.34
Automitigation BGP announcements have been administratively
disabled.
.1.3.6.1.4.1.9694.1.5.3.0.35
Automitigation BGP announcements have been suspended due to
some external problem (nexthop not reachable, BGP down, etc.)
.1.3.6.1.4.1.9694.1.5.3.0.36
The greTunnelDown/greTunnelUp traps are generated when a GRE
tunnel changes state.
.1.3.6.1.4.1.9694.1.5.3.0.37
The greTunnelDown/greTunnelUp traps are generated when a GRE
tunnel changes state.
.1.3.6.1.4.1.9694.1.5.3.0.38
Generated when a BGP neighbor transitions out of
the ESTABLISHED state.
.1.3.6.1.4.1.9694.1.5.3.0.39
Generated when a BGP neighbor transitions into
the ESTABLISHED state.
tmsLinkUp obsolete
.1.3.6.1.4.1.9694.1.5.3.0.4
Obsolete; IF-MIB::linkUp is now used instead
.1.3.6.1.4.1.9694.1.5.3.0.40
Generated when the nexthop host becomes unreachable.
.1.3.6.1.4.1.9694.1.5.3.0.41
Generated when the nexthop host becomes reachable.
.1.3.6.1.4.1.9694.1.5.3.0.42
Generated when the processed traffic rate matches the offered
traffic rate.
.1.3.6.1.4.1.9694.1.5.3.0.43
Generated when the processed traffic rate is lower than the
offered traffic rate.
.1.3.6.1.4.1.9694.1.5.3.0.44
BGP is currently advertising all mitigation prefixes.
.1.3.6.1.4.1.9694.1.5.3.0.45
BGP is not currently advertising all mitigation prefixes.
.1.3.6.1.4.1.9694.1.5.3.0.46
Communication with SP host is degraded.
tmsLinkDown obsolete
.1.3.6.1.4.1.9694.1.5.3.0.5
Obsolete; IF-MIB::linkDown is now used instead
.1.3.6.1.4.1.9694.1.5.3.0.6
Generated when a subhost transitions to active
.1.3.6.1.4.1.9694.1.5.3.0.7
Generated when a subhost transitions to inactive
.1.3.6.1.4.1.9694.1.5.3.0.8
Generated when a BGP neighbor transitions out of
the ESTABLISHED state
.1.3.6.1.4.1.9694.1.5.3.0.9
Generated when a BGP neighbor transitions into
the ESTABLISHED state