0% found this document useful (0 votes)
43 views

Aruba Lab-5-1

The document describes configuring and testing Rapid Spanning Tree Protocol (RSTP) across a network topology. It provides instructions for assigning devices to VLANs, verifying the STP topology, testing link failures, and saving configurations. Key steps include enabling trunk ports, identifying the root bridge, and observing network behavior during a simulated link failure.

Uploaded by

malek
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
43 views

Aruba Lab-5-1

The document describes configuring and testing Rapid Spanning Tree Protocol (RSTP) across a network topology. It provides instructions for assigning devices to VLANs, verifying the STP topology, testing link failures, and saving configurations. Key steps include enabling trunk ports, identifying the root bridge, and observing network behavior during a simulated link failure.

Uploaded by

malek
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 7

===================================================================================

===========================
Lab 5.1: Rapid Spanning Tree Protocol
===================================================================================
===========================

=======================================================
Task 1: Assign PCs to VLAN 711
=======================================================

===================
PC-1
===================

1. Access PC-1.
2. Open Putty and open a SSH session to Core-1 (10.251.0.1) and login with
cxf7/aruba123

===================
Core-1 (via PC-1)
===================
putty: 10.251.0.1
cxf7/aruba123

Core-1# page 40

4. Confirm STP is active.


Core-1# configure terminal
Core-1(config)# show spanning-tree

===================
PC-1
===================
5. Open Putty and open a SSH session to Core-2 (10.251.0.2), and login with:
cxf7/aruba123

===================
Core-2 (via PC-1)
===================

6. Confirm STP is active.

Core-2(config)# show spanning-tree | include Spanning

===================
Access-1 and Access-2
===================
7. Repeat step 6 on Access-1 and Access-2.

T11-Access-1# show spanning-tree | include Spanning


T11-Access-2# show spanning-tree | include Spanning

8. Move back to Access-1.


===================
Access-1
===================

9. Allow VLANs 711 and 712 on interface 1/1/22 and enable the port.
*************************************************************************

T11-Access-1# configure terminal


T11-Access-1(config)# interface 1/1/22
T11-Access-1(config-if)# vlan trunk allowed 711-712
T11-Access-1(config-if)# no shutdown
T11-Access-2(config-if)# show lldp neighbor-info
T11-Access-1(config-if)# description TO_CORE-2_PORT-31

===================
Access-2
===================

12. Move to Access-2 and repeat steps 9 to 11. The remote port that interface
1/1/22 is connected to on the Core-2 side will be 1/1/31.

T11-Access-2# configure terminal


T11-Access-2(config)# interface 1/1/22
T11-Access-2(config-if)# vlan trunk allowed 711-712
T11-Access-2(config-if)# no shutdown
T11-Access-2(config-if)# show lldp neighbor-info
T11-Access-2(config-if)# description TO_CORE-2_PORT-31
T11-Access-2(config-if)#

===================
Core-1
===================
13. Use LLDP to discover the ports used for the connection to Core-2. Use a
filtered version of this command to display relevant output only.
****************************************************************
Core-1# show lldp neighbor-info | exclude 1/21

14. Move to ports 1/1/43 and 1/1/44 and make each port a trunk interface that
allows
VLANs 711 and 712.
NOTE: Replace the highlighted “X” for your table number.
Core-1(config)# interface 1/1/43-1/1/44
Core-1(config-if-<1/1/43-1/1/44>)# vlan trunk allowed 711-712
Core-1(config-if-<1/1/43-1/1/44>)# exit
Core-1(config)#
===================
Core-2
===================
15. Open the SSH session of Core-2.

16. Define the height of the page to 40 lines.


*****************************************************************
Core-2# page 40

17. Create VLAN 711 and name it T7-EMPLOYEE.


*****************************************************************
Core-2# configure terminal
Core-2(config)# vlan 711
Core-2(config-vlan-1111)# name T7_EMPLOYEES
Core-2(config-vlan-1111)# exit

18. Create VLAN 712 and name it T7_MANAGERS.


*****************************************************************
Core-2# configure terminal
Core-2(config)# vlan 712
Core-2(config-vlan-1112)# name T7_MANAGERS
Core-2(config-vlan-1112)# exit

19. Access port 1/1/Y. Make the description TO_T7-ACCESS-1_PORT-22 and make the
interface a trunk interface that allows VLANs 711 and 712.
*****************************************************************
Core-2(config)# interface 1/1/10
Core-2(config-if)# description TO_T7-ACCESS-1_PORT-22
Core-2(config-if)# vlan trunk allowed 711-712

Core-2(config)# interface 1/1/31


Core-2(config-if)# description TO_T7-ACCESS-2_PORT-22
Core-2(config-if)# vlan trunk allowed 711-712

21. Access ports 1/1/43 and 1/1/44, make the port a trunk interface that allows
VLANs 711 and 712.
*****************************************************************
Core-2(config-if)# exit
Core-2(config)# interface 1/1/43-1/1/44
Core-2(config-if-<1/1/43-1/1/44>)# vlan trunk allowed 711-712
Core-2(config-if-<1/1/43-1/1/44>)# exit

NOTICE: If you get the following error message:


Core-2(config)# interface lag 10
Core-2(config-lag-if)# vlan trunk allowed 711-712
Core-2(config-lag-if)# exit
Core-2(config)#

=======================================================
Task 2: Verify the Topology
=======================================================

1. Access the terminal session to Access-1.


*****************************************************************
===================
Access-1
===================

2. Show a filtered version of the “show spanning-tree” to get the switch MAC
address and switch priority only.
*****************************************************************

T11-Access-1# show spanning-tree | begin 1 Bridge

===================
Core-1, Core-2 and Access-2
===================

4. Repeat steps 1 and 2 with Core-1, Core-2 and Access-2.


*****************************************************************

T11-Access-2# show spanning-tree | begin 1 Bridge


Core-1# show spanning-tree | begin 1 Bridge
Core-2# show spanning-tree | begin 1 Bridge

5. On figure 5.1-2 put a start by the switch that you have identified as Root
Bridge.
Other fields you will fill out in later steps

===================
Access-1
===================

6. Move back to Access-1 and run “show spanning-tree” command. What are the path
costs of the ports?
*****************************************************************
T11-Access-1# show spanning-tree | begin 30 Port

7. All ports in this topology should have the same cost.


Write down the path costs of all links on figure 5.1-2
*****************************************************************

8. Issue the “show spanning-tree detail” command. The output will be very long.
*****************************************************************
T11-Access-1(config)# show spanning-tree detail | begin 12 "Port 1/1/21"
9. Now try now a filtered version of the “show spanning-tree detail” command in
order to find the Designated bridge on each uplink.
*****************************************************************
T11-Access-1(config)# show spanning-tree detail | begin 12 "Port 1/1/21"

===================
Access-2
===================

11. Move to Access-2 and repeat step 9.


*****************************************************************

T11-Access-2# show spanning-tree detail | begin 12 "Port 1/1/21"

12. Write down the Designated Bridge of these links on figure 5.1-2.

===================
Core-2
===================

13. Move to Core-2 and repeat step 9 for ports 1/1/43 and 1/1/44.
*****************************************************************
Core-2# show spanning-tree detail | begin 12 "Port 1/1/43"

22. On any switch run the filtered version of the “show spanning-tree” command (you
should be currently on Core-2).
*****************************************************************
Core-2# show spanning-tree | begin 12 Spanning

===================
PC-1
===================
===================
Core-1 and Core-2 (via PC-1)
===================

Core-1# show running-config | include "spanning-tree priority"


Core-2# show running-config | include "spanning-tree priority"

===================
Access-1 and Access-2
===================

24. On Access Switches, use filtered versions of the “show spanning-tree” command
for validating the roles of the ports.
*****************************************************************

T11-Access-1# show spanning-tree | exclude Disabled


T11-Access-2# show spanning-tree | exclude Disabled
===================
Core-1 and Core-2 (via PC-1)
===================

Core-1# show spanning-tree | begin 40 Port


Core-2# show spanning-tree | begin 40 Port

=======================================================
Task 3: Test Link Failure
=======================================================

Objectives
After discovering the CST topology, you should have a good idea of how traffic
flows, you will now test how resilient the network is to a failure of any uplink.

Steps
===================
PC-1
===================
1. Access PC-1 and run a continuous ping to PC-4 (10.7.12.104). Ping should be
successful.

===================
Access-1
===================
2. Move to Access-1 and use the “show spanning-tree” command to verify the current
Root port. It should be 1/1/21.
*****************************************************************
T11-Access-1# show spanning-tree | include Root

3. Disable port 1/1/21.


*****************************************************************
T11-Access-1# configure terminal
T11-Access-1(config)# interface 1/1/21
T11-Access-1(config-if)# shutdown

4. Repeat step 2.
*****************************************************************
T11-Access-1(config-if)# show spanning-tree | include Root

===================
PC-3
===================
5. Move back to PC-1 and verify the ping.

===================
Access-1
===================
6. Move to Access-1 and re-enable port 1/1/21. The topology should return to
normal.

T11-Access-1(config-if)# no shutdown
T11-Access-1(config-if)# show spanning-tree | include Root

=======================================================
Task 4: Save Your Configurations
=======================================================

Objectives
You will now proceed to save your configurations and create checkpoints. Notice
that final
lab checkpoints might be used by later activities.

Steps
===================
Access-1, Access-2, Core-1 and Core-2 (via PC-1)
===================

1. Save the current Access and Core switches’ configuration in the startup
checkpoint.

T11-Access-1# write memory


T11-Access-2# write memory

Core-1# write memory


Core-2# write memory

===================
Access-1 and Access-2
===================

2. Backup the current Access switches’ configuration as a custom checkpoint called


Lab5-1_final.

T11-Access-1# copy running-config checkpoint Lab5-1_final


T11-Access-2# copy running-config checkpoint Lab5-1_final

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!
You have completed Lab 5.1!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!

You might also like