Chassis serial number causes Discovery to fail

[srphayre]

Hey folks.

We have Cisco UCS devices that we are discovering using SSH.,   The returned serial numbers include the Chassis serial number.   We have both the Blades and the Chassis manually entered into the CMDB however because the CMDB record for the Chassis has the serial number that the blade is returning (in the Chassis Serial Number type), it fails with the "Multiple matches were found in the CMDB" error.  

Any thoughts on how I can get over this without having to mask the serial number of the chassis in the CMDB record?

Currently using Berlin.

[doug_schulze]

You might consider tuning your identifiers so that you don't look down that tree for serial numbers for UCS devices... Trusting that you have those in their own custom table....Take a look at the Solaris blade serial number post for what I'm thinking...

[srphayre]

I think we are going to create a new class of hardware for the Chassis and code some business rules to check for chassis serial numbers being discovered and create some relationships between the devices and the chassis but let discovery continue on the device itself.

[SNFan]

Not sure if this is helpful but you can get some UCS chassis information from the associated UCS 6000 over SNMP. e.g.

iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoUnifiedComputingMIB.ciscoUnifiedComputingMIBObjects.cucsEquipmentObjects.cucsEquipmentChassisTable

[bgworld]

We had the same issue in our instance. We had asked our Server Mgmt Team to create unique serial numbers for each server. This removed duplicates creation and 'Multiple matches were found in the CMDB' issue in discovery.

Another way is to create new identifier as suggested by Doug Schulze.

You can refer to his post here: Solaris Blades