draft-ietf-dime-diameter-base-protocol-mib-02.txt   draft-ietf-dime-diameter-base-protocol-mib-03.txt 
Network Working Group G. Zorn, Ed. Network Working Group G. Zorn
Internet-Draft Network Zen Internet-Draft Network Zen
Intended status: Informational S. Comerica Intended status: Standards Track S. Comerica
Expires: January 28, 2010 Cisco Systems Expires: May 13, 2010 Cisco Systems
July 27, 2009 November 9, 2009
Diameter Base Protocol MIB Diameter Base Protocol MIB
draft-ietf-dime-diameter-base-protocol-mib-02.txt draft-ietf-dime-diameter-base-protocol-mib-03.txt
Abstract
Along with providing support for certain basic authentication,
authorization and accounting functions, the Diameter protocol is
designed to provide a framework for AAA applications.
This document defines the Management Information Base (MIB) module
which describes the minimum set of objects needed to manage an
implementation of the Diameter protocol.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 28, 2010. This Internet-Draft will expire on May 13, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
Along with providing support for certain basic authentication, described in the BSD License.
authorization and accounting functions, the Diameter protocol is
designed to provide a framework for AAA applications.
This document defines the Management Information Base (MIB) module This document may contain material from IETF Documents or IETF
which describes the minimum set of objects needed to manage an Contributions published or made publicly available before November
implementation of the Diameter protocol. 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . . 3 1. The Internet-Standard Management Framework . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Diameter Base Protocol MIB Definitions . . . . . . . . . . . . 3 4. Diameter Base Protocol MIB Definitions . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47
6. Security Considerations . . . . . . . . . . . . . . . . . . . 48 6. Security Considerations . . . . . . . . . . . . . . . . . . . 47
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 49 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 48
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 49 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48
9.1. Normative References . . . . . . . . . . . . . . . . . . . 50 9.1. Normative References . . . . . . . . . . . . . . . . . . . 48
9.2. Informative References . . . . . . . . . . . . . . . . . . 50 9.2. Informative References . . . . . . . . . . . . . . . . . . 49
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 51 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 49
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 3, line 30 skipping to change at page 4, line 30
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Overview 3. Overview
This MIB defines objects supporting the management of the Diameter This MIB defines objects supporting the management of the Diameter
base protocol as described in RFC 3588 [RFC3588]. Objects related to base protocol as defined in RFC 3588 [RFC3588]. Objects related to
Diameter applications are defined in separate documents. Diameter applications are defined in separate documents.
4. Diameter Base Protocol MIB Definitions 4. Diameter Base Protocol MIB Definitions
DIAMETER-BASE-PROTOCOL-MIB DEFINITIONS ::= BEGIN DIAMETER-BASE-PROTOCOL-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- [RFC4001]
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
Counter32, Counter32,
Unsigned32, Unsigned32,
Gauge32, Gauge32,
TimeTicks TimeTicks,
mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411] FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
NOTIFICATION-GROUP, NOTIFICATION-GROUP,
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
RowStatus, RowStatus,
TruthValue, TruthValue,
StorageType StorageType
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- [RFC2579]
skipping to change at page 4, line 14 skipping to change at page 5, line 16
FROM SNMP-FRAMEWORK-MIB -- [RFC3411] FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
NOTIFICATION-GROUP, NOTIFICATION-GROUP,
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
RowStatus, RowStatus,
TruthValue, TruthValue,
StorageType StorageType
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- [RFC2579]
DiameterBasePMIB MODULE-IDENTITY diameterBaseProtocolMIB MODULE-IDENTITY
LAST-UPDATED "200906170000Z" -- 17 June 2009 LAST-UPDATED "200802100000Z" -- 10 February 2008
ORGANIZATION "IETF dime Working Group." ORGANIZATION "IETF dime Working Group."
CONTACT-INFO CONTACT-INFO
"Glen Zorn "Glen Zorn
Network Zen Network Zen
1310 East Thomas Street 1310 East Thomas Street
Seattle, WA 98102 Seattle, WA 98102
USA USA
Phone: +1 (206) 377 9035
Email: gwz@net-zen.net" Email: gwz@net-zen.net"
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the "The MIB module for entities implementing the
Diameter Base Protocol. Diameter Base Protocol.
Copyright (C) The IETF Trust (2009). This initial Copyright (C) The IETF Trust (2008). This initial
version of this MIB module was published in RFC yyyy; version of this MIB module was published in RFC yyyy;
for full legal notices see the RFC itself. Supplementary for full legal notices see the RFC itself. Supplementary
information may be available on information may be available on
http://www.ietf.org/copyrights/ianamib.html." http://www.ietf.org/copyrights/ianamib.html."
-- RFC Ed.: replace yyyy with actual RFC number and remove this note -- RFC Ed.: replace yyyy with actual RFC number and remove this note
REVISION "200906170000Z" -- 17 June 2009 REVISION "200802100000Z" -- 10 February 2008
DESCRIPTION "Initial version as published in RFC yyyy" DESCRIPTION "Initial version as published in RFC yyyy"
-- RFC Ed.: replace yyyy with actual RFC number and remove this note -- RFC Ed.: replace yyyy with actual RFC number and remove this note
::= { mib-2 119 } -- Experimental value assigned by IANA. ::= { mib-2 119 } -- Experimental value assigned by IANA.
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
diameterBaseProtocolMIB OBJECT::= { diameterMIB 1 }
diameterBaseNotifications OBJECT IDENTIFIER ::= diameterBaseNotifications OBJECT IDENTIFIER ::=
{ diameterBaseProtocolMIB 0 } { diameterBaseProtocolMIB 0 }
diameterBaseObjects OBJECT IDENTIFIER ::= diameterBaseObjects OBJECT IDENTIFIER ::=
{ diameterBaseProtocolMIB 1 } { diameterBaseProtocolMIB 1 }
diameterBaseConform OBJECT IDENTIFIER ::= diameterBaseConform OBJECT IDENTIFIER ::=
{ diameterBaseProtocolMIB 2 } { diameterBaseProtocolMIB 2 }
dbpLocalCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 1 } dbpLocalCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 1 }
dbpLocalStats OBJECT IDENTIFIER ::= { diameterBaseObjects 2 } dbpLocalStats OBJECT IDENTIFIER ::= { diameterBaseObjects 2 }
dbpPeerCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 3 } dbpPeerCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 3 }
dbpPeerStats OBJECT IDENTIFIER ::= { diameterBaseObjects 4 } dbpPeerStats OBJECT IDENTIFIER ::= { diameterBaseObjects 4 }
dbpRealmCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 5 } dbpRealmCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 5 }
dbpRealmStats OBJECT IDENTIFIER ::= { diameterBaseObjects 6 } dbpRealmStats OBJECT IDENTIFIER ::= { diameterBaseObjects 6 }
dbpNotifCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 7 } dbpNotifCfgs OBJECT IDENTIFIER ::= { diameterBaseObjects 7 }
-- Protocol Error Notifications -- Protocol Error Notifications
skipping to change at page 7, line 7 skipping to change at page 8, line 5
-- Permanent Failure Notifications -- Permanent Failure Notifications
dbpPermanentFailureNotifEnabled OBJECT-TYPE dbpPermanentFailureNotifEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Setting the value of this object to True(1) "Setting the value of this object to True(1)
enables the dbpPermanentFailure notification." enables the dbpPermanentFailure notification."
DEFVALUE { false } DEFVAL { false }
::= { dbpNotifCfgs 3 } ::= { dbpNotifCfgs 3 }
dbpPermanentFailureNotif NOTIFICATION-TYPE dbpPermanentFailureNotif NOTIFICATION-TYPE
OBJECTS { OBJECTS {
dbpPeerId, dbpPeerId,
dbpPerPeerStatsPermanentFailures dbpPerPeerStatsPermanentFailures
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An dbpPermanentFailure notification is sent when "An dbpPermanentFailure notification is sent when
skipping to change at page 18, line 29 skipping to change at page 19, line 27
configured Diameter peer server." configured Diameter peer server."
INDEX { dbpPeerIndex, INDEX { dbpPeerIndex,
dbpAppAdvToPeerVendorId, dbpAppAdvToPeerVendorId,
dbpAppAdvToPeerIndex } dbpAppAdvToPeerIndex }
::= { dbpAppAdvToPeerTable 1 } ::= { dbpAppAdvToPeerTable 1 }
DbpAppAdvToPeerEntry ::= SEQUENCE { DbpAppAdvToPeerEntry ::= SEQUENCE {
dbpAppAdvToPeerVendorId Unsigned32, dbpAppAdvToPeerVendorId Unsigned32,
dbpAppAdvToPeerIndex Unsigned32, dbpAppAdvToPeerIndex Unsigned32,
dbpAppAdvToPeerServices INTEGER, dbpAppAdvToPeerServices INTEGER,
dbpAppAppAdvToPeerStorageType StorageType, dbpAppAdvToPeerStorageType StorageType,
dbpAppAdvToPeerRowStatus RowStatus } dbpAppAdvToPeerRowStatus RowStatus }
dbpAppAdvToPeerVendorId OBJECT-TYPE dbpAppAdvToPeerVendorId OBJECT-TYPE
SYNTAX Unsigned32 ( 1..4294967295 ) SYNTAX Unsigned32 ( 1..4294967295 )
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IANA Enterprise Code value assigned to "The IANA Enterprise Code value assigned to
the vendor of the Diameter device." the vendor of the Diameter device."
::= { dbpAppAdvToPeerEntry 1 } ::= { dbpAppAdvToPeerEntry 1 }
skipping to change at page 21, line 39 skipping to change at page 22, line 39
::= { dbpPeerVendorTable 1 } ::= { dbpPeerVendorTable 1 }
DbpPeerVendorEntry ::= SEQUENCE { DbpPeerVendorEntry ::= SEQUENCE {
dbpPeerVendorIndex Unsigned32, dbpPeerVendorIndex Unsigned32,
dbpPeerVendorId Unsigned32, dbpPeerVendorId Unsigned32,
dbpPeerVendorStorageType StorageType, dbpPeerVendorStorageType StorageType,
dbpPeerVendorRowStatus RowStatus dbpPeerVendorRowStatus RowStatus
} }
dbpPeerVendorIndex OBJECT-TYPE dbpPeerVendorIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295 ) SYNTAX Unsigned32 ( 1..4294967295 )
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number uniquely identifying the Vendor "A number uniquely identifying the Vendor
ID supported by the peer. Upon reload, ID supported by the peer. Upon reload,
dbpPeerVendorIndex values may be changed." dbpPeerVendorIndex values may be changed."
::= { dbpPeerVendorEntry 1 } ::= { dbpPeerVendorEntry 1 }
dbpPeerVendorId OBJECT-TYPE dbpPeerVendorId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295 ) SYNTAX Unsigned32 (1..4294967295 )
skipping to change at page 42, line 41 skipping to change at page 43, line 45
peers defined for the realm, with peers defined for the realm, with
the least loaded server selected the least loaded server selected
first. first.
firstPreferred - The first defined server is always firstPreferred - The first defined server is always
used for transactions unless used for transactions unless
failover occurs. failover occurs.
mostRecentFirst - The most recently used server is mostRecentFirst - The most recently used server is
used first for each transaction." used first for each transaction."
::= { dbpRealmKnownPeersEntry 3 } ::= { dbpRealmKnownPeersEntry 3 }
-- -- Conformance -- dbpMIBCompliances -- Conformance
-- dbpMIBCompliances
diameterBaseProtocolMIBCompliances diameterBaseProtocolMIBCompliances
OBJECT IDENTIFIER ::= { diameterBaseConform 1 } OBJECT IDENTIFIER ::= { diameterBaseConform 1 }
diameterBaseProtocolMIBGroups diameterBaseProtocolMIBGroups
OBJECT IDENTIFIER ::= { diameterBaseConform 2 } OBJECT IDENTIFIER ::= { diameterBaseConform 2 }
-- -- Compliance Statements -- -- Compliance Statements
diameterBaseProtocolCompliance MODULE-COMPLIANCE diameterBaseProtocolCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for Diameter Base "The compliance statement for Diameter Base
Protocol entities." Protocol entities."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { dbpLocalCfgGroup, MANDATORY-GROUPS { dbpLocalCfgGroup,
dbpPeerCfgGroup, dbpPeerCfgGroup,
dbpPeerStatsGroup, dbpPeerStatsGroup,
dbpRealmCfgGroup,
dbpRealmStatsGroup,
dbpNotificationsGroup, dbpNotificationsGroup,
dbpNotifCfgGroup } dbpNotifCfgGroup }
GROUP dbpLocalCfgSkippedGroup ::= { diameterBaseProtocolMIBCompliances 1 }
DESCRIPTION
"This group is only mandatory for a system that
implements all the local config objects."
GROUP dbpLocalStatsSkippedGroup
DESCRIPTION
"This group is only mandatory for a system that
implements all the local statistics objects."
GROUP dbpPeerCfgSkippedGroup
DESCRIPTION
"This group is only mandatory for a system that
implements all the peer config objects."
GROUP dbpPeerStatsSkippedGroup
DESCRIPTION
"This group is only mandatory for a system that
implements all the peer statistic objects."
GROUP dbpRealmCfgSkippedGroup
DESCRIPTION
"This group is only mandatory for a system that
implementsall the realm config objects."
GROUP dbpPMIBRealmStatsSkippedGroup
DESCRIPTION
"This group is only mandatory for a system that
implements all the realm statistic objects."
::= { diameterBaseProtocolCompliances 1 }
-- -- Units of Conformance -- -- Units of Conformance
dbpLocalCfgGroup OBJECT-GROUP dbpLocalCfgGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dbpLocalRealm, dbpLocalRealm,
dbpLocalOriginHost, dbpLocalOriginHost,
dbpLocalVendorId, dbpLocalId,
dbpLocalVendorStorageType, dbpLocalIpAddrType,
dbpLocalVendorRowStatus dbpLocalIpAddress,
dbpLocalTcpListenPort,
dbpLocalSctpListenPort,
dbpLocalStatsTotalMessagesIn,
dbpLocalStatsTotalMessagesOut,
dbpLocalStatsTotalUpTime,
dbpLocalResetTime,
dbpLocalConfigReset,
dbpLocalApplStorageType,
dbpLocalApplRowStatus,
dbpAppAdvToPeerServices,
dbpAppAdvToPeerStorageType,
dbpAppAdvToPeerRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration common "A collection of objects providing configuration common
to the server." to the server."
::= { diameterBaseProtocolMIBGroups 1 } ::= { diameterBaseProtocolMIBGroups 1 }
dbpPeerCfgGroup OBJECT-GROUP dbpPeerCfgGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dbpPeerId, dbpPeerId,
skipping to change at page 44, line 29 skipping to change at page 45, line 19
dbpPeerPortListen, dbpPeerPortListen,
dbpPeerProtocol, dbpPeerProtocol,
dbpPeerSecurity, dbpPeerSecurity,
dbpPeerFirmwareRevision, dbpPeerFirmwareRevision,
dbpPeerStorageType, dbpPeerStorageType,
dbpPeerRowStatus, dbpPeerRowStatus,
dbpPeerIpAddressType, dbpPeerIpAddressType,
dbpPeerIpAddress, dbpPeerIpAddress,
dbpPeerVendorId, dbpPeerVendorId,
dbpPeerVendorStorageType, dbpPeerVendorStorageType,
dbpPeerVendorRowStatus dbpPeerVendorRowStatus,
dbpAppAdvFromPeerType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
of the Diameter peers." of the Diameter peers."
::= { diameterBaseProtocolMIBGroups 2 } ::= { diameterBaseProtocolMIBGroups 2 }
dbpPeerStatsGroup OBJECT-GROUP dbpPeerStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dbpPeerStatsState, dbpPerPeerStatsState,
dbpPeerStatsStateDuration, dbpPerPeerStatsStateDuration,
dbpPeerStatsLastDiscCause, dbpPerPeerStatsLastDiscCause,
dbpPeerStatsWhoInitDisconnect, dbpPerPeerStatsWhoInitDisconnect,
dbpPeerStatsDWCurrentStatus, dbpPerPeerStatsDWCurrentStatus,
dbpPeerStatsTimeoutConnAtmpts, dbpPerPeerStatsTimeoutConnAtmpts,
dbpPeerStatsASRsIn, dbpPerPeerStatsASRsIn,
dbpPeerStatsASRsOut, dbpPerPeerStatsASRsOut,
dbpPeerStatsASAsIn, dbpPerPeerStatsASAsIn,
dbpPeerStatsASAsOut, dbpPerPeerStatsASAsOut,
dbpPeerStatsACRsIn, dbpPerPeerStatsACRsIn,
dbpPeerStatsACRsOut, dbpPerPeerStatsACRsOut,
dbpPeerStatsACAsIn, dbpPerPeerStatsACAsIn,
dbpPeerStatsACAsOut, dbpPerPeerStatsACAsOut,
dbpPeerStatsCERsIn, dbpPerPeerStatsCERsIn,
dbpPeerStatsCERsOut, dbpPerPeerStatsCERsOut,
dbpPeerStatsCEAsIn, dbpPerPeerStatsCEAsIn,
dbpPeerStatsCEAsOut, dbpPerPeerStatsCEAsOut,
dbpPeerStatsDWRsIn, dbpPerPeerStatsDWRsIn,
dbpPeerStatsDWRsOut, dbpPerPeerStatsDWRsOut,
dbpPeerStatsDWAsIn, dbpPerPeerStatsDWAsIn,
dbpPeerStatsDWAsOut, dbpPerPeerStatsDWAsOut,
dbpPeerStatsDPRsIn, dbpPerPeerStatsDPRsIn,
dbpPeerStatsDPRsOut, dbpPerPeerStatsDPRsOut,
dbpPeerStatsDPAsIn, dbpPerPeerStatsDPAsIn,
dbpPeerStatsDPAsOut, dbpPerPeerStatsDPAsOut,
dbpPeerStatsRARsIn, dbpPerPeerStatsRARsIn,
dbpPeerStatsRARsOut, dbpPerPeerStatsRARsOut,
dbpPeerStatsRAAsIn, dbpPerPeerStatsRAAsIn,
dbpPeerStatsRAAsOut, dbpPerPeerStatsRAAsOut,
dbpPeerStatsSTRsIn, dbpPerPeerStatsSTRsIn,
dbpPeerStatsSTRsOut, dbpPerPeerStatsSTRsOut,
dbpPeerStatsSTAsIn, dbpPerPeerStatsSTAsIn,
dbpPeerStatsSTAsOut, dbpPerPeerStatsSTAsOut,
dbpPeerStatsDWReqTimer, dbpPerPeerStatsDWReqTimer,
dbpPeerStatsRedirectEvents, dbpPerPeerStatsRedirectEvents,
dbpPeerStatsAccDupRequests, dbpPerPeerStatsAccDupRequests,
dbpPeerStatsMalformedReqsts, dbpPerPeerStatsMalformedReqsts,
dbpPeerStatsAccsNotRecorded, dbpPerPeerStatsAccsNotRecorded,
dbpPeerStatsAccRetrans, dbpPerPeerStatsAccRetrans,
dbpPeerStatsTotalRetrans, dbpPerPeerStatsTotalRetrans,
dbpPeerStatsAccPendReqstsOut, dbpPerPeerStatsAccPendReqstsOut,
dbpPeerStatsAccReqstsDropped, dbpPerPeerStatsAccReqstsDropped,
dbpPeerStatsHByHDropMessages, dbpPerPeerStatsHByHDropMessages,
dbpPeerStatsEToEDupMessages, dbpPerPeerStatsEToEDupMessages,
dbpPeerStatsUnknownTypes, dbpPerPeerStatsUnknownTypes,
dbpPeerStatsProtocolErrors, dbpPerPeerStatsProtocolErrors,
dbpPeerStatsTransientFailures, dbpPerPeerStatsTransientFailures,
dbpPeerStatsPermanentFailures, dbpPerPeerStatsPermanentFailures,
dbpPeerStatsTransportDown dbpPerPeerStatsTransportDown,
dbpPerPeerStatsDWCurrentStatus,
dbpPerPeerStatsDWReqTimer,
dbpPerPeerStatsRedirectEvents,
dbpPerPeerStatsAccDupRequests,
dbpPerPeerStatsEToEDupMessages
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics "A collection of objects providing statistics
of the Diameter peers." of the Diameter peers."
::= { diameterBaseProtocolMIBGroups 3 } ::= { diameterBaseProtocolMIBGroups 3 }
dbpNotificationsGroup NOTIFICATION-GROUP dbpNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
dbpProtocolErrorNotif, dbpProtocolErrorNotif,
skipping to change at page 46, line 28 skipping to change at page 47, line 25
dbpPermanentFailureNotifEnabled, dbpPermanentFailureNotifEnabled,
dbpPeerConnectionDownNotifEnabled, dbpPeerConnectionDownNotifEnabled,
dbpPeerConnectionUpNotifEnabled dbpPeerConnectionUpNotifEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing configuration for
base protocol notifications." base protocol notifications."
::= { diameterBaseProtocolMIBGroups 5 } ::= { diameterBaseProtocolMIBGroups 5 }
dbpLocalCfgSkippedGroup OBJECT-GROUP dbpRealmCfgGroup OBJECT-GROUP
OBJECTS {
dbpLocalId,
dbpLocalIpAddrType,
dbpLocalIpAddress,
dbpLocalTcpListenPort,
dbpLocalSctpListenPort,
dbpLocalStatsTotalPacketsIn,
dbpLocalStatsTotalPacketsOut,
dbpLocalStatsTotalUpTime,
dbpLocalResetTime,
dbpLocalConfigReset,
dbpLocalApplStorageType,
dbpLocalApplRowStatus,
dbpAppAdvToPeerServices,
dbpAppAdvToPeerStorageType,
dbpAppAdvToPeerRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration common
to the server."
::= { diameterBaseProtocolMIBGroups 6 }
dbpLocalStatsSkippedGroup OBJECT-GROUP
OBJECTS {
dbpLocalStatsTotalPacketsIn,
dbpLocalStatsTotalPacketsOut,
dbpLocalStatsTotalUpTime,
dbpLocalResetTime,
dbpLocalConfigReset
}
STATUS current
DESCRIPTION
"A collection of objects providing statistics common
to the server."
::= { diameterBaseProtocolMIBGroups 7 }
dbpPeerCfgSkippedGroup OBJECT-GROUP
OBJECTS { cdbpAppAdvFromPeerType }
STATUS current
DESCRIPTION
"A collection of objects providing configuration for
Diameter peers."
::= { diameterBaseProtocolMIBGroups 8 }
dbpPeerStatsSkippedGroup OBJECT-GROUP
OBJECTS {
dbpPeerStatsDWCurrentStatus,
dbpPeerStatsDWReqTimer,
dbpPeerStatsRedirectEvents,
dbpPeerStatsAccDupRequests,
dbpPeerStatsEToEDupMessages
}
STATUS current
DESCRIPTION
"A collection of objects providing statistics
of Diameter peers."
::= { diameterBaseProtocolMIBGroups 9 }
dbpRealmCfgSkippedGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dbpRealmKnownPeers, dbpRealmKnownPeers,
dbpRealmKnownPeersChosen dbpRealmKnownPeersChosen
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing configuration for
realm message routing." Realm."
::= { diameterBaseProtocolMIBGroups 10 } ::= { diameterBaseProtocolMIBGroups 6 }
dbpRealmStatsSkippedGroup OBJECT-GROUP dbpRealmStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dbpRealmMessageRouteRealm, dbpRealmMessageRouteRealm,
dbpRealmMessageRouteApp, dbpRealmMessageRouteApp,
dbpRealmMessageRouteType, dbpRealmMessageRouteType,
dbpRealmMessageRouteAction, dbpRealmMessageRouteAction,
dbpRealmMessageRouteACRsIn, dbpRealmMessageRouteACRsIn,
dbpRealmMessageRouteACRsOut, dbpRealmMessageRouteACRsOut,
dbpRealmMessageRouteACAsIn, dbpRealmMessageRouteACAsIn,
dbpRealmMessageRouteACAsOut, dbpRealmMessageRouteACAsOut,
dbpRealmMessageRouteRARsIn, dbpRealmMessageRouteRARsIn,
skipping to change at page 48, line 34 skipping to change at page 48, line 18
dbpRealmMessageRouteASAsOut, dbpRealmMessageRouteASAsOut,
dbpRealmMessageRouteAccRetrans, dbpRealmMessageRouteAccRetrans,
dbpRealmMessageRouteAccDupReqsts, dbpRealmMessageRouteAccDupReqsts,
dbpRealmMessageRoutePendReqstsOut, dbpRealmMessageRoutePendReqstsOut,
dbpRealmMessageRouteReqstsDrop dbpRealmMessageRouteReqstsDrop
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics "A collection of objects providing statistics
of realm message routing." of realm message routing."
::= { diameterBaseProtocolMIBGroups 11 } ::= { diameterBaseProtocolMIBGroups 7 }
END END
5. IANA Considerations 5. IANA Considerations
IANA is requested to assign an OID under mib-2. IANA is requested to assign an OID under mib-2.
6. Security Considerations 6. Security Considerations
There are managed objects defined in this MIB that have a MAX-ACCESS There are managed objects defined in this MIB that have a MAX-ACCESS
clause of read-write and/or read-create. Such objects may be clause of read-write and/or read-create. Such objects may be
considered sensitive or vulnerable in some network environments. The considered sensitive or vulnerable in some network environments. The
support for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
There are a number of managed objects in this MIB that may contain There are several of managed objects in this MIB that may contain
sensitive information. These are: sensitive information. These are:
o diameterHostAddress o diameterHostAddress
o diameterPeerServerAddress o diameterPeerServerAddress
o diameterPeerIpAddress o diameterPeerIpAddress
These can be used to determine the address of the Diameter host, These can be used to determine the address of the Diameter host,
and/or peers with which the host is communicating. This information and/or peers with which the host is communicating. This information
skipping to change at page 49, line 49 skipping to change at page 49, line 32
7. Contributors 7. Contributors
This document is based upon and derived from work done by Jay This document is based upon and derived from work done by Jay
Koehler, Mark Eklund and Hai Li. Koehler, Mark Eklund and Hai Li.
8. Acknowledgements 8. Acknowledgements
Thanks to David Battle for his participation and suggestions in Thanks to David Battle for his participation and suggestions in
designing the table structures; Kevin Lingle, Sumanth Mithra, Tolga designing the table structures; Kevin Lingle, Sumanth Mithra, Tolga
Asveren, Tina Tsou, Mark Jones, John Loughney and Biswaranjan Panda Asveren, Tina Tsou, Mark Jones, John Loughney and Biswaranjan Panda
for reviewing the MIB and making useful suggestions; and Greg Weber for reviewing the MIB and making invaluable suggestions; and Greg
for his help in representing the MIB at IETF meetings. Weber for his help in representing the MIB at IETF meetings.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
skipping to change at page 51, line 7 skipping to change at page 50, line 38
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", STD 62, RFC 3415, Management Protocol (SNMP)", STD 62, RFC 3415,
December 2002. December 2002.
Authors' Addresses Authors' Addresses
Glen Zorn (editor) Glen Zorn
Network Zen Network Zen
1310 East Thomas Street 1310 E. Thomas Street
#306 Seattle, WA 98102
Seattle, Washington 98102
USA USA
Phone: +1 (206) 377-9035
Email: gwz@net-zen.net Email: gwz@net-zen.net
Subash Comerica Subash Comerica
Cisco Systems Cisco Systems
Global Development Centre, Prestige Waterford Global Development Centre, Prestige Waterford
No. 9 Brunton Road No. 9 Brunton Road
BGL3/MZ/ BGL3/MZ/
Bangalore, Karnataka 560025 Bangalore, Karnataka 560025
India India
Phone: +91 80 4103 6427 Phone: +91 80 4103 6427
Email: subashtc@cisco.com Email: subashtc@cisco.com
 End of changes. 40 change blocks. 
214 lines changed or deleted 147 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/