Understanding the NSH and RSCD agent requirements

This topic provides information about the requirements and environment considerations regarding the Network Shell (NSH) and Remote System Call Daemon (RSCD) agents.

Requirements

• The BMC Server Automation Rich Client Platform (BSA RCP) client must be installed on at least one of the hosts where the dispatcher service is installed. The BSA RCP client contains NSH and an authentication tools for connecting to the NSH proxy. 
• RSCD agents must be installed on every target from which you want to retrieve files or to which you want to deploy.  RSCD agents must be configured on the same port as the NSH client installed on the dispatcher host. 
• When you create servers in BMC VaraLogix Q Deployment Automation, you must set the Agent to NSH and the Agent Server to the host where the dispatcher and NSH are installed. This enables you to use NSH to communicate to and from that server. 

Environment considerations related to the NSH proxy

• To retrieve files in a package from a target behind an NSH proxy, you must set the following properties on that package:
  • BLCRED_PROFILE—Profile created by the user outside of RLM on the dispatcher host to authenticate to the NSH proxy/BSA
  • BLUSER—User name to authenticate
  • BLPASSWORD—Password to authenticate
  • (Optional: 4.3.00 and earlier) BL_ROLE and BL_RBAC_ROLE—If the user has more than one role and you do not want to use the default role for that user, you must set this property.
  • (Optional: 4.3.01 and later) BL_RBAC_ROLE—If the user has more than one role and you do not want to use the default role for that user, you must set this property.

• To deploy to targets behind an NSH proxy, you need the same properties but set in Topology.  Those are the Channel properties, but they can be set on the environment if all channels in that environment are managed by the same user/role.
• Package properties overwrite Topology properties. If you have defined the properties in the package and those properties differ to connect to a target during deployment, you must remove or overwrite those properties.
• Only one user/role can be handled per dispatcher at a time.  Blcred stores a file in the same location every time it is called in NSH.  If you try to do two deployments at the same time with different roles,the collision causes the first deployment to fail.