You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe we can add following capabilites to be more precise (I'm not sure how it should work now)
LOWER_UP = Driver signals L1 up (since Linux 2.6.17)
RUNNING = Resources allocated
UP = Interface is running
NO-CARRIER = IF (UP is set) AND (RUNNING is not set)
This issue seems particularly old, but @e3k can you tell us if Quentin's answer helps you to better understand the --critical-status option and how to use it to meet your needs ?
Hi Lucie, it has been a while... Currently i have no more access to the system but if i recall it correctly the problem was that "admin down" devices were considered as a critical status. I opened this one maybe as a question "how to ignore admin down devices". But it also might be feature request.
Yeah it's true that the question is very old ^^, but I would like to be able to determine if the plugin as it is designed can answer it. I'm not sure I'll be able to correctly make the link between "admin down" and the statuses explained by Quentin above. Particularly without having been able to test myself on "admin down" data sample to see/check the value of the $state variable.
lucie-dubrunfaut
changed the title
os::linux::local::plugin --mode traffic Ignore administative down interfaces
[os::linux::local::plugin] mode(traffic): Ignore administative down interfaces
Dec 13, 2024
hi is it possible with linux local plugin in mode traffic to ignore the state of interfaces which are administratively put down?
i have found only the option:
--critical-status
Set critical threshold for status (Default: '%{status} ne
"RU"'). Can used special variables like: %{status}, %{display}
but no real doc that would explain how to achieve ignoring of the admin down interfaces.
is it possible with the current plugin or would this be a new feature request?
The text was updated successfully, but these errors were encountered: