NetMRI have the same discovery engines so when device support is added to the engine, both NI and NetMRI support it. There are two main differences: 1) NI runs as a NIOS grid member and is controlled right in the NIOS UI. So NI is primarily used to discover and synchronize with NIOS IPAM and add meta data on the discovered devices and end points (i.e. model, OS, what's attached where, and when it is on the network). You cannot use NI without NIOS. NetMRI runs as a separate appliance so not a part of the Grid and can be deployed standalone without NIOS. Although there is a connector between NetMRI and NIOS so you have the option of syncing with IPAM from NetMRI also. 2) NetMRI supports a superset of use cases from NI. Where both products support Discovery, IPAM Sync, and Switch Port Management. Only NetMRI supports network configuraiton change management, change automation, configuration compliance, and network analysis.
Dave
@DaveSignori
8801 
1
