draft-ietf-mpls-tp-mib-management-overview-04.txt   draft-ietf-mpls-tp-mib-management-overview-05.txt 
Network Working Group D. King (Editor) Network Working Group D. King (Editor)
Internet-Draft Old Dog Consulting Internet-Draft Old Dog Consulting
Intended status: Informational M. Venkatesan (Editor) Intended status: Informational M. Venkatesan (Editor)
Expires: November 12, 2011 Aricent Expires: February 5, 2012 Aricent
June 12, 2011 August 5, 2011
Multiprotocol Label Switching Transport Profile (MPLS-TP) Multiprotocol Label Switching Transport Profile (MPLS-TP)
MIB-based Management Overview MIB-based Management Overview
draft-ietf-mpls-tp-mib-management-overview-04.txt draft-ietf-mpls-tp-mib-management-overview-05.txt
Abstract Abstract
A range of Management Information Base (MIB) modules has been A range of Management Information Base (MIB) modules has been
developed to help model and manage the various aspects of developed to help model and manage the various aspects of
Multiprotocol Label Switching (MPLS) networks. These MIB modules are Multiprotocol Label Switching (MPLS) networks. These MIB modules are
defined in separate documents that focus on the specific areas of defined in separate documents that focus on the specific areas of
responsibility of the modules that they describe. responsibility of the modules that they describe.
The MPLS Transport Profile (MPLS-TP) is a profile of MPLS The MPLS Transport Profile (MPLS-TP) is a profile of MPLS
functionality specific to the construction of packet-switched functionality specific to the construction of packet-switched
transport networks. transport networks.
This document describes the MIB-based architecture for MPLS-TP, This document describes the MIB-based architecture for MPLS-TP,
and indicates the interrelationships between different existing MIB and indicates the interrelationships between different existing MIB
modules that can be leveraged for MPLS-TP network management and modules that can be leveraged for MPLS-TP network management and
identifies areas where additional MIB modules would be required. identifies areas where additional MIB modules are required.
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 to IETF 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), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 50 skipping to change at page 1, line 50
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 12, 2011. This Internet-Draft will expire on February 5, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 31 skipping to change at page 2, line 31
1. Introduction.................................................3 1. Introduction.................................................3
1.1 MPLS-TP Management Function.................................4 1.1 MPLS-TP Management Function.................................4
2. Terminology..................................................4 2. Terminology..................................................4
3. The SNMP Management Framework................................4 3. The SNMP Management Framework................................4
4. Overview of Existing Work....................................5 4. Overview of Existing Work....................................5
4.1. MPLS Management Overview and Requirements...............5 4.1. MPLS Management Overview and Requirements...............5
4.2. An Introduction to the MPLS and Pseudowire MIB Modules..5 4.2. An Introduction to the MPLS and Pseudowire MIB Modules..5
4.2.1. Structure of the MPLS MIB OID Tree...............5 4.2.1. Structure of the MPLS MIB OID Tree...............5
4.2.2. Textual Convention Modules.......................6 4.2.2. Textual Convention Modules.......................6
4.2.3. Label Edge Router (LER) Modules..................7 4.2.3. Label Switched Path (LSP) Modules................7
4.2.4. Label Switching Router Modules...................7 4.2.4. Label Edge Router (LER) Modules..................7
4.2.5. Label Switched Path Modules......................7 4.2.5. Label Switching Router (LSR) Modules.............7
4.2.6. Pseudowire Modules...............................8 4.2.6. Pseudowire Modules...............................8
4.2.7. Routing and Traffic Engineering..................9 4.2.7. Routing and Traffic Engineering..................9
4.2.8. Resiliency.......................................9 4.2.8. Resiliency.......................................9
4.2.9. Fault Management and Performance Management......10 4.2.9. Fault Management and Performance Management......10
4.2.10. MIB Module Interdependencies....................11 4.2.10. MIB Module Interdependencies....................11
4.2.11. Dependencies on External MIB Modules............13 4.2.11. Dependencies on External MIB Modules............13
5. Applicability of MPLS MIB modules to MPLS-TP.................14 5. Applicability of MPLS MIB modules to MPLS-TP.................14
5.1 MPLS-TP Tunnel...........................................14 5.1 MPLS-TP Tunnel...........................................14
5.1.1 Gap Analysis.......................................14 5.1.1 Gap Analysis.......................................14
5.1.2 Recommendations....................................15 5.1.2 Recommendations....................................15
5.2 MPLS-TP Pseudowire.......................................15 5.2 MPLS-TP Pseudowire.......................................15
5.2.1 Gap Analysis.......................................15 5.2.1 Gap Analysis.......................................15
5.2.2 Recommendations....................................15 5.2.2 Recommendations....................................15
5.3 MPLS-TP Sections.........................................15 5.3 MPLS-TP Sections.........................................16
5.3.1 Gap Analysis.......................................15 5.3.1 Gap Analysis.......................................16
5.3.2 Recommendations....................................15 5.3.2 Recommendations....................................16
5.4 MPLS-TP OAM..............................................16 5.4 MPLS-TP OAM..............................................16
5.4.1 Gap Analysis.......................................16 5.4.1 Gap Analysis.......................................16
5.4.2 Recommendations....................................16 5.4.2 Recommendations....................................16
5.5 MPLS-TP Protection Switching and Recovery................16 5.5 MPLS-TP Protection Switching and Recovery................16
5.5.1 Gap Analysis.......................................16 5.5.1 Gap Analysis.......................................16
5.5.2 Recommendations....................................16 5.5.2 Recommendations....................................17
5.6 MPLS-TP Interfaces.......................................16 5.6 MPLS-TP Interfaces.......................................17
5.6.1 Gap Analysis.......................................16 5.6.1 Gap Analysis.......................................17
5.6.2 Recommendations....................................17 5.6.2 Recommendations....................................17
6. An Introduction to the MPLS-TP MIB Modules...................17 6. An Introduction to the MPLS-TP MIB Modules...................17
6.1 MPLS-TP MIB Modules......................................17 6.1 MPLS-TP MIB Modules......................................18
6.1.1 Structure of the MPLS-TP MIB OID Tree.............17 6.1.1 Structure of the MPLS-TP MIB OID Tree.............18
6.1.2 Textual Conventions for MPLS-TP...................18 6.1.2 Textual Conventions for MPLS-TP...................18
6.1.3 Identifiers for MPLS-TP...........................18 6.1.3 Identifiers for MPLS-TP...........................18
6.1.4 LSR MIB Extensions for MPLS-TP....................18 6.1.4 LSR MIB Extensions for MPLS-TP....................18
6.1.5 Tunnel Extensions for MPLS-TP.....................18 6.1.5 Tunnel Extensions for MPLS-TP.....................19
6.2 PWE3 MIB Modules for MPLS-TP.............................18 6.2 PWE3 MIB Modules for MPLS-TP.............................19
6.2.1 Structure of the PWE3 MIB OID Tree for MPLS-TP....19 6.2.1 Structure of the PWE3 MIB OID Tree for MPLS-TP....19
6.2.2 Pseudowire Textual Conventions for MPLS-TP........19 6.2.2 Pseudowire Textual Conventions for MPLS-TP........19
6.2.3 Pseudowire Extensions for MPLS-TP.................19 6.2.3 Pseudowire Extensions for MPLS-TP.................19
6.2.4 Pseudowire MPLS Extensions for MPLS-TP............19 6.2.4 Pseudowire MPLS Extensions for MPLS-TP............19
6.3 OAM MIB Modules for MPLS-TP..............................19 6.3 OAM MIB Modules for MPLS-TP..............................20
6.3.1 Structure of the OAM MIB OID Tree for MPLS-TP.....19 6.3.1 Structure of the OAM MIB OID Tree for MPLS-TP.....20
6.3.2 LSP Ping MIB module...............................20 6.3.2 BFD MIB module....................................20
6.3.3 BFD MIB module....................................20 6.3.3 Common OAM MIB modules............................20
6.3.4 Common OAM MIB modules............................20
6.4. Protection Switching and Recovery MIB Modules 6.4. Protection Switching and Recovery MIB Modules
for MPLS-TP.............................................20 for MPLS-TP.............................................20
6.4.1 Structure of the Protection Switching 6.4.1 Structure of the Protection Switching
and Recovery MIB OID Tree for MPLS-TP.............21 and Recovery MIB OID Tree for MPLS-TP.............21
6.4.2 Linear Protection Switching MIB module............21 6.4.2 Linear Protection Switching MIB module............21
6.4.3 Ring Protection Switching MIB module..............21 6.4.3 Ring Protection Switching MIB module..............21
6.4.4 Mesh Protection Switching MIB module..............21 6.4.4 Mesh Protection Switching MIB module..............21
7. Management Options...........................................21 7. Management Options...........................................21
8. Security Considerations......................................21 8. Security Considerations......................................21
9. IANA Considerations..........................................22 9. IANA Considerations..........................................22
skipping to change at page 4, line 9 skipping to change at page 4, line 6
The MPLS Transport Profile (MPLS-TP) is a packet transport The MPLS Transport Profile (MPLS-TP) is a packet transport
technology based on a profile of the MPLS functionality specific technology based on a profile of the MPLS functionality specific
to the construction of packet-switched transport networks. to the construction of packet-switched transport networks.
MPLS is described in [RFC3031] and requirements for MPLS-TP are MPLS is described in [RFC3031] and requirements for MPLS-TP are
specified in [RFC5654]. specified in [RFC5654].
A range of Management Information Base (MIB) modules has been A range of Management Information Base (MIB) modules has been
developed to help model and manage the various aspects of developed to help model and manage the various aspects of
Multiprotocol Label Switching (MPLS) networks. These MIB modules Multiprotocol Label Switching (MPLS) networks. These MIB modules
are defined in separate documents that focus on the specific areas of are defined in separate documents that focus on the specific areas of
responsibility of the modules that they describe. responsibility for the modules that they describe.
An MPLS-TP network can be operated via static provisioning of An MPLS-TP network can be operated via static provisioning of
transport paths, or the elective use of a Generalized MPLS (GMPLS) transport paths, Label Switched Paths (LSPs) and Pseudowires (PW).
control plane to support dynamic provisioning of transport paths. Or the elective use of a Generalized MPLS (GMPLS) control plane to
support dynamic provisioning of transport paths, LSPs and PWs.
This document describes the MIB-based management architecture for This document describes the MIB-based management architecture for
MPLS-TP and indicates the interrelationships between different MPLS, as extended for MPLS-TP. The document also indicates the
existing MIB modules that should be leveraged for MPLS-TP network interrelationships between existing MIB modules that should be
management, if SNMP is used for the management interface and leveraged for MPLS-TP network management and identifies areas where
identifies areas where additional MIB modules would be required. Note additional MIB modules are required.
that [RFC5951] does not specify a preferred management interface
Note that [RFC5951] does not specify a preferred management interface
protocol to be used as the standard protocol for managing MPLS-TP protocol to be used as the standard protocol for managing MPLS-TP
networks. networks.
1.1 MPLS-TP Management Function 1.1 MPLS-TP Management Function
The management of the MPLS-TP networks is inseparable from that of The management of the MPLS-TP networks is separable from that of
its client networks so that the same means of management can be used its client networks so that the same means of management can be used
regardless of the client. The management functions of MPLS-TP regardless of the client. The management function of MPLS-TP
includes fault management, configuration management, performance includes fault management, configuration management, performance
monitoring, and security management. monitoring, and security management.
The purpose of the management function is to provide control and The purpose of the management function is to provide control and
monitoring over the protocol mechanisms and procedures that monitoring of the MPLS transport profile protocol mechanisms and
constitute the building blocks for a transport profile of MPLS. procedures. The requirements for the network management
The requirements for the network management functionality are functionality are found in [RFC5951]. A description of the network
found in [RFC5951]. A description of the network and element and element management architectures that can be applied to the
management architectures that can be applied to the management management of MPLS-based transport networks is found in [RFC5950].
of MPLS-based transport networks is found in [RFC5950].
2. Terminology 2. Terminology
This document also uses terminology from the MPLS architecture This document also uses terminology from the MPLS architecture
document [RFC3031] and the following MPLS related MIB modules: document [RFC3031], PWE3 architecture [RFC4805], and the following
MPLS TC MIB [RFC3811], MPLS LSR MIB [RFC3813], MPLS TE MIB [RFC3812], MPLS related MIB modules: MPLS TC MIB [RFC3811], MPLS LSR MIB
MPLS LDP MIB [RFC3815], MPLS FTN MIB [RFC3814] and TE LINK MIB [RFC3813], MPLS TE MIB [RFC3812], MPLS LDP MIB [RFC3815], MPLS FTN
[RFC4220]. MIB [RFC3814] and TE LINK MIB [RFC4220].
3. The SNMP Management Framework 3. The SNMP Management Framework
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). Structure of Management Information (SMI).
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].
This document discusses MIB modules that are compliant to the SMIv2, This document discusses MIB modules that are compliant to the SMIv2,
which is described in [RFC2578], [RFC2579] and [RFC2580]. which is described in [RFC2578], [RFC2579] and [RFC2580].
skipping to change at page 7, line 8 skipping to change at page 7, line 8
+- pwTcStdMIB -- PW-TC-STD-MIB [RFC5542] +- pwTcStdMIB -- PW-TC-STD-MIB [RFC5542]
Note: The OIDs for MIB modules are assigned and managed by IANA. Note: The OIDs for MIB modules are assigned and managed by IANA.
They can be found in the referenced MIB documents. They can be found in the referenced MIB documents.
4.2.2. Textual Convention Modules 4.2.2. Textual Convention Modules
MPLS-TC-STD-MIB [RFC3811], GMPLS-TC-STD-MIB [RFC4801], MPLS-TC-STD-MIB [RFC3811], GMPLS-TC-STD-MIB [RFC4801],
IANA-GMPLS-TC-MIB [RFC4802] and PW-TC-STD-MIB [RFC5542] contains the IANA-GMPLS-TC-MIB [RFC4802] and PW-TC-STD-MIB [RFC5542] contains the
Textual Conventions for MPLS and GMPLS networks. These Textual Textual Conventions for MPLS and GMPLS networks. These Textual
Conventions should be imported by MIB modules which manage MPLS Conventions should be imported by MIB modules which manage MPLS
and GMPLS networks. Section 3.2.11. highlights dependencies on and GMPLS networks. Section 4.2.11. highlights dependencies on
additional external MIB modules additional external MIB modules
4.2.3. Label Edge Router (LER) Modules 4.2.3. Label Switched Path (LSP) Modules
Label Edge Router (LER) Module helps in mapping data to LSP's An LSP is a path over which a labeled packet travels across the
based on the network layer header. The ingress device of the MPLS sequence of LSRs for a given FEC. When a packet, with or without
network is called Label Edge Routers (LER). label, arrives at an ingress LER of an LSP, it is encapsulated with
the label corresponding to the FEC and sent across the LSP. The
labeled packet traverses across the LSRs and arrives at the egress
LER of the LSP, where, it gets forwarded depending on the packet type
it came with. LSPs could be nested using label stacking, such that,
an LSP could traverse over another LSP. A further description of
an LSP can be found in [RFC3031].
At the LER when an unlabelled packet enters the ingress interface, MPLS-LSR-STD-MIB [RFC3813] describes the required objects to define
network layer header is parsed to classify the packet to a forwarding the LSP.
equivalence class (FEC). Each FEC is mapped to an LFIB entry to
encapsulate the unlabelled packet with one or more label entries 4.2.4. Label Edge Router (LER) Modules
referred to as the label stack. Each label stack entry consists of a
label, the 3 TC-bits for classifying the Traffic Class, the bottom of Ingress and Egress LSRs of an LSP are known as Label Edge Routers.
stack bit, and TTL. An ingress LER takes the incoming unlabeled or labeled packets and
encapsulates it with the corresponding label of the LSP it
represents, and forwards it, over to the adjacent LSR of the LSP.
Each FEC is mapped to a label forwarding entry, so that packet could
be encapsulated with one or more label entries, referred as label
stack.
The packet traverses across the LSP, and upon reaching the Egress
LER, further action will be taken to handle the packet, depending on
the packet it received. MPLS Architecture [RFC3031] details
the functionality of an Ingress and Egress LERs.
MPLS-FTN-STD-MIB [RFC3814] describes the managed objects for mapping MPLS-FTN-STD-MIB [RFC3814] describes the managed objects for mapping
FEC's to label bindings. FEC to label bindings.
4.2.4. Label Switching Router Modules 4.2.5. Label Switching Router (LSR) Modules
A router which performs MPLS forwarding is known as an LSR. An LSR A router which performs MPLS forwarding is known as an LSR. An LSR
receives a labelled packet and performs forwarding action based on receives a labelled packet and performs forwarding action based on
the label received. the label received.
LSR maintains a mapping of an incoming label and incoming interface LSR maintains a mapping of an incoming label and incoming interface
to one or more outgoing label and outgoing interfaces in its to one or more outgoing label and outgoing interfaces in its
forwarding database. When a labelled packet is received, LSR examines forwarding database. When a labelled packet is received, LSR examines
the topmost label in the label stack and then does 'swap', 'push' or the topmost label in the label stack and then does 'swap', 'push' or
'pop' operation based on the contents. 'pop' operation based on the contents.
MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling MPLS-LSR-STD-MIB [RFC3813] describes the managed objects for modeling
a Multiprotocol Label Switching (MPLS) [RFC3031] LSR. a Multiprotocol Label Switching (MPLS) [RFC3031] LSR.
MPLS-LSR-STD-MIB [RFC3813] contains the managed objects to maintain MPLS-LSR-STD-MIB [RFC3813] contains the managed objects to maintain
mapping of in-segments to out-segments. mapping of in-segments to out-segments.
4.2.5. Label Switched Path Modules
The path taken through the MPLS domain by a packet is referred to as
a label switched path (LSP). It is possible that this path may not be
understood or completely stored in any one LSR within the MPLS
domain.
MPLS-LSR-STD-MIB [RFC3813] describes the required objects to define
the LSP.
4.2.6. Pseudowire Modules 4.2.6. Pseudowire Modules
The PW (Pseudowire) MIB architecture provides a layered The PW (Pseudowire) MIB architecture provides a layered modular model
modular model into which any supported emulated service such as Frame into which any supported emulated service such as Frame Relay, ATM,
Relay, ATM, Ethernet, TDM and SONET/SDH can be connected to any Ethernet, TDM and SONET/SDH can be connected to any supported packet
supported packet switched network (PSN) type. This MIB architecture switched network (PSN) type. This MIB architecture is modeled based
is modeled based on PW3 architecture [RFC3985]. on PW3 architecture [RFC3985].
Emulated Service Layer, Generic PW Layer and PSN VC Layer constitute Emulated Service Layer, Generic PW Layer and PSN VC Layer constitute
the different layers of the model. A combination of the MIB modules the different layers of the model. A combination of the MIB modules
belonging to each layer provides the glue for mapping the emulated belonging to each layer provides the glue for mapping the emulated
service onto the native PSN service. At least three MIB modules each service onto the native PSN service. At least three MIB modules each
belonging to a different layer are required to define a PW emulated belonging to a different layer are required to define a PW emulated
service. service.
o Service-Specific module is dependent on the emulated signal type o Service-Specific module is dependent on the emulated signal type
and helps in modeling emulated service layer. and helps in modeling emulated service layer.
skipping to change at page 9, line 39 skipping to change at page 9, line 45
can be setup through a management plane or a control plane. can be setup through a management plane or a control plane.
MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling a MPLS-TE-STD-MIB [RFC3812] describes managed objects for modeling a
Multiprotocol Label Switching (MPLS) [RFC3031] based traffic Multiprotocol Label Switching (MPLS) [RFC3031] based traffic
engineering. This MIB module should be used in conjunction with the engineering. This MIB module should be used in conjunction with the
companion document [RFC3813] for MPLS based traffic engineering companion document [RFC3813] for MPLS based traffic engineering
configuration and management. configuration and management.
4.2.8. Resiliency 4.2.8. Resiliency
An MPLS resiliency is to make sure that there is no interruption to The purpose of MPLS resiliency is to ensure minimal interruption to
traffic when the failure occurs within the system or network. traffic when the failure occurs within the system or network.
Various components of MPLS resiliency solutions are, Various components of MPLS resiliency solutions are,
1) Graceful restart in LDP and RSVP-TE modules 1) Graceful restart in LDP and RSVP-TE modules
2) Make Before Break 2) Make Before Break
3) Protection Switching for LSPs 3) Protection Switching for LSPs
4) Fast ReRoute for LSPs 4) Fast ReRoute for LSPs
5) PW redundancy 5) PW redundancy
The below modules only support the SNMP based MIB management
The below modules only support the SNMP based mib management
for MPLS resiliency. for MPLS resiliency.
MPLS Fast Reroute is a restoration network resiliency mechanism used MPLS Fast Reroute is a restoration network resiliency mechanism used
in MPLS TE to redirect the traffic onto the backup LSP's in 10s of in MPLS TE to redirect the traffic onto the backup LSP's in 10s of
milliseconds in case of link or node failure across the LSP. milliseconds in case of link or node failure across the LSP.
MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] MPLS-FRR-GENERAL-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
contains objects that apply to any MPLS LSR implementing MPLS TE fast contains objects that apply to any MPLS LSR implementing MPLS TE fast
reroute functionality. reroute functionality.
skipping to change at page 10, line 30 skipping to change at page 10, line 36
MPLS manages the LSP and pseudowire faults through the use of LSP MPLS manages the LSP and pseudowire faults through the use of LSP
ping [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for ping [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for
VCCV [RFC5885] tools. VCCV [RFC5885] tools.
Current MPLS focuses on the in and/or out packet counters, Current MPLS focuses on the in and/or out packet counters,
errored packets, discontinuity time. errored packets, discontinuity time.
Some of the MPLS and Pseudowire performance tables used for Some of the MPLS and Pseudowire performance tables used for
performance management are given below. performance management are given below.
mplsTunnelPerfTable provides several counters (packets forwarded, mplsTunnelPerfTable [RFC3812] provides several counters (packets
packets dropped because of errors) to measure the performance of forwarded, packets dropped because of errors) to measure the
the MPLS tunnels. performance of the MPLS tunnels.
mplsInterfacePerfTable provides performance information (incoming and mplsInterfacePerfTable [RFC3813] provides performance information
outgoing labels in use and lookup failures) on a per-interface basis. (incoming and outgoing labels in use and lookup failures) on a
per-interface basis.
mplsInSegmentPerfTable contains statistical information (total mplsInSegmentPerfTable [RFC3813] contains statistical information
packets received by the insegment, total errored packets received, (total packets received by the insegment, total errored packets
total packets discarded, discontinuity time) for incoming MPLS received, total packets discarded, discontinuity time) for incoming
segments to an LSR. MPLS segments to an LSR.
mplsOutSegmentPerfTable contains statistical information (total mplsOutSegmentPerfTable [RFC3813] contains statistical information
packets received, total errored packets received, total packets (total packets received, total errored packets received, total
discarded, discontinuity time) for outgoing MPLS segments from an packets discarded, discontinuity time) for outgoing MPLS segments
LSR. from an LSR.
mplsFTNPerfTable contains performance information for the specified mplsFTNPerfTable [RFC3814] contains performance information for the
interface and an FTN entry mapped to this interface. specified interface and an FTN entry mapped to this interface.
mplsLdpEntityStatsTable and mplsLdpSessionStatsTable contain mplsLdpEntityStatsTable [RFC3815] and mplsLdpSessionStatsTable
statistical information (session attempts, errored packets, [RFC3815] contain statistical information (session attempts, errored
notifications) about an LDP entity. packets, notifications) about an LDP entity.
pwPerfCurrentTable, pwPerfIntervalTable, pwPerf1DayIntervalTable pwPerfCurrentTable [RFC5601], pwPerfIntervalTable [RFC5601],
provides pseudowire performance information (in and/or out packets) pwPerf1DayIntervalTable [RFC5601] provides pseudowire performance
based on time (current interval, preconfigured specific interval, information (in and/or out packets) based on time (current interval,
1day interval). preconfigured specific interval, 1day interval).
pwEnetStatsTable contains statistical counters specific for Ethernet pwEnetStatsTable [RFC5603] contains statistical counters specific for
PW. Ethernet PW.
pwTDMPerfCurrentTable, pwTDMPerfIntervalTable and pwTDMPerfCurrentTable [RFC5604], pwTDMPerfIntervalTable [RFC5604] and
pwTDMPerf1DayIntervalTable contain statistical informations pwTDMPerf1DayIntervalTable [RFC5604] contain statistical informations
accumulated per 15-minute, 24 hour, 1 day respectively. accumulated per 15-minute, 24 hour, 1 day respectively.
gmplsTunnelErrorTable and gmplsTunnelReversePerfTable provides
information about performance errored packets and in/out packet gmplsTunnelErrorTable [RFC4802] and gmplsTunnelReversePerfTable
counters. [RFC4802] provides information about performance errored packets and
in/out packet counters.
4.2.10. MIB Module Interdependencies 4.2.10. MIB Module Interdependencies
This section provides an overview of the relationship between the This section provides an overview of the relationship between the
MPLS MIB modules for managing MPLS networks. More details of these MPLS MIB modules for managing MPLS networks. More details of these
relationships are given below. relationships are given below.
[RFC4221] mainly focuses on the MPLS MIB module interdependencies, [RFC4221] mainly focuses on the MPLS MIB module interdependencies,
this section also highlights the GMPLS and PW MIB modules this section also highlights the GMPLS and PW MIB modules
interdependencies. interdependencies.
The relationship "A --> B" means A depends on B and that MIB module The relationship "A --> B" means A depends on B and that MIB module
A uses an object, object identifier, or textual convention defined A uses an object, object identifier, or textual convention defined
in MIB module B, or that MIB module A contains a pointer (index or in MIB module B, or that MIB module A contains a pointer (index or
RowPointer) to an object in MIB module B. RowPointer) to an object in MIB module B.
+-------> MPLS-TC-STD-MIB <-----------------------------------------+ +-------> MPLS-TC-STD-MIB <-----------------------------------------+
| ^ | ^ ^ ^
| | | | | |
| MPLS-LSR-STD-MIB <--------------------------------+ | | MPLS-LSR-STD-MIB <--------------------------------+ |
| ^ |
| | | | | |
+<----------------------- MPLS-LDP-STD-MIB ---------------->+ | +<----------------------- MPLS-LDP-STD-MIB ---------------->+ |
| ^ | | ^ ^ ^ |
| | | | | | | |
+<-- MPLS-LDP-GENERIC-STD-MIB ------>+ | | +<-- MPLS-LDP-GENERIC-STD-MIB ------>+ | |
^ | |
| | | | | |
+<------ MPLS-FTN-STD-MIB ---------+----------------------->+ | +<------ MPLS-FTN-STD-MIB --------------------------------->+ |
| | | | ^ | ^ |
| V | | | V | |
+<------------- MPLS-TE-STD-MIB ->+ | +<------------- MPLS-TE-STD-MIB -->+----------------------->+ |
| GMPLS-TC-STD-MIB ------------>+ ^ GMPLS-TC-STD-MIB ------------>+
| ^ | | ^ ^
| | | | | |
+---+ +<-- GMPLS-LABEL-STD-MIB -->+ +---+ +<-- GMPLS-LABEL-STD-MIB -->+
| ^ ^ ^ | ^ ^ ^ ^ ^
| | | | | | | | | |
+----> PW-TC-STD-MIB | GMPLS-LSR-STD-MIB --------------->+ +----> PW-TC-STD-MIB | GMPLS-LSR-STD-MIB --------------->+
| | ^ ^ | ^ | ^ ^ ^
| | | | | | | | | |
| IANA-PWE3-MIB | | | IANA-GMPLS-TC-MIB | | IANA-PWE3-MIB | | | IANA-GMPLS-TC-MIB |
| ^ | | | ^ | | ^ | | | ^ |
| | | | | | | | | | | | | |
| | +<--- GMPLS-TE-STD-MIB ------------->+ | | +<--- GMPLS-TE-STD-MIB ------------->+
| | ^ | | | ^ ^
+<--- PW-STD-MIB <------+ | | +<--- PW-STD-MIB <------+ | |
^ ^ | |
| | | | | | | |
+<--- PW-ENET-STD-MIB ->+ | | +<--- PW-ENET-STD-MIB ->+ | |
| ^ | | ^ ^ | |
| | | |
| | | | | | | |
+<---------------- PW-MPLS-STD-MIB -------------------------------->+ +<---------------- PW-MPLS-STD-MIB -------------------------------->+
Thus: Thus:
- All the MPLS MIB modules depend on MPLS-TC-STD-MIB. - All the MPLS MIB modules depend on MPLS-TC-STD-MIB.
- All the GMPLS MIB modules depend on GMPLS-TC-STD-MIB. - All the GMPLS MIB modules depend on GMPLS-TC-STD-MIB.
- All the PW MIB modules depend on PW-TC-STD-MIB. - All the PW MIB modules depend on PW-TC-STD-MIB.
skipping to change at page 14, line 11 skipping to change at page 14, line 13
(CSPF) module to obtain the path required for an MPLS tunnel to reach (CSPF) module to obtain the path required for an MPLS tunnel to reach
the end point of the tunnel and BFD module to verify the data-plane the end point of the tunnel and BFD module to verify the data-plane
failures of LSPs and PWs. failures of LSPs and PWs.
Finally, all of the MIB modules import standard textual conventions Finally, all of the MIB modules import standard textual conventions
such as integers, strings, timestamps, etc., from the MIB modules in such as integers, strings, timestamps, etc., from the MIB modules in
which they are defined. which they are defined.
5. Applicability of MPLS MIB modules to MPLS-TP 5. Applicability of MPLS MIB modules to MPLS-TP
This section and its sub sections focus on the possible gaps that This section highlights gaps in existing MPLS MIB modules in
exist in the MPLS MIB modules to extend its use to MPLS-TP networks. order to determine extensions or additional MIB modules that are
required to support MPLS-TP in MPLS networks
[RFC5951] specifies the requirements for the management of [RFC5951] specifies the requirements for the management of equipment
equipment used in networks supporting an MPLS-TP. It also details the used in networks supporting an MPLS-TP. It also details the
essential network management capabilities for operating networks essential network management capabilities for operating networks
consisting of MPLS-TP equipment. consisting of MPLS-TP equipment.
[RFC5950] provides the network management framework for [RFC5950] provides the network management framework for MPLS-TP. The
MPLS-TP. The document explains how network elements and networks that document explains how network elements and networks that support
support MPLS-TP can be managed using solutions that satisfy the MPLS-TP can be managed using solutions that satisfy the
requirements defined in [RFC5951]. The relationship between requirements defined in [RFC5951]. The relationship between MPLS-TP
MPLS-TP management and OAM is described in the MPLS-TP framework management and OAM is described in the MPLS-TP framework [RFC5950]
[RFC5950] document. document.
The MPLS mib modules MPLS-TE-STD-MIB [RFC3812], PW-STD-MIB [RFC5601] The MPLS MIB modules MPLS-TE-STD-MIB [RFC3812], PW-STD-MIB [RFC5601]
and MPLS-LSR-STD-MIB [RFC3813] and their associated mib modules are and MPLS-LSR-STD-MIB [RFC3813] and their associated MIB modules are
reused for MPLS based transport network management. reused for MPLS based transport network management.
Fault management and performance management form key parts of Fault management and performance management form key parts of
Operations, Administration, and Maintenance (OAM) function. MPLS-TP the Operations, Administration, and Maintenance (OAM) function.
OAM is described in [MPLS-TP-OAM-FWK]. MPLS-TP OAM is described in [MPLS-TP-OAM-FWK].
A seperate draft will provide an MPLS-TP abstract model and use a
formal language to define the terminology, the information that
must be retrieved and method for storing.
5.1 MPLS-TP Tunnel 5.1 MPLS-TP Tunnel
5.1.1 Gap Analysis 5.1.1 Gap Analysis
MPLS-TP tunnel can be operated over IP and/or ICC environments, MPLS-TP tunnel can be operated over IP and/or ICC environments,
below points capture the gaps in existing MPLS mib modules below points capture the gaps in existing MPLS MIB modules
for managing the MPLS-TP networks. for managing the MPLS-TP networks.
o IP based environment - IP based environment
i. MPLS-TE-STD-MIB [RFC3812] does not support i. MPLS-TE-STD-MIB [RFC3812] does not support tunnel
tunnel LSR identifier based on Global_ID and Node_ID. Ingress/Egress identifier based on Global_ID and Node_ID
[MPLS-TP-IDENTIFIERS].
ii. MPLS-TE-STD-MIB [RFC3812] does not support ii. MPLS-TE-STD-MIB [RFC3812] does not support
corouted/associated bidirectional tunnel configurations. co-routed/associated bidirectional tunnel configurations.
o ICC based environment - ICC based environment
i. MPLS-TE-STD-MIB [RFC3812] does not support i. MPLS-TE-STD-MIB [RFC3812] does not support tunnel LSR
tunnel LSR identifier based on ICC. identifier based on ICC.
ii. MPLS tunnel does not support forwarding other ii. MPLS tunnel does not support forwarding other than the nexthop
than the nexthop IP address. IP address.
5.1.2 Recommendations 5.1.2 Recommendations
o New MIB definitions can be created for Global_Node_ID and/or - New MIB definitions may be created for Global_Node_ID and/or
ICC configurations. ICC configurations.
o MPLS-LSR-STD-MIB [RFC3813] mib module can be enhanced to identify
the nexthop based on MAC address for IP-less environment. - MPLS-LSR-STD-MIB [RFC3813] MIB modules may be enhanced to identify
o MPLS-TE-STD-MIB [RFC3812] and MPLS-LSR-STD-MIB should be the nexthop based on MAC address for IP-less environments.
enhanced to provide static and signalling mib module OutSegment may be extended to hold the MAC-address also for
extensions for corouted/associated bidirectional LSPs. IP-less environments.
- MPLS-TE-STD-MIB [RFC3812] and MPLS-LSR-STD-MIB may be
enhanced to provide static and signalling MIB module
extensions for co-routed/associated bidirectional LSPs.
5.2 MPLS-TP Pseudowire 5.2 MPLS-TP Pseudowire
5.2.1 Gap Analysis 5.2.1 Gap Analysis
MPLS-TP Pseudowire can be operated over IP and/or ICC environments, MPLS-TP Pseudowire can be operated over IP and/or ICC environments,
below points capture the gaps in existing PW mib modules below points capture the gaps in existing PW MIB modules
for managing the MPLS-TP networks. for managing the MPLS-TP networks.
o IP based environment [MPLS-TP-IDENTIFIERS] specifies an initial set of identifiers to be
used in MPLS-TP. These identifiers were chosen to be compatible with
existing MPLS, GMPLS, and PW definitions.
- IP based environment
i. PW-STD-MIB [RFC5601] does not support i. PW-STD-MIB [RFC5601] does not support
PW end point identifier based on Global_ID and Node_ID. PW end point identifier based on Global_ID and Node_ID.
ii. PW-MPLS-STD-MIB [RFC5602] does not support ii. PW-MPLS-STD-MIB [RFC5602] does not support
its opeation over corouted/associated bidirectional tunnels. its operation over co-routed/associated bidirectional tunnels.
o ICC based environment - ICC based environment
i. PW-STD-MIB [RFC5601] does not support i. PW-STD-MIB [RFC5601] does not support
PW end point identifier based on ICC. PW end point identifier based on ICC.
ii. Pseudowire does not support forwarding other ii. Pseudowire does not support forwarding other
than the nexthop IP address. than the nexthop IP address.
5.2.2 Recommendations 5.2.2 Recommendations
o PW-MPLS-STD-MIB [RFC5602] can be enhanced to operate over - PW-MPLS-STD-MIB [RFC5602] can be enhanced to operate over
corouted/associated bi-directional tunnel. co-routed/associated bi-directional tunnel.
o Pseudowire 129 FEC type-2 can be used in non-IP and IP
- Pseudowire 129 FEC type-2 can be used in non-IP and IP
environments with the required changes. environments with the required changes.
5.3 MPLS-TP Sections 5.3 MPLS-TP Sections
5.3.1 Gap Analysis 5.3.1 Gap Analysis
The existing MPLS MIB modules does not support MPLS-TP sections. The existing MPLS MIB modules does not support MPLS-TP sections.
5.3.2 Recommendations 5.3.2 Recommendations
Link specific and/or path/segment specific sections can be achieved Link specific and/or path/segment specific sections can be achieved
by enhancing the IF-MIB [RFC2863], MPLS-TE-STD-MIB [RFC3812] and by enhancing the IF-MIB [RFC2863], MPLS-TE-STD-MIB [RFC3812] and
PW-STD-MIB [RFC5601] mib modules. PW-STD-MIB [RFC5601] MIB modules.
5.4 MPLS-TP OAM 5.4 MPLS-TP OAM
5.4.1 Gap Analysis 5.4.1 Gap Analysis
MPLS manages the LSP and pseudowire faults through LSP ping MPLS manages the LSP and pseudowire faults through LSP ping
[RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV
[RFC5885] tools. [RFC5885] tools.
The MPLS mib modules do not support the below MPLS-TP OAM functions, The MPLS MIB modules do not support the below MPLS-TP OAM functions:
o Continuity Check and Connectivity Verification o Continuity Check and Connectivity Verification
o Remote Defect Indication o Remote Defect Indication
o Route Tracing
o Alarm Reporting o Alarm Reporting
o Lock Reporting o Lock Reporting
o Lock Instruct o Lock Instruct
o Client Failure Indication o Client Failure Indication
o Packet Loss Measurement o Packet Loss Measurement
o Packet Delay Measurement o Packet Delay Measurement
5.4.2 Recommendations 5.4.2 Recommendations
New mib modules for BFD and LSP Ping can be created to address New MIB module for BFD can be created to address all the gaps
all the gaps mentioned in the 5.4.1 Gap Analysis section. mentioned in Section 5.4.1. (Gap Analysis).
5.5 MPLS-TP Protection Switching and Recovery 5.5 MPLS-TP Protection Switching and Recovery
5.5.1 Gap Analysis 5.5.1 Gap Analysis
An important aspect that MPLS-TP technology provides is protection An important aspect that MPLS-TP technology provides is protection
switching. In general, the mechanism of protection switching switching. In general, the mechanism of protection switching
can be described as the substitution of a protection or standby can be described as the substitution of a protection or standby
facility for a working or primary facility. facility for a working or primary facility.
The MPLS mib modules do not provide support for protection switching The MPLS MIB modules do not provide support for protection switching
and recovery of three different topologies (linear, ring and mesh) and recovery of three different topologies (linear, ring and mesh)
available. available.
5.5.2 Recommendations 5.5.2 Recommendations
New mib modules can be created to address all the gaps mentioned New MIB modules can be created to address all the gaps mentioned
in the 5.5.1 Gap Analysis section. in the 5.5.1 Gap Analysis section.
5.6 MPLS-TP Interfaces 5.6 MPLS-TP Interfaces
5.6.1 Gap Analysis 5.6.1 Gap Analysis
As per [MPLS-TP-IDENTIFIERS], an LSR requires identification of the As per [MPLS-TP-IDENTIFIERS], an LSR requires identification of the
node itself and of its interfaces. An interface is the attachment node itself and of its interfaces. An interface is the attachment
point to a server layer MPLS-TP section or MPLS-TP tunnel. point to a server layer MPLS-TP section or MPLS-TP tunnel.
The MPLS mib modules do not provide support for configuring The MPLS MIB modules do not provide support for configuring
the interfaces within the context of an operator. the interfaces within the context of an operator.
5.6.2 Recommendations 5.6.2 Recommendations
New mib defintions can be created to address the gaps mentioned New MIB definitions can be created to address the gaps mentioned
in the 5.6.1 Gap Analysis section. in the 5.6.1 Gap Analysis section.
6. An Introduction to the MPLS-TP MIB Modules 6. An Introduction to the MPLS-TP MIB Modules
This section highlights new MIB modules that have been identified This section highlights new MIB modules that have been identified
as being required for MPLS-TP. This section also provides an overview as being required for MPLS-TP. This section also provides an overview
of the following: of the following:
- the MPLS Object Identifier (OID) tree structure and the position - the MPLS Object Identifier (OID) tree structure and the position
of different MPLS related MIB modules on this tree; of different MPLS related MIB modules on this tree;
- the purpose of each of the MIB modules within the MIB documents, - the purpose of each of the MIB modules within the MIB documents,
what it can be used for, and how it relates to the other MIB what it can be used for, and how it relates to the other MIB
modules. modules.
Note that each new MIB module (apart from Textual Conventions Note that each new MIB module (apart from Textual Conventions
modules) will contain one or more Compliance Statements to indicate modules) will contain one or more Compliance Statements to indicate
which objects must be suppor in what manner to claim a specific level which objects must be supported in what manner to claim a specific
of compliance. Additional text, either in the documents that define level of compliance. Additional text, either in the documents that
the MIB modules or in separate Applicability Statements, will define define the MIB modules or in separate Applicability Statements, will
which Compliance Statements need tbe conformed to in order to provide define which Compliance Statements need to be conformed to in order
specific MPLS-TP function. This document does not set any to provide specific MPLS-TP function. This document does not set any
requirements in that respect although some recommendations are requirements in that respect although some recommendations are
included in the sections that follow. included in the sections that follow.
6.1 MPLS-TP MIB Modules 6.1 MPLS-TP MIB Modules
6.1.1 Structure of the MPLS-TP MIB OID Tree 6.1.1 Structure of the MPLS-TP MIB OID Tree
The MPLS-TP MIB OID tree has the following structure. The MPLS-TP MIB OID tree has the following structure.
transmission -- RFC 2578 [RFC2578] transmission -- RFC 2578 [RFC2578]
skipping to change at page 18, line 5 skipping to change at page 18, line 23
+- mplsStdMIB +- mplsStdMIB
| |
+- Textual Conventions for MPLS-TP +- Textual Conventions for MPLS-TP
| |
+- Identifiers for MPLS-TP +- Identifiers for MPLS-TP
| |
+- LSR MIB Extensions for MPLS-TP +- LSR MIB Extensions for MPLS-TP
| |
+- TE MIB Extensions for MPLS-TP +- TE MIB Extensions for MPLS-TP
Note that the mib modules mentioned here are applicable Note that the MIB modules mentioned here are applicable
for MPLS operations as well. for MPLS operations as well.
Note: The OIDs for MIB modules are yet to be assigned and managed by Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA. IANA.
6.1.2 Textual Conventions for MPLS-TP 6.1.2 Textual Conventions for MPLS-TP
New textual convention mib module defines textual A new textual convention MIB module will define textual
conventions [RFC2579] for MPLS-TP related MIB modules. conventions [RFC2579] for MPLS-TP related MIB modules.
These conventions allow multiple MIB modules to use the These conventions allow multiple MIB modules to use the
same syntax and format for a concept that is shared between same syntax and format for a concept that is shared between
the MIB modules. the MIB modules.
For example, MEP identifier is used to identify maintenance entity For example, MEP identifier is used to identify maintenance entity
group end point within MPLS-TP networks. The textual convention group end point within MPLS-TP networks. The textual convention
representing the MEP identifier is defined in new textual convention representing the MEP identifier should be defined in a new textual
mib module. convention MIB module.
All new extensions related to MPLS-TP are defined in the MIB module All new extensions related to MPLS-TP are defined in the MIB module
and will be referenced by other MIB modules to support MPLS-TP. and will be referenced by other MIB modules to support MPLS-TP.
6.1.3 Identifiers for MPLS-TP 6.1.3 Identifiers for MPLS-TP
New Identifiers describe managed objects that are used to model New Identifiers describe managed objects that are used to model
common MPLS-TP identifiers [MPLS-TP-IDENTIFIERS]. common MPLS-TP identifiers [MPLS-TP-IDENTIFIERS].
6.1.4 LSR MIB Extensions for MPLS-TP 6.1.4 LSR MIB Extensions for MPLS-TP
MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label
Switching Router (LSR). This puts it at the heart of the management Switching Router (LSR). This puts it at the heart of the management
architecture for MPLS. architecture for MPLS.
In the case of MPLS-TP, the MPLS-LSR-STD-MIB is extended to support In the case of MPLS-TP, the MPLS-LSR-STD-MIB is extended to support
the MPLS-TP LSP's, which are corouted or associated bidirectional. the MPLS-TP LSP's, which are co-routed or associated bidirectional.
This extended MIB is also applicable for modeling MPLS-TP tunnels. This extended MIB is also applicable for modeling MPLS-TP tunnels.
6.1.5 Tunnel Extensions for MPLS-TP 6.1.5 Tunnel Extensions for MPLS-TP
MPLS-TE-STD-MIB describes managed objects that are used to model and MPLS-TE-STD-MIB describes managed objects that are used to model and
manage MPLS Traffic Engineered (TE) Tunnels. manage MPLS Traffic Engineered (TE) Tunnels.
MPLS-TP tunnels are much similar to MPLS-TE tunnels, but are MPLS-TP tunnels are very similar to MPLS-TE tunnels, but are
bidirectional and could be co-routed or associated. co-routed or associated bidirectionally.
The MPLS-TE-STD-MIB is extended to support the MPLS-TP specific
The MPLS-TE-STD-MIB must be extended to support the MPLS-TP specific
attributes for the tunnel. attributes for the tunnel.
6.2 PWE3 MIB Modules for MPLS-TP 6.2 PWE3 MIB Modules for MPLS-TP
This section provides an overview of Pseudowire extension mib
This section provides an overview of Pseudowire extension MIB
modules to meet the MPLS based transport network requirements. modules to meet the MPLS based transport network requirements.
6.2.1 Structure of the PWE3 MIB OID Tree for MPLS-TP 6.2.1 Structure of the PWE3 MIB OID Tree for MPLS-TP
mib-2 -- RFC 2578 [RFC2578] mib-2 -- RFC 2578 [RFC2578]
| |
+-transmission +-transmission
| | | |
| +- Pseudowire Extensions for MPLS-TP | +- Pseudowire Extensions for MPLS-TP
| |
skipping to change at page 19, line 26 skipping to change at page 19, line 44
| |
+- Pseudowire Textual Conventions for MPLS-TP +- Pseudowire Textual Conventions for MPLS-TP
Note: The OIDs for MIB modules are yet to be assigned and managed by Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA. IANA.
6.2.2 Pseudowire Textual Conventions for MPLS-TP 6.2.2 Pseudowire Textual Conventions for MPLS-TP
PW-TC-STD-MIB MIB defines textual conventions used for pseudowire PW-TC-STD-MIB MIB defines textual conventions used for pseudowire
(PW) technology and for Pseudowire Edge-to-Edge Emulation (PWE3) MIB (PW) technology and for Pseudowire Edge-to-Edge Emulation (PWE3) MIB
Modules. New textual convention mib module defines textual Modules. A new textual convention MIB module will define textual
definitions for MPLS-TP specific Pseudowire attributes. definitions for MPLS-TP specific Pseudowire attributes.
6.2.3 Pseudowire Extensions for MPLS-TP 6.2.3 Pseudowire Extensions for MPLS-TP
PW-STD-MIB describes managed objects for modeling of Pseudowire PW-STD-MIB describes managed objects for modeling of Pseudowire
Edge-to-Edge services carried over a general Packet Switched Network. Edge-to-Edge services carried over a general Packet Switched Network.
This MIB module is extended to support MPLS-TP specific attributes This MIB module is extended to support MPLS-TP specific attributes
related to Pseudowires. related to Pseudowires.
6.2.4 Pseudowire MPLS Extensions for MPLS-TP 6.2.4 Pseudowire MPLS Extensions for MPLS-TP
skipping to change at page 19, line 37 skipping to change at page 20, line 4
definitions for MPLS-TP specific Pseudowire attributes. definitions for MPLS-TP specific Pseudowire attributes.
6.2.3 Pseudowire Extensions for MPLS-TP 6.2.3 Pseudowire Extensions for MPLS-TP
PW-STD-MIB describes managed objects for modeling of Pseudowire PW-STD-MIB describes managed objects for modeling of Pseudowire
Edge-to-Edge services carried over a general Packet Switched Network. Edge-to-Edge services carried over a general Packet Switched Network.
This MIB module is extended to support MPLS-TP specific attributes This MIB module is extended to support MPLS-TP specific attributes
related to Pseudowires. related to Pseudowires.
6.2.4 Pseudowire MPLS Extensions for MPLS-TP 6.2.4 Pseudowire MPLS Extensions for MPLS-TP
PW-MPLS-STD-MIB defines the managed objects for Pseudowire PW-MPLS-STD-MIB defines the managed objects for Pseudowire
operations over MPLS LSR's. This MIB supports both, operations over MPLS LSR's. This MIB supports both,
manual and dynamically signaled PW's, point-to-point connections, manual and dynamically signaled PW's, point-to-point connections,
enables the use of any emulated service, MPLS-TE as outer tunnel enables the use of any emulated service, MPLS-TE as outer tunnel
and no outer tunnel as MPLS-TE. and no outer tunnel as MPLS-TE.
The newly extended MIB defines the managed objects, The newly extended MIB defines the managed objects, extending
extending PW-MPLS-STD-MIB, by supporting with or without PW-MPLS-STD-MIB, by supporting with or without MPLS-TP as outer
MPLS-TP as outer tunnel. tunnel.
6.3 OAM MIB Modules for MPLS-TP 6.3 OAM MIB Modules for MPLS-TP
This section provides an overview of Operations, Administration, This section provides an overview of Operations, Administration,
and Maintenance (OAM) mib modules for MPLS LSPs and Pseudowires. and Maintenance (OAM) MIB modules for MPLS LSPs and Pseudowires.
6.3.1 Structure of the OAM MIB OID Tree for MPLS-TP 6.3.1 Structure of the OAM MIB OID Tree for MPLS-TP
mib-2 -- RFC 2578 [RFC2578] mib-2 -- RFC 2578 [RFC2578]
| |
+-transmission +-transmission
| |
+- LSP Ping MIB module
|
+- BFD MIB module +- BFD MIB module
| |
+- OAM MIB module +- OAM MIB module
Note: The OIDs for MIB modules are yet to be assigned and managed by Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA. IANA.
6.3.2 LSP Ping MIB module 6.3.2 BFD MIB module
LSP ping is defined in [RFC4379] to validate data plane consistency
of MPLS LSP's. It defines how LSP ping and Trace Route could be
performed across MPLS networks to identify and diagnose faults
within MPLS networks. This OAM functionality is performed on demand
basis for verification purposes.
New mib module defines managed objects for modeling LSP ping
protocol. It allows user to perform on demand operations based on
[RFC4379].
For example, a MPLS-TP tunnel LSP is to be pinged, a SNMP request
issued using the MIB for the tunnel in test. The results for the
operation could be queried using the managed objects defined in the
MIB module.
6.3.3 BFD MIB module
BFD-STD-MIB defines managed objects for performing BFD operation in BFD-STD-MIB defines managed objects for performing BFD operation in
IP networks. This MIB is modeled to support BFD protocol [RFC5880]. IP networks. This MIB is modeled to support BFD protocol [RFC5880].
New mib module is an extension to BFD-STD-MIB managed objects A new MIB module will be an extension to BFD-STD-MIB managed objects
to support BFD operations on MPLS LSPs and PWs. to support BFD operations on MPLS LSPs and PWs.
6.3.4 Common OAM MIB modules 6.3.3 Common OAM MIB modules
New mib module defines managed objects for OAM maintenance A new MIB module will define managed objects for OAM maintenance
identifiers i.e. Maintenance Entity Group Identifiers (MEG), identifiers i.e. Maintenance Entity Group Identifiers (MEG),
Maintenance Entity Group End-point (MEP), Maintenance Entity Group Maintenance Entity Group End-point (MEP), Maintenance Entity Group
Intermediate Point (MIP). Maintenance points are uniquely Intermediate Point (MIP). Maintenance points are uniquely
associated with a MEG. Within the context of a MEG, MEPs and MIPs associated with a MEG. Within the context of a MEG, MEPs and MIPs
must be uniquely identified. must be uniquely identified.
6.4. Protection Switching and Recovery MIB Modules for MPLS-TP 6.4. Protection Switching and Recovery MIB Modules for MPLS-TP
This section provides an overview of protection switching and This section provides an overview of protection switching and
recovery MIB modules for MPLS LSPs and Pseudowires. recovery MIB modules for MPLS LSPs and Pseudowires.
skipping to change at page 21, line 16 skipping to change at page 21, line 16
Tree for MPLS-TP Tree for MPLS-TP
mib-2 -- RFC 2578 [RFC2578] mib-2 -- RFC 2578 [RFC2578]
| |
+-transmission +-transmission
| |
+- Linear Protection Switching MIB module +- Linear Protection Switching MIB module
| |
+- Ring Protection Switching MIB module +- Ring Protection Switching MIB module
| |
+- Mesh Protection Swithcing MIB module +- Mesh Protection Switching MIB module
Note: The OIDs for MIB modules are yet to be assigned and managed by Note: The OIDs for MIB modules are yet to be assigned and managed by
IANA. IANA.
6.4.2 Linear Protection Switching MIB module 6.4.2 Linear Protection Switching MIB module
New mib module defines managed objects for linear protection A new MIB module will define managed objects for linear protection
switching of MPLS LSPs and Pseudowires. switching of MPLS LSPs and Pseudowires.
6.4.3 Ring Protection Switching MIB module 6.4.3 Ring Protection Switching MIB module
New mib module defines managed objects for ring protection A new MIB module will defined managed objects for ring protection
switching of MPLS LSPs and Pseudowires. switching of MPLS LSPs and Pseudowires.
6.4.4 Mesh Protection Switching MIB module 6.4.4 Mesh Protection Switching MIB module
New mib module defines managed objects for Mesh protection A new MIB module will defined managed objects for Mesh protection
switching of MPLS LSPs and Pseudowires. switching of MPLS LSPs and Pseudowires.
7. Management Options 7. Management Options
This document applies only to scenarios where MIB modules are used to This document applies only to scenarios where MIB modules are used to
manage the MPLS-TP network. It is not the intention of this document manage the MPLS-TP network. It is not the intention of this document
to provide instructions or advice to implementers of management to provide instructions or advice to implementers of management
systems, management agents, or managed entities. It is, however, systems, management agents, or managed entities. It is, however,
useful to make some observations about how the MIB modules described useful to make some observations about how the MIB modules described
above might be used to manage MPLS systems, if SNMP is used in the above might be used to manage MPLS systems, if SNMP is used in the
management interface. management interface.
For MPLS specific management options, refer [RFC4221] Section 12 For MPLS specific management options, refer to [RFC4221] Section 12.
(Management Options). (Management Options).
8. Security Considerations 8. Security Considerations
This document describes the interrelationships amongst the different This document describes the interrelationships amongst the different
MIB modules relevant to MPLS-TP management and as such does not have MIB modules relevant to MPLS-TP management and as such does not have
any security implications in and of itself. any security implications in and of itself.
Each IETF MIB document that specifies MIB objects for MPLS-TP must Each IETF MIB document that specifies MIB objects for MPLS-TP must
provide a proper security considerations section that explains the provide a proper security considerations section that explains the
security aspects of those objects. security aspects of those objects.
The attention of readers is particularly drawn to the security The attention of readers is particularly drawn to the security
implications of making MIB objects available for create or write implications of making MIB objects available for create or write
skipping to change at page 22, line 31 skipping to change at page 22, line 28
View-based Access Control Model STD 62, RFC 3415 [RFC3415], View-based Access Control Model STD 62, RFC 3415 [RFC3415],
is recommended. is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of each MIB module is properly entity giving access to an instance of each MIB module is properly
configured to give access to only those objects, and to those configured to give access to only those objects, and to those
principals (users) that have legitimate rights to access them. principals (users) that have legitimate rights to access them.
9. IANA Considerations 9. IANA Considerations
This document makes no requests for IANA action. This document has identified areas where additional MIB modules are
neccessary for MPLS-TP. The new MIB modules recommended by this
document will require OID assignments from IANA. However, this
document makes no specific request for IANA action.
10. Acknowledgements 10. Acknowledgements
The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin
Niven-Jenkins and Saravanan Narasimhan for their valuable comments. Niven-Jenkins, Saravanan Narasimhan and Joel Halpern for their
valuable comments.
This document benefited from review by participants in ITU-T Study This document also benefited from review by participants in ITU-T
Group 15. Study Group 15.
11. References 11. References
11.1 Normative References 11.1 Normative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB using SMIv2", RFC 2863, June 2000. MIB using SMIv2", RFC 2863, June 2000.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching (MPLS) Conventions and for Multiprotocol Label Switching (MPLS)
skipping to change at page 25, line 37 skipping to change at page 25, line 37
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", RFC 4379, Label Switched (MPLS) Data Plane Failures", RFC 4379,
March 2006. March 2006.
[RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and
G. Heron, "Pseudowire Setup and Maintenance Using the G. Heron, "Pseudowire Setup and Maintenance Using the
Label Distribution Protocol (LDP)", RFC 4447, Label Distribution Protocol (LDP)", RFC 4447,
April 2006. April 2006.
[RFC4805] Nicklass, O., Ed., "Definitions of Managed Objects for the
DS1, J1, E1, DS2, and E2 Interface Types", RFC 4805, March
2007.
[RFC5085] Nadeau, T. and C. Pignataro, "Pseudowire Virtual [RFC5085] Nadeau, T. and C. Pignataro, "Pseudowire Virtual
Circuit Connectivity Verification (VCCV): A Control Circuit Connectivity Verification (VCCV): A Control
Channel for Pseudowires", RFC 5085, December 2007. Channel for Pseudowires", RFC 5085, December 2007.
[RFC5601] Nadeau, T., Ed. and D. Zelig, Ed. "Pseudowire (PW) [RFC5601] Nadeau, T., Ed. and D. Zelig, Ed. "Pseudowire (PW)
Management Information Base (MIB)", RFC 5601, July 2009. Management Information Base (MIB)", RFC 5601, July 2009.
[RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over [RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over
MPLS PSN Management Information Base (MIB)", RFC 5602, MPLS PSN Management Information Base (MIB)", RFC 5602,
July 2009. July 2009.
skipping to change at page 26, line 22 skipping to change at page 26, line 25
RFC5885, June 2010. RFC5885, June 2010.
[RFC5950] Gray, E., Mansfield, S., Lam, K., [RFC5950] Gray, E., Mansfield, S., Lam, K.,
"MPLS-TP Network Management Framework", RFC 5950, "MPLS-TP Network Management Framework", RFC 5950,
September 2010. September 2010.
[RFC5951] Gray, E., Mansfield, S., Lam, K., "MPLS TP [RFC5951] Gray, E., Mansfield, S., Lam, K., "MPLS TP
Network Management Requirements", RFC 5951, September Network Management Requirements", RFC 5951, September
2010. 2010.
[MPLS-TP-IDENTIFIERS] Bocci, M., Swallow, G., "MPLS-TP Identifiers" [MPLS-TP-IDENTIFIERS] Bocci, M., Swallow, G., Gray, E.,
draft-ietf-mpls-tp-identifiers-04, March 2011. "MPLS-TP Identifiers" draft-ietf-mpls-tp-identifiers-07,
July 2011 and Winter, R., Van Helvoort, H., Betts, M.,
"MPLS-TP Identifiers Following ITU-T Conventions"
draft-ietf-mpls-tp-itu-t-identifiers-00, July 2011.
[MPLS-TP-OAM-FWK] Busi, I. and B. Niven-Jenkins, "MPLS-TP OAM [MPLS-TP-OAM-FWK] Busi, I. and B. Niven-Jenkins, "MPLS-TP OAM
Framework and Overview", 2009, Framework and Overview", 2009,
<draft-ietf-mpls-tp-oam-framework>. <draft-ietf-mpls-tp-oam-framework>.
12. Authors' Addresses 12. Authors' Addresses
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
UK UK
 End of changes. 101 change blocks. 
223 lines changed or deleted 239 lines changed or added

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