| 1 |
<pre>Network Working Group M. Dubuc |
| 2 |
Request for Comments: 4220 Consultant |
| 3 |
Category: Standards Track T. Nadeau |
| 4 |
Cisco Systems |
| 5 |
J. Lang |
| 6 |
Sonos, Inc. |
| 7 |
November 2005 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">Traffic Engineering Link Management Information Base</span> |
| 11 |
|
| 12 |
Status of This Memo |
| 13 |
|
| 14 |
This document specifies an Internet standards track protocol for the |
| 15 |
Internet community, and requests discussion and suggestions for |
| 16 |
improvements. Please refer to the current edition of the "Internet |
| 17 |
Official Protocol Standards" (STD 1) for the standardization state |
| 18 |
and status of this protocol. Distribution of this memo is unlimited. |
| 19 |
|
| 20 |
Copyright Notice |
| 21 |
|
| 22 |
Copyright (C) The Internet Society (2005). |
| 23 |
|
| 24 |
Abstract |
| 25 |
|
| 26 |
This memo defines a portion of the Management Information Base (MIB) |
| 27 |
for use with network management protocols in the Internet community. |
| 28 |
In particular, it describes managed objects for modeling TE links as |
| 29 |
described in the Link Bundling in MPLS Traffic Engineering (TE) |
| 30 |
document. |
| 31 |
|
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Dubuc, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. The Internet-Standard Management Framework ......................<a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a>. Introduction ....................................................<a href="#page-3">3</a> |
| 61 |
<a href="#section-3">3</a>. Terminology .....................................................<a href="#page-3">3</a> |
| 62 |
<a href="#section-4">4</a>. Feature Checklist ...............................................<a href="#page-4">4</a> |
| 63 |
<a href="#section-5">5</a>. Outline .........................................................<a href="#page-4">4</a> |
| 64 |
<a href="#section-6">6</a>. Brief Description of MIB Objects ................................<a href="#page-4">4</a> |
| 65 |
<a href="#section-6.1">6.1</a>. teLinkTable ................................................<a href="#page-4">4</a> |
| 66 |
<a href="#section-6.2">6.2</a>. teLinkDescriptorTable ......................................<a href="#page-4">4</a> |
| 67 |
<a href="#section-6.3">6.3</a>. teLinkSrlgTable ............................................<a href="#page-5">5</a> |
| 68 |
<a href="#section-6.4">6.4</a>. teLinkBandwidthTable .......................................<a href="#page-5">5</a> |
| 69 |
<a href="#section-6.5">6.5</a>. componentLinkTable .........................................<a href="#page-5">5</a> |
| 70 |
<a href="#section-6.6">6.6</a>. componentLinkDescriptorTable ...............................<a href="#page-5">5</a> |
| 71 |
<a href="#section-6.7">6.7</a>. componentLinkBandwidthTable ................................<a href="#page-5">5</a> |
| 72 |
<a href="#section-7">7</a>. Example of Bundled Link Setup ...................................<a href="#page-5">5</a> |
| 73 |
<a href="#section-8">8</a>. Application of the Interfaces Group to TE Links .................<a href="#page-9">9</a> |
| 74 |
<a href="#section-8.1">8.1</a>. Support of the TE Link Layer by ifTable ....................<a href="#page-9">9</a> |
| 75 |
<a href="#section-8.2">8.2</a>. Using ifStackTable ........................................<a href="#page-11">11</a> |
| 76 |
<a href="#section-8.3">8.3</a>. Applicability of ifRcvAddressTable ........................<a href="#page-13">13</a> |
| 77 |
<a href="#section-9">9</a>. TE Link MIB Module Definitions .................................<a href="#page-13">13</a> |
| 78 |
<a href="#section-10">10</a>. Security Considerations .......................................<a href="#page-50">50</a> |
| 79 |
<a href="#section-11">11</a>. Contributors ..................................................<a href="#page-51">51</a> |
| 80 |
<a href="#section-12">12</a>. Acknowledgements ..............................................<a href="#page-51">51</a> |
| 81 |
<a href="#section-13">13</a>. IANA Considerations ...........................................<a href="#page-51">51</a> |
| 82 |
<a href="#section-13.1">13.1</a>. IANA Considerations for the TE-LINK-STD-MIB .............<a href="#page-51">51</a> |
| 83 |
<a href="#section-14">14</a>. References ....................................................<a href="#page-51">51</a> |
| 84 |
<a href="#section-14.1">14.1</a>. Normative References ....................................<a href="#page-51">51</a> |
| 85 |
<a href="#section-14.2">14.2</a>. Informative References ..................................<a href="#page-52">52</a> |
| 86 |
|
| 87 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The Internet-Standard Management Framework</span> |
| 88 |
|
| 89 |
For a detailed overview of the documents that describe the current |
| 90 |
Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">section 7 of |
| 91 |
RFC 3410</a> [<a href="./rfc3410" title=""Introduction and Applicability Statements for Internet-Standard Management Framework"">RFC3410</a>]. |
| 92 |
|
| 93 |
Managed objects are accessed via a virtual information store, termed |
| 94 |
the Management Information Base or MIB. MIB objects are generally |
| 95 |
accessed through the Simple Network Management Protocol (SNMP). |
| 96 |
Objects in the MIB are defined using the mechanisms defined in the |
| 97 |
Structure of Management Information (SMI). This memo specifies a MIB |
| 98 |
module that is compliant to the SMIv2, which is described in STD 58, |
| 99 |
<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 2580</a> |
| 100 |
[<a href="./rfc2580" title=""Conformance Statements for SMIv2"">RFC2580</a>]. |
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Dubuc, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Introduction</span> |
| 114 |
|
| 115 |
OSPF [<a href="./rfc3630" title=""Traffic Engineering (TE) Extensions to OSPF Version 2"">RFC3630</a>], Generalized MPLS (GMPLS) [<a href="./rfc3471" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"">RFC3471</a>], and the Link |
| 116 |
Management Protocol (LMP) [<a href="./rfc4204" title=""Link Management Protocol (LMP)"">RFC4204</a>] use the concept of traffic |
| 117 |
engineering (TE) links to abstract link properties. The effect of |
| 118 |
this approach is a reduction in the amount of routing information |
| 119 |
exchanged in the network, which improves routing scalability. In |
| 120 |
addition, the use of TE links allows the implementation of new |
| 121 |
capabilities such as link protection. |
| 122 |
|
| 123 |
In this document, we present a MIB module that can be used to manage |
| 124 |
TE links and their extension, the bundled link. This MIB module |
| 125 |
enables both the configuration and the performance monitoring of TE |
| 126 |
links and the bundled link. |
| 127 |
|
| 128 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 129 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 130 |
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 131 |
|
| 132 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology</span> |
| 133 |
|
| 134 |
This document uses terminology from the documents describing link |
| 135 |
bundling [<a href="./rfc4201" title=""Link Bundling in MPLS Traffic Engineering (TE)"">RFC4201</a>] and GMPLS [<a href="./rfc3945" title=""Generalized Multi-Protocol Label Switching (GMPLS) Architecture"">RFC3945</a>]. |
| 136 |
|
| 137 |
The link bundling feature is designed to aggregate one or more |
| 138 |
similar entities between a node pair into a bundled link [<a href="./rfc4201" title=""Link Bundling in MPLS Traffic Engineering (TE)"">RFC4201</a>]. |
| 139 |
In <a href="./rfc4201">RFC 4201</a>, those entities are referred to as TE links. A TE link |
| 140 |
is a subinterface capable of carrying MPLS traffic engineered |
| 141 |
traffic. A TE Link may be comprised of only one underlying component |
| 142 |
link. In cases where more than one component links are to be |
| 143 |
combined, multiple component links should be created with differing |
| 144 |
priorities to indicate hot-standby or parallel utilization. |
| 145 |
|
| 146 |
A bundled link is another kind of Traffic Engineering (TE) link (see |
| 147 |
[<a href="./rfc4203" title=""OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)"">RFC4203</a>]). A link bundle is a subinterface that binds the traffic |
| 148 |
of a group of one or more TE links. There should be more than one TE |
| 149 |
Link in a link bundle, but this is not a requirement. Furthermore, |
| 150 |
if there are more than one TE links in a link bundle at some time, |
| 151 |
and at some point later, all but one of the links are deleted, the |
| 152 |
agent may choose to either delete the link bundle, or it may choose |
| 153 |
to leave it intact. Traffic counters on a link bundle are cumulative |
| 154 |
for all subinterfaces that it binds together. |
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Dubuc, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Feature Checklist</span> |
| 170 |
|
| 171 |
The TE Link MIB module (TE-LINK-STD-MIB) is designed to satisfy the |
| 172 |
following requirements and constraints: |
| 173 |
|
| 174 |
- The MIB module supports the management of TE links, including |
| 175 |
bundled links. |
| 176 |
|
| 177 |
- Support is provided for configuration of traffic engineering |
| 178 |
parameters associated with TE links. |
| 179 |
|
| 180 |
- The MIB module is used to monitor the priority-based component |
| 181 |
link and TE link bandwidth values. |
| 182 |
|
| 183 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Outline</span> |
| 184 |
|
| 185 |
Configuring bundled links involves the following steps: |
| 186 |
|
| 187 |
- Creating a bundled link. |
| 188 |
|
| 189 |
- Creating TE links. |
| 190 |
|
| 191 |
- Optionally specifying the shared risk link groups associated with |
| 192 |
the TE links. |
| 193 |
|
| 194 |
- Configuring the component links including the bandwidth parameters |
| 195 |
and associating the component links with the appropriate TE link. |
| 196 |
|
| 197 |
- Associating the TE links with the appropriate bundled link. |
| 198 |
|
| 199 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Brief Description of MIB Objects</span> |
| 200 |
|
| 201 |
Sections <a href="#section-6.1">6.1</a> - <a href="#section-6.4">6.4</a> describe objects pertaining to TE links while |
| 202 |
Sections <a href="#section-6.5">6.5</a> - <a href="#section-6.7">6.7</a> describe objects pertaining to component links. |
| 203 |
The MIB objects were derived from the link bundling document |
| 204 |
[<a href="./rfc4201" title=""Link Bundling in MPLS Traffic Engineering (TE)"">RFC4201</a>]. |
| 205 |
|
| 206 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. teLinkTable</span> |
| 207 |
|
| 208 |
This table represents the TE links, including bundled links, and |
| 209 |
their generic traffic engineering parameters. |
| 210 |
|
| 211 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. teLinkDescriptorTable</span> |
| 212 |
|
| 213 |
This table represents the TE link interface switching capability |
| 214 |
descriptors. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Dubuc, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. teLinkSrlgTable</span> |
| 226 |
|
| 227 |
This table represents the shared risk link groups (SRLGs) associated |
| 228 |
with TE links. |
| 229 |
|
| 230 |
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. teLinkBandwidthTable</span> |
| 231 |
|
| 232 |
This table specifies the priority-based bandwidth traffic engineering |
| 233 |
parameters associated with TE links. |
| 234 |
|
| 235 |
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. componentLinkTable</span> |
| 236 |
|
| 237 |
This table enumerates the component links and their generic traffic |
| 238 |
engineering parameters. |
| 239 |
|
| 240 |
<span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. componentLinkDescriptorTable</span> |
| 241 |
|
| 242 |
This table enumerates the interface switching capability descriptors |
| 243 |
that each component link supports. |
| 244 |
|
| 245 |
<span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. componentLinkBandwidthTable</span> |
| 246 |
|
| 247 |
The component link bandwidth table specifies the priority-based |
| 248 |
bandwidth values associated with the component links. |
| 249 |
|
| 250 |
Component links that belong to the same TE link must be compatible. |
| 251 |
If these two tables are managed independently, mechanisms should be |
| 252 |
put in place to ensure consistency between the two tables. TE links |
| 253 |
that form a bundled link must have compatible traffic engineering |
| 254 |
parameters (resource class, link metric, and protection type). |
| 255 |
|
| 256 |
The link descriptors of the teLinkDescriptorTable can be derived from |
| 257 |
the link descriptors of the componentLinkDescrTable. |
| 258 |
|
| 259 |
Some of the bandwidth parameters of the teLinkTable, |
| 260 |
teLinkDescriptorTable, teLinkBandwidthTable are derived from the |
| 261 |
bandwidth parameters of the componentLinkTable, |
| 262 |
componentLinkDescriptorTable, and componentLinkBandwidthTable |
| 263 |
(maximum reservable bandwidth, minimum LSP bandwidth, maximum LSP |
| 264 |
bandwidth at specified priority, and unreserved bandwidth). |
| 265 |
|
| 266 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Example of Bundled Link Setup</span> |
| 267 |
|
| 268 |
In this section, we provide a brief example of using the MIB objects |
| 269 |
described in <a href="#section-10">section 10</a> to set up a bundled link. While this example |
| 270 |
is not meant to illustrate every nuance of the MIB module, it is |
| 271 |
intended as an aid to understanding some of the key concepts. It is |
| 272 |
meant to be read after going through the MIB module itself. Section |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Dubuc, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 279 |
|
| 280 |
|
| 281 |
8.2 provides more details on the use of the ifStackTable to establish |
| 282 |
relationships between bundled links, TE links, and component links. |
| 283 |
|
| 284 |
Suppose that one would like to manually create a bundled link out of |
| 285 |
two 1:1 TE links, as depicted in the figure in <a href="#section-8.2">Section 8.2</a>. Assume |
| 286 |
that the bundled link is associated with SRLGs 10 and 50. Finally, |
| 287 |
let the component links be port entity interfaces (lambdas). The |
| 288 |
following example illustrates which rows and corresponding objects |
| 289 |
might be created to accomplish this. |
| 290 |
|
| 291 |
First, a bundled link entry is created. An ifEntry with the same |
| 292 |
ifIndex and with ifType teLink needs to be created beforehand. |
| 293 |
|
| 294 |
In teLinkTable: |
| 295 |
{ |
| 296 |
ifIndex = 2, |
| 297 |
teLinkAddressType = unknown(0), |
| 298 |
teLinkLocalIpAddr = ''H, |
| 299 |
teLinkRemoteIpAddr = ''H, |
| 300 |
teLinkMetric = 5, |
| 301 |
teLinkProtectionType = dedicated1For1(4), |
| 302 |
teLinkWorkingPriority = 7, |
| 303 |
teLinkResourceClass = 3, |
| 304 |
teLinkIncomingIfId = 0, |
| 305 |
teLinkOutgoingIfId = 2, |
| 306 |
teLinkRowStatus = createAndGo(4), |
| 307 |
teLinkStorageType = nonVolatile(3) |
| 308 |
} |
| 309 |
|
| 310 |
In ifStackTable: |
| 311 |
{ |
| 312 |
ifStackHigherLayer = 0, |
| 313 |
ifStackLowerLayer = 2, |
| 314 |
ifStackStatus = createAndGo(4) |
| 315 |
} |
| 316 |
|
| 317 |
Next, the two TE links are created. |
| 318 |
|
| 319 |
In teLinkTable: |
| 320 |
{ |
| 321 |
ifIndex = 3, |
| 322 |
teLinkAddressType = unknown(0), |
| 323 |
teLinkLocalIpAddr = ''H, |
| 324 |
teLinkRemoteIpAddr = ''H, |
| 325 |
teLinkMetric = 5, |
| 326 |
teLinkProtectionType = unprotected(2), |
| 327 |
teLinkWorkingPriority = 7, |
| 328 |
teLinkResourceClass = 3, |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Dubuc, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 335 |
|
| 336 |
|
| 337 |
teLinkIncomingIfId = 0, |
| 338 |
teLinkOutgoingIfId = 3, |
| 339 |
teLinkRowStatus = createAndGo(4), |
| 340 |
teLinkStorageType = nonVolatile(3) |
| 341 |
} |
| 342 |
|
| 343 |
In ifStackTable: |
| 344 |
{ |
| 345 |
ifStackHigherLayer = 2, |
| 346 |
ifStackLowerLayer = 3, |
| 347 |
ifStackStatus = createAndGo(4) |
| 348 |
} |
| 349 |
|
| 350 |
In teLinkTable: |
| 351 |
{ |
| 352 |
ifIndex = 4, |
| 353 |
teLinkAddressType = unknown(0), |
| 354 |
teLinkLocalIpAddr = ''H, |
| 355 |
teLinkRemoteIpAddr = ''H, |
| 356 |
teLinkMetric = 5, |
| 357 |
teLinkProtectionType = unprotected(2), |
| 358 |
teLinkWorkingPriority = 7, |
| 359 |
teLinkResourceClass = 3, |
| 360 |
teLinkIncomingIfId = 0, |
| 361 |
teLinkOutgoingIfId = 4, |
| 362 |
teLinkRowStatus = createAndGo(4), |
| 363 |
teLinkStorageType = nonVolatile(3) |
| 364 |
} |
| 365 |
|
| 366 |
In ifStackTable: |
| 367 |
{ |
| 368 |
ifStackHigherLayer = 2, |
| 369 |
ifStackLowerLayer = 4, |
| 370 |
ifStackStatus = createAndGo(4) |
| 371 |
} |
| 372 |
|
| 373 |
We assign SRLGs to the TE links. |
| 374 |
|
| 375 |
In the teLinkSrlgTable: |
| 376 |
{ |
| 377 |
ifIndex = 3, |
| 378 |
teLinkSrlg = 10, |
| 379 |
teLinkSrlgRowStatus = createAndGo(4), |
| 380 |
teLinkSrlgStorageType = nonVolatile(3) |
| 381 |
} |
| 382 |
|
| 383 |
In the teLinkSrlgTable: |
| 384 |
{ |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Dubuc, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 391 |
|
| 392 |
|
| 393 |
ifIndex = 4, |
| 394 |
teLinkSrlg = 50, |
| 395 |
teLinkSrlgRowStatus = createAndGo(4), |
| 396 |
teLinkSrlgStorageType = nonVolatile(3) |
| 397 |
} |
| 398 |
|
| 399 |
The bundled link inherits the SRLG properties from the associated TE |
| 400 |
links. |
| 401 |
|
| 402 |
Next, for each unbundled TE link, a component link is created. An |
| 403 |
ifEntry with the same ifIndex needs to be created beforehand. |
| 404 |
|
| 405 |
In componentLinkTable: |
| 406 |
{ |
| 407 |
ifIndex = 5, |
| 408 |
componentLinkPreferredProtection = primary(1), |
| 409 |
componentLinkRowStatus = createAndGo(4), |
| 410 |
componentLinkStorageType = nonVolatile(3) |
| 411 |
} |
| 412 |
|
| 413 |
In ifStackTable: |
| 414 |
{ |
| 415 |
ifStackHigherLayer = 3, |
| 416 |
ifStackLowerLayer = 5, |
| 417 |
ifStackStatus = createAndGo(4) |
| 418 |
} |
| 419 |
|
| 420 |
In componentLinkTable: |
| 421 |
{ |
| 422 |
ifIndex = 6, |
| 423 |
componentLinkPreferredProtection = secondary(2), |
| 424 |
componentLinkRowStatus = createAndGo(4) |
| 425 |
componentLinkStorageType = nonVolatile(3) |
| 426 |
} |
| 427 |
|
| 428 |
In ifStackTable: |
| 429 |
{ |
| 430 |
ifStackHigherLayer = 4, |
| 431 |
ifStackLowerLayer = 6, |
| 432 |
ifStackStatus = createAndGo(4) |
| 433 |
} |
| 434 |
|
| 435 |
In this example, once a component link is added to the |
| 436 |
componentLinkTable, the associated link descriptors are implicitly |
| 437 |
added to the componentLinkDescriptorTable. |
| 438 |
|
| 439 |
TE link link descriptors are derived from their component link |
| 440 |
descriptors. |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Dubuc, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 447 |
|
| 448 |
|
| 449 |
Note that the bandwidth attributes in teLinkDescriptorTable, |
| 450 |
componentLinkDescriptorTable, teLinkBandwidthTable, and |
| 451 |
componentLinkBandwidthTable are maintained by the device according to |
| 452 |
LSP creation/deletion at different priorities. The values in the |
| 453 |
teLinkBandwidthTable are an aggregation of the values for the |
| 454 |
component links of the TE links and the TE links of the bundled link. |
| 455 |
|
| 456 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Application of the Interfaces Group to TE Links</span> |
| 457 |
|
| 458 |
The Interfaces Group [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>] defines generic managed objects for |
| 459 |
managing interfaces. This memo contains the media-specific |
| 460 |
extensions to the Interfaces Group for managing TE Link interfaces as |
| 461 |
logical interfaces. |
| 462 |
|
| 463 |
This memo assumes the interpretation of the Interfaces Group to be in |
| 464 |
accordance with [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>], which states that the interfaces table |
| 465 |
(ifTable) contains information on the managed resource's interfaces |
| 466 |
and that each sub-layer below the internetwork layer of a network |
| 467 |
interface is considered an interface. Thus, the TE Link interface is |
| 468 |
represented as an entry in the ifTable. The interrelation of entries |
| 469 |
in the ifTable is defined by Interfaces Stack Group, as defined in |
| 470 |
[<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. |
| 471 |
|
| 472 |
When using TE Link interfaces, the interface stack table might appear |
| 473 |
as follows: |
| 474 |
|
| 475 |
+----------------------------------------+ |
| 476 |
| TE link-interface ifType = teLink(200) + |
| 477 |
+----------------------------------------+ |
| 478 |
| Underlying Layer... + |
| 479 |
+----------------------------------------+ |
| 480 |
|
| 481 |
In the above diagram, "Underlying Layer..." refers to the ifIndex of |
| 482 |
any interface type, which has been defined for TE Link interworking. |
| 483 |
Examples include ATM, Frame Relay, Ethernet, etc. |
| 484 |
|
| 485 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Support of the TE Link Layer by ifTable</span> |
| 486 |
|
| 487 |
Some specific interpretations of ifTable for the TE Link layer |
| 488 |
follow. |
| 489 |
|
| 490 |
Object Use for the TE Link layer |
| 491 |
|
| 492 |
ifIndex Each TE Link interface is represented by an ifEntry. |
| 493 |
|
| 494 |
ifDescr Description of the TE Link interface. |
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Dubuc, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 503 |
|
| 504 |
|
| 505 |
ifType The value that is allocated for TE Link is 200 |
| 506 |
[<a href="#ref-IANAifType" title=""IANAifType MIB Module"">IANAifType</a>]. |
| 507 |
|
| 508 |
ifSpeed The total bandwidth in bits per second for use by the |
| 509 |
TE Link layer. |
| 510 |
|
| 511 |
ifPhysAddress Unused. |
| 512 |
|
| 513 |
ifAdminStatus This variable indicates the administrator's intent as |
| 514 |
to whether TE Link should be enabled, disabled, or |
| 515 |
running in some diagnostic testing mode on this |
| 516 |
interface. Also see [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. |
| 517 |
|
| 518 |
ifOperStatus This value reflects the actual or operational status of |
| 519 |
the TE Link on this interface. |
| 520 |
|
| 521 |
ifLastChange See [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. |
| 522 |
|
| 523 |
ifInOctets The number of received octets over the interface, i.e., |
| 524 |
the number of received octets in all component links |
| 525 |
associated with the interface. |
| 526 |
|
| 527 |
ifOutOctets The number of transmitted octets over the interface, |
| 528 |
i.e., the number of octets transmitted over all |
| 529 |
component links associated with the interface. |
| 530 |
|
| 531 |
ifInErrors The number of packets dropped due to uncorrectable |
| 532 |
errors. |
| 533 |
|
| 534 |
ifInUnknownProtos |
| 535 |
The number of received packets discarded during packet |
| 536 |
header validation. |
| 537 |
|
| 538 |
ifOutErrors See [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. |
| 539 |
|
| 540 |
ifName Textual name (unique on this system) of the interface, |
| 541 |
or an octet string of zero length. |
| 542 |
|
| 543 |
ifLinkUpDownTrapEnable |
| 544 |
Default is disabled (2). |
| 545 |
|
| 546 |
ifConnectorPresent |
| 547 |
Set to false (2). |
| 548 |
|
| 549 |
ifHighSpeed See [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. |
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Dubuc, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 559 |
|
| 560 |
|
| 561 |
ifHCInOctets The 64-bit version of ifInOctets; supported if required |
| 562 |
by the compliance statements in [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. |
| 563 |
|
| 564 |
ifHCOutOctets The 64-bit version of ifOutOctets; supported if |
| 565 |
required by the compliance statements in [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. |
| 566 |
|
| 567 |
ifAlias The non-volatile 'alias' name for the interface, as |
| 568 |
specified by a network manager. |
| 569 |
|
| 570 |
ifCounterDiscontinuityTime |
| 571 |
See [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>]. |
| 572 |
|
| 573 |
Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, |
| 574 |
ifOutErrors, ifHCInOctets, and ifHCOutOctets objects is not required |
| 575 |
if the encoding type is clear. For other encoding types, traffic |
| 576 |
counters on a TE link are cumulative for all subinterfaces that it |
| 577 |
binds together. |
| 578 |
|
| 579 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Using ifStackTable</span> |
| 580 |
|
| 581 |
This section describes, by example, how to use the ifStackTable to |
| 582 |
represent the relationship of TE links with underlying TE-enabled |
| 583 |
interfaces. Implementors of the stack table for TE link interfaces |
| 584 |
should look at the appropriate RFC for the service being stacked on |
| 585 |
TE links. The examples given below are for illustration purposes |
| 586 |
only. |
| 587 |
|
| 588 |
Example: MPLS is being carried on a bundled TE link. The bundled |
| 589 |
TE link represents a 1:1 optical transport interface. |
| 590 |
|
| 591 |
In this example, the component link is a TE link. The two component |
| 592 |
links/TE links are grouped in a bundled link. |
| 593 |
|
| 594 |
+-------------------------------------------------------------------+ |
| 595 |
| MPLS interface ifType = mpls(166) | |
| 596 |
| ifIndex = 1 | |
| 597 |
+-------------------------------------------------------------------+ |
| 598 |
| TE link (bundled link) ifType = teLink(200) | |
| 599 |
| ifIndex = 2 | |
| 600 |
+--------------------------------+-+--------------------------------+ |
| 601 |
| TE link ifType = teLink(200) | | TE link ifType = teLink(200) | |
| 602 |
| ifIndex = 3 | | ifIndex = 4 | |
| 603 |
+--------------------------------+ +--------------------------------+ |
| 604 |
| Component link | | Component link | |
| 605 |
| ifType = opticalTransport(196) | | ifType = opticalTransport(196) | |
| 606 |
| ifIndex = 5 | | ifIndex = 6 | |
| 607 |
+--------------------------------+ +--------------------------------+ |
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Dubuc, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 615 |
|
| 616 |
|
| 617 |
The assignment of the index values could, for example, be: |
| 618 |
|
| 619 |
ifIndex Description |
| 620 |
1 mpls (type 166) |
| 621 |
2 teLink (type 200) |
| 622 |
3 teLink (type 200) |
| 623 |
4 teLink (type 200) |
| 624 |
5 opticalTransport (type 196) |
| 625 |
6 opticalTransport (type 196) |
| 626 |
|
| 627 |
The ifStackTable is then used to show the relationships between the |
| 628 |
various interfaces. |
| 629 |
|
| 630 |
ifStackTable Entries |
| 631 |
|
| 632 |
HigherLayer LowerLayer |
| 633 |
0 1 |
| 634 |
1 2 |
| 635 |
2 3 |
| 636 |
2 4 |
| 637 |
3 5 |
| 638 |
4 6 |
| 639 |
5 0 |
| 640 |
6 0 |
| 641 |
|
| 642 |
In the case where MPLS is using a single TE link, then the upper TE |
| 643 |
link layer (link bundle) is not required. |
| 644 |
|
| 645 |
+-----------------------------------+ |
| 646 |
| MPLS interface ifType = mpls(166) | |
| 647 |
+-----------------------------------+ |
| 648 |
| TE link ifType = teLink(200) | |
| 649 |
+-----------------------------------+ |
| 650 |
| Component link | |
| 651 |
| ifType = opticalTransport(196) | |
| 652 |
+-----------------------------------+ |
| 653 |
|
| 654 |
The assignment of the index values could for example be: |
| 655 |
|
| 656 |
ifIndex Description |
| 657 |
1 mpls (type 166) |
| 658 |
2 teLink (type 200) |
| 659 |
3 opticalTransport (type 196) |
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Dubuc, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 671 |
|
| 672 |
|
| 673 |
The ifStackTable is then used to show the relationships between the |
| 674 |
various interfaces. |
| 675 |
|
| 676 |
ifStackTable Entries |
| 677 |
|
| 678 |
HigherLayer LowerLayer |
| 679 |
0 1 |
| 680 |
1 2 |
| 681 |
2 3 |
| 682 |
3 0 |
| 683 |
|
| 684 |
<span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Applicability of ifRcvAddressTable</span> |
| 685 |
|
| 686 |
TE link interfaces are logical interfaces with no media-level |
| 687 |
addresses. As such, the ifRcvAddressTable is not applicable to these |
| 688 |
interfaces. |
| 689 |
|
| 690 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. TE Link MIB Module Definitions</span> |
| 691 |
|
| 692 |
TE-LINK-STD-MIB DEFINITIONS ::= BEGIN |
| 693 |
|
| 694 |
IMPORTS |
| 695 |
MODULE-IDENTITY, OBJECT-TYPE, transmission, Integer32, Unsigned32 |
| 696 |
FROM SNMPv2-SMI |
| 697 |
|
| 698 |
MODULE-COMPLIANCE, OBJECT-GROUP |
| 699 |
FROM SNMPv2-CONF |
| 700 |
|
| 701 |
TEXTUAL-CONVENTION, RowStatus, StorageType |
| 702 |
FROM SNMPv2-TC |
| 703 |
|
| 704 |
InterfaceIndexOrZero, ifIndex |
| 705 |
FROM IF-MIB |
| 706 |
|
| 707 |
InetAddressType, InetAddress |
| 708 |
FROM INET-ADDRESS-MIB; |
| 709 |
|
| 710 |
|
| 711 |
teLinkStdMIB MODULE-IDENTITY |
| 712 |
LAST-UPDATED "200510110000Z" -- 11 October 2005 |
| 713 |
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" |
| 714 |
CONTACT-INFO |
| 715 |
" Martin Dubuc |
| 716 |
Email: [email protected] |
| 717 |
|
| 718 |
Thomas D. Nadeau |
| 719 |
Email: [email protected] |
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Dubuc, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 727 |
|
| 728 |
|
| 729 |
Jonathan P. Lang |
| 730 |
Email: [email protected] |
| 731 |
|
| 732 |
Comments about this document should be emailed directly to |
| 733 |
the MPLS working group mailing list at [email protected]." |
| 734 |
|
| 735 |
DESCRIPTION |
| 736 |
"Copyright (C) 2005 The Internet Society. This version of |
| 737 |
this MIB module is part of <a href="./rfc4220">RFC 4220</a>; see the RFC |
| 738 |
itself for full legal notices. |
| 739 |
|
| 740 |
This MIB module contains managed object definitions for |
| 741 |
MPLS traffic engineering links as defined in |
| 742 |
'Link Bundling in MPLS Traffic Engineering (TE)'." |
| 743 |
|
| 744 |
-- Revision history. |
| 745 |
REVISION |
| 746 |
"200510110000Z" -- 11 October 2005 |
| 747 |
DESCRIPTION |
| 748 |
"Initial version published as <a href="./rfc4220">RFC 4220</a>." |
| 749 |
::= { transmission 200 } |
| 750 |
|
| 751 |
-- Textual Conventions |
| 752 |
|
| 753 |
TeLinkBandwidth ::= TEXTUAL-CONVENTION |
| 754 |
STATUS current |
| 755 |
DESCRIPTION |
| 756 |
"This type is used to represent link bandwidth in bps. This |
| 757 |
value is represented using a 4 octet IEEE floating point |
| 758 |
format [<a href="#ref-IEEE" title=""IEEE Standard for Binary Floating-Point Arithmetic"">IEEE</a>]. The floating point representation is not |
| 759 |
used to represent fractional value but rather to allow |
| 760 |
specification of large numbers that cannot be expressed |
| 761 |
with 32-bit integers." |
| 762 |
REFERENCE |
| 763 |
"IEEE Standard for Binary Floating-Point Arithmetic, |
| 764 |
Standard 754-1985" |
| 765 |
SYNTAX OCTET STRING (SIZE(4)) |
| 766 |
|
| 767 |
TeLinkPriority ::= TEXTUAL-CONVENTION |
| 768 |
DISPLAY-HINT "d" |
| 769 |
STATUS current |
| 770 |
DESCRIPTION |
| 771 |
"This type is used to represent a priority. Each connection |
| 772 |
is assigned a priority. This priority is used when |
| 773 |
accounting for bandwidth on TE links or component |
| 774 |
links, for resource allocation and for rerouting purposes. |
| 775 |
Value 0 is the highest priority. Value 7 is the lowest |
| 776 |
priority." |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Dubuc, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 783 |
|
| 784 |
|
| 785 |
SYNTAX Unsigned32 (0..7) |
| 786 |
|
| 787 |
TeLinkProtection ::= TEXTUAL-CONVENTION |
| 788 |
STATUS current |
| 789 |
DESCRIPTION |
| 790 |
"Link protection." |
| 791 |
SYNTAX INTEGER { |
| 792 |
primary(1), |
| 793 |
secondary(2) |
| 794 |
} |
| 795 |
|
| 796 |
TeLinkSwitchingCapability ::= TEXTUAL-CONVENTION |
| 797 |
STATUS current |
| 798 |
DESCRIPTION |
| 799 |
"Switching capability as specified in the 'OSPF Extensions in |
| 800 |
Support of Generalized Multi-Protocol Label Switching |
| 801 |
(GMPLS)' document. The values specified in this document |
| 802 |
are not contiguous." |
| 803 |
SYNTAX INTEGER { |
| 804 |
packetSwitch1(1), |
| 805 |
packetSwitch2(2), |
| 806 |
packetSwitch3(3), |
| 807 |
packetSwitch4(4), |
| 808 |
layer2Switch(51), |
| 809 |
tdm(100), |
| 810 |
lambdaSwitch(150), |
| 811 |
fiberSwitch(200) |
| 812 |
} |
| 813 |
|
| 814 |
TeLinkEncodingType ::= TEXTUAL-CONVENTION |
| 815 |
STATUS current |
| 816 |
DESCRIPTION |
| 817 |
"Link encoding type as specified in 'Generalized |
| 818 |
Multi-Protocol Label Switching (GMPLS) Signaling |
| 819 |
Functional Description' document. The values |
| 820 |
specified in this document are not contiguous." |
| 821 |
SYNTAX INTEGER { |
| 822 |
packet(1), |
| 823 |
ethernet(2), |
| 824 |
ansiEtsiPdh(3), |
| 825 |
sdhItuSonetAnsi(5), |
| 826 |
digitalWrapper(7), |
| 827 |
lambda(8), |
| 828 |
fiber(9), |
| 829 |
fiberChannel(11) |
| 830 |
} |
| 831 |
|
| 832 |
TeLinkSonetSdhIndication ::= TEXTUAL-CONVENTION |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Dubuc, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 839 |
|
| 840 |
|
| 841 |
STATUS current |
| 842 |
DESCRIPTION |
| 843 |
"This convention is used to indicate whether the interface |
| 844 |
supports Standard or Arbitrary SONET/SDH. To simplify the |
| 845 |
mapping process, the values used in this textual convention |
| 846 |
match the values specified in the interface switching |
| 847 |
capability specific information field, i.e., 0 for Standard |
| 848 |
SONET/SDH and 1 for Arbitrary SONET/SDH." |
| 849 |
REFERENCE |
| 850 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 851 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 852 |
SYNTAX INTEGER { |
| 853 |
standard(0), |
| 854 |
arbitrary(1) |
| 855 |
} |
| 856 |
|
| 857 |
-- Top level components of this MIB module |
| 858 |
|
| 859 |
-- Notifications |
| 860 |
teLinkNotifications OBJECT IDENTIFIER ::= { teLinkStdMIB 0 } |
| 861 |
-- Tables, Scalars |
| 862 |
teLinkObjects OBJECT IDENTIFIER ::= { teLinkStdMIB 1 } |
| 863 |
-- Conformance |
| 864 |
teLinkConformance OBJECT IDENTIFIER ::= { teLinkStdMIB 2 } |
| 865 |
|
| 866 |
-- TE Link Table |
| 867 |
|
| 868 |
teLinkTable OBJECT-TYPE |
| 869 |
SYNTAX SEQUENCE OF TeLinkEntry |
| 870 |
MAX-ACCESS not-accessible |
| 871 |
STATUS current |
| 872 |
DESCRIPTION |
| 873 |
"This table specifies the grouping of component links into |
| 874 |
TE links and the grouping of TE links into bundled links." |
| 875 |
::= { teLinkObjects 1 } |
| 876 |
|
| 877 |
teLinkEntry OBJECT-TYPE |
| 878 |
SYNTAX TeLinkEntry |
| 879 |
MAX-ACCESS not-accessible |
| 880 |
STATUS current |
| 881 |
DESCRIPTION |
| 882 |
"An entry in this table exists for each ifEntry with an |
| 883 |
ifType of teLink(200), i.e., for every TE link. An ifEntry |
| 884 |
in the ifTable must exist before a teLinkEntry is created |
| 885 |
with the corresponding ifIndex. If a TE link entry in the |
| 886 |
ifTable is destroyed, then so is the corresponding entry |
| 887 |
in the teLinkTable. The administrative and operational |
| 888 |
status values are controlled from the ifEntry." |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Dubuc, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 895 |
|
| 896 |
|
| 897 |
INDEX { ifIndex } |
| 898 |
::= { teLinkTable 1 } |
| 899 |
|
| 900 |
TeLinkEntry ::= SEQUENCE { |
| 901 |
teLinkAddressType InetAddressType, |
| 902 |
teLinkLocalIpAddr InetAddress, |
| 903 |
teLinkRemoteIpAddr InetAddress, |
| 904 |
teLinkMetric Unsigned32, |
| 905 |
teLinkMaximumReservableBandwidth TeLinkBandwidth, |
| 906 |
teLinkProtectionType INTEGER, |
| 907 |
teLinkWorkingPriority TeLinkPriority, |
| 908 |
teLinkResourceClass Unsigned32, |
| 909 |
teLinkIncomingIfId Integer32, |
| 910 |
teLinkOutgoingIfId InterfaceIndexOrZero, |
| 911 |
teLinkRowStatus RowStatus, |
| 912 |
teLinkStorageType StorageType |
| 913 |
} |
| 914 |
|
| 915 |
teLinkAddressType OBJECT-TYPE |
| 916 |
SYNTAX InetAddressType |
| 917 |
MAX-ACCESS read-create |
| 918 |
STATUS current |
| 919 |
DESCRIPTION |
| 920 |
"The type of Internet address for the TE link." |
| 921 |
::= { teLinkEntry 1 } |
| 922 |
|
| 923 |
teLinkLocalIpAddr OBJECT-TYPE |
| 924 |
SYNTAX InetAddress |
| 925 |
MAX-ACCESS read-create |
| 926 |
STATUS current |
| 927 |
DESCRIPTION |
| 928 |
"The local Internet address for numbered links. The type of |
| 929 |
this address is determined by the value of the |
| 930 |
teLinkAddressType object. |
| 931 |
|
| 932 |
For IPv4 and IPv6 numbered links, this object represents the |
| 933 |
local IP address associated with the TE link. For an |
| 934 |
unnumbered link, the local address is of type unknown, this |
| 935 |
object is set to the zero length string, and the |
| 936 |
teLinkOutgoingIfId object then identifies the unnumbered |
| 937 |
address. |
| 938 |
|
| 939 |
If the TE link is a Forwarding Adjacency (FA), the local |
| 940 |
IP address is set to the head-end address of the FA-LSP. |
| 941 |
|
| 942 |
If ipAddrTable is implemented, this object must have the |
| 943 |
same value as the ipAdEntAddr object that belongs to the |
| 944 |
row in ipAddrTable where ipAdEntIfIndex is equal to |
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Dubuc, et al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 951 |
|
| 952 |
|
| 953 |
ifIndex." |
| 954 |
::= { teLinkEntry 2 } |
| 955 |
|
| 956 |
teLinkRemoteIpAddr OBJECT-TYPE |
| 957 |
SYNTAX InetAddress |
| 958 |
MAX-ACCESS read-create |
| 959 |
STATUS current |
| 960 |
DESCRIPTION |
| 961 |
"The remote Internet address for numbered links. The type of |
| 962 |
this address is determined by the value of the |
| 963 |
teLinkAddressType object. |
| 964 |
|
| 965 |
The remote IP address associated with the TE link (IPv4 and |
| 966 |
IPv6 numbered links). For an unnumbered link, the remote |
| 967 |
address is of type unknown, this object is set to the |
| 968 |
zero length string, and the teLinkIncomingIfId object then |
| 969 |
identifies the unnumbered address. |
| 970 |
|
| 971 |
If the TE link is a Forwarding Adjacency, the remote IP |
| 972 |
address is set to the tail-end address of the FA-LSP." |
| 973 |
::= { teLinkEntry 3 } |
| 974 |
|
| 975 |
teLinkMetric OBJECT-TYPE |
| 976 |
SYNTAX Unsigned32 |
| 977 |
MAX-ACCESS read-create |
| 978 |
STATUS current |
| 979 |
DESCRIPTION |
| 980 |
"The traffic engineering metric for the TE link is |
| 981 |
derived from its component links. All component links |
| 982 |
within the TE link must have the same traffic |
| 983 |
engineering metric." |
| 984 |
REFERENCE |
| 985 |
"Link Bundling in MPLS Traffic Engineering (TE), <a href="./rfc4201">RFC 4201</a>" |
| 986 |
::= { teLinkEntry 4 } |
| 987 |
|
| 988 |
teLinkMaximumReservableBandwidth OBJECT-TYPE |
| 989 |
SYNTAX TeLinkBandwidth |
| 990 |
UNITS "bps" |
| 991 |
MAX-ACCESS read-only |
| 992 |
STATUS current |
| 993 |
DESCRIPTION |
| 994 |
"This attribute specifies the maximum reservable bandwidth on |
| 995 |
the TE link. This is the union of the maximum reservable |
| 996 |
bandwidth of all the component links within the |
| 997 |
TE link that can be used to carry live traffic." |
| 998 |
REFERENCE |
| 999 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1000 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Dubuc, et al. Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
::= { teLinkEntry 5 } |
| 1010 |
|
| 1011 |
teLinkProtectionType OBJECT-TYPE |
| 1012 |
SYNTAX INTEGER { |
| 1013 |
extraTraffic(1), |
| 1014 |
unprotected(2), |
| 1015 |
shared(3), |
| 1016 |
dedicated1For1(4), |
| 1017 |
dedicated1Plus1(5), |
| 1018 |
enhanced(6) |
| 1019 |
} |
| 1020 |
MAX-ACCESS read-create |
| 1021 |
STATUS current |
| 1022 |
DESCRIPTION |
| 1023 |
"This attribute specifies the link protection type of the |
| 1024 |
TE link. Descriptions of the different protection types can |
| 1025 |
be found in the 'Routing Extensions in Support of |
| 1026 |
Generalized Multi-Protocol Label Switching (GMPLS)' |
| 1027 |
document." |
| 1028 |
REFERENCE |
| 1029 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1030 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a> and |
| 1031 |
Routing Extensions in Support of Generalized Multi-Protocol |
| 1032 |
Label Switching (GMPLS), <a href="./rfc4202">RFC 4202</a>" |
| 1033 |
::= { teLinkEntry 6 } |
| 1034 |
|
| 1035 |
teLinkWorkingPriority OBJECT-TYPE |
| 1036 |
SYNTAX TeLinkPriority |
| 1037 |
MAX-ACCESS read-create |
| 1038 |
STATUS current |
| 1039 |
DESCRIPTION |
| 1040 |
"This object represents a priority value such that a new |
| 1041 |
connection with a higher priority, i.e., numerically lower |
| 1042 |
than this value, is guaranteed to be setup on a primary |
| 1043 |
link and not on a secondary link." |
| 1044 |
REFERENCE |
| 1045 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1046 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1047 |
::= { teLinkEntry 7 } |
| 1048 |
|
| 1049 |
teLinkResourceClass OBJECT-TYPE |
| 1050 |
SYNTAX Unsigned32 |
| 1051 |
MAX-ACCESS read-create |
| 1052 |
STATUS current |
| 1053 |
DESCRIPTION |
| 1054 |
"This attribute specifies the TE link resource class. |
| 1055 |
The resource class is a 32 bit bitfield. The resource class |
| 1056 |
for a link bundle is derived from the resource class of its |
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Dubuc, et al. Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
TE links. All TE links within a link bundle must have the |
| 1066 |
same resource class. Encoding of the resource class is |
| 1067 |
described in the 'Traffic Engineering (TE) Extensions to |
| 1068 |
OSPF Version 2' document." |
| 1069 |
REFERENCE |
| 1070 |
"Link Bundling in MPLS Traffic Engineering (TE), <a href="./rfc4201">RFC 4201</a> |
| 1071 |
and Traffic Engineering (TE) Extensions to OSPF Version 2, |
| 1072 |
<a href="./rfc3630">RFC 3630</a>" |
| 1073 |
::= { teLinkEntry 8 } |
| 1074 |
|
| 1075 |
teLinkIncomingIfId OBJECT-TYPE |
| 1076 |
SYNTAX Integer32 (0..2147483647) |
| 1077 |
MAX-ACCESS read-create |
| 1078 |
STATUS current |
| 1079 |
DESCRIPTION |
| 1080 |
"For unnumbered links, the incoming interface is set to the |
| 1081 |
outgoing interface identifier chosen by the neighboring LSR |
| 1082 |
for the reverse link corresponding to this TE link. If the |
| 1083 |
link is numbered, the value of this object is 0 and the |
| 1084 |
address is stored in the teLinkRemoteIpAddr instead." |
| 1085 |
REFERENCE |
| 1086 |
"Link Bundling in MPLS Traffic Engineering (TE), <a href="./rfc4201">RFC 4201</a>" |
| 1087 |
::= { teLinkEntry 9 } |
| 1088 |
|
| 1089 |
teLinkOutgoingIfId OBJECT-TYPE |
| 1090 |
SYNTAX InterfaceIndexOrZero |
| 1091 |
MAX-ACCESS read-create |
| 1092 |
STATUS current |
| 1093 |
DESCRIPTION |
| 1094 |
"If the link is unnumbered, the outgoing interface identifier |
| 1095 |
is set to the outgoing interface identifier chosen for the |
| 1096 |
TE link by the advertising LSR. If the link is numbered, the |
| 1097 |
value of this object is 0 and the address is stored in the |
| 1098 |
teLinkLocalIpAddr instead." |
| 1099 |
REFERENCE |
| 1100 |
"Link Bundling in MPLS Traffic Engineering (TE), <a href="./rfc4201">RFC 4201</a>" |
| 1101 |
::= { teLinkEntry 10 } |
| 1102 |
|
| 1103 |
teLinkRowStatus OBJECT-TYPE |
| 1104 |
SYNTAX RowStatus |
| 1105 |
MAX-ACCESS read-create |
| 1106 |
STATUS current |
| 1107 |
DESCRIPTION |
| 1108 |
"This variable is used to create, modify, and/or |
| 1109 |
delete a row in this table. None of the writable objects in |
| 1110 |
a row can be changed if status is active(1)." |
| 1111 |
::= { teLinkEntry 11 } |
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Dubuc, et al. Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
teLinkStorageType OBJECT-TYPE |
| 1122 |
SYNTAX StorageType |
| 1123 |
MAX-ACCESS read-create |
| 1124 |
STATUS current |
| 1125 |
DESCRIPTION |
| 1126 |
"The storage type for this conceptual row in the |
| 1127 |
teLinkTable. Conceptual rows having the value |
| 1128 |
'permanent' need not allow write-access to any |
| 1129 |
columnar object in the row." |
| 1130 |
::= { teLinkEntry 12 } |
| 1131 |
|
| 1132 |
-- End of teLinkTable |
| 1133 |
|
| 1134 |
|
| 1135 |
-- TE Link Descriptor Table |
| 1136 |
|
| 1137 |
teLinkDescriptorTable OBJECT-TYPE |
| 1138 |
SYNTAX SEQUENCE OF TeLinkDescriptorEntry |
| 1139 |
MAX-ACCESS not-accessible |
| 1140 |
STATUS current |
| 1141 |
DESCRIPTION |
| 1142 |
"This table specifies the interface switching capability |
| 1143 |
descriptors associated with the TE links." |
| 1144 |
::= { teLinkObjects 2 } |
| 1145 |
|
| 1146 |
teLinkDescriptorEntry OBJECT-TYPE |
| 1147 |
SYNTAX TeLinkDescriptorEntry |
| 1148 |
MAX-ACCESS not-accessible |
| 1149 |
STATUS current |
| 1150 |
DESCRIPTION |
| 1151 |
"An entry in this table is created for every TE link interface |
| 1152 |
switching capability descriptor. An ifEntry in the ifTable |
| 1153 |
must exist before a teLinkDescriptorEntry using the same |
| 1154 |
ifIndex is created. ifType of ifEntry must be teLink(200). |
| 1155 |
If a TE link entry in the ifTable is destroyed, then so are |
| 1156 |
all of the entries in the teLinkDescriptorTable that use the |
| 1157 |
ifIndex of this TE link." |
| 1158 |
INDEX { ifIndex, teLinkDescriptorId } |
| 1159 |
::= { teLinkDescriptorTable 1 } |
| 1160 |
|
| 1161 |
TeLinkDescriptorEntry ::= SEQUENCE { |
| 1162 |
teLinkDescriptorId Unsigned32, |
| 1163 |
teLinkDescrSwitchingCapability TeLinkSwitchingCapability, |
| 1164 |
teLinkDescrEncodingType TeLinkEncodingType, |
| 1165 |
teLinkDescrMinLspBandwidth TeLinkBandwidth, |
| 1166 |
teLinkDescrMaxLspBandwidthPrio0 TeLinkBandwidth, |
| 1167 |
teLinkDescrMaxLspBandwidthPrio1 TeLinkBandwidth, |
| 1168 |
teLinkDescrMaxLspBandwidthPrio2 TeLinkBandwidth, |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Dubuc, et al. Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
teLinkDescrMaxLspBandwidthPrio3 TeLinkBandwidth, |
| 1178 |
teLinkDescrMaxLspBandwidthPrio4 TeLinkBandwidth, |
| 1179 |
teLinkDescrMaxLspBandwidthPrio5 TeLinkBandwidth, |
| 1180 |
teLinkDescrMaxLspBandwidthPrio6 TeLinkBandwidth, |
| 1181 |
teLinkDescrMaxLspBandwidthPrio7 TeLinkBandwidth, |
| 1182 |
teLinkDescrInterfaceMtu Unsigned32, |
| 1183 |
teLinkDescrIndication TeLinkSonetSdhIndication, |
| 1184 |
teLinkDescrRowStatus RowStatus, |
| 1185 |
teLinkDescrStorageType StorageType |
| 1186 |
} |
| 1187 |
|
| 1188 |
teLinkDescriptorId OBJECT-TYPE |
| 1189 |
SYNTAX Unsigned32 (1..4294967295) |
| 1190 |
MAX-ACCESS not-accessible |
| 1191 |
STATUS current |
| 1192 |
DESCRIPTION |
| 1193 |
"This object specifies the link descriptor identifier." |
| 1194 |
::= { teLinkDescriptorEntry 1 } |
| 1195 |
|
| 1196 |
teLinkDescrSwitchingCapability OBJECT-TYPE |
| 1197 |
SYNTAX TeLinkSwitchingCapability |
| 1198 |
MAX-ACCESS read-create |
| 1199 |
STATUS current |
| 1200 |
DESCRIPTION |
| 1201 |
"This attribute specifies interface switching capability of |
| 1202 |
the TE link, which is derived from its component links." |
| 1203 |
REFERENCE |
| 1204 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1205 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1206 |
::= { teLinkDescriptorEntry 2 } |
| 1207 |
|
| 1208 |
teLinkDescrEncodingType OBJECT-TYPE |
| 1209 |
SYNTAX TeLinkEncodingType |
| 1210 |
MAX-ACCESS read-create |
| 1211 |
STATUS current |
| 1212 |
DESCRIPTION |
| 1213 |
"This attribute specifies the TE link encoding type." |
| 1214 |
REFERENCE |
| 1215 |
"Generalized Multi-Protocol Label Switching (GMPLS) |
| 1216 |
Signaling Functional Description, <a href="./rfc3471">RFC 3471</a>" |
| 1217 |
::= { teLinkDescriptorEntry 3 } |
| 1218 |
|
| 1219 |
teLinkDescrMinLspBandwidth OBJECT-TYPE |
| 1220 |
SYNTAX TeLinkBandwidth |
| 1221 |
UNITS "bps" |
| 1222 |
MAX-ACCESS read-create |
| 1223 |
STATUS current |
| 1224 |
DESCRIPTION |
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Dubuc, et al. Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
"This attribute specifies the minimum LSP bandwidth on |
| 1234 |
the TE link. This is derived from the union of the |
| 1235 |
minimum LSP bandwidth of all the component links |
| 1236 |
associated with the TE link that can be used to carry |
| 1237 |
live traffic." |
| 1238 |
REFERENCE |
| 1239 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1240 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1241 |
::= { teLinkDescriptorEntry 4 } |
| 1242 |
|
| 1243 |
teLinkDescrMaxLspBandwidthPrio0 OBJECT-TYPE |
| 1244 |
SYNTAX TeLinkBandwidth |
| 1245 |
UNITS "bps" |
| 1246 |
MAX-ACCESS read-create |
| 1247 |
STATUS current |
| 1248 |
DESCRIPTION |
| 1249 |
"This attribute specifies the maximum LSP bandwidth at |
| 1250 |
priority 0 on the TE link. This is the union of the maximum |
| 1251 |
LSP bandwidth at priority 0 of all the component links within |
| 1252 |
the TE link that can be used to carry live traffic." |
| 1253 |
REFERENCE |
| 1254 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1255 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1256 |
::= { teLinkDescriptorEntry 5 } |
| 1257 |
|
| 1258 |
teLinkDescrMaxLspBandwidthPrio1 OBJECT-TYPE |
| 1259 |
SYNTAX TeLinkBandwidth |
| 1260 |
UNITS "bps" |
| 1261 |
MAX-ACCESS read-create |
| 1262 |
STATUS current |
| 1263 |
DESCRIPTION |
| 1264 |
"This attribute specifies the maximum LSP bandwidth at |
| 1265 |
priority 1 on the TE link. This is the union of the maximum |
| 1266 |
LSP bandwidth at priority 1 of all the component links within |
| 1267 |
the TE link that can be used to carry live traffic." |
| 1268 |
REFERENCE |
| 1269 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1270 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1271 |
::= { teLinkDescriptorEntry 6 } |
| 1272 |
|
| 1273 |
teLinkDescrMaxLspBandwidthPrio2 OBJECT-TYPE |
| 1274 |
SYNTAX TeLinkBandwidth |
| 1275 |
UNITS "bps" |
| 1276 |
MAX-ACCESS read-create |
| 1277 |
STATUS current |
| 1278 |
DESCRIPTION |
| 1279 |
"This attribute specifies the maximum LSP bandwidth at |
| 1280 |
priority 2 on the TE link. This is the union of the maximum |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Dubuc, et al. Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
LSP bandwidth at priority 2 of all the component links within |
| 1290 |
the TE link that can be used to carry live traffic." |
| 1291 |
REFERENCE |
| 1292 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1293 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1294 |
::= { teLinkDescriptorEntry 7 } |
| 1295 |
|
| 1296 |
teLinkDescrMaxLspBandwidthPrio3 OBJECT-TYPE |
| 1297 |
SYNTAX TeLinkBandwidth |
| 1298 |
UNITS "bps" |
| 1299 |
MAX-ACCESS read-create |
| 1300 |
STATUS current |
| 1301 |
DESCRIPTION |
| 1302 |
"This attribute specifies the maximum LSP bandwidth at |
| 1303 |
priority 3 on the TE link. This is the union of the maximum |
| 1304 |
LSP bandwidth at priority 3 of all the component links within |
| 1305 |
the TE link that can be used to carry live traffic." |
| 1306 |
REFERENCE |
| 1307 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1308 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1309 |
::= { teLinkDescriptorEntry 8 } |
| 1310 |
|
| 1311 |
teLinkDescrMaxLspBandwidthPrio4 OBJECT-TYPE |
| 1312 |
SYNTAX TeLinkBandwidth |
| 1313 |
UNITS "bps" |
| 1314 |
MAX-ACCESS read-create |
| 1315 |
STATUS current |
| 1316 |
DESCRIPTION |
| 1317 |
"This attribute specifies the maximum LSP bandwidth at |
| 1318 |
priority 4 on the TE link. This is the union of the maximum |
| 1319 |
LSP bandwidth at priority 4 of all the component links within |
| 1320 |
the TE link that can be used to carry live traffic." |
| 1321 |
REFERENCE |
| 1322 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1323 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1324 |
::= { teLinkDescriptorEntry 9 } |
| 1325 |
|
| 1326 |
teLinkDescrMaxLspBandwidthPrio5 OBJECT-TYPE |
| 1327 |
SYNTAX TeLinkBandwidth |
| 1328 |
UNITS "bps" |
| 1329 |
MAX-ACCESS read-create |
| 1330 |
STATUS current |
| 1331 |
DESCRIPTION |
| 1332 |
"This attribute specifies the maximum LSP bandwidth at |
| 1333 |
priority 5 on the TE link. This is the union of the maximum |
| 1334 |
LSP bandwidth at priority 5 of all the component links within |
| 1335 |
the TE link that can be used to carry live traffic." |
| 1336 |
REFERENCE |
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Dubuc, et al. Standards Track [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1346 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1347 |
::= { teLinkDescriptorEntry 10 } |
| 1348 |
|
| 1349 |
teLinkDescrMaxLspBandwidthPrio6 OBJECT-TYPE |
| 1350 |
SYNTAX TeLinkBandwidth |
| 1351 |
UNITS "bps" |
| 1352 |
MAX-ACCESS read-create |
| 1353 |
STATUS current |
| 1354 |
DESCRIPTION |
| 1355 |
"This attribute specifies the maximum LSP bandwidth at |
| 1356 |
priority 6 on the TE link. This is the union of the maximum |
| 1357 |
LSP bandwidth at priority 6 of all the component links within |
| 1358 |
the TE link that can be used to carry live traffic." |
| 1359 |
REFERENCE |
| 1360 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1361 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1362 |
::= { teLinkDescriptorEntry 11 } |
| 1363 |
|
| 1364 |
teLinkDescrMaxLspBandwidthPrio7 OBJECT-TYPE |
| 1365 |
SYNTAX TeLinkBandwidth |
| 1366 |
UNITS "bps" |
| 1367 |
MAX-ACCESS read-create |
| 1368 |
STATUS current |
| 1369 |
DESCRIPTION |
| 1370 |
"This attribute specifies the maximum LSP bandwidth at |
| 1371 |
priority 7 on the TE link. This is the union of the maximum |
| 1372 |
LSP bandwidth at priority 7 of all the component links within |
| 1373 |
the TE link that can be used to carry live traffic." |
| 1374 |
REFERENCE |
| 1375 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1376 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1377 |
::= { teLinkDescriptorEntry 12 } |
| 1378 |
|
| 1379 |
teLinkDescrInterfaceMtu OBJECT-TYPE |
| 1380 |
SYNTAX Unsigned32 (1..65535) |
| 1381 |
MAX-ACCESS read-create |
| 1382 |
STATUS current |
| 1383 |
DESCRIPTION |
| 1384 |
"This attribute specifies the interface MTU for the TE |
| 1385 |
link descriptor." |
| 1386 |
REFERENCE |
| 1387 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1388 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1389 |
::= { teLinkDescriptorEntry 13 } |
| 1390 |
|
| 1391 |
teLinkDescrIndication OBJECT-TYPE |
| 1392 |
SYNTAX TeLinkSonetSdhIndication |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Dubuc, et al. Standards Track [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
MAX-ACCESS read-create |
| 1402 |
STATUS current |
| 1403 |
DESCRIPTION |
| 1404 |
"This attribute specifies whether this interface supports |
| 1405 |
Standard or Arbitrary SONET/SDH." |
| 1406 |
REFERENCE |
| 1407 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1408 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1409 |
::= { teLinkDescriptorEntry 14 } |
| 1410 |
|
| 1411 |
teLinkDescrRowStatus OBJECT-TYPE |
| 1412 |
SYNTAX RowStatus |
| 1413 |
MAX-ACCESS read-create |
| 1414 |
STATUS current |
| 1415 |
DESCRIPTION |
| 1416 |
"This variable is used to create, modify, and/or |
| 1417 |
delete a row in this table. No read-create object |
| 1418 |
can be changed if teLinkDescrRowStatus is in the active(1) |
| 1419 |
state." |
| 1420 |
::= { teLinkDescriptorEntry 15 } |
| 1421 |
|
| 1422 |
teLinkDescrStorageType OBJECT-TYPE |
| 1423 |
SYNTAX StorageType |
| 1424 |
MAX-ACCESS read-create |
| 1425 |
STATUS current |
| 1426 |
DESCRIPTION |
| 1427 |
"The storage type for this conceptual row in the |
| 1428 |
teLinkDescriptorTable. Conceptual rows having the value |
| 1429 |
'permanent' need not allow write-access to any |
| 1430 |
columnar object in the row." |
| 1431 |
::= { teLinkDescriptorEntry 16 } |
| 1432 |
|
| 1433 |
-- End of teLinkDescriptorTable |
| 1434 |
|
| 1435 |
|
| 1436 |
-- TE Link Shared Risk Link Group Table |
| 1437 |
|
| 1438 |
teLinkSrlgTable OBJECT-TYPE |
| 1439 |
SYNTAX SEQUENCE OF TeLinkSrlgEntry |
| 1440 |
MAX-ACCESS not-accessible |
| 1441 |
STATUS current |
| 1442 |
DESCRIPTION |
| 1443 |
"This table specifies the SRLGs associated with TE links." |
| 1444 |
::= { teLinkObjects 3 } |
| 1445 |
|
| 1446 |
teLinkSrlgEntry OBJECT-TYPE |
| 1447 |
SYNTAX TeLinkSrlgEntry |
| 1448 |
MAX-ACCESS not-accessible |
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Dubuc, et al. Standards Track [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
STATUS current |
| 1458 |
DESCRIPTION |
| 1459 |
"An entry in this table contains information about an |
| 1460 |
SRLG associated with a TE link. |
| 1461 |
An ifEntry in the ifTable must exist before a |
| 1462 |
teLinkSrlgEntry using the same ifIndex is created. |
| 1463 |
The ifType of ifEntry must be teLink(200). |
| 1464 |
If a TE link entry in the ifTable is destroyed, then so |
| 1465 |
are all of the entries in the teLinkSrlgTable that use the |
| 1466 |
ifIndex of this TE link." |
| 1467 |
INDEX { ifIndex, teLinkSrlg } |
| 1468 |
::= { teLinkSrlgTable 1 } |
| 1469 |
|
| 1470 |
TeLinkSrlgEntry ::= SEQUENCE { |
| 1471 |
teLinkSrlg Unsigned32, |
| 1472 |
teLinkSrlgRowStatus RowStatus, |
| 1473 |
teLinkSrlgStorageType StorageType |
| 1474 |
} |
| 1475 |
|
| 1476 |
teLinkSrlg OBJECT-TYPE |
| 1477 |
SYNTAX Unsigned32 (0..4294967295) |
| 1478 |
MAX-ACCESS not-accessible |
| 1479 |
STATUS current |
| 1480 |
DESCRIPTION |
| 1481 |
"This identifies an SRLG supported by the TE link. An SRLG is |
| 1482 |
identified with a 32-bit number that is unique within an IGP |
| 1483 |
domain. Zero is a valid SRLG number." |
| 1484 |
REFERENCE |
| 1485 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1486 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1487 |
::= { teLinkSrlgEntry 1 } |
| 1488 |
|
| 1489 |
teLinkSrlgRowStatus OBJECT-TYPE |
| 1490 |
SYNTAX RowStatus |
| 1491 |
MAX-ACCESS read-create |
| 1492 |
STATUS current |
| 1493 |
DESCRIPTION |
| 1494 |
"This variable is used to create, modify, and/or |
| 1495 |
delete a row in this table. No read-create object can |
| 1496 |
be modified if teLinkSrlgRowStatus is active(1)." |
| 1497 |
::= { teLinkSrlgEntry 2 } |
| 1498 |
|
| 1499 |
teLinkSrlgStorageType OBJECT-TYPE |
| 1500 |
SYNTAX StorageType |
| 1501 |
MAX-ACCESS read-create |
| 1502 |
STATUS current |
| 1503 |
DESCRIPTION |
| 1504 |
"The storage type for this conceptual row in the |
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Dubuc, et al. Standards Track [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
teLinkSrlgTable. Conceptual rows having the value |
| 1514 |
'permanent' need not allow write-access to any |
| 1515 |
columnar object in the row." |
| 1516 |
::= { teLinkSrlgEntry 3 } |
| 1517 |
|
| 1518 |
-- End of teLinkSrlgTable |
| 1519 |
|
| 1520 |
|
| 1521 |
-- TE Link Bandwidth Table |
| 1522 |
|
| 1523 |
teLinkBandwidthTable OBJECT-TYPE |
| 1524 |
SYNTAX SEQUENCE OF TeLinkBandwidthEntry |
| 1525 |
MAX-ACCESS not-accessible |
| 1526 |
STATUS current |
| 1527 |
DESCRIPTION |
| 1528 |
"This table specifies the priority-based bandwidth table |
| 1529 |
for TE links." |
| 1530 |
::= { teLinkObjects 4 } |
| 1531 |
|
| 1532 |
teLinkBandwidthEntry OBJECT-TYPE |
| 1533 |
SYNTAX TeLinkBandwidthEntry |
| 1534 |
MAX-ACCESS not-accessible |
| 1535 |
STATUS current |
| 1536 |
DESCRIPTION |
| 1537 |
"An entry in this table contains information about |
| 1538 |
the priority-based bandwidth of TE links. An ifEntry in the |
| 1539 |
ifTable must exist before a teLinkBandwidthEntry using the |
| 1540 |
same ifIndex is created. The ifType of ifEntry must be |
| 1541 |
teLink(200). If a TE link entry in the ifTable is destroyed, |
| 1542 |
then so are all of the entries in the teLinkBandwidthTable |
| 1543 |
that use the ifIndex of this TE link." |
| 1544 |
INDEX { ifIndex, teLinkBandwidthPriority } |
| 1545 |
::= { teLinkBandwidthTable 1 } |
| 1546 |
|
| 1547 |
TeLinkBandwidthEntry ::= SEQUENCE { |
| 1548 |
teLinkBandwidthPriority TeLinkPriority, |
| 1549 |
teLinkBandwidthUnreserved TeLinkBandwidth, |
| 1550 |
teLinkBandwidthRowStatus RowStatus, |
| 1551 |
teLinkBandwidthStorageType StorageType |
| 1552 |
} |
| 1553 |
|
| 1554 |
teLinkBandwidthPriority OBJECT-TYPE |
| 1555 |
SYNTAX TeLinkPriority |
| 1556 |
MAX-ACCESS not-accessible |
| 1557 |
STATUS current |
| 1558 |
DESCRIPTION |
| 1559 |
"This attribute specifies the priority. A value of 0 is valid |
| 1560 |
as specified in the 'Traffic Engineering (TE) Extensions to |
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Dubuc, et al. Standards Track [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
OSPF Version 2' document." |
| 1570 |
REFERENCE |
| 1571 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1572 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a> and |
| 1573 |
Traffic Engineering (TE) Extensions to OSPF Version 2, |
| 1574 |
<a href="./rfc3630">RFC 3630</a>" |
| 1575 |
::= { teLinkBandwidthEntry 1 } |
| 1576 |
|
| 1577 |
teLinkBandwidthUnreserved OBJECT-TYPE |
| 1578 |
SYNTAX TeLinkBandwidth |
| 1579 |
UNITS "bps" |
| 1580 |
MAX-ACCESS read-only |
| 1581 |
STATUS current |
| 1582 |
DESCRIPTION |
| 1583 |
"This attribute specifies the TE link unreserved |
| 1584 |
bandwidth at priority p. It is the sum of the unreserved |
| 1585 |
bandwidths at priority p of all component links associated |
| 1586 |
with the TE link (excluding all links that are strictly |
| 1587 |
used as protecting links)." |
| 1588 |
REFERENCE |
| 1589 |
"Link Bundling in MPLS Traffic Engineering (TE), <a href="./rfc4201">RFC 4201</a>" |
| 1590 |
::= { teLinkBandwidthEntry 2 } |
| 1591 |
|
| 1592 |
teLinkBandwidthRowStatus OBJECT-TYPE |
| 1593 |
SYNTAX RowStatus |
| 1594 |
MAX-ACCESS read-create |
| 1595 |
STATUS current |
| 1596 |
DESCRIPTION |
| 1597 |
"This variable is used to create, modify, and/or |
| 1598 |
delete a row in this table. No read-create object |
| 1599 |
can be modified when teLinkBandwidthRowStatus is active(1)." |
| 1600 |
::= { teLinkBandwidthEntry 3 } |
| 1601 |
|
| 1602 |
teLinkBandwidthStorageType OBJECT-TYPE |
| 1603 |
SYNTAX StorageType |
| 1604 |
MAX-ACCESS read-create |
| 1605 |
STATUS current |
| 1606 |
DESCRIPTION |
| 1607 |
"The storage type for this conceptual row in the |
| 1608 |
teLinkBandwidthTable. Conceptual rows having the value |
| 1609 |
'permanent' need not allow write-access to any |
| 1610 |
columnar object in the row." |
| 1611 |
::= { teLinkBandwidthEntry 4 } |
| 1612 |
|
| 1613 |
-- End of teLinkBandwidthTable |
| 1614 |
|
| 1615 |
|
| 1616 |
-- Component Link Table |
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Dubuc, et al. Standards Track [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
componentLinkTable OBJECT-TYPE |
| 1626 |
SYNTAX SEQUENCE OF ComponentLinkEntry |
| 1627 |
MAX-ACCESS not-accessible |
| 1628 |
STATUS current |
| 1629 |
DESCRIPTION |
| 1630 |
"This table specifies the component link parameters." |
| 1631 |
::= { teLinkObjects 5 } |
| 1632 |
|
| 1633 |
componentLinkEntry OBJECT-TYPE |
| 1634 |
SYNTAX ComponentLinkEntry |
| 1635 |
MAX-ACCESS not-accessible |
| 1636 |
STATUS current |
| 1637 |
DESCRIPTION |
| 1638 |
"An entry in this table exists for each ifEntry that |
| 1639 |
represents a component link. An ifEntry must exist in |
| 1640 |
the ifTable before a componentLinkEntry is created with |
| 1641 |
the corresponding ifIndex. ifEntry's ifType can be |
| 1642 |
of any interface type that has been defined for TE Link |
| 1643 |
interworking. Examples include ATM, Frame Relay, Ethernet, |
| 1644 |
etc. If an entry representing a component link is destroyed |
| 1645 |
in the ifTable, then so is the corresponding entry in the |
| 1646 |
componentLinkTable. The administrative and operational |
| 1647 |
status values are controlled from the ifEntry." |
| 1648 |
INDEX { ifIndex } |
| 1649 |
::= { componentLinkTable 1 } |
| 1650 |
|
| 1651 |
ComponentLinkEntry ::= SEQUENCE { |
| 1652 |
componentLinkMaxResBandwidth TeLinkBandwidth, |
| 1653 |
componentLinkPreferredProtection TeLinkProtection, |
| 1654 |
componentLinkCurrentProtection TeLinkProtection, |
| 1655 |
componentLinkRowStatus RowStatus, |
| 1656 |
componentLinkStorageType StorageType |
| 1657 |
} |
| 1658 |
|
| 1659 |
componentLinkMaxResBandwidth OBJECT-TYPE |
| 1660 |
SYNTAX TeLinkBandwidth |
| 1661 |
UNITS "bps" |
| 1662 |
MAX-ACCESS read-create |
| 1663 |
STATUS current |
| 1664 |
DESCRIPTION |
| 1665 |
"This attribute specifies the maximum reservable bandwidth on |
| 1666 |
the component link." |
| 1667 |
REFERENCE |
| 1668 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1669 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1670 |
::= { componentLinkEntry 1 } |
| 1671 |
|
| 1672 |
componentLinkPreferredProtection OBJECT-TYPE |
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Dubuc, et al. Standards Track [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
SYNTAX TeLinkProtection |
| 1682 |
MAX-ACCESS read-create |
| 1683 |
STATUS current |
| 1684 |
DESCRIPTION |
| 1685 |
"This attribute specifies whether this component link is |
| 1686 |
a primary or secondary entity." |
| 1687 |
::= { componentLinkEntry 2 } |
| 1688 |
|
| 1689 |
componentLinkCurrentProtection OBJECT-TYPE |
| 1690 |
SYNTAX TeLinkProtection |
| 1691 |
MAX-ACCESS read-only |
| 1692 |
STATUS current |
| 1693 |
DESCRIPTION |
| 1694 |
"This attribute specifies whether this component link is |
| 1695 |
currently used as primary or secondary link." |
| 1696 |
::= { componentLinkEntry 3 } |
| 1697 |
|
| 1698 |
componentLinkRowStatus OBJECT-TYPE |
| 1699 |
SYNTAX RowStatus |
| 1700 |
MAX-ACCESS read-create |
| 1701 |
STATUS current |
| 1702 |
DESCRIPTION |
| 1703 |
"This variable is used to create, modify, and/or |
| 1704 |
delete a row in this table. No read-create object |
| 1705 |
can be modified when componentLinkRowStatus is active(1)." |
| 1706 |
::= { componentLinkEntry 4 } |
| 1707 |
|
| 1708 |
componentLinkStorageType OBJECT-TYPE |
| 1709 |
SYNTAX StorageType |
| 1710 |
MAX-ACCESS read-create |
| 1711 |
STATUS current |
| 1712 |
DESCRIPTION |
| 1713 |
"The storage type for this conceptual row in the |
| 1714 |
componentLinkTable. Conceptual rows having the value |
| 1715 |
'permanent' need not allow write-access to any |
| 1716 |
columnar object in the row." |
| 1717 |
::= { componentLinkEntry 5 } |
| 1718 |
|
| 1719 |
-- End of componentLinkTable |
| 1720 |
|
| 1721 |
|
| 1722 |
-- Component Link Descriptor Table |
| 1723 |
|
| 1724 |
componentLinkDescriptorTable OBJECT-TYPE |
| 1725 |
SYNTAX SEQUENCE OF ComponentLinkDescriptorEntry |
| 1726 |
MAX-ACCESS not-accessible |
| 1727 |
STATUS current |
| 1728 |
DESCRIPTION |
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Dubuc, et al. Standards Track [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
"This table specifies the interface switching capability |
| 1738 |
descriptors associated with the component links." |
| 1739 |
::= { teLinkObjects 6 } |
| 1740 |
|
| 1741 |
componentLinkDescriptorEntry OBJECT-TYPE |
| 1742 |
SYNTAX ComponentLinkDescriptorEntry |
| 1743 |
MAX-ACCESS not-accessible |
| 1744 |
STATUS current |
| 1745 |
DESCRIPTION |
| 1746 |
"An entry in this table is created for every component link |
| 1747 |
descriptor. An ifEntry in the ifTable must exist before a |
| 1748 |
componentLinkDescriptorEntry using the same ifIndex is |
| 1749 |
created. ifEntry's ifType can be of any interface type that |
| 1750 |
has been defined for TE Link interworking. Examples include |
| 1751 |
ATM, Frame Relay, Ethernet, etc. If a component link entry |
| 1752 |
in the ifTable is destroyed, then so are all entries in the |
| 1753 |
componentLinkDescriptorTable that use the ifIndex of this |
| 1754 |
component link." |
| 1755 |
INDEX { ifIndex, componentLinkDescrId } |
| 1756 |
::= { componentLinkDescriptorTable 1 } |
| 1757 |
|
| 1758 |
ComponentLinkDescriptorEntry ::= SEQUENCE { |
| 1759 |
componentLinkDescrId Unsigned32, |
| 1760 |
componentLinkDescrSwitchingCapability TeLinkSwitchingCapability, |
| 1761 |
componentLinkDescrEncodingType TeLinkEncodingType, |
| 1762 |
componentLinkDescrMinLspBandwidth TeLinkBandwidth, |
| 1763 |
componentLinkDescrMaxLspBandwidthPrio0 TeLinkBandwidth, |
| 1764 |
componentLinkDescrMaxLspBandwidthPrio1 TeLinkBandwidth, |
| 1765 |
componentLinkDescrMaxLspBandwidthPrio2 TeLinkBandwidth, |
| 1766 |
componentLinkDescrMaxLspBandwidthPrio3 TeLinkBandwidth, |
| 1767 |
componentLinkDescrMaxLspBandwidthPrio4 TeLinkBandwidth, |
| 1768 |
componentLinkDescrMaxLspBandwidthPrio5 TeLinkBandwidth, |
| 1769 |
componentLinkDescrMaxLspBandwidthPrio6 TeLinkBandwidth, |
| 1770 |
componentLinkDescrMaxLspBandwidthPrio7 TeLinkBandwidth, |
| 1771 |
componentLinkDescrInterfaceMtu Unsigned32, |
| 1772 |
componentLinkDescrIndication TeLinkSonetSdhIndication, |
| 1773 |
componentLinkDescrRowStatus RowStatus, |
| 1774 |
componentLinkDescrStorageType StorageType |
| 1775 |
} |
| 1776 |
|
| 1777 |
componentLinkDescrId OBJECT-TYPE |
| 1778 |
SYNTAX Unsigned32 (1..4294967295) |
| 1779 |
MAX-ACCESS not-accessible |
| 1780 |
STATUS current |
| 1781 |
DESCRIPTION |
| 1782 |
"This object specifies the link descriptor identifier." |
| 1783 |
::= { componentLinkDescriptorEntry 1 } |
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Dubuc, et al. Standards Track [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
componentLinkDescrSwitchingCapability OBJECT-TYPE |
| 1794 |
SYNTAX TeLinkSwitchingCapability |
| 1795 |
MAX-ACCESS read-create |
| 1796 |
STATUS current |
| 1797 |
DESCRIPTION |
| 1798 |
"This attribute specifies link multiplexing capabilities of |
| 1799 |
the component link." |
| 1800 |
REFERENCE |
| 1801 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1802 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1803 |
::= { componentLinkDescriptorEntry 2 } |
| 1804 |
|
| 1805 |
componentLinkDescrEncodingType OBJECT-TYPE |
| 1806 |
SYNTAX TeLinkEncodingType |
| 1807 |
MAX-ACCESS read-create |
| 1808 |
STATUS current |
| 1809 |
DESCRIPTION |
| 1810 |
"This attribute specifies the component link encoding type." |
| 1811 |
REFERENCE |
| 1812 |
"Generalized Multi-Protocol Label Switching (GMPLS) Signaling |
| 1813 |
Functional Description, <a href="./rfc3471">RFC 3471</a>" |
| 1814 |
::= { componentLinkDescriptorEntry 3 } |
| 1815 |
|
| 1816 |
componentLinkDescrMinLspBandwidth OBJECT-TYPE |
| 1817 |
SYNTAX TeLinkBandwidth |
| 1818 |
UNITS "bps" |
| 1819 |
MAX-ACCESS read-create |
| 1820 |
STATUS current |
| 1821 |
DESCRIPTION |
| 1822 |
"This attribute specifies the minimum LSP bandwidth on |
| 1823 |
the component link." |
| 1824 |
REFERENCE |
| 1825 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1826 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1827 |
::= { componentLinkDescriptorEntry 4 } |
| 1828 |
|
| 1829 |
componentLinkDescrMaxLspBandwidthPrio0 OBJECT-TYPE |
| 1830 |
SYNTAX TeLinkBandwidth |
| 1831 |
UNITS "bps" |
| 1832 |
MAX-ACCESS read-create |
| 1833 |
STATUS current |
| 1834 |
DESCRIPTION |
| 1835 |
"This attribute specifies the maximum LSP bandwidth at |
| 1836 |
priority 0 on the component link." |
| 1837 |
REFERENCE |
| 1838 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1839 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1840 |
::= { componentLinkDescriptorEntry 5 } |
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Dubuc, et al. Standards Track [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
componentLinkDescrMaxLspBandwidthPrio1 OBJECT-TYPE |
| 1850 |
SYNTAX TeLinkBandwidth |
| 1851 |
UNITS "bps" |
| 1852 |
MAX-ACCESS read-create |
| 1853 |
STATUS current |
| 1854 |
DESCRIPTION |
| 1855 |
"This attribute specifies the maximum LSP bandwidth at |
| 1856 |
priority 1 on the component link." |
| 1857 |
REFERENCE |
| 1858 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1859 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1860 |
::= { componentLinkDescriptorEntry 6 } |
| 1861 |
|
| 1862 |
componentLinkDescrMaxLspBandwidthPrio2 OBJECT-TYPE |
| 1863 |
SYNTAX TeLinkBandwidth |
| 1864 |
UNITS "bps" |
| 1865 |
MAX-ACCESS read-create |
| 1866 |
STATUS current |
| 1867 |
DESCRIPTION |
| 1868 |
"This attribute specifies the maximum LSP bandwidth at |
| 1869 |
priority 2 on the component link." |
| 1870 |
REFERENCE |
| 1871 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1872 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1873 |
::= { componentLinkDescriptorEntry 7 } |
| 1874 |
|
| 1875 |
componentLinkDescrMaxLspBandwidthPrio3 OBJECT-TYPE |
| 1876 |
SYNTAX TeLinkBandwidth |
| 1877 |
UNITS "bps" |
| 1878 |
MAX-ACCESS read-create |
| 1879 |
STATUS current |
| 1880 |
DESCRIPTION |
| 1881 |
"This attribute specifies the maximum LSP bandwidth at |
| 1882 |
priority 3 on the component link." |
| 1883 |
REFERENCE |
| 1884 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1885 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1886 |
::= { componentLinkDescriptorEntry 8 } |
| 1887 |
|
| 1888 |
componentLinkDescrMaxLspBandwidthPrio4 OBJECT-TYPE |
| 1889 |
SYNTAX TeLinkBandwidth |
| 1890 |
UNITS "bps" |
| 1891 |
MAX-ACCESS read-create |
| 1892 |
STATUS current |
| 1893 |
DESCRIPTION |
| 1894 |
"This attribute specifies the maximum LSP bandwidth at |
| 1895 |
priority 4 on the component link." |
| 1896 |
REFERENCE |
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Dubuc, et al. Standards Track [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1906 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1907 |
::= { componentLinkDescriptorEntry 9 } |
| 1908 |
|
| 1909 |
componentLinkDescrMaxLspBandwidthPrio5 OBJECT-TYPE |
| 1910 |
SYNTAX TeLinkBandwidth |
| 1911 |
UNITS "thousand bps" |
| 1912 |
MAX-ACCESS read-create |
| 1913 |
STATUS current |
| 1914 |
DESCRIPTION |
| 1915 |
"This attribute specifies the maximum LSP bandwidth at |
| 1916 |
priority 5 on the component link." |
| 1917 |
REFERENCE |
| 1918 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1919 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1920 |
::= { componentLinkDescriptorEntry 10 } |
| 1921 |
|
| 1922 |
componentLinkDescrMaxLspBandwidthPrio6 OBJECT-TYPE |
| 1923 |
SYNTAX TeLinkBandwidth |
| 1924 |
UNITS "bps" |
| 1925 |
MAX-ACCESS read-create |
| 1926 |
STATUS current |
| 1927 |
DESCRIPTION |
| 1928 |
"This attribute specifies the maximum LSP bandwidth at |
| 1929 |
priority 6 on the component link." |
| 1930 |
REFERENCE |
| 1931 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1932 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1933 |
::= { componentLinkDescriptorEntry 11 } |
| 1934 |
|
| 1935 |
componentLinkDescrMaxLspBandwidthPrio7 OBJECT-TYPE |
| 1936 |
SYNTAX TeLinkBandwidth |
| 1937 |
UNITS "bps" |
| 1938 |
MAX-ACCESS read-create |
| 1939 |
STATUS current |
| 1940 |
DESCRIPTION |
| 1941 |
"This attribute specifies the maximum LSP bandwidth at |
| 1942 |
priority 7 on the component link." |
| 1943 |
REFERENCE |
| 1944 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1945 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1946 |
::= { componentLinkDescriptorEntry 12 } |
| 1947 |
|
| 1948 |
componentLinkDescrInterfaceMtu OBJECT-TYPE |
| 1949 |
SYNTAX Unsigned32 (1..65535) |
| 1950 |
MAX-ACCESS read-create |
| 1951 |
STATUS current |
| 1952 |
DESCRIPTION |
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Dubuc, et al. Standards Track [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
"This attribute specifies the interface MTU for the component |
| 1962 |
link descriptor." |
| 1963 |
REFERENCE |
| 1964 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1965 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1966 |
::= { componentLinkDescriptorEntry 13 } |
| 1967 |
|
| 1968 |
componentLinkDescrIndication OBJECT-TYPE |
| 1969 |
SYNTAX TeLinkSonetSdhIndication |
| 1970 |
MAX-ACCESS read-create |
| 1971 |
STATUS current |
| 1972 |
DESCRIPTION |
| 1973 |
"This attribute specifies whether this interface supports |
| 1974 |
Standard or Arbitrary SONET/SDH." |
| 1975 |
REFERENCE |
| 1976 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 1977 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 1978 |
::= { componentLinkDescriptorEntry 14 } |
| 1979 |
|
| 1980 |
componentLinkDescrRowStatus OBJECT-TYPE |
| 1981 |
SYNTAX RowStatus |
| 1982 |
MAX-ACCESS read-create |
| 1983 |
STATUS current |
| 1984 |
DESCRIPTION |
| 1985 |
"This variable is used to create, modify, and/or |
| 1986 |
delete a row in this table. No read-create object |
| 1987 |
can be modified when componentLinkDescrRowStatus |
| 1988 |
is active(1)." |
| 1989 |
::= { componentLinkDescriptorEntry 15 } |
| 1990 |
|
| 1991 |
componentLinkDescrStorageType OBJECT-TYPE |
| 1992 |
SYNTAX StorageType |
| 1993 |
MAX-ACCESS read-create |
| 1994 |
STATUS current |
| 1995 |
DESCRIPTION |
| 1996 |
"The storage type for this conceptual row in the |
| 1997 |
componentLinkDescriptorTable. Conceptual rows |
| 1998 |
having the value 'permanent' need not allow write-access |
| 1999 |
to any columnar object in the row." |
| 2000 |
::= { componentLinkDescriptorEntry 16 } |
| 2001 |
|
| 2002 |
-- End of componentLinkDescriptorTable |
| 2003 |
|
| 2004 |
|
| 2005 |
-- Component Link Bandwidth Table |
| 2006 |
|
| 2007 |
componentLinkBandwidthTable OBJECT-TYPE |
| 2008 |
SYNTAX SEQUENCE OF ComponentLinkBandwidthEntry |
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
<span class="grey">Dubuc, et al. Standards Track [Page 36]</span></pre> |
| 2013 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2014 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2015 |
|
| 2016 |
|
| 2017 |
MAX-ACCESS not-accessible |
| 2018 |
STATUS current |
| 2019 |
DESCRIPTION |
| 2020 |
"This table specifies the priority-based bandwidth |
| 2021 |
for component links." |
| 2022 |
::= { teLinkObjects 7 } |
| 2023 |
|
| 2024 |
componentLinkBandwidthEntry OBJECT-TYPE |
| 2025 |
SYNTAX ComponentLinkBandwidthEntry |
| 2026 |
MAX-ACCESS not-accessible |
| 2027 |
STATUS current |
| 2028 |
DESCRIPTION |
| 2029 |
"An entry in this table contains information about |
| 2030 |
the priority-based bandwidth on component links. |
| 2031 |
An ifEntry in the ifTable must exist before a |
| 2032 |
componentLinkBandwidthEntry using the same ifIndex is |
| 2033 |
created. ifEntry's ifType can be of any interface type that |
| 2034 |
has been defined for TE Link interworking. Examples |
| 2035 |
include ATM, Frame Relay, Ethernet, etc. If a component link |
| 2036 |
entry in the ifTable is destroyed, then so are all entries |
| 2037 |
in the componentLinkBandwidthTable that use the ifIndex of |
| 2038 |
this component link." |
| 2039 |
INDEX { ifIndex, componentLinkBandwidthPriority } |
| 2040 |
::= { componentLinkBandwidthTable 1 } |
| 2041 |
|
| 2042 |
ComponentLinkBandwidthEntry ::= SEQUENCE { |
| 2043 |
componentLinkBandwidthPriority TeLinkPriority, |
| 2044 |
componentLinkBandwidthUnreserved TeLinkBandwidth, |
| 2045 |
componentLinkBandwidthRowStatus RowStatus, |
| 2046 |
componentLinkBandwidthStorageType StorageType |
| 2047 |
} |
| 2048 |
|
| 2049 |
componentLinkBandwidthPriority OBJECT-TYPE |
| 2050 |
SYNTAX TeLinkPriority |
| 2051 |
MAX-ACCESS not-accessible |
| 2052 |
STATUS current |
| 2053 |
DESCRIPTION |
| 2054 |
"This attribute specifies the priority. A value of 0 is valid |
| 2055 |
as specified in the 'Traffic Engineering (TE) Extensions to |
| 2056 |
OSPF Version 2' document." |
| 2057 |
REFERENCE |
| 2058 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 2059 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a> and |
| 2060 |
Traffic Engineering (TE) Extensions to OSPF Version 2, |
| 2061 |
<a href="./rfc3630">RFC 3630</a>" |
| 2062 |
::= { componentLinkBandwidthEntry 1 } |
| 2063 |
|
| 2064 |
componentLinkBandwidthUnreserved OBJECT-TYPE |
| 2065 |
|
| 2066 |
|
| 2067 |
|
| 2068 |
<span class="grey">Dubuc, et al. Standards Track [Page 37]</span></pre> |
| 2069 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2070 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2071 |
|
| 2072 |
|
| 2073 |
SYNTAX TeLinkBandwidth |
| 2074 |
UNITS "bps" |
| 2075 |
MAX-ACCESS read-only |
| 2076 |
STATUS current |
| 2077 |
DESCRIPTION |
| 2078 |
"This attribute specifies the component link unreserved |
| 2079 |
bandwidth at priority p." |
| 2080 |
REFERENCE |
| 2081 |
"OSPF Extensions in Support of Generalized Multi-Protocol |
| 2082 |
Label Switching (GMPLS), <a href="./rfc4203">RFC 4203</a>" |
| 2083 |
::= { componentLinkBandwidthEntry 2 } |
| 2084 |
|
| 2085 |
componentLinkBandwidthRowStatus OBJECT-TYPE |
| 2086 |
SYNTAX RowStatus |
| 2087 |
MAX-ACCESS read-create |
| 2088 |
STATUS current |
| 2089 |
DESCRIPTION |
| 2090 |
"This variable is used to create, modify, and/or |
| 2091 |
delete a row in this table. No read-create object can |
| 2092 |
be modified when componentLinkBandwidthRowStatus is |
| 2093 |
active(1)." |
| 2094 |
::= { componentLinkBandwidthEntry 3 } |
| 2095 |
|
| 2096 |
componentLinkBandwidthStorageType OBJECT-TYPE |
| 2097 |
SYNTAX StorageType |
| 2098 |
MAX-ACCESS read-create |
| 2099 |
STATUS current |
| 2100 |
DESCRIPTION |
| 2101 |
"The storage type for this conceptual row in the |
| 2102 |
componentLinkBandwidthTable. Conceptual rows |
| 2103 |
having the value 'permanent' need not allow write-access |
| 2104 |
to any columnar object in the row." |
| 2105 |
::= { componentLinkBandwidthEntry 4 } |
| 2106 |
|
| 2107 |
-- End of componentLinkBandwidthTable |
| 2108 |
|
| 2109 |
|
| 2110 |
-- Module compliance |
| 2111 |
|
| 2112 |
teLinkCompliances |
| 2113 |
OBJECT IDENTIFIER ::= { teLinkConformance 1 } |
| 2114 |
|
| 2115 |
teLinkGroups |
| 2116 |
OBJECT IDENTIFIER ::= { teLinkConformance 2 } |
| 2117 |
|
| 2118 |
teLinkModuleFullCompliance MODULE-COMPLIANCE |
| 2119 |
STATUS current |
| 2120 |
DESCRIPTION |
| 2121 |
|
| 2122 |
|
| 2123 |
|
| 2124 |
<span class="grey">Dubuc, et al. Standards Track [Page 38]</span></pre> |
| 2125 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2126 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2127 |
|
| 2128 |
|
| 2129 |
"Compliance statement for agents that support read-create |
| 2130 |
so that both configuration and monitoring of TE links can |
| 2131 |
be accomplished via this MIB module." |
| 2132 |
MODULE -- this module |
| 2133 |
|
| 2134 |
MANDATORY-GROUPS { teLinkGroup, |
| 2135 |
teLinkBandwidthGroup, |
| 2136 |
componentLinkBandwidthGroup } |
| 2137 |
|
| 2138 |
GROUP teLinkSrlgGroup |
| 2139 |
DESCRIPTION |
| 2140 |
"This group is mandatory for GMPLS enabled devices." |
| 2141 |
|
| 2142 |
GROUP teLinkPscGroup |
| 2143 |
DESCRIPTION |
| 2144 |
"This group is mandatory for devices that support the |
| 2145 |
packet switching capability." |
| 2146 |
|
| 2147 |
GROUP teLinkTdmGroup |
| 2148 |
DESCRIPTION |
| 2149 |
"This group is mandatory for devices that support the TDM |
| 2150 |
switching capability." |
| 2151 |
|
| 2152 |
-- teLinkTable |
| 2153 |
|
| 2154 |
OBJECT teLinkAddressType |
| 2155 |
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } |
| 2156 |
DESCRIPTION |
| 2157 |
"Only ipv4(1) and ipv6(2) address types need to be |
| 2158 |
supported for numbered links. For unnumbered links, the |
| 2159 |
unknown(0) address type needs to be supported." |
| 2160 |
|
| 2161 |
OBJECT teLinkLocalIpAddr |
| 2162 |
SYNTAX InetAddress (SIZE(0|4|16)) |
| 2163 |
DESCRIPTION |
| 2164 |
"Size of TE link IP address depends on type of TE link. |
| 2165 |
TE link IP address size is zero if the link is unnumbered, |
| 2166 |
four if the link IP address is IPv4, and sixteen if the |
| 2167 |
link IP address is IPv6." |
| 2168 |
|
| 2169 |
OBJECT teLinkRemoteIpAddr |
| 2170 |
SYNTAX InetAddress (SIZE(0|4|16)) |
| 2171 |
DESCRIPTION |
| 2172 |
"Size of TE link IP address depends on type of TE link. |
| 2173 |
TE link IP address size is zero if the link is unnumbered, |
| 2174 |
four if the link IP address is IPv4, and sixteen if the |
| 2175 |
link IP address is IPv6." |
| 2176 |
|
| 2177 |
|
| 2178 |
|
| 2179 |
|
| 2180 |
<span class="grey">Dubuc, et al. Standards Track [Page 39]</span></pre> |
| 2181 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2182 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2183 |
|
| 2184 |
|
| 2185 |
OBJECT teLinkRowStatus |
| 2186 |
SYNTAX RowStatus { active(1), notInService(2) } |
| 2187 |
WRITE-SYNTAX RowStatus { active(1), notInService(2), |
| 2188 |
createAndGo(4), destroy(6) } |
| 2189 |
DESCRIPTION |
| 2190 |
"Support for notReady(3) and createAndWait(5) is |
| 2191 |
not required." |
| 2192 |
|
| 2193 |
-- teLinkDescriptorTable |
| 2194 |
|
| 2195 |
OBJECT teLinkDescrRowStatus |
| 2196 |
SYNTAX RowStatus { active(1), notInService(2) } |
| 2197 |
WRITE-SYNTAX RowStatus { active(1), notInService(2), |
| 2198 |
createAndGo(4), destroy(6) } |
| 2199 |
DESCRIPTION |
| 2200 |
"Support for notReady(3) and createAndWait(5) is |
| 2201 |
not required." |
| 2202 |
|
| 2203 |
-- teLinkSrlgTable |
| 2204 |
|
| 2205 |
OBJECT teLinkSrlgRowStatus |
| 2206 |
SYNTAX RowStatus { active(1), notInService(2) } |
| 2207 |
WRITE-SYNTAX RowStatus { active(1), notInService(2), |
| 2208 |
createAndGo(4), destroy(6) } |
| 2209 |
DESCRIPTION |
| 2210 |
"Support for notReady(3) and createAndWait(5) is |
| 2211 |
not required." |
| 2212 |
|
| 2213 |
-- teLinkBandwidthTable |
| 2214 |
|
| 2215 |
OBJECT teLinkBandwidthRowStatus |
| 2216 |
SYNTAX RowStatus { active(1), notInService(2) } |
| 2217 |
WRITE-SYNTAX RowStatus { active(1), notInService(2), |
| 2218 |
createAndGo(4), destroy(6) } |
| 2219 |
DESCRIPTION |
| 2220 |
"Support for notReady(3) and createAndWait(5) is |
| 2221 |
not required." |
| 2222 |
|
| 2223 |
-- componentLinkTable |
| 2224 |
|
| 2225 |
OBJECT componentLinkRowStatus |
| 2226 |
SYNTAX RowStatus { active(1), notInService(2) } |
| 2227 |
WRITE-SYNTAX RowStatus { active(1), notInService(2), |
| 2228 |
createAndGo(4), destroy(6) } |
| 2229 |
DESCRIPTION |
| 2230 |
"Support for notReady(3) and createAndWait(5) is |
| 2231 |
not required." |
| 2232 |
|
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
<span class="grey">Dubuc, et al. Standards Track [Page 40]</span></pre> |
| 2237 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2238 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2239 |
|
| 2240 |
|
| 2241 |
-- componentLinkDescriptorTable |
| 2242 |
|
| 2243 |
OBJECT componentLinkDescrRowStatus |
| 2244 |
SYNTAX RowStatus { active(1), notInService(2) } |
| 2245 |
WRITE-SYNTAX RowStatus { active(1), notInService(2), |
| 2246 |
createAndGo(4), destroy(6) } |
| 2247 |
DESCRIPTION |
| 2248 |
"Support for notReady(3) and createAndWait(5) is |
| 2249 |
not required." |
| 2250 |
|
| 2251 |
-- componentLinkBandwidthTable |
| 2252 |
|
| 2253 |
OBJECT componentLinkBandwidthRowStatus |
| 2254 |
SYNTAX RowStatus { active(1), notInService(2) } |
| 2255 |
WRITE-SYNTAX RowStatus { active(1), notInService(2), |
| 2256 |
createAndGo(4), destroy(6) } |
| 2257 |
DESCRIPTION |
| 2258 |
"Support for notReady(3) and createAndWait(5) is |
| 2259 |
not required." |
| 2260 |
|
| 2261 |
::= { teLinkCompliances 1 } |
| 2262 |
|
| 2263 |
teLinkModuleReadOnlyCompliance MODULE-COMPLIANCE |
| 2264 |
STATUS current |
| 2265 |
DESCRIPTION |
| 2266 |
"Compliance statement for agents that support the |
| 2267 |
monitoring of the TE link MIB module." |
| 2268 |
MODULE -- this module |
| 2269 |
|
| 2270 |
MANDATORY-GROUPS { teLinkGroup, |
| 2271 |
teLinkBandwidthGroup, |
| 2272 |
componentLinkBandwidthGroup } |
| 2273 |
|
| 2274 |
GROUP teLinkSrlgGroup |
| 2275 |
DESCRIPTION |
| 2276 |
"This group is mandatory for GMPLS enabled devices." |
| 2277 |
|
| 2278 |
GROUP teLinkPscGroup |
| 2279 |
DESCRIPTION |
| 2280 |
"This group is mandatory for devices that support the |
| 2281 |
packet switching capability." |
| 2282 |
|
| 2283 |
GROUP teLinkTdmGroup |
| 2284 |
DESCRIPTION |
| 2285 |
"This group is mandatory for devices that support the TDM |
| 2286 |
switching capability." |
| 2287 |
|
| 2288 |
-- teLinkTable |
| 2289 |
|
| 2290 |
|
| 2291 |
|
| 2292 |
<span class="grey">Dubuc, et al. Standards Track [Page 41]</span></pre> |
| 2293 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2294 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2295 |
|
| 2296 |
|
| 2297 |
OBJECT teLinkAddressType |
| 2298 |
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } |
| 2299 |
MIN-ACCESS read-only |
| 2300 |
DESCRIPTION |
| 2301 |
"Only ipv4(1) and ipv6(2) address types need to be |
| 2302 |
supported for numbered links. For unnumbered links, the |
| 2303 |
unknown(0) address type needs to be supported." |
| 2304 |
|
| 2305 |
OBJECT teLinkLocalIpAddr |
| 2306 |
SYNTAX InetAddress (SIZE(0|4|16)) |
| 2307 |
MIN-ACCESS read-only |
| 2308 |
DESCRIPTION |
| 2309 |
"Size of TE link IP address depends on type of TE link. |
| 2310 |
TE link IP address size is zero if the link is unnumbered, |
| 2311 |
four if the link IP address is IPv4, and sixteen if the |
| 2312 |
link IP address is IPv6." |
| 2313 |
|
| 2314 |
OBJECT teLinkRemoteIpAddr |
| 2315 |
SYNTAX InetAddress (SIZE(0|4|16)) |
| 2316 |
MIN-ACCESS read-only |
| 2317 |
DESCRIPTION |
| 2318 |
"Size of TE link IP address depends on type of TE link. |
| 2319 |
TE link IP address size is zero if the link is unnumbered, |
| 2320 |
four if the link IP address is IPv4, and sixteen if the |
| 2321 |
link IP address is IPv6." |
| 2322 |
|
| 2323 |
OBJECT teLinkProtectionType |
| 2324 |
MIN-ACCESS read-only |
| 2325 |
DESCRIPTION |
| 2326 |
"Write access is not required." |
| 2327 |
|
| 2328 |
OBJECT teLinkWorkingPriority |
| 2329 |
MIN-ACCESS read-only |
| 2330 |
DESCRIPTION |
| 2331 |
"Write access is not required." |
| 2332 |
|
| 2333 |
OBJECT teLinkRowStatus |
| 2334 |
SYNTAX RowStatus { active(1) } |
| 2335 |
MIN-ACCESS read-only |
| 2336 |
DESCRIPTION |
| 2337 |
"Write access is not required and active(1) is the |
| 2338 |
only status that needs to be supported." |
| 2339 |
|
| 2340 |
OBJECT teLinkStorageType |
| 2341 |
MIN-ACCESS read-only |
| 2342 |
DESCRIPTION |
| 2343 |
"Write access is not required." |
| 2344 |
|
| 2345 |
|
| 2346 |
|
| 2347 |
|
| 2348 |
<span class="grey">Dubuc, et al. Standards Track [Page 42]</span></pre> |
| 2349 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2350 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2351 |
|
| 2352 |
|
| 2353 |
-- teLinkDescriptorTable |
| 2354 |
|
| 2355 |
OBJECT teLinkDescrSwitchingCapability |
| 2356 |
MIN-ACCESS read-only |
| 2357 |
DESCRIPTION |
| 2358 |
"Write access is not required." |
| 2359 |
|
| 2360 |
OBJECT teLinkDescrEncodingType |
| 2361 |
MIN-ACCESS read-only |
| 2362 |
DESCRIPTION |
| 2363 |
"Write access is not required." |
| 2364 |
|
| 2365 |
OBJECT teLinkDescrMinLspBandwidth |
| 2366 |
MIN-ACCESS read-only |
| 2367 |
DESCRIPTION |
| 2368 |
"Write access is not required." |
| 2369 |
|
| 2370 |
OBJECT teLinkDescrMaxLspBandwidthPrio0 |
| 2371 |
MIN-ACCESS read-only |
| 2372 |
DESCRIPTION |
| 2373 |
"Write access is not required." |
| 2374 |
|
| 2375 |
OBJECT teLinkDescrMaxLspBandwidthPrio1 |
| 2376 |
MIN-ACCESS read-only |
| 2377 |
DESCRIPTION |
| 2378 |
"Write access is not required." |
| 2379 |
|
| 2380 |
OBJECT teLinkDescrMaxLspBandwidthPrio2 |
| 2381 |
MIN-ACCESS read-only |
| 2382 |
DESCRIPTION |
| 2383 |
"Write access is not required." |
| 2384 |
|
| 2385 |
OBJECT teLinkDescrMaxLspBandwidthPrio3 |
| 2386 |
MIN-ACCESS read-only |
| 2387 |
DESCRIPTION |
| 2388 |
"Write access is not required." |
| 2389 |
|
| 2390 |
OBJECT teLinkDescrMaxLspBandwidthPrio4 |
| 2391 |
MIN-ACCESS read-only |
| 2392 |
DESCRIPTION |
| 2393 |
"Write access is not required." |
| 2394 |
|
| 2395 |
OBJECT teLinkDescrMaxLspBandwidthPrio5 |
| 2396 |
MIN-ACCESS read-only |
| 2397 |
DESCRIPTION |
| 2398 |
"Write access is not required." |
| 2399 |
|
| 2400 |
OBJECT teLinkDescrMaxLspBandwidthPrio6 |
| 2401 |
|
| 2402 |
|
| 2403 |
|
| 2404 |
<span class="grey">Dubuc, et al. Standards Track [Page 43]</span></pre> |
| 2405 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span> |
| 2406 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2407 |
|
| 2408 |
|
| 2409 |
MIN-ACCESS read-only |
| 2410 |
DESCRIPTION |
| 2411 |
"Write access is not required." |
| 2412 |
|
| 2413 |
OBJECT teLinkDescrMaxLspBandwidthPrio7 |
| 2414 |
MIN-ACCESS read-only |
| 2415 |
DESCRIPTION |
| 2416 |
"Write access is not required." |
| 2417 |
|
| 2418 |
OBJECT teLinkDescrRowStatus |
| 2419 |
SYNTAX RowStatus { active(1) } |
| 2420 |
MIN-ACCESS read-only |
| 2421 |
DESCRIPTION |
| 2422 |
"Write access is not required and active(1) is the |
| 2423 |
only status that needs to be supported." |
| 2424 |
|
| 2425 |
OBJECT teLinkDescrStorageType |
| 2426 |
MIN-ACCESS read-only |
| 2427 |
DESCRIPTION |
| 2428 |
"Write access is not required." |
| 2429 |
|
| 2430 |
-- teLinkSrlgTable |
| 2431 |
|
| 2432 |
OBJECT teLinkSrlgRowStatus |
| 2433 |
SYNTAX RowStatus { active(1) } |
| 2434 |
MIN-ACCESS read-only |
| 2435 |
DESCRIPTION |
| 2436 |
"Write access is not required and active(1) is the |
| 2437 |
only status that needs to be supported." |
| 2438 |
|
| 2439 |
OBJECT teLinkSrlgStorageType |
| 2440 |
MIN-ACCESS read-only |
| 2441 |
DESCRIPTION |
| 2442 |
"Write access is not required." |
| 2443 |
|
| 2444 |
-- teLinkBandwidthTable |
| 2445 |
|
| 2446 |
OBJECT teLinkBandwidthRowStatus |
| 2447 |
SYNTAX RowStatus { active(1) } |
| 2448 |
MIN-ACCESS read-only |
| 2449 |
DESCRIPTION |
| 2450 |
"Write access is not required and active(1) is the |
| 2451 |
only status that needs to be supported." |
| 2452 |
|
| 2453 |
OBJECT teLinkBandwidthStorageType |
| 2454 |
MIN-ACCESS read-only |
| 2455 |
DESCRIPTION |
| 2456 |
"Write access is not required." |
| 2457 |
|
| 2458 |
|
| 2459 |
|
| 2460 |
<span class="grey">Dubuc, et al. Standards Track [Page 44]</span></pre> |
| 2461 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span> |
| 2462 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2463 |
|
| 2464 |
|
| 2465 |
-- componentLinkTable |
| 2466 |
|
| 2467 |
OBJECT componentLinkMaxResBandwidth |
| 2468 |
MIN-ACCESS read-only |
| 2469 |
DESCRIPTION |
| 2470 |
"Write access is not required." |
| 2471 |
|
| 2472 |
OBJECT componentLinkPreferredProtection |
| 2473 |
MIN-ACCESS read-only |
| 2474 |
DESCRIPTION |
| 2475 |
"Write access is not required." |
| 2476 |
|
| 2477 |
OBJECT componentLinkRowStatus |
| 2478 |
SYNTAX RowStatus { active(1) } |
| 2479 |
MIN-ACCESS read-only |
| 2480 |
DESCRIPTION |
| 2481 |
"Write access is not required and active(1) is the |
| 2482 |
only status that needs to be supported." |
| 2483 |
|
| 2484 |
OBJECT componentLinkStorageType |
| 2485 |
MIN-ACCESS read-only |
| 2486 |
DESCRIPTION |
| 2487 |
"Write access is not required." |
| 2488 |
|
| 2489 |
-- componentLinkDescriptorTable |
| 2490 |
|
| 2491 |
OBJECT componentLinkDescrSwitchingCapability |
| 2492 |
MIN-ACCESS read-only |
| 2493 |
DESCRIPTION |
| 2494 |
"Write access is not required." |
| 2495 |
|
| 2496 |
OBJECT componentLinkDescrEncodingType |
| 2497 |
MIN-ACCESS read-only |
| 2498 |
DESCRIPTION |
| 2499 |
"Write access is not required." |
| 2500 |
|
| 2501 |
OBJECT componentLinkDescrMinLspBandwidth |
| 2502 |
MIN-ACCESS read-only |
| 2503 |
DESCRIPTION |
| 2504 |
"Write access is not required." |
| 2505 |
|
| 2506 |
OBJECT componentLinkDescrMaxLspBandwidthPrio0 |
| 2507 |
MIN-ACCESS read-only |
| 2508 |
DESCRIPTION |
| 2509 |
"Write access is not required." |
| 2510 |
|
| 2511 |
OBJECT componentLinkDescrMaxLspBandwidthPrio1 |
| 2512 |
MIN-ACCESS read-only |
| 2513 |
|
| 2514 |
|
| 2515 |
|
| 2516 |
<span class="grey">Dubuc, et al. Standards Track [Page 45]</span></pre> |
| 2517 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span> |
| 2518 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2519 |
|
| 2520 |
|
| 2521 |
DESCRIPTION |
| 2522 |
"Write access is not required." |
| 2523 |
|
| 2524 |
OBJECT componentLinkDescrMaxLspBandwidthPrio2 |
| 2525 |
MIN-ACCESS read-only |
| 2526 |
DESCRIPTION |
| 2527 |
"Write access is not required." |
| 2528 |
|
| 2529 |
OBJECT componentLinkDescrMaxLspBandwidthPrio3 |
| 2530 |
MIN-ACCESS read-only |
| 2531 |
DESCRIPTION |
| 2532 |
"Write access is not required." |
| 2533 |
|
| 2534 |
OBJECT componentLinkDescrMaxLspBandwidthPrio4 |
| 2535 |
MIN-ACCESS read-only |
| 2536 |
DESCRIPTION |
| 2537 |
"Write access is not required." |
| 2538 |
|
| 2539 |
OBJECT componentLinkDescrMaxLspBandwidthPrio5 |
| 2540 |
MIN-ACCESS read-only |
| 2541 |
DESCRIPTION |
| 2542 |
"Write access is not required." |
| 2543 |
|
| 2544 |
OBJECT componentLinkDescrMaxLspBandwidthPrio6 |
| 2545 |
MIN-ACCESS read-only |
| 2546 |
DESCRIPTION |
| 2547 |
"Write access is not required." |
| 2548 |
|
| 2549 |
OBJECT componentLinkDescrMaxLspBandwidthPrio7 |
| 2550 |
MIN-ACCESS read-only |
| 2551 |
DESCRIPTION |
| 2552 |
"Write access is not required." |
| 2553 |
|
| 2554 |
OBJECT componentLinkDescrInterfaceMtu |
| 2555 |
MIN-ACCESS read-only |
| 2556 |
DESCRIPTION |
| 2557 |
"Write access is not required." |
| 2558 |
|
| 2559 |
OBJECT componentLinkDescrIndication |
| 2560 |
MIN-ACCESS read-only |
| 2561 |
DESCRIPTION |
| 2562 |
"Write access is not required." |
| 2563 |
|
| 2564 |
OBJECT componentLinkDescrRowStatus |
| 2565 |
SYNTAX RowStatus { active(1) } |
| 2566 |
MIN-ACCESS read-only |
| 2567 |
DESCRIPTION |
| 2568 |
"Write access is not required and active(1) is the |
| 2569 |
|
| 2570 |
|
| 2571 |
|
| 2572 |
<span class="grey">Dubuc, et al. Standards Track [Page 46]</span></pre> |
| 2573 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span> |
| 2574 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2575 |
|
| 2576 |
|
| 2577 |
only status that needs to be supported." |
| 2578 |
|
| 2579 |
OBJECT componentLinkDescrStorageType |
| 2580 |
MIN-ACCESS read-only |
| 2581 |
DESCRIPTION |
| 2582 |
"Write access is not required." |
| 2583 |
|
| 2584 |
-- componentLinkBandwidthTable |
| 2585 |
|
| 2586 |
OBJECT componentLinkBandwidthRowStatus |
| 2587 |
SYNTAX RowStatus { active(1) } |
| 2588 |
MIN-ACCESS read-only |
| 2589 |
DESCRIPTION |
| 2590 |
"Write access is not required and active(1) is the |
| 2591 |
only status that needs to be supported." |
| 2592 |
|
| 2593 |
OBJECT componentLinkBandwidthStorageType |
| 2594 |
MIN-ACCESS read-only |
| 2595 |
DESCRIPTION |
| 2596 |
"Write access is not required." |
| 2597 |
|
| 2598 |
::= { teLinkCompliances 2 } |
| 2599 |
|
| 2600 |
-- Units of conformance |
| 2601 |
|
| 2602 |
teLinkGroup OBJECT-GROUP |
| 2603 |
OBJECTS { teLinkAddressType, |
| 2604 |
teLinkLocalIpAddr, |
| 2605 |
teLinkRemoteIpAddr, |
| 2606 |
teLinkMetric, |
| 2607 |
teLinkProtectionType, |
| 2608 |
teLinkWorkingPriority, |
| 2609 |
teLinkResourceClass, |
| 2610 |
teLinkIncomingIfId, |
| 2611 |
teLinkOutgoingIfId, |
| 2612 |
teLinkRowStatus, |
| 2613 |
teLinkStorageType, |
| 2614 |
teLinkDescrSwitchingCapability, |
| 2615 |
teLinkDescrEncodingType, |
| 2616 |
teLinkDescrRowStatus, |
| 2617 |
teLinkDescrStorageType, |
| 2618 |
componentLinkPreferredProtection, |
| 2619 |
componentLinkCurrentProtection, |
| 2620 |
componentLinkRowStatus, |
| 2621 |
componentLinkStorageType, |
| 2622 |
componentLinkDescrSwitchingCapability, |
| 2623 |
componentLinkDescrEncodingType, |
| 2624 |
componentLinkDescrRowStatus, |
| 2625 |
|
| 2626 |
|
| 2627 |
|
| 2628 |
<span class="grey">Dubuc, et al. Standards Track [Page 47]</span></pre> |
| 2629 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span> |
| 2630 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2631 |
|
| 2632 |
|
| 2633 |
componentLinkDescrStorageType |
| 2634 |
} |
| 2635 |
|
| 2636 |
STATUS current |
| 2637 |
DESCRIPTION |
| 2638 |
"Collection of objects needed for the management of |
| 2639 |
resources associated with TE links." |
| 2640 |
::= { teLinkGroups 1 } |
| 2641 |
|
| 2642 |
teLinkSrlgGroup OBJECT-GROUP |
| 2643 |
OBJECTS { teLinkSrlgRowStatus, |
| 2644 |
teLinkSrlgStorageType |
| 2645 |
} |
| 2646 |
|
| 2647 |
STATUS current |
| 2648 |
DESCRIPTION |
| 2649 |
"Collection of objects needed for the management of |
| 2650 |
SRLG resources associated with TE links." |
| 2651 |
::= { teLinkGroups 2 } |
| 2652 |
|
| 2653 |
teLinkBandwidthGroup OBJECT-GROUP |
| 2654 |
OBJECTS { teLinkMaximumReservableBandwidth, |
| 2655 |
teLinkDescrMaxLspBandwidthPrio0, |
| 2656 |
teLinkDescrMaxLspBandwidthPrio1, |
| 2657 |
teLinkDescrMaxLspBandwidthPrio2, |
| 2658 |
teLinkDescrMaxLspBandwidthPrio3, |
| 2659 |
teLinkDescrMaxLspBandwidthPrio4, |
| 2660 |
teLinkDescrMaxLspBandwidthPrio5, |
| 2661 |
teLinkDescrMaxLspBandwidthPrio6, |
| 2662 |
teLinkDescrMaxLspBandwidthPrio7, |
| 2663 |
teLinkBandwidthUnreserved, |
| 2664 |
teLinkBandwidthRowStatus, |
| 2665 |
teLinkBandwidthStorageType |
| 2666 |
} |
| 2667 |
|
| 2668 |
STATUS current |
| 2669 |
DESCRIPTION |
| 2670 |
"Collection of objects needed for the management of |
| 2671 |
the bandwidth resources associated with TE links and |
| 2672 |
component links." |
| 2673 |
::= { teLinkGroups 3 } |
| 2674 |
|
| 2675 |
componentLinkBandwidthGroup OBJECT-GROUP |
| 2676 |
OBJECTS { componentLinkMaxResBandwidth, |
| 2677 |
componentLinkDescrMaxLspBandwidthPrio0, |
| 2678 |
componentLinkDescrMaxLspBandwidthPrio1, |
| 2679 |
componentLinkDescrMaxLspBandwidthPrio2, |
| 2680 |
componentLinkDescrMaxLspBandwidthPrio3, |
| 2681 |
|
| 2682 |
|
| 2683 |
|
| 2684 |
<span class="grey">Dubuc, et al. Standards Track [Page 48]</span></pre> |
| 2685 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span> |
| 2686 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2687 |
|
| 2688 |
|
| 2689 |
componentLinkDescrMaxLspBandwidthPrio4, |
| 2690 |
componentLinkDescrMaxLspBandwidthPrio5, |
| 2691 |
componentLinkDescrMaxLspBandwidthPrio6, |
| 2692 |
componentLinkDescrMaxLspBandwidthPrio7, |
| 2693 |
componentLinkBandwidthUnreserved, |
| 2694 |
componentLinkBandwidthRowStatus, |
| 2695 |
componentLinkBandwidthStorageType |
| 2696 |
} |
| 2697 |
|
| 2698 |
STATUS current |
| 2699 |
DESCRIPTION |
| 2700 |
"Collection of objects needed for the management of the |
| 2701 |
bandwidth parameters associated with component links." |
| 2702 |
::= { teLinkGroups 4 } |
| 2703 |
|
| 2704 |
teLinkPscGroup OBJECT-GROUP |
| 2705 |
OBJECTS { teLinkDescrMinLspBandwidth, |
| 2706 |
teLinkDescrInterfaceMtu, |
| 2707 |
componentLinkDescrMinLspBandwidth, |
| 2708 |
componentLinkDescrInterfaceMtu |
| 2709 |
} |
| 2710 |
|
| 2711 |
STATUS current |
| 2712 |
DESCRIPTION |
| 2713 |
"Collection of objects needed for devices that are |
| 2714 |
packet switch capable." |
| 2715 |
::= { teLinkGroups 5 } |
| 2716 |
|
| 2717 |
teLinkTdmGroup OBJECT-GROUP |
| 2718 |
OBJECTS { teLinkDescrMinLspBandwidth, |
| 2719 |
teLinkDescrIndication, |
| 2720 |
componentLinkDescrMinLspBandwidth, |
| 2721 |
componentLinkDescrIndication |
| 2722 |
} |
| 2723 |
|
| 2724 |
STATUS current |
| 2725 |
DESCRIPTION |
| 2726 |
"Collection of objects needed for devices that are |
| 2727 |
TDM switching capable." |
| 2728 |
::= { teLinkGroups 6 } |
| 2729 |
|
| 2730 |
-- End of TE-LINK-STD-MIB |
| 2731 |
END |
| 2732 |
|
| 2733 |
|
| 2734 |
|
| 2735 |
|
| 2736 |
|
| 2737 |
|
| 2738 |
|
| 2739 |
|
| 2740 |
<span class="grey">Dubuc, et al. Standards Track [Page 49]</span></pre> |
| 2741 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span> |
| 2742 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2743 |
|
| 2744 |
|
| 2745 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span> |
| 2746 |
|
| 2747 |
There are a number of management objects defined in this MIB module |
| 2748 |
with a MAX-ACCESS clause of read-write and/or read-create. Such |
| 2749 |
objects may be considered sensitive or vulnerable in some network |
| 2750 |
environments. The support for SET operations in a non-secure |
| 2751 |
environment without proper protection can have a negative effect on |
| 2752 |
network operations. These are the tables and objects and their |
| 2753 |
sensitivity/vulnerability: |
| 2754 |
|
| 2755 |
- All the tables in this MIB module have routing information in |
| 2756 |
them, so they all have the same security attributes. Unauthorized |
| 2757 |
changes to attributes of these tables can disrupt resource |
| 2758 |
allocation in the network. |
| 2759 |
|
| 2760 |
Some of the readable objects in this MIB module (i.e., objects with a |
| 2761 |
MAX-ACCESS other than not-accessible) may be considered sensitive or |
| 2762 |
vulnerable in some network environments. It is thus important to |
| 2763 |
control even GET and/or NOTIFY access to these objects and possibly |
| 2764 |
to even encrypt the values of these objects when sending them over |
| 2765 |
the network via SNMP. These are the tables and objects and their |
| 2766 |
sensitivity/vulnerability: |
| 2767 |
|
| 2768 |
- IP address entries in the teLinkTable (teLinkLocalIpAddr and |
| 2769 |
teLinkRemoteIpAddr) may reveal the internals of a network provider |
| 2770 |
IP address space. |
| 2771 |
|
| 2772 |
SNMP versions prior to SNMPv3 did not include adequate security. |
| 2773 |
Even if the network itself is secure (for example by using IPSec), |
| 2774 |
even then, there is no control as to who on the secure network is |
| 2775 |
allowed to access and GET/SET (read/change/create/delete) the objects |
| 2776 |
in this MIB module. |
| 2777 |
|
| 2778 |
It is RECOMMENDED that implementers consider the security features as |
| 2779 |
provided by the SNMPv3 framework (see <a href="./rfc3410#section-8">[RFC3410], section 8</a>), |
| 2780 |
including full support for the SNMPv3 cryptographic mechanisms (for |
| 2781 |
authentication and privacy). |
| 2782 |
|
| 2783 |
Further, deployment of SNMP versions prior to SNMPv3 is NOT |
| 2784 |
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to |
| 2785 |
enable cryptographic security. It is then a customer/operator |
| 2786 |
responsibility to ensure that the SNMP entity giving access to an |
| 2787 |
instance of this MIB module is properly configured to give access to |
| 2788 |
the objects only to those principals (users) that have legitimate |
| 2789 |
rights to indeed GET or SET (change/create/delete) them. |
| 2790 |
|
| 2791 |
|
| 2792 |
|
| 2793 |
|
| 2794 |
|
| 2795 |
|
| 2796 |
<span class="grey">Dubuc, et al. Standards Track [Page 50]</span></pre> |
| 2797 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span> |
| 2798 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2799 |
|
| 2800 |
|
| 2801 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Contributors</span> |
| 2802 |
|
| 2803 |
Sudheer Dharanikota |
| 2804 |
EMail: [email protected] |
| 2805 |
|
| 2806 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Acknowledgements</span> |
| 2807 |
|
| 2808 |
The authors would like to acknowledge the contribution of Dmitry |
| 2809 |
Ryumkin. |
| 2810 |
|
| 2811 |
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. IANA Considerations</span> |
| 2812 |
|
| 2813 |
The following "IANA Considerations" subsection requests IANA for a |
| 2814 |
new assignment. New assignments can only be made via Standards |
| 2815 |
Action as specified in [<a href="./rfc2434" title="">RFC2434</a>]. |
| 2816 |
|
| 2817 |
<span class="h3"><a class="selflink" id="section-13.1" href="#section-13.1">13.1</a>. IANA Considerations for the TE-LINK-STD-MIB</span> |
| 2818 |
|
| 2819 |
The TE-LINK-STD-MIB should be rooted under the transmission subtree. |
| 2820 |
The IANA has assigned { transmission 200 } to the TE-LINK-STD-MIB |
| 2821 |
module specified in this document. |
| 2822 |
|
| 2823 |
<span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. References</span> |
| 2824 |
|
| 2825 |
<span class="h3"><a class="selflink" id="section-14.1" href="#section-14.1">14.1</a>. Normative References</span> |
| 2826 |
|
| 2827 |
[<a id="ref-IANAifType">IANAifType</a>] "IANAifType MIB Module", |
| 2828 |
<a href="http://www.iana.org/assignments/ianaiftype-mib">http://www.iana.org/assignments/ianaiftype-mib</a>. |
| 2829 |
|
| 2830 |
[<a id="ref-IEEE">IEEE</a>] IEEE, "IEEE Standard for Binary Floating-Point |
| 2831 |
Arithmetic", Standard 754-1985, 1985 (ISBN 1-5593-7653- |
| 2832 |
8). |
| 2833 |
|
| 2834 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 2835 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 2836 |
|
| 2837 |
[<a id="ref-RFC2434">RFC2434</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an |
| 2838 |
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC 2434</a>, |
| 2839 |
October 1998. |
| 2840 |
|
| 2841 |
[<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Perkins, D. and J. Schoenwaelder, |
| 2842 |
"Structure of Management Information Version 2 (SMIv2)", |
| 2843 |
STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999. |
| 2844 |
|
| 2845 |
[<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Perkins, D. and J. Schoenwaelder, |
| 2846 |
"Textual Conventions for SMIv2", STD 58, <a href="./rfc2579">RFC 2579</a>, April |
| 2847 |
1999. |
| 2848 |
|
| 2849 |
|
| 2850 |
|
| 2851 |
|
| 2852 |
<span class="grey">Dubuc, et al. Standards Track [Page 51]</span></pre> |
| 2853 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span> |
| 2854 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2855 |
|
| 2856 |
|
| 2857 |
[<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Perkins, D. and J. Schoenwaelder, |
| 2858 |
"Conformance Statements for SMIv2", STD 58, <a href="./rfc2580">RFC 2580</a>, |
| 2859 |
April 1999. |
| 2860 |
|
| 2861 |
[<a id="ref-RFC2863">RFC2863</a>] McCloghrie, K. and F. Kastenholz, "The Interfaces Group |
| 2862 |
MIB", <a href="./rfc2863">RFC 2863</a>, June 2000. |
| 2863 |
|
| 2864 |
[<a id="ref-RFC3471">RFC3471</a>] Berger, L., "Generalized Multi-Protocol Label Switching |
| 2865 |
(GMPLS) Signaling Functional Description", <a href="./rfc3471">RFC 3471</a>, |
| 2866 |
January 2003. |
| 2867 |
|
| 2868 |
[<a id="ref-RFC3630">RFC3630</a>] Katz, D., Kompella, K. and D. Yeung, "Traffic |
| 2869 |
Engineering (TE) Extensions to OSPF Version 2", <a href="./rfc3630">RFC</a> |
| 2870 |
<a href="./rfc3630">3630</a>, September 2003. |
| 2871 |
|
| 2872 |
[<a id="ref-RFC4201">RFC4201</a>] Kompella, K., Rekhter, Y. and L. Berger, "Link Bundling |
| 2873 |
in MPLS Traffic Engineering (TE)", <a href="./rfc4201">RFC 4201</a>, October |
| 2874 |
2005. |
| 2875 |
|
| 2876 |
[<a id="ref-RFC4202">RFC4202</a>] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing |
| 2877 |
Extensions in Support of Generalized Multi-Protocol |
| 2878 |
Label Switching (GMPLS)", <a href="./rfc4202">RFC 4202</a>, October 2005. |
| 2879 |
|
| 2880 |
[<a id="ref-RFC4203">RFC4203</a>] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions |
| 2881 |
in Support of Generalized Multi-Protocol Label Switching |
| 2882 |
(GMPLS)", <a href="./rfc4203">RFC 4203</a>, October 2005. |
| 2883 |
|
| 2884 |
[<a id="ref-RFC4206">RFC4206</a>] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP) |
| 2885 |
Hierarchy with Generalized Multi-Protocol Label |
| 2886 |
Switching (GMPLS) Traffic Engineering (TE)", <a href="./rfc4206">RFC 4206</a>, |
| 2887 |
October 2005. |
| 2888 |
|
| 2889 |
[<a id="ref-RFC4204">RFC4204</a>] Lang, J., Ed., "Link Management Protocol (LMP)", <a href="./rfc4204">RFC</a> |
| 2890 |
<a href="./rfc4204">4204</a>, October 2005. |
| 2891 |
|
| 2892 |
<span class="h3"><a class="selflink" id="section-14.2" href="#section-14.2">14.2</a>. Informative References</span> |
| 2893 |
|
| 2894 |
[<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D., and B. Stewart, |
| 2895 |
"Introduction and Applicability Statements for |
| 2896 |
Internet-Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, |
| 2897 |
December 2002. |
| 2898 |
|
| 2899 |
[<a id="ref-RFC3945">RFC3945</a>] Mannie, E., "Generalized Multi-Protocol Label Switching |
| 2900 |
(GMPLS) Architecture", <a href="./rfc3945">RFC 3945</a>, October 2004. |
| 2901 |
|
| 2902 |
|
| 2903 |
|
| 2904 |
|
| 2905 |
|
| 2906 |
|
| 2907 |
|
| 2908 |
<span class="grey">Dubuc, et al. Standards Track [Page 52]</span></pre> |
| 2909 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span> |
| 2910 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2911 |
|
| 2912 |
|
| 2913 |
Authors' Addresses |
| 2914 |
|
| 2915 |
Martin Dubuc |
| 2916 |
|
| 2917 |
EMail: [email protected] |
| 2918 |
|
| 2919 |
|
| 2920 |
Thomas D. Nadeau |
| 2921 |
Cisco Systems |
| 2922 |
1414 Massachusetts Ave. |
| 2923 |
Boxborough, MA 01719 |
| 2924 |
|
| 2925 |
Phone: +1-978-244-3051 |
| 2926 |
EMail: [email protected] |
| 2927 |
|
| 2928 |
|
| 2929 |
Jonathan P. Lang |
| 2930 |
Sonos, Inc. |
| 2931 |
223 E. De La Guerra St. |
| 2932 |
Santa Barbara, CA 93101 |
| 2933 |
|
| 2934 |
EMail: [email protected] |
| 2935 |
|
| 2936 |
|
| 2937 |
|
| 2938 |
|
| 2939 |
|
| 2940 |
|
| 2941 |
|
| 2942 |
|
| 2943 |
|
| 2944 |
|
| 2945 |
|
| 2946 |
|
| 2947 |
|
| 2948 |
|
| 2949 |
|
| 2950 |
|
| 2951 |
|
| 2952 |
|
| 2953 |
|
| 2954 |
|
| 2955 |
|
| 2956 |
|
| 2957 |
|
| 2958 |
|
| 2959 |
|
| 2960 |
|
| 2961 |
|
| 2962 |
|
| 2963 |
|
| 2964 |
<span class="grey">Dubuc, et al. Standards Track [Page 53]</span></pre> |
| 2965 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span> |
| 2966 |
<span class="grey"><a href="./rfc4220">RFC 4220</a> MPLS TE Link MIB Module November 2005</span> |
| 2967 |
|
| 2968 |
|
| 2969 |
Full Copyright Statement |
| 2970 |
|
| 2971 |
Copyright (C) The Internet Society (2005). |
| 2972 |
|
| 2973 |
This document is subject to the rights, licenses and restrictions |
| 2974 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 2975 |
retain all their rights. |
| 2976 |
|
| 2977 |
This document and the information contained herein are provided on an |
| 2978 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 2979 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET |
| 2980 |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, |
| 2981 |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE |
| 2982 |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 2983 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 2984 |
|
| 2985 |
Intellectual Property |
| 2986 |
|
| 2987 |
The IETF takes no position regarding the validity or scope of any |
| 2988 |
Intellectual Property Rights or other rights that might be claimed to |
| 2989 |
pertain to the implementation or use of the technology described in |
| 2990 |
this document or the extent to which any license under such rights |
| 2991 |
might or might not be available; nor does it represent that it has |
| 2992 |
made any independent effort to identify any such rights. Information |
| 2993 |
on the procedures with respect to rights in RFC documents can be |
| 2994 |
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>. |
| 2995 |
|
| 2996 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 2997 |
assurances of licenses to be made available, or the result of an |
| 2998 |
attempt made to obtain a general license or permission for the use of |
| 2999 |
such proprietary rights by implementers or users of this |
| 3000 |
specification can be obtained from the IETF on-line IPR repository at |
| 3001 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 3002 |
|
| 3003 |
The IETF invites any interested party to bring to its attention any |
| 3004 |
copyrights, patents or patent applications, or other proprietary |
| 3005 |
rights that may cover technology that may be required to implement |
| 3006 |
this standard. Please address the information to the IETF at ietf- |
| 3007 |
[email protected]. |
| 3008 |
|
| 3009 |
Acknowledgement |
| 3010 |
|
| 3011 |
Funding for the RFC Editor function is currently provided by the |
| 3012 |
Internet Society. |
| 3013 |
|
| 3014 |
|
| 3015 |
|
| 3016 |
|
| 3017 |
|
| 3018 |
|
| 3019 |
|
| 3020 |
Dubuc, et al. Standards Track [Page 54] |
| 3021 |
</pre> |