Monitoring the Physical Appliance Health via SNMP Traps
search cancel

Monitoring the Physical Appliance Health via SNMP Traps


Article ID: 42938


Updated On:


STARTER PACK-7 CA Rapid App Security CA API Gateway



Setting up SNMP Traps on x4170 ILOM

Section 1: Setting the SNMP service state and properties.

1. Log in to the Oracle ILOM web interface.
2. Click Configuration --> System Management Access --> SNMP.?The SNMP Settings page appears.
3. To enable the SNMP port, click the State check box.?When State is disabled, the SNMP port is blocked, prohibiting all ?SNMP communication between?Oracle ILOM and the network.
4. In the Port text field, type the port number. This is the listen port for your monitoring agent.
5.?Leave the Engine ID field blank. This allows the default setting to be used. The engine ID is automatically set by the SNMP agent. While you can use this field to set the engine ID, you should leave this field blank. The engine ID uniquely identifies the SNMP engine and enables users to query the SNMP agent. You should use this field to set the engine ID only if you are familiar with SNMP v3 security and how this setting is used.
6. To enable or disable the Set Requests option, select or clear the Set Requests check box. If the Set Requests option is disabled, all SNMP objects are read-only and no snmpset commands will be processed. Enable this as you see fit.
7. To enable SNMP v1, v2c, or v3, click a Protocols check box. SNMP v3 is enabled by default. You can enable or disable v1, v2c, and v3 protocol versions. The Gateway uses v2c for most requests, however this is communication between your monitoring agent and the hardware so set this as your see fit in coloration with your monitoring agent.
8. Click Save.

Section 2: Manage SNMP Trap Alerts

1. Log in to the Oracle ILOM web interface.
2. Click Configuration --> Alert Management. The Alert Settings page appears. This page shows a table of the alerts that you can configure. You?can configure up to 15 alerts.
3. To create or modify an alert, click the alert radio button.
4. From the Actions drop-down list, select Edit. The Create or Modify Alert dialog appears.
5. In the Level drop-down list, select the level of the alert. The lower the level, the more verbose you logs will be.
6. In the Type drop-down list, select the alert type. You will want to set this to SNMP.
7. In the IP Address field, specify the alert destination IP address for your SNMP Monitoring Agent.
8. For the SNMP Version, choose the version you would like to support
9. Click Save for your changes to take effect.

Section 3: Testing Traps

1. After creating an alert, select the radio button next to your alert, and click "Test Rule." This will send?out a trap message to the destination server.
2. If the trap is successful, on the destination server you should see a log entry that looks similar to this output:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (14373) 0:02:23.73 SNMPv2-
MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises. SNMPv2-
SMI::enterprises. = "" SNMPv2-SMI::enterprises. =
STRING: "1050FMM0E2" SNMPv2-SMI::enterprises. = STRING: "SUN FIRE
X4170 M2 SERVER" SNMPv2-SMI::enterprises. = STRING: "This is a test trap"



Component: APIGTW

Attachments get_app