ViPR SRM | Watch4net : sysUpTime.0 not processed because the value's timestamp is older than the last one
search cancel

ViPR SRM | Watch4net : sysUpTime.0 not processed because the value's timestamp is older than the last one

book

Article ID: 332803

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Data Domain Is missing most of the reports and the following errors can be found in the SNMP collector logs

WARNING -- [2017-01-05 09:14:58 EST] -- AvailabilityFilter::processUpTime(): 'sysUpTime1.atlr2-dd-0031.place.com.sysUpTime.0' not processed because the value's timestamp is older than the last one! (last timestamp:1483625698, new timestamp:1483625698).
WARNING -- [2017-01-05 09:14:58 EST] -- AvailabilityFilter::processUpTime(): 'sysUpTime1.atlr2-dd-2077.place.com.sysUpTime.0' not processed because the value's timestamp is older than the last one! (last timestamp:1483625698, new timestamp:1483625698).

Environment

VMware Smart Assurance - Watch4Net/M&R

Resolution

  1. Discover capabilities for all the affected Data Domains.
  2. Distribute them to enabled collectors.
  3. Lastly, send the Generated Configurations File to collectors