Deploy Riverbed Portal in your own Azure Cloud subscription in just few clicks with the Riverbed Community Toolkit provided by the Riverbed Community.
Please have a try and join the Riverbed Community to discuss.
- Hit the "Deploy to Azure" button above
- Fill usual fields:
- Subscription
- Resource Group: create a new, e.g. Riverbed-Portal-Demo
- Region: Select an Azure Region
- Fill the parameters
- Appliance Source Image Blob Uri: uri of the Blob containing the VHD of Portal. The blob name at source must be properly formatred, for example Portal_3.5.0.vhd
- Appliance Size: Size of the Azure VM, Standard_B8ms is a minimum
- Demo Jumpbox Username: Default is riverbed-community
- Demo Jumpbox Password: Set a password with enough complexity (8 characters lengths, 1 or more numeric, 1 or more special characters)
- Hit "Review + create", then hit "Create"
- Wait for the deployment, approximately 15 min
When the deployment is done, grab the the default admin credential from the deployment outputs. They will be required to log on the Portal appliance webconsole.
A simple topology with a Portal VM appliance and a Windows VM will have been created. The Windows VM is a demo jumpbox from which you can connect to the Portal webconsole.
In the Azure Portal, navigate to the resource group. Then find the virtual machine named "Visibility" and connect via the Bastion using the Jumpbox username and password set in the deployment steps.
| Connect from Azure Portal | Open Session |
|---|---|
 |
 |
On the Jumpbox you can launch the web browser, navigate to the Portal webconsole url https://10.100.5.5 and log in with the initial admin credential of the appliance (grabbed earlier from the deployment output).
Tags: Riverbed,Visibility,NPM,Network,Performance,Monitoring,Portal,Dashboard,Unified