Test

ICX 200
Ruckus ICX
Administrator
Lab Guide
Brocade University
Revision 0817
Corporate Headquarters - San Jose, CA USA
T: (408) 333-8000
info@brocade.com
European Headquarters - Geneva, Switzerland

T: +41 22 799 56 40
emea-info@brocade.com
Asia Pacific Headquarters - Singapore

T: +65-6538-4700
apac-info@brocade.com
© 2017 Brocade Communications Systems, Inc. All Rights Reserved.
ADX, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, HyperEdge, ICX, MLX,
MyBrocade, OpenScript, The Effortless Network, VCS, VDX, Vplane, and Vyatta are registered
trademarks, and Fabric Vision and vADX are trademarks of Brocade Communications Systems, Inc., in
the United States and/or in other countries. Other brands, products, or service names mentioned may be
trademarks of others.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed
or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade.
Brocade reserves the right to make changes to this document at any time, without notice, and assumes
no responsibility for its use. This informational document describes features that may not be currently
available. Contact a Brocade sales office for information on feature and product availability. Export of
technical data contained in this document may require an export license from the United States
government.
Revision 0817
Contents
Module 3 Lab: Basic Switch Administration and Stacking
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Connecting to the RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
CLI Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Command Mode Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Using the CLI Help (?) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Tab Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Abbreviating Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Configuration File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Local Account and SSH Enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Preparation for Next Lab Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Enable Stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Removing the Stacking Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Module 4 Lab: Link Aggregation Groups and VLANs

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Connecting to the RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Dynamic LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Static LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Port-based VLANs with 802.1Q Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Moving Ports Between VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Module 5 Lab: Layer 2 Redundancy

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Rapid Spanning Tree (802.1W) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Enabling Rapid Spanning Tree (802.1W) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Identify the RSTP Port Roles and States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Observe The 802.1w Failover Time Between Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Module 8 Lab: VRRP-Extended (VRRP-E)

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Prepare Devices for Lab Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configure Basic IP Connectivity for Lab Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configure Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configure Access Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configure R7-Internet Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configure VRRP-E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Analyze VRRP-E Failover Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Module 9 Lab A: OSPF Neighbor Adjacency and Link Cost

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
ICX 200 Revision 0817 iii

Connect to the RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Prepare Devices for Lab Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
OSPF Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configure OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Verify and Monitor OSPF Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
OSPF Link Cost Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Using MD5 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Module 9 Lab B: Partitioning OSPF Areas and Redistribution between RIP

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Partitioning OSPF Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Examining the OSPF LSDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Configure OSPF Area 3 on R7-Portland and R5-Seattle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configure OSPF Area 2 on R1-SaltLake and R4-SanDiego . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Verify Network Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Redistribution Between RIP and OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Configure RIP Router: R8-Vancouver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Configure ASBR: R7-Portland . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configure Internal OSPF Interfaces: R1-SaltLake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Examine the Link State Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Lab Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Module 9 Lab C: OSPF Route Summarization and Area Types

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
OSPF Address Summarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Examine Current LSDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Summarize External Networks at ASBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Summarize Internal Networks at ABR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
OSPF Area Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Configure A New External Route Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Reconfigure Normal Area 2 into a Stub Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Optional Lab: Enabling IPv6 and OSPFv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Module 15 Lab: Multi-Chassis Trunking

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Connect to the RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Prepare Devices for Lab Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Configure MCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Configure Cluster Client Link Aggregation Groups (LAGs) and VLANs . . . . . . . . . . . . . . . . . 104
Configure MCT Peer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
View MCT Statistics with Single Operational Peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Configure MCT Peer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
iv Revision 0817 ICX 200

Configure a Keepalive VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
View MCT Failover Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
ICX 200 Revision 0817 v

vi Revision 0817 ICX 200
Module 3 Lab: Basic Switch Administration and Stack-
ing
Time Allocated: 60 Minutes
Working with the switches via CLI is a preferred method for many administrators. It allows for quick,
direct access and enables the scripting of tasks. This lab explores the switch CLI interfaces including
the console and Telnet, management of the switch software and configuration files as well as the
setup and access control for administrative users.
Objectives
In this laboratory exercise, you will perform tasks related to initial switch configuration and other basic
administration including:
• Establishing both serial console and Telnet management sessions to the switches
• Understanding CLI basics
• Managing system software
• Managing configuration files
• Controlling user access
Revision 0817 ICX 200 1

Connecting to the RSL
If you are not already connected, use the instructions in your Student Information Sheet to reconnect
to your RSL station.
CLI Basics
The following sections will introduce the multiple aspects of the CLI including the available commands
at each command mode level and how to retrieve command help.
Command Mode Hierarchy

Moving to lower configuration modes is accomplished one step at a time. You can only move down one
level with each command entry. But you can move all the way back to the top in a single move. This
section demonstrates the steps.
1. On the PC1 Remote Desktop session, click putty and locate the RKUS04-Console saved
connection. On the terminal window that appears, press the return key until you see the device
prompt.
RKUS-04>
• What is your current prompt?

____________________________________________________________________1
• Which mode does the “>” in the prompt represent?
____________________________________________________________________2
2. On RKUS-04, enter the Privileged EXEC mode by issuing the enable command.
RKUS-04> enable
No password has been assigned yet...
• How has the prompt changed?

____________________________________________________________________3
3. On RKUS-04, step down to the Global Configuration mode by entering the configure
terminal command.
RKUS-04# configure terminal
• How did the prompt change?

____________________________________________________________________4
1. RKUS-04>
2. User EXEC mode.
3. The “No password has been assigned yet...” message is displayed. The prompt now ends with a “#” sign.
4. RKUS-04(config)# The (config) has been added to indicate that you are now in Global Configuration mode.
2 Revision 0817 ICX 200

4. On RKUS-04, step down from here to the Interface Configuration mode by entering the
interface ethernet 1/1/1 command.
RKUS-04(config)# interface ethernet 1/1/1
• How did the prompt change?

____________________________________________________________________5
5. On RKUS-04, move back up one level with the exit command. This places you back into the
Global Configuration mode. Your prompt should again contain (config), indicating that you are
in Global Configuration mode.
RKUS-04(config-if-e1000-1/1/1)# exit
RKUS-04(config)#
6. On RKUS-04, move back to the interface configuration mode by entering the interface
ethernet 1/1/1 command.
7. On RKUS-04, return directly to the Privileged EXEC mode by pressing CTRL+Z at the same time.
This will change your prompt back to #. (optionally use the command end with the same results)
RKUS-04(config)# interface ethernet 1/1/1
RKUS-04(config-if-e1000-1/1/1)# ^Z
RKUS-04#
8. On RKUS-04, try to move directly to the Interface Configuration mode from the Privileged EXEC
mode by entering the configure terminal interface ethernet 1/1/1 command.
RKUS-04# configure terminal interface ethernet 1/1/1
• What was the response?

____________________________________________________________________6
Using the CLI Help (?)

At any point during your CLI session you can get help in completing commands, learning syntax or
getting command descriptions by using the ‘?’ entry. This section demonstrates how the ‘?’ can be
used.
9. On RKUS-04, at the Privileged EXEC mode prompt enter the ? command. This displays a list of
available commands at this level of configuration mode.
5. RKUS-04(config-if-e1000-1/1/1)# The (conf-if-e1000-1/1/1) has been added to indicate that you are
now in Interface Configuration mode ready to edit STACKID 1, SLOT 1, PORT interface 1.
6. Invalid input -> int eth 1/1/1. You are only allowed to move down one level at a time.

10. On RKUS-04, to display available command syntax and options enter the “?” after the end of a
particular command. Enter the configure ? command (there is a space before the ?).
RKUS-04# configure ?
terminal Configure thru terminal
Notice that terminal is the available operand to directly follow the configure command. Also
find that the prompt automatically returns with the configure command waiting for the next
operand.
11. On RKUS-04, complete the configure command by entering the terminal operand to enter
the switch configuration mode.
RKUS-04(config)#
12. On RKUS-04, enter the exit command to return to the Privileged EXEC prompt.
13. On RKUS-04, use the ? command to show which commands are available with a certain prefix.
Enter the co? command (no space before the ?) to see a list of commands that start with ‘co’.
• What operands are available? ________________________________________7
RKUS-04# co?
configure Enter configuration mode
copy Copy between flash, tftp, config/code
14. On RKUS-04, when the prompt returns with ‘co’, press the [Enter] key without adding any
additional characters.
• What is the response?
____________________________________________________________________8
RKUS-04# co
Ambiguous input -> co
7. Configure and copy.

8. An Ambiguous input -> co error is returned.

Tab Completion
CLI commands can be completed automatically by using the [Tab] key. While typing a command
pressing [Tab] either completes the entry of the command, if it has a unique prefix, or it offers
available commands that start with the prefix entered. This section of the lab demonstrates this use.
15. On RKUS-04, from the Privileged EXEC # prompt type co then press the [Tab] key. This should
display the available configure and copy commands.
16. On RKUS-04, complete the returned co command by entering n and then pressing the [Tab] key
again.
RKUS-04# con [Tab]
configure Enter configuration mode
RKUS-04# configure

____________________________________________________________________9
17. On RKUS-04, tab completion can also automatically enter the next operand for the command if
there is only one available. Press the [Tab] key again here.
RKUS-04# configure [Tab]
terminal Configure thru terminal

____________________________________________________________________10
18. On RKUS-04, press CTRL+U to clear the command from the prompt.
RKUS-04#
9. Tab completion finishes the configure command since con is unique to it.
10. Tab completion finishes the configure command by adding terminal since it is the only available operand
for configure.

Abbreviating Commands
Abbreviating CLI commands can save time by only typing just enough characters to make the prefix
unique to a specific command. This section demonstrates how to use the abbreviations.
If the abbreviations you enter are not unique to specific commands you get the ambiguous command
error witnessed earlier.
19. On RKUS-04, enter the Global Configuration mode from the Privileged EXEC mode using
abbreviations enter the conf t command.
RKUS-04# conf t
RKUS-04(config)#
Note
Remember from earlier the full command is actually configure terminal.
20. On RKUS-04, enter the exit command to return to the Privileged EXEC mode.
Configuration File Management

Switch configurations and changes to the configuration should be backed up. This section
demonstrates the movement and backup/restore actions for the switch configurations.
21. On RKUS-04, use Privileged EXEC mode to display the contents of the configuration file currently
running on the system, enter the show running-config command.
RKUS-04# show running-config
Current configuration:
!
ver 08.0.30hT211
!
stack unit 1
module 1 icx7250-24p-poe-port-management-module
module 2 icx7250-sfp-plus-8port-80g-module
!
!
hostname RKUS-04
!
!
interface management 1
disable
!
interface ethernet 1/1/1
disable
!
disable
!
disable
!
disable
!

disable
!
disable
!
disable
!
disable
!
disable
!
disable
<Output truncated>
!
!
end
Note
The contents of the configuration is a list of CLI commands that reflect the current state of
each item.
• Do you have an entry for interface ethernet 1/1/9? (Yes / No)11

22. On RKUS-04, display the contents of the configuration stored in flash, which is used during
startup, enter the show configuration command.
The running and the startup configurations are currently the same.
23. On RKUS-04, change the configuration by assigning an IP address to the switch and enabling
interface eth 1/1/9.
RKUS-04# conf t
RKUS-04(config)# ip address 10.10.200.20/24
RKUS-04(config)# int eth 1/1/9
NOTE
The full syntax is interface ethernet 1/1/9
RKUS-04(config-if-e1000-1/1/9)# enable
RKUS-04(config-if-e1000-1/1/9)# end
RKUS-04#
24. On RKUS-04, compare the two configurations. To display the contents of the configuration file
currently running on the system, enter the show running-config command.
RKUS-04# show running-config
11. Yes, interface e 1/1/9 is disabled

12. Yes, interface e 1/1/9 is disabled
13. No

!
ver 08.0.30hT211
<Truncated Output>
!
disable
!
disable
<Truncated Output>
25. On RKUS-04, display the contents of the configuration stored in flash using the show
configuration command.
RKUS-04# show configuration
Startup configuration:
!
ver 08.0.30hT211
<Truncated Output>

disable
!
disable
<Truncated Output>
26. On RKUS-04, save the current running configuration to the startup configuration by entering the
write memory command.
27. On RKUS-04, display the contents of the configuration stored in flash using the show
configuration command.
!
ver 08.0.30hT211
<Truncated Output>

disable
!
disable
<Truncated Output>
14. Yes
15. No

You can use TFTP from Privileged EXEC mode to backup configuration files. The TFTP server for this
RSL is at 10.10.200.100.
28. On RKUS-04, use the end command to return to the Privileged EXEC mode.
29. On RKUS-04, enter the copy running-config tftp 10.10.200.100
b4_backup1.txt command.
The following message is displayed: Upload running-config to TFTP server done.
30. On RKUS-04, enable port 1/1/8
RKUS-04# conf t
RKUS-04(config)# int eth 1/1/8
RKUS-04(config-if-e1000-1/1/8)# end
31. On RKUS-04, write the current running configuration to the startup configuration by entering the
write memory command.
32. On RKUS-04, enter the show configuration command. Notice that the entry for interface
ethernet 1/1/8 is now gone.
!
ver 08.0.10hT7f1
<Truncated Output>

disable
!
disable
<Truncated Output>
33. On RKUS-04, enter the copy tftp startup-config 10.10.200.100

b4_backup1.txt command from Privileged EXEC mode (#) to restore a backed up
configuration to the startup-config.
The following message is displayed: Download startup-config from TFTP server
done.
34. On RKUS-04, enter the show configuration command. Notice that the entry for interface
ethernet 1/1/8 is now back.
!
ver 07.4.00T7f1
<Truncated Output>

disable
!
disable

<Truncated Output>
Local Account and SSH Enablement

SSH access requires authentication either by a local account or by an authentication server. In the
next few steps you will enable SSH by generating a crypto key, configure a local account and configure
AAA parameters.
35. On RKUS-04, create a local account with Super User access by entering the following command:
RKUS-04(config)# username admin1 privilege 0 password icx200
Note
The privilege level options are 0-Super User, 4-Port Configuration, 5-Read-only
36. On RKUS-04, configure AAA authentication to consult local user accounts for access by entering
the following command:
RKUS-04(config)# aaa authentication login default local
37. On RKUS-04, enable SSH by generating a crypto key that will be used for SSH connectivity.
RKUS-04(config)# crypto key generate
Creating DSA key pair, please wait...
DSA Key pair is successfully created
Note
It will take a few moments before you received the confirmation that the key pair was suc-
cessfully generated.
38. On RKUS-04, verify your configuration by issuing the show ip ssh config command. (For
this command the config is not abbreviated and is the full command syntax.)
RKUS-04(config)# show ip ssh config
SSH server : Enabled
SSH port : tcp\22
Host Key : DSA 1024, RSA 2048
Encryption : aes256-cbc, aes192-cbc, aes128-cbc, aes256-ctr,
aes192-ctr, aes128-ctr, 3des-cbc
Permit empty password : No
Authentication methods : Password, Public-key, Interactive
Authentication retries : 3
Login timeout (seconds) : 120
Idle timeout (minutes) : 0
SCP : Enabled
<Output Truncated>

39. On the PC1 Desktop, double-click on the PuTTY application icon and connect to RKUS-04 using
the ssh parameters below:
• Type 10.10.200.20 in the Host Name (or IP address) field
• Select SSH for Connection type
• Click Open
• Click Yes on the security message that pops up
40. On the PC1 PuTTY session window, you should be prompted to login. Log in using the credentials
username: admin1 password: icx200 as seen below.
login as: admin1
Using keyboard-interactive authentication.
Password: icx200
41. On the PC1 PuTTY session window, enter into privileged exec mode by issuing the command
enable.
a. Were you prompted for a password?____________16
42. On the PC1 PuTTY session window, configure AAA authentication for enable mode by entering the
following command:
SSH@RKUS-04# config t
SSH@RKUS-04(config)# aaa authentication enable default local
43. On the PC1 PuTTY session window, return to User EXEC mode by issuing the quit command.
Once at the > prompt issue to enable command once again.
a. Were you prompted for credentials? ____________17
b. Enter the credentials above again to gain Privilege EXEC access.
16. No
17. yes

Preparation for Next Lab Section
44. On the PC1 PuTTY session window, clear the AAA configuration for the next lab.
SSH@RKUS-04# config t
SSH@RKUS-04(config)# no aaa authentication enable default local
SSH@RKUS-04(config)# no aaa authentication login default local
45. On the PC1 PuTTY session window, save the running-configuration.
SSH@RKUS-04(config)# write mem
46. On the PC1 PuTTY session window, close the SSH connection window.
Enable Stacking
This portion of the lab you will enable the stacking ports and form a switch stack using the secure
setup feature.
• Enable stacking ports
• Enable stacking on a switch (planned active switch)
• Configure stack using the secure stack feature
Utilizing the following CLI commands:
Command Context Comment

stack enable Global Configuration Enables stacking to be configured
stack secure-setup Any Stack setup automation
show stack Any Display stack details
show stack neighbors Any Shows neighbors in stack
show stack stack-ports Any Shows stack port order
show int stack-ports Any Shows ports within the stack
47. On RKUS-03, RKUS-04 and RKUS-05, connect to the console, define and enable the stacking
ports for the switches and reload.
RKUS-04> enable
RKUS-04# conf t
RKUS-04(config)# stack unit 1
RKUS-04(config-unit-1)# default-ports 1/2/1 1/2/3
Reload required. Please write memory and then reload or power cycle.
RKUS-04(config-unit-1)# stack-trunk 1/2/1 to 1/2/2
RKUS-04(config-unit-1)# stack-trunk 1/2/3 to 1/2/4
RKUS-04(config-unit-1)# exit
RKUS-04(config)# interface eth 1/2/1 to 1/2/4
RKUS-04(config-mif-1/2/1-1/2/4)# enable
RKUS-04(config-mif-1/2/1-1/2/4)# end
RKUS-04# write memory
Flash Memory Write (1048576 bytes per dot) .
Write startup-config done.
Copy Done.
RKUS-04# reload
Are you sure? (enter 'y' or 'n'): y

48. On RKUS-04, after the switch has reloaded, document the MAC associated with the switch by
executing the show interface brief ethernet 1/1/1 command.
____________________________________________________________________
RKUS-04> en
RKUS-04# sh int br e 1/1/1
Port Link State Dupl Speed Trunk Tag Pvid Pri MAC Name
1/1/1 Disable None None None None No 1 0 0024.38b7.7040
49. On RKUS-05, document the MAC associated with the switch, by executing the show interface
brief ethernet 1/1/1 command.
____________________________________________________________________
RKUS-05> en
1/1/1 Disable None None None None No 1 0 0024.38b7.4bc0
50. On RKUS-03, document the MAC associated with the switch, by executing the show interface
brief ethernet 1/1/1 command.
____________________________________________________________________
RKUS-03> en
1/1/1 Disable None None None None No 1 0 0024.38b7.6840
51. On RKUS-03 enable stacking and initiate the stacking setup by supplying the answer to the
prompts below:
RKUS-03# config t
RKUS-03(config)# stack enable
Enable stacking. This unit actively participates in stacking
stacking is enable. optical monitoring for stacking ports 1/2/1, 1/2/
3 is not available.
RKUS-03(config)# exit
RKUS-03# stack secure-setup (also answer “2” and “y” as shown below)
RKUS-03#Discovering the stack topology...
Available UPSTREAM units
Hop(s) Id Type Mac Address
1 new ICX7450-24 0024.38b7.7040
2 new ICX7450-24 0024.38b7.4bc0
Enter the number of the desired UPSTREAM units (0-2)[0]: 2
Confirm Stacking Links...
UPSTREAM Unit: Id new at 1 hop(s) ICX7450-24P 0024.38b7.7040

Enter the desired links(1-2)[1]: 2
UPSTREAM Unit: Id new at 2 hop(s) ICX7450-24P 0024.38b7.4bc0
Enter the desired links(1-2)[1]: 2
Selected Topology:
Active Id Type Mac Address
1 ICX7450-24 0024.38b7.6840
Selected DOWNSTREAM units

Hop(s) Id Type Mac Address
1 2 ICX7450-24 0024.38b7.7040
2 3 ICX7450-24 0024.38b7.4bc0
Do you accept the unit id's (y/n)?: y

RKUS-03#
RKUS-03#T=2m49.5: Election, was alone --> active, ID=1, pri=128, 3U(1-3),
A=u1, nbr#=2 0, reason: u3: port-up, ,
The period is 25
T=2m51.3: Election, was active, no change, ID=1, pri=128, 3U(1-3), A=u1,
nbr#=2 0, reason: u1: stk-po-chg, ,
T=2m54.4: reset unit 2: u2 bo-id=1
Config changed due to add/del units. Do write mem if you want to keep it
T=2m59.4: Unit 1 loses all neighbors.
T=3m7.9: Active U1 deletes U2 and its config because it is learned.
T=3m12.1: Active U1 deletes U3 and its config because it is learned.
nbr#=2 0, reason: u2: port-up, ,
The period is 25
Detect stack unit 2 has different startup config flash, will synchronize it
T=4m47.0: Synchronize webauth files to u2
Detect stack unit 3 has different startup config flash, will synchronize it
T=4m47.0: Synchronize webauth files to u3
Detect stack member 2 POE capable
Detect stack member 3 POE capable
nbr#=2 0, reason: u1: stk-po-chg, ,
T:4m48.5: Done hot swap: active controller u1 sets u2 to Ready.
T:4m48.5: Done hot swap: active controller u1 sets u3 to Ready.
T=4m49.0: Synchronize startup config to u2
T=4m50.0: Synchronize startup config to u3
Stack unit 3 Power supply 1 is down
PoE: Stack unit 3 Power supply 2 with 748000 mwatts capacity is up
Config changed due to add/del units. Do write mem if you want to keep it
Stack unit 2 Power supply 1 is down

PoE: Stack unit 2 Power supply 2 with 748000 mwatts capacity is up
T=5m49.0: Assigned unit 2 to be standby
T=5m51.0: start running config sync to standby u2
T=5m51.1: Running config sync to standby u2 is complete
Important
Watch the console messages and note the tasks being performed. The message “Running con-
fig sync to standby is complete” will be displayed when the stacking configuration is
complete.
52. On RKUS-03, view the stack configuration.

RKUS-03# show stack
alone: standalone, D: dynamic cfg, S: static
ID Type Role Mac Address Pri State Comment
1 S ICX7450-24 active 0024.38b7.6840 128 local Ready
2 D ICX7450-24 standby 0024.38b7.7040 0 remote Ready
3 D ICX7450-24 member 0024.38b7.4bc0 0 remote Ready
standby active
+---+ +---+ +---+
| 3 |2/3==2/1| 2 |2/3==2/1| 1 |2/3
+---+ +---+ +---+
Standby u2 - protocols ready, can failover
Current stack management MAC is 0024.38b7.6840
a. Using the output, which switch is the active controller (based on MAC addresses recorded
earlier)? ___________18
b. How many downstream units are there? _______________________19
53. Document the unit IDs assigned. RKUS-03 should be assigned unit 1, RKUS-04 should be
assigned unit 2, and RKUS-05 should be assigned unit 3.
18. RKUS-03
19. Two

54. On RKUS-03, issue the show int brief command. Notice the unit IDs of the participating
stack devices.
RKUS-03# show interface brief | in Up
1/2/1 Up Forward Full 10G None No N/A 0 609c.9fb5.7851
1/2/2 Up Forward Full 10G None No N/A 0 609c.9fb5.7852
2/1/4 Up Forward Full 1G None No 1 0 609c.9fb4.fde3
2/1/9 Up Forward Full 1G None No 1 0 609c.9fb4.fde8
2/2/1 Up Forward Full 10G None No N/A 0 609c.9fb4.fdf9
2/2/2 Up Forward Full 10G None No N/A 0 609c.9fb4.fdfa
2/2/3 Up Forward Full 10G None No N/A 0 609c.9fb4.fdfb
2/2/4 Up Forward Full 10G None No N/A 0 609c.9fb4.fdfc
3/1/4 Up Blocked Full 1G None No 1 0 609c.9fb4.fe83
3/1/9 Up Forward Full 1G None No 1 0 609c.9fb4.fe88
3/1/10 Up Blocked Full 1G None No 1 0 609c.9fb4.fe89
3/2/3 Up Forward Full 10G None No N/A 0 609c.9fb4.fe9b
3/2/4 Up Forward Full 10G None No N/A 0 609c.9fb4.fe9c
55. On RKUS-03, identify the changes to the running configuration by issuing the show run
command. Issue CTRL+C to exit the output.
RKUS-03# show run
!
ver 08.0.30hT211
!
stack unit 1
module 1 icx7450-24-port-management-module
module 2 icx7400-xgf-4port-40g-module
module 3 icx7400-qsfp-1port-40g-module
priority 128
default-ports 1/2/1 1/2/3
stack-trunk 1/2/1 to 1/2/2
stack-port 1/2/1 1/2/3
stack unit 2
stack-port 2/2/1 2/2/3
stack unit 3
stack-port 3/2/3
stack enable

stack mac 0024.38b7.6840
!
<Truncated Output>
56. On RKUS-03, gather topology information for the stack by issuing the show stack neighbors
command.
RKUS-03# show stack neighbors
U# Stack-port1 Stack-port2
1 (1/2/1-1/2/2) to U2 (2/2/3-2/2/4) (1/2/3-1/2/4) to none
2 (2/2/1-2/2/2) to U3 (3/2/3-3/2/4) (2/2/3-2/2/4) to U1 (1/2/1-1/2/2)
3 none to none (3/2/3-3/2/4) to U2 (2/2/1-2/2/2)
a. How many stack members is unit 2 connected to? _______________20
b. What is the stack topology, linear or ring? ______________________21
57. On RKUS-03, view another output of the stack topology by issuing the show stack stack-
ports command.
RKUS-03# show stack stack-ports
standby active
+---+ +---+ +---+
| 3 |2/3==2/1| 2 |2/3==2/1| 1 |2/3
+---+ +---+ +---+
U# Stack-port1 Stack-port2
1 up (1/2/1-1/2/2) dn (1/2/3-1/2/4)
up ports: 1/2/1, 1/2/2
2 up (2/2/1-2/2/2) up (2/2/3-2/2/4)
up ports: 2/2/1, 2/2/2
up ports: 2/2/3, 2/2/4
3 none up (3/2/3-3/2/4)
up ports: 2/2/1, 2/2/2
up ports: 3/2/3, 3/2/4
20. Two. It is connected to unit 1 through port 2/2/1-2/2/2 and unit 3 through port 2/2/3-2/2/4.
21. Linear

58. On RKUS-03, view the stacking port interfaces by issuing the show int stack-ports
command.
RKUS-03# show int stack-ports
1/2/1 Up Forward Full 10G None No N/A 0 0024.38b7.6859
1/2/2 Up Forward Full 10G None No N/A 0 0024.38b7.685a
1/2/3 Down None None None None No N/A 0 0024.38b7.685b
1/2/4 Down None None None None No N/A 0 0024.38b7.685c
2/2/1 Up Forward Full 10G None No N/A 0 0024.38b7.7059
2/2/2 Up Forward Full 10G None No N/A 0 0024.38b7.705a
2/2/3 Up Forward Full 10G None No N/A 0 0024.38b7.705b
2/2/4 Up Forward Full 10G None No N/A 0 0024.38b7.705c
3/2/3 Up Forward Full 10G None No N/A 0 0024.38b7.4bdb
3/2/4 Up Forward Full 10G None No N/A 0 0024.38b7.4bdc
a. What speed are the stacking interfaces configured for? ___________22
b. What duplex is used? __________23
Removing the Stacking Configuration

Remove the stacking configuration.
59. On RKUS-03, RKUS-04 and RKUS-05, re-establish console sessions to monitor removal of the
stacking configuration.
60. On RKUS-03, which is the active controller, issue the stack unconfigure all command.
Answer y when prompted.
61. On RKUS-04 and RKUS-05, watch the consoles to see that the units are being reset to pre-
stacking configurations.
62. On RKUS-03, issue the reload command.
63. On RKUS-03, RKUS-04 and RKUS-05, disable all stacking ports.
RKUS-05> en
No password has been assigned yet...
RKUS-05# conf t
RKUS-05(config)# interface eth 1/2/1 to 1/2/4
RKUS-05(config-mif-1/2/1-1/2/4)# disable
22. 10 Gbps.
23. Full duplex.

Close Open Sessions and Exit Remote Connection
64. If you are not doing another lab at this time then please close all the GUI and CLI sessions that you
have open in your workstation.
1. Click Start > Log Off in the client window.
This ends Module 3 Lab: Basic Switch Administration and Stacking lab exercise.

Module 4 Lab: Link Aggregation Groups and VLANs
In this lab, multiple Ethernet links between switches will be combined into larger logical trunks known
as a Link Aggregation Group (LAG). These LAGs provide increased bandwidth, availability and failover.
LAGs can be either dynamic or static. A dynamic LAG is formed automatically using the Link
Aggregation Control Protocol (LACP) while static LAGs are manually configured. Both types will be
configured in the following exercise.
Additionally you will configure two VLANs across three switches, displaying the effects of VLANs
providing separation of traffic while using the same physical links.
Objectives
In this laboratory exercise, you perform tasks related to configuring LAGs:
• Configure a two port static trunk group and deploy it
• Observe failover from one trunk member to another
• Enable dynamic link aggregation on ports between a pair of switches
• Observe failover from one trunk member to another
• Disable ports within a LAG while LAG is deployed
You will also perform tasks related to configuring VLANs and tagging:
• Configure 802.1Q tagged ports and untagged ports in the same network
• Verify that traffic from multiple VLANs can use one physical link, and still be distinguishable as
separate VLAN traffic
• Change a PC’s VLAN membership without changing its physical port position
FIGURE 1 LAG Configuration Topology

Dynamic LAG
You configure a dynamic LAG using LACP between the RKUS-03 and RKUS-04 using ports 21 and 22
on each switch.
1. On RKUS-03, create a dynamic LAG and configure LACP to use a LAG Key ID you assign. (LAG ID is
optional and will be automatically assigned if not configured)
RKUS-03(config)# lag Blue dynamic id 123
2. On RKUS-03, associate ports 21 and 22 to the LAG group and identify the primary port.
RKUS-03(config-lag-Blue)# ports e 1/1/21 to 1/1/22
RKUS-03(config-lag-Blue)# primary-port 1/1/21
3. On RKUS-03, deploy the LAG on the switch.
RKUS-03(config-lag-Blue)# deploy
LAG Blue deployed successfully!
4. On RKUS-04, repeat the steps above to configure the LAG, associate eth 21 and eth 22 interfaces
and identify the primary port. Configure LACP to use a LAG Key ID of 321.
RKUS-04(config)# lag Blue dynamic id 321
RKUS-04(config-lag-Blue)# exit
5. On RKUS-04, execute the show lag command.
RKUS-04# show lag
Total number of LAGs: 1
Total number of deployed LAGs: 1
Total number of trunks created:1 (255 available)
LACP System Priority / ID: 1 / 0024.38b7.7040
LACP Long timeout: 90, default: 90
LACP Short timeout: 3, default: 3
=== LAG "Blue" ID 321 (dynamic Deployed) ===

LAG Configuration:
Ports: e 1/1/21 to 1/1/22
Port Count: 2
Primary Port: 1/1/21
Trunk Type: hash-based
LACP Key: 20321
Deployment: HW Trunk ID 1
1/1/21 Disable None None None 321 No 1 0 0024.38b7.7054
Port [Sys P] [Port P] [ Key ] [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]

1/1/21 1 1 20321 Yes S Agg Syn No No Def No Dwn

1/1/22 1 1 20321 Yes S Agg Syn No No Def No Dwn
Partner Info and PDU Statistics

Port Partner Partner LACP LACP
System MAC Key Rx Count Tx Count
1/1/21 0000.0000.0000 20 0 0
1/1/22 0000.0000.0000 21 0 0
• What is the System Priority [Sys P] of the ports? _________________1

• Are the links of the LAG status operational [Ope]? _________________2
• Why is the LAG not operational? _________________________________ 3
6. On RKUS-03 and RKUS-04 enable the primary port of each LAG.
RKUS-03(config-lag-Blue)# int e 1/1/21
RKUS-04(config-lag-Blue)# int e 1/1/21

NOTE
Because you enabled the primary port all ports that are members of the LAG are enabled. Any
configuration performed under the primary ports stanza will be reflected on all member ports.
7. On RKUS-04, reissue the show lag command and verify both ports are in operational [ope]
state.
Important
If they are not operational troubleshoot the LAG.
Do not proceed until both LAG ports are in an operational state.
8. On RKUS-03, enable the port connecting to RKUS-05

RKUS-03(config-if-e1000-1/1/21)# int e 1/1/11
9. On RKUS-05, enable the ports connecting to PC2 and RKUS-03
RKUS-05(config)# int e 1/1/9 e 1/1/11
RKUS-05(config-mif-1/1/9,1/1/11)# enable
10. On the PC1 desktop, open the command prompt and generate a continuous ping to PC2 to verify
connectivity.
C:\Documents and Settings\Administrator> ping -t 10.10.200.200
Pinging 10.10.200.200 with 32 bytes of data:
Reply from 10.10.200.200: bytes=32 time=1ms TTL=128
1. 1, this is the default setting.

2. No
3. Because the physical ports are not enabled

Important
Do not proceed unless the ping is successful
11. On RKUS-03, execute show statistics a couple of times to identify which link is carrying the
traffic.
RKUS-03(config-if-e1000-1/1/11)# show statistics
Port In Packets Out Packets In Errors Out Errors

<truncated output>
1/1/10 0 0 0 0
1/1/11 129 806 0 0
1/1/12 0 0 0 0
1/1/13 0 0 0 0
1/1/14 0 0 0 0
1/1/15 0 0 0 0
1/1/16 0 0 0 0
1/1/17 0 0 0 0
1/1/18 0 0 0 0
1/1/19 0 0 0 0
1/1/20 0 0 0 0
1/1/21 366 819 0 0
1/1/22 101 134 0 0
1/1/23 0 0 0 0
1/1/24 0 0 0 0
1/2/1 0 0 0 0
1/2/2 0 0 0 0
mgmt1 10 0 0 0
TOTAL 1380 1806 0 0
• Which link is carrying the ping traffic? _______________4

12. On RKUS-04, disable the port that is carrying the traffic identified above.
RKUS-04(config-if-e1000-1/1/21)# lag Blue
RKUS-04(config-lag-Blue)# disable e 1/1/21
13. On RKUS-04, verify that the disabled port is not operational in the lag by issuing the show lag
command.
RKUS-04(config-lag-Blue)# show lag
=== LAG "Blue" ID 321 (dynamic Deployed) ===

LAG Configuration:
Ports: e 1/1/21 to 1/1/22
Port Count: 2
LACP Key: 20321
4. Port 21 will most likely be carrying the traffic.

1/1/22 Up Forward Full 1G 321 No 1 0 0024.38b7.7054
Port [Sys P] [Port P] [ Key ] [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]

1/1/21 1 1 20321 Yes L Agg Syn No No Def No Dwn
1/1/22 1 1 20321 Yes L Agg Syn Col Dis No No Ope
Partner Info and PDU Statistics

Port Partner Partner LACP LACP
System MAC Key Rx Count Tx Count
1/1/21 0000.0000.0000 20 67 67
1/1/22 0024.38b7.6840 20123 100 100
• Why was it important to disable the port within the LAG stanza and not under the physical
port?________________5
14. On RKUS-03 and RKUS-04, remove the lag configuration and disable the ports to prepare for the
next section.
Example:
RKUS-03(config-if-e1000-1/1/11)# no lag Blue
Secondary port 1/1/22 disabled automatically upon LAG un-deploy to
avoid potential loop
LAG Blue un-deployed successfully!
RKUS-03(config)# int e 1/1/21
RKUS-03(config-if-e1000-1/1/21)# disable
RKUS-03(config-if-e1000-1/1/21)# exit
RKUS-03(config)#
5. Because if the port being disabled is the primary port then all ports would reflect the same configuration causing the
LAG to be disabled.

Static LAG
A static LAG will be configured between RKUS-03 and RKUS-04 using ports 1 and 2 on each switch.
15. On RKUS-03 and RKUS-04, configure a static LAG.
Example:
RKUS-03(config)# lag Green static
RKUS-03(config-lag-Green)# ports e 1/1/1 to 1/1/2
RKUS-03(config-lag-Green)# primary-port 1/1/1
RKUS-03(config-lag-Green)# deploy
LAG Green deployed successfully!
16. On RKUS-03 and RKUS-04, enable the LAG ports under the LAG stanza.
RKUS-04(config-lag-Green)# enable e 1/1/1 to 1/1/2
17. On RKUS-03, enter the show lag command.
RKUS-03(config-lag-Green)# show lag
=== LAG "Green" ID 1 (static Deployed) ===

LAG Configuration:
Ports: e 1/1/1 to 1/1/2
Port Count: 2
Primary Port: 1/1/1
1/1/1 Up Learn Full 1G 1 No 1 0 0024.38b7.6840
1/1/2 Up Learn Full 1G 1 No 1 0 0024.38b7.6840
RKUS-03(config-lag-Green)# show lag


LAG Configuration:
Ports: e 1/1/1 to 1/1/2
Port Count: 2
Primary Port: 1/1/1

• What is the Link state? Port 1 ___________ Port 2 __________ 6
• What is the State status? Port 1 ___________ Port 2 __________ 7
Note
The port’s State changes during its initialization due to the Spanning Tree Protocol. Rerun
the show lag command several times to see the state changes. This process takes approx-
imately 30 seconds to complete.
18. On RKUS-03, attempt to configure both ports of the trunk or the secondary port by entering the
int eth 1/1/1 to 1/1/2 command.
RKUS-03(config-lag-Green)# int eth 1/1/1 to 1/1/2
RKUS-03(config-lag-Green)# int e 1/1/2
• What message was returned?

____________________________________________________________________8
19. On RKUS-03 and RKUS-04, save all configurations by executing the write mem command.
Port-based VLANs with 802.1Q Tagging
VLAN 222 and VLAN 333 will be created on each of the three switches in your environment. The PCs
are dual attached to RKUS-04 and RKUS-05 on ports 9 and 10 on each switch. Port 9 of the PC
attachments will be added to VLAN 222 while port 10 will be added to VLAN 333. The links between
switches will be tagged to allow traffic from both VLANs to traverse.
Your environment begins with a static LAG between RKUS-04 and RKUS-03 with all ports on all
devices in the default VLAN 1. You are configuring the ports listed in the diagram to be members of
VLAN 222 and VLAN 333.
6. Up, Up
7. Listen, then Learn, then Forward. Final state: Forward
8. Error - cannot use the interface group to configure trunk port, 1/1/1.
and
Error - cannot configure secondary ports of a trunk

20. On RKUS-03, configure VLAN 222 and VLAN 333 with tagged ports 1 and 11:
RKUS-03(config)# vlan 222
RKUS-03(config-vlan-222)# tagged e 1/1/1
RKUS-03(config-vlan-222)# vlan 333
RKUS-03(config-vlan-333)# tagged e 1/1/1 e 1/1/11
21. On RKUS-04, configure VLAN 222 with tagged port 1 and untagged port 9 and VLAN 333 with
tagged port 1 and untagged port 10:
RKUS-04(config-lag-Green)# vlan 222
RKUS-04(config-vlan-222)# untagged e 1/1/9
• When configuring port e 1/1/1 what was unique in the message that was
returned?_________________________________________________9
Note
Because port e 1/1/1 was the primary port of the static lag, the tagging of the port to the
VLAN causes both ports of the LAG to be added to the VLAN.
22. On RKUS-04, execute the show interface brief command and look at the Tag column:
RKUS-04(config-vlan-333)# show interface brief
Port Link State Dupl Speed Trunk Tag Pri MAC

1 Up Forward Full 1G 1 Yes 0 0024.38b6.e8c0
2 Up Forward Full 1G 1 Yes 0 0024.38b6.e8c0
<Truncated Output>
• What is being reported in the Tag column for ports 1 and 2? _______10
23. On RKUS-04, execute the show vlan command.
RKUS-04(config-vlan-333)# show vlan
Total PORT-VLAN entries: 3
Maximum PORT-VLAN entries: 64
Legend: [Stk=Stack-Id, S=Slot]
PORT-VLAN 1, Name DEFAULT-VLAN, Priority level0, Spanning tree On

Untagged Ports: (U1/M1) 3 4 5 6 7 8 11 12 13 14 15 16
Untagged Ports: (U1/M1) 17 18 19 20 21 22 23 24
Untagged Ports: (U1/M2) 1 2
Tagged Ports: None
Uplink Ports: None
DualMode Ports: None
Mac-Vlan Ports: None
Monitoring: Disabled
PORT-VLAN 222, Name [None], Priority level0, Spanning tree On
Untagged Ports: (U1/M1) 9
Tagged Ports: (U1/M1) 1 2
9. Added tagged port(s) ethe 1/1/1 to 1/1/2 to port-vlan 222.

10. Yes

Uplink Ports: None
PORT-VLAN 333, Name [None], Priority level0, Spanning tree On
Untagged Ports: (U1/M1) 10
Tagged Ports: (U1/M1) 1 2
Uplink Ports: None
• Enter the member ports of VLAN 222: Untagged_________11 Tagged_________12

• Enter the member ports of VLAN 333: Untagged_________13 Tagged_________14
• How did port 2 become a tagged member of VLAN 222 and VLAN 333?
____________________________________________________________________15
24. On RKUS-04, execute the show int eth 1/1/1 command.
RKUS-04(config-vlan-333)# show int eth 1/1/1
GigabitEthernet1/1/1 is up, line protocol is up
Hardware is GigabitEthernet, address is 0024.38b7.7040 (bia
0024.38b7.7040)
Configured speed auto, actual 1Gbit, configured duplex fdx, actual fdx
Configured mdi mode AUTO, actual MDI
Member of 2 L2 VLANs, port is tagged, port state is FORWARDING
BPDU guard is Disabled, ROOT protect is Disabled
<truncated output>
• How many L2 VLANs is port 1/1/1 a member of? __________16

25. On RKUS-05, configure VLAN 222 with tagged port 11 and untagged port 9 and VLAN 333 with
tagged port 11 and untagged port 10:
11. 9
12. 1 and 2
13. 10
14. 1 and 2
15. Since ports 1 and 2 are trunked, any
configuration that you make to the primary port (in this case
port 1) will be reflected on all members of that trunk group.
16. 2

26. On the PC1 desktop, open the Command Prompt and generate a continuous ping to PC2
(10.10.200.200) to verify connectivity.
• Are the Pings successfully replied to? Yes/No17
If they are not, troubleshoot until they are.
Note
Leave the continuous ping running. You will be referring to it again later in the lab.
Important
Do not continue until you are able to ping successfully between the two PCs.
27. On the RKUS-05, disable the port that PC2 is currently using to access the network (port 9), then
enable port 10.
Note
This effectively is moving PC2 from VLAN 222 to VLAN 333.
RKUS-05(config-vlan-333)# int e 1/1/9

• Do the Pings receive replies? Yes/No18
• Why or why not?____________________________________________________________19
Moving Ports Between VLANs

Ports cannot be moved directly between user defined VLANS. Ports in user-defined VLANs must first
be removed from their current VLAN, placed back into default VLAN 1, and then placed into the new
VLAN.
28. On RKUS-05, attempt to move port 10 from VLAN 333 to VLAN 222 directly:
RKUS-05(config-if-e1000-1/1/10)# vlan 222
RKUS-05(config-vlan-222))# untagged e 1/1/10
error - port ethe 1/1/10 are not member of default vlan
RKUS-05(config-vlan-222)#
• What is the outcome? ________________________________________________20
29. On RKUS-05, remove port 10 from VLAN 333, putting it back into the default VLAN:
RKUS-05(config-vlan-333)# no untagged e 1/1/10
17. Yes
18. No
19. PC1 Pings are now kept within VLAN 222, while PC2 is now in VLAN 333.
20. error - port ethe 1/1/10 are not member of default VLAN

30. On RKUS-05, confirm that port 10 has returned to VLAN 1:
RKUS-05(config-vlan-333)# show vlan 1
PORT-VLAN 1, Name DEFAULT-VLAN, Priority level0, Spanning tree On
Untagged Ports: (U1/M1) 1 2 3 4 5 6 7 8 10 12 13 14
<truncated output>
31. On RKUS-05, add 10 to VLAN 222:

Added untagged port(s) ethe 1/1/10 to port-vlan 222.
• Do the pings receive replies? Yes/No21
Note
It will take approximately 30 seconds for the pings to be successful.
Important
Do not continue until ping replies are successful.
32. On RKUS-05, return 10 to VLAN 333 in preparation for the next lab.
RKUS-05(config-vlan-222)# no untagged e 1/1/10
33. On RKUS-05, disable port 10 and re-enable port 9.

RKUS-05(config-vlan-333)# int e 1/1/10
34. On PC1, stop the ping by pressing CTRL+C in the Command Prompt window.
35. On RKUS-03, RKUS-04 and RKUS-05, save all configurations by executing the write mem
command.
21. Yes

This ends Module 4 Lab: Link Aggregation Groups and VLANs lab exercise.

Module 5 Lab: Layer 2 Redundancy
In this lab exercise you will create a layer 2 loop in the topology experiencing the effects of STP and
RSTP.
Objectives
In this laboratory exercise, you perform tasks related to Spanning Tree and RSTP:
• Create a second static LAG between RKUS-03 and RKUS-04
• Observe the network impact when transitioning from 802.1d (STP) to 802.1w (RSTP)
• Record the 802.1w states
• Load balance traffic across two uplinks using 802.1 w port priorities
• Observe 802.1w failover time
• Configure 802.1w Edge Ports
• Observe Edge Port recovery time

lag <name> static Global Configuration Configures a LAG and names it
ports <port #> LAG Configuration Associates ports to a LAG
primary-port <port#> LAG Configuration Identifies the primary port in a LAG
deploy LAG Configuration Activates the LAG
vlan <#> Global Configuration Creates a VLAN on switch
tagged <port #> VLAN Configuration Associates a tagged port to a VLAN
spanning-tree 802-1w VLAN Configuration Enables RSTP on a VLAN

span 802-1w <port> admin- VLAN Configuration Configures a port as a RSTP point-to-
pt2pt-mac point link
show lag Any Displays the status of a LAG

Show 802-1w Any Displays the status of RSTP
FIGURE 2 Lab 6 Topology

Rapid Spanning Tree (802.1W)

In this section the convergence time advantage of Rapid Spanning Tree over Spanning Tree is
demonstrated. These steps let you witness the time difference for convergence of regular STP versus
Rapid Spanning Tree.
Your environment starts with a single LAG between RKUS-03 and RKUS-04 using ports 1 and 2.
1. On RKUS-03 and RKUS-04, establish a second static trunk group using ports 21 and 22.
RKUS-03(config)# lag Blue static
RKUS-03(config-lag-Blue)# enable e 1/1/21 to 1/1/22
RKUS-04(config)# lag Blue static

LAG Green deployed successfully!
RKUS-04(config-lag-Blue)# enable e 1/1/21 to 1/1/22
2. On RKUS-03 and RKUS-04, save the config on the devices by issuing wr mem command.
3. On RKUS-03 and RKUS-04, add port 21 as a tagged port to both VLAN 222 and VLAN 333.
Example:
RKUS-03(config-vlan-222)# tagged eth 1/1/21
Added tagged port(s) ethe 1/1/21 to 1/1/22 to port-vlan 222.
RKUS-03(config-vlan-333)# tagged eth 1/1/21

4. On RKUS-03 and RKUS-04, execute the show lag command and verify that the Link_Status
of the two trunks show Up.
RKUS-03(config-vlan-333)# show lag
=== LAG "Blue" ID 2 (static Deployed) ===

LAG Configuration:
Ports: e 1/1/21 to 1/1/22
Port Count: 2
Port Link State Dupl Speed Trunk Tag Pvid Pri MAC
Name
1/1/21 Up Forward Full 1G 2 Yes N/A 0 0024.38b7.6854

LAG Configuration:
Ports: e 1/1/1 to 1/1/2
Port Count: 2
Primary Port: 1/1/1
Port Link State Dupl Speed Trunk Tag Pvid Pri MAC
Name
5. On the PC1 desktop, establish a continuous ping to PC2 (10.10.200.200). If pings timeout,
troubleshoot until it succeeds. Keep this session open during the completion of the next steps.
Note
By default, STP is enabled on devices running switching code.
6. On RKUS-03, enter the clear stat command to reset all traffic counters to zero.

7. On RKUS-03, enter the show stat command a few times to identify the ports used by the ping
traffic.
• What ports are carrying the ping traffic between RKUS-03 and RKUS-04?
___________________1
RKUS-03(config-vlan-333)# show statatistics

1/1/1 110 100 0 0
1/1/2 0 0 0 0
1/1/3 0 0 0 0
1/1/4 0 0 0 0
1/1/5 0 0 0 0
1/1/6 0 0 0 0
1/1/7 0 0 0 0
1/1/8 0 0 0 0
1/1/9 0 0 0 0
1/1/10 0 0 0 0
1/1/11 21 0 0 0
1/1/12 0 0 0 0
1/1/13 0 0 0 0
1/1/14 0 0 0 0
1/1/15 0 0 0 0
1/1/16 0 0 0 0
1/1/17 0 0 0 0
1/1/18 0 0 0 0
1/1/19 0 0 0 0
Note
Look for ports that have incrementing counters for send and receive packets.
8. On RKUS-03, simulate failing the trunk on ports 1 and 2 by disabling port 1/1/1. Observe the fail-
over time by counting the number of lost pings:
RKUS-03(config-vlan-333)# int eth 1/1/1
Reply from 10.10.200.200: bytes=32 time<1ms TTL=128

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
• How many pings timed out? _______________2
1. 1 or 2 (trunk group 1)
2. Approximately 6 pings, or 30 seconds.

9. On RKUS-03, re-enable the trunk and again record the number of missed pings:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Note
Traffic interruptions are not only caused by failures in links, but also additions to available
paths in the network.
Note
Loss of 3 to 5 pings is typical during these steps.
Enabling Rapid Spanning Tree (802.1W)

10. Convert VLANs 222 and 333 from 802.1D to 802.1W, and observe the network impact.
a. On RKUS-03, enable RSTP on VLAN 222 and immediately make it the root bridge with:
RKUS-03(config-if-e1000-1/1/1)# vlan 222
RKUS-03(config-vlan-222)# spanning-tree 802-1w
RKUS-03(config-vlan-222)# spanning-tree 802-1w priority 1
b. On RKUS-03, enable RSTP on VLAN 333 of the RKUS-03 and immediately make it the root
bridge with the same commands as step 8(a).
RKUS-03(config-vlan-333)# spanning-tree 802-1w priority 1
11. On RKUS-04, enable RSTP on VLAN 222 and VLAN 333:
RKUS-04(config-vlan-333)# span 8
3. Typically 6-12 pings, or 30-60 seconds.

12. On RKUS-04, enter the show 802-1w vlan 222 command.
RKUS-04(config-vlan-333)# show 802 vlan 222
--- VLAN 222 [ STP Instance owned by VLAN 222 ] ----------------------------
Bridge IEEE 802.1W Parameters:
Bridge Bridge Bridge Bridge Force tx

Identifier MaxAge Hello FwdDly Version Hold
hex sec sec sec cnt
8000002438b77040 20 2 15 Default 3
RootBridge RootPath DesignatedBri- Root Max Fwd Hel

Identifier Cost dge Identifier Port Age Dly lo
hex hex sec sec sec
0001002438b76840 20000 0001002438b76840 1/1/1 20 15 2
Port IEEE 802.1W Parameters:
<--- Config Params --><-------------- Current state ----------------->

Port Pri PortPath P2P Edge Role State Designa- Designated
Num Cost Mac Port ted cost bridge
1/1/1 128 20000 F F ROOT FORWARDING 0 0001002438b76840
1/1/9 128 20000 F F DESIGNATED FORWARDING 20000 8000002438b77040
1/1/21 128 20000 F F ALTERNATE DISCARDING 0 0001002438b76840
• What is listed for port 21 Role and State in VLAN 222?_______________4

• What is listed for the Pri (RSTP priority) for port 21 in VLAN 222? ___________5
Note
In 802.1w DISCARDING state is the equivalent of the 802.1D BLOCKING state
13. On RKUS-03, change the RSTP port priority for port 21 in VLAN 222 so that on RKUS-04 port
21 transitions to the FORWARDING state for VLAN 222 and port 1 transitions to DISCARDING
state:
RKUS-03(config-vlan-222)# span 8 eth 1/1/21 pri 16
Note
On ICX switches, port priority can range between 0 and 240 in increments of 16, with a
default of 128. A lower number of 16 received in the BPDU at RKUS-04 port eth 1/1/21
takes priority over the default of 128 received at RKUS-04 port eth 1/1/1.
4. ALTERNATE/DISCARDING
5. 128 (the default priority)

14. Return to RKUS-04 and enter the show 802-1w vlan 222 command to verify the port states
changed.
RKUS-04(config-vlan-333)# show 802 vlan 222

hex sec sec sec cnt
8000002438b77040 20 2 15 Default 3

hex hex sec sec sec
0001002438b76840 20000 0001002438b76840 1/1/21 20 15 2

1/1/9 128 20000 F F DESIGNATED FORWARDING 20000 8000002438b77040
• How has the output changed for port e 1/1/21 from Step 12?
_______________________________________________________6
traffic.
RKUS-03(config-vlan-222)# show stat

1/1/1 0 11 0 0
1/1/2 0 0 0 0
<truncated output>
1/1/9 0 0 0 0
1/1/10 0 0 0 0
1/1/11 12 23 0 0
1/1/12 0 0 0 0
<truncated output>
1/1/20 0 0 0 0
1/1/21 0 110 0 0
1/1/22 120 120 0 0
1/1/23 0 0 0 0
1/1/24 0 0 0 0
• What ports are carrying the ping traffic between RKUS-03 and RKUS-04?
___________________7
6. It was ALTERNATE/DISCARDING, now ROOT/FORWARDING


17. On RKUS-03, simulate failing the trunk on ports 21 and 22 by disabling port 21. Observe the fail-
over time by counting the number of lost pings:
Request timed out.

18. On RKUS-03, re-enable the trunk and again record the number of missed pings:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
RSTP Port Type Settings

19. On RKUS-04, define ports eth 1/1/1 and eth 1/1/21 as point-to-point links in VLANs 222 and
333:
RKUS-04(config-vlan-222)# spanning-tree 802-1w eth 1/1/1 admin-pt2pt-mac
RKUS-04(config-vlan-222)# span 8 eth 1/1/21 admin-pt2pt-mac
8. Approximately 1 ping.
9. Approximately 5-6 pings, or 30 seconds.

20. On RKUS-03, repeat the commands that define ports eth 1/1/1 and eth 1/1/21 as point-to-point
links in VLANs 222 and 333:
RKUS-03(config-vlan-222)# spanning-tree 802-1w ethe 1/1/1 admin-pt2pt-mac
Identify the RSTP Port Roles and States

21. On RKUS-03 and RKUS-04, execute the show 8 command to record the spanning tree: Port
Priority, Port Roles / Port States of each end of the two trunks.
RKUS-03(config-vlan-333)# sh 8
IEEE 802-1w is not configured on port-vlan 1

hex sec sec sec cnt
0001002438142940 20 2 15 Default 3

hex hex sec sec sec
0001002438142940 0 0001002438142940 Root 20 15 2

1/1/1 128 20000 T F DESIGNATED FORWARDING 0 0001002438142940
1/1/11 128 20000 F F DESIGNATED FORWARDING 0 0001002438142940

hex sec sec sec cnt
0001002438142940 20 2 15 Default 3

hex hex sec sec sec
0001002438142940 0 0001002438142940 Root 20 15 2

RKUS-04(config-vlan-333)# show 8

hex sec sec sec cnt
8000002438143140 20 2 15 Default 3

hex hex sec sec sec
0001002438142940 20000 0001002438142940 1/1/21 20 15 2

1/1/1 128 20000 T F ALTERNATE DISCARDING 0 0001002438142940
1/1/21 128 20000 T F ROOT FORWARDING 0 0001002438142940

hex sec sec sec cnt
8000002438143140 20 2 15 Default 3

hex hex sec sec sec
0001002438142940 20000 0001002438142940 1/1/1 20 15 2

1/1/10 128 0 F F DISABLED DISABLED 0 0000000000000000

RKUS-03 VLAN 222 VLAN 333

Pri Port Role Port State Pri Port Role Port State
Port eth 1/1/1 ___ __________ / ____________ ___ __________ / __________
Port eth 1/1/21 ___ __________ / ____________ ___ __________ / __________

Port eth 1/1/1 ___ __________ / ____________ ___ __________ / __________
Port eth 1/1/21 ___ __________ / ____________ ___ __________ / __________
22. On RKUS-04, invoke the sh 8 detail command and familiarize yourself with the spanning tree
details for ports in VLAN 222.
RKUS-04(config-vlan-333)# sh 8 detail
======================================================================
VLAN 222 - SPANNING TREE (IEEE 802.1W) ACTIVE
======================================================================
BridgeId 8000002438143140, forceVersion 2, txHoldCount 3
Port 1/1/1 - Role: ALTERNATE - State: DISCARDING

PathCost 20000, Priority 128, AdminOperEdge F, AdminPt2PtMac T
DesignatedPriority - Root: 0x0001002438142940, Bridge: 0x8000002438143140
ActiveTimers - fdWhile 1 rcvdInfoWhile 1
MachineStates - PIM: CURRENT, PRT: BLOCKED_PORT, PST: DISCARDING
TCM: INACTIVE, PPM: SENDING_RSTP, PTX: TRANSMIT_IDLE
Received - RST BPDUs 927, Config BPDUs 0, TCN BPDUs 0
Port 1/1/9 - Role: DESIGNATED - State: FORWARDING
PathCost 20000, Priority 128, AdminOperEdge F, AdminPt2PtMac F
ActiveTimers - helloWhen 1
MachineStates - PIM: CURRENT, PRT: DESIGNATED_PORT, PST: FORWARDING
TCM: ACTIVE, PPM: SENDING_RSTP, PTX: TRANSMIT_IDLE
Port 1/1/21 - Role: ROOT - State: FORWARDING
ActiveTimers - rrWhile 0 rcvdInfoWhile 0
MachineStates - PIM: CURRENT, PRT: ROOT_PORT, PST: FORWARDING

======================================================================
VLAN 333 - SPANNING TREE (IEEE 802.1W) ACTIVE
======================================================================
BridgeId 8000002438143140, forceVersion 2, txHoldCount 3

Port 1/1/10 - DISABLED
Observe The 802.1w Failover Time Between Trunks

23. On PC1, verify the continuous ping to PC2 is still running.
traffic.
RKUS-03(config-vlan-333)# show stat

1/1/1 0 0 0 0
1/1/2 0 0 0 0
1/1/3 0 0 0 0
1/1/4 0 0 0 0
1/1/5 0 0 0 0
1/1/6 0 0 0 0
1/1/7 0 0 0 0
1/1/8 0 0 0 0
1/1/9 0 0 0 0

1/1/10 0 0 0 0
1/1/11 25 50 0 0
1/1/12 0 0 0 0
1/1/13 0 0 0 0
1/1/14 0 0 0 0
1/1/15 0 0 0 0
1/1/16 0 0 0 0
1/1/17 0 0 0 0
1/1/18 0 0 0 0
1/1/19 0 0 0 0
1/1/20 0 0 0 0
1/1/21 25 49 0 0
1/1/22 0 0 0 0
1/1/23 0 0 0 0
1/1/24 0 0 0 0
• What ports are carrying the ping traffic? ___________________10

26. On RKUS-03, simulate failing the trunk on ports 1 and 2 by disabling port eth 1/1/21. Observe
the fail-over time by counting the number of lost pings:
• How many pings timed out? ______________11

• How do you know that there was a failover?
____________________________________________________________________12
27. On RKUS-03 and RKUS-04, with the trunk disabled, enter the show 8 command and record the
Port Priority, Port Roles / Port States.
RKUS-03(config-if-e1000-1/1/21)# sh 8

hex sec sec sec cnt
0001002438142940 20 2 15 Default 3

hex hex sec sec sec
0001002438142940 0 0001002438142940 Root 20 15 2

11.Zero, possibly 1 ping lost.
12.The pings continue to succeed and the stats are increasing on e 1/1/1.


hex sec sec sec cnt
0001002438142940 20 2 15 Default 3

hex hex sec sec sec
0001002438142940 0 0001002438142940 Root 20 15 2

RKUS-04(config-vlan-333)# sh 8

hex sec sec sec cnt
8000002438143140 20 2 15 Default 3

hex hex sec sec sec
0001002438142940 20000 0001002438142940 1/1/1 20 15 2



hex sec sec sec cnt
8000002438143140 20 2 15 Default 3

hex hex sec sec sec
0001002438142940 20000 0001002438142940 1/1/1 20 15 2


Port eth 1/1/1 ___ __________ / ____________ ___ __________ / __________
Port eth 1/1/21 ___ __________ / ____________ ___ __________ / __________

Port eth 1/1/1 ___ __________ / ____________ ___ __________ / __________
Port eth 1/1/21 ___ __________ / ____________ ___ __________ / __________
28. On RKUS-03, re-enable port 21.


29. On RKUS-03 and RKUS-04, save all configurations by executing the write mem command.
13.Zero, possibly 1 ping lost

This ends the Module 5 Lab: Layer 2 Redundancy lab exercise.

Module 8 Lab: VRRP-Extended (VRRP-E)
In this exercise, you will configure layer 3 switches to perform layer 3 router redundancy through the
use of the proprietary VRRP-Extended protocol.
Objectives
In this lab exercise, you will perform tasks related to layer 3 redundancy and the configuration of
VRRP-Extended protocol. Upon completion you should be able to:
• Demonstrate ability to configure VRRP-E on Layer 3 ICX switches
• Distinguish the different states of VRRP-E routers using the ICX CLI
• Solve problems related to VRRP-E configuration errors

boot sys flash <partition> Global Configuration Enables stacking to be configured
ip address <IPv4 address> Interface Configuration Stack setup automation
ip vrrp-extended vrid <#> Interface Configuration Display stack details
backup pri <#> track-priority <#> VRID Configuration Shows neighbors in stack
track-port <port #> VRID Configuration Shows stack port order
show ip vrrp-extended Any Shows ports within the stack
FIGURE 3 VRRP-E Lab Topology

Prepare Devices for Lab Exercise

The following devices will be used in this lab exercise:
TABLE 1 Lab Device Information
Device Hostname Description Notes
RKUS-01 R1-AccessSW User Access Switch Accessed via PC1

RKUS-03 R3-RouterA VRRP-E Router A Accessed via PC1
RKUS-04 R4-RouterB VRRP-E Router B Accessed via PC1
RKUS-07 R7-Internet Internet Router Accessed via PC1
PC1 PC1 Customer PC Access via RSL Launch Page
PC3 PC3 Internet PC Access via RSL Launch Page
1. On RKUS-03, RKUS-04 and RKUS-07, execute the commands to erase the startup-config file and
reload the switch to router code located on the secondary flash.
RKUS-03# erase start
RKUS-03# boot sys flash secondary
- Answer “y” to any prompts
2. On RKUS-03, RKUS-04 and RKUS-07, configure the hostnames as described in Table 1 above.
ICX7450-24 Router> enable
ICX7450-24 Router# conf t
ICX7450-24 Router(config)# hostname R3-RouterA
R3-RouterA(config)#
3. On R3-RouterA, R4-RouterB and R7-Internet, execute the Global Configuration command to
ensure the device boots from the secondary flash on all reloads.
R3-RouterA(config)# boot sys flash sec
4. On R3-RouterA, R4-RouterB and R7-Internet, enable route-only globally.
R3-RouterA(config)# route-only
5. On R3-RouterA and R4-RouterB, disable all interfaces to avoid loops in lab environment.
(config)# int eth 1/1/1 to 1/1/24
(config-mif-1/1/1-1/1/24)# disable
(config-mif-1/1/1-1/1/24)# interface eth 1/2/1 to 1/2/4
(config-mif-1/2/1-1/2/4)# interface m1
(config-if-mgmt-1)# disable

6. On R7-Internet, disable all interfaces to avoid loops in the lab environment.
R7-Internet(config)# int eth 1/1/1 to 1/1/48
R7-Internet(config-mif-1/1/1-1/1/48)# disable
R7-Internet(config-mif-1/1/1-1/1/48)# interface eth 1/2/1 to 1/2/6
R7-Internet(config-mif-1/2/1-1/2/6)# disable
R7-Internet(config-mif-1/2/1-1/2/6)# interface m1
R7-Internet(config-if-mgmt-1)# disable
7. On RKUS-01, execute the commands to erase the startup-config file and reload the switch.
RKUS-01# reload
8. On RKUS-01, configure the hostname as described in Table 1 above.
ICX7450-24 Switch> enable
ICX7450-24 Switch# conf t
ICX7450-24 Switch(config)# hostname R1-AccessSW
R1-AccessSW(config)#
9. On R1-AccessSW, disable all interfaces to avoid loops in lab environment.
R1-AccessSW(config)# int eth 1/1/1 to 1/1/24
R1-AccessSW(config-mif-1/1/1-1/1/24)# disable
R1-AccessSW(config-mif-1/1/1-1/1/24)# interface eth 1/2/1 to 1/2/4
R1-AccessSW(config-mif-1/2/1-1/2/4)# disable
R1-AccessSW(config-mif-1/2/1-1/2/4)# interface m1
R1-AccessSW(config-if-mgmt-1)# disable

Configure Basic IP Connectivity for Lab Exercise
The following steps you will configure and enable the interfaces necessary for completing this lab
exercise.
TABLE 2 Interface IP Addresses
Hostname Interface IP Address
R3-RouterA e 1/1/5 10.10.200.11/24

e 1/1/23 172.16.10.1/30
R4-RouterB e 1/1/3 10.10.200.12/24
e 1/1/23 172.16.10.5/30
R7-Internet e 1/1/23 172.16.10.2/30
e 1/1/24 172.16.10.6/30
e 1/1/9 144.49.10.1/24
PC1 N/A 10.10.200.100/24
PC3 N/A 144.49.10.100/24
Configure Routers
10. On R3-RouterA, configure an IP address and enable interfaces e 1/1/5 and e 1/1/23 and create
a static route to the 144.49.10.0/24 WAN network.
R3-RouterA(config-if-mgmt-1)# int eth 1/1/5
R3-RouterA(config-if-e1000-1/1/5)# ip address 10.10.200.11/24
R3-RouterA(config-if-e1000-1/1/5)# enable
R3-RouterA(config-if-e1000-1/1/5)# int eth 1/1/23
R3-RouterA(config-if-e1000-1/1/23)# ip address 172.16.10.1/30
R3-RouterA(config-if-e1000-1/1/23)# enable
R3-RouterA(config-if-e1000-1/1/23)# exit
R3-RouterA(config)# ip route 144.49.10.0/24 172.16.10.2
11. On R4-RouterB, configure an IP address and enable interfaces e 1/1/3 and e 1/1/23 and create
a static route to the 144.49.10.0/24 WAN network.
R4-RouterB(config-if-mgmt-1)# int eth 1/1/3
R4-RouterB(config-if-e1000-1/1/3)# ip address 10.10.200.12/24
R4-RouterB(config-if-e1000-1/1/3)# enable
R4-RouterB(config-if-e1000-1/1/3)# int eth 1/1/23
R4-RouterB(config-if-e1000-1/1/23)# ip address 172.16.10.5/30
R4-RouterB(config-if-e1000-1/1/23)# enable
R3-RouterB(config-if-e1000-1/1/23)# exit
R3-RouterB(config)# ip route 144.49.10.0/24 172.16.10.6

Configure Access Switch
12. On R1-AccessSW, invoke the multi-interface mode command to enable interfaces e 1/1/3, e 1/1/
5 and e 1/1/9
R1-AccessSW(config-if-mgmt-1)# int eth 1/1/3 e 1/1/5 e 1/1/9
R1-AccessSW(config-mif-1/1/3,1/1/5,1/1/9)# enable
Configure R7-Internet Router

13. On the R7-Internet router, configure an IP address and enable interfaces e 1/1/23, e 1/1/24 and
e 1/1/9 and create a static route to the 10.10.200.0/24 LAN network.
R7-Internet(config-if-mgmt-1)# int eth 1/1/23
R7-Internet(config-if-e1000-1/1/23)# ip address 172.16.10.2/30
R7-Internet(config-if-e1000-1/1/23)# enable
R7-Internet(config-if-e1000-1/1/23)# int eth 1/1/24
R7-Internet(config-if-e1000-1/1/24)# int eth 1/1/9
R7-Internet(config-if-e1000-1/1/9)# exit
R7-Internet (config)# ip route 10.10.200.0/24 172.16.10.1
R7-Internet (config)# ip route 10.10.200.0/24 172.16.10.5
Configure VRRP-E
In the following steps you will enable and configure VRRP-E on R3-RouterA and R4-RouterB.
14. On R4-RouterB, invoke the command that globally enables the VRRP-Extended protocol
R4-RouterB(config)# router vrrp-extended
15. On R4-RouterB, configure VRRP-E parameters on int eth 1/1/3
R4-RouterB(config-vrrpe-router)# int eth 1/1/3
R4-RouterB(config-if-e1000-1/1/3)# ip vrrp-extended vrid 1
R4-RouterB(config-if-e1000-1/1/3-vrid-1)# backup pri 100 track-priority 9
R4-RouterB(config-if-e1000-1/1/3-vrid-1)# ip-address 10.10.200.1
R4-RouterB(config-if-e1000-1/1/3-vrid-1)# track-port e 1/1/23
R4-RouterB(config-if-e1000-1/1/3-vrid-1)# activate
VRRPE router 1 for this interface is activating
16. On R4-RouterB, execute the show ip vrrp-extended command.
R4-RouterB(config-if-e1000-1/1/3)# show ip vrrp-extended
Total number of VRRP-Extended routers defined: 1
Interface ethernet 1/1/3
auth-type no authentication
VRID 1
state master
administrative-status enabled
priority 100
current priority 100

track-priority 9
hello-interval 1000 msec
dead-interval 0 msec
current dead-interval 3600 msec
preempt-mode true
virtual ip address 10.10.200.1
virtual mac address 02e0.52f2.2f01
advertise backup: disabled
next hello sent in 00:00:01.0
track-port 1/1/23(up)
• What is the state of VRID 1? __________________1
17. On R3-RouterA, enable VRRP-Extended globally and configure VRRP-E parameters on port 1/1/5.
R3-RouterA(config)# router vrrp-extended
R3-RouterA(config-vrrpe-router))# int eth 1/1/5
R3-RouterA(config-if-e1000-1/1/5)# ip vrrp-extended vrid 1
R3-RouterA(config-if-e1000-1/1/5-vrid-1)# backup pri 110 track-priority 9
R3-RouterA(config-if-e1000-1/1/5-vrid-1)# ip-address 10.10.200.1
R3-RouterA(config-if-e1000-1/1/5-vrid-1)# track-port e 1/1/23
R3-RouterA(config-if-e1000-1/1/5-vrid-1)# activate
VRRPE router 1 for this interface is activating
18. On R3-RouterA and R4-RouterB, execute the show ip vrrp-extended command.
R3-RouterA(config-if-e1000-1/1/5)# show ip vrrp-extended
VRID 1
state master
priority 110
track-priority 9
preempt-mode true
• What is the state of VRID 1 on R3-RouterA? __________________2
1. Master
2. Master

VRID 1
state backup
priority 100
track-priority 9
preempt-mode true
master router 10.10.200.11 expires in 00:00:03.0
• What is the state of VRID 1 on R4-RouterB? __________________3

• Why did the state change on R4-RouterB? _________________________________________4
Analyze VRRP-E Failover Operations

In the following steps you will take steps to cause VRRP-E to failover
19. On PC1, execute a ping to PC3 (144.49.10.100)
C:\Documents and Settings\administrator> ping 144.49.10.100
Ping statistics for 144.49.10.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 75ms, Average = 18ms
• Was the ping successful? ___________5
Important
3. Backup
4. R3-RouterA has a higher priority (110 vs. 100)
5. Yes

20. On R1-AccessSW, view the switch MAC address table by executing the show mac-address
command
R1-AccessSw(config)# sh mac-add
Total active entries from all ports = 6
Type D:Dynamic S:Static L:Lock Address M:Secure Mac
MAC Address Port Age Type DMA Valid Flags VLAN DMA:CAM Index ...
0024.38b6.f9c2 3 25 D 00000000-00000001 1
0024.38b6.f9c0 3 65 D 00000000-00000001 1
0024.38b6.f100 5 5 D 00000000-00000001 1
001b.edec.a254 9 55 D 00000000-00000001 1
0050.5697.009d 9 30 D 00000000-00000001 1
02e0.52f2.2f01 5 5 D 00000000-00000001 1
• What port is associate with the 02e0.52xx.xxxx MAC address? _____________________6

• Is this port connected to the VRRP-E master router? _____________________7
21. On R7-Internet, force a track-port failure by disabling int eth 1/1/23
R7-Internet(config)# int eth 1/1/23
R7-Internet(config-if-e1000-1/1/23)# disable
22. On PC1, execute a ping to PC3
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Packets: Sent = 4, Received = 0, Lost = 0 <100% loss>

23. On R3-RouterA and R4-RouterB, execute the show ip vrrp-extended command
R3-RouterA(config-if-e1000-1/1/5)# show ip vrrp-extended
VRID 1
state master
priority 110
track-priority 9
preempt-mode true
6. 1/1/5
7. Yes
8. No

track-port 1/1/23(down)

VRID 1
state backup
priority 100
track-priority 9
preempt-mode true

• Why did the states stay the same? (Hint: see current priority field)
____________________________________________________________________11
• What VRRP-E variable could be changed to force a VRRP-E failover when R3-RouterA’s track
port goes down? ______________________________12
• What value should it be changed to? ____________13
24. On R7-Internet, re-enable int eth 1/1/23
25. On R3-RouterA, change the VRRP-E parameters on int eth 1/1/5 to ensure VRRP-E fails over when
it’s track port goes down
R3-RouterA(config)# int eth 1/1/5
R3-RouterA(config-if-e1000-1/1/5)# ip vrrp-extended vrid 1
R3-RouterA(config-if-e1000-1/1/5-vrid-1)# backup pri 110 track-priority 20
26. On R7-Internet, disable int eth 1/1/24
R7-Internet(config-if-e1000-1/1/23)# int e 1/1/24
R7-Internet(config-if-e1000-1/1/24)# disable
9. Master
10. Backup
11. R3-RouterA still has a higher priority (101 vs. 100)
12. track-priority
13. Any value greater than 10

27. On R3-RouterA and R4-RouterB, execute the show ip vrrp-extended command
R3-RouterA(config-if-e1000-1/1/5-vrid-1)# sh ip vrrp-e
VRID 1
state backup
priority 110
current priority 90
track-priority 20
preempt-mode true
track-port 1/1/23(down)

VRID 1
state master
priority 100
track-priority 9
preempt-mode true
14. Backup
15. Master

28. On PC1, execute a ping to PC3
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 75ms, Average = 18ms
Important
29. On R1-AccessSW, view the switch MAC address table by executing the show mac-address
command
R1-AccessSw(config)# sh mac-add
Total active entries from all ports = 6
Type D:Dynamic S:Static L:Lock Address M:Secure Mac
MAC Address Port Age Type DMA Valid Flags VLAN DMA:CAM Index ...
0024.38b6.f9c2 3 25 D 00000000-00000001 1
0024.38b6.f9c0 3 5 D 00000000-00000001 1
0024.38b6.f100 5 95 D 00000000-00000001 1
001b.edec.a254 9 10 D 00000000-00000001 1
0050.5697.009d 9 25 D 00000000-00000001 1
02e0.52f2.2f01 3 5 D 00000000-00000001 1
• What port is associated with the 02e0.52xx.xxxx MAC address? _____________________17

• Is this port connected to the VRRP-E master router? _____________________18
30. On R7-Internet, re-enable int eth 1/1/24
RR7-Internet(config-if-e1000-1/1/24)# enable
31. On all devices, save the running-configurations by invoking the write memory command.
R7-Internet# write memory
.Write startup-config done.
16. Yes
17. 1/1/3
18. Yes

This ends the Module 8 Lab: VRRP-Extended (VRRP-E) lab exercise.

Module 9 Lab A: OSPF Neighbor Adjacency and Link
Cost
In this lab exercise, ICX switches will be configured to route IP packets using the OSPF routing protocol.
OSPF is a very scalable routing protocol within an autonomous system (AS) due to it’s hierarchical
nature. OSPF has specific requirements for routers to establish neighbor adjacency and begin the
exchanging of IP route information.
Objectives
In this laboratory exercise, you will perform tasks related to the OPSF neighbor adjacency process,
including:
• Recording OSPF packet contents from the neighboring process
• Changing the reference bandwidth to influence path selection based on interface link speed
• Configuring OSPF interfaces for MD5 Authentication
• Troubleshooting the common OSPF problems as they are encountered, if required
Commands Context Comment
ip show-subnet-length Global Configuration Change subnet mask display to prefix
format
router ospf Global Configuration Enables the OSPF routing protocol globally
on the switch
area <area-id> OSPF Configuration Defines the OSPF area(s) this switch can
participate in
auto-cost reference-bandwidth OSPF Configuration Adjusts the reference value to automatically
<ref-value> determining link cost based on link speed.
Default is 100.
ip ospf area <area-id> Interface Configuration Defines the area the interface belongs in
ip ospf md5-authentication Interface Configuration Defines the MD5 authentication key ID and
key-id <key-id> key <key- key value to be exchanged with OSPF
value> neighbors
ip ospf auth-change-wait-time Interface Configuration Defines the delay before enforcing OSPF
<time> MD5 policies
show ip ospf neighbor Any Displays information about OSPF neighbors
debug ip ospf packet Privileged EXEC Displays debug level information about
OSPF packets exchanged between OSPF
neighbors
no debug all Privileged EXEC Disables all debugging

Connect to the RSL

In the following steps, all devices used in this lab exercise will be reloaded in the proper state.
1. On RKUS-06, execute the commands to erase the startup-config file and reload the switch.
RKUS-06# reload
2. On RKUS-01, RKUS-03, RKUS-04, RKUS-05, RKUS-07 and RKUS-08, execute the commands to
erase the startup-config file and reload the switch from the secondary flash.
R1-AccessSW# erase start
R1-AccessSW# boot sys flash secondary
3. On RKUS-01, RKUS-03, RKUS-04, RKUS-05, RKUS-07 and RKUS-08, execute the Global
Configuration command to ensure the device boots from the secondary flash on all reloads.
ICX7450-24 Router(config)# boot sys flash sec
4. On RKUS-01, RKUS-03, RKUS-04, RKUS-05, RKUS-07 and RKUS-08, enable route-only globally.
ICX7450-24 Router(config)# route-only
5. On RKUS-01, RKUS-03, RKUS-04, RKUS-05 and RKUS-06, disable all interfaces, stacking ports
and the management interface.
6. On RKUS-07 and RKUS-08, disable all interfaces, stacking ports and the management interface.

7. On RKUS-01, RKUS-03, RKUS-04, RKUS-05, RKUS-06, RKUS-07 and RKUS-08, configure the
hostnames as described in Table 3 below.
TABLE 3 Device Hostnames
Device Hostname
RKUS-01 R1-SaltLake
RKUS-03 R3-SanJose
RKUS-04 R4-SanDiego
RKUS-05 R5-Seattle
RKUS-06 R6-BackboneSW
RKUS-07 R7-Portland
RKUS-08 R8-Vancouver
ICX7450-24 Router(config)# hostname R4-SanDiego
8. On RKUS-01, RKUS-03, RKUS-04, RKUS-05, RKUS-06, RKUS-07 and RKUS-08, enable LLDP.
R4-SanDiego(config)# lldp run
OSPF Adjacency
FIGURE 4 OSPF topology w/ IP addresses

Configure OSPF
In the following steps, OSPF will be configured on all lab devices.
Configure R6-Backbone
9. On R6-BackboneSW, configure ports 1/1/1, 4 and 11 to operate at 100Mb.
R6-BackboneSW(config)# interface e1/1/1 e1/1/4 e1/1/11
R6-BackboneSW(config-mif-1/1/1,1/1/4,1/1/11)# speed-duplex 100-full
R6-BackboneSW(config-mif-1/1/1,1/1/4,1/1/11)# enable
Note
The configuration of port speed to 100Mb will be used to demonstrate route selection based
on link costs.
10. On R6-BackboneSW, execute the write mem command to save the running configuration to
flash.

Important
When running the router ospf command in the upcoming steps, you may see the follow-
ing dialog:
By selecting 'Y' you have read and accept the Brocade End USER
License Agreement found at the following URL [www.brocade.com/ser-
vices-support/software-license-keys/].
(enter 'y' to continue, 'n' to abort):
Enter y (yes) to accept the license.
Configure R4-SanDiego
11. On R4-SanDiego, enable OSPF globally and create area 0.
R4-SanDiego(config)# router ospf
R4-SanDiego(config-ospf-router)# area 0
12. On R4-SanDiego, configure port 1/1/11 to operate at 100Mb.
R4-SanDiego(config)# interface e1/1/11
R4-SanDiego(config-if-e1000-1/1/11)# speed-duplex 100-full
13. On R4-SanDiego, configure IP addresses, assign an OSPF area and enable interfaces as
described in Table 4 below.
TABLE 4 R4-SanDiego IP/OSPF Interfaces
Interface IP Address OSPF Enabled?
Area
loopback1 10.2.0.1/32 0
e1/1/3 192.168.10.1/30 0
e1/1/11 192.168.20.1/29 0
Important
Make sure to configure interface Loopback 1 before configuring any physical interfaces. This will
ensure the correct RouterID is used.
Example
R4-SanDiego(config)# interface e1/1/3
R4-SanDiego(config-if-e1000-1/1/3)# ip address 192.168.10.1/30
R4-SanDiego(config-if-e1000-1/1/3)# ip ospf area 0
R4-SanDiego(config-if-e1000-1/1/3)# enable

Configure R5-Seattle
14. On R5-Seattle, enable OSPF globally and create area 0.
15. On R5-Seattle, configure port 1/1/1 to operate at 100Mb.
R5-Seattle(config)# interface e1/1/1
R5-Seattle(config-if-e1000-1/1/1)# speed-duplex 100-full
16. On R5-Seattle, configure IP addresses, assign an OSPF area and enable interfaces as described
in Table 5 below. Do not enable interface e5 at this time.
TABLE 5 R5-Seattle IP/OSPF Interfaces
Area
loopback1 10.0.3.1/32 0
e1/1/1 192.168.20.2/29 0
e1/1/5 192.168.50.2/24 0 Do not enable
at this time
Important
Configure R3-SanJose
17. On R3-SanJose, enable OSPF globally and create area 0.
18. On R3-SanJose, configure port 1/1/4 to operate at 100Mb.
R3-SanJose(config)# interface e1/1/4
R3-SanJose(config-if-e1000-1/1/4)# speed-duplex 100-full
19. On R3-SanJose, configure IP addresses, assign an OSPF area and enable interfaces as described
in Table 6 below.
TABLE 6 R3-SanJose IP/OSPF Interfaces
Area
loopback1 10.0.0.1/32 0
e1/1/4 192.168.20.3/29 0
Important

Configure R7-Portland
20. On R7-Portland, enable OSPF globally and create area 0.
21. On R7-Portland, configure IP addresses, assign an OSPF area and enable interfaces as described
in Table 7 below.
TABLE 7 R7-Portland IP/OSPF Interfaces
Area
loopback1 10.3.3.1/32 0
e1/1/5 192.168.50.1/24 0
Important
Configure R1-SaltLake
22. On R1-SaltLake, enable OSPF globally and create area 0.
23. On R1-SaltLake, configure IP addresses, assign an OSPF area and enable interfaces as described
in Table 8 below.
TABLE 8 R1-SaltLake IP/OSPF Interfaces
Area
loopback1 10.2.2.1/32 0
e1/1/3 192.168.10.2/30 0
Important

Verify and Monitor OSPF Adjacency
24. On all routers, execute the command that displays OSPF neighbor states and use the table below
to verify all OSPF neighbor relationships are in a FULL state.
R4-SanDiego# show ip ospf neighbor
Hostname # of Neighbors
R1-SaltLake 1
R3-SanJose 2
R4-SanDiego 3
R5-Seattle 2
R7-Portland 0
Note
The interfaces connecting R7-Portland and R5-Seattle are not enabled yet. R7-Portland,
which is not connected to any neighbors, shows the following output:
No ospf neighbor entries available.
25. On R4-SanDiego, verify LLDP neighbor advertisements and identify what neighbors are directly
connected.
R4-SanDiego(config-if-e1000-1/1/3)# show lldp neighbor
Lcl Port Chassis ID Port ID Port Description System Name
1/1/3 748e.f87b.fe40 748e.f87b.fe42 GigabitEthernet1/1/3 R1-SaltLake
1/1/11 0024.382e.6c00 0024.382e.6c0a GigabitEthernet1/11 R6-Backbone
• Why are B5 and B3 not identifed on port 1/1/11? _______1

26. On R4-SanDiego, issue show lldp neighbor detail command and identify each device’s
advertised details.
• What are the enabled capabilities for the device on port 1/1/3? _______2
• What are the enabled capabilities for the device on port 1/1/11? _______3
27. On R7-Portland, invoke the debug ip ospf packet command in Privilege EXEC mode.
R7-Portland# debug ip ospf packet
28. On R5-Seattle, enable port 1/1/5.
29. On R7-Portland, observe the debug ip ospf packet output. (Many lines of output will scroll
onto your screen)
30. On R7-Portland, when the debug output stops scrolling and only hello packets are seen
(approximately 30 seconds), execute the undebug all command.
1. LLDP is a protocol that detects directly connected devices. Although there might be other deives within the same
broadcast domain only directly connected devices will be discovered.
2. bridge, router
3. bridge

31. On R7-Portland, scroll through the debug output:
a. Find a 1st Database Description (DD) packet received by R7-Portland
List the Type 2 LSAs received.
____________________________________________________________________
____________________________________________________________________4
b. Locate the Link State Request (LS-Req) sent by B7-Portland.
Are the Type 2 LSAs seen in the above Database Description packet present? _______5
c. Locate the LS-Update (LS-Upd) that fulfills the R7-Portland request.
Are these same Type 2 LSAs being supplied? ________6
4. LSType:2, LSID:192.168.20.1 Adv-Router:10.2.0.1

LSType:2, LSID:192.168.10.2 Adv-Router:10.2.2.1
5. Yes
6. Yes

OSPF Link Cost Calculation
In this section, high speed links will be introduced to the OSPF topology. In order to accurately
calculate OSPF path cost based on link speed, the default reference-bandwidth must be adjusted.
FIGURE 5 Adding 1Gbps link to topology
32. On R3-SanJose, execute the show ip route command.

What is the gateway to the 192.168.50.0 network? ____________________7
33. On R5-Seattle and R3-SanJose, assign IP addresses to port 1/1/11 as shown in Table 9. Make
sure to include these interfaces in OSPF area 0.
TABLE 9 New High-speed Links
Device Interface IP address OSPF Area
R3-SanJose e1/1/11 192.168.30.1/24 0

R5-Seattle e1/1/11 192.168.30.2/24 0
Predict which of these routers will be DR on interface e11? ________________
7. 192.168.20.2 (R5-Seattle, via port e1/1/4)

34. On R5-Seattle and R3-SanJose, enable port 1/1/11 and execute the show ip ospf
neighbor command.
Which router is the DR? ____________________8
Why? ___________________________________9
35. On R3-SanJose, execute the show ip route command and record the following:
How many paths are present for the 192.168.50.0 network? _____10
What are the gateways to reach this network?
____________________________________________________________________11
What is the cost to reach the 192.168.50.0 network? ________12
36. On R3-SanJose, execute the show interface brief command and note the speed of
interfaces e1/1/4 and e1/1/11?
Speed of e1/1/4: _______________13
Speed of e1/1/11: _______________14
With each interface operating a different speed, why are they considered equal-cost?
____________________________________________________________________15
37. On R3-SanJose, execute the traceroute 192.168.50.1 command.
Note
The traceroute command can only be executed from Privileged EXEC mode.
• Which of the two gateways is actually being used? ___________________16

38. In order to appropriately adjust the 1Gbps interface cost relative to the 100M interface cost, the
reference bandwidth must be manually adjusted.
• What should the new reference bandwidth be? (Hint: set to highest link speed) ________17
39. On all routers, adjust the auto-cost reference-bandwidth value to be 1000.
R3-SanJose(config)# router ospf
R3-SanJose(config-ospf-router)# auto-cost reference-bandwidth 1000
8. R5-Seattle
9. Higher Router ID (10.0.3.1 vs. 10.0.0.1)
10. 2
11. 192.168.20.2 (R5-Seattle, via port e4) and 192.168.30.2 (R5-Seattle, via port 1/1/11)
12. 2
13. 100M
14. 1G
15. The OSPF auto-cost reference-bandwidth is at the default value of 100
16. 192.168.20.2 (R5-Seattle, via port 1/1/4)
17. 1000

• Has the gateway to the 192.168.50.0 network changed? ________18
• What is the gateway to this network? ____________________19
• What is the cost to reach this network? ________20
• Why is there only one gateway to this network listed now?
____________________________________________________________________21
Using MD5 Authentication

In this section, MD5 authentication will be configured between three routers to ensure only properly
provisioned routers are able to establish OSPF neighbor adjacency.
41. On R4-SanDiego, use the ip ospf md5-authentication command to assign a key ID and
key value on interface e1/1/11.
R4-SanDiego(config)# int e1/1/11
R4-SanDiego(config-if-e1000-1/1/11)# ip ospf md5-authentication key-id 1 key icx200
42. On R4-SanDiego, use the ip ospf auth-change-wait-time command to configure the

delay (in seconds) before activating MD5 authentication on interface e1/1/11.
R4-SanDiego(config-if-e1000-1/1/11)# ip ospf auth-change-wait-time 5
43. On R4-SanDiego, wait 45 seconds and invoke the show ip ospf neighbor command.
• How many neighbors are there? ________22
• Are any neighbors on interface e1/1/11? ________23
44. On R3-SanJose and R5-Seattle, configure the same MD5 authentication keys and wait times on
the interfaces connecting to BackboneSW (R3-SanJose, e1/1/4 and R5-Seattle, e1/1/1).
45. On R4-SanDiego, wait 30 seconds and invoke the show ip ospf neighbor command.
• How many neighbors are there? ________24
• Are any neighbors on interface e1/1/11? ________25
46. On all routers, invoke the write memory command to save the current configuration.
18. Yes
19. 192.168.30.2 (R5-Seattle, via port e11)
20. 2
21. The auto-cost reference-bandwidth command has given the 1Gbps interface a lower cost than the 100M
interface
22. 1
23. No
24. 3
25. Yes

Depending on the remote environment you are using, follow the appropriate instructions to close your
connections.
This ends Module 9 Lab A: OSPF Neighbor Adjacency and Link Cost exercise.

Module 9 Lab B: Partitioning OSPF Areas and Redistri-
bution between RIP
The number of router links within an area, and the stability of these links, is the primary issue that
impacts performance in OSPF networks. These links dictate the size of an area’s LSDB and how fast
convergence will occur. The best approach is to minimize the scope of the link-state database to allow
OSPF routers to learn only the most essential LSAs. In this lab exercise, the size of the LSDB will be
reduced by partitioning the backbone area.
Objectives
In this laboratory exercise, you will perform tasks related to:
• Partitioning a single area in multiple areas.
• Recording the effect on the Link State Databases when one area is broken up into 3 areas.
• Troubleshooting the common OSPF problems encountered, if required.
show ip ospf database link-state Any Displays the contents of the OSPF Link State
database. It does not include external routes
show ip ospf database external-link- Any Displays the contents of the OSPF External
state Link State database

Connect to the RSL
Partitioning OSPF Areas
FIGURE 6 OSPF Lab topology
Examining the OSPF LSDB

1. On all routers, execute the show ip ospf database link-state command and verify that
the databases are identical.
R4-SanDiego# show ip ospf database link-state
Index Area ID Type LS ID Adv Rtr Seq(Hex) Age Cksum

1 0 Rtr 10.0.0.1 10.0.0.1 8000003f 1492 0xaf0a
2 0 Rtr 10.0.3.1 10.0.3.1 8000003f 1472 0x0561
3 0 Rtr 10.2.0.1 10.2.0.1 8000003e 1497 0x0fcf
4 0 Rtr 10.3.3.1 10.3.3.1 80000038 918 0xd6c7
5 0 Rtr 10.2.2.1 10.2.2.1 80000036 108 0x886d
6 0 Net 192.168.20.1 10.2.0.1 80000028 1477 0xc0c3
7 0 Net 192.168.30.2 10.0.3.1 8000002c 366 0x8cf1
8 0 Net 192.168.50.1 10.3.3.1 80000033 918 0xd288
9 0 Net 192.168.10.2 10.2.2.1 80000033 162 0x5f2b

Note
You can isolate a specific LSA Type by using the show ip ospf database link-
state router (for Type 1) or show ip ospf database link-state network (for
Type 2) commands. Use the context sensitive help (?) for other variations of this command.
Note
Type 5 External LSAs are listed with show ip ospf database external-link-
state command.
2. Record the number of each of these LSA Types in the Table 10 below.
TABLE 10 LSA Types for OSPF Area 0
OSPF Area ID Router LSA Network LSA Summary LSA ASBR LSA External LSA NSSA LSA
Type 1 Type 2 Type 3 Type 4 Type 5 Type 7
01 N/A N/A N/A N/A
1. Router - 5, Network - 4, Summary - 0, ASBR - 0, EXT - 0, NSSA - 0
Configure OSPF Area 3 on R7-Portland and R5-Seattle

3. On R7-Portland, partition the areas as defined in Figure 6.
d. On R7-Portland, remove Area 0 under port 1/1/5 and loopback 1.
R7-Portland(config)# int e1/1/5
R7-Portland(config-if-e1000-1/1/5)# no ip ospf area 0
R7-Portland(config-if-e1000-1/1/5)# int loopback 1
R7-Portland(config-lbif-1)# no ip ospf area 0
e. On R7-Portland, remove Area 0 under “router ospf” and add area 3 under the router ospf
context.
R7-Portland(config-lbif-1)# router ospf
R7-Portland(config-ospf-router)# no area 0
R7-Portland(config-ospf-router)# area 3
f. On R7-Portland, configure port 1/1/5 and loopback 1 as OSPF area 3 interfaces.

R7-Portland(config-ospf-router)# int loop 1
R7-Portland(config-lbif-1)# ip ospf area 3
R7-Portland(config-lbif-1)# int e1/1/5
R7-Portland(config-if-e1000-1/1/5)# ip ospf area 3
Note
All interfaces of R7-Portland now belong to OSPF area 3. You can verify port area member-
ship as well as port OSPF configuration by using the show ip ospf interface com-
mand.

4. On R5-Seattle, continue to partition the areas as defined in Figure 6.
a. Add area 3 under the router ospf context.
Note: Do not remove area 0 as we did above because R5-Seattle will now participate in both areas
b. Remove port 1/1/5 from area 0.
c. Add port 1/1/5 to area 3.
Note
Port 1/1/5 of R5-Seattle now belongs to area 3. All other interfaces, including the loopback,
still belong to area 0.
Configure OSPF Area 2 on R1-SaltLake and R4-SanDiego

5. On R1-SaltLake, continue to partition the areas as defined in Figure 6.
a. Remove port 1/1/3 and loopback 1 from OSPF area 0.
b. Remove Area 0 under the router ospf context.
c. Configure OSPF area 2 under the router ospf context.
d. Configure port 1/1/3 and loopback 1 as OSPF area 2 interfaces.
Note
All interface of R1-SaltLake now belong to area 2.
6. On R4-SanDiego, continue to partition the areas as defined in Figure 6.

a. Create the area 2 under the router ospf context.
b. Remove port 1/1/3 from area 0.
c. Add port 1/1/3 to area 2.
Note
Port 1/1/3 of R4-SanDiego now belongs to area 2. All other interfaces, including the loop-
back, still belong to area 0.
• Now that R5-Seattle and R4-SanDiego have interfaces in different areas, what type of
OSPF router are they? _________________________1
1. Area Border Router (ABR)

Verify Network Operations
7. On R5-Seattle and R4-SanDiego, execute the show ip ospf database link-state
command and use the output to populate Table 11 below.
TABLE 11 LSA Types for OSPF Areas 0, 2, and 3
01 N/A N/A N/A

2
2 N/A N/A N/A
33 N/A N/A N/A

Note
Because all routers in Area 0 have identical LSDBs, there may be four LSDB entries that can-
not be flushed. They will only be flushed when the entry ages out (60 minutes max). There-
fore, Area 0 LSAs will vary from a total of 13 down to 9 after all old LSAs have aged out.
Please ignore the following area 0 database entries if present:

Router LSA: 10.2.2.1
Router LSA: 10.3.3.1
Network LSA: 192.168.10.0
Network LSA: 192.168.50.0
If time permits, you may choose to reload all area 0 routers (R3-SanJose, R4-SanDiego and
R5-Seattle) in order to remove these aging entries. Make sure to save the running configura-
tion on each router before executing the reload command
Example
R3-SanJose# wr mem
R3-SanJose# reload
• What additional LSA types are present in Table 11 that were not present in Table 10
above?
____________________________________________________________________2
2. Type 3 - Summary LSA

Redistribution Between RIP and OSPF
Configure RIP Router: R8-Vancouver

9. On R8-Vancouver, configure the following parameters:
a. Enable RIP globally
R8-Vancouver(config)# router rip
b. Configure port 1/1/2 with the IP address of 192.168.90.2/25, enable RIP v2 and enable it.
R8-Vancouver(config-rip-router)# inte e 1/1/2
R8-Vancouver(config-if-e10000-1/1/2)# ip add 192.168.90.2/25
R8-Vancouver(config-if-e10000-1/1/2)# ip rip v2-only
R8-Vancouver(config-if-e10000-1/1/2)# enable
c. Configure interface loopback 4 as a multi-netted interface with the following addresses and
enable RIP v2:
192.168.60.65/29 192.168.60.97/29
192.168.60.73/29 192.168.60.105/29
192.168.60.81/29 192.168.60.113/29
192.168.60.89/29 192.168.60.121/29

Configure ASBR: R7-Portland
10. On R7-Portland, configure the following parameters:
a. Enable RIP globally
R8-Vancouver(config)# router rip
b. Configure port 1/1/2 with the IP address of 192.168.90.1/25, enable RIP v2 and enable it.
R7-Portland(config-rip-router)# int e 1/1/2
R7-Portland(config-if-e1000-1/1/2)# ip address 192.168.90.1/25
R7-Portland(config-if-e1000-1/1/2)# ip rip v2-only
R7-Portland(config-if-e1000-1/1/2)# enable
11. On R7-Portland, issue the show ip rip route command to verify RIP routes are being
received.
R7-Portland(config-if-e1000-1/1/2)# show ip rip route
RIP Routing Table - 9 entries:
192.168.60.64/29, from 192.168.90.2, e 1/1/2 (1)
RIP, metric 2, tag 0, timers: aging 42
192.168.60.72/29, from 192.168.90.2, e 1/1/2 (2)
192.168.60.80/29, from 192.168.90.2, e 1/1/2 (3)
192.168.60.88/29, from 192.168.90.2, e 1/1/2 (4)
192.168.60.96/29, from 192.168.90.2, e 1/1/2 (5)
192.168.60.104/29, from 192.168.90.2, e 1/1/2 (6)
192.168.60.112/29, from 192.168.90.2, e 1/1/2 (7)
192.168.60.120/29, from 192.168.90.2, e 1/1/2 (8)
192.168.90.0/25, from 0.0.0.0, e 1/1/2 (0)
LOCAL, metric 1, tag 0, timers: none
12. On R7-Portland, configure the redistribution of RIP and connected routes into OSPF.
R7-Portland(config)# router ospf
R7-Portland(config-ospf-router)# redistribute rip
R7-Portland(config-ospf-router)# redistribute connected
13. On R7-Portland, configure the redistribution of OSPF and connected routes into RIP.
R7-Portland(config-ospf-router)# router rip
R7-Portland(config-rip-router)# redistribute ospf
R7-Portland(config-rip-router)# redistribute connected

14. On all routers, view the IP routing table.
• On R5-Seattle, are the R8-Vancouver loopback 4 subnets (192.168.60.x) present?
______3
• On R8-Vancouver, is the R1-SaltLake 192.168.10.0 subnet present? ______4
• How many routes are in each IP routing table? _____5
Important
Do not continue unless the above answers are YES and all routers have 18 routes
3. Yes
4. Yes
5. 18

Configure Internal OSPF Interfaces: R1-SaltLake
FIGURE 7 R1-SaltLake multinetted interface
15. On R1-SaltLake, configure interface loopback 7 as a multi-netted interface with the following
addresses:
192.168.40.129/28
192.168.40.145/28
192.168.40.161/28
192.168.40.177/28
16. On R1-SaltLake, add interface loopback7 to Area 2 by invoking the ip ospf area 2 command.
17. On R8-Vancouver, view the IP routing table.
• Are the newly added 192.168.40.0 subnets present? ______6
18. On all remaining routers, view the IP routing table.
• How many routes are present in the IP routing table? ______7
Important
Do not continue unless the answer to Step 17 is “yes” and Step 18 is “22”.
6. Yes
7. 22

Examine the Link State Database
19. On R5-Seattle and R4-SanDiego, execute the show ip ospf database link-state and
show ip ospf database external-link-state commands. Then use the output to
populate Table 19 below.
TABLE 12 LSA Types for OSPF Areas After Redistribution
01 N/A
22 N/A
33 N/A N/A
1. Router - 3, Network - 2, Summary - 8, ASBR - 1, EXT - 9


Lab Review
20. On R5-Seattle, why is there no Type 4 (ASBR Summary) LSA in the Area 3 LSDB?
____________________________________________________________________8
21. On R1-SaltLake, execute the show ip ospf database external-link-state
command.
• How many LSAs describe R8-Vancouver’s 192.168.60.x networks? ________9
• What type of LSA are these? __________10
22. On R5-Seattle, execute the show ip ospf database link-state command.
• How many Summary LSAs describe R1-SaltLake’s 192.168.40.x networks in Area 3?
_______11
23. On R4-SanDiego, execute the show ip ospf database link-state command.
• How many LSAs describe R1-SaltLake’s 192.168.40.x networks in Area 0? ________13
24. On R3-SanJose, examine the IP route table.
• What is the total number of route entries? _________15
8. Type 4 ASBR Summary LSAs are generated by the ABR into adjacent areas
9. 8
10. Type 5 - AS External LSAs
11. 4
12. Type 3 - Summary LSAs
13. 4
15. 22 routes

26. Depending on the remote environment you are using, follow the appropriate instructions to close
your connections.
This ends Module 9 Lab B: Partitioning OSPF Areas and Redistribution between RIP exercise.

Module 9 Lab C: OSPF Route Summarization and Area
Types
In this lab exercise, routes will be summarized to limit the impact on the IP routing table and the OSPF
LSDB. In OSPF, summarization can only be accomplished at OSPF boundaries (ABR or ASBR).
Objectives
In this laboratory exercise, you will perform tasks related to:
Part 1: OSPF Summarization

• Reducing the size of link-state databases throughout the OSPF autonomous system, without
sacrificing performance.
• Applying internal (ABR) and external (ASBR) route summarization.
Part 2: OSPF Area Types

• Injecting external routes into the backbone.
• Recognizing the added load to normal area routers
• Configuring a Stub area to block the external routes from entering Area 2.
• Configuring a NSSA area to block external LSAs from entering Area 3, while allowing RIP routes to
pass through into the OSPF backbone.
• Troubleshooting the common OSPF problems when encountered, as required.
router ospf summary address OSPF Configuration Defines address range to summarize into OSPF
<ip address> on an ASBR
router ospf area <Id> range OSPF Configuration Defines address range and source area to
<ip address> summarize routes into another area on an ABR
show ip ospf database Any Displays the contents of the OSPF Link State
link-state database. It does not include external routes
show ip ospf database Any Displays the contents of the OSPF External Link
external-link-state State database
area <area-id> stub <metric> OSPF Configuration Defines an OSPF area as a stub
area <area-id> stub <metric> OSPF Configuration Defines an OSPF area as a totally-stubby area
no-summary
area <area-id> nssa <metric> OSPF Configuration Defines an OSPF area as a Not-So-Stubby area
area <area-id> nssa default- OSPF Configuration Allows the propagation of the default route into a
information-originate NSSA

Connect to the RSL
OSPF Address Summarization
FIGURE 8 Address Summarization Topology
Examine Current LSDB

1. On R3-SanJose, execute the show ip ospf database external-link-state
command.
• How many Type 5 - AS External LSAs are in database? _____1
• How may routes are present for the R8-Vancouver loopback networks (192.168.60.x)?
_____2
1. 9
2. 8

Summarize External Networks at ASBR
3. Use the table below to record lowest 2 and highest 2 addresses on the R8-Vancouver loopback 4
interface; convert the last octet to binary.
Decimal address Last octet in binary
128 64 32 16 8 4 2 1
1st 1 2
2nd 3 4
5 6
7th
7 8
8th
1. 192.168.60.65
2. 01000001
3. 192.168.60.73
4. 01001001
5. 192.168.60.113
6. 01110001
7. 192.168.60.121
8. 01111001
• What is the common number of contiguous bits (all 4 octets): ________3

• What will be used as the summary address: ____________________4
• What will be used as the summary mask: _______________________5
• Based on the topology in Figure 8, which router will be responsible for summarizing the
R8-Vancouver loopback 4 networks? _______________________6
4. On R7-Portland, execute the command to summarize the 8 RIP routes learned from R8-Vancouver.
R7-Portland(config-ospf-router)# summary-address 192.168.60.64/26
5. On R3-SanJose, view the OSPF AS-External LSDB.
• How many Type 5 - AS External LSAs are in the database? _____7
6. On R3-SanJose, view the IP routing table.
• How may routes are present for the R8-Vancouver loopback networks (192.168.60.x)?
_____8
3. 26
4. 192.168.60.64
5. 255.255.255.192 (/26)
6. R7-Portland (ASBR)
7. 2
8. 1

Summarize Internal Networks at ABR
7. On R3-SanJose, examine the IP route table.
• How may routes are present for the R1-SaltLake loopback networks (192.168.40.x)?
_____9
• Are these routes associated with Type 5 - external LSAs? ________10
• What type of LSAs represent these routes? _______________11
8. Record the four addresses on loopback 7 of R1-SaltLake; convert appropriate octet to binary.
Decimal address Last octet in binary
128 64 32 16 8 4 2 1
1 2
1st
2nd 3 4
5 6
3rd
7 8
4th
1. 192.168.40.129
2. 10000001
3. 192.168.40.145
4. 10010001
5. 192.168.40.161
6. 10100001
7. 192.168.40.177
8. 10110001
• What is the common number of contiguous bits (all 4 octets): ________12

• What will be used as the summary address: ____________________13
• What will be used as the summary mask: _______________________14
• Based on the topology in Figure 8, which router will be responsible for summarizing the
R1-SaltLake loopback 7 networks? _______________________15
9. On R4-SanDiego, execute the command to summarize the 4 loopback networks learned from R1-
SaltLake.
R4-SanDiego(config-ospf-router)# area 2 range 192.168.40.128/26
10. On R4-SanDiego, clear the IP OSPF process to force a refresh of all LSDB advertisements to
neighbor routers.
R4-SanDiego(config-ospf-router)# clear ip ospf all
11. On R3-SanJose, view the OSPF LSDB.
• How many Type 3 - Summary LSAs are in the database for the R1-SaltLake loopback
networks (192.168.40.x)? _____16
9. 4
10. No
12. 26
13. 192.168.40.128
14. 255.255.255.192 (/26)
15. R4-SanDiego (ABR)
16. 1

12. On R3-SanJose, view the IP routing table.
• How may routes are present for the R1-SaltLake loopback networks (192.168.40.x)?
_____17
• How does this compare to Step 7? ______________________18
13. On R3-SanJose, how has the route table changed since the last step of the previous lab?
____________________________________________________________________19
OSPF Area Types

Previously in this lab exercise internal and external LSAs were summarized so that router resources
are used appropriately. However, if all the areas are Normal Areas, the external LSAs propagated out
of area 3 will flood into area 2.
In this exercise, area 2 will be converted to a stub area, thus blocking external LSAs from a new route
source in the backbone (perhaps a link to an ISP).
Configure A New External Route Source

command.
How many external LSAs are there? ______20
15. On R3-SanJose, configure interface loopback 7 as a multi-netted interface with the following
addresses:
192.168.80.1/27 192.168.80.33/27
192.168.80.65/27 192.168.80.97/27
16. On R3-SanJose, configure the router to redistribute these connected networks into OSPF.
R3-SanJose(config-ospf-router)# redistribute connected
Note
Its important to know that anytime you configure a device to redistribute into OSPF it
becomes an ASBR regardless of its location in the network. You can verify this by issuing the
show ip ospf database link-state and you can now see a type 4 LSA (ASBR)
being advertised for R3-SanJose (Router ID 10.0.0.1)

command.
• How many external LSAs are there now? ______21
17. 1
18. Was 4, now 1
19. Was 22, now 12
20. 2
21. 6

Check Point: R1-SaltLake’s external LSDB should contain each of the four networks configured in
Step 15, the summarized address range from OSPF area 3 (192.168.60.64) and the
network connecting R8-Vancouver and R5-Seattle (192.168.90.0).
Reconfigure Normal Area 2 into a Stub Area
18. On R4-SanDiego, perform the following steps to reconfigure area 2 as a stub area.
a. Remove port 1/1/3 from OSPF area 2.
b. Under router ospf, remove the area 2 range 192.168.40.128/26 configuration.
c. Under router ospf, remove area 2
d. Under router ospf, create area 2 as a stub area with an external metric of 100.
R4-SanDiego(config-ospf-router)# area 2 stub 100
Note
The area 2 stub 100 command creates a new OSPF area, which is a stub area with an
advertised external route metric of 100, in this case.
e. Under router ospf, replace the area 2 range 192.168.40.128/26 configuration.

f. Configure port 1/1/3 as an area 2 interface.

19. On R1-SaltLake, perform the following steps to reconfigure area 2 as a stub area.
a. Remove interfaces loopback 1, e1/1/3 and loopback 7 from OSPF area 2.
Why is it not acceptible to keep the same configuration on R1-SaltLake since it is already
configured for area 2? _____________________________________________________22
b. Under router ospf, remove area 2
c. Under router ospf, create area 2 as a stub area with an external metric of 100.
R1-SaltLake(config-ospf-router)# area 2 stub 100
d. Configure interfaces loopback 1, e3 and loopback 7 as area 2 interfaces.
20. On R1-SaltLake and R4-SanDiego, verify that area 2 is now a stub area.
R4-SanDiego# sho ip ospf area
Area Type Cost SPFR ABR ASBR LSA Chksum(Hex)
1 0 normal 0 37 1 2 11 000643fb
2 2 stub 100 5 0 0 11 00067113
21. On R1-SaltLake, examine the IP routing table.

Where did the new default route with a cost of 101 come from?
____________________________________________________________________23
Note
In stub areas, the ABR generates a default route into the stub area with cost value defined in
the area 2 stub 100 command. This value plus the cost of the 1Gbps interface between
R1-SaltLake and R4-SanDiego equals 101.
22. On R1-SaltLake, execute the show ip ospf database external command.

• How does the output differ from Step 17?
________________________________________24
23. On R1-SaltLake, invoke the show ip ospf database link-state command.
• Are there still summary LSAs?_________25
24. On R4-SanDiego, configure the ABR to stop forwarding Type 3 summary LSAs into area 2:
R4-SanDiego(config-ospf-router)# area 2 stub 100 no-summary
Note
With the no-summary argument, the ABR will no longer forward Type 3 summary LSAs into
the stub area. This argument only needs to be applied at the ABR, not all routers in the stub
area.
22. Because OSPF adjacency requires not only the area # but also the area type to match. R4-SanDiego is now
advertising area 2 as a stub area.
23. From the ABR (R4-SanDiego)
24. There are now no external LSDB entries
25. Yes

25. On R1-SaltLake, execute the show ip ospf database link command.
• How many Summary LSAs are present?______26
• Why is this summary LSA present, if no-summary is configured?
____________________________________________________________________27
• What type of area is Area 2 now? ______________________28
26. On R1-SaltLake, execute a traceroute to R7-Portland’s 192.168.50.1 interface.
• What route in the R1-SaltLake’s IP routing table is being used to reach the 192.168.50.0
network? ______________________________________29
• What LSA in the database matches this route? __________________________________30
26. 1
27. The ABR will still generate the default route in a Type 3 summary LSA when no-summary is configured.
28. Totally Stubby Area
29. 0.0.0.0/0 (default route) because the 192.168.50.1 is not listed in the routing table.
30. The summary LSA generated by the ABR

Optional Lab: Enabling IPv6 and OSPFv3
27. On R1-SaltLake, enable IPv6 unicast routing globally.
R1-SaltLake(config)# ipv6 unicast-routing
28. On R1-SaltLake, enable OSPFv3 and then configure port 1/1/3 for IPv6 allowing an auto assigned
link-local address to be created.
R1-SaltLake(config)# ipv6 router ospf
R1-SaltLake(config-ospf6-router)# area 2
R1-SaltLake(config-ospf6-router)# int e 1/1/3
R1-SaltLake(config-if-e1000-1/1/3)# ipv6 enable
29. On R1-SaltLake, enable int e 1/1/3 for OSPFv3 routing.
R1-SaltLake(config-if-e1000-1/1/3)# ipv6 ospf area 2
30. On R1-SaltLake, enable IPv6 on Loopback 1 by assigning IPv6 addresses and enable OPSFv3
R1-SaltLake(config-if-e1000-1/1/3)# interface loopback 1
R1-SaltLake(config-lbif-1)# ipv6 address 2001:db8::/32
R1-SaltLake(config-lbif-1)# ipv6 address 2001:db9::/32
R1-SaltLake(config-lbif-1)# ipv6 ospf area 2
31. On R1-SaltLake, verify that interfaces are enabled for OSPFv3.
R1-SaltLake(config-lbif-1)# show ipv6 ospf interface
e 1/1/3 admin up, oper up, IPv6 enabled

IPv6 Address:
fe80::768e:f8ff:fe7b:fe40
Instance ID 0, Router ID 10.2.2.1
Area ID 2, Cost 1, Type BROADCAST
MTU: 1500
State DR, Transmit Delay 1 sec, Priority 1, Link-LSA Tx not suppressed
Timer intervals :
Hello 10, Hello Jitter 10 Dead 40, Retransmit 5
Authentication Use: Enabled
KeyRolloverTime(sec): Configured: 300 Current: 0
KeyRolloverState: NotActive
Outbound: None
Inbound: None
DR:10.2.2.1 BDR:10.2.0.1 Number of I/F scoped LSAs is 2
DRElection: 2 times, DelayedLSAck: 2 times
Neighbor Count = 1, Adjacent Neighbor Count= 1
Neighbor:
10.2.0.1 (BDR)
Statistics of interface e 1/1/3:
Type tx rx tx-byte rx-byte
Unknown 0 0 0 0
Hello 10 10 396 400
DbDesc 3 3 144 124
LSReq 1 1 40 52
LSUpdate 4 3 364 212
LSAck 2 1 92 96
OSPF messages dropped,no authentication: 0
loopback 1 admin up, oper up, IPv6 enabled

IPv6 Address:

fe80::768e:f8ff:fe7b:fe40
2001:db8::/32
2001:db9::/32
Instance ID 0, Router ID 10.2.2.1
Area ID 2, Cost 1, Type BROADCAST
MTU: 1500
State Loopback, Transmit Delay 1 sec, Priority 1, Link-LSA Tx not suppressed
Timer intervals :
Hello 10, Hello Jitter 10 Dead 40, Retransmit 5
Authentication Use: Disabled
DR:0.0.0.0 BDR:0.0.0.0 Number of I/F scoped LSAs is 0
DRElection: 0 times, DelayedLSAck: 0 times
Neighbor Count = 0, Adjacent Neighbor Count= 0
Statistics of interface loopback 1:
Type tx rx tx-byte rx-byte
Unknown 0 0 0 0
Hello 0 0 0 0
DbDesc 0 0 0 0
LSReq 0 0 0 0
LSUpdate 0 0 0 0
LSAck 0 0 0 0
OSPF messages dropped,no authentication: 0
32. On R4-SanDiego, perform the following steps to enable IPv6 routing

a. Enable IPv6 unicast routing, enable OSPFv3 and configure it for areas 0 and 2
R4-SanDiego(config)# ipv6 unicast-routing
R4-SanDiego(config)# ipv6 router ospf
R4-SanDiego(config-ospf6-router)# area 0
R4-SanDiego(config-ospf6-router)# area 2
b. Enable Ports e 1/1/3 and e 1/1/11 for IPv6 allowing the auto configuration of a link-local
address.
R4-SanDiego(config-ospf6-router)# int e 1/1/3
R4-SanDiego(config-if-e1000-1/1/3)# ipv6 enable
R4-SanDiego(config-if-e1000-1/1/3)# ipv6 ospf area 2
R4-SanDiego(config-if-e1000-1/1/3)# int e 1/1/11
R4-SanDiego(config-if-e1000-1/1/11)# ipv6 enable
R4-SanDiego(config-if-e1000-1/1/11)# ipv6 ospf area 0
c. Verify neighbor adjacency on interface e 1/1/3 by issuing show ipv6 ospf neighbor
command.
Note
Do not move forward if there is not an OSPFv3 neighbor adjacency on interface 1/1/3 and
troubleshoot.
d. On R4-SanDiego, verify IPv6 addresses assigned to SaltLakes loopback addresses are in the
IPv6 routing table.
R4-SanDiego(config-if-e1000-1/1/11)# show ipv6 route
IPv6 Routing Table - 2 entries:
Type Codes - B:BGP C:Connected I:ISIS L:Local O:OSPF R:RIP S:Static
BGP Codes - i:iBGP e:eBGP
OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2
STATIC Codes - d:DHCPv6

Type IPv6 Prefix Next Hop Router Interface Dis/Metric Uptime
O 2001:db8::/128 fe80::768e:f8ff:fe7b:fe40
e 1/1/3 110/1 3m22s
O 2001:db9::/128 fe80::768e:f8ff:fe7b:fe40
e 1/1/3 110/1 3m22s
• Why do you not see the link-local addresses populating the routing table?
_________________31
33. On R5-Seattle, enable IPv6 and OSPFv3 by performing the following tasks.
R5-Seattle(config)# ipv6 unicast-routing
R5-Seattle(config)# ipv6 router ospf
R5-Seattle(config-ospf6-router)# area 0
R5-Seattle(config-ospf6-router)# area 3
R5-Seattle(config-ospf6-router)# interface e 1/1/1
R5-Seattle(config-if-e1000-1/1/1)# ipv6 ena
R5-Seattle(config-if-e1000-1/1/1)# ipv6 ospf area 0
R5-Seattle(config-if-e1000-1/1/1)# int e 1/1/11
R5-Seattle(config-if-e1000-1/1/11)# ipv6 ena
R5-Seattle(config-if-e1000-1/1/11)# ipv6 ospf area 0
34. On R5-Seattle, verify OSPFv3 neighbor adjacencies by issuing the show ipv6 ospf
neighbor command
R5-Seattle(config-if-e1000-1/1/11)# show ipv6 ospf neighbor
Total number of neighbors in all states: 1

Number of neighbors in state Full : 1
RouterID Pri State DR BDR Interface [State]

10.2.0.1 1 Full 10.2.0.1 10.0.3.1 e 1/1/1 [BDR]
35. On R3-SanJose, enable IPv6, OSPFv3 and assign an IPv6 address to the loopback 1 interface by
performing the following tasks.
R3-SanJose(config-ospf-router)# ipv6 unicast
R3-SanJose(config-ospf-router)# ipv6 router ospf
R3-SanJose(config-ospf6-router)# area 0
R3-SanJose(config-ospf6-router)# int e 1/1/11
R3-SanJose(config-if-e1000-1/1/11)# ipv6 ena
R3-SanJose(config-if-e1000-1/1/11)# ipv6 ospf area 0
R3-SanJose(config-if-e1000-1/1/11)# int e 1/1/4
R3-SanJose(config-if-e1000-1/1/4)# ipv6 ena
R3-SanJose(config-if-e1000-1/1/4)# ipv6 ospf area 0
R3-SanJose(config-if-e1000-1/1/4)# int lo 1
R3-SanJose(config-lbif-1)# ipv6 address 2001:db10::/32
R3-SanJose(config-lbif-1)# ipv6 ospf area 0
31. Because link-local addresses are used on a single link or a non-routed network. They do not need to be
unique outside of that link.

36. On R3-SanJose, verify neighbor adjacencies and IPv6 routes by issuing the show ipv6 ospf
neighbor and show ipv6 route commands.
R3-SanJose(config-lbif-1)# show ipv6 ospf neighbor
Total number of neighbors in all states: 3

Number of neighbors in state Full : 3
RouterID Pri State DR BDR Interface [State]

10.0.3.1 1 Full 10.2.0.1 10.0.3.1 e 1/1/4 [DROther]
10.2.0.1 1 Full 10.2.0.1 10.0.3.1 e 1/1/4 [DROther]
10.0.3.1 1 Full 10.0.3.1 10.0.0.1 e 1/1/11 [BDR]
R3-SanJose(config-lbif-1)# show ipv6 route

IPv6 Routing Table - 3 entries:
Type Codes - B:BGP C:Connected I:ISIS L:Local O:OSPF R:RIP S:Static
BGP Codes - i:iBGP e:eBGP
OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2
STATIC Codes - d:DHCPv6
Type IPv6 Prefix Next Hop Router Interface Dis/Metric Uptime
Oi 2001:db8::/128 fe80::224:38ff:feb7:7040
e 1/1/4 110/2 9m7s
Oi 2001:db9::/128 fe80::224:38ff:feb7:7040
e 1/1/4 110/2 9m7s
C 2001:db10::/32 :: loopback 1 0/0 9m47s
37. On R3-SanJose, examine the OSPF link state database by issuing the show ipv6 ospf
database command.
38. On R3-SanJose, examine the OSPFv3 intra and inter area prefix LSAs within the link state
database
R3-SanJose(config-lbif-1)# show ipv6 ospf database inter-prefix
LSA Key - Rtr:Router Net:Network Inap:InterPrefix Inar:InterRouter

Extn:ASExternal Grp:GroupMembership Typ7:Type7 Link:Link
Iap:IntraPrefix Grc:Grace
Area ID Type LSID Adv Rtr Seq(Hex) Age Cksum Len Sync
0 Inap 3 192.168.10.1 80000006 1152 1039 44 Yes
Metric: 1
Prefix Options:
Prefix: 2001:db9::/128
LSA Key - Rtr:Router Net:Network Inap:InterPrefix Inar:InterRouter

Extn:ASExternal Grp:GroupMembership Typ7:Type7 Link:Link
Iap:IntraPrefix Grc:Grace
Area ID Type LSID Adv Rtr Seq(Hex) Age Cksum Len Sync
0 Inap 1 192.168.10.1 80000006 1152 1636 44 Yes
Metric: 1
Prefix Options:
Prefix: 2001:db8::/128
39. On R3-SanJose, ping one of the IPv6 addresses configured on R1-SaltLake to confirm
connectivity.
R3-SanJose(config-lbif-1)# end
R3-SanJose# ping ipv6 2001:db8::
Sending 1, 16-byte ICMPv6 Echo to 2001:db8::
timeout 5000 msec, Hop Limit 64
Type Control-c to abort

Reply from 2001:db8::: bytes=16 time<1ms Hop Limit=63
Success rate is 100 percent (1/1), round-trip min/avg/max=0/0/0 ms.
R3-SanJose# ping ipv6 2001:db9::

Sending 1, 16-byte ICMPv6 Echo to 2001:db9::
timeout 5000 msec, Hop Limit 64
Type Control-c to abort
Reply from 2001:db9::: bytes=16 time<1ms Hop Limit=63
Success rate is 100 percent (1/1), round-trip min/avg/max=0/0/0 ms.

Depending on the remote environment you are using, follow the appropriate instructions to close your
connections.
This ends Module 9 Lab C: OSPF Route Summarization and Area Types exercise.

Module 15 Lab: Multi-Chassis Trunking
In this lab exercise, ICX switches will be configured for Multi-Chassis Trunking (MCT) allowing active-
active Layer2 forwarding between switches through physically separate MCT peers.
Objectives
In this laboratory exercise, you will perform tasks related to configuring and verifying the operation of
Multi-Chassis Trunking.
• Configure Multi-Chassis Trunking on ICX switches
• Verify the operation of MCT using the ICX CLI
• Analyze switch logs during MCT failures
Commands Context Comment
cluster <name> <id> Global Configuration Creates an MCT cluster
rbridge-id <id> Cluster Configuration Defines the local RBridge ID
session-vlan <vlan-id> Cluster Configuration Defines the VLAN used for CCP
keep-alive-vlan <vlan-id> Cluster Configuration Defines the VLAN used for keep-alive
messages
member-vlan <vlan-id> Cluster Configuration Defines member VLAN to used in the cluster
icl <name> ethernet <if> Cluster Configuration Defines the interface to use for CCP
peer <ip> rbridge-id <id> icl Cluster Configuration Defines the MCT peer switch
<icl>
deploy Cluster Configuration Activates the cluster configuration
client <name> Cluster Configuration Creates an MCT client
rbridge-id <id> Cluster Client Defines MCT client RBridge ID
Configuration
client-interface ethernet Cluster Client Defines interfaces connecting to the MCT
<if> Configuration client
deploy Cluster Client Activates the client configuration
Configuration

Connect to the RSL

The following steps will prepare the devices used in these lab exercises for upcoming lab exercises.
1. On RKUS-04 and RKUS-05, execute the commands to erase the startup-config file and reload the
switch.
RKUS-04# reload
2. On RKUS-07 and RKUS-08, execute the commands to erase the startup-config file and reload the
switch from the secondary flash.
RKUS-07# boot sys flash secondary
3. On RKUS-04, RKUS-05, RKUS-07 and RKUS-08, configure the hostnames as described in
Table 13 below.
TABLE 13 Device Hostnames
Device Hostname
RKUS-04 RKUS-04
RKUS-05 RKUS-05
RKUS-07 R7-MCT1
RKUS-08 R8-MCT2
Example:
ICX7450-24 Switch> enable
ICX7450-24 Switch# conf t
ICX7450-24 Switch(config)# hostname RKUS-04
RKUS-04(config)#
4. On RKUS-04 and RKUS-05 disable interfaces e1/1/1 to e1/1/24.

5. On R7-MCT1 and R8-MCT2, disable all interfaces, stacking ports and the management interface.
(config-if-mgmt-1)# exit
6. On R7-MCT1 and R8-MCT2, execute the Global Configuration command to ensure the device
boots from the secondary flash on all reloads.
R7-MCT1(config)# boot sys flash sec

Configure MCT
In the following steps MCT will be in configured as displayed in the topology diagram below.
FIGURE 9 MCT Lab Topology
Configure Cluster Client Link Aggregation Groups (LAGs) and VLANs

In the following steps, cluster client LAGs and user VLANs will be configured for connectivity to the
MCT peer switches.
7. On RKUS-04, configure VLAN 2 with the name Client-VLAN. Add ports 1/1/23 and 1/1/24 as
tagged ports and port 1/1/9 as an untagged port.
RKUS-04(config)# vlan 2 name Client-VLAN
RKUS-04(config-vlan-2)# tagged e1/1/23 to 1/1/24
RKUS-04(config-vlan-2)# untagged e1/1/9

8. On RKUS-04, configure ports 1/1/23 and 1/1/24 for dynamic link-aggregation and enable the
interfaces.
RKUS-04(config-vlan-2)# lag Client4 dynamic
RKUS-04(config-lag-Client4)# ports e 1/1/23 to 1/1/24
RKUS-04(config-lag-Client4)# primary-port 1/1/23
RKUS-04(config-lag-Client4)# deploy
LAG Client4 deployed successfully!
RKUS-04(config-lag-Client4)# enable e 1/1/23 to 1/1/24
9. On RKUS-04, enable port 1/1/9.
RKUS-04(config-lag-Client4)# interface e1/1/9
10. On RKUS-05, configure VLAN 2 with the name Client-VLAN. Add ports 1/1/3, 1/1/5 and 1/1/6 as
tagged ports and port 1/1/9 as an untagged port.
RKUS-05(config)# vlan 2 name Client-VLAN
RKUS-05(config-vlan-2)# tagged e1/1/3 e1/1/5 to 1/1/6
Added tagged port(s) ethe 1/1/3 ethe 1/1/5 to 1/1/6 to port-vlan 2.
RKUS-05(config-vlan-2)# untagged e1/1/9
11. On RKUS-05, configure ports 1/1/3, 1/1/5 and 1/1/6 for dynamic link-aggregation and enable
the interfaces.
RKUS-05(config-vlan-2)# lag Client5 dynamic
RKUS-05(config-lag-Client5)# ports e 1/1/3 e 1/1/5 to 1/1/6
RKUS-05(config-lag-Client5)# primary-port 1/1/5
RKUS-05(config-lag-Client5)# deploy
LAG Client5 deployed successfully!
RKUS-05(config-lag-Client5)# enable e 1/1/3 e 1/1/5 to 1/1/6
12. On RKUS-05, enable port 1/1/9.
RKUS-05(config-lag-Client5)# interface e1/1/9
Configure MCT Peer 1

In the following steps, lab switch RKUS-07 will be configured for multi-chassis trunking (MCT).
13. On R7-MCT1, execute the following commands to configure the LAGs and VLANs used in the lab
topology.
a. Configure a dynamic LAG for the MCT ICL with an ID of 64
R7-MCT1(config)# lag ICL static id 64
b. Assign ports e1 as a member.
R7-MCT1(config-lag-ICL)# ports ethernet 1/1/1
c. Define port e1 as the primary port
R7-MCT1(config-lag-ICL)# primary-port 1/1/1
d. Deploy the LAG
R7-MCT1(config-lag-ICL)# deploy

e. Configure a dynamic LAG for connectivity to cluster client 4 (RKUS-04) with and ID of 4, assign
port 1/1/24 as a member and primary port, then deploy the LAG.
R7-MCT1(config-lag-ICL)# lag CC4 dynamic id 4
R7-MCT1(config-lag-CC4)# ports ethernet 1/1/24
R7-MCT1(config-lag-CC4)# primary-port 1/1/24
R7-MCT1(config-lag-CC4)# deploy
f. Configure a dynamic LAG for connectivity to cluster client 5 (RKUS-05) with and ID of 5, assign
ports 1/1/5-1/1/6 as members and 1/1/5 as the primary port, then deploy the LAG.
R7-MCT1(config-lag-CC4)# lag CC5 dynamic id 5
R7-MCT1(config-lag-CC5)# ports ethernet 1/1/5 to 1/1/6
g. Configure VLAN 2 with the name Client-VLAN and add ports 1/1/1, 1/1/5-1/1/6 and 1/1/24
as tagged ports. Create router-interface VE2.
R7-MCT1(config-lag-CC5)# vlan 2 name Client-VLAN
R7-MCT1(config-vlan-2)# tagged e1/1/1 e1/1/5 to 1/1/6 e1/1/24
R7-MCT1(config-vlan-2)# router-interface ve 2
h. Assign interface VE2 an IP address of 10.10.200.1/24.
R7-MCT1(config-vlan-2)# interface ve 2
R7-MCT1(config-vif-2)# ip address 10.10.200.1/24
i. Configure the MCT session VLAN as VLAN 150 with the name of MCT-VLAN, assign port 1/1/1
as tagged port and create router-interface VE150.
R7-MCT1(config-vif-2)# vlan 150 name MCT-VLAN
R7-MCT1(config-vlan-150)# tagged ethe 1/1/1
j. Assign interface VE150 an IP address of 1.1.1.1/24.
14. On R7-MCT1, execute the following commands to configure the MCT cluster.
a. Configure a cluster named MCT with an ID of 1.
R7-MCT1(config-vif-150)# cluster MCT 1
b. Assign the rbridge-id of 1 to the cluster.
R7-MCT1(config-cluster-MCT)# rbridge-id 1
c. Define the session-vlan as VLAN 150.
R7-MCT1(config-cluster-MCT)# session-vlan 150
Info - IP addresses configured on VE 150 will not be advertised as
connected route by any routing protocol as it is configured as
session-vlan.
d. Define the ICL with the name of ICL over port 1/1/1.
R7-MCT1(config-cluster-MCT)# icl ICL ethernet 1/1/1
e. Define the IP address, rbridge-id and ICL used for communications to the MCT peer switch.
R7-MCT1(config-cluster-MCT)# peer 1.1.1.2 rbridge-id 2 icl ICL

Note
The MCT peer has not been configured at this point in the lab exercise. The IP address,
rbridge-id and ICL used must match those configured on the remote peer.
f. Deploy the cluster.

R7-MCT1(config-cluster-MCT)# deploy
15. On R7-MCT1, execute the following commands to configure the MCT clients.
a. Configure a cluster client named CC4 with an rbridge-id of 400, a client-interface of 1/1/24,
and deploy the client.
R7-MCT1(config-cluster-MCT)# client CC4
R7-MCT1(config-cluster-MCT-client-CC4)# rbridge-id 400
R7-MCT1(config-cluster-MCT-client-CC4)# client-interface e 1/1/24
R7-MCT1(config-cluster-MCT-client-CC4)# deploy
b. Configure a cluster client named CC5 with an rbridge-id of 500, a client-interface of 1/1/5,
R7-MCT1(config-cluster-MCT-client-CC4)# client CC5
16. On R7-MCT1, enable interface e1, e5-6, and e24.
R7-MCT1(config-cluster-MCT-client-CC5)# int e1/1/1
R7-MCT1(config-if-e1000-1/1/1)# enable
R7-MCT1(config-if-e1000-1/1/1)# int e1/1/5

View MCT Statistics with Single Operational Peer
In the following steps, statistics will be viewed while only one MCT peer is operational. These statistics
will be similar to what would be seen if there is failure of one MCT peer.
17. On R7-MCT1, execute the show cluster 1 peer command.
a. Under Cluster MCT1, note the following values:
RBridge ID: ________1
Session Vlan: ___________2
Client Isolation Mode: ________________3
Note
Client Isolation Mode: Loose is the default on MCT cluster devices.
b. Under Peer Info, note the following values:

Peer IP: _______________________4
Peer RBridge ID: ________5
ICL: _______6
Peer State: ________________7
Reason: _____________________________8
Check Point: Do not proceed unless all answers in the above step match the answer key at the bottom
of this page.
18. On R7-MCT1, execute the show cluster 1 client command.
What is the FSM-State of both cluster clients? ________________9
Why? ____________________________________________________10
19. On PC1, start a continuous ping to PC2 (10.10.200.200). Leave the PC1 window open.
C:\Documents and Settings\Administrator> ping 10.10.200.200 -t
Is the ping successful? ______11
Important
Do not continue unless the ping is successful in the above step.
1. 1
2. 150
3. Loose
4. 1.1.1.2
5. 2
6. ICL
7. CCP Down
8. ICL interface down
9. Master
10. MCT peer is not active. It has not been configured yet.
11. Yes

20. On R7-MCT1, clear the log buffer.
R7-MCT1# clear log
21. On R7-MCT1, configure client isolation mode strict.
R7-MCT1# conf t
R7-MCT1(config)# cluster MCT 1
R7-MCT1(config-cluster-MCT)# client-isolation strict
22. On PC1, is the ping is still successful? ______12
23. On R7-MCT1, view the log buffer.
R7-MCT1# show log
Output will be displayed similar to the following:
System: Interface ethernet 1/6, state down
What does this output indicate:

____________________________________________________________________
____________________________________________________________________13
Why did this occur:
____________________________________________________________________
____________________________________________________________________14
Configure MCT Peer 2

In the following steps, lab switch RKUS-08 will be configured for multi-chassis trunking (MCT).
24. On R8-MCT2, execute the following commands to configure the LAGs and VLANs used in the lab
topology.
a. Configure a dynamic LAG for the MCT ICL with and ID of 64, port 1/1/1 as a member and the
primary port, and then deploy the LAG.
R8-MCT2(config)# lag ICL static id 64
R8-MCT2(config-lag-ICL)# ports ethernet 1/1/1
R8-MCT2(config-lag-ICL)# primary-port 1/1/1
R8-MCT2(config-lag-ICL)# deploy
b. Configure a dynamic LAG for connectivity to cluster client 4 (RKUS-04) with and ID of 4, assign
port 1/1/24 as a member and primary port, and then deploy the LAG.
R8-MCT2(config-lag-ICL)# lag CC4 dynamic id 4
12. No
13. The ports configured as cluster-client edge ports (CCEP) have been disabled
14. When client isolation mode strict is configured, all CCEP ports are disabled when the ICL is down

c. Configure a dynamic LAG for connectivity to cluster client 5 (RKUS-05) with and ID of 5, assign
port 1/1/3 as a member and as the primary port, and then deploy the LAG.
R8-MCT2(config-lag-CC4)# lag CC5 dynamic id 5
d. Configure VLAN 2 with the name Client-VLAN and add ports 1/1/1, 1/1/3 and 1/1/24 as
tagged ports. Create router-interface VE2.
R8-MCT2(config-lag-CC5)# vlan 2 name Client-VLAN
R8-MCT2(config-vlan-2)# tagged e1/1/1 e1/1/3 e1/1/24
e. Assign interface VE2 an IP address of 10.10.200.2/24.
f. Configure the MCT session VLAN as VLAN 150 with the name of MCT-VLAN, assign port 1/1/1
as a tagged port and create router-interface VE150.
R8-MCT2(config-vif-2)# vlan 150 name MCT-VLAN
R8-MCT2(config-vlan-150)# tagged ethe 1/1/1
g. Assign interface VE150 an IP address of 1.1.1.2/24.
25. On R8-MCT2, execute the following commands to configure the MCT cluster.
a. Configure a cluster named MCT with an ID of 1.
R8-MCT2(config-vif-150)# cluster MCT 1
b. Assign the rbridge-id of 2 to the cluster.
R8-MCT2(config-cluster-MCT)# rbridge-id 2
c. Configure client isolation mode strict.
R8-MCT2(config-cluster-MCT)# client-isolation strict
d. Define the session-vlan as VLAN 150.
R8-MCT2(config-cluster-MCT)# session-vlan 150
e. Define the ICL with the name of ICL over port e1.
R8-MCT2(config-cluster-MCT)# icl ICL ethernet 1/1/1
f. Define the IP address, rbridge-id and ICL used for communications to the MCT peer switch.
R8-MCT2(config-cluster-MCT)# peer 1.1.1.1 rbridge-id 1 icl ICL
g. Deploy the cluster.

26. On R8-MCT2, execute the following commands to configure the MCT clients.
a. Configure a cluster client named CC4 with an rbridge-id of 400, a client-interface of 1/1/24,
R8-MCT2(config-cluster-MCT)# client CC4
b. Configure a cluster client named CC5 with an rbridge-id of 500, a client-interface of 1/1/3,
R8-MCT2(config-cluster-MCT-client-CC4)# client CC5
27. On R8-MCT2, enable interfaces 1/1/1, 1/1/3, and 1/1/24.
R8-MCT2(config-cluster-MCT-client-CC5)# int e1/1/1
28. On PC1, execute a continuous ping to PC2 (10.10.200.200).
Is the ping successful? ______15
Important
29. On R7-MCT1, execute the show cluster 1 peer command.

How is the Peer State different than it was in Step 17? ________________16
What is the FSM-State of both cluster clients? ________________17
Configure a Keepalive VLAN

In the following steps, a keepalive VLAN will be configured to allow connectivity to cluster client
devices even when the ICL is down.
31. On R7-MCT1 and R8-MCT2, disable client isolation mode strict from cluster MCT 1.
R7-MCT1(config)# cluster MCT 1
R7-MCT1(config-cluster-MCT)# no client-isolation strict
15. Yes
16. CCP Up (was CCP Down in step 16)
17. Up

32. On R7-MCT1 and R8-MCT2, create VLAN 100 and add interface e1/1/2 as a tagged port.
R7-MCT1(config-cluster-MCT)# vlan 100
R7-MCT1(config-vlan-100)# tag e1/1/2
33. On R7-MCT1 and R8-MCT2, assign VLAN 100 as the cluster MCT 1 keepalive VLAN.
Note
A keepalive VLAN cannot be assigned to an actively deployed MCT cluster. The no deploy
command must be used prior to defining the keepalive VLAN, then the cluster must be
deployed again.
R7-MCT1(config-vlan-100)# cluster MCT 1

R7-MCT1(config-cluster-MCT)# no deploy
R7-MCT1(config-cluster-MCT)# keep-alive-vlan 100
34. On R7-MCT1 and R8-MCT2, enable interface e1/1/2.
R8-MCT2(config-cluster-MCT)# int e1/1/2
View MCT Failover Operations

35. On PC1, view the continuous ping to PC2 (10.10.200.200) and ensure it is still successful.
Important
36. On R7-MCT1, disable the ICL (interface e1).

R7-MCT1(config)# int e1/1/1
R7-MCT1(config-if-e1000-1/1/1)# disable
37. On PC1, is the ping is still successful? ______18
What is the FSM-State of both clients? ________________________________________19
What is the FSM-State of both clients? ________________________________________20
Why is R7-MCT1 Master and R8-MCT2 the Slave for these cluster clients?
____________________________________________________________________21
40. On R7-MCT1, re-enable the ICL (interface e1/1/1) to restore normal MCT operations.
18. Yes
19. Master Peer Reachable
20. Slave
21. R7-MCT1 has a lower RBridge ID (1) than R8-MCT2 (2)

This ends the Module 15 Lab: Multi-Chassis Trunking lab exercise.


Test

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Test

Hochgeladen von

Copyright:

Verfügbare Formate

ICX 200

European Headquarters - Geneva, Switzerland

Asia Pacific Headquarters - Singapore

© 2017 Brocade Communications Systems, Inc. All Rights Reserved.

Module 4 Lab: Link Aggregation Groups and VLANs

Module 5 Lab: Layer 2 Redundancy

Module 8 Lab: VRRP-Extended (VRRP-E)

Module 9 Lab A: OSPF Neighbor Adjacency and Link Cost

ICX 200 Revision 0817 iii

Module 9 Lab B: Partitioning OSPF Areas and Redistribution between RIP

Module 9 Lab C: OSPF Route Summarization and Area Types

Module 15 Lab: Multi-Chassis Trunking

iv Revision 0817 ICX 200

ICX 200 Revision 0817 v

Revision 0817 ICX 200 1

Command Mode Hierarchy

• What is your current prompt?

• How has the prompt changed?

• How did the prompt change?

2 Revision 0817 ICX 200

• How did the prompt change?

• What was the response?

Using the CLI Help (?)

Revision 0817 ICX 200 3

7. Configure and copy.

4 Revision 0817 ICX 200

• What is the response?

• What is the response?

Revision 0817 ICX 200 5

Configuration File Management

6 Revision 0817 ICX 200

• Do you have an entry for interface ethernet 1/1/9? (Yes / No)11

11. Yes, interface e 1/1/9 is disabled

Revision 0817 ICX 200 7

interface ethernet 1/1/8

interface ethernet 1/1/8

8 Revision 0817 ICX 200

interface ethernet 1/1/7

33. On RKUS-04, enter the copy tftp startup-config 10.10.200.100

interface ethernet 1/1/8

Revision 0817 ICX 200 9

Local Account and SSH Enablement

10 Revision 0817 ICX 200

Revision 0817 ICX 200 11

Command Context Comment

12 Revision 0817 ICX 200

Enter the number of the desired UPSTREAM units (0-2)[0]: 2

Confirm Stacking Links...

UPSTREAM Unit: Id new at 1 hop(s) ICX7450-24P 0024.38b7.7040

Revision 0817 ICX 200 13

UPSTREAM Unit: Id new at 2 hop(s) ICX7450-24P 0024.38b7.4bc0

Enter the desired links(1-2)[1]: 2

Selected DOWNSTREAM units

Do you accept the unit id's (y/n)?: y

14 Revision 0817 ICX 200

52. On RKUS-03, view the stack configuration.

Revision 0817 ICX 200 15

16 Revision 0817 ICX 200

Revision 0817 ICX 200 17

Removing the Stacking Configuration

18 Revision 0817 ICX 200

Revision 0817 ICX 200 19

FIGURE 1 LAG Configuration Topology

Revision 0817 ICX 200 21

• Enter the member ports of VLAN 222: Untagged_11 Tagged_12