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\Agent\var\sanm.ip ($TMP_DIR means "Work Directory" specified at the Agent installation.)
Solaris OS, Linux, HP-UX	/var/opt/FJSVssage/sanm.ip

Note

For VMware Infrastructure 3 Version 3.5 (or later) or VMware ESXi 3.5 (or later) environment, the fault monitoring function by receiving SNMP Traps is not supported.

Support levels A, B

When this software registers devices, SNMP Trap transmission place addresses are automatically set for devices to be managed.

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.

Support levels E, I (for devices supporting SNMP Traps): The SNMP Trap transmission place address is set on a device to the administrative server. For details of this setting, refer to the operation manual of the device.

Support level I (for devices not supporting SNMP Traps)

Fault monitoring by the mechanism is disabled since said devices do not support the SNMP Trap function.

Other server nodes (including Solaris OS and Windows server nodes without an agent) do not support fault management.

Note

If the Manager cannot receive the SNMP Trap, check the following:

Solaris OS Manager:

Check whether the SNMP Trap monitoring daemon is running. If not, start it. For details about checking and starting the daemon, refer to "12.1.2.1 Starting and stopping the SNMP Trap monitoring daemon".
If ESC Manager and Systemwalker Centric Manager are running on the same server, check whether Systemwalker Centric Manager SNMP Trap monitoring daemon is running. If not, start it. For details about checking and starting the daemon, refer to Systemwalker Centric Manager manual.
ESC Manager and Systemwalker Centric Manager use the same SNMP Trap monitoring service. Therefore, the SNMP Trap monitoring daemon stops if Systemwalker Centric Manager is uninstalled. In this case, either restart the OS or start the SNMP trap monitoring daemon after Systemwalker CentricManager has been uninstalled.
If the IP address of administrative server is changed, execute the procedure of "9.1.2.1 Changing the IP address of the administrative server".

Windows Manager:

Check whether the SNMP Trap monitoring service is running. If not, start it. For details about checking and starting the service, refer to "12.3.2.2 Starting and stopping the SNMP Trap monitoring service".
ESC Manager, Systemwalker Resource Coordinator Virtual server Edition, and Systemwalker Centric Manager use the same SNMP Trap monitoring service. Therefore, if ESC Manager and Systemwalker Resource Coordinator Virtual server Edition and Centric Manager are running on the same server, refer to "4.3.2 Advisory notes" - "Restrictions in the mixed environment of Systemwalker Centric Manager and Systemwalker Resource Coordinator Virtual server Edition" in the ETERNUS SF Storage Cruiser Installation Guide.
If the IP address of administrative server is changed, execute the procedure of "9.1.2.1 Changing the IP address of the administrative server".

Linux Manager:

Check whether the SNMP Trap monitoring daemon is running. If not, start it. For details about checking and starting the daemon, refer to "12.2.2.1 Starting and stopping the SNMP Trap monitoring daemon".
When ESC manager and Systemwalker Centric Manager are running on the same server, check whether Systemwalker Centric Manager SNMP Trap monitoring daemon is running. If not, start it. Refer to Systemwalker Centric Manager manual for details on checking and starting the daemon.
The ESC manager and Systemwalker Centric Manager use the same SNMP Trap monitoring service. When Systemwalker Centric Manager is uninstalled the SNMP Trap monitoring daemon will stop. In this case, after uninstalling Systemwalker Centric Manager, restart the operating system or start the SNMP Trap monitoring daemon.
If the IP address of administrative server is changed, execute the procedure of "9.1.2.1 Changing the IP address of the administrative server".