How to Set Script Permissions and ModesAdded by IBM on November 30, 2011 | Version 1 (Original)
Adequate administrative permissions
Parent topic: Configuring Telephony Control Server R2 and R3
- On the Telephony Control Server: Change the owner and group of the "setup_tracing.ksh" script to srx:other with command:
>chown srx:other setup_tracing.ksh
- Change the owner and group of the "setup_trace_transfer.ksh" script to root:root with command:
>chown root:root setup_trace_transfer.ksh
- Set the executable permissions for both scripts:
>chmod +x setup_trace_transfer.ksh
>chmod +x setup_tracing.ksh
- Disable the Telephony Control Server PrttReader process from reading the trace buffer. This is done via CLI and setting the parameter Srx/PrttReader/ReadFromDriver to 0.
- If tracing has already been configured in the Telephony Control Server, stop the tracing job.
- Stop all oprtt_read processes on each node before running the configuration scripts:
>ps -ef | grep oprtt_read (get process id).
- >kill -9 <process id>
- Remove all existing "raw" files from the /software/RTT directory
Invalid *.raw* files will prevent the transfer process to work properly.
- "Start RTT tracing:
- Run the setup_tracing.ksh script to configure the tracing process:
>setup_tracing.ksh (run as srx user)
- Verify that the oprtt process is running:
- Verify that the trace files (<filename>.raw) are being written to the correct directory:
- Configure the FTP transfer process:
- Run the setup_trace_transfer.ksh script to configure the FTP transfer process:
> setup_trace_transfer.ksh (run as user "root")
- Enter Trace Management (TM server IP address: Type the TM server's IP address.
- Enter TM FTP login: Type the FTP user id configured in TM.
- FTP password: Type the FTP password for the user id configured in TM.
- Enter the system name or ID as created on the TM server, i.e. System1. System ID: Type the system name given to the Telephony Control Server node in TM.
- Enter trace file upload interval (minutes) [1|2|3|4|5|10|15]: Type the frequency (in minutes) that you want the trace files to be transferred to the TM server.
After the "setup_trace_transfer.ksh" script is run, it creates a cron script and sets up a cron job that is run based on the frequency that you set as the "trace file upload interval". The recommended value is 2 minutes.
- Verify that the root cron job was set correctly:
> crontab -l (look for the rttftp2.ksh job)
- Optional: Test the ftp connectivity between the Telephony Control Server and the TM server:
- >ftp <TM_IP_address> username=tracedata passwd=<ftp-tracedata-passwd>
The Telephony Control Server is now configured to generate and transfer trace data to the TM server.
- Verify that the trace files (<filename>.raw) are being written to the correct Telephony Control Server directory: /software/RTT
- Verify that the files are transferred to the TM shared folder \\<TM-server-address>\tracedata\<system-name> (e.g.: \\my-osvtm-serv.mydomain.com\tracedata\SYS1).
- When rebooting or after patching the Lotus Sametime Unified Telephony server, restart the setup_tracing process:
- Run the setup_tracing.ksh script:
> setup_tracing.ksh (run as srx user)
- Verify that the trace files (<filename>.raw) are being written to the correct directory: /software/RTT