Unsolved
This post is more than 5 years old
9 Posts
0
3009
Online Cluster not reachable
Hello,
I was trying to connect to one of the online clusters, but i couldn't find a responding one. (https://community.emc.com/docs/DOC-1038)
Here is an extract from trying to traceroute 128.221.200.56 (EMEA1)
tracert 128.221.200.56
Routenverfolgung zu 128.221.200.56 über maximal 30 Abschnitte...
4 143 ms 134 ms 134 ms was-sa3-i.was.us.net.dtag.de [62.156.131.182]
5 134 ms 134 ms 133 ms 62.156.128.110
6 136 ms 136 ms 144 ms sl-crs1-dc-0-12-0-0.sprintlink.net [144.232.19.5]
7 136 ms 137 ms 137 ms sl-crs1-rly-0-2-0-0.sprintlink.net [144.232.19.222]
8 139 ms 139 ms 139 ms sl-crs1-pen-0-5-3-0.sprintlink.net [144.232.20.213]
9 136 ms 136 ms 136 ms sl-crs1-nyc-0-4-0-1.sprintlink.net [144.232.20.122]
10 145 ms 139 ms 139 ms sl-crs1-spr-0-0-0-0.sprintlink.net [144.232.18.207]
11 141 ms 141 ms 141 ms sl-st21-bos-0-0-0.sprintlink.net [144.232.8.50]
12 144.223.45.62 meldet: Zielnetz nicht erreichbar.
Does someone have an idea when this problem will be fixed?
Greetings
Simon
mckeown_paul
409 Posts
1
April 29th, 2009 03:00
Hi
I just connected to the cluster so it is up.
Is this the first time you have tried to use it? Please make sure that your firewall allows access via port 3218 for BOTH UDP and TCP.
S_Kraemer
9 Posts
0
April 29th, 2009 03:00
Hi again,
thank you for the fast response.
No, i have connected this cluster several times in the last few months.
There has never been a problem, so I assume the settings are ok.
Well, it seems the problem is a server at sprintlink.net.
I think i'll just wait for half an hour and retry again.
Simon
S_Kraemer
9 Posts
0
April 29th, 2009 04:00
I have to apologize.
It seems that there was some bug in my application, two characters twisted, which caused the problem.
The not working traceroute did the rest.
Thank you for your answers.
Simon
mckeown_paul
409 Posts
0
April 29th, 2009 04:00
Hi Simon
I'm in the UK and I have tried it again on a laptop outside of our corporate network (so I'm using the internet diectly) and it works fine for me.
Is it possible your Network people have blocked port 3218 since you last used it?
S_Kraemer
9 Posts
0
April 29th, 2009 04:00
Ok,
i just tried connecting again.
The problem is still there.
Is there someone outside of the US who can verify this?
mckeown_paul
409 Posts
0
April 29th, 2009 04:00
Heres my tracert
$ tracert 128.221.200.56
Tracing route to us1 [128.221.200.56]
over a maximum of 30 hops:
1 90 ms 99 ms 99 ms BeBox.config [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 24 ms 90 ms 25 ms xe-9-1-0.edge3.London1.Level3.net [212.113.15.65]
6 25 ms 25 ms 25 ms ae-11-51.car1.London1.Level3.net [4.69.139.66]
7 25 ms 25 ms 25 ms sl-bb21-lon-10-0-0.sprintlink.net [213.206.131.21]
8 25 ms 27 ms 24 ms sl-bb22-lon-3-0.sprintlink.net [213.206.129.153]
9 94 ms 93 ms 108 ms sl-crs1-nyc-0-5-2-0.sprintlink.net [144.232.9.163]
10 97 ms 97 ms 107 ms sl-crs1-spr-0-0-0-0.sprintlink.net [144.232.18.207]
11 99 ms 98 ms 98 ms sl-st21-bos-0-0-0.sprintlink.net [144.232.8.50]
12 144.223.45.62 reports: Destination net unreachable.
Trace complete.
which looks similar to yours but my pool connect works okay anyway
mckeown_paul
409 Posts
0
April 29th, 2009 04:00
Mr Murphy strikes again!
No problem Simon, I'm glad you got it working!