EIGRP Troubleshooting: Cisco CCNP ROUTE Training

Cisco CCNP ROUTE Training
Instructor: Joe Rinehart, CCIE #14256

EIGRP Troubleshooting
In This Lesson:
Troubleshooting Model
Common Issues and Resolution Steps
Relevant Debug and Show Commands
Dealing with Cisco TAC
1. Define the Problem
2. Gather the Facts
3. Document the Facts
4. Consider the Possibilities
5. Create an Action Plan
6. Implement the Action Plan
7. Repeat Until Resolution
8. Document the Solution
Problem Resolution Methodology
1. Neighbor Relationship Problems
2. Routes Missing from Table
3. Address Summarization Problems
Neighbor Relationship Problems
Neighbor Not Establishing Relationship
Possible Cause: Mismatched K Values
Execute the show ip protocols
command on the affected devices
Examine the output under the
eigrp metric weight line and
note the values
Use the metric weights
command in router configuration
mode to change values if required
Possible Cause: Mismatched ASN
Examine the configuration of
affected devices for the ASN
Possible Cause: Mismatched ASN
Alternatively execute the show ip
protocols to find ASN
Delete and restart the EIGRP
process using the correct ASN
Possible Cause: Misconfigured
neighbor authentication
Execute the show key chain
command to verify key string and
accept/send lifetime settings
Reconfigure correct string if
needed
Possible Cause: Misconfigured
neighbor authentication
Execute the show running-
config command to verify that
both the ip authentication key-
chain and ip authentication
mode command are correct and
in place
Add either or both statements
with correct syntax if missing
Possible Cause: Primary subnets not
matching
Execute the show ip interface
<slot/port> command to verify
the primary IP address configured
on the interfaces of affected
devices
Change IP addressing if primary
subnets are not on the same
network/subnet
Possible Cause: Multicast traffic being
blocked between devices
Execute the show ip interface
and show access-list command
to discover if any filtering is being
done on the affected interfaces
Add statements permitting
224.0.0.10 is necessary
Execute show interface to
determine if interface is up/up
Replace cable or replace
interface/device to resolve
Possible Cause: Network statement
misconfigured under EIGRP
Execute the show ip eigrp
interface to discover if EIGRP has
correctly identified the interfaces
Execute the show running-
config to verify that the network
statements are correctly
configured in EIGRP
Delete and recreate the network
statements with the correct
subnet and mask combinations
Routes Missing from Table
Possible Cause: Split Horizon is In Effect
on a Multipoint Interface
Execute the show running-config
to discover if the no split-horizon
eigrp <ASN> statement is
configured
Enter interface configuration mode on
the multipoint/natural interface and
amend the configuration
If the statement is present, verify that
the ASN is correct and amend if there
is a discrepancy
Possible Cause: Automatic network
summarization is in effect
to discover if the no auto-summary
statement is configured under EIGRP
Use the show ip protocols command
and look for the statement
Automatic network
summarization is/not in effect
If automatic network summarization
is in effect, execute the no auto-
summary command in eigrp router
configuration mode
Possible Cause: Network statement
misconfigured under EIGRP
Execute the show ip eigrp
interface to discover if EIGRP has
correctly identified the interfaces
to verify that the network
statements are correctly configured in
EIGRP
Delete and recreate the network
statements with the correct subnet
and mask combinations
Address Summarization Problems
Possible Cause: No Subnets in the
Routing Table in the Range of the
Summary Address
Execute the show ip route
command to see if any networks
within the range currently exist
to verify that the ip summary-
address eigrp statement is correctly
on the interface (network, ASN, etc.)
Delete and recreate the summary
statement with corrections and/or find
the cause of the missing route
1. EIGRP Show Commands
2. EIGRP Debug Commands
EIGRP Show Commands
show ip protocols
Data displayed by the command
EIGRP status and ASN
Configured K-Values
Protocols being redistributed
Networks being advertised
Neighbors/gateways
Helpful in troubleshooting:
Neighbor relationships
Missing routes
Summarization issues
Filtering problems
EIGRP Show Commands
show ip route eigrp
EIGRP routes from neighbors
Feasible distance metric
Route source/interface
Missing routes
Summarization issues
Filtering problems
General troubleshooting
EIGRP Show Commands
show ip eigrp interfaces
Interfaces participating in EIGRP
Number of neighbors on an
interface
EIGRP ASN in use
Local configuration issues
Routing problems
EIGRP Show Commands
show ip eigrp neighbors
Active fully adjacent neighbors
IP address/interface of neighbors
Holdtime of neighbors
EIGRP ASN in use
Local configuration issues
EIGRP Show Commands
show ip eigrp topology
Complete listing of the EIGRP
topology database
Status of routes (active/passive)
Feasible/Reported distance metric
Successors/Feasible Successor
Missing routes
Stuck-in-Active problems
Filtering problems
General troubleshooting
EIGRP Debug Commands
debug eigrp packet <type>
Types supported
Hello
Update
Query/Reply
ACK
Stub
Routing update issues
Stub router problems
EIGRP Debug Commands
debug ip eigrp
Information provided
EIGRP routing events
Routing table events
Update processing
Routing update issues
1. Understanding TAC
2. Severity Levels
3. Opening a TAC Case
4. Information to Have Ready:
5. Working the Case Actively
6. TAC Case Etiquette
Understanding TAC
24x7x365 coverage for all Cisco product
lines
Located worldwide (primary sites):
San Jose, CA
Sydney, Australia
Raleigh, NC
Brussels, Belgium
Attachment to open cases
Entitlement tied to valid SMARTNet
service contract
Severity Levels
Severity 1 (S1): Your network or
environment is down or there is a
critical impact to your business
operations. You and Cisco will commit all
necessary resources around the clock to
resolve the situation (use care when
designating a situation as an S1, use
escalation if resolution for S2/S3 is not
proceeding as you need it to)
Severity Levels
Severity 2 (S2): Operation of an
existing network or environment is
severely degraded, or significant aspects
of your business operation are negatively
affected by inadequate performance of
Cisco products. You and Cisco will commit
fulltime resources during normal business
hours to resolve the situation
Severity Levels
Severity 3 (S3): Operational
performance of your network or
environment is impaired while most
business operations remain functional.
You and Cisco are willing to commit
resources during normal business hours
to restore service to satisfactory levels
Severity 4 (S4): You require
information or assistance with Cisco
product capabilities, installation, or
configuration. There is little or no effect
on your business operations
Opening a TAC Case
By E-mail: tac@cisco.com
On the web:
http://www.cisco.com/techsupport/servic
erequest
By Phone:
Asia Pacific +61 2 8446 7411
Australia 1 800 805 227
New Zealand 0800 44 6237
Europe +32 2 704 5555
US/Canada 1 800 553 2447
Information to Have Ready:
Must-Have Information:
Cisco Service Contract #
Product/Chassis Serial #
Product Model #/HW config
Physical location of the product
Severity Level of the Issue
Very Helpful Information:
Accurate description of the issue (and
succinct case title)
History of the problem
Network topology and explanation
Information to Have Ready:
Very Helpful Information:
Output from show tech command (if
applicable) and all other relevant
output
Software versions and types of
equipment
Relevant syslog/TACACS+ logs before
the issue occurred
Working the Case Actively:
Send updates & information as requested
Maintain regular communication
Close the case when the issue is resolved
TAC Case Etiquette:
Treat the support engineer with courtesy
and respect
Realize that TAC is not a substitute for
on-site staff
Create separate TAC cases for each issue
unless clearly linked
Realize that you have control over the
severity level
Escalate to the TAC duty manager is you
need to move the case along
Pass along compliments to the support
engineers supervisor
Key Terms You Should Know
Cisco TAC Cisco Technical Assistance Center, the 24x7x365
help desk support system for customers using Cisco products
S1 Severity TAC case severity in which the production
network is down and in a critical state needing immediate
resolution
network is severely degraded with regards to performance
network is impaired but relatively functional
network is fully operational but assistance with information,
configuration/installation guidance is required
What We Covered
Troubleshooting model
Common issues and resolution steps
Relevant debug and show commands

EIGRP Troubleshooting: Cisco CCNP ROUTE Training

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

EIGRP Troubleshooting: Cisco CCNP ROUTE Training

Transféré par

Droits d'auteur :

Formats disponibles

Cisco CCNP ROUTE Training

Instructor: Joe Rinehart, CCIE #14256

Vous aimerez peut-être aussi