draft-ietf-mpls-tp-mib-management-overview-00.txt   draft-ietf-mpls-tp-mib-management-overview-01.txt 
Network Working Group A.Farrel Network Working Group D. King (Editor)
Internet-Draft D. King Internet-Draft Old Dog Consulting
Intended status: Informational Old Dog Consulting Intended status: Informational M. Venkatesan (Editor)
Expires: April 7, 2011 M.Venkatesan Expires: June 5, 2011 Aricent
Aricent January 5, 2011
J. Ryoo
ETRI
S. Mansfield
Ericsson
K. Koushik
Cisco Systems, Inc.
November 7, 2010
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-00.txt draft-ietf-mpls-tp-mib-management-overview-01.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 management architecture for This document describes the MIB-based management architecture for
MPLS-TP and indicates the interrelationships between the different MPLS-TP, indicates the interrelationships between different
MIB modules used for MPLS-TP network management. existing MIB modules that can be leveraged for MPLS-TP network
management and identifies areas where additional MIB modules would be
required.
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication (IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network as capabilities and functionalities of a packet transport network as
defined by the ITU-T. defined by the ITU-T.
This Informational Internet-Draft is aimed at achieving IETF This Informational Internet-Draft is aimed at achieving IETF
Consensus before publication as an RFC and will be subject to an IETF Consensus before publication as an RFC and will be subject to an IETF
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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 March 21, 2011. This Internet-Draft will expire on June 5, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction.................................................3 1. Introduction.................................................4
2. Terminology..................................................4 2. Terminology..................................................4
3. The SNMP Management Framework................................4 3. The SNMP Management Framework................................4
4. Summary of MPLS-TP Management Function.......................4 4. Summary of MPLS-TP Management Function.......................5
5. Overview of Existing Work....................................4 5. Overview of Existing Work....................................5
5.1. MPLS Management Overview and Requirements...............5 5.1. MPLS Management Overview and Requirements...............5
5.2. An Introduction to the MPLS and Pseudowire MIB Modules..5 5.2. An Introduction to the MPLS and Pseudowire MIB Modules..6
5.2.1. Structure of the MPLS MIB OID Tree...............5 5.2.1. Structure of the MPLS MIB OID Tree...............6
5.2.2. Textual Convention Modules.......................6 5.2.2. Textual Convention Modules.......................7
5.2.3. Mapping Data to LSPs.............................7 5.2.3. Mapping Data to LSPs.............................7
5.2.4. Label Switching Router Modules...................8 5.2.4. Label Switching Router Modules...................8
5.2.5. Label Switched Path Modules......................8 5.2.5. Label Switched Path Modules......................8
5.2.6. Pseudowire Modules...............................8 5.2.6. Pseudowire Modules...............................8
5.2.7. Routing and Traffic Engineering..................10 5.2.7. Routing and Traffic Engineering..................10
5.2.8. Resiliency.......................................10 5.2.8. Resiliency.......................................10
5.2.9. Fault Management and Performance Management......10 5.2.9. Fault Management and Performance Management......11
5.2.10. MIB Module Interdependencies....................11 5.2.10. MIB Module Interdependencies....................12
5.2.11. Dependencies on External MIB Modules............12 5.2.11. Dependencies on External MIB Modules............14
6. Applicability of MPLS MIB modules to MPLS-TP.................13 6. Applicability of MPLS MIB modules to MPLS-TP.................14
6.1 Gap Analysis............................................13 6.1 Gap Analysis............................................15
6.1.1 MPLS-TP Tunnel....................................13 6.1.1 MPLS-TP Tunnel....................................15
6.1.2 MPLS-TP Pseudowire................................13 6.1.2 MPLS-TP Pseudowire................................15
6.1.3 MPLS-TP Sections..................................13 6.1.3 MPLS-TP Sections..................................15
6.1.4 MPLS-TP OAM.......................................13 6.1.4 MPLS-TP OAM.......................................15
6.1.5 MPLS-TP Protection Switching......................14 6.1.5 MPLS-TP Protection Switching......................16
6.1.6 MIB Module Interdependencies......................15 7. Interfaces...................................................16
7. Interfaces...................................................17
7.1. MPLS Tunnels as Interfaces..............................17 7.1. MPLS Tunnels as Interfaces..............................17
7.2. Application of the Interfaces Group to TE Links.........17 7.2. Application of the Interfaces Group to TE Links.........17
7.3. References to Interface Objects from MPLS MIB Modules...17 7.3. References to Interface Objects from MPLS MIB Modules...17
8. Management Options...........................................18 8. Management Options...........................................17
9. Security Considerations......................................18 9. Security Considerations......................................18
10. IANA Considerations.........................................18 10. IANA Considerations.........................................18
11. Acknowledgements............................................18 11. Acknowledgements............................................18
12. Normative References........................................19 12. References..................................................18
13. Informational References....................................19 12.1. Normative References..................................18
14. Authors' Addresses..........................................20 12.2. Informational References..............................20
14. Authors' Addresses..........................................22
1. Introduction 1. Introduction
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 of 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, or the elective use of a Generalized MPLS (GMPLS)
control plane to support dynamic provisioning of transport paths. control plane to support dynamic provisioning of transport paths.
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 the existing MPLS-TP and indicates the interrelationships between different
MIB modules used for MPLS-TP network management. The document also existing MIB modules that should be leveraged for MPLS-TP network
indentifies areas where additional MIB modules would be required to management.
support an MPLS-TP network.
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication (IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network. capabilities and functionalities of a packet transport network.
2. Terminology 2. Terminology
This document also uses terminology from the MPLS architecture This document also uses terminology from the MPLS architecture
skipping to change at page 5, line 6 skipping to change at page 5, line 24
monitoring, and security management. monitoring, and security management.
5. Overview of Existing Work 5. Overview of Existing Work
This section describes the existing tools and techniques for This section describes the existing tools and techniques for
managing and modeling MPLS networks, devices, and protocols. It does managing and modeling MPLS networks, devices, and protocols. It does
not focus on MPLS-TP, but is intended to provide a description of the not focus on MPLS-TP, but is intended to provide a description of the
tool kit that is already available. tool kit that is already available.
The following section (Section 6. Applicability of MPLS MIB modules The following section (Section 6. Applicability of MPLS MIB modules
to MPLS-TP) of this document describes the applicability of the MPLS to MPLS-TP) of this document outlines the existing MPLS MIB modules
and optional use of GMPLS MIB modules to MPLS-TP and examines the and optional use of GMPLS MIB modules to MPLS-TP and examines the
additional MIB modules and objects that would be required for additional MIB modules and objects that would be required for
managing an MPLS-TP network. managing an MPLS-TP network.
5.1. MPLS Management Overview and Requirements 5.1. MPLS Management Overview and Requirements
[RFC4378] outlines how data plane protocols can assist in providing [RFC4378] outlines how data plane protocols can assist in providing
the Operations and Management (OAM) requirements outlined in the Operations and Management (OAM) requirements outlined in
[RFC4377] and how it is applied to the management functions of fault, [RFC4377] and how it is applied to the management functions of fault,
configuration, accounting, performance, and security (commonly known configuration, accounting, performance, and security (commonly known
skipping to change at page 6, line 52 skipping to change at page 7, line 10
| |
+- pwTDMMIB -- PW-TDM-MIB [RFC5604] +- pwTDMMIB -- PW-TDM-MIB [RFC5604]
| |
+- 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.
5.2.2. Textual Convention Modules 5.2.2. Textual Convention Modules
MPLS-TC-STD-MIB [RFC3811] contains the Textual Conventions for MPLS-TC-STD-MIB [RFC3811] and GMPLS-TC-STD-MIB [RFC4801] contains the
Multiprotocol Label Switching (MPLS) 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
networks. and GMPLS networks.
5.2.3. Mapping Data to LSPs 5.2.3. Mapping Data to LSPs
MPLS is a packet switching protocol that operates between the MPLS is a packet switching protocol that operates between the
Network layer and the data link layer in the OSI model. Network layer and the data link layer in the OSI model.
There is a clean separation between the control and forwarding There is a clean separation between the control and forwarding
planes in the MPLS protocol. This helps in easy portability and planes in the MPLS protocol. This helps in easy portability and
extensibility to the forwarding functions. extensibility to the forwarding functions.
skipping to change at page 7, line 31 skipping to change at page 7, line 41
The LSR forwarding plane then uses an index which is the incoming The LSR forwarding plane then uses an index which is the incoming
interface and label (usually of 20-bit length) to forward the interface and label (usually of 20-bit length) to forward the
packet. packet.
Each entry in this forwarding table corresponds to a forwarding Each entry in this forwarding table corresponds to a forwarding
equivalence class (FEC). This can be loosely defined as the set of equivalence class (FEC). This can be loosely defined as the set of
characteristics that are being shared by the packets which will be characteristics that are being shared by the packets which will be
forwarded in a similar fashion and may share the same label. forwarded in a similar fashion and may share the same label.
MPLS packets are encapsulated by one more more label entries MPLS packets are encapsulated by one more label entries referred to
referred to as the label stack. Each label stack entry consists of a as the label stack. Each label stack entry consists of a label, the
label, the 3 TC-bits for classifying the Traffic Class, the bottom of 3 TC-bits for classifying the Traffic Class, the bottom of stack bit,
stack bit, and TTL. and TTL.
The ingress and the egress devices of the MPLS network are called The ingress and the egress devices of the MPLS network are called
Label Edge routers. These routers "Push" an MPLS label into an Label Edge routers. These routers "Push" an MPLS label into an
incoming packet and "pop" off the MPLS label from an outgoing packet incoming packet and "pop" off the MPLS label from an outgoing packet
respectively. respectively.
At the ingress when an unlabeled packet enters, one or more label At the ingress when an unlabeled packet enters, one or more label
stack entries are (each label stack with one or more labels) is stack entries are (each label stack with one or more labels) is
prefixed to this packet based on its FEC as discussed above. In prefixed to this packet based on its FEC as discussed above. In
addition, the "MPLS-specific" L2 encapsulation (including, for addition, the "MPLS-specific" L2 encapsulation (including, for
skipping to change at page 8, line 17 skipping to change at page 8, line 26
remains the same. After the swap the packet is forwarded based on the remains the same. After the swap the packet is forwarded based on the
new entry. new entry.
5.2.4. Label Switching Router Modules 5.2.4. Label Switching Router Modules
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-TP is specific to the use of MPLS in transport networks. MPLS-TP is specific to the use of MPLS in transport networks.
According to [RFC5654] multipoint-to-point LSPs do not form part of According to [RFC5654] multipoint-to-point LSPs do not form part of
MPLS-TP, so multipoint-to-point cross connects are not configured in MPLS-TP, so multipoint-to-point cross-connects are out of scope for
this MIB module for use in MPLS-TP. this document.
5.2.5. Label Switched Path Modules 5.2.5. Label Switched Path Modules
The path taken through the MPLS domain by a packet is referred to as 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 a label switched path (LSP). It is possible that this path may not be
understood or completely stored in one LSR within the MPLS domain. understood or completely stored in one LSR within the MPLS domain.
MPLS-LSR-STD-MIB [RFC3813] defines the required objects for setting
up an LSP. It defines the conceptual object MPLS cross-connect that
is used to map incoming labels to outgoing labels on a MPLS enabled
interfaces. This is referenced by other MIB modules in order to refer
to an underlying MPLS LSP.
This label switched path can be programmed using a variety of This label switched path can be programmed using a variety of
mechanisms. These include manual programming and using a signalling mechanisms. These include manual programming and using a signalling
protocol. protocol.
RSVP-TE (Resource reservation protocol for Traffic Engineering) is RSVP-TE (Resource reservation protocol for Traffic Engineering) is
normally used for signalling LSPs used for Traffic Engineering. normally used for signalling LSPs used for Traffic Engineering.
5.2.6. Pseudowire Modules 5.2.6. Pseudowire Modules
The PW (Pseudowire) MIB modules architecture provides a layered The PW (Pseudowire) MIB modules architecture provides a layered
modular model into which any supported emulated service can be modular model into which any supported emulated service can be
connected to any supported packet switched network (PSN) type. This connected to any supported packet switched network (PSN) type.
specific MIB module provides the glue for mapping between the Emulated Service Layer, Generic PW Layer and PSN VC Layer constitute
emulated service onto the native PSN service. As such, the defining the different layers of the model. A combination of the MIB modules
of a PW emulated service requires the use of at least three types of belonging to each layer provides the glue for mapping the emulated
MIB modules. service onto the native PSN service. At least three MIB modules each
belonging to a different layer is required to define a PW emulated
service.
Starting from the emulated service, the first type is a service- Starting from the emulated Service Layer, the first is a
specific module, which is dependent on the emulated signal type. service-specific module that is dependent on the emulated signal
These modules are defined in other documents. type.
The second type is this module, the PW-STD-MIB module, which The second is the PW-STD-MIB module, which configures general
configures general parameters of the PW that are common to all types parameters of the PW that are common to all types of emulated
of emulated services and PSN types. services and PSN types.
The third type of module is a PSN-specific module. There is a The third is a PSN-specific module. There is a different module for
different module for each type of PSN. These modules associate the each type of PSN. These modules associate the PW with one or more
PW with one or more "tunnels" that carry the service over the PSN. "tunnels" that carry the service over the PSN. These modules are
These modules are defined in other documents. defined in other documents.
PW-STD-MIB [RFC5601] defines a MIB module that can be PW-STD-MIB [RFC5601] defines a MIB module that can be
used to manage pseudowire (PW) services for transmission over a used to manage pseudowire (PW) services for transmission over a
Packet Switched Network (PSN) [RFC3931] [RFC4447]. This MIB module Packet Switched Network (PSN) [RFC3931] [RFC4447]. This MIB module
provides generic management of PWs that is common to all types of provides generic management of PWs that is common to all types of
PSN and PW services defined by the IETF PWE3 Working Group. PSN and PW services defined by the IETF PWE3 Working Group.
PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire PW-MPLS-STD-MIB [RFC5602] describes a model for managing pseudowire
services for transmission over different flavors of MPLS tunnels. services for transmission over different flavors of MPLS tunnels.
The general PW MIB module [RFC5601] defines the parameters global to The general PW MIB module [RFC5601] defines the parameters global to
skipping to change at page 9, line 51 skipping to change at page 10, line 21
PW-TDM-MIB [RFC5604] describes a model for managing TDM pseudowires, PW-TDM-MIB [RFC5604] describes a model for managing TDM pseudowires,
i.e., TDM data encapsulated for transmission over a Packet Switched i.e., TDM data encapsulated for transmission over a Packet Switched
Network (PSN). The term TDM in this document is limited to the Network (PSN). The term TDM in this document is limited to the
scope of Plesiochronous Digital Hierarchy (PDH). It is currently scope of Plesiochronous Digital Hierarchy (PDH). It is currently
specified to carry any TDM Signals in either Structure Agnostic specified to carry any TDM Signals in either Structure Agnostic
Transport mode (E1, T1, E3, and T3) or in Structure Aware Transport mode (E1, T1, E3, and T3) or in Structure Aware
Transport mode (E1, T1, and NxDS0) as defined in the Pseudowire Transport mode (E1, T1, and NxDS0) as defined in the Pseudowire
Emulation Edge-to-Edge (PWE3) TDM Requirements document [RFC4197]. Emulation Edge-to-Edge (PWE3) TDM Requirements document [RFC4197].
The PW MIB modules architecture provides a layered modular model
into which any supported emulated service can be connected to any
supported PSN type. This specific MIB module provides the glue for
mapping between the emulated service onto the native PSN service. As
such, the defining of a PW emulated service requires the use of at
least three types of MIB modules.
5.2.7. Routing and Traffic Engineering 5.2.7. Routing and Traffic Engineering
In MPLS traffic engineering, its possible to specify explicit routes In MPLS traffic engineering, its possible to specify explicit routes
or choose routes based on QOS metrics in setting up a path such that or choose routes based on QOS metrics in setting up a path such that
some specific data can be routed around network hot spots. some specific data can be routed around network hot spots.
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
skipping to change at page 10, line 43 skipping to change at page 11, line 10
reroute functionality. reroute functionality.
MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] MPLS-FRR-ONE2ONE-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
contains objects that apply to one-to-one backup method. contains objects that apply to one-to-one backup method.
MPLS-FRR-FACILITY-STD-MIB [draft-ietf-mpls-fastreroute-mib-14] MPLS-FRR-FACILITY-STD-MIB [draft-ietf-mpls-fastreroute-mib-14]
contains objects that apply to facility backup method. contains objects that apply to facility backup method.
5.2.9. Fault Management and Performance Management 5.2.9. Fault Management and Performance Management
MPLS manages the LSP and Pseudowire faults through LSP ping MPLS manages the LSP and pseudowire faults through the use of LSP
[RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV ping [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for
[RFC5885] tools. VCCV [RFC5885] tools.
There is no MIB management model currently available for the above Current MPLS focuses on the in and/or out packet counters,
fault management tools. errored packets, discontinuity time.
There is no performance management tool currently available for MPLS. Some of the MPLS and Pseudowire performance tables used for
performance management are given below.
mplsTunnelPerfTable provides several counters (packets forwarded,
packets dropped because of errors) to measure the performance of
the MPLS tunnels.
mplsInterfacePerfTable provides performance information (incoming and
outgoing labels in use and lookup failures) on a per-interface basis.
mplsInSegmentPerfTable contains statistical information (total
packets received by the insegment, total errored packets received,
total packets discarded, discontinuity time) for incoming MPLS
segments to an LSR.
mplsOutSegmentPerfTable contains statistical information (total
packets received, total errored packets received, total packets
discarded, discontinuity time) for outgoing MPLS segments from an
LSR.
mplsFTNPerfTable contains performance information for the specified
interface and an FTN entry mapped to this interface.
mplsLdpEntityStatsTable and mplsLdpSessionStatsTable contain
statistical information (session attempts, errored packets,
notifications) about an LDP entity.
pwPerfCurrentTable, pwPerfIntervalTable, pwPerf1DayIntervalTable
provides pseudowire performance information (in and/or out packets)
based on time (current interval, each interval, 1day interval).
pwEnetStatsTable contains statistical counters specific for Ethernet
PW.
pwTDMPerfCurrentTable, pwTDMPerfIntervalTable and
pwTDMPerf1DayIntervalTable contain statistical informations
accumulated per 15-minute, 24 hour, 1 day respectively.
gmplsTunnelErrorTable and gmplsTunnelReversePerfTable provides
information about performance errored packets and in/out packet
counters.
5.2.10. MIB Module Interdependencies 5.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,
this section also highlights the GMPLS and PW MIB modules
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 <--------------------------------+ |
| | | | | |
skipping to change at page 12, line 35 skipping to change at page 14, line 24
IANA-GMPLS-TC-MIB. IANA-GMPLS-TC-MIB.
- GMPLS-LSR-STD-MIB contains references to objects in - GMPLS-LSR-STD-MIB contains references to objects in
GMPLS-LABEL-STD-MIB. GMPLS-LABEL-STD-MIB.
Note that there is a textual convention (MplsIndexType) defined in Note that there is a textual convention (MplsIndexType) defined in
MPLS-LSR-STD-MIB that is imported by MPLS-LDP-STD-MIB. MPLS-LSR-STD-MIB that is imported by MPLS-LDP-STD-MIB.
5.2.11. Dependencies on External MIB Modules 5.2.11. Dependencies on External MIB Modules
In addition to the MPLS management overview [RFC4221]
section 4.12 (Dependencies on External MIB Modules), some of the
existing MPLS MIBs, PW MIBs and GMPLS MIBs are re-used with
extensions for achieving the MPLS-TP functionality.
MPLS MIB modules have dependencies with the TE-LINK-STD-MIB MPLS MIB modules have dependencies with the TE-LINK-STD-MIB
for maintaining the traffic engineering information. for maintaining the traffic engineering information.
MPLS MIB modules depend on the CSPF module to get the paths for MPLS MPLS MIB modules depend on the CSPF module to get the paths for MPLS
tunnel to traverse to reach the end point of the tunnel and BFD tunnel to traverse to reach the end point of the tunnel and BFD
module to verify the data-plane failures of LSPs and PWs. module to verify the data-plane 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.
This is business as usual for a MIB module and is not discussed This is business as usual for a MIB module and is not discussed
further in this document. further in this document.
6. Applicability of MPLS MIB modules to MPLS-TP 6. Applicability of MPLS MIB modules to MPLS-TP
In addition to the MPLS management overview [RFC4221]
section 4.12 (Dependencies on External MIB Modules), some of the
existing MPLS MIBs, PW MIBs and GMPLS MIBs are re-used with
extensions for achieving the MPLS-TP functionality.
[RFC5951] specifies the requirements for the management of [RFC5951] specifies the requirements for the management of
equipment used in networks supporting an MPLS-TP. It also details the equipment 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 document explains how network elements and networks that MPLS-TP. The document explains how network elements and networks that
support MPLS-TP can be managed using solutions that satisfy the support 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 management and OAM is described in the MPLS-TP framework MPLS-TP management and OAM is described in the MPLS-TP framework
[RFC5950] document. [RFC5950] document.
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 Operations, Administration, and Maintenance (OAM) function. MPLS-TP
OAM is described in [MPLS-TP-OAM-FWK]. OAM is described in [MPLS-TP-OAM-FWK].
This section also provides the information about the extensions of [Editors note - A seperate draft will provide an MPLS-TP abstract
existing MPLS MIB modules for MPLS-TP and the new MPLS-TP MIB model and use a formal language to define the terminology, the
modules. information that must be retrieved and method for storing. The draft
will also list the new MPLS-TP MIB modules identified in this
document]
6.1 Gap Analysis 6.1 Gap Analysis
6.1.1 MPLS-TP Tunnel 6.1.1 MPLS-TP Tunnel
MPLS-TP tunnel table MPLSTP-STD-MIB is an extension of o An MPLS tunnel may not compatible for non-IP environments.
MPLS tunnel table [RFC3812] to support MPLS-TP requirements. i.e., the tunnel ingress and egress identifiers are not always
Tunnel identifiers are defined based on [MPLS-TP-IDENTIFIERS]. identified via an IP address, rather identification is achieved
using local numbers to operate in a non-IP environment.
o Next-hop IP address in MPLS XC table is not compatible for non-IP
environment.
o Bidirectional LSPs are not introduced until the GMPLS MIB modules,
tunnel table should be enhanced to provide static and signalling
corouted/associated bidirectional connectivity.
6.1.2 MPLS-TP Pseudowire 6.1.2 MPLS-TP Pseudowire
MPLS-TP Pseudowire table MPLSTP-STD-MIB is an extension of o MPLS pseudowire may not be compatible for non-IP environments.
Pseudowire table MPLS-PW-STD-MIB to support MPLS-TP requirements. i.e., pseudowire source and destination identifiers are not always
Pseudowire identifiers are defined based on [MPLS-TP-IDENTIFIERS]. identified via an IP address, rather identification is achieved
using local numbers to operate in a non-IP environment.
o Pseudowire mib modules should be enhanced to operate over
corouted/associated bi-directional tunnel.
o Pseudowire 129 FEC type-2 should be used in non-IP and IP
environments with the required changes.
6.1.3 MPLS-TP Sections 6.1.3 MPLS-TP Sections
This section needs to be updated with the section layer network There is no gap in the existing MPLS MIB modules as this MPLS-TP
managed objects based on the draft-ietf-mpls-tp-data-plane-04.txt section will be defined as the new term for MPLS-TP.
(Section 3.2.) draft.
6.1.4 MPLS-TP OAM 6.1.4 MPLS-TP OAM
MPLS-LSP-PING-STD-MIB describes managed objects used to model and MPLS manages the LSP and pseudowire faults through LSP ping
manage the MPLS LSP ping [RFC4379]. LSP ping is used for [RFC4379], VCCV [RFC5085], BFD for LSPs [RFC5884] and BFD for VCCV
connectivity verification and fault isolation in an MPLS LSPs. [RFC5885] tools.
PW-VCCV-STD-MIB describes managed objects used to model and manage
the VCCV [RFC5085]. VCCV used for end-to-end fault detection and
diagnostics for a Pseudowire.
BFD-MPLS-STD-MIB describes the managed objects for modeling the
BFD for MPLS LSPs [RFC5884]. BFD for LSPs used for detecting
MPLS LSP data plane failures.
BFD-PW-VCCV-STD-MIB describes the managed objects for modeling
the BFD for Pseudowires [RFC5885]. BFD for Pseudowires used for
detecting data plane failures.
MPLS-LSP-PING-STD-MIB, PW-VCCV-STD-MIB, BFD-MPLS-STD-MIB and
BFD-PW-VCCV-STD-MIB are newly defined for MPLS. The new MPLS-TP
managed objects for LSP ping and BFD are based on
draft-ietf-mpls-tp-lsp-ping-bfd-procedures-00.
All MPLS-TP managed for OAM is defined in the MPLSTP-OAM-STD-MIB.
MPLSTP-TC-STD-MIB describes the textual conventions used for MPLS-TP.
MPLSTP-STD-MIB describes managed objects used to model and manage
the new extensions for LSPs, section and Pseudowires for IP and
non-IP packet based MPLS-TP transport networks.
The following MPLS-TP OAM functionalities can be achieved using the
MPLSTP-OAM-STD-MIB mib extensions:
o Continuity Check and Connectivity Verification,
o Alarm Reporting, Diagnostic,
o Route Tracing,
o Loopback tool,
o Lock Instruct,
o Lock Reporting Remote Defect Indication,
o Client Failure Indication,
o Packet Loss Measurement and
o Packet Delay Measurement
MPLS-TP OAM managed objects are defined based on the drafts: There is no MIB management model currently available for the above
fault management tools.
o draft-ietf-mpls-tp-oam-requirements-06, There is no performance management tool currently available for MPLS
o draft-ietf-mpls-tp-oam-framework-06 and except the statistics information.
o draft-ietf-mpls-tp-identifiers-01
6.1.5 MPLS-TP Protection Switching 6.1.5 MPLS-TP Protection Switching
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. An MPLS-TP protection facility for a working or primary facility. An MPLS-TP protection
switching can be managed with the following parameters: switching can be managed with the following parameters:
o Topology (linear, ring, mesh) o Topology (linear, ring, mesh)
skipping to change at page 15, line 23 skipping to change at page 16, line 37
o Timer values (hold-off, Wait-to-Restore) o Timer values (hold-off, Wait-to-Restore)
o Failure of protocol o Failure of protocol
Among those parameters for protection switching, the topology on Among those parameters for protection switching, the topology on
that a protection switching applies has the most significant that a protection switching applies has the most significant
influence on the other parameters. Besides, the mechanism of a influence on the other parameters. Besides, the mechanism of a
particular protection switching heavily depends on its topology. particular protection switching heavily depends on its topology.
Therefore, three MIB modules are to be defined to model and Therefore, three MIB modules are to be defined to model and
manage each of three different topologies protection switching. manage each of three different topologies protection switching.
MPLSTP-LPS-STD-MIB describes managed objects used to model and
manage the linear protection switching.
MPLSTP-RPS-STD-MIB describes managed objects used to model and
manage the ring protection switching.
MPLSTP-MPS-STD-MIB describes managed objects used to model and
manage the mesh protection switching.
6.1.6 MIB Module Interdependencies
This section provides an overview of the relationship between
the MPLS-TP MIB modules. More details of these relationships
are given below.
The arrows in the following diagram show a 'depends on'
relationship. A relationship "MIB module A depends on MIB module
B" means that MIB module A uses an object, object identifier, or
textual convention defined in MIB module B, or that MIB module A
contains a pointer (index or RowPointer) to an object in MIB
module B.
+-------------->MPLSTP-TC-STD-MIB <--------------------------+
| |
| MPLS-TE-STD-MIB PW-STD-MIB |
| ^ ^ |
| | | |
+<----------- MPLSTP-STD-MIB <-------------------------------+
| ^ |
| | +---------> MPLS-LSP-PING-STD-MIB |
| | ^ ^ ^ |
| | | | | |
| | | PW-VCCV-STD-MIB | |
| | | ^ ^ | |
| | | | | | |
| | BFD-MPLS-STD-MIB | | |
| | ^ +----------+ | |
| | | ^ | |
| | | | | |
+<----------- MPLSTP-OAM-STD-MIB ------------->+ |
^ |
| |
+- MPLSTP-LPS-STD-MIB -------------------->+
| |
+- MPLSTP-RPS-STD-MIB -------------------->+
| |
+- MPLSTP-MPS-STD-MIB -------------------->+
Thus:
- All the MPLS-TP MIB modules depend on MPLSTP-TC-STD-MIB.
- MPLSTP-OAM-STD-MIB and MPLSTP-PS-STD-MIB contain references to
objects in MPLSTP-STD-MIB.
- MPLSTP-PS-STD-MIB contains references to objects in
MPLSTP-OAM-STD-MIB.
- MPLSTP-STD-MIB contains references to objects in
MPLS-TE-STD-MIB and PW-STD-MIB.
- MPLSTP-OAM-STD-MIB contains references to objects in
MPLS-LSP-PING-STD-MIB, and
PW-VCCV-STD-MIB and BFD-MPLS-STD-MIB.
- BFD-MPLS-STD-MIB contains references to objects in
MPLS-LSP-PING-STD-MIB and PW-VCCV-STD-MIB.
- PW-VCCV-STD-MIB contains references to objects in
MPLS-LSP-PING-STD-MIB.
7. Interfaces 7. Interfaces
MPLS-TP can be carried over the existing and evolving physical MPLS-TP can be carried over the existing and evolving physical
transport technologies such as SONET/SDH, OTN/WDM, and Ethernet. transport technologies such as SONET/SDH, OTN/WDM, and Ethernet.
The Interfaces Group of IF-MIB [RFC2863] defines generic managed The Interfaces Group of IF-MIB [RFC2863] defines generic managed
objects for managing interfaces. The MPLS-TP MIB modules make objects for managing interfaces. The MPLS-TP MIB modules make
references to interfaces so that it can be clearly determined where references to interfaces so that it can be clearly determined where
the procedures managed by the MIB modules should be performed. the procedures managed by the MIB modules should be performed.
Additionally, the MPLS-TP MIB modules (notably MPLS-TE-STD-MIB and Additionally, the MPLS-TP MIB modules (notably MPLS-TE-STD-MIB and
TE-LINK-STD-MIB, PW-STD-MIB) utilize interface stacking within the TE-LINK-STD-MIB, PW-STD-MIB) utilize interface stacking within the
Interface Group. Interface Group.
Please refer to section 4. (Node and Interface Identifiers) in Please refer to section 4. (Node and Interface Identifiers) in
[MPLS-TP-IDENTIFIERS] for more information on MPLS-TP specific [MPLS-TP-IDENTIFIERS] for more information on MPLS-TP specific
interfaces. interfaces.
7.1. MPLS Tunnels as Interfaces 7.1. MPLS Tunnels as Interfaces
mplstpTunnelTable is extended from mplsTunnelTable for achieving the An extension to mplsTunnelTable should address the tunnel
MPLS-TP tunnel requirements. requirements specific to MPLS-TP.
MPLS Tunnel logical interfaces can be stacked over MPLS Tunnel logical interfaces can be stacked over
PDH/SDH/OTH/Ethernet physical interfaces. For more information on PDH/SDH/OTH/Ethernet physical interfaces. For more information on
Tunnel interfaces, refer section 11.1 (MPLS Tunnels as Interfaces) of Tunnel interfaces, refer section 11.1 (MPLS Tunnels as Interfaces) of
RFC-4221. RFC-4221.
7.2. Application of the Interfaces Group to TE Links 7.2. Application of the Interfaces Group to TE Links
TE links can be formed over PDH/SDH/OTH/Ethernet physical interfaces. TE links can be formed over PDH/SDH/OTH/Ethernet physical interfaces.
For more information on TE links, Refer section 11.2. Application of For more information on TE links, Refer section 11.2. Application of
skipping to change at page 18, line 52 skipping to change at page 18, line 38
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.
10. IANA Considerations 10. IANA Considerations
This document makes no requests for IANA action. This document makes no requests for IANA action.
11. Acknowledgements 11. Acknowledgements
The authors would like to thank Eric Gray, Thomas Nadeau and Benjamin The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin
Niven-Jenkins for their valuable comments. Niven-Jenkins, Sam Aldrin and Anirban Karmakar for their valuable
comments.
12. References 12. References
12.1 Normative References 12.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 22, line 44 skipping to change at page 22, line 39
UK UK
Email: daniel@olddog.co.uk Email: daniel@olddog.co.uk
Venkatesan Mahalingam Venkatesan Mahalingam
Aricent Aricent
India India
Email: venkatesan.mahalingam@aricent.com Email: venkatesan.mahalingam@aricent.com
Scott Mansfield Scott Mansfield
Ericsson Ericsson
300 Holger Way 300 Holger Way, San Jose, CA 95134, US
San Jose, CA 95134
US
Phone: +1 724 931 9316 Phone: +1 724 931 9316
Email: scott.mansfield@ericsson.com Email: scott.mansfield@ericsson.com
Jeong-dong Ryoo Jeong-dong Ryoo
ETRI ETRI
161 Gajeong, Yuseong, Daejeon, 305-700, South Korea 161 Gajeong, Yuseong, Daejeon, 305-700, South Korea
Phone: +82 42 860 5384 Phone: +82 42 860 5384
Email: ryoo@etri.re.kr Email: ryoo@etri.re.kr
A S Kiran Koushik A S Kiran Koushik
Cisco Systems Inc. Cisco Systems Inc.
Email: kkoushik@cisco.com Email: kkoushik@cisco.com
A. Karmakar
Cisco Systems Inc.
Email: akarmaka@cisco.com
 End of changes. 42 change blocks. 
221 lines changed or deleted 163 lines changed or added

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