At times, going through the complete Installation document might become a very time-taking task, hence in this blog, I am trying to provide a gist of installation steps
vRNI installation consists of the installation of 2 different types of Appliances – Platform & Proxy. These are deployed as VMs using OVAs.
These appliances come with 2 brick sizes Medium & Large, depending on the size (mainly number of VMs & Flows) of your environment, you can select an appropriate brick size.
Deployment Steps Overview
- Deploy Platform OVA (Import in vCenter Server)
Make sure to change the Virtual Disk Format to “Thin Provisioning“. Once the OVA is deployed, power on the VM and you would see credentials for “consoleuser” to login. Login using the credentials provided, & type “setup” & hit enter. Here you would configure the IP Address for the Platform VM, etc. Make sure the IP Address you provide for NTP is correct, else configuration would fail
- Open https://<Platform IP Address> & activate license | You would see here Proxy not yet detected
- Generate Shared Secret Key
- Deploy Proxy OVA (during the deployment wizard, you will get an option to enter the shared secret key)
- Setup Proxy OVA, the same way we set up Platform VM. You would see Proxy/Collector detected.
- Login to vRNI using Platform VM’s IP and add Data Sources which you want to have Network Data collected from (like vCenter Server, NSX Manager, etc).
You might get to the same license page, hence clear cache and then try to launch the webpage again, or else, open browser in incognito mode & try to log in.
If you are using firstname.lastname@example.org (to add vCenter Server) & admin (to add NSX Manager) credentials, you don’t need to worry about privileges, however, in Production Environment, you would have different IDs to use. In that case, please refer to this link which talks about privileges required.