T.N. National Guard Uses NetMRI
"With NetMRI...we save a lot of time by not having to sit down and manually search where problem areas may be. It doesn't necessarily have to be routing issues. It can be things like IP phone issues or audio service. The tool gives us a generalized area...to start looking instead of just arbitrarily...hopping through."
—Master Sgt. Earl Salazar, Network Engineer
More CustomersConnect With Us
NetMRI System Requirements
Take the Next Step:
| License Size | Recommended Configuration | ||||
| Devices | Interfaces | VMWare HyperVisor* | Process Cores** | Memory | Local Disk Storage*** |
| 25 | 500 | ESX 4.0 | (1) 2.4GHz | 1GB | 20GB |
| 50 | 1,000 | ESX 4.0 | (1) 2.4GHz | 1GB | 40GB |
| 200 | 10,000 | ESX 4.0 | (2) 2.4GHz | 2GB | 100GB |
| 600 | 30,000 | ESX 4.0 | (4) 2.4GHz | 4GB | 250GB |
| 1,200 | 60,000 | ESX 4.0 | (4) 2.4GHz | 4GB | 500GB |
| 2,000 | 100,000 | ESX 4.0 | (8) 2.4GHz | 6GB | 750GB |
| 3,000 | 150,000 | ESX 4.0 | (8) 2.4GHz | 7GB | 1,200GB |
* It is strongly recommended that a customer not use anything but VMNware ESX in production. Other VMWare HyperVisor choices in order of preference are: ESX 4.0 (most preferred), ESX 3.5, Server 2, Workstation 6.5 (least preferred).
** Performance can be impaired with other applications running on the same VM server as NetMRI, especially if the number of processor cores assigned to NetMRI is greater than half of the total processor cores on the VM server.
*** Disk performance is a critical factor for performance. The more spindles dedicated to NetMRI, the better. In particular, low Average Seek Times of 4 milliseconds or better will produce the best results. This is typically obtained by high disk spindle speeds (15,000 RPM) and dedicated spindles, perhaps achieved with specialized RAID configurations. Sharing Spindles and/or LUNs between NetMRI and other applications is likely to compromise performance and is strongly discouraged.