19402 - Failed to connect Transport
- Event Type:
- TMF
- Description:
- Failed to connect Transport
- Severity:
- Info
- Instance:
- <TransportName>
- HA Score:
- Normal
- Throttle 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 that the
transport's local IP address and port number are configured on the Adjacent
Node (Some Nodes will only accept connections from IP addresses and ports they
are configured to accept connections from).
- Verify that the
transport's remote IP address and port correctly identify an SCTP listening
port on the adjacent node.
- Verify that IP network
connectivity exists between the MP and the adjacent node.
- Verify that 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
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 (MOS).
