Radware Alteon Application Manual page 512

Alteon Application Switch Operating System Application Guide
High Availability
With sharing enabled, an IP interface or a VIP address can be active simultaneously on multiple
Alteons, enabling active-active operation as shown in
Configuration, page 511
Table 47: Active-Active Failover with Shared Interfaces
Alteon Virtual Router 1
Alteon 1 Master-Active
VRID 2
VIP: 205.178.13.226
Virtual Rtr. MAC address:
00-00-5E-00-01-02
Alteon 2 Backup-Active VR 1
VRID 2
VIP: 205.178.13.226
Virtual Rtr. MAC address:
00-00-5E-00-01-02
When sharing is used, incoming packets are processed by the Alteon on which they enter the virtual
router. The ingress Alteon is determined by external factors, such as routing and Spanning Tree
configuration.
Sharing cannot be used in configurations where incoming packets have more than one entry point
into the virtual router. For example, where a hub is used to connect Alteons.
When sharing is enabled, the master election process still occurs. Although the process does not
affect which Alteon processes packets that must be routed or that are destined for the virtual server
IP address, it does determine which Alteon sends advertisements and responds to ARP requests sent
to the virtual router's IP address.
Radware strongly recommends that sharing, rather than active-standby configurations, be used
whenever possible. Sharing offers both better performance and fewer service interruptions in the
face of fault conditions than active-standby configurations. See
for a configuration example.
Service-Based Virtual Router Groups
A service-based virtual router group (vrgroup) consists of one or more virtual routers on an Alteon.
Virtual routers can be grouped together and behave as a single VRRP entity by updating the priority
for the group. Service-based virtual router groups allow for efficient tracking and failover based on
each group's tracking parameters while leaving other groups unaffected.
Virtual routers in one vrgroup (
status (master, backup or init). By contrast, virtual routers in the global vrrp group (
) will always have the same status.
vrrp/group
The priority, tracking and preemption values for each virtual router in a vrgroup are overridden by
the values for the vrgroup itself.
Radware recommends that you enable preemption when working with service-based virtual router
groups. If you do not want to use preemption, you should work with switch-based virtual router
groups instead.
Note: For a vrgroup to work correctly, you must first set virtual router tracking for one of the virtual
routers configured for that group using the
only set tracking for one virtual router in a vrgroup.
As shown in the example in
513, an administrator wants to provide high availability for Customer A and Customer B's servers
and services across the same two Alteons, without one affecting the other:
512
and Table 47 - Active-Active Failover with Shared Interfaces, page
Virtual Router 2
Backup-Active
VRID 4
VIP: 205.178.13.240
Virtual Rtr. MAC address:
00-00-5E-00-01-04
Master-Active VR 2
VRID 4
VIP: 205.178.13.240
Virtual Rtr. MAC address:
00-00-5E-00-01-04
/cfg/l3/vrrp/vrgroup 1
cfg/l3/vrrp/vrgroup/trackvr
Figure 76 - Service-Based Virtual Router Groups Configuration, page
Figure 74 - Virtual Interface Router
Virtual Router 3
Master-Active
VRID 6
VIP: 205.178.13.110
Virtual Rtr. MAC address:
00-00-5E-00-01-06
Backup-Active VR 3
VRID 6
VIP: 205.178.13.110
Virtual Rtr. MAC address:
00-00-5E-00-01-06
Active-Active Redundancy, page 527
) will not necessarily all have the same
Document ID: RDWR-ALOS-V2900_AG1302
512:
/cfg/l3/
command. You can