idnits 2.17.1 draft-ietf-pppext-l2tp-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-24) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 48 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 360: '...s below, all objects MUST be supported...' RFC 2119 keyword, line 377: '... interfaces MUST be supported as described in [17]....' RFC 2119 keyword, line 882: '...be discarded (which MAY causes the PPP...' RFC 2119 keyword, line 1342: '... (which MAY causes the PPP de...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1978 has weird spacing: '...to this sessi...' == Unrecognized Status in 'Category: Internet Draft', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '15') (Obsoleted by RFC 2575) == Outdated reference: A later version (-16) exists of draft-ietf-pppext-l2tp-10 -- Possible downref: Non-RFC (?) normative reference: ref. '17' -- Possible downref: Non-RFC (?) normative reference: ref. '18' Summary: 24 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PPP Working Group Pat R. Calhoun 3 INTERNET DRAFT Sun Microsystems, Inc. 4 Category: Internet Draft Gayam Reddy 5 Title: draft-ietf-pppext-l2tp-mib-03.txt Bill Vroman 6 Date: November 1998 3Com Corporation 7 Ross Wheeler 8 RouterWare 9 Evan Caves 10 ACC 12 Layer Two Tunneling Protocol "L2TP" 13 Management Information Base 14 16 Status of this Memo 18 This document is an Internet-Draft. Internet-Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its areas, 20 and its working groups. Note that other groups may also distribute 21 work ing documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months. Internet-Drafts may be updated, replaced, or obsoleted by 25 other documents at any time. It is not appropriate to use Internet- 26 Drafts as reference material or to cite them other than as a 27 ``working draft'' or ``work in progress.'' 29 To learn the current status of any Internet-Draft, please check the 30 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 31 Directories on ds.internic.net, nic.nordu.net, ftp.nisc.sri.com, or 32 munnari.oz.au. 34 Abstract 36 This memo defines a portion of the Management Information Base (MIB) 37 for use with network management protocols in TCP/IP-based internets. 38 In particular, it defines objects for managing networks using Layer 2 39 Tunneling Protocol. 41 This memo specifies a MIB module in a manner that is both compliant 42 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 43 definitions. 45 Table of Contents 47 1.0 Introduction ......................................... 2 48 1.1 Change Log ............................................. 1 50 2.0 The SNMP Management Framework .......................... 4 52 3.0 Overview ............................................... 5 53 3.1 Relationship to the Interface MIB ...................... 6 54 3.1.1 Layering Model ....................................... 6 55 3.1.2 Interface MIB Objects ................................ 9 56 3.1.2.1 L2TP Tunnel Interfaces ............................. 9 57 3.2 Relationship to other MIBs ............................. 11 58 3.2.1 Relationship to the IP Tunnel MIB .................... 11 59 3.3 L2TP Tunnel Creation ................................... 11 61 4.0 L2TP Object Definitions ................................ 12 63 5.0 Acknowledgements ....................................... 69 65 6.0 References ............................................. 69 67 7.0 Authors' Addresses ..................................... 68 69 1.0 Introduction 71 This memo defines a portion of the Management Information Base (MIB) 72 for use with network management protocols in the Internet Community. 73 In particular, it describes managed objects used for managing L2TP 74 devices. 76 1.1 Change Log 78 This section tracks changes made to the revisions of the Internet 79 Drafts of this document. It will be *deleted* when the document is 80 published as an RFC. 82 3 November 1997 84 The following changes were made for the version of the document dated 85 3 November 1997. These changes were made at the request of the L2TP 86 working group. 88 (1) Removed L2TP protocol stack instancing. 90 (2) Tunnel and Session table now extensions of ifTable. 92 (3) Added IP/UDP transport tables. 94 (4) Several objects were removed and a number of new 95 objects added. 97 (5) Sections 1.1, 2.1, 3.0, 5.0 and 6.0 added. 99 (6) Module Compliance information added. 101 27 July 1998 103 The following changes were made for the version of the document dated 104 27 July 1998. These changes were made as a result of the L2TP MIB 105 presentation during the forty-first IETF in Los Angeles. 107 (1) Added Tunnel Domain configuration and stats tables. 109 (2) Moved most of the scalar configuration and stats objects 110 into the Tunnel Domain tables. 112 (3) Redundant objects removed. 114 (4) Some re-organization and object naming clarifications. 116 (5) Updated section 2.0 118 (6) Introduction of L2TP notifications 120 (7) Removed l2tpUdpConfigTable in favour of the tunnelConfigTable 122 (8) Updated section 3.0 124 3 November 1998 126 The following changes were made for the version of the document dated 127 3 Novemer 1998. These changes were made as a result of the L2TP MIB 128 presentation during the forty-second IETF in Chicago. 130 1) A PPP session within a tunnel is no longer represented as a 131 seperate interface that is visible in the ifTable. 133 2) The Layering Model in section 3.1.1 has been updated to 134 reflect that sessions are not seperate interfaces. 136 3) Section 3.1.2.2 'L2TP Session Interfaces' has been removed. 138 4) Tunnel authentication shared secret objects have been added 139 to the l2tpDomainConfigTable and l2tpTunnelConfigTable. 141 5) The l2tpSessionStatsTable indexing has changed to reflect 142 that sessions are not seperate interfaces. 144 6) A mapping table has been added to assist management 145 applications in quickly locating session statistics. 147 7) The objects l2tpUdpStatsAddressChanges and 148 l2tpUdpStatsPortChanges have been removed. 150 8) The l2tpUdpAddressingChange notification has been 151 removed. 153 9) Updated tunnel/session Bearer and Framing capability 154 object enumerations. 156 2.0 The SNMP Management Framework 158 The SNMP Management Framework presently consists of five major 159 components: 161 o An overall architecture, described in RFC 2271 [1]. 163 o Mechanisms for describing and naming objects and 164 events for the purpose of management. The first 165 version of this Structure of Management Information 166 (SMI) is called SMIv1 and described in RFC 1155 [2], 167 RFC 1212 [3] and RFC 1215 [4]. The second version, 168 called SMIv2, is described in RFC 1902 [5], 169 RFC 1903 [6] and RFC 1904 [7]. 171 o Message protocols for transferring management 172 information. The first version of the SNMP 173 message protocol is called SNMPv1 and described in 174 RFC 1157 [8]. A second version of the SNMP message 175 protocol, which is not an Internet standards track 176 protocol, is called SNMPv2c and described in 177 RFC 1901 [9] and RFC 1905 [13]. The third version 178 of the message protocol is called SNMPv3 and 179 described in RFC 1906 [10], RFC 2272 [11] and 180 RFC 2274 [12]. 182 o Protocol operations for accessing management 183 information. The first set of protocol operations 184 and associated PDU formats is described in 185 RFC 1157 [8]. A second set of protocol operations 186 and associated PDU formats is described in 187 RFC 1905 [13]. 189 o A set of fundamental applications described in 190 RFC 2273 [14] and the view-based access control 191 mechanism described in RFC 2275 [15]. 193 Managed objects are accessed via a virtual information store, termed 194 the Management Information Base or MIB. Objects in the MIB are 195 defined using the mechanisms defined in the SMI. 197 This memo specifies a MIB module that is compliant to the SMIv2. A 198 MIB conforming to the SMIv1 can be produced through the appropriate 199 translations. The resulting translated MIB must be semantically 200 equivalent, except where objects or events are omitted because no 201 translation is possible (e.g., use of Counter64). Some machine 202 readable information in SMIv2 will be converted into textual 203 descriptions in SMIv1 during the translation process. However, this 204 loss of machine readable information is not considered to change the 205 semantics of the MIB. 207 3.0 Overview 209 The objects defined in this MIB are to be used when describing Layer 210 Two Tunneling Protocol (L2TP) tunnels. The L2TP protocol is defined 211 in [16]. This MIB consists of four groups briefly described below: 213 l2tpConfigGroup 214 l2tpStatsGroup 215 These two groups of objects provide information on the configuration, 216 state and statistics of the L2TP protocol, its tunnels and sessions. 217 These groups are mandatory for implementors of this MIB. 219 l2tpDomainGroup 220 This optional group of objects provides configuration, state and 221 statistical information for L2TP tunnel endpoint domains. A L2TP 222 tunnel endpoint domain is considered to be a collection of L2TP 223 devices typically belonging to a common administrative domain or 224 geographic location. 226 l2tpMappingGroup 227 This optional group contains mapping tables to assist management 228 applications to map between protocol identifiers and table indeces. 230 l2tpIpUdpGroup 231 This group provides the state and statistics information for L2TP 232 tunnels which are being transported by IP/UDP. This group is 233 mandatory for L2TP implementations that support L2TP over IP/UDP. 235 3.1 Relationship to the Interface MIB 237 This section clarifies the relationship of this MIB to the Interfaces 238 MIB [17]. Several areas of correlation are addressed in the following 239 subsections. The implementor is referred to the Interfaces MIB document 240 in order to understand the general intent of these areas. 242 3.1.1 Layering Model 244 This MIB contains several tables which are extensions to the IP 245 Tunnel MIB described in [18] which itself defines extensions to 246 the Interface MIB [17]. A L2TP tunnel is represented as a separate 247 identifiable logical interface sub-layer. The tunnel 248 interface appear in the ifStackTable at different sub-layers 249 depending on the functionality the tunnel endpoint is providing. 251 At the LAC end of a tunnel endpoint the tunnel interface appears 252 above the session interfaces. At the LNS end of a tunnel endpoint 253 the tunnel interface appears below the session interfaces. 255 In the example diagram below, the interface layering is shown as it 256 appears at the LNS. Note that the L2TP tunnel interface is at the 257 bottom of the interface stack when the transport layer for L2TP is 258 IP/UDP. This is because tunneled traffic is forwarded to its 259 destination based on routing policy. However L2TP over transports 260 other than IP/UDP may define further sub-layer interfaces below 261 the tunnel interface. 263 +-------------------------------------------------+ 264 | Network Layer Protocol | 265 +-------------+-------------+--------+------------+ 266 | | | 267 +-+--+ | | 268 |MPPP| | | <=== PPP Multilink I/F 269 ++--++ | | 270 | | | | 271 +--+ +--+ | | 272 | | | | 273 +-+-+ +-+-+ +-+-+ +-+-+ 274 |PPP| |PPP| |PPP| |PPP| <=== PPP I/F 275 +-+-+ +-+-+ +-+-+ +-+-+ 276 | | | | 277 +---------+--------+--------+--------+------------+ 278 | L2TP Tunnel I/F | 279 +-------------------------------------------------+ 281 The ifStackTable is used to describe the layering of the interface 282 sub-layers. For the example given above the ifTable and ifStackTable 283 may appear as follows: 285 ifIndex ifType Tunnel MIB tables Description 287 1 tunnel(131) tunnelIfTable Tunnel interface 288 l2tpTunnelConfigTable 289 l2tpTunnelStatsTable 290 2 ppp(23) PPP interface #1 291 3 ppp(23) PPP interface #2 292 4 ppp(23) PPP interface #3 293 5 ppp(23) PPP interface #4 294 6 mlppp(108) MLPPP interface 296 The corresponding ifStack table entries would then be: 298 ifStackTable Entries 300 HigherLayer LowerLayer 301 0 4 302 0 5 303 0 6 304 1 0 305 2 1 306 3 1 307 4 1 308 5 1 309 6 2 310 6 3 312 The following example diagram illustrates the interface layering as 313 it might occur at the LAC. In this case the tunnel interface is at 314 the top of the interface stack for L2TP over IP/UDP. 316 +-------------------------------------------------+ 317 | L2TP Tunnel I/F | 318 +---------+--------+--------+--------+------------+ 319 | | | | 320 +-+-+ +-+-+ +-+-+ +-+-+ 321 |ds0| |ds0| |ds0| |ds0| <=== B channels I/F 322 +-+-+ +-+-+ +-+-+ +-+-+ 323 | | | | 324 +---------+--------+--------+--------+------------+ 325 | ds1 | 326 +-------------------------------------------------+ 328 For the example given above the ifTable and ifStackTable may appear 329 as follows: 331 ifIndex ifType Tunnel MIB tables Description 333 1 ds1(18) Primary Rate physical interface 334 2 ds0(81) B channel #1 335 3 ds0(81) B channel #2 336 4 ds0(81) B channel #3 337 5 ds0(81) B channel #4 338 6 tunnel(131) tunnelIfTable Tunnel Interface 339 l2tpTunnelConfigTable 340 l2tpTunnelStatsTable 342 The corresponding ifStack table entries would then be: 344 ifStackTable Entries 346 HigherLayer LowerLayer 347 0 6 348 1 0 349 2 1 350 3 1 351 4 1 352 5 1 353 6 2 354 6 3 355 6 4 356 6 5 358 3.1.2 Interface MIB Objects 360 Except where noted in the tables below, all objects MUST be supported 361 from the ifGeneralInformationGroup and one of the following three groups: 363 o ifPacketGroup OR 364 o ifHCPacketGroup OR 365 o ifVHCPacketGroup 367 depending on the particular implementation. 369 The following tables describe how objects from the ifGeneralInformationGroup 370 and ifPacketGroup (similar support should be provided for the high and very 371 high capacity packet groups) are to be interpreted and supported for L2TP 372 tunnel interfaces. 374 3.1.2.1 L2TP Tunnel Interfaces 376 All Interface MIB objects not listed in the above groups for L2TP tunnel 377 interfaces MUST be supported as described in [17]. 379 Interface MIB Object Support Description 380 ==================== ======================================= 381 ifTable.ifDescr Refer to the Interface MIB. 383 ifTable.ifType tunnel(131) 385 ifTable.ifMtu Dependant on the tunnel transport layer. 386 For IP/UDP transports the MTU should 387 be 65467 (65535-60(IP)-8(UDP)) 389 ifTable.ifSpeed Return zero. 391 ifTable.ifPhyAddress The assigned tunnel identifier. 393 ifTable.ifAdminStatus All enumerated values supported as per 394 DESCRIPTION clause in the Interfaces MIB. 396 ifTable.ifOperStatus All status events supported. Refer to the 397 Interfaces MIB. 399 ifTable.ifInOctets The total number of octets received on the 400 tunnel including control and payload 401 octets. 403 ifTable.ifInUcastPkts The total number of packets received on 404 the tunnel including control and payload 405 packets. 407 ifTable.ifInDiscards The total number of received packets that 408 were discarded on both control and payload 409 channels. 411 ifTable.ifInErrors The total number of packets received in 412 error including control and payload 413 packets. 415 ifTable.ifInUnknownProtos 416 Return zero. 418 ifTable.ifOutOctets The total number of octets transmitted from 419 the tunnel including control and payload 420 octets. 422 ifTable.ifOutUcastPkts The total number of packets transmitted from 423 the tunnel including control and payload 424 packets. 426 ifTable.ifOutDiscards The total number of discarded packets that 427 were requested to be transmitted including 428 control and payload packets. 430 ifTable.ifOutErrors The total number of packets that were requested 431 to be transmitted that were in error including 432 control and payload packets. 434 ifXTable.ifName Refer to the Interface MIB. 436 ifXTable.ifInMulticastPkts 437 Return zero. 439 ifXTable.ifInBroadcastPkts 440 Return zero. 442 ifXTable.ifOutMulticastPkts 443 Return zero. 445 ifXTable.ifOutBroadcastPkts 446 Return zero. 448 ifXTable.ifOutBroadcastPkts 449 Return zero. 451 ifXTable.ifLinkUpDownTrapEnable 452 Default set to enabled(1). 454 ifXTable.ifHighSpeed Return zero. 456 ifXTable.ifPromiscuousMode 457 Set to false(2). 459 ifXTable.ifConnectorPresent 460 Set to false(2). 462 3.2 Relationship to other MIBs 464 3.2.1 Relationship to the IP Tunnel MIB 466 The IP Tunnel MIB [18] describes tunnel interfaces that have an ifType 467 of tunnel(131). The IP Tunnel MIB is considered to contain a collection of 468 objects common to all IP tunneling protocols, including L2TP. In addition 469 to the IP Tunnel MIB, tunnel encapsulation specific MIBs (like this MIB) 470 extend the IP Tunnel MIB to further describe encapsulation specific 471 information. Implementation of the IP Tunnel MIB is required for L2TP 472 tunnels over IP. 474 3.3 L2TP Tunnel Creation 476 Tunnel creation is detailed for IP tunnels in the IP Tunnel MIB. The 477 creation of a tunnelIfEntry in [18] will have the side affect of 478 creating entries in the l2tpTunnelConfigTable, l2tpTunnelStatsTable 479 and the l2tpUdpStatsTable's. 481 The creation of L2TP tunnel interfaces over transports other than IP 482 is expected to be defined in the MIB definition for that specific 483 L2TP tunnel transport. 485 4.0 L2TP Object Definitions 487 L2TP-MIB DEFINITIONS ::= BEGIN 489 IMPORTS 490 Integer32, Counter32, experimental, Gauge32, 491 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE 492 FROM SNMPv2-SMI 493 TEXTUAL-CONVENTION, DisplayString, RowStatus, TruthValue 494 FROM SNMPv2-TC 495 OBJECT-GROUP, MODULE-COMPLIANCE 496 FROM SNMPv2-CONF 497 InterfaceIndex 498 FROM IF-MIB; 500 l2tp MODULE-IDENTITY 501 LAST-UPDATED "9811181800Z" 502 ORGANIZATION "IETF L2TP Working Group" 503 CONTACT-INFO 504 "Bill Vroman, Gayam Reddy 505 Postal: 3Com Corporation 506 1800 W. Central Rd 507 Mt. Prospect, IL 60056-2293 508 Tel: +1 847222 2008 509 +1 847222 2006 510 Email: bvroman, greddy@usr.com 512 Ross Wheeler 513 Postal: RouterWare 514 3961 MacArthur Blvd, Suite 212 515 Newport Beach, CA 92660 516 Tel: +1 714442 0770 517 Email: ross@routerware.com 519 Pat R. Calhoun 520 Postal: Sun Microsystems, Inc. 521 15 Network Circle 522 Menlo Park, CA, 94025 523 Tel: +1 650786 7733 524 Email: pcalhoun@eng.sun.com 526 Evan Caves 527 Postal: Advanced Computer Communications 528 340 Storke Road 529 Santa Barbara, CA 93117 530 Tel: +1 805685 4455 531 Email: evan@acc.com" 532 DESCRIPTION 533 "The MIB module that describes managed objects of 534 general use by the Layer Two Transport Protocol." 535 ::= { experimental 9999 1 } 537 -- 538 -- Textual Conventions 539 -- 541 MilliSeconds ::= TEXTUAL-CONVENTION 542 DISPLAY-HINT "d-3" 543 STATUS current 544 DESCRIPTION 545 "A period of time measured in units of .001 of seconds 546 when used in conjunction with the DISPLAY-HINT will 547 show seconds and fractions of second with a resolution 548 of .001 of a second." 549 SYNTAX Integer32 (0..2147483646) 551 -- 552 -- Definitions of significant branches 553 -- 554 l2tpObjects OBJECT IDENTIFIER ::= { l2tp 1 } 555 l2tpTraps OBJECT IDENTIFIER ::= { l2tp 2 } 556 l2tpTransports OBJECT IDENTIFIER ::= { l2tp 3 } 557 l2tpConformance OBJECT IDENTIFIER ::= { l2tp 4 } 559 -- 560 -- Definitions of significant branches under l2tpObjects 561 -- 562 l2tpScalar OBJECT IDENTIFIER ::= { l2tpObjects 1 } 563 l2tpConfig OBJECT IDENTIFIER ::= { l2tpScalar 1 } 564 l2tpStats OBJECT IDENTIFIER ::= { l2tpScalar 2 } 566 -- 567 -- Definitions of significant branches under l2tpTransports 568 -- 569 l2tpTransportIpUdp OBJECT IDENTIFIER ::= { l2tpTransports 1 } 570 l2tpIpUdpObjects OBJECT IDENTIFIER ::= { l2tpTransportIpUdp 1 } 571 l2tpIpUdpTraps OBJECT IDENTIFIER ::= { l2tpTransportIpUdp 2 } 572 -- 573 -- The L2TP Scalar Configuration Group 574 -- 575 -- This group of objects is used to manage configuration 576 -- of the L2TP protocol environment. 578 l2pAdminState OBJECT-TYPE 579 SYNTAX INTEGER { 580 enabled(1), 581 disabled(2), 582 drain(3) 583 } 584 MAX-ACCESS read-write 585 STATUS current 586 DESCRIPTION 587 "This object defines the administrative state of 588 this L2TP tunnel domain. Setting this object to 589 'disabled' causes all tunnels to be immediately 590 disconnected and no further tunnels to be either 591 initiated or accepted. Setting this object to 592 'drain' will prevent any new tunnels and/or 593 sessions to be either initiated or accepted but 594 does NOT disconnect any active tunnels/sessions." 595 DEFVAL { enabled } 596 ::= { l2tpConfig 1 } 598 -- 599 -- The L2TP Scalar Status and Statistics Group 600 -- 601 -- This group of objects describe the current state and 602 -- statistics of L2TP. 604 l2tpProtocolVersion OBJECT-TYPE 605 SYNTAX OCTET STRING (SIZE(2..256)) 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 609 "Vector of supported L2TP protocol version and 610 revision numbers. Supported versions are identified 611 via a two octet pairing where the first octet indicates 612 the version and the second octet contains the revision." 613 ::= { l2tpStats 1 } 615 l2tpVendorName OBJECT-TYPE 616 SYNTAX DisplayString 617 MAX-ACCESS read-only 618 STATUS current 619 DESCRIPTION 620 "This object identifies the Vendor name of the L2TP 621 protocol stack." 622 ::= { l2tpStats 2 } 624 l2tpFirmwareRev OBJECT-TYPE 625 SYNTAX Integer32 626 MAX-ACCESS read-only 627 STATUS current 628 DESCRIPTION 629 "This object defines the firmware revision for the 630 L2TP protocol stack." 631 ::= { l2tpStats 3 } 633 -- 634 -- The L2TP Domain Configuration Table 635 -- 636 -- This table contains objects that can be used to 637 -- configure the operational characteristics of a tunnel 638 -- domain. 640 l2tpDomainConfigTable OBJECT-TYPE 641 SYNTAX SEQUENCE OF L2tpDomainConfigEntry 642 MAX-ACCESS not-accessible 643 STATUS current 644 DESCRIPTION 645 "The L2TP Domain configuration table." 646 ::= { l2tpObjects 2 } 648 l2tpDomainConfigEntry OBJECT-TYPE 649 SYNTAX L2tpDomainConfigEntry 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "An L2TP Domain configuration entry. An entry in this 654 table may correspond to a single endpoint or a group 655 of tunnel endpoints." 656 INDEX { l2tpDomainConfigIdentifier } 657 ::= { l2tpDomainConfigTable 1 } 659 L2tpDomainConfigEntry ::= 660 SEQUENCE { 661 l2tpDomainConfigIdentifier 662 DisplayString, 663 l2pDomainConfigAdminState 664 INTEGER, 665 l2tpDomainConfigAuthentication 666 INTEGER, 667 l2tpDomainConfigSecret 668 OCTET STRING, 669 l2tpDomainConfigTunnelSecurity 670 INTEGER, 671 l2tpDomainConfigTunnelHelloInterval 672 Integer32, 673 l2tpDomainConfigTunnelIdleTimeout 674 Integer32, 675 l2tpDomainConfigControlRWS 676 Integer32, 677 l2tpDomainConfigControlRetransmissions 678 Integer32, 679 l2tpDomainConfigPayloadSequencing 680 TruthValue, 682 l2tpDomainConfigPayloadRWS 683 Integer32, 684 l2tpDomainConfigDelayedAckTimeout 685 MilliSeconds, 686 l2tpDomainConfigReassemblyTimeout 687 MilliSeconds, 688 l2tpDomainConfigStatus 689 RowStatus 690 } 692 l2tpDomainConfigIdentifier OBJECT-TYPE 693 SYNTAX DisplayString 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "The identifier, usually in the form of a Domain 698 Name (full or partial), describing a single tunnel 699 endpoint or a domain of tunnel endpoints. This is 700 typically used as a 'handle' to identify the 701 tunnel configuration requirements for both incoming 702 and outgoing tunnel connection attempts. Both the 703 LAC and LNS could use information provided in the 704 Host Name AVP however the tunnel initiator could use 705 other means not specified to identify the domains 706 tunnel configuration requirements." 707 ::= { l2tpDomainConfigEntry 1 } 709 l2pDomainConfigAdminState OBJECT-TYPE 710 SYNTAX INTEGER { 711 enabled(1), 712 disabled(2), 713 drain(3) 714 } 715 MAX-ACCESS read-create 716 STATUS current 717 DESCRIPTION 718 "This object defines the administrative state of this 719 tunnel domain. Setting this object to disabled(2) 720 causes all tunnels to be immediately disconnected 721 and no further tunnels to be either initiated or 722 accepted. Setting this object to drain(3) will prevent 723 any new tunnels and/or sessions to be either initiated 724 or accepted but does NOT forcibly disconnect any 725 active tunnels and/or sessions." 726 DEFVAL { enabled } 727 ::= { l2tpDomainConfigEntry 2 } 729 l2tpDomainConfigAuthentication OBJECT-TYPE 730 SYNTAX INTEGER { 731 none(1), 732 simple(2), 733 challenge(3) 734 } 735 MAX-ACCESS read-create 736 STATUS current 737 DESCRIPTION 738 "This object describes how tunnel peers belonging 739 to this domain are to be authenticated. The value 740 simple(2) indicates that peers are authenticated simply 741 by their host name as described in the Host Name AVP. 742 The value challenge(3) indicates that all peers are 743 challenged to prove their identification. This mechanism 744 is described in the L2TP protocol." 745 DEFVAL { none } 746 ::= { l2tpDomainConfigEntry 3 } 748 l2tpDomainConfigSecret OBJECT-TYPE 749 SYNTAX OCTET STRING (0..255) 750 MAX-ACCESS read-create 751 STATUS current 752 DESCRIPTION 753 "This object is used to configure the shared secret 754 used during the tunnel authentication phase of 755 tunnel establishment. NOTE that this object should 756 not be visible if the proper SNMPv3 security 757 mechanisms are in place." 758 ::= { l2tpDomainConfigEntry 4 } 760 l2tpDomainConfigTunnelSecurity OBJECT-TYPE 761 SYNTAX INTEGER { 762 none(1), 763 other(2), 764 ipSec(3) 765 } 766 MAX-ACCESS read-create 767 STATUS current 768 DESCRIPTION 769 "This object defines whether this tunnel domain 770 requires that all tunnels are to be secured. The 771 value of ipsec(3) indicates that all tunnel packets, 772 control and session, have IP Security headers. The 773 type of IP Security headers (AH, ESP etc) and how 774 they are further described is outside the scope of 775 this document." 776 DEFVAL { none } 777 ::= { l2tpDomainConfigEntry 5 } 779 l2tpDomainConfigTunnelHelloInterval OBJECT-TYPE 780 SYNTAX Integer32 (0..3600) 781 MAX-ACCESS read-create 782 STATUS current 783 DESCRIPTION 784 "This object defines the interval (in seconds) in 785 which Hello (or keep-alive) packets are to be sent 786 by local peers belonging to this tunnel domain." 787 DEFVAL { 60 } 788 ::= { l2tpDomainConfigEntry 6 } 790 l2tpDomainConfigTunnelIdleTimeout OBJECT-TYPE 791 SYNTAX Integer32 (0..86400) 792 MAX-ACCESS read-create 793 STATUS current 794 DESCRIPTION 795 "This object defines the period of time (in seconds) 796 that an established tunnel belonging to this tunnel 797 domain with no active sessions will wait before 798 disconnecting the tunnel. A value of zero indicates 799 that the tunnel will disconnect immediately after the 800 last session disconnects." 801 DEFVAL { 0 } 802 ::= { l2tpDomainConfigEntry 7 } 804 l2tpDomainConfigControlRWS OBJECT-TYPE 805 SYNTAX Integer32 (1..64) 806 MAX-ACCESS read-create 807 STATUS current 808 DESCRIPTION 809 "This object defines the control channel receive 810 window size for tunnels belonging to this domain. It 811 specifies the maximum number of packets the tunnel 812 peer belonging to this domain can send without waiting 813 for an acknowledgement from this peer." 814 DEFVAL { 4 } 815 ::= { l2tpDomainConfigEntry 8 } 817 l2tpDomainConfigControlRetransmissions OBJECT-TYPE 818 SYNTAX Integer32 (0..32) 819 MAX-ACCESS read-create 820 STATUS current 821 DESCRIPTION 822 "This object defines the number of retransmission's 823 which the L2TP stack will attempt for tunnels belonging 824 to this domain before assuming that the peer is no 825 longer responding." 826 DEFVAL { 4 } 827 ::= { l2tpDomainConfigEntry 9 } 829 l2tpDomainConfigPayloadSequencing OBJECT-TYPE 830 SYNTAX TruthValue 831 MAX-ACCESS read-create 832 STATUS current 833 DESCRIPTION 834 "This object determines whether or not session payload 835 packets will be requested to be sent with sequence 836 numbers from tunnel peer's belonging to this domain." 837 DEFVAL { false } 838 ::= { l2tpDomainConfigEntry 10 } 840 l2tpDomainConfigPayloadRWS OBJECT-TYPE 841 SYNTAX Integer32 (0..65535) 842 MAX-ACCESS read-create 843 STATUS current 844 DESCRIPTION 845 "This object defines the payload sessions receive 846 window size. It specifies the maximum number of 847 packets the tunnel peer can send without waiting 848 for an acknowledgement from this peer or an 849 acknowledgement timeout occurs. If paylaod sequencing 850 is not configured for this tunnel domain then this 851 object may be used in the event that the tunnel peer 852 requests payload seqencing." 853 DEFVAL { 0 } 854 ::= { l2tpDomainConfigEntry 11 } 856 l2tpDomainConfigDelayedAckTimeout OBJECT-TYPE 857 SYNTAX MilliSeconds 858 MAX-ACCESS read-create 859 STATUS current 860 DESCRIPTION 861 "This object defines the number of milliseconds 862 which the local tunnel peer will wait to send an 863 acknowledgement to it's peer in the case where there 864 is no data packets to piggyback the acknowledgement 865 on. The default value for this object is zero which 866 results in an immediate acknowledgment to received 867 payload (data) packets. If payload sequencing is not 868 configured then this object should not be interpreted." 869 DEFVAL { 0 } 870 ::= { l2tpDomainConfigEntry 12 } 872 l2tpDomainConfigReassemblyTimeout OBJECT-TYPE 873 SYNTAX MilliSeconds 874 MAX-ACCESS read-create 875 STATUS current 876 DESCRIPTION 877 "This object defines the number of milliseconds that 878 local peer's of this tunnel domain will wait before 879 processing packets that were received out of sequence 880 (which are waiting for the packet(s) to put them in 881 sequence). A low value increases the chance of delayed 882 packets to be discarded (which MAY causes the PPP 883 decompression engine to reset) while a high value may 884 cause more queueing and possibly degrade throughput if 885 packets are truly lost. The default value for this 886 object is zero which will result in all delayed packets 887 being lost." 888 DEFVAL { 0 } 889 ::= { l2tpDomainConfigEntry 13 } 891 l2tpDomainConfigStatus OBJECT-TYPE 892 SYNTAX RowStatus 893 MAX-ACCESS read-create 894 STATUS current 895 DESCRIPTION 896 "The status of this Domain entry." 897 ::= { l2tpDomainConfigEntry 14 } 899 -- 900 -- The L2TP Domain Status and Statistics Table 901 -- 902 -- This table contains objects that can be used to desribe 903 -- the current status and statistics of a tunnel domain. 905 l2tpDomainStatsTable OBJECT-TYPE 906 SYNTAX SEQUENCE OF L2tpDomainStatsEntry 907 MAX-ACCESS not-accessible 908 STATUS current 909 DESCRIPTION 910 "The L2TP Domain Status and Statistics table." 911 ::= { l2tpObjects 3 } 913 l2tpDomainStatsEntry OBJECT-TYPE 914 SYNTAX L2tpDomainStatsEntry 915 MAX-ACCESS not-accessible 916 STATUS current 917 DESCRIPTION 918 "An L2TP Domain Stats entry. An entry in this table 919 may correspond to a single endpoint or a group of 920 tunnel endpoints." 921 INDEX { l2tpDomainStatsIdentifier } 922 ::= { l2tpDomainStatsTable 1 } 924 L2tpDomainStatsEntry ::= 925 SEQUENCE { 926 l2tpDomainStatsIdentifier 927 DisplayString, 928 l2tpDomainStatsTotalTunnels 929 Counter32, 930 l2tpDomainStatsFailedTunnels 931 Counter32, 932 l2tpDomainStatsFailedAuthentications 933 Counter32, 934 l2tpDomainStatsActiveTunnels 935 Gauge32, 936 l2tpDomainStatsTotalSessions 937 Counter32, 938 l2tpDomainStatsFailedSessions 939 Counter32, 940 l2tpDomainStatsActiveSessions 941 Gauge32, 942 l2tpDomainStatsControlRecvOctets 943 Counter32, 944 l2tpDomainStatsControlRecvPackets 945 Counter32, 946 l2tpDomainStatsControlSendOctets 947 Counter32, 948 l2tpDomainStatsControlSendPackets 949 Counter32, 950 l2tpDomainStatsPayloadRecvOctets 951 Counter32, 952 l2tpDomainStatsPayloadRecvPackets 953 Counter32, 954 l2tpDomainStatsPayloadRecvDiscards 955 Counter32, 956 l2tpDomainStatsPayloadSendOctets 957 Counter32, 958 l2tpDomainStatsPayloadSendPackets 959 Counter32 960 } 962 l2tpDomainStatsIdentifier OBJECT-TYPE 963 SYNTAX DisplayString 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "The identifier, usually in the form of a Domain 968 Name (full or partial), describing a single tunnel 969 endpoint or a domain of tunnel endpoints." 970 ::= { l2tpDomainStatsEntry 1 } 972 l2tpDomainStatsTotalTunnels OBJECT-TYPE 973 SYNTAX Counter32 974 MAX-ACCESS read-only 975 STATUS current 976 DESCRIPTION 977 "This object returns the total number of tunnels 978 that have successfully reached the established 979 state for this tunnel domain." 980 ::= { l2tpDomainStatsEntry 2 } 982 l2tpDomainStatsFailedTunnels OBJECT-TYPE 983 SYNTAX Counter32 984 MAX-ACCESS read-only 985 STATUS current 986 DESCRIPTION 987 "This object returns the number of tunnels that 988 failed to reach the established state for this 989 tunnel domain." 990 ::= { l2tpDomainStatsEntry 3 } 992 l2tpDomainStatsFailedAuthentications OBJECT-TYPE 993 SYNTAX Counter32 994 MAX-ACCESS read-only 995 STATUS current 996 DESCRIPTION 997 "This object returns the number of failed tunnel 998 connection attempts for this domain because the 999 tunnel peer failed authentication." 1000 ::= { l2tpDomainStatsEntry 4 } 1002 l2tpDomainStatsActiveTunnels OBJECT-TYPE 1003 SYNTAX Gauge32 1004 MAX-ACCESS read-only 1005 STATUS current 1006 DESCRIPTION 1007 "This object returns the number of tunnels that 1008 are currently active for this domain." 1009 ::= { l2tpDomainStatsEntry 5 } 1011 l2tpDomainStatsTotalSessions OBJECT-TYPE 1012 SYNTAX Counter32 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "This object returns the total number of sessions 1017 that have successfully reached the established state 1018 for this tunnel domain." 1019 ::= { l2tpDomainStatsEntry 6 } 1021 l2tpDomainStatsFailedSessions OBJECT-TYPE 1022 SYNTAX Counter32 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "This object returns the number of sessions that 1027 failed to reach the established state for this 1028 tunnel domain." 1029 ::= { l2tpDomainStatsEntry 7 } 1031 l2tpDomainStatsActiveSessions OBJECT-TYPE 1032 SYNTAX Gauge32 1033 MAX-ACCESS read-only 1034 STATUS current 1035 DESCRIPTION 1036 "This object returns the number of sessions that 1037 are currently active for this domain." 1038 ::= { l2tpDomainStatsEntry 8 } 1040 l2tpDomainStatsControlRecvOctets OBJECT-TYPE 1041 SYNTAX Counter32 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "This object returns the number of control channel 1046 octets received for this tunnel domain." 1047 ::= { l2tpDomainStatsEntry 9 } 1049 l2tpDomainStatsControlRecvPackets OBJECT-TYPE 1050 SYNTAX Counter32 1051 MAX-ACCESS read-only 1052 STATUS current 1053 DESCRIPTION 1054 "This object returns the number of control packets 1055 received for this tunnel domain." 1056 ::= { l2tpDomainStatsEntry 10 } 1058 l2tpDomainStatsControlSendOctets OBJECT-TYPE 1059 SYNTAX Counter32 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "This object returns the number of control channel 1064 octets that were transmitted to tunnel endpoints 1065 for this domain." 1066 ::= { l2tpDomainStatsEntry 11 } 1068 l2tpDomainStatsControlSendPackets OBJECT-TYPE 1069 SYNTAX Counter32 1070 MAX-ACCESS read-only 1071 STATUS current 1072 DESCRIPTION 1073 "This object returns the number of control packets 1074 that were transmitted to tunnel endpoints for 1075 this domain." 1076 ::= { l2tpDomainStatsEntry 12 } 1078 l2tpDomainStatsPayloadRecvOctets OBJECT-TYPE 1079 SYNTAX Counter32 1080 MAX-ACCESS read-only 1081 STATUS current 1082 DESCRIPTION 1083 "This object returns the number of payload channel 1084 octets that were received for this tunnel domain." 1085 ::= { l2tpDomainStatsEntry 13 } 1087 l2tpDomainStatsPayloadRecvPackets OBJECT-TYPE 1088 SYNTAX Counter32 1089 MAX-ACCESS read-only 1090 STATUS current 1091 DESCRIPTION 1092 "This object returns the number of payload packets 1093 that were received for this tunnel domain." 1094 ::= { l2tpDomainStatsEntry 14 } 1096 l2tpDomainStatsPayloadRecvDiscards OBJECT-TYPE 1097 SYNTAX Counter32 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "This object returns the number of received payload 1102 packets that were discarded by this this tunnel 1103 domain." 1104 ::= { l2tpDomainStatsEntry 15 } 1106 l2tpDomainStatsPayloadSendOctets OBJECT-TYPE 1107 SYNTAX Counter32 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "This object returns the number of payload channel 1112 octets that were transmitted to tunnel peers 1113 within this tunnel domain." 1114 ::= { l2tpDomainStatsEntry 16 } 1116 l2tpDomainStatsPayloadSendPackets OBJECT-TYPE 1117 SYNTAX Counter32 1118 MAX-ACCESS read-only 1119 STATUS current 1120 DESCRIPTION 1121 "This object returns the number of payload packets 1122 that were transmitted to tunnel peers within 1123 this tunnel domain." 1124 ::= { l2tpDomainStatsEntry 17 } 1126 -- 1127 -- The L2TP Tunnel Configuration Table 1128 -- 1129 -- This table contains objects that can be used to 1130 -- (re)configure the operational characteristics of a 1131 -- single L2TP tunnel. 1133 l2tpTunnelConfigTable OBJECT-TYPE 1134 SYNTAX SEQUENCE OF L2tpTunnelConfigEntry 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 "The L2TP tunnel configuration table." 1139 ::= { l2tpObjects 4 } 1141 l2tpTunnelConfigEntry OBJECT-TYPE 1142 SYNTAX L2tpTunnelConfigEntry 1143 MAX-ACCESS not-accessible 1144 STATUS current 1145 DESCRIPTION 1146 "A L2TP tunnel interface configuration entry." 1147 INDEX { l2tpTunnelConfigIfIndex } 1148 ::= { l2tpTunnelConfigTable 1 } 1150 L2tpTunnelConfigEntry ::= 1151 SEQUENCE { 1152 l2tpTunnelConfigIfIndex 1153 InterfaceIndex, 1154 l2tpTunnelConfigAuthentication 1155 INTEGER, 1156 l2tpTunnelConfigSecret 1157 OCTET STRING, 1158 l2tpTunnelConfigSecurity 1159 INTEGER, 1160 l2tpTunnelConfigHelloInterval 1161 Integer32, 1162 l2tpTunnelConfigIdleTimeout 1163 Integer32, 1164 l2tpTunnelConfigControlRWS 1165 Integer32, 1166 l2tpTunnelConfigControlRetransmissions 1167 Integer32, 1168 l2tpTunnelConfigPayloadSequencing 1169 TruthValue, 1170 l2tpTunnelConfigPayloadRWS 1171 Integer32, 1172 l2tpTunnelConfigDelayedAckTimeout 1173 MilliSeconds, 1175 l2tpTunnelConfigReassemblyTimeout 1176 MilliSeconds, 1177 l2tpTunnelConfigTransport 1178 INTEGER 1179 } 1181 l2tpTunnelConfigIfIndex OBJECT-TYPE 1182 SYNTAX InterfaceIndex 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION 1186 "This value for this object is equal to the value 1187 of ifIndex of the Interfaces MIB for tunnel 1188 interfaces of type L2TP." 1189 ::= { l2tpTunnelConfigEntry 1 } 1191 l2tpTunnelConfigAuthentication OBJECT-TYPE 1192 SYNTAX INTEGER { 1193 none(1), 1194 simple(2), 1195 challenge(3) 1196 } 1197 MAX-ACCESS read-write 1198 STATUS current 1199 DESCRIPTION 1200 "This object describes how L2TP tunnel peers are 1201 to be authenticated. The value 'simple' indicates 1202 that peers are authenticated simply by their host 1203 name as described in the Host Name AVP. The value 1204 'challenge' indicates that all peers are challenged 1205 to prove their identification. This mechanism is 1206 described in the L2TP protocol." 1207 DEFVAL { none } 1208 ::= { l2tpTunnelConfigEntry 2 } 1210 l2tpTunnelConfigSecret OBJECT-TYPE 1211 SYNTAX OCTET STRING (0..255) 1212 MAX-ACCESS read-write 1213 STATUS current 1214 DESCRIPTION 1215 "This object is used to configure the shared secret 1216 used during the tunnel authentication phase of 1217 tunnel establishment. NOTE that this object should 1218 not be visible if the proper SNMPv3 security 1219 mechanisms are in place." 1220 ::= { l2tpTunnelConfigEntry 3 } 1222 l2tpTunnelConfigSecurity OBJECT-TYPE 1223 SYNTAX INTEGER { 1224 none(1), 1225 other(2), 1226 ipsec(3) 1227 } 1228 MAX-ACCESS read-write 1229 STATUS current 1230 DESCRIPTION 1231 "This object defines whether this tunnel is to be 1232 secured. The value of 'ipSec' indicates that all 1233 tunnel packets, control and session, have IP 1234 Security headers. The type of IP Security headers 1235 (AH, ESP etc) and how they are further described 1236 is outside the scope of this document." 1237 DEFVAL { none } 1238 ::= { l2tpTunnelConfigEntry 4 } 1240 l2tpTunnelConfigHelloInterval OBJECT-TYPE 1241 SYNTAX Integer32 (0..3600) 1242 MAX-ACCESS read-write 1243 STATUS current 1244 DESCRIPTION 1245 "This object defines the interval (in seconds) in 1246 which Hello (or keep-alive) packets are to be sent 1247 to the tunnel peer." 1248 DEFVAL { 60 } 1249 ::= { l2tpTunnelConfigEntry 5 } 1251 l2tpTunnelConfigIdleTimeout OBJECT-TYPE 1252 SYNTAX Integer32 (0..86400) 1253 MAX-ACCESS read-write 1254 STATUS current 1255 DESCRIPTION 1256 "This object defines the period of time (in seconds) 1257 that an established tunnel with no sessions will 1258 wait before disconnecting the tunnel. A value of 1259 zero indicates that the tunnel will disconnect 1260 immediately after the last session disconnects." 1261 DEFVAL { 0 } 1262 ::= { l2tpTunnelConfigEntry 6 } 1264 l2tpTunnelConfigControlRWS OBJECT-TYPE 1265 SYNTAX Integer32 (1..64) 1266 MAX-ACCESS read-write 1267 STATUS current 1268 DESCRIPTION 1269 "This object defines the control channel receive 1270 window size. It specifies the maximum number of 1271 packets the tunnel peer can send without waiting 1272 for an acknowledgement from this peer." 1273 DEFVAL { 4 } 1274 ::= { l2tpTunnelConfigEntry 7 } 1276 l2tpTunnelConfigControlRetransmissions OBJECT-TYPE 1277 SYNTAX Integer32 (0..32) 1278 MAX-ACCESS read-write 1279 STATUS current 1280 DESCRIPTION 1281 "This object defines the number of retransmission's 1282 which the tunnel will attempt before assuming that 1283 the peer is no longer responding. A value of zero 1284 indicates that this peer will not attempt to 1285 retransmit an unacknowledged control packet." 1286 DEFVAL { 4 } 1287 ::= { l2tpTunnelConfigEntry 8 } 1289 l2tpTunnelConfigPayloadSequencing OBJECT-TYPE 1290 SYNTAX TruthValue 1291 MAX-ACCESS read-write 1292 STATUS current 1293 DESCRIPTION 1294 "This object determines whether or not session payload 1295 packets will be requested to be sent with sequence 1296 numbers from the tunnel peer." 1297 DEFVAL { false } 1298 ::= { l2tpTunnelConfigEntry 9 } 1300 l2tpTunnelConfigPayloadRWS OBJECT-TYPE 1301 SYNTAX Integer32 (0..65535) 1302 MAX-ACCESS read-write 1303 STATUS current 1304 DESCRIPTION 1305 "This object defines the payload sessions receive 1306 window size. It specifies the maximum number of 1307 packets the tunnel peer can send without waiting 1308 for an acknowledgement from this peer or an 1309 acknowledgement timeout occurs. If paylaod sequencing 1310 is not configured for this tunnel then this object 1311 may be used in the event that the tunnel peer requests 1312 payload seqencing." 1313 DEFVAL { 0 } 1314 ::= { l2tpTunnelConfigEntry 10 } 1316 l2tpTunnelConfigDelayedAckTimeout OBJECT-TYPE 1317 SYNTAX MilliSeconds 1318 MAX-ACCESS read-write 1319 STATUS current 1320 DESCRIPTION 1321 "This object defines the number of milliseconds 1322 which the local tunnel peer will wait to send an 1323 acknowledgement to it's peer in the case where there 1324 is no data packets to piggyback the acknowledgement 1325 on. The default value for this object is zero which 1326 results in an immediate acknowledgment to received 1327 payload (data) packets. If payload sequencing is not 1328 configured then this object should not be interpreted." 1329 DEFVAL { 0 } 1330 ::= { l2tpTunnelConfigEntry 11 } 1332 l2tpTunnelConfigReassemblyTimeout OBJECT-TYPE 1333 SYNTAX MilliSeconds 1334 MAX-ACCESS read-write 1335 STATUS current 1336 DESCRIPTION 1337 "This object defines the number of milliseconds that 1338 this tunnel will wait before processing packets that 1339 were received out of sequence (which are waiting for 1340 the packet(s) to put them in sequence). A low value 1341 increases the chance of delayed packets to be discarded 1342 (which MAY causes the PPP decompression engine to 1343 reset) while a high value may cause more queueing and 1344 possibly degrade throughput if packets are truly lost. 1345 The default value for this object is zero which will 1346 result in all delayed packets being lost." 1347 DEFVAL { 0 } 1348 ::= { l2tpTunnelConfigEntry 12 } 1350 l2tpTunnelConfigTransport OBJECT-TYPE 1351 SYNTAX INTEGER { 1352 other(1), 1353 none(2), 1354 ipUdp(3), 1355 frameRelay(4) 1356 } 1357 MAX-ACCESS read-write 1358 STATUS current 1359 DESCRIPTION 1360 "This object defines the underlying transport media 1361 that is in use for this tunnel entry. Different tunnel 1362 transports may define MIB extensions to the L2TP tunnel 1363 table to realize the transport layer. For example if the 1364 value of this object is 'ipUdp' then the value of ifIndex 1365 for this table may be used to determine state from the 1366 l2tpUdpStatsTable." 1368 ::= { l2tpTunnelConfigEntry 13 } 1370 -- 1371 -- The L2TP Tunnel Status and Statisticss Table 1372 -- 1373 -- This table contains objects that can be used to describe 1374 -- the current status and statistics of a single L2TP tunnel. 1376 l2tpTunnelStatsTable OBJECT-TYPE 1377 SYNTAX SEQUENCE OF L2tpTunnelStatsEntry 1378 MAX-ACCESS not-accessible 1379 STATUS current 1380 DESCRIPTION 1381 "The L2TP tunnel status and statistics table." 1382 ::= { l2tpObjects 5 } 1384 l2tpTunnelStatsEntry OBJECT-TYPE 1385 SYNTAX L2tpTunnelStatsEntry 1386 MAX-ACCESS not-accessible 1387 STATUS current 1388 DESCRIPTION 1389 "An L2TP tunnel interface stats entry." 1390 INDEX { l2tpTunnelStatsIfIndex } 1391 ::= { l2tpTunnelStatsTable 1 } 1393 L2tpTunnelStatsEntry ::= 1394 SEQUENCE { 1395 l2tpTunnelStatsIfIndex 1396 InterfaceIndex, 1397 l2tpTunnelStatsLocalTID 1398 Integer32, 1399 l2tpTunnelStatsRemoteTID 1400 Integer32, 1401 l2tpTunnelStatsState 1402 INTEGER, 1403 l2tpTunnelStatsInitiated 1404 INTEGER, 1405 l2tpTunnelStatsRemoteHostName 1406 DisplayString, 1407 l2tpTunnelStatsRemoteVendorName 1408 DisplayString, 1409 l2tpTunnelStatsRemoteFirmwareRevision 1410 Integer32, 1411 l2tpTunnelStatsRemoteProtocolVersion 1412 OCTET STRING, 1413 l2tpTunnelStatsInitialRemoteRWS 1414 Integer32, 1415 l2tpTunnelStatsBearerCapabilities 1416 INTEGER, 1418 l2tpTunnelStatsFramingCapabilities 1419 INTEGER, 1420 l2tpTunnelStatsControlRecvPackets 1421 Counter32, 1422 l2tpTunnelStatsControlRecvZLB 1423 Counter32, 1424 l2tpTunnelStatsControlOutOfSequence 1425 Counter32, 1426 l2tpTunnelStatsControlOutOfWindow 1427 Counter32, 1428 l2tpTunnelStatsControlSendPackets 1429 Counter32, 1430 l2tpTunnelStatsControlSendZLB 1431 Counter32, 1432 l2tpTunnelStatsControlAckTimeouts 1433 Counter32, 1434 l2tpTunnelStatsCurrentRemoteRWS 1435 Gauge32, 1436 l2tpTunnelStatsSendSeq 1437 Integer32, 1438 l2tpTunnelStatsSendSeqAck 1439 Integer32, 1440 l2tpTunnelStatsRecvSeq 1441 Integer32, 1442 l2tpTunnelStatsRecvSeqAck 1443 Integer32, 1444 l2tpTunnelStatsTotalSessions 1445 Counter32, 1446 l2tpTunnelStatsFailedSessions 1447 Counter32, 1448 l2tpTunnelStatsActiveSessions 1449 Gauge32, 1450 l2tpTunnelStatsLastResultCode 1451 Integer32, 1452 l2tpTunnelStatsLastErrorCode 1453 Integer32, 1454 l2tpTunnelStatsLastErrorMessage 1455 DisplayString 1456 } 1458 l2tpTunnelStatsIfIndex OBJECT-TYPE 1459 SYNTAX InterfaceIndex 1460 MAX-ACCESS read-only 1461 STATUS current 1462 DESCRIPTION 1463 "This value for this object is equal to the value 1464 of ifIndex of the Interfaces MIB for tunnel 1465 interfaces of type L2TP." 1467 ::= { l2tpTunnelStatsEntry 1 } 1469 l2tpTunnelStatsLocalTID OBJECT-TYPE 1470 SYNTAX Integer32 (0..65535) 1471 MAX-ACCESS read-only 1472 STATUS current 1473 DESCRIPTION 1474 "This object contains the local tunnel Identifier." 1475 ::= { l2tpTunnelStatsEntry 2 } 1477 l2tpTunnelStatsRemoteTID OBJECT-TYPE 1478 SYNTAX Integer32 (0..65535) 1479 MAX-ACCESS read-only 1480 STATUS current 1481 DESCRIPTION 1482 "This object contains the remote tunnel Identifier." 1483 ::= { l2tpTunnelStatsEntry 3 } 1485 l2tpTunnelStatsState OBJECT-TYPE 1486 SYNTAX INTEGER { 1487 tunnelIdle(1), 1488 tunnelConnecting(2), 1489 tunnelEstablished(3), 1490 tunnelDisconnecting(4) 1491 } 1492 MAX-ACCESS read-only 1493 STATUS current 1494 DESCRIPTION 1495 "This field contains the current state of the control 1496 tunnel." 1497 ::= { l2tpTunnelStatsEntry 4 } 1499 l2tpTunnelStatsInitiated OBJECT-TYPE 1500 SYNTAX INTEGER { 1501 locally(1), 1502 remotely(2) 1503 } 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "This object indicates whether the tunnel was 1508 initiated locally or by the remote tunnel peer." 1509 ::= { l2tpTunnelStatsEntry 5 } 1511 l2tpTunnelStatsRemoteHostName OBJECT-TYPE 1512 SYNTAX DisplayString 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "This object contains the host name as discovered 1517 during the tunnel establishment phase (via the Host 1518 Name AVP) of the L2TP peer. If the tunnel is idle 1519 this object should maintain its value from the last 1520 time it was connected." 1521 ::= { l2tpTunnelStatsEntry 6 } 1523 l2tpTunnelStatsRemoteVendorName OBJECT-TYPE 1524 SYNTAX DisplayString 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "This object identifies the vendor name of the peer's 1529 L2TP implementation. If the tunnel is idle this 1530 object should maintain its value from the last time 1531 it was connected." 1532 ::= { l2tpTunnelStatsEntry 7 } 1534 l2tpTunnelStatsRemoteFirmwareRevision OBJECT-TYPE 1535 SYNTAX Integer32 1536 MAX-ACCESS read-only 1537 STATUS current 1538 DESCRIPTION 1539 "This object contains the tunnel peer's firmware 1540 revision number. If the tunnel is idle this object 1541 should maintain its value from the last time it 1542 was connected." 1543 ::= { l2tpTunnelStatsEntry 8 } 1545 l2tpTunnelStatsRemoteProtocolVersion OBJECT-TYPE 1546 SYNTAX OCTET STRING (SIZE(2)) 1547 MAX-ACCESS read-only 1548 STATUS current 1549 DESCRIPTION 1550 "This object describes the protocol version and 1551 revision of the tunnel peers implementation. The 1552 first octet contains the protocol version. The 1553 second octet contains the protocol revision." 1554 ::= { l2tpTunnelStatsEntry 9 } 1556 l2tpTunnelStatsInitialRemoteRWS OBJECT-TYPE 1557 SYNTAX Integer32 (0..65535) 1558 MAX-ACCESS read-only 1559 STATUS current 1560 DESCRIPTION 1561 "This object contains the initial remote peers 1562 receive window size as indicated by the tunnel peer 1563 (in the RWS AVP) during the tunnel establishment 1564 phase. If the tunnel is idle this object should 1565 maintain its value from the last time it was 1566 connected." 1567 ::= { l2tpTunnelStatsEntry 10 } 1569 l2tpTunnelStatsBearerCapabilities OBJECT-TYPE 1570 SYNTAX INTEGER { 1571 none(1), 1572 digital(2), 1573 analog(3), 1574 digitalAnalog(4) 1575 } 1576 MAX-ACCESS read-only 1577 STATUS current 1578 DESCRIPTION 1579 "This object describes the Bearer Capabilities of 1580 the tunnel peer. If the tunnel is idle this object 1581 should maintain its value from the last time it was 1582 connected." 1583 ::= { l2tpTunnelStatsEntry 11 } 1585 l2tpTunnelStatsFramingCapabilities OBJECT-TYPE 1586 SYNTAX INTEGER { 1587 none(1), 1588 sync(2), 1589 async(3), 1590 syncAsync(4) 1591 } 1592 MAX-ACCESS read-only 1593 STATUS current 1594 DESCRIPTION 1595 "This object describes the Framing Capabilities of 1596 the tunnel peer. If the tunnel is idle this object 1597 should maintain its value from the last time it was 1598 connected." 1599 ::= { l2tpTunnelStatsEntry 12 } 1601 l2tpTunnelStatsControlRecvPackets OBJECT-TYPE 1602 SYNTAX Counter32 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "This object contains the number of control packets 1607 received on the tunnel." 1608 ::= { l2tpTunnelStatsEntry 13 } 1610 l2tpTunnelStatsControlRecvZLB OBJECT-TYPE 1611 SYNTAX Counter32 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "This object returns a count of the number of Zero 1616 Length Body control packet acknowledgement packets 1617 that were received." 1618 ::= { l2tpTunnelStatsEntry 14 } 1620 l2tpTunnelStatsControlOutOfSequence OBJECT-TYPE 1621 SYNTAX Counter32 1622 MAX-ACCESS read-only 1623 STATUS current 1624 DESCRIPTION 1625 "This object returns a count of the number of 1626 control packets that were not received in the 1627 correct order (as per the sequence number) on 1628 this tunnel." 1629 ::= { l2tpTunnelStatsEntry 15 } 1631 l2tpTunnelStatsControlOutOfWindow OBJECT-TYPE 1632 SYNTAX Counter32 1633 MAX-ACCESS read-only 1634 STATUS current 1635 DESCRIPTION 1636 "This object contains the number of control 1637 packets that were received outside of the 1638 offered receive window. It is implementation 1639 specific as to whether these packets are queued 1640 or discarded." 1641 ::= { l2tpTunnelStatsEntry 16 } 1643 l2tpTunnelStatsControlSendPackets OBJECT-TYPE 1644 SYNTAX Counter32 1645 MAX-ACCESS read-only 1646 STATUS current 1647 DESCRIPTION 1648 "This object contains the number of control 1649 packets that were transmitted to the tunnel 1650 peer." 1651 ::= { l2tpTunnelStatsEntry 17 } 1653 l2tpTunnelStatsControlSendZLB OBJECT-TYPE 1654 SYNTAX Counter32 1655 MAX-ACCESS read-only 1656 STATUS current 1657 DESCRIPTION 1658 "This object contains the number of Zero Length 1659 Body control packets transmitted transitted to 1660 the tunnel peer." 1661 ::= { l2tpTunnelStatsEntry 18 } 1663 l2tpTunnelStatsControlAckTimeouts OBJECT-TYPE 1664 SYNTAX Counter32 1665 MAX-ACCESS read-only 1666 STATUS current 1667 DESCRIPTION 1668 "This object returns a count of the number of 1669 control packet timeouts due to the lack of a 1670 timely acknowledgement from the tunnel peer." 1671 ::= { l2tpTunnelStatsEntry 19 } 1673 l2tpTunnelStatsCurrentRemoteRWS OBJECT-TYPE 1674 SYNTAX Gauge32 (0..64) 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "This object contains the current remote receive 1679 window size as determined by the local flow 1680 control mechanism employed." 1681 ::= { l2tpTunnelStatsEntry 20 } 1683 l2tpTunnelStatsSendSeq OBJECT-TYPE 1684 SYNTAX Integer32 (0..65535) 1685 MAX-ACCESS read-only 1686 STATUS current 1687 DESCRIPTION 1688 "This object contains the next send sequence number 1689 for the control channel." 1690 ::= { l2tpTunnelStatsEntry 21 } 1692 l2tpTunnelStatsSendSeqAck OBJECT-TYPE 1693 SYNTAX Integer32 (0..65535) 1694 MAX-ACCESS read-only 1695 STATUS current 1696 DESCRIPTION 1697 "This object contains the send sequence number that 1698 the tunnel peer has acknowledged for the control 1699 channel. The flow control state can be determined 1700 by subtracting the l2tpTunnelStatsSendSeq from 1701 l2tpTunnelStatsSendSeqAck and comparing this value 1702 to l2tpTunnelStatsCurrentRemoteRWS." 1703 ::= { l2tpTunnelStatsEntry 22 } 1705 l2tpTunnelStatsRecvSeq OBJECT-TYPE 1706 SYNTAX Integer32 (0..65535) 1707 MAX-ACCESS read-only 1708 STATUS current 1709 DESCRIPTION 1710 "This object contains the next receive sequence 1711 number expected to be received on this control 1712 channel." 1713 ::= { l2tpTunnelStatsEntry 23 } 1715 l2tpTunnelStatsRecvSeqAck OBJECT-TYPE 1716 SYNTAX Integer32 (0..65535) 1717 MAX-ACCESS read-only 1718 STATUS current 1719 DESCRIPTION 1720 "This object contains the last receive sequence 1721 number that was acknowledged back to the tunnel 1722 peer for the control channel." 1723 ::= { l2tpTunnelStatsEntry 24 } 1725 l2tpTunnelStatsTotalSessions OBJECT-TYPE 1726 SYNTAX Counter32 1727 MAX-ACCESS read-only 1728 STATUS current 1729 DESCRIPTION 1730 "This object contains the total number of sessions 1731 that this tunnel has successfully connected through 1732 to its tunnel peer since this tunnel was created." 1733 ::= { l2tpTunnelStatsEntry 25 } 1735 l2tpTunnelStatsFailedSessions OBJECT-TYPE 1736 SYNTAX Counter32 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "This object contains the total number of sessions 1741 that were initiated but failed to reach the 1742 established phase." 1743 ::= { l2tpTunnelStatsEntry 26 } 1745 l2tpTunnelStatsActiveSessions OBJECT-TYPE 1746 SYNTAX Gauge32 1747 MAX-ACCESS read-only 1748 STATUS current 1749 DESCRIPTION 1750 "This object contains the total number of sessions 1751 in the established state for this tunnel." 1752 ::= { l2tpTunnelStatsEntry 27 } 1754 l2tpTunnelStatsLastResultCode OBJECT-TYPE 1755 SYNTAX Integer32 (0..65535) 1756 MAX-ACCESS read-only 1757 STATUS current 1758 DESCRIPTION 1759 "This object contains the last value of the result 1760 code as described in the Result Code AVP which 1761 caused the tunnel to disconnect." 1762 ::= { l2tpTunnelStatsEntry 28 } 1764 l2tpTunnelStatsLastErrorCode OBJECT-TYPE 1765 SYNTAX Integer32 (0..65535) 1766 MAX-ACCESS read-only 1767 STATUS current 1768 DESCRIPTION 1769 "This object contains the last value of the error 1770 code as described in the Result Code AVP which 1771 caused the tunnel to disconnect." 1772 ::= { l2tpTunnelStatsEntry 29 } 1774 l2tpTunnelStatsLastErrorMessage OBJECT-TYPE 1775 SYNTAX DisplayString 1776 MAX-ACCESS read-only 1777 STATUS current 1778 DESCRIPTION 1779 "This object contains the last value of the optional 1780 message as described in the Result Code AVP which 1781 caused the tunnel to disconnect." 1782 ::= { l2tpTunnelStatsEntry 30 } 1784 -- 1785 -- { l2tpObjects 6 } reserved for future use 1786 -- 1787 -- 1788 -- The L2TP Session Status and Statistics Table 1789 -- 1790 -- This table contains the objects that can be used to 1791 -- describe the current status and statistics of a single 1792 -- L2TP tunneled session. 1794 l2tpSessionStatsTable OBJECT-TYPE 1795 SYNTAX SEQUENCE OF L2tpSessionStatsEntry 1796 MAX-ACCESS not-accessible 1797 STATUS current 1798 DESCRIPTION 1799 "The L2TP session status and statistics table." 1800 ::= { l2tpObjects 7 } 1802 l2tpSessionStatsEntry OBJECT-TYPE 1803 SYNTAX L2tpSessionStatsEntry 1804 MAX-ACCESS not-accessible 1805 STATUS current 1806 DESCRIPTION 1807 "An L2TP session interface stats entry." 1808 INDEX { l2tpSessionStatsTunnelIfIndex, l2tpSessionStatsLocalCID } 1809 ::= { l2tpSessionStatsTable 1 } 1811 L2tpSessionStatsEntry ::= 1812 SEQUENCE { 1813 l2tpSessionStatsTunnelIfIndex 1814 InterfaceIndex, 1815 l2tpSessionStatsHLIfIndex 1816 InterfaceIndex, 1817 l2tpSessionStatsLocalCID 1818 Integer32, 1819 l2tpSessionStatsRemoteCID 1820 Integer32, 1821 l2tpSessionStatsUserName 1822 DisplayString, 1823 l2tpSessionStatsState 1824 INTEGER, 1825 l2tpSessionStatsCallType 1826 INTEGER, 1827 l2tpSessionStatsCallSerialNumber 1828 Integer32, 1829 l2tpSessionStatsTxConnectSpeed 1830 Integer32, 1831 l2tpSessionStatsRxConnectSpeed 1832 Integer32, 1833 l2tpSessionStatsCallBearerType 1834 INTEGER, 1835 l2tpSessionStatsFramingType 1836 INTEGER, 1837 l2tpSessionStatsPhysChanId 1838 Integer32, 1839 l2tpSessionStatsDNIS 1840 DisplayString, 1841 l2tpSessionStatsCLID 1842 DisplayString, 1843 l2tpSessionStatsSubAddress 1844 DisplayString, 1845 l2tpSessionStatsPrivateGroupID 1846 DisplayString, 1847 l2tpSessionStatsProxyLcp 1848 TruthValue, 1849 l2tpSessionStatsAuthMethod 1850 INTEGER, 1851 l2tpSessionStatsLocalRWS 1852 Integer32, 1853 l2tpSessionStatsRemoteInitialRWS 1854 Integer32, 1855 l2tpSessionStatsRemotePPD 1856 Integer32, 1857 l2tpSessionStatsSequencingState 1858 INTEGER, 1859 l2tpSessionStatsRecvZLB 1860 Counter32, 1861 l2tpSessionStatsOutSequence 1862 Counter32, 1863 l2tpSessionStatsOutOfWindow 1864 Counter32, 1865 l2tpSessionStatsSendZLB 1866 Counter32, 1867 l2tpSessionStatsAckTimeouts 1868 Counter32, 1869 l2tpSessionStatsReassemblyTimeouts 1870 Counter32, 1871 l2tpSesssionStatsCurrentRemoteRWS 1872 Gauge32, 1873 l2tpSessionStatsSendSeq 1874 Integer32, 1875 l2tpSessionStatsSendSeqAck 1876 Integer32, 1877 l2tpSessionStatsSendSeqResets 1878 Counter32, 1879 l2tpSessionStatsRecvSeq 1880 Integer32, 1881 l2tpSessionStatsRecvSeqAck 1882 Integer32, 1883 l2tpSessionStatsRecvSeqResets 1884 Counter32 1885 } 1887 l2tpSessionStatsTunnelIfIndex OBJECT-TYPE 1888 SYNTAX InterfaceIndex 1889 MAX-ACCESS read-only 1890 STATUS current 1891 DESCRIPTION 1892 "This object identifies the sessions associated 1893 L2TP tunnel ifIndex value." 1894 ::= { l2tpSessionStatsEntry 1 } 1896 l2tpSessionStatsHLIfIndex OBJECT-TYPE 1897 SYNTAX InterfaceIndex 1898 MAX-ACCESS read-only 1899 STATUS current 1900 DESCRIPTION 1901 "This object identifies the ifIndex value of the 1902 interface that is either below (Lower) the tunnel 1903 (if this tunnel endpoint is a LAC) or above 1904 (Higher) the tunnel (if this tunnel endpoint is a 1905 LNS). For example this could be a DS0 ifIndex on a 1906 LAC or it would be the PPP ifIndex on the LNS. 1907 ::= { l2tpSessionStatsEntry 2 } 1909 l2tpSessionStatsLocalCID OBJECT-TYPE 1910 SYNTAX Integer32 (0..65535) 1911 MAX-ACCESS read-only 1912 STATUS current 1913 DESCRIPTION 1914 "This object contains the local call identifier 1915 for the session." 1916 ::= { l2tpSessionStatsEntry 3 } 1918 l2tpSessionStatsRemoteCID OBJECT-TYPE 1919 SYNTAX Integer32 (0..65535) 1920 MAX-ACCESS read-only 1921 STATUS current 1922 DESCRIPTION 1923 "This object contains the remote call identifier 1924 for the session." 1925 ::= { l2tpSessionStatsEntry 4 } 1927 l2tpSessionStatsUserName OBJECT-TYPE 1928 SYNTAX DisplayString 1929 MAX-ACCESS read-only 1930 STATUS current 1931 DESCRIPTION 1932 "This object identifies the peer session name on 1933 this interface. This is typically the login name 1934 of the remote user. If the user name is unknown to 1935 the local tunnel peer then this object will contain 1936 a null string." 1937 ::= { l2tpSessionStatsEntry 5 } 1939 l2tpSessionStatsState OBJECT-TYPE 1940 SYNTAX INTEGER { 1941 sessionIdle(1), 1942 sessionConnecting(2), 1943 sessionEstablished(3), 1944 sessionDisconnecting(4) 1945 } 1946 MAX-ACCESS read-only 1947 STATUS current 1948 DESCRIPTION 1949 "This object contains the current state of the 1950 session." 1951 ::= { l2tpSessionStatsEntry 6 } 1953 l2tpSessionStatsCallType OBJECT-TYPE 1954 SYNTAX INTEGER { 1955 lacIncoming(1), 1956 lnsIncoming(2), 1957 lacOutgoing(3), 1958 lnsOutgoing(4) 1959 } 1960 MAX-ACCESS read-only 1961 STATUS current 1962 DESCRIPTION 1963 "This object indicates the type of call and the 1964 role this tunnel peer is providing for this 1965 session. For example, lacIncoming(1) indicates 1966 that this tunnel peer is acting as a LAC and 1967 generated a Incoming-Call-Request to the tunnel 1968 peer (the LNS). Note that tunnel peers can be 1969 both LAC and LNS simultaneously." 1970 ::= { l2tpSessionStatsEntry 7 } 1972 l2tpSessionStatsCallSerialNumber OBJECT-TYPE 1973 SYNTAX Integer32 1974 MAX-ACCESS read-only 1975 STATUS current 1976 DESCRIPTION 1977 "This object contains the serial number that has 1978 been assigned to this session." 1979 ::= { l2tpSessionStatsEntry 8 } 1981 l2tpSessionStatsTxConnectSpeed OBJECT-TYPE 1982 SYNTAX Integer32 1983 MAX-ACCESS read-only 1984 STATUS current 1985 DESCRIPTION 1986 "This object returns the last known transmit 1987 baud rate for this session." 1988 ::= { l2tpSessionStatsEntry 9 } 1990 l2tpSessionStatsRxConnectSpeed OBJECT-TYPE 1991 SYNTAX Integer32 1992 MAX-ACCESS read-only 1993 STATUS current 1994 DESCRIPTION 1995 "This object returns the last known receive 1996 baud rate for this session established." 1997 ::= { l2tpSessionStatsEntry 10 } 1999 l2tpSessionStatsCallBearerType OBJECT-TYPE 2000 SYNTAX INTEGER { 2001 none(1), 2002 digital(2), 2003 analog(3) 2004 } 2005 MAX-ACCESS read-only 2006 STATUS current 2007 DESCRIPTION 2008 "This object describes the bearer type of this 2009 session." 2010 ::= { l2tpSessionStatsEntry 11 } 2012 l2tpSessionStatsFramingType OBJECT-TYPE 2013 SYNTAX INTEGER { 2014 none(1), 2015 sync(2), 2016 async(3) 2017 } 2018 MAX-ACCESS read-only 2019 STATUS current 2020 DESCRIPTION 2021 "This object describes the framing type of this 2022 session." 2023 ::= { l2tpSessionStatsEntry 12 } 2025 l2tpSessionStatsPhysChanId OBJECT-TYPE 2026 SYNTAX Integer32 2027 MAX-ACCESS read-only 2028 STATUS current 2029 DESCRIPTION 2030 "This object contains the physical channel 2031 identifier for the session." 2032 ::= { l2tpSessionStatsEntry 13 } 2034 l2tpSessionStatsDNIS OBJECT-TYPE 2035 SYNTAX DisplayString 2036 MAX-ACCESS read-only 2037 STATUS current 2038 DESCRIPTION 2039 "This object identifies the Dialed Number 2040 Information String that the LAC obtained from 2041 the network for the session. If no DNIS was 2042 provided then a null string will be returned." 2043 ::= { l2tpSessionStatsEntry 14 } 2045 l2tpSessionStatsCLID OBJECT-TYPE 2046 SYNTAX DisplayString 2047 MAX-ACCESS read-only 2048 STATUS current 2049 DESCRIPTION 2050 "This object identifies the Calling Line ID 2051 that the LAC obtained from the network for 2052 the session. If no CLID was provided then a 2053 null string will be returned." 2054 ::= { l2tpSessionStatsEntry 15 } 2056 l2tpSessionStatsSubAddress OBJECT-TYPE 2057 SYNTAX DisplayString 2058 MAX-ACCESS read-only 2059 STATUS current 2060 DESCRIPTION 2061 "This object identifies the Sub Address that 2062 the LAC obtained from the network for the 2063 session. If no Sub Address was provided then 2064 a null string will be returned." 2065 ::= { l2tpSessionStatsEntry 16 } 2067 l2tpSessionStatsPrivateGroupID OBJECT-TYPE 2068 SYNTAX DisplayString 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "This object identifies the Private Group 2073 Identifier used for this tunneled session. 2075 If no Private Group Identifier was provided 2076 then a null string will be returned." 2077 ::= { l2tpSessionStatsEntry 17 } 2079 l2tpSessionStatsProxyLcp OBJECT-TYPE 2080 SYNTAX TruthValue 2081 MAX-ACCESS read-only 2082 STATUS current 2083 DESCRIPTION 2084 "Indicates whether the LAC performed proxy LCP 2085 for this session." 2086 ::= { l2tpSessionStatsEntry 18 } 2088 l2tpSessionStatsAuthMethod OBJECT-TYPE 2089 SYNTAX INTEGER { 2090 none(1), 2091 text(2), 2092 pppChap(3), 2093 pppPap(4) 2094 } 2095 MAX-ACCESS read-only 2096 STATUS current 2097 DESCRIPTION 2098 "This object contains the proxy authentication 2099 method employed by the LAC for the session. If 2100 l2tpSessionProxyLcp is false(2) this object should 2101 not be interpreted." 2102 ::= { l2tpSessionStatsEntry 19 } 2104 l2tpSessionStatsLocalRWS OBJECT-TYPE 2105 SYNTAX Integer32 (0..65535) 2106 MAX-ACCESS read-only 2107 STATUS current 2108 DESCRIPTION 2109 "This object returns the local send window size 2110 for this session. If the value of the object 2111 l2tpSessionStatsSequencingState is none(1) 2112 then this object should not be interpreted." 2113 ::= { l2tpSessionStatsEntry 20 } 2115 l2tpSessionStatsRemoteInitialRWS OBJECT-TYPE 2116 SYNTAX Integer32 (0..65535) 2117 MAX-ACCESS read-only 2118 STATUS current 2119 DESCRIPTION 2120 "This object returns the initial remote send 2121 window size for this session. If the value 2122 of the object l2tpSessionStatsSequencingState 2123 is none(1) then this object should not be 2124 interpreted." 2125 ::= { l2tpSessionStatsEntry 21 } 2127 l2tpSessionStatsRemotePPD OBJECT-TYPE 2128 SYNTAX Integer32 2129 MAX-ACCESS read-only 2130 STATUS current 2131 DESCRIPTION 2132 "This object contains the Packet Processing Delay 2133 for the session. If the value of the object 2134 l2tpSessionStatsSequencingState is none(1) 2135 then this object should not be interpreted." 2136 ::= { l2tpSessionStatsEntry 22 } 2138 l2tpSessionStatsSequencingState OBJECT-TYPE 2139 SYNTAX INTEGER { 2140 none(1), 2141 remote(2), 2142 local(3), 2143 both(4) 2144 } 2145 MAX-ACCESS read-only 2146 STATUS current 2147 DESCRIPTION 2148 "This object defines which tunnel peers have 2149 requested payload sequencing. The value of 2150 both(4) indicates that both peers have requested 2151 payload sequencing." 2152 ::= { l2tpSessionStatsEntry 23 } 2154 l2tpSessionStatsRecvZLB OBJECT-TYPE 2155 SYNTAX Counter32 2156 MAX-ACCESS read-only 2157 STATUS current 2158 DESCRIPTION 2159 "This object returns the total number of Zero Length 2160 Body acknowlegement payload packets received for 2161 this session." 2162 ::= { l2tpSessionStatsEntry 24 } 2164 l2tpSessionStatsOutSequence OBJECT-TYPE 2165 SYNTAX Counter32 2166 MAX-ACCESS read-only 2167 STATUS current 2168 DESCRIPTION 2169 "This object returns the total number of packets 2170 received for this session which were received out 2171 of sequence." 2172 ::= { l2tpSessionStatsEntry 25 } 2174 l2tpSessionStatsOutOfWindow OBJECT-TYPE 2175 SYNTAX Counter32 2176 MAX-ACCESS read-only 2177 STATUS current 2178 DESCRIPTION 2179 "This object returns a count of the number of 2180 payload packets that were received outside of the 2181 expected window for this session." 2182 ::= { l2tpSessionStatsEntry 26 } 2184 l2tpSessionStatsSendZLB OBJECT-TYPE 2185 SYNTAX Counter32 2186 MAX-ACCESS read-only 2187 STATUS current 2188 DESCRIPTION 2189 "This object returns the total number of Zero 2190 Length Body acknowledgement packets transmitted 2191 on this session." 2192 ::= { l2tpSessionStatsEntry 27 } 2194 l2tpSessionStatsAckTimeouts OBJECT-TYPE 2195 SYNTAX Counter32 2196 MAX-ACCESS read-only 2197 STATUS current 2198 DESCRIPTION 2199 "This object returns the total number of 2200 acknowledgement timeouts seen on payload 2201 packets for this session." 2202 ::= { l2tpSessionStatsEntry 28 } 2204 l2tpSessionStatsReassemblyTimeouts OBJECT-TYPE 2205 SYNTAX Counter32 2206 MAX-ACCESS read-only 2207 STATUS current 2208 DESCRIPTION 2209 "This object returns the number of reassembly 2210 time outs that have occured for this session." 2211 ::= { l2tpSessionStatsEntry 29 } 2213 l2tpSesssionStatsCurrentRemoteRWS OBJECT-TYPE 2214 SYNTAX Gauge32 (0..65535) 2215 MAX-ACCESS read-only 2216 STATUS current 2217 DESCRIPTION 2218 "This object contains the current remote receive 2219 window size as determined by the local flow 2220 control mechanism employed." 2221 ::= { l2tpSessionStatsEntry 30 } 2223 l2tpSessionStatsSendSeq OBJECT-TYPE 2224 SYNTAX Integer32 (0..65535) 2225 MAX-ACCESS read-only 2226 STATUS current 2227 DESCRIPTION 2228 "This object contains the next send sequence number 2229 for for this session." 2230 ::= { l2tpSessionStatsEntry 31 } 2232 l2tpSessionStatsSendSeqAck OBJECT-TYPE 2233 SYNTAX Integer32 (0..65535) 2234 MAX-ACCESS read-only 2235 STATUS current 2236 DESCRIPTION 2237 "This object contains the send sequence number 2238 that the tunnel peer has acknowledged for the 2239 payload channel. The flow control state can be 2240 determined by subtracting the l2tpSessionStatsSendSeq 2241 from l2tpSessionStatsSendSeqAck and comparing this 2242 value to l2tpSesssionStatsCurrentRemoteRWS." 2243 ::= { l2tpSessionStatsEntry 32 } 2245 l2tpSessionStatsSendSeqResets OBJECT-TYPE 2246 SYNTAX Counter32 2247 MAX-ACCESS read-only 2248 STATUS current 2249 DESCRIPTION 2250 "This object contains the total number of sequence 2251 number resets (payload packets with the R-bit set) 2252 sent on this session." 2253 ::= { l2tpSessionStatsEntry 33 } 2255 l2tpSessionStatsRecvSeq OBJECT-TYPE 2256 SYNTAX Integer32 (0..65535) 2257 MAX-ACCESS read-only 2258 STATUS current 2259 DESCRIPTION 2260 "This object contains the next receive sequence 2261 number expected to be received on this session." 2262 ::= { l2tpSessionStatsEntry 34 } 2264 l2tpSessionStatsRecvSeqAck OBJECT-TYPE 2265 SYNTAX Integer32 (0..65535) 2266 MAX-ACCESS read-only 2267 STATUS current 2268 DESCRIPTION 2269 "This object contains the last receive sequence 2270 number that was acknowledged back to the tunnel 2271 peer for the session." 2272 ::= { l2tpSessionStatsEntry 35 } 2274 l2tpSessionStatsRecvSeqResets OBJECT-TYPE 2275 SYNTAX Counter32 2276 MAX-ACCESS read-only 2277 STATUS current 2278 DESCRIPTION 2279 "This object contains the total number of sequence 2280 number resets (payload packets with the R-bit set) 2281 received on this session." 2282 ::= { l2tpSessionStatsEntry 36 } 2284 -- 2285 -- The L2TP Tunnel Mapping Table 2286 -- 2287 -- This table is intended to assist management 2288 -- applications to quickly determine what the ifIndex 2289 -- value is for a given local tunnel identifier. 2291 l2tpTunnelMapTable OBJECT-TYPE 2292 SYNTAX SEQUENCE OF L2tpTunnelMapEntry 2293 MAX-ACCESS not-accessible 2294 STATUS current 2295 DESCRIPTION 2296 "The L2TP Tunnel index mapping table." 2297 ::= { l2tpObjects 8 } 2299 l2tpTunnelMapEntry OBJECT-TYPE 2300 SYNTAX L2tpTunnelMapEntry 2301 MAX-ACCESS not-accessible 2302 STATUS current 2303 DESCRIPTION 2304 "An L2TP tunnel index map entry." 2305 INDEX { l2tpTunnelMapLocalTID } 2306 ::= { l2tpTunnelMapTable 1 } 2308 L2tpTunnelMapEntry ::= 2309 SEQUENCE { 2310 l2tpTunnelMapLocalTID 2311 Integer32, 2312 l2tpTunnelMapIfIndex 2313 InterfaceIndex 2314 } 2316 l2tpTunnelMapLocalTID OBJECT-TYPE 2317 SYNTAX Integer32 (0..65535) 2318 MAX-ACCESS read-only 2319 STATUS current 2320 DESCRIPTION 2321 "This object contains the local tunnel Identifier." 2322 ::= { l2tpTunnelMapEntry 1 } 2324 l2tpTunnelMapIfIndex OBJECT-TYPE 2325 SYNTAX InterfaceIndex 2326 MAX-ACCESS read-only 2327 STATUS current 2328 DESCRIPTION 2329 "This value for this object is equal to the value 2330 of ifIndex of the Interfaces MIB for tunnel 2331 interfaces of type L2TP." 2333 ::= { l2tpTunnelMapEntry 2 } 2335 -- 2336 -- The L2TP Session Mapping Table 2337 -- 2338 -- This table is intended to assist management 2339 -- applications to quickly determine what the instance 2340 -- value is for a given upper or lower ifIndex. 2342 l2tpSessionMapTable OBJECT-TYPE 2343 SYNTAX SEQUENCE OF L2tpSessionMapEntry 2344 MAX-ACCESS not-accessible 2345 STATUS current 2346 DESCRIPTION 2347 "The L2TP Session index mapping table." 2348 ::= { l2tpObjects 9 } 2350 l2tpSessionMapEntry OBJECT-TYPE 2351 SYNTAX L2tpSessionMapEntry 2352 MAX-ACCESS not-accessible 2353 STATUS current 2354 DESCRIPTION 2355 "An L2TP Session index map entry." 2356 INDEX { l2tpSessionMapHLifIndex } 2357 ::= { l2tpSessionMapTable 1 } 2359 L2tpSessionMapEntry ::= 2360 SEQUENCE { 2361 l2tpSessionMapHLifIndex 2362 InterfaceIndex, 2363 l2tpSessionMapTunnelIfIndex 2364 InterfaceIndex, 2365 l2tpSessionMapLocalCID 2366 Integer32 2367 } 2369 l2tpSessionMapHLifIndex OBJECT-TYPE 2370 SYNTAX InterfaceIndex 2371 MAX-ACCESS read-only 2372 STATUS current 2373 DESCRIPTION 2374 "This object identifies the ifIndex value of the 2375 interface that is either below (Lower) the tunnel 2376 (if this tunnel endpoint is a LAC) or above 2377 (Higher) the tunnel (if this tunnel endpoint is a 2378 LNS). For example this could be a DS0 ifIndex on a 2379 LAC or it would be the PPP ifIndex on the LNS. 2380 ::= { l2tpSessionMapEntry 1 } 2382 l2tpSessionMapTunnelIfIndex OBJECT-TYPE 2383 SYNTAX InterfaceIndex 2384 MAX-ACCESS read-only 2385 STATUS current 2386 DESCRIPTION 2387 "This object identifies the sessions associated 2388 L2TP tunnel ifIndex value." 2389 ::= { l2tpSessionMapEntry 2 } 2391 l2tpSessionMapLocalCID OBJECT-TYPE 2392 SYNTAX Integer32 (0..65535) 2393 MAX-ACCESS read-only 2394 STATUS current 2395 DESCRIPTION 2396 "This object contains the local call identifier 2397 for the session." 2398 ::= { l2tpSessionMapEntry 3 } 2400 -- 2401 -- { l2tpIpUdpObjects 1 } reserved for future use 2402 -- 2403 -- The L2TP IP/UDP Transport Status and Statistics Table 2404 -- 2405 -- This table contains objects that can be used to 2406 -- describe the current status and statistics of the 2407 -- IP/UDP L2TP tunnel transport. 2409 l2tpUdpStatsTable OBJECT-TYPE 2410 SYNTAX SEQUENCE OF L2tpUdpStatsEntry 2411 MAX-ACCESS not-accessible 2412 STATUS current 2413 DESCRIPTION 2414 "The L2TP IP/UDP transport stats table." 2415 ::= { l2tpIpUdpObjects 2 } 2417 l2tpUdpStatsEntry OBJECT-TYPE 2418 SYNTAX L2tpUdpStatsEntry 2419 MAX-ACCESS not-accessible 2420 STATUS current 2421 DESCRIPTION 2422 "An L2TP IP/UDP transport stats entry." 2423 INDEX { l2tpUdpStatsIfIndex } 2424 ::= { l2tpUdpStatsTable 1 } 2426 L2tpUdpStatsEntry ::= 2427 SEQUENCE { 2428 l2tpUdpStatsIfIndex 2429 InterfaceIndex, 2430 l2tpUdpStatsPeerPort 2431 Integer32, 2432 l2tpUdpStatsLocalPort 2433 Integer32 2434 } 2436 l2tpUdpStatsIfIndex OBJECT-TYPE 2437 SYNTAX InterfaceIndex 2438 MAX-ACCESS read-only 2439 STATUS current 2440 DESCRIPTION 2441 "This value for this object is equal to the 2442 value of ifIndex of the Interfaces MIB for 2443 tunnel interfaces of type L2TP and which have 2444 a L2TP transport of IP/UDP." 2445 ::= { l2tpUdpStatsEntry 1 } 2447 l2tpUdpStatsPeerPort OBJECT-TYPE 2448 SYNTAX Integer32 (0..65535) 2449 MAX-ACCESS read-only 2450 STATUS current 2451 DESCRIPTION 2452 "This object reflects the peer's UDP port number 2453 of the last packet received." 2454 ::= { l2tpUdpStatsEntry 2 } 2456 l2tpUdpStatsLocalPort OBJECT-TYPE 2457 SYNTAX Integer32 2458 MAX-ACCESS read-only 2459 STATUS current 2460 DESCRIPTION 2461 "This object reflects the local UDP port number 2462 that this tunnel is bound to." 2463 ::= { l2tpUdpStatsEntry 3 } 2465 -- 2466 -- Definition of generic L2TP traps 2467 -- 2469 l2tpTunnelAuthFailure NOTIFICATION-TYPE 2470 OBJECTS { 2471 l2tpTunnelStatsIfIndex, 2472 l2tpTunnelStatsInitiated, 2473 l2tpTunnelStatsRemoteHostName 2474 } 2475 STATUS current 2476 DESCRIPTION 2477 "A l2tpTunnelAuthFailure trap signifies that an 2478 attempt to establish a tunnel to a remote peer 2479 has failed authentication." 2480 ::= { l2tpTraps 1 } 2482 -- 2483 -- conformance information 2484 -- 2486 l2tpGroups OBJECT IDENTIFIER ::= { l2tpConformance 1 } 2487 l2tpCompliances OBJECT IDENTIFIER ::= { l2tpConformance 2 } 2489 -- 2490 -- compliance statements 2491 -- 2493 l2tpCompliance MODULE-COMPLIANCE 2494 STATUS current 2495 DESCRIPTION 2496 "The compliance statement for SNMPv2 entities 2497 which implement the L2TP MIB." 2499 MODULE -- this module 2501 -- unconditionally mandatory groups 2502 MANDATORY-GROUPS { 2503 l2tpConfigGroup, 2504 l2tpStatsGroup 2505 } 2507 -- conditionally mandatory groups 2508 GROUP l2tpIpUdpGroup 2509 DESCRIPTION 2510 "This group is mandatory for implementations that 2511 support L2TP over IP/UDP." 2513 -- optional groups 2514 GROUP l2tpDomainGroup 2515 DESCRIPTION 2516 "This group is optional for L2TP devices that desire 2517 to group tunnel endpoints into tunnel domains." 2519 GROUP l2tpMappingGroup 2520 DESCRIPTION 2521 "This group is optional for L2TP devices that wish 2522 to provide index mapping." 2524 ::= { l2tpCompliances 1 } 2526 -- units of conformance 2528 l2tpConfigGroup OBJECT-GROUP 2529 OBJECTS { 2530 l2pAdminState, 2531 l2tpTunnelConfigAuthentication, 2532 l2tpTunnelConfigSecret, 2533 l2tpTunnelConfigSecurity, 2534 l2tpTunnelConfigHelloInterval, 2535 l2tpTunnelConfigIdleTimeout, 2536 l2tpTunnelConfigControlRWS, 2537 l2tpTunnelConfigControlRetransmissions, 2538 l2tpTunnelConfigPayloadSequencing, 2539 l2tpTunnelConfigPayloadRWS, 2540 l2tpTunnelConfigDelayedAckTimeout, 2541 l2tpTunnelConfigReassemblyTimeout, 2542 l2tpTunnelConfigTransport 2543 } 2544 STATUS current 2545 DESCRIPTION 2546 "A collection of objects providing configuration 2547 information of the L2TP protocol, tunnels and sessions." 2548 ::= { l2tpGroups 1 } 2550 l2tpStatsGroup OBJECT-GROUP 2551 OBJECTS { 2552 l2tpProtocolVersion, 2553 l2tpVendorName, 2554 l2tpFirmwareRev, 2555 l2tpTunnelStatsIfIndex, 2556 l2tpTunnelStatsLocalTID, 2557 l2tpTunnelStatsRemoteTID, 2558 l2tpTunnelStatsState, 2559 l2tpTunnelStatsInitiated, 2560 l2tpTunnelStatsRemoteHostName, 2561 l2tpTunnelStatsRemoteVendorName, 2562 l2tpTunnelStatsRemoteFirmwareRevision, 2563 l2tpTunnelStatsRemoteProtocolVersion, 2564 l2tpTunnelStatsInitialRemoteRWS, 2565 l2tpTunnelStatsBearerCapabilities, 2566 l2tpTunnelStatsFramingCapabilities, 2567 l2tpTunnelStatsControlRecvPackets, 2568 l2tpTunnelStatsControlRecvZLB, 2569 l2tpTunnelStatsControlOutOfSequence, 2570 l2tpTunnelStatsControlOutOfWindow, 2571 l2tpTunnelStatsControlSendPackets, 2572 l2tpTunnelStatsControlSendZLB, 2573 l2tpTunnelStatsControlAckTimeouts, 2574 l2tpTunnelStatsCurrentRemoteRWS, 2575 l2tpTunnelStatsSendSeq, 2576 l2tpTunnelStatsSendSeqAck, 2577 l2tpTunnelStatsRecvSeq, 2578 l2tpTunnelStatsRecvSeqAck, 2579 l2tpTunnelStatsTotalSessions, 2580 l2tpTunnelStatsFailedSessions, 2581 l2tpTunnelStatsActiveSessions, 2582 l2tpTunnelStatsLastResultCode, 2583 l2tpTunnelStatsLastErrorCode, 2584 l2tpTunnelStatsLastErrorMessage, 2585 l2tpSessionStatsTunnelIfIndex, 2586 l2tpSessionStatsHLIfIndex, 2587 l2tpSessionStatsLocalCID, 2588 l2tpSessionStatsRemoteCID, 2589 l2tpSessionStatsUserName, 2590 l2tpSessionStatsState, 2591 l2tpSessionStatsCallType, 2592 l2tpSessionStatsCallSerialNumber, 2593 l2tpSessionStatsTxConnectSpeed, 2594 l2tpSessionStatsRxConnectSpeed, 2595 l2tpSessionStatsCallBearerType, 2596 l2tpSessionStatsFramingType, 2597 l2tpSessionStatsPhysChanId, 2598 l2tpSessionStatsDNIS, 2599 l2tpSessionStatsCLID, 2600 l2tpSessionStatsSubAddress, 2601 l2tpSessionStatsPrivateGroupID, 2602 l2tpSessionStatsProxyLcp, 2603 l2tpSessionStatsAuthMethod, 2604 l2tpSessionStatsLocalRWS, 2605 l2tpSessionStatsRemoteInitialRWS, 2606 l2tpSessionStatsRemotePPD, 2607 l2tpSessionStatsSequencingState, 2608 l2tpSessionStatsRecvZLB, 2609 l2tpSessionStatsOutSequence, 2610 l2tpSessionStatsOutOfWindow, 2611 l2tpSessionStatsSendZLB, 2612 l2tpSessionStatsAckTimeouts, 2613 l2tpSessionStatsReassemblyTimeouts, 2614 l2tpSesssionStatsCurrentRemoteRWS, 2615 l2tpSessionStatsSendSeq, 2616 l2tpSessionStatsSendSeqAck, 2617 l2tpSessionStatsSendSeqResets, 2618 l2tpSessionStatsRecvSeq, 2619 l2tpSessionStatsRecvSeqAck, 2620 l2tpSessionStatsRecvSeqResets 2621 } 2622 STATUS current 2623 DESCRIPTION 2624 "A collection of objects providing status and 2625 statistics of the L2TP protocol, tunnels and 2626 sessions." 2627 ::= { l2tpGroups 2 } 2629 l2tpIpUdpGroup OBJECT-GROUP 2630 OBJECTS { 2631 l2tpUdpStatsIfIndex, 2632 l2tpUdpStatsPeerPort, 2633 l2tpUdpStatsLocalPort, 2634 } 2635 STATUS current 2636 DESCRIPTION 2637 "A collection of objects providing status and 2638 statistics of the L2TP IP/UDP transport layer." 2639 ::= { l2tpGroups 3 } 2641 l2tpDomainGroup OBJECT-GROUP 2642 OBJECTS { 2643 l2pDomainConfigAdminState, 2644 l2tpDomainConfigAuthentication, 2645 l2tpDomainConfigSecret, 2646 l2tpDomainConfigTunnelSecurity, 2647 l2tpDomainConfigTunnelHelloInterval, 2648 l2tpDomainConfigTunnelIdleTimeout, 2649 l2tpDomainConfigControlRWS, 2650 l2tpDomainConfigControlRetransmissions, 2651 l2tpDomainConfigPayloadSequencing, 2652 l2tpDomainConfigPayloadRWS, 2653 l2tpDomainConfigDelayedAckTimeout, 2654 l2tpDomainConfigReassemblyTimeout, 2655 l2tpDomainConfigStatus, 2656 l2tpDomainStatsTotalTunnels, 2657 l2tpDomainStatsFailedTunnels, 2658 l2tpDomainStatsFailedAuthentications, 2659 l2tpDomainStatsActiveTunnels, 2660 l2tpDomainStatsTotalSessions, 2661 l2tpDomainStatsFailedSessions, 2662 l2tpDomainStatsActiveSessions, 2663 l2tpDomainStatsControlRecvOctets, 2664 l2tpDomainStatsControlRecvPackets, 2665 l2tpDomainStatsControlSendOctets, 2666 l2tpDomainStatsControlSendPackets, 2667 l2tpDomainStatsPayloadRecvOctets, 2668 l2tpDomainStatsPayloadRecvPackets, 2669 l2tpDomainStatsPayloadRecvDiscards, 2670 l2tpDomainStatsPayloadSendOctets, 2671 l2tpDomainStatsPayloadSendPackets 2672 } 2673 STATUS current 2674 DESCRIPTION 2675 "A collection of objects providing configuration, 2676 status and statistics of L2TP tunnel domains." 2677 ::= { l2tpGroups 4 } 2679 l2tpDomainGroup OBJECT-GROUP 2680 OBJECTS { 2681 l2tpTunnelMapLocalTID, 2682 l2tpTunnelMapIfIndex, 2683 l2tpSessionMapHLifIndex, 2684 l2tpSessionMapTunnelIfIndex, 2685 l2tpSessionMapLocalCID 2686 } 2687 STATUS current 2688 DESCRIPTION 2689 "A collection of objects providing index mapping." 2690 ::= { l2tpGroups 5 } 2692 END 2694 5.0 Acknowledgements 2696 This MIB module was updated based on feedback from the IETF's 2697 Point-to-Point Protocol Extensions (PPPEXT) Working Group. 2699 6.0 References 2701 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2702 Describing SNMP Management Frameworks", RFC 2271, Cabletron 2703 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 2704 January 1998 2706 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 2707 Management Information for TCP/IP-based Internets", RFC 1155, 2708 Performance Systems International, Hughes LAN Systems, May 1990 2710 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 2711 Performance Systems International, Hughes LAN Systems, March 1991 2713 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 2714 RFC 1215, Performance Systems International, March 1991 2716 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2717 Waldbusser, "Structure of Management Information for Version 2 of 2718 the Simple Network Management Protocol (SNMPv2)", RFC 1902, SNMP 2719 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2720 International Network Services, January 1996. 2722 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2723 Waldbusser, "Textual Conventions for Version 2 of the Simple 2724 Network Management Protocol (SNMPv2)", RFC 1903, SNMP Research, 2725 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2726 International Network Services, January 1996. 2728 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2729 Waldbusser, "Conformance Statements for Version 2 of the Simple 2730 Network Management Protocol (SNMPv2)", RFC 1904, SNMP Research, 2731 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2732 International Network Services, January 1996. 2734 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 2735 Management Protocol", RFC 1157, SNMP Research, Performance Systems 2736 International, Performance Systems International, MIT Laboratory 2737 for Computer Science, May 1990. 2739 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2740 Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 2741 SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 2742 Inc., International Network Services, January 1996. 2744 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2745 Waldbusser, "Transport Mappings for Version 2 of the Simple Network 2746 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco 2747 Systems, Inc., Dover Beach Consulting, Inc., International Network 2748 Services, January 1996. 2750 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2751 Processing and Dispatching for the Simple Network Management 2752 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 2753 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 2755 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 2756 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2757 2274, IBM T. J. Watson Research, January 1998. 2759 [13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2760 Waldbusser, "Protocol Operations for Version 2 of the Simple 2761 Network Management Protocol (SNMPv2)", RFC 1905, SNMP Research, 2762 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2763 International Network Services, January 1996. 2765 [14] Levi, D., Meyer, P., and B. Stewart, MPv3 Applications", RFC 2273, 2766 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 2767 January 1998. 2769 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2770 Control Model (VACM) for the Simple Network Management Protocol 2771 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 2772 Cisco Systems, Inc., January 1998. 2774 [16] Valencia et al., "Layer Two Tunneling Protocol - L2TP", 2775 Internet draft (work in progress), 2776 draft-ietf-pppext-l2tp-10.txt, March, 1998. 2778 [17] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", 2779 Work In Progress, Cisco Systems, Argon Networks, 2780 July 1998. 2782 [18] Thaler, D., "IP Tunnel MIB" , Work In Progress, Microsoft, July 1998. 2784 7.0 Authors' Addresses 2786 Pat Calhoun 2787 Sun MicroComputer Corp. 2788 15 Network Circle 2789 Menlo Park, CA, 94025 2790 Pat.Calhoun@Eng.Sun.Com 2792 Gayam Reddy 2793 3Com Corporation 2794 1800 W. Central Ave 2795 Mount Prospect, Il 60031 2796 greddy@usr.com 2798 Bill Vroman 2799 3Com Corporation 2800 1800 W. Central Ave 2801 Mount Prospect, Il 60031 2802 bvroman@usr.com 2804 Ross Wheeler 2805 RouterWare 2806 3961 MacArthur Blvd, Suite 212 2807 Newport Beach, CA 92660 2808 ross@routerware.com 2810 Evan Caves 2811 Advanced Computer Communications 2812 340 Storke Road 2813 Santa Barbara, CA 93117 2814 evan@acc.com