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
Third-Party Web Scan and Test Tools Cause Sluggish
Oracle ILOM Performance (23564626)
Under certain conditions, third-party web scanning and test tools can cause Oracle ILOM to run
extremely slowly.
Workaround
Install system software release 1.7.1 or newer.
Third-Party Web Scan and Test Tools Cause Sluggish Oracle ILOM Performance (23564626)
Oracle ILOM Enhancements and Issues
73