SRM Error in tomcat log NumberFormatException for lineCardUpdate

Products

• Spectrum
• Network Observability

Issue/Introduction

The following error shows in the tomcat log noting AssetManager.lineCardUpdate:

Jun 05, 2020 22:06:05.806 - SRM/DeviceModelPoll/updates: Error invoking job (com.aprisma.spectrum.app.repmgr.dc.asset.DevicePoller$UpdateDeviceInfo@36de2837) : java.lang.NumberFormatException: For input string: "UCAM (96U) SPARE"

        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)

        at java.lang.Long.parseLong(Long.java:589)

        at java.lang.Long.parseLong(Long.java:631)

        at com.aprisma.spectrum.app.repmgr.dc.asset.AssetManager.lineCardUpdate(AssetManager.java:1304)

        at com.aprisma.spectrum.app.repmgr.dc.asset.AssetManager

Environment

DX NetOps Spectrum, all Releases
Component : Spectrum Reporting

Cause

Device firmware problem.

Resolution

Spectrum will read the Entity Mib and pass through all the entries and parse each one by tokenizing on ';'.
It is expecting the Physical class and physicalContainedIn as a numeric value (Long). The positions for these are 5 and 6 (starting from 0)
For some entries, these values are missing or overwritten or some extra index is added to it.

This would be an enhancement to have this changed as this is a device issue. If it were correctly set on the device the exceptions would not show. Broadcom is not going to code around this as the devices need to be fixed and this would cause too much risk in the Spectrum code.