In firmware versions 3.11 and above, new SNMP status and trap MIBS were created to provide more and better structured SNMP status and traps from the Opengear console servers.
There is an option in the Opengear console server SNMP menu in the UI to Use Legacy Notifications for the SNMP traps. Setting this option means the console server will send SNMP traps that are compatible with those sent in older firmware before the new MIBS were added ensuring that the firmware upgrade won't upset existing SNMP management a user will already have in place.
When upgrading from old firmware which does not support the newer SNMP mibs/traps (versions before 3.10.2) to firmware that does support the new mibs/traps:
- If the SNMP service was enabled and an SNMP manager was configured before upgrading the firmware, the console server will be configured to use the legacy traps after upgrading
- If the SNMP service was not enabled or no SNMP manger was configured before the upgrade, then the console server will be be configured to use the new SNMP traps after the upgrade (but note that this won't have any effect until the SNMP service is turned on and an SNMP manager is configured).
- When starting up in the new firmware after a config erase, the console server will be configured to use the new SNMP traps.
- When upgrading from a version of firmware that supports the new traps to a newer version that supports the new traps, the 'use legacy traps' setting should just be kept the same - no checking of snmp service/manager configuration is needed.
In summary when upgrading to the new firmware or starting up from a config erase while running the new firmware, the console server will be configured to use the new SNMP traps UNLESS you are upgrading and the SNMP service was already enabled and an SNMP manager was configured. Note that you can always configure the device to send the legacy traps when ever you need to.
The new status and trap MIBS can be copied from the console server running the new firmware or from the usual Opengear download locations.
Comments
0 comments
Article is closed for comments.