TIME
Is there a specific time that the problem occurs or begun to occur? Is there a pattern to occur or is it more random in nature?
Diagnoses: check RSS, SNR, scanning, latency and performance data from baseline (log files, MRTG, SolarWinds, etc..) Consider the average value of each, and the dates and times no change drastic occurred in these values.
Changes: consult with colleagues to determine whether changes in equipment and / or configuration have occurred since the time noted in step 1 above.
Customer Reviews (found in step 3, but you may want to move it down the list, depending on the situation): If you are a WISP operator, you are already well aware of the slipperiness of the slope can achieved when winning customers' perspectives. However, this should not be overlooked, especially if the problem affects multiple clients. The correlation of the stories of affected customers can quickly eliminate false information while solidifying the facts. Give special attention to customer questions on the use of wireless equipment in your own home and surroundings.
Check the configuration of radio: radio access question (s) using the connection method with which you are familiar (telnet, HTTP). Check the obvious areas, such as firmware version, power level, frequency, IP settings (address, gateway, DNS, SNMP, SNTP, etc), modulation schemes (if applicable), SSID, authentication (static , RADIUS, TACACS, keys), encryption, QoS, VLAN, etc.
Check the operation of radio and data monitoring tools "link activity (TCP / IP, such as statistics and Tx Rx packets), errors (discarded and retransmitted packets), conducting wireless performance and ping tests and current collecting readings RSS SNR compared to baseline in step 1.
No comments:
Post a Comment