Spectrum ERROR TRACE at csModel1.cc(2273)
search cancel

Spectrum ERROR TRACE at csModel1.cc(2273)

book

Article ID: 202703

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

The $SPECROOT/SS/VNM.OUT is showing the following:


SPC-SHD-29021:
**************************************************************************
The following output is intended to facilitate debugging, please forward
to CA technical support.  The files listed are not part of the customer
installation of SPECTRUM.
**************************************************************************
 
Oct 31 13:07:39 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x7035ba
Oct 31 13:07:39 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x7035ba
Oct 31 13:07:41 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x70299c
Oct 31 13:07:41 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x70299c
Oct 31 13:07:41 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x70299c
Oct 31 13:07:42 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x70299c
Oct 31 13:07:46 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x7176d8
Oct 31 13:07:46 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x7176d8
Oct 31 13:07:47 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x7176d8
Oct 31 13:07:47 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x7176d8
Oct 31 13:07:51 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x702640
Oct 31 13:07:51 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x702640
Oct 31 13:07:51 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x702640
Oct 31 13:07:51 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x702640
Oct 31 13:07:51 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x702640
Oct 31 13:07:51 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x702640
Oct 31 13:07:51 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x702640
Oct 31 13:07:51 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x702640
Oct 31 13:07:59 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x7176c6
Oct 31 13:07:59 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x7176c6
Oct 31 13:07:59 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x7176c6
Oct 31 13:07:59 ERROR TRACE at CsModel1.cc(2273): indx: 0 having attr_id: 0x3b71b04 expects type 10 but device returned type as 24 for model handle 0x7176c6

NOTE: These servers had an in place database upgrade with Spectrum 10.4.2 since new servers with supported OS were built.

 

Environment

Release : Any

DX NetOps Spectrum

Component : Spectrum Core / SpectroSERVER

Cause

Attribute ID 0x3b71b04 is for sysMultiHostCpuUsageRatio on F5 BigIP devices. The mib for sysMultiHostCpuUsageRatio is set to gauge (type 10) however the device actually responds with a 64 bit integer (Counter 64 which is type 24).

Resolution

This is benign and can be ignored as Spectrum is processing the data. It's just a message to let you know the incoming data type is not the same as what's set in the db.

 

To stop these messages from being printed you can add this line to the $SPECROOT/SS/.vnmrc file

 

type_mismatch_debug=FALSE 

 

Then stop and restart the SpectroSERVER, these messages will no longer be printed.

 

Additional Information

If you want to stop these messages, you will want to reach out to the vendor. They would need to resolve the MiB Object to match the trap alert their device is sending. 

  • Using model_handle in the error, find the model type
  • Using a new custom Locator search by Attribute, find the model type, and then search attributes on that model type for the attr_id in the error. or check attributes tab on the device.
  • Once you have the attribute name, use MiB Tools to search for which MIB file this MiB object belongs to
  • Based on timestamp of the error, you may be able to check device Events Log for what trap this came from
  • Contact the vendor to repair the MiB object and provide an updated MIB to import into MiB Tools
  • The old attribute will need to be un mapped and new mapping to the new MIB object
Powered by Wolken Software