13.3.3 Starting and Stopping Daemons (Linux Environment)

The procedure for starting/stopping the SNMP Trap monitoring daemon on the Management Server differs depending on the IP address of the managed device and the protocol used with the device fault monitoring.

IP Address of Managed Device	Combination of Protocols Used with Device Fault Monitoring			Procedure for Starting/Stopping the SNMP Trap Monitoring Daemon
IP Address of Managed Device	SNMPv1	SNMPv2c	SNMPv3
IPv4 address only	Y	N	N	Refer to "For OS-standard SNMP Trap Monitoring Daemon".
Either of the following: IPv4 address only IPv4 address and IPv6 address	N	Y	N	Refer to "For ETERNUS SF SNMP Trap Monitoring Daemon".
	Y	Y	N
	N	N	Y
	Y	N	Y
	N	Y	Y
	Y	Y	Y

Y: Used. N: Not used.

For OS-standard SNMP Trap Monitoring Daemon

Only OS administrator (root) user can execute following commands.

Starting the SNMP Trap monitoring daemon
Execute the following command:
- For Red Hat Enterprise Linux 8 or Red Hat Enterprise Linux 7 environments
```
# systemctl start snmptrapd.service
```
- For Red Hat Enterprise Linux 6 environments
```
# /etc/init.d/snmptrapd start
```
Note
Restart the snmptrapd daemon and trpsrvd daemon for environments using the ServerView trap transfer program.
Stopping the SNMP Trap monitoring daemon
Execute the following command:
- For Red Hat Enterprise Linux 8 or Red Hat Enterprise Linux 7 environments
```
# systemctl stop snmptrapd.service
```
- For Red Hat Enterprise Linux 6 environments
```
# /etc/init.d/snmptrapd stop
```
Note
Do not stop the daemon unless there is a special reason, because it affects other software using snmptrapd.
Checking the SNMP Trap monitoring daemon
- For Red Hat Enterprise Linux 8 or Red Hat Enterprise Linux 7 environments
  Execute the following command to see whether the service is running:
```
# systemctl status snmptrapd.service
```
- For Red Hat Enterprise Linux 6 environments
  Execute the following command to see whether the process exists:
```
# /bin/ps -ef | grep snmptrapd | grep -v grep
```

For ETERNUS SF SNMP Trap Monitoring Daemon

When performing a configuration to use the ETERNUS SF SNMP Trap monitoring daemon in the following sections of the Installation and Setup Guide, the method to start/stop the SNMP Trap daemon is as follows:

"SNMP Trap Setting (for Linux)" in "Setup of Storage Cruiser's Manager"
Only OS administrator (root) user can execute following commands.
Starting the SNMP Trap monitoring daemon
Execute the following command:
- For Red Hat Enterprise Linux 8 or Red Hat Enterprise Linux 7 environments
```
# systemctl start startsc-snmptrapd.service
```
- For Red Hat Enterprise Linux 6 environments
```
# /opt/FJSVswstt/bin/mpnm-trapd start
```
Stopping the SNMP Trap monitoring daemon
Execute the following command:
- For Red Hat Enterprise Linux 8 or Red Hat Enterprise Linux 7 environments
```
# systemctl stop startsc-snmptrapd.service
```
- For Red Hat Enterprise Linux 6 environments
```
# /opt/FJSVswstt/bin/mpnm-trapd stop
```
Checking the SNMP Trap monitoring daemon
- For Red Hat Enterprise Linux 8 or Red Hat Enterprise Linux 7 environments
  Execute the following command to see whether the service is running:
```
# systemctl status startsc-snmptrapd.service
```
- For Red Hat Enterprise Linux 6 environments
  Execute the following command to see whether the process exists:
```
# /bin/ps -ef | grep nwsnmp-trapd | grep -v grep
```

This sub section explains how to start and stop the ETERNUS SF Manager daemons.

Point

If the procedure for starting/stopping daemons of the Management Server has already been completed according to "Starting and Stopping Daemons" in the AdvancedCopy Manager Operation Guide (for Linux), it is not necessary to perform the following procedure.

Only OS administrator (root) user can execute following commands.

Starting the daemons
- When the Management Server is not used for a cluster operation
  Execute the following command.
```
# /opt/FJSVesfcm/bin/startesf.sh
```
- When the Management Server is used for a cluster operation
  Start the cluster application (transaction) to which ETERNUS SF Manager belongs. Refer to the relevant cluster software manuals for information on how to start the cluster application.
Stopping the daemons
- When the Management Server is not used for a cluster operation
  Execute the following command.
```
# /opt/FJSVesfcm/bin/stopesf.sh
```
- When the Management Server is used for a cluster operation
  Stop the cluster application (transaction) to which ETERNUS SF Manager belongs. Refer to the relevant cluster software manuals for information on how to stop the cluster application.

Information

If the settings are configured to monitor devices using an IPv6 address, the SNMPv2c protocol, or the SNMPv3 protocol as described in the following Installation and Setup Guide section, the SNMP Trap monitoring daemon is also started or stopped at the same time.

"SNMP Trap Setting (for Linux)" in "Setup of Storage Cruiser's Manager"

Note

If the ETERNUS SF Manager daemons are stopped, other ETERNUS SF products that share the daemons cannot be operated.

13.3.3 Starting and Stopping Daemons (Linux Environment)

13.3.3.1 Starting and Stopping the SNMP Trap Monitoring Daemon

13.3.3.2 Starting and Stopping the ETERNUS SF Manager Daemons