Since upgrading from 10.2 to 10.2.1, the SpectroSERVER's cpu usage went from less than 10% to 100% and we see "CsHPSERequestSender.cc(569): SNMP send" warnings in the vnm.out.

Since upgrading from 10.2 to 10.2.1, the SpectroSERVER's cpu usage went from less than 10% to 100% and we see "CsHPSERequestSender.cc(569): SNMP send" warnings in the vnm.out.

Article Id: 6839

Status: Published

Updated On: 14-02-2018 08:14

Legacy Id: TEC1908617

Products:

CA Spectrum - OneClick , CA Spectrum - Reporting , CA Spectrum - Integrations , CA Spectrum - Alarms & Event Management

Issue/Introduction:

After upgrading we noticed errors in the vnm as below:

WARNING at CsHPSERequestSender.cc(569): SNMP send took 5114ms! Device IP: xxxxx Request ID: xxx Operation Type: 0 Community: xxx

SendRetCode: 0 usReturnCode: 0 Timeout: 3000 Device Port: 161 m_strCommunity: public

m_nVersion: 0 m_strContextName: m_nSecLevel: 0 m_nAuthProtocol: 0

m_strAuthPwd: m_nPrivProtocol: 0 m_strPrivPwd:

WARNING at CsHPSERequestSender.cc(1571): timeout mutex lock took 4835ms!

A top command shows that the CPU at 100% utilization and on closer inspection, the SpectroSERVER's SNMP listen thread, is consuming 100% CPU.

Environment:

10.2.1Systems with a single SNMP interface.

Resolution:

The patch 10.02.01.PTF_10.2.118, was built to resolve this and allow systems with a single SNMP interface, to function without issue.

Please contact support to request a copy of this patch.

As a workaround, an additional SNMP interface, can be added to the system.