ConfigurationAndManagement DIPM30 RevC

System Release 3.
DIMETRA™
Dimetra IP Micro (DIPM)
CONFIGURATION AND
MANAGEMENT
April 2014
*68015000619*
68015000619-C
© 2014 Motorola Solutions, Inc. All rights reserved

3 | Copyrights
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs. Laws in
the United States and other countries preserve for Motorola certain exclusive rights for copyrighted computer
programs. Accordingly, any copyrighted Motorola computer programs contained in the Motorola products described
in this document may not be copied or reproduced in any manner without the express written permission of Motorola.
© 2014 Motorola Solutions, Inc. All Rights Reserved
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any language
or computer language, in any form or by any means, without the prior written permission of Motorola Solutions, Inc.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication,
estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the
normal non-exclusive, royalty-free license to use that arises by operation of law in the sale of a product.
Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be applicable to or
licensed for use on a particular system, or may be dependent upon the characteristics of a particular mobile subscriber
unit or configuration of certain parameters. Please refer to your Motorola contact for further information.
Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered
trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the property
of their respective owners.
European Union (EU) Waste of Electrical and Electronic Equipment (WEEE)

directive
The European Union's WEEE directive requires that products sold into EU countries must have the crossed out
trash bin label on the product (or the package in some cases).
As defined by the WEEE directive, this cross-out trash bin label means that customers and end-users in EU countries
should not dispose of electronic and electrical equipment or accessories in household waste.
Customers or end-users in EU countries should contact their local equipment supplier representative or service centre
for information about the waste collection system in their country.
68015000619-C | April 2014 | Send Feedback

5 | CMM Labeling and Disclosure Table
CMM Labeling and Disclosure Table

The People’s Republic of China requires that our products comply with China Management Methods (CMM)
environmental regulations. (China Management Methods refers to the Regulation Management Methods for
Controlling Pollution by Electronic Information Products.) Two items are used to demonstrate compliance; the Label
and the Disclosure Table.
The label is placed in a customer visible position on the product. The first of the following examples means that the
product contains no hazardous substances; the second means that the product contains hazardous substances, and has
an Environmental Friendly Use Period (EFUP) of fifty years.
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic and Hazardous
Substances (T&HS) contained in the Electronic Information Product (EIP) will not leak or mutate causing
environmental pollution, or bodily injury from the use of the EIP.
The Disclosure Table, printed in simplified Chinese, is included with each customer order. An example of a
Disclosure Table (in Chinese) follows:

7 | Service Information
Service Information
Government Technical Support (GTS), EA Solutions Support Centre
The Government Technical Support (GTS), EA Solutions Support Centre provides a remote Technical Support
Service to help customers resolve technical issues and quickly restore networks and systems. This team of highly
skilled professionals is available to customers with current service agreements in place that include the Technical
Support Service. The EA GTS technical experts may be accessed through the EMEA Integrated Call Center either
electronically or using the telephone numbers listed below. If you are unsure whether your current service agreement
entitles you to benefit from this service, or if you would like more information about the Technical Support Service,
contact your local customer support or account manager for further information.
Contact Details
Email: essc@motorolasolutions.com
Table 1: List of Telephone Numbers
Country In Country Number to Dial

AUSTRIA 01206091087
DENMARK 043682114
FRANCE 0157323434
GERMANY 06950070204
ITALY 0291483230
LITHUANIA 880 030 828
NETHERLANDS 0202061404
NORWAY 24159815
PORTUGAL 0217616160
RUSSIA 810 800 228 41044
(Alternative 810 800 120 1011)
SAUDI ARABIA 800 844 5345
SOUTH AFRICA 0800981900
SPAIN 0912754787
UNITED KINGDOM 02030 277499
All Other Countries +44 2030 277499
European Systems Component Centre (ESCC)

The European Systems Component Centre provides a repair service for infrastructure equipment. Customers requiring
repair service should contact the Customer Information Desk to obtain a Return Material Authorization number. The
equipment should then be shipped to the following address unless advised otherwise.
Motorola GmbH, European Systems Component Centre, Am Borsigturm 130,13507 Berlin, Germany
Contact Details
• E-Mail: escc.admin@motorolasolutions.com
• Telephone: +49 (0) 30 66861404

8 | Service Information
• Telefax: +49 (0) 30 66861426

• Monday – Friday 08:00 am to 06:00 pm (CET)
Parts Identification and Ordering

Request for help in identification of non-referenced spare parts should be directed to the Customer Care Organization
of Motorola’s local area representation. Orders for replacement parts, kits, and assemblies should be placed directly
on Motorola’s local distribution organization or through the Extranet site Motorola Online at https://
emeaonline.motorolasolutions.com.
Updated Versions of Manuals

Verify the current version of the manual at our Extranet site, Motorola Online: https://
emeaonline.motorolasolutions.com.
Your Input
Send questions and comments regarding user documentation to documentation@motorolasolutions.com
We welcome your feedback on this and other Motorola manuals. To take a short, confidential survey on Motorola
Customer Documentation, go to docsurvey.motorolasolutions.com or scan the following QR code with your mobile
device to access the survey.
Send Feedback | April 2014 | 68015000619-C

9 | Document History
Document History
Edition Description Date
68015000619-A Initial Version May 2012
68015000619-B Important note added to Configuration Examples on page 200. July 2012
68015000619-C Information about CAD User object amended in Advanced NM – Apr. 2014
User Configuration Manager (UCM) on page 581

Contents | 11
Contents
Copyrights........................................................................................................................................ 3
CMM Labeling and Disclosure Table............................................................................................5
Service Information......................................................................................................................... 7
Document History............................................................................................................................ 9
List of Figures................................................................................................................................ 17
List of Tables.................................................................................................................................. 23
List of Processes............................................................................................................................. 31
List of Procedures.......................................................................................................................... 33
About Configuration and Management.......................................................................................37
What Is Covered In This Manual?...................................................................................................................... 37
Helpful Background Information........................................................................................................................ 37
Related Information.............................................................................................................................................37
Icon Conventions........................................................................................................................... 39
Style Conventions...........................................................................................................................41
Chapter 1: Description.......................................................................................... 43
Starting Up the Web NM.....................................................................................................................................43
Web NM Main Window Structure...................................................................................................................... 44
Chapter 2: Operation.............................................................................................45
Status Management............................................................................................................................................. 45
Monitoring the State and Cause of System Alarms................................................................................ 46
Identifying and Troubleshooting the State and Cause.............................................................................47
Downloading the Events......................................................................................................................... 48
Configuration Management.................................................................................................................................49
Configuring a Radio User Capabilities Profile........................................................................................49
Creating a Radio User Capabilities Profile................................................................................. 50
Editing the Settings of the Radio User Capabilities Profile........................................................ 51
Deleting the Radio User Capabilities Profile.............................................................................. 52
Configuring a Radio User........................................................................................................................52
Adding a Radio User to the System............................................................................................ 53
Editing the Settings of a Radio User........................................................................................... 54
Deleting a Radio User................................................................................................................. 56
Configuring a Radio User Interconnect Profile.......................................................................................57
Creating a Radio User Interconnect Profile................................................................................ 58
Editing the Setting of a Radio User Interconnect Profile............................................................58
Deleting Radio User Interconnect Profile................................................................................... 59
Configuring a TG/MG Capabilities Profile.............................................................................................60
Creating a TG/MG Capabilities Profile.......................................................................................60
Editing the Settings of a TG/MG Capabilities Profile................................................................ 61
Deleting a TG/MG Capabilities Profile.......................................................................................62
Configuring a Talkgroup......................................................................................................................... 62
Creating a Talkgroup...................................................................................................................63
Editing the Settings of a Talkgroup.............................................................................................63
Deleting a Talkgroup...................................................................................................................64
Adding/Removing a Talkgroup from a Multigroup.................................................................... 65
Configuring a Multigroup....................................................................................................................... 65
Creating a Multigroup................................................................................................................. 66
Editing the Parameters of a Multigroup...................................................................................... 67
12 | Contents
Deleting a Multigroup................................................................................................................. 68
Configuring a Dispatch Application........................................................................................................69
Creating a Dispatch Application................................................................................................. 69
Editing the Settings of a Dispatch Application........................................................................... 71
Deleting a Dispatch Application Record.....................................................................................72
Configuring Logging Interface Application ...........................................................................................72
Creating a Logging Interface Application Record...................................................................... 73
Editing the Settings of a Logging Interface Application Record................................................ 74
Deleting the Logging Interface Application Record................................................................... 75
Configuring a Console User.................................................................................................................... 75
Creating a Console User..............................................................................................................76
Editing the Settings of a Console User........................................................................................77
Deleting a Console User..............................................................................................................77
Configuring Status Sets........................................................................................................................... 78
Editing the Status Set Messages..................................................................................................78
Configuring Short Data Router Services.................................................................................................80
Enabling the Short Data Router Services.................................................................................... 81
Configuring an MTS Site........................................................................................................................ 82
Creating an MTS Site.................................................................................................................. 83
Editing the Settings of an MTS Site............................................................................................83
Deleting an MTS Site.................................................................................................................. 85
Changing the State of an MTS Site............................................................................................. 85
Configuring a Conventional Channel Gateway.......................................................................................86
Creating a Conventional Channel Gateway................................................................................ 86
Editing the Settings of a Conventional Channel Gateway.......................................................... 87
Deleting the Conventional Channel Gateway............................................................................. 88
Configuring a Telephone Interconnect....................................................................................................88
Creating a Telephone Interconnect Record................................................................................. 89
Editing the Settings of the Telephone Interconnect.................................................................... 90
Deleting a Telephone Interconnect Record................................................................................. 91
Configuring a System..............................................................................................................................92
Configuring a System Optimization Parameters..................................................................................... 93
Configuring Group Calls......................................................................................................................... 95
Configuring Short Data Services.............................................................................................................96
Configuring Ambience Listening............................................................................................................97
Enabling Radio Users for Ambience Listening...........................................................................97
Enabling Console Users for Ambience Listening....................................................................... 97
Configuring Full Duplex Private Calls....................................................................................................98
Enabling Radio Users for Full Duplex Private Calls.................................................................. 99
Configuring Preemptive Priority Calls....................................................................................................99
Setting Priority Levels.................................................................................................................99
Enabling a Talkgroup/Multigroup for PPC............................................................................... 100
Enabling a Radio User Capabilities Profile for PPC.................................................................100
Configuring Status Transfer Service..................................................................................................... 101
Common Secondary Control Channel (C-SCCH) Configuration......................................................... 101
Configuring Common Secondary Control Channel (C-SCCH)............................................................ 102
Configuring Authentication and Air Interface Encryption ...................................................................103
Configuring Packet Data....................................................................................................................... 105
Administration Management.............................................................................................................................106
Performing Backup and Restore............................................................................................................106
Backup.......................................................................................................................................106
Restore.......................................................................................................................................108
Accessing the Servers............................................................................................................................110
Accessing the SunFire X4170 Server........................................................................................110
Accessing the ProLiant DL360 G7 Server................................................................................ 113
Changing the Password......................................................................................................................... 116
Contents | 13
Performing Software Update.................................................................................................................117

Uploading and Updating the Software...................................................................................... 117
Downloading the Software Update Files...................................................................................119
Deleting the Software Files....................................................................................................... 120
Managing Network Configuration Files................................................................................................120
Downloading the Network Configuration Files........................................................................ 121
Applying the Configuration for a Local/Remote Site............................................................... 122
Deleting the Network Configuration Files................................................................................ 123
Downloading ATIA Logs......................................................................................................................124
Enabling the ATIA Call Logging for SunFire X4170 via the ATR Server.............................. 124
Enabling the ATIA Call Logging for ProLiant DL360G7 via the ATR Server........................127
Downloading ATIA Log Files.................................................................................................. 131
Collecting and Downloading Server Log Files..................................................................................... 132
Performing Diagnostics.........................................................................................................................133
Downloading Support Files from the Server.........................................................................................134
Web Network Manager Version............................................................................................................135
Chapter 3: Reference........................................................................................... 137

Status Page........................................................................................................................................................ 137
Current Status........................................................................................................................................ 138
All Events Object.................................................................................................................................. 139
Alarm Severity Levels...........................................................................................................................140
Configuration Page............................................................................................................................................141
Radio User Object................................................................................................................................. 141
Radio User Capabilities Profile.............................................................................................................145
Radio User Interconnect Profile............................................................................................................ 148
Talkgroup Object...................................................................................................................................150
Multigroup Object................................................................................................................................. 152
TG/MG Capabilities Profile.................................................................................................................. 155
Dispatch Application Object................................................................................................................. 157
Logging Interface Application Object...................................................................................................161
Console User Object..............................................................................................................................164
Status Set Object................................................................................................................................... 166
Short Data Router Object...................................................................................................................... 169
MTS Site Object....................................................................................................................................170
Conventional Channel Gateway Object................................................................................................ 174
Telephone Interconnect Object............................................................................................................. 178
System Object........................................................................................................................................182
System Optimization Object................................................................................................................. 185
Administration Page.......................................................................................................................................... 187
Backup and Restore...............................................................................................................................187
Server Connection................................................................................................................................. 189
Change Password.................................................................................................................................. 190
Software Update.................................................................................................................................... 191
Network Configuration..........................................................................................................................192
ATIA Logs............................................................................................................................................ 194
Collect Log Files................................................................................................................................... 195
Diagnostics............................................................................................................................................ 196
Downloads.............................................................................................................................................198
About..................................................................................................................................................... 198
Appendix A: Network Configuration File Guidelines...................................... 199

Introduction....................................................................................................................................................... 199
Configuration Examples....................................................................................................................................200
14 | Contents
Minimal Configuration for Local MTS Only........................................................................................200

Layer 2 Point-to-Multipoint without Border Router and with MTS Connectivity............................... 202
Layer 2 Point-to-Multipoint with Border Router and MTS Connectivity.............................................204
Layer 2 Point-to-Point without Border Router and with MTS Connectivity........................................ 206
Layer 2 Point-to-Point with Border Router and MTS Connectivity..................................................... 208
Layer 3 MTS Connectivity....................................................................................................................210
Configuration Reference................................................................................................................................... 211
Version [Required]................................................................................................................................ 211
Hardware Models [Required]................................................................................................................212
GBN Topology [Required]....................................................................................................................212
RF Sites [Required]............................................................................................................................... 212
VPN Access [Required]........................................................................................................................ 214
CEN Access [Optional]......................................................................................................................... 214
Layer 2 and Layer 3 Topologies with BR................................................................................. 214
Layer 2 Topology without BR...................................................................................................215
CEN APIs [Optional]............................................................................................................................ 215
IP Telephony [Optional]........................................................................................................................216
Layer 2 and Layer 3 Topologies with BR................................................................................. 216
QoS [Optional]...................................................................................................................................... 218
Remote Control Site [Optional]............................................................................................................ 218
Dual Site Link [Optional]......................................................................................................................219
Local Gateway Mode [Optional]...........................................................................................................220
Data [Optional]......................................................................................................................................220
Other [Optional].................................................................................................................................... 221
Other Configuration Tasks Overview............................................................................................................... 221
Ground Based Network (GBN) Gateway(s)......................................................................................... 221
Access Port Settings.............................................................................................................................. 221
Border Router........................................................................................................................................ 223
Motorola Border Configuration.................................................................................................223
Third party (Juniper) Border Configuration..............................................................................225
Third party (HP) Border Configuration.....................................................................................228
Customer Enterprise Network (CEN) Hosts......................................................................................... 229
Appendix B: Alarm Guidelines...........................................................................231

State/Cause Alarm Texts................................................................................................................................... 231
AISA......................................................................................................................................................231
AisaPlatform..........................................................................................................................................237
AisaVoiceCard...................................................................................................................................... 242
ATR....................................................................................................................................................... 245
AtrZcLink..............................................................................................................................................249
AuC....................................................................................................................................................... 250
AudioRP................................................................................................................................................ 253
Ccgw......................................................................................................................................................256
CcgwZcCp.............................................................................................................................................261
CnsRouterSiteManagerLink..................................................................................................................263
CnsSwitchSiteManagerLink..................................................................................................................266
Conventional Channel........................................................................................................................... 269
DispatchApplication..............................................................................................................................270
DispatchPlatform...................................................................................................................................276
DispatchVoiceCard............................................................................................................................... 281
GasFan...................................................................................................................................................285
GasHardDisk......................................................................................................................................... 287
Contents | 15
GasPowerSupply................................................................................................................................... 289
GasTemperature.................................................................................................................................... 291
GasVoltage............................................................................................................................................ 293
GpioModule...........................................................................................................................................295
Mtig....................................................................................................................................................... 298
MtigPort................................................................................................................................................ 300
MtsAtccBoardInternals......................................................................................................................... 302
MtsAtccSignalMeasurements................................................................................................................306
MtsBaseRadio....................................................................................................................................... 316
MtsBrBoardInternals............................................................................................................................. 324
MtsBrDataPorts..................................................................................................................................... 338
MtsBrReceivePathandInterference........................................................................................................349
MtsBrTransmitPath............................................................................................................................... 360
MtsDpmBoardInternals......................................................................................................................... 370
MtsDpmSignalMeasurements............................................................................................................... 374
MtsExternalAlarms............................................................................................................................... 384
MtsFanKit..............................................................................................................................................393
MtsOutputSignals..................................................................................................................................397
MtsPowerSupplyUnit............................................................................................................................ 402
MtsScBoardInternals............................................................................................................................. 418
MtsScDataPorts..................................................................................................................................... 423
MtsScSiteReference.............................................................................................................................. 428
MtsSite.................................................................................................................................................. 435
MtsSscBoardInternals........................................................................................................................... 441
MtsSscSiteReference.............................................................................................................................446
pdgPDR................................................................................................................................................. 453
pdgPDRGGSNLink...............................................................................................................................456
pdgPDRRNG.........................................................................................................................................458
pdgPDRRNGCommunication............................................................................................................... 460
pdgPDRRNGLink................................................................................................................................. 463
pdgPDRRNGSiteLink........................................................................................................................... 465
pdgPDRRNGZCLink............................................................................................................................ 467
pdgPDRZCLink.................................................................................................................................... 469
SDR....................................................................................................................................................... 472
SDRRFSiteLink.................................................................................................................................... 473
SDRMStoGroup.................................................................................................................................... 481
StoreAndForward.................................................................................................................................. 483
SDR->HLR............................................................................................................................................485
SDR->VLR............................................................................................................................................487
UCS01................................................................................................................................................... 489
ZC1/M................................................................................................................................................... 496
ZC-CCGW CP.......................................................................................................................................503
ZcConsoleSCP...................................................................................................................................... 504
ZcMobilityLink..................................................................................................................................... 509
ZcMtigLink........................................................................................................................................... 511
ZcMtsSite.............................................................................................................................................. 513
ZcOperationalHealth............................................................................................................................. 516
ZDS....................................................................................................................................................... 521
Zone.......................................................................................................................................................528
ZoneContlr.............................................................................................................................................536
Transcient Alarm Texts..................................................................................................................................... 539
Atr..........................................................................................................................................................539
AuC....................................................................................................................................................... 540
Ccgw......................................................................................................................................................542
GasHardDisk......................................................................................................................................... 542
GasVoltage............................................................................................................................................ 542
16 | Contents
Mtig....................................................................................................................................................... 543
MtsBaseRadio....................................................................................................................................... 543
MtsScBoardInternals............................................................................................................................. 544
MtsSite.................................................................................................................................................. 547
MtsSscBoardInternals........................................................................................................................... 548
pdgPDR................................................................................................................................................. 551
pdgPDRRNG.........................................................................................................................................554
pdgPDRRNGLink................................................................................................................................. 554
pdgPDRZCLink.................................................................................................................................... 554
SDR....................................................................................................................................................... 555
SDRRFSiteLink.................................................................................................................................... 566
UCS01................................................................................................................................................... 567
ZcOperationalHealth............................................................................................................................. 570
ZDS....................................................................................................................................................... 570
ZoneController...................................................................................................................................... 573
Appendix C: Advanced NM - Differences Appendix........................................581

Advanced NM – User Configuration Manager (UCM).................................................................................... 581
Advanced NM – Zone Configuration Manager (ZCM).................................................................................... 581
Advanced NM – Radio Control Manager (RCM).............................................................................................582
List of Figures | 17
List of Figures
Figure 1: Login Window ................................................................................................................ 43
Figure 2: Web NM Page ................................................................................................................. 44
Figure 3: Web NM Main Window Elements ..................................................................................44
Figure 4: Example of the Status Page .............................................................................................45
Figure 5: Example of a List of Components of One Element ........................................................ 46
Figure 6: Example of Status Changes of an Object ........................................................................ 47
Figure 7: File Download Dialog Box ............................................................................................. 48
Figure 8: Example of Downloaded Events in the .csv File ............................................................ 49
Figure 9: Configuration Page ..........................................................................................................49
Figure 10: Radio User Capabilities Profile Page ............................................................................ 50
Figure 11: Radio User Capabilities Profile Configuration Page .................................................... 51
Figure 12: Modify Radio User Capabilities Profile Page ............................................................... 51
Figure 13: Search Query Example ..................................................................................................52
Figure 14: Example of a Confirmation Dialog Box ....................................................................... 52
Figure 15: Radio User Page ............................................................................................................ 53
Figure 16: Radio User Configuration Page .................................................................................... 54
Figure 17: Example of an Error Message ....................................................................................... 54
Figure 18: Modify Radio User Page ............................................................................................... 55
Figure 19: Example of a Radio User for Deletion .......................................................................... 56
Figure 20: Confirmation Dialog Box ..............................................................................................57
Figure 21: Radio User Interconnect Profile Page ........................................................................... 57
Figure 22: Radio User Interconnect Profile Configuration Page ....................................................58
Figure 23: Modify Radio User Interconnect Profile Page .............................................................. 59
Figure 24: TG/MG Capabilities Profile Page ................................................................................. 60
Figure 25: TG/MG Capabilities Profile Configuration Page ..........................................................61
Figure 26: Modify TG/MG Capabilities Profile Page .................................................................... 61
Figure 27: Talkgroup Page ............................................................................................................. 62
Figure 28: Organization of Users in a Talkgroup ........................................................................... 63
Figure 29: Talkgroup Configuration Page ...................................................................................... 63
Figure 30: Modify Talkgroup Page ................................................................................................ 64
Figure 31: Multigroup Page ............................................................................................................65
Figure 32: Talkgroups in Multigroups ............................................................................................66
Figure 33: Multigroup Configuration Page .................................................................................... 67
18 | List of Figures
Figure 34: Modify Multigroup Page ...............................................................................................68

Figure 35: Dispatch Application Page ............................................................................................ 69
Figure 36: Dispatch Application Configuration Page .................................................................... 70
Figure 37: Modify Dispatch Application Page ............................................................................... 71
Figure 38: Logging Interface Application Page ............................................................................. 73
Figure 39: Logging Interface Application Configuration Page ...................................................... 74
Figure 40: Modify Logging Interface Application Page ................................................................ 74
Figure 41: Console User Page ........................................................................................................ 76
Figure 42: Console User Configuration Page ................................................................................. 76
Figure 43: Modify Console User Page ........................................................................................... 77
Figure 44: Status Set Page .............................................................................................................. 78
Figure 45: Modify Set Status Page ................................................................................................. 79
Figure 46: Short Data Router Page ................................................................................................. 81
Figure 47: Modify Short Data Router Page .................................................................................... 82
Figure 48: MTS Site Page ...............................................................................................................82
Figure 49: MTS Site Configuration Page ....................................................................................... 83
Figure 50: Modify MTS Site Page ..................................................................................................84
Figure 51: Diagnostics Window ..................................................................................................... 85
Figure 52: Conventional Channel Gateway Page ........................................................................... 86
Figure 53: Conventional Channel Gateway Configuration Page ....................................................87
Figure 54: Modify Conventional Channel Gateway Page .............................................................. 88
Figure 55: Telephone Interconnect Page ........................................................................................ 89
Figure 56: Telephone Interconnect Configuration Page .................................................................90
Figure 57: Modify Telephone Interconnect Page ........................................................................... 91
Figure 58: System Page .................................................................................................................. 92
Figure 59: Modify System Page ..................................................................................................... 93
Figure 60: System Optimization Page ............................................................................................ 94
Figure 61: Modify System Optimization Page ............................................................................... 95
Figure 62: Example of a Full Duplex Call ......................................................................................98
Figure 63: Modify Multigroup Page .............................................................................................100
Figure 64: Modify Radio User Capabilities Profile Page ............................................................. 101
Figure 65: Backup and Restore Configuration Page .................................................................... 107
Figure 66: Backup Command Page .............................................................................................. 107
Figure 69: Restore of the Backup File Command Page ............................................................... 110
Figure 70: Server Connection Page .............................................................................................. 111
Figure 71: Integrated Lights Out Manager Log In Window .........................................................112
Figure 72: Security Alert Window (Example for Internet Explorer) ............................................113
Figure 73: Integrated Lights-Out Log In Window ....................................................................... 114
Figure 74: Integrated Lights-Out Overview Window ...................................................................114
Figure 75: Integrated Lights-Out Remote Console Window ........................................................115
Figure 76: Integrated Lights-Out Licensing Window ...................................................................116
Figure 77: Change Password Page ............................................................................................... 117
Figure 78: Software Update Page ................................................................................................. 117
Figure 80: Upload Page ................................................................................................................ 118
Figure 81: Software Update Command Page ............................................................................... 119
Figure 82: Software Update ..........................................................................................................119
Figure 84: Network Configuration Page .......................................................................................121
Figure 87: Upload Page ................................................................................................................ 122
Figure 88: Network Configuration Command Page ..................................................................... 123
Figure 90: Sun Integrated Lights Out Manager Log In Window ................................................. 125
Figure 91: Security Alert Window (Example for Internet Explorer) ............................................127
Figure 92: Integrated Lights-Out Log In Window ....................................................................... 127
Figure 93: Integrated Lights-Out Overview Window ...................................................................128
Figure 94: Integrated Lights-Out Remote Console Window ........................................................128
Figure 95: HP ProLiant DL360 G7 - iGAS Login ....................................................................... 129
Figure 96: Integrated Lights-Out Licensing Window ...................................................................129
Figure 97: ATIA Logs Page ......................................................................................................... 131
Figure 98: Collect Log File ...........................................................................................................132
Figure 99: Collect Log Files Command Page ...............................................................................132
Figure 100: Diagnostics Page ....................................................................................................... 133
Figure 101: Diagnostics Command Page ..................................................................................... 134
Figure 102: Downloads Page ........................................................................................................134
Figure 103: About Page ................................................................................................................ 135
Figure 104: Status Page ................................................................................................................ 137

Figure 105: Current Status Page ................................................................................................... 138
Figure 106: All Events Page ......................................................................................................... 139
Figure 107: Configuration Page ....................................................................................................141
Figure 108: Radio User Object ..................................................................................................... 141
Figure 109: Radio User Capabilities Profile Page ........................................................................ 145
Figure 110: Radio User Interconnect Profile Page ....................................................................... 148
Figure 111: Talkgroup Page ......................................................................................................... 150
Figure 112: Multigroup Page ........................................................................................................152
Figure 113: TG/MG Capabilities Profile ...................................................................................... 155
Figure 114: Dispatch Application Page ........................................................................................ 157
Figure 115: Logging Interface Application Page ......................................................................... 161
Figure 116: Console User Page .................................................................................................... 164
Figure 117: Status Set Page .......................................................................................................... 166
Figure 118: Modify Status Set Page ............................................................................................. 167
Figure 119: Short data Router Page ..............................................................................................169
Figure 120: MTS Site Page ...........................................................................................................170
Figure 121: Conventional Channel Gateway Page ....................................................................... 174
Figure 122: Telephone Interconnect Page .................................................................................... 178
Figure 123: System Page .............................................................................................................. 182
Figure 124: System Optimization Page ........................................................................................ 185
Figure 125: Administration Page ..................................................................................................187
Figure 126: Backup and Restore Page ..........................................................................................187
Figure 127: Example of the Backup Command Page ...................................................................188
Figure 128: Example of the Restore Command Page ...................................................................189
Figure 129: Server Connection Page ............................................................................................ 189
Figure 130: Change Password Page ............................................................................................. 190
Figure 131: Software Update Page ............................................................................................... 191
Figure 132: Example of the Software Update Command Page .................................................... 192
Figure 133: Network Configuration Page .....................................................................................193
Figure 134: Example of the Network Configuration Command Page ..........................................194
Figure 135: ATIA Logs Page ....................................................................................................... 194
Figure 136: Collect Log Files Page .............................................................................................. 195
Figure 137: Example of the Collect Log Files Command Page ................................................... 196
Figure 138: Diagnostics Page ....................................................................................................... 196
Figure 139: Example of Diagnostics Command Page .................................................................. 197

Figure 140: Download Page ......................................................................................................... 198
Figure 141: About Page ................................................................................................................ 198
Figure 142: Example of Minimal Configuration for Local MTS ................................................. 200
Figure 143: Example of L2 P2M without BR and with MTS Connectivity .................................202
Figure 144: Example of L2 P2M with BR and MTS Connectivity .............................................. 204
Figure 145: Example of L2 P2P without BR and MTS Connectivity .......................................... 206
Figure 146: Example of L2 P2P with BR and MTS Connectivity ............................................... 208
Figure 147: Example of L3 MTS Connectivity ............................................................................ 210
List of Tables | 23
List of Tables
Table 1: List of Telephone Numbers ................................................................................................ 7
Table 2: Example of Alarm Messages ............................................................................................47
Table 3: List of Predefined ISSIs ....................................................................................................80
Table 4: Overview of Group Call Configuration Parameters ......................................................... 96
Table 5: Command Buttons .......................................................................................................... 138
Table 6: Parameters for the Current Status ...................................................................................138
Table 7: Command Buttons .......................................................................................................... 139
Table 8: Severity Levels ............................................................................................................... 140
Table 9: Parameters for the Radio User ........................................................................................142
Table 10: Command Buttons for the Radio User ......................................................................... 144
Table 11: Parameters for the Radio User Capabilities Profile ......................................................146
Table 12: Command Buttons for the Radio User Capabilities Profile ......................................... 147
Table 13: Parameters for the Radio User Interconnect Profile .....................................................148
Table 14: Command Buttons for the Radio User Interconnect Profile .........................................149
Table 15: Parameters for the Talkgroup Object ............................................................................150
Table 16: Command Buttons for a Talkgroup .............................................................................. 151
Table 17: Parameters for the Multigroup Object .......................................................................... 152
Table 18: Command Buttons for the Multigroup ......................................................................... 154
Table 19: Parameters for TG/MG Capabilities Profile .................................................................155
Table 20: Command Buttons for the TG/MG Capabilities Profile ...............................................156
Table 21: Parameters for Dispatch Application ............................................................................157
Table 22: Command Buttons for the Dispatch Application ......................................................... 161
Table 23: Parameters for Logging Interface Application Object ................................................. 162
Table 24: Command Buttons for the Logging Interface Application ...........................................163
Table 25: Parameters for Console User Object ............................................................................ 164
Table 26: Command Buttons for the Console User ......................................................................165
Table 27: Parameters for Status Set Object .................................................................................. 167
Table 28: Command Buttons for the Status Set ............................................................................168
Table 29: Parameters for Short Data router Object ...................................................................... 169
Table 30: Parameters for MTS Site .............................................................................................. 170
Table 31: Command Buttons for the MTS Site ............................................................................ 173
Table 32: Parameters for the Conventional Channel Gateway .....................................................175
Table 33: Command Buttons for the Conventional Channel Gateway ........................................ 177
24 | List of Tables
Table 34: Parameters for the Telephone Interconnect .................................................................. 178

Table 35: Command Buttons for the Telephone Interconnect ......................................................181
Table 36: Parameters for System .................................................................................................. 182
Table 37: Parameters for the System Optimization ...................................................................... 186
Table 38: Command Buttons for Backup and Restore ................................................................. 188
Table 39: Command Buttons of the Backup Command Page and Restore Command Page ........189
Table 40: Parameters for the Password .........................................................................................190
Table 41: Command Buttons for Software Update ...................................................................... 191
Table 42: Command Buttons of the Software Update Command Page ....................................... 192
Table 43: Command Buttons for the Network Configuration Page ............................................. 193
Table 44: Command Buttons for the Network Configuration Command Page ............................194
Table 45: Command Buttons for the ATIA Logs Page ................................................................ 195
Table 46: Command Buttons for the Collect Log Files Page ....................................................... 195
Table 47: Command Buttons for the Collect Log Files Command Page ..................................... 196
Table 48: Command Buttons for the Diagnostics Page ................................................................197
Table 49: Command Buttons for the Diagnostics Command Page .............................................. 197
Table 50: Access Port Settings: Speed/Duplex, 802.1Q Tagging, VLANs ..................................221
Table 51: Explanation of the Source Content of an Alarm Message for the Aisa Object ............ 231
Table 52: State/Cause Text for the AISA Object ......................................................................... 231
Table 53: Explanation of the Source Content of an Alarm Message for the AisaPlatform
Object ....................................................................................................................................... 237
Table 54: State/Cause Text for the AisaPlatform Object ............................................................. 237
Table 55: Explanation of the Source Content of an Alarm Message for the AisaVoiceCard
Object ....................................................................................................................................... 242
Table 56: State/Cause Text for the AisaVoiceCard Object .......................................................... 242
Table 57: Explanation of the Source Content of an Alarm Message for the ATR Object ........... 245
Table 58: State/Cause Text for the Atr Object ............................................................................. 246
Table 59: Explanation of the Source Content of an Alarm Message for the AtrZcLink Object .. 249
Table 60: State/Cause Text for the AtrZcLink Object ..................................................................249
Table 61: Explanation of the Source Content of an Alarm Message for the AuC Object ............251
Table 62: State/Cause Text for the AuC Object ........................................................................... 251
Table 63: Explanation of the Source Content of an Alarm Message for the AudioRP Object .... 253
Table 64: State/Cause Text for the AudioRP Object ....................................................................253
Table 65: Explanation of the Source Content of an Alarm Message for the Ccgw Object .......... 257
Table 66: State/Cause Text for the Ccgw Object ......................................................................... 257
List of Tables | 25
Table 67: Explanation of the Source Content of an Alarm Message for the CcgwZcCp Object . 261
Table 68: State/Cause Text for the CcgwZcCp Object .................................................................262
Table 69: Explanation of the Source Content of an Alarm Message for the
CnsRouterSiteManagerLink Object ......................................................................................... 263
Table 70: State/Cause Text for the CnsRouterSiteManagerLink Object ......................................263
CnsSwitchSiteManagerLink Object .........................................................................................266
Table 72: State/Cause Text for the CnsSwitchSiteManagerLink Object ..................................... 266
ConventionalChannel Object ................................................................................................... 269
Table 74: State/Cause Text for the ConventionalChannel Object ................................................269
DispatchApplication Object ..................................................................................................... 270
Table 76: State/Cause Text for the Dispatch Object .....................................................................271
Table 77: Explanation of the Source Content of an Alarm Message for the DispatchPlatform
Object ....................................................................................................................................... 276
Table 78: State/Cause Text for the DispatchPlatform Object .......................................................277
DispatchVoiceCard Object ...................................................................................................... 281
Table 80: State/Cause Text for the DispatchVoiceCard Object ................................................... 282
Table 81: Explanation of the Source Content of an Alarm Message for the GasFan Object ....... 285
Table 82: State/Cause Text for the GasFan Object .......................................................................285
Table 83: Explanation of the Source Content of an Alarm Message for the GasHardDisk
Object ....................................................................................................................................... 287
Table 84: State/Cause Text for the GasHardDisk Object ............................................................. 287
Table 85: Explanation of the Source Content of an Alarm Message for the GasPowerSupply
Object ....................................................................................................................................... 289
Table 86: State/Cause Text for the GasPowerSupply Object ....................................................... 289
Table 87: Explanation of the Source Content of an Alarm Message for the GasTemperature
Object ....................................................................................................................................... 291
Table 88: State/Cause Text for the GasTemperature Object ........................................................ 291
Table 89: Explanation of the Source Content of an Alarm Message for the GasVoltage Object
...................................................................................................................................................293
Table 90: State/Cause Text for the GasVoltage Object ................................................................293
Table 91: Explanation of the Source Content of an Alarm Message for the GpioModule
Object ....................................................................................................................................... 295
Table 92: State/Cause Text for the GpioModule Object .............................................................. 296
Table 93: Explanation of the Source Content of an Alarm Message for the Mtig Object ............299
26 | List of Tables
Table 94: State/Cause Text for the Mtig Object ........................................................................... 299
Table 95: Explanation of the Source Content of an Alarm Message for the MtigPort Object .....301
Table 96: State/Cause Text for the MtigPort Object .................................................................... 301
MtsAtccBoardInternals Object ................................................................................................ 302
Table 98: State/Cause Text for the MtsAtccBoardInternals Object ............................................. 303
MtsAtccSignalMeasurements Object .......................................................................................306
Table 100: State/Cause Text for the MtsAtccSignal Object .........................................................306
Table 101: Explanation of the Source Content of an Alarm Message for the MtsBaseRadio
Object ....................................................................................................................................... 316
Table 102: State/Cause Text for the MtsBaseRadio Object ......................................................... 316
MtsBrBoardInternals Object .................................................................................................... 324
Table 104: State/Cause Text for the MtsBrBoardInternals Object ...............................................324
Table 105: Explanation of the Source Content of an Alarm Message for the MtsBrDataPorts
Object ....................................................................................................................................... 338
Table 106: State/Cause Text for the MtsBrDataPorts Object .......................................................338
MtsBrReceivePathandInterference Object ...............................................................................349
Table 108: State/Cause Text for the MtsBrRecPathAndInterf Object ......................................... 349
MtsBrTransmitPath Object ...................................................................................................... 361
Table 110: State/Cause Text for the MtsBrTransmitPath Object ................................................. 361
MtsDpmBoardInternals Object ................................................................................................ 370
Table 112: State/Cause Text for the MtsDpmBoardInternals Object ...........................................371
MtsDpmSignalMeasurements Object ...................................................................................... 374
Table 114: State/Cause Text for the MtsDpmSignal Object ........................................................ 375
MtsExternalAlarms Object ...................................................................................................... 384
Table 116: State/Cause Text for the MtsExternalAlarms Object ................................................. 385
Table 117: Explanation of the Source Content of an Alarm Message for the MtsFanKit Object
...................................................................................................................................................393
Table 118: State/Cause Text for the MtsFanKit Object ............................................................... 393
Table 119: Explanation of the Source Content of an Alarm Message for the MtsOutputSignals
Object ....................................................................................................................................... 397
List of Tables | 27
Table 120: State/Cause Text for the MtsOutputSignals Object ....................................................398

MtsPowerSupplyUnit Object ................................................................................................... 402
Table 122: State/Cause Text for the MtsPsu Object .....................................................................402
MtsScBoardInternals Object .................................................................................................... 418
Table 124: State/Cause Text for the MtsScBoardInternals Object ...............................................419
Table 125: Explanation of the Source Content of an Alarm Message for the MtsScDataPorts
Object ....................................................................................................................................... 423
Table 126: State/Cause Text for the MtsScDataPorts Object .......................................................424
MtsScSiteReference Object ..................................................................................................... 428
Table 128: State/Cause Text for the MtsScSiteRef Object ...........................................................428
Table 129: Explanation of the Source Content of an Alarm Message for the MtsSite Object .....435
Table 130: State/Cause Text for the MtsSite Object .................................................................... 435
MtsSscBoardInternals Object .................................................................................................. 441
Table 132: State/Cause Text for the MtsSscBoardInernals Object .............................................. 441
MtsSscSiteReference Object ....................................................................................................446
Table 134: State/Cause Text for the MtsSscSiteRef Object ......................................................... 446
Table 135: Explanation of the Source Content of an Alarm Message for the pdgPDR Object ....453
Table 136: State/Cause Text for the pdgPDR Object ................................................................... 453
pdgPDRGGSNLink Object ......................................................................................................456
Table 138: State/Cause Text for the pdgPDRGGSNLink Object .................................................456
Table 139: Explanation of the Source Content of an Alarm Message for the pdgPDRRNG
Object ....................................................................................................................................... 459
Table 140: State/Cause Text for the pdgPDRRNG Object ...........................................................459
pdgPDRRNGCommunication Object ...................................................................................... 461
Table 142: State/Cause Text for the pdgPDRRNGCommunication Object .................................461
pdgPDRRNGLink Object ........................................................................................................ 463
Table 144: State/Cause Text for the pdgPDRRNGLink Object ................................................... 463
pdgPDRRNGSiteLink Object .................................................................................................. 465
Table 146: State/Cause Text for the pdgPDRRNGSiteLink Object .............................................465
28 | List of Tables
pdgPDRRNGZCLink Object ................................................................................................... 467
Table 148: State/Cause Text for the pdgPDRRNGZCLink Object ..............................................467
Table 149: Explanation of the Source Content of an Alarm Message for the pdgPDRZCLink
Object ....................................................................................................................................... 469
Table 150: State/Cause Text for the pdgPDRZCLink Object ...................................................... 469
Table 151: Explanation of the Source Content of an Alarm Message for the SDR Object ..........472
Table 152: State/Cause Text for the SDR Object ......................................................................... 472
Table 153: Explanation of the Source Content of an Alarm Message for the SRDRFSiteLink
Object ....................................................................................................................................... 474
Table 154: State/Cause Text for the sdrRFLink Object ............................................................... 474
Table 155: Explanation of the Source Content of an Alarm Message for the sdrMStoGroup
Object ....................................................................................................................................... 481
Table 156: State/Cause Text for the sdrMStoGroup Object .........................................................482
Table 157: Explanation of the Source Content of an Alarm Message for the StoreAndForward
Object ....................................................................................................................................... 483
Table 158: State/Cause Text for the sdrStoreAndForward Object ............................................... 483
Table 159: Explanation of the Source Content of an Alarm Message for the SDR->HLR
Object ....................................................................................................................................... 485
Table 160: State/Cause Text for the sdrZCHLRLink Object ....................................................... 485
Table 161: Explanation of the Source Content of an Alarm Message for the SDR->VLR
Object ....................................................................................................................................... 487
Table 162: State/Cause Text for the SDR->VLR Object ............................................................. 487
Table 163: Explanation of the Source Content of an Alarm Message for the UCS01 Object ......489
Table 164: State/Cause Text for the UCS01 Object ..................................................................... 489
Table 165: Explanation of the Source Content of an Alarm Message for the ZC1/M Object ......496
Table 166: State/Cause Text for the ZC1/M Object ..................................................................... 496
Table 167: Explanation of the Source Content of an Alarm Message for the ZC-CCGW CP
Object ....................................................................................................................................... 503
Table 168: State/Cause Text for the ZcCcgwCp Object ...............................................................503
Table 169: Explanation of the Source Content of an Alarm Message for the ZcConsoleSCP
Object ....................................................................................................................................... 504
Table 170: State/Cause Text for the ZcConsoleSCP Object ........................................................ 505
Table 171: Explanation of the Source Content of an Alarm Message for the ZcMobilityLink
Object ....................................................................................................................................... 509
Table 172: State/Cause Text for the ZcMobilityLink Object ....................................................... 510
Table 173: Explanation of the Source Content of an Alarm Message for the ZcMtigLink
Object ....................................................................................................................................... 511
List of Tables | 29
Table 174: State/Cause Text for the ZcMtigLink Object ............................................................. 511
Table 175: Explanation of the Source Content of an Alarm Message for the ZcMtsSite Object .513
Table 176: State/Cause Text for the ZcMtsSite Object ................................................................ 513
ZcOperationalHealth Object .................................................................................................... 516
Table 178: State/Cause Text for the ZcOpState Object ................................................................516
Table 179: Explanation of the Source Content of an Alarm Message for the ZDS Object ..........521
Table 180: State/Cause Text for the ZDS Object ......................................................................... 522
Table 181: Explanation of the Source Content of an Alarm Message for the Zone Object ......... 528
Table 182: State/Cause Text for the Zone Object .........................................................................528
Table 183: Explanation of the Source Content of an Alarm Message for the ZoneContlr
Object ....................................................................................................................................... 536
Table 184: State/Cause Text for the ZoneCntlr Object ................................................................ 536
Table 185: Transient Alarm Text for the Atr Object .................................................................... 540
Table 186: Transient Alarm Text for the AuC Object ..................................................................540
Table 187: Transient Alarm Text for the Ccgw Object ................................................................ 542
Table 188: Transient Alarm Text for the GasHardDisk Object ....................................................542
Table 189: Transient Alarm Text for the GasVoltage Object ...................................................... 542
Table 190: Transient Alarm Text for the Mtig Object ..................................................................543
Table 191: Transient Alarm Text for the MtsBaseRadio Object ..................................................543
Table 192: Transient Alarm Text for the MtsScBoardInternals Object ....................................... 544
Table 193: Transient Alarm Text for the MtsSite Object .............................................................547
Table 194: Transient Alarm Text for the MtsSscBoardInernals Object .......................................548
Table 195: Transient Alarm Text for the pdgPDR Object ............................................................551
Table 196: Transient Alarm Text for the pdgPDRRNG Object ................................................... 554
Table 197: Transient Alarm Text for the pdgPDRRNGLink Object ............................................554
Table 198: Transient Alarm Text for the pdgPDRZCLink Object ...............................................554
Table 199: Transient Alarm Text for the SDR Object ..................................................................555
Table 200: Transient Alarm Text for the SRDRFSiteLink Object ...............................................566
Table 201: Transient Alarm Text for the UCS01 Object ..............................................................567
Table 202: Transient Alarm Text for the ZcOpState Object ........................................................ 570
Table 203: Transient Alarm Text for the ZDS Object ..................................................................570
Table 204: Transient Alarm Text for the ZoneCntlr Object .........................................................573
30 | List of Tables
31 | List of Processes
List of Processes
Configuring a Radio User ............................................................................................................... 52
Configuring Ambience Listening ................................................................................................... 97
Downloading ATIA Logs ............................................................................................................. 124

33 | List of Procedures
List of Procedures
Starting Up the Web NM ................................................................................................................ 43
Downloading the Events .................................................................................................................48
Creating a Radio User Capabilities Profile .....................................................................................50
Editing the Settings of the Radio User Capabilities Profile ........................................................... 51
Deleting the Radio User Capabilities Profile ..................................................................................52
Adding a Radio User to the System ................................................................................................53
Editing the Settings of a Radio User ...............................................................................................54
Deleting a Radio User .....................................................................................................................56
Creating a Radio User Interconnect Profile ....................................................................................58
Editing the Setting of a Radio User Interconnect Profile ............................................................... 58
Deleting Radio User Interconnect Profile .......................................................................................59
Creating a TG/MG Capabilities Profile .......................................................................................... 60
Editing the Settings of a TG/MG Capabilities Profile ....................................................................61
Deleting a TG/MG Capabilities Profile .......................................................................................... 62
Creating a Talkgroup ...................................................................................................................... 63
Editing the Settings of a Talkgroup ................................................................................................ 63
Deleting a Talkgroup ...................................................................................................................... 64
Creating a Multigroup .....................................................................................................................66
Editing the Parameters of a Multigroup ..........................................................................................67
Deleting a Multigroup .....................................................................................................................68
Creating a Dispatch Application .....................................................................................................69
Editing the Settings of a Dispatch Application ...............................................................................71
Deleting a Dispatch Application Record ........................................................................................ 72
Creating a Logging Interface Application Record ..........................................................................73
Editing the Settings of a Logging Interface Application Record ....................................................74
Deleting the Logging Interface Application Record .......................................................................75
Creating a Console User ................................................................................................................. 76
Editing the Settings of a Console User ........................................................................................... 77
Deleting a Console User ................................................................................................................. 77
Editing the Status Set Messages ..................................................................................................... 78
Enabling the Short Data Router Services ....................................................................................... 81
Creating an MTS Site ..................................................................................................................... 83
Editing the Settings of an MTS Site ............................................................................................... 83

34 | List of Procedures
Deleting an MTS Site ..................................................................................................................... 85

Changing the State of an MTS Site ................................................................................................ 85
Creating a Conventional Channel Gateway ....................................................................................86
Editing the Settings of a Conventional Channel Gateway ..............................................................87
Deleting the Conventional Channel Gateway .................................................................................88
Creating a Telephone Interconnect Record .................................................................................... 89
Editing the Settings of the Telephone Interconnect ........................................................................90
Deleting a Telephone Interconnect Record .................................................................................... 91
Configuring a System ..................................................................................................................... 92
Configuring a System Optimization Parameters ............................................................................ 93
Configuring Short Data Services .................................................................................................... 96
Enabling Radio Users for Ambience Listening .............................................................................. 97
Enabling Console Users for Ambience Listening .......................................................................... 97
Enabling Radio Users for Full Duplex Private Calls ......................................................................99
Enabling a Talkgroup/Multigroup for PPC .................................................................................. 100
Enabling a Radio User Capabilities Profile for PPC .................................................................... 100
Configuring Common Secondary Control Channel (C-SCCH) ................................................... 102
Configuring Authentication and Air Interface Encryption ........................................................... 103
Configuring Packet Data ...............................................................................................................105
Backup .......................................................................................................................................... 106
Restore .......................................................................................................................................... 108
Accessing the Servers ................................................................................................................... 110
Accessing the SunFire X4170 Server ........................................................................................... 110
Accessing the ProLiant DL360 G7 Server ................................................................................... 113
Changing the Password .................................................................................................................116
Uploading and Updating the Software ......................................................................................... 117
Downloading the Software Update Files ...................................................................................... 119
Deleting the Software Files .......................................................................................................... 120
Downloading the Network Configuration Files ........................................................................... 121
Applying the Configuration for a Local/Remote Site ...................................................................122
Deleting the Network Configuration Files ................................................................................... 123
Enabling the ATIA Call Logging for SunFire X4170 via the ATR Server ..................................124
Enabling the ATIA Call Logging for ProLiant DL360G7 via the ATR Server ........................... 127
Downloading ATIA Log Files ......................................................................................................131
Collecting and Downloading Server Log Files ............................................................................ 132

List of Procedures | 35
Performing Diagnostics ................................................................................................................ 133

Downloading Support Files from the Server ................................................................................ 134

37 | About Configuration and Management
About Configuration and Management

This Web Network Manager (Web NM) is a web-based application intended for technicians, network management
personnel, or any other engineering personnel with responsibility for managing, administrating and troubleshooting
the Dimetra IP Micro/Dimetra LiTE system. This part covers the use of the Web Network Manager and its
functionality.
What Is Covered In This Manual?

This booklet contains the following chapters:
• Description on page 43. This chapter provides information on starting up the Web NM and includes descriptions
of the window elements within the web interface.
• Operation on page 45. This chapter presents procedures for managing, configuring, and administrating the
Dimetra IP Micro/Dimetra LiTE system.
• Reference on page 137. This chapter provides descriptions of the parameters for the all objects and fields visible
within the Dimetra IP Micro/Dimetra LiTE system Web NM.
Helpful Background Information

Motorola offers various courses designed to assist in learning about the system. For information, go to http://
www.motorolasolutions.com/training to view the current course offerings and technology paths.
Related Information
The following table presents a list of referenced manuals and short descriptions of their contents.
Manual Description
What is Dimetra IP Micro/Dimetra LiTE This one-page leaflet contains a brief description of
the system and its key features.
Documentation Overview This one-page document lists all manuals created for
this release of Dimetra IP Micro/Dimetra LiTE sys-
tem.
Dimetra IP Glossary This booklet lists and explains the acronyms and
terms used throughout Dimetra IP documentation.
System Overview This manual explains radio system concepts and de-
scribes the components used in Dimetra IP Micro/
Dimetra LiTE system. It also provides an overview
of all the features.
Quick Start Guide The Quick Start Guide contains information to sup-
port the initial configuration of the equipment in or-
der to get the system up and running.
Service Manual This manual contains backup and restoration proce-
dures and FRU/FRE information for all the compo-
nents in the system.
Table continued…

38 | About Configuration and Management
Manual Description
User Configuration Manager This manual describes the User Configuration Man-
ager (UCM), which is a Windows-based application
used in the advanced configuration of the system.
Advanced configuration may require both the UCM
and the Zone Configuration Manager (ZCM).
Zone Configuration Manager The ZCM is used in the advanced configuration and
maintenance of operational parameters for equipment
in the system. Advanced configuration may require
both the ZCM and the User Configuration Manager
(UCM).
Radio Control Manager This manual describes the Radio Control Manager
(RCM), which is an application used primarily by
operators to monitor and manage radio events, issue
and monitor commands, and make informational
queries of the system database.
MTS1 Installation, Configuration and Basic Service This manual describes all necessary actions to install,
Manual configure and maintain the Motorola TETRA Station
(MTS1) within the system.
MTS LiTE, MTS2 and MTS4 Installation, Configu- This manual describes all necessary actions to install,
ration and Basic Service Manual configure and maintain the Motorola TETRA Station
(MTS LiTE, MTS2 and MTS4) within the system.
Data Subsystem This manual describes the Data feature and its com-
ponents. It provides necessary information to config-
ure, operate and maintain the equipment and soft-
ware.

39 | Icon Conventions
Icon Conventions
The documentation set is designed to give the reader more visual clues. The following graphic icons are used
throughout the documentation set. These icons and their associated meanings are described below.
Danger: The signal word DANGER with the associated safety icon implies information that, if
disregarded, will result in death or serious injury.
Warning: The signal word WARNING with the associated safety icon implies information that, if
disregarded, could result in death or serious injury, or serious product damage.
Caution: The signal word CAUTION with the associated safety icon implies information that, if
disregarded, may result in minor or moderate injury, or serious product damage.
Caution: The signal word CAUTION may be used without the safety icon to state potential damage or
injury that is not related to the product.
Important: IMPORTANT statements contain information that is crucial to the discussion at hand, but is
not CAUTION or WARNING. There is no warning level associated with the IMPORTANT statement.
Note: NOTE contains information more important than the surrounding text, such as exceptions or
preconditions. They also refer the reader elsewhere for additional information, remind the reader how to
complete an action (when it is not part of the current procedure, for instance), or tell the reader where
something is located on the screen. There is no warning level associated with a note.
Suggestion: SUGGESTION implies a recommendation or tip from Motorola that does not require to be
followed, but might be helpful. There is no warning level associated with SUGGESTION.

41 | Style Conventions
Style Conventions
The following style conventions are used:
Convention Description
Bold This typeface is used for names of, for instance, windows, buttons, and labels when
these names appear on the screen (example: the Alarms Browser window). When
it is clear that we are referring to, for instance, a button, the name is used alone
(example: Click OK).
Monospacing font in This typeface is used for words to be typed in exactly as they are shown in the text
bold (example: In the Address field, type http://ucs01.ucs:9080/).
Monospacing font This typeface is used for messages, prompts, and other text displayed on the com-
puter screen (example: A new trap destination has been added).
<Monospacing font in This typeface is used with angle brackets for words to be substituted by a specific
bold Italic> member of the group that the words represent (example: <router number>).
Note: In sequences to be typed in, the angle brackets are omitted to
avoid confusion as to whether the angle brackets are to be included in
the text to be typed.
CAPITAL LETTERS This typeface is used for keyboard keys (example: Press Y, and then press EN-
TER).
Italic This typeface is used citations. This can be the name of a document or a phrase
from another document (example: Dimetra IP System Overview).
→ An → (arrow pointing right) is used for indicating the menu or tab structure in in-
structions on how to select a certain menu item (example: File → Save) or a cer-
tain sub-tab.

43 | Description
Chapter
1
Description
The following parts contain information on managing the Dimetra IP Micro/Dimetra LiTE system through the Web
Network Manager (Web NM). You are also provided with instruction on the process of configuration of the radio
system infrastructure.
Starting Up the Web NM

You start up the Web NM by entering the URL:
http://10.1.237.163, or http://was01.zone1
in the WEB browser (Microsoft Internet Explorer or Mozilla Firefox). Before you are allowed to initiate any of the
services available in the Dimetra IP Micro/Dimetra LiTE system, you are asked to authenticate yourself. The Web
NM provides three access rights:
• Admin provides a read-write access to all elements in the Web NM.
• Guest provides a read-only access to the Status and Configuration pages in the Web NM. You cannot perform
any updates.
• Supermgr provides a read-write access to all elements in the Web NM and the possibility of changing passwords
for other users.
Procedure:
1 In the Internet browser, enter the URL address: http://10.1.237.163 or http://was01.zone1.
The Login Window appears.
Figure 1: Login Window
2 Type the user name and password that uniquely identifies you on the system.
See Change Password on page 190 for character details.
Note: Changing the default password is advisable for security assurance. For instructions, see the
procedure in Changing the Password on page 116.
Note: If you insert the username or password incorrectly, you get an error message informing you to
type in the correct values.
3 Click Login.
The Web Network Manager opens.

44 | Description
Figure 2: Web NM Page
Note: The session times out automatically after 30 minutes when you do not perform any actions within
the Web NM.
Web NM Main Window Structure

The Web NM pages contain the following structure:
• Main Menu
• Submenu
• Information Frame
• Command Buttons
• Command Frame
The following figure shows an example of the main window. It also illustrates the terms used for the different parts of
the window.
Figure 3: Web NM Main Window Elements

45 | Operation
Chapter
2
Operation
The Web NM application allows you to perform several user-oriented functions. You can use it, for example, to
monitor the status of the devices of the system, create radio users, talkgroups, configure specific features, perform
backups/restoration, and so on. Use the described procedures to perform specific tasks in the Dimetra IP Micro/
Dimetra LiTE system infrastructure.
Status Management
The Status Management allows displaying the state and cause of all radio system elements for all managed objects
represented in the Dimetra IP Micro/Dimetra LiTE system. You can monitor the servers, network devices, and
management objects of this system. By checking the status of the managed elements, you can identify if a fault occurs
and if it requires any corrective actions.
The following system alarms are supported by this system:
• State/cause alarms indicate a change in status for a particular device. State/cause alarms represent the most
current status of a system. Click Refresh to refresh the state/cause alarms list on the Current Status page.
• Transient alarms also known as technician messages are general events that do not affect the state of an object in
the system (such as a successful database export or failed connection to remote system). Transient alarms are
meant to provide useful information to assist the user in managing and troubleshooting the radio system. Transient
alarms are sometimes sent in conjunction with state/cause alarm messages to provide additional information about
failure conditions. Any event that would not cause a status change in a managed object is reported as a transient
alarm. Those types of alarms are reported on the All Events page.
See Alarm Guidelines on page 231 for details on system alarms that are applicable to the system.
Figure 4: Example of the Status Page

46 | Operation
Monitoring the State and Cause of System Alarms

Monitoring the state and cause of the elements and components used in the radio system is done using Element or
Component (see Figure 4: Example of the Status Page on page 45).
When you click the Element button, you get information on the state and cause of the devices in the Dimetra IP
Micro/Dimetra LiTE infrastructure. When you click Component, a list of the managed components in the radio
system appears presenting the state and cause of the fault. The time and date of the last change that was detected is
also shown.
Note: If you want to view information of all components of only one selected element click the Filter link.
The link when activated opens a page containing only the components of the selected element (see the
following figure).
Figure 5: Example of a List of Components of One Element
Note: You can also view up to 32 last status changes of an object (if present) by clicking the History link.
The link opens a page with a list of these status changes (see the following figure).

Operation | 47
Figure 6: Example of Status Changes of an Object
Identifying and Troubleshooting the State and Cause

The information on how to interpret the different state and cause messages for specific elements and components used
in this radio system seen in the Status page is presented in the form of tables. The tables provide information on the
types of alarms and actions that should be taken to resolve and validate the fault of a specific object of the system (see
Alarm Guidelines on page 231).
To check the explanations of the messages visible in the Status page and find a solution, it is necessary to gather the
following information:
• Severity a text indication for the severity of the status of the element
• Element the Alias of the Element reporting its status in the system (for example ATR)
• Component the Alias of the component on which the status is reported (for example ZcMobilityLink (1))
• State a text of the status reported for the element followed by the state number (for example ENABLED (2))
• Cause a text of the cause reported for the element followed by the cause number (for example ALL PROCESS
ENABLED (302))
• Time at which this state/cause was reported (for example 15-Jun-2009 10:41:44)
Having gathered the above information, you can find recommendation from the tables on what steps to take next.
Table 2: Example of Alarm Messages
State Cause
Number State Text Severity Number Cause Text Recommendation
2 NORMAL OP- normal (6) 2002 SOME ALARMS Some alarm cases are
ERATION CLEARED cleared. The new state re-
flects if there are still is-
sues left or not.
Table continued…

48 | Operation
State Cause
Number State Text Severity Number Cause Text Recommendation
2 NORMAL OP- normal (6) 2005 RECEIVER SIGNAL Check the RF environ-
ERATION CLEARED ment settings. Receiver
signal problem/fault
cleared (no further prob-
lems on this issues).
2 NORMAL OP- normal (6) 2008 RF INTERFERENCE Check the RF environ-
ERATION CLEARED ment settings. RF Inter-
ference problem/fault
cleared (no further prob-
lems on this issues).
2 NORMAL OP- normal (6) 9998 UNKNOWN CAUSE This is normal system op-
ERATION eration. No action re-
quired.
Note: For the descriptions of the severity alarm level, see Alarm Severity Levels on page 140.
Downloading the Events

The All Events page gives you the possibility of viewing events of the various elements and components in the
system as they occur. The events are listed in the order of occurrence, for example, the newest event is listed first.
This page might be considered a finite history of all the events that have occurred in the system. You can download
these events to a local PC in the form of a comma-separated file. The event logs are stored for maximum 32 status
changes for each managed object (if present).
Procedure:
1 On the Status page, select All Events.
2 Click Download.
The File Download dialog box appears.
Figure 7: File Download Dialog Box
3 Click Save and choose the directory for saving the file on your PC in the form of a comma-separated file (.csv).
4 To view the events, open the saved file.

Operation | 49
Figure 8: Example of Downloaded Events in the .csv File
Configuration Management
The Configuration page (see the following figure) allows you to configure different objects and features within the
Dimetra IP Micro/Dimetra LiTE system.
Figure 9: Configuration Page
Configuring a Radio User Capabilities Profile

Radio User Capabilities Profile defines the general capabilities of the radio user. Each Radio User Capabilities
Profile contains capability parameters that can be customized per configured profile. Every radio user is assigned a
Radio User Capabilities Profile, and you can use this profile to customize a set of parameters that are common to a
specific group of radio users.

50 | Operation
Figure 10: Radio User Capabilities Profile Page
For detailed descriptions of particular parameters, see Table 11: Parameters for the Radio User Capabilities Profile
on page 146.
Creating a Radio User Capabilities Profile

You can customize the capability parameters for a set of radio users by creating a profile. The following procedure
shows how to create a radio user capabilities profile record.
Procedure:
1 On the Configuration page, select Radio User Capabilities Profile.
2 Click New.
The Radio User Capabilities Profile configuration page appears.

Operation | 51
Figure 11: Radio User Capabilities Profile Configuration Page
3 Configure the parameters as required according to the parameter descriptions in Table 11: Parameters for the
Radio User Capabilities Profile on page 146.
4 When finished, click OK to close the window and return to the previous page.
Editing the Settings of the Radio User Capabilities Profile

When and where to use:
If you want to change the settings for the existing Radio User Capabilities Profile, perform the following procedure.
Procedure:
The list of records appears in the Information frame.
2 Select the checkbox with the profile record you want to modify.
3 Click Modify.
The Modify Radio User Capabilities Profile page appears.
Figure 12: Modify Radio User Capabilities Profile Page
Note: The Radio User Capabilities Profile Alias, Radio User Capabilities Profile ID, and the Load
Class Name (if the Common Secondary Control Channel functionality is not enabled) fields are grayed
out.
4 Configure the parameters as required according to the parameter descriptions in the Table 11: Parameters for the
Radio User Capabilities Profile on page 146.
5 When finished, click Apply and return to the previous page.

52 | Operation
Note: When you want to find a specific Radio User Capabilities Profile, you can use the search query
activated by clicking the Open Search command. The search is possible by choosing a determined
operator from the drop-down list, and typing in the Radio User Capabilities Profile Alias or ID in the
Command Frame field. For the Alias, the following operators are available: Starts with, Ends with,
Contains, Equals, In. For the IDs: Equals, Between, and In operator. Additionally, you can mark a
checkbox if case sensitivity for the Alias is crucial. Once you click the Search command button within
the search query, a list of available records meeting your criteria appears on the page. Use the Clean
command to change your search options if necessary, and Close to return to the previous page. The
following figures present an example of the search queries page.
Figure 13: Search Query Example
Deleting the Radio User Capabilities Profile

Perform the following procedure if you want to delete the profile records.
Procedure:
A list of profile records appears in the Information frame.
2 Select the profile record you want to delete and click Delete.
A dialog box confirming the deletion of the configuration record appears.
Figure 14: Example of a Confirmation Dialog Box
3 Click Yes.
The record is deleted from the database.
Configuring a Radio User

Radio Users are referred to as personnel who uses the trunked system and are assigned a radio that is active in the
system. Configuration of radio users can be performed via Web NM for the Radio User object in the Configuration
page (see the following figure). The Radio User Capabilities Profile defines the parameters that are common to a
specific group of radio users.

Operation | 53
Figure 15: Radio User Page
For detailed descriptions of particular parameters, see Table 9: Parameters for the Radio User on page 142.
When you receive a radio, it is necessary to enter and configure a Radio User in the Dimetra IP Micro/Dimetra LiTE
system. For details on configuration, see the following procedure
Process:
1 Add users to the system. See Adding a Radio User to the System on page 53.
2 Optional: If you want to create a talkgroup where a radio would be assigned, perform Creating a Talkgroup on
page 63.
Note: A new radio has a default talkgroup initially configured by your technician.
Adding a Radio User to the System

The following procedure explains how to enter a Radio User into the Dimetra IP Micro/ Dimetra LiTE system.
You can also use this procedure for configuring the Short Data, Ambience Listening and Full Duplex, and Packet
Data (if a dedicated license has been purchased) features. You can either enable or disable the features depending on
your needs in step 3.
Procedure:
1 On the Configuration page, select Radio User.
2 Click New.
The Radio User configuration page appears.

54 | Operation
Figure 16: Radio User Configuration Page
3 Configure the parameters as required according to the parameter descriptions in Table 9: Parameters for the Radio
User on page 142.
Note: If you fill in the fields incorrectly, error messages (marked in red) or a popup window appears
informing about invalid information (see the following figure). To proceed, all the fields must be filled
in with the valid information.
Figure 17: Example of an Error Message
Post requisites: If you want to create a talkgroup, proceed to Creating a Talkgroup on page 63.
Editing the Settings of a Radio User


Operation | 55
If you want to change the settings for the existing Radio User, perform the following procedure.
You can also use this procedure for configuring the Short Data, Ambience Listening and Full Duplex, and Packet
Data (if a dedicated license has been purchased) features. You can either enable or disable the features depending on
your needs in step 4.
Procedure:
2 Select the checkbox with the record you want to modify.
3 Click Modify.
The Modify Radio User page appears.
Figure 18: Modify Radio User Page
Note: The Radio User Alias, Radio Serial Number, Radio ID fields are grayed out. Other parameters
are dependant on the availability of specific services for your system.
4 Configure the parameters as required according to the parameter descriptions in Table 9: Parameters for the Radio
User on page 142.

56 | Operation
Note: When you want to find a specific radio user, you can use the search query activated by clicking
the Open Search command. The search is possible by choosing a determined operator from the drop-
down list, and typing in the Radio User Alias or ID in the Command Frame field. For the Alias, the
following operators are available: Starts with, Ends with, Contains, Equals, In. For the IDs: Equals,
Between, and In operator. Additionally, you can mark a checkbox if case sensitivity for the Alias is
crucial. Once you click the Search command button within the search query, a list of available records
meeting your criteria appears on the page. Use the Clean command to change your search options if
necessary, and Close to return to the previous page.
Deleting a Radio User

Delete the radio user only in cases when you want to remove it from the system, you do not need it anymore or you
want to make it unavailable due to some damage. In this way, you delete the radio user entirely from the User
Configuration Server database.
Before deleting a record, it is important that you consider the following consequences:
• After you delete a radio user, you may assign the deleted ID number of the radio user to a new radio user.
• When deleting a radio user from the system, the radio of the user is not functional on the system until it is
assigned in another record of a radio user.
In cases when the radio has been stolen, you can perform one of the following:
• Clear the checkbox in the User Enabled field for the specific Radio User record when modifying the parameters
of the Radio User in the Configuration page.
• Perform the procedure provided below.
• To disable the functional capabilities of a radio, you can use the Temporary Subscription Disable command in
Radio Control Manager (RCM). For such information contact your technician.
Note: Note that this can be done if you have the RCM license.
Procedure:
A list of radios appears in the Information frame.
2 Select the radio user record you want to delete and click Delete.
Figure 19: Example of a Radio User for Deletion

Operation | 57
Figure 20: Confirmation Dialog Box
3 Click Yes.
Configuring a Radio User Interconnect Profile

The Radio User Interconnect Profile defines the interconnect call capabilities for the radio user. Every radio user is
assigned a Radio User Interconnect Profile. You can use the Radio User Interconnect Profile record to define a set of
parameters that are common to a specific group of radio users. If the interconnect capabilities are enabled, the radio
user can initiate and receive interconnect calls.
Figure 21: Radio User Interconnect Profile Page
For detailed descriptions of particular parameters, see Table 13: Parameters for the Radio User Interconnect Profile
on page 148.

58 | Operation
Creating a Radio User Interconnect Profile

Procedure:
1 On the Configuration page, select Radio User Interconnect Profile.
2 Click New.
The Radio User Interconnect Profile configuration page appears.
Figure 22: Radio User Interconnect Profile Configuration Page
Radio User Interconnect Profile on page 148.
Editing the Setting of a Radio User Interconnect Profile

If you want to change the settings for the existing Radio User Interconnect Profile, perform the following
procedure.
Procedure:
1 On the Configuration page, select Radio User Interconnect.
2 Select the checkbox with the record you want to modify.
3 Click Modify.
The Modify Radio User Interconnect Profile page appears.

Operation | 59
Figure 23: Modify Radio User Interconnect Profile Page
Note: The Radio User Interconnect Profile Alias, ID fields are grayed out.
Radio User Interconnect Profile on page 148.
Note: When you want to find a specific radio user interconnect profile, you can use the search query
operator from the drop-down list, and typing in the Radio User Interconnect Profile Alias or ID in the
command to change your search options if necessary, and Close to return to the previous page.
Deleting Radio User Interconnect Profile

Procedure:
1 On the Configuration page, select Radio User Interconnect Profile.
A list of profiles appears in the Information frame.
2 Select the radio user interconnect profile record you want to delete and click Delete.
3 Click Yes.

60 | Operation
Configuring a TG/MG Capabilities Profile

The TG/MG Capabilities Profile defines the capabilities for a talkgroup or multigroup. You can use the TG/MG
Capabilities Profile record to define a set of parameters that are common to a number of talkgroups and/or
multigroups. Each TG/MG Capabilities Profile contains capability parameters that can be customized per configured
profile. Every talkgroup and multigroup is assigned a TG/MG Capabilities Profile.
Figure 24: TG/MG Capabilities Profile Page
For detailed descriptions of particular parameters, see Table 19: Parameters for TG/MG Capabilities Profile on page
155.
Creating a TG/MG Capabilities Profile

The TG/MG Capabilities Profile record defines the general capabilities that are common to a specific talkgroup or
multigroup. The following procedure explains how to create a profile record for a multigroup and talkgroup.
Procedure:
1 On the Configuration page, select TG/MG Capabilities Profile.
2 Click New.
The TG/MG Capabilities Profile configuration page appears.

Operation | 61
Figure 25: TG/MG Capabilities Profile Configuration Page
3 Configure the parameters as required according to the parameter descriptions in Table 19: Parameters for TG/MG
Capabilities Profile on page 155.
Editing the Settings of a TG/MG Capabilities Profile

If you want to change the settings for the existing TG/MG Capabilities Profile, perform the following procedure.
Procedure:
The list of profile records appears in the Information frame.
2 Select the checkbox with the profile record you want to modify.
3 Click Modify.
The Modify TG/MG Capabilities Profile page appears.
Figure 26: Modify TG/MG Capabilities Profile Page
Note: The TG/MG Capabilities Profile Alias, TG/MG Capabilities Profile ID fields are grayed out.
4 Configure the parameters as required according to the parameter descriptions in Table 19: Parameters for TG/MG
Capabilities Profile on page 155, depending on your needs.
5 When finished, click Apply and return to the previous page.

62 | Operation
Note: When you want to find a specific TG/MG Capabilities Profile, you can use the search query
operator from the drop-down list, and typing in the TG/MG Capabilities Profile Alias or ID in the
command to change your search options if necessary, and Close to return to the previous page.
Deleting a TG/MG Capabilities Profile

Procedure:
A list of profile records appears in the Information frame.
2 Select the profile record you want to delete and click Delete.
3 Click Yes.
Configuring a Talkgroup
You can configure a Talkgroup via Web NM. A TG/MG capabilities profile defines the parameters that are common
to a specific talkgroup.
Figure 27: Talkgroup Page

Operation | 63
For detailed descriptions of particular parameters, see Table 15: Parameters for the Talkgroup Object on page 150.
Note: A talkgroup is the basic unit of communication in a trunked system. In most organizations, radio
users work in groups that are based on their functions and responsibilities. In a trunked radio system, these
groups of radio users can be assigned to communication talkgroups that reflect their function or
responsibilities. Programming of talkgroups in a radio is based on the communication needs of radio users.
A radio can be programmed with only one or with several talkgroups. Radio users selecting a particular
talkgroup on their radios are assigned a voice channel when someone in the group requests talkgroup call
services. Group privacy during conversations is provided since only one talkgroup is assigned to each voice
channel.
Figure 28: Organization of Users in a Talkgroup
Several talkgroups can be combined to form a multigroup (also called an announcement group).
Creating a Talkgroup
The Talkgroup object consists of information that identifies a group of radios that communicate and interact together
on the system. This group can also be a subset of a multigroup.
The following procedure explains how to create a Talkgroup and select configuration values in the remaining fields.
Procedure:
1 On the Configuration page, select the Talkgroup.
2 Click New.
The Talkgroup configuration page appears.
Figure 29: Talkgroup Configuration Page
Talkgroup Object on page 150.
Editing the Settings of a Talkgroup


64 | Operation
In case you want to change the settings of an existing talkgroup, for example change the parameter values, perform
the following procedure.
Procedure:
1 On the Configuration page, select Talkgroup.
2 Select the checkbox with the talkgroup you want to modify.
3 Click Modify.
The Modify Talkgroup page appears.
Figure 30: Modify Talkgroup Page
Note: The Talkgroup Alias, Talkgroup ID fields are grayed out.
Talkgroup Object on page 150.
Note: When you want to find a specific talkgroup, you can use the search query activated by clicking
down list, and typing in the Talkgroup Alias or ID in the Command Frame field. For the Alias, the
Deleting a Talkgroup
You can delete a talkgroup because of changes to user needs, in response to system performance issues, or because of
a decrease in the number of radio users on the system. When you delete a talkgroup from the system, radio users can
no longer use it to communicate. Radio users can continue to communicate on the system by selecting any other
talkgroup that is programmed into their radios.
It is important to consider the following before deleting a talkgroup:
• After you delete a talkgroup, you can assign the deleted ID number of a talkgroup to a new talkgroup.
• When you delete a talkgroup from the system it is automatically deleted from any multigroup it was assigned to.
Procedure:
1 On the Configuration page, select Talkgroup.
A list of talkgroups appears in the Information frame.
2 Select the talkgroup you want to delete and click Delete.

Operation | 65
3 Click Yes.
Adding/Removing a Talkgroup from a Multigroup

It is possible to add or remove talkgroups from multigroups that you have created via the Web NM. For details, see
Editing the Parameters of a Multigroup on page 67.
Configuring a Multigroup
A Multigroup consists of all necessary information that a trunking system requires for a multigroup on the system. A
multigroup is a large group that is composed of several talkgroups.
Note: Each talkgroup can be associated with one (and only one) multigroup.
Figure 31: Multigroup Page
For detailed descriptions of particular parameters, see Table 17: Parameters for the Multigroup Object on page 152.
A multigroup call is also referred to as an announcement call. An announcement call is a point to multipoint group
call that provides the capability to communicate with multiple talkgroups simultaneously.

66 | Operation
Figure 32: Talkgroups in Multigroups
The behavior described in this part is only valid if all radios that are configured in both Web NM and Customer
Programming Software (CPS). If a radio is affiliated to a multigroup and configured only in a Web NM, it can
transmit, however, traffic ongoing on talkgroups associated to the multigroup is not received by the MS.
Before a radio can initiate a call to a multigroup, it must first affiliate with the multigroup. When a user affiliated with
a multigroup initiates a group call, the Switching and Management Infrastructure (SwMI) attempts to set up an
announcement call to all talkgroups associated to the multigroup. The SwMI sets up an announcement call for the
multigroup at each of the following sites:
• Every site with or more members of the multigroup
• Every site with one or more members of any of the talkgroups associated with the multigroup
When a user affiliated with one of the members of a multigroup initiates a group call, the SwMI attempts to set up a
normal group call to the multigroup. However, this call is directed to the following sites:
• Every site with one or more members of the member talkgroup
• Every site with one or more members of the multigroup
Users affiliated with the multigroup are scanning for calls on the associated talkgroups. On the other hand, users
affiliated with one of the members of a multigroup are scanning for calls on the multigroup (but not on other
talkgroup members). This part does not include details of configuration options common to both multigroup and all
other talkgroups.
Creating a Multigroup
The Multigroup is made up of several talkgroups whose members occasionally communicate as a group.
The following procedure explains how to create a Multigroup and select configuration values in the remaining fields.
Procedure:
1 On the Configuration page, select Multigroup.
2 Click New.
The Multigroup configuration page appears.

Operation | 67
Figure 33: Multigroup Configuration Page
Multigroup Object on page 152.
Note: While creating a multigroup, you can add previously created talkgroups to form a multigroup.
You can do it by clicking Add and selecting the determined talkgroups existing in the database. The
selection can be done individually or in groups by selecting a few talkgroups all at once, and clicking
Select.
Editing the Parameters of a Multigroup

In case you want to change the settings of an existing multigroup, for example change the parameter values, perform
the follwing procedure.
This procedure also allows you to add/remove a talkgroup to/from a multigroup. This is possible not only when
modifying the settings of a multigroup, but also when creating them. For details, seethe procedure provided below.
Procedure:
2 Select the checkbox with the multigroup you want to modify.
3 Click Modify.
The Modify Multigroup page appears.

68 | Operation
Figure 34: Modify Multigroup Page
Note: The Multigroup Alias, Multigroup ID fields are grayed out.
Multigroup Object on page 152.
Note: While modifying the settings of a multigroup, you can add previously created talkgroups to form
a multigroup. This can be done by clicking Add and selecting the determined talkgroups existing in the
database. The selection can be done individually or in groups by selecting a few talkgroups all at once,
and clicking Select. To remove the talkgroups, select the ones you want to remove from the system, and
click Delete.
Note: When you want to find a specific multigroup, you can use the search query activated by clicking
down list, and typing in the Multigroup Alias or ID in the Command Frame field. For the Alias, the
Deleting a Multigroup
You can delete a multigroup depending on your needs, in response to system performance issues, or because of a
decrease in the number of radio users on the system. When you delete a multigroup from the system, radio users can
no longer use it to communicate. Radio users can continue to communicate on the system by selecting any other
talkgroup that is programmed into their radios.
Procedure:
A list of multigroups appears in the Information frame.

Operation | 69
2 Select the multigroup you want to delete and click Delete.

3 Click Yes.
Configuring a Dispatch Application

The Dispatch Application object is a software application that is combined with other elements (such as hardware) to
provide a console user (that is, a dispatcher) with the ability to exercise dispatch console functionality (such as
managing and communicating with talkgroups). The Dimetra IP Micro/Dimetra LiTE system uses two types of
dispatch consoles:
• MCC 7500 dispatch console system which uses the General Purpose Input/Output Module (GPIOM) based
interface allowing for multiple peripherals to be connected to a Dispatch Application. The following items are
interfaced through the GPIOM with the Dispatch Application:
- Microphone
- Speakers
- Headset jack
The configuration parameters of the peripherals are set by default, if this type of dispatch console is selected for
your system.
• MCC 7500C dispatch console system which does not use the Purpose Input/Output Module (GPIOM).
Note: This object is also used to create a new Console User, as static console users are assigned
automatically when a new Dispatch Application is created. If you want to create a dynamic Console User
then you need to use the Console User object (see Creating a Console User on page 76).
Figure 35: Dispatch Application Page
For detailed descriptions of particular parameters, see Table 21: Parameters for Dispatch Application on page 157.
Creating a Dispatch Application

The following procedure instructs you how to create a Dispatch Application record.

70 | Operation
Note: When you create a new Dispatch Application object, a new static Console User is created. The static
Console User record identifies a Console User Capability Profile that defines either a full set of permissions
or limited permissions (in the latter case, it means that no dispatcher using this particular dispatch console
can have more permissions than defined via this Console User Capability Profile). If you want to create a
dynamic Console User then you need to use the Console User object (see Creating a Console User on page
76).
Procedure:
1 On the Configuration page, select Dispatch Application.
2 Click New.
The Dispatch Application configuration page appears.
Figure 36: Dispatch Application Configuration Page
Note: Note that when you decide to create a dispatch console in a remote site, the following
requirements must be fulfilled:
• Console Site ID must be the same as the one used for the remote CCGW (if created).
• Local LAN parameter must be disabled.
3 Configure the parameters as required according to the parameter descriptions in Table 21: Parameters for
Dispatch Application on page 157.
Note: When a new Dispatch Application is created, a new Acoustic Cross Mute instance is created with
that Dispatch Application. Therefore, you can select the determined dispatch applications to prevent
listening to undesired audio from another nearby console application by using the Acoustic Cross
Mute parameter. Click Add and from the list of available Application Platform Aliases (existing in the
database) select the Dispatch Applications that this console wants to mute.

Operation | 71
Note: When creating a new Dispatch Application record, depending on the type of dispatch console you
select (MCC 7500 / MCC 7500S, or MCC 7500C), some of the dedicated configuration parameters for
the determined console will be automatically made inactive.
Editing the Settings of a Dispatch Application

If you want to change the settings for the existing Dispatch Application, perform the following procedure.
Procedure:
2 Select the checkbox with the dispatch application object you want to modify.
3 Click Modify.
The Modify Dispatch Application page appears.
Figure 37: Modify Dispatch Application Page
Note: The Application Platform Alias, Application Platform ID, Console User Login Name,
Console Unit ID, Console Site ID, Local LAN, and Dispatch Application Type (depending on the
type of selected dispatch application MCC 7500 / MCC 7500S or MCC 7500C its dedicated peripheral
parameters will be inactive by default) fields are grayed out.
4 Select the necessary parameters for the Dispatch Application object according to the Table 21: Parameters for
Dispatch Application on page 157.

72 | Operation
Note: When you want to find a specific dispatch application, you can use the search query activated by
clicking the Open Search command. The search is possible by choosing a determined operator from
the drop-down list, and typing in the Application Platform Alias or ID in the Command Frame field.
For the Alias, the following operators are available: Starts with, Ends with, Contains, Equals, In. For
the IDs: Equals, Between, and In operator. Additionally, you can mark a checkbox if case sensitivity
for the Alias is crucial. Once you click the Search command button within the search query, a list of
available records meeting your criteria appears on the page. Use the Clean command to change your
search options if necessary, and Close to return to the previous page.
Deleting a Dispatch Application Record

Procedure:
A list of dispatch applications appears in the Information frame.
2 Select the dispatch application record you want to delete and click Delete.
3 Click Yes.
Note: The static Console User is deleted when the Dispatch Application record is deleted.
Configuring Logging Interface Application

The Logging Interface Application object represents the logging server device which serves audio to the third party
Logging Recorder for audio archiving at a Console Site office.
Note: This object is also used to create a new static console user, as static console users are assigned
automatically when a new Logging Interface Application is created.

Operation | 73
Figure 38: Logging Interface Application Page
For detailed descriptions of particular parameters, see Table 23: Parameters for Logging Interface Application Object
on page 162.
Creating a Logging Interface Application Record

The following procedure explains how to add an Logging Interface Application record and select configuration
values in the remaining fields.
Note: Only one Logging Interface Application configuration object can be created, and if one has already
been created, then the New command button is disabled.
When you create a new Logging Interface Application object, a new static Console User is created. The static
Console User record identifies a Console User Capability Profile that defines either a full set of permissions or limited
permissions (in the latter case, it means that no dispatcher using this particular dispatch console can have more
permissions than defined via this Console User Capability Profile). If you want to create a dynamic Console User then
you need to use the Console User object (see Creating a Console User on page 76).
Procedure:
1 On the Configuration page, select Logging Interface Application.
2 Click New.
The Logging Interface Application configuration page appears.

74 | Operation
Figure 39: Logging Interface Application Configuration Page
3 Configure the parameters as required according to the parameter descriptions in Table 23: Parameters for Logging
Interface Application Object on page 162.
Editing the Settings of a Logging Interface Application Record

In case you want to change the settings of an existing Logging Interface Application record, perform the following
procedure.
Procedure:
2 Select the checkbox with the Logging Interface Application record you want to modify.
3 Click Modify.
The Logging Interface Application page appears.
Figure 40: Modify Logging Interface Application Page
Note: The Application Platform Alias, Application Platform ID, Logging Interface User Login
Name, and Logging Interface Unit ID fields are grayed out.
4 Configure the parameters as required according to the parameter descriptions in Table 23: Parameters for Logging
Interface Application Object on page 162.

Operation | 75
Note: When you want to find a specific Logging Interface Application, you can use the search query
operator from the drop-down list, and typing in the Application Platform Alias or ID in the Command
Frame field. For the Alias, the following operators are available: Starts with, Ends with, Contains,
Equals, In. For the IDs: Equals, Between, and In operator. Additionally, you can mark a checkbox if
case sensitivity for the Alias is crucial. Once you click the Search command button within the search
query, a list of available records meeting your criteria appears on the page. Use the Clean command to
change your search options if necessary, and Close to return to the previous page.
Deleting the Logging Interface Application Record

If you want to delete a Logging Interface Application record, perform the following procedure.
Procedure:
A list of Logging Interface Users appears in the Information frame.
2 Select the Logging Interface Application record you want to delete and click Delete.
Note: The static Console User is deleted when the Logging Interface Application record is deleted.

3 Click Yes.
Configuring a Console User

A console user, also called a dispatcher, is a person logged on to the system who monitors and transmits commands to
radio traffic.
Use this object when you want to configure the dynamic Console User and change the setting such as the Capability
Profile or Ambience Listening.
Note: This object allows configuring a dynamic Console User. Static Console Users are assigned
automatically when a new Dispatch Application record is created.

76 | Operation
Figure 41: Console User Page
For detailed descriptions of particular parameters, see Table 25: Parameters for Console User Object on page 164.
Creating a Console User

The following procedure explains how to create a Console User and select configuration values in the remaining
fields.
Note: You can also use this procedure for configuring the Ambience Listening feature. You can either
enable or disable the feature depending on your needs in step 3.
Procedure:
1 On the Configuration page, select Console User.
2 Click New.
The Console User configuration page appears.
Figure 42: Console User Configuration Page
3 Configure the parameters as required according to the parameter descriptions in Table 25: Parameters for Console
User Object on page 164.

Operation | 77
Editing the Settings of a Console User

In case you want to change the settings of an existing console user, for example change the parameter values such
Capability Profile, Ambience Listening, perform the following procedure.
Note: You can also use this procedure for configuring the Ambience Listening feature. You can either
enable or disable the feature depending on your needs in step 4.
Procedure:
2 Select the checkbox with the console user you want to modify.
3 Click Modify.
The Modify Console User page appears.
Figure 43: Modify Console User Page
Note: The Console User Login Name, and Console ID fields are grayed out.
4 Configure the parameters as required according to the parameter descriptions in Table 25: Parameters for Console
User Object on page 164.
Note: Use this step for feature configuration. You can enable or disable a feature by selecting an
appropriate checkbox.
Note: When you want to find a specific console user, you can use the search query activated by clicking
down list, and typing in the Console User Login Name or Console ID in the Command Frame field.
For the Alias, the following operators are available: Starts with, Ends with, Contains, Equals, In. For
the IDs: Equals, Between, and In operator. Additionally, you can mark a checkbox if case sensitivity
for the Alias is crucial. Once you click the Search command button within the search query, a list of
Deleting a Console User

If you want to delete a Console User record, perform the following procedure:
Procedure:
A list of console users appears in the Information frame.

78 | Operation
2 Select the console user you want to delete and click Delete.
3 Click Yes.
Configuring Status Sets

The Status Set object is used to create status messages that are used by the radio users to report their status. For
example, a radio user can send a status message showing they are Returning to Base, Out of Service or
Available and so on. The Status Set lets you create up to 100 status messages which the radio user can reference.
These status messages are displayed at the console after the radio user selects an assigned number that corresponds to
a status message. The Status Set object uses the STATUS-SET-1 as a default record. You cannot create or delete
this status set configuration record, only modification of the status messages is possible.
Figure 44: Status Set Page
Editing the Status Set Messages

The following procedure explains how to modify the status messages.
Procedure:
1 On the Configuration page, select Status Set.
2 Select the checkbox with the Status Set record that you want to modify.
3 Click Modify.

Operation | 79
The Modify Status Set page appears.
Figure 45: Modify Set Status Page
Note: The Status Set Alias, and Status Set ID fields are grayed out.
4 In the Status Text field type the status message, for example Returning to Base, Out of Service,
Available for the console user to see.
Note: For more parameter information, see Table 27: Parameters for Status Set Object on page 167.
Note: The Status Numbers are fixed and cannot be edited.

80 | Operation
Note: When you want to find a specific status set message, you can use the search query activated by
clicking the Open Search command. The search is possible by choosing a determined operator from
the drop-down list, and typing in the Status Set Alias or ID in the Command Frame field. For the
Alias, the following operators are available: Starts with, Ends with, Contains, Equals, In. For the
IDs: Equals, Between, and In operator. Additionally, you can mark a checkbox if case sensitivity for
the Alias is crucial. Once you click the Search command button within the search query, a list of
Configuring Short Data Router Services

The Short Data Router (SDR) features the Short Data Service (SDS) and enables the routing of short data messages
within the system. The source and destination of the message are identified by TETRA Individual Short Subscriber
Identities (ISSIs). All short data packets to be delivered via the SDS are sent to the SDR. The SDR forwards a short
data message to the appropriate Base Transceiver System (BTS) which distributes it appropriately to a desired Mobile
Station (MS) or a user. The short data messages to be delivered to an external fixed host, the SDR maps the ISSI to an
IP address, and forwards the packets to the host using IP. The SDR communicates with the rest of the system over a
single Ethernet connection. Connection between an external SDS host and the SDR is provided via an appropriately
configured IP router.
Table 3: List of Predefined ISSIs
Name of Host ISSI Passcode for Host Registration

HOST-00 to HOST-09 13999000 to 13999009 0-0-0-0 (No password)
Group Message Service 13999998 127-0-0-1
StoreForward Service 13999999 127-0-0-1

Operation | 81
Figure 46: Short Data Router Page
The SDR server co-host the Store and Forward Server (SFS) and the Group Message Server (GMS) (see the figure
above). For more information, see Enabling the Short Data Router Services on page 81.
Note: In order to have Store and Forward feature and MS-to-Group SD feature enabled, licenses have to be
purchased. Additionally, you cannot create or delete the Short Data Router configuration record, only
modification of the two mentioned features is possible.
Enabling the Short Data Router Services

The SDR server co-host the Store and Forward Server (SFS) and the Group Message Server (GMS). The Store and
Forward (SF) feature allows for the delivery of short data messages to a temporarily unreachable MS at a later time.
The SFS buffers the messages for the unreachable MS and delivers them when the MS is available again.
The MS-to-Group Service (also known as Group Message Service) enables broadcast messages to be distributed
from a single radio to a group.
purchased.
For more information on this configuration, see the “SDR — Local Configuration” section in the Data
Subsystem manual.
Prerequisites: Ensure that the following items are configured on the SDR:
• SDTS Hosts
• Broadcast Regions
• Store and Forward Service and Server
• Group Message Service and Server

82 | Operation
Procedure:
1 On the Configuration page, select Short Data Router.
2 Select the checkbox to enable the services.
3 Click Modify.
The Modify Short Data Router page appears.
Figure 47: Modify Short Data Router Page
4 Select the checkboxes for the Store and Forward Service Enabled and MS to Group Service Enabled.
The SDR services are enabled.
Configuring an MTS Site

The MTS Site object is used to configure the MTS site the operations within a zone, and set the parameters for a site
so that it will function correctly in the system. It includes Diagnostics functionality, which involves sending a
message to the site, causing the site to change state.
Figure 48: MTS Site Page
For detailed descriptions of particular parameters, see Table 30: Parameters for MTS Site on page 170.
For more details on the MTS LiTE, MTS2 and MTS4 sites, see the MTS LiTE, MTS2 and MTS4 Installation,
Configuration and Basic Service Manual.
For more details on the MTS1 sites, see the MTS1 Installation, Configuration and Basic Service Manual.

Operation | 83
Creating an MTS Site

The following procedure explains how to create an MTS Site and select configuration values in the remaining fields.
Procedure:
1 On the Configuration page, select MTS Site.
2 Click New.
The MTS Site configuration page appears.
Figure 49: MTS Site Configuration Page
3 Configure the parameters as required according to the parameter descriptions in Table 30: Parameters for MTS
Site on page 170.
Editing the Settings of an MTS Site

If you want to change the settings for the existing MTS Site, perform the following procedure.
Procedure:
2 Select the checkbox with the MTS site you want to modify.
3 Click Modify.

84 | Operation
The Modify MTS Site page appears.
Figure 50: Modify MTS Site Page
Note: The Site Alias and Site ID fields are grayed out. Other parameters depend on the availability of
specific services for your system.
4 Select the necessary parameters for the MTS Site object according to the Table 30: Parameters for MTS Site on
page 170.
Note: Depending on the type of the MTS you chose, you may:
• Add up to two MTS base radio records for MTS1 (MTS1 can be paired to another MTS using an interconnect
kit), up to two MTS base radio records for an MTS2 and up to eight MTS base radio records for an MTS4.
MTS1 is automatically paired if it has two base radios.
• Add up to two MTS Digital Power Meters (DPM) for MTS2 and maximum of eight for MTS4. MTS1 does not
support the Digital Power Meter .
• Add up to four MTS Auto Tune Cavity Combiner (ATCC) for MTS4, as only MTS4 supports ATCC and can
be configured with ATCC. MTS1 and MTS2 does not support the Auto Tune Cavity Combiner.
Note: When modifying the settings of the MTS1 type, note that it is not possible to change the site type
from MTS1 to any other site type. Neither is it possible to change from other site types (MTS2 or
MTS4) to an MTS1 site type. In either situation, delete the site and create a new MTS of the requested
type.

Operation | 85
Note: When you want to find a specific MTS site, you can use the search query which is activated once
you click the Open Search command button. The search is possible by choosing a determined operator
from the drop-down list, and typing in the Site Alias or ID in the Command Frame field. For the Alias,
the following operators are available: Starts with, Ends with, Contains, Equals, In. For the IDs:
Equals, Between and In operator. Additionally, you can mark a checkbox if case sensitivity for the
Alias is crucial. Once you click the Search command button, a list of available records meeting your
criteria appears on the page. Use the Clean command button to change your search options if necessary,
and Close to return to the previous page.
Deleting an MTS Site

If you want to delete an MTS Site record, perform the following procedure.
Procedure:
A list of MTS sites appears in the Information frame.
2 Select the MTS site you want to delete and click Delete.
3 Click Yes.
Changing the State of an MTS Site

The following procedure explains how to change the state of an MTS Site by executing the diagnostic command.
Procedure:
A list of MTS sites appears in the Information frame.
2 Select the MTS site you want to change the state of, and click Diagnostics.
A Diagnostics window appears.
Figure 51: Diagnostics Window
3 Select a specific diagnostics command from the list (Forced Parameter Download, Wide Trunking, Site
Trunking or Site Reset), and click Send. For diagnostics command details, see Table 31: Command Buttons for
the MTS Site on page 173.
The functional state of the selected MTS site has been changed.

86 | Operation
Configuring a Conventional Channel Gateway

Conventional Channel Gateway (CCGW) object configures the physical interface to analog conventional stations.
The CCGW has software that allows for communications with the Zone Controller (ZC) to enable analog call
transmissions to and from an MCC 7500 console. Before a console can utilize any conventional services, it must first
go in service with the ZC.
Figure 52: Conventional Channel Gateway Page
For detailed descriptions of particular parameters, see Table 32: Parameters for the Conventional Channel Gateway
on page 175.
Creating a Conventional Channel Gateway

Procedure:
1 On the Configuration page, select Conventional Channel Gateway.
2 Click New.
The Conventional Channel Gateway configuration page appears.

Operation | 87
Figure 53: Conventional Channel Gateway Configuration Page
Note: Note that when you decide to create CCGW in a remote site, the following requirements must be
fulfilled:
• Console Site ID must be the same as the one used for the remote dispatch console (if created).
• Local CCGW parameter must be disabled.
Conventional Channel Gateway on page 175.
Editing the Settings of a Conventional Channel Gateway

If you want to change the settings for the existing Conventional Channel Gateway record, perform the following
procedure.
Note: Modifications/updates made to the settings of a CCGW are displayed on the console status bar.
Crucial setting changes may affect the operation of the device, therefore a restart of the router or the
CCGW module may be required.
Procedure:
2 Select the checkbox with the CCGW record you want to modify.
3 Click Modify.
The Modify Conventional Channel Gateway page appears.

88 | Operation
Figure 54: Modify Conventional Channel Gateway Page
Note: The Analog Conventional Channel Alias, Analog Conventional Channel ID, Local CCGW,
and Console Site ID fields are grayed out.
Conventional Channel Gateway on page 175.
Note: When you want to find a specific conventional channel gateway, you can use the search query
which is activated once you click the Open Search command button. The search is possible by
choosing a determined operator from the drop-down list, and typing in the Analog Conventional
Channel Alias or ID in the Command Frame field. For the Alias, the following operators are available:
Starts with, Ends with, Contains, Equals, In. For the IDs: Equals, Between and In operator.
Additionally, you can mark a checkbox if case sensitivity for the Alias is crucial. Once you click the
Search command button, a list of available records meeting your criteria appears on the page. Use the
Clean command button to change your search options if necessary, and Close to return to the previous
page.
Deleting the Conventional Channel Gateway

Procedure:
A list of Conventional Channel Gateway appears in the Information frame.
2 Select the CCGW record you want to delete and click Delete.
3 Click Yes.
Configuring a Telephone Interconnect

The telephone interconnect subsystem provides an interface between the Dimetra radio network and an external
telephone network, allowing telephone interconnect calls to be made between radios and external landline telephones.
Telephone Interconnect (TI) service provides connectivity to external telephone networks such as a single customer
Private Branch Exchange (PBX), multiple PBXs and/or Public Switched Telephone Network (PSTN). This
functionality is possible via the Voice Over IP (VoIP). Telephone interconnect capability allows radio users to initiate
and receive full-duplex calls. IP telephony interface enables radio users to make up to 10 simultaneous calls.

Operation | 89
Figure 55: Telephone Interconnect Page
For detailed descriptions of particular parameters, see Table 34: Parameters for the Telephone Interconnect on page
178.
Creating a Telephone Interconnect Record

Note: Only one Telephone Interconnect configuration object can be created.
Procedure:
1 On the Configuration page, select Telephone Interconnect.
2 Click New.
The Telephone Interconnect configuration page appears.

90 | Operation
Figure 56: Telephone Interconnect Configuration Page
Telephone Interconnect on page 178.
Note: PBX Password will always be set to the value entered in the PBX password field when the
security options are enabled in the PBX. It must be left blank if password is not to be updated.
When entering the values of the following parameters: Signaling Gateway Public IP Address, PBX
IP Address, PBX Username , PBX Password, a restart of the MTIG-IP is required for the settings to
take affect. For details on how to perform this, see the Service Manual.
Editing the Settings of the Telephone Interconnect

If you want to change the settings for the existing Telephone Interconnect record, perform the following procedure:
Procedure:
2 Select the checkbox with the telephone Interconnect record you want to modify.
3 Click Modify.
The Modify Telephone Interconnect page appears.

Operation | 91
Figure 57: Modify Telephone Interconnect Page
Telephone Interconnect on page 178.
Note: PBX Password will always be set to the value entered in the PBX password field when the
security options are enabled in the PBX.
Note: When modifying the values of the following parameters: Signaling Gateway Public IP Address,
PBX IP Address, PBX Username, PBX Password, a restart of the MTIG-IP is required for the settings
to take affect. For details on how to perform this, see the Service Manual.
Note: When you want to find a specific telephone interconnect, you can use the search query which is
activated once you click the Open Search command button. The search is possible by choosing a
determined operator from the drop-down list, and typing in the MTIG-IP Alias or ID in the Command
Frame field. For the Alias, the following operators are available: Starts with, Ends with, Contains,
Equals, In. For the IDs: Equals, Between, and In operator. Additionally, you can mark a checkbox if
case sensitivity for the Alias is crucial. Once you click the Search command button, a list of available
records meeting your criteria appears on the page. Use the Clean command button to change your
Deleting a Telephone Interconnect Record

Procedure:
A list of telephone interconnect records appears in the Information frame.
2 Select the telephone interconnect record you want to delete and click Delete.
A dialog box confirming the deletion of the configuration record appears. A confirmation dialog box appears.
3 Click Yes.

92 | Operation
Configuring a System
To get the system running, it is necessary to configure certain System parameters (see the following figure) which
have a critical impact on the system.
Figure 58: System Page

The following procedure is initially conducted by your technician who enters all the necessary parameter values
before the system can run correctly.
Warning: Change the system configuration parameters carefully as they have been configured to meet
specific system requirements. The system may stop working if the system parameters contain incorrect
values.
Note: The following procedure can also be used to configure the following features: Authentication, Air
Interface Encryption (AIE), Common Secondary Control Channel (C-SCCH). You can either enable
or disable those features depending on your needs in step 4, however this can not be done without
dedicated licenses which have to be purchased.
Note: Creation and deletion of the System configuration record is not supported.
Procedure:
1 On the Configuration page, select System.
The System page appears.
2 Select the checkbox with the system record you want to modify.

Operation | 93
3 Click Modify.
The Modify System page appears.
Figure 59: Modify System Page
4 Configure the System object parameters according to Table 36: Parameters for System on page 182.
Note:
It is essential that the values for the System object are unique for each system, that is why the network
code must be unique within the country. The same applies to the country code in which the system is
installed. These parameters are configured by your technician.
Authentication, Air Interface Encryption (AIE), Common Secondary Control Channel (C-SCCH)
features can be enabled only if dedicated licenses have been purchased.
Configuring a System Optimization Parameters

The System Optimization objects contains parameters which have a critical impact on the system. They are
necessary to configure to get the system running. The system optimization is usually done by the technician at the
initial configuration stage, but you can modify the system settings as described in the following procedure.

94 | Operation
Figure 60: System Optimization Page
Note: Creation and deletion of the System Optimization configuration record is not supported.
Procedure:
1 On the Configuration page, select System Optimization.
2 Select the checkbox with the system optimization record that you want to modify.
3 Click Modify.
The Modify System Optimization page appears.

Operation | 95
Figure 61: Modify System Optimization Page
System Optimization on page 186.
Configuring Group Calls

The Group Call feature allows a radio or Dispatch Console (DC) to establish a point to multipoint communication
with a group of users known as a talkgroup. It allows, for instance, a security guard to alert several security guards at
once by calling for assistance in a critical situation. The talkgroup is a predefined group of radio users who
communicate with each other. A radio user can be part of several different talkgroups. A security guard in a hotel may
as an example be part of a security guard talkgroup and a lobby talkgroup.
The membership of a talkgroup is not a static membership configured within the infrastructure, but is determined by
the radio users who have elected to be a member of that talkgroup at that time. Radios must affiliate with a talkgroup
to be a member of a talkgroup. Once a talkgroup is assigned to a dispatch console, the dispatch console becomes a
member of that talkgroup. A dispatch console may be a member of multiple talkgroups.
The group call service is a semi-duplex service. Semi-duplex transmission means that only one user can transmit
traffic in a call at any time. The system gives transmit permission to a single user. A group call is only terminated by
the system.
Note: Radios provide users with the ability to communicate in the system. Each one of these units is
assigned a unique identification number and contains the logic circuitry necessary to perform the following
trunking functions:
• Generate and transmit requests for service in the form of data words that are then used to modulate the
carrier frequency.
• Interpret the data messages sent by the site controller.
• Generate the frequency of the assigned voice channel.
• Generate tones to advise the radio user of the status of the call request.

96 | Operation
Note: Dispatchers (also referred to as console operators) use consoles to dispatch and monitor radio users.
Dispatch consoles provide an interface to the system for console operators. A console operator can monitor
all or any subset of the talkgroups in the system. In addition to basic dispatch calling features, a console
also provides the following capabilities:
• Console priority - Allows operators to take control of calls by having priority to talk first.
• Full duplex private calls - Allows simultaneous two-way call traffic for console operators.
• Talkgroup merge - Merges multiple talkgroups into a single talkgroup for patch and multi-select
(MSEL) operations.
• Emergency call handling - Displays an ID or alias of a radio and can show a pre-programmed alarm
message.
The following table provides an overview of the parameters to be configured in the Web NM for the Group Call
feature.
Table 4: Overview of Group Call Configuration Parameters
Object Parameter
Talkgroup Talkgroup Alias
Talkgroup ID
TG/MG Capabilities Profile Alias
Console TG/MG Capabilities Profile Alias
Preempt Capable
Talkgroup Regroupable
Multigroup Multigroup Alias
Multigroup ID
TG/MG Capabilities Profile Alias
Console TG/MG Capabilities Profile Alias
Interrupt Or Wait Mode
Preempt Capable
TG/MG Capabilities Pro- TG/MG Capabilities Profile Alias
file
TG/MG Capabilities Profile ID
Dispatch Priority Level
Talkgroup Inactivity Time (Hours)
Audio Interrupt Mode
For configuration details, see:

• Configuring a Talkgroup on page 62
• Configuring a Multigroup on page 65
• Configuring a TG/MG Capabilities Profile on page 60
Configuring Short Data Services

The Short Data Service (SDS) are supported by the Short Data Router (SDR) in the system. The SDR enables the
routing of short data messages within the system. The source and destination of the message are identified by TETRA
Individual Short Subscriber Identities (ISSIs). All short data packets to be delivered via the SDS are sent to the SDR.
The SDR forwards a short data message to the appropriate Base Transceiver System (BTS) which distributes it

Operation | 97
appropriately to a desired radio or a user. For the short data messages to be delivered to an external fixed host, the
SDR maps the ISSI to an IP address, and forwards the packets to the host using IP. The SDR communicates with the
rest of the system over a single Ethernet connection. Connection between an external SDS host and the SDR is
provided via an appropriately configured IP router. Short data routing may be point-to-point or point-to-multipoint
(broadcast).
Note: The Short Data Enabled parameter is enabled for radio users per default. In case it is not, perform
Procedure:
1 From the main menu, select Configuration and then Radio User.
2 To enable the feature:
• If you want to enable the feature for a new Radio User, perform the procedure in Adding a Radio User to the
System on page 53, and in step 3, select the Short Data Enabled checkbox, which allows the radio user to
have access to the short data service.
• If you want to enable the feature for the existing Radio, perform the procedure in Editing the Settings of a
Radio User on page 54, and in step 3, select the Short Data Enabled checkbox, which allows the radio user to
have access to the short data service.
3 Click OK to close the window when finished.
Configuring Ambience Listening

The Ambience Listening (AL) feature is a type of private call initiated by the console only. Ambience Listening
allows a console position operator to hear audio activity occurring at a single radio, without giving any indication to
the radio user. Ambience Listening call does not time out or end because of an audio activity timer, unlike regular
individual calls.
Process:
1 Enable radio users for Ambience Listening. See Enabling Radio Users for Ambience Listening on page 97.
2 Enable console users for Ambience Listening. See Enabling Console Users for Ambience Listening on page 97.
Enabling Radio Users for Ambience Listening

Perform the following procedure to enable the Ambience Listening feature via Web NM for the Radio User
Note: The Ambience Listening Monitoring Enabled parameter is enabled for radio users per default. In
case it is not, perform the following procedure.
Procedure:
• If you want to enable the feature for a new Radio User, perform the procedure in Adding a Radio User to the
System on page 53, and in step 3, select the Ambience Listening Monitoring Enabled checkbox, which
enables the dispatch console to monitor the specific radio user.
• If you want to enable the feature for the existing Radio User, perform the procedure in Editing the Settings of a
Radio User on page 54 and in step 3 select the Ambience Listening Monitoring Enabled checkbox, which
Enabling Console Users for Ambience Listening


98 | Operation
Perform the following procedure to enable the Ambience Listening feature via Web NM for the Console User.
Note: The Ambience Listening Monitoring Enabled parameter is enabled for radio users per default. In
case it is not, perform the following procedure.
Procedure:
1 From the main menu, select Configurationand thenConsole User.
•If you want to enable the feature for a new Console User, perform the procedure in Creating a Console User
on page 76 and in step 3 select the Ambience Listening Monitoring Enabled checkbox, which enables the
dispatch console to monitor the specific radio user.
Console User on page 77 and in step 4 select the Ambience Listening Monitoring Enabled checkbox, which
Configuring Full Duplex Private Calls

The full duplex private call is a call in which an audio flows concurrently in both directions, that is the user both
receives and transmits (listen and talk) at the same time. The full duplex private call service allows two parties in the
system to communicate using full duplex speech in three different ways:
• Radio to console: (This call is initiated by a radio to a dispatch console).
• Console to mobile: (This call is initiated by a dispatch console to a radio).
• Radio to radio: (This call is initiated by one radio to another radio).
Figure 62: Example of a Full Duplex Call
TX 851.0125 MHz RX 806.0125 MHz
RX TX
Full duplex communication uses two frequencies: receive (RX) and transmit (TX).
Both the send path and the receive path of the console are open. Therefore, the console operator can talk and listen at
the same time, when push to talk is active. Push to talk works as a microphone mute switch. Operator should latch the
push to talk button (a function of the Plantronics headset amplifier) so that push to talk is active for the duration of the
call. Operator can release push to talk to mute the microphone for privacy reasons.
Both parties experience full duplex conversation if the console microphone is not muted during the conversation.
They can talk and listen at the same time. The background noise at one terminal is continuously and with no variation
in attenuation heard by the user of the other terminal. The ability to interrupt and ease of conversation is excellent.
The resulting communication efficiency is good even for untrained users.
Full Duplex Individual Calls can be enabled or disabled through the Web NM. To set up the Full Duplex Individual
Call feature for your system, see Enabling Radio Users for Full Duplex Private Calls on page 99.

Operation | 99
Enabling Radio Users for Full Duplex Private Calls

Perform the following procedure to enable the Full Duplex feature via Web NM for the Radio User:
Note: The Full Duplex Enabled parameter is enabled for radio users per default. In case it is not, perform
Procedure:
•If you want to enable the feature for a new Radio User, perform the procedure in Adding a Radio User to the
System on page 53, and in step 3 select the Full Duplex Enabled checkbox, which enables the dispatch
console to monitor the specific radio user.
Radio User on page 54, and in step 4 select the Full Duplex Enabled checkbox, which enables the dispatch
console to monitor the specific radio user.
Configuring Preemptive Priority Calls

The Preemptive Priority Call (PPC) feature allows enabled talkgroups, multigroups, and radio users to be given
higher priority for the allocation of traffic resources. It ensures that routine traffic does not block important
communications. High priority calls are not lost by participants roaming into a new site where lower priority calls
occupy all traffic channels.
The Preemptive Priority Calls (PPC group or individual) have preference in resource allocation at call set-up and
roaming. When setting up or restoring a PPC call, if traffic resources are available, the PPC call is set up/restored as
normal calls. However, if traffic channels are not available, the system conducts resource preemption to preempt the
necessary resources from normal voice calls of lower priority for the PPC call.
The PPC call also has preference at busy conversion. If no resources can be preempted at the site to set up or restore a
PPC call, the call is queued. When resources become available, the PPC call gets the resource prior to any existing
normal calls in queue.
In terms of traffic resource allocation, PPC calls have a higher priority compared to normal voice calls, but it is
inferior to emergency calls. Emergency calls can preempt traffic resources used by PPC calls and normal calls but not
vice versa. If in a situation whereby traffic resources at a site are all occupied by emergency calls, any subsequent
emergency calls, PPC calls, and normal calls are put in a busy queue. When resources are available, emergency calls
are busy-converted first, then followed by PPC calls and lastly, normal calls.
For all entities, the PPC feature can be provisioned in one of two ways:
• SwMI invoked, which means that the feature is always active.
• User invoked, which means that the Radio User/Console User can control whether to use the feature or not.
Setting Priority Levels

To make the PPC feature work, configuring the priority level of talkgroups/multigroups and radio users must be done
properly. The priority level is an important factor to determine the priority of a call when it is processed (including
resource allocation). The higher priority level a call has, the more likely it gets a resource when it is set up or restored
and less likely its resource is preempted.
Several parameters exist regarding the priority level of different call types:
• Dispatch Priority Level in the Talkgroup/Multigroup Capabilities Profile object. This is the priority at which
dispatch call request is served by the system.

100 | Operation
• Dispatch Priority Level in the Radio User Capabilities Profile object. This is the priority level at which the radio
user dispatch/private call requests is served by the system.
• Priority Level in the Radio User Interconnect Profile object. This is the priority at which the request of a radio
user for interconnect calls are served by the system.
All parameters can be set from a value ranging from 2 to 10 through the Web NM. The highest Priority Level, value
1, is reserved for emergency calls.
Enabling a Talkgroup/Multigroup for PPC

This procedure is meant for talkgroups/multigroups that are already added to the system. You can also enable the
Preempt Capable parameter when adding a new talkgroup/multigroup.
Procedure:
1 On the Configuration page, select Talkgroup/Multigroup.
The associated list of records appears in the Information frame.
2 Select relevant talkgroup/multigroup record.
3 Click Modify.
The associated Modify Talkgroup/Multigroup page appears.
Figure 63: Modify Multigroup Page
4 Select the Preempt Capable parameter to enable the PPC feature.

5 When finished, click OK to save the changes and return to the previous page.
Enabling a Radio User Capabilities Profile for PPC

Procedure:
2 Select the relevant Radio User Capabilities Profile record.

Operation | 101
3 Click Modify.
The Modify Radio User Capabilities Profile page appears.
Figure 64: Modify Radio User Capabilities Profile Page
Note: The Radio User Capabilities Profile Alias, Radio User Capabilities Profile ID fields are
grayed out.
4 Set Called User Preemption according to the dispatch capability of this range of radio users.
• SwMI Invoked means that the feature is always active.
• User Invoked means that the Radio User may select to use the feature or not at runtime.
• Disabled means that all individual calls initiated by the radio user never preempt the called user.
5 When finished, click OK to save the changes and return to the previous page.
Configuring Status Transfer Service

Status Transfer Service (STS) is a console feature that allows a radio to relay its present status without having to use
voice communication. It provides communication efficiency for predefined messages.
It saves time and provides communication efficiency in high-density areas. Customers use STS to use their field
resources (people and/or vehicles) efficiently by providing automated means of tracking their condition or state. For
example, it allows the user to send predefined Status Messages such as "on duty" or "returning to base" to the
dispatcher. The STS feature provides a quick, easy-to-use overview of the current disposition of the resources. It
helps the console operator to decide how to respond to new incidents.
For configuration details on setting up the Status Transfer Service, see Editing the Status Set Messages on page 78.
Common Secondary Control Channel (C-SCCH) Configuration

The communication over the air in the Dimetra IP Micro/Dimetra LiTE system is structured into channels which are
used for voice, data or control. The Common Secondary Control Channel (C-SCCH) feature is related to the control
channel(s) where the feature allows significant expansion of control channel capacity by changing the use of a
channel from voice or data to control information.
C-SCCH feature is useful in areas with high density MS populations configured with sites with a high number of base
radios. In such cases, sites require sufficient number of Common Control Channels (CCCH) bandwidth in order to
support high load of mobility management operations, voice call setups, and short data transmissions. CCCH
consisting of only one Main Control Channel (MCCH), in some cases, may have not been sufficient for the system to
work properly. Thus, C-SCCH allows to increase the possible capacity on sites.
Due to C-SCCH, it is possible to configure 01 Secondary Control Channels (SCCHs) on the main carrier for the
purposes of common control signaling. Each SCCH occupies one slot on the main carrier. The channels are added in
consecutive slots at the main carrier (for example if there is one Common SCCH available at a site it shall occupy slot
2 of the main carrier). As the number of common control channels increases, the bandwidth available for common

102 | Operation
control signaling is also expanded, so the given site can support more users at the same time, as well as provide
extended bandwidth in excessive roaming scenarios. The channel can be setup on a site that has a feature license
provided. Note that the C-SCCH feature is able to increase the possible capacity on sites, but it does not increase the
number of channels which may be handled in a zone, for example the latter number is kept at the existing level.
To sum up, the advantages of the C-SCCH are the following:
• Increased bandwidth for individually addressed signaling
• Better system resilience in overload cases (which can happen during mobility flooding, when number of users try
to register at the same site)
• Bigger maximal site capacity more radios can be served on the same site as more control traffic capacity can be
made available.
• Since the number of channels can be changed dynamically, the system operator can modify the settings to best suit
current work profile of the site
• Possibility to spread the radios over the different common control channels to make sure that the generated control
channel load is evenly distributed.
An integral part of the C-SCCH feature are the load classes, which help the operators to determine the right moment
to increase or decrease the number of Common Secondary Control Channels. Load class is associated with a specific
radio and defines a class (type) of radios which have given expected contribution to the load on CCCH. Each radio
that registers on the system, has a default load class set with the associated load class weight Default Radio. You can
select any predefined load class when configuring the Radio User Capabilities Profile.
For more details on the initial configuration of the feature, see the User Configuration Manager, and Zone
Configuration Manger manuals.
Configuring Common Secondary Control Channel (C-SCCH)

Use the following procedure to configure the C-SCCH using the Web NM.
Note: Note that the procedure is applicable to System, Radio User Capabilities Profile, and MTS Site
records that have already been created.
Procedure:
The system configuration records appear in the Information frame.
2 Select the relevant system record (SYSTEM1 has been created by default for your during the initial system
configuration) for which you want to enable the C-SCCH services.Click Modify.
The Modify System page appears (see Figure 59: Modify System Page on page 93).
3 Enable the System Ready for C-SCCH parameter.
Note: The C-SCCH can be enabled only when a dedicated license has been purchased.
values.
4 Click Apply to save the settings.
The Common Secondary Control Channel features is turned on.
5 Select the Radio User Capabilities Profile menu item.
The Radio User Capabilities Profile configuration records appear in the Information frame.
6 Select the previously created radio user capabilities profile for which you want to set the load class. Click Modify.

Operation | 103
Note: When creating a Radio User Capabilities Profile, by default the Default Radio load class is
assigned to a specific radio user that registers on the system.
The Modify Radio User Capabilities Profile page appears (see Figure 12: Modify Radio User Capabilities
Profile Page on page 51).
7 Select the load class for a specific radio from the Load Class Name field. The following are available: Default
Radio, Stationary Radio, High Activity Radio, Very High Activity Radio.
8 Click Apply to save the setting.
The load class has been set for a specific radio user.
9 Select the MTS Site menu item.
The MTS site configuration records appear in the Information frame.
10 From the list of previously created sites, select the one you want to set the number of secondary control channels
for.Click Modify.
The Modify MTS Site page appears (see Figure 50: Modify MTS Site Page on page 84).
11 Enter the number of secondary control channels for the selected site in the Number of C-SCCH field. You can set
01 C-SCCH.
Note: The number of channels is limited by the C-SCCH license. If the license is available, you can set
the number of C-SCCHs on the site.
Important: Use these parameters with caution as C-SCCH licenses are non-retrievable.

The control channels are set.
Configuring Authentication and Air Interface Encryption

Authentication is used to verify that a radio accessing the system is valid, and to reject any unauthorized parties from
accessing the system. The Dimetra IP Micro/Dimetra LiTE system uses a challenge-response-result protocol to
authenticate both the radio and the infrastructure.
Air interface encryption provides security for RF signaling between the infrastructure and radios. Air interface
encryption is achieved by using a common encryption key in both an infrastructure base station and a radio, allowing
the devices to encrypt traffic and decrypt traffic from one another. Air interface encryption can be applied to control,
voice, and data traffic. Options can be purchased to support TETRA Encryption Algorithm 1 (TEA1), TETRA
Encryption Algorithm 2 (TEA2) or TETRA Encryption Algorithm 3 (TEA3).
For details on the Authentication and Air Interface Encryption features, and key details, see the Managing
Authentication, Encryption, and Provisioning manual.
values.
Note: The Authentication and Air Interface Encryption (AIE) features are configurable only if dedicated
licenses have been purchased.

Note: Note that the following procedure is applicable to MTS Sites and System records that have already
been created.

104 | Operation
Use the following procedure to configure the Authentication and Air Interface Encryption services using the Web
NM:
Procedure:
The system configuration records appear in the Information frame.
2 Select the relevant system record (SYSTEM1 has been created by default for your during the initial system
configuration), for which you want to enable the C-SCCH services, and click Modify.
The Modify System page appears (see Figure 59: Modify System Page on page 93).
3 Select the Authentication Enabled checkbox to turn on the authentication for the system.
4 Select the Air Interface Encryption checkbox to turn on the air interface encryption for the system.
5 In the TETRA Encryption Algorithm, select the algorithm type that you want the system to use for encryption:
TEA1,TEA2,TEA3.
6 Optional: Select the Secure DMO OTAR Enabled checkbox if you want to have the DMO Static Cipher Key
enabled.
Note: The DMO OTAR Enabled parameter is active with a valid license which has to be purchased,
and Air Interface Encryption functionality enabled.
7 In the Encrypted Radio ID Start Address field, enter a valid address for Static Cipher Key (SCK) encryption.
8 In the Encrypted Radio ID End Address field, enter a valid address for Static Cipher Key (SCK) encryption.
9 Select the Encrypted Broadcast Cell Information checkbox, if you want a neighboring cell and security related
information to be broadcast encrypted by the system.
12 Select the relevant MTS site record for which you want to set the appropriate security classes, and click Modify.
The Modify MTS page appears (see Figure 50: Modify MTS Site Page on page 84).
13 Configure the necessary security classes:
• Enable the Security Class 2 only MS Supported field to allow radios supporting security class 2 to register
on the system.
• Enable the Security Class 3 MS Enabled field in order for the selected MTS site to work in Security Class 3
mode.
Note: This parameter activates the SC3G Encryption Enabled parameter only when valid license keys
are installed.
Note: In order to display the status of the security class on the site (if necessary), use the telnet session.
Log to the site <x>,
where <x> is the site number,
using your username if your are logging on from the console or Network Management Terminal (if
supported by your system), or your IP address if you are logging on from the service PC. Use the
status sec command to display the used security class on the specified site.
The authentication and air interface encryption functionality have been set.

Operation | 105
Configuring Packet Data

The Packet Data Service (PDS) is a bearer service that allows IP hosts to communicate using the Internet Protocol
(IP). It is used to transport various types of data files in the system. For details on the packet data feature, see the Data
Subsystem manual.
When and where to use: The Packet Data functionality is configurable only if a dedicated license has been
purchased. Additionally, the Tetra Enhanced Data Services (TEDS) license is required.
Note: Note that the following procedure is applicable to radio users that have been already created. The
same rule applies to the MTS sites.
Procedure:
The radio user configuration records appear in the Information frame.
2 From the list of previously created radio users, select the one for which you want to enable the Packet Data
functionality, and click Modify.
The Modify Radio User page appears (Editing the Settings of a Radio User on page 54).
3 Select the Packet Data Enabled checkbox to enable the packet data service essential for distributing data within
the system.
4 Select the QAM Data Enabled checkbox to set the QAM type used for modulating data signals onto a carrier.
Note: The QAM Data Enabled parameter is configurable if a dedicated license (Tetra Enhanced Data
Services) has been purchased.
5 In the Assigned IP Addresses field, enter the IP address that can be used by the radio user when connecting a
computer to the radio.
6 Select the Multislot Packet Data Enabled checkbox to enable the radio user to access the multi-slot packet data
service.
9 Select the relevant MTS site record for which you want to set the appropriate packet data parameters, and click
Modify.
The Modify MTS page appears (see Figure 50: Modify MTS Site Page on page 84).
10 Verify that the following parameters have been set according to your needs:
• MTS Type
• Number of Base Radios
These parameters must be set so that the QAM Base Radio, and QAM Modulation parameters can be
configured.
11 From the drop down list of the QAM Base Radio, specify the TEDS capable base radio.
This parameter activates the QAM Modulation field if a specific base radio is selected. For example, setting the
QAM Base Radio to Third, means that the third base radio will be set to the QAM 25/50 channel operation mode,
and the rest of the base radio for this MTS site will be set to the PM channel operation mode. Setting QAM Base
Radio to None results in all the base radios for this MTS running in the PM operation mode.
Note: The QAM Base Radio parameter is configurable only if a dedicated Tetra Enhanced Data
Services (TEDS) license has been purchased.
12 In the QAM Modulation field, select the channel operation mode for a determined base.
13 In the Max Number of Dynamic Single Slot Data Channels field, select the maximum number of channels on
the site that may be allocated as dynamic single slot packet data channels (0 to 10).

106 | Operation
14 In the Max Number of Dynamic Multi Slot Data Channels field, select the maximum number of channels on
the site that may be allocated as multi slot packet data channels (0 to 7).
Note: When configuring the number of multi slot packet data channels, it is also crucial to take into
account the maximum width of multi slot packet data channels. This is configurable via the Advanced
NM, in the Zone Configuration Manager application, using the Max Width of Multi Slot Packet Data
Channel parameter which is set by default to 4. This is done during the initial configuration of the
system.
The packet data functionality has been set.
Administration Management
Note: It is recommended not to open multiple windows with administration management within the same
web browser session. This applies especially to administration operations with progress window, for
example:
• backup/restore
• software update
• network configuration update
If multiple windows with these operations are opened, then progress messages in these windows may be
misplaced between the windows.
Performing Backup and Restore

The following parts are used to perform the backup and restore actions on an actual server.
Important: Backups of the system must be taken after changes are made to the database to ensure that
restoration can be made in the event of a failure with minimal loss of information and operation of the
system.
Backup
The Backup button is responsible for starting the backup of the UCS (User Configuration Server), ZDS (Zone
Database Server), ATR (Air Traffic Router), ZC (Zone Controller), MTIG-IP (Motorola Telephone Interconnect
Gateway ), SDR (Short Data Router), PDR (Packet Data Router if present in the system) and AuC (Authentication
server if present in the system) database and compressing the file into one.
When and where to use: To obtain the last backup file to the PC, download it using the Download button. To
perform the backup, perform the following procedure.
Procedure:
1 On the Administration page, select Backup and Restore.

Operation | 107
Figure 65: Backup and Restore Configuration Page
The Backup and Restore configuration page appears.

2 Click Backup on the Backup and Restore configuration page.
The Backup Command page appears (the content presented in the figure serves as an example).
Figure 66: Backup Command Page
Note: For button descriptions, see Table 39: Command Buttons of the Backup Command Page and
Restore Command Page on page 189.
Note: Depending on the type of application servers your system is supporting, appropriate backup will
be performed.
3 Click Start.
Note: If you want to clear the progress messages, click Clear.

108 | Operation
Note: Note if any errors appear. If so, contact the technician for support.
The backup is initiated (see figure from step 2).

4 Click Back to go to the previous Backup and Restore configuration page.
A list of the backup files appears in the Backup and Restore configuration page.
Note: In case you do not see the updated list of backup files in the Web NM, click the Refresh button.
5 Select the file you want to use as backup from the list.
6 Click Download.
7 Save the selected backup file onto your PC.
The files are downloaded from the WAS server to your PC.
Post requisites: Continue to Restore on page 108.
Restore
This part is used for restoring the servers. The restore uploads the backup file from the PC, running the browser to the
WAS server and onto the actual server being restored.
Procedure:
1 From the Administration page, select Backup and Restore.
The Backup and Restore configuration page appears.

Operation | 109
2 To upload the files to the WAS server:
If… Then…
If the files are stored on the go to step 3.
WAS server,
If the files are stored on 1 Click Upload to upload them to the WAS server and in the upload page spec-
your PC, ify the name of the files to be uploaded and click Upload.
2 Click Back to return to the previous page (Backup and Restore).
3 Continue to step 3.
Note: In case you do not see the updated list of backup files in the Web NM, click Refresh.
The files are uploaded to the WAS server.

3 From the list of the backup files visible in the Backup and Restore page, select the file you want to use for
restore.
4 Before continuing to the next step, ensure that the servers, UCS, ZDS, MTIG-IP, ATR, ZC, SDR, PDG (if present
in the system) and AuC (if present in the system) are disabled. You can enable/disable the servers using the
System Administrator Main Menu. See Service Manual on how to perform this or contact your technician.
5 Click Restore.
The Restore of the Backup File Command page appears (the content presented in the figure serves as an
example).
Warning: Perform this step cautiously as restoring the system configuration impacts the system
operation.

110 | Operation
Figure 69: Restore of the Backup File Command Page
6 From the Restore of the Backup File Command page, select Start, which initiates the restore of the backup
files.
The restore of the servers is initiated (see Figure 69: Restore of the Backup File Command Page on page 110).
Note: For the button descriptions, see Table 39: Command Buttons of the Backup Command Page and
Restore Command Page on page 189.
7 When the restore of the backup files ends, click Back to go to the previous page.
Post requisites: After the restore, the servers must be enabled. See the Service Manual or contact your technician for
this information.
Accessing the Servers

This part provides information on accessing the Integrated Lights Out Management (ILOM)/ Integrated Lights-Out
(iLO) for the server management and console access. Depending on the hardware type you are using perform the
appropriate procedure.
Note: The following procedures contain steps which are done by a technician. Contact your technician for
support.
Accessing the SunFire X4170 Server

Note: Accessing the servers via ILOM requires having it properly setup and configured. For details on this
configuration, see the Service Manual.
Procedure:
1 From the Administration page, select Server Connection.
The Server Connection page appears.

Operation | 111
Figure 70: Server Connection Page
2
If… Then…
If you do not have the Java Runtime Environ- 1 Perform Downloading Support Files from the Server on
ment (JRE) installed on your PC, page 134.
2 After the Java software is downloaded to your PC, con-
tinue to step 3.
If you have the Java Runtime Environment Continue to step 3.

(JRE) installed,
Note: The Java Runtime Environment version is checked when starting up the Integrated Lights Out
Manager (ILOM) Remote Session. The ILOM Remote Console requires Java version 6 to be installed
on your PC. If you do not have it installed, then an error message will pop up informing you about this.
The Download page appears.
3 Click Connect.
The Integrated Lights Out Manager window opens.

112 | Operation
Figure 71: Integrated Lights Out Manager Log In Window
4 Type admin in the User Name field, type the corresponding password in the Password field, and then click Log
In.
You are logged into ILOM.
5 Select the Remote Control tab, then the Redirection tab and click Launch Redirection.
Important: This procedure is only recommending the use of the Remote Control tab for accessing the
Administration menus of the Servers. Use the other tabs only when you are instructed to do so by the
technician.
The Warning Security window appears, informing that the digital signature of the application cannot be verified.
6 Click Run.
Various startup messages appear, and then the z001igas01 console login prompt appears.
7 Type sysadmin and press ENTER.
You are prompted for a password.
8 Type the password and press ENTER.
The Generic Application Server startup screen appears and you are asked to enter your first and last name.
9 Type your first and last name and press ENTER.
You are asked to enter your CSR#. This number is the number of the customer reported error case, which is the
reason for the service action to take place.
10 Type your CSR number.
You are asked to enter a reason for accessing the server.
11 Type a short description of why you want to access the server.
As stated on the screen, you must type a full stop in the left-most position of a line to end the description.
The System Administrator Main Menu appears, which enables you to access the servers.
System Administrator Main Menu

1. Enable all Application Servers

Operation | 113
2. Disable all Application Servers

3. Display Status of all Application Servers
4. Unix Administration
5. Application Servers Administration Menus
6. Application Servers Boot/Reboot/Shutdown
7. Application Servers Status Administration
Please enter selection: (17, q) [q]:
12 Perform all the necessary actions within the accessible devices by typing the appropriate number and log out after
you finish by pressing ENTER. You can, for example, enable or disable the servers (see Service Manual for details).
Accessing the ProLiant DL360 G7 Server

Procedure:
1 From the Administration page, select Server Connectionand click Connect.
A warning message informing on an incorrect security certificate may appear. The exact look of the message
depends on the browser you are using, and the actions required to continue with the connection may be different.
In the example shown here (for Internet Explorer), click Yes. The Integrated Lights-Out window appears.
Figure 72: Security Alert Window (Example for Internet Explorer)

114 | Operation
Figure 73: Integrated Lights-Out Log In Window
2 Type admin in the User Name field, the corresponding password in the Password field, and click the Sign In
button.
You are logged into iLO, and the iLO Overview window appears.
Figure 74: Integrated Lights-Out Overview Window
3 Expand the Remote Console item in the left pane, and click Remote Console underneath.
The Remote Console window appears.

Operation | 115
Figure 75: Integrated Lights-Out Remote Console Window
4 Check that you have Java installed in your browser (see your browser documentation). On the Java tab, you can
find information on the minimum Java version required, and you can find links to download Java.
If you do not have the correct Java version installed, you must close the browser, install Java, and connect to iLO
again.
Note: The following software is needed:
• Microsoft .NET Framework 3.5, or

• JavaTM Runtime Environment Std Edition 1.4.2_13 as minimum or recommended 6.0. To install Java perform
Downloading Support Files from the Server on page 134.
Important: If you use the MCC 7500 console PC for logging on to iLO, you must configure Internet
Explorer to allow Java Integrated Remote Console on the PC (see Service Manual for details).
5 If you have the correct Java version installed, click Launchin the Java Integrated Remote Console link on the
Launch tab.
Some security warnings may appear, asking if you want to run the application. If these warnings appear, confirm
them. After a while, a window containing various start up messages followed by the z001igas-dipm login
prompt appears.
Note: If a message appears, telling that you need a license, you must install your iLO license:
• Expand the Administration item in the left pane of the Integrated Lights-Out Overview window,
and click Licensing.
• In the Activation Key field, type the iLO license key that came with your server, and click Install.
• Then click Remote Console again.

116 | Operation
Figure 76: Integrated Lights-Out Licensing Window
6 At the z001igas-dipm login prompt, type sysadmin and press ENTER.

7 Type the password and press ENTER.
The Generic Application Server start up screen appears and you are asked to enter your first and last name.
8 Type your first and last name and press ENTER.
10 Type a short description of why you want to access the server.
As stated on the screen, you must type a full stop in the left-most position of a line to end the description.
The System Administrator Main Menu appears, and you can access all the server menus.
11 Perform all the necessary actions within the accessible devices by typing the appropriate number and log out after
you finish by pressing ENTER. You can, for example, enable or disable the servers (see Service Manual for details).
Changing the Password

This part instructs you how to change the password for a previously configured user.
Note: It is advisable to change the default password for security assurance. Only the supermgr user allows
for changing the passwords for other users.
Procedure:
1 From the Administration page, select Change Password.
The Change Password page appears.

Operation | 117
Figure 77: Change Password Page
2 Fill in the Username, Old Password, New Password, and Confirm New Password fields according to Table 40:
Parameters for the Password on page 190.
3 Click OK to save the changes.
Performing Software Update

This part displays information on the software update via Web NM.
Figure 78: Software Update Page
Uploading and Updating the Software

This part is used for uploading and installing the new software. It is possible to perform software update separately
for a local IP network devices (using the Update button), and for remote control site (by using the Update Remote
button). Server and firmware types of upgrade is supported (for remote control site devices if reachable and
configured, only firmware type).

118 | Operation
Note: This part is not applicable when a new Dimetra IP Micro/Dimetra LiTE system is installed. Use it
only in cases when the system upgrade is necessary. The software update files are delivered by Motorola on
a DIPM R2.0 to R3.0 Upgrade Disc.
Procedure:
1 From the Administration page, select Software Update.
The Software Update page appears.
2 From the Software Update page, click Upload.

The upload page appears.
Figure 80: Upload Page
3 Click Browse, and in the upload page specify the name of the file to be uploaded to the WAS server. Then click
Upload (a progress bar allows you to follow the operation).
Note: In case you do not see the updated list of software update files in the Web NM after the upload,
click Refresh.
4 Select the file that you want to update, and click Update for a local core server, router and switch, or Update
Remote for a remote control site (if reachable and configured).
The Confirm dialog box appears.
5 In the Confirm dialog box, click Yes.
The Software Update Command page appears.
Warning: The update of the software discontinues the operation of the servers temporarily.

Operation | 119
Figure 81: Software Update Command Page
6 In the Software Update Command page, click Start.

The software update has been initiated.
7 Click Back to go to the previous page when finished.

8 Verify that uploaded file is active – a tick is visible in the Active/Active Remote field.
Downloading the Software Update Files

The following procedure explains how to download the software update files to you PC.
Procedure:
Figure 82: Software Update
2 Select the software update file you want to download and click Download.
A File Download window appears.
3 Click Save to save the files on your PC in the desired location, or Open to view the software update files details.

120 | Operation
Deleting the Software Files

The following procedure explains how to delete the software update files.
Procedure:
2 Select the file you want to remove.

3 Click Delete.
Note: In case you do not see the updated list of network configuration files in the Web NM, click
Refresh.
The selected network configuration files are removed from the WAS server.
Managing Network Configuration Files

This part displays information on the network current IP configuration on various devices, such as switches and
routers. Default network configuration files are provided by Motorola Solutions, and can be used as templates (as
seen in the following figure). These network configuration files can be downloaded to your PC, which later can be
modified according to you needs and applied to your devices.

Operation | 121
Figure 84: Network Configuration Page
For network configuration guidelines, see Network Configuration File Guidelines on page 199.
Downloading the Network Configuration Files

The following procedure explains how to download the network configuration files to you PC in order to set the IP
network according to your system preferences. Such modified network configuration files can be uploaded to WAS
and later applied to your devices.
For network configuration guidelines, see the Network Configuration File Guidelines on page 199.
Procedure:
1 From the Administration page, select Network Configuration.
The Network Configuration page appears.
2 Select the network configuration template you want to download and click Download.
A File Download window appears.

122 | Operation
3 Click Saveto save the files on your PC in the desired location, or Open to view the network configuration files
details.
Applying the Configuration for a Local/Remote Site

This part instructs you how to apply the network configuration that was stored in the network configuration files. It is
possible to apply the network configuration update separately to a core router and switch (by using the Apply button),
and to a remote control site (by using the Apply Remote button).
Warning: Perform this procedure cautiously as it impacts the system operation. Incorrect network
configuration may impact connections to the RF-Site, the SDR hosts and the Telephony Gateway.
For network configuration guidelines, see the Network Configuration File Guidelines on page 199.
Procedure:
2 On the Network Configuration page, click Upload.

The upload page appears.
Figure 87: Upload Page
3 In the upload page click Browse, specify the name of the file to be uploaded and click Upload (the progress bar
allows you to follow the operation).

Operation | 123
Note: In case you do not see the updated list of the network configuration files in the Web NM, click
Refresh.
The files are uploaded to the WAS server.

4 Click Back to navigate to the previous page.
The list of network configuration files appears in the Web NM.
5 Select the network configuration template you uploaded, and click Apply for a core router and switch
configuration update, or the Apply Remote button for remote control site configuration update.
The Confirm dialog box appears.
6 In the Confirm dialog box, click Yes.
The Network Configuration Command page appears (the content presented in the figure serves as an example).
Figure 88: Network Configuration Command Page
7 In the Network Configuration Command page, click Start.

The generation of the selected network configuration file has been initiated.
Warning: Use this button cautiously as it impacts the system operation.
Note: If you want to clear the progress messages click the Clear button.
8 Click Back to go to the previous page when finished.

9 Verify that uploaded file is active – a tick is visible in the Active/Active Remote field.
Deleting the Network Configuration Files

Procedure:

124 | Operation
2 Select the file you want to remove.

3 Click Delete.
Note: If you do not see the updated list of network configuration files in the Web NM, click Refresh.
The selected network configuration files are removed from the WAS server.
Downloading ATIA Logs

The Air Traffic Information Access (ATIA) logs are log files that are generated by the Air Traffic Router (ATR).
These log files contain records of all recent zone activity, such as site registrations and processed calls. You can
download them via the Web NM.
The ATIA log files are not in a readable format but can be used by Motorola support to analyze call and affiliation
behavior when troubleshooting. ATIA log files can be opened by the ATIA Log Viewer that is part of the Private
Radio Network Management (PRNM) Suite application.
Important: The following procedure is used only when you identify a problem, such as a radio or a device
is not working, and you are asked by a third-party support to perform the steps described below.
Process:
1 To view the ATIA logs, ATIA Call Logging Parameter must be enabled on the ATR server via the ATR Server
Administration menu. Depending on the hardware type you are using perform the following procedure:
• For SunFire X4170, perform Enabling the ATIA Call Logging for SunFire X4170 via the ATR Server on page
124.
• For ProLiant DL360 G7, perform Enabling the ATIA Call Logging for ProLiant DL360G7 via the ATR Server
on page 127.
2 Perform Downloading ATIA Log Files on page 131.
Enabling the ATIA Call Logging for SunFire X4170 via the ATR Server
Procedure:
1 Go to the Administration page and from the submenu select Server Connection. Click Connect.

Operation | 125
The Integrated Lights Out Manager window appears.
Figure 90: Sun Integrated Lights Out Manager Log In Window
2 Type admin in the User Name field, type the corresponding password in the Password field, and then click Log
In.
You are logged on to ILOM.
3 Select the Remote Control tab.
4 Select the Redirection tab and click Launch Redirection.
The Warning Security window appears, informing that the digital signature of the application cannot be verified.
5 Click Run.
Various start up messages appear, and then the z001igas01 console login prompt appears.
6 Type sysadmin and press ENTER.
7 Enter the password.
8 Enter your first and last name.
10 Type a short description of why you want to access the server. As stated on the screen, you must type a full stop in
the left-most position of a line to end the description.
The System Administrator Main Menu appears, and you can access the ATR.


126 | Operation
Please enter selection: (17, q,) [q]:
11 Type 5 to select Application Servers Administration Menus menu and press ENTER.
The Application Servers Administration Menus menu appears.
Application Servers Administration Menus

1. Zone Controller (zc01.zone1)
2. Zone Database Server (zds01.zone1)
3. Air Traffic Router (atr01.zone1)
4. User Configuration Server (ucs01.ucs1)
5. Motorola Telephone Interconnect Gateway (mtig_ip01.zone1)
6. Short Data Router (sdr01.zone1)
7. Packet Data Router (pdr_A.zone1)
8. Radio Network Gateway (rng_A.zone1)
Enter Selection: (1-8, q) [q]:
12 Type 3 to select Air Traffic Router (atr01.zone1) and then press ENTER.
The ATR main menu appears.
Main Menu
1. Enable ATR Server
2. Disable ATR Server
3. Display Server Status
4. Server Administration
5. ATIA Call Logging Parameter Setup
6. ATIA Unicast Configuration
7. Radio Control Manager Export Setup
8. Routes Configuration
q. Quit
Enter Selection: (1-8, q)
Note: In order to access the Air Traffic Router you need to enter a password.
13 Type 5 to select ATIA Call Logging Parameter Setup and press ENTER.
The ATIA Call Logging Parameter Setup menu appears.
Note: The ATR is enabled by default.
ATIA Call Logging Parameter Setup

1. Enable ATIA Call Logging
2. Disable ATIA Call Logging
3. Display ATIA Call Logging Status
h. Help
b. Back to Previous Menu
q. Quit
Enter Selection: (1-3, h, b, q):
14 Type 1 and press ENTER.

The following message appears: The status is: enabled.
15 Type q and press ENTER repeatedly until you are logged out.
Post requisites: Continue to Downloading ATIA Log Files on page 131.

Operation | 127
Enabling the ATIA Call Logging for ProLiant DL360G7 via the ATR Server
Procedure:
1 From the Administration page, select Server Connection and click Connect.
A warning message informing on an incorrect security certificate may appear. The exact look of the message
depends on the browser you are using, and the actions required to continue with the connection may be different.
In the example shown here (for Internet Explorer), click Yes. The Integrated Lights-Out window appears.
Figure 91: Security Alert Window (Example for Internet Explorer)
Figure 92: Integrated Lights-Out Log In Window
2 Type admin in the User Name field, type the corresponding password in the Password field, and then click Sign
In.
You are logged into iLO, and the iLO Overview window appears.

128 | Operation
Figure 93: Integrated Lights-Out Overview Window
3 Expand the Remote Console item in the left pane, and click the Remote Console item underneath.
The Remote Console window appears.
Figure 94: Integrated Lights-Out Remote Console Window
4 Check that you have Java installed in your browser (see your browser documentation). On the Java tab you can
find information on the minimum Java version required, and you can find links to download Java.
If you do not have the correct Java version installed, you must close the browser, install Java, and connect to iLO
again.

Operation | 129
Note: The following software is needed:

• Microsoft .NET Framework 3.5, or
• JavaTM Runtime Environment Std Edition 1.4.2_13 as minimum or recommended 6.0. To install
Java perform Downloading Support Files from the Server on page 134.
Important: If you use the MCC 7500 console PC for logging in to iLO, you must configure Internet
Explorer to allow Java Integrated Remote Console on the PC (see Service Manual for details).
5 If you have the correct Java version installed, click Launch in the Java Integrated Remote Console link on the
Launch tab.
Some security warnings may appear, asking if you want to run the application. If these warnings appear, confirm
them. After a while, a window containing various start up messages followed by the login prompt appears.
Figure 95: HP ProLiant DL360 G7 - iGAS Login
Note: If a message appears, telling that you need a license, you must install your iLO license:
• Expand the Administration item in the left pane of the Integrated Lights-Out Overview window, and click
Licensing.
• In the Activation Key fields, type the iLO license key that came with your server, and click Install.
• Then click Remote Console again.
Figure 96: Integrated Lights-Out Licensing Window

130 | Operation
6 At the login prompt, type sysadmin and press ENTER.

7 Enter the password.
8 Enter your first and last name.
10 Type a short description of why you want to access the server. As stated on the screen, you must type a full stop in
the left-most position of a line to end the description.
The System Administrator Main Menu appears, and you can access the ATR.

Please enter selection: (17, q) [q]:
11 Type 5 to select Application Servers Administration Menus menu and press ENTER.
The Application Servers Administration Menus menu appears.
Application Servers Administration Menus

1. Zone Controller (zc01.zone1)
2. Zone Database Server (zds01.zone1)
3. Air Traffic Router (atr01.zone1)
4. User Configuration Server (ucs01.ucs1)
5. Motorola Telephone Interconnect Gateway (mtig_ip01.zone1)
6. Short Data Router (sdr_A.zone1)
7. Packet Data Router (pdr_A.zone1)
8. Radio Network Gateway (rng_A.zone1)
Enter Selection: (1-8, q) [q]:
12 Type 3 to select Air Traffic Router (atr01.zone1) and then press ENTER.
The ATR main menu appears.
Main Menu
1. Enable ATR Server
2. Disable ATR Server
3. Display Server Status
4. Server Administration
5. ATIA Call Logging Parameter Setup
6. ATIA Unicast Configuration
7. Radio Control Manager Export Setup
8. Routes Configuration
q. Quit
Enter Selection: (1-8, q):
Note: In order to access the Air Traffic Router, you need to enter a password.

Operation | 131
13 Type 5 to select ATIA Call Logging Parameter Setup and press ENTER.
The ATIA Call Logging Parameter Setup menu appears.
Note: The ATR is enabled by default.
ATIA Call Logging Parameter Setup

1. Enable ATIA Call Logging
2. Disable ATIA Call Logging
3. Display ATIA Call Logging Status
h. Help
b. Back to Previous Menu
q. Quit
Enter Selection: (1-3, h, b, q):
14 Type 1 and press ENTER.

The following message appears: The status is: enabled.
15 Type q and press ENTER repeatedly until you are logged out.
Post requisites: Continue to Downloading ATIA Log Files on page 131.
Downloading ATIA Log Files

To view and download the ATIA logs, perform the following procedure.
Procedure:
1 On the Administration page, click ATIA Logs.
The ATIA Logs page appears.
Figure 97: ATIA Logs Page
2 Select the log file from the list of logs you want to be downloaded to your PC.
Note: If there are no log files available, check if the ATIA logging is enabled (perform Enabling the
ATIA Call Logging for SunFire X4170 via the ATR Server on page 124 or Enabling the ATIA Call
Logging for ProLiant DL360G7 via the ATR Server on page 127).
3 Click Download to obtain the log files, and save them on your PC.

132 | Operation
Note: You can only download one log file at a time.
Collecting and Downloading Server Log Files

Important: The following procedure is used only when you identify a problem, such as a radio or a device
is not working, and you are asked by a third-party support to perform the steps described below.
Procedure:
1 From the Administration page, select Collect Log Files.
The Collect Log File page appears.
Figure 98: Collect Log File
2 Depending on the kind of logs you want to collect, click Brief (server log files without detailed information), or
Comprehensive (server log files with detailed information) to collect the log files. See Table 46: Command
Buttons for the Collect Log Files Page on page 195 for the descriptions of the buttons.
The Collect Log Files Command page appears (the content presented on the figure serves as an example).
Figure 99: Collect Log Files Command Page

Operation | 133
Note: Depending on the type of application servers, your system is supporting appropriate logs will be
collected.
3 Click Start to initiate the process of collecting logs.

The log files are downloaded to the Web NM. They are saved as archive files. It takes up to several minutes to
collect them.
4 Click Back and then select the log file from the list you want to download to your PC.
Note: In case you do not see the updated list of logs in the Web NM, click Refresh.
5 Click Download and specify the path where you want to store the file on your PC.
Performing Diagnostics
The Diagnostics page is used to diagnose general system behavior. It contains test scripts which allow you to check,
for example, the status of the application servers or the network connectivity.
The following scripts are supported:
• check.sh allows to check the status of all the application servers and component states, server memory usage and
network connectivity
• display_server_time.sh displays the date and time of the server
• version.sh allows to check and record the software versions of the system that are used
Procedure:
1 From the Administration page, select Diagnostics.
The Diagnostics page appears.
Figure 100: Diagnostics Page
2 Select the checkbox with the script you want to execute and click Run.
The Diagnostics Command page appears (the content presented on the figure serves as an example).

134 | Operation
Figure 101: Diagnostics Command Page
3 On the Diagnostics Command page, click Start to execute the script.

The script has been executed and you can see the result in the Diagnostics Command window.
4 Click Back to return to the previous page.
Downloading Support Files from the Server

Perform the following procedure to download a support file from the WAS server. For example you can download the
following files:
• jre-6u16-windows-i586.exe Java Runtime Environment file required in the server connection
• Notice.txt file containing legal notices
Procedure:
1 From the Administration page, select Downloads.
The Download page appears.
Figure 102: Downloads Page

Operation | 135
2 Select the file you want to download and click Download.

The download process is initiated.
Web Network Manager Version

You can check which version of the Web Network Manager you are using by selecting the Administration → About
menu item.
Figure 103: About Page

137 | Reference
Chapter
3
Reference
This part contains information on the fields and commands that are displayed in the Web NM. The information is
presented in the order it appears in the Information frame when you select a specific page. Each part contains a table
with descriptions of the fields visible in the page, including default and valid values for each field and the command
buttons.
Status Page
Figure 104: Status Page
The Status Page consists of the following menu items:

• Current Status on page 138 providing status information on the state/cause type of alarms.
• All Events Object on page 139 providing status information about the transient type of alarms.

138 | Reference
Current Status
Figure 105: Current Status Page
The following table presents descriptions of the Command buttons in the Current Status submenu:
Table 5: Command Buttons
Command Buttons Descriptions

Elements Lists the status of all managed elements in the system.
Components Lists the status of all managed components.
Refresh Updates the status.
The following table presents the descriptions of the fields that are displayed in the Current Status submenu:
Table 6: Parameters for the Current Status
Managed Components Field Descriptions

Severity Displays a text indication for the severity of the status of the elements
in the system.
The level of the severity is marked with the following colors:
• Normal (Green)
• Minor (Yellow)
• Major (Red)
• Critical (Red)
• Warning (Yellow)
• Indeterminate (Green)
Element Displays the Alias of the Element reporting its status.

Example: ZC1, ATR
Component Displays the Alias of the Component being reported on.

Example:ZcMobilityLink (1)
Table continued…

Reference | 139
Managed Components Field Descriptions

State Text Displays the text of the status reported for the element followed by the
state number.
Example:ENABLED (2)
Cause Text Displays the text of the cause reported for the element followed by the
cause number.
Example: ALL PROCESS ENABLED (302)
Time Displays the date and time, when the last change of the State/Cause
was detected.
Example: 12-Dec-2008, 10:12:48
Filter Presented in the form of a link, when activated opens a page listing on-
ly the components of the selected element.
History Presented in the form of a link, when activated opens a page display-
ing up to 32 last status changes of the selected object.
Note: You can sort the managed elements that are displayed in specific fields by consecutively clicking on
the relevant column header. The following sorting order is available:
• Ascending order (alphabetical/time in chronological order)
• Descending order (alphabetical/time in chronological)
• Severity level for the Severity column
• Time in chronological order
All Events Object

Figure 106: All Events Page
The following table presents descriptions of the Command buttons in the All Events submenu:
Table 7: Command Buttons

Refresh Updates the status of the events.
Table continued…

140 | Reference

Download Downloads the events of the various elements and components in the
system to the PC. The events are saved to a coma separated file via a
download dialog box.
For the descriptions of the managed components fields, see Table 6: Parameters for the Current Status on page 138.
Alarm Severity Levels

Alarms are assigned determined severity levels that indicate the health of each individual device or the composite
health of individual devices in a container. Severity levels of the alarms are shown by the color of a symbol and the
descriptive text that appears in the Severity column in the Status page (see Figure 4: Example of the Status Page on
page 45).
The following table lists the severity alarms and its explanations:
Table 8: Severity Levels
Background Severity Num-

Severity Condition Description
Color ber
Critical Red 1 The object is not functioning.
Major Red 2 The object has serious problems, indi-
cating severe degradation of service.
These problems are likely to impede
the normal use of the object.
Minor Yellow 3 The object has a minor problem.
However, this state should not impede
the normal use of the object.
Warning Yellow 4 The object has a condition which may
require attention, potential service af-
fecting fault.
Indeterminate Green 5 The object is in an unknown state (no
information is available about its cur-
rent state).
Normal Green 6 The object is in a normal operational
state.

Reference | 141
Configuration Page
Figure 107: Configuration Page
Radio User Object

Figure 108: Radio User Object
The following table presents the parameters used for the configuration of the Radio User:

142 | Reference
Table 9: Parameters for the Radio User
Valid characters
Field Default Descriptions
Range
Radio User Alias N/A 1-16 UTF-8 characters. Enter a unique name that refers to
a specific radio user on the sys-
Cannot use:| @ _ " %
tem.
Radio ID N/A 1 to 13999999 Select a unique number that refers
to a specific radio on the system.
Radios need a unique ID to com-
municate with other radios in the
system.
Radio Serial Number N/A 1 to 15 characters. Enter a unique serial number of a
specific radio on the system. The
Cannot use: | @ _ " ? %
unique serial number is part of the
$
programming of a radio.
Radio Reference ID N/A 1 to 21 characters. Enter the unique reference of the
radio used for Authentication or
Cannot use: | @ _ " ? %
Encryption purposes. The Radio
$
Reference ID may be a Tetra
Equipment Identifier (TEI), or a
SIM ID in cases where the mobile
station uses SIM cards. TEI: T fol-
lowed by 15 hexadecimal digits
(09 and A-F). SIM: S followed by
20 hexadecimal digits (09 and A-
F).
Short Data Enabled Yes Yes/No Enables/disables the radio user to
have access to the short data serv-
ice.
Full Duplex Enabled Yes Yes/No Enables/disables the radio user to
initiate and receive full duplex pri-
vate calls.
Radio User Capabilities TEMPLATE Valid records Select a unique name that refers to
Profile Alias a specific Radio User Capabilities
Profile defined on the system.
User Enabled Yes Yes/No Allows/prevents the radio user to
make calls on the system.
Ambience Listening No Yes/No Allows/prevents the dispatch con-
Monitoring Enabled sole to monitor the specific radio
user.
Interconnect Enabled No Yes/No • Yes allows the radio user to in-
itiate and receive interconnect
calls. This setting enables all
interconnect-related parame-
ters on the page: Radio User
Interconnect Profile, Direct
Dial Number.
Table continued…

Reference | 143
Valid characters
Range
• No prevents the radio user

from initiating or receiving in-
terconnect calls. This setting
disables all interconnect-relat-
ed parameters on the page.
Radio User Interconnect N/A 1 to 16 characters. Select a unique name that refers to
Profile a specific Radio User Interconnect
Direct Dial Number N/A Valid telephone number Enter a unique telephone number
that identifies the radio user, when
called from an external telephone
network.
Note: This field must
always be empty for
the default SZ$DEF ra-
dio user. Any modifi-
cation of this field for
the SZ$DEF radio user
will not be saved.
Packet Data Enabled No Yes/No Enables/disables the radio user to

have access to the packet data
service which is essential for dis-
tributing data within the Dimetra
IP Micro/Dimetra LiTE system
and also in exchanging data with
other IP networks.
If enabled, the following parame-
ters are editable:
QAM Data Enabled, Assigned IP
Addresses, and Multislot Packet
Data Enabled,
otherwise they are grayed out.
Note: The Packet Data
Enabled parameter is
configurable if a dedi-
cated license has been
purchased.
For an overview of the Packet Da-
ta services, see System Overview.
Details on the Packet Data func-
tionality can be found in Data
Subsystem.
QAM Data Enabled No Yes/No Enables/disables the radio user to
chose the type of the Quadrature
Amplitude Modulation (QAM)
used for modulating data signals
Table continued…

144 | Reference
Valid characters
Range
onto a carrier. If enabled, modula-
tion types can be chosen via the
MTS configuration object.
Note: The QAM Data
Enabled parameter is
configurable if a dedi-
cated license (Tetra
Enhanced Data Serv-
ices) has been pur-
chased.
Assigned IP Addresses N/A Valid IP address Enter the IP address that can be
used by the radio user. That is,
when connecting a computer to
the Mobile Station (MS) the com-
puter can use this address. This
can be done either by configuring
the assigned IP address in the
computer as well as in the system,
or by setting up the computer to
use a network assigned IP address.
Note: The Assigned IP
Addresses parameter is
configurable only if the
Packet Data Enabled
parameter is enabled.
Multislot Packet Data No Yes/No Enables/disables the radio user to

Enabled access the multi-slot packet data
service. For details on the Multi-
slot Packet Data feature, see the
Data Subsystem manual.
Note: The Multislot
Packet Data Enabled
parameter is configura-
ble only if the Packet
Data Enabled parame-
ter is enabled.
Note: If there are more objects than can be shown on a page (20), use the Navigation Links page to
navigate between the pages.
The following table presents information on the Command Buttons displayed in the Configuration page for the
Radio User:
Table 10: Command Buttons for the Radio User
Command Buttons Description

New Allows creating a radio user (record).
Modify Allows modifying a specified/selected radio user (record).
Table continued…

Reference | 145

Delete Allows for deleting an existing radio user (record).
Open Search Activates a search query page which allows searching for a specific ra-
dio user by entering the Radio User Alias or ID. The search query con-
tains a drop down list with different operators that you can chose from.
For the Alias, the following operators are available: Starts with, Ends
with, Contains, Equals, In. For the IDs: Equals, Between, and In
operator. Additionally, you can mark a checkbox if case sensitivity for
the Alias is crucial. Once you click the Search command button with
in the search query window, a list of available records meeting your
criteria appear on the page. Use the Clean command button to change
your search options if necessary, and Close to return to the previous
page.
Radio User Capabilities Profile

Figure 109: Radio User Capabilities Profile Page
The following table presents the parameters used for the configuration of the Radio User Capabilities Profile:

146 | Reference
Table 11: Parameters for the Radio User Capabilities Profile
Valid characters
Range
Radio User Capabilities N/A 1 to 16 characters. Enter a name that refers to a spe-
Profile Alias cific Radio User Capabilities Pro-
Cannot use: | @ _ " %
file defined on the system.
Radio User Capabilities N/A 1 to 2000 Enter a unique number that refers
Profile ID to a specific Radio User Capabili-
ties Profile defined on the system.
This profile is the mechanism by
which general capabilities of a ra-
dio user are configured. You can
customize the capability parame-
ters for a set of radio users by cre-
ating a profile.
Called User Preemption Disabled SwMI Invoked, User In- Select the invocation mode for
voked or Disabled Called User Preemption.
• SwMI Invoked allows all in-
dividual calls initiated by the
radio user to preempt the
called user. It means that the
feature is always active.
• User Invoked allows only in-
dividual calls initiated by au-
thorized radio users (config-
ured in the radio) to preempt
the called user. It means that
the Radio User may select to
use the feature or not at run-
time.
• Disabled means that all indi-
vidual calls initiated by the ra-
dio user never preempt the
called user.
Dispatch Priority Level 10 2 to 10 Select the priority level at which

the radio users dispatch or private
• 2=Highest level
call requests are serviced by the
• 10=Lowest level system.
Note: The priority val-
ue of 1 is reserved by
the system for emer-
gency calls.
Load Class Name Default Radio Default Radio; From the drop-down list, select
Stationery Radio; the predefined Load Class Name
that determines a specific load
High Activity Radio; class defined on the system.
Very High Activity Ra- This parameter indicates deter-
dio; mined classes (types) of radios
which have a given expected con-

Reference | 147
Valid characters
Range
tribution to the load on the Com-

mon Control Channel (CCCH).
Load classes are associated with a
specific radio, and they are initial-
ly predefined in the system. For
maintainability purposes it is rec-
ommended to use the predefined
load classes, however other load
classes can be created and config-
ured in Advanced NM via the
User Configuration Manager ap-
plication. For more details on the
load classes, see User Configura-
tion Manager.
Note: The Load Class
Name parameter is ed-
itable only if the Sys-
tem Ready for C-
SCCH on the System
configuration object is
enabled, and the Com-
mon Secondary Con-
trol Channel license
has been purchased.
Radio User Capabilities Profile:
Table 12: Command Buttons for the Radio User Capabilities Profile

New Allows creating a radio user profile record.
Modify Allows modifying a specified/selected radio user profile record.
Delete Allows deleting an existing radio user profile record.
Open Search Activates a search query page which allows searching for a specific
Radio User Capabilities Profile by entering the Radio User Capabili-
ties Profile Alias or ID. The search query contains a drop down list
with different operators that you can chose from. For the Alias, the fol-
lowing operators are available: Starts with, Ends with, Contains,
Equals, In. For the IDs: Equals, Between, and In operator. Addition-
ally, you can mark a checkbox if case sensitivity for the Alias is cru-
cial. Once you click the Search command button with in the search
query window, a list of available records meeting your criteria appear
on the page. Use the Clean command button to change your search op-
tions if necessary, and Close to return to the previous page.

148 | Reference
Radio User Interconnect Profile

Figure 110: Radio User Interconnect Profile Page
The following table presents the parameters used for the configuration of the Radio User Interconnect Profile:
Table 13: Parameters for the Radio User Interconnect Profile
Valid characters
Range
Radio User Interconnect N/A 1 to 16 characters. Select a unique name that refers to
Profile Alias a specific Radio User Interconnect
Radio User Interconnect N/A 2 to 16 Enter a unique number that refers
Profile ID to a specific Radio User Intercon-
nect Profile defined on the system.
This profile is the mechanism by
which the interconnect capabilities
of a radio user are configured.
You can customize the intercon-
nect configuration information for
a set of radio users by creating a
profile.
Priority Level 10 2 to 10 Select the priority level at which
the radio users dispatch or private
Table continued…

Reference | 149
Valid characters
Range
• 2=Highest level call requests are serviced by the

• 10=Lowest level system.
Note: The priority val-
ue of 1 is reserved by
the system for emer-
gency calls.
Disallowed Dialing Pat- N/A 1 to 15 characters. Enter up to 16 Disallowed Dialing

tern Patterns. Disallowed dialing pat-
Cannot use: | @"_ %
terns are typically used to prevent
dealing of international calls, pre-
mium rate numbers etc. Radio
Users who are assigned this dial-
ing pattern as an Outbound Exclu-
sion Class will not be able to
make telephone calls to phone
numbers that begin with this dial-
ing pattern.
Radio User Interconnect Profile:
Table 14: Command Buttons for the Radio User Interconnect Profile

New Allows creating a radio user interconnect profile record.
Modify Allows modifying a specified/selected radio user interconnect profile
record.
Delete Allows deleting an existing radio user interconnect profile record.
Radio User Interconnect Profile by entering the Radio User Intercon-
nect Profile Alias or ID. The search query contains a drop down list
with different operators that you can chose from. For the Alias, the fol-
lowing operators are available: Starts with, Ends with, Contains,

150 | Reference
Talkgroup Object
Figure 111: Talkgroup Page
The following table presents the parameters used for the configuration of a Talkgroup:
Table 15: Parameters for the Talkgroup Object
Valid Characters
Field Default Description
Range
Talkgroup Alias N/A 1 to 16 characters. Enter a unique name that refers to
a specific talkgroup defined on
Cannot use: |@_" %, and
the system.
cannot prefix with SZ$ or
sz$.
Talkgroup ID N/A 1 to 13999999 Enter a unique number that refers

to a specific talkgroup defined on
the system.
TG/MG Capabilities TEMPLATE Valid records Enter a unique name that refers to
Profile Alias a specific TG/MG Capabilities
Console TG/MG Capa- TEMPLATE Valid records Enter a unique name associated
bilities Profile Alias with the Console Talkgroup/
Multigroup (TG/MG) Resource
Table continued…

Reference | 151
Valid Characters
Range
Capabilities Profile. The Alias
must be unique among all Con-
sole Resource Capabilities Pro-
files, where a Console TG/MG
Capabilities Profile is considered
a Console Resource Capabilities
Profile. If a Console TG/MG Ca-
pabilities Profile is already as-
signed to a multigroup, the Patch
field cannot be set to Yes. Also,
if the Patch field of a Console
TG/MG Capabilities Profile is set
to Yes, it cannot be assigned to a
multigroup.
Preempt Capable No Yes/No Allows/prevents all group calls
initiated in this talkgroup to pre-
empt lower priority calls both on
voice and data channels.
Talkgroup Regroupable Yes Yes/No Enables/disables this talkgroup to
be regrouped with other talk-
groups, allowing the resulting su-
pergroup to transmit using only
one repeater.
Note: If there are more objects than can be shown on a page (20), use the page Navigation Links to
navigate between the pages.
The following table presents information on the Command Buttons displayed in the Configuration for a
Talkgroup:
Table 16: Command Buttons for a Talkgroup

New Allows creating a talkgroup (record).
Modify Allows modifying a specified/selected talkgroup (record).
Delete Allows deleting an existing talkgroup (record).
talkgroup by entering the Talkgroup Alias or ID. The search query
contains a drop down list with different operators that you can chose
from. For the Alias, the following operators are available: Starts with,
Ends with, Contains, Equals, In. For the IDs: Equals, Between, and
In operator. Additionally, you can mark a checkbox if case sensitivity
for the Alias is crucial. Once you click the Search command button
with in the search query window, a list of available records meeting
your criteria appear on the page. Use the Clean command button to
change your search options if necessary, and Close to return to the pre-
vious page.

152 | Reference
Multigroup Object
Figure 112: Multigroup Page
The following table presents the parameters used for the configuration of the Multigroup:
Table 17: Parameters for the Multigroup Object
Valid Characters
Range
Multigroup Alias N/A 1 to 16 characters. Enter a unique name that refers to
a specific multigroup defined on
Cannot use: |@_"%, and
the system.
cannot prefix with SZ$ or
sz$.
Multigroup ID N/A 1 to 13999999 Enter a unique number that refers

to a specific multigroup defined
on the system.
Table continued…

Reference | 153
Valid Characters
Range
Note: The same pool

of IDs is also used for
allocating ID numbers
to Talkgroups and Ra-
dios, and the same
value cannot be as-
signed to both a group
and an individual.
TG/MG Capabilities TEMPALTE Valid records Select a unique name that refers
Profile Alias to a specific TG/MG Capabilities
Console TG/MG Capa- TEMPLATE Valid records Select a unique name associated
bilities Profile Alias with the Console Talkgroup/
Multigroup (TG/MG) Resource
Capabilities Profile. The Alias
must be unique among all Con-
sole Resource Capabilities Pro-
files, where a Console TG/MG
Capabilities Profile is considered
a Console Resource Capabilities
Profile. If a Console TG/MG Ca-
pabilities Profile is already as-
signed to a multigroup, the Patch
field cannot be set to Yes. Also,
if the Patch field of a Console
TG/MG Capabilities Profile is set
to Yes, it cannot be assigned to a
multigroup.
Interrupt Or Wait Mode Wait Interrupt or Wait • Interrupt enables a multi-
group to interrupt talkgroup
calls currently in conversation
to include them in a multi-
group call, regardless if all
talkgroup members are availa-
ble.
• Wait allows a talkgroup call
in progress to end before a
multigroup call begins, so the
multigroup waits for all talk-
group members to be availa-
ble.
Preempt Capable No Yes/No Allows/disables all group calls

initiated in this multigroup to pre-
empt lower priority calls for both
voice and data channels.
Talkgroups N/A N/A You can add/remove specific
talkgroups that form a multigroup
by clicking Add while creating or
modifying a multigroup configu-

154 | Reference
Valid Characters
Range
ration record, and selecting a
talkgroup(s) existing in the data-
base. The selection can be done
individually or in groups by se-
lecting a few talkgroups all at
once, and clicking Select. To re-
move the talkgroups, select the
ones you want to remove from
the system, and click Delete.
Multigroup:
Table 18: Command Buttons for the Multigroup

New Allows creating a multigroup (record).
Modify Allows modifying a specified/selected multigroup (record).
Delete Allows deleting an existing multigroup (record).
multigroup by entering the Multigroup Alias or ID. The search query
vious page.

Reference | 155
TG/MG Capabilities Profile

Figure 113: TG/MG Capabilities Profile
The following table presents the parameters used for the configuration of the TG/MG Capabilities Profile:
Table 19: Parameters for TG/MG Capabilities Profile
Field Default Range Descriptions

TG/MG Capabilities Profile N/A 1 to 16 characters. Enter a unique name that refers to a
Alias specific TG/MG Capabilities Profile
Cannot use: |
defined on the system.
@_"%, and cannot
prefix with SZ$ and
sz$.
TG/MG Capabilities Profile N/A 1 to 2000 Enter a unique number that refers to a
ID specific TG/MG Capabilities Profile
defined on the system. This profile is
the mechanism by which capabilities
of a talkgroup or multigroup are con-
figured. You can customize the talk-
group or multigroup capability param-
eters for a set of talkgroups or multi-
groups by creating a profile.
Table continued…

156 | Reference

Dispatch Priority Level 10 2 to 10 Select a priority level to determine
how the system handles talkgroup call
• 2=Highest level
requests if all resources are not imme-
• 10=Lowest level diately available and the call must be
busied.
Note: The priority value of
1 is reserved by the system
for emergency calls.
Talkgroup Inactivity Time 12 hours 4 to 72 or Infinite Select the time when an inactive radio
(Hours) (increments of 4) affiliated to the current talkgroup or
multigroup is polled to determine if it
is no longer on the system. Infinite
means that it is never polled.
Audio Interrupt Mode Never Never or Always Select one of the following:
• Never prevents all audio interrupt
requests.
• Always lets the system automati-
cally grant preemptive audio inter-
rupt requests on the same talk-
group.
TG/MG Capabilities Profile:
Table 20: Command Buttons for the TG/MG Capabilities Profile

New Allows creating a talkgroup/multigroup profile record.
Modify Allows modifying a specified/selected talkgroup/multigroup profile re-
cord.
Delete Allows deleting an existing talkgroup/multigroup profile record.
TG/MG Capabilities Profile by entering the TG/MG Capabilities Pro-
file Alias or ID. The search query contains a drop down list with dif-
ferent operators that you can chose from. For the Alias, the following
operators are available: Starts with, Ends with, Contains, Equals,
In. For the IDs: Equals, Between, and In operator. Additionally, you
can mark a checkbox if case sensitivity for the Alias is crucial. Once
you click the Search command button with in the search query win-
dow, a list of available records meeting your criteria appear on the
page. Use the Clean command button to change your search options if

Reference | 157
Dispatch Application Object

Figure 114: Dispatch Application Page
The following table presents the parameters used for the configuration of the Dispatch Application:
Table 21: Parameters for Dispatch Application

Application Platform Alias N/A 1 to 16 characters.Enter a user-friendly name for the
platform that is running the applica-
Cannot use: |@_"%,
tion. Must be unique within the same
and cannot prefix
zone.
with SZ$ or sz$.
Application Platform ID N/A 1 to 5 Enter the Application Platform (physi-

cal box) identifier that has been as-
signed by the network manager. Must
be unique within the same zone.
Note: The Dispatch Appli-
cation and Logging Inter-
face Application share the
same pool of Application
Platform IDs, therefore it
is not possible to assign the
same value to both objects.
Console User Login Name N/A 1 to 8 characters. Enter an unique alias name that refers
to a specific user logging into the sys-
Cannot use: | @ _
tem. This field defines the console
" ? %.
users who in the system.
Spaces are not al-
lowed.
Console Unit ID N/A 1 to 13999999; Enter the Console ID. This number
uniquely identifies the console. The
Table continued…

158 | Reference
16777216 to Console ID represents the console as-

16777217; signed to a Dispatch Application that
the console user can use to communi-
16777219; cate with other resources in the sys-
tem.
Console Site ID N/A 1001 to 1230 Enter an ID to represent this Console
Site. Must be unique within the zone.
Note: Console Site ID is
set automatically to 1116
and grayed out if the Local
LAN parameter is enabled.
If a dispatch console is in a
remote site, then the Con-
sole Site ID must be the
same as the one used for
the remote CCGW (if cre-
ated).
Local LAN No Yes/No • Yes specifies that this Console

Site is placed at the master site
(co-located) and is directly con-
nected to the master site LAN
switch.
• No specifies that this Console Site
is not to be connected to a local
LAN.
Note: If the Local LAN
parameter is enabled, the
Console Site ID is auto-
matically set to 1116 and
grayed out.
If the Local LAN is disa-
bled, then the Console Site
ID must be the same as the
one used for the remote
CCGW (if created).
Dispatch Application Type MCC 7500C MCC 7500 / MCC Select the type of the dispatch appli-
7500S; cation to be used:
MCC 7500C • MCC 7500 / MCC 7500S.
MCC 7500 dispatch console sys-

tem uses the General Purpose In-
put/Output Module (GPIOM)
based interface allowing for multi-
ple peripherals to be connected to
a Dispatch Application. If select-
ed, the configuration parameters of
the peripherals are set by default.
Table continued…

Reference | 159
MCC 7500S is not supported for

the Dimetra IP Micro/Dimetra
LiTE systems.
• MCC 7500C dispatch console sys-
tem which does not use the Pur-
pose Input/Output Module
(GPIOM).
Microphone Sensitivity -19.86 -36.36 to -7.86 (in- Enter the value for the transmission
Level (dBu) crements by 1.5) maximum of the Motorola DGM mi-
crophone input. The value for trans-
mission maximum (the maximum rms
voltage in dBu of a sine wave with no
peak clipping) of the input relates to
the input gain relative to the 0dBr ref-
erence point of the console as follows:
Gain = +3.14 dBm0 VALUE. The re-
sulting gain range is 11dB to 39.5dB.
Note: This parameter is
only valid for the MCC
7500 / MCC 7500S Dis-
patch Console.
Headset Audio Input Level 13.36 20.86 to 7.64 (incre- Enter the value for the transmission
(dBm) ments by 1.5) maximum of the GPIOM Headset
speaker. The value for transmission
maximum (the maximum power in a
600 Ohm load in dBm of a sine wave
with no peak clipping) of the output
relates to the output gain relative to
the 0dBr reference point of the con-
sole as follows: Gain = VALUE -
3.14dBm0. The resulting gain range is
+4.5dB to - 24dB; the relative level of
the output can be configured in the
range from +4.5dBr to -24dBr.
7500 / MCC 7500S Dis-
patch Console.
Headset Audio Output Lev- 0.14 20.86 to 7.64 (incre- Enter the value for the transmission
el (dBm) ments by 1.5) maximum of the GPIOM Headset
speaker. The value for transmission
maximum (the maximum power in a
600 Ohm load in dBm of a sine wave
with no peak clipping) of the output
relates to the output gain relative to
the 0dBr reference point of the con-
sole as follows: Gain = VALUE -
3.14dBm0. The resulting gain range is
+4.5dB to - 24dB; the relative level of
Table continued…

160 | Reference

the output can be configured in the
range from +4.5dBr to -24dBr.
7500/MCC 7500S Dis-
patch Console.
Speaker 1and 2 Audio Out- 8.86 20.86 to 7.64 (incre- Enter the value for the transmission
put Level (dBm) ments by 1.5) maximum of the Speaker output.The
value for transmission maximum (the
maximum power in a 600 Ohm load
in dBm of a sine wave with no peak
clipping) of the output relates to the
output gain relative to the 0dBr refer-
ence point of the console as follows:
Gain = VALUE - 3.14dBm0. The re-
sulting gain range is +4.5dB to -
24dB; the relative level of the output
can be configured in the range from
+4.5dBr to -24dBr.
valid for both types of dis-
patch consoles the MCC
7500/MCC 7500S, and
MCC 7500C Dispatch
Console.
Acoustic Cross Mute N/A N/A The Acoustic Cross Mute parameter
enables a console to prevent transmit-
ting to its speaker for an audio stream
that is identified as an acoustical cross
muted pair for another nearby console
in which the dispatcher is transmit-
ting.
When a new Dispatch Application is
created, a new Acoustic Cross Mute
instance is created with that Dispatch
Application. Thus, when you modify
the settings of a Dispatch Application
object you can select the determined
dispatch applications to prevent listen-
ing to undesired audio from another
nearby console application by using
the Acoustic Cross Mute All Dis-
patch Applications field. Click Add,
select from the list of available Appli-
cation Platform Aliases (existing in
the database) the Dispatch Applica-
tions that this console wants to mute.
Dispatch Application:

Reference | 161
Table 22: Command Buttons for the Dispatch Application

New Allows creating a dispatch application record.
Modify Allows modifying a specified/selected dispatch application record.
Delete Allows deleting an existing dispatch application record.
dispatch application record by entering the Application Platform Alias
or ID. The search query contains a drop down list with different opera-
tors that you can chose from. For the Alias, the following operators are
available: Starts with, Ends with, Contains, Equals, In. For the IDs:
Equals, Between, and In operator. Additionally, you can mark a
checkbox if case sensitivity for the Alias is crucial. Once you click the
Search command button with in the search query window, a list of
available records meeting your criteria appear on the page. Use the
Clean command button to change your search options if necessary,
Logging Interface Application Object

Figure 115: Logging Interface Application Page
Note: Only one Logging Interface Application configuration object can be created.

162 | Reference
The following table presents the parameters used for the configuration of the Logging Interface Application:
Table 23: Parameters for Logging Interface Application Object

Application Platform Alias N/A 1 to 16 characters.Enter a user-friendly name for the
platform that is running the applica-
Cannot use: |@_"%,
tion. Must be unique within the same
and cannot prefix
zone.
with SZ$ or sz$.
Application Platform ID N/A 1 to 5 Enter the Application Platform (physi-

cal box) identifier that has been as-
signed by the network manager. Must
be unique within the same zone.
Note: The Logging Inter-
face Application and Dis-
patch Application share the
same pool of Application
Platform IDs, therefore it
is not possible to assign the
same value to both objects.
However, the hostname of
the Logging Interface Ap-
plication created via Web
NM will always be the fol-
lowing:
001s116ais01.vor-
tex1.zone1. If other
hostnames are needed,
they may be created using
the Advanced NM, Zone
Configuration Manager ap-
plication, Archiving Inter-
face Server Application
object.
Logging Interface User N/A 1 to 8 characters. Enter a unique login name that refers
Login Name Cannot use: | @_"? to a specific logging interface user
%, and cannot prefix logging into the system.
with SZ$ and sz$.
Spaces are not al-
lowed.
Logging Interface Unit ID N/A 1 to 13999999; Enter the Logging Interface Unit ID.
This number uniquely identifies the
16777216 to
console. The Unit ID represents the
16777217;
console assigned to a Logging Inter-
16777219; face Application that the console user
can use to communicate with other re-
sources in the system. This Unit ID
must be unique among all console
users on the system.
Table continued…

Reference | 163

Individual Call Logging 0 0 to 60 Sets the logging capacity of individual
Capacity calls.
Note: The Individual Call
Logging functionality is li-
censed.
Group Call Logging Ca- 0 0 to 120 Sets the logging capacity of group
pacity calls.
Note: The Group Call
Logging functionality is li-
censed.
Logging Interface Application:
Table 24: Command Buttons for the Logging Interface Application

New Allows creating a Logging Interface Application record.
Note: Only one Logging Interface Application configura-
tion object can be created, and if one has been already cre-
ated, then this command button is grayed out.
Modify Allows modifying a specified/selected Logging Interface Application

record.
Delete Allows deleting an existing Logging Interface Application record.
Logging Interface Application record by entering the Application Plat-
form Alias or ID. The search query contains a drop down list with dif-
ferent operators that you can chose from. For the Alias, the following
operators are available: Starts with, Ends with, Contains, Equals,
In. For the IDs: Equals, Between, and In operator. Additionally, you
can mark a checkbox if case sensitivity for the Alias is crucial. Once
you click the Search command button with in the search query win-
dow, a list of available records meeting your criteria appear on the
page. Use the Clean command button to change your search options if

164 | Reference
Console User Object

Figure 116: Console User Page
The following table presents the parameters used for the configuration of the Console User:
Table 25: Parameters for Console User Object

Console User Login Name N/A 1 to 8 characters. Enter an unique alias name that refers
to a specific user logging into the sys-
Cannot use: | @_" ?
tem. This field defines the console
%*.
users who in the system.
No spaces allowed.
Console ID N/A 1 to 13999999 Select the Console ID. This number

uniquely identifies the console. The
Console ID represents the console as-
signed to a Dispatch Application that
the console user can use to communi-
cate with other resources in the sys-
tem. This Console ID must be unique
among all console users on the sys-
tem.
Ambience Listening Initia- Yes Yes/No Allows/prevents the MCC 7500 con-
tion Enabled sole user to initiate an Ambience Lis-
tening call.
Console User Capability CONSOLE$ Valid records Select a profile for a Console User
Profile Alias DEF Capabilities Profile Alias. This is the
Console User Capability Profile with
which this Console User is associated.
The Console User Capability Profile
defines the set of features available to
this console user.

Reference | 165
The CONSOLE$DEF record appears

as a default record for console user ca-
pabilities profile. CONSOLE$DEF
defines privileges and default infor-
mation for users and is the default re-
cord for a new console user capabili-
ties profile whose information is not
available at the zone controller during
initialization.
Console User:
Table 26: Command Buttons for the Console User

New Allows creating a console user record.
Modify Allows modifying a specified/selected console user record.
Delete Allows deleting an existing console user record.
console user record by entering the Console User Login Name or Con-
sole ID. The search query contains a drop down list with different op-
erators that you can chose from. For the Alias, the following operators
are available: Starts with, Ends with, Contains, Equals, In. For the
IDs: Equals, Between, and In operator. Additionally, you can mark a

166 | Reference
Status Set Object

Figure 117: Status Set Page

Reference | 167
Figure 118: Modify Status Set Page
The following table presents the parameters used for the configuration of the Status Set:
Table 27: Parameters for Status Set Object

Status Set Alias N/A 1 to 16 characters. Enter a unique name that refers to a
specific status set profile defined on
Cannot use: | @ _
the system. A default record, STA-
" ? %$
TUS-SET-1, is provided for conven-
ience.
Status Set ID N/A 1 to 2000 Enter a unique ID that refers to a spe-
cific status set profile defined on the
system. By default the Status Set ID is
set to 1.
Status Number N/A Not editable, range A number that refers to a specific sta-
from 32768 32867. tus message defined on the system.
You can have up to 100 status mes-
sage. The Status Numbers are set by
default and can not be changed.
Table continued…

168 | Reference

Status Text N/A 1 to 60 characters. Enter a text associated with a specific
Status Number that is displayed when
Cannot use: | @ _ "
the radio user selects and transmits
%
that number, for instance
On scene, Out of Service,
En route, Available
, and so on. You can have up to 100
status message.
Status Set:
Table 28: Command Buttons for the Status Set

New Allows creating a status set record.
Note: This button is implemented for future release purpos-
es, it is not supported in this release.
Modify Allows modifying a specified/selected status set record.

Delete Allows deleting an existing status set record.
Note: This button is implemented for future release purpos-
es, it is not supported in this release.
Status Set record by entering the Status Set Alias or ID. The search
query contains a drop down list with different operators that you can
chose from. For the Alias, the following operators are available: Starts
with, Ends with, Contains, Equals, In. For the IDs: Equals, Be-
tween, and In operator. Additionally, you can mark a checkbox if case
sensitivity for the Alias is crucial. Once you click the Search com-
mand button with in the search query window, a list of available re-
cords meeting your criteria appear on the page. Use the Clean com-
mand button to change your search options if necessary, and Close to
return to the previous page.

Reference | 169
Short Data Router Object

Figure 119: Short data Router Page
The Modify button allows modifying a selected Short Data Router record.
purchased.
The following table presents the parameters used for the configuration of the Short Data Router:
Table 29: Parameters for Short Data router Object

Store and Forward Service Disabled Disable or Enable Enables or disables the Store and For-
Enabled ward Service.
MS to Group Service Disabled Disable or Enable Enables or disables MS to Group
Service.

170 | Reference
MTS Site Object

Figure 120: MTS Site Page
The following table presents the parameters used for the configuration of the MTS Site:
Table 30: Parameters for MTS Site

Site Alias N/A 1 to 16 characters. Enter a unique name that refers to a
specific MTS site within a zone.
Cannot use: |@_"%,
and cannot prefix
with SZ$ or sz$.
Site ID N/A 1 to 100 Enter a unique number that refers to a

specific MTS site within a zone.
MTS Type MTS2 MTS1; MTS2 or Select the type of MTS:
MTS4
• MTS1 holds maximum 2 base ra-
dios
Note: MTS1 can be
paired with another
MTS using an intercon-
nect kit.
dios
dios
Standby Site Controller No Yes/No Indicates if the MTS has a Standby

Site controller.
Table continued…

Reference | 171
Note: For MTS1, the

Standby Site Controller is
licensable.
It is enabled only if two
base radios are in the site.
Number of Base Radios N/A up to 2 for MTS1 if From the drop-down list select the
paired; number of radios depending on the
type of MTS site chosen.
1 to 2 for MTS2;
1 to 8 for MTS4;
Number of DPMs (Digital N/A 1 to 2 for MTS2; From the drop-down list, select a
Power Meter) unique number that refers to the Digi-
1 to 8 for MTS4
tal Power Meter (DPM) of a deter-
mined MTS site.
The Digital Power Meter measures the
effect of the site antenna. Alternative-
ly, it can be measured for each base
radio interface.
Note: MTS1 does not sup-
port the Digital Power Me-
ter.
Number of ATCCs (Active N/A 1 to 4 for MTS4 From the drop-down list, select a
Tune Cavity Combiner) unique number that refers to a specific
Active Tune Cavity Combiner
(ATCC) within the site.
The Auto Tune Cavity Combiner re-
ceives signals from several base ra-
dios and sends a combined signal to
the site sending antenna.
Note: Only MTS4 sup-
ports ATCC and can be
configured with ATCC.
Security Class 2 only MS Yes Yes/No • Yes allows Mobile Stations (MS)
Supported that only support Security Class 2
to register on the system.
• No prevents Mobile Stations that
only support Security Class 2 from
registering on the system.
Security Groups are groups used for
system partitioning of radio users and
infrastructure components. Partition-
ing controls access to the system and
segregates data so that each group can
only access objects for which they are
responsible.
Table continued…

172 | Reference

Security Class 3 MS Ena- No Yes/No • Yes allows the MTS site to work
bled in Security Class 3 mode.
It activates the SC3G Encryption

Enabled field only when valid li-
cense keys are installed.
• No prevents the MTS site from
working in Security Class 3 mode.
SC3G Encryption Enabled No Yes/No Enables/disables the SC3G Encryp-

tion functionality.
Note: As default, SC3G
Encryption Enabled field is
inactive. This functionality
is only available with a
valid license key which
has to be purchased.
Number of C-SCCH 0 0 to 1 Select the number of common secon-

dary control channels available at the
site. The Common Secondary Control
Channel (C-SCCH) service extends
the Main Control Channel (MCCH)
signaling capacity by using one or
more additional channels for the mes-
sages otherwise only sent on the
MCCH.
Note: The number of
channels is limited by the
C-SCCH license. If the li-
cense is available, you can
set the number of C-
SCCHs on the site: 01.
Important: Use these pa-
rameters with caution as
C-SCCH licenses are non-
retrievable.
QAM Base Radio None For MTS1, MTS2: From the drop down list, select the
None, Second; base radio which is TEDS capable and
will use the QAM modulation. For ex-
For MTS4: None,
ample, setting the QAM Base Radio
Second, Third,
to Third, means that the third base ra-
Fourth, Fifth, Sixth,
dio will be set to the QAM 25/50
Seventh, Eighth;
channel operation mode, and the rest
Additionally, the of the base radio for this MTS site
ranges vary depend- will be set to the PM channel opera-
ing on the number tion mode.
of base radios se-
This parameter activates the QAM
lected for a specific
Modulation parameter if a specific
MTS site in the
base radio is selected. Setting QAM
Number of Base Ra-
Table continued…

Reference | 173
dio field. For exam- Base Radio to None results in all the
ple, if the number of base radios for this MTS running in
base radios is set to the PM operation mode.
3, then the following
Note: The QAM Base Ra-
options are availa-
dio parameter is configura-
ble: None, Second,
ble only if a dedicated Tet-
Third.
ra Enhanced Data Services
(TEDS) license has been
purchased.
QAM Modulation QAM 25 QAM25; Select the channel operation mode for
a determined base radio for a particu-
QAM50
lar MTS site.
Note: The QAM Modula-
tion parameter is configu-
rable only if a dedicated
Tetra Enhanced Data Serv-
ices (TEDS) license has
been purchased. Addition-
ally, the channel operation
mode is dependant on the
MTS type and the number
of used base radios for that
MTS.
Max Number of Dynamic 1 0 to 10 Select the maximum number of chan-

Single Slot Data Channels nels on the site that may be allocated
as dynamic single slot packet data
channels.
Max Number of Dynamic 0 0 to 7 Select the maximum number of chan-
Multi Slot Data Channels nels on the site that may be allocated
as multi slot packet data channels.
MTS Site:
Table 31: Command Buttons for the MTS Site

New Allows creating an MTS Site record.
Modify Allows modifying a specified/selected MTS Site record.
Delete Allows deleting an existing MTS Site record.
Diagnostics Allows you to change the functional state. There are 5 possible states
for the selected MTS site:
• Forced Parameter Download – The selected site is reconfigured
with the most recent values of all the parameters.
• Wide Trunking – Trunking operation extends to the entire system.
Table continued…

174 | Reference
• Site Trunking – Trunking operation is limited to the coverage area

of the selected site.
• Site Reset – The site is returned to the operating state.
• Site Off – The site is shut down.
Note: To get the site up and running again issue the
Wide Trunking command.
MTS site record by entering the Site Alias or ID. The search query
vious page.
Conventional Channel Gateway Object

Figure 121: Conventional Channel Gateway Page
The following table presents the parameters used for the configuration of the Conventional Channel Gateway:

Reference | 175
Table 32: Parameters for the Conventional Channel Gateway

Analog Conventional Chan- N/A 1 to 16 characters. Enter a unique name that refers to the
nel Alias channel for the conventional site.
Cannot use: |@_"%,
and cannot prefix
with SZ$ or sz$.
Analog Conventional Chan- N/A 1 to 4 Enter a unique number that refers to a

nel ID specific channel at the conventional
site.
1 indicates a conventional channel on
the CCGW module (in case of the
GGM 8000 router it is indicated as
number 8A port, 2 indicates port 8B
and so on; in case of the S2500 router
it is indicated as number 4 port, 2 in-
dicates port 5 and so on).
Console Site ID N/A 1001 to 1230 Enter an unique ID to represent this

Console Site.
Note: Console Site ID is
set automatically to 1116
and grayed out if the Local
CCGW parameter is ena-
bled.
If a CCGW is created in a
remote site, then the Con-
sole Site ID must be the
same as the one used for
the remote dispatch con-
sole (if created).
Local CCGW Yes Yes/No • Yes specifies that this Convention-

al Channel Gateway (CCGW) is
placed at the master site (co-locat-
ed) and the CCGW module is lo-
cated in the core router.
• No specifies that this CCGW is
placed at a remote console site.
Note: If the Local CCGW
is enabled, the Console
Site ID parameter is set au-
tomatically to 1116 and
grayed out. If the Local
CCGW is disabled, then
the Console Site ID must
be the same as used for the
remote dispatch (if creat-
ed).
Table continued…

176 | Reference

Impedance 600 Ohms 600 Ohms or High Select the impedance for the conven-
Impedance (10 k tional channel; usually a 600 ohm in-
Ohms) terface is needed. If the CCGW is
bridging across two devices connected
at 600 Ohms, select high impedance
(10 k Ohms).
Note: In case of using a

long cable connecting the
CCGW with an analog de-
vice it is advised to select
high impedance.
Caution: High impedance
setting in case of a short
cable connection may
cause interference of an
analog device. What is
more, in extreme case sce-
nario it may even cause its
damage.
Method to Detect Inbound Voice (VOX) Voice (VOX); Select the method for voice detection
Radio Transmission on the conventional channel; VOX for
Carrier Operated
voice detection (the detection of the
Relay (COR)
call is triggered by the presence of
voice) or COR for carrier operated re-
lay detection (the detection of the call
is triggered by the presence of an sig-
nal which triggers the CCGW to start
transmitting; the CCGW will await for
an appropriate signal in case of the in-
coming call before it starts the trans-
mission).
VOX Threshold Adjustment 0 0 to 15 (increments Select the adjustment to the VOX
by 1) threshold. This value is used by the
CCGW to calculate the actual VOX
Threshold. The formula is: VOX
Threshold = Knee - 15 + VOX
Threshold Adjustment.
VOX Hold Off Delay (ms) 1000 500 to 2000 (incre- Select the amount of time the channel
ments by 500) remains active after the voice level re-
ceived by the CCGW falls below the
threshold that initially caused the
channel to be considered active.
Repeat On No Yes/No • Yes specifies that the user can set
in-cabinet repeat to be on or off.
• No specifies that the user cannot
set in-cabinet repeat to be on or
off.
Table continued…

Reference | 177

Inbound AGC Knee Setting -25 -40 to -10, (incre- Select the conventional channels in-
ments of 5) bound AGC Knee setting.
Important: It is strongly
recommended to not
change this value except
under the guidance and di-
rection of a service techni-
cian.
Conventional Channel Gateway:
Table 33: Command Buttons for the Conventional Channel Gateway

New Allows creating a Conventional Channel Gateway record.
Modify Allows modifying a specified/selected Conventional Channel Gateway
record.
Note: Modifications/updates made to the settings of a
CCGW are displayed on the console status bar. Crucial set-
ting changes may affect the operation of the device, there-
fore a restart of the router or the CCGW module may be re-
quired.
Delete Allows deleting an existing Conventional Channel Gateway record.

Conventional Channel Gateway record by entering the Analog Con-
ventional Channel Alias or ID. The search query contains a drop down
list with different operators that you can chose from. For the Alias, the
following operators are available: Starts with, Ends with, Contains,

178 | Reference
Telephone Interconnect Object

Figure 122: Telephone Interconnect Page
Note: Only one Telephone Interconnect configuration object can be created.
The following table presents the parameters used for configuration of the Telephone Interconnect:
Table 34: Parameters for the Telephone Interconnect
De-
Field Range Descriptions
fault
MTIG-IP Alias N/A N/A Displays an unique name that refers to a spe-
cific MTIG-IP.
Note: This parameter is set by de-
fault.
MTIG-IP ID 1 1 Displays an unique number that refers to a

specific MTIG-IP.
Note: This parameter is set by de-
fault.
Telephony Settings:
Table continued…

Reference | 179
De-
fault
Radio ID Prefix 0 4 digits between 0 Enter the digits that prefix the Radio ID in
and 9999 the called number. The prefix is added to the
called number by the external network. It can
be necessary to distinguish incoming tele-
phone interconnect calls using radio IDs from
calls using DDI (Direct Dial In) numbers (re-
quiring translation) if the DDI numbers are
different from their Radio IDs.
Radio ID/DDI Length 15 1 to 15 Enter the number of digits of an incoming
telephone interconnect call number. The in-
coming telephone interconnect call number is
either the Radio ID or the DDI (Direct Dial
In) number, depending on which dialing
method has been selected for the particular
call. When the Zone receives this number of
digits from the external network, it attempts
to set up the call.
Number of DDI Digits 2 2 to 6 Select the number of digits, in the DDI num-
bers that are assigned to Radio Users that
must be unique. (For example, if the Number
of DDI Digits is set to 3 and the DDI number
5555321 was already in use, then the DDI
number 4444321 would not be acceptable be-
cause the last 3 digits are not unique).
Note: Once entered this number it
can only be increased, never de-
creased.
Outgoing Prefix N/A 1 to 6 numeric char- Enter which outgoing prefix numbers shall be
acters added to the called telephone number. This
prefix may be used by network equipment
connected to the TIG (typically a PABX) to
route the call.
Incoming Prefix N/A 00 to 99 or blank Enter which prefix numbers the external net-
work (typically a PABX) adds to the incom-
ing telephone number to indicate which ex-
ternal network route the call followed. This is
used when multiple networks are connected
using PABX as a routing mechanism.
Note: If this field is left blank, on-
ly one call route may be defined.
Private Branch Exchange (PBX) Settings:

Signaling Gateway Public N/A A valid IP address Enter the IP address for the signaling gate-
IP Address way as seen from the PBX point of view.
Table continued…

180 | Reference
De-
fault
Note: The Signaling Gateway

Public IP Address must be filled
in along with the Media Gateway
Public IP Address.
Important: A restart of the MTI-
GIP is needed for the defined IP
address to take affect when creat-
ing and modifying the Telephone
Interconnect. For details on how
to perform this, see Service Man-
ual.
Media Gateway Public IP N/A A valid IP address Enter the IP address for the media gateway as
Address seen from the PBX point of view.
Note: The Media Gateway Public
IP Address must be filled in along
with the Signaling Gateway Pub-
lic IP Address.
PBX IP Address N/A A valid IP address Enter the IP address for the PBX.
Note: This field is mandatory.
Note: The following IP addresses

cannot be used:
10.0.1.0 - 10.0.1.255
10.1.0.0 - 10.1.255.255
10.128.0.0 - 10.128.255.255
224.0.0.0 - 239.255.255.255
ual.
PBX Username N/A N/A Enter a unique alias name that refers to a spe-
cific PBX user logging on to the system.
ual.
Table continued…

Reference | 181
De-
fault
PBX Password N/A N/A Enter a unique text that ensures the security
of the user logging on the system. The *
character appears in the field for each letter
typed.
Note: PBX Password will always
be set to the value entered in the
PBX password field when the se-
curity options are enabled in the
PBX.
ual.
Confirm PBX Password N/A N/A Re-enter the newly created password for con-
firmation.
ual.
Telephone Interconnect:
Table 35: Command Buttons for the Telephone Interconnect

New Allows creating a telephone interconnect record.
Note: Only one Telephone Interconnect configuration ob-
ject can be created.
Modify Allows modifying a specified/selected telephone interconnect record.

Delete Allows deleting an existing telephone interconnect record.
Telephone Interconnect record by entering the MTIG-IP Alias or ID.
The search query contains a drop down list with different operators
that you can chose from. For the Alias, the following operators are
available: Starts with, Ends with, Contains, Equals, In. For the IDs:
Equals, Between, and In operator. Additionally, you can mark a

182 | Reference

System Object
values.
Figure 123: System Page
The Modify button allows you to edit the setting of the System object.
Note: Creation and deletion of the System configuration record is not supported.
The following table presents the parameters used for configuration of the System object:
Table 36: Parameters for System

System Alias SYSTEM1 1 to 16 characters. Enter a name that uniquely identifies
an individual system. SYSTEM1 has
been created by default.
Table continued…

Reference | 183
Cannot use: |@_"%,

and cannot prefix
with SZ$ sz$.
Mobile Country Code 0 0 to 1023 Enter the country code for the TETRA
system, assigned according to the
country in which the network is de-
ployed. The number should be that de-
fined in Annex D of CCITT Recom-
mendation X.121. It is broadcast by
the TETRA system to identify the
country code of the network.
Mobile Network Code 0 0 to 16383 Enter the network code for the TET-
RA system, normally assigned by the
National Administration of the coun-
try in which the network is deployed.
A unique value should be assigned to
each network within a country. It is
broadcast by the TETRA system to
uniquely identify the network.
Authentication Enabled No Yes/No Enables/disables the authentication for
the system.
Note: The Authentication
Enabled parameter is con-
figurable only if a dedicat-
ed license has been pur-
chased.
Air Interface Encryption No Yes/No • Yes indicates that air interface en-
Enabled cryption (AIE) is enabled for the
system. It enables the Secure
DMO OTAR Enabled field, only
when a dedicated license key is in-
stalled. It also enables the follow-
ing fields:
Tetra Encryption Algorithm, En-

crypted Radio ID Start Address,
Encrypted Radio ID End Address,
Encrypted Broadcast Cell Infor-
mation.
• No indicates that air interface en-
cryption is disabled for the system.
Note: The Air Interface
Encryption Enabled pa-
rameter is configurable on-
ly when a dedicated li-
cense has been purchased.
TETRA Encryption Algo- TEA1 TEA1; Select the algorithm type that you
rithm want the system to use for encryption.
TEA2;
Table continued…

184 | Reference
TEA3; Note: This parameter is

active if the Air Interface
Encryption functionality
has been enabled.
Secure DMO OTAR Ena- No Yes/No • Yes enables DMO Static Cipher
bled Key.
• No disables DMO Static Cipher
Key.
Note: The DMO OTAR
Enabled parameter is ac-
tive with a valid license
which has to be purchased,
additionally the Air Inter-
face Encryption function-
ality must be enabled.
For key details, see Managing Au-
thentication, Encryption, and Provi-
sioning.
System Ready for C-SCCH No Yes/No • Yes enables the Common Secon-
dary Control Channel (C-SCCH)
functionality, which extends the
Main Control Channel (MCCH)
signaling capacity by using one or
more additional channels for the
messages otherwise only sent on
the MCCH.
• No disables the Common Secon-
dary Control Channel functionali-
ty. If disabled, then the Common
Secondary Control Channel func-
tionality is switched off in all sites
in the cluster, for example only
Main Control Channels are availa-
ble as control channels.
Note: The System Ready
for C-SCCH parameter is
configurable only if a dedi-
cated license has been pur-
chased.
Encrypted Radio ID Start 1 1 to 15999 999 Enter the Radio ID Start Address for
Address Static Cipher Key (SCK) encryption.
has been enabled.
Encrypted Radio ID End 15999 999 1 to 15999 999 Enter the Radio ID End Address for
Address Static Cipher Key (SCK) encryption.
Table continued…

Reference | 185

has been enabled.
Encrypted Broadcast Cell No Yes/No • Yes indicates if neighboring cell

Information (D-NWRK BROADCAST) and
security related information (D-
CK CHANGE DEMAND) are
broadcast encrypted by the system.
• No disables this capability.
has been enabled.
System Optimization Object

Figure 124: System Optimization Page
The Modify button allows you to edit the setting of the System Optimization object.
Note: Creation and deletion of the System Optimization configuration record is not supported.

186 | Reference
The following table presents the parameters used for configuration of the System Optimization object:
Table 37: Parameters for the System Optimization

Group Call Service Timeout 1.5 0.0 to 30 Select the additional time a talkgroup
(sec) call is permitted to continue when no
radio is transmitting. This field is
commonly known as "hang time". In
message trunking, this is the time that
the assigned channel resource remains
active and keyed up. Longer time-outs
generally increase the system load.
Emergency Call Service 30 0 to INFINITE Select the additional time an emergen-
Timeout (sec) cy call is permitted to continue after
the standard hang time.
Private Call Service Time- 10 10.0 to 60.0 Select the hang time for a private call.
out (sec) This is the additional time a private
call is permitted to continue after the
radio user stops talking.
Private Call Ring Length 20 1 to 60 sec, No Select the time a radio initiated pri-
(sec) Change vate call can be in the ringing state
until it is terminated by the system.
Note: No Change means
the radio uses the Private
Call Ring Length timer
from its codeplug because
the system is not changing/
overwriting it. This timer
is called T302 in the TET-
RA standard.
Note: For a console initiat-
ed private call setup re-
quest towards a radio the
maximum time in the ring-
ing state is calculated as
the Private Call Ring
Length + 10 seconds.
Interconnect Ring Length 60 0 to 60 sec Select the time that the target radio
(sec) rings before an interconnect call is ter-
minated. During this time, resources
are reserved for the interconnect call.
Interconnect Final Warning 15 5 to 30 sec Select a warning period at the start of
(sec) which an alert tone warning is gener-
ated. After the warning period, the in-
terconnect call has exceeded the al-
lowed maximum duration and it will
be terminated.
Maximum Group Call Du- 10 0 to 1440 min Select the maximum amount of time
ration (min) that a group call can last. After this
Table continued…

Reference | 187

time period has expired, the call will
be transmission trunked.
Maximum Private Call Du- 10 0 to 60 min Select the maximum amount of time
ration (min) that a private call can last. After this
time period has expired, the call will
be transmission trunked.
Maximum Interconnect Call 10 1 to 60 min, Infinite Select the maximum amount of time
Duration (min) that an interconnect call can last. An
alert tone is generated indicating that
the call is about to end, before the in-
terconnect call exceeds this time.
Administration Page
Figure 125: Administration Page
Backup and Restore

Figure 126: Backup and Restore Page
The following table presents information on the Command Buttons displayed in the Administration page for the
Backup and Restore:

188 | Reference
Table 38: Command Buttons for Backup and Restore
Command Button Description

Backup Starts the backup of the files. It opens the Backup page where you can
see the backup progress (see Figure 127: Example of the Backup
Command Page on page 188).
Download Starts the download of the selected files from the WAS server to your
PC. It opens a download window which allows you to specify the
name of file on the PC to which the file on the servers will be down-
loaded to.
Upload Starts the upload of the files on your PC to the WAS server for later
restore. It opens an upload page which allows you to specify the name
of the file to be uploaded to the server.
Restore Starts the restore of the backup files (see Figure 128: Example of the
Restore Command Page on page 189).
Warning: Use this button cautiously as restoring the sys-
tem configuration impacts the system operation.
Delete Deletes a selected backup file from the WAS server.

Refresh Updates the list of applicable files on the WAS server.
Figure 127: Example of the Backup Command Page

Reference | 189
Figure 128: Example of the Restore Command Page
The following table presents information on the Command Buttons for the Backup/Restore Command Page:
Table 39: Command Buttons of the Backup Command Page and Restore Command Page

Start Starts the backup/restore.
Clear Clears the content of the Backup/Restore page.
Cancel Stops the backup/restore.
Back Returns you to the Backup and Restore page.
Server Connection
Figure 129: Server Connection Page
The Connect button opens a new browser window, in which a connection to the Integrated Lights Out Management
(ILOM), or Integrated Lights-Out (iLO) web pages is shown for server management and console access depending on
the hardware type your system supports.
Note: See Service Manual for details on how to access the servers.

190 | Reference
Change Password
Figure 130: Change Password Page
The following table presents descriptions of the fields visible in the Change Password page:
Table 40: Parameters for the Password
Field Default Valid Characters - Range Description

Username admin admin; Enter a unique alias name that re-
fers to a specific user logging on
guest;
to the system.
supermgr;
Note: The admin user
You may use the following: has read-write access
to all elements appear-
• Username: 1 to 8 characters
ing in the Web NM.
• Disallowed characters:|@_" ? The guest user has
%* read-only access to the
status pages in the
Web NM. The su-
permgr user provides
a read-write access to
all elements in the
Web NM and the pos-
sibility of changing
passwords for other
users.
Old Password N/A You may use the following: Enter a unique text that ensures
the security of the user logging on
• 6 to 12 characters
the system. The * character ap-
• Disallowed characters: none pears in the field for each letter
typed.
New Password N/A You may use the following: Enter a new unique text that en-
sures the security of the user log-
• 6 to 12 characters
ging on the system. The * charac-
• Disallowed characters: none ter appears in the field for each
letter typed.
Table continued…

Reference | 191
Field Default Valid Characters - Range Description

Confirm New N/A N/A Re-enter the newly created pass-
Password word for confirmation.
Software Update
Software Update:
Table 41: Command Buttons for Software Update

Upload Starts the transfer of a software (SW) update file to the WAS for later
update. It opens an upload page which allows you to specify the name
of the file to be uploaded to the server.
Note: The software update files are delivered by Motorola
on a DIPM R2.0 to R3.0 Upgrade Disc.
Update Starts the update of the selected software file for a core server, router,
and switch. Successful update is indicated by a checkmark visible in
the Active field. Server and firmware types of upgrade is supported
for local network devices (core switch and router).
Warning: Note that the update of the software disables the
servers temporarily.
Update Remote Starts the update of the selected software file for a remote control site.
Successful update is indicated by a checkmark visible in the Active
Remote field. Only firmware update files are supported for remote
control site devices (remote control site router and remote control site
switch if present in the system).
Note: For a remote control site devices (if reachable and
configured), only the firmware software update file type is
supported.
Table continued…

192 | Reference
Warning: Note that the update of the software disables the

servers temporarily.
Download Starts the transfer of the software update files to your PC.
Delete Deletes the selected update file from the WAS server.
Figure 132: Example of the Software Update Command Page
The following table presents information on the Command Buttons for the Software Update Command Page:
Table 42: Command Buttons of the Software Update Command Page

Start Starts the software update.
Clear Clears the content of the Software Update Command page.
Cancel Stops the update.
Back Returns you to the Software Update page.
Network Configuration
Note: Contact your technician for network configuration information and the functionality or, see the
Service Manual.
For network configuration guidelines, see Network Configuration File Guidelines on page 199.

Reference | 193
Network Configuration:
Table 43: Command Buttons for the Network Configuration Page

Upload Starts the transfer of the configuration files from your PC to the WAS
server. It opens an upload page which allows you to specify the name
of the file to be uploaded.
Apply Starts the update of a selected network configuration file for a local
core router, and local switch. Opens the Network Configuration
Command. Successful update is indicated by a checkmark visible in
the Active field.
Warning: Use this button cautiously as it impacts the sys-
tem operation. Incorrect network configuration may impact
connections to the RF-Site, the SDR hosts and the Teleph-
ony Gateway.
Apply Remote Starts the update of the selected network configuration file for a re-
mote control site. Opens the Network Configuration Command
page. Successful update is indicated by a checkmark visible in the Ac-
tive Remote field.
tem operation. Incorrect network configuration may impact
connections to the RF-Site, the SDR hosts and the Teleph-
ony Gateway.
Download Starts the download of the selected network configuration files from
the WAS server to your PC.
Delete Deletes the selected network configuration file from the WAS server.

194 | Reference
Figure 134: Example of the Network Configuration Command Page
The following table presents information on the Command Buttons for the Network Configuration Command
Page:
Table 44: Command Buttons for the Network Configuration Command Page

Start Starts the update of the network configuration file.
tem operation.
Clear Clears the content of the Network Configuration Command page.

Cancel Stops the update of the network configuration file.
Back Returns you to the Network Configuration page.
ATIA Logs
Figure 135: ATIA Logs Page
The following table presents information on the Command Buttons for the ATIA Logs:

Reference | 195
Table 45: Command Buttons for the ATIA Logs Page

Download Starts the download of the selected ATIA log files from the WAS serv-
er to your PC.
Collect Log Files

Figure 136: Collect Log Files Page
Collect Log Files:
Table 46: Command Buttons for the Collect Log Files Page

Brief Generates a brief collection of log files from the servers without de-
tailed information. This set of information allows a technician to make
an initial diagnosis about the box or component a given incident be-
longs to. This button opens a Collect Log Files Command page where
you can see the process of collecting log files to the archive file (see
the following figure ).
Comprehensive Generates a large collection of log files with detailed information. This
button opens a Collect Log Files Command page where you can see
the process of collecting log files to the archive file (see the following
figure ).
Download Starts the download of a log collection from the WAS server to your
PC.
Delete Deletes a selected file from the WAS server.

196 | Reference
Figure 137: Example of the Collect Log Files Command Page
The following table presents information on the Command Buttons for the Collect Logs Command Page:
Table 47: Command Buttons for the Collect Log Files Command Page

Start Starts the log file collection.
Clear Clears the content of the Collect Log Files page.
Cancel Stops the process of collecting logs.
Back Returns you to the Collect Log Files page (see Figure 136: Collect
Log Files Page on page 195).
Diagnostics
The Diagnostics page allows you to run different scripts which allow you to check, for example, the status of the
application servers, the version of the used software etc.
Figure 138: Diagnostics Page
Diagnostics:

Reference | 197
Table 48: Command Buttons for the Diagnostics Page

Run Executes a selected diagnostic executable/script, for example a test
script for checking the status of the application servers or the version
of the used software (see the following figure).
Refresh Updates the list of available diagnostics.
Figure 139: Example of Diagnostics Command Page
The following table presents information on the Command Buttons for the Diagnostics Command Page:
Table 49: Command Buttons for the Diagnostics Command Page

Start Starts running the diagnostics scripts.
Clear Clears the content of the Diagnostics Command page.
Cancel Stops the process of running diagnostics.
Back Returns you to the Diagnostics page (see Figure 138: Diagnostics
Page on page 196).

198 | Reference
Downloads
Figure 140: Download Page
The Download button allows you to download a selected software file to your PC.
About
Figure 141: About Page
The Refresh button updates the version of the Web NM being used.

199 | Network Configuration File Guidelines
Appendix
A
Network Configuration File Guidelines
Introduction
The network configuration is stored in a .csv (Comma-Separated Values) text file.
Each line of the .csv file consists of a variable name and a value or values separated by a comma, for example:
IS_LAYER2_NETWORK, TRUE.
As a good practice it is strongly recommended to use delivered .csv files for typical topologies as a baseline for
further customization (option altering).
• GBN topology – Before you start to configure the network, you have to decide what Ground Base Network
(GBN) topology will be used. The decision might depend on GBN service pricing, availability, configuration
flexibility, and so on. From the customization perspective the simplest topology is Layer 2 Point-to-Multipoint.
Start with this topology or search for another when not available.
After deciding what GBN topology is going to be used you have to agree on some GBN connection parameters
with the Service Provider, for example VLAN numbers, gateway IP addresses, and so on. Some of these
parameters are general, the others are related to particular feature configuration like RF Site, CEN, and so on..
• RF Site configuration – It is an obligatory step defining the RF site connections. The RF site definition depends
on selected GBN topology and consists of VLAN numbers, IP addresses, and so on..
• CEN Access – If you want to use API services (Web NM, SDS, etc) from the CEN you have to configure the
CEN Access. Two options are available: with BR and without BR. You can use BR when you need to connect the
Radio Network Infrastructure (RNI) to the network or to have the RNI separated from the network. In the latter
(simplest) case, you do not have to use BR.
• CEN APIs – Once you have configured the CEN Access you can enable APIs.
Note: Some APIs require additional license, for example UCS API and additional configuration tasks
on API server not covered here.
• IP Telephony – An optional feature enabling the IP Telephony services.
• VPN connection – You can enable VPN connection. VPN connection allows Motorola Solutions Support ESSC
to access the system remotely to provide a more efficient support for your system. We strongly recommend that
this connection is made and tested when the system is installed. It can then be used during the life of the system
when required. If you wish the physical connection to the Internet can be disconnected when not required to
provide Extra Security Air Gap.
Note: Enabling VPN option requires also configuration of VPN Gateway and Client.
• Remote Control Site – An optional feature when Remote Control Site is required. This option is useful when you
want to connect the Consoles located in different site than the RNI.
• Dual Site Link – An optional feature when the additional MTS link redundancy is required.
• QoS – In most cases, the default QoS settings should work. In Dimetra, each kind of traffic has its own ToS bits
assigned. In general, the more important traffic is (for example voice packet) the higher ToS value is assigned.
ToS bits are used by intermediate devices to prioritize the traffic.

When the packet enters L3 GBN network the ToS bits are used for determining traffic priority. You can re-map
ToS bits to the GBN network scheme when the GBN network uses incompatible ToS priority scheme.
For L2 GBN network Layer 2 CoS priority bits are used instead of ToS bits. Since in the Dimetra ToS field is
used, we need to map ToS bits to CoS bits before entering Layer 2 GBN.
In most cases, the GBN provider can respect your priority scheme by reconfiguring its GBN network accordingly.
For cases where the GBN cannot accept our priority scheme, you can redefine them using relevant options
in .csv files.
Configuration Examples
These configurations should be used as a baseline for further customization. For example, when you choose Layer 2
Point-to-Point without Border Router and with MTS Connectivity on page 206, you do not have to configure the IP
Telephony or CEN Access if not needed. On the other hand, you can add an additional option, for example Remote
Control Site, to extend functionality.
Important: Dimetra IP Micro Networking Topology solutions can only be Layer 2 or Layer 3. All
templates within the system are created with either Layer 2 or Layer 3 type, as the mixed configuration is
not supported within one system. Be careful when selecting the RF Site and Console Site IP addresses and
subnets. For Layer 3, ensure that there is no combination of sites directly connected in the same network as
the GBN Gateway router address while other sites are connected beyond the Layer 3 GBN Gateway router.
This is effectively mixing Layer 2 and Layer 3. If a Layer 2 template is selected, the whole of the Customer
GBN Network must be Layer 2. Additionally, customer switches and Layer 2 devices are in the path to all
of the sites but no routers are involved. If a Layer 3 template is selected, the whole of the Customer GBN
Network must be Layer 3. Every site must be beyond at least one router hop beyond the customer supplied
GBN Gateway router and not on a local subnet.
Minimal Configuration for Local MTS Only

Figure 142: Example of Minimal Configuration for Local MTS
This configuration is considered the simplest, as it does not require any external device, for example GBN service to
connect to a local MTS. You just connect the MTS to the GBN Access Port 1 using the RJ-45 patchcord. See Access
Port Settings on page 221 for details.
The following is an example of the .csv file:

Network Configuration File Guidelines | 201
VERSION,4,3,0
IS_LAYER2_NETWORK, TRUE
IS_P2P_TUNNEL, FALSE
REM, SI- NAME NUM- CGR_ADD, CGR_ADD_MASK, MTS_ADD, CIR, CB

TE- , BER, S
LIN
K_V
LAN
,
RFSI 300 MTS- 1, 172.32.1.30, 255.255.255.224, 172.32.1.1, 512, 99
TE, 1, 1, 0
IS_VPN_DISABLED, FALSE
SERVICE_PC_NET, 192.168.201.0
SERVICE_PC_MASK, 255.255.255.0
Since the network is separated from the CEN, you can leave all the IP settings without altering. The only parameter
which needs to be updated is CIR (CIR value in kbits for the connections) and CBS (CBS value in bytes for the
connection).

Layer 2 Point-to-Multipoint without Border Router and with MTS

Connectivity
Figure 143: Example of L2 P2M without BR and with MTS Connectivity
This configuration uses the GBN and enables the configuration of CEN and IP Telephony. The LAN Switch must be
configured with VLAN numbering and tagging such it can connect to the DIPM/LiTE Switch Access Port and allow
connection of the customer equipment on each VLAN. MTSs use one common VLAN. See Access Port Settings on
page 221 for details.
VERSION,4,3,0
REM, SI- NAME NUM- CGR_ADD, CGR_ADD_MASK, MTS_ADD, CIR, CBS

TE- , BER,
LIN
K_V
LAN
,
Table continued…

RFSIT 300 MTS- 1, 172.32.1.30, 255.255.255.224, 172.32.1.1, 512, 990

E, 1, 1,
RFSIT 300 MTS- 2, 172.32.1.30, 255.255.255.224, 172.32.1.2, 512, 990
E, 1, 2,
RFSIT 300 MTS- 3, 172.32.1.30, 255.255.255.224, 172.32.1.3, 512, 990
E, 1, 3,
RFSIT 300 MTS- 4, 172.32.1.30, 255.255.255.224, 172.32.1.4, 512, 990
E, 1, 4,
RFSIT 300 MTS- 5, 172.32.1.30, 255.255.255.224, 172.32.1.5, 512, 990
E, 1, 5,
IS_CEN_BORDER_ROUTER, FALSE
CEN_DMZ_VLAN, 3601
CEN_DMZ_CGR_IP, 192.168.100.254
CEN_DMZ_CGR_MASK, 255.255.255.0
IPTEL_VLAN, 3701
IPTEL_CGR_IP, 192.168.106.254
IPTEL_CGR_MASK, 255.255.255.0
PBX_PUBLIC_IP, 192.168.106.10
SG_PUBLIC_IP, 192.168.101.10
MG_PUBLIC_IP, 192.168.101.11
The CEN_DMZ_VLAN is the VLAN connecting BR router with the RNI. CEN_DMZ_CGR_IP is the IP address of
the CGR router in the CEN_DMZ_VLAN. CEN_DMZ_CGR_MASK is the IP mask used for this connection.
IPTEL_VLAN is the IP Telephony VLAN shared with the RNI.
IPTEL_CGR_IP is the CGR IP address in the IPTEL_VLAN. The IPTEL_CGR_MASK is the IP mask of this
connection.
PBX_PUBLIC_IP represents the PBX IP address.
SG_PUBLIC_IP, MG_PUBLIC_IP represent RNI SG and MG servers.
To enable access to CEN APIs (Web NM, SDS hosts, and so on), follow the CEN API details in Configuration
Reference on page 211.

Layer 2 Point-to-Multipoint with Border Router and MTS Connectivity

Figure 144: Example of L2 P2M with BR and MTS Connectivity
This configuration uses the GBN and enables the configuration of CEN and IP Telephony. They are available through
the BR, that is why it is necessary to configure the BR option as well. The BR is customer supplied and requires a
customer supplied or existing LAN Switch or Layer 2 and/or Layer 3 Network behind it with the IP addressing to
match the information added to the .csv Template. The LAN Switch must be configured with VLAN numbering
and tagging such it can connect to the DIPM/LiTE Switch Access Port and allow connection of the customer
equipment on each VLAN. MTSs use one common VLAN. See Access Port Settings on page 221 for details.
VERSION,4,3,0
REM, SI- NAME NU CGR_ADD, CGR_ADD_MASK, MTS_ADD, CIR, CBS

TE- , MB
LIN ER
K_V ,
Table continued…

LAN
,
RFSI 300 MTS- 1, 172.32.1.30, 255.255.255.224, 172.32.1.1, 512, 990
TE, 1, 1,
RFSI 300 MTS- 2, 172.32.1.30, 255.255.255.224, 172.32.1.2, 512, 990
TE, 1, 2,
RFSI 300 MTS- 3, 172.32.1.30, 255.255.255.224, 172.32.1.3, 512, 990
TE, 1, 3,
RFSI 300 MTS- 4, 172.32.1.30, 255.255.255.224, 172.32.1.4, 512, 990
TE, 1, 4,
RFSI 300 MTS- 5, 172.32.1.30, 255.255.255.224, 172.32.1.5, 512, 990
TE, 1, 5,
IS_CEN_BORDER_ROUTER, TRUE
CEN_BORDER_ROUTER_IP, 10.1.15.254
CEN_DMZ_VLAN, 3601
CEN_DMZ_CGR_IP, 10.1.15.193
CEN_DMZ_CGR_MASK, 255.255.255.192
CEN_PUBLIC_NET, 192.168.254.0
CEN_PUBLIC_MASK, 255.255.255.0
IPTEL_PUBLIC_NET, 192.168.106.0
IPTEL_PUBLIC_MASK, 255.255.255.0
PBX_PUBLIC_IP, 192.168.106.10
SG_PUBLIC_IP, 192.168.101.10
MG_PUBLIC_IP, 192.168.101.11
The CEN_BORDER_ROUTER_IP is the IP address of the BR router from the RNI perspective.
CEN_PUBLIC_NET and CEN_PUBLIC_MASK represent the actual CEN location - the other side of the BR router
from the RNI perspective.
IPTEL_PUBLIC_NET and IPTEL_PUBLIC_MASK represent the actual subnet where the PBX is located.
To enable access to CEN APIs (WebNM, SDS hosts, and so on) follow the CEN API details in Configuration

Layer 2 Point-to-Point without Border Router and with MTS

Connectivity
Figure 145: Example of L2 P2P without BR and MTS Connectivity
This configuration uses the GBN and enables the configuration of CEN and IP Telephony. The LAN Switch must be
configured with VLAN numbering and tagging such it can connect to the DIPM/LiTE Switch Access Port and allow
connection of the customer equipment on each VLAN. Each MTS uses separate VLANs. See Access Port Settings on
page 221 for details.
The following is an example of the .csvfile:
VERSION,4,3,0
IS_P2P_TUNNEL, TRUE

TE- , MB
LIN ER
K_V ,
LAN
,
Table continued…

RFSI 300 MTS- 1, 172.32.1.1, 255.255.255.224, 172.32.1.2, 512, 990

TE, 1, 1,
RFSI 300 MTS- 2, 172.32.2.1, 255.255.255.224, 172.32.2.2, 512, 990
TE, 2, 2,
RFSI 300 MTS- 3, 172.32.3.1, 255.255.255.224, 172.32.3.2, 512, 990
TE, 3, 3,
RFSI 300 MTS- 4, 172.32.4.1, 255.255.255.224, 172.32.4.2, 512, 990
TE, 4, 4,
RFSI 300 MTS- 5, 172.32.5.1, 255.255.255.224, 172.32.5.2, 512, 990
TE, 5, 5,
CEN_DMZ_VLAN, 3601
CEN_DMZ_CGR_IP, 192.168.100.254
IPTEL_VLAN, 3701
IPTEL_CGR_IP, 192.168.106.254
PBX_PUBLIC_IP, 192.168.106.10
SG_PUBLIC_IP, 192.168.101.10
MG_PUBLIC_IP, 192.168.101.11
connection.
To enable access to CEN APIs (WebNM, SDS hosts, and so on), follow the CEN API details in Configuration

Layer 2 Point-to-Point with Border Router and MTS Connectivity

Figure 146: Example of L2 P2P with BR and MTS Connectivity
This configuration uses the GBN and enables the configuration of CEN and IP Telephony. They are available through
the BR that is why it is necessary to configure the BR option as well. The BR is customer supplied and requires a
customer supplied or existing LAN Switch or Layer 2 and/or Layer 3 Network behind it with the IP addressing to
match the information added to the CSV Template. The LAN Switch must be configured with VLAN numbering and
tagging such it can connect to the DIPM/LiTE Switch Access Port and allow connection of the customer equipment
on each VLAN. Each MTS uses separate VLANs. See Access Port Settings on page 221 for details.
VERSION,4,3,0
IS_P2P_TUNNEL, TRUE
REM, SI- NAM NU CGR_ADD, CGR_ADD_MASK, MTS_ADD, CIR CBS

TE- E, MB ,
LIN ER
K_V ,
Table continued…

LAN
,
RFSI 300 MTS 1, 172.32.1.1, 255.255.255.224, 172.32.1.2, 512 990
TE, 1, -1, ,
RFSI 300 MTS 2, 172.32.2.1, 255.255.255.224, 172.32.2.2, 512 990
TE, 2, -2, ,
RFSI 300 MTS 3, 172.32.3.1, 255.255.255.224, 172.32.3.2, 512 990
TE, 3, -3, ,
RFSI 300 MTS 4, 172.32.4.1, 255.255.255.224, 172.32.4.2, 512 990
TE, 4, -4, ,
RFSI 300 MTS 5, 172.32.5.1, 255.255.255.224, 172.32.5.2, 512 990
TE, 5, -5, ,
CEN_DMZ_VLAN, 3601
CEN_DMZ_CGR_MASK, 255.255.255.192
PBX_PUBLIC_IP, 192.168.106.10
SG_PUBLIC_IP, 192.168.101.10
MG_PUBLIC_IP, 192.168.101.11

Layer 3 MTS Connectivity

Figure 147: Example of L3 MTS Connectivity
This example assumes L3 GBN connectivity for MTS, CEN, IP Telephony. GBN gateway is used. See Access Port
Settings on page 221 for details.
VERSION,4,3,0
IS_LAYER2_NETWORK, FALSE
GBN_GATEWAY_PRIMARY, 172.32.1.62

TE- , MB
LINK ER
_VLA ,
N,
RFSI 3001 MTS- 96 172.32.1.33 255.255.255.224, 172.32.1.1, 512, 990
TE, , 1, , ,
Table continued…

RFSI 3001 MTS- 97 172.32.1.33 255.255.255.224, 172.32.1.2, 512, 990

TE, , 2, , ,
RFSI 3001 MTS- 98 172.32.1.33 255.255.255.224, 172.32.1.3, 512, 990
TE, , 3, , ,
RFSI 3001 MTS- 99 172.32.1.33 255.255.255.224, 172.32.1.4, 512, 990
TE, , 4, , ,
RFSI 3001 MTS- 10 172.32.1.33 255.255.255.224, 172.32.1.5, 512, 990
TE, , 5, 0, ,
PBX_PUBLIC_IP, 192.168.106.10
SG_PUBLIC_IP, 192.168.101.10
MG_PUBLIC_IP, 192.168.101.11
CEN_PUBLIC_NET and CEN_PUBLIC_MASK represent the actual CEN location - the other side of the GBN
gateway from the RNI perspective.
Configuration Reference
The following parts define the meaning of each .csv parameter.
.csv parameters are grouped and described in relevant feature sections.
The following tags are used:
• [Required] - relevant section must be configured.
• [Optional] - relevant section can be configured.
Version [Required]
VERSION,4,3,0
This field shall be preserved with the same value as the example .csvfiles for the particular release specifies. During
the upgrade the Version field is used to identify the particular .csv scheme and is updated accordingly. This manual
refers to Version 4 of .csv files. The last two digits of the version can differ from the provided example.

Hardware Models [Required]

ROUTER_MODEL, GGM8000
ROUTER_MODEL variable defines the CGR hardware model. New Dimetra IP Micro R3.0/ Dimetra LiTE R3.0
systems use GGM8000 by default. Upgrading customers can still use S2500 (limitations apply).
SWITCH_MODEL, HP2620
SWITCH_MODEL variable defines the Core Lan Switch hardware model. New Dimetra IP Micro R3.0/ Dimetra
LiTE R3.0 systems use HP2620 by default. Upgrading customers can still use HP2610.
GBN Topology [Required]

The following variables are used to choose the GBN Metro topology:
IS_LAYER2_NETWORK, IS_P2P_TUNNEL
Three kind of topologies can be selected:
• Layer 2 Point-to-Multipoint (L2 P2M) – L2 topology is bridged connection. There is no router involved
between the RNI and MTS links. Point-to-Multipoint means that all MTSs and RNI share the same VLAN.
To enable Layer 2 Point-to-Multipoint topology use:
• Layer 2 Point-to-Point (L2 P2P) – Layer 2 topology is bridged connection. There is no router involved between
the RNI and MTS links. Point-to-Point means that each MTS has its own VLAN to connect to the RNI.
To enable Layer 2 Point-to-Point topology use:
IS_P2P_TUNNEL, TRUE
• Layer 3 (L3) – Layer 3 topology is routed connection. Requires GBN gateway between the RNI and MTS.
To enable Layer 3 topology use:
IS_LAYER2_NETWORK, FALSE
To define the GBN gateway IP address use:
GBN_GATEWAY_PRIMARY, 172.32.1.62
RF Sites [Required]
Each row of the RF Site section represents one MTS connection. Each row must start with the RFSITE keyword
followed by values representing SITELINK_VLAN, NAME, NUMBER, CGR_ADD, CGR_ADD_MASK,
MTS_ADD, CIR, CBS.
• SITELINK_VLAN – For L2 M2M and L3 GBN topology the SITELINK_VLAN has to be the same in each row.
For L2 P2P GBN topology, each row shall have unique VLAN number per each MTS connection.
• NAME – Shall be unique for each site.
• NUMBER – Shall be unique for each site.
• CGR_ADD – For L2 M2M and L3 GBN topology the CGR_ADD is common ie. the same in each row. For L2
P2P GBN topology the CGR_ADD is unique per each MTS connection.
• CGR_ADD_MASK – IP mask for MTS connections.
• MTS_ADD – IP address of the MTS site.
• CIR – CIR value in kbits for the connections.
• CBS – CBS value in bytes for the connection.

The following tables present examples for each kind of GBN topology.
L2 P2P GBN topology:
REM, SITE- NAME, NUM- CGR_ADD, CGR_ADD_MASK, MTS_ADD, CIR CB
LINK_VLAN, BER, , S
RFSIT 3001, MTS-1, 1, 172.32.1.1 255.255.255.2 172.32.1 512 99
E, , 24, .2, , 0
RFSIT 3002, MTS-2, 2, 172.32.2.1 255.255.255.2 172.32.2 512 99
E, , 24, .2, , 0
RFSIT 3003, MTS-3, 3, 172.32.3.1 255.255.255.2 172.32.3 512 99
E, , 24, .2, , 0
RFSIT 3004, MTS-4, 4, 172.32.4.1 255.255.255.2 172.32.4 512 99
E, , 24, .2, , 0
RFSIT 3005, MTS-5, 5, 172.32.5.1 255.255.255.2 172.32.5 512 99
E, , 24, .2, , 0
In this topology each site has its own, unique SITELINK_VLAN number with unique IP addressing per each link.
Note: Each link has to share the same IP network.
L2 P2M GBN topology:

REM, SITE- NAME, NUM- CGR_ADD, CGR_ADD_MASK, MTS_ADD, CIR, CB
LINK_VLAN, BER, S
RFSIT 3001, MTS-1, 1, 172.32.1.3 255.255.255.2 172.32.1 512, 99
E, 0, 24, .1, 0
RFSIT 3001, MTS-2, 2, 172.32.1.3 255.255.255.2 172.32.1 512, 99
E, 0, 24, .2, 0
RFSIT 3001, MTS-3, 3, 172.32.1.3 255.255.255.2 172.32.1 512, 99
E, 0, 24, .3, 0
RFSIT 3001, MTS-4, 4, 172.32.1.3 255.255.255.2 172.32.1 512, 99
E, 0, 24, .4, 0
RFSIT 3001, MTS-5, 5, 172.32.1.3 255.255.255.2 172.32.1 512, 99
E, 0, 24, .5, 0
In this topology each site shares the same SITELINK_VLAN number. Also CGR_ADD is common for all MTS
connections.
Note: All links have to share the same IP network.
L3 GBN topology:
LINK_VLAN, BER, , S
RFSIT 3001, MTS-1, 96, 172.32.1.3 255.255.255.2 172.32.1 512 99
E, 3, 24, .1, , 0
RFSIT 3001, MTS-2, 97, 172.32.1.3 255.255.255.2 172.32.1 512 99
E, 3, 24, .2, , 0
Table continued…

RFSIT 3001, MTS-3, 98, 172.32.1.3 255.255.255.2 172.32.1 512 99

E, 3, 24, .3, , 0
RFSIT 3001, MTS-4, 99, 172.32.1.3 255.255.255.2 172.32.1 512 99
E, 3, 24, .4, , 0
RFSIT 3001, MTS-5, 100, 172.32.1.3 255.255.255.2 172.32.1 512 99
E, 3, 24, .5, , 0
In this topology each site shares the same SITELINK_VLAN number. Also CGR_ADD is common for all MTS
connections.
Note: MTSs do not share the same network as the CGR because they are located in different subnet than
CGR router.
VPN Access [Required]

Here you can configure VPN Access from the CSV perspective.
Note: If there is a VPN Gateway in the system, change the value of the parameter IS_VPN_DISABLED in
the network configuration template from default TRUE to FALSE before applying the network
configuration in WebNM.
To enable VPN access use:
The SERVICE_PC_NET and SERVICE_PC_MASK should be left without changing, because they are internal in the
RNI and will not conflict with CEN.
To disable VPN access use:
IS_VPN_DISABLED, TRUE
CEN Access [Optional]

The CEN Access related variables allow you to configure a few kinds of CEN Access connections. The following are
available:
• Layer 2 and Layer 3 Topologies with BR on page 214
• Layer 2 Topology without BR on page 215
Layer 2 and Layer 3 Topologies with BR

CEN_DMZ_VLAN, 3601
CEN_DMZ_CGR_MASK, 255.255.255.192
CEN_DMZ_CGR_IP is alias of CEN_DMZ_NET. CEN_DMZ_CGR_MASK is alias of CEN_DMZ_MASK. They
can be used interchangeably for backward compatibility purpose, but in new deployments new names are preferred.

You can use the legacy names (CEN_DMZ_NET, CEN_DMZ_MASK) or the new preferred ones
(CEN_DMZ_CGR_IP, CEN_DMZ_CGR_MASK).
Layer 2 Topology without BR

CEN_DMZ_VLAN, 3601
CEN_DMZ_CGR_IP, 192.168.100.254
CEN_DMZ_CGR_IP is alias of CEN_DMZ_NET. CEN_DMZ_CGR_MASK is alias of CEN_DMZ_MASK. They
can be used interchangeably for backward compatibility purpose, but in new deployments new names are preferred.
You can use the legacy names (CEN_DMZ_NET, CEN_DMZ_MASK) or the new preferred ones
(CEN_DMZ_CGR_IP, CEN_DMZ_CGR_MASK).

CEN_PUBLIC_NET and CEN_PUBLIC_MASK represents the actual CEN location – the other side of the GBN
gateway from the RNI perspective.
CEN APIs [Optional]

Several APIs can be available for CEN users. Here you describe the API enablement from the CSV point of view i.e.
you assume that the API is enabled on the relevant API server.
Note: Some APIs might require license key.
Each API is enabled by defining Public IP address of the API server. Every server is located in the RNI and exposed
to the outside of the RNI through NAT. Defined IP represent NATed IP of the real server. Choose the non conflicting
IP address i.e. IP address which is unique within the CEN network (if connected).
To enable SDR API, use:
SDR_PUBLIC_IP, 192.168.101.197
To enable ATIA API or CADI API, use:
CADI_PUBLIC_IP, 192.168.101.196
To enable Logging Recorder API, use:
AIS_PUBLIC_IP, 192.168.101.191
To enable UCS API, use:
UCS_PUBLIC_IP, 192.168.101.193

To enable Web NM management and WNM Fault API, use:

WNM_PUBLIC_IP, 192.168.101.192
To enable external NTP server support, use:
NTS_PUBLIC_IP, 192.168.101.198
To enable Vortex API for co-located consoles:
CONSOLE01_PUBLIC_IP, 192.168.101.199
To enable Vortex API for remote consoles:
REM_CONSOLE01_PUBLIC_IP, 192.168.111.215
IP Telephony [Optional]
The following topologies are available in this configuration:
• Layer 2 and Layer 3 Topologies with BR on page 216
Layer 2 and Layer 3 Topologies with BR

Enables the BR (if "CEN Access" for the Layer 2 and Layer 3 topologies with BRoption was not configured
earlier).
CEN_DMZ_VLAN, 3601
CEN_DMZ_CGR_MASK, 255.255.255.192
Configures DMZ VLAN and IP/MASK for CGR interface in DMZ VLAN (if "CEN Access" for the "Layer 2 and
Layer 3 topologies with BR" option was not configured earlier).
IPTEL_PUBLIC_NET and IPTEL_PUBLIC_MASK replace legacy names (IPTEL_NET and IPTEL_MASK) for
Layer 2 topology with BR, Layer 3 topology with BR, and Layer 3 topology without BR. You can use the legacy
names (IPTEL_NET, IPTEL_MASK) or the new preferred ones (IPTEL_PUBLIC_NET, IPTEL_PUBLIC_MASK).
Note: In new deployments, the new names are preferred. If you use the legacy names, pay attention to the
different meaning of these names in different topologies. Layer 2 topology without BR differs from Layer 2
topology with BR, Layer 3 topology with BR, and Layer 3 topology without BR.
PBX_PUBLIC_IP, 192.168.106.10

SG_PUBLIC_IP, 192.168.101.10
MG_PUBLIC_IP, 192.168.101.11

Disables the BR (if "CEN Access" for the "Layer 2 topology without BR" option was not configured earlier).
IPTEL_VLAN, 3701
IPTEL_CGR_IP, 192.168.106.254
connection.
IPTEL_CGR_IP and IPTEL_CGR_MASK replace legacy names (IPTEL_NET and IPTEL_MASK) for Layer 2
topology without BR. You can use the legacy names (IPTEL_NET and IPTEL_MASK) or the new preferred ones
(IPTEL_CGR_IP, IPTEL_CGR_MASK).
PBX_PUBLIC_IP, 192.168.106.10
SG_PUBLIC_IP, 192.168.101.10
MG_PUBLIC_IP, 192.168.101.11

Disables the BR (if "CEN Access" for the "Layer 3 topology without BR" option was not configured earlier).
IPTEL_PUBLIC_NET and IPTEL_PUBLIC_MASK replace legacy names (IPTEL_NET and IPTEL_MASK) for
Layer 2 topology with BR, Layer 3 topology with BR, and Layer 3 topology without BR. You can use the legacy
names (IPTEL_NET, IPTEL_MASK) or the new preferred ones (IPTEL_PUBLIC_NET, IPTEL_PUBLIC_MASK).
PBX_PUBLIC_IP, 192.168.106.10

SG_PUBLIC_IP, 192.168.101.10
MG_PUBLIC_IP, 192.168.101.11
QoS [Optional]
Note: Change these settings only when the GBN provider requires to alter them.
For Layer 2 topologies use the following settings:
T0S_0X00_COS_VALUE, 2
T0S_0XA0_COS_VALUE, 5
T0S_0XC0_COS_VALUE, 6
T0S_0XE0_COS_VALUE, 7
For each IP precedence represented by the ToS values of 0x00, 0x20, and so on, you assign corresponding CoS value
(802.1p bits) according to Layer 2 GBN provider requirements.
For Layer 3 topology, use the following settings:
T0S_0X00_TOS_VALUE, 40
T0S_0XA0_TOS_VALUE, A0
T0S_0XC0_TOS_VALUE, C0
T0S_0XE0_TOS_VALUE, E0
For each IP precedence represented by the ToS values of 0x00, 0x20, and so on, you assign corresponding ToS value
according to Layer 3 GBN provider requirements.
Remote Control Site [Optional]

A row of the Remote Control Site sections represents Remote Control Site link. Each row must start with the RCSITE
keyword followed by values representing ROUTER_MODEL, SWITCH_MODEL,
IS_REMOTE_CONTROL_SITE_SWITCH, SITELINK_VLAN, NAME, NUMBER,CGR_ADD, CSLINK_VLAN,
CS_ADD, CS_ADD_MASK, CIR, CBS.
• ROUTER_MODEL – the CGR hardware model.
• SWITCH_MODEL – the Core Lan Switch hardware model.
• IS_REMOTE_CONTROL_SITE_SWITCH – Is set to FALSE if you want to use only one console connected
directly to the Control Site Router. If you want to connect more consoles, you need to use the Control Site Switch
and set this variable to TRUE.
• IS_CCGW – When set to TRUE the CCGW functionality is enabled at Remote Control Site.
• SITELINK_VLAN – For L2 M2M and L3 GBN topology the SITELINK_VLAN is the same as the
corresponding SITELINK_VLAN in the RF Site definitions. For L2 P2P GBN topology the VLAN shall be
unique.
• NAME – The name of the remote control site.
• NUMBER – The Site Id.
• CGR_ADD – For L2 M2M and L3 GBN topology the CGR_ADD is the same as for RF Site definition. For L2
P2P GBN topology the CGR_ADD is different than the CGR_ADD used for RF Site definition.

• CSLINK_VLAN – For L2 M2M and L2 P2P GBN topology the CSLINK_VLAN is the same as the one used in
SITELINK_VLAN. For L3 topology the CSLINK_VLAN is different than the SITELINK_VLAN as it represents
the VLAN on the opposite side of the GBN router.
• CS_ADD – Remote Control Site router IP address.
• CS_ADD_MASK – Remote Control Site router IP mask.
• CIR – CIR value in kbits for the connections.
• CBS – CBS value in bytes for the connection.
The following items provide examples for each kind of GBN topology.
For L2 P2P:
IS_REMOTE_CONTROL_SITE, TRUE
For L2 P2M:
For L3:
CS_GATEWAY, 172.32.1.30
Dual Site Link [Optional]

The Dual Site Link feature is defined in very similar way to RF Site configuration and uses the same set of variables.
You use different set of values than for primary RF site definition: SITELINK_VLAN, CGR_ADD,
CGR_ADD_MASK, MTS_ADD. You use the same values as for primary RF site definition for: NAME, NUMBER,
CIR, CBS. See the following examples for each GBN topology.
For L2 P2P:
IS_DUAL_SITE_LINK, TRUE

LINK_VLAN, BER, , S
RFSITE- 3011, MTS-1, 1, 172.32.11 255.255.255.2 172.32.11 512 99
Sec, .1, 24, .2, , 0
RFSITE- 3012, MTS-2, 2, 172.32.12 255.255.255.2 172.32.12 512 99
Sec, .1, 24, .2, , 0
RFSITE- 3013, MTS-3, 3, 172.32.13 255.255.255.2 172.32.13 512 99
Sec, .1, 24, .2, , 0
RFSITE- 3014, MTS-4, 4, 172.32.14 255.255.255.2 172.32.14 512 99
Sec, .1, 24, .2, , 0
RFSITE- 3015, MTS-5, 5, 172.32.15 255.255.255.2 172.32.15 512 99
Sec, .1, 24, .2, , 0
Notice that new set of VLANs representing MTS connections was used.
For L2 P2M:

REM, SITE- NAME, NUM- CGR_ADD, CGR_ADD_MASK, MTS_ADD, CI CB

LINK_VLAN, BER, R, S
RFSITE- 3011, MTS-1 1, 172.32.1.1 255.255.255.2 172.32.1.1 51 99
Sec, , 58, 24, 29, 2, 0
RFSITE- 3011, MTS-2 2, 172.32.1.1 255.255.255.2 172.32.1.1 51 99
Sec, , 58, 24, 30, 2, 0
RFSITE- 3011, MTS-3 3, 172.32.1.1 255.255.255.2 172.32.1.1 51 99
Sec, , 58, 24, 31, 2, 0
RFSITE- 3011, MTS-4 4, 172.32.1.1 255.255.255.2 172.32.1.1 51 99
Sec, , 58, 24, 32, 2, 0
RFSITE- 3011, MTS-5 5, 172.32.1.1 255.255.255.2 172.32.1.1 51 99
Sec, , 58, 24, 33, 2, 0
Notice that new common SITELINK_VLAN was used for redundant connection.
For L3:
GBN_GATEWAY_SECONDARY, 172.32.1.190
REM, SITE- NAME, NUM- CGR_ADD, CGR_ADD_MASK, MTS_ADD, CI CBS

LINK_VLAN, BER, R,
RFSITE- 3011, MTS-1 96, 172.32.1.1 255.255.255.2 172.32.1.1 51 990
Sec, , 61, 24, 29, 2,
RFSITE- 3011, MTS-2 97, 172.32.1.1 255.255.255.2 172.32.1.1 51 990
Sec, , 61, 24, 30, 2,
RFSITE- 3011, MTS-3 98, 172.32.1.1 255.255.255.2 172.32.1.1 51 990
Sec, , 61, 24, 31, 2,
RFSITE- 3011, MTS-4 99, 172.32.1.1 255.255.255.2 172.32.1.1 51 990
Sec, , 61, 24, 32, 2,
RFSITE- 3011, MTS-5 100, 172.32.1.1 255.255.255.2 172.32.1.1 51 990
Sec, , 61, 24, 33, 2,
Notice that new common SITELINK_VLAN was used for redundant connection.
Local Gateway Mode [Optional]

IS_LOCAL_GATEWAY_MODE, FALSE
Must be set to FALSE in all standard deployments. This feature is reserved for topology extension.
Data [Optional]
IS_GGSN, TRUE
IS_GGSN variable controls GGSN configuration. When set to TRUE the GGSN is enabled.
GGSN_IPIP_TUNNEL_IP, 10.128.255.66
GGSN_IPIP_TUNNEL_MASK, 255.255.255.224
GGSN_IPIP_TUNNEL_IP / GGSN_IPIP_TUNNEL_MASK are the IP address and mask of the IPIP tunnel toward
Border Router.

Other [Optional]
IS_LAYER2_DIRECT_ACCESS, TRUE
IS_LAYER2_DIRECT_ACCESS variable controls direct access to Access 1, Access 2 and Access 3 ports. When set
to TRUE, Access ports are dedicated respectively to RF Site, PABX, SD Host i.e. PABX can be connected directly to
Access port 2 and SDHosts can be connected directly to Access port 3. Access port 1 can be used to direct MTS
connection or for GBN purpose.
IS_FW_ENABLED, FALSE
IS_FW_ENABLED variable enables or disables Firewall. When set to TRUE (the default setting), the Firewall is
enabled and only Dimetra application protocols are permitted. When set to FALSE, the Firewall is disabled and all
protocols are permitted, for example ping. This variable might be good for troubleshooting purpose.
IS_LAYER3_LOCAL_BR, TRUE
Applies to Layer 3 topology. When set to TRUE (the default setting), the BR is connected via separated Layer 2
connection. When set to FALSE, the BR is connected via Layer 3 connection, the same way as the MTS is.
Other Configuration Tasks Overview
Ground Based Network (GBN) Gateway(s)

Routing – Layer 3 configuration requires GBN provider to setup and configure GBN gateway(s). It is not the
customer’s task.
Access Port Settings

When you connect customer supplied devices to the system, use the following table as a reference for port settings.
Table 50: Access Port Settings: Speed/Duplex, 802.1Q Tagging, VLANs
Access port 1 Access port 2 Access port 3

Example of .csv
Topology Speed/Duplex, Tag- Speed/Duplex, Tag- Speed/Duplex, Tag-
template name
ging1, VLANs2 ging1, VLANs2 ging1, VLANs2
Layer 2 P2M, Template-Net- Auto/Auto, Tagged, Auto/Auto, Tagged, Auto/Auto, Tagged,
no Border Rout- conf-L2-MtM- VLANs: VLANs: VLANs:
er noBR.txt
<3001> BTS Control <3001> BTS Control <3001> BTS Control
Site, Site, Site,
<3011> BTS (if dual <3011> BTS (if dual <3011> BTS (if dual
Links), Links), Links),
<3601> CEN-DMZ, <3601> CEN-DMZ, <3601> CEN-DMZ,
<3701> IP-Telephony <3701> IP-Telephony <3701> IP-Telephony
Layer 2 P2M, Template-Net- Auto/Auto, Tagged, Auto/Auto, Untagged, Auto/Auto, Untagged,

no Border Rout- conf-L2-MtM- VLANs: VLAN membership: VLAN membership:
er, Direct Ac- noBR-DirectAc-
cess cess.txt <3001> BTS Control <3701> IP-Telephony <3601> CEN-DMZ
Site,
Table continued…


Example of .csv
template name
<3011> BTS (if dual

Links)
Layer 2 P2M Template-Net- Auto/Auto, Tagged, Auto/Auto, Tagged, Auto/Auto, Tagged,

with Border conf-L2-MtM- VLANs: VLANs: VLANs:
Router BR.txt
<3001> BTS Control <3001> BTS Control <3001> BTS Control
Site, Site, Site,
<3011> BTS (if dual <3011> BTS (if dual <3011> BTS (if dual
Links), Links), Links),
<3601> CEN-DMZ <3601> CEN-DMZ <3601> CEN-DMZ
Z
Layer 2 P2P, no Template-Net- Auto/Auto, Tagged, Auto/Auto, Tagged, Auto/Auto, Tagged,
Border Router conf-L2-PtP- VLANs: VLANs: VLANs:
noBR.txt, Tem-
plate-mini- <3001-3006> BTS <3001-3006> BTS <3001-3006> BTS
mal.txt Control Site, Control Site, Control Site,
<3011-3015> BTS (if <3011-3015> BTS (if <3011-3015> BTS (if
dual Links), dual Links), dual Links),
<3601> CEN-DMZ, <3701> IP-Telephony <3601> CEN-DMZ,
<3701> IP-Telephony <3701> IP-Telephony
Layer 2 P2P, no Template-Net- Auto/Auto, Tagged, Auto/Auto, Untagged, Auto/Auto, Untagged,

Border Router, conf-L2-MtM- VLANs: VLAN membership: VLAN membership:
Direct Access noBR-DirectAc-
cess.txt3 <<3001-3006> BTS <3701> IP-Telephony <3601> CEN-DMZ
Control Site,
<3011-3015> BTS (if
dual Links)
Layer 2 P2P Template-Net- Auto/Auto, Tagged, Auto/Auto, Tagged, Auto/Auto, Tagged,

with Border conf-L2-PtP- VLANs: VLANs: VLANs:
Router BR.txt
<3001-3006> BTS <3001-3006> BTS <3001-3006> BTS
Control Site, Control Site, Control Site,
<3011-3015> BTS (if <3011-3015> BTS (if <3011-3015> BTS (if
dual Links), dual Links), dual Links),
<3601> CEN-DMZ <3601> CEN-DMZ <3601> CEN-DMZ
Layer 34, no Template-Net- Auto/Auto, Untagged, Auto/Auto, Untagged, Auto/Auto, Untagged,

Border Router conf-L3- VLAN membership: VLAN membership: VLAN membership: None
noBR.txt
<3001> Primary BTS <3011> Secondary BTS
Control Site
Table continued…


Example of .csv
template name
Layer 34 with Template-Net- Auto/Auto, Untagged, Auto/Auto, Untagged, Auto/Auto, Untagged,
Local Border conf-L3-BR.txt VLAN membership: VLAN membership: VLAN membership:
Router
<3001> Primary BTS <3011> Secondary BTS <3601> CEN-DMZ
Control Site
Layer 34 with Template-Net- Auto/Auto, Untagged, Auto/Auto, Untagged, Auto/Auto, Untagged,

Remote Border conf-L3- VLAN membership: VLAN membership: VLAN membership: None
Router BRL3.txt
<3001> Primary BTS <3011> Secondary BTS
Control Site
1When a port is “tagged” the outgoing Ethernet frames have 802.1Q tag based on VLAN membership. “Untagged” means
that the port is a member of the listed VLAN and no 802.1Q tag is used for outgoing Ethernet frames on this port.
2Value in brackets represents default VLAN number (can be adjusted in the relevant .csvfile). The actual number and type
of configured VLANs depend on enabled feature e.g. if the Dual Site Links are not used the BTS VLAN for dual site link is
not created.
3To use the Template-Netconf-L2-MtM-noBR-DirectAccess.txt for P2P topology the following variable
needs to be set to TRUE instead of FALSE: IS_P2P_TUNNEL, TRUE.
4ForLGT use the relevant L3 row, for example, for “Layer 3 LGT with no Border Router” use the “Layer 3 with no Border
Router” row as the reference for Access port settings.
Border Router
Routing – When you use BR you have to configure routing on it to point out all used public API servers subnet. The
following examples present Border Router configuration.
Motorola Border Configuration

The syntax of the configuration following example is only for informational purposes.
# Administratively Disable the paths
Note: “#” is a comment line operator in the Router. Anything written preceding this parameter is not
processed as command by the Router and is only to improve the readability.
The following block describes the commands used to disable all the Interface paths in the Router.
SETDefault !1 -PAth CONTrol = Disable

SETDefault !2 -PAth CONTrol = Disable
# System Setup
The following block describes the commands used for setting up initial system parameters in the Router.
SETD -SYS NMPrompt = "<string expected within the parenthesis>"

SETD -SYS Prompt = "<string expected within the parenthesis>"
SETD -SYS WelcomeString = "<string expected within the parenthesis>"
SETD -SYS SysLOCation = "<Zone location string expected within the
parenthesis>"
SETD -SYS SysNAMe = "<usually name of the Border router string expected
within the parenthesis>"
SETD -SYS TimeZone = <Time zone value expected>

# LAN Port, Path Setup

The following block describes the commands used for setting up interface configuration in the Router.
SETD !1 -PAth BAud = 100000

SETD !1 -PAth DUplex = Full
Note: Repeat these two commands for all the interfaces in use.
# IP Routing Setup
The following block describes the commands used for Routing in the Router.
SETDefault -IP CONTrol = Route

# VLAN Setup
The following block describes the commands used for setting up Vlans on the Router Interfaces.
ADD !v<vlan identifier> -POrt VirtualPort <Physical port number>VLan

<Backhaul Vlan identifier>
SETDefault !v<vlan identifier> -POrt NAme="<port name string expected within
the parenthesis>"
Note: The above Vlan setup shall be repeated for setting up CEN Interface.
Suggestion: The Backhaul, CEN vlan setup on Port 1 must be configured as follows:
ADD !v1 -POrt VirtualPort 1 VLan 3601

SETDefault !v1 -POrt NAme="Backhaul"
ADD !v10 -POrt VirtualPort 1 VLan 40

SETDefault !v10 -POrt NAme="CEN"
# LAN IP Address Setup
The following block describes the commands used for assigning IP addresses to the Router Interfaces.
SETD -IP SystemIP = <system IP address expected>

SETDefault -SYS UseSystemIP = (NTP, FTP, PING, SNMP, Telnet, TFTP)
SETD !v<backhaul vlan identifier> -IP NETaddr = <backhaul ip address> <Subnet
mask>
SETD !v<CEN vlan identifier> -IP NETaddr = <CEN ip address> <Subnet mask>
# IP over IP tunnel settings
The following block describes the commands used for setting up IP over IP tunnels.
Note: IP over IP tunnel configuration is only required if the system is enabled for Packet Data feature.
add !v<IPoIP vlan identifier> -po vp ipip <backhaul ip address> <Tunnel

termination IP address defined on the Combined Router>
add !v<IPoIP vlan identifier> -ip net = <Tunnel interface IP address> <Subnet
mask>
Note: The Tunnel interface IP address must reside in the same subnet as defined in the Tunnel setup of the
Combined Router.
# IP Route Setup

The following block describes the commands used for setting up IP Routings.
ADD -IP ROUte 0.0.0.0 0.0.0.0 <gateway IP address pointing towards CGE
Router> 1
ADD -IP ROUte <APN IP address> <Subnet Mask> !v<IPoIP vlan identifier> 1
# NAT Setup
The following block describes the commands used for setting up NAT.
Note: NAT configuration is only required, if the system is enabled for Short Data feature.
ADD !v<backhaul vlan identifier> -NAT AddressMap <CEN Native IP address of

the host> <CEN Nated IP address of the Host> bidirectional
Note: The above NAT settings are repeated for all the CEN clients accessing the Short Data API from RNI.
SETDefault !v<backhaul vlan identifier> -NAT CONTrol = Enable

# Port/Path Enable
The following block describes the commands to be used to enable all the used Interface ports/ paths in the Router.
SETDefault ! <Interface Port number> -POrt CONTrol = Enable

SETDefault ! <Interface Port number> -PAth CONTrol = Enable
# Disable Unused Ports
The following block describes the commands to be used to enable all the unused Interface ports/ paths in the Router.
SETDefault ! <Interface Port number> -POrt CONTrol = Disable

SETDefault ! <Interface Port number> -PAth CONTrol = Disable
# End of Motorola Border Router Configuration file
Third party (Juniper) Border Configuration

Juniper border Router configuration is based on third party Juniper Security gateway (SRX100- sw version
10.4R4.5;).
The syntax of the provided configuration example is only for informational purposes. See the Vendor documentation
in case of any syntax/semantic changes occurring in the vendor configuration.
# IP over IP configuration
Note: IP over IP tunnel configuration is only required, if the system is enabled for Packet Data feature.
interfaces {
ip-0/0/0 {
unit 0 {
tunnel {
source <backhaul ip address>;
destination <Tunnel termination IP address defined on the Combined Router>;
path-mtu-discovery;
}
family inet {
address <Tunnel interface IP address> /<Subnet mask identifier>;
}

}
}
# Interface Configuration
fe-0/0/1 {
unit 0 {
family inet {
filter {
input incoming;
}
address <CEN IP Addess>/<Subnet mask identifier>;
}
}
}
fe-0/0/2 {
unit 0 {
family inet {
address <Backhaul subnet IP Addess>/<Subnet mask identifier>;
}
}
}
}
# Routing setup
routing-options {
static {
route 0.0.0.0/0 {
next-hop <gateway IP address pointing towards CGE Router>;
metric 1;
}
route <APN IP subnet>/<Subnet mask identifier>{
next-hop <Tunnel interface IP address>;
metric 1;
}
}
}
# NAT Setup
security {
nat {
static {
rule-set r1 {
from interface fe-0/0/2.0;
rule static {
match {
destination-address <CEN Nated IP address of the Host>/32;
}
then {
static-nat prefix <CEN Native IP address of the host>/32;
}
}
}
}
Note: The provided NAT settings are repeated for all the CEN clients accessing the Short Data API from
RNI.
proxy-arp {
interface fe-0/0/2.0 {
address {

<CEN Nated IP address of the Host>/32 to <CEN Nated IP address of the Host>/
32;
}
}
}
}
Note: The above Proxy ARP settings are repeated for all the CEN clients defined in the NAT setup.
# Security Zone setup
zones {
security-zone untrust {
host-inbound-traffic {
system-services {
ping;
}
}
interfaces {
fe-0/0/1.0;
ip-0/0/0.0;
}
}
security-zone trust {
system-services {
ping;
}
}
interfaces {
fe-0/0/2.0;
}
}
security-zone test {
system-services {
ping;
}
}
}
}
policies {
from-zone trust to-zone untrust {
policy po {
match {
source-address any;
destination-address any;
application any;
}
then {
permit;
}
}
}
from-zone untrust to-zone trust {
policy po1 {
match {
source-address any;
destination-address any;
application any;
}

then {
permit;
}
}
}
default-policy {
permit-all;
}
}
flow {
tcp-mss {
all-tcp {
mss 19000;
}
}
}
}
firewall {
filter incoming {
term allow-access {
from {
protocol [ tcp icmp udp ];
}
}
}
}
# End of Juniper Router Configuration
Third party (HP) Border Configuration

HP border Router configuration is based on third party HP Router Model (MSR20-21).
The syntax of the configuration example provided below is only for informational purposes. See the Vendor
documentation in case of changes.
# Router Interface setup
interface Ethernet0/1
port link-mode route
duplex full
speed 100
ip address <CEN IP Addess><Subnet mask>
port link-mode route
nat outbound static
duplex full
speed 100
ip address <backhaul IP address><subnet mask>
natpt enable
interface NULL0
port link-mode bridge
#
#
#


#
#
#
# IPoverIP tunnel setup for Packet Data feature
Note: IP over IP tunnel configuration is only required if the system is enabled for Packet Data feature.
interface Tunnel1
ip address <Tunnel interface IP address> <Subnet mask>
tunnel-protocol ipv4-ipv4
source <backhaul ip address>
destination <Tunnel termination IP address defined on the Combined Router>
#
ip route-static 0.0.0.0 0.0.0.0 <gateway IP address pointing towards CGE
Router> preference 1
ip route-static <APN IP address> <Subnet Mask> Tunnel1
#
# NAT setup
Note: NAT configuration is only required if the system is enabled for Short Data feature.
nat static <CEN Native IP address of the host> <CEN Nated IP address of the
Host>
Note: The provided NAT settings are repeated for all the CEN clients accessing the Short Data API from
RNI.
# End of HP configuration Border Router Configuration
Customer Enterprise Network (CEN) Hosts

Routing – Every CEN host should have routing configured to access CEN API servers.
For Layer 2 topology, where no BR is used and CEN is separated from the corporate network, use
CEN_DMZ_CGR_IP as the default gateway.
For more complex cases, such as Layer 3 or Layer 2 topologies with BR, configure the default gateway or static
routes for CEN API servers subnet using GBN Gateway IP or BR as gateways.
Domain Name Services (DNS) – The hosts cannot use DNS server to resolve RNI IP addresses. Use the hosts file
instead to define hostname - IP address mappings when the name resolving is required, for example for UCS API.

231 | Alarm Guidelines
Appendix
B
Alarm Guidelines
State/cause alarms indicate a change in status for a particular device. State/cause alarms represent the most current
status of a system. Click Refresh to refresh the state/cause alarms list on the Current Status page.
Transient alarms, also known as technician messages, are general events that do not affect the state of an object in
the system (such as a successful database export or failed connection to remote system). Transient alarms are meant to
provide useful information to assist the user in managing and troubleshooting the radio system. Transient alarms are
sometimes sent in conjunction with state/cause alarm messages to provide additional information about failure
conditions. Any event that would not cause a status change in a managed object is reported as a transient alarm. Those
types of alarms are reported on the All Events page.
State/Cause Alarm Texts

The following parts contain tables listing the State/Cause Alarm Text for Dimetra IP Micro/Dimetra LiTE object
types.
AISA
The following table contains an explanation of source information displayed in the Web NM, Status page for the
AISA object.
Table 51: Explanation of the Source Content of an Alarm Message for the Aisa Object
Source Interpretation of Source Example/Comments

Aisa_a.b.c a = Console Site ID, b = Application Plat- Aisa_1002.3.1 is equal to Aisa 1 on
form ID, c = Aisa ID Application Platform 3 on Console
Site 1002
The following table lists the state and cause text for the AISA object.
Table 52: State/Cause Text for the AISA Object
State State Text Se- Cause Cause Text Recommendation

Number verity Number
1 UNCONFIGURED warn- 1 RESET Alarm determined node
ing (4) was in unconfigured
state. Transitory state.
No action may be need-
ed if node is initializ-
ing. Investigate final
state or if alarm per-
sists, investigate ac-
companying transient
Table continued…


alarms or state transi-
tions or the node con-
figuration or connectiv-
ity or contact service
personnel to investi-
gate.
gate.
1 UNCONFIGURED warn- 9998 UNKNOWN CAUSE Alarm determined node
gate.
2 ENABLING warn- 2 USER REQUESTED State change caused by
ing (4) a user initiated opera-
tion. No action re-
quired.
tion. No action re-
quired.
2 ENABLING warn- 9998 UNKNOWN CAUSE Transition state. No ac-
ing (4) tion required if user re-
quested.
Table continued…

Alarm Guidelines | 233

3 ENABLED nor- 2 USER REQUESTED State change caused by
mal a user initiated opera-
(6) tion. No action re-
quired.
quired.
3 ENABLED nor- 9998 UNKNOWN CAUSE This is normal system
mal operation. No action re-
(6) quired if enable was
user initiated.
4 DISABLING warn- 2 USER REQUESTED State change caused by
tion.
tion.
4 DISABLING warn- 9998 UNKNOWN CAUSE The node is disabling.
ing (4) Check reason: No ac-
tion required if disable
was User Requested or
planned. Note: This is a
transitory state which
should transition to dis-
abled. In case node
does not transition con-
tact service personnel.
5 DISABLED warn- 2 USER REQUESTED State change caused by
tion.
tion.
5 DISABLED warn- 9998 UNKNOWN CAUSE The node is disabled.
planned, otherwise re-
enable if appropriate
and contact service per-
sonnel.
5555 INDETERMINATE inde- 5555 OBJECT NOT Alarm state from object
termi- FOUND was indeterminate and
nate most likely only a tim-
(5) ing related or transitory
state or Fault Manager
Table continued…


has no knowledge of
object. Investigate ac-
companying status
alarms from node or fi-
nal state. Check that
managed object is
known and managed.
Contact service person-
nel if alarm persists.
6 CRITICAL MALFUNC- critical 13 CONFIG FAULT Possible hardware or
TION (1) software configuration
problem. Check instal-
lation and configura-
tion is complete. If the
problem continues con-
tact service personnel
to rectify the module
problem or replace the
module hardware.
6 CRITICAL MALFUNC- critical 14 NETWORK FAULT -
TION (1)
6 CRITICAL MALFUNC- critical 3 CLIENT FAULT AISA Application has
TION (1) failed or has been shut-
down. Contact service
personnel.
6 CRITICAL MALFUNC- critical 4 RESOURCE FAULT Voice Card has a fail-
TION (1) ure condition. Reboot
the Console PC. If the
module hardware.
6 CRITICAL MALFUNC- critical 6003 CLIENT FAULT AISA Application has
personnel.
6 CRITICAL MALFUNC- critical 6004 RESOURCE FAULT Voice Card has a fail-
TION (1) ure condition. Reboot
the Console PC. If the
module hardware.
Table continued…


module hardware.
6 CRITICAL MALFUNC- critical 6014 NETWORK FAULT -
TION (1)
6 CRITICAL MALFUNC- critical 9998 UNKNOWN CAUSE AISA Application has
personnel. Possible
CryptoCards / connec-
tion failure.
7 MAJOR MALFUNC- major 10 KEYSET MIS- -
TION (2) MATCH
7 MAJOR MALFUNC- major 11 ALGORITHM MIS- -
TION (2) MATCH
7 MAJOR MALFUNC- major 12 KEYSET AND AL- -
TION (2) GORITHM MIS-
MATCH
7 MAJOR MALFUNC- major 14 NETWORK FAULT -
TION (2)
7 MAJOR MALFUNC- major 4 RESOURCE FAULT -
TION (2)
7 MAJOR MALFUNC- major 7004 RESOURCE FAULT -
TION (2)
7 MAJOR MALFUNC- major 7010 KEYSET MIS- -
TION (2) MATCH
7 MAJOR MALFUNC- major 7011 ALGORITHM MIS- -
TION (2) MATCH
7 MAJOR MALFUNC- major 7012 KEYSET AND AL- -
TION (2) GORITHM MIS-
MATCH
7 MAJOR MALFUNC- major 7014 NETWORK FAULT -
TION (2)
7 MAJOR MALFUNC- major 9998 UNKNOWN CAUSE -
TION (2)
8 MINOR MALFUNC- minor 14 NETWORK FAULT -
TION (3)
8 MINOR MALFUNC- minor 4 RESOURCE FAULT -
TION (3)
Table continued…


8 MINOR MALFUNC- minor 8004 RESOURCE FAULT -
TION (3)
8 MINOR MALFUNC- minor 8014 NETWORK FAULT -
TION (3)
8 MINOR MALFUNC- minor 9998 UNKNOWN CAUSE -
TION (3)
9 WARNING MAL- warn- 14 NETWORK FAULT -
FUNCTION ing (4)
9 WARNING MAL- warn- 4 RESOURCE FAULT -
FUNCTION ing (4)
9 WARNING MAL- warn- 9004 RESOURCE FAULT -
FUNCTION ing (4)
9 WARNING MAL- warn- 9014 NETWORK FAULT -
FUNCTION ing (4)
9 WARNING MAL- warn- 9998 UNKNOWN CAUSE -
FUNCTION ing (4)
9994 UNKNOWN warn- 9992 UNREACHABLE The node is unreacha-
ing (4) FROM MANAGER ble from the manager.
(SNMP NOSUCH- This should only be a
NAME) temporary state other-
wise service personnel
should be alerted to in-
vestigate.
(SNMP GENERICER- This should only be a
ROR) temporary state other-
vestigate.
(SNMP TIMEOUT) This should only be a
temporary state other-
vestigate.
9998 UNKNOWN STATE inde- 9998 UNKNOWN CAUSE Alarm state from object
termi- was indeterminate and
(5) ing related transitory
state. Investigate final
state.

AisaPlatform
AisaPlatform object.
Table 53: Explanation of the Source Content of an Alarm Message for the AisaPlatform Object

The alias assigned to the n/a Since this is an object to which an
ApplicationPlatform ob- alias is assigned, the source infor-
ject associated to the Ai- mation is a user determined setting.
saApplication object
The following table lists the state and cause text for the AisaPlatform object.
Table 54: State/Cause Text for the AisaPlatform Object

gate.
gate.
Table continued…


gate.
tion. No action re-
quired.
tion. No action re-
quired.
quested.
quired.
quired.
user initiated.
tion.
tion.
Table continued…


abled. In case node
tion.
tion.
sonnel.
has no knowledge of
companying status
managed object is
known and managed.
6 CRITICAL MALFUNC- critical 15 TEMPERATURE -
TION (1) FAULT
6 CRITICAL MALFUNC- critical 16 BUSS POWER -
TION (1) FAULT
6 CRITICAL MALFUNC- critical 3 CLIENT FAULT Console PC reported a
TION (1) client fault. Possible
console PC has failed
or has been shutdown.
Check console PC is
booted with correct
configuration (if not
amend and reboot) and
check if the database
synchronization was
successful. Contact
service personnel if
problem persists.
Table continued…


6 CRITICAL MALFUNC- critical 6003 CLIENT FAULT Console PC reported a
TION (1) client fault. Possible
console PC has failed
or has been shutdown.
Check console is boot-
ed with correct config-
uration (if not amend
and reboot) and check
if the database synchro-
nization was success-
ful. Contact service
personnel if problem
persists.
6 CRITICAL MALFUNC- critical 6015 TEMPERATURE -
TION (1) FAULT
6 CRITICAL MALFUNC- critical 6016 BUSS POWER -
TION (1) FAULT
6 CRITICAL MALFUNC- critical 9998 UNKNOWN CAUSE Console PC reported a
TION (1) fault. Possible console
PC has failed or has
been shutdown. Check
console is booted with
correct configuration
(if not amend and re-
boot) and check if the
database synchroniza-
tion was successful.
nel if problem persists.
7 MAJOR MALFUNC- major 17 POWER SUPPLY -
TION (2) FAULT
7 MAJOR MALFUNC- major 18 FAN FAULT -
TION (2)
7 MAJOR MALFUNC- major 7017 POWER SUPPLY -
TION (2) FAULT
7 MAJOR MALFUNC- major 7018 FAN FAULT -
TION (2)
7 MAJOR MALFUNC- major 9998 UNKNOWN CAUSE -
TION (2)
8 MINOR MALFUNC- minor 18 FAN FAULT -
TION (3)
8 MINOR MALFUNC- minor 3 CLIENT FAULT Console PC reported a
Table continued…


8 MINOR MALFUNC- minor 8003 CLIENT FAULT Console PC reported a
8 MINOR MALFUNC- minor 8018 FAN FAULT -
TION (3)
8 MINOR MALFUNC- minor 9998 UNKNOWN CAUSE -
TION (3)
9 WARNING MAL- warn- 19 MONITOR LINK -
FUNCTION ing (4) FAULT
9 WARNING MAL- warn- 9019 MONITOR LINK -
FUNCTION ing (4) FAULT
9 WARNING MAL- warn- 9998 UNKNOWN CAUSE -
FUNCTION ing (4)
vestigate.
vestigate.
Table continued…


vestigate.
state.
AisaVoiceCard
AisaVoiceCard object.
Table 55: Explanation of the Source Content of an Alarm Message for the AisaVoiceCard Object

AisaVoiceCard.a.b.c a = Console Site ID, b = Application Plat- AisaVoiceCard.1002.3.2 is equal to
form ID, c = Voice Card ID Voice Card 2 on Application Plat-
form 3 on Console Site 1002
The following table lists the state and cause text for the AisaVoiceCard object.
Table 56: State/Cause Text for the AisaVoiceCard Object

gate.
Table continued…


gate.
gate.
2 ENABLING warn- 1 RESET Transition state. No ac-
quested.
2 ENABLING warn- 13 CONFIG FAULT Transition state. Possi-
ing (4) ble node configuration
issue - configuration in-
complete or with er-
rors. Most likely seen
during commissioning
phase only. No action
required if user request-
ed otherwise contact
service personnel to in-
vestigate.
quested.
Table continued…


vestigate.
quested.
3 ENABLED nor- 1 RESET This is normal system
(6) quired.
(6) quired.
user initiated.
has no knowledge of
companying status
managed object is
known and managed.
6 CRITICAL MALFUNC- critical 5 CARD FAULT Possible hardware
TION (1) problem. If the problem
continues contact serv-
ice personnel to rectify
the module problem or
replace the module
hardware.
replace the module
hardware.
6 CRITICAL MALFUNC- critical 9998 UNKNOWN CAUSE Possible hardware
Table continued…


replace the module
hardware.
vestigate.
vestigate.
vestigate.
state.
ATR
The following table contains an explanation of source information displayed in the Web NM, Status page for the ATR
object.
Table 57: Explanation of the Source Content of an Alarm Message for the ATR Object

ATR n/a Fixed name
The following table lists the state and cause text for the ATR object.

Table 58: State/Cause Text for the Atr Object

1 ENABLING nor- 1300 USER REQUESTED State change caused by
quired.
1 ENABLING nor- 300 USER REQUESTED State change caused by
quired.
1 ENABLING nor- 9998 UNKNOWN CAUSE Transition state. No ac-
mal tion required if user re-
(6) quested.
2 ENABLED nor- 2302 ALL PROCESS ENA- This is normal system
mal BLED operation. No action re-
(6) quired.
2 ENABLED nor- 302 ALL PROCESS ENA- This is normal system
mal BLED operation. No action re-
(6) quired.
user initiated.
tion.
3 DISABLING warn- 301 ENABLING FAILED The server could not be
ing (4) enabled and current
transitional status is
disabling. An error has
occurred however
please wait and check
final state. Try again or
contact Motorola sup-
port in case that alarm
persists.
3 DISABLING warn- 303 USER REQ SHUT- State change caused by
ing (4) DOWN a user initiated opera-
tion.
tion.
3 DISABLING warn- 3301 ENABLING FAILED The server could not be
ing (4) enabled and current
transitional status is
disabling. An error has
occurred however
Table continued…


please wait and check
final state. Try again or
contact Motorola sup-
port in case that alarm
persists.
3 DISABLING warn- 3303 USER REQ SHUT- State change caused by
ing (4) DOWN a user initiated opera-
tion.
abled. In case node
4 DISABLED major 300 USER REQUESTED State change caused by
(2) a user initiated opera-
tion.
4 DISABLED major 301 ENABLING FAILED The server could not be
(2) enabled. Please try
again or contact Motor-
ola support.
4 DISABLED major 303 USER REQ SHUT- State change caused by
(2) DOWN a user initiated opera-
tion.
4 DISABLED major 4300 USER REQUESTED State change caused by
tion.
4 DISABLED major 4301 ENABLING FAILED The server could not be
(2) enabled. Please try
again or contact Motor-
ola support.
4 DISABLED major 4303 USER REQ SHUT- State change caused by
tion.
4 DISABLED major 9998 UNKNOWN CAUSE The node is disabled.
(2) Check reason: No ac-
sonnel.
Table continued…


5 SHUTDOWN critical 303 USER REQ SHUT- State change caused by
tion.
5 SHUTDOWN critical 5303 USER REQ SHUT- State change caused by
tion.
5 SHUTDOWN critical 9998 UNKNOWN CAUSE The server was shut-
(1) down. No action re-
quired if shutdown was
User Requested.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.


state.
AtrZcLink
AtrZcLink object.
Table 59: Explanation of the Source Content of an Alarm Message for the AtrZcLink Object

AtrZcLink_1 n/a Fixed name
The following table lists the state and cause text for the AtrZcLink object.
Table 60: State/Cause Text for the AtrZcLink Object

1 UP nor- 1400 CONNECTION UP This is normal system
(6) quired.
1 UP nor- 400 CONNECTION UP This is normal system
(6) quired.
1 UP nor- 9998 UNKNOWN CAUSE This is normal system
(6) quired.
2 DOWN critical 2401 CONNECTION Connection between
(1) DOWN ATR and ZC down.
Check the ATR and
Zone Controller status
and the network con-
nectivity.
2 DOWN critical 401 CONNECTION Connection between
(1) DOWN ATR and ZC down.
Check the ATR and
and the network con-
nectivity.
2 DOWN critical 9998 UNKNOWN CAUSE Connection from ZC to
(1) the ATR is down. No
action required if ATR
or ZC disable was User
Requested. If link
down is unexpected
please check the ATR,
ZC and link status and
Table continued…


contact service person-
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.
state.
AuC
The following table contains an explanation of source information displayed in the Web NM, Status page for the AuC
object.

Table 61: Explanation of the Source Content of an Alarm Message for the AuC Object

Authentication_Center_ a.b.c.d = IP address of the AuC Authentication_Center_10.0.1.219 is
a.b.c.d equal to the AuC with IP address
10.0.1.219
The following table lists the state and cause text for the AuC object.
Table 62: State/Cause Text for the AuC Object

1 DISABLED critical 1 UNKNOWN The AuC is disabled.
(1) New key material can
not be distributed. In-
vestigate possible soft-
ware or hardware prob-
lem with AUC.
1 DISABLED critical 2 RESET State transition. Please
(1) wait for final state.
1 DISABLED critical 3 OPERATOR COM- State change caused by
(1) MAND a user initiated opera-
tion.
1 DISABLED critical 4 CRYPTO RE- The AuC is disabled.
(1) SOURCE FAILURE New key material can
vestigate possible soft-
ware or hardware prob-
lem with AUC.
1 DISABLED critical 5 DATABASE FAIL- The AuC is disabled.
(1) URE New key material can
vestigate possible con-
figuration, software or
database problem. If
database is suspected to
be corrupt then restore
database from backup
or contact Motorola
support.
1 DISABLED critical 9998 UNKNOWN CAUSE The node is disabled.
sonnel.
Table continued…


(6) quired.
2 ENABLED nor- 3 OPERATOR COM- State change caused by
mal MAND a user initiated opera-
quired.
user initiated.
3 DISCONNECTED major 6 NETWORK FAIL- Check the network con-
(2) URE nection to the Authenti-
cation Server.
3 DISCONNECTED major 9998 UNKNOWN CAUSE Check the network con-
(2) nection to the Authenti-
cation Server.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
Table continued…


vestigate.
state.
AudioRP
AudioRP object.
Table 63: Explanation of the Source Content of an Alarm Message for the AudioRP Object

AudioRP n/a Fixed name
The following table lists the state and cause text for the AudioRP object.
Table 64: State/Cause Text for the AudioRP Object

1 UNKNOWN inde- 1 NO REASON Alarm state from object
state.
1 UNKNOWN inde- 1001 NO REASON Alarm state from object
state.
2 UNCONFIGURED critical 1 NO REASON Alarm determined node
(1) was in unconfigured
Table continued…


gate.
gate.
2 UNCONFIGURED critical 2004 USER REQUESTED State change caused by
tion.
tion.
3 ENABLED nor- 1 NO REASON This is normal system
user initiated.
user initiated.
4 ENABLING warn- 4005 RECOVERY Transition state. Inves-
ing (4) tigate final state and
cause of AudioRP loss/
recovery. No action re-
quired if user request-
ed.
4 ENABLING warn- 5 RECOVERY Transition state. Inves-
ing (4) tigate final state and
cause of AudioRP loss/
recovery. No action re-
ed.
Table continued…


tion.
tion.
has no knowledge of
companying status
managed object is
known and managed.
tion.
tion.
7 MALFUNCTIONED critical 2 RP PATH DOWN Node has indicated a
(1) malfunction because
the Rendezvous Point
path is down. This is a
possible hardware or
connectivity problem.
Investigate configura-
tion of node RP rout-
ing/connectivity.
7 MALFUNCTIONED critical 3 NO MCIP ADDRESS Node has indicated a
(1) malfunction because no
Multi-Cast IP address
is configured. This is a
tion of node MCIP
routing connectivity.
7 MALFUNCTIONED critical 7002 RP PATH DOWN Node has indicated a
(1) malfunction because
the Rendezvous Point
path is down. This is a
Table continued…


tion of node RP rout-
ing/connectivity.
7 MALFUNCTIONED critical 7003 NO MCIP ADDRESS Node has indicated a
(1) malfunction because no
Multi-Cast IP address
is configured. This is a
tion of node MCIP
routing connectivity.
vestigate.
vestigate.
vestigate.
state.
Ccgw
Ccgw object.

Table 65: Explanation of the Source Content of an Alarm Message for the Ccgw Object

Ccgw_a.b a = Analog Conventional Site ID, b = Ccgw_2003.2 is equal to CCGW 2
CCGW ID on Analog Conventional Site 2003
The following table lists the state and cause texts for the Ccgw object.
Table 66: State/Cause Text for the Ccgw Object

1 UNCONFIGURED minor 1018 CCGW INCOM- No action required.
(3) PLETE CONFIGU-
RATION DATA
2 DISABLED warn- 1 CCGW CONFIGU- Configuration associat-
ing (4) RATION COM- ed with CCGW was
PLETE completed by user and
it has been configured
to be disabled.
ing (4) CCGW DISABLE a user initiated opera-
tion.
2 DISABLED warn- 2001 CCGW CONFIGU- Configuration associat-
ing (4) RATION COM- ed with CCGW was
PLETE completed by user and
it has been configured
to be disabled.
ing (4) CCGW DISABLE a user initiated opera-
tion.
3 DOWN critical 3 USER REQUESTED State change caused by
(1) CCGW ENABLE a user initiated opera-
tion.
3 DOWN critical 3003 USER REQUESTED State change caused by
(1) CCGW ENABLE a user initiated opera-
tion.
3 DOWN critical 3004 CCGW-ZC CP The Zone Controller
(1) DOWN Control Path is down.
Check the Zone Con-
troller status and con-
nectivity.
3 DOWN critical 4 CCGW-ZC CP The Control Path be-
(1) DOWN tween Zone Controller
and CCGW is down.
Check CCGW and the
and connectivity.
Table continued…


4 UP nor- 11 ALL CHANNELS UP This is normal system
(6) quired.
4 UP nor- 13 BOTH DSPS RE- Both DSPs recovered
mal COVERED from failed state and
(6) CCGW node is now up.
No action required.
4 UP nor- 4003 USER REQUESTED This is normal system
mal CCGW ENABLE operation. No action re-
(6) quired.
4 UP nor- 4005 CCGW-ZC CP UP This is normal system
(6) quired.
4 UP nor- 4007 4W CARD RECOV- 4W (4 wire EM mod-
mal ERED ule) Card recovered
(6) from failure state. No
action required.
4 UP nor- 4011 ALL CHANNELS UP This is normal system
(6) quired.
4 UP nor- 4013 BOTH DSPS RE- Both DSPs recovered
mal COVERED from failed state and
(6) CCGW node is now up.
No action required.
4 UP nor- 4017 V24 CARD RECOV- No action required.
mal ERED
(6)
4 UP nor- 5 CCGW-ZC CP UP This is normal system
(6) quired.
4 UP nor- 7 4W CARD RECOV- 4W (4 wire EM mod-
mal ERED ule) Card recovered
(6) from failure state. No
action required.
5 DEGRADED minor 5008 USER HAS DISA- State change caused by
(3) BLED 50% OR a user initiated opera-
MORE CHANNELS tion.
5 DEGRADED minor 5009 USER ENABLED State change caused by
(3) CHANNELS. 50% + a user initiated opera-
CHANS ARE tion.
AVAILABLE
5 DEGRADED minor 8 USER HAS DISA- State change caused by
(3) BLED 50% OR a user initiated opera-
MORE CHANNELS tion.
Table continued…


5 DEGRADED minor 9 USER ENABLED State change caused by
(3) CHANNELS. 50% + a user initiated opera-
CHANS ARE tion.
AVAILABLE
has no knowledge of
companying status
managed object is
known and managed.
6 MAJOR MALFUNC- major 15 ONE DSP RECOV- One DSP has recovered
TION (2) ERED from failure condition
but status indicates a
major malfunction still
exists - possible hard-
ware failure. Investi-
gate accompanying
alarms or states to de-
termine what else is in
failure condition and
nel for possible hard-
ware replacement.
6 MAJOR MALFUNC- major 6015 ONE DSP RECOV- One DSP has recovered
TION (2) ERED from failure condition
but status indicates a
major malfunction still
exists - possible hard-
ware failure. Investi-
gate accompanying
alarms or states to de-
termine what else is in
failure condition and
nel for possible hard-
ware replacement.
6 MAJOR MALFUNC- major 6020 LESS THAN 50% No action required.
TION (2) AVAILABLE
7 CRITICAL MALFUNC- critical 10 NO AVAILABLE Capacity problem. The
TION (1) CHANNELS. resources are not avail-
able. It the problem
Table continued…


ice personnel. Correc-
tive action could be to
increase capacity.
7 CRITICAL MALFUNC- critical 12 BOTH DSPS HAVE Both Digital Signal
TION (1) FAILED Processing devices
failed. Investigate ac-
companying alarms or
nel to investigate possi-
ble hardware replace-
ment.
7 CRITICAL MALFUNC- critical 14 ONE DSP FAILED A Digital Signal Proc-
TION (1) essing device has
ment.
7 CRITICAL MALFUNC- critical 6 4W CARD FAILED 4W (4 wire EM mod-
TION (1) ule) Card failure. Con-
to investigate possible
hardware replacement.
7 CRITICAL MALFUNC- critical 7006 4W CARD FAILED 4W (4 wire EM mod-
TION (1) ule) Card failure. Con-
to investigate possible
hardware replacement.
7 CRITICAL MALFUNC- critical 7010 NO AVAILABLE Capacity problem. The
TION (1) CHANNELS. resources are not avail-
able. It the problem
ice personnel. Correc-
tive action could be to
increase capacity.
7 CRITICAL MALFUNC- critical 7012 BOTH DSPS HAVE Both Digital Signal
TION (1) FAILED Processing devices
ment.
7 CRITICAL MALFUNC- critical 7014 ONE DSP FAILED A Digital Signal Proc-
TION (1) essing device has
Table continued…


ment.
7 CRITICAL MALFUNC- critical 7016 V24 CARD FAILED No action required.
TION (1)
8 MINOR MALFUNC- minor 8019 BETWEEN 100% No action required.
TION (3) AND 50% (INCLU-
SIVE) CHANNELS
AVAILABLE
vestigate.
vestigate.
vestigate.
state.
CcgwZcCp
CcgwZcCp object.
Table 67: Explanation of the Source Content of an Alarm Message for the CcgwZcCp Object

CcgwZcCp_a.b.c.d a = Analog Conventional Site ID, b = CcgwZcCp_2001.3.1.2 is equal to
CCGW ID, c = 1, d = ZC Control Path ID CCGW 3 on Analog Conventional


or a = 1, b = Analog Conventional Site Site 2001 to Zone Controller 2 Con-
ID, c = CCGW ID, d = ZC Control Path trol Path or CcgwZcCp_1.2001.3.1
ID is equal to Zone Controller 1 to
CCGW 3 on Analog Conventional
Site 2001 Control Path
The following table lists the state and cause texts for the CcgwZcCp object.
Table 68: State/Cause Text for the CcgwZcCp Object

1 DOWN critical 1002 CCGW-ZC CON- Connection between
(1) NECTION LOST Zone Controller and
CCGW lost. Check
CCGW and the Zone
Controller status and
connectivity.
1 DOWN critical 2 CCGW-ZC CON- Connection between
(1) NECTION LOST Zone Controller and
CCGW lost. Check
CCGW and the Zone
Controller status and
connectivity.
2 UP nor- 1 CCGW-ZC CON- This is normal system
mal NECTION ESTAB- operation. No action re-
(6) LISHED quired.
2 UP nor- 2001 CCGW-ZC CON- This is normal system
mal NECTION ESTAB- operation. No action re-
(6) LISHED quired.
has no knowledge of
companying status
managed object is
known and managed.
Table continued…


vestigate.
vestigate.
vestigate.
state.
CnsRouterSiteManagerLink
CnsRouterSiteManagerLink object.
CnsRouterSiteManagerLink Object

CnsRouterSiteManager- b = Console Site ID CnsRouterSiteManager-
Link_3.b.1 Link_3.1002.1 is equal to Console
Site 1002 to Zone Database Server
(ZDS) Link
The following table lists the state and cause text for the CnsRouterSiteManagerLink object.
Table 70: State/Cause Text for the CnsRouterSiteManagerLink Object

1 UNKNOWN warn- 1 UNKNOWN CAUSE Alarm state from object
ing (4) was unknown and most
likely only a timing re-
lated transitory state.
Investigate accompany-
ing alarms and final
Table continued…


transition state. If alarm
state persists investi-
gate connectivity from
the node subsystem to
the node or from the
node to manager or
nel to investigate.
node to manager or
nel to investigate.
node to manager or
nel to investigate.
1 UNKNOWN warn- 2 NO CONNECTION Alarm state from object
Investigate final state.
If state remains persis-
tent check network
connectivity between
Manager and Site.
Table continued…


node to manager or
nel to investigate.
2 UP nor- 2003 CONNECTION ES- This is normal system
mal TABLISHED operation. No action re-
(6) quired.
(6) quired.
(6) quired.
3 DOWN critical 2 NO CONNECTION Connection between
(1) manager server and site
is lost.
is lost.
3 DOWN critical 9998 UNKNOWN CAUSE Connection between
is lost.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
Table continued…


vestigate.
vestigate.
termi- was unknown and most
nate likely only a timing re-
(5) lated transitory state.
CnsSwitchSiteManagerLink
CnsSwitchSiteManagerLink object.
Note: This object is optional, therefore, its status may be unknown (UNREACHABLE FROM
MANAGER) in some cases.
CnsSwitchSiteManagerLink Object

CnsSwitchSiteManager- b = Console Site ID CnsSwitchSiteManager-
Link_3.b.1 Link_3.1002.1 is equal to Console
Site 1002 to Zone Database Server
(ZDS) Link
The following table lists the state and cause texts for the CnsSwitchSiteManagerLink object.
Table 72: State/Cause Text for the CnsSwitchSiteManagerLink Object

Table continued…


node to manager or
nel to investigate.
node to manager or
nel to investigate.
node to manager or
nel to investigate.
1 UNKNOWN warn- 2 NO CONNECTION Alarm state from object
If state remains persis-
tent check network
connectivity between
Manager and Site.
Table continued…


node to manager or
nel to investigate.
(6) quired.
(6) quired.
(6) quired.
is lost.
is lost.
3 DOWN critical 9998 UNKNOWN CAUSE Connection between
is lost.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
Table continued…


vestigate.
vestigate.
Conventional Channel
Table 73: Explanation of the Source Content of an Alarm Message for the ConventionalChannel
Object

ConventionalChan- a = Analog Conventional Site ID, b = ConventionalChannel_2001.1.1 is equal to
nel_a.b.c CCGW ID, c = Analog Conventional Analog Conventional Channel 1 on
Channel ID CCGW 1 on Analog Conventional Site
2001
Table 74: State/Cause Text for the ConventionalChannel Object
State State Text Severity Cause Cause Text Recommendation

Num- Num-
ber ber
1 UP normal (6) 1 USER ENABLE CHAN- State change caused by a user initiated
NEL operation. No action required.
1 UP normal (6) 1001 USER ENABLE CHAN- State change caused by a user initiated
NEL operation. No action required.
1 UP normal (6) 1003 CHANNEL RECOV- No action required.
ERED
1 UP normal (6) 3 CHANNEL RECOV- No action required.
ERED
2 DOWN warning (4) 2 USER DISABLE State change caused by a user initiated
CHANNEL operation.
Table continued…

State State Text Severity Cause Cause Text Recommendation

Num- Num-
ber ber
2 DOWN warning (4) 2002 USER DISABLE State change caused by a user initiated
CHANNEL operation.
2 DOWN warning (4) 2004 CHANNEL FAILED If alarm persists contact service person-
nel.
2 DOWN warning (4) 4 CHANNEL FAILED If alarm persists contact service person-
nel.
5555 INDETER- indetermi- 5555 OBJECT NOT FOUND Alarm state from object was indetermi-
MINATE nate (5) nate and most likely only a timing related
or transitory state or Fault Manager has
no knowledge of object. Investigate ac-
companying status alarms from node or
final state. Check that managed object is
known and managed. Contact service
personnel if alarm persists.
9994 UN- warning (4) 9992 UNREACHABLE The node is unreachable from the man-
KNOWN FROM MANAGER ager. This should only be a temporary
(SNMP NOSUCH- state otherwise service personnel should
NAME) be alerted to investigate.
(SNMP GENERICER- state otherwise service personnel should
ROR) be alerted to investigate.
(SNMP TIMEOUT) state otherwise service personnel should
be alerted to investigate.
9998 UN- indetermi- 9998 UNKNOWN CAUSE Alarm state from object was indetermi-
KNOWN nate (5) nate and most likely only a timing related
STATE transitory state. Investigate final state.
DispatchApplication
DispatchApplication object.
Table 75: Explanation of the Source Content of an Alarm Message for the DispatchApplication
Object

DispatchApplica- a = Console Site ID, b = Application Plat- DispatchApplication_1001.2.1 is
tion_a.b.c form ID, c = Dispatch Application ID equal to Dispatch Application 1 on
Application Platform 2 on Console
Site 1001
The following table lists the state and cause texts for the Dispatch object.

Table 76: State/Cause Text for the Dispatch Object

gate.
gate.
gate.
10 ENABLEDLOGGED- nor- 10002 USER REQUESTED If alarm persists contact
OFF mal service personnel.
(6)
Table continued…


10 ENABLEDLOGGED- nor- 2 USER REQUESTED If alarm persists contact
OFF mal service personnel.
(6)
10 ENABLEDLOGGED- nor- 9998 UNKNOWN CAUSE State change caused by
OFF mal a user initiated opera-
(6) tion.
11 DISABLEDLOGGED- warn- 11002 USER REQUESTED If alarm persists contact
OFF ing (4) service personnel.
11 DISABLEDLOGGED- warn- 2 USER REQUESTED If alarm persists contact
11 DISABLEDLOGGED- warn- 9998 UNKNOWN CAUSE If alarm persists contact
tion. No action re-
quired.
tion. No action re-
quired.
quested.
quired.
quired.
user initiated.
tion.
tion.
Table continued…


abled. In case node
tion.
tion.
sonnel.
has no knowledge of
companying status
managed object is
known and managed.
module hardware.
6 CRITICAL MALFUNC- critical 3 CLIENT FAULT Dispatch Application
TION (1) has failed or has been
shutdown. Check con-
sole PC is booted with
Table continued…


6 CRITICAL MALFUNC- critical 4 RESOURCE FAULT Voice Card or GPIOM
TION (1) has a failure condition.
Check GPIOM connec-
tion to the Console PC
and peripherals connec-
tion to the GPIOM. Re-
boot the Console PC. If
the problem continues
nel to rectify the mod-
ule problem or replace
the module hardware.
6 CRITICAL MALFUNC- critical 6003 CLIENT FAULT Dispatch Application
6 CRITICAL MALFUNC- critical 6004 RESOURCE FAULT Voice Card or GPIOM
TION (1) has a failure condition.
Check GPIOM connec-
tion to the Console PC
and peripherals connec-
tion to the GPIOM. Re-
boot the Console PC. If
nel to rectify the mod-
ule problem or replace
the module hardware.
Table continued…


module hardware.
6 CRITICAL MALFUNC- critical 9998 UNKNOWN CAUSE Dispatch Application
7 MAJOR MALFUNC- major 10 KEYSET MIS- If alarm persists contact
TION (2) MATCH service personnel.
7 MAJOR MALFUNC- major 11 ALGORITHM MIS- If alarm persists contact
7 MAJOR MALFUNC- major 12 KEYSET AND AL- If alarm persists contact
TION (2) GORITHM MIS- service personnel.
MATCH
7 MAJOR MALFUNC- major 4 RESOURCE FAULT If alarm persists contact
TION (2) service personnel.
7 MAJOR MALFUNC- major 7004 RESOURCE FAULT If alarm persists contact
7 MAJOR MALFUNC- major 7010 KEYSET MIS- If alarm persists contact
7 MAJOR MALFUNC- major 7011 ALGORITHM MIS- If alarm persists contact
7 MAJOR MALFUNC- major 7012 KEYSET AND If alarm persists contact
TION (2) LGORITHM MIS- service personnel.
MATCH
7 MAJOR MALFUNC- major 9998 UNKNOWN CAUSE If alarm persists contact
8 MINOR MALFUNC- minor 4 RESOURCE FAULT If alarm persists contact
8 MINOR MALFUNC- minor 8004 RESOURCE FAULT If alarm persists contact
8 MINOR MALFUNC- minor 9998 UNKNOWN CAUSE If alarm persists contact
9 WARNING MAL- warn- 4 RESOURCE FAULT If alarm persists contact
FUNCTION ing (4) service personnel.
9 WARNING MAL- warn- 9004 RESOURCE FAULT If alarm persists contact
Table continued…


9 WARNING MAL- warn- 9998 UNKNOWN CAUSE If alarm persists contact
vestigate.
vestigate.
vestigate.
state.
DispatchPlatform
DispatchPlatform object.
Table 77: Explanation of the Source Content of an Alarm Message for the DispatchPlatform Object

The alias assigned to the n/a Since this is an object to which an
DispatchPlatform object alias is assigned, the source infor-
mation is a user defined setting
The following table lists the state and cause texts for the DispatchPlatform object.

Table 78: State/Cause Text for the DispatchPlatform Object

gate.
gate.
gate.
Table continued…


tion. No action re-
quired.
tion. No action re-
quired.
quested.
quired.
quired.
user initiated.
tion.
tion.
abled. In case node
tion.
tion.
Table continued…


sonnel.
has no knowledge of
companying status
managed object is
known and managed.
6 CRITICAL MALFUNC- critical 15 TEMPERATURE If alarm persists contact
TION (1) FAULT service personnel.
6 CRITICAL MALFUNC- critical 16 BUSS POWER If alarm persists contact
6 CRITICAL MALFUNC- critical 3 CLIENT FAULT Dispatch position has
TION (1) reported Client applica-
tion has failed or has
console PC is booted
with correct configura-
tion (if not amend and
reboot) and check if the
6 CRITICAL MALFUNC- critical 6003 CLIENT FAULT Dispatch position has
TION (1) reported Client applica-
tion has failed or has
console PC is booted
with correct configura-
tion (if not amend and
reboot) and check if the
6 CRITICAL MALFUNC- critical 6015 TEMPERATURE If alarm persists contact
Table continued…


6 CRITICAL MALFUNC- critical 6016 BUSS POWER If alarm persists contact
6 CRITICAL MALFUNC- critical 9998 UNKNOWN CAUSE Dispatch Application
7 MAJOR MALFUNC- major 17 POWER SUPPLY If alarm persists contact
7 MAJOR MALFUNC- major 18 FAN FAULT If alarm persists contact
7 MAJOR MALFUNC- major 7017 POWER SUPPLY If alarm persists contact
7 MAJOR MALFUNC- major 7018 FAN FAULT If alarm persists contact
7 MAJOR MALFUNC- major 9998 UNKNOWN CAUSE If alarm persists contact
8 MINOR MALFUNC- minor 18 FAN FAULT If alarm persists contact
8 MINOR MALFUNC- minor 3 CLIENT FAULT Reboot the Console
TION (3) PC, check if the data-
base synchronization
was successful.
8 MINOR MALFUNC- minor 8003 CLIENT FAULT Reboot the Console
TION (3) PC, check if the data-
base synchronization
was successful.
8 MINOR MALFUNC- minor 8018 FAN FAULT If alarm persists contact
8 MINOR MALFUNC- minor 9998 UNKNOWN CAUSE If alarm persists contact
9 WARNING MAL- warn- 19 MONITOR LINK If alarm persists contact
FUNCTION ing (4) FAULT service personnel.
9 WARNING MAL- warn- 9019 MONITOR LINK If alarm persists contact
FUNCTION ing (4) FAULT service personnel.
9 WARNING MAL- warn- 9998 UNKNOWN CAUSE If alarm persists contact
Table continued…


vestigate.
vestigate.
vestigate.
state.
DispatchVoiceCard
DispatchVoiceCard object.
Table 79: Explanation of the Source Content of an Alarm Message for the DispatchVoiceCard
Object

DispatchVoiceCard.a.b.c a = Console Site ID, b = Application Plat- DispatchVoiceCard.1001.1.1 is
form ID, c = Voice Card ID equal to Voice Card 1 on Applica-
tion Platform 1 on Console Site
1001
The following table lists the state and cause texts for the DispatchVoiceCard object.

Table 80: State/Cause Text for the DispatchVoiceCard Object

gate.
gate.
gate.
quested.
Table continued…


vestigate.
quested.
vestigate.
quested.
(6) quired.
(6) quired.
user initiated.
has no knowledge of
companying status
Table continued…


managed object is
known and managed.
replace the module
hardware.
replace the module
hardware.
6 CRITICAL MALFUNC- critical 9998 UNKNOWN CAUSE Possible hardware
replace the module
hardware.
vestigate.
vestigate.
vestigate.
most likely only a tim-


nate ing related transitory
(5) state. Investigate final
state.
GasFan
GasFan object.
Table 81: Explanation of the Source Content of an Alarm Message for the GasFan Object

GasFan_2.1 n/a Fixed name
The following table lists the state and cause texts for the GasFan object.
Table 82: State/Cause Text for the GasFan Object

2 ONLINE nor- 2001 NO REASON This is normal system
(6) quired.
2 ONLINE nor- 2002 NO PROBLEM This is normal system
(6) quired.
3 OFFLINE major 3002 NO PROBLEM The component is off-
(2) line but not reporting a
problem. No action re-
quired.
4 INITIALIZATION minor 4002 NO PROBLEM State transition. Please
(3) wait for final state. No
action required.
5 FAILURE critical 5021 A COOLING FAN Log in as sysadmin and
(1) HAS COMPLETELY check the component
FAILED OR states. This is a possi-
SLOWED DOWN ble hardware failure.
5 FAILURE critical 5048 POWER SUPPLY Log in as sysadmin and
(1) FAILURE check the component
states. This is a possi-
ble hardware failure.
5 FAILURE critical 5078 TEMP THRESHOLD Log in as sysadmin and
(1) VIOLATION check the component
Table continued…


5 FAILURE critical 5082 HARD DISK TEST Log in as sysadmin and
(1) FAILED check the component
ble hardware failure or
an indication of immi-
nent failure. Notify
spect the Hard Disk
and replace faulty hard-
ware.
5 FAILURE critical 5098 VOLTAGE THRESH- Log in as sysadmin and
(1) OLD VIOLATION check the component
5 FAILURE critical 5153 UNKNOWN ERROR Log in as sysadmin and
(1) check the component
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
Table continued…


vestigate.
GasHardDisk
GasHardDisk object.
Table 83: Explanation of the Source Content of an Alarm Message for the GasHardDisk Object

GasHardDisk_2.1 n/a Fixed name
The following table lists the state and cause texts for the GasHardDisk object.
Table 84: State/Cause Text for the GasHardDisk Object

(6) quired.
(6) quired.
quired.
action required.
Table continued…


spect the Hard Disk
ware.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
Table continued…


vestigate.
vestigate.
GasPowerSupply
GasPowerSupply object.
Table 85: Explanation of the Source Content of an Alarm Message for the GasPowerSupply Object

GasPowerSupply_2.1 n/a Fixed name
The following table lists the state and cause texts for the GasPowerSupply object.
Table 86: State/Cause Text for the GasPowerSupply Object

(6) quired.
(6) quired.
quired.
action required.
Table continued…


spect the Hard Disk
ware.
has no knowledge of
companying status
managed object is
known and managed.
Table continued…


vestigate.
vestigate.
vestigate.
GasTemperature
GasTemperature object.
Table 87: Explanation of the Source Content of an Alarm Message for the GasTemperature Object

GasTemperature_2.1 n/a Fixed name
The following table lists the state and cause texts for the GasTemperature object.
Table 88: State/Cause Text for the GasTemperature Object

(6) quired.
(6) quired.
quired.
Table continued…


action required.
spect the Hard Disk
ware.
5 FAILURE critical 5098 TEMPERATURE Log in as sysadmin and
(1) OUT OF NOMINAL check the component
RANGE (HIGH/ states. This is a possi-
LOW) ble hardware failure.
has no knowledge of
companying status
managed object is
known and managed.
Table continued…


vestigate.
vestigate.
vestigate.
GasVoltage
GasVoltage object.
Table 89: Explanation of the Source Content of an Alarm Message for the GasVoltage Object

GasVoltage_2.1 n/a Fixed name
The following table lists the state and cause texts for the GasVoltage object.
Table 90: State/Cause Text for the GasVoltage Object

(6) quired.
Table continued…


(6) quired.
quired.
action required.
5 FAILURE critical 5078 VOLTAGE OUT OF Log in as sysadmin and
(1) NOMINAL RANGE check the component
(HIGH/LOW) states. This is a possi-
spect the Hard Disk
ware.
5 FAILURE critical 5098 TEMPERATURE Log in as sysadmin and
(1) OUT OF NOMINAL check the component
RANGE (HIGH/ states. This is a possi-
LOW) ble hardware failure.
has no knowledge of
Table continued…


companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.
GpioModule
GpioModule object.
Table 91: Explanation of the Source Content of an Alarm Message for the GpioModule Object

GpioModule-a-b a = Application Platform ID, GpioModule–1–1 is equal to GPIOM 1
b = GPIOM ID on Application Platform 1
The following table lists the state and cause texts for the GpioModule object.

Table 92: State/Cause Text for the GpioModule Object

gate.
gate.
gate.
quested.
Table continued…


vestigate.
quested.
vestigate.
quested.
(6) quired.
(6) quired.
user initiated.
has no knowledge of
companying status
Table continued…


managed object is
known and managed.
6 CRITICAL MALFUNC- critical 5 MODULE FAULT Check GPIOM connec-
TION (1) tion to the Console PC
6 CRITICAL MALFUNC- critical 6005 MODULE FAULT Check GPIOM connec-
6 CRITICAL MALFUNC- critical 9998 UNKNOWN CAUSE Check GPIOM connec-
vestigate.
vestigate.
vestigate.
state.
Mtig
The following table contains an explanation of source information displayed in the Web NM, Status page for the Mtig
object.

Table 93: Explanation of the Source Content of an Alarm Message for the Mtig Object

The alias assigned to the Mtig ob- n/a Since this is an object to which an alias
ject is assigned the source information is a
user determined setting
The following table lists the state and cause text for the Mtig object.
Table 94: State/Cause Text for the Mtig Object

1 ACTIVE nor- 1000 MTIG STARTED This is normal system
mal AND RUNNING. operation. No action re-
(6) quired.
1 ACTIVE nor- 2000 MTIG STARTED This is normal system
mal AND RUNNING. operation. No action re-
(6) quired.
2 UNINITIALIZED warn- 1001 MTIG INITIALIZ- Transitional state. No
ing (4) ING. action required.
2 UNINITIALIZED warn- 3001 MTIG INITIALIZ- Transitional state. No
ing (4) ING. action required.
3 DISABLED major 1002 MTIG SERVICE IN- Possible E1 card hard-
(2) ACTIVE. FAULTY ware failure. Contact
E1 CARD. service personnel.
3 DISABLED major 1003 MTIG SERVICE IN- Possibility of incorrect
(2) ACTIVE. FAILED MTIG installation or
TO LOAD DSP faulty voice card. Re-
SOFTWARE boot MTIG. If problem
persists contact service
gate.
3 DISABLED major 4002 MTIG SERVICE IN- Possible E1 card hard-
(2) ACTIVE. FAULTY ware failure. Contact
E1 CARD. service personnel.
3 DISABLED major 4003 MTIG SERVICE IN- Possibility of incorrect
(2) ACTIVE. FAILED MTIG installation or
TO LOAD DSP faulty voice card. Re-
SOFTWARE boot MTIG. If problem
gate.
3 DISABLED major 4004 MTIG SERVICE IS MTIG service didnt
(2) NOT ACTIVE. UN- start properly. Recon-
ABLE TO START figure MTIG.
MTIG SERVICE
4 EXTERNAL ERROR warn- 5005 UNSTABLE PABX Check the physical link
ing (4) LINK DETECTED, with PABX.
Table continued…


MAY BE UNAVAIL-
ABLE.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.
state.
MtigPort
MtigPort object.

Table 95: Explanation of the Source Content of an Alarm Message for the MtigPort Object

MtigPort_a.b a = MTIG ID, b = Port ID MtigPort_1.1 is equal to Port 1on
MTIG 1
The following table lists the state and cause text for the MtigPort object.
Table 96: State/Cause Text for the MtigPort Object

gate.
2 DOWN warn- 2002 MTIG LINK DOWN Investigate network
ing (4) connectivity to MTIG.
2 DOWN warn- 2003 LAPD LINK DOWN Possible E1 card hard-
ing (4) ware failure or faulty
PABX configuration .
nel to investigate.
2 DOWN warn- 2004 MTIG TONE GEN- If alarm persists contact
ing (4) ERATOR FAILURE service personnel.
3 UP nor- 3001 NO REASON This is normal system
(6) quired.
has no knowledge of
companying status
managed object is
known and managed.
Table continued…


vestigate.
vestigate.
vestigate.
state.
MtsAtccBoardInternals
MtsAtccBoardInternals object.
Table 97: Explanation of the Source Content of an Alarm Message for the MtsAtccBoardInternals
Object

MtsAtccBoardInternals_a.b.1 a = MTS Site ID, b = ATCC MtsAtccBoardInternals_55.2.1 is equal
ID to ATCC Board Internals 2 on MTS
Site 55
The following table lists the state and cause texts for the MtsAtccBoardInternals object.

Table 98: State/Cause Text for the MtsAtccBoardInternals Object

1 UNKNOWN/ major 1001 NO REASON The no reason cause is
UNREACHABLE (2) only sent when the giv-
en component is not
able to identify the rea-
son e.g. after a start up
after a reset. If the state
entered is unreachable/
unknown and it stays
so permanently then
nel for investigating the
network to the site or
on the site. In case of
other states then con-
sider the repair actions
for the alarms which
can lead to the given
state.
1 UNKNOWN/ major 1002 SOME ALARMS Some alarm cases are
UNREACHABLE (2) CLEARED cleared. The new state
reflects if there are still
issues left or not.
1 UNKNOWN/ major 9998 UNKNOWN CAUSE The node is unreacha-
UNREACHABLE (2) ble from the manager.
This should only be a
vestigate network con-
nectivity to the site or
state.
2 NORMAL OPERA- nor- 2001 NO REASON The no reason cause is
TION mal only sent when the giv-
(6) en component is not
after a reset. Accord-
ingly, the repair action
will fully depend on the
state entered. If the
state entered is un-
reachable/ unknown
and it stays so perma-
Table continued…


nently then contact
service personnel for
investigating the net-
work to the site or on
the site. In case of other
states then consider the
repair actions for the
alarms which can lead
to the given state.
2 NORMAL OPERA- nor- 2002 SOME ALARMS Some alarm cases are
TION mal CLEARED cleared. The new state
(6) reflects if there are still
issues left or not.
2 NORMAL OPERA- nor- 9998 UNKNOWN CAUSE If alarm persists contact
TION mal service personnel.
(6)
4 MODULE FAULT major 4001 NO REASON The no reason cause is
(2) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
4 MODULE FAULT major 4002 SOME ALARMS Some alarm cases are
(2) CLEARED cleared. The new state
issues left or not.
4 MODULE FAULT major 4003 MODULE FAULT Service personnel
(2) should immediately be
contacted to rectify the
module problem or re-
place the module on the
site.
4 MODULE FAULT major 9998 UNKNOWN CAUSE If alarm persists contact
(2) service personnel.
Table continued…


5 MODULE PROBLEM minor 5001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
5 MODULE PROBLEM minor 5002 SOME ALARMS Some alarm cases are
issues left or not.
5 MODULE PROBLEM minor 5004 MODULE PROBLEM Service personnel
(3) should be contacted to
rectify the module
module on the site.
5 MODULE PROBLEM minor 9998 UNKNOWN CAUSE If alarm persists contact
has no knowledge of
companying status
managed object is
known and managed.
Table continued…


(SNMP NOSUCH- temporary state other-
NAME) wise service personnel
vestigate.
vestigate.
vestigate.
state.
MtsAtccSignalMeasurements
The following table contains an explanation of source information displayed in the Web NM, Status page for
theMtsAtccSignalMeasurements object.
MtsAtccSignalMeasurements Object

MtsAtccSignalMeasurements_a.b. a = MTS Site ID, b = ATCC MtsAtccSignalMeasurements_55.1.1 is
1 ID equal to ATCC Signal Measurements 1
on MTS Site 55
The following table lists the state and cause texts for the MtsAtccSignalMeasurements object.
Table 100: State/Cause Text for the MtsAtccSignal Object

en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
issues left or not.
state.
100 SIGNAL critical 100001 NO REASON The no reason cause is
FAULTS:VSWR, (1) only sent when the giv-
POWL en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
100 SIGNAL critical 100002 SOME ALARMS Some alarm cases are
FAULTS:VSWR, (1) CLEARED cleared. The new state
POWL reflects if there are still
issues left or not.
100 SIGNAL critical 100005 FORWARD POWER Immediately contact
FAULTS:VSWR, (1) LEVEL FAULT the service personnel to
POWL correct the antenna,
correct the output ca-
bling, correct the out-
put terminations, recti-
fy the module problem
or replace the module.
100 SIGNAL critical 100007 VOLTAGE STAND- Immediately contact
FAULTS:VSWR, (1) ING WAVE RATION the service personnel to
POWL FAULT correct the antenna,
100 SIGNAL critical 9998 UNKNOWN CAUSE If the state stays so per-
FAULTS:VSWR, (1) manently contact serv-
POWL ice personnel for inves-
tigation the network to
the site or on the site.
In case of other states
then consider the repair
actions for the alarms
which can lead to the
given state.
FAULTS:POWL, (1) only sent when the giv-
(VSWR) en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
FAULTS:POWL, (1) CLEARED cleared. The new state
(VSWR) reflects if there are still
issues left or not.
101 SIGNAL critical 101005 FORWARD POWER Contact the service per-
FAULTS:POWL, (1) LEVEL FAULT sonnel to correct the
(VSWR) antenna, correct the
output cabling, correct
the output cabling ter-
minations, rectify the
place the module.
101 SIGNAL critical 101008 VOLTAGE STAND- Contact the service per-
FAULTS:POWL, (1) ING WAVE RATION sonnel to correct the
(VSWR) PROBLEM antenna, correct the
place the module.
101 SIGNAL critical 9998 UNKNOWN CAUSE Contact the service per-
FAULTS:POWL, (1) sonnel to correct the
place the module.
(POWL) en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
(POWL) reflects if there are still
issues left or not.
FAULTS:VSWR, (1) LEVEL PROBLEM sonnel to correct the
(POWL) antenna, correct the
place the module.
(POWL) FAULT correct the antenna,
102 SIGNAL critical 9998 UNKNOWN CAUSE If the state stays so per-
FAULTS:VSWR, (1) manently contact serv-
(POWL) ice personnel for inves-
given state.
103 SIGNAL minor 103001 NO REASON The no reason cause is
PROB.:VSWR, POWL (3) only sent when the giv-
en component is not
reachable/ unknown
Table continued…


nently then contact
to the given state.
103 SIGNAL minor 103002 SOME ALARMS Some alarm cases are
PROB.:VSWR, POWL (3) CLEARED cleared. The new state
issues left or not.
103 SIGNAL minor 103006 FORWARD POWER Contact the service per-
PROB.:VSWR, POWL (3) LEVEL PROBLEM sonnel to correct the
antenna, correct the
place the module.
103 SIGNAL minor 103008 VOLTAGE STAND- Contact the service per-
PROB.:VSWR, POWL (3) ING WAVE RATION sonnel to correct the
PROBLEM antenna, correct the
place the module.
103 SIGNAL minor 9998 UNKNOWN CAUSE If alarm persists contact
PROB.:VSWR, POWL (3) service personnel.
reachable/ unknown
nently then contact
Table continued…


to the given state.
issues left or not.
2 NORMAL OPERA- nor- 9998 UNKNOWN CAUSE If alarm persists contact
TION mal service personnel.
(6)
3 FORWARD POWER critical 3001 NO REASON The no reason cause is
LEVEL FAULT (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
3 FORWARD POWER critical 3002 SOME ALARMS Some alarm cases are
LEVEL FAULT (1) CLEARED cleared. The new state
issues left or not.
3 FORWARD POWER critical 3005 FORWARD POWER Immediately contact
LEVEL FAULT (1) LEVEL FAULT the service personnel to
correct the antenna,
3 FORWARD POWER critical 9998 UNKNOWN CAUSE If the state stays so per-
LEVEL FAULT (1) manently contact serv-
ice personnel for inves-
Table continued…


given state.
4 FORWARD POWER minor 4001 NO REASON The no reason cause is
LEVEL PROB. (3) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
4 FORWARD POWER minor 4002 SOME ALARMS Some alarm cases are
LEVEL PROB. (3) CLEARED cleared. The new state
issues left or not.
4 FORWARD POWER minor 4006 FORWARD POWER Contact the service per-
LEVEL PROB. (3) LEVEL PROBLEM sonnel to correct the
place the module.
4 FORWARD POWER minor 9998 UNKNOWN CAUSE If alarm persists contact
LEVEL PROB. (3) service personnel.
5 VSWR STANDING critical 5001 NO REASON The no reason cause is
WAVE FAULT (1) only sent when the giv-
en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
5 VSWR STANDING critical 5002 SOME ALARMS Some alarm cases are
WAVE FAULT (1) CLEARED cleared. The new state
issues left or not.
5 VSWR STANDING critical 5007 VOLTAGE STAND- Immediately contact
WAVE FAULT (1) ING WAVE RATION the service personnel to
FAULT correct the antenna,
5 VSWR STANDING critical 9998 UNKNOWN CAUSE If the state stays so per-
WAVE FAULT (1) manently contact serv-
ice personnel for inves-
given state.
has no knowledge of
companying status
managed object is
known and managed.
6 VSWR STANDING minor 6001 NO REASON The no reason cause is
WAVE PROB. (3) only sent when the giv-
Table continued…


en component is not
reachable/ unknown
nently then contact
to the given state.
6 VSWR STANDING minor 6002 SOME ALARMS Some alarm cases are
WAVE PROB. (3) CLEARED cleared. The new state
issues left or not.
6 VSWR STANDING minor 6008 VOLTAGE STAND- Contact the service per-
WAVE PROB. (3) ING WAVE RATION sonnel to correct the
place the module.
6 VSWR STANDING minor 9998 UNKNOWN CAUSE If alarm persists contact
WAVE PROB. (3) service personnel.
vestigate.
vestigate.
Table continued…


vestigate.
state.
MtsBaseRadio
MtsBaseRadio object.
Table 101: Explanation of the Source Content of an Alarm Message for the MtsBaseRadio Object

MtsBaseRadio_a.b a = MTS Site ID, b = MTS MtsBaseRadio_55.2 is equal to MTS
Base Radio ID Base Radio 2 on MTS Site 55
The following table lists the state and cause texts for the MtsBaseRadio object.
Table 102: State/Cause Text for the MtsBaseRadio Object

1 UNKNOWN critical 1001 INITIALIZED The BR has reset. It is
(1) initialized and in the
process of configuring
itself for operation.
This is a normal mode
of operation but should
be a transitory state on-
ly.
1 UNKNOWN critical 1022 BR NOT RESPOND- The device is reported
(1) ING unknown with cause
BR not responding.
Possible connection or
device failure. Try
manually resetting the
BR or contact service
personnel.
10 STANDBY ACTIVE major 10017 BR4 FAILED Base Radio 4 has failed
BR4 (2) and the Standby Base
Table continued…


Radio has been auto-
matically reconfigured
to replace it. Investi-
gate BR4 failure.
10 STANDBY ACTIVE major 9998 UNKNOWN CAUSE If alarm persists contact
BR4 (2) service personnel.
to replace it.
to replace it.
to replace it.
13 STANDBY ACTIVE major 13021 ENCRYPTION SUB- BR has suffered an en-
BR7 (2) SYSTEM FAILURE cryption subsystem
failure.
to replace it.
to replace it.
Table continued…


16 STANDBY ACTIVE major 16028 BR10 FAILED Base Radio 10 has
BR10 (2) failed and the Standby
Base Radio has been
automatically reconfig-
ured to replace it.
Base Radio has been
ured to replace it.
Base Radio has been
ured to replace it.
Base Radio has been
ured to replace it.
2 ENABLED nor- 2003 KEYED_PM The Base Radio is
mal keyed and ready to ac-
(6) cept channel requests.
This is the normal op-
erating mode of the
Base Radio. No action
required.
quired.
2 ENABLED nor- 2010 UNLOCKED An Unlock (key) re-
mal quest has been received
(6) by the base radio. The
base radio has been set
into the enabled state.
This was initiated by a
user request or as part
of the base radios nor-
Table continued…


mal start-up sequence.
ly.
2 ENABLED nor- 2013 STANDBY IN USE Base Radio has been
mal replaced by the Stand-
(6) by Base Radio.
2 ENABLED nor- 2024 KEYED_QAM_25 The Base Radio is
erating mode of the
required.
2 ENABLED nor- 2025 KEYED_QAM_50 The Base Radio is
erating mode of the
required.
2 ENABLED nor- 2026 KEYED_QAM_50_F The Base Radio is
mal R keyed and ready to ac-
erating mode of the
required.
user initiated.
Base Radio has been
ured to replace it.
Base Radio has been
ured to replace it.
Table continued…


Base Radio has been
ured to replace it.
3 DISABLED critical 3004 LOCKED A lock (dekey) request
(1) has been received by
the Base Radio. The
Base Radio has been
set into the Disabled
state by a request from
the Site Controller or
Network Manager. The
MTS state and the
states of all other MTS
components should be
checked.
3 DISABLED critical 3005 LOCK CONDITION An internal Base Radio
(1) (BR) failure condition
has resulted in a Lock
action which has disa-
bled the BR to prevent
damage to itself and
other MTS compo-
nents. The status of the
BR FRUs should be
checked to determine
the root of the problem.
If the problem persists
Motorola service per-
sonnel should be con-
tacted to rectify the
problem.
3 DISABLED critical 3006 SC LINK FAILURE The Base Radios con-
(1) trol link to Site Con-
troller has failed. Ether-
net cabling and termi-
nation should be
checked. If problem
persists, service person-
nel should be contact-
ed.
3 DISABLED critical 3007 DISABLE CONDI- The Base Radio (BR)
(1) TION has detected a failure
condition resulting in a
disable action to pre-
vent damage to itself
Table continued…


and other MTS compo-
nents. Investigate ac-
companying messages
or the status of the BR
FRUs to determine the
root cause of the prob-
lem or contact service
personnel to investigate
and rectify the prob-
lem.
3 DISABLED critical 3008 DISABLE A Base Radio (BR)
(1) failure resulted in the
BR disabling itself to
prevent damage to it-
self and other MTS
components. Investi-
gate accompanying
messages or contact
vestigate and rectify the
problem.
3 DISABLED critical 3009 USER REQUESTED State change caused by
tion.
3 DISABLED critical 3021 ENCRYPTION SUB- BR has detected an en-
(1) SYSTEM FAILURE cryption subsystem
failure. Possible key
mismatch. Check Site
has been keyed with ki
and receipts loaded
back in AuC. Contact
service personnel to
check status from AuC
and from BTS. From
AuC determine if site is
enabled for key updates
and ki is current. From
BTS examine status sec
and status keys. In case
that errors still persist,
reset the BR or contact
Motorola support.
sonnel.
Table continued…


4 CONFIGURING warn- 4001 INITIALIZED The BR has reset. It is
ing (4) initialized and in the
process of configuring
itself for operation.
ly.
4 CONFIGURING warn- 4002 ENABLED Configuration data has
ing (4) been received from the
Site Controller, all Dis-
able Conditions are
clear and the Base Ra-
dio is preparing itself
for operation. This is a
normal mode of opera-
tion but should be a
transitory state only.
4 CONFIGURING warn- 9998 UNKNOWN CAUSE BR is configuring.
ing (4) Transitional state.
Check final state.
5 STANDBY minor 5009 USER REQUESTED State change caused by
tion. No action re-
quired.
5 STANDBY minor 5012 STANDBY BR Base Radio is config-
(3) ured as a Standby Base
Radio from TESS, has
completed initialization
and is help in Locked-
Enable-Idle state. No
other Base Radio has
failed. If replacement
for a failed BR is re-
quired (any other BR
fails) then the Standby
BR will be unlocked.
Otherwise, the Standby
BR will be kept in L-E-
I state.
5 STANDBY minor 9998 UNKNOWN CAUSE Base Radio is config-
(3) ured as a Standby Base
Radio, cause of state
change is unknown but
may be transitory. In-
vestigate accompany-
ing alarms or final
state. No action re-
Table continued…


ed.
has no knowledge of
companying status
managed object is
known and managed.
6 EXTRA CAPACITY nor- 6009 USER REQUESTED State change caused by
quired.
6 EXTRA CAPACITY nor- 9998 UNKNOWN CAUSE If alarm persists contact
mal service personnel.
(6)
gate BR 1 failure.
gate BR2 failure.
gate BR3 failure.
Table continued…


vestigate.
vestigate.
vestigate.
state.
MtsBrBoardInternals
MtsBrBoardInternals object.
Table 103: Explanation of the Source Content of an Alarm Message for the MtsBrBoardInternals
Object

MtsBrBoardInternals_a.b.1 a = MTS Site ID, b = MTS MtsBrBoardInternals_55.2.1 is equal to
Base Radio ID MTS Base Radio Board Internals on
MTS Base Radio 2 on MTS Site 55
The following table lists the state and cause texts for the MtsBrBoardInternals object.
Table 104: State/Cause Text for the MtsBrBoardInternals Object

1 UNKNOWN/ critical 1001 NO REASON The no reason cause is
Table continued…


en component is not
reachable/ unknown
nently then contact
to the given state.
1 UNKNOWN/ critical 1002 SOME ALARMS Some alarm cases are
issues left or not.
1 UNKNOWN/ critical 9998 UNKNOWN CAUSE The node is unreacha-
state.
100 MODULE FAULT, critical 100001 NO REASON The no reason cause is
HEAT FAULT (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
100 MODULE FAULT, critical 100002 SOME ALARMS Some alarm cases are
HEAT FAULT (1) CLEARED cleared. The new state
issues left or not.
100 MODULE FAULT, critical 100003 MODULE FAULT Service personnel
HEAT FAULT (1) should immediately be
site.
100 MODULE FAULT, critical 100005 POWER FAULT Check the status of the
HEAT FAULT (1) PSU to see if it is caus-
ing the problem. The
PSUs supply the BRs
and SCs as follows:
PSU1: SC, BR1, BR2;
PSU2: (SSC), BR3,
BR4; For expanded
sites: PSU3: X-hub1,
BR5, BR6; PSU4: X-
hub2, BR7, BR8. If
there are no PSU prob-
lems service personnel
should immediately be
module problem, cor-
rect the power cables or
replace the module on
the site.
100 MODULE FAULT, critical 100007 CONFIGURATION Service personnel
HEAT FAULT (1) FAULT should immediately be
contacted to correct the
configuration problem
in this module
100 MODULE FAULT, critical 100009 HIGH TEMPERA- Check the status of the
HEAT FAULT (1) TURE ALARM fans in the PSU object.
If there are no fan prob-
problem by investigat-
Table continued…


ing the temperatures on
other boards and then
repair the heating/cool-
ing on the site or re-
place this module if it
is the only one with the
problem.
100 MODULE FAULT, critical 9998 UNKNOWN CAUSE Check the status of the
HEAT FAULT (1) fans in the PSU object.
problem.
101 MODULE FAULT, critical 101001 NO REASON The no reason cause is
HEAT PROB (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
101 MODULE FAULT, critical 101002 SOME ALARMS Some alarm cases are
HEAT PROB (1) CLEARED cleared. The new state
issues left or not.
101 MODULE FAULT, critical 101003 MODULE FAULT Service personnel
HEAT PROB (1) should immediately be
Table continued…


site.
101 MODULE FAULT, critical 101005 POWER FAULT Check the status of the
HEAT PROB (1) PSU to see if it is caus-
PSUs supply the BRs
and SCs as follows:
PSU1: SC, BR1, BR2;
PSU2: (SSC), BR3,
BR4; For expanded
BR5, BR6; PSU4: X-
hub2, BR7, BR8. If
the site.
101 MODULE FAULT, critical 101007 CONFIGURATION Service personnel
HEAT PROB (1) FAULT should immediately be
in this module
101 MODULE FAULT, critical 101010 HIGH TEMPERA- Check the status of the
HEAT PROB (1) TURE WARNING fans in the PSU object.
should be contacted to
rectify the problem by
investigating the tem-
peratures on other
boards and then repair
the heating/cooling on
the site or replace this
module if it is the only
one with the problem.
101 MODULE FAULT, critical 9998 UNKNOWN CAUSE Check the status of the
HEAT PROB (1) fans in the PSU object.
Table continued…


problem.
102 HEAT FAULT, MOD- critical 102001 NO REASON The no reason cause is
ULE PROB (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
102 HEAT FAULT, MOD- critical 102002 SOME ALARMS Some alarm cases are
ULE PROB (1) CLEARED cleared. The new state
issues left or not.
102 HEAT FAULT, MOD- critical 102004 MODULE PROBLEM Service personnel
ULE PROB (1) should be contacted to
rectify the module
module on the site.
102 HEAT FAULT, MOD- critical 102006 POWER PROBLEM Check the status of the
ULE PROB (1) PSU to see if it is caus-
PSUs supply the BRs
and SCs as follows:
PSU1: SC, BR1, BR2;
PSU2: (SSC), BR3,
BR4; For expanded
BR5, BR6; PSU4: X-
hub2, BR7, BR8. If
Table continued…


the site.
102 HEAT FAULT, MOD- critical 102008 CONFIGURATION Service personnel
ULE PROB (1) PROBLEM should be contacted to
correct the configura-
tion problem in this
module.
102 HEAT FAULT, MOD- critical 102009 HIGH TEMPERA- Check the status of the
ULE PROB (1) TURE ALARM fans in the PSU object.
problem.
102 HEAT FAULT, MOD- critical 9998 UNKNOWN CAUSE Check the status of the
ULE PROB (1) fans in the PSU object.
problem.
103 MODULE, HEAT minor 103001 NO REASON The no reason cause is
PROBLEMS (3) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
103 MODULE, HEAT minor 103002 SOME ALARMS Some alarm cases are
PROBLEMS (3) CLEARED cleared. The new state
issues left or not.
103 MODULE, HEAT minor 103004 MODULE PROBLEM Service personnel
PROBLEMS (3) should be contacted to
rectify the module
module on the site.
103 MODULE, HEAT minor 103006 POWER PROBLEM Check the status of the
PROBLEMS (3) PSU to see if it is caus-
PSUs supply the BRs
and SCs as follows:
PSU1: SC, BR1, BR2;
PSU2: (SSC), BR3,
BR4; For expanded
BR5, BR6; PSU4: X-
hub2, BR7, BR8. If
the site.
103 MODULE, HEAT minor 103008 CONFIGURATION Service personnel
PROBLEMS (3) PROBLEM should be contacted to
module.
103 MODULE, HEAT minor 103010 HIGH TEMPERA- Check the status of the
PROBLEMS (3) TURE WARNING fans in the PSU object.
peratures on other
Table continued…


103 MODULE, HEAT minor 9998 UNKNOWN CAUSE If alarm persists contact
PROBLEMS (3) service personnel.
reachable/ unknown
nently then contact
to the given state.
issues left or not.
2 NORMAL OPERA- nor- 9998 UNKNOWN CAUSE This is normal system
TION mal operation. No action re-
(6) quired.
3 MODULE FAULT critical 3001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
3 MODULE FAULT critical 3002 SOME ALARMS Some alarm cases are
issues left or not.
3 MODULE FAULT critical 3003 MODULE FAULT Service personnel
site.
3 MODULE FAULT critical 3005 POWER FAULT Check the status of the
(1) PSU to see if it is caus-
PSUs supply the BRs
and SCs as follows:
PSU1: SC, BR1, BR2;
PSU2: (SSC), BR3,
BR4; For expanded
BR5, BR6; PSU4: X-
hub2, BR7, BR8. If
the site.
3 MODULE FAULT critical 3007 CONFIGURATION Service personnel
(1) FAULT should immediately be
in this module
3 MODULE FAULT critical 3011 DEKEYED FROM Service personnel
(1) MMI ALARM should immediately be
site.
3 MODULE FAULT critical 9998 UNKNOWN CAUSE Check the status of the
PSUs supply the BRs
Table continued…


and SCs as follows:
PSU1: SC, BR1, BR2;
PSU2: (SSC), BR3,
BR4; For expanded
BR5, BR6; PSU4: X-
hub2, BR7, BR8. If
the site.
en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
rectify the module
module on the site.
4 MODULE PROBLEM minor 4006 POWER PROBLEM Check the status of the
PSUs supply the BRs
and SCs as follows:
Table continued…


PSU1: SC, BR1, BR2;
PSU2: (SSC), BR3,
BR4; For expanded
BR5, BR6; PSU4: X-
hub2, BR7, BR8. If
the site.
4 MODULE PROBLEM minor 4008 CONFIGURATION Service personnel
(3) PROBLEM should be contacted to
module.
5 HEAT FAULT critical 5001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
5 HEAT FAULT critical 5002 SOME ALARMS Some alarm cases are
issues left or not.
5 HEAT FAULT critical 5009 HIGH TEMPERA- Check the status of the
(1) TURE ALARM fans in the PSU object.
Table continued…


problem.
5 HEAT FAULT critical 9998 UNKNOWN CAUSE Check the status of the
(1) fans in the PSU object.
problem.
has no knowledge of
companying status
managed object is
known and managed.
6 HEAT PROBLEM minor 6001 NO REASON The no reason cause is
en component is not
reachable/ unknown
Table continued…


nently then contact
to the given state.
6 HEAT PROBLEM minor 6002 SOME ALARMS Some alarm cases are
issues left or not.
6 HEAT PROBLEM minor 6010 HIGH TEMPERA- Check the status of the
(3) TURE WARNING fans in the PSU object.
peratures on other
6 HEAT PROBLEM minor 9998 UNKNOWN CAUSE Check the status of the
(3) fans in the PSU object.
peratures on other
vestigate.
Table continued…


vestigate.
vestigate.
state.
MtsBrDataPorts
MtsBrDataPorts object.
Table 105: Explanation of the Source Content of an Alarm Message for the MtsBrDataPorts Object

MtsBrDataPorts_a.b.1 a = MTS Site ID, b = MTS MtsBrDataPorts_55.2.1 is equal to
Base Radio ID MTS Base Radio Port/Link on MTS
Base Radio 2 on MTS Site 55
The following table lists the state and cause texts for the MtsBrDataPorts object.
Table 106: State/Cause Text for the MtsBrDataPorts Object

1 UNKNOWN critical 1001 NO REASON The no reason cause is
en component is not
reachable/ unknown
Table continued…


nently then contact
to the given state.
1 UNKNOWN critical 1002 SOME ALARMS Some alarm cases are
issues left or not.
1 UNKNOWN critical 9998 UNKNOWN CAUSE Alarm state from object
(1) was unknown and most
node to manager or
nel to investigate.
100 LAN FAULT: ETHER, critical 100001 NO REASON The no reason cause is
REF (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
100 LAN FAULT: ETHER, critical 100002 SOME ALARMS Some alarm cases are
REF (1) CLEARED cleared. The new state
Table continued…


issues left or not.
100 LAN FAULT: ETHER, critical 100003 ETHERNET PORT Contact the service per-
REF (1) FAULT sonnel to check and
correct cables and ter-
minations or eventually
repair/replace this mod-
ule or the site controller
ports.
100 LAN FAULT: ETHER, critical 100004 REFERENCE FAULT Collect information
REF (1) about the status of the
site reference. Then
contact the service per-
sonnel to check and
module.
100 LAN FAULT: ETHER, critical 9998 UNKNOWN CAUSE Possible transitory
REF (1) state. Investigate final
state - if state entered is
remains in a failure
condition or unreacha-
ble/ unknown contact
vestigate site reference
status, cables and ter-
minations or possible
node repair/replace-
ment.
101 LAN FAULT: critical 101001 NO REASON The no reason cause is
ETHER,REF,LINK (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
101 LAN FAULT: critical 101002 SOME ALARMS Some alarm cases are
ETHER,REF,LINK (1) CLEARED cleared. The new state
issues left or not.
101 LAN FAULT: critical 101003 ETHERNET PORT Contact the service per-
ETHER,REF,LINK (1) FAULT sonnel to check and
ports.
101 LAN FAULT: critical 101004 REFERENCE FAULT Collect information
ETHER,REF,LINK (1) about the status of the
sonnel to check and
module.
101 LAN FAULT: critical 101005 LINK FAULT Collect information
ETHER,REF,LINK (1) about the status of
Ethernet ports and the
links from the site con-
troller to the other base
radios. Then contact
the service personnel to
check and correct ca-
bles and terminations
or eventually repair/
replace this module or
the site controller mod-
ule.
101 LAN FAULT: critical 9998 UNKNOWN CAUSE Possible transitory
ETHER,REF,LINK (1) state. Investigate final
ment.
Table continued…


102 LAN FAULT: ETHER, critical 102001 NO REASON The no reason cause is
LINK (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
102 LAN FAULT: ETHER, critical 102002 SOME ALARMS Some alarm cases are
LINK (1) CLEARED cleared. The new state
issues left or not.
102 LAN FAULT: ETHER, critical 102003 ETHERNET PORT Contact the service per-
LINK (1) FAULT sonnel to check and
ports.
102 LAN FAULT: ETHER, critical 102005 LINK FAULT Collect information
LINK (1) about the status of
ule.
102 LAN FAULT: ETHER, critical 9998 UNKNOWN CAUSE If the state entered is
LINK (1) unreachable/ unknown
nently then contact
Table continued…


investigating the node
connectivity. Check in-
formation about the sta-
tus of Ethernet ports
and the links from the
site controller to the
other base radios. Con-
tact the service person-
nel to check and correct
cables and terminations
ule.
103 LAN FAULT: REF, critical 103001 NO REASON The no reason cause is
LINK (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
103 LAN FAULT: REF, critical 103002 SOME ALARMS Some alarm cases are
LINK (1) CLEARED cleared. The new state
issues left or not.
103 LAN FAULT: REF, critical 103004 REFERENCE FAULT Collect information
LINK (1) about the status of the
sonnel to check and
module.
Table continued…


103 LAN FAULT: REF, critical 103005 LINK FAULT Collect information
LINK (1) about the status of
ule.
103 LAN FAULT: REF, critical 9998 UNKNOWN CAUSE Possible transitory
LINK (1) state. Investigate final
ment.
reachable/ unknown
nently then contact
to the given state.
issues left or not.
Table continued…


(6) quired.
3 ETHERNET PORT major 3001 NO REASON The no reason cause is
FAILURE (2) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
3 ETHERNET PORT major 3002 SOME ALARMS Some alarm cases are
FAILURE (2) CLEARED cleared. The new state
issues left or not.
3 ETHERNET PORT major 3003 ETHERNET PORT Contact the service per-
FAILURE (2) FAULT sonnel to check and
ports.
3 ETHERNET PORT major 9998 UNKNOWN CAUSE Collect information
FAILURE (2) about the status of the
Ethernet ports of the
BRs/SSC and then con-
replace this or other
modules on the site.
4 REFERENCE FAIL- critical 4001 NO REASON The no reason or un-
URE (1) known cause is only
sent when the given
component is not able
Table continued…


to identify the reason
e.g. after a start up after
a reset. Accordingly,
the repair action will
fully depend on the
state entered remains in
some failure condition
or unreachable/ un-
known and it stays so
permanently then con-
for investigating con-
nectivity to the node. In
case of other states then
consider the repair ac-
tions for the alarms
given state.
4 REFERENCE FAIL- critical 4002 SOME ALARMS Some alarm cases are
URE (1) CLEARED cleared. The new state
issues left or not.
4 REFERENCE FAIL- critical 4004 REFERENCE FAULT Collect information
URE (1) about the status of the
sonnel to check and
module.
4 REFERENCE FAIL- critical 9998 UNKNOWN CAUSE The no reason or un-
URE (1) known cause is only
sent when the given
fully depend on the
some failure condition
or unreachable/ un-
known and it stays so
permanently then col-
lect information about
the status of the site
Table continued…


reference. check site
reference subsystem
accordingly or contact
replace the module.
5 LINK FAILURE critical 5001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
5 LINK FAILURE critical 5002 SOME ALARMS Some alarm cases are
issues left or not.
5 LINK FAILURE critical 5005 LINK FAULT Base Radio reported a
(1) link failure alarm -
check network connec-
tivity to the BR or from
TSC - collect informa-
tion about the status of
troller to the other BRs.
state. If alarm persists
sonnel to check cables
and terminations or
eventually repair/
Table continued…


ule. In case of other
to the given state.
5 LINK FAILURE critical 9998 UNKNOWN CAUSE Base Radio reported a
(1) link failure alarm -
tivity to the BR or from
TSC - collect informa-
tion about the status of
troller to the other BRs.
state. If alarm persists
sonnel to check cables
and terminations or
eventually repair/
ule. In case of other
to the given state.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
Table continued…


vestigate.
vestigate.
state.
MtsBrReceivePathandInterference
MtsBrReceivePathandInterference object.
MtsBrReceivePathandInterference Object

MtsBrReceivePathandInterfer- a = MTS Site ID, b = MTS MtsBrReceivePathandInterfer-
ence_a.b.1 Base Radio ID ence_55.2.1 is equal to MTS Base Ra-
dio Receive Path on MTS Base Radio
2 on MTS Site 55
The following table lists the state and cause texts for the MtsBrReceivePathandInterference object.
Table 108: State/Cause Text for the MtsBrRecPathAndInterf Object

en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
issues left or not.
node to manager or
nel to investigate.
100 FAULTS:INTER- critical 100001 NO REASON The no reason cause is
FER,SIGNAL (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
100 FAULTS:INTER- critical 100002 SOME ALARMS Some alarm cases are
FER,SIGNAL (1) CLEARED cleared. The new state
issues left or not.
100 FAULTS:INTER- critical 100003 RECEIVER SIGNAL Immediately contact
FER,SIGNAL (1) ALARM the service personnel to
correct the input ca-
bling, correct the input
cable termination, recti-
100 FAULTS:INTER- critical 100006 RF INTERFERENCE If it is believed that this
FER,SIGNAL (1) ALARM (AIH ENA- is a false alarm, disa-
BLED) bling the Automatic In-
terference Handler
(AIH) will immediately
allow the affected
channels to be used ir-
respective of the inter-
ference. Otherwise, im-
mediately contact the
100 FAULTS:INTER- critical 9998 UNKNOWN CAUSE If the state entered is
FER,SIGNAL (1) unreachable/ unknown
nently then contact
investigating the con-
on the site including
the antenna, cabling,
terminations. In case of
state.
101 FAULTS:INTERFER, critical 101001 NO REASON The no reason cause is
(SIGNAL) (1) only sent when the giv-
en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
101 FAULTS:INTERFER, critical 101002 SOME ALARMS Some alarm cases are
(SIGNAL) (1) CLEARED cleared. The new state
issues left or not.
101 FAULTS:INTERFER, critical 101004 RECEIVER SIGNAL Contact the service per-
(SIGNAL) (1) WARNING sonnel to correct the
antenna, correct the ca-
bling, correct the cable
terminations, rectify the
place the module.
101 FAULTS:INTERFER, critical 101006 RF INTERFERENCE If it is believed that this
(SIGNAL) (1) ALARM (AIH ENA- is a false alarm, disa-
terference Handler
allow the affected
101 FAULTS:INTERFER, critical 9998 UNKNOWN CAUSE If the state entered is
(SIGNAL) (1) unreachable/ unknown
nently then contact
Table continued…


state.
102 FAULTS:SIGNAL,(IN- critical 102001 NO REASON The no reason cause is
TERFER) (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
102 FAULTS:SIGNAL,(IN- critical 102002 SOME ALARMS Some alarm cases are
TERFER) (1) CLEARED cleared. The new state
issues left or not.
102 FAULTS:SIGNAL,(IN- critical 102003 RECEIVER SIGNAL Immediately contact
TERFER) (1) ALARM the service personnel to
102 FAULTS:SIGNAL,(IN- critical 102007 RF INTERFERENCE Contact the service per-
TERFER) (1) WARNING (AIH sonnel to correct the
DISABLED) antenna, correct the ca-
Table continued…


place the module.
102 FAULTS:SIGNAL,(IN- critical 9998 UNKNOWN CAUSE If the state entered is
TERFER) (1) unreachable/ unknown
nently then contact
state.
103 PROBL.:SIGNAL,IN- major 103001 NO REASON The no reason cause is
TERFER (2) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
103 PROBL.:SIGNAL,IN- major 103002 SOME ALARMS Some alarm cases are
TERFER (2) CLEARED cleared. The new state
issues left or not.
103 PROBL.:SIGNAL,IN- major 103004 RECEIVER SIGNAL Contact the service per-
TERFER (2) WARNING sonnel to correct the
place the module.
Table continued…


103 PROBL.:SIGNAL,IN- major 103007 RF INTERFERENCE Contact the service per-
TERFER (2) WARNING (AIH sonnel to correct the
place the module.
103 PROBL.:SIGNAL,IN- major 9998 UNKNOWN CAUSE Check the RF environ-
TERFER (2) ment settings. If alarm
personnel.
reachable/ unknown
nently then contact
to the given state.
issues left or not.
2 NORMAL OPERA- nor- 2005 RECEIVER SIGNAL Check the RF environ-
TION mal CLEARED ment settings. Receiver
(6) signal problem / fault
cleared (no further
problems on this issue).
2 NORMAL OPERA- nor- 2008 RF INTERFERENCE Check the RF environ-
TION mal CLEARED ment settings. RF Infer-
(6) ence problem / fault
cleared (no further
problems on this issue).
(6) quired.
Table continued…


3 RECEIVER SIGNAL critical 3001 NO REASON The no reason cause is
FAULT (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
3 RECEIVER SIGNAL critical 3002 SOME ALARMS Some alarm cases are
FAULT (1) CLEARED cleared. The new state
issues left or not.
3 RECEIVER SIGNAL critical 3003 RECEIVER SIGNAL Immediately contact
FAULT (1) ALARM the service personnel to
3 RECEIVER SIGNAL critical 3008 RF INTERFERENCE Check the RF environ-
FAULT (1) CLEARED ment settings. RF Infer-
ence problem / fault
cleared (no further
problems on this issue),
however the receiver
signal fault is still
present. Immediately
sonnel to correct the
antenna, correct the in-
put cabling, correct the
input cable termination,
rectify the module
module.
Table continued…


3 RECEIVER SIGNAL critical 9998 UNKNOWN CAUSE If the state entered is
FAULT (1) unreachable/ unknown
nently then contact
to the given state.
4 RECEIVER SIGNAL major 4001 NO REASON The no reason cause is
PROBLEM (2) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
4 RECEIVER SIGNAL major 4002 SOME ALARMS Some alarm cases are
PROBLEM (2) CLEARED cleared. The new state
issues left or not.
4 RECEIVER SIGNAL major 4004 RECEIVER SIGNAL Contact the service per-
PROBLEM (2) WARNING sonnel to correct the
place the module.
4 RECEIVER SIGNAL major 4008 RF INTERFERENCE Check the RF environ-
PROBLEM (2) CLEARED ment settings. If alarm
personnel.
Table continued…


4 RECEIVER SIGNAL major 9998 UNKNOWN CAUSE Check the RF environ-
PROBLEM (2) ment settings. If alarm
personnel.
5 RF INTERFERENCE critical 5001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
5 RF INTERFERENCE critical 5002 SOME ALARMS Some alarm cases are
issues left or not.
5 RF INTERFERENCE critical 5005 RECEIVER SIGNAL Check the RF environ-
FAULT (1) CLEARED ment settings. If alarm
personnel.
5 RF INTERFERENCE critical 5006 RF INTERFERENCE If it is believed that this
FAULT (1) ALARM (AIH ENA- is a false alarm, disa-
terference Handler
allow the affected
Table continued…


5 RF INTERFERENCE critical 9998 UNKNOWN CAUSE If the state entered is
nently then contact
to the given state.
has no knowledge of
companying status
managed object is
known and managed.
6 RF INTERFERENCE minor 6001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
6 RF INTERFERENCE minor 6002 SOME ALARMS Some alarm cases are
Table continued…


issues left or not.
6 RF INTERFERENCE minor 6005 RECEIVER SIGNAL Check the RF environ-
PROBLEM (3) CLEARED ment settings. If alarm
personnel.
6 RF INTERFERENCE minor 6007 RF INTERFERENCE Contact the service per-
PROBLEM (3) WARNING (AIH sonnel to correct the
place the module.
6 RF INTERFERENCE minor 9998 UNKNOWN CAUSE Check the RF environ-
PROBLEM (3) ment settings. If alarm
personnel.
vestigate.
vestigate.
vestigate.
state.
MtsBrTransmitPath
MtsBrTransmitPath object.

Table 109: Explanation of the Source Content of an Alarm Message for the MtsBrTransmitPath
Object

MtsBrTransmitPath_a.b.1 a = MTS Site ID, b = MTS MtsBrTransmitPath_55.2.1 is equal to
Base Radio ID MTS Base Radio Transmit Path on
MTS Base Radio 2 on MTS Site 55
The following table lists the state and cause texts for the MtsBrTransmitPath object.
Table 110: State/Cause Text for the MtsBrTransmitPath Object

en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
node to manager or
nel to investigate.
Table continued…


ROLLB en component is not
reachable/ unknown
nently then contact
to the given state.
ROLLB reflects if there are still
issues left or not.
100 SIGNAL critical 100003 POWER ROLLBACK Immediately contact
FAULTS:VSWR, (1) FAULT the service personnel to
ROLLB correct the antenna,
ROLLB FAULT correct the antenna,
100 SIGNAL critical 9998 UNKNOWN CAUSE If the state entered is
FAULTS:VSWR, (1) unreachable/ unknown
ROLLB and it stays so perma-
nently then contact
Table continued…


to the given state.
FAULTS:ROLLB(VSW (1) only sent when the giv-
R) en component is not
reachable/ unknown
nently then contact
to the given state.
FAULTS:ROLLB(VSW (1) CLEARED cleared. The new state
R) reflects if there are still
issues left or not.
101 SIGNAL critical 101003 POWER ROLLBACK Immediately contact
FAULTS:ROLLB(VSW (1) FAULT the service personnel to
R) correct the antenna,
FAULTS:ROLLB(VSW (1) ING WAVE RATION sonnel to correct the
R) PROBLEM antenna, correct the
place the module.
FAULTS:ROLLB(VSW (1) sonnel to correct the
R) antenna, correct the
Table continued…


place the module.
FAULTS:VSWR(ROLL (1) only sent when the giv-
B) en component is not
reachable/ unknown
nently then contact
to the given state.
FAULTS:VSWR(ROLL (1) CLEARED cleared. The new state
B) reflects if there are still
issues left or not.
102 SIGNAL critical 102004 POWER ROLLBACK Contact the service per-
FAULTS:VSWR(ROLL (1) PROBLEM sonnel to correct the
B) antenna, correct the
place the module.
FAULTS:VSWR(ROLL (1) ING WAVE RATION the service personnel to
B) FAULT correct the antenna,
FAULTS:VSWR(ROLL (1) unreachable/ unknown
B) and it stays so perma-
nently then contact
Table continued…


to the given state.
PROB.:VSWR, ROLLB (3) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
PROB.:VSWR, ROLLB (3) CLEARED cleared. The new state
issues left or not.
103 SIGNAL minor 103004 POWER ROLLBACK Contact the service per-
PROB.:VSWR, ROLLB (3) PROBLEM sonnel to correct the
place the module.
PROB.:VSWR, ROLLB (3) ING WAVE RATION sonnel to correct the
place the module.
Table continued…


PROB.:VSWR, ROLLB (3) service personnel.
reachable/ unknown
nently then contact
to the given state.
issues left or not.
(6) quired.
3 POWER ROLLBACK critical 3001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
3 POWER ROLLBACK critical 3002 SOME ALARMS Some alarm cases are
issues left or not.
3 POWER ROLLBACK critical 3003 POWER ROLLBACK Immediately contact
FAULT (1) FAULT the service personnel to
3 POWER ROLLBACK critical 9998 UNKNOWN CAUSE If the state entered is
nently then contact
to the given state.
4 POWER ROLLBACK minor 4001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
4 POWER ROLLBACK minor 4002 SOME ALARMS Some alarm cases are
Table continued…


issues left or not.
4 POWER ROLLBACK minor 4004 POWER ROLLBACK Contact the service per-
PROBLEM (3) PROBLEM sonnel to correct the
place the module.
4 POWER ROLLBACK minor 9998 UNKNOWN CAUSE If alarm persists contact
PROBLEM (3) service personnel.
en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
5 VSWR STANDING critical 9998 UNKNOWN CAUSE If the state entered is
WAVE FAULT (1) unreachable/ unknown
nently then contact
Table continued…


to the given state.
has no knowledge of
companying status
managed object is
known and managed.
en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
Table continued…


place the module.
vestigate.
vestigate.
vestigate.
state.
MtsDpmBoardInternals
MtsDpmBoardInternals object.
Table 111: Explanation of the Source Content of an Alarm Message for the MtsDpmBoardInternals
Object

MtsDpmBoardInternals_a.b.1 a = MTS Site ID, b = MTS MtsDpmBoardInternals_55.2.1 is equal
DPM ID to MTS DPM Board Internals on MTS
DPM 2 on MTS Site 55
The following table lists the state and cause texts for the MtsDpmBoardInternals object.

Table 112: State/Cause Text for the MtsDpmBoardInternals Object

en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
state.
Table continued…


reachable/ unknown
nently then contact
to the given state.
issues left or not.
(6) quired.
4 MODULE FAULT major 4001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
4 MODULE FAULT major 4002 SOME ALARMS Some alarm cases are
issues left or not.
4 MODULE FAULT major 4003 MODULE FAULT Service personnel
Table continued…


site.
4 MODULE FAULT major 9998 UNKNOWN CAUSE If alarm persists contact
en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
rectify the module
module on the site.
has no knowledge of
companying status
managed object is
known and managed.
Table continued…


vestigate.
vestigate.
vestigate.
state.
MtsDpmSignalMeasurements
MtsDpmSignalMeasurements object.
MtsDpmSignalMeasurements Object

MtsDpmSignalMeasure- a = MTS Site ID, b = MTS MtsDpmSignalMeasurements_55.2.1 is
ments_a.b.1 DPM ID equal to MTS DPM Signal Measure-
ments on MTS DPM 2 on MTS Site 55
The following table lists the state and cause texts for the MtsDpmSignalMeasurements object.

Table 114: State/Cause Text for the MtsDpmSignal Object

en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
state.
POWL en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
POWL reflects if there are still
issues left or not.
FAULTS:VSWR, (1) LEVEL FAULT the service personnel to
POWL correct the antenna,
POWL FAULT correct the antenna,
POWL and it stays so perma-
nently then contact
to the given state.
FAULTS:POWL, (1) only sent when the giv-
(VSWR) en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
FAULTS:POWL, (1) CLEARED cleared. The new state
(VSWR) reflects if there are still
issues left or not.
FAULTS:POWL, (1) LEVEL FAULT the service personnel to
(VSWR) correct the antenna,
FAULTS:POWL, (1) ING WAVE RATION sonnel to correct the
(VSWR) PROBLEM antenna, correct the
place the module.
FAULTS:POWL, (1) sonnel to correct the
place the module.
(POWL) en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
(POWL) reflects if there are still
issues left or not.
FAULTS:VSWR, (1) LEVEL PROBLEM sonnel to correct the
(POWL) antenna, correct the
place the module.
(POWL) FAULT correct the antenna,
(POWL) and it stays so perma-
nently then contact
to the given state.
Table continued…


PROB.:VSWR, POWL (3) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
PROB.:VSWR, POWL (3) CLEARED cleared. The new state
issues left or not.
103 SIGNAL minor 103004 FORWARD POWER Contact the service per-
PROB.:VSWR, POWL (3) LEVEL PROBLEM sonnel to correct the
place the module.
PROB.:VSWR, POWL (3) ING WAVE RATION sonnel to correct the
place the module.
PROB.:VSWR, POWL (3) service personnel.
Table continued…


reachable/ unknown
nently then contact
to the given state.
issues left or not.
(6) quired.
3 FORWARD POWER critical 3001 NO REASON The no reason cause is
LEVEL FAULT (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
3 FORWARD POWER critical 3002 SOME ALARMS Some alarm cases are
LEVEL FAULT (1) CLEARED cleared. The new state
issues left or not.
3 FORWARD POWER critical 3003 FORWARD POWER Immediately contact
LEVEL FAULT (1) LEVEL FAULT the service personnel to
Table continued…


3 FORWARD POWER critical 9998 UNKNOWN CAUSE If the state entered is
LEVEL FAULT (1) unreachable/ unknown
nently then contact
to the given state.
4 FORWARD POWER minor 4001 NO REASON The no reason cause is
LEVEL PROB. (3) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
4 FORWARD POWER minor 4002 SOME ALARMS Some alarm cases are
LEVEL PROB. (3) CLEARED cleared. The new state
issues left or not.
4 FORWARD POWER minor 4004 FORWARD POWER Contact the service per-
LEVEL PROB. (3) LEVEL PROBLEM sonnel to correct the
Table continued…


place the module.
4 FORWARD POWER minor 9998 UNKNOWN CAUSE If alarm persists contact
LEVEL PROB. (3) service personnel.
en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
5 VSWR STANDING critical 9998 UNKNOWN CAUSE If the state entered is
WAVE FAULT (1) unreachable/ unknown
nently then contact
to the given state.
Table continued…


has no knowledge of
companying status
managed object is
known and managed.
en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
place the module.
Table continued…


vestigate.
vestigate.
vestigate.
state.
MtsExternalAlarms
MtsExternalAlarms object.
Table 115: Explanation of the Source Content of an Alarm Message for the MtsExternalAlarms
Object

MtsExternalAlarms_a.1 a = MTS Site ID MtsExternalAlarms_55.1 is equal to
MTS External Alarms on MTS Site 55
The following table lists the state and cause texts for the MtsExternalAlarms object.

Table 116: State/Cause Text for the MtsExternalAlarms Object

Number veri- Number
ty
1 UNKNOWN criti- 1001 NO REASON The no reason cause is
cal only sent when the giv-
reachable/ unknown
nently then contact
to the given state.
1 UNKNOWN criti- 9998 UNKNOWN CAUSE Alarm state from object
cal was unknown and most
(1) likely only a timing re-
node to manager or
nel to investigate.
2 NO ALARMS nor- 2001 NO REASON The no reason cause is
mal only sent when the giv-
reachable/ unknown
nently then contact
Table continued…


Number veri- Number
ty
to the given state.
2 NO ALARMS nor- 2201 ALARM 1 IS External alarm cleared.
mal CLEARED No action required un-
(6) less state persistently
re-occurs and re-occur-
rence is not planned, in
which case investigate
this user defined alarm
and possible causes.
Table continued…


Number veri- Number
ty
Table continued…


Number veri- Number
ty
2 NO ALARMS nor- 9998 UNKNOWN CAUSE External alarm cleared.
mal No action required un-
Table continued…


Number veri- Number
ty
3 SOME INPUTS ARE major 3001 NO REASON The no reason cause is
ALARMED (2) only sent when the giv-
en component is not
an alarm or unreacha-
ble/ unknown condition
then contact service
personnel for investi-
gating the alarm input
or connectivity to the
site or on the site.
3 SOME INPUTS ARE major 3101 ALARM 1 IS AC- Investigate the user de-
ALARMED (2) TIVE fined text in the alarm
and act accordingly to
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
Table continued…


Number veri- Number
ty
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
3 SOME INPUTS ARE major 3201 ALARM 1 IS Investigate the user de-
ALARMED (2) CLEARED fined text in the alarm
rectify alarm.
rectify alarm.
Table continued…


Number veri- Number
ty
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
rectify alarm.
Table continued…


Number veri- Number
ty
rectify alarm.
rectify alarm.
rectify alarm.
3 SOME INPUTS ARE major 9998 UNKNOWN CAUSE The no reason cause is
ALARMED (2) only sent when the giv-
en component is not
an alarm or unreacha-
ble/ unknown condition
gating the alarm input
or connectivity to the
site or on the site.
has no knowledge of
companying status
managed object is
known and managed.
ing FROM MANAGER ble from the manager.
(4) (SNMP NOSUCH- This should only be a
vestigate.
Table continued…


Number veri- Number
ty
(4) (SNMP GENERICER- This should only be a
vestigate.
(4) (SNMP TIMEOUT) This should only be a
vestigate.
state.
MtsFanKit
MtsFanKit object.
Table 117: Explanation of the Source Content of an Alarm Message for the MtsFanKit Object

MtsFanKit_a.1 a = MTS Site ID MtsFanKit_55.1 is equal to MTS Fan
Kit on MTS Site 55
The following table lists the state and cause texts for the MtsFanKit object.
Table 118: State/Cause Text for the MtsFanKit Object

en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
issues left or not.
state.
TION WITH FAN mal only sent when the giv-
reachable/ unknown
nently then contact
to the given state.
Table continued…


TION WITH FAN mal CLEARED cleared. The new state
issues left or not.
TION WITH FAN mal operation. No action re-
(6) quired.
TION NO FANS mal only sent when the giv-
reachable/ unknown
nently then contact
to the given state.
TION NO FANS mal CLEARED cleared. The new state
issues left or not.
TION NO FANS mal operation. No action re-
(6) quired.
4 FAN FAILURE major 4001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
Table continued…


nectivity to the node. In
case of other states then
consider the repair ac-
tions for the alarms
given state.
4 FAN FAILURE major 4002 SOME ALARMS Some alarm cases are
issues left or not.
4 FAN FAILURE major 4003 FAN FAILURE - KIT Service personnel
(2) 1 should be contacted to
clean or replace the
fans on the site.
fans on the site.
fans on the site.
4 FAN FAILURE major 9998 UNKNOWN CAUSE The unknown cause is
en component is not
state does not transition
to a non-failure state,
gating the alarm.
has no knowledge of
companying status
managed object is
known and managed.
Table continued…


vestigate.
vestigate.
vestigate.
state.
MtsOutputSignals
MtsOutputSignals object.
Table 119: Explanation of the Source Content of an Alarm Message for the MtsOutputSignals
Object

MtsOutputSignals_a.1 a = MTS Site ID MtsOutputSignals_55.1 is equal to
MTS Output Signals on MTS Site 55
The following table lists the state and cause texts for the MtsOutputSignals object.

Table 120: State/Cause Text for the MtsOutputSignals Object

en component is not
reachable/ unknown
nently then contact
to the given state.
state.
2 NO SIGNALS ACTIVE nor- 2001 NO REASON The no reason cause is
mal only sent when the giv-
reachable/ unknown
nently then contact
Table continued…


to the given state.
2 NO SIGNALS ACTIVE nor- 2003 OUTPUT SIGNAL 1 It is totally customer
mal DEACTIVATED specific if deactivating
(6) an output signal re-
quires action or is fully
ok
2 NO SIGNALS ACTIVE nor- 2005 OUTPUT SIGNAL 2 It is totally customer
mal DEACTIVATED specific if deactivating
ok
2 NO SIGNALS ACTIVE nor- 9998 UNKNOWN CAUSE This is normal system
(6) quired.
3 OUTPUT SIGNAL 1 nor- 3001 NO REASON The no reason cause is
ACTIVE mal only sent when the giv-
reachable/ unknown
nently then contact
to the given state.
3 OUTPUT SIGNAL 1 nor- 3002 OUTPUT SIGNAL 1 It is totally customer
ACTIVE mal ACTIVATED specific if activating an
(6) output signal requires
action or is fully ok
ACTIVE mal DEACTIVATED specific if deactivating
Table continued…


ok
3 OUTPUT SIGNAL 1 nor- 9998 UNKNOWN CAUSE This is normal system
ACTIVE mal operation. No action re-
(6) quired.
4 OUTPUT SIGNAL 2 nor- 4001 NO REASON The no reason cause is
reachable/ unknown
nently then contact
to the given state.
ACTIVE mal DEACTIVATED specific if deactivating
ok
4 OUTPUT SIGNAL 2 nor- 9998 UNKNOWN CAUSE This is normal system
(6) quired.
5 OUTPUT SIGNALS 1,2 nor- 5001 NO REASON The no reason cause is
reachable/ unknown
Table continued…


nently then contact
to the given state.
5 OUTPUT SIGNALS 1,2 nor- 5002 OUTPUT SIGNAL 1 It is totally customer
5 OUTPUT SIGNALS 1,2 nor- 5004 OUTPUT SIGNAL 2 It is totally customer
5 OUTPUT SIGNALS 1,2 nor- 9998 UNKNOWN CAUSE This is normal system
(6) quired.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
Table continued…


vestigate.
state.
MtsPowerSupplyUnit
MtsPowerSupplyUnit object.
Table 121: Explanation of the Source Content of an Alarm Message for the MtsPowerSupplyUnit
Object

MtsPowerSupplyUnit_a.1 a = MTS Site ID MtsPowerSupplyUnit_55.1 is equal to
MTS Power Supply Unit on MTS Site
55
The following table lists the state and cause texts for the MtsPowerSupplyUnit object.
Table 122: State/Cause Text for the MtsPsu Object

1 UNKNOWN/ critical 1001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
1 UNKNOWN/ critical 1002 SOME ALARMS Some alarm cases are
issues left or not.
state.
100 PSU FAULT: INPUT, critical 100001 NO REASON The no reason cause is
OUTPUT (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
100 PSU FAULT: INPUT, critical 100002 SOME ALARMS Some alarm cases are
OUTPUT (1) CLEARED cleared. The new state
issues left or not.
100 PSU FAULT: INPUT, critical 100003 POWER SUPPLY Service personnel
OUTPUT (1) OUTPUT FAILURE should be contacted to
Table continued…


check for cable short
cuts, rectify the module
module on the site.
100 PSU FAULT: INPUT, critical 100004 POWER SUPPLY IN- Service personnel
OUTPUT (1) PUT VOLTAGE should immediately be
FAILURE contacted to check the
sites power supply,
module on the site.
OUTPUT (1) BATTERY VOLT- should immediately be
AGE FAILURE contacted to check the
sites power supply,
check the battery sta-
tus, check for cable
short cuts, rectify the
site.
OUTPUT (1) BATTERY VOLT- should be contacted to
AGE WARNING check the sites power
supply, check the bat-
tery status, check for
cable short cuts, rectify
the site.
100 PSU FAULT: INPUT, critical 9998 UNKNOWN CAUSE If the state stays so per-
OUTPUT (1) manently then contact
to the given state.
101 PSU FAULT: IN, OUT, critical 101001 NO REASON The no reason cause is
HEAT (1) only sent when the giv-
en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
101 PSU FAULT: IN, OUT, critical 101002 SOME ALARMS Some alarm cases are
HEAT (1) CLEARED cleared. The new state
issues left or not.
101 PSU FAULT: IN, OUT, critical 101003 POWER SUPPLY Service personnel
HEAT (1) OUTPUT FAILURE should be contacted to
module on the site.
101 PSU FAULT: IN, OUT, critical 101004 POWER SUPPLY IN- Service personnel
HEAT (1) PUT VOLTAGE should immediately be
sites power supply,
module on the site.
HEAT (1) BATTERY VOLT- should immediately be
sites power supply,
site.
HEAT (1) BATTERY VOLT- should be contacted to
Table continued…


the site.
101 PSU FAULT: IN, OUT, critical 101007 HIGH TEMPERA- Check the status of the
HEAT (1) TURE ALARM fans in the PSU object.
problem.
101 PSU FAULT: IN, OUT, critical 9998 UNKNOWN CAUSE If the state stays so per-
HEAT (1) manently then contact
to the given state.
102 PSU critical 102001 NO REASON The no reason cause is
FAULT:IN,OUT,HEAT (1) only sent when the giv-
PR. en component is not
reachable/ unknown
nently then contact
to the given state.
102 PSU critical 102002 SOME ALARMS Some alarm cases are
FAULT:IN,OUT,HEAT (1) CLEARED cleared. The new state
PR.
Table continued…


issues left or not.
102 PSU critical 102003 POWER SUPPLY Service personnel
FAULT:IN,OUT,HEAT (1) OUTPUT FAILURE should be contacted to
PR. check for cable short
module on the site.
102 PSU critical 102004 POWER SUPPLY IN- Service personnel
FAULT:IN,OUT,HEAT (1) PUT VOLTAGE should immediately be
PR. FAILURE contacted to check the
sites power supply,
module on the site.
FAULT:IN,OUT,HEAT (1) BATTERY VOLT- should immediately be
PR. AGE FAILURE contacted to check the
sites power supply,
site.
FAULT:IN,OUT,HEAT (1) BATTERY VOLT- should be contacted to
PR. AGE WARNING check the sites power
the site.
102 PSU critical 102008 HIGH TEMPERA- Check the status of the
FAULT:IN,OUT,HEAT (1) TURE WARNING fans in the PSU object.
PR. If there are no fan prob-
peratures on other
Table continued…


102 PSU critical 9998 UNKNOWN CAUSE If the state stays so per-
FAULT:IN,OUT,HEAT (1) manently then contact
PR. service personnel for
to the given state.
103 PSU FAULT: OUTPUT, critical 103001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
103 PSU FAULT: OUTPUT, critical 103002 SOME ALARMS Some alarm cases are
issues left or not.
103 PSU FAULT: OUTPUT, critical 103003 POWER SUPPLY Service personnel
HEAT (1) OUTPUT FAILURE should be contacted to
module on the site.
103 PSU FAULT: OUTPUT, critical 103007 HIGH TEMPERA- Check the status of the
Table continued…


problem.
103 PSU FAULT: OUTPUT, critical 9998 UNKNOWN CAUSE If the state stays so per-
to the given state.
104 PSU FAULT:OUT- critical 104001 NO REASON The no reason cause is
PUT,HEAT PR. (1) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
104 PSU FAULT:OUT- critical 104002 SOME ALARMS Some alarm cases are
PUT,HEAT PR. (1) CLEARED cleared. The new state
issues left or not.
104 PSU FAULT:OUT- critical 104003 POWER SUPPLY Service personnel
PUT,HEAT PR. (1) OUTPUT FAILURE should be contacted to
module on the site.
104 PSU FAULT:OUT- critical 104008 HIGH TEMPERA- Check the status of the
PUT,HEAT PR. (1) TURE WARNING fans in the PSU object.
Table continued…


peratures on other
104 PSU FAULT:OUT- critical 9998 UNKNOWN CAUSE If the state stays so per-
PUT,HEAT PR. (1) manently then contact
to the given state.
105 PSU FAULT: INPUT, critical 105001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
105 PSU FAULT: INPUT, critical 105002 SOME ALARMS Some alarm cases are
issues left or not.
105 PSU FAULT: INPUT, critical 105004 POWER SUPPLY IN- Service personnel
HEAT (1) PUT VOLTAGE should immediately be
sites power supply,
Table continued…


module on the site.
HEAT (1) BATTERY VOLT- should immediately be
sites power supply,
site.
HEAT (1) BATTERY VOLT- should be contacted to
the site.
105 PSU FAULT: INPUT, critical 105007 HIGH TEMPERA- Check the status of the
problem.
105 PSU FAULT: INPUT, critical 9998 UNKNOWN CAUSE If the state stays so per-
to the given state.
106 PSU FAULT:INPUT, critical 106001 NO REASON The no reason cause is
HEAT PR. (1) only sent when the giv-
en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
106 PSU FAULT:INPUT, critical 106002 SOME ALARMS Some alarm cases are
HEAT PR. (1) CLEARED cleared. The new state
issues left or not.
106 PSU FAULT:INPUT, critical 106004 POWER SUPPLY IN- Service personnel
HEAT PR. (1) PUT VOLTAGE should immediately be
power supply to the site
or the battery status and
the power supply ca-
bling.
106 PSU FAULT:INPUT, critical 106005 POWER SUPPLY Service personnel
HEAT PR. (1) BATTERY VOLT- should immediately be
bling.
106 PSU FAULT:INPUT, critical 106006 POWER SUPPLY Service personnel
HEAT PR. (1) BATTERY VOLT- should immediately be
AGE WARNING contacted to check the
bling.
106 PSU FAULT:INPUT, critical 106008 HIGH TEMPERA- Check the status of the
HEAT PR. (1) TURE WARNING fans in the PSU object.
Table continued…


peratures on other
106 PSU FAULT:INPUT, critical 9998 UNKNOWN CAUSE If the state stays so per-
HEAT PR. (1) manently then contact
to the given state.
reachable/ unknown
nently then contact
to the given state.
issues left or not.
(6) quired.
3 PSU OUTPUT FAULT critical 3001 NO REASON The no reason cause is
en component is not
Table continued…


reachable/ unknown
nently then contact
to the given state.
3 PSU OUTPUT FAULT critical 3002 SOME ALARMS Some alarm cases are
issues left or not.
3 PSU OUTPUT FAULT critical 3003 POWER SUPPLY Service personnel
(1) OUTPUT FAILURE should be contacted to
module on the site.
3 PSU OUTPUT FAULT critical 9998 UNKNOWN CAUSE If the state stays so per-
(1) manently then contact
to the given state.
4 PSU INPUT FAULT critical 4001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
4 PSU INPUT FAULT critical 4002 SOME ALARMS Some alarm cases are
issues left or not.
4 PSU INPUT FAULT critical 4004 POWER SUPPLY IN- Service personnel
(1) PUT VOLTAGE should immediately be
sites power supply,
module on the site.
4 PSU INPUT FAULT critical 4005 POWER SUPPLY Service personnel
(1) BATTERY VOLT- should immediately be
sites power supply,
site.
4 PSU INPUT FAULT critical 4006 POWER SUPPLY Service personnel
(1) BATTERY VOLT- should be contacted to
the site.
4 PSU INPUT FAULT critical 9998 UNKNOWN CAUSE If the state stays so per-
to the given state.
Table continued…


5 PSU HEAT FAULT critical 5001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
5 PSU HEAT FAULT critical 5002 SOME ALARMS Some alarm cases are
issues left or not.
5 PSU HEAT FAULT critical 5007 HIGH TEMPERA- Check the status of the
problem.
5 PSU HEAT FAULT critical 9998 UNKNOWN CAUSE If the state stays so per-
to the given state.
Table continued…


has no knowledge of
companying status
managed object is
known and managed.
6 PSU HEAT PROBLEM major 6001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
6 PSU HEAT PROBLEM major 6002 SOME ALARMS Some alarm cases are
issues left or not.
6 PSU HEAT PROBLEM major 6008 HIGH TEMPERA- Check the status of the
peratures on other
Table continued…


6 PSU HEAT PROBLEM major 9998 UNKNOWN CAUSE If alarm persists contact
vestigate.
vestigate.
vestigate.
state.
MtsScBoardInternals
MtsScBoardInternals object.
Table 123: Explanation of the Source Content of an Alarm Message for the MtsScBoardInternals
Object

MtsScBoardInternals_a.1 a = MTS Site ID MtsScBoardInternals_55.1 is equal to
MTS Site Controller Board Internals
on MTS Site 55
The following table lists the state and cause texts for the MtsScBoardInternals object.

Table 124: State/Cause Text for the MtsScBoardInternals Object

en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
node to manager or
nel to investigate.
Table continued…


reachable/ unknown
nently then contact
to the given state.
issues left or not.
(6) quired.
3 MODULE FAULT critical 3001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
3 MODULE FAULT critical 3002 SOME ALARMS Some alarm cases are
issues left or not.
3 MODULE FAULT critical 3003 MODULE FAULT Service personnel
Table continued…


site.
3 MODULE FAULT critical 3005 HIGH TEMPERA- Check the status of the
problem.
3 MODULE FAULT critical 3007 CONFIGURATION Service personnel
(1) FAULT should immediately be
in this module
3 MODULE FAULT critical 9998 UNKNOWN CAUSE Supplementary text
(1) will be useful to identi-
fy source of the prob-
lem which can be one
of the following: 1)
temperature alarm (pro-
cessor) 2) OCXO clock
3) CP2 input 3) GPRS
4) CAN config. Con-
en component is not
reachable/ unknown
nently then contact
Table continued…


to the given state.
issues left or not.
rectify the module
module on the site.
4 MODULE PROBLEM minor 4006 HIGH TEMPERA- Check the status of the
peratures on other
4 MODULE PROBLEM minor 4008 CONFIGURATION Service personnel
(3) PROBLEM should be contacted to
module.
4 MODULE PROBLEM minor 9998 UNKNOWN CAUSE Supplementary text
(3) will be useful to identi-
fy source of the prob-
lem which can be one
of following: 1) tem-
perature warning (pro-
cessor) 2) OCXO clock
3) CP2 input 3) GPRS
4) CAN config 5) RTS
battery. Contact service
personnel.
has no knowledge of
companying status
Table continued…


managed object is
known and managed.
vestigate.
vestigate.
vestigate.
state.
MtsScDataPorts
MtsScDataPorts object.
Table 125: Explanation of the Source Content of an Alarm Message for the MtsScDataPorts Object

MtsScDataPorts_a.1 a = MTS Site ID MtsScDataPorts_55.1 is equal to MTS
Site Controller Data Port/Link on MTS
Site 55
The following table lists the state and cause texts for the MtsScDataPorts object.

Table 126: State/Cause Text for the MtsScDataPorts Object

en component is not
reachable/ unknown
nently then contact
to the given state.
issues left or not.
node to manager or
nel to investigate.
Table continued…


reachable/ unknown
nently then contact
to the given state.
issues left or not.
(6) quired.
4 ETHERNET PORT critical 4001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
4 ETHERNET PORT critical 4002 SOME ALARMS Some alarm cases are
issues left or not.
4 ETHERNET PORT critical 4003 ETHERNET PORT Service personnel
FAULT (1) FAULT should immediately be
contacted to check and
Table continued…


repair/replace this or
other modules on the
site.
4 ETHERNET PORT critical 9998 UNKNOWN CAUSE Collect information
FAULT (1) about the status of the
5 ETHERNET PORT minor 5001 NO REASON The no reason cause is
PROBLEMS (3) only sent when the giv-
en component is not
reachable/ unknown
nently then contact
to the given state.
5 ETHERNET PORT minor 5002 SOME ALARMS Some alarm cases are
PROBLEMS (3) CLEARED cleared. The new state
issues left or not.
5 ETHERNET PORT minor 5004 ETHERNET PORT Collect information
PROBLEMS (3) PROBLEM about the status of the
Table continued…


5 ETHERNET PORT minor 9998 UNKNOWN CAUSE Collect information
PROBLEMS (3) about the status of the
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.


state.
MtsScSiteReference
MtsScSiteReference object.
Table 127: Explanation of the Source Content of an Alarm Message for the MtsScSiteReference
Object

MtsScSiteReference_a.1 a = MTS Site ID MtsScSiteReference_55.1 is equal to
MTS Site Controller Site Reference on
MTS Site 55
The following table lists the state and cause texts for the MtsScSiteReference object.
Table 128: State/Cause Text for the MtsScSiteRef Object

1 UNKNOWN critical 1001 NO REASON The site controller has
(1) just started and is wait-
ing for GPS signal, this
condition is transitory
1 UNKNOWN critical 1005 1PPS LOST The GPS receiver has
(1) lost track of satellites
before the site refer-
ence start-up complet-
ed. This condition is
transitory.
1 UNKNOWN critical 1006 FREE RUN TIMER Lock to GPS signal has
(1) EXPIRED not been performed
during configured start-
up time. Check GPS re-
ceiver status.
1 UNKNOWN critical 1012 FREQUENCY CALI- GPS is presently not
(1) BRATION TIMER available and the Site
EXPIRED Reference has been in
non-sync. mode with-
out GPS for so long
that frequency may be
outside Type approval
limits. The BTS should
be disabled or calibrat-
ed within 2 weeks by
SL2 approved Service
Personnel
Table continued…


1 UNKNOWN critical 1013 GPS OK The site controller has
(1) just started, the GPS re-
ceiver is tracking satel-
lites however the site
reference has not com-
pleted initialization.
This condition is transi-
tory
1 UNKNOWN critical 1014 GPS AND NTS LOST Lost GPS and NTS.
(1) Check the connection
and GPS receiver.
node to manager or
nel to investigate.
2 ENABLED SYNC nor- 2001 NO REASON Normal operation. Site
mal Reference is fully
(6) synchronized to GPS
signal
2 ENABLED SYNC nor- 2013 GPS OK This is normal system
(6) quired.
2 ENABLED SYNC nor- 9998 UNKNOWN CAUSE If alarm persists contact
(6)
3 DISABLED critical 3001 NO REASON Site Reference is not
(1) able to offer its service
to the BTS. It could be
DAC/OCXO failure or
Site Reference alarm.
3 DISABLED critical 3006 FREE RUN TIMER The Site Reference
(1) EXPIRED card is currently in free
run mode but the con-
figurable timer has ex-
pired. This situation is
may be due to the GPS
receiver not receiving
an adequate GPS sig-
Table continued…


nal. The GPS antenna
and connection from
the antenna to the Site
Controller should be
checked and replaced if
necessary. If problem
persists, service person-
nel should be contact-
ed.
3 DISABLED critical 3009 SITE REFERENCE The Site Reference has
(1) ALARM reported an internal
alarm. Motorola service
personnel should be
problem.
planned, otherwise pos-
sible normal operation
caused by loss of GPS.
If the state continues
check the GPS receiver
and signal or contact
vestigate.
4 FREE-RUN SYNC minor 4005 1PPS LOST The 1PPS signal from
(3) the GPS has been lost.
Site Controller cabling
and termination should
be checked. If the prob-
lem persists the GPS
should be replaced.
4 FREE-RUN SYNC minor 4013 GPS OK The Site reference is
phase and the GPS has
been able to find suffi-
cient satellites to begin
the transition to the En-
abled Sync state. This
is a transitory state, no
user action is required.
4 FREE-RUN SYNC minor 9998 UNKNOWN CAUSE The Site Reference has
(3) reported a state change
however cause was un-
known. No action re-
quired if user initiated
changes were made
Table continued…


however if alarm per-
sists contact service
Site Ref.
5 NON-SYNC minor 5005 1PPS LOST The Site reference is
(3) not synchronized to
GPS phase. The BTS is
configured for ASC op-
eration, and the GPS
was unable to acquire
sufficient satellites be-
fore the configurable
GPS start up timer ex-
pired. This is normal
operation and no fur-
ther action is required.
The BTS is capable of
operating in this mode
without GPS for up to
12 months.
5 NON-SYNC minor 5006 FREE RUN TIMER The Site reference is
(3) EXPIRED not synchronized to
GPS phase because the
configurable timer has
expired. This situation
and connection from
necessary. If the prob-
lem persists service
personnel should be
contacted to examine
the problem. The BTS
is capable of operating
in this mode without
GPS for up to 12
months.
5 NON-SYNC minor 5009 SITE REFERENCE The Site reference is
(3) ALARM not synchronized to
GPS phase. An unspe-
cified site reference
alarm condition has oc-
curred. Motorola serv-
ice personnel should be
Table continued…


problem.
5 NON-SYNC minor 5013 GPS OK The BTS is working in
(3) non-synchronized
mode. However now
the GPS is restored.
This is normal opera-
tion and no further ac-
tion is required, howev-
er a restart of the BTS
will bring the BTS
back into synchronized
operation in most cir-
cumstances.
5 NON-SYNC minor 5014 GPS AND NTS LOST GPS as well as NTS
(3) connection is lost.
Check GPS and NTS
status. Manual calibra-
tion will be required if
this situation prolongs
for more then 12
months.
5 NON-SYNC minor 9998 UNKNOWN CAUSE If alarm persists contact
has no knowledge of
companying status
managed object is
known and managed.
6 NON-SYNC ADJ-RE- critical 6005 1PPS LOST The Site reference is
QUIRED (1) not synchronized to
Table continued…


12 months.
6 NON-SYNC ADJ-RE- critical 6006 FREE RUN TIMER The Site reference is
QUIRED (1) EXPIRED not synchronized to
GPS phase. The GPS
has not been able to
track satellites for the
past 12 months and the
BTS may be operating
outside its frequency
specifications. SL2
service personnel
rectify the problem.
6 NON-SYNC ADJ-RE- critical 6009 SITE REFERENCE The Site reference is
QUIRED (1) ALARM not synchronized to
GPS phase. The GPS
specifications and an
unspecified site refer-
ence condition has oc-
problem.
6 NON-SYNC ADJ-RE- critical 6012 FREQUENCY CALI- The Site reference is
QUIRED (1) BRATION TIMER not synchronized to
EXPIRED GPS phase. GPS is
presently not available
and the Site Reference
has been in non-sync.
mode without GPS for
so long that frequency
may be outside Type
approval limits. The
BTS should be disabled
or calibrated within 2
weeks by SL2 ap-
proved Service Person-
nel
6 NON-SYNC ADJ-RE- critical 6013 GPS OK The Site reference is
GPS phase. The GPS
Table continued…


receiver has been re-
stored after the calibra-
tion timer has expired.
The GPS signal will
automatically calibrate
the site reference in a
few minutes. This con-
dition is transitory and
no user action is re-
quired.
6 NON-SYNC ADJ-RE- critical 9998 UNKNOWN CAUSE The Site reference is
GPS phase.
7 ENABLED NON-SYNC nor- 7001 NO REASON The Site reference is
mal not synchronized to
(6) GPS phase. This is nor-
mal system operation
when the site controller
is configured for FNC
operation. No action is
required.
7 ENABLED NON-SYNC nor- 7005 1PPS LOST The Site reference is
(6) GPS phase. The GPS
signal that was being
used to maintain site
reference calibration
has ceased. The site is
capable of continuing
operation for up to 12
months in the condi-
tion.
7 ENABLED NON-SYNC nor- 7013 GPS OK The Site reference is
mal operation and no
action is required. A
GPS signal is available
and is being used to
maintain calibration of
the site reference.
7 ENABLED NON-SYNC nor- 9998 UNKNOWN CAUSE If alarm persists contact
(6)
Table continued…


vestigate.
vestigate.
vestigate.
state.
MtsSite
MtsSite object.
Table 129: Explanation of the Source Content of an Alarm Message for the MtsSite Object

The alias assigned to the MtsSite n/a Since this is an object to which an alias
object is assigned the source information is a
The following table lists the state and cause texts for the MtsSite object.
Table 130: State/Cause Text for the MtsSite Object

1 UNKNOWN/ critical 1001 NO REASON This state occurs during
UNREACHABLE (1) initialization. Then it
should be replaced by
state Normal, cause No
reason. If it happens
than no action is re-
quired. If not check
other alarms and follow
Table continued…


instructions or contact
service personnel.
state.
11 SITE RESET critical 11006 USER REQUESTED State change caused by
tion. No action re-
quired.
11 SITE RESET critical 9998 UNKNOWN CAUSE State change cause was
(1) reported as unknown.
Transitory state. Inves-
tigate accompanying
alarms and final state.
No action required if
user requested. Other-
wise contact service
personnel for investiga-
tion of Site reset.
21 SITE DISABLE/SITE critical 21006 USER REQUESTED State change caused by
OFF (1) a user initiated opera-
tion.
21 SITE DISABLE/SITE critical 21007 RECOVERY Transitory state. The
OFF (1) site is in the process of
recovery before trunk-
ing operations can
commence. No action
is required.
21 SITE DISABLE/SITE critical 9998 UNKNOWN CAUSE The site is in the proc-
OFF (1) ess of recovery or the
state was changed by
the user. No action is
required.
31 NO TRUNKING critical 31001 NO REASON This state occurs during
(1) initialization. The site
should enter to wide
trunking or site trunk-
Table continued…


ing state in a few mi-
nutes. If it does than no
action is required. If
not check other alarms
and follow instructions
or contact service per-
sonnel. This state may
also occur when site
link is down and site
trunking is disabled.
31 NO TRUNKING critical 31002 NO MINIMUM There are insufficient
(1) NUMBERS OF resources available at
CHANNELS the site for the MTS to
perform trunking oper-
ations. This indicates
the Base Radio(s) has
failed. Contact service
the root cause.
31 NO TRUNKING critical 31003 NO VOICE CHAN- No voice channels are
(1) NEL available at the site and
therefore the site is un-
able to operate in
trunking mode. This
can be seen while the
site is transitioning into
the normal trunking
mode. If the state per-
sists it may indicates
that either the Base Ra-
dio(s) has failed or the
voice link to the MTS
has failed. Further in-
vestigation will be re-
quired to identify the
root cause.
31 NO TRUNKING critical 31004 NO CONTROL No control channel is
(1) CHANNEL currently available at
the site. Without the
control channel the site
is unable to operate in
trunking mode. This is
caused by the failure of
the Base Radio carry-
ing the control channel.
31 NO TRUNKING critical 31005 SITE LINK WAS The site is reporting its
(1) DOWN current state. This indi-
cates the site is unable
to operate in trunking
mode due to the link
Table continued…


between the site and
the master site being
down. The site will re-
cover to wide trunking
mode from this state.
31 NO TRUNKING critical 31006 USER REQUESTED State change was
(1) caused by a user initiat-
ed operation.
31 NO TRUNKING critical 31007 RECOVERY The site is in the proc-
(1) ess of recovery before
trunking operations can
commence. This is nor-
mal system operation,
no action is required.
31 NO TRUNKING critical 31008 ETHERNET SITE The site is reporting its
(1) LINK DISABLED current state. This indi-
cates the site is unable
to operate in trunking
mode due to lack of
valid Ethernet site link
license. The site will
recover to wide trunk-
ing mode from this
state.
31 NO TRUNKING critical 9998 UNKNOWN CAUSE If the state is not user
(1) requested check the
Base Radio status.
51 SITE TRUNKING major 51003 NO VOICE CHAN- No voice channels are
(2) NEL available at the site.
This indicates that the
has failed. System con-
figuration and physical
links to the site should
be checked to identify
the root cause.
51 SITE TRUNKING major 51005 SITE LINK WAS The site is reporting its
(2) DOWN current state. This indi-
cates the site has been
operating in site trunk-
ing due to the link be-
tween the site and the
master site being down.
The site will recover to
wide trunking mode
from this state.
Table continued…


51 SITE TRUNKING major 51006 USER REQUESTED State change caused by
tion.
51 SITE TRUNKING major 51007 RECOVERY The site is in the proc-
(2) ess of recovery before
51 SITE TRUNKING major 51008 ETHERNET SITE The site is reporting its
(2) LINK DISABLED current state. This indi-
cates the site is operat-
ing in site trunking
mode due to lack of
ing mode from this
state.
51 SITE TRUNKING major 9998 UNKNOWN CAUSE The site is in site trunk-
(2) ing. Use diagnostics in
to set the site in wide
trunking.
has no knowledge of
companying status
managed object is
known and managed.
61 SITE TO WIDE TRAN- warn- 61001 NO REASON This is a transitional
SITION ing (4) state which can occur
in normal system oper-
ation. No action is re-
quired.
61 SITE TO WIDE TRAN- warn- 61005 SITE LINK WAS This is a transitional
SITION ing (4) DOWN state which can occur
ation. This state and
cause indicates the site
has been operating in
site trunking due to the
Table continued…


link between the re-
mote site and the mas-
ter site being down.
The site will recover to
wide trunking mode
from this state.
61 SITE TO WIDE TRAN- warn- 61009 ETHERNET SITE The site is reporting its
SITION ing (4) LINK ENABLED current state. This indi-
cates the site was oper-
ating in site trunking
mode due to lack of
ing mode from this
state.
61 SITE TO WIDE TRAN- warn- 9998 UNKNOWN CAUSE This is a transitional
SITION ing (4) state which can occur
ation. No action is re-
quired.
71 WIDE TRUNKING nor- 71001 NO REASON This is normal system
(6) quired.
71 WIDE TRUNKING nor- 71003 NO VOICE CHAN- -
mal NEL
(6)
71 WIDE TRUNKING nor- 71006 USER REQUESTED State change caused by
quired.
71 WIDE TRUNKING nor- 71007 RECOVERY -
mal
(6)
71 WIDE TRUNKING nor- 9998 UNKNOWN CAUSE This is normal system
(6) quired.
vestigate.
Table continued…


(SNMP GENERICER- temporary state other-
ROR) wise service personnel
vestigate.
vestigate.
state.
MtsSscBoardInternals
MtsSscBoardInternals object.
Table 131: Explanation of the Source Content of an Alarm Message for the MtsSscBoardInternals
Object

MtsSscBoardInternals_a.1 a = MTS Site ID MtsSscBoardInternals_66.1 is equal to
MTS Standby Site Controller Board
Internals on MTS Site 66
The following table lists the state and cause texts for the MtsSscBoardInternals object.
Table 132: State/Cause Text for the MtsSscBoardInernals Object

1 UNKNOWN major 1001 NO REASON The no reason cause is
en component is not
reachable/ unknown
Table continued…


nently then contact
to the given state.
1 UNKNOWN major 1002 SOME ALARMS Some alarm cases are
issues left or not.
1 UNKNOWN major 9998 UNKNOWN CAUSE Alarm state from object
node to manager or
nel to investigate.
2 STANDBY NORMAL nor- 2001 NO REASON The no reason cause is
OPERATION mal only sent when the giv-
reachable/ unknown
nently then contact
to the given state.
Table continued…


2 STANDBY NORMAL nor- 2002 SOME ALARMS Some alarm cases are
OPERATION mal CLEARED cleared. The new state
issues left or not.
2 STANDBY NORMAL nor- 9998 UNKNOWN CAUSE This is normal system
OPERATION mal operation. No action re-
(6) quired.
3 STANDBY MODULE major 3001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
3 STANDBY MODULE major 3002 SOME ALARMS Some alarm cases are
issues left or not.
3 STANDBY MODULE major 3003 MODULE FAULT Service personnel
FAULT (2) should immediately be
site.
3 STANDBY MODULE major 3005 HIGH TEMPERA- Check the status of the
FAULT (2) TURE ALARM fans in the PSU object.
Table continued…


problem.
3 STANDBY MODULE major 3007 CONFIGURATION Service personnel
FAULT (2) FAULT should immediately be
in this module
3 STANDBY MODULE major 9998 UNKNOWN CAUSE If alarm persists contact
FAULT (2) service personnel.
4 STANDBY MODULE minor 4001 NO REASON The no reason cause is
en component is not
reachable/ unknown
nently then contact
to the given state.
4 STANDBY MODULE minor 4002 SOME ALARMS Some alarm cases are
issues left or not.
4 STANDBY MODULE minor 4004 MODULE PROBLEM Service personnel
PROBLEM (3) should be contacted to
rectify the module
module on the site.
4 STANDBY MODULE minor 4006 HIGH TEMPERA- Check the status of the
PROBLEM (3) TURE WARNING fans in the PSU object.
peratures on other
Table continued…


4 STANDBY MODULE minor 4008 CONFIGURATION Service personnel
PROBLEM (3) PROBLEM should be contacted to
module.
4 STANDBY MODULE minor 9998 UNKNOWN CAUSE If alarm persists contact
PROBLEM (3) service personnel.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.


state.
MtsSscSiteReference
MtsSscSiteReference object.
Table 133: Explanation of the Source Content of an Alarm Message for the MtsSscSiteReference
Object

MtsSscSiteReference_a.1 a = MTS Site ID MtsSscSiteReference_66.1 is equal to
MTS Standby Site Controller Site Ref-
erence on MTS Site 66
The following table lists the state and cause texts for the MtsSscSiteReference object.
Table 134: State/Cause Text for the MtsSscSiteRef Object

1 UNKNOWN major 1001 NO REASON The Site Controller has
(2) just started. This condi-
tion is transitory
1 UNKNOWN major 1005 1PPS LOST If alarm persists contact
1 UNKNOWN major 1006 FREE RUN TIMER If alarm persists contact
(2) EXPIRED service personnel.
1 UNKNOWN major 1012 FREQUENCY CALI- If alarm persists contact
(2) BRATION TIMER service personnel.
EXPIRED
1 UNKNOWN major 1013 GPS OK The site controller has
(2) just started, the GPS re-
ceiver is tracking satel-
lites however the site
reference has not com-
pleted initialization.
This condition is transi-
tory
1 UNKNOWN major 1014 GPS AND NTS LOST If alarm persists contact
1 UNKNOWN major 9998 UNKNOWN CAUSE Alarm state from object
Table continued…


node to manager or
nel to investigate.
2 ENABLED SYNC nor- 2001 NO REASON Normal operation. Site
mal Reference is fully
signal
2 ENABLED SYNC nor- 2013 GPS OK This is normal system
(6) quired.
2 ENABLED SYNC nor- 9998 UNKNOWN CAUSE If alarm persists contact
(6)
3 DISABLED major 3001 NO REASON Site Reference is not
(2) able to offer its service
to the BTS. It could be
DAC/OCXO failure or
Site Reference alarm.
nel to investigate.
3 DISABLED major 3006 FREE RUN TIMER The Site Reference
(2) EXPIRED card is currently in free
run mode but the con-
figurable timer has ex-
pired. This situation is
and connection from
lem persists a SL2
service personnel
examine the problem.
3 DISABLED major 3009 SITE REFERENCE The Site Reference has
(2) ALARM reported an internal
alarm. Motorola service
personnel should be
Table continued…


problem.
planned, otherwise pos-
sible normal operation
caused by loss of GPS.
If the state continues
check the GPS receiver
and signal or contact
vestigate.
4 FREE-RUN SYNC minor 4005 1PPS LOST The 1PPS signal from
(3) the GPS has been lost.
Site Controller cabling
and termination should
be checked. If the prob-
lem persists the GPS
should be replaced.
4 FREE-RUN SYNC minor 4013 GPS OK The Site reference is
phase and the GPS has
been able to find suffi-
cient satellites to begin
the transition to the En-
abled Sync state. This
is a transitory state, no
user action is required.
4 FREE-RUN SYNC minor 9998 UNKNOWN CAUSE The Site Reference has
(3) reported a state change
however cause was un-
known. No action re-
quired if user initiated
changes were made
however if alarm per-
sists contact service
Site Ref.
5 NON-SYNC minor 5005 1PPS LOST The Site reference is
(3) not synchronized to
Table continued…


12 months.
5 NON-SYNC minor 5006 FREE RUN TIMER The Site reference is
(3) EXPIRED not synchronized to
GPS phase because the
configurable timer has
expired. This situation
and connection from
lem persists service
personnel should be
contacted to examine
the problem. The BTS
is capable of operating
in this mode without
GPS for up to 12
months.
5 NON-SYNC minor 5009 SITE REFERENCE The Site reference is
(3) ALARM not synchronized to
GPS phase. An unspe-
cified site reference
alarm condition has oc-
problem.
5 NON-SYNC minor 5013 GPS OK The BTS is working in
(3) non-synchronized
mode. However now
the GPS is restored.
This is normal opera-
tion and no further ac-
tion is required, howev-
er a restart of the BTS
will bring the BTS
back into synchronized
operation in most cir-
cumstances.
Table continued…


5 NON-SYNC minor 5014 GPS AND NTS LOST GPS as well as NTS
(3) connection is lost.
Check GPS and NTS
status. Manual calibra-
tion will be required if
this situation prolongs
for more then 12
months.
5 NON-SYNC minor 9998 UNKNOWN CAUSE If alarm persists contact
has no knowledge of
companying status
managed object is
known and managed.
6 NON-SYNC ADJ-RE- major 6005 1PPS LOST The Site reference is
12 months.
6 NON-SYNC ADJ-RE- major 6006 FREE RUN TIMER The Site reference is
QUIRED (2) EXPIRED not synchronized to
GPS phase. The GPS
specifications. If prob-
lem persists, service
Table continued…


personnel should be
contacted.
6 NON-SYNC ADJ-RE- major 6009 SITE REFERENCE The Site reference is
QUIRED (2) ALARM not synchronized to
GPS phase. The GPS
specifications and an
unspecified site refer-
ence condition has oc-
problem.
6 NON-SYNC ADJ-RE- major 6012 FREQUENCY CALI- The Site reference is
QUIRED (2) BRATION TIMER not synchronized to
EXPIRED GPS phase. GPS is
presently not available
and the Site Reference
has been in non-sync.
mode without GPS for
so long that frequency
may be outside Type
approval limits. The
BTS should be disabled
or calibrated within 2
weeks by Motorola ap-
proved Service Person-
nel
6 NON-SYNC ADJ-RE- major 6013 GPS OK The Site reference is
GPS phase. The GPS
receiver has been re-
stored after the calibra-
tion timer has expired.
The GPS signal will
automatically calibrate
the site reference in a
few minutes. This con-
dition is transitory and
no user action is re-
quired.
6 NON-SYNC ADJ-RE- major 9998 UNKNOWN CAUSE If alarm persists contact
QUIRED (2) service personnel.
Table continued…


7 ENABLED NON-SYNC nor- 7001 NO REASON The Site reference is
mal system operation
when the site controller
is configured for FNC
operation. No action is
required.
7 ENABLED NON-SYNC nor- 7005 1PPS LOST The Site reference is
(6) GPS phase. The GPS
signal that was being
used to maintain site
reference calibration
has ceased. The site is
capable of continuing
operation for up to 12
months in the condi-
tion.
7 ENABLED NON-SYNC nor- 7013 GPS OK The Site reference is
mal operation and no
action is required. A
GPS signal is available
and is being used to
maintain calibration of
the site reference.
7 ENABLED NON-SYNC nor- 9998 UNKNOWN CAUSE If alarm persists contact
(6)
vestigate.
vestigate.
Table continued…


vestigate.
state.
pdgPDR
pdgPDR object.
Table 135: Explanation of the Source Content of an Alarm Message for the pdgPDR Object

pdgPDR_a.1.1 a = Local Zone ID pdgPDR_56.1.1 is equal to PDR in
Zone 56
The following table lists the state and cause text for the pdgPDR object.
Table 136: State/Cause Text for the pdgPDR Object

1 ENABLED (NON-RE- nor- 5300 PDR STARTED AND This is normal system
DUNDANT) mal RUNNING operation. No action re-
(6) quired.
1 ENABLED (NON-RE- nor- 6300 PDR STARTED AND This is normal system
DUNDANT) mal RUNNING operation. No action re-
(6) quired.
2 RESTARTING warn- 5301 PDR RESTARTING PDR application is re-
ing (4) starting. No action re-
quired if restart was
User Requested.
2 RESTARTING warn- 7301 PDR RESTARTING PDR application is re-
User Requested.
3 OVERLOADED warn- 5304 PDR MESSAGE CA- Excessive message
ing (4) PACITY EXCEEDED traffic through the
PDR. Reduce data traf-
fic.
3 OVERLOADED warn- 8304 PDR MESSAGE CA- Excessive message
ing (4) PACITY EXCEEDED traffic through the
Table continued…


PDR. Reduce data traf-
fic.
4 ACTIVE nor- 5311 PDR STARTED AND PDR application started
mal RUNNING and running. No action
(6) required.
4 ACTIVE nor- 9311 PDR STARTED AND PDR application started
mal RUNNING and running. No action
(6) required.
5 STANDBY nor- 10305 PDR IS READY. No action required.
mal SWITCHOVER
(6) AVAILABLE
5 STANDBY nor- 5305 PDR IS READY. No action required.
mal SWITCHOVER
(6) AVAILABLE
has no knowledge of
companying status
managed object is
known and managed.
6 OPERATIONALLY minor 11306 DB RETRIEVAL ER- No action required.
DOWN (3) ROR
6 OPERATIONALLY minor 11307 DB RESTORATION Switchover discour-
DOWN (3) ERROR aged. DB corruption
possible.
6 OPERATIONALLY minor 11308 STANDBY PDR UN- No action required.
DOWN (3) AVAILABLE
6 OPERATIONALLY minor 11309 STANDBY CO-RESI- No action required.
DOWN (3) DENT RNG UN-
AVAILABLE
6 OPERATIONALLY minor 11312 UNKNOWN FAIL- No action required.
DOWN (3) URE
6 OPERATIONALLY minor 5306 DB RETRIEVAL ER- No action required.
DOWN (3) ROR
6 OPERATIONALLY minor 5307 DB RESTORATION Switchover discour-
DOWN (3) ERROR aged. DB corruption
possible.
Table continued…


6 OPERATIONALLY minor 5308 STANDBY PDR UN- No action required.
DOWN (3) AVAILABLE
6 OPERATIONALLY minor 5309 STANDBY CO-RESI- No action required.
DOWN (3) DENT RNG UN-
AVAILABLE
DOWN (3) URE
7 ADMINISTRATIVELY warn- 12310 STANDBY PDR AD- No action required.
DOWN ing (4) MINISTRATIVELY
DOWN
DOWN - UPGRADE
DOWN
DOWN - UPGRADE
vestigate.
vestigate.
vestigate.
state.

pdgPDRGGSNLink
pdgPDRGGSNLink object.
Table 137: Explanation of the Source Content of an Alarm Message for the pdgPDRGGSNLink
Object

pdgPDRGGSNLink_a.1.1.d a = Local Zone ID, d = GGSN ID pdgPDRGGSNLink_1.1.1.10 is equal
to PDR in Zone 1 to GGSN 10 Link
The following table lists the state and cause text for the pdgPDRGGSNLink object.
Table 138: State/Cause Text for the pdgPDRGGSNLink Object

1 DOWN critical 6201 PDR-GGSN COM- Communication be-
(1) MUNICATION tween PDR and GGSN
FAILED failed while the link
was up and monitored.
Number of message re-
tries exceeded the max-
imum number of at-
tempts. Check connec-
tivity between PDR and
GGSN.
1 DOWN critical 6203 PDR-GGSN LINK First context activation
(1) DOWN UNMONI- attempted while the
TORED link was up and unmo-
nitored failed, or the
link was down and
monitored while last
mobile context was re-
moved. Check connec-
GGSN. Note: re-estab-
lishment of PDR-
GGSN connectivity
will not cause a link
state change until the
first context activation
attempt.
1 DOWN critical 7201 PDR-GGSN COM- Communication be-
(1) MUNICATION tween PDR and GGSN
FAILED failed while the link
was up and monitored.
Number of message re-
tries exceeded the max-
imum number of at-
tempts. Check connec-
Table continued…


GGSN.
1 DOWN critical 7203 PDR-GGSN LINK First context activation
(1) DOWN UNMONI- attempted while the
TORED link was up and unmo-
nitored failed, or the
link was down and
monitored while last
mobile context was re-
moved. Check connec-
GGSN. Note: re-estab-
lishment of PDR-
GGSN connectivity
will not cause a link
state change until the
first context activation
attempt.
1 DOWN critical 9998 UNKNOWN CAUSE Check connectivity be-
(1) tween PDR and GGSN.
2 UP nor- 6200 PDR-GGSN LINK IS Communication be-
mal UP tween PDR and GGSN
(6) succeeded and PDR
now has at least one ac-
tive mobile context.
Normal operation. No
action required.
2 UP nor- 6202 PDR-GGSN LINK UP Communication be-
mal MONITORED tween PDR and GGSN
(6) was successful while
last active mobile con-
text was removed. Nor-
mal operation. No ac-
tion required.
2 UP nor- 8200 PDR-GGSN LINK IS Communication be-
mal UP tween PDR and GGSN
(6) succeeded and PDR
now has at least one ac-
tive mobile context.
Normal operation. No
action required.
2 UP nor- 8202 PDR-GGSN LINK UP Communication be-
mal MONITORED tween PDR and GGSN
(6) was successful while
last active mobile con-
text was removed. Nor-
mal operation. No ac-
tion required.
Table continued…


(6) quired.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.
state.
pdgPDRRNG
pdgPDRRNG object.

Table 139: Explanation of the Source Content of an Alarm Message for the pdgPDRRNG Object

pdgPDRRNG_a.1.1 a = Local Zone ID pdgPDRRNG_56.1.1 is equal to RNG
in Zone 56
The following table lists the state and cause text for the pdgPDRRNG object.
Table 140: State/Cause Text for the pdgPDRRNG Object

1 ENABLED nor- 6600 RNG RUNNING This is normal system
(6) quired.
1 ENABLED nor- 7600 RNG RUNNING This is normal system
(6) quired.
user initiated.
2 RESTARTING warn- 6601 RNG RESTARTING RNG application is re-
User Requested and
alarm is not repeating.
2 RESTARTING warn- 8601 RNG RESTARTING RNG application is re-
User Requested and
2 RESTARTING warn- 9998 UNKNOWN CAUSE RNG application is re-
User Requested and
3 OVERLOADED warn- 6604 RNG MESSAGE CA- RNG is overloaded. In-
ing (4) PACITY EXCEEDED vestigate the load on
the RNG BTS. If there
is excessive message
traffic, reduce data traf-
fic.
3 OVERLOADED warn- 9604 RNG MESSAGE CA- RNG is overloaded. In-
ing (4) PACITY EXCEEDED vestigate the load on
fic.
Table continued…


3 OVERLOADED warn- 9998 UNKNOWN CAUSE RNG is overloaded. In-
ing (4) vestigate the load on
fic.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.
state.
pdgPDRRNGCommunication

pdgPDRRNGCommunication object.
pdgPDRRNGCommunication Object

pdgPDRRNGCommunica- a = Local Zone ID, d = Local Zone pdgPDRRNGCommunica-
tion_ a.1.1.d.1.1 ID tion_56.1.1.56.1.1 is equal to RNG to
PDR communication in Zone 56
The following table lists the state and cause text for the pdgPDRRNGCommunication object.
Table 142: State/Cause Text for the pdgPDRRNGCommunication Object

1 REACHABLE nor- 6800 LOCAL RNG IS Local RNG control link
mal REACHABLE is up. The RNG is
(6) reachable from the
PDR. States of RNG
related objects can be
obtained. Normal sys-
tem operation - No ac-
tion required.
1 REACHABLE nor- 7800 LOCAL RNG IS Local RNG control link
mal REACHABLE is up. The RNG is
PDR. States of RNG
tion required.
1 REACHABLE nor- 9998 UNKNOWN CAUSE Local RNG control link
mal is up. The RNG is
PDR. States of RNG
tion required.
2 UNREACHABLE critical 6801 LOCAL RNG IS UN- Local RNG control link
(1) REACHABLE is down. The RNG is
unreachable from the
PDR. True states of
RNG related objects
cannot be obtained.
Check connection be-
tween PDR and RNG.
2 UNREACHABLE critical 8801 LOCAL RNG IS UN- Local RNG control link
(1) REACHABLE is down. The RNG is
unreachable from the
Table continued…


PDR. True states of
RNG related objects
cannot be obtained.
tween PDR and RNG.
2 UNREACHABLE critical 9998 UNKNOWN CAUSE Local RNG control link
(1) is down, but the true
states of RNG related
objects cannot be ob-
tained. Check connec-
tion between PDR and
RNG.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.


state.
pdgPDRRNGLink
pdgPDRRNGLink object.
Table 143: Explanation of the Source Content of an Alarm Message for the pdgPDRRNGLink Object

pdgPDRRNGLink_a.1.1.d. a = Local Zone ID, d = Local Zone pdgPDRRNGLink_56.1.1.56.1.1 is
1.1 ID equal to RNG in Zone 56 to PDR
Link.
The following table lists the state and cause text for the pdgPDRRNGLink object.
Table 144: State/Cause Text for the pdgPDRRNGLink Object

1 DOWN critical 6421 PDR-RNG CONNEC- An RNG has discon-
(1) TION FAILURE nected from the PDR,
or unable to connect to
the PDR. If the RNG
was not disconnected
via local configuration
interface, the PDR will
continuously attempt to
reconnect.
1 DOWN critical 6422 INBOUND INAC- Transitional alarm
(1) TIVITY where PDR has not re-
ceived any inbound da-
ta or loopback respons-
es within a configured
time interval. Hence
PDR will initiate dis-
connect from the RNG.
tween PDR and RNG.
1 DOWN critical 7421 PDR LOST CON- Check connectivity be-
(1) NECTION WITH tween PDR and RNG.
RNG Investigate any accom-
panying alarms. If
alarm persists contact
service personnel.
1 DOWN critical 7422 INBOUND INAC- Transitional alarm
(1) TIVITY where PDR has not re-
Table continued…


ceived any inbound da-
ta or loopback respons-
es within a configured
time interval. Hence
PDR will initiate dis-
connect from the RNG.
tween PDR and RNG.
1 DOWN critical 9998 UNKNOWN CAUSE Check connectivity be-
(1) tween PDR and RNG.
Investigate any accom-
panying alarms. If
alarm persists contact
service personnel.
2 UP nor- 6420 PDR-RNG LINK ES- This is normal system
(6) quired.
2 UP nor- 8420 PDR-RNG LINK ES- This is normal system
(6) quired.
(6) quired.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
Table continued…


vestigate.
vestigate.
state.
pdgPDRRNGSiteLink
pdgPDRRNGSiteLink object.
Table 145: Explanation of the Source Content of an Alarm Message for the pdgPDRRNGSiteLink
Object

pdgPDRRNGSiteLink_a. a = Local Zone ID, d = RF Site ID pdgPDRRNGSiteLink_56.1.1.33 is
1.1.d (EBTS or MTS) equal to RNG in Zone 56 to RF Site
33 Link
The following table lists the state and cause text for the pdgPDRRNGSiteLink object.
Table 146: State/Cause Text for the pdgPDRRNGSiteLink Object

1 DOWN critical 7201 RNG-BASE SITE A Base Site disconnect-
(1) CONNECTION LOST ed from the RNG, or is
unable to connect to the
RNG. If condition per-
sists, check Base Site
status, then check con-
figuration parameters
and communication
links between the RNG
and Base Sites.
1 DOWN critical 8201 RNG-BASE SITE A Base Site disconnect-
(1) CONNECTION LOST ed from the RNG, or is
unable to connect to the
Table continued…


RNG. If condition per-
sists, check Base Site
status, then check con-
figuration parameters
and communication
links between the RNG
and Base Sites.
1 DOWN critical 9998 UNKNOWN CAUSE If condition persists,
(1) then check configura-
tion parameters and
communication links
between the RNG and
Base Sites.
2 UP nor- 7200 RNG-BASE SITE This is normal system
mal LINK IS UP operation. No action re-
(6) quired.
2 UP nor- 9200 RNG-BASE SITE This is normal system
mal LINK IS UP operation. No action re-
(6) quired.
(6) quired.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
Table continued…


vestigate.
vestigate.
state.
pdgPDRRNGZCLink
pdgPDRRNGZCLink object.
Table 147: Explanation of the Source Content of an Alarm Message for the pdgPDRRNGZCLink
Object

pdgPDRRNGZCLink_a. a = Local Zone ID, d = Local Zone pdgPDRRNGZCLink_56.1.1.56 is
1.1.d ID equal to RNG in Zone 56 to Zone
Controller Link
The following table lists the state and cause text for the pdgPDRRNGZCLink object.
Table 148: State/Cause Text for the pdgPDRRNGZCLink Object

1 DOWN critical 7001 RNG-ZC COMMUNI- Number of failed mobi-
(1) CATION FAILED lity queries sent by
RNG to Zone Control-
ler exceeded the prede-
termined threshold.
This could be due to
excessive load on the
Zone Controller, as
well as network fail-
ures. Check network
connections.
1 DOWN critical 8001 RNG-ZC COMMUNI- Number of failed mobi-
(1) CATION FAILED lity queries sent by
RNG to Zone Control-
Table continued…


ler exceeded the prede-
termined threshold.
This could be due to
excessive load on the
Zone Controller, as
ures. Check network
connections.
1 DOWN critical 9998 UNKNOWN CAUSE This could be due to
(1) excessive load on the
Zone Controller, as
ures. Check network
connections.
2 UP nor- 7000 RNG-ZC COMMUNI- A mobility query from
mal CATION SUCCEED- RNG to Zone Control-
(6) ED ler succeeded while the
RNG-ZC link was tag-
ged as disconnected.
No action required.
2 UP nor- 9000 RNG-ZC COMMUNI- A mobility query from
mal CATION SUCCEED- RNG to Zone Control-
RNG-ZC link was tag-
No action required.
(6) quired.
has no knowledge of
companying status
managed object is
known and managed.
Table continued…


vestigate.
vestigate.
vestigate.
state.
pdgPDRZCLink
pdgPDRZCLink object.
Table 149: Explanation of the Source Content of an Alarm Message for the pdgPDRZCLink Object

pdgPDRZCLink_a.1.1.d a = Local Zone ID, d = Local Zone pdgPDRZCLink_56.1.1.56 is equal to
ID PDR in Zone 56 to Zone Controller
Link
The following table lists the state and cause text for the pdgPDRZCLink object.
Table 150: State/Cause Text for the pdgPDRZCLink Object

1 DOWN critical 6001 PDR-ZC COMMUNI- Communication be-
(1) CATION FAILED tween PDR and ZC is
down either because
1).Number of failed
mobility queries sent
by PDR to Zone Con-
troller exceeded the
predetermined thresh-
Table continued…


old. This could be due
to excessive load on the
Zone Controller, as
ures. Check network
connections. OR 2).
Check if multi-cast IP
address is configured
correctly in PDR zone
information config
menu.
1 DOWN critical 7001 PDR-ZC COMMUNI- Communication be-
(1) CATION FAILED tween PDR and ZC is
down either because
1).Number of failed
by PDR to Zone Con-
Zone Controller, as
ures. Check network
connections. OR 2).
information config
menu.
1 DOWN critical 9998 UNKNOWN CAUSE Communication be-
(1) tween PDR and ZC is
down either because
1).Number of failed
by PDR to Zone Con-
Zone Controller, as
ures. Check network
connections. OR 2).
information config
menu.
Table continued…


2 UP nor- 6000 PDR-ZC COMMUNI- A mobility query from
mal CATION SUCCEED- PDR to Zone Control-
PDR-ZC link was tag-
No action required.
2 UP nor- 8000 PDR-ZC COMMUNI- A mobility query from
mal CATION SUCCEED- PDR to Zone Control-
PDR-ZC link was tag-
No action required.
(6) quired.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.
Table continued…


state.
SDR
The following table contains an explanation of source information displayed in the Web NM, Status page for the SDR
object.
Table 151: Explanation of the Source Content of an Alarm Message for the SDR Object

SDR_a.b.c.d a.b.c.d = IP address of the SDR SDR_10.128.105.199 is equal to the
SDR with IP address 10.128.105.199
The following table lists the state and cause texts for the SDR object.
Table 152: State/Cause Text for the SDR Object

1 ACTIVE nor- 5811 SDR STARTED No action required.
mal
(6)
2 STANDBY nor- 5650 SDR READY No action required.
mal
(6)
3 NON REDUNDANT nor- 5805 SDR STARTED This is normal system
(6) quired.
4 OPERATIONALLY minor 5651 SDR DATABASE No action required.
DOWN (3) RETRIEVAL ERROR
4 OPERATIONALLY minor 5652 SDR DATABASE Switchover discour-
DOWN (3) RESTORATION ER- aged. Operator should
ROR investigate the prob-
lem.
4 OPERATIONALLY minor 5653 SDR UNREACHA- No action required.
DOWN (3) BLE
DOWN (3) URE
5 ADMINISTRATIVELY warn- 5654 SDR ADMINISTRA- No action required.
DOWN ing (4) TIVELY DOWN
Table continued…


5 ADMINISTRATIVELY warn- 5655 SDR ADMINISTRA- No action required.
DOWN ing (4) TIVELY DOWN -
UPGRADE
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.
state.
SDRRFSiteLink
SRDRFSiteLink object.

Table 153: Explanation of the Source Content of an Alarm Message for the SRDRFSiteLink Object

SDRRFSiteLink_a.b a = Local Zone ID, b = RF Site ID SDRRFSiteLink_1.3 is equal to
SDR to RF Site 3 (EBTS or MTS)
Link in Zone 1
The following table lists the state and cause texts for the SDRRFSiteLink object.
Table 154: State/Cause Text for the sdrRFLink Object

1 RF SITE CID IS STOP- critical 0 UNKNOWN CAUSE The RF SITE CID
PED (1) failed. If the problem
continues check the site
status and if necessary
stop and then restart the
CID from the SDR
config menu.
1 RF SITE CID IS STOP- critical 5100 OUTBOUND INITI- The SDR failed to send
PED (1) ALIZE CID FAILED the RF SITE Connec-
tion ID initialization
message. Stop and then
restart the RF SITE
CID from SDR config
menu.
1 RF SITE CID IS STOP- critical 5103 START MESSAGE The RF SITE CID start
PED (1) FLOW FAILED message flow transac-
tion failed. Stop and
then restart the RF
SITE CID from SDR
config menu.
1 RF SITE CID IS STOP- critical 5104 ASSIGN REGISTRA- The RF SITE Connec-
PED (1) TION CID FAILED tion ID assign registra-
tion host transaction
failed. Stop and then
restart the RF SITE
CID from SDR config
menu.
1 RF SITE CID IS STOP- critical 5105 ASSIGN CONTROL The RF SITE Connec-
PED (1) CID FAILED tion ID assign control
session transaction
restart the RF SITE
CID from SDR config
menu.
1 RF SITE CID IS STOP- critical 5107 INVALID CID The RF SITE did not
PED (1) STATE return a response to a
CID start-up request
message within the
Table continued…


configured time limit,
but the CID is no lon-
ger in the STARTING
state. Stop and then re-
start the RF SITE CID
from SDR config
menu.
1 RF SITE CID IS STOP- critical 5109 RF SITE CID HAS An RF SITE CID has
PED (1) BEEN STARTED been started. Normal
operation - no action is
required.
1 RF SITE CID IS STOP- critical 5110 RF SITE CID HAS The RF SITE Connec-
PED (1) BEEN STOPPED tion ID has been stop-
ped. If the RF SITE
CID was not stopped
via user command
check site status, restart
the RF SITE CID from
SDR config menu.
1 RF SITE CID IS STOP- critical 5305 TCP CONNECT The TCP/IP connection
PED (1) STATUS CHANGED status has been set suc-
cessfully. Normal oper-
ation - no action re-
quired.
1 RF SITE CID IS STOP- critical 5806 EBTS LINK DIS- Restart the RF SITE
PED (1) COVERED CID from SDR config.
1 RF SITE CID IS STOP- critical 9998 UNKNOWN CAUSE The RF SITE CID
PED (1) failed. If the problem
continues check the site
status and if necessary
stop and the restart the
CID from the SDR
config menu.
2 RF SITE CID IS nor- 0 UNKNOWN CAUSE Stop and then restart
STARTING mal the RF SITE CID from
(6) SDR config.
2 RF SITE CID IS nor- 5100 OUTBOUND INITI- The SDR failed to send
STARTING mal ALIZE CID FAILED the RF SITE CID initi-
(6) alization message. Stop
and then restart the RF
SITE CID from SDR
config.
2 RF SITE CID IS nor- 5103 START MESSAGE The RF SITE CID start
STARTING mal FLOW FAILED message flow transac-
(6) tion failed. Stop and
then restart the RF
SITE CID from SDR
config.
Table continued…


2 RF SITE CID IS nor- 5104 ASSIGN REGISTRA- The RF SITE CID as-
STARTING mal TION CID FAILED sign registration host
(6) transaction failed. Stop
SITE CID from SDR
config.
2 RF SITE CID IS nor- 5105 ASSIGN CONTROL The RF SITE CID as-
STARTING mal CID FAILED sign control session
SITE CID from SDR
config.
2 RF SITE CID IS nor- 5107 INVALID CID An RF SITE did not re-
STARTING mal STATE turn a response to a
(6) CID start-up request
message within the
ger in the STARTING
from SDR config.
2 RF SITE CID IS nor- 5109 RF SITE CID HAS An RF SITE CID has
STARTING mal BEEN STARTED been started. Normal
(6) operation - no action is
required.
STARTING mal BEEN STOPPED been stopped. If the RF
(6) SITE CID was not
stopped via a user com-
mand, restart the RF
SITE CID from SDR
config.
2 RF SITE CID IS nor- 5305 TCP CONNECT The TCP/IP connection
STARTING mal STATUS CHANGED status has been set suc-
(6) cessfully. Normal oper-
quired.
2 RF SITE CID IS nor- 5806 EBTS LINK DIS- No action required.
STARTING mal COVERED
(6)
2 RF SITE CID IS nor- 9998 UNKNOWN CAUSE Stop and then restart
STARTING mal the RF SITE CID from
(6) SDR config.
3 RF SITE CID IS nor- 0 UNKNOWN CAUSE RF SITE CID has been
STARTED mal started. Normal opera-
(6) tion - No action re-
quired.
Table continued…


3 RF SITE CID IS nor- 5100 OUTBOUND INITI- The SDR failed to send
STARTED mal ALIZE CID FAILED the RF SITE CID initi-
(6) alization message. Stop
SITE CID from SDR
config.
3 RF SITE CID IS nor- 5103 START MESSAGE The RF SITE CID start
STARTED mal FLOW FAILED message flow transac-
(6) tion failed. Stop and
then restart the RF
SITE CID from SDR
config.
3 RF SITE CID IS nor- 5104 ASSIGN REGISTRA- The RF SITE CID as-
STARTED mal TION CID FAILED sign registration host
SITE CID from SDR
config.
3 RF SITE CID IS nor- 5105 ASSIGN CONTROL The RF SITE CID as-
STARTED mal CID FAILED sign control session
SITE CID from SDR
config.
3 RF SITE CID IS nor- 5107 INVALID CID An RF SITE did not re-
STARTED mal STATE turn a response to a
(6) CID start-up request
message within the
ger in the STARTING
from SDR config.
3 RF SITE CID IS nor- 5109 RF SITE CID HAS The RF SITE Connec-
STARTED mal BEEN STARTED tion ID has been start-
(6) ed. Normal operation -
No action required.
STARTED mal BEEN STOPPED been stopped. If the RF
(6) SITE CID was not
SITE CID from SDR
config.
3 RF SITE CID IS nor- 5113 CAPABILITYIES RF SITE did not con-
STARTED mal NOT CONFIRMED firmed capability op-
(6) tions sent by SDR. RF
Table continued…


SITE connection is re-
started.
3 RF SITE CID IS nor- 5305 TCP CONNECT The TCP/IP connection
STARTED mal STATUS CHANGED status has been set suc-
(6) cessfully. Normal oper-
quired.
3 RF SITE CID IS nor- 5806 EBTS LINK DIS- The RF SITE Connec-
STARTED mal COVERED tion ID was started due
(6) to SDR-EBTS link be-
ing discovered. Normal
operation - No action
required.
3 RF SITE CID IS nor- 9998 UNKNOWN CAUSE The RF SITE CID has
STARTED mal been started. Normal
(6) operation - No action
required.
4 RF SITE CID IS STOP- critical 0 UNKNOWN CAUSE Stop and then restart
PING (1) the RF SITE CID from
SDR config.
4 RF SITE CID IS STOP- critical 5100 OUTBOUND INITI- The SDR failed to send
PING (1) ALIZE CID FAILED the RF SITE CID initi-
alization message. Stop
SITE CID from SDR
config.
4 RF SITE CID IS STOP- critical 5103 START MESSAGE The RF SITE CID start
PING (1) FLOW FAILED message flow transac-
then restart the RF
SITE CID from SDR
config
4 RF SITE CID IS STOP- critical 5104 ASSIGN REGISTRA- The RF SITE CID as-
PING (1) TION CID FAILED sign registration host
transaction failed. Stop
SITE CID from SDR
config.
4 RF SITE CID IS STOP- critical 5105 ASSIGN CONTROL The RF SITE CID as-
PING (1) CID FAILED sign control transaction
restart the RF SITE
CID from SDR config.
4 RF SITE CID IS STOP- critical 5107 INVALID CID An RF SITE did not re-
PING (1) STATE turn a response to a
message within the
Table continued…


ger in the STARTING
from SDR config.
PING (1) BEEN STARTED been started. Normal
required.
PING (1) BEEN STOPPED been stopped. If the RF
SITE CID was not
SITE CID from SDR
config.
4 RF SITE CID IS STOP- critical 5305 TCP CONNECT The TCP/IP connection
PING (1) STATUS CHANGED status has been set suc-
quired.
4 RF SITE CID IS STOP- critical 5806 EBTS LINK DIS- Restart the RF SITE
PING (1) COVERED CID from SDR config.
4 RF SITE CID IS STOP- critical 9998 UNKNOWN CAUSE Stop and then restart
PING (1) the RF SITE CID from
SDR config.
5 RF SITE CID STATE critical 0 UNKNOWN CAUSE Stop and then restart
UNKNOWN (1) the RF SITE CID from
SDR config.
5 RF SITE CID STATE critical 5100 OUTBOUND INITI- The SDR failed to send
UNKNOWN (1) ALIZE CID FAILED the RF SITE CID initi-
alization message. Stop
SITE CID from SDR
config.
5 RF SITE CID STATE critical 5103 START MESSAGE The RF SITE CID start
UNKNOWN (1) FLOW FAILED message flow transac-
then restart the RF
SITE CID from SDR
config.
5 RF SITE CID STATE critical 5104 ASSIGN REGISTRA- The RF SITE CID as-
UNKNOWN (1) TION CID FAILED sign registration host
Table continued…


SITE CID from SDR
config.
5 RF SITE CID STATE critical 5105 ASSIGN CONTROL The RF SITE CID as-
UNKNOWN (1) CID FAILED sign control session
SITE CID from SDR
config.
5 RF SITE CID STATE critical 5107 INVALID CID An RF SITE did not re-
UNKNOWN (1) STATE turn a response to a
message within the
ger in the STARTING
from SDR config.
5 RF SITE CID STATE critical 5109 RF SITE CID HAS An RF SITE CID has
UNKNOWN (1) BEEN STARTED been started. Normal
required.
5 RF SITE CID STATE critical 5110 RF SITE CID HAS An RF SITE CID has
UNKNOWN (1) BEEN STOPPED been stopped. If the RF
SITE CID was not
SITE CID from SDR
config.
5 RF SITE CID STATE critical 5305 TCP CONNECT The TCP/IP connection
UNKNOWN (1) STATUS CHANGED status has been set suc-
quired.
5 RF SITE CID STATE critical 5806 EBTS LINK DIS- No action required.
UNKNOWN (1) COVERED
5 RF SITE CID STATE critical 9998 UNKNOWN CAUSE Stop and then restart
UNKNOWN (1) the RF SITE CID from
SDR config.
has no knowledge of
companying status
Table continued…


managed object is
known and managed.
vestigate.
vestigate.
vestigate.
state.
SDRMStoGroup
sdrMStoGroup object.
Table 155: Explanation of the Source Content of an Alarm Message for the sdrMStoGroup Object

sdrMStoGroup_a a = SDR ID MStoGroup_1 is equal to MS-to-
Group functionality on SDR 1
The following table lists the state and cause text for the sdrMStoGroup object.

Table 156: State/Cause Text for the sdrMStoGroup Object

1 ACTIVE nor- 0 UNKNOWN CAUSE If alarm persists contact
(6)
1 ACTIVE nor- 6900 GMS STARTED No action required.
mal
(6)
(6)
2 ADMINISTRATIVELY warn- 0 UNKNOWN CAUSE If alarm persists contact
DOWN ing (4) service personnel.
2 ADMINISTRATIVELY warn- 6901 GMS ADMINISTRA- MStoGroup service has
DOWN ing (4) TIVELY DOWN been administratively
disabled. No action re-
quired.
3 OPERATIONALLY critical 0 UNKNOWN CAUSE If alarm persists contact
DOWN (1) service personnel.
3 OPERATIONALLY critical 6902 GMS OPERATION- MStoGroup is not op-
DOWN (1) ALLY DOWN erational. Configure
MStoGroup service on
SDR.
has no knowledge of
companying status
managed object is
known and managed.
Table continued…


vestigate.
vestigate.
vestigate.
StoreAndForward
StoreAndForward object.
Table 157: Explanation of the Source Content of an Alarm Message for the StoreAndForward Object

StoreAndForward_a a = SDR ID StoreAndForward_1 is equal to Store
and Forward on SDR 1
The following table lists the state and cause text for the StoreAndForward object.
Table 158: State/Cause Text for the sdrStoreAndForward Object

(6)
1 ACTIVE nor- 6850 SF STARTED No action required.
mal
(6)
(6)
Table continued…


2 ADMINISTRATIVELY warn- 6851 SF ADMINISTRA- StoreAndForward serv-
DOWN ing (4) TIVELY DOWN ice has been adminis-
tratively disabled. No
action required.
3 OPERATIONALLY critical 6852 SF OPERATIONAL- StoreAndForward is
DOWN (1) LY DOWN not operational. Con-
figure StoreAndFor-
ward service on SDR.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
Table continued…


vestigate.
SDR->HLR
SDR->HLR object.
Table 159: Explanation of the Source Content of an Alarm Message for the SDR->HLR Object

SDR->HLR_a a = Local Zone ID SDR->HLR_1 is equal to the link
from the SDR to the HLR on Zone
Controller Zone 1
The following table lists the state and cause texts for the SDR->HLR object.
Table 160: State/Cause Text for the sdrZCHLRLink Object

1 ZC HLR CONNECTED nor- 0 UNKNOWN CAUSE This is normal system
(6) quired.
1 ZC HLR CONNECTED nor- 6501 ZC HLR LINK CON- This is normal system
mal NECTED operation. No action re-
(6) quired.
1 ZC HLR CONNECTED nor- 9998 UNKNOWN CAUSE This is normal system
(6) quired.
2 ZC HLR DISCON- critical 0 UNKNOWN CAUSE Multicast IP traffic is
NECTED (1) routed between the ZCs
and SDR for this link to
be up. Check IP net-
work multicast routing
setup in the Zone Con-
troller Interface in the
SDR config menu and
tions.
Table continued…


2 ZC HLR DISCON- critical 6500 ZC HLR LINK DIS- Multicast IP traffic is
NECTED (1) CONNECTED routed between the ZCs
SDR config menu and
tions.
2 ZC HLR DISCON- critical 9998 UNKNOWN CAUSE Multicast IP traffic is
SDR config menu and
tions.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
Table continued…


vestigate.
state.
SDR->VLR
SDR->VLR object.
Table 161: Explanation of the Source Content of an Alarm Message for the SDR->VLR Object

SDR->VLR_a a = Local Zone ID SDR->VLR_1 is equal to the link
from the SDR to the VLR on Zone
Controller 1
The following table lists the state and cause texts for the SDR->VLR object.
Table 162: State/Cause Text for the SDR->VLR Object

1 ZC VLR CONNECTED nor- 0 UNKNOWN CAUSE This is normal system
(6) quired.
1 ZC VLR CONNECTED nor- 6509 ZC VLR LINK CON- This is normal system
mal NECTED operation. No action re-
(6) quired.
1 ZC VLR CONNECTED nor- 9998 UNKNOWN CAUSE This is normal system
(6) quired.
2 ZC VLR DISCON- critical 0 UNKNOWN CAUSE Multicast IP traffic is
Table continued…


SDR config menu and
tions.
2 ZC VLR DISCON- critical 6508 ZC VLR LINK DIS- Multicast IP traffic is
NECTED (1) CONNECTED routed between the ZCs
SDR config menu and
tions.
2 ZC VLR DISCON- critical 9998 UNKNOWN CAUSE Multicast IP traffic is
SDR config menu and
tions.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
Table continued…


vestigate.
vestigate.
state.
UCS01
UCS01 object.
Table 163: Explanation of the Source Content of an Alarm Message for the UCS01 Object

UCS01 n/a Fixed name
The following table lists the state and cause text for the UCS01 object.
Table 164: State/Cause Text for the UCS01 Object

0 UNKNOWN warn- 0 NO FAN MGR. DIS- Please check the status
ing (4) ABLED of the server. If this sit-
uation remains contact
Motorola support.
node to manager or
Table continued…


nel to investigate.
1 UNCONFIGURED warn- 0 NO FAN MGR. DIS- Alarm determined node
ing (4) ABLED was in unconfigured
gate.
1 UNCONFIGURED warn- 1000 NO REASON Alarm determined node
gate.
gate.
10 SHUTTING DOWN warn- 0 NO FAN MGR. DIS- The server was shut-
ing (4) ABLED down. No action re-
Table continued…


User Requested.
10 SHUTTING DOWN warn- 10000 NO AC MGR. DISA- The server was shut-
ing (4) BLED down. No action re-
User Requested.
10 SHUTTING DOWN warn- 9998 UNKNOWN CAUSE The server was shut-
ing (4) down. No action re-
User Requested.
User Requested.
User Requested.
User Requested.
12 SHUTDOWN critical 12003 USER REQUESTED State change caused by
tion.
tion.
2 DISABLED major 0 NO FAN MGR. DIS- The server was disa-
(2) ABLED bled. No action re-
User Requested.
2 DISABLED major 2000 NO REASON Server is disabled. No
(2) action required if disa-
ble was User Request-
ed.
sonnel.
Table continued…


3 ENABLED nor- 0 NO FAN MGR. DIS- This is normal system
mal ABLED operation. No action re-
user initiated.
3 ENABLED nor- 1 UCS DISABLING Transition state. No ac-
mal tion required.
(6)
user initiated.
3 ENABLED nor- 3001 UNKNOWN US This is normal system
mal STATUS operation. No action re-
(6) quired.
user initiated.
4 RECONNECTED nor- 0 NO FAN MGR. DIS- No action required.
mal ABLED
(6)
4 RECONNECTED nor- 4000 NO REASON No action required.
mal
(6)
4 RECONNECTED nor- 9998 UNKNOWN CAUSE No action required.
mal
(6)
5 ENABLING warn- 0 NO FAN MGR. DIS- The server is enabling.
ing (4) ABLED Transitory state. No ac-
tion required if enable
was User Requested.
5 ENABLING warn- 1 UCS DISABLING The server is enabling.
ing (4) Transitory state. No ac-
was User Requested.
5 ENABLING warn- 2 US DISABLING The server is enabling.
was User Requested.
5 ENABLING warn- 5000 NO REASON The server is enabling.
was User Requested.
5 ENABLING warn- 5001 UCS ENABLING The server is enabling.
Table continued…


was User Requested.
5 ENABLING warn- 5002 US ENABLING The server is enabling.
was User Requested.
5 ENABLING warn- 9998 UNKNOWN CAUSE The server is enabling.
was User Requested.
has no knowledge of
companying status
managed object is
known and managed.
6 ON BATTERY critical 0 NO FAN MGR. DIS- Probably power supply
(1) ABLED problem occurred.
Server is on auxiliary
power (UPS). Investi-
gate power supply con-
dition.
6 ON BATTERY critical 6000 NO REASON Probably power supply
(1) problem occurred.
dition.
6 ON BATTERY critical 9998 UNKNOWN CAUSE Probably power supply
dition.
7 DISABLING warn- 0 NO FAN MGR. DIS- The server is disabling.
tion required if shut-
down was User Re-
quested.
Table continued…


7 DISABLING warn- 1 UCS DISABLING The node is disabling.
abled. In case node
7 DISABLING warn- 2 US DISABLING The node is disabling.
abled. In case node
7 DISABLING warn- 7000 NO REASON The node is disabling.
abled. In case node
abled. In case node
abled. In case node
Table continued…


abled. In case node
User Requested.
8 SHUTTING DOWN warn- 8000 NO AC The server was shut-
User Requested.
User Requested.
User Requested.
9 SHUTTING DOWN warn- 9000 NO FAN The server was shut-
User Requested.
User Requested.
vestigate.
vestigate.
Table continued…


vestigate.
state.
ZC1/M
ZC1/M object.
Table 165: Explanation of the Source Content of an Alarm Message for the ZC1/M Object

ZC1/M n/a Fixed name
The following table lists the state and cause text for the ZC1/M object.
Table 166: State/Cause Text for the ZC1/M Object

Motorola support.
node to manager or
nel to investigate.
Table continued…


gate.
gate.
gate.
User Requested.
Table continued…


User Requested.
User Requested.
User Requested.
User Requested.
User Requested.
tion.
tion.
User Requested.
ed.
sonnel.
user initiated.
Table continued…


mal tion required.
(6)
user initiated.
(6) quired.
user initiated.
mal ABLED
(6)
mal
(6)
mal
(6)
was User Requested.
was User Requested.
was User Requested.
was User Requested.
was User Requested.
Table continued…


was User Requested.
was User Requested.
has no knowledge of
companying status
managed object is
known and managed.
dition.
dition.
dition.
down was User Re-
quested.
Table continued…


abled. In case node
abled. In case node
abled. In case node
abled. In case node
abled. In case node
Table continued…


abled. In case node
User Requested.
User Requested.
User Requested.
User Requested.
User Requested.
User Requested.
vestigate.
vestigate.
Table continued…


vestigate.
state.
ZC-CCGW CP
The following table contains an explanation of source information displayed in the Web NM, Status page for the ZC-
CCGW CP object.
Table 167: Explanation of the Source Content of an Alarm Message for the ZC-CCGW CP Object

ZC-CCGW CP_1.b.c.d b = Analog Conventional Site ID, c ZC-CCGW CP_1.2001.1.1 is equal
= CCGW ID, d = Zone Controller ID to the link from Zone Controller 1 to
CCGW 1 on Analog Conventional
Site 2001
The following table lists the state and cause texts for the ZC-CCGW CP object.
Table 168: State/Cause Text for the ZcCcgwCp Object

(6) quired.
3 DOWN critical 3004 NO ACTIVITY RE- This is a possible hard-
(1) CEIVED ware or connection
problem
3 DOWN critical 3005 TRANSMIT RETRY This is a possible hard-
(1) FAILURE ware or connection
problem
tion.
has no knowledge of
Table continued…


companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.
state.
ZcConsoleSCP
ZcConsoleSCP object.
Table 169: Explanation of the Source Content of an Alarm Message for the ZcConsoleSCP Object

ConsoleSiteControl- a = Console Site ID, b = Control Path ConsoleSiteControlPath_3.2
Path_a.b Number
The following table lists the state and cause text for the ZcConsoleSCP object.

Table 170: State/Cause Text for the ZcConsoleSCP Object

(6) quired.
(6) quired.
(6) quired.
2 DEGRADED warn- 2 BOTH LINKS ON ZC Console Site Con-
ing (4) CONTROL INTER- trol Path indicated has
FACE 1 degraded. Check net-
work connectivity to
site and networking
components. Contact
alarm persists.
site and networking
components. Contact
alarm persists.
site and networking
components. Contact
alarm persists.
site and networking
components. Contact
alarm persists.
2 DEGRADED warn- 9998 UNKNOWN CAUSE ZC Console Site Con-
ing (4) trol Path indicated has
degraded. Check net-
site and networking
Table continued…


components. Contact
alarm persists.
3 DOWN critical 3004 NO ACTIVITY RE- ZC Console Site Con-
(1) CEIVED trol Path indicated is
down. Check network
connectivity to site and
networking compo-
nents. Contact service
personnel if alarm per-
sists.
3 DOWN critical 3005 TRANSMIT RETRY ZC Console Site Con-
(1) FAILURE trol Path indicated is
down. Check network
networking compo-
sists.
3 DOWN critical 3006 INTERFACE RE- ZC Console Site Con-
(1) COVERY trol Path indicated is
down. Check network
networking compo-
sists.
3 DOWN critical 3007 INTERFACE FAIL- ZC Console Site Con-
(1) URE trol Path indicated is
down. Check network
networking compo-
sists.
3 DOWN critical 4 NO ACTIVITY RE- ZC Console Site Con-
(1) CEIVED trol Path indicated is
down. Check network
networking compo-
sists.
3 DOWN critical 5 TRANSMIT RETRY ZC Console Site Con-
(1) FAILURE trol Path indicated is
down. Check network
networking compo-
Table continued…


sists.
3 DOWN critical 6 INTERFACE RE- ZC Console Site Con-
(1) COVERY trol Path indicated is
down. Check network
networking compo-
sists.
3 DOWN critical 7 INTERFACE FAIL- ZC Console Site Con-
(1) URE trol Path indicated is
down. Check network
networking compo-
sists.
3 DOWN critical 9998 UNKNOWN CAUSE ZC Console Site Con-
(1) trol Path indicated is
down. Check network
networking compo-
sists.
4 NOT IN USE warn- 4008 CONSOLE DISCON- ZC Console Site Con-
ing (4) NECT trol Path indicated is
not in use. Cause re-
ported is that console
has disconnected.
Check console discon-
nection is user intended
otherwise check net-
site, networking com-
ponents and Console
configuration. Contact
alarm persists.
4 NOT IN USE warn- 8 CONSOLE DISCON- ZC Console Site Con-
ing (4) NECT trol Path indicated is
ported is that console
has disconnected.
Check console discon-
nection is user intended
otherwise check net-
Table continued…


site, networking com-
ponents and Console
configuration. Contact
alarm persists.
4 NOT IN USE warn- 9998 UNKNOWN CAUSE ZC Console Site Con-
ing (4) trol Path indicated is
ported as unknown.
Check if console dis-
connection was per-
formed otherwise
tivity to site, network-
ing components and
Console configuration.
tion.
tion.
5 UNCONFIGURED critical 9998 UNKNOWN CAUSE Alarm determined node
gate.
has no knowledge of
companying status
Table continued…


managed object is
known and managed.
vestigate.
vestigate.
vestigate.
state.
ZcMobilityLink
ZcMobilityLink object.
Table 171: Explanation of the Source Content of an Alarm Message for the ZcMobilityLink Object

ZcMobilityLink_a a = Link ID ZcMobilityLink_1 is equal to mobili-
ty link 1
The following table lists the state and cause texts for the ZcMobilityLink object.

Table 172: State/Cause Text for the ZcMobilityLink Object

1 UP nor- 1001 NO REASON ZC Mobility Link indi-
mal cated is up. No action
(6) required if user request-
vestigate.
2 DOWN critical 2002 INTERFACE FAIL- ZC Mobility Link indi-
(1) URE cated is down. Check
network connectivity
and networking compo-
sists.
tion.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
Table continued…


vestigate.
ZcMtigLink
ZcMtigLink object.
Table 173: Explanation of the Source Content of an Alarm Message for the ZcMtigLink Object

ZcMtigLink_a.1 a = MTIG ID ZcMtigLink_1.1 is equal to Zone
Controller to MTIG 1 link
The following table lists the state and cause text for the ZcMtigLink object.
Table 174: State/Cause Text for the ZcMtigLink Object

1 UNKNOWN critical 1001 NO REASON ZC - MTIG link un-
(1) known. Check connec-
tivity between ZC and
MTIG and box config-
uration. Contact service
sists.
gate.
Table continued…


3 UP nor- 3002 ZC-MTIG CONTROL This is normal system
mal LINK RECOVERED operation. No action re-
(6) quired.
4 DOWN warn- 4001 NO REASON ZC - MTIG link down.
ing (4) Check connectivity be-
tween ZC and MTIG
and box configuration.
4 DOWN warn- 4003 ZC-MTIG NETCOM ZC - MTIG link down.
ing (4) LINK DOWN Check connectivity be-
tween ZC and MTIG
4 DOWN warn- 4004 ZC-MTIG TCP LINK ZC - MTIG link down.
ing (4) DOWN Check connectivity be-
tween ZC and MTIG
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
Table continued…


vestigate.
state.
ZcMtsSite
ZcMtsSite object.
Table 175: Explanation of the Source Content of an Alarm Message for the ZcMtsSite Object

ZcMtsSite ZcAlias , Alias is the alias name for Mts ZcMTS1– where MTS1 is the
Site alias name for added Mts Site.
The following table lists the state and cause text for the ZcMtsSite object.
Table 176: State/Cause Text for the ZcMtsSite Object

1 UNKNOWN critical 1001 NO REASON Mts site indicated is
(1) unknown. Investigate
accompanying alarms
and Mts site. Contact
alarm persists.
node to manager or
Table continued…


nel to investigate.
101 NOT WIDE TRUNK- critical 101004 NO VOICE CHAN- No voice channels are
ING (1) NEL available at the site and
therefore the site is un-
able to operate in
trunking mode. This
can be seen while the
site is transitioning into
the normal trunking
mode. If the state per-
sists it may indicates
that either the Base Ra-
dio(s) has failed or the
has failed. Contact
further investigation re-
quired to identify the
root cause.
101 NOT WIDE TRUNK- critical 101005 NO CONTROL No control channel is
ING (1) CHANNEL currently available at
the site. Without the
control channel the site
is unable to operate in
trunking mode. This is
caused by the failure of
the Base Radio carry-
ing the control channel.
101 NOT WIDE TRUNK- critical 101006 SITE CONTROL The connection (Net-
ING (1) PATH DOWN com) to the site is
down. This can be due
to a negotiation issue
between site and ZC.
Check the site view on
the site status.
101 NOT WIDE TRUNK- critical 101007 USER REQUESTED State change caused by
ING (1) a user initiated opera-
tion.
101 NOT WIDE TRUNK- critical 101008 RECOVERY The site is in the proc-
ING (1) ess of recovery before
101 NOT WIDE TRUNK- critical 101011 NO CORE ROUTER The site might be in the
ING (1) process of recovery. If
it might be due to Base
Table continued…


Radio failures. Contact
vestigate.
101 NOT WIDE TRUNK- critical 9998 UNKNOWN CAUSE The site might be in the
ING (1) process of recovery. If
it might be due to Base
Radio failures. Contact
vestigate.
has no knowledge of
companying status
managed object is
known and managed.
71 WIDE TRUNKING nor- 71001 NO REASON This is normal system
(6) quired if user request-
ed.
71 WIDE TRUNKING nor- 71006 USER REQUESTED State change caused by
quired.
71 WIDE TRUNKING nor- 9998 UNKNOWN CAUSE This is normal system
(6) quired.
vestigate.
Table continued…


vestigate.
vestigate.
state.
ZcOperationalHealth
ZcOperationalHealth object.
Table 177: Explanation of the Source Content of an Alarm Message for the ZcOperationalHealth
Object

ZcOperationalHealth_a.1 a = Zone Controller ID ZcOperationalHealth_1.1 is equal to
operational health on Zone Control-
ler 1
The following table lists the state and cause texts for the ZcOperationalHealth object.
Table 178: State/Cause Text for the ZcOpState Object

2 NORMAL nor- 1 NO REASON This is normal system
(6) quired.
2 NORMAL nor- 2001 NO REASON This is normal system
(6) quired.
2 NORMAL nor- 9998 UNKNOWN CAUSE This is normal system
(6) quired.
3 STABLE minor 3002 SERIAL SWITCH Log in as admin and
Table continued…


3 STABLE minor 3003 ASYNC CARD FAIL- Log in as admin and
(3) URE check the component
3 STABLE minor 3004 ETHERNET CARD Log in as admin and
3 STABLE minor 3006 HARD DISK FAIL- Log in as admin and
spect the Hard Disk
ware.
3 STABLE minor 3007 POWER SUPPLY Log in as admin and
3 STABLE minor 3009 VOLTAGE THRESH- Log in as admin and
3 STABLE minor 3010 TEMPERATURE Investigate temperature
(3) THRESHOLD VIO- of local environment
LATION where node is located
and rectify any temper-
ature violation. Log in
as admin and check the
component states. This
is a possible hardware
failure.
3 STABLE minor 3011 FAN FAILURE Log in as admin and
3 STABLE minor 4 ETHERNET CARD Log in as admin and
3 STABLE minor 6 HARD DISK FAIL- Log in as admin and
Table continued…


spect the Hard Disk
ware.
3 STABLE minor 7 POWER SUPPLY Log in as admin and
3 STABLE minor 9998 UNKNOWN CAUSE Log in as admin and
4 FAILING major 1 NO REASON The device is reported
(2) as failing. The no rea-
son cause is only sent
when the given compo-
nent is not able to iden-
tify the reason e.g. after
a start up after a reset.
Accordingly, the repair
action will fully depend
on the state entered. If
the state entered is un-
reachable/ unknown
nently then contact
inspection and possible
replacement.
4 FAILING major 4001 NO REASON The device is reported
(2) as failing. The no rea-
son cause is only sent
when the given compo-
nent is not able to iden-
tify the reason e.g. after
a start up after a reset.
Accordingly, the repair
action will fully depend
on the state entered. If
the state entered is un-
reachable/ unknown
nently then contact
replacement.
4 FAILING major 9998 UNKNOWN CAUSE The device is reported
(2) as failing. The un-
Table continued…


known cause is only
sent when the given
fully depend on the
reachable/ unknown
nently then contact
replacement.
5 INOPERABLE critical 10 TEMPERATURE Investigate temperature
failure.
5 INOPERABLE critical 11 FAN FAILURE Log in as admin and
5 INOPERABLE critical 4 ETHERNET CARD Log in as admin and
5 INOPERABLE critical 5002 SERIAL SWITCH Log in as admin and
5 INOPERABLE critical 5003 ASYNC CARD FAIL- Log in as admin and
5 INOPERABLE critical 5004 ETHERNET CARD Log in as admin and
5 INOPERABLE critical 5005 SYNC CARD FAIL- Log in as admin and
Table continued…


5 INOPERABLE critical 5008 ZONE ID FAILURE ZC operational state is
(1) inoperable. Alarm
should appear only
where some System In-
tegration/Configuration
has gone wrong but not
in normal operation.
Contact Motorola sup-
port.
5 INOPERABLE critical 5009 VOLTAGE THRESH- Log in as admin and
5 INOPERABLE critical 5010 TEMPERATURE Investigate temperature
failure.
5 INOPERABLE critical 5011 FAN FAILURE Log in as admin and
5 INOPERABLE critical 8 ZONE ID FAILURE ZC operational state is
(1) inoperable. Alarm
should appear only
where some System In-
tegration/Configuration
has gone wrong but not
in normal operation.
Contact Motorola sup-
port.
5 INOPERABLE critical 9 VOLTAGE THRESH- Log in as admin and
5 INOPERABLE critical 9998 UNKNOWN CAUSE Log in as admin and
Table continued…


nate ing related or transitory
(5) state or Fault Manager
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.
state.
ZDS
The following table contains an explanation of source information displayed in the Web NM, Status page for the ZDS
object.
Table 179: Explanation of the Source Content of an Alarm Message for the ZDS Object

ZDS n/a Fixed name
The following table lists the state and cause text for the ZDS object.

Table 180: State/Cause Text for the ZDS Object

Motorola support.
node to manager or
nel to investigate.
gate.
gate.
Table continued…


gate.
User Requested.
User Requested.
User Requested.
User Requested.
User Requested.
User Requested.
tion.
tion.
Table continued…


User Requested.
ed.
sonnel.
user initiated.
mal tion required.
(6)
user initiated.
(6) quired.
user initiated.
mal ABLED
(6)
mal
(6)
mal
(6)
was User Requested.
Table continued…


was User Requested.
was User Requested.
was User Requested.
was User Requested.
was User Requested.
was User Requested.
has no knowledge of
companying status
managed object is
known and managed.
dition.
Table continued…


dition.
dition.
down was User Re-
quested.
abled. In case node
abled. In case node
abled. In case node
Table continued…


abled. In case node
abled. In case node
abled. In case node
User Requested.
User Requested.
User Requested.
User Requested.
User Requested.
User Requested.
Table continued…


vestigate.
vestigate.
vestigate.
state.
Zone
The following table contains an explanation of source information displayed in the Web NM, Status page for the Zone
object.
Table 181: Explanation of the Source Content of an Alarm Message for the Zone Object

The alias assigned to the Zone ob- n/a Since this is an object to which an alias
ject is assigned the source information is a
The following table lists the state and cause texts for the Zone object.
Table 182: State/Cause Text for the Zone Object

0 UNKNOWN warn- 0 NO REASON Alarm state from object
Table continued…


gate network connec-
tivity to manager or
nel to investigate.
node to manager or
nel to investigate.
11 NOT IZ TRUNKING major 11001 NO LOCAL IND ID Local Zone reported
CAP (2) MAP not being IZ Trunking
capable. Cause of state
change was No IND ID
map in effect. Check
active ZC status from
Home Zone Map Proc-
essing Status in User
Configuration Manag-
er. Ensure a valid
Home Zone Map is
submitted and contact
alarm persists.
11 NOT IZ TRUNKING major 11002 NO LOCAL TG ID Local Zone reported IZ
CAP (2) MAP Trunking capable.
Cause of state change
was no IND ID map in
effect in local zone.
Check active ZC status
from Home Zone Map
Processing Status in
User Configuration
Manager.
11 NOT IZ TRUNKING major 11004 LOCAL USER RE- Local Zone reports IZ
CAP (2) QUEST Trunking. Cause of
state change was No
Table continued…


IND ID map in effect
in zone. Check active
ZC status from Home
Zone Map Processing
Status in UCM.
11 NOT IZ TRUNKING major 11009 NO ZONE ID Zone not capable of in-
CAP (2) ter-zone trunking.
Check ZC status from
Home Zone Map Proc-
essing Status in UCM.
No Zone ID Cause in-
dicates configuration/
commissioning/initiali-
sation issue - check ac-
or status alarms or final
state or if alarm persists
nel to investigate.
11 NOT IZ TRUNKING major 11014 NO LOCAL CORE Remote Zone reported
CAP (2) RP IZ Trunking capable.
Cause of state change
from Home Zone Map
User Configuration
Manager.
11 NOT IZ TRUNKING major 9998 UNKNOWN CAUSE Zone not capable of in-
CAP (2) ter-zone trunking. If
reason was not that
SAC download was
performed (to the ac-
tive ZC) or that the link
is down, then investi-
gate.
12 NO IZ TRUNKING major 12002 NO LOCAL TG ID Local Zone reported no
(2) MAP IZ trunking. Cause of
state change was No
TG ID map in effect.
from Home Zone Map
User Configuration
Manager.
12 NO IZ TRUNKING major 12003 NO IZ AUDIO PATH Local Zone reported no
(2) IZ Trunking. Cause of
state change was no IZ
Table continued…


audio path. Check ac-
companying alarms and
nel to investigate. Mon-
itor Home Zone Map
processing status from
User Configuration
Manager.
12 NO IZ TRUNKING major 12004 LOCAL USER RE- State change caused by
(2) QUEST a user initiated opera-
tion.
12 NO IZ TRUNKING major 12005 NO IZ DATA COMM Zone is not Inter-Zone
(2) trunking. Check Inter-
Zone network connec-
tivity and Zone Con-
troller status. If alarm
gate.
12 NO IZ TRUNKING major 12006 NO REMOTE IND ID Local Zone reports IZ
(2) MAP Trunking. Cause of
state change was re-
ported as No IND ID
accompanying alarms
and check the Home
Zone Map Processing
Status from User Con-
figuration Manager and
confirm IZ Trunking
capability transitions as
expected.
12 NO IZ TRUNKING major 12007 NO REMOTE TG ID Local Zone reports No
(2) MAP IZ Trunking. Cause of
state change was re-
ported as No TG ID
map in effect in remote
zone. Check ZC status
from Home Zone Map
UCM.
12 NO IZ TRUNKING major 12008 REMOTE USER RE- State change caused by
(2) QUEST a user initiated opera-
tion.
12 NO IZ TRUNKING major 12009 NO ZONE ID Check ZC status from
(2) Home Zone Map Proc-
essing Status in UCM.
No Zone ID Cause in-
dicates configuration/
Table continued…


commissioning/initiali-
sation issue - check ac-
or status alarms or final
state or if alarm persists
nel to investigate.
12 NO IZ TRUNKING major 12014 NO LOCAL CORE Local Zone reported no
(2) RP IZ Trunking. Cause of
state change was no lo-
cal core rendezvous
point. Check accompa-
nying alarms and moni-
tor Zone status from
Home Zone Map proc-
essing status from User
er. Contact service per-
sonnel if alarm persists.
12 NO IZ TRUNKING major 12015 NO REMOTE CORE Local Zone reported no
(2) RP IZ Trunking. Cause of
state change was no re-
mote core rendezvous
point. Check accompa-
nying alarms and moni-
tor Zone status from
Home Zone Map proc-
essing status from User
er. Contact service per-
sonnel if alarm persists.
12 NO IZ TRUNKING major 12016 MISMATCH TG CZ Local Zone reported no
(2) MAPS IZ Trunking. Cause of
state change was mis-
match detected be-
tween Talkgroup map
of controlling zone.
Check Home Zone
Maps are not mis-
matched between clus-
ters. Monitor Home
Zone Map processing
status from User Con-
figuration Manager.
12 NO IZ TRUNKING major 9998 UNKNOWN CAUSE Loss of Inter-Zone
(2) trunking. If reason was
not that SAC download
was performed (to the
active ZC) or that the
Table continued…


link is down, then in-
vestigate.
13 IZ TRUNKING CAPA- nor- 13000 NO REASON Local Zone reported IZ
BLE mal Trunking capable.
(6) Cause of state change
was unknown. Check
Home Zone Map Proc-
er.
13 IZ TRUNKING CAPA- nor- 13001 NO LOCAL IND ID Local Zone reported IZ
BLE mal MAP Trunking capable.
from Home Zone Map
User Configuration
Manager.
13 IZ TRUNKING CAPA- nor- 9998 UNKNOWN CAUSE Local Zone reported IZ
BLE mal Trunking capable.
was unknown. Check
Home Zone Map Proc-
er.
14 IZ TRUNKING nor- 14000 NO REASON Local Zone reports IZ
mal Trunking. Cause of
(6) state change was un-
known. Check active
ZC status from Home
Zone Map Processing
Status in UCM.
14 IZ TRUNKING nor- 14001 NO LOCAL IND ID Local Zone reports IZ
mal MAP Trunking. Cause of
(6) state change was No
IND ID map in effect
in zone. Check active
ZC status from Home
Zone Map Processing
Status in UCM.
14 IZ TRUNKING nor- 14006 NO REMOTE IND ID Local Zone reports IZ
mal MAP Trunking. Cause of
(6) state change was re-
ported as No IND ID
Table continued…


accompanying alarms
and check the Home
Zone Map Processing
Status from User Con-
figuration Manager and
confirm IZ Trunking
capability transitions as
expected.
14 IZ TRUNKING nor- 14010 IZDP 1 CONFIG Local Zone reports IZ
mal Trunking. Check ac-
(6) companying alarms and
Home Zone Map Proc-
essing Status in UCM
transitions as expected.
14 IZ TRUNKING nor- 14011 IZDP 2 CONFIG Local Zone reports IZ
Home Zone Map Proc-
14 IZ TRUNKING nor- 14012 IZDP 1 DOWN Local Zone reports IZ
Home Zone Map Proc-
14 IZ TRUNKING nor- 14013 IZDP 2 DOWN Local Zone reports IZ
Home Zone Map Proc-
14 IZ TRUNKING nor- 14017 MISMATCH IND ID Home Zone Mapping
mal MAPS mismatch detected.
(6) HZMs should be same
across all Clusters and
submitted with the
same Date / Time pa-
rameters. Check HZM
status from UCM
across clusters.
14 IZ TRUNKING nor- 9998 UNKNOWN CAUSE Local Zone reports IZ
mal Trunking. Cause of
(6) state change was un-
Table continued…


known. Check accom-
panying alarms and
check the Home Zone
Map Processing Status
from User Configura-
tion Manager and con-
firm IZ Trunking capa-
bility transitions as ex-
pected.
has no knowledge of
companying status
managed object is
known and managed.
vestigate.
vestigate.
vestigate.
Table continued…


state.
ZoneContlr
ZoneContlr object.
Table 183: Explanation of the Source Content of an Alarm Message for the ZoneContlr Object

The alias assigned to the Zone- n/a Since this is an object to which an
Contlr object alias is assigned the source informa-
tion is a user determined setting
The following table lists the state and cause texts for the ZoneContlr object.
Table 184: State/Cause Text for the ZoneCntlr Object

0 UNKNOWN critical 0 NO REASON Alarm state from object
gate network connec-
tivity to manager or
nel to investigate.
node to manager or
Table continued…


nel to investigate.
11 LOADING ACTIVE warn- 11000 NO REASON This is normal system
ing (4) operation during SAC
download to the ZC or
ZC initialization. It is a
transitory state and
should transition to En-
abled Active.
11 LOADING ACTIVE warn- 9998 UNKNOWN CAUSE This is normal system
abled Active.
12 LOADING IDLE warn- 12000 NO REASON This is normal system
abled Idle.
12 LOADING IDLE warn- 9998 UNKNOWN CAUSE This is normal system
abled Idle.
13 RELOADING ACTIVE warn- 13000 NO REASON This is normal system
abled Active.
13 RELOADING ACTIVE warn- 9998 UNKNOWN CAUSE This is normal system
abled Active.
14 RELOADING IDLE warn- 14000 NO REASON This is normal system
Table continued…


abled Idle.
14 RELOADING IDLE warn- 9998 UNKNOWN CAUSE This is normal system
abled Idle.
15 ENABLED ACTIVE nor- 15000 NO REASON This is normal system
(6) quired.
15 ENABLED ACTIVE nor- 9998 UNKNOWN CAUSE This is normal system
(6) quired if user request-
ed.
16 ENABLED IDLE nor- 16000 NO REASON This is normal system
(6) quired.
16 ENABLED IDLE nor- 9998 UNKNOWN CAUSE This is normal state for
mal the redundant (idle)
(6) Zone Controller. No
action required if user
requested.
17 REMAPPING ACTIVE warn- 17000 NO REASON This is normal system
ZC initialization or dur-
ing HZM submission.
It is a transitory state
and should transition to
Enabled Active.
17 REMAPPING ACTIVE warn- 9998 UNKNOWN CAUSE This is normal system
ing HZM submission.
Enabled Active.
18 REMAPPING IDLE warn- 18000 NO REASON This is normal system
ing HZM submission.
Table continued…


Enabled Idle.
18 REMAPPING IDLE warn- 9998 UNKNOWN CAUSE This is normal system
ing HZM submission.
Enabled Idle.
has no knowledge of
companying status
managed object is
known and managed.
9994 UNKNOWN critical 9994 UNREACHABLE The node is unreacha-
(1) FROM MANAGER ble from the manager.
vestigate.
state.
Transcient Alarm Texts

The following topics contain tables listing the Transient Alarm Text for Dimetra IP Micro/ Dimetra LiTE object
types.
Atr
The following table lists the transient alarm text for the Atr object.

Table 185: Transient Alarm Text for the Atr Object
Alarm Alarm Text Severity

Code
1 Unknown Error indeterminate
(5)
2 File Error critical (1)
3 I/O Error major (2)
4 Unable to complete processing for last interval warning (4)
5 Maximum job count reached for interval warning (4)
6 Trying to create stats file for deleted interval warning (4)
7 Operating System Call Error critical (1)
8 Database initialization failed critical (1)
8003 Receive Manager Change Flag - Flag changed minor (3)
8004 Receive Manager Own Change Flag - Flag cleared minor (3)
8005 Receive Manager Own Change Flag - Flag reset minor (3)
9 Unable to get Zone Information critical (1)
AuC
The following table lists the transient alarm text for the AuC object.
Table 186: Transient Alarm Text for the AuC Object

Code
1 Backup. A database backup operation is being performed on the AuC serv- normal (6)
ers database.
10 CCK timeout. One or more device(s) failed to respond to a CCK message. major (2)
11 Cluster update timeout. One or more AuC(s) failed to respond to a cluster major (2)
update message.
12 Cluster activation timeout. One or more AuC(s) failed to respond to a clus- major (2)
ter activate message.
13 KEKm general failure. A KEKm update or activation operation has failed major (2)
due to an unresolved NACK or other failure.
14 KEKz general failure. A KEKz update or activation operation has failed major (2)
due to an unresolved NACK or other failure.
15 SCK general failure. An SCK update or activation operation has failed due major (2)
to an unresolved NACK or other failure.
16 CCK general failure. A CCK update or activation operation has failed due major (2)
to an unresolved NACK or other failure.
17 Cluster update general failure. A cluster key update has failed due to an un- major (2)
resolved NACK or other failure.
Table continued…


Code
18 Cluster activation general failure. A cluster key activation has failed due to major (2)
an unresolved NACK or other failure.
2 Backup failed. A database backup operation failed to complete properly. warning (4)
20 GSKO timeout. There is no response from one or more devices to a GSKO major (2)
message.
21 GSKO general failure. Update cannot be started, or unspecified failure. major (2)
22 GCK timeout. There is no response from one or more devices to a GCK major (2)
message.
23 GCK general failure. Update cannot be started, or unspecified failure. major (2)
24 DM-SCK timeout. There is no response from one or more devices to a DM- major (2)
SCK message.
25 DM-SCK general failure. Update cannot be started, or unspecified failure. major (2)
26 MGCK decryption failure. One or more device(s) failed to decrypt a major (2)
MGCK message.
27 MGCK timeout. There is no response from one or more devices to a major (2)
MGCK message.
28 MGCK general failure. Update cannot be started, or unspecified failure. major (2)
29 There is no response from one or more devices to MS update message. major (2)
3 KEKm decryption failure. One or more device(s) failed to decrypt a KEKm major (2)
message. May need to re-provision Ki.
30 Mobile update cannot be started, or unspecified failure. major (2)
31 One or more AuC(s) slaves is unable to connect to restored CHS Master major (2)
AuC.
32 Master AuC CHS restoration is unsafe to complete keys synchronization. major (2)
Manual intervention is required.
33 AuC has lost connectivity to at least one AuC in a nation-wide system major (2)
34 AuC has resumed connectivity in a nation-wide system major (2)
4 KEKz decryption failure. One or more device(s) failed to decrypt a KEKz major (2)
message. May need to re-provision Ki.
5 SCK decryption failure. One or more device(s) failed to decrypt an SCK major (2)
message.
6 CCK decryption failure. One or more device(s) failed to decrypt a CCK major (2)
message.
7 KEKm timeout. One or more device(s) failed to respond to a KEKm mes- major (2)
sage.
8 KEKz timeout. One or more device(s) failed to respond to a KEKz mes- major (2)
sage.
9 SCK timeout. One or more device(s) failed to respond to an SCK message. major (2)

Ccgw
The following table lists the transient alarm text for the Ccgw object.
Table 187: Transient Alarm Text for the Ccgw Object

Code
1 Network Time Protocol is unconfigured. warning (4)
2 Network Time Protocol server is unreachable. warning (4)
3 One CCGW-ZC CP down. warning (4)
4 User has disabled available channel (more than 50% channels available). warning (4)
5 Second CCGW-ZC CP up. normal (6)
GasHardDisk
The following table lists the transient alarm text for the GasHardDisk object.
Table 188: Transient Alarm Text for the GasHardDisk Object

Code
5001 Please replace HDD0. Redundancy is not available. major (2)
5002 Please replace HDD1. Redundancy is not available. major (2)
5003 RAID failed. Disk HDD0 submirrors are not in OK state. Redundancy is major (2)
not available.
5004 RAID failed. Disk HDD1 submirrors are not in OK state. Redundancy is major (2)
not available.
5005 Resynchronization in progress. Redundancy is not available at the moment major (2)
but will become available automatically.
5006 The filesystem is running out of space. major (2)
5007 Hardware RAID failed. Redundancy is not available. major (2)
5008 Failed to obtain RAID status. Please check manually. major (2)
GasVoltage
The following table lists the transient alarm text for the GasVoltage object.
Table 189: Transient Alarm Text for the GasVoltage Object

Code
7001 State changed to DOWN for major (2)
7002 State changed to UP for minor (3)
7003 New active slave minor (3)
7010 No active slaves on critical (1)

Mtig
The following table lists the transient alarm text for the Mtig object.
Table 190: Transient Alarm Text for the Mtig Object

Code
MtsBaseRadio
The following table lists the transient alarm text for the MtsBaseRadio object.
Table 191: Transient Alarm Text for the MtsBaseRadio Object

Code
1 BR Reset Error major (2)
10 BRC EEPROM checksum failure minor (3)
11 RX1 EEPROM checksum error detected minor (3)
14 Exciter EEPROM checksum error detected minor (3)
15 PA EEPROM checksum error detected minor (3)
16 RX1 missing major (2)
19 Exciter missing critical (1)
2 BR Cold Boot: No Previous Reset Error normal (6)
20 PA missing critical (1)
21 Battery revert operation initiated minor (3)
22 Battery revert operation terminated normal (6)
23 Minimum battery voltage not programmed minor (3)
24 Minimum battery charger voltage not programmed minor (3)
25 Diversity branch failure minor (3)
26 Auto detection of ATCC normal (6)
27 Auto detection of MTCC normal (6)
3 BRC reset requested by the Site Controller. Resetting now .... normal (6)
Table continued…


Code
30 High Level of Illegal Authentication Trials. Several failed authentication major (2)
trials have been detected for several minutes i.e. potentially an intruder is
trying to get access.
31 The High Level of Illegal Authentication Trials is now cleared as new ille- normal (6)
gal authentication trials have not been detected for several minutes.
32 High level of Illegal Protocol Packets Detected. An unexpected high num- major (2)
ber of illegal protocol packets have been received for a period i.e. potential-
ly an intruder is trying to use the data/voice communication.
33 High level of Illegal Protocol Packets Detected is now cleared. The number normal (6)
of illegal protocol packets is now back to normal level.
34 BRC Channel Operation Mode has changed - reset is expected. Resetting warning (4)
now.
4 BR Reset due to Front Panel Reset normal (6)
5 RX1 Delta value out of range minor (3)
8 BR Reset due to Watchdog Timer Expiry major (2)
9 Invalid BRC Revision Number critical (1)
MtsScBoardInternals
The following table lists the transient alarm text for the MtsScBoardInternals object.
Table 192: Transient Alarm Text for the MtsScBoardInternals Object

Code
1 GPS SW version mismatch minor (3)
10 Site Controller MMI requested reset normal (6)
1001 External contact alarm detected - 1 minor (3)
Table continued…


Code
1017 EAS contact alarm detected - 17 minor (3)
Table continued…


Code
11 BTS reset after GPS free run time expired major (2)
12 Unequipped BR registered minor (3)
13 Duplicate BR registered major (2)
14 Equipped BR failed to register major (2)
15 Site Controller software error detected minor (3)
16 GPS DPLL and GPS phase are out of lock minor (3)
17 Remote Link: Critical error: Received a ghost packet major (2)
18 BR configuration file not found major (2)
19 GPS: Site Reference Free Run beginning minor (3)
2 Site Controller reset - Unable to start CRM major (2)
20 Site Controller reset - Indeterminate reason major (2)
2001 External Output 1 activated normal (6)
2003 EAS Output 3 activated normal (6)
21 Site Controller reset - First boot from factory normal (6)
2101 External Output 1 deactivated normal (6)
2103 EAS Output 3 deactivated normal (6)
22 Site Controller reset - SM unable to start task major (2)
23 Site Controller reset - GPS lock lost major (2)
Table continued…


Code
24 Site Controller reset - BSL timeout major (2)
25 Multiple MCCH Mode Enabled normal (6)
26 MTS Multiple MCCH Mode Reminder minor (3)
27 Multiple MCCH Mode Disabled minor (3)
28 TSC-initiated BRC reset due to encryption subsystem failure major (2)
29 Security Class or key change ABORTED at site major (2)
3 Site Controller reset - DLCI retrieval failed major (2)
34 Extended band BRs temporarily de-keyed due to changing eTetra configu- normal (6)
ration in the system.
35 Standby BRC is not QAM capable warning (4)
36 All QAM-PD Base Radios within the RF Site have failed major (2)
37 QAM-PD is available within the RF Site normal (6)
4 Site Controller reset - DLX configuration failed major (2)
5 Site Controller reset - CM failure while loading IC major (2)
6 Site Controller reset - SM failure allocating memory major (2)
7 Site Controller reset - Failed to open GPSR serial i/p channel major (2)
8 Site Controller reset - Failed to open GPSR serial o/p channel major (2)
9 Manager requested reset normal (6)
MtsSite
The following table lists the transient alarm text for the MtsSite object.
Table 193: Transient Alarm Text for the MtsSite Object

Code
8000 Receive Old Change Flag - Flag cleared minor (3)
8001 Configuration changed via local interface (TESS) minor (3)
8002 Receive Old Change Flag - Flag reset minor (3)

MtsSscBoardInternals
The following table lists the transient alarm text for the MtsScBoardInternals object.
Table 194: Transient Alarm Text for the MtsSscBoardInernals Object

Code
1 GPS SW version mismatch minor (3)
10 Site Controller MMI requested reset normal (6)
Table continued…


Code
11 BTS reset after GPS free run time expired major (2)
12 Unequipped BR registered minor (3)
13 Duplicate BR registered major (2)
14 Equipped BR failed to register major (2)
15 Site Controller software error detected minor (3)
16 GPS DPLL and GPS phase are out of lock minor (3)
17 Remote Link: Critical error: Received a ghost packet major (2)
18 BR configuration file not found major (2)
19 GPS: Site Reference Free Run beginning minor (3)
2 Site Controller reset - Unable to start CRM major (2)
20 Site Controller reset - Indeterminate reason major (2)
Table continued…


Code
21 Site Controller reset - First boot from factory normal (6)
22 Site Controller reset - SM unable to start task major (2)
23 Site Controller reset - GPS lock lost major (2)
24 Site Controller reset - BSL timeout major (2)
25 Multiple MCCH Mode Enabled normal (6)
26 MTS Multiple MCCH Mode Reminder minor (3)
27 Multiple MCCH Mode Disabled minor (3)
28 TSC-initiated BRC reset due to encryption subsystem failure major (2)
29 Security Class or key change ABORTED at site major (2)
3 Site Controller reset - DLCI retrieval failed major (2)
34 Extended band BRs temporarily de-keyed due to changing eTetra configu- normal (6)
ration in the system.
35 Standby BRC is not QAM capable warning (4)
Table continued…


Code
36 All QAM-PD Base Radios within the RF Site have failed major (2)
37 QAM-PD is available within the RF Site normal (6)
4 Site Controller reset - DLX configuration failed major (2)
5 Site Controller reset - CM failure while loading IC major (2)
6 Site Controller reset - SM failure allocating memory major (2)
7 Site Controller reset - Failed to open GPSR serial i/p channel major (2)
8 Site Controller reset - Failed to open GPSR serial o/p channel major (2)
9 Manager requested reset normal (6)
pdgPDR
The following table lists the transient alarm text for the pdgPDR object.
Table 195: Transient Alarm Text for the pdgPDR Object

Code
1 Internal Software Error. If problem persists, restart the PDR. major (2)
5000 A message was received with an invalid size. warning (4)
5001 An invalid message has been discarded. warning (4)
5002 An error has occurred while accessing the mobile database. Restart the major (2)
PDR.
5003 Mark shared memory segment operation failed. minor (3)
5004 Detach from shared memory segment operation failed. minor (3)
5005 Invalid RNG IP address. Co-resident RNGs IP address is not on the same major (2)
subnet as its home PDR.
5006 Set user id to root operation failed. Re-install PDR application. major (2)
5050 Context activation failed. Mobile is not provisioned. minor (3)
5051 Context activation failed. Invalid NSAPI in the registration request. minor (3)
5052 Context activation failed. Invalid protocol configuration options length or minor (3)
invalid Qos length in the registration request.
5053 Context activation failed. Invalid header compression data in the registra- minor (3)
tion request.
5054 Context activation failed. Invalid data compression data in the registration minor (3)
request.
5055 Context activation failed. Invalid Element Present data in the registration minor (3)
request.
5056 Context activation failed. Invalid SNDCP version in the registration re- minor (3)
quest.
Table continued…


Code
5057 Context activation failed. Invalid MSU type in the registration request. minor (3)
5058 Context activation failed. Invalid network address type in the registration minor (3)
request.
5059 Context activation failed. Invalid IP address in the registration request. minor (3)
5060 Context activation failed. Number of contexts for this mobile exceeded the minor (3)
allowed maximum number.
5061 Context activation failed. Static IP address is not allowed for this mobile. minor (3)
5062 Context activation failed. Static IP address in the registration request does minor (3)
not match the provisioned IP address for this mobile.
5063 Context activation failed. Invalid APN index in the registration request. minor (3)
5064 Context activation failed. The PDR failed to resolve GGSN IP address. minor (3)
5065 Context activation failed. GGSN returned status: No Resource Available. minor (3)
5066 Context activation failed. GGSN returned status: Service Not Supported. minor (3)
5067 Context activation failed. GGSN returned status: User Authentication Fail- minor (3)
ure.
5068 Context activation failed. GGSN returned status: System Failure. minor (3)
5069 Context activation failed. GGSN returned status: Mandatory IE Incorrect. minor (3)
5070 Context activation failed. GGSN returned status: Mandatory IE Missing. minor (3)
5071 Context activation failed. GGSN returned status: Optional IE Incorrect. minor (3)
5072 Context activation failed. GGSN returned status: Invalid Message Format. minor (3)
5073 Context activation failed. GGSN returned status: Version Not Supported. minor (3)
5074 Context activation failed. No response received from Packet Data Home minor (3)
Location Register.
5075 Context activation failed. No response received from GGSN. minor (3)
5076 Context activation failed. Add User request to RNG timed out. minor (3)
5077 Context activation failed. RNG failed to add a New User record. minor (3)
5078 Context activation failed. Provisioning was updated while context activa- minor (3)
tion was in progress.
5079 Context activation failed. Context activation request for the mobile was re- minor (3)
ceived while context deactivation was in progress.
5080 Context renewal failed. Context renewal was received for an inactive con- minor (3)
text.
5081 Unexpected message was received from the same RNG while the context minor (3)
activation triggered by the New User indication was in progress.
5082 Site ID is out of range. warning (4)
5083 ZC query response: Mobile unknown to the Zone Controller HLR. minor (3)
Table continued…


Code
5084 Context activation failed. Number of active mobiles already at the maxi- warning (4)
mum allowed number.
5150 Outbound message discarded because number of bytes queued for mobile warning (4)
exceeded configured limit. Reduce excessive data traffic to the mobile.
5151 Outbound message discarded because number of records queued for mobile warning (4)
exceeded configured limit. Reduce excessive data traffic to the mobile.
5152 PDR mobile device outbound message queue has reached the 80% full lev- warning (4)
el. Reduce excessive data traffic to the mobile.
5153 PDR mobile device outbound message queue has reached the 90% full lev- warning (4)
el. Reduce excessive data traffic to the mobile.
5154 PDR mobile device outbound message queue has dropped below the 80% warning (4)
level. Excessive message traffic is decreasing.
5155 PDR mobile device outbound message queue has dropped below the 90% warning (4)
5156 Outbound message discarded because number of bytes in PDR message minor (3)
queues exceeded the system limitation. Reduce excessive data traffic to
PDR.
5157 The save bytes returned from the RNG do not match the save bytes sent in warning (4)
the original message. The PDR will take corrective actions to resynchron-
ize with the RNG.
5158 A response was received from an RNG after the response time limit ex- warning (4)
pired. The PDR will ignore the late response.
5159 A message was received with an unknown PDGP message type. Mobile de- major (2)
vice must be reconfigured to properly communicate with the PDR.
5160 A message was received from an unknown mobile device. If mobiles L2 ID warning (4)
is valid, add the device to the PDR configuration.
5161 Unknown state name of the RNG data link was received by a PDR process. warning (4)
The unknown state name is ignored.
5162 Specified RNG Number was not found. If problem persists, stop and then major (2)
start the PDR.
5200 Add to local mobile table failed. If problem persists, restart the PDR. major (2)
5250 Invalid RNG name received. Contact Motorola support. major (2)
5251 Unable to send a request to reset the RNG. Refer to the PDG troubleshoot- major (2)
ing manual to correct the problem.
5302 An attempt was made to send a trap for an unknown managed object. If major (2)
problem persists, restart the PDR.
5350 Zone ID change attempted. If PDR was moved to a different zone, the PDR major (2)
database must be deleted and re-created.
5400 Version Not Supported message was received from GGSN. Check the ver- warning (4)
sion supported for the GGSN and the PDR. There is a mismatch in the
product software versions.
Table continued…


Code
pdgPDRRNG
The following table lists the transient alarm text for the pdgPDRRNG object.
Table 196: Transient Alarm Text for the pdgPDRRNG Object

Code
6603 RNG rejected a configuration request as coming not from home PDR. Con- major (2)
tact Motorola Support.
6605 PDGP protocol versions supported by PDR and RNG do not match. Verify major (2)
PDR-RNG software version compatibility if it fits.
6606 SPDP protocol versions supported by PDR and RNG do not match. Verify major (2)
PDR-RNG software version compatibility if it fits.
pdgPDRRNGLink
The following table lists the transient alarm text for the pdgPDRRNGLink object.
Table 197: Transient Alarm Text for the pdgPDRRNGLink Object

Code
6400 RNG control link connected. normal (6)
6401 RNG control link disconnected. warning (4)
6423 An invalid message length or invalid message type has been received from major (2)
an RNG. The PDR will reset connection with the RNG. If problem persists,
reboot the PDR and the RNG.
pdgPDRZCLink
The following table lists the transient alarm text for the pdgPDRZCLink object.
Table 198: Transient Alarm Text for the pdgPDRZCLink Object

Code
6002 PDR-ZC connection table is full. warning (4)
6004 ZC query response/push message size is wrong. minor (3)
6006 PDR failed to send a UDP packet to Zone Controller. minor (3)

SDR
The following table lists the transient alarm text for the SDR object.
Table 199: Transient Alarm Text for the SDR Object

Code
1000 A configuration instance notification all operation failed. If problem per- major (2)
sists, reboot the SDR.
1001 A configuration definition notification all operation failed. If problem per- major (2)
1002 A configuration definition get all operation failed. If problem persists, re- major (2)
boot the SDR.
1003 A configuration function get all operation failed. If problem persists, reboot major (2)
the SDR.
1004 A configuration function get info operation failed. If problem persists, re- major (2)
boot the SDR.
1005 A configuration definition describe operation failed. If problem persists, re- major (2)
boot the SDR.
1006 A configuration instance read operation failed. If problem persists, reboot major (2)
the SDR.
1007 A configuration instance get type operation failed. If problem persists, re- major (2)
boot the SDR.
1008 A configuration instance find first operation failed. If problem persists, re- major (2)
boot the SDR.
1009 A configuration instance find next operation failed. If problem persists, re- major (2)
boot the SDR.
1010 A configuration instance get component operation failed. If problem per- major (2)
1011 A configuration instance clear notification operation failed. If problem per- major (2)
1012 A configuration instance set component operation failed. If problem per- major (2)
1013 A configuration instance write operation failed. If problem persists, reboot major (2)
the SDR.
1014 A configuration instance create operation failed. If problem persists, reboot major (2)
the SDR.
1015 A configuration instance destroy operation failed. If problem persists, re- major (2)
boot the SDR.
1100 A name resolve by name operation failed. If problem persists, reboot the major (2)
SDR.
1101 A name get all operation failed. If problem persists, reboot the SDR. major (2)
1102 A name register operation failed. If problem persists, reboot the SDR. major (2)
Table continued…


Code
1103 A name deregister operation failed. If problem persists, reboot the SDR. major (2)
1200 A tag is identified with an invalid address. If problem persists, reboot the major (2)
SDR.
1201 A tag is identified with no address. If problem persists, reboot the SDR. major (2)
1202 A tag object get operation failed. If problem persists, reboot the SDR. major (2)
1203 A tag create operation failed. If problem persists, reboot the SDR. major (2)
1204 A tag insert operation failed. If problem persists, reboot the SDR. major (2)
1205 A tag describe operation failed. If problem persists, reboot the SDR. major (2)
1206 A tag get all by module operation failed. If problem persists, reboot the major (2)
SDR.
1207 A tag change owner operation failed. If problem persists, reboot the SDR. major (2)
1208 A tag change owner force operation failed. If problem persists, reboot the major (2)
SDR.
1209 A tag copy operation failed. If problem persists, reboot the SDR. major (2)
1210 A tag change owner system operation failed. If problem persists, reboot the major (2)
SDR.
1211 A tag object update operation failed. If problem persists, reboot the SDR. major (2)
1212 A tag object delete operation failed. If problem persists, reboot the SDR. major (2)
1213 A tag destroy operation failed. If problem persists, reboot the SDR. major (2)
1300 A memory table get all operation failed. If problem persists, reboot the major (2)
SDR.
1301 A memory table get users operation failed. If problem persists, reboot the major (2)
SDR.
1302 A memory table describe operation failed. If problem persists, reboot the major (2)
SDR.
1303 A memory table open operation failed. If problem persists, reboot the SDR. major (2)
1304 A memory table object insert operation failed. If problem persists, reboot major (2)
the SDR.
1305 A memory table object update operation failed. If problem persists, reboot major (2)
the SDR.
1306 A memory table object delete operation failed. If problem persists, reboot major (2)
the SDR.
1307 A memory table copy operation failed. If problem persists, reboot the SDR. major (2)
1308 A memory table change owner operation failed. If problem persists, reboot major (2)
the SDR.
1309 A memory table object get operation failed. If problem persists, reboot the major (2)
SDR.
Table continued…


Code
1310 A memory table object delete all operation failed. If problem persists, re- major (2)
boot the SDR.
1311 A memory table close operation failed. If problem persists, reboot the SDR. major (2)
1312 A memory table object get all operation failed. If problem persists, reboot major (2)
the SDR.
1400 A semaphore get all operation failed. If problem persists, reboot the SDR. major (2)
1401 A semaphore open operation failed. If problem persists, reboot the SDR. major (2)
1402 A semaphore describe operation failed. If problem persists, reboot the major (2)
SDR.
1500 A tracker application select address operation failed. If problem persists, re- major (2)
boot the SDR.
1501 A tracker application registration operation failed. If problem persists, re- major (2)
boot the SDR.
1600 A route operation failed. If problem persists, reboot the SDR. major (2)
1601 A route query operation failed. If problem persists, reboot the SDR. major (2)
1602 A route add response operation failed. If problem persists, reboot the SDR. major (2)
1603 A route send response operation failed. If problem persists, reboot the SDR. major (2)
1604 A route dump operation failed. If problem persists, reboot the SDR. major (2)
1800 A statistical element was not found. If problem persists, reboot the SDR. major (2)
1801 A statistic module initialization operation failed. If problem persists, reboot major (2)
the SDR.
1802 A statistic module insert operation failed. If problem persists, reboot the major (2)
SDR.
1803 An invalid statistical element was specified. If problem persists, reboot the major (2)
SDR.
1804 A statistic application deselect all operation failed. If problem persists, re- major (2)
boot the SDR.
1805 An invalid statistical element was specified. If problem persists, reboot the major (2)
SDR.
1806 A statistic application deselect all operation failed. If problem persists, re- major (2)
boot the SDR.
1807 A statistic application get operation failed. If problem persists, reboot the major (2)
SDR.
1808 A statistic application reset operation failed. If problem persists, reboot the major (2)
SDR.
1809 A statistic module delete operation failed. If problem persists, reboot the major (2)
SDR.
1810 A statistic module get operation failed. If problem persists, reboot the SDR. major (2)
Table continued…


Code
1811 A statistic module write operation failed. If problem persists, reboot the major (2)
SDR.
2000 A device queue create operation failed. If problem persists, reboot the SDR. major (2)
2001 A device queue peek operation failed. If problem persists, reboot the SDR. major (2)
2002 A device queue write operation failed. If problem persists, reboot the SDR. major (2)
2003 A device queue read operation failed. If problem persists, reboot the SDR. major (2)
2004 A device queue get operation failed. If problem persists, reboot the SDR. major (2)
2005 A device queue alternate key addition operation failed. If problem persists, major (2)
reboot the SDR.
2006 A device queue set operation failed. If problem persists, reboot the SDR. major (2)
2007 A device queue destroy operation failed. If problem persists, reboot the major (2)
SDR.
2008 A device queue lookup operation failed. If problem persists, reboot the major (2)
SDR.
2009 A device queue find first operation failed. If problem persists, reboot the major (2)
SDR.
201 A socket open operation failed. If problem persists, reboot the SDR. major (2)
2010 A device queue find next operation failed. If problem persists, reboot the major (2)
SDR.
202 A socket set option operation failed. If problem persists, reboot the SDR. major (2)
203 A socket set flags operation failed. If problem persists, reboot the SDR. major (2)
204 A socket get flags operation failed. If problem persists, reboot the SDR. major (2)
205 A socket bind operation failed. If problem persists, reboot the SDR. major (2)
206 A socket listen operation failed. If problem persists, reboot the SDR. major (2)
207 A socket before accept condition has been identified. If problem persists, major (2)
reboot the SDR.
208 A socket accept operation failed. If problem persists, reboot the SDR. major (2)
2100 A list and queue insert operation failed. If problem persists, reboot the major (2)
SDR.
2101 A list and queue create operation failed. If problem persists, reboot the major (2)
SDR.
2102 A list and queue push operation failed. If problem persists, reboot the SDR. major (2)
2103 A list and queue pop operation failed. If problem persists, reboot the SDR. major (2)
2104 A list and queue get first operation failed. If problem persists, reboot the major (2)
SDR.
2105 A list and queue delete operation failed. If problem persists, reboot the major (2)
SDR.
Table continued…


Code
2106 A list and queue search operation failed. If problem persists, reboot the major (2)
SDR.
2107 A list and queue count operation failed. If problem persists, reboot the major (2)
SDR.
2108 A list and queue find first operation failed. If problem persists, reboot the major (2)
SDR.
2109 A list and queue find next operation failed. If problem persists, reboot the major (2)
SDR.
211 A socket read operation failed. If problem persists, reboot the SDR. major (2)
2110 A list and queue get next operation failed. If problem persists, reboot the major (2)
SDR.
2111 A list and queue walk operation failed. If problem persists, reboot the SDR. major (2)
212 A socket connect operation was refused. If problem persists, reboot the major (2)
SDR.
213 A socket connect operation failed. If problem persists, reboot the SDR. major (2)
216 A socket was not found. If problem persists, reboot the SDR. major (2)
217 A socket create operation failed. If problem persists, reboot the SDR. major (2)
2200 A database client initialization operation failed. If problem persists, reboot major (2)
the SDR.
2201 A database client login initialization operation failed. If problem persists, major (2)
reboot the SDR.
2202 A database table destroy operation failed. If problem persists, reboot the major (2)
SDR.
2203 A database handle destroy operation failed. If problem persists, reboot the major (2)
SDR.
2204 A database OMS error occurred. If problem persists, reboot the SDR. major (2)
2205 A database error occurred. If problem persists, reboot the SDR. major (2)
300 A write pipe operation failed. If problem persists, reboot the SDR. major (2)
301 A select operation failed. If problem persists, reboot the SDR. major (2)
302 A before read condition has been identified. If problem persists, reboot the major (2)
SDR.
305 An improper socket type was detected. If problem persists, reboot the SDR. major (2)
306 An open pipe operation failed. If problem persists, reboot the SDR. major (2)
307 A get pipe flags operation failed. If problem persists, reboot the SDR. major (2)
308 A set pipe flags operation failed. If problem persists, reboot the SDR. major (2)
309 An open operation failed. If problem persists, reboot the SDR. major (2)
310 A put message operation failed. If problem persists, reboot the SDR. major (2)
311 A get message operation failed. If problem persists, reboot the SDR. major (2)
Table continued…


Code
312 A ioctl operation failed. If problem persists, reboot the SDR. major (2)
313 A write operation failed. If problem persists, reboot the SDR. major (2)
314 A tty name operation failed. If problem persists, reboot the SDR. major (2)
315 A file open operation failed. If problem persists, reboot the SDR. major (2)
316 A read operation failed. If problem persists, reboot the SDR. major (2)
317 A tcgetattr operation failed. If problem persists, reboot the SDR. major (2)
318 A tcsetattr operation failed. If problem persists, reboot the SDR. major (2)
319 A read pipe operation failed. If problem persists, reboot the SDR. major (2)
3900 A connection is not active. If problem persists, reboot the SDR. major (2)
3901 A send operation received an error. If problem persists, reboot the SDR. major (2)
3902 An improper address format was detected. If problem persists, reboot the major (2)
SDR.
3903 An improper connection type was detected. If problem persists, reboot the major (2)
SDR.
3904 Operation identified number of loaded endpoints. If problem persists, re- major (2)
boot the SDR.
3905 Operation detected no endpoints. If problem persists, reboot the SDR. major (2)
3909 A process fork operation failed. If problem persists, reboot the SDR. major (2)
SDR.
3911 Operation could not find the source address. If problem persists, reboot the major (2)
SDR.
3912 Operation read an invalid message length. If problem persists, reboot the major (2)
SDR.
3913 Operation received a bad command. If problem persists, reboot the SDR. major (2)
3914 An insert module operation failed. If problem persists, reboot the SDR. major (2)
SDR.
3916 A send data operation failed. If problem persists, reboot the SDR. major (2)
3917 A get matching modules operation failed. If problem persists, reboot the major (2)
SDR.
3918 A get modules operation failed. If problem persists, reboot the SDR. major (2)
3919 A get routes operation failed. If problem persists, reboot the SDR. major (2)
3920 A get protocols operation failed. If problem persists, reboot the SDR. major (2)
3921 A get networks operation failed. If problem persists, reboot the SDR. major (2)
3922 A get route list operation failed. If problem persists, reboot the SDR. major (2)
3923 An address create operation failed. If problem persists, reboot the SDR. major (2)
Table continued…


Code
3924 Operation received a bad response. If problem persists, reboot the SDR. major (2)
3925 Operation detected an invalid parameter. If problem persists, reboot the major (2)
SDR.
3926 Operation detected a bad parameter. If problem persists, reboot the SDR. major (2)
3927 An invalid element was requested. If problem persists, reboot the SDR. major (2)
3928 A reaper operation failed. If problem persists, reboot the SDR. major (2)
3929 A routing tag data component is empty. If problem persists, reboot the major (2)
SDR.
3930 An OMS Package was empty. If problem persists, reboot the SDR. major (2)
400 A threads attribute initialization operation failed. If problem persists, reboot major (2)
the SDR.
4000 A timer get all operation failed. If problem persists, reboot the SDR. major (2)
4001 A timer get operation failed. If problem persists, reboot the SDR. major (2)
4003 A timer create operation failed. If problem persists, reboot the SDR. major (2)
4006 A timer destroy operation failed. If problem persists, reboot the SDR. major (2)
4007 A timer set operation failed. If problem persists, reboot the SDR. major (2)
4008 A timer start operation failed. If problem persists, reboot the SDR. major (2)
4009 A timer stop operation failed. If problem persists, reboot the SDR. major (2)
401 A threads attribute setd operation failed. If problem persists, reboot the major (2)
SDR.
4010 A timer reset operation failed. If problem persists, reboot the SDR. major (2)
402 A threads create operation failed. If problem persists, reboot the SDR. major (2)
403 A threads join operation failed. If problem persists, reboot the SDR. major (2)
404 A threads mutual exclusion attribute create operation failed. If problem per- major (2)
405 A threads mutual exclusion create operation failed. If problem persists, re- major (2)
boot the SDR.
406 A threads condition attributes object initialization operation failed. If prob- major (2)
lem persists, reboot the SDR.
407 A threads condition variable initialization operation failed. If problem per- major (2)
408 A threads mutual exclusion lock operation failed. If problem persists, re- major (2)
boot the SDR.
409 A threads condition wait operation failed. If problem persists, reboot the major (2)
SDR.
410 A thread condition signal failed. If problem persists, reboot the SDR. major (2)
411 A create mutual exclusion lock operation failed. If problem persists, reboot major (2)
the SDR.
Table continued…


Code
412 A threads prctl operation failed. If problem persists, reboot the SDR. major (2)
413 A threads sproc operation failed. If problem persists, reboot the SDR. major (2)
414 A mutual exclusion lock operation failed. If problem persists, reboot the major (2)
SDR.
415 A mutual exclusion unlock operation failed. If problem persists, reboot the major (2)
SDR.
416 A threads usinit operation failed. If problem persists, reboot the SDR. major (2)
417 A threads usnewsma operation failed. If problem persists, reboot the SDR. major (2)
418 A thread once failed. If problem persists, reboot the SDR. major (2)
419 A thread mutex unlock operation failed. If problem persists, reboot the major (2)
SDR.
420 A thread set cancel type operation failed. If problem persists, reboot the major (2)
SDR.
421 A thread mutex initialization failed. If problem persists, reboot the SDR. major (2)
5000 AUTHORIZATION DENIED: Host not in configuration or host not regis- warning (4)
tered.
5001 DEREGISTRATION DENIED: FLM rejected the deregistration. warning (4)
5002 ROAMING DENIED: Mobiles registration state is ROAM PENDING. warning (4)
5003 REGISTRATION DENIED: Mobile Registration denial. warning (4)
5004 REGISTRATION TIMEOUT: Mobile Registration timeout. warning (4)
5005 INVALID REGISTRATION STATE: Mobile registration state is either un- warning (4)
known or pending.
5006 Outbound message discarded because number of bytes queued for mobile warning (4)
would exceed configured limit. Reduce excessive data traffic to mobile.
5007 Outbound message discarded because number of records queued for mobile warning (4)
would exceed configured limit. Reduce excessive data traffic to mobile.
5008 SDR mobile device outbound message queue has reached the 80% full lev- warning (4)
el. Reduce excessive data traffic to mobile.
5009 SDR mobile device outbound message queue has reached the 90% full lev- warning (4)
el. Reduce excessive data traffic to mobile.
5010 SDR mobile device outbound message queue has dropped below the 80% normal (6)
5011 SDR mobile device outbound message queue has dropped below the 90% normal (6)
5012 Outbound message discarded because number of bytes in SDR message minor (3)
queues exceeded the system limitation. Reduce excessive data traffic to
SDR.
Table continued…


Code
5014 The save bytes returned from the RF SITE do not match the save bytes sent warning (4)
in the original message. The SDR will take corrective actions to re-
synchronize with the RF SITE.
5015 A response was received from the RF SITE after the response time limit warning (4)
expired. The SDR will ignore the late response.
5016 A message was received with an unknown FLM message type. Mobile de- warning (4)
vice and/or RF SITE must be reconfigured to properly communicate with
the SDR.
5017 A message was received with an unknown FLM register number. Mobile warning (4)
device must be reconfigured to properly communicate with the SDR.
5018 A message was received from an unknown mobile device. If LLI is valid, warning (4)
add the device to the SDR configuration.
5019 Message received from mobile device in an unknown registration state. warning (4)
Verify the mobile devices registration state through SDR configuration.
5020 An illegal configuration change was attempted. The requested configura- warning (4)
tion change was not processed. This is a software error.
5021 A message was received with an invalid size. warning (4)
5022 An unknown statistic was received by a SDR module. The unknown statis- warning (4)
tic is ignored. If problem persists reboot the SDR.
5023 A message has been discarded. A prior alarm should explain the cause. warning (4)
5024 Channel for broadcast message is not granted as requested minor (3)
5029 ISSI not in Home Zone Mapping Table. Add ISSI to Home Zone Mapping minor (3)
Table.
5030 Home Zone Mapping Table exceeds. Reduce the number of entries in the major (2)
Home Zone Mapping Table and restart the SDR.
5031 Wrong datagram version on the G-Interface (ZC). minor (3)
5101 The SDR failed to retrieve the CID status. Stop and then start the RF SITE major (2)
CID.
5102 The SDR failed to select the CID status. Stop and then start the RF SITE major (2)
CID.
5106 The RF SITE configuration record contains an invalid CID number. critical (1)
5200 A SLIP component failed verification by having an invalid value. Change major (2)
the SLIP component identified to a valid value.
5201 Failed to retrieve SLIP interface characteristics. major (2)
5202 An input or output stream could not be created or could not allocate enough major (2)
memory.
5203 A SLIP interface SLATTACH failed verification. Verify that the SLAT- major (2)
TACH processes are running on the SDR. If they are not running, restart
the SDR.
Table continued…


Code
5204 A SLIP interface failed verification. Verify that both cfgsvr_mod and major (2)
ip_mod processes are running on the SDR. If not, restart the SDR and retry
the operation.
5205 Adding a subnet failed. Verify that both cfgsvr_mod and ip_mod processes warning (4)
are running on the SDR. If not, restart the SDR and retry the operation.
5206 Deleting a subnet failed. Verify that both cfgsvr_mod and ip_mod are run- warning (4)
ning on the SDR. If not, restart the SDR and retry the operation.
5207 The transaction submitted from the SDR configuration to a server process warning (4)
was incomplete. Retry the transaction.
5300 An invalid message length or invalid message type has been received from major (2)
an RF SITE CID. Stop and then restart the RF SITE CID.
5301 A parent process has failed to send a message to a child process. Restart the critical (1)
SDR. Process communication has been lost.
5302 Process communication is not synchronized. Restart the SDR. critical (1)
5303 Process communication is not synchronized. Restart the SDR. critical (1)
5308 Failed to receive loop back messages from RF SITE. SDR will attempt to major (2)
stop and restart connection.
5400 Internal error adding, modifying or deleting log definition. View the log minor (3)
definition and if necessary, retry the modification.
5401 Internal error closing log session file. If necessary retry the operation. minor (3)
5402 Internal error opening log session file. Verify that user has write access to minor (3)
specified directory.
5403 Internal error occurred while adding, modifying or deleting a log session. minor (3)
Retry the modification.
5404 Internal error occurred while adding, modifying, or deleting a module table minor (3)
entry. Stop and start the SDR.
5405 A logging session rollover failed. warning (4)
5406 A system command failed. warning (4)
5500 FLMHOST CONNECTION ESTABLISHED. normal (6)
5501 FLMHOST CONNECTION TERMINATED. normal (6)
5502 FLMHOST CID SESSION STARTED. normal (6)
5503 FLMHOST CID SESSION STOPPED. normal (6)
5504 FLMHOST CID TERMINATED BY OTHER HOST. minor (3)
5505 FLMHOST INITIATE CID TIMEOUT. minor (3)
5506 FLMHOST CONNECTION PAIR TIMEOUT. minor (3)
5507 FLMHOST INITIATE INVALID CID RECEIVED. minor (3)
5508 FLMHOST INITIATE DUPLICATE CID RECEIVED. minor (3)
5509 FLMHOST IDLE CID SESSION TERMINATION. minor (3)
Table continued…


Code
5510 FLMHOST TERMINATE NON-EXIST CID RECEIVED. warning (4)
5600 ALARM SI UNK TYPECODE. warning (4)
5601 ALARM SI UNK FIELDTYPECODE. warning (4)
5602 ALARM SI MOBILE ERROR. warning (4)
5700 ALARM DATACOMP UNK ALG. warning (4)
5701 ALARM DATACOMP COMP FAILED. warning (4)
5702 ALARM DATACOMP DECOMP FAILED. warning (4)
5800 The SDR subagent temporarily lost the connection to the SNMP master minor (3)
agent. Trap is sent when connection is restored.
5801 An SNMP sub-agent created a socket connection to the Master SNMP normal (6)
agent. The sub-agent will now be able to respond to SNMP requests and
send SNMP traps.
5802 The SDR could not retrieve its host ID. The SDR will not be able to send major (2)
SNMP traps and respond to SNMP requests. Restart the SDR.
5803 An alarm occurred, but it was configured to an unknown managed object. minor (3)
This is a software error.
5804 An alarm occurred, but the alarm was not known to the snmp trap subagent. minor (3)
This is a software error.
5805 An EBTS link managed object was discovered on the SDR. normal (6)
5806 EBTS Link discovered. normal (6)
5808 The EBTS Link configuration changed in the SDR database, but the SNMP minor (3)
agent could not be notified. Restart the SDR.
5809 A manager requested to be deregistered from trap notification. warning (4)
5810 The interprocess communication mechanisms within the SNMP agent minor (3)
failed. Restart the SDR.
600 A memory convert operation failed. If problem persists, reboot the SDR. major (2)
601 A memory read operation failed. If problem persists, reboot the SDR. major (2)
602 A local memory allocation operation failed. If problem persists, reboot the major (2)
SDR.
603 A global memory allocation operation failed. If problem persists, reboot the major (2)
SDR.
604 A memory write operation failed. If problem persists, reboot the SDR. major (2)
605 A memory size operation failed. If problem persists, reboot the SDR. major (2)
606 A bad memory was detected. If problem persists, reboot the SDR. major (2)
607 A memory duplicate operation failed. If problem persists, reboot the SDR. major (2)
608 A memory change owner operation failed. If problem persists, reboot the major (2)
SDR.
Table continued…


Code
609 A memory change owner by process ID operation failed. If problem per- major (2)
610 A memory splice operation failed. If problem persists, reboot the SDR. major (2)
611 A memory split operation failed. If problem persists, reboot the SDR. major (2)
612 A memory block semaphore lock operation failed. If problem persists, re- major (2)
boot the SDR.
613 A memory truncation operation failed. If problem persists, reboot the SDR. major (2)
614 A memory free operation failed. If problem persists, reboot the SDR. major (2)
700 An event get all operation failed. If problem persists, reboot the SDR. major (2)
701 An event get handler operation failed. If problem persists, reboot the SDR. major (2)
702 An event table lock operation failed. If problem persists, reboot the SDR. major (2)
703 An event send synchronous operation failed. If problem persists, reboot the major (2)
SDR.
704 An event send asynchronous operation failed. If problem persists, reboot major (2)
the SDR.
705 An event register handler operation failed. If problem persists, reboot the major (2)
SDR.
706 An event deregister handler operation failed. If problem persists, reboot the major (2)
SDR.
707 An event receive operation failed. If problem persists, reboot the SDR. major (2)
708 An event send operation failed. If problem persists, reboot the SDR. major (2)
709 An event deregister all operation failed. If problem persists, reboot the major (2)
SDR.
800 A process owner could not be found. If problem persists, reboot the SDR. major (2)
801 A process get all operation failed. If problem persists, reboot the SDR. major (2)
SDRRFSiteLink
The following table lists the transient alarm text for the SRDRFSiteLink object.
Table 200: Transient Alarm Text for the SRDRFSiteLink Object

Code
5100 Outbound initialize CID failed. critical (1)
5103 Start message flow failed. critical (1)
5104 Assign registration CID failed. critical (1)
5105 Assign control CID failed. critical (1)
5107 Invalid CID state. critical (1)
5109 RF SITE CID has been started. normal (6)
Table continued…


Code
5110 RF SITE CID has been stopped. critical (1)
UCS01
The following table lists the transient alarm text for the UCS01 object.
Table 201: Transient Alarm Text for the UCS01 Object

Code
1000 Backup incomplete due to both ways of replications between the UCS and minor (3)
the ZDS server not ready
10001 Swap partition is running out of space because it reached maximal allowed critical (1)
value
10002 Swap space reallocation impossible critical (1)
10003 Increased Swap due to Swap partition running out of space warning (4)
101 DB transfer backup to master success normal (6)
10101 Root filesystem is running out of space critical (1)
102 DB transfer master to backup success normal (6)
10201 Detected potential Firebird server freeze. It is advised to perform database major (2)
optimization. If problem persists then server reboot is recommended.
10202 Detected invalid database state. It is advised to perform database optimiza- major (2)
tion. If problem persists then server reboot is recommended.
10203 Detected missing or potentially corrupted database file. It is advised to per- major (2)
form database optimization. If problem persists then restore database from
backup.
backup or from ZDS with promote.
UCS with syncdown.
1111 DB transfer backup to master failed on backup major (2)
1112 DB transfer backup to master failed on move major (2)
1113 DB transfer backup to master failed on restore major (2)
1121 DB transfer master to backup failed on backup major (2)
1122 DB transfer master to backup failed on move major (2)
1123 DB transfer master to backup failed on restore major (2)
113 DB transfer failed on restore - invalid pair of hosts major (2)
122 DB transfer master to backup aborted major (2)
Table continued…


Code
123 DB transfer point of no return has started normal (6)
124 Database transfer has started normal (6)
125 Database transfer has been completed successfully normal (6)
131 restoring the database failed critical (1)
132 Enabling the smartzone manager failed after transferring the database major (2)
133 System that the database is being transferred to is no longer idle minor (3)
134 enabling the smartzone manager failed critical (1)
135 Failed to establish connection to remote system major (2)
136 A database transfer is currently in progress normal (6)
137 Backing up the database failed major (2)
138 Database transfer failed, attempted transfer from active master to active minor (3)
backup
139 Database transfer failed, attempted transfer from idle master to idle backup warning (4)
141 Database transfer failed, attempted transfer from idle master to active back- warning (4)
up
142 Database transfer failed, attempted transfer from active backup to active minor (3)
master
143 Database transfer failed, attempted transfer from idle backup to idle master minor (3)
144 Database transfer failed, attempted transfer from idle backup to active mas- warning (4)
ter
145 Attempt to transfer the database has failed major (2)
146 Unable to determine if the system that originated the transfer is master or major (2)
backup
147 Unable to determine the current status of the zone controller minor (3)
148 Unrecognized zone controller state from system that originated the data- major (2)
base transfer
149 Cannot determine status of zone controller on the system that the database major (2)
is being transferred to
151 Unrecognized zone controller state on the system that the database is being major (2)
transferred to
152 Conflicting db operation in progress, transfer failed minor (3)
153 The versions of the database on the systems are not compatible major (2)
154 Could not establish connection with the zc/m server on the system that the major (2)
database is being transferred to
155 Infrastructure export failed, zc started with old database minor (3)
156 Database transfer processing failed on system that the database is being major (2)
transferred to
Table continued…


Code
157 The zone controller status on the system that the database is being transfer- major (2)
red to is not valid for a transfer, it should be reset to ensure that the zone
controller has the latest database information
158 The zone controller status on originating system is not valid for a database major (2)
transfer
159 The zone controller on the transfer to system was not reset during the data- warning (4)
base transfer, this should be done manually to ensure that the zone control-
ler has the latest database information
171 Standalone database exported successfully normal (6)
172 Standalone database export failed to copy to zc/m server major (2)
173 Standalone database export failed major (2)
174 Conflicting db operation in progress, db export failed minor (3)
175 Standalone database export failed to load to zc/m server major (2)
180 Replication to the server is DOWN, database synchronization is required major (2)
186 Sending data to ZC resulted in SNMPError major (2)
187 Sending data to PDR resulted in SNMPError major (2)
188 Sending data to EBTS resulted in SNMPError major (2)
189 Sending data to MTIG resulted in SNMPError major (2)
190 ZC replied with bad response normal (6)
191 PDR replied with bad response normal (6)
192 EBTS replied with bad response normal (6)
193 MTIG replied with bad response normal (6)
194 Database update exception during receiving configuration data warning (4)
211 Scheduled Backup Started normal (6)
212 Scheduled Backup Succeeded normal (6)
213 Scheduled Backup Interrupted minor (3)
214 Scheduled Backup Failed major (2)
215 Manual Backup Started normal (6)
216 Manual Backup Succeeded normal (6)
217 Manual Backup Interrupted minor (3)
218 Manual Backup Failed major (2)
Table continued…


Code
299 Undefined status of UCS backup major (2)
ZcOperationalHealth
The following table lists the transient alarm text for the ZcOpState object.
Table 202: Transient Alarm Text for the ZcOpState Object

Code
1 Communication with the Serial Switch is available normal (6)
2 Communication with the Serial Switch is unavailable warning (4)
3 The Serial Switch failed to switchover warning (4)
ZDS
The following table lists the transient alarm text for the ZDS object.
Table 203: Transient Alarm Text for the ZDS Object

Code
1000 Backup incomplete due to both ways of replications between the UCS and minor (3)
the ZDS server not ready
10001 Swap partition is running out of space because it reached maximal allowed critical (1)
value
10002 Swap space reallocation impossible critical (1)
10003 Increased Swap due to Swap partition running out of space warning (4)
101 DB transfer backup to master success normal (6)
10101 Root filesystem is running out of space critical (1)
102 DB transfer master to backup success normal (6)
10201 Detected potential Firebird server freeze. It is advised to perform database major (2)
optimization. If problem persists then server reboot is recommended.
10202 Detected invalid database state. It is advised to perform database optimiza- major (2)
tion. If problem persists then server reboot is recommended.
backup.
backup or from ZDS with promote.
UCS with syncdown.
Table continued…


Code
1111 DB transfer backup to master failed on backup major (2)
1112 DB transfer backup to master failed on move major (2)
1113 DB transfer backup to master failed on restore major (2)
1121 DB transfer master to backup failed on backup major (2)
1122 DB transfer master to backup failed on move major (2)
1123 DB transfer master to backup failed on restore major (2)
113 DB transfer failed on restore - invalid pair of hosts major (2)
122 DB transfer master to backup aborted major (2)
123 DB transfer point of no return has started normal (6)
124 Database transfer has started normal (6)
125 Database transfer has been completed successfully normal (6)
131 restoring the database failed critical (1)
132 Enabling the smartzone manager failed after transferring the database major (2)
133 System that the database is being transferred to is no longer idle minor (3)
134 enabling the smartzone manager failed critical (1)
135 Failed to establish connection to remote system major (2)
136 A database transfer is currently in progress normal (6)
137 Backing up the database failed major (2)
138 Database transfer failed, attempted transfer from active master to active minor (3)
backup
139 Database transfer failed, attempted transfer from idle master to idle backup warning (4)
141 Database transfer failed, attempted transfer from idle master to active back- warning (4)
up
142 Database transfer failed, attempted transfer from active backup to active minor (3)
master
143 Database transfer failed, attempted transfer from idle backup to idle master minor (3)
144 Database transfer failed, attempted transfer from idle backup to active mas- warning (4)
ter
145 Attempt to transfer the database has failed major (2)
146 Unable to determine if the system that originated the transfer is master or major (2)
backup
147 Unable to determine the current status of the zone controller minor (3)
148 Unrecognized zone controller state from system that originated the data- major (2)
base transfer
149 Cannot determine status of zone controller on the system that the database major (2)
is being transferred to
Table continued…


Code
151 Unrecognized zone controller state on the system that the database is being major (2)
transferred to
152 Conflicting db operation in progress, transfer failed minor (3)
153 The versions of the database on the systems are not compatible major (2)
154 Could not establish connection with the zc/m server on the system that the major (2)
database is being transferred to
155 Infrastructure export failed, zc started with old database minor (3)
156 Database transfer processing failed on system that the database is being major (2)
transferred to
157 The zone controller status on the system that the database is being transfer- major (2)
red to is not valid for a transfer, it should be reset to ensure that the zone
controller has the latest database information
158 The zone controller status on originating system is not valid for a database major (2)
transfer
159 The zone controller on the transfer to system was not reset during the data- warning (4)
base transfer, this should be done manually to ensure that the zone control-
ler has the latest database information
180 Replication to the server is DOWN, database synchronization is required major (2)
186 Sending data to ZC resulted in SNMPError major (2)
187 Sending data to PDR resulted in SNMPError major (2)
188 Sending data to EBTS resulted in SNMPError major (2)
189 Sending data to MTIG resulted in SNMPError major (2)
190 ZC replied with bad response normal (6)
191 PDR replied with bad response normal (6)
192 EBTS replied with bad response normal (6)
193 MTIG replied with bad response normal (6)
194 Database update exception during receiving configuration data warning (4)
Table continued…


Code
211 Scheduled Backup Started normal (6)
212 Scheduled Backup Succeeded normal (6)
213 Scheduled Backup Interrupted minor (3)
214 Scheduled Backup Failed major (2)
215 Manual Backup Started normal (6)
216 Manual Backup Succeeded normal (6)
217 Manual Backup Interrupted minor (3)
218 Manual Backup Failed major (2)
299 Undefined status of UCS backup major (2)
ZoneController
The following table lists the transient alarm text for the ZoneCntlr object.
Table 204: Transient Alarm Text for the ZoneCntlr Object

Code
1280 SZM Add MG ID Does Not Exist warning (4)
1281 SZM Add MG ID is Not a MG warning (4)
1282 SZM Add TG ID Does Not Exist warning (4)
1283 SZM Added a TG Associated To Another MG warning (4)
1284 SZM Add TG ID is Not a TG warning (4)
1285 SZM Del TG from a non-existent MG warning (4)
1286 SZM Delete of TG from wrong MG warning (4)
1287 SZM Delete of TG from non-existent MG warning (4)
1288 SZM Delete of non-existent TG from an MG warning (4)
1289 SZM Delete of TG which has no MG warning (4)
1290 SZM Delete of TG which is really MG warning (4)
1291 Get Ind auth Rec Buffer Failure warning (4)
1292 Get Individual Rec Buffer Failure major (2)
1293 Get TG Rec Buffer Failure major (2)
1294 Get Individual TG Tree Buffer Failure major (2)
1295 Get TG Tree Buffer Failure major (2)
1296 SZM Updating an Individual Rec That Does Not Exist warning (4)
1297 SZM Updating a TG ID that Does Not Exist warning (4)
1298 SZM Updating Ind auth With No IND Rec normal (6)
Table continued…


Code
1299 SZM Updating Ind auth, Interconnect Not Enabled normal (6)
1300 SZM Updating Ind auth that Does Not Exist normal (6)
1301 SZM Deleted a Individual Rec That Does Not Exist normal (6)
1302 SZM Deleted a TG ID That Does Not Exist warning (4)
1303 No Individual Rec to Del SZM Auth Rec warning (4)
1304 SZM Deleted a Auth Rec That Does Not Exist warning (4)
1305 SZM Add of Critical User Failed to Get Ind Rec major (2)
1306 SZM Add of Critical User Failed to Get TG Rec major (2)
1307 SZM Add of Critical User Max Exceeded major (2)
1308 SZM Delete of Critical User Failed to Get Ind Rec warning (4)
1309 SZM Delete of Critical User Failed to Get TG Rec warning (4)
1310 ISWP Return Individual Tree Buffer Failed major (2)
1311 ISWP Return TG Tree Buffer Failed major (2)
1312 Can Not Delete SiteWide TG Rec warning (4)
1313 Error Pending Message warning (4)
1314 SZM Secure Upgrade Mismatch warning (4)
1315 SZM TG Mod Type Undefined warning (4)
1316 SZM Secure Cap Int Rec Steering Mismatch warning (4)
1317 SZM Secure Cap Auth Rec Steering Mismatch warning (4)
1318 SZM Update Bad IND AUTH Rec Ptr warning (4)
1319 No Individual Rec To Delete Auth Rec From SZM warning (4)
1320 Op Changed its TG Affiliation normal (6)
1321 Unreserve Request From Delete Individual Record normal (6)
1322 Active TG Call Ended Due To TG SAC Deletion normal (6)
1323 Active MG Call Ended Due To MG SAC Deletion normal (6)
1324 Active Supergrp Call Ended Due To SAC Deletion normal (6)
1325 Active Emerg TG Call Ended Due To TG SAC Delete normal (6)
1326 Active Emerg MG Call Ended Due To MG SAC Delete normal (6)
1327 Busy TG Call Ended Due To TG SAC Deletion normal (6)
1328 Busy MG Call Ended Due To MG SAC Deletion normal (6)
1329 Busy Supergrp Call Ended Due To Supergrp SAC Del normal (6)
1330 Busy Emerg TG Call Ended Due To TG SAC Deletion normal (6)
1331 Busy Emerg TG Call Ended Due To MG SAC Deletion normal (6)
1332 Disp Interrupt Activity Ended Due To Ind SAC Del normal (6)
Table continued…


Code
1333 Active Ind Int Act Ended Due To Ind SAC Deletion normal (6)
1334 Busied Ind Int Act Ended Due To Ind SAC Deletion normal (6)
1335 Active PC Call Ended Due To Ind SAC Deletion normal (6)
1336 Busy PC Call Ended Due To Ind SAC Deletion normal (6)
1337 SZM Assoc TG and MG of Diff Resource Type major (2)
1338 Site Only TG Calls Without Console Flag is True warning (4)
1339 Site Only TG User Desig Site Mask is Not Empty warning (4)
1340 Site Only TG Mand Sites Mask is Not Empty warning (4)
1341 Site Only TG Interconnect Cap Flag not False warning (4)
1342 SZM added Mand or Crit Users to Site Only TG warning (4)
1343 TG Resource Type modified after orig creation warning (4)
1344 SZM attempt to modify a sitewide TG record warning (4)
1345 Console ind changed op warning (4)
1346 Console has user designated sites warning (4)
1347 Device Type Mismatch across zones major (2)
1348 Console illegally roamed across zones warning (4)
1349 Invalid TG/MG received in TG-MG association warning (4)
1350 Invalid TG/MG received in TG-MG disassociation warning (4)
1351 TG attributes cause patch incapable warning (4)
1352 TG deletion converted Repeat Disable to Repeat Enable. normal (6)
1353 TG deletion converted Tactical Priority to Normal Priority normal (6)
1362 VLR failed to decrypt a KEKm or KEKz that received from the AuC normal (6)
1367 A cell is being referred to as a neighbour by a large number of other cells: warning (4)
site ID, zone ID
1377 Get a headnumber and console association tree buffer fails. warning (4)
1536 CZ Get TG Buffer Failed warning (4)
1537 CZ Get TG Tree Buffer Failed warning (4)
1792 GHLR could not retrieve TG tree node buffer warning (4)
1793 GHLR could not retrieve TG subscriber node buffer warning (4)
Table continued…


Code
1794 GHLR could not retrieve atts tree node buffer warning (4)
1795 GHLR could not retrieve ind atts tracking buffer warning (4)
1796 The GHLR tried to update a talkgroup subscriber record that was referenc- major (2)
ing an talkgroup capabilities profile that didnt exist
1797 The GHLR tried to update a talkgroup subscriber record that was referenc- major (2)
ing an talkgroup all zone profile that didnt exist
1798 The GHLR tried to delete a talkgroup capabilities profile record that was major (2)
still being referenced by one or more subscriber records
1799 The GHLR tried to delete a talkgroup all zone profile record that was still major (2)
being referenced by one or more subscriber records
2048 IHLR could not retrieve ind tree node buffer warning (4)
2049 IHLR could not retrieve ind subs node buffer warning (4)
2050 IHLR could not retrieve ind authorization buffer warning (4)
2051 IHLR could not retrieve atts tree node buffer warning (4)
2052 The IHLR tried to update an individual subscriber record that was referenc- major (2)
ing an individual capabilities profile that didnt exist
ing an individual interconnect profile that didnt exist
ing an individual all zone profile that didnt exist
2055 The IHLR tried to delete an individual capabilities profile record that was major (2)
2056 The IHLR tried to delete an individual interconnect profile record that was major (2)
2057 The IHLR tried to delete an individual all zone profile record that was still major (2)
being referenced by one or more subscriber records
2061 IHLR could not retrieve individual atts buffer major (2)
2062 ZC Active-Standby Ki validation failure normal (6)
2063 A console which is associated with a Head Number registered in a zone dif- warning (4)
ferent from the location of the Head Number.
256 Invalid Radio Requestor ID warning (4)
Table continued…


Code
257 The consoles individual ID is invalid. The console information of the re- warning (4)
quest is given. Ind, Slot: 0 based. Tline, AEB: 1 based. IP based consoles
will set the AEB, Tline, and Lot to 254.
258 Invalid HLR Individual ID warning (4)
259 Radio Individual SAC Record Not Available minor (3)
260 Invalid Group ID from Radio warning (4)
261 The Group ID sent by the Console is Invalid. The console information of warning (4)
the request is given. Ind, TG, Slot: 0 based. AEB, Tline: 1 based. IP based
consoles will set the AEB, Tline, and Slot to 254.
262 Invalid HLR Group ID warning (4)
263 Radio Emergency Request Downgraded normal (6)
264 The console is requesting an emergency on a Group that is not allowed to warning (4)
have emergency calls. The console information of the request is given. Ind,
TG, Slot: 0 based. AEB, Tline: 1 based. IP based consoles will set the
AEB, Tline, and Slot to 254.
265 Radio TG Request made on MG Group warning (4)
266 Console TG Request made on MG Group warning (4)
267 Radio MG Request made on TG Group warning (4)
268 Console MG Request made on TG Group warning (4)
269 Radio Request with Console Individual ID major (2)
270 A console device is using a Radio ID. The console information of the re- critical (1)
quest is given. Ind, Slot: 0 based. AEB, Tline: 1 baesd. IP based consoles
will set the AEB, Tline, and Slot to 254.
271 Mismatched TG to MG Warning warning (4)
272 Invalid Single Word ISW minor (3)
273 Invalid Dual Word ISW minor (3)
274 Dynamic Group TG Request made on MG Group warning (4)
275 Dynamic Group MG Request made on TG group warning (4)
276 Invalid Console OP Information in Packet minor (3)
277 Too Many AEB Slots Configured for Consoles critical (1)
278 Assign Op Location Already Assigned warning (4)
279 Get PND Command Block Failure warning (4)
280 Analog Individual Tried to Affiliate to ASTRO TG warning (4)
281 Sub-band Restricted Individual Tried to Affiliate to Non Sub-band Capable warning (4)
Talkgroup
282 Invalid grid OP ID received warning (4)
283 Radio request made by grid op ID major (2)
Table continued…


Code
284 Radio request made by console op ID major (2)
285 Grid op request made by radio ID critical (1)
286 Grid op request made by console op ID critical (1)
287 Could not get DFB information block warning (4)
288 CP/PZ failed to send logging packets warning (4)
289 IZ Mismatch - MG Request on TG warning (4)
290 IZ Mismatch - Different Modulation Types warning (4)
291 Invalid group ID received from ONM warning (4)
292 Different modulation types for PC warning (4)
293 Mismatched modulation tables between zones major (2)
294 Two console devices are using the same ID. The console info of the request warning (4)
that exposed the duplicate is given with the conflicting consoles info. Ind,
Slot, TG: 0 based. AEB, Tline: 1 based. IP based consoles will set the
AEB, Tline, and Slot to 254.
295 Console op logging device status changed warning (4)
296 Console op out of service critical (1)
297 IZ Mismatch - TG Request on MG warning (4)
298 The target id received from SU is not the RCM ID warning (4)
299 An Individual ID is equivalent to the RCM ID warning (4)
300 Radio Emergency Request Not Emergency Capable warning (4)
301 The number of affiliated IP based console ops has exceeded the maximum warning (4)
limit a Zone Controller can support.
302 RF Interference on channel during call (Site Number, Channel Number: warning (4)
Zero-based; Call number: One- based)
303 A radio is using a head number ID. The radio information of the request is major (2)
given. Ind, Site Number: 0 base.
304 A console is using a head number ID. The console information of the re- major (2)
quest is given. Ind, Slot: 0 basedAEB, Tline: 1, basedIP based consoles will
set the AEB, Tline, and Slot to 254.
4096 InterZone Mux Mismatch major (2)
4097 InterZone Channel Misconfiguration major (2)
4098 AEB ID Mismatch. Expected major (2)
4099 Slot Modulation Type must be Astro/Analog Clear major (2)
512 Radio protection timer expired warning (4)
513 Console op slot already assigned to another device critical (1)
514 Failed to allocate buffer for ATS info block warning (4)
515 CZ failed to send logging packets warning (4)
Table continued…


Code
516 The number of IP based console ops that can support patch/msel/repeat dis- warning (4)
able activity have exceeded the maximum limit a Zone Controller can sup-
port.
8006 Receive Agent Own Change Flag - Flag changed minor (3)
8007 Receive Agent Own Change Flag - Flag cleared minor (3)

581 | Advanced NM - Differences Appendix
Appendix
C
Advanced NM - Differences Appendix
This part covers differences for Dimetra IP Micro/Dimetra LiTE system in relation to Dimetra IP system. It
concentrates on the descriptions of what is not applicable in Dimetra IP Micro/Dimetra LiTE in comparison to
Dimetra IP system.
Advanced NM – User Configuration Manager (UCM)

The following objects do not exist in User Configuration Manager for Dimetra IP Micro/Dimetra LiTE:
• Zone to Alias Server Map
• User Group
• Security Group
• ZoneWatch Configuration
While using the User Configuration Manager, do not use sections where they are described.
CAD User may be added if an appropriate licence is purchased.
There are also objects which are visible in the GUI but they should not be configured. These are:
• InterZone Control Path
• Control Room Head Number
• External Configuration
In the User object, it is not possible to create new users.
In the Dimetra IP Micro/Dimetra LiTE, when creating the Status Set in UCM, you can create up to 100 messages.
The Status Number parameter is fixed and not configurable. The range of the preconfigured Status Number is
32768 – 32867.
For details on configuration and operation of the UCM, see User Configuration Manager.
Advanced NM – Zone Configuration Manager (ZCM)

In ZCM for Dimetra IP Micro/Dimetra LiTE, Alias Server object is not present, so please do not use any sections
describing it.
The Zone Controller object – as there is only one Zone Controller in Dimetra IP Micro/Dimetra LiTE system, you
cannot create new ones in ZCM.
Just as in UCM, some objects are visible in the GUI, but they should not be configured in any way:
• Air Traffic Router
• Control RP Router
• Core RP Router
• MGEG Application Platform
• EBTS Site

582 | Advanced NM - Differences Appendix
• Switch
There are the following changes in structure:
• The number of the MTSs is equal to the number of purchased licenses.
• By default there is one Console Site with a complete configuration. A Console Site can contain up to 5 consoles.
Note: You should not add more consoles, even though there is such a possibility. The system does not
support more than 5.
Important: Zone object – do not change anything in the Redundancy Configuration tab.
For more details on configuration and maintaining operational parameters for equipment in a system using ZCM, see
Zone Configuration Manager.
Advanced NM – Radio Control Manager (RCM)

The only difference in Dimetra IP Micro/Dimetra LiTE system is that there are no RCM Reports.
The rest of the functionality remains the same. For details, see Radio Control Manager.

ConfigurationAndManagement DIPM30 RevC

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ConfigurationAndManagement DIPM30 RevC

Caricato da

Copyright:

Formati disponibili

System Release 3.

© 2014 Motorola Solutions, Inc. All rights reserved

European Union (EU) Waste of Electrical and Electronic Equipment (WEEE)

68015000619-C | April 2014 | Send Feedback

CMM Labeling and Disclosure Table

68015000619-C | April 2014 | Send Feedback

Table 1: List of Telephone Numbers

Country In Country Number to Dial

European Systems Component Centre (ESCC)

68015000619-C | April 2014 | Send Feedback

• Telefax: +49 (0) 30 66861426

Parts Identification and Ordering

Updated Versions of Manuals

Send Feedback | April 2014 | 68015000619-C

68015000619-C | April 2014 | Send Feedback

Performing Software Update.................................................................................................................117

Chapter 3: Reference........................................................................................... 137

Appendix A: Network Configuration File Guidelines...................................... 199

Minimal Configuration for Local MTS Only........................................................................................200

Appendix B: Alarm Guidelines...........................................................................231

Appendix C: Advanced NM - Differences Appendix........................................581

Figure 34: Modify Multigroup Page ...............................................................................................68

Figure 104: Status Page ................................................................................................................ 137

Figure 139: Example of Diagnostics Command Page .................................................................. 197

Table 34: Parameters for the Telephone Interconnect .................................................................. 178

Table 120: State/Cause Text for the MtsOutputSignals Object ....................................................398

68015000619-C | April 2014 | Send Feedback

68015000619-C | April 2014 | Send Feedback

Deleting an MTS Site ..................................................................................................................... 85

Send Feedback | April 2014 | 68015000619-C

Performing Diagnostics ................................................................................................................ 133

68015000619-C | April 2014 | Send Feedback

About Configuration and Management

What Is Covered In This Manual?

Helpful Background Information

68015000619-C | April 2014 | Send Feedback

Send Feedback | April 2014 | 68015000619-C

68015000619-C | April 2014 | Send Feedback

68015000619-C | April 2014 | Send Feedback

Starting Up the Web NM

Figure 1: Login Window

68015000619-C | April 2014 | Send Feedback

Figure 2: Web NM Page

Web NM Main Window Structure

Figure 3: Web NM Main Window Elements

Send Feedback | April 2014 | 68015000619-C

Figure 4: Example of the Status Page

68015000619-C | April 2014 | Send Feedback

Monitoring the State and Cause of System Alarms

Figure 5: Example of a List of Components of One Element

Send Feedback | April 2014 | 68015000619-C

Figure 6: Example of Status Changes of an Object

Identifying and Troubleshooting the State and Cause

Table 2: Example of Alarm Messages

68015000619-C | April 2014 | Send Feedback

Downloading the Events

Figure 7: File Download Dialog Box

Send Feedback | April 2014 | 68015000619-C

Figure 8: Example of Downloaded Events in the .csv File

Figure 9: Configuration Page

Configuring a Radio User Capabilities Profile

68015000619-C | April 2014 | Send Feedback

Figure 10: Radio User Capabilities Profile Page