Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Proxy servers

The BMC Server Automation environment can include the following proxy servers:

  • Network Shell proxy servers
     Network Shell proxy servers are used as a security enhancement measure. A Network Shell proxy server authenticates the Network Shell client user and associates an appropriate RBAC role to it. This ensures that NSH commands are launched only after the NSH client user is authenticated as a particular RBAC user and role. The NSH proxy serves as a single point for configuration of authentication, replacing the need for such configuration on each of the agents. For optimum security, BMC always recommends the use of Network Shell proxy servers.
  • SOCKS proxies
     To access targets that are behind a firewall (for example, because they are in a remote data center) or otherwise not directly accessible from the Application Servers, BMC recommends using SOCKet Secure (SOCKS) proxy servers. In this situation, do the following:
    • Locate a SOCKS proxy server in each remote data center and configure firewalls to allow the Application Servers to contact the SOCKS proxy server over port 1080.
    • Configure the Application Server to establish communications with the remote targets by using the SOCKS proxy server, usually over port 4750, instead of contacting the remote hosts directly.

      A SOCKS proxy server normally requires minimal computing power. However, it requires network bandwidth commensurate with its role as a communication concentrator for the remotely-managed targets.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Server Automation 8.3