Skip to main content

Master-Slave Configuration in SafeSquid

What does Master/Slave mean?​

In computer networking, master/slave is a model for a communication in which one device or process (known as the master) controls one or more other devices or processes (known as slaves). Once the master/slave relationship is established, the direction of control is always from the master to the slave(s).

In a master-slave configuration of SafeSquid, a specific instance of SafeSquid (the master server) manages other instances of SafeSquid (the slave servers). The stand-alone and slave instances are almost identical in functionality.

A slave server acts as a single (stand-alone) instance of SafeSquid, managing network computers. Furthermore, the slave server receives policies and tasks from its master server.

The master server does not have its own managed computers, but it indirectly manages those of its slave servers by assigning policies and tasks to them. Another purpose of the master server is to provide you with information on the network security status, by centralizing data from all managed servers. In this way, you can get centralized results from all the clients of the slave servers in a single report.

Prerequisites​

SafeSquid should be installed and activated using same product activation key on all the machines (master as well as slave)

Master Slave configuration​

Access the SafeSquid User Interface​

Configuration on Slave Server​

Go to Support​

clicking on support in safesquid interface in top right corner

Go to Startup params​

clicking on start up params

clicking on edit button

entering the master IP address

entering the port of master server

clicking on submit button

clicking on restart button

clicking on yes for backup current configuration to cloud

Configuration on Master Server if authentication is Enabled​

Go to Access Restriction under Application Setup​

Going to Access Restriction under Application Setup

If authentication is enabled on master server you have to configure policies as shown on master server

Go to Allow list​

going to allow list tab in access restrictions

enabling the policy as true

enabling the policy as true for giving access to slave server

clicking on save to save the policy

policy saved

Verify the synchronization of defined sections on Slave server​

Verifying the synchronization of defined sections on Slave server

Feedback