What are the resource requirements for vRealize Network Insight?

Refer to the vRealize Network Insight Installation Guide for Resource Requirements.

What happens if I enter the incorrect key during vRealize Network Insight Proxy OVA Deployment?

The secret key is not validated during vRealize Network Insight Proxy OVA deployment. The deployment completes even with incorrect secret key. However, pairing can fail and vRealize Network Insight Proxy does not show up as detected on vRealize Network Insight UI.

To correct the shared secret, log in to vRealize Network Insight Proxy CLI and run the set-proxy-shared-secret command to set the correct secret key. This command replaces the old key with the new one, and therefore, vRealize Network Insight Platform detects vRealize Network Insight Proxy and pairs up.

How do I configure DNS after vRealize Network Insight Proxy OVA is deployed?

Log in to vRealize Network Insight Proxy CLI, and run setup command. This interactive command will provide the user an option to add or modify DNS after which the vRealize Network Insight Proxy will be reconfigured with the new DNS.

How do I find out vRealize Network Insight Proxy VM IP from the UI?

Go to Settings page and select vRealize Network Insight Infrastructure menu option. The IP address of both, vRealize Network Insight Platform and vRealize Network Insight Proxy VMs is displayed.

What should I do if vRealize Network Insight Proxy is not detected in 5 minutes after deploying vRealize Network Insight Proxy OVA?

Log in to vRealize Network Insight Proxy using consoleuser (refer to the vRealize Network Insight Command-Line Reference Guide) and verify the following:

  • Verify vRealize Network Insight Platform pairing status with vRealize Network Insight Proxy using the CLI show-connectivity-status .

  • If the pairing stating is shown Passed, open the Platform UI in a new browser window and login to check status.

  • If the pairing status is showing Failed, then the shared secret key specified during the vRealize Network Insight Proxy OVA deployment could be wrong. To fix this problem, use the set-proxy-shared-secret command to set the correct secret key. This command replaces the old key with the new one, and therefore, vRealize Network Insight Platform can detect vRealize Network Insight Proxy.

  • If the show-connectivity-status shows network reachability to vRealize Network Insight Platform as Failed, then verify whether vRealize Network Insight Platform is reachable from vRealize Network Insight Proxy VM using the ping command.

  • If it is not reachable, then verify if NTP, DNS, gateway, and other network parameters are configured correctly using show-config command.

  • If any of the network parameters is not configured correctly, use the setup command to modify the network configuration parameters.

What should I do if I forget my login credentials?

If you are the UI local user: Contact vRealize Network Insight UI administrator to reset the credentials for you.

If you are the administrator: From vRealize Network Insight 3.4, the UI credentials can be changed by using CLI modify-password. Refer the CLI guide for details. If you are working on vRealize Network Insight versions previous to 3.4, contact support.

How do I change the login password?

To change the login password:

  1. Go to Administrator > Settings, and then click My Profile on the left pane.

  2. On the Change Password page, fill in the required information and click Save.

What do I do if I get the login screen before detecting the vRealize Network Insight Proxy VM?

  • This behavior is expected when the browser is refreshed or URL is opened in a new window before detecting the proxy.

  • Log in by using the credentials set during license activation for the admin@local username.

Does vRealize Network Insight support multiple vCenter Server/NSX Manager?

Yes, vRealize Network Insight supports multiple vCenter Servers and NSX Manager.

Which services of vRealize Network Insight need Internet access and why?

vRealize Network Insight supports remote home calling feature that requires Internet access. This feature or services allow the vRealize Network Insight team to gain a better understanding of customer environments and proactively troubleshoot or repair issues. The following services need Internet access:

  1. Upgrade Service (svc.ni.vmware.com:443): vRealize Network Insight uses this service to contact the remote upgrade host and pull in newly released bits as they become available. Certain metrics related to key services and performance of vRealize Network Insight are periodically gathered and uploaded using upgrade host for the vRealize Network Insight Support team to monitor and identify any anomaly in the environment so that they can act before it impacts critical services.

  2. Metric service (svc.ni.vmware.com:443): Certain metrics related to key services and performance of vRealize Network Insight are periodically gathered and uploaded for the vRealize Network Insight Support team to monitor and identify any anomaly in the environment so that they can act before it impacts critical services. It can be enabled/disabled while deploying the vApp or through "telemetry" CLI later.

  3. Support Service (support2.ni.vmware.com:443): This service establishes remote secured tunnels to the vRealize Network Insight support host that allow authorized personnel to remotely access and work on deployments. It is disabled by default and can be enabled/disabled through UI as well as "support-tunnel" CLI.

  4. Registration Service (reg.ni.vmware.com:443): For registering the appliance with all external services. It will enable trusted communication between above mentioned services. When setup has access to internet, registration happens automatically. In an isolated environment it can be done using "offline-registration" CLI (Please refer to CLI guide for more details). It is required for enabling Support Tunnel.

Note:

If the vRealize Network Insight platform is behind an Internet proxy, whitelist the following domain names and ports:

Table 1.

Service

URL

Port

Upgrade Service/Metric Service

svc.ni.vmware.com

443

Support Tunnel Service

support2.ni.vmware.com

443

Registration Service

reg.ni.vmware.com

443

Log Service

log.ni.vmware.com

443

How do I change the IP Address/Gateway/Netmask after vRealize Network Insight OVA is deployed?

To change vRealize Network Insight Platform/Proxy network settings, log in to CLI and run the setup command. This interactive command will provide the user an option to modify the IP address, gateway, netmask, and so forth after which the vRealize Network Insight appliance is reconfigured with new details.

Note:
  • VM reboot is required when Gateway IP subnet is changed. It can be done using the appliance-reboot now CLI.

  • If vRNI Platform IP is modified and it is paired with proxies then on each proxy VM run this CLI command:

    vrni-proxy set-platform --ip-or-fqdn <New_Platform_IP>

How do I change from an Evaluation License to a Perpetual License?

Refer to the Change License section in the vRealize Network Insight User Guide.

How are licenses characterized in vRealize Network Insight?

Table 2.

License Name

License Type

Features

Enterprise

Full/Production: It can be perpetual or time bound.

The following features are enabled:

  • AWS as data provider

  • Tunable data retention policies

Advanced

Full/Production: It can be perpetual or time bound.

Existing customer licenses will be translated to this new model in following manner post upgrade:

Advanced Full/Production

Note:

ALL licenses are capacitated per CPU socket and CCU (Concurrent Users). The evaluation licenses can be renewed or converted to Production with the updated key through UI -> Settings ->About. Refer to the user guide for more details.