Note: Please see the TSSA RSCD Agent Connectivity Troubleshooting Guide for more details on troubleshooting this issue.

Attempting to add/access/verify a target with TrueSight Server Automation (TSSA) RSCD Agent returns "No Authorization to acces host".



The rscd.log file on the target contains the following "Host not granted access" error:

EXAMPLE #1:
06/11/17 13:57:37.073 WARN     rscd -  ::ffff:XX.XX.XX.XX 12550 -1/-1 (Not_available): (Not_available): Host not granted access 

EXAMPLE #2:
03/20/23 10:04:31.174 WARN     rscd -  ::1 278792 SYSTEM (Not_available): (Not_available): Host not granted access

 

The 'exports' file on Target Server is not allowing NSH/RSCD communication from the source machine (NSH client, Appserver etc)

The solution is add the IP Address or Hostname shown in the error message to the 'exports' file.(located under 'C:\windows\rsc' for Windows server or '/etc/rsc' for Linux/Unix)

Example:
XX.XX.XX.XX rw,user=xxx

If after doing suggested steps still see the same error, clear file content and enter manually the entries since old exports file could be corrupted

This IP is an example. See the following doc for more details on how to correctly configure the exports file:

https://docs.bmc.com/docs/tssa2102/configuring-the-exports-file-975414464.html

The exports file determines which BMC Server Automation clients have access to a server. With the exports file you can set permissions on a per-client basis and, when necessary, use the users or users.local files to override those permissions for particular users. Often the exports file is used to set global permission that apply to users on all client machines.

NOTE:
- If the target server is behind socks proxy, then make sure the following:
   1) Socks proxy is configured under 'Proxy Servers' in 'Infrastructure Management' along with a network routing rule for the target
   2) Target 'exports' file contains the socks proxy IP address together with the appserver IP addresses
   3) Example #2 can occur when only a single appserver IP address is configured in 'exports' file not allowing incoming connection as loop back. In such cases, including the appserver hostname will help getting around the issue. Also depending on NSH script/command that is being run against the target, it may require target hostname to be added in the 'exports' file for loop back.