Scribd
Upload
248 views4 pages

CCIE Troubleshooting Tips

To troubleshoot network issues, follow these steps: 1. Check basic connectivity using Ping and Traceroute. 2. Use show commands like show ip interface brief, show run interface, show run | include, and show run | section to check interface configurations, routing protocols, filtering rules, and other configurations. 3. For specific issues, check additional configurations like MPLS, IPv6, PPP, multicast, and MSDP settings as outlined in the document.

Uploaded by

hem777
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
248 views4 pages

CCIE Troubleshooting Tips

To troubleshoot network issues, follow these steps: 1. Check basic connectivity using Ping and Traceroute. 2. Use show commands like show ip interface brief, show run interface, show run | include, and show run | section to check interface configurations, routing protocols, filtering rules, and other configurations. 3. For specific issues, check additional configurations like MPLS, IPv6, PPP, multicast, and MSDP settings as outlined in the document.

Uploaded by

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

CCIE Troubleshooting Tips

To troubleshoot, always first check by Pinging and


Traceroute/Telnet. AFTER this basic approach follow these steps
(step 1 to 6 in all cases, then depending on the question)

1.) show ip interface brief

! To check which interfaces are configured with


ip addresses and whether they are up/down

2.) sh run interface Serial1/1 (example)


interface

3.) sh run | section router

! Then to check detail configuration of

! To check all routing protocols

4.) sh run | include list|permit|deny|map|match|set

5.) sh run | include ip route

! to check all Filtering.


VERY useful command.

! To check any static routes

6) In IGPs check :
A.) NEIGHBORSHIP
B.) AUTHENTICATION
C.) NETWORK COMMANDS
D.) Any special configuration which may be creating problem.

7.) IF policy-map is configured (which you will find out by Command # 4) then run the
following command to check :
"show run | section policy-map"
"sh run | include interface|service"

8.) For MPLS check :


A.) show mpls ldp neighbor

B.) show mpls forwarding-table

C.) show ip vrf

D.) show run | sec ip vrf

E.) show ip bgp vpnv4 all

F.) sh ip route vrf <name>

! to find out what is it doing and where is


it applied.

ContC
-> Check for any ACL stopping router in creating LABELS for prefixes.
-> Check for RD values and check whether right RTs are imported and exported or
not.
-> Check for PE-CE IGP neighborship
-> Check for "PE-CE IGP" to BGP and BGP to "PE-CE IGP" redistribution
-> Check for PE to PE BGP vpnv4 neighborship.
-> in OSPF over MPLS, check for sham-link and any discontageous Areas.

9.) in IPv6 question check ip addressing on interfaces and


"ipv6 unicast-routing"

command.

10.) ip IPv6 IGPs, route-ids are "IPv4 ADDRESSES", which MUST BE UNIQUE!!, check
that on all devices.

11.) show run | include interface|ipv6

! To check all ipv6 configuration

12.) in PPP question check local database and password. Use :

sh run | include username|ppp|aaa|interface

13.) in MULTICAST question use


"sh run | include multicast|pim|rp|interface|igmp" command to check proper
configuration

14.) in MSDP question use the above command AND "sh run | include msdp" to check
the configuration.

You might also like