CCNP Enterprise Workbook v1.0
CCNP Enterprise Workbook v1.0
COM/C/NETWORKJOURNEY
WORKBOOK
Table of Contents
Verifications: 8
Verifications: 13
VERIFICATIONS: 18
CONFIGURATIONS: 50
VERIFICATION TASK#5 50
VERIFICATION TASK#6 51
CONFIGURATION TASK#7: To manipulate “hello timer” in MST switch SCOTSW02 51
VERIFICATION TASK#7: 51
VERIFICATION TASK#8: 52
IMPORTANT FACT!!! 52
Switch#reload
Proceed with reload? [confirm]
vlan 100
name SERVERS
!
vlan 110
name GUEST
!
vlan 120
name OFFICE
!
vlan 999
name PARKING_LOT
state suspend
!
vlan 666
name NATIVE_DO_NOT_USE
exit
3. Create Management Interface on Vlan 99
4. Enable Telnet and SSH for Remote connection for user id “admin” with privilege level
“15” with password “cisco”
Configuration:
SCOTSW01
Switch#configure terminal
Switch(config)#hostname SCOTSW01
SCOTSW01(config)#vlan 99
SCOTSW01(config-vlan)#name MANAGEMENT
SCOTSW01(config-vlan)#!
SCOTSW01(config-vlan)#vlan 100
SCOTSW01(config-vlan)#name SERVERS
SCOTSW01(config-vlan)#!
SCOTSW01(config-vlan)#vlan 110
SCOTSW01(config-vlan)#name GUEST
SCOTSW01(config-vlan)#!
SCOTSW01(config-vlan)#vlan 120
SCOTSW01(config-vlan)#name OFFICE
SCOTSW01(config-vlan)#!
SCOTSW01(config-vlan)#vlan 999
SCOTSW01(config-vlan)#name PARKING_LOT
SCOTSW01(config-vlan)#state suspend
SCOTSW01(config-vlan)#!
SCOTSW01(config-vlan)#vlan 666
SCOTSW01(config-vlan)#name NATIVE_DO_NOT_USE
SCOTSW01(config-vlan)#exit
NOTE: The VLANs will not appear in the VLAN database until the exit command is issued
To globally suspend a VLAN, use the state suspend command in the VLAN configuration mode.
This state is propagated by VTP to all other switches in the VTP domain if VTP is in use.
To locally shut down a VLAN, use the shutdown command in the VLAN configuration mode. This
setting is not propagated through VTP
SCOTSW01(config)#interface vlan 99
SCOTSW01(config-if)#ip address 192.168.99.101 255.255.255.0
SCOTSW01(config-if)#no shutdown
SCOTSW01(config-if)#exit
NOTE: Interface Vlan 99 will be initially Down as the Vlan 99 (broadcast) is not mapped with any
interface.
Wait for some time. We will make Trunking between inter-switch’s and allow Vlan 99
NOTE: We are creating user “admin” with highest privilege of 15 level. Hence, no need to creating
“enable secret “ or “enable password “
The Hostname, Management IP address will differ for each switch. So please refer the topology
for the right hostname and management IP address.
Verifications:
After configuring the VLANs, issue the show vtp status command and you will see that the all-
important configuration revision number has increased based on these changes to the VLAN
database. Note that the revision number you have when performing this lab may be different.
You can test if telnet and ssh are configured rightly or not by doing self-connection test
To self-test telnet:
SCOTSW01#telnet 192.168.99.101
Trying 192.168.99.101 ... Open
To self-test SSH:
SCOTSW01#ssh -l admin 192.168.99.101
**************************************************************************
* IOSv is strictly limited to use for evaluation, demonstration and IOS *
* education. IOSv is provided as-is and is not supported by Cisco's *
* Technical Advisory Center. Any use or disclosure, in whole or in part, *
* of the IOSv Software or Documentation to any third party for any *
* purposes is expressly prohibited except as otherwise authorized by *
* Cisco in writing. *
**************************************************************************
Password:
The Hostname, Management IP address will differ for each switch. So please refer the topology
for the right hostname and management IP address.
Verify the configured commands with the help of above “show ….” Commands accordingly.
SCOTSW02#
int range gi0/0-1
no sw trunk native vlan 666
8. After synchronization both switches must not propagate VLAN configuration changes to
each other
Configuration:
SCOTW01
hostname SCOTSW01
vlan 811
mtu 1400
SCOTSW02
hostname SCOTSW02
SCOTSW03
hostname SCOTSW03
SCOTSW04
hostname SCOTSW04
SCOTSW05
hostname SCOTSW05
SCOTSW06
hostname SCOTSW06
SCOTSW07
hostname SCOTSW07
SCOTSW08
hostname SCOTSW08
NOTE: The VTP will only start working once “trunking” is configured and activated.
VTP is functional only on over Trunking interface.
Verifications:
**GNS3 and EVE-NG both failed at task 3. This might be due to IOS version used inside Emulators
**I got successful output with Packet-Tracer.
**As a turnover fix on GNS/Eveng, make SCOTSW03 SCOTSW04 as “client mode”
Feature VLAN:
--------------
VTP Operating Mode : Server
Maximum VLANs supported locally : 1005
Number of existing VLANs : 27
Configuration Revision : 18
MD5 digest : 0x25 0xB6 0x82 0xAA 0x89 0xE6 0xBE 0x33
0xD7 0x6E 0xA6 0x03 0x19 0x4D 0xE5 0xAD
Note: MD5 digest changes everytime because the configuration revision number is used to calculate the
hash and as it is different after creating the vlan then the md5 will be different.
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
811 enet 100811 1400 - - - - - 0 0
VERIFICATION TASK 8:
Config:
SCOTSW01(config)#vtp mode transparent
Verifications:
SCOTSW01#sh vtp status | i Operating
VTP Operating Mode : Transparent
VTP version 3 is backwards compatible with VTP version 2; at the boundary of the two protocols, a
VTP version 3 switch will send out both version 3 and version 2-compatible messages. Version 2
messages received by a version 3 switch are discarded.
Switch(config)#vtp version 3
Cannot set the version to 3 because domain name is not configured
1. The VTP domain should be configured to “CCNP_ENTERPRISE” (without the quotes) since it
is already done in Lab#2, goto Task#2.
2. Configure VTP version 3 on SCOTSW01, SCOTSW03, SCOTSW05, SCOTSW07.
Configuration:
SCOTW01
vtp version 3
SCOTW05
SCOTSW05(config)#vtp version 3
SCOTSW05(config)#vtp mode server
SCOTW07
SCOTSW07(config)#vtp version 3
SCOTSW07(config)#vtp mode client
Answer for #4
SCOTW01
!
Vlan 444
exit
!
VERIFICATIONS:
VERIFICATION TASK 1:
Feature VLAN:
--------------
VTP Operating Mode : Primary Server
Number of existing VLANs :5
Number of existing extended VLANs : 0
Maximum VLANs supported locally : 4096
Configuration Revision :1
Primary ID : 0c67.916e.8000
Primary Description : SCOTSW01
MD5 digest : 0x74 0xEB 0x87 0xFF 0xA2 0x91 0x60 0x2D
0xFD 0x82 0x67 0x93 0xC4 0x6C 0x2B 0xB4
Feature MST:
--------------
VTP Operating Mode : Transparent
Feature UNKNOWN:
--------------
VTP Operating Mode : Transparent
VERIFICATION TASK 2:
Verify VTP packet versions getting by VTPv3 switch to another VTPv3 and also VTPv3 switch to VTPv2
using Wiresharks:
VTPv3 Primary Server Switch will advertise advertisement of version 3 to Switch running on VTPv3
mode.
VTPv3 Primary Server Switch will advertise advertisement of version 2 to Switch running on VTPv2
mode.
VERIFICATION TASK 3:
All other Switches are pointing to SCOTSW01 which is VTPv3 Primary Server.
Use the show spanning-tree root command on all of the switches to find the root switch for all of the VLANs.
Note: Your results may vary from the examples.
The current root bridge was elected based on the lowest Bridge ID (consisting of the Priority,
extended system ID equal to the VLAN ID, and base MAC address values). In the output above, the
root’s MAC is 0c67.9114.be00
There are two basic ways to manipulate the configuration to control the location of the root bridge.
• The spanning-tree vlan vlan-id priority value command can be used to manually set a
priority value
• The spanning-tree vlan vlan-id root { primary | secondary } command can be
used to automatically set a priority value.
The difference between the two is the priority command will set a specific number (multiple of
4096) as the priority, while the root primary command will set the local bridge's priority to 24,576 (if
the local bridge MAC is lower than the current root bridge's MAC) or 4096 lower than the current
root's priority (if the local bridge MAC is higher than the current root bridge's MAC).
The logic behind this operation is straight-forward. The root primary command tries to lower the
priority only as much as is needed to win the root election, while leaving priorities between 24576
and the default 32768 for use by secondary bridges. The command always takes the entire Bridge ID
into account when computing the resulting priority value.
SCOTTSW01# conf t
Enter configuration commands, one per line. End with CNTL/Z.
SCOTTSW01(config)# spanning-tree vlan 1 root primary
SCOTTSW02(config)# exit
SCOTTSW02# conf t
SCOTTSW02(config)# spanning-tree vlan 1 root secondary
SCOTTSW02(config)# exit
The Priority is lowered to 24,576 on Primary Root (Calculation: 32768-8192 for primary root)
SCOTTSW01# sh spanning-tree
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 24577
Address 0c67.916e.7e00
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
The Priority is lowered by 28,672 on Secondary Root (Calculation: 32768-4096 for secondary root)
SCOTTSW02# sh spanning-tree
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 24577
Address 0c67.916e.7e00
Cost 4
Port 1 (GigabitEthernet0/0)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
The show spanning-tree bridge command also provides detailed information about the current
configuration of the local bridge:
As the network is implemented right now, there are two paths between each directly connected
switch. As the Root Port is elected, path and port costs are evaluated to determine the shortest path
to the root bridge.
In the case where there are multiple equal cost paths to the root bridge, additional attributes must
be evaluated. In our case, the lower interface number (for example, Gi0/1) is chosen as the Root
Port, and the higher interface number (for example, Gi0/2) is put into a spanning tree Blocking state.
You can see which ports are blocked with the show spanning-tree vlan-id command or the show
spanning-tree blockedports command. For now, examine VLAN 1 on SCOTTSW02, SCOTTSW03,
SCOTTSW04.
SCOTTSW02#show spanning-tree
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 24577
Address 0c67.916e.7e00
Cost 4
Port 1 (GigabitEthernet0/0)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 28673 (priority 28672 sys-id-ext 1)
Address 0c67.9159.b100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi0/0 Root FWD 4 128.1 P2p
Gi0/1 Altn BLK 4 128.2 P2p
Gi0/2 Desg FWD 4 128.3 P2p
Gi0/3 Desg FWD 4 128.4 P2p
Gi1/0 Desg FWD 4 128.5 P2p
Gi1/1 Desg FWD 4 128.6 P2p
Gi1/2 Desg FWD 4 128.7 P2p
Note: The changes you are about to implement are considered topology changes and could have a
significant impact on the overall structure of the spanning tree in your switch network. Do not
make these changes in a production network without careful planning and prior coordination.
Goto SCOTTSW03 and Manipulate the Cost for Gi0/3 (currently STP blocked port)
SCOTTSW03#sh spanning-tree
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 24577
Address 0c67.916e.7e00
Cost 4
Port 3 (GigabitEthernet0/2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
SCOTTSW03# conf t
Enter configuration commands, one per line. End with CNTL/Z.
SCOTTSW03(config)#int ran gi0/2-3
SCOTTSW03(config-if-range)#shut
SCOTTSW03(config-if-range)#exit
SCOTTSW03(config)#interface gi0/3
SCOTTSW03(config-if)#spanning-tree cost 2
SCOTTSW03(config-if)#exit
SCOTTSW03#show spanning-tree
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 24577
Address 0c67.916e.7e00
Cost 2
Port 4 (GigabitEthernet0/3)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 0c67.912e.9400
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi0/0 Desg FWD 4 128.1 P2p
Gi0/1 Desg FWD 4 128.2 P2p
Gi0/2 Altn BLK 4 128.3 P2p
Gi0/3 Root FWD 2 128.4 P2p
Gi1/0 Desg FWD 4 128.5 P2p
Gi1/1 Desg FWD 4 128.6 P2p
Gi1/2 Desg FWD 4 128.7 P2p
Alternatively, you can modify this behaviour with manipulating Port-Priority as well:
Verifications:
SCOTTSW03#
*Apr 20 13:13:57.732: STP: VLAN0001 Gi0/2 -> listening
*Apr 20 13:13:58.090: STP: VLAN0001 heard root 24577-0c67.916e.7e00 on Gi0/2
*Apr 20 13:13:58.091: supersedes 32769-0c67.9114.be00
*Apr 20 13:14:12.731: STP: VLAN0001 Gi0/2 -> learning
*Apr 20 13:14:27.738: STP[1]: Generating TC trap for port GigabitEthernet0/2
*Apr 20 13:14:27.740: STP: VLAN0001 sent Topology Change Notice on Gi0/2
*Apr 20 13:14:27.740: STP: VLAN0001 Gi0/2 -> forwarding
*Apr 20 13:14:29.156: STP: VLAN0001 Topology Change rcvd on Gi0/0
*Apr 20 13:14:29.158: STP: VLAN0001 sent Topology Change Notice on Gi0/2
Upon activating RSTP on every switch, you can see “proposal” and “agreements”
In addition to above output, we can see additional two features “ALT BLK” port and “BACKUP BLK”
port in RSTP.
SCOTSW01#sh spanning-tree
VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 4097
Address 0c67.91c0.f900
Cost 12
Port 3 (GigabitEthernet0/2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
<!output omitted>
Gi0/3 Altn BLK 4 128.4 P2p Altn BLK = Uplinkfast (Alternate port)
SCOTSW08#show spanning-tree
VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 32769
Address 0c67.9114.be00
Cost 4
Port 3 (GigabitEthernet0/2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Or
SCOTTSW03(config)#interface gi0/3
SCOTTSW03(config-if)#spanning-tree cost 2
SCOTTSW03(config-if)#exit
Method 2: Alternatively, you can modify this behaviour with manipulating Port-Priority as well:
Switch(config)#int gi0/0
Switch(config-if)#spanning-tree port-priority ?
<0-224> port priority in increments of 32
PC2:
#
# This is a sample network config uncomment lines to configure the network
#
# Static config for eth0
auto eth0
iface eth0 inet static
address 192.168.99.2
netmask 255.255.255.0
gateway 192.168.99.100
up echo nameserver 192.168.0.1 > /etc/resolv.conf
SCOTSW07:
interface vlan 99
ip address 192.168.99.107 255.255.255.0
no shut
exit
int gi0/0
switchport mode access
switchport access vlan 99
no shut
int gi0/3
switchport mode access
switchport access vlan 99
no shut
Now ping from PC1 to PC2 over RSTP, it would take 1 second to switchport transit from “Learning”
to “Forwarding”
Let us see by enabling the “Portfast” features on Egde port, SCOTSW07_Gi0/0 and Gi0/3
SCOTSW07(config)#int gi0/0
SCOTSW07(config-if)#spanning-tree portfast
SCOTSW07(config)#int gi0/3
SCOTSW07(config-if)#spanning-tree portfast
To test the “portfast” behaviour, shut/no shutdown SCOTSW07_Gi0/0 and observe the time it takes
to allow PING reachability between PC1 and PC2
SCOTSW07(config-if)#int gi0/0
SCOTSW07(config-if)#shut
SCOTSW07(config-if)#no shut
BPDU Guard feature can be enabled globally at Global configuration mode or per interface
at Interface configuration mode.
When a BPDU Guard enabled port receive BPDU from the connected device, BPDU Guard
disables the port and the port state is changed to Errdisable state.
Global and Interface config has the same impact on receiving any BPDU, they would put the
switchport in “err-disabled” state.
**Initial Config PC1, PC2 and SCOTSW07 as above done for “portfast” lab
Considering the fact, you have already configured “portfast” on SCOTSW07_Gi0/0 in the previous
Task.
Remove the cable between SCOTSW07 and PC1, plug the same cable between SCOTSW07 <-> BAD-
SWITCH
SCOTSW07(config-if)#
The reason for detection and going into errdisable state is because by default “bpduguard”
detection is enabled on all switches as shown below:
We can set the automatic recovery for “bpduguard” for every “30” seconds
SCOTSW07#
SCOTSW07#sh int gi0/0
GigabitEthernet0/0 is up, line protocol is up (connected)
• BPDU Filtering at the global level will work with Portfast interfaces, and simply kick them
out of portfast if a BPDU is received.
• BPDU Filtering configured on the interface level will COMPLETELY stop send/receive
BPDU, and if you plug in two switches then you may have a loop because they don't 'see'
each other as a problem.
Now let us assume someone disconnected the PC1 and connected that cable to another BPDU
switch “BAD-SWITCH” as show in diagram below:
Also, both Switch SCOTSW07 <-> BAD-SWITCH becomes Root Bridge for Vlan 1 because BPDU are
not sent/received
The BPDU FILTER mode is removed in Global mode once BPDU is rcvd
If a root-guard-enabled port receives BPDUs that are superior to those that the current root
bridge is sending, then that port is moved to a root-inconsistent state, which is effectively equal to
an STP listening state, and no data traffic is forwarded across that port.
BEFORE ROOTGUARD:
SCOTSW01(config)#do sh span
VLAN0001
Spanning tree enabled protocol rstp
Root ID Priority 32769
Address 0c67.912e.9400
Cost 4
Port 3 (GigabitEthernet0/2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
AFTER ROOTGUARD:
Let us make SCOTSW01 as ROOT SWITCH.
If SCOTSW01 received any superior BPDU it will put that switchport into “root-inconsistent state”.
SCOTSW01#show spanning-tree
<!output omitted>
Gi0/2 Desg BKN*4 128.3 P2p Peer(STP) *ROOT_Inc
Gi0/3 Desg BKN*4 128.4 P2p Peer(STP) *ROOT_Inc
Remove that Switch which is sending Superior BPDU to SCOTSW01, you can remove the switch or
shutdown that interface.
Bounce the switchport (Shut/No Shutdown) on SCOTSW01 to rectify the “Inconsistency” mode:
CONFIGURATION TASK#1,2 & 3: To configure & verify MST Region 1, Region 2 and
Interoperability
SCOTSW01 (config)#
spanning-tree mode mst
spanning-tree mst configuration
name region1
revision 1
instance 1 vlan 99,100
instance 2 vlan 110,120
spanning-tree mst 1 priority 0
spanning-tree mst 2 priority 4096
SCOTSW02 (config)#
spanning-tree mode mst
spanning-tree mst configuration
name region1
revision 1
instance 1 vlan 99,100
instance 2 vlan 110,120
spanning-tree mst 1 priority 4096
spanning-tree mst 2 priority 0
SCOTSW03 (config)#
spanning-tree mode rapid-pvst
SCOTSW04 (config)#
spanning-tree mode mst
spanning-tree mst configuration
name region2
revision 1
instance 1 vlan 99,100
instance 2 vlan 110,120
spanning-tree mst 1 priority 8192
spanning-tree mst 2 priority 8192
VLAN0100
Spanning tree enabled protocol rstp
VLAN0110
Spanning tree enabled protocol rstp
Root ID Priority 32768
Address 0c67.9159.b100
Cost 4
Port 3 (GigabitEthernet0/2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
VLAN0120
Spanning tree enabled protocol rstp
Root ID Priority 32768
Address 0c67.9159.b100
Cost 4
Port 3 (GigabitEthernet0/2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
SCOTSW02(config)
spanning-tree mst 1 priority 4096
spanning-tree mst 2 priority 0
**********or***************
SCOTSW02(config)
spanning-tree mst 1 root secondary
spanning-tree mst 2 root primary
CONFIGURATIONS:
SCOTSW04(config)# interface gi0/3
SCOTSW04(config-if)#spanning-tree mst 0 cost 2000
SCOTSW04(config-if)#shutdown
SCOTSW04(config-if)#no shutdown
VERIFICATION TASK#5
SCOTSW04#show spanning int gi0/3
Mst Instance Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
MST0 Root FWD 2000 128.4 P2p Bound(RSTP)
MST1 Mstr FWD 20000 128.4 P2p Bound(RSTP)
MST2 Mstr FWD 20000 128.4 P2p Bound(RSTP)
VERIFICATION TASK#6
SCOTSW04#show spanning int gi0/3
Mst Instance Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
MST0 Root FWD 20000 64.4 P2p Bound(RSTP)
MST1 Mstr FWD 20000 64.4 P2p Bound(RSTP)
MST2 Mstr FWD 20000 64.4 P2p Bound(RSTP)
VERIFICATION TASK#7:
SCOTSW02# show spanning-tree mst
##### MST0 vlans mapped: 1-98,101-109,111-119,121-4094
Bridge address 0c67.9159.b100 priority 32768 (32768 sysid 0)
Root this switch for the CIST
Operational hello time 5 , forward delay 15, max age 20, txholdcount 6
Configured hello time 5 , forward delay 15, max age 20, max hops 20
The forward delay is the number of seconds a port waits before changing from its spanning-tree
learning and listening states to the forwarding state.
VERIFICATION TASK#8:
SCOTSW02# show spanning-tree mst
##### MST0 vlans mapped: 1-98,101-109,111-119,121-4094
Bridge address 0c67.9159.b100 priority 32768 (32768 sysid 0)
Root this switch for the CIST
Operational hello time 5 , forward delay 10, max age 20, txholdcount 6
Configured hello time 5 , forward delay 10, max age 20, max hops 20
The maximum-aging time is the number of seconds a switch waits without receiving spanning-tree
configuration messages before attempting a reconfiguration.
VERIFICATION TASK#9:
SCOTSW02#show spanning-tree mst
##### MST0 vlans mapped: 1-98,101-109,111-119,121-4094
Bridge address 0c67.9159.b100 priority 32768 (32768 sysid 0)
Root this switch for the CIST
Operational hello time 2 , forward delay 10, max age 30, txholdcount 6
Configured hello time 2 , forward delay 10, max age 30, max hops 20
IMPORTANT FACT!!!
To restart the protocol migration process (force the renegotiation with neighboring switches) on
the switch, use the below command under privileged EXEC command.:
VERIFICATION TASK#1:
SCOTSW01#show interfaces trunk
Port Mode Encapsulation Status Native vlan
Gi0/0 desirable n-isl trunking 1
Gi0/1 desirable n-isl trunking 1
<!—output omitted>
VERIFICATION TASK#2:
SCOTSW01#show interfaces trunk
Port Mode Encapsulation Status Native vlan
Gi0/2 auto n-isl trunking 1
Gi0/3 auto n-isl trunking 1
<!—output omitted>
Dynamic AUTO on both sides will not bring up “n-Trunking”as shown here SCOTSW03_gi0/0-1 <->
SCOTSW04_gi0/0-1.
It is recommended statically make it “Trunking” and do not keep DTP auto negotiations.
Some IOS software comes by default with “Auto” enabled on switchports.
VERIFICATION TASK#1
• show etherchannel summary
• show etherchannel detail
• show etherchannel port-channel
• show pagp counter
• show pagp neighbor
Local information:
Hello Partner PAgP Learning Group
Port Flags State Timers Interval Count Priority Method Ifindex
Gi0/2 SAC U6/S7 HQ 30s 1 128 Any 19
! This interface's partner is configured with PAgP Slow packets, has a system-id
! of 0c67.916e.8000 , a port priority of 128 , and is desirable in the bundle
! for 0d:01h:27m:31s.
Partner's information:
Port: Gi0/3
------------
Local information:
Hello Partner PAgP Learning Group
Port Flags State Timers Interval Count Priority Method Ifindex
Gi0/3 SAC U6/S7 HQ 30s 1 128 Any 19
Partner's information:
Port-channel: Po12
------------
Group: 12
----------
Port-channels in the group:
---------------------------
Port-channel: Po12
------------
When viewing the output of the show etherchannel summary command, the first thing that
should be checked is the EtherChannel status, which is listed in the Port-channel column. The
status should be SU
VERIFICATION TASK#2
• show etherchannel summary
• show etherchannel detail
• show etherchannel port-channel
• show spanning-tree vlan 1
• show lacp counters
• show lacp neighbor
Group: 11
----------
Group state = L2
Ports: 2 Maxports = 4
Port-channels: 1 Max Port-channels = 4
Protocol: LACP
Minimum Links: 0
Local information:
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Gi0/0 SP bndl 32768 0xB 0xB 0x1 0x3C
Partner's information:
Port: Gi0/1
------------
Local information:
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Gi0/1 SP bndl 32768 0xB 0xB 0x2 0x3C
Partner's information:
------------
VLAN0099
Spanning tree enabled protocol ieee
Partner's information:
The LACP counters can be cleared with the command clear lacp counters.
VERIFICATION TASK#3
show etherchannel summary
show etherchannel detail
show etherchannel port-channel
show spanning-tree vlan 99
R - Layer3 S - Layer2
U - in use N - not in use, no aggregation
f - failed to allocate aggregator
Group: 22
----------
Group state = L2
Ports: 2 Maxports = 4
Port-channels: 1 Max Port-channels = 1
Protocol: -
Minimum Links: 0
Port: Gi0/3
------------
Port-channel: Po22
------------
VLAN0099
Spanning tree enabled protocol ieee
Root ID Priority 32867
Address 0c67.912e.9400
Cost 4
Port 1 (GigabitEthernet0/0)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
LACP provides some additional tuning that is not available with PAgP.
LACP Fast:
The original LACP standards sent out LACP packets every 30 seconds. A link is deemed unusable if an
LACP packet is not received after three intervals, which results in a potential 90 seconds of packet
loss for a link before that member interface is removed from a port channel.
An amendment to the standards was made so that LACP packets are advertised every 1 second.
This is known as LACP fast because a link can be identified and removed in 3 seconds compared to
the 90 seconds specified in the initial LACP standard.
LACP fast is enabled on the member interfaces with the interface configuration command lacp rate
fast.
All the interfaces on both switches need to be configured the same—either using LACP fast or
LACP slow—for the EtherChannel to successfully come up.
Channel group 1
In some design scenarios using LACP, a minimum number of adjacencies is required before a port-
channel interface becomes active. This option can be configured with the port-channel interface
command port-channel min-links min-links.
Test the behaviour by shutting one of the physical member manually “shutdown”
SCOTSW01(config-if)# interface gi1/0/1
SCOTSW01(config-if)# shutdown
10:44:46.516: %ETC-5-MINLINKS_NOTMET: Port-channel Po1 is down bundled ports (1)
doesn't meet min-links
10:44:47.506: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabit
Ethernet1/0/2, changed state to down
10:44:47.508: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1,
changed state to down
10:44:48.499: %LINK-5-CHANGED: Interface GigabitEthernet1/0/1, changed state to
administratively down
10:44:48.515: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down
This may be done to ensure that the active member interface count proceeds with powers of two
(for example, 2, 4, 8) to accommodate load-balancing hashes.
The maximum number of member interfaces in a port channel can be configured with the port-
channel interface command lacp max-bundle max-links.
The port-channel master switch controls which member interfaces (and associated links) are active
by examining the LACP port priority. A lower port priority is preferred. If the port priority is the
same, then the lower interface number is preferred.
The master switch on a port channel is responsible for choosing which member interfaces are
active in a port channel when there are more member interfaces than the maximum number of
member interfaces associated with a port-channel interface.
The LACP system priority can be changed with the command lacp system-priority priority.
PRE_CHECKS:
SCOTSW01# show lacp sys-id
32768, 0062.ec9d.c500
CONFIG:
SCOTSW01# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
SW1(config)# lacp system-priority 1
POST_CHECKS:
SCOTSW01# show lacp sys-id
1, 0062.ec9d.c50
The interface configuration command lacp port-priority priority sets the interface priority.
SCOTSW01 is the master switch for port channel 11, the Gi0/1 interface becomes active, and port
Gi0/1 becomes Hot-standby.
PRE_CHECKS:
SCOTSW01# show etherchannel summary | b Group
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
11 Po1(SU) LACP Gi0/0(P) Gi0/1(H)
CONFIGS:
SCOTSW01(config)# interface gi0/1
SCOTSW01(config-if)# lacp port-priority 1
POST_CHECKS:
SCOTSW01# show etherchannel summary | b Group
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
11 Po1(SU) LACP Gi0/0(H) Gi0/1(P)
interface Ethernet0/2
ip address dhcp
end
MOSCOWR20
interface e0/1
no shut
interface e0/1.1
encap dot 1
ip address 172.16.10.2 255.255.255.0
interface e0/1.40
encap dot 40
ip address 172.16.40.2 255.255.255.0
interface Ethernet0/2
ip address dhcp
end
MOSCOWSW01
interface gi0/3
no shutdown
interface gi0/2
no shutdown
switchport mode access
switchport access vlan 40
interface range gi0/0-1
switchport tr enc dot1
switchport mode trunk
switchport trunk allowed vlan 1,40
MOSCOWSW02
interface gi0/3
no shutdown
interface gi0/2
no shutdown
switchport mode access
switchport access vlan 40
interface range gi0/0-1
switchport tr enc dot1
PC10
PC9
PC11
PC12
MOSCOWR19#ping 8.8.8.8
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 47/72/91 ms
MOSCOWR19#
MOSCOWR20#ping 8.8.8.8
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 44/61/85 ms
MOSCOWR20#
end
/ # traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 46 byte packets
1 172.16.10.1 (172.16.10.1) 4.968 ms 3.694 ms 4.079 ms →packet going via MOSCOWR19
2 192.168.32.2 (192.168.32.2) 5.946 ms 5.493 ms 6.467 ms
CONFIGURATION TASK #2: Configure “HSRPv1” for “Vlan 1”, observe the behaviour.
Configure HSRPv1
MOSCOWR19(router)
interface e0/1.1
standby 1 ip 172.16.10.254
standby 1 preempt
interface e0/1.40
standby 40 ip 172.16.40.254
MOSCOWR20(router)
interface e0/1.1
standby 1 ip 172.16.10.254
interface e0/1.40
standby 40 ip 172.16.40.254
standby 40 preempt
MOSCOWR20#sh standby br
P indicates configured to preempt.
|
Interface Grp Pri P State Active Standby Virtual IP
Et0/1.1 1 100 Standby 172.16.10.1 local 172.16.10.254
Et0/1.40 40 100 P Standby 172.16.40.1 local 172.16.40.254
Observation:
1. By default, whenever there is no priority set on HSRP, the highest IP address wins the
election and takes up “ACTIVE” role so that way MOSCOWR20 should have been the
“ACTIVE” as it has highest IP on its interface.
2. However, here in our scenario, MOSCOWR19 is elected as “ACTIVE” because
“MOSCOWR19” was configured first and it declared itself as “ACTIVE” and when you
configure “MOSCOWR20” is it going to take “Standby” role.
3. Though we have “Preempt” configured under MOSCOWR20, it is not going to become
“ACTIVE” until “Priority” is set greater than 100 (default)
4. Please note, if you configure on both router at same time the HSRP election would pick
MOSCOWR20 to be “ACTIVE” being having highest interface IP address
MOSCOWR19#show standby
Ethernet0/1.1 - Group 1
State is Standby
6 state changes, last state change 00:03:08
Virtual IP address is 172.16.10.254
Active virtual MAC address is 0000.0c07.ac01
Local virtual MAC address is 0000.0c07.ac01 (v1 default)
Hello time 3 sec, hold time 10 sec
Next hello sent in 1.296 secs
Preemption enabled
Active router is 172.16.10.2, priority 110 (expires in 9.456 sec)
Standby router is local
Priority 100 (default 100)
Group name is "hsrp-Et0/1.1-1" (default)
Ethernet0/1.40 - Group 40
State is Standby
6 state changes, last state change 00:18:41
Virtual IP address is 172.16.40.254
Active virtual MAC address is 0000.0c07.ac28
Local virtual MAC address is 0000.0c07.ac28 (v1 default)
Hello time 3 sec, hold time 10 sec
Next hello sent in 1.904 secs
Preemption disabled
Active router is 172.16.40.2, priority 110 (expires in 10.800 sec)
Standby router is local
Priority 100 (default 100)
Group name is "hsrp-Et0/1.40-40" (default)
MOSCOWR19#
MOSCOWR20#show standby
Ethernet0/1.1 - Group 1
State is Active
2 state changes, last state change 00:04:14
Virtual IP address is 172.16.10.254
Active virtual MAC address is 0000.0c07.ac01
Local virtual MAC address is 0000.0c07.ac01 (v1 default)
Hello time 3 sec, hold time 10 sec
Next hello sent in 0.704 secs
Preemption disabled
Active router is local
Standby router is 172.16.10.1, priority 100 (expires in 11.008 sec)
Priority 110 (configured 110)
Group name is "hsrp-Et0/1.1-1" (default)
Ethernet0/1.40 - Group 40
State is Active
2 state changes, last state change 00:19:32
Virtual IP address is 172.16.40.254
Active virtual MAC address is 0000.0c07.ac28
Local virtual MAC address is 0000.0c07.ac28 (v1 default)
MOSCOWR20(config)#interface e0/1.1
MOSCOWR20(config-subif)#standby 1 priority 110
MOSCOWR20(config)#interface e0/1.40
MOSCOWR20(config-subif)#standby 40 priority 110
MOSCOWR19#sh stand br
P indicates configured to preempt.
|
Interface Grp Pri P State Active Standby Virtual IP
Et0/1.1 1 100 P Standby 172.16.10.2 local 172.16.10.254
Et0/1.40 40 100 Standby 172.16.40.2 local 172.16.40.254
Observation:
1. As soon as you configured the “priority 110” on MOSCOWR20, the “preempt” triggered
up the re-election, MOSCOWR20 is “ACTIVE” for both Vlan 1 and 40
MOSCOWR19(config)#
interface e0/1.1
standby 1 priority 120
MOSCOWR19#sh stand br
P indicates configured to preempt.
|
Interface Grp Pri P State Active Standby Virtual IP
Et0/1.1 1 120 P Active local unknown 172.16.10.254
Et0/1.40 40 100 Standby 172.16.40.2 local 172.16.40.254
Observation:
Nothing to be changed for Vlan40 as Vlan40 is already “Active” on MOSCOWR20.
Pre-checks
From PC10:
PC10/ # traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 46 byte packets
1 172.16.10.1 (172.16.10.2) 7.521 ms 3.646 ms 7.701 ms →packet going via MOSCOWR19
2 192.168.32.2 (192.168.32.2) 5.977 ms 7.163 ms 6.677 ms
MOSCOWR19(config)#
interface e0/2
shut
Post-checks:
MOSCOWR19#show standby brief
Interface Grp Pri P State Active Standby Virtual IP
Et0/1.1 1 90 P Standby 172.16.10.2 local 172.16.10.254
Et0/1.40 40 100 Standby 172.16.40.2 local 172.16.40.254
Observations:
Priority decreased by “30” as per the object-tracking command
We have set decrement of “30” incase of MOSCOWR19_Eth0/2 Line-protocol going “Down”
/ # traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 46 byte packets
1 172.16.10.2 (172.16.10.2) 7.146 ms 4.018 ms 3.937 ms →now traffic goes over MOSCOWR20
2 192.168.32.2 (192.168.32.2) 7.994 ms 7.780 ms 7.122 ms
Gratuitous ARP:
The Gratuitous ARP is sent as a broadcast, as a way for a node to announce or update its IP to MAC mapping to
the entire network.
MUMBAIR2(config)#
hostname MUMBAIR2
int loopback 1
ip address 2.2.2.2 255.255.255.0
no shut
int e0/0
ip add 192.168.23.13 255.255.255.0
no shut
MUMBAIR3(config)#
hostname MUMBAIR3
int loopback 1
ip address 3.3.3.3 255.255.255.0
no shut
int e0/0
ip add 192.168.23.12 255.255.255.0
no shut
MUMBAIR4
hostname MUMBAIR4
int loopback 1
ip address 4.4.4.4 255.255.255.0
no shut
int e0/0
ip add 192.168.23.14 255.255.255.0
no shut
MUMBAIR7
hostname MUMBAIR7
int loopback 1
ip address 7.7.7.7 255.255.255.0
no shut
int e0/0
ip add 192.168.23.15 255.255.255.0
no shut
By default, any router can become DR, BDR, DROTHERS as per the configurations are done.
To make the rightful Router as DR and BDR based out of known formulae, DR = Priority+R-ID
Make use of CLI command “clear ip ospf process” → Reloads the ospf process so that re-election
happens.
You can also enable the “debug” commands to see the packet captures:
----
DEBUG OSPF
----
MUMBAIR1#debug ip ospf packet
OSPF packet debugging is on
MUMBAIR1#debug ip ospf adj
OSPF adjacency debugging is on
VERIFICATION TASKS#2
MUMBAIR1#show ip ospf neighbor
MUMBAIR1#show ip route
<!-output omitted-!>
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:04
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 3
Last flood scan time is 0 msec, maximum is 1 msec
Neighbor Count is 2, Adjacent neighbor count is 1
Adjacent with neighbor 2.2.2.2 (Backup Designated Router)
Suppress hello for 0 neighbor(s)
MUMBAIR3#
As we know:
DR/BDR = PRIORITY (DEFAULT=1) + ROUTER-ID (elected in 2-Way state)
MASTER/SLAVE = HIGHEST ROUTER-ID (elected in Extract state)
TROUBLESHOOTING OSPF:
MUMBAIR3(config)#
interface e0/0
ip ospf priority 0
Reference: https://www.browserling.com/tools/dec-to-ip
int e0/0
ip ospf authentication-key 0 cisco
Verification:
show ip ospf inter e0/0
----
MD5 METHOD
----
2 Ways:
1. Global
2. Interface
interface e0/0
ip ospf message-digest-key 1 md5 cisco
MUMBAIR2(config)#
int e0/0
ip mtu 1000
shutdown
no shutdown
MUMBAIR1#
Neighbor ID Pri State Dead Time Address Interface
2.2.2.2 1 EXCHANGE/DROTHER00:00:38 192.168.23.13 Ethernet0/0
3.3.3.3 1 FULL/DR 00:00:37 192.168.23.12 Ethernet0/0
int e0/0
ip ospf mtu-ignore
CONFIGURATION TASK #10: VERIFY OSPF MUTLICAST ADDRESS 224.0.0.6 and 224.0.0.5
MUMBAIR2(config)#
int loopback1
shutdown
Remember!!!
DROTHERS --> DR,BDR = 224.0.0.6 and
(only)DR -> BDR and DR -> DROTHER = 224.0.0.5
VERIFICATIONS TASK#10
<!-output omitted-!>
Multicast reserved groups joined: 224.0.0.251 224.0.0.5
<!-output omitted-!>
interface e0/1
ip address 10.100.100.1 255.255.255.0
no shutdown
MUMBAIR5(config)
hostname MUMBAIR5
interface e0/0
ip address 10.100.100.2 255.255.255.0
no shutdown
interface e0/1
ip address 172.16.23.1 255.255.255.252
no shutdown
interface loopback1
ip address 5.5.5.5 255.255.255.0
no shutdown
MUMBAIR6(config)
hostname MUMBAIR6
interface e0/0
ip address 10.100.100.3 255.255.255.0
no shutdown
interface e0/1
ip address 172.16.23.2 255.255.255.252
no shutdown
interface loopback1
ip add 6.6.6.6 255.255.255.0
no shut
interface e1/0
ip add 113.23.23.1 255.255.255.0
no shut
MUMBAIR2(config)
interface e0/1
ip address 33.33.33.1 255.255.255.0
no shutdown
TOKYOR7
interface e1/0
ip address 113.23.23.2 255.255.255.0
no shut
interface loopback 10
ip add 114.114.114.1 255.255.255.0
no shut
ROMER01
hostname ROMER01
interface e0/1
no shut
ip add 33.33.33.2 255.255.255.0
TOKYOR7
router eigrp 100
network 113.0.0.0
network 114.0.0.0