Multi Area OSPF for CCNA

This session will introduce the use, operation and configuration of Open Shortest Path First (OSPF) in multiple areas. If a single OSPF area ballooned into 400 networks, how might an OSPF topology be modified so the SPF algorithm does not overwhelm the network and so routing and link-state tables are manageable? Attend this session to learn the basics of Multi-area OSPF and use Packet Tracer 6.x to configure a Multi-area OSPF network.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Multi Area OSPF for CCNA

Please click this link to download Topology of Multi Area OSPF for CCNA

Step 1 – Initial Topology

a.      Open the Packet Tracer 6.0.1 file MultiAreaOSPF-Step1.pkt to configure the following topology.  Skip to Step 2 to bypass the necessary IP Address configuration.

b.      Configure the Hostnames and IP Addresses as shown in the following table.  Also enter the command no shutdown on each of the interfaces (except loopback interfaces)

Source	Interface	Destination	Interface	IP Address	Subnet Mask
RTA	Serial 0/0/0	RTB	Serial 0/0/0	10.1.1.1	255.255.255.252
RTA	Serial 0/0/1	RTC	Serial 0/0/1	10.1.1.5	255.255.255.252
RTA	Loopback 0	Internet		172.16.1.1	255.255.255.0
RTB	Serial 0/0/0	RTA	Serial 0/0/0	10.1.1.2	255.255.255.252
RTB	Serial 0/0/1	RTC	Serial 0/0/0	10.1.1.9	255.255.255.252
RTB	Gigabit 0/0	RTD	Gigabit 0/0	192.168.0.1	255.255.255.0
RTC	Serial 0/0/1	RTA	Serial 0/0/1	10.1.1.6	255.255.255.252
RTC	Serial 0/0/0	RTB	Serial 0/0/1	10.1.1.10	255.255.255.252
RTC	Gigabit 0/0	RTE	Gigabit 0/0	192.168.4.1	255.255.255.0
RTD	Gigabit 0/0	RTB	Gigabit 0/0	192.168.0.2	255.255.255.0
RTD	Loopback 0	LAN		192.168.1.1	255.255.255.0
RTE	Gigabit 0/0	RTC	Gigabit 0/0	192.168.4.2	255.255.255.0
RTE	Loopback 0	LAN		192.168.5.1	255.255.255.0

c.       Example, for RTA, the configuration would be as follows:

Router>enable

Router#config t

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)#hostname RTA

RTA(config)#int s 0/0/0

RTA(config-if)#ip address 10.1.1.1 255.255.255.252

RTA(config-if)#no shutdown

RTA(config-if)#int s 0/0/1

RTA(config-if)#ip address 10.1.1.5 255.255.255.252

RTA(config-if)#no shutdown

RTA(config-if)#int loopback 0

RTA(config-if)#ip address 172.16.1.1 255.255.255.0

RTA(config-if)#exit

RTA(config)#

Step 2 – Basic OSPF Configuration

a.      Continue from Step 1 or open the file MultiAreaOSPF-Step2.pkt to begin configuring OSPF.  The initial configuration will combine RTA, RTB, and RTC into a single area (Area 0, the Backbone).

b.      Configure the serial interfaces on RTA to participate in OSPF.

RTA(config)#router ospf 1

RTA(config-router)#network 10.1.1.0 0.0.0.3 area 0

RTA(config-router)#network 10.1.1.4 0.0.0.3 area 0

RTA(config-router)#exit

RTA(config)#

c.       Now configure the serial interfaces on RTB to participate in OSPF.

RTB#config t

Enter configuration commands, one per line.  End with CNTL/Z.

RTB(config)#router ospf 1

RTB(config-router)#network 10.1.1.0 0.0.0.255 area 0

RTB(config-router)#exit

RTB(config)#

01:03:54: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.1.1 on Serial0/0/0 from LOADING to FULL, Loading Done

What is the difference in the network statements used to enable OSPF on RTA and those used on RTB?  Would you have been able to use the same command on RTB if you did not want OSPF to run on the link between RTB and RTC?

d.      Now configure the serial interfaces on RTC to also participate with OSPF.

RTC(config)#router ospf 1

RTC(config-router)#network 10.1.1.0 0.0.0.255 area 0

RTC(config-router)#

01:26:48: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.1.1 on Serial0/0/1 from LOADING to FULL, Loading Done

01:26:48: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.0.1 on Serial0/0/0 from LOADING to FULL, Loading Done

Notice the adjacency changes for RTC’s neighbors when OSPF was configured.  Where did the Router ID values for RTA and RTB come from?  Which interface is 172.16.1.1 assigned to?  Which interface is 192.168.0.1 assigned to?  What command can we use to change the Router ID values so that interface values are not used?

e.       Verify that OSPF is working for RTA, RTB, and RTC in area 0.   You can use various show commands, such as show ip route, or show ipospf neighbor.  Notice there is currently only one OSPF route in the routing table for each router.

RTA#showip route

     10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks

C       10.1.1.0/30 is directly connected, Serial0/0/0

L       10.1.1.1/32 is directly connected, Serial0/0/0

C       10.1.1.4/30 is directly connected, Serial0/0/1

L       10.1.1.5/32 is directly connected, Serial0/0/1

O      10.1.1.8/30 [110/128] via 10.1.1.2, 00:07:50, Serial0/0/0

                    [110/128] via 10.1.1.6, 00:07:50, Serial0/0/1

     172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks

C       172.16.1.0/24 is directly connected, Loopback0

L       172.16.1.1/32 is directly connected, Loopback0

RTA#showipospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface

192.168.0.1       0   FULL/  -        00:00:35    10.1.1.2        Serial0/0/0

192.168.4.1       0   FULL/  -        00:00:34    10.1.1.6        Serial0/0/1

RTA#

Other helpful commands to verify OSPF operation:

showipospf database

showipospf interface

debugipospfadj

debugipospf events

Step 3 – Configure OSPF Area 1

a.      Continue from Step 2 or open the file MultiAreaOSPF-Step3.pkt to configure OSPF area 1.

b.      On RTA, configure a default route for the internet interface on loopback 0.  Configure OSPF to send this route to other OSPF routers.

RTA(config)#ip route 0.0.0.0 0.0.0.0 loopback 0

RTA(config)#router ospf 1

RTA(config-router)#default-information originate

c.        Check the routing tables on RTB and RTC.  What route has now been added to the routing table for each router?  What is the type of OSPF route that has been added?  What is the LSA type associated with this type of route?  What is the metric?

d.       Configure OSPF on RTB and RTD to include the appropriate interfaces in area 1.

RTB(config)#router ospf 1

RTB(config-router)#network 192.168.0.0 0.0.0.255 area 1

RTD(config)#router ospf 1

RTD(config-router)#network 192.168.0.0 0.0.0.255 area 1

RTD(config-router)#network 192.168.1.0 0.0.0.255 area 1

RTD(config-router)#exit

00:24:40: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.0.1 on GigabitEthernet0/0 from LOADING to FULL, Loading Done

e.      Verify that RTD has both inter-area routes (IA) and the external (E2) route displayed in the routing table.

RTD#shoip route

Gateway of last resort is 192.168.0.1 to network 0.0.0.0

     10.0.0.0/30 is subnetted, 3 subnets

O IA    10.1.1.0/30 [110/65] via 192.168.0.1, 00:00:07, GigabitEthernet0/0

O IA    10.1.1.4/30 [110/129] via 192.168.0.1, 00:00:07, GigabitEthernet0/0

O IA    10.1.1.8/30 [110/65] via 192.168.0.1, 00:00:07, GigabitEthernet0/0

     192.168.0.0/24 is variably subnetted, 2 subnets, 2 masks

C       192.168.0.0/24 is directly connected, GigabitEthernet0/0

L       192.168.0.2/32 is directly connected, GigabitEthernet0/0

     192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks

C       192.168.1.0/24 is directly connected, Loopback0

L       192.168.1.1/32 is directly connected, Loopback0

O*E2 0.0.0.0/0 [110/1] via 192.168.0.1, 00:00:07, GigabitEthernet0/0

f.        View the Link State Database on RTD with the command show ipospf database.  What is the LSA type associated with the inter-area (IA) routes?  Which LSA type is associated with the default route advertised by RTA?

Step 4 – Configure OSPF Area 2.  Configure the area as a Stub area.

a.      Continue from Step 3 or open the file MultiAreaOSPF-Step4.pkt to configure OSPF area 2.

b.      Configure RTC for OSPF operation on Gigabit Ethernet 0/0 in area 2.

RTC(config)#router ospf 1

RTC(config-router)#network 192.168.4.0 0.0.0.255 area 2

RTC(config-router)#area 2 stub

c.       Configure RTE for OSPF operation in area 2.

RTE(config)#router ospf 1

RTE(config-router)#network 192.168.4.0 0.0.0.255 area 2

RTE(config-router)#network 192.168.5.0 0.0.0.255 area 2

RTE(config-router)#area 2 stub

d.      Use the show ip route command on RTE to verify that OSPF routing information has been received from RTC.  Is there any difference between the number and type of routes shown when compared to those previously seen on RTD?  Does RTE have any routes listed that are in area 1?

e.      Use the show ipospf database command on RTE to view the LSA types received.  Are there differences in the LSAs received by RTE when compared to those previously seen on RTD?

f.        On RTD, use the show ip route command to view the current routing table.  Does RTD have any routes listed that are in area 2?

g.      Verify on RTD that you are able to reach both the route for the internet (172.16.1.1) and the route for the LAN on RTE (192.168.5.1).

RTD#ping 172.16.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/6/11 ms

RTD#ping 192.168.5.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.5.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/9 ms

h.      Verify on RTE that you are able to reach both the route for the internet (172.16.1.1) and the route for the LAN on RTC (192.168.1.1).

RTE#ping 172.16.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/10 ms

RTE#ping 192.168.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/6 ms

i.        Change area 2 to be configured as a totally-stubby area.

RTC(config)#router ospf 1

RTC(config-router)#area 2 stub no-summary

j.        Use the show ip route command on RTE to view the changes to the routing table now that area 2 is configured as totally-stubby.

RTE#ship route

Gateway of last resort is 192.168.4.1 to network 0.0.0.0

     192.168.4.0/24 is variably subnetted, 2 subnets, 2 masks

C       192.168.4.0/24 is directly connected, GigabitEthernet0/0

L       192.168.4.2/32 is directly connected, GigabitEthernet0/0

     192.168.5.0/24 is variably subnetted, 2 subnets, 2 masks

C       192.168.5.0/24 is directly connected, Loopback0

L       192.168.5.1/32 is directly connected, Loopback0

O*IA 0.0.0.0/0 [110/2] via 192.168.4.1, 00:14:04, GigabitEthernet0/0

Notice that since RTE has 192.168.4.0 and 192.168.5.0 networks directly connected, there are no OSPF routes listed with the ‘O’ designation (intra-area).  Which route will be used to reach networks in area 0, area 1, and the internet?

Verify that both the 192.168.1.1 and 172.16.1.1 routes are still reachable.

RTE#ping 192.168.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms

RTE#ping 172.16.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/9 ms

k.       On RTE, use the show ipospf database command to view the LSA types now being sent from RTC.  How does changing the type of area affect the LSA types seen in that area?

Step 5 – Configure area 2 as an NSSA. 

a.      Continue from Step 4 or open the file MultiAreaOSPF-Step5.pkt to configure area 2 as a Not So Stubby Area (NSSA).

b.      On RTE, network 192.168.5.0 will now be used to reach a network that is not native to OSPF.  This would normally create a type 5 LSA (same as that used for the internet connection 172.16.1.1), but type 5 LSAs are not allowed in stub or totally-stubby areas.  Remove network 192.168.5.0 from OSPF and add it to EIGRP in AS 100.

RTE(config)#router ospf 1

RTE(config-router)#no network 192.168.5.0 0.0.0.255 area 2

RTE(config-router)#exit

RTE(config)#router eigrp 100

RTE(config-router)#network 192.168.5.0 0.0.0.255

c.       RTD now will not be able to reach the 192.168.5.1 address on RTE as it is no longer being advertised.

RTD#ping 192.168.5.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.5.1, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

d.      Change the area type for area 2 to be an NSSA area, first by removing the configuration for totally stubby, then by adding the NSSA configuration.

RTE(config)#router ospf 1

RTE(config-router)#no area 2 stub

RTE(config-router)#area 2 nssa

RTC(config)#router ospf 1

RTC(config-router)#no area 2 stub no-summary

RTC(config-router)#area 2 nssa

Note:  If necessary you can force OSPF to renegotiate neighbor connections by shutting down the link between neighbors, or reload one (or both) routers.

e.      Redistribute the EIGRP route into OSPF on RTE to allow it to be advertised throughout the OSPF network.

RTE(config)#router ospf 1

RTE(config-router)#redistribute eigrp 100 subnets

RTE(config-router)#

f.        Verify that RTD can now once again reach the 192.168.5.1 address.

RTD#ping 192.168.5.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.5.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/6/12 ms

(Note that since we have not redistributed any routes from OSPF into EIGRP, if this was for an ethernet or serial interface full connectivity would not be achieved beyond this network.)

g.      On RTD, what is the type of route associated with the 192.168.5.0 network?  Use the show ip route command.  Using the show ipospf database command, what type of LSA is being used for RTD to learn of this network?

Network 192.168.5.0

Routing Table -  Network Type:

LSDB -  LSA Type:

h.      On RTC, what is the type of route associated with the 192.168.5.0 network?  Use the show ip route command.  Using the show ipospf database command, what type of LSA is being used for RTD to learn of this network?

Network 192.168.5.0

Routing Table -  Network Type:

LSDB -  LSA Type:

Aggregation, Load Balancing, and Redundancy

EtherChannel has numerous advantages, the most probable being bandwidth aggregation. Learn EtherChannel aggregation techniques including PAgP and LACP as defined by Cisco and IEEE 802.3ad. Compare methods used to include load balancing and redundancy techniques on physical switches and connecting to the virtual data center. Explore configuration examples which include both Layer 2 and Layer 3 connectivity. Participants will demonstrate basic EtherChannel concepts using a Packet Tracer activity. Second place GIR Contest regional winner United States and Canada.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

EtherChannel: Aggregation, Load Balancing, and Redundancy 

Click here to download topology  Topology of EtherChannel: Aggregation, Load Balancing, and Redundancy

Topology Diagram

Addressing Table:

Host	Interface	Address
MLS1	G0/1	172.16.1.1/30
	VLAN 10	192.168.10.1/24
	VLAN 20	192.168.20.1/24
R1	G0/1	172.16.1.2/30
	G0/0.20	192.168.30.1/24
	G0/0.30	192.168.30.1/24
PC1-V10	Ethernet	192.168.10.5
PC2-V10	Ethernet	192.168.10.6
PC3-V20	Ethernet	192.168.20.5
PC4-V20	Ethernet	192.168.20.6
PC5-V10	Ethernet	192.168.10.7
PC6-V10	Ethernet	192.168.10.8
PC7-V20	Ethernet	192.168.20.7
PC8-V20	Ethernet	192.168.20.8
PC10-V30	Ethernet	192.168.30.5
PC11-V30	Ethernet	192.168.30.6
PC12-V40	Ethernet	192.168.40.5
PC13-V40	Ethernet	192.168.40.6

In this lab all PCs have been assigned their associated IP addresses as static.  Instructors may decide to add appropriate requirements to enable a DHCP server with helper-addresses on router interfaces or use DHCP services on the layer 3 devices.

Introduction:

When a switched network spans multiple switches, a method of linking those switches must be used.  A Fast Ethernet, Gigabit Ethernet or 10Gigabit Ethernet port can be used to uplink between switches, but this introduces a bottleneck to the flow of traffic.  To demonstrate try using a 24-port 2960 switch having 23 Fast Ethernet ports sending traffic over a single Fast Ethernet link to another switch. 

Unfortunately when we connect two or more ports from one switch to another spanning-tree will place one port into blocking state to protect against a layer 2 loop. 

The initial configuration of this lab could vary depending on the instructors intended use.  This Packet Tracer file could be used to present a number of switching related topics: VLANs, Trunking, VTP, InterVLAN routing, and EtherChannel.

Review the address design.  In an effort to save time for this demonstration the PCs have been configured with appropriate addresses and default gateways.  The following tasks/objectives will need to be performed:

• Enable each switch as VTP Transparent Mode
• Create the proper VLANs on each Transparent mode switch
• Create Trunks for each port interconnecting switches
• Create Etherchannels to aggregate trunks between switches
• Confirm or configure load-balance method for Etherchannels
• Troubleshoot if needed

Part 1 Prepare the switches

Step 1. Enable each switch as VTP Transparent Mode

SW1(config)#vtp mode transparent
Setting device to VTP TRANSPARENT mode

Step 2.  Create Appropriate VLANs on each switch.

SW1(config)#vlan 10
SW1(config-vlan)#vlan 20
SW1(config-vlan)#exit

Repeat for each switch – MLS1, SW2,  Create VLAN 30, 40 on SW3, SW4

Step 3. Assign Access VLANs to the appropriate ports on each switch

SW1(config)#int range fa0/5 - 6

SW1(config-if-range)#switchport mode access

SW1(config-if-range)#switchport access vlan 10

SW1(config-if-range)#spanning-tree portfast

%Warning: portfast should only be enabled on ports connected to a single

 host. Connecting hubs, concentrators, switches, bridges, etc... to this

 interface  when portfast is enabled, can cause temporary bridging loops.

 Use with CAUTION

%Portfast will be configured in 2 interfaces due to the range command

 but will only have effect when the interfaces are in a non-trunking mode

Repeat for fa0/7 – 8 and assign vlan 20, complete the same task on SW2.  On SW3 assign fa0/5 – 6 vlan 30 and on SW4 assign fa0/5 – 6 vlan 40

Step 4. Create Trunk links between switches

MLS1(config)#int range fa0/1 – 4
MLS1(config-if-range)#switchport trunk encap dot1q
MLS1(config-if-range)#switchport mode trunk

SW1(config-if-range)#int range fa0/1 – 2
SW1(config-if-range)#switchport mode trunk

SW2(config-if-range)#int range fa0/3 – 4
SW2(config-if-range)#switchport mode trunk

Now test the default spanning-tree results:  output may vary!

SW2#sho spanning-tree vlan 1

VLAN0001
  Spanning tree enabled protocol ieee
  Root ID    Priority    32769
             Address     000A.4139.EE2E
             Cost        19
             Port        3(FastEthernet0/3)
             Hello Time  2 sec  Max Age 20 sec  Forward Delay 15 sec

  Bridge ID  Priority    32769  (priority 32768 sys-id-ext 1)
             Address     000C.8511.C2C9
             Hello Time  2 sec  Max Age 20 sec  Forward Delay 15 sec
             Aging Time  20

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- --------------------------------
Fa0/3            Root FWD 19        128.3    P2p
Fa0/4            Altn BLK 19          128.4    P2p

PART 2 Create Etherchannels

Step 1:  Use PAgP for etherchannel between MLS1 and SW1

MLS1(config)#int range fa0/1 – 2
MLS1(config-if-range)#channel-protocol pagp
MLS1(config-if-range)#channel-group 1 mode desirable
MLS1(config-if-range)#
Creating a port-channel interface Port-channel 1

SW1(config)#int range fa0/1 – 2
SW1(config-if-range)#channel-protocol pagp
SW1(config-if-range)#channel-group 1 mode auto
SW1(config-if-range)#
Creating a port-channel interface Port-channel 1

Step 2:  Use LACP for etherchannel between MLS1 and SW2

MLS1(config)#interface range fa0/3 – 4
MLS1(config-if-range)#channel-protocol lacp
MLS1(config-if-range)#channel-group 2 mode active
MLS1(config-if-range)#
Creating a port-channel interface Port-channel 2

SW2(config)#int range fa0/3 – 4
SW2(config-if-range)#channel-protocol lacp
SW2(config-if-range)#channel-group 2 mode passive
SW2(config-if-range)#
Creating a port-channel interface Port-channel 2

Step 3.  Use manual ON for etherchannel between SW3 and SW4.

SW3(config)#int range fa0/1 – 2
SW3(config-if-range)#channel-group 3 mode on
SW3(config-if-range)#
Creating a port-channel interface Port-channel

SW4(config-if-range)#channel-group 3 mode on
SW4(config-if-range)#
Creating a port-channel interface Port-channel 3

Step 4.  Take another look at spanning-tree and verify the port-channel interfaces have the least cost path and there are no ports in blocking state.  This is an indication that all uplink ports are in use.  Check each switch.  Output may vary.

SW2#show spanning-tree
.
.
VLAN0010
  Spanning tree enabled protocol ieee
  Root ID    Priority    32778
             Address     000A.4139.EE2E
             Cost        9
             Port        27(Port-channel 2)
             Hello Time  2 sec  Max Age 20 sec  Forward Delay 15 sec

  Bridge ID  Priority    32778  (priority 32768 sys-id-ext 10)
             Address     000C.8511.C2C9
             Hello Time  2 sec  Max Age 20 sec  Forward Delay 15 sec
             Aging Time  20

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- --------------------------------
Fa0/5            Desg FWD 19        128.5    P2p
Fa0/6            Desg FWD 19        128.6    P2p
Po2              Root FWD 9         128.27   Shr

Step 5.  Verify that EtherChannel is working.

SW2#sho etherchannel summary
Flags:  D - down        P - in port-channel
        I - stand-alone s – suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port

Number of channel-groups in use: 1
Number of aggregators:           1

Group  Port-channel  Protocol    Ports
---------+------------------+-------------+----------------------------------------------
2            Po2(SU)          LACP           Fa0/3(P)   Fa0/4(P)

Note:  if the EtherChannel does not come up, you might want to try shutting down the physical interfaces on both ends of the EtherChannel.  Using the “shut” , “no shut” commands. 

Also use:

MLS1#sho interface trunk
Port        Mode         Encapsulation  Status        Native vlan
Po1         on             802.1q               trunking      1
Po2         on             802.1q               trunking      1

Port        Vlans allowed on trunk
Po1         1-1005
Po2         1-1005

Port        Vlans allowed and active in management domain
Po1         1,10,20
Po2         1,10,20

Port        Vlans in spanning tree forwarding state and not pruned
Po1         1,10,20
Po2         1,10,20

Use the “show etherchannel port-channel command to verify aggregation state and protocol

MLS1#sho etherchannel port-channel
                Channel-group listing:
                ----------------------
Group: 1
----------
                Port-channels in the group:
                ---------------------------
Port-channel: Po1
-----------
Age of the Port-channel   = 00d:00h:40m:16s
Logical slot/port   = 2/1       Number of ports = 2
GC                  = 0x00000000      HotStandBy port = null
Port state          = Port-channel
Protocol            =   PAGP
Port Security       = Disabled

Ports in the Port-channel:

Index   Load   Port     EC state        No of bits
------+-------------+----------+-------------------+-----------
  0         00      Fa0/2    Active             0
  0         00      Fa0/1    Active             0
Time since last port bundled:    00d:00h:38m:02s    Fa0/1

Part 3 Load Balancing

Step 1:  Check the default load balance method used

SW1#sho etherchannel load-balance
EtherChannel Load-Balancing Operational State (src-mac):
Non-IP: Source MAC address
  IPv4: Source MAC address
  Ipv6: Source MAC address

Step 2:  Change the load-balance method to src-dst-ip

SW1(config)#port-channel load-balance src-dst-ip

SW1#sho etherchannel load-balance
EtherChannel Load-Balancing Operational State (src-dst-ip):
Non-IP: Source XOR Destination MAC address
  IPv4: Source XOR Destination IP address
  IPv6: Source XOR Destination IP address

Note:  Packet Tracer currently lacks support for fully testing load –balance with the following command I have placed it here for reference that could be used on live physical switches to test the load balance algorithm.

SWA# test etherchannel load-balance interface port-channel number {ip|mac} [source ip] [destination ip]
Would select Fa0/2 of Po1

Part 4 Configure the Intervlan routing

Step 1:  Turn on routing for the MLS1 switch

MLS1(config)#ip routing
MLS1(config)#int g0/1
MLS1(config-if)#no switchport
MLS1(config-if)#ip add 172.16.1.1 255.255.255.252

MLS1(config-if)#interface vlan 10
MLS1(config-if)#ip address 192.168.10.1 255.255.255.0

MLS1(config-if)#interface vlan 20
MLS1(config-if)#ip address 192.168.20.1 255.255.255.0

MLS1(config)#ip route 192.168.30.0 255.255.255.0 172.16.1.2
MLS1(config)#ip route 192.168.40.0 255.255.255.0 172.16.1.2

Step 2:  Configure R1 with intervlan routing (Router-on-a-stick)

SW4(config)#interface g1/1
SW4(config-if)#switchport mode trunk 

R1(config)#interface g0/0
R1(config-if)#no shutdown

R1(config-if)#interface g0/0.30
R1(config-subif)#encapsulation dot1q 30
R1(config-subif)#ip address 192.168.30.1 255.255.255.0

R1(config-subif)#interface g0/0.40
R1(config-subif)#encapsulation dot1q 40
R1(config-subif)#ip address 192.168.40.1 255.255.255.0

R1(config)#interface g0/1
R1(config-if)#ip address 172.16.1.2 255.255.255.252
R1(config-if)#no shutdown

R1(config)#ip route 192.168.10.0 255.255.255.0 172.16.1.1
R1(config)#ip route 192.168.20.0 255.255.255.0 172.16.1.1

Test successful pings from PC1-V10 to PC7-V20, PC10-V30, and PC12-V40.  All pings should respond successfully.  Otherwise troubleshoot appropriate etherchannel, trunks, and intervlan routing.