vReps

• 3 min to read •

vReps are discovery agents that despite being installed on the devices that are a part of a virtual private network, can be detected by an external cloud server. The devices with vReps installed on them are called domain controllers.

To discover devices, the cloud server sends a request to the domain controller, and the controller then discovers other devices and installs a Syxsense agent on them.

Important Information

The Discovery Task process can install the Micro Agent on Windows-based devices if required;

It is good practice to install the vRep agent only on devices that are continually switched on, such as servers;

A vRep is required to communicate with Mac and Linux devices and any tasks that target such devices will be routed and controlled by the vRep;

The first vRep to register with your cloud console will automatically be approved; if the vRep agent is installed on any other devices, they will need to be approved manually;

The solution can function without any vReps being set up, but this limits the devices that can be managed to Windows- or Mac-based devices that have a MicroAgent or Mac Agent installed.

Prerequisites

A device in the Syxsense Manage console that has the vRep agent installed

A Syxsense Manage account that has the 'Admin' user permissions

Discovery: vRepsDiscovery: vRepsRe

Indicate vRep

Within the 'Devices' area of Syxsense Manage vReps are shown with a blue device icon ①

A dark-blue icon indicates that the vRep is online.

A light-blue icon indicates that the device currently does not have a connection to Syxsense Manage.Drop-down TitleDrop-down Title

View and Manage

In order to view and manage the vReps which are reporting into your console select 'vReps' from the 'Devices' area of Syxsense ManageDrop-down TitleDrop-down Title

Example

In the screenshot provided below the following can be observed:

③ The device named 'Device-vrep1' has been approved, it resides in the site named 'Site A', it is the default vRep which means that it will be used in any discovery task for any site that does not have an allocated vRep associated to it;

④ The device named 'Device-vrep2' has been approved, it resides in the site named 'Site B', it has been applied to the site named 'Site B' therefore it is the only vrep that that will be used when performing a discovery task on Site B, Linux devices in Site B will only communicate with this device;

Non-internet-facing devices in Site B can only use this device as a relay agent;

This vRep will only communicate with devices in Site B;

⑤ The device named 'Device-vrep3' has been approved, it resides in the site named 'Site 1', it has been applied to the sites named 'Site 1', 'Site 2', and 'Site 3' therefore it is the only vrep that that will be used when performing a discovery task on these sites ; Linux devices in these sites will only communicate with this device;

Non-internet-facing devices in these sites can only use this device as a relay agent;

This vRep will only communicate with devices in these sites;

⑥ The device named 'Device-vrep4' has not been approved, it resides in the site named 'Site 4', it has been applied to the site named 'Site 4';

Devices in Site 4 that can only communicate with the console via this vRep will fail to carry out any tasks set up to run on them;

Devices in Site 4 that have a Micro Agent installed will not be affected by the unapproved vRep, they will still be able to perform tasks as long as they have their own connection to the Syxsense Manage Console;Drop-down TitleDrop-down Title

Last Update: July, 2024