13.3.3 Starting and Stopping Daemons (Linux Environment)

The procedure to start and stop the SNMP Trap daemon on the Management Server is different depending on the IP address of the managed device and the protocol used for device fault monitoring.

IP Address of Managed Device	Protocol Used by Device Fault Monitoring	SNMP Trap Settings
IPv4 address only	SNMPv1 only	Refer to "For OS-standard SNMP Trap Monitoring Daemon".
IPv4 address only	SNMPv3 only, or SNMPv1 and SNMPv3	Refer to "For ETERNUS SF SNMP Trap Monitoring Daemon".
IPv4 address and IPv6 address	SNMPv3 only, or SNMPv1 and SNMPv3	Refer to "For ETERNUS SF SNMP Trap Monitoring Daemon".

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:
- In the case of RHEL5 or RHEL6
```
# /etc/init.d/snmptrapd start
```
- In the case of RHEL7
```
# systemctl start snmptrapd.service
```
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:
- In the case of RHEL5 or RHEL6
```
# /etc/init.d/snmptrapd stop
```
- In the case of RHEL7
```
# systemctl stop snmptrapd.service
```
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
- In the case of RHEL5 or RHEL6
  Execute the following command to see whether the process exists:
```
# /bin/ps -ef | grep snmptrapd | grep -v grep
```
- In the case of RHEL7
  Execute the following command to see whether the service is running:
```
# systemctl status snmptrapd.service
```

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 ETERNUS SF 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:
- In the case of RHEL5 or RHEL6
```
# /opt/FJSVswstt/bin/mpnm-trapd start
```
- In the case of RHEL7
```
# systemctl start startsc-snmptrapd.service
```
Stopping the SNMP Trap monitoring daemon
Execute the following command:
- In the case of RHEL5 or RHEL6
```
# /opt/FJSVswstt/bin/mpnm-trapd stop
```
- In the case of RHEL7
```
# systemctl stop startsc-snmptrapd.service
```
Checking the SNMP Trap monitoring daemon
- In the case of RHEL5 or RHEL6
  Execute the following command to see whether the process exists:
```
# /bin/ps -ef | grep nwsnmp-trapd | grep -v grep
```
- In the case of RHEL7
  Execute the following command to see whether the service is running:
```
# systemctl status startsc-snmptrapd.service
```

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

Starting daemons
Execute the following command.
```
# /opt/FJSVesfcm/bin/startesf.sh
```
Stopping daemons
Execute the following command.
```
# /opt/FJSVesfcm/bin/stopesf.sh
```

Information

If the settings are done in order to monitor IPv6 address assigned devices in the following sections in the ETERNUS SF Installation and Setup Guide, the SNMP Trap daemon is also started / stopped at the same time:

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

Note

When the batch stop is done, AdvancedCopy Manager cannot be operated from the Web Console.

13.3.3 Starting and Stopping Daemons (Linux Environment)

13.3.3.1 Starting and Stopping SNMP Trap Monitoring Daemon

13.3.3.2 Starting and Stopping Daemon