Feb 25, 2008 #1 LambMan Technical User Mar 17, 2005 97 GB Does anybody know which tcp ports need to be opened up on firewalls for CMS RTA feeds? Is there a way to specify which ports are used on the CMS for these feeds or are they always on the same port range? Cheers.
Does anybody know which tcp ports need to be opened up on firewalls for CMS RTA feeds? Is there a way to specify which ports are used on the CMS for these feeds or are they always on the same port range? Cheers.
Feb 26, 2008 #3 theblackbag Technical User Mar 23, 2007 34 GB Different feeds use different ports, and it looks like it is configurable. To confirm go to /export/home/pserv and check for any rta directories, for instance rta_iex. In the rta folder do a 'cat startrta | grep wtmout'. This should tell you which host is using which port on that particular feed. Ian. Upvote 0 Downvote
Different feeds use different ports, and it looks like it is configurable. To confirm go to /export/home/pserv and check for any rta directories, for instance rta_iex. In the rta folder do a 'cat startrta | grep wtmout'. This should tell you which host is using which port on that particular feed. Ian.
Feb 26, 2008 #4 BIS Technical User Jun 1, 2001 1,893 NL On some versions that command will not give an output. In the startrta script, the port will be defined like $home/rta_iex1 iex 6996 acd1 (In this case 6996) Upvote 0 Downvote
On some versions that command will not give an output. In the startrta script, the port will be defined like $home/rta_iex1 iex 6996 acd1 (In this case 6996)
Feb 26, 2008 Thread starter #5 LambMan Technical User Mar 17, 2005 97 GB Excellent thanks for the info! Upvote 0 Downvote
May 28, 2008 #6 Zowwie438 Programmer Aug 27, 2004 74 US There are default ports that are used, however from what I have read they can be customized on the CMS side. Remember that CMS is the client and your RTA box/app is the server. So it's the CMS client that is selecting the ports to talk on, not the RTA. If you have a spare linux box on the same subnet, you can simply fire up tcpdump -s0 -X not port ssh and dst [your rta box ip] This will show you everthing that is talking to that box and their associated ports. Your could also do: tcpdump -s0 -X not port ssh and dst [your rta box] and src [your cms ip] Good luck. ==Zow Upvote 0 Downvote
There are default ports that are used, however from what I have read they can be customized on the CMS side. Remember that CMS is the client and your RTA box/app is the server. So it's the CMS client that is selecting the ports to talk on, not the RTA. If you have a spare linux box on the same subnet, you can simply fire up tcpdump -s0 -X not port ssh and dst [your rta box ip] This will show you everthing that is talking to that box and their associated ports. Your could also do: tcpdump -s0 -X not port ssh and dst [your rta box] and src [your cms ip] Good luck. ==Zow