After upgrading to Spectrum 10.0, you may notice that the Interface In load threshold values are not showing the correct values. The value is greater than 100% which is not correct.
This problem occurs after a fresh Install of Spectrum 10.0 or even after upgrading from a earlier release of Spectrum.
Check the associated 0x10d80 event for this Alarm and you should notice that the 64Bit and 32 Bit counters are wrapping around and that is causing the issue. The "ifInOctets" is used for 32bit counter and "ifHCInOctets" is used for 64bit Counter. You should see something similar to below:
Problem detected with data in the Interface Performance Calculations
SOURCE DATA ************************************
Initial X_IN_OCTETS: 1207461384790
Final X_IN_OCTETS: 575859985
External AttrID = 0x10e41 (ifInOctets)
External Value (32bit) = 3085160267
External AttrID = 0x11f65 (ifHCInOctets)
External Value (64bit) = 436876857163
The 0x10d80 event basically shows the user what data was used to compute load, load in and load out. Out of the box, when CA Spectrum initially models a device, CA Spectrum tests which counters (32 and 64 bit) a ports supports. It also checks when the model is reconfigured and once every 24 hours. If a port supports a 64 bit counter, CA Spectrum will use the 64 bit counter when computing load, load in and load out.
This is a known issue identified as bug WI 374889 and has been fixed via patch 10.00.00.D06. This would be included in Spectrum 10.1 and 9.4.4 Releases.
Please contact CA Support for any further information.