Hello, We have issues with NAV , using same system for several years already , since SNMP profile introduced the switch losse its Switch Type result we cannot manage it . and any new switch added with RW profile is not able to be scanned for ports and config and etc... as soon as we uncheck the RW checkbox , switch is scanned for its ports and config Please advice Thanks
On Mon, 16 Nov 2020 10:07:07 +0200 Tal Bar-Or tbaror@gmail.com wrote:
We have issues with NAV , using same system for several years already , since SNMP profile introduced the switch losse its Switch Type result we cannot manage it . and any new switch added with RW profile is not able to be scanned for ports and config and etc... as soon as we uncheck the RW checkbox , switch is scanned for its ports and config Please advice
Hi,
I think it's probably a bug in NAV.
Originally, each IP device could be configured directly with a read-only SNMP community, and a read-write SNMP community in SeedDB. NAV would use the read-only community for all read-operations, and only use the read-write community for write operations.
That way of thinking has probably been transferred onto the management profiles model - so you need both a read-only SNMP profile for the read operations, and a read-write profile for write operations.
It's likely NAV doesn't take into account the fact that an RW profile can also be used for read operations - but that is likely just a small bugfix in the code that looks for a usable SNMP profile. I would urge you to report a bug at https://github.com/Uninett/nav/issues/new/choose