Hi Robert,
yah, that was added recently, but now I removed this statuses for Cisco devices.
Try rediscover after update to r10011.
Robert Williams via observium wrote on 09/09/2019 16:13:
Hi, After no issues for ages, rather like busses, these things seem to come along at the same time!... Following a svn up earlier today to ensure we had the latest version (for a storage/snmp issue) – we now seem to have gained some sensors which are in alarm state on every single 6500 chassis. I have a really vague memory of hitting this before, like many years ago, but can’t quite put my finger on it. It seems to be picking up all these new sensors (which is fine) - but one of them (clock 2 ‘clock-inuse’) should probably be considered “false=happy” and “true=alert” – (because that means clock 1 has failed). If it helps, the new ones are all within ENTITY-SENSOR-MIB as shown above (and not CISCO-ENTITY-SENSOR-MIB which are the original ones). Some are also duplicates it seems. So, is it possible to flip the true/false alert-ness around for this Clock 2 one? Cheers! Robert Williams Custodian Data Centres https://www.CustodianDC.com
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
