...
If you limit the context of the SNMP community string in an individual VRF to the context of only that VRF, Network Insight will not be able to determine that the device it has discovered inside that VRF is the same device it has found inside other virtual networks. This may result in extra, un-correlated devices in the network. For information about how to configure SNMP credentials, see Configuring SNMP1/v2 Credentials for Polling and Configuring SNMPv3 PropertiesCredentials.
Network Insight will become aware of some devices inside of virtual networks from the route and ARP tables of routers that it manages. Without network connectivity into those virtual networks through a virtual discovery interface, Network Insight cannot discover all the devices or manage them. To create the necessary connectivity, you must configure a Network Insight discovery interface to be part of the VRF.
Network Insight collects and parses the ARP and routing information from within a VRF context, but this data will not be used for further discovery unless the VRF virtual network is associated with a network view that is mapped on a discovery interface. For more information about how to map network views to discovery interfaces, see Mapping Discovery Interfaces to Network Views.
Global VRFs are labeled as: "default(IOS)" for IOS, "default" for Nexus and "master" for JunOS.
For discovery and periodic polling on Juniper devices through an interface that is not in the Juniper default VRF (master), the query must use a special "default@credential" format. This setting assumes that users do not have management interfaces in a VRF. Your defined SNMP credentials for VRF-aware Juniper devices must use syntax similar to: "@credential". (Note that when querying VRF-aware Juniper devices via an interface that is in the default VRF, a plain community string can be used without the "@" character.)
When configuring Network Insight to discover networks that employ route-leaking, discovery ranges for each network view should only be defined to include IP addresses that belong to that network view. In other words, any given Device IP should only fall within the discovery ranges of one network view. If discovery ranges are defined such that a device can be discovered by two different network views, the device may also be discovered via an unexpected network view. For information about how to define discovery ranges, see Discovering Devices and Networks.
...
The topology of your network helps determine how you deploy Network Insight for VRF network management. To use Network Insight effectively in the network, you must possess some knowledge about your network so you can decide how to configure Network Insight to reach all the virtual networks you want to discover and manage. This section describes some common VRF-related network types for which you can deploy Network Insight.
Using the following three network types, all examples in this section help you define the number of network views and discovery interfaces so you can reach all locations in your network.
VRF Network Type 1: A network with a management VRF and several isolated production VRFs that include VRF-aware devices in the network.
VRF Network Type 2: A network with a shared service deployment VRF (shared VRF) and several isolated production VRFs that include VRF-aware devices in the network. The production VRFs share routes with the shared VRF, a practice also called route-leaking.
VRF Network Type 3: A network with several VRF-ignorant devices that reside in different L3 spaces, with no management VRF.
VRF Network Type 1 has the following characteristics:
...
Network Views: Create a network view for each network (Management, Red, Yellow, Green).
Discovery Interfaces: Create virtual discovery interfaces for each VRF network.
Discovery Ranges: Define IP discovery ranges for each VRF network.
The discovered VRF instances must be associated with the network views to which they belong. For more information, see Viewing Discovered VRFs and Mapping Network Views.
Deploying Network Insight in VRF Network Type 2: All VRFs Reachable from a Shared Services VRF
...
Network Views: Create a network view for each network (e.g., Management, Red, Yellow, Green).
Discovery Interfaces: Create virtual discovery interfaces for each VRF network.
Discovery Ranges: Define IP discovery ranges for each VRF network.
The discovered VRF instances must be associated with the network views to which they belong. For more information, see Viewing Discovered VRFs and Mapping Network Views.
Each of the network views requires a single virtual discovery interface using 802.1q tagging as indicated in the figure. When defining the virtual discovery interfaces, use the 802.1q tag from the network devices. The primary differences are as follows:
...