1. Diagnostics and Troubleshooting
Month Year
May 2005
September 2005
Diagnostics and Troubleshooting
Authors:
Date:
Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Emily Qi, Intel Corporation
Emily Qi, Intel Corporation

2. Month Year
May 2005
September 2005
Abstract
This document suggests Diagnostics and Troubleshooting requirements for Wireless Network Management.
Emily Qi, Intel Corporation
Emily Qi, Intel Corporation

3. Month Year
May 2005
September 2005
Motivation
STA and AP cooperative troubleshooting and Diagnostics to improve wireless performance and reduce IT cost
Improve user roaming and seamless connection experience
Fault detection
Event Log
Healing
Emily Qi, Intel Corporation
Emily Qi, Intel Corporation

4. Diagnostics Reactive Diagnostics Passive Diagnostics
Month Year
May 2005
September 2005
Diagnostics
Reactive Diagnostics
STA will alert other STA (AP) when a certain failure occurs or performance degrades
Passive Diagnostics
STA will report event log to other STA (AP) to help troubleshooting
Possible Areas:
Roaming
Link quality and connection
Authentication and Security, etc.
Emily Qi, Intel Corporation
Emily Qi, Intel Corporation

5. Roaming Diagnostics Roaming Alerts: Roaming event Log September 2005
Failure Roaming count exceeds a certain amount
Succeeded Roaming count exceeds a certain amount during the certain period
Transition time exceeds a certain amount time
Roaming event Log
Transition Initiate Time
Current BSSID
Target BSSID
Roaming reason
Transition time
Transition Reject Reason.
Emily Qi, Intel Corporation

6. Link Quality and Connection
September 2005
Link Quality and Connection
Link Alerts
STA sends alert when frame lost rate increases or throughput degrades
STA send alert when missed beacon count increases
Link Event Log
Most of them have been covered in TGk
RSSI value
Noise level (or SNR)
Signal Quality, etc.
DLS Event Log
Indication of a DLS connection initiation
Indication of a DLS connection teardown
Show MAC address of the 2 DLS peers (source and destination MAC address)
Emily Qi, Intel Corporation

7. Authentication and Security
September 2005
Authentication and Security
Association and Authentication Alerts
STA can also report “bad AP list” that STA has problem to associate to or fail to process 802.1X authentication and key generation
Authentication and Security Event Log
Authenticated key management suite: Pre-share key and 802.1X
Unicast Cipher suite – WEP, TKIP, and AES-CCMP
PMK ID that has been used
Capability Bits that have been negotiated, etc.
Emily Qi, Intel Corporation

8. Suggested Requirements for TGv
September 2005
Suggested Requirements for TGv
Add the following text to the objectives document:
TGv should support MAC extensions to improve wireless network diagnostics and troubleshooting.
TGv should provide a mechanism to allow STAs to report alerts when a certain failure occurs or performance degrades
TGv should provide an extensible framework for STAs to report event log and diagnostics data as AP requested
Emily Qi, Intel Corporation

9. September 2005
Feedback?
Emily Qi, Intel Corporation