Specifications

Using the Configuration CLI Commands

Configuration CLI Commands

Note: The highest strength cipher that Policy Manager currently

supports is the 3DES 168-bit cipher. However, the Policy Manager can

be configured to use the AES 256-bit cipher. For more information,

refer to the EMC Secure Remote Support Policy Manager Operations

Guide.

• add-proxy. If applicable, provide Proxy Server for Policy

Manager only with the following parameters:

– http or socks. The proxy will be used for Gateway Client to

Policy Manager communication only. It will not affect the

communication between the Gateway Client and the EMC

Enterprise.

Note: If the Gateway Client cannot connect to the Policy Manager

using the proxy you entered, it will attempt to connect without

using the proxy server.

– proxy-host, provide with the IP address.

– proxy-port, provide with the port number.

• proxy-user. If applicable, provide with user name and

password.

Note: You must provide a username and password if you are using a

SOCKS proxy.

3. Running the command links the Gateway Client to the Policy

Manager.

4. You can verify the connection by running the

config_policy_manager.sh -- list command.

Disabling

communication

To disable communication between a Gateway Client and a Policy

Manager, run the following command:

[root@185rhel62d Gateway]# ./config_policy_manager.sh

--remove

Error : 0 Agent PM changes successful

Note: An Error code of 0 as above means sucessful; any other result

(alpha or numeric) indicates some failure to complete sucessfully.

Figure 63 config_policy_manager.sh --remove command