Sep 16, 2011 11:29 PM
Production state "Decommissioned" still ping - Zenoss 3.2.0
-
Like (0)
Hi,
I run Zenoss 3.2. In a device class, I have some decommissioned devices. Some never been active and never been modeled. One other once been active and collected some RRD, etc.
Even "decommissioned", the one with history still raises red flag on the device. However, the one with no data work as expected. Is this a know issue in 3.2?
Thanks
Well, I though I would at least get an acknoledgment here...
According to many threads I read, the fact of setting a device to "Decommissioned" is supposed to stop pinging status and report red flags. Not only a set the device to "Decommissionned" but also set to zPingMonitorIgnore to "true" and still get red flags on this device.
In the meantime, I deleted the device since it was polluting the overall health figure of our infrastructure.
This doesn't seem to be a known issue. Can you open a ticket on this?
http://dev.zenoss.com/trac/wiki/HowToAddTicket
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
Eric -
After you set the state to decommisioned did you restart zenhub and zenping (or all of the daemons to be sure)? The collectors don't necessarily pickup those kind of changes right away.
--Dennis
Dennis, I knew that zenping may be slow to detect changes in configuration, but my device been decommissioned for 3 or 4 days before I decided to raise the flag. After this delay, I would have assumed that zenping woke-up and see something new.
Anyways, I not only restarted some Zen services without any improvement.
I'm willing to open a ticket. I primarily wanted to poll the folks to see if someone is successfully dealing with this feature with Zenoss Core 3.2.0.
Will try one or two other things and open a ticket.
Thanks to all.
Eric,
Form the device status screen try 'push config'. I'm curious if that will have any effect.
Thanks!
--Shane
I did a push config and this seemed to help. Thank you
Eric:
Glad it worked.
Best,
--Shane
What does push config do?
mwcotton:
Notifies daemons of configuration changes.
Hi folks, so if I got it right, the right way to decommission a device via api calls is:
setProductionState()
pushChanges()
right?
Few questions though:
- I did decommission a device and pushed changes, but Device Status still says "UP", what does it mean?
- what about collected data and events for decommissioned devices? will they still be available for the future?
Thanks
The Device Status of "Up" doesn't really mean anything for a decommissioned device.
The history of events and performance data will still be there for a decommissioned device as long as you don't delete the device. I *think* the RRD files (performance data) may eventually get cleaned up since they won't have been modified for a certain length of time but I am not 100% sure on that.
--Dennis
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||