Vmware vrealize network insight установка и настройка
In a nutshell, vRealize Network Insight delivers intelligent operations for software-defined networking and security. It enables customers to build an optimised, highly-available, and secure network infrastructure across multi-cloud environments. It accelerates micro-segmentation planning and deployment, enables visibility across virtual and physical networks, and provides operational views to manage and scale the VMware NSX deployments.
Welcome to the first in a five-part series which sees us cover everything from the installation of vRNI, to how we can manually implement micro-segmentation by using the NSX-T Distributed Firewall following an analysis of vRNI’s collected data flows. I recommend following each article in the series, as each one sets up the next. If you’d prefer to jump to a specific article, simply use the below links.
What can VMware vRealize Network Insight do?
When deploying your software-defined infrastructure and planning out your micro-segmentation strategy, vRealize Network Insight helps to take the guesswork out of how your network flows actually happen. You no longer have to guess what network flows happen for a particular application.
It can also provide visibility for your virtual and physical networks. Overall, it helps to manage, troubleshoot, and secure your network.
Features of vRNI include the follwoing:
- Ability to plan micro-segmentation
- Troubleshoot security on-premises, in the cloud, or in hybrid deployments
- Minimize risk
- Reduce mean time to resolution (MTR) for connectivity issues
- Eliminate network bottlenecks
- Scale across NSX managers
- Ensure compliance
VMware vRealize Network Insight Install Guide
VMware vRealize Network Insight is installed in two parts. These include the following:
- Installing the vRNI platform appliance
- Installing the vRNI collector appliance/proxy
Both components are deployed using the very familiar OVF/OVA deployment process in the vSphere Client. During the process of standing up the platform appliance, you will generate a secret key that will be used in the deployment of the collector VM.
I am not going to show each screenshot of the OVA deployement here as it is standard, however, just showing a few of the highlights and screens to note. Here we are choosing the OVA for the Platform appliance solution.
Beginning the deployment of the vRNI 5.2 platform appliance
Make note of the size of appliance you would like to deploy. A note here is the vRNI solution is not a lightweight pair of VMs. The Platform appliance, even in the Medium configuration, requires 8 vCPUs and 32GB of memory. The collector requires 4 vCPUs and 12GB of memory.
Select the configuration size for the Platform appliance
The deployment displays the note that you will need to manually configure the appliance after it is deployed.
Customize template for the vRealize Network Insight Platform appliance
The first part of the configuration of both the Platform and Collector appliances is that you will need to open a console session and run a setup wizard to get some basic configuration on the solution. This includes:
- Setting up user accounts
- Network configuration
- Web proxy configuration
You login with consoleuser and the password of console.
Logging into the console and performing steps 1 and 2 of the setup process
Running steps 3 & 4.
Configuring steps 3 and 4 of the setup process with vRNI 5.2
After a few minutes, you should see the Appliance configured successfully message displayed.
Platform appliance is configured successfully
Now, we move on to the browser portion of the configuration. Open your browser and point to the IP you configured during the setup wizard. You will first enter a license key and validate the license.
Enter your vRealize Network Insight license key and validate
Next, generate a shared secret key for the collector VM.
Generate a shared secret for the collector VM
Secret key is generated. Click the Copy button to copy it to the clipboard. You will leave your browser session open as you deploy the collector VM.
Copy the generated shared secret to use during the deployment of the collector appliance
Full vRNI Series
There are two main flavours of vRNI – an on-premises installation or VMware’s SaaS offering, Network Insight Cloud. The latter comes with all the benefits of a cloud-based solution (namely managed updates, integration with the suite of VMware Cloud products, etc.); however, the two flavours have the same functionally.
This article focuses on the on-premises flavour and, specifically, version 5.3.0 (released 2020-07-14).
NSX Controllers
Configuration of the NSX Controllers is a little different as configuration is via REST API only. First of all, we need to identify our NSX Controller IDs in readiness for the configuration.
1. Identify Controller IDs by browsing to Networking & Security > Installation and Upgrade > Management. The Controller IDs can be identified under the Controller Node column (in the below example, these are controller-16, controller-17, and controller-19).
2. Via your REST client of choice (I’m using the Chrome-based Postman extension), the below payload will need to be sent to each of your NSX Controllers.
POST
CUSTOM HEADERS
REQUEST BODY
3. Confirm the new configuration by a final GET request.
GET
In conclusion, and as a result of adding both vSphere and NSX elements to Log Insight, you are now blessed with some very powerful data when it comes to either troubleshooting or environment tuning. Furthermore, if you utilise any other VMware products then please do take a look to see if a corresponding Content Pack exists, however, do keep in mind the 25 OSI.
Installing vRealize Network Insight 4.0 Platform and Proxy Appliances
As we briefly touched on the installation overview post, there are several components to the installation of vRealize Network Insight 4.0. They include the following in this order:
- Deploy the Platform Appliance
- Perform the console configuration of the Platform Appliance
- Connect to the web interface of the Platform appliance after the console configuration, provision a shared secret key.
- Deploy the Proxy Appliance including entering the shared secret key that was generated in the web interface of the Platform appliance.
- Perform the console configuration of the Proxy Appliance
- Finish out the web configuration on the Platform Appliance, once the Proxy Appliance is detected
Wrapping Up
There you have it – VMware vRealize Network Insight Install Guide using vRealize Network Insight 5.2 as a guide for the walk through. The vRNI platform is easily configured with just a bit of time and quickly leads to time to value for your NSX environment.
Stay tuned for more vRNI goodness as I delve deeper into the solution and look at traffic flows, micro-segmentation, security, etc.
The installation of the vRealize Network Insight 4.0 Platform is fairly straightforward and involves provisioning and configuring two appliances in the environment that allow collecting and analyzing the network information via traffic flows that are collected and analyzed. In this post, I will step through the steps to get the two appliances up and running to start collecting information on traffic flows from an NSX-V environment that I have running in the lab environment. Let’s take a look at Installing vRealize Network Insight 4.0 Platform and Proxy appliances.
Configuration:
Login Page
Once you are logged in, by default you will be in “NSX Assessment Mode”, you can continue on that mode or change to “Full Product Evaluation” mode.
Change or accept the current mode
If you click on the change mode button (small green button at the bottom right corner of the page) you will be shown the details of the environment. Ideally it should be filled with data but since till now I did not configure any data sources so it is all blank.
Full Evaluation Mode
Let’s go back and add data source. The first data source to be added is vCenter sever.
Add Data source
Clicking on the link takes you to the addition of Data Sources Page. Go to the page and click on “Add new source”.
First you need to select a source type.
Select Source
The first source available is VMware vCenter Server (before anything else is added).
VMware vCenter as source type
Provide details of the vCenter.
I love the way the button changes color with and without the details. After you provide the details you need to click on Validate to validate the details.
Validation of details
Once the details are validated, all the available VDS are listed and you have the option to enable NetFlow on the vCenter. If you want to enable it, select the required options and click on Submit.
Configuring NetFlow
Now you are done with first data source configuration.
Configured Data Source
Since we have configured the first source, let us see what other options are available. The first thing that I do is integrate the solution with Active Directory so that I can easily configure role based access control. So let’s start this configuration by Clicking on “Active Directory Integration” on the left hand side and select the option to enable it.
Enabling AD
In the details page provide the details of the AD and click on Save button to save the information.
Details of AD
AD is configured. You can add the user later. Next task should be to change the default password. For that, click on “My Profile” and change the password.
You can check the Infrastructure state from the left side menu option.
Check status
Since we have done basic house keeping so let’s add NSX as another data source. We will again visit the “Data Source” button.
Add Second Data Source
Now if you click on “Select Source Type” list you will see a lot more option. Choose NSX Manager from the list.
NSX as Data Source
Next provide the details of the NSX Manager and Validate.
Provide details of NSX
For my environment I will “Enable NSX Controller”.
Enable NSX Controller
Sources configured
You can configure the system notifications by clicking to the respective button.
System Notification
Recommendations to Support High Availability
You can customize vSphere HA options to enable vSphere high availability.
- Host Failure – Restart VMs
- Host Isolation– Disabled
- Guest not heartbeating– Disabled
Deploying the vRealize Network Insight Collector Appliance
Now that the Platform appliance is deployed, it waits on the Collector/Proxy VM to come online. Below, we are beginning the process to deploy the Collector VM. Note the size requirements.
Viewing the configuration size of the Collector VM
Paste in the Shared Secret for Proxy that you copied from the web interface of the Platform appliance.
Paste in the shared secret key you generated on the web configuration of the Platform appliance
You follow the same process here for the Collector. Open a console session and run the setup wizard. You will configure the same values here including accounts, network, NTP, proxy, and it will automatically configure the connection to the Platform appliance.
Beginning the console configuration of the Collector VM
Shared secret configuration working…
Finishing the console configuration of the Collector VM
The connection is successfully made to the Platform appliance. You should see the Appliance configured successfully displayed in the console.
VMware vRealize Network Insight Collector VM appliance configured successfully
Going back to the web interface of the platform appliance, you should see the Proxy Detected Click Finish. Click Finish.
Proxy detected finish the configuration from the Platform appliance web interface
Login to the web interface of the platform appliance. Here, I am setting up a connection to a vCenter Server integrated with an NSX-T environment.
Select an account to add to vRNI
Under the Accounts and Data Sources menu, you will populate the credentials for your connection to vCenter as well as setup NetFlow, VDS and then submit the configuration.
Validate the vCenter connection netflow and VDS before submitting
Finish the configuration
Other Requirements and Considerations
- The maximum time skew between the platform nodes has to be lesser than 30 seconds.
- The availability of the NTP service is critical to system operations. Ensure that you do not reboot the platform node or the collector node when the NTP service is not available.
- When the existing compute resources are completely used by the other processes on the platform, vRealize Network Insight crashes and does not recover automatically. If the services fail to recover, reboot the platform node.
- If the network latency between platform node and upgrade server is greater than 500ms, the vRealize Network Insight upgrade might encounter an error. So, the network latency must be less than 500ms.
- The recommended disk latency for optimal performance is up to 5ms. If the disk latency is greater than 5ms, the system performance degrades.
- The recommended disk IOPS is 7500.
Platform Appliance Deployment
1. From vSphere, deploy a new OVF Template and browse to the Platform OVA file you downloaded earlier. Progress through the usual deployment requirements – assign the VM to a suitable VM Folder, select an appropriate compute resource, accept EULA, deployment configuration, storage, network, etc.
2. Once the appliance has successfully deployed, power-on and open a console window. When prompted, log in using the default Network Insight credentials – Username: consoleuser, Password: console.
3. When prompted, create passwords for the support and consoleuser users.
4. Enter the appliance’s IP address, subnet mask, default gateway, DNS, and domain accordingly.
5. Enter your NTP server information.
6. If appropriate, enter your web-proxy details.
7. NTP will now sync and, once complete, will finalise the last of the configuration steps.
8. Once the appliance reports that it has been successfully configuration, open a web browser and browse to the appropriate FQDN/IP address of the appliance. When prompted, provide the license key and click Activate.
9. You will now be presented with a Collecter VM Shared Secret. This will be required when deploying the Collecter (Proxy) appliance in the next set of steps. Keep this screen running while we look at deploying the Collecter appliance.
This concludes the deployment of the Platform VM.
NSX Manager
First up, NSX Manager. Nice and easy, and configurable via a few simple steps.
1. Login to NSX Manager.
2. Click Manager Appliance Settings.
3. Under the Syslog Server section, click Edit.
4. Enter the FQDN/IP Address of your vRealize Log Insight server, Port (default 514), and Protocol (UDP). When complete, click OK.
NSX Distributed Logical Router & Edge Services Gateway
As above, another simple process for each of your DLRs and ESGs.
1. Browse to Networking & Security > NSX Edges and double-click into each of the Edges you wish to monitor. Remember, a 25 OSI limit is included with this basic license, therefore, if you have a high number of edges, which ones you choose to monitor will be down to you.
2. Browse to Manage > Settings > Configuration and, under the Details section, click Change next to the Syslog Servers.
3. Enter the FQDN/IP Address of your vRealize Log Insight server, and select the protocol. When complete, click OK.
…Back to the Platform Appliance User Interface
1. As the Proxy/Collector appliance is now visible, click Finish.
2. Finally, login utilising the admin@local credentials defined during deployment.
This concludes the deployment of the VMware vRealize Network Insight Platform and Proxy/Collector appliances.
Conclusion:
This is an awesome tool to monitor your network environment. I am pretty impressed with the capabilities. In my opinion if you have NSX in your environment then this is a must have tool in your kitty. Go ahead and explore the option. For more details visit VMware site for more information. For detailed documentation, check this link.
If you have a VMware NSX-powered softwared-defined networking infrastructure, you have an incredibly capable platform for delivering next generation networking for your environment. However, understanding how your traffic flows, having vsibiility to the ins and outs of your now “abstracted” networking layer can be difficult without the right tools. VMware vRealize Network Insight is the premeire tool for managing your software-defined networks and security policies. In this post, we will take a look at VMware vRealize Network Insight install guide to see how to get the solution off the ground in your environment.
Content Pack Installation – VMware NSX-vSphere
1. Browse to Settings > Content Packs > Content Pack Marketplace > Marketplace.
2. From the grid of Content Packs, select VMware – NSX-vSphere.
2. When presented with the Install Content Pack window, review the information and, when ready, click Install.
3. Review the Setup Instructions and click OK.
As far as the installation goes, that’s it. vRealize Log Insight is now ready to receive Syslog data from VMware NSX. To that end, we now need to configure all elements of NSX to forward this Syslog data.
In Summary
In this article, we performed a simple deployment of the on-premises vRNI Platform and Proxy/Collector appliances.
In Part 2 (VMware vRealize Network Insight (vRNI) – Part 2 – Configuration) we will add our vCenter Server(s) and NSX-T Managers as data sources before, in Part 3 (VMware vRealize Network Insight (vRNI) – Part 3 – Identity & Access Management via LDAP), configuring identity and access management via LDAP to enable users to login with domain credentials.
vRealize Network Insight ( vRNI ) is the newest addition to the range of products from VMware. vRealize Network Insight (vRNI) is a product for delivering intelligent operations for your software defined network environment (specially NSX). In short, it does what vRealize Operations does for your virtualized environment, but only to the SDN environment. With the help of this product you can optimize network performance and availability with visibility and analytics across virtual and physical networks. Provide planning and recommendations for implementing micro-segmentation security, plus operational views to quickly and confidently manage and scale VMware NSX deployment.
It is a very exciting product and I thought of taking it for a spin in my lab. Provided below is a detailed installation and configuration guide for this product. So if you are a VMware professional and looking to deploy this in your environment or you want to do a PoC then this blog is for you.
With the introduction out of the way, let’s start the main topic.vRealize Network Insight is currently in version 3.0 and in this blog I am covering this version. This product comes with the following two OVA files.
- VMware_vRealize_Network_Insight_3.0.0-1469457715_platform.ova
- VMware_vRealize_Network_Insight_3.0.0-1469457715_proxy.ova
The platform.ova is the main appliance and the other one is the proxy appliance. Go ahead and download the appliances from download link.
To keep the length of the post to a reasonable length I have omitted the OVA deployment steps except the final network information input screens.
vRealize Network Insight 5.2 Installation Requirements
Below are the documented requirements for installing vRealize Network Insight 5.2.
Platform brick requirements
Brick Size | Cores requiredfor 2.1 GHz CPU | Cores requiredfor 2.3 GHz CPU | Cores requiredfor 2.6 GHz CPU | RAM | Disk |
---|---|---|---|---|---|
Medium | 10 | 9 | 8 | 32 GB | 1 TB |
Large | 15 | 14 | 12 | 48 GB | 1 TB |
Extra Large | 20 | 18 | 16 | 64 GB | 2 TB |
Collector brick requirements
Brick Size | Cores required for 2.1 GHz CPU | Cores required for 2.3 GHz CPU | Cores required for 2.6 GHz CPU | RAM | Disk |
---|---|---|---|---|---|
Medium | 5 | 5 | 4 | 12 GB | 200 GB |
Large | 10 | 9 | 8 | 16 GB | 200 GB |
Extra Large | 10 | 9 | 8 | 24 GB | 200 GB |
Final Thoughts
As shown in detail, Installing vRealize Network Insight 4.0 Platform and Proxy appliances is for the most part a standard installation of OVA appliances, configuration using the console, and to generating the shared secret key on the platform appliance and configure this during the proxy appliance installation. The VMware vRNI 4.0 platform has powerful features that allow visibility into both on-premises and hybrid cloud environments. Stay tuned for further vRNI 4.0 posts.
In Part 1 of this series we covered the simple installation and configuration of VMware vRealize Log Insight. In Part 2 we will cover how we can further configure and customise Log Insight via Content Packs in order to leverage further logging capabilities.
As mentioned in Part 1, one of the caveats of utilising this ‘free’ version of Log Insight (or more aptly, the 25 OSI license available to all vCenter Server licensees), is the ability to use VMware-only Content Packs. This is far from a bad thing and, as a result, enables us to integrate with other VMware products including NSX, Horizon, SRM, etc. In this article we will focus on the former product.
Similarly to my previous post where I configured all ESXi hosts to forward Syslog data to a our new Log Insight server via the Syslog.global.logHost attribute, the below steps will detail how to configure the NSX Manager, all NSX Controllers, as well as Distributed Logical Routers and Edge Service Gateways to do the same. For the most part, this is done simply via UI (DLRs, ESGs, and NSX Manager), however, configuration of the NSX Controllers is via REST API only. More on the latter item later.
Prerequisites
Firstly, you’ll need to download the OVA files required to get this solution up and running. Visit your My VMware account and download both the Platform and Proxy (Collector) OVA files as shown in the below screenshot.
First of all, we’ll need to deploy the Platform appliance. This is the brains of the operation, and where all that nice data you collect will be stored. The Platform appliance also provides the analytics, user interface and data management for Network Insight.
The other component is the Proxy VM (aka – Collector appliance) which is used to connect to the various data sources supported by Network Insight – vCenter Server, NSX, as well as physical network devices.
The hardware requirements of the various ‘brick’ sizes for a single platform and a single Proxy/Collector appliance are as follows:
Brick Size | Cores required for 2.1 GHz CPU | Cores required for 2.3 GHz CPU | Cores required for 2.6 GHz CPU | RAM | Disk |
---|---|---|---|---|---|
Medium | 10 | 9 | 8 | 32 GB | 1 TB |
Large | 15 | 14 | 12 | 48 GB | 1 TB |
Extra Large | 20 | 18 | 16 | 64 GB | 2 TB |
Note, the reservation for the CPU speed and RAM for each node must be 100% of the value specified above.
Monitoring environment:
Since everything is configured, let’s check the information. Next few screenshots show how to see the details of a single ESXi host.
Select host from left side option Click on select host Select the host for which you want to see the details Submit the request. You can modify the time frame for which you want to see the details All the statistics
Similarly, I chose to see the details of the NSX manager.
NSX Details 1 Scrolled down view for more information
vRealize Network Insight 4.0 Platform Appliance Installation
The first step in getting the vRealize Network Insight 4.0 Platform installation up and running is to download the OVA appliance file. The size and details of the installation that I have downloaded the following file version for vRNI below:
- vRNI Platform OVA – VMware-vRealize-Network-Insight-4.0.0.1545292702-platform.ova (at time of writing) (size 6.2 GB)
Choose the platform OVA appliance file downloaded from VMware.
Choose the vRealize Network Insight 4.0 platform OVA file for deployment
Name the platform appliance as you want it to appear in vSphere inventory.
Name your vRealize Network Insight 4.0 platform virtual machine
Choose the compute resource that will house the appliance.
Choose the compute resource for the vRealize Network Insight 4.0 platform appliance
Review the vRealize Network Insight 4.0 platform OVA template details
Accept the EULA for the appliance installation.
Accept the EULA agreement for vRNI 4.0 platform appliance
As you will notice there is no Small configuration. There is only Medium, Large, and Extra Large. The requirements for the platform appliance in any of the configurations is not insignificant. Even in the Medium configuration, it requires 32 GB of memory and 8 vCPUs.
Configure the deployment size of the installation for vRealize Network Insight 4.0 platform appliance
Choose a storage location for the platform appliance.
Select storage for provisioning the vRealize Network Insight 4.0 platform appliance
Choose the vSwitch you want to connect the appliance to.
Select the network to connect the vRNI 4.0 appliance to
Customize the vRNI 4.0 template
Ready to deploy the appliance.
Ready to deploy the vRNI 4.0 OVA appliance
After deploying the Platform appliance, you will need to connect to the console of the Platform appliance VM and login to the appliance using the consoleuser and password for the user that is displayed on the console. The default login credentials as defined in the VMware KB here are as follows.
vAdmin UI | [email protected] | Set this password in Activate License screen during installation |
SSH User | support | ark1nc0113ct0r |
CLI User | consoleuser | ark1nc0ns0l3 |
Login to the console session of the vRNI 4.0 platform appliance to complete configuration
You will begin a five step process that has you configure passwords, setup the network, NTP settings, web proxy, etc.
Configure the vRealize Network Insight 4.0 passwords for the platform appliance
Configuring the network settings.
vRNI 4.0 network configuration and setup
NTP server configuration.
NTP configuration on the vRealize Network Insight 4.0 platform appliance
Web Proxy configuration if needed.
Configure vRNI 4.0 web proxy information if needed
Opting in or out of sending data to VMware.
Opt in or out of sending telemetry data to VMware for the appliance
Console configuration is completed successfully. You are now ready to connect to the web interface of the Platform appliance using the configured IP address.
The console configuration of the vRNI 4.0 platform appliance completes successfully
First things first, you need to enter the license key to be used with your vRNI 4.0 installation.
Connect to the web interface of the vRNI 4.0 platform appliance and enter license key
Once you have entered a license key and activated, you will move on to the Add Collector & Finish section of the web configuration on the platform appliance. You will see a button to generate a shared secret key and then as you see below, you can copy this key into the clipboard to be used with the proxy appliance deployment process.
Generate and copy the shared secret key for the vRealize Network Insight Proxy appliance
Now that you have generated the shared secret key for the proxy appliance, copy the key and leave the web interface for the Platform appliance open. You now need to deploy the Proxy appliance using the shared secret that was generated.
Supported Web Browser
-
: The latest two versions.
- Mozilla Firefox: The latest two versions.
Collector (Proxy) Deployment
1. From vSphere, deploy a new OVF Template and browse to the Proxy OVA file you downloaded earlier. Progress through the usual deployment requirements.
IMPORTANT – When prompted to enter a shared secret, copy the Shared Secret from Step 9 above and paste into the Shared Secret for Proxy field.
Once complete, click Next.
2. Once the Proxy/Collector appliance has successfully deployed, power-on, and open a console window. When prompted, log in using the displayed credentials, and run through the same configuration as the Platform appliance.
3. Once complete, the Proxy appliance will begin processing the Shared Secret provided earlier. Grab a coffee and monitor both consoles until the Platform appliance detects the Proxy/Collector.
Shared Secret – Completed Successfully.
vRealize Network Insight 4.0 Proxy Appliance Installation
The vRealize Network Insight 4.0 Proxy appliance installation is in the same manner as the Platform appliance via the normal OVA deployment process. The file downloaded from VMware for the proxy appliance has the following details:
- vRNI Proxy OVA – VMware-vRealize-Network-Insight-4.0.0.1545292702-proxy.ova (at time of writing) (size 5.1 GB)
Choose the Proxy appliance OVA in the deployment wizard.
Choose a name for the virtual machine as it will appear in vSphere inventory.
Choose the vRNI 4.0 proxy appliance virtual machine name for inventory
Choosing the compute resource for the proxy appliance.
Choose the compute resource
Review the template details for vRNI 4.0 proxy appliance
Accept the EULA.
Accept the EULA for the vRNI 4.0 proxy appliance
Choose the deployment size configuration. While the resource requirements of the proxy appliance are not as demanding as the platform appliance, again they are not trivial.
Set the configuration size for the vRNI proxy appliance
Choose the storage location for the vRNI proxy appliance.
Choose storage location for the vRNI 4.0 proxy appliance deployment
Select the network configuration for the proxy appliance.
Configure the network for the vRNI 4.0 proxy appliance
On step 9 which is the Customize template step on the proxy appliance deployment process, you will see the field for Shared Secret for Proxy. Here is where you paste in the shared secret key you have in the clipboard from the web configuration on the platform appliance.
Customize the template for the vRealize Network Insight 4.0 proxy appliance enter shared key
Once the key has been entered, click Next.
After entering the shared secret key that was generated in the vRNI 4.0 Platform appliance
Finalize the deployment of the proxy appliance.
Ready to complete the vRNI 4.0 proxy appliance OVA deployment
As was needed with the platform appliance, you need to finish the configuration of the Proxy appliance once the appliance is deployed by means of the console. As you can see on the Step 4/6, the shared secret will be processed and finalized.
Running the same console configuration as with Platform controller shared secret processes
Also, at this point, if you flip back to the web configuration on the platform appliance, you will see the status at the bottom of the web screen change to Proxy Detected! Click Finish.
VMware vRNI 4.0 proxy detected and configuration ready to complete
At this point, once you click Finish, the vRNI installation is completed. There is, however, the need for additional configuration that we will cover in a future post involving setting up the connection to a vCenter Server.
Installation:
Provided below is the screenshot of the screen where you need to provide the details like IP, DNS, NTP etc.
Network details input
Advance setting for network
Accepting certificate warning
Next comes the license page. You need to provide the license key and validate it. So let me put the license key there and Validate.
License validation page
Once validated, it shows the details of the license and asks for Activation. Click on Activate button to activate the license.
Validated details of license and Activation Page
Next page is for generating the secret for the proxy VM. Click on Generate button to generate the Secret.
Secret generation page
Once the secret is generated we have the Copy button to copy the secret.
Secret generation and copying stage
Next, this setup will wait for the deployment of Proxy VM. It will keep looking for it till the time proxy VM is deployed. So let’s go ahead and deploy the Proxy VM. The deployment is similar to any OVA deployment. One difference is, in this case you need to provide the above generated secret at the deployment stage of the OVA.
Secret providing at the OVA deployment of Proxy VM
Next two screenshots are for the details that needed to be provided at the time of OVA deployment. It is similar to the ones provided at the time of platform OVA deployment (screenshots are provided here for reference).
Details page 1 Details page 2
Once the deployment is done and the Proxy VM is up and running, it is automatically sensed in the main configuration page.
Auto Sensing of the presence of Proxy VM
Click on Finish button to finish off the installation. Congratulations . your have done a successful installation of vRealize Network Insight environment.
Since the installation is done, let’s configure the environment.
Читайте также: