Chapter 4: Troubleshooting Planning - Avaya 3524gt Troubleshooting Manual

Chapter 4: Troubleshooting planning

There are things you can do to minimize the need for troubleshooting and to plan for doing it as effectively
as possible:
1. Use the Avaya Ethernet Routing Switch 3500 Series — Documentation Roadmap , NN47203–
101 to familiarize yourself with the documentation set, so you know where to get information
when you need it.
2. Make sure the system is properly installed and maintained so that it operates as expected.
3. 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).
• 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.
• A good practice is 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.
Troubleshooting March 2013 17