AAA Working Group J. Koehler Internet-Draft M. Eklund Category: Standards Track H. Li Cisco Systems, Inc. expires December 2001 August 2001 Diameter Base Protocol MIB Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at: http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at: http://www.ietf.org/shadow.html. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. Abstract The Diameter base protocol is intended to provide a AAA framework for Mobile-IP [17, 18] , NASREQ [16] and ROAMOPS [21]. This draft defines the Management Information Base (MIB) module which describes the minimum amount of objects needed to manage the implementation of the Diameter base protocol. 1. Introduction Koehler et al. [Page 1] Internet-Draft Diameter Base Protocol MIB August 2001 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing Diameter base protocol. The Diameter base protocol provides the minimum requirements needed for an AAA transport protocol, as required by NASREQ [16], Mobile IP [17, 18], and ROAMOPS [21]. Over time, routers and network access servers (NAS) have increased in complexity and density, making the historically used RADIUS protocol increasingly unsuitable. The basic concept behind Diameter is to provide a base protocol that can be extended in order to provide AAA services to new access technologies. Currently, the protocol only concerns itself with Internet access, both in the traditional PPP sense as well as taking into account the ROAMOPS model, and Mobile-IP. 2. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [1]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 15, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in STD 58, RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13]. o A set of fundamental applications described in RFC 2573 [14] and the view-based access control mechanism described in RFC 2575 [15]. Koehler et al. [Page 2] Internet-Draft Diameter Base Protocol MIB August 2001 A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [22]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 3. Overview The base Diameter protocol is never used on its own. It is always extended for a particular application. Three Diameter applications are defined by companion documents: NASREQ [16], Mobile IP [17, 18], End-to-End Security [19]. This MIB supports objects which are defined in the base Diameter protocol as described in [20]. Objects related to the additional applications mentioned above will be implemented in separate MIBS as well as any additional applications added in the future. 4. Definitions DIAMETER-BASE-PROTOCOL-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Counter32, Integer32, Unsigned32, TimeTicks, mib-2 FROM SNMPv2-SMI InetAddressType, InetAddress FROM INET-ADDRESS-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; diameterMIB MODULE-IDENTITY LAST-UPDATED "200108160000Z" ORGANIZATION "IETF AAA Working Group." CONTACT-INFO " Jay Koehler Cisco Systems, Inc. 10850 Murdock Road Koehler et al. [Page 3] Internet-Draft Diameter Base Protocol MIB August 2001 Knoxville, TN 37932 US Phone: +1 865 671 0429 EMail: jkoehler@cisco.com Mark Eklund Cisco Systems, Inc. 10850 Murdock Road Knoxville, TN 37932 US Phone: +1 865 671 6255 Email: meklund@cisco.com Hai Li Cisco Systems, Inc. 10850 Murdock Road Knoxville, TN 37932 US Phone: +1 865 671 0429 EMail: haili@cisco.com" DESCRIPTION "The MIB module is based on the Diameter base protocol, draft-ietf-aaa-diameter-07.txt." ::= { mib-2 TBD } diameterBaseProtocolMIB OBJECT IDENTIFIER ::= {diameterMIB 1} diameterBaseProtocolMIBObjects OBJECT IDENTIFIER ::= { diameterBaseProtocolMIB 1 } diameterBaseTables OBJECT IDENTIFIER ::= { diameterBaseProtocolMIBObjects 1 } diameterBaseHostConfigs OBJECT IDENTIFIER ::= { diameterBaseProtocolMIBObjects 2 } diameterBaseHostStats OBJECT IDENTIFIER ::= { diameterBaseProtocolMIBObjects 3 } diameterServerID OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The implementation identification string for the Diameter authentication server software in use on the system, for example; `diameterd'" ::= {diameterBaseHostConfigs 1} diameterHostAddressType OBJECT-TYPE Koehler et al. [Page 4] Internet-Draft Diameter Base Protocol MIB August 2001 SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of internet address stored in diameterHostAddress." ::= {diameterBaseHostConfigs 2} diameterHostAddress OBJECT-TYPE SYNTAX InetAddres MAX-ACCESS read-only STATUS current DESCRIPTION "The IP-Address that corresponds to the Origin-Host AVP." ::= {diameterBaseHostConfigs 3} diameterTcpListenPort OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Diameter Tcp listen port." ::= {diameterBaseHostConfigs 4 } diameterSctpListenPort OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Diameter Sctp listen port." ::= {diameterBaseHostConfigs 5 } diameterServerStatsTotalPacketsIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of packets in." ::= { diameterBaseHostStats 1 } diameterServerStatsTotalPacketsOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of packets out." ::= { diameterBaseHostStats 2 } Koehler et al. [Page 5] Internet-Draft Diameter Base Protocol MIB August 2001 diameterServerStatsTotalUpTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The total server up time." ::= { diameterBaseHostStats 3 } diameterServerResetTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "If the server has a persistent state (e.g., a process) and supports a `reset' operation (e.g., can be told to re-read configuration files), this value will be the time elapsed (in hundredths of a second) since the server was `reset.' For software that does not have persistence or does not support a `reset' operation, this value will be zero." ::= { diameterBaseHostStats 4 } diameterServerConfigReset OBJECT-TYPE SYNTAX INTEGER { other(1), reset(2), initializing(3), running(4) } MAX-ACCESS read-write STATUS current DESCRIPTION "Status/action object to reinitialize any persistent server state. When set to reset(2), any persistent server state (such as a process) is reinitialized as if the server had just been started. This value will never be returned by a read operation. When read, one of the following values will be returned: other(1) - server in some unknown state; initializing(3) - server (re)initializing; running(4) - server currently running." ::= { diameterBaseHostStats 5 } diameterApplicationsTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterApplicationsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter supported applications." Koehler et al. [Page 6] Internet-Draft Diameter Base Protocol MIB August 2001 ::= { diameterBaseTables 1 } diameterApplicationsEntry OBJECT-TYPE SYNTAX DiameterApplicationsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter server." INDEX { diameterApplicationsIndex } ::= { diameterApplicationsTable 1 } DiameterApplicationsEntry ::= SEQUENCE { diameterApplicationsIndex Unsigned32 } diameterApplicationsIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "A number uniquely identifying the Diameter server supported applications." ::= { diameterApplicationsEntry 1 } diameterPeerServerTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterPeerServerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter Discovered and Configured Peer Servers information." ::= { diameterBaseTables 2 } diameterPeerServerEntry OBJECT-TYPE SYNTAX DiameterPeerServerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Discovered and Configured Peer Server." INDEX { diameterPeerServerIndex } ::= { diameterPeerServerTable 1 } DiameterPeerServerEntry ::= SEQUENCE { diameterPeerServerIndex Unsigned32, diameterPeerServerId SnmpAdminString, diameterPeerServerAddressType InetAddressType, diameterPeerServerAddress InetAddress, Koehler et al. [Page 7] Internet-Draft Diameter Base Protocol MIB August 2001 diameterPeerServerPortConnect Integer32, diameterPeerServerPortListen Integer32, diameterPeerServerProtocol INTEGER, diameterPeerServerSecurity INTEGER, diameterPeerServerVendorId Unsigned32 } diameterPeerServerIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number uniquely identifying each Diameter Peer with which the host server communicates." ::= { diameterPeerServerEntry 1 } diameterPeerServerId OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The server identifier for the Diameter Peer." ::= { diameterPeerServerEntry 2 } diameterPeerServerAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of address stored in diameterPeerServerAddress." ::= { diameterPeerServerEntry 3 } diameterPeerServerAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP Address for the Diameter Peer." ::= { diameterPeerServerEntry 4 } diameterPeerServerPortConnect OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The connection port the server used to connect to the Diameter Peer. If there is no active connection, this Koehler et al. [Page 8] Internet-Draft Diameter Base Protocol MIB August 2001 value will be zero(0)." ::= { diameterPeerServerEntry 5 } diameterPeerServerPortListen OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The port the server is listening on." ::= { diameterPeerServerEntry 6 } diameterPeerServerProtocol OBJECT-TYPE SYNTAX INTEGER { tcp(1), sctp(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The transport protocol (tcp/sctp) the Diameter Peer is using." ::= { diameterPeerServerEntry 7 } diameterPeerServerSecurity OBJECT-TYPE SYNTAX INTEGER { tls(1) } MAX-ACCESS read-only STATUS current DESCRIPTION "The security the Diameter Peer is using." ::= { diameterPeerServerEntry 8 } diameterPeerServerVendorId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The IANA Enterprise Codes value assigned to the vendor of the Diameter device." ::= { diameterPeerServerEntry 9 } diameterPeerIpAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterPeerIpAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter peer IP Addresses." ::= { diameterBaseTables 3 } diameterPeerIpAddrEntry OBJECT-TYPE Koehler et al. [Page 9] Internet-Draft Diameter Base Protocol MIB August 2001 SYNTAX DiameterPeerIpAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Peer Diameter server." INDEX { diameterPeerServerIndex, diameterIteratorIndex } ::= { diameterPeerIpAddrTable 1 } DiameterPeerIpAddrEntry ::= SEQUENCE { diameterIteratorIndex Unsigned32, diameterPeerIpAddressType InetAddressType, diameterPeerIpAddress InetAddress } diameterIteratorIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number uniquely identifying the number of IP Addresses supported by all Peer Diameter Servers." ::= { diameterPeerIpAddrEntry 1 } diameterPeerIpAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of address stored in diameterIpAddress." ::= {diameterPeerIpAddrEntry 2} diameterPeerIpAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP Address used for connections." ::= {diameterPeerIpAddrEntry 3} diameterAdvToPeerTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterAdvToPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the advertised applications from host to peer and the type Koehler et al. [Page 10] Internet-Draft Diameter Base Protocol MIB August 2001 of services supported, accounting, authentication or both." ::= { diameterBaseTables 4 } diameterAdvToPeerEntry OBJECT-TYPE SYNTAX DiameterAdvToPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Discovered and Configured Peer Server." INDEX { diameterPeerServerIndex, diameterAdvToPeerIndex } ::= { diameterAdvToPeerTable 1 } DiameterAdvToPeerEntry ::= SEQUENCE { diameterAdvToPeerIndex Unsigned32, diameterAdvToPeerServices INTEGER } diameterAdvToPeerIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number uniquely identifying the applications advertised to be supported to each Diameter Peer." ::= { diameterAdvToPeerEntry 1 } diameterAdvToPeerServices OBJECT-TYPE SYNTAX INTEGER { acct(1), auth(2), both(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The type of services supported for each application, accounting, authentication or both." ::= { diameterAdvToPeerEntry 2 } diameterAdvFromPeerTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterAdvFromPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the advertised applications to peer from host and the type of services supported, accounting, authentication or both." Koehler et al. [Page 11] Internet-Draft Diameter Base Protocol MIB August 2001 ::= { diameterBaseTables 5 } diameterAdvFromPeerEntry OBJECT-TYPE SYNTAX DiameterAdvFromPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Discovered and Configured Peer Server." INDEX { diameterPeerServerIndex, diameterAdvFromPeerIndex } ::= { diameterAdvFromPeerTable 1 } DiameterAdvFromPeerEntry ::= SEQUENCE { diameterAdvFromPeerIndex Unsigned32, diameterAdvFromPeerTypes INTEGER } diameterAdvFromPeerIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number uniquely identifying the applications advertised to be supported from each Diameter Peer." ::= { diameterAdvFromPeerEntry 1 } diameterAdvFromPeerTypes OBJECT-TYPE SYNTAX INTEGER { accounting(1), auth(2), both(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The type of services supported for each application, accounting, authentication or both." ::= { diameterAdvFromPeerEntry 2 } diameterPeerVendorIdTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterPeerVendorIdEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the supported vendor identifiers which may be used in order to know which vendor specific attributes may be sent to the peer." ::= { diameterBaseTables 6 } Koehler et al. [Page 12] Internet-Draft Diameter Base Protocol MIB August 2001 diameterPeerVendorIdEntry OBJECT-TYPE SYNTAX DiameterPeerVendorIdEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Discovered and Configured Peer Server." INDEX { diameterPeerServerIndex, diameterPeerVendorIdIndex} ::= { diameterPeerVendorIdTable 1 } DiameterPeerVendorIdEntry ::= SEQUENCE { diameterPeerVendorIdIndex Unsigned32 } diameterPeerVendorIdIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The IANA Enterprise Codes value assigned to the vendor of the Diameter device." ::= { diameterPeerVendorIdEntry 1 } diameterPeerApplicationsTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterPeerApplicationsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter Peer supported applications." ::= { diameterBaseTables 7 } diameterPeerApplicationsEntry OBJECT-TYPE SYNTAX DiameterPeerApplicationsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Peer." INDEX { diameterPeerServerIndex, diameterPeerApplicationsIndex } ::= { diameterPeerApplicationsTable 1 } DiameterPeerApplicationsEntry ::= SEQUENCE { diameterPeerApplicationsIndex Unsigned32, diameterPeerApplicationsSupported Unsigned32 } diameterPeerApplicationsIndex OBJECT-TYPE Koehler et al. [Page 13] Internet-Draft Diameter Base Protocol MIB August 2001 SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "A number uniquely identifying the application with which this peer server supports." ::= { diameterPeerApplicationsEntry 1 } diameterPeerApplicationsSupported OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "A number uniquely identifying the application with which this peer server supports." ::= { diameterPeerApplicationsEntry 2 } diameterPerPeerStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterPerPeerStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter Peer Statistics." ::= { diameterBaseTables 8 } diameterPerPeerStatsEntry OBJECT-TYPE SYNTAX DiameterPerPeerStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Peer." INDEX { diameterPeerServerIndex } ::= { diameterPerPeerStatsTable 1 } DiameterPerPeerStatsEntry ::= SEQUENCE { diameterPerPeerStatsFirmwareRevision Integer32, diameterPerPeerStatsState INTEGER, diameterPerPeerStatsStateDuration TimeTicks, diameterPerPeerStatsConnectionUpTime TimeTicks, diameterPerPeerStatsLastDisconnectCause INTEGER, diameterPerPeerStatsWhoInitiatedDisconnect INTEGER, diameterPerPeerStatsDWCurrentStatus INTEGER, diameterPerPeerStatsTimeoutConnectionAttempts Counter32, diameterPerPeerStatsASRIn Counter32, diameterPerPeerStatsASROut Counter32, diameterPerPeerStatsASAIn Counter32, Koehler et al. [Page 14] Internet-Draft Diameter Base Protocol MIB August 2001 diameterPerPeerStatsASAOut Counter32, diameterPerPeerStatsACRIn Counter32, diameterPerPeerStatsACROut Counter32, diameterPerPeerStatsACAIn Counter32, diameterPerPeerStatsACAOut Counter32, diameterPerPeerStatsCERIn Counter32, diameterPerPeerStatsCEROut Counter32, diameterPerPeerStatsCEAIn Counter32, diameterPerPeerStatsCEAOut Counter32, diameterPerPeerStatsDWRIn Counter32, diameterPerPeerStatsDWROut Counter32, diameterPerPeerStatsDWAIn Counter32, diameterPerPeerStatsDWAOut Counter32, diameterPerPeerStatsDPRIn Counter32, diameterPerPeerStatsDPROut Counter32, diameterPerPeerStatsDPAIn Counter32, diameterPerPeerStatsDPAOut Counter32, diameterPerPeerStatsRARIn Counter32, diameterPerPeerStatsRAROut Counter32, diameterPerPeerStatsRAAIn Counter32, diameterPerPeerStatsRAAOut Counter32, diameterPerPeerStatsSTRIn Counter32, diameterPerPeerStatsSTROut Counter32, diameterPerPeerStatsSTAIn Counter32, diameterPerPeerStatsSTAOut Counter32, diameterPerPeerStatsDWReqTimer TimeTicks, diameterPerPeerStatsInfoEvent Counter32, diameterPerPeerStatsRedirectEvent Counter32, diameterPerPeerStatsAccDupRequests Counter32, diameterPerPeerStatsAccMalformedRequests Counter32, diameterPerPeerStatsAccNotRecorded Counter32, diameterPerPeerStatsAccRetransmissions Counter32, diameterPerPeerStatsTotalRetransmissions Counter32, diameterPerPeerStatsAccPendingRequestsOut Gauge32, diameterPerPeerStatsAccRequestsDropped Counter32, diameterPerPeerStatsHopByHopIdMessDropped Counter32, diameterPerPeerStatsEndToEndDupMessages Counter32, diameterPerPeerStatsUnknownTypes Counter32, diameterPerPeerStatsMandatoryAVPUnknownRejects Counter32, diameterPerPeerStatsMandatoryAVPFaultRejects Counter32, diameterPerPeerStatsIgnoredAVP Counter32, diameterPerPeerStatsProtocolErrors Counter32, diameterPerPeerStatsTransientFailure Counter32, diameterPerPeerStatsPermanentFailures Counter32 } diameterPerPeerStatsFirmwareRevision OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only Koehler et al. [Page 15] Internet-Draft Diameter Base Protocol MIB August 2001 STATUS current DESCRIPTION "Firmware revision of peer. If no firmware revision, the revision of the Diameter software module may be reported instead." ::= { diameterPerPeerStatsEntry 1 } diameterPerPeerStatsState OBJECT-TYPE SYNTAX INTEGER { closed(1), wait-conn-ack(2), wait-i-cea(3), wait-conn-ack-elect(4), wait-returns(5), r-open(6), i-open(7) } MAX-ACCESS read-only STATUS current DESCRIPTION "Connection state in the Peer State Machine of the peer that this Diameter server is communicating." ::= { diameterPerPeerStatsEntry 2 } diameterPerPeerStatsStateDuration OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "Peer state duration." ::= { diameterPerPeerStatsEntry 3 } diameterPerPeerStatsConnectionUpTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "Peer session connection up time for duration of normal state." ::= { diameterPerPeerStatsEntry 4 } diameterPerPeerStatsLastDisconnectCause OBJECT-TYPE SYNTAX INTEGER { rebooting(1), busy(2), do-not-want-to-talk(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The last cause for a peers disconnection." ::= { diameterPerPeerStatsEntry 5 } Koehler et al. [Page 16] Internet-Draft Diameter Base Protocol MIB August 2001 diameterPerPeerStatsWhoInitiatedDisconnect OBJECT-TYPE SYNTAX INTEGER { host(1), peer(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Did the host or peer initiate the disconnect." ::= { diameterPerPeerStatsEntry 6 } diameterPerPeerStatsDWCurrentStatus OBJECT-TYPE SYNTAX INTEGER { okay(1), wait-dwa(2), suspect(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "okay -- indicates the connection is presumed working. wait-dwa -- indicates that a DWR has been sent but a DWA has not yet been received. suspect -- indicates the connection is possibly congested or down." ::= { diameterPerPeerStatsEntry 7 } diameterPerPeerStatsTimeoutConnectionAttempts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "If there is no transport connection with a peer, this is the number of times the server attempts to connect to that peer." ::= { diameterPerPeerStatsEntry 8 } diameterPerPeerStatsASRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Abort-Session-Request's in per peer." ::= { diameterPerPeerStatsEntry 9 } diameterPerPeerStatsASROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Abort-Session-Request's out per peer." ::= { diameterPerPeerStatsEntry 10 } Koehler et al. [Page 17] Internet-Draft Diameter Base Protocol MIB August 2001 diameterPerPeerStatsASAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Abort-Session-Answer in per peer." ::= { diameterPerPeerStatsEntry 11 } diameterPerPeerStatsASAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Abort-Session-Answer out per peer." ::= { diameterPerPeerStatsEntry 12 } diameterPerPeerStatsACRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Request in per peer." ::= { diameterPerPeerStatsEntry 13 } diameterPerPeerStatsACROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Request out per peer." ::= { diameterPerPeerStatsEntry 14 } diameterPerPeerStatsACAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Answer in per peer." ::= { diameterPerPeerStatsEntry 15 } diameterPerPeerStatsACAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Answer out per peer." ::= { diameterPerPeerStatsEntry 16 } Koehler et al. [Page 18] Internet-Draft Diameter Base Protocol MIB August 2001 diameterPerPeerStatsCERIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Capabilities-Exchange-Request in per peer." ::= { diameterPerPeerStatsEntry 17 } diameterPerPeerStatsCEROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Capabilities-Exchange-Request out per peer." ::= { diameterPerPeerStatsEntry 18 } diameterPerPeerStatsCEAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Capabilities-Exchange-Answer in per peer." ::= { diameterPerPeerStatsEntry 19 } diameterPerPeerStatsCEAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Capabilities-Exchange-Answer out per peer." ::= { diameterPerPeerStatsEntry 20 } diameterPerPeerStatsDWRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Device-Watchdog-Request in per peer." ::= { diameterPerPeerStatsEntry 21 } diameterPerPeerStatsDWROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Device-Watchdog-Request out per peer." ::= { diameterPerPeerStatsEntry 22 } Koehler et al. [Page 19] Internet-Draft Diameter Base Protocol MIB August 2001 diameterPerPeerStatsDWAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Device-Watchdog-Answer in per peer." ::= { diameterPerPeerStatsEntry 23 } diameterPerPeerStatsDWAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Device-Watchdog-Answer out per peer." ::= { diameterPerPeerStatsEntry 24 } diameterPerPeerStatsDPRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Disconnect-Peer-Request messages received." ::= { diameterPerPeerStatsEntry 25 } diameterPerPeerStatsDPROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Disconnect-Peer-Request messages sent." ::= { diameterPerPeerStatsEntry 26 } diameterPerPeerStatsDPAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Disconnect-Peer-Answer messages received." ::= { diameterPerPeerStatsEntry 27 } diameterPerPeerStatsDPAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION Koehler et al. [Page 20] Internet-Draft Diameter Base Protocol MIB August 2001 "Number of Disconnect-Peer-Answer messages sent." ::= { diameterPerPeerStatsEntry 28 } diameterPerPeerStatsRARIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Re-Auth-Request messages received." ::= { diameterPerPeerStatsEntry 29 } diameterPerPeerStatsRAROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Re-Auth-Request messages sent." ::= { diameterPerPeerStatsEntry 30 } diameterPerPeerStatsRAAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Re-Auth-Answer messages received." ::= { diameterPerPeerStatsEntry 31 } diameterPerPeerStatsRAAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Re-Auth-Answer messages sent." ::= { diameterPerPeerStatsEntry 32 } diameterPerPeerStatsSTRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session-Termination-Request in per peer." ::= { diameterPerPeerStatsEntry 33 } Koehler et al. [Page 21] Internet-Draft Diameter Base Protocol MIB August 2001 diameterPerPeerStatsSTROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session-Termination-Request out per peer." ::= { diameterPerPeerStatsEntry 34 } diameterPerPeerStatsSTAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session-Termination-Answer in per peer." ::= { diameterPerPeerStatsEntry 35 } diameterPerPeerStatsSTAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session-Termination-Answer out per peer." ::= { diameterPerPeerStatsEntry 36 } diameterPerPeerStatsDWReqTimer OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "Device-Watchdog Request Timer per peer." ::= { diameterPerPeerStatsEntry 37 } diameterPerPeerStatsInfoEvent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Information Event count." ::= { diameterPerPeerStatsEntry 38 } diameterPerPeerStatsRedirectEvent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Redirect Event count." ::= { diameterPerPeerStatsEntry 39 } Koehler et al. [Page 22] Internet-Draft Diameter Base Protocol MIB August 2001 diameterPerPeerStatsAccDupRequests OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of duplicate Diameter Accounting-Request packets received." ::= { diameterPerPeerStatsEntry 40 } diameterPerPeerStatsAccMalformedRequests OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of malformed Diameter Accounting-Request packets received." ::= { diameterPerPeerStatsEntry 41 } diameterPerPeerStatsAccNotRecorded OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Diameter Accounting-Request packets which were received and responded to but not recorded." ::= { diameterPerPeerStatsEntry 42 } diameterPerPeerStatsAccRetransmissions OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Diameter Accounting-Request packets retransmitted to this Diameter server." ::= { diameterPerPeerStatsEntry 43 } diameterPerPeerStatsTotalRetransmissions OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Diameter packets retransmitted to this Diameter server, not to include Diameter Accounting-Request packets retransmitted." ::= { diameterPerPeerStatsEntry 44 } diameterPerPeerStatsAccPendingRequestsOut OBJECT-TYPE Koehler et al. [Page 23] Internet-Draft Diameter Base Protocol MIB August 2001 SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Diameter Accounting-Request packets sent to this peer that have not yet timed out or received a response. This variable is incremented when an Accounting-Request is sent to this server and decremented due to receipt of an Accounting-Response, a timeout or a retransmission." ::= { diameterPerPeerStatsEntry 45 } diameterPerPeerStatsAccRequestsDropped OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Accounting-Requests to this server that have been dropped." ::= { diameterPerPeerStatsEntry 46 } diameterPerPeerStatsHopByHopIdMessDropped OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "An answer message that is received with an unknown Hop-by-Hop Identifier. Does not include Accounting Requests dropped." ::= { diameterPerPeerStatsEntry 47 } diameterPerPeerStatsEndToEndDupMessages OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Duplicate answer messages that are to be locally consumed. Does not include duplicate Accounting Requests received." ::= { diameterPerPeerStatsEntry 48 } diameterPerPeerStatsUnknownTypes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Diameter packets of unknowntype which were received." Koehler et al. [Page 24] Internet-Draft Diameter Base Protocol MIB August 2001 ::= { diameterPerPeerStatsEntry 49 } diameterPerPeerStatsMandatoryAVPUnknownRejects OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of unrecognized AVPs with the 'M' bit set received from peer." ::= { diameterPerPeerStatsEntry 50 } diameterPerPeerStatsMandatoryAVPFaultRejects OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of AVPs with the 'M' bit set where the AVP is not defined in a given message's ABNF." ::= { diameterPerPeerStatsEntry 51 } diameterPerPeerStatsIgnoredAVP OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of AVPs with the 'M' bit cleared and the AVP is not supported." ::= { diameterPerPeerStatsEntry 52 } diameterPerPeerStatsProtocolErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of protocol errors returned to peer." ::= { diameterPerPeerStatsEntry 53 } diameterPerPeerStatsTransientFailure OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Transient Failure count." ::= { diameterPerPeerStatsEntry 54 } diameterPerPeerStatsPermanentFailures OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only Koehler et al. [Page 25] Internet-Draft Diameter Base Protocol MIB August 2001 STATUS current DESCRIPTION "Number of permanent failures returned to peer." ::= { diameterPerPeerStatsEntry 55 } diameterRealmBasedMessageRouteTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterRealmBasedMessageRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter Realm Based Message Route information." ::= { diameterBaseTables 9 } diameterRealmBasedMessageRouteEntry OBJECT-TYPE SYNTAX DiameterRealmBasedMessageRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Realm Based Message Route server." INDEX { diameterRealmBasedMessageRouteIndex } ::= { diameterRealmBasedMessageRouteTable 1 } DiameterRealmBasedMessageRouteEntry ::= SEQUENCE { diameterRealmBasedMessageRouteIndex Unsigned32, diameterRealmBasedMessageRouteRealm SnmpAdminString, diameterRealmBasedMessageRouteApplication Unsigned32, diameterRealmBasedMessageRouteType INTEGER, diameterRealmBasedMessageRouteAction INTEGER, diameterRealmBasedMessageRouteACRIn Counter32, diameterRealmBasedMessageRouteACROut Counter32, diameterRealmBasedMessageRouteACAIn Counter32, diameterRealmBasedMessageRouteACAOut Counter32, diameterRealmBasedMessageRouteRARIn Counter32, diameterRealmBasedMessageRouteRAROut Counter32, diameterRealmBasedMessageRouteRAAIn Counter32, diameterRealmBasedMessageRouteRAAOut Counter32, diameterRealmBasedMessageRouteSTRIn Counter32, diameterRealmBasedMessageRouteSTROut Counter32, diameterRealmBasedMessageRouteASRIn Counter32, diameterRealmBasedMessageRouteASROut Counter32, diameterRealmBasedMessageRouteAccRetrans Counter32, diameterRealmBasedMessageRouteAccDupRequsts Counter32, diameterRealmBasedMessageRoutePendingRequestsOut Gauge32, diameterRealmBasedMessageRouteRequestDropped Counter32 } diameterRealmBasedMessageRouteIndex OBJECT-TYPE Koehler et al. [Page 26] Internet-Draft Diameter Base Protocol MIB August 2001 SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number uniquely identifying each Realm." ::= { diameterRealmBasedMessageRouteEntry 1 } diameterRealmBasedMessageRouteRealm OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "Realm name" ::= { diameterRealmBasedMessageRouteEntry 2 } diameterRealmBasedMessageRouteApplication OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Application requested by the user." ::= { diameterRealmBasedMessageRouteEntry 3 } diameterRealmBasedMessageRouteType OBJECT-TYPE SYNTAX INTEGER { accounting(1), auth(2), both(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The type of services supported for each application, accounting, authentication or both." ::= { diameterRealmBasedMessageRouteEntry 4 } diameterRealmBasedMessageRouteAction OBJECT-TYPE SYNTAX INTEGER { local(1), relay(2), proxy(3), redirect(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The local action is used to identify how a message should be treated based on the realm, application and type." ::= { diameterRealmBasedMessageRouteEntry 5 } diameterRealmBasedMessageRouteACRIn OBJECT-TYPE Koehler et al. [Page 27] Internet-Draft Diameter Base Protocol MIB August 2001 SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Request in per realm." ::= { diameterRealmBasedMessageRouteEntry 6 } diameterRealmBasedMessageRouteACROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Request out per realm." ::= { diameterRealmBasedMessageRouteEntry 7 } diameterRealmBasedMessageRouteACAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Answer in per realm." ::= { diameterRealmBasedMessageRouteEntry 8 } diameterRealmBasedMessageRouteACAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Answer out per realm." ::= { diameterRealmBasedMessageRouteEntry 9 } diameterRealmBasedMessageRouteRARIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Re-Auth-Request messages received." ::= { diameterRealmBasedMessageRouteEntry 10 } diameterRealmBasedMessageRouteRAROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Re-Auth-Request messages sent." ::= { diameterRealmBasedMessageRouteEntry 11 } Koehler et al. [Page 28] Internet-Draft Diameter Base Protocol MIB August 2001 diameterRealmBasedMessageRouteRAAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Re-Auth-Answer messages received." ::= { diameterRealmBasedMessageRouteEntry 12 } diameterRealmBasedMessageRouteRAAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Re-Auth-Answer messages sent." ::= { diameterRealmBasedMessageRouteEntry 13 } diameterRealmBasedMessageRouteSTRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session-Termination-Request in per realm." ::= { diameterRealmBasedMessageRouteEntry 14 } diameterRealmBasedMessageRouteSTROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session-Termination-Request out per realm." ::= { diameterRealmBasedMessageRouteEntry 15 } diameterRealmBasedMessageRouteASRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Abort-Session-Request's in per realm." ::= { diameterRealmBasedMessageRouteEntry 16 } diameterRealmBasedMessageRouteASROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Abort-Session-Request's out per realm." Koehler et al. [Page 29] Internet-Draft Diameter Base Protocol MIB August 2001 ::= { diameterRealmBasedMessageRouteEntry 17 } diameterRealmBasedMessageRouteAccRetrans OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Diameter accounting packets retransmitted to this realm." ::= { diameterRealmBasedMessageRouteEntry 18 } diameterRealmBasedMessageRouteAccDupRequsts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of duplicate Diameter accounting packets sent to this realm." ::= { diameterRealmBasedMessageRouteEntry 19 } diameterRealmBasedMessageRoutePendingRequestsOut OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Diameter Accounting-Request packets sent to this peer that have not yet timed out or received a response. This variable is incremented when an Accounting-Request is sent to this server and decremented due to receipt of an Accounting-Response, a timeout or a retransmission." ::= { diameterRealmBasedMessageRouteEntry 20 } diameterRealmBasedMessageRouteRequestDropped OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of requsts dropped by this real." ::= { diameterRealmBasedMessageRouteEntry 21 } diameterRealmKnownPeersTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterRealmKnownPeersEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter Realms and known peers ." Koehler et al. [Page 30] Internet-Draft Diameter Base Protocol MIB August 2001 ::= { diameterBaseTables 10 } diameterRealmKnownPeersEntry OBJECT-TYPE SYNTAX DiameterRealmKnownPeersEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Realm and known peers." INDEX { diameterRealmBasedMessageRouteIndex, diameterRealmKnownPeersIndex } ::= { diameterRealmKnownPeersTable 1 } DiameterRealmKnownPeersEntry ::= SEQUENCE { diameterRealmKnownPeersIndex Unsigned32, diameterRealmKnownPeersMapToPeerServer Unsigned32 } diameterRealmKnownPeersIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A sequential identifier number." ::= { diameterRealmKnownPeersEntry 1 } diameterRealmKnownPeersMapToPeerServer OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The index of the peer this realm knows about. Same as the diameterPeerServerIndex." ::= { diameterRealmKnownPeersEntry 2 } END 5. References [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 2001. [2] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991. Koehler et al. [Page 31] Internet-Draft Diameter Base Protocol MIB August 2001 [4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, Performance Systems International, March 1991. [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2001. [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 2001. [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 2001. [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990. [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 2001. [12] Blumenthal, U., and B. Wijnen, "User-based Security Model for Version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 2001. [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [14] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", RFC 2573, April 2001. [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model for the Simple Network Management Protocol (SNMP)", RFC 2575, April 2001. [16] P. Calhoun, W. Bulley, A. Rubens, J. Haag, "Diameter NASREQ Application", draft-ietf-aaa-diameter-nasreq-05.txt, IETF work in progress, June 2001. Koehler et al. [Page 32] Internet-Draft Diameter Base Protocol MIB August 2001 [17] P. Calhoun, C. Perkins, "Diameter Mobile IP Application", draft-ietf-aaa-diameter-mobileip-05.txt, IETF work in progress, June 2001. [18] T. Hiller and al, "CDMA2000 Wireless Data Requirements for AAA", draft-hiller-cdma2000-aaa-02.txt, IETF work in progress, Sep- tember 2000. [19] P. Calhoun, W. Bulley, S. Farrell, "Diameter CMS Security appli- cation", draft-ietf-aaa-diameter-cms-sec-00.txt (work in pro- gress), June 2001. [20] P. Calhoun, H. Akhtar, J. Arkko, E. Guttman, A. Rubens, G. Zorn, "Diameter Base Protocol", draft-ietf-aaa-diameter-06.txt, IETF work in progress, May 2001. [21] B. Aboba, G. Zorn, "Criteria for Evaluating Roaming Protocols", RFC 2477, January 1999. [22] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. 6. Acknowledgements The authors would like to thank David Battle for his participation and suggestions in designing the table structures. 7. Security Considerations There are no management objects defined in this MIB that have a MAX- ACCESS clause of read-write and/or read-create. So, if this MIB is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB via direct SNMP SET operations. There are a number of managed objects in this MIB that may contain sensitive information. These are: diameterHostAddress, diameterPeerServerAddress, diameterPeerIpAddress, This can be used to determine the address of the Diameter host server, peer server, etc with which the servers are communicating. This information could be useful in impersonating the peer server. It is thus important to control GET access to these objects and Koehler et al. [Page 33] Internet-Draft Diameter Base Protocol MIB August 2001 possibly to even encrypt the values of these object when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment. SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), there is no control as to who on the secure network is allowed to access and GET (read) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2574 [12] and the View-based Access Control Model RFC 2575 [15] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 8. Authors' Addresses Jay Koehler Cisco Systems, Inc. 10850 Murdock Road Knoxville, TN 37932 Phone: 865-671-0429 EMail: jkoehler@cisco.com Mark Eklund Cisco Systems, Inc. 10850 Murdock Road Knoxville, TN 37932 Phone: 865-671-6255 Email: meklund@cisco.com Hai Li Cisco Systems, Inc. 10850 Murdock Road Knoxville, TN 37932 Phone: 865-777-1563 EMail: haili@cisco.com 9. Full Copyright Statement Koehler et al. [Page 34] Internet-Draft Diameter Base Protocol MIB August 2001 Copyright (C) The Internet Society (2001). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implmentation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Koehler et al. [Page 35]