Page 178 of 260
Maintenance
553-3001-225
Standard 1.00
May 2006
enabling the backup virtual routers to confirm that it is down before going on
to the next step:
•
If ARP replies from the active master are not received, failover occurs.
•
If ARP replies from the active master are received, no failover occurs.
Note:
If VRRP multicast advertisement packets are not received on any
backup router, the reason might be that the traffic on the active master is
too heavy for it to send advertisement packets within the advertisement
interval. If you believe this is the case, increase the advertisement
interval value.
When a virtual router comes up from the fault state, it sends ARP requests for
an active master. If the virtual router receives an ARP response, the virtual
router assumes the role of backup. The backup continues sending ARP
messages to the virtual router until it does not receive a response and then
initiates the failover process.
VRRP failover based on links
Link failures decrement the internal priority value that VRRP maintains for
both SMCs. A link failure is defined as a loss of link at the VRRP interface.
At initialization, VRRP sets the priority value to 100 for both SMCs. When a
physical link fails, VRRP reduces the priority value for that SMC by two. If
that causes the SMC’s priority value to fall below that of the other SMC,
failover occurs.
When the link is restored, the priority value for that SMC is increased by two.
This may cause both SMCs to have the same priority values. Nevertheless,
the cluster status does not change until a link failure occurs on the backup and
this causes VRRP to reduce its priority value by two and trigger a failover.
MAC address mapping
The active master uses its virtual router ID (vrid) to set a unique virtual router
MAC address according to this formula: 0x00005E0001<vrid>. This is the
address that the active master returns in response to end-host ARP requests
and proxy ARP requests. Gratuitous ARP (GARP) messages also contain the
active master’s virtual router MAC address. Meanwhile, the backup retains
its physical MAC address.
Summary of Contents for SMC 2450
Page 2: ......
Page 4: ...Page 4 of 260 Revision history 553 3001 225 Standard 1 00 May 2006...
Page 10: ...Page 10 of 260 Contents 553 3001 225 Standard 1 00 May 2006 Format 251 Log message table 253...
Page 16: ...Page 16 of 260 List of procedures 553 3001 225 Standard 1 00 May 2006...
Page 20: ...Page 20 of 260 About this document 553 3001 225 Standard 1 00 May 2006...
Page 56: ...Page 56 of 260 Description 553 3001 225 Standard 1 00 May 2006...
Page 76: ...Page 76 of 260 Hardware installation 553 3001 225 Standard 1 00 May 2006...
Page 120: ...Page 120 of 260 Firewall deployment 553 3001 225 Standard 1 00 May 2006...
Page 160: ...Page 160 of 260 Secure UNIStim deployment 553 3001 225 Standard 1 00 May 2006...
Page 182: ...Page 182 of 260 Maintenance 553 3001 225 Standard 1 00 May 2006...
Page 196: ...Page 196 of 260 The Command Line Interface CLI 553 3001 225 Standard 1 00 May 2006...
Page 212: ...Page 212 of 260 Logging 553 3001 225 Standard 1 00 May 2006...
Page 250: ...Page 250 of 260 Appendix D Software licenses 553 3001 225 Standard 1 00 May 2006...
Page 260: ...Page 260 of 260 Appendix E SMC packet filter log messages 553 3001 225 Standard 1 00 May 2006...
Page 261: ......