Evaluate System Performance - Avaya Cajun P882 User Manual

Recognize
Performance
Issues

Evaluate System Performance

Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide, v5.3.1
Manage F-Chip memory
Manage Cache Timers
When the ACL is the root of a performance problem, it shows as the
Slow Path becoming overused. The Slow Path is not designed to
handle significant traffic levels since the single CPU also handles all
other management functions. There are several ways to determine if
the CPU is overloaded:
Continuous PING to the supervisor: timeouts or inconsistent
timing of echo responses.
Slow Scrolling LED Marquee: This is good visual sign that the
CPU is busy.
Slow Management response: If Avaya Multiservice Network
Manager (MSNM), Avaya Policy Manager (APM), HPOV, or a
MIB browser get slow updates, this can signify a busy CPU or
saturated network.
Slow network response: This can be measured in a variety of
ways.
Once you have determined that the ACL is the root cause, and have
optimized the rules, you need to tune system parameters.
The first step is to determine whether the use of an ACL affects
system performance. This requires an analysis of traffic patterns, the
use of device statistics, and a "process of elimination". If you suspect
that the use of an ACL is degrading system performance and
"Disabling Access Control" improves performance, you are ready to
begin the process.
In order to perform the diagnosis, you need to generally identify
routed Flows through the switch. You will need this information to
match Flows against the F-chip statistics to locate the problem area.
The next step (and this will be repeated as needed) is to note the
usage statistics with and without the ACL enabled.
Configuring IP Routing
9-33