The Active alarm instance data, which can be viewed
from
Alarms &
Events, and then View
Active, contains the Transport Name as configured in
Transport
Manager, and then Configuration, and then Transport
Additional Information for the alarm can be found in
Alarms &
Events, and then View Active or View
History by locating the row with a sequence number
that matches the active alarm sequence number and viewing the Additional Info
column. This column will include the local and remote IP addresses and ports,
the administrative state, and the protocol state of the association.
This alarm is raised when:
The association is
configured and the admin state is enabled, but the SCTP transport is not in the
ASP-UP protocol state for the M3UA plugin, or
The association is
configured, but the SCTP transport is not in the APP-UP state for other plugins
Note:
It is normal to have an association alarm if the
association is in the Blocked or Disabled administrative state.
This alarm is cleared when:
The association
received an ASP-UP-ACK from the far-end and the SCTP transport in the ASP-UP
state for the M3UA plugin, or
The SCTP transport is
an APP-UP state for other plugins, or
The association is
disabled/deleted
If an association's protocol state does not match
the association's administrative state, the system will automatically attempt
to recover the association if configured as Initiator and enabled. Connection
attempts occur every "Connection Retry Interval" seconds, as defined in the
Transport Configuration Set screen for the configuration set used by the failed
association (default: 10 seconds).
Association administrative states are set from
Transport
Manager, and then Maintenance, and then Transport by clicking on the desired
action for the row containing the association. This screen is also used to
monitor association status.
To troubleshoot:
If the association is
manually Blocked or Disabled, then no further action is necessary.
Verify the
association's local IP address and port number are configured on the IP
Signaling Gateway (Some Signaling Gateways only accept connections from IP
addresses and ports they are configured to accept from).
Verify the
association's remote IP address and port correctly identify an SCTP listening
port on the adjacent server.
Verify IP network
connectivity exists between the MP server and the adjacent server.
Check the event
history logs at
Alarms &
Events, and then View
History for additional SS7 events or alarms from this
MP server.
Verify the adjacent
server on the Signaling Gateway is not under maintenance.
If the alarm persists, it is recommended to contact
My Oracle Support
if further assistance is needed.