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

2.1 Receiving SNMP Traps

First, set up an environment in which devices can send SNMP Traps.

Server Node

SNMP Trap transmission place addresses are automatically set for the server node agent when this software registers devices.

If Manager operates across multiple networks, however, this software may not be able to set correct settings for the server node agent. In this event, check whether SNMP Trap transmission place addresses are correctly set for the server node agent. The files indicated below for the server nodes specify the SNMP Trap transmission place addresses of the server node agent. Check the addresses, and edit any address that must be corrected. To operate according to the contents of the file the restart of Agent is needed.

Server Node OS

Place of File

Windows

$TMP_DIR\ESC\Agent\var\sanm.ip
($TMP_DIR means "Work Directory" specified at the Agent installation.)

Solaris OS,
Linux,
HP-UX,
AIX

/var/opt/FJSVssage/sanm.ip

Note

The SNMP Trap fault monitoring function is not supported for VMware vSphere.

Support Levels A and B

When using SNMPv1, the SNMP Trap destination address is automatically set on each managed device when registering the device with this product.

However, if Manager operates across multiple networks, this software may not be able to set the correct setting for each device to be managed. In this case, check whether SNMP Trap transmission target addresses are correctly set for the managed devices.

In addition, if SNMP Trap transmission place addresses are automatically set, the SNMP Trap transmission send destination community name is fixed to "public".

When using SNMPv3, set the Management Server IP address manually to the SNMP Trap destination address for the device. Refer to the device manual for details.

Support Level E

Set the Management Server IP address manually to the SNMP Trap destination address for the device. Refer to the device manual for details.

Support Level I

The fault management for server nodes on which the Storage Cruiser's agent is not installed is not supported.

Note