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"?
Ubiquiti Unifi Switch USW-Pro-Aggregation, 5.76.7.13442.
Driver is GENERIC and the Unifi Switch template has been applied automatically.
Server is 4.0.2157.
I just added a new CiscoSB switch, this has the CISCO-SB driver and does the same.
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.
Yes, set to AUTO was the fix. Removed/readded a switch, behaves as expected.