How to identify if port 9021 is open on the ECS node

Just a couple more suggestions ...

If you're having trouble verifying the file server in CTA (i.e. your S3 configuration to ECS), make sure you're using a base URL (configured in ECS) and the correct port is set in CTA rain.xml file.  The configuration for S3 in CTA defaults to 80/443 and uses virtually hosted bucket addressing (http://{bucket_name}.my.ecs.com:9020).

The rain.xml file is located in: /opt/rainfinity/filemanagement/conf/rain.xml

Once you've updated rain.xml, make sure to run: filemanagement restart

For the base URL, you will need a way to resolve the host name and then make sure it's also configured in ECS.

Ben

From the CTA, you can use the CLI to test.  First, you need the IP address or name of your ECS node.  You can use the telnet command to check, using the format 'telnet 9021 '.  In my case, my ECS node is 10.134.5.120:

fma-prod:~ # which telnet

/usr/bin/telnet

fma-prod:~ # ping 10.134.5.120

PING 10.134.5.120 (10.134.5.120) 56(84) bytes of data.

64 bytes from 10.134.5.120: icmp_seq=1 ttl=63 time=0.187 ms

64 bytes from 10.134.5.120: icmp_seq=2 ttl=63 time=0.161 ms

^C

--- 10.134.5.120 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 3999ms

rtt min/avg/max/mdev = 0.160/0.182/0.231/0.026 ms

fma-prod:~ # telnet 10.134.5.120 9021

Trying 10.134.5.120...

Connected to bmh-ecs01.bronsonhg.org.

Escape character is '^]'.

^CConnection closed by foreign host.

In this example, the ECS node was listening on the port and allowed me to attempt a connection.  If this port is not open, it looks like this:

fma-prod:~ # telnet 10.134.5.220 9100

Trying 10.134.5.220...

In this case, this node never allowed the connection.

Let us know if that helps!

Karl

I tried Pinging the ECS node from the CTA which works fine, but when I am trying to do a telnet it fails. Also the traceroute to ECS fails.

Have checked with the Firewall team and NW team and they confirmed that there is no Firewall btw them and we may have to required routes are added on both source and destination machines/devices.

Not sure how to take this forward.

you could ssh onto one of the nodes and try telnet from there (don't use localhost or 127.0.0.1).

You could also try netstat to see if the port is actually open and listening:

netstat -tulpn | grep 902

That's a good idea from coneryj .  How many nodes in your ECS?  SSH into one of the nodes (for example node 1) and try to run telnet command to node 2.  I don't think the failed tracepath is of concern.  Are your ECS nodes and CTA appliance on different subnets?  Can you give some details on the network config?

schumb@USENSCHUMBL4C MINGW64 /c/Projects/sdk-tools/bucket-perf/build/libs (master)

$ ssh admin@10.1.83.51 <---- THIS IS NODE 1 IN MY CLUSTER

Password:

Password:

Last failed login: Thu Jul 13 13:51:13 UTC 2017 from 128.222.228.53 on ssh:notty

There was 1 failed login attempt since the last successful login.

Last login: Thu Jul 13 13:41:26 2017 from 10.97.6.143

admin@ecs-obj-1-1:~> telnet 10.1.83.52 9020 <-- THIS IS NODE 2 IN MY CLUSTER

Trying 10.1.83.52...

Connected to 10.1.83.52.

I was able to get the nodes visible to the AWS S3 bucket.

But when I am trying to add the CTA to the S# bucket but it throws an error stating that " the URL is not the correct one" I am using CTA version 10.0 SP3 and someone told me that I need to upgrade this to either 11 or 12 so that I can get the CTA communicate with the AWS S3 browser to ECS.

I was able to get the nodes visible to the AWS S3 bucket.

But when I am trying to add the CTA to the S# bucket but it throws an error stating that " the URL is not the correct one" I am using CTA version 10.0 SP3 and someone told me that I need to upgrade this to either 11 or 12 so that I can get the CTA communicate with the AWS S3 browser to ECS.

That's correct.  If you're running VNX or Unity backed with ECS/S3 you need to use CTA 11.  Again, don't forget you need to use a base URL and manually set the port in CTA rain.xml file to use 9020/9021.