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