Configure Unidirectional Agent - Server Communication

Available only in vFabric Hyperic

If your security policies dictate, you can configure the agent to initiate all communications with the HQ Server. You can configure unidirectional communications at first startup. Unidirectional communications are always via SSL.

This section has instructions for changing agent communications from bidirectional to unidirectional and vice versa after the agent has already been configured.

Changing from Bidirectional to Unidirectional Communications

  1. Stop the agent.

  2. Remove the agent's \data directory.

    • Removing the \data directory will cause the agent, at next startup, to look for the startup settings it needs to connect to the HQ Server in its agent.properties file; if the properties file doesn't contain them, it will prompt for settings in the shell.

  3. Configure the agent for unidirectional communications using one of these methods:

    • If your practice is to provide all agent startup properties in the properties file, edit agent.properties to set agent.setup.unidirectional=yes, and start the agent.

    • If your practice is to configure the agent startup properties interactively, start the agent, and respond "yes" when asked if the agent should be configured for unidirectional communications.

  4. In the HQ user interface, navigate to the platform's Inventory tab and click Edit in the "Type & Network Properties" section.

    • In the edit view for "Type & Network Properties", the "Agent Connection" drop-down list will show your currently selected port for bidirectional communications, something like 10.2.0.213:2144, where 10.2.0.213 is the IP address of the platform, and 2144 is the bidirectional port number previously used.

  5. Expand the drop-down list and select the entry that shows the same IP address, and "-1" as the port:

  6. 10.2.0.213:-1

    • Your agent will now use unidirectional communications.

Changing from Unidirectional to Bidirectional Communications

  1. Stop the agent.

  2. Remove the agent's data directory.

    • Removing the data directory will cause the agent, at next startup, to look for the startup settings it needs to connect to the HQ Server in its agent.properties file; if the properties file doesn't contain them, it will prompt for settings in the shell.

  3. Configure the agent for bidirectional communications using one of these methods:

    • If your practice is to provide all agent startup properties in the properties file, edit agent.properties to set agent.setup.unidirectional=no, and start the agent.

    • If your practice to configure the agent startup properties interactively, start the agent, and when prompted for communications direction, respond "no" when asked if the agent should be configured to run in uni-directional mode.

  4. In the HQ user interface, navigate to the platform's Inventory tab and click Edit in the "Type & Network Properties" selection.

  5. Select the appropriate agent in the "Agent Connection" drop down.

    • In the edit view for "Type & Network Properties", the "Agent Connection" drop-down list will show your currently selected port for unidirectional communications, something like 10.2.0.213:-1, where 10.2.0.213 is the IP address of the platform, and -1 is the port number.

  6. Expand the drop-down list and select the entry that shows the same IP address, and "2144" as the port (or the port you are configured to use, if not the default), for example, 10.2.0.213:2144

    • Your agent will now use bidirectional communications.