Configuring VRRP-E on the MCT Client VLAN
Summary
This KBA explains how to configure VRRP-E in the MCT topology.Question
Customer Environment
Peer A: ICX 7850-48F Peer B: ICX 7850-48F Client A: ICX 7550-24P Firmware Version (all devices): 10.0.10g_cd6Symptoms
Root Cause
This KBA explains how to configure VRRP-E in the MCT topology.Troubleshooting Steps
Configuring VRRP-E on the MCT Client VLAN
Purpose
This section explains how to configure VRRP-E on the same client VLAN already used in the MCT topology.
VRRP-E provides a virtual gateway IP address for hosts connected to VLAN. This allows the hosts to use a single default gateway address while Peer-A and Peer-B provide redundancy for the gateway function. VRRP-E is a RUCKUS enhanced version of VRRP where all routers start as backup, the router with the highest active priority becomes master, and the master replies to ARP and ICMP requests for the virtual IP.
NOTE : MCT configuration is on the Following KB: 000015488
1. Existing VLAN and VE Reference and Topology used
Topology Information:
Client VLAN: VLAN 10
Client VE Interface: VE 10
LAG 21: Client-facing LAG connecting the MCT peer switches to Client-A.
LAG 2: Inter-Chassis Link (ICL) between the two MCT peer switches.
- Peer A: ICX 7850-48F
Peer-A#show running-config interface ve 10
interface ve 10
ip address 192.168.10.2 255.255.255.0
Peer-A#show running-config vlan 10
vlan 10 name MCT-CLIENT-VLAN by port
tagged lag 2 lag 21
- Peer B: ICX 7850-48F
Peer-A#show running-config interface ve 10
interface ve 10
ip address 192.168.10.1 255.255.255.0
Peer-B#show running-config vlan 10
vlan 10 name MCT-CLIENT-VLAN by port
tagged lag 2 lag 21
- Client A: ICX 7550-24P
Client-A#show running-config interface ve 10
interface ve 10
ip address 192.168.10.10 255.255.255.0
Client-A#show running-config vlan 10
vlan 10 name MCT-CLIENT-VLAN by port
tagged lag 21
- Firmware Version (all devices): 10.0.10g_cd6
2. VRRP-E Design Notes Before Configuration on this scenario
- Before configuring VRRP-E, validate the following:
- VLAN 10 must already exist on both MCT peers.
- VE 10 must already be configured on both MCT peers.
- The VRRP-E virtual IP must be in the same subnet as the VE 10 real IP addresses.
- The VRRP-E virtual IP must not be the same as any real interface IP address.
- Both peers must use the same VRID for the same VRRP-E instance. states that VRRP-E virtual router IDs can range from 1 to 255.
- The peer with the highest active VRRP-E priority becomes the master.
- VRRP-E is not supported on non-RUCKUS devices and does not interoperate with standards-based VRRP sessions.
- The peer with the higher priority should become the preferred master.
- The peer with the lower priority should remain as backup and take over only if the master is no longer available.
3. VRRP-E Configuration
3.1 Peer-A Configuration
Peer-A will be configured as the backup of VRRP-E master by assigning a lower priority.
To enable VRRP-extended
Peer-A(config)#router vrrp-extended
Peer-A(config-vrrpe-router)#exit
Peer-A(config)#interface ve 10
backup priPeer-A(config-vif-10)#ip vrrp-extended vrid 10
Peer-A(config-vif-10-vrid-10)#backup priority 100 track-priority 10
Peer-A(config-vif-10-vrid-10)#ip-address 192.168.10.254
Peer-A(config-vif-10-vrid-10)#advertise backup
Peer-A(config-vif-10-vrid-10)#activate
VRRPE router 10 for this interface is activating
Explanation:Peer-A uses priority 100, so Peer-B should remain in the backup state while Peer-A is operating as master. The backup role means Peer-B is standing by for the same virtual gateway IP. If Peer-A loses the master role or becomes unavailable, Peer-B can transition from backup to master and continue providing the same default gateway IP to the client VLAN.
The advertise backup command allows Peer-B to advertise its backup availability to the master router. This is useful because the master can see the backup router availability in the VRRP-E instance without requiring the engineer to log into the backup router
3.2 Peer-B Configuration
Peer-B will be configured as the preferred VRRP-E master by assigning a higher priority.
To enable VRRP-extended
Peer-B(config)#router vrrp-extended
Peer-B(config-vrrpe-router)#exit
Peer-B(config)#interface ve 10
vrid 1Peer-B(config-vif-10)#ip vrrp-extended vrid 10
Peer-B(config-vif-10-vrid-10)#backup priority 105 track-priority 10
Peer-B(config-vif-10-vrid-10)#ip-address 192.168.10.254
Peer-B(config-vif-10-vrid-10)#activate
VRRPE router 10 for this interface is activating
Explanation:
Peer-B uses priority 105, which makes this peer the preferred master for VRRP-E instance 10. As long as Peer-B remains available and its active priority is higher than Peer-B.
4. Verification Commands for validation:
show ip vrrp-extended brief
show ip vrrp-extended ve 10
show ip vrrp-extended stat
Peer-A
Peer-B
Client-A Default Gateway
Client-A should use the VRRP-E virtual IP as the default gateway.
If a default route is needed on Client-A for testing:
Client-A(config)#ip route 0.0.0.0/0 192.168.10.254
Explanation:
The client should point to the VRRP-E virtual IP instead of the real VE IP address from Peer-A or Peer-B. This keeps the gateway consistent even if the VRRP-E master changes.
Resolution
Note: The configuration and reference commands are attached for your review.
Attachment 1
Peer-Artf
Download
(81.1 KB)
Attachment 2
Client-Artf
Download
(66.5 KB)
Attachment 3
Peer-Brtf
Download
(79.4 KB)
Article Number:
000015491
Updated:
August 26, 2026 12:43 AM (8 days ago)
Answer Attachment 1
Peer-A
rtf
Download
(81.1 KB)
Answer Attachment 2
Client-A
rtf
Download
(66.5 KB)
Answer Attachment 3
Peer-B
rtf
Download
(79.4 KB)
Tags:
Configuration, Ruckus ICX Switches
Votes:
0
This article is:
helpful
not helpful