Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Isolating a Broken Network Connection

By applying the standard four-step process illustrated in Figure 1, you can isolate a failed node in the network. Note that the functionality described in this section is not supported in versions 15.1X49, 15.1X49-D30, or 15.1X49-D40.

Figure 1: Process for Diagnosing Problems in Your NetworkProcess for Diagnosing Problems in Your Network

Before you embark on the four-step process, however, it is important that you are prepared for the inevitable problems that occur on all networks. While you might find a solution to a problem by simply trying a variety of actions, you can reach an appropriate solution more quickly if you are systematic in your approach to the maintenance and monitoring of your network. To prepare for problems on your network, understand how the network functions under normal conditions, have records of baseline network activity, and carefully observe the behavior of your network during a problem situation.

Figure 2 shows the network topology used in this topic to illustrate the process of diagnosing problems in a network.

Figure 2: Network with a ProblemNetwork with a Problem

The network in Figure 2 consists of two autonomous systems (ASs). AS 65001 includes two routers, and AS 65002 includes three routers. The border router (R1) in AS 65001 announces aggregated prefixes 100.100/24 to the AS 65002 network. The problem in this network is that R6 does not have access to R5 because of a loop between R2 and R6.

To isolate a failed connection in your network, follow the steps in these topics: