Diagnostic Functionality for Wireless Client Connectivity Problems in Wireless Networks

• US 20090113244A1
• Filed: 12/17/2007
• Published: 04/30/2009
• Est. Priority Date: 10/30/2007
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Doshi, Bhautik, Marathe, Ranganatha, Narayanan, Premnath, Mohanty, Ambika Prasad, Gambhir, Amish, Raju, Bijuraj, Badjate, Pramod, O'Hara, Robert B. JR.
• Granted Patent: US 7,765,256 B2
• Time in Patent Office: Days
• US Class Current: 714/25
• CPC Class Codes: H04W 24/08 Testing, supervising or monitoring using real traffic

Abstract

A troubleshooting system. In particular implementations, a method includes collecting, from a first wireless network element, PEM state associated with a wireless client having a connection problem, and collecting log data associated with the wireless client from the first wireless network elements and one or more other wireless network elements. The method further includes correlating the PEM state and log data based on a network security protocol employed by the wireless client, where the network security protocol corresponds to an expected sequence of events. The correlating includes correlating events and messages collected based on the expected sequence of events, and comparing the correlated sequence of events to a data store of diagnostic information to identify one or more possible causes of the connection problem.

Claims

1. A method comprising:

receiving from one or more wireless network elements, connection state information associated with a wireless client having a connection problem;

receiving from one or more network infrastructure elements log data associated with the wireless client;

correlating the connection state information and the log data based on a network security protocol employed by the wireless client, wherein the network security protocol corresponds to an expected sequence of events, wherein the correlating comprises;

ordering events and messages indicated in the log data based on the expected sequence of events and the connection state information; and

comparing the correlated events and messages to a data store of diagnostic information to identify one or more possible causes of the connection problem.

2. The method of claim 1 wherein the correlating comprises comparing a plurality of last N event messages and the connection state information against possible connection problem causes in a lookup table.

3. The method of claim 1 wherein the correlating further comprises:

determining from the log data time stamps corresponding to the events and messages; and

ordering the events and messages based on the time stamps and the expected sequence of events.

4. The method of claim 1 further comprising displaying the one or more possible causes of the connection problem in a graphical user interface (GUI).

5. The method of claim 4 further comprising displaying a connection state of the wireless client in the GUI.

6. The method of claim 4 further comprising providing a troubleshoot wizard in the GUI, wherein the troubleshoot wizard facilitates analysis of the connection problem.

7. The method of claim 1 further comprising displaying the one or more identified possible causes of the connection problem and one or more corrective action suggestions in a graphical user interface (GUI).

8. Logic encoded in one or more tangible media for execution and when executed operable to:

receive from one or more wireless network elements, connection state information associated with a wireless client having a connection problem;

receive from one or more network infrastructure elements log data associated with the wireless client;

correlate the connection state information and the log data based on a network security protocol employed by the wireless client, wherein the network security protocol corresponds to an expected sequence of events, wherein to correlate the connection state information and log data, the logic is further operable to;

order events and messages indicated in the log data based on the expected sequence of events and the connection state information; and

compare the correlated events and messages to a data store of diagnostic information to identify one or more possible causes of the connection problem.

9. The logic of claim 8 wherein the logic is further operable to compare a plurality of last N event messages and the connection state information against possible connection problem causes in a lookup table.

10. The logic of claim 8 wherein the logic is further operable to:

determine from the log data time stamps corresponding to the events and messages; and

order the events and messages based on the time stamps and the expected sequence of events.

11. The logic of claim 8 wherein the logic is further operable to display the one or more possible causes of the connection problem in a graphical user interface (GUI).

12. The logic of claim 11 wherein the logic is further operable to display a connection state of the wireless client in the GUI.

13. The logic of claim 11 wherein the logic is further operable to provide a troubleshoot wizard in the GUI, wherein the troubleshoot wizard facilitates analysis of the connection problem.

14. The logic of claim 8 wherein the logic is further operable to display the one or more identified possible causes of the connection problem and one or more corrective action suggestions in a graphical user interface (GUI).

15. An apparatus comprising:

one or more processors;

a memory;

a network interface; and

logic encoded in one or more tangible media for execution and when executed operable to cause the one or more processors to;

receive from one or more wireless network elements, connection state information associated with a wireless client having a connection problem;

receive from one or more network infrastructure elements log data associated with the wireless client;

correlate the connection state information and the log data based on a network security protocol employed by the wireless client, wherein the network security protocol corresponds to an expected sequence of events, wherein to correlate the connection state information and log data, the logic is further operable to cause the one or more processors to;

order events and messages indicated in the log data based on the expected sequence of events and the connection state information; and

compare the correlated events and messages to a data store of diagnostic information to identify one or more possible causes of the connection problem.

16. The apparatus of claim 15 wherein the logic is further operable to cause the one or more processors to:

compare a plurality of last N event messages and the connection state information against possible connection problem causes in a lookup table.

17. The apparatus of claim 15 wherein the logic is further operable to cause the one or more processors to:

determine from the log data time stamps corresponding to the events and messages; and

order the events and messages based on the time stamps and the expected sequence of events.

18. The apparatus of claim 15 wherein the logic is further operable to cause the one or more processors to:

display the one or more possible causes of the connection problem in a graphical user interface (GUI).

19. The apparatus of claim 18 wherein the logic is further operable to cause the one or more processors to:

display a connection state of the wireless client in the GUI.

20. The apparatus of claim 18 wherein the logic is further operable to cause the one or more processors to:

provide a troubleshoot wizard in the GUI, wherein the troubleshoot wizard facilitates analysis of the connection problem.

21. The apparatus of claim 15 wherein the logic is further operable to cause the one or more processors to:

display the one or more identified possible causes of the connection problem and one or more corrective action suggestions in a graphical user interface (GUI).