Management Lost alerts on Power Supply models.

Products

• CA Spectrum

Issue/Introduction

MANAGEMENT AGENT LOST alarms asserted on for Aros NetmanPlus UPS device models but the device responds to SNMP successfully. Adjusting the DCM time out, retry or throttle activation and throttle count (even as low as 1) did not influence the behavior in any way. A sniffer  trace clearly shows an snmp response from the device but is ignored by Spectrum.  

When sapwalk is run on the device, there are LEXORDER errors seen in the results:

#ERROR:LEXORDER:1.3.6.1.2.1.1.1.0 , OctetString , NetMan 100 plus
#ERROR:LEXORDER:1.3.6.1.2.1.1.2.0 , ObjectID , 1.3.6.1.4.1.5491.6
#ERROR:LEXORDER:1.3.6.1.2.1.1.3.0 , TimeTicks , 00 hrs: 00 min: 00 sec
#ERROR:LEXORDER:1.3.6.1.2.1.1.4.0 , OctetString ,
#ERROR:LEXORDER:1.3.6.1.2.1.1.5.0 , OctetString , <deviceName>
#ERROR:LEXORDER:1.3.6.1.2.1.1.6.0 , OctetString , <deviceLocation>
#ERROR:LEXORDER:1.3.6.1.2.1.1.7.0 , NULL , NULL
#ERROR:LEXORDER:1.3.6.1.2.1.2.2.1.6 , OctetString , <ifPhysAddress>

Environment

Release:
Component:

Cause

In the sniffer trace, when Spectrum requests the sysUpTime, the device responds with a value larger than 4294967296 which is greater than the max allowed value for sysUpTime with SNMP v1.  As a result of this non compliant SNMP v1 value,  Spectrum rejects the returned value and Sapwalk has a LEXORDER error beside the returned value.

Resolution

Configure the device with an SNMPv2 community string and update the "SNMP Community String" field in the "CA Spectrum Modeling Information" subview in the Information tab of the model.

For example, if the v2 community string is "public", enter "#v2/public" in the "SNMP Community String" field.

NOTE: Rebooting the device does not initialize the sysUpTime and looking at the devices internal clock we see other unusual behavior such as a current date of 2054.  Please discuss any such incidents with the vendor to get a solution to this device problem.