Vista has two paths to network . You must use advanced debug features to verify that both paths are being used to load-balance traffic to and to test both perpacket and per-destination load balancing. | Equal-Cost Load Balancing with RIP Workstation 24 Fa0 0 24 Vista S0 0 24 S0 1 24 S0 0 2 S0 1 24 Fa0 0 24 SanJose1 Fa0 0 24 SanJose2 Objective In this lab you observe equal-cost load balancing on a per-packet and per-destination basis by using advanced debug commands. Scenario Vista has two paths to network . You must use advanced debug features to verify that both paths are being used to load-balance traffic to and to test both perpacket and per-destination load balancing. Step 1 Build and configure the network according to the diagram just shown. Use RIPv1 and enable updates on all active interfaces with network commands similar to these SanJose1 config router rip SanJose1 config-router network SanJose1 config-router network Use the ping command to verify your work and test connectivity between all interfaces. 1 - 4 Semester 5 Advanced Routing - Lab Copyright 2001 Cisco Systems Inc. Step 2 Check the routing table on Vista using the show ip route command. Vista should have two routes to network in its table. Troubleshoot if necessary. RIP automatically performs load balancing using equal-cost routes. Note that both routes have a metric in this case a hop count of 1. RIP cannot perform unequal-cost load balancing. You will see in the next lab that IGRP can. Step 3 To configure Vista to load-balance on a per-packet basis both S0 0 and S0 1 must use process switching. Process switching forces the router to look in the routing table for the destination network of each routed packet. In contrast fast switching performs a table lookup for the first packet only. The router then stores the result in a high-speed cache and uses the cached information to forward all additional packets to the same destination. Fast switching is the default setting. Enable process switching on both of Vista s serial interfaces with the .
