draft-ietf-mpls-tp-linear-protection-mib-05.txt   draft-ietf-mpls-tp-linear-protection-mib-06.txt 
Internet Engineering Task Force Kingston Smiler Selvaraj MPLS Working Group Kingston Smiler Selvaraj
Internet-Draft IpInfusion Internet-Draft IpInfusion
Intended status: Standards Track M.Venkatesan Intended status: Standards Track M. Venkatesan
Expires: February 04, 2016 Dell Inc. Expires: June 8, 2016 Dell Inc.
V. Manral V. Manral
Ionos Corp. Ionos Corp
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
Sam Aldrin Sam Aldrin
Google, Inc. Google, Inc.
August 03, 2015 J. Ryoo
ETRI
December 6, 2015
MPLS Transport Profile Linear Protection MIB MPLS Transport Profile Linear Protection MIB
draft-ietf-mpls-tp-linear-protection-mib-05 draft-ietf-mpls-tp-linear-protection-mib-06
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines for use with network management protocols. In particular it defines
objects for managing MPLS Transport Profile (MPLS-TP) Linear objects for managing MPLS Transport Profile (MPLS-TP) Linear
Protection. Protection.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on June 8, 2016.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 04, 2016.
Copyright and License Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4
5.2. The MPLS TP Linear Protection Subtree . . . . . . . . . . . 4 5.2. The MPLS-TP Linear Protection Subtree . . . . . . . . . . 4
5.3. The Notifications Subtree . . . . . . . . . . . . . . . . . 4 5.3. The Notifications Subtree . . . . . . . . . . . . . . . . 4
5.4. The Table Structures . . . . . . . . . . . . . . . . . . . 4 5.4. The Table Structures . . . . . . . . . . . . . . . . . . 5
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6
6.1. Relationship to the MPLS OAM maintenance identifiers MIB 6.1. Relationship to the MPLS OAM maintenance identifiers MIB
module . . . . . . . . . . . . . . . . . . . . . . . . . . 5 module . . . . . . . . . . . . . . . . . . . . . . . . . 6
7. Example of Protection switching configuration for MPLS-TP TE 7. Example of Protection switching configuration for
tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 MPLS-TP TE tunnel . . . . . . . . . . . . . . . . . . . . . . 6
8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8
9. Security Considerations . . . . . . . . . . . . . . . . . . . 26 9. Security Considerations . . . . . . . . . . . . . . . . . . . 34
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 36
11.1. Normative References . . . . . . . . . . . . . . . . . . 28 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 36
11.2. Informative References . . . . . . . . . . . . . . . . . 29 12.1. Normative References . . . . . . . . . . . . . . . . . . 36
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30 12.2. Informative References . . . . . . . . . . . . . . . . . 36
13. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines for use with network management protocols. In particular it defines
objects for managing MPLS Transport Profile (MPLS-TP) Linear objects for managing MPLS Transport Profile (MPLS-TP) Linear
Protection. Protection.
This MIB module should be used for configuring and managing the MPLS This MIB module should be used for configuring and managing the MPLS-
TP linear protection for MPLS TP LSPs. TP linear protection for MPLS-TP LSPs.
At the time of writing, SNMP SET is no longer recommended as a way to At the time of writing, SNMP SET is no longer recommended as a way to
configure MPLS networks as was described in [RFC3812]. However, configure MPLS networks as was described in RFC 3812 [RFC3812].
since the MIB modules specified in this document are intended to work However, since the MIB modules specified in this document are
in parallel with the MIB modules for MPLS specified in [RFC3812], intended to work in parallel with the MIB modules for MPLS specified
certain objects defined here are specified with MAX-ACCESS of read- in [RFC3812], certain objects defined here are specified with MAX-
write or read-create so that specifications of the base tables in ACCESS of read- write or read-create so that specifications of the
[RFC3812] and the new MIB modules in this document are consistent. base tables in [RFC3812] and the new MIB modules in this document are
Although the examples described in Section 7 specify means to consistent. Although the examples described in Section 7 specify
configure OAM identifiers for MPLS-TP tunnels, this should be seen as means to configure OAM identifiers for MPLS-TP tunnels, this should
indicating how the MIB values would be returned in the specified be seen as indicating how the MIB values would be returned in the
circumstances having been configured by alternative means. specified circumstances having been configured by alternative means.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Conventions 3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119].
4. Overview 4. Overview
[RFC6378] defines the protocol to provide a linear protection RFC 6378 [RFC6378] defines the protocol to provide a linear
switching mechanism for MPLS transport profile with protection protection switching mechanism for MPLS transport profile with
domain as point-to-point LSP. The detailed protocol specification of protection domain as a point-to-point LSP. RFC 7271 [RFC7271]
MPLS transport profile linear protection is described in [RFC6378]. describes alternate mechanisms to perform some of the functions
This document specifies a MIB module for the LER that supports MPLS defined in [RFC6378], and also defines additional mechanisms, in
TP Linear protection and a MIB module that defines textual order to provide operator control and experience that more closely
conventions. models the behavior of linear protection seen in other transport
networks. Two modes are defined for MPLS-TP linear protection
switching: Protection State Coordination (PSC) mode and Automatic
Protection Switching (APS) mode as specified in [RFC6378] and
[RFC7271], respectively. The detailed protocol specification of MPLS
transport profile linear protection is described in [RFC6378] and
[RFC7271].
This document specifies a MIB module for the Label Edge Router (LER)
that supports MPLS TP Linear protection and a MIB module that defines
textual conventions. Objects defined in the document are generally
applied to both PSC and APS modes. If an object is valid for a
particular mode only, it is noted in the description for the object.
5. Structure of the MIB Module 5. Structure of the MIB Module
5.1. Textual Conventions 5.1. Textual Conventions
The following new textual conventions are defined in a separate MIB The following new textual conventions are defined in a separate MIB
module in this document module in this document
MplsLpsReq MplsLpsReq
MplsLpsFpathPath MplsLpsFpathPath
MplsLpsCommand MplsLpsCommand
MplsLpsState
5.2. The MPLS TP Linear Protection Subtree 5.2. The MPLS-TP Linear Protection Subtree
MPLS-LPS-MIB is the MIB module defined in this document, and it is MPLS-LPS-MIB is the MIB module defined in this document, and it is
put under mplsStdMIB. put under mplsStdMIB.
5.3. The Notifications Subtree 5.3. The Notifications Subtree
Notifications are defined to inform the management station about Notifications are defined to inform the management station about
switchover and mode mismatch of linear protection switching group. switchover, provisioning mismatches, and protocol failures of linear
Two notifications are defined for this purpose. The notification, protection domain. The following notifications are defined for this
mplsLpsEventSwitchover is to inform the management station about the purpose:
switchover of the active path and the notification
mplsLpsEventModeMismatch is to inform the management station about o The notification, mplsLpsEventSwitchover is to inform the
the mismatch in the revertive mode across the end point of the management station about the switchover of the active path.
protection domain.
o The notification, mplsLpsEventRevertiveMismatch is to inform the
management station about the provisioning mismatch in the
revertive mode across the end point of the protection domain.
o The notification, mplsLpsEventProtecTypeMismatch is to inform the
management station about the provisioning mismatch in protection
type, representing both bridge and switching types, across the end
point of the protection domain.
o The notification, mplsLpsEventCapabilitiesMismatch is to inform
the management station about the provisioning mismatch in
Capabilities TLVs across the end point of the protection domain.
o The notification, mplsLpsEventPathConfigMismatch is to inform the
management station about the provisioning mismatch in the
protection path configuration for PSC communication.
o The notification, mplsLpsEventFopNoResponse is to inform the
management station about the failure of protocol due to a lack of
response to a traffic switchover request in 50 ms.
o The notification, mplsLpsEventFopTimOut is to inform the
management station about the failure of protocol due to no
protocol message received during at least 3.5 times the long PSC
message interval.
5.4. The Table Structures 5.4. The Table Structures
The MPLS TP Linear protection MIB module has four tables. The tables The MPLS-TP linear protection MIB module has four tables. The tables
are as follows are as follows
o mplsLpsConfigTable o mplsLpsConfigTable
This table is used to configure MPLS TP Linear protection This table is used to configure MPLS-TP linear protection domain.
switching Group. The protection switching group is identified by The protection domain is identified by mplsLpsConfigGroupName.
mplsLpsConfigGroupName. The other attributes in this table can be The other attributes in this table can be used to configure
used to configure properties that are specific to the protection properties that are specific to the protection domain.
switching group.
o mplsLpsStatusTable o mplsLpsStatusTable
This table provides the current status information of mpls linear
protection groups that have been configured on the system. When a This table provides the current status information of MPLS-TP
protection group is configured or deleted in the linear protection domains that have been configured on the system.
When a protection domain is configured or deleted in the
mplsLpsConfigTable, then the corresponding row of that session in mplsLpsConfigTable, then the corresponding row of that session in
the mplsLpsStatusTable is, respectively, automatically created or the mplsLpsStatusTable is, respectively, automatically created or
deleted. deleted.
o mplsLpsMeConfigTable o mplsLpsMeConfigTable
This table is used to associate the Maintenance Entities (MEs) to This table is used to associate the Maintenance Entities (MEs) to
the protection switching group. The ME is identified by the protection domain. The ME is identified by mplsOamIdMegIndex,
mplsOamIdMegIndex, mplsOamIdMeIndex and mplsOamIdMeMpIndex. mplsOamIdMeIndex and mplsOamIdMeMpIndex.
o mplsLpsMeStatusTable o mplsLpsMeStatusTable
This table provides the current information about the protection This table provides the current information about the protection
state of MEs that have been configured on the system. When a state of MEs that have been configured on the system. When a ME
ME configured or deleted in the mplsLpsMeConfigTable, then the configured or deleted in the mplsLpsMeConfigTable, then the
corresponding row of that session in the mplsLpsMeStatusTable corresponding row of that session in the mplsLpsMeStatusTable is,
is, respectively, automatically created or deleted. respectively, automatically created or deleted.
6. Relationship to Other MIB Modules 6. Relationship to Other MIB Modules
6.1. Relationship to the MPLS OAM maintenance identifiers MIB module 6.1. Relationship to the MPLS OAM maintenance identifiers MIB module
The mplsLpsMeConfigTable entry is extended by entry in the The mplsLpsMeConfigTable entry is extended by entry in the
mplsOamIdMeTable [MPLS-OAM-ID-STD-MIB] defined in draft-ietf-mpls-tp- mplsOamIdMeTable defined in draft-ietf-mpls-tp-oam-id-mib
oam-id-mib. Note that the nature of the 'extends' relationship is a [I-D.ietf-mpls-tp-oam-id-mib]. Note that the nature of the 'extends'
sparse augmentation so that the entry in the mplsLpsMeConfigTable has relationship is a sparse augmentation so that the entry in the
the same index values as the entry in the mplsOamIdMeTable. Each time mplsLpsMeConfigTable has the same index values as the entry in the
that an entry is created in the mplsOamIdMeTable for which the LER mplsOamIdMeTable. Each time that an entry is created in the
supports MPLS TP Linear protection a row is created automatically in mplsOamIdMeTable for which the LER supports MPLS-TP linear protection
the mplsLpsMeConfigTable. a row is created automatically in the mplsLpsMeConfigTable.
7. Example of Protection switching configuration for MPLS-TP TE tunnel 7. Example of Protection switching configuration for MPLS-TP TE tunnel
This example considers the protection group configuration on a This example considers the protection domain configuration on a head-
head-end LSR to provide protection for a co-routed bidirectional end LSR to provide protection for a co-routed bidirectional MPLS
MPLS tunnel. tunnel.
Only relevant objects which are applicable for protection group
identifiers of co-routed MPLS tunnel are illustrated here.
In mplsOamIdMegTable: Only relevant objects which are applicable for protection domain
{ identifiers of co-routed MPLS tunnel are illustrated here.
-- MEG index (Index to the table)
mplsOamIdMegIndex = 1,
mplsOamIdMegName = "MEG1",
mplsOamIdMegOperatorType = ipCompatible (1),
mplsOamIdMegServiceType = lsp (1),
mplsOamIdMegMpLocation = perNode(1),
-- Mandatory parameters needed to activate the row go here
mplsOamIdMegRowStatus = createAndGo (4)
}
This will create an entry in the mplsOamIdMegTable to protect In mplsOamIdMegTable:
the MPLS tunnel. {
-- MEG index (Index to the table)
mplsOamIdMegIndex = 1,
mplsOamIdMegName = "MEG1",
mplsOamIdMegOperatorType = ipCompatible (1),
mplsOamIdMegServiceType = lsp (1),
mplsOamIdMegMpLocation = perNode(1),
-- Mandatory parameters needed to activate the row go here
mplsOamIdMegRowStatus = createAndGo (4)
}
The following ME table is used to associate the path information This will create an entry in the mplsOamIdMegTable to protect the
to a MEG. MPLS tunnel.
In mplsOamIdMeTable: The following ME table is used to associate the path information to a
{ MEG.
-- ME index (Index to the table)
mplsOamIdMeIndex = 1,
-- MP index (Index to the table)
mplsOamIdMeMpIndex = 1,
mplsOamIdMeName = "ME1",
mplsOamIdMeMpIfIndex = 0,
-- Source MEP id is derived from the IP compatible MPLS
-- tunnel
mplsOamIdMeSourceMepIndex = 0,
-- Source MEP id is derived from the IP compatible MPLS
-- tunnel
mplsOamIdMeSinkMepIndex = 0,
mplsOamIdMeMpType = mep (1),
mplsOamIdMeMepDirection = down (2),
mplsOamIdMeProactiveOamPhbTCValue = 0,
mplsOamIdMeOnDemandOamPhbTCValue = 0,
-- RowPointer MUST point to the first accessible column
-- of an MPLS tunnel
mplsOamIdMeServicePointer = mplsTunnelName.1.1.1.2,
-- Mandatory parameters needed to activate the row go here
mplsOamIdMeRowStatus = createAndGo (4)
}
The below table associates the MEs with protection switching In mplsOamIdMeTable:
groups. {
In mplsLpsConfigTable: -- ME index (Index to the table)
mplsLpsConfigEntry ::= SEQUENCE { mplsOamIdMeIndex = 1,
-- Group index -- MP index (Index to the table)
mplsLpsConfigGroupIndex = 1, mplsOamIdMeMpIndex = 1,
mplsLpsConfigGroupName = "PGGroup1", mplsOamIdMeName = "ME1",
mplsLpsConfigMode = onePlusOne (1), mplsOamIdMeMpIfIndex = 0,
-- Mandatory parameters needed to activate the row go here -- Source MEP id is derived from the IP compatible MPLS
mplsLpsConfigRowStatus = createAndGo (4) -- tunnel
} mplsOamIdMeSourceMepIndex = 0,
In mplsLpsMeConfigTable: -- Source MEP id is derived from the IP compatible MPLS
MplsLpsMeConfigEntry ::= SEQUENCE { -- tunnel
-- MEG index (Index to the table) mplsOamIdMeSinkMepIndex = 0,
mplsOamIdMegIndex = 1, mplsOamIdMeMpType = mep (1),
-- ME index mplsOamIdMeMepDirection = down (2),
mplsOamIdMeIndex = 1, mplsOamIdMeProactiveOamPhbTCValue = 0,
-- MP index (Index to the table) mplsOamIdMeOnDemandOamPhbTCValue = 0,
mplsOamIdMeMpIndex = 1, -- RowPointer MUST point to the first accessible column
-- Group index -- of an MPLS tunnel
mplsLpsMeConfigGroupIndex = 1, mplsOamIdMeServicePointer = mplsTunnelName.1.1.1.2,
-- Configuration state -- Mandatory parameters needed to activate the row go here
mplsLpsMeConfigState = primary(1) mplsOamIdMeRowStatus = createAndGo (4)
} }
The below table associates the MEs with protection domains.
In mplsLpsConfigTable:
mplsLpsConfigEntry ::= SEQUENCE {
-- Group index
mplsLpsConfigDomainIndex = 1,
mplsLpsConfigDomainName = "LPDomain1",
mplsLpsConfigMode = psc (1),
mplsLpsConfigProtectionType = oneColonOneBidirectional (2),
-- Mandatory parameters needed to activate the row go here
mplsLpsConfigRowStatus = createAndGo (4)
}
In mplsLpsMeConfigTable:
MplsLpsMeConfigEntry ::= SEQUENCE {
-- MEG index (Index to the table)
mplsOamIdMegIndex = 1,
-- ME index
mplsOamIdMeIndex = 1,
-- MP index (Index to the table)
mplsOamIdMeMpIndex = 1,
-- Group index
mplsLpsMeConfigDomainIndex = 1,
-- Configuration state
mplsLpsMeConfigState = working(1)
}
8. Definitions 8. Definitions
MPLS-LPS-MIB DEFINITIONS ::= BEGIN MPLS-LPS-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE,
Gauge32, Counter32, Integer32, Unsigned32 Gauge32, Counter32, Integer32, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
TEXTUAL-CONVENTION, RowStatus,
TimeStamp, StorageType
FROM SNMPv2-TC
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
mplsStdMIB FROM SNMPv2-CONF -- [RFC2580]
FROM MPLS-TC-STD-MIB -- [RFC3811]
mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex
FROM MPLS-OAM-ID-STD-MIB;
mplsLpsMIB MODULE-IDENTITY TEXTUAL-CONVENTION, RowStatus, TimeStamp, StorageType
LAST-UPDATED "201508030000Z" -- August 03, 2015 FROM SNMPv2-TC
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
" SnmpAdminString
Kingston Smiler FROM SNMP-FRAMEWORK-MIB
IP Infusion
RMZ Centennial
Mahadevapura Post
Bangalore - 560048 India
EMail: kingstonsmiler@gmail.com
Venkatesan Mahalingam
Dell Inc.
5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com
Vishwas Manral mplsStdMIB
Ionos Corp, FROM MPLS-TC-STD-MIB -- [RFC3811]
4100 Moorpark Ave,
San Jose, CA
Email: vishwas@ionosnetworks.com
Daniel King mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex
Old Dog Consulting FROM MPLS-OAM-ID-STD-MIB;
UK
Email:daniel@olddog.co.uk
Sam Aldrin mplsLpsMIB MODULE-IDENTITY
Google, Inc. LAST-UPDATED "201512060000Z" -- December 06, 2015
1600 Amphitheatre Parkway ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
Mountain View, CA CONTACT-INFO
USA "
Email: aldrin.ietf@gmail.com" Kingston Smiler Selvaraj
DESCRIPTION IP Infusion
"This management information module supports the RMZ Centennial
configuration and management of MPLS TP linear Mahadevapura Post
protection groups. " Bangalore - 560048 India
REVISION EMail: kingstonsmiler@gmail.com
"201508030000Z" -- August 03, 2015
DESCRIPTION
"MPLS Protection Switching Group objects for LSP
MEPs"
::= { mplsStdMIB xxx } -- xxx to be replaced with Mahalingam Venkatesan
-- correct value Dell Inc.
5450 Great America Parkway,
Santa Clara, CA 95054, USA
Email: venkat.mahalingams@gmail.com
Vishwas Manral
Ionos Corp,
4100 Moorpark Ave,
San Jose, CA
Email: vishwas@ionosnetworks.com
Daniel King
Old Dog Consulting
UK
Email:daniel@olddog.co.uk
Sam Aldrin
Google, Inc.
1600 Amphitheatre Parkway
Mountain View, CA
USA
Email: aldrin.ietf@gmail.com
Jeong-dong Ryoo
ETRI
218 Gajeong-ro
Yuseong-gu, Daejeon 34129
South Korea
Email:ryoo@etri.re.kr
"
DESCRIPTION
"This management information module supports the
configuration and management of MPLS-TP linear
protection domains. "
REVISION
"201512060000Z" -- December 06, 2015
DESCRIPTION
"MPLS-TP Protection Switching Domain objects for LSP
MEPs"
::= { mplsStdMIB xxx } -- xxx to be replaced with
-- correct value
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- Notifications -- Notifications
mplsLpsNotifications mplsLpsNotifications
OBJECT IDENTIFIER ::= { mplsLpsMIB 0 } OBJECT IDENTIFIER ::= { mplsLpsMIB 0 }
-- tables, scalars -- tables, scalars
mplsLpsObjects mplsLpsObjects
OBJECT IDENTIFIER ::= { mplsLpsMIB 1 } OBJECT IDENTIFIER ::= { mplsLpsMIB 1 }
-- conformance
-- conformance
mplsLpsConformance mplsLpsConformance
OBJECT IDENTIFIER ::= { mplsLpsMIB 2 } OBJECT IDENTIFIER ::= { mplsLpsMIB 2 }
MplsLpsReq ::= TEXTUAL-CONVENTION MplsLpsReq ::= TEXTUAL-CONVENTION
STATUS current DISPLAY-HINT "1d"
DESCRIPTION STATUS current
"This Textual Convention describes an object that stores DESCRIPTION
the PSC Request field of the PSC control packet. The values "This Textual Convention describes an object that stores
are as follows the PSC Request field of the PSC control packet. The values
are as follows
1110 Lockout of Protection 1110 Lockout of Protection
1100 Forced Switch 1100 Forced Switch
1010 Signal Fail (SF) 1010 Signal Fail (SF)
0111 Signal Degrade (SD) 0111 Signal Degrade (SD)
0101 Manual Switch 0101 Manual Switch
0100 Wait-to-Restore 0100 Wait-to-Restore
0001 Do Not Revert 0011 Exercise
0000 No Request" 0010 Reverse Request
REFERENCE 0001 Do Not Revert
"Section 4.2.2 of RFC6378" 0000 No Request"
SYNTAX OCTET STRING (SIZE (2)) REFERENCE
"Section 4.2.2 of RFC6378 and Section 8 of RFC7271"
SYNTAX OCTET STRING (SIZE (2))
MplsLpsFpathPath ::= TEXTUAL-CONVENTION MplsLpsFpathPath ::= TEXTUAL-CONVENTION
STATUS current DISPLAY-HINT "1x:"
DESCRIPTION STATUS current
"This Textual Convention describes an object that stores DESCRIPTION
the Fault Path (FPath) field and Data Path (Path) field of "This Textual Convention describes an object that stores
the PSC control packet. the Fault Path (FPath) field and Data Path (Path) field of
the PSC control packet.
FPath is located in the first octet and Path is FPath is located in the first octet and Path is
located in the second octet. Bits are numbered from left to located in the second octet. Bits are numbered from left to
right. right.
The value and the interpretation of FPath field is as follows The value and the interpretation of FPath field is as follows
2-255 for future extensions 2-255 for future extensions
1 the anomaly condition is on the working path 1 the anomaly condition is on the working path
0 the anomaly condition is on the protection path 0 the anomaly condition is on the protection path
The value and the interpretation of Path field is as follows The value and the interpretation of Path field is as follows
2-255 for future extensions 2-255 for future extensions
1 protection path is transporting user data traffic 1 protection path is transporting user data traffic
0 protection path is not transporting user data traffic 0 protection path is not transporting user data traffic
" "
REFERENCE REFERENCE
"Section 4.2.5 and 4.2.6 of RFC6378" "Section 4.2.5 and 4.2.6 of RFC6378"
SYNTAX OCTET STRING (SIZE (2)) SYNTAX OCTET STRING (SIZE (2))
MplsLpsCommand ::= TEXTUAL-CONVENTION MplsLpsCommand ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This command allows a user to perform any action over ME. "This command allows a user to perform any action over a
If the protection command cannot be executed because an protection domain. If the protection command cannot be
equal or higher priority request is in effect, an executed because an equal or higher priority request is
inconsistentValue error is returned. in effect, an inconsistentValue error is returned.
The command values are: The command values are:
noCmd noCmd
This value should be returned by a read request when no command This value should be returned by a read request when no
has been written to the object in question since command has been written to the object in question since
initialization. This value may not be used in a write initialization. This value may not be used in a write
operation. If noCmd is used in a write operation a wrongValue operation. If noCmd is used in a write operation a
error is returned. wrongValue error is returned.
clear clear
Clears all of the commands listed below for the specified ME. Clears all of the commands listed below for the protection
domain.
lockoutOfProtection lockoutOfProtection
Prevents switching traffic to the protection path.
Prevents any of the working ME from switching to the protection forcedSwitch
ME. The specified ME should be the protection ME, otherwise an
inconsistentValue error is returned.
forcedSwitchWorkToProtect Switches traffic from the working path to the protection path.
Switches the specified working ME to the protection path. manualSwitchToWork
If the protection ME is specified an inconsistentValue
error is returned.
manualSwitchWorkToProtect Switches traffic from the protection path to the working path.
Switches the specified working ME to the protection ME. manualSwitchToProtect
If the protection ME is specified an inconsistentValue
error is returned."
SYNTAX INTEGER { Switches traffic from the working path to the protection path.
noCmd(1),
clear(2),
lockoutOfProtection(3),
forcedSwitchWorkToProtect(4),
manualSwitchWorkToProtect(5)
}
exercise
mplsLpsConfigGroups OBJECT-TYPE Used to verify the correct operation of the PSC communication
SYNTAX Gauge32 and the integrity of the protection path. This command is not
MAX-ACCESS read-only applicable to the PSC mode.
STATUS current
DESCRIPTION
"The object hold the count of MPLS Protection Switching
groups. This count includes all rows in mplsLpsConfigTable,
regardless of the value of mplsLpsConfigRowStatus."
::= { mplsLpsObjects 1 }
mplsLpsConfigTable OBJECT-TYPE freeze
SYNTAX SEQUENCE OF MplsLpsConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table lists the mpls linear protection groups that
have been configured on the system."
::= { mplsLpsObjects 2 }
mplsLpsConfigEntry OBJECT-TYPE This command freezes the protection state and is a local
SYNTAX MplsLpsConfigEntry command that is not signaled to the remote node.
MAX-ACCESS not-accessible This command is not applicable to the PSC mode.
STATUS current
DESCRIPTION
"A conceptual row in the mplsLpsConfigTable."
INDEX { mplsLpsConfigGroupIndex }
::= { mplsLpsConfigTable 1 }
MplsLpsConfigEntry ::= SEQUENCE { clearfreeze
mplsLpsConfigGroupIndex Unsigned32,
mplsLpsConfigGroupName SnmpAdminString,
mplsLpsConfigMode INTEGER,
mplsLpsConfigRevertive INTEGER,
mplsLpsConfigProtectionScheme INTEGER,
mplsLpsConfigSdThreshold Integer32,
mplsLpsConfigWaitToRestore Integer32,
mplsLpsConfigContinualTxInterval Integer32,
mplsLpsConfigRapidTxInterval Integer32,
mplsLpsConfigCreationTime TimeStamp,
mplsLpsConfigRowStatus RowStatus,
mplsLpsConfigStorageType StorageType
} Clears the local freeze. This command is not applicable to
the PSC mode.
"
mplsLpsConfigGroupIndex OBJECT-TYPE SYNTAX INTEGER {
SYNTAX Unsigned32 noCmd(1),
MAX-ACCESS not-accessible clear(2),
STATUS current lockoutOfProtection(3),
DESCRIPTION forcedSwitch(4),
"Index for the conceptual row identifying a protection group." manualSwitchToWork(5),
::= { mplsLpsConfigEntry 1 } manualSwitchToProtect(6),
exercise(7),
freeze(8),
clearfreeze(9)
}
mplsLpsConfigGroupName OBJECT-TYPE MplsLpsState ::= TEXTUAL-CONVENTION
SYNTAX SnmpAdminString (SIZE (1..32)) STATUS current
MAX-ACCESS read-create DESCRIPTION
STATUS current "This Textual Convention describes an object that stores
DESCRIPTION the current state of the PSC state machine. The values
"Textual name represents the mpls tp protection group. are as follows:
Each Protection Group is identified by a unique
protection group name. "
::= { mplsLpsConfigEntry 2 }
mplsLpsConfigMode OBJECT-TYPE normal
SYNTAX INTEGER {
onePlusOne(1),
oneColonOne(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The architectural mode of the Protection group. This can
either be 1+1, 1:1.
1+1 normal state
In the 1+1 protection scheme, a fully dedicated unavLOlocal
protection entity is allocated. Data traffic is copied
and fed at the source to both the working and the
protection entities. The traffic on the working and the
protection entities is transmitted simultaneously to
the sink of the protection domain, where selection
between the working and protection entities is performed
1:1 Unavailable state due to local LO command.
In the 1:1 scheme, a protection path is allocated to unavSFPlocal
protect against a defect, failure, or a degradation in a
working path. In normal conditions, data traffic is
transmitted over the working entity, while the
protection entity functions in the idle state. If there
is a defect on the working entity or a specific
administrative request, traffic is switched to the
protection entity."
DEFVAL {onePlusOne} Unavailable state due to local SF-P.
::= { mplsLpsConfigEntry 3 }
mplsLpsConfigRevertive OBJECT-TYPE unavSDPlocal
SYNTAX INTEGER { nonrevertive(1), revertive(2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object represents the reversion mode of the Linear
Protection Switching group. The reversion mode of
protection mechanism may be either revertive or
non-revertive.
nonrevertive Unavailable state due to local SD-P.
In non-revertive mode, after a service has been unavLOremote
recovered, traffic will be forwarded on the recovery
path.
revertive Unavailable state due to remote LO message.
In revertive mode, after a service has been unavSFPremote
recovered, traffic will be redirected back onto the
original working path."
DEFVAL { nonrevertive } Unavailable state due to remote SF-P message.
::= { mplsLpsConfigEntry 4 }
mplsLpsConfigProtectionScheme OBJECT-TYPE unavSDPremote
SYNTAX INTEGER { bidirectional(1), unidirectional(2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The object represents the operational scheme of
protection switching group. The protection scheme may
either be unidirectional or bidirectional.
bidirectional Unavailable state due to remote SD-P message.
In bidirectional protection scheme, both the directions protfailSFWlocal
will be switched simultaneously even if the fault
applies to only one direction of the path.
unidirectional Protecting Failure state due to local SF-W.
In unidirectional protection scheme protection switching
will be performed independently for each direction of a
bidirectional transport path
This object may not be modified if the associated protfailSDWlocal
mplsLpsConfigRowStatus object is equal to active(1). "
DEFVAL {bidirectional} Protecting Failure state due to local SD-W.
::= { mplsLpsConfigEntry 5 }
mplsLpsConfigSdThreshold OBJECT-TYPE protfailSFWremote
SYNTAX Integer32 (1..9)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object holds the threshold value of the Signal
Degrade.
When the MPLS DM OAM reaches this threshold value, the Protecting Failure state due to remote SF-W message.
Signal Degrade event will be given to this
protection domain.
This object may be modified if the associated protfailSDWremote
mplsLpsConfigRowStatus object is equal to active(1)."
::= { mplsLpsConfigEntry 6 }
mplsLpsConfigWaitToRestore OBJECT-TYPE Protecting Failure state due to remote SD-W message.
SYNTAX Integer32 (0..720)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current switadmFSlocal
DESCRIPTION Switching Administrative state due to local FS command.
"This object hold the Wait To Restore timer value in Same as Protecting administrative state due to local FS
seconds. command in the PSC mode.
The WTR timer is used to delay reversion of PSC state
to Normal state when recovering from a failure
condition on the working path when the protection
domain is configured for revertive behavior
This object may not be modified if the associated switadmMSWlocal
mplsLpsConfigRowStatus object is equal to active(1)."
DEFVAL { 300 }
::= { mplsLpsConfigEntry 7 }
mplsLpsConfigContinualTxInterval OBJECT-TYPE Switching Administrative state due to local MS-W command
SYNTAX Integer32 (1..20)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Continual Tx Time in Seconds. Represents the time
interval to send the continual LPS packet to the other
end based on the current state."
DEFVAL { 5 }
::= { mplsLpsConfigEntry 8 }
mplsLpsConfigRapidTxInterval OBJECT-TYPE switadmMSPlocal
SYNTAX Integer32 (1000..20000)
UNITS "micro-seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Rapid Tx interval in micro-Seconds. Represents the time
interval to send the LPS packet to the other end, when
there is a change in state of Linear Protection domain due
to local input. The default value is 3.3 milli-seconds
which is 3300 micro-seconds"
DEFVAL { 3300 }
::= { mplsLpsConfigEntry 9 }
mplsLpsConfigCreationTime OBJECT-TYPE Switching Administrative state due to local MS-P command.
SYNTAX TimeStamp Same as Protecting administrative state due to local MS
MAX-ACCESS read-only command in the PSC mode
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the row was
created."
::= { mplsLpsConfigEntry 10 }
mplsLpsConfigRowStatus OBJECT-TYPE switadmFSremote
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This represents the status of the MPLS TP Linear
Protection group Entry. This variable is used to
create, modify, and/or delete a row in this table.
An entry may not exist in the active state unless all
objects in the entry have an appropriate value."
::= { mplsLpsConfigEntry 11 }
mplsLpsConfigStorageType OBJECT-TYPE Switching Administrative state due to remote FS message.
SYNTAX StorageType Same as Protecting administrative state due to remote FS
MAX-ACCESS read-create message in the PSC mode.
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."
DEFVAL { nonVolatile }
::= { mplsLpsConfigEntry 12 }
switadmMSWremote
mplsLpsStatusTable OBJECT-TYPE Switching Administrative state due to remote MS-W message
SYNTAX SEQUENCE OF MplsLpsStatusEntry
MAX-ACCESS not-accessible switadmMSPremote
STATUS current
DESCRIPTION
"This table provides status information about mpls
linear protection groups that have been configured
on the system."
::= { mplsLpsObjects 3 }
mplsLpsStatusEntry OBJECT-TYPE Switching Administrative state due to remote MS-P message.
SYNTAX MplsLpsStatusEntry Same as Protecting administrative state due to remote MS
MAX-ACCESS not-accessible message in the PSC mode.
STATUS current
DESCRIPTION
"A conceptual row in the mplsLpsStatusTable."
AUGMENTS { mplsLpsConfigEntry }
::= { mplsLpsStatusTable 1 }
MplsLpsStatusEntry ::= SEQUENCE { wtr
mplsLpsStatusReqRcv MplsLpsReq,
mplsLpsStatusReqSent MplsLpsReq,
mplsLpsStatusFpathPathRcv MplsLpsFpathPath,
mplsLpsStatusFpathPathSent MplsLpsFpathPath,
mplsLpsStatusModeMismatches Counter32
}
mplsLpsStatusReqRcv OBJECT-TYPE Wait-to-Restore state
SYNTAX MplsLpsReq
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current value of the PSC Request field received on
more recent PSC packet."
::= { mplsLpsStatusEntry 1 }
mplsLpsStatusReqSent OBJECT-TYPE dnr
SYNTAX MplsLpsReq
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current value of the PSC Request field sent on the
more recent PSC packet."
::= { mplsLpsStatusEntry 2 }
mplsLpsStatusFpathPathRcv OBJECT-TYPE Do-not-Revert state
SYNTAX MplsLpsFpathPath
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current value of the FPath and Path fields received
on more recent PSC packet."
::= { mplsLpsStatusEntry 3 }
mplsLpsStatusFpathPathSent OBJECT-TYPE exerLocal
SYNTAX MplsLpsFpathPath
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current value of the FPath and Path fields sent
on more recent PSC packet."
::= { mplsLpsStatusEntry 4 }
mplsLpsStatusModeMismatches OBJECT-TYPE Exercise state due to local EXER command.
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object holds number of occurrences of mismatch in
revertive mode across the protection domain end points."
::= { mplsLpsStatusEntry 5 }
exerRemote
mplsLpsMeConfigTable OBJECT-TYPE Exercise state due to remote EXER message."
SYNTAX SEQUENCE OF MplsLpsMeConfigEntry SYNTAX INTEGER {
MAX-ACCESS not-accessible normal (1),
STATUS current unavLOlocal (2),
DESCRIPTION unavSFPlocal (3),
"This table lists Maintenance Association that have been unavSDPlocal (4),
configured in Protection groups." unavLOremote (5),
::= { mplsLpsObjects 4 } unavSFPremote (6),
unavSDPremote (7),
protfailSFWlocal (8),
protfailSDWlocal (9),
protfailSFWremote (10),
protfailSDWremote (11),
switadmFSlocal (12),
switadmMSWlocal (13),
switadmMSPlocal (14),
switadmFSremote (15),
switadmMSWremote (16),
switadmMSPremote (17),
wtr (18),
dnr (19),
exerLocal (20),
exerRemote (21)
}
mplsLpsMeConfigEntry OBJECT-TYPE -- Start of MPLS Transport Profile Protection Switching
SYNTAX MplsLpsMeConfigEntry -- Table
MAX-ACCESS not-accessible -- MPLS TP Protection Switching Configuration Table
STATUS current -- This table supports the addition, configuration and deletion
DESCRIPTION -- of MPLS-TP linear protection domains.
"A conceptual row in the mplsLpsMeConfigTable."
INDEX {mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex}
::= { mplsLpsMeConfigTable 1 }
MplsLpsMeConfigEntry ::= SEQUENCE { mplsLpsConfigDomains OBJECT-TYPE
mplsLpsMeConfigGroupIndex Unsigned32, SYNTAX Gauge32
mplsLpsMeConfigState INTEGER, MAX-ACCESS read-only
mplsLpsMeConfigCommand MplsLpsCommand, STATUS current
mplsLpsMeConfigHoldOff Integer32 DESCRIPTION
} "The object holds the count of MPLS-TP linear protection
domains. This count includes all rows in mplsLpsConfigTable,
regardless of the value of mplsLpsConfigRowStatus."
::= { mplsLpsObjects 1 }
mplsLpsMeConfigGroupIndex OBJECT-TYPE mplsLpsConfigTable OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX SEQUENCE OF MplsLpsConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the Protection group index wherein "This table lists the MPLS-TP linear protection domains that
this ME included in. If this ME is not part of any protection have been configured on the system."
group then this object contains value 0. " ::= { mplsLpsObjects 2 }
DEFVAL { 0 }
::= { mplsLpsMeConfigEntry 1 }
mplsLpsMeConfigState OBJECT-TYPE mplsLpsConfigEntry OBJECT-TYPE
SYNTAX INTEGER { primary(1), backup(2) } SYNTAX MplsLpsConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in the mplsLpsConfigTable."
INDEX { mplsLpsConfigDomainIndex }
::= { mplsLpsConfigTable 1 }
MAX-ACCESS read-create MplsLpsConfigEntry ::= SEQUENCE {
STATUS current mplsLpsConfigDomainIndex Unsigned32,
DESCRIPTION mplsLpsConfigDomainName SnmpAdminString,
"This object represents the operational state of the ME mplsLpsConfigMode INTEGER,
as either primary or backup" mplsLpsConfigProtectionType INTEGER,
::= { mplsLpsMeConfigEntry 2 } mplsLpsConfigRevertive INTEGER,
mplsLpsConfigSdThreshold Integer32,
mplsLpsConfigSdBadSeconds Integer32,
mplsLpsConfigSdGoodSeconds Integer32,
mplsLpsConfigWaitToRestore Integer32,
mplsLpsConfigHoldOff Integer32,
mplsLpsConfigContinualTxInterval Integer32,
mplsLpsConfigRapidTxInterval Integer32,
mplsLpsConfigCommand MplsLpsCommand,
mplsLpsConfigCreationTime TimeStamp,
mplsLpsConfigRowStatus RowStatus,
mplsLpsConfigStorageType StorageType
}
mplsLpsMeConfigCommand OBJECT-TYPE mplsLpsConfigDomainIndex OBJECT-TYPE
SYNTAX MplsLpsCommand SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index for the conceptual row identifying a protection domain."
::= { mplsLpsConfigEntry 1 }
"Allows the initiation of an MPLS Linear protection command on mplsLpsConfigDomainName OBJECT-TYPE
the protection group and the ME specified by the index values. SYNTAX SnmpAdminString (SIZE (1..32))
When read this object returns the last command written MAX-ACCESS read-create
or noCmd if no command has been written to this ME STATUS current
since initialization. The return of the last command DESCRIPTION
written does not imply that this command is currently in "Textual name represents the MPLS-TP linear protection domain.
effect. This request may have been preempted by a higher Each protection domain is identified by a unique protection
priority local or remote request. domain name. "
::= { mplsLpsConfigEntry 2 }
The value lockoutOfProtection should only be applied to the mplsLpsConfigMode OBJECT-TYPE
protection path / ME since that switch command prevents any SYNTAX INTEGER {
of the working path / ME from switching to the protection path. psc(1),
Following the same logic, forcedSwitchWorkToProtect and aps(2)
manualSwitchWorkToProtect should only be applied to a working }
ME." MAX-ACCESS read-create
::= { mplsLpsMeConfigEntry 3 } STATUS current
DESCRIPTION
"The mode of MPLS-TP linear protection mechanism. This can
either be PSC or APS as follows:
mplsLpsMeConfigHoldOff OBJECT-TYPE PSC
SYNTAX Integer32 (0..10000)
UNITS "milli-seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The hold-off time in milliseconds. Represents the time
between SF/SD condition detection and declaration of The Protection State Coordination mode as described in
an SF/SD request to the protection switching logic. RFC 6378.
It is intended to avoid unnecessary switching when a lower-
layer protection mechanism is in place.
Can be configured in steps of 100"
DEFVAL { 0 }
::= { mplsLpsMeConfigEntry 4 }
APS
mplsLpsMeStatusTable OBJECT-TYPE The Automatic Protection Switching mode as described in
SYNTAX SEQUENCE OF MplsLpsMeStatusEntry RFC 7271."
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains status information of all the ME
that are included in MPLS Protection groups."
::= { mplsLpsObjects 5 }
mplsLpsMeStatusEntry OBJECT-TYPE DEFVAL {psc}
SYNTAX MplsLpsMeStatusEntry ::= { mplsLpsConfigEntry 3 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in the mplsLpsMeStatusTable."
AUGMENTS { mplsLpsMeConfigEntry }
::= { mplsLpsMeStatusTable 1 }
MplsLpsMeStatusEntry ::= SEQUENCE { mplsLpsConfigProtectionType OBJECT-TYPE
mplsLpsMeStatusCurrent BITS, SYNTAX INTEGER {
mplsLpsMeStatusSignalDegrades Counter32, onePlusOneUnidirectional (1),
mplsLpsMeStatusSignalFailures Counter32, oneColonOneBidirectional (2),
mplsLpsMeStatusSwitchovers Counter32, onePlusOneBidirectional (3)
mplsLpsMeStatusLastSwitchover TimeStamp, }
mplsLpsMeStatusSwitchoverSeconds Counter32 MAX-ACCESS read-create
} STATUS current
DESCRIPTION
"The protection architecture type of the Protection domain.
This represents both bridge type, which can be
either permanent bridge (1+1) or selector bridge (1:1),
and switching scheme, which can be
either unidirectional or bidirectional.
mplsLpsMeStatusCurrent OBJECT-TYPE 1+1
SYNTAX BITS {
localLockedOut(0),
localSd(1),
localSf(2),
localSwitched(3),
localWtr(4),
remoteLockedout(5),
remoteSd(6),
remoteSf(7),
remoteSwitched(8),
remoteWtr(9)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the current state of the MA.
localLockedOut In the 1+1 protection scheme, a fully dedicated protection
path is allocated. Data traffic is copied and fed
at the source to both the working and the protection path.
The traffic on the working and the protection paths is
transmitted simultaneously to the sink of the protection
domain, where selection between the working and protection
paths is performed
This bit, when it is set on a working ME or working path 1:1
indicates that the working path is prevented from In the 1:1 scheme, a protection path is allocated to
switching to the protection path because of local request. protect against a defect, failure, or a degradation in the
When it is set on protection / backup path, this bit working path. In normal conditions, data traffic is
indicates that none of the working path can switch transmitted over the working path, while the protection path
to the protection path. functions in the idle state. If there is a defect on the
working path or a specific administrative request,
traffic is switched to the protection path.
localSd bidirectional
This bit implies that local signal degrade condition is In bidirectional protection scheme, both the directions
in effect on this ME / path. will be switched simultaneously even if the fault applies
to only one direction of the path.
localSf unidirectional
This bit implies that local signal failure condition is In unidirectional protection scheme protection switching
in effect on this ME / path. will be performed independently for each direction of a
bidirectional transport path.
localSwitched This object may not be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). "
This bit is only applicable to the working ME / path. DEFVAL {oneColonOneBidirectional}
It implies that the working path is currently switched ::= { mplsLpsConfigEntry 4 }
to the protection path because of local request.
local wtr mplsLpsConfigRevertive OBJECT-TYPE
SYNTAX INTEGER { nonrevertive(1), revertive(2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object represents the reversion mode of the linear
protection domain. The reversion mode of protection
mechanism may be either revertive or non-revertive.
This bit implies that local Wait-to-Restore state is nonrevertive
in effect.
remoteLockedOut In non-revertive mode, after a service has been recovered,
traffic will be forwarded on the protection path.
This bit, when it is set on a working ME or working path revertive
indicates that the working path is prevented from
switching to the protection path because of remote request.
When it is set on protection / backup path, this bit
indicates that none of the working path can switch
to the protection path.
remoteSd In revertive mode, after a service has been recovered,
traffic will be redirected back onto the original working
path."
This bit implies that remote signal degrade condition is DEFVAL { revertive }
in effect on this ME / path. ::= { mplsLpsConfigEntry 5 }
remoteSf mplsLpsConfigSdThreshold OBJECT-TYPE
SYNTAX Integer32 (0..100)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object holds the threshold value of the Signal Degrade
defect in percent.
This bit implies that remote signal failure condition is In order to detect the Signal Degrade (SD) defect,
in effect on this ME / path. the MPLS-TP packet loss measurement (LM) is performed
every second.
remoteSwitched If either the packet loss is negative (i.e., there are more
packets received than transmitted) or the packet loss ratio
(lost packets/transmitted packets) in percent is greater this
threshold value, a Bad Second is declared. The SD defect is
detected if there are mplsLpsConfigSdBadSeconds consecutive
Bad Seconds and cleared if there are
mplsLpsConfigSdGoodSeconds consecutive Good Seconds.
This bit is only applicable to the working ME / path. This object may be modified if the associated
It implies that the working path is currently switched mplsLpsConfigRowStatus object is equal to active(1)."
to the protection path because of remote request.
remoteWtr DEFVAL { 30 }
::= { mplsLpsConfigEntry 6 }
This bit implies that remote Wait-to-Restore state is mplsLpsConfigSdBadSeconds OBJECT-TYPE
in effect." SYNTAX Integer32 (2..10)
::= { mplsLpsMeStatusEntry 1 } MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object holds the number of Bad Seconds to detect the SD.
See the description of mplsLpsConfigSdThreshold.
This object may be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1)."
mplsLpsMeStatusSignalDegrades OBJECT-TYPE DEFVAL { 10 }
SYNTAX Counter32 ::= { mplsLpsConfigEntry 7 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the count of Signal Degrade conditions.
This condition occurs when the DM exceeds the
currently configured value of the relevant instance of
mplsLpsConfigSdThreshold."
::= { mplsLpsMeStatusEntry 2 }
mplsLpsMeStatusSignalFailures OBJECT-TYPE mplsLpsConfigSdGoodSeconds OBJECT-TYPE
SYNTAX Integer32 (2..10)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object holds the number of Good Seconds to declare the
clearance of SD defect.
See the description of mplsLpsConfigSdThreshold.
This object may be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1)."
SYNTAX Counter32 DEFVAL { 10 }
MAX-ACCESS read-only ::= { mplsLpsConfigEntry 8 }
STATUS current
DESCRIPTION
"Represents the count of Signal failure conditions.
This condition occurs when the OAM running on this MA
detects the Signal Fail event."
::= { mplsLpsMeStatusEntry 3 }
mplsLpsMeStatusSwitchovers OBJECT-TYPE mplsLpsConfigWaitToRestore OBJECT-TYPE
SYNTAX Counter32 SYNTAX Integer32 (0..720)
MAX-ACCESS read-only UNITS "seconds"
STATUS current MAX-ACCESS read-create
DESCRIPTION STATUS current
"Represents the count of SwitchOvers happened in this DESCRIPTION
MA. "This object holds the Wait To Restore timer value in seconds.
Can be configured in 1 minute steps between 5 and 12 minutes.
The WTR timer is used to delay reversion of PSC state
to Normal state when recovering from a failure
condition on the working path when the protection
domain is configured for revertive behavior
When the mplsLpsMeConfigState is primary, this This object may not be modified if the associated
object will return the number of times this path mplsLpsConfigRowStatus object is equal to active(1)."
has switched to the protection path.
When the mplsLpsMeConfigState is backup, this object DEFVAL { 300 }
will return the number of times that any working paths ::= { mplsLpsConfigEntry 9 }
has been switched back to the working path from this
protection path."
::= { mplsLpsMeStatusEntry 4 }
mplsLpsMeStatusLastSwitchover OBJECT-TYPE mplsLpsConfigHoldOff OBJECT-TYPE
SYNTAX TimeStamp SYNTAX Integer32 (0..10000)
MAX-ACCESS read-only UNITS "milli-seconds"
STATUS current MAX-ACCESS read-create
DESCRIPTION STATUS current
"This object holds the value of sysUpTime wherein the DESCRIPTION
last switchover happened. "The hold-off time in milliseconds. Represents the time
between SF/SD condition detection and declaration of
an SF/SD request to the protection switching logic.
It is intended to avoid unnecessary switching when a lower-
layer protection mechanism is in place.
Can be configured in steps of 100.
When the mplsLpsMeConfigState is primary, this object When a new defect or more severe defect occurs at
will return the value of sysUpTime when this path last the active path (the path from which the selector selects
completed a switchover. If this path has never switched the user data traffic) and this value is non-zero,
to the protection line, the value 0 will be returned. the hold-off timer will be started. A defect on the standby
path (the path from which the selector does not select the
user data traffic) does not trigger the start of the hold-off
timer as there is no need for a traffic switchover."
When the mplsLpsMeConfigState is backup, this object DEFVAL { 0 }
will return the value of sysUpTime the last time that ::= { mplsLpsConfigEntry 10 }
a working path was switched back to the working path
from this protection path. If no working path has ever
switched back to the working path from this protection
path, the value 0 will be returned."
::= { mplsLpsMeStatusEntry 5 } mplsLpsConfigContinualTxInterval OBJECT-TYPE
SYNTAX Integer32 (1..20)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Continual Tx Time in Seconds. Represents the time
interval to send the continual LPS packet to the other
end based on the current state."
mplsLpsMeStatusSwitchoverSeconds OBJECT-TYPE DEFVAL { 5 }
SYNTAX Counter32 ::= { mplsLpsConfigEntry 11 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The cumulative Protection Switching Duration (PSD) time
in seconds.
ForM a working path, this is the cumulative number of mplsLpsConfigRapidTxInterval OBJECT-TYPE
seconds that traffic was carried on the protection SYNTAX Integer32 (1000..20000)
path. UNITS "micro-seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Rapid Tx interval in micro-Seconds. Represents the time
interval to send the LPS packet to the other end, when
there is a change in state of linear protection domain due
to local input. The default value is 3.3 milli-seconds
which is 3300 micro-seconds"
For the protection path, this is the cumulative number DEFVAL { 3300 }
of seconds that the protection path has been used to ::= { mplsLpsConfigEntry 12 }
carry any working path traffic."
::= { mplsLpsMeStatusEntry 6 } mplsLpsConfigCommand OBJECT-TYPE
SYNTAX MplsLpsCommand
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Allows the initiation of an operator command on
the protection domain.
mplsLpsNotificationEnable OBJECT-TYPE When read this object returns the last command written
SYNTAX BITS { or noCmd if no command has been written
switchover(0), since initialization. The return of the last command
modeMismatch(1) written does not imply that this command is currently in
} effect. This request may have been preempted by a higher
MAX-ACCESS read-write priority local or remote request."
STATUS current ::= { mplsLpsConfigEntry 13 }
DESCRIPTION mplsLpsConfigCreationTime OBJECT-TYPE
"Provides the ability to enable and disable notifications SYNTAX TimeStamp
defined in this MIB. MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the row was created."
::= { mplsLpsConfigEntry 14 }
switchover mplsLpsConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This represents the status of the MPLS-TP linear
protection domain entry. This variable is used to
create, modify, and/or delete a row in this table.
An entry may not exist in the active state unless all
objects in the entry have an appropriate value."
::= { mplsLpsConfigEntry 15 }
Indicates mplsLpsEventSwitchover notifications mplsLpsConfigStorageType OBJECT-TYPE
should be generated. SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."
DEFVAL { nonVolatile }
::= { mplsLpsConfigEntry 16 }
modeMismatch --
-- MPLS TP Linear Protection Switching Status Table
--
-- This table provides Protection Switching domain statistics.
--
Indicates mplsLpsEventModeMismatch notifications mplsLpsStatusTable OBJECT-TYPE
should be generated." SYNTAX SEQUENCE OF MplsLpsStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides status information about MPLS-TP
linear protection domains that have been configured
on the system."
::= { mplsLpsObjects 3 }
DEFVAL { { } } mplsLpsStatusEntry OBJECT-TYPE
::= { mplsLpsObjects 6 } SYNTAX MplsLpsStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in the mplsLpsStatusTable."
AUGMENTS { mplsLpsConfigEntry }
::= { mplsLpsStatusTable 1 }
-- MPLS Linear Protection EVENTS MplsLpsStatusEntry ::= SEQUENCE {
mplsLpsStatusState MplsLpsState,
mplsLpsStatusReqRcv MplsLpsReq,
mplsLpsStatusReqSent MplsLpsReq,
mplsLpsStatusFpathPathRcv MplsLpsFpathPath,
mplsLpsStatusFpathPathSent MplsLpsFpathPath,
mplsLpsStatusRevertiveMismatch INTEGER,
mplsLpsStatusProtecTypeMismatch INTEGER,
mplsLpsStatusCapabilitiesMismatch INTEGER,
mplsLpsStatusPathConfigMismatch INTEGER,
mplsLpsStatusFopNoResponses Counter32,
mplsLpsStatusFopTimeOuts Counter32
}
mplsLpsEventSwitchover NOTIFICATION-TYPE mplsLpsStatusState OBJECT-TYPE
OBJECTS { mplsLpsMeStatusSwitchovers, mplsLpsMeStatusCurrent } SYNTAX MplsLpsState
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"An mplsLpsEventSwitchover notification is sent when the DESCRIPTION
value of an instance of mplsLpsMeStatusSwitchovers increments." "The current state of the PSC state machine."
::= { mplsLpsNotifications 1 } ::= { mplsLpsStatusEntry 1 }
mplsLpsEventModeMismatch NOTIFICATION-TYPE mplsLpsStatusReqRcv OBJECT-TYPE
OBJECTS { mplsLpsStatusModeMismatches } SYNTAX MplsLpsReq
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"An mplsLpsEventModeMismatch notification is sent when the DESCRIPTION
value of an instance of mplsLpsStatusModeMismatches increments." "The current value of the PSC Request field received on
the most recent PSC packet."
::= { mplsLpsStatusEntry 2 }
::= { mplsLpsNotifications 2 } mplsLpsStatusReqSent OBJECT-TYPE
SYNTAX MplsLpsReq
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current value of the PSC Request field sent on the
most recent PSC packet."
::= { mplsLpsStatusEntry 3 }
mplsLpsStatusFpathPathRcv OBJECT-TYPE
SYNTAX MplsLpsFpathPath
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current value of the FPath and Path fields received
on the most recent PSC packet."
::= { mplsLpsStatusEntry 4 }
mplsLpsStatusFpathPathSent OBJECT-TYPE
SYNTAX MplsLpsFpathPath
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current value of the FPath and Path fields sent
on the most recent PSC packet."
::= { mplsLpsStatusEntry 5 }
mplsLpsCompliances mplsLpsStatusRevertiveMismatch OBJECT-TYPE
OBJECT IDENTIFIER ::= { mplsLpsConformance 1 } SYNTAX INTEGER {true (1), false (2)}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the provisioning mismatch in
revertive mode across the protection domain end points.
The value of this object becomes true when a PSC message with
incompatible Revertive field is received, or false
when a PSC message with compatible Revertive field is
received. "
::= { mplsLpsStatusEntry 6 }
mplsLpsGroups mplsLpsStatusProtecTypeMismatch OBJECT-TYPE
OBJECT IDENTIFIER ::= { mplsLpsConformance 2 } SYNTAX INTEGER {true (1), false (2)}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the provisioning mismatch in
protection type, representing both bridge and switching types,
across the protection domain end points.
The value of this object becomes true when a PSC message with
incompatible PT field is received, or false
when a PSC message with compatible PT field is received. "
::= { mplsLpsStatusEntry 7 }
mplsLpsStatusCapabilitiesMismatch OBJECT-TYPE
SYNTAX INTEGER {true (1), false (2)}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the provisioning mismatch in
Capabilities TLVs across the protection domain end points.
The value of this object becomes true when a PSC message with
incompatible Capabilities TLV field is received, or false
when a PSC message with compatible Capabilities TLV field is
received.
mplsLpsModuleFullCompliance MODULE-COMPLIANCE The Capabilities TLV with 0xF8000000 indicates that the APS
mode is used for MPLS-TP linear protection mechanism,
whereas PSC mode uses either the Capabilities TLV with Ox0
or no existence of the Capabilities TLV."
::= { mplsLpsStatusEntry 8 }
STATUS current mplsLpsStatusPathConfigMismatch OBJECT-TYPE
DESCRIPTION "Compliance statement for agents that provide full SYNTAX INTEGER {true (1), false (2)}
support for MPLS-LPS-MIB. Such devices can MAX-ACCESS read-only
provide linear protection and also be configured using STATUS current
this MIB module." DESCRIPTION
"This object indicates the provisioning mismatch in the
protection path configuration for PSC communication across
the protection domain end points.
MODULE -- This module. The value of this object becomes true when a PSC message is
MANDATORY-GROUPS { received from the working path, or false when a PSC message
mplsLpsScalarGroup, is received from the protection path."
mplsLpsConfigTableGroup, ::= { mplsLpsStatusEntry 9 }
mplsLpsMeTableGroup
}
GROUP mplsLpsNotificationGroup mplsLpsStatusFopNoResponses OBJECT-TYPE
DESCRIPTION "This group is only mandatory for those SYNTAX Counter32
implementations which can efficiently implement MAX-ACCESS read-only
the notifications contained in this group." STATUS current
DESCRIPTION
"This object holds the number of occurrences of the failure
of protocol due to a lack of response to a traffic switchover
request within in 50 ms.
::= { mplsLpsCompliances 1 } When there is a traffic switchover due to a local request,
a 50 ms timer is started to detect the failure of protocol
due to no response. If there is no PSC message is received
with the same Path value as in the transmitted PSC message
until the 50 ms timer expires, the failure of protocol due to
no response occurs."
::= { mplsLpsStatusEntry 10 }
-- Units of conformance. mplsLpsStatusFopTimeOuts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object holds the number of occurrences of the failure
of protocol due to no PSC message received during at least
3.5 times the long PSC message interval.
mplsLpsScalarGroup OBJECT-GROUP When no PSC message is received on the protection path during
OBJECTS { at least 3.5 times the long PSC message interval and there
mplsLpsConfigGroups, is no defect on the protection path, the failure of protocol
mplsLpsNotificationEnable due to no PSC message occurs."
} ::= { mplsLpsStatusEntry 11 }
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS Linear Protection."
::= { mplsLpsGroups 1 }
mplsLpsConfigTableGroup OBJECT-GROUP -- MPLS Linear Protection ME Association Configuration Table
OBJECTS { -- This table supports the addition, configuration and deletion
mplsLpsConfigGroupName, -- of MPLS Linear Protection Maintenance Entities in protection
mplsLpsConfigRowStatus, -- domains.
mplsLpsConfigMode,
mplsLpsConfigRevertive,
mplsLpsConfigProtectionScheme,
mplsLpsConfigSdThreshold,
mplsLpsConfigWaitToRestore,
mplsLpsConfigContinualTxInterval,
mplsLpsConfigRapidTxInterval,
mplsLpsConfigCreationTime,
mplsLpsConfigStorageType,
mplsLpsStatusReqRcv,
mplsLpsStatusReqSent,
mplsLpsStatusFpathPathRcv, mplsLpsMeConfigTable OBJECT-TYPE
mplsLpsStatusFpathPathSent, SYNTAX SEQUENCE OF MplsLpsMeConfigEntry
mplsLpsStatusModeMismatches MAX-ACCESS not-accessible
} STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This table lists Maintenance Association that have been
"Collection of objects needed for MPLS Linear Protection configured in Protection domains."
configuration and statistics." ::= { mplsLpsObjects 4 }
::= { mplsLpsGroups 2 }
mplsLpsMeTableGroup OBJECT-GROUP mplsLpsMeConfigEntry OBJECT-TYPE
OBJECTS { SYNTAX MplsLpsMeConfigEntry
mplsLpsMeConfigState, MAX-ACCESS not-accessible
mplsLpsMeConfigCommand, STATUS current
mplsLpsMeConfigHoldOff, DESCRIPTION
mplsLpsMeStatusCurrent, "A conceptual row in the mplsLpsMeConfigTable."
mplsLpsMeStatusSignalDegrades, INDEX {mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex}
mplsLpsMeStatusSignalFailures, ::= { mplsLpsMeConfigTable 1 }
mplsLpsMeStatusSwitchovers,
mplsLpsMeStatusLastSwitchover, MplsLpsMeConfigEntry ::= SEQUENCE {
mplsLpsMeStatusSwitchoverSeconds mplsLpsMeConfigDomainIndex Unsigned32,
mplsLpsMeConfigState INTEGER
} }
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS Linear Protection
ME configuration and statistics."
::= { mplsLpsGroups 3 }
mplsLpsNotificationGroup NOTIFICATION-GROUP mplsLpsMeConfigDomainIndex OBJECT-TYPE
NOTIFICATIONS { SYNTAX Unsigned32
mplsLpsEventSwitchover, MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object holds the Protection domain index wherein
this ME included in. If this ME is not part of any protection
domain then this object contains value 0. "
DEFVAL { 0 }
::= { mplsLpsMeConfigEntry 1 }
mplsLpsEventModeMismatch mplsLpsMeConfigState OBJECT-TYPE
SYNTAX INTEGER { working(1), protection(2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object represents the operational state of the ME
as either working or protection"
::= { mplsLpsMeConfigEntry 2 }
-- MPLS Linear Protection ME Status Table
-- This table provides Protection Switching ME statistics.
mplsLpsMeStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLpsMeStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains status information of all the MEs
that are included in MPLS-TP liear protection domains."
::= { mplsLpsObjects 5 }
mplsLpsMeStatusEntry OBJECT-TYPE
SYNTAX MplsLpsMeStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row in the mplsLpsMeStatusTable."
AUGMENTS { mplsLpsMeConfigEntry }
::= { mplsLpsMeStatusTable 1 }
MplsLpsMeStatusEntry ::= SEQUENCE {
mplsLpsMeStatusCurrent BITS,
mplsLpsMeStatusSignalDegrades Counter32,
mplsLpsMeStatusSignalFailures Counter32,
mplsLpsMeStatusSwitchovers Counter32,
mplsLpsMeStatusLastSwitchover TimeStamp,
mplsLpsMeStatusSwitchoverSeconds Counter32
} }
STATUS current
DESCRIPTION
"Collection of objects needed to implement notifications."
::= { mplsLpsGroups 4 }
END mplsLpsMeStatusCurrent OBJECT-TYPE
SYNTAX BITS {
localSelectTraffic(0),
localSD(1),
localSF(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the current state of the ME.
localSelectTraffic
This bit indicates that traffic is being selected from
this ME.
localSD
This bit implies that local signal degrade condition is
in effect on this ME / path.
localSF
This bit implies that local signal failure condition is
in effect on this ME / path."
::= { mplsLpsMeStatusEntry 1 }
mplsLpsMeStatusSignalDegrades OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the count of Signal Degrade conditions.
For the detection and clearance of Signal Degrade,
see the description of mplsLpsConfigSdThreshold."
::= { mplsLpsMeStatusEntry 2 }
mplsLpsMeStatusSignalFailures OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the count of Signal failure conditions.
This condition occurs when the OAM running on this ME
detects the Signal Fail event."
::= { mplsLpsMeStatusEntry 3 }
mplsLpsMeStatusSwitchovers OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the count of SwitchOvers happened in this ME.
When the mplsLpsMeConfigState is working, this object will
return the number of times that traffic has been switched
from this working path to the protection path.
When the mplsLpsMeConfigState is protection, this object
will return the number of times that traffic has been
switched back to the working path from this protection path."
::= { mplsLpsMeStatusEntry 4 }
mplsLpsMeStatusLastSwitchover OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object holds the value of sysUpTime wherein the
last switchover happened.
When the mplsLpsMeConfigState is working, this object
will return the value of sysUpTime when traffic was switched
from this path to the protection path.
If traffic has never switched to the protection path, the
value 0 will be returned.
When the mplsLpsMeConfigState is protection, this object
will return the value of sysUpTime the last time that
traffic was switched back to the working path from this path.
If no traffic has ever switched back to the working path from
this protection path, the value 0 will be returned."
::= { mplsLpsMeStatusEntry 5 }
mplsLpsMeStatusSwitchoverSeconds OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The cumulative Protection Switching Duration (PSD) time
in seconds.
For the working path, this is the cumulative number of
seconds that traffic was selected from the protection path.
For the protection path, this is the cumulative number
of seconds that the working path has been used to
select traffic."
::= { mplsLpsMeStatusEntry 6 }
mplsLpsNotificationEnable OBJECT-TYPE
SYNTAX BITS {
switchover(0),
revertiveMismatch(1),
protecTypeMismatch(2),
capabilitiesMismatch(3),
pathConfigMismatch(4),
fopNoResponse(5),
fopTimeOut(6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Provides the ability to enable and disable notifications
defined in this MIB.
switchover
Indicates mplsLpsEventSwitchover notifications should be
generated.
revertiveMismatch
Indicates mplsLpsEventRevertiveMismatch notifications
should be generated.
protecTypeMismatch
Indicates mplsLpsEventProtecTypeMismatch notifications
should be generated.
capabilitiesMismatch
Indicates mplsLpsEventCapabilitiesMismatch notifications
should be generated.
pathConfigMismatch
Indicates mplsLpsEventPathConfigMismatch notifications
should be generated.
fopNoResponse
Indicates mplsLpsEventFopNoResponse notifications
should be generated.
fopTimeOut
Indicates mplsLpsEventFopTimOut notifications
should be generated."
DEFVAL { { } }
::= { mplsLpsObjects 6 }
-- MPLS Linear Protection EVENTS
mplsLpsEventSwitchover NOTIFICATION-TYPE
OBJECTS { mplsLpsMeStatusSwitchovers, mplsLpsMeStatusCurrent }
STATUS current
DESCRIPTION
"An mplsLpsEventSwitchover notification is sent when the
value of an instance of mplsLpsMeStatusSwitchovers
increments."
::= { mplsLpsNotifications 1 }
mplsLpsEventRevertiveMismatch NOTIFICATION-TYPE
OBJECTS { mplsLpsStatusRevertiveMismatch }
STATUS current
DESCRIPTION
"An mplsLpsEventRevertiveMismatch notification is sent when
the value of mplsLpsStatusRevertiveMismatch changes."
::= { mplsLpsNotifications 2 }
mplsLpsEventProtecTypeMismatch NOTIFICATION-TYPE
OBJECTS { mplsLpsStatusProtecTypeMismatch }
STATUS current
DESCRIPTION
"An mplsLpsEventProtecTypeMismatch notification is sent
when the value of mplsLpsStatusProtecTypeMismatch changes."
::= { mplsLpsNotifications 3 }
mplsLpsEventCapabilitiesMismatch NOTIFICATION-TYPE
OBJECTS { mplsLpsStatusCapabilitiesMismatch }
STATUS current
DESCRIPTION
"An mplsLpsEventCapabilitiesMismatch notification is sent
when the value of mplsLpsStatusCapabilitiesMismatch changes."
::= { mplsLpsNotifications 4 }
mplsLpsEventPathConfigMismatch NOTIFICATION-TYPE
OBJECTS { mplsLpsStatusPathConfigMismatch }
STATUS current
DESCRIPTION
"An mplsLpsEventPathConfigMismatch notification is sent
when the value of mplsLpsStatusPathConfigMismatch changes."
::= { mplsLpsNotifications 5 }
mplsLpsEventFopNoResponse NOTIFICATION-TYPE
OBJECTS { mplsLpsStatusFopNoResponses }
STATUS current
DESCRIPTION
"An mplsLpsEventFopNoResponse notification is sent when the
value of mplsLpsStatusFopNoResponses increments."
::= { mplsLpsNotifications 6 }
mplsLpsEventFopTimOut NOTIFICATION-TYPE
OBJECTS { mplsLpsStatusFopTimeOuts }
STATUS current
DESCRIPTION
"An mplsLpsEventFopTimOut notification is sent when the
value of mplsLpsStatusFopTimeOuts increments."
::= { mplsLpsNotifications 7 }
-- End of Notifications.
-- Module Compliance.
mplsLpsCompliances
OBJECT IDENTIFIER ::= { mplsLpsConformance 1 }
mplsLpsGroups
OBJECT IDENTIFIER ::= { mplsLpsConformance 2 }
-- Compliance requirement for fully compliant implementations.
mplsLpsModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support for MPLS-LPS-MIB. Such devices can
provide linear protection and also be configured using
this MIB module."
MODULE -- This module.
MANDATORY-GROUPS {
mplsLpsScalarGroup,
mplsLpsTableGroup,
mplsLpsMeTableGroup
}
GROUP mplsLpsNotificationGroup
DESCRIPTION
"This group is only mandatory for those
implementations which can efficiently implement
the notifications contained in this group."
::= { mplsLpsCompliances 1 }
-- Units of conformance.
mplsLpsScalarGroup OBJECT-GROUP
OBJECTS {
mplsLpsConfigDomains,
mplsLpsNotificationEnable
}
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS Linear Protection."
::= { mplsLpsGroups 1 }
mplsLpsTableGroup OBJECT-GROUP
OBJECTS {
mplsLpsConfigDomainName,
mplsLpsConfigRowStatus,
mplsLpsConfigMode,
mplsLpsConfigProtectionType,
mplsLpsConfigRevertive,
mplsLpsConfigSdThreshold,
mplsLpsConfigSdBadSeconds,
mplsLpsConfigSdGoodSeconds,
mplsLpsConfigWaitToRestore,
mplsLpsConfigHoldOff,
mplsLpsConfigContinualTxInterval,
mplsLpsConfigRapidTxInterval,
mplsLpsConfigCommand,
mplsLpsConfigCreationTime,
mplsLpsConfigStorageType,
mplsLpsStatusState,
mplsLpsStatusReqRcv,
mplsLpsStatusReqSent,
mplsLpsStatusFpathPathRcv,
mplsLpsStatusFpathPathSent,
mplsLpsStatusRevertiveMismatch,
mplsLpsStatusProtecTypeMismatch,
mplsLpsStatusCapabilitiesMismatch,
mplsLpsStatusPathConfigMismatch,
mplsLpsStatusFopNoResponses,
mplsLpsStatusFopTimeOuts
}
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS Linear Protection
configuration and statistics."
::= { mplsLpsGroups 2 }
mplsLpsMeTableGroup OBJECT-GROUP
OBJECTS {
mplsLpsMeConfigState,
mplsLpsMeStatusCurrent,
mplsLpsMeStatusSignalDegrades,
mplsLpsMeStatusSignalFailures,
mplsLpsMeStatusSwitchovers,
mplsLpsMeStatusLastSwitchover,
mplsLpsMeStatusSwitchoverSeconds
}
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS Linear Protection
ME configuration and statistics."
::= { mplsLpsGroups 3 }
mplsLpsNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
mplsLpsEventSwitchover,
mplsLpsEventRevertiveMismatch,
mplsLpsEventProtecTypeMismatch,
mplsLpsEventCapabilitiesMismatch,
mplsLpsEventPathConfigMismatch,
mplsLpsEventFopNoResponse,
mplsLpsEventFopTimOut
}
STATUS current
DESCRIPTION
"Collection of objects needed to implement notifications."
::= { mplsLpsGroups 4 }
-- MPLS-LPS-MIB module ends
END
9. Security Considerations 9. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some networks in objects may be considered sensitive or vulnerable in some networks in
a non-secure environment without proper protection can have a a non-secure environment without proper protection can have a
negative effect on network operations. These are the tables and negative effect on network operations. These are the tables and
objects and their sensitivity/vulnerability: objects and their sensitivity/vulnerability:
o mplsLpsConfigTable is used to configure MPLS-TP linear protection
domains. Improper manipulation of the objects in this table may
result in different behaviors than network operators have
originally intended, such as delaying traffic switching or causing
a race condition with server layer protection after network
failure (mplsLpsConfigHoldOff), delaying or speeding up reversion
after recovering network failure (mplsLpsConfigWaitToRestore),
unexpected traffic switching (mplsLpsConfigCommand), or
discontinuance of operation of a protection switching control
process (mplsLpsConfigMode, mplsLpsConfigProtectionType).
o mplsLpsMeConfigTable is used to assign each ME either working or
protection path. Improper manipulation of this object may result
in discontinuance of operation of a protection switching control
process.
o In the case of the discontinuance of a protection switching
control process, network operators will be notified. However, the
notification is controlled by mplsLpsNotificationEnable object,
which is read-write.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
- mplsLpsConfigTable, mplsLpsStatusTable, mplsLpsMeConfigTable and o mplsLpsStatusTable and mplsLpsMeStatusTable collectively show the
mplsLpsMeStatusTable collectively show the MPLS Linear Protection history and current status of the MPLS-TP linear protection
characteristics. If an Administrator does not want to reveal this domains. They can be used to estimate the performances and
information, then these tables should be considered qualities of the network being operated with the MPLS-TP linear
sensitive/vulnerable. protection. If an Administrator does not want to reveal this
information, then these tables should be considered sensitive/
vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security.
if the network itself is secure (for example by using IPsec), there Even if the network itself is secure (for example by using IPsec),
is no control as to who on the secure network is allowed to access there is no control as to who on the secure network is allowed to
and GET/SET (read/change/create/delete) the objects in this MIB access and GET/SET (read/change/create/delete) the objects in this
module. MIB module.
Implementations SHOULD provide the security features described by Implementations SHOULD provide the security features described by the
the SNMPv3 framework (see [RFC3410]), and implementations claiming SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM) authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations RFC 3414 [RFC3414] with the AES cipher algorithm RFC 3826 [RFC3826].
MAY also provide support for the Transport Security Model (TSM) Implementations MAY also provide support for the Transport Security
[RFC5591] in combination with a secure transport such as SSH Model (TSM) RFC 5591 [RFC5591] in combination with a secure transport
[RFC5592] or TLS/DTLS [RFC6353]. such as SSH RFC 5592 [RFC5592] or TLS/DTLS RFC 6353 [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is not Further, deployment of SNMP versions prior to SNMPv3 is not
recommended. Instead, it is RECOMMENDED to deploy SNMPv3 and to recommended. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
10. IANA Considerations 10. IANA Considerations
IANA is requested to assign an OID for the MIB module from the "MIB IANA is requested to assign an OID for the MIB module from the "MIB
Transmission Group - MPLS STD" sub-registry of the "Internet-standard Transmission Group - MPLS STD" sub-registry of the "Internet-standard
MIB - Transmission Group" registry for the MPLS Linear Protection MIB MIB - Transmission Group" registry for the MPLS Linear Protection MIB
module specified in this document. module specified in this document.
11. References 11. Acknowledgments
11.1. Normative References The authors wish to thank Joan Cucchiara for her review as MIB
Doctor, Joan's detailed comments were of great help for improving the
quality of this document.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 12. References
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 12.1. Normative References
Schoenwaelder, Ed., "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Requirement Levels", BCP 14, RFC 2119,
STD 58, RFC 2579, April 1999. DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Conformance Statements for SMIv2", STD 58, RFC 2580, Schoenwaelder, Ed., "Structure of Management Information
April 1999. Version 2 (SMIv2)", STD 58, RFC 2578,
DOI 10.17487/RFC2578, April 1999,
<http://www.rfc-editor.org/info/rfc2578>.
11.2. Informative References [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
<http://www.rfc-editor.org/info/rfc2579>.
[RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction and [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Applicability Statement for Internet Standard Management Schoenwaelder, Ed., "Conformance Statements for SMIv2",
Framework", RFC 3410, December 2002. STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,
<http://www.rfc-editor.org/info/rfc2580>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security 12.2. Informative References
Model(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Textual Conventions (TCs) for Multiprotocol Label Switching "Introduction and Applicability Statements for Internet-
(MPLS) Management", RFC 3811, June 2004. Standard Management Framework", RFC 3410,
DOI 10.17487/RFC3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
"Multiprotocol Label Switching (MPLS) Traffic Engineering (USM) for version 3 of the Simple Network Management
(TE) Management Information Base (MIB)", RFC 3812, June Protocol (SNMPv3)", STD 62, RFC 3414,
2004. DOI 10.17487/RFC3414, December 2002,
<http://www.rfc-editor.org/info/rfc3414>.
[RFC3826] Blumenthal, U., F. Maino and K. McCloghrie, "The Advanced [RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of
Encryption Standard (AES) Cipher Algorithm in the SNMP Textual Conventions (TCs) for Multiprotocol Label
User-based Security Model", RFC 3826, June 2004. Switching (MPLS) Management", RFC 3811,
DOI 10.17487/RFC3811, June 2004,
<http://www.rfc-editor.org/info/rfc3811>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
for the Simple Network Management Protocol(SNMP)",RFC 5591, "Multiprotocol Label Switching (MPLS) Traffic Engineering
June 2009. (TE) Management Information Base (MIB)", RFC 3812,
DOI 10.17487/RFC3812, June 2004,
<http://www.rfc-editor.org/info/rfc3812>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Transport Model for the Simple Network Management Protocol Advanced Encryption Standard (AES) Cipher Algorithm in the
(SNMP)", RFC 5592, June 2009. SNMP User-based Security Model", RFC 3826,
DOI 10.17487/RFC3826, June 2004,
<http://www.rfc-editor.org/info/rfc3826>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
Model for the Simple Network Management Protocol (SNMP)", for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, July 2011. STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
<http://www.rfc-editor.org/info/rfc5591>.
[RFC6378] Weingarten, Y., Osborne, E., Sprecher, N., Fulignoli, [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
A., Ed., and Y. Weingarten, Ed., "MPLS-TP Linear Shell Transport Model for the Simple Network Management
Protection", October 2011. Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June
2009, <http://www.rfc-editor.org/info/rfc5592>.
[MPLS-OAM-ID-STD-MIB] Sam Aldrin, M.Venkatesan, Kannan KV Sampath, [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Thomas D. Nadeau, Sami Boutros, Ping Pan, Model for the Simple Network Management Protocol (SNMP)",
"MPLS-TP Operations, Administration, and STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011,
Management (OAM) Identifiers Management <http://www.rfc-editor.org/info/rfc6353>.
Information Base (MIB)", ID
draft-ietf-mpls-tp-oam-id-mib-08, February 2015.
12. Acknowledgments [RFC6378] Weingarten, Y., Ed., Bryant, S., Osborne, E., Sprecher,
N., and A. Fulignoli, Ed., "MPLS Transport Profile (MPLS-
TP) Linear Protection", RFC 6378, DOI 10.17487/RFC6378,
October 2011, <http://www.rfc-editor.org/info/rfc6378>.
The authors wish to thank Joan Cucchiara for her review as MIB [RFC7271] Ryoo, J., Ed., Gray, E., Ed., van Helvoort, H.,
Doctor, Joan's detailed comments were of great help for improving the D'Alessandro, A., Cheung, T., and E. Osborne, "MPLS
quality of this document. Transport Profile (MPLS-TP) Linear Protection to Match the
Operational Expectations of Synchronous Digital Hierarchy,
Optical Transport Network, and Ethernet Transport Network
Operators", RFC 7271, DOI 10.17487/RFC7271, June 2014,
<http://www.rfc-editor.org/info/rfc7271>.
13. Author's Address [I-D.ietf-mpls-tp-oam-id-mib]
Aldrin, S., Mahalingam, V., Sampath, K., and T. Nadeau,
"MPLS-TP Operations, Administration, and Management (OAM)
Identifiers Management Information Base (MIB)", draft-
ietf-mpls-tp-oam-id-mib-11 (work in progress), September
2015.
Kingston Smiler Authors' Addresses
IP Infusion
RMZ Centennial
Mahadevapura Post
Bangalore - 560048 India
EMail: kingstonsmiler@gmail.com
Venkatesan Mahalingam Kingston Smiler Selvaraj
Dell Inc. IpInfusion
5450 Great America Parkway, RMZ Centennial
Santa Clara, CA 95054, USA Mahadevapura Post
Email: venkat.mahalingams@gmail.com Bangalore - 560048
India
Vishwas Manral EMail: kingstonsmiler@gmail.com
Ionos Corp,
4100 Moorpark Ave,
San Jose, CA
Email: vishwas@ionosnetworks.com
Daniel King Mahalingam Venkatesan
Old Dog Consulting Dell Inc.
UK 5450 Great America Parkway
Email:daniel@olddog.co.uk Santa Clara, CA 95054
USA
Sam Aldrin EMail: venkat.mahalingams@gmail.com
Google, Inc.
1600 Amphitheatre Parkway Vishwas Manral
Mountain View, CA Ionos Corp
USA 4100 Moorpark Ave
Email: aldrin.ietf@gmail.com" San Jose, CA
USA
EMail: vishwas@ionosnetworks.com
Daniel King
Old Dog Consulting
UK
EMail: daniel@olddog.co.uk
Sam Aldrin
Google, Inc.
1600 Amphitheatre Parkway
Mountain View, CA
USA
EMail: aldrin.ietf@gmail.com
Jeong-dong Ryoo
ETRI
218 Gajeong-ro
Yuseong-gu, Daejeon 34129
South Korea
EMail: ryoo@etri.re.kr
 End of changes. 236 change blocks. 
1001 lines changed or deleted 1424 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/