idnits 2.17.1 draft-ietf-l2tpext-l2tpmib-base-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2777. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2750. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2757. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2763. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([L2TP-MIB]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 2006) is 6461 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'L2TP-MIB' is mentioned on line 2619, but not defined == Missing Reference: 'L2TP-BASE' is mentioned on line 2616, but not defined == Missing Reference: 'PWE3-PW-MIB' is mentioned on line 2623, but not defined == Missing Reference: 'RFC2863' is mentioned on line 2627, but not defined == Unused Reference: 'RFC1155' is defined on line 2632, but no explicit reference was found in the text == Unused Reference: 'RFC1157' is defined on line 2636, but no explicit reference was found in the text == Unused Reference: 'RFC1212' is defined on line 2640, but no explicit reference was found in the text == Unused Reference: 'RFC1215' is defined on line 2645, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 2648, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 2652, but no explicit reference was found in the text == Unused Reference: 'RFC1906' is defined on line 2656, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 2663, but no explicit reference was found in the text == Unused Reference: 'RFC2571' is defined on line 2667, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 2671, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 2676, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 2679, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 2683, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 2687, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 2694, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 2698, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 1905 (Obsoleted by RFC 3416) -- Obsolete informational reference (is this intentional?): RFC 1906 (Obsoleted by RFC 3417) -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) -- Obsolete informational reference (is this intentional?): RFC 2571 (Obsoleted by RFC 3411) -- Obsolete informational reference (is this intentional?): RFC 2572 (Obsoleted by RFC 3412) -- Obsolete informational reference (is this intentional?): RFC 2573 (Obsoleted by RFC 3413) -- Obsolete informational reference (is this intentional?): RFC 2574 (Obsoleted by RFC 3414) -- Obsolete informational reference (is this intentional?): RFC 2575 (Obsoleted by RFC 3415) -- Obsolete informational reference (is this intentional?): RFC 2667 (Obsoleted by RFC 4087) Summary: 4 errors (**), 0 flaws (~~), 21 warnings (==), 16 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Thomas D. Nadeau (Ed.) 2 Internet-Draft A S Kiran Koushik (Ed.) 3 Category: Standards Track cisco Systems, Inc. 4 6 August 2006 8 Layer Two Tunneling Protocol (Version 3) "L2TPv3" 9 Management Information Base 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as 21 Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other documents 25 at any time. It is inappropriate to use Internet-Drafts as 26 reference material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Abstract 36 This document describes a portion of the Management Information Base 37 (MIB) to manage the Layer Two Tunneling Protocol, Version 3 (L2TPv3). 39 Acknowledgments 41 The original L2TP MIB, [L2TP-MIB], was authored by Evan Caves, Pat 42 Calhoun, and Ross Wheeler. 44 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 46 Contents 48 Status of this Memo.......................................... 1 50 1. Introduction............................................. 2 51 1.1 Changes from the L2TPv2 MIB.......................... 2 52 1.2 Specification of Requirements........................ 3 53 1.3 Terminology.......................................... 3 55 2. The SNMP Management Framework............................ 3 57 3. Overview................................................. 4 58 3.1 Organization of the L2TP MIB......................... 5 59 3.2 Relationship to the Interface MIB.................... 5 60 3.2.1 Layering Model................................ 5 61 3.2.2 Interface MIB Objects......................... 6 62 3.2.2.1 L2TP Tunnel Interfaces............... 7 63 3.3 Relationship to other MIBs........................... 10 64 3.3.1 Relationship to the IP Tunnel MIB............. 10 65 3.4 L2TP Tunnel Creation................................. 10 66 3.5 L2TP Session Mapping................................. 10 68 4. L2TPv3 MIB Object Definitions............................ 11 70 5. Security Considerations.................................. 51 72 6. IANA Considerations....................................... 52 74 7. References................................................ 52 75 7.1 Normative Referneces.................................. 52 76 7.2. Informative References............................... 52 78 8. Editors' Addresses....................................... 54 80 9. Intellectual Property Considerations...................... 54 82 10. Full Copyright Statement.................................. 55 84 1. Introduction 86 The Managed Information Base (MIB) for the Layer Two Tunneling 87 Protocol, Version 3 (L2TPv3) describes a model for managing the 88 common attributes of L2TP control connections and sessions. L2TP 89 provides a dynamic tunneling mechanism for multiple Layer 2 (L2) 90 circuits across a packet-oriented data network. This MIB supports 91 the base L2TP mechanism as specified in [L2TP-BASE]. 93 1.1 Changes from the L2TPv2 MIB 95 Most of the MIB objects defined in this document are carried over 96 from [L2TP-MIB]. Changes include the following: 98 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 100 o Separation of all payload-specific (namely PPP) and 101 transport-specific (e.g. IP/UDP) objects. Payload- and transport- 102 specific constructs are defined in companion documents. 104 o Transition from a 16-bit Session ID and Tunnel ID to a 105 32-bit Session ID and Control Connection ID, respectively. 107 The MIB defined in [L2TP-MIB] will be referred to as the "L2TPv2 108 MIB", while the MIB defined in this document will be referred to as 109 the "L2TPv3 MIB" or, more simply, as the "L2TP MIB" when the 110 distinction is clear. Note that the L2TPv3 MIB supports both L2TPv2 111 and L2TPv3 implementations. 113 1.2 Specification of Requirements 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 117 document are to be interpreted as described in [RFC2119]. 119 1.3 Terminology 121 See also the "Terminology" section in [L2TP-BASE]. 123 2. The SNMP Management Framework 125 The SNMP Management Framework presently consists of five major 126 components: 128 o An overall architecture, described in RFC 2571. 130 o Mechanisms for describing and naming objects and events for the 131 purpose of management. The first version of this Structure of 132 Management Information (SMI) is called SMIv1 and is described in 133 STD 16 / RFC 1155, STD 16 / RFC 1212, and RFC 1215. The second 134 version, called SMIv2, is described in STD 58 / RFC 2578, STD 58 / 135 RFC 2579, and STD 58 / RFC 2580. 137 o Message protocols for transferring management information. The 138 first version of the SNMP message protocol is called SNMPv1 and is 139 described in STD 15 / RFC 1157. A second version of the SNMP 140 message protocol, which is not an Internet standards track 141 protocol, is called SNMPv2c and is described in RFC 1901 and RFC 142 1906. The third version of the message protocol is called SNMPv3 143 and is described in RFC 1906, RFC 2572, and RFC 2574. 145 o Protocol operations for accessing management information. The 146 first set of protocol operations and associated PDU formats is 147 described in STD 15 / RFC 1157. A second set of protocol 148 operations and associated PDU formats is described in RFC 1905. 150 o A set of fundamental applications described in RFC 2573 and the 151 view-based access control mechanism described in RFC 2575. 153 A more detailed introduction to the current SNMP Management Framework 154 can be found in RFC 2570. 156 Managed objects are accessed via a virtual information store, termed 157 the "Management Information Base" (MIB). Objects in the MIB are 158 defined using the mechanisms defined in the SMI. 160 This memo specifies a MIB module that is compliant to the SMIv2. A 161 MIB conforming to the SMIv1 can be produced through the appropriate 162 translations. The resulting translated MIB must be semantically 163 equivalent, except cases in which objects or events are omitted 164 because no translation is possible (e.g. use of Counter64). Some 165 machine-readable information in SMIv2 will be converted into textual 166 descriptions in SMIv1 during the translation process. However, this 167 loss of machine-readable information is not considered to change the 168 semantics of the MIB. 170 3. Overview 172 The L2TP MIB defines the attributes that are common across all L2TP 173 control connections and sessions, supporting at least L2TPv2 and 174 L2TPv3. Other companion MIBs convey more specific characteristics 175 about the tunneled link, such as the transport (e.g. IP, MPLS, ATM, 176 etc.) or the payload (e.g. PPP, Ethernet, Frame Relay, etc.). The 177 following reference model is suggested, but not required, as a 178 framework in which the L2TP MIB may reside: 180 Figure 3.0: Sample MIB Layering with the L2TP MIB 182 Pseudowire Layer 183 | 184 --------------------------------|------------------------------------ 185 +--------+ 186 Tunnel Layer _ |L2TP MIB| _ 187 ________/ +--------+ \________ 188 / | \ 189 +------------------+ | +-----------------------+ 190 |transport-specific| | |payload-specific | 191 |session MIBs | | |control connection MIBs| 192 +------------------+ | +-----------------------+ 193 --------------------------------|------------------------------------ 194 | 195 Tunnel Transport Layer 197 In the diagram above, the Tunnel Layer comprises the MIBs that are 198 specific to the tunneling protocol. For L2TP, this layer includes 199 the L2TP MIB plus any payload-specific control connection MIBs or 200 transport-specific session MIBs. The Pseudowire Layer contains MIBs 201 that characterize the L2 payloads being forwarded by the tunneling 202 protocol (e.g. the PWE3 Pseudowire MIB, see [PWE3-PW-MIB]). The 203 Tunnel Transport Layer consists of MIBs that describe the transport- 204 level characteristics of a connection between two tunnel endpoints 205 (e.g. the IP Tunnel MIB, see RFC 2667). 207 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 209 The interaction of the L2TP MIB with other MIBs in different layers 210 may require intermediate MIBs to map one MIB instance to another. 212 These intermediate MIBs are defined in companion documents. 214 3.1 Organization of the L2TP MIB 216 This MIB consists of the following seven groups: 218 l2tpConfigGroup 219 l2tpStatsGroup 220 These two groups provide information on the configuration, states, 221 and statistics of the L2TP stack, its control connections, and its 222 sessions. These groups are mandatory for implementors of this 223 MIB. 225 l2tpCtrlDomainGroup 226 This optional group of objects provides configuration, states, and 227 statistical information for L2TP control domains. An L2TP control 228 domain is defined as a collection of L2TP LCCEs typically 229 belonging to a common administrative domain or geographic 230 location. 232 l2tpMappingGroup 233 This optional group contains mapping tables to assist management 234 applications to map between protocol identifiers and table 235 indices. 237 l2tpSecurityGroup 238 This optional group is for SNMP agents that support both 239 authentication and privacy of SNMP messages for the management of 240 L2TP keys. 242 l2tpTrapGroup 243 This group contains the notifications that could be generated by 244 an L2TP stack. 246 l2tpHCPacketGroup 247 This group is optional for L2TP implementations that could 248 potentially overflow the L2TP control domain tables 32-bit 249 statistics counters in less than an hour. 251 3.2 Relationship to the Interface MIB 253 This section clarifies the relationship of this MIB to the Interfaces 254 MIB [RFC2863]. Several areas of correlation are addressed in the 255 following subsections. The implementor is referred to the Interfaces 256 MIB document in order to understand the general intent of these 257 areas. 259 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 261 3.2.1 Layering Model 263 This MIB contains several tables which are extensions to the IP 264 Tunnel MIB described in [RFC2667] which itself defines extensions to 265 the Interface MIB [RFC2863]. An L2TP tunnel is represented as a 266 separate identifiable logical interface sub-layer. The tunnel stack 267 layering model is described in [RFC2667]. 269 In addition to that described in [RFC2667] an L2TP tunnel will not be 270 at the top of the ifStack on a L2TP device that is acting as a L2TP 271 Network Server (LNS). In this case PPP interfaces will be layered on 272 top of the tunnel interface. 274 In the example diagram below, the interface layering is shown as it 275 might appear at the LNS. 277 +--------------------------------------------+ 278 | Network Layer Protocol | 279 +-+-----------+-------------+--------+-------+ 280 | | | | 281 | +-+--+ | | 282 | |MPPP| | | <=== PPP Multilink I/F 283 | ++--++ | | 284 | | | | | 285 | +--+ +--+ | | 286 | | | | | 287 | +-+-+ +-+-+ +-+-+ +-+-+ 288 | |PPP| |PPP| |PPP| |PPP| <=== PPP I/F 289 | +-+-+ +-+-+ +-+-+ +-+-+ 290 | | | | | 291 | +----+--------+--------+--------+----+ 292 | | L2TP Tunnel I/F | 293 | +------------------+-----------------+ 294 | | 295 +-+---------------------+------+ 296 | Ethernet | 297 +------------------------------+ 299 The ifStackTable is used to describe the layering of the interface 300 sub-layers. For the example given above the ifTable and ifStackTable 301 may appear as follows: 303 ifIndex ifType Tunnel MIB tables Description 305 1 ethernetCsmacd(6) Ethernet interface 306 2 tunnel(131) tunnelIfTable Tunnel interface 307 l2tpTunnelConfigTable 308 l2tpTunnelStatsTable 309 3 ppp(23) PPP interface #1 310 4 ppp(23) PPP interface #2 311 5 ppp(23) PPP interface #3 313 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 315 6 ppp(23) PPP interface #4 316 7 mlppp(108) MLPPP interface 318 The corresponding ifStack table entries would then be: 320 ifStackTable Entries 322 HigherLayer LowerLayer 323 0 5 324 0 6 325 0 7 326 1 0 327 2 1 328 3 2 329 4 2 330 5 2 331 6 2 332 7 3 333 7 4 335 L2TP Access Concentrator (LAC) tunnel interfaces on the other hand 336 appear at the top of the interface layering stack. In this case the 337 layering model is as described in [RFC2667]. 339 However in order to support the tunneling of packets received from 340 interfaces carrying framed PPP packets on the LAC to the LNS (and the 341 propagation of decapsulated PPP packets to that interface) additional 342 configuration is required. This is further described in section 3.4. 344 3.2.2 Interface MIB Objects 346 Except where noted in the tables below, all objects MUST be supported 347 from the ifGeneralInformationGroup and one of the following three 348 groups: 350 o ifPacketGroup OR 351 o ifHCPacketGroup OR 352 o ifVHCPacketGroup 354 depending on the particular implementation. 356 The following tables describe how objects from the 357 ifGeneralInformationGroup and ifPacketGroup (similar support should 358 be provided for the high and very high capacity packet groups) are to 359 be interpreted and supported for L2TP tunnel interfaces. 361 3.2.2.1 L2TP Tunnel Interfaces 362 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 364 All Interface MIB objects not listed in the above groups for L2TP 365 tunnel interfaces MUST be supported as described in [RFC2863]. 367 Interface MIB Object Support Description 368 ==================== ======================================== 369 ifTable.ifDescr Refer to the Interface MIB. 371 ifTable.ifType tunnel(131). 373 ifTable.ifMtu Dependent on the tunnel transport layer. 374 For UDP/IP transports the MTU should 375 be 65467 (65535-60(IP)-8(UDP)). 377 ifTable.ifSpeed Return zero. 379 ifTable.ifPhyAddress The assigned tunnel identifier. 381 ifTable.ifAdminStatus Setting ifAdminStatus to 'up' injects a 382 'Local Open' request into the tunnel FSM. 383 Setting ifAdminStatus to 'down' injects 384 a 'Tunnel Close' event into the tunnel 385 FSM. Setting ifAdminStatus to 'testing' 386 is not currently defined but could be 387 used to test tunnel connectivity. 389 ifTable.ifOperStatus The ifOperStatus values are to be 390 interpreted as follows: 391 'up' - tunnel is established. 392 'down' - administratively down 393 or peer unreachable. 394 'testing' - in some test mode. 395 'unknown' - status cannot be 396 determined for some 397 reason. 398 'dormant' - operational but 399 waiting for local or 400 remote trigger to bring 401 up the tunnel. 402 'notPresent' - configuration missing. 403 'lowerLayerDown' - down due to state of 404 lower-layer 405 interface(s). 407 ifTable.ifInOctets The total number of octets received on the 408 tunnel including control and payload 409 octets. 411 ifTable.ifInUcastPkts The total number of packets received on 413 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 415 the tunnel including control and payload 416 packets. 418 ifTable.ifInDiscards The total number of received packets that 419 were discarded on both control and payload 420 channels. 422 ifTable.ifInErrors The total number of packets received in 423 error including control and payload 424 packets. 426 ifTable.ifInUnknownProtos 427 Return zero. 429 ifTable.ifOutOctets The total number of octets transmitted 430 from the tunnel including control and 431 payload octets. 433 ifTable.ifOutUcastPkts The total number of packets transmitted 434 from the tunnel including control and 435 payload packets. 437 ifTable.ifOutDiscards The total number of discarded packets that 438 were requested to be transmitted including 439 control and payload packets. 441 ifTable.ifOutErrors The total number of packets that were 442 requested to be transmitted that were in 443 error including control and payload 444 packets. 446 ifXTable.ifName Refer to the Interface MIB. 448 ifXTable.ifInMulticastPkts 449 Return zero. 451 ifXTable.ifInBroadcastPkts 452 Return zero. 454 ifXTable.ifOutMulticastPkts 455 Return zero. 457 ifXTable.ifOutBroadcastPkts 458 Return zero. 460 ifXTable.ifOutBroadcastPkts 461 Return zero. 463 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 465 ifXTable.ifLinkUpDownTrapEnable 466 Default set to enabled(1). 468 ifXTable.ifHighSpeed Return zero. 470 ifXTable.ifPromiscuousMode 471 Set to false(2). 473 ifXTable.ifConnectorPresent 474 Set to false(2). 476 3.3 Relationship to other MIBs 478 3.3.1 Relationship to the IP Tunnel MIB 480 The IP Tunnel MIB [RFC2667] describes tunnel interfaces that have an 481 ifType of tunnel(131). The IP Tunnel MIB is considered to contain a 482 collection of objects common to all IP tunneling protocols, including 483 L2TP. In addition to the IP Tunnel MIB, tunnel encapsulation 484 specific MIBs (like this MIB) extend the IP Tunnel MIB to further 485 describe encapsulation specific information. Implementation of the 486 IP Tunnel MIB is required for L2TP tunnels over IP. 488 3.4 L2TP Tunnel Creation 490 Tunnel creation is detailed for tunnels over IP in the IP Tunnel MIB. 491 The creation of a tunnelIfEntry in [RFC2667] when the encapsulation 492 method is "l2tp" will have the side effect of creating entries in the 493 l2tpTunnelConfigTable, l2tpTunnelStatsTable and the 494 l2tpUdpStatsTable's. 496 The creation of L2TP tunnel interfaces over transports other than IP 497 is expected to be defined in the MIB definition for that specific 498 L2TP tunnel transport. 500 3.5 L2TP Session Mapping 502 The l2tpSessionMapTable table allows management applications to 503 determine which session within a tunnel a particular interface 504 (either a PPP or DS0 interface) is mapped to. On the LAC it also 505 provides a management application the ability to map a particular 506 physical or virtual interface terminating a PPP link to a particular 507 L2TP tunnel. This is required since the interface stacking as 508 performed (and instrumented by the ifStackTable) on the LNS cannot be 509 applied at the LAC. 511 The following diagram illustrates the conceptual binding that occurs. 513 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 515 +---------------------------------------+ 516 | L2TP Session Map Database | 517 +----------+-----------------+----------+ 518 | | 519 +---+---+ +-----+------+ 520 | ds0 | | Tunnel I/F | 521 +---+---+ +-----+------+ 522 | | 523 +---+---+ +-----+------+ 524 | ds1 | | Ethernet | 525 +-------+ +------------+ 527 The stacking of the individual interface stacks would be described by 528 the ifStackTable. 530 4. L2TPv3 MIB Object Definitions 532 L2TPv3-MIB DEFINITIONS ::= BEGIN 534 IMPORTS 535 MODULE-IDENTITY, 536 NOTIFICATION-TYPE, 537 OBJECT-TYPE, 538 Counter32, 539 Counter64, 540 Gauge32, 541 Integer32, 542 Unsigned32 543 FROM SNMPv2-SMI 545 TEXTUAL-CONVENTION, 546 DisplayString, 547 RowStatus, 548 TruthValue 549 FROM SNMPv2-TC 551 SnmpAdminString 552 FROM SNMP-FRAMEWORK-MIB 554 MODULE-COMPLIANCE, 555 NOTIFICATION-GROUP, 556 OBJECT-GROUP 557 FROM SNMPv2-CONF 559 InterfaceIndex 560 FROM IF-MIB; 562 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 564 l2tpv3 MODULE-IDENTITY 565 LAST-UPDATED "200608230000Z" -- 23 August 2006 566 ORGANIZATION "IETF L2TP Working Group" 567 CONTACT-INFO 568 "Layer Two Tunneling Protocol Extensions WG 569 Working Group Area: Internet 570 Working Group Name: l2tpext 571 General Discussion: l2tp@l2tp.net" 573 DESCRIPTION 574 "The MIB module that describes managed objects of general 575 use by the Layer Two Tunneling Protocol, Version 3 576 (L2TPv3)." 578 -- 579 -- Revision log 580 -- 581 REVISION "200608230000Z" -- 23 August 2006 582 DESCRIPTION 583 "Editorial changes." 584 REVISION "200211030000Z" -- 3 November 2002 585 DESCRIPTION 586 "First revision." 587 ::= { transmission XXX } -- To be assigned by IANA 589 -- 590 -- Textual Conventions 591 -- 593 L2tpv3MilliSeconds ::= TEXTUAL-CONVENTION 594 DISPLAY-HINT "d-3" 595 STATUS current 596 DESCRIPTION 597 "A period of time, measured in units of .001 seconds. 598 When used in conjunction with the DISPLAY-HINT, shows 599 seconds and fractions of a second with a resolution of 600 .001 of a second." 601 SYNTAX Integer32 (0..2147483646) 603 L2tpv3TransportType ::= TEXTUAL-CONVENTION 604 DISPLAY-HINT "" 605 STATUS current 606 DESCRIPTION 607 "Supported L2TP transport types. Different transports 608 may define MIB extensions to the L2TP control connection 609 table to fully describe the transport layer. Objects of 610 this type may be used to determine which MIB extensions 611 to reference." 613 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 615 SYNTAX INTEGER { 616 other(1), 617 none(2), 618 ipv4(3), 619 udpIpv4(4), 620 ipv6(5), 621 udpIpv6(6), 622 mpls(7), 623 frameRelay(8), 624 atm(9) 625 } 627 L2tpv3PWType ::= TEXTUAL-CONVENTION 628 DISPLAY-HINT "" 629 STATUS current 630 DESCRIPTION 631 "Supported L2TP pseudowire types." 632 SYNTAX INTEGER { 633 frameRelay(1), 634 atmAAL5(2), 635 atmTransCell(3), 636 ethernetVLAN(4), 637 ethernet(5), 638 hdlc(6), 639 ppp(7), 640 cem(8), 641 atmVCCCell(9), 642 atmVPCCell(10) 643 } 645 L2tpv3DataSequencing ::= TEXTUAL-CONVENTION 646 DISPLAY-HINT "" 647 STATUS current 648 DESCRIPTION 649 "L2TP data sequencing levels. A value of 'none' 650 indicates that no received data packets require 651 sequencing. A value of 'nonIP' indicates that only 652 non-IP data packets require sequencing. A value of 653 'all' indicates that all received data packets require 654 sequencing. The appropriate sequencing level is 655 communicated to the peer via the Data Sequencing AVP." 656 SYNTAX INTEGER { 657 none(0), 658 nonIP(1), 659 all(2) 660 } 662 -- 663 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 665 -- Definitions of significant branches 666 -- 667 l2tpv3Notifications OBJECT IDENTIFIER ::= { l2tpv3 0 } 668 l2tpv3Objects OBJECT IDENTIFIER ::= { l2tpv3 1 } 669 l2tpv3Conformance OBJECT IDENTIFIER ::= { l2tpv3 2 } 671 -- 672 -- The L2TP Stack Configuration Group 673 -- 674 -- This group of objects is used to manage configuration 675 -- of the L2TP stack. 676 -- 677 l2tpv3StackCfg OBJECT IDENTIFIER ::= { l2tpv3Objects 1 } 679 l2tpv3StackCfgAdminState OBJECT-TYPE 680 SYNTAX INTEGER { 681 enabled(1), 682 disabled(2) 683 } 684 MAX-ACCESS read-write 685 STATUS current 686 DESCRIPTION 687 "The administrative state of the L2TP stack. Setting 688 this object to 'disabled' causes all control connections 689 to be immediately disconnected. After this point, no 690 further control connections or session may be initiated 691 or accepted. The value of this object must be 692 maintained in non-volatile memory." 693 ::= { l2tpv3StackCfg 1 } 695 l2tpv3StackCfgDrain OBJECT-TYPE 696 SYNTAX TruthValue 697 MAX-ACCESS read-write 698 STATUS current 699 DESCRIPTION 700 "Setting this object to 'true' prevents any new control 701 connections and/or sessions from being initiated or 702 accepted. However, it does not disconnect any active 703 control connections and/or sessions. The 704 'l2tpv3StackStatsIsDraining' object and the 705 'l2tpv3CtrlStatsIsDraining' object of each control 706 connection is set to 'true'. To cancel a drain, this 707 object is set to 'false'. The value of this object must 708 be maintained in non-volatile memory." 709 ::= { l2tpv3StackCfg 2 } 711 -- 712 -- The L2TP Status and Statistics Group 713 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 715 -- 716 -- This group of objects describe the current state and 717 -- statistics of the L2TP stack. 718 -- 719 l2tpv3StackStats OBJECT IDENTIFIER ::= { l2tpv3Objects 2 } 721 l2tpv3StackStatsVersion OBJECT-TYPE 722 SYNTAX Integer32 (1..65535) 723 MAX-ACCESS read-only 724 STATUS current 725 DESCRIPTION 726 "The highest protocol version number supported by this 727 L2TP stack." 728 ::= { l2tpv3StackStats 1 } 730 l2tpv3StackStatsRevision OBJECT-TYPE 731 SYNTAX Integer32 (1..65535) 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "The revision number of the L2TP stack." 736 ::= { l2tpv3StackStats 2 } 738 l2tpv3StackStatsVendorName OBJECT-TYPE 739 SYNTAX SnmpAdminString 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "The vendor name of the L2TP stack." 744 ::= { l2tpv3StackStats 3 } 746 l2tpv3StackStatsAdminState OBJECT-TYPE 747 SYNTAX INTEGER { 748 enabled(1), 749 disabled(2) 750 } 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION 754 "The administrative state of the L2TP stack. It reflects 755 the value of the l2tpv3StackCfgAdminState object." 756 ::= { l2tpv3StackStats 4 } 758 l2tpv3StackStatsIsDraining OBJECT-TYPE 759 SYNTAX TruthValue 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 764 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 766 "Indicates whether the L2TP stack is draining sessions 767 from all control connections." 768 ::= { l2tpv3StackStats 5 } 770 l2tpv3StackStatsNumCtrlEst OBJECT-TYPE 771 SYNTAX Counter32 772 MAX-ACCESS read-only 773 STATUS current 774 DESCRIPTION 775 "The total number of control connections that are 776 currently established." 777 ::= { l2tpv3StackStats 6 } 779 l2tpv3StackStatsNumSessEst OBJECT-TYPE 780 SYNTAX Counter32 781 MAX-ACCESS read-only 782 STATUS current 783 DESCRIPTION 784 "The total number of sessions that are currently 785 established." 786 ::= { l2tpv3StackStats 7 } 788 -- 789 -- The L2TP Control Connection Configuration Table 790 -- 791 l2tpv3CtrlCfgTable OBJECT-TYPE 792 SYNTAX SEQUENCE OF L2tpv3CtrlCfgEntry 793 MAX-ACCESS not-accessible 794 STATUS current 795 DESCRIPTION 796 "Table used to (re)configure the operational 797 characteristics of a single L2TP control connection. 798 There is a 1:1 correspondence between conceptual rows of 799 this table and conceptual rows of the 800 l2tpv3CtrlStatsTable. Entries in this table have the 801 same persistency characteristics as that of the 802 l2tpv3CtrlStatsTable." 803 ::= { l2tpv3Objects 3 } 805 l2tpv3CtrlCfgEntry OBJECT-TYPE 806 SYNTAX L2tpv3CtrlCfgEntry 807 MAX-ACCESS not-accessible 808 STATUS current 809 DESCRIPTION 810 "An L2TP control connection configuration entry. Entries 811 in this table are added and deleted as a result of 812 protocol interactions or management operations. The 813 latter occurs when a row is instantiated in the 815 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 817 l2tpv3CtrlCfgTable row and the encapsulation method is 818 'l2tp'." 819 INDEX { l2tpv3CtrlCfgIfIndex } 820 ::= { l2tpv3CtrlCfgTable 1 } 822 L2tpv3CtrlCfgEntry ::= 823 SEQUENCE { 824 l2tpv3CtrlCfgIfIndex InterfaceIndex, 825 l2tpv3CtrlCfgRouterID SnmpAdminString, 826 l2tpv3CtrlCfgTransport L2tpv3TransportType, 827 l2tpv3CtrlCfgPWCap OCTET STRING, 828 l2tpv3CtrlCfgFallback TruthValue, 829 l2tpv3CtrlCfgDrain TruthValue, 830 l2tpv3CtrlCfgAuth INTEGER, 831 l2tpv3CtrlCfgSecret SnmpAdminString, 832 l2tpv3CtrlCfgSecurity INTEGER, 833 l2tpv3CtrlCfgHelloInt Integer32, 834 l2tpv3CtrlCfgRWS Integer32, 835 l2tpv3CtrlCfgMaxRetrans Integer32, 836 l2tpv3CtrlCfgMaxRetransTO Integer32, 837 l2tpv3CtrlCfgReassemblyTO L2tpv3MilliSeconds, 838 l2tpv3CtrlCfgIdleTO Integer32 839 } 841 l2tpv3CtrlCfgIfIndex OBJECT-TYPE 842 SYNTAX InterfaceIndex 843 MAX-ACCESS not-accessible 844 STATUS current 845 DESCRIPTION 846 "Value equal to the ifIndex value of the Interfaces Group 847 MIB for an interface of type L2TP." 848 ::= { l2tpv3CtrlCfgEntry 1 } 850 l2tpv3CtrlCfgRouterID OBJECT-TYPE 851 SYNTAX SnmpAdminString 852 MAX-ACCESS read-write 853 STATUS current 854 DESCRIPTION 855 "The local router ID of this peer, as communicated via 856 the Router ID AVP for this control connection." 857 ::= { l2tpv3CtrlCfgEntry 2 } 859 l2tpv3CtrlCfgTransport OBJECT-TYPE 860 SYNTAX L2tpv3TransportType 861 MAX-ACCESS read-write 862 STATUS current 863 DESCRIPTION 864 "The transport type of this control connection entry. 866 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 868 This object cannot be modified when the control 869 connection is in a connecting or connected state." 870 ::= { l2tpv3CtrlCfgEntry 3 } 872 l2tpv3CtrlCfgPWCap OBJECT-TYPE 873 SYNTAX OCTET STRING (SIZE(1..256)) 874 MAX-ACCESS read-write 875 STATUS current 876 DESCRIPTION 877 "The pseudowire capabilities of this control connection 878 entry. Each octet must be a value within the range 879 specified by the L2tpv3PWType textual convention." 880 ::= { l2tpv3CtrlCfgEntry 4 } 882 l2tpv3CtrlCfgFallback OBJECT-TYPE 883 SYNTAX TruthValue 884 MAX-ACCESS read-write 885 STATUS current 886 DESCRIPTION 887 "Indicates whether fallback to older versions of L2TP is 888 enabled during control connection establishment." 889 ::= { l2tpv3CtrlCfgEntry 5 } 891 l2tpv3CtrlCfgDrain OBJECT-TYPE 892 SYNTAX TruthValue 893 MAX-ACCESS read-write 894 STATUS current 895 DESCRIPTION 896 "Setting this object to 'true' prevents any new sessions 897 from being either initiated or accepted by this control 898 connection. However, it does not disconnect any active 899 sessions for this control connection. The 900 'l2tpv3CtrlStatsIsDraining' object for this control 901 connection is set to 'true'. To cancel a drain, this 902 object is set to 'false'. This object may be overridden 903 by the global 'l2tpv3StackCfgDrain' object, which 904 globally applies drain settings to all control 905 connections." 906 DEFVAL { false } 907 ::= { l2tpv3CtrlCfgEntry 6 } 909 l2tpv3CtrlCfgAuth OBJECT-TYPE 910 SYNTAX INTEGER { 911 none(1), 912 simple(2), 913 challenge(3) 914 } 915 MAX-ACCESS read-write 917 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 919 STATUS current 920 DESCRIPTION 921 "Describes how a pair of LCCEs are to be authenticated. 922 The value 'simple' indicates that peers are 923 authenticated by their host name as described in the 924 Host Name AVP. The value 'challenge' indicates that all 925 peers are challenged to prove their identification. 926 This object cannot be modified when the control 927 connection is in a connecting or connected state." 928 DEFVAL { none } 929 ::= { l2tpv3CtrlCfgEntry 7 } 931 l2tpv3CtrlCfgSecret OBJECT-TYPE 932 SYNTAX SnmpAdminString (SIZE (0..255)) 933 MAX-ACCESS read-write 934 STATUS current 935 DESCRIPTION 936 "The shared secret used during the authentication phase 937 of control connection establishment. This object cannot 938 be modified when the control connection is in a 939 connecting or connected state. This object MUST be 940 accessible only via requests using both authentication 941 and privacy. The agent MUST report an empty string in 942 response to get, get-next, and get-bulk requests." 943 ::= { l2tpv3CtrlCfgEntry 8 } 945 l2tpv3CtrlCfgSecurity OBJECT-TYPE 946 SYNTAX INTEGER { 947 none(1), 948 other(2), 949 ipsec(3) 950 } 951 MAX-ACCESS read-write 952 STATUS current 953 DESCRIPTION 954 "Sets whether this control connection is to be secured. 955 The value of 'ipsec' indicates that all control packets 956 have IPsec headers. The types of IPsec headers (e.g. 957 AH, ESP, etc.) and their usage are outside the scope of 958 this document. This object cannot be modified when the 959 control connection is in a connecting or connected 960 state." 961 DEFVAL { none } 962 ::= { l2tpv3CtrlCfgEntry 9 } 964 l2tpv3CtrlCfgHelloInt OBJECT-TYPE 965 SYNTAX Integer32 (0..3600) 966 UNITS "seconds" 968 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 970 MAX-ACCESS read-write 971 STATUS current 972 DESCRIPTION 973 "The interval in which Hello (keepalive) packets are sent 974 by a local peer. The value zero effectively disables 975 the sending of Hello packets. Modifications to this 976 object have immediate effect." 977 DEFVAL { 60 } 978 ::= { l2tpv3CtrlCfgEntry 10 } 980 l2tpv3CtrlCfgRWS OBJECT-TYPE 981 SYNTAX Integer32 (1..65535) 982 MAX-ACCESS read-write 983 STATUS current 984 DESCRIPTION 985 "The control packet receive window size. It specifies 986 the maximum number of control packets an LCCE can send 987 for the control connection without waiting for an 988 acknowledgement from the peer. This object cannot be 989 modified when the control connection is in a connecting 990 or connected state." 991 DEFVAL { 4 } 992 ::= { l2tpv3CtrlCfgEntry 11 } 994 l2tpv3CtrlCfgMaxRetrans OBJECT-TYPE 995 SYNTAX Integer32 (0..32) 996 MAX-ACCESS read-write 997 STATUS current 998 DESCRIPTION 999 "The number of control packet retransmissions that the 1000 L2TP stack attempts for this control connection before 1001 assuming that the peer is no longer responding. A value 1002 of zero indicates that this peer does not attempt to 1003 retransmit an unacknowledged control packet. 1004 Modifications to this object have immediate effect." 1005 DEFVAL { 5 } 1006 ::= { l2tpv3CtrlCfgEntry 12 } 1008 l2tpv3CtrlCfgMaxRetransTO OBJECT-TYPE 1009 SYNTAX Integer32 (1..32) 1010 UNITS "seconds" 1011 MAX-ACCESS read-write 1012 STATUS current 1013 DESCRIPTION 1014 "The maximum retransmission timeout interval that the 1015 control connection waits before retransmitting an 1016 unacknowledged control packet. Modifications to this 1017 object have immediate effect." 1019 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1021 DEFVAL { 16 } 1022 ::= { l2tpv3CtrlCfgEntry 13 } 1024 l2tpv3CtrlCfgReassemblyTO OBJECT-TYPE 1025 SYNTAX L2tpv3MilliSeconds 1026 MAX-ACCESS read-write 1027 STATUS current 1028 DESCRIPTION 1029 "The number of milliseconds that this control connection 1030 waits before processing data packets that were received 1031 out of sequence (and that are being held for processing 1032 in sequence). A low value increases the chance of 1033 delayed packets being discarded, while a high value may 1034 cause more queueing and possibly degrade throughput if 1035 packets are truly lost. The default value for this 1036 object is zero, which means that delayed packets are 1037 considered lost, and received packets are processed in 1038 increasing order, despite any sequence number gaps." 1039 DEFVAL { 0 } 1040 ::= { l2tpv3CtrlCfgEntry 14 } 1042 l2tpv3CtrlCfgIdleTO OBJECT-TYPE 1043 SYNTAX Integer32 (-1..86400) 1044 UNITS "seconds" 1045 MAX-ACCESS read-write 1046 STATUS current 1047 DESCRIPTION 1048 "The period of time that an established control 1049 connection with no sessions waits before disconnecting 1050 the control connection. A value of zero indicates that 1051 the control connection disconnects immediately after the 1052 last session disconnects. A value of -1 leaves the 1053 control connection up indefinitely. Modifications to 1054 this object have immediate effect." 1055 DEFVAL { 0 } 1056 ::= { l2tpv3CtrlCfgEntry 15 } 1058 -- 1059 -- The L2TP Control Connection Status and Statistics Table 1060 -- 1061 l2tpv3CtrlStatsTable OBJECT-TYPE 1062 SYNTAX SEQUENCE OF L2tpv3CtrlStatsEntry 1063 MAX-ACCESS not-accessible 1064 STATUS current 1065 DESCRIPTION 1066 "Table describing the current status and statistics of a 1067 single L2TP control connection. There is a 1:1 1068 correspondence between conceptual rows of this table and 1070 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1072 conceptual rows of the l2tpv3CtrlCfgTable." 1073 ::= { l2tpv3Objects 4 } 1075 l2tpv3CtrlStatsEntry OBJECT-TYPE 1076 SYNTAX L2tpv3CtrlStatsEntry 1077 MAX-ACCESS not-accessible 1078 STATUS current 1079 DESCRIPTION 1080 "An L2TP control connection interface statistics entry." 1081 AUGMENTS { l2tpv3CtrlCfgEntry } 1082 ::= { l2tpv3CtrlStatsTable 1 } 1084 L2tpv3CtrlStatsEntry ::= 1085 SEQUENCE { 1086 l2tpv3CtrlStatsLocalID Unsigned32, 1087 l2tpv3CtrlStatsRemoteID Unsigned32, 1088 l2tpv3CtrlStatsRemoteRouterID SnmpAdminString, 1089 l2tpv3CtrlStatsState INTEGER, 1090 l2tpv3CtrlStatsIsDraining TruthValue, 1091 l2tpv3CtrlStatsInitiated INTEGER, 1092 l2tpv3CtrlStatsRemoteHostName SnmpAdminString, 1093 l2tpv3CtrlStatsRemoteVendorName SnmpAdminString, 1094 l2tpv3CtrlStatsRemoteVersion OCTET STRING, 1095 l2tpv3CtrlStatsRemotePWCap OCTET STRING, 1096 l2tpv3CtrlStatsInitialRemoteRWS Integer32, 1097 l2tpv3CtrlStatsCtrlRxZLB Counter32, 1098 l2tpv3CtrlStatsCtrlOutOfSeq Counter32, 1099 l2tpv3CtrlStatsCtrlOutOfWindow Counter32, 1100 l2tpv3CtrlStatsCtrlTxZLB Counter32, 1101 l2tpv3CtrlStatsCtrlAckTO Counter32, 1102 l2tpv3CtrlStatsCurrentRemoteRWS Gauge32, 1103 l2tpv3CtrlStatsTxSeq Integer32, 1104 l2tpv3CtrlStatsRxSeq Integer32, 1105 l2tpv3CtrlStatsNumSessCumEst Counter32, 1106 l2tpv3CtrlStatsNumSessCurrentEst Gauge32, 1107 l2tpv3CtrlStatsNumSessFailed Counter32, 1108 l2tpv3CtrlStatsLastResultCode Integer32, 1109 l2tpv3CtrlStatsLastErrorCode Integer32, 1110 l2tpv3CtrlStatsLastErrorMessage SnmpAdminString, 1111 l2tpv3CtrlStatsCtrlRxOctets Counter32, 1112 l2tpv3CtrlStatsCtrlRxPkts Counter32, 1113 l2tpv3CtrlStatsCtrlTxOctets Counter32, 1114 l2tpv3CtrlStatsCtrlTxPkts Counter32, 1115 l2tpv3CtrlStatsDataRxOctets Counter32, 1116 l2tpv3CtrlStatsDataRxPkts Counter32, 1117 l2tpv3CtrlStatsDataRxDrops Counter32, 1118 l2tpv3CtrlStatsDataTxOctets Counter32, 1119 l2tpv3CtrlStatsDataTxPkts Counter32, 1121 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1123 l2tpv3CtrlStatsCtrlHCRxOctets Counter64, 1124 l2tpv3CtrlStatsCtrlHCRxPkts Counter64, 1125 l2tpv3CtrlStatsCtrlHCTxOctets Counter64, 1126 l2tpv3CtrlStatsCtrlHCTxPkts Counter64, 1127 l2tpv3CtrlStatsDataHCRxOctets Counter64, 1128 l2tpv3CtrlStatsDataHCRxPkts Counter64, 1129 l2tpv3CtrlStatsDataHCRxDrops Counter64, 1130 l2tpv3CtrlStatsDataHCTxOctets Counter64, 1131 l2tpv3CtrlStatsDataHCTxPkts Counter64 1132 } 1134 l2tpv3CtrlStatsLocalID OBJECT-TYPE 1135 SYNTAX Unsigned32 1136 MAX-ACCESS read-only 1137 STATUS current 1138 DESCRIPTION 1139 "The local control connection ID." 1140 ::= { l2tpv3CtrlStatsEntry 1 } 1142 l2tpv3CtrlStatsRemoteID OBJECT-TYPE 1143 SYNTAX Unsigned32 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION 1147 "The remote control connection ID." 1148 ::= { l2tpv3CtrlStatsEntry 2 } 1150 l2tpv3CtrlStatsRemoteRouterID OBJECT-TYPE 1151 SYNTAX SnmpAdminString 1152 MAX-ACCESS read-only 1153 STATUS current 1154 DESCRIPTION 1155 "The remote router ID for this control connection, as 1156 communicated by the peer via the Router ID AVP." 1157 ::= { l2tpv3CtrlStatsEntry 3 } 1159 l2tpv3CtrlStatsState OBJECT-TYPE 1160 SYNTAX INTEGER { 1161 ctrlIdle(1), 1162 ctrlConnecting(2), 1163 ctrlEstablished(3), 1164 ctrlDisconnecting(4) 1165 } 1166 MAX-ACCESS read-only 1167 STATUS current 1168 DESCRIPTION 1169 "The current state of the control connection." 1170 ::= { l2tpv3CtrlStatsEntry 4 } 1172 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1174 l2tpv3CtrlStatsIsDraining OBJECT-TYPE 1175 SYNTAX TruthValue 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "Indicates whether the control connection is draining 1180 sessions. This object is set to 'true' if either 1181 'l2tpv3StackCfgDrain' or 'l2tpv3CtrlCfgDrain' is set to 1182 'true', and is only set to 'false' if both configuration 1183 objects are 'false'." 1184 ::= { l2tpv3CtrlStatsEntry 5 } 1186 l2tpv3CtrlStatsInitiated OBJECT-TYPE 1187 SYNTAX INTEGER { 1188 locally(1), 1189 remotely(2) 1190 } 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "Indicates whether the control connection was initiated 1195 locally or remotely." 1196 ::= { l2tpv3CtrlStatsEntry 6 } 1198 l2tpv3CtrlStatsRemoteHostName OBJECT-TYPE 1199 SYNTAX SnmpAdminString 1200 MAX-ACCESS read-only 1201 STATUS current 1202 DESCRIPTION 1203 "The peer's host name as discovered during the control 1204 connection establishment (via the Host Name AVP). If 1205 the control connection is idle, this object should 1206 maintain its value from the last time it was connected." 1207 ::= { l2tpv3CtrlStatsEntry 7 } 1209 l2tpv3CtrlStatsRemoteVendorName OBJECT-TYPE 1210 SYNTAX SnmpAdminString 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "The vendor name of the peer. If the control connection 1215 is idle, this object should maintain its value from the 1216 last time it was connected." 1217 ::= { l2tpv3CtrlStatsEntry 8 } 1219 l2tpv3CtrlStatsRemotePWCap OBJECT-TYPE 1220 SYNTAX OCTET STRING (SIZE(1..256)) 1222 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1224 MAX-ACCESS read-write 1225 STATUS current 1226 DESCRIPTION 1227 "The peer's pseudowire capabilities for this control 1228 connection. Each octet must be a value within the range 1229 specified by the L2tpv3PWType textual convention." 1230 ::= { l2tpv3CtrlStatsEntry 9 } 1232 l2tpv3CtrlStatsRemoteVersion OBJECT-TYPE 1233 SYNTAX OCTET STRING (SIZE(2)) 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "The peer implementation's protocol version number and 1238 revision number. The first octet contains the protocol 1239 version number. The second octet contains the protocol 1240 revision number." 1241 ::= { l2tpv3CtrlStatsEntry 10 } 1243 l2tpv3CtrlStatsInitialRemoteRWS OBJECT-TYPE 1244 SYNTAX Integer32 (0..65535) 1245 MAX-ACCESS read-only 1246 STATUS current 1247 DESCRIPTION 1248 "The peer's receive window size as conveyed during 1249 control connection establishment (via the Remote Window 1250 Size AVP). If the control connection is idle, this 1251 object should maintain its value from the last time it 1252 was connected." 1253 ::= { l2tpv3CtrlStatsEntry 11 } 1255 l2tpv3CtrlStatsCtrlRxZLB OBJECT-TYPE 1256 SYNTAX Counter32 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "The number of Zero-Length-Body (acknowledgement) control 1261 packets that have been received on the control 1262 connection." 1263 ::= { l2tpv3CtrlStatsEntry 12 } 1265 l2tpv3CtrlStatsCtrlOutOfSeq OBJECT-TYPE 1266 SYNTAX Counter32 1267 MAX-ACCESS read-only 1268 STATUS current 1269 DESCRIPTION 1270 "The number of control packets that have been received 1271 out of order (per the sequence numbers) on this control 1273 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1275 connection, including out of window packets." 1276 ::= { l2tpv3CtrlStatsEntry 13 } 1278 l2tpv3CtrlStatsCtrlOutOfWindow OBJECT-TYPE 1279 SYNTAX Counter32 1280 MAX-ACCESS read-only 1281 STATUS current 1282 DESCRIPTION 1283 "The number of control packets that have been received 1284 outside of the offered receive window for the control 1285 connection. Whether these packets are queued or 1286 discarded is implementation-specific." 1287 ::= { l2tpv3CtrlStatsEntry 14 } 1289 l2tpv3CtrlStatsCtrlTxZLB OBJECT-TYPE 1290 SYNTAX Counter32 1291 MAX-ACCESS read-only 1292 STATUS current 1293 DESCRIPTION 1294 "The number of Zero-Length-Body (acknowledgement) control 1295 packets that have been sent to the peer for this control 1296 connection." 1297 ::= { l2tpv3CtrlStatsEntry 15 } 1299 l2tpv3CtrlStatsCtrlAckTO OBJECT-TYPE 1300 SYNTAX Counter32 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "The number of control packet timeouts due to late 1305 acknowledgements from the peer for this control 1306 connection." 1307 ::= { l2tpv3CtrlStatsEntry 16 } 1309 l2tpv3CtrlStatsCurrentRemoteRWS OBJECT-TYPE 1310 SYNTAX Gauge32 (0..65535) 1311 MAX-ACCESS read-only 1312 STATUS current 1313 DESCRIPTION 1314 "The current remote receive window size as determined by 1315 the local flow control mechanism employed." 1316 ::= { l2tpv3CtrlStatsEntry 17 } 1318 l2tpv3CtrlStatsTxSeq OBJECT-TYPE 1319 SYNTAX Integer32 (0..65535) 1320 MAX-ACCESS read-only 1321 STATUS current 1322 DESCRIPTION 1324 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1326 "The next send (Ns) sequence number for the control 1327 connection." 1328 ::= { l2tpv3CtrlStatsEntry 18 } 1330 l2tpv3CtrlStatsRxSeq OBJECT-TYPE 1331 SYNTAX Integer32 (0..65535) 1332 MAX-ACCESS read-only 1333 STATUS current 1334 DESCRIPTION 1335 "The next receive (Nr) sequence number for the control 1336 connection." 1337 ::= { l2tpv3CtrlStatsEntry 19 } 1339 l2tpv3CtrlStatsNumSessCumEst OBJECT-TYPE 1340 SYNTAX Counter32 1341 MAX-ACCESS read-only 1342 STATUS current 1343 DESCRIPTION 1344 "The cumulative number of sessions that this control 1345 connection has established during its lifetime." 1346 ::= { l2tpv3CtrlStatsEntry 20 } 1348 l2tpv3CtrlStatsNumSessCurrentEst OBJECT-TYPE 1349 SYNTAX Gauge32 1350 MAX-ACCESS read-only 1351 STATUS current 1352 DESCRIPTION 1353 "The number of sessions currently in the established 1354 state for this control connection." 1355 ::= { l2tpv3CtrlStatsEntry 21 } 1357 l2tpv3CtrlStatsNumSessFailed OBJECT-TYPE 1358 SYNTAX Counter32 1359 MAX-ACCESS read-only 1360 STATUS current 1361 DESCRIPTION 1362 "The total number of sessions that were negotiated but 1363 failed to be established by this control connection." 1364 ::= { l2tpv3CtrlStatsEntry 22 } 1366 l2tpv3CtrlStatsLastResultCode OBJECT-TYPE 1367 SYNTAX Integer32 (0..65535) 1368 MAX-ACCESS read-only 1369 STATUS current 1370 DESCRIPTION 1371 "The result code as conveyed by the Result Code AVP from 1372 the most recent session to be torn down." 1373 ::= { l2tpv3CtrlStatsEntry 23 } 1375 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1377 l2tpv3CtrlStatsLastErrorCode OBJECT-TYPE 1378 SYNTAX Integer32 (0..65535) 1379 MAX-ACCESS read-only 1380 STATUS current 1381 DESCRIPTION 1382 "The error code as conveyed by the Result Code AVP from 1383 the most recent session to be torn down." 1384 ::= { l2tpv3CtrlStatsEntry 24 } 1386 l2tpv3CtrlStatsLastErrorMessage OBJECT-TYPE 1387 SYNTAX SnmpAdminString 1388 MAX-ACCESS read-only 1389 STATUS current 1390 DESCRIPTION 1391 "The optional message as conveyed by the Result Code AVP 1392 from the most recent session to be torn down." 1393 ::= { l2tpv3CtrlStatsEntry 25 } 1395 l2tpv3CtrlStatsCtrlRxOctets OBJECT-TYPE 1396 SYNTAX Counter32 1397 MAX-ACCESS read-only 1398 STATUS current 1399 DESCRIPTION 1400 "The number of control octets that have been received by 1401 this control connection." 1402 ::= { l2tpv3CtrlStatsEntry 26 } 1404 l2tpv3CtrlStatsCtrlRxPkts OBJECT-TYPE 1405 SYNTAX Counter32 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "The number of control packets that have been received by 1410 this control connection." 1411 ::= { l2tpv3CtrlStatsEntry 27 } 1413 l2tpv3CtrlStatsCtrlTxOctets OBJECT-TYPE 1414 SYNTAX Counter32 1415 MAX-ACCESS read-only 1416 STATUS current 1417 DESCRIPTION 1418 "The number of control octets that have been sent by this 1419 control connection." 1420 ::= { l2tpv3CtrlStatsEntry 28 } 1422 l2tpv3CtrlStatsCtrlTxPkts OBJECT-TYPE 1423 SYNTAX Counter32 1425 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1427 MAX-ACCESS read-only 1428 STATUS current 1429 DESCRIPTION 1430 "The number of control packets that have been sent by 1431 this control connection." 1432 ::= { l2tpv3CtrlStatsEntry 29 } 1434 l2tpv3CtrlStatsDataRxOctets OBJECT-TYPE 1435 SYNTAX Counter32 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "The number of data octets that have been received by 1440 sessions negotiated by this control connection." 1441 ::= { l2tpv3CtrlStatsEntry 30 } 1443 l2tpv3CtrlStatsDataRxPkts OBJECT-TYPE 1444 SYNTAX Counter32 1445 MAX-ACCESS read-only 1446 STATUS current 1447 DESCRIPTION 1448 "The number of data packets that have been received by 1449 sessions negotiated by this control connection." 1450 ::= { l2tpv3CtrlStatsEntry 31 } 1452 l2tpv3CtrlStatsDataRxDrops OBJECT-TYPE 1453 SYNTAX Counter32 1454 MAX-ACCESS read-only 1455 STATUS current 1456 DESCRIPTION 1457 "The number of received data packets that have been 1458 dropped by sessions negotiated by this control 1459 connection." 1460 ::= { l2tpv3CtrlStatsEntry 32 } 1462 l2tpv3CtrlStatsDataTxOctets OBJECT-TYPE 1463 SYNTAX Counter32 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "The number of data octets that have been sent by 1468 sessions negotiated by this control connection." 1469 ::= { l2tpv3CtrlStatsEntry 33 } 1471 l2tpv3CtrlStatsDataTxPkts OBJECT-TYPE 1472 SYNTAX Counter32 1473 MAX-ACCESS read-only 1474 STATUS current 1476 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1478 DESCRIPTION 1479 "The number of data packets that have been sent by 1480 sessions negotiated by this control connection." 1481 ::= { l2tpv3CtrlStatsEntry 34 } 1483 -- 1484 -- High-capacity counter objects.These objects are all 64-bit 1485 -- versions of the above 32-bit counters.They have the same 1486 -- basic semantics as their 32-bit counterparts. 1487 -- 1488 l2tpv3CtrlStatsCtrlHCRxOctets OBJECT-TYPE 1489 SYNTAX Counter64 1490 MAX-ACCESS read-only 1491 STATUS current 1492 DESCRIPTION 1493 "The 64-bit version of l2tpv3CtrlStatsCtrlRxOctets." 1494 ::= { l2tpv3CtrlStatsEntry 35 } 1496 l2tpv3CtrlStatsCtrlHCRxPkts OBJECT-TYPE 1497 SYNTAX Counter64 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "The 64-bit version of l2tpv3CtrlStatsCtrlRxPkts." 1502 ::= { l2tpv3CtrlStatsEntry 36 } 1504 l2tpv3CtrlStatsCtrlHCTxOctets OBJECT-TYPE 1505 SYNTAX Counter64 1506 MAX-ACCESS read-only 1507 STATUS current 1508 DESCRIPTION 1509 "The 64-bit version of l2tpv3CtrlStatsCtrlTxOctets." 1510 ::= { l2tpv3CtrlStatsEntry 37 } 1512 l2tpv3CtrlStatsCtrlHCTxPkts OBJECT-TYPE 1513 SYNTAX Counter64 1514 MAX-ACCESS read-only 1515 STATUS current 1516 DESCRIPTION 1517 "The 64-bit version of l2tpv3CtrlStatsCtrlTxPkts." 1518 ::= { l2tpv3CtrlStatsEntry 38 } 1520 l2tpv3CtrlStatsDataHCRxOctets OBJECT-TYPE 1521 SYNTAX Counter64 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "The 64-bit version of l2tpv3CtrlStatsDataRxOctets." 1527 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1529 ::= { l2tpv3CtrlStatsEntry 39 } 1531 l2tpv3CtrlStatsDataHCRxPkts OBJECT-TYPE 1532 SYNTAX Counter64 1533 MAX-ACCESS read-only 1534 STATUS current 1535 DESCRIPTION 1536 "The 64-bit version of l2tpv3CtrlStatsDataRxPkts." 1537 ::= { l2tpv3CtrlStatsEntry 40 } 1539 l2tpv3CtrlStatsDataHCRxDrops OBJECT-TYPE 1540 SYNTAX Counter64 1541 MAX-ACCESS read-only 1542 STATUS current 1543 DESCRIPTION 1544 "The 64-bit version of l2tpv3CtrlStatsDataRxDrops." 1545 ::= { l2tpv3CtrlStatsEntry 41 } 1547 l2tpv3CtrlStatsDataHCTxOctets OBJECT-TYPE 1548 SYNTAX Counter64 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "The 64-bit version of l2tpv3CtrlStatsDataTxOctets." 1553 ::= { l2tpv3CtrlStatsEntry 42 } 1555 l2tpv3CtrlStatsDataHCTxPkts OBJECT-TYPE 1556 SYNTAX Counter64 1557 MAX-ACCESS read-only 1558 STATUS current 1559 DESCRIPTION 1560 "The 64-bit version of l2tpv3CtrlStatsDataTxPkts." 1561 ::= { l2tpv3CtrlStatsEntry 43 } 1563 -- 1564 -- The L2TP Control Connection Mapping Table 1565 -- 1566 l2tpv3CtrlMapTable OBJECT-TYPE 1567 SYNTAX SEQUENCE OF L2tpv3CtrlMapEntry 1568 MAX-ACCESS not-accessible 1569 STATUS current 1570 DESCRIPTION 1571 "Table intended to assist management applications to 1572 quickly determine the ifIndex value for a given local 1573 control connection ID." 1574 ::= { l2tpv3Objects 5 } 1576 l2tpv3CtrlMapEntry OBJECT-TYPE 1577 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1579 SYNTAX L2tpv3CtrlMapEntry 1580 MAX-ACCESS not-accessible 1581 STATUS current 1582 DESCRIPTION 1583 "An L2TP control connection index map entry." 1584 INDEX { l2tpv3CtrlMapLocalID } 1585 ::= { l2tpv3CtrlMapTable 1 } 1587 L2tpv3CtrlMapEntry ::= 1588 SEQUENCE { 1589 l2tpv3CtrlMapLocalID Unsigned32, 1590 l2tpv3CtrlMapIfIndex InterfaceIndex 1591 } 1593 l2tpv3CtrlMapLocalID OBJECT-TYPE 1594 SYNTAX Unsigned32 1595 MAX-ACCESS not-accessible 1596 STATUS current 1597 DESCRIPTION 1598 "The local control connection ID." 1599 ::= { l2tpv3CtrlMapEntry 1 } 1601 l2tpv3CtrlMapIfIndex OBJECT-TYPE 1602 SYNTAX InterfaceIndex 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "The ifIndex value of a control connection interface, 1607 represented in the Interfaces Group MIB as an entry with 1608 an interface type of L2TP." 1609 ::= { l2tpv3CtrlMapEntry 2 } 1611 -- 1612 -- The L2TP Session Configuration Table 1613 -- 1614 l2tpv3SessionCfgTable OBJECT-TYPE 1615 SYNTAX SEQUENCE OF L2tpv3SessionCfgEntry 1616 MAX-ACCESS not-accessible 1617 STATUS current 1618 DESCRIPTION 1619 "Table used to (re)configure the operational 1620 characteristics of a single L2TP session. There is a 1621 1:1 correspondence between conceptual rows of this table 1622 and conceptual rows of the l2tpv3SessionStatsTable. 1623 Entries in this table have the same persistency 1624 characteristics as that of the l2tpv3SessionStatsTable." 1625 ::= { l2tpv3Objects 6 } 1627 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1629 l2tpv3SessionCfgEntry OBJECT-TYPE 1630 SYNTAX L2tpv3SessionCfgEntry 1631 MAX-ACCESS not-accessible 1632 STATUS current 1633 DESCRIPTION 1634 "An L2TP session configuration entry. Entries in this 1635 table are added and deleted as a result of protocol 1636 interactions or management operations." 1637 INDEX { l2tpv3SessionCfgIfIndex } 1638 ::= { l2tpv3SessionCfgTable 1 } 1640 L2tpv3SessionCfgEntry ::= 1641 SEQUENCE { 1642 l2tpv3SessionCfgIfIndex InterfaceIndex, 1643 l2tpv3SessionCfgLocalID Unsigned32, 1644 l2tpv3SessionCfgRemoteID Unsigned32, 1645 l2tpv3SessionCfgCtrlLocalID Unsigned32, 1646 l2tpv3SessionCfgPWType L2tpv3PWType, 1647 l2tpv3SessionCfgEndID DisplayString, 1648 l2tpv3SessionCfgAppID DisplayString, 1649 l2tpv3SessionCfgPWEncap INTEGER, 1650 l2tpv3SessionCfgSeq L2tpv3DataSequencing, 1651 l2tpv3SessionCfgLocalCookie DisplayString, 1652 l2tpv3SessionCfgRemoteCookie DisplayString, 1653 l2tpv3SessionCfgCallType INTEGER 1654 } 1656 l2tpv3SessionCfgIfIndex OBJECT-TYPE 1657 SYNTAX InterfaceIndex 1658 MAX-ACCESS not-accessible 1659 STATUS current 1660 DESCRIPTION 1661 "The ifIndex value of the interface from which L2 frames 1662 are being forwarded. For example, the ifIndex could be 1663 a DS0 on an LAC or a virtual PPP interface on an LNS." 1664 ::= { l2tpv3SessionCfgEntry 1 } 1666 l2tpv3SessionCfgLocalID OBJECT-TYPE 1667 SYNTAX Unsigned32 1668 MAX-ACCESS read-create 1669 STATUS current 1670 DESCRIPTION 1671 "Sets the local session ID." 1672 ::= { l2tpv3SessionCfgEntry 2 } 1674 l2tpv3SessionCfgRemoteID OBJECT-TYPE 1675 SYNTAX Unsigned32 1676 MAX-ACCESS read-create 1678 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1680 STATUS current 1681 DESCRIPTION 1682 "Sets the remote session ID." 1683 ::= { l2tpv3SessionCfgEntry 3 } 1685 l2tpv3SessionCfgCtrlLocalID OBJECT-TYPE 1686 SYNTAX Unsigned32 1687 MAX-ACCESS read-create 1688 STATUS current 1689 DESCRIPTION 1690 "Sets the local control connection ID of the control 1691 connection with which this session may be associated. 1692 If the session is not associated with a control 1693 connection, the value of this object is 0." 1694 ::= { l2tpv3SessionCfgEntry 4 } 1696 l2tpv3SessionCfgPWType OBJECT-TYPE 1697 SYNTAX L2tpv3PWType 1698 MAX-ACCESS read-create 1699 STATUS current 1700 DESCRIPTION 1701 "Sets the pseudowire type of the session, which is sent 1702 to the peer via the Pseudowire Type AVP." 1703 ::= { l2tpv3SessionCfgEntry 5 } 1705 l2tpv3SessionCfgEndID OBJECT-TYPE 1706 SYNTAX DisplayString (SIZE(0..255)) 1707 MAX-ACCESS read-create 1708 STATUS current 1709 DESCRIPTION 1710 "Sets the End Identifier that is sent to the peer via the 1711 End ID AVP." 1712 ::= { l2tpv3SessionCfgEntry 6 } 1714 l2tpv3SessionCfgAppID OBJECT-TYPE 1715 SYNTAX DisplayString (SIZE(0..255)) 1716 MAX-ACCESS read-create 1717 STATUS current 1718 DESCRIPTION 1719 "Sets the Application Code and Application Info that are 1720 sent to the peer via the Application ID AVP." 1721 ::= { l2tpv3SessionCfgEntry 7 } 1723 l2tpv3SessionCfgPWEncap OBJECT-TYPE 1724 SYNTAX INTEGER { 1725 none(0), 1726 default(1) 1727 } 1729 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1731 MAX-ACCESS read-create 1732 STATUS current 1733 DESCRIPTION 1734 "Sets the Control Encapsulation Type that is sent to the 1735 peer via the Pseudowire Control Encapsulation AVP." 1736 DEFVAL { none } 1737 ::= { l2tpv3SessionCfgEntry 8 } 1739 l2tpv3SessionCfgSeq OBJECT-TYPE 1740 SYNTAX L2tpv3DataSequencing 1741 MAX-ACCESS read-create 1742 STATUS current 1743 DESCRIPTION 1744 "Sets the Data Sequencing Level that is required of the 1745 peer. Sent to the peer via the Data Sequencing AVP." 1746 DEFVAL { none } 1747 ::= { l2tpv3SessionCfgEntry 9 } 1749 l2tpv3SessionCfgLocalCookie OBJECT-TYPE 1750 SYNTAX DisplayString (SIZE(0..8)) 1751 MAX-ACCESS read-create 1752 STATUS current 1753 DESCRIPTION 1754 "Sets the local cookie that is included in outgoing data 1755 packets." 1756 ::= { l2tpv3SessionCfgEntry 10 } 1758 l2tpv3SessionCfgRemoteCookie OBJECT-TYPE 1759 SYNTAX DisplayString (SIZE(0..8)) 1760 MAX-ACCESS read-create 1761 STATUS current 1762 DESCRIPTION 1763 "Sets the remote cookie that is expected in incoming data 1764 packets." 1765 ::= { l2tpv3SessionCfgEntry 11 } 1767 l2tpv3SessionCfgCallType OBJECT-TYPE 1768 SYNTAX INTEGER { 1769 lacInitiator(1), 1770 lacResponder(2), 1771 lnsInitiator(3), 1772 lnsResponder(4) 1773 } 1774 MAX-ACCESS read-create 1775 STATUS current 1776 DESCRIPTION 1777 "The role this LCCE is playing for this session. For 1778 example, 'lacInitiator' indicates that this control 1780 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1782 connection peer is acting as an LAC and generated an 1783 call request (ICRQ or OCRQ) to its peer." 1784 ::= { l2tpv3SessionCfgEntry 12 } 1786 -- 1787 -- The L2TP Session Status and Statistics Table 1788 -- 1789 l2tpv3SessionStatsTable OBJECT-TYPE 1790 SYNTAX SEQUENCE OF L2tpv3SessionStatsEntry 1791 MAX-ACCESS not-accessible 1792 STATUS current 1793 DESCRIPTION 1794 "Table that describes the current status and statistics 1795 of a single L2TP session." 1796 ::= { l2tpv3Objects 7 } 1798 l2tpv3SessionStatsEntry OBJECT-TYPE 1799 SYNTAX L2tpv3SessionStatsEntry 1800 MAX-ACCESS not-accessible 1801 STATUS current 1802 DESCRIPTION 1803 "An L2TP session interface statistics entry." 1804 AUGMENTS { l2tpv3SessionCfgEntry } 1805 ::= { l2tpv3SessionStatsTable 1 } 1807 L2tpv3SessionStatsEntry ::= 1808 SEQUENCE { 1809 l2tpv3SessionStatsRemoteEndID DisplayString, 1810 l2tpv3SessionStatsRemoteAppID DisplayString, 1811 l2tpv3SessionStatsRemotePWEncap INTEGER, 1812 l2tpv3SessionStatsRemoteSeq L2tpv3DataSequencing, 1813 l2tpv3SessionStatsState INTEGER, 1814 l2tpv3SessionStatsCircuitStatus Unsigned32, 1815 l2tpv3SessionStatsSerialNumber Unsigned32, 1816 l2tpv3SessionStatsRxConnectSpeed Unsigned32, 1817 l2tpv3SessionStatsTxConnectSpeed Unsigned32, 1818 l2tpv3SessionStatsPhysChannelID Unsigned32, 1819 l2tpv3SessionStatsPrivateGroupID SnmpAdminString, 1820 l2tpv3SessionStatsOutOfSeq Counter32, 1821 l2tpv3SessionStatsReassemblyTO Counter32, 1822 l2tpv3SessionStatsTxSeq Counter32, 1823 l2tpv3SessionStatsRxSeq Counter32, 1824 l2tpv3SessionStatsRxOctets Counter32, 1825 l2tpv3SessionStatsRxPkts Counter32, 1826 l2tpv3SessionStatsRxDrops Counter32, 1827 l2tpv3SessionStatsTxOctets Counter32, 1828 l2tpv3SessionStatsTxPkts Counter32, 1829 l2tpv3SessionStatsHCRxOctets Counter64, 1831 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1833 l2tpv3SessionStatsHCRxPkts Counter64, 1834 l2tpv3SessionStatsHCRxDrops Counter64, 1835 l2tpv3SessionStatsHCTxOctets Counter64, 1836 l2tpv3SessionStatsHCTxPkts Counter64 1837 } 1839 l2tpv3SessionStatsRemoteEndID OBJECT-TYPE 1840 SYNTAX DisplayString (SIZE(0..255)) 1841 MAX-ACCESS read-only 1842 STATUS current 1843 DESCRIPTION 1844 "The peer's End Identifier, as communicated via the End 1845 ID AVP." 1846 ::= { l2tpv3SessionStatsEntry 1 } 1848 l2tpv3SessionStatsRemoteAppID OBJECT-TYPE 1849 SYNTAX DisplayString (SIZE(0..255)) 1850 MAX-ACCESS read-only 1851 STATUS current 1852 DESCRIPTION 1853 "The peer's Application Code and Application Info, as 1854 communicated via the Application ID AVP." 1855 ::= { l2tpv3SessionStatsEntry 2 } 1857 l2tpv3SessionStatsRemotePWEncap OBJECT-TYPE 1858 SYNTAX INTEGER { 1859 none(0), 1860 default(1) 1861 } 1862 MAX-ACCESS read-only 1863 STATUS current 1864 DESCRIPTION 1865 "The peer's Control Encapsulation Type, as communicated 1866 via the Pseudowire Control Encapsulation AVP." 1867 ::= { l2tpv3SessionStatsEntry 3 } 1869 l2tpv3SessionStatsRemoteSeq OBJECT-TYPE 1870 SYNTAX L2tpv3DataSequencing 1871 MAX-ACCESS read-create 1872 STATUS current 1873 DESCRIPTION 1874 "The peer's Data Sequencing Level, as communicated via 1875 the Data Sequencing AVP." 1876 DEFVAL { none } 1877 ::= { l2tpv3SessionStatsEntry 4 } 1879 l2tpv3SessionStatsState OBJECT-TYPE 1880 SYNTAX INTEGER { 1882 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1884 sessionIdle(1), 1885 sessionConnecting(2), 1886 sessionEstablished(3), 1887 sessionDisconnecting(4) 1888 } 1889 MAX-ACCESS read-only 1890 STATUS current 1891 DESCRIPTION 1892 "The current state of the session." 1893 ::= { l2tpv3SessionStatsEntry 5 } 1895 l2tpv3SessionStatsCircuitStatus OBJECT-TYPE 1896 SYNTAX Unsigned32 1897 MAX-ACCESS read-only 1898 STATUS current 1899 DESCRIPTION 1900 "The current status of the circuit forwarded by the 1901 session." 1902 ::= { l2tpv3SessionStatsEntry 6 } 1904 l2tpv3SessionStatsSerialNumber OBJECT-TYPE 1905 SYNTAX Unsigned32 1906 MAX-ACCESS read-only 1907 STATUS current 1908 DESCRIPTION 1909 "The serial number that has been assigned to this 1910 session." 1911 ::= { l2tpv3SessionStatsEntry 7 } 1913 l2tpv3SessionStatsRxConnectSpeed OBJECT-TYPE 1914 SYNTAX Unsigned32 1915 UNITS "bits per second" 1916 MAX-ACCESS read-only 1917 STATUS current 1918 DESCRIPTION 1919 "The last known receive baud rate for this session." 1920 ::= { l2tpv3SessionStatsEntry 8 } 1922 l2tpv3SessionStatsTxConnectSpeed OBJECT-TYPE 1923 SYNTAX Unsigned32 1924 UNITS "bits per second" 1925 MAX-ACCESS read-only 1926 STATUS current 1927 DESCRIPTION 1928 "The last known transmit baud rate for this session." 1929 ::= { l2tpv3SessionStatsEntry 9 } 1931 l2tpv3SessionStatsPhysChannelID OBJECT-TYPE 1932 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1934 SYNTAX Unsigned32 1935 MAX-ACCESS read-only 1936 STATUS current 1937 DESCRIPTION 1938 "The physical channel identifier for the session." 1939 ::= { l2tpv3SessionStatsEntry 10 } 1941 l2tpv3SessionStatsPrivateGroupID OBJECT-TYPE 1942 SYNTAX SnmpAdminString 1943 MAX-ACCESS read-only 1944 STATUS current 1945 DESCRIPTION 1946 "The private group ID used for this L2TP session. If no 1947 private group ID is found, then a null string is 1948 returned." 1949 ::= { l2tpv3SessionStatsEntry 11 } 1951 l2tpv3SessionStatsOutOfSeq OBJECT-TYPE 1952 SYNTAX Counter32 1953 MAX-ACCESS read-only 1954 STATUS current 1955 DESCRIPTION 1956 "The total number of data packets received out of 1957 sequence for this session." 1958 ::= { l2tpv3SessionStatsEntry 12 } 1960 l2tpv3SessionStatsReassemblyTO OBJECT-TYPE 1961 SYNTAX Counter32 1962 MAX-ACCESS read-only 1963 STATUS current 1964 DESCRIPTION 1965 "The number of reassembly timeouts that have occurred for 1966 this session." 1967 ::= { l2tpv3SessionStatsEntry 13 } 1969 l2tpv3SessionStatsTxSeq OBJECT-TYPE 1970 SYNTAX Counter32 1971 MAX-ACCESS read-only 1972 STATUS current 1973 DESCRIPTION 1974 "The current sequence number for outgoing data packets 1975 for this session." 1976 ::= { l2tpv3SessionStatsEntry 14 } 1978 l2tpv3SessionStatsRxSeq OBJECT-TYPE 1979 SYNTAX Counter32 1980 MAX-ACCESS read-only 1981 STATUS current 1983 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 1985 DESCRIPTION 1986 "The current sequence number for incoming data packets 1987 for this session." 1988 ::= { l2tpv3SessionStatsEntry 15 } 1990 l2tpv3SessionStatsRxOctets OBJECT-TYPE 1991 SYNTAX Counter32 1992 MAX-ACCESS read-only 1993 STATUS current 1994 DESCRIPTION 1995 "The number of data octets that have been received by 1996 this session." 1997 ::= { l2tpv3SessionStatsEntry 16 } 1999 l2tpv3SessionStatsRxPkts OBJECT-TYPE 2000 SYNTAX Counter32 2001 MAX-ACCESS read-only 2002 STATUS current 2003 DESCRIPTION 2004 "The number of data packets that have been received by 2005 this session." 2006 ::= { l2tpv3SessionStatsEntry 17 } 2008 l2tpv3SessionStatsRxDrops OBJECT-TYPE 2009 SYNTAX Counter32 2010 MAX-ACCESS read-only 2011 STATUS current 2012 DESCRIPTION 2013 "The number of received data packets that have been 2014 dropped by this session." 2015 ::= { l2tpv3SessionStatsEntry 18 } 2017 l2tpv3SessionStatsTxOctets OBJECT-TYPE 2018 SYNTAX Counter32 2019 MAX-ACCESS read-only 2020 STATUS current 2021 DESCRIPTION 2022 "The number of data octets that have been sent by this 2023 session." 2024 ::= { l2tpv3SessionStatsEntry 19 } 2026 l2tpv3SessionStatsTxPkts OBJECT-TYPE 2027 SYNTAX Counter32 2028 MAX-ACCESS read-only 2029 STATUS current 2030 DESCRIPTION 2031 "The number of data packets that have been sent by this 2032 session." 2034 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2036 ::= { l2tpv3SessionStatsEntry 20 } 2038 l2tpv3SessionStatsHCRxOctets OBJECT-TYPE 2039 SYNTAX Counter64 2040 MAX-ACCESS read-only 2041 STATUS current 2042 DESCRIPTION 2043 "The 64-bit version of l2tpv3SessionStatsRxOctets." 2044 ::= { l2tpv3SessionStatsEntry 21 } 2046 l2tpv3SessionStatsHCRxPkts OBJECT-TYPE 2047 SYNTAX Counter64 2048 MAX-ACCESS read-only 2049 STATUS current 2050 DESCRIPTION 2051 "The 64-bit version of l2tpv3SessionStatsRxPkts." 2052 ::= { l2tpv3SessionStatsEntry 22 } 2054 l2tpv3SessionStatsHCRxDrops OBJECT-TYPE 2055 SYNTAX Counter64 2056 MAX-ACCESS read-only 2057 STATUS current 2058 DESCRIPTION 2059 "The 64-bit version of l2tpv3SessionStatsRxDrops." 2060 ::= { l2tpv3SessionStatsEntry 23 } 2062 l2tpv3SessionStatsHCTxOctets OBJECT-TYPE 2063 SYNTAX Counter64 2064 MAX-ACCESS read-only 2065 STATUS current 2066 DESCRIPTION 2067 "The 64-bit version of l2tpv3SessionStatsTxOctets." 2068 ::= { l2tpv3SessionStatsEntry 24 } 2070 l2tpv3SessionStatsHCTxPkts OBJECT-TYPE 2071 SYNTAX Counter64 2072 MAX-ACCESS read-only 2073 STATUS current 2074 DESCRIPTION 2075 "The 64-bit version of l2tpv3SessionStatsTxPkts." 2076 ::= { l2tpv3SessionStatsEntry 25 } 2078 -- 2079 -- The L2TP Session Mapping Table 2080 -- 2081 l2tpv3SessionMapTable OBJECT-TYPE 2082 SYNTAX SEQUENCE OF L2tpv3SessionMapEntry 2083 MAX-ACCESS not-accessible 2085 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2087 STATUS current 2088 DESCRIPTION 2089 "Table intended to assist management applications to map 2090 interfaces to control connection and session IDs." 2091 ::= { l2tpv3Objects 8 } 2093 l2tpv3SessionMapEntry OBJECT-TYPE 2094 SYNTAX L2tpv3SessionMapEntry 2095 MAX-ACCESS not-accessible 2096 STATUS current 2097 DESCRIPTION 2098 "An L2TP session index map entry." 2099 INDEX { l2tpv3SessionMapIfIndex } 2100 ::= { l2tpv3SessionMapTable 1 } 2102 L2tpv3SessionMapEntry ::= 2103 SEQUENCE { 2104 l2tpv3SessionMapIfIndex InterfaceIndex, 2105 l2tpv3SessionMapCtrlIfIndex InterfaceIndex, 2106 l2tpv3SessionMapLocalID Unsigned32, 2107 l2tpv3SessionMapStatus RowStatus 2108 } 2110 l2tpv3SessionMapIfIndex OBJECT-TYPE 2111 SYNTAX InterfaceIndex 2112 MAX-ACCESS not-accessible 2113 STATUS current 2114 DESCRIPTION 2115 "The ifIndex value of the interface being forwarded via 2116 an L2TP session. For example, the interface could be an 2117 Ethernet interface on an LAC or a virtual PPP interface 2118 on the LNS." 2119 ::= { l2tpv3SessionMapEntry 1 } 2121 l2tpv3SessionMapCtrlIfIndex OBJECT-TYPE 2122 SYNTAX InterfaceIndex 2123 MAX-ACCESS read-create 2124 STATUS current 2125 DESCRIPTION 2126 "The ifIndex value of the session's control connection. 2127 The object establishes a binding between a particular 2128 interface identified by l2tpv3SessionMapIfIndex to a 2129 particular control connection." 2130 ::= { l2tpv3SessionMapEntry 2 } 2132 l2tpv3SessionMapLocalID OBJECT-TYPE 2133 SYNTAX Unsigned32 2134 MAX-ACCESS read-only 2136 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2138 STATUS current 2139 DESCRIPTION 2140 "The local session ID for this session." 2141 ::= { l2tpv3SessionMapEntry 3 } 2143 l2tpv3SessionMapStatus OBJECT-TYPE 2144 SYNTAX RowStatus 2145 MAX-ACCESS read-create 2146 STATUS current 2147 DESCRIPTION 2148 "The status of this session map entry." 2149 ::= { l2tpv3SessionMapEntry 4 } 2151 -- 2152 -- Definition of generic L2TP notifications 2153 -- 2154 l2tpv3CtrlAuthFailure NOTIFICATION-TYPE 2155 OBJECTS { 2156 l2tpv3CtrlStatsInitiated, 2157 l2tpv3CtrlStatsRemoteHostName 2158 } 2159 STATUS current 2160 DESCRIPTION 2161 "Trap signifying that an attempt to establish a control 2162 connection to a remote peer has failed authentication." 2163 ::= { l2tpv3Notifications 1 } 2165 -- 2166 -- Conformance information 2167 -- 2168 l2tpv3Groups OBJECT IDENTIFIER ::= { l2tpv3Conformance 1 } 2169 l2tpv3Compliances OBJECT IDENTIFIER ::= { l2tpv3Conformance 2 } 2171 -- 2172 -- Compliance statements 2173 -- 2174 l2tpv3MIBFullCompliance MODULE-COMPLIANCE 2175 STATUS current 2176 DESCRIPTION 2177 "An implementation claims full compliance when this MIB 2178 is implemented with support for read-create and read- 2179 write operations, thereby allowing configuration and 2180 monitoring, respectively." 2182 MODULE -- this module 2184 -- unconditionally mandatory groups 2185 MANDATORY-GROUPS { 2187 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2189 l2tpv3CfgGroup, 2190 l2tpv3StatsGroup, 2191 l2tpv3TrapGroup 2192 } 2194 -- optional Mapping Group 2195 GROUP l2tpv3MappingGroup 2196 DESCRIPTION 2197 "Optional group for L2TP devices that provide index 2198 mapping." 2200 -- optional Security Group 2201 GROUP l2tpv3SecurityGroup 2202 DESCRIPTION 2203 "Optional group for SNMP agents that support both 2204 authentication and privacy of SNMP messages for the 2205 management of L2TP keys." 2207 -- optional High Capacity Group 2208 GROUP l2tpv3HCPacketGroup 2209 DESCRIPTION 2210 "Optional group for implementations that cannot overflow 2211 the 32-bit packet and byte counters in less than one 2212 hour. Mandatory otherwise." 2214 ::= { l2tpv3Compliances 1 } 2216 l2tpv3MIBReadOnlyCompliance MODULE-COMPLIANCE 2217 STATUS current 2218 DESCRIPTION 2219 "An implementation claims read-only compliance when this 2220 MIB is implemented without support for read-create and 2221 read-write operations (i.e. operates in read-only mode), 2222 thereby allowing monitoring but not configuration." 2224 MODULE -- this module 2226 -- unconditionally mandatory groups 2227 MANDATORY-GROUPS { 2228 l2tpv3CfgGroup, 2229 l2tpv3StatsGroup, 2230 l2tpv3TrapGroup 2231 } 2233 OBJECT l2tpv3StackCfgAdminState 2234 MIN-ACCESS read-only 2235 DESCRIPTION 2236 "Write access is not required." 2238 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2240 OBJECT l2tpv3StackCfgDrain 2241 MIN-ACCESS read-only 2242 DESCRIPTION 2243 "Write access is not required." 2245 OBJECT l2tpv3CtrlCfgRouterID 2246 MIN-ACCESS read-only 2247 DESCRIPTION 2248 "Write access is not required." 2250 OBJECT l2tpv3CtrlCfgTransport 2251 MIN-ACCESS read-only 2252 DESCRIPTION 2253 "Write access is not required." 2255 OBJECT l2tpv3CtrlCfgPWCap 2256 MIN-ACCESS read-only 2257 DESCRIPTION 2258 "Write access is not required." 2260 OBJECT l2tpv3CtrlCfgFallback 2261 MIN-ACCESS read-only 2262 DESCRIPTION 2263 "Write access is not required." 2265 OBJECT l2tpv3CtrlCfgDrain 2266 MIN-ACCESS read-only 2267 DESCRIPTION 2268 "Write access is not required." 2270 OBJECT l2tpv3CtrlCfgAuth 2271 MIN-ACCESS read-only 2272 DESCRIPTION 2273 "Write access is not required." 2275 OBJECT l2tpv3CtrlCfgSecret 2276 MIN-ACCESS read-only 2277 DESCRIPTION 2278 "Write access is not required." 2280 OBJECT l2tpv3CtrlCfgSecurity 2281 MIN-ACCESS read-only 2282 DESCRIPTION 2283 "Write access is not required." 2285 OBJECT l2tpv3CtrlCfgHelloInt 2286 MIN-ACCESS read-only 2288 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2290 DESCRIPTION 2291 "Write access is not required." 2293 OBJECT l2tpv3CtrlCfgRWS 2294 MIN-ACCESS read-only 2295 DESCRIPTION 2296 "Write access is not required." 2298 OBJECT l2tpv3CtrlCfgMaxRetrans 2299 MIN-ACCESS read-only 2300 DESCRIPTION 2301 "Write access is not required." 2303 OBJECT l2tpv3CtrlCfgMaxRetransTO 2304 MIN-ACCESS read-only 2305 DESCRIPTION 2306 "Write access is not required." 2308 OBJECT l2tpv3CtrlCfgReassemblyTO 2309 MIN-ACCESS read-only 2310 DESCRIPTION 2311 "Write access is not required." 2313 OBJECT l2tpv3CtrlCfgIdleTO 2314 MIN-ACCESS read-only 2315 DESCRIPTION 2316 "Write access is not required." 2318 OBJECT l2tpv3SessionCfgLocalID 2319 MIN-ACCESS read-only 2320 DESCRIPTION 2321 "Write/create access is not required." 2323 OBJECT l2tpv3SessionCfgRemoteID 2324 MIN-ACCESS read-only 2325 DESCRIPTION 2326 "Write/create access is not required." 2328 OBJECT l2tpv3SessionCfgCtrlLocalID 2329 MIN-ACCESS read-only 2330 DESCRIPTION 2331 "Write/create access is not required." 2333 OBJECT l2tpv3SessionCfgPWType 2334 MIN-ACCESS read-only 2335 DESCRIPTION 2336 "Write/create access is not required." 2338 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2340 OBJECT l2tpv3SessionCfgEndID 2341 MIN-ACCESS read-only 2342 DESCRIPTION 2343 "Write/create access is not required." 2345 OBJECT l2tpv3SessionCfgAppID 2346 MIN-ACCESS read-only 2347 DESCRIPTION 2348 "Write/create access is not required." 2350 OBJECT l2tpv3SessionCfgPWEncap 2351 MIN-ACCESS read-only 2352 DESCRIPTION 2353 "Write/create access is not required." 2355 OBJECT l2tpv3SessionCfgSeq 2356 MIN-ACCESS read-only 2357 DESCRIPTION 2358 "Write/create access is not required." 2360 OBJECT l2tpv3SessionCfgLocalCookie 2361 MIN-ACCESS read-only 2362 DESCRIPTION 2363 "Write/create access is not required." 2365 OBJECT l2tpv3SessionCfgRemoteCookie 2366 MIN-ACCESS read-only 2367 DESCRIPTION 2368 "Write/create access is not required." 2370 OBJECT l2tpv3SessionCfgCallType 2371 MIN-ACCESS read-only 2372 DESCRIPTION 2373 "Write/create access is not required." 2375 -- optional Mapping Group 2376 GROUP l2tpv3MappingGroup 2377 DESCRIPTION 2378 "Optional group for L2TP devices that provide index 2379 mapping." 2381 OBJECT l2tpv3SessionMapCtrlIfIndex 2382 MIN-ACCESS read-only 2383 DESCRIPTION 2384 "Write access is not required." 2386 OBJECT l2tpv3SessionMapStatus 2387 MIN-ACCESS read-only 2389 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2391 DESCRIPTION 2392 "Write access is not required." 2394 -- optional Security Group 2395 GROUP l2tpv3SecurityGroup 2396 DESCRIPTION 2397 "Optional group for SNMP agents that support both 2398 authentication and privacy of SNMP messages for the 2399 management of L2TP keys." 2401 -- optional High Capacity Group 2402 GROUP l2tpv3HCPacketGroup 2403 DESCRIPTION 2404 "Optional group for implementations that cannot overflow 2405 the 32-bit packet and byte counters in less than one 2406 hour. Mandatory otherwise." 2407 ::= { l2tpv3Compliances 2 } 2409 -- 2410 -- Units of conformance 2411 -- 2412 l2tpv3CfgGroup OBJECT-GROUP 2413 OBJECTS { 2414 l2tpv3StackCfgAdminState, 2415 l2tpv3StackCfgDrain, 2416 l2tpv3CtrlCfgRouterID, 2417 l2tpv3CtrlCfgTransport, 2418 l2tpv3CtrlCfgPWCap, 2419 l2tpv3CtrlCfgFallback, 2420 l2tpv3CtrlCfgDrain, 2421 l2tpv3CtrlCfgAuth, 2422 l2tpv3CtrlCfgSecret, 2423 l2tpv3CtrlCfgSecurity, 2424 l2tpv3CtrlCfgHelloInt, 2425 l2tpv3CtrlCfgRWS, 2426 l2tpv3CtrlCfgMaxRetrans, 2427 l2tpv3CtrlCfgMaxRetransTO, 2428 l2tpv3CtrlCfgReassemblyTO, 2429 l2tpv3CtrlCfgIdleTO, 2430 l2tpv3SessionCfgLocalID, 2431 l2tpv3SessionCfgRemoteID, 2432 l2tpv3SessionCfgCtrlLocalID, 2433 l2tpv3SessionCfgPWType, 2434 l2tpv3SessionCfgEndID, 2435 l2tpv3SessionCfgAppID, 2436 l2tpv3SessionCfgPWEncap, 2437 l2tpv3SessionCfgSeq, 2438 l2tpv3SessionCfgLocalCookie, 2440 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2442 l2tpv3SessionCfgRemoteCookie, 2443 l2tpv3SessionCfgCallType 2444 } 2445 STATUS current 2446 DESCRIPTION 2447 "A collection of objects providing configuration 2448 information of the L2TP stack, its control connections, 2449 and its sessions." 2450 ::= { l2tpv3Groups 1 } 2452 l2tpv3StatsGroup OBJECT-GROUP 2453 OBJECTS { 2454 l2tpv3StackStatsVersion, 2455 l2tpv3StackStatsRevision, 2456 l2tpv3StackStatsVendorName, 2457 l2tpv3StackStatsAdminState, 2458 l2tpv3StackStatsIsDraining, 2459 l2tpv3StackStatsNumCtrlEst, 2460 l2tpv3StackStatsNumSessEst, 2461 l2tpv3CtrlStatsLocalID, 2462 l2tpv3CtrlStatsRemoteID, 2463 l2tpv3CtrlStatsState, 2464 l2tpv3CtrlStatsIsDraining, 2465 l2tpv3CtrlStatsInitiated, 2466 l2tpv3CtrlStatsRemoteRouterID, 2467 l2tpv3CtrlStatsRemoteHostName, 2468 l2tpv3CtrlStatsRemoteVendorName, 2469 l2tpv3CtrlStatsRemoteVersion, 2470 l2tpv3CtrlStatsRemotePWCap, 2471 l2tpv3CtrlStatsInitialRemoteRWS, 2472 l2tpv3CtrlStatsCtrlRxZLB, 2473 l2tpv3CtrlStatsCtrlOutOfSeq, 2474 l2tpv3CtrlStatsCtrlOutOfWindow, 2475 l2tpv3CtrlStatsCtrlTxZLB, 2476 l2tpv3CtrlStatsCtrlAckTO, 2477 l2tpv3CtrlStatsCurrentRemoteRWS, 2478 l2tpv3CtrlStatsTxSeq, 2479 l2tpv3CtrlStatsRxSeq, 2480 l2tpv3CtrlStatsNumSessCumEst, 2481 l2tpv3CtrlStatsNumSessCurrentEst, 2482 l2tpv3CtrlStatsNumSessFailed, 2483 l2tpv3CtrlStatsLastResultCode, 2484 l2tpv3CtrlStatsLastErrorCode, 2485 l2tpv3CtrlStatsLastErrorMessage, 2486 l2tpv3CtrlStatsCtrlRxOctets, 2487 l2tpv3CtrlStatsCtrlRxPkts, 2488 l2tpv3CtrlStatsCtrlTxOctets, 2489 l2tpv3CtrlStatsCtrlTxPkts, 2491 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2493 l2tpv3CtrlStatsDataRxOctets, 2494 l2tpv3CtrlStatsDataRxPkts, 2495 l2tpv3CtrlStatsDataRxDrops, 2496 l2tpv3CtrlStatsDataTxOctets, 2497 l2tpv3CtrlStatsDataTxPkts, 2498 l2tpv3SessionStatsRemoteEndID, 2499 l2tpv3SessionStatsRemoteAppID, 2500 l2tpv3SessionStatsRemotePWEncap, 2501 l2tpv3SessionStatsRemoteSeq, 2502 l2tpv3SessionStatsState, 2503 l2tpv3SessionStatsCircuitStatus, 2504 l2tpv3SessionStatsSerialNumber, 2505 l2tpv3SessionStatsRxConnectSpeed, 2506 l2tpv3SessionStatsTxConnectSpeed, 2507 l2tpv3SessionStatsPhysChannelID, 2508 l2tpv3SessionStatsPrivateGroupID, 2509 l2tpv3SessionStatsOutOfSeq, 2510 l2tpv3SessionStatsReassemblyTO, 2511 l2tpv3SessionStatsTxSeq, 2512 l2tpv3SessionStatsRxSeq, 2513 l2tpv3SessionStatsRxOctets, 2514 l2tpv3SessionStatsRxPkts, 2515 l2tpv3SessionStatsRxDrops, 2516 l2tpv3SessionStatsTxOctets, 2517 l2tpv3SessionStatsTxPkts 2518 } 2519 STATUS current 2520 DESCRIPTION 2521 "A collection of objects providing status and statistics 2522 of the L2TP stack, its control connections, and its 2523 sessions." 2524 ::= { l2tpv3Groups 2 } 2526 l2tpv3MappingGroup OBJECT-GROUP 2527 OBJECTS { 2528 l2tpv3CtrlMapIfIndex, 2529 l2tpv3SessionMapCtrlIfIndex, 2530 l2tpv3SessionMapLocalID, 2531 l2tpv3SessionMapStatus 2532 } 2533 STATUS current 2534 DESCRIPTION 2535 "A collection of objects providing index mapping." 2536 ::= { l2tpv3Groups 3 } 2538 l2tpv3SecurityGroup OBJECT-GROUP 2539 OBJECTS { 2540 l2tpv3CtrlCfgAuth, 2542 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2544 l2tpv3CtrlCfgSecret, 2545 l2tpv3CtrlCfgSecurity 2546 } 2547 STATUS current 2548 DESCRIPTION 2549 "A collection of objects providing L2TP security 2550 configuration." 2551 ::= { l2tpv3Groups 4 } 2553 l2tpv3TrapGroup NOTIFICATION-GROUP 2554 NOTIFICATIONS { 2555 l2tpv3CtrlAuthFailure 2556 } 2557 STATUS current 2558 DESCRIPTION 2559 "A collection of L2TP trap events as specified in 2560 NOTIFICATION-TYPE constructs." 2561 ::= { l2tpv3Groups 5 } 2563 l2tpv3HCPacketGroup OBJECT-GROUP 2564 OBJECTS { 2565 l2tpv3CtrlStatsCtrlHCRxOctets, 2566 l2tpv3CtrlStatsCtrlHCRxPkts, 2567 l2tpv3CtrlStatsCtrlHCTxOctets, 2568 l2tpv3CtrlStatsCtrlHCTxPkts, 2569 l2tpv3CtrlStatsDataHCRxOctets, 2570 l2tpv3CtrlStatsDataHCRxPkts, 2571 l2tpv3CtrlStatsDataHCRxDrops, 2572 l2tpv3CtrlStatsDataHCTxOctets, 2573 l2tpv3CtrlStatsDataHCTxPkts, 2574 l2tpv3SessionStatsHCRxOctets, 2575 l2tpv3SessionStatsHCRxPkts, 2576 l2tpv3SessionStatsHCRxDrops, 2577 l2tpv3SessionStatsHCTxOctets, 2578 l2tpv3SessionStatsHCTxPkts 2579 } 2580 STATUS current 2581 DESCRIPTION 2582 "A collection of objects providing high-capacity 64-bit 2583 counter objects." 2584 ::= { l2tpv3Groups 6 } 2586 END 2587 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2589 5. Security Considerations 2591 It is clear that the MIB modules described in this document in 2592 useful for monitoring of L2TPv3 routers. These MIB modules can also 2593 be used for configuration of certain objects, and anything that can 2594 be configured can be incorrectly configured, with potentially 2595 disastrous results. 2597 There are a number of management objects defined in these MIB modules 2598 with a MAX-ACCESS clause of read-write and/or read-create. Such 2599 objects may be considered sensitive or vulnerable in some network 2600 environments. The support for SET operations in a non-secure 2601 environment without proper protection can have a negative effect on 2602 network operations. These are the tables and objects and their 2603 sensitivity/vulnerability: 2605 6. IANA Considerations 2607 -- (Note to RFC-Editor:) 2608 -- We request that you assign contiguous RFC numbers to the 2609 -- IANA is requested to root MIB objects in the MIB module 2610 -- contained in this document under the transmission subtree. 2611 -- 2613 7. References 2614 7.1 Normative Referneces 2616 [L2TP-BASE] Townsley, et. al. "Layer Two Tunneling Protocol 2617 (Version 3) 'L2TPv3'", STD 15, RFC 3931, March 2005. 2619 [L2TP-MIB] Caves, E., Calhoun, P., and Wheeler, R., 2620 "Layer Two Tunneling Protocol 'L2TP' Management 2621 Information Base", STD 4, RFC 3371, August 2002. 2623 [PWE3-PW-MIB] Zelig, D., Nadeau, T., Danenberg, D., and Mantin, S., 2624 "Pseudo Wire (PW) Management Information Base", 2625 , June 2006. 2627 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2628 MIB", RFC 2863, June 2000. 2630 7.2. Informative References 2632 [RFC1155] Rose, M., and McCloghrie, K., "Structure and 2633 Identification of Management Information for TCP/IP- 2634 Based Internets", STD 16, RFC 1155, May 1990. 2636 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and Davin, J., 2637 "Simple Network Management Protocol", STD 15, RFC 1157, 2638 May 1990. 2640 [RFC1212] Rose, M., and McCloghrie, K., "Concise MIB Definitions", 2641 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2643 STD 16, RFC 1212, March 1991. 2645 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 2646 the SNMP", RFC 1215, March 1991. 2648 [RFC1901] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 2649 "Introduction to Community-based SNMPv2", RFC 1901, 2650 January 1996. 2652 [RFC1905] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 2653 "Protocol Operations for Version 2 of the Simple Network 2654 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2656 [RFC1906] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 2657 "Transport Mappings for Version 2 of the Simple Network 2658 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2660 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2661 Requirement Levels", BCP 14, RFC 2119, March 1997. 2663 [RFC2570] Case, J., Mundy, R., Partain, D., and Stewart, B., 2664 "Introduction to Version 3 of the Internet-standard 2665 Network Management Framework", RFC 2570, April 1999. 2667 [RFC2571] Harrington, D., Presuhn, R., and Wijnen, B., 2668 "An Architecture for Describing SNMP Management 2669 Frameworks", RFC 2571, April 1999. 2671 [RFC2572] Case, J., Harrington D., Presuhn R., and Wijnen, B., 2672 "Message Processing and Dispatching for the Simple 2673 Network Management Protocol (SNMP)", RFC 2572, 2674 April 1999. 2676 [RFC2573] Levi, D., Meyer, P., and Stewart, B., "SNMPv3 2677 Applications", RFC 2573, April 1999. 2679 [RFC2574] Blumenthal, U., and Wijnen, B., "User-based Security Model 2680 (USM) for version 3 of the Simple Network Management 2681 Protocol (SNMPv3)", RFC 2574, April 1999. 2683 [RFC2575] Wijnen, B., Presuhn, R., and McCloghrie, K., "View-based 2684 Access Control Model (VACM) for the Simple Network 2685 Management Protocol (SNMP)", RFC 2575, April 1999. 2687 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2688 Rose, M., and Waldbusser, S., "Structure of Management 2689 Information Version 2 (SMIv2)", STD 58, RFC 2578, 2690 April 1999. 2692 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2694 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2695 Rose, M., and Waldbusser, S., "Textual Conventions for 2696 SMIv2", STD 58, RFC 2579, April 1999. 2698 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2699 Rose, M., and Waldbusser, S., "Conformance Statements for 2700 SMIv2", STD 58, RFC 2580, April 1999. 2702 [RFC2667] Thaler, D., "IP Tunnel MIB", RFC 2667, Microsoft, 2703 August 1999. 2705 8. Authors' Addresses 2707 Evan Caves 2708 Occam Networks 2709 77 Robin Hill Road 2710 Santa Barbara, CA 93117 2711 evan@occamnetworks.com 2713 Walter Klausberger 2714 Siemens AG 2715 Vienna, Austria 2716 walter.klausberger@siemens.com 2718 Jed Lau 2719 jedlau@gmail.com 2721 Thomas D. Nadeau 2722 Cisco Systems, Inc. 2723 1414 Massachusetts Ave. 2724 Boxborough, MA 01719 2725 Email: tnadeau@cisco.com 2727 A S Kiran Koushik 2728 cisco Systems, Inc. 2729 12515 Research Blvd, Bldg 4 2730 Austin, TX 78759 2731 kkoushik@cisco.com 2733 Carlos Pignataro 2734 cisco Systems, Inc. 2735 7025-1 Kit Creek Rd 2736 PO Box 14987 2737 Research Triangle Park, NC 27709-4987 2738 cpignata@cisco.com 2739 draft-ietf-l2tpext-l2tpmib-base-02 L2TPv3-MIB August 30, 2006 2741 9. Intellectual Property Considerations 2743 The IETF takes no position regarding the validity or scope of any 2744 Intellectual Property Rights or other rights that might be claimed to 2745 pertain to the implementation or use of the technology described in 2746 this document or the extent to which any license under such rights 2747 might or might not be available; nor does it represent that it has 2748 made any independent effort to identify any such rights. Information 2749 on the procedures with respect to rights in RFC documents can be 2750 found in BCP 78 and BCP 79. 2752 Copies of IPR disclosures made to the IETF Secretariat and any 2753 assurances of licenses to be made available, or the result of an 2754 attempt made to obtain a general license or permission for the use of 2755 such proprietary rights by implementers or users of this 2756 specification can be obtained from the IETF on-line IPR repository at 2757 http://www.ietf.org/ipr. 2759 The IETF invites any interested party to bring to its attention any 2760 copyrights, patents or patent applications, or other proprietary 2761 rights that may cover technology that may be required to implement 2762 this standard. Please address the information to the IETF at ietf- 2763 ipr@ietf.org. 2765 10. Full Copyright Statement 2767 Copyright (C) The Internet Society (2006). This document is subject 2768 to the rights, licenses and restrictions contained in BCP 78, and 2769 except as set forth therein, the authors retain all their rights. 2771 This document and the information contained herein are provided on an 2772 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2773 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2774 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2775 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2776 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2777 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.