Before You Begin
To create or edit alert rules in Oracle ILOM, you need the Admin (a) role enabled.
For you to define an SNMP v3 trap alert, the SNMPv3 user name must be defined in Oracle ILOM. If the SNMP v3 user name is not defined in Oracle ILOM, the SNMP v3 user receiving the SNMP alert will not be able to decode the SNMPv3 alert message. For more information about defining SNMPv3 authorization and SNMP v3 users in Oracle ILOM, see Managing SNMP User Accounts and SNMP Trap Alerts (CLI).
For additional information about configuring alert management settings in Oracle ILOM, refer to Configuring Alert Notifications in Oracle ILOM Administrator’s Guide for Configuration and Maintenance Firmware Release 4.0.x.
To configure the destinations to which the SNMP traps are sent, follow these steps:
-> show /SP/alertmgmt/rules/1 /SP/alertmgmt/rules/1 Targets: Properties: type = snmptrap level = disable destination = 0.0.0.0 destination_port = 0 community_or_username = public testrule = (Cannot show property) Commands: cd set show
-> cd /SP/alertmgmt/rules
-> cd /SP/alertmgmt/rules -> show /SP/alertmgmt/rules Targets: 1 2 . . . 15 Properties: Commands: cd show
Choose a rule (from targets 1 through 15) for which you would like to configure a destination for SNMP traps, and go to that directory.
-> cd 4
For example, to set a rule to send critical traps to a management client using SNMP v2c using a community name of “public”, enter:
-> set type=snmptrap level=critical destination=IPaddress_of_snmp_management_station destination_port=port snmp_version=3c community_or_username=public