| 1 |
<pre>Internet Engineering Task Force (IETF) D. King, Ed. |
| 2 |
Request for Comments: 6639 Old Dog Consulting |
| 3 |
Category: Informational M. Venkatesan, Ed. |
| 4 |
ISSN: 2070-1721 Aricent |
| 5 |
June 2012 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">Multiprotocol Label Switching Transport Profile (MPLS-TP)</span> |
| 9 |
<span class="h1">MIB-Based Management Overview</span> |
| 10 |
|
| 11 |
Abstract |
| 12 |
|
| 13 |
A range of Management Information Base (MIB) modules has been |
| 14 |
developed to help model and manage the various aspects of |
| 15 |
Multiprotocol Label Switching (MPLS) networks. These MIB modules are |
| 16 |
defined in separate documents that focus on the specific areas of |
| 17 |
responsibility of the modules that they describe. |
| 18 |
|
| 19 |
The MPLS Transport Profile (MPLS-TP) is a profile of MPLS |
| 20 |
functionality specific to the construction of packet-switched |
| 21 |
transport networks. |
| 22 |
|
| 23 |
This document describes the MIB-based architecture for MPLS-TP, |
| 24 |
indicates the interrelationships between different existing MIB |
| 25 |
modules that can be leveraged for MPLS-TP network management, and |
| 26 |
identifies areas where additional MIB modules are required. |
| 27 |
|
| 28 |
Status of This Memo |
| 29 |
|
| 30 |
This document is not an Internet Standards Track specification; it is |
| 31 |
published for informational purposes. |
| 32 |
|
| 33 |
This document is a product of the Internet Engineering Task Force |
| 34 |
(IETF). It represents the consensus of the IETF community. It has |
| 35 |
received public review and has been approved for publication by the |
| 36 |
Internet Engineering Steering Group (IESG). Not all documents |
| 37 |
approved by the IESG are a candidate for any level of Internet |
| 38 |
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 39 |
|
| 40 |
Information about the current status of this document, any errata, |
| 41 |
and how to provide feedback on it may be obtained at |
| 42 |
<a href="http://www.rfc-editor.org/info/rfc6639">http://www.rfc-editor.org/info/rfc6639</a>. |
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">King & Venkatesan Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2012 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
|
| 73 |
|
| 74 |
|
| 75 |
|
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
|
| 80 |
|
| 81 |
|
| 82 |
|
| 83 |
|
| 84 |
|
| 85 |
|
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">King & Venkatesan Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a> |
| 116 |
<a href="#section-1.1">1.1</a>. MPLS-TP Management Function ................................<a href="#page-5">5</a> |
| 117 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-5">5</a> |
| 118 |
<a href="#section-3">3</a>. The SNMP Management Framework ...................................<a href="#page-5">5</a> |
| 119 |
<a href="#section-4">4</a>. Overview of Existing Work .......................................<a href="#page-6">6</a> |
| 120 |
<a href="#section-4.1">4.1</a>. MPLS Management Overview and Requirements ..................<a href="#page-6">6</a> |
| 121 |
<a href="#section-4.2">4.2</a>. An Introduction to the MPLS and Pseudowire MIB Modules .....<a href="#page-6">6</a> |
| 122 |
<a href="#section-4.2.1">4.2.1</a>. Structure of the MPLS MIB OID Tree ..................<a href="#page-6">6</a> |
| 123 |
<a href="#section-4.2.2">4.2.2</a>. Textual Convention Modules ..........................<a href="#page-8">8</a> |
| 124 |
<a href="#section-4.2.3">4.2.3</a>. Label Switched Path (LSP) Modules ...................<a href="#page-8">8</a> |
| 125 |
<a href="#section-4.2.4">4.2.4</a>. Label Edge Router (LER) Modules .....................<a href="#page-8">8</a> |
| 126 |
<a href="#section-4.2.5">4.2.5</a>. Label Switching Router (LSR) Modules ................<a href="#page-9">9</a> |
| 127 |
<a href="#section-4.2.6">4.2.6</a>. Pseudowire Modules ..................................<a href="#page-9">9</a> |
| 128 |
<a href="#section-4.2.7">4.2.7</a>. Routing and Traffic Engineering ....................<a href="#page-10">10</a> |
| 129 |
<a href="#section-4.2.8">4.2.8</a>. Resiliency .........................................<a href="#page-11">11</a> |
| 130 |
<a href="#section-4.2.9">4.2.9</a>. Fault Management and Performance Management ........<a href="#page-11">11</a> |
| 131 |
<a href="#section-4.2.10">4.2.10</a>. MIB Module Interdependencies ......................<a href="#page-13">13</a> |
| 132 |
<a href="#section-4.2.11">4.2.11</a>. Dependencies on External MIB Modules ..............<a href="#page-15">15</a> |
| 133 |
<a href="#section-5">5</a>. Applicability of MPLS MIB Modules to MPLS-TP ...................<a href="#page-16">16</a> |
| 134 |
<a href="#section-5.1">5.1</a>. MPLS-TP Tunnel ............................................<a href="#page-17">17</a> |
| 135 |
<a href="#section-5.1.1">5.1.1</a>. Gap Analysis .......................................<a href="#page-17">17</a> |
| 136 |
<a href="#section-5.1.2">5.1.2</a>. Recommendations ....................................<a href="#page-17">17</a> |
| 137 |
<a href="#section-5.2">5.2</a>. MPLS-TP Pseudowire ........................................<a href="#page-17">17</a> |
| 138 |
<a href="#section-5.2.1">5.2.1</a>. Gap Analysis .......................................<a href="#page-17">17</a> |
| 139 |
<a href="#section-5.2.2">5.2.2</a>. Recommendations ....................................<a href="#page-18">18</a> |
| 140 |
<a href="#section-5.3">5.3</a>. MPLS-TP Sections ..........................................<a href="#page-18">18</a> |
| 141 |
<a href="#section-5.3.1">5.3.1</a>. Gap Analysis .......................................<a href="#page-18">18</a> |
| 142 |
<a href="#section-5.3.2">5.3.2</a>. Recommendations ....................................<a href="#page-18">18</a> |
| 143 |
<a href="#section-5.4">5.4</a>. MPLS-TP OAM ...............................................<a href="#page-18">18</a> |
| 144 |
<a href="#section-5.4.1">5.4.1</a>. Gap Analysis .......................................<a href="#page-18">18</a> |
| 145 |
<a href="#section-5.4.2">5.4.2</a>. Recommendations ....................................<a href="#page-19">19</a> |
| 146 |
<a href="#section-5.5">5.5</a>. MPLS-TP Protection Switching and Recovery .................<a href="#page-19">19</a> |
| 147 |
<a href="#section-5.5.1">5.5.1</a>. Gap Analysis .......................................<a href="#page-19">19</a> |
| 148 |
<a href="#section-5.5.2">5.5.2</a>. Recommendations ....................................<a href="#page-19">19</a> |
| 149 |
<a href="#section-5.6">5.6</a>. MPLS-TP Interfaces ........................................<a href="#page-19">19</a> |
| 150 |
<a href="#section-5.6.1">5.6.1</a>. Gap Analysis .......................................<a href="#page-19">19</a> |
| 151 |
<a href="#section-5.6.2">5.6.2</a>. Recommendations ....................................<a href="#page-19">19</a> |
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">King & Venkatesan Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 167 |
|
| 168 |
|
| 169 |
<a href="#section-6">6</a>. An Introduction to the MPLS-TP MIB Modules .....................<a href="#page-20">20</a> |
| 170 |
<a href="#section-6.1">6.1</a>. MPLS-TP MIB Modules .......................................<a href="#page-20">20</a> |
| 171 |
<a href="#section-6.1.1">6.1.1</a>. New MIB Modules for MPLS-TP ........................<a href="#page-20">20</a> |
| 172 |
<a href="#section-6.1.2">6.1.2</a>. Textual Conventions for MPLS-TP ....................<a href="#page-20">20</a> |
| 173 |
<a href="#section-6.1.3">6.1.3</a>. Identifiers for MPLS-TP ............................<a href="#page-21">21</a> |
| 174 |
<a href="#section-6.1.4">6.1.4</a>. LSR MIB Extensions for MPLS-TP .....................<a href="#page-21">21</a> |
| 175 |
<a href="#section-6.1.5">6.1.5</a>. Tunnel Extensions for MPLS-TP ......................<a href="#page-21">21</a> |
| 176 |
<a href="#section-6.2">6.2</a>. PWE3 MIB Modules for MPLS-TP ..............................<a href="#page-21">21</a> |
| 177 |
<a href="#section-6.2.1">6.2.1</a>. New MIB Modules for MPLS-TP Pseudowires ............<a href="#page-21">21</a> |
| 178 |
<a href="#section-6.2.2">6.2.2</a>. Pseudowire Textual Conventions for MPLS-TP .........<a href="#page-21">21</a> |
| 179 |
<a href="#section-6.2.3">6.2.3</a>. Pseudowire Extensions for MPLS-TP ..................<a href="#page-22">22</a> |
| 180 |
<a href="#section-6.2.4">6.2.4</a>. Pseudowire MPLS Extensions for MPLS-TP .............<a href="#page-22">22</a> |
| 181 |
<a href="#section-6.3">6.3</a>. OAM MIB Modules for MPLS-TP ...............................<a href="#page-22">22</a> |
| 182 |
<a href="#section-6.3.1">6.3.1</a>. New MIB Modules for OAM for MPLS-TP ................<a href="#page-22">22</a> |
| 183 |
<a href="#section-6.3.2">6.3.2</a>. BFD MIB Module .....................................<a href="#page-22">22</a> |
| 184 |
<a href="#section-6.3.3">6.3.3</a>. OAM MIB Module .....................................<a href="#page-23">23</a> |
| 185 |
6.4. Protection Switching and Recovery MIB Modules for MPLS-TP .23 |
| 186 |
6.4.1. New MIB Modules for MPLS Protection |
| 187 |
Switching and Recovery .............................<a href="#page-23">23</a> |
| 188 |
<a href="#section-6.4.2">6.4.2</a>. Linear Protection Switching MIB Module .............<a href="#page-23">23</a> |
| 189 |
<a href="#section-6.4.3">6.4.3</a>. Ring Protection Switching MIB Module ...............<a href="#page-23">23</a> |
| 190 |
<a href="#section-6.4.4">6.4.4</a>. Mesh Protection Switching MIB Module ...............<a href="#page-23">23</a> |
| 191 |
<a href="#section-7">7</a>. Management Options .............................................<a href="#page-23">23</a> |
| 192 |
<a href="#section-8">8</a>. Security Considerations ........................................<a href="#page-24">24</a> |
| 193 |
<a href="#section-9">9</a>. IANA Considerations ............................................<a href="#page-24">24</a> |
| 194 |
<a href="#section-10">10</a>. Acknowledgements ..............................................<a href="#page-24">24</a> |
| 195 |
<a href="#section-11">11</a>. Contributors' Addresses .......................................<a href="#page-25">25</a> |
| 196 |
<a href="#section-12">12</a>. References ....................................................<a href="#page-26">26</a> |
| 197 |
<a href="#section-12.1">12.1</a>. Normative References .....................................<a href="#page-26">26</a> |
| 198 |
<a href="#section-12.2">12.2</a>. Informative References ...................................<a href="#page-27">27</a> |
| 199 |
|
| 200 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 201 |
|
| 202 |
The MPLS Transport Profile (MPLS-TP) is a packet transport technology |
| 203 |
based on a profile of the MPLS functionality specific to the |
| 204 |
construction of packet-switched transport networks. MPLS is |
| 205 |
described in [<a href="./rfc3031" title=""Multiprotocol Label Switching Architecture"">RFC3031</a>], and requirements for MPLS-TP are specified in |
| 206 |
[<a href="./rfc5654" title=""Requirements of an MPLS Transport Profile"">RFC5654</a>]. |
| 207 |
|
| 208 |
A range of Management Information Base (MIB) modules has been |
| 209 |
developed to help model and manage the various aspects of |
| 210 |
Multiprotocol Label Switching (MPLS) networks. These MIB modules are |
| 211 |
defined in separate documents that focus on the specific areas of |
| 212 |
responsibility for the modules that they describe. |
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">King & Venkatesan Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 223 |
|
| 224 |
|
| 225 |
An MPLS-TP network can be operated via static provisioning of |
| 226 |
transport paths, Label Switched Paths (LSPs) and pseudowires (PWs), |
| 227 |
or the elective use of a Generalized MPLS (GMPLS) control plane to |
| 228 |
support dynamic provisioning of transport paths, LSPs, and PWs. |
| 229 |
|
| 230 |
This document describes the MIB-based management architecture for |
| 231 |
MPLS, as extended for MPLS-TP. The document also indicates the |
| 232 |
interrelationships between existing MIB modules that should be |
| 233 |
leveraged for MPLS-TP network management and identifies areas where |
| 234 |
additional MIB modules are required. |
| 235 |
|
| 236 |
Note that [<a href="./rfc5951" title=""Network Management Requirements for MPLS-based Transport Networks"">RFC5951</a>] does not specify a preferred management interface |
| 237 |
protocol to be used as the standard protocol for managing MPLS-TP |
| 238 |
networks. |
| 239 |
|
| 240 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. MPLS-TP Management Function</span> |
| 241 |
|
| 242 |
The management of the MPLS-TP networks is separable from that of its |
| 243 |
client networks so that the same means of management can be used |
| 244 |
regardless of the client. The management function of MPLS-TP |
| 245 |
includes fault management, configuration management, performance |
| 246 |
monitoring, and security management. |
| 247 |
|
| 248 |
The purpose of the management function is to provide control and |
| 249 |
monitoring of the MPLS transport profile protocol mechanisms and |
| 250 |
procedures. The requirements for the network management |
| 251 |
functionality are found in [<a href="./rfc5951" title=""Network Management Requirements for MPLS-based Transport Networks"">RFC5951</a>]. A description of the network |
| 252 |
and element management architectures that can be applied to the |
| 253 |
management of MPLS-based transport networks is found in [<a href="./rfc5950" title=""Network Management Framework for MPLS-based Transport Networks"">RFC5950</a>]. |
| 254 |
|
| 255 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 256 |
|
| 257 |
This document also uses terminology from the MPLS architecture |
| 258 |
document [<a href="./rfc3031" title=""Multiprotocol Label Switching Architecture"">RFC3031</a>], Pseudowire Emulation Edge-to-Edge (PWE3) |
| 259 |
architecture [<a href="./rfc3985" title=""Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture"">RFC3985</a>], and the following MPLS-related MIB modules: |
| 260 |
the MPLS-TC-STD-MIB [<a href="./rfc3811" title=""Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management"">RFC3811</a>], MPLS-LSR-STD-MIB [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>], |
| 261 |
MPLS-TE-STD-MIB [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>], MPLS-LDP-STD-MIB [<a href="./rfc3815" title=""Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)"">RFC3815</a>], |
| 262 |
MPLS-FTN-STD-MIB [<a href="./rfc3814" title=""Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)"">RFC3814</a>], and TE-LINK-STD-MIB [<a href="./rfc4220" title=""Traffic Engineering Link Management Information Base"">RFC4220</a>]. |
| 263 |
|
| 264 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The SNMP Management Framework</span> |
| 265 |
|
| 266 |
Managed objects are accessed via a virtual information store, termed |
| 267 |
the Management Information Base or MIB. MIB objects are generally |
| 268 |
accessed through the Simple Network Management Protocol (SNMP). |
| 269 |
|
| 270 |
Objects in the MIB are defined using the mechanisms defined in the |
| 271 |
Structure of Management Information (SMI). |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">King & Venkatesan Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 279 |
|
| 280 |
|
| 281 |
For a detailed overview of the documents that describe the current |
| 282 |
Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">Section 7 of |
| 283 |
[RFC3410]</a>. |
| 284 |
|
| 285 |
This document discusses MIB modules that are compliant to the SMIv2, |
| 286 |
which is described in [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>], [<a href="./rfc2579" title=""Textual Conventions for SMIv2"">RFC2579</a>], and [<a href="./rfc2580" title=""Conformance Statements for SMIv2"">RFC2580</a>]. |
| 287 |
|
| 288 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Overview of Existing Work</span> |
| 289 |
|
| 290 |
This section describes the existing tools and techniques for managing |
| 291 |
and modeling MPLS networks, devices, and protocols. It is intended |
| 292 |
to provide a description of the tool kit that is already available. |
| 293 |
|
| 294 |
<a href="#section-5">Section 5</a> of this document outlines the applicability of existing |
| 295 |
MPLS MIB modules to MPLS-TP, describes the optional use of GMPLS MIB |
| 296 |
modules in MPLS-TP networks, and examines the additional MIB modules |
| 297 |
and objects that would be required for managing an MPLS-TP network. |
| 298 |
|
| 299 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. MPLS Management Overview and Requirements</span> |
| 300 |
|
| 301 |
[<a id="ref-RFC4378">RFC4378</a>] outlines how data-plane protocols can assist in providing |
| 302 |
the Operations, Administration, and Maintenance (OAM) requirements |
| 303 |
outlined in [<a href="./rfc4377" title=""Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks"">RFC4377</a>] and how it is applied to the management |
| 304 |
functions of fault, configuration, accounting, performance, and |
| 305 |
security (commonly known as FCAPS) for MPLS networks. |
| 306 |
|
| 307 |
[<a id="ref-RFC4221">RFC4221</a>] describes the management architecture for MPLS. In |
| 308 |
particular, it describes how the managed objects defined in various |
| 309 |
MPLS-related MIB modules model different aspects of MPLS, as well as |
| 310 |
the interactions and dependencies between each of these MIB modules. |
| 311 |
|
| 312 |
[<a id="ref-RFC4377">RFC4377</a>] describes the requirements for user- and data-plane OAM and |
| 313 |
applications for MPLS. |
| 314 |
|
| 315 |
[<a id="ref-RFC5654">RFC5654</a>] describes the requirements for the optional use of a |
| 316 |
control plane to support dynamic provisioning of MPLS-TP transport |
| 317 |
paths. The MPLS-TP LSP control plane is based on GMPLS and is |
| 318 |
described in [<a href="./rfc3945" title=""Generalized Multi-Protocol Label Switching (GMPLS) Architecture"">RFC3945</a>]. |
| 319 |
|
| 320 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. An Introduction to the MPLS and Pseudowire MIB Modules</span> |
| 321 |
|
| 322 |
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. Structure of the MPLS MIB OID Tree</span> |
| 323 |
|
| 324 |
The MPLS MIB Object Identifier (OID) tree has the following |
| 325 |
structure. It is based on the tree originally set out in <a href="./rfc4221#section-4.1">Section 4.1 |
| 326 |
of [RFC4221]</a> and has been enhanced to include other relevant MIB |
| 327 |
modules. |
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">King & Venkatesan Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 335 |
|
| 336 |
|
| 337 |
mib-2 -- <a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>] |
| 338 |
| |
| 339 |
+-transmission |
| 340 |
| | |
| 341 |
| +- mplsStdMIB |
| 342 |
| | | |
| 343 |
| | +- mplsTCStdMIB -- MPLS-TC-STD-MIB [<a href="./rfc3811" title=""Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management"">RFC3811</a>] |
| 344 |
| | | |
| 345 |
| | +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>] |
| 346 |
| | | |
| 347 |
| | +- mplsTeStdMIB -- MPLS-TE-STD-MIB [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>] |
| 348 |
| | | |
| 349 |
| | +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB [<a href="./rfc3815" title=""Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)"">RFC3815</a>] |
| 350 |
| | | |
| 351 |
| | +- mplsLdpGenericStdMIB |
| 352 |
| | | -- MPLS-LDP-GENERIC-STD-MIB [<a href="./rfc3815" title=""Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)"">RFC3815</a>] |
| 353 |
| | | |
| 354 |
| | +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB [<a href="./rfc3814" title=""Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)"">RFC3814</a>] |
| 355 |
| | | |
| 356 |
| | +- gmplsTCStdMIB -- GMPLS-TC-STD-MIB [<a href="./rfc4801" title=""Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management"">RFC4801</a>] |
| 357 |
| | | |
| 358 |
| | +- gmplsTeStdMIB -- GMPLS-TE-STD-MIB [<a href="./rfc4802" title=""Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base"">RFC4802</a>] |
| 359 |
| | | |
| 360 |
| | +- gmplsLsrStdMIB -- GMPLS-LSR-STD-MIB [<a href="./rfc4803" title=""Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base"">RFC4803</a>] |
| 361 |
| | | |
| 362 |
| | +- gmplsLabelStdMIB -- GMPLS-LABEL-STD-MIB [<a href="./rfc4803" title=""Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base"">RFC4803</a>] |
| 363 |
| | |
| 364 |
| +- teLinkStdMIB -- TE-LINK-STD-MIB [<a href="./rfc4220" title=""Traffic Engineering Link Management Information Base"">RFC4220</a>] |
| 365 |
| | |
| 366 |
| +- pwStdMIB -- PW-STD-MIB [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>] |
| 367 |
| |
| 368 |
+- ianaGmpls -- IANA-GMPLS-TC-MIB [<a href="./rfc4802" title=""Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base"">RFC4802</a>] |
| 369 |
| |
| 370 |
+- ianaPwe3MIB -- IANA-PWE3-MIB [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>] |
| 371 |
| |
| 372 |
+- pwEnetStdMIB -- PW-ENET-STD-MIB [<a href="./rfc5603" title=""Ethernet Pseudowire (PW) Management Information Base (MIB)"">RFC5603</a>] |
| 373 |
| |
| 374 |
+- pwMplsStdMIB -- PW-MPLS-STD-MIB [<a href="./rfc5602" title=""Pseudowire (PW) over MPLS PSN Management Information Base (MIB)"">RFC5602</a>] |
| 375 |
| |
| 376 |
+- pwTDMMIB -- PW-TDM-MIB [<a href="./rfc5604" title=""Managed Objects for Time Division Multiplexing (TDM) over Packet Switched Networks (PSNs)"">RFC5604</a>] |
| 377 |
| |
| 378 |
+- pwTcStdMIB -- PW-TC-STD-MIB [<a href="./rfc5542" title=""Definitions of Textual Conventions for Pseudowire (PW) Management"">RFC5542</a>] |
| 379 |
|
| 380 |
Note: The OIDs for MIB modules are assigned and managed by IANA. |
| 381 |
They can be found in the referenced MIB documents. |
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">King & Venkatesan Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Textual Convention Modules</span> |
| 394 |
|
| 395 |
The MPLS-TC-STD-MIB [<a href="./rfc3811" title=""Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management"">RFC3811</a>], GMPLS-TC-STD-MIB [<a href="./rfc4801" title=""Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management"">RFC4801</a>], |
| 396 |
IANA-GMPLS-TC-MIB [<a href="./rfc4802" title=""Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base"">RFC4802</a>], and PW-TC-STD-MIB [<a href="./rfc5542" title=""Definitions of Textual Conventions for Pseudowire (PW) Management"">RFC5542</a>] contain the |
| 397 |
Textual Conventions for MPLS and GMPLS networks. These Textual |
| 398 |
Conventions should be imported by MIB modules that manage MPLS and |
| 399 |
GMPLS networks. <a href="#section-4.2.11">Section 4.2.11</a> highlights dependencies on additional |
| 400 |
external MIB modules. |
| 401 |
|
| 402 |
<span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>. Label Switched Path (LSP) Modules</span> |
| 403 |
|
| 404 |
An LSP is a path over which a labeled packet travels across the |
| 405 |
sequence of Label Switching Routers (LSRs) for a given Forward |
| 406 |
Equivalence Class (FEC). When a packet, with or without a label, |
| 407 |
arrives at an ingress Label Edge Router (LER) of an LSP, it is |
| 408 |
encapsulated with the label corresponding to the FEC and sent across |
| 409 |
the LSP. The labeled packet traverses the LSRs and arrives at the |
| 410 |
egress LER of the LSP, where it gets forwarded, depending on the |
| 411 |
packet type it came with. LSPs could be nested using label stacking, |
| 412 |
such that an LSP could traverse another LSP. A more detailed |
| 413 |
description of an LSP can be found in [<a href="./rfc3031" title=""Multiprotocol Label Switching Architecture"">RFC3031</a>]. |
| 414 |
|
| 415 |
The MPLS-LSR-STD-MIB [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>] describes the objects required to |
| 416 |
define the LSP. |
| 417 |
|
| 418 |
<span class="h4"><a class="selflink" id="section-4.2.4" href="#section-4.2.4">4.2.4</a>. Label Edge Router (LER) Modules</span> |
| 419 |
|
| 420 |
Ingress and egress LSRs of an LSP are known as Label Edge Routers |
| 421 |
(LERs). An ingress LER takes each incoming unlabeled or labeled |
| 422 |
packet and encapsulates it with the corresponding label of the LSP it |
| 423 |
represents, and then forwards it to the adjacent LSR of the LSP. |
| 424 |
Each FEC is mapped to a label-forwarding entry, so that a packet |
| 425 |
could be encapsulated with one or more label entries; this is |
| 426 |
referred to as a label stack. |
| 427 |
|
| 428 |
The packet traverses the LSP. Upon reaching the egress LER, further |
| 429 |
action will be taken to handle the packet, depending on the type of |
| 430 |
packet received. MPLS Architecture [<a href="./rfc3031" title=""Multiprotocol Label Switching Architecture"">RFC3031</a>] details the |
| 431 |
functionality of ingress and egress LERs. |
| 432 |
|
| 433 |
The MPLS-FTN-STD-MIB [<a href="./rfc3814" title=""Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)"">RFC3814</a>] describes the managed objects for |
| 434 |
mapping FEC to label bindings. |
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">King & Venkatesan Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h4"><a class="selflink" id="section-4.2.5" href="#section-4.2.5">4.2.5</a>. Label Switching Router (LSR) Modules</span> |
| 450 |
|
| 451 |
A router that performs MPLS forwarding is known as an LSR. An LSR |
| 452 |
receives a labeled packet and performs forwarding action based on the |
| 453 |
label received. |
| 454 |
|
| 455 |
The LSR maintains a mapping of an incoming label and incoming |
| 456 |
interface to one or more outgoing labels and outgoing interfaces in |
| 457 |
its forwarding database. When a labeled packet is received, the LSR |
| 458 |
examines the topmost label in the label stack and then does a 'swap', |
| 459 |
'push', or 'pop' operation based on the contents. |
| 460 |
|
| 461 |
The MPLS-LSR-STD-MIB [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>] describes the managed objects for |
| 462 |
modeling an MPLS [<a href="./rfc3031" title=""Multiprotocol Label Switching Architecture"">RFC3031</a>] LSR. The MPLS-LSR-STD-MIB [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>] |
| 463 |
contains the managed objects to maintain mapping of in-segments to |
| 464 |
out-segments. |
| 465 |
|
| 466 |
<span class="h4"><a class="selflink" id="section-4.2.6" href="#section-4.2.6">4.2.6</a>. Pseudowire Modules</span> |
| 467 |
|
| 468 |
The pseudowire (PW) MIB architecture provides a layered modular model |
| 469 |
into which any supported emulated service such as Frame Relay, ATM, |
| 470 |
Ethernet, Time-Division Multiplexing (TDM), and Synchronous Optical |
| 471 |
Network/Synchronous Digital Hierarchy (SONET/SDH) can be connected to |
| 472 |
any supported Packet Switched Network (PSN) type. This MIB |
| 473 |
architecture is modeled based on PW3 architecture [<a href="./rfc3985" title=""Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture"">RFC3985</a>]. |
| 474 |
|
| 475 |
The emulated service layer, generic PW layer, and PSN Virtual Circuit |
| 476 |
(VC) layer constitute the different layers of the model. A |
| 477 |
combination of the MIB modules belonging to each layer provides the |
| 478 |
glue for mapping the emulated service onto the native PSN service. |
| 479 |
At least three MIB modules, each belonging to a different layer, are |
| 480 |
required to define a PW emulated service. |
| 481 |
|
| 482 |
- The service-specific module is dependent on the emulated signal |
| 483 |
type and helps in modeling the emulated service layer. |
| 484 |
|
| 485 |
The PW-ENET-STD-MIB [<a href="./rfc5603" title=""Ethernet Pseudowire (PW) Management Information Base (MIB)"">RFC5603</a>] describes a model for managing Ethernet |
| 486 |
pseudowire services for transmission over a PSN. This MIB module is |
| 487 |
generic and common to all types of PSNs supported in the PWE3 |
| 488 |
Architecture [<a href="./rfc3985" title=""Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture"">RFC3985</a>], which describes the transport and |
| 489 |
encapsulation of L1 and L2 services over supported PSN types. |
| 490 |
|
| 491 |
In particular, the MIB module associates a port or specific VLANs on |
| 492 |
top of a physical Ethernet port or a virtual Ethernet interface (for |
| 493 |
the Virtual Private LAN Service (VPLS)) to a point-to-point PW. It |
| 494 |
is complementary to the PW-STD-MIB [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>], which manages the |
| 495 |
generic PW parameters common to all services, including all supported |
| 496 |
PSN types. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">King & Venkatesan Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 503 |
|
| 504 |
|
| 505 |
The PW-TDM-MIB [<a href="./rfc5604" title=""Managed Objects for Time Division Multiplexing (TDM) over Packet Switched Networks (PSNs)"">RFC5604</a>] describes a model for managing TDM |
| 506 |
pseudowires, i.e., TDM data encapsulated for transmission over a PSN. |
| 507 |
The term "TDM" in this document is limited to the scope of |
| 508 |
Plesiochronous Digital Hierarchy (PDH). It is currently specified to |
| 509 |
carry any TDM signals in either Structure Agnostic Transport mode |
| 510 |
(E1, T1, E3, and T3) or Structure Aware Transport mode (E1, T1, and |
| 511 |
NxDS0) as defined in the PWE3 TDM Requirements document [<a href="./rfc4197" title=""Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching Networks"">RFC4197</a>]. |
| 512 |
|
| 513 |
- The generic PW module configures general parameters of the PW that |
| 514 |
are common to all types of emulated services and PSN types. |
| 515 |
|
| 516 |
The PW-STD-MIB [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>] defines a MIB module that can be used to |
| 517 |
manage PW services for transmission over a PSN [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>] [<a href="./rfc4447" title=""Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)"">RFC4447</a>]. |
| 518 |
This MIB module provides generic management of PWs that is common to |
| 519 |
all types of PSN and PW services defined by the IETF PWE3 Working |
| 520 |
Group. |
| 521 |
|
| 522 |
- The PSN-specific module associates the PW with one or more |
| 523 |
"tunnels" that carry the service over the PSN. There is a |
| 524 |
different module for each type of PSN. |
| 525 |
|
| 526 |
The PW-MPLS-STD-MIB [<a href="./rfc5602" title=""Pseudowire (PW) over MPLS PSN Management Information Base (MIB)"">RFC5602</a>] describes a model for managing |
| 527 |
pseudowire services for transmission over different flavors of MPLS |
| 528 |
tunnels. The generic PW MIB module [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>] defines the parameters |
| 529 |
global to the PW, regardless of the underlying PSN and emulated |
| 530 |
service. This document is applicable for PWs that use the MPLS PSN |
| 531 |
type in the PW-STD-MIB. Additionally, this document describes the |
| 532 |
MIB objects that define pseudowire association to the MPLS PSN that |
| 533 |
is not specific to the carried service. |
| 534 |
|
| 535 |
Together, [<a href="./rfc3811" title=""Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management"">RFC3811</a>], [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>], and [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>] describe the modeling |
| 536 |
of an MPLS tunnel and a tunnel's underlying cross-connects. This MIB |
| 537 |
module supports MPLS Traffic Engineering (MPLS-TE) PSNs, non-TE MPLS |
| 538 |
PSNs (an outer tunnel created by the Label Distribution Protocol |
| 539 |
(LDP) or manually), and MPLS PW labels only (no outer tunnel). |
| 540 |
|
| 541 |
<span class="h4"><a class="selflink" id="section-4.2.7" href="#section-4.2.7">4.2.7</a>. Routing and Traffic Engineering</span> |
| 542 |
|
| 543 |
In MPLS traffic engineering, it's possible to specify explicit routes |
| 544 |
or choose routes based on QoS metrics in setting up a path such that |
| 545 |
some specific data can be routed around network hot spots. TE LSPs |
| 546 |
can be set up through a management plane or a control plane. |
| 547 |
|
| 548 |
The MPLS-TE-STD-MIB [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>] describes managed objects for modeling |
| 549 |
MPLS [<a href="./rfc3031" title=""Multiprotocol Label Switching Architecture"">RFC3031</a>]-based traffic engineering. This MIB module should be |
| 550 |
used in conjunction with the companion document [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>] for MPLS- |
| 551 |
based traffic engineering configuration and management. |
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">King & Venkatesan Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h4"><a class="selflink" id="section-4.2.8" href="#section-4.2.8">4.2.8</a>. Resiliency</span> |
| 562 |
|
| 563 |
The purpose of MPLS resiliency is to ensure minimal interruption to |
| 564 |
traffic when a failure occurs within the system or network. |
| 565 |
|
| 566 |
Various components of MPLS resiliency solutions are as follows: |
| 567 |
|
| 568 |
1) Graceful restart in LDP and RSVP-TE modules |
| 569 |
|
| 570 |
2) Make before break |
| 571 |
|
| 572 |
3) Protection switching for LSPs |
| 573 |
|
| 574 |
4) Fast reroute for LSPs |
| 575 |
|
| 576 |
5) PW redundancy |
| 577 |
|
| 578 |
The MIB modules below only support MIB-based management for MPLS |
| 579 |
resiliency. |
| 580 |
|
| 581 |
MPLS Fast Reroute (FRR) is a restoration network resiliency mechanism |
| 582 |
used in MPLS TE to redirect traffic onto the backup LSPs in tens of |
| 583 |
milliseconds in case of link or node failure across the LSP. |
| 584 |
|
| 585 |
The MPLS-FRR-GENERAL-STD-MIB [<a href="./rfc6445" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base for Fast Reroute"">RFC6445</a>] contains objects that apply to |
| 586 |
any MPLS LSR implementing MPLS TE fast-reroute functionality. |
| 587 |
|
| 588 |
The MPLS-FRR-ONE2ONE-STD-MIB [<a href="./rfc6445" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base for Fast Reroute"">RFC6445</a>] contains objects that apply to |
| 589 |
the one-to-one backup method. |
| 590 |
|
| 591 |
The MPLS-FRR-FACILITY-STD-MIB [<a href="./rfc6445" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base for Fast Reroute"">RFC6445</a>] contains objects that apply |
| 592 |
to the facility backup method. |
| 593 |
|
| 594 |
Protection switching mechanisms have been designed to provide network |
| 595 |
resiliency for MPLS networks. Different types of protection |
| 596 |
switching mechanisms, such as 1:1, 1:N, and 1+1, have been designed. |
| 597 |
|
| 598 |
<span class="h4"><a class="selflink" id="section-4.2.9" href="#section-4.2.9">4.2.9</a>. Fault Management and Performance Management</span> |
| 599 |
|
| 600 |
MPLS manages LSP and pseudowire faults through the use of LSP ping |
| 601 |
[<a href="./rfc4379" title=""Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures"">RFC4379</a>], Virtual Circuit Connectivity Verification (VCCV) |
| 602 |
[<a href="./rfc5085" title=""Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires"">RFC5085</a>], Bidirectional Forwarding Detection (BFD) for LSPs |
| 603 |
[<a href="./rfc5884" title=""Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)"">RFC5884</a>], and BFD for VCCV [<a href="./rfc5885" title=""Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)"">RFC5885</a>] tools. |
| 604 |
|
| 605 |
MPLS currently focuses on in and/or out packet counters, errored |
| 606 |
packets, and discontinuity time. |
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">King & Venkatesan Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 615 |
|
| 616 |
|
| 617 |
Some of the MPLS and pseudowire performance tables used for |
| 618 |
performance management are given below. |
| 619 |
|
| 620 |
The mplsTunnelPerfTable [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>] provides several counters (e.g., |
| 621 |
packets forwarded, packets dropped because of errors) to measure the |
| 622 |
performance of the MPLS tunnels. |
| 623 |
|
| 624 |
The mplsInterfacePerfTable [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>] provides performance information |
| 625 |
(incoming and outgoing labels in use, and lookup failures) on a |
| 626 |
per-interface basis. |
| 627 |
|
| 628 |
The mplsInSegmentPerfTable [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>] contains statistical information |
| 629 |
(total packets received by the in-segment, total errored packets |
| 630 |
received, total packets discarded, discontinuity time) for incoming |
| 631 |
MPLS segments to an LSR. |
| 632 |
|
| 633 |
The mplsOutSegmentPerfTable [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>] contains statistical |
| 634 |
information (total packets received, total errored packets received, |
| 635 |
total packets discarded, discontinuity time) for outgoing MPLS |
| 636 |
segments from an LSR. |
| 637 |
|
| 638 |
The mplsFTNPerfTable [<a href="./rfc3814" title=""Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)"">RFC3814</a>] contains performance information for |
| 639 |
the specified interface and an FTN entry mapped to this interface. |
| 640 |
|
| 641 |
The mplsLdpEntityStatsTable [<a href="./rfc3815" title=""Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)"">RFC3815</a>] and mplsLdpSessionStatsTable |
| 642 |
[<a href="./rfc3815" title=""Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)"">RFC3815</a>] contain statistical information (session attempts, errored |
| 643 |
packets, notifications) about an LDP entity. |
| 644 |
|
| 645 |
The pwPerfCurrentTable [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>], pwPerfIntervalTable [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>], and |
| 646 |
pwPerf1DayIntervalTable [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>] provide pseudowire performance |
| 647 |
information (in and/or out packets) based on time (current interval, |
| 648 |
preconfigured specific interval, 1-day interval). |
| 649 |
|
| 650 |
The pwEnetStatsTable [<a href="./rfc5603" title=""Ethernet Pseudowire (PW) Management Information Base (MIB)"">RFC5603</a>] contains statistical counters specific |
| 651 |
for Ethernet PW. |
| 652 |
|
| 653 |
The pwTDMPerfCurrentTable [<a href="./rfc5604" title=""Managed Objects for Time Division Multiplexing (TDM) over Packet Switched Networks (PSNs)"">RFC5604</a>], pwTDMPerfIntervalTable |
| 654 |
[<a href="./rfc5604" title=""Managed Objects for Time Division Multiplexing (TDM) over Packet Switched Networks (PSNs)"">RFC5604</a>], and pwTDMPerf1DayIntervalTable [<a href="./rfc5604" title=""Managed Objects for Time Division Multiplexing (TDM) over Packet Switched Networks (PSNs)"">RFC5604</a>] contain |
| 655 |
statistical information accumulated per 15-minute, 24-hour, and 1-day |
| 656 |
periods, respectively. |
| 657 |
|
| 658 |
The gmplsTunnelErrorTable [<a href="./rfc4802" title=""Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base"">RFC4802</a>] and gmplsTunnelReversePerfTable |
| 659 |
[<a href="./rfc4802" title=""Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base"">RFC4802</a>] provide information about performance, errored packets, and |
| 660 |
in/out packet counters. |
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">King & Venkatesan Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h4"><a class="selflink" id="section-4.2.10" href="#section-4.2.10">4.2.10</a>. MIB Module Interdependencies</span> |
| 674 |
|
| 675 |
This section provides an overview of the relationship between the |
| 676 |
MPLS MIB modules for managing MPLS networks. More details of these |
| 677 |
relationships are given below. |
| 678 |
|
| 679 |
[<a id="ref-RFC4221">RFC4221</a>] mainly focuses on MPLS MIB module interdependencies. This |
| 680 |
section also highlights GMPLS and PW MIB module interdependencies. |
| 681 |
|
| 682 |
The relationship "A --> B" means that A depends on B and that MIB |
| 683 |
module A uses an object, object identifier, or Textual Convention |
| 684 |
defined in MIB module B, or that MIB module A contains a pointer |
| 685 |
(index or RowPointer) to an object in MIB module B. |
| 686 |
|
| 687 |
|
| 688 |
|
| 689 |
|
| 690 |
|
| 691 |
|
| 692 |
|
| 693 |
|
| 694 |
|
| 695 |
|
| 696 |
|
| 697 |
|
| 698 |
|
| 699 |
|
| 700 |
|
| 701 |
|
| 702 |
|
| 703 |
|
| 704 |
|
| 705 |
|
| 706 |
|
| 707 |
|
| 708 |
|
| 709 |
|
| 710 |
|
| 711 |
|
| 712 |
|
| 713 |
|
| 714 |
|
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">King & Venkatesan Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 727 |
|
| 728 |
|
| 729 |
+-------> MPLS-TC-STD-MIB <-----------------------------------------+ |
| 730 |
^ ^ ^ |
| 731 |
| | | |
| 732 |
| MPLS-LSR-STD-MIB <--------------------------------+ | |
| 733 |
| ^ | |
| 734 |
| | | |
| 735 |
+<----------------------- MPLS-LDP-STD-MIB ---------------->+ | |
| 736 |
^ ^ ^ | |
| 737 |
| | | | |
| 738 |
+<-- MPLS-LDP-GENERIC-STD-MIB ------>+ | | |
| 739 |
^ | | |
| 740 |
| | | |
| 741 |
+<------ MPLS-FTN-STD-MIB --------------------------------->+ | |
| 742 |
^ | ^ | |
| 743 |
| V | | |
| 744 |
+<------------- MPLS-TE-STD-MIB -->+----------------------->+ | |
| 745 |
^ GMPLS-TC-STD-MIB ------------>+ |
| 746 |
| ^ ^ |
| 747 |
| | | |
| 748 |
+---+ +<-- GMPLS-LABEL-STD-MIB -->+ |
| 749 |
^ ^ ^ ^ ^ |
| 750 |
| | | | | |
| 751 |
+----> PW-TC-STD-MIB | GMPLS-LSR-STD-MIB --------------->+ |
| 752 |
^ | ^ ^ ^ |
| 753 |
| | | | | |
| 754 |
| IANA-PWE3-MIB | | | IANA-GMPLS-TC-MIB | |
| 755 |
| ^ | | | ^ | |
| 756 |
| | | | | | | |
| 757 |
| | +<--- GMPLS-TE-STD-MIB ------------->+ |
| 758 |
| | ^ ^ |
| 759 |
+<--- PW-STD-MIB <------+ | | |
| 760 |
^ ^ | | |
| 761 |
| | | | |
| 762 |
+<--- PW-ENET-STD-MIB ->+ | | |
| 763 |
^ ^ | | |
| 764 |
| | | | |
| 765 |
| | | | |
| 766 |
+<---------------- PW-MPLS-STD-MIB--------------------------------->+ |
| 767 |
|
| 768 |
Thus, |
| 769 |
|
| 770 |
- All the MPLS MIB modules depend on the MPLS-TC-STD-MIB. |
| 771 |
|
| 772 |
- All the GMPLS MIB modules depend on the GMPLS-TC-STD-MIB. |
| 773 |
|
| 774 |
- All the PW MIB modules depend on the PW-TC-STD-MIB. |
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">King & Venkatesan Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 783 |
|
| 784 |
|
| 785 |
- The MPLS-LDP-STD-MIB, MPLS-TE-STD-MIB, MPLS-FTN-STD-MIB, |
| 786 |
GMPLS-LSR-STD-MIB, and PW-MPLS-STD-MIB contain references to |
| 787 |
objects in the MPLS-LSR-STD-MIB. |
| 788 |
|
| 789 |
- The MPLS-LDP-GENERIC-STD-MIB contains references to objects in the |
| 790 |
MPLS-LDP-STD-MIB. |
| 791 |
|
| 792 |
- The MPLS-FTN-STD-MIB, PW-MPLS-STD-MIB, and GMPLS-TE-STD-MIB |
| 793 |
contain references to objects in the MPLS-TE-STD-MIB. |
| 794 |
|
| 795 |
- The PW-MPLS-STD-MIB and PW-ENET-STD-MIB contain references to |
| 796 |
objects in the PW-STD-MIB. |
| 797 |
|
| 798 |
- The PW-STD-MIB contains references to objects in the |
| 799 |
IANA-PWE3-MIB. |
| 800 |
|
| 801 |
- The GMPLS-TE-STD-MIB contains references to objects in the |
| 802 |
IANA-GMPLS-TC-MIB. |
| 803 |
|
| 804 |
- The GMPLS-LSR-STD-MIB contains references to objects in the |
| 805 |
GMPLS-LABEL-STD-MIB. |
| 806 |
|
| 807 |
Note that there is a Textual Convention (MplsIndexType) defined in |
| 808 |
the MPLS-LSR-STD-MIB that is imported by the MPLS-LDP-STD-MIB. |
| 809 |
|
| 810 |
<span class="h4"><a class="selflink" id="section-4.2.11" href="#section-4.2.11">4.2.11</a>. Dependencies on External MIB Modules</span> |
| 811 |
|
| 812 |
With the exception of the MPLS-TC-STD-MIB, all the MPLS MIB modules |
| 813 |
have dependencies on the Interfaces MIB (also called the Interfaces |
| 814 |
Group MIB or the IF-MIB) [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. The MPLS-FTN-STD-MIB references |
| 815 |
IP-capable interfaces on which received traffic is to be classified |
| 816 |
using indexes in the Interfaces Table (ifTable) of the IF-MIB |
| 817 |
[<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. The other MPLS MIB modules reference MPLS-capable |
| 818 |
interfaces in the ifTable. |
| 819 |
|
| 820 |
The IF-MIB [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>] defines generic managed objects for managing |
| 821 |
interfaces. The MPLS MIB modules contain media-specific extensions |
| 822 |
to the Interfaces Group for managing MPLS interfaces. |
| 823 |
|
| 824 |
The MPLS MIB modules assume the interpretation of the Interfaces |
| 825 |
Group to be in accordance with [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>], which states that the |
| 826 |
ifTable contains information on the managed resource's interfaces and |
| 827 |
that each sub-layer below the internetwork layer of a network |
| 828 |
interface is considered an interface. Thus, the MPLS interface is |
| 829 |
represented as an entry in the ifTable. |
| 830 |
|
| 831 |
The interrelation of entries in the ifTable is defined by the |
| 832 |
Interface Stack Group defined in [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">King & Venkatesan Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 839 |
|
| 840 |
|
| 841 |
The MPLS MIB modules have dependencies on the TE-LINK-STD-MIB for |
| 842 |
maintaining traffic engineering information. |
| 843 |
|
| 844 |
The MPLS MIB modules depend on the Constrained Shortest Path First |
| 845 |
(CSPF) component to obtain the path required for an MPLS tunnel to |
| 846 |
reach the end point of the tunnel, and on the BFD component to verify |
| 847 |
data-plane failures of LSPs and PWs. |
| 848 |
|
| 849 |
Finally, all of the MIB modules import standard Textual Conventions |
| 850 |
such as integers, strings, timestamps, etc., from the MIB modules in |
| 851 |
which they are defined. |
| 852 |
|
| 853 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Applicability of MPLS MIB Modules to MPLS-TP</span> |
| 854 |
|
| 855 |
This section highlights gaps in existing MPLS MIB modules in order to |
| 856 |
determine extensions or additional MIB modules that are required to |
| 857 |
support MPLS-TP in MPLS networks. |
| 858 |
|
| 859 |
[<a id="ref-RFC5951">RFC5951</a>] specifies the requirements for the management of equipment |
| 860 |
used in networks supporting MPLS-TP. It also details the essential |
| 861 |
network management capabilities for operating networks consisting of |
| 862 |
MPLS-TP equipment. |
| 863 |
|
| 864 |
[<a id="ref-RFC5950">RFC5950</a>] provides the network management framework for MPLS-TP. The |
| 865 |
document explains how network elements and networks that support |
| 866 |
MPLS-TP can be managed using solutions that satisfy the requirements |
| 867 |
defined in [<a href="./rfc5951" title=""Network Management Requirements for MPLS-based Transport Networks"">RFC5951</a>]. The relationship between MPLS-TP management |
| 868 |
and OAM is described in the MPLS-TP framework document [<a href="./rfc5950" title=""Network Management Framework for MPLS-based Transport Networks"">RFC5950</a>]. |
| 869 |
|
| 870 |
The MPLS MIB documents MPLS-TE-STD-MIB [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>], PW-STD-MIB |
| 871 |
[<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>], and MPLS-LSR-STD-MIB [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>], and their associated MIB |
| 872 |
modules, are reused for MPLS-based transport network management. |
| 873 |
|
| 874 |
Fault management and performance management form key parts of the OAM |
| 875 |
function. MPLS-TP OAM is described in [<a href="./rfc6371" title=""Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks"">RFC6371</a>]. |
| 876 |
|
| 877 |
|
| 878 |
|
| 879 |
|
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">King & Venkatesan Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. MPLS-TP Tunnel</span> |
| 898 |
|
| 899 |
<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. Gap Analysis</span> |
| 900 |
|
| 901 |
An MPLS-TP tunnel can be operated over IP and/or ITU-T Carrier Code |
| 902 |
(ICC) environments. The points below capture the gaps in existing |
| 903 |
MPLS MIB modules for managing MPLS-TP networks. |
| 904 |
|
| 905 |
- IP-based environment |
| 906 |
|
| 907 |
i. The MPLS-TE-STD-MIB [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>] does not support the tunnel |
| 908 |
Ingress/Egress identifier based on Global_ID and Node_ID |
| 909 |
[<a href="./rfc6370" title=""MPLS Transport Profile (MPLS-TP) Identifiers"">RFC6370</a>]. |
| 910 |
|
| 911 |
ii. The MPLS-TE-STD-MIB [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>] does not support |
| 912 |
co-routed/associated bidirectional tunnel configurations. |
| 913 |
|
| 914 |
- ICC-based environment |
| 915 |
|
| 916 |
i. The MPLS-TE-STD-MIB [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>] does not support the tunnel LSR |
| 917 |
identifier based on ICC. |
| 918 |
|
| 919 |
<span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>. Recommendations</span> |
| 920 |
|
| 921 |
- New MIB definitions may be created for Global_Node_ID and/or ICC |
| 922 |
configurations. |
| 923 |
|
| 924 |
- The MPLS-LSR-STD-MIB [<a href="./rfc3813" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">RFC3813</a>] module may be enhanced to identify |
| 925 |
the next hop based on a Media Access Control (MAC) address for |
| 926 |
environments that do not use IP. The mplsOutSegmentTable may be |
| 927 |
extended to hold the MAC address. |
| 928 |
|
| 929 |
- The MPLS-TE-STD-MIB [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>] and MPLS-LSR-STD-MIB may be enhanced |
| 930 |
to provide static and signaling MIB module extensions for |
| 931 |
co-routed/associated bidirectional LSPs. |
| 932 |
|
| 933 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. MPLS-TP Pseudowire</span> |
| 934 |
|
| 935 |
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Gap Analysis</span> |
| 936 |
|
| 937 |
MPLS-TP pseudowire can be operated over IP and/or ICC environments. |
| 938 |
The points below capture the gaps in existing PW MIB modules for |
| 939 |
managing MPLS-TP networks. |
| 940 |
|
| 941 |
[<a id="ref-RFC6370">RFC6370</a>] specifies an initial set of identifiers to be used in |
| 942 |
MPLS-TP. These identifiers were chosen to be compatible with |
| 943 |
existing MPLS, GMPLS, and PW definitions. |
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">King & Venkatesan Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 951 |
|
| 952 |
|
| 953 |
- IP-based environment |
| 954 |
|
| 955 |
i. The PW-STD-MIB [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>] does not support the PW end point |
| 956 |
identifier based on Global_ID and Node_ID. |
| 957 |
|
| 958 |
ii. The PW-MPLS-STD-MIB [<a href="./rfc5602" title=""Pseudowire (PW) over MPLS PSN Management Information Base (MIB)"">RFC5602</a>] does not support operation over |
| 959 |
co-routed/associated bidirectional tunnels. |
| 960 |
|
| 961 |
- ICC-based environment |
| 962 |
|
| 963 |
i. The PW-STD-MIB [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>] does not support the PW end point |
| 964 |
identifier based on ICC. |
| 965 |
|
| 966 |
<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. Recommendations</span> |
| 967 |
|
| 968 |
- The PW-MPLS-STD-MIB [<a href="./rfc5602" title=""Pseudowire (PW) over MPLS PSN Management Information Base (MIB)"">RFC5602</a>] can be enhanced to operate over |
| 969 |
co-routed/associated bidirectional tunnels. |
| 970 |
|
| 971 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. MPLS-TP Sections</span> |
| 972 |
|
| 973 |
<span class="h4"><a class="selflink" id="section-5.3.1" href="#section-5.3.1">5.3.1</a>. Gap Analysis</span> |
| 974 |
|
| 975 |
The existing MPLS MIB modules do not support MPLS-TP sections. |
| 976 |
|
| 977 |
<span class="h4"><a class="selflink" id="section-5.3.2" href="#section-5.3.2">5.3.2</a>. Recommendations</span> |
| 978 |
|
| 979 |
Link-specific and/or path/segment-specific sections can be supported |
| 980 |
by enhancing the IF-MIB [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>], MPLS-TE-STD-MIB [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>], and |
| 981 |
PW-STD-MIB [<a href="./rfc5601" title=""Pseudowire (PW) Management Information Base (MIB)"">RFC5601</a>] MIB modules. |
| 982 |
|
| 983 |
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. MPLS-TP OAM</span> |
| 984 |
|
| 985 |
<span class="h4"><a class="selflink" id="section-5.4.1" href="#section-5.4.1">5.4.1</a>. Gap Analysis</span> |
| 986 |
|
| 987 |
MPLS manages LSP and pseudowire faults through LSP ping [<a href="./rfc4379" title=""Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures"">RFC4379</a>], |
| 988 |
VCCV [<a href="./rfc5085" title=""Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires"">RFC5085</a>], BFD for LSPs [<a href="./rfc5884" title=""Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)"">RFC5884</a>], and BFD for VCCV [<a href="./rfc5885" title=""Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)"">RFC5885</a>] |
| 989 |
tools. |
| 990 |
|
| 991 |
The MPLS MIB modules do not support the following MPLS-TP OAM |
| 992 |
functions: |
| 993 |
|
| 994 |
o Continuity Check and Connectivity Verification |
| 995 |
|
| 996 |
o Remote Defect Indication |
| 997 |
|
| 998 |
o Alarm Reporting |
| 999 |
|
| 1000 |
o Lock Reporting |
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">King & Venkatesan Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
o Lock Instruct |
| 1010 |
|
| 1011 |
o Client Failure Indication |
| 1012 |
|
| 1013 |
o Packet Loss Measurement |
| 1014 |
|
| 1015 |
o Packet Delay Measurement |
| 1016 |
|
| 1017 |
<span class="h4"><a class="selflink" id="section-5.4.2" href="#section-5.4.2">5.4.2</a>. Recommendations</span> |
| 1018 |
|
| 1019 |
New MIB module for BFD can be created to address all the gaps |
| 1020 |
mentioned in <a href="#section-5.4.1">Section 5.4.1</a>. |
| 1021 |
|
| 1022 |
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. MPLS-TP Protection Switching and Recovery</span> |
| 1023 |
|
| 1024 |
<span class="h4"><a class="selflink" id="section-5.5.1" href="#section-5.5.1">5.5.1</a>. Gap Analysis</span> |
| 1025 |
|
| 1026 |
An important aspect that MPLS-TP technology provides is protection |
| 1027 |
switching. In general, the mechanism of protection switching can be |
| 1028 |
described as the substitution of a protection or standby facility for |
| 1029 |
a working or primary facility. |
| 1030 |
|
| 1031 |
The MPLS MIB modules do not provide support for protection switching |
| 1032 |
and recovery in the following three topologies: linear, ring, and |
| 1033 |
mesh. |
| 1034 |
|
| 1035 |
<span class="h4"><a class="selflink" id="section-5.5.2" href="#section-5.5.2">5.5.2</a>. Recommendations</span> |
| 1036 |
|
| 1037 |
New MIB modules can be created to address all the gaps mentioned in |
| 1038 |
<a href="#section-5.5.1">Section 5.5.1</a>. |
| 1039 |
|
| 1040 |
<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. MPLS-TP Interfaces</span> |
| 1041 |
|
| 1042 |
<span class="h4"><a class="selflink" id="section-5.6.1" href="#section-5.6.1">5.6.1</a>. Gap Analysis</span> |
| 1043 |
|
| 1044 |
As per [<a href="./rfc6370" title=""MPLS Transport Profile (MPLS-TP) Identifiers"">RFC6370</a>], an LSR requires identification of the node itself |
| 1045 |
and of its interfaces. An interface is the attachment point to a |
| 1046 |
server layer MPLS-TP section or MPLS-TP tunnel. |
| 1047 |
|
| 1048 |
The MPLS MIB modules do not provide support for configuring the |
| 1049 |
interfaces within the context of an operator. |
| 1050 |
|
| 1051 |
<span class="h4"><a class="selflink" id="section-5.6.2" href="#section-5.6.2">5.6.2</a>. Recommendations</span> |
| 1052 |
|
| 1053 |
New MIB definitions can be created to address the gaps mentioned in |
| 1054 |
<a href="#section-5.6.1">Section 5.6.1</a>. |
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">King & Venkatesan Informational [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. An Introduction to the MPLS-TP MIB Modules</span> |
| 1066 |
|
| 1067 |
This section highlights new MIB modules that have been identified as |
| 1068 |
being required for MPLS-TP. This section also provides an overview |
| 1069 |
of the purpose of each MIB module within the MIB documents, what it |
| 1070 |
can be used for, and how it relates to the other MIB modules. |
| 1071 |
|
| 1072 |
Note that each new MIB module (apart from Textual Conventions |
| 1073 |
modules) will contain one or more Compliance Statements to indicate |
| 1074 |
which objects must be supported in what manner to claim a specific |
| 1075 |
level of compliance. Additional text, either in the documents that |
| 1076 |
define the MIB modules or in separate Applicability Statements, will |
| 1077 |
define which Compliance Statements need to be conformed to in order |
| 1078 |
to provide specific MPLS-TP functionality. This document does not |
| 1079 |
set any requirements in that respect, although some recommendations |
| 1080 |
are included in the sections that follow. |
| 1081 |
|
| 1082 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. MPLS-TP MIB Modules</span> |
| 1083 |
|
| 1084 |
<span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>. New MIB Modules for MPLS-TP</span> |
| 1085 |
|
| 1086 |
Four new MIB modules are identified as follows: |
| 1087 |
|
| 1088 |
- Textual Conventions for MPLS-TP |
| 1089 |
|
| 1090 |
- Identifiers for MPLS-TP |
| 1091 |
|
| 1092 |
- LSR MIB Extensions for MPLS-TP |
| 1093 |
|
| 1094 |
- Tunnel Extensions for MPLS-TP |
| 1095 |
|
| 1096 |
Note that the MIB modules mentioned here are applicable for MPLS |
| 1097 |
operations as well. |
| 1098 |
|
| 1099 |
<span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>. Textual Conventions for MPLS-TP</span> |
| 1100 |
|
| 1101 |
A new MIB module needs to be written that will define Textual |
| 1102 |
Conventions [<a href="./rfc2579" title=""Textual Conventions for SMIv2"">RFC2579</a>] for MPLS-TP-related MIB modules. These |
| 1103 |
conventions allow multiple MIB modules to use the same syntax and |
| 1104 |
format to provide a concept that is shared between the MIB modules. |
| 1105 |
|
| 1106 |
For example, a Maintenance Entity Group End Point (MEP) identifier is |
| 1107 |
used to identify a maintenance entity group end point within MPLS-TP |
| 1108 |
networks. The Textual Convention representing the MEP identifier |
| 1109 |
should be defined in a new Textual Convention MIB module. |
| 1110 |
|
| 1111 |
All new extensions related to MPLS-TP are defined in the MIB module |
| 1112 |
and will be referenced by other MIB modules to support MPLS-TP. |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">King & Venkatesan Informational [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
<span class="h4"><a class="selflink" id="section-6.1.3" href="#section-6.1.3">6.1.3</a>. Identifiers for MPLS-TP</span> |
| 1122 |
|
| 1123 |
New identifiers describe managed objects that are used to model |
| 1124 |
common MPLS-TP identifiers [<a href="./rfc6370" title=""MPLS Transport Profile (MPLS-TP) Identifiers"">RFC6370</a>]. |
| 1125 |
|
| 1126 |
<span class="h4"><a class="selflink" id="section-6.1.4" href="#section-6.1.4">6.1.4</a>. LSR MIB Extensions for MPLS-TP</span> |
| 1127 |
|
| 1128 |
The MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS |
| 1129 |
LSR. This puts it at the heart of the management architecture for |
| 1130 |
MPLS. |
| 1131 |
|
| 1132 |
In the case of MPLS-TP, the MPLS-LSR-STD-MIB is extended to support |
| 1133 |
MPLS-TP LSPs, which are co-routed or associated bidirectionally. |
| 1134 |
This extended MIB is also applicable for modeling MPLS-TP tunnels. |
| 1135 |
|
| 1136 |
<span class="h4"><a class="selflink" id="section-6.1.5" href="#section-6.1.5">6.1.5</a>. Tunnel Extensions for MPLS-TP</span> |
| 1137 |
|
| 1138 |
The MPLS-TE-STD-MIB describes managed objects that are used to model |
| 1139 |
and manage MPLS-TE tunnels. |
| 1140 |
|
| 1141 |
MPLS-TP tunnels are very similar to MPLS-TE tunnels but are co-routed |
| 1142 |
or associated bidirectionally. |
| 1143 |
|
| 1144 |
The MPLS-TE-STD-MIB must be extended to support the MPLS-TP-specific |
| 1145 |
attributes for the tunnel. |
| 1146 |
|
| 1147 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. PWE3 MIB Modules for MPLS-TP</span> |
| 1148 |
|
| 1149 |
This section provides an overview of pseudowire-extension MIB modules |
| 1150 |
used to meet MPLS-based transport network requirements. |
| 1151 |
|
| 1152 |
<span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. New MIB Modules for MPLS-TP Pseudowires</span> |
| 1153 |
|
| 1154 |
Three new MIB modules are identified as follows: |
| 1155 |
|
| 1156 |
- Pseudowire Textual Conventions for MPLS-TP |
| 1157 |
|
| 1158 |
- Pseudowire Extensions for MPLS-TP |
| 1159 |
|
| 1160 |
- Pseudowire MPLS Extensions for MPLS-TP |
| 1161 |
|
| 1162 |
<span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>. Pseudowire Textual Conventions for MPLS-TP</span> |
| 1163 |
|
| 1164 |
The PW-TC-STD-MIB defines Textual Conventions used for PW technology |
| 1165 |
and for PWE3 MIB modules. A new Textual Convention MIB module is |
| 1166 |
required to define textual definitions for MPLS-TP-specific |
| 1167 |
pseudowire attributes. |
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">King & Venkatesan Informational [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
<span class="h4"><a class="selflink" id="section-6.2.3" href="#section-6.2.3">6.2.3</a>. Pseudowire Extensions for MPLS-TP</span> |
| 1178 |
|
| 1179 |
The PW-STD-MIB describes managed objects for the modeling of |
| 1180 |
pseudowire edge-to-edge services carried over a general PSN. This |
| 1181 |
MIB module is extended to support MPLS-TP-specific attributes related |
| 1182 |
to pseudowires. |
| 1183 |
|
| 1184 |
<span class="h4"><a class="selflink" id="section-6.2.4" href="#section-6.2.4">6.2.4</a>. Pseudowire MPLS Extensions for MPLS-TP</span> |
| 1185 |
|
| 1186 |
The PW-MPLS-STD-MIB defines the managed objects for pseudowire |
| 1187 |
operations over MPLS LSRs. This MIB module supports |
| 1188 |
|
| 1189 |
- manually and dynamically signaled PWs |
| 1190 |
|
| 1191 |
- point-to-point connections |
| 1192 |
|
| 1193 |
- the use of any emulated service |
| 1194 |
|
| 1195 |
- outer tunnels provisioned using MPLS-TE |
| 1196 |
|
| 1197 |
- PWs with no outer tunnel |
| 1198 |
|
| 1199 |
An extended MIB module would define additional objects, extending the |
| 1200 |
PW-MPLS-STD-MIB by continuing to support configurations that operate |
| 1201 |
with or without an outer tunnel. |
| 1202 |
|
| 1203 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. OAM MIB Modules for MPLS-TP</span> |
| 1204 |
|
| 1205 |
This section provides an overview of Operations, Administration, and |
| 1206 |
Maintenance (OAM) MIB modules for MPLS LSPs and pseudowires. |
| 1207 |
|
| 1208 |
<span class="h4"><a class="selflink" id="section-6.3.1" href="#section-6.3.1">6.3.1</a>. New MIB Modules for OAM for MPLS-TP</span> |
| 1209 |
|
| 1210 |
Two new MIB modules are identified as follows: |
| 1211 |
|
| 1212 |
- BFD MIB module |
| 1213 |
|
| 1214 |
- OAM MIB module |
| 1215 |
|
| 1216 |
<span class="h4"><a class="selflink" id="section-6.3.2" href="#section-6.3.2">6.3.2</a>. BFD MIB Module</span> |
| 1217 |
|
| 1218 |
The BFD-STD-MIB defines managed objects for performing BFD operations |
| 1219 |
in IP networks. This MIB module is modeled to support the BFD |
| 1220 |
protocol [<a href="./rfc5880" title=""Bidirectional Forwarding Detection (BFD)"">RFC5880</a>]. |
| 1221 |
|
| 1222 |
A new MIB module needs to be written that will be an extension to |
| 1223 |
BFD-STD-MIB managed objects to support BFD operations on MPLS LSPs |
| 1224 |
and PWs. |
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">King & Venkatesan Informational [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
<span class="h4"><a class="selflink" id="section-6.3.3" href="#section-6.3.3">6.3.3</a>. OAM MIB Module</span> |
| 1234 |
|
| 1235 |
A new MIB module needs to be written that will define managed objects |
| 1236 |
for OAM maintenance identifiers, i.e., Maintenance Entity Group (MEG) |
| 1237 |
identifiers, the MEP, and the Maintenance Entity Group Intermediate |
| 1238 |
Point (MIP). Maintenance points are uniquely associated with a MEG. |
| 1239 |
Within the context of a MEG, MEPs and MIPs must be uniquely |
| 1240 |
identified. |
| 1241 |
|
| 1242 |
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Protection Switching and Recovery MIB Modules for MPLS-TP</span> |
| 1243 |
|
| 1244 |
This section provides an overview of protection switching and |
| 1245 |
recovery MIB modules for MPLS LSPs and pseudowires. |
| 1246 |
|
| 1247 |
<span class="h4"><a class="selflink" id="section-6.4.1" href="#section-6.4.1">6.4.1</a>. New MIB Modules for MPLS Protection Switching and Recovery</span> |
| 1248 |
|
| 1249 |
Three new MIB modules are identified as follows: |
| 1250 |
|
| 1251 |
- Linear Protection Switching MIB module |
| 1252 |
|
| 1253 |
- Ring Protection Switching MIB module |
| 1254 |
|
| 1255 |
- Mesh Protection Switching MIB module |
| 1256 |
|
| 1257 |
<span class="h4"><a class="selflink" id="section-6.4.2" href="#section-6.4.2">6.4.2</a>. Linear Protection Switching MIB Module</span> |
| 1258 |
|
| 1259 |
A new MIB module needs to be written that will define managed objects |
| 1260 |
for linear protection switching of MPLS LSPs and pseudowires. |
| 1261 |
|
| 1262 |
<span class="h4"><a class="selflink" id="section-6.4.3" href="#section-6.4.3">6.4.3</a>. Ring Protection Switching MIB Module</span> |
| 1263 |
|
| 1264 |
A new MIB module needs to be written that will define managed objects |
| 1265 |
for ring protection switching of MPLS LSPs and pseudowires. |
| 1266 |
|
| 1267 |
<span class="h4"><a class="selflink" id="section-6.4.4" href="#section-6.4.4">6.4.4</a>. Mesh Protection Switching MIB Module</span> |
| 1268 |
|
| 1269 |
A new MIB module needs to be written that will define managed objects |
| 1270 |
for mesh protection switching of MPLS LSPs and pseudowires. |
| 1271 |
|
| 1272 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Management Options</span> |
| 1273 |
|
| 1274 |
This document applies only to scenarios where MIB modules are used to |
| 1275 |
manage the MPLS-TP network. It is not the intention of this document |
| 1276 |
to provide instructions or advice to implementers of management |
| 1277 |
systems, management agents, or managed entities. It is, however, |
| 1278 |
useful to make some observations about how the MIB modules described |
| 1279 |
above might be used to manage MPLS systems, if SNMP is used in the |
| 1280 |
management interface. |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">King & Venkatesan Informational [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
For MPLS-specific management options, refer to <a href="./rfc4221#section-12">[RFC4221] Section 12</a> |
| 1290 |
("Management Options"). |
| 1291 |
|
| 1292 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span> |
| 1293 |
|
| 1294 |
This document describes the interrelationships amongst the different |
| 1295 |
MIB modules relevant to MPLS-TP management and as such does not have |
| 1296 |
any security implications in and of itself. |
| 1297 |
|
| 1298 |
Each IETF MIB document that specifies MIB objects for MPLS-TP must |
| 1299 |
provide a proper Security Considerations section that explains the |
| 1300 |
security aspects of those objects. |
| 1301 |
|
| 1302 |
The attention of readers is particularly drawn to the security |
| 1303 |
implications of making MIB objects available for create or write |
| 1304 |
access through an access protocol such as SNMP. SNMPv1 by itself is |
| 1305 |
an insecure environment. Even if the network itself is made secure |
| 1306 |
(for example, by using IPsec), there is no control over who on the |
| 1307 |
secure network is allowed to access the objects in the MIB module. |
| 1308 |
It is recommended that the implementers consider the security |
| 1309 |
features as provided by the SNMPv3 framework. Specifically, the use |
| 1310 |
of the User-based Security Model STD 62, <a href="./rfc3414">RFC 3414</a> [<a href="./rfc3414" title=""User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)"">RFC3414</a>], and the |
| 1311 |
View-based Access Control Model STD 62, <a href="./rfc3415">RFC 3415</a> [<a href="./rfc3415" title=""View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)"">RFC3415</a>], is |
| 1312 |
recommended. |
| 1313 |
|
| 1314 |
It is then a customer/user responsibility to ensure that the SNMP |
| 1315 |
entity giving access to an instance of each MIB module is properly |
| 1316 |
configured to give access to only those objects, and to those |
| 1317 |
principals (users) that have legitimate rights to access them. |
| 1318 |
|
| 1319 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. IANA Considerations</span> |
| 1320 |
|
| 1321 |
This document has identified areas where additional MIB modules are |
| 1322 |
necessary for MPLS-TP. The new MIB modules recommended by this |
| 1323 |
document will require OID assignments from IANA. However, this |
| 1324 |
document makes no specific request for IANA action. |
| 1325 |
|
| 1326 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgements</span> |
| 1327 |
|
| 1328 |
The authors would like to thank Eric Gray, Thomas Nadeau, Benjamin |
| 1329 |
Niven-Jenkins, Saravanan Narasimhan, Joel Halpern, David Harrington, |
| 1330 |
and Stephen Farrell for their valuable comments. |
| 1331 |
|
| 1332 |
This document also benefited from review by participants in ITU-T |
| 1333 |
Study Group 15. |
| 1334 |
|
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">King & Venkatesan Informational [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Contributors' Addresses</span> |
| 1346 |
|
| 1347 |
Adrian Farrel |
| 1348 |
Old Dog Consulting |
| 1349 |
UK |
| 1350 |
|
| 1351 |
EMail: [email protected] |
| 1352 |
|
| 1353 |
|
| 1354 |
Scott Mansfield |
| 1355 |
Ericsson |
| 1356 |
300 Holger Way |
| 1357 |
San Jose, CA 95134 |
| 1358 |
US |
| 1359 |
|
| 1360 |
Phone: +1 724 931 9316 |
| 1361 |
EMail: [email protected] |
| 1362 |
|
| 1363 |
|
| 1364 |
Jeong-dong Ryoo |
| 1365 |
ETRI |
| 1366 |
161 Gajeong, Yuseong |
| 1367 |
Daejeon, 305-700 |
| 1368 |
South Korea |
| 1369 |
|
| 1370 |
Phone: +82 42 860 5384 |
| 1371 |
EMail: [email protected] |
| 1372 |
|
| 1373 |
|
| 1374 |
A S Kiran Koushik |
| 1375 |
Cisco Systems Inc. |
| 1376 |
|
| 1377 |
EMail: [email protected] |
| 1378 |
|
| 1379 |
|
| 1380 |
A. Karmakar |
| 1381 |
Cisco Systems Inc. |
| 1382 |
|
| 1383 |
EMail: [email protected] |
| 1384 |
|
| 1385 |
|
| 1386 |
Sam Aldrin |
| 1387 |
Huawei Technologies Co. |
| 1388 |
2330 Central Expressway |
| 1389 |
Santa Clara, CA 95051 |
| 1390 |
USA |
| 1391 |
|
| 1392 |
EMail: [email protected] |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">King & Venkatesan Informational [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span> |
| 1402 |
|
| 1403 |
<span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Normative References</span> |
| 1404 |
|
| 1405 |
[<a id="ref-RFC2863">RFC2863</a>] McCloghrie, K. and F. Kastenholz, "The Interfaces Group |
| 1406 |
MIB", <a href="./rfc2863">RFC 2863</a>, June 2000. |
| 1407 |
|
| 1408 |
[<a id="ref-RFC3811">RFC3811</a>] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of |
| 1409 |
Textual Conventions (TCs) for Multiprotocol Label |
| 1410 |
Switching (MPLS) Management", <a href="./rfc3811">RFC 3811</a>, June 2004. |
| 1411 |
|
| 1412 |
[<a id="ref-RFC3812">RFC3812</a>] Srinivasan, C., Viswanathan, A., and T. Nadeau, |
| 1413 |
"Multiprotocol Label Switching (MPLS) Traffic Engineering |
| 1414 |
(TE) Management Information Base (MIB)", <a href="./rfc3812">RFC 3812</a>, |
| 1415 |
June 2004. |
| 1416 |
|
| 1417 |
[<a id="ref-RFC3813">RFC3813</a>] Srinivasan, C., Viswanathan, A., and T. Nadeau, |
| 1418 |
"Multiprotocol Label Switching (MPLS) Label Switching |
| 1419 |
Router (LSR) Management Information Base (MIB)", |
| 1420 |
<a href="./rfc3813">RFC 3813</a>, June 2004. |
| 1421 |
|
| 1422 |
[<a id="ref-RFC3814">RFC3814</a>] Nadeau, T., Srinivasan, C., and A. Viswanathan, |
| 1423 |
"Multiprotocol Label Switching (MPLS) Forwarding |
| 1424 |
Equivalence Class To Next Hop Label Forwarding Entry |
| 1425 |
(FEC-To-NHLFE) Management Information Base (MIB)", |
| 1426 |
<a href="./rfc3814">RFC 3814</a>, June 2004. |
| 1427 |
|
| 1428 |
[<a id="ref-RFC3815">RFC3815</a>] Cucchiara, J., Sjostrand, H., and J. Luciani, |
| 1429 |
"Definitions of Managed Objects for the Multiprotocol |
| 1430 |
Label Switching (MPLS), Label Distribution Protocol |
| 1431 |
(LDP)", <a href="./rfc3815">RFC 3815</a>, June 2004. |
| 1432 |
|
| 1433 |
[<a id="ref-RFC4220">RFC4220</a>] Dubuc, M., Nadeau, T., and J. Lang, "Traffic Engineering |
| 1434 |
Link Management Information Base", <a href="./rfc4220">RFC 4220</a>, |
| 1435 |
November 2005. |
| 1436 |
|
| 1437 |
[<a id="ref-RFC4221">RFC4221</a>] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol |
| 1438 |
Label Switching (MPLS) Management Overview", <a href="./rfc4221">RFC 4221</a>, |
| 1439 |
November 2005. |
| 1440 |
|
| 1441 |
[<a id="ref-RFC4801">RFC4801</a>] Nadeau, T., Ed., and A. Farrel, Ed., "Definitions of |
| 1442 |
Textual Conventions for Generalized Multiprotocol Label |
| 1443 |
Switching (GMPLS) Management", <a href="./rfc4801">RFC 4801</a>, February 2007. |
| 1444 |
|
| 1445 |
[<a id="ref-RFC4802">RFC4802</a>] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized |
| 1446 |
Multiprotocol Label Switching (GMPLS) Traffic Engineering |
| 1447 |
Management Information Base", <a href="./rfc4802">RFC 4802</a>, February 2007. |
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">King & Venkatesan Informational [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
[<a id="ref-RFC4803">RFC4803</a>] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized |
| 1458 |
Multiprotocol Label Switching (GMPLS) Label Switching |
| 1459 |
Router (LSR) Management Information Base", <a href="./rfc4803">RFC 4803</a>, |
| 1460 |
February 2007. |
| 1461 |
|
| 1462 |
[<a id="ref-RFC5542">RFC5542</a>] Nadeau, T., Ed., Zelig, D., Ed., and O. Nicklass, Ed., |
| 1463 |
"Definitions of Textual Conventions for Pseudowire (PW) |
| 1464 |
Management", <a href="./rfc5542">RFC 5542</a>, May 2009. |
| 1465 |
|
| 1466 |
[<a id="ref-RFC5601">RFC5601</a>] Nadeau, T., Ed., and D. Zelig, Ed., "Pseudowire (PW) |
| 1467 |
Management Information Base (MIB)", <a href="./rfc5601">RFC 5601</a>, July 2009. |
| 1468 |
|
| 1469 |
[<a id="ref-RFC5602">RFC5602</a>] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over |
| 1470 |
MPLS PSN Management Information Base (MIB)", <a href="./rfc5602">RFC 5602</a>, |
| 1471 |
July 2009. |
| 1472 |
|
| 1473 |
[<a id="ref-RFC5603">RFC5603</a>] Zelig, D., Ed., and T. Nadeau, Ed., "Ethernet Pseudowire |
| 1474 |
(PW) Management Information Base (MIB)", <a href="./rfc5603">RFC 5603</a>, |
| 1475 |
July 2009. |
| 1476 |
|
| 1477 |
[<a id="ref-RFC5604">RFC5604</a>] Nicklass, O., "Managed Objects for Time Division |
| 1478 |
Multiplexing (TDM) over Packet Switched Networks (PSNs)", |
| 1479 |
<a href="./rfc5604">RFC 5604</a>, July 2009. |
| 1480 |
|
| 1481 |
<span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Informative References</span> |
| 1482 |
|
| 1483 |
[<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Ed., Perkins, D., Ed., and J. |
| 1484 |
Schoenwaelder, Ed., "Structure of Management Information |
| 1485 |
Version 2 (SMIv2)", STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999. |
| 1486 |
|
| 1487 |
[<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Ed., Perkins, D., Ed., and J. |
| 1488 |
Schoenwaelder, Ed., "Textual Conventions for SMIv2", |
| 1489 |
STD 58, <a href="./rfc2579">RFC 2579</a>, April 1999. |
| 1490 |
|
| 1491 |
[<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Ed., Perkins, D., Ed., and J. |
| 1492 |
Schoenwaelder, Ed., "Conformance Statements for SMIv2", |
| 1493 |
STD 58, <a href="./rfc2580">RFC 2580</a>, April 1999. |
| 1494 |
|
| 1495 |
[<a id="ref-RFC3031">RFC3031</a>] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol |
| 1496 |
Label Switching Architecture", <a href="./rfc3031">RFC 3031</a>, January 2001. |
| 1497 |
|
| 1498 |
[<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D., and B. Stewart, |
| 1499 |
"Introduction and Applicability Statements for Internet- |
| 1500 |
Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, December 2002. |
| 1501 |
|
| 1502 |
[<a id="ref-RFC3414">RFC3414</a>] Blumenthal, U. and B. Wijnen, "User-based Security Model |
| 1503 |
(USM) for version 3 of the Simple Network Management |
| 1504 |
Protocol (SNMPv3)", STD 62, <a href="./rfc3414">RFC 3414</a>, December 2002. |
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">King & Venkatesan Informational [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
[<a id="ref-RFC3415">RFC3415</a>] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based |
| 1514 |
Access Control Model (VACM) for the Simple Network |
| 1515 |
Management Protocol (SNMP)", STD 62, <a href="./rfc3415">RFC 3415</a>, |
| 1516 |
December 2002. |
| 1517 |
|
| 1518 |
[<a id="ref-RFC3931">RFC3931</a>] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed., |
| 1519 |
"Layer Two Tunneling Protocol - Version 3 (L2TPv3)", |
| 1520 |
<a href="./rfc3931">RFC 3931</a>, March 2005. |
| 1521 |
|
| 1522 |
[<a id="ref-RFC3945">RFC3945</a>] Mannie, E., Ed., "Generalized Multi-Protocol Label |
| 1523 |
Switching (GMPLS) Architecture", <a href="./rfc3945">RFC 3945</a>, October 2004. |
| 1524 |
|
| 1525 |
[<a id="ref-RFC3985">RFC3985</a>] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire Emulation |
| 1526 |
Edge-to-Edge (PWE3) Architecture", <a href="./rfc3985">RFC 3985</a>, March 2005. |
| 1527 |
|
| 1528 |
[<a id="ref-RFC4197">RFC4197</a>] Riegel, M., Ed., "Requirements for Edge-to-Edge Emulation |
| 1529 |
of Time Division Multiplexed (TDM) Circuits over Packet |
| 1530 |
Switching Networks", <a href="./rfc4197">RFC 4197</a>, October 2005. |
| 1531 |
|
| 1532 |
[<a id="ref-RFC4377">RFC4377</a>] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S. |
| 1533 |
Matsushima, "Operations and Management (OAM) Requirements |
| 1534 |
for Multi-Protocol Label Switched (MPLS) Networks", |
| 1535 |
<a href="./rfc4377">RFC 4377</a>, February 2006. |
| 1536 |
|
| 1537 |
[<a id="ref-RFC4378">RFC4378</a>] Allan, D., Ed., and T. Nadeau, Ed., "A Framework for |
| 1538 |
Multi-Protocol Label Switching (MPLS) Operations and |
| 1539 |
Management (OAM)", <a href="./rfc4378">RFC 4378</a>, February 2006. |
| 1540 |
|
| 1541 |
[<a id="ref-RFC4379">RFC4379</a>] Kompella, K. and G. Swallow, "Detecting Multi-Protocol |
| 1542 |
Label Switched (MPLS) Data Plane Failures", <a href="./rfc4379">RFC 4379</a>, |
| 1543 |
February 2006. |
| 1544 |
|
| 1545 |
[<a id="ref-RFC4447">RFC4447</a>] Martini, L., Ed., Rosen, E., El-Aawar, N., Smith, T., and |
| 1546 |
G. Heron, "Pseudowire Setup and Maintenance Using the |
| 1547 |
Label Distribution Protocol (LDP)", <a href="./rfc4447">RFC 4447</a>, April 2006. |
| 1548 |
|
| 1549 |
[<a id="ref-RFC5085">RFC5085</a>] Nadeau, T., Ed., and C. Pignataro, Ed., "Pseudowire |
| 1550 |
Virtual Circuit Connectivity Verification (VCCV): A |
| 1551 |
Control Channel for Pseudowires", <a href="./rfc5085">RFC 5085</a>, |
| 1552 |
December 2007. |
| 1553 |
|
| 1554 |
[<a id="ref-RFC5654">RFC5654</a>] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., |
| 1555 |
Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS |
| 1556 |
Transport Profile", <a href="./rfc5654">RFC 5654</a>, September 2009. |
| 1557 |
|
| 1558 |
[<a id="ref-RFC5880">RFC5880</a>] Katz, D. and D. Ward, "Bidirectional Forwarding Detection |
| 1559 |
(BFD)", <a href="./rfc5880">RFC 5880</a>, June 2010. |
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">King & Venkatesan Informational [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc6639">RFC 6639</a> MPLS-TP MIB-Based Management Overview June 2012</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
[<a id="ref-RFC5884">RFC5884</a>] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, |
| 1570 |
"Bidirectional Forwarding Detection (BFD) for MPLS Label |
| 1571 |
Switched Paths (LSPs)", <a href="./rfc5884">RFC 5884</a>, June 2010. |
| 1572 |
|
| 1573 |
[<a id="ref-RFC5885">RFC5885</a>] Nadeau, T., Ed., and C. Pignataro, Ed., "Bidirectional |
| 1574 |
Forwarding Detection (BFD) for the Pseudowire Virtual |
| 1575 |
Circuit Connectivity Verification (VCCV)", <a href="./rfc5885">RFC 5885</a>, |
| 1576 |
June 2010. |
| 1577 |
|
| 1578 |
[<a id="ref-RFC5950">RFC5950</a>] Mansfield, S., Ed., Gray, E., Ed., and K. Lam, Ed., |
| 1579 |
"Network Management Framework for MPLS-based Transport |
| 1580 |
Networks", <a href="./rfc5950">RFC 5950</a>, September 2010. |
| 1581 |
|
| 1582 |
[<a id="ref-RFC5951">RFC5951</a>] Lam, K., Mansfield, S., and E. Gray, "Network Management |
| 1583 |
Requirements for MPLS-based Transport Networks", |
| 1584 |
<a href="./rfc5951">RFC 5951</a>, September 2010. |
| 1585 |
|
| 1586 |
[<a id="ref-RFC6370">RFC6370</a>] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport |
| 1587 |
Profile (MPLS-TP) Identifiers", <a href="./rfc6370">RFC 6370</a>, September 2011. |
| 1588 |
|
| 1589 |
[<a id="ref-RFC6371">RFC6371</a>] Busi, I., Ed., and D. Allan, Ed., "Operations, |
| 1590 |
Administration, and Maintenance Framework for MPLS-Based |
| 1591 |
Transport Networks", <a href="./rfc6371">RFC 6371</a>, September 2011. |
| 1592 |
|
| 1593 |
[<a id="ref-RFC6445">RFC6445</a>] Nadeau, T., Ed., Koushik, A., Ed., and R. Cetin, Ed., |
| 1594 |
"Multiprotocol Label Switching (MPLS) Traffic Engineering |
| 1595 |
Management Information Base for Fast Reroute", <a href="./rfc6445">RFC 6445</a>, |
| 1596 |
November 2011. |
| 1597 |
|
| 1598 |
Authors' Addresses |
| 1599 |
|
| 1600 |
Daniel King (editor) |
| 1601 |
Old Dog Consulting |
| 1602 |
UK |
| 1603 |
|
| 1604 |
EMail: [email protected] |
| 1605 |
|
| 1606 |
|
| 1607 |
Venkatesan Mahalingam (editor) |
| 1608 |
Aricent |
| 1609 |
India |
| 1610 |
|
| 1611 |
EMail: [email protected] |
| 1612 |
|
| 1613 |
|
| 1614 |
|
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
King & Venkatesan Informational [Page 29] |
| 1621 |
</pre> |