after updating our CheckMK enterprise version to 2.2.0p12, i am not receiving an CRIT state for the interfaces that changes their operational state anymore.
well, before this version, the service state is OK whatever its initial interface OPerational state (UP or Down), the state becomes CRIT, if the OPerational state has been changed.
NOW, the interface changes its operational state, but the service state still OK, and this is very problematic in terms of monitoring.
does anybody have an idea, what is changed? and how we could get it to the old situation
Hi @hdemachk and welcome to the forum!
A Checkmk upgrade should not have caused this, and I think you know about Network Monitoring with Checkmk: 3 rules to rule them all | Checkmk. So I would ask you do double-check the relevant rules, especially “Network interfaces and switch ports”. Maybe you can share the rules here, if you do not catch an obvious error.
Well, in the attachments you will find the "Network interfaces and switch port " rule + the config of the device that i am testing + the service state ( before and after the cable unplugg)
i have reviewed the links you shared here, i did not find the clue unfortunitally.
The task is to go back to the initial status that we had, it is to have a CRIT state whenever any
interface change its operational state in both cases (UP>Down & Down>UP).
Do you think you should then uncheck ignore operational state? Because having that enabled with ignore the up and down changes. I enable that solely for that purpose on some switches.
Hi @bbinder,
thank you for your intervention.
unfortunately, even after uncheck “operational state”, we got no change,
uncheck “ignore operational state” alone will force us to choose an OK status, which is not our requirement
I re-read this line and now I get what you’re after. Like freezing the state of everything as it is right now, and then if anything changes, it would cause a CRIT, right? I’m not sure that I’ve ever done such a thing before. How many interfaces are we talking about in total that require this?
@bbinder exactly as you described, the functionality was like that, but it has been change for unknown reason
we will have at the end more than 50,000 interfaces (switches, routers, Firewalls )
Hi @bbinder,
the problem is solved after unchecking the “operational state”, however we need to reset the state of the interfaces, that discovered different at the beginning.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.
