• Aucun résultat trouvé

Troubleshooting Processes for Complex Enterprise Networks

N/A
N/A
Protected

Academic year: 2022

Partager "Troubleshooting Processes for Complex Enterprise Networks"

Copied!
22
0
0

Texte intégral

(1)

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public Course v6 Chapter #

1

Chapter 2:

Troubleshooting

Processes for Complex Enterprise Networks

CCNP TSHOOT: Maintaining and Troubleshooting IP Networks

(2)

Chapter 2 Objectives

 Identify troubleshooting principles and evaluate troubleshooting methodologies.

 Plan and implement troubleshooting procedures as part of a structured troubleshooting methodology.

 Plan and implement troubleshooting and network

maintenance procedures to effectively support each other.

(3)

Chapter #

3

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public

Troubleshooting Methodologies

Flow chart of a structured troubleshooting approach

(4)

Troubleshooting Methodologies

Shoot from the hip vs. structured troubleshooting method

(5)

Chapter #

5

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public

Troubleshooting Approaches

Top-down

Bottom-up

Divide and conquer

Follow-the-path

Spot the differences

Move the problem

(6)

Troubleshooting Approaches - Spot the Differences Example

 Branch1 is in good working order

 Branch2 has connectivity problems

Branch2# show ip route <output omitted>

10.0.0.0/24 is subnetted, 1 subnets

C 10.132.126.0 is directly connected, FastEthernet4 C 192.168.37.0/24 is directly connected, BVI1

Branch1# show ip route <output omitted>

10.0.0.0/24 is subnetted, 1 subnets

C 10.132.125.0 is directly connected, FastEthernet4 C 192.168.36.0/24 is directly connected, BVI1

S* 0.0.0.0/0 [254/0] via 10.132.125.1

(7)

Chapter #

7

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public

Troubleshooting Approaches - Move the Problem Example

Laptop B is having network problems. Cable or port swapping can help

isolate the problem.

(8)

Implementing Troubleshooting Procedures

 Defining the problem

 Gathering information

 Analyzing the information

 Eliminating possible problem causes

 Formulating a hypothesis about the likely cause of the problem

 Testing that hypothesis

 Solving the problem

(9)

Chapter #

9

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public

The Troubleshooting Process – Verify and

Define the Problem

(10)

The Troubleshooting Process – Gather

Information

(11)

Chapter #

11

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public

The Troubleshooting Process – Analyze

(12)

The Troubleshooting Process – Eliminate

(13)

Chapter #

13

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public

The Troubleshooting Process – Propose

Hypothesis

(14)

The Troubleshooting Process – Test

Hypothesis

(15)

Chapter #

15

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public

The Troubleshooting Process – Solve Problem

(16)

The Troubleshooting and Network Maintenance

(17)

Chapter #

17

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public

The Troubleshooting and Network Maintenance – Cont.

 Accurate documentation is critical to effective troubleshooting.

 A network baseline is essential and can include:

• Interface load for critical network links (IOS)

• CPU load and memory usage of routers and switches (SNMP)

• Accounting of network traffic (NBAR, NetFlow)

• Measurement of network performance characteristics (IP SLA)

(18)

The Troubleshooting and Network

Maintenance – Cont.

(19)

Chapter #

19

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public

Communication and Change Control

Communication plays a role in all phases of structured troubleshooting.

(20)

Chapter 2 Summary

 The fundamental elements of a troubleshooting process:

• Gathering of information and symptoms

• Analyzing information

• Eliminating possible causes

• Formulating a hypothesis

• Testing the hypothesis

 Some commonly used troubleshooting approaches are:

• Top-down

• Bottom-up

• Divide-and-conquer

• Follow-the-path

• Spot the differences

• Move the problem

(21)

Chapter #

21

© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public

Chapter 2 Summary – Cont.

 Useful data to gather and create a network baseline are:

• Basic performance statistics using show commands

• Accounting of network traffic using RMON, NBAR, or NetFlow statistics

• Measurements of network performance characteristics using the IP SLA feature in IOS

 Communication is an essential part of the troubleshooting process and happens in all stages of troubleshooting:

• Report the problem

• Gather information

• Analyze and eliminate possible causes

• Propose and test a hypothesis

• Solve the problem

 Change control is one of the most fundamental processes in

network maintenance.

(22)

Références

Documents relatifs

Calls are sent to Cisco Unity ports that set for MWIs but not set to Answer Calls D?. 6.3 kbps

• The default XenServer block device-based storage inserts a Logical Volume manager on a disk.. VDIs are represented as volumes within the

Since DHCP client messages use the destination IP address of 255.255.255.255 (all Nets Broadcast), DHCP clients will not be able to send requests to a DHCP server on a

Loosen but do not remove· the two screws indicated in the diagram. Remove the screws indicated. Disconnect the connector from the board. Remove the other connector from

No serial console No serial console Connect local console Connect local console Any errors on the console. Any errors on

Administrative private-vlan trunk Native VLAN tagging: enabled Administrative private-vlan trunk encapsulation: dot1q Administrative private-vlan trunk normal VLANs: none

• For back-to-back Serial links, DCE end must perform link clocking. – If link is up/down, clocking

– Discover EIGRP Neighbors – Exchange Topology Information – Choose Best Path. – Neighbor and Topology