Unsolved
This post is more than 5 years old
3 Posts
0
1784
fp_socket_error -10101 (jcenteraverify)
since a few days we have communication problems between an application and centera. Both tcp/udp port 3218 are open, telnet works, the PEA file works between centera node and replication node. but when I try jcenteraverify on the application host with the pea file I got this error. error within the application: "EMC CENTERA NOT FOUND AT POOL ADDRESS" or "error on network socket hostname/nn/POOLINFO". can this be firewall related, maybe some changes ?
**************************************************************
************** Start of JCenteraVerify log ******************
**************************************************************
--------------------- General information -----------------------
Time: Mon Mar 11 11:28:20 CET 2013
Tool Version: 3.2.23
SDK Version: 3.2.607
--------------------- User configuration ------------------------
TOOL SETTINGS
Number Of Files: 3
FileSize (KB): 1, 10, 100
Working Dir: .\Temp
Restore Dir: .\Temp\Retrieve
Log File: .\JCenteraVerify.log
Delete temp Files: true
Delete restore Files: true
SDK SETTINGS
Number of Retries: -1
Retry Sleep: -1
----------------- JCenteraVerify test results -------------------
ACCESS NODE CONNECTIVITY CHECK
"IP Adress Centera Node 1"?K:\evdaten\centera_pae\RS_ARCH.pea is not available.
FP_SOCKET_ERR -10101
"IP Adress Centera Node 2"?K:\evdaten\centera_pae\RS_ARCH.pea is not available.
FP_SOCKET_ERR -10101
"IP Adress Centera Node 3"??K:\evdaten\centera_pae\RS_ARCH.pea is not available.
FP_SOCKET_ERR -10101
"IP Adress Centera Node 4"??K:\evdaten\centera_pae\RS_ARCH.pea is not available.
FP_SOCKET_ERR -10101
"IP Adress Centera Node 5"??K:\evdaten\centera_pae\RS_ARCH.pea is not available.
FP_SOCKET_ERR -10101
"IP Adress Centera Node 6"??K:\evdaten\centera_pae\RS_ARCH.pea is not available.
FP_SOCKET_ERR -10101
**************************************************************
***************** End of JCenteraVerify log ****************
**************************************************************
cincystorage
467 Posts
1
March 14th, 2013 00:00
In my experience this is caused by a network problem. Has the host which is running centera verify been able to successfully run centera verify again this centera cluster before? This can also be due to your access nodes running out of memory. Is this consistent or sporadic? I'd engage emc for a health check, just to be sure.
susika1
3 Posts
0
March 15th, 2013 01:00
well it seems after a lot try and error, that the 1st access node didn't reply within an amount of time. even the other nodes are slow. when I remove the 1st node, all the others answer within poor time ... don't know whats wrong with it. EMC Support case still open ... health check o.k. ... no heavy load they say. strange.
cincystorage
467 Posts
0
March 15th, 2013 01:00
First thing I would check would be the network pork settings not being full duplex. I've seen that setting cause something very similar.