Log events
Get a summary of the supported alarms and raising events and detailed descriptions per alarm and event object.
MC_REDUNDANCY
tmnxMcMobileBothLockedToMaster
Property name | Value |
|---|---|
Application name |
MC_REDUNDANCY |
Event ID | 5002 |
Event name | tmnxMcMobileBothLockedToMaster |
SNMP notification prefix and OID |
TIMETRA-MC-REDUNDANCY-MIB.tmnxMcMobRedundancyNotifications.6 |
Default severity |
minor |
Source stream | main |
|
Message format string | For peers $tmnxMcPeerIpAddrForNotify$ and $tmnxMcPeerSrcIpAddr$ both nodes locked to the active operational role |
Cause | A misconfiguration, to enable mc-master-lock on both Primary and Secondary geo-redundancy nodes is ONLY allowed when mc-mobile link between the geo-redundancy nodes is down and both have turned into the active operational role. When the mc-mobile link comes UP, the notification tmnxMcMobileBothLockedToMaster is generated indicating both the Primary and Secondary nodes are locked in the active operational role. Under steady state, that is, mc-mobile link between the geo-redundancy nodes is UP and peering is successful, mc-master-lock CLI configuration is allowed only on the node in the active operational role. |
Effect | The geo-redundancy link will not be established as these mobile-gateways cannot be peered. |
Recovery | Diagnose and fix the mc-master-lock misconfiguration. |
tmnxMcMobileGeoRedChgInfo
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID |
2040 |
Event name | tmnxMcMobileGeoRedChgInfo |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcMobRedundancyNotifications.2 |
Default severity | major |
Source stream |
main |
Message format string | Gw- $tmnxMcPeerMobileMGId$ ,Src Address- $tmnxMcPeerSrcIpAddr$, CPM Geo-Red State-$tmnxMcPeerMobileMGCPMGeoRedState$, Mob GW Geo Red State- $tmnxMcPeerMobileMGGeoRedState$, Number of Hot Groups-$tmnxMcPeerMobileMGNumHotGroups$ ($tmnxMcPeerMGHotGroupList$), Number Of Warm Groups- $tmnxMcPeerMobileMGNumWarmGroups$ ($tmnxMcPeerMGWarmGroupList$), Number Of Cold Groups-$tmnxMcPeerMobileMGNumColdGroups$ ( $tmnxMcPeerMGColdGroupList$), Peer Address-$tmnxMcPeerIpAddr$, Peer State-$tmnxMcPeerMobileMGPeerState$, Peer State Reason- $tmnxMcPeerMobileMGPeerStChgRsn$ |
Cause | The chassis or the CPM changed its geo-redundancy state or the peer connection status changed. |
Effect | If the chassis state or the CPM state has changed to "cold" or "warm" the system is no longer in geo-redundant state. If the peer state is "disconnected" the system is no longer in a geo-redundant state. |
Recovery | Diagnose what caused this state change. Bring the peer and/or peer-link up and ensure that the chassis and CPM geo-redundancy states are "hot". |
tmnxMcMonitorMcIcrAlarm
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID |
5001 |
Event name | tmnxMcMonitorMcIcrAlarm |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcMobRedundancyNotifications.5 |
Default severity | minor |
Source stream |
main |
Message format string | The monitor-mc-icr alarm occurred on interface $vRtrIfIndex$ for the reason $tmnxMcMonitorMcIcrAlarmRsnCode$. |
Cause |
Generated with the following reason codes: 1. tmnxMcMonitorMcIcrAlarmRsnCode trafficDetected the reference point traffic detected on the standby node reaches the configured monitor-mc-redirect high threshold vRtrIfMonMcRedirectHighThresh. 2. tmnxMcMonitorMcIcrAlarmRsnCode trafficCleared the reference point traffic is below the configured monitor-mc- redirect low threshold vRtrIfMonMcRedirectLowThresh. |
Effect | A network configuration issue or a partial network failure is detected. |
Recovery | Diagnose and fix the partial network failure. |
MOBILE_CUPS_BNG
tmnxMobBngStaticSeOperStateUp
Property name | Value |
|---|---|
Application name |
MOBILE_CUPS_BNG |
Event ID | 2012 |
Event name | tmnxMobBngStaticSeOperStateUp |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.150 |
Default severity |
warning |
Source stream | main |
Message format string | Static session $tmnxMobGwNtfySessionName$ is $tmnxMobGwNtfyTruthValue$operational |
Cause | The operational state of a static CUPS BNG session changes. |
Effect | When the operational state of a static CUPS BNG session is down, the user associated with the session is disconnected. |
Recovery | The recovery action depends on the cause. |
tmnxMobGwBngLockoutLimitExceeded
Property name | Value |
|---|---|
Application name | MOBILE_CUPS_BNG |
Event ID |
2007 |
Event name | tmnxMobGwBngLockoutLimitExceeded |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.120 |
Default severity | warning |
Source stream |
main |
Message format string | The maximum number of BNG sessions in locked-out or monitored state is exceeded $tmnxMobGwNtfyInformation$ |
Cause | While the maximum number of BNG sessions in monitored or locked-out state is in use, a new session must be monitored or locked out. |
Effect | Another session being monitored or locked out is prematurely released to accommodate the new session. |
Recovery | Recovery is not necessary. |
tmnxMobGwBngNatPrefixRevocation
Property name | Value |
|---|---|
Application name | MOBILE_CUPS_BNG |
Event ID |
2009 |
Event name | tmnxMobGwBngNatPrefixRevocation |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.133 |
Default severity | minor |
Source stream |
main |
Message format string | CUPS BNG NAT Prefix revocation : MSCP $tmnxMobGwNtfyMscpId$ Realm $tmnxMobGwNtfyNwRealmName$ pool $tmnxMobGwNtfyPoolName$ Gw $tmnxMobGwNtfyGatewayId$, UP $tmnxMobGwNtfyUpPeerAddress$, prefix $tmnxMobGwNtfyAddr$/$tmnxMobGwNtfyPfxLength$, reason ' $tmnxMobGwNtfyRevocationReason$' |
Cause | An error occurred during NAT audit between MSCP and OAM or ODSA can't ack the prefix. |
Effect | The session will be deleted. |
Recovery |
N/A |
tmnxMobGwBngResFsgUpfChange
Property name | Value |
|---|---|
Application name |
MOBILE_CUPS_BNG |
Event ID | 2010 |
Event name | tmnxMobGwBngResFsgUpfChange |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.134 |
Default severity |
warning |
Source stream | main |
Message format string | UP resiliency: UP change: Gw $tmnxMobGwNtfyGatewayId$, UP group $tmnxMobGwNtfyCupsBngUpGroup$, FSG $tmnxMobGwNtfyFsgId$, primary UP $tmnxMobGwNtfyUpf1$ (health $tmnxMobGwNtfyUpf1Health$), secondary UP $tmnxMobGwNtfyUpf2$ (health $tmnxMobGwNtfyUpf2Health$), previous primary UP $tmnxMobGwNtfyUpf1Prev$, previous secondary UP $tmnxMobGwNtfyUpf2Prev$ |
|
Cause | The value of TIMETRA-MOBILE-PDN-MIB::tmnxMobPdnBngResFsgPrimUpf or TIMETRA-MOBILE-PDN-MIB::tmnxMobPdnBngResFsgSecUpf has changed. |
Effect | If it is the primary UPF that changed, the traffic associated with this Fate Sharing Group is now going through another UPF system. If it is the secondary UPF that changed and if the pair is hot-standby, another UPF system now keeps track of sessions state. |
Recovery | No recovery actions are required. |
tmnxMobGwBngResFsgUpfError
Property name | Value |
|---|---|
Application name | MOBILE_CUPS_BNG |
Event ID |
2011 |
Event name | tmnxMobGwBngResFsgUpfError |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.149 |
Default severity | warning |
Source stream |
main |
Message format string | UP resiliency: UP error: Gw $tmnxMobGwNtfyGatewayId$, UP group $tmnxMobGwNtfyCupsBngUpGroup$, FSG $tmnxMobGwNtfyFsgId$, $tmnxMobGwNtfyTruthValue$ UP $tmnxMobGwNtfyUpf1$: $tmnxMobGwNtfyError$$tmnxMobGwNtfyInformation$ |
Cause | This system, acting as a CUPS Control Plane, has requested a UP to modify (including create/delete) a Fate Sharing Group, and the UP reported an error. |
Effect | If the UP is the active UPF for this Fate Sharing Group, the role of active UPF is transferred to the UPF that was previously the active UPF. |
Recovery | No recovery actions are required. |
tmnxMobGwBngSessCreateUpfNonResp
Property name | Value |
|---|---|
Application name | MOBILE_CUPS_BNG |
Event ID |
2002 |
Event name | tmnxMobGwBngSessCreateUpfNonResp |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.106 |
Default severity | minor |
Source stream |
main |
Message format string | CUPS BNG Session create UP non-response for: Gw $tmnxMobGwNtfyGatewayId$, VRtr $tmnxMobGwNtfyVrtrId$, UP $tmnxMobGwNtfyUpPeerAddress$, node-ID $tmnxMobGwNtfyPeerNodeId$, session key: L2-access-id $tmnxMobGwNtfyCupsBngSessKeyL2Acc$, s-vlan $tmnxMobGwNtfyCupsBngSessKeySVlan$, c-vlan $tmnxMobGwNtfyCupsBngSessKeyCVlan$, mac $tmnxMobGwNtfyCupsBngSessKeyMac$, circuit-id '0x$tmnxMobGwNtfyCupsBngSessKeyCirId$', remote-id '0x $tmnxMobGwNtfyCupsBngSessKeyRemId$' |
Cause | A Create Session Request sent to the UP is not acknowledged with a response message. |
Effect | The session in setup is cancelled on the CP. The UP might have a lingering session state. |
Recovery | The operator's assistance is needed to remove any session state lingering on the UP. |
tmnxMobGwBngSessDuplAttr
Property name | Value |
|---|---|
Application name | MOBILE_CUPS_BNG |
Event ID |
2008 |
Event name | tmnxMobGwBngSessDuplAttr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.132 |
Default severity | minor |
Source stream |
main |
Message format string | CUPS BNG Session setup duplicate session identification attribute detected: Gw $tmnxMobGwNtfyGatewayId$, VRtr $tmnxMobGwNtfyVrtrId$, UP $tmnxMobGwNtfyUpPeerAddress$, node-ID $tmnxMobGwNtfyPeerNodeId$, L2-access-id $tmnxMobGwNtfyCupsBngSessKeyL2Acc$, s-vlan $tmnxMobGwNtfyCupsBngSessKeySVlan$, c-vlan $tmnxMobGwNtfyCupsBngSessKeyCVlan$, mac $tmnxMobGwNtfyCupsBngSessKeyMac$, circuit-id '0x$tmnxMobGwNtfyCupsBngSessKeyCirId$', remote-id '0x $tmnxMobGwNtfyCupsBngSessKeyRemId$', up-group '$tmnxMobGwNtfyCupsBngUpGroup$' |
Cause | A session is setup with attributes which conflict with other active sessions' unique session identification attributes or attribute combinations. |
Effect | The setup session is not available for external targeting based on session attribute identification. |
Recovery | In case external targeting capability is required, the operator's assistance is needed to clear the session. |
tmnxMobGwBngSessTermBySystem
Property name | Value |
|---|---|
Application name | MOBILE_CUPS_BNG |
Event ID |
2001 |
Event name | tmnxMobGwBngSessTermBySystem |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.105 |
Default severity | warning |
Source stream |
main |
Message format string | CUPS BNG session terminated by the system: Reason $tmnxMobGwNtfyCupsBngSessTermReas$, extra info '$tmnxMobGwNtfyCupsBngSessTermInfo$', Gw $tmnxMobGwNtfyGatewayId$, VRtr $tmnxMobGwNtfyVrtrId$, UP-ip $tmnxMobGwNtfyUpPeerAddress$, L2-access-id $tmnxMobGwNtfyCupsBngSessKeyL2Acc$, s-vlan $tmnxMobGwNtfyCupsBngSessKeySVlan$, c-vlan $tmnxMobGwNtfyCupsBngSessKeyCVlan$, mac $tmnxMobGwNtfyCupsBngSessKeyMac$, circuit-id '0x $tmnxMobGwNtfyCupsBngSessKeyCirId$', remote-id '0x$tmnxMobGwNtfyCupsBngSessKeyRemId$', up-group ' $tmnxMobGwNtfyCupsBngUpGroup$' |
Cause | The system found a reason, as indicated by tmnxMobGwNtfyCupsBngSessTermReas for terminating a session. |
Effect | The established session is terminated or the session in setup is cancelled. |
Recovery | None. |
tmnxMobGwBngSubscriberCreate
Property name | Value |
|---|---|
Application name |
MOBILE_CUPS_BNG |
Event ID | 2003 |
Event name | tmnxMobGwBngSubscriberCreate |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.111 |
Default severity |
warning |
Source stream | main |
Message format string | CUPS BNG new subscriber created: Sub-Id '$tmnxMobGwNtfyCupsBngSubId$', externally assigned alias (if any) ' $tmnxMobGwNtfyCupsBngSubExtAlias$, UP IP $tmnxMobGwNtfyAddr$' |
Cause |
A session setup, for which there wasn't any subscriber state yet, is successful. |
Effect | The subscriber state is created. |
Recovery |
Not applicable. |
tmnxMobGwBngSubscriberDelete
Property name | Value |
|---|---|
Application name |
MOBILE_CUPS_BNG |
Event ID | 2004 |
Event name | tmnxMobGwBngSubscriberDelete |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.112 |
Default severity |
warning |
Source stream | main |
Message format string | CUPS BNG subscriber deleted: Sub-Id '$tmnxMobGwNtfyCupsBngSubId$', externally assigned alias (if any) ' $tmnxMobGwNtfyCupsBngSubExtAlias$, UP IP $tmnxMobGwNtfyAddr$' |
Cause |
A session termination of the last session belonging to an active subscriber. |
|
Effect | The subscriber state is deleted. |
Recovery |
Not applicable. |
MOBILE_GATEWAY
tmnxMcRedundancyTrafficReceived
Property name | Value |
|---|---|
Application name |
MOBILE_GATEWAY |
Event ID | 2084 |
Event name | tmnxMcRedundancyTrafficReceived |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.82 |
Default severity |
major |
Source stream | main |
|
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Ref point-$tmnxMobGwNtfyRefPointType$, RefPointName- $tmnxMobGwNtfyRefPointName$, InterfaceType-$tmnxMobGwNtfyIfType$. |
Cause |
Traffic is detected at the ICR node due to a network issue. |
Effect |
When traffic comes to the ICR node, it is dropped if traffic redirection, which means shunting, is not used. If shunting is used, then the traffic is forwarded accordingly. |
Recovery | Check the cause of routing change in the network and fix it if possible. If the traffic can not be directed back, but the whole routing works towards the node, perform an ICR switchover. |
tmnxMobDbRedRoleActive
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2151 |
Event name | tmnxMobDbRedRoleActive |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.153 |
Default severity | warning |
Source stream |
main |
Message format string | Database $tmnxMobDbId$ with IP address $tmnxMobDbIpAddr$ is now active |
Cause | The redundancy role of a database has changed from 'standby' to 'active'. |
Effect | The database is actively being used. |
Recovery |
Not applicable. |
tmnxMobDbStatusChanged
Property name | Value |
|---|---|
Application name |
MOBILE_GATEWAY |
Event ID | 2152 |
Event name | tmnxMobDbStatusChanged |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.154 |
Default severity |
minor |
Source stream | main |
|
Message format string | Database $tmnxMobDbId$ with IP address $tmnxMobDbIpAddr$ is now $tmnxMobDbStatus$ |
Cause | The state of a database has changed. |
Effect | When the new state is 'up', the connection with the database is available. When the new state is 'down', the connection with the database is not available. |
Recovery | If the new state is 'down' and there is no subsequent 'tmnxMobDbRedRoleActive' notification, an ICR switchover is recommended. |
tmnxMobGwApnMaxAttachLmtAlrm
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2124 |
Event name | tmnxMobGwApnMaxAttachLmtAlrm |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.124 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, APN Name- $tmnxMobGwNtfyApnName$, attach request rate reached maximum limit. |
Cause |
The GTP-based attach rate exceeds the configurable max-session-attach limit for tmnxMobGwNtfyApnName is reached |
Effect | If there is a new GTP-based attach and attach rate has been exceeded, the new attach will be rejected. |
Recovery | The alarm is cleared when the rate goes back below the limit. |
tmnxMobGwApnMaxAttachLmtAlrmClr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2125 |
Event name | tmnxMobGwApnMaxAttachLmtAlrmClr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.125 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, APN Name- $tmnxMobGwNtfyApnName$, attach request rate goes below maximum limit. |
Cause |
The GTP-based attach rate drops below the configurable limit max-session-attach limit for this tmnxMobGwNtfyApnName. |
Effect | The GTP-based attach rate drops below the configurable limit. |
Recovery | No further action required. |
tmnxMobGwAssociationPeerState
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2075 |
Event name | tmnxMobGwAssociationPeerState |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.73 |
Default severity | minor |
Source stream |
main |
Message format string | Association state changed to $tmnxMobGwNtfyPeerAssociatnState$ for $tmnxMobGwNtfySigPlaneType$ Peer $tmnxMobGwNtfyPeerNodeId$ on GW $tmnxMobGwNtfyGatewayId$ Reference Point $tmnxMobGwNtfyRefPointType$ $tmnxMobGwNtfyRefPointName$ (IP Address: $tmnxMobGwNtfyRfPtPeerAddr$). Recovery Time: $tmnxMobGwNtfyRecoveryTimestamp$ cp func $tmnxMobGwNtfyPeerCPFuncFeatures$ up func $tmnxMobGwNtfyPeerUPFuncFeatures$ bbf up func $tmnxMobGwNtfyPeerBbfUPFuncFeats$ |
Cause | The Association state changes when the association is either setup or released. The association can be setup/released by association related Node level messages triggered by either the gateway or the peer. Association Messages are initiated by the gateway if the peer is configured in the association Peer list. |
Effect | Path management for PFCP peers and UPF selection can occur after the association is established. Path management or UPF selection will not happen in case of association down. |
Recovery | If the association state is down and the release was initiated by the Gateway, the Gateway must come up for the association to be reestablished. If the release was initiated by the peer, the peer will trigger the setup when it comes up again. |
tmnxMobGwAssocNodeIdFail
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2121 |
Event name | tmnxMobGwAssocNodeIdFail |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.121 |
Default severity | major |
Source stream |
main |
Message format string | Gw - $tmnxMobGwNtfyGatewayId$, epc-node not configured for $tmnxMobGwPdnNtfySxAssociation$ |
Cause | PFCP Association Setup failure to establish due to Node ID missing. |
Effect | PFCP Association Setup procedure will continue to fail to peer node while Node ID is missing. |
Recovery | Configure a valid string for epc-node under the context configure mobile-gateway pdn. |
tmnxMobGwAssocNodeIdFailClr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2123 |
Event name | tmnxMobGwAssocNodeIdFailClr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.123 |
Default severity | major |
Source stream |
main |
Message format string | Gw - $tmnxMobGwNtfyGatewayId$, configured epc-node re-established for $tmnxMobGwPdnNtfySxAssociation$ |
Cause | PFCP Association Setup re-established after node id is present. |
Effect | There is no effect for this notification. |
|
Recovery | No further action is required. |
tmnxMobGwAssocNodeIdMismatch
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2143 |
Event name | tmnxMobGwAssocNodeIdMismatch |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.143 |
Default severity | major |
Source stream |
main |
Message format string | Gw - $tmnxMobGwNtfyGatewayId$, node ID mismatched for $tmnxMobGwPdnNtfySxAssociation$ PFCP association setup |
Cause |
PFCP Association Setup failure to establish due to mismatch of the provided node ID value from all of the PFCP association peer list configuration. |
Effect | PFCP Association Setup procedure will continue to fail the peer node while node ID provided continues to mismatch to any entry in the association list. |
Recovery | Provide a valid node ID configuration entry for the peer list configuration based on the node ID in the PFCP association. |
tmnxMobGwAssocNodeIdMismatchClr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2144 |
Event name | tmnxMobGwAssocNodeIdMismatchClr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.144 |
Default severity | cleared |
Source stream |
main |
Message format string | Gw - $tmnxMobGwNtfyGatewayId$, node ID match found for $tmnxMobGwPdnNtfySxAssociation$ PFCP association |
Cause |
PFCP Association Setup is re-established after the node id provided matches with a valid peer list configuration. |
Effect | PFCP Association Setup is established. |
|
Recovery | No further action is required. |
tmnxMobGwAssocPfcpNdIdIpTypErClr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2146 |
Event name | tmnxMobGwAssocPfcpNdIdIpTypErClr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.146 |
Default severity | cleared |
Source stream |
main |
Message format string | Gw - $tmnxMobGwNtfyGatewayId$, PFCP node ID IP type match occurred after a prior mismatch for $tmnxMobGwPdnNtfySxAssociation$ PFCP association |
Cause |
PFCP Association Setup is re-established after the node ID IP-type value provided matches with a valid Sx reference point peer interface address configuration. |
Effect | PFCP Association Setup is established. |
|
Recovery | No further action is required. |
tmnxMobGwAssocPfcpNodeIdIpTypErr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2145 |
Event name | tmnxMobGwAssocPfcpNodeIdIpTypErr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.145 |
Default severity | major |
Source stream |
main |
Message format string | Gw - $tmnxMobGwNtfyGatewayId$, pfcp node ID IP type mismatched for $tmnxMobGwPdnNtfySxAssociation$ PFCP association |
Cause |
PFCP Association Setup failure to establish due to mismatch of the provided node ID IP-type value with all the configured Sx reference point entry interface address types. |
Effect | PFCP Association Setup procedure will continue to fail while the PFCP node ID IP-type provided continues to mismatch to any address in all the Sx reference point interface configuration. |
Recovery | To provide a valid node ID IP-type configuration in the TIMETRA-MOBILE-PDN-MIB::tmnxMobPdnPfcpNodeIdIpType or create an equivalent IP-type address interface configuration of the Sx reference point configuration. |
tmnxMobGwBngChfFailAlmClr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2156 |
Event name | tmnxMobGwBngChfFailAlmClr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.158 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, the CHF failure handling threshold alarm is cleared because upper limit of $tmnxMobGwNtfyFhAlarmLowerThr$% is reached for APN $tmnxMobGwNtfyApnName$ on VM-$tmnxMobGwNtfyVmId$ |
Cause | The lower threshold limit of the CHF failure handling threshold has been reached. |
Effect | Enough sessions (determined by the threshold) have recovered from failure handling and are being fully charged again. |
Recovery | Not applicable. |
tmnxMobGwBngChfFailAlmSet
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2155 |
Event name | tmnxMobGwBngChfFailAlmSet |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.157 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, the CHF failure handling threshold alarm is set because upper limit of $tmnxMobGwNtfyFhAlarmUpperThr$% is reached for APN $tmnxMobGwNtfyApnName$ on VM-$tmnxMobGwNtfyVmId$ |
Cause | The upper threshold limit of the CHF failure handling threshold has been reached. |
Effect | A signifcant number of sessions (determined by the threshold) have entered failure handling and are not being charged as intended. |
Recovery | Restore the CHF servers to provide full connectivity and functionality. |
tmnxMobGwBngPcfFailAlmClr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2158 |
Event name | tmnxMobGwBngPcfFailAlmClr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.160 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, the PCF failure handling threshold alarm is cleared because upper limit of $tmnxMobGwNtfyFhAlarmLowerThr$% is reached for APN $tmnxMobGwNtfyApnName$ on VM-$tmnxMobGwNtfyVmId$ |
Cause | The lower threshold limit of the PCF failure handling threshold has been reached. |
Effect | Enough sessions (determined by the threshold) have recovered from failure handling and are being fully charged again. |
Recovery | Not applicable. |
tmnxMobGwBngPcfFailAlmSet
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2157 |
Event name | tmnxMobGwBngPcfFailAlmSet |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.159 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, the PCF failure handling threshold alarm is set because upper limit of $tmnxMobGwNtfyFhAlarmUpperThr$% is reached for APN $tmnxMobGwNtfyApnName$ on VM-$tmnxMobGwNtfyVmId$ |
Cause | The upper threshold limit of the PCF failure handling threshold has been reached. |
Effect | A signifcant number of sessions (determined by the threshold) have entered failure handling and are not being charged as intended. |
Recovery | Restore the PCF servers to provide full connectivity and functionality. |
tmnxMobGwBngUdmSdmFailAlmClr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2160 |
Event name | tmnxMobGwBngUdmSdmFailAlmClr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.162 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, the UDM SDM failure handling threshold alarm is cleared because upper limit of $tmnxMobGwNtfyFhAlarmLowerThr$% is reached for APN $tmnxMobGwNtfyApnName$ on VM-$tmnxMobGwNtfyVmId$ |
Cause | The lower threshold limit of the UDM failure handling threshold has been reached. |
Effect | Enough sessions (determined by the threshold) have recovered from failure handling and are being fully charged again. |
Recovery | Not applicable. |
tmnxMobGwBngUdmSdmFailAlmSet
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2159 |
Event name | tmnxMobGwBngUdmSdmFailAlmSet |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.161 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, the UDM SDM failure handling threshold alarm is set because upper limit of $tmnxMobGwNtfyFhAlarmUpperThr$% is reached for APN $tmnxMobGwNtfyApnName$ on VM-$tmnxMobGwNtfyVmId$ |
Cause | The upper threshold limit of the UDM failure handling threshold has been reached. |
Effect | A signifcant number of sessions (determined by the threshold) have entered failure handling and are not being charged as intended. |
Recovery | Restore the UDM servers to provide full connectivity and functionality. |
tmnxMobGwBngUdmUecmFailAlmClr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2162 |
Event name | tmnxMobGwBngUdmUecmFailAlmClr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.164 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, the UDM UECM failure handling threshold alarm is cleared because upper limit of $tmnxMobGwNtfyFhAlarmLowerThr$% is reached for APN $tmnxMobGwNtfyApnName$ on VM-$tmnxMobGwNtfyVmId$ |
Cause | The lower threshold limit of the UDM UECM failure handling threshold has been reached. |
Effect | Enough sessions (determined by the threshold) have recovered from failure handling and are being fully charged again. |
Recovery | Not applicable. |
tmnxMobGwBngUdmUecmFailAlmSet
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2161 |
Event name | tmnxMobGwBngUdmUecmFailAlmSet |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.163 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, the UDM UECM failure handling threshold alarm is set because upper limit of $tmnxMobGwNtfyFhAlarmUpperThr$% is reached for APN $tmnxMobGwNtfyApnName$ on VM-$tmnxMobGwNtfyVmId$ |
Cause | The upper threshold limit of the UDM UECM failure handling threshold has been reached. |
Effect | A signifcant number of sessions (determined by the threshold) have entered failure handling and are not being charged as intended. |
Recovery | Restore the UDM servers to provide full connectivity and functionality. |
tmnxMobGwCfCapacityAlarmMinor
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2011 |
Event name | tmnxMobGwCfCapacityAlarmMinor |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.7 |
Default severity | minor |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Flash ID- $tmnxMobGwNtfyFlashId$, Flash Limit-$tmnxMobGwNtfyCfLimit$, GTP Prime Server Group-$tmnxMobGwNtfyGtpPriGrpName$. |
Cause | The compact flash capacity reaches the 85% limit. |
Effect | N/A |
Recovery | N/A |
tmnxMobGwCfCapacityAlmMjrClear
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2014 |
Event name | tmnxMobGwCfCapacityAlmMjrClear |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.10 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Flash ID- $tmnxMobGwNtfyFlashId$, Flash Limit-$tmnxMobGwNtfyCfLimit$, GTP Prime Server Group-$tmnxMobGwNtfyGtpPriGrpName$. |
Cause | The compact flash capacity drops below the 90% limit. |
Effect | N/A |
Recovery | N/A |
tmnxMobGwCfCapacityAlmMnrClear
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2012 |
Event name | tmnxMobGwCfCapacityAlmMnrClear |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.8 |
Default severity | minor |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Flash ID- $tmnxMobGwNtfyFlashId$, Flash Limit-$tmnxMobGwNtfyCfLimit$, GTP Prime Server Group-$tmnxMobGwNtfyGtpPriGrpName$. |
Cause | The compact flash capacity drops below the 80% limit. |
Effect | N/A |
Recovery | N/A |
tmnxMobGwCntrlFabricPartialFail
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2100 |
Event name | tmnxMobGwCntrlFabricPartialFail |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.98 |
Default severity | minor |
Source stream |
main |
Message format string | Detected $tmnxMobGwNtfyFailureDirection$ failure for slot $tmnxMobGwNtfySlot$ on control fabric $tmnxMobGwNtfyFabricId$ |
Cause |
A tmnxMobGwCntrlFabricPartialFail is generated when a card loses connectivity to other cards in a particular direction over a particular control fabric. The card ID is indicated in tmnxMobGwNtfySlot, the failed fabric ID is indicated in tmnxMobGwNtfyFabricId and the direction of the failure (transmit/receive) is indicated in tmnxMobGwNtfyFailureDirection. |
Effect | The system uses a different control fabric that is operational to communicate with the affected card. |
Recovery | Manual intervention may be required to restore the connectivity. |
tmnxMobGwControlFabricFailure
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2101 |
Event name | tmnxMobGwControlFabricFailure |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.99 |
Default severity | minor |
Source stream |
main |
Message format string | Detected $tmnxMobGwNtfyFailureDirection$ failure for slot $tmnxMobGwNtfySlot$ on all control fabrics |
Cause | A loss of connectivity to other cards in a particular direction over all available control fabrics. |
Effect | The card cannot function properly as part of the system. |
Recovery | Attempt to restore connectivity by rebooting the affected card. |
tmnxMobGwDdnThrottlingStart
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2033 |
Event name | tmnxMobGwDdnThrottlingStart |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.29 |
Default severity | warning |
Source stream |
main |
Message format string | Acct Application: Throttling DDN: Gw- $tmnxMobGwNtfyGatewayId$, Ref point-$tmnxMobGwNtfyRefPointType$, Ref protocol-$tmnxMobGwNtfyRefPointProtocol$, RefPointName- $tmnxMobGwNtfyRefPointName$, address type-$tmnxMobGwNtfyRfPtPeerAddrType$, peer address-$tmnxMobGwNtfyRfPtPeerAddr$, port- $tmnxMobGwNtfyRfPtPeerPort$, duration-$tmnxMobGwNtfyDdnThrotDuration$, factor-$tmnxMobGwNtfyDdnThrotFactor$ |
Cause | The SGW starts throttling the DDN when it receives a throttling instruction carried in the "downlink (DL) low priority traffic Throttling" IE from a peer node. |
Effect | The SGW starts throttling the DDN based on a priority threshold value. The traffic with a priority value higher than or equal to the threshold value is considered as a bearer for non-priority traffic. |
Recovery | When the throttling time is over, the SGW stops throttling the DDN. |
tmnxMobGwDdnThrottlingStop
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2034 |
Event name | tmnxMobGwDdnThrottlingStop |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.30 |
Default severity | warning |
Source stream |
main |
Message format string | Acct Application: Throttling DDN: Gw- $tmnxMobGwNtfyGatewayId$, Ref point-$tmnxMobGwNtfyRefPointType$, Ref protocol-$tmnxMobGwNtfyRefPointProtocol$, RefPointName- $tmnxMobGwNtfyRefPointName$, address type-$tmnxMobGwNtfyRfPtPeerAddrType$, peer address-$tmnxMobGwNtfyRfPtPeerAddr$, port- $tmnxMobGwNtfyRfPtPeerPort$, duration-$tmnxMobGwNtfyDdnThrotDuration$, factor-$tmnxMobGwNtfyDdnThrotFactor$ |
Cause | The SGW stops throttling the DDN when the throttling time is over. |
Effect | The SGW stops throttling the DDN based on a priority threshold value. All DDNs are sent to the peer node. |
Recovery | When another throttling instruction is received from a peer node, the SGW starts throttling the DDN. |
tmnxMobGwDnsSnpFqdnIpLimitAlarm
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2102 |
Event name | tmnxMobGwDnsSnpFqdnIpLimitAlarm |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.100 |
Default severity | minor |
Source stream |
main |
Message format string | Gw:$tmnxMobGwNtfyGatewayId$ Number of server addresses learned by DNS Snooping reached $tmnxMobGwDnsSnpFqdnThres$ % of maximum $tmnxMobGwDnsSnpFqdnIpMax$ |
Cause |
The number of stored DNS resolved IP addresses approaches a threshold limit of the maximum number of cacheable addresses. The threshold in percentage is indicated by tmnxMobGwDnsSnpFqdnThres and the maximum size of stored IP addresses is indicated by the tmnxMobGwDnsSnpFqdnIpMax value. |
Effect | The PGW may reach the maximum limit and may not be able to store new IP addresses. |
Recovery | The operator assistance is needed to clear the resolved filters for the specified FQDN list. |
tmnxMobGwLciOverload
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2080 |
Event name | tmnxMobGwLciOverload |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.78 |
Default severity | minor |
Source stream |
main |
Message format string | Mobile Gateway in GTP-C LCI 100% |
Cause | The resources for the mobile gateway group have reached their limit. |
Effect | The mobile gateway group resources are at critical levels. The system will attempt to lower resource usage on this mobile gateway group. |
Recovery | None |
tmnxMobGwLciOverloadClear
Property name | Value |
|---|---|
Application name |
MOBILE_GATEWAY |
Event ID | 2081 |
Event name | tmnxMobGwLciOverloadClear |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.79 |
Default severity |
minor |
Source stream | main |
|
Message format string | Mobile Gateway GTP-C no longer at LCI 100% |
Cause | The resources for the mobile gateway group are back to the normal operating levels. |
Effect | The mobile gateway group is back to the normal operating levels. |
Recovery | None, the system is back to the normal operating levels. |
tmnxMobGwMcRedPurgeRebootStandby
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2063 |
Event name | tmnxMobGwMcRedPurgeRebootStandby |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.61 |
Default severity | minor |
Source stream |
main |
Message format string | MC_RED purge: Active card- $tmnxMobGwNtfyActiveCardSlotNum$ initialized reboot on standby card-$tmnxMobGwNtfyStandbyCardSlotNum$ |
Cause | In the case of a multi-chassis redundancy purge, if the RED state is not 'hot', the active card initializes a reboot on the standby card after the purge finishes on the active card. |
Effect | The standby card reboots. |
Recovery |
No further action is required. |
tmnxMobGwNnrfBlocklistAlarm
Property name | Value |
|---|---|
Application name |
MOBILE_GATEWAY |
Event ID | 2126 |
Event name | tmnxMobGwNnrfBlocklistAlarm |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.126 |
Default severity |
warning |
Source stream | main |
Message format string | NRF peer for service $tmnxMobGwNtfyNnrfServiceType$ on GW- $tmnxMobGwNtfyGatewayId$ is block-listed |
Cause | All the NRF peers for service nnrf-nfm or nnrf-disc are block-listed after failure responses or response timeouts. |
Effect | The block list duration is not applied. All NRF peers are sending failure responses or the responses time out. The Gateway continuously retries service requests to all peers. |
Recovery | The alarm is cleared when the first NRF peer from the block list is successfully contacted (a success HTTP status is received). |
tmnxMobGwNnrfBlocklistAlarmClear
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2127 |
Event name | tmnxMobGwNnrfBlocklistAlarmClear |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.127 |
Default severity | warning |
Source stream |
main |
Message format string | NRF peer for service $tmnxMobGwNtfyNnrfServiceType$ on GW-$tmnxMobGwNtfyGatewayId$ is no longer block-listed |
Cause | All the NRF peers for service nnrf-nfm or nnrf-disc are no longer block-listed. |
Effect | The block list duration is applied. |
Recovery |
No further action required. |
tmnxMobGwNrfHeartbeatAlarm
Property name | Value |
|---|---|
Application name |
MOBILE_GATEWAY |
Event ID | 2094 |
Event name | tmnxMobGwNrfHeartbeatAlarm |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.90 |
Default severity |
major |
Source stream | main |
|
Message format string | NRF heartbeat failed for peer $tmnxMobGwNtfyRfPtPeerAddr$ on GW $tmnxMobGwNtfyGatewayId$ with error: $tmnxMobGwNtfyNrfHbAlarmReason$ |
|
Cause | Loss of connectivity to the NRF, NRF failure. |
Effect |
The NRF does not consider MAG-c SMF or UPF to be registered and eligible for discovery anymore. The NRF may also consider the MAG-c SMF or UPF to be out of service and notify the subscribed peer NF instances. |
Recovery | Recovery is TBD according to failure handling of failed HB responses and failover to next NRF is concluded. |
tmnxMobGwNrfHeartbeatAlarmClear
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2095 |
Event name | tmnxMobGwNrfHeartbeatAlarmClear |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.91 |
Default severity | major |
Source stream |
main |
Message format string | NRF heartbeat succeeded for peer $tmnxMobGwNtfyRfPtPeerAddr$ on GW $tmnxMobGwNtfyGatewayId$ with error: $tmnxMobGwNtfyNrfHbAlarmReason$ |
Cause | Successful Heartbeat message request/response sequence with NRF. |
Effect | The NRF considers MAG-c SMF or UPF to be registered and eligible for discovery. |
Recovery | No further action is required. |
tmnxMobGwOciOverload
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2082 |
Event name | tmnxMobGwOciOverload |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.80 |
Default severity | major |
Source stream |
main |
Message format string | Mobile Gateway in GTP-C OCI overload |
Cause | The resources for the mobile gateway group have been almost exhausted due to high load. |
Effect | The mobile gateway group resources are at critical levels. The system will attempt to lower resource usage on this mobile gateway group. |
Recovery | None. |
tmnxMobGwOciOverloadClear
Property name | Value |
|---|---|
Application name |
MOBILE_GATEWAY |
Event ID | 2083 |
Event name | tmnxMobGwOciOverloadClear |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.81 |
Default severity |
major |
Source stream | main |
|
Message format string | Mobile Gateway no longer in GTP-C overload |
Cause | The resources for the mobile gateway group are back to the normal operating levels. |
Effect | The mobile gateway group is back to the normal operating levels. |
Recovery | None, the system is back to the normal operating levels. |
tmnxMobGwOciOvldThrtStart
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2103 |
Event name | tmnxMobGwOciOvldThrtStart |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.101 |
Default severity | major |
Source stream |
main |
Message format string | The mobile gateway has started throttling incoming call flows due to local overload. |
Cause | The resources for the mobile gateway group have been almost exhausted due to high load. |
Effect | The mobile gateway group resources are at critical level. The system attempts to lower the resource usage on this mobile gateway group. |
Recovery | The mobile-gateway stops throttling incoming call flows when it is out of local overload. |
tmnxMobGwOciOvldThrtStop
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2104 |
Event name | tmnxMobGwOciOvldThrtStop |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.102 |
Default severity | major |
Source stream |
main |
Message format string | The mobile gateway has stopped throttling incoming call flows due to local overload. |
Cause | Either incoming call flows are not received for the last 30 seconds, or the resources for the mobile gateway group are back to normal operating levels in the last 30 seconds. |
Effect | The mobile gateway is no longer throttling incoming call flows due local overload. |
Recovery | Not applicable. |
tmnxMobGwPathMgmtPeerState
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2001 |
Event name | tmnxMobGwPathMgmtPeerState |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.1 |
Default severity | major |
Source stream |
main |
Message format string | Path Management: Peer State: $tmnxMobGwNtfyPathMgmtPeerState$: Gw-$tmnxMobGwNtfyGatewayId$, Ref point-$tmnxMobGwNtfyRefPointType$, protocol- $tmnxMobGwNtfyRefPointProtocol$, RefPointName-$tmnxMobGwNtfyRefPointName$,peer-$tmnxMobGwNtfyRfPtPeerAddr$, port- $tmnxMobGwNtfyRfPtPeerPort$, Local address -$tmnxMobGwNtfyPathLocAddress$, Previous Restart Counter- $tmnxMobGwNtfyPrevRestartCounter$, Current Restart Counter-$tmnxMobGwNtfyCurrRestartCounter$, Peer Restart Reason- $tmnxMobGwNtfyPeerRestartReason$, Pkt Seq Number-$tmnxMobGwNtfyPeerRestPktSeqNum$, Peer Type-$tmnxMobGwNtfySigPeerType$, Plane Type- $tmnxMobGwNtfySigPlaneType$. |
Cause | A change in the reference point peer state during path management. The supported trap event values are the following: Added - raised when a new peer is identified due to incoming messages Up - raised when a peer moves to UP state, for a SGW peer, this state change happens when a CS Req is received. for PGW peers, this state change happens when a CS Resp from the PGW peer is received (this is to make sure that Path UP trap is generated only for a real PGW peer in case of GTP-C redirection) Down - raised when a peer moves to the FAULT state while detecting a path management failure. Idle - raised when a peer moves to the IDLE state after session cleanup is done due to path management Failure/ Detach/Admin delete Restart - raised when a peer restart is detected, it is associated with Peer RESTART state Deleted - raised when a peer entry is deleted due to a peer aging out, a peer ages out when it is Idle for more than the Age Out Interval. |
Effect | N/A |
Recovery | N/A |
tmnxMobGwPcmdOperStateChange
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2045 |
Event name | tmnxMobGwPcmdOperStateChange |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.43 |
Default severity | minor |
Source stream |
main |
Message format string | PCMD: Oper State: $tmnxMobGwNtfyPcmdOperState$: Gw- $tmnxMobGwNtfyGatewayId$, PCMD profile-$tmnxMobGwNtfyPcmdProfile$ |
Cause |
The PCMD operational state changes when the destination address reachability changes. |
Effect | When the PCMD state is down, the generated PCMD packets are not sent to the destination address. When the PCMD state is up, the PCMD packets are sent to the destination address. |
Recovery | If the PCMD state is down, then generated PCMD packets are dropped. |
tmnxMobGwPfcpRestoreInProg
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2122 |
Event name | tmnxMobGwPfcpRestoreInProg |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.122 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$ VRtr- $tmnxMobGwNtfyVrtrId$ RefPointType-$tmnxMobGwNtfyRefPointType$ RefPointName-$tmnxMobGwNtfyRefPointName$ PFCP restoration in progress for RemotePeerAddress- $tmnxMobGwNtfyRfPtPeerAddr$ LocalPeerAddress-$tmnxMobGwNtfyPeerLocAddress$ RestoreTimer-$tmnxMobGwNtfyRestoreTimer$ NodeId- $tmnxMobGwNtfyPeerNodeId$ |
Cause | A PFCP keepalive failure between UP and CP has been detected. |
Effect | The restoration timer has started. |
Recovery |
Restore the path between UP and CP to allow keepalives to succeed again. If keepalives recover before the restoration timer times out, the CP and UP will perform an audit and recover from the failure automatically. |
tmnxMobGwPfcpViaUpFuncFailureClr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2129 |
Event name | tmnxMobGwPfcpViaUpFuncFailureClr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.129 |
Default severity | cleared |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, $tmnxMobGwNtfyGrpName$ detected a PFCP-u tunnel connectivity re-established between the CP function and UP function. |
Cause | PFCP-u tunnel used for via-up-function (radius-group or dhcp-server-group) traffic between CP and UP function is failing re-established. |
Effect | Any traffic routed over the PFCP-u tunnel will no longer fail. |
Recovery | No further action required. |
tmnxMobGwRadGrpFailAlarm
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2024 |
Event name | tmnxMobGwRadGrpFailAlarm |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.20 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Radius Server Group- $tmnxMobGwNtfyRadGrpName$, Group State-$tmnxMobGwNtfyRadGrpState$. |
Cause |
All the RADIUS servers for the group are in a down operating state. |
Effect |
When the group of RADIUS servers fails, RADIUS messages may not be sent to the group. |
Recovery | The RADIUS server group will recover from this failure mode when one of its servers returns to the up operating state. |
tmnxMobGwRadGrpFailAlarmClrd
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2025 |
Event name | tmnxMobGwRadGrpFailAlarmClrd |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.21 |
Default severity | minor |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Radius Server Group- $tmnxMobGwNtfyRadGrpName$, Group State-$tmnxMobGwNtfyRadGrpState$. |
Cause |
The RADIUS server group is recovered from the previous failure mode and at least one of its servers has transitioned to the up operating state. |
Effect | The operation for the RADIUS group is back to normal. |
Recovery | No further action is required. |
tmnxMobGwRadPeerFailAlarm
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2022 |
Event name | tmnxMobGwRadPeerFailAlarm |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.18 |
Default severity | minor |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Radius Server Group- $tmnxMobGwNtfyRadGrpName$, Address-$tmnxMobGwNtfyRadPeerAddr$, Authentication port-$tmnxMobGwNtfyRadPeerAuthPort$, Accounting port- $tmnxMobGwNtfyRadPeerAcctPort$, Peer State-$tmnxMobGwNtfyRadPeerState$. |
|
Cause | The operating state for RADIUS server is changed to the down state. |
Effect | RADIUS messages may not be sent to the RADIUS server. |
Recovery | RADIUS messages can continue to be sent to a RADIUS server after the RADIUS server's operating state changes back to up or the dead timer expires. |
tmnxMobGwRadPeerFailAlarmClrd
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2023 |
Event name | tmnxMobGwRadPeerFailAlarmClrd |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.19 |
Default severity | minor |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Radius Server Group- $tmnxMobGwNtfyRadGrpName$, Address-$tmnxMobGwNtfyRadPeerAddr$, Authentication port-$tmnxMobGwNtfyRadPeerAuthPort$, Accounting port- $tmnxMobGwNtfyRadPeerAcctPort$, Peer State-$tmnxMobGwNtfyRadPeerState$. |
|
Cause | The RADIUS server recovered from the previous failure mode and one of its servers has transitioned to the up operating state. |
Effect | The operation for the RADIUS server is back to normal. |
Recovery | No further action is required. |
tmnxMobGwSbiPeerState
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2130 |
Event name | tmnxMobGwSbiPeerState |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.130 |
Default severity | warning |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Group ID- $tmnxMobGwNtfySbiGroupId$, NF service name- $tmnxMobGwNtfySbiNfServiceName$, Service Instance- $tmnxMobGwNtfySbiNfServiceIns$, peer UUID- $tmnxMobGwNtfySbiPeerUuid$, peer ip address- $tmnxMobGwNtfySbiPeerIpAddress$, peer port- $tmnxMobGwNtfySbiPeerPort$, connection state- $tmnxMobGwNtfySbiConnectionState$, NF service state- $tmnxMobGwNtfySbiNfServiceState$. |
Cause | A change in the NF peer connection status or peer is deleted from peer list. |
Effect | N/A. |
Recovery | N/A. |
tmnxMobGwSmfDnnOvld
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2116 |
Event name | tmnxMobGwSmfDnnOvld |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.115 |
Default severity | minor |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, APN Name- $tmnxMobGwNtfyApnName$ SMF entered into DNN overloaded state. |
Cause |
SMF reaches DNN level overload state. |
Effect | The system throttles new sessions and signals a backoff timer as configured with 'pdn apn dnn-overload-control n1-back-off-timer'. |
Recovery | Not applicable. |
tmnxMobGwSmfDnnOvldClear
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2117 |
Event name | tmnxMobGwSmfDnnOvldClear |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.116 |
Default severity | minor |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, APN Name- $tmnxMobGwNtfyApnName$ SMF no longer in DNN overload. |
Cause |
SMF no longer in DNN level overload. |
Effect | The system stops throttling new sessions. |
Recovery | Not applicable. |
tmnxMobGwSmfNodeOvld
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2114 |
Event name | tmnxMobGwSmfNodeOvld |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.113 |
Default severity | minor |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Group ID- $tmnxMobGwNtfySysGroupId$ SMF entered into node level overloaded state. |
Cause |
SMF reaches node level overload. |
Effect | The system throttles new sessions and signals a backoff timer as configured with 'pdn apn overload-back-off overload-back-off-timer'. |
Recovery | Not applicable. |
tmnxMobGwSmfNodeOvldClear
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2115 |
Event name | tmnxMobGwSmfNodeOvldClear |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.114 |
Default severity | minor |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, Group ID- $tmnxMobGwNtfySysGroupId$ SMF no longer in node level overload. |
Cause |
SMF no longer in overload. |
Effect | The system stops throttling new sessions. |
Recovery | Not applicable. |
tmnxMobPdnApnMaxPdnConnAlarm
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2035 |
Event name | tmnxMobPdnApnMaxPdnConnAlarm |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.33 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, APN Name- $tmnxMobGwNtfyApnName$. |
Cause | The maximum number of PDN connections for this APN on the gateway is reached. |
Effect | New PDN connections are not accepted until the limit drops below the value of TIMETRA-MOBILE-PDN-MIB::tmnxMobPdnApnMaxPdnConnections. |
Recovery | To accept new PDN connections, the system has to wait until the maximum PDN connections number drops below the threshold. |
tmnxMobPdnApnMaxPdnConnAlarmClr
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2036 |
Event name | tmnxMobPdnApnMaxPdnConnAlarmClr |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.34 |
Default severity | major |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, APN Name- $tmnxMobGwNtfyApnName$. |
Cause | The existing number of PDN connections for this APN on the gateway drops below the value of TIMETRA-MOBILE-PDN-MIB::tmnxMobPdnApnMaxPdnConnections. |
Effect | New PDN connections are accepted. |
Recovery |
No further action is required. |
tmnxMobPdnBearerContextClear
Property name | Value |
|---|---|
Application name |
MOBILE_GATEWAY |
Event ID | 2153 |
Event name | tmnxMobPdnBearerContextClear |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.155 |
Default severity |
warning |
Source stream | main |
Message format string | Clear bearer context in PDN $tmnxMobGwNtfyGatewayId$ $tmnxMobGwNtfyLongText$ $tmnxMobGwNtfyStartEnd$ (#$tmnxMobGwNtfyNumber$) |
Cause | The system starts or terminates processing a request to clear a PDN bearer context. The request can be done with the CLI command 'clear mobile-gateway pdn bearer-context' or by using one of the appropriate rows in the TIMETRA-CLEAR-MIB::tmnxClearTable, like the row named 'clearMobPdnBearerContext'. |
Effect | In the time interval between the start and end notification, the system has cleared a number of PDN bearer contexts that match the specified parameters. The UE's associated with the bearer contexts lose their connection with the PDN. |
Recovery | None. |
tmnxMobPdnLaaPfxInsufficientMem
Property name | Value |
|---|---|
Application name |
MOBILE_GATEWAY |
Event ID | 2113 |
Event name | tmnxMobPdnLaaPfxInsufficientMem |
SNMP notification prefix and OID |
TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.113 |
Default severity |
warning |
Source stream | main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, network realm $tmnxMobGwNtfyNwRealmName$, pool $tmnxMobGwNtfyPoolName$, prefix $tmnxMobGwNtfyAddr$/$tmnxMobGwNtfyPfxLength$ not operational due to insufficient memory |
Cause | Insufficient memory for an IP address prefix and all of its micronets. |
Effect | The IP address prefix is not activated, and its operational status goes down. |
Recovery | Add memory to the system, or reduce the number of the prefix micronets. |
tmnxMobPdnLaaPlNoFreeMnets
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2136 |
Event name | tmnxMobPdnLaaPlNoFreeMnets |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.136 |
Default severity | minor |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, network realm $tmnxMobGwNtfyNwRealmName$, pool $tmnxMobGwNtfyPoolName$ IPv6 type $tmnxMobGwNtfyIpv6AssignmentType$: no more free $tmnxMobGwNtfyLaaUnfragmentedMn$ micronets $tmnxMobGwNtfyTruthValue$ |
|
Cause | The last available micronet of its kind in the pool is activated. |
Effect | Setup of new end user sessions will start to fail. |
Recovery | Add prefixes to the pool. |
tmnxMobPdnLaaPlNumFreeMnetsLow
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2110 |
Event name | tmnxMobPdnLaaPlNumFreeMnetsLow |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.108 |
Default severity | warning |
Source stream |
main |
Message format string | Gw-$tmnxMobGwNtfyGatewayId$, network realm $tmnxMobGwNtfyNwRealmName$, pool $tmnxMobGwNtfyPoolName$ IPv6 type $tmnxMobGwNtfyIpv6AssignmentType$: running low on $tmnxMobGwNtfyLaaUnfragmentedMn$ micronets $tmnxMobGwNtfyTruthValue$ |
|
Cause | A micronet is activated while the number of free micronets in the pool is already low. |
Effect | None. |
Recovery | No recovery is immediately required. However, it is recommended to add prefixes in order to avoid complete depletion of the pool. |
tmnxMobProfNodeSelTrgtSugstRebal
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2149 |
Event name | tmnxMobProfNodeSelTrgtSugstRebal |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.151 |
Default severity | warning |
Source stream |
main |
Message format string | Evaluate target-profile $tmnxMobGwNtfyProfileName$ and rebalance if necessary - new UP=$tmnxMobGwNtfyUpPeerAddress$, surviving number of UPs= $tmnxMobGwNtfyNumber$ |
Cause | The system has reconnected to a UPF after having been disconnected. |
Effect | While the UPF connection was down session distribution among the UPFs in a target profile may have become unbalanced. This event indicates session load rebalancing may be necessary. |
Recovery | Session load among the available UPFs in the target profile should be evaluated, and if necessary, rebalanced using a clear operation. |
tmnxMobProfNodeSelTrgtSugstRevrt
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2150 |
Event name | tmnxMobProfNodeSelTrgtSugstRevrt |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.152 |
Default severity | warning |
Source stream |
main |
Message format string | Evaluate target-profile $tmnxMobGwNtfyProfileName$ and revert if necessary |
Cause |
The number of available UPFs in a target profile entry has reached the necessary minimum threshold. |
Effect | While the number of available UPF connections was below the minimum threshold new sessions will be directed to backup UPFs. This event indicates it may be appropriate to revert sessions to primary UPFs. |
Recovery | Session load among primary and secondary UPFs of the target profile should be evaluated and if necessary, reverted using a clear operation. |
tmnxOverlayFabricFailure
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2072 |
Event name | tmnxOverlayFabricFailure |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.70 |
Default severity | minor |
Source stream |
main |
Message format string | Detected $tmnxMobGwNtfyFailureDirection$ failure for slot $tmnxMobGwNtfySlot$ on all overlay fabrics |
Cause | A loss of connectivity to other cards in a particular direction over all available overlay fabrics. |
Effect | The card cannot function properly as part of the system. |
Recovery | Attempt to restore connectivity by rebooting the affected card. |
tmnxOverlayFabricPartialFailure
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2073 |
Event name | tmnxOverlayFabricPartialFailure |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.71 |
Default severity | minor |
Source stream |
main |
Message format string | Detected $tmnxMobGwNtfyFailureDirection$ failure for slot $tmnxMobGwNtfySlot$ on overlay fabric $tmnxMobGwNtfyFabricId$ |
Cause |
Loss of connectivity between the affected card and the other cards in a particular direction over a particular overlay fabric. |
Effect | The system will use a different overlay fabric that is operational to communicate with the affected card, but the capacity will be reduced. |
Recovery | Manual intervention may be required to restore the connectivity. |
tmnxOverlayFabricStatus
Property name | Value |
|---|---|
Application name | MOBILE_GATEWAY |
Event ID |
2060 |
Event name | tmnxOverlayFabricStatus |
SNMP notification prefix and OID | TIMETRA-MOBILE-GATEWAY-MIB.tmnxMobGatewayNotifications.58 |
Default severity | major |
Source stream |
main |
Message format string | Operational state of last overlay fabric port transitioned to $tmnxMobGwNtfyOverlayFabricState$ state for VM $tmnxMobGwNtfyVmId$ |
Cause |
A change in the operational state of the overlay fabric switch, either when the last operational overlay fabric port transitions to the down state or when the first overlay fabric port transitions to an operationally up state. |
Effect | If the value of tmnxMobGwNtfyOverlayFabricState is down, the VM fails (crashes) and ceases to process any new packets. |
Recovery | If the value of tmnxMobGwNtfyOverlayFabricState is down, the VM fails to process new packets and reboots. The VM remains in the booting state until the value of tmnxMobGwNtfyOverlayFabricState changes to up. |