Symptoms

Provider is trying to open Hardware Nodes list in POA PP, but following error is returned by POA:

The operation you are trying to perform requires interaction with a component, which is presently unavailable. Please try again later.

Following errors are registered in /var/log/poa-ui.log at POA-UI host:

2014-03-01 09:32:01,974 0563a5fffb ec-68 DEBUG  ERR Caused by: org.omg.CORBA.COMM_FAILURE: 
Cannot connect to host '<POA MN host name>/<POA MN IP address>', port 8520 (java.net.ConnectException: Connection refused)  
vmcid: 0x444f7000  minor code: 266  completed: No

Or manual POA agent installation fails with following message in installation log:

MSI (s) (60!E0) [17:04:30:239]: Product: POA Agent -- POA Error: getCredentials: CORBA error: ExSystem: module_id:'Kernel', ex_type_id:'10',Message:'The operation can not be completed because the following component is missing                  or is not running: hub (sc_name '', sc_id #0)', deprecated_codes = (6, 0), properties = { service_type: 'hub',sc_name: '',sc_id: '0', }
Method name 
taskDeployApplicationInstanceFiles on OBJREF:SaaSManagerTasks:0:getAPSSharedTasks:0
Last execution output   
Destination host 'hostname' (#40), IP 'IP' : attribute 'perm' is not declared for element 'EXTRACT'

Netstat shows the following:

> netstat -na |findstr <POA Core IP>
TCP    192.168.9.54:52171     <POA Core IP>:8354      ESTABLISHED
TCP    192.168.9.54:52172     <POA Core IP>:8564      SYN_SENT

Cause

In "Firewall Configuration Guide" the range of TCP ports 8352-8500 is requested to be open at POA Management Node. Slave POA hosts must be able to connect to those TCP ports at POA MN, however, due to POA-83394, TCP port of service controller can step out of range of accepted ports

Resolution

Please contact your account manager regarding POA-83394 or allow ports with numbers greater than 8500 for access on management node.

Internal content