It is quite possible that either the unlisted server's beacon is down or the unlisted server is located in a different subnet. To restart the beacon do the following:
Redeploy the beacon and check its status:
- From the app server command prompt "niku add beacon" then "niku deploy beacon".
- Enter "niku status beacon". If it has a [+] next to it, it's ok (newer versions will not show this [+] sign but it will tell if the services are already there). Otherwise, run 'niku start beacon', and then 'niku status beacon', the results should tell you taht beacon is started.
- If the beacon is still not running, verify the path and verify that execute privileges are correctly setup for the nikubeacon executable.
If the above does not show results check with your IT department to determine if the unlisted server is on the same subnet as the other servers. Something else to consider is that multicast address, NSA password, and beacon port must be the same accross all servers in the Clarity Cluster environment.
Keyword: claritykb, beacon, cluster, multicast.