ic flow. Let's look at a sample configuration based on our example. Here are the basic GLBP configs for our three routers: R1 configuration: interface FastEtherneto/o ip address 10.0.0.2 255.255.255.0 glbp 10 ip 10.0.0.1 glbp 10 preempt glbp 10 weighting 50 glbp 10 load-balancing weighted Without a configured value, R1 will default to a priority of 100. R2 configuration: interface FastEtherneto/o ip address 10.0.0.3 255.255.255.0 glbp 10 ip 10.0.0.1 glbp 10 priority 50 glbp 10 preempt glbp 10 weighting 25 glbp 10 load-balancing weighted R3 configuration: interface Etherneto/o ip address 10.0.0.4 255.255.255.0 glbp 10 ip 10.0.0.1 glbp 10 priority 25 glbp 10 preempt glbp 10 weighting 25 glbp 10 load-balancing weighted On Nexus, you must first enable GLBP with the feature glbp command. Weighting is used both for load distribution and object tracking (see the next section). The weighting value can be between 1 and 254, which means you can configure a single router with a weight over 100. How does the router distribute load when the weighting values can all be over 100? The Cisco documentation has this to say: The amount of load directed to an AVF is dependent upon the weighting value advertised by the gateway containing that AVF. Each Virtual Forwarder in a gateway uses the current weighting value of that gateway, regardless of how many Virtual Forwarders are active in that gateway. This is the ability [of] GLBP to place a weight on each device when calculating the amount of load sharing that will occur through MAC assignment. Each GLBP router in the group will advertise its weighting and assignment; the AVG will act based on that value. For example, if there are two routers in a group and router A has double the forwarding capacity of router B, the weighting value of router A should be configured to be double the amount of router B. The weighting is determined by dividing the individual router's weight by the sum of all the weights in the group. For example, if we configure our three gateways with weights of 50/25/2