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

...

Group data collection settings (Settings icon –> > Setup –>  > Collection and Groups) settings define global NetMRI settings for discovery and configuration management:

...

Global tab settings in the Network Polling panel (Settings icon –> > Setup –>  > Collection and Groups –>  > Global tab –> > Network Polling side tab) provide system-level control over NetMRI's SNMP and discovery data collection operations.

  • Port Scanning: If enabled, NetMRI probes the TCP and UDP ports listed at Settings icon –> > Setup –>  > Port List, to determine whether they are open. See the results of this scanning action at Network Explorer –>  > Summaries –>  > Ports for the entire network, and Device Viewer –>  > Device/Network Explorer –>  > Open Services for an individual network device.
    If Port Scanning is disabled, NetMRI attempts no port probes other than SNMP on any device. 
  • Fingerprinting: (Available in full NetMRI license) If enabled, NetMRI attempts to identify each network device based on the response characteristics of its TCP stack. This information is used to determine the device type. In the absence of SNMP access, fingerprinting is usually the only way to identify non-network devices. If disabled, devices accessible via SNMP are identified correctly; all other devices are assigned a device type of Unknown.
    Fingerprinting is disabled by default for network polling
    Anchor
    bookmark150
    bookmark150
    . You must enable fingerprinting to use the Automation Change Manager's Rogue DHCP Detection feature.

...

Note
titleNote

Smart subnet ping sweeps should not be attempted on subnets larger than /22. Ping sweeps are

Anchor
bookmark152
bookmark152
not used on IPv6 networks because of the dramatically greater scale of network addresses in the IPv6 realm. Smart subnet ping sweeps also have several differences from the discovery ping sweeps that can be enabled under Discovery Settings, which can be found under Settings icon –> > Setup –>  > Discovery Settings.


  • Refresh device caches before collecting switch port data: Check box to enable refreshing of ARP caches on switches and switch-routers in the managed network before NetMRI performs polling of switch ports. Enabling this feature will not produce an automatic ping sweep of the managed network. The benefit of this feature is that it enables more accurate detection of all endpoint devices on switches. Without ARP refresh, some endpoint devices may not be detected. This feature is globally disabled by default. With this setting globally enabled, individual device groups can also be set to enable or disable this feature.

...

The Collection and Groups feature set also specifies the protocols allowed for configuration collection. You specify the Collectors of network data for NetMRI through the Config Management

Anchor
bookmark154
bookmark154
 section of the Global page (Settings icon –>> Setup –>> Collection and Groups –>> Global –>> Config Management).

Note
titleNote

Disabling the Config Collection check box will disable configuration data collection for the current NetMRI appliance.

...

Note
titleNote

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

...

NetMRI carries out Switch Port Management polling after discovering the relevant devices and adds them to a Switch Port Management device license count. NetMRI offers several polling options from the Settings icon –>> Setup –>  > Collection and Groups –>  > Switch Port Management side tab:

...

The Device Viewer offers dedicated CLI Credentials and SNMP Credentials pages (Settings icon –> > Setup –>  > CLI Credentials and Settings icon –> > Setup –>  > SNMP Credentials) to globally manage and test CLI and SNMP credentials. See About SNMP Credentials, About CLI Credentials, and Credential Import Formats for further details about credential definition.

...

To establish SNMP device credentials at the device level, perform the following:

  1. Go to Network Explorer –>  > Inventory –>  > Devices and click a device IP, or to Network Explorer –>  > Discovery and click a device IP. The chosen device's Device Viewer appears.
  2. Click Settings and Status –>  > SNMP Credentials to open the page for creating SNMP login credentials.
  3. Click the Edit button to enable changes to the current settings for device-specific SNMP information.
  4. Click either Use SNMP v1/2c or Use SNMP v3. The options are mutually exclusive. If using SNMP v1/2c, enter the community string for the device.
    If using SNMP v3, enter the required authentication and privacy passwords and choose their encryption protocols from the Auth. Protocol and Privacy Protocol drop-downs.
  5. Click Test to try out the new credential. You can also click Show Password to verify that you've entered the correct values.

...

To establish CLI device credentials at the device level, complete the following:

  1. Go to Network Explorer –>  > Inventory –>  > Devices and click a device IP, or to Network Explorer –>  > Discovery and click a device IP. The chosen device's Device Viewer appears.
  2. Click Settings and Status –>  > CLI Credentials to open the page for creating CLI login credentials.
  3. Click Edit.
  4. For CLI Credentials, you may supply up to three different login tuples: for SSH, Telnet, and for the HTTP protocol. Enter the username and password for any or all three as required for the selected device. For SSH and Telnet, you also provide a port number. You can use the default or custom ports.
  5. Provide the Enable Password.
  6. Click Test to try out the new credential. You can also click Show Password to verify that you have entered the correct values.

...

This feature can be verified under Configuration Management –>  > Archive tab, and clicking the table row for the device. This brings up the Config Explorer for the selected device. A Get Config button is also provided in this location.

...

Manually entered community strings are used first, in priority order, then the default community strings are tried in priority order if the Use Vendor Default Community Strings option is enabled in the Settings icon –> Setup section –> > Collection and Groups –>  > Global tab –> > Network Polling panel. That option allows you to disable the use of the vendor default community strings for determination of which strings NetMRI can use. This is typically done in installations having tight security setups that have removed all vendor defaults from their installation. Note that this option does not prevent the vendor default from running.

NetMRI can periodically check for vendor default community strings. Checking for vendor default community strings can help ensure that the network meets compliance standards. You can add vendor-specific default community strings that may not be listed. NetMRI will only check for default vendor community strings when the Vendor Default Credential Collection option is enabled in the Settings icon –> > Setup –>  > Collection and Groups –>  > Global tab –> > Config Management panel.

Anchor
SNMP Collection Logic
SNMP Collection Logic
Anchor
bookmark165
bookmark165
SNMP Collection Logic
Anchor
bookmark166
bookmark166

...

  • For the network: In the Network Polling panel (Settings icon –> > Setup section –> > Collection and Groups –>  > Global tab).
  • For groups: In the Device Groups side tab (Settings icon –> > Setup section Collection and Groups page –> > Groups tab –> tab > Device Groups side tab).
  • For devices: In the Device Viewer's General Settings page (Device Viewer –>  > Settings & Status section –> > General Settings page).

SNMP Data Collection and Licensing Effects

...

NetMRI automatically discovers and manages devices that support only the SNMPv1 protocol, regardless of setting. To define how NetMRI applies its SNMPv1 and SNMPv2 support for data collection, two Advanced Settings can be changed.

  1. 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.
  2. 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.
  3. Click OK to commit settings.
  4. Go to Settings icon –> > General Settings –>  > Advanced Settings –>  > Discovery category. The SNMPv1/SNMPv2c Discovery Version setting allows a choice between three options:

...

To add SNMPv3 credentials, complete the following:

  1. Open Settings icon –> Credentials –>  > SNMPv3.
  2. Click New
  3. To define the order of lookup, enter a new Priority value. The lower the value, the higher the priority of the user credential.
  4. Enter the Authentication Password and choose the Authentication Protocol.
  5. Enter the Privacy Password and choose the Privacy Protocol.
  6. Click Save.
  7. To test a credential, click Test. Choose the Hostname or IP and click Start.
  8. To import a set of credentials, click Import. The .CSV file should be a set of tab-separated values matching the categories for the SNMPv3 credentials table. You do not need the column headers as the first row in the file, which can be created in a text editor or exported from Microsoft Excel.

Anchor
About CLI Credentials
About CLI Credentials
Anchor
bookmark171
bookmark171
About CLI Credentials

The CLI tab (Settings icon –> > Setup –>  > Credentials –>  > CLI tab) lists site-specific username and password combinations that NetMRI uses when attempting to access a device using telnet or SSH. After a device is discovered, NetMRI uses these for configuration collection, CCS scripts, and other purposes.

...

The CLI Vendor Defaults tab (Settings icon –> > Setup –>  > Credentials –>  > CLI Vendor Defaults tab) lists well-known (and therefore weak) username and password combinations. These credentials are a subset of the published vendor default username/passwords used when the device is shipped by the manufacturer.

Add other vendor default passwords listed in the Default Credentials Report. If the Vendor Default Credential Collector option (Settings icon –>> Setup –> > Collection and Groups –> > Global tab –> > Config Management panel) is enabled and a vendor default username/password combination successfully logs into a device, an issue is generated.

...

The syntax for credential data files imported through corresponding tabs in the Settings icon –> > Setup –>  > Credentials page, and in the Setup Wizard's Setup Wizard: CLI Credentials, Setup Wizard: SNMPv1/2 Credentials, and Setup Wizard: SNMPv3 Credentials (Rare) steps, are described in this section.

...

The CC column in the Network Explorer –>  > Discovery table reveals important debugging information for configuration collection issues. The most important discovery and Config Collection issues are listed in this topic, along with where in NetMRI to fix them.

Config Collection
Image RemovedWarning icons
Warning icons in the CC column indicate possible configuration data collection problems. Other locations that report related messages include Device Viewer
–>
 > Settings & Status
–>
> Management Status and Settings icon
–>
> Setup
–>
 > Discovery Settings
–>
 > Seed Router. Specific messages are described below.
Config Not ChangedThe configuration for the device has not changed since the previous polling of the device. No problem is indicated here unless you have pushed a changed configuration to the device. Even in those cases, allow some more time for the device to synchronize with NetMRI. If you expect changes to be reflected in device polling. go to Device Viewer
–>
> Configuration Management
–>
> Config Explorer and check the Running Config Saved? status line. If the answer is No, ensure the changes in the device's running-config are saved according to the device's configuration data saving requirements.
CLI Credentials UnknownNetMRI cannot obtain the device configuration due to not having the correct CLI username/password tuple, and credential guessing did not work for the device. Go to the Device Viewer
–>
 > Settings & Status
–>
 > CLI Credentials page for that device. Click Edit and enter the necessary values for the SSH and/or Telnet login tuple and the Enable Password if necessary. Each attempt at connection and collection is listed in the table. Note that the C column, for CLI Credentials Status, may show an Error, usually listed as Failed to authenticate: Invalid Username and/or password.
Configuration Collection Disabled GloballyThis message appears for devices that support configuration collection, but the collection was skipped because Config Collection is globally disabled in NetMRI. The same message appears in the Device Viewer
–>
> Settings & Status
–>
 > Management Status page. Go to Settings icon
–>
> Setup
–>
 > Collection and Groups
–>
 > Groups
–>
 > Config Management side tab, and enable the Config Collection checkbox. Also, ensure the proper protocols (SSH, Telnet, HTTP) are enabled for config collection.
Configuration Collection Enabled Globally, All Protocol Options DisabledThis message appears for devices that support configuration collection, but the collection was skipped because Config Collection is globally enabled in NetMRI but no data collection protocols were enabled. The same message appears in the Device Viewer
–>
> Settings & Status
–> 
 > Management Status page. Go to Settings icon
–>
> Setup 
–>
> Collection and Groups
–>
 > Groups
–>
 > Config Management side tab, and enable the Config Collection checkbox. Ensure the proper protocols (SSH, Telnet, and/or HTTP) are enabled for config collection.
Configuration Collection Disabled at Device Group levelThe device showing this message currently has config collection disabled for the Device Group to which the device belongs. Go to Settings icon
–>
> Setup
–>
 > Collection and Groups
–>
 > Groups, click the Action icon and choose Edit for the selected Device Group. In the Group Settings tab, enable the Config Collection checkbox.
Not Included by Discovery SettingsThe message indicates that although the device has been detected by NetMRI, it is not included in any IP Ranges or as a Static IP with the Exclude from Discovery Settings option, is not reachable through Device Hints, or is not detectable as a Seed Router.

The device in question may also be explicitly excluded from management by previously clicking the Unmanage button in Device Viewer
–>
 > Settings & Status
–>
 > Management Status page. Go to Settings icon
–>
> Setup
–>
 > Discovery Settings and change the appropriate settings in any of the four categories. This message appears only during a manual Get Config operation.
Not
LIcensed
LicensedThe message indicates that the device has not been added automatically to the full NetMRI license for the appliance reporting the Issue. Go to the Device Viewer
–>
> Settings & Status
–>
 > Management Status page and click the License button. In the License Status dialog, choose the settings necessary to change the licensing status for the device. This message appears only during a manual Get Config operation.

Anchor
Running Discovery Diagnostics
Running Discovery Diagnostics
Anchor
bookmark178
bookmark178
Running Discovery Diagnostics

...

The Discovery Diagnostics tool (Tools –>  > Device –>> Discovery Diagnostics) helps Infoblox Technical Support to diagnose discovery and data problems for a given device.

...

NetMRI tracks the last time it has successfully communicated with a device via NMAP (used for fingerprinting), SNMP, and telnet/SSH/HTTP. This timestamp information appears in the Network Explorer –> > Discovery page in NetMRI. To provide the most accurate possible timestamp, the protocols used to generate the timestamps also includes ICMP Ping and NetBIOS communications protocols. Ping and NetBIOS data results are not directly displayed in the Network Explorer –> > Discovery page. NetMRI uses the maximum timestamp for a given device (i.e. across all protocols) to populate the timestamp value that is sent to NIOS.

For how to configure a synchronization, see Configuring IPAM Sync. This section also lists IPAM Sync data fields that are exported from NetMRI to NIOS.

...

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:

...

To add a sync configuration, complete the following:

  1. In Settings –> > Setup –> > NIOS IPAM Sync –> Sync > Add Sync Configuration.
    The Sync configuration wizard opens.
  2. In Step 1 of the Wizard, enter the NIOS Grid Master IP address or host name, with user name and password. For standalone NIOS deployments, enter the IP address or host name of the NIOS device. The default login credentials are admin/infoblox.
  3. Click Next.


    Note
    titleNote

    Make sure the NIOS system is reachable before attempting a connection, and ensure you have the correct admin account and password. The specified username and password also must provide access to the Infoblox DMAPI (Data and Management API). Any NIOS administrator account can be set to allow API access from within NIOS with an Allowed Interfaces setting of API. Consult the Infoblox API Documentation guide for the version of NIOS in the current operation for more details, and consult the NIOS Administration Guide for the procedure on defining API interface access for an admin account. 


  4. In Step 2, in NS1 Network View, select default as the view to which to export data. This information is obtained from the Infoblox Grid Master.
  5. In NetMRI Network View, select the required view.
  6. In Time restriction, select Include all data, regardless of polling time.

    In versions prior to 7.3.1, NetMRI sent data collected from devices that were successfully polled within the last two hours. This restriction was removed in version 7.3.1. You can request to export all data regardless of last successful device polling time or data from devices successfully polled in the last several hours.
  7. Activate Synchronize Device Information if devices (IP addresses) are to be included in the synchronization.
  8. If you enabled the synchronization of device information and you want to include end host IP addresses into NIOS IPAM Sync, select Include addresses from ARP tables.
    By default, only routers IP addresses are included into NIOS IPAM Sync. Selecting this option allows you to export IP addresses of end hosts from ARP tables of discovered devices to NIOS IP Map, along with routers IP addresses. These end hosts are listed in a separate tab in NetMRI: Network Explorer ->  > Switch Port Management ->  > End Hosts ->  > End Host Present. If the discovery engine does not recognize a device as infrastructure or network device, it is treated as end host. Data displayed for end hosts collected from ARP tables includes the IP address, MAC address, and Last Discovered and First Discovered stamps.


    Note
    titleNote

    Retrieving end hosts IPs based on ARP entries does not guarantee accurate results as the lifetime of ARP tables entries on network devices is very limited (e.g., up to 5 minutes officially, 10 minutes in real life for Cisco IOS-based devices) and the amount of tables entries is relatively small.


  9. To add internal subnets as networks in NIOS, activate the Add IPAM networks for subnets within NetMRI discovery ranges option. This will export subnets discovered by NetMRI and classified as internal (i.e., within the defined discovery ranges). To export all internal subnets, select the All option. To limit the exported internal subnets, select the Restrict to subnet s within the following summary routes option, and enter a list of summary routes. Separate each route with a comma, or put each on a new line. Subnets within a listed summary route are exported. For example, to export only the subnets in a class A 10 network, enter 10.0.0.0/8.
  10. To add external subnets as networks in NIOS, activate the Add IPAM networks for subnets outside of NetMRI discovery ranges option. This will export subnets discovered by NetMRI and classified as external (i.e., outside the defined CIDR blocks). To export all external subnets, select the All option. To limit the exported external subnets, select the Restrict to subnets within the following summary routes option, and enter a list of summary routes as described above for internal subnets.
  11. Click Next.
  12. In Step 3, if you want to schedule synchronization, select Schedule Enabled. This is optional. If you do not schedule a synchronization, you can execute a synchronization at any time. For information, see the next section.
  13. Select a Recurrence PatternExecution Time, and day (this is the starting day for repetitive synchronizations).
  14. Click Next.
  15. In Step 4, review the sync configuration. Click < Previous if you need to change any settings.
  16. Click Finish.

...

To edit a sync configuration, perform the following:

  1. In Settings –>  > Setup –>  > NIOS IPAM Sync, select Edit in the Actions column for the required sync configuration. This displays a summary of the current configuration.
  2. Click Edit.
    The Sync configuration wizard is started. See the procedure for adding a sync configuration above for the wizard steps.

To delete a sync configuration, complete the following:

  1. In Settings –>  > Setup –>  > NIOS IPAM Sync, select Delete in the Actions column for the required sync configuration.
  2. Confirm the deletion.

...

To run a synchronization between NetMRI and a NIOS appliance, complete the following:

  1. In Settings –>  > Setup –>  > NIOS IPAM Sync, select Sync in the Actions column for the required sync configuration. 
  2. Click Yes to confirm.
    The CSV import of discovered data to NIOS is performed. The IPv4 and IPv6 networks are added to the NIOS appliance database.

...

The following table lists the data fields in the CSV file used for IPAM Sync:

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.
Maximum
The maximum size is 15 characters. Optional.
osDevice
-
> DeviceVersionThe OS of the IP address. String Type.
Maximum
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
-
> DeviceName
Name
The name of component connected to the IP address. Optional. String type. Max size 64.
network_component_ descriptionDevice
-
> DeviceSysDesc
Description
The 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
-
> DeviceVendor
Vendor
The vendor of component connected to the IP address.
network_
component
compInterface > ifNameonent_locationDevice
-
> DeviceSysLocation
Type
The type of component connected to the IP address.
network_component_contactDevice
-
> DeviceSysContact
Contact
The contact of the component connected to the IP address.
network_component_port_ numberInterface
-
> SwitchPortNumber
Port
The port number on the component connected to the IP address. Optional. Unsigned integer type. Range 0 - 9999.
network_component_port_ nameInterface
-
> ifName
Port
The port name on the component connected to the IP address. Optional. String type. Max size 64.
network_component_port _descriptionInterface
-
> ifDescr
Description
The description of the Port on the component connected to the IP address. Optional. String type. Max size 256.
Port Data
port_vlan_nameVlan
-
> VlanName
Name
The name of
the Vlan
the VLAN on the Port. Optional. String type. Max size 64.
port_vlan_numberVlan
-
> VlanIndex
Port Vlan
The port VLAN Number. Optional. Unsigned integer type. Range 0 - 9999.
port_speedInterface
-
> ifSpeed
Speed
The speed settings on the switch port. Optional. String type. Valid values are 10M, 100M, 1G, 10G, 100G, and Unknown.
port_duplexInterface
-
> ifDuplex
Duplex
The 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/A
Name
The 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.

Anchor
Overlay/Overwrite Logic
Overlay/Overwrite Logic
Overlay/Overwrite Logic

...

  • 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 is 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:

  • IP addresses data: IPAM –> > select a network –> network > IP List.
  • Networks data: IPAM –> NetworksIPAM > Networks.

The following table helps to locate IPAM Sync discovered data in the NetMRI UI.

UI Name of Discovered Data FieldData Field DescriptionPlace in NetMRI UI
General Device Data
IP AddressThe IP address of discovered network device or end host interface.Network Explorer
-
> Discovery
Last DiscoveredThe timestamp when the IP address was last discovered.
First DiscoveredThe timestamp when the IP address was first discovered.
Discovered MAC AddressThe discovered MAC address for the network device or end host. The discovery acquires the MAC address for hosts that are located on the same network as the Grid member that is running the discovery.Interface Viewer
DiscovererSpecifies whether the IP address was discovered by NetMRI or Network Insight discovery process. Equals to “NetMRI” of “Network Insight” correspondingly.N/A
OSGuess for OS by network discovery. OS info is collected from device by SNMP. Depending on device SNMP settings, this field can be populated with OS version or remain empty (mostly for end hosts) -- in last case Device Type will contain OS name. In NIOS 8.4 and newer versions fingerprint scan result will be displayed as OS of end hosts.Device Viewer
Discovered NameThe name of the network device or end host associated with the discovered IP address.
Device ModelModel name of the device in the vendor terminology.
Device VendorThe vendor name of the discovered device.
Device LocationThe physical location of the network device or endhost.Device Viewer
-
> Device/Network Explorer
-
> Device Identification
Device ContactThe contact details for the network device or endhost.
NetBIOS NameThe name returned in the NetBIOS reply or the name you manually register for the discovered host.Switch Port Management
-
> End hosts
Device Type(s)Identifies the device type.

Network Explorer

-

> Discovery

Device Viewer

Device Management IPManagement IP address of the device if the device has more than one IP.Device Viewer
-
> Settings & Status
-
> General Settings
Interface Port NameSystem name of the interface the IP associates with.Device Viewer
-
> Interfaces
Interface Port TypeHardware type of the interface the IP associates with.Device Viewer
-
> Interfaces
Open Port(s)Open ports of the device. Sample format is "TCP: 21,22,25,80 UDP: 137,139". Limited to max total 1000 ports. Data is collected by Nmap and refreshes every 24 hours. Port scanning must be enabled.N/A
Device OUIThe OUI of device.N/A
Attached Device Data
Attached Device VendorThe vendor name of the switch port connected to the discovered device.For an attached device: Device Viewer
Attached Device AddressThe IP address of the switch that is connected to the network device or endhost.
Attached Device NameIf a reverse lookup was successful for the IP address associated with this switch, the host name is displayed here.
Attached Device TypeIdentifies the switch that is connected to the discovered device.
Attached Device ModelIf a reverse lookup was successful for the IP address associated with this switch, the device model is displayed here.

Attached Device Description

A textual description of the switch that is connected to the discovered device.For an attached device: Device Viewer
-
> Device/Network Explorer
-
> Device Identification
Attached Device LocationThe physical location of the network device to which the discovered host is connected, as detected from the device during discovery.
Attached Device ContactThe contact details of the network device to which the endhost is connected, as detected from the device during discovery.
Attached Device Port DescriptionA textual description of the switch port that is connected to the discovered device.For an attached device: Device Viewer
-
> Interface
-
> Configuration
Attached Device Port NameThe name of the switch port connected to the discovered device.
Attached Device PortThe number of the switch port connected to the discovered device.
Attached Device Port IDIdentificator of the switch port that is connected to the discovered device.
Port Data
Port TypeHardware type of the interface with which the IP is associated.
Port DuplexDuplex settings of the port ofn the network component. Possible values: Full, Half.Interface Viewer
Port LinkLink Status of the port on the network component. Possible values: Connected, Not Connected, Unknown.
Port SpeedSpeed settings of the port of the network component. Possible values:  100G, 100M, 10G, 10M, 1G, Unknown.
Port StatusStatus of the port of the network component. Possible values: Down, Unknown, Up.
VLAN NameName of the VLAN of the network component port.Device Viewer
-
> Interfaces
-
> Configuration
VLAN IDNumber of the VLAN of the network component port.
Cisco ACI Data
TenantDiscovered tenant.Device Viewer
-
> ACI
Bridge domainDiscovered bridge domain.
EPGList of comma-separated discovered endpoint groups.
VRF and BGP Data
VRF NameVRF name of IP address.Device Viewer
-
> Router
-
> VRF table
VRF DescriptionVRF description of IP address.
VRF RDVRF route distinguisher of IP address.
BGP ASBGP autonomous system number of device.Device Viewer
-
> Router
-
> BGP
Wireless Access Point Data
AP NameDiscovered name of Wireless Access Point.Device Viewer
-
> Wireless

AP IP address

Discovered IP address of Wireless Access Point.

SSIDService set identifier (SSID) associated with Wireless Access Point.

Fields related to Cisco ACI data (tenant, bridge_domain, endpoint_groups) are specific for SDN elements and controllers.

...

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:

...