Starting Up and Shutting Down

Introduction

A jtel ACD consists of a minimum of 2 virtual machines and may grow to sizes of 30 or more, depending on redundancy or performance requirements. Based on a systems architecture, there are certain dependencies between the services, so a clean startup and shutdown is required and only done in a certain order to prevent problems during and after startup. The following pages describe the general parameters, as well as some of the various possible scenarios for proper shutdown and startup procedures, depending on the systems architecture. 

Page Layout

The pages are split into a parent and child pages. This parent page contains general information. The child pages each contain information about the specific procedure, depending on the sizing of the system. The sizing variants are Small, Medium and Large

Redundancy - Controlled Failovers

If you wish to shutdown only one side of your redundant jtel cluster, the following child page provides a guide for this procedure  Shutdown/Startup Procedure - Redundancy - Controlled Failover and Failback

This procedure is useful for cases where one of your VM-Hosts must be shutdown, but your jtel ACD is required to maintain service during this time. 

jtel System Dependencies

All services of the platform are dependent on two central entities:

• The Storage(s)
• The Database(s)

To boot the solution, the storage should always be booted first. If this is external to the solution, continue with the next step. Otherwise, the computer (or in case of redundancy - both computers) is started on which the storage is located. This is usually the load balancer, but for larger systems a separate storage machine could have been implemented. Afterwards, the master database is booted. As soon as its is finished, the slave can be started up. Finally, the telephony servers and web servers can be started up in any order, even simultaneously.

Redundant Systems

Shutting down redundant clusters is generally easier than starting them back up. If problems occur after starting back up, some components must be checked:

Database:

• MySQL Replication between all replication partners

Load Balancing:

• pcs cluster status

Storage:

• pcs cluster status
• drbd status

Checks after starting a system

To ensure proper system functionality after a boot, tests are required. Follow the guideline on this page: System Health Check

Machines and Shutdown Priorities