2. SR Log Events

2.1. ADP

2.1.1. tmnxDiscoveryCellularReq

tmnxDiscoveryCellularReq:ADP
Table 4:  tmnxDiscoveryCellularReq properties 

Property name

Value

Application name

ADP

Event ID

2050

Event name

tmnxDiscoveryCellularReq

SNMP notification prefix and OID

TIMETRA-DISCOVERY-MIB.tmnxDiscoveryNotifications.1

Default severity

minor

Message format string

NMS Cellular PDN Configuration Request sent

Cause

N/A

Effect

N/A

Recovery

N/A

2.1.2. tmnxDiscoveryEndNotify

tmnxDiscoveryEndNotify:ADP
Table 5:  tmnxDiscoveryEndNotify properties 

Property name

Value

Application name

ADP

Event ID

2005

Event name

tmnxDiscoveryEndNotify

SNMP notification prefix and OID

TIMETRA-DISCOVERY-MIB.tmnxDiscoveryNotifications.2

Default severity

minor

Message format string

Auto-Discovery process has ended

Cause

N/A

Effect

N/A

Recovery

N/A

2.2. APPLICATION_ASSURANCE

2.2.1. tmnxBsxAarpInstOperStateChanged

tmnxBsxAarpInstOperStateChanged:APPLICATION_ASSURANCE
Table 6:  tmnxBsxAarpInstOperStateChanged properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4435

Event name

tmnxBsxAarpInstOperStateChanged

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.35

Default severity

warning

Message format string

Status of AARP instance $tmnxBsxAarpInstId$ changed operational state: $tmnxBsxAarpInstOperState$, flags = $tmnxBsxAarpInstOperFlags$

Cause

A tmnxBsxAarpInstOperStateChanged notification is generated when the operational state of the AARP instance changes.

Effect

The transition to an operational state of 'outOfService(3)' indicates that the AARP instance is not performing asymmetry removal.

Recovery

No recovery is required.

2.2.2. tmnxBsxAarpInstStateChanged

tmnxBsxAarpInstStateChanged:APPLICATION_ASSURANCE
Table 7:  tmnxBsxAarpInstStateChanged properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4436

Event name

tmnxBsxAarpInstStateChanged

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.36

Default severity

warning

Message format string

Status of AARP instance $tmnxBsxAarpInstId$ changed state: $tmnxBsxAarpInstState$, flags = $tmnxBsxAarpInstOperFlags$

Cause

A tmnxBsxAarpInstStateChanged notification is generated when the state of the AARP instance changes.

Effect

None.

Recovery

No recovery is required.

2.2.3. tmnxBsxAaSubPolResExceeded

tmnxBsxAaSubPolResExceeded:APPLICATION_ASSURANCE
Table 8:  tmnxBsxAaSubPolResExceeded properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4413

Event name

tmnxBsxAaSubPolResExceeded

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.13

Default severity

warning

Message format string

Policer resources have been exceeded for subscribers in group $tmnxBsxNotifyAaGrpPartIndex$.

Cause

A tmnxBsxAaSubPolResExceeded notification is generated when Application Assurance policer resources have been exceeded for subscribers with the ISA-AA group and partition.

Effect

Subscriber policing is degraded.

Recovery

Recovery from this condition requires the reconfiguration of subscriber policy to reduce the number of policers being applied.

2.2.4. tmnxBsxAaSubPolResExceededClear

tmnxBsxAaSubPolResExceededClear:APPLICATION_ASSURANCE
Table 9:  tmnxBsxAaSubPolResExceededClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4414

Event name

tmnxBsxAaSubPolResExceededClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.14

Default severity

warning

Message format string

Policer resources are no longer exceeded for subscribers in group $tmnxBsxNotifyAaGrpPartIndex$.

Cause

A tmnxBsxAaSubPolResExceededClear notification is generated when Application Assurance policer resources are no longer exceeded for subscribers with the ISA-AA group and partition.

Effect

Policer resources are no longer exceeded for subscribers.

Recovery

None.

2.2.5. tmnxBsxAaSubscriberAcctDataLoss

tmnxBsxAaSubscriberAcctDataLoss:APPLICATION_ASSURANCE
Table 10:  tmnxBsxAaSubscriberAcctDataLoss properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4412

Event name

tmnxBsxAaSubscriberAcctDataLoss

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.12

Default severity

warning

Message format string

Accounting data loss occurred for subscriber $tmnxBsxNotifyAaSubscriberName$.

Cause

A tmnxBsxAaSubscriberAcctDataLoss notification is generated when Application Assurance subscriber statistics cannot be written to the accounting file. This can occur if the accounting interval expires while collecting statistics.

Effect

When this notification is generated it signifies that the statistic records, for this application assurance subscriber, are missing from the accounting file for the indicated interval.

Recovery

No recovery is required.

2.2.6. tmnxBsxAaSubscribersUnassigned

tmnxBsxAaSubscribersUnassigned:APPLICATION_ASSURANCE
Table 11:  tmnxBsxAaSubscribersUnassigned properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4411

Event name

tmnxBsxAaSubscribersUnassigned

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.11

Default severity

warning

Message format string

ISA-AA group $tmnxBsxNotifyIsaAaGroupIndex$ has unassigned subscribers

Cause

A tmnxBsxAaSubscribersUnassigned notification is generated when one or more subscribers for a particular service-id cannot be assigned to an ISA-AA MDA within an Application Assurance group due to insufficient resources. The resources in question include service queues, AA subscriber counts or AA subscriber statistics.

Effect

Unassigned subscribers will behave as specified by the fail-to mode configured within the Application Assurance group.

Recovery

Recovery from this condition requires the removal and re-creation of the AA subscribers when sufficient resources become available.

2.2.7. tmnxBsxCertProfileOperStateChngd

tmnxBsxCertProfileOperStateChngd:APPLICATION_ASSURANCE
Table 12:  tmnxBsxCertProfileOperStateChngd properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4462

Event name

tmnxBsxCertProfileOperStateChngd

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.62

Default severity

minor

Message format string

The operational state of certificate profile $tmnxBsxNotifyCertProfileName$ in ISA-AA Group $tmnxBsxNotifyIsaAaGroupIndex$ is $tmnxBsxNotifyCertProfOperState$. Reason: $tmnxBsxNotifyReason$

Cause

A tmnxBsxCertProfileOperStateChngd notification is generated when the operational state of the certificate-profile is changed. The tmnxBsxNotifyReason will identify the reason. Most common cause are:

- use of a unsupported algorithm.

- use of a key with unsupported key length.

- file permissions

Effect

Functions dependent on the certificate profiles may not work as expected, if the operational state is outOfService(3).

Recovery

Resolve the condition as reported in tmnxBsxNotifyReason.

2.2.8. tmnxBsxDatapathCpuUsage

tmnxBsxDatapathCpuUsage:APPLICATION_ASSURANCE
Table 13:  tmnxBsxDatapathCpuUsage properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4458

Event name

tmnxBsxDatapathCpuUsage

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.58

Default severity

minor

Message format string

Datapath CPU usage is greater than or equal to $tmnxBsxDatapathCpuHighWatermark$% on ISA-AA MDA $tmnxBsxNotifyActiveMda$ in group $tmnxBsxNotifyIsaAaGroupIndex$.

Cause

A tmnxBsxDatapathCpuUsage notification is generated when the current datapath CPU usage on the MDA in the ISA-AA group is greater than or equal to the tmnxBsxDatapathCpuHighWatermark and the prior usage was less than this threshold.

Effect

There is no immediate effect, but when the usage hits the limit of 100%, traffic will be dropped unless the value of tmnxBsxIsaAaGrpOverloadCutThru is 'enabled (1)' for the Application Assurance group.

Recovery

There is no recovery for this notification.

2.2.9. tmnxBsxDatapathCpuUsageClear

tmnxBsxDatapathCpuUsageClear:APPLICATION_ASSURANCE
Table 14:  tmnxBsxDatapathCpuUsageClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4459

Event name

tmnxBsxDatapathCpuUsageClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.59

Default severity

minor

Message format string

Datapath CPU usage is less than or equal to $tmnxBsxDatapathCpuLowWatermark$% on ISA-AA MDA $tmnxBsxNotifyActiveMda$ in group $tmnxBsxNotifyIsaAaGroupIndex$.

Cause

A tmnxBsxDatapathCpuUsageClear notification is generated to indicate a prior tmnxBsxDatapathCpuUsage notification has cleared due to the current datapath CPU usage on the MDA in the ISA-AA group being less than or equal to the tmnxBsxDatapathCpuLowWatermark.

Effect

The tmnxBsxDatapathCpuUsage notification is cleared.

Recovery

There is no recovery for this notification.

2.2.10. tmnxBsxDnsIpCacheFull

tmnxBsxDnsIpCacheFull:APPLICATION_ASSURANCE
Table 15:  tmnxBsxDnsIpCacheFull properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4444

Event name

tmnxBsxDnsIpCacheFull

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.44

Default severity

minor

Message format string

The usage of ISA-AA Group $tmnxBsxIsaAaGroupIndex$ DNS IP Cache \"$tmnxBsxDnsIpCacheName$\" for ISA-MDA $tmnxBsxNotifyActiveMda$ is greater than or equal to the $tmnxBsxDnsIpCacheHighWatermark$% high watermark. The cache size is $tmnxBsxDnsIpCacheSize$.

Cause

A tmnxBsxDnsIpCacheFull notification is generated when the number of entries in a DNS IP Cache is greater than or equal to the percentage value tmnxBsxDnsIpCacheHighWatermark of its tmnxBsxDnsIpCacheSize and the previous percentage value was less than this threshold.

Effect

The DNS IP Cache is relatively close to being full.

Recovery

The notification can be cleared if enough cache entries timeout to drop below the threshold, or if the cache is cleared, or tmnxBsxDnsIpCacheSize is sufficiently increased.

2.2.11. tmnxBsxDnsIpCacheFullClear

tmnxBsxDnsIpCacheFullClear:APPLICATION_ASSURANCE
Table 16:  tmnxBsxDnsIpCacheFullClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4445

Event name

tmnxBsxDnsIpCacheFullClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.45

Default severity

minor

Message format string

The usage of ISA-AA Group $tmnxBsxIsaAaGroupIndex$ DNS IP Cache \"$tmnxBsxDnsIpCacheName$\" for ISA-MDA $tmnxBsxNotifyActiveMda$ is less than or equal to the $tmnxBsxDnsIpCacheLowWatermark$% low watermark. The cache size is $tmnxBsxDnsIpCacheSize$.

Cause

A tmnxBsxDnsIpCacheFullClear notification is generated when the number of entries in a DNS IP Cache is less than or equal to the percentage value tmnxBsxDnsIpCacheLowWatermark of its tmnxBsxDnsIpCacheSize and the previous percentage value was greater than this threshold.

Effect

The DNS IP Cache is no longer relatively close to being full.

Recovery

No recovery is required.

2.2.12. tmnxBsxHttpUrlParamLimitExceeded

tmnxBsxHttpUrlParamLimitExceeded:APPLICATION_ASSURANCE
Table 17:  tmnxBsxHttpUrlParamLimitExceeded properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4441

Event name

tmnxBsxHttpUrlParamLimitExceeded

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.41

Default severity

minor

Message format string

Subscriber HTTP URL Parameter storage has been exceeded for subscribers in group $tmnxBsxNotifyIsaAaGroupIndex$, reason: $tmnxBsxNotifyReason$

Cause

A tmnxBsxHttpUrlParamLimitExceeded notification is generated when the group limit of unique tmnxBsxAaSubHttpUrlParam values has been exceeded. The tmnxBsxNotifyReason will identify the reason this notification was raised.

Effect

Some subscribers will not have their HTTP URL Parameters applied.

Recovery

No recovery is required.

2.2.13. tmnxBsxIsaAaGrpBitRate

tmnxBsxIsaAaGrpBitRate:APPLICATION_ASSURANCE
Table 18:  tmnxBsxIsaAaGrpBitRate properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4419

Event name

tmnxBsxIsaAaGrpBitRate

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.19

Default severity

warning

Message format string

Bit rate is greater than or equal to $tmnxBsxBitRateHighWatermark$ megabits/s on ISA-AA MDA $tmnxBsxNotifyActiveMda$.

Cause

A tmnxBsxIsaAaGrpBitRate notification is generated when the current bit rate on the MDA in the ISA-AA group is greater than or equal to the tmnxBsxBitRateHighWatermark and the prior rate was less than this threshold.

Effect

None.

Recovery

No recovery is required.

2.2.14. tmnxBsxIsaAaGrpBitRateClear

tmnxBsxIsaAaGrpBitRateClear:APPLICATION_ASSURANCE
Table 19:  tmnxBsxIsaAaGrpBitRateClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4420

Event name

tmnxBsxIsaAaGrpBitRateClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.20

Default severity

warning

Message format string

Bit rate is less than or equal to $tmnxBsxBitRateLowWatermark$ megabits/s on ISA-AA MDA $tmnxBsxNotifyActiveMda$ or corresponding tmnxBsxIsaAaGrpBitRate notification has been disabled.

Cause

A tmnxBsxIsaAaGrpBitRateClear notification is generated to indicate a prior tmnxBsxIsaAaGrpBitRate notification has cleared due to one of the following reasons:

1. The current bit rate on the MDA in the ISA-AA group is less than or equal to the tmnxBsxBitRateLowWatermark.

2. The corresponding tmnxBsxIsaAaGrpBitRate notification has been disabled raising the tmnxBsxBitRateHighWatermark to maximum.

Effect

None.

Recovery

No recovery is required.

2.2.15. tmnxBsxIsaAaGrpCapCostThres

tmnxBsxIsaAaGrpCapCostThres:APPLICATION_ASSURANCE
Table 20:  tmnxBsxIsaAaGrpCapCostThres properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4409

Event name

tmnxBsxIsaAaGrpCapCostThres

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.9

Default severity

warning

Message format string

The capacity cost on ISA-AA MDA $tmnxBsxNotifyActiveMda$ in ISA-AA Group $tmnxBsxIsaAaGroupIndex$ is greater than or equal to the high threshold $tmnxBsxIsaAaGrpCapCostHighThres$

Cause

A tmnxBsxIsaAaGrpCapCostThres notification is generated when the current capacity cost for an MDA within an ISA-AA Group is greater than or equal to the threshold specified by tmnxBsxIsaAaGrpCapCostHighThres and the prior cost was less than this threshold.

Effect

There is no direct adverse effect, however this may indicate that resources are limited. Exhaustion of resources will cause new aa-sub assignment to fail.

Recovery

If resource availability is sufficient, the capacity cost threshold can be increased or the app-profile capacity cost configuration can be reduced. If resources are limited and need to be recovered, remove aa-subs, or add additional isa-aa cards to the group.

2.2.16. tmnxBsxIsaAaGrpCapCostThresClear

tmnxBsxIsaAaGrpCapCostThresClear:APPLICATION_ASSURANCE
Table 21:  tmnxBsxIsaAaGrpCapCostThresClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4410

Event name

tmnxBsxIsaAaGrpCapCostThresClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.10

Default severity

warning

Message format string

The capacity cost on ISA-AA MDA $tmnxBsxNotifyActiveMda$ in ISA-AA Group $tmnxBsxIsaAaGroupIndex$ is less than or equal to the low threshold $tmnxBsxIsaAaGrpCapCostLowThres$

Cause

A tmnxBsxIsaAaGrpCapCostThresClear notification is generated when the current capacity cost for an MDA within an ISA-AA Group is less than or equal to the threshold specified by tmnxBsxIsaAaGrpCapCostLowThres and the prior cost was greater than this threshold.

Effect

None.

Recovery

No recovery is required.

2.2.17. tmnxBsxIsaAaGrpFailureClearV2

tmnxBsxIsaAaGrpFailureClearV2:APPLICATION_ASSURANCE
Table 22:  tmnxBsxIsaAaGrpFailureClearV2 properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4402

Event name

tmnxBsxIsaAaGrpFailureClearV2

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.6

Default severity

warning

Message format string

ISA-AA Group $tmnxBsxNotifyIsaAaGroupIndex$ recovered

Cause

All configured ISA-AA MDAs are in service.

Effect

Service is fully restored.

Recovery

No recovery is required.

2.2.18. tmnxBsxIsaAaGrpFailureV2

tmnxBsxIsaAaGrpFailureV2:APPLICATION_ASSURANCE
Table 23:  tmnxBsxIsaAaGrpFailureV2 properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4401

Event name

tmnxBsxIsaAaGrpFailureV2

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.5

Default severity

major

Message format string

ISA-AA Group $tmnxBsxNotifyIsaAaGroupIndex$ failed

Cause

The ISA-AA Group has no configured primary MDA or the number of active MDAs is not equal to the number of configured primary MDAs.

Effect

Traffic that was to be diverted to the ISA-AA Group will instead have the rule specified in TIMETRA-BSX-NG-MIB::tmnxBsxIsaAaGrpFailToMode applied to it.

Recovery

No recovery is required.

2.2.19. tmnxBsxIsaAaGrpFlowFull

tmnxBsxIsaAaGrpFlowFull:APPLICATION_ASSURANCE
Table 24:  tmnxBsxIsaAaGrpFlowFull properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4405

Event name

tmnxBsxIsaAaGrpFlowFull

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.3

Default severity

major

Message format string

ISA-AA Group $tmnxBsxNotifyIsaAaGroupIndex$ flow record usage is greater than or equal to high watermark. The Active ISA-AA MDA is $tmnxBsxNotifyActiveMda$

Cause

Excessive traffic including denial of service attacks that target flow state exhaustion

Effect

Traffic that is unable to allocate a flow record is treated using policy defined for the subscriber for an "Unknown" protocol.

Recovery

No recovery is required.

2.2.20. tmnxBsxIsaAaGrpFlowFullClear

tmnxBsxIsaAaGrpFlowFullClear:APPLICATION_ASSURANCE
Table 25:  tmnxBsxIsaAaGrpFlowFullClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4407

Event name

tmnxBsxIsaAaGrpFlowFullClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.4

Default severity

warning

Message format string

ISA-AA Group $tmnxBsxNotifyIsaAaGroupIndex$ flow record usage is less than or equal to low watermark. The Active ISA-AA MDA is $tmnxBsxNotifyActiveMda$

Cause

The conditions that caused tmnxBsxIsaAaGrpFlowFull or tmnxBsxIsaAaGrpFlowFull have been alleviated.

Effect

None.

Recovery

No recovery is required.

2.2.21. tmnxBsxIsaAaGrpFlowSetup

tmnxBsxIsaAaGrpFlowSetup:APPLICATION_ASSURANCE
Table 26:  tmnxBsxIsaAaGrpFlowSetup properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4415

Event name

tmnxBsxIsaAaGrpFlowSetup

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.15

Default severity

warning

Message format string

Flow setup rate is greater than or equal to $tmnxBsxFlowSetupHighWatermark$ flows/s on ISA-AA MDA $tmnxBsxNotifyActiveMda$.

Cause

A tmnxBsxIsaAaGrpFlowSetup notification is generated when the current flow setup rate on the MDA in the ISA-AA group is greater than or equal to tmnxBsxFlowSetupHighWatermark and the prior rate was less than this threshold.

Effect

None.

Recovery

No recovery is required.

2.2.22. tmnxBsxIsaAaGrpFlowSetupClear

tmnxBsxIsaAaGrpFlowSetupClear:APPLICATION_ASSURANCE
Table 27:  tmnxBsxIsaAaGrpFlowSetupClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4416

Event name

tmnxBsxIsaAaGrpFlowSetupClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.16

Default severity

warning

Message format string

Flow setup rate is less than or equal to $tmnxBsxFlowSetupLowWatermark$ flows/s on ISA-AA MDA $tmnxBsxNotifyActiveMda$ or corresponding tmnxBsxIsaAaGrpFlowSetup notification has been disabled.

Cause

A tmnxBsxIsaAaGrpFlowSetupClear notification is generated to indicate a prior tmnxBsxIsaAaGrpFlowSetup notification has cleared due to one of the following reasons:

1. The current flow setup rate on the MDA in the ISA-AA group is less than or equal to tmnxBsxFlowSetupLowWatermark.

2. The corresponding tmnxBsxIsaAaGrpFlowSetup notification has been disabled by raising the tmnxBsxFlowSetupHighWatermark to maximum.

Effect

None.

Recovery

No recovery is required.

2.2.23. tmnxBsxIsaAaGrpFmSbWaSBufOvld

tmnxBsxIsaAaGrpFmSbWaSBufOvld:APPLICATION_ASSURANCE
Table 28:  tmnxBsxIsaAaGrpFmSbWaSBufOvld properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4428

Event name

tmnxBsxIsaAaGrpFmSbWaSBufOvld

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.28

Default severity

warning

Message format string

ISA-AA group $tmnxBsxIsaAaGroupIndex$ MDA $tmnxBsxNotifyActiveMda$ wa-shared buffer use is greater than or equal to $tmnxBsxIsaAaGrpFromSubWaSBfHiWmk$ in the from-subscriber direction.

Cause

A tmnxBsxIsaAaGrpFmSbWaSBufOvld is generated when the current weighted average shared buffer use for an ISA in the from-subscriber direction is greater than or equal to a high watermark after being in a normal, non-overloaded, state.

Effect

If ISA overload cut-through is enabled, the ISA MDA performs subscriber level cut-through of all traffic.

Recovery

No recovery is required.

2.2.24. tmnxBsxIsaAaGrpFmSbWaSBufOvldClr

tmnxBsxIsaAaGrpFmSbWaSBufOvldClr:APPLICATION_ASSURANCE
Table 29:  tmnxBsxIsaAaGrpFmSbWaSBufOvldClr properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4429

Event name

tmnxBsxIsaAaGrpFmSbWaSBufOvldClr

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.29

Default severity

warning

Message format string

ISA-AA group $tmnxBsxIsaAaGroupIndex$ MDA $tmnxBsxNotifyActiveMda$ wa-shared buffer use is less than or equal to $tmnxBsxIsaAaGrpFromSubWaSBfLoWmk$ in the from-subscriber direction or corresponding tmnxBsxIsaAaGrpFmSbWaSBufOvld notification has been disabled.

Cause

A tmnxBsxIsaAaGrpFmSbWaSBufOvldClr is generated to indicate a prior tmnxBsxIsaAaGrpFmSbWaSBufOvld notification has cleared due to one of the following reasons:

1. The current weighted average shared buffer use in the from-subscriber direction is less than or equal to a low watermark.

2. The corresponding tmnxBsxIsaAaGrpFmSbWaSBufOvld notification has been disabled by raising the tmnxBsxIsaAaGrpFromSubWaSBfHiWmk to maximum.

Effect

The buffer pool in the from-subscriber direction exits overload. ISA MDA overload cut-through ends if it was in effect and the buffer pools in both directions are no longer overloaded.

Recovery

No recovery is required.

2.2.25. tmnxBsxIsaAaGrpNonRedundantV2

tmnxBsxIsaAaGrpNonRedundantV2:APPLICATION_ASSURANCE
Table 30:  tmnxBsxIsaAaGrpNonRedundantV2 properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4403

Event name

tmnxBsxIsaAaGrpNonRedundantV2

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.7

Default severity

minor

Message format string

ISA-AA Group $tmnxBsxNotifyIsaAaGroupIndex$ has a backup MDA configured, but has no standby MDA available.

Cause

The ISA-AA Group has a configured backup MDA but there is no standby MDA available.

Effect

Traffic is diverted but in the event of a failure of any of the active ISA-AA MDAs, there is no backup ISA-AA MDA to take over.

Recovery

No recovery is required.

2.2.26. tmnxBsxIsaAaGrpOvrldCutthru

tmnxBsxIsaAaGrpOvrldCutthru:APPLICATION_ASSURANCE
Table 31:  tmnxBsxIsaAaGrpOvrldCutthru properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4432

Event name

tmnxBsxIsaAaGrpOvrldCutthru

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.32

Default severity

warning

Message format string

ISA AA Group $tmnxBsxNotifyIsaAaGroupIndex$ MDA $tmnxBsxNotifyActiveMda$ entering overload cut through processing.

Cause

A tmnxBsxIsaAaGrpOvrldCutthru is generated when cut through processing starts on an ISA MDA.

Effect

The ISA MDA performs subscriber level cut-through of all traffic.

Recovery

No recovery is required.

2.2.27. tmnxBsxIsaAaGrpOvrldCutthruClr

tmnxBsxIsaAaGrpOvrldCutthruClr:APPLICATION_ASSURANCE
Table 32:  tmnxBsxIsaAaGrpOvrldCutthruClr properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4433

Event name

tmnxBsxIsaAaGrpOvrldCutthruClr

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.33

Default severity

warning

Message format string

ISA AA Group $tmnxBsxNotifyIsaAaGroupIndex$ MDA $tmnxBsxNotifyActiveMda$ exiting overload cut through processing.

Cause

A tmnxBsxIsaAaGrpOvrldCutthru is generated when cut through processing ends on an ISA MDA.

Effect

The ISA MDA stops performing subscriber level cut-through of all traffic.

Recovery

No recovery is required.

2.2.28. tmnxBsxIsaAaGrpPacketRate

tmnxBsxIsaAaGrpPacketRate:APPLICATION_ASSURANCE
Table 33:  tmnxBsxIsaAaGrpPacketRate properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4417

Event name

tmnxBsxIsaAaGrpPacketRate

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.17

Default severity

warning

Message format string

Packet rate is greater than or equal to $tmnxBsxPacketRateHighWatermark$ packets/s on ISA-AA MDA $tmnxBsxNotifyActiveMda$.

Cause

A tmnxBsxIsaAaGrpPacketRate notification is generated when the current packet rate on the MDA in the ISA-AA group is greater than or equal to the tmnxBsxPacketRateHighWatermark and the prior rate was less than this threshold.

Effect

None.

Recovery

No recovery is required.

2.2.29. tmnxBsxIsaAaGrpPacketRateClear

tmnxBsxIsaAaGrpPacketRateClear:APPLICATION_ASSURANCE
Table 34:  tmnxBsxIsaAaGrpPacketRateClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4418

Event name

tmnxBsxIsaAaGrpPacketRateClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.18

Default severity

warning

Message format string

Packet rate is less than or equal to $tmnxBsxPacketRateLowWatermark$ packets/s on ISA-AA MDA $tmnxBsxNotifyActiveMda$ or corresponding tmnxBsxIsaAaGrpPacketRate notification has been disabled.

Cause

A tmnxBsxIsaAaGrpPacketRateClear notification is generated to indicate a prior tmnxBsxIsaAaGrpPacketRate notification has cleared due to one of the following reasons:

1. The current packet rate on the MDA in the ISA-AA group is less than or equal to the tmnxBsxPacketRateLowWatermark.

2. The corresponding tmnxBsxIsaAaGrpPacketRate notification has been disabled by raising the tmnxBsxPacketRateHighWatermark to maximum.

Effect

None.

Recovery

No recovery is required.

2.2.30. tmnxBsxIsaAaGrpSwitchover

tmnxBsxIsaAaGrpSwitchover:APPLICATION_ASSURANCE
Table 35:  tmnxBsxIsaAaGrpSwitchover properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4404

Event name

tmnxBsxIsaAaGrpSwitchover

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.2

Default severity

warning

Message format string

ISA-AA Group $tmnxBsxNotifyIsaAaGroupIndex$ has switched activity. The Active ISA-AA MDA is now $tmnxBsxNotifyActiveMda$

Cause

Other events will show the reason that the activity switch occurred.

Effect

A small amount of traffic may be lost during the activity switch.

Recovery

No recovery is required.

2.2.31. tmnxBsxIsaAaGrpToSbWaSBufOvld

tmnxBsxIsaAaGrpToSbWaSBufOvld:APPLICATION_ASSURANCE
Table 36:  tmnxBsxIsaAaGrpToSbWaSBufOvld properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4430

Event name

tmnxBsxIsaAaGrpToSbWaSBufOvld

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.30

Default severity

warning

Message format string

ISA-AA group $tmnxBsxIsaAaGroupIndex$ MDA $tmnxBsxNotifyActiveMda$ wa-shared buffer use is greater than or equal to $tmnxBsxIsaAaGrpToSubWaSBfHiWmk$ in the to-subscriber direction.

Cause

A tmnxBsxIsaAaGrpToSbWaSBufOvld is generated when the current weighted average shared buffer use for an ISA in the to-subscriber direction is greater than or equal to a high watermark after being in a normal, non-overloaded, state.

Effect

If ISA overload cut through is enabled, the ISA MDA performs subscriber level cut-through of all traffic.

Recovery

No recovery is required.

2.2.32. tmnxBsxIsaAaGrpToSbWaSBufOvldClr

tmnxBsxIsaAaGrpToSbWaSBufOvldClr:APPLICATION_ASSURANCE
Table 37:  tmnxBsxIsaAaGrpToSbWaSBufOvldClr properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4431

Event name

tmnxBsxIsaAaGrpToSbWaSBufOvldClr

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.31

Default severity

warning

Message format string

ISA-AA group $tmnxBsxIsaAaGroupIndex$ MDA $tmnxBsxNotifyActiveMda$ wa-shared buffer use is less than or equal to $tmnxBsxIsaAaGrpToSubWaSBfLoWmk$ in the to-subscriber direction or corresponding tmnxBsxIsaAaGrpToSbWaSBufOvld notification has been disabled.

Cause

A tmnxBsxIsaAaGrpToSbWaSBufOvldClr is generated to indicate a prior tmnxBsxIsaAaGrpToSbWaSBufOvld notification has cleared due to one of the following reasons:

1. The weighted average shared buffer use for an ISA in the to-subscriber direction is less than or equal to a low watermark.

2. The corresponding tmnxBsxIsaAaGrpToSbWaSBufOvld notification has been disabled by raising the tmnxBsxIsaAaGrpToSubWaSBfHiWmk to maximum.

Effect

The buffer pool in the to-subscriber direction exits overload. ISA MDA overload cut-through ends if it was in effect and the buffer pools in both directions are no longer overloaded.

Recovery

No recovery is required.

2.2.33. tmnxBsxIsaAaSubLoadBalance

tmnxBsxIsaAaSubLoadBalance:APPLICATION_ASSURANCE
Table 38:  tmnxBsxIsaAaSubLoadBalance properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4408

Event name

tmnxBsxIsaAaSubLoadBalance

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.8

Default severity

warning

Message format string

Subscriber load-balancing operation for ISA-AA Group $tmnxBsxNotifyIsaAaGroupIndex$, $tmnxBsxNotifyActionStatus$

Cause

Triggered by an operator.

Effect

A small amount of traffic may be lost for balanced subscribers.

Recovery

No recovery is required.

2.2.34. tmnxBsxIsaAaTimFileProcFailure

tmnxBsxIsaAaTimFileProcFailure:APPLICATION_ASSURANCE
Table 39:  tmnxBsxIsaAaTimFileProcFailure properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4448

Event name

tmnxBsxIsaAaTimFileProcFailure

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.48

Default severity

minor

Message format string

Failed to process isa-aa.tim file with reason: $tmnxBsxNotifyReason$.

Cause

A tmnxBsxIsaAaTimFileProcFailure notification is generated when a problem is encountered while attempting to process the isa-aa.tim file from the boot options file (BOF) images directory. The tmnxBsxNotifyReason will identify the reason this notification was raised.

Effect

The isa-aa.tim file cannot be processed.

Recovery

Based on the reason noted in tmnxBsxNotifyReason, if necessary take action to ensure that a valid isa-aa.tim file, compatible with the running CPM software version, is located in the images directory configured in the BOF. If successive attempts to load the isa-aa.tim fail, please contact Nokia customer support.

2.2.35. tmnxBsxMobileSubModifyFailure

tmnxBsxMobileSubModifyFailure:APPLICATION_ASSURANCE
Table 40:  tmnxBsxMobileSubModifyFailure properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4439

Event name

tmnxBsxMobileSubModifyFailure

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.39

Default severity

minor

Message format string

Failed to modify a subscriber in group $tmnxBsxNotifyAaGrpPartIndex$ with reason: $tmnxBsxNotifyReason$.

Cause

A tmnxBsxMobileSubModifyFailure notification is generated when attempting to apply an override (app-profile or ASO) to a subscriber based on information received from the ISA-MG. The tmnxBsxNotifyReason will identify the reason this trap was raised.

Effect

The override will not be applied to the subscriber.

Recovery

Based on the reason noted in tmnxBsxNotifyReason, if necessary take action to ensure that a configuration mis-match has not occurred to allow the overrides to be applied appropriately.

2.2.36. tmnxBsxRadApFailure

tmnxBsxRadApFailure:APPLICATION_ASSURANCE
Table 41:  tmnxBsxRadApFailure properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4437

Event name

tmnxBsxRadApFailure

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.37

Default severity

warning

Message format string

A RADIUS accounting request failed to be sent to any of the RADIUS servers in accounting policy $tmnxBsxRadApName$ with reason: $tmnxBsxNotifyReason$.

Cause

The tmnxBsxRadApFailure notification is generated when a RADIUS accounting request was not successfully sent to any of the RADIUS servers in the accounting policy.

Effect

Accounting data for current subscribers will not be exported externally.

Recovery

Based on the reason noted in tmnxBsxNotifyReason, if necessary take action to ensure that the next RADIUS accounting request will be successfully sent.

2.2.37. tmnxBsxRadApIntrmUpdateSkipped

tmnxBsxRadApIntrmUpdateSkipped:APPLICATION_ASSURANCE
Table 42:  tmnxBsxRadApIntrmUpdateSkipped properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4440

Event name

tmnxBsxRadApIntrmUpdateSkipped

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.40

Default severity

minor

Message format string

Interim update interval, configured as $tmnxBsxRadApIntrmUpdateInterval$ minutes, has been ignored.

Cause

The tmnxBsxRadApIntrmUpdateSkipped notification is generated when an interim update has been triggered while subscriber accounting information is still being sent for the previous interim update interval.

Effect

Accounting data for this interim update will not be sent.

Recovery

If this continues to occur consider increasing the RADIUS Accounting interim update interval (tmnxBsxRadApIntrmUpdateInterval).

2.2.38. tmnxBsxRadApServOperStateChange

tmnxBsxRadApServOperStateChange:APPLICATION_ASSURANCE
Table 43:  tmnxBsxRadApServOperStateChange properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4438

Event name

tmnxBsxRadApServOperStateChange

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.38

Default severity

warning

Message format string

AA RADIUS accounting policy $tmnxBsxRadApName$ server $tmnxBsxRadApServIndex$ address $tmnxBsxRadApServAddr$ state changed to $tmnxBsxRadApServOperState$.

Cause

The tmnxBsxRadApServOperStateChange notification is generated when the operational status of an AA RADIUS accounting policy server has transitioned either from 'inService' to 'outOfService' or from 'outOfService' to 'inService'.

Effect

None.

Recovery

No recovery is required.

2.2.39. tmnxBsxStatFtrEnTcaThreshCrClear

tmnxBsxStatFtrEnTcaThreshCrClear:APPLICATION_ASSURANCE
Table 44:  tmnxBsxStatFtrEnTcaThreshCrClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4456

Event name

tmnxBsxStatFtrEnTcaThreshCrClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.56

Default severity

minor

Message format string

Threshold Crossing Alert cleared for ISA-AA Group $tmnxBsxNotifyAaGrpPartIndex$ $tmnxBsxNotifyTcaCfgFilterType$ \"$tmnxBsxNotifyTcaCfgFilterName$\" entry $tmnxBsxNotifyTcaFtrEnCfgEntryId$ in the $tmnxBsxNotifyTcaCfgDirection$ direction ($tmnxBsxNotifyReason$).

Cause

A tmnxBsxStatFtrEnTcaThreshCrClear notification is generated when the utilization matching a tmnxBsxStatTcaFtrEnCfgEntry in the past minute is less than or equal to the value of tmnxBsxStatTcaFtrEnCfgLoWmark and tmnxBsxStatFtrEnTcaThreshCrossed is currently raised. The tmnxBsxNotifyReason will identify the utilization.

Effect

The tmnxBsxStatFtrEnTcaThreshCrossed notification is cleared.

Recovery

There is no recovery for this notification.

2.2.40. tmnxBsxStatFtrEnTcaThreshCrossed

tmnxBsxStatFtrEnTcaThreshCrossed:APPLICATION_ASSURANCE
Table 45:  tmnxBsxStatFtrEnTcaThreshCrossed properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4455

Event name

tmnxBsxStatFtrEnTcaThreshCrossed

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.55

Default severity

minor

Message format string

Threshold Crossing Alert raised for ISA-AA Group $tmnxBsxNotifyAaGrpPartIndex$ $tmnxBsxNotifyTcaCfgFilterType$ \"$tmnxBsxNotifyTcaCfgFilterName$\" entry $tmnxBsxNotifyTcaFtrEnCfgEntryId$ in the $tmnxBsxNotifyTcaCfgDirection$ direction ($tmnxBsxNotifyReason$).

Cause

A tmnxBsxStatFtrEnTcaThreshCrossed notification is generated when the utilization matching a tmnxBsxStatTcaFtrEnCfgEntry in the past minute is greater than or equal to the value of tmnxBsxStatTcaFtrEnCfgHiWmark and the notification is not currently raised for the same entry. The tmnxBsxNotifyReason will identify the utilization.

Effect

There is no effect for this notification.

Recovery

There is no recovery for this notification.

2.2.41. tmnxBsxStatFtrTcaThreshCrClear

tmnxBsxStatFtrTcaThreshCrClear:APPLICATION_ASSURANCE
Table 46:  tmnxBsxStatFtrTcaThreshCrClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4454

Event name

tmnxBsxStatFtrTcaThreshCrClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.54

Default severity

minor

Message format string

Threshold Crossing Alert cleared for ISA-AA Group $tmnxBsxNotifyAaGrpPartIndex$ $tmnxBsxNotifyTcaCfgFilterType$ \"$tmnxBsxNotifyTcaCfgFilterName$\" $tmnxBsxNotifyTcaCfgFltrWmarkType$ in the $tmnxBsxNotifyTcaCfgDirection$ direction ($tmnxBsxNotifyReason$).

Cause

A tmnxBsxStatFtrTcaThreshCrClear notification is generated when the utilization matching a tmnxBsxStatTcaFtrCfgEntry in the past minute is less than or equal to the value of tmnxBsxStatTcaFtrCfgLoWmark and tmnxBsxStatFtrTcaThreshCrossed is currently raised. The tmnxBsxNotifyReason will identify the utilization.

Effect

The tmnxBsxStatFtrTcaThreshCrossed notification is cleared.

Recovery

There is no recovery for this notification.

2.2.42. tmnxBsxStatFtrTcaThreshCrossed

tmnxBsxStatFtrTcaThreshCrossed:APPLICATION_ASSURANCE
Table 47:  tmnxBsxStatFtrTcaThreshCrossed properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4453

Event name

tmnxBsxStatFtrTcaThreshCrossed

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.53

Default severity

minor

Message format string

Threshold Crossing Alert raised for ISA-AA Group $tmnxBsxNotifyAaGrpPartIndex$ $tmnxBsxNotifyTcaCfgFilterType$ \"$tmnxBsxNotifyTcaCfgFilterName$\" $tmnxBsxNotifyTcaCfgFltrWmarkType$ in the $tmnxBsxNotifyTcaCfgDirection$ direction ($tmnxBsxNotifyReason$).

Cause

A tmnxBsxStatFtrTcaThreshCrossed notification is generated when the utilization matching a tmnxBsxStatTcaFtrCfgEntry in the past minute is greater than or equal to the value of tmnxBsxStatTcaFtrCfgHiWmark and the notification is not currently raised for the same entry. The tmnxBsxNotifyReason will identify the utilization.

Effect

There is no effect for this notification.

Recovery

There is no recovery for this notification.

2.2.43. tmnxBsxStatPolcrTcaThreshCrClear

tmnxBsxStatPolcrTcaThreshCrClear:APPLICATION_ASSURANCE
Table 48:  tmnxBsxStatPolcrTcaThreshCrClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4452

Event name

tmnxBsxStatPolcrTcaThreshCrClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.52

Default severity

minor

Message format string

Threshold Crossing Alert cleared for ISA-AA Group $tmnxBsxNotifyAaGrpPartIndex$ policer \"$tmnxBsxNotifyTcaPolicerName$\" in the $tmnxBsxNotifyTcaCfgDirection$ direction ($tmnxBsxNotifyReason$).

Cause

A tmnxBsxStatPolcrTcaThreshCrClear notification is generated when the utilization matching a tmnxBsxStatTcaPolcrCfgEntry in the past minute is less than or equal to the value of tmnxBsxStatTcaPolcrCfgLoWmark and tmnxBsxStatPolcrTcaThreshCrossed is currently raised. The tmnxBsxNotifyReason will identify the utilization.

Effect

The tmnxBsxStatPolcrTcaThreshCrossed notification is cleared.

Recovery

There is no recovery for this notification.

2.2.44. tmnxBsxStatPolcrTcaThreshCrossed

tmnxBsxStatPolcrTcaThreshCrossed:APPLICATION_ASSURANCE
Table 49:  tmnxBsxStatPolcrTcaThreshCrossed properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4451

Event name

tmnxBsxStatPolcrTcaThreshCrossed

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.51

Default severity

minor

Message format string

Threshold Crossing Alert raised for ISA-AA Group $tmnxBsxNotifyAaGrpPartIndex$ policer \"$tmnxBsxNotifyTcaPolicerName$\" in the $tmnxBsxNotifyTcaCfgDirection$ direction ($tmnxBsxNotifyReason$).

Cause

A tmnxBsxStatPolcrTcaThreshCrossed notification is generated when the utilization matching a tmnxBsxStatTcaPolcrCfgEntry in the past minute is greater than or equal to the value of tmnxBsxStatTcaPolcrCfgHiWmark and the notification is not currently raised for the same entry. The tmnxBsxNotifyReason will identify the utilization.

Effect

There is no effect for this notification.

Recovery

There is no recovery for this notification.

2.2.45. tmnxBsxStatTcaThreshCrossed

tmnxBsxStatTcaThreshCrossed:APPLICATION_ASSURANCE
Table 50:  tmnxBsxStatTcaThreshCrossed properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4449

Event name

tmnxBsxStatTcaThreshCrossed

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.49

Default severity

minor

Message format string

Threshold Crossing Alert raised for ISA-AA Group $tmnxBsxNotifyAaGrpPartIndex$ $tmnxBsxNotifyTcaCfgType$ in the $tmnxBsxNotifyTcaCfgDirection$ direction ($tmnxBsxNotifyReason$).

Cause

A tmnxBsxStatTcaThreshCrossed notification is generated when the utilization matching a tmnxBsxStatTcaCfgEntry in the past minute is greater than or equal to the value of tmnxBsxStatTcaCfgHiWmark and the notification is not currently raised for the same entry. The tmnxBsxNotifyReason will identify the utilization.

Effect

There is no effect for this notification.

Recovery

There is no recovery for this notification.

2.2.46. tmnxBsxStatTcaThreshCrossedClear

tmnxBsxStatTcaThreshCrossedClear:APPLICATION_ASSURANCE
Table 51:  tmnxBsxStatTcaThreshCrossedClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4450

Event name

tmnxBsxStatTcaThreshCrossedClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.50

Default severity

minor

Message format string

Threshold Crossing Alert cleared for ISA-AA Group $tmnxBsxNotifyAaGrpPartIndex$ $tmnxBsxNotifyTcaCfgType$ in the $tmnxBsxNotifyTcaCfgDirection$ direction ($tmnxBsxNotifyReason$).

Cause

A tmnxBsxStatTcaThreshCrossedClear notification is generated when the utilization matching a tmnxBsxStatTcaCfgEntry in the past minute is less than or equal to the value of tmnxBsxStatTcaCfgLoWmark and tmnxBsxStatTcaThreshCrossed is currently raised. The tmnxBsxNotifyReason will identify the utilization.

Effect

The tmnxBsxStatTcaThreshCrossed notification is cleared.

Recovery

There is no recovery for this notification.

2.2.47. tmnxBsxSubModifyFailure

tmnxBsxSubModifyFailure:APPLICATION_ASSURANCE
Table 52:  tmnxBsxSubModifyFailure properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4443

Event name

tmnxBsxSubModifyFailure

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.43

Default severity

minor

Message format string

Failed to $tmnxBsxNotifySubFailedAction$ a subscriber in group $tmnxBsxNotifyAaGrpPartIndex$ on ISA-MDA $tmnxBsxNotifyActiveMda$ with reason: $tmnxBsxNotifyReason$.

Cause

A tmnxBsxSubModifyFailure notification is generated when a problem is encountered while attempting to apply an override (app-profile or ASO) to a subscriber based on information received from the Policy Server. The tmnxBsxNotifyReason will identify the reason this notification was raised.

Effect

The override is not applied to the subscriber.

Recovery

Based on the reason noted in tmnxBsxNotifyReason, if necessary take action to ensure that a configuration mismatch has not occurred to allow the overrides to be applied appropriately.

2.2.48. tmnxBsxSubQuarantined

tmnxBsxSubQuarantined:APPLICATION_ASSURANCE
Table 53:  tmnxBsxSubQuarantined properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4463

Event name

tmnxBsxSubQuarantined

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.63

Default severity

minor

Message format string

$tmnxBsxAaSubscriberType$ subscriber $tmnxBsxAaSubscriber$ added to quarantine

Cause

A tmnxBsxSubQuarantined notification is generated when a subscriber enters quarantined state.

Effect

The subscriber traffic will be marked as 'best effort' and colored as 'exceed profile' which will cause early discards.

Recovery

The subscriber quarantine must be removed manually using the tools command.

2.2.49. tmnxBsxSubQuarantinedClear

tmnxBsxSubQuarantinedClear:APPLICATION_ASSURANCE
Table 54:  tmnxBsxSubQuarantinedClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4464

Event name

tmnxBsxSubQuarantinedClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.64

Default severity

minor

Message format string

$tmnxBsxAaSubscriberType$ subscriber $tmnxBsxAaSubscriber$ removed from quarantine

Cause

A tmnxBsxSubQuarantined notification is generated when a subscriber exits quarantined state.

Effect

The tmnxBsxTcpValTcaCrossed notification is cleared.

Recovery

There is no recovery for this notification.

2.2.50. tmnxBsxTcpValTcaCrossed

tmnxBsxTcpValTcaCrossed:APPLICATION_ASSURANCE
Table 55:  tmnxBsxTcpValTcaCrossed properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4460

Event name

tmnxBsxTcpValTcaCrossed

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.60

Default severity

minor

Message format string

Threshold Crossing Alert raised for ISA-AA Group $tmnxBsxNotifyAaGrpPartIndex$ TCP validate \"$tmnxBsxNotifyTcpValTcaName$\" in the $tmnxBsxNotifyTcaCfgDirection$ direction ($tmnxBsxNotifyReason$).

Cause

A tmnxBsxTcpValTcaCrossed notification is generated when the utilization matching a tmnxBsxTcpValTcaEntry in the past minute is greater than or equal to the value of tmnxBsxTcpValTcaHighWatermark and the notification is not currently raised for the same entry. The tmnxBsxNotifyReason will identify the utilization.

Effect

There is no effect for this notification.

Recovery

There is no recovery for this notification.

2.2.51. tmnxBsxTcpValTcaCrossedClear

tmnxBsxTcpValTcaCrossedClear:APPLICATION_ASSURANCE
Table 56:  tmnxBsxTcpValTcaCrossedClear properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4461

Event name

tmnxBsxTcpValTcaCrossedClear

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.61

Default severity

minor

Message format string

Threshold Crossing Alert cleared for ISA-AA Group $tmnxBsxNotifyAaGrpPartIndex$ TCP validate \"$tmnxBsxNotifyTcpValTcaName$\" in the $tmnxBsxNotifyTcaCfgDirection$ direction ($tmnxBsxNotifyReason$).

Cause

A tmnxBsxTcpValTcaCrossedClear notification is generated when the utilization matching a tmnxBsxTcpValTcaEntry in the past minute is less than or equal to the value of tmnxBsxTcpValTcaLowWatermark and tmnxBsxTcpValTcaCrossed is currently raised. The tmnxBsxNotifyReason will identify the utilization.

Effect

The tmnxBsxTcpValTcaCrossed notification is cleared.

Recovery

There is no recovery for this notification.

2.2.52. tmnxBsxTransIpPolAaSubCreated

tmnxBsxTransIpPolAaSubCreated:APPLICATION_ASSURANCE
Table 57:  tmnxBsxTransIpPolAaSubCreated properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4421

Event name

tmnxBsxTransIpPolAaSubCreated

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.21

Default severity

warning

Message format string

A dynamic transit subscriber $tmnxBsxNotifyAaSubscriberName$ has been created in group-partition $tmnxBsxNotifyAaGrpPartIndex$ transit IP policy $tmnxBsxNotifyTransitIpPolicyId$.

Cause

A tmnxBsxTransIpPolAaSubCreated notification is generated when a dynamic subscriber is created in a Transit IP Policy.

Effect

None.

Recovery

No recovery is required.

2.2.53. tmnxBsxTransIpPolAaSubDeleted

tmnxBsxTransIpPolAaSubDeleted:APPLICATION_ASSURANCE
Table 58:  tmnxBsxTransIpPolAaSubDeleted properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4422

Event name

tmnxBsxTransIpPolAaSubDeleted

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.22

Default severity

warning

Message format string

A dynamic transit subscriber $tmnxBsxNotifyAaSubscriberName$ has been deleted from group-partition $tmnxBsxNotifyAaGrpPartIndex$ transit IP policy $tmnxBsxNotifyTransitIpPolicyId$.

Cause

A tmnxBsxTransIpPolAaSubDeleted notification is generated when a dynamic subscriber is deleted in a Transit IP Policy.

Effect

None.

Recovery

No recovery is required.

2.2.54. tmnxBsxTransIpPolDhcpAddWarning

tmnxBsxTransIpPolDhcpAddWarning:APPLICATION_ASSURANCE
Table 59:  tmnxBsxTransIpPolDhcpAddWarning properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4426

Event name

tmnxBsxTransIpPolDhcpAddWarning

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.26

Default severity

warning

Message format string

Problem encountered while attempting to add a transit subscriber to group-partition $tmnxBsxNotifyAaGrpPartIndex$ transit IP policy $tmnxBsxNotifyTransitIpPolicyId$ : $tmnxBsxNotifyReason$.

Cause

A tmnxBsxTransIpPolDhcpAddWarning notification is generated when a problem occurs while attempting to add a dynamic transit subscriber learned via DHCP. The notification is informational and may not be an error. The tmnxBsxNotifyReason will identify the reason this trap was raised.

Effect

None.

Recovery

No recovery is required.

2.2.55. tmnxBsxTransIpPolDhcpDelWarning

tmnxBsxTransIpPolDhcpDelWarning:APPLICATION_ASSURANCE
Table 60:  tmnxBsxTransIpPolDhcpDelWarning properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4427

Event name

tmnxBsxTransIpPolDhcpDelWarning

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.27

Default severity

warning

Message format string

Problem encountered while attempting to delete a transit subscriber from group-partition $tmnxBsxNotifyAaGrpPartIndex$ transit IP policy $tmnxBsxNotifyTransitIpPolicyId$ : $tmnxBsxNotifyReason$.

Cause

A tmnxBsxTransIpPolDhcpDelWarning notification is generated when a problem occurs while attempting to delete a dynamic transit subscriber learned via DHCP. The notification is informational and may not be an error. The tmnxBsxNotifyReason will identify the reason this trap was raised.

Effect

None.

Recovery

No recovery is required.

2.2.56. tmnxBsxTransIpPolDiamGxError

tmnxBsxTransIpPolDiamGxError:APPLICATION_ASSURANCE
Table 61:  tmnxBsxTransIpPolDiamGxError properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4457

Event name

tmnxBsxTransIpPolDiamGxError

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.57

Default severity

minor

Message format string

Problem encountered while processing a Diameter GX request/answer for group $tmnxBsxNotifyAaGrpPartIndex$ transit IP policy $tmnxBsxNotifyTransitIpPolicyId$ : $tmnxBsxNotifyReason$.

Cause

A tmnxBsxTransIpPolDiamGxError notification is generated when an error occurs while processing a Credit-Control Answer (CCA) or Re-Authorization Request (RAR) from a Diameter server over Gx. The tmnxBsxNotifyReason will identify the reason for failing to process the Diameter answer/request.

Effect

The addition or modification of a transit subscriber indicated in the Diameter Gx message will not have been performed.

Recovery

There is no recovery for this notification.

2.2.57. tmnxBsxTransIpPolRadCoAAudit

tmnxBsxTransIpPolRadCoAAudit:APPLICATION_ASSURANCE
Table 62:  tmnxBsxTransIpPolRadCoAAudit properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4423

Event name

tmnxBsxTransIpPolRadCoAAudit

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.23

Default severity

warning

Message format string

CoA audit for group-partition $tmnxBsxNotifyAaGrpPartIndex$ transit IP policy $tmnxBsxNotifyTransitIpPolicyId$ is in state $tmnxBsxNotifyRadiusCoAAuditState$.

Cause

A tmnxBsxTransIpPolRadCoAAudit notification is generated when at the start and the end of the Change of Authorization (CoA) Audit.

Effect

None.

Recovery

No recovery is required.

2.2.58. tmnxBsxTransIpPolRadCoAError

tmnxBsxTransIpPolRadCoAError:APPLICATION_ASSURANCE
Table 63:  tmnxBsxTransIpPolRadCoAError properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4424

Event name

tmnxBsxTransIpPolRadCoAError

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.24

Default severity

minor

Message format string

Problem encountered while processing a CoA request for group-partition $tmnxBsxNotifyAaGrpPartIndex$ transit IP policy $tmnxBsxNotifyTransitIpPolicyId$: $tmnxBsxNotifyReason$.

Cause

A tmnxBsxTransIpPolRadCoAError notification is generated when an error occurs while processing a Change of Authorization (CoA) request from a RADIUS server. The tmnxBsxNotifyReason will identify the reason for failing to process the CoA request.

Effect

The addition or modification of a transit subscriber indicated in the CoA will not have been performed.

Recovery

No recovery is required.

2.2.59. tmnxBsxTransIpPolRadDiscError

tmnxBsxTransIpPolRadDiscError:APPLICATION_ASSURANCE
Table 64:  tmnxBsxTransIpPolRadDiscError properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4425

Event name

tmnxBsxTransIpPolRadDiscError

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.25

Default severity

minor

Message format string

Problem encountered while processing a RADIUS disconnect request for group-partition $tmnxBsxNotifyAaGrpPartIndex$ transit IP policy $tmnxBsxNotifyTransitIpPolicyId$ : $tmnxBsxNotifyReason$.

Cause

A tmnxBsxTransIpPolRadDiscError notification is generated when an error occurs while processing a Disconnect request from a RADIUS server. The tmnxBsxNotifyReason will identify the reason for failing to process the Disconnect request.

Effect

The removal of a transit subscriber indicated by a Disconnect request will not have been performed.

Recovery

No recovery is required.

2.2.60. tmnxBsxTransitIpPersistenceWarn

tmnxBsxTransitIpPersistenceWarn:APPLICATION_ASSURANCE
Table 65:  tmnxBsxTransitIpPersistenceWarn properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4434

Event name

tmnxBsxTransitIpPersistenceWarn

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.34

Default severity

warning

Message format string

Problem encountered while registering transit subscriber address persistently for group-partition $tmnxBsxNotifyAaGrpPartIndex$ transit IP policy $tmnxBsxNotifyTransitIpPolicyId$ : $tmnxBsxNotifyReason$.

Cause

A tmnxBsxTransitIpPersistenceWarn notification is generated when a problem occurs while attempting to register a dynamic transit subscriber address with the persistence infrastructure. The tmnxBsxNotifyReason will identify the reason this trap was raised.

Effect

The affected transit subscriber address will not be persistent across a system reboot.

Recovery

No recovery is required.

2.2.61. tmnxBsxUrlFilterOperStateChange

tmnxBsxUrlFilterOperStateChange:APPLICATION_ASSURANCE
Table 66:  tmnxBsxUrlFilterOperStateChange properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4442

Event name

tmnxBsxUrlFilterOperStateChange

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.42

Default severity

warning

Message format string

AA Group $tmnxBsxIsaAaGroupIndex$ URL Filter $tmnxBsxUrlFilterName$ state changed to $tmnxBsxUrlFltrOperState$, flags = $tmnxBsxUrlFltrOperFlags$.

Cause

The tmnxBsxUrlFilterOperStateChange notification is generated when the operational status of a URL Filter has transitioned either from 'inService' to 'outOfService' or from 'outOfService' to 'inService'.

Effect

None.

Recovery

No recovery is required.

2.2.62. tmnxBsxUrlListFailure

tmnxBsxUrlListFailure:APPLICATION_ASSURANCE
Table 67:  tmnxBsxUrlListFailure properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4447

Event name

tmnxBsxUrlListFailure

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.47

Default severity

minor

Message format string

URL list \"$tmnxBsxUrlListName$\" in ISA-AA group $tmnxBsxIsaAaGroupIndex$ has failed. The current operational state is: $tmnxBsxUrlListStatusOperState$, flags = $tmnxBsxUrlListStatusOperFlags$.

Cause

A tmnxBsxUrlListFailure notification is generated when a URL List has failed.

Effect

If the operational state is 'inService (2)', the URL List is operating using the last successfully processed list. If the operational state is 'outOfService (3)', there was no previous successful update and the URL List will be operationally down.

Recovery

The customer should ensure the correct file is configured in tmnxBsxUrlListFileUrl, and use tmnxBsxUrlListAdminState or tmnxBsxUrlListUpgrade to restart the URL List.

2.2.63. tmnxBsxUrlListUpdate

tmnxBsxUrlListUpdate:APPLICATION_ASSURANCE
Table 68:  tmnxBsxUrlListUpdate properties 

Property name

Value

Application name

APPLICATION_ASSURANCE

Event ID

4446

Event name

tmnxBsxUrlListUpdate

SNMP notification prefix and OID

TIMETRA-BSX-NG-MIB.tmnxBsxNotifications.46

Default severity

minor

Message format string

URL list \"$tmnxBsxUrlListName$\" in ISA-AA group $tmnxBsxIsaAaGroupIndex$ has been updated. There are $tmnxBsxUrlListStatusNumEntries$ entries in the URL list.

Cause

A tmnxBsxUrlListUpdate notification is generated when a URL List has been updated.

Effect

The URL List is installed on each ISA-AA in the group.

Recovery

There is no recovery for this notification.

2.3. APS

2.3.1. apsEventChannelMismatch

apsEventChannelMismatch:APS
Table 69:  apsEventChannelMismatch properties 

Property name

Value

Application name

APS

Event ID

2003

Event name

apsEventChannelMismatch

SNMP notification prefix and OID

APS-MIB.apsNotificationsPrefix.3

Default severity

minor

Message format string

Channel Mismatch is declared

Cause

Channel Mismatch notification is generated due to mismatch between the transmitted K1 channel (phys port) and the received K2 channel (phys port).

Effect

N/A

Recovery

Configure both local and remote with the same channel type.

2.3.2. apsEventFEPLF

apsEventFEPLF:APS
Table 70:  apsEventFEPLF properties 

Property name

Value

Application name

APS

Event ID

2005

Event name

apsEventFEPLF

SNMP notification prefix and OID

APS-MIB.apsNotificationsPrefix.5

Default severity

minor

Message format string

FEPL failure is declared

Cause

FEPLF (Far-End Protection Line Failure) notification is generated based on SF (Signal Failure) condition on the protection port in the received K1 Byte.

Effect

Traffic will switch (Tx/Rx) to the working port if the traffic is presently Tx-ed/Rx-ed to/from the protection port.

Recovery

N/A

2.3.3. apsEventModeMismatch

apsEventModeMismatch:APS
Table 71:  apsEventModeMismatch properties 

Property name

Value

Application name

APS

Event ID

2002

Event name

apsEventModeMismatch

SNMP notification prefix and OID

APS-MIB.apsNotificationsPrefix.2

Default severity

minor

Message format string

Mode Mismatch is declared

Cause

Mode Mismatch notification is generated due to a conflict between the current local mode (switching direction or architecture) and the received K2 mode information.

Effect

For switching direction mismatch, the operational switching direction is changed to uni-directional. For switch architecture mismatch, the local end runs in 1+1 mode irrespective of the remote end switching architecture.

Recovery

Configure both local and remote end to run in same switching mode (direction/architecture).

2.3.4. apsEventPSBF

apsEventPSBF:APS
Table 72:  apsEventPSBF properties 

Property name

Value

Application name

APS

Event ID

2004

Event name

apsEventPSBF

SNMP notification prefix and OID

APS-MIB.apsNotificationsPrefix.4

Default severity

minor

Message format string

PSB Failure is declared

Cause

A PSBF (Protection Switching Byte Failure) notification is generated due to inconsistent Rx K1 byte or invalid Rx K1 Byte.

Effect

A PSBF condition is considered as signal failure (SF) on the protection port.

Recovery

Correct the K1 byte value.

2.3.5. apsEventSwitchover

apsEventSwitchover:APS
Table 73:  apsEventSwitchover properties 

Property name

Value

Application name

APS

Event ID

2001

Event name

apsEventSwitchover

SNMP notification prefix and OID

APS-MIB.apsNotificationsPrefix.1

Default severity

minor

Message format string

APS switchover from $subject$.

Cause

APS switchover between working port (channel 1) and protection port (channel 0) can happen due to change of status of any port or user initiated switch commands on any port.

Effect

Traffic is transmitted to and received from the other channel/port.

Recovery

None.

2.3.6. tApsChannelMismatchClear

tApsChannelMismatchClear:APS
Table 74:  tApsChannelMismatchClear properties 

Property name

Value

Application name

APS

Event ID

2007

Event name

tApsChannelMismatchClear

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.2

Default severity

minor

Message format string

Channel Mismatch is cleared

Cause

The Channel mismatch clear notification is generated when the current status of an APS group gets the channel mismatch condition cleared.

Effect

N/A

Recovery

N/A

2.3.7. tApsChanTxLaisStateChange

tApsChanTxLaisStateChange:APS
Table 75:  tApsChanTxLaisStateChange properties 

Property name

Value

Application name

APS

Event ID

2015

Event name

tApsChanTxLaisStateChange

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.10

Default severity

warning

Message format string

APS forced Tx-LAIS state changed to $tApsChanTxLaisState$

Cause

The tApsChanTxLaisStateChange notification is generated when there is a change in the value of tApsChanTxLaisState.

Effect

N/A

Recovery

Investigation is required to determine the cause of the change.

2.3.8. tApsFEPLFClear

tApsFEPLFClear:APS
Table 76:  tApsFEPLFClear properties 

Property name

Value

Application name

APS

Event ID

2009

Event name

tApsFEPLFClear

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.4

Default severity

minor

Message format string

FEPL Failure is cleared

Cause

The FEPLF clear notification is generated when the current status of an APS group gets the FEPLF condition cleared.

Effect

N/A

Recovery

N/A

2.3.9. tApsLocalSwitchCommandClear

tApsLocalSwitchCommandClear:APS
Table 77:  tApsLocalSwitchCommandClear properties 

Property name

Value

Application name

APS

Event ID

2011

Event name

tApsLocalSwitchCommandClear

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.6

Default severity

warning

Message format string

Local - $apsCommandSwitch$ cleared

Cause

The tApsLocalSwitchCommandClear notification is generated when an APS switch command in the local node gets cleared. Note that a switch command in the local node can be cleared either due to execution of the clear switch command in the local node or due to presence of a higher priority condition in the local or remote node.

Effect

N/A

Recovery

N/A

2.3.10. tApsLocalSwitchCommandSet

tApsLocalSwitchCommandSet:APS
Table 78:  tApsLocalSwitchCommandSet properties 

Property name

Value

Application name

APS

Event ID

2010

Event name

tApsLocalSwitchCommandSet

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.5

Default severity

warning

Message format string

Local - $apsCommandSwitch$ set

Cause

The tApsLocalSwitchCommandSet is generated when any of the following APS switch commands is executed on an APS channel in the local node. The switch commands are lockoutOfProtection, forcedSwitchWorkToProtect, forcedSwitchProtectToWork, manualSwitchWorkToProtect, and manualSwitchProtectToWork.

Effect

N/A

Recovery

N/A

2.3.11. tApsMcApsCtlLinkStateChange

tApsMcApsCtlLinkStateChange:APS
Table 79:  tApsMcApsCtlLinkStateChange properties 

Property name

Value

Application name

APS

Event ID

2014

Event name

tApsMcApsCtlLinkStateChange

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.9

Default severity

warning

Message format string

Control link state changed to $tApsMcApsCtlLinkState$

Cause

The tApsMcApsCtlLinkStateChange notification is generated when there is a change in the value of tApsMcApsCtlLinkState.

Effect

N/A

Recovery

Investigation is required to determine the cause of the change.

2.3.12. tApsModeMismatchClear

tApsModeMismatchClear:APS
Table 80:  tApsModeMismatchClear properties 

Property name

Value

Application name

APS

Event ID

2006

Event name

tApsModeMismatchClear

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.1

Default severity

minor

Message format string

Mode Mismatch is cleared

Cause

The Mode mismatch clear notification is generated when the current status of an APS group gets the mode mismatch condition cleared.

Effect

N/A

Recovery

N/A

2.3.13. tApsPrimaryChannelChange

tApsPrimaryChannelChange:APS
Table 81:  tApsPrimaryChannelChange properties 

Property name

Value

Application name

APS

Event ID

2016

Event name

tApsPrimaryChannelChange

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.11

Default severity

minor

Message format string

Switch of the primary APS channel to $apsStatusK1K2Trans$.

Cause

The tApsPrimaryChannelChange notification is generated when there is a switch of the primary APS channel. Object apsStatusK1K2Trans indicates the new primary APS channel.

Effect

N/A

Recovery

Investigation is required to determine the cause of the change.

2.3.14. tApsPSBFClear

tApsPSBFClear:APS
Table 82:  tApsPSBFClear properties 

Property name

Value

Application name

APS

Event ID

2008

Event name

tApsPSBFClear

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.3

Default severity

minor

Message format string

PSB Failure is cleared

Cause

The PSBF clear notification is generated when the current status of an APS group gets the PSBF condition cleared.

Effect

N/A

Recovery

N/A

2.3.15. tApsRemoteSwitchCommandClear

tApsRemoteSwitchCommandClear:APS
Table 83:  tApsRemoteSwitchCommandClear properties 

Property name

Value

Application name

APS

Event ID

2013

Event name

tApsRemoteSwitchCommandClear

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.8

Default severity

warning

Message format string

Remote - $apsCommandSwitch$ cleared

Cause

The tApsRemoteSwitchCommandClear is generated when the received K1 byte (APS-MIB::apsStatusK1K2Rcv) from a peer indicates that an APS switch command just got cleared on an APS channel in the remote (peer) node.

Effect

N/A

Recovery

N/A

2.3.16. tApsRemoteSwitchCommandSet

tApsRemoteSwitchCommandSet:APS
Table 84:  tApsRemoteSwitchCommandSet properties 

Property name

Value

Application name

APS

Event ID

2012

Event name

tApsRemoteSwitchCommandSet

SNMP notification prefix and OID

TIMETRA-APS-MIB.tApsNotifications.7

Default severity

warning

Message format string

Remote - $apsCommandSwitch$ set

Cause

The tApsRemoteSwitchCommandSet is generated when the received K1 byte (APS-MIB::apsStatusK1K2Rcv) from a peer indicates that an APS switch command just got executed on an APS channel in the remote (peer) node.

Effect

N/A

Recovery

Investigation is required to determine the cause of the change.

2.4. ATM

2.4.1. atmIfcStatusChange

atmIfcStatusChange:ATM
Table 85:  atmIfcStatusChange properties 

Property name

Value

Application name

ATM

Event ID

2009

Event name

atmIfcStatusChange

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

Status of $subject$ owned by $tAtmIfcInfoOwner$ has changed to administrative state: $tAtmIfcAdminStatus$ operational state: $tAtmIfcOperStatus$

Cause

The state of the ATM interface has changed.

Effect

N/A

Recovery

N/A

2.4.2. atmIlmiPeerVclStatusChange

atmIlmiPeerVclStatusChange:ATM
Table 86:  atmIlmiPeerVclStatusChange properties 

Property name

Value

Application name

ATM

Event ID

2016

Event name

atmIlmiPeerVclStatusChange

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

Status of VCL $atmVclVpi$/$atmVclVci$ on $subject$ has changed to operational state: $atmVclOperStatus$

Cause

The state of the ILMI peer VCL has changed.

Effect

N/A

Recovery

Investigate what caused the new state.

2.4.3. atmIlmiPeerVplStatusChange

atmIlmiPeerVplStatusChange:ATM
Table 87:  atmIlmiPeerVplStatusChange properties 

Property name

Value

Application name

ATM

Event ID

2017

Event name

atmIlmiPeerVplStatusChange

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

Status of VPL $atmVplVpi$ on $subject$ has changed to operational state: $atmVplOperStatus$

Cause

The state of the ILMI peer VPL has changed.

Effect

N/A

Recovery

Investigate what caused the new state.

2.4.4. atmVclStatusChange

atmVclStatusChange:ATM
Table 88:  atmVclStatusChange properties 

Property name

Value

Application name

ATM

Event ID

2006

Event name

atmVclStatusChange

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

Status of $subject$ owned by $tAtmVclInfoOwner$ has changed to administrative state: $atmVclAdminStatus$ operational state: $atmVclOperStatus$ OAM state: $tAtmVclInfoOamStatus$

Cause

The state of the ATM VCL has changed.

Effect

N/A

Recovery

N/A

2.4.5. atmVplStatusChange

atmVplStatusChange:ATM
Table 89:  atmVplStatusChange properties 

Property name

Value

Application name

ATM

Event ID

2007

Event name

atmVplStatusChange

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

Status of $subject$ owned by $tAtmVplInfoOwner$ has changed to administrative state: $atmVplAdminStatus$ operational state: $atmVplOperStatus$ OAM state: $tAtmVplInfoOamStatus$

Cause

The state of the ATM VPL has changed.

Effect

N/A

Recovery

N/A

2.4.6. atmVtlStatusChange

atmVtlStatusChange:ATM
Table 90:  atmVtlStatusChange properties 

Property name

Value

Application name

ATM

Event ID

2008

Event name

atmVtlStatusChange

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

Status of $subject$ owned by $tAtmVtlInfoOwner$ has changed to administrative state: $tAtmVtlAdminStatus$ operational state: $tAtmVtlOperStatus$

Cause

The state of the ATM VTL has changed.

Effect

N/A

Recovery

N/A

2.4.7. tAtmEpOutOfPeerVpiOrVciRange

tAtmEpOutOfPeerVpiOrVciRange:ATM
Table 91:  tAtmEpOutOfPeerVpiOrVciRange properties 

Property name

Value

Application name

ATM

Event ID

2012

Event name

tAtmEpOutOfPeerVpiOrVciRange

SNMP notification prefix and OID

TIMETRA-ATM-MIB.tAtmNotifications.5

Default severity

warning

Message format string

ATM EPs on ATM interface $subject$ are outside of the negotiated VPI or VCI range

Cause

The tAtmEpOutOfPeerVpiOrVciRange notification is sent whenever an ILMI link becomes operationally up and ATM EPs are configured on the ILMI-managed interface that are outside the VPI or VCI range allowed by the peer.

Effect

N/A

Recovery

Adjust the VPI or VCI range.

2.4.8. tAtmIlmiLinkStatusChange

tAtmIlmiLinkStatusChange:ATM
Table 92:  tAtmIlmiLinkStatusChange properties 

Property name

Value

Application name

ATM

Event ID

2015

Event name

tAtmIlmiLinkStatusChange

SNMP notification prefix and OID

TIMETRA-ATM-MIB.tAtmNotifications.8

Default severity

warning

Message format string

Status of ILMI on ATM Interface $subject$ vpi=$tAtmIlmiLinkVpi$ vci=$tAtmIlmiLinkVci$ has changed administrative status: $tAtmIlmiLinkAdminStatus$ operational status: $tAtmIlmiLinkOperStatus$

Cause

The tAtmIlmiLinkStatusChange notification is sent whenever a status change occurs on an ILMI link. This includes changes to the ILMI link's administrative status and the ILMI link's operational status.

Effect

N/A

Recovery

N/A

2.4.9. tAtmMaxPeerVccsExceeded

tAtmMaxPeerVccsExceeded:ATM
Table 93:  tAtmMaxPeerVccsExceeded properties 

Property name

Value

Application name

ATM

Event ID

2013

Event name

tAtmMaxPeerVccsExceeded

SNMP notification prefix and OID

TIMETRA-ATM-MIB.tAtmNotifications.6

Default severity

warning

Message format string

The number of ATM VCLs on ATM interface $subject$ exceeds the negotiated maximum

Cause

The tAtmMaxPeerVccsExceeded notification is sent whenever an ILMI link becomes operationally up and there are more ATM VCLs configured on the ILMI-managed interface than are supported by the peer.

Effect

N/A

Recovery

N/A

2.4.10. tAtmMaxPeerVpcsExceeded

tAtmMaxPeerVpcsExceeded:ATM
Table 94:  tAtmMaxPeerVpcsExceeded properties 

Property name

Value

Application name

ATM

Event ID

2014

Event name

tAtmMaxPeerVpcsExceeded

SNMP notification prefix and OID

TIMETRA-ATM-MIB.tAtmNotifications.7

Default severity

warning

Message format string

The number of ATM VPLs on ATM interface $subject$ exceeds the negotiated maximum

Cause

The tAtmMaxPeerVpcsExceeded notification is sent whenever an ILMI link becomes operationally up and there are more ATM VPLs configured on the ILMI-managed interface than are supported by the peer.

Effect

N/A

Recovery

N/A

2.4.11. tAtmPlcpSubLayerClear

tAtmPlcpSubLayerClear:ATM
Table 95:  tAtmPlcpSubLayerClear properties 

Property name

Value

Application name

ATM

Event ID

2011

Event name

tAtmPlcpSubLayerClear

SNMP notification prefix and OID

TIMETRA-ATM-MIB.tAtmNotifications.4

Default severity

minor

Message format string

ATM Interface $subject$ entered the no error state

Cause

The tAtmPlcpSubLayerClear notification is generated when the ATM interface has left the far end alarm or incoming LOF error state and entered the no error state.

Effect

N/A

Recovery

N/A

2.4.12. tAtmPlcpSubLayerDown

tAtmPlcpSubLayerDown:ATM
Table 96:  tAtmPlcpSubLayerDown properties 

Property name

Value

Application name

ATM

Event ID

2010

Event name

tAtmPlcpSubLayerDown

SNMP notification prefix and OID

TIMETRA-ATM-MIB.tAtmNotifications.3

Default severity

minor

Message format string

ATM Interface $subject$ entered failure state

Cause

The tAtmPlcpSubLaerDown notification is generated when the ATM interface has left the no error state and entered the far end alarm or incoming LOF state.

Effect

N/A

Recovery

N/A

2.4.13. tAtmTcSubLayerClear

tAtmTcSubLayerClear:ATM
Table 97:  tAtmTcSubLayerClear properties 

Property name

Value

Application name

ATM

Event ID

2005

Event name

tAtmTcSubLayerClear

SNMP notification prefix and OID

TIMETRA-ATM-MIB.tAtmNotifications.2

Default severity

minor

Message format string

ATM Interface $subject$ entered the LCD no error state

Cause

The tAtmTcSubLayerClear notification is generated when the ATM interface has left the Loss of Cell Delineation (LCD) error state and entered the LCD no error state.

Effect

N/A

Recovery

N/A

2.4.14. tAtmTcSubLayerDown

tAtmTcSubLayerDown:ATM
Table 98:  tAtmTcSubLayerDown properties 

Property name

Value

Application name

ATM

Event ID

2004

Event name

tAtmTcSubLayerDown

SNMP notification prefix and OID

TIMETRA-ATM-MIB.tAtmNotifications.1

Default severity

minor

Message format string

ATM Interface $subject$ entered LCD failure state

Cause

The tAtmTcSubLayerUp notification is generated when the ATM interface has left the no error Loss of Cell Delineation (LCD) state and entered the default LCD state.

Effect

N/A

Recovery

Investigate why the ATM TC Sublayer is currently in the LCD state.

2.5. AUTO_PROV

2.5.1. autoNodeProv

autoNodeProv:AUTO_PROV
Table 99:  autoNodeProv properties 

Property name

Value

Application name

AUTO_PROV

Event ID

2001

Event name

autoNodeProv

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

$subject$: $title$\n$message$

Cause

The system generated a auto-node-provision message.

Effect

Unknown.

Recovery

Contact Nokia customer service.

2.6. BFD

2.6.1. tmnxBfdOnLspSessDeleted

tmnxBfdOnLspSessDeleted:BFD
Table 100:  tmnxBfdOnLspSessDeleted properties 

Property name

Value

Application name

BFD

Event ID

2003

Event name

tmnxBfdOnLspSessDeleted

SNMP notification prefix and OID

TIMETRA-BFD-MIB.tmnxBfdNotifications.3

Default severity

minor

Message format string

The $tmnxBfdOnLspSessLinkType$ BFD Session with Local Discriminator $tmnxBfdOnLspSessLclDisc$ on $subject$ has been deleted

Cause

The tmnxBfdOnLspSessDeleted notification is generated when a BFD on LSP session is deleted.

Effect

The deletion of this session will either take down any protocol that is riding over top of it or notifies them that the session has been deleted.

Recovery

There is no recovery required for this notification.

2.6.2. tmnxBfdOnLspSessDown

tmnxBfdOnLspSessDown:BFD
Table 101:  tmnxBfdOnLspSessDown properties 

Property name

Value

Application name

BFD

Event ID

2001

Event name

tmnxBfdOnLspSessDown

SNMP notification prefix and OID

TIMETRA-BFD-MIB.tmnxBfdNotifications.1

Default severity

minor

Message format string

The $tmnxBfdOnLspSessLinkType$ BFD session with Local Discriminator $tmnxBfdOnLspSessLclDisc$ on $subject$ is down due to $tmnxBfdOnLspSessOperFlags$

Cause

The tmnxBfdOnLspSessDown notification is generated when a BFD on LSP session goes down.

Effect

The effect of this session going down is that it either takes down any protocol that is riding over top of it or it notifies them that the session has gone down.

Recovery

The session will automatically attempt to re-establish on its own.

2.6.3. tmnxBfdOnLspSessNoCpmNpResources

tmnxBfdOnLspSessNoCpmNpResources:BFD
Table 102:  tmnxBfdOnLspSessNoCpmNpResources properties 

Property name

Value

Application name

BFD

Event ID

2005

Event name

tmnxBfdOnLspSessNoCpmNpResources

SNMP notification prefix and OID

TIMETRA-BFD-MIB.tmnxBfdNotifications.5

Default severity

minor

Message format string

The $tmnxBfdOnLspSessLinkType$ BFD session with local discriminator $tmnxBfdOnLspSessLclDisc$ on $subject$ could not be established because cpm-np session termination resources are not available

Cause

The tmnxBfdOnLspSessNoCpmNpResources notification is generated when a BFD on LSP session could not be established because the session requires a cpmNp session termination resource (see TIMETRA-VRTR-MIB::vRtrIfBfdExtType), and no cpmNp session termination resources are available.

Effect

The BFD session cannot be established until a cpmNp session termination resource is available

Recovery

There is no recovery required for this notification.

2.6.4. tmnxBfdOnLspSessNoTailResources

tmnxBfdOnLspSessNoTailResources:BFD
Table 103:  tmnxBfdOnLspSessNoTailResources properties 

Property name

Value

Application name

BFD

Event ID

2006

Event name

tmnxBfdOnLspSessNoTailResources

SNMP notification prefix and OID

TIMETRA-BFD-MIB.tmnxBfdNotifications.6

Default severity

minor

Message format string

BFD on LSP session(s) could not be established because BFD on LSP session tail-end creation is administratively disabled, or the limit on the number of BFD on LSP session tail-ends has been reached (admin state = $vRtrLspBfdSession$, limit = $vRtrLspBfdMaxSessions$)

Cause

The tmnxBfdOnLspSessNoTailResources notification is generated when a BFD on LSP session could not be established by the LSP's tail-end system because the system limit on the number of session tail ends has been reached. If TIMETRA-VRTR-MIB::vRtrLspBfdSession is 'enabled(1)', the system limit on the number of session tail ends is TIMETRA-VRTR-MIB::vRtrLspBfdMaxSessions. If TIMETRA-VRTR-MIB::vRtrLspBfdSession is 'disabled(2)', the system limit on the number of session tail ends is zero. This notification is throttled using the following mechanism. In the initial state (e.g. at CPM startup), when the first failure is detected, tmnxBfdOnLspSessNoTailResources is raised, and a ten minute timer is started. When the timer expires:

1. tmnxBfdOnLspSessNoTailResources is raised if one or more failures occurred in the ten minute interval, and

2. A ten minute timer is started (and the process repeats). Any change to TIMETRA-VRTR-MIB::vRtrLspBfdSession and/or TIMETRA-VRTR-MIB::vRtrLspBfdMaxSessions restarts the process at the initial state.

Effect

One or more BFD on LSP sessions could not be established.

Recovery

Change TIMETRA-VRTR-MIB::vRtrLspBfdSession to 'enabled(1)', or increase TIMETRA-VRTR-MIB::vRtrLspBfdMaxSessions, or change the network configuration to reduce the number of active BFD on LSP session tail ends.

2.6.5. tmnxBfdOnLspSessProtChange

tmnxBfdOnLspSessProtChange:BFD
Table 104:  tmnxBfdOnLspSessProtChange properties 

Property name

Value

Application name

BFD

Event ID

2004

Event name

tmnxBfdOnLspSessProtChange

SNMP notification prefix and OID

TIMETRA-BFD-MIB.tmnxBfdNotifications.4

Default severity

minor

Message format string

The protocol ($tmnxBfdOnLspSessChangedProtocol$) using BFD session on node $subject$ has been $tmnxBfdOnLspSessProtoChngdState$

Cause

The tmnxBfdOnLspSessProtChange notification is generated when there is a change in the list of protocols specified by tmnxBfdOnLspSessProtocols using the BFD on LSP session.

Effect

The list of protocols using this session are modified.

Recovery

There is no recovery required for this notification.

2.6.6. tmnxBfdOnLspSessUp

tmnxBfdOnLspSessUp:BFD
Table 105:  tmnxBfdOnLspSessUp properties 

Property name

Value

Application name

BFD

Event ID

2002

Event name

tmnxBfdOnLspSessUp

SNMP notification prefix and OID

TIMETRA-BFD-MIB.tmnxBfdNotifications.2

Default severity

minor

Message format string

The $tmnxBfdOnLspSessLinkType$ BFD session with Local Discriminator $tmnxBfdOnLspSessLclDisc$ on $subject$ is up

Cause

The tmnxBfdOnLspSessUp notification is generated when a BFD on LSP session goes up.

Effect

The BFD session will be active.

Recovery

There is no recovery required for this notification.

2.7. BGP

2.7.1. bgpBackwardTransNotification

bgpBackwardTransNotification:BGP
Table 106:  bgpBackwardTransNotification properties 

Property name

Value

Application name

BGP

Event ID

2039

Event name

bgpBackwardTransNotification

SNMP notification prefix and OID

BGP4-MIB.bgpNotification.2

Default severity

warning

Message format string

$bgp_peer_name$: moved from higher state $old_state_str$ to lower state $new_state_str$ due to event $event_str$

Cause

The bgpBackwardTransNotification event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state. This Notification replaces the bgpBackwardsTransition Notification.

Effect

N/A

Recovery

N/A

2.7.2. bgpCfgViol

bgpCfgViol:BGP
Table 107:  bgpCfgViol properties 

Property name

Value

Application name

BGP

Event ID

2017

Event name

bgpCfgViol

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$subject$: BGP - $field$ configuration ignored - $reason$

Cause

BGP configuration was invalid.

Effect

The configuration that lead to the violation will be totally ignored.

Recovery

N/A

2.7.3. bgpConnMgrTerminated

bgpConnMgrTerminated:BGP
Table 108:  bgpConnMgrTerminated properties 

Property name

Value

Application name

BGP

Event ID

2013

Event name

bgpConnMgrTerminated

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$subject$: BGP connection manager for address family $addr_family_str$ has terminated

Cause

BGP is being shutdown or deleted.

Effect

No inbound BGP connections will be accepted.

Recovery

BGP must be re-enabled.

2.7.4. bgpConnNoKA

bgpConnNoKA:BGP
Table 109:  bgpConnNoKA properties 

Property name

Value

Application name

BGP

Event ID

2008

Event name

bgpConnNoKA

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$bgp_peer_name$: closing inbound connection because the BGP peer did not receive \"keepalive\"

Cause

A BGP KEEPALIVE message was not received within the holdtime limit.

Effect

Inbound connection failed to establish.

Recovery

Reset and try again.

2.7.5. bgpConnNoOpenRcvd

bgpConnNoOpenRcvd:BGP
Table 110:  bgpConnNoOpenRcvd properties 

Property name

Value

Application name

BGP

Event ID

2009

Event name

bgpConnNoOpenRcvd

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$bgp_peer_name$: closing inbound connection because the BGP peer did not receive \"open\"

Cause

A BGP OPEN message was not received within the holdtime limit.

Effect

Inbound connection failed to establish.

Recovery

Reset and try again.

2.7.6. bgpEstablishedNotification

bgpEstablishedNotification:BGP
Table 111:  bgpEstablishedNotification properties 

Property name

Value

Application name

BGP

Event ID

2038

Event name

bgpEstablishedNotification

SNMP notification prefix and OID

BGP4-MIB.bgpNotification.1

Default severity

minor

Message format string

$bgp_peer_name$: moved into established state

Cause

The bgpEstablishedNotification event is generated when the BGP FSM enters the established state. This Notification replaces the bgpEstablished Notification.

Effect

The BGP instance is now running.

Recovery

N/A

2.7.7. bgpInterfaceDown

bgpInterfaceDown:BGP
Table 112:  bgpInterfaceDown properties 

Property name

Value

Application name

BGP

Event ID

2007

Event name

bgpInterfaceDown

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$bgp_peer_name$: being disabled because the interface is operationally disabled

Cause

The IP interface is down.

Effect

All EBGP peers directly attached to the interface for the peering go down.

Recovery

Bring the interface up.

2.7.8. bgpNoMemoryPeer

bgpNoMemoryPeer:BGP
Table 113:  bgpNoMemoryPeer properties 

Property name

Value

Application name

BGP

Event ID

2015

Event name

bgpNoMemoryPeer

SNMP notification prefix and OID

N/A

Default severity

critical

Message format string

$bgp_peer_name$: out of memory - disabled the peer

Cause

The router has run out of memory.

Effect

The peering that first hit the out of memory condition on a memory allocation request is going to go down and it will be marked DISABLED.

Recovery

Upgrade the box's memory or shut down the memory hogging peering sessions.

2.7.9. bgpPeerNotFound

bgpPeerNotFound:BGP
Table 114:  bgpPeerNotFound properties 

Property name

Value

Application name

BGP

Event ID

2012

Event name

bgpPeerNotFound

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$subject$: Closing connection: $peer_ip_str$ not enabled or not in configuration

Cause

BGP peering session won't come up.

Effect

Inbound connection failed to establish as the peer that the remote end is trying to connect to does not exist in the current configuration.

Recovery

Change the BGP configuration to create a peering session with the remote peer.

2.7.10. bgpRejectConnBadLocAddr

bgpRejectConnBadLocAddr:BGP
Table 115:  bgpRejectConnBadLocAddr properties 

Property name

Value

Application name

BGP

Event ID

2010

Event name

bgpRejectConnBadLocAddr

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$bgp_peer_name$: inbound connection rejected because the BGP peer received connection attempt on $rcv_addr_str$ but it only accepts connection on $lcl_addr_str$

Cause

Inbound BGP connection not being attempted through the correct IP address.

Effect

Inbound connection will be rejected - failed to establish the peering session.

Recovery

The remote peer should be trying to open the peering connection to the appropriate IP address - i.e. the one mentioned in the local-address of the local peer.

2.7.11. bgpRemoteEndClosedConn

bgpRemoteEndClosedConn:BGP
Table 116:  bgpRemoteEndClosedConn properties 

Property name

Value

Application name

BGP

Event ID

2011

Event name

bgpRemoteEndClosedConn

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$bgp_peer_name$: remote end closed connection

Cause

The remote end of the BGP connection closed the TCP connection.

Effect

The BGP peering session is closed. All routes learned from that peer were rejected.

Recovery

Reset and try to re-establish the peering.

2.7.12. bgpTerminated

bgpTerminated:BGP
Table 117:  bgpTerminated properties 

Property name

Value

Application name

BGP

Event ID

2014

Event name

bgpTerminated

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$subject$: BGP has terminated

Cause

BGP is being shutdown or deleted.

Effect

The BGP protocol will terminate.

Recovery

BGP must be re-enabled.

2.7.13. bgpVariableRangeViolation

bgpVariableRangeViolation:BGP
Table 118:  bgpVariableRangeViolation properties 

Property name

Value

Application name

BGP

Event ID

2016

Event name

bgpVariableRangeViolation

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$subject$: trying to set $varname$ to $tryval$ - valid range is [$minval$-$maxval$] - setting to $finalval$

Cause

The event is caused by setting some variable through a MIB that is outside the valid range accepted by the application. The system gets into this scenario when the agent is not able to catch the variable range violation because from the perspective of the MIB variable that is being set it is an acceptable value. e.g. min-route-advertisement has a range in the Nokia MIB that is more strict than the standard BGP4 MIB. Although the agent will allow larger range values for this MIB variable the BGP implementation will reject it as it is restricted by the Nokia BGP MIB.

Effect

The set value is not accepted but the closest valid value to the set value is accepted.

Recovery

N/A

2.7.14. receiveNotification

receiveNotification:BGP
Table 119:  receiveNotification properties 

Property name

Value

Application name

BGP

Event ID

2006

Event name

receiveNotification

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$bgp_peer_name$: received notification: code $code_str$ subcode $subcode_str$

Cause

Any error that occurred between BGP peers that was first recognized by the remote BGP instance. e.g. 1) An error occurred in the state transitions of a peering session. 2) An error occurred during the exchange of routing information between BGP peers. 3) The two BGP peers mismatch on the capability that they can support.

Effect

The system closes the existing socket connection and tries to establish the peering session again.

Recovery

N/A

2.7.15. sendNotification

sendNotification:BGP
Table 120:  sendNotification properties 

Property name

Value

Application name

BGP

Event ID

2005

Event name

sendNotification

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$bgp_peer_name$: sending notification: code $code_str$ subcode $subcode_str$

Cause

Any error that occurred between BGP peers that was first recognized by the local BGP instance. e.g. 1) An error occurred in the state transitions of a peering session. 2) An error occurred during the exchange of routing information between BGP peers. 3) The two BGP peers mismatch on the capability that they can support.

Effect

The system brings down the peering and attempts to establish a new peering session.

Recovery

N/A

2.7.16. tBgp4PathAttrDiscarded

tBgp4PathAttrDiscarded:BGP
Table 121:  tBgp4PathAttrDiscarded properties 

Property name

Value

Application name

BGP

Event ID

2040

Event name

tBgp4PathAttrDiscarded

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.24

Default severity

warning

Message format string

$vRtrID$: Discarded path attribute received from BGP Peer $tBgpPeerNgAddr$ with attribute type [$tBgp4PathAttrType$] and length [$tBgp4PathAttrLength$].\nHex dump: $tBgp4PathAttribute$

Cause

The tBgp4PathAttrDiscarded notification is generated when a path attribute tBgp4PathAttribute is discarded from an UPDATE message. A path attribute may be discarded because it is malformed.

Effect

A log entry is generated for each path attribute discarded from an UPDATE message. The UPDATE message continues to be processed.

Recovery

There is no recovery required for this notification.

2.7.17. tBgp4PathAttrInvalid

tBgp4PathAttrInvalid:BGP
Table 122:  tBgp4PathAttrInvalid properties 

Property name

Value

Application name

BGP

Event ID

2028

Event name

tBgp4PathAttrInvalid

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.16

Default severity

warning

Message format string

$vRtrID$: BGP Peer $tBgpPeerNgAddr$: Invalid path attribute received with attribute type [$tBgp4PathAttrType$] and length [$tBgp4PathAttrLength$].\nHex dump: $tBgp4PathAttribute$

Cause

The tBgp4PathAttrInvalid notification is generated when an error with a path attribute tBgp4PathAttribute is detected.

Effect

A log entry is generated for each withdrawn route. Further effect depends on fault-tolerance and graceful-restart settings.

Recovery

There is no recovery required for this notification.

2.7.18. tBgp4RouteInvalid

tBgp4RouteInvalid:BGP
Table 123:  tBgp4RouteInvalid properties 

Property name

Value

Application name

BGP

Event ID

2027

Event name

tBgp4RouteInvalid

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.15

Default severity

warning

Message format string

$vRtrID$: BGP Peer: $tBgpPeerNgAddr$, Route invalid Reason - $tBgpRouteInvalidReason$\nNLRI - $tBgpRouteNLRI$

Cause

The tBgp4RouteInvalid notification is generated when the received route is invalid for a specific reason and the route can not be used or advertised further.

Effect

The BGP peer ignores the route and flags the path attribute and the route so that the peer/tribe that was attempting to advertise the associated route can skip this route. The BGP peering is not torn down in this case.

Recovery

There is no recovery required for this notification.

2.7.19. tBgp4UpdateInvalid

tBgp4UpdateInvalid:BGP
Table 124:  tBgp4UpdateInvalid properties 

Property name

Value

Application name

BGP

Event ID

2030

Event name

tBgp4UpdateInvalid

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.18

Default severity

warning

Message format string

$vRtrID$: BGP Peer: $tBgpPeerNgAddr$.\nHex dump: $tBgp4UpdateMessage$

Cause

The tBgp4UpdateInvalid notification is generated when an UPDATE message has a critical length error or an error not specific to any path attribute.

Effect

A log entry is generated for each withdrawn route. Further effect depends on fault-tolerance and graceful-restart settings.

Recovery

There is no recovery required for this notification.

2.7.20. tBgp4WithdrawnRtFromUpdateError

tBgp4WithdrawnRtFromUpdateError:BGP
Table 125:  tBgp4WithdrawnRtFromUpdateError properties 

Property name

Value

Application name

BGP

Event ID

2029

Event name

tBgp4WithdrawnRtFromUpdateError

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.17

Default severity

warning

Message format string

$vRtrID$: BGP Peer: $tBgpPeerNgAddr$, Route: $tBgp4WithdrawnRoutePrefix$ withdrawn because of error in BGP update message.

Cause

The tBgp4WithdrawnRtFromUpdateError notification is generated when NLRI is withdrawn because of error in BGP update message.

Effect

This notification has no direct effect. The withdrawn routes are logged to aid debugging and tracking back the root cause of the problem.

Recovery

There is no recovery required for this notification.

2.7.21. tBgpFibResourceFailPeer

tBgpFibResourceFailPeer:BGP
Table 126:  tBgpFibResourceFailPeer properties 

Property name

Value

Application name

BGP

Event ID

2032

Event name

tBgpFibResourceFailPeer

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$bgp_peer_name$: FIB resource fail - disabled the peer

Cause

The router has run out of memory. It is triggered when BGP fails to add a route into RTM.

Effect

The system disables the peer.

Recovery

There is no automatic recovery. The user has to manually enable the peer again.

2.7.22. tBgpFlowspecUnsupportdComAction

tBgpFlowspecUnsupportdComAction:BGP
Table 127:  tBgpFlowspecUnsupportdComAction properties 

Property name

Value

Application name

BGP

Event ID

2022

Event name

tBgpFlowspecUnsupportdComAction

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.10

Default severity

warning

Message format string

$bgp_peer_name$: Flowspec NLRI - unsupported community action : [$tBgpFlowspecExtCommunityAction$], action value : [$tBgpFlowspecExtCommActionValue$] received.

Cause

The tBgpFlowspecUnsupportdComAction notification is generated when the best route for a flow specification NLRI(Network Layer Reachability Information) is received from a remote BGP peer with an extended community action that is unsupported.

Effect

The BGP peer does not create ip filter entry for the received flow route even if the NLRI(Network Layer Reachability Information) has valid extended community actions.

Recovery

There is no recovery required for this notification.

2.7.23. tBgpGeneral

tBgpGeneral:BGP
Table 128:  tBgpGeneral properties 

Property name

Value

Application name

BGP

Event ID

2031

Event name

tBgpGeneral

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

$subject$: $title$\n$message$

Cause

The general event is generated when certain error conditions are reported by the BGP application.

Effect

Each condition has its own effect.

Recovery

The recovery depends on the condition reported.

2.7.24. tBgpInstanceDynamicPeerLmtReachd

tBgpInstanceDynamicPeerLmtReachd:BGP
Table 129:  tBgpInstanceDynamicPeerLmtReachd properties 

Property name

Value

Application name

BGP

Event ID

2036

Event name

tBgpInstanceDynamicPeerLmtReachd

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.22

Default severity

minor

Message format string

$bgp_peer_name$: Closing connection: reached dynamic peer limit ($tBgpInstanceDynamicPeerLimit$) for BGP instance $tBgpInstanceIndex$

Cause

A tBgpInstanceDynamicPeerLmtReachd notification is generated when the dynamic peer limit for this BGP instance is reached.

Effect

Whenever an incoming connection for a new dynamic session would cause dynamic peer limit for this BGP instance to be exceeded, the connection attempt is rejected.

Recovery

Increase the dynamic peer limit for this BGP instance.

2.7.25. tBgpMaxNgPfxLmt

tBgpMaxNgPfxLmt:BGP
Table 130:  tBgpMaxNgPfxLmt properties 

Property name

Value

Application name

BGP

Event ID

2034

Event name

tBgpMaxNgPfxLmt

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.20

Default severity

minor

Message format string

$bgp_peer_name$: number of routes learned has exceeded configured maximum ($tBgpPeerNgPfxLmtMaxPrefix$) for $tBgpPeerNgPfxLmtFamily$ family

Cause

A tBgpMaxNgPfxLmt notification is generated when the number of routes learned from the peer has exceeded the configured maximum.

Effect

No direct effect but if the peer continues to advertise more routes then the number of routes may exceed the configured maximum (tBgpPeerNgPfxLmtMaxPrefix). In that case the peer would just be disabled.

Recovery

Increase the max-prefix for this peer.

2.7.26. tBgpMaxNgPfxLmtThresholdReached

tBgpMaxNgPfxLmtThresholdReached:BGP
Table 131:  tBgpMaxNgPfxLmtThresholdReached properties 

Property name

Value

Application name

BGP

Event ID

2035

Event name

tBgpMaxNgPfxLmtThresholdReached

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.21

Default severity

minor

Message format string

$bgp_peer_name$: number of routes learned has exceeded $tBgpPeerNgPfxLmtThreshold$ percentage of the configured maximum ($tBgpPeerNgPfxLmtMaxPrefix$) for $tBgpPeerNgPfxLmtFamily$ family

Cause

A tBgpMaxNgPfxLmtThresholdReached notification is generated when the number of routes learned from the peer has exceeded tBgpPeerNgPfxLmtThreshold percent of the configured maximum (tBgpPeerNgPfxLmtMaxPrefix).

Effect

No direct effect but if the peer continues to advertise more routes then the number of routes may exceed the configured maximum (tBgpPeerNgPfxLmtMaxPrefix). In that case the peer would just be disabled.

Recovery

Increase the max-prefix for this peer.

2.7.27. tBgpNgBackwardTransition

tBgpNgBackwardTransition:BGP
Table 132:  tBgpNgBackwardTransition properties 

Property name

Value

Application name

BGP

Event ID

2020

Event name

tBgpNgBackwardTransition

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.8

Default severity

warning

Message format string

$bgp_peer_name$: moved from higher state $old_state_str$ to lower state $new_state_str$ due to event $event_str$

Cause

The tBgpNgBackwardTransition notification is generated when the BGP FSM moves from a higher numbered state to a lower numbered state.

Effect

N/A

Recovery

N/A

2.7.28. tBgpNgEstablished

tBgpNgEstablished:BGP
Table 133:  tBgpNgEstablished properties 

Property name

Value

Application name

BGP

Event ID

2019

Event name

tBgpNgEstablished

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.7

Default severity

minor

Message format string

$bgp_peer_name$: moved into established state

Cause

The tBgpNgEstablished notification is generated when the BGP FSM enters the ESTABLISHED state.

Effect

The BGP instance is now running.

Recovery

N/A

2.7.29. tBgpPeerGRStatusChange

tBgpPeerGRStatusChange:BGP
Table 134:  tBgpPeerGRStatusChange properties 

Property name

Value

Application name

BGP

Event ID

2018

Event name

tBgpPeerGRStatusChange

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.6

Default severity

warning

Message format string

$bgp_peer_name$: graceful restart status changed to $tBgpPeerNgOperGRStatus$

Cause

The BGP peer is either restarting or just changed the graceful restart status to 'helping'/'not helping'/'restart complete'.

Effect

N/A

Recovery

N/A

2.7.30. tBgpPeerNgHoldTimeInconsistent

tBgpPeerNgHoldTimeInconsistent:BGP
Table 135:  tBgpPeerNgHoldTimeInconsistent properties 

Property name

Value

Application name

BGP

Event ID

2021

Event name

tBgpPeerNgHoldTimeInconsistent

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.9

Default severity

warning

Message format string

$bgp_peer_name$: attempted to negotiate a hold timer lower than the configured minimum value of $tBgpPeerNgMinHoldTime$

Cause

The BGP peer tried to establish a peering with a hold time less than the configured minimum hold time value.

Effect

The BGP peering is rejected.

Recovery

Establish peering with a hold time equal to or greater than the minimum hold time configured.

2.7.31. tBgpPGDynamicPeerLmtReached

tBgpPGDynamicPeerLmtReached:BGP
Table 136:  tBgpPGDynamicPeerLmtReached properties 

Property name

Value

Application name

BGP

Event ID

2037

Event name

tBgpPGDynamicPeerLmtReached

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.23

Default severity

minor

Message format string

$bgp_peer_name$: Closing connection: reached dynamic peer limit ($tBgpPGDynamicPeerLimit$) for BGP group $tBgpPeerGroupName$

Cause

A tBgpPGDynamicPeerLmtReached notification is generated when the dynamic peer limit for this group is reached.

Effect

Whenever an incoming connection for a new dynamic session would cause dynamic peer limit for this group to be exceeded, the connection attempt is rejected.

Recovery

Increase the dynamic peer limit for this group.

2.7.32. tBgpReceivedInvalidNlri

tBgpReceivedInvalidNlri:BGP
Table 137:  tBgpReceivedInvalidNlri properties 

Property name

Value

Application name

BGP

Event ID

2033

Event name

tBgpReceivedInvalidNlri

SNMP notification prefix and OID

TIMETRA-BGP-MIB.tBgpNotifications.19

Default severity

warning

Message format string

For the bad_network error type $tBgp4BadErrorMessageType$ the message received is $tBgp4BadErrorMessage$.

Cause

The tBgpReceivedInvalidNlri notification is generated when there is a parsing error in BGP routes that is not related to attribute errors.

Effect

BGP will send a notification message to the peer and bring down the peering.

Recovery

Peering will be re-established with the offending peer.

2.8. CALLTRACE

2.8.1. calltraceDebugEvent

calltraceDebugEvent:CALLTRACE
Table 138:  calltraceDebugEvent properties 

Property name

Value

Application name

CALLTRACE

Event ID

2003

Event name

calltraceDebugEvent

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

$subject$: $title$\n$message$

Cause

Calltrace generated a debug message because calltrace debugging was enabled. The event may show packet or an event related to the sessions being traced in the system.

Effect

None.

Recovery

Disable calltrace debugging to stop receiving the event.

2.8.2. tmnxCallTraceLocSizeLimitReached

tmnxCallTraceLocSizeLimitReached:CALLTRACE
Table 139:  tmnxCallTraceLocSizeLimitReached properties 

Property name

Value

Application name

CALLTRACE

Event ID

2002

Event name

tmnxCallTraceLocSizeLimitReached

SNMP notification prefix and OID

TIMETRA-CALLTRACE-MIB.tmnxCallTraceNotifications.2

Default severity

minor

Message format string

Size limit ($tmnxCallTraceLocationSizeLimit$ MB) of all call trace log files on 'cf$tmnxCallTraceLocationCFlashId$' has been reached

Cause

This notification is triggered when the cumulative size of all call trace log files on a given cflash card on the active CPM has reached the limit specified by the value of the object tmnxCallTraceLocationSizeLimit.

Effect

New call trace log file(s) cannot be created on the impacted cflash card.

Recovery

Operator may execute one of the following actions to restore the functionality: 1) Remove some call trace log files from the cflash card. 2) Increase the size limit (value of the object tmnxCallTraceLocationSizeLimit) for the given cflash card.

2.8.3. tmnxCallTraceMaxFilesNumReached

tmnxCallTraceMaxFilesNumReached:CALLTRACE
Table 140:  tmnxCallTraceMaxFilesNumReached properties 

Property name

Value

Application name

CALLTRACE

Event ID

2001

Event name

tmnxCallTraceMaxFilesNumReached

SNMP notification prefix and OID

TIMETRA-CALLTRACE-MIB.tmnxCallTraceNotifications.1

Default severity

minor

Message format string

Cumulative limit of $tmnxCallTraceMaxFilesNumber$ call trace log files on all cflash cards on the active CPM has been reached

Cause

This notification is triggered for the following reasons: 1) Cumulative number of call trace log files present on all cflash cards on the active CPM that are being used for their local storage has reached the limit defined by the value of the object tmnxCallTraceMaxFilesNumber. 2) The value of the object tmnxCallTraceMaxFilesNumber has been changed to a value that is lower than the current cumulative number of all call trace log files present on all cflash cards on the active CPM that are being used for their local storage. Details about cflash cards that are being used for the local storage of call trace log files can be found in tmnxCallTraceLocationTable.

Effect

New call trace log file(s) cannot be created on any cflash card.

Recovery

Operator may execute one of the following actions to restore the functionality: 1) Remove some call trace log files from (a) cflash card(s). 2) Increase the value of the object tmnxCallTraceMaxFilesNumber.

2.9. CFLOWD

2.9.1. tmnxCflowdCreateFailure

tmnxCflowdCreateFailure:CFLOWD
Table 141:  tmnxCflowdCreateFailure properties 

Property name

Value

Application name

CFLOWD

Event ID

2002

Event name

tmnxCflowdCreateFailure

SNMP notification prefix and OID

TIMETRA-CFLOWD-MIB.tmnxCflowdNotifications.2

Default severity

minor

Message format string

Cflowd creation failed

Cause

The tmnxCflowdCreateFailure event is generated when Cflowd instance creation fails on the system.

Effect

cflowd is not running.

Recovery

Contact Nokia customer service.

2.9.2. tmnxCflowdFlowCreateFailure

tmnxCflowdFlowCreateFailure:CFLOWD
Table 142:  tmnxCflowdFlowCreateFailure properties 

Property name

Value

Application name

CFLOWD

Event ID

2006

Event name

tmnxCflowdFlowCreateFailure

SNMP notification prefix and OID

TIMETRA-CFLOWD-MIB.tmnxCflowdNotifications.6

Default severity

minor

Message format string

Cflowd flow creation failed - $tmnxCflowdFlowFailureReasonCode$

Cause

The tmnxCflowdFlowCreateFailure event is generated when the creation of a Cflowd flow fails.

Effect

Flow data may be lost.

Recovery

N/A

2.9.3. tmnxCflowdPacketTxFailure

tmnxCflowdPacketTxFailure:CFLOWD
Table 143:  tmnxCflowdPacketTxFailure properties 

Property name

Value

Application name

CFLOWD

Event ID

2009

Event name

tmnxCflowdPacketTxFailure

SNMP notification prefix and OID

TIMETRA-CFLOWD-MIB.tmnxCflowdNotifications.9

Default severity

minor

Message format string

Cflowd failed to send packet to collector $tmnxCFHostCollAddress$:$tmnxCFHostCollUdpPort$ Version $tmnxCFHostCollVersion$ - Reason: $tmnxCflowdFlowFailureReasonCode$

Cause

The tmnxCflowdPacketTxFailure event is generated when a cflowd packet fails to transmit from an active collector host.

Effect

Flow data may be lost.

Recovery

N/A

2.9.4. tmnxCflowdStateChange

tmnxCflowdStateChange:CFLOWD
Table 144:  tmnxCflowdStateChange properties 

Property name

Value

Application name

CFLOWD

Event ID

2004

Event name

tmnxCflowdStateChange

SNMP notification prefix and OID

TIMETRA-CFLOWD-MIB.tmnxCflowdNotifications.4

Default severity

minor

Message format string

Status of cflowd changes to administrative state: $tmnxCflowdAdminStatus$, operational state: $tmnxCflowdOperStatus$

Cause

The tmnxCflowdStateChange event is triggered when tmnxCflowdAdminStatus or tmnxCflowdOperStatus reports a change.

Effect

N/A

Recovery

N/A

2.10. CHASSIS

2.10.1. CpmIcPortSFFStatusDDMCorrupt

CpmIcPortSFFStatusDDMCorrupt:CHASSIS
Table 145:  CpmIcPortSFFStatusDDMCorrupt properties 

Property name

Value

Application name

CHASSIS

Event ID

4012

Event name

CpmIcPortSFFStatusDDMCorrupt

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.7

Default severity

minor

Message format string

CPM interconnect port SFF DDM checksums do not match

Cause

The tmnxCpmIcPortSFFStatusFailure notification is generated when the value of tmnxCpmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'.

Effect

The SFF device is not operational and the associated CPM interconnect port can not be used. The SFF and port will not recover without operator intervention.

Recovery

Remove and re-insert the SFF device. If the problem persists then replace the SFF device.

2.10.2. CpmIcPortSFFStatusFailure

CpmIcPortSFFStatusFailure:CHASSIS
Table 146:  CpmIcPortSFFStatusFailure properties 

Property name

Value

Application name

CHASSIS

Event ID

4011

Event name

CpmIcPortSFFStatusFailure

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.7

Default severity

minor

Message format string

CPM interconnect port SFF checksums do not match

Cause

The tmnxCpmIcPortSFFStatusFailure notification is generated when the value of tmnxCpmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'.

Effect

The SFF device is not operational and the associated CPM interconnect port can not be used. The SFF and port will not recover without operator intervention.

Recovery

Remove and re-insert the SFF device. If the problem persists then replace the SFF device.

2.10.3. CpmIcPortSFFStatusReadError

CpmIcPortSFFStatusReadError:CHASSIS
Table 147:  CpmIcPortSFFStatusReadError properties 

Property name

Value

Application name

CHASSIS

Event ID

4013

Event name

CpmIcPortSFFStatusReadError

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.7

Default severity

minor

Message format string

CPM interconnect port SFF read failure

Cause

The tmnxCpmIcPortSFFStatusFailure notification is generated when the value of tmnxCpmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'.

Effect

The SFF device is not operational and the associated CPM interconnect port can not be used. The SFF and port will not recover without operator intervention.

Recovery

Remove and re-insert the SFF device. If the problem persists then replace the SFF device.

2.10.4. CpmIcPortSFFStatusUnsupported

CpmIcPortSFFStatusUnsupported:CHASSIS
Table 148:  CpmIcPortSFFStatusUnsupported properties 

Property name

Value

Application name

CHASSIS

Event ID

4014

Event name

CpmIcPortSFFStatusUnsupported

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.7

Default severity

minor

Message format string

CPM interconnect port SFF unsupported type

Cause

The tmnxCpmIcPortSFFStatusFailure notification is generated when the value of tmnxCpmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'.

Effect

The SFF device is not operational and the associated CPM interconnect port can not be used. The SFF and port will not recover without operator intervention.

Recovery

Remove and re-insert the SFF device. If the problem persists then replace the SFF device.

2.10.5. SfmIcPortSFFStatusDDMCorrupt

SfmIcPortSFFStatusDDMCorrupt:CHASSIS
Table 149:  SfmIcPortSFFStatusDDMCorrupt properties 

Property name

Value

Application name

CHASSIS

Event ID

4022

Event name

SfmIcPortSFFStatusDDMCorrupt

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.5

Default severity

minor

Message format string

SFM interconnect port SFF DDM checksums do not match

Cause

The tmnxSfmIcPortSFFStatusFailure notification is generated when the value of tmnxSfmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'.

Effect

The SFF device is not operational and the associated SFM interconnect port can not be used. The SFF and port will not recover without operator intervention.

Recovery

Remove and re-insert the SFF device. If the problem persists then replace the SFF device.

2.10.6. SfmIcPortSFFStatusFailure

SfmIcPortSFFStatusFailure:CHASSIS
Table 150:  SfmIcPortSFFStatusFailure properties 

Property name

Value

Application name

CHASSIS

Event ID

4021

Event name

SfmIcPortSFFStatusFailure

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.5

Default severity

minor

Message format string

SFM interconnect port SFF checksums do not match

Cause

The tmnxSfmIcPortSFFStatusFailure notification is generated when the value of tmnxSfmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'.

Effect

The SFF device is not operational and the associated SFM interconnect port can not be used. The SFF and port will not recover without operator intervention.

Recovery

Remove and re-insert the SFF device. If the problem persists then replace the SFF device.

2.10.7. SfmIcPortSFFStatusReadError

SfmIcPortSFFStatusReadError:CHASSIS
Table 151:  SfmIcPortSFFStatusReadError properties 

Property name

Value

Application name

CHASSIS

Event ID

4023

Event name

SfmIcPortSFFStatusReadError

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.5

Default severity

minor

Message format string

SFM interconnect port SFF read failure

Cause

The tmnxSfmIcPortSFFStatusFailure notification is generated when the value of tmnxSfmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'.

Effect

The SFF device is not operational and the associated SFM interconnect port can not be used. The SFF and port will not recover without operator intervention.

Recovery

Remove and re-insert the SFF device. If the problem persists then replace the SFF device.

2.10.8. SfmIcPortSFFStatusUnsupported

SfmIcPortSFFStatusUnsupported:CHASSIS
Table 152:  SfmIcPortSFFStatusUnsupported properties 

Property name

Value

Application name

CHASSIS

Event ID

4024

Event name

SfmIcPortSFFStatusUnsupported

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.5

Default severity

minor

Message format string

SFM interconnect port SFF unsupported type

Cause

The tmnxSfmIcPortSFFStatusFailure notification is generated when the value of tmnxSfmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'.

Effect

The SFF device is not operational and the associated SFM interconnect port can not be used. The SFF and port will not recover without operator intervention.

Recovery

Remove and re-insert the SFF device. If the problem persists then replace the SFF device.

2.10.9. tIPsecIsaMemHighWatermark

tIPsecIsaMemHighWatermark:CHASSIS
Table 153:  tIPsecIsaMemHighWatermark properties 

Property name

Value

Application name

CHASSIS

Event ID

2151

Event name

tIPsecIsaMemHighWatermark

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.138

Default severity

minor

Message format string

The memory usage ratio for ISA $tmnxCardSlotNum$/$tmnxMDASlotNum$ has almost reached the maximum value.

Cause

A tIPsecIsaMemHighWatermark notification is generated when the ISA card memory usage ratio has almost reached the maximum value.

Effect

The system may stop accepting new IKE states shortly.

Recovery

Use fewer SAs for each IKE tunnel.

2.10.10. tIPsecIsaMemLowWatermark

tIPsecIsaMemLowWatermark:CHASSIS
Table 154:  tIPsecIsaMemLowWatermark properties 

Property name

Value

Application name

CHASSIS

Event ID

2150

Event name

tIPsecIsaMemLowWatermark

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.137

Default severity

minor

Message format string

The memory usage ratio for ISA $tmnxCardSlotNum$/$tmnxMDASlotNum$ has dropped back to the normal level.

Cause

A tIPsecIsaMemLowWatermark notification is generated when the ISA card memory usage ratio has dropped back to the normal level.

Effect

The system accepts new IKE states.

Recovery

There is no recovery required for this notification.

2.10.11. tIPsecIsaMemMax

tIPsecIsaMemMax:CHASSIS
Table 155:  tIPsecIsaMemMax properties 

Property name

Value

Application name

CHASSIS

Event ID

2152

Event name

tIPsecIsaMemMax

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.139

Default severity

minor

Message format string

The memory usage for ISA $tmnxCardSlotNum$/$tmnxMDASlotNum$ has reached the maximum value.

Cause

A tIPsecIsaMemMax notification is generated when the ISA card memory usage ratio has reached the maximum value.

Effect

The system stops accepting new IKE states.

Recovery

Use fewer SAs for each IKE tunnel.

2.10.12. tmnxAlarmInputVoltageFailure

tmnxAlarmInputVoltageFailure:CHASSIS
Table 156:  tmnxAlarmInputVoltageFailure properties 

Property name

Value

Application name

CHASSIS

Event ID

3014

Event name

tmnxAlarmInputVoltageFailure

SNMP notification prefix and OID

TIMETRA-SAS-ALARM-INPUT-MIB.tmnxSASChassisNotification.10

Default severity

major

Message format string

Class $tmnxHwClass$ : alarm input voltage failure

Cause

A tmnxAlarmInputVoltageFailure notification is sent when the internal power supply for alarm inputs fails. The value of tmnxSasAlarmInputPowerStatus indicates whether the power to external alarm inputs is on or off.

Effect

If the alarm inputs use the internal power supply, then a failure in the power supply will cause state change event alarms to not be raised.

Recovery

Check the internal power source for alarm inputs and rectify the problem.

2.10.13. tmnxBluetoothModuleConnectionChg

tmnxBluetoothModuleConnectionChg:CHASSIS
Table 157:  tmnxBluetoothModuleConnectionChg properties 

Property name

Value

Application name

CHASSIS

Event ID

2187

Event name

tmnxBluetoothModuleConnectionChg

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.178

Default severity

minor

Message format string

Bluetooth Module $tmnxChassisNotifyCpmCardSlotNum$ got $tmnxBluetoothModuleConnected$ to $tmnxBluetoothModuleConnectedMac$.

Cause

The tmnxBluetoothModuleConnectionChg notification is generated when a remote Bluetooth device connects with or disconnects from the indicated Bluetooth module.

Effect

A Bluetooth device has connected with or disconnected from a Bluetooth module.

Recovery

No recovery required.

2.10.14. tmnxCardResMacFdbHighUsgClr

tmnxCardResMacFdbHighUsgClr:CHASSIS
Table 158:  tmnxCardResMacFdbHighUsgClr properties 

Property name

Value

Application name

CHASSIS

Event ID

5164

Event name

tmnxCardResMacFdbHighUsgClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.149

Default severity

minor

Message format string

The FDB table usage for card $tmnxMacScaleCardSlotNum$ is below 90% of the card limit

Cause

The tmnxCardResMacFdbHighUsgClr notification is generated when the FDB table size drops below 90% of the card limit.

Effect

The FDB table size for the card drops below 90% of the card limit.

Recovery

None needed.

2.10.15. tmnxCardResMacFdbHighUsgSet

tmnxCardResMacFdbHighUsgSet:CHASSIS
Table 159:  tmnxCardResMacFdbHighUsgSet properties 

Property name

Value

Application name

CHASSIS

Event ID

5163

Event name

tmnxCardResMacFdbHighUsgSet

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.148

Default severity

minor

Message format string

The FDB table usage for card $tmnxMacScaleCardSlotNum$ is above 95% of the card limit

Cause

The tmnxCardResMacFdbHighUsgSet notification is generated when the FDB table size exceeds 95% of the card limit.

Effect

The FDB table size for the card exceeds 95% of the card limit.

Recovery

None needed.

2.10.16. tmnxChassisHiBwMcastAlarm

tmnxChassisHiBwMcastAlarm:CHASSIS
Table 160:  tmnxChassisHiBwMcastAlarm properties 

Property name

Value

Application name

CHASSIS

Event ID

2052

Event name

tmnxChassisHiBwMcastAlarm

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.43

Default severity

minor

Message format string

Class $tmnxHwClass$ : Plane shared by multiple multicast high bandwidth taps

Cause

The tmnxChassisHiBwMcastAlarm notification is generated when a plane is shared by more than one high bandwidth multicast tap.

Effect

N/A

Recovery

N/A

2.10.17. tmnxChassisNotificationClear

tmnxChassisNotificationClear:CHASSIS
Table 161:  tmnxChassisNotificationClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2016

Event name

tmnxChassisNotificationClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.25

Default severity

major

Message format string

Clear $tmnxHwClass$ $tmnxHwIndex$ $tmnxChassisNotifyOID$

Cause

A trap indicating the clear of a chassis notification identified by tmnxChassisNotifyOID.

Effect

N/A

Recovery

N/A

2.10.18. tmnxChassisUpgradeComplete

tmnxChassisUpgradeComplete:CHASSIS
Table 162:  tmnxChassisUpgradeComplete properties 

Property name

Value

Application name

CHASSIS

Event ID

2034

Event name

tmnxChassisUpgradeComplete

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.42

Default severity

major

Message format string

Class $tmnxHwClass$ : software upgrade complete

Cause

The tmnxChassisUpgradeComplete notification is generated to indicate that all the IOMs are running matching software versions in reference to the active CPM software version changed as part of the upgrade process.

Effect

N/A

Recovery

N/A

2.10.19. tmnxChassisUpgradeInProgress

tmnxChassisUpgradeInProgress:CHASSIS
Table 163:  tmnxChassisUpgradeInProgress properties 

Property name

Value

Application name

CHASSIS

Event ID

2033

Event name

tmnxChassisUpgradeInProgress

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.41

Default severity

major

Message format string

Class $tmnxHwClass$ : software upgrade in progress

Cause

The tmnxChassisUpgradeInProgress notification is generated only after a CPM switchover occurs and the new active CPM is running new software, while the IOMs or XCMs are still running old software. This is the start of the upgrade process. The tmnxChassisUpgradeInProgress notification will continue to be generated every 30 minutes while at least one IOM is still running older software.

Effect

A software mismatch between the CPM and IOM or XCM is generally fine for a short duration (during an upgrade) but may not allow for correct long term operation.

Recovery

Complete the upgrade of all IOMs or XCMs.

2.10.20. tmnxCpmALocalIcPortAvail

tmnxCpmALocalIcPortAvail:CHASSIS
Table 164:  tmnxCpmALocalIcPortAvail properties 

Property name

Value

Application name

CHASSIS

Event ID

4009

Event name

tmnxCpmALocalIcPortAvail

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.6

Default severity

major

Message format string

CPM $tmnxChassisNotifyCpmCardSlotNum$ can reach the chassis using its local CPM interconnect ports

Cause

The tmnxCpmLocalIcPortAvail notification is generated when the CPM re-establishes communication with the other chassis using its local CPM interconnect ports.

Effect

A new control communications path is now available between the CPM and the other chassis.

Recovery

N/A

2.10.21. tmnxCpmANoLocalIcPort

tmnxCpmANoLocalIcPort:CHASSIS
Table 165:  tmnxCpmANoLocalIcPort properties 

Property name

Value

Application name

CHASSIS

Event ID

4007

Event name

tmnxCpmANoLocalIcPort

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.5

Default severity

major

Message format string

CPM $tmnxChassisNotifyCpmCardSlotNum$ can not reach the chassis using its local CPM interconnect ports

Cause

The tmnxCpmNoLocalIcPort alarm is generated when the CPM cannot reach the other chassis using its local CPM interconnect ports.

Effect

Another control communications path may still be available between the CPM and the other chassis via the mate CPM in the same chassis. If that alternative path is not available then complete disruption of control communications to the other chassis will occur and the tmnxInterChassisCommsDown alarm is raised. A tmnxCpmNoLocalIcPort alarm on the active CPM indicates that a further failure of the local CPM interconnect ports on the standby CPM will cause complete disruption of control communications to the other chassis and the tmnxInterChassisCommsDown alarm is raised. A tmnxCpmNoLocalIcPort alarm on the standby CPM indicates that a CPM switchover may cause temporary disruption of control communications to the other chassis while the rebooting CPM comes back into service.

Recovery

Ensure that all CPM interconnect ports in the system are properly cabled together with working cables.

2.10.22. tmnxCpmBLocalIcPortAvail

tmnxCpmBLocalIcPortAvail:CHASSIS
Table 166:  tmnxCpmBLocalIcPortAvail properties 

Property name

Value

Application name

CHASSIS

Event ID

4010

Event name

tmnxCpmBLocalIcPortAvail

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.6

Default severity

major

Message format string

CPM $tmnxChassisNotifyCpmCardSlotNum$ can reach the chassis using its local CPM interconnect ports

Cause

The tmnxCpmLocalIcPortAvail notification is generated when the CPM re-establishes communication with the other chassis using its local CPM interconnect ports.

Effect

A new control communications path is now available between the CPM and the other chassis.

Recovery

N/A

2.10.23. tmnxCpmBNoLocalIcPort

tmnxCpmBNoLocalIcPort:CHASSIS
Table 167:  tmnxCpmBNoLocalIcPort properties 

Property name

Value

Application name

CHASSIS

Event ID

4008

Event name

tmnxCpmBNoLocalIcPort

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.5

Default severity

major

Message format string

CPM $tmnxChassisNotifyCpmCardSlotNum$ can not reach the chassis using its local CPM interconnect ports

Cause

The tmnxCpmNoLocalIcPort alarm is generated when the CPM cannot reach the other chassis using its local CPM interconnect ports.

Effect

Another control communications path may still be available between the CPM and the other chassis via the mate CPM in the same chassis. If that alternative path is not available then complete disruption of control communications to the other chassis will occur and the tmnxInterChassisCommsDown alarm is raised. A tmnxCpmNoLocalIcPort alarm on the active CPM indicates that a further failure of the local CPM interconnect ports on the standby CPM will cause complete disruption of control communications to the other chassis and the tmnxInterChassisCommsDown alarm is raised. A tmnxCpmNoLocalIcPort alarm on the standby CPM indicates that a CPM switchover may cause temporary disruption of control communications to the other chassis while the rebooting CPM comes back into service.

Recovery

Ensure that all CPM interconnect ports in the system are properly cabled together with working cables.

2.10.24. tmnxCpmCardSyncFileNotPresent

tmnxCpmCardSyncFileNotPresent:CHASSIS
Table 168:  tmnxCpmCardSyncFileNotPresent properties 

Property name

Value

Application name

CHASSIS

Event ID

2057

Event name

tmnxCpmCardSyncFileNotPresent

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.45

Default severity

minor

Message format string

Class $tmnxHwClass$ : Optional file $tmnxChassisNotifyCardSyncFile$ is not present during sync operation

Cause

The tmnxCpmCardSyncFileNotPresent notification is generated when the redundancy file synchronization failed to locate an optional file.

Effect

N/A

Recovery

N/A

2.10.25. tmnxCpmIcPortDDMClear

tmnxCpmIcPortDDMClear:CHASSIS
Table 169:  tmnxCpmIcPortDDMClear properties 

Property name

Value

Application name

CHASSIS

Event ID

4016

Event name

tmnxCpmIcPortDDMClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.9

Default severity

minor

Message format string

CPM interconnect port SFF DDM $tmnxDDMLaneIdOrModule$ ($tmnxDDMFailedObject$) cleared

Cause

The tmnxCpmIcPortDDMFailure notification is generated when an SFF in a CPM interconnect port that supports Digital Diagnostic Monitoring (DDM) clears a failed state.

Effect

N/A

Recovery

N/A

2.10.26. tmnxCpmIcPortDDMFailure

tmnxCpmIcPortDDMFailure:CHASSIS
Table 170:  tmnxCpmIcPortDDMFailure properties 

Property name

Value

Application name

CHASSIS

Event ID

4015

Event name

tmnxCpmIcPortDDMFailure

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.8

Default severity

minor

Message format string

CPM interconnect port SFF DDM $tmnxDDMLaneIdOrModule$ ($tmnxDDMFailedObject$) raised

Cause

The tmnxCpmIcPortDDMFailure notification is generated when an SFF in a CPM interconnect port that supports Digital Diagnostic Monitoring (DDM) enters a failed state.

Effect

N/A

Recovery

N/A

2.10.27. tmnxCpmIcPortDown

tmnxCpmIcPortDown:CHASSIS
Table 171:  tmnxCpmIcPortDown properties 

Property name

Value

Application name

CHASSIS

Event ID

4003

Event name

tmnxCpmIcPortDown

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.1

Default severity

minor

Message format string

CPM interconnect port is not operational. Error code = $tmnxCpmIcPortOperState$

Cause

The tmnxCpmIcPortDown alarm is generated when the CPM interconnect port is not operational. The reason may be a cable connected incorrectly, a disconnected cable, a faulty cable, or a misbehaving CPM interconnect port or card.

Effect

At least one of the control plane paths used for inter-chassis CPM communication is not operational. Other paths may be available.

Recovery

A manual verification and testing of each CPM interconnect port is required to ensure fully functional operation. Physical replacement of cabling may be required.

2.10.28. tmnxCpmIcPortSFFInserted

tmnxCpmIcPortSFFInserted:CHASSIS
Table 172:  tmnxCpmIcPortSFFInserted properties 

Property name

Value

Application name

CHASSIS

Event ID

4005

Event name

tmnxCpmIcPortSFFInserted

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.3

Default severity

minor

Message format string

CPM interconnect port SFF inserted

Cause

The tmnxCpmIcPortSFFInserted notification is generated when the small form factor (SFF) pluggable optical module (for example, QSFP) is inserted into a CPM interconnect port.

Effect

This event is for notification only.

Recovery

N/A

2.10.29. tmnxCpmIcPortSFFRemoved

tmnxCpmIcPortSFFRemoved:CHASSIS
Table 173:  tmnxCpmIcPortSFFRemoved properties 

Property name

Value

Application name

CHASSIS

Event ID

4006

Event name

tmnxCpmIcPortSFFRemoved

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.4

Default severity

minor

Message format string

CPM interconnect port SFF removed

Cause

The tmnxCpmIcPortSFFRemoved notification is generated when the SFF (eg. QSFP) is removed from the CPM interconnect port. Removing an SFF causes both this trap, and also a tmnxCpmIcPortDown event.

Effect

Removing the SFF will cause the CPM interconnect port to go down. This port will no longer be able to be used as part of the control plane between chassis but other paths may be available.

Recovery

Insert a working SFF into the port.

2.10.30. tmnxCpmIcPortUp

tmnxCpmIcPortUp:CHASSIS
Table 174:  tmnxCpmIcPortUp properties 

Property name

Value

Application name

CHASSIS

Event ID

4004

Event name

tmnxCpmIcPortUp

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.2

Default severity

minor

Message format string

CPM interconnect port is operational

Cause

The tmnxCpmIcPortUp notification is generated when the CPM interconnect port is operational again.

Effect

A control plane communication path between CPM cards in the different chassis have been established.

Recovery

N/A

2.10.31. tmnxCpmMemSizeMismatch

tmnxCpmMemSizeMismatch:CHASSIS
Table 175:  tmnxCpmMemSizeMismatch properties 

Property name

Value

Application name

CHASSIS

Event ID

2153

Event name

tmnxCpmMemSizeMismatch

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.140

Default severity

major

Message format string

The standby CPM $tmnxChassisNotifyCpmCardSlotNum$ has a different memory size than the active $tmnxChassisNotifyHwIndex$

Cause

A tmnxCpmMemSizeMismatch notification is generated when the RAM memory size of the standby CPM (i.e., tmnxChassisNotifyCpmCardSlotNum) is different than the active CPM (i.e., tmnxChassisNotifyHwIndex).

Effect

There is an increased risk of the memory overflow on the standby CPM during the CPM switchover.

Recovery

Use CPMs with the same memory size.

2.10.32. tmnxCpmMemSizeMismatchClear

tmnxCpmMemSizeMismatchClear:CHASSIS
Table 176:  tmnxCpmMemSizeMismatchClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2154

Event name

tmnxCpmMemSizeMismatchClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.141

Default severity

cleared

Message format string

The standby CPM $tmnxChassisNotifyCpmCardSlotNum$ has the same memory size as the active $tmnxChassisNotifyHwIndex$

Cause

A tmnxCpmMemSizeMismatchClear notification is generated when the RAM memory sizes of the standby (i.e., tmnxChassisNotifyCpmCardSlotNum) and active (i.e., tmnxChassisNotifyHwIndex) CPMs become matched.

Effect

The tmnxCpmMemSizeMismatch notification is cleared.

Recovery

There is no recovery required for this notification.

2.10.33. tmnxDcpCardFpEventOvrflw

tmnxDcpCardFpEventOvrflw:CHASSIS
Table 177:  tmnxDcpCardFpEventOvrflw properties 

Property name

Value

Application name

CHASSIS

Event ID

2084

Event name

tmnxDcpCardFpEventOvrflw

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.72

Default severity

minor

Message format string

TODO

Cause

The tmnxDcpCardFpEventOvrflw notification is generated when a flood of distributed CPU FP protection events occur on a particular card and some of the events are lost due to event throttling mechanism.

Effect

Some FP notifications configured on the card may not be received.

Recovery

Notifications will resume once the event throttling ends.

2.10.34. tmnxDcpCardFpEventOvrflwClr

tmnxDcpCardFpEventOvrflwClr:CHASSIS
Table 178:  tmnxDcpCardFpEventOvrflwClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2089

Event name

tmnxDcpCardFpEventOvrflwClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.77

Default severity

minor

Message format string

TODO

Cause

The tmnxDcpCardFpEventOvrflwClr notification is generated when the event throttling has ended for distributed CPU protection FP events on a particular card.

Effect

Notifications are received again since the event throttling has ended.

Recovery

There is no recovery for this notification.

2.10.35. tmnxDcpCardSapEventOvrflw

tmnxDcpCardSapEventOvrflw:CHASSIS
Table 179:  tmnxDcpCardSapEventOvrflw properties 

Property name

Value

Application name

CHASSIS

Event ID

2085

Event name

tmnxDcpCardSapEventOvrflw

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.73

Default severity

minor

Message format string

TODO

Cause

The tmnxDcpCardSapEventOvrflw notification is generated when a flood of distributed CPU protection SAP events occur on a particular card and some of the events are lost due to event throttling mechanism.

Effect

Some SAP notifications configured on the card may not be received.

Recovery

Notifications will resume once the event throttling ends.

2.10.36. tmnxDcpCardSapEventOvrflwClr

tmnxDcpCardSapEventOvrflwClr:CHASSIS
Table 180:  tmnxDcpCardSapEventOvrflwClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2090

Event name

tmnxDcpCardSapEventOvrflwClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.78

Default severity

minor

Message format string

TODO

Cause

The tmnxDcpCardSapEventOvrflwClr notification is generated when the event throttling has ended for distributed CPU protection SAP events on a particular card.

Effect

Notifications are received again since the event throttling has ended.

Recovery

There is no recovery for this notification.

2.10.37. tmnxDcpCardVrtrIfEventOvrflw

tmnxDcpCardVrtrIfEventOvrflw:CHASSIS
Table 181:  tmnxDcpCardVrtrIfEventOvrflw properties 

Property name

Value

Application name

CHASSIS

Event ID

2086

Event name

tmnxDcpCardVrtrIfEventOvrflw

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.74

Default severity

minor

Message format string

TODO

Cause

The tmnxDcpCardVrtrIfEventOvrflw notification is generated when a flood of distributed CPU protection network-interface events occur on a particular card and some of the events are lost due to event throttling mechanism.

Effect

Some network-interface notifications configured on the card may not be received.

Recovery

Notifications will resume once the event throttling ends.

2.10.38. tmnxDcpCardVrtrIfEventOvrflwClr

tmnxDcpCardVrtrIfEventOvrflwClr:CHASSIS
Table 182:  tmnxDcpCardVrtrIfEventOvrflwClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2091

Event name

tmnxDcpCardVrtrIfEventOvrflwClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.79

Default severity

minor

Message format string

TODO

Cause

The tmnxDcpCardVrtrIfEventOvrflwClr notification is generated when the event throttling has ended for distributed CPU protection network-interface events on a particular card.

Effect

Notifications are received again since the event throttling has ended.

Recovery

There is no recovery for this notification.

2.10.39. tmnxDcpFpDynPoolUsageHiAlmClear

tmnxDcpFpDynPoolUsageHiAlmClear:CHASSIS
Table 183:  tmnxDcpFpDynPoolUsageHiAlmClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2088

Event name

tmnxDcpFpDynPoolUsageHiAlmClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.76

Default severity

minor

Message format string

TODO

Cause

The tmnxDcpFpDynPoolUsageHiAlmClear notification is generated when the dynamic enforcement policer pool usage on the forwarding plane is no longer exhausted.

Effect

Dynamic enforcement policers are available in the free pool to be allocated when needed.

Recovery

There is no recovery required for this notification.

2.10.40. tmnxDcpFpDynPoolUsageHiAlmRaise

tmnxDcpFpDynPoolUsageHiAlmRaise:CHASSIS
Table 184:  tmnxDcpFpDynPoolUsageHiAlmRaise properties 

Property name

Value

Application name

CHASSIS

Event ID

2087

Event name

tmnxDcpFpDynPoolUsageHiAlmRaise

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.75

Default severity

minor

Message format string

TODO

Cause

The tmnxDcpFpDynPoolUsageHiAlmRaise notification is generated when the dynamic enforcement policer pool usage on the forwarding plane is nearly exhausted.

Effect

Dynamic enforcement policers may not get allocated on the forwarding plane.

Recovery

This notification will be cleared when either the dynamic enforcement policer pool is increased or the usage drops.

2.10.41. tmnxEnvTempTooHigh

tmnxEnvTempTooHigh:CHASSIS
Table 185:  tmnxEnvTempTooHigh properties 

Property name

Value

Application name

CHASSIS

Event ID

2005

Event name

tmnxEnvTempTooHigh

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.2

Default severity

major

Message format string

$tmnxHwClass$ $tmnxChassisNotifyHwIndex$: temperature too high

Cause

Generated when the temperature sensor reading on an equipment object is greater than its configured threshold.

Effect

This could be causing intermittent errors and could also cause permanent damage to components.

Recovery

Remove or power down the affected cards, or improve the cooling to the node. More powerful fan trays may also be required.

2.10.42. tmnxEqBpEpromFail

tmnxEqBpEpromFail:CHASSIS
Table 186:  tmnxEqBpEpromFail properties 

Property name

Value

Application name

CHASSIS

Event ID

2161

Event name

tmnxEqBpEpromFail

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.150

Default severity

critical

Message format string

CPM BP EPROM could not be accessed

Cause

The tmnxEqBpEpromFail notification is generated when the active CPM is no longer able to access the backplane EPROM due to a hardware defect.

Effect

The active CPM is at risk of failing to initialize after node reboot due to not being able to access the BP EPROM to read the chassis type.

Recovery

Contact Nokia customer support.

2.10.43. tmnxEqBpEpromFailClear

tmnxEqBpEpromFailClear:CHASSIS
Table 187:  tmnxEqBpEpromFailClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2162

Event name

tmnxEqBpEpromFailClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.151

Default severity

cleared

Message format string

CPM BP EPROM can now be accessed

Cause

The tmnxEqBpEpromFailClear notification is generated when the EPROM error condition is cleared.

Effect

N/A

Recovery

N/A

2.10.44. tmnxEqBpEpromWarning

tmnxEqBpEpromWarning:CHASSIS
Table 188:  tmnxEqBpEpromWarning properties 

Property name

Value

Application name

CHASSIS

Event ID

2163

Event name

tmnxEqBpEpromWarning

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.152

Default severity

minor

Message format string

One CPM BP EPROM could not be accessed

Cause

The tmnxEqBpEpromWarning notification is generated when the active CPM is no longer able to access one backplane EPROM due to a hardware defect but a redundant EPROM is present and accessible.

Effect

There is no effect on system operation.

Recovery

No recovery action required.

2.10.45. tmnxEqBpEpromWarningClear

tmnxEqBpEpromWarningClear:CHASSIS
Table 189:  tmnxEqBpEpromWarningClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2164

Event name

tmnxEqBpEpromWarningClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.153

Default severity

cleared

Message format string

All CPM BP EPROMs can be accessed

Cause

The tmnxEqBpEpromWarningClear notification is generated when the backplane EPROM warning condition is cleared.

Effect

N/A

Recovery

N/A

2.10.46. tmnxEqCardChipIfCellEvent

tmnxEqCardChipIfCellEvent:CHASSIS
Table 190:  tmnxEqCardChipIfCellEvent properties 

Property name

Value

Application name

CHASSIS

Event ID

2103

Event name

tmnxEqCardChipIfCellEvent

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.90

Default severity

minor

Message format string

$tmnxHwIndex$ experienced internal datapath cell errors

Slot $tmnxHwIndex$ experienced internal datapath cell errors on complex $tmnxCardComplexNumber$

Cause

The tmnxEqCardChipIfCellEvent notification is generated when an inter-chip interface (XPL2 bundle) experiences internal datapath cell errors.

Effect

Contact Nokia customer support.

Recovery

Contact Nokia customer support.

2.10.47. tmnxEqCardChipIfDownEvent

tmnxEqCardChipIfDownEvent:CHASSIS
Table 191:  tmnxEqCardChipIfDownEvent properties 

Property name

Value

Application name

CHASSIS

Event ID

2102

Event name

tmnxEqCardChipIfDownEvent

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.89

Default severity

minor

Message format string

$tmnxHwIndex$ experienced an internal datapath problem

Slot $tmnxHwIndex$ experienced an internal datapath problem on complex $tmnxCardComplexNumber$

Cause

The tmnxEqCardChipIfDownEvent notification is generated when an inter-chip interface (XPL2 bundle) experiences an internal datapath problem.

Effect

7750 SR/7450 ESS: The IOM or IMM will either remain operational or the card will reset along with its associated MDAs. 7950 XRS: The associated XMA (MDA CLI context) will either remain operational or it will reset. The XCM (CLI card context) will not reset.

Recovery

Contact Nokia customer support.

2.10.48. tmnxEqCardFailure

tmnxEqCardFailure:CHASSIS
Table 192:  tmnxEqCardFailure properties 

Property name

Value

Application name

CHASSIS

Event ID

2001

Event name

tmnxEqCardFailure

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.7

Default severity

major

Message format string

Class $tmnxHwClass$ : failed, reason: $tmnxChassisNotifyCardFailureReason$

Cause

Generated when one of the cards in a chassis has failed. The card type may be IOM (or XCM), MDA (or XMA), SFM, CCM, CPM, Compact Flash, etc. The reason is indicated in the details of the log event or alarm, and also available in the tmnxChassisNotifyCardFailureReason attribute included in the SNMP notification.

Effect

The effect is dependent on the card that has failed. IOM (or XCM) or MDA (or XMA) failure will cause a loss of service for all services running on that card. A fabric failure can impact traffic to/from all cards. 7750 SR/7450 ESS - If the IOM/IMM fails then the two associated MDAs for the slot will also go down. 7950 XRS - If one out of two XMAs fails in a XCM slot then the XCM will remain up. If only one remaining operational XMA within a XCM slot fails, then the XCM will go into a booting operational state.

Recovery

Before taking any recovery steps, collect a tech-support file, then try resetting (clear) the card. If that doesn't work then try removing and then reinserting the card. If that doesn't work then replace the card.

2.10.49. tmnxEqCardFirmwareUpgraded

tmnxEqCardFirmwareUpgraded:CHASSIS
Table 193:  tmnxEqCardFirmwareUpgraded properties 

Property name

Value

Application name

CHASSIS

Event ID

2032

Event name

tmnxEqCardFirmwareUpgraded

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.40

Default severity

major

Message format string

Class $tmnxHwClass$ : firmware upgraded

Cause

Generated when a card is hot-inserted into the chassis and its firmware is automatically upgraded. The card type may be IOM or CPM module.

Effect

N/A

Recovery

N/A

2.10.50. tmnxEqCardInserted

tmnxEqCardInserted:CHASSIS
Table 194:  tmnxEqCardInserted properties 

Property name

Value

Application name

CHASSIS

Event ID

2002

Event name

tmnxEqCardInserted

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.8

Default severity

minor

Message format string

Class $tmnxHwClass$ : inserted

Cause

Generated when a card is inserted into the chassis. The card type may be IOM, Fabric, MDA, MCM, CCM CPM module, compact flash module, etc.

Effect

N/A

Recovery

N/A

2.10.51. tmnxEqCardPChipCamEvent

tmnxEqCardPChipCamEvent:CHASSIS
Table 195:  tmnxEqCardPChipCamEvent properties 

Property name

Value

Application name

CHASSIS

Event ID

2076

Event name

tmnxEqCardPChipCamEvent

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.64

Default severity

critical

Message format string

A fault has been detected in the hardware on IOM $tmnxSlotNum$-forwarding engine $tmnxCardComplexNumber$

Cause

The tmnxEqCardPChipCamEvent notification is generated when either an IOM or a CPM experiences a persistent occurrence of a PChip CAM error. On a CPM card, the tmnxCardComplexNumber will be fixed to the value zero (0).

Effect

Contact Nokia customer support.

Recovery

Contact Nokia customer support.

2.10.52. tmnxEqCardPChipError

tmnxEqCardPChipError:CHASSIS
Table 196:  tmnxEqCardPChipError properties 

Property name

Value

Application name

CHASSIS

Event ID

2059

Event name

tmnxEqCardPChipError

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.47

Default severity

minor

Message format string

Slot $tmnxCardSlotNum$ detected $tmnxCardFwdDirection$ FCS errors on complex $tmnxCardComplexNumber$. Source card(s) of detected errors: $tmnxCardSrcSlotBitmap$

Cause

The tmnxEqCardPChipError notification is generated when persistent FCS errors are detected by the P chip in either the ingress or egress datapath/complex. The value tmnxCardSrcSlotBitmap is only used for the egress datapath/complex direction.

Effect

N/A

Recovery

N/A

2.10.53. tmnxEqCardPChipMemoryEvent

tmnxEqCardPChipMemoryEvent:CHASSIS
Table 197:  tmnxEqCardPChipMemoryEvent properties 

Property name

Value

Application name

CHASSIS

Event ID

2063

Event name

tmnxEqCardPChipMemoryEvent

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.51

Default severity

minor

Message format string

$tmnxHwIndex$ experienced a pchip memory error occurrence

Slot $tmnxHwIndex$ experienced a pchip parity error occurrence on complex $tmnxCardComplexNumber$

Cause

The tmnxEqCardPChipMemoryEvent notification is generated when a P-chip experiences an occurrence of a memory error.

Effect

N/A

Recovery

N/A

2.10.54. tmnxEqCardQChipBufMemoryEvent

tmnxEqCardQChipBufMemoryEvent:CHASSIS
Table 198:  tmnxEqCardQChipBufMemoryEvent properties 

Property name

Value

Application name

CHASSIS

Event ID

2098

Event name

tmnxEqCardQChipBufMemoryEvent

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.86

Default severity

minor

Message format string

$tmnxHwIndex$ experienced a Q-chip buffer memory error occurrence

Slot $tmnxHwIndex$ experienced a Q-chip buffer memory error occurrence on complex $tmnxCardComplexNumber$

Cause

The tmnxEqCardQChipBufMemoryEvent notification is generated when a Q-chip experiences an occurrence of a buffer memory error.

Effect

Contact Nokia customer support.

Recovery

Contact Nokia customer support.

2.10.55. tmnxEqCardQChipIntMemoryEvent

tmnxEqCardQChipIntMemoryEvent:CHASSIS
Table 199:  tmnxEqCardQChipIntMemoryEvent properties 

Property name

Value

Application name

CHASSIS

Event ID

2101

Event name

tmnxEqCardQChipIntMemoryEvent

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.88

Default severity

minor

Message format string

$tmnxHwIndex$ experienced a qchip internal memory error occurrence

Slot $tmnxHwIndex$ experienced a qchip internal memory error occurrence on complex $tmnxCardComplexNumber$

Cause

The tmnxEqCardQChipIntMemoryEvent notification is generated when a Q-chip experiences an occurrence of an internal memory error.

Effect

Contact Nokia customer support.

Recovery

Contact Nokia customer support.

2.10.56. tmnxEqCardQChipStatsMemoryEvent

tmnxEqCardQChipStatsMemoryEvent:CHASSIS
Table 200:  tmnxEqCardQChipStatsMemoryEvent properties 

Property name

Value

Application name

CHASSIS

Event ID

2099

Event name

tmnxEqCardQChipStatsMemoryEvent

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.87

Default severity

minor

Message format string

$tmnxHwIndex$ experienced a Q-chip statistics memory error occurrence

Slot $tmnxHwIndex$ experienced a Q-chip statistics memory error occurrence on complex $tmnxCardComplexNumber$

Cause

The tmnxEqCardQChipStatsMemoryEvent notification is generated when a Q-chip experiences an occurrence of a statistics memory error.

Effect

Contact Nokia customer support.

Recovery

Contact Nokia customer support.

2.10.57. tmnxEqCardRemoved

tmnxEqCardRemoved:CHASSIS
Table 201:  tmnxEqCardRemoved properties 

Property name

Value

Application name

CHASSIS

Event ID

2003

Event name

tmnxEqCardRemoved

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.9

Default severity

major

Message format string

Class $tmnxHwClass$ : removed

Cause

Generated when a card is removed from the chassis. The card type may be IOM (or XCM), MDA (or XMA), SFM, CCM, CPM, Compact Flash, etc.

Effect

The effect is dependent on the card that has been removed. IOM (or XCM) or MDA (or XMA) removal will cause a loss of service for all services running on that card. A fabric removal can impact traffic to/from all cards.

Recovery

Before taking any recovery steps collect a tech-support file, then try re-inserting the card. If that doesn't work then replace the card.

2.10.58. tmnxEqCardSoftResetAlarm

tmnxEqCardSoftResetAlarm:CHASSIS
Table 202:  tmnxEqCardSoftResetAlarm properties 

Property name

Value

Application name

CHASSIS

Event ID

2060

Event name

tmnxEqCardSoftResetAlarm

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.48

Default severity

minor

Message format string

Slot $tmnxHwIndex$ entered soft-reset state $tmnxCardSoftResetState$

Cause

The tmnxEqCardSoftResetAlarm notification is generated when an IOM card enters and exits the 'soft-reset' state.

Effect

N/A

Recovery

N/A

2.10.59. tmnxEqCardTChipParityEvent

tmnxEqCardTChipParityEvent:CHASSIS
Table 203:  tmnxEqCardTChipParityEvent properties 

Property name

Value

Application name

CHASSIS

Event ID

2110

Event name

tmnxEqCardTChipParityEvent

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.97

Default severity

minor

Message format string

Slot $tmnxHwIndex$ experienced a T-chip memory error occurrence on complex $tmnxCardComplexNumber$

Cause

The tmnxEqCardTChipParityEvent notification is generated when a T-chip experiences an occurrence of an internal memory error.

Effect

Contact Nokia customer support.

Recovery

Contact Nokia customer support.

2.10.60. tmnxEqDataPathFailureProtImpact

tmnxEqDataPathFailureProtImpact:CHASSIS
Table 204:  tmnxEqDataPathFailureProtImpact properties 

Property name

Value

Application name

CHASSIS

Event ID

2126

Event name

tmnxEqDataPathFailureProtImpact

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.113

Default severity

minor

Message format string

$tmnxHwClass$ $tmnxHwIndex$ experienced a datapath failure which impacted a protocol.

Cause

The tmnxEqDataPathFailureProtImpact notification is generated when a slot experienced a data path failure which impacted a protocol.

Effect

Services-related data associated with the impacted protocol may be lost.

Recovery

N/A

2.10.61. tmnxEqFlashDataLoss

tmnxEqFlashDataLoss:CHASSIS
Table 205:  tmnxEqFlashDataLoss properties 

Property name

Value

Application name

CHASSIS

Event ID

2023

Event name

tmnxEqFlashDataLoss

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.32

Default severity

major

Message format string

Class $tmnxHwClass$ : probable data loss

Cause

tmnxEqFlashDataLoss is generated when an error occurs while data was being written to the compact flash. This notification indicates a probable data loss.

Effect

N/A

Recovery

N/A

2.10.62. tmnxEqFlashDiskFull

tmnxEqFlashDiskFull:CHASSIS
Table 206:  tmnxEqFlashDiskFull properties 

Property name

Value

Application name

CHASSIS

Event ID

2024

Event name

tmnxEqFlashDiskFull

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.33

Default severity

major

Message format string

Class $tmnxHwClass$ : disk full

Cause

tmnxEqFlashDiskFull is generated when there is no space left on the compact flash. No more data can be written to it.

Effect

N/A

Recovery

N/A

2.10.63. tmnxEqHwEnhancedCapability

tmnxEqHwEnhancedCapability:CHASSIS
Table 207:  tmnxEqHwEnhancedCapability properties 

Property name

Value

Application name

CHASSIS

Event ID

2078

Event name

tmnxEqHwEnhancedCapability

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.66

Default severity

major

Message format string

CPM Upgrade In Progress. Card in slot $tmnxCardSlotNum$ has enhanced capabilities.

Cause

The tmnxEqHwEnhancedCapability notification is generated when the hardware, specified by the supplied objects, consists of enhanced capabilities as compared to the active hardware.

Effect

The system behaves normally under this situation, however, switching to the newer hardware will put the system in an incompatible state with the currently active hardware. That is, once this device takes activity, the lesser capable hardware will fail to communicate with it. In this mode, the system is deemed in a 'one-way upgrade' scenario.

Recovery

Two modes of recovery exist for this notification: 1) Remove the enhanced hardware, and supply a more compatible device (status quo) with the active hardware. 2) Switch to the enhanced device, and replace the older hardware with a similarly enhanced device (upgrade).

2.10.64. tmnxEqLowSwitchFabricCap

tmnxEqLowSwitchFabricCap:CHASSIS
Table 208:  tmnxEqLowSwitchFabricCap properties 

Property name

Value

Application name

CHASSIS

Event ID

2104

Event name

tmnxEqLowSwitchFabricCap

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.91

Default severity

major

Message format string

The switch fabric capacity is less than the forwarding capacity of $tmnxHwClass$ $tmnxHwIndex$ due to errors in fabric links.

Cause

The tmnxEqLowSwitchFabricCap alarm is generated when the total switch fabric capacity becomes less than the IOM capacity due to link failures. At least one of the taps on the IOM is below 100% capacity.

Effect

There is diminished switch fabric capacity to forward service-impacting information.

Recovery

If the system does not self-recover, the IOM must be rebooted.

2.10.65. tmnxEqLowSwitchFabricCapClear

tmnxEqLowSwitchFabricCapClear:CHASSIS
Table 209:  tmnxEqLowSwitchFabricCapClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2105

Event name

tmnxEqLowSwitchFabricCapClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.92

Default severity

major

Message format string

The switch fabric capacity alarm for $tmnxHwClass$ $tmnxHwIndex$ was cleared.

Cause

The tmnxEqLowSwitchFabricCapClear notification is generated when the link failures that resulted in the tmnxEqLowSwitchFabricCap alarm to be raised have been resolved.

Effect

There is sufficient switch fabric capacity to forward service-impacting information.

Recovery

N/A

2.10.66. tmnxEqMdaCfgNotCompatible

tmnxEqMdaCfgNotCompatible:CHASSIS
Table 210:  tmnxEqMdaCfgNotCompatible properties 

Property name

Value

Application name

CHASSIS

Event ID

2056

Event name

tmnxEqMdaCfgNotCompatible

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.44

Default severity

major

Message format string

Class $tmnxHwClass$ : configuration not compatible with equipped MDA

Cause

Generated when a supported MDA is inserted into a slot of an IOM, the MDA is compatible with the currently provisioned MDA, but the current configuration on the MDA's ports is not compatible with the inserted MDA.

Effect

Though services can still be created, if the tmnxMdaNotifyType is the same as the tmnxMDAEquippedType then the MDA will fail to operate as configured and will be in a failed state.

Recovery

Change the configuration to reflect the capabilities of the MDA port, or switch out/re-provision the MDA for one that is compatible.

2.10.67. tmnxEqMdaIngrXplError

tmnxEqMdaIngrXplError:CHASSIS
Table 211:  tmnxEqMdaIngrXplError properties 

Property name

Value

Application name

CHASSIS

Event ID

2129

Event name

tmnxEqMdaIngrXplError

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.116

Default severity

minor

Message format string

MDA $tmnxCardSlotNum$/$tmnxEqMdaSlotNum$ experienced an ingress XPL error occurrence.

Cause

The tmnxEqMdaIngrXplError notification is generated when an MDA exhibits persistent ingress XPL errors.

Effect

Contact Nokia customer support.

Recovery

Contact Nokia customer support.

2.10.68. tmnxEqMdaSyncENotCompatible

tmnxEqMdaSyncENotCompatible:CHASSIS
Table 212:  tmnxEqMdaSyncENotCompatible properties 

Property name

Value

Application name

CHASSIS

Event ID

2061

Event name

tmnxEqMdaSyncENotCompatible

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.49

Default severity

major

Message format string

Provisioned synchronous ethernet not compatible with equipped MDA

Cause

The tmnxEqMdaSyncENotCompatible notification is generated when an MDA card is inserted into a slot of an IOM. The MDA is compatible with the currently provisioned MDA, but the currently configured synchronous ethernet, tmnxMDASynchronousEthernet, is not compatible with the inserted MDA.

Effect

Though services can still be created, if the tmnxMdaNotifyType is the same as the tmnxMDAEquippedType then the MDA will fail to operate as configured and will be in a failed state.

Recovery

Change the configuration to reflect the capabilities of the MDA port, or switch out/re-provision the MDA for one that is compatible.

2.10.69. tmnxEqMdaXplError

tmnxEqMdaXplError:CHASSIS
Table 213:  tmnxEqMdaXplError properties 

Property name

Value

Application name

CHASSIS

Event ID

2058

Event name

tmnxEqMdaXplError

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.46

Default severity

minor

Message format string

MDA $tmnxCardSlotNum$/$tmnxMDASlotNum$ experienced an egress XPL error occurrence.

Cause

The tmnxEqMdaXplError notification is generated when an MDA exhibits persistent egress XPL Errors.

Effect

N/A

Recovery

N/A

2.10.70. tmnxEqMgmtEthRedStandbyClear

tmnxEqMgmtEthRedStandbyClear:CHASSIS
Table 214:  tmnxEqMgmtEthRedStandbyClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2137

Event name

tmnxEqMgmtEthRedStandbyClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.122

Default severity

minor

Message format string

The active CPM's management Ethernet port $tmnxChassisNotifyMgmtEthRedPort$ is serving as the system's management Ethernet port.

Cause

The tmnxEqMgmtEthRedStandbyClear notification is generated when the active CPM's management Ethernet port goes operationally up and the management Ethernet port reverts from the standby CPM to the active CPM.

Effect

The management of the node is operating from the active CPM's management Ethernet port and is redundant.

Recovery

No recovery required.

2.10.71. tmnxEqMgmtEthRedStandbyRaise

tmnxEqMgmtEthRedStandbyRaise:CHASSIS
Table 215:  tmnxEqMgmtEthRedStandbyRaise properties 

Property name

Value

Application name

CHASSIS

Event ID

2136

Event name

tmnxEqMgmtEthRedStandbyRaise

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.121

Default severity

minor

Message format string

The standby CPM's management Ethernet port $tmnxChassisNotifyMgmtEthRedPort$ is serving as the system's management Ethernet port.

Cause

The tmnxEqMgmtEthRedStandbyRaise notification is generated when the active CPM's management Ethernet port goes operationally down and the standby CPM's management Ethernet port is operationally up and now serving as the system's management Ethernet port.

Effect

The management Ethernet port is no longer redundant. The node can be managed via the standby CPM's management Ethernet port only.

Recovery

Bring the active CPM's management Ethernet port operationally up.

2.10.72. tmnxEqPhysChassisFanFailure

tmnxEqPhysChassisFanFailure:CHASSIS
Table 216:  tmnxEqPhysChassisFanFailure properties 

Property name

Value

Application name

CHASSIS

Event ID

2148

Event name

tmnxEqPhysChassisFanFailure

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.135

Default severity

critical

Message format string

Chassis $tmnxPhysChassisNum$ fan $tmnxPhysChassisFanIndex$ failure

Cause

The tmnxEqPhysChassisFanFailure notification is generated when one of the fans in a fan tray fails on a particular physical chassis.

Effect

The fan is no longer operational.

Recovery

Insert a new fan.

2.10.73. tmnxEqPhysChassisFanFailureClear

tmnxEqPhysChassisFanFailureClear:CHASSIS
Table 217:  tmnxEqPhysChassisFanFailureClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2149

Event name

tmnxEqPhysChassisFanFailureClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.136

Default severity

cleared

Message format string

Chassis $tmnxPhysChassisNum$ fan $tmnxPhysChassisFanIndex$ failure cleared

Cause

The tmnxEqPhysChassisFanFailureClear notification is generated when the fan failure is cleared on the particular physical chassis.

Effect

The fan is operational again.

Recovery

There is no recovery for this notification.

2.10.74. tmnxEqPhysChassPowerSupAcFail

tmnxEqPhysChassPowerSupAcFail:CHASSIS
Table 218:  tmnxEqPhysChassPowerSupAcFail properties 

Property name

Value

Application name

CHASSIS

Event ID

2140

Event name

tmnxEqPhysChassPowerSupAcFail

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.127

Default severity

critical

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ AC failure

Cause

The tmnxEqPhysChassPowerSupAcFail notification is generated when an AC failure occurs on the power supply.

Effect

The power supply is no longer operational.

Recovery

Insert a new power supply.

2.10.75. tmnxEqPhysChassPowerSupAcFailClr

tmnxEqPhysChassPowerSupAcFailClr:CHASSIS
Table 219:  tmnxEqPhysChassPowerSupAcFailClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2141

Event name

tmnxEqPhysChassPowerSupAcFailClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.128

Default severity

cleared

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ AC failure cleared

Cause

The tmnxEqPhysChassPowerSupAcFailClr notification is generated when the AC failure is cleared on the power supply.

Effect

The power supply is operational again.

Recovery

There is no recovery for this notification.

2.10.76. tmnxEqPhysChassPowerSupDcFail

tmnxEqPhysChassPowerSupDcFail:CHASSIS
Table 220:  tmnxEqPhysChassPowerSupDcFail properties 

Property name

Value

Application name

CHASSIS

Event ID

2142

Event name

tmnxEqPhysChassPowerSupDcFail

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.129

Default severity

critical

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ DC failure

Cause

The tmnxEqPhysChassPowerSupDcFail notification is generated when a DC failure occurs on the power supply.

Effect

The power supply is no longer operational.

Recovery

Insert a new power supply.

2.10.77. tmnxEqPhysChassPowerSupDcFailClr

tmnxEqPhysChassPowerSupDcFailClr:CHASSIS
Table 221:  tmnxEqPhysChassPowerSupDcFailClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2143

Event name

tmnxEqPhysChassPowerSupDcFailClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.130

Default severity

cleared

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ DC failure cleared

Cause

The tmnxEqPhysChassPowerSupDcFailClr notification is generated when the DC failure is cleared on the power supply.

Effect

The power supply is operational again.

Recovery

There is no recovery for this notification.

2.10.78. tmnxEqPhysChassPowerSupInFail

tmnxEqPhysChassPowerSupInFail:CHASSIS
Table 222:  tmnxEqPhysChassPowerSupInFail properties 

Property name

Value

Application name

CHASSIS

Event ID

2144

Event name

tmnxEqPhysChassPowerSupInFail

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.131

Default severity

critical

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ input failure

Cause

The tmnxEqPhysChassPowerSupInFail notification is generated when an input failure occurs on the power supply.

Effect

The power supply is no longer operational.

Recovery

Check input feed and/or insert a new power supply.

2.10.79. tmnxEqPhysChassPowerSupInFailClr

tmnxEqPhysChassPowerSupInFailClr:CHASSIS
Table 223:  tmnxEqPhysChassPowerSupInFailClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2145

Event name

tmnxEqPhysChassPowerSupInFailClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.132

Default severity

cleared

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ input failure cleared

Cause

The tmnxEqPhysChassPowerSupInFailClr notification is generated when the input failure is cleared on the power supply.

Effect

The power supply is operational again.

Recovery

There is no recovery for this notification.

2.10.80. tmnxEqPhysChassPowerSupOutFail

tmnxEqPhysChassPowerSupOutFail:CHASSIS
Table 224:  tmnxEqPhysChassPowerSupOutFail properties 

Property name

Value

Application name

CHASSIS

Event ID

2146

Event name

tmnxEqPhysChassPowerSupOutFail

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.133

Default severity

critical

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ output failure

Cause

The tmnxEqPhysChassPowerSupOutFail notification is generated when an output failure occurs on the power supply.

Effect

The power supply is no longer operational.

Recovery

Insert a new power supply.

2.10.81. tmnxEqPhysChassPowerSupOutFailCl

tmnxEqPhysChassPowerSupOutFailCl:CHASSIS
Table 225:  tmnxEqPhysChassPowerSupOutFailCl properties 

Property name

Value

Application name

CHASSIS

Event ID

2147

Event name

tmnxEqPhysChassPowerSupOutFailCl

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.134

Default severity

cleared

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ output failure cleared

Cause

The tmnxEqPhysChassPowerSupOutFailCl notification is generated when an output failure is cleared on the power supply.

Effect

The power supply is operational again.

Recovery

There is no recovery for this notification.

2.10.82. tmnxEqPhysChassPowerSupOvrTmp

tmnxEqPhysChassPowerSupOvrTmp:CHASSIS
Table 226:  tmnxEqPhysChassPowerSupOvrTmp properties 

Property name

Value

Application name

CHASSIS

Event ID

2138

Event name

tmnxEqPhysChassPowerSupOvrTmp

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.125

Default severity

critical

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ over temperature

Cause

The tmnxEqPhysChassPowerSupOvrTmp notification is generated when a power supply's temperature surpasses the threshold of the particular physical chassis.

Effect

The power supply is no longer operational.

Recovery

Check input feed and/or insert a new power supply.

2.10.83. tmnxEqPhysChassPowerSupOvrTmpClr

tmnxEqPhysChassPowerSupOvrTmpClr:CHASSIS
Table 227:  tmnxEqPhysChassPowerSupOvrTmpClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2139

Event name

tmnxEqPhysChassPowerSupOvrTmpClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.126

Default severity

cleared

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ over temperature cleared

Cause

The tmnxEqPhysChassPowerSupOvrTmpClr notification is generated when a power supply's temperature is reduced below the threshold of the particular physical chassis.

Effect

The power supply is operational again.

Recovery

There is no recovery for this notification.

2.10.84. tmnxEqPowerCapacityExceeded

tmnxEqPowerCapacityExceeded:CHASSIS
Table 228:  tmnxEqPowerCapacityExceeded properties 

Property name

Value

Application name

CHASSIS

Event ID

2092

Event name

tmnxEqPowerCapacityExceeded

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.80

Default severity

minor

Message format string

The system has reached maximum power capacity $tmnxChassisNotifyPowerCapacity$ watts

Cause

The tmnxEqPowerCapacityExceeded alarm is generated when a device needs power to boot, but there is not enough power capacity to support the device.

Effect

A non-powered device will not boot until the power capacity is increased to support the device.

Recovery

Add a new power supply to the system or change the faulty power supply for a working one.

2.10.85. tmnxEqPowerCapacityExceededClear

tmnxEqPowerCapacityExceededClear:CHASSIS
Table 229:  tmnxEqPowerCapacityExceededClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2093

Event name

tmnxEqPowerCapacityExceededClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.81

Default severity

minor

Message format string

The system power capacity is sufficient to support installed devices

Cause

The tmnxEqPowerCapacityExceededClear notification is generated when the available power capacity exceeds the required power to boot all inserted devices.

Effect

Devices that failed to boot due to power constrains, power up.

Recovery

N/A

2.10.86. tmnxEqPowerLostCapacity

tmnxEqPowerLostCapacity:CHASSIS
Table 230:  tmnxEqPowerLostCapacity properties 

Property name

Value

Application name

CHASSIS

Event ID

2094

Event name

tmnxEqPowerLostCapacity

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.82

Default severity

major

Message format string

The system can no longer support configured devices. Power capacity dropped to $tmnxChassisNotifyPowerCapacity$ watts

Cause

The tmnxEqPowerLostCapacity alarm is generated when a power supply fails or is removed which puts the system in an overloaded situation.

Effect

Devices are powered off in order of lowest power priority (tmnxMDAHwPowerPriority) until the available power capacity can support the powered devices.

Recovery

Add a new power supply to the system or change the faulty power supply for a working one.

2.10.87. tmnxEqPowerLostCapacityClear

tmnxEqPowerLostCapacityClear:CHASSIS
Table 231:  tmnxEqPowerLostCapacityClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2095

Event name

tmnxEqPowerLostCapacityClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.83

Default severity

major

Message format string

The system has reached a sustainable power capacity.

Cause

The tmnxEqPowerLostCapacityClear notification is generated when the available power capacity exceeds the required power to boot all inserted devices.

Effect

Devices that powered off due to power constrains, power up.

Recovery

N/A

2.10.88. tmnxEqPowerOverloadState

tmnxEqPowerOverloadState:CHASSIS
Table 232:  tmnxEqPowerOverloadState properties 

Property name

Value

Application name

CHASSIS

Event ID

2096

Event name

tmnxEqPowerOverloadState

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.84

Default severity

critical

Message format string

The system has reached critical power capacity. Increase available power now.

Cause

The tmnxEqPowerOverloadState alarm is generated when the overloaded power capacity can not support the power requirements and there are no further devices that can be powered off.

Effect

The system runs a risk of experiencing brownouts while the available power capacity does not meet the required power consumption.

Recovery

Add power capacity or manually shut down devices until the power capacity meets the power needs.

2.10.89. tmnxEqPowerOverloadStateClear

tmnxEqPowerOverloadStateClear:CHASSIS
Table 233:  tmnxEqPowerOverloadStateClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2097

Event name

tmnxEqPowerOverloadStateClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.85

Default severity

critical

Message format string

The system has reached a sustainable power capacity for critical equipment.

Cause

The tmnxEqPowerOverloadStateClear notification is generated when the available power capacity meets or exceeds the power needs of the powered on devices.

Effect

N/A

Recovery

N/A

2.10.90. tmnxEqPowerSafetyAlertClear

tmnxEqPowerSafetyAlertClear:CHASSIS
Table 234:  tmnxEqPowerSafetyAlertClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2107

Event name

tmnxEqPowerSafetyAlertClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.94

Default severity

minor

Message format string

The system power capacity safety alert for zone $tmnxChassisPwrMgmtZone$ has been disabled.

The system power capacity for zone $tmnxChassisPwrMgmtZone$ meets or exceeds the configured safety alert threshold of $tmnxChassisPwrMgmtSafetyAlert$ watts.

Cause

The tmnxEqPowerSafetyAlertClear notification is generated when the system power capacity raises above the configured safety alert threshold.

Effect

This event is for notification only.

Recovery

N/A

2.10.91. tmnxEqPowerSafetyAlertThreshold

tmnxEqPowerSafetyAlertThreshold:CHASSIS
Table 235:  tmnxEqPowerSafetyAlertThreshold properties 

Property name

Value

Application name

CHASSIS

Event ID

2106

Event name

tmnxEqPowerSafetyAlertThreshold

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.93

Default severity

minor

Message format string

The system power capacity for zone $tmnxChassisPwrMgmtZone$ dropped below the configured safety alert threshold of $tmnxChassisPwrMgmtSafetyAlert$ watts.

Cause

The tmnxEqPowerSafetyAlertThreshold notification is generated when the system power capacity drops below the configured safety alert threshold.

Effect

This event is for notification only.

Recovery

N/A

2.10.92. tmnxEqPowerSafetyLevelClear

tmnxEqPowerSafetyLevelClear:CHASSIS
Table 236:  tmnxEqPowerSafetyLevelClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2109

Event name

tmnxEqPowerSafetyLevelClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.96

Default severity

minor

Message format string

The peak nodal power for zone $tmnxChassisPwrMgmtZone$ consumption dropped below the configured safety level threshold of $tmnxChassisPwrMgmtSafetyLevel$ percent

Cause

The tmnxEqPowerSafetyLevelClear notification is generated when the peak nodal power consumption drops below the configured safety level threshold.

Effect

This event is for notification only.

Recovery

N/A

2.10.93. tmnxEqPowerSafetyLevelThreshold

tmnxEqPowerSafetyLevelThreshold:CHASSIS
Table 237:  tmnxEqPowerSafetyLevelThreshold properties 

Property name

Value

Application name

CHASSIS

Event ID

2108

Event name

tmnxEqPowerSafetyLevelThreshold

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.95

Default severity

minor

Message format string

The peak nodal power for zone $tmnxChassisPwrMgmtZone$ consumption exceeded the configured safety level threshold of $tmnxChassisPwrMgmtSafetyLevel$ percent

Cause

The tmnxEqPowerSafetyLevelThreshold notification is generated when the peak nodal power consumption exceeds the configured safety level threshold.

Effect

This event is for notification only.

Recovery

N/A

2.10.94. tmnxEqPowerSupplyInserted

tmnxEqPowerSupplyInserted:CHASSIS
Table 238:  tmnxEqPowerSupplyInserted properties 

Property name

Value

Application name

CHASSIS

Event ID

2010

Event name

tmnxEqPowerSupplyInserted

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.4

Default severity

major

Message format string

$tmnxChassisNotifyHwIndex$ inserted

Cause

Generated when one of the chassis' power supplies is inserted.

Effect

N/A

Recovery

N/A

2.10.95. tmnxEqPowerSupplyRemoved

tmnxEqPowerSupplyRemoved:CHASSIS
Table 239:  tmnxEqPowerSupplyRemoved properties 

Property name

Value

Application name

CHASSIS

Event ID

2011

Event name

tmnxEqPowerSupplyRemoved

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.5

Default severity

major

Message format string

$tmnxChassisNotifyHwIndex$, power lost

Cause

The tmnxEqPowerSupplyRemoved notification is generated when one of the power supplies is removed from the chassis or low input voltage is detected. The operating voltage range for the 7750 SR-7 and 7750 SR-12 is -40 to -72 VDC. The notification is generated if the system detects that the voltage of the power supply has dropped to -42.5 VDC.

Effect

Reduced power can cause intermittent errors and could also cause permanent damage to components.

Recovery

Re-insert the power supply or raise the input voltage above -42.5 VDC.

2.10.96. tmnxEqProvPowerCapacityAlm

tmnxEqProvPowerCapacityAlm:CHASSIS
Table 240:  tmnxEqProvPowerCapacityAlm properties 

Property name

Value

Application name

CHASSIS

Event ID

2115

Event name

tmnxEqProvPowerCapacityAlm

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.102

Default severity

minor

Message format string

The provisioned power capacity can no longer support configured devices.

Cause

The tmnxEqProvPowerCapacityAlm notification is generated if a power zone's provisioned power capacity can no longer support configured devices.

Effect

There is an increased risk of device power outages that may be service affecting.

Recovery

Increase the provisioned power capacity.

2.10.97. tmnxEqProvPowerCapacityAlmClr

tmnxEqProvPowerCapacityAlmClr:CHASSIS
Table 241:  tmnxEqProvPowerCapacityAlmClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2116

Event name

tmnxEqProvPowerCapacityAlmClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.103

Default severity

minor

Message format string

The provisioned power capacity now supports configured devices.

Cause

The tmnxEqProvPowerCapacityAlmClr notification is generated when the power zone's provisioned power capacity can support configured devices.

Effect

All configured devices in the power zone have enough provisioned power capacity.

Recovery

N/A

2.10.98. tmnxEqSyncIfTimingBITS2Alarm

tmnxEqSyncIfTimingBITS2Alarm:CHASSIS
Table 242:  tmnxEqSyncIfTimingBITS2Alarm properties 

Property name

Value

Application name

CHASSIS

Event ID

2073

Event name

tmnxEqSyncIfTimingBITS2Alarm

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.61

Default severity

minor

Message format string

Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on BITS 2 reference

Cause

Generated when an alarm condition on the BITS 2 timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

N/A

Recovery

N/A

2.10.99. tmnxEqSyncIfTimingBITS2AlarmClr

tmnxEqSyncIfTimingBITS2AlarmClr:CHASSIS
Table 243:  tmnxEqSyncIfTimingBITS2AlarmClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2074

Event name

tmnxEqSyncIfTimingBITS2AlarmClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.62

Default severity

minor

Message format string

Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on BITS 2 reference cleared

Cause

Generated when an alarm condition on the BITS 2 timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

N/A

Recovery

N/A

2.10.100. tmnxEqSyncIfTimingBITS2Quality

tmnxEqSyncIfTimingBITS2Quality:CHASSIS
Table 244:  tmnxEqSyncIfTimingBITS2Quality properties 

Property name

Value

Application name

CHASSIS

Event ID

2071

Event name

tmnxEqSyncIfTimingBITS2Quality

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.59

Default severity

minor

Message format string

Synchronous Timing interface, reference BITS2 received quality level $tmnxSyncIfTimingBITS2RxQltyLevel$

Cause

Generated when there is a change of the received quality level on the second bits interface.

Effect

N/A

Recovery

N/A

2.10.101. tmnxEqSyncIfTimingBITSAlarm

tmnxEqSyncIfTimingBITSAlarm:CHASSIS
Table 245:  tmnxEqSyncIfTimingBITSAlarm properties 

Property name

Value

Application name

CHASSIS

Event ID

2030

Event name

tmnxEqSyncIfTimingBITSAlarm

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.38

Default severity

minor

Message format string

Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on BITS$bits-two-supported$ reference

Cause

Generated when an alarm condition on the BITS timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

N/A

Recovery

N/A

2.10.102. tmnxEqSyncIfTimingBITSAlarmClear

tmnxEqSyncIfTimingBITSAlarmClear:CHASSIS
Table 246:  tmnxEqSyncIfTimingBITSAlarmClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2031

Event name

tmnxEqSyncIfTimingBITSAlarmClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.39

Default severity

minor

Message format string

Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on BITS$bits-two-supported$ reference cleared

Cause

Generated when an alarm condition on the BITS timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

N/A

Recovery

N/A

2.10.103. tmnxEqSyncIfTimingBITSOutRefChg

tmnxEqSyncIfTimingBITSOutRefChg:CHASSIS
Table 247:  tmnxEqSyncIfTimingBITSOutRefChg properties 

Property name

Value

Application name

CHASSIS

Event ID

2075

Event name

tmnxEqSyncIfTimingBITSOutRefChg

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.63

Default severity

minor

Message format string

Synchronous Timing interface, BITS output timing reference changed to $tmnxSyncIfTimingBITSOutRefSel$

Cause

Generated when the BITS Out timing reference selection changes.

Effect

N/A

Recovery

N/A

2.10.104. tmnxEqSyncIfTimingBITSQuality

tmnxEqSyncIfTimingBITSQuality:CHASSIS
Table 248:  tmnxEqSyncIfTimingBITSQuality properties 

Property name

Value

Application name

CHASSIS

Event ID

2070

Event name

tmnxEqSyncIfTimingBITSQuality

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.58

Default severity

minor

Message format string

Synchronous Timing interface, reference BITS$bits-two-supported$ received quality level $tmnxSyncIfTimingBITSRxQltyLevel$

Cause

Generated when there is a change of the received quality level on the bits interface.

Effect

N/A

Recovery

N/A

2.10.105. tmnxEqSyncIfTimingHoldover

tmnxEqSyncIfTimingHoldover:CHASSIS
Table 249:  tmnxEqSyncIfTimingHoldover properties 

Property name

Value

Application name

CHASSIS

Event ID

2017

Event name

tmnxEqSyncIfTimingHoldover

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.26

Default severity

critical

Message format string

Synchronous Timing interface in holdover state

Cause

Generated when the synchronous equipment timing subsystem transitions into a holdover state. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

Any node-timed ports will have very slow frequency drift limited by the central clock oscillator stability. The oscillator meets the holdover requirements of a Stratum 3 and G.813 Option 1 clock.

Recovery

Address issues with the central clock input references.

2.10.106. tmnxEqSyncIfTimingHoldoverClear

tmnxEqSyncIfTimingHoldoverClear:CHASSIS
Table 250:  tmnxEqSyncIfTimingHoldoverClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2018

Event name

tmnxEqSyncIfTimingHoldoverClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.27

Default severity

critical

Message format string

Synchronous Timing interface holdover state cleared

Cause

Generated when the synchronous equipment timing subsystem transitions out of the holdover state. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

N/A

Recovery

N/A

2.10.107. tmnxEqSyncIfTimingPTPAlarm

tmnxEqSyncIfTimingPTPAlarm:CHASSIS
Table 251:  tmnxEqSyncIfTimingPTPAlarm properties 

Property name

Value

Application name

CHASSIS

Event ID

2080

Event name

tmnxEqSyncIfTimingPTPAlarm

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.68

Default severity

minor

Message format string

Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on PTP reference

Cause

Generated when an alarm condition on the Precision Timing Protocol (PTP) timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

N/A

Recovery

N/A

2.10.108. tmnxEqSyncIfTimingPTPAlarmClr

tmnxEqSyncIfTimingPTPAlarmClr:CHASSIS
Table 252:  tmnxEqSyncIfTimingPTPAlarmClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2081

Event name

tmnxEqSyncIfTimingPTPAlarmClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.69

Default severity

minor

Message format string

Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on PTP reference cleared

Cause

Generated when an alarm condition on the Precision Timing Protocol (PTP) timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

N/A

Recovery

N/A

2.10.109. tmnxEqSyncIfTimingPTPQuality

tmnxEqSyncIfTimingPTPQuality:CHASSIS
Table 253:  tmnxEqSyncIfTimingPTPQuality properties 

Property name

Value

Application name

CHASSIS

Event ID

2079

Event name

tmnxEqSyncIfTimingPTPQuality

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.67

Default severity

minor

Message format string

Synchronous Timing interface, reference PTP received quality level $tmnxSyncIfTimingPTPRxQltyLevel$

Cause

Generated when there is a change of the received quality level on the Precision Timing Protocol (PTP).

Effect

N/A

Recovery

N/A

2.10.110. tmnxEqSyncIfTimingRef1Alarm

tmnxEqSyncIfTimingRef1Alarm:CHASSIS
Table 254:  tmnxEqSyncIfTimingRef1Alarm properties 

Property name

Value

Application name

CHASSIS

Event ID

2019

Event name

tmnxEqSyncIfTimingRef1Alarm

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.28

Default severity

minor

Message format string

Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on reference 1

Cause

Generated when an alarm condition on the first timing reference is detected. The type of alarm (los, oof, etc) is indicated in the details of the log event or alarm, and is also available in the tmnxSyncIfTimingNotifyAlarm attribute included in the SNMP notification. The SNMP notification will have the same indices as those of the tmnxCpmCardTable.

Effect

Indicated timing reference (1, 2, or BITS) cannot be used as a source of timing into the central clock.

Recovery

Address issues with the signal associated with indicated timing reference (1, 2, or BITS).

2.10.111. tmnxEqSyncIfTimingRef1AlarmClear

tmnxEqSyncIfTimingRef1AlarmClear:CHASSIS
Table 255:  tmnxEqSyncIfTimingRef1AlarmClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2020

Event name

tmnxEqSyncIfTimingRef1AlarmClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.29

Default severity

minor

Message format string

Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on reference 1 cleared

Cause

Generated when an alarm condition on the first timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

N/A

Recovery

N/A

2.10.112. tmnxEqSyncIfTimingRef1Quality

tmnxEqSyncIfTimingRef1Quality:CHASSIS
Table 256:  tmnxEqSyncIfTimingRef1Quality properties 

Property name

Value

Application name

CHASSIS

Event ID

2068

Event name

tmnxEqSyncIfTimingRef1Quality

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.56

Default severity

minor

Message format string

Synchronous Timing interface, reference 1 received quality level $tmnxSyncIfTimingRef1RxQltyLevel$

Cause

Generated when there is a change of the received quality level on timing reference 1.

Effect

N/A

Recovery

N/A

2.10.113. tmnxEqSyncIfTimingRef2Alarm

tmnxEqSyncIfTimingRef2Alarm:CHASSIS
Table 257:  tmnxEqSyncIfTimingRef2Alarm properties 

Property name

Value

Application name

CHASSIS

Event ID

2021

Event name

tmnxEqSyncIfTimingRef2Alarm

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.30

Default severity

minor

Message format string

Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on reference 2

Cause

Generated when an alarm condition on the second timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

N/A

Recovery

N/A

2.10.114. tmnxEqSyncIfTimingRef2AlarmClear

tmnxEqSyncIfTimingRef2AlarmClear:CHASSIS
Table 258:  tmnxEqSyncIfTimingRef2AlarmClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2022

Event name

tmnxEqSyncIfTimingRef2AlarmClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.31

Default severity

minor

Message format string

Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on reference 2 cleared

Cause

Generated when an alarm condition on the second timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable.

Effect

N/A

Recovery

N/A

2.10.115. tmnxEqSyncIfTimingRef2Quality

tmnxEqSyncIfTimingRef2Quality:CHASSIS
Table 259:  tmnxEqSyncIfTimingRef2Quality properties 

Property name

Value

Application name

CHASSIS

Event ID

2069

Event name

tmnxEqSyncIfTimingRef2Quality

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.57

Default severity

minor

Message format string

Synchronous Timing interface, reference 2 received quality level $tmnxSyncIfTimingRef2RxQltyLevel$

Cause

Generated when there is a change of the received quality level on timing reference 2.

Effect

N/A

Recovery

N/A

2.10.116. tmnxEqSyncIfTimingRefSwitch

tmnxEqSyncIfTimingRefSwitch:CHASSIS
Table 260:  tmnxEqSyncIfTimingRefSwitch properties 

Property name

Value

Application name

CHASSIS

Event ID

2072

Event name

tmnxEqSyncIfTimingRefSwitch

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.60

Default severity

minor

Message format string

Synchronous Timing interface, timing reference changed to $tmnxSyncIfTimingRef1InUse$

Cause

Generated when there is a change of which timing reference is providing timing for the system.

Effect

N/A

Recovery

N/A

2.10.117. tmnxEqSyncIfTimingSystemQuality

tmnxEqSyncIfTimingSystemQuality:CHASSIS
Table 261:  tmnxEqSyncIfTimingSystemQuality properties 

Property name

Value

Application name

CHASSIS

Event ID

2077

Event name

tmnxEqSyncIfTimingSystemQuality

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.65

Default severity

minor

Message format string

Synchronous Timing interface, System Quality Level changed to $tmnxSyncIfTimingSystemQltyLevel$

Cause

This notification may be triggered for the following reasons: 1) There has been a switch in the timing reference in use by the network element, either because the previously active timing reference was disqualified, or to ensure that the network element is using the timing reference with the best timing quality. 2) There has been a change in the active timing reference's quality and the change does not result in a timing reference switch. 3) The network element has transitioned into or out of the holdover state.

Effect

The system quality level is used to determine the SSM code transmitted on synchronous interfaces. This may affect the SSM code transmitted on some or all interfaces, which may affect the distribution of timing throughout the network.

Recovery

If the customer is expecting the system to be locked to a reference of a particular quality and the system quality has decreased, the customer will need to determine the root cause (for example, loss of communication with a satellite) and resolve the issue.

2.10.118. tmnxEqWrongCard

tmnxEqWrongCard:CHASSIS
Table 262:  tmnxEqWrongCard properties 

Property name

Value

Application name

CHASSIS

Event ID

2004

Event name

tmnxEqWrongCard

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.10

Default severity

minor

Message format string

Class $tmnxHwClass$ : wrong type inserted

Cause

Generated when the wrong type of card is inserted into a slot of the chassis. Even though a card may be physically supported by the slot, it may have been administratively configured to allow only certain card types in a particular slot location. The card type may be IOM (or XCM), Fabric, MDA (or XMA), MCM, CPM module, etc.

Effect

The effect is dependent on the card that has been incorrectly inserted. Incorrect IOM (or XCM) or MDA (or XMA) insertion will cause a loss of service for all services running on that card.

Recovery

Insert the correct card into the correct slot, and ensure the slot is configured for the correct type of card.

2.10.119. tmnxExtStandbyCpmReboot

tmnxExtStandbyCpmReboot:CHASSIS
Table 263:  tmnxExtStandbyCpmReboot properties 

Property name

Value

Application name

CHASSIS

Event ID

2127

Event name

tmnxExtStandbyCpmReboot

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.114

Default severity

warning

Message format string

Rebooting extension standby CPM due to master standby CPM reboot and transition into or out of an ISSU state.

Cause

The tmnxExtStandbyCpmReboot notification is generated after a master standby CPM reboots and it is determined that the master standby CPM has transitioned into or out of an ISSU state. This detected transition will cause a reboot of the extension standby CPM (this reboot is necessary and expected for ISSU operation). This notification helps an operator understand why an extension standby CPM may have rebooted.

Effect

The extension standby CPM will reboot.

Recovery

There is no recovery for this notification.

2.10.120. tmnxExtStandbyCpmRebootFail

tmnxExtStandbyCpmRebootFail:CHASSIS
Table 264:  tmnxExtStandbyCpmRebootFail properties 

Property name

Value

Application name

CHASSIS

Event ID

2128

Event name

tmnxExtStandbyCpmRebootFail

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.115

Default severity

minor

Message format string

Unable to automatically reboot extension standby CPM during ISSU.

Cause

The tmnxExtStandbyCpmRebootFail notification is generated after a master standby CPM reboots and it is determined that the master standby CPM has transitioned into or out of an ISSU state. The system will attempt to reboot the extension standby CPM as part of the normal ISSU process. If the system determines that it cannot reboot the extension standby CPM (i.e. it is not reachable) then this log event is raised.

Effect

The extension standby CPM may not transition to the ISSU state in which case the ISSU cannot proceed normally.

Recovery

Resetting the extension standby CPM can be attempted to try and get the CPM into an ISSU state. If that is not successful, then the ISSU should be aborted.

2.10.121. tmnxGnssAcquiredFix

tmnxGnssAcquiredFix:CHASSIS
Table 265:  tmnxGnssAcquiredFix properties 

Property name

Value

Application name

CHASSIS

Event ID

2189

Event name

tmnxGnssAcquiredFix

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.180

Default severity

minor

Message format string

GNSS Receiver - position fix obtained

Cause

The tmnxGnssAcquiredFix notification is generated when the GNSS receiver has acquired a valid fix on its position.

Effect

The position of the system is known.

Recovery

None needed

2.10.122. tmnxGnssAcquiringFix

tmnxGnssAcquiringFix:CHASSIS
Table 266:  tmnxGnssAcquiringFix properties 

Property name

Value

Application name

CHASSIS

Event ID

2188

Event name

tmnxGnssAcquiringFix

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.179

Default severity

minor

Message format string

GNSS Receiver - attempting to acquire a position fix

Cause

The tmnxGnssAcquiringFix notification is generated when the GNSS receiver starts to acquire a fix. This occurs when the GNSS receiver is enabled, and also when the GNSS receiver loses its fix.

Effect

The position of the system is unknown until the receiver acquires a fix.

Recovery

Ensure that the GNSS antenna is properly connected to the system.

2.10.123. tmnxInterChassisCommsDown

tmnxInterChassisCommsDown:CHASSIS
Table 267:  tmnxInterChassisCommsDown properties 

Property name

Value

Application name

CHASSIS

Event ID

4001

Event name

tmnxInterChassisCommsDown

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxInterChassisNotifications.1

Default severity

critical

Message format string

Control communications disrupted between the active CPM and the chassis

Cause

The tmnxInterChassisCommsDown alarm is generated when the active CPM cannot reach the far-end chassis.

Effect

The resources on the far-end chassis are not available. This event for the far-end chassis means that the CPM, SFM, and XCM cards in the far-end chassis will reboot and remain operationally down until communications are re-established.

Recovery

Ensure that all CPM interconnect ports in the system are properly cabled together with working cables.

2.10.124. tmnxInterChassisCommsUp

tmnxInterChassisCommsUp:CHASSIS
Table 268:  tmnxInterChassisCommsUp properties 

Property name

Value

Application name

CHASSIS

Event ID

4002

Event name

tmnxInterChassisCommsUp

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxInterChassisNotifications.2

Default severity

critical

Message format string

Control communications established between the active CPM and the chassis

Cause

The tmnxInterChassisCommsUp notification is generated when the control communications are re-established between the active CPM and the far-end chassis.

Effect

The resources on the far-end chassis are now available. This event for the far-end chassis means that the CPM, SFM and XCM cards in the far-end chassis will start the process of coming back into service.

Recovery

N/A

2.10.125. tmnxIomEventOverflow

tmnxIomEventOverflow:CHASSIS
Table 269:  tmnxIomEventOverflow properties 

Property name

Value

Application name

CHASSIS

Event ID

2124

Event name

tmnxIomEventOverflow

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.111

Default severity

minor

Message format string

Iom $tmnxIomResourceType$ Resource event overflow occurred on card $tmnxChassisNotifyCardSlotNum$ at $tmnxIomResLimitTimeEventOccured$.

Cause

The tmnxIomEventOverflow notification is generated when tmnxIomResStateClr, tmnxIomResExhausted and tmnxIomResHighLimitReached occur more than 200 times because of resource usage fluctuation. The Iom Raises the final trap to indicate overflow and stops logging traps.

Effect

Some FP notifications configured on the card may not be received.

Recovery

Notifications will resume once the Overflow clear is set.

2.10.126. tmnxIomEventOverflowClr

tmnxIomEventOverflowClr:CHASSIS
Table 270:  tmnxIomEventOverflowClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2125

Event name

tmnxIomEventOverflowClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.112

Default severity

minor

Message format string

$tmnxIomResLimMissingNotifCount$ Iom $tmnxIomResourceType$ Resources events were dropped in the last event throttling interval on card $tmnxChassisNotifyCardSlotNum$ at $tmnxIomResLimitTimeEventOccured$.

Cause

The tmnxIomEventOverflowClr notification is generated when the CPM polls the IOM for traps and the overflow is cleared by logging an overflow-clear on a particular card.

Effect

Notifications are received again since the event throttling has ended.

Recovery

There is no recovery for this notification.

2.10.127. tmnxIomResExhausted

tmnxIomResExhausted:CHASSIS
Table 271:  tmnxIomResExhausted properties 

Property name

Value

Application name

CHASSIS

Event ID

2122

Event name

tmnxIomResExhausted

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.109

Default severity

critical

Message format string

The $tmnxIomResourceType$ resources on IOM $tmnxChassisNotifyCardSlotNum$ and Forwarding Plane $tmnxChassisNotifyFpNum$ has been exhausted at $tmnxIomResLimitTimeEventOccured$.

Cause

The tmnxIomResExhausted notification is generated when the type of resources on IOM as specified by tmnxIomResourceType has reached the 100% of its utilization threshold.

Effect

The specified resource has reached the stats pool limit.

Recovery

Intervention may be required to recover resources.

2.10.128. tmnxIomResHighLimitReached

tmnxIomResHighLimitReached:CHASSIS
Table 272:  tmnxIomResHighLimitReached properties 

Property name

Value

Application name

CHASSIS

Event ID

2121

Event name

tmnxIomResHighLimitReached

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.108

Default severity

major

Message format string

The $tmnxIomResourceType$ resources on IOM $tmnxChassisNotifyCardSlotNum$ and Forwarding Plane $tmnxChassisNotifyFpNum$ has reached the $tmnxIomResourceLimitPct$% utilization threshold at $tmnxIomResLimitTimeEventOccured$.

Cause

The tmnxIomResHighLimitReached notification is generated when the resource (of type tmnxIomResourceType) utilization on IOM has reached the value of tmnxIomResourceLimitPct.

Effect

The specified resource limit is cleared when the number of in-use stats resources falls below the clear threshold of the stats pool limit.

Recovery

There is no recovery required for this notification.

2.10.129. tmnxIomResStateClr

tmnxIomResStateClr:CHASSIS
Table 273:  tmnxIomResStateClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2123

Event name

tmnxIomResStateClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.110

Default severity

minor

Message format string

The $tmnxIomResourceType$ resources on IOM $tmnxChassisNotifyCardSlotNum$ and Forwarding Plane $tmnxChassisNotifyFpNum$ has dropped below the $tmnxIomResourceLimitPct$% utilization threshold at $tmnxIomResLimitTimeEventOccured$.

Cause

The tmnxIomResStateClr notification is generated when the type of resources on IOM as specified by tmnxIomResourceType has dropped back down below the value of tmnxIomResourceLimitPct.

Effect

The specified resource limit is cleared when the number of in-use stats resources falls below tmnxIomResourceLimitPct of the stats pool limit.

Recovery

There is no recovery required for this notification.

2.10.130. tmnxIPMacCpmFilterNearFull

tmnxIPMacCpmFilterNearFull:CHASSIS
Table 274:  tmnxIPMacCpmFilterNearFull properties 

Property name

Value

Application name

CHASSIS

Event ID

2283

Event name

tmnxIPMacCpmFilterNearFull

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.205

Default severity

minor

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has IPv4 or MAC CPM Filter at near full utilization.

Cause

The tmnxIPMacCpmFilterNearFull notification is generated when an IPv4 or MAC CPM Filter policy is near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.131. tmnxIPMacCpmFilterNearFullClear

tmnxIPMacCpmFilterNearFullClear:CHASSIS
Table 275:  tmnxIPMacCpmFilterNearFullClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2284

Event name

tmnxIPMacCpmFilterNearFullClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.206

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has IPv4 or MAC CPM Filter at near full utilization.

Cause

The tmnxIPMacCpmFilterNearFullClear notification is generated when IPv4 or MAC CPM Filter policy is no longer near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.132. tmnxIPMacCpmFilterOverload

tmnxIPMacCpmFilterOverload:CHASSIS
Table 276:  tmnxIPMacCpmFilterOverload properties 

Property name

Value

Application name

CHASSIS

Event ID

2183

Event name

tmnxIPMacCpmFilterOverload

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.172

Default severity

critical

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has an IPv4 or MAC CPM Filter in overload.

Cause

The tmnxIPMacCpmFilterOverload notification is generated when an IPv4 or MAC CPM Filter policy is in overload on an FP.

Effect

The impacted IPv4 or MAC CPM Filter policy on the affected FP will not work as expected, because not all entries are programmed.

Recovery

Identify the impacted IPv4 or MAC CPM Filter policy, policy entries, and FPs using the appropriate tools commands. Remove or modify policy entries or change the policy assigned to the impacted FPs until the overload condition is cleared.

2.10.133. tmnxIPMacCpmFilterOverloadClear

tmnxIPMacCpmFilterOverloadClear:CHASSIS
Table 277:  tmnxIPMacCpmFilterOverloadClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2184

Event name

tmnxIPMacCpmFilterOverloadClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.173

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has an IPv4 or MAC CPM Filter in overload.

Cause

The tmnxIPMacCpmFilterOverloadClear notification is generated when IPv4 or MAC CPM Filter policies are no longer in overload on an FP.

Effect

The IPv4 or MAC CPM Filter policies on the affected FP will work as expected, because all entries are programmed.

Recovery

No recovery required.

2.10.134. tmnxIPMacFilterEgrNearFull

tmnxIPMacFilterEgrNearFull:CHASSIS
Table 278:  tmnxIPMacFilterEgrNearFull properties 

Property name

Value

Application name

CHASSIS

Event ID

2277

Event name

tmnxIPMacFilterEgrNearFull

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.199

Default severity

minor

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has egress IPv4 or MAC ACL Filters at near full utilization.

Cause

The tmnxIPMacFilterEgrNearFull notification is generated when an egress IPv4 or MAC ACL Filter policies are near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.135. tmnxIPMacFilterEgrNearFullClear

tmnxIPMacFilterEgrNearFullClear:CHASSIS
Table 279:  tmnxIPMacFilterEgrNearFullClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2278

Event name

tmnxIPMacFilterEgrNearFullClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.200

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has egress IPv4 or MAC ACL Filters near full utilization.

Cause

The tmnxIPMacFilterEgrNearFullClear notification is generated when egress IPv4 or MAC ACL Filter policies are no longer near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.136. tmnxIPMacFilterEgrOverload

tmnxIPMacFilterEgrOverload:CHASSIS
Table 280:  tmnxIPMacFilterEgrOverload properties 

Property name

Value

Application name

CHASSIS

Event ID

2177

Event name

tmnxIPMacFilterEgrOverload

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.166

Default severity

critical

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has an egress IPv4 or MAC ACL Filter in overload.

Cause

The tmnxIPMacFilterEgrOverload notification is generated when an egress IPv4 or MAC ACL Filter policy is in overload on an FP.

Effect

The impacted egress IPv4 or MAC ACL Filter policy on the affected FP will not work as expected, because not all entries are programmed.

Recovery

Identify the impacted egress IPv4 or MAC ACL Filter policy, policy entries, and FPs using the appropriate tools commands. Remove or modify policy entries or change the policy assigned to the impacted FPs until the overload condition is cleared.

2.10.137. tmnxIPMacFilterEgrOverloadClear

tmnxIPMacFilterEgrOverloadClear:CHASSIS
Table 281:  tmnxIPMacFilterEgrOverloadClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2178

Event name

tmnxIPMacFilterEgrOverloadClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.167

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has an egress IPv4 or MAC ACL Filter in overload.

Cause

The tmnxIPMacFilterEgrOverloadClear notification is generated when egress IPv4 or MAC ACL Filter policies are no longer in overload on an FP.

Effect

The egress IPv4 or MAC ACL Filter policies on the affected FP will work as expected, because all entries are programmed.

Recovery

No recovery required.

2.10.138. tmnxIPMacFilterIngNearFull

tmnxIPMacFilterIngNearFull:CHASSIS
Table 282:  tmnxIPMacFilterIngNearFull properties 

Property name

Value

Application name

CHASSIS

Event ID

2275

Event name

tmnxIPMacFilterIngNearFull

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.197

Default severity

minor

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has ingress IPv4 or MAC ACL Filters at near full utilization.

Cause

The tmnxIPMacFilterIngNearFull notification is generated when an ingress IPv4 or MAC ACL Filter policies are near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.139. tmnxIPMacFilterIngNearFullClear

tmnxIPMacFilterIngNearFullClear:CHASSIS
Table 283:  tmnxIPMacFilterIngNearFullClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2276

Event name

tmnxIPMacFilterIngNearFullClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.198

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has ingress IPv4 or MAC ACL Filters at near full utilization.

Cause

The tmnxIPMacFilterIngNearFullClear notification is generated when ingress IPv4 or MAC ACL Filter policies are no longer near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.140. tmnxIPMacFilterIngOverload

tmnxIPMacFilterIngOverload:CHASSIS
Table 284:  tmnxIPMacFilterIngOverload properties 

Property name

Value

Application name

CHASSIS

Event ID

2175

Event name

tmnxIPMacFilterIngOverload

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.164

Default severity

critical

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has an ingress IPv4 or MAC ACL Filter in overload.

Cause

The tmnxIPMacFilterIngOverload notification is generated when an ingress IPv4 or MAC ACL Filter policy is in overload on an FP.

Effect

The impacted ingress IPv4 or MAC ACL Filter policy on the affected FP will not work as expected, because not all entries are programmed.

Recovery

Identify the impacted ingress IPv4 or MAC ACL Filter policy, policy entries, and FPs using the appropriate tools commands. Remove or modify policy entries or change the policy assigned to the impacted FPs until the overload condition is cleared.

2.10.141. tmnxIPMacFilterIngOverloadClear

tmnxIPMacFilterIngOverloadClear:CHASSIS
Table 285:  tmnxIPMacFilterIngOverloadClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2176

Event name

tmnxIPMacFilterIngOverloadClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.165

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has an ingress IPv4 or MAC ACL Filter in overload.

Cause

The tmnxIPMacFilterIngOverloadClear notification is generated when ingress IPv4 or MAC ACL Filter policies are no longer in overload on an FP.

Effect

The ingress IPv4 or MAC ACL Filter policies on the affected FP will work as expected, because all entries are programmed.

Recovery

No recovery required.

2.10.142. tmnxIPMacQosIngOverload

tmnxIPMacQosIngOverload:CHASSIS
Table 286:  tmnxIPMacQosIngOverload properties 

Property name

Value

Application name

CHASSIS

Event ID

2167

Event name

tmnxIPMacQosIngOverload

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.156

Default severity

major

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has an ingress QoS policy with IPv4 or MAC criteria entries in overload.

Cause

The tmnxIPMacQosIngOverload notification is generated when an ingress QoS policy is in overload on an FP due to its configured IPv4 or MAC criteria entries.

Effect

The impacted IPv4 or MAC criteria entires in the ingress QoS policy on the affected FP will not work as expected, because not all entries are programmed.

Recovery

Identify the impacted ingress QoS policy, policy entries, and FPs using the appropriate tools commands. Remove or modify the policy criteria entries or change the policy assigned to the impacted FPs until the overload condition is cleared.

2.10.143. tmnxIPMacQosIngOverloadClear

tmnxIPMacQosIngOverloadClear:CHASSIS
Table 287:  tmnxIPMacQosIngOverloadClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2168

Event name

tmnxIPMacQosIngOverloadClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.157

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has an ingress QoS policy with IPv4 or MAC criteria entries in overload.

Cause

The tmnxIPMacQosIngOverloadClear notification is generated when ingress QoS policies are no longer in overload on an FP.

Effect

The IPv4 or MAC criteria entries in the ingress QoS policies on the affected FP will work as expected, because all entries are programmed.

Recovery

No recovery required.

2.10.144. tmnxIPQosEgrOverload

tmnxIPQosEgrOverload:CHASSIS
Table 288:  tmnxIPQosEgrOverload properties 

Property name

Value

Application name

CHASSIS

Event ID

2169

Event name

tmnxIPQosEgrOverload

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.158

Default severity

major

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has an egress QoS policy with IPv4 criteria entries in overload.

Cause

The tmnxIPQosEgrOverload notification is generated when an egress QoS policy is in overload on an FP due to its configured IPv4 criteria entries.

Effect

The impacted IPv4 criteria entires in the egress QoS policy on the affected FP will not work as expected, because not all entries are programmed.

Recovery

Identify the impacted egress QoS policy, policy entries, and FPs using the appropriate tools commands. Remove or modify the policy criteria entries or change the policy assigned to the impacted FPs until the overload condition is cleared.

2.10.145. tmnxIPQosEgrOverloadClear

tmnxIPQosEgrOverloadClear:CHASSIS
Table 289:  tmnxIPQosEgrOverloadClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2170

Event name

tmnxIPQosEgrOverloadClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.159

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has an egress QoS policy with IPv4 criteria entries in overload.

Cause

The tmnxIPQosEgrOverloadClear notification is generated when egress QoS policies are no longer in overload on an FP.

Effect

The IPv4 criteria entries in the egress QoS policy on the affected FP will work as expected, because all entries are programmed.

Recovery

No recovery required.

2.10.146. tmnxIPsecIsaGrpActiveIsaChgd

tmnxIPsecIsaGrpActiveIsaChgd:CHASSIS
Table 290:  tmnxIPsecIsaGrpActiveIsaChgd properties 

Property name

Value

Application name

CHASSIS

Event ID

2062

Event name

tmnxIPsecIsaGrpActiveIsaChgd

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.50

Default severity

minor

Message format string

Active ISA changed to $tmnxIPsecIsaGrpActiveIsa$ for IPSec ISA group $tmnxIPsecIsaGrpId$ where primary ISA is $tmnxIPsecIsaGrpPrimaryIsa$ and Backup ISA is $tmnxIPsecIsaGrpBackupIsa$

Cause

The tmnxIPsecIsaGrpActiveIsaChgd notification is generated when a change in the active ISA (Integrated Service Adapter) occurs in an IPsec ISA module group.

Effect

N/A

Recovery

N/A

2.10.147. tmnxIPsecIsaGrpTnlHighWMark

tmnxIPsecIsaGrpTnlHighWMark:CHASSIS
Table 291:  tmnxIPsecIsaGrpTnlHighWMark properties 

Property name

Value

Application name

CHASSIS

Event ID

2066

Event name

tmnxIPsecIsaGrpTnlHighWMark

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.54

Default severity

minor

Message format string

Number of tunnels for an IPsec ISA module for the group $tmnxIPsecIsaGrpId$ has reached to the high watermark which is 95% of the maximum limit $tmnxIPsecIsaGrpMaxTunnels$.

Cause

The number of tunnels for an IPsec ISA (Integrated Service Adapter) module has reached to the high watermark which is 95% of the maximum limit.

Effect

N/A

Recovery

N/A

2.10.148. tmnxIPsecIsaGrpTnlLowWMark

tmnxIPsecIsaGrpTnlLowWMark:CHASSIS
Table 292:  tmnxIPsecIsaGrpTnlLowWMark properties 

Property name

Value

Application name

CHASSIS

Event ID

2065

Event name

tmnxIPsecIsaGrpTnlLowWMark

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.53

Default severity

minor

Message format string

Number of tunnels for an IPsec ISA module for the group $tmnxIPsecIsaGrpId$ has dropped to the low watermark which is 90% of the maximum limit $tmnxIPsecIsaGrpMaxTunnels$.

Cause

The number of tunnels for an IPsec ISA (Integrated Service Adapter) module has dropped to the low watermark which is 90% of the maximum limit.

Effect

N/A

Recovery

N/A

2.10.149. tmnxIPsecIsaGrpTnlMax

tmnxIPsecIsaGrpTnlMax:CHASSIS
Table 293:  tmnxIPsecIsaGrpTnlMax properties 

Property name

Value

Application name

CHASSIS

Event ID

2067

Event name

tmnxIPsecIsaGrpTnlMax

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.55

Default severity

minor

Message format string

Number of tunnels for an IPsec ISA module the for group $tmnxIPsecIsaGrpId$ has reached the maximum limit $tmnxIPsecIsaGrpMaxTunnels$.

Cause

The number of tunnels for an IPsec ISA (Integrated Service Adapter) module has reached the maximum limit.

Effect

N/A

Recovery

N/A

2.10.150. tmnxIPsecIsaGrpUnableToSwitch

tmnxIPsecIsaGrpUnableToSwitch:CHASSIS
Table 294:  tmnxIPsecIsaGrpUnableToSwitch properties 

Property name

Value

Application name

CHASSIS

Event ID

2064

Event name

tmnxIPsecIsaGrpUnableToSwitch

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.52

Default severity

minor

Message format string

IPsec ISA $tmnxIPsecIsaGrpActiveIsa$ for group $tmnxIPsecIsaGrpId$ is unable to switch due to lack of resources on the destination MDA

Cause

IPsec ISA group is unable to switch due to lack of resources on the destination MDA.

Effect

In such an event the IPsec ISA group is left without an active MDA and the tmnxIPsecIsaGrpOperState is set to 'outOfService'.

Recovery

Recovery is possible by releasing resources and performing a shutdown/no shutdown operation to bring up the ISA group.

2.10.151. tmnxIPv6CpmFilterNearFull

tmnxIPv6CpmFilterNearFull:CHASSIS
Table 295:  tmnxIPv6CpmFilterNearFull properties 

Property name

Value

Application name

CHASSIS

Event ID

2285

Event name

tmnxIPv6CpmFilterNearFull

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.207

Default severity

minor

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has IPv6 CPM Filter at near full utilization.

Cause

The tmnxIPv6CpmFilterNearFull notification is generated when an IPv6 CPM Filter policy is near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.152. tmnxIPv6CpmFilterNearFullClear

tmnxIPv6CpmFilterNearFullClear:CHASSIS
Table 296:  tmnxIPv6CpmFilterNearFullClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2286

Event name

tmnxIPv6CpmFilterNearFullClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.208

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has IPv6 CPM Filter at near full utilization.

Cause

The tmnxIPv6CpmFilterNearFullClear notification is generated when IPv6 CPM Filter policy is no longer near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.153. tmnxIPv6CpmFilterOverload

tmnxIPv6CpmFilterOverload:CHASSIS
Table 297:  tmnxIPv6CpmFilterOverload properties 

Property name

Value

Application name

CHASSIS

Event ID

2185

Event name

tmnxIPv6CpmFilterOverload

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.174

Default severity

critical

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has an IPv6 CPM Filter in overload.

Cause

The tmnxIPv6CpmFilterOverload notification is generated when an IPv6 CPM Filter policy is in overload on an FP.

Effect

The impacted IPv6 CPM Filter policy on the affected FP will not work as expected, because not all entries are programmed.

Recovery

Identify the impacted IPv6 CPM Filter policy, policy entries, and FPs using the appropriate tools commands. Remove or modify policy entries or change the policy assigned to the impacted FPs until the overload condition is cleared.

2.10.154. tmnxIPv6CpmFilterOverloadClear

tmnxIPv6CpmFilterOverloadClear:CHASSIS
Table 298:  tmnxIPv6CpmFilterOverloadClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2186

Event name

tmnxIPv6CpmFilterOverloadClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.175

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has an IPv6 CPM Filter in overload.

Cause

The tmnxIPv6CpmFilterOverloadClear notification is generated when IPv6 CPM Filter policies are no longer in overload on an FP.

Effect

The IPv6 CPM Filter policies on the affected FP will work as expected, because all entries are programmed.

Recovery

No recovery required.

2.10.155. tmnxIPv6FilterEgrNearFull

tmnxIPv6FilterEgrNearFull:CHASSIS
Table 299:  tmnxIPv6FilterEgrNearFull properties 

Property name

Value

Application name

CHASSIS

Event ID

2281

Event name

tmnxIPv6FilterEgrNearFull

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.203

Default severity

minor

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has egress IPv6 ACL Filters at near full utilization.

Cause

The tmnxIPv6FilterEgrNearFull notification is generated when an egress IPv6 ACL Filter policies are near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.156. tmnxIPv6FilterEgrNearFullClear

tmnxIPv6FilterEgrNearFullClear:CHASSIS
Table 300:  tmnxIPv6FilterEgrNearFullClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2282

Event name

tmnxIPv6FilterEgrNearFullClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.204

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has egress IPv6 ACL Filters at near full utilization.

Cause

The tmnxIPv6FilterEgrNearFullClear notification is generated when egress IPv6 ACL Filter policies are no longer near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.157. tmnxIPv6FilterEgrOverload

tmnxIPv6FilterEgrOverload:CHASSIS
Table 301:  tmnxIPv6FilterEgrOverload properties 

Property name

Value

Application name

CHASSIS

Event ID

2181

Event name

tmnxIPv6FilterEgrOverload

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.170

Default severity

critical

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has an egress IPv6 ACL Filter in overload.

Cause

The tmnxIPv6FilterEgrOverload notification is generated when an egress IPv6 ACL Filter policy is in overload on an FP.

Effect

The impacted egress IPv6 ACL Filter policy on the affected FP will not work as expected, because not all entries are programmed.

Recovery

Identify the impacted egress IPv6 ACL Filter policy, policy entries, and FPs using the appropriate tools commands. Remove or modify policy entries or changed the policy assigned to the impacted FPs until the overload condition is cleared.

2.10.158. tmnxIPv6FilterEgrOverloadClear

tmnxIPv6FilterEgrOverloadClear:CHASSIS
Table 302:  tmnxIPv6FilterEgrOverloadClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2182

Event name

tmnxIPv6FilterEgrOverloadClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.171

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has an egress IPv6 ACL Filter in overload.

Cause

The tmnxIPv6FilterEgrOverloadClear notification is generated when egress IPv6 ACL Filter policies are no longer in overload on an FP.

Effect

The egress IPv6 ACL Filter policies on the affected FP will work as expected, because all entries are programmed.

Recovery

No recovery required.

2.10.159. tmnxIPv6FilterIngNearFull

tmnxIPv6FilterIngNearFull:CHASSIS
Table 303:  tmnxIPv6FilterIngNearFull properties 

Property name

Value

Application name

CHASSIS

Event ID

2279

Event name

tmnxIPv6FilterIngNearFull

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.201

Default severity

minor

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has ingress IPv6 ACL Filters at near full utilization.

Cause

The tmnxIPv6FilterIngNearFull notification is generated when an ingress IPv6 ACL Filter policies are near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.160. tmnxIPv6FilterIngNearFullClear

tmnxIPv6FilterIngNearFullClear:CHASSIS
Table 304:  tmnxIPv6FilterIngNearFullClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2280

Event name

tmnxIPv6FilterIngNearFullClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.202

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has ingress IPv6 ACL Filters at near full utilization.

Cause

The tmnxIPv6FilterIngNearFullClear notification is generated when ingress IPv6 ACL Filter policies are no longer near full utilization on an FP.

Effect

There is no operational impact due to this event.

Recovery

None required.

2.10.161. tmnxIPv6FilterIngOverload

tmnxIPv6FilterIngOverload:CHASSIS
Table 305:  tmnxIPv6FilterIngOverload properties 

Property name

Value

Application name

CHASSIS

Event ID

2179

Event name

tmnxIPv6FilterIngOverload

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.168

Default severity

critical

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has an ingress IPv6 ACL Filter in overload.

Cause

The tmnxIPv6FilterIngOverload notification is generated when an ingress IPv6 ACL Filter policy is in overload on a FP.

Effect

The impacted ingress IPv6 ACL Filter policy on the affected FP will not work as expected, because not all entries are programmed.

Recovery

Identify the impacted ingress IPv6 ACL Filter policy, policy entries, and FPs using the appropriate tools commands. Remove or modify policy entries or change the policy assigned to the impacted FPs until the overload condition is cleared.

2.10.162. tmnxIPv6FilterIngOverloadClear

tmnxIPv6FilterIngOverloadClear:CHASSIS
Table 306:  tmnxIPv6FilterIngOverloadClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2180

Event name

tmnxIPv6FilterIngOverloadClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.169

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has an ingress IPv6 ACL Filter in overload.

Cause

The tmnxIPv6FilterIngOverloadClear notification is generated when ingress IPv6 ACL Filter policies are no longer in overload on an FP.

Effect

The ingress IPv6 ACL Filter policies on the affected FP will work as expected, because all entries are programmed.

Recovery

No recovery required.

2.10.163. tmnxIPv6QosEgrOverload

tmnxIPv6QosEgrOverload:CHASSIS
Table 307:  tmnxIPv6QosEgrOverload properties 

Property name

Value

Application name

CHASSIS

Event ID

2173

Event name

tmnxIPv6QosEgrOverload

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.162

Default severity

major

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has an egress QoS policy with IPv6 criteria entries in overload.

Cause

The tmnxIPv6QosEgrOverload notification is generated when an egress QoS policy is in overload on an FP due to its configured IPv6 criteria entries.

Effect

The impacted IPv6 criteria entires in the egress QoS Policy on the affected FP will not work as expected, because not all entries are programmed.

Recovery

Identify the impacted egress QoS policy, policy entries, and FPs using the appropriate tools commands. Remove or modify the policy criteria entries or change the policy assigned to the impacted FPs until the overload condition is cleared.

2.10.164. tmnxIPv6QosEgrOverloadClear

tmnxIPv6QosEgrOverloadClear:CHASSIS
Table 308:  tmnxIPv6QosEgrOverloadClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2174

Event name

tmnxIPv6QosEgrOverloadClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.163

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has an egress QoS policy with IPv6 criteria entries in overload.

Cause

The tmnxIPv6QosEgrOverloadClear notification is generated when egress QoS policies are no longer in overload on an FP.

Effect

The IPv6 criteria entries in the egress QoS policy on the affected FP will work as expected, because all entries are programmed.

Recovery

No recovery required.

2.10.165. tmnxIPv6QosIngOverload

tmnxIPv6QosIngOverload:CHASSIS
Table 309:  tmnxIPv6QosIngOverload properties 

Property name

Value

Application name

CHASSIS

Event ID

2171

Event name

tmnxIPv6QosIngOverload

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.160

Default severity

major

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ has an ingress QoS policy with IPv6 criteria entries in overload.

Cause

The tmnxIPv6QosIngOverload notification is generated when an ingress QoS policy is in overload on an FP due to its configured IPv6 criteria entries.

Effect

The impacted IPv6 criteria entires in the ingress QoS policy on the affected FP will not work as expected, because not all entries are programmed.

Recovery

Identify the impacted ingress QoS policy, policy entries, and FPs using the appropriate tools commands. Remove or modify the policy criteria entries or change the policy assigned to the impacted FPs until the overload condition is cleared.

2.10.166. tmnxIPv6QosIngOverloadClear

tmnxIPv6QosIngOverloadClear:CHASSIS
Table 310:  tmnxIPv6QosIngOverloadClear properties 

Property name

Value

Application name

CHASSIS

Event ID

2172

Event name

tmnxIPv6QosIngOverloadClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.161

Default severity

cleared

Message format string

Slot $tmnxChassisNotifyCardSlotNum$ FP $tmnxChassisNotifyFpNum$ no longer has an ingress QoS policy with IPv6 criteria entries in overload.

Cause

The tmnxIPv6QosIngOverloadClear notification is generated when ingress QoS policies are no longer in overload on an FP.

Effect

The IPv6 criteria entries in the ingress QoS policy on the affected FP will work as expected, because all entries are programmed.

Recovery

No recovery required.

2.10.167. tmnxMDAIsaTunnelGroupChange

tmnxMDAIsaTunnelGroupChange:CHASSIS
Table 311:  tmnxMDAIsaTunnelGroupChange properties 

Property name

Value

Application name

CHASSIS

Event ID

2083

Event name

tmnxMDAIsaTunnelGroupChange

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.71

Default severity

minor

Message format string

MDA $tmnxCardSlotNum$/$tmnxMDASlotNum$ is $tmnxMDAIsaTunnelGroupInUse$ active in the ISA tunnel-group $tmnxMDAIsaTunnelGroup$

Cause

The tmnxMDAIsaTunnelGroupChange notification is generated when IPsec ISA (Integrated Service Adapter) tunnel-group in-use for the MDA changes value.

Effect

There is no operational impact due to this event.

Recovery

N/A

2.10.168. tmnxPeBootloaderVersionMismatch

tmnxPeBootloaderVersionMismatch:CHASSIS
Table 312:  tmnxPeBootloaderVersionMismatch properties 

Property name

Value

Application name

CHASSIS

Event ID

2027

Event name

tmnxPeBootloaderVersionMismatch

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.35

Default severity

major

Message format string

Class $tmnxHwClass$ : Bootloader version mismatch - expected software version $tmnxHwSoftwareCodeVersion$, equipped version $tmnxChassisNotifyMismatchedVer$

Cause

Generated when there is a mismatch between the CPM and boot loader versions. tmnxChassisNotifyHwIndex identifies the CPM card. tmnxChassisNotifyMismatchedVer contains the mismatched version of bootloader and tmnxHwSoftwareCodeVersion contains the expected version of the bootloader.

Effect

N/A

Recovery

N/A

2.10.169. tmnxPeBootromVersionMismatch

tmnxPeBootromVersionMismatch:CHASSIS
Table 313:  tmnxPeBootromVersionMismatch properties 

Property name

Value

Application name

CHASSIS

Event ID

2028

Event name

tmnxPeBootromVersionMismatch

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.36

Default severity

major

Message format string

Class $tmnxHwClass$ : Bootrom version mismatch - expected version $tmnxHwSoftwareCodeVersion$, equipped version $tmnxChassisNotifyMismatchedVer$

Cause

Generated when there is a mismatch between the boot rom versions. tmnxChassisNotifyHwIndex identifies the IOM card. tmnxChassisNotifyMismatchedVer contains the mismatched version of bootrom and tmnxHwSoftwareCodeVersion contains the expected version of the bootrom.

Effect

N/A

Recovery

N/A

2.10.170. tmnxPeFirmwareVersionWarning

tmnxPeFirmwareVersionWarning:CHASSIS
Table 314:  tmnxPeFirmwareVersionWarning properties 

Property name

Value

Application name

CHASSIS

Event ID

2082

Event name

tmnxPeFirmwareVersionWarning

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.70

Default severity

major

Message format string

Class $tmnxHwClass$ : Firmware version $tmnxHwFirmwareCodeVersion$ is compatible but not the latest. Hard reset the MDA/IMM to upgrade to the most recent firmware if desired.

Cause

Generated when a card is running compatible yet older firmware than the firmware associated with the current software release. tmnxChassisNotifyHwIndex identifies the card. The tmnxHwFirmwareCodeVersion object will contain the programmed the firmware version.

Effect

N/A

Recovery

N/A

2.10.171. tmnxPeFPGAVersionMismatch

tmnxPeFPGAVersionMismatch:CHASSIS
Table 315:  tmnxPeFPGAVersionMismatch properties 

Property name

Value

Application name

CHASSIS

Event ID

2029

Event name

tmnxPeFPGAVersionMismatch

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.37

Default severity

major

Message format string

Class $tmnxHwClass$ : FPGA version mismatch - expected version $tmnxHwSoftwareCodeVersion$, equipped version $tmnxChassisNotifyMismatchedVer$

Cause

Generated when there is a mismatch between the FPGA versions. tmnxChassisNotifyHwIndex identifies the IOM card. tmnxChassisNotifyMismatchedVer contains the mismatched version of FPGA and tmnxHwSoftwareCodeVersion contains the expected version of the FPGA.

Effect

N/A

Recovery

N/A

2.10.172. tmnxPeSoftwareLoadFailed

tmnxPeSoftwareLoadFailed:CHASSIS
Table 316:  tmnxPeSoftwareLoadFailed properties 

Property name

Value

Application name

CHASSIS

Event ID

2026

Event name

tmnxPeSoftwareLoadFailed

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.34

Default severity

major

Message format string

Class $tmnxHwClass$ : Failed to load software from $tmnxChassisNotifySoftwareLocation$

Cause

Generated when the CPM fails to load the software from a specified location. tmnxChassisNotifyHwIndex identifies the card for which the software load failed and tmnxChassisNotifySoftwareLocation contains the location from where the software load was attempted.

Effect

N/A

Recovery

N/A

2.10.173. tmnxPeSoftwareVersionMismatch

tmnxPeSoftwareVersionMismatch:CHASSIS
Table 317:  tmnxPeSoftwareVersionMismatch properties 

Property name

Value

Application name

CHASSIS

Event ID

2025

Event name

tmnxPeSoftwareVersionMismatch

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.16

Default severity

major

Message format string

Class $tmnxHwClass$ : Software version mismatch - expected software version $tmnxHwSoftwareCodeVersion$, equipped version $tmnxChassisNotifyMismatchedVer$

Cause

Generated when there is a mismatch between software versions of the active CPM and standby CPM or the CPM and IOM. tmnxChassisNotifyHwIndex identifies the mismatched CPM/IOM card and tmnxChassisNotifyMismatchedVer will contain the version of the mismatched card. The tmnxHwSoftwareCodeVersion object will contain the expected version.

Effect

N/A

Recovery

N/A

2.10.174. tmnxPhysChassisFilterDoorClosed

tmnxPhysChassisFilterDoorClosed:CHASSIS
Table 318:  tmnxPhysChassisFilterDoorClosed properties 

Property name

Value

Application name

CHASSIS

Event ID

2195

Event name

tmnxPhysChassisFilterDoorClosed

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.194

Default severity

cleared

Message format string

Filter door is closed

Cause

The tmnxPhysChassisFilterDoorClosed notification is generated when the filter door is present and closed.

Effect

The power shelves are protected by the closed door.

Recovery

No recovery required.

2.10.175. tmnxPhysChassisFilterDoorOpen

tmnxPhysChassisFilterDoorOpen:CHASSIS
Table 319:  tmnxPhysChassisFilterDoorOpen properties 

Property name

Value

Application name

CHASSIS

Event ID

2194

Event name

tmnxPhysChassisFilterDoorOpen

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.193

Default severity

minor

Message format string

Filter door is missing or open

Cause

The tmnxPhysChassisFilterDoorOpen notification is generated when the filter door is either open or not present.

Effect

Power shelf protection may be compromised.

Recovery

If the filter door is not installed, install it. Close the filter door.

2.10.176. tmnxPhysChassisPCMInputFeed

tmnxPhysChassisPCMInputFeed:CHASSIS
Table 320:  tmnxPhysChassisPCMInputFeed properties 

Property name

Value

Application name

CHASSIS

Event ID

2165

Event name

tmnxPhysChassisPCMInputFeed

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.154

Default severity

minor

Message format string

Chassis $tmnxPhysChassisNum$ pcm $tmnxPhysChassisPCMId$ $tmnxPhysChassisPCMInFeedDown$not supplying power.

Cause

The tmnxPhysChassisPCMInputFeed notification is generated if any one of the input feeds for a given PCM has gone offline.

Effect

There is an increased risk of system power brown-outs or black-outs.

Recovery

Restore all of the input feeds that are not supplying power.

2.10.177. tmnxPhysChassisPCMInputFeedClr

tmnxPhysChassisPCMInputFeedClr:CHASSIS
Table 321:  tmnxPhysChassisPCMInputFeedClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2166

Event name

tmnxPhysChassisPCMInputFeedClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.155

Default severity

cleared

Message format string

The input feeds for chassis $tmnxPhysChassisNum$ pcm $tmnxPhysChassisPCMId$ are supplying power.

Cause

The tmnxPhysChassisPCMInputFeedClr notification is generated when the last of the missing input feeds for a given PCM has been brought back online.

Effect

All PCM input feeds are supplying power.

Recovery

No recovery required.

2.10.178. tmnxPhysChassisPMInputFeed

tmnxPhysChassisPMInputFeed:CHASSIS
Table 322:  tmnxPhysChassisPMInputFeed properties 

Property name

Value

Application name

CHASSIS

Event ID

2192

Event name

tmnxPhysChassisPMInputFeed

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.191

Default severity

minor

Message format string

Power module $tmnxHwIndex$ $tmnxPhysChassisPMInputFeedDown$not supplying power.

Cause

The tmnxPhysChassisPMInputFeed notification is generated if any one of the input feeds for a given power module is not supplying power.

Effect

There is an increased risk of system power brownouts or blackouts.

Recovery

Restore all of the input feeds that are not supplying power.

2.10.179. tmnxPhysChassisPMInputFeedClr

tmnxPhysChassisPMInputFeedClr:CHASSIS
Table 323:  tmnxPhysChassisPMInputFeedClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2193

Event name

tmnxPhysChassisPMInputFeedClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.192

Default severity

cleared

Message format string

The input feeds for power module $tmnxHwIndex$ are supplying power.

Cause

The tmnxPhysChassPwrSupInputFeedClr notification is generated when the last of the missing input feeds has been brought back online.

Effect

All power module input feeds are supplying power.

Recovery

No recovery required.

2.10.180. tmnxPhysChassisPMOutFail

tmnxPhysChassisPMOutFail:CHASSIS
Table 324:  tmnxPhysChassisPMOutFail properties 

Property name

Value

Application name

CHASSIS

Event ID

2190

Event name

tmnxPhysChassisPMOutFail

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.189

Default severity

critical

Message format string

Power module $tmnxHwIndex$ output failure

Cause

The tmnxPhysChassisPMOutFail notification is generated when an output failure occurs on the power module.

Effect

The power module is no longer operational.

Recovery

Insert a new power module.

2.10.181. tmnxPhysChassisPMOutFailClr

tmnxPhysChassisPMOutFailClr:CHASSIS
Table 325:  tmnxPhysChassisPMOutFailClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2191

Event name

tmnxPhysChassisPMOutFailClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.190

Default severity

cleared

Message format string

Power module $tmnxHwIndex$ output failure cleared

Cause

The tmnxPhysChassisPMOutFailClr notification is generated when an output failure is cleared on the power module.

Effect

The power module is operational again.

Recovery

There is no recovery for this notification.

2.10.182. tmnxPhysChassisPMOverTemp

tmnxPhysChassisPMOverTemp:CHASSIS
Table 326:  tmnxPhysChassisPMOverTemp properties 

Property name

Value

Application name

CHASSIS

Event ID

2196

Event name

tmnxPhysChassisPMOverTemp

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.195

Default severity

critical

Message format string

$tmnxHwIndex$ over temperature

Cause

The tmnxPhysChassisPMOverTemp notification is generated when a power module's temperature surpasses the temperature threshold.

Effect

The power module is no longer operational.

Recovery

Check input feed and/or insert a new power module.

2.10.183. tmnxPhysChassisPMOverTempClr

tmnxPhysChassisPMOverTempClr:CHASSIS
Table 327:  tmnxPhysChassisPMOverTempClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2197

Event name

tmnxPhysChassisPMOverTempClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.196

Default severity

cleared

Message format string

$tmnxHwIndex$ over temperature cleared

Cause

The tmnxPhysChassisPMOverTempClr notification is generated when a power module's temperature is reduced below the temperature threshold.

Effect

The power module is operational again.

Recovery

There is no recovery for this notification.

2.10.184. tmnxPhysChassPwrSupInputFeed

tmnxPhysChassPwrSupInputFeed:CHASSIS
Table 328:  tmnxPhysChassPwrSupInputFeed properties 

Property name

Value

Application name

CHASSIS

Event ID

2159

Event name

tmnxPhysChassPwrSupInputFeed

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.146

Default severity

minor

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ $tmnxPhysChassPowerSupInFeedDown$not supplying power.

Cause

The tmnxPhysChassPwrSupInputFeed notification is generated if any one of the input feeds for a given power supply is not supplying power.

Effect

There is an increased risk of system power brown-outs or black-outs.

Recovery

Restore all of the input feeds that are not supplying power.

2.10.185. tmnxPhysChassPwrSupInputFeedClr

tmnxPhysChassPwrSupInputFeedClr:CHASSIS
Table 329:  tmnxPhysChassPwrSupInputFeedClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2160

Event name

tmnxPhysChassPwrSupInputFeedClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.147

Default severity

cleared

Message format string

The input feeds for chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ are supplying power.

Cause

The tmnxPhysChassPwrSupInputFeedClr notification is generated when the last of the missing input feeds has been brought back online.

Effect

All power supply input feeds are supplying power.

Recovery

No recovery required.

2.10.186. tmnxPhysChassPwrSupPemACRect

tmnxPhysChassPwrSupPemACRect:CHASSIS
Table 330:  tmnxPhysChassPwrSupPemACRect properties 

Property name

Value

Application name

CHASSIS

Event ID

2157

Event name

tmnxPhysChassPwrSupPemACRect

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.144

Default severity

minor

Message format string

Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ $tmnxPhysChassPowerSupPemACRect$failed or missing.

Cause

The tmnxPhysChassPwrSupPemACRect notification is generated if any one of the AC rectifiers for a given power supply is in a failed state or is missing.

Effect

There is an increased risk of the power supply failing, causing insufficient power to the system.

Recovery

Bring the AC rectifiers back online.

2.10.187. tmnxPhysChassPwrSupPemACRectClr

tmnxPhysChassPwrSupPemACRectClr:CHASSIS
Table 331:  tmnxPhysChassPwrSupPemACRectClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2158

Event name

tmnxPhysChassPwrSupPemACRectClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.145

Default severity

cleared

Message format string

The chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ AC rectifiers are fully operational.

Cause

The tmnxPhysChassPwrSupPemACRectClr notification is generated when the last of the failed or missing AC rectifiers has been brought back online.

Effect

The power supply AC rectifiers are fully operational.

Recovery

No recovery required.

2.10.188. tmnxPhysChassPwrSupWrgFanDir

tmnxPhysChassPwrSupWrgFanDir:CHASSIS
Table 332:  tmnxPhysChassPwrSupWrgFanDir properties 

Property name

Value

Application name

CHASSIS

Event ID

2155

Event name

tmnxPhysChassPwrSupWrgFanDir

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.142

Default severity

major

Message format string

The $tmnxPhysChassPowerSupFanDir$ fan direction for chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ is not supported.

Cause

The tmnxPhysChassPwrSupWrgFanDir notification is generated when the airflow direction of the power supply's fan is incorrect.

Effect

The power supply is not cooling properly and may overheat.

Recovery

Replace the power supply with one that has the proper fan direction.

2.10.189. tmnxPhysChassPwrSupWrgFanDirClr

tmnxPhysChassPwrSupWrgFanDirClr:CHASSIS
Table 333:  tmnxPhysChassPwrSupWrgFanDirClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2156

Event name

tmnxPhysChassPwrSupWrgFanDirClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.143

Default severity

cleared

Message format string

The fan direction for chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ has been corrected.

Cause

The tmnxPhysChassPwrSupWrgFanDirClr notification is generated when the airflow direction of the power supply's fan is corrected.

Effect

The fan is cooling the power supply in the proper direction.

Recovery

No recovery required.

2.10.190. tmnxPlcyAcctStatsEventOvrflw

tmnxPlcyAcctStatsEventOvrflw:CHASSIS
Table 334:  tmnxPlcyAcctStatsEventOvrflw properties 

Property name

Value

Application name

CHASSIS

Event ID

2120

Event name

tmnxPlcyAcctStatsEventOvrflw

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.107

Default severity

minor

Message format string

Policy Accounting FP log event overflow occurred on card $tmnxChassisNotifyCardSlotNum$ at $tmnxPlcyAcctTimeEventOccured$.

Cause

The tmnxPlcyAcctStatsEventOvrflw notification is generated when tmnxPlcyAcctStatsPoolExcResource and tmnxPlcyAcctStatsPoolLowResource occur more than 200 times because of resource usage fluctuation. The IOM raises the final trap to indicate overflow and stops logging traps.

Effect

Some FP notifications configured on the card may not be received.

Recovery

Notifications will resume once the Overflow clear is set.

2.10.191. tmnxPlcyAcctStatsEventOvrflwClr

tmnxPlcyAcctStatsEventOvrflwClr:CHASSIS
Table 335:  tmnxPlcyAcctStatsEventOvrflwClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2119

Event name

tmnxPlcyAcctStatsEventOvrflwClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.106

Default severity

minor

Message format string

$tmnxPlcyAcctMissingNotifCount$ Policy Accounting FP log events were dropped in the last event throttling interval on card $tmnxChassisNotifyCardSlotNum$ at $tmnxPlcyAcctTimeEventOccured$.

Cause

The tmnxPlcyAcctStatsEventOvrflwClr notification is generated when the CPM polls the IOM for traps and the overflow is cleared by logging an overflow-clear on a particular card.

Effect

Notifications are received again since the event throttling has ended.

Recovery

There is no recovery for this notification.

2.10.192. tmnxPlcyAcctStatsPoolExcResource

tmnxPlcyAcctStatsPoolExcResource:CHASSIS
Table 336:  tmnxPlcyAcctStatsPoolExcResource properties 

Property name

Value

Application name

CHASSIS

Event ID

2117

Event name

tmnxPlcyAcctStatsPoolExcResource

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.104

Default severity

minor

Message format string

Stats Resource usage on card $tmnxCardSlotNum$ and forwarding plane $tmnxFPNum$ exceeds 95 percent of the stats pool limit. Total stats resource used is '$tmnxFPPlcyAcctStatsInUse$' and the limit is '$tmnxFPPlcyAcctStatsPool$'

Cause

The tmnxPlcyAcctStatsPoolExcResource notification is generated when the number of in-use stats resource usage as specified by tmnxFPPlcyAcctStatsInUse exceeds 95 percent of the stats pool limit as specified by tmnxFPPlcyAcctStatsPool.

Effect

The affected device may not provide accurate and complete statistics.

Recovery

There is no recovery required for this notification.

2.10.193. tmnxPlcyAcctStatsPoolLowResource

tmnxPlcyAcctStatsPoolLowResource:CHASSIS
Table 337:  tmnxPlcyAcctStatsPoolLowResource properties 

Property name

Value

Application name

CHASSIS

Event ID

2118

Event name

tmnxPlcyAcctStatsPoolLowResource

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.105

Default severity

minor

Message format string

Stats Resource usage on card $tmnxCardSlotNum$ and forwarding plane $tmnxFPNum$ is below 85 percent of the stats pool limit. Total stats resource used is '$tmnxFPPlcyAcctStatsInUse$' and the limit is '$tmnxFPPlcyAcctStatsPool$'

Cause

The tmnxPlcyAcctStatsPoolLowResource notification is generated when the number of in-use stats resource as specified by tmnxFPPlcyAcctStatsInUse is below 85 percent of the stats pool limit as specified by tmnxFPPlcyAcctStatsPool.

Effect

The configured stats pool limit is cleared when the number of in-use stats resources falls below 85 percent of the stats pool limit.

Recovery

There is no recovery required for this notification.

2.10.194. tmnxPowerShelfCommsDown

tmnxPowerShelfCommsDown:CHASSIS
Table 338:  tmnxPowerShelfCommsDown properties 

Property name

Value

Application name

CHASSIS

Event ID

6002

Event name

tmnxPowerShelfCommsDown

SNMP notification prefix and OID

TIMETRA-POWER-SHELF-MIB.tmnxPowerShelfNotifications.2

Default severity

minor

Message format string

Lost communications to $tmnxHwIndex$

Cause

The tmnxPowerShelfCommsDown is generated when there is a loss of communications with the power shelf controller.

Effect

If there is a power failure, it will not be detected since the power modules cannot be polled. The system will continue to report the state of the power modules as they were when last seen.

Recovery

Correct the power shelf controller communications problem.

2.10.195. tmnxPowerShelfCommsUp

tmnxPowerShelfCommsUp:CHASSIS
Table 339:  tmnxPowerShelfCommsUp properties 

Property name

Value

Application name

CHASSIS

Event ID

6003

Event name

tmnxPowerShelfCommsUp

SNMP notification prefix and OID

TIMETRA-POWER-SHELF-MIB.tmnxPowerShelfNotifications.3

Default severity

cleared

Message format string

Re-established communications to $tmnxHwIndex$

Cause

The tmnxPowerShelfCommsUp notification is generated when a loss of communications with the power shelf controller has been resolved.

Effect

Power failures can be detected.

Recovery

No recovery required.

2.10.196. tmnxPowerShelfInputPwrModeSwitch

tmnxPowerShelfInputPwrModeSwitch:CHASSIS
Table 340:  tmnxPowerShelfInputPwrModeSwitch properties 

Property name

Value

Application name

CHASSIS

Event ID

6001

Event name

tmnxPowerShelfInputPwrModeSwitch

SNMP notification prefix and OID

TIMETRA-POWER-SHELF-MIB.tmnxPowerShelfNotifications.1

Default severity

minor

Message format string

$tmnxHwIndex$ input power mode switched to $tmnxPowerShelfInputPowerMode$A

Cause

The tmnxPowerShelfInputPwrModeSwitch is generated when tmnxPowerShelfInputPowerMode has changed value.

Effect

No effect.

Recovery

No recovery required.

2.10.197. tmnxPowerShelfOutputStatusSwitch

tmnxPowerShelfOutputStatusSwitch:CHASSIS
Table 341:  tmnxPowerShelfOutputStatusSwitch properties 

Property name

Value

Application name

CHASSIS

Event ID

6004

Event name

tmnxPowerShelfOutputStatusSwitch

SNMP notification prefix and OID

TIMETRA-POWER-SHELF-MIB.tmnxPowerShelfNotifications.4

Default severity

minor

Message format string

$tmnxHwIndex$ output status switched to $tmnxPowerShelfOutputStatus$

Cause

The tmnxPowerShelfOutputStatusSwitch is generated when tmnxPowerShelfOutputStatus has changed value.

Effect

No effect.

Recovery

No recovery required.

2.10.198. tmnxRedPrimaryCPMFail

tmnxRedPrimaryCPMFail:CHASSIS
Table 342:  tmnxRedPrimaryCPMFail properties 

Property name

Value

Application name

CHASSIS

Event ID

2012

Event name

tmnxRedPrimaryCPMFail

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.21

Default severity

critical

Message format string

Active CPM failed

Cause

Generated when the primary CPM fails.

Effect

N/A

Recovery

N/A

2.10.199. tmnxSasAlarminput1StateChanged

tmnxSasAlarminput1StateChanged:CHASSIS
Table 343:  tmnxSasAlarminput1StateChanged properties 

Property name

Value

Application name

CHASSIS

Event ID

3001

Event name

tmnxSasAlarminput1StateChanged

SNMP notification prefix and OID

TIMETRA-SAS-ALARM-INPUT-MIB.tmnxSasAlarmInputNotifications.1

Default severity

major

Message format string

Alarm Input \"$tmnxSasAlarmInputDescription$\" has changed status\n\"$tmnxSasAlarmInputNotifyMessage$\"

Cause

A tmnxSasAlarminput1StateChanged notification is sent when status of the alarm input on pin one(1) changes. When this notification is sent, the field tmnxSasAlarmInputNotifyMessage is populated with either the tmnxSasAlarmInputTriggerMessage when the alarm is raised, or the tmnxSasAlarmInputClearMessage when the alarm is cleared. The trigger or clear actions depend on the polarity of the input as defined in tmnxSasAlarmInputPolarity.

Effect

A desirable or undesirable event has occurred in the external equipment connected to the alarm input. Hence the characteristics of effect and the associated risks vary depending on the nature of the external equipment being monitored over the alarm input.

Recovery

Check the external equipment, connected to the alarm input pin one(1), that resulted in this alarm and rectify the problem.

2.10.200. tmnxSasAlarminput2StateChanged

tmnxSasAlarminput2StateChanged:CHASSIS
Table 344:  tmnxSasAlarminput2StateChanged properties 

Property name

Value

Application name

CHASSIS

Event ID

3002

Event name

tmnxSasAlarminput2StateChanged

SNMP notification prefix and OID

TIMETRA-SAS-ALARM-INPUT-MIB.tmnxSasAlarmInputNotifications.2

Default severity

major

Message format string

Alarm Input \"$tmnxSasAlarmInputDescription$\" has changed status\n\"$tmnxSasAlarmInputNotifyMessage$\"

Cause

A tmnxSasAlarminput2StateChanged notification is sent when status of the alarm input on pin two(2) changes. When this notification is sent, the field tmnxSasAlarmInputNotifyMessage is populated with either the tmnxSasAlarmInputTriggerMessage when the alarm is raised, or the tmnxSasAlarmInputClearMessage when the alarm is cleared. The trigger or clear actions depend on the polarity of the input as defined in tmnxSasAlarmInputPolarity.

Effect

A desirable or undesirable event has occurred in the external equipment connected to the alarm input. Hence the characteristics of effect and the associated risks vary depending on the nature of the external equipment being monitored over the alarm input.

Recovery

Check the external equipment, connected to the alarm input pin two(2), that resulted in this alarm and rectify the problem.

2.10.201. tmnxSasAlarminput3StateChanged

tmnxSasAlarminput3StateChanged:CHASSIS
Table 345:  tmnxSasAlarminput3StateChanged properties 

Property name

Value

Application name

CHASSIS

Event ID

3003

Event name

tmnxSasAlarminput3StateChanged

SNMP notification prefix and OID

TIMETRA-SAS-ALARM-INPUT-MIB.tmnxSasAlarmInputNotifications.3

Default severity

major

Message format string

Alarm Input \"$tmnxSasAlarmInputDescription$\" has changed status\n\"$tmnxSasAlarmInputNotifyMessage$\"

Cause

A tmnxSasAlarminput3StateChanged notification is sent when status of the alarm input on pin three(3) changes. When this notification is sent, the field tmnxSasAlarmInputNotifyMessage is populated with either the tmnxSasAlarmInputTriggerMessage when the alarm is raised, or the tmnxSasAlarmInputClearMessage when the alarm is cleared. The trigger or clear actions depend on the polarity of the input as defined in tmnxSasAlarmInputPolarity.

Effect

A desirable or undesirable event has occurred in the external equipment connected to the alarm input. Hence the characteristics of effect and the associated risks vary depending on the nature of the external equipment being monitored over the alarm input.

Recovery

Check the external equipment, connected to the alarm input pin three(3), that resulted in this alarm and rectify the problem.

2.10.202. tmnxSasAlarminput4StateChanged

tmnxSasAlarminput4StateChanged:CHASSIS
Table 346:  tmnxSasAlarminput4StateChanged properties 

Property name

Value

Application name

CHASSIS

Event ID

3004

Event name

tmnxSasAlarminput4StateChanged

SNMP notification prefix and OID

TIMETRA-SAS-ALARM-INPUT-MIB.tmnxSasAlarmInputNotifications.4

Default severity

major

Message format string

Alarm Input \"$tmnxSasAlarmInputDescription$\" has changed status\n\"$tmnxSasAlarmInputNotifyMessage$\"

Cause

A tmnxSasAlarminput4StateChanged notification is sent when status of the alarm input on pin four(4) changes. When this notification is sent, the field tmnxSasAlarmInputNotifyMessage is populated with either the tmnxSasAlarmInputTriggerMessage when the alarm is raised, or the tmnxSasAlarmInputClearMessage when the alarm is cleared. The trigger or clear actions depend on the polarity of the input as defined in tmnxSasAlarmInputPolarity.

Effect

A desirable or undesirable event has occurred in the external equipment connected to the alarm input. Hence the characteristics of effect and the associated risks vary depending on the nature of the external equipment being monitored over the alarm input.

Recovery

Check the external equipment, connected to the alarm input pin four(4), that resulted in this alarm and rectify the problem.

2.10.203. tmnxSfmIcPortDDMClear

tmnxSfmIcPortDDMClear:CHASSIS
Table 347:  tmnxSfmIcPortDDMClear properties 

Property name

Value

Application name

CHASSIS

Event ID

4026

Event name

tmnxSfmIcPortDDMClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.7

Default severity

minor

Message format string

SFM interconnect port SFF DDM $tmnxDDMLaneIdOrModule$ ($tmnxDDMFailedObject$) cleared

Cause

The tmnxSfmIcPortDDMFailure notification is generated when an SFF in an SFM interconnect port that supports Digital Diagnostic Monitoring (DDM) clears a failed state.

Effect

N/A

Recovery

N/A

2.10.204. tmnxSfmIcPortDDMFailure

tmnxSfmIcPortDDMFailure:CHASSIS
Table 348:  tmnxSfmIcPortDDMFailure properties 

Property name

Value

Application name

CHASSIS

Event ID

4025

Event name

tmnxSfmIcPortDDMFailure

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.6

Default severity

minor

Message format string

SFM interconnect port SFF DDM $tmnxDDMLaneIdOrModule$ ($tmnxDDMFailedObject$) raised

Cause

The tmnxSfmIcPortDDMFailure notification is generated when an SFF in an SFM interconnect port that supports Digital Diagnostic Monitoring (DDM) enters a failed state.

Effect

N/A

Recovery

N/A

2.10.205. tmnxSfmIcPortDegraded

tmnxSfmIcPortDegraded:CHASSIS
Table 349:  tmnxSfmIcPortDegraded properties 

Property name

Value

Application name

CHASSIS

Event ID

4027

Event name

tmnxSfmIcPortDegraded

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.8

Default severity

minor

Message format string

Switch fabric capacity associated with the SFM interconnect port is in a $tmnxSfmIcPortDegradeState$ state

Cause

The tmnxSfmIcPortDegraded notification is generated when the system has detected a degradation of the switch fabric that is associated with a particular SFM interconnect port. The value of tmnxSfmIcPortDegradeState will reflect this condition by having a value that is NOT 'none (1)'. If the value of tmnxSfmIcPortDegradeState is 'degraded (2)' the SFM interconnect port can still carry some traffic but not at the full capacity of the port. The port and attached cable are not necessarily the cause of the degradation but are a likely cause.

Effect

Switch fabric capacity on this port is reduced when tmnxSfmIcPortDegradeState is degraded. This may not be causing any impact to service because of redundancy in the fabric.

Recovery

Although it may not be necessary to maintain full service, replacing the affected components may restore some fabric capacity."

2.10.206. tmnxSfmIcPortDegradedClear

tmnxSfmIcPortDegradedClear:CHASSIS
Table 350:  tmnxSfmIcPortDegradedClear properties 

Property name

Value

Application name

CHASSIS

Event ID

4028

Event name

tmnxSfmIcPortDegradedClear

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.9

Default severity

minor

Message format string

Switch fabric capacity associated with the SFM interconnect port is not in a degraded state

Cause

The tmnxSfmIcPortDegradedClear notification is generated when the switch fabric associated with the SFM interconnect port is not degraded. This occurs when the value of tmnxSfmIcPortDegradeState is 'none (1)'."

Effect

N/A

Recovery

N/A

2.10.207. tmnxSfmIcPortDown

tmnxSfmIcPortDown:CHASSIS
Table 351:  tmnxSfmIcPortDown properties 

Property name

Value

Application name

CHASSIS

Event ID

4017

Event name

tmnxSfmIcPortDown

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.1

Default severity

minor

Message format string

SFM interconnect port is not operational. Error code = $tmnxSfmIcPortOperState$ to Fabric $tmnxSfmIcPortMisconSfm$ IcPort $tmnxSfmIcPortMisconSfmIcPort$

SFM interconnect port is not operational. Error code = $tmnxSfmIcPortOperState$

Cause

The tmnxSfmIcPortDown alarm is generated when the SFM interconnect port is not operational. The reason may be a cable connected incorrectly, a disconnected cable, a faulty cable, or a misbehaving SFM interconnect port or SFM card.

Effect

This port can no longer be used as part of the user plane fabric between chassis. Other fabric paths may be available resulting in no loss of capacity.

Recovery

A manual verification and testing of each SFM interconnect port is required to ensure fully functional operation. Physical replacement of cabling may be required.

2.10.208. tmnxSfmIcPortSFFInserted

tmnxSfmIcPortSFFInserted:CHASSIS
Table 352:  tmnxSfmIcPortSFFInserted properties 

Property name

Value

Application name

CHASSIS

Event ID

4019

Event name

tmnxSfmIcPortSFFInserted

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.3

Default severity

minor

Message format string

SFM interconnect port SFF inserted

Cause

The tmnxSfmIcPortSFFInserted notification is generated when the Small Form Factor (SFF) pluggable optical module (eg. CXP) is inserted into an SFM interconnect port.

Effect

This event is for notification only.

Recovery

N/A

2.10.209. tmnxSfmIcPortSFFRemoved

tmnxSfmIcPortSFFRemoved:CHASSIS
Table 353:  tmnxSfmIcPortSFFRemoved properties 

Property name

Value

Application name

CHASSIS

Event ID

4020

Event name

tmnxSfmIcPortSFFRemoved

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.4

Default severity

minor

Message format string

SFM interconnect port SFF removed

Cause

The tmnxSfmIcPortSFFRemoved notification is generated when the SFF (eg. CXP) is removed from the SFM interconnect port.

Effect

Removing the module will cause the port to go down. This port can no longer be used as part of the user plane fabric between chassis. Other fabric paths may be available resulting in no loss of capacity.

Recovery

Insert a working SFF into the SFM interconnect port.

2.10.210. tmnxSfmIcPortUp

tmnxSfmIcPortUp:CHASSIS
Table 354:  tmnxSfmIcPortUp properties 

Property name

Value

Application name

CHASSIS

Event ID

4018

Event name

tmnxSfmIcPortUp

SNMP notification prefix and OID

TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.2

Default severity

minor

Message format string

SFM interconnect port is operational

Cause

The tmnxSfmIcPortUp notification is generated when the SFM interconnect port is operational again.

Effect

This port can now be used as part of the user plane fabric between chassis.

Recovery

N/A

2.10.211. tmnxSyncIfTimBITS2048khzUnsup

tmnxSyncIfTimBITS2048khzUnsup:CHASSIS
Table 355:  tmnxSyncIfTimBITS2048khzUnsup properties 

Property name

Value

Application name

CHASSIS

Event ID

2134

Event name

tmnxSyncIfTimBITS2048khzUnsup

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.123

Default severity

major

Message format string

The revision of $tmnxHwIndex$ does not meet the specifications to support the 2048kHz BITS interface type.

Cause

The tmnxSyncIfTimBITS2048khzUnsup notification is generated when the value of tSyncIfTimingAdmBITSIfType is set to 'g703-2048khz (5)' and the CPM does not meet the specifications for the 2048kHz BITS output signal under G.703.

Effect

The BITS input will not be used as the Sync reference and the 2048kHz BITS output signal generated by the CPM is squelched.

Recovery

Replace the CPM with one that is capable of generating the 2048kHz BITS output signal, or set tSyncIfTimingAdmBITSIfType to a value other than 'g703-2048khz (5)'.

2.10.212. tmnxSyncIfTimBITS2048khzUnsupClr

tmnxSyncIfTimBITS2048khzUnsupClr:CHASSIS
Table 356:  tmnxSyncIfTimBITS2048khzUnsupClr properties 

Property name

Value

Application name

CHASSIS

Event ID

2135

Event name

tmnxSyncIfTimBITS2048khzUnsupClr

SNMP notification prefix and OID

TIMETRA-CHASSIS-MIB.tmnxChassisNotification.124

Default severity

major

Message format string

$tmnxHwIndex$ has been replaced with a CPM that meets the specification for 2048kHz or the BITS interface type is no longer 2048kHz.

Cause

The tmnxSyncIfTimBITS2048khzUnsupClr notification is generated when a tmnxSyncIfTimBITS2048khzUnsup notification is outstanding and the CPM was replaced with one that meets the specifications for the 2048kHz BITS output signal under G.703 or tSyncIfTimingAdmBITSIfType is set to a value other than 'g703-2048khz (5)'.

Effect

The CPM can now support the configuration of tSyncIfTimingAdmBITSIfType.

Recovery

No recovery required.

2.11. DEBUG

2.11.1. traceEvent

traceEvent:DEBUG
Table 357:  traceEvent properties 

Property name

Value

Application name

DEBUG

Event ID

2001

Event name

traceEvent

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

$subject$: $title$\n$message$

Cause

The system generated a debug message.

Effect

Unknown.

Recovery

Contact Nokia customer service.

2.12. DHCP

2.12.1. sapDHCPLeaseEntriesExceeded

sapDHCPLeaseEntriesExceeded:DHCP
Table 358:  sapDHCPLeaseEntriesExceeded properties 

Property name

Value

Application name

DHCP

Event ID

2002

Event name

sapDHCPLeaseEntriesExceeded

SNMP notification prefix and OID

TIMETRA-SAP-MIB.sapTraps.9

Default severity

warning

Message format string

Lease state for (CiAddr = $svcDhcpLseStateNewCiAddr$, ChAddr = $svcDhcpLseStateNewChAddr$, leaseTime = $svcDhcpClientLease$) was not stored because the number of DHCP lease states on SAP $sapEncapValue$ in service $svcId$ has reached its upper limit

Cause

The sapDHCPLeaseEntriesExceeded notification is generated when the number of DHCP lease state entries on a given SAP reaches a user configurable upper limit. This limit is given by sapTlsDhcpLeasePopulate for a TLS service and by TIMETRA-VRTR-MIB::vRtrIfDHCPLeasePopulate for an IES or VPRN service.

Effect

N/A

Recovery

Investigate the cause of the excessive DHCP lease states.

2.12.2. sapDHCPLseStateMobilityError

sapDHCPLseStateMobilityError:DHCP
Table 359:  sapDHCPLseStateMobilityError properties 

Property name

Value

Application name

DHCP

Event ID

2027

Event name

sapDHCPLseStateMobilityError

SNMP notification prefix and OID

TIMETRA-SAP-MIB.sapTraps.22

Default severity

warning

Message format string

Unable to perform mobility check on SAP $sapEncapValue$ in service $svcId$

Cause

The sapDHCPLseStateMobilityError notification indicates that the system was unable to perform a mobility check for this lease state.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.3. sapDHCPLseStateOverride

sapDHCPLseStateOverride:DHCP
Table 360:  sapDHCPLseStateOverride properties 

Property name

Value

Application name

DHCP

Event ID

2003

Event name

sapDHCPLseStateOverride

SNMP notification prefix and OID

TIMETRA-SAP-MIB.sapTraps.10

Default severity

warning

Message format string

Existing lease state (ipAddr = $svcDhcpLseStateOldCiAddr$, macAddr = $svcDhcpLseStateOldChAddr$) on SAP $sapEncapValue$ in service $svcId$ overridden to (ipAddr = $svcDhcpLseStateNewCiAddr$, macAddr = $svcDhcpLseStateNewChAddr$)

Cause

The sapDHCPLseStateOverride notification is generated when an existing DHCP lease state is overridden by a new lease state which has the same IP address but a different MAC address.

Effect

Informational.

Recovery

N/A

2.12.4. sapDHCPLseStatePopulateErr

sapDHCPLseStatePopulateErr:DHCP
Table 361:  sapDHCPLseStatePopulateErr properties 

Property name

Value

Application name

DHCP

Event ID

2005

Event name

sapDHCPLseStatePopulateErr

SNMP notification prefix and OID

TIMETRA-SAP-MIB.sapTraps.12

Default severity

warning

Message format string

Lease state table population error on SAP $sapEncapValue$ in service $svcId$ - $svcDhcpLseStatePopulateError$

Cause

The sapDHCPLseStatePopulateErr notification indicates that the system was unable to update the DHCP Lease State table with the information contained in the DHCP ACK message.

Effect

The DHCP ACK message has been discarded.

Recovery

Contact Nokia customer service.

2.12.5. sapDHCPProxyServerError

sapDHCPProxyServerError:DHCP
Table 362:  sapDHCPProxyServerError properties 

Property name

Value

Application name

DHCP

Event ID

2013

Event name

sapDHCPProxyServerError

SNMP notification prefix and OID

TIMETRA-SAP-MIB.sapTraps.18

Default severity

warning

Message format string

DHCP Proxy error on SAP $sapEncapValue$ in service $svcId$ - $svcDhcpProxyError$

Cause

The sapDHCPProxyServerError notification indicates that the system was unable to proxy DHCP requests.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.6. sapDHCPSuspiciousPcktRcvd

sapDHCPSuspiciousPcktRcvd:DHCP
Table 363:  sapDHCPSuspiciousPcktRcvd properties 

Property name

Value

Application name

DHCP

Event ID

2004

Event name

sapDHCPSuspiciousPcktRcvd

SNMP notification prefix and OID

TIMETRA-SAP-MIB.sapTraps.11

Default severity

warning

Message format string

Suspicious DHCP packet received on SAP $sapEncapValue$ in service $svcId$ - $svcDhcpPacketProblem$

Cause

The sapDHCPSuspiciousPcktRcvd notification is generated when a DHCP packet is received with suspicious content.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.7. sapStatHost6DynMacConflict

sapStatHost6DynMacConflict:DHCP
Table 364:  sapStatHost6DynMacConflict properties 

Property name

Value

Application name

DHCP

Event ID

2030

Event name

sapStatHost6DynMacConflict

SNMP notification prefix and OID

TIMETRA-SAP-MIB.sapTraps.58

Default severity

warning

Message format string

The system could not update the MAC address for static host $sapStatHost6IpAddress$ on SAP:$sapEncapValue$, service:$svcId$ - $sapNotifyReason$

Cause

The system failed to update the MAC address of a static IPv6 host.

Effect

The static IPv6 host has a MAC address that is not up to date.

Recovery

The recovery action depends on the exact reason why the MAC update failed. This is clarified in the sapNotifyReason object.

2.12.8. sapStaticHostDynMacConflict

sapStaticHostDynMacConflict:DHCP
Table 365:  sapStaticHostDynMacConflict properties 

Property name

Value

Application name

DHCP

Event ID

2012

Event name

sapStaticHostDynMacConflict

SNMP notification prefix and OID

TIMETRA-SAP-MIB.sapTraps.16

Default severity

warning

Message format string

Trying to learn conflicting dynamic MAC address for static host $staticHostDynamicMacIpAddress$ on SAP $sapEncapValue$ (service $svcId$) - $staticHostDynamicMacConflict$

Cause

The sapStaticHostDynMacConflict notification indicates that the system is trying to learn a conflicting IP-only static host dynamic MAC address (sapStaticHostDynMacAddress).

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.9. sdpBindDHCPLeaseEntriesExceeded

sdpBindDHCPLeaseEntriesExceeded:DHCP
Table 366:  sdpBindDHCPLeaseEntriesExceeded properties 

Property name

Value

Application name

DHCP

Event ID

2006

Event name

sdpBindDHCPLeaseEntriesExceeded

SNMP notification prefix and OID

TIMETRA-SDP-MIB.sdpTraps.10

Default severity

warning

Message format string

Lease state for (CiAddr = $svcDhcpLseStateNewCiAddr$, ChAddr = $svcDhcpLseStateNewChAddr$, leaseTime = $svcDhcpClientLease$) was not stored because the number of DHCP lease states on SDP Bind $sdpBindId$ in service $svcId$ has reached its upper limit

Cause

The sdpBindDHCPLeaseEntriesExceeded notification is generated when the number of DHCP lease state entries on a given IES or VRPN spoke-SDP reaches the user configurable upper limit given by TIMETRA-VRTR-MIB::vRtrIfDHCPLeasePopulate.

Effect

N/A

Recovery

Investigate the cause of the excessive DHCP lease states.

2.12.10. sdpBindDHCPLseStateMobilityErr

sdpBindDHCPLseStateMobilityErr:DHCP
Table 367:  sdpBindDHCPLseStateMobilityErr properties 

Property name

Value

Application name

DHCP

Event ID

2028

Event name

sdpBindDHCPLseStateMobilityErr

SNMP notification prefix and OID

TIMETRA-SDP-MIB.sdpTraps.21

Default severity

warning

Message format string

Unable to perform mobility check on SDP Bind $sdpBindId$ in service $svcId$

Cause

The sdpBindDHCPLseStateMobilityErr notification indicates that the system was unable to perform a mobility check for this lease state.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.11. sdpBindDHCPLseStateOverride

sdpBindDHCPLseStateOverride:DHCP
Table 368:  sdpBindDHCPLseStateOverride properties 

Property name

Value

Application name

DHCP

Event ID

2007

Event name

sdpBindDHCPLseStateOverride

SNMP notification prefix and OID

TIMETRA-SDP-MIB.sdpTraps.11

Default severity

warning

Message format string

Existing lease state (ipAddr = $svcDhcpLseStateOldCiAddr$, macAddr = $svcDhcpLseStateOldChAddr$) on SDP Bind $sdpBindId$ in service $svcId$ overridden to (ipAddr = $svcDhcpLseStateNewCiAddr$, macAddr = $svcDhcpLseStateNewChAddr$)

Cause

The sdpBindDHCPLseStateOverride notification is generated when an existing DHCP lease state is overridden by a new lease state which has the same IP address but a different MAC address. This notification is only applicable to IES and VPRN spoke-SDPs.

Effect

Informational.

Recovery

N/A

2.12.12. sdpBindDHCPLseStatePopulateErr

sdpBindDHCPLseStatePopulateErr:DHCP
Table 369:  sdpBindDHCPLseStatePopulateErr properties 

Property name

Value

Application name

DHCP

Event ID

2009

Event name

sdpBindDHCPLseStatePopulateErr

SNMP notification prefix and OID

TIMETRA-SDP-MIB.sdpTraps.13

Default severity

warning

Message format string

Lease state table population error on SDP Bind $sdpBindId$ in service $svcId$ - $svcDhcpLseStatePopulateError$

Cause

The sdpBindDHCPLseStatePopulateErr notification indicates that the system was unable to update the DHCP Lease State table with the information contained in the DHCP ACK message. This notification is only applicable to IES and VPRN spoke-SDPs.

Effect

The DHCP ACK message has been discarded.

Recovery

Contact Nokia customer service.

2.12.13. sdpBindDHCPProxyServerError

sdpBindDHCPProxyServerError:DHCP
Table 370:  sdpBindDHCPProxyServerError properties 

Property name

Value

Application name

DHCP

Event ID

2016

Event name

sdpBindDHCPProxyServerError

SNMP notification prefix and OID

TIMETRA-SDP-MIB.sdpTraps.17

Default severity

warning

Message format string

DHCP Proxy error on SDP Bind $sdpBindId$ in service $svcId$ - $svcDhcpProxyError$

Cause

The sdpBindDHCPProxyServerError notification indicates that the system was unable to proxy DHCP requests.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.14. sdpBindDHCPSuspiciousPcktRcvd

sdpBindDHCPSuspiciousPcktRcvd:DHCP
Table 371:  sdpBindDHCPSuspiciousPcktRcvd properties 

Property name

Value

Application name

DHCP

Event ID

2008

Event name

sdpBindDHCPSuspiciousPcktRcvd

SNMP notification prefix and OID

TIMETRA-SDP-MIB.sdpTraps.12

Default severity

warning

Message format string

Suspicious DHCP packet received on SDP Bind $sdpBindId$ in service $svcId$ - $svcDhcpPacketProblem$

Cause

The sdpBindDHCPSuspiciousPcktRcvd notification is generated when a DHCP packet is received with suspicious content.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.15. svcDHCPLseStateRestoreProblem

svcDHCPLseStateRestoreProblem:DHCP
Table 372:  svcDHCPLseStateRestoreProblem properties 

Property name

Value

Application name

DHCP

Event ID

2001

Event name

svcDHCPLseStateRestoreProblem

SNMP notification prefix and OID

TIMETRA-SERV-MIB.svcTraps.14

Default severity

warning

Message format string

Problem occured while processing DHCP lease state persistency record (CiAddr = $svcDhcpRestoreLseStateCiAddr$) - $svcDhcpRestoreLseStateProblem$

Cause

The svcDHCPLseStateRestoreProblem notification is generated when an error is detected while processing a persistency record.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.16. svcDHCPMiscellaneousProblem

svcDHCPMiscellaneousProblem:DHCP
Table 373:  svcDHCPMiscellaneousProblem properties 

Property name

Value

Application name

DHCP

Event ID

2029

Event name

svcDHCPMiscellaneousProblem

SNMP notification prefix and OID

TIMETRA-SERV-MIB.svcTraps.23

Default severity

warning

Message format string

$tmnxFailureDescription$

Cause

The svcDHCPMiscellaneousProblem notification is generated on miscellaneous DHCP problems.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.17. tmnxVRtrDHCP6AssignedIllegSubnet

tmnxVRtrDHCP6AssignedIllegSubnet:DHCP
Table 374:  tmnxVRtrDHCP6AssignedIllegSubnet properties 

Property name

Value

Application name

DHCP

Event ID

2025

Event name

tmnxVRtrDHCP6AssignedIllegSubnet

SNMP notification prefix and OID

TIMETRA-VRTR-MIB.tmnxVRtrNotifications.26

Default severity

warning

Message format string

Dropped incoming message because the IP address (inetAddr = $vRtrDHCP6AssignedNetAddr$/$vRtrDHCP6AssignedPrefixLen$) assigned to client (inetAddr = $vRtrDHCP6ClientNetAddr$) does not match the subnet of the incoming interface $vRtrIfName$, or conflicts with an existing node IP address in service $vRtrServiceId$ (vRtr $vRtrID$)

Cause

The tmnxVRtrDHCP6AssignedIllegSubnet notification is generated when an IP address assigned to the client does not match the subnet of the interface.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.18. tmnxVRtrDHCP6ClientMacUnresolved

tmnxVRtrDHCP6ClientMacUnresolved:DHCP
Table 375:  tmnxVRtrDHCP6ClientMacUnresolved properties 

Property name

Value

Application name

DHCP

Event ID

2026

Event name

tmnxVRtrDHCP6ClientMacUnresolved

SNMP notification prefix and OID

TIMETRA-VRTR-MIB.tmnxVRtrNotifications.27

Default severity

warning

Message format string

Received a relay reply for a client with an unresolved MAC address (inetAddr = $vRtrDHCP6ClientNetAddr$) on interface $vRtrIfName$ in service $vRtrServiceId$ (vRtr $vRtrID$)

Cause

The tmnxVRtrDHCP6ClientMacUnresolved notification is generated when a relay reply is received for a client, and the client's MAC address has not been resolved yet.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.19. tmnxVRtrDHCP6IllegalClientAddr

tmnxVRtrDHCP6IllegalClientAddr:DHCP
Table 376:  tmnxVRtrDHCP6IllegalClientAddr properties 

Property name

Value

Application name

DHCP

Event ID

2024

Event name

tmnxVRtrDHCP6IllegalClientAddr

SNMP notification prefix and OID

TIMETRA-VRTR-MIB.tmnxVRtrNotifications.25

Default severity

warning

Message format string

Dropped incoming message because the client source IP (inetAddr = $vRtrDHCP6ClientNetAddr$) does not match the subnet of the incoming interface $vRtrIfName$, or conflicts with an existing node IP address in service $vRtrServiceId$ (vRtr $vRtrID$)

Cause

The tmnxVRtrDHCP6IllegalClientAddr notification is generated when an incoming message is dropped because the client's source IP does not match the subnet of the incoming interface.

Effect

N/A

Recovery

Contact Nokia customer service.

2.12.20. tmnxVRtrDHCP6LseStateOverride

tmnxVRtrDHCP6LseStateOverride:DHCP
Table 377:  tmnxVRtrDHCP6LseStateOverride properties 

Property name

Value

Application name

DHCP

Event ID

2022

Event name

tmnxVRtrDHCP6LseStateOverride

SNMP notification prefix and OID

TIMETRA-VRTR-MIB.tmnxVRtrNotifications.23

Default severity

warning

Message format string

Override existing lease state (inetAddr = $vRtrDHCP6OldAssignedNetAddr$/$vRtrDHCP6OldAssignedPrefixLen$, chAddr = $vRtrDhcpLseStateOldChAddr$, DUID = $vRtrDHCP6OldClientId$) on interface $vRtrIfName$ in service $vRtrServiceId$ (vRtr $vRtrID$) to (inetAddr = $vRtrDHCP6AssignedNetAddr$/$vRtrDHCP6AssignedPrefixLen$, chAddr = $vRtrDhcpLseStateNewChAddr$, DUID = $vRtrDHCP6NewClientId$) - $vRtrDHCP6LeaseOverrideResult$

Cause

The tmnxVRtrDHCP6LseStateOverride notification is generated when an existing DHCP6 lease state is overridden by a new lease state which has the same IP address but a different client ID.

Effect

Informational.

Recovery

N/A

2.12.21. tmnxVRtrDHCP6RelayLseStExceeded

tmnxVRtrDHCP6RelayLseStExceeded:DHCP
Table 378:  tmnxVRtrDHCP6RelayLseStExceeded properties 

Property name

Value

Application name

DHCP

Event ID

2020

Event name

tmnxVRtrDHCP6RelayLseStExceeded

SNMP notification prefix and OID

TIMETRA-VRTR-MIB.tmnxVRtrNotifications.21

Default severity

warning

Message format string

Lease state for (inetAddr = $vRtrDHCP6AssignedNetAddr$/$vRtrDHCP6AssignedPrefixLen$, DUID = $vRtrDHCP6NewClientId$, leaseTime = $svcDhcpClientLease$) was not stored because the number of DHCP6 relay lease states on interface $vRtrIfName$ in service $vRtrServiceId$ (vRtr $vRtrID$) has reached its upper limit of $vRtrIfDHCP6LeasePopulate$

Cause

The tmnxVRtrDHCP6RelayLseStExceeded notification is generated when the number of lease states populated by DHCP6 relay on an interface exceeds vRtrIfDHCP6LeasePopulate.

Effect

N/A

Recovery

Investigate the cause of the excessive DHCP lease states.

2.12.22. tmnxVRtrDHCP6RelayReplyStripUni

tmnxVRtrDHCP6RelayReplyStripUni:DHCP
Table 379:  tmnxVRtrDHCP6RelayReplyStripUni properties 

Property name

Value

Application name

DHCP

Event ID

2023

Event name

tmnxVRtrDHCP6RelayReplyStripUni

SNMP notification prefix and OID

TIMETRA-VRTR-MIB.tmnxVRtrNotifications.24

Default severity

warning

Message format string

DHCP6 relay stripped unicast option from message relayed from server (inetAddr = $vRtrDHCP6ServerNetAddr$) in relay reply message on interface $vRtrIfName$ in service $vRtrServiceId$ (vRtr $vRtrID$)

Cause

The tmnxVRtrDHCP6RelayReplyStripUni notification is generated when a unicast option is stripped from a message relayed from a server to a client in a relay reply message.

Effect

Informational.

Recovery

N/A

2.12.23. tmnxVRtrDHCP6ServerLseStExceeded

tmnxVRtrDHCP6ServerLseStExceeded:DHCP
Table 380:  tmnxVRtrDHCP6ServerLseStExceeded properties 

Property name

Value

Application name

DHCP

Event ID

2021

Event name

tmnxVRtrDHCP6ServerLseStExceeded

SNMP notification prefix and OID

TIMETRA-VRTR-MIB.tmnxVRtrNotifications.22

Default severity

warning

Message format string

Lease state for (inetAddr = $vRtrDHCP6AssignedNetAddr$/$vRtrDHCP6AssignedPrefixLen$, DUID = $vRtrDHCP6NewClientId$, leaseTime = $svcDhcpClientLease$) was not stored because the number of DHCP6 server lease states on interface $vRtrIfName$ in service $vRtrServiceId$ (vRtr $vRtrID$) has reached its upper limit of $vRtrIfDHCP6ServerMaxLeaseStates$

Cause

The tmnxVRtrDHCP6ServerLseStExceeded notification is generated when the number of lease states populated by DHCP6 server on an interface exceeds vRtrIfDHCP6ServerMaxLeaseStates.

Effect

N/A

Recovery

Investigate the cause of the excessive DHCP lease states.

2.12.24. tmnxVRtrDHCPIfLseStatesExceeded

tmnxVRtrDHCPIfLseStatesExceeded:DHCP
Table 381:  tmnxVRtrDHCPIfLseStatesExceeded properties 

Property name

Value

Application name

DHCP

Event ID

2014

Event name

tmnxVRtrDHCPIfLseStatesExceeded

SNMP notification prefix and OID

TIMETRA-VRTR-MIB.tmnxVRtrNotifications.20

Default severity

warning

Message format string

Lease state for (CiAddr = $svcDhcpLseStateNewCiAddr$, ChAddr = $svcDhcpLseStateNewChAddr$, leaseTime = $svcDhcpClientLease$) received on SAP $sapEncapValue$ was not stored because the number of DHCP lease states on interface $vRtrIfName$ in service $vRtrServiceId$ (vRtr $vRtrID$) has reached its upper limit of $vRtrIfDHCPLeasePopulate$.

Cause

The tmnxVRtrDHCPIfLseStatesExceeded notification is generated when the number of lease states on an interface exceeds vRtrIfDHCPLeasePopulate.

Effect

N/A

Recovery

Investigate the cause of the excessive DHCP lease states.

2.12.25. tmnxVRtrDHCPSuspiciousPcktRcvd

tmnxVRtrDHCPSuspiciousPcktRcvd:DHCP
Table 382:  tmnxVRtrDHCPSuspiciousPcktRcvd properties 

Property name

Value

Application name

DHCP

Event ID

2010

Event name

tmnxVRtrDHCPSuspiciousPcktRcvd

SNMP notification prefix and OID

TIMETRA-VRTR-MIB.tmnxVRtrNotifications.14

Default severity

warning

Message format string

Suspicious DHCP packet received on interface $vRtrIfIndex$ in service $vRtrServiceId$ - $vRtrDhcpPacketProblem$

Cause

The tmnxVRtrDHCPSuspiciousPcktRcvd notification is generated when a DHCP packet is received with suspicious content.

Effect

N/A

Recovery

Contact Nokia customer service.

2.13. DHCPS

2.13.1. tmnxDhcpsAddrAllocationFailure

tmnxDhcpsAddrAllocationFailure:DHCPS
Table 383:  tmnxDhcpsAddrAllocationFailure properties 

Property name

Value

Application name

DHCPS

Event ID

2035

Event name

tmnxDhcpsAddrAllocationFailure

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.35

Default severity

warning

Message format string

Server \"$tmnxDhcpSvrNotifServerName$\" could not allocate IP address to client (mac=$tmnxDhcpSvrNotifMsgHwAddress$). Reason: $tmnxDhcpSvrNotifString$

Cause

The tmnxDhcpsAddrAllocationFailure notification is generated when a DHCP server instance could not allocate an address for a client. The reason could be that the DHCP server instance could not find a free address, or it could be a configuration issue.

Effect

The client does not get an IP address lease this time. The client will have to try again if it needs a lease from this system.

Recovery

The recovery action, if any, will depend on the reason.

2.13.2. tmnxDhcpsFoLeaseUpdateFailed

tmnxDhcpsFoLeaseUpdateFailed:DHCPS
Table 384:  tmnxDhcpsFoLeaseUpdateFailed properties 

Property name

Value

Application name

DHCPS

Event ID

2008

Event name

tmnxDhcpsFoLeaseUpdateFailed

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.8

Default severity

warning

Message format string

BNDUPD message could not be processed for DHCP lease (serverName=$tmnxDhcpSvrNotifServerName$, ipAddr=$tmnxDhcpSvrNotifLeaseClientAddr$) sender (mac=$tmnxDhcpSvrNotifMsgHwAddress$ DUID=0x$tmnxDhcpSvrNotifClientDUID$) -- reason: $tmnxDhcpsFoLeaseFailureReason$

Cause

The tmnxDhcpsFoLeaseUpdateFailed notification is generated when a Binding Database Update (BNDUPD) packet received from the failover peer, cannot be processed successfully. The failure reason can be one of the following: foShutdown : the failover state of this DHCP Server instance is 'shutdown'; expired : the lease received from the peer has expired; maxReached : the maximum number of leases is already reached; subnetNotFound : no valid subnet for this lease could be found; rangeNotFound : no valid include range for this lease could be found.

Effect

If this DHCP server instance would have to perform a failover switch, it may lease addresses that were already given in lease by the failover peer. The effect is the same regardless of the failure reason.

Recovery

The required recovery action depends on the failure reason: foShutdown : put the DHCP server instance in state 'inService'; put the DHCP server instance failover facility in state 'inService'; expired : ensure the system clocks of this system and its failover peer are synchronized; maxReached : no recovery is possible; subnetNotFound : configure a valid subnet for this lease; rangeNotFound : configure a valid include range for this lease.

2.13.3. tmnxDhcpsFoStateChange

tmnxDhcpsFoStateChange:DHCPS
Table 385:  tmnxDhcpsFoStateChange properties 

Property name

Value

Application name

DHCPS

Event ID

2007

Event name

tmnxDhcpsFoStateChange

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.7

Default severity

warning

Message format string

DHCP server $tmnxDhcpServerCfgServerName$ changed failover state: $tmnxDhcpsFoState$.

Cause

The failover state of the DHCP server instance changed.

Effect

The effect depends on the new failover state: init | failover is not operational; the DHCP server startUp | instance is not operational; shutdown : failover is not operational; the DHCP server instance is operational in standalone mode; noCommunication : the communication with the partner is lost; the DHCP server temporarily continues to operate as in normal failover state; partnerDown : the partner is assumed down; the DHCP server instance is leasing addresses from its remote ranges as well as its local ranges; normal : failover is operational; the DHCP server instance is leasing addresses from its local ranges.

Recovery

The required recovery action depends on the new failover state: init | no recovery is required; startUp | shutdown : put the DHCP server instance in state 'inService'; put the DHCP server instance failover facility in state 'inService'; noCommunication | repair the communication with the peer; partnerDown | normal : no recovery is required.

2.13.4. tmnxDhcpsLeaseOfferedExpired

tmnxDhcpsLeaseOfferedExpired:DHCPS
Table 386:  tmnxDhcpsLeaseOfferedExpired properties 

Property name

Value

Application name

DHCPS

Event ID

2034

Event name

tmnxDhcpsLeaseOfferedExpired

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.34

Default severity

warning

Message format string

Lease offered by server \"$tmnxDhcpServerCfgServerName$\" ip-address \"$tmnxDhcpSvrLeaseClientAddress$\" to client (mac=$tmnxDhcpSvrNotifMsgHwAddress$ DUID=0x$tmnxDhcpSvrNotifClientDUID$ expired

Cause

The tmnxDhcpsLeaseOfferedExpired notification is generated when a DHCP lease that this system had offered to a client, expires while it is still in the 'offered' state, because this system did not receive a DHCP request message from the client.

Effect

The client does not get a lease this time. The client will have to try again if it needs a lease from this system.

Recovery

The recovery action, if any, will depend on the reason of the expiry.

2.13.5. tmnxDhcpsPacketDropped

tmnxDhcpsPacketDropped:DHCPS
Table 387:  tmnxDhcpsPacketDropped properties 

Property name

Value

Application name

DHCPS

Event ID

2036

Event name

tmnxDhcpsPacketDropped

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.36

Default severity

warning

Message format string

Server \"$tmnxDhcpSvrNotifServerName$\" dropped a packet from client (mac=$tmnxDhcpSvrNotifMsgHwAddress$ DUID=0x$tmnxDhcpSvrNotifClientDUID$). Reason: $tmnxDhcpSvrNotifString$

Cause

The tmnxDhcpsPacketDropped notification is generated when a DHCP server instance dropped a DHCP packet it received.

Effect

Some client request fails. The client will have to try again.

Recovery

The recovery action, if any, will depend on the reason.

2.13.6. tmnxDhcpsPoolFoLeaseUpdateFailed

tmnxDhcpsPoolFoLeaseUpdateFailed:DHCPS
Table 388:  tmnxDhcpsPoolFoLeaseUpdateFailed properties 

Property name

Value

Application name

DHCPS

Event ID

2025

Event name

tmnxDhcpsPoolFoLeaseUpdateFailed

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.25

Default severity

warning

Message format string

BNDUPD message could not be processed for DHCP lease (serverName=$tmnxDhcpServerCfgServerName$, pool=$tmnxDhcpServerPoolName$s, ipAddr=$tmnxDhcpSvrNotifLeaseClientAddr$) sender (mac=$tmnxDhcpSvrNotifMsgHwAddress$ DUID=0x$tmnxDhcpSvrNotifClientDUID$) -- reason: $tmnxDhcpsFoLeaseFailureReason$

Cause

The tmnxDhcpsPoolFoLeaseUpdateFailed notification is generated when a Binding Database Update (BNDUPD) packet received from the failover peer, cannot be processed successfully. This notification is only generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)' or 'ipv6(2)'.

Effect

N/A

Recovery

N/A

2.13.7. tmnxDhcpsPoolFoStateChange

tmnxDhcpsPoolFoStateChange:DHCPS
Table 389:  tmnxDhcpsPoolFoStateChange properties 

Property name

Value

Application name

DHCPS

Event ID

2024

Event name

tmnxDhcpsPoolFoStateChange

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.22

Default severity

warning

Message format string

DHCP server $tmnxDhcpServerCfgServerName$ pool $tmnxDhcpServerPoolName$ changed failover state: $tmnxDhcpsPoolFoState$.

Cause

The tmnxDhcpsPoolFoStateChange notification is generated when the failover state of the DHCP server instance pool changes. This notification is generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)' or 'ipv6(2)'.

Effect

N/A

Recovery

N/A

2.13.8. tmnxDhcpSvrDeclineStaticAddr

tmnxDhcpSvrDeclineStaticAddr:DHCPS
Table 390:  tmnxDhcpSvrDeclineStaticAddr properties 

Property name

Value

Application name

DHCPS

Event ID

2005

Event name

tmnxDhcpSvrDeclineStaticAddr

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.5

Default severity

warning

Message format string

DHCP static IP address (serverName=$tmnxDhcpSvrNotifServerName$, ipAddr=$tmnxDhcpSvrNotifLeaseClientAddr$) is declined by client (HwAddr=$tmnxDhcpSvrNotifMsgHwAddress$)

Cause

The tmnxDhcpSvrDeclineStaticAddr notification is generated when a DHCP decline message is received from a DHCP client that has a static IP address assigned.

Effect

N/A

Recovery

Further investigation is required to determine the cause of the incorrect messages from the client.

2.13.9. tmnxDhcpSvrHostConflict

tmnxDhcpSvrHostConflict:DHCPS
Table 391:  tmnxDhcpSvrHostConflict properties 

Property name

Value

Application name

DHCPS

Event ID

2002

Event name

tmnxDhcpSvrHostConflict

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.2

Default severity

warning

Message format string

DHCP server $tmnxDhcpSvrNotifServerName$ detects IP address assignment conflict for host (name=$tmnxDhcpSvrNotifHostName$, type=$tmnxDhcpSvrNotifHostType$) sender (mac=$tmnxDhcpSvrNotifMsgHwAddress$); ipAddr=$tmnxDhcpSvrNotifLeaseClientAddr$. $tmnxDhcpSvrNotifDescription$

Cause

The tmnxDhcpSvrHostConflict notification can be generated for hosts configured with a fixed IP address in the local user database. If such a host requests an IP address and the system detects that this IP address has already been handed out to another (dynamic) host, then the tmnxDhcpSvrHostConflict notification is generated. This notification is only generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)'.

Effect

N/A

Recovery

Investigate the cause of the address conflict.

2.13.10. tmnxDhcpSvrIntLseConflict

tmnxDhcpSvrIntLseConflict:DHCPS
Table 392:  tmnxDhcpSvrIntLseConflict properties 

Property name

Value

Application name

DHCPS

Event ID

2016

Event name

tmnxDhcpSvrIntLseConflict

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.16

Default severity

warning

Message format string

Internal lease conflict in server \"$tmnxDhcpSvrNotifServerName$\" client (mac=$tmnxDhcpSvrNotifMsgHwAddress$ DUID=0x$tmnxDhcpSvrNotifClientDUID$)

Cause

The tmnxDhcpSvrIntLseConflict notification is generated for DHCP hosts trying to acquire an IP address that was handed through the local address assignment infrastructure, or the local address assignment infrastructure tries to use an IP address that was handed out to a DHCP client. This notification is only generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)'.

Effect

N/A

Recovery

N/A

2.13.11. tmnxDhcpSvrLeaseCreate

tmnxDhcpSvrLeaseCreate:DHCPS
Table 393:  tmnxDhcpSvrLeaseCreate properties 

Property name

Value

Application name

DHCPS

Event ID

2018

Event name

tmnxDhcpSvrLeaseCreate

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.18

Default severity

warning

Message format string

Lease for server \"$tmnxDhcpServerCfgServerName$\" ip-address \"$tmnxDhcpSvrLeaseClientAddress$\" client (mac=$tmnxDhcpSvrNotifMsgHwAddress$ DUID=0x$tmnxDhcpSvrNotifClientDUID$) configuration created

Cause

The tmnxDhcpSvrLeaseCreate notification is generated when a DHCP host is created. This notification is generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)' or 'ipv6(2)'.

Effect

N/A

Recovery

N/A

2.13.12. tmnxDhcpSvrLeaseDefaultTimers

tmnxDhcpSvrLeaseDefaultTimers:DHCPS
Table 394:  tmnxDhcpSvrLeaseDefaultTimers properties 

Property name

Value

Application name

DHCPS

Event ID

2012

Event name

tmnxDhcpSvrLeaseDefaultTimers

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.12

Default severity

warning

Message format string

Reverted to default lease timers for DHCP lease (serverName=$tmnxDhcpSvrNotifServerName$, ipAddr=$tmnxDhcpSvrNotifLeaseClientAddr$) client (mac=$tmnxDhcpSvrNotifMsgHwAddress$ DUID=0x$tmnxDhcpSvrNotifClientDUID$)-- $tmnxDhcpSvrNotifDescription$

Cause

The tmnxDhcpSvrLeaseDefaultTimers notification is generated when, for a particular DHCP client, the system has reverted to default lease timer values, because the configuration of the lease timers was inconsistent. The lease renew time T1 and lease rebind time T2 have been reverted to the default values of 1/2 and 2/3 of the lease time. This notification is generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)' or 'ipv6(2)'.

Effect

N/A

Recovery

N/A

2.13.13. tmnxDhcpSvrLeaseDelete

tmnxDhcpSvrLeaseDelete:DHCPS
Table 395:  tmnxDhcpSvrLeaseDelete properties 

Property name

Value

Application name

DHCPS

Event ID

2019

Event name

tmnxDhcpSvrLeaseDelete

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.19

Default severity

warning

Message format string

Lease for server \"$tmnxDhcpServerCfgServerName$\" ip-address \"$tmnxDhcpSvrLeaseClientAddress$\" client (mac=$tmnxDhcpSvrNotifMsgHwAddress$ DUID=0x$tmnxDhcpSvrNotifClientDUID$ configuration deleted

Cause

The tmnxDhcpSvrLeaseDelete notification is generated when a DHCP host is deleted. This notification is generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)' or 'ipv6(2)'.

Effect

N/A

Recovery

N/A

2.13.14. tmnxDhcpSvrLeaseModify

tmnxDhcpSvrLeaseModify:DHCPS
Table 396:  tmnxDhcpSvrLeaseModify properties 

Property name

Value

Application name

DHCPS

Event ID

2017

Event name

tmnxDhcpSvrLeaseModify

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.17

Default severity

warning

Message format string

Lease for server \"$tmnxDhcpServerCfgServerName$\" ip-address \"$tmnxDhcpSvrLeaseClientAddress$\" client (mac=$tmnxDhcpSvrNotifMsgHwAddress$ DUID=0x$tmnxDhcpSvrNotifClientDUID$) configuration modified

Cause

The tmnxDhcpSvrLeaseModify notification is generated when a DHCP host is modified. This notification is generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)' or 'ipv6(2)'.

Effect

N/A

Recovery

N/A

2.13.15. tmnxDhcpSvrLeaseNotOwner

tmnxDhcpSvrLeaseNotOwner:DHCPS
Table 397:  tmnxDhcpSvrLeaseNotOwner properties 

Property name

Value

Application name

DHCPS

Event ID

2004

Event name

tmnxDhcpSvrLeaseNotOwner

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.4

Default severity

warning

Message format string

DHCP lease (serverName=$tmnxDhcpSvrNotifServerName$, ipAddr=$tmnxDhcpSvrNotifLeaseClientAddr$, ipAddrLen=$tmnxDhcpSvrNotifLeaseClientAddrLen$) is not owned by sender of DHCP message (HwAddr=$tmnxDhcpSvrNotifMsgHwAddress$, DUID=0x$tmnxDhcpSvrNotifClientDUID$) $tmnxDhcpSvrNotifDescription$

Cause

The tmnxDhcpSvrLeaseNotOwner notification is generated when a DHCP message is received from a DHCP client that does not own the lease indicated by the IP address from the message.

Effect

N/A

Recovery

Further investigation is required to determine the cause of the incorrect messages from the client.

2.13.16. tmnxDhcpSvrMaxLeasesReached

tmnxDhcpSvrMaxLeasesReached:DHCPS
Table 398:  tmnxDhcpSvrMaxLeasesReached properties 

Property name

Value

Application name

DHCPS

Event ID

2010

Event name

tmnxDhcpSvrMaxLeasesReached

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.10

Default severity

warning

Message format string

The maximum number of leases ($tmnxDhcpSvrMaxLeases$) has been reached -- dropping DHCP message from sender (mac=$tmnxDhcpSvrNotifMsgHwAddress$ DUID=0x$tmnxDhcpSvrNotifClientDUID$)

Cause

The tmnxDhcpSvrMaxLeasesReached notification is generated when any local DHCP server instance drops a DHCP message because the maximum number of leases was reached.

Effect

No DHCP server instances can lease any addresses.

Recovery

No recovery is possible.

2.13.17. tmnxDhcpSvrMsgTooLong

tmnxDhcpSvrMsgTooLong:DHCPS
Table 399:  tmnxDhcpSvrMsgTooLong properties 

Property name

Value

Application name

DHCPS

Event ID

2006

Event name

tmnxDhcpSvrMsgTooLong

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.6

Default severity

warning

Message format string

DHCP server $tmnxDhcpSvrNotifServerName$ outgoing message to client (mac=$tmnxDhcpSvrNotifMsgHwAddress$, DUID=0x$tmnxDhcpSvrNotifClientDUID$) too long (max size=$tmnxDhcpSvrNotifMsgSizeLimit$)

Cause

The actual length of the DHCP message being built exceeds the maximum size. The maximum size is the minimum of either the maximum DHCP message size or the size provided by the client in the option 'maximum DHCP message size'. A reason can be that too many options are defined on host, pool and subnet levels.

Effect

The Local DHCP Server cannot reply to the client's DHCP requests. The client cannot get an IP address from this DHCP Server.

Recovery

Reduce the number of DHCP options defined on host, pool and subnet levels. Or, if possible, modify the client's DHCP configuration to increase the 'maximum DHCP message size'.

2.13.18. tmnxDhcpSvrNoContFreeBlocks

tmnxDhcpSvrNoContFreeBlocks:DHCPS
Table 400:  tmnxDhcpSvrNoContFreeBlocks properties 

Property name

Value

Application name

DHCPS

Event ID

2022

Event name

tmnxDhcpSvrNoContFreeBlocks

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.20

Default severity

warning

Message format string

Lease creation failed, no contiguous free blocks on server=$tmnxDhcpServerCfgServerName$, link-address=$tmnxDhcpSvrNotifLinkAddr$, pri-pool=$tmnxDhcpSvrNotifPrimaryPool$, sec-pool=$tmnxDhcpSvrNotifSecondaryPool$, client DUID=0x$tmnxDhcpSvrNotifClientDUID$. Reason: $tmnxDhcpSvrNotifString$

Cause

The tmnxDhcpSvrNoContFreeBlocks notification is generated when a lease cannot be created because not enough contiguous blocks are found for the requested delegated prefix size. This notification is only generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv6(2)'. More detailed information about the failure is indicated in the tmnxDhcpSvrNotifString object.

Effect

N/A

Recovery

N/A

2.13.19. tmnxDhcpSvrNoSubnetFixAddr

tmnxDhcpSvrNoSubnetFixAddr:DHCPS
Table 401:  tmnxDhcpSvrNoSubnetFixAddr properties 

Property name

Value

Application name

DHCPS

Event ID

2011

Event name

tmnxDhcpSvrNoSubnetFixAddr

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.11

Default severity

warning

Message format string

DHCP server $tmnxDhcpSvrNotifServerName$ could not find subnet for fixed IP address $tmnxDhcpSvrNotifLeaseClientAddr$ of host (db name =$tmnxDhcpSvrNotifUserDatabaseName$, host name=$tmnxDhcpSvrNotifHostName$, type=$tmnxDhcpSvrNotifHostType$) -- dropping DHCP message from sender (mac=$tmnxDhcpSvrNotifMsgHwAddress$)

Cause

The tmnxDhcpSvrNoSubnetFixAddr notification can be generated for hosts configured with a fixed IP address in the local user database. If such a host requests an IP address and the system cannot find a matching subnet in this server instance for this IP address, then the tmnxDhcpSvrNoSubnetFixAddr notification is generated, and the request is dropped. This notification is only generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)'.

Effect

The Local DHCP Server cannot reply to the client's DHCP requests. The client cannot get an IP address from this DHCP Server.

Recovery

Either configure another fixed IP address for this host, or configure a new subnet in this server instance.

2.13.20. tmnxDhcpSvrPfxThDepletedV6

tmnxDhcpSvrPfxThDepletedV6:DHCPS
Table 402:  tmnxDhcpSvrPfxThDepletedV6 properties 

Property name

Value

Application name

DHCPS

Event ID

2033

Event name

tmnxDhcpSvrPfxThDepletedV6

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.33

Default severity

warning

Message format string

No free prefixes with minimum threshold length $tmnxDhcpsPfxMinFreePrefixLen$ in prefix '$tmnxDhcpSvrSubnetAddress$/$tmnxDhcpSvrSubnetPrefixLength$' in server '$tmnxDhcpServerCfgServerName$'.

Cause

The tmnxDhcpSvrPfxThDepletedV6 notification is generated when the actual number of free prefixes with minimum free threshold length available in the considered prefix becomes zero.

Effect

No more prefixes with minimum free threshold length are available in considered prefix.

Recovery

The operator may create additional prefixes in the considered prefix. Alternatively, examination of the leases in the pool may reveal that the distribution is not appropriate.

2.13.21. tmnxDhcpSvrPfxThTooLowV6

tmnxDhcpSvrPfxThTooLowV6:DHCPS
Table 403:  tmnxDhcpSvrPfxThTooLowV6 properties 

Property name

Value

Application name

DHCPS

Event ID

2032

Event name

tmnxDhcpSvrPfxThTooLowV6

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.32

Default severity

warning

Message format string

The number of prefixes with minimum threshold length in prefix '...' is becoming low. $tmnxDhcpsPfxThCurrFreeBlksHw$/$tmnxDhcpsPfxThCurrFreeBlksLw$ free prefix(es). (Minimum free threshold $tmnxDhcpsPfxMinFreePercent$%/$tmnxDhcpsPfxMinFreeNumber$)

Cause

The tmnxDhcpSvrPfxThTooLowV6 notification is generated when the actual number of free prefixes with minimum free threshold length available in the considered prefix is becoming too low.

Effect

Only a limited number of free prefixes with minimum free threshold length are available in the considered prefix.

Recovery

The operator may create additional prefixes in the considered prefix to prevent a shortage of available prefixes with minimum free threshold length. Alternatively, examination of the leases in the prefix may reveal that the distribution is not appropriate.

2.13.22. tmnxDhcpSvrPlThDepletedV6

tmnxDhcpSvrPlThDepletedV6:DHCPS
Table 404:  tmnxDhcpSvrPlThDepletedV6 properties 

Property name

Value

Application name

DHCPS

Event ID

2031

Event name

tmnxDhcpSvrPlThDepletedV6

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.31

Default severity

warning

Message format string

No free prefixes with minimum threshold length $tmnxDhcpsPlMinFreePrefixLen$ in pool '$tmnxDhcpServerPoolName$' in server '$tmnxDhcpServerCfgServerName$'.

Cause

The tmnxDhcpSvrPlThDepletedV6 notification is generated when the actual number of free prefixes with minimum free threshold length available in the pool becomes zero.

Effect

No more free prefixes with minimum free threshold length are available in the pool.

Recovery

The operator may create additional prefixes in the pool. Alternatively, examination of the leases in the pool may reveal that the distribution is not appropriate.

2.13.23. tmnxDhcpSvrPlThTooLowV6

tmnxDhcpSvrPlThTooLowV6:DHCPS
Table 405:  tmnxDhcpSvrPlThTooLowV6 properties 

Property name

Value

Application name

DHCPS

Event ID

2030

Event name

tmnxDhcpSvrPlThTooLowV6

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.30

Default severity

warning

Message format string

The number of prefixes with minimum threshold length in pool '$tmnxDhcpSvrPoolName$' is becoming low. $tmnxDhcpsPlThCurrFreeBlksHw$/$tmnxDhcpsPlThCurrFreeBlksLw$ free prefix(es). (Minimum free threshold $tmnxDhcpsPlMinFreePercent$%)

Cause

The tmnxDhcpSvrPlThTooLowV6 notification is generated when the actual number of free prefixes with minimum free threshold length available in the pool is becoming too low.

Effect

Only a limited number of free prefixes with minimum free threshold length are available in the pool.

Recovery

The operator may create additional prefixes in the pool to prevent a shortage of available prefixes with minimum free threshold length. Alternatively, examination of the leases in the pool may reveal that the distribution is not appropriate.

2.13.24. tmnxDhcpSvrPoolDepleted

tmnxDhcpSvrPoolDepleted:DHCPS
Table 406:  tmnxDhcpSvrPoolDepleted properties 

Property name

Value

Application name

DHCPS

Event ID

2015

Event name

tmnxDhcpSvrPoolDepleted

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.15

Default severity

warning

Message format string

No free addresses in pool \"$tmnxDhcpServerPoolName$\"

Cause

The tmnxDhcpSvrPoolDepleted notification is generated when the actual number of free addresses becomes zero. This notification is only generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)'.

Effect

N/A

Recovery

N/A

2.13.25. tmnxDhcpSvrPoolMinFreeExc

tmnxDhcpSvrPoolMinFreeExc:DHCPS
Table 407:  tmnxDhcpSvrPoolMinFreeExc properties 

Property name

Value

Application name

DHCPS

Event ID

2013

Event name

tmnxDhcpSvrPoolMinFreeExc

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.13

Default severity

warning

Message format string

The number of free addresses ($tmnxDhcpSvrNotifPoolFree$) has fallen below the desired minimum ($tmnxDhcpServerPoolMinFree$) in pool \"$tmnxDhcpServerPoolName$\"

Cause

The tmnxDhcpSvrPoolMinFreeExc notification is generated when the actual number of free addresses in a pool falls below the desired minimum number.

Effect

If the actual number of free addresses in the pool kept falling, and if it reached zero, no more addresses in this pool would be available for new DHCP hosts.

Recovery

The operator may create additional ranges in the subnet(s), or create an additional subnet. Alternatively, examination of the leases in the pool may reveal that the address distribution is not appropriate.

2.13.26. tmnxDhcpSvrPoolUnknown

tmnxDhcpSvrPoolUnknown:DHCPS
Table 408:  tmnxDhcpSvrPoolUnknown properties 

Property name

Value

Application name

DHCPS

Event ID

2003

Event name

tmnxDhcpSvrPoolUnknown

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.3

Default severity

warning

Message format string

DHCP server $tmnxDhcpSvrNotifServerName$ detects an unknown pool ($tmnxDhcpSvrNotifUnknownPoolName$). $tmnxDhcpSvrNotifDescription$ sender (mac=$tmnxDhcpSvrNotifMsgHwAddress$, DUID=0x$tmnxDhcpSvrNotifClientDUID$)

Cause

The tmnxDhcpServerPoolUnknown notification is generated when the lookup in the local user database for a host returns a pool name which is not defined within the local DHCP server.

Effect

The DHCP server may not be able to serve an IP address.

Recovery

Investigate the cause of the invalid pool name, likely a configuration error.

2.13.27. tmnxDhcpSvrSubnetDepleted

tmnxDhcpSvrSubnetDepleted:DHCPS
Table 409:  tmnxDhcpSvrSubnetDepleted properties 

Property name

Value

Application name

DHCPS

Event ID

2014

Event name

tmnxDhcpSvrSubnetDepleted

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.14

Default severity

warning

Message format string

No free addresses in subnet $tmnxDhcpSvrSubnetAddress$/$tmnxDhcpSvrSubnetPrefixLength$

Cause

The tmnxDhcpSvrSubnetDepleted notification is generated when the actual number of free addresses becomes zero. This notification is only generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)'.

Effect

N/A

Recovery

N/A

2.13.28. tmnxDhcpSvrSubnetMinFreeExc

tmnxDhcpSvrSubnetMinFreeExc:DHCPS
Table 410:  tmnxDhcpSvrSubnetMinFreeExc properties 

Property name

Value

Application name

DHCPS

Event ID

2001

Event name

tmnxDhcpSvrSubnetMinFreeExc

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.1

Default severity

warning

Message format string

The number of free addresses ($tmnxDhcpSvrSubnetStatsFree$) has fallen below the desired minimum ($tmnxDhcpSvrSubnetMinFree$) in subnet $tmnxDhcpSvrSubnetAddress$/$tmnxDhcpSvrSubnetPrefixLength$

Cause

The tmnxDhcpSvrSubnetMinFreeExc notification is generated when the actual number of free addresses in a subnet falls below the desired minimum number.

Effect

If the actual number of free addresses in the subnet kept falling, and if it reached zero, no more addresses in this subnet would be available for new DHCP hosts.

Recovery

The operator may create additional ranges in the subnet, or create an additional subnet. Alternatively, examination of the leases in the subnet may reveal that the address distribution is not appropriate.

2.13.29. tmnxDhcpSvrUserDbUnknown

tmnxDhcpSvrUserDbUnknown:DHCPS
Table 411:  tmnxDhcpSvrUserDbUnknown properties 

Property name

Value

Application name

DHCPS

Event ID

2009

Event name

tmnxDhcpSvrUserDbUnknown

SNMP notification prefix and OID

TIMETRA-DHCP-SERVER-MIB.tmnxDhcpServerNotifications.9

Default severity

warning

Message format string

User database $tmnxDhcpServerCfgUserDatabase$ specified for server $tmnxDhcpServerCfgServerName$ does not exist -- dropping DHCP message from sender (mac=$tmnxDhcpSvrNotifMsgHwAddress$)

Cause

The tmnxDhcpSvrUserDbUnknown notification is generated when the local DHCP server instance drops a DHCP message because a local user database with the name specified for this server instance could not be found. This notification is only generated for DHCP server instances with the value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)'.

Effect

This DHCP server instance cannot lease any addresses.

Recovery

Either reset the object tmnxDhcpServerCfgUserDatabase to its default value, or specify the name of an existing user database.

2.13.30. tmnxLudbDhcpGroupIfTooLong

tmnxLudbDhcpGroupIfTooLong:DHCPS
Table 412:  tmnxLudbDhcpGroupIfTooLong properties 

Property name

Value

Application name

DHCPS

Event ID

2020

Event name

tmnxLudbDhcpGroupIfTooLong

SNMP notification prefix and OID

TIMETRA-LOCAL-USER-DB-MIB.tmnxLocalUserDbNotifications.1

Default severity

warning

Message format string

\"$tmnxLocUsrDbDhcpDefMsapGroupIf$\" concatenated with \"$tmnxLudbNotifyPortId$\" is too long.

Cause

The tmnxLudbDhcpGroupIfTooLong notification is generated when the default MSAP group interface name concatenated with the port-id is longer than 32 characters.

Effect

N/A

Recovery

N/A

2.13.31. tmnxLudbPppoeGroupIfTooLong

tmnxLudbPppoeGroupIfTooLong:DHCPS
Table 413:  tmnxLudbPppoeGroupIfTooLong properties 

Property name

Value

Application name

DHCPS

Event ID

2021

Event name

tmnxLudbPppoeGroupIfTooLong

SNMP notification prefix and OID

TIMETRA-LOCAL-USER-DB-MIB.tmnxLocalUserDbNotifications.2

Default severity

warning

Message format string

\"$tmnxLocUsrDbPppoeDefMsapGroupIf$\" concatenated with \"$tmnxLudbNotifyPortId$\" is too long.

Cause

The tmnxLudbPppoeGroupIfTooLong notification is generated when the default MSAP group interface name concatenated with the port-id is longer than 32 characters.

Effect

N/A

Recovery

N/A

2.14. DIAMETER

2.14.1. tmnxDiamAppSessionFailure

tmnxDiamAppSessionFailure:DIAMETER
Table 414:  tmnxDiamAppSessionFailure properties 

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

Message format string

DIAMETER session failure, sessid=$tmnxDiamAppSessionId$, subscrid=$tmnxDiamAppSubscrId$, sapid=$tmnxDiamAppSapId$, slaprof=$tmnxDiamAppSLAProfName$, $tmnxDiamAppTrapDescription$

Cause

The tmnxDiamAppSessionFailure notification indicates that the DIAMETER protocol has a session failure.

Effect

Determined by cc-failure-handling settings.

Recovery

N/A

2.14.2. tmnxDiamMessageDropped

tmnxDiamMessageDropped:DIAMETER
Table 415:  tmnxDiamMessageDropped properties 

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

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

2.14.3. tmnxDiamPolicyPeerStateChange

tmnxDiamPolicyPeerStateChange:DIAMETER
Table 416:  tmnxDiamPolicyPeerStateChange properties 

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

Message format string

DIAMETER policy $tmnxDiamPlcyName$, peer $tmnxDiamPlcyPeerName$ now has operational state: PrimarySecundary = $tmnxDiamPeerPrimarySecondary$, connectionSuspended = $tmnxDiamPeerConnectionSuspended$ and cooldownSeqActive = $tmnxDiamPeerCooldownSeqActive$, $tmnxDiamAppTrapDescription$

Cause

The state of the diameter policy peer changed.

Effect

N/A

Recovery

No recovery is necessary.

2.14.4. tmnxDiamPpPrxMcLocStateChanged

tmnxDiamPpPrxMcLocStateChanged:DIAMETER
Table 417:  tmnxDiamPpPrxMcLocStateChanged properties 

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

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.

2.14.5. tmnxDiamSessionEvent

tmnxDiamSessionEvent:DIAMETER
Table 418:  tmnxDiamSessionEvent properties 

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

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.

2.15. DYNSVC

2.15.1. tmnxDynSvcSapFailed

tmnxDynSvcSapFailed:DYNSVC
Table 419:  tmnxDynSvcSapFailed properties 

Property name

Value

Application name

DYNSVC

Event ID

2001

Event name

tmnxDynSvcSapFailed

SNMP notification prefix and OID

TIMETRA-DYNAMIC-SERVICES-MIB.tmnxDynSvcNotifications.1

Default severity

minor

Message format string

The requested action for control-session $tmnxDynSvcNotifSapAcctSessionId$ (SAP $tmnxDynSvcNotifSapPortId$) could not be completed - $tmnxDynSvcNotifDescription$

Cause

The tmnxDynSvcSapFailed notification is sent when a Dynamic Services service SAP creation, modification or removal failed.

Effect

The desired new configuration is not in effect; the system has returned to the original configuration if possible.

Recovery

No recovery is necessary when the original configuration could be restored.

2.16. EFM_OAM

2.16.1. dot3OamNonThresholdEvent

dot3OamNonThresholdEvent:EFM_OAM
Table 420:  dot3OamNonThresholdEvent properties 

Property name

Value

Application name

EFM_OAM

Event ID

2005

Event name

dot3OamNonThresholdEvent

SNMP notification prefix and OID

DOT3-OAM-MIB.dot3OamNotifications.2

Default severity

minor

Message format string

Port $ifIndex$ raised $dot3OamEventLogLocation$ fault $dot3OamEventLogType$

Cause

A dot3OamNonThresholdEvent notification is sent when a local or remote non-threshold crossing event is detected. A local event is detected by the local entity, while a remote event is detected by the reception of an Ethernet OAM Event Notification OAMPDU that indicates a non-threshold crossing event. This notification should not be sent more than once per second. The OAM entity can be derived from extracting the ifIndex from the variable bindings. The objects in the notification correspond to the values in a row instance of the dot3OamEventLogTable. The management entity should periodically check dot3OamEventLogTable to detect any missed events.

Effect

N/A

Recovery

N/A

2.16.2. dot3OamThresholdEvent

dot3OamThresholdEvent:EFM_OAM
Table 421:  dot3OamThresholdEvent properties 

Property name

Value

Application name

EFM_OAM

Event ID

2004

Event name

dot3OamThresholdEvent

SNMP notification prefix and OID

DOT3-OAM-MIB.dot3OamNotifications.1

Default severity

major

Message format string

Port $ifIndex$ raised $dot3OamEventLogLocation$ SF fault $dot3OamEventLogType$ - $dot3OamEventLogValue$ errors exceeded the $dot3OamEventLogThresholdLo$ error threshold during the $dot3OamEventLogWindowLo$ decisecond window

Cause

A dot3OamThresholdEvent notification is sent when a local or remote threshold crossing event is detected. A local threshold crossing event is detected by the local entity, while a remote threshold crossing event is detected by the reception of an Ethernet OAM Event Notification OAMPDU that indicates a threshold event. This notification should not be sent more than once per second. The OAM entity can be derived from extracting the ifIndex from the variable bindings. The objects in the notification correspond to the values in a row instance in the dot3OamEventLogTable. The management entity should periodically check dot3OamEventLogTable to detect any missed events.

Effect

N/A

Recovery

N/A

2.16.3. tmnxDot3OamLoopCleared

tmnxDot3OamLoopCleared:EFM_OAM
Table 422:  tmnxDot3OamLoopCleared properties 

Property name

Value

Application name

EFM_OAM

Event ID

2003

Event name

tmnxDot3OamLoopCleared

SNMP notification prefix and OID

TIMETRA-DOT3-OAM-MIB.tmnxDot3OamNotifications.3

Default severity

minor

Message format string

Loop cleared on port $subject$

Cause

The tmnxDot3OamLoopCleared notification is generated if efm-oam is enabled and the protocol stops receiving PDUs with the source MAC address equal to the MAC address of the port it was received on.

Effect

N/A

Recovery

N/A

2.16.4. tmnxDot3OamLoopDetected

tmnxDot3OamLoopDetected:EFM_OAM
Table 423:  tmnxDot3OamLoopDetected properties 

Property name

Value

Application name

EFM_OAM

Event ID

2002

Event name

tmnxDot3OamLoopDetected

SNMP notification prefix and OID

TIMETRA-DOT3-OAM-MIB.tmnxDot3OamNotifications.2

Default severity

minor

Message format string

Loop detected on port $subject$

Cause

The tmnxDot3OamLoopDetected notification is generated if efm-oam is enabled and the protocol receives a PDU with the source MAC address equal to the MAC address of the port it was received on. Only the first such PDU will cause the notification to be generated.

Effect

N/A

Recovery

N/A

2.16.5. tmnxDot3OamNonThresholdEventClr

tmnxDot3OamNonThresholdEventClr:EFM_OAM
Table 424:  tmnxDot3OamNonThresholdEventClr properties 

Property name

Value

Application name

EFM_OAM

Event ID

2008

Event name

tmnxDot3OamNonThresholdEventClr

SNMP notification prefix and OID

TIMETRA-DOT3-OAM-MIB.tmnxDot3OamNotifications.6

Default severity

minor

Message format string

Port $ifIndex$ cleared $dot3OamEventLogLocation$ fault $dot3OamEventLogType$

Cause

The tmnxDot3OamNonThresholdEventClr notification is generated when the local or remote non-threshold crossing event (DOT3-OAM-MIB::dot3OamNonThresholdEvent) is cleared on the port.

Effect

This non-threshold crossing event is no longer a potential cause for the port to restrict user traffic.

Recovery

There is no recovery for this notification.

2.16.6. tmnxDot3OamPeerChanged

tmnxDot3OamPeerChanged:EFM_OAM
Table 425:  tmnxDot3OamPeerChanged properties 

Property name

Value

Application name

EFM_OAM

Event ID

2001

Event name

tmnxDot3OamPeerChanged

SNMP notification prefix and OID

TIMETRA-DOT3-OAM-MIB.tmnxDot3OamNotifications.1

Default severity

minor

Message format string

Peer MAC for port $subject$ has changed to $dot3OamPeerMacAddress$

Cause

The tmnxDot3OamPeerChanged notification is generated when the peer information (specifically the Peer MAC address) changes. Note that this notification will only be sent out if the peer information was previously available and the information changed, and not when the peer information is first learned or becomes unavailable.

Effect

N/A

Recovery

N/A

2.16.7. tmnxDot3OamSdThresholdEvent

tmnxDot3OamSdThresholdEvent:EFM_OAM
Table 426:  tmnxDot3OamSdThresholdEvent properties 

Property name

Value

Application name

EFM_OAM

Event ID

2006

Event name

tmnxDot3OamSdThresholdEvent

SNMP notification prefix and OID

TIMETRA-DOT3-OAM-MIB.tmnxDot3OamNotifications.4

Default severity

minor

Message format string

Port $ifIndex$ $tmnxDot3OamSdEventLogCleared$ $tmnxDot3OamSdEventLogLocation$ SD fault $tmnxDot3OamSdEventLogType$ - $tmnxDot3OamSdEventLogValue$ errors exceeded the $tmnxDot3OamEventLogSdThresholdLo$ error threshold during the $tmnxDot3OamSdEventLogWindowLo$ $tmnxDot3OamSdEventLogType$ window

Cause

The tmnxDot3OamSdThresholdEvent notification is generated when a local or remote threshold crossing event for signal degradation is detected. A local threshold crossing SD event is detected by the local entity, while a remote threshold crossing event is detected by the reception of an Ethernet OAM Event Notification OAMPDU that indicates an SD threshold event. This notification should not be sent more than once per second. The OAM entity can be derived from extracting the ifIndex from the variable bindings. The objects in the notification correspond to the values in a row instance in the tmnxDot3OamSdEventLogTable. The management entity should periodically check tmnxDot3OamSdEventLogTable to detect any missed events.

Effect

N/A

Recovery

N/A

2.16.8. tmnxDot3OamThresholdEventClr

tmnxDot3OamThresholdEventClr:EFM_OAM
Table 427:  tmnxDot3OamThresholdEventClr properties 

Property name

Value

Application name

EFM_OAM

Event ID

2007

Event name

tmnxDot3OamThresholdEventClr

SNMP notification prefix and OID

TIMETRA-DOT3-OAM-MIB.tmnxDot3OamNotifications.5

Default severity

minor

Message format string

Port $ifIndex$ cleared $dot3OamEventLogLocation$ SF fault $dot3OamEventLogType$ - $dot3OamEventLogValue$ errors exceeded the $dot3OamEventLogThresholdLo$ error threshold during the $dot3OamEventLogWindowLo$ $dot3OamEventLogType$ window

Cause

The tmnxDot3OamThresholdEventClr notification is generated when the local or remote signal failure (SF) threshold crossing event is cleared on the port.

Effect

This SF threshold crossing event is no longer a potential cause for the port to restrict user traffic.

Recovery

There is no recovery for this notification.

2.17. ELMI

2.17.1. tmnxElmiEVCStatusChangeEvent

tmnxElmiEVCStatusChangeEvent:ELMI
Table 428:  tmnxElmiEVCStatusChangeEvent properties 

Property name

Value

Application name

ELMI

Event ID

2002

Event name

tmnxElmiEVCStatusChangeEvent

SNMP notification prefix and OID

TIMETRA-ELMI-MIB.tmnxElmiNotifications.2

Default severity

minor

Message format string

EVC $tmnxPortPortID$:$tmnxElmiEvcCfgVlanId$ status has changed to $tmnxElmiEvcCfgStatus$

Cause

The tmnxElmiEVCStatusChangeEvent notification indicates that the indicated Ethernet Virtual Connection (EVC) has changed its active state (ie. from not active to active). The notification is suppressed when the tmnxElmiIfCfgMode is set to 'none (0)'."

Effect

N/A

Recovery

N/A

2.17.2. tmnxElmiIfStatusChangeEvent

tmnxElmiIfStatusChangeEvent:ELMI
Table 429:  tmnxElmiIfStatusChangeEvent properties 

Property name

Value

Application name

ELMI

Event ID

2001

Event name

tmnxElmiIfStatusChangeEvent

SNMP notification prefix and OID

TIMETRA-ELMI-MIB.tmnxElmiNotifications.1

Default severity

minor

Message format string

ELMI on $tmnxPortPortID$ has changed status to $tmnxElmiIfCfgStatus$

Cause

The tmnxElmiStatusChangeEvent notification indicates that the Ethernet LMI Interface has changed state.

Effect

N/A

Recovery

Investigate the cause of the state change.

2.18. ERING

2.18.1. tmnxEthRingApsPrvsnClearAlarm

tmnxEthRingApsPrvsnClearAlarm:ERING
Table 430:  tmnxEthRingApsPrvsnClearAlarm properties 

Property name

Value

Application name

ERING

Event ID

2003

Event name

tmnxEthRingApsPrvsnClearAlarm

SNMP notification prefix and OID

TIMETRA-ETH-RING-MIB.tmnxEthRingApsNotifications.2

Default severity

minor

Message format string

Eth-Ring $tmnxEthRingIndex$ provisioning mismatch (FOP-PM) cleared

Cause

The tmnxEthRingApsPrvsnClearAlarm is generated when an Ethernet Ring provisioning mismatch is cleared.

Effect

N/A

Recovery

N/A

2.18.2. tmnxEthRingApsPrvsnRaiseAlarm

tmnxEthRingApsPrvsnRaiseAlarm:ERING
Table 431:  tmnxEthRingApsPrvsnRaiseAlarm properties 

Property name

Value

Application name

ERING

Event ID

2002

Event name

tmnxEthRingApsPrvsnRaiseAlarm

SNMP notification prefix and OID

TIMETRA-ETH-RING-MIB.tmnxEthRingApsNotifications.1

Default severity

minor

Message format string

Eth-Ring $tmnxEthRingIndex$ provisioning mismatch (FOP-PM) detected: RPL blocked in Node $node$

Cause

The tmnxEthRingApsPrvsnRaiseAlarm is generated when an Ethernet Ring provisioning mismatch is detected. A mismatch occurs when the RPL Owner Node receives one or more No Request R-APS message(s) with RPL Blocked status flag set (NR,RB) and a Node ID that differs from its own.

Effect

N/A

Recovery

Investigate the provisioning mismatch.

2.18.3. tmnxEthRingPathFwdStateChange

tmnxEthRingPathFwdStateChange:ERING
Table 432:  tmnxEthRingPathFwdStateChange properties 

Property name

Value

Application name

ERING

Event ID

2001

Event name

tmnxEthRingPathFwdStateChange

SNMP notification prefix and OID

TIMETRA-ETH-RING-MIB.tmnxEthRingOprNotifications.1

Default severity

minor

Message format string

Eth-Ring $tmnxEthRingIndex$ path $tmnxEthRingPathIndex$ changed fwd state to $tmnxethRingPathFwdState$

Cause

The tmnxEthRingPathFwdStateChange is generated when an Ethernet Ring Path changes its forwarding state (tmnxEthRingPathFwdState) from blocked to unblocked or from unblocked to blocked.

Effect

N/A

Recovery

Further investigation required to determine why the forwarding state has changed.

2.19. ETH_CFM

2.19.1. dot1agCfmFaultAlarm

dot1agCfmFaultAlarm:ETH_CFM
Table 433:  dot1agCfmFaultAlarm properties 

Property name

Value

Application name

ETH_CFM

Event ID

2001

Event name

dot1agCfmFaultAlarm

SNMP notification prefix and OID

IEEE8021-CFM-MIB.dot1agNotifications.1

Default severity

minor

Message format string

MEP $dot1agCfmMdIndex$/$dot1agCfmMaIndex$/$dot1agCfmMepIdentifier$ highest defect is now $dot1agCfmMepHighestPrDefect$

Cause

A MEP has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the MEP that has detected the fault. Whenever a MEP has a persistent defect, it may or may not generate a Fault Alarm to warn the system administrator of the problem, as controlled by the MEP Fault Notification Generator State Machine and associated Managed Objects. Only the highest-priority defect, as shown in Table 20-1, is reported in the Fault Alarm. If a defect with a higher priority is raised after a Fault Alarm has been issued, another Fault Alarm is issued. The management entity receiving the notification can identify the system from the network source address of the notification, and can identify the MEP reporting the defect by the indices in the OID of the dot1agCfmMepHighestPrDefect variable in the notification: dot1agCfmMdIndex - Also the index of the MEP's Maintenance Domain table entry (dot1agCfmMdTable). dot1agCfmMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association network table entry (dot1agCfmMaNetTable), and (with the MD table index and component ID) of the MEP's MA component table entry (dot1agCfmMaCompTable). dot1agCfmMepIdentifier - MEP Identifier and final index into the MEP table (dot1agCfmMepTable). Reference: 802.1ag clause 12.14.7.7

Effect

N/A

Recovery

Investigation is required to determine the cause of the MEP alarm.

2.19.2. tmnxDot1agCfmMepAisStateChanged

tmnxDot1agCfmMepAisStateChanged:ETH_CFM
Table 434:  tmnxDot1agCfmMepAisStateChanged properties 

Property name

Value

Application name

ETH_CFM

Event ID

2006

Event name

tmnxDot1agCfmMepAisStateChanged

SNMP notification prefix and OID

TIMETRA-IEEE8021-CFM-MIB.tmnxDot1agNotifications.5

Default severity

minor

Message format string

MEP $dot1agCfmMdIndex$/$dot1agCfmMaIndex$/$dot1agCfmMepIdentifier$

Cause

The tmnxDot1agCfmMepAisStateChanged notification is generated when a MEP enters or exits an AIS state.

Effect

N/A

Recovery

N/A

2.19.3. tmnxDot1agCfmMepCsfStateChanged

tmnxDot1agCfmMepCsfStateChanged:ETH_CFM
Table 435:  tmnxDot1agCfmMepCsfStateChanged properties 

Property name

Value

Application name

ETH_CFM

Event ID

2009

Event name

tmnxDot1agCfmMepCsfStateChanged

SNMP notification prefix and OID

TIMETRA-IEEE8021-CFM-MIB.tmnxDot1agNotifications.8

Default severity

minor

Message format string

MEP $dot1agCfmMdIndex$/$dot1agCfmMaIndex$/$dot1agCfmMepIdentifier$ is clear of CSF state

MEP $dot1agCfmMdIndex$/$dot1agCfmMaIndex$/$dot1agCfmMepIdentifier$ is in CSF state

Cause

The tmnxDot1agCfmMepCsfStateChanged notification is generated when a MEP enters or exits a CSF state.

Effect

N/A

Recovery

N/A

2.19.4. tmnxDot1agCfmMepDMTestComplete

tmnxDot1agCfmMepDMTestComplete:ETH_CFM
Table 436:  tmnxDot1agCfmMepDMTestComplete properties 

Property name

Value

Application name

ETH_CFM

Event ID

2005

Event name

tmnxDot1agCfmMepDMTestComplete

SNMP notification prefix and OID

TIMETRA-IEEE8021-CFM-MIB.tmnxDot1agNotifications.4

Default severity

minor

Message format string

$tmnxDot1agCfmMepDelayTestType$ test complete on MEP $dot1agCfmMdIndex$/$dot1agCfmMaIndex$/$dot1agCfmMepIdentifier$: Delay=$tmnxDot1agCfmMepDelayTestDelay$us

Cause

The tmnxDot1agCfmMepDMTestComplete notification indicates that a One-Way-Delay-Test (OWDT) frame, or a Two-Way-Delay-Test (TWDT) response was received. For an OWDT frame, traps are raised only when a delay threshold of three seconds is exceeded.

Effect

N/A

Recovery

N/A

2.19.5. tmnxDot1agCfmMepEthTestComplete

tmnxDot1agCfmMepEthTestComplete:ETH_CFM
Table 437:  tmnxDot1agCfmMepEthTestComplete properties 

Property name

Value

Application name

ETH_CFM

Event ID

2004

Event name

tmnxDot1agCfmMepEthTestComplete

SNMP notification prefix and OID

TIMETRA-IEEE8021-CFM-MIB.tmnxDot1agNotifications.3

Default severity

minor

Message format string

eth-test complete on MEP $dot1agCfmMdIndex$/$dot1agCfmMaIndex$/$dot1agCfmMepIdentifier$: Bytes/Failed Bits/CRC Failures=$tmnxDot1agCfmMepCurrByteCount$/$tmnxDot1agCfmMepCurrFailedBits$/$tmnxDot1agCfmMepCurrCrcFailures$

Cause

The tmnxDot1agCfmMepEthTestComplete notification indicates that an eth-test has been issued and results are ready. The tmnxDot1agCfmMepCurrByteCount indicates the number of bytes contained in the frame's Test TLV, and the tmnxDot1agCfmMepCurrFailedBits and tmnxDot1agCfmMepCurrCrcFailures indicate the failure state of the test. A value of Zero (0) for tmnxDot1agCfmMepCurrFailedBits and a value of 'false (2)' for tmnxDot1agCfmMepCurrCrcFailures indicates a successful test.

Effect

N/A

Recovery

N/A

2.19.6. tmnxDot1agCfmMepFcltyFaultClear

tmnxDot1agCfmMepFcltyFaultClear:ETH_CFM
Table 438:  tmnxDot1agCfmMepFcltyFaultClear properties 

Property name

Value

Application name

ETH_CFM

Event ID

2011

Event name

tmnxDot1agCfmMepFcltyFaultClear

SNMP notification prefix and OID

TIMETRA-IEEE8021-CFM-MIB.tmnxDot1agNotifications.10

Default severity

cleared

Message format string

ETH-CFM MEP facility fault cleared $tmnxDot1agCfmMepFcltyType$ $tmnxDot1agCfmMepFcltyInstance$

Cause

The tmnxDot1agCfmMepFcltyFaultClear notification is generated when the associated facility MEP has cleared an event affecting the specific tmnxDot1agCfmMepFcltyType tmnxDot1agCfmMepFcltyInstance combination over which it is configured.

Effect

This notification can be used to correlate the ETH_CFM dot1agCfmFaultAlarm event and the related IF-MIB::linkUp notification caused by the facility MEP.

Recovery

N/A

2.19.7. tmnxDot1agCfmMepFcltyFaultRaise

tmnxDot1agCfmMepFcltyFaultRaise:ETH_CFM
Table 439:  tmnxDot1agCfmMepFcltyFaultRaise properties 

Property name

Value

Application name

ETH_CFM

Event ID

2010

Event name

tmnxDot1agCfmMepFcltyFaultRaise

SNMP notification prefix and OID

TIMETRA-IEEE8021-CFM-MIB.tmnxDot1agNotifications.9

Default severity

warning

Message format string

ETH-CFM MEP facility fault raised $tmnxDot1agCfmMepFcltyType$ $tmnxDot1agCfmMepFcltyInstance$

Cause

The tmnxDot1agCfmMepFcltyFaultRaise notification is generated when the associated facility MEP dot1agCfmMepHighestPrDefect has increased.

Effect

This notification can be used to correlate the ETH_CFM dot1agCfmFaultAlarm event and the related IF-MIB::linkDown notification caused by the failure of the facility MEP.

Recovery

Follow the recovery for the dot1agCfmFaultAlarm and the related IF-MIB::linkDown caused by the failure of the facility MEP.

2.19.8. tmnxDot1agCfmMepLbmTestComplete

tmnxDot1agCfmMepLbmTestComplete:ETH_CFM
Table 440:  tmnxDot1agCfmMepLbmTestComplete properties 

Property name

Value

Application name

ETH_CFM

Event ID

2002

Event name

tmnxDot1agCfmMepLbmTestComplete

SNMP notification prefix and OID

TIMETRA-IEEE8021-CFM-MIB.tmnxDot1agNotifications.1

Default severity

minor

Message format string

loopback test results on MEP $dot1agCfmMdIndex$/$dot1agCfmMaIndex$/$dot1agCfmMepIdentifier$ for $dot1agCfmMepTransmitLbmDestMacAddress$ are available

Cause

The tmnxDot1agCfmMepLbmTestComplete notification indicates that a loopback test has been issued and results are ready.

Effect

N/A

Recovery

N/A

2.19.9. tmnxDot1agCfmMepLtmTestComplete

tmnxDot1agCfmMepLtmTestComplete:ETH_CFM
Table 441:  tmnxDot1agCfmMepLtmTestComplete properties 

Property name

Value

Application name

ETH_CFM

Event ID

2003

Event name

tmnxDot1agCfmMepLtmTestComplete

SNMP notification prefix and OID

TIMETRA-IEEE8021-CFM-MIB.tmnxDot1agNotifications.2

Default severity

minor

Message format string

linktrace test results with sequenceNumber $dot1agCfmMepTransmitLtmSeqNumber$ on MEP $dot1agCfmMdIndex$/$dot1agCfmMaIndex$/$dot1agCfmMepIdentifier$ are now available

Cause

The tmnxDot1agCfmMepLtmTestComplete notification indicates that a linktrace test has been issued and results are ready. The dot1agCfmMepTransmitLtmSeqNumber indicates the Transaction Identifier to use to retrieve the Link-trace results.

Effect

N/A

Recovery

N/A

2.19.10. tmnxDot1agCfmMepSLMTestComplete

tmnxDot1agCfmMepSLMTestComplete:ETH_CFM
Table 442:  tmnxDot1agCfmMepSLMTestComplete properties 

Property name

Value

Application name

ETH_CFM

Event ID

2008

Event name

tmnxDot1agCfmMepSLMTestComplete

SNMP notification prefix and OID

TIMETRA-IEEE8021-CFM-MIB.tmnxDot1agNotifications.7

Default severity

minor

Message format string

SLM $tmnxDot1agCfmMepSlmTestType$ (test-id $tmnxDot1agCfmMepSlmTestId$) completed for remote-mep $tmnxDot1agCfmMepSlmRemoteMepId$ remote MAC $tmnxDot1agCfmMepSlmRemoteMacAddr$

Cause

The tmnxDot1agCfmMepSLMTestComplete notification is generated when a one-way or two-way Synthetic Loss Measurement (SLM) test is completed. For one-way SLM test results, tmnxDot1agCfmMepSlmPacketLossOut and tmnxDot1agCfmMepSlmPacketUnack values are fixed at 'zero(0)'.

Effect

N/A

Recovery

N/A

2.19.11. tmnxDot1agCfmMipEvaluation

tmnxDot1agCfmMipEvaluation:ETH_CFM
Table 443:  tmnxDot1agCfmMipEvaluation properties 

Property name

Value

Application name

ETH_CFM

Event ID

2007

Event name

tmnxDot1agCfmMipEvaluation

SNMP notification prefix and OID

TIMETRA-IEEE8021-CFM-MIB.tmnxDot1agNotifications.6

Default severity

minor

Message format string

Reevaluating MIPs on service $tmnxDot1agCfmNotifySvcId$ due to virtual MEP configuration

Cause

The tmnxDot1agCfmMipEvaluation notification is generated when a virtual MEP is created or deleted causing MIP reevaluation on the service. On virtual MEP creation, any MIPs in the service will be removed. On virtual MEP deletion, the MIPs are reevaluated.

Effect

N/A

Recovery

N/A

2.20. ETH_TUNNEL

2.20.1. tmnxEthTunnelApsCfgClearAlarm

tmnxEthTunnelApsCfgClearAlarm:ETH_TUNNEL
Table 444:  tmnxEthTunnelApsCfgClearAlarm properties 

Property name

Value

Application name

ETH_TUNNEL

Event ID

2002

Event name

tmnxEthTunnelApsCfgClearAlarm

SNMP notification prefix and OID

TIMETRA-ETH-TUNNEL-MIB.tmnxEthTunnelApsNotifications.2

Default severity

minor

Message format string

Eth-Tunnel $tmnxEthTunnelIndex$ cleared configuration mismatch $tmnxEthTunnelApsDefectStatus$

Cause

The tmnxEthTunnelApsCfgClearAlarm is generated when an Ethernet Tunnel Group working and protection configuration mismatch is cleared.

Effect

N/A

Recovery

N/A

2.20.2. tmnxEthTunnelApsCfgRaiseAlarm

tmnxEthTunnelApsCfgRaiseAlarm:ETH_TUNNEL
Table 445:  tmnxEthTunnelApsCfgRaiseAlarm properties 

Property name

Value

Application name

ETH_TUNNEL

Event ID

2001

Event name

tmnxEthTunnelApsCfgRaiseAlarm

SNMP notification prefix and OID

TIMETRA-ETH-TUNNEL-MIB.tmnxEthTunnelApsNotifications.1

Default severity

minor

Message format string

Eth-Tunnel $tmnxEthTunnelIndex$ experiencing configuration mismatch $tmnxEthTunnelApsDefectStatus$

Cause

The tmnxEthTunnelApsCfgRaiseAlarm is generated when an Ethernet Tunnel Group working and protection configuration mismatch is detected, at the ETH layer, by detecting the reception of APS protocol from the working transport entity.

Effect

N/A

Recovery

Further investigation required to determine the source of the configuration mismatch.

2.20.3. tmnxEthTunnelApsNoRspClearAlarm

tmnxEthTunnelApsNoRspClearAlarm:ETH_TUNNEL
Table 446:  tmnxEthTunnelApsNoRspClearAlarm properties 

Property name

Value

Application name

ETH_TUNNEL

Event ID

2006

Event name

tmnxEthTunnelApsNoRspClearAlarm

SNMP notification prefix and OID

TIMETRA-ETH-TUNNEL-MIB.tmnxEthTunnelApsNotifications.6

Default severity

minor

Message format string

Eth-Tunnel $tmnxEthTunnelIndex$ cleared incomplete protection switch ($tmnxEthTunnelApsDefectStatus$)

Cause

The tmnxEthTunnelApsNoRspClearAlarm is generated when an Ethernet Tunnel Group no longer experiences an incompletion of protection switching at the ETH layer.

Effect

N/A

Recovery

N/A

2.20.4. tmnxEthTunnelApsNoRspRaiseAlarm

tmnxEthTunnelApsNoRspRaiseAlarm:ETH_TUNNEL
Table 447:  tmnxEthTunnelApsNoRspRaiseAlarm properties 

Property name

Value

Application name

ETH_TUNNEL

Event ID

2005

Event name

tmnxEthTunnelApsNoRspRaiseAlarm

SNMP notification prefix and OID

TIMETRA-ETH-TUNNEL-MIB.tmnxEthTunnelApsNotifications.5

Default severity

minor

Message format string

Eth-Tunnel $tmnxEthTunnelIndex$ experiencing incomplete protection switch ($tmnxEthTunnelApsDefectStatus$)

Cause

The tmnxEthTunnelApsNoRspRaiseAlarm is generated when an Ethernet Tunnel Group experiences an incompletion of protection switching, at the ETH layer, by comparing the transmitted 'Requested Signal' values and the received 'Bridged Signal' in the APS protocol.

Effect

N/A

Recovery

Further investigation is required to determine the cause of the incomplete protection switch.

2.20.5. tmnxEthTunnelApsPrvsnClearAlarm

tmnxEthTunnelApsPrvsnClearAlarm:ETH_TUNNEL
Table 448:  tmnxEthTunnelApsPrvsnClearAlarm properties 

Property name

Value

Application name

ETH_TUNNEL

Event ID

2004

Event name

tmnxEthTunnelApsPrvsnClearAlarm

SNMP notification prefix and OID

TIMETRA-ETH-TUNNEL-MIB.tmnxEthTunnelApsNotifications.4

Default severity

minor

Message format string

Eth-Tunnel $tmnxEthTunnelIndex$ cleared provisioning mismatch $tmnxEthTunnelApsDefectStatus$ ($tmnxEthTunnelApsRxPdu$/$tmnxEthTunnelApsTxPdu$)

Cause

The tmnxEthTunnelApsPrvsnClearAlarm is generated when an Ethernet Tunnel Group provisioning mismatch is cleared.

Effect

N/A

Recovery

N/A

2.20.6. tmnxEthTunnelApsPrvsnRaiseAlarm

tmnxEthTunnelApsPrvsnRaiseAlarm:ETH_TUNNEL
Table 449:  tmnxEthTunnelApsPrvsnRaiseAlarm properties 

Property name

Value

Application name

ETH_TUNNEL

Event ID

2003

Event name

tmnxEthTunnelApsPrvsnRaiseAlarm

SNMP notification prefix and OID

TIMETRA-ETH-TUNNEL-MIB.tmnxEthTunnelApsNotifications.3

Default severity

minor

Message format string

Eth-Tunnel $tmnxEthTunnelIndex$ experiencing provisioning mismatch $tmnxEthTunnelApsDefectStatus$: Rx 0x$tmnxEthTunnelApsRxPdu$ Tx 0x$tmnxEthTunnelApsTxPdu$

Cause

The tmnxEthTunnelApsPrvsnRaiseAlarm is generated when an Ethernet Tunnel Group provisioning mismatch is detected, at the ETH layer, by comparing A, B and D bits of the transmitted and received APS protocol. The provision mismatch state is considered as if there is a signal failure on the protection member. This ensures that the working member is kept as active member in the provision mismatch state.

Effect

N/A

Recovery

Further investigation required to determine the source of the provisioning mismatch.

2.20.7. tmnxEthTunnelApsSwitchoverAlarm

tmnxEthTunnelApsSwitchoverAlarm:ETH_TUNNEL
Table 450:  tmnxEthTunnelApsSwitchoverAlarm properties 

Property name

Value

Application name

ETH_TUNNEL

Event ID

2007

Event name

tmnxEthTunnelApsSwitchoverAlarm

SNMP notification prefix and OID

TIMETRA-ETH-TUNNEL-MIB.tmnxEthTunnelApsNotifications.7

Default severity

minor

Message format string

Eth-Tunnel $tmnxEthTunnelIndex$ experienced member activity switchover. Path $tmnxEthTunnelMemberIndex$ is now active.

Cause

The tmnxEthTunnelApsSwitchoverAlarm is generated when an Ethernet Tunnel Group experiences a member activity switchover. The tmnxEthTunnelMemberPrecedence always specifies the active member.

Effect

N/A

Recovery

N/A

2.21. FILTER

2.21.1. tFilterApplyPathProblem

tFilterApplyPathProblem:FILTER
Table 451:  tFilterApplyPathProblem properties 

Property name

Value

Application name

FILTER

Event ID

2008

Event name

tFilterApplyPathProblem

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.8

Default severity

minor

Message format string

TODO

Cause

The tFilterApplyPathProblem notification is generated when a problem is encountered for a configured apply-path rule.

Effect

None.

Recovery

No recovery is required.

2.21.2. tFilterBgpFlowSpecProblem

tFilterBgpFlowSpecProblem:FILTER
Table 452:  tFilterBgpFlowSpecProblem properties 

Property name

Value

Application name

FILTER

Event ID

2007

Event name

tFilterBgpFlowSpecProblem

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.7

Default severity

minor

Message format string

N/A

Cause

N/A

Effect

N/A

Recovery

N/A

2.21.3. tFilterEmbeddingOperStateChange

tFilterEmbeddingOperStateChange:FILTER
Table 453:  tFilterEmbeddingOperStateChange properties 

Property name

Value

Application name

FILTER

Event ID

2011

Event name

tFilterEmbeddingOperStateChange

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.11

Default severity

minor

Message format string

The operational state of the embedded filter ID $tFilterEmbeddedRefEmbeddedFltrId$ in the embedding filter $tFilterEmbeddedRefFilterType$ ID $tFilterEmbeddedRefInsertFltrId$ has changed to $tFilterEmbeddedRefOperState$.

Cause

This notification may be triggered for the following reasons: 1) An attempt to embed an embedded filter into embedding filter was done. 2) An attempt to recover an embedding that is operationally down was done. 3) An attempt to change the admin state of an embedding was done. 4) The operational state of an embedding has changed to inactive due to lack of resources.

Effect

The effect depends on the new state. If the new state is 'active', the embedding of the filter was successful. If the new state is 'embedFailedNoResources' the embedding was not successful due to lack of resources. If the new state is 'inactive' and the previous state was 'active' then the embedded entries were removed. Otherwise the embedding filter was not changed.

Recovery

If the new state is 'active' or 'inactive', no action is required. If the new state is 'embedFailedNoResources', an attempt to recover the operational state can be done by removal and reapplication of the embedding.

2.21.4. tFilterEmbedFlowspecOperStateChg

tFilterEmbedFlowspecOperStateChg:FILTER
Table 454:  tFilterEmbedFlowspecOperStateChg properties 

Property name

Value

Application name

FILTER

Event ID

2015

Event name

tFilterEmbedFlowspecOperStateChg

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.14

Default severity

minor

Message format string

The operational state of the embedded flowspec rules of virtual router $tFilterEmbedFlowspecRtrId$ in the embedding filter $tFilterEmbedFlowspecFilterType$ ID $tFilterEmbedFlowspecInsertFltrId$ has changed to $tFilterEmbedFlowspecOperState$.

Cause

This notification may be triggered for the following reasons: 1) An attempt to embed a set of flowspec rules into an embedding filter was done. 2) An attempt to recover a flowspec rules embedding that is operationally down was done. 3) An attempt to change the admin state of a flowspec rules embedding was done. 4) The operational state of a flowspec rules embedding has changed to inactive due to lack of resources.

Effect

The effect depends on the new state. If the new state is 'active', the embedding of a set of flowspec rules was successful. If the new state is 'embedFailedNoResources' the embedding was not successful due to lack of resources. If the new state is 'inactive' and the previous state was 'active' then the set of flowspec rules were removed. Otherwise the embedding filter was not changed.

Recovery

If the new state is 'active' or 'inactive', no action is required. If the new state is 'embedFailedNoResources', an attempt to recover the operational state can be done by removal and reapplication of the flowspec rules embedding.

2.21.5. tFilterEmbedOpenflowOperStateChg

tFilterEmbedOpenflowOperStateChg:FILTER
Table 455:  tFilterEmbedOpenflowOperStateChg properties 

Property name

Value

Application name

FILTER

Event ID

2012

Event name

tFilterEmbedOpenflowOperStateChg

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.12

Default severity

minor

Message format string

The operational state of the embedded open-flow switch $tFilterEmbedOpenflowOfsName$ in the embedding filter $tFilterEmbedOpenflowFilterType$ ID $tFilterEmbedOpenflowInsertFltrId$ has changed to $tFilterEmbedOpenflowOperState$.

Cause

This notification may be triggered for the following reasons: 1) An attempt to embed an open-flow switch into an embedding filter was done. 2) An attempt to recover an open-flow embedding that is operationally down was done. 3) An attempt to change the admin state of an open-flow embedding was done. 4) The operational state of an open-flow embedding has changed to inactive due to lack of resources.

Effect

The effect depends on the new state. If the new state is 'active', the embedding of an open-flow switch was successful. If the new state is 'embedFailedNoResources' the embedding was not successful due to lack of resources. If the new state is 'inactive' and the previous state was 'active' then the open-flow switch entries were removed. Otherwise the embedding filter was not changed.

Recovery

If the new state is 'active' or 'inactive', no action is required. If the new state is 'embedFailedNoResources', an attempt to recover the operational state can be done by removal and reapplication of the open-flow embedding.

2.21.6. tFilterEmbedVsdOperStateChg

tFilterEmbedVsdOperStateChg:FILTER
Table 456:  tFilterEmbedVsdOperStateChg properties 

Property name

Value

Application name

FILTER

Event ID

2016

Event name

tFilterEmbedVsdOperStateChg

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.15

Default severity

minor

Message format string

The operational state of the embedded VSD $tFilterEmbedVsdFilterType$ filter ID _tmnx_vsd_$tFilterEmbedVsdEmbeddedFltrId$ in the embedding $tFilterEmbedVsdFilterType$ filter ID $tFilterEmbedVsdInsertFltrId$ has changed to $tFilterEmbedVsdOperState$.

Cause

This notification may be triggered for the following reasons: 1) An attempt to embed a filter managed by a VSD controller into an embedding filter was done. 2) An attempt to recover an embedding that is operationally down was done. 3) An attempt to change the admin state of an embedding was done. 4) The operational state of an embedding has changed to inactive due to lack of resources.

Effect

The effect depends on the new state. If the new state is 'active', the embedding of a filter managed by a VSD controller was successful. If the new state is 'embedFailedNoResources' the embedding was not successful due to lack of resources. If the new state is 'inactive' and the previous state was 'active' then the embedded entries were removed. Otherwise the embedding filter was not changed.

Recovery

If the new state is 'active' or 'inactive', no action is required. If the new state is 'embedFailedNoResources', an attempt to recover the operational state can be done by removal and reapplication of the embedding.

2.21.7. tFilterOpenflowRequestRejected

tFilterOpenflowRequestRejected:FILTER
Table 457:  tFilterOpenflowRequestRejected properties 

Property name

Value

Application name

FILTER

Event ID

2013

Event name

tFilterOpenflowRequestRejected

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

An error was encountered while handlig filter entry $fltrOpenFlowFlowEntryId$ for the open-flow flowTable $fltrOpenFlowFlowTable$. Additional Info: $fltrOpenFlowProblemDescription$.

Cause

N/A

Effect

N/A

Recovery

N/A

2.21.8. tFilterRadSharedFltrAlarmClear

tFilterRadSharedFltrAlarmClear:FILTER
Table 458:  tFilterRadSharedFltrAlarmClear properties 

Property name

Value

Application name

FILTER

Event ID

2010

Event name

tFilterRadSharedFltrAlarmClear

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.10

Default severity

minor

Message format string

The number of dynamically allocated Radius Shared Filters based on $tFilterType$ $tFilterId$ has dropped below the threshold of $tFilterThresholdReached$

Cause

The tFilterRadSharedFltrAlarmClear notification is generated when the number of Radius Shared Filters that are dynamically created in the system dropped below to the configured low watermark for the indicated filter.

Effect

The system is working properly, and well within its configured bounds.

Recovery

No recovery is needed.

2.21.9. tFilterRadSharedFltrAlarmRaised

tFilterRadSharedFltrAlarmRaised:FILTER
Table 459:  tFilterRadSharedFltrAlarmRaised properties 

Property name

Value

Application name

FILTER

Event ID

2009

Event name

tFilterRadSharedFltrAlarmRaised

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.9

Default severity

minor

Message format string

The number of dynamically allocated Radius Shared Filters based on $tFilterType$ $tFilterId$ has exceeded its threshold of $tFilterThresholdReached$

Cause

The tFilterRadSharedFltrAlarmRaised notification is generated when the number of Radius Shared Filters that are dynamically created in the system increases to the configured high watermark for the indicated filter.

Effect

No direct effect, however the system may run out of filter resources.

Recovery

The way in which dynamically filters are used in the system/network may need to be reconsidered.

2.21.10. tFilterRPActiveDestChangeEvent

tFilterRPActiveDestChangeEvent:FILTER
Table 460:  tFilterRPActiveDestChangeEvent properties 

Property name

Value

Application name

FILTER

Event ID

2017

Event name

tFilterRPActiveDestChangeEvent

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.16

Default severity

minor

Message format string

The active destination of redirect policy $tFilterRedirectPolicy$ has changed to $tFilterRPActiveDestAddr$.

Cause

This notification was triggered because active destination of a redirect policy has changed.

Effect

Traffic hitting filter entries with forward redirect-policy set to this redirect policy will be directed toward the new active destination.

Recovery

No recovery action is required.

2.21.11. tFilterSubInsFltrEntryDropped

tFilterSubInsFltrEntryDropped:FILTER
Table 461:  tFilterSubInsFltrEntryDropped properties 

Property name

Value

Application name

FILTER

Event ID

2006

Event name

tFilterSubInsFltrEntryDropped

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.6

Default severity

warning

Message format string

A request to insert a filter-entry in $tFilterType$ $tFilterId$ for $tFilterSubInsSpaceOwner$ has failed - $tFilterAlarmDescription$

Cause

A request to insert a filter entry failed.

Effect

The filter may not be working as intended.

Recovery

Actions may be taken depending on the reason of why the insertion failed.

2.21.12. tFilterSubInsSpaceAlarmCleared

tFilterSubInsSpaceAlarmCleared:FILTER
Table 462:  tFilterSubInsSpaceAlarmCleared properties 

Property name

Value

Application name

FILTER

Event ID

2005

Event name

tFilterSubInsSpaceAlarmCleared

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.5

Default severity

warning

Message format string

The range of entries reserved in $tFilterType$ $tFilterId$ for $tFilterSubInsSpaceOwner$ has fallen below its configured low watermark level $tFilterThresholdReached$

Cause

A range of entries in the filter has been reserved (via configuration) to be used for inserting entries by the system. If the number of used entries drops below the (configured) low watermark, this notification is sent.

Effect

The system is working properly, and well within its configured bounds.

Recovery

No recovery is needed.

2.21.13. tFilterSubInsSpaceAlarmRaised

tFilterSubInsSpaceAlarmRaised:FILTER
Table 463:  tFilterSubInsSpaceAlarmRaised properties 

Property name

Value

Application name

FILTER

Event ID

2004

Event name

tFilterSubInsSpaceAlarmRaised

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.4

Default severity

warning

Message format string

The range of entries reserved in $tFilterType$ $tFilterId$ for $tFilterSubInsSpaceOwner$ is filled up to its configured high watermark level $tFilterThresholdReached$

Cause

A range of entries in the filter has been reserved (via configuration) to be used for inserting entries by the system. If the number of used entries reaches the (configured) high watermark, this notification is sent.

Effect

If no more entries are available, no more filter entries will be inserted by the system

Recovery

If needed, more entries can be reserved for inserting entries by the system.

2.21.14. tIPFilterPBRPacketsDrop

tIPFilterPBRPacketsDrop:FILTER
Table 464:  tIPFilterPBRPacketsDrop properties 

Property name

Value

Application name

FILTER

Event ID

2001

Event name

tIPFilterPBRPacketsDrop

SNMP notification prefix and OID

TIMETRA-FILTER-MIB.tFilterNotifications.1

Default severity

warning

Message format string

Filter $tIPFilterId$ entry $tIPFilterParamsIndex$ PBR packets dropped on interface $tIPFilterParamsForwardNHInterface$ because $tFilterPBRDropReason$.

Cause

The tIPFilterPlcyBasedRoutingPacketsDrop event is generated either when the configuration of a forwarding action refers to an invalid/unconfigured next-hop or if the active interface goes down operationally in the process of active filtering.

Effect

The tIPFilterPlcyBasedRoutingPacketsDrop event is generated either when the configuration of a forwarding action refers to an invalid/unconfigured next-hop or if the active interface goes down operationally in the process of active filtering.

Recovery

No recovery is required.

2.22. GMPLS

2.22.1. vRtrGmplsLspPathStateChange

vRtrGmplsLspPathStateChange:GMPLS
Table 465:  vRtrGmplsLspPathStateChange properties 

Property name

Value

Application name

GMPLS

Event ID

2001

Event name

vRtrGmplsLspPathStateChange

SNMP notification prefix and OID

TIMETRA-GMPLS-MIB.tmnxGmplsNotifications.1

Default severity

minor

Message format string

Status of $lspPathName$ changed administrative state: $vRtrGmplsLspPathAdminState$, operational state: $vRtrGmplsLspPathOperState$

Cause

A vRtrGmplsLspPathStateChange notification is generated when the operational state of the GMPLS LSP Path changes.

Effect

N/A

Recovery

N/A

2.23. GSMP

2.23.1. tmnxAncpEgrRateMonitorEvent

tmnxAncpEgrRateMonitorEvent:GSMP
Table 466:  tmnxAncpEgrRateMonitorEvent properties 

Property name

Value

Application name

GSMP

Event ID

2003

Event name

tmnxAncpEgrRateMonitorEvent

SNMP notification prefix and OID

TIMETRA-GSMP-MIB.tmnxGsmpNotifications.2

Default severity

warning

Message format string

The Egress rate monitor function for the port identified by $tmnxNotifAncpString$ detects that the scheduler rate $tmnxNotifAncpPlcyActualRate$ has dropped below the value specified by $tmnxNotifAncpPolicyName$

Cause

This notification is generated when the egress rate monitor function for the port identified by tmnxAncpString detects that the scheduler rate has dropped below tmnxAncpPlcyEgrRateMonitor.

Effect

The DLSAM reports (via ANCP) that a subscriber gets less BW than what is currently configured in the system.

Recovery

No recovery is necessary.

2.23.2. tmnxAncpEgrRateMonitorEventL

tmnxAncpEgrRateMonitorEventL:GSMP
Table 467:  tmnxAncpEgrRateMonitorEventL properties 

Property name

Value

Application name

GSMP

Event ID

2004

Event name

tmnxAncpEgrRateMonitorEventL

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

The Egress rate monitor function for the port identified by $tmnxNotifAncpString$ detects that the scheduler rate $tmnxNotifAncpPlcyActualRate$ has dropped below the value specified by $tmnxNotifAncpPolicyName$

Cause

This notification is generated when the egress rate monitor function for the port identified by tmnxAncpString detects that the scheduler rate has dropped below tmnxAncpPlcyEgrRateMonitor.

Effect

The DLSAM reports (via ANCP) that a subscriber gets less BW than what is currently configured in the system.

Recovery

No recovery is necessary.

2.23.3. tmnxAncpIngRateMonitorEvent

tmnxAncpIngRateMonitorEvent:GSMP
Table 468:  tmnxAncpIngRateMonitorEvent properties 

Property name

Value

Application name

GSMP

Event ID

2001

Event name

tmnxAncpIngRateMonitorEvent

SNMP notification prefix and OID

TIMETRA-GSMP-MIB.tmnxGsmpNotifications.1

Default severity

warning

Message format string

The ingress rate monitor function for the port identified by $tmnxNotifAncpString$ detects that the scheduler rate $tmnxNotifAncpPlcyActualRate$ has dropped below the value specified by $tmnxNotifAncpPolicyName$

Cause

This notification is generated whenever the ingress rate monitor function for the port identified by tmnxAncpString detects that the scheduler rate has dropped below tmnxAncpPlcyIngRateMonitor.

Effect

The DLSAM reports (via ANCP) that a subscriber gets less BW then what is currently configured in the system.

Recovery

No recovery is necessary.

2.23.4. tmnxAncpIngRateMonitorEventL

tmnxAncpIngRateMonitorEventL:GSMP
Table 469:  tmnxAncpIngRateMonitorEventL properties 

Property name

Value

Application name

GSMP

Event ID

2002

Event name

tmnxAncpIngRateMonitorEventL

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

The ingress rate monitor function for the port identified by $tmnxNotifAncpString$ detects that the scheduler rate $tmnxNotifAncpPlcyActualRate$ has dropped below the value specified by $tmnxNotifAncpPolicyName$

Cause

This notification is generated when the ingress rate monitor function for the port identified by tmnxAncpString detects that the scheduler rate has dropped below tmnxAncpPlcyIngRateMonitor.

Effect

The DLSAM reports (via ANCP) that a subscriber gets less BW than what is currently configured in the system.

Recovery

No recovery is necessary.

2.23.5. tmnxAncpSesRejected

tmnxAncpSesRejected:GSMP
Table 470:  tmnxAncpSesRejected properties 

Property name

Value

Application name

GSMP

Event ID

2007

Event name

tmnxAncpSesRejected

SNMP notification prefix and OID

TIMETRA-GSMP-MIB.tmnxGsmpNotifications.4

Default severity

warning

Message format string

An incoming ANCP session has been rejected: $tmnxAncpRejectReason$

Cause

The tmnxAncpSesRejected notification is generated when an incoming ANCP session is rejected by the system. Details on why this happened are specified in tmnxAncpRejectReason.

Effect

The ANCP session is rejected.

Recovery

No recovery is necessary.

2.23.6. tmnxAncpShcvDisabledEvent

tmnxAncpShcvDisabledEvent:GSMP
Table 471:  tmnxAncpShcvDisabledEvent properties 

Property name

Value

Application name

GSMP

Event ID

2005

Event name

tmnxAncpShcvDisabledEvent

SNMP notification prefix and OID

TIMETRA-GSMP-MIB.tmnxGsmpNotifications.3

Default severity

warning

Message format string

Subscriber host connectivity verification is disabled for all hosts of the subscriber associated with the $tmnxNotifAncpString$ when a port-down event was received. AncpPolicy: $tmnxNotifAncpPolicyName$

Cause

This notification is generated whenever the SHCV (Subscriber Host Connectivity Verification) is disabled for all hosts of the subscriber associated with the tmnxAncpString when a port-down event was received for the tmnxAncpString.

Effect

The SHCV function is disabled.

Recovery

No recovery is necessary.

2.23.7. tmnxAncpShcvDisabledEventL

tmnxAncpShcvDisabledEventL:GSMP
Table 472:  tmnxAncpShcvDisabledEventL properties 

Property name

Value

Application name

GSMP

Event ID

2006

Event name

tmnxAncpShcvDisabledEventL

SNMP notification prefix and OID

N/A

Default severity

warning

Message format string

Subscriber host connectivity verification is disabled for all hosts of the subscriber associated with the $tmnxNotifAncpString$ when a port-down event was received. AncpPolicy: $tmnxNotifAncpPolicyName$

Cause

This notification is generated whenever the SHCV (Subscriber Host Connectivity Verification) is disabled for all hosts of the subscriber associated with the tmnxAncpString when a port-down event was received for the tmnxAncpString."

Effect

The SHCV function is disabled.

Recovery

No recovery is necessary.

2.23.8. tmnxAncpStringRejected

tmnxAncpStringRejected:GSMP
Table 473:  tmnxAncpStringRejected properties 

Property name

Value

Application name

GSMP

Event ID

2008

Event name

tmnxAncpStringRejected

SNMP notification prefix and OID

TIMETRA-GSMP-MIB.tmnxGsmpNotifications.5

Default severity

warning

Message format string

An incoming ANCP string rejected: $tmnxAncpRejectReason$

Cause

The tmnxAncpStringRejected notification is sent when an incoming ANCP string received on an established ANCP session is rejected by the system. Details on why this happened are specified in tmnxAncpRejectReason.

Effect

The ANCP string is rejected.

Recovery

No recovery is necessary.

2.24. IGH

2.24.1. tmnxIfGroupHandlerProtoOprChange

tmnxIfGroupHandlerProtoOprChange:IGH
Table 474:  tmnxIfGroupHandlerProtoOprChange properties 

Property name

Value

Application name

IGH

Event ID

2001

Event name

tmnxIfGroupHandlerProtoOprChange

SNMP notification prefix and OID

TIMETRA-IF-GROUP-HANDLER-MIB.tmnxIfGroupNotifications.1

Default severity

minor

Message format string

IGH $tmnxIfGroupHandlerIndex$ protocol $tmnxIfGroupHdlrProtoIndex$ changed to state $tmnxIfGroupHdlrProtoStatus$ - admin status: $tmnxIfGroupHandlerAdminStatus$, active-links: $tmnxIfGroupHdlrProtoActLinks$, threshold: $tmnxIfGroupHandlerThreshold$

Cause

N/A

Effect

N/A

Recovery

N/A

2.24.2. tmnxIfGroupHdlrMbrProtoOprChange

tmnxIfGroupHdlrMbrProtoOprChange:IGH
Table 475:  tmnxIfGroupHdlrMbrProtoOprChange properties 

Property name

Value

Application name

IGH

Event ID

2002

Event name

tmnxIfGroupHdlrMbrProtoOprChange

SNMP notification prefix and OID

TIMETRA-IF-GROUP-HANDLER-MIB.tmnxIfGroupNotifications.2

Default severity

minor

Message format string

IGH $tmnxIfGroupHandlerIndex$ Member $tmnxPortPortID$ protocol $tmnxIfGroupHdlrMemberProtoIndex$ changed to state $tmnxIfGroupHdlrMemberProtoStatus$

Cause

N/A

Effect

N/A

Recovery

N/A

2.25. IGMP

2.25.1. vRtrIgmpGrpIfSapCModeRxQueryMism

vRtrIgmpGrpIfSapCModeRxQueryMism:IGMP
Table 476:  vRtrIgmpGrpIfSapCModeRxQueryMism properties 

Property name

Value

Application name

IGMP

Event ID

2015

Event name

vRtrIgmpGrpIfSapCModeRxQueryMism

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.15

Default severity

minor

Message format string

Mismatch between compatible mode ($vRtrIgmpGrpIfSapOperVersion$) for SAP $sapPortId$ on interface $vRtrGrpIfIndex$, IGMP instance $vRtrID$, and the IGMP query version ($vRtrIgmpNotifyQueryVersion$) received

Cause

A vRtrIgmpGrpIfSapCModeRxQueryMism notification is generated when there is a mismatch between the compatible mode of the IGMP SAP and the version of the received query. It is generated when the SAP is in IGMPv1 compatible mode but it receives a IGMPv2 or IGMPv3 Query. It is also generated when the compatibility mode of the SAP is IGMPv2 but the query received is IGMPv3. sapPortId and sapEncapValue will identify the SAP on which the query is received. vRtrIgmpGrpIfSapOperVersion will indicate the compatibility mode of the SAP and vRtrIgmpNotifyQueryVersion will contain the version of the received query.

Effect

N/A

Recovery

N/A

2.25.2. vRtrIgmpGrpIfSapMaxGrpsLimExceed

vRtrIgmpGrpIfSapMaxGrpsLimExceed:IGMP
Table 477:  vRtrIgmpGrpIfSapMaxGrpsLimExceed properties 

Property name

Value

Application name

IGMP

Event ID

2012

Event name

vRtrIgmpGrpIfSapMaxGrpsLimExceed

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.12

Default severity

minor

Message format string

The number of groups for SAP $sapPortId$ on interface $vRtrGrpIfIndex$, IGMP instance $vRtrID$, has exceeded the maximum limit of $vRtrIgmpGrpIfSapMaxGroups$

Cause

The vRtrIgmpGrpIfSapMaxGrpsLimExceed event is generated when an attempt is made to configure a group when vRtrIgmpGrpIfSapGroupCount, the number of groups configured on the SAP, is equal to vRtrIgmpGrpIfSapMaxGroups, the maximum number of groups supported on the system.

Effect

N/A

Recovery

N/A

2.25.3. vRtrIgmpGrpIfSapMaxGrpSrcLimExcd

vRtrIgmpGrpIfSapMaxGrpSrcLimExcd:IGMP
Table 478:  vRtrIgmpGrpIfSapMaxGrpSrcLimExcd properties 

Property name

Value

Application name

IGMP

Event ID

2019

Event name

vRtrIgmpGrpIfSapMaxGrpSrcLimExcd

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.19

Default severity

minor

Message format string

The number of groups or sources for SAP $sapPortId$ on interface $vRtrGrpIfIndex$, IGMP instance $vRtrID$, has exceeded the maximum limit of $vRtrIgmpGrpIfSapMaxSources$

Cause

The vRtrIgmpGrpIfSapMaxGrpSrcLimExcd event is generated when an attempt is made to configure a group source for a group when the number of group sources is equal to vRtrIgmpGrpIfSapMaxGrpSources, the maximum number of group sources per group supported on the SAP.

Effect

N/A

Recovery

N/A

2.25.4. vRtrIgmpGrpIfSapMaxSrcsLimExceed

vRtrIgmpGrpIfSapMaxSrcsLimExceed:IGMP
Table 479:  vRtrIgmpGrpIfSapMaxSrcsLimExceed properties 

Property name

Value

Application name

IGMP

Event ID

2013

Event name

vRtrIgmpGrpIfSapMaxSrcsLimExceed

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.13

Default severity

minor

Message format string

The number of sources for SAP $sapPortId$ on interface $vRtrGrpIfIndex$, IGMP instance $vRtrID$, has exceeded the maximum limit of $vRtrIgmpGrpIfSapMaxSources$

Cause

The vRtrIgmpGrpIfSapMaxSrcsLimExceed event is generated when an attempt is made to configure a source for a group when the number of sources for this group is equal to vRtrIgmpGrpIfSapMaxSources, the maximum number of sources per group supported on the system.

Effect

N/A

Recovery

N/A

2.25.5. vRtrIgmpGrpIfSapMcacPlcyDropped

vRtrIgmpGrpIfSapMcacPlcyDropped:IGMP
Table 480:  vRtrIgmpGrpIfSapMcacPlcyDropped properties 

Property name

Value

Application name

IGMP

Event ID

2014

Event name

vRtrIgmpGrpIfSapMcacPlcyDropped

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.14

Default severity

minor

Message format string

Group $vRtrIgmpNotifyGrpAddr$ is dropped because of MCAC policy $vRtrIgmpNotifyMcacPolicyName$ for SAP $sapPortId$ on interface $vRtrGrpIfIndex$, IGMP instance $vRtrID$

Cause

The vRtrIgmpGrpIfSapMcacPlcyDropped event is generated when an IGMP group is dropped on a given SAP because of applying a multicast CAC policy given by vRtrIgmpNotifyMcacPolicyName.

Effect

N/A

Recovery

N/A

2.25.6. vRtrIgmpGrpIfSapRxQueryVerMism

vRtrIgmpGrpIfSapRxQueryVerMism:IGMP
Table 481:  vRtrIgmpGrpIfSapRxQueryVerMism properties 

Property name

Value

Application name

IGMP

Event ID

2016

Event name

vRtrIgmpGrpIfSapRxQueryVerMism

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.16

Default severity

minor

Message format string

IGMPv$vRtrIgmpNotifyQueryVersion$ query received for SAP $sapPortId$ on interface $vRtrGrpIfIndex$, IGMP instance $vRtrID$, configured as IGMPv$vRtrIgmpGrpIfSapAdminVersion$

Cause

A vRtrIgmpGrpIfSapRxQueryVerMism notification is generated when the IGMP host SAP is configured as IGMPv3 but receives a IGMPv1 Query or IGMPv2 General Query on the host. sapPortId and sapEncapValue will identify the SAP on which the query is received. vRtrIgmpGrpIfSapAdminVersion will contain the configured version of the SAP and vRtrIgmpNotifyQueryVersion will contain the version of the received query.

Effect

N/A

Recovery

N/A

2.25.7. vRtrIgmpHostCModeRxQueryMismatch

vRtrIgmpHostCModeRxQueryMismatch:IGMP
Table 482:  vRtrIgmpHostCModeRxQueryMismatch properties 

Property name

Value

Application name

IGMP

Event ID

2008

Event name

vRtrIgmpHostCModeRxQueryMismatch

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.8

Default severity

minor

Message format string

TODO

Cause

N/A

Effect

N/A

Recovery

N/A

2.25.8. vRtrIgmpHostInstantiationFail

vRtrIgmpHostInstantiationFail:IGMP
Table 483:  vRtrIgmpHostInstantiationFail properties 

Property name

Value

Application name

IGMP

Event ID

2005

Event name

vRtrIgmpHostInstantiationFail

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.5

Default severity

minor

Message format string

Could not start IGMP on $vRtrIgmpGrpIfHostLastChangeTime$ - $vRtrIgmpNotifyDescription$

Cause

The vRtrIgmpHostInstantiationFail event is generated when a host is eligible for running IGMP, but IGMP cannot be started on the host.

Effect

None.

Recovery

Contact Nokia customer service.

2.25.9. vRtrIgmpHostMaxGrpsLimitExceeded

vRtrIgmpHostMaxGrpsLimitExceeded:IGMP
Table 484:  vRtrIgmpHostMaxGrpsLimitExceeded properties 

Property name

Value

Application name

IGMP

Event ID

2006

Event name

vRtrIgmpHostMaxGrpsLimitExceeded

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.6

Default severity

minor

Message format string

Could not start IGMP on $vRtrIgmpGrpIfHostLastChangeTime$ - $vRtrIgmpNotifyDescription$

Cause

The vRtrIgmpMaxGrpsLimitExceeded event is generated when an attempt is made to configure a group when vRtrIgmpHostGroupCount, the number of groups configured on the PIM interface, is equal to vRtrIgmpHostMaxGroups, the maximum number of groups supported on the system.

Effect

None.

Recovery

Contact Nokia Customer Service.

2.25.10. vRtrIgmpHostMaxGrpSrcsLimitExcd

vRtrIgmpHostMaxGrpSrcsLimitExcd:IGMP
Table 485:  vRtrIgmpHostMaxGrpSrcsLimitExcd properties 

Property name

Value

Application name

IGMP

Event ID

2017

Event name

vRtrIgmpHostMaxGrpSrcsLimitExcd

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.17

Default severity

minor

Message format string

The number of groups or sources configured has exceeded the maximum limit of $vRtrIgmpHostMaxSources$

Cause

The vRtrIgmpHostMaxGrpSrcsLimitExcd event is generated when an attempt is made to configure a source for a group when the number of group sources is equal to vRtrIgmpHostMaxGrpSources, the maximum number of group sources per group supported on the host.

Effect

N/A

Recovery

N/A

2.25.11. vRtrIgmpHostMaxSrcsLimitExceeded

vRtrIgmpHostMaxSrcsLimitExceeded:IGMP
Table 486:  vRtrIgmpHostMaxSrcsLimitExceeded properties 

Property name

Value

Application name

IGMP

Event ID

2010

Event name

vRtrIgmpHostMaxSrcsLimitExceeded

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.10

Default severity

minor

Message format string

The number of sources configured for a group has exceeded the maximum limit of $vRtrIgmpHostMaxSources$

Cause

The vRtrIgmpHostMaxSrcsLimitExceeded event is generated when an attempt is made to configure a source for a group when the number of sources for this group is equal to vRtrIgmpHostMaxSources, the maximum number of sources per group supported on the system.

Effect

N/A

Recovery

N/A

2.25.12. vRtrIgmpHostMcacPlcyDropped

vRtrIgmpHostMcacPlcyDropped:IGMP
Table 487:  vRtrIgmpHostMcacPlcyDropped properties 

Property name

Value

Application name

IGMP

Event ID

2007

Event name

vRtrIgmpHostMcacPlcyDropped

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.7

Default severity

minor

Message format string

TODO

Cause

N/A

Effect

N/A

Recovery

N/A

2.25.13. vRtrIgmpHostQryIntervalConflict

vRtrIgmpHostQryIntervalConflict:IGMP
Table 488:  vRtrIgmpHostQryIntervalConflict properties 

Property name

Value

Application name

IGMP

Event ID

2020

Event name

vRtrIgmpHostQryIntervalConflict

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.20

Default severity

minor

Message format string

TODO

Cause

The vRtrIgmpHostQryIntervalConflict event is generated when one of the IGMP-policy query intervals violates restrictions, we fall back to the node query intervals.

Effect

N/A

Recovery

N/A

2.25.14. vRtrIgmpHostRxQueryVerMismatch

vRtrIgmpHostRxQueryVerMismatch:IGMP
Table 489:  vRtrIgmpHostRxQueryVerMismatch properties 

Property name

Value

Application name

IGMP

Event ID

2009

Event name

vRtrIgmpHostRxQueryVerMismatch

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.9

Default severity

minor

Message format string

TODO

Cause

N/A

Effect

N/A

Recovery

N/A

2.25.15. vRtrIgmpIfCModeRxQueryMismatch

vRtrIgmpIfCModeRxQueryMismatch:IGMP
Table 490:  vRtrIgmpIfCModeRxQueryMismatch properties 

Property name

Value

Application name

IGMP

Event ID

2002

Event name

vRtrIgmpIfCModeRxQueryMismatch

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.2

Default severity

warning

Message format string

Mismatch between the interface $vRtrIfIndex$ compatible mode($vRtrIgmpIfOperVersion$) and the version of the IGMP query (version $vRtrIgmpNotifyQueryVersion$) received on the interface

Cause

This notification is generated when there is a mismatch between the compatibility mode of the interface and the version of the IGMP query received on the interface.

Effect

The query will be ignored.

Recovery

No recovery is necessary.

2.25.16. vRtrIgmpIfRxQueryVerMismatch

vRtrIgmpIfRxQueryVerMismatch:IGMP
Table 491:  vRtrIgmpIfRxQueryVerMismatch properties 

Property name

Value

Application name

IGMP

Event ID

2001

Event name

vRtrIgmpIfRxQueryVerMismatch

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.1

Default severity

warning

Message format string

IGMPv$vRtrIgmpNotifyQueryVersion$ query received on interface $vRtrIfIndex$ configured as IGMPv$vRtrIgmpIfAdminVersion$

Cause

The event is generated when the router receives IGMPv1 or IGMPv2 query on an interface which is configured as IGMPv3.

Effect

IGMP interface transitions into IGMPv1 or IGMPv2 compatibility mode.

Recovery

No recovery is necessary.

2.25.17. vRtrIgmpMaxGrpsLimitExceeded

vRtrIgmpMaxGrpsLimitExceeded:IGMP
Table 492:  vRtrIgmpMaxGrpsLimitExceeded properties 

Property name

Value

Application name

IGMP

Event ID

2003

Event name

vRtrIgmpMaxGrpsLimitExceeded

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.3

Default severity

warning

Message format string

The number of groups configured on the interface $ifName$ has exceeded the maximum limit of $vRtrIgmpIfMaxGroups$

Cause

This notification is generated when the number of groups configured on the interface exceeds the maximum number of groups supported on the system.

Effect

None.

Recovery

Contact Nokia Customer Service.

2.25.18. vRtrIgmpMaxGrpSrcsLimitExceeded

vRtrIgmpMaxGrpSrcsLimitExceeded:IGMP
Table 493:  vRtrIgmpMaxGrpSrcsLimitExceeded properties 

Property name

Value

Application name

IGMP

Event ID

2018

Event name

vRtrIgmpMaxGrpSrcsLimitExceeded

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.18

Default severity

minor

Message format string

The number of groups or sources configured has exceeded the maximum limit of $vRtrIgmpIfMaxSources$

Cause

The vRtrIgmpMaxGrpSrcsLimitExceeded event is generated when an attempt is made to configure a group source for a group when the number of group sources is equal to vRtrIgmpIfMaxGrpSources, the maximum number of group sources per group supported on the interface.

Effect

N/A

Recovery

N/A

2.25.19. vRtrIgmpMaxSrcsLimitExceeded

vRtrIgmpMaxSrcsLimitExceeded:IGMP
Table 494:  vRtrIgmpMaxSrcsLimitExceeded properties 

Property name

Value

Application name

IGMP

Event ID

2011

Event name

vRtrIgmpMaxSrcsLimitExceeded

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.11

Default severity

minor

Message format string

The number of sources configured for a group has exceeded the maximum limit of $vRtrIgmpIfMaxSources$

Cause

The vRtrIgmpMaxSrcsLimitExceeded event is generated when an attempt is made to configure a source for a group when the number of sources for this group is equal to vRtrIgmpHostMaxSources, the maximum number of sources per group supported on the system.

Effect

N/A

Recovery

N/A

2.25.20. vRtrIgmpMcacPlcyDropped

vRtrIgmpMcacPlcyDropped:IGMP
Table 495:  vRtrIgmpMcacPlcyDropped properties 

Property name

Value

Application name

IGMP

Event ID

2004

Event name

vRtrIgmpMcacPlcyDropped

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.4

Default severity

warning

Message format string

Group $vRtrIgmpNotifyGrpAddress$ is dropped because of multicast CAC policy $vRtrIgmpIfMcacPolicyName$ on interface $ifName$ IGMP instance $vRtrID$

Cause

The vRtrIgmpMcacPlcyDropped event is generated when an IGMP group is dropped on a given interface because of applying a multicast CAC policy given by vRtrIgmpIfMcacPolicyName

Effect

None.

Recovery

The Multicast CAC policy must be modified to allow additional groups.

2.25.21. vRtrIgmpNotifyNumOfIPsecIfHighWm

vRtrIgmpNotifyNumOfIPsecIfHighWm:IGMP
Table 496:  vRtrIgmpNotifyNumOfIPsecIfHighWm properties 

Property name

Value

Application name

IGMP

Event ID

2022

Event name

vRtrIgmpNotifyNumOfIPsecIfHighWm

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.22

Default severity

minor

Message format string

The number of IPsec multicast interfaces is $vRtrIgmpNotifyNumOfIPsecIf$ and has almost reached the maximum value $vRtrIgmpNotifyMaxNumOfIPsecIf$.

Cause

A vRtrIgmpNotifyNumOfIPsecIfHighWm notification is generated when the number of IPsec interfaces has almost reached the maximum value.

Effect

The system may stop accepting new IPsec multicast interfaces shortly.

Recovery

Use fewer IPsec multicast interfaces.

2.25.22. vRtrIgmpNotifyNumOfIPsecIfLowWm

vRtrIgmpNotifyNumOfIPsecIfLowWm:IGMP
Table 497:  vRtrIgmpNotifyNumOfIPsecIfLowWm properties 

Property name

Value

Application name

IGMP

Event ID

2021

Event name

vRtrIgmpNotifyNumOfIPsecIfLowWm

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.21

Default severity

minor

Message format string

The number of IPsec multicast interfaces is $vRtrIgmpNotifyNumOfIPsecIf$ and has dropped back to the low watermark.

Cause

A vRtrIgmpNotifyNumOfIPsecIfLowWm notification is generated when the number of IPsec interfaces has dropped back to the low watermark.

Effect

The system accepts new IPsec multicast interfaces.

Recovery

There is no recovery required for this notification.

2.25.23. vRtrIgmpNotifyNumOfIPsecIfMaxRch

vRtrIgmpNotifyNumOfIPsecIfMaxRch:IGMP
Table 498:  vRtrIgmpNotifyNumOfIPsecIfMaxRch properties 

Property name

Value

Application name

IGMP

Event ID

2023

Event name

vRtrIgmpNotifyNumOfIPsecIfMaxRch

SNMP notification prefix and OID

TIMETRA-IGMP-MIB.vRtrIgmpNotifications.23

Default severity

minor

Message format string

The number of IPsec multicast interfaces has reached its maximum value $vRtrIgmpNotifyMaxNumOfIPsecIf$.

Cause

A vRtrIgmpNotifyNumOfIPsecIfMaxRch notification is generated when the number of IPsec interfaces has reached the maximum value.

Effect

The system stops accepting new IPsec multicast interfaces.

Recovery

Delete IPsec multicast interfaces.

2.26. IGMP_SNOOPING

2.26.1. eMplsIgmpSnpgMfibFailure

eMplsIgmpSnpgMfibFailure:IGMP_SNOOPING
Table 499:  eMplsIgmpSnpgMfibFailure properties 

Property name

Value

Application name

IGMP_SNOOPING

Event ID

2010

Event name

eMplsIgmpSnpgMfibFailure

SNMP notification prefix and OID

ALCATEL-IGMP-SNOOPING-MIB.alxIgmpSnpgEMplsNotifications.1

Default severity

minor

Message format string

Failing to store an entry in the MFIB table for service $svcId

Cause

The eMplsIgmpSnpgMfibFailure notification is generated when an evpn-mpls binding fails to store an entry in the MFIB table. To resolve this, try to increase the svcTlsMfibTableSize or remove another entry from the MFIB table for this service.

Effect

N/A

Recovery

N/A

2.26.2. sapIgmpSnpgGrpLimitExceeded

sapIgmpSnpgGrpLimitExceeded:IGMP_SNOOPING
Table 500:  sapIgmpSnpgGrpLimitExceeded properties 

Property name

Value

Application name

IGMP_SNOOPING

Event ID

2001

Event name

sapIgmpSnpgGrpLimitExceeded

SNMP notification prefix and OID

ALCATEL-IGMP-SNOOPING-MIB.alxIgmpSnpgSapNotifications.1

Default severity

warning

Message format string

The number of groups on SAP $sapEncapValue$ in service $svcId$ has exceeded the maximum limit of $sapIgmpSnpgCfgMaxNbrGrps$ - Dropping group $alxIgmpSnpgGroupAddress$

Cause

The sapIgmpSnpgGrpLimitExceeded notification is generated when an IGMP group is dropped on a given SAP because a user configurable upper limit given by sapIgmpSnpgCfgMaxNbrGrps is reached.

Effect

None.

Recovery

Investigate the cause of the excessive groups.

2.26.3. sapIgmpSnpgGrpSrcLimitExceeded

sapIgmpSnpgGrpSrcLimitExceeded:IGMP_SNOOPING
Table 501:  sapIgmpSnpgGrpSrcLimitExceeded properties 

Property name

Value

Application name

IGMP_SNOOPING

Event ID

2009

Event name

sapIgmpSnpgGrpSrcLimitExceeded

SNMP notification prefix and OID

ALCATEL-IGMP-SNOOPING-MIB.alxIgmpSnpgSapNotifications.5

Default severity

minor

Message format string

The number of groups or sources on SAP $sapEncapValue$ in service $svcId$ has exceeded the maximum limit of $sapIgmpSnpgCfgMaxNbrSrcs$ - Dropping source $alxIgmpSnpgSourceAddress$ for group $alxIgmpSnpgGroupAddress$

Cause

The sapIgmpSnpgGrpSrcLimitExceeded notification is generated when an IGMP group or source is dropped dropped on a given SAP because a user configurable upper limit given by sapIgmpSnpgCfgMaxNbrGrpSrcs is reached.

Effect

The specified S,G was not added.

Recovery

Investigate the cause of the excessive sources.

2.26.4. sapIgmpSnpgMcacPlcyDropped

sapIgmpSnpgMcacPlcyDropped:IGMP_SNOOPING
Table 502:  sapIgmpSnpgMcacPlcyDropped properties 

Property name

Value

Application name

IGMP_SNOOPING

Event ID

2002

Event name

sapIgmpSnpgMcacPlcyDropped

SNMP notification prefix and OID

ALCATEL-IGMP-SNOOPING-MIB.alxIgmpSnpgSapNotifications.2

Default severity

warning

Message format string

Group $alxIgmpSnpgGroupAddress$ is dropped because of multicast CAC policy $sapIgmpSnpgCfgMcacPolicyName$ on SAP $sapEncapValue$ in service $svcId$

Cause

The sapIgmpSnpgMcacPlcyDropped notification is generated when an IGMP group is dropped on a given SAP because of applying a multicast CAC policy given by sapIgmpSnpgCfgMcacPolicyName.

Effect

None.

Recovery

Investigate the cause of the excessive groups.

2.26.5. sapIgmpSnpgMcsFailure

sapIgmpSnpgMcsFailure:IGMP_SNOOPING
Table 503:  sapIgmpSnpgMcsFailure properties 

Property name

Value

Application name

IGMP_SNOOPING

Event ID

2005

Event name

sapIgmpSnpgMcsFailure

SNMP notification prefix and OID

ALCATEL-IGMP-SNOOPING-MIB.alxIgmpSnpgSapNotifications.3

Default severity

warning

Message format string

Group $alxIgmpSnpgGroupAddress$ on SAP $sapEncapValue$ in service $svcId$ could not be synced to MCS - $alxIgmpSnpgMcsFailureReason$

Cause

The sapIgmpSnpgMcsFailure notification is generated when an IGMP group on a given SAP could not be synced to the MCS (multi-chassis synchronization) database.

Effect

Synchronization between chassis has been lost.

Recovery

No recovery is required.

2.26.6. sapIgmpSnpgSrcLimitExceeded

sapIgmpSnpgSrcLimitExceeded:IGMP_SNOOPING
Table 504:  sapIgmpSnpgSrcLimitExceeded properties 

Property name

Value

Application name

IGMP_SNOOPING

Event ID

2006

Event name

sapIgmpSnpgSrcLimitExceeded

SNMP notification prefix and OID

ALCATEL-IGMP-SNOOPING-MIB.alxIgmpSnpgSapNotifications.1

Default severity

warning

Message format string

The number of sources for group $alxIgmpSnpgGroupAddress$ on SAP $sapEncapValue$ in service $svcId$ has exceeded the maximum limit of $sapIgmpSnpgCfgMaxNbrSrcs$ - Dropping source $alxIgmpSnpgSourceAddress$ for group $alxIgmpSnpgGroupAddress$

Cause

The sapIgmpSnpgSrcLimitExceeded notification is generated when an IGMP source is dropped on a given SAP because a user configurable upper limit given by sapIgmpSnpgCfgMaxNbrSrcs is reached.

Effect

The specified S,G was not added.

Recovery

Investigate the cause of the excessive sources.

2.26.7. sdpBndIgmpSnpgGrpLimitExceeded

sdpBndIgmpSnpgGrpLimitExceeded:IGMP_SNOOPING
Table 505:  sdpBndIgmpSnpgGrpLimitExceeded properties 

Property name

Value

Application name

IGMP_SNOOPING

Event ID

2003

Event name

sdpBndIgmpSnpgGrpLimitExceeded

SNMP notification prefix and OID

ALCATEL-IGMP-SNOOPING-MIB.alxIgmpSnpgSdpBndNotifications.1

Default severity

warning

Message format string

The number of groups on SDP Bind $sdpBindId$ in service $svcId$ has exceeded the maximum limit of $sdpBndIgmpSnpgCfgMaxNbrGrps$ - Dropping group $alxIgmpSnpgGroupAddress$

Cause

The sdpBndIgmpSnpgGrpLimitExceeded notification is generated when an IGMP group is dropped on a given SDP bind because a user configurable upper limit given by sdpBndIgmpSnpgCfgMaxNbrGrps is reached.

Effect

None.

Recovery

Investigate the cause of the excessive groups.

2.26.8. sdpBndIgmpSnpgGrpSrcLimitExceed

sdpBndIgmpSnpgGrpSrcLimitExceed:IGMP_SNOOPING
Table 506:  sdpBndIgmpSnpgGrpSrcLimitExceed properties 

Property name

Value

Application name

IGMP_SNOOPING

Event ID

2008

Event name

sdpBndIgmpSnpgGrpSrcLimitExceed

SNMP notification prefix and OID

ALCATEL-IGMP-SNOOPING-MIB.alxIgmpSnpgSdpBndNotifications.4

Default severity

minor

Message format string

The number of groups or sources on SDP Bind $sdpBindId$ in service $svcId$ has exceeded the maximum limit of $sdpBndIgmpSnpgCfgMaxNbrSrcs$ - Dropping source $alxIgmpSnpgSourceAddress$ for group $alxIgmpSnpgGroupAddress$

Cause

The sdpBndIgmpSnpgGrpSrcLimitExceed notification is generated when an IGMP group or source is dropped on a given SDP Bind because a user configurable upper limit given by sdpBndIgmpSnpgCfgMaxNbrGrpSrcs is reached.

Effect

The specified S,G was not added.

Recovery

Investigate the cause of the excessive sources.

2.26.9. sdpBndIgmpSnpgMcacPlcyDropped

sdpBndIgmpSnpgMcacPlcyDropped:IGMP_SNOOPING
Table 507:  sdpBndIgmpSnpgMcacPlcyDropped properties 

Property name

Value

Application name

IGMP_SNOOPING

Event ID

2004

Event name

sdpBndIgmpSnpgMcacPlcyDropped

SNMP notification prefix and OID

ALCATEL-IGMP-SNOOPING-MIB.alxIgmpSnpgSdpBndNotifications.2

Default severity

warning

Message format string

Group $alxIgmpSnpgGroupAddress$ is dropped because of multicast CAC policy $sdpBndIgmpSnpgCfgMcacPolicyName$ on SDP Bind $sdpBindId$ in service $svcId$

Cause

The sdpBndIgmpSnpgMcacPlcyDropped notification is generated when an IGMP group is dropped on a given SDP bind because of applying a multicast CAC policy given by sdpBndIgmpSnpgCfgMcacPolicyName.

Effect

None.

Recovery

Investigate the cause of the excessive groups.

2.26.10. sdpBndIgmpSnpgSrcLimitExceeded

sdpBndIgmpSnpgSrcLimitExceeded:IGMP_SNOOPING
Table 508:  sdpBndIgmpSnpgSrcLimitExceeded properties 

Property name

Value

Application name

IGMP_SNOOPING

Event ID

2007

Event name

sdpBndIgmpSnpgSrcLimitExceeded

SNMP notification prefix and OID

ALCATEL-IGMP-SNOOPING-MIB.alxIgmpSnpgSdpBndNotifications.1

Default severity

warning

Message format string

The number of sources for group $alxIgmpSnpgGroupAddress$ on SDP Bind $sdpBindId$ in service $svcId$ has exceeded the maximum limit of $sdpBndIgmpSnpgCfgMaxNbrSrcs$ - Dropping source $alxIgmpSnpgSourceAddress$ for group $alxIgmpSnpgGroupAddress$

Cause

The sdpBndIgmpSnpgSrcLimitExceeded notification is generated when an IGMP source is dropped on a given SDP Bind because a user configurable upper limit given by sdpBndIgmpSnpgCfgMaxNbrSrcs is reached.

Effect

The specified S,G was not added.

Recovery

Investigate the cause of the excessive sources.

2.27. IP

2.27.1. clearRTMError

clearRTMError:IP
Table 509:  clearRTMError properties 

Property name

Value

Application name

IP

Event ID

2001

Event name

clearRTMError

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

Could not flush IOMs $iomList$ because 'clear' failed

Cause

A failure has occurred with communications with the associated IOM.

Effect

N/A

Recovery

Contact the Nokia Customer Service.

2.27.2. fibAddFailed

fibAddFailed:IP
Table 510:  fibAddFailed properties 

Property name

Value

Application name

IP

Event ID

2005

Event name

fibAddFailed

SNMP notification prefix and OID

N/A

Default severity

major

Message format string

FIB add failed for VRF $vRtrID$ prefix $prefix$

Cause

FIB resources have been exhausted.

Effect

Additional routing information can not be added to the forwarding table.

Recovery

Further investigation is required to determine why the IP route table entry could not be added.

2.27.3. ipAnyDuplicateAddress

ipAnyDuplicateAddress:IP
Table 511:  ipAnyDuplicateAddress properties 

Property name

Value

Application name

IP

Event ID

2010

Event name

ipAnyDuplicateAddress

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

State changed from $stateFrom$ to $stateTo$ for IP address $ipAddress$ sent from ethernet address $macAddress$ for interface $intName$

Cause

Another system on the subnet has the same IP address.

Effect

Communications to or from systems with duplicate IP addresses may not be possible.

Recovery

The duplicate IP address should be removed.

2.27.4. ipArpBadInterface

ipArpBadInterface:IP
Table 512:  ipArpBadInterface properties 

Property name

Value

Application name

IP

Event ID

2007

Event name

ipArpBadInterface

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

ARP request for $ipAddress$ received on $interface1$, expected $interface2$

Cause

ARP request received on the wrong interface.

Effect

Communications to or from systems with duplicate IP addresses may not be possible.

Recovery

Further investigation is required, a possible L2 loop could exist.

2.27.5. ipArpDuplicateIpAddress

ipArpDuplicateIpAddress:IP
Table 513:  ipArpDuplicateIpAddress properties 

Property name

Value

Application name

IP

Event ID

2008

Event name

ipArpDuplicateIpAddress

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

duplicate IP address $ipAddress$ with $macAddress$ on interface $interface$

Cause

Another system on the subnet has the same IP address.

Effect

Communications to or from systems with duplicate IP addresses may not be possible.

Recovery

Duplicate IP addresses must be corrected by changing the IP address on one of the systems.

2.27.6. ipArpDuplicateMacAddress

ipArpDuplicateMacAddress:IP
Table 514:  ipArpDuplicateMacAddress properties 

Property name

Value

Application name

IP

Event ID

2009

Event name

ipArpDuplicateMacAddress

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

duplicate MAC address $macAddress$ with $ipAddress$ on interface $interface$

Cause

Another system or host on the ethernet segment has the same ethernet MAC address.

Effect

Communications to or from systems with duplicate MAC addresses may not be possible.

Recovery

The duplicate MAC address should be removed.

2.27.7. ipArpInfoOverwritten

ipArpInfoOverwritten:IP
Table 515:  ipArpInfoOverwritten properties 

Property name

Value

Application name

IP

Event ID

2004

Event name

ipArpInfoOverwritten

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

ARP information overwritten for $ipAddress$ by $macAddress$

Cause

ARP information has been updated.

Effect

None.

Recovery

No recovery is required.

2.27.8. ipDuplicateAddress

ipDuplicateAddress:IP
Table 516:  ipDuplicateAddress properties 

Property name

Value

Application name

IP

Event ID

2003

Event name

ipDuplicateAddress

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

Duplicate IP address $ipAddress$ sent from ethernet address $macAddress$

Cause

Another system or host on the ethernet subnet has the same IP address.

Effect

Communications to or from systems with duplicate IP addresses may not be possible.

Recovery

Duplicate IP addresses must be corrected by changing the IP address on one of the systems.

2.27.9. ipEtherBroadcast

ipEtherBroadcast:IP
Table 517:  ipEtherBroadcast properties 

Property name

Value

Application name

IP

Event ID

2002

Event name

ipEtherBroadcast

SNMP notification prefix and OID

N/A

Default severity

minor

Message format string

Invalid ethernet (broadcast) address for IP address $ipAddress$

Cause

Misconfigured or misbehaving host is sending the incorrect MAC address.

Effect

Communications to or from systems with invalid MAC addresses may not be possible.

Recovery

Further investigation required on the host.

2.27.10. qosNetworkPolicyMallocFailed

qosNetworkPolicyMallocFailed:IP
Table 518:  qosNetworkPolicyMallocFailed properties 

Property name

Value

Application name

IP

Event ID

2006

Event name

qosNetworkPolicyMallocFailed

SNMP notification prefix and OID

N/A

Default severity

major

Message format string

Qos Network Policy malloc failed in $function$

Cause

QoS Network policies have been exhausted.

Effect

Additional QoS Network policies can not be configured.

Recovery

Contact the Nokia Customer Service.

2.28. IPSEC

2.28.1. tIPsecBfdIntfSessStateChgd

tIPsecBfdIntfSessStateChgd:IPSEC
Table 519:  tIPsecBfdIntfSessStateChgd properties 

Property name

Value

Application name

IPSEC

Event ID

2003

Event name

tIPsecBfdIntfSessStateChgd

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.3

Default severity

minor

Message format string

BFD session on service $tIPsecNotifBfdIntfSvcId$ interface $tIPsecNotifBfdIntfIfName$ to peer $tIPsecNotifBfdIntfDestIp$ changed state to $tIPsecNotifBfdIntfSessState$.

Cause

The operational state of a BFD session of the IPsec instance changed.

Effect

None.

Recovery

No recovery is necessary.

2.28.2. tIPsecRadAcctPlcyFailure

tIPsecRadAcctPlcyFailure:IPSEC
Table 520:  tIPsecRadAcctPlcyFailure properties 

Property name

Value

Application name

IPSEC

Event ID

2004

Event name

tIPsecRadAcctPlcyFailure

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.4

Default severity

minor

Message format string

Failed to send RADIUS accounting request for policy $tIPsecRadAcctPlcyName$ due to: $tIPsecRadAcctPlcyFailReason$

Cause

The tIPsecRadAcctPlcyFail notification is generated when a RADIUS accounting request was not sent out successfully to any of the RADIUS servers in the indicated accounting policy.

Effect

The RADIUS server may not receive the accounting information.

Recovery

Depending on the reason indicated as per 'tIPsecRadAcctPlcyFailReason', 'tIPsecRadAcctPlcyTable' configuration may need to be changed.

2.28.3. tIPsecRUSAFailToAddRoute

tIPsecRUSAFailToAddRoute:IPSEC
Table 521:  tIPsecRUSAFailToAddRoute properties 

Property name

Value

Application name

IPSEC

Event ID

2002

Event name

tIPsecRUSAFailToAddRoute

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.2

Default severity

warning

Message format string

IPsec Remote-User tunnel $tIPsecRUTnlInetAddress$:$tIPsecRUTnlPort$ failed to add route to $tIPsecRUSARemAddr$/$tIPsecRUSARemAPrefLen$ because $tIPsecNotifReason$.

Cause

The event is generated when creation of a remote-user tunnel fails.

Effect

None.

Recovery

No recovery is necessary.

2.28.4. tIPsecRuTnlEncapIpMtuTooSmall

tIPsecRuTnlEncapIpMtuTooSmall:IPSEC
Table 522:  tIPsecRuTnlEncapIpMtuTooSmall properties 

Property name

Value

Application name

IPSEC

Event ID

2007

Event name

tIPsecRuTnlEncapIpMtuTooSmall

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.7

Default severity

warning

Message format string

Addition of tunnel encapsulation at IPsec remote user tunnel on SAP:$sapEncapValue$, service:$svcId$ for IP address $tIPsecNotifRUTnlInetAddress$:$tIPsecNotifRUTnlPort$ with configured MTU of $tIPsecNotifConfigIpMtu$, having encapsulated MTU of $tIPsecNotifConfigEncapIpMtu$ has an overhead of $tIPsecNotifEncapOverhead$.

Cause

The tIPsecRuTnlEncapIpMtuTooSmall notification is generated when the addition of tunnel encapsulation to a packet at or near the IPsec remote user tunnel's configured IP MTU may cause it to exceed the tunnel's configured encapsulated IP MTU.

Effect

The pre-encapsulated packet may be fragmented, and will require reassembly by the tunnel remote endpoint, causing a performance impact.

Recovery

Configured IP MTU and/or encapsulated IP MTU may need to be changed depending on the size of the encapsulation overhead as indicated in 'tIPsecNotifEncapOverhead', and the transmission capabilities of the tunnel's transport network.

2.28.5. tIPsecRUTnlFailToCreate

tIPsecRUTnlFailToCreate:IPSEC
Table 523:  tIPsecRUTnlFailToCreate properties 

Property name

Value

Application name

IPSEC

Event ID

2001

Event name

tIPsecRUTnlFailToCreate

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.1

Default severity

warning

Message format string

Creation of an IPsec Remote-User tunnel $tIPsecNotifRUTnlInetAddress$:$tIPsecNotifRUTnlPort$ on SAP:$sapEncapValue$, service:$svcId$ failed because $tIPsecNotifReason$.

Cause

The event is generated when creation of a remote-user tunnel fails.

Effect

None.

Recovery

No recovery is necessary.

2.28.6. tIPsecRUTnlRemoved

tIPsecRUTnlRemoved:IPSEC
Table 524:  tIPsecRUTnlRemoved properties 

Property name

Value

Application name

IPSEC

Event ID

2013

Event name

tIPsecRUTnlRemoved

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.13

Default severity

minor

Message format string

IPsec Remote-User tunnel $tIPsecNotifRUTnlInetAddress$:$tIPsecNotifRUTnlPort$ on SAP:$sapEncapValue$, service:$svcId$ was removed because $tIPsecNotifReason$.

Cause

A tIPsecRUTnlRemoved notification is generated when a remote-user tunnel is removed under certain reasons, which are indicated by tIPsecNotifReason (e.g., failed to renew private address lease with DHCP server).

Effect

The IPsec tunnel becomes operationally out of service.

Recovery

N/A

2.28.7. tIPSecTrustAnchorPrfOprChg

tIPSecTrustAnchorPrfOprChg:IPSEC
Table 525:  tIPSecTrustAnchorPrfOprChg properties 

Property name

Value

Application name

IPSEC

Event ID

2005

Event name

tIPSecTrustAnchorPrfOprChg

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.5

Default severity

minor

Message format string

$tIPsecTrustAnchorCAProfDown$ of the configured trust-anchors in profile $tIPsecTrustAnchorProfName$ are not operational

Cause

The tIPSecTrustAnchorPrfOprChg notification is generated when not all of the trust-anchors in a profile are operational.

Effect

Authentication of tunnels configured with the trust-anchor-profile will fail if the trusted CA (Certificate Authority) in the certificate chain is not operational.

Recovery

Bring the trusted CA-profile operational up.

2.28.8. tIPsecTunnelEncapIpMtuTooSmall

tIPsecTunnelEncapIpMtuTooSmall:IPSEC
Table 526:  tIPsecTunnelEncapIpMtuTooSmall properties 

Property name

Value

Application name

IPSEC

Event ID

2006

Event name

tIPsecTunnelEncapIpMtuTooSmall

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.6

Default severity

warning

Message format string

Addition of tunnel encapsulation at IPsec static tunnel $tIPsecNotifIPsecTunnelName$ on SAP:$sapEncapValue$, service:$svcId$ with configured MTU of $tIPsecNotifConfigIpMtu$, having encapsulated MTU of $tIPsecNotifConfigEncapIpMtu$ has an overhead of $tIPsecNotifEncapOverhead$

Cause

The tIPsecTunnelEncapIpMtuTooSmall notification is generated when the addition of tunnel encapsulation to a packet at or near the IPsec static tunnel's configured IP MTU may cause it to exceed the tunnel's configured encapsulated IP MTU.

Effect

The pre-encapsulated packet may be fragmented, and will require reassembly by the tunnel remote endpoint, causing a performance impact.

Recovery

Configured IP MTU and/or encapsulated IP MTU may need to be changed depending on the size of the encapsulation overhead as indicated in 'tIPsecNotifEncapOverhead', and the transmission capabilities of the tunnel's transport network.

2.28.9. tmnxIPsecGWOperStateChange

tmnxIPsecGWOperStateChange:IPSEC
Table 527:  tmnxIPsecGWOperStateChange properties 

Property name

Value

Application name

IPSEC

Event ID

2012

Event name

tmnxIPsecGWOperStateChange

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.12

Default severity

minor

Message format string

Operational state change for IPsec Gateway $tmnxIPsecGWName$ on service $svcId$ and SAP $sapEncapValue$, admin state: $tmnxIPsecGWAdminState$, oper state: $tmnxIPsecGWOperState$, oper flags: $tmnxIPsecGWOperFlags$

Cause

The tmnxIPsecGWOperStateChange notification is generated when there is a state change in tmnxIPsecGWOperState for an IPsec gateway.

Effect

When the value of tmnxIPsecGWOperState is 'outOfService (3)', the IPsec gateway is operationally down and it is not ready to negotiate IKE sessions with remote clients. When the value of tmnxIPsecGWOperState is 'inService (2)', the IPsec gateway is operationally up. When the value of tmnxIPsecGWOperState is 'limited (5)', the IPsec gateway is not fully operationally up due to the conditions indicated in tmnxIPsecTunnelOperFlags and can only negotiate limited new IKE sessions.

Recovery

Please refer to tmnxIPsecGWOperFlags for information on why the gateway is operationally down.

2.28.10. tmnxIPsecTunnelOperStateChange

tmnxIPsecTunnelOperStateChange:IPSEC
Table 528:  tmnxIPsecTunnelOperStateChange properties 

Property name

Value

Application name

IPSEC

Event ID

2011

Event name

tmnxIPsecTunnelOperStateChange

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.11

Default severity

minor

Message format string

Operational state change for IPsec Tunnel $tmnxIPsecTunnelName$ on service $svcId$ and SAP $sapEncapValue$, admin state: $tmnxIPsecTunnelAdminState$, oper state: $tmnxIPsecTunnelOperState$, oper flags: $tmnxIPsecTunnelOperFlags$

Cause

The tmnxIPsecTunnelOperStateChange notification is generated when there is a change in tmnxIPsecTunnelOperState for an IPsec tunnel.

Effect

When the value of tmnxIPsecTunnelOperState is 'outOfService (3)', the IPesc tunnel is operationally down and traffic arriving at the tunnel endpoints will not be encapsulated and transported. When the value of tmnxIPsecTunnelOperState is 'inService (2)', the IPsec tunnel is operationally up. When the value of tmnxIPsecGWOperState is 'limited (5)', the IPsec tunnel is operationally up but may not be ready to re-establish the connection until the conditions indicated in the tmnxIPsecTunnelOperFlags are cleared.

Recovery

Please refer to tmnxIPsecTunnelOperFlags for information on why the tunnel is operationally down.

2.28.11. tmnxSecNotifCmptedCertChnChngd

tmnxSecNotifCmptedCertChnChngd:IPSEC
Table 529:  tmnxSecNotifCmptedCertChnChngd properties 

Property name

Value

Application name

IPSEC

Event ID

2009

Event name

tmnxSecNotifCmptedCertChnChngd

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.9

Default severity

minor

Message format string

Certificate chain changed to $tIPsecNotifCaProfNames$ in cert-profile $tIPsecNotifCertProfileName$ entry $tIPsecNotifCertProfEntryId$

Cause

The tmnxSecNotifCmptedCertChnChngd notification is generated when a computed certificate chain is changed due to a dependent CA profile being changed and brought into service.

Effect

The hash of the recomputed certificate chain, if changed, will be used for choosing cert-profile entry during new IPsec tunnel establishment.

Recovery

If the changed CA certificate is used as a trust-anchor at the peer, then the certificate should be updated at the peer as well to ensure correct cert-profile entry selection.

2.28.12. tmnxSecNotifCmptedCertHashChngd

tmnxSecNotifCmptedCertHashChngd:IPSEC
Table 530:  tmnxSecNotifCmptedCertHashChngd properties 

Property name

Value

Application name

IPSEC

Event ID

2008

Event name

tmnxSecNotifCmptedCertHashChngd

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.8

Default severity

minor

Message format string

Hash of certificate chain changed in cert-profile $tIPsecNotifCertProfileName$ entry $tIPsecNotifCertProfEntryId$ due to CA profile $tIPsecNotifCaProfNames$

Cause

The tmnxSecNotifCmptedCertHashChngd notification is generated when the hash of a certificate chain is changed.

Effect

The hash of the recomputed certificate chain will be used for choosing cert-profile entry during new IPsec tunnel establishment.

Recovery

If the changed CA certificate is used as a trust-anchor at the peer, then the certificate should be updated at the peer as well to ensure correct cert-profile entry selection.

2.28.13. tmnxSecNotifSendChnNotInCmptChn

tmnxSecNotifSendChnNotInCmptChn:IPSEC
Table 531:  tmnxSecNotifSendChnNotInCmptChn properties 

Property name

Value

Application name

IPSEC

Event ID

2010

Event name

tmnxSecNotifSendChnNotInCmptChn

SNMP notification prefix and OID

TIMETRA-IPSEC-MIB.tmnxIPsecNotifications.10

Default severity

minor

Message format string