View
54
Download
0
Category
Preview:
Citation preview
5/22/2018 Pdn 98904754
1/176
Serve atOnce Traffica
Z5.2
Administering TrafficaP-DN98904754
Issue 6-2
5/22/2018 Pdn 98904754
2/176
2 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805806352d9
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-
TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-
RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2010/9/9. All rights reserved
f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected
has to comply with the applicable safety standards.
The same text in German:
Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Span-
nung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverlet-
zungen und Sachschden fhren.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die
Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene
Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.
5/22/2018 Pdn 98904754
3/176
P-DN98904754
Issue 6-2
3
Administering Traffica
Id:0900d805806352d9
Table of ContentsThis document has 176 pages.
1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 What you need to know first . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1.1 Administering Traffica in Windows 64bit operating systems . . . . . . . . . 11
1.2 Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2 Change information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3 System availabil ity assurance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1 Monitoring TSs and TNESs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.1 Monitoring the hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.2 Monitoring the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.3 Monitoring Traffica DCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 System management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.1 Traffica system log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.2 Modifying the registry remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.3 Managing TNES-TS connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.3.1 Adjusting the message transfer rate . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.3.2 Compressing messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.4 Managing Traffica workspaces remotely . . . . . . . . . . . . . . . . . . . . . . . . 24
4.4.1 Managing workspace definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.4.1.1 Creating a new workspace in TS for TNESs . . . . . . . . . . . . . . . . . . . . . 24
4.4.1.2 Transferring and activating TNES definitions from TS. . . . . . . . . . . . . . 25
4.5 Internal alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.5.1 Configuring internal alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.5.1.1 Editing entries: enabled, sendupperlevel and sendnms . . . . . . . . . . . . 31
4.5.2 Traffic News, Traffic Views, Database Export, and File Transfer Service in-
ternal alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.5.3 Traffica Database Manager internal alarms. . . . . . . . . . . . . . . . . . . . . . 35
4.5.4 Traffica at Customer Care internal alarms. . . . . . . . . . . . . . . . . . . . . . . 35
4.6 Managing workspace content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.6.1 Workspace structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.6.2 Workspace naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.6.3 Managing IDS fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.6.3.1 Removing IDS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.6.3.2 Removing IDS fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.6.4 Managing CCMA counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.6.5 Managing open nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.6.6 Managing graph sets and categories. . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.7 Managing Traffica databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.7.1 Default database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.7.2 Managing database overload control. . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.7.2.1 Managing Traffica Database Manager overload control . . . . . . . . . . . . 45
4.7.3 Managing Traffica database switchovers. . . . . . . . . . . . . . . . . . . . . . . . 464.7.4 Managing maximum database size . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5/22/2018 Pdn 98904754
4/176
4 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805806352d9
4.7.5 Managing database tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.7.6 Managing database columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.7.6.1 Mandatory columns for Summary Report Tool in the MSC 2G adaptation.
504.7.7 Managing database indexes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.7.8 Managing unsupported database user . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.7.9 Managing RTT Server database passwords. . . . . . . . . . . . . . . . . . . . . . 54
4.7.10 Managing database cache sizes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.7.11 Managing automatic database deletion . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.7.12 General Traffica Database Manager configuration . . . . . . . . . . . . . . . . . 56
4.8 Modifying mapping fi les . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.9 Taking new mapping files into use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.10 Managing RTT Server performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.11 Managing Traffic News . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.11.1 Log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.11.2 Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.11.3 Managing Traffica web server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.11.4 Managing the Traffic News web client . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.11.5 Managing connections between Traffic News Java Client and Mediator 65
4.11.6 Managing connections between Traffic News Web Client and Mediator 66
4.11.7 Managing connections between Mediator and QEP. . . . . . . . . . . . . . . . 66
4.11.8 Managing time formats and settings in Traffic News . . . . . . . . . . . . . . . 66
4.11.9 Managing query reason codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.11.10 Managing security settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.11.11 Configuring source databases in Traffic News . . . . . . . . . . . . . . . . . . . . 67
4.11.11.1 Restarting Mediator and QEP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.11.12 Configuring the launch of external applications from Traffic News Client68
4.11.12.1 CommandLine Attribute Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.11.12.2 Filling CommandLine parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.12 Managing Traffic Simulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.12.1 Configuration and log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.12.2 Managing database connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.12.2.1 Running several database servers on one computer . . . . . . . . . . . . . . . 75
4.12.3 Using Traffica databases in Traffic Simulator . . . . . . . . . . . . . . . . . . . . . 76
4.13 Managing Database Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.13.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784.13.2 Configuring export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.13.3 Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.13.4 Registry Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.13.5 TrafExtract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.13.6 Output files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.13.7 Managing Database Export Admin Client . . . . . . . . . . . . . . . . . . . . . . . . 83
4.13.8 Licensing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.14 Managing Traffica configuration and user management. . . . . . . . . . . . . 86
4.14.1 Default CUS database configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.14.2 Configuring Traffica Configuration and User Server . . . . . . . . . . . . . . . . 87
4.14.3 Configuring the sender name in E-mail notifications. . . . . . . . . . . . . . . . 87
5/22/2018 Pdn 98904754
5/176
P-DN98904754
Issue 6-2
5
Administering Traffica
Id:0900d805806352d9
4.14.4 Configuring user account info logging . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.14.5 Configuring CUS database backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.14.6 Restoring CUS database from backup . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.14.7 Configuring Traffica CCD Inserter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894.14.7.1 Configuring CCD Inserter if there are several TNESs with different NE ad-
aptations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.14.7.2 Configuring CCD Inserter to enable TNES specific mappings. . . . . . . . 90
4.15 Managing Automatic File Transfers. . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.15.1 Supported File Transfer Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.15.2 Managing Traffica File Transfer Service . . . . . . . . . . . . . . . . . . . . . . . . 91
4.15.3 Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
5 System maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5.1 Traffica hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5.1.1 Processors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5.1.2 Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.1.3 Hard disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.1.3.1 Hard disk capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.1.3.2 Hard disk speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.1.3.3 Number of hard disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.2 Taking workspace backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.3 Maintaining History databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5.3.1 Taking backups to an external drive . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5.3.2 Restoring backup files from an external drive . . . . . . . . . . . . . . . . . . . . 97
6 System security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.1 Managing Traffica workspace users . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.1.1 User levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.1.2 Updating workspace user rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.1.3 Restricting user access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.1.3.1 Cancelling autologon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6.1.3.2 Modifying screen saver properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6.2 Managing Traffic News users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
6.3 Managing Traffic Simulator users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
6.4 Authorised connections between TS and TNES . . . . . . . . . . . . . . . . . 102
6.5 Encrypting messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
6.6 Creating a new certificate for Traffic News web client . . . . . . . . . . . . . 103
7 System development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
7.1 Traffica Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
7.2 Managing services on Windows 2008 / Windows 2008 R2 operating sys-
tem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
7.3 Managing services on Windows 2003 operating systems. . . . . . . . . . 105
8 Administering Traffic Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.1 Traffic Views architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.1.1 Traffic Views Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.1.2 Traffic Views Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
8.1.2.1 Admin process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118.1.2.2 UI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5/22/2018 Pdn 98904754
6/176
6 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805806352d9
8.1.2.3 Counter Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.1.2.4 TrafViewsService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.1.3 Traffic Views Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.1.4 Traffic Views Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138.1.4.1 Basic solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
8.1.4.2 Dual level solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
8.1.5 Traffic Views graph definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
8.1.5.1 Predefined graphs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
8.1.5.2 Importing Traffica workspace graph definitions . . . . . . . . . . . . . . . . . . 118
8.2 Configuring Traffic Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
8.2.1 Configuring Traffic Views when NAT is used . . . . . . . . . . . . . . . . . . . . 120
8.2.2 Configuring Default Colors for graphs. . . . . . . . . . . . . . . . . . . . . . . . . . 122
8.3 Traffic Views system monitoring and optimising . . . . . . . . . . . . . . . . . . 122
8.3.1 Checking the number of used licenses. . . . . . . . . . . . . . . . . . . . . . . . . 122
8.3.2 Traffic Views system internal alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 122
8.3.3 Traffic Views log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.3.4 Using startup parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
9 Administering KPI Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.1 KPI Export overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.2 Architecture, functionality and configuration files . . . . . . . . . . . . . . . . . 125
9.3 Using KPI Export Config Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.3.1 Installing and starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.3.2 KPI Export Config Tool User Interface . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.3.3 Managing KPI Export configuration files. . . . . . . . . . . . . . . . . . . . . . . . 127
9.4 Configuring KPI Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1289.4.1 Taking KPI Export into use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
9.4.1.1 Activating CCMA configuration in TNESs. . . . . . . . . . . . . . . . . . . . . . . 128
9.4.1.2 Configuring data destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
9.4.1.3 Defining the NetActObjectInstanceID parameter for elements . . . . . . . 129
9.4.2 Customising KPI Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.4.2.1 Using other data sources than the default . . . . . . . . . . . . . . . . . . . . . . 130
9.4.2.2 Configuring CCMA Open Nodes in TNESs. . . . . . . . . . . . . . . . . . . . . . 131
9.4.2.3 Filtering of KPIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
10 Administering Symantec Crit ical System Protection. . . . . . . . . . . . . . . 133
10.1 Symantec Critical System Protection architecture . . . . . . . . . . . . . . . . 13310.2 Installing Symantec Critical System Protection. . . . . . . . . . . . . . . . . . . 134
10.2.1 Planning the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
10.2.1.1 Symantec Critical System Protection system requirements . . . . . . . . . 134
10.2.2 Installing SCSP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
10.2.3 Installing SCSP Management Console. . . . . . . . . . . . . . . . . . . . . . . . . 135
10.2.4 Installing SCSP Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
10.3 Configuring Symantec Critical System Protection . . . . . . . . . . . . . . . . 136
10.3.1 SCSP Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
10.3.1.1 Login to SCSP Management Console . . . . . . . . . . . . . . . . . . . . . . . . . 136
10.3.1.2 Master View of SCSP Management Console . . . . . . . . . . . . . . . . . . . . 137
10.3.1.3 Prevention view of SCSP Management Console . . . . . . . . . . . . . . . . . 138
5/22/2018 Pdn 98904754
7/176
P-DN98904754
Issue 6-2
7
Administering Traffica
Id:0900d805806352d9
10.3.2 Gathering information from Traffica environment . . . . . . . . . . . . . . . . 138
10.3.3 Decrypting and importing policy rule sets . . . . . . . . . . . . . . . . . . . . . . 139
10.3.4 Creating a common policy rule set. . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
10.3.4.1 Disable Prevention option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14010.3.4.2 Allow all users to override the policy option. . . . . . . . . . . . . . . . . . . . . 140
10.3.4.3 Copying and renaming policy rule sets . . . . . . . . . . . . . . . . . . . . . . . . 140
10.3.5 Configuring Traffica policy rule set for TS . . . . . . . . . . . . . . . . . . . . . . 141
10.3.5.1 Installed Traffica Components menu . . . . . . . . . . . . . . . . . . . . . . . . . . 141
10.3.5.2 Installed Clients menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
10.3.5.3 IP Address Configurations menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
10.3.5.4 Other Possible Connections menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
10.3.5.5 External Drives menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
10.3.6 Configuring Traffica policy rule set for TNES. . . . . . . . . . . . . . . . . . . . 144
10.3.6.1 Installed Traffica components menu . . . . . . . . . . . . . . . . . . . . . . . . . . 144
10.3.6.2 Installed Clients menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
10.3.6.3 IP Address Configurations menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
10.3.6.4 Other Possible Connections menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
10.3.6.5 External Drives menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
10.3.7 Modifying ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
10.3.8 Applying the policy to the SCSP Agent . . . . . . . . . . . . . . . . . . . . . . . . 147
10.3.9 Monitoring logs from SCSP Management Console . . . . . . . . . . . . . . . 147
10.3.10 Making backups of policy rule sets . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
10.4 Changes to the SCSP environment and uninstallation . . . . . . . . . . . . 149
10.4.1 SCSP Server IP address changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
10.4.2 TS or TNES IP address changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
10.4.3 Uninstalling SCSP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
10.4.4 Uninstalling SCSP Management Console . . . . . . . . . . . . . . . . . . . . . . 150
10.4.5 Uninstalling SCSP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
10.5 Options groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
11 Administering Traffica at Customer Care. . . . . . . . . . . . . . . . . . . . . . . 158
11.1 Traffica at Customer Care System. . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
11.1.1 Basic Architecture of Traffica at Customer Care . . . . . . . . . . . . . . . . . 158
11.1.2 TCC Server Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
11.2 Managing the TCC Database Server. . . . . . . . . . . . . . . . . . . . . . . . . . 160
11.2.1 Managing TrafCCLoader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
11.2.1.1 Configuring TrafCCLoader registry entries . . . . . . . . . . . . . . . . . . . . . 161
11.2.1.2 Managing TrafCCLoader bd.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
11.2.1.3 Managing TrafCCLoader server configuration file . . . . . . . . . . . . . . . . 164
11.2.1.4 Configuring TrafCCLoader alarm sending to NetAct . . . . . . . . . . . . . . 165
11.2.2 Managing Traffica File Server (TrafFS) . . . . . . . . . . . . . . . . . . . . . . . . 166
11.2.2.1 Managing TrafFS registry parameters . . . . . . . . . . . . . . . . . . . . . . . . . 166
11.2.2.2 Managing File Server settings configuration . . . . . . . . . . . . . . . . . . . . 166
11.2.2.3 Managing FTP users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
11.2.3 TCC DB server error logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
11.3 Managing the TCC Mediator Server . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.3.1 Configuring TCC Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 16811.3.2 Creating new TCC users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5/22/2018 Pdn 98904754
8/176
8 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805806352d9
11.3.3 Modifying CCD Mapping Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.3.4 TCC Mediator server error log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.4 Managing the TCC Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
11.4.1 Configuring TCC Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16911.4.2 Managing TCC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
11.4.2.1 Removing adaptation specific use cases . . . . . . . . . . . . . . . . . . . . . . . 169
11.4.3 TCC web server error log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
12 Virus Scanner Configuration Principles . . . . . . . . . . . . . . . . . . . . . . . . 172
12.1 Configuration Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5/22/2018 Pdn 98904754
9/176
P-DN98904754
Issue 6-2
9
Administering Traffica
Id:0900d805806352d9
List of FiguresFigure 1 Traffic News architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 2 Database Export architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 3 Registry Entries for TNES groups and data transfer settings. . . . . . . . . 79
Figure 4 The relation between the data file and the metadata file . . . . . . . . . . . . 82
Figure 5 Traffic Views subsystem context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 6 Interfaces between Traffic Views Client and Traffica Tier 2. . . . . . . . . 113
Figure 7 Basic solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 8 Basic solution with oneTraffic Views User Extension Server. . . . . . . . 114
Figure 9 Dual level solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Figure 10 Adding Traffic Views Extension Server . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 11 TNES groups of predefined graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 12 TNESs split into regional groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 13 Example of network structure when NAT is used . . . . . . . . . . . . . . . . 120Figure 14 Rows in the color ranges table with colors configured. . . . . . . . . . . . . 122
Figure 15 KPI Export architecture and configuration files . . . . . . . . . . . . . . . . . . 126
Figure 16 Architecture of Symantec Critical System Protection environment . . . 133
Figure 17 SCSP Management Console view. . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Figure 18 Monitor's log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 19 Basic Traffica at Customer Care architecture . . . . . . . . . . . . . . . . . . . 160
5/22/2018 Pdn 98904754
10/176
10 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805806352d9
List of TablesTable 1 Traffica terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 2 Traffica abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 3 DCN graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 4 Traffica system log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 5 Traffica internal alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 6 Entries in the ad_internal.ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 7 Traffic Views, Database Export, and File Transfer internal alarms . . . . 34
Table 8 Traffica Database Manager internal alarms . . . . . . . . . . . . . . . . . . . . . . 35
Table 9 Traffica Database Manager internal alarms . . . . . . . . . . . . . . . . . . . . . . 35
Table 10 Data source information as presented in the Solid.ini file. . . . . . . . . . . . 54
Table 11 The recommended cache sizes for current active insert and old active in-
sert (second youngest) Solid databases . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 12 Entries in the ccd.ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Table 13 Traffic News Mediator and QEP log files . . . . . . . . . . . . . . . . . . . . . . . . 61
Table 14 Application server log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Table 15 Traffic News Mediator and QEP configuration files . . . . . . . . . . . . . . . . 62
Table 16 Application server configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Table 17 Registry entries for TrafTomcatService . . . . . . . . . . . . . . . . . . . . . . . . . 64
Table 18 Entries in the TNWConfig.properties file . . . . . . . . . . . . . . . . . . . . . . . . 65
Table 19 Entries in the Trafnewsserver.ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Table 20 Traffic Simulator configuration and log files . . . . . . . . . . . . . . . . . . . . . . 74
Table 21 Entries in the tsinternal.ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 22 Estimates of the exported data file sizes from one TNES . . . . . . . . . . . 78
Table 23 Possible data formats in the DBE data file . . . . . . . . . . . . . . . . . . . . . . . 81
Table 24 Settings dialog check boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 25 HKEY_LOCAL_MACHINE\SOFTWARE\Nokia Siemens Networks\
TrafCus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Table 26 Values for the Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Nokia
Siemens Networks\TrafCumCcdInsert . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Table 27 Example of TNES specific ccd.ini files . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Table 28 File transfer protocols supported by Traffica File Transfer Service . . . . 91
Table 29 Registry entries for Traffica File Transfer Service . . . . . . . . . . . . . . . . . 92
Table 30 Traffica File Transfer Service log files . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Table 31 Traffica user levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Table 32 Managing services on Windows 2003 operating systems . . . . . . . . . . 106
Table 33 Communication table for Traffic Views Client . . . . . . . . . . . . . . . . . . . 113
Table 34 Traffic Views log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Table 35 KPI Export log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Table 36 Installed Traffica Components options group . . . . . . . . . . . . . . . . . . . 151
Table 37 Installed Clients options group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Table 38 IP Address Configurations options group . . . . . . . . . . . . . . . . . . . . . . 153
Table 39 Other Possible Connections options group . . . . . . . . . . . . . . . . . . . . . 155
Table 40 External Drives options group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5/22/2018 Pdn 98904754
11/176
P-DN98904754
Issue 6-2
11
Administering Traffica About this document
Id:0900d805807da473
1 About this documentThis document describes the tasks the system administrator needs to carry out to
ensure that Traffica remains functional at all times. All information in this document
relates to Traffica release Z5.2.
The information presented in this document and that in Traffica Principles complement
each other. Certain tasks that are not strictly system administrator related, such as,
monitoring the network and defining new counters and alarms are explained in Traffica
Principlesand RTT Server Help.
This document does not instruct how to administer the probe system in the Traffica for
Probes environment. For more information on the probe system, see the probe vendors
system administration document.
1.1 What you need to know first
This document assumes that you are familiar with the following:
The Windows operating system
Traffica basics
1.1.1 Administering Traffica in Windows 64bit operating systems
Registry paths mentioned in this document refer to Windows 32bit operating system. If
you are using Windows 64bit operating system, you can find some registry paths under
the Wow6432Noderegistry key.
For example:
The registry path HKEY_LOCAL_MACHINE\SOFTWARE\Nokia Siemens Networksis
mentioned in this document.
In Windows 64bit operating system the corresponding registry path is located in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Nokia Siemens Networksin
the registry.
Also the process names mentioned in this document refer to Windows 32bitoperating
system. If you are using Windows 64bitoperating system, there is a *32postfix in
Traffica process names listed in the Windows Task Manager.
For example:
The process name Traffica.exeis mentioned in this document. In Windows 64bit
operating system the corresponding process name is Traffica.exe *32.
1.2 Terms
The following table presents the most important Traffica terms and concepts used in this
document. If a term does not appear in this section, see Glossary.
http://pdn98904742.pdf/http://pdn98904742.pdf/http://general_glossary.pdf/http://general_glossary.pdf/http://pdn98904742.pdf/http://pdn98904742.pdf/5/22/2018 Pdn 98904754
12/176
12 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805807da473
About this document
Concept Description
CCMA (Clear Code Matrix) A tree structure which consists of nodes and counters, and
functions as a data storage for the counter values post-processed from RTTs.
When an RTT arrives, the CCMA is scanned through and
the counters are updated.
For more information on the CCMA, refer to Clear Code
Matrixin Traffica Principlesand RTT Server Help.
For detailed information on the predefined CCMA, refer to
the relevant Traffica Reference Guide.
CUS Traffica Configuration and User Server. TS SW compo-
nent which is used to store Traffica's configuration infor-
mation.
Database A data storage for all RTTs in the TNES. The database is
automatically cleaned up and oldest data is deleted.
Database capacity depends on the size of the hard disk
and the volume of network traffic.
To access the database, use Traffic News.
For more information, see chapter Managing Traffica
databases.
Data Destination Destination where the generated measurements are send.
Normally Net Act PM Pipe.
Database Export Mediator
(DBEM)
A mediator service that runs on the TS level. The DBEM
connects and controls all the defined DBEPs on the
TNESs.
Database Export Process
(DBEP)
An exporting process on a TNES. A DBEP is controlled by
the DBEM.
Data source The origin of the information that Traffica receives. A data
source is typically a network element or probe system.
When RTTs are redirected from a TNES to a TS, the
TNES is a data source for the TS.
DBM Traffica Database Manager. DBM is a software compo-
nent running on every TS and TNES. DBM manages the
Traffica databases used by different Traffica components,
such as RTT Server and CUS. For more information, see
chapter Managing Traffica databases.
FTS Traffica File Transfer Service. TS/TNES SW componentthat provides automatic transferring of files to a remote
server.
IDS, Internal Data Structure Traffica forwards an RTT report as such into Trafficas
IDS. Once the RTT report data is in the IDS, the fields in
the report are mapped with the corresponding IDS fields.
Traffica uses the data in the RTT reports, which are in the
IDS, for updating the CCMA. Traffica stores the reports
from the IDS into the database. For more information on
the IDS, refer to the relevant Traffica Reference Guide.
Table 1 Traffica terms
http://pdn98904742.pdf/http://pdn98904742.pdf/http://pdn98904742.pdf/http://pdn98904742.pdf/5/22/2018 Pdn 98904754
13/176
P-DN98904754
Issue 6-2
13
Administering Traffica About this document
Id:0900d805807da473
IDS field An IDS field is mapped with a corresponding field in an
RTT report. Consequently, the contents of an IDS field are
identical with the contents of an RTT report field.
Lower Traffica A Traffica that is lower in the hierarchy. A TNES is a lower
Traffica for a TS.
Measurement Collection of KPIs from certain time period
Network Element (NE) A general term, used for all NEs that Traffica can be con-
nected to, for example, Mobile Switching Centre (MSC),
Fixed Switching Centre (FSC) or Serving GPRS Support
Node (SGSN).
Policy rule set Collection of rules that governs process and users access
resources.
Probe system A system that can collect signalling information from
various network interfaces and pass its predefined contentas RTT reports to Traffica TNES.
Registry Windows registry
RTT (Real-time Traffic)
report
RTT reports is a general term used for the real-time traffic
reports that are generated by NEs and issued to the con-
nected TNES. The term also includes redirected RTT
reports that are transferred from a TNES to a TS.
An RTT report can contain, for example, the following
information:
Call start and end time
Cause why the call ended
Clear code A and B subscribers identities
Incoming and outgoing CGR, PCM and TSL
In the GSM networks, the RTT report contains alsothe mobile identities (IMEI), the dialled digits,
incoming and outgoing BSC, LAC, and the cell.
RTT Server A software component that runs on every TNES and
possibly on TS. Consists of RTT Server and databases,
which are managed by DBM. Responsible for collecting,
storing and analysing RTT reports.
SCSP Agent Each Symantec Critical System Protection Agent enforces
policy rules.
SCSP Manager Symantec Critical System Protections manager which
keeps up the connection to SQL database for policies and
manages SCSP Agents.
SQL Database Database which stores the policy rule sets.
SCSP Management
Console
The Management Console lets you manage policies and
SCSP Agents, and perform basic administrative tasks,
such as adding users and restricting the functions that
they can access.
Concept Description
Table 1 Traffica terms (Cont.)
5/22/2018 Pdn 98904754
14/176
14 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805807da473
About this document
1.3 Abbreviations
The following table lists most of the Traffica-specific abbreviations used in this docu-
ment. If an abbreviation does not appear in this section, see Glossary.
SCSP Server Consists of SCSP Manager and SQL database. The
SCSP Server stores policies in a centralised location. The
server coordinates policy distribution, and manages SCSPAgent event logging and reporting.
Traffic News client A tool that can be used for database queries and can be
installed into an office PC.
When the term Traffic News client is used, it refers to both
the Java and the web client. If there are differences, it is
mentioned separately.
Traffic News Mediator A process running on a TS. The Mediator handles the
Traffic News configuration and mediates queries and
results between QEPs and clients.
Traffic News Query Execu-
tion Process (QEP)
A process running on each TNES. The QEP executes
queries to the Traffica databases.
Traffic News web client A lighter, web-based version of the Traffic News client.
Traffica Client PC/workstation that has the required runtime environment
for running Traffica client applications, such as Traffic
News or Traffic Views.
Traffica for Probes (TFP) Traffica for Probes solution enables Traffica application
and content usage in multivendor and multitechnology
networks. The solution uses probe systems, which
capture signalling events in real time from different inter-
faces in 2G, GPRS and 3G networks.
Traffica Network Element
Server (TNES)
A TNES is the Traffica that is connected to an NE.
TNESs receive the RTT reports and these reports are
stored into the Traffica database.
Traffica Server (TS) A central point in the Traffica system, which is connected
to all TNESs. Acts as a server for Traffica clients.
Upper Traffica A Traffica that is higher in the hierarchy. For example, a
TS is an upper Traffica for a TNES.
Workspace A workspace is a set of configuration files which define
how the TNES/TS works. The configuration files are read
when Traffica is started (in other words, the workspace is
opened). They can be divided into *.conf files, which are
predefined and *.ini files, which contain user specific infor-
mation.
A workspace contains, for example, definitions for
predefined CCMA and graphs
user defined CCMA, graphs and alarms
RTT report structures and identification rules
database tables and indexes
Concept Description
Table 1 Traffica terms (Cont.)
http://general_glossary.pdf/http://general_glossary.pdf/5/22/2018 Pdn 98904754
15/176
P-DN98904754
Issue 6-2
15
Administering Traffica About this document
Id:0900d805807da473
Abbreviation Explanation
AH Alarms function
CCMA Clear Code Matrix
CCMAH Clear Code Matrix function
CUS Traffica Configuration and User Server
DBEM Database Export Mediator
DBEP Database Export Process
DBH Database function
DBM Traffica Database Manager
DME Data Mediation Engine
DRH Data Redirector function
FTP File Transfer Protocol
FTS Traffica File Transfer Service
IDS Internal Data Structure
KPI Key Performance Indicator
MS KPI Export Measurement Server
MSC DX MSC
NE Network Element
OMeS Open Measurement Standard
PM Performance ManagementQEP (Traffic News) Query Execution Process
RCH Remote Communications function
REDI Real-time Graphs function
RTT (report) Real-time Traffic (report)
SFTP Secure File Transfer Protocol
SGSN Serving GPRS support node
SMB Secure File Transfer Protocol
SRT Summary Report Tool (for GSM adaptation only))
SSH Secure Shell
TFP Traffica for Probes
TCC Traffica at Customer Care
TNES Traffica Network Element Server
TS Traffica Server
UI User Interface
Table 2 Traffica abbreviations
5/22/2018 Pdn 98904754
16/176
16 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805807da473
Change information
2 Change informationThis chapter lists changes in this document between releases.
Changes in Z5.2
The information on default maximum database size, the number of database files,
as well as the postindex reserve values in the DBM registry entries have been cor-
rected in this document as follows:
Maximum number of database files = 20
Default maximum database size = 40 gigabytes
Postindex reserve value = 6144 bytes
For more information, see Managing Traffica databases.
There is a new licensed feature, High Performance Data Insertion. For more infor-
mation on using this feature, see chapter Managing RTT Server performance.
Added section Managing services on Windows 2008 / Windows 2008 R2 operating
system
Changes in Z5.1
Change in Traffic Simulator installation path for 64-bit machines
In 64-bit Windows machines, the Traffic Simulator installation path might be C:\
Program Files (x86)\Nokia Siemens Networks\Traffica\TrafficSim
instead of the default C:\Program Files\Nokia Siemens Networks\Traffica\
TrafficSim. This information has been added to section Configuration and log files.
Negative values in ccd.ini
You can now add negative values in ccd.ini. For more information, see Modifying
mapping files
Changes in Z5
Changes related to database management:
In Z5, Traffica Database Manager (DBM) takes care of managing Traffica data-
bases. RTT Server and CUS connect to DBM in order to acquire and access their
databases. The Query Execution Process (QEP), Database Export Process (DBEP)
and Summary Report Tool also connect to DBM to use databases in their queries.
For more information, see chapter Managing Traffica databases.
The following sections have been updated related to Traffica database manage-
ment:
System Managementhas been updated.
Table Traffica system log fileshas been updated with Database Manager log
files.
Traffica Database Manager internal alarmshas been added.
Managing Traffica databaseshas been updated.
Default database configurationhas been updated.
Managing Traffica Database Manager overload controlhas been added.
Managing Traffica database switchovershas been updated.
Managing maximum database sizehas been completely rewritten.
Managing unsupported database userhas been updated.
Managing database cache sizeshas been updated.
Managing automatic database deletionhas been updated.
5/22/2018 Pdn 98904754
17/176
P-DN98904754
Issue 6-2
17
Administering Traffica Change information
Id:0900d805807da473
Default CUS database configurationhas been added.
Configuring CUS database backuphas been updated.
Managing database exporthas been updated.
Maintaining history databaseshas been updated. Taking backups to tape drivehas been renamed to Taking backups to an
external driveand updated.
Restoring backup files from tapehas been renamed to Restoring backup files
from an external driveand completely rewritten.
Table Symantec critical system protection / options groups: \RTT Server\Traffica
Database Manager has been added.
In Z5, user management is handled in a centralized manner with Traffica Admin
Tool. The Traffica User Manager application has been removed in Z5. The following
sections have been updated related to centralized user management:
The table Traffic News Mediator and QEP log filesin section Log fileshas been
updated. The tableApplication server log filesin section Log fileshas been updated.
The table Traffic News Mediator and QEP configuration filesin section Configu-
ration fileshas been updated.
The tableApplication server configuration filesin section Configuration fileshas
been updated.
Managing connections between Mediator and QEPhas been updated.
Managing time formats and settings in Traffic Newshas been updated.
Managing query reason codeshas been updated.
Configuring source databases in Traffic Newshas been updated.
Importing Traffic News users to CUShas been removed.
Taking backups of Traffic News configurationhas been removed.
Managing Traffic News usershas been updated.
Traffica User Managerhas been removed because Traffica User Manager is no
longer used for user management.
Updating workspace user rightshas been updated, as this procedure is now
carried out with Traffica Admin Tool.
The procedure To update workspace users remotelyhas been removed.
Remote update of users is no longer needed or possible, as the users.inifile
is computer specific.
Section Using Traffica databases in Traffic Simulatorhas been added, as it is
now possible to generate new RTT Server Database passwords with TrafficaAdmin Tool. Therefore it may be necessary to export and import the password
history file when Traffica databases need to be used in Traffic Simulator.
The section Taking authorised connections into user between TS and TNEShas
been renamed asAuthorised connections between TS and TNESand rewritten,
because authorised connections are now checked based on element topology from
CUS.
Instructions for removing an unused adaptation have been added to section
Managing TCC configuration.
5/22/2018 Pdn 98904754
18/176
18 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805807da473
Change information
In the Database Export Admin Client, you can now configure scripts that will run on
a TNES group. For more information, seeCreating a script in Managing Database
Export Admin Client.
Summary Report Tool is now included in the Client installation. ChapterAdminister-ing Symantec Critical System Protectionhas been updated with changes in options
groups and menu items related to Summary Report Tool. For more information, see
tables Installed Traffica Components options group, Installed Clients options group
and IP Address Configurations options group.
A note on using "\n" to insert line breaks into the Traffic News Client update infor-
mation when editing the TrafNewsUpdateInfo.ini file has been added in table
Traffic News Mediator and QEP configuration files.
5/22/2018 Pdn 98904754
19/176
P-DN98904754
Issue 6-2
19
Administering Traffica System availability assurance
Id:0900d805807da473
3 System availability assuranceTrafficas system availability aims to ensure the reliability of the system. This chapter
describes what you need to observe in order to achieve a reliable system.
3.1 Monitoring TSs and TNESs
3.1.1 Monitoring the hardware
You can use HP Insight Manager for monitoring the physical state of the device. With
the HP Insight Manager you can see, for example, if the hard disk and memory function
properly and if there are processor faults.
HP Insight Manager can be used from the TS, and with it you can see the hardware
status of the TNESs.
To open HP Insight Manager
1 Click Start Programs Insight Manager HP Insight Manager.
3.1.2 Monitoring the software
This chapter gives information about how to check that Traffica functions properly.
TNESs
In the TNESs it is vital that the Status bar shows "Connection OK". Only then does
Traffica collect RTT reports. If the connection is lost, an internal alarm is generated. If
the connection to the data source is not OK, check the possible causes listed in chapterConnection to data source lostin the Troubleshooting Trafficadocument.
Memory consumption
Use the Task Manager to monitor the memory consumption caused by a Traffica
process. To open the Task Manager, press CTRL + ALT + DEL and click Task
Manager.
The consumption of memory depends on the size of both the CCMA and the network.
Excessive memory consumption may be caused by, for example, too broad a CCMA.
Excessive memory consumption makes the watchdog restart Traffica. You can monitor
the memory usage of the CCMA in werlogTrafficaSystemStatus.log . Open the
log file in a text editor and find the string CCMA Memory Usage.
For instructions on how to configure an alarm for exceptional memory consumption, see
Configuring internal alarms.
Internal alarms
Internal alarms in all Trafficas can be centralised into one TS and studied there. It is also
possible to forward internal alarms to NetAct Monitor.
Processor load
High processor load may be caused by an excessive number of incoming reports or the
fact that another application consumes all processor time. If there is not enough proces-
sor time available for Traffica, the size of Traffica queues increase, which in turn
consumes memory capacity.
http://pdn01170224.pdf/http://pdn01170224.pdf/5/22/2018 Pdn 98904754
20/176
20 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805807da473
System availability assurance
Use the Task Manager to monitor the processor load caused by a Traffica process. To
open the Task Manager, press CTRL + ALT + DEL and click Task Manager.
3.1.3 Monitoring Traffica DCNTraffica system administrator should check regularly from the DCN (Data Communica-
tions Network) graphs that the DCN bandwidth is sufficient for Traffica usage.
In every DCN graph, the title shows first the average value for the reports presented in
that particular graph. Then the title specifies the data shown in the graph and, finally,
gives the time span during which the data is received.
The following table presents the DCN graphs.
Row Explanation
1st row: NE reports
received
These graphs show the number of reports Traffica has
received from the network element it is connected to, that is,its data source.
1. The first graph shows the number of reports per second
for the last three minutes.
2. The second graph shows the number of reports per
minute for the last hour.
3. The third graph shows the number of reports per hour for
the last 24 hours.
2nd row: TCP/IP data
received
These graphs show how many kilobits or kilobytes of data
Traffica has received through the TCP/IP connection. The
TCP/IP protocol is used in the connection to Traffic Simula-
tor and NE traffic.
1. The first graph shows the kilobits per second for the last
three minutes.
2. The second graph shows the kilobytes per minute for the
last hour.
3. The third graph shows the kilobytes per hour for the last
24 hours.
3rd row: ISO TP4 data
received
These graphs show how many kilobits or kilobytes of data
Traffica has received through the ISO TP4 connection.
1. The first graph shows the kilobits per second for the last
three minutes.
2. The second graph shows the kilobytes per minute for the
last hour.
3. The third graph shows the kilobytes per hour for the last
24 hours.
Table 3 DCN graphs
5/22/2018 Pdn 98904754
21/176
P-DN98904754
Issue 6-2
21
Administering Traffica System availability assurance
Id:0900d805807da473
gTraffica DCN graphs do not contain the bandwidth usage of Traffic News, TrafficViews, Database Export or KPI export.
4th row: UDP/IP data
received
These graphs show how many kilobits or kilobytes of data
Traffica has received through the UDP/IP connection. The
UDP/IP protocol is used in the Traffica (TNES and TS) andNE interworking: for example, in remote graphs, alarm for-
warding, redirecting of reports from TNES to TS, and file
transfers. Notice that these graphs show only the amount of
data received, and there is a separate set of graphs for the
sent data.
1. The first graph shows the kilobits per second for the last
three minutes.
2. The second graph shows the kilobytes per minute for the
last hour.
3. The third graph shows the kilobytes per hour for the last
24 hours.
5th row: UDP/IP data sent These graphs show how many kilobits or kilobytes of dataTraffica has sent through the UDP/IP connection. The
UDP/IP protocol is used in the Traffica (TNES and TS) inter-
working: for example, in remote graphs, alarm forwarding,
redirecting of reports from TNES to TS, and file transfers.
Notice that these graphs show only the amount of data sent,
and there is a separate set of graphs for the received data.
1. The first graph shows the kilobits per second for the last
three minutes.
2. The second graph shows the kilobytes per minute for the
last hour.
3. The third graph shows kilobytes per hour for the last 24
hours.
Row Explanation
Table 3 DCN graphs (Cont.)
5/22/2018 Pdn 98904754
22/176
22 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805807da473
System management
4 System managementThis chapter describes system management tasks for Traffica Database Manager, Traf-
fica, Traffic News, Traffic Simulator and Database Export. For information on system
management of Traffic Views, see Administering Traffic Views.
4.1 Traffica system log files
The following table presents the Traffica systems log files.
Name Explanation
werlogTrafCUS.log This log file contains administrator and error messages related
to CUS.
werlogTrafCUSDebug.log CUS debug messages. This log is used for troubleshooting.
werlogTrafCUSStatistic.log CUS statistics related messages, for example information onlicense reservation and release.
werlogTrafDBMAdmin.log TrafDBM administrat ive messages, for example switchover
and backup events and client login events.
werlogTrafDBMError.log TrafDBM error messages.
werlogTrafDBMStatistics.log TrafDBM statistics related messages, for example database
server performance parameters and Traffica Active Insert
database size calculation.
werlogTrafDBMDebug.log TrafDBM debug messages. This log is used for troubleshoot-
ing, and it is not written by default. File writing is enabled by
setting the registry entry HKEY_LOCAL_MACHINE\
SOFTWARE\Nokia Siemens Networks\TrafDBM\Traceto value '1' and restarting TrafDBM
werlogTrafficaAdmin.log The administrative information log for RTT Server.See Trou-
bleshooting Traffica, Appendix Entries in WerlogTrafficaAd-
min.log.
werlogTrafficaAlarm.log All the Traffica alarms and how to cancel them.
werlogTrafficaCCMAIfSubscrip-
tions.log
Contains information on counter subscriptions, subscribers
and subscription cancellations made to the CCMA interface.
Also, reasons for possible subscription failures can be found
from the log.
werlogTrafficaCCMAIf.log Contains general information on CCMA interface functionality:
possible error situations and their causes, subscriber connec-tions/disconnects etc.
werlogTrafficaError.log Errors in the Traffica application.
werlogTrafRepAsmAdmin.log Administrat ive events in the TrafRepAsm.exeprocess.
werlogTrafRepAsmError.log Errors in the TrafRepAsm.exeprocess. These errors are
related to the MSC connection.
werlogTrafRepAsmSystemStatus.log This file contains the status information for the
TrafRepAsm.exeprocess.
Table 4 Traffica system log files
http://pdn01170224.pdf/http://pdn01170224.pdf/http://pdn01170224.pdf/http://pdn01170224.pdf/5/22/2018 Pdn 98904754
23/176
P-DN98904754
Issue 6-2
23
Administering Traffica System management
Id:0900d805807da473
4.2 Modifying the registry remotely
In Windows the registry can be modified remotely with Registry Editor. You can start the
Registry Editor by clicking Start Runand entering regeditinto the dialog box.
4.3 Managing TNES-TS connections
When managing the TNES-TS connections, you should regularly check the DCN
graphs. For more information, see Monitoring Traffica DCN.
For more information on the security aspects between the TS and TNESs, see Autho-
rised connections between TS and TNES, and Encrypting messages.
4.3.1 Adjusting the message transfer rateIt is possible to adjust the maximum message transfer rate. One reason for adjusting the
message transfer rate is to make sure that the message transfer rate is not bigger than
the bandwidth available for the TNES-TS connection. Another reason for adjusting the
message transfer rate is to keep the additional network load caused by Trafficas on an
appropriate level.
To adjust the message transfer rate
1 Click Definitions Remote Communications General...The General Interworking Definitions dialog opens.
2 In the Definitions pane, select Maximum message transfer rate, and clickProperties...
The Max. Message Transfer Rate Properties dialog opens.
The optimal combination for message lengths and the number of messages sent in
a second depends on the network. You can see the total network load in the
Maximum message transfer rate box. Make your definitions and click OK.
3 In the General Interworking Definitions dialog, click Save.Check the internal alarms in the TS to find out if there are problems in the TNES-TS con-
nection. If there are problems, adjust the message transfer rate in the TNESs. For
instructions on how to adjust the message transfer rate remotely, see Managing Traffica
workspaces remotely.
werlogTrafficaSystemStatus.log The system status information (reported every 15 minutes).
See Troubleshooting Traffica, Appendix Entries in WerlogTraf-
ficaSystemStatus.log every 15 minutes.
werlogTrafficaUsage.log The usage of graph sets in the Traffica application.
Every time the user changes a graph set, it is noted in this file.
This file lists the history of the used graph sets.
werlogTraWatch.log The log for TraWatch.exe. In this log you can see entries if
Watchdog has restarted any other Traffica processes due to
unexpected errors or jamming.
Name Explanation
Table 4 Traffica system log files (Cont.)
http://pdn01170224.pdf/http://pdn01170224.pdf/http://pdn01170224.pdf/http://pdn01170224.pdf/5/22/2018 Pdn 98904754
24/176
24 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805807da473
System management
DCN graphs help you to observe how Traffica loads the network. Usually, starting
Traffica and restarting CCMA cause a peak in the network load. To open the DCN
graphs, click View DCN Graphs.
4.3.2 Compressing messages
Traffica remote communication and file transfer messages can be compressed. It is rec-
ommended that these messages are compressed because then Traffica requires less
network bandwidth. Redirected reports cannot be compressed.
In new installations, compression is used by default.
To compress messages:
1 Click Definitions General...The General Definitions dialog opens.
2 Select Compression, and click Properties...The Compression Properties dialog opens.
3 Select Compress remote communication messages and transferred filesandclick OK.
4 In the General Definitions dialog, click Saveand Close.
4.4 Managing Traffica workspaces remotely
It is possible to transfer files between Trafficas. You can use remote transfer for the fol-
lowing purposes to transfer workspaces or definition files. This chapter describes how
you can manage TNES workspaces remotely in a TS and how you take workspacebackups.
4.4.1 Managing workspace definitions
It is recommended that you concentrate the updating of Traffica workspace definitions
in a TS. When you want to modify a whole TNES workspace, you should have the work-
space in the TS. When you have modified the lower level workspace definitions in the
upper level, transfer the modifications back to the TNES.
If the CCMA is the same in all the TNESs, and you need a new counter in the CCMA,
transfer the workspace from any of the TNESs, and modify the CCMA definitions in the
upper level. When you have finished the modifications, transfer the new CCMA defini-tion file to every TNES and activate the file.
However, you should notice that if a TNES user has changed the definitions in the lower
level, these changes are lost when the new definition file is transferred from the upper
level. For this reason, it is recommended that TNES users do not have rights to create
or modify workspace definitions.
All the menu commands given in the following examples are carried out in a TS. For
details, see RTT Server Help.
4.4.1.1 Creating a new workspace in TS for TNESs
In a TS, you can create a new workspace which can then be transferred simultaneouslyto several TNESs. To transfer the new workspace, click Remote Transfer
5/22/2018 Pdn 98904754
25/176
P-DN98904754
Issue 6-2
25
Administering Traffica System management
Id:0900d805807da473
Workspaces...Store each workspace in its own directory. If there is no directory for the
new workspace in a TNES, this function creates a directory for it in the TNES and trans-
fers all workspace files into that directory.
When you have transferred the same workspace to several TNESs, in each of theseTNESs, you have to update the definitions of the data source (rds.ini), the lower
Traffica definitions (rcd.ini), and the data redirector definitions (drd.ini). As an
example, updating rds.inimakes it possible for the TNESs to contact their own
network elements. To update the definitions of the data source, lower Traffica definitions
and the data redirector definitions, click Remote Transfer Definitions...If the TS does not have any of these lower level definition files in store, you can transfer
them to the TS from each TNES separately. To transfer the lower level definition files to
the upper level, click Remote Transfer Workspaces...To take the new workspace into use in a TNES, click Remote Switch Workspace...
gWhen the workspaces are switched, the CCMA, and the alarms and graphs arereset.
4.4.1.2 Transferring and activating TNES definitions from TS
You can transfer a TNES workspace into a directory in the TS and modify the TNES def-
initions in the upper level. To transfer a TNES workspace to the upper level, click
Remote Transfer Workspaces...When you have transferred the workspace, you can open it in the TS and modify the def-
initions. When you want to transfer the workspace back to the TNES, there are two
possible ways to do so. One is recommended if there are many major changes and the
other if the changes are small.
Major changes in the definitions
If you have made several major changes, the easiest way to transfer the new workspace
definitions back to the TNES is the following. To transfer the workspace files back to the
lower level, click Remote Transfer Workspaces...To take the new workspace intouse in the TNES, click Remote Switch Workspace. In the Switch Remote Work-space dialog, remember to deselect the Save currently active workspacecheck box,
which is selected by default. Notice that switching the workspace clears the current
counters in the memory, and that is why it is recommended that you activate the modi-
fications just before the CCMA is automatically reset.
Minor changes in the definitions
If it is important that the CCMA data is not lost, and the changes are small and concern
mainly the alarm or graph definitions, it is recommended that you transfer the new work-
space definitions back to the lower level differently. The assumption is that you are mod-
ifying a workspace which is currently running in a TNES. Before the transfer, you should
stop the threads which use the modified definitions in the TNES or Trafficas. Notice that
the threads have to be stopped and started separately for each TNES. To stop the
function states, click Definitions Function States...To transfer the modified files tothe TNES, click Remote Transfer Definitions...To take the new definitions into useand to restart the threads, click Definitions Function States...
5/22/2018 Pdn 98904754
26/176
26 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805807da473
System management
4.5 Internal alarms
This chapter describes the internal alarms and how to configure them in Traffica.
You can edit all Traffica internal alarms in the ad_internal.inifile.
The following table describes the internal alarms. In this table the term Traffica server is
used in a general sense, and it can refer to either a Traffica Server (TS) or a server in
the TNES.
Alarm name Number Severity Description
Connection
Lost
19800 Major The connection between Traffica and its data source
has been lost. Traffica cannot receive data from the data
source, which means that all data sent by the data
source, for example MSC, is lost.
The reason for the lost connection can be, for example,
a network failure, or a data source failure (MSC failure).
Check the physical connection. If the connection is OK,
check that TNES is up and running.
This alarm is automatically cancelled when the connec-
tion is re-established.
No Connection 19801 Info Connection to the data source is manually terminated,
for example, when you disconnect the data source
manually from the user interface (Actions Connect...).
Connection
OK
19802 Info Connection to the data source is established manually,
for example, when you connect to a data source
manually from the user interface (Actions Connect...).
Lower Traffica
Connection
Lost
19803 Info Connection to a TNES is lost. The name of the TNES is
given in the alarms description field. A possible cause is
a network failure.
Lower Traffica
Connection
Re-established
19804 Info Connection to a TNES is established. This can occur
when the network connection is up and running again
after a transient network failure. The name of the TNES
is given in the description field of the alarm.
Workspace
shutdown
19805 Info Traffica workspace is closed. This alarm is generated
before the closing takes place. It is forwarded to upper
Trafficas, where it is possible to observe that a Traffica
workspace has been closed in a TNES.
Workspace
startup
19806 Info Traffica workspace has been started. This alarm is gen-
erated when a workspace is started. It is forwarded to
upper Trafficas, where you can see that a Traffica work-
space has been started in a TNES.
Database
function
startup
19807 Info Database function (DBH) has been started. This alarm
is generated when a DBH is started. It is forwarded to
upper Trafficas, where you can see that a DBH has been
started in a TNES.
Database
function
error/shutdown
19808 Info Database function (DBH) has stopped. Possible causes
are unrecoverable errors or a manual stopping of the
DBH function. This alarm indicates that the database
servers are running but no reports are inserted into the
Traffica Active Insert database.
Table 5 Traffica internal alarms
5/22/2018 Pdn 98904754
27/176
P-DN98904754
Issue 6-2
27
Administering Traffica System management
Id:0900d805807da473
Low virtual
memory
19809 Major The amount of free virtual memory in a Traffica server is
less than the configured limit. The reason for the low
virtual memory can be that the CCMA configuration istoo large and complex, or that there is too much data
coming in (it is buffered into the memory), or that there
are unnecessary processes running on a Traffica server.
Check that the number of incoming reports is below the
limit given in the capacity statement. Check that there
are no other memory consuming processes running on
the Traffica server than Traffica.exeand
solid.exe. Check that the CCMA memory usage is
not too high.
Low hard disk
space on drive
C
19810 Major There is less than the configured limit of free hard disk
space in a Traffica server logical drive C.
Remove all unnecessary files from the hard disk drive C.
In a Traffica server, the hard disk drive C should be
reserved only for the operating system and Traffica soft-
ware.
This alarm is cancelled when there is more free disk
space than the configured limit.
Low hard disk
space on drive
D
19811 Major There is less than the configured limit of free hard disk
space in a Traffica server logical drive D.
Remove all unnecessary files from the hard disk drive D.
In a Traffica server, hard disk drive D should be reserved
only for the Traffica databases. The Traffica system
automatically deletes the oldest database files if the disk
space is not sufficient. However, copying other files to
the hard disk drive D can disturb this functionality.
This alarm is cancelled when there is more free disk
space than the configured limit.
High database
server load
19813 Minor Traffica server receives more reports than it can insert
into the database. For this reason reports are stored in
an internal queue in the memory. This alarm can be
caused by an exceptionally high number of database
queries but it should be active only temporarily.
Check that the requirements given in the capacity state-
ment are met. Check that no other than Traffica pro-
cesses are accessing the Traffica database.
When this alarm is triggered, Traffic News performs
normally the queries that have already been started.
However, new queries are not started until the alarm is
cancelled.
This alarm is cancelled when the internal alarm queue is
smaller than the configured limit.
Alarm name Number Severity Description
Table 5 Traffica internal alarms (Cont.)
5/22/2018 Pdn 98904754
28/176
28 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805807da473
System management
Very high
database
server load
19814 Major Traffica server receives more reports than it can insert
into the database. For this reason, reports are stored in
an internal queue in the memory. This alarm can becaused by an exceptionally high number of database
queries but it should be active only temporarily.
Check that the requirements given in the capacity state-
ment are met. Check that no other than Traffica pro-
cesses are accessing the Traffica database.
When this alarm is triggered, Traffic News cancels the
queries that have already been started. Also, new
queries are not started until both the Very high database
server load and the High database server load alarms
have been cancelled.
This alarm is cancelled when the internal alarm queue is
smaller than the configured limit.
Critically high
database
server load
19815 Critical Traff ica server receives more reports than it can insert
into the database. For this reason, reports are stored in
an internal queue in the memory.
Check that the requirements given in the capacity state-
ment are met. Check that no other than Traffica pro-
cesses are accessing the Traffica database.
Database
backup
function
startup
19816 Info Database backup function (DBBH) is started. This alarm
can be forwarded to upper Trafficas, where you can see
that a DBBH has been started in a TNES.
Database
backupfunction
error/shutdown
19817 Info Database backup function (DBBH) is stopped. Possible
causes are unrecoverable errors or manual stopping ofthe DBBH function. This alarm indicates that no reports
are inserted into the Traffica database, and the data-
bases are not available for Traffic News queries.
High CCMA
memory usage
19818 Minor The CCMA in a Traffica server consumes more memory
than expected.
Check that the requirements given in the capacity state-
ment are met. If the number of reports is not the
problem, remove some unnecessary CCMA time
classes or CCMA members.
This alarm is cancelled when the size of the CCMA is
smaller than the configured limit.
Very highCCMA
memory usage
19819 Major The CCMA in a Traffica server consumes more memorythan expected.
Check that the requirements given in the capacity state-
ment are met. If the number of reports is not the
problem, remove some unnecessary CCMA time
classes or CCMA members.
This alarm is cancelled when the size of the CCMA is
smaller than the configured limit.
Alarm name Number Severity Description
Table 5 Traffica internal alarms (Cont.)
5/22/2018 Pdn 98904754
29/176
P-DN98904754
Issue 6-2
29
Administering Traffica System management
Id:0900d805807da473
Low physical
memory
19820 Major There is less than the configured limit of free physical
memory in a Traffica server. The reason for the low
physical memory can be that the CCMA configuration istoo big and complex, or that there is too much data
coming in (it is buffered into the memory), or that there
are unnecessary processes running on a Traffica server.
Check that the requirements given in the capacity state-
ment are met. Check that there are no other memory
consuming processes running on the Traffica server
than Traffica.exeand solid.exe. Check that the
CCMA memory usage is not too high.
Traffica auto-
matic restart
due to reboot
or unexpected
error
19821 Minor The Traffica.exeprocess has been successfully
automatically restarted. This is due to the system reboot
or an unexpected error. You can see if the system was
rebooted from Windows Event Viewer. The reboot can
be done manually or it can be caused by a break in theelectricity distribution. If there has not been a reboot, the
reason for the alarm is an unexpected error and
Traffica.exewas restarted by the TraWatch.exesupervision process.
Database
function termi-
nated due to
error
19822 Major Database function (DBH) was terminated because of an
error. DBH must be manually restarted. You can see the
error in werlogTrafficaError.log.
Database and
database
backup func-
tions termi-nated due to
error
19823 Major Database backup function (DBBH) was terminated to an
error. DBBH must be manually restarted. You can see
the error in werlogTrafficaError.log.
Traffica
manual restart
19824 Info The Traffica.exeprocess was manually restarted by
a user.
Database
backup
function error
19825 Minor There has been an error in the Database backup
function (DBBH). You should check the error from
werlogTrafficaError.logor the Traffica user
interface.
CUS connec-
tion lost
19827 Minor Connection from TNES or TS to Traffica Configuration
and User Server (CUS) has been lost.
Open node
definition error
19826 Minor Reading open node definition(s) from
open_node_ccma*.inifile has failed and all open
nodes are not working correctly. For more details about
the error, see werlogTrafficaError.log.
Expiring
license
19828 Minor License contains an expiring adaptation license entry
and should be renewed. Alarm is given when there is 20
days or less left until the license expires.
DBM connec-
tion lost
19829 Major Connection to Traffica Database Manager has been
lost. RTT Server will continue to insert data into the data-
base. Database switch overs cannot happen until this
connection is restored.
Alarm name Number Severity Description
Table 5 Traffica internal alarms (Cont.)
5/22/2018 Pdn 98904754
30/176
30 P-DN98904754
Issue 6-2
Administering Traffica
Id:0900d805807da473
System management
4.5.1 Configuring internal alarms
The Traffica system administrator can use internal alarms for ensuring that the Traffica
system remains stable and reliable, and for deriving general information about the status
of the system, for example, about overload.
Every TS and TNES is an individual case and they have to be configured separately.
Traffica internal alarms are configured in the ad_internal.ini file. Traffica reads the
ad_internal.ini file once an hour, and your changes to the alarm configurations are
then automatically used. You can edit the ad_internal.inifile in a text editor, for
example, Notepad.
RTT Export
function
startup
19870 Info The RTT Export function was started. This alarm informs
the user if the startup functions as expected.
RTT Export
function
shutdown
19871 Info The RTT Export function was shut down.
RTT Export
function error
19872 Minor The Traffica RTT Export function was stopped due to an
error and data received from a network element cannot
be exported. If the function has been running success-
fully for the previous 15 minutes, Traffica tries to restart
the function. If the restart succeeds the alarm is can-
celled.
If the function has been running for a shorter time, it is
not restarted and the alarm stays active. The function
can be restarted manually when the error has been cor-rected.
RTT Export job
error
19873 Major Traffica RTT Export job is stopped due to an error and
data received from a network element cannot be
exported for the job.
If for example the target directory is deleted, Traffica
triggers this alarm. Traffica tries to start the failed jobs at
each file update. If
Recommended