Impossible to connect to any feature of any nodes when using the Univiewer Console over VPN
Article ID: 86380
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Affects Release version(s): 5
Error Message :
No error.
Patch level detected:Dollar Universe 5.6.0
Product Version: Dollar.Universe 5.6.0 FX25010
Description :Univiewer Console (standalone or web console)is used over a VPN connection.
Connection is OK between console and Management server, but Impossible to connect to any feature of any nodes. Time-out when the user try to access any kind of feature like (node settings, job runs, development of objcest). BUT the nodes are seen as UP in the node list.
Error Message :
No error.
Patch level detected:Dollar Universe 5.6.0
Product Version: Dollar.Universe 5.6.0 FX25010
Description :Univiewer Console (standalone or web console)is used over a VPN connection.
Connection is OK between console and Management server, but Impossible to connect to any feature of any nodes. Time-out when the user try to access any kind of feature like (node settings, job runs, development of objcest). BUT the nodes are seen as UP in the node list.
Environment
OS: All
OS Version: All
OS Version: All
Cause
Cause type:
Configuration
Root Cause: The VPN system does not authorize entering connections on TCP ports of the Dollar Universe IO, CDJ and DQM ports .
Configuration
Root Cause: The VPN system does not authorize entering connections on TCP ports of the Dollar Universe IO, CDJ and DQM ports .
Resolution
Provide to the customer all TCP ports that are used by DUAS and DQM (if used). The list could be similar to the following one.
The simplest way to identify these ports is to refer to the /etc/services on UNIX and c:\windows\system32\drivers\etc\services on Windows, like in the following example:
TST560_IO_X 10600/tcp # Io server area X
TST560_IO_S 10601/tcp # Io server area S
TST560_IO_I 10602/tcp # Io server area I
TST560_IO_A 10603/tcp # Io server area A
TST560_CMD 10604/tcp # Command server
TST560_CMD_X 10604/tcp # Command server
TST560_CMD_S 10604/tcp # Command server
TST560_CMD_I 10604/tcp # Command server
TST560_CMD_A 10604/tcp # Command server
TST560_BVS_X 10605/tcp # BVS server area X
TST560_BVS_S 10606/tcp # BVS server area S
TST560_BVS_I 10607/tcp # BVS server area I
TST560_BVS_A 10608/tcp # BVS server area A
TST560_CDJ_X 10611/tcp # Collect dispatch job area X
TST560_CDJ_S 10612/tcp # Collect dispatch job area S
TST560_CDJ_I 10613/tcp # Collect dispatch job area I
TST560_CDJ_A 10614/tcp # Collect dispatch job area A
TST560_DQM_X 10615/tcp # Access DQM on Area X.
The firewalls rules should take in account this port definition and allow entering connection on them.
It is also mandatory that the DNS resolution of hostnames is correction forwarded on the VPN channel, otherwise connection to the node will not work. Reason therefore: in the node settings the hosts is often declared with his hostname.
Fix Status: Released
Fix Version(s):
Component: Application.Server
Version: Dollar.Universe 5.6.0 FX25010
The simplest way to identify these ports is to refer to the /etc/services on UNIX and c:\windows\system32\drivers\etc\services on Windows, like in the following example:
TST560_IO_X 10600/tcp # Io server area X
TST560_IO_S 10601/tcp # Io server area S
TST560_IO_I 10602/tcp # Io server area I
TST560_IO_A 10603/tcp # Io server area A
TST560_CMD 10604/tcp # Command server
TST560_CMD_X 10604/tcp # Command server
TST560_CMD_S 10604/tcp # Command server
TST560_CMD_I 10604/tcp # Command server
TST560_CMD_A 10604/tcp # Command server
TST560_BVS_X 10605/tcp # BVS server area X
TST560_BVS_S 10606/tcp # BVS server area S
TST560_BVS_I 10607/tcp # BVS server area I
TST560_BVS_A 10608/tcp # BVS server area A
TST560_CDJ_X 10611/tcp # Collect dispatch job area X
TST560_CDJ_S 10612/tcp # Collect dispatch job area S
TST560_CDJ_I 10613/tcp # Collect dispatch job area I
TST560_CDJ_A 10614/tcp # Collect dispatch job area A
TST560_DQM_X 10615/tcp # Access DQM on Area X.
The firewalls rules should take in account this port definition and allow entering connection on them.
It is also mandatory that the DNS resolution of hostnames is correction forwarded on the VPN channel, otherwise connection to the node will not work. Reason therefore: in the node settings the hosts is often declared with his hostname.
Fix Status: Released
Fix Version(s):
Component: Application.Server
Version: Dollar.Universe 5.6.0 FX25010
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
