When I first discovered and polled these particular switches (cisco and edgeswitch) the Ports that were down were not showing up on the device_status_boxes. Which is what I expected.
But today the equipment at that site was power cycled when we switched over to generator backup while the electricians hooked up the new auto switch over equipment for the new permanent backup generator.
Since then device_status_boxes shows all the down ports and that the devices rebooted.
So they will not go away. Other software I used in the past had a mechanism to acknowledge them and they would go away. I can find no such mechanism here to clear these unused ports etc.
It has almost eight hours and they are still there
What am I doing wrong?
device_status_boxes is legacy and not really intended to be used these days.
But the original intention of that module was to show all devices which had rebooted in the past 24 hours, and all ports which are down but not disabled.
There was no ability to "acknowledge" a status, since this module pre-dates this sort of configurability (and down-but-not-disabled ports are not something anyone should have in any great number)
But now that module is deprecated, so... :)
adam. On 2018-02-27 23:48:34, Art Stephens astephens@ptera.com wrote: When I first discovered and polled these particular switches (cisco and edgeswitch) the Ports that were down were not showing up on the device_status_boxes. Which is what I expected.
But today the equipment at that site was power cycled when we switched over to generator backup while the electricians hooked up the new auto switch over equipment for the new permanent backup generator.
Since then device_status_boxes shows all the down ports and that the devices rebooted.
So they will not go away. Other software I used in the past had a mechanism to acknowledge them and they would go away. I can find no such mechanism here to clear these unused ports etc.
It has almost eight hours and they are still there
What am I doing wrong? --
Arthur Stephens Senior Network Administrator Ptera Inc. PO Box 135 24001 E Mission Suite 50 Liberty Lake, WA 99019 509-927-7837
ptera.com [http://ptera.com] | facebook.com/PteraInc [http://facebook.com/PteraInc] | twitter.com/Ptera [http://twitter.com/Ptera] ----------------------------------------------------------------------------- "This message may contain confidential and/or propriety information, and is intended for the person/entity to whom it was originally addressed. Any use by others is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company."
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Ok so it times out in 24 hours. That is Ok with me. Funny that the default install would have a legacy and not really intended module.
Was / is it bring replaced by some thing as good as or better?
Thanks
On Tue, Feb 27, 2018 at 3:55 PM, Adam Armstrong adama@observium.org wrote:
device_status_boxes is legacy and not really intended to be used these days.
But the original intention of that module was to show all devices which had rebooted in the past 24 hours, and all ports which are down but not disabled.
There was no ability to "acknowledge" a status, since this module pre-dates this sort of configurability (and down-but-not-disabled ports are not something anyone should have in any great number)
But now that module is deprecated, so... :)
adam.
On 2018-02-27 23:48:34, Art Stephens astephens@ptera.com wrote: When I first discovered and polled these particular switches (cisco and edgeswitch) the Ports that were down were not showing up on the device_status_boxes. Which is what I expected.
But today the equipment at that site was power cycled when we switched over to generator backup while the electricians hooked up the new auto switch over equipment for the new permanent backup generator.
Since then device_status_boxes shows all the down ports and that the devices rebooted.
So they will not go away. Other software I used in the past had a mechanism to acknowledge them and they would go away. I can find no such mechanism here to clear these unused ports etc.
It has almost eight hours and they are still there
What am I doing wrong?
Arthur Stephens Senior Network Administrator Ptera Inc. PO Box 135 24001 E Mission Suite 50 Liberty Lake, WA 99019 509-927-7837 <(509)%20927-7837> ptera.com | facebook.com/PteraInc | twitter.com/Ptera
"This message may contain confidential and/or propriety information, and is intended for the person/entity to whom it was originally addressed. Any use by others is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company." _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/ cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
The functionality of notifying for down ports was never really replicated, since all it ever created was a disproportionate number of people people moaning about some minor aspect of it.
Everything else was replaced by the alerting system. You could replicate alerting on down ports with that, but you probably shouldn't.
adam. On 2018-02-28 00:12:31, Art Stephens astephens@ptera.com wrote: Ok so it times out in 24 hours. That is Ok with me. Funny that the default install would have a legacy and not really intended module.
Was / is it bring replaced by some thing as good as or better?
Thanks
On Tue, Feb 27, 2018 at 3:55 PM, Adam Armstrong <adama@observium.org [mailto:adama@observium.org]> wrote:
device_status_boxes is legacy and not really intended to be used these days.
But the original intention of that module was to show all devices which had rebooted in the past 24 hours, and all ports which are down but not disabled.
There was no ability to "acknowledge" a status, since this module pre-dates this sort of configurability (and down-but-not-disabled ports are not something anyone should have in any great number)
But now that module is deprecated, so... :)
adam. On 2018-02-27 23:48:34, Art Stephens <astephens@ptera.com [mailto:astephens@ptera.com]> wrote: When I first discovered and polled these particular switches (cisco and edgeswitch) the Ports that were down were not showing up on the device_status_boxes. Which is what I expected.
But today the equipment at that site was power cycled when we switched over to generator backup while the electricians hooked up the new auto switch over equipment for the new permanent backup generator.
Since then device_status_boxes shows all the down ports and that the devices rebooted.
So they will not go away. Other software I used in the past had a mechanism to acknowledge them and they would go away. I can find no such mechanism here to clear these unused ports etc.
It has almost eight hours and they are still there
What am I doing wrong? --
Arthur Stephens Senior Network Administrator Ptera Inc. PO Box 135 24001 E Mission Suite 50 Liberty Lake, WA 99019 509-927-7837 [tel:(509)%20927-7837]
ptera.com [http://ptera.com] | facebook.com/PteraInc [http://facebook.com/PteraInc] | twitter.com/Ptera [http://twitter.com/Ptera] ----------------------------------------------------------------------------- "This message may contain confidential and/or propriety information, and is intended for the person/entity to whom it was originally addressed. Any use by others is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company."
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
--
Arthur Stephens Senior Network Administrator Ptera Inc. PO Box 135 24001 E Mission Suite 50 Liberty Lake, WA 99019 509-927-7837
ptera.com [http://ptera.com] | facebook.com/PteraInc [http://facebook.com/PteraInc] | twitter.com/Ptera [http://twitter.com/Ptera] ----------------------------------------------------------------------------- "This message may contain confidential and/or propriety information, and is intended for the person/entity to whom it was originally addressed. Any use by others is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company."
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Ok Thanks - I have not dived into that part of the program yet.
On Tue, Feb 27, 2018 at 4:15 PM, Adam Armstrong adama@observium.org wrote:
The functionality of notifying for down ports was never really replicated, since all it ever created was a disproportionate number of people people moaning about some minor aspect of it.
Everything else was replaced by the alerting system. You could replicate alerting on down ports with that, but you probably shouldn't.
adam.
On 2018-02-28 00:12:31, Art Stephens astephens@ptera.com wrote: Ok so it times out in 24 hours. That is Ok with me. Funny that the default install would have a legacy and not really intended module.
Was / is it bring replaced by some thing as good as or better?
Thanks
On Tue, Feb 27, 2018 at 3:55 PM, Adam Armstrong adama@observium.org wrote:
device_status_boxes is legacy and not really intended to be used these days.
But the original intention of that module was to show all devices which had rebooted in the past 24 hours, and all ports which are down but not disabled.
There was no ability to "acknowledge" a status, since this module pre-dates this sort of configurability (and down-but-not-disabled ports are not something anyone should have in any great number)
But now that module is deprecated, so... :)
adam.
On 2018-02-27 23:48:34, Art Stephens astephens@ptera.com wrote: When I first discovered and polled these particular switches (cisco and edgeswitch) the Ports that were down were not showing up on the device_status_boxes. Which is what I expected.
But today the equipment at that site was power cycled when we switched over to generator backup while the electricians hooked up the new auto switch over equipment for the new permanent backup generator.
Since then device_status_boxes shows all the down ports and that the devices rebooted.
So they will not go away. Other software I used in the past had a mechanism to acknowledge them and they would go away. I can find no such mechanism here to clear these unused ports etc.
It has almost eight hours and they are still there
What am I doing wrong?
Arthur Stephens Senior Network Administrator Ptera Inc. PO Box 135 24001 E Mission Suite 50 Liberty Lake, WA 99019 509-927-7837 <(509)%20927-7837> ptera.com | facebook.com/PteraInc | twitter.com/Ptera
"This message may contain confidential and/or propriety information, and is intended for the person/entity to whom it was originally addressed. Any use by others is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company." _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi -bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Arthur Stephens Senior Network Administrator Ptera Inc. PO Box 135 24001 E Mission Suite 50 Liberty Lake, WA 99019 509-927-7837 <(509)%20927-7837> ptera.com | facebook.com/PteraInc | twitter.com/Ptera
"This message may contain confidential and/or propriety information, and is intended for the person/entity to whom it was originally addressed. Any use by others is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company." _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/ cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (2)
-
Adam Armstrong -
Art Stephens