Cisco Systems 4.1 Working With Conflicting Device Types

3-38
User Guide for Resource Manager Essentials 4.1
OL-11714-01
Chapter 3 Adding and Troubleshooting Devices Using Device Management
Working With Conflicting Device Types
Step 4 Select a device you want to resolve from the Alias Devices pane.
While resolving the alias state devices:
• If you have chosen to delete the device in the Alias Device state, all Syslog messages collected are
retained.
• If you have chosen to delete the device in the Normal Device state, all Syslog messages collected
are deleted.
We recommend that you delete the device in the Alias Device state and keep the device in the Normal
Device state to retain all Syslog messages.
Step 5 Click Select.
The selected device is moved to either the Normal device state or the Pre-deployed device state, based
on whether the device is reachable or not.
You can view the RME Device State using Resource Manager Essentials > Devices > Device
Management.
Working With Conflicting Device Types
The Conflicting device state occurs if the sysObjectID in the device and that in the Device and Credential
Repository do not match.
Detecting a Conflicting Device Type
The prerequisites for detecting an conflicting device are:
• The conflicting device is detected when you perform the first inventory collection for a device.
• A device is detected as an conflict device only after a successful inventory collection.
• If the inventory collection is partially successful or failed, a conflict device may be listed as a
Normal Device or as a Pre-deployed Device, based on whether the device was reachable or not.
• Devices in Conflicting Device state cannot be included in the RME workflows. You must update the
Device and Credential Repository with the correct device type so that these devices can be included
in the RME workflows.
The devices go into Conflicting Device state because the device type that you entered in the Device and
Credential Repository may be different from the device type that RME determines during inventory
collection.
In such a case, RME Device Management provides a User Interface listing the devices with the incorrect
device types. It also allows you to update the device type in the Device and Credential Repository or
delete the device and re-submit the device for management.
Conflicting Device Type Algorithm
RME detects an conflict device using this algorithm:
1. RME gets sysObjectID from Device and Credential Repository.
If the sysObjectID is null, RME updates the sysObjectID collected by Inventory collection, else go
to step 2.
2. RME compares the sysObjectID in the Device and Credential Repository with the sysObjectID
collected by Inventory application for a given device.