Table of Contents
Advertisement
Network Node Processor (NNP) Adapter Trace Function
The NNP adapter trace function collects data on the line activity of any processor
(CLP, TRP, and ESCP) that you have installed on the 3746. You use the trace
function if you have a problem with traffic flow through the processors.
On the service processor, you start a trace in the NNP which produces a data file.
You then format the data file and view the formatted results on the service
processor. You can select from three types of formatter, each one designed to
read and format the data in your trace:
Running the Trace
The trace is initiated manually by you on the service processor. You have to
manually stop the trace after you have encountered the problem with traffic flow.
6-MB file limit: There is a 6-MB limit on the size of the trace file. If the trace is
For further reference on formatted trace file interpretation, see the standards as
described in the following:
You can also use a search engine on the Web to access the most current RFCs on
trace file interpretation.
APPN (but not HPR) protocols and above.
IP protocols and above.
DLC (this does not include PPP and ISDN) protocols, including APPN/HPR.
not manually stopped, when the file reaches the 6 MB maximum, the data
will wrap, replacing the original data.
Attention
Running a trace impacts the performance of 3746 network operations.
Token-Ring Network Architecture, SC30-3374
Synchronous Data Link Control Concepts, GA27-3093
SNA Formats, GA27-3136
3745/3746 Planning Series: Protocols Description, GA27-4241
The ANSI/IEEE 802.2 standard for token-ring and frame relay
ITU-T recommendation X.25
Chapter 4. Working with Network Node Processor (NNP) Functions
4-11
Advertisement
Table of Contents
