PreviousNextJavaScript must be enabled to correctly display this content
19402 - Failed to Connect Transport
Alarm Group:
TMF
Description:
Failed to connect Transport
Severity:
Info
Instance:
<TransportName>
HA Score:
Normal
Auto Clear Seconds:
60
OID:
awptransmgrFailedToConnectTransportNotify
Recovery:
The Transport named in the Instance field has failed
in a connection attempt. If configured as an SCTP Initiator, the system will
automatically attempt to recover the association/connection. Connection
attempts occur every "Connection Retry Interval" seconds, as defined in the
Transport Configuration Set screen for the configuration set used by the failed
transport (default: 10 seconds). If configured as an SCTP or UDP Listener, no
further action is taken.
To troubleshoot
Verify the transport's
local IP address and port number are configured on the Adjacent Node (Some
Nodes only accept connections from IP addresses and ports they are configured
to accept connections from).
Verify the transport's
remote IP address and port correctly identify an SCTP listening port on the
adjacent node.
Verify IP network
connectivity exists between the MP and the adjacent node.
Verify the timers in
the transport's configuration set are not set too short to allow the connection
to proceed. This should be rare if the IP network is functioning correctly.
Check the event
history logs at
Alarms &
Events > View
History for additional SS7 events or alarms from this
MP server.
Verify 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.