VMware Cloud Community
sdhu1st
Contributor
Contributor
Jump to solution

VRNI Without NSX

I keep reading that VRNI can be used without NSX and micro-segmentation. In other words it is a good Day 2 Operational tool for VMWare without NSX. We do not have VMware Log Insight. We use Splunk.

We originally purchased VRNI to aid our migration to NSX and micro-segmentation. These projections have been put on hold for the foreseeable future.

However, the support contract for VRNI now needs renewal. I am looking for some use cases (people are currently using successfully) to create a business case for the $10,000 renewal cost.

Can someone give me some insight on using VRNI in a non-NSX environment?

Thanks 

Reply
0 Kudos
1 Solution

Accepted Solutions
smitmartijn
VMware Employee
VMware Employee
Jump to solution

Hi,

While NSX and vRNI are often paired, vRNI has exactly the same capabilities when you're not using NSX. You can add the physical network devices (you should also do this when using NSX, btw) and vSphere environments to ingest the data and then take advantage of the security visibility (what's talking to what, virtual & physical), networking 2-day ops by having your network topology on hand, checking for any issues there, it'll use the built-in health checks and events that react to configuration and operational (packet loss, devices that have 100% CPU, etc) and you can get notifications from those.

When NSX is added to vRNI, you'll have the same visibility in the NSX topology that you can get into the physical network. The added value here is that the virtual and physical network topologies mesh together and visible in 1 diagram. Without NSX, you still have the physical network visibility and all the other capabilities of vRNI.


Hope that helps,

View solution in original post

Reply
0 Kudos
1 Reply
smitmartijn
VMware Employee
VMware Employee
Jump to solution

Hi,

While NSX and vRNI are often paired, vRNI has exactly the same capabilities when you're not using NSX. You can add the physical network devices (you should also do this when using NSX, btw) and vSphere environments to ingest the data and then take advantage of the security visibility (what's talking to what, virtual & physical), networking 2-day ops by having your network topology on hand, checking for any issues there, it'll use the built-in health checks and events that react to configuration and operational (packet loss, devices that have 100% CPU, etc) and you can get notifications from those.

When NSX is added to vRNI, you'll have the same visibility in the NSX topology that you can get into the physical network. The added value here is that the virtual and physical network topologies mesh together and visible in 1 diagram. Without NSX, you still have the physical network visibility and all the other capabilities of vRNI.


Hope that helps,

Reply
0 Kudos