Starting and stopping cluster nodes manually

You may need to stop the entire Kaspersky Security Center Linux failover cluster or temporarily detach one of the nodes of the cluster for maintenance. If this is the case, follow the instructions in this section. Do not try to start or stop the services or processes related to the failover cluster by using any other means. This may cause data loss.

Starting and stopping the entire failover cluster for maintenance

To start or stop the entire failover cluster:

On the active node, run one of the following commands:

• To stop the cluster, run: /opt/kaspersky/ksc64/sbin/klfoc -stopcluster --stp klfoc
• To start the cluster, run: /opt/kaspersky/ksc64/sbin/klfoc -startcluster --stp klfoc

The failover cluster is started or stopped, depending on the command that you run.

Maintaining one of the nodes

To maintain one of the nodes:

1. On the active node, stop the failover cluster by using the klfoc -stopcluster --stp klfoc command.
2. On the node that you want to maintain, go to /opt/kaspersky/ksc64/sbin.
3. Open command line, and then detach the node from the cluster by running the detach_node.sh command.
4. On the active node, start the failover cluster by using the klfoc -startcluster --stp klfoc command.
5. Perform maintenance activities.
6. On the active node, stop the failover cluster by using the klfoc -stopcluster --stp klfoc command.
7. On the node that was maintained, go to /opt/kaspersky/ksc64/sbin.
8. Open command line, and then attach the node to the cluster by running the attach_node.sh command.
9. On the active node, start the failover cluster by using the klfoc -startcluster --stp klfoc command.
10. To ensure that the current node is active, run the following commands to check if the services are run:

    systemctl status klnagent_klfoc.service

    systemctl status kladminserver_klfoc.service

    systemctl status klactprx_klfoc.service

    systemctl status klwebsrv_klfoc.service

    systemctl status kliam_klfoc.service

    These services are run on the active node and not on the passive node.

The node is maintained and attached to the failover cluster.

See also: About Kaspersky Security Center Linux failover cluster Scenario: Deployment of Kaspersky Security Center Linux failover cluster

Page top