MPLS-FRR-FACILITY-STD-MIB

        Copyright (c) 2011 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 MIB module contains object definitions for the
MPLS Traffic Engineering facility backup method for
Fast Reroute as defined in RFC 4090.
    
Source file
MPLS-FRR-FACILITY-STD-MIB
Last revised
Identity
mplsFrrFacilityMIB
Base OID
1.3.6.1.2.1.204
Imported Objects
IF-MIB InterfaceIndex
MPLS-FRR-GENERAL-STD-MIB mplsFrrGeneralConstraintsGroup (no object page) mplsFrrGeneralScalarGroup (no object page) mplsFrrGeneralTunnelARHopGroup (no object page)
MPLS-TC-STD-MIB MplsBitRate MplsLsrIdentifier MplsTunnelIndex MplsTunnelInstanceIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Gauge32 Integer32 mib-2 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC TruthValue
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 'MPLS-FRR-FACILITY-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'MPLS-FRR-FACILITY-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (25)
.1.3.6.1.2.1.204
.1.3.6.1.2.1.204.0
.1.3.6.1.2.1.204.1
Integer32
.1.3.6.1.2.1.204.1.1
.1.3.6.1.2.1.204.1.2
.1.3.6.1.2.1.204.1.3
.1.3.6.1.2.1.204.1.4
.1.3.6.1.2.1.204.1.5
Notifications per SecondSNMPv2-SMIGauge32
.1.3.6.1.2.1.204.1.6
.1.3.6.1.2.1.204.1.7
.1.3.6.1.2.1.204.1.7.1
.1.3.6.1.2.1.204.1.7.1.1
Enumeration
.1.3.6.1.2.1.204.1.7.1.10
kilobits per secondMPLS-TC-STD-MIBMplsBitRate
.1.3.6.1.2.1.204.1.7.1.11
.1.3.6.1.2.1.204.1.7.1.2
.1.3.6.1.2.1.204.1.7.1.3
.1.3.6.1.2.1.204.1.7.1.4
.1.3.6.1.2.1.204.1.7.1.5
.1.3.6.1.2.1.204.1.7.1.6
.1.3.6.1.2.1.204.1.7.1.7
.1.3.6.1.2.1.204.1.7.1.8
.1.3.6.1.2.1.204.1.7.1.9
.1.3.6.1.2.1.204.2
.1.3.6.1.2.1.204.2.1
.1.3.6.1.2.1.204.2.2
Dependencies (14) 6 direct · 8 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
Compliance Statements (2)

OID .1.3.6.1.2.1.204.2.1.1
Compliance statements for SNMP engines that support the
MPLS-FRR-FACILITY-STD-MIB module.
Required groups

OID .1.3.6.1.2.1.204.2.1.2
Compliance statements for SNMP engines that support the
MPLS-FRR-FACILITY-STD-MIB module.
Required groups
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.2.1.204.0.1
This notification is generated when a tunnel running over an
interface as specified in the mplsFrrConstraintsTable is
initially protected by the backup tunnel also specified in the
mplsFrrConstraintsTable. In some implementations, there may
be a difference between when the control plane triggers
this notification and when the hardware is programmed to
utilize the protection path. Due to the urgency of this
operation, it is acceptable for the control plane to
issue this notification either before or after it programs
the hardware. In cases where it is the latter approach,
the notification MUST be sent immediately after the
data plane has been altered.

This notification should not be generated for each subsequent
tunnel that is backed up by the FRR feature on this LSR, as
this may result in potential scaling issues with regard to
LSR performance and network load. Note also that
notifications MUST be generated in accordance with the

mplsFrrNotificationsMaxRate.
.1.3.6.1.2.1.204.0.2
This notification is generated when the final tunnel that is
being protected by a backup tunnel as specified in the
mplsFrrConstraintsTable is restored to normal operation. This
notification should not be generated for each restored tunnel,
as this may result in potential scaling issues with regard to
LSR performance and network load. Note also that
notifications MUST be generated in accordance with the
mplsFrrNotificationsMaxRate.