How can I create a Symantec Traffic Shaper failover cluster larger than the default of n+3?
| Article:TECH97008 | | | Created: 2009-01-23 | | | Updated: 2012-01-25 | | | Article URL http://www.symantec.com/docs/TECH97008 |
Problem
You have an STS cluster that is larger than the default of 4 outlined in the Symantec Traffic Shaper (STS) Implementation Guide and you wish to create an advanced failover cluster larger than the default of n+3.
Cause
The STS only allows 3 levels of backup per appliance. However, using a "rolling scheme" each appliance can in effect have N number of backups.
Solution
In the tables below, the column headings are the Virtual IP (VIP) addresses. The rows are the STS Virtual Router ID (VRID) numbers:
|
VRID / Virtual IP
|
VIP 1
|
VIP 2
|
VIP 3
|
VIP 4
|
VIP 5
|
VIP 6
|
|
VRID 1
|
primary
|
secondary
|
tertiary
|
quaternary
|
-
|
-
|
|
VRID 2
|
-
|
primary
|
secondary
|
tertiary
|
quaternary
|
-
|
|
VRID 3
|
-
|
-
|
primary
|
secondary
|
tertiary
|
quaternary
|
|
VRID 4
|
quaternary
|
-
|
-
|
primary
|
secondary
|
tertiary
|
|
VRID 5
|
tertiary
|
quaternary
|
-
|
-
|
primary
|
secondary
|
|
VRID 6
|
secondary
|
tertiary
|
quaternary
|
-
|
-
|
primary
|
So, based on this, appliance #1 would use its own VIP as its primary. It would then use the VIP of the second appliance as its secondary backup, the VIP of the third appliance as it tertiary backup and the VIP of fourth appliance as its quaternary backup. Appliance #2 would use its own VIP as primary, appliance #3 as secondary, and so on. Each appliance uses this same scheme including a "wrap around".
If you expand this to 9 systems, and they still end up with 3 backups each.
|
VRID / Virtual IP
|
VIP 1
|
VIP 2
|
VIP 3
|
VIP 4
|
VIP 5
|
VIP 6
|
VIP 7
|
VIP 8
|
VIP 9
|
|
VRID 1
|
primary
|
secondary
|
tertiary
|
quaternary
|
-
|
-
|
-
|
-
|
-
|
|
VRID 2
|
-
|
primary
|
secondary
|
tertiary
|
quaternary
|
-
|
-
|
-
|
-
|
|
VRID 3
|
-
|
-
|
primary
|
secondary
|
tertiary
|
quaternary
|
-
|
-
|
-
|
|
VRID 4
|
-
|
-
|
-
|
primary
|
secondary
|
tertiary
|
quaternary
|
-
|
-
|
|
VRID 5
|
-
|
-
|
-
|
-
|
primary
|
secondary
|
tertiary
|
quaternary
|
-
|
|
VRID 6
|
-
|
-
|
-
|
-
|
-
|
primary
|
secondary
|
tertiary
|
quaternary
|
|
VRID 7
|
quaternary
|
-
|
-
|
-
|
-
|
-
|
primary
|
secondary
|
tertiary
|
|
VRID 8
|
tertiary
|
quaternary
|
-
|
-
|
-
|
-
|
-
|
primary
|
secondary
|
|
VRID 9
|
secondary
|
tertiary
|
quaternary
|
-
|
-
|
-
|
-
|
-
|
primary
|
Using the above maps, you can configure STS Advanced Failover clusters that are much larger than the 4 hosts outlined in the Implementation Guide. The configuration is still all completed on the "Advanced Failover" page within the STS UI, as you only need to list each VIP, VRID and the order of one host relative to the other.
You can expand this same scheme out to 13 systems or more and the n+3 failover redundancy still holds.
|
|
Legacy ID
2009102316415954
Article URL http://www.symantec.com/docs/TECH97008
Terms of use for this information are found in Legal Notices
Thank you.