Default interface expected state in 4.0
-
First new device I have added since upgrading to 4.0.
The default interface expected state is UP for every interface, leading to the node immediately going Critical due to many of the ports being down.
This device is definitely completely new, nothing has had this hostname or IP before.
I could have sworn that previously, the expected state when adding a device is the current state, ie when you add it, it is assumed to be all OK. Then any deviation from this in future causes an alarm.
Is this new behaviour in 4.x compared to 3.x? -
It should be the same logic in 4.0 - state of ports on first configuration poll should become expected state.
It's SNMP device, right? What is the model of the device? In object details -> overview what is written next to "Driver"? -
-
-
Objects.Interfaces.DefaultExpectedState is set to UP.
Documentation says default is "1". https://www.netxms.org/documentation/adminguide/appendix.html
I guess it should be AUTO? I swear I didn't change this. -
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login