Start a Conversation

Unsolved

This post is more than 5 years old

5637

February 5th, 2009 08:00

CenteraPing fails. Why?

Hi,

I am currently using the Centera-Ping Tool to test a connection to Centerastar on the internet.

Would you please be so kind to give me a hint (or several hints) why I am experiencing this behaviour of CenterePing:

C:\>RunMe.bat

C:\>CenteraPing.exe -address 128.221.200.60?us2_profile1_rqecw.pea
128.221.200.60?us2_profile1_rqecw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.61?us2_profile1_rqecw.pea
128.221.200.61?us2_profile1_rqecw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.62?us2_profile1_rqecw.pea
128.221.200.62?us2_profile1_rqecw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.63?us2_profile1_rqecw.pea
128.221.200.63?us2_profile1_rqecw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.60?us2_profile2_rdqecw.pea
128.221.200.60?us2_profile2_rdqecw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.61?us2_profile2_rdqecw.pea
128.221.200.61?us2_profile2_rdqecw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.62?us2_profile2_rdqecw.pea
128.221.200.62?us2_profile2_rdqecw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.63?us2_profile2_rdqecw.pea
128.221.200.63?us2_profile2_rdqecw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.60?us2_profile3_rdqeDcw.pea
128.221.200.60?us2_profile3_rdqeDcw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.61?us2_profile3_rdqeDcw.pea
128.221.200.61?us2_profile3_rdqeDcw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.62?us2_profile3_rdqeDcw.pea
128.221.200.62?us2_profile3_rdqeDcw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>CenteraPing.exe -address 128.221.200.63?us2_profile3_rdqeDcw.pea
128.221.200.63?us2_profile3_rdqeDcw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

C:\>REM CenteraPing.exe -address 128.221.200.60,128.221.200.61,128.221.200.62,12
8.221.200.63?us2_profile1_rqecw.pea

C:\>REM CenteraPing.exe -address 128.221.200.60,128.221.200.61,128.221.200.62,12
8.221.200.63?us2_profile2_rdqecw.pea

C:\>REM CenteraPing.exe -address 128.221.200.60,128.221.200.61,128.221.200.62,12
8.221.200.63?us2_profile3_rdqeDcw.pea

C:\>

Thank you very much & best regards

Adrian

136 Posts

February 5th, 2009 09:00

Hi Adrian,

I just tested the cluster with one of the PEA files you used and it seems to be responding for all but 1 access node. The one access node might be having some connectivity issues:

C:\CenteraPing.exe -address 128.221.200.60,128.221.200.61,128.221.200.62,128.221.200.63?C:\us2_profile3_rdqeDcw.pea
128.221.200.60?C:\us2_profile3_rdqeDcw.pea is accessible
128.221.200.61?C:\us2_profile3_rdqeDcw.pea is
accessible
128.221.200.62?C:\us2_profile3_rdqeDcw.pea is not accessible
SDK  Error        :-10020
SDK Error Message :no primary cluster found

128.221.200.63?C:\us2_profile3_rdqeDcw.pea is accessible

Are you behind a firewall that is preventing you to access the online clusters?

Thanks,

Zeeshan

10 Posts

February 6th, 2009 00:00

Hi Zheshaan,

Many thanks. So my assumption seems to be correct: The firewall is most probably blocking us. We have requested to open the firewall from our firewall team, they have opened the firewall but it still doesnt work. Here is the request we used:

Source   (hostname and/or IP)

Destination   (hostname and/or IP)

Destination

Port   #

System  

(internal source hostname and ip)

128.221.200.60 

128.221.200.61  

128.221.200.62  

128.221.200.63

Port 3218 (TCP/UDP)

Internet Firewall

 


Is there any additional information I should add about the EMC protocol what seems to be missing?

Best regards

Adrian

10 Posts

February 6th, 2009 06:00

Exactely. Thank you!

The hardest part is to find out how the INBOUND traffic actually comes in (from Centerastart to CenteraSDK). Is it UDP? TCP? Which port?I could not find any description of that on the EMC website.

Can you help?

136 Posts

February 6th, 2009 06:00

You need to tell your network security folks to open up the firewall for both inbound and outbound traffic so that you are able to send and receive requests. 

417 Posts

February 6th, 2009 07:00

Cluster probes use UDP in both directions. Other operations use TCP.

So you must open port 3218 inbound and outbound for both TCP and UDP.

No Events found!

Top