Go to main content

Oracle® Server X6-2 Product Notes

Exit Print View

Updated: July 2020
 
 

Oracle ILOM SNMP v3 traps are not delivered after SNMP engine ID change

Bug ID 23634048

Issue: If you change the engine ID, create an SNMP v3 user, and configure an alert using that user without waiting approximately 10 seconds between each action, the internal user configuration might be incorrect and traps are missed.

Affected hardware and software: Oracle Server X6-2

Workaround: Do not create multiple configuration changes without verifying the effect of each configuration change. To prevent misconfigured users and missed traps, insert sleep statements in the script. For example:

# change engineID
set /SP/services/snmp engineid=NEWENGINEID
# sleep 10 seconds to give snmp enough time to make the change
sleep 10
# verify engineID
show /SP/services/snmp engineid
# verify SNMPv3 users have been deleted
show /SP/services/snmp/users

# create snmpv3 user
create /SP/services/snmp/users newuser authenticationpassword=...
# sleep 10 seconds to give snmp enough time to make the change
sleep 10
# verify user
show /SP/services/snmp/users newuser
# do a snmpget with that user to verify it

# configure alert
set /SP/alertmgmt/rules/1 type=snmptrap ...
# sleep 10 seconds to give snmp enough time to make the change
sleep 10
# verify alert
show /SP/alertmgmt/rules/1
set /SP/alertmgmt/rules/1 testrule=true