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. |
InterfaceIndex | IF-MIB |
mplsFrrGeneralConstraintsGroup, mplsFrrGeneralTunnelARHopGroup, mplsFrrGeneralScalarGroup | MPLS-FRR-GENERAL-STD-MIB |
MplsBitRate, MplsLsrIdentifier, MplsTunnelInstanceIndex, MplsTunnelIndex | MPLS-TC-STD-MIB |
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP | SNMPv2-CONF |
OBJECT-TYPE, Gauge32, NOTIFICATION-TYPE, Integer32, mib-2, MODULE-IDENTITY | SNMPv2-SMI |
TruthValue | SNMPv2-TC |
Name | OID | Description |
---|---|---|
.1.3.6.1.2.1.204.0.1 | ication 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 | ication 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. |