PRIMECLUSTER Global Link Services Configuration and AdministrationGuide 4.7Redundant Line Control Function

Appendix J Resident Process in GLS and Monitoring Target

This appendix explains the resident process in GLS and the monitoring target.

• Resident Process in GLS

  Table J.1 Processes in GLS

  Process name	Function	Resident
  /opt/FJSVhanet/etc/sbin/hanetctld	GLS control daemon	Resident
  /opt/FJSVhanet/etc/sbin/hanetmond	Monitors the status of the GLS control daemon and the sha driver.	Non-resident
  /opt/FJSVhanet/etc/sbin/hanetpathmd	Monitors the network in the Virtual NIC mode.	Non-resident
  /opt/FJSVhanet/etc/sbin/hanetselect	Monitors the transfer path in the NIC switching mode and the GS linkage mode.	Non-resident

  GLS: Global Link Services

  Note

  The following are not resident processes because the processes stop if an error is detected when a virtual interface is stopped.

  • hanetmond

  • hanetpathmd

  • hanetselect

• Monitoring Target

  Table J.2 Process that can be set as a monitoring target

  Process name	Function	Number of processes
  /opt/FJSVhanet/etc/sbin/hanetctld	GLS control daemon	1 to 3

  GLS: Global Link Services

  Note

  • In the following cases, the GLS control daemon is restarted, so the process may not temporarily exist.

    • Restarting GLS by using the resethanet -s command

    • Restarting GLS service (fjsvhanet.service)

  • The number of processes of the GLS control daemon is usually one. However, it may be temporarily two or three when a child process is started.