Network commentator

• US 5,383,178 A
• Filed: 03/26/1992
• Issued: 01/17/1995
• Est. Priority Date: 03/26/1992
• Status: Expired due to Term

• Current Assignee: Agilent Technologies, Inc.
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Unverrich, Rod
• Primary Examiner(s): Olms, Douglas W.
• Assistant Examiner(s): VU, HUY DUY
• Application Number:
  US07/857,894
• Time in Patent Office: 1,027 Days
• Field of Search: 370/13, 370/14, 370/15, 370/16, 370/16.1, 370/17, 370/85.4, 370/85.3, 370/85.15, 370/85.1, 371/15.1, 371/20.1, 371/20.4, 371/23, 371/24, 371/29.1, 371/48, 371/55, 371/61, 371/62, 371/20.6, 340/825.05, 340/825.06, 340/825.5, 340/825.51
• US Class Current: 370/245
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route

Abstract

Disclosed is a system that monitors a local area network by receiving all messages transmitted over the local area network, and analyzing selected sequences of messages to determine if certain, architecturally defined, processes are properly completed. If a network station starts one of these processes, and the process does not complete normally, the system analyzes the messages involved in the process to determine the network stations that participated in the process, and the phase or phases of the process that were completed. This allows the system to provide information to a user of the system that identifies a possible cause for the process not completing, and a possible network station or stations likely to be at fault.

Claims

1. A test device for identifying one of a plurality of error types in a token-ring local area network, wherein said token-ring local area network has at least one network computer station attached thereto, and further wherein said at least one network computer station may send a plurality of messages, each message being one of several types of messages, through said token-ring local area network, said test device comprising:

interface means for connecting said test device to said token-ring local area network and for receiving a plurality of messages being transmitted over said local area network by said at least one network computer station;

a first timer means connected to said interface means for timing a duration between received messages;

means connected to said interface means and said first timer means for analyzing each of said plurality of messages, and for starting said first timer means when a first duplicate address type of message is received; and

means connected to said interface means and said first timer means for displaying a duplicate address test failure error message when a time value within said first timer means exceeds a first predetermined duration before said interface means receives a second duplicate address type of message.

7. The test device of claim 1 further comprising:

a bad-dat-message counter means connected to said means for analyzing, said bad-dat-message counter means for counting a number of duplicate address type of messages received that indicate a duplicate address; and

means connected to said bad-dat-message counter means and said interface means for displaying an insertion failure error message when said bad-dat-message counter means exceeds a first predetermined value.

8. The test device of claim 7 further comprising:

a second timer means connected to said interface means;

a good-dat-message counter means connected to said interface means, said good-dat-message counter means for counting a number of duplicate address type of messages received that do not indicate a duplicate address;

means connected to said second timer means, said good-dat-message counter means, and said interface means, for analyzing each of said plurality of messages, and for starting said second timer means when said good-dat-message counter means exceeds a second predetermined value; and

means connected to said interface means and said second timer means for displaying a neighbor notification failed type of error message when said second timer means exceeds a second predetermined duration before a message is received indicating a nearest upstream active neighbor has changed.

9. The test device of claim 8 further comprising:

a third timer means connected to said interface;

a request-init counter means connected to said interface;

means connected to said interface means and said third timer means for analyzing each of said plurality of messages and for starting said third timer after said interface means receives a message indicating a nearest active upstream neighbor has changed and also after said interface means receives a request init message, and for incrementing said request-init counter means each time a request init message is received;

means connected to said third timer means and said interface means for displaying a request init failed type of error message when said third timer means exceeds a third predetermined amount of time before said request-init counter means exceeds a third predetermined number.

10. The test device of claim 9 further comprising:

means connected to said interface means for displaying a station inserted message after said request-init counter means exceeds said third predetermined number.

2. A test device for monitoring a token-ring local area network, wherein said token-ring local area network has at least one network computer station attached thereto, and further wherein said at least one network computer station may send a plurality of frames, each frame being one of several types of frames, through said token-ring local area network, said test device comprising:

an interface connecting said test device and said token-ring local area network, wherein said interface receives a plurality of frames being transmitted over said local area network by said at least one network computer station;

a first timer connected to said interface, wherein said first timer measures an amount of time between frames received by said interface;

an analyzer connected to said interface and said first timer, wherein said analyzer examines each of said plurality of frames and starts said first timer when a first duplicate address type of frame is received by said interface;

a display system connected to said interface and said analyzer, wherein said display system displays a duplicate address test failure error message when said first timer exceeds a first predetermined amount of time before said interface receives a second duplicate address type of frame.

3. The test device of claim 2 further comprising:

a bad-dat-frame counter connected to said analyzer, wherein said bad-dat-frame counter counts a number of duplicate address type of frames received that indicate a duplicate address; and

a second display system connected to said bad-dat-frame counter and said interface, wherein said display system displays an insertion failure error message when said bad-dat-frame counter exceeds a first predetermined value.

4. The test device of claim 3 further comprising:

a second timer connected to said interface;

a good-dat-frame counter connected to said interface means, wherein said good-dat-frame counter counts a number of duplicate address type of frames received that do not indicate a duplicate address;

a second analyzer connected to said second timer, said good-dat-frame counter and said interface means, wherein said analyzer analyzes each of said plurality of frames, and starts said second timer when said good-dat-frame counter exceeds a second predetermined value; and

a third display system connected to said interface and said second timer, wherein said third display system displays a neighbor notification failed type of error message when said second timer exceeds a second predetermined time before said interface receives a frame indicating a nearest active upstream neighbor has changed.

5. The test device of claim 4 further comprising:

a third timer connected to said interface;

a request-init counter connected to said interface;

a third analyzer connected to said interface and said third timer, wherein said third analyzer analyzes each of said plurality of frames and starts said third timer when said interface receives a frame indicating a nearest active upstream neighbor has changed and said interface subsequently receives a request init frame, and further wherein said third analyzer increments said request-init counter each time a request init frame is received;

a fourth display system connected to said third timer and said third analyzer, wherein said fourth display system displays a request init failed type of error message when said third timer exceeds a third predetermined time before said request-init counter exceeds a third predetermined number.

6. The test device of claim 5 further comprising:

a fifth display system connected to said interface for displaying a station inserted message after said request-init counter exceeds said third predetermined number.

11. A method for monitoring a token-ring local area network, wherein said token-ring local area network has at least one network computer station attached thereto, and further wherein said at least one network computer station may send a plurality of frames, each frame being one of several types of frames, through said token-ring local area network, said method comprising the steps of:

(a) receiving a plurality of frames being transmitted over said local area network by said at least one network computer station;

(b) examining each of said plurality of frames and starting a first timer after receiving a first duplicate address type of frame;

(c) displaying a duplicate address test failure error message when said first timer exceeds a first predetermined time before receiving a second duplicate address type of frame.

12. The method of claim 11 further comprising the steps of:

(d) counting a number of duplicate address type of frames received that indicate a duplicate address; and

(e) displaying an insertion failure error message when said number of duplicate address type of frames exceeds a first predetermined count.

13. The method of claim 12 further comprising the steps of:

(f) counting a number of duplicate address type of frames received that do not indicate a duplicate address;

(g) examining each of said plurality of frames, and starting a second timer when said count of said duplicate address type of frames that do not indicate a duplicate address exceeds a second predetermined value; and

(h) displaying a neighbor notification failed type of error message when said second timer exceeds a second predetermined time before a frame is received that indicates a nearest active upstream neighbor has changed.

14. The method of claim 13 further comprising the steps of:

(i) examining each of said plurality of frames and starting a third timer after receiving a frame indicating a nearest active upstream neighbor has changed and after also receiving a request init frame;

(j) displaying a request init failed type of error message when said third timer exceeds a third predetermined time before a predetermined number of request init frames have been received.

15. The method of claim 14 further comprising the steps of:

(k) displaying a station inserted message after receiving said predetermined number of request init frames.