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.
...
Configuring IPAM Sync
This section describes the following:
...
Data Field in IPAM Sync Export File | NetMRI Model->Attribute | Field Description | |||
|---|---|---|---|---|---|
| General Device Data | |||||
ip_address | A valid IPv4 addressDevice -> DeviceIPDotted. Required. | ||||
| ip_address | 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_timestampDevice -> DeviceFirstOccurrence | Timestamp of the first time the discoverer has seen the device. A UTC timestamp. Optional | ||||
netbios_name<none> | The NETBIOS NetBIOS name of device. String Type. Maximum size is 15 characters. Optional. | ||||
os | Device -> DeviceVersion | The OS of the IP. String Type. Maximum size is 256 characters. Optional.network | |||
| device_ | component_typeDevice -> DeviceType | The type of component connected to the IP. Eg Switch, Router, Other. Optional. String type. Max size 32. | network_component_name | Device -> DeviceNamemodel | The model of device. |
| device_vendor | The vendor of device. | ||||
| device_location | The location of device. | ||||
| device_contact | The contact of device. | ||||
| oui | The OUI of device. | ||||
| Attached Device Data (only for endhosts) | |||||
network_component_type | The type of component connected to the IP. Eg Switch, Router, Other. Optional. String type. Max size 32. | ||||
network_component_name | Name of component connected to the IP. Optional. String type. Max size 64. | ||||
network_component_ description | Device -> DeviceSysDesc | Description of component connected to the IP. Optional. String type. Max size 256. | |||
network_component_ip | Device -> DeviceIPDotted | IP address of component connected to the IP. Optional. String type. IPv4 address format. IPv4 address format. | |||
| network_component_model | The model of component connected to the IP. | ||||
| network_component_vendor | Vendor of component connected to the IP. | ||||
| network_component_location | Type of component connected to the IP. | ||||
| network_component_contact | Contact of component connected to the IP. | ||||
network_component_port_ numberInterface -> SwitchPortNumber | Port number on the component connected to the IP. Optional. Unsigned integer type. Range 0 - 9999. | ||||
network_component_port_ name | Interface -> ifName | Port name on the component connected to the IP. Optional. String type. Max size 64. | |||
network_component_port _description | Interface -> ifDescr | Description of the Port on the component connected to the IP. Optional. String type. Max size 256. | |||
| Port Data | |||||
port_vlan_nameVlan -> VlanName | Name of the Vlan on the Port. Optional. String type. Max size 64. | ||||
port_vlan_description | <none> | Description of the port Vlan. Optional. String type. Max size 256. | port_vlan_numberVlan -> VlanIndex | Port Vlan Number. Optional. Unsigned integer type. Range 0 - 9999. | |
port_speedInterface -> ifSpeed | Speed settings on the switch port. Optional. String type. Valid values are 10M, 100M, 1G, 10G, 100G, and Unknown. | ||||
port_duplex | Interface -> ifDuplex | 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 -> ifOperStatus | Connected or not. Optional. String type. Valid values are: Connected, Not Connected, and Unknown. | discovered_name | Device -> DeviceDNSName | DNS name of the IP. Optional. String Type. Max size 256.|
| Cisco ACI Data | |||||
| VRF and BGP data | |||||
Overlay/Overwrite Logic
The following overlay/overwrite logic applies to IPAM Sync, complete the following:
- 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 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
The following table helps to locate IPAM Sync discovered data in the NetMRI UI.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
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:
...