• A good practice is 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.
4. 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 traffic data that you capture during troubleshooting. This speeds the
process of isolating network problems.
Troubleshooting planning
18 Troubleshooting March 2013
Comments? infodev@avaya.com
To Next Page
Loading...
