|
|
The Protocol Conversion Trace function is a diagnostic tool used to trace Protocol Data Unit (PDU) problems. It captures all PDUs sent or received on a 64Kbps signaling path. All traffic channels that are logically connected to those on the desired signaling path are also captured. This raw data provides the Conversion Analyzer with a view in both directions of a call of the following:
Conversion tracing is started by issuing the MML Start Trace command, and stopped using the MML Stop Trace command. During the period between the start and stop trace commands, called the "capture" period, the trace function writes the PDUs to the capture file. See "MML Commands" for Stop Trace Procedures.
Automatically installed at time of initial installation.
No site configuration required.
The operational service state of the signal path will affect the collection of PDUs.
This command starts a protocol conversion trace on a signal path. For a more detailed explanation of the process, see "MML Commands."
mml> STA-SC-TRC:<sigPath id>:<parms>;
| Logical identifier for the signaling path. |
| One or more optional parameters. |
| File where the captured PDUs are stored. This file is automatically created by the TransPath system and stored in the trace directory (see directory tree diagram). If this value is not present, the TransPath system will open a file with the default name " |
| Duration in seconds to trace. |
The log can be used as input to the Conversion Analyzer, to identify and isolate signaling protocol problems. For performance reasons, the log file is written from the TransPath system until the 8 Kb boundary has been reached or until the capture session has been stopped.
| Path has commenced tracing. |
| Trace cannot be performed because the path is already being traced. |
In this example, a capture session is started for all PDUs going through the signaling path identified as T-1-1. It stores the trace log in ./var/trace/T-1-16.log as in the following:
mml> STA-SC-TRC:T-1-1
In the next example, a capture session is started for the signaling path identified as T-2-18. Output is stored in ./var/trace/Signal01.trc. This session runs for 600 seconds (10 minutes) as in the following:
mml> STA-SC-TRC:T-2-18:log="Signal01.trc",prd=600
This command stops protocol conversion trace on a signal path or all signal paths. For a more detailed explanation of the process, see "MML Commands."
mml> STP-SC-TRC:<sigPath id>
mml> STP-SC-TRC:ALL
<sigPath id> is the logical identifier for the signaling path. <ALL> is the logical identifier for all signaling paths currently being traced.
| The stop trace cannot be performed because the trace has already been stopped. |
The following command example will stop a capture session on the path identified as T-1-1.
mml> STP-SC-TRC:T-1-1
This next example will stop all active capture sessions.
mml> STP-SC-TRC:ALL
Signal channel trace analysis is done at the Technical Assistance Center. The file is to be supplied to the technical assistance center for examination and evaluation.
The Log Rotation program performs maintenance on the following TransPath system system logs:
The program is set up to maintain one current and eight historical copies for each of the logs given above. For the command format, see "MML Commands." The current and all historical versions of the log are stored in the /var/log directory.
The Log Rotation program is named: log_rotate.sh. This program must be run as the Superuser because it affects syslogd, the UNIX system log daemon. The cron process executes the rotate script daily at 04:05 hours, local time.
The Log Rotation program operates in the following manner:
1. The age of a historical file is determined by its numeric suffix.
2. The youngest historic file is <log name>.0 and the oldest is <log name>.7.
3. Each execution of the program will move <log name>.6 to <log name>.7, then <log name >.5 to <log name> .6 and so on.
4. Finally, it will move the current log to <log name> .0, create a new <log name> file, and then start storing in it again.
The installation automatically puts an entry for log_rotate.sh in the UNIX crontab so it runs automatically at 04:05 hours once a day. No further configuration is necessary.
Automatic execution of log_rotate.sh can be modified by editing the log_rotate.sh entry in /var/spool/cron/crontabs/root. SuperUser access is necessary to do this.
No site configuration is required.
This Disk Monitor program periodically checks the amount of disk space used within the configurable set of disk partitions. This ensures that there is sufficient disk space available in each disk partition for TransPath system to continue to operate at peak performance. If any disk partition exceeds the configurable usage threshold, TransPath system will generate a "DISK" alarm, a warning of a disk partition overrun, and a warning of insufficient disk space.
The disk-monitoring program is named diskmonitor.sh.
The Disk Monitor program is run periodically by the Process Manager, according to the chkInterval configuration value set in the processes.dat file. If any disk in the filesys list in diskmonitor.sh has been filled beyond the maximum (MAX) capacity, the Disk Monitor generates a "DISK" alarm. The Disk Monitor will automatically clear the alarm when all disks have receded below the MAX threshold. While in alarm, the log trimmer script will run the files residing in the spool and log directories.
When disk space utilization is over the set threshold in the script, old log files will be trimmed. The diskmonitor.sh script invoked periodically by the Process manager also trims old platform, command, and alarm log files in the ../var/log and ../var/spool directories. The script will delete previous days log files from the directories mentioned above until the disk space utilization recedes below the set threshold. The script will not trim log files that are at most 24 hours old.
The diskmonitor.sh program is initially installed in the following directory path:
TransPath/local/
In order for the disk monitoring program to function correctly, the following two files must be configured (edited) to the site requirements: diskmonitor.sh and process.dat
During initial installation, the customer must access and configure the diskmonitor.sh "Customizable Variables" to the specific site requirements. This means that the MAX and filesys in diskmonitor.sh are preset to default settings and must be configured to customer site requirements. Configure the diskmonitor.sh doing the following steps:
Step 1 filesys - Replace the preset-defined file systems with the customer required site configurations.
Step 2 MAX - Change the preset-defined partition threshold to the desired configurable partition usage threshold required to generate the alarm. The units of disk space in use is expressed as a percentage of the amount of available partitioned disk space (the maximum value = 100%).
On the "DSKM-01" line, change the chkInterval value to the desired site sampling time period required for running the disk monitor program. Do not change any other values on this line.
|
|