Configuring Discovery Agent
Follow the instructions in the Linux Discovery Agent README file (which you download from the Cloud Portal) to configure the Discovery Agent on a Linux server.
For Windows, update the Cloud Portal or appliance settings based on the discovery mode you choose. You can choose the Cloud Portal, manual, or local portal as the discovery mechanism.
Configuring Discovery Agent through Cloud Portal
For Cloud Accelerator for AWS virtual appliances, you can configure the Discovery Agent using the Cloud Portal.
1. Log in to your Windows server and double-click the Riverbed Discovery Agent icon in the system tray.
2. Select Settings.
3. Click Configure to display the Configure Discovery Agent page. The default Use Riverbed Portal mode is automatically selected.
4. Click Edit to display the Riverbed Portal Configuration dialog box. Specify these parameters:
– Client ID enables you to copy and paste the client ID from the Cloud Portal.
– Client Key enables you to copy and paste the client key from the Cloud Portal.
– Configure HTTP Proxy makes the fields below editable and configures an HTTP proxy server to connect to the Cloud Portal.
– Proxy Hostname or IP specifies the proxy server hostname or IP address.
– Proxy Port specifies the port number of the proxy server.
Configuring Discovery Agent manually
If you are using the Discovery Agent with Cloud Accelerator virtual appliances for Azure and ESXi, you must manually configure the Discovery Agent.
1. Log in to your Windows server and double-click the Riverbed Discovery Agent icon in the system tray.
2. Select Settings.
3. Click Configure to display the Configure Discovery Agent page. Click Manual to display the Manual Configuration page.
4. Choose a load-balancing policy from the drop-down list:
– Priority selects a Cloud Accelerator for load balancing until its connection count exceeds the maximum and then moves on to the next available Cloud Accelerator. When the load of the first Cloud Accelerator decreases below the maximum, it is available again. This policy is the default setting.
– Round robin selects a Cloud Accelerator and then another (using the round-robin policy) for load balancing. Use the round-robin policy only if the connection rate is high and you need more than one Cloud Accelerator to handle the load.
5. Either specify a Cloud Accelerator to connect to the Discovery Agent, or add a new Cloud Accelerator to connect to the Discovery Agent.
6. Enter the IP address of the Cloud Accelerator, and then click OK. The Cloud Accelerator is added to the appliances list in the Configuration Dialog box.
You can use the arrows to adjust the priority in which the Discovery Agent connects to the Cloud Accelerator.
Configuring Discovery Agent using local portal mode
If you are using your own local portal and not the Cloud Portal, you can configure the Discovery Agent using the local portal mode for Cloud Accelerator for AWS virtual appliances.
1. Log in to your Windows server and double-click the Riverbed Discovery Agent icon in the system tray.
2. Select Settings.
3. Click Configure.
4. Click Configure Local Portal. The Local Portal Configuration page displays the portal hostname or IP address, client ID, and client key, and proxy settings that you specified in the installation wizard.
5. Click Edit to display the Riverbed Portal Configuration dialog box.
6. Specify these parameters in the Riverbed Portal Configuration dialog box:
– Client ID specifies the client ID of your Cloud Accelerator or server on which you want to configure the Discovery Agent.
– Client Key specifies the client key of your Cloud Accelerator or server on which you want to configure the Discovery Agent.
– Configure HTTP Proxy makes the fields below editable and configures an HTTP proxy server to connect to the portal.
– Proxy Hostname or IP specifies the proxy server hostname or IP address.
– Proxy Port specifies the port number of the proxy server.