| 2016-10-26 06:23:02 |
Morten Brekkevold |
description |
The underlying netsnmp library supports SNMPv3. Implement support for this in NAV.
This entails, among othe things:
* Re-modeling how credentials are stored and entered into NAV via SeedDB
* SNMP version can no longer be autodetected, but must be explicitly set when adding a device. |
The underlying NET-SNMP backend supports SNMPv3. Implement support for this in NAV.
This entails, among other things:
* Re-modeling how credentials are stored and entered into NAV via SeedDB, as simple community strings will no longer suffice.
* SNMP version can no longer be autodetected, but must be explicitly set when adding a device.
* Both the synchronous and asynchronous SNMP facades of NAV must have their APIs changed to allow more complex session parameters.
* The synchronous tools snmptrapd (w/plugins), arnold, portadmin and psuwatch must be reviewed and refactored.
* We likely need to rewrite the handling of BRIDGE-MIB for Cisco equipment to use SNMPv3 contexts for switching between VLANs, as community indexing is no longer an option under v3.
* Review and refactor code that tries to verify SNMP support by checking whether a community has been set on an IP device (as this model will disappear). |
|
