...
A virtual machine version of NetMRI installed on a VMware ESX server or OpenStackin a virtual infrastructure platform. You can use NetMRI VMs as collectors and as an Operations Center. When deployed on a virtual machine, NetMRI demands a lot of performance resources that A NetMRI VM performance should be sufficient to handle a required number of devices. For more information on how to ensure this, see Benchmarking of NetMRI Virtual Appliancesfor the Operations Center.
...
Note: In the Operations Center context, when an appliance acts as the Operations Center it uses only a single port, which is the MGMT port for the NT-1400, NT-2200 or NT-4000. Collectors may use multiple interfaces for network discovery and management, including 802.1q virtual scan interfaces. Typically, both the LAN1 and LAN2 ports are used in this manner on each Collector appliance. For more information, see Configuring Network Interfaces for Operations Center.
...
Infoblox NetMRI appliances should always be supported by an uninterruptible power supply (UPS) to avoid data corruption problems in cases of power outage.
| Anchor |
|---|
...
Initial connections to the NetMRI Administrative Shell using an SSH command line client to the IP address of the MGMT port require a username as one of the command line parameters, as shown in this example:
ssh –l admin <system>
where <system> is the hostname or IP address assigned to NetMRI. At that point, you are prompted for the admin account password, which is the same as that used for the browser interface.
...
When you set up and deploy an Operations Center and its associated collectors, follow some best-practices guidelines to ensure a smooth and effective rollout.
...
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
A NetMRI VM, whether a collector or an Operations Center, is hardware intensive and requires high performance. If you run or plan to run virtual machines in an Operations Center environment, make sure that your virtual machine hosts successfully conform to the required number of network devices. To do so, download the Infoblox Benchmark tool from the Infoblox Support site at https://support.infoblox.com. For more information, also download the Benchmarking Guide for NetMRI 7.4.2 from the same location.
For related VM best practices, see Virtual Machine Best Practices.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Initial connections to the NetMRI Administrative Shell using an SSH command line client to the IP address of the MGMT port require a username as one of the command line parameters, as shown in this example:
ssh –l admin <system>
where <system> is the hostname or IP address assigned to NetMRI. At that point, you are prompted for the admin account password, which is the same as that used for the browser interface.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
When you set up and deploy an Operations Center and its associated collectors, follow some best-practices guidelines to ensure a smooth and effective rollout.
- Keep device management levels below the licensed device limits on each collector appliance.
- Though you have greater flexibility for network connectivity through using network views, multiple scan interfaces and virtual scan interfaces, these features do not influence the licensing limits and capacities of your appliances.
- License limits should be defined to allow for organic and anticipated growth of the network. Consult with your Infoblox sales representative for a detailed assessment of your licensing needs.
- License limits are enforced on each collector appliance in an OC deployment. Your OC design should avoid having excessive numbers of licenses on collectors, which can overwhelm the Operations Center and prevent timely operation.
- New devices can 'bump' older previously-discovered devices from the license limit.
- Devices in higher-ranked device groups will be prioritized for licensing. (You can change device group rankings in Settings icon –> Setup –> Collection and Groups –> Groups tab.)
- Avoid using device licenses on devices in end-user network segments.
- During setup of a new deployment, use the default network view when you define your first discovery ranges to initially discover the network.
- An initial network view will be present in a new Operations Center deployment. Initial setup for a new Operations Center deployment automatically creates a default network view, named Network 1, as part of the procedure. This network view is automatically assigned to the Collector appliance's LAN1 port before you perform discovery of the network.
- When you create your initial discovery ranges, the Network 1 network view is automatically assigned to the LAN1 interface on the Collector. This network view represents the global routed network, which is the network that NetMRI will discover that is not reliant on virtual networks to route traffic.
- When you create your discovery ranges, static IP addresses and Seed Routers (in Settings icon –> Setup –> Discovery Settings –> Ranges/Static IPs/Seed Routers), each range provides a Network View drop-down menu. You select one network view for each discovery setting; however, a network view can work with multiple discovery ranges. A single network view can use all three discovery objects.
You define network views (under Settings icon –> Setup –> Network Views) and can assign other networks to those views. - For VRF discovery, you do not need to define discovery ranges in the initial rollout. NetMRI will discover VRF-aware devices in its first discovery of the global enterprise network. The system then displays a System Health alert notifying you that unassigned VRFs have been discovered.
...
- Filter down to the most important data, such as individual device groups, specific time windows and other Report settings.
- Schedule large, complex reports to run during off-hours.
- Avoid unnecessarily large reports. Example: Save out monthly reports instead of running multiple-month reports.
- Disable details for reports offering that function, if and when desirable and the details are not germane to the report.
- If you have simultaneously running reports, change the Concurrently Running Reports setting under Settings icon –>General Settings–>Advanced Settings page.
6. Manage Syslog Traffic.
- When sending syslog to the appliance, limit the log level to reduce volume.
- You can find a description of the specific Syslogs that NetMRI processes at the example URL: https://your-netmri/netmri/api/change/syslog-config.tdf?contentType=text/xml.
...
A NetMRI VM, whether a collector or an Operations Center, is highly demanding of the host's I/O processes. Should you plan to run one or more virtual machines as collectors in an Operations Center environment, you must verify your virtual machine hosts to successfully conform to the requested number of network device licenses. To do so, contact your Infoblox Sales representative or Infoblox Support.
For more information, refer to the Benchmarking Guide for NetMRI 7.4.2 that is available for download from the Infoblox Support site at https://support.infoblox.com.
...
6. Manage Syslog Traffic.
- When sending syslog to the appliance, limit the log level to reduce volume.
- You can find a description of the specific Syslogs that NetMRI processes at the example URL: https://your-netmri/netmri/api/change/syslog-config.tdf?contentType=text/xml.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
4. Enable Intel VT options in the BIOS of the host system.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Follow the points below to ensure effective discovery of the network:
...