Active/Backup reservation (VRRP) [Документация VAS Experts]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

en:dpi:dpi_components:platform:dpi_reserve [2024/09/26 15:29] – created - external edit 127.0.0.1en:dpi:dpi_components:platform:dpi_reserve [2025/04/29 07:38] (current) elena.krasnobryzh
Line 2: Line 2:
 ======Active/Backup reservation (VRRP)====== ======Active/Backup reservation (VRRP)======
  
-[[https://en.wikipedia.org/wiki/Virtual_Router_Redundancy_Protocol|VRRP]] support is implemented in SSG using the Linux daemon [[https://linux.die.net/man/8/keepalived|keepalived]]. It configures scripts for calling CLI commands to put SCAT in master or backup mode.+[[https://en.wikipedia.org/wiki/Virtual_Router_Redundancy_Protocol|VRRP]] support is implemented in SSG using the Linux daemon [[https://linux.die.net/man/8/keepalived|keepalived]]. It configures scripts for calling CLI commands to put SSG in master or backup mode.
  
 In master mode, all SSG functionality is available. In backup mode, SSG works only as a bridge in_dev <-> out_dev, no packets are emitted by SSG itself. It is supposed that in backup mode no traffic should come to SSG at all. But it seems that some service L2 protocols necessary for the operator's network may still arrive at the SSG in backup mode, which is why the transparent bridge mode remains enabled in backup mode. In master mode, all SSG functionality is available. In backup mode, SSG works only as a bridge in_dev <-> out_dev, no packets are emitted by SSG itself. It is supposed that in backup mode no traffic should come to SSG at all. But it seems that some service L2 protocols necessary for the operator's network may still arrive at the SSG in backup mode, which is why the transparent bridge mode remains enabled in backup mode.