idnits 2.17.1 draft-zorn-dime-diameter-base-protocol-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(i) Publication Limitation clause. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The 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 1730: '... this category MUST be routed to a...' RFC 2119 keyword, line 1734: '... category MUST be routed to a n...' RFC 2119 keyword, line 1737: '... category MUST have the identit...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year ** The document contains RFC2119-like boilerplate, but doesn't seem to mention RFC 2119. The boilerplate contains a reference [RFC1215], but that reference does not seem to mention RFC 2119 either. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 6, 2009) is 5501 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC4001' is mentioned on line 117, but not defined == Missing Reference: 'RFC3411' is mentioned on line 128, but not defined ** Obsolete normative reference: RFC 3588 (Obsoleted by RFC 6733) -- Obsolete informational reference (is this intentional?): RFC 4005 (Obsoleted by RFC 7155) -- Obsolete informational reference (is this intentional?): RFC 4006 (Obsoleted by RFC 8506) Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn 3 Internet-Draft Network Zen 4 Intended status: Informational S. Comerica 5 Expires: September 7, 2009 Cisco Systems 6 March 6, 2009 8 Diameter Base Protocol MIB 9 draft-zorn-dime-diameter-base-protocol-mib-05.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. This document may not be modified, 15 and derivative works of it may not be created, except to format it 16 for publication as an RFC or to translate it into languages other 17 than English. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on September 7, 2009. 37 Copyright Notice 39 Copyright (c) 2009 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents in effect on the date of 44 publication of this document (http://trustee.ietf.org/license-info). 45 Please review these documents carefully, as they describe your rights 46 and restrictions with respect to this document. 48 Abstract 50 Along with providing support for certain basic authentication, 51 authorization and accounting functions, the Diameter protocol is 52 designed to provide a framework for AAA applications. 54 This document defines the Management Information Base (MIB) module 55 which describes the minimum set of objects needed to manage an 56 implementation of the Diameter protocol. 58 Table of Contents 60 1. The Internet-Standard Management Framework . . . . . . . . . . 3 61 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 62 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 4. Diameter Base Protocol MIB Definitions . . . . . . . . . . . . 3 64 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 65 6. Security Considerations . . . . . . . . . . . . . . . . . . . 49 66 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 50 67 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 50 68 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50 69 9.1. Normative References . . . . . . . . . . . . . . . . . . . 50 70 9.2. Informative References . . . . . . . . . . . . . . . . . . 50 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 51 73 1. The Internet-Standard Management Framework 75 For a detailed overview of the documents that describe the current 76 Internet-Standard Management Framework, please refer to section 7 of 77 RFC 3410 [RFC3410]. 79 Managed objects are accessed via a virtual information store, termed 80 the Management Information Base or MIB. MIB objects are generally 81 accessed through the Simple Network Management Protocol (SNMP). 82 Objects in the MIB are defined using the mechanisms defined in the 83 Structure of Management Information (SMI). This memo specifies a MIB 84 module that is compliant to the SMIv2, which is described in STD 58, 85 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 86 [RFC2580]. In particular, it describes managed objects used for 87 managing the base Diameter protocol. 89 Discussion of this draft may be directed to the authors. 91 2. Requirements Language 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 95 document are to be interpreted as described in [RFC1215]. 97 3. Overview 99 The base Diameter protocol [RFC3588] is never used alone; it is 100 always extended for a particular application. Four standard Diameter 101 applications have been defined to date: NASREQ [RFC4005], Mobile IP 102 [RFC4004] [RFC3141], Credit Control [RFC4006] and EAP [RFC4072]; 103 others may be defined in the future. 105 This MIB defines objects supporting the management of the Diameter 106 base protocol as described in [RFC3588]. Objects related to the 107 applications mentioned above (and any additional applications created 108 in the future) will be defined in separate documents. 110 4. Diameter Base Protocol MIB Definitions 112 DIAMETER-BASE-PROTOCOL-MIB DEFINITIONS ::= BEGIN 114 IMPORTS 115 InetAddressType, 116 InetAddress 117 FROM INET-ADDRESS-MIB -- [RFC4001] 119 MODULE-IDENTITY, 120 OBJECT-TYPE, 121 NOTIFICATION-TYPE, 122 Counter32, 123 Unsigned32, 124 Gauge32, 125 TimeTicks 126 FROM SNMPv2-SMI -- [RFC2578] 127 SnmpAdminString 128 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 129 NOTIFICATION-GROUP, 130 MODULE-COMPLIANCE, 131 OBJECT-GROUP 132 FROM SNMPv2-CONF -- [RFC2580] 133 RowStatus, 134 TruthValue, 135 StorageType 136 FROM SNMPv2-TC; -- [RFC2579] 138 DiameterBasePMIB MODULE-IDENTITY 139 LAST-UPDATED "200903060000Z" -- 06 March 2009 140 ORGANIZATION "IETF dime Working Group." 141 CONTACT-INFO 142 "Glen Zorn 143 Network Zen 144 1310 East Thomas Street 145 Seattle, WA 98102 146 USA 147 Phone: +1 (206) 377 9035 148 Email: gwz@net-zen.net" 149 DESCRIPTION 150 "The MIB module for entities implementing the 151 Diameter Base Protocol. 153 Copyright (C) The IETF Trust (2009). This initial 154 version of this MIB module was published in RFC yyyy; 155 for full legal notices see the RFC itself. Supplementary 156 information may be available on 157 http://www.ietf.org/copyrights/ianamib.html." 159 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 161 REVISION "200903060000Z" -- 06 March 2009 162 DESCRIPTION "Initial version as published in RFC yyyy" 163 -- RFC Ed.: replace yyyy with actual RFC number and remove this note 164 ::= { mib-2 119 } -- Experimental value assigned by IANA. 166 -- Top-Level Components of this MIB. 167 diameterBaseProtocolMIB OBJECT::= { diameterMIB 1 } 168 diameterBaseNotifications OBJECT IDENTIFIER ::= 169 { diameterBaseProtocolMIB 0 } 170 diameterBaseObjects OBJECT IDENTIFIER ::= 171 { diameterBaseProtocolMIB 1 } 172 diameterBaseConform OBJECT IDENTIFIER ::= 173 { diameterBaseProtocolMIB 2 } 175 dbpLocalCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 1 } 176 dbpLocalStats OBJECT IDENTIFIER ::= { diameterBaseObjects 2 } 177 dbpPeerCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 3 } 178 dbpPeerStats OBJECT IDENTIFIER ::= { diameterBaseObjects 4 } 179 dbpRealmCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 5 } 180 dbpRealmStats OBJECT IDENTIFIER ::= { diameterBaseObjects 6 } 181 dbpNotifCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 7 } 183 -- Protocol Error Notifications 185 dbpProtocolErrorNotifEnabled OBJECT-TYPE 186 SYNTAX TruthValue 187 MAX-ACCESS read-write 188 STATUS current 189 DESCRIPTION 190 "Setting the value of this object to True(1) 191 enables the dbpProtocolErrorNotif notification." 192 DEFVAL {false} 193 ::= { dbpNotifCfgs 1 } 195 dbpProtocolErrorNotif NOTIFICATION-TYPE 196 OBJECTS { 197 dbpPeerId, 198 dbpPerPeerStatsProtocolErrors 199 } 200 STATUS current 201 DESCRIPTION 202 "An dbpProtocolError Notification is sent when both the 203 following conditions are true: 204 1) the value of dbpProtocolErrorNotifEnabled is True(1) 205 2) the value of dbpPerPeerStatsProtocolErrors changes 206 It can be utilized by an NMS to trigger 207 logical/physical entity table maintenance polls. 208 An agent must not generate more than one 209 dbpProtocolError 'notification event' in a five second 210 period, where a 'notification event' is the 211 transmission of a single Notification PDU to a list of 212 Notification destinations. 214 If additional protocol errors occur within the 215 five second 'throttling' period, then these 216 notification events should be suppressed by the agent. 217 An NMS should periodically check the value of 218 dbpPerPeerStatsProtocolErrors to detect any missed 219 dbpProtocolError notification events, e.g. due to 220 throttling or transmission loss." 221 ::= { diameterBaseNotifications 1 } 223 -- Transient Error Notifications 225 dbpTransientFailureNotifEnabled OBJECT-TYPE 226 SYNTAX TruthValue 227 MAX-ACCESS read-write 228 STATUS current 229 DESCRIPTION 230 "Setting the value of this object to True(1) 231 enables the dbpTransientFailure Notification." 232 ::= { dbpNotifCfgs 2 } 234 dbpTransientFailureNotif NOTIFICATION-TYPE 235 OBJECTS { 236 dbpPeerId, 237 dbpPerPeerStatsTransientFailures 238 } 239 STATUS current 240 DESCRIPTION 241 "An dbpTransientFailure Notification is sent when both 242 the following conditions are true: 243 1) the value of dbpTransientFailureNotifEnabled 244 is True(1) 245 2) the value of dbpPerPeerStatsTransientFailures 246 changes 247 It can be utilized by an NMS to trigger 248 logical/physical entity table maintenance polls. 249 An agent must not generate more than one 250 dbpTransientFailure 'notification event' in a five 251 second period, where a 'notification event' is the 252 transmission of a single notification PDU to a list 253 of notification destinations. 254 If additional transient failures occur 255 within the five second 'throttling' period, then 256 these notification events should be suppressed 257 by the agent. 258 An NMS should periodically check the value of 259 dbpPerPeerStatsTransientFailures to detect any 260 missed dbpTransientFailure notification events, 261 e.g. due to throttling or transmission loss." 262 ::= { diameterBaseNotifications 2 } 264 -- Permanent Failure Notifications 266 dbpPermanentFailureNotifEnabled OBJECT-TYPE 267 SYNTAX TruthValue 268 MAX-ACCESS read-write 269 STATUS current 270 DESCRIPTION 271 "Setting the value of this object to True(1) 272 enables the dbpPermanentFailure notification." 273 DEFVALUE { false } 274 ::= { dbpNotifCfgs 3 } 276 dbpPermanentFailureNotif NOTIFICATION-TYPE 277 OBJECTS { 278 dbpPeerId, 279 dbpPerPeerStatsPermanentFailures 280 } 281 STATUS current 282 DESCRIPTION 283 "An dbpPermanentFailure notification is sent when 284 both the following conditions are true: 285 1) the value of dbpPermanentFailureNotifEnabled 286 is True(1) 287 2) the value of dbpPerPeerStatsPermanentFailures 288 changes 289 It can be utilized by an NMS to trigger 290 logical/physical entity table maintenance polls. 291 An agent must not generate more than one 292 dbpPermanentFailure 'notification event' in a five 293 second period, where a 'notification event' is the 294 transmission of a single notification PDU to a list 295 of notification destinations. 296 If additional permanent failures occur within the 297 five second 'throttling' period, then these 298 trap-events should be suppressed by the agent. 299 An NMS should periodically check the value of 300 dbpPerPeerStatsPermanentFailures to detect 301 any missed dbpPermanentFailure trap-events, 302 e.g. due to throttling or transmission loss." 303 ::= { diameterBaseNotifications 3 } 305 -- Connection Down Notifs 306 dbpPeerConnectionDownNotifEnabled OBJECT-TYPE 307 SYNTAX TruthValue 308 MAX-ACCESS read-write 309 STATUS current 310 DESCRIPTION 311 "Setting the value of this object to True(1) 312 enables the dbpPeerConnectionDown notification." 313 DEFVAL { false } 314 ::= { dbpNotifCfgs 4 } 316 dbpPeerConnectionDownNotif NOTIFICATION-TYPE 317 OBJECTS { 318 dbpLocalId, 319 dbpPeerId 320 } 321 STATUS current 322 DESCRIPTION 323 "An dbpPeerConnectionDown notification is sent when 324 both the following conditions are true: 325 1) the value of dbpPeerConnectionDownNotifEnabled is 326 True(1) 327 2) dbpPerPeerStatsState changes to closed(1) 328 It can be utilized by an NMS to trigger 329 logical/physical 330 entity table maintenance polls. An agent must not 331 generate more than one dbpPeerConnectionDown 332 'notification event' in a five second period, where a 333 'notification event' is the transmission of a single 334 notification PDU to a list of notification 335 destinations. 336 If additional 'transport down' events occur within the 337 five second 'throttling' period, then these trap-events 338 should be suppressed by the agent." 339 ::= { diameterBaseNotifications 4 } 341 -- Connection Up Notifications 343 dbpPeerConnectionUpNotifEnabled OBJECT-TYPE 344 SYNTAX TruthValue 345 MAX-ACCESS read-write 346 STATUS current 347 DESCRIPTION 348 "Setting the value of this object to True(1) 349 enables the dbpPeerConnectionUp notification." 350 DEFVAL { false } 351 ::= { dbpNotifCfgs 5 } 353 dbpPeerConnectionUpNotif NOTIFICATION-TYPE 354 OBJECTS { 355 dbpLocalId, 356 dbpPeerId 357 } 358 STATUS current 359 DESCRIPTION 360 "An dbpPeerConnectionUp notification is sent 361 when both thefollowing conditions are true: 362 1) the value of dbpPeerConnectionUpNotifEnabled is 363 True(1) 364 2) the value of dbpPerPeerStatsState changes to 365 either rOpen(6)or iOpen(7) 366 It can be utilized by an NMS to trigger 367 logical/physical entity table maintenance polls. 368 An agent must not generate 369 more than one dbpPeerConnectionUp 370 'notification event' in a 371 five second period, where a 'notification event' is the 372 transmission of a single notification PDU to a 373 list of notification destinations. 374 If additional 'connection up' events 375 occur within the five second 'throttling' period, 376 then these trap-events should be suppressed by the 377 agent." 378 ::= { diameterBaseNotifications 5 } 380 -- Local Configs 382 dbpLocalId OBJECT-TYPE 383 SYNTAX SnmpAdminString 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The implementation-specific identification 388 string for the Diameter software in use on 389 the system; for example: 'diameterd'" 390 ::= { dbpLocalCfgs 1 } 392 dbpLocalIpAddrTable OBJECT-TYPE 393 SYNTAX SEQUENCE OF DbpLocalIpAddrEntry 394 MAX-ACCESS not-accessible 395 STATUS current 396 DESCRIPTION 397 "The table listing the Diameter 398 local host's IP Addresses." 399 ::= { dbpLocalCfgs 2 } 401 dbpLocalIpAddrEntry OBJECT-TYPE 402 SYNTAX DbpLocalIpAddrEntry 403 MAX-ACCESS not-accessible 404 STATUS current 405 DESCRIPTION 406 "A row entry representing a Diameter 407 local host IP Address." 408 INDEX { dbpLocalIpAddrIndex } 409 ::= { dbpLocalIpAddrTable 1 } 411 DbpLocalIpAddrEntry ::= SEQUENCE { 412 dbpLocalIpAddrIndex Unsigned32, 413 dbpLocalIpAddrType InetAddressType, 414 dbpLocalIpAddress InetAddress 415 } 417 dbpLocalIpAddrIndex OBJECT-TYPE 418 SYNTAX Unsigned32 (1..4294967295 ) 419 MAX-ACCESS not-accessible 420 STATUS current 421 DESCRIPTION 422 "A number uniquely identifying an IP Address 423 supported by this Diameter host." 424 ::= { dbpLocalIpAddrEntry 1 } 426 dbpLocalIpAddrType OBJECT-TYPE 427 SYNTAX InetAddressType 428 MAX-ACCESS read-only 429 STATUS current 430 DESCRIPTION 431 "The type of internet address stored 432 in dbpLocalIpAddress." 433 ::= { dbpLocalIpAddrEntry 2 } 435 dbpLocalIpAddress OBJECT-TYPE 436 SYNTAX InetAddress 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "The IP-Address of the host, which is of the type 441 specified in dbpLocalIpAddrType." 442 ::= { dbpLocalIpAddrEntry 3 } 444 dbpLocalTcpListenPort OBJECT-TYPE 445 SYNTAX Unsigned32 (1..65535) 446 MAX-ACCESS read-only 447 STATUS current 448 DESCRIPTION 449 "Diameter TCP 'listen' port." 450 ::= { dbpLocalCfgs 3 } 452 dbpLocalSctpListenPort OBJECT-TYPE 453 SYNTAX Unsigned32 (1..65535) 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "Diameter SCTP 'listen' port." 458 ::= { dbpLocalCfgs 4 } 460 dbpLocalOriginHost OBJECT-TYPE 461 SYNTAX SnmpAdminString 462 MAX-ACCESS read-write 463 STATUS current 464 DESCRIPTION "This object represents the Local Origin Host." 465 DEFVAL { "" } 466 ::= { dbpLocalCfgs 5 } 468 dbpLocalRealm OBJECT-TYPE 469 SYNTAX SnmpAdminString 470 MAX-ACCESS read-only 471 STATUS current 472 DESCRIPTION "This object represents the Local Realm Name." 473 DEFVAL { "" } 474 ::= { dbpLocalCfgs 6 } 476 dbpLocalStatsTotalMessagesIn OBJECT-TYPE 477 SYNTAX Counter32 478 MAX-ACCESS read-only 479 STATUS current 480 DESCRIPTION 481 "The total number of Diameter Base Protocol 482 messages received." 483 ::= { dbpLocalStats 1 } 485 dbpLocalStatsTotalMessagesOut OBJECT-TYPE 486 SYNTAX Counter32 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION 490 "The total number of Diameter Base Protocol 491 messages transmitted." 492 ::= { dbpLocalStats 2 } 494 dbpLocalStatsTotalUpTime OBJECT-TYPE 495 SYNTAX TimeTicks 496 MAX-ACCESS read-only 497 STATUS current 498 DESCRIPTION 499 "This object represents the total time this Diameter 500 server has been up until now." 501 ::= { dbpLocalStats 3 } 503 dbpLocalResetTime OBJECT-TYPE 504 SYNTAX TimeTicks 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "If the server keeps persistent state (e.g., a process) 509 and supports a 'reset' operation (e.g., can be told to 510 re-read configuration files), this value will be the 511 time elapsed (in hundredths of a second) since the 512 server was 'reset'. For software that does not 513 have persistence or does not support a 'reset' 514 operation, this value will be zero." 515 ::= { dbpLocalStats 4 } 517 dbpLocalConfigReset OBJECT-TYPE 518 SYNTAX INTEGER { other(1), 519 initializing(2), 520 running(3) } 521 MAX-ACCESS read-write 522 STATUS current 523 DESCRIPTION 524 "Status/action object to reinitialize any persistent 525 server state. When set to reset(2), any persistent 526 server state (such as a process) is reinitialized as 527 if the server had just been started. This value will 528 never be returned by a read operation. When read, 529 one of the following values will be returned: 530 other(1) - server in some unknown state; 531 initializing(2) - server (re)initializing; 532 running(3) - server currently running." 533 DEFVAL { other } 534 ::= { dbpLocalStats 5 } 536 dbpLocalApplTable OBJECT-TYPE 537 SYNTAX SEQUENCE OF DbpLocalApplEntry 538 MAX-ACCESS not-accessible 539 STATUS current 540 DESCRIPTION 541 "The table listing the Diameter applications 542 supported by this server." 543 ::= { dbpLocalCfgs 7 } 545 dbpLocalApplEntry OBJECT-TYPE 546 SYNTAX DbpLocalApplEntry 547 MAX-ACCESS not-accessible 548 STATUS current 549 DESCRIPTION 550 "A row entry representing a Diameter 551 application on this server." 552 INDEX { dbpLocalApplIndex } 553 ::= { dbpLocalApplTable 1 } 555 DbpLocalApplEntry ::= SEQUENCE { 556 dbpLocalApplIndex Unsigned32, 557 dbpLocalApplStorageType StorageType, 558 dbpLocalApplRowStatus RowStatus 559 } 561 dbpLocalApplIndex OBJECT-TYPE 562 SYNTAX Unsigned32 ( 1..4294967295 ) 563 MAX-ACCESS not-accessible 564 STATUS current 565 DESCRIPTION 566 "A number uniquely identifying a 567 supported Diameter application. Upon reload, 568 dbpLocalApplIndex values may be changed." 569 ::= { dbpLocalApplEntry 1 } 571 dbpLocalApplStorageType OBJECT-TYPE 572 SYNTAX StorageType 573 MAX-ACCESS read-create 574 STATUS current 575 DESCRIPTION 576 "The storage type for this conceptual row. None of 577 the columnar objects is writable when the conceptual 578 row is permanent." 579 REFERENCE "Textual Conventions for SMIv2, Section 2." 580 DEFVAL { nonVolatile } 581 ::= { dbpLocalApplEntry 2 } 583 dbpLocalApplRowStatus OBJECT-TYPE 584 SYNTAX RowStatus 585 MAX-ACCESS read-create 586 STATUS current 587 DESCRIPTION 588 "The status of this conceptual row. 590 To create a row in this table, a manager must 591 set this object to either createAndGo(4) or 592 createAndWait(5). 594 Until instances of all corresponding columns are 595 appropriately configured, the value of the 596 corresponding instance of the dbpLocalApplRowStatus 597 column is 'notReady'. 599 In particular, a newly created row cannot be made 600 active until the corresponding dbpLocalApplIndex 601 has been set. 603 dbpLocalApplIndex may not be modified while 604 the value of this object is active(1): An attempt 605 to set these objects while the value of 606 dbpLocalApplRowStatus is active(1) will result in 607 an inconsistentValue error. 609 Entries in this table with dbpLocalApplRowStatus equal 610 to active(1) remain in the table until destroyed. 612 Entries in this table with dbpLocalApplRowStatus equal 613 to values other than active(1) will be destroyed after 614 timeout (5 minutes)." 615 ::= { dbpLocalApplEntry 3 } 617 dbpPeerTable OBJECT-TYPE 618 SYNTAX SEQUENCE OF DbpPeerEntry 619 MAX-ACCESS not-accessible 620 STATUS current 621 DESCRIPTION 622 "The table listing information regarding 623 the discovered or configured Diameter 624 peer servers." 625 ::= { dbpPeerCfgs 1 } 627 dbpPeerEntry OBJECT-TYPE 628 SYNTAX DbpPeerEntry 629 MAX-ACCESS not-accessible 630 STATUS current 631 DESCRIPTION 632 "A row entry representing a discovered 633 or configured Diameter peer server." 634 INDEX { dbpPeerIndex } 635 ::= { dbpPeerTable 1 } 637 DbpPeerEntry ::= SEQUENCE { 638 dbpPeerIndex Unsigned32, 639 dbpPeerId SnmpAdminString, 640 dbpPeerPortConnect Unsigned32, 641 dbpPeerPortListen Unsigned32, 642 dbpPeerProtocol INTEGER, 643 dbpPeerSecurity INTEGER, 644 dbpPeerFirmwareRevision Unsigned32, 645 dbpPeerStorageType StorageType, 646 dbpPeerRowStatus RowStatus } 648 dbpPeerIndex OBJECT-TYPE 649 SYNTAX Unsigned32 (1..4294967295) 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "A number uniquely identifying each Diameter peer 654 with which the host server communicates. 655 Upon reload, dbpPeerIndex values may be changed." 656 ::= { dbpPeerEntry 1 } 658 dbpPeerId OBJECT-TYPE 659 SYNTAX SnmpAdminString 660 MAX-ACCESS read-create 661 STATUS current 662 DESCRIPTION 663 "The server identifier for the Diameter peer. 664 It must be unique and non-empty." 665 ::= { dbpPeerEntry 2 } 667 dbpPeerPortConnect OBJECT-TYPE 668 SYNTAX Unsigned32 (1..65535) 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "The connection port this server used 673 to connect to the Diameter peer. 674 If there is no active connection, this 675 value will be zero(0)." 676 ::= { dbpPeerEntry 3 } 678 dbpPeerPortListen OBJECT-TYPE 679 SYNTAX Unsigned32 (1..65535) 680 MAX-ACCESS read-only 681 STATUS current 682 DESCRIPTION 683 "The port the server is listening on." 684 ::= { dbpPeerEntry 4 } 686 dbpPeerProtocol OBJECT-TYPE 687 SYNTAX INTEGER { tcp(1), 688 sctp(2) } 689 MAX-ACCESS read-only 690 STATUS current 691 DESCRIPTION 692 "The transport protocol (tcp/sctp) the 693 Diameter peer is using." 694 ::= { dbpPeerEntry 5 } 696 dbpPeerSecurity OBJECT-TYPE 697 SYNTAX INTEGER { other(1), 698 tls(2), 699 ipsec(3) } 700 MAX-ACCESS read-only 701 STATUS current 702 DESCRIPTION 703 "The security the Diameter peer is using. 705 other(1) - Unknown Security Protocol 706 tls(2) - Transport Layer Security Protocol 707 ipsec(3) - Internet Protocol Security" 708 DEFVAL { other } 709 ::= { dbpPeerEntry 6 } 711 dbpPeerFirmwareRevision OBJECT-TYPE 712 SYNTAX Unsigned32 (1..4294967295) 713 MAX-ACCESS read-only 714 STATUS current 715 DESCRIPTION 716 "Firmware revision of peer. If no firmware 717 revision, the revision of the Diameter software 718 module may be reported instead." 719 ::= { dbpPeerEntry 7 } 721 dbpPeerStorageType OBJECT-TYPE 722 SYNTAX StorageType 723 MAX-ACCESS read-create 724 STATUS current 725 DESCRIPTION 726 "The storage type for this conceptual row. 727 Only the dbpPeerPortListen object is writable when 728 the conceptual row is permanent." 729 REFERENCE "Textual Conventions for SMIv2, Section 2." 730 DEFVAL { nonVolatile } 731 ::= { dbpPeerEntry 8 } 733 dbpPeerRowStatus OBJECT-TYPE 734 SYNTAX RowStatus 735 MAX-ACCESS read-create 736 STATUS current 737 DESCRIPTION 738 "Status of the peer entry: creating the entry 739 enables the peer, destroying the entry disables 740 the peer." 741 ::= {dbpPeerEntry 9 } 743 dbpPeerIpAddrTable OBJECT-TYPE 744 SYNTAX SEQUENCE OF DbpPeerIpAddrEntry 745 MAX-ACCESS not-accessible 746 STATUS current 747 DESCRIPTION 748 "The table listing the Diameter 749 peer IP addresses." 750 ::= { dbpPeerCfgs 2 } 752 dbpPeerIpAddrEntry OBJECT-TYPE 753 SYNTAX DbpPeerIpAddrEntry 754 MAX-ACCESS not-accessible 755 STATUS current 756 DESCRIPTION 757 "A row entry representing a 758 peer Diameter server." 759 INDEX { 760 dbpPeerIndex, 761 dbpPeerIpAddressIndex } 762 ::= { dbpPeerIpAddrTable 1 } 764 DbpPeerIpAddrEntry ::= SEQUENCE { 765 dbpPeerIpAddressIndex Unsigned32, 766 dbpPeerIpAddressType InetAddressType, 767 dbpPeerIpAddress InetAddress } 769 dbpPeerIpAddressIndex OBJECT-TYPE 770 SYNTAX Unsigned32 (1..4294967295) 771 MAX-ACCESS not-accessible 772 STATUS current 773 DESCRIPTION 774 "A number uniquely identifying an IP Address 775 supported by this Diameter peer." 776 ::= { dbpPeerIpAddrEntry 1 } 778 dbpPeerIpAddressType OBJECT-TYPE 779 SYNTAX InetAddressType 780 MAX-ACCESS read-only 781 STATUS current 782 DESCRIPTION 783 "The type of address stored in dbpPeerIpAddress." 784 ::= {dbpPeerIpAddrEntry 2} 786 dbpPeerIpAddress OBJECT-TYPE 787 SYNTAX InetAddress 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "The active IP Address(es) used for connections." 792 ::= {dbpPeerIpAddrEntry 3} 794 dbpAppAdvToPeerTable OBJECT-TYPE 795 SYNTAX SEQUENCE OF DbpAppAdvToPeerEntry 796 MAX-ACCESS not-accessible 797 STATUS current 798 DESCRIPTION 799 "The table listing the applications advertised by 800 this host to each peer and the types of service 801 supported: accounting, authentication or both." 802 ::= { dbpLocalCfgs 8 } 804 dbpAppAdvToPeerEntry OBJECT-TYPE 805 SYNTAX DbpAppAdvToPeerEntry 806 MAX-ACCESS not-accessible 807 STATUS current 808 DESCRIPTION 809 "A row entry representing a discovered or 810 configured Diameter peer server." 811 INDEX { dbpPeerIndex, 812 dbpAppAdvToPeerVendorId, 813 dbpAppAdvToPeerIndex } 814 ::= { dbpAppAdvToPeerTable 1 } 816 DbpAppAdvToPeerEntry ::= SEQUENCE { 817 dbpAppAdvToPeerVendorId Unsigned32, 818 dbpAppAdvToPeerIndex Unsigned32, 819 dbpAppAdvToPeerServices INTEGER, 820 dbpAppAppAdvToPeerStorageType StorageType, 821 dbpAppAdvToPeerRowStatus RowStatus } 823 dbpAppAdvToPeerVendorId OBJECT-TYPE 824 SYNTAX Unsigned32 ( 1..4294967295 ) 825 MAX-ACCESS not-accessible 826 STATUS current 827 DESCRIPTION 828 "The IANA Enterprise Code value assigned to 829 the vendor of the Diameter device." 830 ::= { dbpAppAdvToPeerEntry 1 } 832 dbpAppAdvToPeerIndex OBJECT-TYPE 833 SYNTAX Unsigned32 ( 1..4294967295 ) 834 MAX-ACCESS not-accessible 835 STATUS current 836 DESCRIPTION 837 "A number uniquely identifying a Diameter 838 application advertised as supported by 839 this host to each peer. Upon reload, 840 dbpAppAdvToPeerIndex values may be 841 changed" 842 ::= { dbpAppAdvToPeerEntry 2 } 844 dbpAppAdvToPeerServices OBJECT-TYPE 845 SYNTAX INTEGER { acct(1), 846 auth(2), 847 both(3) } 848 MAX-ACCESS read-only 849 STATUS current 850 DESCRIPTION 851 "The type of services supported for each application, 852 accounting, authentication or both." 853 ::= { dbpAppAdvToPeerEntry 3 } 855 dbpAppAdvToPeerStorageType OBJECT-TYPE 856 SYNTAX StorageType 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "The storage type for this conceptual row. 861 None of the objects are writable when the 862 conceptual row is permanent." 863 REFERENCE "Textual Conventions for SMIv2, Section 2." 864 DEFVAL { nonVolatile } 865 ::= { dbpAppAdvToPeerEntry 4 } 867 dbpAppAdvToPeerRowStatus OBJECT-TYPE 868 SYNTAX RowStatus 869 MAX-ACCESS read-create 870 STATUS current 871 DESCRIPTION 872 "Status of the entry: creating the entry causes the 873 application to be advertised, destroying the entry 874 ceases advertisement." 875 ::= { dbpAppAdvToPeerEntry 5 } 877 -- Applications advertised BY peers 879 dbpAppAdvFromPeerTable OBJECT-TYPE 880 SYNTAX SEQUENCE OF DbpAppAdvFromPeerEntry 881 MAX-ACCESS not-accessible 882 STATUS current 883 DESCRIPTION 884 "The table listing the applications advertised by 885 each peer to this host and the types of service 886 supported: accounting, authentication or both." 887 ::= { dbpPeerCfgs 3 } 889 dbpAppAdvFromPeerEntry OBJECT-TYPE 890 SYNTAX DbpAppAdvFromPeerEntry 891 MAX-ACCESS not-accessible 892 STATUS current 893 DESCRIPTION 894 "A row entry representing a discovered or 895 configured Diameter peer server." 896 INDEX { 897 dbpPeerIndex, 898 dbpAppAdvFromPeerVendorId, 899 dbpAppAdvFromPeerIndex 900 } 901 ::= { dbpAppAdvFromPeerTable 1 } 903 DbpAppAdvFromPeerEntry ::= SEQUENCE { 904 dbpAppAdvFromPeerVendorId Unsigned32, 905 dbpAppAdvFromPeerIndex Unsigned32, 906 dbpAppAdvFromPeerType INTEGER 907 } 909 dbpAppAdvFromPeerVendorId OBJECT-TYPE 910 SYNTAX Unsigned32 (1..4294967295 ) 911 MAX-ACCESS not-accessible 912 STATUS current 913 DESCRIPTION 914 "The IANA Enterprise Code value assigned to 915 the vendor of the Diameter application." 916 ::= { dbpAppAdvFromPeerEntry 1 } 918 dbpAppAdvFromPeerIndex OBJECT-TYPE 919 SYNTAX Unsigned32 (1..4294967295 ) 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "A number uniquely identifying the applications 924 advertised as supported from each Diameter peer." 925 ::= { dbpAppAdvFromPeerEntry 2 } 927 dbpAppAdvFromPeerType OBJECT-TYPE 928 SYNTAX INTEGER { 929 acct(1), 930 auth(2), 931 both(3) 932 } 933 MAX-ACCESS read-only 934 STATUS current 935 DESCRIPTION 936 "The type of services supported for each application, 937 accounting, authentication or both. 938 acct(1) - accounting 939 auth(2) - authentication 940 both(3) - both accounting and authentication." 941 ::= { dbpAppAdvFromPeerEntry 3 } 943 -- table of vendor-IDs supported by each peer 945 dbpPeerVendorTable OBJECT-TYPE 946 SYNTAX SEQUENCE OF DbpPeerVendorEntry 947 MAX-ACCESS not-accessible 948 STATUS current 949 DESCRIPTION 950 "The table listing the Vendor IDs 951 supported by the peer." 952 ::= { dbpPeerCfgs 4 } 954 dbpPeerVendorEntry OBJECT-TYPE 955 SYNTAX DbpPeerVendorEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "A row entry representing a 960 Vendor ID supported by the peer." 961 INDEX { 962 dbpPeerIndex, 963 dbpPeerVendorIndex 964 } 965 ::= { dbpPeerVendorTable 1 } 967 DbpPeerVendorEntry ::= SEQUENCE { 968 dbpPeerVendorIndex Unsigned32, 969 dbpPeerVendorId INTEGER , 970 dbpPeerVendorStorageType StorageType, 971 dbpPeerVendorRowStatus RowStatus 972 } 974 dbpPeerVendorIndex OBJECT-TYPE 975 SYNTAX Unsigned32 (1..4294967295 ) 976 MAX-ACCESS not-accessible 977 STATUS current 978 DESCRIPTION 979 "A number uniquely identifying the Vendor 980 ID supported by the peer. Upon reload, 981 dbpPeerVendorIndex values may be changed." 982 ::= { dbpPeerVendorEntry 1 } 984 dbpPeerVendorId OBJECT-TYPE 985 SYNTAX INTEGER { 986 diameterVendorIetf(0), 987 diameterVendorCisco(9), 988 diameterVendor3gpp(10415), 989 diameterVendorVodafone(12645) 990 } 991 MAX-ACCESS read-create 992 STATUS current 993 DESCRIPTION 994 "The active vendor ID used for peer connections. 995 diameterVendorIetf(0) -- IETF 996 diameterVendor3gpp(10415) - 3GPP 997 DEFVAL { diameterVendorIetf } 998 ::= { dbpPeerVendorEntry 2 } 1000 dbpPeerVendorStorageType OBJECT-TYPE 1001 SYNTAX StorageType 1002 MAX-ACCESS read-create 1003 STATUS current 1004 DESCRIPTION 1005 "The storage type for this conceptual row. 1006 None of the objects are writable when the 1007 conceptual row is permanent." 1008 REFERENCE "Textual Conventions for SMIv2, Section 2." 1009 DEFVAL { nonVolatile } 1010 ::= { dbpPeerVendorEntry 3 } 1012 dbpPeerVendorRowStatus OBJECT-TYPE 1013 SYNTAX RowStatus 1014 MAX-ACCESS read-create 1015 STATUS current 1016 DESCRIPTION 1017 "The status of this conceptual row. 1019 To create a row in this table, a manager must 1020 set this object to either createAndGo(4) or 1021 createAndWait(5). 1023 Until instances of all corresponding columns are 1024 appropriately configured, the value of the 1025 corresponding instance of the dbpPeerVendorRowStatus 1026 column is 'notReady'. 1028 In particular, a newly created row cannot be made 1029 active until the corresponding dbpPeerVendorId has been 1030 set. Also, a newly created row cannot be made active 1031 until the corresponding 'dbpPeerIndex' has been set. 1033 dbpPeerVendorId may not be modified while the 1034 value of this object is active(1): 1035 An attempt to set these objects while the value of 1036 dbpPeerVendorRowStatus is active(1) will result in 1037 an inconsistentValue error. 1039 Entries in this table with dbpPeerVendorRowStatus equal 1040 to active(1) remain in the table until destroyed. 1042 Entries in this table with dbpPeerVendorRowStatus equal 1043 to values other than active(1) will be destroyed after 1044 timeout (5 minutes)." 1045 ::= { dbpPeerVendorEntry 4 } 1047 dbpPerPeerStatsTable OBJECT-TYPE 1048 SYNTAX SEQUENCE OF DbpPerPeerStatsEntry 1049 MAX-ACCESS not-accessible 1050 STATUS current 1051 DESCRIPTION 1052 "The table listing the Diameter peer statistics." 1053 ::= { dbpPeerStats 1 } 1055 dbpPerPeerStatsEntry OBJECT-TYPE 1056 SYNTAX DbpPerPeerStatsEntry 1057 MAX-ACCESS not-accessible 1058 STATUS current 1059 DESCRIPTION 1060 "A row entry representing a Diameter peer." 1061 INDEX { dbpPeerIndex } 1062 ::= { dbpPerPeerStatsTable 1 } 1064 DbpPerPeerStatsEntry ::= SEQUENCE { 1065 dbpPerPeerStatsState INTEGER, 1066 dbpPerPeerStatsStateDuration TimeTicks, 1067 dbpPerPeerStatsLastDiscCause INTEGER, 1068 dbpPerPeerStatsWhoInitDisconnect INTEGER, 1069 dbpPerPeerStatsDWCurrentStatus INTEGER, 1070 dbpPerPeerStatsTimeoutConnAtmpts Counter32, 1071 dbpPerPeerStatsASRsIn Counter32, 1072 dbpPerPeerStatsASRsOut Counter32, 1073 dbpPerPeerStatsASAsIn Counter32, 1074 dbpPerPeerStatsASAsOut Counter32, 1075 dbpPerPeerStatsACRsIn Counter32, 1076 dbpPerPeerStatsACRsOut Counter32, 1077 dbpPerPeerStatsACAsIn Counter32, 1078 dbpPerPeerStatsACAsOut Counter32, 1079 dbpPerPeerStatsCERsIn Counter32, 1080 dbpPerPeerStatsCERsOut Counter32, 1081 dbpPerPeerStatsCEAsIn Counter32, 1082 dbpPerPeerStatsCEAsOut Counter32, 1083 dbpPerPeerStatsDWRsIn Counter32, 1084 dbpPerPeerStatsDWRsOut Counter32, 1085 dbpPerPeerStatsDWAsIn Counter32, 1086 dbpPerPeerStatsDWAsOut Counter32, 1087 dbpPerPeerStatsDPRsIn Counter32, 1088 dbpPerPeerStatsDPRsOut Counter32, 1089 dbpPerPeerStatsDPAsIn Counter32, 1090 dbpPerPeerStatsDPAsOut Counter32, 1091 dbpPerPeerStatsRARsIn Counter32, 1092 dbpPerPeerStatsRARsOut Counter32, 1093 dbpPerPeerStatsRAAsIn Counter32, 1094 dbpPerPeerStatsRAAsOut Counter32, 1095 dbpPerPeerStatsSTRsIn Counter32, 1096 dbpPerPeerStatsSTRsOut Counter32, 1097 dbpPerPeerStatsSTAsIn Counter32, 1098 dbpPerPeerStatsSTAsOut Counter32, 1099 dbpPerPeerStatsDWReqTimer TimeTicks, 1100 dbpPerPeerStatsRedirectEvents Counter32, 1101 dbpPerPeerStatsAccDupRequests Counter32, 1102 dbpPerPeerStatsMalformedReqsts Counter32, 1103 dbpPerPeerStatsAccsNotRecorded Counter32, 1104 dbpPerPeerStatsAccRetrans Counter32, 1105 dbpPerPeerStatsTotalRetrans Counter32, 1106 dbpPerPeerStatsAccPendReqstsOut Gauge32, 1107 dbpPerPeerStatsAccReqstsDropped Counter32, 1108 dbpPerPeerStatsHByHDropMessages Counter32, 1109 dbpPerPeerStatsEToEDupMessages Counter32, 1110 dbpPerPeerStatsUnknownTypes Counter32, 1111 dbpPerPeerStatsProtocolErrors Counter32, 1112 dbpPerPeerStatsTransientFailures Counter32, 1113 dbpPerPeerStatsPermanentFailures Counter32, 1114 dbpPerPeerStatsTransportDown Counter32 } 1116 dbpPerPeerStatsState OBJECT-TYPE 1117 SYNTAX INTEGER { closed(1), 1118 waitConnAck(2), 1119 waitICea(3), 1120 elect(4), 1121 waitReturns(5), 1122 rOpen(6), 1123 iOpen(7), 1124 closing(8) } 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "Connection state in the Peer State Machine of 1129 the peer with which this Diameter server is 1130 communicating. 1132 closed - Connection closed with this peer. 1133 waitConnAck - Waiting for an acknowledgment 1134 from this peer. 1135 waitICea - Waiting for a Capabilities-Exchange- 1136 Answer from this peer. 1137 elect - When the peer and the server are both 1138 trying to bring up a connection with 1139 each other at the same time. An 1140 election process begins which 1141 determines which socket remains open. 1142 waitReturns - Waiting for election returns. 1143 r-open - Responder transport connection is 1144 used for communication. 1145 i-open - Initiator transport connection is 1146 used for communication. 1147 closing - Actively closing and doing cleanup." 1148 ::= { dbpPerPeerStatsEntry 1 } 1150 dbpPerPeerStatsStateDuration OBJECT-TYPE 1151 SYNTAX TimeTicks 1152 MAX-ACCESS read-only 1153 STATUS current 1154 DESCRIPTION 1155 "Peer state duration." 1156 ::= { dbpPerPeerStatsEntry 2 } 1158 dbpPerPeerStatsLastDiscCause OBJECT-TYPE 1159 SYNTAX INTEGER { rebooting(1), 1160 busy(2), 1161 doNotWantToTalk(3), 1162 election(4) } 1163 MAX-ACCESS read-only 1164 STATUS current 1165 DESCRIPTION 1166 "The last cause for a peer's disconnection. 1168 rebooting - A scheduled reboot is imminent. 1170 busy - The peer's internal resources are 1171 constrained, and it has determined 1172 that the transport connection needs 1173 to be shutdown. 1174 doNotWantToTalk - The peer has determined that 1175 it does not see a need for the 1176 transport connection to exist, 1177 since it does not expect any 1178 messages to be exchanged in 1179 the foreseeable future. 1180 electionLost - The peer has determined that it 1181 has lost the election process 1182 and has therefore disconnected 1183 the transport connection." 1184 ::= { dbpPerPeerStatsEntry 3 } 1186 dbpPerPeerStatsWhoInitDisconnect OBJECT-TYPE 1187 SYNTAX INTEGER { host(1), 1188 peer(2) } 1189 MAX-ACCESS read-only 1190 STATUS current 1191 DESCRIPTION 1192 "Did the host or peer initiate the disconnect? 1194 host - If this server initiated the disconnect. 1195 peer - If the peer with which this server was 1196 connected initiated the disconnect." 1197 ::= { dbpPerPeerStatsEntry 4 } 1199 dbpPerPeerStatsDWCurrentStatus OBJECT-TYPE 1200 SYNTAX INTEGER { okay(1), 1201 suspect(2), 1202 down(3), 1203 reopen(4) } 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "okay - Indicates the connection is presumed working. 1208 suspect - Indicates the connection is possibly 1209 congested or down. 1210 down - The peer is no longer reachable, causing 1211 the transport connection to be shutdown. 1212 reopen - Three watchdog messages are exchanged with 1213 accepted round trip times, and the connection 1214 to the peer is considered stabilized." 1215 ::= { dbpPerPeerStatsEntry 5 } 1217 dbpPerPeerStatsTimeoutConnAtmpts OBJECT-TYPE 1218 SYNTAX Counter32 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "If there is no transport connection with a peer, 1223 this is the number of times the server attempts 1224 to connect to that peer. This is reset on 1225 disconnection." 1226 ::= { dbpPerPeerStatsEntry 6 } 1228 dbpPerPeerStatsASRsIn OBJECT-TYPE 1229 SYNTAX Counter32 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "Number of Abort-Session-Request messages 1234 received from the peer." 1235 ::= { dbpPerPeerStatsEntry 7 } 1237 dbpPerPeerStatsASRsOut OBJECT-TYPE 1238 SYNTAX Counter32 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "Number of Abort-Session-Request 1243 messages sent to the peer." 1244 ::= { dbpPerPeerStatsEntry 8 } 1246 dbpPerPeerStatsASAsIn OBJECT-TYPE 1247 SYNTAX Counter32 1248 MAX-ACCESS read-only 1249 STATUS current 1250 DESCRIPTION 1251 "Number of Abort-Session-Answer 1252 messages received from the peer." 1253 ::= { dbpPerPeerStatsEntry 9 } 1255 dbpPerPeerStatsASAsOut OBJECT-TYPE 1256 SYNTAX Counter32 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "Number of Abort-Session-Answer 1261 messages sent to the peer." 1262 ::= { dbpPerPeerStatsEntry 10 } 1264 dbpPerPeerStatsACRsIn OBJECT-TYPE 1265 SYNTAX Counter32 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "Number of Accounting-Request messages 1270 received from the peer." 1271 ::= { dbpPerPeerStatsEntry 11 } 1273 dbpPerPeerStatsACRsOut OBJECT-TYPE 1274 SYNTAX Counter32 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "Number of Accounting-Request messages 1279 sent to the peer." 1280 ::= { dbpPerPeerStatsEntry 12 } 1282 dbpPerPeerStatsACAsIn OBJECT-TYPE 1283 SYNTAX Counter32 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "Number of Accounting-Answer messages 1288 received from the peer." 1289 ::= { dbpPerPeerStatsEntry 13 } 1291 dbpPerPeerStatsACAsOut OBJECT-TYPE 1292 SYNTAX Counter32 1293 MAX-ACCESS read-only 1294 STATUS current 1295 DESCRIPTION 1296 "Number of Accounting-Answer messages 1297 sent to the peer." 1298 ::= { dbpPerPeerStatsEntry 14 } 1300 dbpPerPeerStatsCERsIn OBJECT-TYPE 1301 SYNTAX Counter32 1302 MAX-ACCESS read-only 1303 STATUS current 1304 DESCRIPTION 1305 "Number of Capabilities-Exchange-Request 1306 messages received from the peer." 1307 ::= { dbpPerPeerStatsEntry 15 } 1309 dbpPerPeerStatsCERsOut OBJECT-TYPE 1310 SYNTAX Counter32 1311 MAX-ACCESS read-only 1312 STATUS current 1313 DESCRIPTION 1314 "Number of Capabilities-Exchange-Request 1315 messages sent to the peer." 1316 ::= { dbpPerPeerStatsEntry 16 } 1318 dbpPerPeerStatsCEAsIn OBJECT-TYPE 1319 SYNTAX Counter32 1320 MAX-ACCESS read-only 1321 STATUS current 1322 DESCRIPTION 1323 "Number of Capabilities-Exchange-Answer 1324 messages received from the peer." 1325 ::= { dbpPerPeerStatsEntry 17 } 1327 dbpPerPeerStatsCEAsOut OBJECT-TYPE 1328 SYNTAX Counter32 1329 MAX-ACCESS read-only 1330 STATUS current 1331 DESCRIPTION 1332 "Number of Capabilities-Exchange-Answer 1333 messages sent to the peer." 1334 ::= { dbpPerPeerStatsEntry 18 } 1336 dbpPerPeerStatsDWRsIn OBJECT-TYPE 1337 SYNTAX Counter32 1338 MAX-ACCESS read-only 1339 STATUS current 1340 DESCRIPTION 1341 "Number of Device-Watchdog-Request 1342 messages received from the peer." 1343 ::= { dbpPerPeerStatsEntry 19 } 1345 dbpPerPeerStatsDWRsOut OBJECT-TYPE 1346 SYNTAX Counter32 1347 MAX-ACCESS read-only 1348 STATUS current 1349 DESCRIPTION 1350 "Number of Device-Watchdog-Request 1351 messages sent to the peer." 1352 ::= { dbpPerPeerStatsEntry 20 } 1354 dbpPerPeerStatsDWAsIn OBJECT-TYPE 1355 SYNTAX Counter32 1356 MAX-ACCESS read-only 1357 STATUS current 1358 DESCRIPTION 1359 "Number of Device-Watchdog-Answer 1360 messages received from the peer." 1361 ::= { dbpPerPeerStatsEntry 21 } 1363 dbpPerPeerStatsDWAsOut OBJECT-TYPE 1364 SYNTAX Counter32 1365 MAX-ACCESS read-only 1366 STATUS current 1367 DESCRIPTION 1368 "Number of Device-Watchdog-Answer 1369 messages sent to the peer." 1370 ::= { dbpPerPeerStatsEntry 22 } 1372 dbpPerPeerStatsDPRsIn OBJECT-TYPE 1373 SYNTAX Counter32 1374 MAX-ACCESS read-only 1375 STATUS current 1376 DESCRIPTION 1377 "Number of Disconnect-Peer-Request messages 1378 received." 1379 ::= { dbpPerPeerStatsEntry 23 } 1381 dbpPerPeerStatsDPRsOut OBJECT-TYPE 1382 SYNTAX Counter32 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "Number of Disconnect-Peer-Request messages 1387 sent." 1388 ::= { dbpPerPeerStatsEntry 24 } 1390 dbpPerPeerStatsDPAsIn OBJECT-TYPE 1391 SYNTAX Counter32 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "Number of Disconnect-Peer-Answer messages 1396 received." 1397 ::= { dbpPerPeerStatsEntry 25 } 1399 dbpPerPeerStatsDPAsOut OBJECT-TYPE 1400 SYNTAX Counter32 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "Number of Disconnect-Peer-Answer messages 1405 sent." 1406 ::= { dbpPerPeerStatsEntry 26 } 1408 dbpPerPeerStatsRARsIn OBJECT-TYPE 1409 SYNTAX Counter32 1410 MAX-ACCESS read-only 1411 STATUS current 1412 DESCRIPTION 1413 "Number of Re-Auth-Request messages 1414 received." 1415 ::= { dbpPerPeerStatsEntry 27 } 1417 dbpPerPeerStatsRARsOut OBJECT-TYPE 1418 SYNTAX Counter32 1419 MAX-ACCESS read-only 1420 STATUS current 1421 DESCRIPTION 1422 "Number of Re-Auth-Request messages 1423 sent." 1424 ::= { dbpPerPeerStatsEntry 28 } 1426 dbpPerPeerStatsRAAsIn OBJECT-TYPE 1427 SYNTAX Counter32 1428 MAX-ACCESS read-only 1429 STATUS current 1430 DESCRIPTION 1431 "Number of Re-Auth-Answer messages 1432 received." 1433 ::= { dbpPerPeerStatsEntry 29 } 1435 dbpPerPeerStatsRAAsOut OBJECT-TYPE 1436 SYNTAX Counter32 1437 MAX-ACCESS read-only 1438 STATUS current 1439 DESCRIPTION 1440 "Number of Re-Auth-Answer messages 1441 sent." 1442 ::= { dbpPerPeerStatsEntry 30 } 1444 dbpPerPeerStatsSTRsIn OBJECT-TYPE 1445 SYNTAX Counter32 1446 MAX-ACCESS read-only 1447 STATUS current 1448 DESCRIPTION 1449 "Number of Session-Termination-Request 1450 messages received from the peer." 1451 ::= { dbpPerPeerStatsEntry 31 } 1453 dbpPerPeerStatsSTRsOut OBJECT-TYPE 1454 SYNTAX Counter32 1455 MAX-ACCESS read-only 1456 STATUS current 1457 DESCRIPTION 1458 "Number of Session-Termination-Request 1459 messages sent to the peer." 1460 ::= { dbpPerPeerStatsEntry 32 } 1462 dbpPerPeerStatsSTAsIn OBJECT-TYPE 1463 SYNTAX Counter32 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "Number of Session-Termination-Answer 1468 messages received from the peer." 1469 ::= { dbpPerPeerStatsEntry 33 } 1471 dbpPerPeerStatsSTAsOut OBJECT-TYPE 1472 SYNTAX Counter32 1473 MAX-ACCESS read-only 1474 STATUS current 1475 DESCRIPTION 1476 "Number of Session-Termination-Answer 1477 messages sent to the peer." 1478 ::= { dbpPerPeerStatsEntry 34 } 1480 dbpPerPeerStatsDWReqTimer OBJECT-TYPE 1481 SYNTAX TimeTicks 1482 MAX-ACCESS read-only 1483 STATUS current 1484 DESCRIPTION 1485 "Device-Watchdog Request Timer, which 1486 is the interval between packets sent to 1487 peers." 1488 ::= { dbpPerPeerStatsEntry 35 } 1490 dbpPerPeerStatsRedirectEvents OBJECT-TYPE 1491 SYNTAX Counter32 1492 MAX-ACCESS read-only 1493 STATUS current 1494 DESCRIPTION 1495 "Redirect Event count, which is the number 1496 of redirects sent from a peer." 1497 ::= { dbpPerPeerStatsEntry 36 } 1499 dbpPerPeerStatsAccDupRequests OBJECT-TYPE 1500 SYNTAX Counter32 1501 MAX-ACCESS read-only 1502 STATUS current 1503 DESCRIPTION 1504 "The number of duplicate Diameter Accounting-Request 1505 packets received." 1506 ::= { dbpPerPeerStatsEntry 37 } 1508 dbpPerPeerStatsMalformedReqsts OBJECT-TYPE 1509 SYNTAX Counter32 1510 MAX-ACCESS read-only 1511 STATUS current 1512 DESCRIPTION 1513 "The number of malformed Diameter 1514 packets received." 1515 ::= { dbpPerPeerStatsEntry 38 } 1517 dbpPerPeerStatsAccsNotRecorded OBJECT-TYPE 1518 SYNTAX Counter32 1519 MAX-ACCESS read-only 1520 STATUS current 1521 DESCRIPTION 1522 "The number of Diameter Accounting-Request packets 1523 which were received and responded to but not 1524 recorded." 1525 ::= { dbpPerPeerStatsEntry 39 } 1527 dbpPerPeerStatsAccRetrans OBJECT-TYPE 1528 SYNTAX Counter32 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "The number of Diameter Accounting-Request packets 1533 retransmitted to this Diameter server." 1534 ::= { dbpPerPeerStatsEntry 40 } 1536 dbpPerPeerStatsTotalRetrans OBJECT-TYPE 1537 SYNTAX Counter32 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "The number of Diameter packets retransmitted 1542 to this Diameter server, not to include Diameter 1543 Accounting-Request packets retransmitted." 1544 ::= { dbpPerPeerStatsEntry 41 } 1546 dbpPerPeerStatsAccPendReqstsOut OBJECT-TYPE 1547 SYNTAX Gauge32 1548 MAX-ACCESS read-only 1549 STATUS current 1550 DESCRIPTION 1551 "The number of Diameter Accounting-Request packets 1552 sent to this peer that have not yet timed out or 1553 received a response. This variable is incremented when an 1554 Accounting-Request is sent to this server and decremented 1555 due to receipt of an Accounting-Response, a timeout or 1556 a retransmission." 1557 ::= { dbpPerPeerStatsEntry 42 } 1559 dbpPerPeerStatsAccReqstsDropped OBJECT-TYPE 1560 SYNTAX Counter32 1561 MAX-ACCESS read-only 1562 STATUS current 1563 DESCRIPTION 1564 "The number of Accounting-Requests to this server 1565 that have been dropped." 1566 ::= { dbpPerPeerStatsEntry 43 } 1568 dbpPerPeerStatsHByHDropMessages OBJECT-TYPE 1569 SYNTAX Counter32 1570 MAX-ACCESS read-only 1571 STATUS current 1572 DESCRIPTION 1573 "An answer message that is received with an unknown 1574 Hop-by-Hop Identifier. Does not include Accounting 1575 Requests dropped." 1576 ::= { dbpPerPeerStatsEntry 44 } 1578 dbpPerPeerStatsEToEDupMessages OBJECT-TYPE 1579 SYNTAX Counter32 1580 MAX-ACCESS read-only 1581 STATUS current 1582 DESCRIPTION 1583 "Duplicate answer messages that are to be locally 1584 consumed. Does not include duplicate Accounting 1585 Requests received." 1586 ::= { dbpPerPeerStatsEntry 45 } 1588 dbpPerPeerStatsUnknownTypes OBJECT-TYPE 1589 SYNTAX Counter32 1590 MAX-ACCESS read-only 1591 STATUS current 1592 DESCRIPTION 1593 "The number of Diameter packets of unknown type 1594 which were received." 1595 ::= { dbpPerPeerStatsEntry 46 } 1597 dbpPerPeerStatsProtocolErrors OBJECT-TYPE 1598 SYNTAX Counter32 1599 MAX-ACCESS read-only 1600 STATUS current 1601 DESCRIPTION 1602 "Number of protocol errors returned to peer, 1603 but not including redirects." 1605 ::= { dbpPerPeerStatsEntry 47 } 1607 dbpPerPeerStatsTransientFailures OBJECT-TYPE 1608 SYNTAX Counter32 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "Transient Failure count." 1613 ::= { dbpPerPeerStatsEntry 48 } 1615 dbpPerPeerStatsPermanentFailures OBJECT-TYPE 1616 SYNTAX Counter32 1617 MAX-ACCESS read-only 1618 STATUS current 1619 DESCRIPTION 1620 "Number of permanent failures returned to peer." 1621 ::= { dbpPerPeerStatsEntry 49 } 1623 dbpPerPeerStatsTransportDown OBJECT-TYPE 1624 SYNTAX Counter32 1625 MAX-ACCESS read-only 1626 STATUS current 1627 DESCRIPTION 1628 "Number of unexpected transport failures." 1629 ::= { dbpPerPeerStatsEntry 50 } 1631 dbpRealmMessageRouteTable OBJECT-TYPE 1632 SYNTAX SEQUENCE OF DbpRealmMessageRouteEntry 1633 MAX-ACCESS not-accessible 1634 STATUS current 1635 DESCRIPTION 1636 "The table listing the Diameter 1637 Realm-based Message Route information." 1638 ::= { dbpRealmStats 1 } 1640 dbpRealmMessageRouteEntry OBJECT-TYPE 1641 SYNTAX DbpRealmMessageRouteEntry 1642 MAX-ACCESS not-accessible 1643 STATUS current 1644 DESCRIPTION 1645 "A row entry representing a Diameter 1646 Realm Based Message Route server." 1647 INDEX { dbpRealmMessageRouteIndex } 1648 ::= { dbpRealmMessageRouteTable 1 } 1650 DbpRealmMessageRouteEntry ::= SEQUENCE { 1651 dbpRealmMessageRouteIndex Unsigned32, 1652 dbpRealmMessageRouteRealm SnmpAdminString, 1653 dbpRealmMessageRouteApp Unsigned32, 1654 dbpRealmMessageRouteType INTEGER, 1655 dbpRealmMessageRouteAction INTEGER, 1656 dbpRealmMessageRouteACRsIn Counter32, 1657 dbpRealmMessageRouteACRsOut Counter32, 1658 dbpRealmMessageRouteACAsIn Counter32, 1659 dbpRealmMessageRouteACAsOut Counter32, 1660 dbpRealmMessageRouteRARsIn Counter32, 1661 dbpRealmMessageRouteRARsOut Counter32, 1662 dbpRealmMessageRouteRAAsIn Counter32, 1663 dbpRealmMessageRouteRAAsOut Counter32, 1664 dbpRealmMessageRouteSTRsIn Counter32, 1665 dbpRealmMessageRouteSTRsOut Counter32, 1666 dbpRealmMessageRouteSTAsIn Counter32, 1667 dbpRealmMessageRouteSTAsOut Counter32, 1668 dbpRealmMessageRouteASRsIn Counter32, 1669 dbpRealmMessageRouteASRsOut Counter32, 1670 dbpRealmMessageRouteASAsIn Counter32, 1671 dbpRealmMessageRouteASAsOut Counter32, 1672 dbpRealmMessageRouteAccRetrans Counter32, 1673 dbpRealmMessageRouteAccDupReqsts Counter32, 1674 dbpRealmMessageRoutePendReqstsOut Gauge32, 1675 dbpRealmMessageRouteReqstsDrop Counter32 } 1677 dbpRealmMessageRouteIndex OBJECT-TYPE 1678 SYNTAX Unsigned32 (1..4294967295) 1679 MAX-ACCESS not-accessible 1680 STATUS current 1681 DESCRIPTION 1682 "A number uniquely identifying each Realm." 1683 ::= { dbpRealmMessageRouteEntry 1 } 1685 dbpRealmMessageRouteRealm OBJECT-TYPE 1686 SYNTAX SnmpAdminString 1687 MAX-ACCESS read-only 1688 STATUS current 1689 DESCRIPTION 1690 "Realm name" 1691 ::= { dbpRealmMessageRouteEntry 2 } 1693 dbpRealmMessageRouteApp OBJECT-TYPE 1694 SYNTAX Unsigned32 (1..4294967295) 1695 MAX-ACCESS read-only 1696 STATUS current 1697 DESCRIPTION 1698 "Application id used to route packets 1699 to this realm." 1700 ::= { dbpRealmMessageRouteEntry 3 } 1702 dbpRealmMessageRouteType OBJECT-TYPE 1703 SYNTAX INTEGER { acct(1), 1704 auth(2), 1705 both(3) } 1706 MAX-ACCESS read-only 1707 STATUS current 1708 DESCRIPTION 1709 "The types of service supported for each 1710 realm application: accounting, 1711 authentication or both." 1712 ::= { dbpRealmMessageRouteEntry 4 } 1714 dbpRealmMessageRouteAction OBJECT-TYPE 1715 SYNTAX INTEGER { local(1), 1716 relay(2), 1717 proxy(3), 1718 redirect(4) } 1719 MAX-ACCESS read-only 1720 STATUS current 1721 DESCRIPTION 1722 "The action is used to identify how a 1723 message should be treated based on the realm, 1724 application and type. 1725 local - Diameter messages that resolve to a 1726 route entry with the Local Action set to 1727 Local can be satisfied locally, and do 1728 not need to be routed to another server. 1729 relay - All Diameter messages that fall within 1730 this category MUST be routed to a 1731 next-hop server, without modifying any 1732 non-routing AVPs. 1733 proxy - All Diameter messages that fall within this 1734 category MUST be routed to a next-hop 1735 server. 1736 redirect - Diameter messages that fall within this 1737 category MUST have the identity of the home 1738 Diameter server(s) appended, and returned 1739 to the sender of the message." 1740 ::= { dbpRealmMessageRouteEntry 5 } 1742 dbpRealmMessageRouteACRsIn OBJECT-TYPE 1743 SYNTAX Counter32 1744 MAX-ACCESS read-only 1745 STATUS current 1746 DESCRIPTION 1747 "Number of Accounting-Request messages 1748 received from the realm." 1749 ::= { dbpRealmMessageRouteEntry 6 } 1751 dbpRealmMessageRouteACRsOut OBJECT-TYPE 1752 SYNTAX Counter32 1753 MAX-ACCESS read-only 1754 STATUS current 1755 DESCRIPTION 1756 "Number of Accounting-Request messages 1757 sent to the realm." 1758 ::= { dbpRealmMessageRouteEntry 7 } 1760 dbpRealmMessageRouteACAsIn OBJECT-TYPE 1761 SYNTAX Counter32 1762 MAX-ACCESS read-only 1763 STATUS current 1764 DESCRIPTION 1765 "Number of Accounting-Answer messages 1766 received from the realm." 1767 ::= { dbpRealmMessageRouteEntry 8 } 1769 dbpRealmMessageRouteACAsOut OBJECT-TYPE 1770 SYNTAX Counter32 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION 1774 "Number of Accounting-Answer messages 1775 sent to the realm." 1776 ::= { dbpRealmMessageRouteEntry 9 } 1778 dbpRealmMessageRouteRARsIn OBJECT-TYPE 1779 SYNTAX Counter32 1780 MAX-ACCESS read-only 1781 STATUS current 1782 DESCRIPTION 1783 "Number of Re-Auth-Request messages 1784 received from the realm." 1785 ::= { dbpRealmMessageRouteEntry 10 } 1787 dbpRealmMessageRouteRARsOut OBJECT-TYPE 1788 SYNTAX Counter32 1789 MAX-ACCESS read-only 1790 STATUS current 1791 DESCRIPTION 1792 "Number of Re-Auth-Request messages 1793 sent to the realm." 1794 ::= { dbpRealmMessageRouteEntry 11 } 1796 dbpRealmMessageRouteRAAsIn OBJECT-TYPE 1797 SYNTAX Counter32 1798 MAX-ACCESS read-only 1799 STATUS current 1800 DESCRIPTION 1801 "Number of Re-Auth-Answer messages 1802 received from the realm." 1803 ::= { dbpRealmMessageRouteEntry 12 } 1805 dbpRealmMessageRouteRAAsOut OBJECT-TYPE 1806 SYNTAX Counter32 1807 MAX-ACCESS read-only 1808 STATUS current 1809 DESCRIPTION 1810 "Number of Re-Auth-Answer messages 1811 sent to the realm." 1812 ::= { dbpRealmMessageRouteEntry 13 } 1814 dbpRealmMessageRouteSTRsIn OBJECT-TYPE 1815 SYNTAX Counter32 1816 MAX-ACCESS read-only 1817 STATUS current 1818 DESCRIPTION 1819 "Number of Session-Termination-Request messages 1820 received from the realm." 1821 ::= { dbpRealmMessageRouteEntry 14 } 1823 dbpRealmMessageRouteSTRsOut OBJECT-TYPE 1824 SYNTAX Counter32 1825 MAX-ACCESS read-only 1826 STATUS current 1827 DESCRIPTION 1828 "Number of Session-Termination-Request messages 1829 sent to the realm." 1830 ::= { dbpRealmMessageRouteEntry 15 } 1832 dbpRealmMessageRouteSTAsIn OBJECT-TYPE 1833 SYNTAX Counter32 1834 MAX-ACCESS read-only 1835 STATUS current 1836 DESCRIPTION 1837 "Number of Session-Termination-Answer messages 1838 received from the realm." 1839 ::= { dbpRealmMessageRouteEntry 16 } 1841 dbpRealmMessageRouteSTAsOut OBJECT-TYPE 1842 SYNTAX Counter32 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "Number of Session-Termination-Answer messages 1847 sent to the realm." 1848 ::= { dbpRealmMessageRouteEntry 17 } 1850 dbpRealmMessageRouteASRsIn OBJECT-TYPE 1851 SYNTAX Counter32 1852 MAX-ACCESS read-only 1853 STATUS current 1854 DESCRIPTION 1855 "Number of Abort-Session-Request messages 1856 received from the realm." 1857 ::= { dbpRealmMessageRouteEntry 18 } 1859 dbpRealmMessageRouteASRsOut OBJECT-TYPE 1860 SYNTAX Counter32 1861 MAX-ACCESS read-only 1862 STATUS current 1863 DESCRIPTION 1864 "Number of Abort-Session-Request messages 1865 sent to the realm." 1866 ::= { dbpRealmMessageRouteEntry 19 } 1868 dbpRealmMessageRouteASAsIn OBJECT-TYPE 1869 SYNTAX Counter32 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "Number of Abort-Session-Answer messages 1874 received from the realm." 1875 ::= { dbpRealmMessageRouteEntry 20 } 1877 dbpRealmMessageRouteASAsOut OBJECT-TYPE 1878 SYNTAX Counter32 1879 MAX-ACCESS read-only 1880 STATUS current 1881 DESCRIPTION 1882 "Number of Abort-Session-Answer messages 1883 sent to the realm." 1884 ::= { dbpRealmMessageRouteEntry 21 } 1886 dbpRealmMessageRouteAccRetrans OBJECT-TYPE 1887 SYNTAX Counter32 1888 MAX-ACCESS read-only 1889 STATUS current 1890 DESCRIPTION 1891 "The number of Diameter accounting packets 1892 retransmitted to this realm." 1893 ::= { dbpRealmMessageRouteEntry 22 } 1895 dbpRealmMessageRouteAccDupReqsts OBJECT-TYPE 1896 SYNTAX Counter32 1897 MAX-ACCESS read-only 1898 STATUS current 1899 DESCRIPTION 1900 "The number of duplicate Diameter accounting 1901 packets sent to this realm." 1902 ::= { dbpRealmMessageRouteEntry 23 } 1904 dbpRealmMessageRoutePendReqstsOut OBJECT-TYPE 1905 SYNTAX Gauge32 1906 MAX-ACCESS read-only 1907 STATUS current 1908 DESCRIPTION 1909 "The number of Diameter Accounting-Request packets 1910 sent to this peer that have not yet timed out or 1911 received a response. This variable is incremented when an 1912 Accounting-Request is sent to this server and decremented 1913 due to receipt of an Accounting-Response, a timeout or 1914 a retransmission." 1915 ::= { dbpRealmMessageRouteEntry 24 } 1917 dbpRealmMessageRouteReqstsDrop OBJECT-TYPE 1918 SYNTAX Counter32 1919 MAX-ACCESS read-only 1920 STATUS current 1921 DESCRIPTION 1922 "The number of requsts dropped by this realm." 1923 ::= { dbpRealmMessageRouteEntry 25 } 1925 dbpRealmKnownPeersTable OBJECT-TYPE 1926 SYNTAX SEQUENCE OF DbpRealmKnownPeersEntry 1927 MAX-ACCESS not-accessible 1928 STATUS current 1929 DESCRIPTION 1930 "The table listing the Diameter 1931 Realms and known peers." 1932 ::= { dbpRealmCfgs 1 } 1934 dbpRealmKnownPeersEntry OBJECT-TYPE 1935 SYNTAX DbpRealmKnownPeersEntry 1936 MAX-ACCESS not-accessible 1937 STATUS current 1938 DESCRIPTION 1939 "A row entry representing a Diameter 1940 Realm and known peers." 1941 INDEX { dbpRealmMessageRouteIndex, 1942 dbpRealmKnownPeersIndex } 1944 ::= { dbpRealmKnownPeersTable 1 } 1946 DbpRealmKnownPeersEntry ::= SEQUENCE { 1947 dbpRealmKnownPeersIndex Unsigned32, 1948 dbpRealmKnownPeers Unsigned32, 1949 dbpRealmKnownPeersChosen INTEGER } 1951 dbpRealmKnownPeersIndex OBJECT-TYPE 1952 SYNTAX Unsigned32 (1..4294967295) 1953 MAX-ACCESS not-accessible 1954 STATUS current 1955 DESCRIPTION 1956 "A sequential identifier number." 1957 ::= { dbpRealmKnownPeersEntry 1 } 1959 dbpRealmKnownPeers OBJECT-TYPE 1960 SYNTAX Unsigned32 (1..4294967295) 1961 MAX-ACCESS read-only 1962 STATUS current 1963 DESCRIPTION 1964 "The index of the peer this realm knows about. 1965 This is an ordered list, where the ordering 1966 signifies the order in which the peers are 1967 tried. Same as the dbpPeerIndex" 1968 ::= { dbpRealmKnownPeersEntry 2 } 1970 dbpRealmKnownPeersChosen OBJECT-TYPE 1971 SYNTAX INTEGER { roundRobin(1), 1972 loadBalance(2), 1973 firstPreferred(3), 1974 mostRecentFirst(4), 1975 other(5) } 1976 MAX-ACCESS read-only 1977 STATUS current 1978 DESCRIPTION 1979 "How the realm chooses which peer to send 1980 packets to. 1981 roundRobin - The peer used for each transaction 1982 is selected based on the order in 1983 which peers are configured. 1984 loadBalance - The peer used for each transaction 1985 is based on the load metric (maybe 1986 implementation dependent) of all 1987 peers defined for the realm, with 1988 the least loaded server selected 1989 first. 1990 firstPreferred - The first defined server is always 1991 used for transactions unless 1992 failover occurs. 1993 mostRecentFirst - The most recently used server is 1994 used first for each transaction." 1995 ::= { dbpRealmKnownPeersEntry 3 } 1997 -- -- Conformance -- dbpMIBCompliances 1999 diameterBaseProtocolMIBCompliances 2000 OBJECT IDENTIFIER ::= { diameterBaseConform 1 } 2002 diameterBaseProtocolMIBGroups 2003 OBJECT IDENTIFIER ::= { diameterBaseConform 2 } 2005 -- -- Compliance Statements -- 2007 diameterBaseProtocolCompliance MODULE-COMPLIANCE 2008 STATUS current 2009 DESCRIPTION 2010 "The compliance statement for Diameter Base 2011 Protocol entities." 2012 MODULE -- this module 2013 MANDATORY-GROUPS { dbpLocalCfgGroup, 2014 dbpPeerCfgGroup, 2015 dbpPeerStatsGroup, 2016 dbpNotificationsGroup, 2017 dbpNotifCfgGroup } 2019 GROUP dbpLocalCfgSkippedGroup 2020 DESCRIPTION 2021 "This group is only mandatory for a system that 2022 implements all the local config objects." 2024 GROUP dbpLocalStatsSkippedGroup 2025 DESCRIPTION 2026 "This group is only mandatory for a system that 2027 implements all the local statistics objects." 2029 GROUP dbpPeerCfgSkippedGroup 2030 DESCRIPTION 2031 "This group is only mandatory for a system that 2032 implements all the peer config objects." 2034 GROUP dbpPeerStatsSkippedGroup 2035 DESCRIPTION 2036 "This group is only mandatory for a system that 2037 implements all the peer statistic objects." 2039 GROUP dbpRealmCfgSkippedGroup 2040 DESCRIPTION 2041 "This group is only mandatory for a system that 2042 implementsall the realm config objects." 2044 GROUP dbpPMIBRealmStatsSkippedGroup 2045 DESCRIPTION 2046 "This group is only mandatory for a system that 2047 implements all the realm statistic objects." 2049 ::= { diameterBaseProtocolCompliances 1 } 2051 -- -- Units of Conformance -- 2053 dbpLocalCfgGroup OBJECT-GROUP 2054 OBJECTS { 2055 dbpLocalRealm, 2056 dbpLocalOriginHost, 2057 dbpLocalVendorId, 2058 dbpLocalVendorStorageType, 2059 dbpLocalVendorRowStatus 2060 } 2061 STATUS current 2062 DESCRIPTION 2063 "A collection of objects providing configuration common 2064 to the server." 2065 ::= { diameterBaseProtocolMIBGroups 1 } 2067 dbpPeerCfgGroup OBJECT-GROUP 2068 OBJECTS { 2069 dbpPeerId, 2070 dbpPeerPortConnect, 2071 dbpPeerPortListen, 2072 dbpPeerProtocol, 2073 dbpPeerSecurity, 2074 dbpPeerFirmwareRevision, 2075 dbpPeerStorageType, 2076 dbpPeerRowStatus, 2077 dbpPeerIpAddressType, 2078 dbpPeerIpAddress, 2079 dbpPeerVendorId, 2080 dbpPeerVendorStorageType, 2081 dbpPeerVendorRowStatus 2082 } 2083 STATUS current 2084 DESCRIPTION 2085 "A collection of objects providing configuration 2086 of the Diameter peers." 2087 ::= { diameterBaseProtocolMIBGroups 2 } 2089 dbpPeerStatsGroup OBJECT-GROUP 2090 OBJECTS { 2091 dbpPeerStatsState, 2092 dbpPeerStatsStateDuration, 2093 dbpPeerStatsLastDiscCause, 2094 dbpPeerStatsWhoInitDisconnect, 2095 dbpPeerStatsDWCurrentStatus, 2096 dbpPeerStatsTimeoutConnAtmpts, 2097 dbpPeerStatsASRsIn, 2098 dbpPeerStatsASRsOut, 2099 dbpPeerStatsASAsIn, 2100 dbpPeerStatsASAsOut, 2101 dbpPeerStatsACRsIn, 2102 dbpPeerStatsACRsOut, 2103 dbpPeerStatsACAsIn, 2104 dbpPeerStatsACAsOut, 2105 dbpPeerStatsCERsIn, 2106 dbpPeerStatsCERsOut, 2107 dbpPeerStatsCEAsIn, 2108 dbpPeerStatsCEAsOut, 2109 dbpPeerStatsDWRsIn, 2110 dbpPeerStatsDWRsOut, 2111 dbpPeerStatsDWAsIn, 2112 dbpPeerStatsDWAsOut, 2113 dbpPeerStatsDPRsIn, 2114 dbpPeerStatsDPRsOut, 2115 dbpPeerStatsDPAsIn, 2116 dbpPeerStatsDPAsOut, 2117 dbpPeerStatsRARsIn, 2118 dbpPeerStatsRARsOut, 2119 dbpPeerStatsRAAsIn, 2120 dbpPeerStatsRAAsOut, 2121 dbpPeerStatsSTRsIn, 2122 dbpPeerStatsSTRsOut, 2123 dbpPeerStatsSTAsIn, 2124 dbpPeerStatsSTAsOut, 2125 dbpPeerStatsDWReqTimer, 2126 dbpPeerStatsRedirectEvents, 2127 dbpPeerStatsAccDupRequests, 2128 dbpPeerStatsMalformedReqsts, 2129 dbpPeerStatsAccsNotRecorded, 2130 dbpPeerStatsAccRetrans, 2131 dbpPeerStatsTotalRetrans, 2132 dbpPeerStatsAccPendReqstsOut, 2133 dbpPeerStatsAccReqstsDropped, 2134 dbpPeerStatsHByHDropMessages, 2135 dbpPeerStatsEToEDupMessages, 2136 dbpPeerStatsUnknownTypes, 2137 dbpPeerStatsProtocolErrors, 2138 dbpPeerStatsTransientFailures, 2139 dbpPeerStatsPermanentFailures, 2140 dbpPeerStatsTransportDown 2141 } 2142 STATUS current 2143 DESCRIPTION 2144 "A collection of objects providing statistics 2145 of the Diameter peers." 2146 ::= { diameterBaseProtocolMIBGroups 3 } 2148 dbpNotificationsGroup NOTIFICATION-GROUP 2149 NOTIFICATIONS { 2150 dbpProtocolErrorNotif, 2151 dbpTransientFailureNotif, 2152 dbpPermanentFailureNotif, 2153 dbpPeerConnectionDownNotif, 2154 dbpPeerConnectionUpNotif 2155 } 2156 STATUS current 2157 DESCRIPTION 2158 "The set of notifications which an agent is required 2159 to implement." 2160 ::= { diameterBaseProtocolMIBGroups 4 } 2162 dbpNotifCfgGroup OBJECT-GROUP 2163 OBJECTS { 2164 dbpProtocolErrorNotifEnabled, 2165 dbpTransientFailureNotifEnabled, 2166 dbpPermanentFailureNotifEnabled, 2167 dbpPeerConnectionDownNotifEnabled, 2168 dbpPeerConnectionUpNotifEnabled 2169 } 2170 STATUS current 2171 DESCRIPTION 2172 "A collection of objects providing configuration for 2173 base protocol notifications." 2174 ::= { diameterBaseProtocolMIBGroups 5 } 2176 dbpLocalCfgSkippedGroup OBJECT-GROUP 2177 OBJECTS { 2178 dbpLocalId, 2179 dbpLocalIpAddrType, 2180 dbpLocalIpAddress, 2181 dbpLocalTcpListenPort, 2182 dbpLocalSctpListenPort, 2183 dbpLocalStatsTotalPacketsIn, 2184 dbpLocalStatsTotalPacketsOut, 2185 dbpLocalStatsTotalUpTime, 2186 dbpLocalResetTime, 2187 dbpLocalConfigReset, 2188 dbpLocalApplStorageType, 2189 dbpLocalApplRowStatus, 2190 dbpAppAdvToPeerServices, 2191 dbpAppAdvToPeerStorageType, 2192 dbpAppAdvToPeerRowStatus 2193 } 2194 STATUS current 2195 DESCRIPTION 2196 "A collection of objects providing configuration common 2197 to the server." 2198 ::= { diameterBaseProtocolMIBGroups 6 } 2200 dbpLocalStatsSkippedGroup OBJECT-GROUP 2201 OBJECTS { 2202 dbpLocalStatsTotalPacketsIn, 2203 dbpLocalStatsTotalPacketsOut, 2204 dbpLocalStatsTotalUpTime, 2205 dbpLocalResetTime, 2206 dbpLocalConfigReset 2207 } 2208 STATUS current 2209 DESCRIPTION 2210 "A collection of objects providing statistics common 2211 to the server." 2212 ::= { diameterBaseProtocolMIBGroups 7 } 2214 dbpPeerCfgSkippedGroup OBJECT-GROUP 2215 OBJECTS { cdbpAppAdvFromPeerType } 2216 STATUS current 2217 DESCRIPTION 2218 "A collection of objects providing configuration for 2219 Diameter peers." 2220 ::= { diameterBaseProtocolMIBGroups 8 } 2222 dbpPeerStatsSkippedGroup OBJECT-GROUP 2223 OBJECTS { 2224 dbpPeerStatsDWCurrentStatus, 2225 dbpPeerStatsDWReqTimer, 2226 dbpPeerStatsRedirectEvents, 2227 dbpPeerStatsAccDupRequests, 2228 dbpPeerStatsEToEDupMessages 2229 } 2230 STATUS current 2231 DESCRIPTION 2232 "A collection of objects providing statistics 2233 of Diameter peers." 2234 ::= { diameterBaseProtocolMIBGroups 9 } 2236 dbpRealmCfgSkippedGroup OBJECT-GROUP 2237 OBJECTS { 2238 dbpRealmKnownPeers, 2239 dbpRealmKnownPeersChosen 2240 } 2241 STATUS current 2242 DESCRIPTION 2243 "A collection of objects providing configuration for 2244 realm message routing." 2245 ::= { diameterBaseProtocolMIBGroups 10 } 2247 dbpRealmStatsSkippedGroup OBJECT-GROUP 2248 OBJECTS { 2249 dbpRealmMessageRouteRealm, 2250 dbpRealmMessageRouteApp, 2251 dbpRealmMessageRouteType, 2252 dbpRealmMessageRouteAction, 2253 dbpRealmMessageRouteACRsIn, 2254 dbpRealmMessageRouteACRsOut, 2255 dbpRealmMessageRouteACAsIn, 2256 dbpRealmMessageRouteACAsOut, 2257 dbpRealmMessageRouteRARsIn, 2258 dbpRealmMessageRouteRARsOut, 2259 dbpRealmMessageRouteRAAsIn, 2260 dbpRealmMessageRouteRAAsOut, 2261 dbpRealmMessageRouteSTRsIn, 2262 dbpRealmMessageRouteSTRsOut, 2263 dbpRealmMessageRouteSTAsIn, 2264 dbpRealmMessageRouteSTAsOut, 2265 dbpRealmMessageRouteASRsIn, 2266 dbpRealmMessageRouteASRsOut, 2267 dbpRealmMessageRouteASAsIn, 2268 dbpRealmMessageRouteASAsOut, 2269 dbpRealmMessageRouteAccRetrans, 2270 dbpRealmMessageRouteAccDupReqsts, 2271 dbpRealmMessageRoutePendReqstsOut, 2272 dbpRealmMessageRouteReqstsDrop 2273 } 2274 STATUS current 2275 DESCRIPTION 2276 "A collection of objects providing statistics 2277 of realm message routing." 2278 ::= { diameterBaseProtocolMIBGroups 11 } 2280 END 2282 5. IANA Considerations 2284 IANA is requested to assign an OID under mib-2. 2286 6. Security Considerations 2288 There are managed objects defined in this MIB that have a MAX-ACCESS 2289 clause of read-write and/or read-create. Such objects may be 2290 considered sensitive or vulnerable in some network environments. The 2291 support for SET operations in a non-secure environment without proper 2292 protection can have a negative effect on network operations. 2294 There are a number of managed objects in this MIB that may contain 2295 sensitive information. These are: 2297 o diameterHostAddress 2299 o diameterPeerServerAddress 2301 o diameterPeerIpAddress 2303 These can be used to determine the address of the Diameter host, 2304 and/or peers with which the host is communicating. This information 2305 could be useful in impersonating the host or peer. 2307 It is important to control GET access to these objects and possibly 2308 to even encrypt the values of these object when sending them over the 2309 network via SNMP. Not all versions of SNMP provide features for such 2310 a secure environment. 2312 SNMPv1 by itself is not a secure environment. Even if the network 2313 itself is secure (for example by using IPSec), there is no control as 2314 to who on the secure network is allowed to access and GET (read) the 2315 objects in this MIB. 2317 It is recommended that the implementers consider the security 2318 features as provided by the SNMPv3 framework. Specifically, the use 2319 of the User-based Security Model [RFC3414] and the View-based Access 2320 Control Model [RFC3415] is recommended. 2322 It is then a customer/user responsibility to ensure that the SNMP 2323 entity giving access to an instance of this MIB, is properly 2324 configured to give access to the objects only to those principals 2325 (users) that have legitimate rights to indeed GET or SET (change/ 2326 create/delete) them. 2328 7. Contributors 2330 This document is based upon and derived from work done by Jay 2331 Koehler, Mark Eklund and Hai Li. 2333 8. Acknowledgements 2335 Thanks to David Battle for his participation and suggestions in 2336 designing the table structures; Kevin Lingle, Sumanth Mithra, Tolga 2337 Asveren and Biswaranjan Panda for reviewing the MIB and making 2338 invaluable suggestions; and Greg Weber for his help in representing 2339 the MIB at IETF meetings. 2341 9. References 2343 9.1. Normative References 2345 [RFC1215] Rose, M., "Convention for defining traps for use with the 2346 SNMP", RFC 1215, March 1991. 2348 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2349 Schoenwaelder, Ed., "Structure of Management Information 2350 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2352 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2353 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2354 STD 58, RFC 2579, April 1999. 2356 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2357 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2358 April 1999. 2360 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 2361 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 2363 [RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and 2364 P. McCann, "Diameter Mobile IPv4 Application", RFC 4004, 2365 August 2005. 2367 9.2. Informative References 2369 [RFC3141] Hiller, T., Walsh, P., Chen, X., Munson, M., Dommety, G., 2370 Sivalingham, S., Lim, B., McCann, P., Shiino, H., 2371 Hirschman, B., Manning, S., Hsu, R., Koo, H., Lipford, M., 2372 Calhoun, P., Lo, C., Jaques, E., Campbell, E., Y.Xu, 2373 S.Baba, T.Ayaki, T.Seki, and A.Hameed, "CDMA2000 Wireless 2374 Data Requirements for AAA", RFC 3141, June 2001. 2376 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2377 "Introduction and Applicability Statements for Internet- 2378 Standard Management Framework", RFC 3410, December 2002. 2380 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2381 (USM) for version 3 of the Simple Network Management 2382 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 2384 [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2385 Access Control Model (VACM) for the Simple Network 2386 Management Protocol (SNMP)", STD 62, RFC 3415, 2387 December 2002. 2389 [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, 2390 "Diameter Network Access Server Application", RFC 4005, 2391 August 2005. 2393 [RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. 2394 Loughney, "Diameter Credit-Control Application", RFC 4006, 2395 August 2005. 2397 [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible 2398 Authentication Protocol (EAP) Application", RFC 4072, 2399 August 2005. 2401 Authors' Addresses 2403 Glen Zorn 2404 Network Zen 2405 1310 East Thomas Street 2406 #306 2407 Seattle, Washington 98102 2408 USA 2410 Phone: +1 (206) 377-9035 2411 Email: gwz@net-zen.net 2412 Subash Comerica 2413 Cisco Systems 2414 Global Development Centre, Prestige Waterford 2415 No. 9 Brunton Road 2416 BGL3/MZ/ 2417 Bangalore, Karnataka 560025 2418 India 2420 Phone: +91 80 4103 6427 2421 Email: subashtc@cisco.com