---
title: "Operational and Deployment Best Practices"
canonical: "https://docs.infoblox.com/space/NetMRIAdminG752/42402136/Operational%20and%20Deployment%20Best%20Practices"
format: markdown
---
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.

1. *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 the 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.
2. *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 the 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.  
To define network views, click the **Settings** icon > **Setup** > **Network** **Views** and then 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.

*3. Avoid using too many device groups. Target using 50 or fewer Extended device groups. Platform Limits also influence the number of device groups allowable in your system.*

> Macro (legacy-content)

*4. Ensure** reliable** network** connections** between** collectors** and** the** Operations** Center **node*.

> Macro (legacy-content)

*5. Use recommended methods to improve reporting performance for your Operations Center.*

> Macro (legacy-content)

*6. Manage Syslog Traffic.*

> Macro (legacy-content)