OAM
svcIdInvalid
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2053 |
Event name | svcIdInvalid |
SNMP notification prefix and OID | N/A |
Default severity | minor |
Message format string | Service id $serviceId$ is invalid: $reasonToReport$ |
Cause |
Svc-ping tried to send or process a packet to a non-existent svc-id. |
Effect | N/A |
|
Recovery | N/A |
svcIdWrongType
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2054 |
Event name | svcIdWrongType |
SNMP notification prefix and OID | N/A |
Default severity | minor |
Message format string | Service id $serviceId$ has a wrong type: $reasonToReport$ |
Cause |
Svc-ping tried to send or process a packet to a svc-id with a wrong svc-type. |
Effect | N/A |
|
Recovery | N/A |
tmnxAncpLoopbackTestCompleted
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2004 |
Event name | tmnxAncpLoopbackTestCompleted |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamPingNotifications.7 |
Default severity | warning |
Message format string | The ANCP loopback test for ANCP string $tmnxOamAncpHistoryAncpString$ has ended. The access Node has sent Result $tmnxOamAncpHistoryAccNodeResult$; code$tmnxOamAncpHistoryAccNodeCode$; and reply string $tmnxOamAncpHistoryAccNodeRspStr$. |
|
Cause | An ANCP loopback is finished and a notification was explicitly requested. |
Effect | N/A |
|
Recovery | N/A |
tmnxAncpLoopbackTestCompletedL
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2005 |
Event name | tmnxAncpLoopbackTestCompletedL |
SNMP notification prefix and OID | N/A |
Default severity | warning |
Message format string | The ANCP loopback test for ANCP string $tmnxOamAncpHistoryAncpString$ has ended. The access Node has sent Result $tmnxOamAncpHistoryAccNodeResult$; code$tmnxOamAncpHistoryAccNodeCode$; and reply string $tmnxOamAncpHistoryAccNodeRspStr$. |
|
Cause | N/A |
Effect |
N/A |
Recovery |
N/A |
tmnxOamDiagTestCompleted
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2150 |
Event name | tmnxOamDiagTestCompleted |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamDiagNotifications.1 |
Default severity | minor |
Message format string | OAM $tmnxOamDiagCtlTestMode$ test " $tmnxOamDiagCtlTestIndex$" created by "$tmnxOamDiagCtlOwnerIndex$" run # $tmnxOamTestRunIndex$ completed |
Cause |
A tmnxOamDiagTestCompleted trap is generated at the end of every diagnostic test run. A diagnostic test is configured using tmnxOamDiagCtlTable. tmnxOamDiagCtlTestMode indicates the type of the diagnostic test (e.g. 'findEgressDiag(1)'). tmnxOamTestRunIndex indicates the run number of the completed diagnostic test run. For example, the second run of a test with owner 'owner_A' and test 'test_Z' has tmnxOamTestRunIndex=2. |
Effect | The result of the test run can be read (e.g. from the indicated row in tmnxOamFindEgrDiagResultsTable). |
Recovery | No recovery is required. |
tmnxOamLdpTtraceAutoDiscState
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2055 |
Event name | tmnxOamLdpTtraceAutoDiscState |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamTraceRouteNotifications.4 |
Default severity | minor |
Message format string | The discovery state of the 'Auto Ldp Tree Trace entity' has changed to $tmnxOamLTtraceAutoDiscoveryState$ |
|
Cause | The discovery state of the 'Auto Ldp Tree Trace entity' represented by tmnxOamLTtraceAutoDiscoveryState has been changed. |
Effect | N/A |
|
Recovery | N/A |
tmnxOamLdpTtraceFecDisStatus
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2057 |
Event name | tmnxOamLdpTtraceFecDisStatus |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamTraceRouteNotifications.6 |
Default severity | minor |
Message format string | The FEC $strTmnxOamLTtraceFecPrefix$/ $strTmnxOamLTtraceFecPrefLen$ is discovered with $tmnxOamLTtraceFecDisPaths$ paths. The discovery status BITs are $strTmnxOamLTtraceFecDisStatusBits$. |
|
Cause | The discovery status BITS or the number of discovered paths of the 'auto discovered FEC' has been changed. Note that the changes were evaluated at the end of a FEC discovery. |
Effect | N/A |
|
Recovery | N/A |
tmnxOamLdpTtraceFecPFailUpdate
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2058 |
Event name | tmnxOamLdpTtraceFecPFailUpdate |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamTraceRouteNotifications.7 |
Default severity | minor |
Message format string | Path probe state update for the 'auto discovered' FEC, $strTmnxOamLTtraceFecPrefix$/$strTmnxOamLTtraceFecPrefLen$. $tmnxOamLTtraceFecFailedProbes$ out of $tmnxOamLTtraceFecDisPaths$ paths are in failed probing state. |
Cause | The probe state of the 'auto discovered FEC' has been changed. |
Effect | N/A |
|
Recovery | N/A |
tmnxOamLdpTtraceFecProbeState
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2056 |
Event name | tmnxOamLdpTtraceFecProbeState |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamTraceRouteNotifications.5 |
Default severity | minor |
Message format string | The probe state of the 'auto discovered' FEC, $strTmnxOamLTtraceFecPrefix$/$strTmnxOamLTtraceFecPrefLen$, has changed to $tmnxOamLTtraceFecProbeState$.$tmnxOamLTtraceFecFailedProbes$ out of $tmnxOamLTtraceFecDisPaths$ paths are in failed probing state. |
Cause | The probe state of the 'auto discovered FEC' has been changed. |
Effect | N/A |
|
Recovery | N/A |
tmnxOamPingProbeFailedV3
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2001 |
Event name | tmnxOamPingProbeFailedV3 |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamPingNotifications.8 |
Default severity | minor |
Message format string | OAM $tmnxOamPingCtlTestMode$ test " $tmnxOamPingCtlTestIndex$" created by "$tmnxOamPingCtlOwnerIndex$" run # $tmnxOamPingResultsTestRunIndex$ probe $tmnxOamPingHistoryIndex$ failed |
Cause | A probe failure was detected when the corresponding tmnxOamPingCtlTrapGeneration object is set to probeFailure(0) subject to the value of tmnxOamPingCtlTrapProbeFailureFilter. The object tmnxOamPingCtlTrapProbeFailureFilter can be used to specify the number of successive probe failures that are required before this notification can be generated. |
Effect | N/A |
|
Recovery | N/A |
tmnxOamPingTestCompletedV3
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2003 |
Event name | tmnxOamPingTestCompletedV3 |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamPingNotifications.10 |
Default severity | minor |
Message format string | OAM $tmnxOamPingCtlTestMode$ test " $tmnxOamPingCtlTestIndex$" created by "$tmnxOamPingCtlOwnerIndex$" run # $tmnxOamPingResultsTestRunIndex$ completed |
Cause | A ping test when the corresponding tmnxOamPingCtlTrapGeneration object is set to testCompletion(2). |
Effect | N/A |
|
Recovery | N/A |
tmnxOamPingTestFailedV3
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2002 |
Event name | tmnxOamPingTestFailedV3 |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamPingNotifications.9 |
Default severity | minor |
Message format string | OAM $tmnxOamPingCtlTestMode$ test " $tmnxOamPingCtlTestIndex$" created by "$tmnxOamPingCtlOwnerIndex$" run # $tmnxOamPingResultsTestRunIndex$ failed |
|
Cause | A ping test failed when the corresponding tmnxOamPingCtlTrapGeneration object is set to testFailure(1). In this instance tmnxOamPingCtlTrapTestFailureFilter specifies the number of probes in a test required to have failed in order to consider the test as failed. |
Effect | N/A |
|
Recovery | N/A |
tmnxOamPmThrClear
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2301 |
Event name | tmnxOamPmThrClear |
SNMP notification prefix and OID | TIMETRA-OAM-PM-MIB.tmnxOamPmNotifications.2 |
Default severity | warning |
Message format string | OAM-PM TCA cleared for session " $tmnxOamPmCfgSessName$", test type $tmnxOamPmStsBaseTestType$, measurement interval duration $tmnxOamPmStsMeasIntvlDuration$, MI start $tmnxOamPmStsBaseStartTime$ UTC, delay bin type $tmnxOamPmNotifThrDelayBinType$. Threshold type $tmnxOamPmNotifThrType$, direction $tmnxOamPmNotifThrDirection$, bin lower bound (us) $tmnxOamPmNotifThrBinLowerBound$, configured threshold $tmnxOamPmNotifThrCfgClear$, operational value $tmnxOamPmNotifThrOperClear$. TCA type $tmnxOamPmNotifThrStateType$, suspect flag $tmnxOamPmStsBaseSuspect$. |
Cause | A tmnxOamPmThrClear trap is sent at the end of an OAM-PM measurement interval when a loss or delay counter meets or falls below its configured Clear threshold. At most one tmnxOamPmThrClear trap is sent per tmnxOamPmThrRaise trap. OAM-PM thresholds are explained in the description clauses of tmnxOamPmCfgThrDelayTable, tmnxOamPmCfgThrLossFwBwAgTable, and tmnxOamPmCfgThrLossFwBwTable. OAM-PM counters are explained in the description clauses of the tmnxOamPmStatsTableObjs tables. |
Effect | For an LMM test, the loss of live traffic has met or fallen below a configured threshold. For other test types, the loss or delay of OAM-PM test probes has met or fallen below a configured threshold, indicating a possible improvement in the loss or delay of live traffic. |
Recovery | No recovery is required for this trap. |
tmnxOamPmThrRaise
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2300 |
Event name | tmnxOamPmThrRaise |
SNMP notification prefix and OID | TIMETRA-OAM-PM-MIB.tmnxOamPmNotifications.1 |
Default severity | warning |
Message format string | OAM-PM TCA raised for session " $tmnxOamPmCfgSessName$", test type $tmnxOamPmStsBaseTestType$, measurement interval duration $tmnxOamPmStsMeasIntvlDuration$, MI start $tmnxOamPmStsBaseStartTime$ UTC, delay bin type $tmnxOamPmNotifThrDelayBinType$. Threshold type $tmnxOamPmNotifThrType$, direction $tmnxOamPmNotifThrDirection$, bin lower bound (us) $tmnxOamPmNotifThrBinLowerBound$, configured threshold $tmnxOamPmNotifThrCfgRaise$, operational value $tmnxOamPmNotifThrOperRaise$. TCA type $tmnxOamPmNotifThrStateType$, suspect flag $tmnxOamPmStsBaseSuspect$. |
Cause | A tmnxOamPmThrRaise trap is sent when an OAM-PM loss or delay counter meets or exceeds its configured Raise threshold. If an Average Frame Loss Ratio (FLR) threshold (i.e. tmnxOamPmCfgThrLossAvgFlrRaise) is met or exceeded, the tmnxOamPmThrRaise trap is sent at the end of the measurement interval. If another type of threshold (e.g. tmnxOamPmCfgThrLossHliRaise) is met or exceeded, the tmnxOamPmThrRaise trap is sent when the problem is detected. The Average FLR threshold is a special case because the measured Average FLR can fluctuate during a measurement interval. At most one tmnxOamPmThrRaise trap is sent per threshold type during one OAM-PM measurement interval. For example, at most one tmnxOamPmThrRaise trap is sent to record an excessive High Loss Indicator (HLI) count in the forward direction seen in a particular 15 minute interval belonging to the SLM test belonging to OAM-PM session 'oamPmSession1'. OAM-PM thresholds are explained in the description clauses of tmnxOamPmCfgThrDelayTable, tmnxOamPmCfgThrLossFwBwAgTable, and tmnxOamPmCfgThrLossFwBwTable. OAM-PM counters are explained in the description clauses of the tmnxOamPmStatsTableObjs tables. |
Effect | For an LMM test, the loss of live traffic has met or exceeded a configured threshold. For the other test types, the loss or delay of OAM-PM test probes has met or exceeded a configured threshold, indicating possible excessive loss or excessive delay of live traffic. |
Recovery | Fix the cause of the excessive loss or excessive delay. |
tmnxOamSaaThreshold
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2101 |
Event name | tmnxOamSaaThreshold |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamSaaNotifications.1 |
Default severity | minor |
Message format string | OAM SAA $tmnxOamSaaCtlTestMode$ test " $tmnxOamSaaCtlTestIndex$" created by "$tmnxOamSaaCtlOwnerIndex$" run # $tmnxOamSaaTTestRunIndex$ crossed $tmnxOamSaaTDirection$ $tmnxOamSaaTType$ threshold $tmnxOamSaaTThreshold$ with value $tmnxOamSaaTValue$ |
Cause |
At the completion of an SAA OAM trace route test the threshold has been crossed for a results statistic. |
Effect | N/A |
|
Recovery | N/A |
tmnxOamSathSvcStrmCompleted
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2401 |
Event name | tmnxOamSathSvcStrmCompleted |
SNMP notification prefix and OID | TIMETRA-OAM-SERV-ACTIV-TEST-MIB.tmnxOamSathNotifications.2 |
Default severity | warning |
Message format string | Service activation service test " $tmnxOamSathCfgSvcTestName$" run $tmnxOamSathStsSvcTestRun$ service stream $tmnxOamSathCfgSvcStrmNum$ completed ($tmnxOamSathStsSvcStrmOprState$) |
Cause | The tmnxOamSathSvcStrmCompleted notification is sent at the end of a Y.1564 service-stream run. |
Effect | Informational. If the service-stream run failed, a live deployment of the services owned by the service-stream may fail. |
Recovery | If the service-stream run failed, investigate the cause. |
tmnxOamSathSvcTestCompleted
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2400 |
Event name | tmnxOamSathSvcTestCompleted |
SNMP notification prefix and OID | TIMETRA-OAM-SERV-ACTIV-TEST-MIB.tmnxOamSathNotifications.1 |
Default severity | warning |
Message format string | Service activation service test " $tmnxOamSathCfgSvcTestName$" run $tmnxOamSathStsSvcTestRun$ completed ( $tmnxOamSathStsSvcTestOprState$) |
Cause |
The tmnxOamSathSvcTestCompleted notification is sent at the end of a Y.1564 service-test run. |
Effect | Informational. If the service-test run failed, a live deployment of the services owned by the service-test may fail. |
Recovery | If the service-test run failed, investigate the cause. |
tmnxOamTrPathChange
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2050 |
Event name | tmnxOamTrPathChange |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamTraceRouteNotifications.1 |
Default severity | minor |
Message format string | OAM $tmnxOamTrCtlTestMode$ test " $tmnxOamTrCtlTestIndex$" created by "$tmnxOamTrCtlOwnerIndex$" run # $tmnxOamTrResultsTestRunIndex$ path changed |
Cause | The path to a target has changed. |
Effect | N/A |
|
Recovery | N/A |
tmnxOamTrTestCompleted
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2052 |
Event name | tmnxOamTrTestCompleted |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamTraceRouteNotifications.3 |
Default severity | minor |
Message format string | OAM $tmnxOamTrCtlTestMode$ test " $tmnxOamTrCtlTestIndex$" created by "$tmnxOamTrCtlOwnerIndex$" run # $tmnxOamTrResultsTestRunIndex$ completed |
|
Cause | The OAM trace route test has just completed. |
Effect | N/A |
|
Recovery | N/A |
tmnxOamTrTestFailed
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2051 |
Event name | tmnxOamTrTestFailed |
SNMP notification prefix and OID | TIMETRA-OAM-TEST-MIB.tmnxOamTraceRouteNotifications.2 |
Default severity | minor |
Message format string | OAM $tmnxOamTrCtlTestMode$ test " $tmnxOamTrCtlTestIndex$" created by "$tmnxOamTrCtlOwnerIndex$" run # $tmnxOamTrResultsTestRunIndex$ failed |
|
Cause | The OAM trace route test failed to complete successfully. |
Effect | N/A |
|
Recovery | N/A |
tmnxTwampRflInactivityTimeout
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2205 |
Event name | tmnxTwampRflInactivityTimeout |
SNMP notification prefix and OID | TIMETRA-TWAMP-MIB.tmnxTwampNotifications.6 |
Default severity | minor |
Message format string | TWAMP Reflector test session localAddr $tmnxTwampRflNotifLocalAddr$ port $tmnxTwampRflNotifLocalUdpPort$ remoteAddr $tmnxTwampRflNotifRemoteAddr$ port $tmnxTwampRflNotifRemoteUdpPort$ disconnected because REFWAIT expired, Client Connection Addr $tmnxTwampSrvNotifClientAddr$ |
Cause |
The tmnxTwampRflInactivityTimeout notification is generated when a TWAMP test session is disconnected by the TWAMP Reflector because the session was inactive for a period exceeding the reflector's inactivity timeout (tmnxTwampRflInactTimeout). |
Effect | The TWAMP reflector cannot receive any traffic on the disconnected session. |
Recovery | Check the IP connectivity between this reflector and the TWAMP client. |
tmnxTwampSrvInactivityTimeout
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2200 |
Event name | tmnxTwampSrvInactivityTimeout |
SNMP notification prefix and OID | TIMETRA-TWAMP-MIB.tmnxTwampNotifications.1 |
Default severity | minor |
Message format string | TWAMP server control connection to client $tmnxTwampSrvConnClientAddr$ disconnected because it was inactive for $tmnxTwampSrvConnIdleTime$ seconds |
|
Cause | The tmnxTwampSrvInactivityTimeout notification is generated when a TWAMP control connection was disconnected by the TWAMP server because the connection was inactive for a period exceeding the server's inactivity timeout (tmnxTwampSrvInactTimeout). |
Effect | The TWAMP client cannot request test runs on the disconnected connection. |
Recovery | Check the IP connectivity between this node and the TWAMP client. |
tmnxTwampSrvMaxConnsExceeded
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2201 |
Event name | tmnxTwampSrvMaxConnsExceeded |
SNMP notification prefix and OID | TIMETRA-TWAMP-MIB.tmnxTwampNotifications.2 |
Default severity | minor |
Message format string | TWAMP server control connection to client $tmnxTwampSrvNotifClientAddr$ could not be established because the system limit ( $tmnxTwampSrvConnectionCount$ concurrent connections) has been reached |
Cause | The tmnxTwampSrvMaxConnsExceeded notification is generated when a TWAMP control connection could not be established by the TWAMP server because the system-level maximum number of concurrent TWAMP control connections (tmnxTwampSrvMaxConnections) has been reached. |
Effect | The TWAMP client cannot request test runs on the rejected connection. |
Recovery | Configure the system-level maximum number of concurrent TWAMP control connections to a larger value, or disconnect any TWAMP control connection. |
tmnxTwampSrvMaxSessExceeded
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2203 |
Event name | tmnxTwampSrvMaxSessExceeded |
SNMP notification prefix and OID | TIMETRA-TWAMP-MIB.tmnxTwampNotifications.4 |
Default severity | minor |
Message format string | TWAMP server session to client $tmnxTwampSrvNotifClientAddr$ could not be established because the system limit ( $tmnxTwampSrvSessionCount$ concurrent sessions) has been reached |
Cause | The tmnxTwampSrvMaxSessExceeded notification is generated when a TWAMP session could not be established by the TWAMP server because the system-level maximum number of concurrent TWAMP sessions (tmnxTwampSrvMaxSessions) has been reached. |
Effect | The TWAMP client cannot request test runs on the rejected session. |
Recovery | Configure the system-level maximum number of concurrent TWAMP sessions to a larger value, or disconnect any TWAMP session. |
tmnxTwampSrvPfxMaxConnsExceeded
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2202 |
Event name | tmnxTwampSrvPfxMaxConnsExceeded |
SNMP notification prefix and OID | TIMETRA-TWAMP-MIB.tmnxTwampNotifications.3 |
Default severity | minor |
Message format string | TWAMP server control connection to client $tmnxTwampSrvNotifClientAddr$ could not be established because the limit for prefix $tmnxTwampSrvPrefixAddr$/$tmnxTwampSrvPrefixLen$ ($tmnxTwampSrvPfxConnCount$ concurrent connections) has been reached |
Cause | The tmnxTwampSrvPfxMaxConnsExceeded notification is generated when a TWAMP control connection could not be established by the TWAMP server because the maximum number of concurrent TWAMP control connections configured against the TWAMP client's prefix (tmnxTwampSrvPrefixMaxConnections) has been reached. |
Effect | The TWAMP client cannot request test runs on the rejected connection. |
Recovery | Configure the prefix's maximum number of concurrent TWAMP control connections to a larger value, or disconnect a TWAMP control connection which uses the prefix. |
tmnxTwampSrvPfxMaxSessExceeded
|
Property name | Value |
|---|---|
Application name | OAM |
Event ID | 2204 |
Event name | tmnxTwampSrvPfxMaxSessExceeded |
SNMP notification prefix and OID | TIMETRA-TWAMP-MIB.tmnxTwampNotifications.5 |
Default severity | minor |
Message format string | TWAMP server session to client $tmnxTwampSrvNotifClientAddr$ could not be established because the limit for prefix $tmnxTwampSrvPrefixAddr$/$tmnxTwampSrvPrefixLen$ ($tmnxTwampSrvPfxSessionCount$ concurrent sessions) has been reached |
Cause | The tmnxTwampSrvPfxMaxSessExceeded notification is generated when a TWAMP session could not be established by the TWAMP server because the maximum number of concurrent TWAMP sessions configured against the TWAMP client's prefix (tmnxTwampSrvPrefixMaxSessions) has been reached. |
Effect | The TWAMP client cannot request test runs on the rejected session. |
Recovery | Configure the prefix's maximum number of concurrent TWAMP sessions to a larger value, or disconnect a TWAMP session which uses the prefix. |