OSI/TS Configuration and Management Manual

OSI/TS Configuration and Management Manual—424831-001
4-1
4
Performing Monitoring and
Troubleshooting Guide
This section contains general information on performance monitoring and on
troubleshooting; it does not describe all possible combinations of what can occur in an
OSI network. It includes discussion of the following:
•
An approach to measuring performance
•
General sources of performance problems
•
Monitoring performance
•
Improving performance
•
When to use the CHECK SU command
•
An approach to troubleshooting
•
TSP process problems
•
NSP process (X25AM) problems
(with a step-by-step troubleshooting example)
•
NSP process (TLAM/PAM) problems
(with a step-by-step troubleshooting example)
•
Getting help
An Approach to Measuring Performance
There are many factors in an OSI/TS subsystem that affect performance. They include
configuration attributes, hardware, software, applications design, traffic mix and volume
of messages, and line speeds. You must consider not only these variables, but also how
these variables affect the interrelationships among the components of the subsystem.
System performance is usually measured in terms of reliability, throughput, and delay.
When configuring or adjusting the configuration of a subsystem, you must consider the
tradeoffs between usability, performance constraints, and reliability.
The OSI/TS subsystem cannot be treated in isolation the system environment must be
properly configured to provide for the needs of all the users of the network. You must
consider the importance of the OSI/TS subsystem in relation to other applications
operating on the network. Because programs share network hardware and software
resources, the whole system and all the demands on its resources must be taken into
consideration.
The subsections on monitoring performance are written under the assumption that you
have sufficient knowledge of the OSI/TS subsystem, the operating system, and