Use the lacp command to answer the following question

Use the LACP command to answer the following question:
2920-3(config)# show lacp peer
LACP Peer Information.
System ID: 308d99-a51361
Local Local Port Oper LACP
Port Trunk System ID Port Priority Key Mode
------ ------ -------------- ----- --------- ------- -------- -----
1/24 Trk1 70106f-8c1900 2 0 963 Active
2/24 Trk1 70106f-8c1900 12 0 963 Active
How can you tell that LACP has negotiated between the switches? __________
Tx
Timer
Slow
Slow

Technical white paper
For HPE and Channel Partner internal use only.
How can you tell both links are part of the LAG? _______________
Investigate Spanning Tree operation
2920-3(config)# show spanning-tree
Are any ports blocked by STP? ____________________
What are some of the differences between using STP vs Trunking for resiliency?
___________________________
Save your configuration.
2920-3(config)# save
2920-3(config)# exit
2920-3# exit
Testing Failover
In this section we will test resiliency and recovery of our network. We will simulate network
failures and observe how the system redirects traffic around the failure. We will also test
recovery to insure that when links are reconnected, the system automatically restores normal
operation.
 Connect your laptop to port 1/5 of your 2920 switch.
 Insure you obtain an IP address in the 10.10.130.0 network.
 Initiate a continuous ping to the Lab’s Server: ping –t 10.10.1.10
Simulate a link failure on unit 2:
 Disconnect port 2/24 on your 2920 switch.
How many pings did you drop during fail-over? _______________
Simulate recovery on unit 2:
 Reconnect port 2/24.
 Wait approximately 5 seconds
 How many pings did you drop while failing-back? ____________
Simulate a link failure on unit 1:
 disconnect port 1/24.
How many pings did you drop during fail-over? ______________
Simulate recovery on unit 1:
 Reconnect port 1/24.
How many pings did you drop during fail-back? ______________
In any of these cases, you should not have dropped more than 1 ping.

Technical white paper
For HPE and Channel Partner internal use only.
Lab 5: VLAN & IP Configuration
In this lab we will configure VLANs and IP interfaces. In most enterprise networks you will want to
configure at least a few VLANs. Some enterprises have hundreds or even thousands of VLANs.
Typically VLANs will be assigned to an application such as voice or video. Usually each VLAN will
also be a separate IP subnet. Traffic is forwarded between VLANs using IP routing. As shown in
the figure below we have defined three VLANs. Each VLAN exists on both switches. Traffic
between VLANs is routed by the IP interfaces on the 2920 switches. Although there are two 2920
switches, L2 and L3 configuration is only done once because Stacking virtualizes them into one
logical switch. VLAN and IP configuration is built on top of the existing Stacking and Trunking
topology so no additional configuration is required to implement redundancy and resiliency.
When you have completed this lab your switches will be in the configuration shown below.

Technical white paper
For HPE and Channel Partner internal use only.
Aruba O/S-Switch VLAN Configuration
In this step we will configure the VLANs and ports on your 2920 switches. Note that you only
have to configure this once to have it take effect on all switches in the stack.