Chapter 10:

Troubleshooting Case
Study:
RADULKO Transport

CCNP TSHOOT: Maintaining and Troubleshooting IP Networks

TSHOOT v7 Chapter 10
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 1
 Chapter 10 Objectives
 RADULKO Transport Trouble Ticket 1
• Troubleshooting Spanning Tree Protocol
• Troubleshooting Policy-Based Routing
• Troubleshooting CDP and LLDP
 RADULKO Transport Trouble Ticket 2
• Troubleshooting VTP
• Troubleshooting EIGRP for IPv6
• Troubleshooting MP-BGP
 RADULKO Transport Trouble Ticket 3
• Troubleshooting the OSPFv3 Address Families Feature

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 2
 Troubleshooting Case Study:
RADULKO Transport

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 3
 RADULKO Transport Scenario

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 4
 RADULKO Transport
Ticket 1

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 5
 Troubleshooting Spanning Tree Protocol
 The Spanning Tree Protocol (STP) is a Layer 2 protocol that
runs on bridges and LAN switches, and it operates based
on the IEEE 802.1D standard and specifications.

 The main purpose of STP is to ensure that the network is

loop free but yet all devices have a communication path.

 Spanning tree also monitors the network for failures and

changes the topology to maintain connectivity of all devices
in a loop-free manner.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 6
 Troubleshooting Spanning Tree Protocol
 The current spanning-tree modes supported on most Cisco
LAN switches include the following:
• PVST+
• This spanning-tree mode is based on the IEEE 802.1D standard and Cisco
proprietary extensions. It is the default spanning-tree mode (in most switches) and is
used on all Ethernet port-based VLANs. There is a separate instance of STP for each
VLAN configured.
• PVRST+ or Rapid PVST+
• This spanning-tree mode is based on Rapid Spanning Tree Protocol (RSTP), which
is specified in the IEEE 802.1w standard. RSTP is based on the assumption that
switch-to-switch connections are point-to-point full-duplex connections; therefore,
interface role and state decisions are based on a proposal/ challenge/accept
negotiation method rather than on timers and timeouts. This gives RSTP a much
faster convergence time (subsecond).
• MSTP
• This spanning-tree mode is based on the IEEE 802.1s standard. The current Multiple
Spanning Tree Protocol (MSTP) is Rapid, but it also allows you to map multiple
VLANs to the same spanning-tree instance, thus reducing the number of active STP
instances.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 7
 Troubleshooting Spanning Tree Protocol
 Misconfiguration, hardware errors, or unexpected topology
changes can result in the following STP-related issues:
• Forwarding loops
• Suboptimal traffic flow
• Excessive flooding due to the high rate of topology changes
• Convergence time-related issues
 Useful spanning-tree troubleshooting commands include the
following:
• show spanning-tree: This command enables you to check the status of
the spanning- tree elements and parameters’ values; it also displays the
spanning-tree status for all VLANs or MST instances. To check the status
of a specific VLAN or MST instance, use the show spanning-tree vlan
vlan-id or the show spanning-tree mst instance-id command.
• show spanning-tree summary: Use this command to verify all the
features that are enabled for STP; this command also displays the
number of blocked, listening, learning, and forwarding interfaces.
• show spanning-tree mst configuration: Use this command to display
which VLANs are configured for specific MST instances.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 8
 Troubleshooting Spanning Tree Protocol
Troubleshooting STP helps to isolate and possibly find the cause
for a particular failure; however, implementation of the following
stability mechanisms enables us to secure the network against
forwarding loops:

PortFast
• This feature causes a switch port to enter the spanning-tree Forwarding
state immediately, bypassing the Listening and Learning states.
• You can enable PortFast globally with the command spanning-tree
portfast default or per interface with the interface configuration mode
command spanning-tree portfast .
• Enabling PortFast globally will enable PortFast on all nontrunking ports.
• To verify interface PortFast status, use the show spanning-tree
interface interface-id portfast command.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 9
 Troubleshooting Spanning Tree Protocol
 PortFast BPDU Guard
• This feature prevents loops by moving a nontrunking port into an Err-
Disabled state when a BPDU is received on that port.
• You can enable BPDU Guard globally with the spanning-tree
portfast bpduguard default command. This will enable BPDU Guard
on all PortFast ports.
• You can enable BPDU Guard on a single interface with the command
spanning-tree bpduguard enable without having to enable the
PortFast feature.
• To recover an interface from the Err-Disabled state, you can use the
shutdown and no shutdown command, or use the command
errdisable recovery cause bpduguard to enable a switch to
automatically try to recover err-disabled interfaces.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 10
 Troubleshooting Spanning Tree Protocol
 BPDUFilter
• This feature can be enabled globally or per interface.
• Depending on the configuration method, there are differences in its
operation.
• When BPDUFilter is enabled globally using the spanning-tree portfast
bpdufilter default , it will enable BPDUFilter on PortFast interfaces. This
command prevents interfaces from sending or receiving BPDUs. The
interfaces still send a few BPDUs when a linkcomes up before the switch
begins to filter outbound BPDUs. If BPDU is received on a PortFast-
enabled interface, the interface loses its PortFast operational status, and
BPDUFilter is disabled.
• You can also enable BPDUFilter per interface by using the spanning-tree
bpdufilter enable command without also enabling the PortFast feature.
This command will prevent the interface from sending or receiving
BPDUs, which is functionally the same as disabling STP and can result in
spanning-tree loops.
• Note that BPDUFilter is a very specific tool, tailored for certain occasions,
such as when you need to merge two Layer 2 domains using different
types of STP, and you need to filter both protocols on the connecting link.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 11
 Troubleshooting Spanning Tree Protocol
 Loop Guard
• You can use Loop Guard to prevent alternate or root ports from becoming
designated ports because of a failure that leads to a unidirectional link.
• You can enable this feature by using the spanning-tree loopguard
default global configuration mode command.
 Root Guard
• In switched networks, any switch with the lowest bridge ID becomes the
root bridge.
• To prevent other switches connected to specific ports on your switch from
becoming the root bridge, you can use the Root Guard feature.
• When Root Guard is enabled on a port and spanning-tree calculation
causes an interface to be selected as root port, the Root Guard places
the interface in the Root Inconsistent state, which is equivalent to the port
being blocked.
• When BPDUs with higher bridge IDs are received again, the port recovers
from the Root Inconsistent state. You can enable Root Guard on an
interface by using the spanning-tree guard root command.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 12
 Troubleshooting Policy-Based Routing
The following is a short checklist helpful for troubleshooting
PBR cases:
• Check path control route-map statement: When a packet matches
a deny route map statement, it is not policy routed; it is routed
normally. When a packet matches a permit route-map statement, the
statement’s set commands are applied.
• Check traffic-matching configuration: When access control lists
(ACLs) or prefix lists are used to define policy-routed traffic, verify
ACLs to understand what traffic is policy routed.
• Check actions for the matched traffic: Understand the set
statements applied by the PBR route map.
• Check how the route map is applied: Policy routing works only on
inbound packets; therefore, it must be applied on the interface
receiving the traffic to be policy routed

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 13
 Troubleshooting CDP and LLDP
To troubleshoot CDP or LLDP neighbor discovery problems,
check the following items:
• Check whether all devices are Cisco devices or whether there are
other vendor devices in the network as well.
• If the network is multivendor, use LLDP.
• Check whether CDP/LLDP is enabled globally, and check to make
sure that it has not been disabled on the required interfaces.
• The [no] cdp run command is used to enable/disable CDP globally.
• The [no] cdp enable command is used to enable/ disable CDP on a
particular interface.
• The same commands are available and applicable for LLDP.
• Check the LLDP/CDP timer values. If you configure the CDP/LLDP
hold time to be less than the Update timer, your device will lose its
CDP/LLDP adjacencies repeatedly.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 14
 Troubleshooting CDP and LLDP
The following commands are useful for troubleshooting CDP- and LLDP-
related cases:
• show cdp, show lldp: Display global protocol information, including timer and
hold-time information and protocol version
• show cdp entry, show lldp entry: Display information about a specific
neighboring device, including device ID, protocols and addresses, platform,
interface, hold time, and version
• show cdp interface, show lldp interface: Display information about the
interfaces on which the protocol is enabled, including status information and
information about timer and hold time
• show cdp neighbors, show lldp neighbors: Display detailed information about
neighboring devices, including the type of the device, its name, and MAC address
or serial number, local interconnecting interface, remaining hold-time interval,
product number, and neighbor’s interconnecting interface and port number
• show cdp neighbors detail, show lldp neighbors detail: Display additional
detail about neighbors, including network addresses, enabled protocols, and
software version
• show cdp traffic, show lldp traffic: Display information about traffic between
devices, such as the total number of packets sent and received and
advertisements per version
• debug cdp, debug lldp: Display the protocol messages exchanged in real time

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 15
RADULKO Transport
Ticket 2

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 16
 Troubleshooting VTP
 The best practice is to either put all switches in transparent mode or use VTP
with caution.
 Being cautious with VTP means that you should have no more than two
switches in server mode, should have long and uncommon domain names, and
should use long and uncommon VTP passwords.
 Also, before connecting a switch to your network, make sure that the switch is in
transparent mode.
 It is important to know that VTP is propagated over trunk interfaces only and that
VTP messages are not encrypted.
 Keep in mind that a switch with no domain name configured will adopt the
domain name of the first VTP advertisement it receives.
 VTP Version 3 adds a new VTP mode called off. A switch in off mode acts
similarly to a switch in transparent mode, but it does not forward VTP messages
through.
 When troubleshooting VTP, consider VTP version mismatch, authentication
mismatch, and nonoperational trunk connection as possible culprits.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 17
 Troubleshooting EIGRP for IPv6
 Configuring Enhanced Interior Gateway Routing Protocol
(EIGRP) for IPv6 is similar to configuring EIGRP for IPv4.
 The main difference is that EIGRP is enabled on the
interface for IPv6 with the command ipv6 eigrp as-
number , as network statement is deprecated.

The following are a few commands you can use for

troubleshooting EIGRP:
• show ipv6 protocols
• The output of this command shows information about the locally active IPv6
routing protocols. The EIGRP section of the output displays metric weights
(K parameters), router ID, EIGRP interfaces, redistribution information, and
other information about EIGRP.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 18
 Troubleshooting EIGRP for IPv6
• show ipv6 eigrp neighbors
• This command reveals the list of a local router’s EIGRP neighbors. All
EIGRP neighbors are listed, with some useful information such as interface
used to connect the neighbor, timers, and so on.
• show ipv6 eigrp interfaces
• This command displays detailed information about interfaces where EIGRP
has been activated.
• show ipv6 eigrp topology
• This command displays the EIGRP topology table. You can see all routing
updates received by the router, with administrative distance (AD) and
feasible distance (FD) information, next hop, and so on.
• debug ipv6 eigrp
• This debug enables you to observe the EIGRP events observed/processed
by your local router in real time.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 19
 Troubleshooting MP-BGP
 Multiprotocol BGP extensions for IPv6 support the same features and functionality as
IPv4 BGP.
 IPv6 enhancements to multiprotocol BGP include support for the IPv6 address family
 Use address-family ipv6 to enter the unicast IPv6 address family. By default,
neighbors that are defined using the neighbor remote-as command in router
configuration mode exchange only IPv4 unicast address prefixes.
 To exchange IPv6 prefixes, neighbors must be activated using the neighbor
activate command in address family configuration mode for IPv6 prefixes.
 Configuring IPv6 multiprotocol BGP between two IPv6 routers (peers) using link-
local addresses requires that the outgoing interface toward the neighbor be identified
by using the update-source command.
 You also need a route map (applied to neighbor outbound) to set the next-hop
attribute to a global IPv6 unicast address.
 To inject a network into an IPv6 BGP database, you must define the network using
the network command in address family configuration mode.
 By default, route maps that are applied in router configuration mode using the
neighbor route-map command are applied to only IPv4 unicast address prefixes.
 Route maps for IPv6 address family must be applied in IPv6 address family
configuration mode using the neighbor route-map command.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 20
 Troubleshooting MP-BGP

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 21
 Troubleshooting MP-BGP
Useful commands to troubleshoot IPv6 BGP include the following:
• clear bgp ipv6 unicast *
• Use this command to reset all IPv6 BGP sessions on the router. You can use
several other keywords, such as IP address of the neighbor, autonomous
system number, and so on, instead of an asterisk to make some more specific
clearing.
• show bgp ipv6 unicast
• Use this command to display the IPv6 BGP table. You can see IPv6 prefixes
with next-hop address, local preference, metric, autonomous system path, and
other attributes.
• show bgp ipv6 unicast summary
• Use this command to verify all IPv6 BGP peers and related information such as
status of the peering, how many prefixes have been received, and so forth.
• debug bgp ipv6 unicast updates
• This command will enable debugging for all IPv6 BGP update packets received
and sent by the router.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 22
 RADULKO Transport
Ticket 3

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 23
 Troubleshooting the OSPFv3 Address Families
Feature
 OSPFv3 is a link-state routing protocol originally developed for IPv6 routing only.
 OSPFv2 can only handle IPv4 unicast routing.
 With the introduction of address families within OSPFv3, this protocol now
supports routing for the IPv4 unicast address family as well.
 The “address family” feature maps an address family to a separate OSPFv3
instance, using the Instance ID field in the packet header.
 Each OSPFv3 instance maintains its own adjacencies, link-state database, and
shortest path computation.
 OSPFv3 runs on IPv6 and it uses IPv6 link-local addresses as the source of
Hello packets and next-hop calculations.
 To use the IPv4 unicast address family in OSPFv3, you must enable IPv6 on a
link, but the link may not be participating in IPv6 unicast routing.
 OSPFv3 makes use of IPsec Authentication Header (AH) and therefore has a
broader range of supported authentication algorithms (message digest 5 [MD5]
authentication and Secure Hash [SHA]) than OSPFv2.
 OSPFv3 can also use IPsec Encapsulating Security Payload (ESP) for
encryption purposes.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 24
 OSPFv3 Address Families Example

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 25
 Troubleshooting the OSPFv3 Address Families
Feature
The following commands are useful for troubleshooting OSPFv3:
show ip route ospfv3: Use this command to list the OSPFv3 entries in the IPv4 routing
table.
show ipv6 route ospf: Use this command to list the OSPFv3 entries in the IPv6 routing
table.
show running-config | section router ospfv3: Use this command to see the OSPFv3
configuration section of the running configuration.
show running-config | section interface: Use this command to see the interface
configuration section of the running configuration.
show ospfv3: Use this command to display general information about the OSPFv3 routing
process.
show ospfv3 interface: Use this command to gather detailed information about interfaces
where OSPFv3 has been activated.
show ospfv3 neighbor: Use this command to gather information about OSPFv3 neighbors.
debug ospfv3 events: Use this debug to gather live information about OSPFv3 events.

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 26
 Chapter 10 Summary
 Troubleshooting Spanning Tree Protocol
 Troubleshooting Policy-Based Routing
 Troubleshooting CDP and LLDP
 Troubleshooting VTP
 Troubleshooting EIGRP for IPv6
 Troubleshooting MP-BGP
 Troubleshooting the OSPFv3 Address Families Feature

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 27
 Chapter 10 Labs
 10-1 Troubleshooting Complex Environments

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 28
Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 29
 Acknowledgment
• Some of the texts and images are from Troubleshooting and Maintaining Cisco
IP Networks (TSHOOT) Foundation Learning Guide by Amir Ranjbar
(158720455X)
• Copyright © 2015 – 2016 Cisco Systems, Inc.
• Special Thanks to Bruno Silva

Chapter 1
© 2007 – 2016, Cisco Systems, Inc. All rights reserved. Cisco Public 30