This section describes how to establish a dual-device backup platform to back up IGMP snooping entries. If a network node or link fails, a rapid Layer 2 multicast service switchover is triggered, improving service reliability.
Prerequisites
An Eth-Trunk interface has been created using the interface eth-trunk trunk-id command, and an Ethernet interface has been added to the Eth-Trunk interface using the eth-trunk trunk-id command.
An E-Trunk has been created using the e-trunk e-trunk-id command, and the Eth-Trunk interface has been added to the E-Trunk using the e-trunk e-trunk-id [ remote-eth-trunk eth-trunk-id ] command.
Context
In a master/backup E-Trunk scenario, a dual-device backup platform enables the master device to back up IGMP snooping entries to the backup device through a remote backup service (RBS) channel, ensuring multicast service continuity. Establishing a dual-device backup platform includes configuring an RBS, a remote backup profile (RBP), and a dual-device E-Trunk backup platform.
Perform the following steps on both the master and backup devices:
Procedure
- Configure an RBS.
- Run system-view
The system view is displayed.
- Run remote-backup-serviceservice-name
An RBS is created, and the RBS view is displayed.
- Run peer peer-ip-address source source-ip-address port port-id
TCP connection parameters are set for the RBS.
source-ip-address and peer-ip-address specify the IP addresses of the master and backup devices, respectively. The IP addresses of the master and backup devices must have been configured on their own interfaces, sub-interfaces, or logical interfaces (such as loopback interfaces) and be able to ping each other.
port-id specifies a TCP port number. The TCP port numbers configured on the master and backup devices must be the same.
- Run quit
Return to the system view.
- Configure an RBP.
- Run remote-backup-profileprofile-name
An RBP is created, and the RBP view is displayed.
- Run backup-id backup-id remote-backup-service service-name
A backup ID is configured for the RBP, and the RBP is associated with a specified RBS.
backup-id specifies a backup ID for an RBP. You can use a backup ID and an RBS to determine an RBP. The backup IDs configured for the same RBP must be the same on the master and backup devices and can no longer be configured for other RBPs.
- Run peer-backup hot
The backup type of the master device and backup device is set to hot backup mode.
- Run quit
Return to the system view.
- Configure a dual-device E-Trunk backup platform.
- Run remote-backup-profileprofile-name
The RBP view is displayed.
- Run e-trunk e-trunk-id eth-trunk eth-trunk-id
An E-Trunk's member interface Eth-Trunk is bound to a specified RBP. The interface bound to an RBP can only be an Eth-Trunk interface or an Eth-Trunk sub interface in normal mode, dot1q VLAN tag termination mode, or QinQ VLAN tag termination mode.
- Run quit
Return to the system view.
- Run e-trunke-trunk-id
The E-Trunk view is displayed.
- Run peer-address peer-ip-address source-address source-ip-address
IP addresses are assigned to the local and peer ends of the E-Trunk.
The peer IP address of the local end is the local IP address of the peer end. For example, an E-Trunk is established between device A and device B. On device A, the peer IP address is 2.2.2.2 and the local IP address is 1.1.1.1. Then, on device B, the peer IP address is 1.1.1.1 and the local IP address is 2.2.2.2.
- Run commit
The configuration is committed.
- (Optional) Configure BFD for E-Trunk
- Run bfd
The BFD is enabled.
- Run quit
Return to the system view.
- Run bfd session-name bind peer-ip ip-address
The BFD session for peer device is configured.
- Run discriminator
Local and remote discriminators are configured.
- Run quit
Return to the system view.
- Run bfd session-name bind peer-ip default-ip interface {interface-name | interface-type interface-number }[source-ip source-ip]
The BFD session for Eth-Trunk is configured.
- Run quit
Return to the system view.
- Run e-trunk e-trunk-id
The E-Trunk view is displayed.
- Run e-trunk track bfd-session session-name bfd-session-name
The E-Trunk is bound to the BFD session.
- Run commit
The configuration is committed.
