ServerIron ADX Server Load Balancing Guide

Release 12.0.00

June 15, 2009

Tracking Trunk Ports with VRRP-E

Several application switching network designs involve configuring of trunk ports in order to handle higher bandwidth. These multi-port trunks design work well until one of the port within trunk fail. In the event of such failure, the trunk interface fall short of the expected throughput, however the ServerIron has no method of identifying this shortfall. If VRRP-E is configured then the failover occurs only after all ports within trunk fail.

When one of the trunk ports loses the link, the trunk ports exceed the throughput of a single gigabit link, but the ServerIon has no way of knowing to fail over. Only when all trunk member ports lose their link, is the track-priority appropriately decremented. If one of the trunk member is up, the track-priority must not be decreased.

This TrafficWorks software release enables the ServerIron to track failure of individual ports within trunk link and associate it with VRRP-E. In the previous software releases, the VRRP-E failover was triggered only after all ports within the trunk link failed. This enhancement allows the administrator to trigger failover even after the failure of one of the ports within the trunk link.

This release adds the following command under an interface and the ip vrrp-extended vrid <vrid-num> command:

•	"track-trunk-port ethernet <slot/port>"

This command is for VRRP-E only. It can only be configured for a primary trunk when VRRP-E is enabled. You must:

•	Add "track-port" before you add "track-trunk-port" for the same trunk.

•	Add "no track-trunk-port" before you add "no track-port" for the same trunk.

The decreased track-priority for a trunk can be calculated as the following:

•	Assume <track-priority> is the track-priority configured in "track-port" or default track-priority value.

•	If all trunk ports are up, the track-priority decreased is 0.

•	If no trunk ports are up, the track-priority decreased is <track-priority> of the trunk.

•	Otherwise, it must be calculated as the following: "track-priority> * (<num-config-ports> - <num-active-ports>)/<num-config-ports>"

Configuring Tracking Trunk Ports with VRRP-E

ServerIron(config)# trunk switch e 4/9 to 4/10

Trunk will be created in next trunk deploy.

ServerIron(config-)# trunk deploy

ServerIron(config)# int ve 1

ServerIron(config-vif-1)# ip vrrp-extended vrid 1

ServerIron(config-vif-1-vrid-1)# backup priority 200 track-priority 100

NOTE: The backup priority needs to be a decimal of 6-255 for vrrp-extended. The track-priority needs to be a decimal from 1-254.

ServerIron(config-vif-1-vrid-1)# track-port e 4/9

ServerIron(config-vif-1-vrid-1)# track-trunk-port e 4/9

NOTE: Optionally, you can specify track priority for the track-port. This overrides the track-priority specified in "backup priority x track-priority y".

ServerIron(config-vif-1-vrid-1)# track-trunk-port e 4/9 priority 80

NOTE: The track-port and track-trunk-port has to be trunk primary, otherwise an error will be prompted:

ServerIron(config-vif-1-vrid-1)# track-port e 4/10

Error - track port must be the first port of a trunk.

 

ServerIron(config-vif-1-vrid-1)# track-trunk-p e 4/10
Error - track trunk port must be the trunk primary.

Sample Configuration

ServerIron#sh run | i trunk

trunk server ethe 4/1 to 4/4

trunk server ethe 4/5 to 4/6

trunk switch ethe 4/9 to 4/10

ServerIron#sh run int ve 1

!Building configuration...

!Current configuration : 346 bytes

interface ve 1

ip address 2.2.2.21 255.255.255.0

ip vrrp-extended vrid 1

backup priority 200 track-priority 100

advertise backup

ip-address 2.2.2.30

vip-group 1

track-port e 4/1 priority 80

track-trunk-port e 4/1

track-port e 4/5

track-trunk-port e 4/5

track-port e 4/9

track-trunk-port e 4/9

enable

!

To remove track-port, track-trunk-port needs to be removed first

ServerIron(config-vif-1-vrid-1)# no track-port e 4/9

Must disable track-trunk-port before track-port

ServerIron(config-vif-1-vrid-1)#

NOTE: To remove trunk, track-trunk-port needs to be removed first

ServerIron(config-vif-1-vrid-1)# no trunk swi e 4/9 to 4/10

Need to remove track-port in vrrp(e) configuration first!

To configure this feature, follow these steps:

1.	This command can ONLY be configured for trunk primary.

ServerIron(config-vif-13-vrid-1)# track-trunk-port ethernet 4/34

Error - track trunk port must be the trunk primary.

ServerIron(config-vif-13-vrid-1)#

2.	Add "track-port" before adding "track-trunk-port" for the same trunk.

ServerIron(config-vif-13-vrid-1)# track-trunk-port ethernet 4/33

Must track-port this trunk before track-trunk-port the same trunk

ServerIron(config-vif-13-vrid-1)#

3.	Add "no track-trunk-port" before adding "no track-port" for the same trunk.

ServerIron(config-vif-13-vrid-1)#no track-port e 4/33

Must disable track-trunk-port before track-port

ServerIron(config-vif-13-vrid-1)#

Sample Configuration

In the following configurion, both SI-A and SI-B share a trunk with a FastIron switch. The trunk has two ports (e4/33-34) and the primary trunk is e4/33. VRRP-E vrid 1 is configured in interface e4/17.

SI-A

trunk switch ethe 4/33 to 4/34

!

vlan 2 by port

untagged ethe 4/17

router-interface ve 13

!

router vrrp-extended

!

interface ve 13

ip access-group 130 in

ip address 10.13.30.170 255.255.255.0

ip vrrp-extended vrid 1

backup priority 106 track-priority 21

ip-address 10.13.30.254

track-port e 4/33

track-trunk-port e 4/33

enable

!

SI-B

trunk switch ethe 4/33 to 4/34

!

vlan 2 by port

untagged ethe 4/17

router-interface ve 13

!

router vrrp-extended

!

interface ve 13

ip access-group 130 in

ip address 10.13.30.171 255.255.255.0

ip vrrp-extended vrid 1

backup priority 100 track-priority 20

ip-address 10.13.30.254

track-port e 4/33

track-trunk-port e 4/33

enable

!