idnits 2.17.1 draft-ietf-pppext-l2tp-mib-02.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-19) 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 58 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 352: '...s below, all objects MUST be supported...' RFC 2119 keyword, line 368: '... interfaces MUST be supported as described in [17]....' RFC 2119 keyword, line 456: '... interfaces MUST be supported as described in [17]....' RFC 2119 keyword, line 948: '...be discarded (which MAY causes the PPP...' RFC 2119 keyword, line 1396: '... (which MAY causes the PPP de...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 2027 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-02.txt Bill Vroman 6 Date: August 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 ............................................. 2 50 2.0 The SNMP Management Framework .......................... 3 52 3.0 Overview ............................................... 4 53 3.1 Relationship to the Interface MIB ...................... 5 54 3.1.1 Layering Model ....................................... 5 55 3.1.2 Interface MIB Objects ................................ 8 56 3.1.2.1 L2TP Tunnel Interfaces ............................. 8 57 3.1.2.2 L2TP Session Interfaces ............................ 10 58 3.2 Relationship to other MIBs ............................. 12 59 3.2.1 Relationship to the IP Tunnel MIB .................... 12 60 3.3 L2TP Tunnel Creation ................................... 12 62 4.0 L2TP Object Definitions ................................ 14 64 5.0 Acknowledgements ....................................... 67 66 6.0 References ............................................. 67 68 7.0 Authors' Addresses ..................................... 68 70 1.0 Introduction 72 This memo defines a portion of the Management Information Base (MIB) 73 for use with network management protocols in the Internet Community. 74 In particular, it describes managed objects used for managing L2TP 75 devices. 77 1.1 Change Log 79 This section tracks changes made to the revisions of the Internet 80 Drafts of this document. It will be *deleted* when the document is 81 published as an RFC. 83 3 November 1997 85 The following changes were made for the version of the document dated 86 3 November 1997. These changes were made at the request of the L2TP 87 working group. 89 (1) Removed L2TP protocol stack instancing. 91 (2) Tunnel and Session table now extensions of ifTable. 93 (3) Added IP/UDP transport tables. 95 (4) Several objects were removed and a number of new 96 objects added. 98 (5) Sections 1.1, 2.1, 3.0, 5.0 and 6.0 added. 100 (6) Module Compliance information added. 102 27 July 1998 104 The following changes were made for the version of the document dated 105 27 July 1998. These changes were made as a result of the L2TP MIB 106 presentation during the forty-first IETF in Los Angeles. 108 (1) Added Tunnel Domain configuration and stats tables. 110 (2) Moved most of the scalar configuration and stats objects 111 into the Tunnel Domain tables. 113 (3) Redundant objects removed. 115 (4) Some re-organization and object naming clarifications. 117 (5) Updated section 2.0 119 (6) Introduction of L2TP notifications 121 (7) Removed l2tpUdpConfigTable in favour of the tunnelConfigTable 123 (8) Updated section 3.0 125 2.0 The SNMP Management Framework 127 The SNMP Management Framework presently consists of five major 128 components: 130 o An overall architecture, described in RFC 2271 [1]. 132 o Mechanisms for describing and naming objects and 133 events for the purpose of management. The first 134 version of this Structure of Management Information 135 (SMI) is called SMIv1 and described in RFC 1155 [2], 136 RFC 1212 [3] and RFC 1215 [4]. The second version, 137 called SMIv2, is described in RFC 1902 [5], 138 RFC 1903 [6] and RFC 1904 [7]. 140 o Message protocols for transferring management 141 information. The first version of the SNMP 142 message protocol is called SNMPv1 and described in 143 RFC 1157 [8]. A second version of the SNMP message 144 protocol, which is not an Internet standards track 145 protocol, is called SNMPv2c and described in 146 RFC 1901 [9] and RFC 1905 [13]. The third version 147 of the message protocol is called SNMPv3 and 148 described in RFC 1906 [10], RFC 2272 [11] and 149 RFC 2274 [12]. 151 o Protocol operations for accessing management 152 information. The first set of protocol operations 153 and associated PDU formats is described in 154 RFC 1157 [8]. A second set of protocol operations 155 and associated PDU formats is described in 156 RFC 1905 [13]. 158 o A set of fundamental applications described in 159 RFC 2273 [14] and the view-based access control 160 mechanism described in RFC 2275 [15]. 162 Managed objects are accessed via a virtual information store, termed 163 the Management Information Base or MIB. Objects in the MIB are 164 defined using the mechanisms defined in the SMI. 166 This memo specifies a MIB module that is compliant to the SMIv2. A 167 MIB conforming to the SMIv1 can be produced through the appropriate 168 translations. The resulting translated MIB must be semantically 169 equivalent, except where objects or events are omitted because no 170 translation is possible (e.g., use of Counter64). Some machine 171 readable information in SMIv2 will be converted into textual 172 descriptions in SMIv1 during the translation process. However, this 173 loss of machine readable information is not considered to change the 174 semantics of the MIB. 176 3.0 Overview 178 The objects defined in this MIB are to be used when describing Layer 179 Two Tunneling Protocol (L2TP) tunnels. The L2TP protocol is defined 180 in [16]. This MIB consists of four groups briefly described below: 182 l2tpConfigGroup 183 l2tpStatsGroup 184 These two groups of objects provide information on the configuration, 185 state and statistics of the L2TP protocol, its tunnels and sessions. 186 These groups are mandatory for implementors of this MIB. 188 l2tpDomainGroup 189 This optional group of objects provides configuration, state and 190 statistical information for L2TP tunnel endpoint domains. A L2TP 191 tunnel endpoint domain is considered to be a collection of L2TP 192 devices typically belonging to a common administrative domain or 193 geographic location. 195 l2tpIpUdpGroup 196 This group provides the state and statistics information for L2TP 197 tunnels which are being transported by IP/UDP. This group is 198 mandatory for L2TP implementations that support L2TP over IP/UDP. 200 3.1 Relationship to the Interface MIB 202 This section clarifies the relationship of this MIB to the Interfaces 203 MIB [17]. Several areas of correlation are addressed in the following 204 subsections. The implementor is referred to the Interfaces MIB document 205 in order to understand the general intent of these areas. 207 3.1.1 Layering Model 209 This MIB contains several tables which are extensions to the 210 IP Tunnel MIB described in [18] which itself defines extensions 211 to the Interface MIB [17]. A L2TP tunnel and each of the PPP 212 sessions multiplexed within it are represented as separate 213 identifiable logical interface sub-layers. The tunnel and session 214 interfaces appear in the ifStackTable at different sub-layers 215 depending on the functionality the tunnel endpoint is providing 216 for each session. At the LAC end of a tunnel endpoint the tunnel 217 interface appears above the session interfaces. At the LNS end 218 of a tunnel endpoint the tunnel interface appears below the 219 session interfaces. 221 In the example diagram below, the interface layering is shown as it 222 appears at the LNS. Note that the L2TP tunnel interface is at the 223 bottom of the interface stack when the transport layer for L2TP is 224 IP/UDP. This is because tunneled traffic is forwarded to its 225 destination based on routing policy. However L2TP over transports 226 other than IP/UDP may define further sub-layer interfaces below 227 the tunnel interface. 229 In both diagrams the acronym "LSI" is used to indicate "L2TP Session 230 I/F". 232 +-------------------------------------------------+ 233 | Network Layer Protocol | 234 +-------------+-------------+--------+------------+ 235 | | | 236 +-+--+ | | 237 |MPPP| | | <=== PPP Multilink I/F 238 ++--++ | | 239 | | | | 240 +--+ +--+ | | 241 | | | | 242 +-+-+ +-+-+ +-+-+ +-+-+ 243 |PPP| |PPP| |PPP| |PPP| <=== PPP I/F 244 +-+-+ +-+-+ +-+-+ +-+-+ 245 | | | | 246 +-+-+ +-+-+ +-+-+ +-+-+ 247 |LSI| |LSI| |LSI| |LSI| <=== L2TP Session I/F 248 +-+-+ +-+-+ +-+-+ +-+-+ 249 | | | | 250 +---------+--------+--------+--------+------------+ 251 | L2TP Tunnel I/F | 252 +-------------------------------------------------+ 254 The ifStackTable is used to describe the layering of the interface 255 sub-layers. For the example given above the ifTable and ifStackTable 256 may appear as follows: 258 ifIndex ifType Tunnel MIB tables Description 260 1 tunnel(131) tunnelIfTable Tunnel Interface 261 l2tpTunnelConfigTable 262 l2tpTunnelStatsTable 263 2 session(??) l2tpSessionStatsTable Tunnel Session Interface #1 264 3 session(??) l2tpSessionStatsTable Tunnel Session Interface #2 265 4 session(??) l2tpSessionStatsTable Tunnel Session Interface #3 266 5 session(??) l2tpSessionStatsTable Tunnel Session Interface #4 267 6 ppp(23) subordinate entry #1 268 7 ppp(23) subordinate entry #2 269 8 ppp(23) subordinate entry #3 270 9 ppp(23) subordinate entry #4 271 10 mlppp(108) subordinate entries #1,#2 273 The corresponding ifStack table entries would then be: 275 ifStackTable Entries 276 HigherLayer LowerLayer 277 0 10 278 0 8 279 0 9 280 1 0 281 2 1 282 3 1 283 4 1 284 5 1 285 6 2 286 7 3 287 8 4 288 9 5 289 10 6 290 10 7 292 The following example diagram illustrates the interface layering as 293 it might occur at the LAC. In this case the tunnel interface is at 294 the top of the interface stack for L2TP over IP/UDP. 296 +-------------------------------------------------+ 297 | L2TP Tunnel I/F | 298 +---------+--------+--------+--------+------------+ 299 | | | | 300 +-+-+ +-+-+ +-+-+ +-+-+ 301 |LSI| |LSI| |LSI| |LSI| <=== L2TP Session I/F 302 +-+-+ +-+-+ +-+-+ +-+-+ 303 | | | | 304 +-+-+ +-+-+ +-+-+ +-+-+ 305 |ds0| |ds0| |ds0| |ds0| <=== B channels I/F 306 +-+-+ +-+-+ +-+-+ +-+-+ 307 | | | | 308 +---------+--------+--------+--------+------------+ 309 | ds1 | 310 +-------------------------------------------------+ 312 For the example given above the ifTable and ifStackTable may appear 313 as follows: 315 ifIndex ifType Tunnel MIB tables Description 317 1 ds1(18) Primary Rate physical interface 318 2 ds0(81) B channel #1 319 3 ds0(81) B channel #2 320 4 ds0(81) B channel #3 321 5 ds0(81) B channel #4 322 6 session(??) l2tpSessionStatsTable L2TP Session Interface #1 323 7 session(??) l2tpSessionStatsTable L2TP Session Interface #2 324 8 session(??) l2tpSessionStatsTable L2TP Session Interface #3 325 9 session(??) l2tpSessionStatsTable L2TP Session Interface #4 326 10 tunnel(131) tunnelIfTable Tunnel Interface 327 l2tpTunnelConfigTable 328 l2tpTunnelStatsTable 330 The corresponding ifStack table entries would then be: 332 ifStackTable Entries 334 HigherLayer LowerLayer 335 0 10 336 1 0 337 2 1 338 3 1 339 4 1 340 5 1 341 6 2 342 7 3 343 8 4 344 9 5 345 10 6 346 10 7 347 10 8 348 10 9 350 3.1.2 Interface MIB Objects 352 Except where noted in the tables below, all objects MUST be supported 353 from the ifGeneralInformationGroup and one of the following three groups: 355 o ifPacketGroup OR 356 o ifHCPacketGroup OR 357 o ifVHCPacketGroup 359 depending on the particular implementation. 361 The following tables describe how objects from the ifGeneralInformationGroup 362 and ifPacketGroup (similar support should be provided for the high and very 363 high capacity packet groups) are to be interpreted and supported for both 364 L2TP tunnel interfaces and L2TP session interfaces. 366 3.1.2.1 L2TP Tunnel Interfaces 367 All Interface MIB objects not listed in the above groups for L2TP tunnel 368 interfaces MUST be supported as described in [17]. 370 Interface MIB Object Support Description 371 ==================== ======================================= 372 ifTable.ifDescr Refer to the Interface MIB. 374 ifTable.ifType tunnel(131) 376 ifTable.ifMtu Dependant on the tunnel transport layer. 377 For IP/UDP transports the MTU should 378 be 65467 (65535-60(IP)-8(UDP)) 380 ifTable.ifSpeed Return zero. 382 ifTable.ifPhyAddress The assigned tunnel identifier. 384 ifTable.ifAdminStatus All enumerated values supported as per 385 DESCRIPTION clause in the Interfaces MIB. 387 ifTable.ifOperStatus All status events supported. Refer to the 388 Interfaces MIB. 390 ifTable.ifInOctets The total number of octets received on the 391 tunnel including control and payload 392 octets. 394 ifTable.ifInUcastPkts The total number of packets received on 395 the tunnel including control and payload 396 packets. 398 ifTable.ifInDiscards The total number of received packets that 399 were discarded on both control and payload 400 channels. 402 ifTable.ifInErrors The total number of packets received in 403 error including control and payload 404 packets. 406 ifTable.ifInUnknownProtos 407 Return zero. 409 ifTable.ifOutOctets The total number of octets transmitted from 410 the tunnel including control and payload 411 octets. 413 ifTable.ifOutUcastPkts The total number of packets transmitted from 414 the tunnel including control and payload 415 packets. 417 ifTable.ifOutDiscards The total number of discarded packets that 418 were requested to be transmitted including 419 control and payload packets. 421 ifTable.ifOutErrors The total number of packets that were requested 422 to be transmitted that were in error including 423 control and payload packets. 425 ifXTable.ifName Refer to the Interface MIB. 427 ifXTable.ifInMulticastPkts 428 Return zero. 430 ifXTable.ifInBroadcastPkts 431 Return zero. 433 ifXTable.ifOutMulticastPkts 434 Return zero. 436 ifXTable.ifOutBroadcastPkts 437 Return zero. 439 ifXTable.ifOutBroadcastPkts 440 Return zero. 442 ifXTable.ifLinkUpDownTrapEnable 443 Default set to enabled(1). 445 ifXTable.ifHighSpeed Return zero. 447 ifXTable.ifPromiscuousMode 448 Set to false(2). 450 ifXTable.ifConnectorPresent 451 Set to false(2). 453 3.1.2.2 L2TP Session Interfaces 455 All Interface MIB objects not listed in the above groups for L2TP session 456 interfaces MUST be supported as described in [17]. 458 Interface MIB Object Support Description 459 ==================== ======================================= 460 ifTable.ifDescr Refer to the Interface MIB. 462 ifTable.ifType tunnel session (??) 464 ifTable.ifMtu Dependant on the MRU negotiated by PPP. 465 Maximum size for IP/UDP transports is 466 65467 (65535-60(IP)-8(UDP)) 468 ifTable.ifSpeed Return the value of (Tx) Connect Speed 469 or zero if unknown. 471 ifTable.ifPhyAddress The assigned call identifier. 473 ifTable.ifAdminStatus All enumerated values supported as per 474 DESCRIPTION clause in the Interfaces MIB. 476 ifTable.ifOperStatus All status events supported. Refer to the 477 Interfaces MIB. 479 ifTable.ifInOctets The total number of octets received on the 480 payload channel. 482 ifTable.ifInUcastPkts The total number of packets received on 483 the payload channel. 485 ifTable.ifInDiscards The total number of received packets that 486 were discarded on the payload channel. 488 ifTable.ifInErrors The total number of packets received in 489 error on the payload channel. 491 ifTable.ifInUnknownProtos 492 Return zero. 494 ifTable.ifOutOctets The total number of octets sent on this 495 payload channel. 497 ifTable.ifOutUcastPkts The total number of packets sent on this 498 payload channel. 500 ifTable.ifOutDiscards The total number of packets that were 501 requested to be sent on the payload channel 502 but were discarded. Refer to the Interface 503 MIB. 505 ifTable.ifOutErrors The total number of packets that were 506 requested to be sent but were in error on 507 the payload channel. Refer to the Interface 508 MIB. 510 ifXTable.ifName Refer to the Interface MIB. 512 ifXTable.ifInMulticastPkts 513 Return zero. 515 ifXTable.ifInBroadcastPkts 516 Return zero. 518 ifXTable.ifOutMulticastPkts 519 Return zero. 521 ifXTable.ifOutBroadcastPkts 522 Return zero. 524 ifXTable.ifOutBroadcastPkts 525 Return zero. 527 ifXTable.ifLinkUpDownTrapEnable 528 Default set to disabled(2). 530 ifXTable.ifHighSpeed Return zero. 532 ifXTable.ifPromiscuousMode 533 Set to false(2). 535 ifXTable.ifConnectorPresent 536 Set to false(2). 538 3.2 Relationship to other MIBs 540 3.2.1 Relationship to the IP Tunnel MIB 542 The IP Tunnel MIB [18] describes tunnel interfaces that have an ifType 543 of tunnel(131). The IP Tunnel MIB is considered to contain a collection of 544 objects common to all IP tunneling protocols, including L2TP. In addition 545 to the IP Tunnel MIB, tunnel encapsulation specific MIBs (like this MIB) 546 extend the IP Tunnel MIB to further describe encapsulation specific 547 information. Implementation of the IP Tunnel MIB is required for L2TP 548 tunnels over IP. 550 3.3 L2TP Tunnel Creation 552 Tunnel creation is detailed for IP tunnels in the IP Tunnel MIB. The 553 creation of a tunnelIfEntry in [18] will have the side affect of 554 creating entries in the l2tpTunnelConfigTable, l2tpTunnelStatsTable 555 and the l2tpUdpStatsTable's. 557 The creation of L2TP tunnel interfaces over transports other than IP 558 is expected to be defined in the MIB definition for that specific 559 L2TP tunnel transport. 561 4.0 L2TP Object Definitions 563 L2TP-MIB DEFINITIONS ::= BEGIN 565 IMPORTS 566 Integer32, Counter32, experimental, Gauge32, 567 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE 568 FROM SNMPv2-SMI 569 TEXTUAL-CONVENTION, DisplayString, RowStatus, TruthValue 570 FROM SNMPv2-TC 571 OBJECT-GROUP, MODULE-COMPLIANCE 572 FROM SNMPv2-CONF 573 tunnelIfRemoteAddress 574 FROM TUNNEL-MIB 575 InterfaceIndex 576 FROM IF-MIB; 578 l2tp MODULE-IDENTITY 579 LAST-UPDATED "9808011800Z" 580 ORGANIZATION "IETF L2TP Working Group" 581 CONTACT-INFO 582 "Bill Vroman, Gayam Reddy 583 Postal: 3Com Corporation 584 1800 W. Central Rd 585 Mt. Prospect, IL 60056-2293 586 Tel: +1 847222 2008 587 +1 847222 2006 588 Email: bvroman, greddy@usr.com 590 Ross Wheeler 591 Postal: RouterWare 592 3961 MacArthur Blvd, Suite 212 593 Newport Beach, CA 92660 594 Tel: +1 714442 0770 595 Email: ross@routerware.com 597 Pat R. Calhoun 598 Postal: Sun Microsystems, Inc. 599 15 Network Circle 600 Menlo Park, CA, 94025 601 Tel: +1 650786 7733 602 Email: pcalhoun@eng.sun.com 604 Evan Caves 605 Postal: Advanced Computer Communications 606 340 Storke Road 607 Santa Barbara, CA 93117 608 Tel: +1 805685 4455 609 Email: evan@acc.com" 610 DESCRIPTION 611 "The MIB module that describes managed objects of 612 general use by the Layer Two Transport Protocol." 613 ::= { experimental 9999 1 } 615 -- 616 -- Textual Conventions 617 -- 619 MilliSeconds ::= TEXTUAL-CONVENTION 620 DISPLAY-HINT "d-3" 621 STATUS current 622 DESCRIPTION 623 "A period of time measured in units of .001 of seconds 624 when used in conjunction with the DISPLAY-HINT will 625 show seconds and fractions of second with a resolution 626 of .001 of a second." 627 SYNTAX Integer32 (0..2147483646) 629 -- 630 -- Definitions of significant branches 631 -- 632 l2tpObjects OBJECT IDENTIFIER ::= { l2tp 1 } 633 l2tpTraps OBJECT IDENTIFIER ::= { l2tp 2 } 634 l2tpTransports OBJECT IDENTIFIER ::= { l2tp 3 } 635 l2tpConformance OBJECT IDENTIFIER ::= { l2tp 4 } 637 -- 638 -- Definitions of significant branches under l2tpObjects 639 -- 640 l2tpScalar OBJECT IDENTIFIER ::= { l2tpObjects 1 } 641 l2tpConfig OBJECT IDENTIFIER ::= { l2tpScalar 1 } 642 l2tpStats OBJECT IDENTIFIER ::= { l2tpScalar 2 } 644 -- 645 -- Definitions of significant branches under l2tpTransports 646 -- 647 l2tpTransportIpUdp OBJECT IDENTIFIER ::= { l2tpTransports 1 } 648 l2tpIpUdpObjects OBJECT IDENTIFIER ::= { l2tpTransportIpUdp 1 } 649 l2tpIpUdpTraps OBJECT IDENTIFIER ::= { l2tpTransportIpUdp 2 } 650 -- 651 -- The L2TP Scalar Configuration Group 652 -- 653 -- This group of objects is used to manage configuration 654 -- of the L2TP protocol environment. 656 l2pAdminState OBJECT-TYPE 657 SYNTAX INTEGER { 658 enabled(1), 659 disabled(2), 660 drain(3) 661 } 662 MAX-ACCESS read-write 663 STATUS current 664 DESCRIPTION 665 "This object defines the administrative state of 666 this L2TP tunnel domain. Setting this object to 667 'disabled' causes all tunnels to be immediately 668 disconnected and no further tunnels to be either 669 initiated or accepted. Setting this object to 670 'drain' will prevent any new tunnels and/or 671 sessions to be either initiated or accepted but 672 does NOT disconnect any active tunnels/sessions." 673 DEFVAL { enabled } 674 ::= { l2tpConfig 1 } 676 -- 677 -- The L2TP Scalar Status and Statistics Group 678 -- 679 -- This group of objects describe the current state and 680 -- statistics of L2TP. 682 l2tpProtocolVersion OBJECT-TYPE 683 SYNTAX OCTET STRING (SIZE(2..256)) 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "Vector of supported L2TP protocol version and 688 revision numbers. Supported versions are identified 689 via a two octet pairing where the first octet indicates 690 the version and the second octet contains the revision." 691 ::= { l2tpStats 1 } 693 l2tpVendorName OBJECT-TYPE 694 SYNTAX DisplayString 695 MAX-ACCESS read-only 696 STATUS current 697 DESCRIPTION 698 "This object identifies the Vendor name of the L2TP 699 protocol stack." 700 ::= { l2tpStats 2 } 702 l2tpFirmwareRev OBJECT-TYPE 703 SYNTAX Integer32 704 MAX-ACCESS read-only 705 STATUS current 706 DESCRIPTION 707 "This object defines the firmware revision for the 708 L2TP protocol stack." 709 ::= { l2tpStats 3 } 711 -- 712 -- The L2TP Domain Configuration Table 713 -- 714 -- This table contains objects that can be used to 715 -- configure the operational characteristics of a tunnel 716 -- domain. 718 l2tpDomainConfigTable OBJECT-TYPE 719 SYNTAX SEQUENCE OF L2tpDomainConfigEntry 720 MAX-ACCESS not-accessible 721 STATUS current 722 DESCRIPTION 723 "The L2TP Domain configuration table." 724 ::= { l2tpObjects 2 } 726 l2tpDomainConfigEntry OBJECT-TYPE 727 SYNTAX L2tpDomainConfigEntry 728 MAX-ACCESS not-accessible 729 STATUS current 730 DESCRIPTION 731 "An L2TP Domain configuration entry. An entry in this 732 table may correspond to a single endpoint or a group 733 of tunnel endpoints." 734 INDEX { l2tpDomainConfigIdentifier } 735 ::= { l2tpDomainConfigTable 1 } 737 L2tpDomainConfigEntry ::= 738 SEQUENCE { 739 l2tpDomainConfigIdentifier 740 DisplayString, 741 l2pDomainConfigAdminState 742 INTEGER, 743 l2tpDomainConfigAuthentication 744 INTEGER, 745 l2tpDomainConfigTunnelSecurity 746 INTEGER, 747 l2tpDomainConfigTunnelHelloInterval 748 Integer32, 749 l2tpDomainConfigTunnelIdleTimeout 750 Integer32, 751 l2tpDomainConfigControlRWS 752 Integer32, 753 l2tpDomainConfigControlRetransmissions 754 Integer32, 755 l2tpDomainConfigPayloadSequencing 756 TruthValue, 757 l2tpDomainConfigPayloadRWS 758 Integer32, 760 l2tpDomainConfigDelayedAckTimeout 761 MilliSeconds, 762 l2tpDomainConfigReassemblyTimeout 763 MilliSeconds, 764 l2tpDomainConfigStatus 765 RowStatus 766 } 768 l2tpDomainConfigIdentifier OBJECT-TYPE 769 SYNTAX DisplayString 770 MAX-ACCESS not-accessible 771 STATUS current 772 DESCRIPTION 773 "The identifier, usually in the form of a Domain 774 Name (full or partial), describing a single tunnel 775 endpoint or a domain of tunnel endpoints. This is 776 typically used as a 'handle' to identify the 777 tunnel configuration requirements for both incoming 778 and outgoing tunnel connection attempts. Both the 779 LAC and LNS could use information provided in the 780 Host Name AVP however the tunnel initiator could use 781 other means not specified to identify the domains 782 tunnel configuration requirements." 783 ::= { l2tpDomainConfigEntry 1 } 785 l2pDomainConfigAdminState OBJECT-TYPE 786 SYNTAX INTEGER { 787 enabled(1), 788 disabled(2), 789 drain(3) 790 } 791 MAX-ACCESS read-create 792 STATUS current 793 DESCRIPTION 794 "This object defines the administrative state of this 795 tunnel domain. Setting this object to disabled(2) 796 causes all tunnels to be immediately disconnected 797 and no further tunnels to be either initiated or 798 accepted. Setting this object to drain(3) will prevent 799 any new tunnels and/or sessions to be either initiated 800 or accepted but does NOT forcibly disconnect any 801 active tunnels and/or sessions." 802 DEFVAL { enabled } 803 ::= { l2tpDomainConfigEntry 2 } 805 l2tpDomainConfigAuthentication OBJECT-TYPE 806 SYNTAX INTEGER { 807 none(1), 808 simple(2), 809 challenge(3) 810 } 811 MAX-ACCESS read-create 812 STATUS current 813 DESCRIPTION 814 "This object describes how tunnel peers belonging 815 to this domain are to be authenticated. The value 816 simple(2) indicates that peers are authenticated simply 817 by their host name as described in the Host Name AVP. 818 The value challenge(3) indicates that all peers are 819 challenged to prove their identification. This mechanism 820 is described in the L2TP protocol. How the tunnel 821 peers exchange tunnel secrets for this later case 822 is outside the scope of this document." 823 DEFVAL { none } 824 ::= { l2tpDomainConfigEntry 3 } 826 l2tpDomainConfigTunnelSecurity OBJECT-TYPE 827 SYNTAX INTEGER { 828 none(1), 829 other(2), 830 ipSec(3) 831 } 832 MAX-ACCESS read-create 833 STATUS current 834 DESCRIPTION 835 "This object defines whether this tunnel domain 836 requires that all tunnels are to be secured. The 837 value of ipsec(3) indicates that all tunnel packets, 838 control and session, have IP Security headers. The 839 type of IP Security headers (AH, ESP etc) and how 840 they are further described is outside the scope of 841 this document." 842 DEFVAL { none } 843 ::= { l2tpDomainConfigEntry 4 } 845 l2tpDomainConfigTunnelHelloInterval OBJECT-TYPE 846 SYNTAX Integer32 (0..3600) 847 MAX-ACCESS read-create 848 STATUS current 849 DESCRIPTION 850 "This object defines the interval (in seconds) in 851 which Hello (or keep-alive) packets are to be sent 852 by local peers belonging to this tunnel domain." 853 DEFVAL { 60 } 854 ::= { l2tpDomainConfigEntry 5 } 856 l2tpDomainConfigTunnelIdleTimeout OBJECT-TYPE 857 SYNTAX Integer32 (0..86400) 858 MAX-ACCESS read-create 859 STATUS current 860 DESCRIPTION 861 "This object defines the period of time (in seconds) 862 that an established tunnel belonging to this tunnel 863 domain with no active sessions will wait before 864 disconnecting the tunnel. A value of zero indicates 865 that the tunnel will disconnect immediately after the 866 last session disconnects." 867 DEFVAL { 0 } 868 ::= { l2tpDomainConfigEntry 6 } 870 l2tpDomainConfigControlRWS OBJECT-TYPE 871 SYNTAX Integer32 (1..64) 872 MAX-ACCESS read-create 873 STATUS current 874 DESCRIPTION 875 "This object defines the control channel receive 876 window size for tunnels belonging to this domain. It 877 specifies the maximum number of packets the tunnel 878 peer belonging to this domain can send without waiting 879 for an acknowledgement from this peer." 880 DEFVAL { 4 } 881 ::= { l2tpDomainConfigEntry 7 } 883 l2tpDomainConfigControlRetransmissions OBJECT-TYPE 884 SYNTAX Integer32 (0..32) 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "This object defines the number of retransmission's 889 which the L2TP stack will attempt for tunnels belonging 890 to this domain before assuming that the peer is no 891 longer responding." 892 DEFVAL { 4 } 893 ::= { l2tpDomainConfigEntry 8 } 895 l2tpDomainConfigPayloadSequencing OBJECT-TYPE 896 SYNTAX TruthValue 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "This object determines whether or not session payload 901 packets will be requested to be sent with sequence 902 numbers from tunnel peer's belonging to this domain." 903 DEFVAL { false } 904 ::= { l2tpDomainConfigEntry 9 } 906 l2tpDomainConfigPayloadRWS OBJECT-TYPE 907 SYNTAX Integer32 (0..65535) 908 MAX-ACCESS read-create 909 STATUS current 910 DESCRIPTION 911 "This object defines the payload sessions receive 912 window size. It specifies the maximum number of 913 packets the tunnel peer can send without waiting 914 for an acknowledgement from this peer or an 915 acknowledgement timeout occurs. If paylaod sequencing 916 is not configured for this tunnel domain then this 917 object may be used in the event that the tunnel peer 918 requests payload seqencing." 919 DEFVAL { 0 } 920 ::= { l2tpDomainConfigEntry 10 } 922 l2tpDomainConfigDelayedAckTimeout OBJECT-TYPE 923 SYNTAX MilliSeconds 924 MAX-ACCESS read-create 925 STATUS current 926 DESCRIPTION 927 "This object defines the number of milliseconds 928 which the local tunnel peer will wait to send an 929 acknowledgement to it's peer in the case where there 930 is no data packets to piggyback the acknowledgement 931 on. The default value for this object is zero which 932 results in an immediate acknowledgment to received 933 payload (data) packets. If payload sequencing is not 934 configured then this object should not be interpreted." 935 DEFVAL { 0 } 936 ::= { l2tpDomainConfigEntry 11 } 938 l2tpDomainConfigReassemblyTimeout OBJECT-TYPE 939 SYNTAX MilliSeconds 940 MAX-ACCESS read-create 941 STATUS current 942 DESCRIPTION 943 "This object defines the number of milliseconds that 944 local peer's of this tunnel domain will wait before 945 processing packets that were received out of sequence 946 (which are waiting for the packet(s) to put them in 947 sequence). A low value increases the chance of delayed 948 packets to be discarded (which MAY causes the PPP 949 decompression engine to reset) while a high value may 950 cause more queueing and possibly degrade throughput if 951 packets are truly lost. The default value for this 952 object is zero which will result in all delayed packets 953 being lost." 954 DEFVAL { 0 } 955 ::= { l2tpDomainConfigEntry 12 } 957 l2tpDomainConfigStatus OBJECT-TYPE 958 SYNTAX RowStatus 959 MAX-ACCESS read-create 960 STATUS current 961 DESCRIPTION 962 "The status of this Domain entry." 963 ::= { l2tpDomainConfigEntry 13 } 965 -- 966 -- The L2TP Domain Status and Statistics Table 967 -- 968 -- This table contains objects that can be used to desribe 969 -- the current status and statistics of a tunnel domain. 971 l2tpDomainStatsTable OBJECT-TYPE 972 SYNTAX SEQUENCE OF L2tpDomainStatsEntry 973 MAX-ACCESS not-accessible 974 STATUS current 975 DESCRIPTION 976 "The L2TP Domain Status and Statistics table." 977 ::= { l2tpObjects 3 } 979 l2tpDomainStatsEntry OBJECT-TYPE 980 SYNTAX L2tpDomainStatsEntry 981 MAX-ACCESS not-accessible 982 STATUS current 983 DESCRIPTION 984 "An L2TP Domain Stats entry. An entry in this table 985 may correspond to a single endpoint or a group of 986 tunnel endpoints." 987 INDEX { l2tpDomainStatsIdentifier } 988 ::= { l2tpDomainStatsTable 1 } 990 L2tpDomainStatsEntry ::= 991 SEQUENCE { 992 l2tpDomainStatsIdentifier 993 DisplayString, 994 l2tpDomainStatsTotalTunnels 995 Counter32, 996 l2tpDomainStatsFailedTunnels 997 Counter32, 998 l2tpDomainStatsFailedAuthentications 999 Counter32, 1000 l2tpDomainStatsActiveTunnels 1001 Gauge32, 1002 l2tpDomainStatsTotalSessions 1003 Counter32, 1004 l2tpDomainStatsFailedSessions 1005 Counter32, 1006 l2tpDomainStatsActiveSessions 1007 Gauge32, 1008 l2tpDomainStatsControlRecvOctets 1009 Counter32, 1010 l2tpDomainStatsControlRecvPackets 1011 Counter32, 1012 l2tpDomainStatsControlSendOctets 1013 Counter32, 1014 l2tpDomainStatsControlSendPackets 1015 Counter32, 1016 l2tpDomainStatsPayloadRecvOctets 1017 Counter32, 1018 l2tpDomainStatsPayloadRecvPackets 1019 Counter32, 1020 l2tpDomainStatsPayloadRecvDiscards 1021 Counter32, 1022 l2tpDomainStatsPayloadSendOctets 1023 Counter32, 1024 l2tpDomainStatsPayloadSendPackets 1025 Counter32 1026 } 1028 l2tpDomainStatsIdentifier OBJECT-TYPE 1029 SYNTAX DisplayString 1030 MAX-ACCESS not-accessible 1031 STATUS current 1032 DESCRIPTION 1033 "The identifier, usually in the form of a Domain 1034 Name (full or partial), describing a single tunnel 1035 endpoint or a domain of tunnel endpoints." 1036 ::= { l2tpDomainStatsEntry 1 } 1038 l2tpDomainStatsTotalTunnels OBJECT-TYPE 1039 SYNTAX Counter32 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "This object returns the total number of tunnels 1044 that have successfully reached the established 1045 state for this tunnel domain." 1046 ::= { l2tpDomainStatsEntry 2 } 1048 l2tpDomainStatsFailedTunnels OBJECT-TYPE 1049 SYNTAX Counter32 1050 MAX-ACCESS read-only 1051 STATUS current 1052 DESCRIPTION 1053 "This object returns the number of tunnels that 1054 failed to reach the established state for this 1055 tunnel domain." 1056 ::= { l2tpDomainStatsEntry 3 } 1058 l2tpDomainStatsFailedAuthentications OBJECT-TYPE 1059 SYNTAX Counter32 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "This object returns the number of failed tunnel 1064 connection attempts for this domain because the 1065 tunnel peer failed authentication." 1066 ::= { l2tpDomainStatsEntry 4 } 1068 l2tpDomainStatsActiveTunnels OBJECT-TYPE 1069 SYNTAX Gauge32 1070 MAX-ACCESS read-only 1071 STATUS current 1072 DESCRIPTION 1073 "This object returns the number of tunnels that 1074 are currently active for this domain." 1075 ::= { l2tpDomainStatsEntry 5 } 1077 l2tpDomainStatsTotalSessions OBJECT-TYPE 1078 SYNTAX Counter32 1079 MAX-ACCESS read-only 1080 STATUS current 1081 DESCRIPTION 1082 "This object returns the total number of sessions 1083 that have successfully reached the established state 1084 for this tunnel domain." 1085 ::= { l2tpDomainStatsEntry 6 } 1087 l2tpDomainStatsFailedSessions OBJECT-TYPE 1088 SYNTAX Counter32 1089 MAX-ACCESS read-only 1090 STATUS current 1091 DESCRIPTION 1092 "This object returns the number of sessions that 1093 failed to reach the established state for this 1094 tunnel domain." 1095 ::= { l2tpDomainStatsEntry 7 } 1097 l2tpDomainStatsActiveSessions OBJECT-TYPE 1098 SYNTAX Gauge32 1099 MAX-ACCESS read-only 1100 STATUS current 1101 DESCRIPTION 1102 "This object returns the number of sessions that 1103 are currently active for this domain." 1104 ::= { l2tpDomainStatsEntry 8 } 1106 l2tpDomainStatsControlRecvOctets OBJECT-TYPE 1107 SYNTAX Counter32 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "This object returns the number of control channel 1112 octets received for this tunnel domain." 1113 ::= { l2tpDomainStatsEntry 9 } 1115 l2tpDomainStatsControlRecvPackets OBJECT-TYPE 1116 SYNTAX Counter32 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION 1120 "This object returns the number of control packets 1121 received for this tunnel domain." 1122 ::= { l2tpDomainStatsEntry 10 } 1124 l2tpDomainStatsControlSendOctets OBJECT-TYPE 1125 SYNTAX Counter32 1126 MAX-ACCESS read-only 1127 STATUS current 1128 DESCRIPTION 1129 "This object returns the number of control channel 1130 octets that were transmitted to tunnel endpoints 1131 for this domain." 1132 ::= { l2tpDomainStatsEntry 11 } 1134 l2tpDomainStatsControlSendPackets OBJECT-TYPE 1135 SYNTAX Counter32 1136 MAX-ACCESS read-only 1137 STATUS current 1138 DESCRIPTION 1139 "This object returns the number of control packets 1140 that were transmitted to tunnel endpoints for 1141 this domain." 1142 ::= { l2tpDomainStatsEntry 12 } 1144 l2tpDomainStatsPayloadRecvOctets OBJECT-TYPE 1145 SYNTAX Counter32 1146 MAX-ACCESS read-only 1147 STATUS current 1148 DESCRIPTION 1149 "This object returns the number of payload channel 1150 octets that were received for this tunnel domain." 1151 ::= { l2tpDomainStatsEntry 13 } 1153 l2tpDomainStatsPayloadRecvPackets OBJECT-TYPE 1154 SYNTAX Counter32 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "This object returns the number of payload packets 1159 that were received for this tunnel domain." 1160 ::= { l2tpDomainStatsEntry 14 } 1162 l2tpDomainStatsPayloadRecvDiscards OBJECT-TYPE 1163 SYNTAX Counter32 1164 MAX-ACCESS read-only 1165 STATUS current 1166 DESCRIPTION 1167 "This object returns the number of received payload 1168 packets that were discarded by this this tunnel 1169 domain." 1170 ::= { l2tpDomainStatsEntry 15 } 1172 l2tpDomainStatsPayloadSendOctets OBJECT-TYPE 1173 SYNTAX Counter32 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "This object returns the number of payload channel 1178 octets that were transmitted to tunnel peers 1179 within this tunnel domain." 1180 ::= { l2tpDomainStatsEntry 16 } 1182 l2tpDomainStatsPayloadSendPackets OBJECT-TYPE 1183 SYNTAX Counter32 1184 MAX-ACCESS read-only 1185 STATUS current 1186 DESCRIPTION 1187 "This object returns the number of payload packets 1188 that were transmitted to tunnel peers within 1189 this tunnel domain." 1190 ::= { l2tpDomainStatsEntry 17 } 1192 -- 1193 -- The L2TP Tunnel Configuration Table 1194 -- 1195 -- This table contains objects that can be used to 1196 -- (re)configure the operational characteristics of a 1197 -- single L2TP tunnel. 1199 l2tpTunnelConfigTable OBJECT-TYPE 1200 SYNTAX SEQUENCE OF L2tpTunnelConfigEntry 1201 MAX-ACCESS not-accessible 1202 STATUS current 1203 DESCRIPTION 1204 "The L2TP tunnel configuration table." 1205 ::= { l2tpObjects 4 } 1207 l2tpTunnelConfigEntry OBJECT-TYPE 1208 SYNTAX L2tpTunnelConfigEntry 1209 MAX-ACCESS not-accessible 1210 STATUS current 1211 DESCRIPTION 1212 "A L2TP tunnel interface configuration entry." 1213 INDEX { l2tpTunnelConfigIfIndex } 1214 ::= { l2tpTunnelConfigTable 1 } 1216 L2tpTunnelConfigEntry ::= 1217 SEQUENCE { 1218 l2tpTunnelConfigIfIndex 1219 InterfaceIndex, 1220 l2tpTunnelConfigAuthentication 1221 INTEGER, 1222 l2tpTunnelConfigSecurity 1223 INTEGER, 1224 l2tpTunnelConfigHelloInterval 1225 Integer32, 1226 l2tpTunnelConfigIdleTimeout 1227 Integer32, 1228 l2tpTunnelConfigControlRWS 1229 Integer32, 1230 l2tpTunnelConfigControlRetransmissions 1231 Integer32, 1232 l2tpTunnelConfigPayloadSequencing 1233 TruthValue, 1234 l2tpTunnelConfigPayloadRWS 1235 Integer32, 1236 l2tpTunnelConfigDelayedAckTimeout 1237 MilliSeconds, 1238 l2tpTunnelConfigReassemblyTimeout 1239 MilliSeconds, 1241 l2tpTunnelConfigTransport 1242 INTEGER 1243 } 1245 l2tpTunnelConfigIfIndex OBJECT-TYPE 1246 SYNTAX InterfaceIndex 1247 MAX-ACCESS read-only 1248 STATUS current 1249 DESCRIPTION 1250 "This value for this object is equal to the value 1251 of ifIndex of the Interfaces MIB for tunnel 1252 interfaces of type L2TP." 1253 ::= { l2tpTunnelConfigEntry 1 } 1255 l2tpTunnelConfigAuthentication OBJECT-TYPE 1256 SYNTAX INTEGER { 1257 none(1), 1258 simple(2), 1259 challenge(3) 1260 } 1261 MAX-ACCESS read-write 1262 STATUS current 1263 DESCRIPTION 1264 "This object describes how L2TP tunnel peers are 1265 to be authenticated. The value 'simple' indicates 1266 that peers are authenticated simply by their host 1267 name as described in the Host Name AVP. The value 1268 'challenge' indicates that all peers are challenged 1269 to prove their identification. This mechanism is 1270 described in the L2TP protocol. How the tunnel 1271 peers exchange tunnel secrets for this later case 1272 is outside the scope of this document." 1273 DEFVAL { none } 1274 ::= { l2tpTunnelConfigEntry 2 } 1276 l2tpTunnelConfigSecurity OBJECT-TYPE 1277 SYNTAX INTEGER { 1278 none(1), 1279 other(2), 1280 ipsec(3) 1281 } 1282 MAX-ACCESS read-write 1283 STATUS current 1284 DESCRIPTION 1285 "This object defines whether this tunnel is to be 1286 secured. The value of 'ipSec' indicates that all 1287 tunnel packets, control and session, have IP 1288 Security headers. The type of IP Security headers 1289 (AH, ESP etc) and how they are further described 1290 is outside the scope of this document." 1291 DEFVAL { none } 1292 ::= { l2tpTunnelConfigEntry 3 } 1294 l2tpTunnelConfigHelloInterval OBJECT-TYPE 1295 SYNTAX Integer32 (0..3600) 1296 MAX-ACCESS read-write 1297 STATUS current 1298 DESCRIPTION 1299 "This object defines the interval (in seconds) in 1300 which Hello (or keep-alive) packets are to be sent 1301 to the tunnel peer." 1302 DEFVAL { 60 } 1303 ::= { l2tpTunnelConfigEntry 4 } 1305 l2tpTunnelConfigIdleTimeout OBJECT-TYPE 1306 SYNTAX Integer32 (0..86400) 1307 MAX-ACCESS read-write 1308 STATUS current 1309 DESCRIPTION 1310 "This object defines the period of time (in seconds) 1311 that an established tunnel with no sessions will 1312 wait before disconnecting the tunnel. A value of 1313 zero indicates that the tunnel will disconnect 1314 immediately after the last session disconnects." 1315 DEFVAL { 0 } 1316 ::= { l2tpTunnelConfigEntry 5 } 1318 l2tpTunnelConfigControlRWS OBJECT-TYPE 1319 SYNTAX Integer32 (1..64) 1320 MAX-ACCESS read-write 1321 STATUS current 1322 DESCRIPTION 1323 "This object defines the control channel receive 1324 window size. It specifies the maximum number of 1325 packets the tunnel peer can send without waiting 1326 for an acknowledgement from this peer." 1327 DEFVAL { 4 } 1328 ::= { l2tpTunnelConfigEntry 6 } 1330 l2tpTunnelConfigControlRetransmissions OBJECT-TYPE 1331 SYNTAX Integer32 (0..32) 1332 MAX-ACCESS read-write 1333 STATUS current 1334 DESCRIPTION 1335 "This object defines the number of retransmission's 1336 which the tunnel will attempt before assuming that 1337 the peer is no longer responding. A value of zero 1338 indicates that this peer will not attempt to 1339 retransmit an unacknowledged control packet." 1340 DEFVAL { 4 } 1341 ::= { l2tpTunnelConfigEntry 7 } 1343 l2tpTunnelConfigPayloadSequencing OBJECT-TYPE 1344 SYNTAX TruthValue 1345 MAX-ACCESS read-write 1346 STATUS current 1347 DESCRIPTION 1348 "This object determines whether or not session payload 1349 packets will be requested to be sent with sequence 1350 numbers from the tunnel peer." 1351 DEFVAL { false } 1352 ::= { l2tpTunnelConfigEntry 8 } 1354 l2tpTunnelConfigPayloadRWS OBJECT-TYPE 1355 SYNTAX Integer32 (0..65535) 1356 MAX-ACCESS read-write 1357 STATUS current 1358 DESCRIPTION 1359 "This object defines the payload sessions receive 1360 window size. It specifies the maximum number of 1361 packets the tunnel peer can send without waiting 1362 for an acknowledgement from this peer or an 1363 acknowledgement timeout occurs. If paylaod sequencing 1364 is not configured for this tunnel then this object 1365 may be used in the event that the tunnel peer requests 1366 payload seqencing." 1367 DEFVAL { 0 } 1368 ::= { l2tpTunnelConfigEntry 9 } 1370 l2tpTunnelConfigDelayedAckTimeout OBJECT-TYPE 1371 SYNTAX MilliSeconds 1372 MAX-ACCESS read-write 1373 STATUS current 1374 DESCRIPTION 1375 "This object defines the number of milliseconds 1376 which the local tunnel peer will wait to send an 1377 acknowledgement to it's peer in the case where there 1378 is no data packets to piggyback the acknowledgement 1379 on. The default value for this object is zero which 1380 results in an immediate acknowledgment to received 1381 payload (data) packets. If payload sequencing is not 1382 configured then this object should not be interpreted." 1383 DEFVAL { 0 } 1384 ::= { l2tpTunnelConfigEntry 10 } 1386 l2tpTunnelConfigReassemblyTimeout OBJECT-TYPE 1387 SYNTAX MilliSeconds 1388 MAX-ACCESS read-write 1389 STATUS current 1390 DESCRIPTION 1391 "This object defines the number of milliseconds that 1392 this tunnel will wait before processing packets that 1393 were received out of sequence (which are waiting for 1394 the packet(s) to put them in sequence). A low value 1395 increases the chance of delayed packets to be discarded 1396 (which MAY causes the PPP decompression engine to 1397 reset) while a high value may cause more queueing and 1398 possibly degrade throughput if packets are truly lost. 1399 The default value for this object is zero which will 1400 result in all delayed packets being lost." 1401 DEFVAL { 0 } 1402 ::= { l2tpTunnelConfigEntry 11 } 1404 l2tpTunnelConfigTransport OBJECT-TYPE 1405 SYNTAX INTEGER { 1406 other(1), 1407 none(2), 1408 ipUdp(3), 1409 frameRelay(4) 1410 } 1411 MAX-ACCESS read-write 1412 STATUS current 1413 DESCRIPTION 1414 "This object defines the underlying transport media 1415 that is in use for this tunnel entry. Different tunnel 1416 transports may define MIB extensions to the L2TP tunnel 1417 table to realize the transport layer. For example if the 1418 value of this object is 'ipUdp' then the value of ifIndex 1419 for this table may be used to determine state from the 1420 l2tpUdpStatsTable." 1421 ::= { l2tpTunnelConfigEntry 12 } 1423 -- 1424 -- The L2TP Tunnel Status and Statisticss Table 1425 -- 1426 -- This table contains objects that can be used to describe 1427 -- the current status and statistics of a single L2TP tunnel. 1429 l2tpTunnelStatsTable OBJECT-TYPE 1430 SYNTAX SEQUENCE OF L2tpTunnelStatsEntry 1431 MAX-ACCESS not-accessible 1432 STATUS current 1433 DESCRIPTION 1434 "The L2TP tunnel status and statistics table." 1435 ::= { l2tpObjects 5 } 1437 l2tpTunnelStatsEntry OBJECT-TYPE 1438 SYNTAX L2tpTunnelStatsEntry 1439 MAX-ACCESS not-accessible 1440 STATUS current 1441 DESCRIPTION 1442 "An L2TP tunnel interface stats entry." 1443 INDEX { l2tpTunnelStatsIfIndex } 1444 ::= { l2tpTunnelStatsTable 1 } 1446 L2tpTunnelStatsEntry ::= 1447 SEQUENCE { 1448 l2tpTunnelStatsIfIndex 1449 InterfaceIndex, 1450 l2tpTunnelStatsLocalTID 1451 Integer32, 1452 l2tpTunnelStatsRemoteTID 1453 Integer32, 1454 l2tpTunnelStatsState 1455 INTEGER, 1456 l2tpTunnelStatsInitiated 1457 INTEGER, 1458 l2tpTunnelStatsRemoteHostName 1459 DisplayString, 1460 l2tpTunnelStatsRemoteVendorName 1461 DisplayString, 1462 l2tpTunnelStatsRemoteFirmwareRevision 1463 Integer32, 1464 l2tpTunnelStatsRemoteProtocolVersion 1465 OCTET STRING, 1466 l2tpTunnelStatsInitialRemoteRWS 1467 Integer32, 1468 l2tpTunnelStatsBearerCapabilities 1469 INTEGER, 1471 l2tpTunnelStatsFramingCapabilities 1472 INTEGER, 1473 l2tpTunnelStatsControlRecvPackets 1474 Counter32, 1475 l2tpTunnelStatsControlRecvZLB 1476 Counter32, 1477 l2tpTunnelStatsControlOutOfSequence 1478 Counter32, 1479 l2tpTunnelStatsControlOutOfWindow 1480 Counter32, 1481 l2tpTunnelStatsControlSendPackets 1482 Counter32, 1483 l2tpTunnelStatsControlSendZLB 1484 Counter32, 1485 l2tpTunnelStatsControlAckTimeouts 1486 Counter32, 1487 l2tpTunnelStatsCurrentRemoteRWS 1488 Gauge32, 1489 l2tpTunnelStatsSendSeq 1490 Integer32, 1491 l2tpTunnelStatsSendSeqAck 1492 Integer32, 1493 l2tpTunnelStatsRecvSeq 1494 Integer32, 1495 l2tpTunnelStatsRecvSeqAck 1496 Integer32, 1497 l2tpTunnelStatsTotalSessions 1498 Counter32, 1499 l2tpTunnelStatsFailedSessions 1500 Counter32, 1501 l2tpTunnelStatsActiveSessions 1502 Gauge32, 1503 l2tpTunnelStatsLastResultCode 1504 Integer32, 1505 l2tpTunnelStatsLastErrorCode 1506 Integer32, 1507 l2tpTunnelStatsLastErrorMessage 1508 DisplayString 1509 } 1511 l2tpTunnelStatsIfIndex OBJECT-TYPE 1512 SYNTAX InterfaceIndex 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "This value for this object is equal to the value 1517 of ifIndex of the Interfaces MIB for tunnel 1518 interfaces of type L2TP." 1520 ::= { l2tpTunnelStatsEntry 1 } 1522 l2tpTunnelStatsLocalTID OBJECT-TYPE 1523 SYNTAX Integer32 (0..65535) 1524 MAX-ACCESS read-only 1525 STATUS current 1526 DESCRIPTION 1527 "This object contains the local tunnel Identifier." 1528 ::= { l2tpTunnelStatsEntry 2 } 1530 l2tpTunnelStatsRemoteTID OBJECT-TYPE 1531 SYNTAX Integer32 (0..65535) 1532 MAX-ACCESS read-only 1533 STATUS current 1534 DESCRIPTION 1535 "This object contains the remote tunnel Identifier." 1536 ::= { l2tpTunnelStatsEntry 3 } 1538 l2tpTunnelStatsState OBJECT-TYPE 1539 SYNTAX INTEGER { 1540 tunnelIdle(1), 1541 tunnelConnecting(2), 1542 tunnelEstablished(3), 1543 tunnelDisconnecting(4) 1544 } 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "This field contains the current state of the control 1549 tunnel." 1550 ::= { l2tpTunnelStatsEntry 4 } 1552 l2tpTunnelStatsInitiated OBJECT-TYPE 1553 SYNTAX INTEGER { 1554 locally(1), 1555 remotely(2) 1556 } 1557 MAX-ACCESS read-only 1558 STATUS current 1559 DESCRIPTION 1560 "This object indicates whether the tunnel was 1561 initiated locally or by the remote tunnel peer." 1562 ::= { l2tpTunnelStatsEntry 5 } 1564 l2tpTunnelStatsRemoteHostName OBJECT-TYPE 1565 SYNTAX DisplayString 1566 MAX-ACCESS read-only 1567 STATUS current 1568 DESCRIPTION 1569 "This object contains the host name as discovered 1570 during the tunnel establishment phase (via the Host 1571 Name AVP) of the L2TP peer. If the tunnel is idle 1572 this object should maintain its value from the last 1573 time it was connected." 1574 ::= { l2tpTunnelStatsEntry 6 } 1576 l2tpTunnelStatsRemoteVendorName OBJECT-TYPE 1577 SYNTAX DisplayString 1578 MAX-ACCESS read-only 1579 STATUS current 1580 DESCRIPTION 1581 "This object identifies the vendor name of the peer's 1582 L2TP implementation. If the tunnel is idle this 1583 object should maintain its value from the last time 1584 it was connected." 1585 ::= { l2tpTunnelStatsEntry 7 } 1587 l2tpTunnelStatsRemoteFirmwareRevision OBJECT-TYPE 1588 SYNTAX Integer32 1589 MAX-ACCESS read-only 1590 STATUS current 1591 DESCRIPTION 1592 "This object contains the tunnel peer's firmware 1593 revision number. If the tunnel is idle this object 1594 should maintain its value from the last time it 1595 was connected." 1596 ::= { l2tpTunnelStatsEntry 8 } 1598 l2tpTunnelStatsRemoteProtocolVersion OBJECT-TYPE 1599 SYNTAX OCTET STRING (SIZE(2)) 1600 MAX-ACCESS read-only 1601 STATUS current 1602 DESCRIPTION 1603 "This object describes the protocol version and 1604 revision of the tunnel peers implementation. The 1605 first octet contains the protocol version. The 1606 second octet contains the protocol revision." 1607 ::= { l2tpTunnelStatsEntry 9 } 1609 l2tpTunnelStatsInitialRemoteRWS OBJECT-TYPE 1610 SYNTAX Integer32 (0..65535) 1611 MAX-ACCESS read-only 1612 STATUS current 1613 DESCRIPTION 1614 "This object contains the initial remote peers 1615 receive window size as indicated by the tunnel peer 1616 (in the RWS AVP) during the tunnel establishment 1617 phase. If the tunnel is idle this object should 1618 maintain its value from the last time it was 1619 connected." 1620 ::= { l2tpTunnelStatsEntry 10 } 1622 l2tpTunnelStatsBearerCapabilities OBJECT-TYPE 1623 SYNTAX INTEGER { 1624 sync(1), 1625 async(2), 1626 syncAsync(3) 1627 } 1628 MAX-ACCESS read-only 1629 STATUS current 1630 DESCRIPTION 1631 "This object describes the Bearer Capabilities of 1632 the tunnel peer. If the tunnel is idle this object 1633 should maintain its value from the last time it was 1634 connected." 1635 ::= { l2tpTunnelStatsEntry 11 } 1637 l2tpTunnelStatsFramingCapabilities OBJECT-TYPE 1638 SYNTAX INTEGER { 1639 digital(1), 1640 analog(2), 1641 digitalAnalog(3) 1642 } 1643 MAX-ACCESS read-only 1644 STATUS current 1645 DESCRIPTION 1646 "This object describes the Framing Capabilities of 1647 the tunnel peer. If the tunnel is idle this object 1648 should maintain its value from the last time it was 1649 connected." 1650 ::= { l2tpTunnelStatsEntry 12 } 1652 l2tpTunnelStatsControlRecvPackets OBJECT-TYPE 1653 SYNTAX Counter32 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION 1657 "This object contains the number of control packets 1658 received on the tunnel." 1659 ::= { l2tpTunnelStatsEntry 13 } 1661 l2tpTunnelStatsControlRecvZLB OBJECT-TYPE 1662 SYNTAX Counter32 1663 MAX-ACCESS read-only 1664 STATUS current 1665 DESCRIPTION 1666 "This object returns a count of the number of Zero 1667 Length Body control packet acknowledgement packets 1668 that were received." 1669 ::= { l2tpTunnelStatsEntry 14 } 1671 l2tpTunnelStatsControlOutOfSequence OBJECT-TYPE 1672 SYNTAX Counter32 1673 MAX-ACCESS read-only 1674 STATUS current 1675 DESCRIPTION 1676 "This object returns a count of the number of 1677 control packets that were not received in the 1678 correct order (as per the sequence number) on 1679 this tunnel." 1680 ::= { l2tpTunnelStatsEntry 15 } 1682 l2tpTunnelStatsControlOutOfWindow OBJECT-TYPE 1683 SYNTAX Counter32 1684 MAX-ACCESS read-only 1685 STATUS current 1686 DESCRIPTION 1687 "This object contains the number of control 1688 packets that were received outside of the 1689 offered receive window. It is implementation 1690 specific as to whether these packets are queued 1691 or discarded." 1692 ::= { l2tpTunnelStatsEntry 16 } 1694 l2tpTunnelStatsControlSendPackets OBJECT-TYPE 1695 SYNTAX Counter32 1696 MAX-ACCESS read-only 1697 STATUS current 1698 DESCRIPTION 1699 "This object contains the number of control 1700 packets that were transmitted to the tunnel 1701 peer." 1702 ::= { l2tpTunnelStatsEntry 17 } 1704 l2tpTunnelStatsControlSendZLB OBJECT-TYPE 1705 SYNTAX Counter32 1706 MAX-ACCESS read-only 1707 STATUS current 1708 DESCRIPTION 1709 "This object contains the number of Zero Length 1710 Body control packets transmitted transitted to 1711 the tunnel peer." 1713 ::= { l2tpTunnelStatsEntry 18 } 1715 l2tpTunnelStatsControlAckTimeouts OBJECT-TYPE 1716 SYNTAX Counter32 1717 MAX-ACCESS read-only 1718 STATUS current 1719 DESCRIPTION 1720 "This object returns a count of the number of 1721 control packet timeouts due to the lack of a 1722 timely acknowledgement from the tunnel peer." 1723 ::= { l2tpTunnelStatsEntry 19 } 1725 l2tpTunnelStatsCurrentRemoteRWS OBJECT-TYPE 1726 SYNTAX Gauge32 (0..64) 1727 MAX-ACCESS read-only 1728 STATUS current 1729 DESCRIPTION 1730 "This object contains the current remote receive 1731 window size as determined by the local flow 1732 control mechanism employed." 1733 ::= { l2tpTunnelStatsEntry 20 } 1735 l2tpTunnelStatsSendSeq OBJECT-TYPE 1736 SYNTAX Integer32 (0..65535) 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "This object contains the next send sequence number 1741 for the control channel." 1742 ::= { l2tpTunnelStatsEntry 21 } 1744 l2tpTunnelStatsSendSeqAck OBJECT-TYPE 1745 SYNTAX Integer32 (0..65535) 1746 MAX-ACCESS read-only 1747 STATUS current 1748 DESCRIPTION 1749 "This object contains the send sequence number that 1750 the tunnel peer has acknowledged for the control 1751 channel. The flow control state can be determined 1752 by subtracting the l2tpTunnelStatsSendSeq from 1753 l2tpTunnelStatsSendSeqAck and comparing this value 1754 to l2tpTunnelStatsCurrentRemoteRWS." 1755 ::= { l2tpTunnelStatsEntry 22 } 1757 l2tpTunnelStatsRecvSeq OBJECT-TYPE 1758 SYNTAX Integer32 (0..65535) 1759 MAX-ACCESS read-only 1760 STATUS current 1761 DESCRIPTION 1762 "This object contains the next receive sequence 1763 number expected to be received on this control 1764 channel." 1765 ::= { l2tpTunnelStatsEntry 23 } 1767 l2tpTunnelStatsRecvSeqAck OBJECT-TYPE 1768 SYNTAX Integer32 (0..65535) 1769 MAX-ACCESS read-only 1770 STATUS current 1771 DESCRIPTION 1772 "This object contains the last receive sequence 1773 number that was acknowledged back to the tunnel 1774 peer for the control channel." 1775 ::= { l2tpTunnelStatsEntry 24 } 1777 l2tpTunnelStatsTotalSessions OBJECT-TYPE 1778 SYNTAX Counter32 1779 MAX-ACCESS read-only 1780 STATUS current 1781 DESCRIPTION 1782 "This object contains the total number of sessions 1783 that this tunnel has successfully connected through 1784 to its tunnel peer since this tunnel was created." 1785 ::= { l2tpTunnelStatsEntry 25 } 1787 l2tpTunnelStatsFailedSessions OBJECT-TYPE 1788 SYNTAX Counter32 1789 MAX-ACCESS read-only 1790 STATUS current 1791 DESCRIPTION 1792 "This object contains the total number of sessions 1793 that were initiated but failed to reach the 1794 established phase." 1795 ::= { l2tpTunnelStatsEntry 26 } 1797 l2tpTunnelStatsActiveSessions OBJECT-TYPE 1798 SYNTAX Gauge32 1799 MAX-ACCESS read-only 1800 STATUS current 1801 DESCRIPTION 1802 "This object contains the total number of sessions 1803 in the established state for this tunnel." 1804 ::= { l2tpTunnelStatsEntry 27 } 1806 l2tpTunnelStatsLastResultCode OBJECT-TYPE 1807 SYNTAX Integer32 (0..65535) 1808 MAX-ACCESS read-only 1809 STATUS current 1810 DESCRIPTION 1811 "This object contains the last value of the result 1812 code as described in the Result Code AVP which 1813 caused the tunnel to disconnect." 1814 ::= { l2tpTunnelStatsEntry 28 } 1816 l2tpTunnelStatsLastErrorCode OBJECT-TYPE 1817 SYNTAX Integer32 (0..65535) 1818 MAX-ACCESS read-only 1819 STATUS current 1820 DESCRIPTION 1821 "This object contains the last value of the error 1822 code as described in the Result Code AVP which 1823 caused the tunnel to disconnect." 1824 ::= { l2tpTunnelStatsEntry 29 } 1826 l2tpTunnelStatsLastErrorMessage OBJECT-TYPE 1827 SYNTAX DisplayString 1828 MAX-ACCESS read-only 1829 STATUS current 1830 DESCRIPTION 1831 "This object contains the last value of the optional 1832 message as described in the Result Code AVP which 1833 caused the tunnel to disconnect." 1834 ::= { l2tpTunnelStatsEntry 30 } 1836 -- 1837 -- { l2tpObjects 6 } reserved for future use 1838 -- 1839 -- 1840 -- The L2TP Session Status and Statistics Table 1841 -- 1842 -- This table contains the objects that can be used to 1843 -- describe the current status and statistics of a single 1844 -- L2TP tunneled session. 1846 l2tpSessionStatsTable OBJECT-TYPE 1847 SYNTAX SEQUENCE OF L2tpSessionStatsEntry 1848 MAX-ACCESS not-accessible 1849 STATUS current 1850 DESCRIPTION 1851 "The L2TP session status and statistics table." 1852 ::= { l2tpObjects 7 } 1854 l2tpSessionStatsEntry OBJECT-TYPE 1855 SYNTAX L2tpSessionStatsEntry 1856 MAX-ACCESS not-accessible 1857 STATUS current 1858 DESCRIPTION 1859 "An L2TP session interface stats entry." 1860 INDEX { l2tpSessionStatsIfIndex } 1861 ::= { l2tpSessionStatsTable 1 } 1863 L2tpSessionStatsEntry ::= 1864 SEQUENCE { 1865 l2tpSessionStatsIfIndex 1866 InterfaceIndex, 1867 l2tpSessionStatsTID 1868 Integer32, 1869 l2tpSessionStatsLocalCID 1870 Integer32, 1871 l2tpSessionStatsRemoteCID 1872 Integer32, 1873 l2tpSessionStatsUserName 1874 DisplayString, 1875 l2tpSessionStatsState 1876 INTEGER, 1877 l2tpSessionStatsCallType 1878 INTEGER, 1879 l2tpSessionStatsCallSerialNumber 1880 Integer32, 1881 l2tpSessionStatsTxConnectSpeed 1882 Integer32, 1883 l2tpSessionStatsRxConnectSpeed 1884 Integer32, 1885 l2tpSessionStatsCallBearerType 1886 INTEGER, 1887 l2tpSessionStatsFramingType 1888 INTEGER, 1889 l2tpSessionStatsPhysChanId 1890 Integer32, 1891 l2tpSessionStatsDNIS 1892 DisplayString, 1893 l2tpSessionStatsCLID 1894 DisplayString, 1895 l2tpSessionStatsSubAddress 1896 DisplayString, 1897 l2tpSessionStatsPrivateGroupID 1898 DisplayString, 1899 l2tpSessionStatsProxyLcp 1900 TruthValue, 1901 l2tpSessionStatsAuthMethod 1902 INTEGER, 1903 l2tpSessionStatsLocalRWS 1904 Integer32, 1905 l2tpSessionStatsRemoteInitialRWS 1906 Integer32, 1907 l2tpSessionStatsRemotePPD 1908 Integer32, 1909 l2tpSessionStatsSequencingState 1910 INTEGER, 1911 l2tpSessionStatsRecvZLB 1912 Counter32, 1913 l2tpSessionStatsOutSequence 1914 Counter32, 1915 l2tpSessionStatsOutOfWindow 1916 Counter32, 1917 l2tpSessionStatsSendZLB 1918 Counter32, 1919 l2tpSessionStatsAckTimeouts 1920 Counter32, 1921 l2tpSessionStatsReassemblyTimeouts 1922 Counter32, 1923 l2tpSesssionStatsCurrentRemoteRWS 1924 Gauge32, 1925 l2tpSessionStatsSendSeq 1926 Integer32, 1927 l2tpSessionStatsSendSeqAck 1928 Integer32, 1929 l2tpSessionStatsSendSeqResets 1930 Counter32, 1931 l2tpSessionStatsRecvSeq 1932 Integer32, 1933 l2tpSessionStatsRecvSeqAck 1934 Integer32, 1935 l2tpSessionStatsRecvSeqResets 1936 Counter32 1937 } 1939 l2tpSessionStatsIfIndex OBJECT-TYPE 1940 SYNTAX InterfaceIndex 1941 MAX-ACCESS read-only 1942 STATUS current 1943 DESCRIPTION 1944 "This value for this object is equal to the value 1945 of ifIndex of the Interfaces MIB for session 1946 interfaces of type L2TP." 1947 ::= { l2tpSessionStatsEntry 1 } 1949 l2tpSessionStatsTID OBJECT-TYPE 1950 SYNTAX Integer32 (0..65535) 1951 MAX-ACCESS read-only 1952 STATUS current 1953 DESCRIPTION 1954 "This object contains the control channel tunnel 1955 identifier for this session." 1956 ::= { l2tpSessionStatsEntry 2 } 1958 l2tpSessionStatsLocalCID OBJECT-TYPE 1959 SYNTAX Integer32 (0..65535) 1960 MAX-ACCESS read-only 1961 STATUS current 1962 DESCRIPTION 1963 "This object contains the local call identifier 1964 for the session." 1965 ::= { l2tpSessionStatsEntry 3 } 1967 l2tpSessionStatsRemoteCID OBJECT-TYPE 1968 SYNTAX Integer32 (0..65535) 1969 MAX-ACCESS read-only 1970 STATUS current 1971 DESCRIPTION 1972 "This object contains the remote call identifier 1973 for the session." 1974 ::= { l2tpSessionStatsEntry 4 } 1976 l2tpSessionStatsUserName OBJECT-TYPE 1977 SYNTAX DisplayString 1978 MAX-ACCESS read-only 1979 STATUS current 1980 DESCRIPTION 1981 "This object identifies the peer session name on 1982 this interface. This is typically the login name 1983 of the remote user. If the user name is unknown to 1984 the local tunnel peer then this object will contain 1985 a null string." 1986 ::= { l2tpSessionStatsEntry 5 } 1988 l2tpSessionStatsState OBJECT-TYPE 1989 SYNTAX INTEGER { 1990 sessionIdle(1), 1991 sessionConnecting(2), 1992 sessionEstablished(3), 1993 sessionDisconnecting(4) 1994 } 1995 MAX-ACCESS read-only 1996 STATUS current 1997 DESCRIPTION 1998 "This object contains the current state of the 1999 session." 2000 ::= { l2tpSessionStatsEntry 6 } 2002 l2tpSessionStatsCallType OBJECT-TYPE 2003 SYNTAX INTEGER { 2004 lacIncoming(1), 2005 lnsIncoming(2), 2006 lacOutgoing(3), 2007 lnsOutgoing(4) 2008 } 2009 MAX-ACCESS read-only 2010 STATUS current 2011 DESCRIPTION 2012 "This object indicates the type of call and the 2013 role this tunnel peer is providing for this 2014 session. For example, lacIncoming(1) indicates 2015 that this tunnel peer is acting as a LAC and 2016 generated a Incoming-Call-Request to the tunnel 2017 peer (the LNS). Note that tunnel peers can be 2018 both LAC and LNS simultaneously." 2019 ::= { l2tpSessionStatsEntry 7 } 2021 l2tpSessionStatsCallSerialNumber OBJECT-TYPE 2022 SYNTAX Integer32 2023 MAX-ACCESS read-only 2024 STATUS current 2025 DESCRIPTION 2026 "This object contains the serial number that has 2027 been assigned to this session." 2028 ::= { l2tpSessionStatsEntry 8 } 2030 l2tpSessionStatsTxConnectSpeed OBJECT-TYPE 2031 SYNTAX Integer32 2032 MAX-ACCESS read-only 2033 STATUS current 2034 DESCRIPTION 2035 "This object returns the last known transmit 2036 baud rate for this session." 2037 ::= { l2tpSessionStatsEntry 9 } 2039 l2tpSessionStatsRxConnectSpeed OBJECT-TYPE 2040 SYNTAX Integer32 2041 MAX-ACCESS read-only 2042 STATUS current 2043 DESCRIPTION 2044 "This object returns the last known receive 2045 baud rate for this session established." 2046 ::= { l2tpSessionStatsEntry 10 } 2048 l2tpSessionStatsCallBearerType OBJECT-TYPE 2049 SYNTAX INTEGER { 2050 digital(1), 2051 analog(2) 2052 } 2053 MAX-ACCESS read-only 2054 STATUS current 2055 DESCRIPTION 2056 "This object describes the bearer type of this 2057 session." 2058 ::= { l2tpSessionStatsEntry 11 } 2060 l2tpSessionStatsFramingType OBJECT-TYPE 2061 SYNTAX INTEGER { 2062 asynchronous(1), 2063 synchronous(2) 2064 } 2065 MAX-ACCESS read-only 2066 STATUS current 2067 DESCRIPTION 2068 "This object describes the framing type of this 2069 session." 2070 ::= { l2tpSessionStatsEntry 12 } 2072 l2tpSessionStatsPhysChanId OBJECT-TYPE 2073 SYNTAX Integer32 2074 MAX-ACCESS read-only 2075 STATUS current 2076 DESCRIPTION 2077 "This object contains the physical channel 2078 identifier for the session." 2079 ::= { l2tpSessionStatsEntry 13 } 2081 l2tpSessionStatsDNIS OBJECT-TYPE 2082 SYNTAX DisplayString 2083 MAX-ACCESS read-only 2084 STATUS current 2085 DESCRIPTION 2086 "This object identifies the Dialed Number 2087 Information String that the LAC obtained from 2088 the network for the session. If no DNIS was 2089 provided then a null string will be returned." 2090 ::= { l2tpSessionStatsEntry 14 } 2092 l2tpSessionStatsCLID OBJECT-TYPE 2093 SYNTAX DisplayString 2094 MAX-ACCESS read-only 2095 STATUS current 2096 DESCRIPTION 2097 "This object identifies the Calling Line ID 2098 that the LAC obtained from the network for 2099 the session. If no CLID was provided then a 2100 null string will be returned." 2101 ::= { l2tpSessionStatsEntry 15 } 2103 l2tpSessionStatsSubAddress OBJECT-TYPE 2104 SYNTAX DisplayString 2105 MAX-ACCESS read-only 2106 STATUS current 2107 DESCRIPTION 2108 "This object identifies the Sub Address that 2109 the LAC obtained from the network for the 2110 session. If no Sub Address was provided then 2111 a null string will be returned." 2112 ::= { l2tpSessionStatsEntry 16 } 2114 l2tpSessionStatsPrivateGroupID OBJECT-TYPE 2115 SYNTAX DisplayString 2116 MAX-ACCESS read-only 2117 STATUS current 2118 DESCRIPTION 2119 "This object identifies the Private Group 2120 Identifier used for this tunneled session. 2121 If no Private Group Identifier was provided 2122 then a null string will be returned." 2123 ::= { l2tpSessionStatsEntry 17 } 2125 l2tpSessionStatsProxyLcp OBJECT-TYPE 2126 SYNTAX TruthValue 2127 MAX-ACCESS read-only 2128 STATUS current 2129 DESCRIPTION 2130 "Indicates whether the LAC performed proxy LCP 2131 for this session." 2132 ::= { l2tpSessionStatsEntry 18 } 2134 l2tpSessionStatsAuthMethod OBJECT-TYPE 2135 SYNTAX INTEGER { 2136 none(1), 2137 text(2), 2138 pppChap(3), 2139 pppPap(4) 2140 } 2141 MAX-ACCESS read-only 2142 STATUS current 2143 DESCRIPTION 2144 "This object contains the proxy authentication 2145 method employed by the LAC for the session. If 2146 l2tpSessionProxyLcp is false(2) this object should 2147 not be interpreted." 2148 ::= { l2tpSessionStatsEntry 19 } 2150 l2tpSessionStatsLocalRWS OBJECT-TYPE 2151 SYNTAX Integer32 (0..65535) 2152 MAX-ACCESS read-only 2153 STATUS current 2154 DESCRIPTION 2155 "This object returns the local send window size 2156 for this session. If the value of the object 2157 l2tpSessionStatsSequencingState is none(1) 2158 then this object should not be interpreted." 2159 ::= { l2tpSessionStatsEntry 20 } 2161 l2tpSessionStatsRemoteInitialRWS OBJECT-TYPE 2162 SYNTAX Integer32 (0..65535) 2163 MAX-ACCESS read-only 2164 STATUS current 2165 DESCRIPTION 2166 "This object returns the initial remote send 2167 window size for this session. If the value 2168 of the object l2tpSessionStatsSequencingState 2169 is none(1) then this object should not be 2170 interpreted." 2171 ::= { l2tpSessionStatsEntry 21 } 2173 l2tpSessionStatsRemotePPD OBJECT-TYPE 2174 SYNTAX Integer32 2175 MAX-ACCESS read-only 2176 STATUS current 2177 DESCRIPTION 2178 "This object contains the Packet Processing Delay 2179 for the session. If the value of the object 2180 l2tpSessionStatsSequencingState is none(1) 2181 then this object should not be interpreted." 2182 ::= { l2tpSessionStatsEntry 22 } 2184 l2tpSessionStatsSequencingState OBJECT-TYPE 2185 SYNTAX INTEGER { 2186 none(1), 2187 remote(2), 2188 local(3), 2189 both(4) 2190 } 2191 MAX-ACCESS read-only 2192 STATUS current 2193 DESCRIPTION 2194 "This object defines which tunnel peers have 2195 requested payload sequencing. The value of 2196 both(4) indicates that both peers have requested 2197 payload sequencing." 2198 ::= { l2tpSessionStatsEntry 23 } 2200 l2tpSessionStatsRecvZLB OBJECT-TYPE 2201 SYNTAX Counter32 2202 MAX-ACCESS read-only 2203 STATUS current 2204 DESCRIPTION 2205 "This object returns the total number of Zero Length 2206 Body acknowlegement payload packets received for 2207 this session." 2208 ::= { l2tpSessionStatsEntry 24 } 2210 l2tpSessionStatsOutSequence OBJECT-TYPE 2211 SYNTAX Counter32 2212 MAX-ACCESS read-only 2213 STATUS current 2214 DESCRIPTION 2215 "This object returns the total number of packets 2216 received for this session which were received out 2217 of sequence." 2218 ::= { l2tpSessionStatsEntry 25 } 2220 l2tpSessionStatsOutOfWindow OBJECT-TYPE 2221 SYNTAX Counter32 2222 MAX-ACCESS read-only 2223 STATUS current 2224 DESCRIPTION 2225 "This object returns a count of the number of 2226 payload packets that were received outside of the 2227 expected window for this session." 2228 ::= { l2tpSessionStatsEntry 26 } 2230 l2tpSessionStatsSendZLB OBJECT-TYPE 2231 SYNTAX Counter32 2232 MAX-ACCESS read-only 2233 STATUS current 2234 DESCRIPTION 2235 "This object returns the total number of Zero 2236 Length Body acknowledgement packets transmitted 2237 on this session." 2238 ::= { l2tpSessionStatsEntry 27 } 2240 l2tpSessionStatsAckTimeouts OBJECT-TYPE 2241 SYNTAX Counter32 2242 MAX-ACCESS read-only 2243 STATUS current 2244 DESCRIPTION 2245 "This object returns the total number of 2246 acknowledgement timeouts seen on payload 2247 packets for this session." 2248 ::= { l2tpSessionStatsEntry 28 } 2250 l2tpSessionStatsReassemblyTimeouts OBJECT-TYPE 2251 SYNTAX Counter32 2252 MAX-ACCESS read-only 2253 STATUS current 2254 DESCRIPTION 2255 "This object returns the number of reassembly 2256 time outs that have occured for this session." 2257 ::= { l2tpSessionStatsEntry 29 } 2259 l2tpSesssionStatsCurrentRemoteRWS OBJECT-TYPE 2260 SYNTAX Gauge32 (0..65535) 2261 MAX-ACCESS read-only 2262 STATUS current 2263 DESCRIPTION 2264 "This object contains the current remote receive 2265 window size as determined by the local flow 2266 control mechanism employed." 2267 ::= { l2tpSessionStatsEntry 30 } 2269 l2tpSessionStatsSendSeq OBJECT-TYPE 2270 SYNTAX Integer32 (0..65535) 2271 MAX-ACCESS read-only 2272 STATUS current 2273 DESCRIPTION 2274 "This object contains the next send sequence number 2275 for for this session." 2276 ::= { l2tpSessionStatsEntry 31 } 2278 l2tpSessionStatsSendSeqAck OBJECT-TYPE 2279 SYNTAX Integer32 (0..65535) 2280 MAX-ACCESS read-only 2281 STATUS current 2282 DESCRIPTION 2283 "This object contains the send sequence number 2284 that the tunnel peer has acknowledged for the 2285 payload channel. The flow control state can be 2286 determined by subtracting the l2tpSessionStatsSendSeq 2287 from l2tpSessionStatsSendSeqAck and comparing this 2288 value to l2tpSesssionStatsCurrentRemoteRWS." 2289 ::= { l2tpSessionStatsEntry 32 } 2291 l2tpSessionStatsSendSeqResets OBJECT-TYPE 2292 SYNTAX Counter32 2293 MAX-ACCESS read-only 2294 STATUS current 2295 DESCRIPTION 2296 "This object contains the total number of sequence 2297 number resets (payload packets with the R-bit set) 2298 sent on this session." 2299 ::= { l2tpSessionStatsEntry 33 } 2301 l2tpSessionStatsRecvSeq OBJECT-TYPE 2302 SYNTAX Integer32 (0..65535) 2303 MAX-ACCESS read-only 2304 STATUS current 2305 DESCRIPTION 2306 "This object contains the next receive sequence 2307 number expected to be received on this session." 2308 ::= { l2tpSessionStatsEntry 34 } 2310 l2tpSessionStatsRecvSeqAck OBJECT-TYPE 2311 SYNTAX Integer32 (0..65535) 2312 MAX-ACCESS read-only 2313 STATUS current 2314 DESCRIPTION 2315 "This object contains the last receive sequence 2316 number that was acknowledged back to the tunnel 2317 peer for the session." 2319 ::= { l2tpSessionStatsEntry 35 } 2321 l2tpSessionStatsRecvSeqResets OBJECT-TYPE 2322 SYNTAX Counter32 2323 MAX-ACCESS read-only 2324 STATUS current 2325 DESCRIPTION 2326 "This object contains the total number of sequence 2327 number resets (payload packets with the R-bit set) 2328 received on this session." 2329 ::= { l2tpSessionStatsEntry 36 } 2331 -- 2332 -- { l2tpIpUdpObjects 1 } reserved for future use 2333 -- 2334 -- The L2TP IP/UDP Transport Status and Statistics Table 2335 -- 2336 -- This table contains objects that can be used to 2337 -- describe the current status and statistics of the 2338 -- IP/UDP L2TP tunnel transport. 2340 l2tpUdpStatsTable OBJECT-TYPE 2341 SYNTAX SEQUENCE OF L2tpUdpStatsEntry 2342 MAX-ACCESS not-accessible 2343 STATUS current 2344 DESCRIPTION 2345 "The L2TP IP/UDP transport stats table." 2346 ::= { l2tpIpUdpObjects 2 } 2348 l2tpUdpStatsEntry OBJECT-TYPE 2349 SYNTAX L2tpUdpStatsEntry 2350 MAX-ACCESS not-accessible 2351 STATUS current 2352 DESCRIPTION 2353 "An L2TP IP/UDP transport stats entry." 2354 INDEX { l2tpUdpStatsIfIndex } 2355 ::= { l2tpUdpStatsTable 1 } 2357 L2tpUdpStatsEntry ::= 2358 SEQUENCE { 2359 l2tpUdpStatsIfIndex 2360 InterfaceIndex, 2361 l2tpUdpStatsPeerPort 2362 Integer32, 2363 l2tpUdpStatsLocalPort 2364 Integer32, 2365 l2tpUdpStatsAddressChanges 2366 Counter32, 2367 l2tpUdpStatsPortChanges 2368 Counter32 2369 } 2371 l2tpUdpStatsIfIndex OBJECT-TYPE 2372 SYNTAX InterfaceIndex 2373 MAX-ACCESS read-only 2374 STATUS current 2375 DESCRIPTION 2376 "This value for this object is equal to the 2377 value of ifIndex of the Interfaces MIB for 2378 tunnel interfaces of type L2TP and which have 2379 a L2TP transport of IP/UDP." 2381 ::= { l2tpUdpStatsEntry 1 } 2383 l2tpUdpStatsPeerPort OBJECT-TYPE 2384 SYNTAX Integer32 (0..65535) 2385 MAX-ACCESS read-only 2386 STATUS current 2387 DESCRIPTION 2388 "This object reflects the peer's UDP port number 2389 of the last packet received." 2390 ::= { l2tpUdpStatsEntry 2 } 2392 l2tpUdpStatsLocalPort OBJECT-TYPE 2393 SYNTAX Integer32 2394 MAX-ACCESS read-only 2395 STATUS current 2396 DESCRIPTION 2397 "This object reflects the local UDP port number 2398 that this tunnel is bound to." 2399 ::= { l2tpUdpStatsEntry 3 } 2401 l2tpUdpStatsAddressChanges OBJECT-TYPE 2402 SYNTAX Counter32 2403 MAX-ACCESS read-only 2404 STATUS current 2405 DESCRIPTION 2406 "This object reflects the number of times the 2407 source IP address has changed since the tunnel 2408 reached the established state." 2409 ::= { l2tpUdpStatsEntry 4 } 2411 l2tpUdpStatsPortChanges OBJECT-TYPE 2412 SYNTAX Counter32 2413 MAX-ACCESS read-only 2414 STATUS current 2415 DESCRIPTION 2416 "This object reflects the number of times the 2417 source UDP port has changed since the tunnel 2418 reached the established state." 2419 ::= { l2tpUdpStatsEntry 5 } 2421 -- 2422 -- Definition of generic L2TP traps 2423 -- 2425 l2tpTunnelAuthFailure NOTIFICATION-TYPE 2426 OBJECTS { 2427 l2tpTunnelStatsIfIndex, 2428 l2tpTunnelStatsInitiated, 2429 l2tpTunnelStatsRemoteHostName 2430 } 2431 STATUS current 2432 DESCRIPTION 2433 "A l2tpTunnelAuthFailure trap signifies that an 2434 attempt to establish a tunnel to a remote peer 2435 has failed authentication." 2436 ::= { l2tpTraps 1 } 2438 -- 2439 -- Definition of L2TP IP/UDP transport traps 2440 -- 2442 l2tpUdpAddressingChange NOTIFICATION-TYPE 2443 OBJECTS { 2444 l2tpUdpStatsIfIndex, 2445 tunnelIfRemoteAddress, 2446 l2tpUdpStatsPeerPort 2447 } 2448 STATUS current 2449 DESCRIPTION 2450 "A l2tpUdpAddressingChange trap signifies that 2451 the L2TP tunnel peer has (un)successfully changed 2452 its IP address and/or UDP port. This notification 2453 should be rate limited to no more than 1 every 2454 60 seconds." 2455 ::= { l2tpIpUdpTraps 1 } 2457 -- 2458 -- conformance information 2459 -- 2461 l2tpGroups OBJECT IDENTIFIER ::= { l2tpConformance 1 } 2462 l2tpCompliances OBJECT IDENTIFIER ::= { l2tpConformance 2 } 2464 -- 2465 -- compliance statements 2466 -- 2468 l2tpCompliance MODULE-COMPLIANCE 2469 STATUS current 2470 DESCRIPTION 2471 "The compliance statement for SNMPv2 entities 2472 which implement the L2TP MIB." 2474 MODULE -- this module 2476 -- unconditionally mandatory groups 2477 MANDATORY-GROUPS { 2478 l2tpConfigGroup, 2479 l2tpStatsGroup 2480 } 2482 -- conditionally mandatory groups 2483 GROUP l2tpIpUdpGroup 2484 DESCRIPTION 2485 "This group is mandatory for implementations that 2486 support L2TP over IP/UDP." 2488 -- optional groups 2489 GROUP l2tpDomainGroup 2490 DESCRIPTION 2491 "This group is optional for L2TP devices that desire 2492 to group tunnel endpoints into tunnel domains." 2494 ::= { l2tpCompliances 1 } 2496 -- units of conformance 2498 l2tpConfigGroup OBJECT-GROUP 2499 OBJECTS { 2500 l2pAdminState, 2501 l2tpTunnelConfigAuthentication, 2502 l2tpTunnelConfigSecurity, 2503 l2tpTunnelConfigHelloInterval, 2504 l2tpTunnelConfigIdleTimeout, 2505 l2tpTunnelConfigControlRWS, 2506 l2tpTunnelConfigControlRetransmissions, 2507 l2tpTunnelConfigPayloadSequencing, 2508 l2tpTunnelConfigPayloadRWS, 2509 l2tpTunnelConfigDelayedAckTimeout, 2510 l2tpTunnelConfigReassemblyTimeout, 2511 l2tpTunnelConfigTransport 2512 } 2513 STATUS current 2514 DESCRIPTION 2515 "A collection of objects providing configuration 2516 information of the L2TP protocol, tunnels and sessions." 2517 ::= { l2tpGroups 1 } 2519 l2tpStatsGroup OBJECT-GROUP 2520 OBJECTS { 2521 l2tpProtocolVersion, 2522 l2tpVendorName, 2523 l2tpFirmwareRev, 2524 l2tpTunnelStatsIfIndex, 2525 l2tpTunnelStatsLocalTID, 2526 l2tpTunnelStatsRemoteTID, 2527 l2tpTunnelStatsState, 2528 l2tpTunnelStatsInitiated, 2529 l2tpTunnelStatsRemoteHostName, 2530 l2tpTunnelStatsRemoteVendorName, 2531 l2tpTunnelStatsRemoteFirmwareRevision, 2532 l2tpTunnelStatsRemoteProtocolVersion, 2533 l2tpTunnelStatsInitialRemoteRWS, 2534 l2tpTunnelStatsBearerCapabilities, 2535 l2tpTunnelStatsFramingCapabilities, 2536 l2tpTunnelStatsControlRecvPackets, 2537 l2tpTunnelStatsControlRecvZLB, 2538 l2tpTunnelStatsControlOutOfSequence, 2539 l2tpTunnelStatsControlOutOfWindow, 2540 l2tpTunnelStatsControlSendPackets, 2541 l2tpTunnelStatsControlSendZLB, 2542 l2tpTunnelStatsControlAckTimeouts, 2543 l2tpTunnelStatsCurrentRemoteRWS, 2544 l2tpTunnelStatsSendSeq, 2545 l2tpTunnelStatsSendSeqAck, 2546 l2tpTunnelStatsRecvSeq, 2547 l2tpTunnelStatsRecvSeqAck, 2548 l2tpTunnelStatsTotalSessions, 2549 l2tpTunnelStatsFailedSessions, 2550 l2tpTunnelStatsActiveSessions, 2551 l2tpTunnelStatsLastResultCode, 2552 l2tpTunnelStatsLastErrorCode, 2553 l2tpTunnelStatsLastErrorMessage, 2554 l2tpSessionStatsIfIndex, 2555 l2tpSessionStatsTID, 2556 l2tpSessionStatsLocalCID, 2557 l2tpSessionStatsRemoteCID, 2558 l2tpSessionStatsUserName, 2559 l2tpSessionStatsState, 2560 l2tpSessionStatsCallType, 2561 l2tpSessionStatsCallSerialNumber, 2562 l2tpSessionStatsTxConnectSpeed, 2563 l2tpSessionStatsRxConnectSpeed, 2564 l2tpSessionStatsCallBearerType, 2565 l2tpSessionStatsFramingType, 2566 l2tpSessionStatsPhysChanId, 2567 l2tpSessionStatsDNIS, 2568 l2tpSessionStatsCLID, 2569 l2tpSessionStatsSubAddress, 2570 l2tpSessionStatsPrivateGroupID, 2571 l2tpSessionStatsProxyLcp, 2572 l2tpSessionStatsAuthMethod, 2573 l2tpSessionStatsLocalRWS, 2574 l2tpSessionStatsRemoteInitialRWS, 2575 l2tpSessionStatsRemotePPD, 2576 l2tpSessionStatsSequencingState, 2577 l2tpSessionStatsRecvZLB, 2578 l2tpSessionStatsOutSequence, 2579 l2tpSessionStatsOutOfWindow, 2580 l2tpSessionStatsSendZLB, 2581 l2tpSessionStatsAckTimeouts, 2582 l2tpSessionStatsReassemblyTimeouts, 2583 l2tpSesssionStatsCurrentRemoteRWS, 2584 l2tpSessionStatsSendSeq, 2585 l2tpSessionStatsSendSeqAck, 2586 l2tpSessionStatsSendSeqResets, 2587 l2tpSessionStatsRecvSeq, 2588 l2tpSessionStatsRecvSeqAck, 2589 l2tpSessionStatsRecvSeqResets 2590 } 2591 STATUS current 2592 DESCRIPTION 2593 "A collection of objects providing status and 2594 statistics of the L2TP protocol, tunnels and 2595 sessions." 2596 ::= { l2tpGroups 2 } 2598 l2tpIpUdpGroup OBJECT-GROUP 2599 OBJECTS { 2600 l2tpUdpStatsIfIndex, 2601 l2tpUdpStatsPeerPort, 2602 l2tpUdpStatsLocalPort, 2603 l2tpUdpStatsAddressChanges, 2604 l2tpUdpStatsPortChanges 2605 } 2606 STATUS current 2607 DESCRIPTION 2608 "A collection of objects providing status and 2609 statistics of the L2TP IP/UDP transport layer." 2610 ::= { l2tpGroups 3 } 2612 l2tpDomainGroup OBJECT-GROUP 2613 OBJECTS { 2614 l2pDomainConfigAdminState, 2615 l2tpDomainConfigAuthentication, 2616 l2tpDomainConfigTunnelSecurity, 2617 l2tpDomainConfigTunnelHelloInterval, 2618 l2tpDomainConfigTunnelIdleTimeout, 2619 l2tpDomainConfigControlRWS, 2620 l2tpDomainConfigControlRetransmissions, 2621 l2tpDomainConfigPayloadSequencing, 2622 l2tpDomainConfigPayloadRWS, 2623 l2tpDomainConfigDelayedAckTimeout, 2624 l2tpDomainConfigReassemblyTimeout, 2625 l2tpDomainConfigStatus, 2626 l2tpDomainStatsTotalTunnels, 2627 l2tpDomainStatsFailedTunnels, 2628 l2tpDomainStatsFailedAuthentications, 2629 l2tpDomainStatsActiveTunnels, 2630 l2tpDomainStatsTotalSessions, 2631 l2tpDomainStatsFailedSessions, 2632 l2tpDomainStatsActiveSessions, 2633 l2tpDomainStatsControlRecvOctets, 2634 l2tpDomainStatsControlRecvPackets, 2635 l2tpDomainStatsControlSendOctets, 2636 l2tpDomainStatsControlSendPackets, 2637 l2tpDomainStatsPayloadRecvOctets, 2638 l2tpDomainStatsPayloadRecvPackets, 2639 l2tpDomainStatsPayloadRecvDiscards, 2640 l2tpDomainStatsPayloadSendOctets, 2641 l2tpDomainStatsPayloadSendPackets 2642 } 2643 STATUS current 2644 DESCRIPTION 2645 "A collection of objects providing configuration, 2646 status and statistics of L2TP tunnel domains." 2647 ::= { l2tpGroups 4 } 2649 END 2651 5.0 Acknowledgements 2653 This MIB module was updated based on feedback from the IETF's 2654 Point-to-Point Protocol Extensions (PPPEXT) Working Groups. 2656 6.0 References 2658 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2659 Describing SNMP Management Frameworks", RFC 2271, Cabletron 2660 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 2661 January 1998 2663 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 2664 Management Information for TCP/IP-based Internets", RFC 1155, 2665 Performance Systems International, Hughes LAN Systems, May 1990 2667 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 2668 Performance Systems International, Hughes LAN Systems, March 1991 2670 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 2671 RFC 1215, Performance Systems International, March 1991 2673 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2674 Waldbusser, "Structure of Management Information for Version 2 of 2675 the Simple Network Management Protocol (SNMPv2)", RFC 1902, SNMP 2676 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2677 International Network Services, January 1996. 2679 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2680 Waldbusser, "Textual Conventions for Version 2 of the Simple 2681 Network Management Protocol (SNMPv2)", RFC 1903, SNMP Research, 2682 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2683 International Network Services, January 1996. 2685 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2686 Waldbusser, "Conformance Statements for Version 2 of the Simple 2687 Network Management Protocol (SNMPv2)", RFC 1904, SNMP Research, 2688 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2689 International Network Services, January 1996. 2691 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 2692 Management Protocol", RFC 1157, SNMP Research, Performance Systems 2693 International, Performance Systems International, MIT Laboratory 2694 for Computer Science, May 1990. 2696 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2697 Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 2698 SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 2699 Inc., International Network Services, January 1996. 2701 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2702 Waldbusser, "Transport Mappings for Version 2 of the Simple Network 2703 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco 2704 Systems, Inc., Dover Beach Consulting, Inc., International Network 2705 Services, January 1996. 2707 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2708 Processing and Dispatching for the Simple Network Management 2709 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 2710 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 2712 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 2713 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2714 2274, IBM T. J. Watson Research, January 1998. 2716 [13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2717 Waldbusser, "Protocol Operations for Version 2 of the Simple 2718 Network Management Protocol (SNMPv2)", RFC 1905, SNMP Research, 2719 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2720 International Network Services, January 1996. 2722 [14] Levi, D., Meyer, P., and B. Stewart, MPv3 Applications", RFC 2273, 2723 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 2724 January 1998. 2726 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2727 Control Model (VACM) for the Simple Network Management Protocol 2728 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 2729 Cisco Systems, Inc., January 1998. 2731 [16] Valencia et al., "Layer Two Tunneling Protocol - L2TP", 2732 Internet draft (work in progress), 2733 draft-ietf-pppext-l2tp-10.txt, March, 1998. 2735 [17] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", 2736 Work In Progress, Cisco Systems, Argon Networks, 2737 July 1998. 2739 [18] Thaler, D., "IP Tunnel MIB" , Work In Progress, Microsoft, July 1998. 2741 7.0 Authors' Addresses 2743 Pat Calhoun 2744 Sun MicroComputer Corp. 2745 15 Network Circle 2746 Menlo Park, CA, 94025 2747 Pat.Calhoun@Eng.Sun.Com 2749 Gayam Reddy 2750 3Com Corporation 2751 1800 W. Central Ave 2752 Mount Prospect, Il 60031 2753 greddy@usr.com 2755 Bill Vroman 2756 3Com Corporation 2757 1800 W. Central Ave 2758 Mount Prospect, Il 60031 2759 bvroman@usr.com 2761 Ross Wheeler 2762 RouterWare 2763 3961 MacArthur Blvd, Suite 212 2764 Newport Beach, CA 92660 2765 ross@routerware.com 2767 Evan Caves 2768 Advanced Computer Communications 2769 340 Storke Road 2770 Santa Barbara, CA 93117 2771 evan@acc.com