VRRP & E-Trunk

    Hi, LSA

We’re very sorry to hear that you’re experiencing this issue. We wanted to let you know that we’re doing our best to fix this issue as soon as possible

Additional technologies are required to enhance the VRRP active/standby function. For example, when the link from the master to a network is disconnected, VRRP cannot detect the fault and an active/standby switchover cannot be performed. As a result, hosts cannot remotely access the network through the master. To address this issue, you can configure association between VRRP and the interface status.

When the master detects that the uplink interface fails, the master reduces its priority to be lower than the priority of the backup and immediately sends VRRP packets. After the backup receives the VRRP packets, it detects that the priority in the VRRP packets is lower than its priority and switches to the master. This ensures correct traffic forwarding.

You can more detailed information regarding their configuration on following link:

https://support.huawei.com/enterprise/en/doc/EDOC1000069608/d4f7ac71/example-for-configuring-an-eth-trunk-and-association-between-vrrp-and-the-interface-status

VRRP is a Layer 3 protocol. e-Trunk is a Layer 2 protocol

Eth-Trunk implements link reliability between single devices. However, if a device fails, Eth-Trunk fails to take effect.

To improve network reliability, carriers introduced device redundancy with master and backup devices. If the master device or primary link fails, the backup device can take over user services. In this situation, another device must be dual-homed to the master and backup devices, and inter-device link reliability must be ensured.

E-Trunk was introduced to meet the requirements. E-Trunk aggregates data links of multiple devices to form a link aggregation group (LAG). If a link or device fails, services are automatically switched to the other available links or devices in the E-Trunk, improving link and device-level reliability. For more details, please refer to https://support.huawei.com/hedex/hdx.do?docid=EDOC1100109721&id=EN-US_CONCEPT_0172352196&lang=en

The Virtual Routing Redundancy Protocol (VRRP) combines several routing devices into a virtual routing device to implement active/standby backup of gateways and ensure reliable communication. As shown in the figure, switchA and Switch B form a VRRP group. In normal situations, SwitchA is the master device and is responsible for forwarding tasks, SwitchB is a backup device and does not forward services. If SwitchAw fails, SwitchB becomes the new master device and continues to forward data to hosts to implement gateway backup. For more details, please refer to https://support.huawei.com/enterprise/en/doc/EDOC1000088597

Overview of Layer 2 Redundancy Solutions:

      STP - the oldest STP, only for backward compatibility. Do not use it if you don't need it. It is slow and does not guarantee the longest recovery time.

      RSTP - the successor of STP. It still does not guarantee the longest recovery time, but it is usually quite fast. It is standardized by IEEE 802.1D, so it is supported by almost all manufacturers' products.

      MST - an extended version of RSTP.

      Link Aggregation - Standardized by IEEE

      HIPER-Ring - Very fast and reliable ring redundancy, exclusive to Hirschmann and Siemens

      MRP - Very fast and reliable ring redundancy, standardized by IEC

      PRP - Lossless redundancy of parallel paths standardized by IEC, requiring special hardware

      HSR - Requires lossless redundancy by using rings in both directions of IEC standardization, requiring special hardware

      DLR - Uses lossless redundancy of rings standardized by IEC and driven by ***kwell, requiring special hardware

Layer 3 redundancy solution:

      VRRP - Standardized by IETF (RFC)

      HiVRRP - faster than VRRP, proprietary by Hirschmann, based on VRRP, faster.

I hope to help you

@LSA hello,
as far as my understanding, VRRP provides a network layer redundancy while E-trunk provides a link redundancy.
VRRP is used for the gateway redundancy, so that the failure of the gateway device is blackbox to the hosts.
E-Trunk is a enhanced Eth-trunk, eth-trunk provides the link redundancy, but it requires the membership links are in the same devices or boards. If the device goes wrong, eth-trunk wouldn't be helpful. To prevent such error, the E-Trunk is introduced, it allows the membership links located in multi devices, so that it could work fine though one device go wrong.
In briefly, VRRP provides a layer 3 redundancy(gateway redundancy) while E-Trunk provides layer 2 redundancy.