tems automatic administration

TEMS Automatic 8.3 Administration April 2011, © Ascom 1

TEMS AUTOMATIC

- Administration

03809 LZU 102 1759


SYSTEM OVERVIEW

Data Test Nodes

PLMN

[ Administration]


TEMS Discovery

Operator Console

ComServer

TAConfigurationDatabase(Measurement)

Statisticaldatabase

LogfileStorage OLAP

TU

CallGenerator

FTP Server

DATA FLOW

The following file types are sent between the TU and the Measurement database:

Log file *.log/*.lzz/*.lzmIP log file *.pcap (+ *.log in zip container, lzm compressed) SW Upgrade package *.upgTU Event file *.entTU Statistics *.staTU Configuration *.intWork Order *.wntTU Report *.rntLogfile Info *.lfiLogfile Request *.lfr

File from the TU that is sent to the GARBAGE folder:

TU Trace file *.trc

For Manua Upload of logfiles

TDE Master/ MeasurementDatabase

TDE Databases

TDE ProjectDatabases

REGIONS FOLDER


Let’s follow the files from the TU all the way to the database and beyond.

Data upload is performed and the file is sent to the TUs folder under the IN folder in the FTP Server.

Logfiles are compressed to reduce the upload time. (*.lzz/*.lzm/*.zip (if IP logging used))

ComServer

ADP

Measurementdatabase

TU FTP Server

FTP server Each TU has its own IN folder.

DATA FLOW FROM THE TU

TDE Project Database



The file is first fetched through the firewall and put in the LINEHANDLER/IN folder by the ComServer.

If it is a logfile it is also moved to the LOGFILES folder by the ComServer.

ComServer/ADP

DATA FLOW FROM THE TU

ComServer

TLH

Measurementdatabase

TU FTP Server



Note! This regards all files except logfiles.

The file is fetched from the LINEHANDLER/IN folder and is formatted to fit into the Measurement database to which it is moved by the ComServer.

DATA FLOW FROM THE TUOther files than a logfile

ComServer

ADP

Measurementdatabase

TU FTP Server

ComServer/TLH


Let’s follow a log file from the TU all the way to the database and beyond.

Note! This regards logfiles only.

The logfile is fetched from the LOGFILES folder, the Events are extracted and it is formatted to fit into the TDE Project database to which it is moved by the ADP.

If the system is installed with a Logfile Storage database, a copy of the logfile will also be stored there by the ADP. If not, the logfiles are stored in the CONVERTED folder.

LogfileStorage

ComServer/TLH

DATA FLOW FROM THE TUOnly logfiles

*.log *.lzz

*.lzm *.zip

*.log => *.lzz

*.lzz

*.lzm

*.zip

ComServer

ADP

TDE Projectdatabase

TU FTP Server

ComServer/TLH



Log file *.log/*.lzz/*.lzm/*.zip

TEMS Discovery can be used to export it later from the Logfile Storage database to any folder you like.

TEMSDiscovery

Statisticaldatabase

OLAP

CallGenerator

Logfiles to your desired location(new folder created & named after TU or TI logfile location at import)

Uncompressed:*.logFor *.zip, new folder created with uncompressed content of zip container (*.log + *.pcap)

Compressed:*.lzz or *.lzmFor *.zip, new (zipped) folder created with content of zip container

LogfileStorage

ComServer

ADP

TDE Projectdatabase

TU FTP Server

DATA FLOWLogfile storage


Let’s follow a log file from the TU all the way to the database and beyond.

As soon as the files are transferred into the TDE Project database it will be possible to look at the logfiles in TEMS Discovery and TU information in the Operator Console.

After the Cube has been processed it will be possible to view the latest statistical plots in an external reporting tool and in TEMS Discovery.

TEMSDiscovery

Measurementdatabase

Statisticaldatabase

OLAP

Operator ConsoleDATA FLOWViewing the data


Let’s follow the files all the way to the TU from the database.

When changes are done to the TU from the Operator Console, the Measurement database will be updated with the new information.

If it is a Work Order the status for it will be: New

ComServer

Measurementdatabase

TU FTP Server

Operator Console

DATA FLOWTo the TU



The ComServer reads the Measurement database in intervals and creates a plain text file with the changes. This file is put in the LINEHANDLER/OUT folder for this TU.

The status in the OC is updated to transfer.

ComServer

Measurementdatabase

TU FTP Server

Operator Console

DATA FLOWTo the TU

ComServer



The ComServer moves the file to the FTP Server OUT folder for the TU.

FTP server Each TU has its own OUT folder.

ComServer

Measurementdatabase

TU FTP Server

Operator Console

DATA FLOWTo the TU



The next time the TU performs a data upload it will check the OUT folder if there are any files and download these.

When the transfer is complete and the TU has sent its acknowledge, the status in the OC is changed to: Running

ComServer

Measurementdatabase

TU FTP Server

Operator Console

DATA FLOWTo the TU


At each voice call setup there are DTMF signaling with the MSN number and an index for this unique call.

These are used to be able to synchronize the UL and DL PESQ scores in the database later.

The TU calculates and collects the DL PESQ scores as well as the MSN and the index for the call in the logfile.

The Call Generator calculates and collects the UL PESQ scores, the MSN and the index temporarily in a list during the call.

Measurementdatabase

TU

CallGeneratorPSTN

PLMN

DL PESQUL PESQ

DATA FLOWPESQ


At a fixed interval the Call Generator will use the MSN and index to populate the database with the accumulated UL PESQ values in the list.

The DL PESQ scores are still in the logfile in the TU.

DL PESQUL PESQ

Measurementdatabase

TU

CallGenerator

DATA FLOWPESQ


At the next Data upload the logfile with the DL PESQ will be merged with the info from the list into the database.

DL PESQUL PESQ

ComServer

TLH

Measurementdatabase

TU FTP Server

DATA FLOWPESQ


Initiated by a work order from the Operator Console, the TU makes a call (without DTMF signaling) to the Mobile Receiving Unit (MRU) which answers automatically and starts to play PESQ sentences.

The TU calculates and collects the DL PESQ scores (in fact affected by the whole mobile-to-mobile path, both UL from MRU and DL to TU).

The PESQ scores are placed at the correct time and position in the logfile, which is then delivered at the next Data upload.

Measurementdatabase

TU

PSTN

PLMN

DL PESQ

MRU

DL PESQ

DATA FLOWMobile-to-Mobile PESQ with MRU


Initiated by a work order from Operator Console, TU 1 makes a call to TU 2 which answers automatically (as stated in the corresponding work order for that TU) and starts to play PESQ sentences.TU 1 calculates DL PESQ scores (in fact affected by the whole path, both UL from TU 2 and DL to TU 1).

TU 1 also plays PESQ sentences and TU 2 calculates the UL PESQ scores (in fact affected by the whole path, both UL from TU 1 and DL to TU 2).

The PESQ scores are then stored in the corresponding logfiles, which are then delivered at the next Data upload.

The same principle is applied for the case where the call is set up between two internal devices in one TU.

Measurementdatabase

TU 1

PSTN

PLMN

DL PESQ in logfile from TU 1

DL PESQ

DATA FLOWMobile-to-Mobile PESQ with TUs

TU 2

UL PESQ

UL PESQ in logfile from TU 2


Point out all functions...


TEMS Discovery


Check the NT Eventlog for invalid logins from TUs.

Clean the TU folders by deleting invalid or corrupt

files. Check the Quick Guide for valid files.

FTP SERVER, MAINTENANCE


Verify that files are processed (moved) from the Logfiles directory and moved to the Converted folder.

Check the amount of files in the Garbage folder. Monitor the Converted folder and zip/delete logfiles at regular

intervals. (Maintenance plan) Import TEMS Investigation, TEMS Pocket and TEMS

Drivetester logfiles.

COMSERVER/TLH

COMSERVER & TLH


In the OC, check that the call generator is

working (calling and answering).

This is where the PESQ limit for when to save

bad PESQ samples are located.

CALL GENERATOR


Perform backups at regular intervals Transaction logs, daily

Full backup, weekly

Monitor disk space Never run out of disk space.

DB Clean Use DB Clean to remove old data.

MEASUREMENT DATABASE


Perform backups at regular intervals Weekly full backup

Monitor disk space

STATISTICS DATABASE


Perform backups at regular intervals

Weekly full backup

Monitor disk space

Remove logfiles that are no longer needed.

LOGFILE STORAGE DATABASE


Make sure that the statistics is updated/processed Can be done from the statistics process information window available on the statistics client.

Perform weekly full backups of the Geobases.

Monitor disk space

OLAP


STATISTICS

Create geobase Decide what data it should contain.

Set the user defined parameters.

Templates

Initial processing

Schedule processing


CREATING A GEOBASE

Technology Time Area Partitions TEMS Investigation/TEMS Automatic TU (UMTS only) Measure Groups (“Cubes”) Distribution group definitions. KPI settings (UMTS only)

NOTE – Only some* of the settings of a geobase can be altered once it is created.

*KPI settings, time, parcel size and database connections


CREATING A GEOBASE – LOG IN

In the Statistics Configuration window, you right-click and select

Log on...

You select server and Statistics database


From the popup menu when right-clicking the Statistics Database, you add a Geobase of a certain technology.

You select any of the templates, or browse for a previously exported geobase settings file to copy

A wizard will guide you through the creation process

CREATING A GEOBASE – START 1


CREATING A GEOBASE – START 2

In the result view of Route Selector, you select the logfile(s)

you want to include in the Geobase.

From the popup menu when right-clicking the selected

logfile(s), you create a Geobase of a certain technology.

A wizard will guide you through the creation process


You specify or edit the connections to the servers and

databases involved

Datastaging area database contains data transferred from

the Measurement database, to be processed and entered

into the OLAP database which is contained by the Analysis

server

Statistical db(stat config+ datastaging)

CREATING A GEOBASE – CONNECTIONS

(Analysis server)

OLAP

Measurement db


CREATING A GEOBASE – GENERAL


If you decided to use partitions in previous step, the option

“To time” is not valid and therefore not visible.

CREATING A GEOBASE – TIME


CREATING A GEOBASE – POSITION


CREATING A GEOBASE – MEASURE GROUPS


CREATING A GEOBASE – KPIs


Backup & recovery strategies

User administration

Admin tasks in MS SQL 2008

DATABASE ADMINISTRATION


Most crashes are due to disk failure Monitor the state of the Raid-5 disks, catch the first disk failure

BACKUP AND RECOVERY


Weekly full backup

Daily backup of transaction logs

No software backups

BACKUP PROCEDURE


Measurement, Statistics and the Logfile Storage databases

OLAP Server geobases

Logfiles and TU administration files in Regions\Converted

folder

Map files in the Map server folder

BACKUP PROCEDURE – WEEKLY FULL BACKUP


Backup to disk/tape the Measurement database transaction log

Backup to separate disk of the Regions\Converted folders or the Logfile Storage

database transaction log.

No transaction log backup for Geobases. Full backup is the only option. When

recovering, incremental processing is therefore required for Geobases to

include most recent data.

NOTE – the master database needs to be backed up whenever changes to

logins have been made.

DAILY BACKUP OF TRANSACTION LOGS


Day No. Day of the Week Events Backup Tasks Notes

1 Thursday New system installation. Full backup of Measurement, Statistics, Geobases, msdb, and master.Backup of Map Server folder.

A

2 Friday Transaction log backup of Measurement and Logfile storage. Full backup of msdb.

B

3 Saturday Full backup of Measurement, Statistics, Logfile storage, Geobases, and msdb.Backup of Region\Converted and Map Server directories.

C

4 Sunday Transaction log backup of Measurement and Logfile storage. Full backup of msdb.

5 Monday Transaction log backup of Measurement and Logfile storage. Full backup of msdb.

6 Tuesday A new login is created (master database modified).

Transaction log backup of Measurement and Logfile storage. Full backup of master. Full backup of msdb.

D

7 Wednesday Transaction log backup of Measurement and Logfile storage. Full backup of msdb.

8 Thursday Transaction log backup of Measurement and Logfile storage. Full backup of msdb.

9 Friday New Geobases are created. Transaction log backup of Measurement and Logfile storage. Full backup of msdb.

E

10 Saturday Full backup of Measurement, Statistics, Logfile storage, Geobases, and msdb.Backup of Region\Converted and Map Server folders.

11 Sunday Transaction log backup of Measurement and Logfile storage. Full backup of msdb.

12 Monday Transaction log backup of Measurement and Logfile storage. Full backup of msdb.

13 Tuesday Transaction log backup of Measurement and Logfile storage. Full backup of msdb.

14 Wednesday Transaction log backup of Measurement and Logfile storage. Full backup of msdb.

BACKUP EVENT SCHEDULE


Day No.

Day of the Week

Events Backup/Recovery Tasks Notes

15 Thursday Database crash One or several databases crashes and the TEMS Automatic system has to be recovered from backups.

16 Friday Transaction log backup of Measurement and Logfile storage.Full backup of msdb. Ordinary system operation is resumed.

RECOVERY PROCEDURE


Tool User Profile Database Roles

Presentation Normal user TEMS_Presentation_User

Operator Console Administrator user TEMS_Automatic_Administrator

Operator Console Normal user TEMS_Automatic_Operator

Operator Console Read-only user TEMS_Automatic_Monitor

Call Generator Application TEMS_Automatic_CallGenerator

ComServer Application TEMS_Automatic_ComServer

Logfile Handler (TLH) Application TEMS_Automatic_TLH

Service Monitor Application TEMS_Automatic_Administrator

Database Clean (no profile exists) (uses the database owner, “tems”)

Statistics (no profile exists) (uses the database owner, “tems”)

Presentation Diagnostics user TEMS_Diagnostics_Administrator

USER HANDLING


Scheduling database backups using the maintenance plan

Scheduling archiving of geobases

Restoring a database using the maintenance plan

Restoring geobases

Backing up a database manually

Restoring a database manually

Adding users

Changing user passwords

Altering user rights

Connecting database users and logins

Creating a linked server

Changing the remote query timeout value

Administrating the logfile storage database

HOW TO PERFORM ADMIN TASKS- In MS SQL Server


Make sure that all work orders are valid Create & send new work orders.

Monitor the status of servers & TUs (alarms, uptime etc.). Remove events. TU Software upgrades.

OC


Verify that the correct site data is available.

Make sure to create areas and update statistics.

Remove old presentations.

Remove old templates.

PRESENTATION APPLICATION


MapInfo maps can be used.

Contact TEMS Automatic support.

HOW TO USE MAPS IN TA


Areas are used by:

The TU, for deciding where to measure or not.

Statistics, for calculating statistics in specific areas.

Presentation, for searching logfiles and displaying statistics.

Reporting tools, the available reports can be distributed, grouped or filtered by

area.

HOW TO CREATE AND USE AREAS


Logfile spec:

outputtype=file

output=c:\temp\LogfileHandlerTrace.log

maxentries=50000

fullaction=delete/backup

backupextension=".BUP"

execute=notepad.exe

timeformat=""

Logfile Handler components: [DBWRITER]#tracelevel=MESSAGE/WARNING/FATAL [DECODER]#tracelevel= MESSAGE [FRONTEND]#tracelevel= MESSAGE [EVENTHANDLER]#tracelevel= MESSAGE

LogfileHandlerTrace.ini

Changing a parameter => restart of application needed

Start trace by deleting # and save the file

Edit tracelevel sections to change tracing behaviour at runtime

TRACE TLH


1. Stop the Logfile Handler Monitor and Logfile Handler via Services.

2. Open and edit the LogfileHandler_1Trace.ini located in the Logfile

Handler directory C:\Program Files\Ascom\TEMS Products\Logfile

Handler\Application

3. Set the ‘output=’ line to the absolute path to the Logfile Handler trace file

(e.g C:\Program Files\Ascom\TEMS Products\Logfile Handler\

Application\Trace\TEMS Logfile Handler_1.log).

4. Remove the # tokens to enable the trace functionality for specific

component.

5. Save and close LogfileHandler_1Trace.ini.

6. Restart the Logfile Handler Monitor.

7. Now is the trace enabled, open the trace file and locate the problem.

TRACING PROCEDURE


The TLH is not processing any logfiles. Logfiles in the Logfile directory?

Connection to the Regions directory working?

TLH computer has access to the measurement database?

Is the TLH service running?

Warnings or error messages from the Logfile handler in the EventViewer?

Enable trace and send to support.

Disable the trace.

TROUBLE SHOOTING - TLH


THANK YOU!

03809 LZU 102 1759

tems automatic administration

Documents

ascomtems automatic

logfiles folder

tu trace

linehandlerin folder

garbage folder

tus folder

converted folder

measurement database