Alert Management Configure SNMP Trap Settings
Use this window to view and configure SNMP traps in Server Administrator. Configure SNMP trap settings by selecting a component or event to which the setting is to be applied, and then by selecting the severities for which you want to be notified.
User Privileges
Selection | View | Manage |
Alert Management: Configure SNMP Trap Settings | User, Power User, Administrator, Elevated Administrator (Linux only) | Power User, Administrator, Elevated Administrator (Linux only) |
SNMP Test Trap
The SNMP Test Trap sends the test trap to the destination on selection from the list of configured trap destination. This feature is available for users having Administrative privileges. The Server Administrator SNMP component should be installed for sending the test trap. The administrator should configure in the OS SNMP service or configuration file to get the list of trap destinations.
Enable SNMP Traps
The Enable SNMP Traps window allows you to configure settings for a component using a check box and radio button. Selecting a radio button makes the appropriate check-box state change, whereas deselecting the radio button also changes the appropriate check-box state.
You can enable or disable an SNMP trap associated with a system component by event severity. Components generate three types of events:
- Informational
- Warning
- Critical/Failure
You can configure event severity levels for the following components or events:
- Batteries
- Power Supplies
- Redundancy
- Temperature Probes
- Fan Probes
- Fan enclosures
- Voltage Probes
- Logs
- Memory
- Chassis Intrusion
- System Power
- System Peak Power
- Removable Flash Media
Components are categorized into groups with a parent-child relationship. For example, all of the components such as fans, power supplies, memory, CPU, and so on, are children of the system. Any configuration at the system level impacts the individual components beneath it. If you change the system settings to disable informational events and enable warning and critical events, this setting would be assumed for all of the components beneath system.