NetMRI discovery depends on a collection of under-the-hood features to ensure that polling and addition of devices in the network proceed smoothly and accurately. This chapter describes the three following critical tasks.
Defining Data Collection and Device Groups: You must define important settings for network polling. This topic involves the processes of data collection and polling of devices across the network, including polling of switched Ethernet devices. The definition of device and interface groups is discussed in other topics later in this Guide. For more information, see Defining Group Data Collection Settings.
- ManagingSNMPandCLICredentials: Credentials are a critical component for discovery and Configuration Management. You can define global default values for admin account logins, enable passwords, and also define admin account logins and enable passwords on individual devices. For more information, see Adding and Editing Device Credentials.
- DebuggingandManagingCollectionResults: When data collection and polling stops for any reason, NetMRI provides methods for determining the cause of the failure and ways to fix it. See Debugging Issues in Discovery and Data Data Collection Techniques and and Running Discovery Diagnostics for more information.
Anchor |
---|
| Defining Group Data Collection Settings |
---|
| Defining Group Data Collection Settings |
---|
|
Defining Group Data Collection Settings
...
- Go to Settings icon > General Settings > Advanced Settings > Data Collection category. The SNMPv1 Data Collection Fallback setting prevents NetMRI from attempting to collect from a device that has a spurious or incorrect SNMPv2c credential, and will 'fall back' to SNMPv1 for collection.
- Click the Actions icon and choose Edit.
- If you want SNMPv1 to be allowed for data collection, choose enabled for data collection;
- If you want SNMPv2c to be the specific data collection protocol, choose disabled for data collection.
- Click OK to commit settings.
- Go to Settings icon > General Settings > Advanced Settings > Discovery category. The SNMPv1/SNMPv2c Discovery Version setting allows a choice between three options:
- Use SNMPv1 for credential discovery.
- Use SNMPv2c for credential discovery.
- Use both SNMPv1/SNMPv2c for credential discovery.
Should you choose the third option, Use both SNMPv1/SNMPv2c for credential discovery, NetMRI continues to use SNMPv1 for credential discovery on devices that support only SNMPv1, and uses SNMPv2c whenever it is supported by target devices. Using the Use both SNMPv1/SNMPv2c option imposes some time delay for credential collection, in cases where non-working/incorrect credentials are attempted during data collection.
- Click the Actions icon and choose Edit.
- For exclusive use of SNMPv1, choose the Use SNMPv1 for credential discovery option.
- For exclusive use of SNMPv2c without fallback to SNMPv1, choose the Use SNMPv2c for credential discovery option.
- For default use of SNMPv2c with fallback to SNMPv1 for devices that support that protocol, choose the Use both SNMPv1 and SNMPv2c for credential discovery option.
- Click OK to save your settings.
...
For additional information about NIOS IPAM Sync, see Overlay/Overwrite Logic
Anchor |
---|
| Configuring IPAM Sync |
---|
| Configuring IPAM Sync |
---|
|
Configuring IPAM Sync
This section describes the following:
...
Data Field in IPAM Sync Export File | NetMRIModel >Attribute | Field Description |
---|
General Device Data |
discovered_name | Device > DeviceName | DNS name of the IP address. |
ip_address | Device > DeviceIPDotted | A valid IPv4 address. Required. |
mac_address | Device > DeviceMAC | A valid mac address. Must be lowercase. Optional. |
last_discovered_timestamp | Device > DeviceTimestamp | Timestamp of last time the discoverer has seen the device. A UTC timestamp. Required. |
first_discovered_timestamp | Device > DeviceFirstOccurrence | Timestamp of the first time the discoverer has seen the device. A UTC timestamp. Optional. |
netbios_name | N/A | The NetBIOS name of the device. String type. The maximum size is 15 characters. Optional. |
os | Device > DeviceVersion | The OS of the IP address. String Type. The maximum size is 256 characters. Optional. |
device_model | Device > DeviceModel | The model of the device. |
device_vendor | Device > DeviceVendor | The vendor of the device. |
device_location | Device > DeviceSysLocation | The location of the device. |
device_contact | Device > DeviceSysContact | The contact of the device. |
oui | Device > DeviceOUI | The OUI of the device. |
discoverer | N/A | Always "NetMRI". |
Attached Device Data (only for endhosts) |
network_component_type | Device > DeviceType | The type of component connected to the IP address. Eg Switch, Router, Other. Optional. String type. Max size 32. |
network_component_name | Device > DeviceName | The name of component connected to the IP address. Optional. String type. Max size 64. |
network_component_ description | Device > DeviceSysDesc | The description of component connected to the IP address. Optional. String type. Max size 256. |
network_component_ip | Device > DeviceIPDotted | The IP address of the component connected to the IP address. Optional. String type. IPv4 address format. |
network_component_model | Device > DeviceModel | The model of the component connected to the IP address. |
network_component_vendor | Device > DeviceVendor | The vendor of component connected to the IP address. |
network_compInterface > ifNameonent_location | Device > DeviceSysLocation | The type of component connected to the IP address. |
network_component_contact | Device > DeviceSysContact | The contact of the component connected to the IP address. |
network_component_port_ number | Interface > SwitchPortNumber | The port number on the component connected to the IP address. Optional. Unsigned integer type. Range 0 - 9999. |
network_component_port_ name | Interface > ifName | The port name on the component connected to the IP address. Optional. String type. Max size 64. |
network_component_port _description | Interface > ifDescr | The description of the Port on the component connected to the IP address. Optional. String type. Max size 256. |
Port Data |
port_vlan_name | Vlan > VlanName | The name of the VLAN on the Port. Optional. String type. Max size 64. |
port_vlan_number | Vlan > VlanIndex | The port VLAN Number. Optional. Unsigned integer type. Range 0 - 9999. |
port_speed | Interface > ifSpeed | The speed settings on the switch port. Optional. String type. Valid values are 10M, 100M, 1G, 10G, 100G, and Unknown. |
port_duplex | Interface > ifDuplex | The duplex settings on the switch port. Optional. String type. Valid values are Full and Half. |
port_status | Interface > ifAdminStatus | Administratively up or down. Optional. String type. Valid values are Up, Down, and Unknown. |
port_link_status | Interface > ifAdminStatus | Connected or not. Optional. String type. Valid values are: Connected, Not Connected, and Unknown. |
Cisco ACI Data |
tenant | N/A | The ACI tenant. |
bridge_domain | N/A | The ACI bridge domain. |
endpoint_groups | N/A | The ACI endpoint groups. |
VRF and BGP Data |
vrf_name | Interface > vrf_name | The VRF name of the IP address. |
vrf_description | Interface > vrf_description | The VRF description of the IP address. |
vrf_rd | Interface > vrf_rd | The VRF route distinguisher of the IP address. |
bgp_as | N/A | The BGP autonomous system number of the device. |
Wireless Access Point Data |
ap_name | N/A | The name of the wireless access point. |
ap_ip_address | N/A | The IP address of the wireless access point. |
ap_ssid | N/A | SSID of the wireless access point. |
...
- Network sync: Newly-imported subnets are imported as “managed”.
- If the imported subnet conflicts with an existing subnet, it is not accepted. The imported subnet can go into a container as long as there is no conflict.
- If the subnet already exists, no changes are made.
- If the subnet is in IPAM but not in NetMRI, it is left in IPAM.
- IP address sync: New IP addresses are added and marked as “unmanaged”. If an IP address already exists, the field values are overwritten during the import.
- Before NetMRI 7.1.4 and NIOS 8.1, if the IP address exists in IPAM but it is not in the import file, it is left in IPAM.
- As of NetMRI 7.1.4 and NIOS 8.1, if the IP address exists in IPAM but it is not in the import file, its discovered data is cleared out. You can control the time that the IP address stays in the NetMRI database after it is no longer discovered under NetMRI. To do so, go to Setup > General Settings > Advanced Settings.
Viewing IPAM Sync Discovered Data in NetMRI and NIOS
In NIOS, you can view the data discovered by NetMRI and synchronized using IPAM Sync as follows:
...
Anchor |
---|
| Supporting Cisco Discovery Service |
---|
| Supporting Cisco Discovery Service |
---|
|
Supporting Cisco Discovery ServiceNetMRI automatically supports an Infoblox utility, Cisco Discovery Service, that enables network administrators to provide Cisco-validated reporting and analysis. NetMRI operates as a Cisco Discovery Service-enabled system supporting discovery of network systems for analysis and management. You can use the CDS Integration Tool as part of a new NetMRI installation, or use the tool to extract further insight and value from an existing deployment. Cisco Gold Partner status is required for effective use of the software utility.
NetMRI supports CDS API version 2.0 and uses a NetMRI device or virtual machine to inspect all aspects of a network's Cisco infrastructure to collect the following information:
...