Joined: Tue Aug 11, 2009 2:19 am Posts: 7734
It just means 'invalid'. It's not necessarily an error. For example, a firewall filter rule that refers to an address list that doesn't exist is invalid and highlighted in red. That isn't an error - you can create dynamic address list entries based on RADIUS logins, for example, and the rule isn't an 'error' just because at the time you're looking no one with those properties is logged in. Same with a Hotspot associated with an interface that is considered down because it's WLAN interface that no one is connected to - the moment someone connects it stops being invalid.
It's up to you to double-check the relationship between entries that renders them invalid. For DHCP server entries the most likely case is quite simply that you're referring to an IP pool by name that doesn't exist.
_________________ Specific answers require specific questions. When in doubt, post the output of "/ip address print detail", "/ip route print detail", "/interface print detail", "/ip firewall export", and an accurate network diagram.
Joined: Fri Aug 17, 2007 7:42 am Posts: 730
It's up to you to double-check the relationship between entries that renders them invalid.
It's too bad this info isn't available. Mikrotik is obviously doing this in the background (to detect invalid state/relationship).
Maybe something like [/menu <...> get <*item> invalid-description] Something simple like: "ip pool required", "dhcp interface invalid", "address list invalid", etc...
I know there have been stupid mistakes I've made where multiple relationships might exist, and I'd have to pinpoint the exact one which was the cause. (I say stupid because being a network admin, I shouldn't have made those mistakes)
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum