DIAMETER-BASE-PROTOCOL-MIB
AI MIB Summary
The DIAMETER-BASE-PROTOCOL-MIB enables monitoring of Diameter protocol entities by exposing session state transitions, message transmission and reception counters, and error statistics for Diameter agents and clients. This module facilitates the tracking of connection establishment failures, retransmission rates, and protocol state machine health within Diameter-based authentication, authorization, and accounting (AAA) infrastructures.
The MIB module for entities implementing the Diameter Base Protocol. Copyright (C) The Internet Society (2007). This initial version of this MIB module was published in RFC yyyy; for full legal notices see the RFC itself. Supplementary information may be available on http://www.ietf.org/copyrights/ianamib.html.
Main OID:
diameterBasePMIB.1.3.6.1.2.1.119
174
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
174 total| Object Name |
|---|
diameterBasePMIBThe MIB module for entities implementing the Diameter Base Protocol. Copyright (C) The Internet Society (2007). This initial version of this MIB module was published in RFC yyyy; for full legal notices see the RFC itself. Supplementary information may be available on http://www.ietf.org/copyrights/ianamib.html. MODULE-IDENTITY .1.3.6.1.2.1.119 |
diameterBaseProtocolMIB OBJECT IDENTIFIER .1.3.6.1.2.1.119.1 |
diameterBaseNotifications OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.0 |
dbpProtocolErrorNotifAn dbpProtocolError Notification is sent when both the following conditions are true: 1) the value of dbpProtocolErrorNotifEnabled is True(1) 2) the value of dbpPerPeerStatsProtocolErrors changes It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent must not generate more than one dbpProtocolError 'notification event' in a five second period, where a 'notification event' is the transmission of a single Notification PDU to a list of Notification destinations. If additional premanent failures occur within the five second 'throttling' period, then these notification events should be suppressed by the agent. An NMS should periodically check the value of dbpPerPeerStatsProtocolErrors to detect any missed dbpProtocolError notification events, e.g. due to throttling or transmission loss. NOTIFICATION-TYPE .1.3.6.1.2.1.119.1.0.1 |
dbpTransientFailureNotifAn dbpTransientFailure Notification is sent when both the following conditions are true: 1) the value of dbpTransientFailureNotifEnabled is True(1) 2) the value of dbpPerPeerStatsTransientFailures changes It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent must not generate more than one dbpTransientFailure 'notification event' in a five second period, where a 'notification event' is the transmission of a single notification PDU to a list of notification destinations. If additional transient failures occur within the five second 'throttling' period, then these notification events should be suppressed by the agent. An NMS should periodically check the value of dbpPerPeerStatsTransientFailures to detect any missed dbpTransientFailure notification events, e.g. due to throttling or transmission loss. NOTIFICATION-TYPE .1.3.6.1.2.1.119.1.0.2 |
dbpPermanentFailureNotifAn dbpPermanentFailure notification is sent when both the following conditions are true: 1) the value of dbpPermanentFailureNotifEnabled is True(1) 2) the value of dbpPerPeerStatsPermanentFailures changes It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent must not generate more than one dbpPermanentFailure 'notification event' in a five second period, where a 'notification event' is the transmission of a single notification PDU to a list of notification destinations. If additional premanent failures occur within the five second 'throttling' period, then these trap-events should be suppressed by the agent. An NMS should periodically check the value of dbpPerPeerStatsPermanentFailures to detect any missed dbpPermanentFailure trap-events, e.g. due to throttling or transmission loss. NOTIFICATION-TYPE .1.3.6.1.2.1.119.1.0.3 |
dbpPeerConnectionDownNotifAn dbpPeerConnectionDown notification is sent when both the following conditions are true: 1) the value of dbpPeerConnectionDownNotifEnabled is True(1) 2) dbpPerPeerStatsState changes to closed(1) It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent must not generate more than one dbpPeerConnectionDown 'notification event' in a five second period, where a 'notification event' is the transmission of a single notification PDU to a list of notification destinations. If additional 'transport down' events occur within the five second 'throttling' period, then these trap-events should be suppressed by the agent. NOTIFICATION-TYPE .1.3.6.1.2.1.119.1.0.4 |
dbpPeerConnectionUpNotifAn dbpPeerConnectionUp notification is sent when both thefollowing conditions are true: 1) the value of dbpPeerConnectionUpNotifEnabled is True(1) 2) the value of dbpPerPeerStatsState changes to either rOpen(6)or iOpen(7) It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent must not generate more than one dbpPeerConnectionDown 'notification event' in a five second period, where a 'notification event' is the transmission of a single notification PDU to a list of notification destinations. If additional 'transport down' events occur within the five second 'throttling' period, then these trap-events should be suppressed by the agent. NOTIFICATION-TYPE .1.3.6.1.2.1.119.1.0.5 |
diameterBaseObjects OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.1 |
dbpLocalCfgs OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.1.1 |
dbpLocalIdThe implementation-specific identification string for the Diameter software in use on the system; for example: 'diameterd'ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.119.1.1.1.1 |
dbpLocalIpAddrTableThe table listing the Diameter local host's IP Addresses. SEQUENCE OF DbpLocalIpAddrEntry .1.3.6.1.2.1.119.1.1.1.2 |
dbpLocalIpAddrEntryA row entry representing a Diameter local host IP Address. DbpLocalIpAddrEntry .1.3.6.1.2.1.119.1.1.1.2.1 |
dbpLocalIpAddrIndexA number uniquely identifying the number of IP Addresses supported by this Diameter host. Unsigned32 (1..4294967295 ) .1.3.6.1.2.1.119.1.1.1.2.1.1 |
dbpLocalIpAddrTypeThe type of internet address stored in dbpLocalIpAddress.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.119.1.1.1.2.1.2 |
dbpLocalIpAddressThe IP-Address of the host, which is of the type specified in dbpLocalIpAddrType.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.119.1.1.1.2.1.3 |
dbpLocalTcpListenPortDiameter TCP 'listen' port.ro Unsigned32 .1.3.6.1.2.1.119.1.1.1.3 |
dbpLocalSctpListenPortDiameter SCTP 'listen' port.ro Unsigned32 .1.3.6.1.2.1.119.1.1.1.4 |
dbpLocalOriginHostThis object represents the Local Origin Host.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.119.1.1.1.5 |
dbpLocalRealmThis object represents the Local Realm Name.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.119.1.1.1.6 |
dbpLocalApplicationsTableThe table listing the Diameter applications supported by this server. SEQUENCE OF DbpLocalApplicationsEntry .1.3.6.1.2.1.119.1.1.1.7 |
dbpLocalApplicationsEntryA row entry representing a Diameter application on this server. DbpLocalApplicationsEntry .1.3.6.1.2.1.119.1.1.1.7.1 |
dbpLocalApplicationsIndexA number uniquely identifying a supported Diameter application. Upon reload, dbpLocalApplIndex values may be changed. Unsigned32 ( 1..4294967295 ) .1.3.6.1.2.1.119.1.1.1.7.1.1 |
dbpLocalApplStorageTypeThe storage type for this conceptual row. None of the columnar objects is writable when the conceptual row is permanent.rw StorageType (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.1.7.1.2 |
dbpLocalApplicationsStatusThe status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the cdsgStatus column is 'notReady'. In particular, a newly created row cannot be made active until the corresponding dbpLocalApplIndex has been set. dbpLocalApplIndex may not be modified while the value of this object is active(1): An attempt to set these objects while the value of dbpLocalApplStatus is active(1) will result in an inconsistentValue error. Entries in this table with dbpLocalApplStatus equal to active(1) remain in the table until destroyed. Entries in this table with dbpLocalApplStatus equal to values other than active(1) will be destroyed after timeout (5 minutes).rw RowStatus (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.1.7.1.3 |
dbpAppAdvToPeerTableThe table listing the applications advertised by this host to each peer and the types of service supported: accounting, authentication or both. SEQUENCE OF DbpAppAdvToPeerEntry .1.3.6.1.2.1.119.1.1.1.8 |
dbpAppAdvToPeerEntryA row entry representing a discovered or configured Diameter peer server. DbpAppAdvToPeerEntry .1.3.6.1.2.1.119.1.1.1.8.1 |
dbpAppAdvToPeerVendorIdThe IANA Enterprise Code value assigned to the vendor of the Diameter device. Unsigned32 ( 1..4294967295 ) .1.3.6.1.2.1.119.1.1.1.8.1.1 |
dbpAppAdvToPeerIndexA number uniquely identifying a Diameter application advertised as supported by this host to each peer. Upon reload, dbpAppAdvToPeerIndex values may be changed Unsigned32 ( 1..4294967295 ) .1.3.6.1.2.1.119.1.1.1.8.1.2 |
dbpAppAdvToPeerServicesThe type of services supported for each application, accounting, authentication or both.ro Enumeration .1.3.6.1.2.1.119.1.1.1.8.1.3 |
dbpAppAdvToPeerStorageTypeThe storage type for this conceptual row. None of the objects are writable when the conceptual row is permanent.rw StorageType (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.1.8.1.4 |
dbpAppAdvToPeerStatusStatus of the entry: creating the entry causes the application to be advertised, destroying the entry ceases advertisement.rw RowStatus (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.1.8.1.5 |
dbpLocalStats OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.1.2 |
dbpLocalStatsTotalMessagesInThe total number of Diameter Base Protocol messages received.ro Counter32 .1.3.6.1.2.1.119.1.1.2.1 |
dbpLocalStatsTotalMessagesOutThe total number of Diameter Base Protocol messages transmitted.ro Counter32 .1.3.6.1.2.1.119.1.1.2.2 |
dbpLocalStatsTotalUpTimeThis object represents the total time this Diameter server has been up until now.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.2.1.119.1.1.2.3 |
dbpLocalResetTimeIf the server keeps 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.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.2.1.119.1.1.2.4 |
dbpLocalConfigResetStatus/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; reset(2) - command to reinitialize server state; initializing(3) - server (re)initializing; running(4) - server currently running.rw Enumeration .1.3.6.1.2.1.119.1.1.2.5 |
dbpPeerCfgs OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.1.3 |
dbpPeerTableThe table listing information regarding the discovered or configured Diameter peer servers. SEQUENCE OF DbpPeerEntry .1.3.6.1.2.1.119.1.1.3.1 |
dbpPeerEntryA row entry representing a discovered or configured Diameter peer server. DbpPeerEntry .1.3.6.1.2.1.119.1.1.3.1.1 |
dbpPeerIndexA number uniquely identifying each Diameter peer with which the host server communicates. Upon reload, dbpPeerIndex values may be changed. Unsigned32 .1.3.6.1.2.1.119.1.1.3.1.1.1 |
dbpPeerIdThe server identifier for the Diameter peer. It must be unique and non-empty.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.119.1.1.3.1.1.2 |
dbpPeerPortConnectThe connection port this server used to connect to the Diameter peer. If there is no active connection, this value will be zero(0).ro Unsigned32 .1.3.6.1.2.1.119.1.1.3.1.1.3 |
dbpPeerPortListenThe port the server is listening on.ro Unsigned32 .1.3.6.1.2.1.119.1.1.3.1.1.4 |
dbpPeerProtocolThe transport protocol (tcp/sctp) the Diameter peer is using.ro Enumeration .1.3.6.1.2.1.119.1.1.3.1.1.5 |
dbpPeerSecurityThe security the Diameter peer is using. other(1) - Unknown Security Protocol tls(2) - Transport Layer Security Protocol ipsec(3) - Internet Protocol Securityro Enumeration .1.3.6.1.2.1.119.1.1.3.1.1.6 |
dbpPeerFirmwareRevisionFirmware revision of peer. If no firmware revision, the revision of the Diameter software module may be reported instead.ro Unsigned32 .1.3.6.1.2.1.119.1.1.3.1.1.7 |
dbpPeerStorageTypeThe storage type for this conceptual row. Only the dbpPeerPortListen object is writable when the conceptual row is permanent.rw StorageType (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.3.1.1.8 |
dbpPeerStatusStatus of the peer entry: creating the entry enables the peer, destroying the entry disables the peer.rw RowStatus (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.3.1.1.9 |
dbpPeerIpAddrTableThe table listing the Diameter peer IP addresses. SEQUENCE OF DbpPeerIpAddrEntry .1.3.6.1.2.1.119.1.1.3.2 |
dbpPeerIpAddrEntryA row entry representing a peer Diameter server. DbpPeerIpAddrEntry .1.3.6.1.2.1.119.1.1.3.2.1 |
dbpPerrIpAddressIndexA number uniquely identifying the number of IP Addresses supported by all Diameter peers. Unsigned32 .1.3.6.1.2.1.119.1.1.3.2.1.1 |
dbpPeerIpAddressTypeThe type of address stored in diameterPeerIpAddress.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.119.1.1.3.2.1.2 |
dbpPeerIpAddressThe active IP Address(es) used for connections.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.119.1.1.3.2.1.3 |
dbpAppAdvFromPeerTableThe table listing the applications advertised by each peer to this host and the types of service supported: accounting, authentication or both. SEQUENCE OF DbpAppAdvFromPeerEntry .1.3.6.1.2.1.119.1.1.3.3 |
dbpAppAdvFromPeerEntryA row entry representing a discovered or configured Diameter peer server. DbpAppAdvFromPeerEntry .1.3.6.1.2.1.119.1.1.3.3.1 |
dbpAppAdvFromPeerVendorIdThe IANA Enterprise Code value assigned to the vendor of the Diameter application. Unsigned32 (1..4294967295 ) .1.3.6.1.2.1.119.1.1.3.3.1.1 |
dbpAppAdvFromPeerIndexA number uniquely identifying the applications advertised as supported from each Diameter peer. Unsigned32 (1..4294967295 ) .1.3.6.1.2.1.119.1.1.3.3.1.2 |
dbpAppAdvFromPeerTypeThe type of services supported for each application, accounting, authentication or both. acct(1) - accounting auth(2) - authentication both(3) - both accounting and authentication.ro Enumeration .1.3.6.1.2.1.119.1.1.3.3.1.3 |
dbpPeerVendorTableThe table listing the Vendor IDs supported by the peer. SEQUENCE OF DbpPeerVendorEntry .1.3.6.1.2.1.119.1.1.3.4 |
dbpPeerVendorEntryA row entry representing a Vendor ID supported by the peer. DbpPeerVendorEntry .1.3.6.1.2.1.119.1.1.3.4.1 |
dbpPeerVendorIndexA number uniquely identifying the Vendor ID supported by the peer. Upon reload, dbpPeerVendorIndex values may be changed. Unsigned32 (1..4294967295 ) .1.3.6.1.2.1.119.1.1.3.4.1.1 |
dbpPeerVendorIdThe active vendor ID used for peer connections. diameterVendorIetf(0) -- IETF diameterVendor3gpp(10415) - 3GPPrw Enumeration .1.3.6.1.2.1.119.1.1.3.4.1.2 |
dbpPeerVendorStorageTypeThe storage type for this conceptual row. None of the objects are writable when the conceptual row is permanent.rw StorageType (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.3.4.1.3 |
dbpPeerVendorRowStatusThe status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the dbpPeerVendorRowStatus column is 'notReady'. In particular, a newly created row cannot be made active until the corresponding dbpPeerVendorId has been set. Also, a newly created row cannot be made active until the corresponding 'dbpPeerIndex' has been set. dbpPeerVendorId may not be modified while the value of this object is active(1): An attempt to set these objects while the value of dbpPeerVendorRowStatus is active(1) will result in an inconsistentValue error. Entries in this table with dbpPeerVendorRowStatus equal to active(1) remain in the table until destroyed. Entries in this table with dbpPeerVendorRowStatus equal to values other than active(1) will be destroyed after timeout (5 minutes).rw RowStatus (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.3.4.1.4 |
dbpPeerStats OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.1.4 |
dbpPerPeerStatsTableThe table listing the Diameter peer statistics. SEQUENCE OF DbpPerPeerStatsEntry .1.3.6.1.2.1.119.1.1.4.1 |
dbpPerPeerStatsEntryA row entry representing a Diameter peer. DbpPerPeerStatsEntry .1.3.6.1.2.1.119.1.1.4.1.1 |
dbpPerPeerStatsStateConnection state in the Peer State Machine of the peer with which this Diameter server is communicating. closed - Connection closed with this peer. waitConnAck - Waiting for an acknowledgment from this peer. waitICea - Waiting for a Capabilities-Exchange- Answer from this peer. elect - When the peer and the server are both trying to bring up a connection with each other at the same time. An election process begins which determines which socket remains open. waitReturns - Waiting for election returns. r-open - Responder transport connection is used for communication. i-open - Initiator transport connection is used for communication. closing - Actively closing and doing cleanup.ro Enumeration .1.3.6.1.2.1.119.1.1.4.1.1.1 |
dbpPerPeerStatsStateDurationPeer state duration.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.2.1.119.1.1.4.1.1.2 |
dbpPerPeerStatsLastDiscCauseThe last cause for a peers disconnection. rebooting - A scheduled reboot is imminent. busy - The peer's internal resources are constrained, and it has determined that the transport connection needs to be shutdown. doNotWantToTalk - The peer has determined that it does not see a need for the transport connection to exist, since it does not expect any messages to be exchanged in the foreseeable future. electionLost - The peer has determined that it has lost the election process and has therefore disconnected the transport connection.ro Enumeration .1.3.6.1.2.1.119.1.1.4.1.1.3 |
dbpPerPeerStatsWhoInitDisconnectDid the host or peer initiate the disconnect? host - If this server initiated the disconnect. peer - If the peer with which this server was connected initiated the disconnect.ro Enumeration .1.3.6.1.2.1.119.1.1.4.1.1.4 |
dbpPerPeerStatsDWCurrentStatusokay - Indicates the connection is presumed working. suspect - Indicates the connection is possibly congested or down. down - The peer is no longer reachable, causing the transport connection to be shutdown. reopen - Three watchdog messages are exchanged with accepted round trip times, and the connection to the peer is considered stabilized.ro Enumeration .1.3.6.1.2.1.119.1.1.4.1.1.5 |
dbpPerPeerStatsTimeoutConnAtmptsIf there is no transport connection with a peer, this is the number of times the server attempts to connect to that peer. This is reset on disconnection.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.6 |
dbpPerPeerStatsASRsInAbort-Session-Request messages received from the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.7 |
dbpPerPeerStatsASRsOutAbort-Session-Request messages sent to the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.8 |
dbpPerPeerStatsASAsInNumber of Abort-Session-Answer messages received from the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.9 |
dbpPerPeerStatsASAsOutNumber of Abort-Session-Answer messages sent to the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.10 |
dbpPerPeerStatsACRsInNumber of Accounting-Request messages received from the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.11 |
dbpPerPeerStatsACRsOutNumber of Accounting-Request messages sent to the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.12 |
dbpPerPeerStatsACAsInNumber of Accounting-Answer messages received from the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.13 |
dbpPerPeerStatsACAsOutNumber of Accounting-Answer messages sent to the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.14 |
dbpPerPeerStatsCERsInNumber of Capabilities-Exchange-Request messages received from the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.15 |
dbpPerPeerStatsCERsOutNumber of Capabilities-Exchange-Request messages sent to the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.16 |
dbpPerPeerStatsCEAsInNumber of Capabilities-Exchange-Answer messages received from the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.17 |
dbpPerPeerStatsCEAsOutNumber of Capabilities-Exchange-Answer messages sent to the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.18 |
dbpPerPeerStatsDWRsInNumber of Device-Watchdog-Request messages received from the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.19 |
dbpPerPeerStatsDWRsOutNumber of Device-Watchdog-Request messages sent to the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.20 |
dbpPerPeerStatsDWAsInNumber of Device-Watchdog-Answer messages received from the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.21 |
dbpPerPeerStatsDWAsOutNumber of Device-Watchdog-Answer messages sent to the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.22 |
dbpPerPeerStatsDPRsInNumber of Disconnect-Peer-Request messages received.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.23 |
dbpPerPeerStatsDPRsOutNumber of Disconnect-Peer-Request messages sent.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.24 |
dbpPerPeerStatsDPAsInNumber of Disconnect-Peer-Answer messages received.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.25 |
dbpPerPeerStatsDPAsOutNumber of Disconnect-Peer-Answer messages sent.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.26 |
dbpPerPeerStatsRARsInNumber of Re-Auth-Request messages received.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.27 |
dbpPerPeerStatsRARsOutNumber of Re-Auth-Request messages sent.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.28 |
dbpPerPeerStatsRAAsInNumber of Re-Auth-Answer messages received.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.29 |
dbpPerPeerStatsRAAsOutNumber of Re-Auth-Answer messages sent.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.30 |
dbpPerPeerStatsSTRsInNumber of Session-Termination-Request messages received from the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.31 |
dbpPerPeerStatsSTRsOutNumber of Session-Termination-Request messages sent to the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.32 |
dbpPerPeerStatsSTAsInNumber of Session-Termination-Answer messages received from the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.33 |
dbpPerPeerStatsSTAsOutNumber of Session-Termination-Answer messages sent to the peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.34 |
dbpPerPeerStatsDWReqTimerDevice-Watchdog Request Timer, which is the interval between packets sent to peers.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.2.1.119.1.1.4.1.1.35 |
dbpPerPeerStatsRedirectEventsRedirect Event count, which is the number of redirects sent from a peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.36 |
dbpPerPeerStatsAccDupRequestsThe number of duplicate Diameter Accounting-Request packets received.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.37 |
dbpPerPeerStatsMalformedReqstsThe number of malformed Diameter packets received.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.38 |
dbpPerPeerStatsAccsNotRecordedThe number of Diameter Accounting-Request packets which were received and responded to but not recorded.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.39 |
dbpPerPeerStatsAccRetransThe number of Diameter Accounting-Request packets retransmitted to this Diameter server.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.40 |
dbpPerPeerStatsTotalRetransThe number of Diameter packets retransmitted to this Diameter server, not to include Diameter Accounting-Request packets retransmitted.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.41 |
dbpPerPeerStatsAccPendReqstsOutThe 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.ro Gauge32 .1.3.6.1.2.1.119.1.1.4.1.1.42 |
dbpPerPeerStatsAccReqstsDroppedThe number of Accounting-Requests to this server that have been dropped.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.43 |
dbpPerPeerStatsHByHDropMessagesAn answer message that is received with an unknown Hop-by-Hop Identifier. Does not include Accounting Requests dropped.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.44 |
dbpPerPeerStatsEToEDupMessagesDuplicate answer messages that are to be locally consumed. Does not include duplicate Accounting Requests received.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.45 |
dbpPerPeerStatsUnknownTypesThe number of Diameter packets of unknown type which were received.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.46 |
dbpPerPeerStatsProtocolErrorsNumber of protocol errors returned to peer, but not including redirects.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.47 |
dbpPerPeerStatsTransientFailuresTransient Failure count.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.48 |
dbpPerPeerStatsPermanentFailuresNumber of permanent failures returned to peer.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.49 |
dbpPerPeerStatsTransportDownNumber of unexpected transport failures.ro Counter32 .1.3.6.1.2.1.119.1.1.4.1.1.50 |
dbpRealmCfgs OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.1.5 |
dbpRealmKnownPeersTableThe table listing the Diameter Realms and known peers. SEQUENCE OF DbpRealmKnownPeersEntry .1.3.6.1.2.1.119.1.1.5.1 |
dbpRealmKnownPeersEntryA row entry representing a Diameter Realm and known peers. DbpRealmKnownPeersEntry .1.3.6.1.2.1.119.1.1.5.1.1 |
dbpRealmKnownPeersIndexA sequential identifier number. Unsigned32 .1.3.6.1.2.1.119.1.1.5.1.1.1 |
dbpRealmKnownPeersThe index of the peer this realm knows about. This is an ordered list, where the ordering signifies the order in which the peers are tried. Same as the dbpPeerIndexro Unsigned32 .1.3.6.1.2.1.119.1.1.5.1.1.2 |
dbpRealmKnownPeersChosenHow the realm chooses which peer to send packets to. roundRobin - The peer used for each transaction is selected based on the order in which peers are configured. loadBalance - The peer used for each transaction is based on the load metric (maybe implementation dependent) of all peers defined for the realm, with the least loaded server selected first. firstPreferred - The first defined server is always used for transactions unless failover occurs. mostRecentFirst - The most recently used server is used first for each transaction.ro Enumeration .1.3.6.1.2.1.119.1.1.5.1.1.3 |
dbpRealmStats OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.1.6 |
dbpRealmMessageRouteTableThe table listing the Diameter Realm-based Message Route information. SEQUENCE OF DbpRealmMessageRouteEntry .1.3.6.1.2.1.119.1.1.6.1 |
dbpRealmMessageRouteEntryA row entry representing a Diameter Realm Based Message Route server. DbpRealmMessageRouteEntry .1.3.6.1.2.1.119.1.1.6.1.1 |
dbpRealmMessageRouteIndexA number uniquely identifying each Realm. Unsigned32 .1.3.6.1.2.1.119.1.1.6.1.1.1 |
dbpRealmMessageRouteRealmRealm namero SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.119.1.1.6.1.1.2 |
dbpRealmMessageRouteAppApplication id used to route packets to this realm.ro Unsigned32 .1.3.6.1.2.1.119.1.1.6.1.1.3 |
dbpRealmMessageRouteTypeThe types of service supported for each realm application: accounting, authentication or both.ro Enumeration .1.3.6.1.2.1.119.1.1.6.1.1.4 |
dbpRealmMessageRouteActionThe action is used to identify how a message should be treated based on the realm, application and type. local - Diameter messages that resolve to a route entry with the Local Action set to Local can be satisfied locally, and do not need to be routed to another server. relay - All Diameter messages that fall within this category MUST be routed to a next-hop server, without modifying any non-routing AVPs. proxy - All Diameter messages that fall within this category MUST be routed to a next-hop server. redirect - Diameter messages that fall within this category MUST have the identity of the home Diameter server(s) appended, and returned to the sender of the message.ro Enumeration .1.3.6.1.2.1.119.1.1.6.1.1.5 |
dbpRealmMessageRouteACRsInNumber of Accounting-Request messages received from the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.6 |
dbpRealmMessageRouteACRsOutNumber of Accounting-Request messages sent to the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.7 |
dbpRealmMessageRouteACAsInNumber of Accounting-Answer messages received from the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.8 |
dbpRealmMessageRouteACAsOutNumber of Accounting-Answer messages sent to the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.9 |
dbpRealmMessageRouteRARsInNumber of Re-Auth-Request messages received from the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.10 |
dbpRealmMessageRouteRARsOutNumber of Re-Auth-Request messages sent to the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.11 |
dbpRealmMessageRouteRAAsInNumber of Re-Auth-Answer messages received from the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.12 |
dbpRealmMessageRouteRAAsOutNumber of Re-Auth-Answer messages sent to the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.13 |
dbpRealmMessageRouteSTRsInNumber of Session-Termination-Request messages received from the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.14 |
dbpRealmMessageRouteSTRsOutNumber of Session-Termination-Request messages sent to the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.15 |
dbpRealmMessageRouteSTAsInNumber of Session-Termination-Answer messages received from the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.16 |
dbpRealmMessageRouteSTAsOutNumber of Session-Termination-Answer messages sent to the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.17 |
dbpRealmMessageRouteASRsInNumber of Abort-Session-Request messages received from the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.18 |
dbpRealmMessageRouteASRsOutNumber of Abort-Session-Request messages sent to the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.19 |
dbpRealmMessageRouteASAsInNumber of Abort-Session-Answer messages received from the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.20 |
dbpRealmMessageRouteASAsOutNumber of Abort-Session-Answer messages sent to the realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.21 |
dbpRealmMessageRouteAccRetransThe number of Diameter accounting packets retransmitted to this realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.22 |
dbpRealmMessageRouteAccDupReqstsThe number of duplicate Diameter accounting packets sent to this realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.23 |
dbpRealmMessageRoutePendReqstsOutThe 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.ro Gauge32 .1.3.6.1.2.1.119.1.1.6.1.1.24 |
dbpRealmMessageRouteReqstsDropThe number of requsts dropped by this realm.ro Counter32 .1.3.6.1.2.1.119.1.1.6.1.1.25 |
dbpNotifCfgs OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.1.7 |
dbpProtocolErrorNotifEnabledSetting the value of this object to True(1) enables the dbpProtocolErrorNotif notification.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.7.1 |
dbpTransientFailureNotifEnabledSetting the value of this object to True(1) enables the dbpTransientFailure Notification.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.7.2 |
dbpPermanentFailureNotifEnabledSetting the value of this object to True(1) enables the dbpPermanentFailure notification.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.7.3 |
dbpPeerConnectionDownNotifEnabledSetting the value of this object to True(1) enables the dbpPeerConnectionDown notification.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.7.4 |
dbpPeerConnectionUpNotifEnabledSetting the value of this object to True(1) enables the dbpPeerConnectionUp notification.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.119.1.1.7.5 |
diameterBaseConform OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.2 |
diameterBaseProtocolMIBCompliances OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.2.1 |
diameterBaseProtocolComplianceThe compliance statement for Diameter Base Protocol entities. Unknown .1.3.6.1.2.1.119.1.2.1.1 |
diameterBaseProtocolMIBGroups OBJECT IDENTIFIER .1.3.6.1.2.1.119.1.2.2 |
dbpLocalCfgGroupA collection of objects providing configuration common to the server. Unknown .1.3.6.1.2.1.119.1.2.2.1 |
dbpPeerCfgGroupA collection of objects providing configuration of the Diameter peers. Unknown .1.3.6.1.2.1.119.1.2.2.2 |
dbpPeerStatsGroupA collection of objects providing statistics of the Diameter peers. Unknown .1.3.6.1.2.1.119.1.2.2.3 |
dbpNotificationsGroupThe set of notifications which an agent is required to implement. Unknown .1.3.6.1.2.1.119.1.2.2.4 |
dbpNotifCfgGroupA collection of objects providing configuration for base protocol notifications. Unknown .1.3.6.1.2.1.119.1.2.2.5 |
dbpLocalCfgSkippedGroupA collection of objects providing configuration common to the server. Unknown .1.3.6.1.2.1.119.1.2.2.6 |
dbpLocalStatsSkippedGroupA collection of objects providing statistics common to the server. Unknown .1.3.6.1.2.1.119.1.2.2.7 |
dbpPeerCfgSkippedGroupA collection of objects providing configuration for Diameter peers. Unknown .1.3.6.1.2.1.119.1.2.2.8 |
dbpPeerStatsSkippedGroupA collection of objects providing statistics of Diameter peers. Unknown .1.3.6.1.2.1.119.1.2.2.9 |
dbpRealmCfgSkippedGroupA collection of objects providing configuration for realm message routing. Unknown .1.3.6.1.2.1.119.1.2.2.10 |
dbpRealmStatsSkippedGroupA collection of objects providing statistics of realm message routing. Unknown .1.3.6.1.2.1.119.1.2.2.11 |