Diagnosis of network fault conditions

• US 7,761,746 B1
• Filed: 11/02/2007
• Issued: 07/20/2010
• Est. Priority Date: 09/19/2001
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Wilson, Reid E., Shafer, Philip A.
• Primary Examiner(s): Beausoilel; Robert
• Assistant Examiner(s): Manoskey; Joseph D
• Application Number:
  US11/934,468
• Time in Patent Office: 991 Days
• Field of Search: 714/4, 714/20, 714/30, 714/33, 714/49, 714/57, 714/48, 709/220
• US Class Current: 714/48
• CPC Class Codes: H04L 41/0266 using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/18 Delegation of network management function, e.g. customer network management [CNM]
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/0829 Packet loss

Abstract

In general, the invention facilitates diagnosing fault conditions, such as flapping, by permitting users to request information for specific components in a network device such as a router. The invention also facilitates the diagnosis of other fault conditions, including, but not limited to, excessive numbers of dropped packets, hard drive crashes, high temperature readings, and inactive interface cards. A user may obtain a targeted log containing information relating to selected fault conditions or other network device events, rather than a system log containing information relating to all network device events, some of which may not be of interest to the user. The targeted log may be parsed and analyzed with greater ease than the system log.

Claims

1. A method for processing diagnosis commands with a router comprising:

receiving, with a diagnosis module within a router, a diagnose command that specifies a selection criteria relating to a fault condition using extensible markup language tags;

sending a request for information from the diagnosis module to a management module of the router to retrieve a system log that contains information relating to a plurality of network device events for a plurality of different components of the router;

processing the system log with the diagnosis module to extract one or more of the network device events based on the selection criteria;

based on the extracted events, automatically applying one or more rules with the diagnosis module to repeatedly and automatically generate one or more subsequent requests for additional information from one or more different components of the router until a source of the fault condition can be identified to a threshold degree of certainty, wherein the diagnosis module of the router automatically formats the subsequent requests in accordance with the extensible markup language;

processing the subsequent requests with one or more of the different components of the router to produce one or more subsequent replies that include additional information relating to the fault condition;

receiving, with the diagnosis module, the one or more subsequent replies from the different components of the router; and

presenting the received information relating to the fault condition to a user.

2. The method of claim 1, wherein the selection criteria identifies at least one of the components of the network device about which information is requested by the user.

3. The method of claim 1, wherein the selection criteria specifies a level of detail of the requested information.

4. The method of claim 1, wherein the extensible markup language is XML.

5. The method of claim 1, further comprising generating the extensible markup language tags based on input received using a command line interface (CLI).

6. The method of claim 1, further comprising:

generating, with the client device, an abridged system log from the system log by extracting information from the system log based on the selection criteria; and

presenting the abridged system log to a user with the client device.

7. The method of claim 1, wherein the fault condition comprises at least one of flapping, dropped packets, component failures, inactive interface cards, or abnormal environmental conditions of the network device.

8. The method of claim 1, wherein the subsequent requests are automatically generated to include at least one user-specified criterion that identifies the component from which the information is to be received.

9. The method of claim 8, further comprising presenting the information with a level of detail determined by the at least one user-specified criterion.

10. The method of claim 1, wherein the extensible markup language tags are defined by one or more data type definition (DTD) files.

11. The method of claim 1, wherein the extensible markup language tags are defined by one or more XML Schema Language files.

12. A router comprising:

a plurality of components installed within the router;

a rule base defining a set of rules;

a management module having a system log that contains information relating to a plurality of network device events;

an interface supporting input by which a user initiates remote diagnostics with respect to a fault condition of the router, wherein the input includes at least one user-specified criterion; and

a diagnosis module that, in response to the input, automatically formats one or more commands using extensible markup language tags and sends the commands to the management module to retrieve one or more of the events from the system log,

wherein the diagnosis module is further configured to apply the rules of the rule base based on the events from the system log to repeatedly and automatically format and send one or more subsequent requests to the installed components for additional information relating to the fault condition until a source of the fault condition can be identified to a threshold degree of certainty.