Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
Testing PATROL Event Manager's Automated SNMP Traps
This task describes how to test whether automatic SNMP traps (that is those based on the BMC PATROL event manager system) are generated by BMC PATROL when a parameter changes state. They demonstrate that certain BMC PATROL Events have the send trap option turned on.
Before you begin
To generate automatic SNMP traps, at least one SNMP Manager must be registered to receive traps. A list of SNMP Managers are stored in the agent configuration variable /snmp/piV1m_list. The format is host / port / community, where the port and community string default to 162 and public, respectively.
To Test the Event Manager's Automated SNMP Traps
- Access the SNMPHealth application menu as described in Accessing KM Commands and InfoBoxes.
- Select Test PATROL SNMP System > Test SNMP Traps from PEM. BMC PATROL creates a task object entitled Test SNMP Traps from PEM. BMC PATROL writes the information to a PATROL task object (Test SNMP Traps from PEM) in the UNIX OS container.
Access the Listen for SNMP Traps task object as described in Accessing KM Commands and InfoBoxes and view the results. Your results should resemble this example:
SNMP Listen Running...- Select one of the following tests: Test PATROL SNMP System >
- Set testparm Parameter OK--test BMC PATROL standard event class 9
- Set testparm Parameter Alarm--test BMC PATROL standard event class 11
Set testparm Parameter Warn--test BMC PATROL standard event class 11
BMC PATROL changes the state of testparm in the SNMPHealth application. BMC PATROL also sends a message to the message area.
State Change Messages Based on Automated Traps
- Access the Listen for SNMP Traps task object. Your results should resemble this example, a trap for Set testparm parameter to Warn command:
2.1.2.1.2.1.2121.1.1.2.1.0 93 string Alarm #1 of global parameter 'testparm' triggered on 'SNMPHealth.SNMPHealth'. 1 <= 1.00 <= 1
2.1.2.1.2.1.2121.1.1.2.2.0 31 string /SNMPHealth/SNMPHealth/testparm
2.1.2.1.2.1.2121.1.1.2.3.0 0 string
Related topics