Pillar Axiom: How to Generate and Test SNMP Traps

Asset ID:	1-71-2000267.1
Update Date:	2018-01-08
Keywords:

Solution Type Technical Instruction Sure

Solution 2000267.1 : Pillar Axiom: How to Generate and Test SNMP Traps

Applies to:

Pillar Axiom 600 Storage System - Version All Versions and later
Information in this document applies to any platform.

Goal

This document provides the steps to generate an SNMP trap on the Axiom 600 and trace it on a configured host, using either the GUI or the CLI.

Solution

The Simple Network Management Protocol (SNMP) trap facility can be configured on the Axiom 600 to send traps to configured hosts. Any workstation that has an SNMP-based management application installed on it can be a trap host. For further details, refer to the Pillar Axiom Administrator's Guide for your release version.

Note: The Axiom 600 also performs (GET) SNMP v2 functionality via MIB interface (not detailed here).

Configuring SNMP Using the GUI

Navigate to System > Global Settings > SNMP.
Select Actions > Create.
Enter a Name for the SNMP host.
Enter the values in the Host IP field and the Community String field to specify where the traps are directed. The community string must contain at least six characters.
Select the Receive traps option to enable the Trap Port Number field.
Enter the Trap Port Number. For SNMP traps, use port 162.
(Optional) Select the Severity threshold from the list of possible filters:
- Informational: Requires no action for events that are information only.
- Warning: Requires no immediate action for minor conditions that you can address at your convenience.
- Critical: Requires prompt action to prevent system failures or offline conditions.
Click OK.

Configuring SNMP Using AxiomCLI

For details, refer to the Pillar Axiom CLI Reference Guide for your release version.

Syntax:

snmp_host { [ ‑add | ‑delete | ‑list | ‑modify ] | [ ‑usage | ‑help ] }

Example:

$ axiomcli snmp_host ‑add ‑name snmp_trap_server_1 ‑ip 192.168.10.5 ‑community public ‑trapPort 162 ‑trapEvent warning

Generating a Test Trap

Any add, delete, or modify of the SNMP settings will send a trap to a configured SNMP host. On the host, trace on the configured UDP port (usually 162). Examples are shown below for Solaris and Linux.

Note: Ensure your snoop or tcpdump is monitoring on the required physical network interface.

On Solaris use snoop. For example:

# snoop -x0 udp port 162

ax600-pilot1 -> myhost-a-dom00 UDP D=162 S=44825 LEN=265

48: 0406 7075 626c 6963 a781 f002 0100 0201 ..public........
64: 0002 0100 3081 e430 1006 082b 0601 0201 ....0..0...+....
80: 0103 0043 0419 462f b130 1906 0a2b 0601 ...C..F/.0...+..
96: 0603 0101 0401 0006 0b2b 0601 0401 f93c .........+.....<
112: 0204 0270 3010 060b 2b06 0104 01f9 3c02 ...p0...+.....<.
128: 0401 0102 0101 3010 060b 2b06 0104 01f9 ......0...+.....
144: 3c02 0401 0202 0103 3013 060b 2b06 0104 <.......0...+...
160: 01f9 3c02 0401 0302 0455 2e5f 4a30 2006 ..<......U._J0 .
176: 0b2b 0601 0401 f93c 0204 0104 0411 534e .+.....<......SN
192: 4d50 5f48 4f53 545f 4352 4541 5445 4430 MP_HOST_CREATED0
208: 5a06 0b2b 0601 0401 f93c 0204 0105 044b Z..+.....<.....K
224: 3c45 7665 6e74 5061 7261 6d65 7465 7273 <EventParameters
240: 3e3c 6166 6665 6374 6564 4974 656d 4651 ><affectedItemFQ
256: 4e3e 2f74 6573 743c 2f61 6666 6563 7465 N>/test</affecte
272: 6449 7465 6d46 514e 3e3c 2f45 7665 6e74 dItemFQN></Event
288: 5061 7261 6d65 7465 7273 3e Parameters>

On Linux use tcpdump. For example:

# tcpdump -vv udp port 162

12:55:05.418770 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 210)
192.168.10.5.44825 > myhost-a.snmptrap: [udp sum ok] { SNMPv2c { V2Trap(240) R=0 system.sysUpTime.0=439871257 S:1.1.4.1.0=E:15548.2.4.2.112 E:15548.2.4.1.1=1 E:15548.2.4.1.2=3 E:15548.2.4.1.3=1429260822 E:15548.2.4.1.4="SNMP_HOST_CREATED" E:15548.2.4.1.5="<EventParameters><affectedItemFQN>/test</affectedItemFQN></EventParameters>" } }

Attachments

This solution has no attachment