DIAMETER
tmnxDiamAppSessionFailure
Property name | Value |
---|---|
Application name | DIAMETER |
Event ID |
2003 |
Event name | tmnxDiamAppSessionFailure |
SNMP notification prefix and OID | TIMETRA-DIAMETER-MIB.tmnxDiameterNotifications.3 |
Default severity | minor |
Source stream |
main |
Message format string | DIAMETER session failure, sessid= $tmnxDiamAppSessionId$, subscrid=$tmnxDiamAppSubscrId$, sapid=$tmnxDiamAppSapId$, slaprof= $tmnxDiamAppSLAProfName$ $tmnxDiamNotifySpiShareType$:$tmnxDiamNotifySpiShareId$, $tmnxDiamAppTrapDescription$ |
Cause | The tmnxDiamAppSessionFailure notification indicates that the DIAMETER protocol has a session failure. |
Effect | Determined by cc-failure-handling settings. |
Recovery | N/A |
tmnxDiamMessageDropped
Property name | Value |
---|---|
Application name | DIAMETER |
Event ID |
2007 |
Event name | tmnxDiamMessageDropped |
SNMP notification prefix and OID | TIMETRA-DIAMETER-MIB.tmnxDiameterNotifications.7 |
Default severity | minor |
Source stream |
main |
Message format string | Diameter message dropped, policy= $tmnxDiamPlcyName$, peer=$tmnxDiamPeerStatsPeerName$, client-side-peer-ip=$tmnxDiamPeerStatsPeerIpAddr$, tcp-port= $tmnxDiamPeerStatsPeerPort$, drop-count=$tmnxDiamPeerStatsFailedMessages$, $tmnxDiamAppTrapDescription$ |
Cause | The tmnxDiamMessageDropped notification indicates that the DIAMETER protocol has dropped a message. |
Effect | N/A |
Recovery | N/A |
tmnxDiamNdPeerStatActiveChanged
Property name | Value |
---|---|
Application name |
DIAMETER |
Event ID | 2008 |
Event name | tmnxDiamNdPeerStatActiveChanged |
SNMP notification prefix and OID |
TIMETRA-DIAMETER-MIB.tmnxDiameterNotifications.8 |
Default severity |
minor |
Source stream | main |
Message format string | DIAMETER node $tmnxDiamNodeOriginHost$, peer $tmnxDiamNodeDestinationHost$ is $tmnxDiamNdPeerStatActive$ active |
Cause | The value of tmnxDiamNdPeerStatActive can be impacted by various conditions, such as configuration, routing, physical connectivity, and so on. |
Effect | When the peer is active, the diameter applications can use it. When the peer is not active, the diameter applications can not use the peer; there may be a standby peer available to use. |
Recovery | The recovery actions, if any are required, depend on the actual condition that affected the activity of the peer. |
tmnxDiamPolicyPeerStateChange
Property name | Value |
---|---|
Application name |
DIAMETER |
Event ID | 2001 |
Event name | tmnxDiamPolicyPeerStateChange |
SNMP notification prefix and OID |
TIMETRA-DIAMETER-MIB.tmnxDiameterNotifications.1 |
Default severity |
minor |
Source stream | main |
Message format string | DIAMETER policy $tmnxDiamPlcyName$, peer $tmnxDiamPlcyPeerName$ now has operational state: PrimarySecondary = $tmnxDiamPeerPrimarySecondary$, connectionSuspended = $tmnxDiamPeerConnectionSuspended$ and cooldownSeqActive = $tmnxDiamPeerCooldownSeqActive$, $tmnxDiamAppTrapDescription$ |
Cause |
The state of the diameter policy peer changed. |
Effect |
N/A |
Recovery | No recovery is necessary. |
tmnxDiamPpPrxMcLocStateChanged
Property name | Value |
---|---|
Application name |
DIAMETER |
Event ID | 2005 |
Event name | tmnxDiamPpPrxMcLocStateChanged |
SNMP notification prefix and OID |
TIMETRA-DIAMETER-MIB.tmnxDiameterNotifications.5 |
Default severity |
minor |
Source stream | main |
Message format string | The proxy multi-chassis redundancy state of the Diameter peer policy $tmnxDiamPlcyName$ changed to $tmnxDiamPpPrxMcLocState$ |
Cause |
The MCS (Multi Chassis redundancy Synchronization) state of a proxy function has changed. |
Effect | The effect depends on the actual state transition. The states 'active' and 'standby' are normal states. In other states, Diameter communication may be interrupted, and hosts may be refused access to network services. |
Recovery | The need for recovery action depends on the state transition. In the states 'active' and 'standby', no recovery action may be necessary. |
tmnxDiamSessionEvent
Property name | Value |
---|---|
Application name |
DIAMETER |
Event ID | 2004 |
Event name | tmnxDiamSessionEvent |
SNMP notification prefix and OID |
TIMETRA-DIAMETER-MIB.tmnxDiameterNotifications.4 |
Default severity |
minor |
Source stream | main |
Message format string | Session event, session ID='$tmnxDiamAppSessionId$', policy=' $tmnxDiamAppPlcyId$', application=$tmnxDiamAppPlcyApplication$, event=$tmnxDiamNotifyEventId$, $tmnxDiamAppTrapDescription$ |
Cause | A Diameter session has experienced a problem. The session ID is indicated with the tmnxDiamAppSessionId. The associated Diameter application policy is indicated with the tmnxDiamAppPlcyApplication. What happened is indicated with the tmnxDiamNotifyEventId and the tmnxDiamAppTrapDescription. |
Effect | The effect depends on the cause. For example: if a Diameter message could not be transmitted, session set-up may fail. |
Recovery | The recovery depends on the cause. |