Master Slave configuration

From Secure Web Gateway
Share/Save/Bookmark
Jump to: navigation, search

What does Master/Slave means?

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

MasterslaveSlide1 (1).PNG

 

Go to Startup params

 
MasterslaveSlide1 (2).PNG
 
   
MasterslaveSlide1 (3).PNG
 
MasterslaveSlide1 (4).PNG
 
MasterslaveSlide1 (5).PNG
 
MasterslaveSlide1 (6).PNG
 
MasterslaveSlide1 (7).PNG
 
   
MasterslaveSlide1 (8).PNG
 
 

Configuration on Master Server if authentication is Enabled 

Go to Access Restriction under Application Setup

 
MasterslaveSlide1 (9).PNG

 

 
MasterslaveSlide1 (9).PNG

 

Go to Allow list

 
MasterslaveSlide1 (10).PNG
 
MasterslaveSlide1 (11).PNG
 
MasterslaveSlide1 (12).PNG
 
MasterslaveSlide1 (13).PNG
 
MasterslaveSlide1 (14).PNG
 

Verify the synchronization of defined sections on Slave server

Master slave configuration123.png