> Starent Chassis Traps
> This chapter describes the traps for the system
> Traps
> Object
> starCardTempOverheat
> Object ID
> enterprises.8164.2.1
> Description
> The card has reached a temperature beyond its safe operating range. Probable Cause: External temperature is too high; One or more fan failures; blockages the prevent fan air inflow/outflow.
> Action to be Taken: Inspect chassis for any item that may be blocking chassis air flow. Verify adjacent equipment is not obstructing air flow. Verify that the fans are running via the CLI/Web Element Manager. Check air filters. Check chassis maintenance schedule to see if chassis needs routine air filter replacement. Verify room temperature is within acceptable operating conditions. Clear Condition: This condition is cleared when the card reaches its operating temperature range or is removed from the system.
> Condition Clear Alarm: This condition is cleared by a starCardTempOK notification.
> Objects
> starSlotNum
> starCardTemperature
> Object
> starCardTempOK
> Object ID
> enterprises.8164.2.2
> Description
> The temperature of the card is now within its safe operating range. This notification is only generated if the card has previously generated a starCardTempOverheat notification.
> Action to be Taken: No action required. The cause for the card overheat condition should be investigated.
> Objects
> starSlotNum
> starCardTemperature
> Object
> starCardReset
> Object ID
> enterprises.8164.2.3
> Description
> A reset operation has been invoked on the card.
> Important: This trap is obsolete.
> Objects
> starSlotNum
> starCardType
> Object
> starCardRebootRequest
> Object ID
> enterprises.8164.2.4
> Description
> A Reboot operation has been invoked on this card by an administrator. If successful, a subsequent CardDown trap is typically generated.
> Action to be Taken: No action required. If the reboot was not scheduled the admin logs can be examined to determine who invoked the reboot operation.
> Objects
> starSlotNum
> starCardType
> Object
> starCardUp
> Object ID
> enterprises.8164.2.5
> Description
> The card is up (operational).
> Objects
> starSlotNum
> starCardType
> Object
> starCardVoltageFailure
> Object ID
> enterprises.8164.2.6
> Description
> A voltage regulation failure has been detected this card.
> Probable Cause: Problem with incoming power; failure of power filters; hardware issue with card. Note that this is an extremely abnormal condition.
> Action to be Taken: Verify that the power supplied to the chassis is operating correctly; use the CLI/Web Element Manager to check the state of the chassis power filters; replace the card.
> Clear Condition: This is not a recoverable error except via restarting the card, so the condition is only cleared via a starCardUp or starCardActive notification.
> Objects
> starSlotNum
> starCardType
> Object
> starCardRemoved
> Object ID
> enterprises.8164.2.7
> Description
> A card has been removed from the chassis.
> Probable Cause: An operator has physically unlocked and removed a card from the chassis.
> Action to be Taken: No action is required. If the card removal was unplanned, the admin logs can identify the time when the card was initially unlocked.
> Objects
> starSlotNum
> starCardType
> Object
> starCardInserted
> Object ID
> enterprises.8164.2.8
> Description
> A card has been inserted into the chassis.
> Objects
> starSlotNum
> starCardType
> Object
> starCardBootFailed
> Object ID
> enterprises.8164.2.9
> Description
> A card has failed to startup properly. The card is not operational. Probable Cause: The system logs should contain additional information about the cause of the boot failure.
> Objects
> starSlotNum
> starCardType
> Object
> starCardFailed
> Object ID
> enterprises.8164.2.10
> Description
> The card has failed and is no longer operational. This trap is obsolete and has been replaced with more specific traps to identify specific failures.
> Objects
> starSlotNum
> starCardType
> Object
> starCardSWFailed
> Object ID
> enterprises.8164.2.11
> Description
> An unrecoverable software error has occurred on the card. This trap is obsolete and has been replaced with more specific traps to identify specific failures.
> Objects
> starSlotNum
> Important: This trap is obsolete.
> Object
> starCardRCCFailed
> Object ID
> enterprises.8164.2.12
> Description
> The RCC has failed.
> Probable Cause: A hardware failure on the RCC card.
> Important: This trap is obsolete.
> Objects
> starSlotNum
> Object
> starCardMismatch
> Object ID
> enterprises.8164.2.13
> Description
> The card does not match its configuration, or the card does not match the slot it was inserted into, or the card is of an unsupported type.
> Probable Cause: A card was inserted into a slot which was configured for a different type of card. For example, a Gigabit Ethernet card was inserted into a slot configured for a Fast Ethernet card.
> Clear Condition: A starCardUp or starCardActive notification would indicate that this condition has been cleared.
> Objects
> starSlotNum
> starCardType
> Object
> starCardFailureLEDOn
> Object ID
> enterprises.8164.2.14
> Description
> The failure LED is illuminated on the card. This trap is obsolete and has been replaced with more specific traps for specific failures.
> Objects
> starSlotNum
> starCardType
> Important: This object is obsolete.
> Object
> starCardFailureLEDOff
> Object ID
> enterprises.8164.2.15
> Description
> The failure LED is no longer illuminated on the card. This notification is only generated if the card has previously generated a starCardFailureLEDOn notification. This trap is obsolete and has been replaced with more specific traps for specific failures.
> Objects
> starSlotNum
> starCardType
> Object
> starCardPACMigrateStart
> Object ID
> enterprises.8164.2.16
> Description
> A PAC/PSC Migration operation has begun. The first varbind identifies the PAC/PSC being migrated away from; the second varbind identifies the PAC being migrated to.
> Probable Cause: This is typically caused by an operator action; it can also represent the system recovering from a software or hardware fault.
> Clear Condition: A starCardPACMigrateComplete is generated when the migration is completed.
> Objects
> starSlotNum
> starSlotNum
> Object
> starCardPACMigrateComplete
> Object ID
> enterprises.8164.2.17
> Description
> A PAC/PSC Migration operation has successfully completed. The first varbind identifies the PAC/PSC that was migrated away from; the second varbind identifies the PAC/PSC that was migrated to.
> Objects
> starSlotNum
> starSlotNum
> Object
> starCardPACMigrateFailed
> Object ID
> enterprises.8164.2.18
> Description
> A PAC/PSC Migration operation has failed. The first varbind identifies the PAC/PSC that was attempted to be migrated away from; the second varbind identifies the PAC/PSC that was attempted to be migrated to.
> Probable Cause: The PAC/PSC being migrated to was removed or reset before the migration completed; the migration operation was terminated by an operator; or a software or hardware failure on either PAC/PSC involved in the migration operation.
> Clear Condition: The PAC/PSC in question will be reset; a starCardUp notification will be generated when the card is operational again.
> Objects
> starSlotNum
> starSlotNum
> Object
> starCardSPCSwitchoverStart
> Object ID
> enterprises.8164.2.19
> Description
> An SPC switchover operation has begun. The first varbind identifies the SPC being switched away from; the second varbind identifies the SPC being switched to. Note that since an SPC switchover can cause a momentary loss of communication through the management (SPIO) interface, it is possible that this trap will not be successfully delivered.
> Probable Cause: This is typically caused by an operator action; it can also represent the system recovering from a software or hardware fault.
> Action to be Taken: If the SPC switchover was unplanned, the admin logs should be examined for the cause of the switchover. If the cause was a software failure, the system crash logs should be examined.
> Clear Condition: Verify the SPC switchover completes successfully.
> Clear Condition Alarm: A starCardSPCSwitchoverComplete is generated when the switchover operation has completed.
> Objects
> starSlotNum
> starSlotNum
> Object
> starCardSPCSwitchoverComplete
> Object ID
> enterprises.8164.2.20
> Description
> An SPC Switchover has completed successfully. The starSlotNum varbind identifies the new primary SPC.
> Action to be Taken: If the SPC switchover was unplanned, the admin logs should be examined for the cause of the switchover. If the cause was a software failure, the system crash logs should be examined.
> Objects
> starSlotNum
> Object
> starCardSPCSwitchoverFailed
> Object ID
> enterprises.8164.2.21
> Description
> An SPC switchover operation has failed. The first varbind identifies the SPC that was attempted to be switched away from; the second varbind identifies the SPC that was attempted to be switched to.
> Probable Cause: The SPC being migrated to was removed or reset before the migration completed; the migration operation was terminated by an operator; or a software or hardware failure on either SPC.
> Action to be Taken: Verify that both SPCs have the card locks in the locked position; examine the admin logs for the cause of the failure. If the cause was a software failure, the system crash logs should be examined.
> Clear Condition:The SPC in question will be reset; a starCardUp notification will be generated when the card is operational again.
> Objects
> starSlotNum
> starSlotNum
> Object
> starFanFailed
> Object ID
> enterprises.8164.2.22
> Description
> One of more fans have failed on the indicated fan controller.
> Probable Cause: A hardware failure on the fan tray. The fan tray should be replaced. Action to be Taken: Verify there is no physical obstruction to the fans; Replace the fan tray.
> Clear Condition: Verify the fans are running Condition Clear Alarm: A starFanInserted notification will be generated when the fan tray is replaced.
> Objects
> starFanNum
> starFanStatus
> Object
> starFanRemoved
> Object ID
> enterprises.8164.2.23
> Description
> A fan tray has been removed.
> Action to be Taken: Replace the fan tray.
> Clear Condition: Verify both fan trays are present and operational.
> Condition Clear Alarm: A starFanInserted notification will be generated when the fan tray is replaced.
> Objects
> starFanNum
> Object
> starFanInserted
> Object ID
> enterprises.8164.2.24
> Description
> A fan tray has been inserted.
> Objects
> starFanNum
> Object
> starLogThreshold
> Object ID
> enterprises.8164.2.25
> Description
> A system log has reached its maximum size. This trap is obsolete.
> Objects
> starLogName
> starLogCurSize
> starLogMaxSize
> Important: This object is obsolete.
> Object
> starCPUBusy
> Object ID
> enterprises.8164.2.26
> Description
> The CPU is experiencing very high usage.
> Probable Cause: For SPC/SMC CPUs this typically represents an abnormal amount of management (CLI, SNMP, CORBA) requests. For PAC/PSC cards this indicates that the system is reaching its capacity.
> Action to be Taken:For SPC/SMC cards, this may be a transient condition because of a burst of management activity. Monitor the CPU usage and if it is persistently high, examine the CPU table to determine which management activity is causing the excessive usage. For PAC/PSC cards, this indicates the system is nearing its overall capacity. Monitor CPU usage and if it is persistently high, the system may need additional PACs/PSCs to keep up with the system load.
> Clear Condition:Verify that CPU usage returned to a normal load. This can represent a transient condition; the trap will be periodically repeated if the condition persists.
> Objects
> starCPUSlot
> starCPUNumber
> Object
> starCPUMemoryLow
> Object ID
> enterprises.8164.2.27
> Description
> The CPU is experiencing a low memory condition.
> Probable Cause: For SPC/SMC CPUs this typically represents an abnormal number of management sessions, in particular CLI sessions. For PAC/PSC cards this indicates that the system is reaching its capacity.
> Action to be Taken: For SPC/SMC cards, this may be a transient condition because of a burst of management activity. Monitor memory usage and if it is persistently high, examine the CPU table to determine which management activity is causing the excessive usage. Verify that large numbers of CLI sessions are not being generated and, if needed, terminate extra sessions. For PAC/PSC cards, this indicated the system is nearing its overall capacity. Monitor memory usage and if it is persistently high, the system may need additional PACs/PSCs or additional PAC/PSC memory to keep up with the system load.
> Clear Condition: Verify that memory usage returned to a normal load. This can represent a transient condition; the trap will be periodically repeated if the condition persists.
> Objects
> starCPUSlot
> starCPUNumber
> Object
> starCPUMemoryFailed
> Object ID
> enterprises.8164.2.28
> Description
> The memory on this CPU has failed.
> Probable Cause: This indicates a hardware problem.
> Action to be Taken: Replace the failing card.
> Clear Condition: The card will be reset; a starCardUp will be generated if the card is restored to an operational state.
> Objects
> starCPUSlot
> starCPUNumber
> Object
> starCPUFailed
> Object ID
> enterprises.8164.2.29
> Description
> The CPU has failed.
> Probable Cause: This indicates a hardware problem.
> Action to be Taken: Replace the failing card.
> Clear Condition:The card will be reset; a starCardUp will be generated if the card is restored to an operational state.
> Objects
> starCPUSlot
> starCPUNumber
> Object
> starCPUWatchDogExpired
> Object ID
> enterprises.8164.2.30
> Description
> The watch dog timer has failed on this CPU.
> Probable Cause: This could indicate an extremely busy CPU, a software problem, or a hardware issue.
> Action to be Taken:Check the admin logs for an indication of the problem. Check the system crash logs for an indication of software problems. If the problem persists, replace the card.
> Clear Condition: Verify that an SPC/SMC switchover or PAC/PSC migration completes successfully to recover from the failure condition.
> Condition Clear Alarm: A starCardUp will be generated if the card is restored to an operational state.
> Objects
> starCPUSlot
> starCPUNumber
> Object
> starNPUARPPoolExhausted
> Object ID
> enterprises.8164.2.31
> Description
> The ARP pool on this NPU manager is exhausted. When this occurs, the ARP entry isn't added and traffic to the local device is forwarded through a slower path.
> Action To Be Taken: Reduce the total number of directly connected devices or clear ARP entries.
> Objects
> starNPUMgrNumber
> Object
> starPowerFilterUnitFailed
> Object ID
> enterprises.8164.2.32
> Description
> A Power Filter Unit (PFU) failed.
> Probable Cause: The external power source has failed or has been disconnected, or a hardware failure on the PFU.
> Action to be Taken:Verify that the input power to the power filter is operational and repair if needed. Verify that the connections to the power filter are intact and that the power filter is properly inserted into the chassis. Replace the power filter if required.
> Clear Condition:Verify that both power filters are operating.
> Condition Clear Alarm: A starPowerFilterAvail will be generated when the power filter is replaced.
> Objects
> starPowerNumber
> Object
> starPowerFilterUnitUnavail
> Object ID
> enterprises.8164.2.33
> Description
> A Power Filter Unit (PFU) is unavailable.
> Probable Cause: The power filter has been removed from the chassis, or no power is being provided to the PFU.
> Action to be Taken: If the power filter removal wasn't planned, Verify that the input power to the power filter is operational and repair if needed. Verify that the connections to the power filter are intact and that the power filter is properly inserted into the chassis. Replace the power filter if required.
> Clear Condition:Verify that both power filters are operating.
> Condition Clear Alarm: A starPowerFilterUnitAvail will be generated when the power filter is replaced.
> Objects
> starPowerNumber
> Object
> starPowerFilterUnitAvail
> Object ID
> enterprises.8164.2.34
> Description
> A Power Filter Unit (PFU) is available. This typically means that a PFU has been inserted into the chassis or has its power source restored.
> Action to be Taken: No action required.
> Objects
> starPowerNumber
> Object
> starAlertsDisabled
> Object ID
> enterprises.8164.2.37
> Description
> The sending of SNMP Traps has been disabled because too many alerts were generated within the defined window type.
> Probable Cause: Either a large number of SNMP notifications are being generated, or the configured threshold which limits the number of notifications is set too aggressively.
> Actions to be Taken: Examine the admin logs and the SNMP trap logs to determine the source of the large number of traps and take appropriate actions; verify that the configured limit for the rate at which traps will be sent is appropriate for your environment.
> Clear Condition Alarm: When the rate of SNMP notifications goes down a starAlertsEnabled notification is generated.
> Objects
> starMaxAlertsPerTime
> starWindowTime
> Object
> starAlertsEnabled
> Object ID
> enterprises.8164.2.38
> Description
> The sending of SNMP Traps has been re-enabled.
> Object
> starAAAAuthServerUnreachable
> Object ID
> enterprises.8164.2.39
> Description
> The Authentication, Authorization and Accounting (AAA) server cannot be reached.
> Probable Cause: The AAA server is down, or there is a network issue preventing communication with the AAA server. Actions to be Taken: Restore the AAA server to an operational status; Verify that the AAA server is reachable by performing a 'ping' operation from the CLI in the appropriate context. Check the admin logs for notification of communication problems.
> Clear Condition: Verify that communication to the AAA authentication server has been restored.
> Condition Clear Alarm: When this condition clears a starAAAAuthServerReachable notification will be generated. Note that if in a AAA group all the configured RADIUS servers are detected as Down, their state is brought back to Active before the deadtime expiry period so that call setup signaling with AAA can proceed for subsequent requests. Therefore, when the last Active authentication server in the group is detected as Down, starAAAAuthServerUnreachable is generated, and immediately later when the server state changes to Active, starAAAAuthServerReachable is generated. This behavior is the same when there is only one RADIUS server configured.
> Objects
> radiusAuthServerIndex
> radiusAuthServerAddress
> Object
> starAAAAuthServerReachable
> Object ID
> enterprises.8164.2.40
> Description
> The Authentication, Authorization and Accounting (AAA) server is now reachable. This can be the result of a system startup, the configuration of a new server, or a previously unreachable server becoming reachable.
> Action to be Taken: No Action Required.
> Objects
> radiusAuthServerIndex
> radiusAuthServerAddress
> Object
> starAAAAuthServerMisconfigured
> Object ID
> enterprises.8164.2.41
> Description
> The Authentication, Authorization and Accounting (AAA) server has been misconfigured. This server is not usable until this condition is repaired.
> Action to be Taken: Examine the system configuration and correct the misconfiguration. See the user documentation for details on AAA configuration.
> Clear Condition: Verify that communication to the AAA authentication server has been restored.
> Condition Clear Alarm: When this condition clears a starAAAAuthServerReachable notification will be generated.
> Objects
> radiusAuthServerIndex
> radiusAuthServerAddress
> Object
> starAAAAccServerUnreachable
> Object ID
> enterprises.8164.2.42
> Description
> The Authentication, Authorization and Accounting (AAA) server cannot be reached.
> Probable Cause: The AAA server is down, or there is a network issue preventing communication with the AAA server. Actions to be Taken: Restore the AAA server to an operational status; Verify that the AAA server is reachable by performing a 'ping' operation from the CLI in the appropriate context. Check the admin logs for notification of communication problems.
> Clear Condition: Verify that communication to the AAA accounting server has been restored.
> Condition Clear Alarm: When this condition clears a starAAAAccServerReachable notification will be generated. Note that if in a AAA group all the configured RADIUS servers are detected as Down, their state is brought back to Active before the deadtime expiry period so that call setup signaling with AAA can proceed for subsequent requests. Therefore, when the last Active Accounting server in the group is detected as Down, starAAAAccServerUnreachable is generated, and immediately later when the server state changes to Active, starAAAAccServerReachable is generated. This behavior is the same when there is only one RADIUS server configured.
> Objects
> radiusAccServerIndex
> radiusAccServerAddress
> Object
> starAAAAccServerReachable
> Object ID
> enterprises.8164.2.43
> Description
> The Authentication, Authorization and Accounting (AAA) server is now reachable. This can be the result of a system startup, the configuration of a new server, or a previously unreachable server becoming reachable. Note that since Accounting servers are not responding to 'hello'-type messages, it is not always possible to accurately determine when an accounting server is reachable. A server may be declared 'reachable' when the ST-16 is ready to start using the server, but before any acknowledgement is actually received from the server. Once accounting information actually is sent to the server a starAAAAccServerUnreachable will be generated if the server does not properly respond.
> Action to be Taken: No Action Required.
> Objects
> radiusAccServerIndex
> radiusAccServerAddress
> Object
> starAAAAccServerMisconfigured
> Object ID
> enterprises.8164.2.44
> Description
> The Authentication, Authorization and Accounting (AAA) server has been misconfigured. This server is not usable until this condition is repaired.
> Action to be Taken: Examine the system configuration and correct the misconfiguration. See the user documentation for details on AAA configuration.
> Clear Condition: Verify that communication to the AAA authentication server has been restored.
> Condition Clear Alarm: When this condition clears a starAAAAccServerReachable notification will be generated.
> Objects
> radiusAccServerIndex
> radiusAccServerAddress
> Object
> starLogMsg
> Object ID
> enterprises.8164.2.45
> Description
> A log message. This trap is used only for debugging.
> Objects
> starLogText
> Object
> starPDSNServiceStart
> Object ID
> enterprises.8164.2.46
> Description
> A PDSN service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPDSNServiceStop
> Object ID
> enterprises.8164.2.47
> Description
> A PDSN service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the PDSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the PDSN service is operational.
> Condition Clear Alarm: A starPDSNServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starHAServiceStart
> Object ID
> enterprises.8164.2.48
> Description
> An HA service has started.Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starHAServiceStop
> Object ID
> enterprises.8164.2.49
> Description
> An HA service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the PDSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the PDSN service is operational.
> Condition Clear Alarm: A starHAServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starFAServiceStart
> Object ID
> enterprises.8164.2.50
> Description
> An FA service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starFAServiceStop
> Object ID
> enterprises.8164.2.51
> Description
> An FA service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the FA service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the FA service is operational.
> Condition Clear Alarm: A starFAServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starCLISessionStart
> Object ID
> enterprises.8164.2.52
> Description
> An interactive CLI session has started.
> Condition Clear Alarm: A starCLISessionEnd notification will be sent when the CLI session is terminated.
> Objects
> starCLIUsername
> starCLIPrivs
> starCLITtyname
> Object
> starCLISessionEnd
> Object ID
> enterprises.8164.2.53
> Description
> An interactive CLI session has ended. The CLI session may have been terminated by the CLI user; the session may have expired due to an idle timeout, or a session timeout; or the session may have been terminated by operator intervention.
> Objects
> starCLIUsername
> starCLIPrivs
> starCLITtyname
> Object
> starCritTaskFailed
> Object ID
> enterprises.8164.2.54
> Description
> A critical task has failed and the appropriate recovery steps begun. The card containing the failed task will be restarted; migration/recovery operations will proceed.
> Probable Cause: Software error.
> Actions to be Taken: Examine the admin logs for an indication of the source of the failure. Clear Condition: Verify that an SPC/SMC switchover or PAC migration completes to recover from this condition.
> Condition Clear Alarm: A starCardUp will be generated when the card has successfully restarted.
> Objects
> starTaskFacilityName
> starTaskInstance
> starTaskCard
> starTaskCPU
> Object
> starCardActive
> Object ID
> enterprises.8164.2.55
> Description
> The card is now active.
> Objects
> starSlotNum
> starCardType
> Object
> starLACServiceStart
> Object ID
> enterprises.8164.2.56
> Description
> A LAC service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starLACServiceStop
> Object ID
> enterprises.8164.2.57
> Description
> A LAC service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the LAC service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the LAC service is operational.
> Condition Clear Alarm: A starLACServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starLNSServiceStart
> Object ID
> enterprises.8164.2.58
> Description
> A LNS service has started.Action to be Taken: No Action Required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starLNSServiceStop
> Object ID
> enterprises.8164.2.59
> Description
> A LNS service has stopped.
> Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the LNS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition:Verify that the LNS service is operational.
> Condition Clear Alarm: A starLNSServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starCardDown
> Object ID
> enterprises.8164.2.60
> Description
> The card is now down.
> Probable Cause: The card was shut down by an operator; the card was removed by an operator; or a hardware or software fault caused the card to shut down. In the latter case an additional notification is generated with the specific failure.
> Action to be Taken:If the card shutdown was not planned, verify that the card is present in the system and its card lock is in the locked position. Check the admin logs for the cause of the card shutdown.
> Clear Condition: Verify that an SPC switchover/card migration completes to recover from the card shutdown.
> Condition Clear Alarm: A starCardUp notification is generated when the card is restarted.
> Objects
> starSlotNum
> starCardType
> Object
> dsx3LineStatusChange
> Object ID
> enterprises.8164.2.61
> Description
> As defined by RFC2496, this trap (mib-2.10.30.15.0 1) is sent when there is a change in the value of an dsx3LineStatus instance. If the line status change is the result of a line status change at a lower level (i.e. ds1), then no traps for the ds3 are sent.
> Objects
> dsx3LineStatus
> dsx3LineStatusLastChange
> Object
> dsx1LineStatusChange
> Object ID
> enterprises.8164.2.62
> Description
> As defined by RFC2496, this trap (mib-2.10.18.15.0 1) is sent when there is a change in the value of an dsx1LineStatus instance. If the line status change is the result of a line status change at a higher level (i.e. ds3), then no traps for the ds1 are sent.
> Objects
> dsx1LineStatus
> dsx1LineStatusLastChange
> Object
> starGGSNServiceStart
> Object ID
> enterprises.8164.2.63
> Description
> A GGSN Service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starGGSNServiceStop
> Object ID
> enterprises.8164.2.64
> Description
> A GGSN Service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the GGSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the GGSN service is operational.
> Condition Clear Alarm: A starGGSNServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starLicenseExceeded
> Object ID
> enterprises.8164.2.65
> Description
> The licenses session limit has been exceeded; note that a small number of sessions are permitted beyond the licensed limit.
> Probable Cause: The usage of the system has exceeded the capacity of the license installed, the license installed does not match the identification of the system. No license is installed.
> Action to be Taken:Verify that the proper license is installed on the system, verify that the SPCs present in the system match those identified in the software license. If required, install an additional higher-capacity license.
> clear condition: This condition is cleared when usage goes under the licensed limit.
> condition clear alarm: This condition is cleared by a starlicenseunderlimit notification.
> Objects
> starLicensedSessions
> starCurrentSessions
> starServiceType
> Object
> starSubscriberLimit
> Object ID
> enterprises.8164.2.66
> Description
> The specified service has reached its configured limit for number of subscribers.
> Action to be Taken: Verify that the configured subscriber limit is correct. Configure additional services, or configure the existing service to permit a larger number of subscribers.
> Objects
> starServiceVpnName
> starServiceServName
> starServiceSubLimit
> starServiceSubCurrent
> starServiceType
> Object
> starSessionRejectNoResource
> Object ID
> enterprises.8164.2.67
> Description
> A session setup was rejected because of a lack of available resources.
> Probable Cause: The system has reached its maximum capacity based on the number of available PACs/PSCs/CPUs/memory.
> Actions to be Taken: Examine the system CPU table to determine if there is abnormal system usage or if the system is reaching its capacity. If this condition persists, additional PACs/PSCs or PAC/PSC memory may be required. Note that there is a configuration threshold which can be setup to monitor the number of NORESOURCE rejects.
> Objects
> starServiceVpnID starServiceType
> Object
> starLongDurTimerExpiry
> Object ID
> enterprises.8164.2.68
> Description
> The long duration timer has expired for the identified subscriber.
> Action to be Taken: No action is typically required. If an abnormal number of expiries occur, verify that the configuration expiry time is correct.
> Objects
> starSubContext
> starSubMSID
> starSubName
> starSubTimerDuration
> starSubLongDurTimeoutAction
> starSubSetupTime
> starSubHomeAddr
> starSubHomeAddrv6
> Object
> starClosedRPServiceStart
> Object ID
> enterprises.8164.2.69
> Description
> Closed RP Service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starClosedRPServiceStop
> Object ID
> enterprises.8164.2.70
> Description
> Closed RP Service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the Closed RP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the Closed RP service is operational.
> Condition Clear Alarm: A starClosedRPServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starGtpcPathFailure
> Object ID
> enterprises.8164.2.71
> Description
> GTP Control Path Failure.
> Objects
> starSessGGSNVpnName
> starSessGGSNServName
> starSessGGSNPeerAddr
> Object
> starGtpuPathFailure
> Object ID
> enterprises.8164.2.72
> Description
> GTP Data Path Failure.
> Objects
> starSessGGSNVpnName
> starSessGGSNServName
> starSessGGSNPeerAddr
> Object
> starManagerFailure
> Object ID
> enterprises.8164.2.73
> Description
> Software manager Failure.
> Probable Cause: A software failure. The failing manager will be restarted.
> Action to be Taken: Examine the admin and crash logs for more information about the failure.
> Objects
> starTaskFacilityName
> starTaskInstance
> starTaskCard
> starTaskCPU
> Object
> starEISServerAlive
> Object ID
> enterprises.8164.2.74
> Description
> EIS Server alive.
> Objects
> starEISServerVPNID
> starEISServerAddr
> Object
> starEISServerDead
> Object ID
> enterprises.8164.2.75
> Description
> EIS Server down.
> Probable Cause: The remote EIS server is down or there is a network error making it unreachable.
> Condition Clear Alarm: A starEISServerAlive notification will be generated when this condition is cleared.
> Objects
> starEISServerVPNID
> starEISServerAddr
> Object
> starCgfAlive
> Object ID
> enterprises.8164.2.76
> Description
> GTPP CGF Server Alive.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerPort
> starSessGGSNPeerAddr
> Object
> starCgfDead
> Object ID
> enterprises.8164.2.77
> Description
> GTPP CGF Server Dead.
> Probable Cause: The remote CGF server is down or there is a network error making it unreachable.
> Action to be Taken: Verify that the CGF server is functioning properly, verify network connectivity to the CGF server.
> Clear Condition: This condition is cleared when the CGF server becomes reachable.
> Condition Clear Alarm: A starCgfServerAlive notification will be generated when this condition is cleared.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerPort
> starSessGGSNPeerAddr
> Object
> starStorageServerAlive
> Object ID
> enterprises.8164.2.78
> Description
> GTPP Storage Server is Alive.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> Object
> starStorageServerDead
> Object ID
> enterprises.8164.2.79
> Description
> GTPP Storage Server is Dead.
> Probable Cause: The remote storage server is down. There is a network error making it unreachable.
> Action to be Taken: Verify that the storage server is functioning properly, verify network connectivity to the storage server.
> Clear Condition: This condition is cleared when the Storage server becomes reachable.
> Condition Clear Alarm: A starStorageServerAlive notification is generated when this condition is cleared.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> Object
> starGgsnInitiatedUpdtFailed
> Object ID
> enterprises.8164.2.80
> Description
> GGSN Initiated Update PDP Context Response Failed.
> Probable Cause: This can happen if there is an inter-SGSN handoff and the new SGSN is not listed in GGSN service and its PLMN policy is set to reject unknown SGSNs.
> Action to be Taken: List the SGSN address in the GGSN service.
> Condition Clear Alarm: N/A
> Objects
> starSessGGSNVpnName
> starSessGGSNServName
> starSessGGSNSubsName
> starSessGGSNAPNName
> starSessGGSNImsi
> starSessGGSNPeerAddr
> Object
> starCongestion
> Object ID
> enterprises.8164.2.81
> Description
> A congestion condition has occurred.
> Probable Cause: This is the result of an operator-configured congestion threshold being reached. This can be due to high usage of the resource being monitored which indicates that the system is reaching its peak capacity, or could be caused by the incorrect configuration of the congestion thresholds.
> Actions to be Taken: Verify that the congestion thresholds are correct, if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online.
> Clear Condition: This system is cleared when the use of the specific resource falls below the configured limit.
> Condition Clear Alarm: A starCongestionClear notification is sent when there are no congestion conditions for a service type.
> Objects
> starServiceType
> starCongestionPolicy
> starCongestionResourceType
> Object
> starCongestionClear
> Object ID
> enterprises.8164.2.82
> Description
> A congestion condition has cleared.
> Objects
> starServiceType
> Object
> starCscfSessResourceCongestion
> Object ID
> enterprises.8164.2.1114
> Description
> A congestion condition has occurred at Session Manager for Cscf Service.
> Probable Cause: This is the result of an operator-configured congestion threshold being reached for Cscf Service at Session Manager. This can be due to high usage of the resource being monitored which indicates that the IMG is reaching its peak capacity, or could be caused by the incorrect configuration of the congestion thresholds.
> Action to be Taken: Verify that the congestion thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online.
> Condition Clear Alarm: A starCscfSessResourceCongestionClear notification is sent when there are no congestion conditions for cscf service in that Session Manager Instance.
> Objects
> starSmgrId
> starCongestionPolicy
> starCscfSessCongestionResourceType
> Object
> starCscfSessResourceCongestionClear
> Object ID
> enterprises.8164.2.1115
> Description
> A congestion condition has cleared at Session Manager for Cscf service
> Objects
> starSmgrId
> Object
> starServiceLossPTACs
> Object ID
> enterprises.8164.2.83
> Description
> A service loss condition has occurred due to PAC/PSC/TAC failure or removal.
> Probable Cause: Multiple PAC/PSC/TAC cards are no longer available, due to failure, removal, or operator action -- or configuration changes have been made which eliminated the availability of redundant cards.
> Action to be Taken: Bring additional PAC/PSC/TAC cards online to match the number of configured cards, or update the configuration to require fewer active PAC/PSC/TAC cards.
> Clear Condition: This condition is cleared when the number of active PAC/PSC/TAC cards reaches or exceeds the configured number.
> Objects
> starCardMode
> starPTACConfig
> starPTACActive
> Object
> starServiceLossLC
> Object ID
> enterprises.8164.2.84
> Description
> A service loss condition has occurred due to LC failure or removal.
> Probable Cause: Multiple Line Cards (LCs) are no longer available, due to failure, removal, or operator action.
> Action to be Taken: Bring additional LCs online to match the number of configured cards, or update the configuration to require fewer active LCs.
> Clear Condition:This condition is cleared when the number of active line cards reaches or exceeds the configured number.
> Objects
> starCardType
> starSlotNum
> starSlotNum
> Object
> starServiceLossSPIO
> Object ID
> enterprises.8164.2.85
> Description
> A service loss condition has occurred due to SPIO failure or removal. Since the SPIO contains the ports used for SNMP access, this notification cannot normally be delivered as an SNMP trap. The notification will be logged and stored in the historical trap list, and if the system is configured to send INFORM PDUs the notification might be delivered at a later time.
> Probable Cause: Both SPIOs are no longer available, due to failure, removal, or operator action.
> Action to be Taken: Bring at least one SPIO online.
> Clear Condition: This condition is cleared when a SPIO is made active.
> Object
> starIPSPAllAddrsFree
> Object ID
> enterprises.8164.2.86
> Description
> All IP addresses are now free on the IP Pool Sharing Protocol (IPSP) primary HA.
> Probable Cause: IP Pool Sharing Protocol (IPSP) is running between two HAs (a primary and a secondary). The primary HA has now released the last address that was in use. This presumably is done in preparation for taking the primary HA out of server.
> Action to be Taken: Perform the desired maintenance on the primary HA that required taking the device out of service.
> Objects
> starContextName
> starInterfaceName
> Object
> starPCFUnreachable
> Object ID
> enterprises.8164.2.87
> Description
> A PCF that the system communicates with is no longer reachable.
> Probable Cause: The PCF has failed or is otherwise unavailable, or a network connectivity problem makes it unreachable.
> Action to be Taken: If the PCF outage was unplanned, restart/reset the PCF, verify network connectivity.
> Objects
> starContextName
> starPCFAddress
> Object
> starDhcpAlive
> Object ID
> enterprises.8164.2.88
> Description
> DHCP Server Alive.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerPort
> starSessGGSNPeerAddr
> Object
> starDhcpDead
> Object ID
> enterprises.8164.2.89
> Description
> DHCP Server Dead.
> Probable Cause: The remote DHCP server is down or there is a network error making it unreachable.
> Action to be Taken:Verify that the DHCP server is functioning properly; verify network connectivity to the DHCP server.
> Clear Condition: The condition is cleared when the DHCP server becomes reachable, or if the configuration is changes to not use this server.
> Condition Clear Alarm: A starDhcpAlive notification is generated when the server becomes reachable.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerPort
> starSessGGSNPeerAddr
> Object
> starNTPPeerUnreachable
> Object ID
> enterprises.8164.2.90
> Description
> NTP Peer Unreachable.
> Probable Cause: The NTP server is down or unavailable, or there is a network connectivity issue that prevents access to the NTP server.
> Action to be Taken: Verify that the NTP server is running properly; verify that the connection to the NTP server is functioning.
> Clear Condition: This condition is cleared when the NTP server becomes reachable.
> Condition Clear Alarm: This condition is cleared by a starNTPPeerReachable notification.
> Objects
> starPeerAddress
> Object
> starNTPSyncLost
> Object ID
> enterprises.8164.2.91
> Description
> NTP Synchronization Lost.
> Probable Cause: All configured NTP server are no longer available, or some/all NTP servers have been un-configured by an operator.
> Action to be Taken: Verify that the NTP server(s) are running properly and that the network connections to the NTP servers are available. Check the configured of the NTP servers for correctness. If needed, configure additional NTP servers.
> Clear Condition: This condition is cleared when any (one) NTP server becomes reachable.
> Condition Clear Alarm: This condition is cleared by a starNTPSyncEstablished notification.
> Object
> starL2TPTunnelDownPeerUnreachable
> Object ID
> enterprises.8164.2.92
> Description
> L2TP tunnel down due to peer unreachable.
> Probable Cause: Misconfiguration of the peer router address or inability to route to the peer.
> Action to be Taken: Verify the peer address is correct; verify that the peer is operational; verify network connectivity to the peer.
> Objects
> starL2TPLocalTunnelID
> starL2TPPeerTunnelID
> starL2TPContextName
> starL2TPServiceName
> starL2TPServiceTypeName
> starL2TPLocalAddress
> starL2TPPeerAddress
> Object
> starCardStandby
> Object ID
> enterprises.8164.2.93
> Description
> The card is now standby.
> Objects
> starSlotNum
> starCardType
> Object
> starLicenseUnderLimit
> Object ID
> enterprises.8164.2.94
> Description
> Usage is now under the licensed session limit.
> Objects
> starLicensedSessions
> starCurrentSessions
> starServiceType
> Object
> starIPSECPriTunDown
> Object ID
> enterprises.8164.2.95
> Description
> IPSEC Primary Tunnel Down
> Objects
> starIPSECContextName
> starIPSECGroupName
> starIPSECTunLocalIPAddr
> starIPSECTunRemoteIPAddr
> Object
> starIPSECPriTunUp
> Object ID
> enterprises.8164.2.96
> Description
> IPSEC Primary Tunnel Up
> Objects
> starIPSECContextName
> starIPSECGroupName
> starIPSECTunLocalIPAddr
> starIPSECTunRemoteIPAddr
> Object
> starIPSECSecTunDown
> Object ID
> enterprises.8164.2.97
> Description
> IPSEC Secondary Tunnel Down
> Objects
> starIPSECContextName
> starIPSECGroupName
> starIPSECTunLocalIPAddr
> starIPSECTunRemoteIPAddr
> Object
> starIPSECSecTunUp
> Object ID
> enterprises.8164.2.98
> Description
> IPSEC Secondary Tunnel Up
> Objects
> starIPSECContextName
> starIPSECGroupName
> starIPSECTunLocalIPAddr
> starIPSECTunRemoteIPAddr
> Object Group
> starIPSECTunSwitchFail
> Object ID
> enterprises.8164.2.99
> Description
> IPSEC Tunnel Switchover failed or unable to be attempted
> Objects
> starIPSECContextName
> starIPSECGroupName
> Object
> starIPSECTunSwitchComplete
> Object ID
> enterprises.8164.2.100
> Description
> IPSEC Tunnel Switchover complete
> Objects
> starIPSECContextName
> starIPSECGroupName
> starIPSECTunLocalIPAddr
> starIPSECTunRemoteIPAddr
> Object
> starNwReachServerAlive
> Object ID
> enterprises.8164.2.101
> Description
> Nw Reachable Server alive
> Objects
> starNwReachName
> starNwReachSrvrAddr
> Object
> starNwReachServerDead
> Object ID
> enterprises.8164.2.102
> Description
> Nw Reachable Server Dead.
> Probable Cause: The remote server is down or there is a network error making it unreachable. A starNwReachServerAlive notification will be generated when this condition is cleared.
> Objects
> starNwReachName
> starNwReachSrvrAddr
> Object
> starStorageServerUnackedGcdrVolPurge
> Object ID
> enterprises.8164.2.103
> Description
> GTPP storage server has performed un-acked GCDRs volume purge.
> Probable Cause: GTPP storage server has purged un-acked GCDRs after hitting the max allowed configured limit on un-acked GCDR in the backup database.
> Action to be Taken: Check for the unacked file generated for these GCDRs.
> Clear Condition: There is no clear condition for this notification.
> Condition Clear Alarm: There is no clear alarm for this notification.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> Object
> starStorageServerUnackedGcdrFileGen
> Object ID
> enterprises.8164.2.104
> Description
> GTPP storage server has exported the unacked GCDRs to file from backup db.
> Probable Cause: GTPP storage server has generated and saved all the unacked GCDRs to file.
> Action to be Taken: Operator needs to FTP the generated file.
> Clear Condition: There is no clear condition for this notification.
> Condition Clear Alarm: There is no clear alarm for this notification.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> Object
> starNTPPeerReachable
> Object ID
> enterprises.8164.2.105
> Description
> NTP Peer Reachable.
> Probable Cause: The NTP server is reachable. This could indicate a newly configured NTP server (including an initial configuration on system startup) or could indicate a previously unreachable server has become reachable.
> Action to be Taken: No action required.
> Objects
> starPeerAddress
> Object
> starNTPSyncEstablished
> Object ID
> enterprises.8164.2.106
> Description
> NTP Synchronization Established.
> Probable Cause: An NTP server is available when previously no server was available. This could indicate a newly configured NTP server (including an initial configuration on system startup) or could indicate that one or more previously unreachable server(s) has become reachable.
> Action to be Taken: No action required.
> Object
> starSIPServiceStart
> Object ID
> enterprises.8164.2.107
> Description
> A SIP service has started Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSIPServiceStop
> Object ID
> enterprises.8164.2.108
> Description
> A SIP service has stopped.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starVIMServiceStart
> Object ID
> enterprises.8164.2.109
> Description
> A VIM service has started Action to be Taken: No action required
> Syntax
> starServiceVpnName
> starServiceServName
> Object
> starVIMServiceStop
> Object ID
> enterprises.8164.2.110
> Description
> A VIM service has stopped. This is because of application out-of-service or if vim is down or no app. server Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starCHATCONFServiceStart
> Object ID
> enterprises.8164.2.111
> Description
> A CHAT/CONF service has started Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starCHATCONFServiceStop
> Object ID
> enterprises.8164.2.112
> Description
> A CHAT/CONF service has stopped. This is because of application out-of-service or if chatconf is down or no app. server.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSIPRouteNomatch
> Object ID
> enterprises.8164.2.113
> Description
> SIP session has failed since there is no match in the routing table with matching prefix.
> Action to be Taken: Operator has to configure with matching prefix if required.
> Objects
> starSIPRouteVpnName
> starSIPRouteVmgName
> starSIPRouteAsName
> starSIPRouteDestPartyNum
> starSIPRouteReqNum
> Object
> starL3AddrUnreachable
> Object ID
> enterprises.8164.2.114
> Description
> A L3 Address is unreachable through the specific slot and port. Action to be taken: No action required
> Objects
> starL3Address
> starPortSlot
> starPortNum
> Object
> starSWUpgradeStart
> Object ID
> enterprises.8164.2.115
> Description
> An operator has begun to upgrade the software on the ST-16.
> Object
> starSWUpgradeComplete
> Object ID
> enterprises.8164.2.116
> Description
> An operator-initiated software upgrade has been completed.
> Object
> starSWUpgradeAborted
> Object ID
> enterprises.8164.2.117
> Description
> An operator-initiated software upgrade has been aborted.
> Object
> starBGPPeerSessionUp
> Object ID
> enterprises.8164.2.118
> Description
> The BGP peer session to the specified IP address is operational. This may indicate the initial configuration of a new peer, the initial connectivity after a system restart, or the restoration of connectivity after a starBGNPeerSessionDown event.
> Action to be Taken: No action required.
> Objects
> starContextName
> starBGPPeerIPAddress
> Object
> starBGPPeerSessionDown
> Object ID
> enterprises.8164.2.119
> Description
> The BGP peer session to the specified IP address is no longer operational.
> Probable Cause: The BGP peer is not-operational; the network between the ST-16 and the BGP peer is experiencing an outage; LC failure(s) on the ST-16.
> Action to be Taken: Verify the BGP peer is operational; verify network connectivity to the BGP peer.
> Clear Condition Alarm: starBGPPeerSessionUp is generated when connectivity is reestablished.
> Objects
> starContextName
> starBGPPeerIPAddress
> Object
> starSRPActive
> Object ID
> enterprises.8164.2.120
> Description
> The SRP Chassis Status is now Active.
> Action to be Taken: No action is required.
> Objects
> starContextName
> starSRPIPAddress
> Object
> starSRPStandby
> Object ID
> enterprises.8164.2.121
> Description
> The SRP Chassis Status is now Standby.
> Action to be Taken: No action is required.
> Objects
> starContextName
> starSRPIPAddress
> Object
> starBGPPeerReachable
> Object ID
> enterprises.8164.2.122
> Description
> The monitored BGP peer is now Reachable. This notification can represent the initial detection of the peer's state, or the re-connection to a peer after a starBGPPeerDown notification.
> Action to be Taken: No action is required.
> Objects
> starContextName
> starSRPIPAddress
> starUDPPortNum
> starBGPPeerIPAddress
> Object
> starBGPPeerUnreachable
> Object ID
> enterprises.8164.2.123
> Description
> The monitored BGP peer is now Unreachable.
> Action to be Taken: Verify that the BGP Peer is running and is properly configured. Verify the network link to the BGP Peer.
> Clear Condition: This condition is cleared when communication with the BGP peer is reestablished.
> Condition Clear Alarm: This condition is cleared by a starBGPPeerReachable notification.
> Objects
> starContextName
> starSRPIPAddress
> starUDPPortNum
> starBGPPeerIPAddress
> Object
> starSRPAAAReachable
> Object ID
> enterprises.8164.2.124
> Description
> The SRP AAA monitor has found a reachable AAA server. This notification can represent the initial detection of an AAA server, or the restoration of reachability after a starSRPAAAUnreachable notification. This notification is only generated if there was previously no reachable AAA server.
> Action to be Taken: No action required.
> Objects
> starContextName
> starSRPIPAddress
> starUDPPortNum
> Object
> starSRPAAAUnreachable
> Object ID
> enterprises.8164.2.125
> Description
> The SRP AAA monitor has determined that all AAA servers are unreachable.
> Action to be Taken: Verify the state of the configured AAA server(s) and restart them if required. Verify the network link to the AAA Server(s). Configure additional AAA servers if required.
> Clear Condition:This condition is cleared when communication with any single AAA service is (re)established.
> Condition Clear Alarm: This condition is cleared by a starSRPAAAReachable notification.
> Objects
> starContextName
> starSRPIPAddress
> starUDPPortNum
> Object
> starHASwitchoverInitiated
> Object ID
> enterprises.8164.2.126
> Description
> An HA Switchover operation has been initiated by an operator.
> Action to be Taken: Verify that the switchover was a planned operator action.
> Objects
> starContextName
> starSRPIPAddress
> Object
> starSRPCheckpointFailure
> Object ID
> enterprises.8164.2.127
> Description
> The system has detected that a checkpoint messaged failed to be sent successfully to the standby HA. If the active HA were to fail, this information will be lost.
> Action to be Taken: Verify the communication path to the Standby HA.
> Objects
> starContextName
> starSRPIPAddress
> Object
> starSRPConfigOutOfSync
> Object ID
> enterprises.8164.2.128
> Description
> The system has detected that the standby HA has a different configuration than the active HA. In the event of a failure of the active HA, it is possible that the standby HA is not configured properly to be able to take over.
> Action to be Taken: Update the configuration of the standby HA to match the active HA.
> Clear Condition: This condition is cleared when the active HA confirms that the standby HA has an identify configuration.
> Condition Clear Alarm: This condition is cleared by a starSRPConfigInSync notification.
> Objects
> starContextName
> starSRPIPAddress
> Object
> starSRPConfigInSync
> Object ID
> enterprises.8164.2.129
> Description
> The system has detected that the standby HA has a matching configuration as the active HA. This notification is generated only after a starSRPConfigOutOfSync notification.
> Action to be Taken: No action required.
> Objects
> starContextName
> starSRPIPAddress
> Object
> starGESwitchFailure
> Object ID
> enterprises.8164.2.130
> Description
> A failure of an internal Gigabit Ethernet switch has been detected. If it is possible to determine the slow containing the failed switch it is identified in starSlotNum, otherwise starSlotNum is 0.
> Action to be Taken: If this condition persists, the identified card needs to be replaced.
> Objects
> starSlotNum
> Object
> starSIPRouteServerAvailable
> Object ID
> enterprises.8164.2.131
> Description
> SIP route server is available.
> Action to be Taken: No action required.
> Objects
> starSIPRouteServerVpnName
> starSIPRouteServerVmgName
> starSIPRouteServerAsName
> starSIPRouteServerIpAddr
> Object
> starSIPRouteServerUnavailable
> Object ID
> enterprises.8164.2.132
> Description
> SIPsession has failed since the route server is unavailable.
> Action to be Taken: Operator has to check the reason for the unavailability of the server an act accordingly.
> Objects
> starSIPRouteServerVpnName
> starSIPRouteServerVmgName
> starSIPRouteServerAsName
> starSIPRouteServerIpAddr
> Object
> starFMDMaxCallRateReached
> Object ID
> enterprises.8164.2.133
> Description
> FMD max call rate reached.
> Action to be Taken: Increase the value of fmd-max-call-rate or set no fmd-max-call-rate.
> Condition Clear Alarm: This condition is cleared by a starFMDCallRateUnderControl notification
> Objects
> starVIMServiceVpnName
> starVIMServiceInstanceId
> starVIMServiceFMDMaxCallRate
> starVIMServiceFMDContinuousLoadCount
> Object
> starFMDCallRateUnderControl
> Object ID
> enterprises.8164.2.134
> Description
> FMD call rate is under control.
> Action to be Taken: No action required.
> Objects
> starVIMServiceVpnName
> starVIMServiceInstanceId
> starVIMServiceFMDMaxCallRate
> starVIMServiceFMDContinuousLoadCount
> Object
> starStorageServerCPUBusy
> Object ID
> enterprises.8164.2.135
> Deseceiption
> GTPP Storage Server is experiencing high CPU usage. The usage has exceeded an operator-configure value.
> Important: Note that this is an external server, not part of the ST16/ASR 5000 - series hardware.
> Probable Cause: The amount of information being sent to the Storage Server is approaching the server's capacity, the Storage Server has other tasks running on it which are taking CPU time, a problem with the Storage Server is causing the CPU to be abnormally busy.
> Condition Clear Alarm: This condition is cleared by a starStorageServerCPUNormal notification
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starThreshPct
> starThreshMeasuredPct
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerCPUNormal
> Object ID
> enterprises.8164.2.136
> Description
> GTPP Storage Server CPU usage has returned to a normal range.
> Important: Note that this is an external server, not part of the chassis.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starThreshPct
> starThreshMeasuredPct
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerDiskSpaceLow
> Object ID
> enterprises.8164.2.137
> Description
> GTPP Storage Server is experiencing low available disk space. The available disk space has gone below an operator-configure value.
> Important: Note that this is an external server, not part of the chassis.
> Description
> Probable Cause: This can be caused by an improper configuration, or by the failure or removal of other cards in the system.
> Condition Clear Alarm: This condition is cleared by a starStorageServerDiskSpaceOK notification.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starThreshGB
> starThreshMeasuredGB
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerDiskSpaceOK
> Object ID
> enterprises.8164.2.138
> Description
> Available disk space for GTPP Storage Server is now in a normal range.
> Important: Note that this is an external server, not part of the chassis.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starThreshPct
> starThreshMeasuredPct
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starCardSPOFAlarm
> Object ID
> enterprises.8164.2.139
> Description
> The identified card is a Single Point of Failure (SPOF). There is no redundant card available to take over in the event of a failure.
> Probable Cause: This can be caused by an improper configuration, or by the failure or removal of other cards in the system.
> Action to be Taken:Install or configure additional redundant cards.
> Condition Clear Alarm: A starCardSPOFClear notification will be generated is a redundant card becomes available. Notifications like starCardDown could also obsolete this notification.
> Objects
> starSlotNum
> starCardType
> Object
> starCardSPOFClear
> Object ID
> enterprises.8164.2.140
> Description
> The identified card is no longer a Single Point of Failure (SPOF).
> Objects
> starSlotNum
> starCardType
> Object
> starStorageServerOldGcdrPending
> Object ID
> enterprises.8164.2.141
> Description
> GCDR files on the Storage Server have been unprocessed since the configured threshold value of time period.
> Important: Note that this is an external server, not part of the ST-16.
> Description
> Probable Cause: No action has been taken long for the GCDR files generated by Storage Server.
> Condition Clear Alarm: This condition is cleared by a starStorageServerOldGcdrCleared notification.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starThreshInt
> starThreshMeasuredInt
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerOldGcdrCleared
> Object ID
> enterprises.8164.2.142
> Description
> GCDR files on the Storage Server have been processed on the Storage Server. The threshold condition is now clear.
> Important: Note that this is an external server, not part of the ST16/ASR 5000-series hardware.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starThreshInt
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starLoginFailure
> Object ID
> enterprises.8164.2.143
> Description
> A login failure occurred attempting to establish a CLI or FTP session.
> Objects
> starCLITtyname
> starCLIRemoteIPAddr
> starCLIType
> Object Group
> starIPSGServiceStart
> Object ID
> enterprises.8164.2.144
> Description
> A IP Services Gateway (IPSG) Service has started.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starIPSGServiceStop
> Object ID
> enterprises.8164.2.145
> Description
> A IP Services Gateway (IPSG) Service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the IPSG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the IPSG service is operational.
> Condition Clear Alarm: A starIPSGServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starHAUnreachable
> Object ID
> enterprises.8164.2.146
> Description
> A monitored HA is unreachable from the identified FA Service.
> Condition Clear Alarm: A starHAReachable notification will be generated when the HA becomes reachable.
> Objects
> starServiceVPNName
> starServiceServName
> starServiceFAIpAddr
> starServiceHAIpAddr
> Object
> starHAReachable
> Object ID
> enterprises.8164.2.147
> Description
> A monitored HA is now reachable. A starHAReachable notification is only generated for monitored HA's which previously were marked unreachable.
> Objects
> starServiceVPNName
> starServiceServName
> starServiceFAIpAddr
> starServiceHAIpAddr
> Object
> starASNGWServiceStart
> Object ID
> enterprises.8164.2.148
> Description
> A WiMAX ASN Gateway (ASNGW) Service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starASNGWServiceStop
> Object ID
> enterprises.8164.2.149
> Description
> A WiMAX ASN Gateway (ASNGW) Service has stopped.
> Probable Cause: This is typically caused by operator intervention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the ASNGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Condition Clear Alarm:A starASNGWServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starTaskFailed
> Object ID
> enterprises.8164.2.150
> Description
> A non-critical task has failed and the appropriate recovery steps begun. The failing task will be restarted.
> Probable Cause:Software error.
> Actions to be Taken: Examine the admin logs for an indication of the source of the failure.
> Clear Condition: Verify that the task has been restarted.
> Condition Clear Alarm: A starTaskRestart notification will be generated when task has successfully restarted.
> Objects
> starTaskFacilityName
> starTaskInstance
> starTaskCard
> starTaskCPU
> Object
> starTaskRestart
> Object ID
> enterprises.8164.2.151
> Description
> A non-critical task has restarted after an earlier failure.
> Actions to be Taken: None.
> Objects
> starTaskFacilityName
> starTaskInstance
> starTaskCard
> starTaskCPU
> Object
> starCSCFServiceStart
> Object ID
> enterprises.8164.2.152
> Description
> A CSCF Service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starCSCFServiceStop
> Object ID
> enterprises.8164.2.153
> Description
> A CSCF Service has stopped.
> Probable Cause: This is typically caused by operator intervention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the CSCF service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the CSCF service is operational.
> Condition Clear Alarm: A starCSCFServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starDhcpServiceStarted
> Object ID
> enterprises.8164.2.154
> Description
> A DHCP Service has started.
> Action to be Taken: No action required.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerPort
> starSessGGSNPeerAddr
> Object
> starDhcpServiceStopped
> Object ID
> enterprises.8164.2.155
> Description
> A DHCP Service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the DHCP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the DHCP service is operational.
> Condition Clear Alarm: A starDHCPServiceStart notification will be generated when the service is restarted.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerPort
> starSessGGSNPeerAddr
> Object
> starContFiltDBError
> Object ID
> enterprises.8164.2.156
> Description
> The Content Filtering OPTCMDB file error displayed with an error code.
> Action to be Taken: If no OPTCMDB file is there in the specified directory then Place a OPTCMDB-FULL file in the directory and give an upgrade command. If the error is related to merge/loading failure then give an upgrade command with a new inc/full database file.
> Condition Clear Alarm: This condition is cleared by a starContFiltDBErrorClear notification.
> Objects
> starContFiltCFFilename
> starContFiltCFErrorCode
> Object
> starContFiltDBErrorClear
> Object ID
> enterprises.8164.2.157
> Description
> The Content Filtering OPTCMDB file error removed.
> Action to be Taken: No action required.
> Objects
> starContFiltCFFilename
> starContFiltCFErrorCode
> Object
> starBLDBError
> Object ID
> enterprises.8164.2.158
> Description
> The Blacklisting OPTBLDB file error displayed with an error code.
> Action to be Taken: If no or invalid OPTBLDB file is there in the specified directory then Place a OPTBLDB_FULL file in the directory and give an upgrade command.
> Condition Clear Alarm: This condition is cleared by a starBLDBErrorClear notification.
> Objects
> starBLFilename
> starBLErrorCode
> Object
> starBLDBErrorClear
> Object ID
> enterprises.8164.2.159
> Description
> The Blacklisting OPTBLDB file error removed
> Objects
> starBLFilename
> starBLErrorCode
> Object
> starContFiltDBUpgradeError
> Object ID
> enterprises.8164.2.160
> Description
> The Content Filtering OPTCMDB file error displayed with an error code.
> Action to be Taken:Place a valid OPTCMDB-FULL file or OPTCMDB_INCR file in the directory and give an upgrade command.
> Condition Clear Alarm: This condition is cleared by a starContFiltDBUpgradeErrorClear notification.
> Objects
> starContFiltCFUpgradeFilename
> starContFiltCFUpgradeErrorCode
> Object
> starContFiltDBUpgradeErrorClear
> Object ID
> enterprises.8164.2.161
> Description
> The Content Filtering OPTCMDB file error removed.
> Action to be Taken: No action required.
> Objects
> starContFiltCFUpgradeFilename
> starContFiltCFUpgradeErrorCode
> Object
> starBLDBUpgradeError
> Object ID
> enterprises.8164.2.162
> Description
> The Blacklisting OPTBLDB file error displayed with an error code.
> Action to be Taken: No action required
> Condition Cleaar Alarm: This condition is cleared by a starBLDBUpgradeErrorClear.
> Objects
> starBLUpgradeFilename
> starBLUpgradeErrorCode
> Object
> starBLDBUpgradeErrorClear
> Object ID
> enterprises.8164.2.163
> Description
> The Blacklisting OPTBLDB file error removed.
> Action to be Taken: No action required.
> Objects
> starBLUpgradeFilename
> starBLUpgradeErrorCode
> Object
> starIPSECDynTunUp
> Object ID
> enterprises.8164.2.164
> Description
> IPSEC Dynamic Tunnel Up.
> Action to be Taken: No action required.
> Objects
> starIPSECContextName
> starIPSECPolicyName
> starIPSECDynPolicyType
> starIPSECPolicyPayloadType
> starIPSECLocalGateway
> starIPSECRemoteGateway
> Object
> starIPSECDynTunDown
> Object ID
> enterprises.8164.2.165
> Description
> IPSEC Dynamic Tunnel Down.
> Objects
> starIPSECContextName
> starIPSECPolicyName
> starIPSECDynPolicyType
> starIPSECDynPolicyPayloadType
> starIPSECLocalGateway
> starIPSECRemoteGateway
> Object
> starHeartbeat
> Object ID
> enterprises.8164.2.166
> Description
> Periodic SNMP heartbeat. A starHeartbeat notification can be generated periodically if the system is configured to do so. These notifications serve only to validate that there is communication to external entities which sink SNMP notifications
> Object
> starOverloadSystem
> Object ID
> enterprises.8164.2.167
> Description
> A system-wide congestion overload condition has occurred.
> Probable Cause: This is the result of an operator-configured congestion overload value reached. This notification indicated a chassis-wide overload condition, typically overall system usage reaching some fraction of capacity. Once this limit is reached, the configured behavior is taken. This will cause certain older and/or dormant calls to be dropped in favor of newer calls. Note that this is similar to, but different than, the starCongestion notification. Typically the 'overload' condition will be configured to trigger at an earlier point.
> Actions to be Taken: Verify that the congestion overload thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online.
> Clear Condition: This system is cleared when the use of the specific resource falls below the configured limit.
> Condition Clear Alarm: A starOverloadSystemClear notification is sent when the system overload condition is clear.
> Objects
> starCongestionResourceType
> Object
> starOverloadSystemClear
> Object ID
> enterprises.8164.2.168
> Description
> A system-wide congestion overload condition has cleared
> Object
> starOverloadService
> Object ID
> enterprises.8164.2.169
> Description
> A service-specific congestion overload condition has occurred.
> Probable Cause: This is the result of an operator-configured congestion overload value reached. This notification indicated a service-specific overload condition, typically the use of the service reaching some fraction of capacity. Once this limit is reached, the configured behavior is taken. This will cause certain older and/or dormant calls to be dropped in favor of newer calls. Note that this is similar to, but different than, the starCongestion notification. Typically the 'overload' condition will be configured to trigger at an earlier point. Since this is a service-specific notification, it is possible to receive multiple notifications for different services.
> Action to be Taken:Verify that the congestion overload thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online.
> Clear Condition: This system is cleared when the use of the specific resource falls below the configured limit.
> Condition Clear Alarm: A starOverloadServiceClear notification is sent when the service-specific overload condition is clear.
> Objects
> starCongestionResourceType
> starServiceVpnName
> starServiceServName
> Object
> starOverloadServiceClear
> Object ID
> enterprises.8164.2.170
> Description
> A service-specific congestion overload condition has cleared
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starStorageServerClusterStateChange
> Object ID
> enterprises.8164.2.171
> Description
> GTPP Storage Server cluster state has been changed. GTPP Storage Server may have gone offline from all the nodes or switchover has been occurred.
> Important: Note that this is an external server, not part of the ST16/ASR 5000-series hardware.
> Probable Cause: GTPP Storage Server cluster hardware/software component failure or maintenance of GTPP Storage Server is in progress.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starGSSClusterName
> starGSSClusterRgName
> starGSSClusterRsName
> starGSSClusterNodeState
> starGSSClusterPrevOnlineNode
> Object
> starStorageServerCluswitchOver
> Object ID
> enterprises.8164.2.172
> Description
> GTPP Storage Server switchover from current online node to next available node in cluster.
> Important: Note that this is an external server, not part of the ST16/ASR 5000-series hardware.
> Probable Cause: GTPP storage server cluster hardware/software component failure or maintenance of GTPP storage server is in progress.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starGSSClusterName
> starGSSClusterRgName
> starGSSClusterFromNode
> starGSSClusterToNode
> Object
> starStorageServerClusPathFail
> Object ID
> enterprises.8164.2.173
> Description
> GTPP Storage Server cluster disk path failure has been occurred.
> Important: Note that this is an external server, not part of the ST16/ASR 5000-series hardware.
> Probable Cause: Fibre cable may have been damaged, fibre cable may have been pulled out or disk fault may have been occurred.
> Condition Clear Alarm: This condition is cleared by a starStorageServerClusPathOK notification.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starGSSDiskPath
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerClusPathOK
> Object ID
> enterprises.8164.2.174
> Description
> GTPP Storage Server cluster disk path failure has been restored to ok state.
> Important: Note that this is an external server, not part of the ST16/ASR 5000-series hardware.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starGSSDiskPath
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerClusInterCFail
> Object ID
> enterprises.8164.2.175
> Description
> GTPP Storage Server cluster transport path (Interconnect) failure has been occurred.
> Important: Note that this is an external server, not part of the ST16/ASR 5000-series hardware.
> Probable Cause: Interconnect interface may have been failed, Interconnect interface cable may have been pulled out.
> Condition Clear Alarm:This condition is cleared by a starStorageServerClusInterCOK notification.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starGSSTransportPath
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerClusInterCOK
> Object ID
> enterprises.8164.2.176
> Description
> GTPP Storage Server cluster transport path (Interconnect) failure has been restored to an operational state.
> Important: Note that this is an external server, not part of the ST16/ASR 5000-series hardware.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starGSSTransportPath
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerClusIntfFail
> Object ID
> enterprises.8164.2.177
> Description
> GTPP Storage Server cluster disk path failure has been occurred.
> Important: Note that this is an external server, not part of the ST16/ASR 5000-series hardware
> Probable Cause: Interface may have been failed, interface cable may have been pulled out.
> Condition Clear Alarm: This condition is cleared by a starStorageServerClusIntfOK notification.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starGSSIPMPGroupName
> starGSSInterfaceName
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerClusIntfOK
> Object ID
> enterprises.8164.2.178
> Description
> GTPP Storage Server cluster GE Interface failure has been restored to ok state.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starGSSIPMPGroupName
> starGSSInterfaceName
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerMemLow
> Object ID
> enterprises.8164.2.179
> Description
> GTPP Storage Server is experiencing a low memory condition.
> Description
> Probable Cause: The amount of free memory used by Storage Server is approaching the server's capacity.
> Condition Clear Alarm:This condition is cleared by a starStorageServerMemNormal notification.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starThreshMB
> starThreshMeasuredMB
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starStorageServerMemNormal
> Object ID
> enterprises.8164.2.180
> Description
> GTPP Storage Server Memory usage has returned to a normal range.
> Important: Note that this is an external server, not part of the ST16.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starThreshMB
> starThreshMeasuredMB
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starPDIFServiceStart
> Object ID
> enterprises.8164.2.181
> Description
> A PDIF Service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPDIFServiceStop
> Object ID
> enterprises.8164.2.182
> Description
> A PDIF Service has stopped.
> Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs) to support the running configuration.
> Action to be Taken: If the PDIF service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the PDIF service is operational.
> Condition Clear Alarm: A starPDIFServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSessMgrRecoveryComplete
> Object ID
> enterprises.8164.2.183
> Description
> A Sess Mgr Recovery Complete.
> Probable Cause: This is typically caused by session manager task fails and successfully completed recovery.
> Action to be Taken: None.
> Objects
> starCPUSlot
> starCPUNumber
> Object
> starDiameterPeerDown
> Object ID
> enterprises.8164.2.184
> Description
> A diameter peer is down.
> Problem Cause: The diameter peer has failed, or a network connectivity prevents reaching the peer.
> Condition Clear Alarm: A starDiameterPeerUp notification will be generated when the peer is up.
> Objects
> starDiameterVpnName
> starDiameterPeerAddr
> starDiameterEndpointName
> Object
> starDiameterPeerUp
> Object ID
> enterprises.8164.2.185
> Description
> A diameter peer is up. This notification is only generated for peers which have previously been declared down.
> Objects
> starDiameterVpnName
> starDiameterPeerAddr
> starDiameterEndpointName
> Object
> starDiameterServerUnreachable
> Object ID
> enterprises.8164.2.186
> Description
> A diameter server is down.
> Problem Cause: The diameter server has failed, or a network connectivity prevents reaching the server.
> Condition Clear Alarm: A starDiameterServerReachable notification will be generated when the server is reachable.
> Objects
> starServiceVpnName
> starDiameterPeerAddr
> starDiameterEndpointName
> Object
> starDiameterServerReachable
> Object ID
> enterprises.8164.2.187
> Description
> A diameter server is up. This notification is only generated for servers which have previously been declared unreachable.
> Objects
> starServiceVpnName
> starDiameterPeerAddr
> starDiameterEndpointName
> Object
> starCDRFileRemoved
> Object ID
> enterprises.8164.2.188
> Description
> A Charging Data Record (CDR) file has been deleted from the system due to a lack of available storage space. When required, the system deletes old files to make space for new files. This notification is only generated when specifically enabled on the system.
> Probable Cause:CDR files are not being moved off the system, or these files are not being deleted after they have been transferred.
> Objects
> starCDRFilename
> Object
> starCSCFPeerServerReachable
> Object ID
> enterprises.8164.2.189
> Description
> A peer server is reachable
> Objects
> starServiceVPNName
> starServiceServName
> starServicePeerServerName
> Object
> starCSCFPeerServerUnreachable
> Object ID
> enterprises.8164.2.190
> Description
> A peer server is reachable
> Objects
> starServiceVPNName
> starServiceServName
> starServicePeerServerName
> Object
> starCLIConfigMode
> Object ID
> enterprises.8164.2.192
> Description
> An interactive CLI session has an “enter configuration” mode for the specified context. Thus the CLI user can potentially start entering configuration commands that could impact the entire system. Note that this notification is not enabled by default; it is only generated if the system is specifically configured to enable it.
> Objects
> starCLIUsername
> starCLIContext
> Object
> starSGSNServiceStart
> Object ID
> enterprises.8164.2.194
> Description
> A SGSN Service has started.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSGSNServiceStop
> Object ID
> enterprises.8164.2.195
> Description
> A SGSN Service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the SGSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the SGSN service is operational.
> Condition Clear Alarm: A starSGSNServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName,
> starServiceServName
> Object
> starM3UAPCUnavailable
> Object ID
> enterprises.8164.2.196
> Description
> M3UA route to the Point code becomes unavailable.
> Probable Cause: Received destination unavailable (DUNA) message SCTP association is down Remote peer server is down.
> Action to be taken: Verify that the peer server is UP.
> Objects
> starSS7rdId
> starSS7Pc
> starSS7M3UAPsId
> Object
> starM3UAPCAvailable
> Object ID
> enterprises.8164.2.197
> Description
> M3UA route to the Point code becomes available.
> Probable Cause: Received destination available (DAVA) message. SCTP Association is up. Remote peer server is up.
> Condition Clear Alarm: A starM3UAPCAvailable message is generated only after a starM3UAPCUnavailable message was generated.
> Objects
> starSS7M3UAPsId
> starSS7Pc
> starSS7rdId
> Object
> starDynPkgLoadError
> Object ID
> enterprises.8164.2.1103
> Description
> The Dynamic rater package error displayed with an error code. Condition Clear Alarm: This condition is cleared by a starDynPkgLoadErrorClear notification
> Objects
> starDynPkgFilename
> starDynCFErrorCode
> Object
> starDynPkgLoadErrorClear
> Object ID
> enterprises.8164.2.1104
> Description
> The Dynamic rater package error removed.
> Objects
> starDynPkgFilename
> starDynCFErrorCode
> Object
> starDynPkgUpgradeError
> Object ID
> enterprises.8164.2.1105
> Description
> The Dynamic rater package error displayed with an error code. This condition is cleared by a starDynPkgUpgradeErrorClear . The Dynamic rater package error displayed with an error code.
> Objects
> starDynPkgUpgradeFilename
> starDynCFUpgradeErrorCode
> Object
> starDynPkgUpgradeErrorClear
> Object ID
> enterprises.8164.2.1106
> Description
> The Dynamic Rater package error removed.
> Objects
> starDynPkgUpgradeFilename
> starDynCFUpgradeErrorCode
> Object
> starCSCFPeerServerUnavailable
> Object ID
> enterprises.8164.2.1107
> Description
> Peer server is unavailable
> Objects
> starCSCFPeerServerVpnName
> starCSCFPeerServerSvcName
> starCSCFPeerServerName
> Object
> starCSCFPeerServerOutofService
> Object ID
> enterprises.8164.2.1108
> Description
> Peer server is out-of-service
> Objects
> starCSCFPeerServerVpnName
> starCSCFPeerServerSvcName
> starCSCFPeerServerName
> Object
> starCSCFPeerServerInService
> Object ID
> enterprises.8164.2.1109
> Description
> Peer server unavailable and/or out of service condition cleared.
> Objects
> starCSCFPeerServerVpnName
> starCSCFPeerServerSvcName
> starCSCFPeerServerName
> Object
> starThreshCPUUtilization
> Object ID
> enterprises.8164.2.200
> Description
> The overall CPU utilization for the identified processor has exceeded for configured threshold value for the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCPUUtilization notification will be generated when the measured value falls below the threshold.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearCPUUtilization
> Object ID
> enterprises.8164.2.201
> Description
> The threshold condition is now clear.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshCPUMemory
> Object ID
> enterprises.8164.2.202
> Description
> The amount of available memory for the identified processor has fallen below the configured threshold value.
> Probable Cause: This is a user configurable threshold. Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCPUMemory notification will be generated when the measured value falls below the threshold.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCPUMemory
> Object ID
> enterprises.8164.2.203
> Description
> The threshold condition is now clear.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshLicense
> Object ID
> enterprises.8164.2.204
> Description
> The percentage available, licensed subscribers has fallen below the configured threshold value.
> Probable Cause:This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearLicense notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshPct
> starThreshMeasuredPct
> starServiceType
> Object
> starThreshClearLicense
> Object ID
> enterprises.8164.2.205
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> starServiceType
> Object
> starThreshSubscriberTotal
> Object ID
> enterprises.8164.2.206
> Description
> The total number of subscribers is above the configured threshold value.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearSubscriberTotal notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearSubscriberTotal
> Object ID
> enterprises.8164.2.207
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshSubscriberActive
> Object ID
> enterprises.8164.2.208
> Description
> The total number of active subscribers is above the configured threshold value.
> Probable Cause: This is a user configurable threshold. Condition
> Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearSubscriberActive notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearSubscriberActive
> Object ID
> enterprises.8164.2.209
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPortRxUtil
> Object ID
> enterprises.8164.2.210
> Description
> The Rx utilization of the port has exceeded the configured threshold value during the current monitoring period.
> Probable Cause:This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPortRxUtil notification will be generated when the measured value falls below the threshold.
> Objects
> starPortSlot
> starPortNum
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearPortRxUtil
> Object ID
> enterprises.8164.2.211
> Description
> The threshold condition is now clear.
> Objects
> starPortSlot
> starPortNum
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshPortTxUtil
> Object ID
> enterprises.8164.2.212
> Description
> The Tx utilization of the port has exceeded the configured threshold value during the current monitoring period.
> Probable Cause:This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPortTxUtil notification will be generated when the measured value falls below the threshold.
> Objects
> starPortSlot
> starPortNum
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearPortTxUtil
> Object ID
> enterprises.8164.2.213
> Description
> The threshold condition is now clear.
> Objects
> starPortSlot
> starPortNum
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshPortHighActivity
> Object ID
> enterprises.8164.2.214
> Description
> The number of seconds of 'high activity' time on the port has exceeded the configured threshold value during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPortHighActivity notification is generated when the measured value falls below the threshold.
> Objects
> starPortSlot
> starPortNum
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPortHighActivity
> Object ID
> enterprises.8164.2.215
> Description
> The threshold condition is now clear.
> Objects
> starPortSlot
> starPortNum
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshAAAAuthFail
> Object ID
> enterprises.8164.2.216
> Description
> The number of AAA authentication failures has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAuthFail notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearAAAAuthFail
> Object ID
> enterprises.8164.2.217
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshAAAAuthFailRate
> Object ID
> enterprises.8164.2.218
> Description
> The percentage of AAA authentication requests which failed has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAuthFailRate notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearAAAAuthFailRate
> Object ID
> enterprises.8164.2.219
> Description
> The threshold condition is now clear.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshAAAAcctFail
> Object ID
> enterprises.8164.2.220
> Description
> The number of AAA accounting failures has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAcctFail notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearAAAAcctFail
> Object ID
> enterprises.8164.2.221
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshAAAAcctFailRate
> Object ID
> enterprises.8164.2.222
> Description
> The percentage of AAA accounting requests which failed has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAAcctFailRate notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearAAAAcctFailRate
> Object ID
> enterprises.8164.2.223
> Description
> The threshold condition is now clear.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshAAARetryRate
> Object ID
> enterprises.8164.2.224
> Description
> The percentage of AAA requests which has to be retried has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAARetryRate notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearAAARetryRate
> Object ID
> enterprises.8164.2.225
> Description
> The threshold condition is now clear.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshCallSetup
> Object ID
> enterprises.8164.2.226
> Description
> The number of call setup operations has exceeded the configured threshold during the current monitoring period.
> Probable Cause:This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCallSetup notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCallSetup
> Object ID
> enterprises.8164.2.227
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCallSetupFailure
> Object ID
> enterprises.8164.2.228
> Description
> The number of call setup operations which failed has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCallSetupFailure notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCallSetupFailure
> Object ID
> enterprises.8164.2.229
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCallRejectNoResource
> Object ID
> enterprises.8164.2.230
> Description
> The number of call setup operations which were rejected due to a no resource condition has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCallRejectNoResource notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCallRejectNoResource
> Object ID
> enterprises.8164.2.231
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPacketsFilteredDropped
> Object ID
> enterprises.8164.2.232
> Description
> The number of user data packets filtered has exceeded the configured threshold for the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in an alarm mode, a starThreshClearPacketsFilteredDropped notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPacketsFilteredDropped
> Object ID
> enterprises.8164.2.233
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPacketsForwarded
> Object ID
> enterprises.8164.2.234
> Description
> The number of user data packets forwarded has exceeded the configured threshold for the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPacketsForwarded notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPacketsForwarded
> Object ID
> enterprises.8164.2.235
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshSessCPUThroughput
> Object ID
> enterprises.8164.2.236
> Description
> The total session throughout for the specified processor has exceeded the configured threshold for the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearSessCPUThroughput notification will be generated when the measured value falls below the threshold.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshMB
> starThreshMeasuredMB
> Object
> starThreshClearSessCPUThroughput
> Object ID
> enterprises.8164.2.237
> Description
> The threshold condition is now clear.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshMB
> starThreshMeasuredMB
> Object
> starThreshIPPoolAvail
> Object ID
> enterprises.8164.2.238
> Description
> The available IP pool addresses in a context has fallen below the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPPoolAvail notification will be generated when the measured value falls below the threshold.
> Objects
> starIPPoolContext
> starIPPoolGroup
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearIPPoolAvail
> Object ID
> enterprises.8164.2.239
> Description
> The threshold condition is now clear.
> Objects
> starIPPoolContext
> starIPPoolGroup
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCPUUtilization10Sec
> Object ID
> enterprises.8164.2.240
> Description
> The CPU utilization of 10 second measurement for the identified processor has exceeded for configured threshold value for the current monitoring period.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearCPUUtilization10Sec
> Object ID
> enterprises.8164.2.241
> Description
> The threshold condition is now clear.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshCPULoad
> Object ID
> enterprises.8164.2.242
> Description
> The CPU load for the identified processor has exceeded for configured threshold value for the current monitoring period.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCPULoad
> Object ID
> enterprises.8164.2.243
> Description
> The threshold condition is now clear.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCPUMemUsage
> Object ID
> enterprises.8164.2.244
> Description
> The CPU mem usage for the identified processor has exceeded for configured threshold value for the current monitoring period.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearCPUMemUsage
> Object ID
> enterprises.8164.2.245
> Description
> The threshold condition is now clear.
> Objects
> starCPUSlot
> starCPUNumber
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshPDSNSessions
> Object ID
> enterprises.8164.2.246
> Description
> The total number of PDSN sessions is above the configured threshold value.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPDSNSessions
> Object ID
> enterprises.8164.2.247
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshGGSNSessions
> Object ID
> enterprises.8164.2.248
> Description
> The total number of GGSN sessions is above the configured threshold value.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearGGSNSessions
> Object ID
> enterprises.8164.2.249
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshHASessions
> Object ID
> enterprises.8164.2.250
> Description
> The total number of HA sessions is above the configured threshold value.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearHASessions
> Object ID
> enterprises.8164.2.251
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshLNSSessions
> Object ID
> enterprises.8164.2.252
> Description
> The total number of L2TP LNS sessions is above the configured threshold value.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearLNSSessions
> Object ID
> enterprises.8164.2.253
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPerServicePDSNSessions
> Object ID
> enterprises.8164.2.254
> Description
> The total number of PDSN sessions in a service is above the configured threshold value.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPerServicePDSNSessions
> Object ID
> enterprises.8164.2.255
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPerServiceGGSNSessions
> Object ID
> enterprises.8164.2.256
> Description
> The total number of GGSN sessions in a service is above the configured threshold value.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPerServiceGGSNSessions
> Object ID
> enterprises.8164.2.257
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPerServiceHASessions
> Object ID
> enterprises.8164.2.258
> Description
> The total number of HA sessions in a service is above the configured threshold value.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPerServiceHASessions
> Object ID
> enterprises.8164.2.259
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPerServiceLNSSessions
> Object ID
> enterprises.8164.2.260
> Description
> The total number of L2TP LNS sessions in a service is above the configured threshold value.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPerServiceLNSSessions
> Object ID
> enterprises.8164.2.261
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshIPPoolHold
> Object ID
> enterprises.8164.2.262
> Description
> The percentage IP pool addresses in HOLD state in a context has gone above the configured threshold.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearIPPoolHold
> Object ID
> enterprises.8164.2.263
> Description
> The threshold condition is now clear.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshIPPoolUsed
> Object ID
> enterprises.8164.2.264
> Description
> The percentage IP pool addresses in USED state in a context has gone above the configured threshold.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearIPPoolUsed
> Object ID
> enterprises.8164.2.265
> Description
> The threshold condition is now clear.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshIPPoolRelease
> Object ID
> enterprises.8164.2.266
> Description
> The percentage IP pool addresses in RELEASE state in a context has gone above the configured threshold.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearIPPoolRelease
> Object ID
> enterprises.8164.2.267
> Description
> The threshold condition is now clear.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshIPPoolFree
> Object ID
> enterprises.8164.2.268
> Description
> The percentage IP pool addresses in HOLD state in a context has gone below the configured threshold.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearIPPoolFree
> Object ID
> enterprises.8164.2.269
> Description
> The threshold condition is now clear.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshAAAAcctArchive
> Object ID
> enterprises.8164.2.270
> Description
> The AAA accounting archive size has gone above the configured threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearAAAAcctArchive
> Object ID
> enterprises.8164.2.271
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPortSpecRxUtil
> Object ID
> enterprises.8164.2.272
> Description
> The Rx utilization of the port has exceeded the configured threshold value during the current monitoring period.
> Probable Cause:This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPortSpecRxUtil notification will be generated when the measured value falls below the threshold.
> Objects
> starPortSlot
> starPortNum
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearPortSpecRxUtil
> Object ID
> enterprises.8164.2.273
> Description
> The threshold condition is now clear.
> Objects
> starPortSlot
> starPortNum
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshPortSpecTxUtil
> Object ID
> enterprises.8164.2.274
> Description
> The Tx utilization of the port has exceeded the configured threshold value during the current monitoring period.
> Probable Cause:This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPortSpecTxUtil notification will be generated when the measured value falls below the threshold.
> Objects
> starPortSlot
> starPortNum
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearPortSpecTxUtil
> Object ID
> enterprises.8164.2.275
> Description
> The threshold condition is now clear.
> Objects
> starPortSlot
> starPortNum
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshHACallSetupRate
> Object ID
> enterprises.8164.2.276
> Description
> The per-context HA call setup rate (calls per second) has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in 'alarm' mode, a starThreshClearHACallSetupRate notification will be generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearHACallSetupRate
> Object ID
> enterprises.8164.2.277
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshHASvcCallSetupRate
> Object ID
> enterprises.8164.2.278
> Description
> The per-service HA Call setup rate (calls per second) has gone above the configured threshold Probable Cause: This is a user configurable threshold. Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearHASvcCallSetupRate notification will be generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearHASvcCallSetupRate
> Object ID
> enterprises.8164.2.279
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshHASvcRegReplyError
> Object ID
> enterprises.8164.2.280
> Description
> The per-service HA Reg Reply Error count has gone above the configured threshold
> Probable Cause: This is a user configurable threshold. Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearHASvcRegReplyError notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearHASvcRegReplyError
> Object ID
> enterprises.8164.2.281
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshHASvcReregReplyError
> Object ID
> enterprises.8164.2.282
> Description
> The per-service HA Rereg Reply Error count has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold. Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearHASvcReregReplyError notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearHASvcReregReplyError
> Object ID
> enterprises.8164.2.283
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshHASvcDeregReplyError
> Object ID
> enterprises.8164.2.284
> Description
> The per-service HA Dereg Reply Error count has gone above the configured threshold
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearHASvcDeregReplyError notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearHASvcDeregReplyError
> Object ID
> enterprises.8164.2.285
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshFASvcRegReplyError
> Object ID
> enterprises.8164.2.286
> Description
> The Per-Service FA Reg Reply Error count has gone above the configured threshold
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearFASvcRegReplyError notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearFASvcRegReplyError
> Object ID
> enterprises.8164.2.287
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPDSNCallSetupRate
> Object ID
> enterprises.8164.2.288
> Description
> The Per-Context PDSN Call Setup Rate (calls per second) has gone above the configured threshold
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDSNCallSetupRate notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPDSNCallSetupRate
> Object ID
> enterprises.8164.2.289
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPDSNSvcCallSetupRate
> Object ID
> enterprises.8164.2.290
> Description
> The Per-Service PDSN Call Setup Rate (calls per second) has gone above the configured threshold
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDSNSvcCallSetupRate notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPDSNSvcCallSetupRate
> Object ID
> enterprises.8164.2.291
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPDSNSvcA11RRPFailure
> Object ID
> enterprises.8164.2.292
> Description
> The Per-Service PDSN A11 RRP Failure count has gone above the configured threshold
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDSNSvcA11RRPFailure notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPDSNSvcA11RRPFailure
> Object ID
> enterprises.8164.2.293
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPDSNSvcA11RRQMsgDiscard
> Object ID
> enterprises.8164.2.294
> Description
> The Per-Service PDSN A11 RRQ Msg Discard count has gone above the configured threshold
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode a starThreshClearPDSNSvcA11RRQMsgDiscard notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPDSNSvcA11RRQMsgDiscard
> Object ID
> enterprises.8164.2.295
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPDSNSvcA11RACMsgDiscard
> Object ID
> enterprises.8164.2.296
> Description
> The Per-Service PDSN A11 RAC Msg Discard count has gone above the configured threshold
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode a starThreshClearPDSNSvcA11RACMsgDiscard notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPDSNSvcA11RACMsgDiscard
> Object ID
> enterprises.8164.2.297
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPDSNSvcA11PPPSendDiscard
> Object ID
> enterprises.8164.2.298
> Description
> he Per-Service PDSN A11 PPP Send Discard count has gone above the configured threshold
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearPDSNSvcA11PPPSendDiscard notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPDSNSvcA11PPPSendDiscard
> Object ID
> enterprises.8164.2.299
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshAAAMgrQueue
> Object ID
> enterprises.8164.2.300
> Description
> The Per-AAA Manager internal request queue usage has gone above the configured threshold
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearAAAMgrQueue is generated when the measured value falls below the threshold.
> Objects
> starTaskInstance
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearAAAMgrQueue
> Object ID
> enterprises.8164.2.301
> Description
> The threshold condition is now clear.
> Objects
> starTaskInstance
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshCPUOrbsWarn
> Object ID
> enterprises.8164.2.302
> Description
> The ORBs task has exceeding the CPU usage configured as a warning
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearCPUOrbsWarn
> Object ID
> enterprises.8164.2.303
> Description
> The threshold condition is now clear
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshCPUOrbsCritical
> Object ID
> enterprises.8164.2.304
> Description
> The ORBs task has exceeded the CPU usage configured as a critical error
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearCPUOrbsCritical
> Object ID
> enterprises.8164.2.305
> Description
> The threshold condition is now clear
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshRPSetupFailRate
> Object ID
> enterprises.8164.2.306
> Description
> The RP call setup failure rate has exceeded the configured threshold
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearRPSetupFailRate
> Object ID
> enterprises.8164.2.307
> Description
> The threshold condition is now clear
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshPPPSetupFailRate
> Object ID
> enterprises.8164.2.308
> Description
> The PPP call setup failure rate has exceeded the configured threshold
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearPPPSetupFailRate
> Object ID
> enterprises.8164.2.309
> Description
> The threshold condition is now clear
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshStorageUtilization
> Object ID
> enterprises.8164.2.310
> Description
> The utilization of a mass storage device has exceeded the configured threshold.
> Objects
> starStorageSlot
> starStorageName
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearStorageUtilization
> Object ID
> enterprises.8164.2.311
> Description
> The threshold condition is now clear.
> Objects
> starStorageSlot
> starStorageName
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshDCCAProtocolErrors
> Object ID
> enterprises.8164.2.312
> Description
> The number of DCCA Protocol Errors has exceeded the configured threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearDCCAProtocolErrors
> Object ID
> enterprises.8164.2.313
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshDCCABadAnswers
> Object ID
> enterprises.8164.2.314
> Description
> The number of DCCA BadAnswers has exceeded the configured threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearDCCABadAnswers
> Object ID
> enterprises.8164.2.315
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshDCCAUnknownRatingGroup
> Object ID
> enterprises.8164.2.316
> Description
> The number of DCCA UnknownRatingGroup has exceeded the configured threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearDCCAUnknownRatingGroup
> Object ID
> enterprises.8164.2.317
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshDCCARatingFailed
> Object ID
> enterprises.8164.2.318
> Description
> The number of DCCA RatingFailed has exceeded the configured threshold
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearDCCARatingFailed
> Object ID
> enterprises.8164.2.319
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshIPSECIKERequests
> Object ID
> enterprises.8164.2.320
> Description
> The number of IPSEC IKE requests seen for this HA service has exceeded the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in an alarm mode, a starThreshClearIPSECIKERequests notification will be generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearIPSECIKERequests
> Object ID
> enterprises.8164.2.321
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshIPSECIKEFailures
> Object ID
> enterprises.8164.2.322
> Description
> The number of IPSEC IKE failures seen for this HA service has exceeded the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPSECIKEFailures notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearIPSECIKEFailures
> Object ID
> enterprises.8164.2.323
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshIPSECIKEFailRate
> Object ID
> enterprises.8164.2.324
> Description
> The rate of IPSEC IKE failures (as a percentage of total requests) seen for this HA service has exceeded the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPSECIKEFailRate notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearIPSECIKEFailRate
> Object ID
> enterprises.8164.2.325
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshIPSECTunSetup
> Object ID
> enterprises.8164.2.326
> Description
> The number of IPSEC tunnels setup over the last measurement period for this HA service has exceeded the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPSECTunSetup notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearIPSECTunSetup
> Object ID
> enterprises.8164.2.327
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshIPSECTunEstabl
> Object ID
> enterprises.8164.2.328
> Description
> The current number of IPSEC tunnels established for this HA service has exceeded the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPSECTunEstabl notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearIPSECTunEstabl
> Object ID
> enterprises.8164.2.329
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshIPSECCallReqRej
> Object ID
> enterprises.8164.2.330
> Description
> The number of IPSEC Rejected Call Requests has exceeded the configured threshold.
> Probable Cause: This is a user configurable threshold. Reject Call Requests indicate that an IPSEC Manager has reached its maximum allowable number of IPSEC tunnels.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearIPSECTunnelsTotal notification is generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearIPSECCallReqRej
> Object ID
> enterprises.8164.2.331
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCSCFSvcRouteFailure
> Object ID
> enterprises.8164.2.332
> Description
> The Per-Service CSCF Route failure count has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearCSCFSvcRouteFailure notification will be generated when the measured value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCSCFSvcRouteFailure
> Object ID
> enterprises.8164.2.333
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshContFiltRating
> Object ID
> enterprises.8164.2.334
> Description
> The number of Content Filtering Rating operations performed has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearContFiltRating notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearContFiltRating
> Object ID
> enterprises.8164.2.335
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshContFiltBlock
> Object ID
> enterprises.8164.2.336
> Description
> The number of Content Filtering Block operations performed has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearContFiltBlock notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearContFiltBlock
> Object ID
> enterprises.8164.2.337
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCDRFileSpace
> Object ID
> enterprises.8164.2.338
> Description
> The CDR file space usage is above the configured threshold percentage.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in an alarm mode, a starThreshClearCDRFileSpaceOverLimit notification is generated when the measured value falls below the threshold.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearCDRFileSpace
> Object ID
> enterprises.8164.2.339
> Description
> This information indicates that the threshold condition is now clear.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshEDRFileSpace
> Object ID
> enterprises.8164.2.340
> Description
> The EDR file space usage is above the configured threshold percentage.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in alarm mode, a starThreshClearEDRFileSpaceOverLimit notification generated when the measured value falls below the threshold.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearEDRFileSpace
> Object ID
> enterprises.8164.2.341
> Description
> This information indicates that the threshold condition is now clear.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshPDIFCurrSess
> Object ID
> enterprises.8164.2.342
> Description
> The chassis-wide count of current PDIF sessions has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Condition Clear Alarm: If the thresholding subsystem is configured to run in 'alarm' mode, a starThreshClearPDIFCurrSess notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPDIFCurrSess
> Object ID
> enterprises.8164.2.343
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPDIFCurrActSess
> Object ID
> enterprises.8164.2.344
> Description
> The chassis-wide count of current PDIF active sessions has gone above the configured threshold.
> Probable Cause:This is a user configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in ‘alarm’ mode, a starThreshClearPDIFCurrActSess notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPDIFCurrActSess
> Object ID
> enterprises.8164.2.345
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCDRFlowControl
> Object ID
> enterprises.8164.2.346
> Description
> The number of Charging Data Record (CDR) records which have been discarded at an ACSMGR due to flow control has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold. This threshold potentially indicates an overload condition due which prevents processes CDR messages at the same rate as the incoming packets.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearCDRFlowControl notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCDRFlowControl
> Object ID
> enterprises.8164.2.347
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshASNGWSessTimeout
> Object ID
> enterprises.8164.2.348
> Description
> ASNGW session timeout has exceeded the configured threshold.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in ‘alarm’ mode, a starThreshClearASNGWSessTimeout notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearASNGWSessTimeout
> Object ID
> enterprises.8164.2.349
> Description
> Threshold condition is now clear
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshASNGWSessSetupTimeout
> Object ID
> enterprises.8164.2.350
> Description
> ASNGW session setup timeout has exceeded the configured threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshASNGWSessSetupTimeout notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearASNGWSessSetupTimeout
> Object ID
> enterprises.8164.2.351
> Description
> Threshold condition is now clear
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshASNGWAuthFail
> Object ID
> enterprises.8164.2.352
> Description
> Number of ASNGW authentication failures has exceeded the configured threshold in the current monitoring period.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearASNGWAuthFail notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearASNGWAuthFail
> Object ID
> enterprises.8164.2.353
> Description
> Threshold conditrion is now clear
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshASNGWR6InvNai
> Object ID
> enterprises.8164.2.354
> Description
> Number of ASNGW Invalid NAI has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshASNGWR6InvNai notification is generated when the value falls below the threshold.
> Important: This object is obsolete.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearASNGWR6InvNai
> Object ID
> enterprises.8164.2.355
> Description
> Threshold condition is now clear
> Important: This object is obsolete.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshASNGWMaxEAPRetry
> Object ID
> enterprises.8164.2.356
> Description
> Number of ASNGW EAP retries has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearASNGWMaxEAPRetry notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearASNGWMaxEAPRetry
> Object ID
> enterprises.8164.2.357
> Description
> Threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshASNGWNWEntryDenial
> Object ID
> enterprises.8164.2.358
> Description
> Number of ASNGW network entry denials has exceeded the configured threshold during the current monitoring period.
> Probable Cause:This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshASNGWNWEntryDenial notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearASNGWNWEntryDenial
> Object ID
> enterprises.8164.2.359
> Description
> Threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshASNGWHandoffDenial
> Object ID
> enterprises.8164.2.360
> Description
> Number of ASNGW handoff denials has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshASNGW Handoff Denial notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearASNGWHandoffDenial
> Object ID
> enterprises.8164.2.361
> Description
> Threshold condition is now clear
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshSGSNSessions
> Object ID
> enterprises.8164.2.362
> Description
> The total number of SGSN sessions is above the configured threshold value.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearSGSNSessions notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearSGSNSessions
> Object ID
> enterprises.8164.2.363
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPerServiceSGSNSessions
> Object ID
> enterprises.8164.2.364
> Description
> The total number of SGSN sessions in a service is above the configured threshold value.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearPerServiceSGSNSessions notification is generated when the value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPerServiceSGSNSessions
> Object ID
> enterprises.8164.2.365
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshSGSNPdpSessions
> Object ID
> enterprises.8164.2.366
> Description
> The total number of SGSN PDP sessions is above the configured threshold value.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearSGSNPdpSessions notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearSGSNPdpSessions
> Object ID
> enterprises.8164.2.367
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPerServiceSGSNPdpSessions
> Object ID
> enterprises.8164.2.368
> Description
> The total number of SGSN PDP sessions in a service is above the configured threshold value.
> Probable Cause:This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearPerServiceSGSNPdpSessions notification is generated when the value falls below the threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPerServiceSGSNPdpSessions
> Object ID
> enterprises.8164.2.369
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshFWDosAttack
> Object ID
> enterprises.8164.2.370
> Description
> The cumulative number of FW DoS Attacks has exceeded the configured threshold during the current monitoring period.
> Probable Cause:This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearFWDoSAttack notification is generated when the value falls below the threshold.
> Description
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearFWDosAttack
> Object ID
> enterprises.8164.2.371
> Description
> Threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshFWDropPacket
> Object ID
> enterprises.8164.2.372
> Description
> The cumulative number of FW dropped packets has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearFWDropPacket notification is generated when the value falls below the threshold.
> Description
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearFWDropPacket
> Object ID
> enterprises.8164.2.373
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshFWDenyRule
> Object ID
> enterprises.8164.2.374
> Description
> The cumulative number of FW Deny-Rules has exceeded the user-configurable threshold.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearFWDenyRule notification is generated when the value falls below the threshold.
> Description
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearFWDenyRule
> Object ID
> enterprises.8164.2.375
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshFWNoRule
> Object ID
> enterprises.8164.2.376
> Description
> The cumulative number of FW No Rules has exceeded the configured threshold in the current monitoring period.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: If thresholding is configured to run in alarm mode, a starThreshClearFWDenyRulenotification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearFWNoRule
> Object ID
> enterprises.8164.2.377
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSGWSessTimeout
> Object ID
> enterprises.8164.2.378
> Description
> The PHSGW session timeout has gone above the configured threshold. Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSGWSessTimeout
> Object ID
> enterprises.8164.2.379
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSGWSessSetupTimeout
> Object ID
> enterprises.8164.2.380
> Description
> The PHSGW session setup timeout has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSGWSessSetupTimeout
> Object ID
> enterprises.8164.2.381
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSGWAuthFail
> Object ID
> enterprises.8164.2.382
> Description
> The number of PHSGW authentication failures has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSGWAuthFail
> Object ID
> enterprises.8164.2.383
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSGWMaxEAPRetry
> Object ID
> enterprises.8164.2.384
> Description
> The number of PHSGW Maximum EAP Retry has exceeded the configured threshold during the current monitoring period.
> Probable Cause:This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSGWMaxEAPRetry
> Object ID
> enterprises.8164.2.385
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSGWNWEntryDenial
> Object ID
> enterprises.8164.2.386
> Description
> The number of PHSGW Network Entry Denial has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSGWNWEntryDenial
> Object ID
> enterprises.8164.2.387
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSGWHandoffDenial
> Object ID
> enterprises.8164.2.388
> Description
> The number of PHSGW Handoff Denial has exceeded the configured threshold during the current monitoring period.
> Probable Cause:This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSGWHandoffDenial
> Object ID
> enterprises.8164.2.389
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshASNGWSessions
> Object ID
> enterprises.8164.2.390
> Description
> The total number of ASNGW sessions is above the configured threshold value.
> Probable Cause: This is a user-configurable threshold.
> Condition Clear Alarm: a starThreshClearASNGWSessions notification is generated when the value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearASNGWSessions
> Object ID
> enterprises.8164.2.391
> Description
> Threshold condition is now clear
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPerServiceASNGWSessions
> Object ID
> enterprises.8164.2.392
> Description
> The total number of PDSN sessions in a service is above the configured threshold value.
> Possible Cause: This is a user-configurable threshold.
> Condition Clear Alarm: a starThreshClearPerServiceASNGWSessions notification is generated when the value falls below the threshold.
> Objects
> starServiceVPNName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPerServiceASNGWSessions
> Object ID
> enterprises.8164.2.393
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSPCSessSetupTimeout
> Object ID
> enterprises.8164.2.394
> Description
> The PHSPC session setup timeout has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSPCSessSetupTimeout
> Object ID
> enterprises.8164.2.395
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSPCSleepModeTimeout
> Object ID
> enterprises.8164.2.396
> Description
> The PHSPC idle mode timeout has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSPCSleepModeTimeout
> Object ID
> enterprises.8164.2.397
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSPCSmEntryDenial
> Object ID
> enterprises.8164.2.398
> Description
> The number of PHSPC sm entry denial has exceeded the configured threshold during the current monitoring period.
> Probable Cause:This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSPCSmEntryDenial
> Object ID
> enterprises.8164.2.399
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshSGWSessions
> Object ID
> enterprises.8164.2.408
> Description
> The total number of SGW sessions is above the configured threshold value.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearSGWSessions
> Object ID
> enterprises.8164.2.409
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPGWSessions
> Object ID
> enterprises.8164.2.410
> Description
> The total number of PGW sessions is above the configured threshold value.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPGWSessions
> Object ID
> enterprises.8164.2.411
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshLMASessions
> Object ID
> enterprises.8164.2.412
> Description
> The total number of LMA sessions is above the configured threshold value.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearLMASessions
> Object ID
> enterprises.8164.2.413
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshMAGSessions
> Object ID
> enterprises.8164.2.414
> Description
> The total number of MAG sessions is above the configured threshold value.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearMAGSessions
> Object ID
> enterprises.8164.2.415
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshFNGCurrSess
> Object ID
> enterprises.8164.2.416
> Description
> The chassis-wide count of current FNG sessions has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearFNGCurrSess notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearFNGCurrSess
> Object ID
> enterprises.8164.2.417
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshFNGCurrActSess
> Object ID
> enterprises.8164.2.418
> Description
> The chassis-wide count of current FNG active sessions has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearFNGCurrActiveSess notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearFNGCurrActSess
> Object ID
> enterprises.8164.2.419
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSGWEAPOLAuthFailure
> Object ID
> enterprises.8164.2.420
> Description
> The number of PHSGW EAPOL Auth Failure has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSGWEAPOLAuthFailure
> Object ID
> enterprises.8164.2.421
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPHSGWMaxEAPOLRetry
> Object ID
> enterprises.8164.2.422
> Description
> The number of PHSGW max EAPOL retry has exceeded the configured threshold during the current monitoring period.
> Probable Cause:This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPHSGWMaxEAPOLRetry
> Object ID
> enterprises.8164.2.423
> Description
> The threshold condition is now clear."
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshHSGWSessions
> Object ID
> enterprises.8164.2.424
> Description
> The total number of HSGW sessions is above the configured threshold value.
> Probable Cause: This is a user configurable threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshNAPTPortChunks
> Object ID
> enterprises.8164.2.425
> Description
> The NAT port chunks utilization of NAT pool is above the configured threshold value.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPDGCurrSess
> Object ID
> enterprises.8164.2.426
> Description
> The chassis-wide count of current PDG sessions has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDGCurrSess notification will be generated when the measured value falls below the threshold.
> Object ID
> enterprises.8164.2.427
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPDGCurrActSess
> Object ID
> enterprises.8164.2.428
> Description
> The chassis-wide count of current PDG active sessions has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDGCurrActiveSess notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPDGCurrActSess
> Object ID
> enterprises.8164.2.429
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshNAPTPortChunks
> Object ID
> enterprises.8164.2.430
> Description
> The NAT port chunks utilization of NAT pool is above the configured threshold value.
> Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearNAPTPortChunks notification will be generated when the measured value exceeds the threshold.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearNAPTPortChunks
> Object ID
> enterprises.8164.2.431
> Description
> The threshold condition is now clear.
> Objects
> starIPPoolContext
> starIPPoolName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshGPRSSessions
> Object ID
> enterprises.8164.2.432
> Description
> The total number of GPRS sessions is above the configured threshold value.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearGPRSSessions
> Object ID
> enterprises.8164.2.433
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPerServiceGPRSSessions
> Object ID
> enterprises.8164.2.434
> Description
> The total number of GPRS sessions in a service is above the configured threshold value.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPerServiceGPRSSessions
> Object ID
> enterprises.8164.2.435
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshGPRSPdpSessions
> Object ID
> enterprises.8164.2.436
> Description
> The total number of GPRS PDP sessions is above the configured threshold value.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearGPRSPdpSessions
> Object ID
> enterprises.8164.2.437
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPerServiceGPRSPdpSessions
> Object ID
> enterprises.8164.2.438
> Description
> The total number of GPRS PDP sessions in a service is above the configured threshold value.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPerServiceGPRSPdpSessions
> Object ID
> enterprises.8164.2.439
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCSCFSvcRegPerInterval
> Object ID
> enterprises.8164.2.446
> Description
> The Per-Service CSCF Registration Per Interval count has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCSCFSvcRegPerInterval
> Object ID
> enterprises.8164.2.447
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCSCFSvcTotalActiveReg
> Object ID
> enterprises.8164.2.448
> Description
> The Per-Service CSCF Total Active Registrations count has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCSCFSvcTotalActiveReg
> Object ID
> enterprises.8164.2.449
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCSCFSvcCallsPerInterval
> Object ID
> enterprises.8164.2.450
> Description
> The Per-Service CSCF Calls Per Interval count has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCSCFSvcCallsPerInterval
> Object ID
> enterprises.8164.2.451
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCSCFSvcTotalActiveCalls
> Object ID
> enterprises.8164.2.452
> Description
> The Per-Service CSCF Total Active Calls count has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCSCFSvcTotalActiveCalls
> Object ID
> enterprises.8164.2.453
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCSCFSvcTotalCallFailure
> Object ID
> enterprises.8164.2.454
> Description
> The Per-Service CSCF Total Call Failure count has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCSCFSvcTotalCallFailure
> Object ID
> enterprises.8164.2.455
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCSCFSvcErrorNoResource
> Object ID
> enterprises.8164.2.456
> Description
> The Per-Service CSCF No resource failure count has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCSCFSvcErrorNoResource
> Object ID
> enterprises.8164.2.457
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCSCFSvcErrorTcp
> Object ID
> enterprises.8164.2.458
> Description
> The Per-Service CSCF Tcp failure count has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCSCFSvcErrorTcp
> Object ID
> enterprises.8164.2.459
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCSCFSvcErrorPresence
> Object ID
> enterprises.8164.2.460
> Description
> The Per-Service CSCF Presence failure count has gone above the configured threshold. Probable Cause: This is a user configurable threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCSCFSvcErrorPresence
> Object ID
> enterprises.8164.2.461
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshCSCFSvcErrorRegAuth
> Object ID
> enterprises.8164.2.462
> Description
> The Per-Service CSCF Reg-Auth failure count has gone above the configured threshold. Probable Cause: This is a user configurable threshold.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearCSCFSvcErrorRegAuth
> Object ID
> enterprises.8164.2.463
> Description
> The threshold condition is now clear.
> Objects
> starServiceVpnName
> starServiceServName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshBGPRoutes
> Object ID
> enterprises.8164.2.464
> Description
> The Total number of BGP routes is above the configured threshold value.
> Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearBGPRoutes notification will be generated when the measured value falls below the threshold.
> Objects
> starContextName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearBGPRoutes
> Object ID
> enterprises.8164.2.465
> Description
> The threshold condition is now clear.
> Objects
> starContextName
> starThreshInt
> starThreshMeasuredInt
> Object ID
> enterprises.8164.2.478
> Description
> The overall NPU utilization for the identified processor has exceeded for configured threshold value for the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearNPUUtilization notification will be generated when the measured value falls below the threshold.
> Objects
> starNPUSlot
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearNPUUtilization
> Object ID
> enterprises.8164.2.479
> Description
> The threshold condition is now clear.
> Objects
> starNPUSlot
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshDnsLookupFailure
> Object ID
> enterprises.8164.2.480
> Description
> The Total number of DNS lookup failures is above the configured threshold value.
> Probable Cause: This is a user configurable threshold.
> If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearDnsLookupFailure notification will be generated when the measured value falls below the threshold.
> Objects
> starContextName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearDnsLookupFailure
> Object ID
> enterprises.8164.2.481
> Description
> The threshold condition is now clear.
> Objects
> starContextName
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshDiameterRetryRate
> Object ID
> enterprises.8164.2.482
> Description
> The percentage of Diameter requests which has to be retried has exceeded the configured threshold during the current monitoring period.
> Probable Cause: This is a user configurable threshold.
> If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearDiameterRetryRate notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearDiameterRetryRate
> Object ID
> enterprises.8164.2.483
> Description
> The threshold condition is now clear.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshHNBGWHnbSess
> Object ID
> enterprises.8164.2.484
> Description
> The chassis-wide count of current HNBGW HNB sessions has gone above the configured threshold
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearHNBGWHnbSess
> Object ID
> enterprises.8164.2.485
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshHNBGWUeSess
> Object ID
> enterprises.8164.2.486
> Description
> The chassis-wide count of current HNBGW UE sessions has gone above the configured threshold
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearHNBGWUeSess
> Object ID
> enterprises.8164.2.487
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshHNBGWIuSess
> Object ID
> enterprises.8164.2.488
> Description
> The chassis-wide count of current HNBGW IU sessions has gone above the configured threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearHNBGWIuSess
> Object ID
> enterprises.8164.2.489
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshPerServicePDGSessions
> Object ID
> enterprises.8164.2.491
> Description
> he total number of PDG sessions in a service is above the configured threshold value.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearPerServicePDGSessions
> Object ID
> enterprises.8164.2.492
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshSystemCapacity
> Object ID
> enterprises.8164.2.493
> Description
> The System resource capacity has exceeded the configured threshold
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshClearSystemCapacity
> Object ID
> enterprises.8164.2.494
> Description
> The threshold condition is now clear for system capacity.
> Objects
> starThreshPct
> starThreshMeasuredPct
> Object
> starThreshTpoRtoTimeout
> Object ID
> enterprises.8164.2.495
> Description
> The total number of TPO RTO timeouts is above the configured threshold value.
> Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearTpoRtoTimeout notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshClearTpoRtoTimeout
> starThreshMeasuredInt
> Object
> starThreshHNBGWIuSess
> Object ID
> enterprises.8164.2.496
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshTpoDnsFailure
> Object ID
> enterprises.8164.2.497
> Description
> The total number of TPO DNS query failure is above the configured threshold value
> Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearTpoDnsFailure notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearTpoDnsFailure
> Object ID
> enterprises.8164.2.498
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshTpoLowCompressionGain
> Object ID
> enterprises.8164.2.499
> Description
> The total number of TPO low compression gain is above the configured threshold value.
> Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearTpoLowCompressionGain notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearTpoLowCompressionGain
> Object ID
> enterprises.8164.2.500
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshEPDGCurrSess
> Object ID
> enterprises.8164.2.501
> Description
> The chassis-wide count of current EPDG sessions has gone above the configured threshold.
> Probable Cause: This is a user configurable threshold
> If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearEPDGCurrSess notification will be generated when the measured value falls below the threshold.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starThreshClearEPDGCurrSess
> Object ID
> enterprises.8164.2.502
> Description
> The threshold condition is now clear.
> Objects
> starThreshInt
> starThreshMeasuredInt
> Object
> starM3UAPSPDown
> Object ID
> enterprises.8164.2.1006
> Description
> ASP Down message received from the remote M3UA peer indicates the adaptation layer at the remote peer is not ready to receive DATA, SSNM, RKM or ASPTM messages.
> Probable Cause: SCTP association down or Remote peer server down.
> Condition Clear Alarm: A starM3UAPSPUp notification will be generated when remote ASP is available.
> Objects
> starSS7rdId
> starSS7M3UAPspID
> Object
> starM3UAPSPUp
> Object ID
> enterprises.8164.2.1007
> Description
> ASP Up message from remote M3UA Peer indicates the adaptation layer at the remote per is ready to receive ASPSM/ASPTM messages for all routing keys the ASP is configured to serve. Up message is only generated after a previous Down message.
> Objects
> starSS7rdId
> starSS7M3UAPspId
> starSS7M3UAPsId
> Object
> starSCCPSspRcvd
> Object ID
> enterprises.8164.2.1008
> Description
> Subsystem Prohibited message was received from a peer.
> Probable Cause: This is sent by the peer SCCP layer when one of its apps (subsystems), such as the HLR, is out of commission.
> Action to be Taken: Receiving node needs to update the translation tables so that traffic can be directed to a backup system if available.
> Condition Clear Alarm: A starSCCPSspClear notification is generated when this condition is cleared.
> Objects
> starSccpNwId
> starSS7Pc
> starSccpSsn
> Object
> starSCCPSspClear
> Object ID
> enterprises.8164.2.1009
> Description
> Subsystem Available received from a peer This indicates a previously prohibited node is now available.
> Objects
> starSccpNwId
> starSS7Pc
> starSccpSsn
> Object
> starSGSNRNCReset
> Object ID
> enterprises.8164.2.1010
> Description
> SGSN has received a Radio Network Controller reset event. SGSN will clean up all the lu connections.
> Important: This event is not generated for RNC Reset the first time the system boots up.
> Objects
> starSessSGSNVpnName
> starSessSGSNServName
> starSessSGSNMcc
> starSessSGSNMnc
> starSessSGSNRncId
> Object
> starSGSNHLRReset
> Object ID
> enterprises.8164.2.1011
> Description
> Home Location Register (HLR) reset event received. SGSN will mark all subscribers served by this HLR so the subscription record can be fetched again on subsequent activity.
> Objects
> starSessSGSNVpnName
> starSessSGSNServName
> starSessSGSNhlrNum
> Object
> starSGSNGtpcPathFailure
> Object ID
> enterprises.8164.2.1012
> Description
> No response received from peer GSN as several messages have timed out. The control path to the GSN is down.
> Probable Cause: Remote GSN is down.
> Condition Clear Alarm: A starSGSNGtpcPathFailureClear alarm is generated when the GSN becomes reachable.
> Objects
> starSGTPVpnName
> starSGTPServName
> starSGTPPeerAdd
> starSGTPPeerPort
> starSGSNSelfAddr
> starSGSNSelfPort
> Object
> starSGSNFtpcPathFailureClear
> Object ID
> enterprises.8164.2.1013
> Description
> The path to the peer GSN which was down is now available. Generated only for GSNs which had previously been down.
> Objects
> starSGTPVpnName
> starSGTPServName
> starSGTPPeerAddr
> Object
> starSGSNGtpuPathFailure
> Object ID
> enterprises.8164.2.1014
> Description
> No Response received for Echo Request sent from SGSN. Data path failure detected toward GSN or RNC.
> Probable Cause: Remote GSN is down.
> Action to be Taken: Check if peer RNC or GSN is up.
> Condition Clear Alarm: A starSGSNGtpuPathFailureClear message is generated when the remote GSN becomes available again.
> Objects
> starSGTPVpnName
> starSGTPNServName
> starSGTPPeerAddr
> tarSGTPPeerPort
> starSGSNSelfAddr
> starSGSNSelfPort
> Object
> starSGSNGtpuPathFailureClear
> Object ID
> enterprises.8164.2.1015
> Description
> The data path toward the peer GSN or RNC is now available. A path failure clear notification will only be sent for peers which had previously generated a path failure notification.
> Objects
> starSGTPVpnName,
> starSGTPServName
> starSGTPPeerAddr
> starSGTPPeerPort
> starSGSNSelfAddr
> starSGSNSelfPor
> Object
> starMTP3LinkOutofService
> Object ID
> enterprises.8164.2.1016
> Description
> Message Transfer Part (MTP3) Link out of service.
> Probable Cause: Physical link is down, Layer 2 SSCOP/MTP2 is down or link deactivated by operator.
> Condition Clear Alarm: A starMTP3LinkInService message is generated when the link is restored.
> Objects
> starSS7rdId
> starSS7MTP3LinkSetId
> starSS7MTP3LinkId
> Object
> starMTP3LinkinService
> Object ID
> enterprises.8164.2.1017
> Description
> MTP3 link is now in service.
> Objects
> starSS7rdId
> starSS7MTP3LinkSetId
> starSS7MP3LinkId
> Object
> starMTP3LinkSetUnAvailable
> Object ID
> enterprises.8164.2.1018
> Description
> MTP3 Linkset Unavailable message.
> Probable Cause: All links in linkset are down. Linkset deactivated by operator.
> Condition Clear Alarm: A starMTP3LinkSetAvailable message is generated when the previously down linkset is restored.
> Objects
> starSS7rdId
> starSS7MTP3LinkSetId
> Object
> starMTP3LinkSetAvailable
> Object ID
> enterprises.8164.2.1019
> Description
> MTP3 linkset is now available
> Objects
> starSS7rdId
> starSS7MTP3LinkSetId
> Object
> starSCTPAssociationFail
> Object ID
> enterprises.8164.2.1020
> Description
> M3UA SCTP association establishment failure.
> Probable Cause: Peer is down. Network is down. The endpoint configuration is incorrect at our end.
> Condition Clear Alarm:A starSCTPAssociationEstablished message is sent when a previously failed association is restored.
> Objects
> starSS7rdId
> starSS7M3UAPspId
> starSS7M3UAPsId
> Object
> starSCTPAssociationEstablished
> Object ID
> enterprises.8164.2.1021
> Description
> M3UA SCTP association established successfully. This message is only generated for peers which previously generated an Association Fail message.
> Objects
> starSS7rdId
> starSS7M3UAPspId
> starSS7M3UAPsId
> Object
> starSCTPPathDown
> Object ID
> enterprises.8164.2.1022
> Description
> SCTP path is down.
> Probable Cause: Peer is down. Network to the remote server is down. The endpoint configuration is incorrect at our end.
> Condition Clear Alarm:A starSCTPPathUp notification is generated when the path is restored.
> Objects
> starSS7rdId
> starSS7M3UAPspId
> starSS7M3UAPsId
> starSS7SCTPPeerAddr
> starSS7SCTPSelfAddr
> starSS7SCTPPeerPort
> starSS7SCTPSelfPort
> Object
> starSCTPPathUp
> Object ID
> enterprises.8164.2.1023
> Description
> SCTP path up. This notification is only generated for peers which had previously generated an SCTP path down notification.
> Objects
> starSS7rdId
> starSS7M3UAPspId
> starSS7M3UAPsId
> starSS7SCTPPeerAddr
> starSS7SCTPPeerPort
> starSS7SCTPSelfPort
> starSS7SCTPSelfAddr
> Object
> starPortDown
> Object ID
> enterprises.8164.2.1024
> Description
> Physical port status is down.
> Probable Cause: Network is down. Port disconnected.
> Condition Clear Alarm: A starPortUp notification is generated when the port is restored.
> Objects
> starPortSlot
> starPortNum
> starPortType
> Object
> starPortUp
> Object ID
> enterprises.8164.2.1025
> Description
> Physical port is up. This notification is only generated for a physical port with a previous starPortDown notification.
> Objects
> starPortSlot
> starPortNum
> starPortType
> Object
> starBSReachable
> Object ID
> enterprises.8164.2.1026
> Description
> The base station that the IMG communicates with is now reachable.
> Objects
> starContextName
> starASNGWServiceName
> starBSAddress
> Object
> starBSUnreachable
> Object ID
> enterprises.8164.2.1027
> Description
> The Base Station that the IMG communicates with is not reachable.
> Probable Cause: The Base Station has failed. Network has connectivity problems.
> Action to be Taken: If the outage was unplanned, reboot the base station and verify network connectivity.
> Condition Clear Alarm: A starBSReachable notification is generated when the base station is reconnected.
> Objects
> starContextName
> starASNGWServiceName
> starBSAddress
> Object
> starSystemStartup
> Object ID
> enterprises.8164.2.1028
> Description
> The system has completed a reboot/startup
> Objects
> starChassisType
> starChassisDescription
> starChassisSWRevision
> Object
> starMTP3PCUnavailable
> Object ID
> enterprises.8164.2.1029
> Description
> MTP3 route to the point code is unavailable.
> Probable Cause:All links within the linkset become unavailable. Remote peer is down.
> Condition Clear Alarm:A starMTP3PCAvailable message is generated when the route to the point code is reestablished.
> Objects
> starSS7rdId
> starSS7Pc
> starSS7MTP3LinkSetId
> Object
> starMTP3PCAvailable
> Object ID
> enterprises.8164.2.1030
> Description
> MTP3 route to the point code available
> Objects
> starSS7rdId
> starSS7Pc
> starSS7MTP3LinkSetId
> Object
> starSS7PCUnavailable
> Object ID
> enterprises.8164.2.1031
> Description
> SS7 point code unavailable.
> Probable Cause: All MTP3 and M3UA routes to the point code become unavailable.
> Condition Clear Alarm: A starSS7PCAvailable message is generated when the route is reestablished.
> Objects
> starSS7rdId
> starSS7Pc
> Object
> starSS7PCAvailable
> Object ID
> enterprises.8164.2.1032
> Description
> SS7 point code available.Probable Cause: one of the M3UA or MTP3 routes is back up. Action to be Taken: No action required.
> Objects
> starSS7rdId
> starSS7Pc
> Object
> starASNPCServiceStart
> Object ID
> enterprises.8164.2.1033
> Description
> A WiMAX ASN Paging Controller (ASNPC) Service has started. Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starASNPCServiceStop
> Object ID
> enterprises.8164.2.1034
> Description
> A WiMAX ASN Paging Controller (ASNPC) Service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the ASNPC service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the ASNPC service is operational.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starDiameterCapabilitiesExchangeFailure
> Object ID
> enterprises.8164.2.1035
> Description
> Capability negotiations have failed and connections are down.
> Probable Cause:Connections have been torn down due to an error in the Capability Exchange Answer received from the peer.
> Objects
> starDiameterVpnName
> starDiameterPeerAddr
> starDiameterEndpointName
> Object
> starDiameterCapabilitiesExchangeSuccess
> Object ID
> enterprises.8164.2.1036
> Description
> Diameter server is up. This notification is only generated for a server that has been previously declared unreachable
> Objects
> starDiameterVpnName
> starDiameterPeerAddr
> starDiameterEndpointName
> Object
> starSRPConnDown
> Object ID
> enterprises.8164.2.1037
> Objects
> SRP system connection is down and active system is now without a standby and therefore unable to perform an SRP switchover.
> Probable Cause: Network connectivity problem.
> Action to be Taken:Verify standby system is operational and check the network connections are up.
> Clear Condition: A starSRPConnUp notification s generated when condition is cleared.
> Objects
> starContextName
> starSRPIpAddress
> Object
> starSRPConnUP
> Object ID
> enterprises.8164.2.1038
> Description
> SRP connection is restored. This notification is only generated after a previous connection loss was reported.
> Objects
> starContextName
> starSRPIpAddress
> Object
> starDiameterIpv6PeerDown
> Object ID
> enterprises.8164.2.1039
> Description
> A diameter peer is down. This diameter peer is reached using an IPv6 address. For IPv4-connected diameter peers, a starDiameterPeerDown notification would be generated.
> Problem Cause: The diameter peer has failed, or a network connectivity prevents reaching the peer.
> Condition Clear Alarm: A starDiameterPeerUp notification will be generated when the peer is up.
> Objects
> starDiameterVpnName
> starDiameterPeerAddrIpv6
> starDiameterEndpointName
> Object
> starDiameterIpv6PeerUp
> Object ID
> enterprises.8164.2.1040
> Description
> A diameter peer is up. This diameter peer is reached using an IPv6 address. This notification is only generated for peers which have previously been declared down. For IPv4-connected diameter peers, a starDiameterPeerUp notification would be generated.
> Objects
> starDiameterVpnName
> starDiameterPeerAddrIpv6
> starDiameterEndpointName
> Object
> starIPMSServerUnreachable
> Object ID
> enterprises.8164.2.1041
> Description
> An IPMS server is unreachable.
> Probable Cause: The IPMS server has failed, or a network connectivity issue prevents reaching the server.
> Condition Clear Alarm: A 7713dcf72--1301" mergeid="a--92d120d-127713dcf72--1300">starStorageName.
> Object
> starIPMSServerReachable
> Object ID
> enterprises.8164.2.1042
> Description
> An IPMS server is reachable. A starIPMSServerReachable notification is only generated for servers which had previously been declared unreachable
> Objects
> starIPMSServerVpnName
> starIPMSServerAddr
> Object
> starCertShortLifetime
> Object ID
> enterprises.8164.2.1043
> Description
> A certificate is approaching its expiration. The certificate is still valid, but should beupdated with a new certificate.
> Action to be Taken: A new certificate should be created and configured on the system.
> Object
> starCertExpired
> Object ID
> enterprises.8164.2.1044
> Description
> A certificate has expired. The certificate is no longer valid.
> Action to be Taken: A new certificate should be created and configured on the system.
> Condition Clear Alarm: A starCertValid notification is sent when a new, valid, certificate is configured.
> Objects
> starCertSerialNumber
> starCertIssuer
> starCertExpiryTime
> Object
> starCertValid
> Object ID
> enterprises.8164.2.1045
> Description
> A valid certificate has been configured. This notification is only generated if a starCertExpired had been previously generated.
> Objects
> starCertSerialNumber
> starCertIssuer
> starCertExpiryTime
> Object
> starFTPPushFail
> Object ID
> enterprises.8164.2.1046
> Description
> An FTP push operation has failed for the specified file to the specified server.
> Objects
> starFTPServVpnName
> starFTPServIpAddr
> starFileName
> starFileApplication
> Object
> starFTPServSwitch
> Object ID
> enterprises.8164.2.1047
> Description
> An FTP server switchover has been performed; that is, the system has determined that an external FTP server is unreachable, and is not using an alternate FTP server
> Objects
> starFTPServVpnName
> starFTPServIpAddr
> starFTPServIpAddr
> starFileApplication
> Object
> starSDHSectionDown
> Object ID
> enterprises.8164.2.1048
> Description
> The SDH interface on this port is down. The starSDHOperState identifies the specific issue.
> Condition Clear Alarm: This condition is cleared by a starSDHSectionUp notification
> Objects
> starSDHSlot
> starSDHPort
> starSDHOperState
> Object
> starSDHSectionUp
> Object ID
> enterprises.8164.2.1049
> Description
> The SDH interface on this port is now up. A starSDHSectionUp notification is only generated if a starSDHSectionDown was previously generated for this port.
> Objects
> starSDHSlot
> starSDHPort
> Object
> starSDHPathHopDown
> Object ID
> enterprises.8164.2.1050
> Description
> The identified SDH Path is down. The value of starSDHPathOperState identifies the specific failure bits.
> Objects
> starSDHPathSlot
> starSDHPathPort
> starSDHPathNum
> starSDHPathOperState
> Object
> starSDHPathHopUp
> Object ID
> enterprises.8164.2.1051
> Description
> The identified SDH Path is up.
> Objects
> starSDHPathSlot
> starSDHPathPort
> starSDHPathNum
> Object
> starSDHLopDown
> Object ID
> enterprises.8164.2.1052
> Description
> The identified E1 Tributary on this port is down. The value of starE1TribOperStateLOP identifies the specific failure bits.
> Condition Clear Alarm: This condition is cleared by a starSDHLopDown notification
> Objects
> starE1TribSlot
> starE1TribPort
> starE1TribPath
> starE1TribTug2
> starE1TribTu12
> starE1TribOperStateLOP
> Object
> starSDHLopUp
> Object ID
> enterprises.8164.2.1053
> Description
> The identified E1 Tributary on this port is now up. A starE1TributaryUp notification is only generated if a starSDHLopDown was previously generated for this E1 tributary.
> Objects
> starE1TribSlot
> starE1TribPort
> starE1TribPath
> starE1TribTug2
> starE1TribTu12
> Object
> starPHSGWServiceStart
> Object ID
> enterprises.8164.2.1058
> Description
> A PHS-GW Service has started
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPHSGWServiceStop
> Object ID
> enterprises.8164.2.1059
> Description
> A PHS-GW Service has stopped
> Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the PHS-GW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the PHS-GW service is operational
> Condition Clear Alarm: A starPHSGWServiceStart notification will be generated when the service is restarted
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starGPRSServiceStart
> Object ID
> enterprises.8164.2.1060
> Description
> A GPRS Service has started
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starGPRSServiceStop
> Object ID
> enterprises.8164.2.1061
> Description
> A GPRS Service has stopped.
> ;: In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.This can also happen due to some misconfiguration of the service parameters.
> Action to be Taken: If the GPRS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the GPRS service is operational.
> Condition Clear Alarm: A starGPRSServiceStart notification will be generated when the service is restarted
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starGPRSNseDown
> Object ID
> enterprises.8164.2.1062
> Description
> Network Service Entity (NSE) is down.
> Possible reasons: The Last NSVC(Network Service virtual circuit in the NSE is down.
> Condition Clear Alarm: A starGPRSNseUp will be generated when at least one NSVC in the NSE comes up
> Objects
> starGPRSNsei
> Object
> starGPRSNseUp
> Object ID
> enterprises.8164.2.1063
> Description
> Network Service Entity (NSE) is up.
> Possible reasons: The First NSVC(Network Service virtual circuit in the NSE is up. starGPRSNseUp is generated only when a previous starGPRSNseDown has been generated
> Objects
> starGPRSNsei
> Object
> starGPRSNsvcDown
> Object ID
> enterprises.8164.2.1064
> Description
> Network Service Entity Virtual Circuit (NSVC) is down.
> Possible reasons: NS_ALIVE heartbeat messages sent from the Serving GPRS support Node (SGSN) were not acknowledged by the Base Station Subsystem(BSS) for a configured number of maximum retries. This trap is generated only when an NSVC goes down due to reasons other than physical port failure. A separate trap is generated for a physical port failure event.
> Condition Clear Alarm: A starGPRSNsvcUp will be generated when the NSVC comes up
> Objects
> starGPRSNsei
> starGPRSNsvci
> Object
> starGPRSNsvcUp
> Object ID
> enterprises.8164.2.1065
> Description
> An Network Service Entity Virtual Circuit (NSVC) comes up. An starGPRSNsvcUp trap is generated only when a previous starGPRSNsvcDown was generated
> Objects
> starGPRSNsei
> starGPRSNsvci
> Object
> starGPRSBvcDown
> Object ID
> enterprises.8164.2.1066
> Description
> Base Station Subsystem (BSS) GPRS (General Packet Radio Service) Protocol (BSSGP) Virtual Circuit (BVC) is Down.
> Possible reasons: ALL Network Service Entity Virtual Circuit (NSVC) associated with this BVC are down
> Condition Clear Alarm: A starGPRSBvcUp will be generated when the BVC is available
> Objects
> starGPRSNsei
> starGPRSBvci
> Object
> starGPRSBvcUp
> Object ID
> enterprises.8164.2.1067
> Description
> Base Station Subsystem (BSS) GPRS ((General Packet Radio Service) Protocol (BSSGP) Virtual Circuit (BVC) is Up
> Possible reasons: Atleast one NSVC associated with the BVC becomes available. starGPRSBvcUp is generated only when a previous starGPRSBvcDown has been generated.
> Objects
> starGPRSNsei
> starGPRSBvci
> Object
> starSDHE1TribDown
> Object ID
> enterprises.8164.2.1068
> Description
> The identified E1 Tributary on this port is down.
> Condition Clear Alarm: This condition is cleared by a starSDHTugUp notification
> Objects
> starE1TribSlot
> starE1TribPort
> starE1TribPath
> starE1TribTug2
> starE1TribTu12
> starE1TribOperState
> Object
> starSDHE1TribUp
> Object ID
> enterprises.8164.2.1069
> Description
> The identified E1 Tributary on this port is up.
> Objects
> starE1TribSlot
> starE1TribPort
> starE1TribPath
> starE1TribTug2
> starE1TribTu12
> Object
> starSDHFractE1LMIDown
> Object ID
> enterprises.8164.2.1070
> Description
> The identified fractional E1 Tributary on this port is down.
> Objects
> starFractE1TribSlot
> starFractE1TribPort
> starFractE1TribPath
> starFractE1TribTug2
> starFractE1TribTu12
> starFractE1TribTimeslots
> Object
> starSDHFractE1LMIUp
> Object ID
> enterprises.8164.2.1071
> Description
> The identified fractional E1 Tributary on this port is up.
> Objects
> starFractE1TribSlot
> starFractE1TribPort
> starFractE1TribPath
> starFractE1TribTug2
> starFractE1TribTu12
> Object
> starPHSPCServiceStart
> Object ID
> enterprises.8164.2.1072
> Description
> A PHS-PC Service has started
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPHSPCServiceStop
> Object ID
> enterprises.8164.2.1073
> Description
> A PHS-PC Service has stopped
> Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration
> Action to be Taken: If the PHS-PC service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the PHS-PC service is operational.
> Condition Clear Alarm: A starPHSPCServiceStart notification will be generated when the service is restarted
> Objects
> starIPMSServerVpnName
> starIPMSServerAddr
> Object
> starRaidDegraded
> Object ID
> enterprises.8164.2.1079
> Description
> The specified raid array is running in a degraded state. This typically means one of the member devices has failed or become unavailable. The raid array continues to function and can read/store data, but may not be operating in a redundant manner.
> Probable Cause: Hardware failure(s) on the devices within the raid array; Hardware failure(s) on the card(s) to which the devices are attached; the removal of the cards containing devices in the array; operator action which disabled the raid array.
> The first variable binding, starStorageName is indicating the raid array name; The second variable binding, starStorageSlot is the disk card number, in which the fail happens; The third varbind, which is also the second starStorageName, is the name of the disk that the fail happens.
> Condition Clear Alarm: a starRaidRecovered notification will be generated when the raid array is fully recovered.
> Objects
> starStorageName
> starStorageSlot
> starStorageName
> Object
> starRaidRecovered
> Object ID
> enterprises.8164.2.1080
> Description
> The specific raid array has been recovered and is running in its normal, redundant state. This notification is only generated if a starRaidDegraded notification was previously generated for this array. As to the variable bindings, please refer to the trap starRaidDegraded.
> Objects
> starStorageName
> starStorageSlot
> starStorageName
> Object
> starPGWServiceStart
> Object ID
> enterprises.8164.2.1081
> Description
> A Packet Data Network Gateway (PGW) Service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPGWServiceStop
> Object ID
> enterprises.8164.2.1082
> Description
> A Packet Data Network Gateway (PGN) Service has stopped.
> Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration.
> Action to be Taken: If the PGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the PGW service is operational.
> Condition Clear Alarm: A starPGWServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSGWServiceStart
> Object ID
> enterprises.8164.2.1083
> Description
> A Serving Gateway (SGW) Service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSGWServiceStop
> Object ID
> enterprises.8164.2.1084
> Description
> A Serving Gateway (SGW) Service has stopped.
> Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration.
> Action to be Taken: If the SGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the SGW service is operational.
> Condition Clear Alarm: A starSGWServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starEGTPServiceStart
> Object ID
> enterprises.8164.2.1085
> Description
> An Evolved GPRS Tunneling Protocol (EGTP) Service has started. Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starEGTPServiceStop
> Object ID
> enterprises.8164.2.1086
> Description
> An Evolved GPRS Tunneling Protocol (EGTP) Service has stopped.
> Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration.
> Action to be Taken: If the EGTP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the EGTP service is operational.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starLMAServiceStart
> Object ID
> enterprises.8164.2.1087
> Description
> A Local Mobility Anchor (LMA) Service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starLMAServiceStop
> Object ID
> enterprises.8164.2.1088
> Description
> A Local Mobility Anchor (LMA) Service has stopped.
> Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration.
> Action to be Taken: If the LMA service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the LMA service is operational.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starMAGServiceStart
> Object ID
> enterprises.8164.2.1089
> Description
> A Mobile Access Gateway (MAG) Service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starMAGServiceStop
> Object ID
> enterprises.8164.2.1090
> Description
> A MAG Service has stopped.
> Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration.
> Action to be Taken: If the MAG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the MAG service is operational. Condition Clear Alarm: A starMAGServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starMMEServiceStart
> Object ID
> enterprises.8164.2.1091
> Description
> A Mobility Management Entity (MME) Service has started.
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starMMEServiceStop
> Object ID
> enterprises.8164.2.1092
> Description
> A Mobility Management Entity (MME) Service has stopped.
> Probable Cause:This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration.
> Action to be Taken : If the MME service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Codition : Verify that the MME service is operational.
> Condition Clear Alarm: A starMMEServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starHSGWServiceStart
> Object ID
> enterprises.8164.2.1093
> Description
> A HRPD Serving Gateway (HSGW) Service has started.
> Action to be Taken:No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starHSGWServiceStop
> Object ID
> enterprises.8164.2.1094
> Description
> A HRPD Servi g Gateway (HSGW) Service has stopped.
> Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration.
> Actio to be Taken : If the HSGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the HSGW service is operational.
> Conditio Clear Alarm: A starHSGWServiceStart otification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starCPUBusyClear
> Object ID
> enterprises.8164.2.1095
> Description
> The CPU is no longer busy.
> Objects
> starCPUSlot
> starCPUNumber
> Object
> starCPUMemoryLowClear
> Object ID
> enterprises.8164.2.1096
> Description
> The identified manager task has been restarted.
> Objects
> starCPUSlot
> starCPUNumber
> Object
> starFNGServiceStart
> Object ID
> enterprises.8164.2.1097
> Description
> A FNG Service has started.
> Action to be Taken:No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starFNGServiceStop
> Object ID
> enterprises.8164.2.1098
> Description
> A FNG Service has stopped.
> Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs) to support the running configuration.
> Action to be Taken: If the FNG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the FNG service is operational.
> Condition Clear Alarm: A starFNGServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starManagerRestart
> Object ID
> enterprises.8164.2.1099
> Description
> The identified manager task has been restarted.
> Objects
> starTaskFacilityName
> starTaskInstance
> starTaskCard
> starTaskCPU
> Object
> starConfigurationUpdate
> Object ID
> enterprises.8164.2.1100
> Description
> The configuration of the chassis has been changed. This notification is generated based on a periodic polling of the chassis, it is not real-time generated based on individual changes. The configuration change could have been made via CLI sessions, CORBA management operations, or other methods. This notification is not generated by default, it is only generated if the configuration polling mechanism is specifically enabled.
> Object
> starPDGServiceStart
> Object ID
> enterprises.8164.2.1101
> Description
> A PDG Service has started
> Action to be Taken: No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPDGServiceStop
> Object ID
> enterprises.8164.2.1102
> Description
> A PDG Service has stopped.
> Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs) to support the running configuration.
> Action to be Taken: If the PDG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the PDG service is operational.
> Condition Clear Alarm: A starPDGServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starASNPCServiceStart
> Object ID
> enterprises.8164.2.1103
> Description
> A WiMAX ASN Paging Controller (ASNPC) Service has started
> Objects
> starServiceVpnName, starServiceServName
> Object
> starPDGServiceStop
> Object ID
> enterprises.8164.2.1104
> Description
> A PDG Service has stopped.
> Objects
> starServiceVpnName, starServiceServName
> Object
> starDiameterIpv6PeerDown
> Object ID
> enterprises.8164.2.1105
> Description
> A diameter peer is down.
> Objects
> starDiameterVpnName, starDiameterPeerAddrIpv6, starDiameterEndpointName
> Object
> starDiameterIpv6PeerUp
> Object ID
> enterprises.8164.2.1106
> Description
> A diameter peer is up.
> Objects
> starDiameterVpnName, starDiameterPeerAddrIpv6, starDiameterEndpointName
> Object
> starIPMSServerUnreachable
> Object ID
> enterprises.8164.2.1107
> Description
> An IPMS server is unreachable.
> Objects
> starIPMSServerVpnName, starIPMSServerAddr
> Object
> starIPMSServerReachable
> Object ID
> enterprises.8164.2.1108
> Description
> An IPMS server is reachable. A starIPMSServerReachable notification is only generated for servers which had previously been declared unreachable.
> Objects
> starIPMSServerVpnName, starIPMSServerAddr
> Object
> starCertShortLifetime
> Object ID
> enterprises.8164.2.1109
> Description
> A certificate is approaching its expiration. The certificate is still valid, but should be updated with a new certificate.
> Objects
> starCertSerialNumber, starCertIssuer, starCertExpiryTime
> Object
> starServiceLossPTACsClear
> Object ID
> enterprises.8164.2.1110
> Description
> Service Loss condition is no longer valid for PAC/PSC/TACs
> Objects
> starCardMode
> Object
> starServiceLossLCClear
> Object ID
> enterprises.8164.2.1111
> Description
> Service Loss condition is no longer valid for LC
> Objects
> starCardMode
> Object
> starEgtpcPathFailure
> Object ID
> enterprises.8164.2.1112
> Description
> EGTP Control Path Failure. No response received for GTPV2 request sent from MME or SGW or PGW.
> Possibe reason: Remote peer MME or SGW or PGW is down.
> Condition Clear Alarm: A StarEgtpcPathFailureClear notification will be generated when the control path to the remote peer MME or SGW or PGW becomes available.
> Objects
> starEGTPVpnName
> starEGTPServName
> starEGTPInterfaceType
> starEGTPSelfAddr
> starEGTPPeerAddr
> starEGTPPeerOldRstCnt
> starEGTPPeerNewRstCnt
> starEGTPPeerSessCnt
> starEGTPFailureReason
> Object
> starEgtpcPathFailureClear
> Object ID
> enterprises.8164.2.1113
> Description
> EGTP Control Path Failure condition is no longer valid.
> Objects
> starEGTPVpnName
> starEGTPServName
> starEGTPInterfaceType
> starEGTPSelfAddr
> starEGTPPeerAddr
> Object
> starCscfSessResourceCongestion
> Object ID
> enterprises.8164.2.1114
> Description
> A congestion condition has occurred at Session Manager for Cscf Service
> Probable Cause: This is the result of an operator-configured congestion threshold being reached for Cscf Service at Session Manager. This can be due to high usage of the resource being monitored which indicates that the IMG is reaching its peak capacity, or could be caused by the incorrect configuration of the congestion thresholds.
> Actions to be Taken:Verify that the congestion thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online.
> Condition Clear Alarm: A starCscfSessResourceCongestionClear notification is sent when there are no congestion conditions for cscf service in that Session Manager Instance.
> This system is cleared when the use of the specific resource falls below the configured limit.
> Objects
> starSmgrId
> starCongestionPolicy
> starCscfSessCongestionResourceType
> Object
> starCscfSessResourceCongestionClear
> Object ID
> enterprises.8164.2.1115
> Description
> A congestion condition has cleared at Session Manager for Cscf service
> Objects
> starSmgrId
> Object
> starOSPFv3NeighborDown
> Object ID
> enterprises.8164.2.1116
> Description
> An OSPFv3 neighbor is down
> Objects
> starContextName
> starInterfaceName
> starInterfaceIPAddress
> starOSPFNeighborRouterID
> starOSPFFromState
> starOSPFToState
> Object
> starOSPFv3NeighborFull
> Object ID
> enterprises.8164.2.1117
> Description
> An OSPFv3 neighbor is full. A starOSPFv3NeighborFull notification is only sent for neighbors which had previous been declared down via a starOSPFv3NeighborDown notification
> Objects
> starContextName
> starInterfaceName
> starInterfaceIPAddress
> starOSPFNeighborRouterID
> Object
> starServiceLossSPIOClear
> Object ID
> enterprises.8164.2.1118
> Description
> Service Loss condition is no longer valid for SPIO
> Objects
> starCardMode
> Object
> starEgtpuPathFailure
> Object ID
> enterprises.8164.2.1119
> Description
> No response received for GTP-U ECHO requests. Data path failure detected towards peer EPC Node. Check if the peer RNC or GSN is up.
> Possible reason: Remote EPC node is down.
> Condition Clear Alarm: A starEgtpuPathFailureClear notification will be generated when the data path towards the peer node is available.
> Objects
> starEGTPVpnName
> starEGTPServName
> starEGTPSelfAddr
> starEGTPPeerAddr
> starEGTPSelfPort
> starEGTPPeerPort
> starEGTPPeerSessCnt
> Object
> starEgtpuPathFailureClear
> Object ID
> enterprises.8164.2.1120
> Description
> The data path to the peer EPC node which was down is now available A starEgtpuPathFailureClear notification is only generated for nodes which had previously generated a starEgtpuPathFailure notification.
> Objects
> starEGTPVpnName
> starEGTPServName
> starEGTPSelfAddr
> starEGTPPeerAddr
> starEGTPSelfPort
> starEGTPPeerPort
> Object
> starStorageServerCDRLoss
> Object ID
> enterprises.8164.2.1121
> Description
> GTPP Storage Server is experiencing CDR Loss greater than the configured threshold value at the GSS.
> Objects
> starSessGGSNVpnName
> starSessGGSNPeerAddr
> starGSSCDRLossConfigured
> starGSSCDRLossMeasured
> starGSSClusterName
> starGSSClusterNodeName
> Object
> starHNBGWServiceStart
> Object ID
> enterprises.8164.2.1122
> Description
> A Home Node B Gateway (HNB GW) Service has started
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starHNBGWServiceStop
> Object ID
> enterprises.8164.2.1123
> Description
> A Home Node B Gateway (PGN) Service has stopped
> Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration
> Action to be Taken: If the HNB GW service shutdown was not planned, examine the ad min logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure
> Clear Condition: Verify that the HNB GW service is operational
> Condition Clear Alarm: A starHNBGWServiceStart notification will be generated when the service is restarted
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSystemReboot
> Object ID
> enterprises.8164.2.1124
> Description
> The system has rebooted by the operator. If successful, a subsequent starSystemStartup trap is typically generated.
> Action to be Taken: No action required. If the reboot was not scheduled the admin logs can be examined to determine who invoked the reboot operation.
> Objects
> starChassisType
> starChassisDescription
> starChassisSWRevision
> Object
> starLicenseAboutToExpire
> Object ID
> enterprises.8164.2.1125
> Description
> A license is about to expire
> Action to be Taken: A new license should be created and configured on the system before the grace period is over
> Objects
> starLicenseKey
> starLicenseExpiryDate
> starLicenseDaysRemaining
> Object
> starLicenseExpired
> Object ID
> enterprises.8164.2.1126
> Description
> A license is in the grace period and should be updated with a new license
> Action to be Taken: A new license should be created and configured on the system
> Objects
> starLicenseKey
> starLicenseExpiryDate
> starLicenseDaysAfterExpiry
> Object
> starPCCPolicyServiceStart
> Object ID
> enterprises.8164.2.1127
> Description
> A PCC-Policy Service has started
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPCCPolicyServiceStop
> Object ID
> enterprises.8164.2.1128
> Description
> A PCC-Policy Service has stopped.
> Probable Cause:This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the PCC-Policy service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition Verify that the PCC-Policy service is operational.
> Condition Clear Alarm A starPCCPolicyServiceStart notification will be generated when the service is restarted
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPCCQuotaServiceStart
> Object ID
> enterprises.8164.2.1129
> Description
> A PCC-Quota Service has started
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPCCQuotaServiceStop
> Object ID
> enterprises.8164.2.1130
> Description
> A PCC-Quota Service has stopped.
> Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the PCC-Quota service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the PCC-Quota service is operational.
> Condition Clear Alarm: A starPCCQuotaServiceStart notification will be generated when the service is restarted
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPCCAFServiceStart
> Object ID
> enterprises.8164.2.1131
> Description
> A PCC-AF Service has started.
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starPCCAFServiceStop
> Object ID
> enterprises.8164.2.1132
> Description
> A PCC-AF Service has stopped.
> Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the PCC-AF service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the PCC-AF service is operational.
> Condition Clear Alarm: A starPCCAFServiceStart notification will be generated when the service is restarted
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSPRServerUnreachable
> Object ID
> enterprises.8164.2.1133
> Description
> The Subscriber Profile Repository (SPR) server cannot be reached.
> Probable Cause:The SPR server is down, or there is a network issue preventing communication with the SPR server.
> Action to be Taken: Restore the SPR server to an operational status; Verify that the SPR server is reachable by performing a 'ping' operation from the CLI in the appropriate context. Check the admin logs for notification of communication problems.
> Clear Condition: Verify that communication to the SPR authentication server has been restored.
> Condition Clear Alarm:When this condition clears a starSPRServerReachable notification will be generated.
> Objects
> starSPRServerIpAddr
> Object
> starSPRServerReachable
> Object ID
> enterprises.8164.2.1134
> Description
> The Subscriber Profile Repository (SPR) server is now reachable. This can be the result of a system startup, the configuration of a new server, or a previously unreachable server becoming reachable.
> Action to be Taken:No Action Required.
> Objects
> starSPRServerIpAddr
> Object
> starGSServiceStart
> Object ID
> enterprises.8164.2.1135
> Description
> A GS Service has started
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starGSServiceStop
> Object ID
> enterprises.8164.2.1136
> Description
> A GS Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the GS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starMAPServiceStart
> Object ID
> enterprises.8164.2.1137
> Description
> A MAP Service has started
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starMAPServiceStop
> Object ID
> enterprises.8164.2.1138
> Description
> A MAP Service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starIUPSServiceStart
> Object ID
> enterprises.8164.2.1139
> Description
> An IUPS Service has started.
> Action to be Taken:No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starIUPSServiceStop
> Object ID
> enterprises.8164.2.1140
> Description
> An IUPS Service has stopped.
> Action to be Taken:This is typically caused by operator invention. In nusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the IUPS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the IUPS service is operational.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSGTPServiceStart
> Object ID
> enterprises.8164.2.1141
> Description
> A SGTP Service has started
> Action to be Taken:No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSGTPServiceStop
> Object ID
> enterprises.8164.2.1142
> Description
> A SGTP Service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken:If the SGTP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the SGTP service is operational.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starEPDGServiceStart
> Object ID
> enterprises.8164.2.1143
> Description
> A EPDG Service has started
> Action to be Taken:No action required.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starEPDGServiceStop
> Object ID
> enterprises.8164.2.1144
> Description
> A EPDG Service has stopped..
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken:If the EPDG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Clear Condition: Verify that the EPDG service is operational.
> Condition Clear Alarm: A starEPDGServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starApsCommandSuccess
> Object ID
> enterprises.8164.2.1145
> Description
> APS Command Succes Status.
> Objects
> starPortSlot
> starPortType
> Object
> starApsCommandFailure
> Object ID
> enterprises.8164.2.1146
> Description
> APS Command Failure Status.
> Objects
> starPortSlot
> starPortType
> Object
> starApsSwitchSuccess
> Object ID
> enterprises.8164.2.1147
> Description
> APS Switch Command Status.
> Objects
> starPortSlot
> starPortType
> Object
> starApsSwitchFailure
> Object ID
> enterprises.8164.2.1148
> Description
> APS Switch Command Failure Status.
> Objects
> starPortSlot
> starPortType
> Object
> starApsModeMismatch
> Object ID
> enterprises.8164.2.1149
> Description
> APS Mode Mismatch.
> Objects
> starPortSlot
> starPortType
> Object
> starApsChannelMismatch
> Object ID
> enterprises.8164.2.1150
> Description
> APS Channel Mismatch.
> Objects
> starPortSlot
> starPortType
> Object
> starApsByteMismatch
> Object ID
> enterprises.8164.2.1151
> Description
> APS Byte Mismatch.
> Objects
> starPortSlot
> starPortType
> Object
> starApsFeProtLineFailure
> Object ID
> enterprises.8164.2.1152
> Description
> APS FE Port Line Failure Status.
> Objects
> starPortSlot
> starPortType
> Object
> starApsLossOfRedundancy
> Object ID
> enterprises.8164.2.1153
> Description
> APS Loss of Redundancy.
> Objects
> starSlotNum
> starCardType
> starSlotNum
> starSlotNum
> Object
> starApsLossOfRedundancyClear
> Object ID
> enterprises.8164.2.1154
> Description
> APS Redundancy Restored.
> Objects
> starSlotNum
> starCardType
> starSlotNum
> starSlotNum
> Object
> starHNBGWSGSNRanapReset
> Object ID
> enterprises.8164.2.1155
> Description
> HNBGW has received RANAP Reset event from SGSN.
> This event is sent by SGSN whenever it restarts. Restart can be a normal boot of SGSN or because of failures at SGSN.
> HNBGW shall cleanup all the Iu connections with the SGSN.
> HNBGW shall send RUA Disconnect to HNB for the corresponding Ius.
> Objects
> starSessHNBGWVpnName
> starSessHNBGWServName
> starSessHNBGWPsNwName
> starSessHNBGWSgsnPtCd
> Object
> starHNBGWMSCRanapReset
> Object ID
> enterprises.8164.2.1156
> Description
> HNBGW has received RANAP Reset event from MSC.
> This event is sent by MSC whenever it restarts. Restart can be a normal boot of MSC or because of failures at MSC.
> HNBGW shall cleanup all the Iu connections with the MSC.
> HNBGW shall send RUA Disconnect to HNB for the corresponding Ius.
> Objects
> starServiceVpnName
> starSessHNBGWServName
> starSessHNBGWCsNwName
> starSessHNBGWMscPtCd
> Object
> starALCAPNodeReset
> Object ID
> enterprises.8164.2.1157
> Description
> HNBGW has received ALCAP Node Reset from MGW.
> This event is sent by MGW on restart. It also sends the event on detection of certain failures. MGW can also provide CLI to send the event.
> HNBGW shall terminate all the cs calls impacted due to the node reset.
> Objects
> starSessALCAPVpnName
> starSessALCAPServName
> starSessALCAPNodeName
> Object
> starALCAPPathReset
> Object ID
> enterprises.8164.2.1158
> Description
> HNBGW has received ALCAP Path Reset from MGW.
> This event is sent by MGW on detection of certain failures. MGW can also provide CLI to send the event.
> HNBGW shall terminate all the cs calls impacted due to the path reset.
> Objects
> starSessALCAPVpnName
> starSessALCAPServName
> starSessALCAPNodeName
> starSessALCAPPathId
> Object
> starALCAPPathBlock
> Object ID
> enterprises.8164.2.1159
> Description
> HNBGW has received ALCAP Path Block from MGW.
> This event is sent by MGW when maintenance activity needs to be performed. With the event MGW informs to block future calls on the Path.
> HNBGW shall not allow any future cs calls on the blocked path.
> This is cleared on receiving ALCAP Path Un Block from MGW.
> Objects
> starSessALCAPVpnName
> starSessALCAPServName
> starSessALCAPPathId
> Object
> starALCAPPathUnBlock
> Object ID
> enterprises.8164.2.1160
> Description
> HNBGW has received ALCAP Path Un Block from MGW.
> This event is sent by MGW when maintenance activity for blocked Path is over and it informs to allow future calls on the Path.
> HNBGW shall allow any future cs calls on the path.
> Objects
> starSessALCAPVpnName
> starSessALCAPServName
> starSessALCAPPathId
> Object
> starSGSServiceStart
> Object ID
> enterprises.8164.2.1161
> Description
> A SGS Service has started.
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starSGSServiceStop
> Object ID
> enterprises.8164.2.1162
> Description
> A SGS Service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Clear Condition: Verify that the SGS service is operational.
> Condition Clear Alarm: A starSGSServiceStart notification will be generated when the service is restarted
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starMMES1AssocFail
> Object ID
> enterprises.8164.2.1163
> Description
> An S1 Association between an MME service and an eNodeB has failed.
> Action to be Taken: If the shutdown of the eNodeB was not planned, determine the health/status of the eNodeB. If available, verify the health of the network between the two elements.
> Clear Condition: The condition is cleared with the S1 Association is reestablished.
> Objects
> starMMES1AssocVpnName
> starMMES1AssocServName
> starMMES1AssocENBID
> Object
> starMMES1AssocSetup
> Object ID
> enterprises.8164.2.1164
> Description
> An S1 Association between an MME service and an eNodeB has been established. Normally a starMMES1AssocSetup notification would be generated only for an associated which had previously failed, but optionally this notification can be generated for any association setup.
> Objects
> starMMES1AssocVpnName
> starMMES1AssocServName
> starMMES1AssocENBID
> Object
> starBNGServiceStart
> Object ID
> enterprises.8164.2.1165
> Description
> A BNG Service has started.
> Action to be Taken: No action required
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starBNGServiceStop
> Object ID
> enterprises.8164.2.1166
> Description
> A BNG Service has stopped.
> Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.
> Action to be Taken: If the BNG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure.
> Condition Clear Alarm: A starBNGServiceStart notification will be generated when the service is restarted.
> Objects
> starServiceVpnName
> starServiceServName
> Object
> starMVGPeerDown
> Object ID
> enterprises.8164.2.1169
> Description
> A MVG peer is down.
> Problem Cause: The MVG peer has failed, or a network connectivity prevents reaching the peer.
> Condition Clear Alarm: A starMVGPeerUp notification will be generated when the peer is up.
> Objects
> starServiceVpnName
> starPeerAddress
> starMVGEndpointName
> starMVGCauseCode
> starMVGProtocolType
> Object
> starMVGPeerUp
> Object ID
> enterprises.8164.2.1170
> Description
> A MVG peer is up. This notification is only generated for peers which have previously been declared down.
> Objects
> starServiceVpnName
> starPeerAddress
> starMVGEndpointName
> starMVGCauseCode
> starMVGProtocolType
> Object
> starPCCNtfyIntfPeerUnreachable
> Object ID
> enterprises.8164.2.1173
> Description
> The IPCF Event Notification Interface peer cannot be reached.
> Probable Cause: The Event Notification server on SPR is down Or the IP-address/port configuration does not match with the server
> Actions to be Taken: Check the Event notification server on SPR and ensure it is running. Ensure that IP-address port combination on IPCF match the server side configurations
> Clear Condition: Verify that the Event notification interface status on boxer is up.�
> Objects
> starPCCNtfyIntfPeerName
> Object
> starPCCNtfyIntfPeerReachable
> Object ID
> enterprises.8164.2.1174
> Description
> The Notification Interface peer can be reached.
> Action to be Taken: No Action Required.
> Objects
> starPCCNtfyIntfPeerName
> Standards-based Traps
> The following traps are defined in RFC 1157, Simple Network Management Protocol (SNMP) and are supported by the system:

> • | linkDown The Interface Index for this trap is the IfIndex for the physical port, not the logical interface.

> • | linkUp The Interface Index for this trap is the IfIndex for the physical port, not the logical interface.

> • | authenticationFailure

> • | enterpriseSpecific

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883