Oracle Key Manager (OKM) - SOAP Error: connect failed in tcp

Asset ID:	1-72-1924424.1
Update Date:	2017-12-22
Keywords:

Solution Type Problem Resolution Sure

Solution 1924424.1 : Oracle Key Manager (OKM) - SOAP Error: connect failed in tcp_connect(), Error Code = 28

Applies to:

Oracle Key Manager - Version 2.3 to 3.3 [Release 2.0 to 3.0]
Information in this document applies to any platform.

Symptoms

Cannot connect to the eLOM network of KMA 3.

Management port of KMA 3 has been going up and down.

Peer KMA 1 is not able to connect to KMA 3:
----

A45BBC378BDDA35500000000002616D1 A45BBC378BDDA355 KMA03 Cluster Client Communication Medium Term Retention Request Peer Replication Service SOAP Error Warning 000088000025 2014-08-28 20:18:25.233147+00 KMA01 121.126.128.125 Peer KMA ID = 8A651AD391646ECC, Peer KMA Name = va2kmmfm01, Peer KMA Network Address = 121.126.128.125, Function Name = RequestAntiEntropyPush, SOAP Fault Code = SOAP-ENV:Client, SOAP Fault String = Timeout, SOAP Fault Detail = connect failed in tcp_connect(), Error Code = 28 If the peer KMA is currently applying initial updates after joining the Cluster, then wait until it completes applying these updates. Otherwise, check the management network connection on the KMA reporting the issue as well as the peer KMA. If this condition persists, then one of these KMAs might need to be rebooted.

Peer KMA 3 stopped responding:
---

06F4E686402172CF00000000018B5B14 06F4E686402172CF KMA02 Cluster Operations Medium Term Retention Update Peer Response Peer Stopped Responding Warning 000089000228 2014-08-28 20:17:31.403812+00 va2kmmfm03 121.222.127.22 Peer KMA ID = A45BBC378BDDA355, Peer KMA Name = KMA03, Peer KMA Network Address = 121.222.127.22 Check the network connection to the peer KMA as well as the peer KMA itself. If this condition persists, then the peer KMA might need to be rebooted.

Changes

none

Cause

Possible network or server socket issues causing TCP connection timeout errors

Solution

Try rebooting the KMA.
  Refer to: KMS - How to Correctly Shutdown and Reboot a KMA Document 1019656.1

If the ELOM is not responding after a reboot or power cycle:
  Try attaching a monitor and a keyboard to the KMA's serial port and see if the system processor comes up.
  If the system processor does not come up, there may be a problem with the system board and the system board may have to be replaced.
  If the system processor comes up, there may be a problem with the ELOM network - i.e., check port, cable, and switch.

Attachments

This solution has no attachment