What are SS7 SGC alarms?

Alarms in the SS7 SGC stack alert the administrator to exceptional conditions. Subsystems in the SS7 SGC stack raise them upon detecting an error condition or an event of high importance. The SS7 SGC stack clears alarms automatically when the error conditions are resolved; an administrator can clear any alarm at any time. When an alarm is raised or cleared, the SS7 SGC stack generates a notification that is sent as a JMX Notification and an SNMP trap/notification.

The SS7 SGC stack defines multiple alarm types. Each alarm type corresponds to a type of error condition or important event (such as "SCTP association down"). The SGC stack can raise multiple alarms of any type (for example, multiple "SCTP association down" alarms, one for each disconnected association).

Alarms are inspected and managed through a set of commands exposed by the Command-Line Management Console, which is distributed with SGC SS7 Stack.

Tip
See also

Below are details of Active Alarms and Event History, Generic Alarm Attributes, and Alarm Types.

Active alarms and event history

The SS7 SGC Stack stores and exposes two types of alarm-related information:

  • active alarms — a list of alarms currently active

  • event history — a list of alarms and notifications that where raised or emitted in the last 24 hours (this is default value — see Configuring the SS7 SGC Stack).

At any time, an administrator can clear all or selected alarms.

Tip
See also

Supported CLI Operations for Alarms and Event history

Generic alarm attributes

Alarm attributes represent information about events that result in an alarm being raised. Each alarm type has the following generic attributes, plus a group of attributes specific to that alarm type (described in the following sections).

There are two types of generic attribute; basic and extended.

Basic attributes:

  • Are displayed by default in the SGC’s CLI.

  • They are always included in full in SNMP traps.

  • And they are returned in full by SNMP queries.

Extended attributes:

  • Are not displayed by default in the SGC’s CLI. This behaviour may be overridden by specifiying additional columns using the column attribute in the display-active-alarm or display-event-history CLI commands.

  • Will be included in an SNMP trap or inform if the SNMP agent is configured for extended-traps, otherwise these will be omitted.

  • Are returned in full by SNMP queries.

The full set of attributes is described in the following table:

Attribute Type Description

id

basic

A unique alarm instance identifier, presented as a number. This identifier can be used to track alarms, for example by using it to identify the raise and clear event entries for an alarm in the event history, or to refer to a specific alarm in the commands which can be used to manipulate alarms.

name

basic

The name of the alarm type. A catalogue of alarm types is given below.

severity

basic

The alarm severity:

  • CRITICAL — application encountered an error which prevents it from continuing (it can no longer provide services)

  • MAJOR — application encountered an event which significantly impacts delivered services; some services may no longer be available

  • MINOR — application reports an event which does not have significant impact on delivered services

  • INFO — application reports an information event which does not have any impact on delivered services

  • CLEARED — alarm has been cleared.

timestamp

basic

The date and time at which the event occurred.

parameters

basic

A comma-separated list of key=value pairs specific to the alarm. The catalogue below documents the parameters each alarm may have.

description

basic

A short description of the alarm.

longDescription

extended

A longer description of the alarm.

cause

extended

A guide to some possible causes of the alarm. The described causes should not be considered exhaustive.

effect

extended

The possible consequences of the condition that caused the alarm to be raised.

action

extended

Actions that can be taken to remedy the alarm. Note that not all remedies can be described within the constraints of an alarm text. Refer back to this guide or contact support for more assistance.

Alarm types

This section describes all alarm types that can be raised in an SGC cluster.

General Alarms

This section describes alarms raised concerning the general operational state of the SGC or SGC cluster.

commswitchbindfailure

The CommSwitch is unable to bind to the configured switch-local-address and switch-port. This alarm is cleared when the CommSwitch is able to successfully bind the configured address and port.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

commswitchbindfailure

severity

alarm severity

CRITICAL

timestamp

timestamp when the event occurred

description

short alarm description

The CommSwitch was unable to bind its listen port

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

nodeId

affected node

failureDescription

the cause of the bind failure

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

The CommSwitch is unable to bind to the configured switch-local-address and switch-port. This alarm is cleared when the CommSwitch is able to successfully bind the configured address and port.

cause

possible alarm causes

Typically misconfigured; the administrator must ensure that the CommSwitch is configured to use a host and port pair which is always available for the SGC’s exclusive use.

effect

potential consequences

SGC nodes in the same cluster are unable to route messages to each other.

action

summary of remedial action

Correct the SGC’s CommSwitch configuration or locate and terminate the process that is bound to the SGC’s CommSwitch address and port.

configSaveFailed

This alarm is raised when the SGC is unable to save its configuration. This alarm is cleared when the configuration file is next successfully saved.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

configSaveFailed

severity

alarm severity

MAJOR

timestamp

timestamp when the event occurred

description

short alarm description

Failed to save SGC configuration

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

nodeId

affected node

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised when the SGC is unable to save its configuration. This alarm is cleared when the configuration file is next successfully saved.

cause

possible alarm causes

Insufficient storage space, or changes to the read/write permissions of any previously saved configuration files.

effect

potential consequences

The SGC configuration may be out of date or not saved at all.

action

summary of remedial action

Examine SGC logs to determine cause of save failure and rectify.

distributedDataInconsistency

This alarm is raised when a distributed data inconsistency is detected. This alarm must be cleared manually since it indicates a problem that may result in undefined behaviour within the SGC, and requires a restart of the SGC cluster to correct. When restarting the cluster it is necessary to fully stop all SGC nodes and only then begin restarting them to properly correct the problem detected by this alarm.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

distributedDataInconsistency

severity

alarm severity

CRITICAL

timestamp

timestamp when the event occurred

description

short alarm description

a distributed data inconsistency has been detected

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

nodeId

affected node

source

the location where the data inconsistency was detected

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised when a distributed data inconsistency is detected. This alarm must be cleared manually since it indicates a problem that may result in undefined behaviour within the SGC, and requires a restart of the SGC cluster to correct. When restarting the cluster it is necessary to fully stop all SGC nodes and only then begin restarting them to properly correct the problem detected by this alarm.

cause

possible alarm causes

A distributed data inconsistency has been detected; the most likely cause of this is a misconfigured backup-count parameter in hazelcast.xml

effect

potential consequences

Undefined behaviour from the SGC is possible at any time

action

summary of remedial action

Fully terminate the cluster, correct the underlying issue, then restart the whole cluster

illegalClusterEntry

This alarm is raised when a node that doesn’t support the current cluster version enters the cluster. This alarm must be cleared manually.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

illegalClusterEntry

severity

alarm severity

CRITICAL

timestamp

timestamp when the event occurred

description

short alarm description

A node entered the cluster with an unsupported distributed data version.

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

nodeInfo

information about the illegally entering node

mode

current cluster mode

clusterVersion

current cluster version

targetVersion

target cluster version

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised when a node that doesn’t support the current cluster version enters the cluster. This alarm must be cleared manually.

cause

possible alarm causes

A node that doesn’t support the current cluster version entered the cluster.

effect

potential consequences

Potential for cluster data corruption and instability.

action

summary of remedial action

Terminate the node that doesn’t support the current cluster version. Evaluate cluster status.

mapdatalosspossible

This alarm is raised when the number of SGC nodes present in the cluster exceeds 1 plus the backup-count configured for Hazelcast map data structures. See Hazelcast cluster configuration for information on how to fix this. This alarm must be cleared manually since it indicates a configuration error requiring correction and a restart of the SGC.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

mapdatalosspossible

severity

alarm severity

MAJOR

timestamp

timestamp when the event occurred

description

short alarm description

Hazelcast data loss possible due to mismatch between configured map backup count and actual cluster size

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

backupCount

the currently configured backup count

nodeCount

the number of nodes in the cluster when at its largest

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised when the number of SGC nodes present in the cluster exceeds 1 plus the backup-count configured for Hazelcast map data structures. See Hazelcast cluster configuration for information on how to fix this. This alarm must be cleared manually since it indicates a configuration error requiring correction and a restart of the SGC.

cause

possible alarm causes

Misconfiguration of cluster nodes or unexpected nodes have entered the cluster.

effect

potential consequences

Potential for distributed data loss.

action

summary of remedial action

See Hazelcast cluster configuration for information on how to correct this.

migrationErrors

This alarm is raised when errors are encountered during the data migration phase of an SGC cluster upgrade or revert. This alarm must be cleared manually since it indicates a potentially critical error during the cluster upgrade which may have an impact on cluster stability.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

migrationErrors

severity

alarm severity

CRITICAL

timestamp

timestamp when the event occurred

description

short alarm description

Errors were encountered during data migration

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

sourceVersion

data version before migration

targetVersion

data version being migrated to

migrationErrors

detailed information about the migration errors

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised when errors are encountered during the data migration phase of an SGC cluster upgrade or revert. This alarm must be cleared manually since it indicates a potentially critical error during the cluster upgrade which may have an impact on cluster stability.

cause

possible alarm causes

One or more errors were encountered during the data migration phase of an SGC cluster upgrade or revert.

effect

potential consequences

The SGC cluster’s behaviour may be undefined, either now or in the future.

action

summary of remedial action

Run bin/generate-report.sh on each cluster member, then terminate the whole cluster. Reinstate the previous cluster version from backups and start the old cluster. Submit a support request.

nodeManagerBindFailure

This alarm is raised when the legacy node manager is unable to bind to the configured stack-http-address and stack-http-port for any reason. This is typically caused by misconfiguration; the administrator must ensure that the node manager is configured to use a host and port pair which is always available for the SGC’s exclusive use. This alarm is cleared when the node manager is able to successfully bind the configured socket.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

nodeManagerBindFailure

severity

alarm severity

CRITICAL

timestamp

timestamp when the event occurred

description

short alarm description

The legacy node manager was unable to bind its listen socket

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

nodeId

affected node

failureDescription

additional information about the failure

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised when the legacy node manager is unable to bind to the configured stack-http-address and stack-http-port for any reason. This is typically caused by misconfiguration; the administrator must ensure that the node manager is configured to use a host and port pair which is always available for the SGC’s exclusive use. This alarm is cleared when the node manager is able to successfully bind the configured socket.

cause

possible alarm causes

The configured stack-http-address and stack-http-port cannot be bound.

effect

potential consequences

Legacy TCAP stacks (those using the urlList method) will not be able to connect to the affected SGC.

action

summary of remedial action

Ensure that stack-http-address and stack-http-port are correctly configured and that no other applications have bound the configured address and port.

nodefailure

This alarm is raised whenever a node configured in the cluster is down. It is cleared when an SGC instance acting as that particular node becomes active.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

nodefailure

severity

alarm severity

MAJOR

timestamp

timestamp when the event occurred

description

short alarm description

A node has left the cluster.

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

nodeId

affected node

failureDescription

additional information about the node failure

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever a node configured in the cluster is down. It is cleared when an SGC instance acting as that particular node becomes active.

cause

possible alarm causes

A configured node is not running. This may be due to administrative action, or the node may have exited abnormally.

effect

potential consequences

Any remaining cluster nodes will continue to provide service.

action

summary of remedial action

Determine why the node is not running, resolve any issues and restart the stopped node.

poolCongestion

This alarm is raised whenever over 80% of a pool’s pooled objects are in use. This is typically caused by misconfiguration, see Static SGC instance configuration. It is cleared when less than 50% of pooled objects are in use.

Note
What is a task pool?

A task pool is a pool of objects used during message processing, where each allocated object represents a message that may be processing or waiting to be processed. Each SGC node uses separate task pools for outgoing and incoming messages.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

poolCongestion

severity

alarm severity

MAJOR

timestamp

timestamp when the event occurred

description

short alarm description

Task Pool congestion occurred

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

nodeId

affected node

poolName

name of the affected task pool

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever over 80% of a pool’s pooled objects are in use. This is typically caused by misconfiguration, see Static SGC instance configuration. It is cleared when less than 50% of pooled objects are in use.

cause

possible alarm causes

Misconfiguration

effect

potential consequences

None unless poolExhaustion alarm is also raised

action

summary of remedial action

Examine the SGC’s sizing requirements

poolExhaustion

This alarm is raised whenever a task allocation request is made on a pool whose objects are all already allocated. This is typically caused by misconfiguration, see Static SGC instance configuration. This alarm must be cleared manually.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

poolExhaustion

severity

alarm severity

MAJOR

timestamp

timestamp when the event occurred

description

short alarm description

Task Pool exhaustion occurred

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

nodeId

affected node

poolName

name of the affected task pool

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever a task allocation request is made on a pool whose objects are all already allocated. This is typically caused by misconfiguration, see Static SGC instance configuration. This alarm must be cleared manually.

cause

possible alarm causes

A task allocation request is made on a task pool whose members are all in use

effect

potential consequences

Delays processing messages and/or messages being dropped

action

summary of remedial action

Examine the SGC’s sizing requirements.

workgroupCongestion

This alarm is raised when the worker work queue is over 80% occupied. It is cleared when the worker work queue is less than 50% occupied.

Note
What is a worker group?

A worker group is a group of workers (threads) that are responsible for processing tasks (incoming/outgoing messages). Each worker has a separate work queue.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

workgroupCongestion

severity

alarm severity

MAJOR

timestamp

timestamp when the event occurred

description

short alarm description

Workgroup thread is congested

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

nodeId

affected node

threadIndex

affected worker index

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised when the worker work queue is over 80% occupied. It is cleared when the worker work queue is less than 50% occupied.

cause

possible alarm causes

The queue of tasks waiting to be processed is larger than 80% of the configured maximum worker queue size

effect

potential consequences

Tasks may fail to be queued if the workgroup congestion hits 100%

action

summary of remedial action

Examine the SGC’s sizing requirements.

M3UA

This section describes alarms raised concerning the M3UA layer of the SGC cluster.

asConnDown

This alarm is raised when an AS connection which was active becomes inactive. This alarm can be caused either by misconfiguration at one or both ends of the M3UA association used, such as by a disagreement on the routing context to be used, or by network failure. It is cleared when the Application Server becomes active on the connection.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

asConnDown

severity

alarm severity

MAJOR

timestamp

timestamp when the event occurred

description

short alarm description

AS is down on selected connection

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

asId

the affected AS

connectionId

name of affected connection

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised when an AS connection which was active becomes inactive. This alarm can be caused either by misconfiguration at one or both ends of the M3UA association used, such as by a disagreement on the routing context to be used, or by network failure. It is cleared when the Application Server becomes active on the connection.

cause

possible alarm causes

Misconfiguration of one or both ends of the M3UA association or network failure.

effect

potential consequences

The affected AS connection cannot be used for message send or receive.

action

summary of remedial action

Correct configuration or resolve network failure.

asDown

This alarm is raised whenever a configured M3UA Application Server is not active. This alarm is typically caused by either a misconfiguration at one or both ends of an M3UA association or by network failure. It is cleared when the Application Server becomes active again.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

asDown

severity

alarm severity

MAJOR

timestamp

timestamp when the event occurred

description

short alarm description

AS identified by asId is DOWN

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

asId

the affected AS

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever a configured M3UA Application Server is not active. This alarm is typically caused by either a misconfiguration at one or both ends of an M3UA association or by network failure. It is cleared when the Application Server becomes active again.

cause

possible alarm causes

Misconfiguration of one or both ends of the M3UA association or network failure.

effect

potential consequences

The Application Server is down and messages cannot be sent or received on that AS

action

summary of remedial action

Correct configuration or resolve network failure.

associationCongested

This alarm is raised whenever an SCTP association becomes congested. An association is considered congested if the outbound queue size grows to more than 80% of the configured out-queue-size for the connection. This alarm is cleared when the outbound queue size drops below 50% of the configured out-queue-size.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

associationCongested

severity

alarm severity

MINOR

timestamp

timestamp when the event occurred

description

short alarm description

Association is congested

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

connectionId

name of affected connection

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever an SCTP association becomes congested. An association is considered congested if the outbound queue size grows to more than 80% of the configured out-queue-size for the connection. This alarm is cleared when the outbound queue size drops below 50% of the configured out-queue-size.

cause

possible alarm causes

The association’s outbound queue size has grown to more than 80% of the configured out-queue-size.

effect

potential consequences

Possible higher latency sending M3UA messages and if the queue becomes full, message send failure.

action

summary of remedial action

Examine the SGC’s sizing requirements

associationDown

This alarm is raised whenever a configured connection is not active. This alarm is typically caused either by a misconfiguration at one or both ends of the M3UA association or by network failure. It is cleared when an association becomes active again.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

associationDown

severity

alarm severity

MAJOR

timestamp

timestamp when the event occurred

description

short alarm description

Association is not established

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

connectionId

name of affected connection

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever a configured connection is not active. This alarm is typically caused either by a misconfiguration at one or both ends of the M3UA association or by network failure. It is cleared when an association becomes active again.

cause

possible alarm causes

Misconfiguration at one or both ends of the M3UA association or network failure.

effect

potential consequences

The SCTP association will not be used.

action

summary of remedial action

Correct configuration or resolve network failure.

associationPathDown

This alarm is raised whenever a network path within an association becomes unreachable but the association as a whole remains functional because at least one other path remains available. This alarm is only raised for assocations using SCTP’s multi-homing feature (i.e. having multiple connection IP addresses assigned to a single connection). Association path failure is typically caused by either misconfiguration at one or both ends or by network failure. This alarm will be cleared when SCTP signals that the path is available again, or when all paths have failed, in which case a single associationDown alarm will be raised to replace all the former associationPathDown alarms.

Note This alarm will also always be raised briefly during association establishment for all paths within the association which SCTP does not consider primary while SCTP is testing the alternative paths.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

associationPathDown

severity

alarm severity

MINOR

timestamp

timestamp when the event occurred

description

short alarm description

SCTP association path is down

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

connectionId

name of affected connection

pathId

the peer address which has become unreachable

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever a network path within an association becomes unreachable but the association as a whole remains functional because at least one other path remains available. This alarm is only raised for assocations using SCTP’s multi-homing feature (i.e. having multiple connection IP addresses assigned to a single connection). Association path failure is typically caused by either misconfiguration at one or both ends or by network failure. This alarm will be cleared when SCTP signals that the path is available again, or when all paths have failed, in which case a single associationDown alarm will be raised to replace all the former associationPathDown alarms.

cause

possible alarm causes

A network path within the SCTP association has become unreachable.

effect

potential consequences

Other path(s) within the association will be used.

action

summary of remedial action

Correct configuration or resolve network failure.

associationUnresolvable

This alarm is raised whenever an association is detected to be configured with an unresolvable remote address. This alarm will be cleared whenever a connect attempt is made using any address on the association and the unresolvable address has since become resolvable. It may also be cleared if the connection is disabled and the address has become unresolvable.

Since automatic clearing of the alarm is dependent upon association activity (reconnect attempts or disabling) this may not happen for some time - for example if there are alternate addresses and one of those was used for a successful connect. In this case the user may prefer to clear the alarm manually.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

associationUnresolvable

severity

alarm severity

MINOR

timestamp

timestamp when the event occurred

description

short alarm description

SCTP association address could not be resolved

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

connectionId

name of affected connection

address

the peer address which could not be resolved

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever an association is detected to be configured with an unresolvable remote address. This alarm will be cleared whenever a connect attempt is made using any address on the association and the unresolvable address has since become resolvable. It may also be cleared if the connection is disabled and the address has become unresolvable.

cause

possible alarm causes

An association has been configured with an unresolvable remote address.

effect

potential consequences

If this is the only address on the association, then the association will be DOWN. If other resolvable addresses exist, one of these will be used to establish the association.

action

summary of remedial action

Correct configuration or resolve network failure (e.g. DNS lookup).

dpcRestricted

This alarm is raised when the SGC receives a Destination Restricted message from its remote SGP or IPSP peer for a remote destination point code. It is cleared when the DPC restricted state abates on a particular SCTP association.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

dpcRestricted

severity

alarm severity

MINOR

timestamp

timestamp when the event occurred

description

short alarm description

DPC is restricted on this connection in the context of AS

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

asId

the affected AS

dpcId

the affected DPC

connectionId

name of affected connection

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised when the SGC receives a Destination Restricted message from its remote SGP or IPSP peer for a remote destination point code. It is cleared when the DPC restricted state abates on a particular SCTP association.

cause

possible alarm causes

The remote SGP or IPSP peer has sent a Destination Restricted message to the SGC.

effect

potential consequences

The SGC will route traffic to the affected DPC via an alternate route if possible.

action

summary of remedial action

None at the SGC.

dpcUnavailable

This alarm is raised when a configured DPC is unreachable through a particular SCTP association. It is cleared when a DPC becomes reachable again through the particular SCTP association.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

dpcUnavailable

severity

alarm severity

MINOR

timestamp

timestamp when the event occurred

description

short alarm description

Dpc is not reachable on this connection in the context of AS

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

asId

the affected AS

dpcId

the affected DPC

connectionId

name of affected connection

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised when a configured DPC is unreachable through a particular SCTP association. It is cleared when a DPC becomes reachable again through the particular SCTP association.

cause

possible alarm causes

Network failure or misconfiguration.

effect

potential consequences

The DPC cannot be reached through the affected connection and affected AS.

action

summary of remedial action

Correct configuration or resolve network failure.

mtpCongestion

This alarm is raised whenever a remote MTP reports congestion for an association and a specific destination point code normally reachable through that association. It is cleared when the remote MTP reports that congestion has abated.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

mtpCongestion

severity

alarm severity

MINOR

timestamp

timestamp when the event occurred

description

short alarm description

MTP congestion reported (SCON)

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

connectionId

name of affected connection

dpcId

the affected DPC

mtpCongestionLevel

the reported MTP congestion level (ANSI only)

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever a remote MTP reports congestion for an association and a specific destination point code normally reachable through that association. It is cleared when the remote MTP reports that congestion has abated.

cause

possible alarm causes

The remote MTP has reported congestion.

effect

potential consequences

Standard MTP congestion procedures are followed.

action

summary of remedial action

None; the alarm is automatically cleared when the remote MTP reports abatement.

SCCP

This section describes Alarms raised by the SCCP subsystem.

sccpLocalSsnProhibited

This alarm is raised whenever all previously connected TCAP stacks (with the CGIN RA) using a particular SSN become disconnected. This is typically caused by either network failure or administrative action (such as deactivating an RA entity in Rhino). It is cleared when at least one TCAP stack configured for the affected SSN connects.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

sccpLocalSsnProhibited

severity

alarm severity

MAJOR

timestamp

timestamp when the event occurred

description

short alarm description

SSN that is prohibited

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

ssn

affected SubSystem

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever all previously connected TCAP stacks (with the CGIN RA) using a particular SSN become disconnected. This is typically caused by either network failure or administrative action (such as deactivating an RA entity in Rhino). It is cleared when at least one TCAP stack configured for the affected SSN connects.

cause

possible alarm causes

All TCAP stacks registered for the affected SSN have disconnected.

effect

potential consequences

Messages received for the affected SSN will follow SCCP return procedures.

action

summary of remedial action

Correct network failure or resolve administrative action.

sccpRemoteNodeCongestion

This alarm is raised whenever a remote SCCP node reports congestion. It is cleared when the congestion abates. This alarm will only be emitted when the sccp-variant in General Configuration is configured for ITU. See mtpCongestion for information on MTP-level congestion notification (SCON/MTP-STATUS) alarms.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

sccpRemoteNodeCongestion

severity

alarm severity

MINOR

timestamp

timestamp when the event occurred

description

short alarm description

Remote DPC reports congestion

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

dpc

affected PointCode

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever a remote SCCP node reports congestion. It is cleared when the congestion abates. This alarm will only be emitted when the sccp-variant in General Configuration is configured for ITU. See mtpCongestion for information on MTP-level congestion notification (SCON/MTP-STATUS) alarms.

cause

possible alarm causes

The remote SCCP has reported congestion.

effect

potential consequences

ITU-T SCCP congestion algorithms will be applied to the specified DPC.

action

summary of remedial action

None; this alarm is automatically cleared when congestion abates.

sccpRemoteNodeNotAvailable

This alarm is raised whenever a remote SCCP node becomes unavailable. It is cleared when the remote node becomes available.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

sccpRemoteNodeNotAvailable

severity

alarm severity

MINOR

timestamp

timestamp when the event occurred

description

short alarm description

Remote DPC is no longer available

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

dpc

affected PointCode

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever a remote SCCP node becomes unavailable. It is cleared when the remote node becomes available.

cause

possible alarm causes

The remote SCCP node has become unavailable.

effect

potential consequences

The remote SCCP will not have messages sent to it.

action

summary of remedial action

None; this alarm is cleared when the remote SCCP becomes available.

sccpRemoteSsnProhibited

This alarm is raised whenever a remote SCCP node reports that a particular SSN is prohibited. It is cleared when the remote SCCP node reports that the affected SSN is available.

The following table shows the basic attributes raised as part of this alarm.

Attribute Description Values of constants

id

unique alarm identifier

name

name of alarm type

sccpRemoteSsnProhibited

severity

alarm severity

MINOR

timestamp

timestamp when the event occurred

description

short alarm description

Remote subsystem is prohibited

Additionally, the parameters attribute is a basic attribute consisting of a comma-separated list of key=value pairs containing the following alarm-specific parameters:

Attribute Description

dpc

affected PointCode

ssn

affected SubSystem

This alarm’s extended attributes have the following fixed values:

Attribute Description Value

longDescription

long alarm description

This alarm is raised whenever a remote SCCP node reports that a particular SSN is prohibited. It is cleared when the remote SCCP node reports that the affected SSN is available.

cause

possible alarm causes

The remote SCCP has reported the affected SSN to be prohibited.

effect

potential consequences

The affected SSN at the affected point code will not have messages sent to it.

action

summary of remedial action

None; this alarm is cleared when the remote SCCP reports that the affected SSN is available.
Previous page Next page