Service
P31003-H3550-S403-4-7620, 02/05
12-30 HiPath 3000 V5.0, HiPath 5000 V5.0, Service Manual
service.fm
Guided Maintenance
12.3.1.6 HiPath Manager PCM Trace Monitor for HiPath 5000
12.3.1.6.1 HiPath Manager PCM Trace Monitor Applications
Communication between the different HiPath 5000 applications is organized using various buff-
er tables and messages. You can monitor the individual entries in the different buffer tables, ex-
changed immediate messages, program and communication messages for the relevant com-
ponent in a separate trace window, in other words, a separate window is opened for each
component (application).
The trace windows can be viewed using the Trace Monitor and swapped out for further process-
ing.
Trace messages can be displayed for the following HiPath 5000 applications:
● Feature Server
Two trace files are available:
– \winnt\system32\carlogfile.txt
provides details on which HG 1500 boards have logged on to the network and when.
– \winnt\system32\rgtracefile.txt
provides details on when the individual HG 1500 boards were assigned a station num-
ber.
● Presence Manager
Two trace files are available:
– \winnt\system32\dssdiagnosefile.txt
– \winnt\system32\dsslogfile.txt
● HiPath Manager PCM Administration
Administration of the configuration parameters for component control by the user, for gen-
eral parameters, for call charge evaluation and analysis.
● HiPath Manager PCM
Configuration of call handling and call forwarding using definable profiles.
● HiPath GetAccount
Internal component that is responsible for evaluating and saving call charges and for im-
mediate printing.
>
This documentation does not cover interpretation of the trace window contents by
the Trace Monitor. Trace files are used for problem analysis and are interpreted by
Service Support during servicing.
The description below can be used to determine the work steps required for Trace
Monitor navigation and control and for swapping out the trace contents to a file.
To Next Page
Loading...
Need help?
General