Chapter 2: Troubleshooting Planning - Avaya WLAN 8100 Series Troubleshooting Manual

Hide thumbs Also See for WLAN 8100 Series:
Table of Contents

Advertisement

Chapter 2: Troubleshooting Planning

There are some things you can do to minimize the need for troubleshooting and to plan for doing it as
effectively as possible.
First, use the WLAN 8100 Series Documentation Roadmap to familiarize yourself with the documentation
set, so you know where to get information when you need it.
Second, make sure the system is properly installed and maintained so that it operates as expected.
Third, make sure you gather and keep up to date the site map, logical connections, device configuration
information, and other data that you will require if you have to troubleshoot.
• A site network map identifies where each device is physically located on your site, which helps locate
the users and applications that are affected by a problem. You can use the map to systematically
search each part of your network for problems.
• You must know how your devices are connected logically and physically with virtual local area
networks (VLAN).
• You should maintain online and paper copies of your device configuration information. Ensure that
all online data is stored with your site's regular data backup for your site. If your site has no backup
system, copy the information onto a backup medium and store the backup offsite.
• Store passwords in a safe place. It is a good practice to keep records of your previous passwords in
case you must restore a device to a previous software version. You need to use the old password
that was valid for that version.
• It is a good practice to maintain a device inventory, which list all devices and relevant information for
your network. Use this inventory to easily see the device types, IP addresses, ports, MAC addresses,
and attached devices.
• If your hubs or switches are not managed, you must keep a list of the MAC addresses that correlate
to the ports on your hubs and switches.
• Maintain a change-control system for all critical systems. Permanently store change-control
records.
• It is a good practice to store the details of all key contacts, such as support contacts, support numbers,
engineer details, and telephone and fax numbers. Having this information available during
troubleshooting saves you time.
Fourth, understand the normal network behavior so you can be more effective at troubleshooting
problems.
• Monitor your network over a period of time sufficient to allow you to obtain statistics and data to see
patterns in the traffic flow, such as which devices are typically accessed or when peak usage times
occur.
• Use a baseline analysis as an important indicator of overall network health. A baseline view of
network traffic as it typically is during normal operation is a reference that you can compare to network
Avaya WLAN 8100 Troubleshooting Guide
August 2011
7

Advertisement

Table of Contents
loading

Table of Contents