NETIM : Why do Juniper devices get merged when running Add/Discover wizard

Categories: SteelCentral NetIM
Solution Number: S33751

Issue

After clearing the OrderedIPs.txt file and performing an import of Juniper devices, the first device is imported correctly.
However, any following Juniper devices are not added as separate entities but merged into the one added before them.

Solution

This behavior occurs when the NetIM finds common IP addresses in the configuration file or collected MIB data file from the device during the import process. 
A common IP address on the devices signifies that they may the same device and hence are merged. 
However, this shouldn't occur when the OrderedIPs.txt file is cleared and only one device is added prior to the merge occurring.
The reason is that Juniper devices have the following addresses assigned to them as Martian Address (Not routable, to-be-ignored) on all devices. 

IP-MIB::ipAdEntAddr.128.0.0.1 = IpAddress: 128.0.0.1
IP-MIB::ipAdEntAddr.128.0.0.4 = IpAddress: 128.0.0.4
IP-MIB::ipAdEntAddr.128.0.0.16 = IpAddress: 128.0.0.16
IP-MIB::ipAdEntAddr.128.0.0.32 = IpAddress: 128.0.0.32
IP-MIB::ipAdEntAddr.128.0.0.127 = IpAddress: 128.0.0.127


These can be verified by checking for the list of IP addresses on the devices via the MIB_BROWSER or getting a SNMP walk.

When NetIM checks the devices for common addresses these are found.
Hence all devices discovered after the first one are merged into the first one. 

The workaround is to add these IP addresses in the   \Riverbed\NetIM\1.4.0_1058\input\AutoDiscovery\excludeFromDpiSelection.txt file.
Clear the OrderedIPs.txt file once again.
Run Add/Discover once again.

Environment

SteelCentral NetIM 1.5.x
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Last Modified: 2019-10-28
Can't find an answer? Create a case