Top
ETERNUS SF Storage Cruiser V16.9 Operation Guide
FUJITSU Storage

5.3 Checking SNMP Trap Settings

With the following methods, check whether SNMP Trap monitoring is set up correctly in the device that supports the SNMP Trap monitoring for fault management. Refer to "1.1 Support Levels" for the devices that support SNMP Trap monitoring.

[Test 1] Check Whether Every Device (Excluding Server Node Agent) Can Correctly Receive SNMP Traps

This software receives generic traps 0 to 5, which are SNMP Traps not unique to a specific vendor, and it decodes their contents and displays information about each event (that does not use Systemwalker Centric Manager linkage or Shell/bat linkage.) As one of generic traps 0 to 5, a COLD START trap is issued by an ordinary device. When using this trap to test whether the software can correctly receive an SNMP Trap.

A device sends the COLD START trap and other traps by turning OFF and ON the device to be managed, performing a variety of setup tasks (setup of the SNMP environment for ETERNUS), doing other such work. Check whether the event is displayed with regard to the above operation and trap.

However, generic traps 0 to 5 are not normally required, so after the test is completed, you can disable display of generic traps 0 to 5 by using the following method:

Edit the following definition file:

Platform of Manager

File Location

Windows

$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\sanma.conf
($ENV_DIR means "Environment Directory" specified at the Manager installation.)

Solaris OS,
Linux

/etc/opt/FJSVssmgr/current/sanma.conf

Edit one description as follows (0=Hide, 1=Show): DISPLAY_SNMP_STANDARD_EVENT = 0;.

Using Web Console, execute re-read definition file and import the definition files into the program.

[Test 2] Check Whether Server Node (Agent) Can Correctly Receive SNMP Traps

The server node (Agent) provides the following command that issue SNMP Trap for the test.

Platform of Agent

Command Location

Windows

$INS_DIR\Agent\bin\traptest [ipAddress]
($INS_DIR means "Program Directory" specified at the Agent installation.)

Solaris OS,
Linux,
HP-UX,
AIX

/opt/FJSVssage/bin/traptest [ipAddress]

Only in the environment where the host holds two or more IP addresses, a server node's IP (Agent start IP address) address which the manager recognizes is specified to ip-address.

Make sure the IP address input is correct, if the event cannot be received correctly.

If SNMP Trap monitoring is set up correctly in the device, an event is issued to Web Console when the command is executed.

If you change the action for SNMP Trap, refer to "A.5 SNMP Trap XML Definition File".

Information

The community name of a test SNMP Trap is fixed to "public".

[Test 3] Check Systemwalker Centric Manager Linkage and Shell/Bat Linkage of Events

Events cannot be linked with Systemwalker Centric Manager or Shell/bat for the standard SNMP Trap. To test the Systemwalker Centric Manager linkage and Shell/bat linkage of an SNMP Trap from a device, execute a tentative SNMP Trap command for the test on the Management Server. This command changes internal information of an SNMP Trap so that the SNMP Trap seems to have been sent from a device being monitored, and it sends such an SNMP Trap to the system's own port for receiving the SNMP Trap. Since descriptions of events are linked to Systemwalker Centric Manager and Shell/bat, Systemwalker Centric Manager linkage and Shell/bat linkage can be tested. To test the Shell/bat linkage of an SNMP Trap of the server node agent, use the method described in [Test 2].

For the IP address of an argument, specify the IP address of a device (ETERNUS Disk storage systems or Fibre Channel switch) registered with this software. The contents of this simulated SNMP Trap are loaded into the event log.

To generate a simulated SNMP Trap for the ETERNUS DX series, ETERNUS AF All-Flash Arrays, and ETERNUS DX200F that are registered in this software, execute the commands shown below. Using these commands, the manager creates the simulated trap, receives the same trap, and checks whether the displayed event and shell/bat linkage are correct. Here, the simulated trap is a fan fault with "public" as the Community name. This simulated trap has arbitrary test information that is distinct from actual trap information.
Also, the ETERNUS Disk storage systems can issue an SNMP Trap from the device by using the "SNMP Trap sending test" function of ETERNUS Web GUI. Though the test uses a simulated trap, its results are the same as those from a test that sends a real trap and checks the response, since the trap is sent from an actual ETERNUS Disk storage systems.

Platform of Manager

Command Location

Windows

$INS_DIR\Manager\opt\FJSVssmgr\bin\grtraptest ipAddress
($INS_DIR means "Program Directory" specified at the Manager installation.)

Solaris OS,
Linux

/opt/FJSVssmgr/bin/grtraptest ipAddress

To generate a simulated SNMP Trap for a Fibre Channel switch that is registered in this software, execute the commands shown below. (A simulated error that is a port fault is issued.):

Platform of Manager

Command Location

Windows

$INS_DIR\Manager\opt\FJSVssmgr\bin\swtraptest ipAddress
($INS_DIR means "Program Directory" specified at the Manager installation.)

Solaris OS,
Linux

/opt/FJSVssmgr/bin/swtraptest ipAddress

Note

Execute [Test 1] and [Test 3] on devices that are using SNMPv1. Use the device side function to confirm the receipt of the SNMP Traps from devices that are using SNMPv3.