Troubleshooting
Problem
What ports need to be open if there is a firewall between the Domain Server and the Primary Storage Server
Symptom
Discovery Storage is not working. Customer is seeing the following error in the Domain Server TADDM logs when trying to run a discovery:
2012-04-17 13:55:58,385 ProcessFlowManager
[DiscoveryServerHeartbeatThread] ERROR topomgr.TopologyManagerFactory - connection failed for server [adm2stl16:build=FP220120103:jini=4160:web=33030:webSSL=33031:api=9530:a pissl=9531]
2012-04-17 13:56:33,405 ProcessFlowManager [DiscoveryServerHeartbeatThread] ERROR topomgr.TopologyManagerFactory - connection failed for server
[adm2stl16:build=FP220120103:jini=4160:web=33030:webSSL=33031:api=9530:a pissl=9531].
Cause
This is caused by not properly configuring the firewall and ports needed by the Domain Server and Primary Storage Server to communicate..
Diagnosing The Problem
The $COLLATION_HOME/dist/services/ProcessFlowManager.log on the Domain Server will show where it poll's back and forth as it should. If the proper configuration of the firewall and ports is not in place, it will also show a failure there.
Example:
[DiscoveryServerHeartbeatThread]
DEBUG cdb.TopologyManagerServiceFactory - findRemoteService(adm2stl16:4160) using cached service accessor
2012-04-17 12:36:11,295 ProcessFlowManager [RMI TCP Connection(99)-10.154.20.25] DEBUG
processflowmgr.ProcessFlowManagerImpl - getDependentServiceStatus() 2012-04-17 12:36:11,295 ProcessFlowManager [RMI TCP Connection(99)-10.154.20.25]
DEBUG processflowmgr.ProcessFlowManagerImpl - getDependentServiceStatus() - true
2012-04-17 12:36:11,295 ProcessFlowManager [RMI TCP Connection(99)-10.154.20.25]
DEBUG shared.ActivatableSharedService - Shared ping DiscoveryService returns true: AuthorizationManager=true
SecurityManager=true ApiServer=true ClientProxy=true DiscoverObserver=true ProcessFlowManager=true Template=true Semaphore=true ProfileManager=true
2012-04-17 12:36:31,213 ProcessFlowManager [DiscoveryServerHeartbeatThread] ERROR
cdb.TopologyManagerServiceFactory - findRemoteService(adm2stl16:4160) failed after 20.006 seconds
2012-04-17 12:36:31,213 ProcessFlowManager [DiscoveryServerHeartbeatThread] ERROR topomgr.TopologyManagerFactory - connection failed for server
[adm2stl16:build=FP220120103:jini=4160:web=33030:webSSL=33031:api=9530:a pissl=9531]
In order to resolve the error, and explain what one should look for in the logs, here is a quick overview on how Storage Server Pool works :
- Storage Server pool is managed by Primary Storage Server
- Secondary Storage Servers register themselves with Primary Storage Server
- Discovery Servers are notified when a Storage Server is added or removed (or fails).
- Storage servers can be added at any time without reconfiguring Discovery Servers.
- Discovery Server will try another server from the pool if an existing server fails, and retry any failed operation.
- Running discoveries, UI operations, etc are unaffected by Secondary Storage Server failures.
- If all Storage Servers have failed, Discovery Servers must wait for Primary Storage Server to recover (failover).
- Storage Servers are also data portals. By default the Primary Storage Server is used.
Resolving The Problem
Setting up ports on the Domains Server and Primary Storage Server if a firewall is involved between the two servers.
- Setting up Firewall on the side of Primary Storage Server:
In case user has a firewall on the side of Primary Storage Server the following ports (for TADDM default port setting) needs to be open
Table 1. Communication ports used by the firewallDefault port Description Direction
4160 TPC The port used for communicating unicast discovery information.
It is the listening port of the TADDM database. Incoming and
Outgoing
9430 TPC The port used for communicating HTTP information.
Incoming and Outgoing
9433 TPC The port used for communicating naming service information.
Outgoing
9435 TPC The port used for communicating RMI information.
Outgoing
9540 TPC The port used for communicating security manager information in an enterprise environment.
Outgoing
9550 TPC The port used for communicating topology manager information in an enterprise environment.
Outgoing
19430 TPC The port used for communicating topology manager information.
Incoming and Outgoing
19431 TPC The port used for communicating change manager information.
Outgoing
19432 TPC The port used for communicating API server information.
Outgoing
19433 TPC The port used for communicating user registry information.
Incoming and Outgoing
19434 TPC The port used for communicating reports server information.
Outgoing
19435 TPC The port used for communicating user registry information.
Incoming and Outgoing
If you have changed any of the default ports set in $COLLATION_HOME/etc/collation.properties, you must ensure that you open ports that are appropriate to how your environment is configured.
The following default port values are set in $COLLATION_HOME/etc/collation.properties, on the discovery server:
com.collation.jini.unicastdiscoveryport=4160
com.collation.webport=9430
com.collation.rmiport=9433
com.collation.commport=9435
com.collation.TopologyManager.port=19430
com.collation.ChangeManager.port=19431
com.collation.ApiServer.port=19432
com.collation.SecurityManager.port=19433
com.collation.ReportsServer.port=19434
- Setting up Firewall on the side of Discovery Server:
In case user has a firewall on the side of Discovery Server the following ports (for TADDM default port setting) need to be open
4160 The port used for communicating unicast discovery information. It is the listening port of the TADDM database. Incoming and Outgoing
9430 The port used for communicating HTTP information. Incoming and
Outgoing
9432 The port used for communicating HTTP information. Incoming and
Outgoing
5637 The port used for communicating HTTP information. Incoming and
Outgoing
If you have changed any of the default ports set in $COLLATION_HOME/etc/collation.properties, you must ensure that you open ports that are appropriate to how your environment is configured.
The following default port values are set in $COLLATION_HOME/etc/collation.properties, on the discovery server:
com.collation.jini.unicastdiscoveryport=4160
com.collation.webport=9430
com.collation.rmiport=9433
com.collation.commport=9435
com.collation.TopologyManager.port=19430
com.collation.ChangeManager.port=19431
com.collation.ApiServer.port=19432
com.collation.SecurityManager.port=19433
com.collation.ReportsServer.port=19434
Product Synonym
TADDM
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21591740