idnits 2.17.1 draft-ietf-pppext-l2tp-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == It seems as if not all pages are separated by form feeds - found 0 form feeds but 68 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 28 instances of too long lines in the document, the longest one being 4 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 408: '...s below, all objects MUST be supported...' RFC 2119 keyword, line 427: '... interfaces MUST be supported as described in [17]....' RFC 2119 keyword, line 916: '...kets to be discarded (which MAY causes...' RFC 2119 keyword, line 1358: '... (which MAY causes the PPP de...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1969 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) == Missing Reference: '24' is mentioned on line 2562, but not defined ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** 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 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) -- Possible downref: Non-RFC (?) normative reference: ref. '16' -- Possible downref: Non-RFC (?) normative reference: ref. '17' -- Possible downref: Non-RFC (?) normative reference: ref. '18' Summary: 15 errors (**), 0 flaws (~~), 5 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 PPP Working Group Evan Caves 2 INTERNET DRAFT Ericsson 3 Category: Internet Draft Pat R. Calhoun 4 Title: draft-ietf-pppext-l2tp-mib-05.txt Sun Microsystems 5 Date: August 1999 Ross Wheeler 6 RouterWare 8 Layer Two Tunneling Protocol "L2TP" 9 Management Information Base 10 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Copyright Notice 35 Copyright (C) The Internet Society (1999). All Rights Reserved. 37 Abstract 39 This memo defines a portion of the Management Information Base (MIB) 40 for use with network management protocols in TCP/IP-based internets. 41 In particular, it defines objects for managing networks using Layer 2 42 Tunneling Protocol. 44 This memo specifies a MIB module in a manner that is both compliant 45 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 46 definitions. 48 Table of Contents 50 1.0 Introduction ......................................... 2 51 1.1 Change Log ............................................. 2 53 2.0 The SNMP Management Framework .......................... 5 55 3.0 Overview ............................................... 6 56 3.1 Relationship to the Interface MIB ...................... 7 57 3.1.1 Layering Model ....................................... 7 58 3.1.2 Interface MIB Objects ................................ 10 59 3.1.2.1 L2TP Tunnel Interfaces ............................. 10 60 3.2 Relationship to other MIBs ............................. 12 61 3.2.1 Relationship to the IP Tunnel MIB .................... 12 62 3.3 L2TP Tunnel Creation ................................... 12 64 4.0 L2TP Object Definitions ................................ 13 66 5.0 Security Considerations ................................ 65 68 6.0 Acknowledgements ....................................... 65 70 7.0 Authors' Addresses ..................................... 65 72 8.0 References ............................................. 66 74 9.0 Full Copyright Statement ............................... 68 76 1.0 Introduction 78 This memo defines a portion of the Management Information Base (MIB) 79 for use with network management protocols in the Internet Community. 80 In particular, it describes managed objects used for managing L2TP 81 devices. 83 1.1 Change Log 85 This section tracks changes made to the revisions of the Internet 86 Drafts of this document. It will be *deleted* when the document is 87 published as an RFC. 89 3 November 1997 91 The following changes were made for the version of the document dated 92 3 November 1997. These changes were made at the request of the L2TP 93 working group. 95 (1) Removed L2TP protocol stack instancing. 97 (2) Tunnel and Session table now extensions of ifTable. 99 (3) Added IP/UDP transport tables. 101 (4) Several objects were removed and a number of new 102 objects added. 104 (5) Sections 1.1, 2.1, 3.0, 5.0 and 6.0 added. 106 (6) Module Compliance information added. 108 27 July 1998 110 The following changes were made for the version of the document dated 111 27 July 1998. These changes were made as a result of the L2TP MIB 112 presentation during the forty-first IETF in Los Angeles. 114 (1) Added Tunnel Domain configuration and stats tables. 116 (2) Moved most of the scalar configuration and stats objects 117 into the Tunnel Domain tables. 119 (3) Redundant objects removed. 121 (4) Some re-organization and object naming clarifications. 123 (5) Updated section 2.0 125 (6) Introduction of L2TP notifications 127 (7) Removed l2tpUdpConfigTable in favour of the tunnelConfigTable 129 (8) Updated section 3.0 131 3 November 1998 133 The following changes were made for the version of the document dated 134 3 Novemer 1998. These changes were made as a result of the L2TP MIB 135 presentation during the forty-second IETF in Chicago. 137 1) A PPP session within a tunnel is no longer represented as a 138 seperate interface that is visible in the ifTable. 140 2) The Layering Model in section 3.1.1 has been updated to 141 reflect that sessions are not seperate interfaces. 143 3) Section 3.1.2.2 'L2TP Session Interfaces' has been removed. 145 4) Tunnel authentication shared secret objects have been added 146 to the l2tpDomainConfigTable and l2tpTunnelConfigTable. 148 5) The l2tpSessionStatsTable indexing has changed to reflect 149 that sessions are not seperate interfaces. 151 6) A mapping table has been added to assist management 152 applications in quickly locating session statistics. 154 7) The objects l2tpUdpStatsAddressChanges and 155 l2tpUdpStatsPortChanges have been removed. 157 8) The l2tpUdpAddressingChange notification has been 158 removed. 160 9) Updated tunnel/session Bearer and Framing capability 161 object enumerations. 163 25 June 1999 165 The following changes were made for the version of the document dated 166 25 June 1999. These changes were made as a result of the changes made 167 to the base L2TP protocol which commenced from draft-ietf-pppext- 168 l2tp-13.txt and onwards. 170 1) Updated 'Status of this Memo' to conform to latest text. 172 2) Added Copyright Notice and Statement. 174 3) Updated 'The SNMP Management Framework' section. 176 4) Removed objects related to payload flow control. 178 6 August 1999 180 The following changes were made for the version of the document dated 181 6 August 1999. These changes were made due to working group comments. 183 1) Added back the object l2tpSessionStatsRecvSeq. 185 2) Renamed l2tpDomainConfigControlRetransmissions to 186 l2tpDomainConfigControlMaxRetransmissions. 188 3) Added l2tpDomainConfigControlMaxRetransmissionTimeout 189 object. 191 4) Renamed l2tpTunnelConfigControlRetransmissions to 192 l2tpTunnelConfigControlMaxRetransmissions. 194 5) Added l2tpTunnelConfigControlMaxRetransmissionTimeout 195 object. 197 6) Minor editorial changes and clarifications to the 'Layering 198 Model' section. 200 2.0 The SNMP Management Framework 202 The SNMP Management Framework presently consists of five major 203 components: 205 o An overall architecture, described in RFC 2271 [1]. 207 o Mechanisms for describing and naming objects and 208 events for the purpose of management. The first 209 version of this Structure of Management Information 210 (SMI) is called SMIv1 and described in RFC 1155 [2], 211 RFC 1212 [3] and RFC 1215 [4]. The second version, 212 called SMIv2, is described in RFC 2578 [5], 213 RFC 2579 [6] and RFC 2580 [7]. 215 o Message protocols for transferring management 216 information. The first version of the SNMP 217 message protocol is called SNMPv1 and described in 218 RFC 1157 [8]. A second version of the SNMP message 219 protocol, which is not an Internet standards track 220 protocol, is called SNMPv2c and described in 221 RFC 1901 [9] and RFC 1905 [13]. The third version 222 of the message protocol is called SNMPv3 and 223 described in RFC 1906 [10], RFC 2572 [11] and 224 RFC 2574 [12]. 226 o Protocol operations for accessing management 227 information. The first set of protocol operations 228 and associated PDU formats is described in 229 RFC 1157 [8]. A second set of protocol operations 230 and associated PDU formats is described in 231 RFC 1905 [13]. 233 o A set of fundamental applications described in 234 RFC 2573 [14] and the view-based access control 235 mechanism described in RFC 2575 [15]. 237 Managed objects are accessed via a virtual information store, termed 238 the Management Information Base or MIB. Objects in the MIB are 239 defined using the mechanisms defined in the SMI. 241 This memo specifies a MIB module that is compliant to the SMIv2. A 242 MIB conforming to the SMIv1 can be produced through the appropriate 243 translations. The resulting translated MIB must be semantically 244 equivalent, except where objects or events are omitted because no 245 translation is possible (e.g., use of Counter64). Some machine 246 readable information in SMIv2 will be converted into textual 247 descriptions in SMIv1 during the translation process. However, this 248 loss of machine readable information is not considered to change the 249 semantics of the MIB. 251 3.0 Overview 253 The objects defined in this MIB are to be used when describing Layer 254 Two Tunneling Protocol (L2TP) tunnels. The L2TP protocol is defined 255 in [16]. This MIB consists of four groups briefly described below: 257 l2tpConfigGroup 258 l2tpStatsGroup 259 These two groups of objects provide information on the 260 configuration, state and statistics of the L2TP protocol, its 261 tunnels and sessions. These groups are mandatory for implementors 262 of this MIB. 264 l2tpDomainGroup 265 This optional group of objects provides configuration, state and 266 statistical information for L2TP tunnel endpoint domains. A L2TP 267 tunnel endpoint domain is considered to be a collection of L2TP 268 devices typically belonging to a common administrative domain or 269 geographic location. 271 l2tpMappingGroup 272 This optional group contains mapping tables to assist management 273 applications to map between protocol identifiers and table 274 indeces. 276 l2tpIpUdpGroup 277 This group provides the state and statistics information for L2TP 278 tunnels which are being transported by IP/UDP. This group is 279 mandatory for L2TP implementations that support L2TP over IP/UDP. 281 3.1 Relationship to the Interface MIB 283 This section clarifies the relationship of this MIB to the Interfaces 284 MIB [17]. Several areas of correlation are addressed in the following 285 subsections. The implementor is referred to the Interfaces MIB 286 document in order to understand the general intent of these areas. 288 3.1.1 Layering Model 290 This MIB contains several tables which are extensions to the IP 291 Tunnel MIB described in [18] which itself defines extensions to the 292 Interface MIB [17]. A L2TP tunnel is represented as a separate 293 identifiable logical interface sub-layer. The tunnel interface 294 appears in the ifStackTable at different stacking points depending on 295 the functionality the tunnel endpoint is providing. 297 At the LAC end of a tunnel endpoint the tunnel interface conceptually 298 appears above the interfaces (for example DS0s) which are being 299 tunneled. At the LNS end of a tunnel endpoint the tunnel interface 300 appears below the PPP interfaces. 302 In the example diagram below, the interface layering is shown as it 303 appears at the LNS. Note that the L2TP tunnel interface is at the 304 bottom of the interface stack when the transport layer for L2TP is 305 IP/UDP. This is because tunneled traffic is forwarded to its 306 destination based on routing policy. However L2TP over transports 307 other than IP/UDP may define further sub-layer interfaces below the 308 tunnel interface. 310 +-------------------------------------------------+ 311 | Network Layer Protocol | 312 +-------------+-------------+--------+------------+ 313 | | | 314 +-+--+ | | 315 |MPPP| | | <=== PPP Multilink I/F 316 ++--++ | | 317 | | | | 318 +--+ +--+ | | 319 | | | | 320 +-+-+ +-+-+ +-+-+ +-+-+ 321 |PPP| |PPP| |PPP| |PPP| <=== PPP I/F 322 +-+-+ +-+-+ +-+-+ +-+-+ 323 | | | | 324 +---------+--------+--------+--------+------------+ 325 | L2TP Tunnel I/F | 326 +-------------------------------------------------+ 328 The ifStackTable is used to describe the layering of the interface 329 sub-layers. For the example given above the ifTable and ifStackTable 330 may appear as follows: 332 ifIndex ifType Tunnel MIB tables Description 334 1 tunnel(131) tunnelIfTable Tunnel interface 335 l2tpTunnelConfigTable 336 l2tpTunnelStatsTable 337 2 ppp(23) PPP interface #1 338 3 ppp(23) PPP interface #2 339 4 ppp(23) PPP interface #3 340 5 ppp(23) PPP interface #4 341 6 mlppp(108) MLPPP interface 343 The corresponding ifStack table entries would then be: 345 ifStackTable Entries 347 HigherLayer LowerLayer 348 0 4 349 0 5 350 0 6 351 1 0 352 2 1 353 3 1 354 4 1 355 5 1 356 6 2 357 6 3 359 The following example diagram illustrates the interface layering as 360 it might occur at the LAC. In this case the tunnel interface is at 361 the top of the interface stack for L2TP over IP/UDP. 363 +-------------------------------------------------+ 364 | L2TP Tunnel I/F | 365 +---------+--------+--------+--------+------------+ 366 | | | | 367 +-+-+ +-+-+ +-+-+ +-+-+ 368 |ds0| |ds0| |ds0| |ds0| <=== B channel I/F 369 +-+-+ +-+-+ +-+-+ +-+-+ 370 | | | | 371 +---------+--------+--------+--------+------------+ 372 | ds1 | 373 +-------------------------------------------------+ 375 For the example given above the ifTable and ifStackTable may appear 376 as follows: 378 ifIndex ifType Tunnel MIB tables Description 380 1 ds1(18) Primary Rate physical 381 interface 382 2 ds0(81) B channel #1 383 3 ds0(81) B channel #2 384 4 ds0(81) B channel #3 385 5 ds0(81) B channel #4 386 6 tunnel(131) tunnelIfTable Tunnel Interface 387 l2tpTunnelConfigTable 388 l2tpTunnelStatsTable 390 The corresponding ifStack table entries would then be: 392 ifStackTable Entries 394 HigherLayer LowerLayer 395 0 6 396 1 0 397 2 1 398 3 1 399 4 1 400 5 1 401 6 2 402 6 3 403 6 4 404 6 5 406 3.1.2 Interface MIB Objects 408 Except where noted in the tables below, all objects MUST be supported 409 from the ifGeneralInformationGroup and one of the following three groups: 411 o ifPacketGroup OR 412 o ifHCPacketGroup OR 413 o ifVHCPacketGroup 415 depending on the particular implementation. 417 The following tables describe how objects from the 418 ifGeneralInformationGroup 419 and ifPacketGroup (similar support should be provided for the high and 420 very 421 high capacity packet groups) are to be interpreted and supported for L2TP 422 tunnel interfaces. 424 3.1.2.1 L2TP Tunnel Interfaces 426 All Interface MIB objects not listed in the above groups for L2TP tunnel 427 interfaces MUST be supported as described in [17]. 429 Interface MIB Object Support Description 430 ==================== ======================================= 431 ifTable.ifDescr Refer to the Interface MIB. 433 ifTable.ifType tunnel(131) 435 ifTable.ifMtu Dependant on the tunnel transport layer. 436 For IP/UDP transports the MTU should 437 be 65467 (65535-60(IP)-8(UDP)) 439 ifTable.ifSpeed Return zero. 441 ifTable.ifPhyAddress The assigned tunnel identifier. 443 ifTable.ifAdminStatus All enumerated values supported as per 444 DESCRIPTION clause in the Interfaces MIB. 446 ifTable.ifOperStatus All status events supported. Refer to the 447 Interfaces MIB. 449 ifTable.ifInOctets The total number of octets received on the 450 tunnel including control and payload 451 octets. 453 ifTable.ifInUcastPkts The total number of packets received on 454 the tunnel including control and payload 455 packets. 457 ifTable.ifInDiscards The total number of received packets that 458 were discarded on both control and payload 459 channels. 461 ifTable.ifInErrors The total number of packets received in 462 error including control and payload 463 packets. 465 ifTable.ifInUnknownProtos 466 Return zero. 468 ifTable.ifOutOctets The total number of octets transmitted from 469 the tunnel including control and payload 470 octets. 472 ifTable.ifOutUcastPkts The total number of packets transmitted from 473 the tunnel including control and payload 474 packets. 476 ifTable.ifOutDiscards The total number of discarded packets that 477 were requested to be transmitted including 478 control and payload packets. 480 ifTable.ifOutErrors The total number of packets that were 481 requested 482 to be transmitted that were in error including 483 control and payload packets. 485 ifXTable.ifName Refer to the Interface MIB. 487 ifXTable.ifInMulticastPkts 488 Return zero. 490 ifXTable.ifInBroadcastPkts 491 Return zero. 493 ifXTable.ifOutMulticastPkts 494 Return zero. 496 ifXTable.ifOutBroadcastPkts 497 Return zero. 499 ifXTable.ifOutBroadcastPkts 500 Return zero. 502 ifXTable.ifLinkUpDownTrapEnable 503 Default set to enabled(1). 505 ifXTable.ifHighSpeed Return zero. 507 ifXTable.ifPromiscuousMode 508 Set to false(2). 510 ifXTable.ifConnectorPresent 511 Set to false(2). 513 3.2 Relationship to other MIBs 515 3.2.1 Relationship to the IP Tunnel MIB 517 The IP Tunnel MIB [18] describes tunnel interfaces that have an ifType 518 of tunnel(131). The IP Tunnel MIB is considered to contain a collection 519 of 520 objects common to all IP tunneling protocols, including L2TP. In addition 521 to the IP Tunnel MIB, tunnel encapsulation specific MIBs (like this MIB) 522 extend the IP Tunnel MIB to further describe encapsulation specific 523 information. Implementation of the IP Tunnel MIB is required for L2TP 524 tunnels over IP. 526 3.3 L2TP Tunnel Creation 528 Tunnel creation is detailed for IP tunnels in the IP Tunnel MIB. The 529 creation of a tunnelIfEntry in [18] will have the side affect of 530 creating entries in the l2tpTunnelConfigTable, l2tpTunnelStatsTable 531 and the l2tpUdpStatsTable's. 533 The creation of L2TP tunnel interfaces over transports other than IP 534 is expected to be defined in the MIB definition for that specific 535 L2TP tunnel transport. 537 4.0 L2TP Object Definitions 539 L2TP-MIB DEFINITIONS ::= BEGIN 541 IMPORTS 542 Integer32, Counter32, experimental, Gauge32, 543 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE 544 FROM SNMPv2-SMI 545 TEXTUAL-CONVENTION, DisplayString, RowStatus, TruthValue 546 FROM SNMPv2-TC 547 OBJECT-GROUP, MODULE-COMPLIANCE 548 FROM SNMPv2-CONF 549 InterfaceIndex 550 FROM IF-MIB; 552 l2tp MODULE-IDENTITY 553 LAST-UPDATED "9908061800Z" 554 ORGANIZATION "IETF L2TP Working Group" 555 CONTACT-INFO 556 "Evan Caves 557 Postal: Ericsson 558 340 Storke Road 559 Santa Barbara, CA, 93117 560 Tel: +1 805685 4455 561 Email: evan@acc.com 563 Pat R. Calhoun 564 Postal: Sun Microsystems, Inc. 565 15 Network Circle 566 Menlo Park, CA, 94025 567 Tel: +1 650786 7733 568 Email: pcalhoun@eng.sun.com 570 Ross Wheeler 571 Postal: RouterWare 572 3961 MacArthur Blvd, Suite 212 573 Newport Beach, CA, 92660 574 Tel: +1 714442 0770 575 Email: ross@routerware.com" 576 DESCRIPTION 577 "The MIB module that describes managed objects of 578 general use by the Layer Two Transport Protocol." 579 ::= { experimental 9999 1 } 581 -- 582 -- Textual Conventions 583 -- 585 MilliSeconds ::= TEXTUAL-CONVENTION 586 DISPLAY-HINT "d-3" 587 STATUS current 588 DESCRIPTION 589 "A period of time measured in units of .001 of seconds 590 when used in conjunction with the DISPLAY-HINT will 591 show seconds and fractions of second with a resolution 592 of .001 of a second." 593 SYNTAX Integer32 (0..2147483646) 595 -- 596 -- Definitions of significant branches 597 -- 598 l2tpObjects OBJECT IDENTIFIER ::= { l2tp 1 } 599 l2tpTraps OBJECT IDENTIFIER ::= { l2tp 2 } 600 l2tpTransports OBJECT IDENTIFIER ::= { l2tp 3 } 601 l2tpConformance OBJECT IDENTIFIER ::= { l2tp 4 } 603 -- 604 -- Definitions of significant branches under l2tpObjects 605 -- 606 l2tpScalar OBJECT IDENTIFIER ::= { l2tpObjects 1 } 607 l2tpConfig OBJECT IDENTIFIER ::= { l2tpScalar 1 } 608 l2tpStats OBJECT IDENTIFIER ::= { l2tpScalar 2 } 610 -- 611 -- Definitions of significant branches under l2tpTransports 612 -- 613 l2tpTransportIpUdp OBJECT IDENTIFIER ::= { l2tpTransports 1 } 614 l2tpIpUdpObjects OBJECT IDENTIFIER ::= { l2tpTransportIpUdp 1 } 615 l2tpIpUdpTraps OBJECT IDENTIFIER ::= { l2tpTransportIpUdp 2 } 616 -- 617 -- The L2TP Scalar Configuration Group 618 -- 619 -- This group of objects is used to manage configuration 620 -- of the L2TP protocol environment. 622 l2pAdminState OBJECT-TYPE 623 SYNTAX INTEGER { 624 enabled(1), 625 disabled(2), 626 drain(3) 627 } 628 MAX-ACCESS read-write 629 STATUS current 630 DESCRIPTION 631 "This object defines the administrative state of 632 this L2TP tunnel domain. Setting this object to 633 'disabled' causes all tunnels to be immediately 634 disconnected and no further tunnels to be either 635 initiated or accepted. Setting this object to 636 'drain' will prevent any new tunnels and/or 637 sessions to be either initiated or accepted but 638 does NOT disconnect any active tunnels/sessions." 639 DEFVAL { enabled } 640 ::= { l2tpConfig 1 } 642 -- 643 -- The L2TP Scalar Status and Statistics Group 644 -- 645 -- This group of objects describe the current state and 646 -- statistics of L2TP. 648 l2tpProtocolVersion OBJECT-TYPE 649 SYNTAX OCTET STRING (SIZE(2..256)) 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION 653 "Vector of supported L2TP protocol version and 654 revision numbers. Supported versions are identified 655 via a two octet pairing where the first octet indicates 656 the version and the second octet contains the revision." 657 ::= { l2tpStats 1 } 659 l2tpVendorName OBJECT-TYPE 660 SYNTAX DisplayString 661 MAX-ACCESS read-only 662 STATUS current 663 DESCRIPTION 664 "This object identifies the Vendor name of the L2TP 665 protocol stack." 666 ::= { l2tpStats 2 } 668 l2tpFirmwareRev OBJECT-TYPE 669 SYNTAX Integer32 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "This object defines the firmware revision for the 674 L2TP protocol stack." 675 ::= { l2tpStats 3 } 677 -- 678 -- The L2TP Domain Configuration Table 679 -- 680 -- This table contains objects that can be used to 681 -- configure the operational characteristics of a tunnel 682 -- domain. 684 l2tpDomainConfigTable OBJECT-TYPE 685 SYNTAX SEQUENCE OF L2tpDomainConfigEntry 686 MAX-ACCESS not-accessible 687 STATUS current 688 DESCRIPTION 689 "The L2TP Domain configuration table." 690 ::= { l2tpObjects 2 } 692 l2tpDomainConfigEntry OBJECT-TYPE 693 SYNTAX L2tpDomainConfigEntry 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "An L2TP Domain configuration entry. An entry in this 698 table may correspond to a single endpoint or a group 699 of tunnel endpoints." 700 INDEX { IMPLIED l2tpDomainConfigIdentifier } 701 ::= { l2tpDomainConfigTable 1 } 703 L2tpDomainConfigEntry ::= 704 SEQUENCE { 705 l2tpDomainConfigIdentifier 706 DisplayString, 707 l2pDomainConfigAdminState 708 INTEGER, 709 l2tpDomainConfigAuthentication 710 INTEGER, 711 l2tpDomainConfigSecret 712 OCTET STRING, 713 l2tpDomainConfigTunnelSecurity 714 INTEGER, 715 l2tpDomainConfigTunnelHelloInterval 716 Integer32, 717 l2tpDomainConfigTunnelIdleTimeout 718 Integer32, 719 l2tpDomainConfigControlRWS 720 Integer32, 721 l2tpDomainConfigControlMaxRetransmissions 722 Integer32, 723 l2tpDomainConfigControlMaxRetransmissionTimeout 724 Integer32, 726 l2tpDomainConfigPayloadSequencing 727 INTEGER, 728 l2tpDomainConfigReassemblyTimeout 729 MilliSeconds, 730 l2tpDomainConfigStatus 731 RowStatus 732 } 734 l2tpDomainConfigIdentifier OBJECT-TYPE 735 SYNTAX DisplayString (SIZE (1..255)) 736 MAX-ACCESS not-accessible 737 STATUS current 738 DESCRIPTION 739 "The identifier, usually in the form of a Domain 740 Name (full or partial), describing a single tunnel 741 endpoint or a domain of tunnel endpoints. This is 742 typically used as a 'handle' to identify the 743 tunnel configuration requirements for both incoming 744 and outgoing tunnel connection attempts. Both the 745 LAC and LNS could use information provided in the 746 Host Name AVP attribute however the tunnel initiator 747 could use other means not specified to identify 748 the domains tunnel configuration requirements. For 749 example; three rows in this table have 750 l2tpDomainConfigIdentifier values of 'lac1.isp.com', 751 'isp.com' and 'com'. A tunnel endpoint then identifies 752 itself as 'lac1.isp.com' which would match the 753 'lac1.isp.com' entry in this table. A second tunnel 754 endpoint then identifies itself as 'lac2.isp.com'. 755 This endpoint is then associated with the 'isp.com' 756 entry of this table." 757 ::= { l2tpDomainConfigEntry 1 } 759 l2pDomainConfigAdminState OBJECT-TYPE 760 SYNTAX INTEGER { 761 enabled(1), 762 disabled(2), 763 drain(3) 764 } 765 MAX-ACCESS read-create 766 STATUS current 767 DESCRIPTION 768 "This object defines the administrative state of this 769 tunnel domain. Setting this object to disabled(2) 770 causes all tunnels to be immediately disconnected 771 and no further tunnels to be either initiated or 772 accepted. Setting this object to drain(3) will prevent 773 any new tunnels and/or sessions to be either initiated 774 or accepted but does NOT forcibly disconnect any 775 active tunnels and/or sessions." 776 DEFVAL { enabled } 777 ::= { l2tpDomainConfigEntry 2 } 779 l2tpDomainConfigAuthentication OBJECT-TYPE 780 SYNTAX INTEGER { 781 none(1), 782 simple(2), 783 challenge(3) 784 } 785 MAX-ACCESS read-create 786 STATUS current 787 DESCRIPTION 788 "This object describes how tunnel peers belonging 789 to this domain are to be authenticated. The value 790 simple(2) indicates that peers are authenticated simply 791 by their host name as described in the Host Name AVP. 792 The value challenge(3) indicates that all peers are 793 challenged to prove their identification. This mechanism 794 is described in the L2TP protocol." 795 DEFVAL { none } 796 ::= { l2tpDomainConfigEntry 3 } 798 l2tpDomainConfigSecret OBJECT-TYPE 799 SYNTAX OCTET STRING (SIZE (0..255)) 800 MAX-ACCESS read-create 801 STATUS current 802 DESCRIPTION 803 "This object is used to configure the shared secret 804 used during the tunnel authentication phase of 805 tunnel establishment. NOTE that this object should 806 not be visible if the proper SNMPv3 security 807 mechanisms are in place." 808 ::= { l2tpDomainConfigEntry 4 } 810 l2tpDomainConfigTunnelSecurity OBJECT-TYPE 811 SYNTAX INTEGER { 812 none(1), 813 other(2), 814 ipSec(3) 815 } 816 MAX-ACCESS read-create 817 STATUS current 818 DESCRIPTION 819 "This object defines whether this tunnel domain 820 requires that all tunnels are to be secured. The 821 value of ipsec(3) indicates that all tunnel packets, 822 control and session, have IP Security headers. The 823 type of IP Security headers (AH, ESP etc) and how 824 they are further described is outside the scope of 825 this document." 826 DEFVAL { none } 827 ::= { l2tpDomainConfigEntry 5 } 829 l2tpDomainConfigTunnelHelloInterval OBJECT-TYPE 830 SYNTAX Integer32 (0..3600) 831 MAX-ACCESS read-create 832 STATUS current 833 DESCRIPTION 834 "This object defines the interval (in seconds) in 835 which Hello (or keep-alive) packets are to be sent 836 by local peers belonging to this tunnel domain." 837 DEFVAL { 60 } 838 ::= { l2tpDomainConfigEntry 6 } 840 l2tpDomainConfigTunnelIdleTimeout OBJECT-TYPE 841 SYNTAX Integer32 (0..86400) 842 MAX-ACCESS read-create 843 STATUS current 844 DESCRIPTION 845 "This object defines the period of time (in seconds) 846 that an established tunnel belonging to this tunnel 847 domain with no active sessions will wait before 848 disconnecting the tunnel. A value of zero indicates 849 that the tunnel will disconnect immediately after the 850 last session disconnects." 851 DEFVAL { 0 } 852 ::= { l2tpDomainConfigEntry 7 } 854 l2tpDomainConfigControlRWS OBJECT-TYPE 855 SYNTAX Integer32 (1..64) 856 MAX-ACCESS read-create 857 STATUS current 858 DESCRIPTION 859 "This object defines the control channel receive 860 window size for tunnels belonging to this domain. It 861 specifies the maximum number of packets the tunnel 862 peer belonging to this domain can send without waiting 863 for an acknowledgement from this peer." 864 DEFVAL { 4 } 865 ::= { l2tpDomainConfigEntry 8 } 867 l2tpDomainConfigControlMaxRetransmissions OBJECT-TYPE 868 SYNTAX Integer32 (0..32) 869 MAX-ACCESS read-create 870 STATUS current 871 DESCRIPTION 872 "This object defines the maximum number of retransmission's 873 which the L2TP stack will attempt for tunnels belonging 874 to this domain before assuming that the peer is no 875 longer responding." 876 DEFVAL { 5 } 877 ::= { l2tpDomainConfigEntry 9 } 879 l2tpDomainConfigControlMaxRetransmissionTimeout OBJECT-TYPE 880 SYNTAX Integer32 (1..32) 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "This object defines the maximum retransmission timeout 885 interval which the L2TP stack will wait for tunnels 886 belonging to this domain before retransmitting a control 887 packet that has not been acknowledged." 888 DEFVAL { 16 } 889 ::= { l2tpDomainConfigEntry 10 } 891 l2tpDomainConfigPayloadSequencing OBJECT-TYPE 892 SYNTAX INTEGER { 893 onDemand(1), 894 never(2), 895 always(3) 896 } 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 { onDemand } 904 ::= { l2tpDomainConfigEntry 11 } 906 l2tpDomainConfigReassemblyTimeout OBJECT-TYPE 907 SYNTAX MilliSeconds 908 MAX-ACCESS read-create 909 STATUS current 910 DESCRIPTION 911 "This object defines the number of milliseconds that 912 local peer's of this tunnel domain will wait before 913 processing payload packets that were received out of 914 sequence (which are waiting for the packet(s) to put 915 them in sequence). A low value increases the chance 916 of delayed packets to be discarded (which MAY causes 917 the PPP decompression engine to reset) while a high 918 value may cause more queueing and possibly degrade 919 throughput if packets are truly lost. The default 920 value for this object is zero which will result in 921 all delayed packets being lost." 922 DEFVAL { 0 } 923 ::= { l2tpDomainConfigEntry 12 } 925 l2tpDomainConfigStatus OBJECT-TYPE 926 SYNTAX RowStatus 927 MAX-ACCESS read-create 928 STATUS current 929 DESCRIPTION 930 "The status of this Domain entry." 931 ::= { l2tpDomainConfigEntry 13 } 933 -- 934 -- The L2TP Domain Status and Statistics Table 935 -- 936 -- This table contains objects that can be used to desribe 937 -- the current status and statistics of a tunnel domain. 939 l2tpDomainStatsTable OBJECT-TYPE 940 SYNTAX SEQUENCE OF L2tpDomainStatsEntry 941 MAX-ACCESS not-accessible 942 STATUS current 943 DESCRIPTION 944 "The L2TP Domain Status and Statistics table." 945 ::= { l2tpObjects 3 } 947 l2tpDomainStatsEntry OBJECT-TYPE 948 SYNTAX L2tpDomainStatsEntry 949 MAX-ACCESS not-accessible 950 STATUS current 951 DESCRIPTION 952 "An L2TP Domain Stats entry. An entry in this table 953 may correspond to a single endpoint or a group of 954 tunnel endpoints." 955 INDEX { IMPLIED l2tpDomainStatsIdentifier } 956 ::= { l2tpDomainStatsTable 1 } 958 L2tpDomainStatsEntry ::= 959 SEQUENCE { 960 l2tpDomainStatsIdentifier 961 DisplayString, 962 l2tpDomainStatsTotalTunnels 963 Counter32, 964 l2tpDomainStatsFailedTunnels 965 Counter32, 966 l2tpDomainStatsFailedAuthentications 967 Counter32, 968 l2tpDomainStatsActiveTunnels 969 Gauge32, 970 l2tpDomainStatsTotalSessions 971 Counter32, 972 l2tpDomainStatsFailedSessions 973 Counter32, 974 l2tpDomainStatsActiveSessions 975 Gauge32, 976 l2tpDomainStatsControlRecvOctets 977 Counter32, 978 l2tpDomainStatsControlRecvPackets 979 Counter32, 980 l2tpDomainStatsControlSendOctets 981 Counter32, 982 l2tpDomainStatsControlSendPackets 983 Counter32, 984 l2tpDomainStatsPayloadRecvOctets 985 Counter32, 986 l2tpDomainStatsPayloadRecvPackets 987 Counter32, 988 l2tpDomainStatsPayloadRecvDiscards 989 Counter32, 990 l2tpDomainStatsPayloadSendOctets 991 Counter32, 992 l2tpDomainStatsPayloadSendPackets 993 Counter32 994 } 996 l2tpDomainStatsIdentifier OBJECT-TYPE 997 SYNTAX DisplayString (SIZE (1..255)) 998 MAX-ACCESS not-accessible 999 STATUS current 1000 DESCRIPTION 1001 "The identifier, usually in the form of a Domain 1002 Name (full or partial), describing a single tunnel 1003 endpoint or a domain of tunnel endpoints." 1004 ::= { l2tpDomainStatsEntry 1 } 1006 l2tpDomainStatsTotalTunnels OBJECT-TYPE 1007 SYNTAX Counter32 1008 MAX-ACCESS read-only 1009 STATUS current 1010 DESCRIPTION 1011 "This object returns the total number of tunnels 1012 that have successfully reached the established 1013 state for this tunnel domain." 1014 ::= { l2tpDomainStatsEntry 2 } 1016 l2tpDomainStatsFailedTunnels OBJECT-TYPE 1017 SYNTAX Counter32 1018 MAX-ACCESS read-only 1019 STATUS current 1020 DESCRIPTION 1021 "This object returns the number of tunnels that 1022 failed to reach the established state for this 1023 tunnel domain." 1024 ::= { l2tpDomainStatsEntry 3 } 1026 l2tpDomainStatsFailedAuthentications OBJECT-TYPE 1027 SYNTAX Counter32 1028 MAX-ACCESS read-only 1029 STATUS current 1030 DESCRIPTION 1031 "This object returns the number of failed tunnel 1032 connection attempts for this domain because the 1033 tunnel peer failed authentication." 1034 ::= { l2tpDomainStatsEntry 4 } 1036 l2tpDomainStatsActiveTunnels OBJECT-TYPE 1037 SYNTAX Gauge32 1038 MAX-ACCESS read-only 1039 STATUS current 1040 DESCRIPTION 1041 "This object returns the number of tunnels that 1042 are currently active for this domain." 1043 ::= { l2tpDomainStatsEntry 5 } 1045 l2tpDomainStatsTotalSessions OBJECT-TYPE 1046 SYNTAX Counter32 1047 MAX-ACCESS read-only 1048 STATUS current 1049 DESCRIPTION 1050 "This object returns the total number of sessions 1051 that have successfully reached the established state 1052 for this tunnel domain." 1053 ::= { l2tpDomainStatsEntry 6 } 1055 l2tpDomainStatsFailedSessions OBJECT-TYPE 1056 SYNTAX Counter32 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "This object returns the number of sessions that 1061 failed to reach the established state for this 1062 tunnel domain." 1063 ::= { l2tpDomainStatsEntry 7 } 1065 l2tpDomainStatsActiveSessions OBJECT-TYPE 1066 SYNTAX Gauge32 1067 MAX-ACCESS read-only 1068 STATUS current 1069 DESCRIPTION 1070 "This object returns the number of sessions that 1071 are currently active for this domain." 1072 ::= { l2tpDomainStatsEntry 8 } 1074 l2tpDomainStatsControlRecvOctets OBJECT-TYPE 1075 SYNTAX Counter32 1076 MAX-ACCESS read-only 1077 STATUS current 1078 DESCRIPTION 1079 "This object returns the number of control channel 1080 octets received for this tunnel domain." 1081 ::= { l2tpDomainStatsEntry 9 } 1083 l2tpDomainStatsControlRecvPackets OBJECT-TYPE 1084 SYNTAX Counter32 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 "This object returns the number of control packets 1089 received for this tunnel domain." 1090 ::= { l2tpDomainStatsEntry 10 } 1092 l2tpDomainStatsControlSendOctets OBJECT-TYPE 1093 SYNTAX Counter32 1094 MAX-ACCESS read-only 1095 STATUS current 1096 DESCRIPTION 1097 "This object returns the number of control channel 1098 octets that were transmitted to tunnel endpoints 1099 for this domain." 1100 ::= { l2tpDomainStatsEntry 11 } 1102 l2tpDomainStatsControlSendPackets OBJECT-TYPE 1103 SYNTAX Counter32 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "This object returns the number of control packets 1108 that were transmitted to tunnel endpoints for 1109 this domain." 1110 ::= { l2tpDomainStatsEntry 12 } 1112 l2tpDomainStatsPayloadRecvOctets OBJECT-TYPE 1113 SYNTAX Counter32 1114 MAX-ACCESS read-only 1115 STATUS current 1116 DESCRIPTION 1117 "This object returns the number of payload channel 1118 octets that were received for this tunnel domain." 1119 ::= { l2tpDomainStatsEntry 13 } 1121 l2tpDomainStatsPayloadRecvPackets OBJECT-TYPE 1122 SYNTAX Counter32 1123 MAX-ACCESS read-only 1124 STATUS current 1125 DESCRIPTION 1126 "This object returns the number of payload packets 1127 that were received for this tunnel domain." 1128 ::= { l2tpDomainStatsEntry 14 } 1130 l2tpDomainStatsPayloadRecvDiscards OBJECT-TYPE 1131 SYNTAX Counter32 1132 MAX-ACCESS read-only 1133 STATUS current 1134 DESCRIPTION 1135 "This object returns the number of received payload 1136 packets that were discarded by this this tunnel 1137 domain." 1138 ::= { l2tpDomainStatsEntry 15 } 1140 l2tpDomainStatsPayloadSendOctets OBJECT-TYPE 1141 SYNTAX Counter32 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION 1145 "This object returns the number of payload channel 1146 octets that were transmitted to tunnel peers 1147 within this tunnel domain." 1148 ::= { l2tpDomainStatsEntry 16 } 1150 l2tpDomainStatsPayloadSendPackets OBJECT-TYPE 1151 SYNTAX Counter32 1152 MAX-ACCESS read-only 1153 STATUS current 1154 DESCRIPTION 1155 "This object returns the number of payload packets 1156 that were transmitted to tunnel peers within 1157 this tunnel domain." 1158 ::= { l2tpDomainStatsEntry 17 } 1160 -- 1161 -- The L2TP Tunnel Configuration Table 1162 -- 1163 -- This table contains objects that can be used to 1164 -- (re)configure the operational characteristics of a 1165 -- single L2TP tunnel. 1167 l2tpTunnelConfigTable OBJECT-TYPE 1168 SYNTAX SEQUENCE OF L2tpTunnelConfigEntry 1169 MAX-ACCESS not-accessible 1170 STATUS current 1171 DESCRIPTION 1172 "The L2TP tunnel configuration table." 1173 ::= { l2tpObjects 4 } 1175 l2tpTunnelConfigEntry OBJECT-TYPE 1176 SYNTAX L2tpTunnelConfigEntry 1177 MAX-ACCESS not-accessible 1178 STATUS current 1179 DESCRIPTION 1180 "A L2TP tunnel interface configuration entry." 1181 INDEX { l2tpTunnelConfigIfIndex } 1182 ::= { l2tpTunnelConfigTable 1 } 1184 L2tpTunnelConfigEntry ::= 1185 SEQUENCE { 1186 l2tpTunnelConfigIfIndex 1187 InterfaceIndex, 1188 l2tpTunnelConfigAuthentication 1189 INTEGER, 1190 l2tpTunnelConfigSecret 1191 OCTET STRING, 1192 l2tpTunnelConfigSecurity 1193 INTEGER, 1194 l2tpTunnelConfigHelloInterval 1195 Integer32, 1196 l2tpTunnelConfigIdleTimeout 1197 Integer32, 1198 l2tpTunnelConfigControlRWS 1199 Integer32, 1200 l2tpTunnelConfigControlMaxRetransmissions 1201 Integer32, 1202 l2tpTunnelConfigControlMaxRetransmissionTimeout 1203 Integer32, 1204 l2tpTunnelConfigPayloadSequencing 1205 INTEGER, 1206 l2tpTunnelConfigReassemblyTimeout 1207 MilliSeconds, 1209 l2tpTunnelConfigTransport 1210 INTEGER 1211 } 1213 l2tpTunnelConfigIfIndex OBJECT-TYPE 1214 SYNTAX InterfaceIndex 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "This value for this object is equal to the value 1219 of ifIndex of the Interfaces MIB for tunnel 1220 interfaces of type L2TP." 1221 ::= { l2tpTunnelConfigEntry 1 } 1223 l2tpTunnelConfigAuthentication OBJECT-TYPE 1224 SYNTAX INTEGER { 1225 none(1), 1226 simple(2), 1227 challenge(3) 1228 } 1229 MAX-ACCESS read-write 1230 STATUS current 1231 DESCRIPTION 1232 "This object describes how L2TP tunnel peers are 1233 to be authenticated. The value 'simple' indicates 1234 that peers are authenticated simply by their host 1235 name as described in the Host Name AVP. The value 1236 'challenge' indicates that all peers are challenged 1237 to prove their identification. This mechanism is 1238 described in the L2TP protocol." 1239 DEFVAL { none } 1240 ::= { l2tpTunnelConfigEntry 2 } 1242 l2tpTunnelConfigSecret OBJECT-TYPE 1243 SYNTAX OCTET STRING (SIZE (0..255)) 1244 MAX-ACCESS read-write 1245 STATUS current 1246 DESCRIPTION 1247 "This object is used to configure the shared secret 1248 used during the tunnel authentication phase of 1249 tunnel establishment. NOTE that this object should 1250 not be visible if the proper SNMPv3 security 1251 mechanisms are in place." 1252 ::= { l2tpTunnelConfigEntry 3 } 1254 l2tpTunnelConfigSecurity OBJECT-TYPE 1255 SYNTAX INTEGER { 1256 none(1), 1257 other(2), 1258 ipsec(3) 1259 } 1260 MAX-ACCESS read-write 1261 STATUS current 1262 DESCRIPTION 1263 "This object defines whether this tunnel is to be 1264 secured. The value of 'ipSec' indicates that all 1265 tunnel packets, control and session, have IP 1266 Security headers. The type of IP Security headers 1267 (AH, ESP etc) and how they are further described 1268 is outside the scope of this document." 1269 DEFVAL { none } 1270 ::= { l2tpTunnelConfigEntry 4 } 1272 l2tpTunnelConfigHelloInterval OBJECT-TYPE 1273 SYNTAX Integer32 (0..3600) 1274 MAX-ACCESS read-write 1275 STATUS current 1276 DESCRIPTION 1277 "This object defines the interval (in seconds) in 1278 which Hello (or keep-alive) packets are to be sent 1279 to the tunnel peer." 1280 DEFVAL { 60 } 1281 ::= { l2tpTunnelConfigEntry 5 } 1283 l2tpTunnelConfigIdleTimeout OBJECT-TYPE 1284 SYNTAX Integer32 (0..86400) 1285 MAX-ACCESS read-write 1286 STATUS current 1287 DESCRIPTION 1288 "This object defines the period of time (in seconds) 1289 that an established tunnel with no sessions will 1290 wait before disconnecting the tunnel. A value of 1291 zero indicates that the tunnel will disconnect 1292 immediately after the last session disconnects." 1293 DEFVAL { 0 } 1294 ::= { l2tpTunnelConfigEntry 6 } 1296 l2tpTunnelConfigControlRWS OBJECT-TYPE 1297 SYNTAX Integer32 (1..64) 1298 MAX-ACCESS read-write 1299 STATUS current 1300 DESCRIPTION 1301 "This object defines the control channel receive 1302 window size. It specifies the maximum number of 1303 packets the tunnel peer can send without waiting 1304 for an acknowledgement from this peer." 1306 DEFVAL { 4 } 1307 ::= { l2tpTunnelConfigEntry 7 } 1309 l2tpTunnelConfigControlMaxRetransmissions OBJECT-TYPE 1310 SYNTAX Integer32 (0..32) 1311 MAX-ACCESS read-write 1312 STATUS current 1313 DESCRIPTION 1314 "This object defines the number of retransmission's 1315 which the tunnel will attempt before assuming that 1316 the peer is no longer responding. A value of zero 1317 indicates that this peer will not attempt to 1318 retransmit an unacknowledged control packet." 1319 DEFVAL { 5 } 1320 ::= { l2tpTunnelConfigEntry 8 } 1322 l2tpTunnelConfigControlMaxRetransmissionTimeout OBJECT-TYPE 1323 SYNTAX Integer32 (1..32) 1324 MAX-ACCESS read-write 1325 STATUS current 1326 DESCRIPTION 1327 "This object defines the maximum retransmission timeout 1328 interval which the tunnel will wait before retransmitting 1329 a control packet that has not been acknowledged." 1330 DEFVAL { 16 } 1331 ::= { l2tpTunnelConfigEntry 9 } 1333 l2tpTunnelConfigPayloadSequencing OBJECT-TYPE 1334 SYNTAX INTEGER { 1335 onDemand(1), 1336 never(2), 1337 always(3) 1338 } 1339 MAX-ACCESS read-write 1340 STATUS current 1341 DESCRIPTION 1342 "This object determines whether or not session payload 1343 packets will be requested to be sent with sequence 1344 numbers from the tunnel peer." 1345 DEFVAL { onDemand } 1346 ::= { l2tpTunnelConfigEntry 10 } 1348 l2tpTunnelConfigReassemblyTimeout OBJECT-TYPE 1349 SYNTAX MilliSeconds 1350 MAX-ACCESS read-write 1351 STATUS current 1352 DESCRIPTION 1353 "This object defines the number of milliseconds that 1354 this tunnel will wait before processing payload packets 1355 that were received out of sequence (which are waiting 1356 for the packet(s) to put them in sequence). A low value 1357 increases the chance of delayed packets to be discarded 1358 (which MAY causes the PPP decompression engine to 1359 reset) while a high value may cause more queueing and 1360 possibly degrade throughput if packets are truly lost. 1361 The default value for this object is zero which will 1362 result in all delayed packets being lost." 1363 DEFVAL { 0 } 1364 ::= { l2tpTunnelConfigEntry 11 } 1366 l2tpTunnelConfigTransport OBJECT-TYPE 1367 SYNTAX INTEGER { 1368 other(1), 1369 none(2), 1370 ipUdp(3), 1371 frameRelay(4) 1372 } 1373 MAX-ACCESS read-write 1374 STATUS current 1375 DESCRIPTION 1376 "This object defines the underlying transport media 1377 that is in use for this tunnel entry. Different tunnel 1378 transports may define MIB extensions to the L2TP tunnel 1379 table to realize the transport layer. For example if the 1380 value of this object is 'ipUdp' then the value of ifIndex 1381 for this table may be used to determine state from the 1382 l2tpUdpStatsTable." 1383 ::= { l2tpTunnelConfigEntry 12 } 1385 -- 1386 -- The L2TP Tunnel Status and Statisticss Table 1387 -- 1388 -- This table contains objects that can be used to describe 1389 -- the current status and statistics of a single L2TP tunnel. 1391 l2tpTunnelStatsTable OBJECT-TYPE 1392 SYNTAX SEQUENCE OF L2tpTunnelStatsEntry 1393 MAX-ACCESS not-accessible 1394 STATUS current 1395 DESCRIPTION 1396 "The L2TP tunnel status and statistics table." 1397 ::= { l2tpObjects 5 } 1399 l2tpTunnelStatsEntry OBJECT-TYPE 1400 SYNTAX L2tpTunnelStatsEntry 1401 MAX-ACCESS not-accessible 1402 STATUS current 1403 DESCRIPTION 1404 "An L2TP tunnel interface stats entry." 1405 INDEX { l2tpTunnelStatsIfIndex } 1406 ::= { l2tpTunnelStatsTable 1 } 1408 L2tpTunnelStatsEntry ::= 1409 SEQUENCE { 1410 l2tpTunnelStatsIfIndex 1411 InterfaceIndex, 1412 l2tpTunnelStatsLocalTID 1413 Integer32, 1414 l2tpTunnelStatsRemoteTID 1415 Integer32, 1416 l2tpTunnelStatsState 1417 INTEGER, 1418 l2tpTunnelStatsInitiated 1419 INTEGER, 1420 l2tpTunnelStatsRemoteHostName 1421 DisplayString, 1422 l2tpTunnelStatsRemoteVendorName 1423 DisplayString, 1424 l2tpTunnelStatsRemoteFirmwareRevision 1425 Integer32, 1426 l2tpTunnelStatsRemoteProtocolVersion 1427 OCTET STRING, 1428 l2tpTunnelStatsInitialRemoteRWS 1429 Integer32, 1430 l2tpTunnelStatsBearerCapabilities 1431 INTEGER, 1433 l2tpTunnelStatsFramingCapabilities 1434 INTEGER, 1435 l2tpTunnelStatsControlRecvPackets 1436 Counter32, 1437 l2tpTunnelStatsControlRecvZLB 1438 Counter32, 1439 l2tpTunnelStatsControlOutOfSequence 1440 Counter32, 1441 l2tpTunnelStatsControlOutOfWindow 1442 Counter32, 1443 l2tpTunnelStatsControlSendPackets 1444 Counter32, 1445 l2tpTunnelStatsControlSendZLB 1446 Counter32, 1447 l2tpTunnelStatsControlAckTimeouts 1448 Counter32, 1449 l2tpTunnelStatsCurrentRemoteRWS 1450 Gauge32, 1451 l2tpTunnelStatsSendSeq 1452 Integer32, 1453 l2tpTunnelStatsSendSeqAck 1454 Integer32, 1455 l2tpTunnelStatsRecvSeq 1456 Integer32, 1457 l2tpTunnelStatsRecvSeqAck 1458 Integer32, 1459 l2tpTunnelStatsTotalSessions 1460 Counter32, 1461 l2tpTunnelStatsFailedSessions 1462 Counter32, 1463 l2tpTunnelStatsActiveSessions 1464 Gauge32, 1465 l2tpTunnelStatsLastResultCode 1466 Integer32, 1467 l2tpTunnelStatsLastErrorCode 1468 Integer32, 1469 l2tpTunnelStatsLastErrorMessage 1470 DisplayString 1471 } 1473 l2tpTunnelStatsIfIndex OBJECT-TYPE 1474 SYNTAX InterfaceIndex 1475 MAX-ACCESS read-only 1476 STATUS current 1477 DESCRIPTION 1478 "This value for this object is equal to the value 1479 of ifIndex of the Interfaces MIB for tunnel 1480 interfaces of type L2TP." 1482 ::= { l2tpTunnelStatsEntry 1 } 1484 l2tpTunnelStatsLocalTID OBJECT-TYPE 1485 SYNTAX Integer32 (0..65535) 1486 MAX-ACCESS read-only 1487 STATUS current 1488 DESCRIPTION 1489 "This object contains the local tunnel Identifier." 1490 ::= { l2tpTunnelStatsEntry 2 } 1492 l2tpTunnelStatsRemoteTID OBJECT-TYPE 1493 SYNTAX Integer32 (0..65535) 1494 MAX-ACCESS read-only 1495 STATUS current 1496 DESCRIPTION 1497 "This object contains the remote tunnel Identifier." 1498 ::= { l2tpTunnelStatsEntry 3 } 1500 l2tpTunnelStatsState OBJECT-TYPE 1501 SYNTAX INTEGER { 1502 tunnelIdle(1), 1503 tunnelConnecting(2), 1504 tunnelEstablished(3), 1505 tunnelDisconnecting(4) 1506 } 1507 MAX-ACCESS read-only 1508 STATUS current 1509 DESCRIPTION 1510 "This field contains the current state of the control 1511 tunnel." 1512 ::= { l2tpTunnelStatsEntry 4 } 1514 l2tpTunnelStatsInitiated OBJECT-TYPE 1515 SYNTAX INTEGER { 1516 locally(1), 1517 remotely(2) 1518 } 1519 MAX-ACCESS read-only 1520 STATUS current 1521 DESCRIPTION 1522 "This object indicates whether the tunnel was 1523 initiated locally or by the remote tunnel peer." 1524 ::= { l2tpTunnelStatsEntry 5 } 1526 l2tpTunnelStatsRemoteHostName OBJECT-TYPE 1527 SYNTAX DisplayString 1528 MAX-ACCESS read-only 1529 STATUS current 1530 DESCRIPTION 1531 "This object contains the host name as discovered 1532 during the tunnel establishment phase (via the Host 1533 Name AVP) of the L2TP peer. If the tunnel is idle 1534 this object should maintain its value from the last 1535 time it was connected." 1536 ::= { l2tpTunnelStatsEntry 6 } 1538 l2tpTunnelStatsRemoteVendorName OBJECT-TYPE 1539 SYNTAX DisplayString 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "This object identifies the vendor name of the peer's 1544 L2TP implementation. If the tunnel is idle this 1545 object should maintain its value from the last time 1546 it was connected." 1547 ::= { l2tpTunnelStatsEntry 7 } 1549 l2tpTunnelStatsRemoteFirmwareRevision OBJECT-TYPE 1550 SYNTAX Integer32 1551 MAX-ACCESS read-only 1552 STATUS current 1553 DESCRIPTION 1554 "This object contains the tunnel peer's firmware 1555 revision number. If the tunnel is idle this object 1556 should maintain its value from the last time it 1557 was connected." 1558 ::= { l2tpTunnelStatsEntry 8 } 1560 l2tpTunnelStatsRemoteProtocolVersion OBJECT-TYPE 1561 SYNTAX OCTET STRING (SIZE(2)) 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "This object describes the protocol version and 1566 revision of the tunnel peers implementation. The 1567 first octet contains the protocol version. The 1568 second octet contains the protocol revision." 1569 ::= { l2tpTunnelStatsEntry 9 } 1571 l2tpTunnelStatsInitialRemoteRWS OBJECT-TYPE 1572 SYNTAX Integer32 (0..65535) 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "This object contains the initial remote peers 1577 receive window size as indicated by the tunnel peer 1578 (in the RWS AVP) during the tunnel establishment 1579 phase. If the tunnel is idle this object should 1580 maintain its value from the last time it was 1581 connected." 1582 ::= { l2tpTunnelStatsEntry 10 } 1584 l2tpTunnelStatsBearerCapabilities OBJECT-TYPE 1585 SYNTAX INTEGER { 1586 none(1), 1587 digital(2), 1588 analog(3), 1589 digitalAnalog(4) 1590 } 1591 MAX-ACCESS read-only 1592 STATUS current 1593 DESCRIPTION 1594 "This object describes the Bearer Capabilities of 1595 the tunnel peer. If the tunnel is idle this object 1596 should maintain its value from the last time it was 1597 connected." 1598 ::= { l2tpTunnelStatsEntry 11 } 1600 l2tpTunnelStatsFramingCapabilities OBJECT-TYPE 1601 SYNTAX INTEGER { 1602 none(1), 1603 sync(2), 1604 async(3), 1605 syncAsync(4) 1606 } 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "This object describes the Framing Capabilities of 1611 the tunnel peer. If the tunnel is idle this object 1612 should maintain its value from the last time it was 1613 connected." 1614 ::= { l2tpTunnelStatsEntry 12 } 1616 l2tpTunnelStatsControlRecvPackets OBJECT-TYPE 1617 SYNTAX Counter32 1618 MAX-ACCESS read-only 1619 STATUS current 1620 DESCRIPTION 1621 "This object contains the number of control packets 1622 received on the tunnel." 1623 ::= { l2tpTunnelStatsEntry 13 } 1625 l2tpTunnelStatsControlRecvZLB OBJECT-TYPE 1626 SYNTAX Counter32 1627 MAX-ACCESS read-only 1628 STATUS current 1629 DESCRIPTION 1630 "This object returns a count of the number of Zero 1631 Length Body control packet acknowledgement packets 1632 that were received." 1633 ::= { l2tpTunnelStatsEntry 14 } 1635 l2tpTunnelStatsControlOutOfSequence OBJECT-TYPE 1636 SYNTAX Counter32 1637 MAX-ACCESS read-only 1638 STATUS current 1639 DESCRIPTION 1640 "This object returns a count of the number of 1641 control packets that were not received in the 1642 correct order (as per the sequence number) on 1643 this tunnel." 1644 ::= { l2tpTunnelStatsEntry 15 } 1646 l2tpTunnelStatsControlOutOfWindow OBJECT-TYPE 1647 SYNTAX Counter32 1648 MAX-ACCESS read-only 1649 STATUS current 1650 DESCRIPTION 1651 "This object contains the number of control 1652 packets that were received outside of the 1653 offered receive window. It is implementation 1654 specific as to whether these packets are queued 1655 or discarded." 1656 ::= { l2tpTunnelStatsEntry 16 } 1658 l2tpTunnelStatsControlSendPackets OBJECT-TYPE 1659 SYNTAX Counter32 1660 MAX-ACCESS read-only 1661 STATUS current 1662 DESCRIPTION 1663 "This object contains the number of control 1664 packets that were transmitted to the tunnel 1665 peer." 1666 ::= { l2tpTunnelStatsEntry 17 } 1668 l2tpTunnelStatsControlSendZLB OBJECT-TYPE 1669 SYNTAX Counter32 1670 MAX-ACCESS read-only 1671 STATUS current 1672 DESCRIPTION 1673 "This object contains the number of Zero Length 1674 Body control packets transmitted transitted to 1675 the tunnel peer." 1676 ::= { l2tpTunnelStatsEntry 18 } 1678 l2tpTunnelStatsControlAckTimeouts OBJECT-TYPE 1679 SYNTAX Counter32 1680 MAX-ACCESS read-only 1681 STATUS current 1682 DESCRIPTION 1683 "This object returns a count of the number of 1684 control packet timeouts due to the lack of a 1685 timely acknowledgement from the tunnel peer." 1686 ::= { l2tpTunnelStatsEntry 19 } 1688 l2tpTunnelStatsCurrentRemoteRWS OBJECT-TYPE 1689 SYNTAX Gauge32 (0..64) 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "This object contains the current remote receive 1694 window size as determined by the local flow 1695 control mechanism employed." 1696 ::= { l2tpTunnelStatsEntry 20 } 1698 l2tpTunnelStatsSendSeq OBJECT-TYPE 1699 SYNTAX Integer32 (0..65535) 1700 MAX-ACCESS read-only 1701 STATUS current 1702 DESCRIPTION 1703 "This object contains the next send sequence number 1704 for the control channel." 1705 ::= { l2tpTunnelStatsEntry 21 } 1707 l2tpTunnelStatsSendSeqAck OBJECT-TYPE 1708 SYNTAX Integer32 (0..65535) 1709 MAX-ACCESS read-only 1710 STATUS current 1711 DESCRIPTION 1712 "This object contains the send sequence number that 1713 the tunnel peer has acknowledged for the control 1714 channel. The flow control state can be determined 1715 by subtracting the l2tpTunnelStatsSendSeq from 1716 l2tpTunnelStatsSendSeqAck and comparing this value 1717 to l2tpTunnelStatsCurrentRemoteRWS." 1718 ::= { l2tpTunnelStatsEntry 22 } 1720 l2tpTunnelStatsRecvSeq OBJECT-TYPE 1721 SYNTAX Integer32 (0..65535) 1722 MAX-ACCESS read-only 1723 STATUS current 1724 DESCRIPTION 1725 "This object contains the next receive sequence 1726 number expected to be received on this control 1727 channel." 1728 ::= { l2tpTunnelStatsEntry 23 } 1730 l2tpTunnelStatsRecvSeqAck OBJECT-TYPE 1731 SYNTAX Integer32 (0..65535) 1732 MAX-ACCESS read-only 1733 STATUS current 1734 DESCRIPTION 1735 "This object contains the last receive sequence 1736 number that was acknowledged back to the tunnel 1737 peer for the control channel." 1738 ::= { l2tpTunnelStatsEntry 24 } 1740 l2tpTunnelStatsTotalSessions OBJECT-TYPE 1741 SYNTAX Counter32 1742 MAX-ACCESS read-only 1743 STATUS current 1744 DESCRIPTION 1745 "This object contains the total number of sessions 1746 that this tunnel has successfully connected through 1747 to its tunnel peer since this tunnel was created." 1748 ::= { l2tpTunnelStatsEntry 25 } 1750 l2tpTunnelStatsFailedSessions OBJECT-TYPE 1751 SYNTAX Counter32 1752 MAX-ACCESS read-only 1753 STATUS current 1754 DESCRIPTION 1755 "This object contains the total number of sessions 1756 that were initiated but failed to reach the 1757 established phase." 1758 ::= { l2tpTunnelStatsEntry 26 } 1760 l2tpTunnelStatsActiveSessions OBJECT-TYPE 1761 SYNTAX Gauge32 1762 MAX-ACCESS read-only 1763 STATUS current 1764 DESCRIPTION 1765 "This object contains the total number of sessions 1766 in the established state for this tunnel." 1767 ::= { l2tpTunnelStatsEntry 27 } 1769 l2tpTunnelStatsLastResultCode OBJECT-TYPE 1770 SYNTAX Integer32 (0..65535) 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION 1774 "This object contains the last value of the result 1775 code as described in the Result Code AVP which 1776 caused the tunnel to disconnect." 1777 ::= { l2tpTunnelStatsEntry 28 } 1779 l2tpTunnelStatsLastErrorCode OBJECT-TYPE 1780 SYNTAX Integer32 (0..65535) 1781 MAX-ACCESS read-only 1782 STATUS current 1783 DESCRIPTION 1784 "This object contains the last value of the error 1785 code as described in the Result Code AVP which 1786 caused the tunnel to disconnect." 1787 ::= { l2tpTunnelStatsEntry 29 } 1789 l2tpTunnelStatsLastErrorMessage OBJECT-TYPE 1790 SYNTAX DisplayString 1791 MAX-ACCESS read-only 1792 STATUS current 1793 DESCRIPTION 1794 "This object contains the last value of the optional 1795 message as described in the Result Code AVP which 1796 caused the tunnel to disconnect." 1797 ::= { l2tpTunnelStatsEntry 30 } 1799 -- 1800 -- { l2tpObjects 6 } reserved for future use 1801 -- 1802 -- 1803 -- The L2TP Session Status and Statistics Table 1804 -- 1805 -- This table contains the objects that can be used to 1806 -- describe the current status and statistics of a single 1807 -- L2TP tunneled session. 1809 l2tpSessionStatsTable OBJECT-TYPE 1810 SYNTAX SEQUENCE OF L2tpSessionStatsEntry 1811 MAX-ACCESS not-accessible 1812 STATUS current 1813 DESCRIPTION 1814 "The L2TP session status and statistics table." 1815 ::= { l2tpObjects 7 } 1817 l2tpSessionStatsEntry OBJECT-TYPE 1818 SYNTAX L2tpSessionStatsEntry 1819 MAX-ACCESS not-accessible 1820 STATUS current 1821 DESCRIPTION 1822 "An L2TP session interface stats entry." 1823 INDEX { l2tpSessionStatsTunnelIfIndex, l2tpSessionStatsLocalCID } 1824 ::= { l2tpSessionStatsTable 1 } 1826 L2tpSessionStatsEntry ::= 1827 SEQUENCE { 1828 l2tpSessionStatsTunnelIfIndex 1829 InterfaceIndex, 1830 l2tpSessionStatsHLIfIndex 1831 InterfaceIndex, 1832 l2tpSessionStatsLocalCID 1833 Integer32, 1834 l2tpSessionStatsRemoteCID 1835 Integer32, 1836 l2tpSessionStatsUserName 1837 DisplayString, 1838 l2tpSessionStatsState 1839 INTEGER, 1840 l2tpSessionStatsCallType 1841 INTEGER, 1842 l2tpSessionStatsCallSerialNumber 1843 Integer32, 1844 l2tpSessionStatsTxConnectSpeed 1845 Integer32, 1846 l2tpSessionStatsRxConnectSpeed 1847 Integer32, 1848 l2tpSessionStatsCallBearerType 1849 INTEGER, 1850 l2tpSessionStatsFramingType 1851 INTEGER, 1852 l2tpSessionStatsPhysChanId 1853 Integer32, 1854 l2tpSessionStatsDNIS 1855 DisplayString, 1856 l2tpSessionStatsCLID 1857 DisplayString, 1858 l2tpSessionStatsSubAddress 1859 DisplayString, 1860 l2tpSessionStatsPrivateGroupID 1861 DisplayString, 1862 l2tpSessionStatsProxyLcp 1863 TruthValue, 1864 l2tpSessionStatsAuthMethod 1865 INTEGER, 1866 l2tpSessionStatsSequencingState 1867 INTEGER, 1868 l2tpSessionStatsOutSequence 1869 Counter32, 1870 l2tpSessionStatsReassemblyTimeouts 1871 Counter32, 1872 l2tpSessionStatsSendSeq 1873 Integer32, 1874 l2tpSessionStatsRecvSeq 1875 Integer32 1876 } 1878 l2tpSessionStatsTunnelIfIndex OBJECT-TYPE 1879 SYNTAX InterfaceIndex 1880 MAX-ACCESS read-only 1881 STATUS current 1882 DESCRIPTION 1883 "This object identifies the sessions associated 1884 L2TP tunnel ifIndex value." 1885 ::= { l2tpSessionStatsEntry 1 } 1887 l2tpSessionStatsHLIfIndex OBJECT-TYPE 1888 SYNTAX InterfaceIndex 1889 MAX-ACCESS read-only 1890 STATUS current 1891 DESCRIPTION 1892 "This object identifies the ifIndex value of the 1893 interface that is either below (Lower) the tunnel 1894 (if this tunnel endpoint is a LAC) or above 1895 (Higher) the tunnel (if this tunnel endpoint is a 1896 LNS). For example this could be a DS0 ifIndex on a 1897 LAC or it would be the PPP ifIndex on the LNS." 1898 ::= { l2tpSessionStatsEntry 2 } 1900 l2tpSessionStatsLocalCID OBJECT-TYPE 1901 SYNTAX Integer32 (0..65535) 1902 MAX-ACCESS read-only 1903 STATUS current 1904 DESCRIPTION 1905 "This object contains the local call identifier 1906 for the session." 1907 ::= { l2tpSessionStatsEntry 3 } 1909 l2tpSessionStatsRemoteCID OBJECT-TYPE 1910 SYNTAX Integer32 (0..65535) 1911 MAX-ACCESS read-only 1912 STATUS current 1913 DESCRIPTION 1914 "This object contains the remote call identifier 1915 for the session." 1916 ::= { l2tpSessionStatsEntry 4 } 1918 l2tpSessionStatsUserName OBJECT-TYPE 1919 SYNTAX DisplayString 1920 MAX-ACCESS read-only 1921 STATUS current 1922 DESCRIPTION 1923 "This object identifies the peer session name on 1924 this interface. This is typically the login name 1925 of the remote user. If the user name is unknown to 1926 the local tunnel peer then this object will contain 1927 a null string." 1928 ::= { l2tpSessionStatsEntry 5 } 1930 l2tpSessionStatsState OBJECT-TYPE 1931 SYNTAX INTEGER { 1932 sessionIdle(1), 1933 sessionConnecting(2), 1934 sessionEstablished(3), 1935 sessionDisconnecting(4) 1936 } 1937 MAX-ACCESS read-only 1938 STATUS current 1939 DESCRIPTION 1940 "This object contains the current state of the 1941 session." 1942 ::= { l2tpSessionStatsEntry 6 } 1944 l2tpSessionStatsCallType OBJECT-TYPE 1945 SYNTAX INTEGER { 1946 lacIncoming(1), 1947 lnsIncoming(2), 1948 lacOutgoing(3), 1949 lnsOutgoing(4) 1950 } 1951 MAX-ACCESS read-only 1952 STATUS current 1953 DESCRIPTION 1954 "This object indicates the type of call and the 1955 role this tunnel peer is providing for this 1956 session. For example, lacIncoming(1) indicates 1957 that this tunnel peer is acting as a LAC and 1958 generated a Incoming-Call-Request to the tunnel 1959 peer (the LNS). Note that tunnel peers can be 1960 both LAC and LNS simultaneously." 1961 ::= { l2tpSessionStatsEntry 7 } 1963 l2tpSessionStatsCallSerialNumber OBJECT-TYPE 1964 SYNTAX Integer32 1965 MAX-ACCESS read-only 1966 STATUS current 1967 DESCRIPTION 1968 "This object contains the serial number that has 1969 been assigned to this session." 1970 ::= { l2tpSessionStatsEntry 8 } 1972 l2tpSessionStatsTxConnectSpeed OBJECT-TYPE 1973 SYNTAX Integer32 1974 MAX-ACCESS read-only 1975 STATUS current 1976 DESCRIPTION 1977 "This object returns the last known transmit 1978 baud rate for this session." 1979 ::= { l2tpSessionStatsEntry 9 } 1981 l2tpSessionStatsRxConnectSpeed OBJECT-TYPE 1982 SYNTAX Integer32 1983 MAX-ACCESS read-only 1984 STATUS current 1985 DESCRIPTION 1986 "This object returns the last known receive 1987 baud rate for this session established." 1988 ::= { l2tpSessionStatsEntry 10 } 1990 l2tpSessionStatsCallBearerType OBJECT-TYPE 1991 SYNTAX INTEGER { 1992 none(1), 1993 digital(2), 1994 analog(3) 1995 } 1996 MAX-ACCESS read-only 1997 STATUS current 1998 DESCRIPTION 1999 "This object describes the bearer type of this 2000 session." 2001 ::= { l2tpSessionStatsEntry 11 } 2003 l2tpSessionStatsFramingType OBJECT-TYPE 2004 SYNTAX INTEGER { 2005 none(1), 2006 sync(2), 2007 async(3) 2008 } 2009 MAX-ACCESS read-only 2010 STATUS current 2011 DESCRIPTION 2012 "This object describes the framing type of this 2013 session." 2014 ::= { l2tpSessionStatsEntry 12 } 2016 l2tpSessionStatsPhysChanId OBJECT-TYPE 2017 SYNTAX Integer32 2018 MAX-ACCESS read-only 2019 STATUS current 2020 DESCRIPTION 2021 "This object contains the physical channel 2022 identifier for the session." 2023 ::= { l2tpSessionStatsEntry 13 } 2025 l2tpSessionStatsDNIS OBJECT-TYPE 2026 SYNTAX DisplayString 2027 MAX-ACCESS read-only 2028 STATUS current 2029 DESCRIPTION 2030 "This object identifies the Dialed Number 2031 Information String that the LAC obtained from 2032 the network for the session. If no DNIS was 2033 provided then a null string will be returned." 2034 ::= { l2tpSessionStatsEntry 14 } 2036 l2tpSessionStatsCLID OBJECT-TYPE 2037 SYNTAX DisplayString 2038 MAX-ACCESS read-only 2039 STATUS current 2040 DESCRIPTION 2041 "This object identifies the Calling Line ID 2042 that the LAC obtained from the network for 2043 the session. If no CLID was provided then a 2044 null string will be returned." 2045 ::= { l2tpSessionStatsEntry 15 } 2047 l2tpSessionStatsSubAddress OBJECT-TYPE 2048 SYNTAX DisplayString 2049 MAX-ACCESS read-only 2050 STATUS current 2051 DESCRIPTION 2052 "This object identifies the Sub Address that 2053 the LAC obtained from the network for the 2054 session. If no Sub Address was provided then 2055 a null string will be returned." 2056 ::= { l2tpSessionStatsEntry 16 } 2058 l2tpSessionStatsPrivateGroupID OBJECT-TYPE 2059 SYNTAX DisplayString 2060 MAX-ACCESS read-only 2061 STATUS current 2062 DESCRIPTION 2063 "This object identifies the Private Group 2064 Identifier used for this tunneled session. 2065 If no Private Group Identifier was provided 2066 then a null string will be returned." 2067 ::= { l2tpSessionStatsEntry 17 } 2069 l2tpSessionStatsProxyLcp OBJECT-TYPE 2070 SYNTAX TruthValue 2071 MAX-ACCESS read-only 2072 STATUS current 2073 DESCRIPTION 2074 "Indicates whether the LAC performed proxy LCP 2075 for this session." 2076 ::= { l2tpSessionStatsEntry 18 } 2078 l2tpSessionStatsAuthMethod OBJECT-TYPE 2079 SYNTAX INTEGER { 2080 none(1), 2081 text(2), 2082 pppChap(3), 2083 pppPap(4), 2084 pppEap(5) 2085 } 2086 MAX-ACCESS read-only 2087 STATUS current 2088 DESCRIPTION 2089 "This object contains the proxy authentication 2090 method employed by the LAC for the session. If 2091 l2tpSessionProxyLcp is false(2) this object should 2092 not be interpreted." 2093 ::= { l2tpSessionStatsEntry 19 } 2095 l2tpSessionStatsSequencingState OBJECT-TYPE 2096 SYNTAX INTEGER { 2097 none(1), 2098 remote(2), 2099 local(3), 2100 both(4) 2101 } 2102 MAX-ACCESS read-only 2103 STATUS current 2104 DESCRIPTION 2105 "This object defines which tunnel peers have 2106 requested payload sequencing. The value of 2107 both(4) indicates that both peers have requested 2108 payload sequencing." 2109 ::= { l2tpSessionStatsEntry 20 } 2111 l2tpSessionStatsOutSequence OBJECT-TYPE 2112 SYNTAX Counter32 2113 MAX-ACCESS read-only 2114 STATUS current 2115 DESCRIPTION 2116 "This object returns the total number of packets 2117 received for this session which were received out 2118 of sequence." 2119 ::= { l2tpSessionStatsEntry 21 } 2121 l2tpSessionStatsReassemblyTimeouts OBJECT-TYPE 2122 SYNTAX Counter32 2123 MAX-ACCESS read-only 2124 STATUS current 2125 DESCRIPTION 2126 "This object returns the number of reassembly 2127 timeouts that have occured for this session." 2128 ::= { l2tpSessionStatsEntry 22 } 2130 l2tpSessionStatsSendSeq OBJECT-TYPE 2131 SYNTAX Integer32 (0..65535) 2132 MAX-ACCESS read-only 2133 STATUS current 2134 DESCRIPTION 2135 "This object contains the next send sequence number 2136 for for this session." 2138 ::= { l2tpSessionStatsEntry 23 } 2140 l2tpSessionStatsRecvSeq OBJECT-TYPE 2141 SYNTAX Integer32 (0..65535) 2142 MAX-ACCESS read-only 2143 STATUS current 2144 DESCRIPTION 2145 "This object contains the next receive sequence 2146 number expected to be received on this session." 2147 ::= { l2tpSessionStatsEntry 24 } 2149 -- 2150 -- The L2TP Tunnel Mapping Table 2151 -- 2152 -- This table is intended to assist management 2153 -- applications to quickly determine what the ifIndex 2154 -- value is for a given local tunnel identifier. 2156 l2tpTunnelMapTable OBJECT-TYPE 2157 SYNTAX SEQUENCE OF L2tpTunnelMapEntry 2158 MAX-ACCESS not-accessible 2159 STATUS current 2160 DESCRIPTION 2161 "The L2TP Tunnel index mapping table." 2162 ::= { l2tpObjects 8 } 2164 l2tpTunnelMapEntry OBJECT-TYPE 2165 SYNTAX L2tpTunnelMapEntry 2166 MAX-ACCESS not-accessible 2167 STATUS current 2168 DESCRIPTION 2169 "An L2TP tunnel index map entry." 2170 INDEX { l2tpTunnelMapLocalTID } 2171 ::= { l2tpTunnelMapTable 1 } 2173 L2tpTunnelMapEntry ::= 2174 SEQUENCE { 2175 l2tpTunnelMapLocalTID 2176 Integer32, 2177 l2tpTunnelMapIfIndex 2178 InterfaceIndex 2179 } 2181 l2tpTunnelMapLocalTID OBJECT-TYPE 2182 SYNTAX Integer32 (0..65535) 2183 MAX-ACCESS read-only 2184 STATUS current 2185 DESCRIPTION 2186 "This object contains the local tunnel Identifier." 2187 ::= { l2tpTunnelMapEntry 1 } 2189 l2tpTunnelMapIfIndex OBJECT-TYPE 2190 SYNTAX InterfaceIndex 2191 MAX-ACCESS read-only 2192 STATUS current 2193 DESCRIPTION 2194 "This value for this object is equal to the value 2195 of ifIndex of the Interfaces MIB for tunnel 2196 interfaces of type L2TP." 2198 ::= { l2tpTunnelMapEntry 2 } 2200 -- 2201 -- The L2TP Session Mapping Table 2202 -- 2203 -- This table is intended to assist management 2204 -- applications to quickly determine what the instance 2205 -- value is for a given upper or lower ifIndex. 2207 l2tpSessionMapTable OBJECT-TYPE 2208 SYNTAX SEQUENCE OF L2tpSessionMapEntry 2209 MAX-ACCESS not-accessible 2210 STATUS current 2211 DESCRIPTION 2212 "The L2TP Session index mapping table." 2213 ::= { l2tpObjects 9 } 2215 l2tpSessionMapEntry OBJECT-TYPE 2216 SYNTAX L2tpSessionMapEntry 2217 MAX-ACCESS not-accessible 2218 STATUS current 2219 DESCRIPTION 2220 "An L2TP Session index map entry." 2221 INDEX { l2tpSessionMapHLifIndex } 2222 ::= { l2tpSessionMapTable 1 } 2224 L2tpSessionMapEntry ::= 2225 SEQUENCE { 2226 l2tpSessionMapHLifIndex 2227 InterfaceIndex, 2228 l2tpSessionMapTunnelIfIndex 2229 InterfaceIndex, 2230 l2tpSessionMapLocalCID 2231 Integer32 2232 } 2234 l2tpSessionMapHLifIndex OBJECT-TYPE 2235 SYNTAX InterfaceIndex 2236 MAX-ACCESS read-only 2237 STATUS current 2238 DESCRIPTION 2239 "This object identifies the ifIndex value of the 2240 interface that is either below (Lower) the tunnel 2241 (if this tunnel endpoint is a LAC) or above 2242 (Higher) the tunnel (if this tunnel endpoint is a 2243 LNS). For example this could be a DS0 ifIndex on a 2244 LAC or it would be the PPP ifIndex on the LNS." 2245 ::= { l2tpSessionMapEntry 1 } 2247 l2tpSessionMapTunnelIfIndex OBJECT-TYPE 2248 SYNTAX InterfaceIndex 2249 MAX-ACCESS read-only 2250 STATUS current 2251 DESCRIPTION 2252 "This object identifies the sessions associated 2253 L2TP tunnel ifIndex value." 2254 ::= { l2tpSessionMapEntry 2 } 2256 l2tpSessionMapLocalCID OBJECT-TYPE 2257 SYNTAX Integer32 (0..65535) 2258 MAX-ACCESS read-only 2259 STATUS current 2260 DESCRIPTION 2261 "This object contains the local call identifier 2262 for the session." 2263 ::= { l2tpSessionMapEntry 3 } 2265 -- 2266 -- { l2tpIpUdpObjects 1 } reserved for future use 2267 -- 2268 -- The L2TP IP/UDP Transport Status and Statistics Table 2269 -- 2270 -- This table contains objects that can be used to 2271 -- describe the current status and statistics of the 2272 -- IP/UDP L2TP tunnel transport. 2274 l2tpUdpStatsTable OBJECT-TYPE 2275 SYNTAX SEQUENCE OF L2tpUdpStatsEntry 2276 MAX-ACCESS not-accessible 2277 STATUS current 2278 DESCRIPTION 2279 "The L2TP IP/UDP transport stats table." 2280 ::= { l2tpIpUdpObjects 2 } 2282 l2tpUdpStatsEntry OBJECT-TYPE 2283 SYNTAX L2tpUdpStatsEntry 2284 MAX-ACCESS not-accessible 2285 STATUS current 2286 DESCRIPTION 2287 "An L2TP IP/UDP transport stats entry." 2288 INDEX { l2tpUdpStatsIfIndex } 2289 ::= { l2tpUdpStatsTable 1 } 2291 L2tpUdpStatsEntry ::= 2292 SEQUENCE { 2293 l2tpUdpStatsIfIndex 2294 InterfaceIndex, 2295 l2tpUdpStatsPeerPort 2296 Integer32, 2297 l2tpUdpStatsLocalPort 2298 Integer32 2299 } 2301 l2tpUdpStatsIfIndex OBJECT-TYPE 2302 SYNTAX InterfaceIndex 2303 MAX-ACCESS read-only 2304 STATUS current 2305 DESCRIPTION 2306 "This value for this object is equal to the 2307 value of ifIndex of the Interfaces MIB for 2308 tunnel interfaces of type L2TP and which have 2309 a L2TP transport of IP/UDP." 2310 ::= { l2tpUdpStatsEntry 1 } 2312 l2tpUdpStatsPeerPort OBJECT-TYPE 2313 SYNTAX Integer32 (0..65535) 2314 MAX-ACCESS read-only 2315 STATUS current 2316 DESCRIPTION 2317 "This object reflects the peer's UDP port number 2318 of the last packet received." 2319 ::= { l2tpUdpStatsEntry 2 } 2321 l2tpUdpStatsLocalPort OBJECT-TYPE 2322 SYNTAX Integer32 (0..65535) 2323 MAX-ACCESS read-only 2324 STATUS current 2325 DESCRIPTION 2326 "This object reflects the local UDP port number 2327 that this tunnel is bound to." 2328 ::= { l2tpUdpStatsEntry 3 } 2330 -- 2331 -- Definition of generic L2TP traps 2332 -- 2334 l2tpTunnelAuthFailure NOTIFICATION-TYPE 2335 OBJECTS { 2336 l2tpTunnelStatsIfIndex, 2337 l2tpTunnelStatsInitiated, 2338 l2tpTunnelStatsRemoteHostName 2339 } 2340 STATUS current 2341 DESCRIPTION 2342 "A l2tpTunnelAuthFailure trap signifies that an 2343 attempt to establish a tunnel to a remote peer 2344 has failed authentication." 2345 ::= { l2tpTraps 1 } 2347 -- 2348 -- conformance information 2349 -- 2351 l2tpGroups OBJECT IDENTIFIER ::= { l2tpConformance 1 } 2352 l2tpCompliances OBJECT IDENTIFIER ::= { l2tpConformance 2 } 2354 -- 2355 -- compliance statements 2356 -- 2358 l2tpCompliance MODULE-COMPLIANCE 2359 STATUS current 2360 DESCRIPTION 2361 "The compliance statement for SNMPv2 entities 2362 which implement the L2TP MIB." 2364 MODULE -- this module 2366 -- unconditionally mandatory groups 2367 MANDATORY-GROUPS { 2368 l2tpConfigGroup, 2369 l2tpStatsGroup 2370 } 2372 -- conditionally mandatory groups 2373 GROUP l2tpIpUdpGroup 2374 DESCRIPTION 2375 "This group is mandatory for implementations that 2376 support L2TP over IP/UDP." 2378 -- optional groups 2379 GROUP l2tpDomainGroup 2380 DESCRIPTION 2381 "This group is optional for L2TP devices that desire 2382 to group tunnel endpoints into tunnel domains." 2384 GROUP l2tpMappingGroup 2385 DESCRIPTION 2386 "This group is optional for L2TP devices that wish 2387 to provide index mapping." 2389 ::= { l2tpCompliances 1 } 2391 -- units of conformance 2393 l2tpConfigGroup OBJECT-GROUP 2394 OBJECTS { 2395 l2pAdminState, 2396 l2tpTunnelConfigIfIndex, 2397 l2tpTunnelConfigAuthentication, 2398 l2tpTunnelConfigSecret, 2399 l2tpTunnelConfigSecurity, 2400 l2tpTunnelConfigHelloInterval, 2401 l2tpTunnelConfigIdleTimeout, 2402 l2tpTunnelConfigControlRWS, 2403 l2tpTunnelConfigControlMaxRetransmissions, 2404 l2tpTunnelConfigControlMaxRetransmissionTimeout, 2405 l2tpTunnelConfigPayloadSequencing, 2406 l2tpTunnelConfigReassemblyTimeout, 2407 l2tpTunnelConfigTransport 2408 } 2409 STATUS current 2410 DESCRIPTION 2411 "A collection of objects providing configuration 2412 information of the L2TP protocol, tunnels and sessions." 2413 ::= { l2tpGroups 1 } 2415 l2tpStatsGroup OBJECT-GROUP 2416 OBJECTS { 2417 l2tpProtocolVersion, 2418 l2tpVendorName, 2419 l2tpFirmwareRev, 2420 l2tpTunnelStatsIfIndex, 2421 l2tpTunnelStatsLocalTID, 2422 l2tpTunnelStatsRemoteTID, 2423 l2tpTunnelStatsState, 2424 l2tpTunnelStatsInitiated, 2425 l2tpTunnelStatsRemoteHostName, 2426 l2tpTunnelStatsRemoteVendorName, 2427 l2tpTunnelStatsRemoteFirmwareRevision, 2428 l2tpTunnelStatsRemoteProtocolVersion, 2429 l2tpTunnelStatsInitialRemoteRWS, 2430 l2tpTunnelStatsBearerCapabilities, 2431 l2tpTunnelStatsFramingCapabilities, 2432 l2tpTunnelStatsControlRecvPackets, 2433 l2tpTunnelStatsControlRecvZLB, 2434 l2tpTunnelStatsControlOutOfSequence, 2435 l2tpTunnelStatsControlOutOfWindow, 2436 l2tpTunnelStatsControlSendPackets, 2437 l2tpTunnelStatsControlSendZLB, 2438 l2tpTunnelStatsControlAckTimeouts, 2439 l2tpTunnelStatsCurrentRemoteRWS, 2440 l2tpTunnelStatsSendSeq, 2441 l2tpTunnelStatsSendSeqAck, 2442 l2tpTunnelStatsRecvSeq, 2443 l2tpTunnelStatsRecvSeqAck, 2444 l2tpTunnelStatsTotalSessions, 2445 l2tpTunnelStatsFailedSessions, 2446 l2tpTunnelStatsActiveSessions, 2447 l2tpTunnelStatsLastResultCode, 2448 l2tpTunnelStatsLastErrorCode, 2449 l2tpTunnelStatsLastErrorMessage, 2450 l2tpSessionStatsTunnelIfIndex, 2451 l2tpSessionStatsHLIfIndex, 2452 l2tpSessionStatsLocalCID, 2453 l2tpSessionStatsRemoteCID, 2454 l2tpSessionStatsUserName, 2455 l2tpSessionStatsState, 2456 l2tpSessionStatsCallType, 2457 l2tpSessionStatsCallSerialNumber, 2458 l2tpSessionStatsTxConnectSpeed, 2459 l2tpSessionStatsRxConnectSpeed, 2460 l2tpSessionStatsCallBearerType, 2461 l2tpSessionStatsFramingType, 2462 l2tpSessionStatsPhysChanId, 2463 l2tpSessionStatsDNIS, 2464 l2tpSessionStatsCLID, 2465 l2tpSessionStatsSubAddress, 2466 l2tpSessionStatsPrivateGroupID, 2467 l2tpSessionStatsProxyLcp, 2468 l2tpSessionStatsAuthMethod, 2469 l2tpSessionStatsSequencingState, 2470 l2tpSessionStatsOutSequence, 2471 l2tpSessionStatsReassemblyTimeouts, 2472 l2tpSessionStatsSendSeq, 2473 l2tpSessionStatsRecvSeq 2474 } 2475 STATUS current 2476 DESCRIPTION 2477 "A collection of objects providing status and 2478 statistics of the L2TP protocol, tunnels and 2479 sessions." 2480 ::= { l2tpGroups 2 } 2482 l2tpIpUdpGroup OBJECT-GROUP 2483 OBJECTS { 2484 l2tpUdpStatsIfIndex, 2485 l2tpUdpStatsPeerPort, 2486 l2tpUdpStatsLocalPort 2487 } 2488 STATUS current 2489 DESCRIPTION 2490 "A collection of objects providing status and 2491 statistics of the L2TP IP/UDP transport layer." 2492 ::= { l2tpGroups 3 } 2494 l2tpDomainGroup OBJECT-GROUP 2495 OBJECTS { 2496 l2pDomainConfigAdminState, 2497 l2tpDomainConfigAuthentication, 2498 l2tpDomainConfigSecret, 2499 l2tpDomainConfigTunnelSecurity, 2500 l2tpDomainConfigTunnelHelloInterval, 2501 l2tpDomainConfigTunnelIdleTimeout, 2502 l2tpDomainConfigControlRWS, 2503 l2tpDomainConfigControlMaxRetransmissions, 2504 l2tpDomainConfigControlMaxRetransmissionTimeout, 2505 l2tpDomainConfigPayloadSequencing, 2506 l2tpDomainConfigReassemblyTimeout, 2507 l2tpDomainConfigStatus, 2508 l2tpDomainStatsTotalTunnels, 2509 l2tpDomainStatsFailedTunnels, 2510 l2tpDomainStatsFailedAuthentications, 2511 l2tpDomainStatsActiveTunnels, 2512 l2tpDomainStatsTotalSessions, 2513 l2tpDomainStatsFailedSessions, 2514 l2tpDomainStatsActiveSessions, 2515 l2tpDomainStatsControlRecvOctets, 2516 l2tpDomainStatsControlRecvPackets, 2517 l2tpDomainStatsControlSendOctets, 2518 l2tpDomainStatsControlSendPackets, 2519 l2tpDomainStatsPayloadRecvOctets, 2520 l2tpDomainStatsPayloadRecvPackets, 2521 l2tpDomainStatsPayloadRecvDiscards, 2522 l2tpDomainStatsPayloadSendOctets, 2523 l2tpDomainStatsPayloadSendPackets 2524 } 2525 STATUS current 2526 DESCRIPTION 2527 "A collection of objects providing configuration, 2528 status and statistics of L2TP tunnel domains." 2529 ::= { l2tpGroups 4 } 2531 l2tpMappingGroup OBJECT-GROUP 2532 OBJECTS { 2533 l2tpTunnelMapLocalTID, 2534 l2tpTunnelMapIfIndex, 2535 l2tpSessionMapHLifIndex, 2536 l2tpSessionMapTunnelIfIndex, 2537 l2tpSessionMapLocalCID 2539 } 2540 STATUS current 2541 DESCRIPTION 2542 "A collection of objects providing index mapping." 2543 ::= { l2tpGroups 5 } 2545 END 2547 5.0 Security Considerations 2549 This MIB contains readable objects whose values provide information 2550 related to L2TP tunnel interfaces. There are also a number of objects 2551 that have a MAX-ACCESS clause of read-write and/or read-create, such as 2552 those which allow an administrator to dynamically configure tunnels. 2554 While unauthorized access to the readable objects is relatively 2555 innocuous, unauthorized access to the write-able objects could cause a 2556 denial of service, or could cause unauthorized creation and/or 2557 manipulation of tunnels. Hence, the support for SET operations in a 2558 non-secure environment without proper protection can have a negative 2559 effect on network operations. 2561 SNMPv1 by itself is such an insecure environment. Even if the network 2562 itself is secure (for example by using IPSec [24]), even then, there is 2563 no control as to who on the secure network is allowed to access and SET 2564 (change/create/delete) the objects in this MIB. 2566 It is recommended that the implementers consider the security features 2567 as provided by the SNMPv3 framework. Specifically, the use of the 2568 User-based Security Model RFC 2574 [12] and the View-based Access 2569 Control Model RFC 2575 [15] is recommended. 2571 It is then a customer/user responsibility to ensure that the SNMP entity 2572 giving access to this MIB, is properly configured to give access to 2573 those objects only to those principals (users) that have legitimate 2574 rights to access them. 2576 6.0 Acknowledgements 2578 Special thanks go to John Shriver (Shiva) for providing continued 2579 feedback 2580 throughout the development of this MIB. 2582 7.0 Authors' Addresses 2584 Evan Caves 2585 Ericsson 2586 340 Storke Road 2587 Santa Barbara, CA 93117 2588 evan@acc.com 2590 Pat Calhoun 2591 Sun MicroComputer Corp. 2592 15 Network Circle 2593 Menlo Park, CA, 94025 2594 Pat.Calhoun@Eng.Sun.Com 2595 Ross Wheeler 2596 RouterWare 2597 3961 MacArthur Blvd, Suite 212 2598 Newport Beach, CA 92660 2599 ross@routerware.com 2601 8.0 References 2603 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2604 Describing SNMP Management Frameworks", RFC 2271, Cabletron 2605 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 2606 January 1998 2608 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 2609 Management Information for TCP/IP-based Internets", RFC 1155, 2610 Performance Systems International, Hughes LAN Systems, May 1990 2612 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 2613 1212, 2614 Performance Systems International, Hughes LAN Systems, March 2615 1991 2617 [4] M. Rose, "A Convention for Defining Traps for use with the 2618 SNMP", 2619 RFC 1215, Performance Systems International, March 1991 2621 [5] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of 2622 Management Information Version 2 (SMIv2)", STD 58, RFC 2578, 2623 April 2624 1999. 2626 [6] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual 2627 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 2629 [7] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance 2630 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2632 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2633 Network 2634 Management Protocol", RFC 1157, SNMP Research, Performance 2635 Systems 2636 International, Performance Systems International, MIT Laboratory 2637 for Computer Science, May 1990. 2639 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2640 Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 2641 SNMP Research, Inc., Cisco Systems, Inc., Dover Beach 2642 Consulting, 2643 Inc., International Network Services, January 1996. 2645 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2646 Waldbusser, "Transport Mappings for Version 2 of the Simple 2647 Network 2648 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., 2649 Cisco 2650 Systems, Inc., Dover Beach Consulting, Inc., International 2651 Network 2652 Services, January 1996. 2654 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2655 Processing and Dispatching for the Simple Network Management 2656 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron 2657 Systems, 2658 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 2660 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 2661 for 2662 version 3 of the Simple Network Management Protocol (SNMPv3)", 2663 RFC 2664 2574, IBM T. J. Watson Research, April 1999. 2666 [13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2667 Waldbusser, "Protocol Operations for Version 2 of the Simple 2668 Network Management Protocol (SNMPv2)", RFC 1905, SNMP Research, 2669 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2670 International Network Services, January 1996. 2672 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2673 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 2674 Systems, April 1999. 2676 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2677 Control Model (VACM) for the Simple Network Management Protocol 2678 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, 2679 Inc., 2680 Cisco Systems, Inc., April 1999. 2682 [16] Valencia et al., "Layer Two Tunneling Protocol - L2TP", 2683 Work In Progress, Cisco Systems, Ascend Communications, 2684 Microsoft 2685 Corporation, Redback Networks, June 1999. 2687 [17] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", 2688 Work In Progress, Cisco Systems, Argon Networks, 2689 July 1998. 2691 [18] Thaler, D., "IP Tunnel MIB" , Work In Progress, Microsoft, June 2692 1999. 2694 9.0 Full Copyright Statement 2696 Copyright (C) The Internet Society (1999). All Rights Reserved. 2698 This document and translations of it may be copied and furnished to 2699 others, and derivative works that comment on or otherwise explain it 2700 or assist in its implmentation may be prepared, copied, published and 2701 distributed, in whole or in part, without restriction of any kind, 2702 provided that the above copyright notice and this paragraph are 2703 included on all such copies and derivative works. However, this 2704 document itself may not be modified in any way, such as by removing 2705 the copyright notice or references to the Internet Society or other 2706 Internet organizations, except as needed for the purpose of 2707 developing Internet standards in which case the procedures for 2708 copyrights defined in the Internet Standards process must be 2709 followed, or as required to translate it into languages other than 2710 English. 2712 The limited permissions granted above are perpetual and will not be 2713 revoked by the Internet Society or its successors or assigns. 2715 This document and the information contained herein is provided on an 2716 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2717 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2718 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2719 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2720 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."