draft-ietf-mpls-tp-linear-protection-mib-08.txt   draft-ietf-mpls-tp-linear-protection-mib-09.txt 
MPLS Working Group Kingston Smiler Selvaraj MPLS Working Group Kingston Smiler Selvaraj
Internet-Draft IpInfusion Internet-Draft IpInfusion
Intended status: Standards Track Venkatesan Mahalingam Intended status: Standards Track Venkatesan Mahalingam
Expires: November 20, 2016 Dell Inc. Expires: February 9, 2017 Dell Inc.
V. Manral V. Manral
Nano Sec Nano Sec
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
Sam Aldrin Sam Aldrin
Google, Inc. Google, Inc.
J. Ryoo J. Ryoo
ETRI ETRI
May 19, 2016 August 8, 2016
MPLS Transport Profile Linear Protection MIB MPLS Transport Profile Linear Protection MIB
draft-ietf-mpls-tp-linear-protection-mib-08 draft-ietf-mpls-tp-linear-protection-mib-09
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 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). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. 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."
This Internet-Draft will expire on November 20, 2016. This Internet-Draft will expire on February 9, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 2, line 30 skipping to change at page 2, line 30
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 . . . . . . . . . . . . . . . . . . 5 5.4. The Table Structures . . . . . . . . . . . . . . . . . . 5
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . . . . . . . . 6 Module . . . . . . . . . . . . . . . . . . . . . . . . . 6
7. Example of Protection Switching Configuration . . . . . . . . 6 7. Example of Protection Switching Configuration . . . . . . . . 6
8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 38 9. Security Considerations . . . . . . . . . . . . . . . . . . . 40
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 39 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 41
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 41
12.1. Normative References . . . . . . . . . . . . . . . . . . 39 12.1. Normative References . . . . . . . . . . . . . . . . . . 41
12.2. Informative References . . . . . . . . . . . . . . . . . 40 12.2. Informative References . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43
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 Label Switched Paths (LSPs).
At the time of writing, SNMP SET is no longer recommended as a way to
configure MPLS networks as was described in RFC 3812 [RFC3812].
However, since the MIB module specified in this document are intended
to work in parallel with the MIB module for MPLS specified in
[RFC3812], certain objects defined here are specified with MAX-ACCESS At the time of writing, Simple Network Management Protocol (SNMP) SET
of read- write or read-create so that specifications of the base is no longer recommended as a way to configure MPLS networks as was
tables in [RFC3812] and the new MIB module in this document is described in RFC 3812 [RFC3812]. However, since the MIB module
consistent. Although the examples described in Section 7 specify specified in this document is intended to work in parallel with the
means to configure OAM identifiers for MPLS-TP tunnels, this should MIB module for MPLS specified in [RFC3812], certain objects defined
be seen as indicating how the MIB values would be returned in the here are specified with MAX-ACCESS of read- write or read-create so
specified circumstances having been configured by alternative means. that specifications of the base tables in [RFC3812] and the new MIB
module in this document is consistent. Although the example
described in Section 7 specify means to configure OAM identifiers for
MPLS-TP tunnels, this should be seen as indicating how the MIB values
would be returned in the 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 MIB. MIB objects are generally accessed through the 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 BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. [RFC2119].
4. Overview 4. Overview
RFC 6378 [RFC6378] defines the protocol to provide a linear RFC 6378 [RFC6378] defines the protocol to provide a linear
protection switching mechanism for MPLS transport profile with protection switching mechanism for MPLS-TP with protection domain as
protection domain as a point-to-point LSP. RFC 7271 [RFC7271] a point-to-point LSP. RFC 7271 [RFC7271] describes alternate
describes alternate mechanisms to perform some of the functions mechanisms to perform some of the functions defined in [RFC6378], and
defined in [RFC6378], and also defines additional mechanisms, in also defines additional mechanisms, in order to provide operator
order to provide operator control and experience that more closely control and experience that more closely models the behavior of
models the behavior of linear protection seen in other transport linear protection seen in other transport networks. Two modes are
networks. Two modes are defined for MPLS-TP linear protection defined for MPLS-TP linear protection switching: Protection State
switching: Protection State Coordination (PSC) mode and Automatic Coordination (PSC) mode and Automatic Protection Switching (APS) mode
Protection Switching (APS) mode as specified in [RFC6378] and as specified in [RFC6378] and [RFC7271], respectively. The detailed
[RFC7271], respectively. The detailed protocol specification of MPLS protocol specification of MPLS transport profile linear protection is
transport profile linear protection is described in [RFC6378] and described in [RFC6378] and [RFC7271].
[RFC7271].
This document specifies a MIB module for the Label Edge Router (LER) This document specifies a MIB module for the Label Edge Router (LER)
that supports MPLS-TP Linear protection as described in [RFC6378] and that supports MPLS-TP linear protection as described in [RFC6378] and
[RFC7271]. Objects defined in the document are generally applied to [RFC7271]. Objects defined in the document are generally applied to
both PSC and APS modes. If an object is valid for a particular mode both PSC and APS modes. If an object is valid for a particular mode
only, it is noted in the description for the object. 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 this document: The following new textual conventions are defined in this document:
skipping to change at page 5, line 9 skipping to change at page 5, line 9
Capabilities TLVs across the end point of the protection domain. Capabilities TLVs across the end point of the protection domain.
o The notification, mplsLpsEventPathConfigMismatch is to inform the o The notification, mplsLpsEventPathConfigMismatch is to inform the
management station about the provisioning mismatch in the management station about the provisioning mismatch in the
protection path configuration for PSC communication. protection path configuration for PSC communication.
o The notification, mplsLpsEventFopNoResponse is to inform the o The notification, mplsLpsEventFopNoResponse is to inform the
management station about the failure of protocol due to a lack of management station about the failure of protocol due to a lack of
response to a traffic switchover request in 50 ms. response to a traffic switchover request in 50 ms.
o The notification, mplsLpsEventFopTimout is to inform the o The notification, mplsLpsEventFopTimeout is to inform the
management station about the failure of protocol due to no management station about the failure of protocol due to no
protocol message received during at least 3.5 times the long PSC protocol message received during at least 3.5 times the long PSC
message interval. 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 domain. This table is used to configure MPLS-TP linear protection domains.
The protection domain is identified by mplsLpsConfigDomainName. An MPLS-TP linear protection domain (or a protection domain) is
The other objects in this table can be used to configure identified by mplsLpsConfigDomainIndex. A protection domain
properties that are specific to the protection domain. consists of two LERs and the working and protection paths that
connect the two LERs. The objects in this table are used to
configure properties that are specific to the protection domain.
Two Maintenance Entities (MEs) MUST be defined for each protection
domain: one for the working path and the other for the protection
path. Therefore, two entries of the mplsLpsMeConfigTable, which
is for configuring the MEs used in protection switching, are
associated to one entry in this table.
o mplsLpsStatusTable o mplsLpsStatusTable
This table provides the current status information of MPLS-TP This table provides the current status information of MPLS-TP
linear protection domains that have been configured on the system. linear protection domains that have been configured on the system.
The entries of mplsLpsStatusTable have an AUGMENTS relationship The entries of mplsLpsStatusTable have an AUGMENTS relationship
with the entries of mplsLpsConfigTable. When a protection domain with the entries of mplsLpsConfigTable. When a protection domain
is configured or deleted in the mplsLpsConfigTable, then the is configured or deleted in the mplsLpsConfigTable, then the
corresponding row of that session in the mplsLpsStatusTable is, corresponding row of that session in the mplsLpsStatusTable is,
respectively, automatically created or deleted. respectively, automatically created or deleted.
o mplsLpsMeConfigTable o mplsLpsMeConfigTable
This table is used to associate the Maintenance Entities (MEs) to This table is used to associate MEs to the protection domain.
the protection domain. The ME is identified by mplsOamIdMegIndex, Each protection domain requires two MEs. One entry in the
mplsOamIdMeIndex and mplsOamIdMeMpIndex. mplsLpsConfigTable is associated with two entries in this table:
one for the working path and the other for the protection path of
the protection domain. The mplsLpsMeConfigPath object in this
table indicates that the path is either working or protection.
The ME is identified by mplsOamIdMegIndex, mplsOamIdMeIndex and
mplsOamIdMeMpIndex, which are the same index values as the entry
in the mplsOamIdMeTable defined in RFC 7697 [RFC7697]. The
relationship with the mplsOamIdMeTable is described in
Section 6.1.
o mplsLpsMeStatusTable o mplsLpsMeStatusTable
This table provides the current information about the protection This table provides the current information about protection
state of MEs that have been configured on the system. When a ME status of MEs that have been configured on the system. When an 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 is, corresponding row of that session in the mplsLpsMeStatusTable 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 the entry in the
mplsOamIdMeTable defined in [RFC7697]. Note that the nature of the mplsOamIdMeTable defined in [RFC7697]. Note that the nature of the
'extends' relationship is a sparse augmentation so that the entry in 'extends' relationship is a sparse augmentation so that the entry in
the mplsLpsMeConfigTable has the same index values as the entry in the mplsLpsMeConfigTable has the same index values as the entry in
the mplsOamIdMeTable. Each time that an entry is created in the the mplsOamIdMeTable. Each time that an entry is created in the
mplsOamIdMeTable for which the LER supports MPLS-TP linear protection mplsOamIdMeTable for which the LER supports MPLS-TP linear
a row is created automatically in the mplsLpsMeConfigTable. protection, a row is created automatically in the
mplsLpsMeConfigTable.
7. Example of Protection Switching Configuration An entry of this table is related to a single entry in
mplsOamIdMeTable. When a point-to-point transport path needs to be
monitored, one ME is needed for the path and one entry in the
mplsOamIdMeTable will be created. But, the ME entry in the
mplsOamIdMeTable may or may not participate in protection switching.
If an ME participates in protection switching, an entry in
mplsLpsMeConfigTable MUST be created, and the objects in the entry
indicates which protection domain this ME belongs to and whether this
ME is for either working path or protection path. If the ME does not
participate in protection switching, an entry in
mplsLpsMeConfigTable does not need to be created.
This example considers the protection domain configuration on a head- 7. Example of Protection Switching Configuration
end LSR to provide protection for a co-routed bidirectional MPLS
tunnel.
Only relevant objects which are applicable for protection domain This example considers the protection domain configuration on an LER
identifiers of co-routed MPLS tunnel are illustrated here. to provide protection for a co-routed bidirectional MPLS tunnel. For
the working and protection paths of the protection domain, two
Maintenance Entity Groups (MEGs) need to be configured and each MEG
contains one ME for a point-to-point transport path. For more
information on mplsOamIdMegTable and mplsOamIdMeTable, see [RFC7697].
In mplsOamIdMegTable: In mplsOamIdMegTable:
{ {
-- MEG index (Index to the table) -- MEG index (Index to the table)
mplsOamIdMegIndex = 1, mplsOamIdMegIndex = 1,
-- MEG name
mplsOamIdMegName = "MEG1", mplsOamIdMegName = "MEG1",
mplsOamIdMegOperatorType = ipCompatible (1), -- Mandatory parameters needed to activate the row go here
mplsOamIdMegServiceType = lsp (1), mplsOamIdMegRowStatus = createAndGo (4)
mplsOamIdMegMpLocation = perNode(1), }
-- Mandatory parameters needed to activate the row go here {
-- MEG index (Index to the table)
mplsOamIdMegIndex = 2,
-- MEG name
mplsOamIdMegName = "MEG2",
-- Mandatory parameters needed to activate the row go here
mplsOamIdMegRowStatus = createAndGo (4) mplsOamIdMegRowStatus = createAndGo (4)
} }
This will create an entry in the mplsOamIdMegTable to protect the This will create two MEG entres in the mplsOamIdMegTable.
MPLS tunnel.
The following ME table is used to associate the path information to a The following ME table is used to associate the ME information to
MEG. each MEG.
In mplsOamIdMeTable: In mplsOamIdMeTable:
{ {
-- MEG index (Index to the table)
mplsOamIdMegIndex = 1,
-- ME index (Index to the table) -- ME index (Index to the table)
mplsOamIdMeIndex = 1, mplsOamIdMeIndex = 1,
-- MP index (Index to the table) -- MP index (Index to the table)
mplsOamIdMeMpIndex = 1, mplsOamIdMeMpIndex = 1,
-- ME name
mplsOamIdMeName = "ME1", 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), mplsOamIdMeMpType = mep (1),
mplsOamIdMeMepDirection = down (2), -- Mandatory parameters needed to activate the row go here
mplsOamIdMeProactiveOamPhbTCValue = 0, mplsOamIdMeRowStatus = createAndGo (4)
mplsOamIdMeOnDemandOamPhbTCValue = 0, }
-- RowPointer MUST point to the first accessible column {
-- of an MPLS tunnel -- MEG index (Index to the table)
mplsOamIdMeServicePointer = mplsTunnelName.1.1.1.2, mplsOamIdMegIndex = 2,
-- ME index (Index to the table)
mplsOamIdMeIndex = 2,
-- MP index (Index to the table)
mplsOamIdMeMpIndex = 2,
-- ME name
mplsOamIdMeName = "ME2",
mplsOamIdMeMpType = mep (1),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsOamIdMeRowStatus = createAndGo (4) mplsOamIdMeRowStatus = createAndGo (4)
} }
The below table associates the MEs with protection domains. The following table configures a protection domain.
In mplsLpsConfigTable: In mplsLpsConfigTable:
mplsLpsConfigEntry ::= SEQUENCE { mplsLpsConfigEntry ::= SEQUENCE
-- Group index {
mplsLpsConfigDomainIndex = 1, -- Protection Domain index (Index to the table)
mplsLpsConfigDomainName = "LPDomain1", mplsLpsConfigDomainIndex = 3,
-- Protection Domain name
mplsLpsConfigDomainName = "LPDomain3",
mplsLpsConfigMode = psc (1), mplsLpsConfigMode = psc (1),
mplsLpsConfigProtectionType = oneColonOneBidirectional (2), mplsLpsConfigProtectionType = oneColonOneBidirectional (2),
-- Mandatory parameters needed to activate the row go here -- Mandatory parameters needed to activate the row go here
mplsLpsConfigRowStatus = createAndGo (4) mplsLpsConfigRowStatus = createAndGo (4)
} }
The following table associates the MEs with the protection domain.
In mplsLpsMeConfigTable: In mplsLpsMeConfigTable:
MplsLpsMeConfigEntry ::= SEQUENCE { MplsLpsMeConfigEntry ::= SEQUENCE
{
-- MEG index (Index to the table) -- MEG index (Index to the table)
mplsOamIdMegIndex = 1, mplsOamIdMegIndex = 1,
-- ME index (Index to the table) -- ME index (Index to the table)
mplsOamIdMeIndex = 1, mplsOamIdMeIndex = 1,
-- MP index (Index to the table) -- MP index (Index to the table)
mplsOamIdMeMpIndex = 1, mplsOamIdMeMpIndex = 1,
-- Domain index -- Protection Domain this ME belongs to
mplsLpsMeConfigDomainIndexValue = 1, mplsLpsMeConfigDomain = 3,
-- Configuration state -- Configuration state
mplsLpsMeConfigState = working(1) mplsLpsMeConfigPath = working(1)
} }
{
-- MEG index (Index to the table)
mplsOamIdMegIndex = 2,
-- ME index (Index to the table)
mplsOamIdMeIndex = 2,
-- MP index (Index to the table)
mplsOamIdMeMpIndex = 2,
-- Protection Domain this ME belongs to
mplsLpsMeConfigDomain = 3,
-- Configuration state
mplsLpsMeConfigPath = protection(2)
}
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,
Counter32, Unsigned32 Counter32, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
skipping to change at page 9, line 9 skipping to change at page 10, line 12
IndexIntegerNextFree IndexIntegerNextFree
FROM DIFFSERV-MIB -- RFC 3289 FROM DIFFSERV-MIB -- RFC 3289
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC 3811 FROM MPLS-TC-STD-MIB -- RFC 3811
mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex
FROM MPLS-OAM-ID-STD-MIB; -- RFC 7697 FROM MPLS-OAM-ID-STD-MIB; -- RFC 7697
mplsLpsMIB MODULE-IDENTITY mplsLpsMIB MODULE-IDENTITY
LAST-UPDATED "201605190000Z" -- May 19, 2016 LAST-UPDATED "201608080000Z" -- August 8, 2016
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" "
Kingston Smiler Selvaraj Kingston Smiler Selvaraj
IP Infusion IP Infusion
RMZ Centennial RMZ Centennial
Mahadevapura Post Mahadevapura Post
Bangalore - 560048 India Bangalore - 560048 India
EMail: kingstonsmiler@gmail.com EMail: kingstonsmiler@gmail.com
skipping to change at page 10, line 7 skipping to change at page 11, line 10
218 Gajeong-ro 218 Gajeong-ro
Yuseong-gu, Daejeon 34129 Yuseong-gu, Daejeon 34129
South Korea South Korea
Email:ryoo@etri.re.kr Email:ryoo@etri.re.kr
" "
DESCRIPTION DESCRIPTION
"This management information module supports the "This management information module supports the
configuration and management of MPLS-TP linear configuration and management of MPLS-TP linear
protection domains. " protection domains. "
REVISION REVISION
"201605190000Z" -- May 19, 2016 "201608080000Z" -- August 8, 2016
DESCRIPTION DESCRIPTION
"MPLS-TP Protection Switching Domain objects for LSP "MPLS-TP Protection Switching Domain objects for LSP
MEPs" MEPs"
::= { mplsStdMIB xxx } -- xxx to be replaced with ::= { mplsStdMIB xxx } -- xxx to be replaced with
-- correct value -- correct value
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- Notifications -- Notifications
mplsLpsNotifications mplsLpsNotifications
skipping to change at page 15, line 52 skipping to change at page 17, line 8
as they do not correspond to valid values of as they do not correspond to valid values of
mplsLpsConfigDomainIndex." mplsLpsConfigDomainIndex."
::= { mplsLpsObjects 1 } ::= { mplsLpsObjects 1 }
mplsLpsConfigTable OBJECT-TYPE mplsLpsConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsLpsConfigEntry SYNTAX SEQUENCE OF MplsLpsConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists the MPLS-TP linear protection domains that "This table lists the MPLS-TP linear protection domains that
have been configured on the system." have been configured on the system.
An entry is created by a network operator who wants to run
the MPLS-TP linear protection protocol for the protection
domain."
::= { mplsLpsObjects 2 } ::= { mplsLpsObjects 2 }
mplsLpsConfigEntry OBJECT-TYPE mplsLpsConfigEntry OBJECT-TYPE
SYNTAX MplsLpsConfigEntry SYNTAX MplsLpsConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the mplsLpsConfigTable." "A conceptual row in the mplsLpsConfigTable."
INDEX { mplsLpsConfigDomainIndex } INDEX { mplsLpsConfigDomainIndex }
::= { mplsLpsConfigTable 1 } ::= { mplsLpsConfigTable 1 }
skipping to change at page 16, line 51 skipping to change at page 18, line 11
Managers should obtain new values for row Managers should obtain new values for row
creation in this table by reading mplsLpsConfigIndexNext." creation in this table by reading mplsLpsConfigIndexNext."
::= { mplsLpsConfigEntry 1 } ::= { mplsLpsConfigEntry 1 }
mplsLpsConfigDomainName OBJECT-TYPE mplsLpsConfigDomainName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Textual name represents the MPLS-TP linear protection domain. "Textual name represents the MPLS-TP linear protection domain.
Each protection domain is identified by a unique protection It facilitates easy administrative identification of
domain name. " each protection domain."
DEFVAL {""}
::= { mplsLpsConfigEntry 2 } ::= { mplsLpsConfigEntry 2 }
mplsLpsConfigMode OBJECT-TYPE mplsLpsConfigMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
psc(1), psc(1),
aps(2) aps(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 17, line 27 skipping to change at page 18, line 36
PSC PSC
The Protection State Coordination mode as described in The Protection State Coordination mode as described in
RFC 6378. RFC 6378.
APS APS
The Automatic Protection Switching mode as described in The Automatic Protection Switching mode as described in
RFC 7271. RFC 7271.
This object may not be modified if the associated This object may not be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). " mplsLpsConfigRowStatus object is equal to active(1).
The value of this object is not supposed to be changed
during operation. When the value should be changed,
the protection processes in both LERs MUST be
restarted with the same new value.
In case that this value is changed at one LER during
operation, the LER will generate PSC packets with a new
Capabilities TLV value. As a consequence, this will
result in mplsLpsEventCapabilitiesMismatch notification
at both LERs. "
REFERENCE REFERENCE
"Section 9.2 of RFC7271" "Sections 9.2 and 10 of RFC7271"
DEFVAL {psc} DEFVAL {psc}
::= { mplsLpsConfigEntry 3 } ::= { mplsLpsConfigEntry 3 }
mplsLpsConfigProtectionType OBJECT-TYPE mplsLpsConfigProtectionType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
onePlusOneUnidirectional (1), onePlusOneUnidirectional (1),
oneColonOneBidirectional (2), oneColonOneBidirectional (2),
onePlusOneBidirectional (3) onePlusOneBidirectional (3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 19, line 18 skipping to change at page 20, line 37
"Section 4.2.4 of RFC6378" "Section 4.2.4 of RFC6378"
DEFVAL { revertive } DEFVAL { revertive }
::= { mplsLpsConfigEntry 5 } ::= { mplsLpsConfigEntry 5 }
mplsLpsConfigSdThreshold OBJECT-TYPE mplsLpsConfigSdThreshold OBJECT-TYPE
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..100)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the threshold value of the Signal Degrade "This object holds the threshold value of the Signal Degrade
defect in percent. (SD) defect in percent. In order to detect the SD defect,
In order to detect the Signal Degrade (SD) defect,
the MPLS-TP packet loss measurement (LM) is performed the MPLS-TP packet loss measurement (LM) is performed
every second. every second.
If either the packet loss is negative (i.e., there are more If either the packet loss is negative (i.e., there are more
packets received than transmitted) or the packet loss ratio packets received than transmitted) or the packet loss ratio
(lost packets/transmitted packets) in percent is greater this (lost packets/transmitted packets) in percent is greater than
threshold value, a Bad Second is declared. The SD defect is this threshold value, a Bad Second is declared.
detected if there are mplsLpsConfigSdBadSeconds consecutive Otherwise, a Good Second is declared.
Bad Seconds and cleared if there are
The SD defect is detected if there are
mplsLpsConfigSdBadSeconds consecutive Bad Seconds
and cleared if there are
mplsLpsConfigSdGoodSeconds consecutive Good Seconds. mplsLpsConfigSdGoodSeconds consecutive Good Seconds.
This object may be modified if the associated This object may be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1)." mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Section 7 of RFC7271" "Clause 6.1.3.3 of [G8121] and Table 8-1 of [G8151]"
DEFVAL { 30 } DEFVAL { 30 }
::= { mplsLpsConfigEntry 6 } ::= { mplsLpsConfigEntry 6 }
mplsLpsConfigSdBadSeconds OBJECT-TYPE mplsLpsConfigSdBadSeconds OBJECT-TYPE
SYNTAX Unsigned32 (2..10) SYNTAX Unsigned32 (2..10)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the number of Bad Seconds to detect the SD. "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 If the number of consecutive Bad Seconds reaches this value,
mplsLpsConfigRowStatus object is equal to active(1). the SD defect is detected and used as an input to
the protection switching process.
This object may be modified if the associated This object may be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1). " mplsLpsConfigRowStatus object is equal to active(1). "
REFERENCE REFERENCE
"Section 7 of RFC7271" "Clause 6.1.3.3 of [G8121] and Table 8-1 of [G8151]"
DEFVAL { 10 } DEFVAL { 10 }
::= { mplsLpsConfigEntry 7 } ::= { mplsLpsConfigEntry 7 }
mplsLpsConfigSdGoodSeconds OBJECT-TYPE mplsLpsConfigSdGoodSeconds OBJECT-TYPE
SYNTAX Unsigned32 (2..10) SYNTAX Unsigned32 (2..10)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the number of Good Seconds to declare the "This object holds the number of Good Seconds to declare
clearance of SD defect. the clearance of SD defect.
See the description of mplsLpsConfigSdThreshold.
After an SD defect occurs at a path, if the number of
consecutive Good Seconds reaches this value for the
degraded path, the clearance of SD defect is declared and
used as an input to the protection switching process.
This object may be modified if the associated This object may be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1)." mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Section 7 of RFC7271" "Clause 6.1.3.3 of [G8121] and Table 8-1 of [G8151]"
DEFVAL { 10 } DEFVAL { 10 }
::= { mplsLpsConfigEntry 8 } ::= { mplsLpsConfigEntry 8 }
mplsLpsConfigWaitToRestore OBJECT-TYPE mplsLpsConfigWaitToRestore OBJECT-TYPE
SYNTAX Unsigned32 (5..12) SYNTAX Unsigned32 (5..12)
UNITS "minutes" UNITS "minutes"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the Wait To Restore timer value in seconds. "This object holds the Wait To Restore timer value in minutes,
Can be configured in 1 minute steps between 5 and 12 minutes. and can be configured in 1 minute steps between 5 and
12 minutes.
The WTR timer is used to delay reversion of PSC state The WTR timer is used to delay reversion of PSC state
to Normal state when recovering from a failure to Normal state when recovering from a failure
condition on the working path when the protection condition on the working path when the protection
domain is configured for revertive behavior domain is configured for revertive behavior
This object may not be modified if the associated This object may not be modified if the associated
mplsLpsConfigRowStatus object is equal to active(1)." mplsLpsConfigRowStatus object is equal to active(1)."
REFERENCE REFERENCE
"Section 3.5 of RFC6378" "Section 3.5 of RFC6378"
DEFVAL { 5 } DEFVAL { 5 }
skipping to change at page 27, line 35 skipping to change at page 29, line 17
DESCRIPTION DESCRIPTION
"This table lists Maintenance Association that have been "This table lists Maintenance Association that have been
configured in Protection domains." configured in Protection domains."
::= { mplsLpsObjects 4 } ::= { mplsLpsObjects 4 }
mplsLpsMeConfigEntry OBJECT-TYPE mplsLpsMeConfigEntry OBJECT-TYPE
SYNTAX MplsLpsMeConfigEntry SYNTAX MplsLpsMeConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the mplsLpsMeConfigTable. There is "A conceptual row in the mplsLpsMeConfigTable. There is
a sparse relationship between the conceptual rows of a sparse relationship between the conceptual rows of
this table and mplsOamIdMeTable." this table and mplsOamIdMeTable.
Each time that an entry is created in the mplsOamIdMeTable
for which the LER supports MPLS-TP linear protection,
a row is created automatically in the mplsLpsMeConfigTable.
An entry of this table is related to a single entry in
mplsOamIdMeTable. When a point-to-point transport path
needs to be monitored, one ME is needed for the path
and one entry in the mplsOamIdMeTable will be created.
But, the ME entry in the mplsOamIdMeTable may or may not
participate in protection switching.
If an ME participates in protection switching,
an entry in mplsLpsMeConfigTable MUST be created,
and the objects in the entry indicates
which protection domain this ME belongs to and
whether this ME is for either working path or protection path.
If the ME does not participate in protection switching,
an entry in mplsLpsMeConfigTable does not need to be created. "
INDEX {mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex} INDEX {mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex}
::= { mplsLpsMeConfigTable 1 } ::= { mplsLpsMeConfigTable 1 }
MplsLpsMeConfigEntry ::= SEQUENCE { MplsLpsMeConfigEntry ::= SEQUENCE {
mplsLpsMeConfigDomainIndexValue Unsigned32, mplsLpsMeConfigDomain Unsigned32,
mplsLpsMeConfigState INTEGER mplsLpsMeConfigPath INTEGER
} }
mplsLpsMeConfigDomainIndexValue OBJECT-TYPE mplsLpsMeConfigDomain OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the value of Protection domain index wherein "This object holds the value of protection domain index wherein
this ME included in. If this ME is not part of any protection this ME included in. If this ME is not part of any protection
domain then this object contains value 0. " domain then this object contains value 0. "
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsLpsMeConfigEntry 1 } ::= { mplsLpsMeConfigEntry 1 }
mplsLpsMeConfigState OBJECT-TYPE mplsLpsMeConfigPath OBJECT-TYPE
SYNTAX INTEGER { working(1), protection(2) } SYNTAX INTEGER { working(1), protection(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the operational state of the ME "This object represents whether the ME is configured
as either working or protection" as either the working path or the protection path"
REFERENCE REFERENCE
"Section 4.3 of RFC6378" "Section 4.3 of RFC6378"
::= { mplsLpsMeConfigEntry 2 } ::= { mplsLpsMeConfigEntry 2 }
-- --
-- MPLS Linear Protection ME Status Table -- MPLS Linear Protection ME Status Table
-- This table provides Protection Switching ME statistics. -- This table provides Protection Switching ME statistics.
-- --
mplsLpsMeStatusTable OBJECT-TYPE mplsLpsMeStatusTable OBJECT-TYPE
skipping to change at page 29, line 50 skipping to change at page 32, line 4
::= { mplsLpsMeStatusEntry 2 } ::= { mplsLpsMeStatusEntry 2 }
mplsLpsMeStatusSignalFailures OBJECT-TYPE mplsLpsMeStatusSignalFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the count of Signal failure conditions. "Represents the count of Signal failure conditions.
This condition occurs when the OAM running on this ME This condition occurs when the OAM running on this ME
detects the Signal Fail event." detects the Signal Fail event."
REFERENCE REFERENCE
"Section 4.3 of RFC6378" "Section 4.3 of RFC6378"
::= { mplsLpsMeStatusEntry 3 } ::= { mplsLpsMeStatusEntry 3 }
mplsLpsMeStatusSwitchovers OBJECT-TYPE mplsLpsMeStatusSwitchovers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the count of SwitchOvers happened in this ME. "Represents the count of SwitchOvers happened in this ME.
When the mplsLpsMeConfigState is working, this object will When the mplsLpsMeConfigPath is working, this object will
return the number of times that traffic has been switched return the number of times that traffic has been switched
from this working path to the protection path. from this working path to the protection path.
When the mplsLpsMeConfigState is protection, this object When the mplsLpsMeConfigPath is protection, this object
will return the number of times that traffic has been will return the number of times that traffic has been
switched back to the working path from this protection path." switched back to the working path from this protection path."
REFERENCE REFERENCE
"Section 4.3 of RFC6378" "Section 4.3 of RFC6378"
::= { mplsLpsMeStatusEntry 4 } ::= { mplsLpsMeStatusEntry 4 }
mplsLpsMeStatusLastSwitchover OBJECT-TYPE mplsLpsMeStatusLastSwitchover OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object holds the value of sysUpTime wherein the "This object holds the value of sysUpTime wherein the
last switchover happened. last switchover happened.
When the mplsLpsMeConfigState is working, this object When the mplsLpsMeConfigPath is working, this object
will return the value of sysUpTime when traffic was switched will return the value of sysUpTime when traffic was switched
from this path to the protection path. from this path to the protection path.
If traffic has never switched to the protection path, the If traffic has never switched to the protection path, the
value 0 will be returned. value 0 will be returned.
When the mplsLpsMeConfigState is protection, this object When the mplsLpsMeConfigPath is protection, this object
will return the value of sysUpTime the last time that will return the value of sysUpTime the last time that
traffic was switched back to the working path from this path. traffic was switched back to the working path from this path.
If no traffic has ever switched back to the working path from If no traffic has ever switched back to the working path from
this protection path, the value 0 will be returned." this protection path, the value 0 will be returned."
REFERENCE REFERENCE
"Section 4.3 of RFC6378" "Section 4.3 of RFC6378"
::= { mplsLpsMeStatusEntry 5 } ::= { mplsLpsMeStatusEntry 5 }
mplsLpsMeStatusSwitchoverSeconds OBJECT-TYPE mplsLpsMeStatusSwitchoverSeconds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at page 32, line 14 skipping to change at page 34, line 15
pathConfigMismatch pathConfigMismatch
Indicates mplsLpsEventPathConfigMismatch notifications Indicates mplsLpsEventPathConfigMismatch notifications
should be generated. should be generated.
fopNoResponse fopNoResponse
Indicates mplsLpsEventFopNoResponse notifications Indicates mplsLpsEventFopNoResponse notifications
should be generated. should be generated.
fopTimeout fopTimeout
Indicates mplsLpsEventFopTimout notifications Indicates mplsLpsEventFopTimeout notifications
should be generated." should be generated."
REFERENCE REFERENCE
"Section 12 of RFC7271" "Section 12 of RFC7271"
DEFVAL { { } } DEFVAL { { } }
::= { mplsLpsObjects 6 } ::= { mplsLpsObjects 6 }
-- MPLS Linear Protection EVENTS -- MPLS Linear Protection EVENTS
mplsLpsEventSwitchover NOTIFICATION-TYPE mplsLpsEventSwitchover NOTIFICATION-TYPE
OBJECTS { mplsLpsMeStatusSwitchovers, mplsLpsMeStatusCurrent } OBJECTS { mplsLpsMeStatusSwitchovers, mplsLpsMeStatusCurrent }
skipping to change at page 33, line 23 skipping to change at page 35, line 25
::= { mplsLpsNotifications 5 } ::= { mplsLpsNotifications 5 }
mplsLpsEventFopNoResponse NOTIFICATION-TYPE mplsLpsEventFopNoResponse NOTIFICATION-TYPE
OBJECTS { mplsLpsStatusFopNoResponses } OBJECTS { mplsLpsStatusFopNoResponses }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An mplsLpsEventFopNoResponse notification is sent when the "An mplsLpsEventFopNoResponse notification is sent when the
value of mplsLpsStatusFopNoResponses increments." value of mplsLpsStatusFopNoResponses increments."
::= { mplsLpsNotifications 6 } ::= { mplsLpsNotifications 6 }
mplsLpsEventFopTimout NOTIFICATION-TYPE mplsLpsEventFopTimeout NOTIFICATION-TYPE
OBJECTS { mplsLpsStatusFopTimeouts } OBJECTS { mplsLpsStatusFopTimeouts }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An mplsLpsEventFopTimout notification is sent when the "An mplsLpsEventFopTimeout notification is sent when the
value of mplsLpsStatusFopTimeouts increments." value of mplsLpsStatusFopTimeouts increments."
::= { mplsLpsNotifications 7 } ::= { mplsLpsNotifications 7 }
-- End of Notifications. -- End of Notifications.
-- Module Compliance. -- Module Compliance.
mplsLpsCompliances mplsLpsCompliances
OBJECT IDENTIFIER ::= { mplsLpsConformance 1 } OBJECT IDENTIFIER ::= { mplsLpsConformance 1 }
skipping to change at page 36, line 4 skipping to change at page 38, line 6
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsConfigStorageType OBJECT mplsLpsConfigStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- mplsLpsMeConfigTable -- mplsLpsMeConfigTable
OBJECT mplsLpsMeConfigDomainIndexValue
OBJECT mplsLpsMeConfigDomain
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLpsMeConfigState OBJECT mplsLpsMeConfigPath
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsLpsCompliances 2 } ::= { mplsLpsCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsLpsScalarGroup OBJECT-GROUP mplsLpsScalarGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 37, line 17 skipping to change at page 39, line 19
mplsLpsStatusFopTimeouts mplsLpsStatusFopTimeouts
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS Linear Protection "Collection of objects needed for MPLS Linear Protection
configuration and statistics." configuration and statistics."
::= { mplsLpsGroups 2 } ::= { mplsLpsGroups 2 }
mplsLpsMeTableGroup OBJECT-GROUP mplsLpsMeTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLpsMeConfigDomainIndexValue, mplsLpsMeConfigDomain,
mplsLpsMeConfigState, mplsLpsMeConfigPath,
mplsLpsMeStatusCurrent, mplsLpsMeStatusCurrent,
mplsLpsMeStatusSignalDegrades, mplsLpsMeStatusSignalDegrades,
mplsLpsMeStatusSignalFailures, mplsLpsMeStatusSignalFailures,
mplsLpsMeStatusSwitchovers, mplsLpsMeStatusSwitchovers,
mplsLpsMeStatusLastSwitchover, mplsLpsMeStatusLastSwitchover,
mplsLpsMeStatusSwitchoverSeconds mplsLpsMeStatusSwitchoverSeconds
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS Linear Protection "Collection of objects needed for MPLS Linear Protection
skipping to change at page 37, line 40 skipping to change at page 39, line 42
::= { mplsLpsGroups 3 } ::= { mplsLpsGroups 3 }
mplsLpsNotificationGroup NOTIFICATION-GROUP mplsLpsNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
mplsLpsEventSwitchover, mplsLpsEventSwitchover,
mplsLpsEventRevertiveMismatch, mplsLpsEventRevertiveMismatch,
mplsLpsEventProtecTypeMismatch, mplsLpsEventProtecTypeMismatch,
mplsLpsEventCapabilitiesMismatch, mplsLpsEventCapabilitiesMismatch,
mplsLpsEventPathConfigMismatch, mplsLpsEventPathConfigMismatch,
mplsLpsEventFopNoResponse, mplsLpsEventFopNoResponse,
mplsLpsEventFopTimout mplsLpsEventFopTimeout
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement notifications." "Collection of objects needed to implement notifications."
::= { mplsLpsGroups 4 } ::= { mplsLpsGroups 4 }
-- MPLS-LPS-MIB module ends -- MPLS-LPS-MIB module ends
END END
9. Security Considerations 9. Security Considerations
skipping to change at page 41, line 40 skipping to change at page 43, line 40
Operators", RFC 7271, DOI 10.17487/RFC7271, June 2014, Operators", RFC 7271, DOI 10.17487/RFC7271, June 2014,
<http://www.rfc-editor.org/info/rfc7271>. <http://www.rfc-editor.org/info/rfc7271>.
[RFC7697] Pan, P., Aldrin, S., Venkatesan, M., Sampath, K., Nadeau, [RFC7697] Pan, P., Aldrin, S., Venkatesan, M., Sampath, K., Nadeau,
T., and S. Boutros, "MPLS Transport Profile (MPLS-TP) T., and S. Boutros, "MPLS Transport Profile (MPLS-TP)
Operations, Administration, and Maintenance (OAM) Operations, Administration, and Maintenance (OAM)
Identifiers Management Information Base (MIB)", RFC 7697, Identifiers Management Information Base (MIB)", RFC 7697,
DOI 10.17487/RFC7697, January 2016, DOI 10.17487/RFC7697, January 2016,
<http://www.rfc-editor.org/info/rfc7697>. <http://www.rfc-editor.org/info/rfc7697>.
Authors' Addresses [G8121] International Telecommunication Union, "Characteristics of
MPLS-TP equipment functional blocks", ITU-T Recommendation
G.8121/Y.1381, April 2016.
[G8151] International Telecommunication Union, "Management aspects
of the MPLS-TP network element", ITU-T Recommendation
G.8151/Y.1374, January 2015.
Authors' Addresses
Kingston Smiler Selvaraj Kingston Smiler Selvaraj
IpInfusion IpInfusion
RMZ Centennial RMZ Centennial
Mahadevapura Post Mahadevapura Post
Bangalore - 560048 Bangalore - 560048
India India
EMail: kingstonsmiler@gmail.com EMail: kingstonsmiler@gmail.com
Venkatesan Mahalingam Venkatesan Mahalingam
Dell Inc. Dell Inc.
5450 Great America Parkway 5450 Great America Parkway
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
EMail: venkat.mahalingams@gmail.com EMail: venkat.mahalingams@gmail.com
Vishwas Manral Vishwas Manral
Nano Sec Nano Sec
 End of changes. 73 change blocks. 
146 lines changed or deleted 245 lines changed or added

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