Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 GroupsYou 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.

    Note
    titleNote

    See Creating Device Groups for information on the Groups tab and its associated functions.


  • 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 Collection and Running Discovery Diagnostics for more information.

...

Note
titleNote

See the section Global Switch Port Management Polling Settings for more information on global settings for switch port polling.

...

  • Config Collection: If enabled, the current NetMRI virtual is able to collect configuration data from network devices using enabled protocols.
  • Config Locked: Devices with collected information that show changes during subsequent config collections can be reported as showing "Unauthorized Changes".
  • Use Telnet Protocol: NetMRI opens Telnet terminal sessions with devices that support this option and reads the configurations. Individual devices can make use of Telnet login credentials.
  • Use SSH Protocol: NetMRI opens SSH terminal sessions with devices that support this option and reads the configurations. Individual devices can make use of SSH login credentials.
  • Use HTTP Protocol: NetMRI opens HTTP browser sessions with devices that support this option and reads the configurations. Individual devices can make use of HTTP login credentials.
  • Use Vendor Default Credentials: Enables NetMRI to use its library of vendor-default credentials as part of the process of collecting configuration data.


Note
titleNote

See Adding and Editing Device Credentials30802695 for more information on adding logins for specific devices in the Device Viewer.

...

Note
titleNote

SNMP and/or CLI Credentials can be specified within the Device Viewer for individual devices. Should such a credential not work for a given device, or if command-line access is lost for a given device, NetMRI will always re-guess credentials from the global credential list, including vendor defaults if available. See the sections Adding and Testing SNMP Credentials for a Device and Adding and Testing CLI Credentials for a Device for more information.

...

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 FileNetMRIModel >AttributeField Description
General Device Data
discovered_nameDevice > DeviceNameDNS name of the IP address.
ip_addressDevice > DeviceIPDottedA valid IPv4 address. Required.
mac_addressDevice > DeviceMACA valid mac address. Must be lowercase. Optional.
last_discovered_timestampDevice > DeviceTimestampTimestamp of last time the discoverer has seen the device. A UTC timestamp. Required.
first_discovered_timestampDevice > DeviceFirstOccurrenceTimestamp of the first time the discoverer has seen the device. A UTC timestamp. Optional.
netbios_nameN/AThe NetBIOS name of the device. String type. The maximum size is 15 characters. Optional.
osDevice > DeviceVersionThe OS of the IP address. String Type. The maximum size is 256 characters. Optional.
device_modelDevice > DeviceModelThe model of the device.
device_vendorDevice > DeviceVendorThe vendor of the device.
device_locationDevice > DeviceSysLocationThe location of the device.
device_contactDevice > DeviceSysContactThe contact of the device.
ouiDevice > DeviceOUIThe OUI of the device.
discovererN/AAlways "NetMRI".
Attached Device Data (only for endhosts)
network_component_typeDevice > DeviceTypeThe type of component connected to the IP address. Eg Switch, Router, Other. Optional. String type. Max size 32.
network_component_nameDevice > DeviceNameThe name of component connected to the IP address. Optional. String type. Max size 64.
network_component_ descriptionDevice > DeviceSysDescThe description of component connected to the IP address. Optional. String type. Max size 256.
network_component_ipDevice > DeviceIPDottedThe IP address of the component connected to the IP address. Optional. String type. IPv4 address format.
network_component_modelDevice > DeviceModelThe model of the component connected to the IP address.
network_component_vendorDevice > DeviceVendorThe vendor of component connected to the IP address.
network_compInterface > ifNameonent_locationDevice > DeviceSysLocationThe type of component connected to the IP address.
network_component_contactDevice > DeviceSysContactThe contact of the component connected to the IP address.
network_component_port_ numberInterface > SwitchPortNumberThe port number on the component connected to the IP address. Optional. Unsigned integer type. Range 0 - 9999.
network_component_port_ nameInterface > ifNameThe port name on the component connected to the IP address. Optional. String type. Max size 64.
network_component_port _descriptionInterface > ifDescrThe description of the Port on the component connected to the IP address. Optional. String type. Max size 256.
Port Data
port_vlan_nameVlan > VlanNameThe name of the VLAN on the Port. Optional. String type. Max size 64.
port_vlan_numberVlan > VlanIndexThe port VLAN Number. Optional. Unsigned integer type. Range 0 - 9999.
port_speedInterface > ifSpeedThe speed settings on the switch port. Optional. String type. Valid values are 10M, 100M, 1G, 10G, 100G, and Unknown.
port_duplexInterface > ifDuplexThe duplex settings on the switch port. Optional. String type. Valid values are Full and Half.
port_statusInterface > ifAdminStatusAdministratively up or down. Optional. String type. Valid values are Up, Down, and Unknown.
port_link_statusInterface > ifAdminStatusConnected or not. Optional. String type. Valid values are: Connected, Not Connected, and Unknown.
Cisco ACI Data
tenantN/AThe ACI tenant.
bridge_domainN/AThe ACI bridge domain.
endpoint_groupsN/AThe ACI endpoint groups.
VRF and BGP Data
vrf_nameInterface > vrf_nameThe VRF name of the IP address.
vrf_descriptionInterface > vrf_descriptionThe VRF description of the IP address.
vrf_rdInterface > vrf_rdThe VRF route distinguisher of the IP address.
bgp_asN/AThe BGP autonomous system number of the device.
Wireless Access Point Data
ap_nameN/AThe name of the wireless access point.
ap_ip_addressN/AThe IP address of the wireless access point.
ap_ssidN/ASSID 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
Anchor
bookmark189
bookmark189
Supporting Cisco Discovery Service

NetMRI 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:

...