| 1 |
<pre>Network Working Group T. Nadeau |
| 2 |
Request for Comments: 4221 Cisco Systems, Inc. |
| 3 |
Category: Informational C. Srinivasan |
| 4 |
Bloomberg L.P. |
| 5 |
A. Farrel |
| 6 |
Old Dog Consulting |
| 7 |
November 2005 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">Multiprotocol Label Switching (MPLS) Management Overview</span> |
| 11 |
|
| 12 |
Status of This Memo |
| 13 |
|
| 14 |
This memo provides information for the Internet community. It does |
| 15 |
not specify an Internet standard of any kind. Distribution of this |
| 16 |
memo is unlimited. |
| 17 |
|
| 18 |
Copyright Notice |
| 19 |
|
| 20 |
Copyright (C) The Internet Society (2005). |
| 21 |
|
| 22 |
Abstract |
| 23 |
|
| 24 |
A range of Management Information Base (MIB) modules has been |
| 25 |
developed to help model and manage the various aspects of |
| 26 |
Multiprotocol Label Switching (MPLS) networks. These MIB modules are |
| 27 |
defined in separate documents that focus on the specific areas of |
| 28 |
responsibility of the modules that they describe. |
| 29 |
|
| 30 |
This document describes the management architecture for MPLS and |
| 31 |
indicates the interrelationships between the different MIB modules |
| 32 |
used for MPLS network management. |
| 33 |
|
| 34 |
Table of Contents |
| 35 |
|
| 36 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a> |
| 37 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a> |
| 38 |
<a href="#section-3">3</a>. The SNMP Management Framework ...................................<a href="#page-3">3</a> |
| 39 |
<a href="#section-4">4</a>. An Introduction to the MPLS Working Group MIB Modules ...........<a href="#page-4">4</a> |
| 40 |
<a href="#section-4.1">4.1</a>. Structure of the MPLS MIB OID Tree .........................<a href="#page-5">5</a> |
| 41 |
<a href="#section-4.2">4.2</a>. MPLS-TC-STD-MIB ............................................<a href="#page-5">5</a> |
| 42 |
<a href="#section-4.3">4.3</a>. MPLS-LSR-STD-MIB ...........................................<a href="#page-5">5</a> |
| 43 |
<a href="#section-4.4">4.4</a>. MPLS-LDP-STD-MIB ...........................................<a href="#page-6">6</a> |
| 44 |
<a href="#section-4.5">4.5</a>. MPLS-LDP-GENERIC-STD-MIB ...................................<a href="#page-6">6</a> |
| 45 |
<a href="#section-4.6">4.6</a>. MPLS-LDP-ATM-STD-MIB .......................................<a href="#page-6">6</a> |
| 46 |
<a href="#section-4.7">4.7</a>. MPLS-LDP-FRAME-RELAY-STD-MIB ...............................<a href="#page-7">7</a> |
| 47 |
<a href="#section-4.8">4.8</a>. MPLS-TE-STD-MIB ............................................<a href="#page-7">7</a> |
| 48 |
<a href="#section-4.9">4.9</a>. MPLS-FTN-STD-MIB ...........................................<a href="#page-7">7</a> |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Nadeau, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 55 |
|
| 56 |
|
| 57 |
<a href="#section-4.10">4.10</a>. TE-LINK-STD-MIB ...........................................<a href="#page-7">7</a> |
| 58 |
<a href="#section-4.11">4.11</a>. MIB Module Interdependencies ..............................<a href="#page-8">8</a> |
| 59 |
<a href="#section-4.12">4.12</a>. Dependencies on External MIB Modules ......................<a href="#page-9">9</a> |
| 60 |
<a href="#section-5">5</a>. Tables, Scalars, and Notifications in MPLS-LSR-STD-MIB .........<a href="#page-10">10</a> |
| 61 |
<a href="#section-5.1">5.1</a>. Tables ....................................................<a href="#page-10">10</a> |
| 62 |
<a href="#section-5.2">5.2</a>. Scalars ...................................................<a href="#page-10">10</a> |
| 63 |
<a href="#section-5.3">5.3</a>. Indexing ..................................................<a href="#page-11">11</a> |
| 64 |
<a href="#section-5.4">5.4</a>. Notifications .............................................<a href="#page-12">12</a> |
| 65 |
<a href="#section-5.5">5.5</a>. Dependencies between MIB Module Tables ....................<a href="#page-12">12</a> |
| 66 |
<a href="#section-6">6</a>. Tables, Scalars, and Notifications in the LDP MIB ..............<a href="#page-13">13</a> |
| 67 |
<a href="#section-6.1">6.1</a>. MIB Modules ...............................................<a href="#page-13">13</a> |
| 68 |
<a href="#section-6.2">6.2</a>. Tables ....................................................<a href="#page-14">14</a> |
| 69 |
<a href="#section-6.3">6.3</a>. Scalars ...................................................<a href="#page-15">15</a> |
| 70 |
<a href="#section-6.4">6.4</a>. Notifications .............................................<a href="#page-15">15</a> |
| 71 |
<a href="#section-6.5">6.5</a>. Dependencies between MIB Module Tables ....................<a href="#page-15">15</a> |
| 72 |
<a href="#section-7">7</a>. Tables, Scalars, and Notifications in MPLS-TE-STD-MIB ..........<a href="#page-16">16</a> |
| 73 |
<a href="#section-7.1">7.1</a>. Tables ....................................................<a href="#page-16">16</a> |
| 74 |
<a href="#section-7.2">7.2</a>. Scalars ...................................................<a href="#page-17">17</a> |
| 75 |
<a href="#section-7.3">7.3</a>. Notifications .............................................<a href="#page-18">18</a> |
| 76 |
<a href="#section-7.4">7.4</a>. Dependencies between MIB Module Tables ....................<a href="#page-18">18</a> |
| 77 |
<a href="#section-8">8</a>. Tables, Scalars, and Notifications in MPLS-FTN-STD-MIB .........<a href="#page-18">18</a> |
| 78 |
<a href="#section-8.1">8.1</a>. Tables ....................................................<a href="#page-18">18</a> |
| 79 |
<a href="#section-8.2">8.2</a>. Scalars ...................................................<a href="#page-19">19</a> |
| 80 |
<a href="#section-8.3">8.3</a>. Notifications .............................................<a href="#page-19">19</a> |
| 81 |
<a href="#section-8.4">8.4</a>. Dependencies between MIB Module Tables ....................<a href="#page-19">19</a> |
| 82 |
<a href="#section-9">9</a>. Tables and Objects in TE-LINK-STD-MIB ..........................<a href="#page-19">19</a> |
| 83 |
<a href="#section-9.1">9.1</a>. Tables ....................................................<a href="#page-19">19</a> |
| 84 |
<a href="#section-9.2">9.2</a>. Scalars ...................................................<a href="#page-20">20</a> |
| 85 |
<a href="#section-9.3">9.3</a>. Notifications .............................................<a href="#page-20">20</a> |
| 86 |
<a href="#section-9.4">9.4</a>. Dependencies between MIB Module Tables ....................<a href="#page-20">20</a> |
| 87 |
<a href="#section-10">10</a>. Table Dependencies between MPLS MIB Modules ...................<a href="#page-21">21</a> |
| 88 |
<a href="#section-11">11</a>. A Note on Interfaces ..........................................<a href="#page-21">21</a> |
| 89 |
<a href="#section-11.1">11.1</a>. MPLS Tunnels as Interfaces ...............................<a href="#page-21">21</a> |
| 90 |
<a href="#section-11.2">11.2</a>. Application of the Interfaces Group to TE Links ..........<a href="#page-22">22</a> |
| 91 |
11.3. References to Interface MIB Objects from MPLS MIB |
| 92 |
Modules ..................................................<a href="#page-23">23</a> |
| 93 |
<a href="#section-12">12</a>. Management Options ............................................<a href="#page-24">24</a> |
| 94 |
<a href="#section-13">13</a>. Related IETF MIB Modules ......................................<a href="#page-25">25</a> |
| 95 |
<a href="#section-13.1">13.1</a>. PWE3 Working Group MIB Modules ...........................<a href="#page-26">26</a> |
| 96 |
<a href="#section-13.2">13.2</a>. PPVPN Working Group MIB Modules ..........................<a href="#page-26">26</a> |
| 97 |
<a href="#section-13.2.1">13.2.1</a>. PPVPN-MPLS-VPN-STD-MIB ............................<a href="#page-26">26</a> |
| 98 |
<a href="#section-13.3">13.3</a>. CCAMP Working Group MIB Modules ..........................<a href="#page-26">26</a> |
| 99 |
<a href="#section-14">14</a>. Traffic Engineering Working Group TE MIB ......................<a href="#page-27">27</a> |
| 100 |
<a href="#section-14.1">14.1</a>. Choosing between TE MIB Modules ..........................<a href="#page-27">27</a> |
| 101 |
<a href="#section-15">15</a>. Security Considerations .......................................<a href="#page-28">28</a> |
| 102 |
<a href="#section-16">16</a>. Acknowledgements ..............................................<a href="#page-28">28</a> |
| 103 |
<a href="#section-17">17</a>. Normative References ..........................................<a href="#page-29">29</a> |
| 104 |
<a href="#section-18">18</a>. Informative References ........................................<a href="#page-30">30</a> |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Nadeau, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
This document describes the Management Architecture for Multi- |
| 116 |
Protocol Label Switching (MPLS) [<a href="./rfc3031" title=""Multiprotocol Label Switching Architecture"">RFC3031</a>]. In particular, it |
| 117 |
describes how the managed objects defined in various MPLS-related |
| 118 |
Management Information Base (MIB) documents model different aspects |
| 119 |
of MPLS. Furthermore, this document explains the interactions and |
| 120 |
dependencies between each of these MIB modules. |
| 121 |
|
| 122 |
For additional information, this document also includes a brief note |
| 123 |
on MIB modules produced by the Pseudo Wire Emulation Edge to Edge |
| 124 |
(PWE3), Provider Provisioned Virtual Private Network (PPVPN), Common |
| 125 |
Control and Measurement Plane (CCAMP), and Internet Traffic |
| 126 |
Engineering (TEWG) working groups. |
| 127 |
|
| 128 |
The document begins with a brief outline of the SNMP framework. This |
| 129 |
is not intended to be a complete reference on SNMP, but is provided |
| 130 |
to give context to the rest of the document and to indicate reference |
| 131 |
material for readers that need to know more about SNMP. |
| 132 |
|
| 133 |
This document does not propose any additions to the MPLS MIB |
| 134 |
framework, nor define any standards for the Internet community. It |
| 135 |
is an informational document. In all cases, the reader is advised to |
| 136 |
turn to the document that defines the MIB module in question for |
| 137 |
further information. |
| 138 |
|
| 139 |
Comments should be made directly to the MPLS mailing list at |
| 140 |
[email protected]. |
| 141 |
|
| 142 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 143 |
|
| 144 |
This document uses terminology from the MPLS architecture document |
| 145 |
[<a href="./rfc3031" title=""Multiprotocol Label Switching Architecture"">RFC3031</a>] and the following MPLS related MIB modules: MPLS TC MIB |
| 146 |
[<a href="#ref-TCMIB" title=""Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management"">TCMIB</a>], MPLS LSR MIB [<a href="#ref-LSRMIB" title=""Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)"">LSRMIB</a>], MPLS TE MIB [<a href="#ref-TEMIB" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">TEMIB</a>], MPLS LDP MIB |
| 147 |
[<a href="#ref-LDPMIB" title=""Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)"">LDPMIB</a>], MPLS FTN MIB [<a href="#ref-FTNMIB" title=""Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)"">FTNMIB</a>], TE LINK MIB [<a href="#ref-TELMIB" title=""Traffic Engineering Link Management Information Base"">TELMIB</a>], and PPVPN MPLS |
| 148 |
VPN MIB [<a href="#ref-VPNMIB" title=""MPLS/BGP Virtual Private Network Management Information Base Using SMIv2"">VPNMIB</a>]. |
| 149 |
|
| 150 |
Throughout this document hyphenated MIB names (such as MPLS-TE-STD- |
| 151 |
MIB) should be taken to refer to specific MIB modules. Non- |
| 152 |
hyphenated MIB names (such as MPLS LDP MIB) indicate MIB documents. |
| 153 |
|
| 154 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The SNMP Management Framework</span> |
| 155 |
|
| 156 |
For a detailed overview of the documents that describe the current |
| 157 |
Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">section 7 of |
| 158 |
RFC 3410</a> [<a href="./rfc3410" title=""Introduction and Applicability Statements for Internet-Standard Management Framework"">RFC3410</a>]. |
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Nadeau, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 167 |
|
| 168 |
|
| 169 |
Managed objects are accessed via a virtual information store, termed |
| 170 |
the Management Information Base or MIB. MIB objects are generally |
| 171 |
accessed through the Simple Network Management Protocol (SNMP). |
| 172 |
Objects in the MIB are defined using the mechanisms defined in the |
| 173 |
Structure of Management Information (SMI). This document specifies a |
| 174 |
MIB module that is compliant to the SMIv2, which is described in STD |
| 175 |
58, <a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>], STD 58, <a href="./rfc2579">RFC 2579</a> [<a href="./rfc2579" title=""Textual Conventions for SMIv2"">RFC2579</a>] and STD 58, <a href="./rfc2580">RFC</a> |
| 176 |
<a href="./rfc2580">2580</a> [<a href="./rfc2580" title=""Conformance Statements for SMIv2"">RFC2580</a>]. |
| 177 |
|
| 178 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. An Introduction to the MPLS Working Group MIB Modules</span> |
| 179 |
|
| 180 |
This section addresses the MIB documents produced by the MPLS working |
| 181 |
group, namely MPLS TC MIB, MPLS LSR MIB, MPLS TE MIB, MPLS LDP MIB, |
| 182 |
MPLS FTN MIB, and TE LINK MIB. The rest of this section briefly |
| 183 |
describes the following: |
| 184 |
|
| 185 |
- the MPLS Object Identifier (OID) tree structure and the position |
| 186 |
of different MPLS related MIB modules on this tree; |
| 187 |
|
| 188 |
- the purpose of each of the MIB modules within the MIB documents, |
| 189 |
what it can be used for, and how it relates to the other MIB |
| 190 |
modules. |
| 191 |
|
| 192 |
Note that each MIB document contains one or more compliance |
| 193 |
statements for the modules and objects that it defines. Therefore, |
| 194 |
the support for the different MIB modules and objects is beyond the |
| 195 |
scope of this document, although some recommendations are included in |
| 196 |
the sections that follow. |
| 197 |
|
| 198 |
|
| 199 |
|
| 200 |
|
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
|
| 205 |
|
| 206 |
|
| 207 |
|
| 208 |
|
| 209 |
|
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Nadeau, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Structure of the MPLS MIB OID Tree</span> |
| 226 |
|
| 227 |
The MPLS MIB OID tree has the following structure. |
| 228 |
|
| 229 |
transmission -- <a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>] |
| 230 |
| |
| 231 |
+- mplsStdMIB -- MPLS-TC-STD-MIB |
| 232 |
| | |
| 233 |
| +- mplsTCStdMIB -- MPLS-TC-STD-MIB |
| 234 |
| | |
| 235 |
| +- mplsLsrStdMIB -- MPLS-LSR-STD-MIB |
| 236 |
| | |
| 237 |
| +- mplsTeStdMIB -- MPLS-TE-STD-MIB |
| 238 |
| | |
| 239 |
| +- mplsLdpStdMIB -- MPLS-LDP-STD-MIB |
| 240 |
| | |
| 241 |
| +- mplsLdpAtmStdMIB -- MPLS-LDP-ATM-STD-MIB |
| 242 |
| | |
| 243 |
| +- mplsLdpFrameRelayStdMIB -- MPLS-LDP-FRAME-RELAY-STD-MIB |
| 244 |
| | |
| 245 |
| +- mplsLdpGenericStdMIB -- MPLS-LDP-GENERIC-STD-MIB |
| 246 |
| | |
| 247 |
| +- mplsFTNStdMIB -- MPLS-FTN-STD-MIB |
| 248 |
| |
| 249 |
+- teLinkStdMIB -- TE-LINK-STD-MIB |
| 250 |
|
| 251 |
Note: The OIDs for MIB modules are assigned and managed by IANA. |
| 252 |
They can be found in the referenced MIB documents. |
| 253 |
|
| 254 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. MPLS-TC-STD-MIB</span> |
| 255 |
|
| 256 |
MPLS-TC-STD-MIB defines textual conventions [<a href="./rfc2579" title=""Textual Conventions for SMIv2"">RFC2579</a>] that may be |
| 257 |
common to MPLS-related MIB modules. These conventions allow multiple |
| 258 |
MIB modules to use the same syntax and format for a concept that is |
| 259 |
shared between the MIB modules. |
| 260 |
|
| 261 |
For example, labels are a central part of MPLS and need to be |
| 262 |
presented in many of the MIB modules. The textual convention for |
| 263 |
representing an MPLS label is defined in MPLS-TC-STD-MIB. |
| 264 |
|
| 265 |
All of the other MPLS MIB modules import textual conventions from |
| 266 |
this MIB module. |
| 267 |
|
| 268 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. MPLS-LSR-STD-MIB</span> |
| 269 |
|
| 270 |
MPLS-LSR-STD-MIB describes managed objects for modeling an MPLS Label |
| 271 |
Switching Router (LSR). This puts it at the heart of the management |
| 272 |
architecture for MPLS. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Nadeau, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 279 |
|
| 280 |
|
| 281 |
This MIB module is used to model and manage the basic label switching |
| 282 |
behavior of an MPLS LSR. It represents the label forwarding |
| 283 |
information base (LFIB) of the LSR and provides a view of the LSPs |
| 284 |
that are being switched by the LSR in question. |
| 285 |
|
| 286 |
Since basic MPLS label switching is common to all MPLS applications, |
| 287 |
this MIB module is referenced by many of the other MPLS MIB modules. |
| 288 |
|
| 289 |
In general, MPLS-LSR-STD-MIB provides a model of incoming labels on |
| 290 |
MPLS-enabled interfaces being mapped to outgoing labels on MPLS- |
| 291 |
enabled interfaces via a conceptual object called an MPLS cross- |
| 292 |
connect. MPLS cross-connect entries and their properties are |
| 293 |
represented in MPLS-LSR-STD-MIB and are typically referenced by other |
| 294 |
MIB modules in order to refer to the underlying MPLS LSP. |
| 295 |
|
| 296 |
For example, MPLS-TE-STD-MIB models traffic-engineered tunnels. |
| 297 |
These tunnels map to one or more underlying MPLS LSPs. MPLS-TE-STD- |
| 298 |
MIB refers to the underlying LSPs by pointing to cross-connect |
| 299 |
entries in MPLS-LSR-STD-MIB. |
| 300 |
|
| 301 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. MPLS-LDP-STD-MIB</span> |
| 302 |
|
| 303 |
MPLS-LDP-STD-MIB describes managed objects used to model and manage |
| 304 |
the MPLS Label Distribution Protocol (LDP) [<a href="./rfc3036" title=""LDP Specification"">RFC3036</a>]. LDP is one of |
| 305 |
the MPLS protocols used to distribute labels and establish LSPs. |
| 306 |
|
| 307 |
This MIB module contains objects common to all LDP implementations. |
| 308 |
For an LDP implementation that provides standard MIB support, this |
| 309 |
MIB module provides the core set of objects that are needed, along |
| 310 |
with one or more of the other LDP MIB modules from the following |
| 311 |
sections. |
| 312 |
|
| 313 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. MPLS-LDP-GENERIC-STD-MIB</span> |
| 314 |
|
| 315 |
This MIB module provides objects for managing the LDP Per Platform |
| 316 |
Label Space and is typically implemented along with the MPLS-LDP- |
| 317 |
STD-MIB module. This MIB Module contains tables for configuring MPLS |
| 318 |
Generic Label Ranges. Although the LDP Specification does not |
| 319 |
provide a way to configure Label Ranges for Generic Labels, the MIB |
| 320 |
module does provide a way to reserve a range of generic labels |
| 321 |
because the working group thought this was useful. |
| 322 |
|
| 323 |
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. MPLS-LDP-ATM-STD-MIB</span> |
| 324 |
|
| 325 |
This MIB module is typically supported along with MPLS-LDP-STD-MIB by |
| 326 |
LDP implementations if LDP uses ATM as the Layer 2 medium. Tables in |
| 327 |
this MIB module allow for configuring LDP to use ATM. |
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Nadeau, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. MPLS-LDP-FRAME-RELAY-STD-MIB</span> |
| 338 |
|
| 339 |
This MIB module is typically supported along with MPLS-LDP-STD-MIB by |
| 340 |
LDP implementations if LDP uses Frame Relay as the Layer 2 medium. |
| 341 |
Tables in this MIB module allow for configuration of LDP to use Frame |
| 342 |
Relay. |
| 343 |
|
| 344 |
<span class="h3"><a class="selflink" id="section-4.8" href="#section-4.8">4.8</a>. MPLS-TE-STD-MIB</span> |
| 345 |
|
| 346 |
MPLS-TE-STD-MIB describes managed objects that are used to model and |
| 347 |
manage MPLS Traffic Engineered (TE) Tunnels. |
| 348 |
|
| 349 |
This MIB module is based on a table that represents TE tunnels that |
| 350 |
either originate from, traverse via, or terminate on the LSR in |
| 351 |
question. The MIB module provides configuration and statistics |
| 352 |
objects needed for TE tunnels. |
| 353 |
|
| 354 |
<span class="h3"><a class="selflink" id="section-4.9" href="#section-4.9">4.9</a>. MPLS-FTN-STD-MIB</span> |
| 355 |
|
| 356 |
MPLS-FTN-STD-MIB describes managed objects that are used to model and |
| 357 |
manage the MPLS FEC-to-NHLFE (FTN) mappings that take place at an |
| 358 |
ingress Label Edge Router (LER). |
| 359 |
|
| 360 |
An LER is an LSR placed at the edge of an MPLS domain, and it passes |
| 361 |
traffic into and out of the MPLS domain. An ingress LER is |
| 362 |
responsible for classifying data and assigning it to a suitable LSP |
| 363 |
or tunnel. |
| 364 |
|
| 365 |
This classification is done using Forwarding Equivalence Classes |
| 366 |
(FECs) that define the common attributes of data (usually packets) |
| 367 |
that will be treated in the same way. Once data has been classified, |
| 368 |
it can be handed off to an LSP or tunnel through the Next Hop Label |
| 369 |
Forwarding Entry (NHLFE). |
| 370 |
|
| 371 |
In the case of an IP-to-MPLS mapping, the FEC objects describe IP |
| 372 |
6-tuples that represent source and destination address ranges, source |
| 373 |
and destination port ranges, the IPv4 Protocol field or IPv6 next- |
| 374 |
header field, and the DiffServ Code Point (DSCP). |
| 375 |
|
| 376 |
<span class="h3"><a class="selflink" id="section-4.10" href="#section-4.10">4.10</a>. TE-LINK-STD-MIB</span> |
| 377 |
|
| 378 |
TE-LINK-STD-MIB describes managed objects that are used to model and |
| 379 |
manage TE links, including bundled links, in an MPLS network. |
| 380 |
|
| 381 |
The TE link feature is designed to aggregate one or more similar data |
| 382 |
channels or TE links between a pair of LSRs. A TE link is a sub- |
| 383 |
interface capable of carrying traffic-engineered MPLS traffic. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Nadeau, et al. Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 391 |
|
| 392 |
|
| 393 |
A bundled link is a sub-interface that bonds the traffic of a group |
| 394 |
of one or more TE links. |
| 395 |
|
| 396 |
<span class="h3"><a class="selflink" id="section-4.11" href="#section-4.11">4.11</a>. MIB Module Interdependencies</span> |
| 397 |
|
| 398 |
This section provides an overview of the relationship between the |
| 399 |
MPLS MIB modules described above. More details of these |
| 400 |
relationships are given below after the MIB modules have been |
| 401 |
discussed in more detail. |
| 402 |
|
| 403 |
The arrows in the following diagram show a 'depends on' relationship. |
| 404 |
A relationship "MIB module A depends on MIB module B" means that MIB |
| 405 |
module A uses an object, object identifier, or textual convention |
| 406 |
defined in MIB module B, or that MIB module A contains a pointer |
| 407 |
(index or RowPointer) to an object in MIB module B. |
| 408 |
|
| 409 |
+-------> MPLS-TC-STD-MIB |
| 410 |
| ^ |
| 411 |
| | |
| 412 |
| MPLS-LSR-STD-MIB <------------------+ |
| 413 |
| | |
| 414 |
+<----------------------- MPLS-LDP-STD-MIB -->+ |
| 415 |
| ^ | |
| 416 |
| | | |
| 417 |
+<-- MPLS-LDP-GENERIC-STD-MIB ------>+ | |
| 418 |
| | | |
| 419 |
+<-- MPLS-LDP-ATM-STD-MIB ---------->+ | |
| 420 |
| | | |
| 421 |
+<-- MPLS-LDP-FRAME-RELAY-STD-MIB -->+ | |
| 422 |
| | |
| 423 |
+<------- MPLS-TE-STD-MIB ------------------->+ |
| 424 |
| ^ | |
| 425 |
| | | |
| 426 |
+<------- MPLS-FTN-STD-MIB ------------------>+ |
| 427 |
|
| 428 |
Thus: |
| 429 |
|
| 430 |
- All the MPLS MIB modules depend on MPLS-TC-STD-MIB. |
| 431 |
|
| 432 |
- MPLS-LDP-STD-MIB, MPLS-TE-STD-MIB, and MPLS-FTN-STD-MIB contain |
| 433 |
references to objects in MPLS-LSR-STD-MIB. |
| 434 |
|
| 435 |
- MPLS-LDP-GENERIC-STD-MIB, MPLS-LDP-ATM-STD-MIB, and MPLS-LDP- |
| 436 |
FRAME-RELAY-STD-MIB contain references to objects in MPLS-LDP- |
| 437 |
STD-MIB. |
| 438 |
|
| 439 |
- MPLS-FTN-STD-MIB contains references to objects in MPLS-TE-STD- |
| 440 |
MIB. |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Nadeau, et al. Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 447 |
|
| 448 |
|
| 449 |
Note that there is a textual convention (MplsIndexType) defined in |
| 450 |
MPLS-LSR-STD-MIB that is imported by MPLS-LDP-STD-MIB. |
| 451 |
|
| 452 |
<span class="h3"><a class="selflink" id="section-4.12" href="#section-4.12">4.12</a>. Dependencies on External MIB Modules</span> |
| 453 |
|
| 454 |
With the exception of MPLS-TC-STD-MIB, all the MPLS MIB modules have |
| 455 |
dependencies on the Interfaces MIB [<a href="./rfc2863" title=""The Interfaces Group MIB "">RFC2863</a>]. MPLS-FTN-STD-MIB |
| 456 |
references IP-capable interfaces on which received traffic is to be |
| 457 |
classified using indexes in the Interface Table (ifTable) of IF-MIB |
| 458 |
[<a href="./rfc2863" title=""The Interfaces Group MIB "">RFC2863</a>]. The other MPLS MIB modules reference MPLS-capable |
| 459 |
interfaces in ifTable. |
| 460 |
|
| 461 |
The Interfaces Group of IF-MIB [<a href="./rfc2863" title=""The Interfaces Group MIB "">RFC2863</a>] defines generic managed |
| 462 |
objects for managing interfaces. The MPLS MIB modules contain |
| 463 |
media-specific extensions to the Interfaces Group for managing MPLS |
| 464 |
interfaces. |
| 465 |
|
| 466 |
The MPLS MIB modules assume the interpretation of the Interfaces |
| 467 |
Group to be in accordance with [<a href="./rfc2863" title=""The Interfaces Group MIB "">RFC2863</a>], which states that ifTable |
| 468 |
contains information on the managed resource's interfaces and that |
| 469 |
each sub-layer below the internetwork layer of a network interface is |
| 470 |
considered an interface. Thus, the MPLS interface is represented as |
| 471 |
an entry in ifTable. |
| 472 |
|
| 473 |
The interrelation of entries in ifTable is defined by the Interfaces |
| 474 |
Stack Group defined in [<a href="./rfc2863" title=""The Interfaces Group MIB "">RFC2863</a>]. |
| 475 |
|
| 476 |
Additionally, MPLS-LDP-ATM-STD-MIB imports the textual convention |
| 477 |
AtmVpIdentifier from ATM-TC-MIB to represent an ATM virtual path |
| 478 |
identifier, whereas MPLS-LDP-FRAME-RELAY-STD-MIB imports the textual |
| 479 |
convention DLCI from FRAME-RELAY-DTE-MIB to represent a Data Link |
| 480 |
Channel identifier. |
| 481 |
|
| 482 |
MPLS-LDP-STD-MIB imports the textual conventions IndexInteger and |
| 483 |
IndexIntegerNextFree from [<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>], and MPLS-TE-STD-MIB imports |
| 484 |
IndexIntegerNextFree. IndexInteger provides a standard arbitrary |
| 485 |
index, whereas IndexIntegerNextFree is used by a management agent |
| 486 |
that needs to select an appropriate value for an arbitrary index. |
| 487 |
|
| 488 |
Finally, all of the MIB modules import standard textual conventions |
| 489 |
such as integers, strings, timestamps, etc., from the MIB modules in |
| 490 |
which they are defined. This is business as usual for a MIB module |
| 491 |
and is not discussed further in this document. |
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Nadeau, et al. Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Tables, Scalars, and Notifications in MPLS-LSR-STD-MIB</span> |
| 506 |
|
| 507 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Tables</span> |
| 508 |
|
| 509 |
MPLS-LSR-STD-MIB contains the following tables. |
| 510 |
|
| 511 |
- The interface configuration table (mplsInterfaceTable) is used for |
| 512 |
enabling MPLS on MPLS-capable interfaces. |
| 513 |
|
| 514 |
- The in-segment (mplsInSegmentTable) and out-segment |
| 515 |
(mplsOutSegmentTable) tables are used to configure and monitor LSP |
| 516 |
segments carrying data into and out of the LSR, respectively. |
| 517 |
|
| 518 |
- The in-segment mapping table (mplsInSegmentMapTable) provides a |
| 519 |
look-up table that enables the discovery of an in-segment in |
| 520 |
mplsInSegmentTable from the known incoming interface and incoming |
| 521 |
label. |
| 522 |
|
| 523 |
- The cross-connect table (mplsXCTable) is used to associate in and |
| 524 |
out segments in order to form a cross-connect (i.e., to represent |
| 525 |
an LSP transiting the LSR). |
| 526 |
|
| 527 |
- The label stack table (mplsLabelStackTable) allows the |
| 528 |
specification of multi-label stacks to be imposed on a given LSP |
| 529 |
at this LSR. |
| 530 |
|
| 531 |
- The MPLS in-segment (mplsInSegmentPerfTable) and out-segment |
| 532 |
(mplsOutSegmentPerfTable) performance tables contain objects to |
| 533 |
measure the performance of LSPs. |
| 534 |
|
| 535 |
- The MPLS interface performance table (mplsInterfacePerfTable) has |
| 536 |
objects to measure MPLS performance on a per-interface basis. |
| 537 |
|
| 538 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Scalars</span> |
| 539 |
|
| 540 |
Where tables in the MIB module have arbitrary indexes, scalars are |
| 541 |
provided to supply the next available index. This applies to |
| 542 |
mplsInSegmentTable, mplsOutSegmentTable, mplsXCTable, and |
| 543 |
mplsLabelStackTable, but see the section on indexing, below. |
| 544 |
|
| 545 |
mplsMaxLabelStackDepth defines the maximum size of a imposed label |
| 546 |
stack supported at this LSR (and not, as the description in MPLS- |
| 547 |
LSR-STD-MIB states, the maximum label stack depth supported by the |
| 548 |
LSR). |
| 549 |
|
| 550 |
mplsXCNotificationsEnable is used to enable and disable notifications |
| 551 |
from MPLS-LSR-STD-MIB. |
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Nadeau, et al. Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Indexing</span> |
| 562 |
|
| 563 |
Note that the indexing used by the tables in MPLS-LSR-STD-MIB is |
| 564 |
unusual. A specific textual convention, MplsIndexType, is defined in |
| 565 |
the MIB module and is used as the type for indexes to |
| 566 |
mplsInSegmentTable, mplsOutSegmentTable, mplsXCTable, and |
| 567 |
mplsLabelStackTable. The textual convention is defined as an octet |
| 568 |
string of between one and twenty-four octets, inclusive. |
| 569 |
|
| 570 |
Although this convention can be used to map simple integers and so |
| 571 |
preserve the normal indexing techniques, it may also be used to |
| 572 |
encode more complex indexing rules that may be useful to |
| 573 |
implementations that subdivide their label spaces according to |
| 574 |
physical or implementation constraints (such as placing the |
| 575 |
responsibility for a subset of labels with a line card). |
| 576 |
|
| 577 |
Note that it would be unusual, but not impossible, to make |
| 578 |
sophisticated use of these indexes in a write-access MIB since the |
| 579 |
'next' index value would be hard to determine. Thus, non-simple |
| 580 |
values are likely only to be used in read-only MIBs in which the |
| 581 |
indexes are generated as a result of signaling protocol |
| 582 |
implementations or other configuration means. The formatting and |
| 583 |
interpretation of non-simple indexes is out of the scope of the MIB |
| 584 |
module definition and is expected to be part of the manageability |
| 585 |
statement for a particular device. When the formatting is not known |
| 586 |
by an agent, it should treat the index as a plain octet string |
| 587 |
containing an integer of between one and twenty-four octets. |
| 588 |
|
| 589 |
As described in the previous section, scalars are provided to allow |
| 590 |
agents to discover a suitable value to use as an index when creating |
| 591 |
a new row in one of these tables. These scalars all use a second |
| 592 |
textual convention, MplsIndexNextType, also defined within MPLS-LSR- |
| 593 |
STD-MIB. This textual convention allows the 'null string', (that is, |
| 594 |
a string of length one octet with value 0x00). The null string is |
| 595 |
used to indicate that either write access is not supported or no more |
| 596 |
indexes are currently available. |
| 597 |
|
| 598 |
Note that the usage of the nextIndex scalars is such that at any time |
| 599 |
a scalar supplies a value that is currently unused as an index to the |
| 600 |
specific table. In order to avoid lacunae in the indexing of a table |
| 601 |
under normal usage, implementations are recommended to change the |
| 602 |
value in an nextIndex scalar only when the index is used (that is, |
| 603 |
when a row is created) and not when the nextIndex scalar is read. In |
| 604 |
a 'busy' table, this may result in row creation attempts failing and |
| 605 |
agents having to re-read the scalar before making a second row |
| 606 |
creation attempt. The desire to avoid this issue is in opposition to |
| 607 |
the desire to avoid lacunae. |
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Nadeau, et al. Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Notifications</span> |
| 618 |
|
| 619 |
MPLS-LSR-STD-MIB can issue two notifications (if notifications are |
| 620 |
enabled). |
| 621 |
|
| 622 |
- mplsXCUp reports when a cross-connect becomes active. |
| 623 |
|
| 624 |
- mplsXCDown reports when a cross-connect becomes |
| 625 |
inactive. |
| 626 |
|
| 627 |
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Dependencies between MIB Module Tables</span> |
| 628 |
|
| 629 |
The tables in MPLS-LSR-STD-MIB are related as shown on the diagram |
| 630 |
below. The arrows indicate a reference from one table to another. |
| 631 |
|
| 632 |
Note that the various MIB tables contain two instances of pointers to |
| 633 |
external tables that are not currently defined. Entries in an |
| 634 |
external Traffic Parameters Table (external_Traffic_Table) are |
| 635 |
pointed to using RowPointers from the mplsInSegmentTable |
| 636 |
(mplsInSegmentTrafficParamPtr) and from the mplsOutSegmentTable |
| 637 |
(mplsOutSegmentTrafficParamPtr) to allow representation of the |
| 638 |
traffic parameters for the MPLS segment. Alternatively, the pointers |
| 639 |
may indicate an entry in the Tunnel Resource Table |
| 640 |
(mplsTunnelResourceTable) in MPLS-TE-STD-MIB. Similarly, an external |
| 641 |
label table may be used to store label values if, for some reason, |
| 642 |
they are not stored in place within the LSR MIB tables. This might |
| 643 |
occur if extra per-label space information needs to be stored, and it |
| 644 |
paves the way for GMPLS where labels cannot always be stored in a |
| 645 |
32-bit value. RowPointers are used from the mplsInSegmentTable |
| 646 |
(mplsInSegmentLabelPtr), the mplsOutSegmentTable |
| 647 |
(mplsOutSegmentTopLabelPtr), and from the mplsLabelStackTable |
| 648 |
(mplsLabelStackLabelPtr). |
| 649 |
|
| 650 |
|
| 651 |
|
| 652 |
|
| 653 |
|
| 654 |
|
| 655 |
|
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Nadeau, et al. Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 671 |
|
| 672 |
|
| 673 |
mplsInterfacePerfTable |
| 674 |
^ |
| 675 |
| |
| 676 |
V |
| 677 |
mplsInterfaceTable |
| 678 |
^ ^ |
| 679 |
mplsInSegmentMapTable | | mplsLabelStackTable |
| 680 |
| | | ^ | |
| 681 |
| +----+ +----+ | | |
| 682 |
| | | | | |
| 683 |
| | external_Traffic_Table | | | |
| 684 |
| | ^ ^ | | | |
| 685 |
V | | | | | | |
| 686 |
mplsInSegmentTable mplsOutSegmentTable | |
| 687 |
| ^ ^ ^ ^ | | |
| 688 |
| | | | | | V |
| 689 |
+------+ | +----> mplsXCTable <----+ | +--+ |
| 690 |
| V V | |
| 691 |
| mplsInSegmentPerfTable mplsOutSegmentPerfTable | |
| 692 |
| | |
| 693 |
+--------------> external_Label_Table <-------------+ |
| 694 |
|
| 695 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Tables, Scalars, and Notifications in the LDP MIB</span> |
| 696 |
|
| 697 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. MIB Modules</span> |
| 698 |
|
| 699 |
The MIB document for LDP contains four MIB modules. This structure |
| 700 |
makes it easier for an implementation to select only those modules |
| 701 |
that are relevant to it. The MIB Modules are MPLS-LDP-STD-MIB, |
| 702 |
MPLS-LDP-GENERIC-STD-MIB, MPLS-LDP-ATM-STD-MIB, and MPLS-LDP-FRAME- |
| 703 |
RELAY-STD-MIB. |
| 704 |
|
| 705 |
MPLS-LDP-STD-MIB defines objects that are specific to LDP without any |
| 706 |
Layer 2 objects. MPLS-LDP-GENERIC-STD-MIB defines Layer 2 Per |
| 707 |
Platform Label Space objects for use with MPLS-LDP-STD-MIB and for |
| 708 |
use on Ethernet. MPLS-LDP-ATM-STD-MIB defines Layer 2 Asynchronous |
| 709 |
Transfer Mode (ATM) objects for use with MPLS-LDP-STD-MIB. MPLS- |
| 710 |
LDP-FRAME-RELAY-STD-MIB defines Layer 2 FRAME-RELAY objects for use |
| 711 |
with MPLS-LDP-STD-MIB. |
| 712 |
|
| 713 |
The MPLS-LDP-STD-MIB module provides the core support and is |
| 714 |
typically supported along with at least one of the Layer 2 MIB |
| 715 |
modules. |
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Nadeau, et al. Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Tables</span> |
| 730 |
|
| 731 |
The tables in the LDP MIB for configuring the LDP behavior of an LSR |
| 732 |
are as follows. |
| 733 |
|
| 734 |
- The LDP Entity Table (mplsLdpEntityTable) provides a way to |
| 735 |
configure the LSR for using LDP. There must be at least one LDP |
| 736 |
Entity for the LSR to support LDP. Each entry/row in this table |
| 737 |
represents a single LDP Entity. |
| 738 |
|
| 739 |
- Several tables exist to help configure LDP's use of labels. These |
| 740 |
are spread through the MIB modules described in the previous |
| 741 |
section. They are: mplsLdpEntityGenLRTable, |
| 742 |
mplsLdpEntityAtmParmsTable and mplsLdpEntityAtmLRTable, |
| 743 |
mplsLdpEntityFrameRelayParmsTable and mplsLdpEntityFrLRTable. |
| 744 |
They are used to configure generic, ATM, and Frame Relay labels as |
| 745 |
their names suggest. |
| 746 |
|
| 747 |
- The LDP Peer Table (mplsLdpPeerTable) is a read-only table that |
| 748 |
contains information about LDP Peers known to LDP Entities. |
| 749 |
|
| 750 |
- The LDP Hello Adjacencies Table (mplsLdpHelloAdjacencyTable) is a |
| 751 |
table of all adjacencies between all LDP Entities and all LDP |
| 752 |
Peers. |
| 753 |
|
| 754 |
- Several tables exist to monitor and control LDP sessions. The LDP |
| 755 |
Session Table (mplsLdpSessionTable) represents sessions between an |
| 756 |
LDP Entity and a Peer. mplsLdpAtmSesTable and |
| 757 |
mplsLdpFrameRelaySesTable contain session information specific to |
| 758 |
ATM. |
| 759 |
|
| 760 |
- The MPLS LDP Session Peer Address Table (mplsLdpSesPeerAddrTable) |
| 761 |
stores addresses learned after session initialization via Address |
| 762 |
Message advertisement. |
| 763 |
|
| 764 |
- The LDP FEC Table (mplsFecTable) represents FEC (Forwarding |
| 765 |
Equivalence Class) information that may be in use on one or more |
| 766 |
LSPs. The LDP LSP FEC Table (mplsLdpLspFecTable) shows the FECs |
| 767 |
associated with each LSP. |
| 768 |
|
| 769 |
- MPLS-LDP-STD-MIB has a mapping table (mplsLdpLspTable) that maps |
| 770 |
the LDP MIB's representation of LDP sessions to the underlying LSR |
| 771 |
MIB's representation of the LSPs created by these sessions, by |
| 772 |
pointing to mplsInSegmentTable, mplsOutSegmentTable, and |
| 773 |
mplsXCTable, respectively. |
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Nadeau, et al. Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 783 |
|
| 784 |
|
| 785 |
- Statistics may be gathered through the LDP Entity Statistics Table |
| 786 |
(mplsLdpEntityStatsTable) and the LDP Session Statistics Table |
| 787 |
(mplsLdpSesStatsTable). |
| 788 |
|
| 789 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Scalars</span> |
| 790 |
|
| 791 |
Where tables in the MIB modules have arbitrary indexes, scalars are |
| 792 |
provided to supply the next available index. This applies to |
| 793 |
mplsLdpEntityTable and mplsFecTable. |
| 794 |
|
| 795 |
Two scalars exist to configure the LSR. The LSR ID is set in |
| 796 |
mplsLdpLsrId, and the loop detection capabilities are reported in |
| 797 |
mplsLdpLsrLoopDetectionCapable. |
| 798 |
|
| 799 |
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Notifications</span> |
| 800 |
|
| 801 |
MPLS-LDP-STD-MIB defines four notifications that a device can issue. |
| 802 |
|
| 803 |
- mplsLdpInitSesThresholdExceeded is reported when the number of |
| 804 |
Session Initialization messages exceeds a configured threshold. |
| 805 |
|
| 806 |
- mplsLdpPVLMismatch is issued if the Path Vector Limit for a |
| 807 |
configured Entity and Peer do not match. |
| 808 |
|
| 809 |
- mplsLdpSessionUp and mplsLdpSessionDown report the transition of |
| 810 |
Session state. |
| 811 |
|
| 812 |
No scalar object is provided to enable and disable notifications from |
| 813 |
MPLS-LDP-STD-MIB. Instead, the implementer is referred to [<a href="./rfc3413" title=""Simple Network Management Protocol (SNMP) Applications"">RFC3413</a>]. |
| 814 |
|
| 815 |
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Dependencies between MIB Module Tables</span> |
| 816 |
|
| 817 |
The many tables in the four LDP MIB modules are related as shown on |
| 818 |
the diagram below. The arrows indicate a reference from one table to |
| 819 |
another. Note that in many cases the reference is through an |
| 820 |
augmentation of the referenced table. |
| 821 |
|
| 822 |
|
| 823 |
|
| 824 |
|
| 825 |
|
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Nadeau, et al. Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 839 |
|
| 840 |
|
| 841 |
mplsLdpEntityGenLRTable ------------->+ |
| 842 |
mplsLdpEntityAtmParmsTable ---------->+ |
| 843 |
mplsLdpEntityAtmLRTable ------------->+ |
| 844 |
mplsLdpEntityFrameRelayParmsTable --->+ |
| 845 |
mplsLdpEntityFrLRTable -------------->+ |
| 846 |
mplsLdpEntityStatsTable ------------->+ |
| 847 |
| |
| 848 |
mplsLdpHelloAdjacencyTable | |
| 849 |
| | |
| 850 |
| mplsLdpEntityTable <--+ |
| 851 |
| ^ ^ |
| 852 |
V | | |
| 853 |
mplsLdpPeerTable <-+- mplsLdpSesPeerAddrTable |
| 854 |
^ | |
| 855 |
| V |
| 856 |
mplsLdpSessionTable |
| 857 |
^ ^ |
| 858 |
| | |
| 859 |
mplsLdpSesStatsTable ------+ +-- mplsLdpLspFecTable |
| 860 |
mplsLdpAtmSesTable --------+ | | | |
| 861 |
mplsLdpFrameRelaySesTable--+ | | V |
| 862 |
| | mplsFecTable |
| 863 |
| V |
| 864 |
+-- mplsLdpLspTable |
| 865 |
|
| 866 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Tables, Scalars, and Notifications in MPLS-TE-STD-MIB</span> |
| 867 |
|
| 868 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Tables</span> |
| 869 |
|
| 870 |
MPLS-TE-STD-MIB contains the following tables. |
| 871 |
|
| 872 |
- The Tunnel Table (mplsTunnelTable) is used to configure and report |
| 873 |
MPLS tunnels. Note that reporting of tunnels in this table at |
| 874 |
transit LSRs is optional. |
| 875 |
|
| 876 |
Entries in mplsTunnelTable are indexed by four objects. The |
| 877 |
source and destination LSR IDs give context to the entry, and an |
| 878 |
index (mplsTunnelIndex) identifies the tunnel itself. However, |
| 879 |
the fourth index (mplsTunnelInstance) may give rise to some |
| 880 |
confusion since its usage is not clearly explained. |
| 881 |
|
| 882 |
The description says: "Uniquely identifies an instance of a |
| 883 |
tunnel. It is useful to identify multiple instances of tunnels |
| 884 |
for the purposes of backup and parallel tunnels." In the case of |
| 885 |
backup tunnels, multiple instances of the same tunnel may be |
| 886 |
defined, but only one is active at any time. Different instances |
| 887 |
may have different properties (such as explicit routes), and one |
| 888 |
instance may be set up to protect against failure of another. |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Nadeau, et al. Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 895 |
|
| 896 |
|
| 897 |
Parallel tunnels may be used to provide load sharing or |
| 898 |
protection. |
| 899 |
|
| 900 |
The mplsTunnelInstancePriority object is used to indicate the |
| 901 |
precedence of tunnels with the same LSR IDs and mplsTunnelIndex |
| 902 |
value. The mplsTunnelPrimaryInstance object gives a quick |
| 903 |
reference back to the preferred instance of the tunnel. |
| 904 |
|
| 905 |
The mplsTunnelIndex value is typically signaled as the Tunnel ID, |
| 906 |
and the mplsTunnelInstance as the LSP ID, in protocols where both |
| 907 |
fields exist. In protocols where there is only one identifying |
| 908 |
index (usually known as the LSP ID), only the mplsTunnelIndex is |
| 909 |
signaled. |
| 910 |
|
| 911 |
- The Resource Table (mplsTunnelResourceTable) is used to configure |
| 912 |
resources to be requested on this tunnel. The CRLDP resource |
| 913 |
table (mplsTunnelCRLDPResTable) is used to request additional |
| 914 |
resource details that are specific to tunnels signaled using CR- |
| 915 |
LDP. |
| 916 |
|
| 917 |
- The routes requested, computed, and actually used for a tunnel are |
| 918 |
found in the Tunnel Hop Table (mplsTunnelHopTable), Tunnel |
| 919 |
Computed Hop Table (mplsTunnelCHopTable), and Tunnel Actual Hop |
| 920 |
Table (mplsTunnelARHopTable). |
| 921 |
|
| 922 |
- Statistics about the performance of tunnels may be gathered |
| 923 |
through the Tunnel Performance Table (mplsTunnelPerfTable). |
| 924 |
|
| 925 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Scalars</span> |
| 926 |
|
| 927 |
Where tables in the MIB module have arbitrary indexes, scalars are |
| 928 |
provided to supply the next available index. This applies to |
| 929 |
mplsTunnelTable, mplsTunnelResourceTable, and mplsTunnelHopTable. |
| 930 |
|
| 931 |
Two scalars exist to configure the support for MPLS tunnels on the |
| 932 |
LSR. mplsTunnelTEDistProto lists the signaling methods and protocols |
| 933 |
supported. mplsTunnelMaxHops defines the size of route that may be |
| 934 |
configured on the LSR. |
| 935 |
|
| 936 |
Two further scalars enhance the statistics on the LSR by counting the |
| 937 |
number of configured (mplsTunnelConfigured) and active |
| 938 |
(mplsTunnelActive) tunnels. |
| 939 |
|
| 940 |
The scalar mplsTunnelNotificationMaxRate is used to control the rate |
| 941 |
at which notifications are issued from MPLS-TE-STD-MIB. A rate of |
| 942 |
zero means that notifications must not be issued. If notifications |
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Nadeau, et al. Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 951 |
|
| 952 |
|
| 953 |
would be generated faster than the configured rate, an implementation |
| 954 |
may choose to discard notifications or to queue them for distribution |
| 955 |
at a quieter time. |
| 956 |
|
| 957 |
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Notifications</span> |
| 958 |
|
| 959 |
MPLS-TE-STD-MIB defines four notifications that a device can issue. |
| 960 |
The rate of dispatch of notifications is controlled as described in |
| 961 |
the previous section. |
| 962 |
|
| 963 |
- mplsTunnelUp and mplsTunnelDown report the transition of Tunnel |
| 964 |
state. |
| 965 |
|
| 966 |
- Rerouting and re-optimization of Tunnels paths are reported by |
| 967 |
mplsTunnelRerouted and mplsTunnelReoptimized. |
| 968 |
|
| 969 |
<span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. Dependencies between MIB Module Tables</span> |
| 970 |
|
| 971 |
The tables in MPLS-TE-STD-MIB are related as shown on the diagram |
| 972 |
below. The arrows indicate a reference from one table to another. |
| 973 |
|
| 974 |
mplsTunnelPerfTable |
| 975 |
^ |
| 976 |
| |
| 977 |
V |
| 978 |
mplsTunnelTable |
| 979 |
| | |
| 980 |
V | |
| 981 |
mplsTunnelResourceTable +--> mplsTunnelHopTable |
| 982 |
^ | |
| 983 |
| +--> mplsTunnelCHopTable |
| 984 |
V | |
| 985 |
mplsTunnelCRLDPResTable +--> mplsTunnelARHopTable |
| 986 |
|
| 987 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Tables, Scalars, and Notifications in MPLS-FTN-STD-MIB</span> |
| 988 |
|
| 989 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Tables</span> |
| 990 |
|
| 991 |
MPLS-FTN-STD-MIB contains the following tables. |
| 992 |
|
| 993 |
- The FEC-to-NHLFE Table (mplsFTNTable) defines the FEC to NHLFE |
| 994 |
rules to be applied to incoming packets, and the actions to be |
| 995 |
taken on matching packets. |
| 996 |
|
| 997 |
- The FEC-to-NHLFE Mapping Table (mplsFTNMapTable) provides the |
| 998 |
capability to activate FTN rules defined in the mplsFTNTable on |
| 999 |
specific interfaces in the system. |
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Nadeau, et al. Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
- Performance statistics for FTN rules are found in the |
| 1010 |
mplsFTNPerfTable. |
| 1011 |
|
| 1012 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Scalars</span> |
| 1013 |
|
| 1014 |
This MIB module contains the scalars mplsFTNTableLastChanged and |
| 1015 |
mplsFTNMapTableLastChanged to indicate the last time an object |
| 1016 |
changed in mplsFTNTable and mplsFTNMapTable, respectively. Another |
| 1017 |
scalar, mplsFTNIndexNext, is used to supply the next valid index for |
| 1018 |
creating new conceptual rows in mplsFTNTable. |
| 1019 |
|
| 1020 |
<span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Notifications</span> |
| 1021 |
|
| 1022 |
There are no notifications in this MIB module. |
| 1023 |
|
| 1024 |
<span class="h3"><a class="selflink" id="section-8.4" href="#section-8.4">8.4</a>. Dependencies between MIB Module Tables</span> |
| 1025 |
|
| 1026 |
The tables in MPLS-FTN-STD-MIB are related as shown on the diagram |
| 1027 |
below. The arrows indicate a reference from one table to another. |
| 1028 |
|
| 1029 |
mplsFTNTable |
| 1030 |
^ |
| 1031 |
| |
| 1032 |
mplsFTNMapTable |
| 1033 |
^ |
| 1034 |
| |
| 1035 |
mplsFTNPerfTable |
| 1036 |
|
| 1037 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Tables and Objects in TE-LINK-STD-MIB</span> |
| 1038 |
|
| 1039 |
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Tables</span> |
| 1040 |
|
| 1041 |
TE-LINK-STD-MIB contains the following tables. |
| 1042 |
|
| 1043 |
- The TE link table (teLinkTable) is used to specify TE links, |
| 1044 |
including bundled links, and their generic traffic-engineering |
| 1045 |
parameters. |
| 1046 |
|
| 1047 |
- The TE link descriptor table (teLinkDescriptorTable) is used to |
| 1048 |
list the TE link descriptors. |
| 1049 |
|
| 1050 |
- The shared risk link group (SRLG) table (teLinkSrlgTable) is used |
| 1051 |
to specify the SRLGs associated with TE links. |
| 1052 |
|
| 1053 |
- The TE link bandwidth table (teLinkBandwidthTable) is used to |
| 1054 |
report priority-based bandwidth values associated with TE links. |
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Nadeau, et al. Informational [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
- The component link table (componentLinkTable) is used to identify |
| 1066 |
the data-bearing component links that are associated with the TE |
| 1067 |
links and specify the data-bearing link generic traffic |
| 1068 |
engineering parameters. |
| 1069 |
|
| 1070 |
- The component link descriptor table (componentLinkDescriptorTable) |
| 1071 |
is used to list the data-bearing component link descriptors. |
| 1072 |
|
| 1073 |
- The component link bandwidth table (componentLinkBandwidthTable) |
| 1074 |
is used to report priority-based bandwidth values associated with |
| 1075 |
data-bearing component links. |
| 1076 |
|
| 1077 |
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Scalars</span> |
| 1078 |
|
| 1079 |
There are no scalars in this MIB module. |
| 1080 |
|
| 1081 |
<span class="h3"><a class="selflink" id="section-9.3" href="#section-9.3">9.3</a>. Notifications</span> |
| 1082 |
|
| 1083 |
There are no notifications in this MIB module. |
| 1084 |
|
| 1085 |
<span class="h3"><a class="selflink" id="section-9.4" href="#section-9.4">9.4</a>. Dependencies between MIB Module Tables</span> |
| 1086 |
|
| 1087 |
The tables in TE-LINK-STD-MIB are related as shown on the diagram |
| 1088 |
below. The arrows indicate a reference from one table to another. |
| 1089 |
|
| 1090 |
Note that many of the associations between tables are through a |
| 1091 |
common index that is the ifIndex of the related interface. |
| 1092 |
|
| 1093 |
teLinkTable |
| 1094 |
^ |
| 1095 |
| |
| 1096 |
teLinkDescriptorTable ---+ |
| 1097 |
| |
| 1098 |
teLinkSrlgTable ---------+ |
| 1099 |
| |
| 1100 |
teLinkBandwidthTable ----+ |
| 1101 |
|
| 1102 |
componentLinkTable |
| 1103 |
^ |
| 1104 |
| |
| 1105 |
componentLinkDescriptorTable ---+ |
| 1106 |
| |
| 1107 |
componentLinkBandwidthTable ----+ |
| 1108 |
|
| 1109 |
|
| 1110 |
|
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Nadeau, et al. Informational [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Table Dependencies between MPLS MIB Modules</span> |
| 1122 |
|
| 1123 |
<a href="#section-4.11">Section 4.11</a> gave an overview of how the MPLS MIB modules are |
| 1124 |
related. Now that the tables in the MIB modules have been |
| 1125 |
introduced, it is possible to give a more detailed diagram of these |
| 1126 |
relationships. |
| 1127 |
|
| 1128 |
MPLS-TC-STD-MIB is left off the diagram because many of the MIB |
| 1129 |
module tables use textual conventions from that MIB module. |
| 1130 |
|
| 1131 |
mplsLsrXCTable mplsLsrInSegmentTable |
| 1132 |
^ ^ |
| 1133 |
| | |
| 1134 |
+---- mplsLdpLspTable |
| 1135 |
| | |
| 1136 |
mplsTunnelTable ------+ V |
| 1137 |
^ | mplsLsrOutSegmentTable |
| 1138 |
| | |
| 1139 |
mplsFTNTable ---------+ |
| 1140 |
|
| 1141 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. A Note on Interfaces</span> |
| 1142 |
|
| 1143 |
The Interfaces Group of IF-MIB [<a href="./rfc2863" title=""The Interfaces Group MIB "">RFC2863</a>] defines generic managed |
| 1144 |
objects for managing interfaces. The MPLS MIB modules make |
| 1145 |
references to interfaces so that it can be clearly determined where |
| 1146 |
the procedures managed by the MIB modules should be performed. |
| 1147 |
Additionally, the MPLS MIB modules (notably MPLS-TE-STD-MIB and TE- |
| 1148 |
LINK-STD-MIB) utilize interface stacking within the Interface Group. |
| 1149 |
|
| 1150 |
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. MPLS Tunnels as Interfaces</span> |
| 1151 |
|
| 1152 |
MPLS-TE-STD-MIB builds on the concept of managing MPLS Tunnels as |
| 1153 |
logical interfaces. [<a href="./rfc2863" title=""The Interfaces Group MIB "">RFC2863</a>] states that the interfaces table |
| 1154 |
(ifTable) contains information on the managed resource's interfaces, |
| 1155 |
and that each sub-layer below the internetwork layer of a network |
| 1156 |
interface is considered an interface. Thus, an MPLS Tunnel managed |
| 1157 |
as an interface is represented as an entry in the ifTable. The |
| 1158 |
interrelation of entries in the ifTable is defined by the Interfaces |
| 1159 |
Stack Group defined in [<a href="./rfc2863" title=""The Interfaces Group MIB "">RFC2863</a>]. |
| 1160 |
|
| 1161 |
When using MPLS Tunnels as interfaces, the interface stack table |
| 1162 |
might appear as follows: |
| 1163 |
|
| 1164 |
|
| 1165 |
|
| 1166 |
|
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Nadeau, et al. Informational [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
+------------------------------------------------+ |
| 1178 |
| MPLS tunnel interface ifType = mplsTunnel(150) | |
| 1179 |
+------------------------------------------------+ |
| 1180 |
| MPLS interface ifType = mpls(166) | |
| 1181 |
+------------------------------------------------+ |
| 1182 |
| Underlying layer | |
| 1183 |
+------------------------------------------------+ |
| 1184 |
|
| 1185 |
In the diagram above, "Underlying layer" refers to the ifIndex of any |
| 1186 |
interface type for which MPLS internetworking has been defined. |
| 1187 |
Examples include ATM, Frame Relay, and Ethernet. |
| 1188 |
|
| 1189 |
A detailed listing of the mapping between ifTable objects and their |
| 1190 |
use for MPLS Tunnels is given in [<a href="#ref-TEMIB" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">TEMIB</a>]. A few key objects are |
| 1191 |
listed here to provide an overview of the concepts. |
| 1192 |
|
| 1193 |
Each MPLS tunnel is represented by an entry in the ifTable. Each |
| 1194 |
tunnel is therefore assigned a unique ifIndex. |
| 1195 |
|
| 1196 |
The type of an interface represented by an entry in the ifTable is |
| 1197 |
indicated by the ifType object. The value that is allocated to |
| 1198 |
identify an MPLS tunnel is 150. |
| 1199 |
|
| 1200 |
The ifOperStatus object reflects the actual operational status of the |
| 1201 |
MPLS tunnel and may be mapped from the mplsTunnelOperStatus object. |
| 1202 |
|
| 1203 |
It may be considered convenient and good management to set the ifName |
| 1204 |
object to reflect the name of the MPLS tunnel as contained in the |
| 1205 |
mplsTunnelName object. |
| 1206 |
|
| 1207 |
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Application of the Interfaces Group to TE Links</span> |
| 1208 |
|
| 1209 |
TE-LINK-STD-MIB also uses interface stacking to manage TE Link |
| 1210 |
interfaces as logical interfaces. The TE Link interface is |
| 1211 |
represented as an entry in the ifTable. The interrelation of entries |
| 1212 |
in the ifTable is defined by Interfaces Stack Group defined in |
| 1213 |
[<a href="./rfc2863" title=""The Interfaces Group MIB "">RFC2863</a>]. When using TE Link interfaces, the interface stack table |
| 1214 |
might appear as follows: |
| 1215 |
|
| 1216 |
|
| 1217 |
|
| 1218 |
|
| 1219 |
|
| 1220 |
|
| 1221 |
|
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Nadeau, et al. Informational [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
+-------------------------------------------------------------------+ |
| 1234 |
| MPLS interface ifType = mpls(166) | |
| 1235 |
| ifIndex = 1 | |
| 1236 |
+-------------------------------------------------------------------+ |
| 1237 |
| TE link (bundled link) ifType = teLink(200) | |
| 1238 |
| ifIndex = 2 | |
| 1239 |
+--------------------------------+-+--------------------------------+ |
| 1240 |
| TE link ifType = teLink(200) | | TE link ifType = teLink(200) | |
| 1241 |
| ifIndex = 3 | | ifIndex = 4 | |
| 1242 |
+--------------------------------+ +--------------------------------+ |
| 1243 |
| Component link | | Component link | |
| 1244 |
| ifType = opticalTransport(196) | | ifType = opticalTransport(196) | |
| 1245 |
| ifIndex = 5 | | ifIndex = 6 | |
| 1246 |
+--------------------------------+ +--------------------------------+ |
| 1247 |
|
| 1248 |
In the above diagram, "opticalTransport" is an example of an |
| 1249 |
underlying physical interface: in this case an optical transport |
| 1250 |
interface. TE link management and bundling can be seen in the levels |
| 1251 |
of interface stacking. Two TE links are defined, each managing an |
| 1252 |
optical transport link. These two TE links are combined into a |
| 1253 |
bundle, which is managed as a single TE link interface. This TE Link |
| 1254 |
interface supports MPLS and is presented as an MPLS interface. |
| 1255 |
|
| 1256 |
A detailed listing of the mapping between ifTable objects and their |
| 1257 |
use for TE Links is given in [<a href="#ref-TELMIB" title=""Traffic Engineering Link Management Information Base"">TELMIB</a>]. A few key objects are listed |
| 1258 |
here to provide an overview of the concepts. |
| 1259 |
|
| 1260 |
Each TE Link interface is represented by a separate entry in the |
| 1261 |
ifTable, with a unique ifIndex. |
| 1262 |
|
| 1263 |
The type of an interface represented by an entry in the ifTable is |
| 1264 |
indicated by the ifType object. The value that is allocated to |
| 1265 |
identify a TE Link is 200. |
| 1266 |
|
| 1267 |
<span class="h3"><a class="selflink" id="section-11.3" href="#section-11.3">11.3</a>. References to Interface MIB Objects from MPLS MIB Modules</span> |
| 1268 |
|
| 1269 |
MPLS-TE-STD-MIB contains two objects that reference the management of |
| 1270 |
an MPLS tunnel as an interface. mplsTunnelIsIf is a TruthValue that |
| 1271 |
indicates whether the tunnel is present in the ifTable. If the |
| 1272 |
tunnel is managed as an interface, the mplsTunnelIfIndex object |
| 1273 |
contains the ifIndex that identifies the corresponding entry in the |
| 1274 |
ifTable. |
| 1275 |
|
| 1276 |
MPLS-LSR-STD-MIB includes a table (mplsInterfaceTable) for |
| 1277 |
configuring the support for MPLS on specific interfaces. A |
| 1278 |
conceptual row in this table is created automatically by an LSR for |
| 1279 |
every interface that is capable of and configured for support of |
| 1280 |
MPLS. A conceptual row in this table will exist if and only if a |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Nadeau, et al. Informational [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
corresponding entry in ifTable exists with ifType = mpls(166). The |
| 1290 |
fate of the entries in the two tables are closely linked so that if |
| 1291 |
the entry in the ifTable is operationally disabled, the entry in |
| 1292 |
mplsInterfaceTable is deleted. During the life of an entry in |
| 1293 |
mplsInterfaceTable, a corresponding entry is managed in |
| 1294 |
mplsInterfacePerfTable to show performance counters for the MPLS- |
| 1295 |
capable interface. |
| 1296 |
|
| 1297 |
The ifIndex that identifies MPLS-capable interfaces also plays an |
| 1298 |
important indexing role in MPLS-LSR-STD-MIB. In-segments (that is, |
| 1299 |
incoming LSP labels) are represented in mplsInSegmentTable, which is |
| 1300 |
indexed by the mplsInSegmentIfIndex and mplsInSegmentLabel objects. |
| 1301 |
mplsInSegmentIfIndex is set to the ifIndex of the incoming MPLS- |
| 1302 |
capable interface. mplsInSegmentLabel identifies the incoming MPLS |
| 1303 |
label. Note that the corresponding mplsOutSegmentTable contains an |
| 1304 |
mplsOutSegmentIfIndex object to identify the outgoing MPLS-capable |
| 1305 |
interface, but that this does not form part of the index of the |
| 1306 |
table. |
| 1307 |
|
| 1308 |
MPLS-LDP-STD-MIB uses ifIndex extensively to identify the interface |
| 1309 |
over which MPLS is active. |
| 1310 |
|
| 1311 |
Within MPLS-FTN-STD-MIB, mplsFTNMapTable maps entries in mplsFTNTable |
| 1312 |
to interfaces on which mplsFTNTable entries should be activated. |
| 1313 |
Interfaces are identified using their ifIndex values. |
| 1314 |
|
| 1315 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Management Options</span> |
| 1316 |
|
| 1317 |
It is not the intention of this document to provide instructions or |
| 1318 |
advice to implementers of Management Stations, Management Agents, or |
| 1319 |
managed entities. It is, however, useful to make some observations |
| 1320 |
about how the MIB modules described above might be used to manage |
| 1321 |
MPLS systems. |
| 1322 |
|
| 1323 |
All MPLS LSPs may appear in MPLS-LSR-STD-MIB. At transit nodes, they |
| 1324 |
are seen as full cross-connects between incoming labels on incoming |
| 1325 |
interfaces and outgoing labels on outgoing interfaces. At ingress or |
| 1326 |
egress points, the cross-connections are unbalanced having spoof |
| 1327 |
upstream or downstream legs, respectively. |
| 1328 |
|
| 1329 |
Split and merge points of LSPs may be represented as more complex |
| 1330 |
cross-connects in MPLS-LSR-STD-MIB. Similarly, bidirectional LSPs |
| 1331 |
can be represented by using the same cross-connect index for each of |
| 1332 |
the forward and reverse cross-connections. |
| 1333 |
|
| 1334 |
The modules in the LDP MIB are intended solely for use with LDP and |
| 1335 |
CR-LDP. LSPs that are signaled through other means may conveniently |
| 1336 |
be stored in mplsLdpLspTable for consistency with LSPs set up using |
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Nadeau, et al. Informational [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
LDP, but there is little further value to this because the table |
| 1346 |
gives only pointers into MPLS-LSR-STD-MIB. If, however, the LSPs are |
| 1347 |
established with associated FECs using some signaling method other |
| 1348 |
than LDP (for example, BGP), it may be advantageous to use |
| 1349 |
mplsLdpLspTable, mplsFecTable, and mplsLdpLspFecTable to correlate |
| 1350 |
the LSPs. |
| 1351 |
|
| 1352 |
Note that if CR-LDP is the signaling protocol, there is no |
| 1353 |
requirement to use the LSP-related tables in the LDP MIB since the |
| 1354 |
LSP will be adequately represented in MPLS-TE-MIB and MPLS-LSR-STD- |
| 1355 |
MIB. |
| 1356 |
|
| 1357 |
MPLS tunnels may be represented in MPLS-TE-STD-MIB with their cross- |
| 1358 |
connects indicated in MPLS-LSR-STD-MIB. Tunnels are often (although |
| 1359 |
not always) set up with a series of constraints that may be |
| 1360 |
represented in MPLS-TE-STD-MIB. Note that a distinguishing feature |
| 1361 |
of a tunnel is that it has an ingress and an egress, where LSPs |
| 1362 |
established through LDP may be end-to-end or may be hop-by-hop. |
| 1363 |
|
| 1364 |
All LSPs (tunnels and non-tunnels) may be established as a result of |
| 1365 |
signaling protocols already defined or for future study. In |
| 1366 |
addition, LSPs may be set up manually by issuing configuration |
| 1367 |
commands to each of the LSRs on the LSP. These commands may utilize |
| 1368 |
SNMP by performing SET operations to the MIB module tables and |
| 1369 |
objects described here. Alternatively, configuration may be through |
| 1370 |
some non-standard interface such as a Command Line or a Graphical |
| 1371 |
User Interface. Such configured LSPs may also be represented in the |
| 1372 |
MIB module tables. |
| 1373 |
|
| 1374 |
Do not be misled by considerations of the "permanence" of LSPs when |
| 1375 |
deciding which tables of which MIB modules to use. An MPLS tunnel |
| 1376 |
may have a very long life expectancy if it is set up by an amnesiac |
| 1377 |
user. Otherwise, it may have a very short lifetime if it is |
| 1378 |
automatically provisioned to satisfy on-demand traffic requirements. |
| 1379 |
Similarly, an LSP established in response to a routing protocol |
| 1380 |
(sometimes known as a hop-by-hop LSP) may be equally stable or |
| 1381 |
unstable. |
| 1382 |
|
| 1383 |
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Related IETF MIB Modules</span> |
| 1384 |
|
| 1385 |
This section describes the broad interactions between MIB modules |
| 1386 |
produced by the PWE3, PPVPN, and CCAMP working groups and the MPLS |
| 1387 |
MIB modules. This information is provided as background and is not |
| 1388 |
central to this document. |
| 1389 |
|
| 1390 |
|
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Nadeau, et al. Informational [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
<span class="h3"><a class="selflink" id="section-13.1" href="#section-13.1">13.1</a>. PWE3 Working Group MIB Modules</span> |
| 1402 |
|
| 1403 |
The PWE3 working group has produced a document [<a href="#ref-PWE3FW" title=""Pseudo Wire Emulation Edge- to-Edge (PWE3) Architecture"">PWE3FW</a>] that includes |
| 1404 |
a description of the framework for MIB modules within PWE3 operation. |
| 1405 |
Since the PWE3 architecture includes the use of MPLS as an emulated |
| 1406 |
service and as a PSN service, the MPLS MIB modules described above |
| 1407 |
may be leveraged. The PWE3 framework document describes the |
| 1408 |
interactions between the MPLS MIB modules and the PWE3 MIB modules. |
| 1409 |
|
| 1410 |
<span class="h3"><a class="selflink" id="section-13.2" href="#section-13.2">13.2</a>. PPVPN Working Group MIB Modules</span> |
| 1411 |
|
| 1412 |
At present, the PPVPN working group has not included a discussion of |
| 1413 |
how the MPLS MIB modules interact with the MIB modules being produced |
| 1414 |
by that working group. The authors of this document hope to make a |
| 1415 |
forthcoming addition to the PPVPN framework document [<a href="#ref-PPVPNFW" title=""A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)"">PPVPNFW</a>] |
| 1416 |
detailing these interactions. At the moment, there are two MIB |
| 1417 |
modules, [<a href="#ref-VPNMIB" title=""MPLS/BGP Virtual Private Network Management Information Base Using SMIv2"">VPNMIB</a>] and [<a href="#ref-VPNTCMIB" title=""Definition of Textual Conventions for Provider Provisioned Virtual Private Network (PPVPN) Management"">VPNTCMIB</a>], which are discussed next. |
| 1418 |
|
| 1419 |
<span class="h4"><a class="selflink" id="section-13.2.1" href="#section-13.2.1">13.2.1</a>. PPVPN-MPLS-VPN-STD-MIB</span> |
| 1420 |
|
| 1421 |
PPVPN-MPLS-VPN-STD-MIB describes managed objects that are used to |
| 1422 |
model and manage RFC2547bis MPLS VPNs [<a href="#ref-RFC2547Bis" title=""MPLS/BGP VPNs"">RFC2547Bis</a>]. This MIB module |
| 1423 |
contains tables that model virtual routing forwarding entries (VRFs), |
| 1424 |
as well as the interfaces associated with those VRFs. |
| 1425 |
|
| 1426 |
<span class="h5"><a class="selflink" id="section-13.2.1.1" href="#section-13.2.1.1">13.2.1.1</a>. Position in the OID Tree</span> |
| 1427 |
|
| 1428 |
transmission -- <a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>] |
| 1429 |
| |
| 1430 |
+- vpnMIB -- PPVPN-MPLS-VPN-STD-MIB |
| 1431 |
|
| 1432 |
<span class="h5"><a class="selflink" id="section-13.2.1.2" href="#section-13.2.1.2">13.2.1.2</a>. Dependencies</span> |
| 1433 |
|
| 1434 |
This MIB module currently has no direct dependencies on any of the |
| 1435 |
MPLS MIB modules. This MIB module models MPLS VPN interfaces as |
| 1436 |
entries in the Interfaces MIB's Interfaces Table (ifTable). This MIB |
| 1437 |
module may be modified in the future to import textual conventions |
| 1438 |
from MPLS-TC-STD-MIB. |
| 1439 |
|
| 1440 |
A specific textual conventions MIB module [<a href="#ref-VPNTCMIB" title=""Definition of Textual Conventions for Provider Provisioned Virtual Private Network (PPVPN) Management"">VPNTCMIB</a>] defines textual |
| 1441 |
conventions that are imported into PPVPN-MPLS-VPN-STD-MIB. |
| 1442 |
|
| 1443 |
<span class="h3"><a class="selflink" id="section-13.3" href="#section-13.3">13.3</a>. CCAMP Working Group MIB Modules</span> |
| 1444 |
|
| 1445 |
The CCAMP working group is developing MIB modules in support of GMPLS |
| 1446 |
that interact directly with the MPLS MIB modules. Along with any MIB |
| 1447 |
modules produced by the CCAMP working group, a separate CCAMP- |
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Nadeau, et al. Informational [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
specific Management Framework document is expected to be issued |
| 1458 |
describing the relationship between these MIB modules and the |
| 1459 |
existing MPLS (and other) MIB modules. |
| 1460 |
|
| 1461 |
<span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. Traffic Engineering Working Group TE MIB</span> |
| 1462 |
|
| 1463 |
The TEWG has produced a traffic engineering MIB (TE-MIB) [<a href="#ref-TEWGMIB" title=""A Traffic Engineering (TE) MIB"">TEWGMIB</a>] |
| 1464 |
containing objects for monitoring traffic-engineered tunnels at their |
| 1465 |
ingress points. |
| 1466 |
|
| 1467 |
In many senses TE-MIB contains the same information as MPLS-TE-STD- |
| 1468 |
MIB. Both MIB modules can be used to monitor MPLS tunnels; however, |
| 1469 |
TE-MIB is minimalistic and caters best to TE tunnels as tunnels, at |
| 1470 |
the expense of not having many advanced features of MPLS-TE-STD-MIB, |
| 1471 |
whereas MPLS-TE-STD-MIB can deconstruct tunnels into hop-by-hop |
| 1472 |
cross-connects, at the expense of more complexity. |
| 1473 |
|
| 1474 |
The TE-MIB module imports textual conventions from the MPLS-TC-STD- |
| 1475 |
MIB module and therefore is dependent on that document. |
| 1476 |
|
| 1477 |
<span class="h3"><a class="selflink" id="section-14.1" href="#section-14.1">14.1</a>. Choosing between TE MIB Modules</span> |
| 1478 |
|
| 1479 |
TE-MIB is a flexible MIB module designed to manage traffic |
| 1480 |
engineering tunnels regardless of the implementation technology. |
| 1481 |
This flexibility and a focus on simplicity lead to some compromises. |
| 1482 |
|
| 1483 |
- Some MPLS configuration parameters are left out. For example, the |
| 1484 |
resource management in TE-MIB is confined to bandwidth, so missing |
| 1485 |
the full IntServ control. |
| 1486 |
|
| 1487 |
- Other TE-MIB parameters are present but with only limited options; |
| 1488 |
for example, the ability to configure different label distribution |
| 1489 |
methods per LSP. |
| 1490 |
|
| 1491 |
Extensibility of TE-MIB to related concepts (such as DiffServ and |
| 1492 |
Fast Reroute) and integrations with other MIB modules (such as that |
| 1493 |
in MPLS-LSR-STD-MIB) are not work items at the time of writing. The |
| 1494 |
MPLS MIB modules are more closely integrated as described in this |
| 1495 |
document. |
| 1496 |
|
| 1497 |
Write/create access to TE-MIB is only available at the ingress, where |
| 1498 |
it can be used to configure an ingress to signal a tunnel with |
| 1499 |
constraints. It cannot be used to configure hop-by-hop cross- |
| 1500 |
connects to build a tunnel. |
| 1501 |
|
| 1502 |
The purpose of TE-MIB module is to allow a Management Agent to |
| 1503 |
configure tunnels, and to inspect and monitor all tunnels (however |
| 1504 |
created) at their ingress points. It does not provide information |
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Nadeau, et al. Informational [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
about tunnels at any other point in the network (that is, at transit |
| 1514 |
or egress nodes). This module can be used, for example, to configure |
| 1515 |
the constraints of a tunnel, whereupon the ingress would compute the |
| 1516 |
tunnel path and signal it. The MIB module can then be used at the |
| 1517 |
ingress to monitor the tunnel's path(s), their status, and the |
| 1518 |
tunnel's uptime and counters. This MIB module is not designed to |
| 1519 |
configure hop-by-hop cross-connects to build a tunnel. |
| 1520 |
|
| 1521 |
<span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a>. Security Considerations</span> |
| 1522 |
|
| 1523 |
This document describes the interrelationships amongst the different |
| 1524 |
MIB modules relevant to MPLS management and as such does not have any |
| 1525 |
security implications in and of itself. |
| 1526 |
|
| 1527 |
Each specific MIB document specifies specific MIB objects, and such a |
| 1528 |
document must provide a proper security considerations section that |
| 1529 |
explains the security aspects of those objects. |
| 1530 |
|
| 1531 |
The attention of readers is particularly drawn to the security |
| 1532 |
implications of making MIB objects available for create or write |
| 1533 |
access through an access protocol such as SNMP. SNMPv1 by itself is |
| 1534 |
an insecure environment. Even if the network itself is made secure |
| 1535 |
(for example, by using IPSec), there is no control over who on the |
| 1536 |
secure network is allowed to access and GET (read) the objects in |
| 1537 |
this MIB. It is recommended that the implementers consider the |
| 1538 |
security features as provided by the SNMPv3 framework. Specifically, |
| 1539 |
the use 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>], |
| 1540 |
and the 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>], |
| 1541 |
is recommended. |
| 1542 |
|
| 1543 |
It is then a customer/user responsibility to ensure that the SNMP |
| 1544 |
entity giving access to an instance of this MIB is properly |
| 1545 |
configured to give access to only those objects, and to those |
| 1546 |
principals (users) that have legitimate rights to access them. |
| 1547 |
|
| 1548 |
<span class="h2"><a class="selflink" id="section-16" href="#section-16">16</a>. Acknowledgements</span> |
| 1549 |
|
| 1550 |
Many small pieces of text in this document have been borrowed from |
| 1551 |
the documents that define the MIB modules described here. The |
| 1552 |
authors would like to express appreciation to all who worked on those |
| 1553 |
MIB documents. |
| 1554 |
|
| 1555 |
Thanks also to all those who attended the November 2002 MPLS MIB open |
| 1556 |
meeting and gave constructive feedback, and in particular to Sharon |
| 1557 |
Chisholm for her thoughts on Management Options. |
| 1558 |
|
| 1559 |
Thanks to Kireeti Kompella for revising the text on TE-MIB. |
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Nadeau, et al. Informational [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
Without the consistent pressure and encouragement from Bert Wijnen, |
| 1570 |
this document would not have been written. |
| 1571 |
|
| 1572 |
<span class="h2"><a class="selflink" id="section-17" href="#section-17">17</a>. Normative References</span> |
| 1573 |
|
| 1574 |
[<a id="ref-FTNMIB">FTNMIB</a>] Nadeau, T., Srinivasan, C., and A. Viswanathan, |
| 1575 |
"Multiprotocol Label Switching (MPLS) Forwarding |
| 1576 |
Equivalence Class To Next Hop Label Forwarding Entry |
| 1577 |
(FEC-To-NHLFE) Management Information Base (MIB)", <a href="./rfc3814">RFC</a> |
| 1578 |
<a href="./rfc3814">3814</a>, June 2004. |
| 1579 |
|
| 1580 |
[<a id="ref-LDPMIB">LDPMIB</a>] Cucchiara, J., Sjostrand, H., and J. Luciani, |
| 1581 |
"Definitions of Managed Objects for the Multiprotocol |
| 1582 |
Label Switching (MPLS), Label Distribution Protocol |
| 1583 |
(LDP)", <a href="./rfc3815">RFC 3815</a>, June 2004. |
| 1584 |
|
| 1585 |
[<a id="ref-LSRMIB">LSRMIB</a>] Srinivasan, C., Viswanathan, A., and T. Nadeau, |
| 1586 |
"Multiprotocol Label Switching (MPLS) Label Switching |
| 1587 |
Router (LSR) Management Information Base (MIB)", <a href="./rfc3813">RFC</a> |
| 1588 |
<a href="./rfc3813">3813</a>, June 2004. |
| 1589 |
|
| 1590 |
[<a id="ref-RFC2863">RFC2863</a>] McCloghrie, K. and F. Kastenholtz, "The Interfaces |
| 1591 |
Group MIB ", <a href="./rfc2863">RFC 2863</a>, June 2000. |
| 1592 |
|
| 1593 |
[<a id="ref-RFC3289">RFC3289</a>] Baker, F., Chan, K., and A. Smith, "Management |
| 1594 |
Information Base for the Differentiated Services |
| 1595 |
Architecture", <a href="./rfc3289">RFC 3289</a>, May 2002. |
| 1596 |
|
| 1597 |
[<a id="ref-TCMIB">TCMIB</a>] Nadeau, T. and J. Cucchiara, "Definitions of Textual |
| 1598 |
Conventions (TCs) for Multiprotocol Label Switching |
| 1599 |
(MPLS) Management", <a href="./rfc3811">RFC 3811</a>, June 2004. |
| 1600 |
|
| 1601 |
[<a id="ref-TELMIB">TELMIB</a>] Dubuc, M., Dharanikota, S., Nadeau, T., J. Lang, |
| 1602 |
"Traffic Engineering Link Management Information Base", |
| 1603 |
<a href="./rfc4220">RFC 4220</a>, November 2005. |
| 1604 |
|
| 1605 |
[<a id="ref-TEMIB">TEMIB</a>] Srinivasan, C., Viswanathan, A., and T. Nadeau, |
| 1606 |
"Multiprotocol Label Switching (MPLS) Traffic |
| 1607 |
Engineering (TE) Management Information Base (MIB)", |
| 1608 |
<a href="./rfc3812">RFC 3812</a>, June 2004. |
| 1609 |
|
| 1610 |
|
| 1611 |
|
| 1612 |
|
| 1613 |
|
| 1614 |
|
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Nadeau, et al. Informational [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
<span class="h2"><a class="selflink" id="section-18" href="#section-18">18</a>. Informative References</span> |
| 1626 |
|
| 1627 |
[<a id="ref-PPVPNFW">PPVPNFW</a>] Callon, R. and M. Suzuki, "A Framework for Layer 3 |
| 1628 |
Provider-Provisioned Virtual Private Networks |
| 1629 |
(PPVPNs)", <a href="./rfc4110">RFC 4110</a>, July 2005. |
| 1630 |
|
| 1631 |
[<a id="ref-PWE3FW">PWE3FW</a>] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge- |
| 1632 |
to-Edge (PWE3) Architecture", <a href="./rfc3985">RFC 3985</a>, March 2005. |
| 1633 |
|
| 1634 |
[<a id="ref-RFC2026">RFC2026</a>] Bradner, S., "The Internet Standards Process -- |
| 1635 |
Revision 3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996. |
| 1636 |
|
| 1637 |
[<a id="ref-RFC2547Bis">RFC2547Bis</a>] Rosen, E., et al., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22MPLS%2FBGP+VPNs%22'>"MPLS/BGP VPNs"</a>, Work in Progress, |
| 1638 |
October 2002. |
| 1639 |
|
| 1640 |
[<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder, |
| 1641 |
"Structure of Management Information Version 2 |
| 1642 |
(SMIv2)", STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999. |
| 1643 |
|
| 1644 |
[<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder, |
| 1645 |
"Textual Conventions for SMIv2", STD 58, <a href="./rfc2579">RFC 2579</a>, |
| 1646 |
April 1999. |
| 1647 |
|
| 1648 |
[<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder, |
| 1649 |
"Conformance Statements for SMIv2", STD 58, <a href="./rfc2580">RFC 2580</a>, |
| 1650 |
April 1999. |
| 1651 |
|
| 1652 |
[<a id="ref-RFC3031">RFC3031</a>] Rosen, E., Viswanathan, A., and R. Callon, |
| 1653 |
"Multiprotocol Label Switching Architecture", <a href="./rfc3031">RFC 3031</a>, |
| 1654 |
January 2001. |
| 1655 |
|
| 1656 |
[<a id="ref-RFC3036">RFC3036</a>] Andersson, L., Doolan, P., Feldman, N., Fredette, A., |
| 1657 |
and B. Thomas, "LDP Specification", <a href="./rfc3036">RFC 3036</a>, January |
| 1658 |
2001. |
| 1659 |
|
| 1660 |
[<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D. and B. Stewart, |
| 1661 |
"Introduction and Applicability Statements for |
| 1662 |
Internet-Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, |
| 1663 |
December 2002. |
| 1664 |
|
| 1665 |
[<a id="ref-RFC3413">RFC3413</a>] Levi, D., Meyer, P., and B. Stewart, "Simple Network |
| 1666 |
Management Protocol (SNMP) Applications", STD 62, <a href="./rfc3413">RFC</a> |
| 1667 |
<a href="./rfc3413">3413</a>, December 2002. |
| 1668 |
|
| 1669 |
[<a id="ref-RFC3414">RFC3414</a>] Blumenthal, U. and B. Wijnen, "User-based Security |
| 1670 |
Model (USM) for version 3 of the Simple Network |
| 1671 |
Management Protocol (SNMPv3)", STD 62, <a href="./rfc3414">RFC 3414</a>, |
| 1672 |
December 2002. |
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Nadeau, et al. Informational [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
[<a id="ref-RFC3415">RFC3415</a>] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based |
| 1682 |
Access Control Model (VACM) for the Simple Network |
| 1683 |
Management Protocol (SNMP)", STD 62, <a href="./rfc3415">RFC 3415</a>, December |
| 1684 |
2002. |
| 1685 |
|
| 1686 |
[<a id="ref-TEWGMIB">TEWGMIB</a>] Kompella, K., "A Traffic Engineering (TE) MIB", <a href="./rfc3970">RFC</a> |
| 1687 |
<a href="./rfc3970">3970</a>, January 2005. |
| 1688 |
|
| 1689 |
[<a id="ref-VPNMIB">VPNMIB</a>] Nadeau, T., et al., "MPLS/BGP Virtual Private Network |
| 1690 |
Management Information Base Using SMIv2", Work in |
| 1691 |
Progress, November 2002. |
| 1692 |
|
| 1693 |
[<a id="ref-VPNTCMIB">VPNTCMIB</a>] Schliesser, B. and T. Nadeau, "Definition of Textual |
| 1694 |
Conventions for Provider Provisioned Virtual Private |
| 1695 |
Network (PPVPN) Management", Work in Progress, November |
| 1696 |
2002. |
| 1697 |
|
| 1698 |
Authors' Addresses |
| 1699 |
|
| 1700 |
Thomas D. Nadeau |
| 1701 |
Cisco Systems, Inc. |
| 1702 |
1414 Massachusetts Ave. |
| 1703 |
Boxborough, MA 01719 |
| 1704 |
|
| 1705 |
EMail: [email protected] |
| 1706 |
|
| 1707 |
|
| 1708 |
Cheenu Srinivasan |
| 1709 |
Bloomberg L.P. |
| 1710 |
731 Lexington Avenue |
| 1711 |
New York, NY 10022 |
| 1712 |
|
| 1713 |
Phone: (212) 617-3682 |
| 1714 |
EMail: [email protected] |
| 1715 |
|
| 1716 |
|
| 1717 |
Adrian Farrel |
| 1718 |
Old Dog Consulting |
| 1719 |
|
| 1720 |
Phone: +44 (0) 1978 860944 |
| 1721 |
EMail: [email protected] |
| 1722 |
|
| 1723 |
|
| 1724 |
|
| 1725 |
|
| 1726 |
|
| 1727 |
|
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Nadeau, et al. Informational [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc4221">RFC 4221</a> MPLS Management Overview November 2005</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
Full Copyright Statement |
| 1738 |
|
| 1739 |
Copyright (C) The Internet Society (2005). |
| 1740 |
|
| 1741 |
This document is subject to the rights, licenses and restrictions |
| 1742 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 1743 |
retain all their rights. |
| 1744 |
|
| 1745 |
This document and the information contained herein are provided on an |
| 1746 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 1747 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET |
| 1748 |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, |
| 1749 |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE |
| 1750 |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 1751 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 1752 |
|
| 1753 |
Intellectual Property |
| 1754 |
|
| 1755 |
The IETF takes no position regarding the validity or scope of any |
| 1756 |
Intellectual Property Rights or other rights that might be claimed to |
| 1757 |
pertain to the implementation or use of the technology described in |
| 1758 |
this document or the extent to which any license under such rights |
| 1759 |
might or might not be available; nor does it represent that it has |
| 1760 |
made any independent effort to identify any such rights. Information |
| 1761 |
on the procedures with respect to rights in RFC documents can be |
| 1762 |
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. |
| 1763 |
|
| 1764 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 1765 |
assurances of licenses to be made available, or the result of an |
| 1766 |
attempt made to obtain a general license or permission for the use of |
| 1767 |
such proprietary rights by implementers or users of this |
| 1768 |
specification can be obtained from the IETF on-line IPR repository at |
| 1769 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 1770 |
|
| 1771 |
The IETF invites any interested party to bring to its attention any |
| 1772 |
copyrights, patents or patent applications, or other proprietary |
| 1773 |
rights that may cover technology that may be required to implement |
| 1774 |
this standard. Please address the information to the IETF at ietf- |
| 1775 |
[email protected]. |
| 1776 |
|
| 1777 |
Acknowledgement |
| 1778 |
|
| 1779 |
Funding for the RFC Editor function is currently provided by the |
| 1780 |
Internet Society. |
| 1781 |
|
| 1782 |
|
| 1783 |
|
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
Nadeau, et al. Informational [Page 32] |
| 1789 |
</pre> |