Diameter Stack Agent Input/Output Data and MIM(4.3)
Input/Output Data
The Input/Output data is the type of data an agent expects and delivers.
The agent emits and receives UDRs of the type RequestCycleUDR
.
When you have configured an error route, the agent also emits UDRs of the type DiameterErrorUDR
.
MIM
Publishes
MIM Value | Description |
---|---|
Bytes Received | This MIM parameter contains the number of received bytes from each peer in the selected Diameter Routing profile.
|
Bytes Transmitted | This MIM parameter contains the number of transmitted bytes to each peer in the selected Diameter Routing profile.
|
CEA Count | This MIM parameter contains the number of sent and received CEA (Capabilities-Exchange-Answer) commands for each peer in the selected Diameter Routing profile.
|
CER Count | This MIM parameter contains the number of sent and received CER (Capabilities-Exchange-Request) commands for each peer in the selected Diameter Routing profile.
|
Communication Failure Network Layer | This MIM parameter contains the number of connection problems detected on network level.
|
Communication Failure Protocol Layer | This MIM parameter contains the number of connection problems detected on protocol level.
|
Diameter Too Busy Count | This MIM parameter contains the number of sent Diameter Too Busy responses. The MIM value is reset each time the MIM is read.
|
Diameter Too Busy Total Count | This MIM parameter contains the number of Diameter Too Busy responses sent, since Workflow start.
|
DPA Count | This MIM parameter contains the number of sent and received DPA (Disconnect-Peer-Answer) commands for each peer in the selected Diameter Routing profile.
|
DPR Count | This MIM parameter contains the number of sent and received DPR (Disconnect-Peer-Request) commands for each peer in the selected Diameter Routing profile.
|
DWA Count | This MIM parameter contains the number of sent and received DWA (Device-Watchdog-Answer) commands for each peer in the selected Diameter Routing profile.
|
DWR Count | This MIM parameter contains the number of sent and received DWR (Device-Watchdog-Request) commands for each peer in the selected Diameter Routing profile.
|
Incoming Messages | This MIM parameter contains the number of received messages.
|
Origin State Id | This MIM parameter contains a value that is incremented in the initialize workflow execution state. It is used for populating the AVP Origin-State-Id.
To amend this counter, see Diameter Functions(4.3). |
Outgoing Messages | This MIM parameter contains the number of sent messages.
|
Peer Status | This MIM parameter contains the status of a Peer. The first string is the hostname and the second string is the status for that peer. Status can be any of the following: OKAY, SUSPECT, DOWN, REOPEN, or INITIAL. These are the watchdog states as de fi ned in RFC3539. The value of Peer Status is always INITIAL in the initialize work fl ow execution state. |
Peer Round Trip Latency Avg | This MIM parameter contains the average round trip latency to peer, calculated (in milliseconds) over the last 1000 received records. |
Peer Round Trip Latency Max | This MIM parameter contains the maximum round trip latency to peer since Workflow start. |
Peer Round Trip Latency Min | This MIM parameter contains the minimum round trip latency to peer since Workflow start.
|
Peer Status | This MIM parameter contains the state of a peer connection. The first string is the hostname and the second string is the state. The state can be any of the following: OKAY, SUSPECT, DOWN, REOPEN, or INITIAL. These are The value of
|
Realm Routing Table | This MIM parameter contains the realm routing table of the Diameter Stack
Note!This MIM value only contains realms that have static peers, i e not dynamically discovered via DNS lookups. For an example of how to use this MIM value, see the section, To Read the Realm Routing Table in APL, in Diameter Routing (4.3) profile. |
Records in decoder queue | This MIM parameter contains the current number of records in the queue for decoding.
|
Rejected Messages | This MIM parameter contains the number of rejected messages.
|
Workflow Round Trip Latency Avg | This MIM parameter contains the average workflow processing latency, calculated (in milliseconds) over the last 1000 processed records.
|
Workflow Round Trip Latency Max | This MIM parameter contains the minimum workflow processing latency, since Workflow start.
|
Workflow Round Trip Latency Min | This MIM parameter contains the maximum workflow processing latency, since Workflow start.
|
Accesses
Â