Serial Number showing incorrectly in CA Spectrum 9.4.2.1 and 10.0

Document ID : KB000032879
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue: 

Serial numbers on some Cisco devices are showing multiple serial numbers all crammed into one.  For instance:
FOC1623R07D;ECL1337043X;ECL1337043X;ECL1337043X;ECL1337043X 
 
Also, this is causing mysql exceptions:
 
Jul 10, 2015 15:46:47.956 - Unable to process device entity because of a MySQL data integrity issue. This will cause unexpected results in reports. Exception: 
org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [INSERT INTO devicemodel (model_h, landscape_h, model_name, model_class, create_time, model_creator, mtype_h, security_string, IP, MAC, serial_nbr, sys_desc, fw_rev, sys_OID, location, contact_person, last_reboot, vendor, device_type, last_successful_poll, cust_asset_tag, cust_asset_ID, cust_asset_owner, cust_asset_organization, cust_asset_office, cust_asset_contractnumber, cust_asset_contractstartdate, cust_asset_contractenddate, cust_asset_description, SDM_host_address, model_key, topology_model_name_string ) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; Data truncation: Data too long for column 'serial_nbr' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'serial_nbr' at row 1 
Jul 10, 2015 15:46:47.960 - Unable to process device entity because of a MySQL data integrity issue. This will cause unexpected results in reports. Exception: 
org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [INSERT INTO devicemodel (model_h, landscape_h, model_name, model_class, create_time, model_creator, mtype_h, security_string, IP, MAC, serial_nbr, sys_desc, fw_rev, sys_OID, location, contact_person, last_reboot, vendor, device_type, last_successful_poll, cust_asset_tag, cust_asset_ID, cust_asset_owner, cust_asset_organization, cust_asset_office, cust_asset_contractnumber, cust_asset_contractstartdate, cust_asset_contractenddate, cust_asset_description, SDM_host_address, model_key, topology_model_name_string ) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; Data truncation: Data too long for column 'serial_nbr' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'serial_nbr' at row 1 
 

 

 

Environment: 

 
CA Spectrum 9.4.2.1, 10.0

 

 

Cause:

 
This behavior was introduced with "enable_stack_serialnumber"  functionality in 9.4.2.1.
When the flag "enable_stack_serialnumber" is set to true in the <SPECROOT>/SS/.vnmrc file, CA Spectrum uses the EntityMib "entPhysicalClass" table to figure out how many chassis are present.  Using all the serial numbers, CA Spectrum appends them so that the serial number attribute will have all serial numbers. This is especially applicable in stack mode.

However, CA Spectrum should restrict the serial number attribute when "enable_stack_serialnumber" is set to false or not entered in the .vnmrc.  This was not happening.
 

 

Resolution

This will be resolved in CA Spectrum release 10.1.