FORCES-MIB

        This MIB module contains managed object definitions
for the ForCES Protocol.
        
Copyright (c) 2010 IETF Trust and the persons identified
as authors of the code.  All rights reserved.
        
Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and
subject to the license terms contained in, the
Simplified BSD License set forth in Section 4.c of the
IETF Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
        
This version of this MIB module is part of RFC 5813;
see the RFC itself for full legal notices.
    
Source file
FORCES-MIB
Last revised
Identity
forcesMib
Base OID
1.3.6.1.2.1.187
Imported Objects
RMON2-MIB ZeroBasedCounter32
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 mib-2 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC TEXTUAL-CONVENTION (no object page) TimeStamp
Net-SNMP examples using the rfc 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 'FORCES-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'FORCES-MIB::forcesMib'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'FORCES-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'FORCES-MIB::forcesMib'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (20)
.1.3.6.1.2.1.187
.1.3.6.1.2.1.187.0
.1.3.6.1.2.1.187.1
.1.3.6.1.2.1.187.1.1
.1.3.6.1.2.1.187.1.2
.1.3.6.1.2.1.187.1.2.1
.1.3.6.1.2.1.187.1.2.1.1
.1.3.6.1.2.1.187.1.2.1.1.1
.1.3.6.1.2.1.187.1.2.1.1.10
.1.3.6.1.2.1.187.1.2.1.1.2
.1.3.6.1.2.1.187.1.2.1.1.3
.1.3.6.1.2.1.187.1.2.1.1.4
.1.3.6.1.2.1.187.1.2.1.1.5
.1.3.6.1.2.1.187.1.2.1.1.6
.1.3.6.1.2.1.187.1.2.1.1.7
.1.3.6.1.2.1.187.1.2.1.1.8
.1.3.6.1.2.1.187.1.2.1.1.9
.1.3.6.1.2.1.187.2
.1.3.6.1.2.1.187.2.1
.1.3.6.1.2.1.187.2.2
Dependencies (13) 4 direct · 9 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
Type Definitions (2)
OctetString range: 4
Integer32 range: 1..255
Conformance Groups (4)
A collection of notifications for signaling
important ForCES events.
.1.3.6.1.2.1.187.2.2.1
A collection of objects to support management
of ForCES routers.
.1.3.6.1.2.1.187.2.2.2
A collection of optional notifications for
signaling important ForCES events including
statistics.
.1.3.6.1.2.1.187.2.2.3
A collection of optional objects to provide
extra information about the associations.
There is no protocol reason to keep such
information, but these objects can be very
useful in debugging connectivity problems.
.1.3.6.1.2.1.187.2.2.4
Compliance Statements (1)

OID .1.3.6.1.2.1.187.2.1.1
The compliance statement for routers running
ForCES and implementing the ForCES MIB.
Required groups
mandatory forcesMibGroup
mandatory forcesNotificationGroup
optional forcesNotificationStatsGroup Implementation of this group is recommended.
optional forcesStatsGroup Implementation of this group is recommended.
Notifications / Traps (4)
NameOIDDescription
.1.3.6.1.2.1.187.0.1
This notification is generated as soon
as an association enters the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations.
.1.3.6.1.2.1.187.0.2
This notification is generated as soon
as an association leaves the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations.
.1.3.6.1.2.1.187.0.3
This notification is generated as soon
as an association enters the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations.
.1.3.6.1.2.1.187.0.4
This notification is generated as soon
as an association leaves the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations.