Reference Manual - WillowCherry.COM

Transcription

411-8111-803
GSM / UMTS Voice Core Network
OAM
Reference Manual
GSM18/UMTS04 Standard 01.06 May 2006
DRAFT
test
OAM
Reference Manual
Document number: 411-8111-803
Product release: GSM18/UMTS04
Document version: Standard 01.06
Date: May 2006
Copyright Country of printing Confidentiality Legal statements Trademarks
Copyright © 2004–2006 Nortel Networks, All Rights Reserved
Originated in the United States of America
NORTEL NETWORKS CONFIDENTIAL
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees
with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree
of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant.
* Nortel Networks, the Nortel Networks logo, the Globemark HOW the WORLD SHARES IDEAS, and Unified Networks are
trademarks of Nortel Networks. DMS, DMS-HLR, DMS-MSC, MAP, and SuperNode are trademarks of Nortel Networks. GSM is a
trademark of GSM MOU Association.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
ii
Nortel Networks Confidential
Copyright © 2004–2006 Nortel Networks
The following apply to components or elements used in the GEM load and are
used by permission of the respective owners.
Copyright notice/license for Perl
Preamble:
The intent of this document is to state the conditions under which a Package
may be copied, such that the Copyright Holder maintains some semblance of
artistic control over the development of the package, while giving the users of
the package the right to use and distribute the Package in a more-or-less
customary fashion, plus the right to make reasonable modifications.
Definitions:
“Package” refers to the collection of files distributed by the Copyright Holder,
and derivatives of that collection of files created through textual modification.
“Standard Version” refers to such a Package if it has not been modified, or has
been modified in accordance with the wishes of the Copyright Holder as
specified below.
“Copyright Holder” is whoever is named in the copyright or copyrights for
the package.
“You” is you, if you're thinking about copying or distributing this Package.
“Reasonable copying fee” is whatever you can justify on the basis of media
cost, duplication charges, time of people involved, and so on. (You will not be
required to justify it to the Copyright Holder, but only to the computing
community at large as a market that must bear the fee.)
“Freely Available” means that no fee is charged for the item itself, though there
may be fees involved in handling the item. It also means that recipients of the
item may redistribute it under the same conditions they received it.
1. You may make and give away verbatim copies of the source form of the
Standard Version of this Package without restriction, provided that you
duplicate all of the original copyright notices and associated disclaimers.
2. You may apply bug fixes, portability fixes and other modifications derived
from the Public Domain or from the Copyright Holder. A Package
modified in such a way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way,
provided that you insert a prominent notice in each changed file stating
how and when you changed that file, and provided that you do at least
ONE of the following:
a. place your modifications in the Public Domain or otherwise make
them Freely Available, such as by posting said modifications to
411-8111-803
Standard
01.06
May 2006
Publication history iii
Usenet or an equivalent medium, or placing the modifications on a
major archive site such as uunet.uu.net, or by allowing the Copyright
Holder to include your modifications in the Standard Version of the
Package.
b. use the modified Package only within your corporation or
organization.
c. rename any non-standard executables so the names do not conflict
with standard executables, which must also be provided, and provide a
separate manual page for each non-standard executable that clearly
documents how it differs from the Standard Version.
d. make other distribution arrangements with the Copyright Holder.
4. You may distribute the programs of this Package in object code or
executable form, provided that you do at least ONE of the following:
a. distribute a Standard Version of the executables and library files,
together with instructions (in the manual page or equivalent) on where
to get the Standard Version.
b. accompany the distribution with the machine-readable source of the
Package with your modifications.
c. give non-standard executables non-standard names, and clearly
document the differences in manual pages (or equivalent), together
with instructions on where to get the Standard Version.
d. make other distribution arrangements with the Copyright Holder.
5. You may charge a reasonable copying fee for any distribution of this
Package. You may charge any fee you choose for support of this Package.
You may not charge a fee for this Package itself. However, you may
distribute this Package in aggregate with other (possibly commercial)
programs as part of a larger (possibly commercial) software distribution
provided that you do not advertise this Package as a product of your own.
You may embed this Package's interpreter within an executable of yours
(by linking); this shall be construed as a mere form of aggregation,
provided that the complete Standard Version of the interpreter is so
embedded.
6. The scripts and library files supplied as input to or produced as output
from the programs of this Package do not automatically fall under the
copyright of this Package, but belong to whoever generated them, and
may be sold commercially, and may be aggregated with this Package. If
such scripts or library files are aggregated with this Package via the socalled "undump" or "unexec" methods of producing a binary executable
image, then distribution of such an image shall neither be construed as a
distribution of this Package nor shall it fall under the restrictions of
Paragraphs 3 and 4, provided that you do not represent such an executable
image as a Standard Version of this Package.
OAM Reference Manual
GSM18/UMTS04
iv Publication history
7. C subroutines (or comparably compiled subroutines in other languages)
supplied by you and linked into this Package in order to emulate
subroutines and variables of the language defined by this Package shall
not be considered part of this Package, but are the equivalent of input as in
Paragraph 6, provided these subroutines do not change the language in
any way that would cause it to fail the regression tests for the language.
8. Aggregation of this Package with a commercial distribution is always
permitted provided that the use of this Package is embedded; that is, when
no overt attempt is made to make this Package's interfaces visible to the
end user of the commercial distribution. Such use shall not be construed
as a distribution of this Package.
9. The name of the Copyright Holder may not be used to endorse or promote
products derived from this software without specific prior written
permission.
10. This package is provided “as is” and without any express or implied
warranties, including, without limitation, the implied warranties of
merchantibility and fitness for a particular purpose.
The standard version of the Perl interpreter is obtained from the following
link: http://www.perl.com/pub/a/language/info/software.html
Copyright notice/license for Zlib library for data compression
(C) 1995-1998 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty. In
no event will the authors be held liable for any damages arising from the use
of this software.
Permission is granted to anyone to use this software for any purpose, including
commercial applications, and to alter it and redistribute it freely, subject to the
following restrictions:
1. The origin of this software must not be misrepresented; you must not
claim that you wrote the original software. If you use this software in a
product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly: [email protected]
Mark Adler: [email protected]
411-8111-803
Standard
01.06
May 2006
v
Publication history
May 2006
GSM18/UMTS04, Standard, 01.06.
December 2005
October 2005
October 2005
GSM18/UMTS04, Preliminary, 01.03.
March 2005
GSM18/UMTS04, Preliminary, 01.02. This document release includes review
comments and updated operational measurements information.
December 2004
GSM18/UMTS04, Draft, 01.01. First release of this document.
GSM18/UMTS04
vi Publication history
411-8111-803
Standard
01.06
May 2006
vii
Contents
1
About this document
xv
Notice of design intent and enhancement xv
Audience for this document xv
Organization of this document xvi
Related documents xvii
Software release applicability xviii
CEM overview for Voice Core Network
1-1
GSM/UMTS core network and TMN relationship 1-2
OMC-S components 1-2
Types of elements managed by OMC-S 1-5
SDM/FT and CBM 1-6
CEM support for R4 BICN/BICC 1-16
CEM support for HLR 200 1-24
CEM support for NEs in W-NMS environment 1-42
CEM support for IWF 1-49
Operational measurements
2-1
Supported OMs 2-2
Summary OMs 2-16
Correlated OMs 2-17
HLR100 correlated OMs 2-81
MSC correlated OMs 2-85
DMS-VLR correlated OMs 2-89
Billing OMs 2-92
CEM logs
How logs are defined 3-2
Log example 3-3
Logs shown in this chapter
Field descriptions 3-12
CEMDS100 3-14
CEMDS101 3-15
CEMDS102 3-16
CEMDS103 3-19
CEMDS104 3-22
3-1
3-4
GSM18/UMTS04
viii Contents
CEMDS105 3-22
CEMDS106 3-23
CEMDS107 3-24
CEMDS199 3-25
CEMDS200 3-26
CEMDS201 3-26
CEMDS202 3-27
CEMDS203 3-28
CEMDS204 3-29
CEMDS205 3-29
CEMDS206 3-30
CEMDS207 3-31
CEMDS208 3-31
CEMDS209 3-32
CEMDS210 3-32
CEMDS301 3-33
CEMDS302 3-34
CEMDS303 3-34
CEMDS600 3-35
MON001 3-35
MON002 3-36
MON003 3-37
MON004 3-37
MON005 3-38
MON006 3-39
MON007 3-40
MON008 3-40
OSA302 3-41
OSA303 3-42
OSA304 3-42
OSA305 3-43
OSA306 3-43
OSA307 3-44
OSA308 3-45
OSA602 3-45
OSA603 3-46
OSA604 3-46
TMN301 3-47
TMN302 3-48
TMN303 3-53
TMN304 3-56
TMN305 3-61
TMN306 3-64
TMN307 3-74
TMN308 3-94
TMN309 3-94
TMN310 3-95
TMN311 3-97
TMN312 3-99
TMN313 3-100
TMN314 3-101
411-8111-803
Standard
01.06
May 2006
Contents ix
TMN317
TMN318
TMN319
TMN341
TMN342
TMN343
TMN600
TMN601
TMN603
TMN604
TMN605
TMN610
TMN614
TMN618
TMN619
3-101
3-102
3-105
3-105
3-106
3-107
3-107
3-111
3-111
3-113
3-116
3-117
3-117
3-118
3-119
Logs index
4-1
CEM browser icons
5-1
General rules 5-1
Terminal resources 5-3
Performance management resources
Square containers 5-4
Barrel containers 5-5
Link icons 5-6
Network element icons 5-7
5-4
Mapped resources
6-1
XA-Core and MMU components 6-2
Application subsystem 6-11
CCS subsystem 6-14
CompCore 6-18
EXT 6-35
IOD 6-37
MS 6-46
NET 6-58
PM 6-75
SPM 6-94
Software subsystem 6-108
Trunk group container 6-109
Mapped resources for OM groups 6-111
Index
A-1
Figures
Figure 1-1
Figure 1-2
Figure 1-3
Figure 1-4
Figure 1-5
OMC-S System Components 1-4
SDM/FT cabinet 1-6
SDM/FT architecture 1-7
SDM in server mode 1-7
SDM in stand-alone mode 1-8
GSM18/UMTS04
x Contents
Figure 1-6
Figure 1-7
Figure 1-8
Figure 1-9
Figure 1-10
Figure 1-11
Figure 1-12
Figure 1-13
Figure 1-14
Figure 1-15
Figure 1-16
Figure 1-17
Figure 1-18
Figure 1-19
Figure 1-20
Figure 1-21
Figure 1-22
Figure 1-23
Figure 1-24
Figure 1-25
Figure 3-1
Figure 5-1
Figure 5-2
Figure 5-3
Figure 5-4
Figure 6-1
Figure 6-2
Figure 6-3
Figure 6-4
Figure 6-5
Figure 6-6
Figure 6-7
Figure 6-8
Figure 6-9
Figure 6-10
Figure 6-11
Figure 6-12
Figure 6-13
Figure 6-14
Figure 6-15
Figure 6-16
Figure 6-17
Figure 6-18
CBM architecture 1-9
GSM - CBM - CEM server platform 1-10
OMC-S software 1-11
Telnet/FTP via SDM Functional Diagram 1-14
CEM Interface with MDM 1-16
SGW NE model 1-21
MSC model containing USP components 1-22
Network overview of HLR200 interacting with R4 BICN 1-24
HLR 200 Mini-Complex Network Connection Overview 1-25
Mated HLRs Managed by CEM 1-26
Object Model of HLR200 Memory Application and Associated
Objects 1-27
CEM View of the USP 1-31
CEM View of Passport 8600 1-32
CEM View of the SLR 1-33
Message Flow for SAM21 Fault Management 1-34
Message Flow for STORM Fault Management 1-35
CEM - DS Simplified View 1-36
Sun MC Collects Information from Data Server Agents 1-37
Simplified W-NMS architecture with CEM 1-43
CEM Server Management of SLR and MDM 1-46
Example log 3-3
Terminal resources icon 5-3
Performance management resources icon 5-4
Square container icon 5-4
Barrel containers icon 5-5
Top Level 6-2
Component Layout 6-2
MMU Layout 6-3
XA Core Layout 6-5
MultiCore Layout 6-5
Application Level 6-11
Common Channel Signaling 6-14
compCore (SuperNode) 6-18
EXT 6-35
Input Output Device 6-37
Message Switch 6-46
Network 6-59
Peripheral Module 6-75
File Processor 6-76
SPM Components Layout 6-94
HSCarriers Layout 6-101
Software Subsystem 6-108
Trunk Groups 6-109
Tables
Table 1-1
Table 1-2
Table 1-3
Table 1-4
411-8111-803
Standard
Popular SDM tools renamed under CBM 1-12
List of Low-Water Mark Registers 1-19
Allowed Grouping Based on Passport Application Types 1-44
Allowed Re-typing Based on Passport Application Types 1-45
01.06
May 2006
Contents xi
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
Table 2-6
Table 2-7
Table 2-8
Table 2-9
Table 2-10
Table 2-11
Table 2-12
Table 2-13
Table 2-14
Table 2-15
Table 2-16
Table 3-1
Table 3-2
Table 3-3
Table 3-4
Table 3-5
Table 3-6
Table 4-1
Table 5-1
Table 5-2
Table 5-3
Table 6-1
Table 6-2
Table 6-3
Table 6-4
Table 6-5
Table 6-6
Table 6-7
Table 6-8
Table 6-9
Table 6-10
Table 6-11
Table 6-12
Table 6-13
Table 6-14
Table 6-15
Table 6-16
Table 6-17
Table 6-18
Table 6-19
Table 6-20
Table 6-21
Table 6-22
Supported MSC/VLR OM groups 2-2
Supported single-tuple MSC OM groups 2-5
Supported multi-tuple MSC/VLR OM groups 2-6
Supported single-tuple Base OM groups 2-8
Supported multi-tuple Base OM groups 2-10
Supported single-tuple HLR100 OM groups 2-11
Supported multi-tuple HLR100 OM groups 2-14
Correlated MSC OM groups 2-17
Correlated OMs related to G-SGSN 2-48
Correlated OMs related to U-SGSN 2-62
Correlated OMs related to GGSN 2-73
Correlated OMs (hlrMeasurementFunction1
hlrMeasurementFunction2) related to HLR100 2-81
Correlated OMs (mscMeasurementFunction) related to MSC 2-85
Correlated OMs (vlrMeasurementFunction) related to DMS-VLR 2-89
Correlated OMs (vlrMeasurementFunction1) related to DMS-VLR 290
OM groups derived from billing data 2-92
Event class definitions 3-2
OMC-S/CEM system log summary 3-4
Logs raised on the CEM by modules running within a DS Sun MC
agent 3-8
Logs raised by the mated pair monitor 3-11
OMC-S/CEM system log field descriptions 3-12
Mated pair monitor log field descriptions 3-12
VCN Logs collected by OMC-S 4-2
|General Rules 5-1
Link Icons 5-6
NE Type Icons 5-7
mobilityManagementPool 6-3
mobilityManagementUnit 6-3
Extended Architecture Core 6-6
xacSharedMemory 6-7
processorElement 6-8
inputOutputProcessor 6-8
coreMSInterConnect 6-9
remoteTerminalInterface 6-9
xacTape 6-10
xacDisk 6-10
SDM 6-11
DRM 6-12
LKSET Subsystem 6-14
LINK 6-15
RTESET Subsystem 6-15
ROUTE 6-16
MOD 6-19
CONS 6-20
Image Dump 6-21
DST 6-22
CM 6-24
CM_MNT 6-27
GSM18/UMTS04
xii Contents
Table 6-23
Table 6-25
Table 6-24
Table 6-26
Table 6-27
Table 6-28
Table 6-29
Table 6-30
Table 6-31
Table 6-32
Table 6-33
Table 6-34
Table 6-35
Table 6-36
Table 6-37
Table 6-38
Table 6-39
Table 6-40
Table 6-41
Table 6-42
Table 6-43
Table 6-44
Table 6-45
Table 6-46
Table 6-47
Table 6-48
Table 6-49
Table 6-50
Table 6-51
Table 6-52
Table 6-53
Table 6-54
Table 6-55
Table 6-56
Table 6-57
Table 6-58
Table 6-59
Table 6-60
Table 6-61
Table 6-62
Table 6-63
Table 6-64
Table 6-65
Table 6-66
Table 6-67
Table 6-68
Table 6-69
Table 6-70
Table 6-71
Table 6-72
Table 6-73
411-8111-803
Standard
PMC-0 6-28
Mem Proc 6-29
Link-0/1 6-29
MC-0/1 6-30
MC Resources 6-31
CPU-0/1 6-32
SLM-0/1 6-32
SLM Devices 6-33
SoftAlarm 6-35
scapPoint 6-36
iodProtocol 6-37
DIRP Subsystem 6-38
DIRP 6-38
IOC Subsystem 6-39
DDU 6-39
MTD 6-41
MAP 6-42
MPC 6-43
DPACDEV 6-44
NX25 6-45
MS-0/1 6-46
DS-512 Chains 6-47
Link-0/1 6-48
Ports 6-49
Clock 6-50
CMIC 6-51
DS30 6-51
DS512 6-52
PBUS 6-53
Memory 6-54
TBusAcc 6-54
MSP 6-56
TFI 6-56
Taps 6-58
enetPlane 6-59
enetMatrix 6-60
ENET-0/1 6-61
enetShelf 6-61
enetPowerCard 6-62
enetXPoint 6-64
enetProcessor 6-65
enetClock 6-66
enetMsgLink 6-67
enetRTIF 6-68
enetDS30 6-69
enetDS30DS512 6-70
enetDS512 6-72
enetLink 6-73
enetFiber 6-74
FP 6-76
fpPlane 6-78
01.06
May 2006
Contents xiii
Table 6-74
Table 6-75
Table 6-76
Table 6-77
Table 6-78
Table 6-79
Table 6-80
Table 6-81
Table 6-82
Table 6-83
Table 6-84
Table 6-85
Table 6-86
Table 6-87
Table 6-88
Table 6-89
Table 6-90
Table 6-91
Table 6-92
Table 6-93
Table 6-94
Table 6-95
Table 6-96
Table 6-97
Table 6-98
Table 6-99
Table 6-100
Table 6-101
Table 6-102
Table 6-103
Table 6-104
Table 6-105
Table 6-106
Table 6-107
Table 6-108
Table 6-109
Table 6-110
Table 6-111
Table 6-112
fpPortCard 6-78
fpCPU 6-79
fpPlink 6-80
fpDRAM 6-81
fpMsgCh 6-82
fpDABM 6-82
fpSCSI 6-83
fpDevice 6-84
LIM 6-85
FBUS-0/1 6-86
Taps 6-86
LIU 6-87
LIU Type PMs 6-88
DTC/DTCI/PDTC 6-88
pcmDS1 6-90
pcmD30 6-90
pcmTTC 6-91
pcmM20 6-92
pcmNDS0 6-92
TM Resources 6-93
SPM 6-96
CEM 6-98
spmModule 6-99
oc3Section (or STM1R) 6-101
STS3Line 6-102
hsCarrier=STS1/ STS3cP/VT15P/DS3P/STM1M/VC12P/VC4P/
E1P 6-103
DS1Path 6-104
Default Datafill of Alarm 6-105
TRKGRP 6-109
Trunk 6-110
Mapping of U-SGSN OM groups 6-111
Mapping of G-SGSN OM groups 6-112
Mapping of GGSN Shasta OM groups 6-115
Mapping of SIG OM groups 6-116
Mapping of AN OM groups 6-116
Mapping of USP (HLR peripheral ) OM groups 6-116
Mapping of SLR / UNPM OM groups 6-118
Mapping of SGW ( MSC peripheral ) OM groups 6-120
Mapping of SGW (stand alone) OM groups 6-123
GSM18/UMTS04
xiv Contents
411-8111-803
Standard
01.06
May 2006
xv
About this document
1
This document describes the functionality of the Core Element Manager for
the Global System for Mobile Communications (GSM) Digital Multiplex
System Home Location Register (DMS-HLR). It also applies to the 3G
UMTS Voice Core Networks Home Location Register (VCN HLR).
In this document, VCN MSC/HLR designates either of these voice core
network elements.
Notice of design intent and enhancement
1
The design intent is reflected in the level of detail in the Nortel Technical
Publications (NTP) regarding the following elements:
• Logs
•
Parameters
•
Data Schema
•
Tables
•
OMs
Starting at GSM13, enhanced attributes were developed to define and
document these GSM elements. However, for those elements introduced prior
to GSM13, the user will find a minimalist level of documentation to represent
these elements. This level of documentation reflects the original design intent.
Audience for this document
1
This document is intended for persons involved in the engineering,
administration, operation, maintenance, and provisioning (OAM&P) of the
Voice core network elements (MSC/HLR) using the OMC-S applications on
the SuperNode Data Manager Fault-tolerant (SDM/FT) and a PC or Sun Core
Element Manager workstation. This document describes the following
functions:
• Configuration Management (CM) Resource Discovery - automatically
show hardware and software components contained within the managed
Voice core network elements.
GSM18/UMTS04
xvi About this document
•
Fault Management (FM) - view active and cleared alarms from a MSC/
HLR and access the MSC/HLR sub-elements in a manner similar to a
Nortel Maintenance and Administration Position (MAP).
•
Performance Management (PM) - retrieve and view operational
measurements (OMs) of a MSC/HLR.
To best use this document, the reader should have knowledge of the following
topics:
• TMN standards - The Core Element Manager requires at least a high-level
understanding of TMN standards to interpret the TMN Open System
Interconnection (OSI) states. These states reflect the different attributes of
components and elements.
•
European Telecommunication Standards - For the Core Element Manager,
the system administrator must have a high-level understanding of the
operational measurements described in the GSM 12.04 standards.
•
Voice Core Network knowledge - Required to understand the hierarchy of
the VCN MSC/HLR components and elements.
•
MAP knowledge - Required to use the Maintenance and Administration
Position Command Interpreter (MAPCI) interface.
Organization of this document
1
This document includes the following sections:
• Overview - Description of CEM relative to Voice Core Network.
•
Operational measurements - A list of supported, correlated, summary and
billing OMs collected by Performance Management.
•
OMC-S/CEM system logs - Identifies the logs produced by the SDM and
any actions that may be taken to correct the identified problems.
•
Logs index - A log index.
•
CEM browser icons - A description of the icons and the rules that drive
the colors of the icons presented in the CEM browser.
•
Mapped resources - Detailed information on the resources mapped by the
Core Element Manager.
•
Index - An index to the topics covered in this document.
Indication of hypertext links
Hypertext links in this document are indicated in blue. If viewing a PDF
version of this document, click on the blue text to jump to the associated
section or page.
411-8111-803
Standard
01.06
May 2006
About this document xvii
Related documents
1
Refer to the following documents for more information on the Core Element
Management System:
• GSM / UMTS Voice Core Network OAM Upgrades, NTP 411-8111-233
•
GSM / UMTS Voice Core Network OAM User Guide, NTP 411-8111-503
•
GSM / UMTS Voice Core Network OAM Administration, Maintenance
and Troubleshooting Guide, NTP 411-8111-937
•
GSM / UMTS Peripheral Modules Release Document (2 Volumes), NTP
411-2231-599
Refer to the following documents for more information on specific network
elements of the Core Element Management System:
• SuperNode Data Manager Fault-tolerant (SDM/FT) User Guide, NTP
297-5061-906
•
GSM / UMTS MSC Operational Measurements Reference Manual (3
Volumes), NTP 411-2231-814
•
GSM / UMTS HLR100/200 Operational Measurements Reference
Manual, NTP 411-2831-814
•
GSM / UMTS MSC Log Reference Manual, NTP 411-2231-510
•
GSM / UMTS HLR100/200 Log Reference Manual, NTP 411-2831-510
•
GSM / UMTS HLR200 Solution Overview, NTP 411-2831-014
•
GSM / UMTS HLR200 Data Server Operations and User Guide, NTP
411-2831-330
•
GSM / UMTS MSC Office Parameters Reference Manual, NTP 411-2231455
•
GSM / UMTS HLR100/200 Office Parameters Reference Manual, NTP
411-2831-455
•
GSM / UMTS MSC MAP Commands Reference Manual, NTP 411-2231809
•
GSM / UMTS HLR100/200 MAP Commands Reference Manual, NTP
411-2831-809
Refer to the following documents for more information on the Wireless
Network Management System:
• Wireless Network Management System Administrator Guide, NTP 4115221-305
•
Wireless Network Management System Operator Guide, NTP 411-5221505
GSM18/UMTS04
xviii About this document
Software release applicability
1
Nortel software releases for the Wireless product are developed and identified
by the product lines. The GSM product line software is identified by the
letters GSM and a 2-digit number, such as GSM18, signifying the current
release in the GSM software stream.
This publication is applicable to the DMS-MSC Family offices that have the
GSM NSS18/UMTS VCN04 software release. Unless this publication is
revised, it also applies to offices that have software releases greater than GSM
NSS18/UMTS VCN04.
Customers must be running on NSS16 or NSS17 before they can upgrade to
NSS18. Since there is no GSM-R support on the MSC in NSS18, customers
on GSM-R NSS17 will not upgrade to NSS18. Customers on NSS16/
UMTS03 for the MSC, must upgrade to NSS18/UMTS04.
For more information about the new features contained in the GSM NSS18/
UMTS VCN04 software release, refer to the GSM / UMTS MSC Software
Delta, 411-2231-199, and the GSM / UMTS HLR100/200 Software Delta,
411-2831-199.
GSM18/UMTS04 Product Computing Module Loads
The NSS18 software load consists of GSM18 (MSC & HLR), GEM18 (SDM
or CBM, and CEM), and MG18 (Media Gateway) software.
Before GSM05, software loads were package-based loads. GSM05 was the
first DMS-MSC Product Computing Module Load (PCL). PCLs are
composed of layers of software, or Delivery Receivable Units (DRUs).
The following PCLs comprise the NSS18 software load:
• DMS CSP20 (BASE21, TL20, SHR20)
411-8111-803
•
XPM20
•
CBM18
•
USP10.0
•
SN07
•
Passport v3.7
•
SP21 (North America market)
•
SP17.2 (International market)
•
Media Gateway (MG) PCR6.1
•
GSM18/UMTS04 DRUs
Standard
01.06
May 2006
1-1
CEM overview for Voice Core Network 1
The Nortel Universal Mobile Telecommunication System (UMTS) Core
Network has three functional subnetworks. For each of these, there is a specific
Nortel Operations and Maintenance Center (OMC) management system.
• Voice Core Network - The OMC-S (switch) management system manages
the Voice Core Network elements, such as the MSC, VLR, HLR, and
AUC.
•
Packet Core Network- The OMC-D (data) management system manages
the Packet Core Network elements, such as the SSGN equipment and
GGSN.
•
Radio Access Network - The OMC-R (radio) management system
manages the Radio Access Core Network elements.
The GSM/UMTS Voice Core Network (VCN) Mobile services Switching
Center (MSC) is the Nortel third generation (3G) circuit switch. It is
responsible for subscriber connection services, as with the first generation
(1G) and second generation (2G) systems (GSM and GPRS, respectively).
To ensure a smooth transition from 2G (GSM and GPRS) to 3G (UMTS),
existing parts of the GSM and GPRS networks, such as the circuit switch and
packet switch, are being reused. This manual focuses on the Voice Core
Network Core Element Manager that manages the GSM/UMTS DMS MSC/
HLR network elements.
This manual documents the Core Element Manager (CEM) that manages the
administrative and maintenance operations of the GSM/UMTS DMS MSC/
HLR within a Public Land Mobile Network (PLMN). CEM Server and
applications provide the OAM&P functionality to many different type of
network elements, including: MSC/HLR, USP, SLR, UNPM GPRS_SGSN,
U_SGSN, GGSN Shasta, IWF, Media Gateway, AN LIG-D, SGW, Border
Gateway and Passports.
GSM18/UMTS04
1-2 CEM overview for Voice Core Network
GSM/UMTS core network and TMN relationship
1
The Core Element Manager (CEM) system is the Nortel implementation of a
Telecommunication Management Network (TMN). The TMN provides the
GSM/UMTS Voice Core Network with the following:
• An interconnection between the specific management applications that
are on workstations and operated by systems personnel, over a Local Area
Network/Wide Area Network (LAN/WAN) using Transmission Control
Protocol/Internet Protocol (TCP/IP).
•
An exchange of management information (data) between the management
applications and the various elements of the Core Network elements. In
the Voice Core Network, the management application is the CEM,
installed on a PC or Sun platform.
•
Mediation functionality (data accumulation, filtering, manipulation, and
transfer) between the DMS MSC/HLR network elements and the Core
Element Manager workstation.
OMC-S components
1
The OMC-S configuration includes the following voice core network
components (see Figure 1-1):
• Core Element Manager application on a PC or SUN Platform. The
workstation provides facilitator interaction between operations,
administration, maintenance, and provisioning (OAM&P) and the DMS
MSC/HLR network elements.
•
Core Element Manager (CEM) Server manages the administrative,
maintenance and provisioning operations within a Public Land Mobile
Network. CEM Server resides on a Sun Solaris 8 platform and is the
location of most of the CEM processes.
•
SuperNode Data Manager Fault-tolerant (SDM/FT) and Core Billing
Manager (CBM) within the TMN act on information as it passes between
voice core network elements and the workstations. The mediation
functions include:
— protocol and communication control - routing data, data
communications back up, security (for example, workstation access)
— data conversion - data handling functions, such as data collection, data
concentration, data formatting, and data translation
— decision making - creation of some alarm logs, thresholding
— data storage - data dictionaries, network configurations, equipment
identification, memory backup
•
411-8111-803
The operations function, on various hardware devices, is responsible for
processing telecommunications management information, which supports
Standard
01.06
May 2006
CEM overview for Voice Core Network 1-3
or controls various aspects of the TMN. The operations function is
executed on one or more devices that provide the following services:
— application program support
— database functions
— user terminal support
— analysis programs
— data formatting and reporting
— analysis and decision support
•
LAN/WAN network connections (data communications function) from
the Core Element Manager PC or SUN to each SDM using TCP/IP
protocol. The data communication network transports telecommunication
management information between functional entities and is primarily
responsible for routing or processing information passed between
standard interfaces.
GSM18/UMTS04
Figure 1-1
OMC-S System Components
CEM Browser on
PC or Sun Workstation
WAN/LAN
CEM Server
TCP/IP
TCP/IP
SDM/FT
C
SDM/FT
TCP/IP
MSC
TCP/IP
HLR100
Connections from DMS to SDM/FT to CEM Server established by NORTEL
Connections to TELCO LAN/WAN is responsibility of TELCO abiding by connection requirements
411-8111-803
Standard
01.06
May 2006
Types of elements managed by OMC-S
1
The following are examples of voice core network elements that can be
managed by Fault Manager (FM) and Configuration Manager (CM):
• mediation device (SDM)
•
call intercept applications (MSC and SDM)
•
message switch (MS)
•
enhanced network (ENET)
•
message controllers
•
DTC/PDTC (trunk controller)
•
trunk modules (such as the maintenance trunk modules and the service
trunk modules)
•
link peripheral processor (LPP)
•
link interface unit (LIU)
•
mobility management unit (MMU) or VLR processing
•
network interface unit (NIU)
•
ethernet interface unit (EIU)
The following are examples of network element resources that can be managed
by Fault Manager and Performance Manager (PM):
• trunks and trunk groups, including C7 signaling links, link sets, routes,
and route sets
•
Location Area Codes (LACs) that include group call IDs
•
computing modules (CMs) and extended architecture core (XACore)
modules
•
DMS MSC call processing and Visitor Location Register (VLR) functions
(as high-level logical components)
•
Voice Core Network (VCN) network elements, such as MSC, VLR, HLR,
AUC, EIR, and the signaling networks, communicate with the Core
Element Manager for the purpose of being monitored or controlled.
GSM18/UMTS04
SDM/FT and CBM
1
SDM/FT
The SuperNode Data Manager Fault-tolerant (SDM/FT or SDM) is a UNIXbased computing platform on which a variety of services and applications can
be hosted to provide Voice Core Network (VCN) OAM&P services. The
SDM includes redundant fiber connectivity to a single MSC or HLR.
The SDM configuration contains redundant hardware making it fault tolerant.
The SDM is based on custom Motorola FX Series hardware housed in a DMS
cabinet (Figure 1-2) and running an adapted version of IBM’s AIX operating
system.
Figure 1-2
SDM/FT cabinet
Outside view
Inside view
The SDM/FT connects to the switch by using a pair of DS512 links. Fault
Tolerant scheme in SDM/FT was made up of two parallel running domains. If
one fails, the mate can pick up with minimal service interruption. Figure 1-3
shows an overview of SDM/FT Architecture.
Note: Stand-alone SDM migration is supported for versions GEM16 and
up. An SDM, however, must first be upgraded to GEM18 due to changes
in databases and protocols before it can be migrated into server mode.
411-8111-803
Standard
01.06
May 2006
Figure 1-3
SDM/FT architecture
MS
ENET
Domain0
DS512
CPU
RootVg
DS512
DS512
DataVg
RootVg
CPU
SDM
DS512
DataVg
Switch
CM
Domain1
Figure 1-4
SDM in server mode
EM Browser
EM Browser
OSS (ASCII Interface)
Mass Export Client
Server Box
CEM Server Software
SDM
MSC/HLR
SDM
SDM
MSC/HLR
HLR200
GSM18/UMTS04
Figure 1-5
SDM in stand-alone mode
EM Browser
OSS (ASCII Interface)
Mass Export Client
SDM
MSC/HLR
CBM
Beginning in GSM18, the Core and Billing Manager (CBM) is a new
platform for the SDM functionality running on Sun Solaris. The CBM is only
used with MSC switches.
Note: SDM/FT does not have slices. One SDM/FT per DMS-GSM
switch. CBM supports slices and has one CBM per multiple DMS-GSM
switches.
The CBM platform uses Sun Commercial Off-The Shelf (COTS) hardware
and the Sun operation system. The High Availability scheme in CBM is made
of two running units. That reduces cost, is easier to upgrade and offers
reduced disk integration time. Figure 1-6 shows a high level view of the CBM
Architecture.
The CBM is built from a Core and Billing Manager 850 (CBM850) platform.
This platform consists of a pair of Sun Netra 240’s each equipped with the
following:
• Dual UltraSparc IIIi 1.2 GHz Processors
411-8111-803
•
2 Ultra160 SCSI 73GB Hard Drives
•
2GB Memory
•
DVD-RW Drive
Standard
01.06
May 2006
Figure 1-6
CBM architecture
Switch
CM
XAC
MS
HIOP
CBM
100 MB
Ethernet
GB
Netra 240
Netra 240
Ethernet
Unit 0
Unit 1
CEM application root directory
In SDM/FT, the CEM application root directory is in /sdm/mscomc/.
In CBM, CEM executable base root directory is in: /opt/nortel/cbm/
<release no>/cem/. For each slice, CEM application root directory is in /
opt/nortel/cbm/slices/<slicename>/cem. This CEM application
directory is a soft link to executable base directory:
/opt/nortel/cbm/slices/<slicename>/cem/ ->/opt/nortel/cbm/
<release no>/cem/
SDM tools directory
In SDM/FT, sdm tools such as imagename, queryflt, etc. are in /sdmtools/
bin directory.
In CBM, sdm tools reside in /opt./nortel/cbm/<release no>/bin. There
is a soft link to sdm tools directory in slice directory:
/opt/nortel/cbm/slices/<slicename>/bin -> /opt/nortel/cbm/
<release no>/bin.
GSM18/UMTS04
Figure 1-7
GSM - CBM - CEM server platform
WebStart from PC
WAN/LAN
WAN/LAN
USP
CEM Server
Alarm Database
SLR
SunMC/DS
MDM
or
MDM
Sun Server
Sun Solaris 8
SESM
Core Billing Manager (CBM)
HLR200
(GCBM Base Software)
Sun Solaris 8
Down Stream
Billing Center
TCP/IP connections
411-8111-803
Standard
01.06
May 2006
DMS-GSM
SDM software
The SDM has continuously available computing resources and connection to
the VCN switching core network. The fault tolerant architecture of the SDM
assures a reduced risk of hardware failure and, consequently, a lower risk of
OAM&P data and service loss.
There are three layers of software installed on the SDM (see Figure 1-8):
• AIX operating system — to control the Motorola PowerPC hardware
•
SDM base software — Nortel supplied for the mediation device and
communication to the MSC/HLR
•
GEM OAM&P applications — OMC-S, CIS, GSBA, HLR-PS, Call
Trace, and HLR-HST
Figure 1-8
OMC-S software
SDM/FT
AIX Operating System
SDM Base Software
FM/PM Server Software
DMS MSC
or
Configuration Management
HLR
Fault Management
Element
Manager Performance Management
PC/SUN
CBM software
Nortel’s software components included in the CBM include:
• Succession Server Platform Foundation Software (SSPFS) - provides the
Solaris Operating System and High-Availability capabilities.
•
Core and Billing Manager (CBM) - provides the common SDM platform
services enabling connectivity and management of the switch.
GSM18/UMTS04
•
GSM Core and Billing Manager (GCBM) - provides overall GEM
application capabilities to meet the market requirements.
SDM OMC-S applications
The OMC-S software aids in the OAM&P of the network elements on the GSM/
UMTS Voice Core network. The SDM performs the following functions:
• access, process, and deliver operational measurements (OMs)
•
table change notification (TCN)
•
remote procedure calls (RPC)
•
access, process, and deliver switch and network logs
•
table access (TA)
•
access, process, and deliver billing call detail records (CDRs)
•
access, process, and deliver legal call intercept CDRs
•
CDRs call trace CDRs
Table 1-1
Popular SDM tools renamed under CBM
SDM tools
CBM tools
sdmgather
cbmgather
sdmmtc
cbmmtc
querysdm
querycbm
Telnet/FTP pass through on SDM
Telnet and FTP connections to and from the XA-Core utilize the SuperNode
Data Manager (SDM) as a pass-through server. This enables Telnet and FTP
requests to and from the XA-Core using the DS512 interface between the
XA-Core and SDM.
A client wanting to connect to the XA-Core using Telnet or FTP issues the
request to the SDM attached to the XA-Core, and specify a pre-determined
connection port. This enables the pass-through server on the SDM to properly
direct the request to the XA-Core. An example of the new connection request
would be:
> telnet <SDM IP> <telnet pass-through port>
> ftp <SDM IP> <ftp pass-through port>
411-8111-803
Standard
01.06
May 2006
The following list specifies the seven ways to use the SDM as a pass-through
server:
1. telnet Request from Remote Node to XA-Core
> telnet <sdm_ip_addr> 22397
2. FTP Request from Remote Node to XA-Core
> ftp <sdm_ip_addr> 22398
3. Telnet Request from Remote Node to SDM/FT
> telnet <sdm_ip_addr> 22399
4. FTP Request from Remote Node to SDM/FT
5. FTP Request from XA-Core without EIUs to Remote Node. On XA-Core,
from a MAP window, issue the FTP request:
> ftp
> forcesdm
> ftpopen `<remote_node_ip>'
6. Non secure FTP to XA-Core from any FTP Client
7. Non secure FTP to SDM/FT from any FTP Client
By specifying a port on the Telnet / FTP request, the request will be routed to
the pass-through server and then routed to the XA-Core without invoking the
local security on the SDM.
To provide file transfer capabilities from the XA-Core to a remote node, the
FTP Client on the XA-Core needs to determine if the request should be
directed to the remote node via the Ethernet Interface Unit (EIU), or the
SDM. In either case, the open request issued by the operator will not change.
In an environment with an EIU, the FTP Client will send FTP requests to the
EIU, as it is done today. In an environment without the EIU, the pass-through
server on the SDM will establish two logical connections: a connection
between the XA-Core and the SDM, and a connection between the SDM and
the desired remote node. The pass-through server will manage the two
connections and present them to the FTP client as a single logical connection.
Figure 1-9 shows the functional diagram for Telnet/FTP service.
GSM18/UMTS04
Figure 1-9
Telnet/FTP via SDM Functional Diagram
GSM MSC
XA-Core
EIU
FTPCI
LANCOMM
Message Shelf (MS)
DS512
Telnet/FTP
SuperNode Data Manager (SDM)
Telnet / FTP
Pass-Through
FTP From
XA-Core
Telnet/FTP
To XA-Core
Legend
Existing Path
Alternate Path
411-8111-803
Standard
01.06
May 2006
Remote
Node
Restrictions for the use of the SDM and GCBM platforms
1. The SDM is not a public UNIX platform. Users are not permitted to add
applications or change the directories outside of the installation
procedures.
2. Nortel puts significant testing into the SDM hardware, operating system,
and SDM applications to ensure that performance specifications are met.
Other uses of the SDM may impact system performance. Nortel’s
recourse during troubleshooting may lead to a full system reinstall at
operator's expense.
3. Special user accounts, applications, and other non-Nortel modifications
are not migrated during system upgrades.
4. GEM SDMs prior to GEM17.1 must be upgraded to GEM17.1 server
mode SDMs before they can be upgraded to GEM18.
5. GEM SDMs prior to GEM18 must be upgraded to GEM18 server mode
SDMs before the SDM to GCBM transition occurs.
6. The following file sets are not available on the GCBM:
— Enhanced Terminal Access
— Enhanced Terminal Access Client
— Secure File Transfer - this functionality is provided by Open SSH
— Secure File Transfer Client
— DCE and DCE base applications are not be available
GSM18/UMTS04
CEM support for R4 BICN/BICC
1
Support for the Media Gateway and Aggregation Node through the MDM
The CEM will now support the Media Gateway and Aggregation Node by
using the MDM software, release 15.1. This is a reuse of the existing
management capability.
A managed Passport of EM type can be named as a MGW type and be
displayed as a Media Gateway Network Element on the CEM GUI.
Aggregation Node also has its own node type in the MDMConfig tool.
Figure 1-10
CEM Interface with MDM
CEM Software Architecture
To CEM GUI Client
CEM Server
EM Adapter
Object
Manager
PM Archive
CM
Normalizer
Device Manager
Log
Normalizer
Voice
MDM Normalizer
MDM OSS Public Interface
MDM
SDM/FT
MSC
411-8111-803
Media Gateway
SDM/FT
Passport 15000
HLR100
Standard
01.06
May 2006
Packet
Passport OMs
Operational Measurement (OM) thresholding groups are extended to support
Management Data Provider (MDP) OMs from Media Gateway and
Aggregation Node. The following functionalities are available for these new
OM thresholds:
• Threshold values can be set for these OMs in each of the Critical, Major
and Minor categories.
•
The direction (slope) can be set for these thresholds.
Wizards for R4 BICN/BICC provisioning
The CEM configuration wizards support provisioning for the R4 Bearer
Independent Core Network (BICN) and the Bearer Independent Call Control
(BICC). Provisioning is done in “serial.” The Media Gateway (MGW) is first
provisioned (via MDM Nodal Provisioning templates). Then the wizards add
Media Gateways (VSP cards) to the GWINV table on the DMS and add trunk
members on the DMS (using carriers on the MGW). MGW provisioning will
be “visible” to CEM through the interface, but the wizards will only query
MGW datafill through the MDM interfaces.
The following wizards are added to provision R4 BICN/BICC on the MSC:
• Add BICN Trunk Group - Add datafill for R4 BICN to tables TRKGRP,
TRKSGRP and TRKMEM.
•
Add BICN Trunk Members - Add datafill for R4 BICN to table
TRKMEM.
•
Add MGW - Add datafill for MGW to table GWINV.
•
Add BICC Trunk Group - Add datafill for BICC to tables CLLI,
TRKGRP, TRKSGRP, ISUPDEST, TRKOPTS and GBCIC.
•
Delete MGW - Remove datafill for MGW from the table GWINV.
•
Add CFIWF Trunk Group.
•
Delete CFIWF Trunk Group.
•
BICN Audit - Checks for all the inconsistencies of the MGW datafill in
TRKMEM and GWINV tables.
•
Recovery - Resubmits the datafill. Whenever a wizard submits datafill
changes to DMS, a recovery file will be created with all the tuples. The
file will also have information whether the tuple has been successfully
submitted or not. The Recovery wizard lists out the recovery files created.
When a file is selected this recovery wizard will submit all the
unsuccessful tuples in that file.
•
Fallback - During an upgrade this wizard can be used to fallback any
datafill. Whenever a wizard submits datafill changes to DMS, a fallback
file will be created with all the tuples. The Fallback wizard lists all the
GSM18/UMTS04
fallback files created. When a file is selected this fallback wizard till
submit all the fallback tuples in that file.
For more information on wizards for R4 BICN provisioning, refer to the
Configuration Management chapter of GSM / UMTS Voice Core Network
OAM User Guide , NTP 411-8111-503.
Wizard support for migration to BICN MSC
Wizards are needed to support the process of upgrading a non-BICN MSC to
be a BICN MSC. This includes a requirement to support migration of legacy
trunks to MGW-based trunks. Also, wizard support is included for
configuring Connection Fabric Interworking Function (CFIWF) trunks, used
to support hybrid calls, in which one call half-uses an XPM/SPM-based trunk
while the other call half-uses a MGW-based trunk.
Reduction/relocation of visible attributes
Much of the raw data shown in the node Info window is not used by the
customer. In addition, there are specific requirements to remove MDM
attributes from MDM-managed nodes that are inconsistent with the CEM.
In an effort to simplify the use of this window and its contents, the window’s
contents will be analyzed for their value and necessity. Then, the Info window
attributes will be cleaned up (either removed from view or reorganized). This
will ease the use and increase the usefulness of the Info window to the
customer.
Note: This functionality is not R4 or Passport specific.
Support of low-water mark as an accumulation type
There are 3 accumulation types that are used for performance studies; these
types use a time interval greater than the collected time interval. The types are
peg (default), high-water mark and average registers. There are some Passport
OM groups that require a low-water mark register type. The low-water mark
type is added as another accumulation type.
411-8111-803
Standard
01.06
May 2006
Table 1-2 shows the list of registers which are supported as low-water mark
registers.
Table 1-2
List of Low-Water Mark Registers
OM Group
Low-Water Mark Registers
ATM Interface
txMinCellRate,
txMinCellRateByServiceCat0,
rxMinCellRate,
rxMinCellRateByServiceCat0,
rxMinCellRateByServiceCat4
txMinCellRateClp,
txMinCellRateClpByServiceCat0,
rxMinCellRateClp,
rxMinCellRateClpByServiceCat0,
rxMinCellRateClpByServiceCat4
Logical Processor
cpuUtilAvgMin,
localMsgBlockUsageMin,
memoryUsageAvgMin0,
memoryUsageAvgMin1,
memoryUsageAvgMin2,
sharedMsgBlockUsageAvgMin
GSM18/UMTS04
USP
USP also serves as a signalling gateway (SGW) for the R4 BICN MSC. This
USP replaces legacy LPP in the MSC. One SGW is dedicated to one MSC.
For more information on USP, refer to “USP” on page 1-30.
Resource discovery
USP acting as signalling gateway (SGW) for MSC will contain the following
resources if provisioned:
• Resource discovery of platform resources:
— shelf
— slot (card)
•
Resource discovery of MTP resources:
— routeset
— linkset group
— combined linkset
— linkset
— link (SLC)
The component state for the MTP resources is ’unknown’ since no MTP
alarms are issued against the these components.
Two configurations are possible for the SGW. One is the standalone network
element model (Figure 1-11), and the other is a sub-component of the MSC
network element model (Figure 1-12). The configuration of the USP being
under an MSC requires that the USP services only one MSC. If the USP ever
services multiple MSCs, then the standalone network element is the only
configuration option available.
411-8111-803
Standard
01.06
May 2006
Figure 1-11
SGW NE model
SGW
CCS
OM_Container
SHELF
ROUTESET
LINKSET_GRP
COMBINED
_LINKSET
LINKSET
routeset
linkset
group
combined
linkset
linkset
MISCELLANEOUS*
slot
slc
misc
objects*
object
container
association
* only exist when an alarm cannot be identified against an existing component
GSM18/UMTS04
Figure 1-12
MSC model containing USP components
object
MSC
container
association
CCS
USP_
ROUTESET
USP_
LKSET_GRP
routeset
linkset
group
PM
USP
USP_
COMBINED
_LKSET
USP_
LKSET
combined
linkset
linkset
SHELF
MISCELLANEOUS
slc
slot
objects
misc
Fault management
CEM will gather existing alarms on start up and be notified of any new alarms
and logs. These alarm/logs will either be raised against the NE or a card
component. There are currently 6 different types of alarms and logs that can be
sent from the USP. They are listed below:
1. Minor Alarm Notification - generated when a minor alarm is raised.
2. Major Alarm Notification - generated when a major alarm is raised.
3. Critical Alarm Notification - generated when a critical alarm is raised.
411-8111-803
Standard
01.06
May 2006
4. Alarm Clear Notification - generated when any alarm severity is to be
cleared.
5. Log Swerr Notification - generated when the USP encounters a software
error. This will be a manually clearable alarm with ‘minor’ severity.
6. Log Info Notification - generated when the USP wants to report
informational only type log. These alarms will be manually clearable
alarms having ‘warning’ severity.
Acknowledged alarms from the USP will not be propagated to CEM.
Acknowledged alarms from CEM will not be propagated to USP.
Note: User initiated clearing of USP fault alarms is not allowed and is
disabled in the CEM GUI.
GSM18/UMTS04
CEM support for HLR 200
1
CEM provides the OAM solution in the GSM switch network. It provides
configuration, fault, and performance management capabilities for MSC and
HLR nodes in the network. OMC-S server, a Sun Solaris 8 platform, is where
most of the OMC-S processes reside.
HLR 200 is the next evolution phase of the HLR. Its provides reliability,
capacity, scalability, cost reduction, and evolution toward 3GPP Home
Subscriber System (HSS). HLR 200 consists of the HLR, USP, PP8600,
Service Location Register (SLR), SAM21, STORM, and the Data Server.
Figure 1-13 depicts the relationship among the network elements. PP8600 is
not depicted in Figure 1-13 because it acts as a router among the network
elements.
Figure 1-13
Network overview of HLR200 interacting with R4 BICN
SMI
MSC
HLR
M3UA/UDP
USP
UNPM
MSC
HLR
Data Server
HLR-PS
USP/SGW
M3UA/UDP
MSP
SLR
USP
SS7 Network
USP/SGW
MSC
HLR
M3UA/UDP
USP/SGW
USP
HLR 200
R4 BICN
The SAM21 shelf will contain 3PC cards, which is co-located with the XACore HLR. STORM (STORe Manager) is a file server to the 3PC cards. The
STORM, SAM21 shelf, SDM and XA-Core HLR communicate to each other
through a Passport 8600 router. The communication between the HLR and
SDM remains through the DS512 link (refer to Figure 1-14). There will also
be an OAM Server called the CMT Server. The CMT Server is a Sun Netra
240 machine with SSPFS application with SESM and SAM21 EM installed.
411-8111-803
Standard
01.06
May 2006
There are two USP cards, two STORM and two SAM21 Shelves per HLR for
redundancy. The HLR, USP, SDM, STORM, SAM21, Passport 8600 and the
CMT server together are called the HLR 200 mini-complex. The whole minicomplex has a mated pair for additional protection. Further detail can be
found in the HLR 200 Solution Overview (411-2831-014).
The CEM can monitor the HLR and the new 3PC memory application, the
SAM21 Shelf (i.e. the SC and 3PC cards), the STORM, the USP, the Passport
8600, Data Server and SLR.
Figure 1-14
HLR 200 Mini-Complex Network Connection Overview
CEM GUI host
CEM Server (OAM server)
Ethernet
Ethernet
LAN Network
Ethernet
CMT Server (OAM server)
Ethernet
Ethernet
Passport 8600
Ethernet
Ethernet
3
3
3
p
p
p
C
C
C
Ethernet
SDM
S
C
S
C
3
3
3
p
p
p
C
C
C
3
3
3
p
p
p
C
C
C
SAM21 Shelf
Ethernet
Ethernet
DS512
Ethernet
STORM
STORM
Ethernet
3
3
3
p
p
p
C
C
C
S
C
S
C
SAM21 Shelf
HLR
USP
Figure 1-15 shows the CEM architecture for the HLR 200. As Figure 1-15
suggests, the devices introduced in the HLR 200 will be monitored using the
GSM18/UMTS04
device managers (DM) which will feed their information into the existing
CEM. The DMs for SAM21, SESM and USP as well as the CEM processes
for the HLR feed into the same CEM server stack. Thus, the user will have a
integrated view of the HLR, SAM21, SESM and USP. The figures below
shows how CEM GUI will show these elements.
Figure 1-15
Mated HLRs Managed by CEM
Client Machine
DM - Device Manager
CEM GUI
DM for
SESM
DM for
SAM21
CEM Processes
for HLR 200
DM for
USP
SAM21 EM
Server
CEM Server Stack
for SLR
DM for
Passport
USP
SESM
Server
USP
CMT Server
SDM
CEM Server
CEM Server Stack
For Passport
CEM Server Stack
for HLR Mini-Complex
SNMP
Agent
Passport
DM for
SLR
SLR
SLR
CEM Server Stack
for Sun MC
DM for
Data Server
Data Server
Agent
Data Server
SAM21
Agent
HLR
Storm
Agent
SAM21 SC STORM
HLR mini-complex’s memory application
Figure 1-16 shows the CEM view of the Memory Application and its
associated objects. Three containers exist under the APPL container for HLR
200: the CS2K_COMPONENT container, the SAM21_Shelf container and
the MEM_APP container. The CS2K_COMPONENT container will contain
the STORM objects. These objects will monitor the STORM alarms. These
objects will be discovered through the SESM on the CMT server. Thus SESM
server must be properly configured to get STORM resource information and
traps.
411-8111-803
Standard
01.06
May 2006
Figure 1-16
Object Model of HLR200 Memory Application and Associated Objects
object
HLR
container
Association
APPL
CS2K_COMPONENT
CompCore
SAM21_Shelf
MEM_APP
STORM 1
STORM 2
Shelf-1
Shelf-2
H3PC ME
App 1
Card 1
H3PC ME
App 2
Card 2
The SAM21_Shelf contains the shelves which in turn contain the cards. There
are three types of cards: SCU (Shelf controller unit), H3PC ME (memory
extension) and cards with unassigned services. These objects will be
discovered through the SAM21 EM server on CMT server. Thus, the
SAM21EM server must be properly configured to get SAM21 shelf resource
information and their alarms.
The MEM_APP container will contain H3PC Memory extension application
objects. These objects will be discovered using the processes on the SDM
which gets these information from the HLR. These objects represents the
application running on the 3PC cards and will have OMs associated with
them.
Monitoring of HLR mated pair relationship
If configured, the mated pair monitor process will allow the operator to:
• view mate attributes from the HLR slice in the CEM GUI.
•
view alarms raised on combined attributes of the mated-pair.
GSM18/UMTS04
Configuration of the mated pair monitor
The mated pair monitor is configured using the configCEMS tool which can
be accessed on any CEM in the /opt/nortel/data/coreEMS/nodes/server/bin
directory. The configCEMS tool is used to provision a new CEM ‘slice,’ but
in this case it will be used to configure a process which will monitor two
slices.
To configure the mated pair monitor, the user needs to start the configCEMS
tool and choose the mated pair monitor option. After doing this, the user can
configure up to sixteen mated pairs. The only information the user must enter
to configure a mated pair is the two HLR slice names which make up the
mated-pair. ConfigCEMS will prevent the user from entering information
which does not correspond to a ‘slice’ name and will prevent the user from
using any ‘slice’ name twice. ConfigCEMs will allow user to enter HLR
‘slice’ names only (DMS or HLR200).
The monitor process will be started as soon as a mated pair is provisioned.
After the process is started, it will become visible in the CEM GUI when the
user chooses ‘Server Application Management’ under the ‘Administration’
menu. The Mated Pair Monitor process will be visible under the <server>/
OMC-S/server level on the resulting window.
The operator can use configCEMS to add and remove mated-pairs from the
monitor. The monitor process will disappear from the CEM GUI when the
last mated-pair is removed from configCEMS.
How to view mated pair attributes
Beginning in GEM18, a number of new attributes which are retrieved for all
HLRs are added and indicate their mated pair configuration data. This matedpair configuration data is primarily retrieved from the GHLRPARM table on
the HLR.
These attributes (and where they are retrieved from) are:
• SbyOn (from the STANDBY_ON field, tuple STANDBY in table
GHLRPARM
411-8111-803
•
SbySynchOn (from the STANDBY_SYNC_ON field, tuple STANDBY
in GHLRPARM)
•
SbyHdoOn (from STANDBY_HANDOVER_ON field, tuple STANDBY
in GHLRPARM)
•
SbyMode (from STANDBY_MODE field, tuple STANDBY in
GHLRPARM)
•
AcoOn (from ACO_ON field, tuple ACUTOVER in GHLRPARM)
•
AcoMode (from ACO_MODE field, tuple ACUTOVER in GHLRPARM)
•
HlrNumber (from GHLR_HLR_NUMBER tuple in OFCSTD)
Standard
01.06
May 2006
•
MateHlrNumver (from table GHLRPARM, tuple STANDBY, parm
STANDBY_MATE_HLR_NUM)
•
AcoState (autocutover audit state which is retrieved from logs GHLR821
or GHLR823)
These attributes will be available whether the mated pair monitor is
configured or not.
Attributes that appear when the monitor is configured
If an HLR slice is part of a mated pair which has been configured for monitoring
(refer to “Configuration of the mated pair monitor” on page 1-28), new
attributes will be seen in the HlrStby container. These attributes provide
information about the mate HLR:
• Mate_AcoMode - AcoMode attribute duplicated from mate slice
•
Mate_AcoOn - AcoOn attribute duplicated from mate slice
•
Mate_HlrNumber - HlrNumber attribute duplicated from mate slice
•
Mate_SbyHdoOn - SbyHdoOn attribute duplicated from mate slice
•
Mate_SbyMode - SbyMode attribute duplicated from mate slice
•
Mate_SbySynchOn - SbySynchOn attribute duplicated from mate slice
•
Mate_SbyOn - SbyOn attribute duplicated from mate slice
•
Mate_AcoState - AcoState attribute duplicated from mate slice
•
Mate_Slice - mate slice alias
When the pair is removed from the mated pair monitor, the above attributes
are no longer available.
Alarms raised by the mated pair monitor
Alarms will be raised against the HLRStby container on the two HLR nodes
of the mated pair when attributes related to the mated pair indicate it is in an
unsupported or misconfigured state. Alarms MON001 - MON007 will only
be raised against the HLRs when the mated pair monitor is configured to
monitor them. If the mated-pair is removed from the monitor, the alarms will
be cleared.
Alarms MON001 - MON007 will be raised after the problem caused the
alarm exists for more than 1 minute. Alarm MON008 will be raised after the
problem caused the alarm exists for more than 90 seconds.
GSM18/UMTS04
USP
The Universal Signalling Point (USP) application is based on Nortel
Network's Signalling Server platform. USP is the SS7 gateway for the HLR.
USP replaced LIU7/LPP peripherals that existed on the HLR. It provides high
capacity and significant footprint reduction.
Note: CEM supports USP10.0 for SLR, UNPM, SGW, and USP under
HLR 200.
The USP performs the following functions:
• encapsulates and routes SS7 ISUP and SCCP messages over an IP
network to an Application Server (AS) using the SIGTRAN protocols
M3UA over UDP
•
routes received IP encapsulated ISUP and SCCP messages from an
Application Server (AS) (via M3UA/UDP) to an SS7 Network
The USP provides a message switching function between nodes in a SS7
network and Application Servers in an IP network. SS7 functions performed
by an USP are related to message discrimination, routing and distribution, and
signaling link and network management, supported by link error detection
and correction.
Note: For upgrades to GEM18 from releases prior to GEM17,
thresholding for USP OMs does not become available until the USP itself
is upgraded.
411-8111-803
Standard
01.06
May 2006
Figure 1-17
CEM View of the USP
object
HLR
container
association
CCS
PM
USP
USP_
ROUTESET
USP_
LKSET_GRP
USP_
COMBINED
_LKSET
USP_
LKSET
routeset
linkset
group
combined
linkset
linkset
SHELF
MISCELLANEOUS
link
slot
misc.
objects
Passport 8600
The Passport 8600 is a network element; not a subcomponent of an HLR.
Each HLR mini complex will have a Passport 8600. The user can associate
the Passport with its HLR mini complex. Figure 1-18 shows the resources of
the Passport 8600. There could be multiple CARD, PS, FAN, IF objects and
are polled for initial resource discovery and alarm list. The OSPF and the
objects under it are dynamic objects and are created only if any traps occur on
these objects. There are no performance management for Passport 8600.
GSM18/UMTS04
Figure 1-18
CEM View of Passport 8600
object
PP8600
CARD
PS
FAN
container
OSPF
IF
NBR
IFADDR
VIRTNBR
VIRTIF
SLR
Service Location Register (SLR) is based on the Signalling Server platform
similar to the USP. SLR is a system that routes network originated MAP
requests to the HLR node serving the subscriber associated with the
transaction. To the network, multiple HLRs are deemed to be one since MAP
requests to the HLR are sent to one SLR. SLR is automatically provisioned by
the Data Server. SLR redundancy exists in the network for reliability.
The SLR will be identified as a network element. The SLR’s object model is
shown in Figure 1-19. The CEM GUI will provide pop-up menu items for
available maintenance actions on SLR resources in the GUI containment tree.
The performance management for SLR will provide OM graphs and
thresholds.
411-8111-803
Standard
01.06
May 2006
Figure 1-19
CEM View of the SLR
SLR
CCS
SHELF
ROUTESET
LINKSET_GRP
COMBINED
_LINKSET
LINKSET
routeset
linkset
group
combined
linkset
linkset
MISCELLANEOUS
slot
link
misc.
objects
object
container
association
SAM21
The Service Application Module 21 (SAM21) is a shelf controller that
provides booting and loading of cards such as 3PC cards on the SAM21
chassis. 3PC is the card that RAM disk application will be running on.
The alarms of SAM21 can be monitored by CEM. This is achieved by having
a CEM normalizer, or device manager, on the CS2K Management Tool
(CMT) server (see Figure 1-20). This device manager will take resource
information, alarms from SAM21 EM feeding into the CEM processes. The
SAM21 device manager supports CMT releases SN06 and SN07.
GSM18/UMTS04
The SAM21 device manager uses Succession Java libraries for resource
discovery and fault management: Succession Server Platform Foundation
Software (SSPFS), Media Gateway 9000 (MG9K) Frame Work and SAM21
Element Manager libraries.
Note: The SAM21 EM needs to be installed on CMT server and then it
needs to be configured to get resource information and traps from the
SAM21 shelves. This can be done using the SAM21EM GUI.
Figure 1-20
Message Flow for SAM21 Fault Management
CEM Server
Proprietary
CEM
GUI
CMT Server
CEM Processes
Proprietary
Device Manager
CORBA
SAM21 Shelf
SAM21 SNMP Agent
SNMP
SAM21 EM
STORM
STORM is the controller to the storage disk. The STORM box has a SNMP
agent process running on the STORM cards. Thus, similar to the SAM21 fault
management, the STORM fault management will be via a device manager. In
regards to STORM, the source of the information is another process called the
SESM. The SESM device manager supports CMT releases SN06 and SN07.
The SESM device manager uses Succession Java libraries for resource
discovery and fault management: SSPFS, Manatee Iteration 2 (MI2)
FrameWork and SESM libraries.
Note: SESM has to be installed and configured on the CMT server.
411-8111-803
Standard
01.06
May 2006
Figure 1-21
Message Flow for STORM Fault Management
CEM Server
Proprietary
CEM
GUI
CMT Server
CEM Processes
Proprietary
Device Manager
CORBA
STORM Box
SNMP
STORM SNMP
Agent
SESM
(PTM)
Data Server
Data Server (DS) provides a single point provisioning, coordinates HLR
mating, geographical redundancy, stores subscriber data, and controls the
distribution of this data. The DS consists of a provisioning manager and a
database engine. The Data Server uses the Oracle database for storage of
subscriber information. MSP messaging is used to provision the HLR. DS
also allows an increased number of Administration Data Center (AdC)
sessions and supports encrypted authentication data exchange with HLR-PS
systems.
The standard network configuration (see Figure 1-22) includes two Data
Server nodes, one active and one in place for redundancy. The two nodes may
be separated geographically. On both Data Server nodes, the subscriber
mappings are synchronized using the Data Replication function of the
embedded Oracle database. The Data Server holds the subscriber mappings
within this embedded database and populates the SLR nodes with current
routing information, providing common point of signalling for the GSM/
UMTS wireless network.
In the W-NMS environment, the Data Server is only supported by the primary
Main Server.
The Data Server does not communicate directly with the CEM. The CEM
gets information about the DS through the Sun MC. The Sun MC collects,
stores, logs and displays the data provided to it by any network elements (on
Sun platforms). The Sun MC in turn gets information from an agent running
on the Data Server platform.
GSM18/UMTS04
The operator should display Data Server information using the CEM GUI. If
more detailed information is required than is directly available on the CEM
GUI, the operator should access the Sun MC GUI. The Sun MC GUI provides
more information about the Data Servers connected to it. For more
information, refer to GSM / UMTS HLR200 Data Server Operations and User
Guide, NTP 411-2831-330.
This is the recommended mode of operation, but in the case that the Sun MC
application is down, the user may want to get direct access to the Data
Servers. That can be done via a SSH connection directly to the DS from the
CEM GUI. The user is prompted for a valid <user_name> and <password>.
Figure 1-22
CEM - DS Simplified View
CEM console
CEM console
OAM Links
CEM SERVER
Sun MC
Data
Server
Data
HLR-PS
Server
DataData
Server
Server
HLR-PS
Sun MC
The Sun MC (Sun Management Center) is defined as a network element. The
Sun MC is a monitoring device which gathers data from Data Servers. The
Sun MC is collocated, running on the same platform, with the CEM Server.
The Sun MC is designed to provide information about the operating system
and the hardware for any compatible network element. This is possible
because there is a process on the network element called an ‘agent’ which
sends status and performance information to the Sun MC about the hardware
411-8111-803
Standard
01.06
May 2006
and O/S. The agent takes information from a number of standard modules
which are included as part of the Sun MC software. These standard modules
will monitor the hardware and operating system of the Sun node.
A network operator requires additional information about the DS than what is
provided by the Sun MC. Due to this, enhanced monitoring is provided to the
Sun MC through the use of custom modules. New modules have been
developed and installed on the DS which give the operator DS alarms and
Management Information (MI) statistics. Information from these modules
will be made available to the CEM.
Since the Sun MC is a monitoring device, there is no extensive monitoring of
the Sun MC node on the CEM. There are no logs or operational
measurements provided about the Sun MC. The only information which is
displayed about the Sun MC is state information, and alarms which indicate
that connectivity to the Sun MC is down or that it is configured incorrectly.
The state of the Sun MC is displayed as ‘inservice’ if the CEM is able to
connect and the configuration is correct. Otherwise, the state is shown as
‘unknown’.
The Data Servers have many associated alarms and more detailed state
information. Of course, the state of the Data Servers will be ‘unknown’ if the
Sun MC state is ‘unknown’ since the CEM server will be unable to access
information about them.
Figure 1-23
Sun MC Collects Information from Data Server Agents
Sun MC Console
CEM
Client API
Client API
RMI
RMI
Sun Management Center Server
Data Server 1
Agent
O/S info
H/W info
Other OAM info
Data Server 2
Agent
O/S info
H/W info
Other OAM info
Modules
GSM18/UMTS04
Sun Management Center software is an open, extensible system monitoring
and management solution that uses Java (TM) software protocol and Simple
Network Management Protocol (SNMP) to provide an integrated and
comprehensive enterprise-wide management of Sun products and their
subsystems, components, and peripheral devices. Sun Management Center
software comprises three component layers: console, server, and agent. It is
based on the manager/agent architecture.
The console is the user interface which interacts with the user to initiate
management tasks. The server (manager) executes management applications
and sends requests to agents in order to perform management tasks on the
user’s behalf. The agents, executing on the managed nodes: access the
management information, monitor local resources, and respond to manager
requests.
The Sun MC agents for DS reside on the DS host machine. Traps and events
are forwarded from each agent to its configured Sun MC server. Each agent is
made up of a set of different functional modules which monitor various
software and hardware components of the DS host.
The Sun MC console is the OAM interface for displaying detailed monitoring
of the Data Server(s). The Sun MC console gives the operator access to all
information provided to the Sun MC server by the Data Server (DS) agents.
The console, which may be installed on a remote PC or SUN workstation,
communicates with the Sun MC server using a java-based Remote Method
Invocation (RMI) system. The same RMI system is used by the CEM to get
information about the Data Server from the Sun MC.
A package called the Client API (Application Programming Interface) is
installed on the CEM and retrieves information about the DS from the Sun
MC. The CEM can use the Client API to request data from the Sun MC
server, but the Sun MC server does not send any information unless
requested. For example, if a DS goes out of service and an alarm appears on
the Sun MC, the CEM is not informed of this alarm until it has sent in a
request for data about alarms. The CEM must use the Client API to
continually request, or poll, for the latest data from the Sun MC server. For
more information refer to “Polling” on page 1-40.
Note: The time span between requests must be small enough to ensure
that the CEM updates within a reasonable time, but long enough not to
use excess resources.
The CEM is a network monitoring node and only shows the relevant subset of
the Data Server information which can be seen on the Sun MC console. The
CEM displays the important information for the network view. For example,
alarms indicating state changes or major problems are shown on the CEM
411-8111-803
Standard
01.06
May 2006
while those showing very minor Data Server disruptions are only available on
the Sun MC console.
Note: The W-NMS environment is using a Sun MC server and agents in
version 3.5 to monitor the main server and performance server hosts
whereas the DS uses the Sun MC server and agents in version 3.0. There
are other key configuration differences between the Sun MC software
used by the HLR 200 and W-NMS including the port differences,
specifically the trap port, and the difference in security key used to
communicate between Sun MC agent and Sun MC server.
CEM support of Data Server (non-UMTS environments only)
To display the DS on the CEM, the following information is required at
configuration time:
• <Sun MC Server host address> defaults to ‘localhost.’
•
<Sun MC Server initial connection port> defaults to 2099.
•
<login_id> and <password> to connect to the Sun MC.
•
<Data Server agent IP addresses>
•
<Data Server agent ports> defaults to 6161.
•
<polling interval> this is how often the client API asks the Sun MC for
new information. The recommended polling interval is 60 minutes.
•
<audit interval> this is how often the CEM will re synchronize it’s alarms
with those displayed on the CEM. The recommended audit interval
should be 60 minutes or more.
This information must be configured on the CEM, using the configCEMS
tool, and is stored by the CEM software. If any of the above configuration
information changes after the initial configuration, this information must be
reconfigured using the configCEMS tool. If the configuration changes, or if
the Sun MC password is changed, it will not be detected automatically.
Note: Information like default port numbers, login_id and passwords will
be provided by Nortel.
Data Server node configuration
In order to monitor Data Servers in the network, the CEM user must first
configure a Data Server node using the configCEMS tool. The information
required to configure the slice is included in section “CEM support of Data
Server (non-UMTS environments only)” on page 1-39.
Resource discovery
When the Data Server node on the CEM is returned to service, resource
discovery will begin. In order for the Data Servers to be discovered correctly
they must be configured correctly on the Sun MC. Especially important is that
GSM18/UMTS04
the two Data Servers be configured under the “HLR200 Data Servers”
domain as “Unit 1” and “Unit 2” or “Site 1” and “Site 2”. Please refer to NTP
411-8111-937 for more information on Sun MC configuration.
Once discovery has completed (it could take several minutes), the Sun MC
and Data Servers will be displayed on the CEM GUI. The DS nodes will be
displayed as peers to the Sun MC node.
Polling
Once resource discovery has been completed the CEM will repeatedly poll
the Sun MC after the configured polling interval. The recommended polling
interval is 60 minutes. Alarms will be raised/cleared and attributes updated
with each poll.
Audit
Since alarms are manually clearable from the Sun MC and CEM, the CEM
and Sun MC could get out of sync. For example, the Sun MC user could
choose to “delete all closed alarms” to prevent a buildup of closed alarms on
the Sun MC. If this happens during the polling interval, some cleared alarms
may not be propagated to the Sun MC. In order to prevent such a mismatch,
an audit occurs after a configured interval to re-synchronize alarms.
DS alarm interface
The CEM receives all of its alarm information from the Sun MC. All Data
Server alarms of minor, major or critical severity which exist on the Sun MC,
are propagated to the CEM, and cleared when applicable. This includes any
alarm from the following ten modules:
• Kernel Reader - This module monitors various system statistics.
411-8111-803
•
Config Reader - This module monitors various hardware configuration
information.
•
Agent Stats - This module monitors the health of the agent installed on the
Data Server.
•
Partition Size - Monitors the usage of space in the mounted partitions.
•
Process Monitoring - Monitors the health of Oracle processes running on
the Data Server.
•
Data Server Process States - monitors the state of the PRT, DLM, SLR
and BSP processes.
•
Oracle Directory - Monitors the size of the Oracle directories.
•
Oracle Stats - Monitors statistics associated with the Data Server
database.
•
Oracle Streams - Monitors replication between the two Data Servers.
•
DS Active MI Alarms - This module monitors Data Server MI alarms.
Standard
01.06
May 2006
Alarms will appear in the same format as existing CEM alarms. As with other
CEM alarms, they will affect the color of the Data Server node in the CEM
GUI display. However, Data Server alarms will not display the associated
Data Server log information in the alarm text.
Data Server performance data
OMs are not provided in this release. However, additional attributes have been
added to monitor DS process states. The following process states will be
updated with each poll of the Sun MC:
• Provisioning State
•
State of All processes
•
State of Mihub process
•
State of CCSM process
•
State of PRT process
•
State of DLM process
•
State of SLRDM process
•
State of SLR audit process
•
State of BSP process
Restrictions and limitations for Data Server
1. Manually clearable alarms shown on the CEM are only cleared in the
CEM alarm database. Data Server alarms will not be cleared when a user
clears an alarm on the CEM GUI. If the user has cleared the CEM alarms,
the CEM will restore the alarms during the next audit cycle.
2. When alarms are manually deleted on the Sun MC, there may arise a
mismatch with the alarms on the CEM. This will be cleared at audit time.
3. Alarm and process state information is subject to an update delay. The
size of this delay depends on the refresh rate of the Sun MC data and the
time required to access it from the CEM server (this delay may take
several minutes).
4. Data Server logs and MIs are not propagated to the CEM.
5. This is supported for Sun MC version 3.5.1. The Sun MC must be
configured correctly to monitor the two Data Servers (for example, the
‘HLR200 Data Servers’ domain must be configured) before starting the
Sun MC slice. For information on configuring the Sun MC, please refer to
NTP 411-8111-937.
Restrictions and limitations for HLR 200
1. No OMs (operational measurements) for SAM21 shelf and STORM will
be monitored by CEM.
GSM18/UMTS04
2. Provisioning of SAM21 shelves will be done through the SAM21 EM
GUI.
3. Provisioning of the STORM will be done via a command line interface.
4. Java Web Start and a web browser (e.g. IE 6.0 or Netscape 4.7) must be
installed on the client machines to launch the SAM21EM GUI from CEM
GUI.
5. Provisioning of the SAM21 will be done through the SAM21 EM GUI.
CEM support for NEs in W-NMS environment
1
CEM provides the OAM solution in the GSM/UMTS core network. It
provides configuration, fault, and performance management capabilities for
variety of nodes including MSC, HLR, TriNode, Passport, etc. in the network.
The Wireless Network Management System (W-NMS) is the umbrella
environment which allows management of voice core network as well as the
radio access network. The CEM can monitor the voice core network in a
stand-alone mode where W-NMS is not present and can also be used to
monitor the core network as a part of the W-NMS.
Note: Prior to GSM18, W-NMS was referred to as Preside for Wireless
Internet (W-NMS).
411-8111-803
Standard
01.06
May 2006
Figure 1-24
Simplified W-NMS architecture with CEM
Client Machine
MFT GUI
MFT Stack
CEM Processes
for HLR 200
SDM
CEM Server Stack
For Passport
CEM Server Stack
for SLR
CEM Server Stack
for SMC
DM for SMC
DM for
SESM
DM for
USP
SAM21 EM SESM
Server
Server
CMT Server
SAM21
Agent
HLR
Main/CEM Server
coreDA
CEM Server Stack
for HLR Mini-Complex
DM for
SAM21
SMC GUI
CEM GUI
SAM21 SC
DM for
SLR
DM for
Passport
USP
USP
SNMP
Agent
Passport
SMC Server
SLR
SLR
Data Server
Agent
Data Server
Storm
Agent
STORM
DM - Device Manager
Figure 1-24 shows the W-NMS architecture for HLR 200. The devices
introduced in the HLR 200 are monitored using the device managers (DM)
which will feed their information into the existing CEM. The DMs for
SAM21, SESM and USP as well as the CEM processes for the HLR feeds
into the same CEM server stack. The user has an integrated view of the
objects of the HLR, SAM21, SESM and USP.
The CEM server slices all feed their information into the coreDA as well as
the CEM GUI. The coreDA in turn feeds its information into the NSP stack
which sends the information to NSP GUI.
GSM18/UMTS04
Passport based NEs
CEM manages packet network elements such as Passports, through successful
integration with MDM interface. CEM has been supporting MDM managed
Passports and SNMP devices since GEM15. CEM has also been providing the
additional ability for the operator to rename the Passport types and group
Passports shelves under one logical view. The ability to re-type and aggregate
Passports is available through the MDM configuration tool, MDMConfig.
The supported Passport hardware shelf types shall include:
• PP7420 (3 slot PP7400 series device)
•
PP7440 (5 slot PP7400 series device)
•
PP7480 (16 slot PP7400 series device)
•
PP15000
•
PP20000
The Device Manager application which interfaces with the MDM Network
Model and Alarm APIs will discover the Passport load names prior to
discovering the network elements. Based on the load names retrieved from
MDM, the Device Manager will update ‘daNodeId’ attribute to an application
type. The MDMConfig tool can detect the load names, display the application
types and perform validation of aggregation and re-type functionalities.
Aggregation of Passports
Groupings will be based on Passport Application Types as listed in Table 1-3.
Table 1-3
Allowed Grouping Based on Passport Application Types
Group Node Type
Passport Application Types
G_SGSN
G_SGSN
U_SGSN
U_SGSN, AN, PP
WG
WG, AN, PP
Note: If a Passport type cannot be determined at the time that the
Passport needs to be grouped, it will be allowed to be grouped with no
restriction. The Passport will be identified with the type ‘EM’ in the
MDMConfig tool.
Any Passport aggregation performed in the MDMConfig tool will result in the
clearing of existing alarms on the Passports that are being grouped and reraising alarms under this group in CEM.
411-8111-803
Standard
01.06
May 2006
Re-typing of Passports
Only the ‘AN’ type will be allowed during operator override of Passport retype. Type rename is allowed for the application types listed in Table 1-4.
Table 1-4
Allowed Re-typing Based on Passport Application Types
Override Node Type
Passport Application Types
AN
PP
Note: If a Passport type cannot be determined, it will be allowed to be retyped with no restriction. The Passport will be identified with the type
‘EM’ in the MDMConfig tool.
Any manual re-type that occurred in previous releases will result in clearing
of existing alarms on the re-typed Passports and re-raising alarms under these
Passports. However, going forward any re-type of Passport will not cause a
clearing and re-raising of alarms.
UNPM
Universal Number Portability Master (UNPM) is based on the USP
Signalling Server platform. It provides a highly scalable global number
portability service with flexible deployment option.
SLR
CEM also supports the management of SLR network elements which are
based on USP hardware platform and software release. Management of
UNPMs will re-use design and configuration of SLR management.
Figure 1-25 depicts the CEM applications required on the CEM Server to
manage both the Passports and SLR network elements. MDM/MDP software
is required to manage Passports.
GSM18/UMTS04
Figure 1-25
CEM Server Management of SLR and MDM
CEM Software Architecture
CEM Server
CEM GUI
EM Adapter
EM Adapter
dataProcessor*
Object
Manager
CfgBroker*
dataProcessor*
Object
Manager
CfgBroker*
ArReader*
ArReader*
. ArWriter*
arDB
arDB. ArWriter*
Device Adapter Layer
MDM Device Manager
Passport FM Normalizer
Prov IF
USP based Device Manager
FM Normalizer
DataCollector*
DataCollector*
USP OSS Public Interface
TCP/IP
MDM
MDP
MDM/MDP
Passport
UNPM
CEM
NE
Restrictions and limitations for CEM in W-NMS environment
• The supported migration path is from CEM GEM 18 to W-NMS 4.2. All
entities involved such as the CEM Server, W-NMS Servers, SDMs etc.
have to be of GEM18 version prior to the migration. Previous upgrade on
411-8111-803
Standard
01.06
May 2006
the CEM or W-NMS Servers must have finished before the migration is
initiated.
•
The user should not run the configCEMS Tool on either the CEM or WNMS Server during the migration.
•
The user must not run more than one CEM to W-NMS Client process on
the CEM Server and must not initiate more than one migration process
from different CEM Servers to the same W-NMS Server simultaneously.
•
The migration process doesn’t support migrating a non-MDM slice that
has a slice name conflict between the CEM and W-NMS Servers.
•
Any configuration or data changed and alarms acknowledged after the
migration client process is initiated are not migrated to the target slice.
•
All MDM-managed NEs need to be migrated to a single W-NMS Server.
There is no way to split them across different W-NMS Servers.
•
Once MDP has been migrated to the W-NMS Server, IWF and MGW
performance data is no longer available through the CEM Server.
•
During the migration there will be minimal loss of supervision of the
existing Packet Core network. The downtime is the time required to do reconfiguration and to merge data.
•
Include only those that are visible to the user. Describe the
incompatibilities, limitations and restrictions imposed by this feature that
may affect the customer. For example, call waiting is not compatible with
call forwarding busy.Because the alarms on the CEM Server are merged
with the alarms on the W-NMS Main Server for the MDM slice, there will
be a momentary spike in the alarm histogram display on the CEM
Browser.
•
For the MDM slice, the cleared alarms and the alarm history are not
migrated.
•
For the MDM slice, a discrepancy is possible between the timestamp in
the original alarm on the CEM Server and the timestamp in that same
alarm regenerated on the W-NMS Server corresponding to the MDM
slice.
•
During the transitional stage when the slices have been migrated/merged
from a CEM Server to a W-NMS Server but the connection between the
CEM Server and the SDMs/MDMs has not been severed, the alarm
information displayed in the CEM Browser on the CEM Server may not
be in sync with the alarm information displayed in the W-NMS GUI or
the alarms displayed in the CEM Browser launched from the W-NMS
GUI.
•
The ASCII Interface available with the CEM should not be used within
the W-NMS environment.
GSM18/UMTS04
411-8111-803
•
After migration, changes to configuration data on either one of the CEM
and W-NMS Servers, such as thresholds, remain on that Server and could
result in discrepancies in data between the two Servers.
•
Some SNMP devices, such the SMC Agent on the HLR Data Server and
APS in BICN, can only send traps to one server. Therefore, the user needs
to manually set the trap destination to the W-NMS Main Server for these
devices after migration. And the CEM Server will lose supervision on
these NEs after migration.
•
The mass export configuration file is not migrated from the CEM Server
to the W-NMS Server.
•
User Preferences are not migrated from the CEM Server to the W-NMS
Server.
•
Following the migration, OAM users who had accounts on the CEM
Server, will need to have accounts set up in the LDAP Server on the WNMS system. User accounts are not migrated from the CEM Server to the
W-NMS system.
•
Alarm unacknowledgement from the MFT is not propagated to Sun MC
as the Sun MC does not allow this operation.
•
Manual clear from MFT to Sun MC is not supported.
•
The propagation alarm acknowledgment from Sun MC alarm list to MFT
alarm list is done only for open (or active) Sun MC alarms and is subject
to Sun MC client API limitations.
Standard
01.06
May 2006
CEM support for IWF
1
CEM provides the following functionalities to support IWF:
• Fault Management - Fault management of IWF re-uses the CEM
management of Passports. Any fault capability available to Passport is
available for the IWF elements. The IWF element can also be re-typed
automatically if the load name starts with ‘I’.
•
Performance Management - Performance management of IWF extends
thresholding capability to IWF OMs. Threshold values can be set on the
OMs for critical, major and minor categories. The direction of
thresholding can also be set.
•
Maintenance Action - Maintenance actions on IWF components is the
same as performing maintenance actions on Passport components.
•
MDM/MDP GUI Launch (MDM/MDP 15.1) - The IWF node displayed
on CEM GUI has in-context launch of MDP nodal provisioning viewer
and data viewer, previously known as performance viewer. The IWF node
also has a menu item for launching MDM toolset, nmstool.
•
Telnet Capability - The CEM GUI will provide in-context telnet
capability to the selected IWF. This is provided by a ‘telnet’ option on the
pop-up menu invoked from any IWF component.
GSM18/UMTS04
411-8111-803
Standard
01.06
May 2006
2-1
Operational measurements
2
From GEM15 onwards, collection of all the groups available on the network
elements is supported. The correlations are supported only for the list of
Operational Measurements (OM) groups listed in this chapter.
This chapter documents Billing OMs produced by the CEM and additional
key performance indicators, such as formulas and correlations, produced by
the CEM.
In addition, if an OM group that is associated with a Network Element (NE) is
not found in this NTP, you can find it in the applicable NTP, as follows:
• For Base OMs, refer to the following Base/Telecom and DMS-100 NTPs:
— 411-3001-814, Wireless Networks Base/Telecom Operational
Measurements Reference Manual
— 297-8021-814, North American DMS-100 Operational Measurements
Reference Manual
— 297-2621-814, Digital Switching Systems UCS DMS-250
Operational Measurements Reference Manual
•
For MSC OMs, refer to NTP 411-2231-814, GSM / UMTS MSC
Operational Measurements Reference Manual (3 Volumes)
•
For HLR100 OMs, refer to NTP 411-2831-814, GSM / UMTS HLR100/
200 Operational Measurements Reference Manual
GSM18/UMTS04
2-2 Operational measurements
Supported OMs
2
The tables in this section list the OM groups supported in this release from the
different network elements.
The following list describes the columns for Table 2-1 through Table 2-7:
• Group — Identifies the supported OM group.
•
Component — This column lists the network element from which the OM
group is collected.
•
GSM 12.04 — An “x” in this column indicates that the group contains
OMs mentioned in the GSM 12.04 standard.
•
Rel — Indicates the release (GEM08, GEM09, GEM10, etc.) that the OM
groups were first supported.
•
Description — Provides a description of the OM group.
Table 2-1
Supported MSC/VLR OM groups
Group
Component
ANN
GSM
12.04
Rel
Description
MSC
13
Announcements
AOCSS
MSC
10
GSM MSC Advice of Charge
CALLINT
MSC
10
Call Interception
CLISS
MSC
10
Calling Line Identification Supplementary
Services
CLOSS
MSC
10
Calling Line Identification Supplementary
Services
CUGSS
MSC
10
Closed User Group Supplementary Services
EMLPPSS
MSC
(GSM-R)
12
Provides OMs for New eMLPP Supplementary
Service
EXHOCA
MSC
09
Handover reasons
FRDCNTL
MSC
10
Fraud Control
GACODE
MSC
10
GSM Account Code
GINAP
MSC
10
GSM Intelligent Network Application Protocol
GINAP2
MSC
10
GSM Intelligent Network Application Protocol - 2
x
—sheet 1 of 4—
411-8111-803
Standard
01.06
May 2006
Operational measurements 2-3
Table 2-1
Group
Component
GINAP3
MSC
GMAPCH
MSC
GMAPCH2
GSM
12.04
Rel
Description
12
GSM Intelligent Network Application Protocol - 3
x
08
GSM MAP Call Handling
MSC
x
02
GSM MAP Call Handling - 2
GMAPEMGT
MSC
x
08
GSM MAP Equipment Management
GMAPFREC
MSC
10
GSM MAP Fault Recovery
GMAPMMGT
VLR
08
GSM MAP Mobility Management
GMAPSMGT
VLR
x
08
GSM MAP Subscriber Management
GMAPSMS
MSC
x
08
GSM MAP Short Message Service
GMAPSS
VLR
08
GSM MAP Supplementary Services
GMAPSS2
VLR
08
GSM MAP Supplementary Services
GMAPTR
MSC
12
GSM MAP Tracing
GMEANTM
MSC
09
GSM Meantime
GMEANTM2
MSC
09
GSM Meantime
GMMLTRN
MSC
09
GSM Mobility Management Layer transactions
GSMLERRS
MSC
08
GSM Link Interface Unit (LIU) Errors
GSMLUSAG
MSC
08
GSM Link Interface Unit (LIU) Usage
GSMUSSD
MSC
10
GSM Unstructured Supplementary Data
GSRVCBAR
MSC
10
GSM Services Barred OM Group
HO2GTO2G
MSC
15
2G to 2G Handovers
HO2GT2G2
MSC
15
Extension OM group for HO2GTO2G
HO3GTO3G
MSC
15
3G to 3G Handovers
HO3GTO2G
MSC
15
3G to 2G Handovers
HO2GTO3G
MSC
15
2G to 3G Handovers
IN1SUM
MSC
10
Number Services Code Call Summary
—sheet 2 of 4—
GSM18/UMTS04
Table 2-1
Group
Component
MCLUSTER
GSM
12.04
Rel
Description
MSC
(GSM-R)
12
Events in a Mobile Cluster Call (VBS or VGCS)
Terminating to a List of Cells in the Service Area
MSCCALLR
MSC
10
MSC Call Re-establishment
MSCCBSS
MSC
10
MSC Call Barring Supplementary Services
MSCCFSS
MSC
08
MSC Call Forwarding Supplementary Services
MSCCNAM
MSC
10
MSC Calling Name Delivery
MSCCP
MSC
08
MSC Call Processing
MSCCP2
MSC
08
MSC Call Processing 2
MSCCP3
MSC
08
MSC Call Processing 3 - Classmark update
message of type 2
MSCCWTSS
MSC
10
MSC Call Waiting Supplementary Services
MSCDSRV
MSC
10
MSC Data Services
MSCEXTSS
MSC
10
MSC Extension Service Supplementary
Services
MSCGCS
MSC
(GSM-R)
12
Usages of VGCS and VBS Services
MSCHLDSS
MSC
10
MSC Call Hold Supplementary Services
MSCMPTSS
MSC
10
Mobile Switching Services Center Multi-Party
MSCRLT
MSC
10
MSC Release Link Trunk
MSCSMS
MSC
08
MSC Short Message Service
MSC3GHO2
MSC
15
3G MSC Handover
MSCTRACE
MSC
10
MSC Subscriber Trace
MSC2GHO2
MSC
15
2G MSC Handover
MSCUPLNK
MSC
(GSM-R)
12
Uplink Requests Received and Uplink Requests
Rejected for VGCS Group Calls
x
x
x
—sheet 3 of 4—
411-8111-803
Standard
01.06
May 2006
Table 2-1
Group
Component
NPACGGRP
GSM
12.04
Rel
Description
MSC
10
Local Number Portability Automatic Code
Gapping
NPSUM
MSC
10
Local Number Portability Service Call Summary
OFFBDIN
MSC
10
Off-Board IN Access
PETCUT
MSC
10
PET Customer Unauthorized Treatment
TFACGGRP
MSC
10
Toll-Free Automatic Code Gapping
TFSUM
MSC
10
Toll-Free Service Call Summary
VLR
MSC
08
Visitor Location Register Activities
VLR2
VLR
08
VLR4
VLR
08
VLR5
VLR
08
—sheet 4 of 4—
Table 2-2
Supported single-tuple MSC OM groups
Group
Component
CPADPRBK
GSM
12.04
Rel
Description
MSC
11
CPIPP Address Pair Block OMs
CSRPL5SZ
MSC
11
Call Recording Stream Sub Recording Unit
Pool5 Size OMs
CSRPL1SZ
MSC
11
Pool1 Size OMs
CSRPL4SZ
MSC
11
Pool4 Size OMs
CSRPL4SZ
MSC
11
Pool3 Size OMs
—sheet 1 of 2—
GSM18/UMTS04
Table 2-2
Supported single-tuple MSC OM groups
FPFMSGS
MSC
11
FPF MESSAGES OMs
FPXLMSGB
MSC
11
FPF XL Message Blocks OMs
GCISBXBK
MSC
11
GSM CI SUB Extension Block OMs
GINAPXBK
MSC
11
GSM INAP Extension Blocks OMs
GMAMSXBK
MSC
11
GSM MAP MSC Extension Block OMs
GMASCXBK
MSC
11
GSM MAP SCCP Extension Blocks OMs
GMAVLXBK
MSC
11
GSM MAP VLR Extension Block OMs
GSMSGBKS
MSC
11
GSM Messages Block OMs
GUSSDMMU
MSC
11
GSM Unstructured Supplementary Service
Data on the MMU
HLDSSMMU
MSC
11
MSC Call-Hold Supplementary Services
Counts call hold operations on the MMU
HOPRMXBK
MSC
11
Handover Parm Extension Blocks OMs
MPTSSMMU
MSC
11
Mobile Switching Services Center Multi-Party
Supplementary Service
PERMEXTO
MSC
11
PERM EXT OMs
—sheet 2 of 2—
Table 2-3
Supported multi-tuple MSC/VLR OM groups
Group
Component
CLINTMMU
GSM
12.04
Rel
Description
MSC
12
Call Intercept on MMUs
EXHOCAMU
MSC
12
Handover Cause OMs on MMUs
GINAPMMU
MSC
12
IN on MMUs
GINAP2MU
MSC
12
IN on MMUs - 2
GINAP3MU
MSC
12
IN on MMUs - 3
—sheet 1 of 3—
411-8111-803
Standard
01.06
May 2006
Table 2-3
GCBK
MSC
10
GSM Code Blocking
GMCHMMU
MSC
12
GSM MAP Call Handling OMs on MMUs
GMCH2MMU
MSC
12
GSM MAP Call Handling OMs on MMUs - 2
GMEANTMU
MSC
12
Average Time OMs for Data Calls on MMUs
GMEAN2MU
MSC
12
Average Time OMs for Intr/Inter LUs on MMUs
GMEMGTMU
MSC
12
GSM MAP Mobility Management OMs on
MMUs
GMFREMMU
MSC
12
GSM MAP Fault Recovery OMs on MMUs
GMMLTRMU
MSC
12
MM Layer Transactions OMs on MMUs
GMMMGTMU
VLR
12
GSM MAP Mobility Management OMs on
MMUs
GMSMGTMU
VLR
12
GSM MAP Subscriber Management OMs on
MMUs
GMSMSMMU
MSC
12
GSM MAP SMS OMs on MMUs
GMSSMMU
VLR
12
GSM MAP Supplementary Service OMs on
MMUs
GMSS2MMU
VLR
12
GSM MAP Supplementary Service OMs on
MMUs - 2
GMTRMMU
MSC
12
GSM MAP Activate/Deactivate Trace Mode on
MMUs
GPRP
MSC
10
GSM Pre-Route Peg
GSBARMMU
MSC
12
GSM MAP Service Barring on MMUs
GTASOM
MSC
HO2G2GMU
MSC
15
HO2GTO2G for MMU
H2G2G2MU
MSC
15
HO2GT2G2 for MMU
HO3G3GMU
MSC
15
HO3GTO3G for MMU
HO3G2GMU
MSC
15
HO3GTO2G for MMU
HO2G3GMU
MSC
15
HO2GTO3G for MMU
GSM Traffic Analysis System
—sheet 2 of 3—
GSM18/UMTS04
Table 2-3
MSCCP3MU
MSC
12
Classmark/Encryption/Authentication
MSCCPSRV
MSC
09
Data Services
MSCCRMMU
MSC
12
Call Re-establishment OMs on MMUs
MSCSMSMU
MSC
12
SMS Functionality OMs on MMUs
MSCTRMMU
MSC
12
MS Trace OMs on MMUs
M2GHO2MU
MSC
15
MSC2GHO2 for MMU
M3GHO2MU
MSC
15
MSC3GHO2 for MMU
VLRMMU
VLR
12
VLR Group 1 - LUs Containing IMSI or TMSI on
MMUs
VLR2MMU
VLR
12
VLR Group 2 - More LU Information on MMUs
VLR3MMU
VLR
12
VLR Group 3 - Page/Search Information per
LAC on MMUs
VLR4MMU
VLR
VLR Group 4 - Page/Search Information per
MSC on MMUs
VLR5MMU
VLR
VLR Group 5 - Sub Counters and TMSI Reuse
on MMUs
VLR3
VLR
x
08
Visitor Location Register Activities 3
—sheet 3 of 3—
Table 2-4
Supported single-tuple Base OM groups
Group
Component
BRSTAT
GSM
12.04
Rel
Description
Base
08
BRISC Occupancy Status
C7MTP
Base
10.1
CCS7 Message Transfer Part
C7SCCP
Base
10.1
CCS7 Signaling Connection Control Part
C7SCCPCO
Base
08
C7 SCCP Connection Oriented
CP
Base
08
Call Processing Software Resources
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 2-4
Supported single-tuple Base OM groups
CP2
Base
08
Call Processing Software Resources 2
ENETPLNK
Base
10.1
ENET Peripheral Side Links
ISUPCKTA
Base
10
ISUP Circuit Availability
ISUPCONN
Base
10
ISUP Connection
ISUPERRS
Base
10
ISDN User part Errors
OFZ
Base
08
Office Traffic Summary
OFZ2
Base
08
Office Traffic Extension Summary
OTS
Base
11
Office Traffic Summary
STORE
Base
09
Memory usage
SYSPERF
Base
10.1
System Performance
TRMTCM
Base
11
Customer Miscellaneous Treatment
TRMTCM2
Base
11
Customer Miscellaneous Treatment
TRMTCU
Base
10
Customer Unauthorized Treatment
TRMTCU2
Base
10
TRMTCU3
Base
11
TRMTER
Base
11
Equipment-related Treatment
TRMTFR
Base
10
Failure-related Treatment
TRMTFR2
Base
10
TRMTFR3
Base
10
TRMTPR
Base
11
Protocol-related Treatment
TRMTRS
Base
10.1
Resource Shortage Treatment
—sheet 2 of 2—
GSM18/UMTS04
Table 2-5
Supported multi-tuple Base OM groups
Group
Component
ANN
GSM
12.04
Rel
Description
Base
10.1
Announcements
C7LINK1
Base
10.1
CCS7 Link Group
C7LINK2
Base
10.1
CCS7 Link Group
C7LINK3
Base
10.1
CCS7 Link Group
C7LKSET
Base
10.1
CCS7 Linkset
C7ROUTE
Base
10.1
CCS7 Route
C7ROUTER
Base
10.1
CCS7 Router
C7RTESET
Base
10.1
CCS7 Routeset
CF3P
Base
10.1
Three-port Conference Circuits
CM
Base
10.1
Computing Module
CPMMU
Base
12
Call Processing Software Resource OM on the
MMU
CP2MMU
Base
12
Call Processing Software Resource OM on the
MMU - 2
CPRPL1SZ
Base
12
Pool1 Size OMs
CPRPL2SZ
Base
12
Call Recording Stream Sub Primary Unit Pool2
Size OMs
CPRPL3SZ
Base
12
Pool3 Size OMs
CPRPL4SZ
Base
12
Pool4 Size OMs
CPRPL5SZ
Base
12
Pool5 Size OMs
EXT
Base
08
Extension Block
FXLGAXBK
Base
12
FPF Extra large Auxiliary Block OMs
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 2-5
Supported multi-tuple Base OM groups
FLRGAXBK
Base
12
FPF Large Auxiliary Block OMs
FMDMAXBK
Base
12
FPF Medium Auxiliary Block OMs
FSMLAXBK
Base
12
FPF Small Auxiliary Block OMs
FHUGAXBK
Base
12
FPF Huge Auxiliary Block OMs
ISUPCGRP
Base
10
ISUP Circuit Group Availability
ISUPCONG
Base
10
ISUP Congestion
ISUPUSAG
Base
09
ISDN User Part Utilization
MS
Base
10.1
Message Switch
TCAPERRS
Base
10
Transaction Capabilities Application Part Errors
Count
TCAPUSAG
Base
10
Transaction Capabilities Application Part Usage
Measurements
TONES
Base
10.1
Tones
TRK
Base
08
Trunk Group - info on traffic for each trunk group
UTR
Base
10.1
Universal Tone Receiver
XACORE
Base
11
XACORE Resource: Processor Element
x
—sheet 2 of 2—
Table 2-6
Supported single-tuple HLR100 OM groups
Group
Element
GHLRADM
GSM
12.04
Release
Description
HLR
10
GSM HLR Administration (1 of 3)
GHLRADM2
HLR
10
GHLRADM3
HLR
10
GHLRBS
HLR
10
GSM HLR Basic Services
—sheet 1 of 3—
GSM18/UMTS04
Table 2-6
Group
Element
GHLRCH
GSM
12.04
Release
Description
HLR
10
GSM HLR Call Handling
GHLRCOS
HLR
10
GSM HLR Class of Service
GHLRFREC
HLR
10
GSM HLR Fault Recovery
GHLRODB
HLR
10
GSM HLR Operator Determined Barring
GHLRODBT
HLR
10
GSM HLR Operator Determined Barring Traffic
GHLRROAM
HLR
10
HLR Roaming
GHLRSIMR
HLR
10
GSM HLR Subscriber Identity Module
Replacement
GHLRSMGT
HLR
10
GSM HLR Subscriber Management for Version 1
GHLRSMS
HLR
10
HLR Short Message Service
GHLRSSCB
HLR
10
GSM HLR Supplementary Services Call Barring
GHLRSSCF
HLR
10
GSM HLR Supplementary Services Call
Forwarding
GHLRSSCW
HLR
10
GSM HLR Supplementary Services Call Waiting
GHLRSSPW
HLR
10
GSM HLR Register Password
GHSBYADM
HLR
13
GSM HLR StandBY ADMinistration
HACCOUNT
HLR
10
HLR Accounting Code Provisioning Options
HCMLMPT
HLR
10
HLR CAMEL Miscellaneous Provider Traffic
HCMLMRT
HLR
10
HLR CAMEL Miscellaneous Requester Traffic
HCUGSRI
HLR
10
HLR Closed User Group Send Routing
Information Traffic
HCUGSUB
HLR
10
HLR Closed User Group Subscription Data
HEQACCS
HLR
10
HLR Equal Access
HISTAT
HLR
10
GSM HLR Subscriber IMSI Status
HLRCAMEL
HLR
10
GSM HLR CAMEL Subscription Data
—sheet 2 of 3—
411-8111-803
Standard
01.06
May 2006
Table 2-6
Group
Element
HLRCAMLT
GSM
12.04
Release
Description
HLR
10
HLR CAMEL Traffic
HLREXTT
HLR
10
HLR Extension Services Traffic
HLRGPRS
HLR
11
Statistics relating to the number of subscribers in
the GHLRGPRS table, and how many subscribers
have one or more PDPs provisioned
HLRHB
HLR
10
HLR HotBill
HLRIN
HLR
10
HLR Intelligent Network
HLRINT
HLR
10
HLR Intelligent Network Traffic
HLRMAPT
HLR
10
GSM HLR MAP Traffic
HLRMISCH
HLR
10
HLR Miscellaneous Call Handling
HLRORT
HLR
10
GSM HLR Optimal Routing Traffic
HLRWORK
HLR
10
HLR Work-load Handling
HODBMISC
HLR
10
GSM HLR Operator Determined Barring for
ODBMISC categories
HREGSUB
HLR
10
HLR Regional Subscription
HSMG2
HLR
10
HLR Subscriber Management for Phase 2
HSUBSMWD
HLR
10
HLR Subscriber Message Waiting Data
XASTAT
HLR
9
Equivalent functionality of the BRSTAT group for
XA-Core
—sheet 3 of 3—
GSM18/UMTS04
Table 2-7
Supported multi-tuple HLR100 OM groups
Group
Element
AUCSTATS
GSM
12.04
Release
Description
HLR
10.1*,
11* 12
Authentication Center Statistic
GHLRMMGT
HLR
10.1*,
11* 12
GSM HLR Mobility Management
HBOOSTER
HLR
10
HLR Requests sent to Booster
HCISSOPS
HLR
10.1*,
11* 12
HLR Call Independent Supplementary Services
Operations
HEXTSUB
HLR
10
HLR Extension Service Supplementary Service
Provisioning Statistics
HLRCAP
HLR
10
HLR Capacity
HOPTMMGT
HLR
10.1*,
11* 12
HLR Optimized Mobility Management
HMWDSC
HLR
10
HLR Message Waiting Data for Service Centers
HSMSERR
HLR
10
GSM HLR Short Message Service Errors
HSMSOPS
HLR
10
HLR Short Message Service Operations
HSSERROR
HLR
10
HLR Supplementary Service Errors
HSUBPRTN
HLR
10
HLR Subscriber Partition Provisioning Statistics
HVLRSMGT
HLR
10.1*,
11* 12
HLR Visitor Location Register Subscriber
SRINODE
HLR
10
Send Routing Information Per Node
*Available in GEM10.1 and GEM11 using mass export only.
Note: Four OM groups are combined into one OM group called
GHLRMMGT. GHLRMMGT contains:
— GHLRMMGT (GSM HLR Mobility Management)
— HCISSOPS (HLR Call Independent Supplementary Services
Operations)
411-8111-803
Standard
01.06
May 2006
— HOPTMMGT (HLR Optimized Mobility Management)
— HVLRSMGT (HLR Visitor Location Register Subscriber
Management)
Refer to Chapter 6, “Mapped resources” for tables specifying the OM groups
supported and mapped resources for the OM groups for the following NE types:
• U-SGSN
•
G-SGSN
•
GGSN Shasta
•
SIG
•
AN
GSM18/UMTS04
Summary OMs
2
Four summary OM groups are produced for every regular group. The
summary groups have one tuple each. The fields will be an accumulation of
the corresponding fields in the tuples of the regular group.
The names of the summary groups will be the name of the regular group with
one of _SUM, _AVG, _MIN, or _MAX appended to the name of the regular
group.
For example, group X has five fields A, B, C, D and E, with four tuples. The
summary groups will be named X_SUM, X_AVG, X_MIN, and X_MAX.
The registers in X_SUM will be the summation of the tuples in group X.
Likewise for X_AVG (average of the registers) et. al. There will be exactly
one tuple in each of the summary groups.
The format of the resource name for the single tuple in each of the summary
groups is a modification of the resource names in the regular group. Up to the
last component of the name, it will be the same as the resource names in the
regular group. The final component and instance ID will be replaced by the
group name and one of "-NE_SUM", "-NE_AVG", "-NE_MIN" or "NE_MAX". For example a resource name in a regular group might look like
this:
~MDM-mdm-test/EM-UCARF001/ATMIF-90
The resource name of the tuple in the averaging summary group would then be:
~MDM-mdm-test/EM-UCARF001/AtmInterface-NE_AVG
Additionally, an extra field is appended to the single tuple in each of the
summary groups. This field will provide a count of the number of tuples in
the regular group which were accumulated to come up with the summary
tuple. This will allow weighted averages and other such calculations to be
done on the summary tuples.
Note: For DMS nodes, two new OM groups "VLR3_SUM" and
"VLRMMU_SUM" has been added. These groups have only one tuple
and have the same set of registers as the normal groups. However the
values of these registers are the sum of the values across all the tuples.
411-8111-803
Standard
01.06
May 2006
Correlated OMs
2
Table 2-8 shows the definitions of the correlated OMs. The “Name” column
lists the internal name for the correlated OMs. All arithmetic calculations are
based on actual OM registers or the correlated OMs.
Note 1: All OM registers referenced below assume that the extension
registers have already been amalgamated.
Note 2: The arithmetic calculation results for correlated OMs containing
division (“/”) will be multiplied by 100.
Table 2-8
Correlated MSC OM groups
Group
Name
Description
Definition (OM group:register)
C7SCCPCO
C7CCTXSR
Connection Confirmations Transmitted to Connection
Requests Received Ratio (%)
= C7CCTX / C7CRRX * 100
C7CCRXSR
Connection Confirmations Received to Connection Requests
Transmitted Ratio (%)
= C7CCRX / C7CRTX * 100
C7RCTXSR
Connection Released Complete Transmitted to Connection
Release Received Ratio (%)
= C7RLCTX / C7RLSDRX * 100
C7RCRXSR
Connection Released Complete Received to Connection
Release Transmitted Ratio (%)
= C7RLCRX / C7RLSDTX * 100
C7CRTXFR
Connection Refused Transmitted to Class 2 Transmitted
Ratio (%)
= C7CREFTX / C7CLS2TX * 100
C7CRRXFR
Connection Refused Received to Class 2 Received Ratio (%)
= C7CREFRX / C7CLS2RX * 100
—sheet 1 of 31—
GSM18/UMTS04
Table 2-8
Group
Name
Description
C7COFAFR
Connection Failed to Connection Released Received Ratio
(%)
= C7COFAIL / C7RLSDRX * 100
C7COMRFR
Connection Oriented Message Request Rejected to
Connection Request Received Ratio (%)
= C7COMREJ / C7CRRX * 100
Transmitted Overhead Ratio (%)
C7TXOVHR
= (C7CLS2TX - C7DT1TX) / C7CLS2TX * 100
Received Overhead Ratio (%)
C7REOVHR
= (C7CLS2RX - C7DT1RX) / C7CLS2RX * 100
HLRSUMPAGE
HLRULNOISD
HLR Update Location Message with No Insert Subscriber
Data Message
= sum of all ULNOISD
HLRREGSSREQ
HLR Register Supplementary Service Requests
= sum of all REGSSREQ
HLRERASSREQ
HLR Erase Supplementary Service Requests
= sum of all ERASSREQ
HLRACTSSREQ
HLR Active Supplementary Service Requests
= sum of all ACTSSREQ
HLRDACSSREQ
HLR Deactive Supplementary Service Requests
= sum of all DACSSREQ
HLRRPWSSREQ
HLR Register Password Request
= sum of all RPWSSREQ
—sheet 2 of 31—
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
HLRINTSSREQ
HLR Interrogate Supplementary Service Requests
= sum of all INTSSREQ
HLRAUCRQ
HLR Authentication Center Request
= sum of all AUCRQ
HLRAUCERR
HLR Authentication Center Errors
= sum of all AUCERR
HLRAUCOVLD
HLR Authentication Center Overloads
= sum of all AUCOVLD
HLRAUCTOUT
HLR Authentication Center Time-outs
= sum of all AUCTOUT
HLRCRRPRN
HLR Call Routing Requests involving a PRN
PRNRQ/ACTIVE
HLROCRR
HLR Other Call Routing Requests
(SRIRQ-PRNRQ)/ACTIVE
HLRLURQ
HLR Location Update Request
LURQ/ACTIVE
HLRAUCREQ
HLR Authentication Requests
(SPAURQ + SAIREQS)/ACTIVE
HLRSMSR
HLR SMS Routing Requests
SRMREQ/ACTIVE
HLRRSMDR
HLR Report SM Delivery Requests
RDSREQ/ACTIVE
—sheet 3 of 31—
GSM18/UMTS04
Table 2-8
Group
Name
Description
HLRRFSMR
HLR Ready for SM Requests
RFSMREQ/ACTIVE
HO2GTO2G
AINEMHPC
Rate of the number of attempted 2G Incoming Inter-MSC
handovers over total number of attempts to establish a
communication channel between a BSS to/from MS (%)
(A2GIEMHO / (MMBID + MLBID+ LMBID) *100 )
AOERMHPC
Rate of the number of attempted 2G Outgoing Inter-MSC
handovers over total number of attempts to establish a
communication channel between a BSS to/from MS (%)
(A2GOEMHO / (MMBID + MLBID+ LMBID) *100 )
ARAMCHPC
Rate of the number of attempted 2G Intra MSC-A handovers
over total number of attempts to establish a communication
channel between a BSS to/from MS (%)
(A2GRAMAH / (MMBID + MLBID+ LMBID) *100 )
ASBHBHPC
Rate of the number of attempted 2G Subsequent Handbacks
over total number of attempts to establish a communication
channel between a BSS to/from MS (%)
(A2GSUBHB / (MMBID + MLBID+ LMBID) *100 )
ASBIMHPC
Rate of the number of attempted Subsequent Inter-MSC
Handovers after 2G-to-2G Handover over total number of
attempts to establish a communication channel between a
BSS to/from MS (%)
(A2GSBEMH / (MMBID + MLBID+ LMBID) *100 )
TAOUERMH
Sum of number of attempted 2G Outgoing Inter-MSC
handovers, Subsequent Inter-MSC Handovers after 2G-to-2G
Handover and 2G Subsequent Handbacks
(A2GOEMHO + A2GSBEMH + A2GSUBHB)
—sheet 4 of 31—
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
TEHA
Sum of the number of attempted 2G Intra MSC-A handovers,
Outcoming Inter-MSC handovers, Subsequent Inter-MSC
Handovers after 2G-to-2G Handover and 2G Subsequent
Handbacks
(A2GRAMAH + A2GOEMHO + A2GSBEMH+ A2GSUBHB)
TFOUERMH
Number of unsuccessful attempts with respect to 2G
Outgoing Inter-MSC handovers, Subsequent Inter-MSC
Handovers after 2G-to-2G Handover and 2G Subsequent
Handbacks
(A2GOEMHO + A2GSBEMH + A2GSUBHB) - (S2GOEMHO
+ S2GSBEMH + S2GSUBHB)
TOUERMHO
Successful attempts with respect to 2G Outgoing Inter-MSC
handovers, Subsequent Inter-MSC Handovers after 2G-to-2G
Handover and 2G Subsequent Handbacks
S2GOEMHO + S2GSBEMH + S2GSUBHB
MSCCP
MCSUCCRT
All Mobile Calls Success Ratio (%)
= (MMSUCC+MLSUCC+LMSUCC+LLSUCC) /
(MMBID+MLBID+LMBID+LLBID) * 100
CIM1FAIL
Ciphering Mode Failures (phase 1)
= CIM1ATT - CIM1SUC
CIM2FAIL
Ciphering Mode Failures (phase 2)
= CIM2ATT - CIM2SUC
LLBIDF
Land to Land Bid Failures
= LLBID - LLSUCC
LMBIDF
Land to Mobile Bid Failures
= LMBID - LMSUCC
—sheet 5 of 31—
GSM18/UMTS04
Table 2-8
Group
Name
Description
MEEBIDF
Mobile Subscriber Emergency Call Failures
= MEEBID - MEESUCC
MLBIDF
Mobile to Land Bid Failures
= MLBID - MLSUCC
MMBIDF
Mobile to Mobile Bid Failures
= MMBID - MMSUCC
TBIDFAIL
Total Bid Failures (Mobile to Mobile, Mobile to Land, Land to
Mobile and Land to Land)
= MMBIDF + MLBIDF + LMBIDF + LLBIDF
TBIDSUCC
Total Bid Successes (Mobile to Mobile, Mobile to Land, Land
to Mobile and Land to Land)
= MMSUCC + MLSUCC + LMSUCC + LLSUCC
TGASRIRN
Total Gateway Calls Involving an SRI and an MSRN
= LLSRIRN + MLSRIRN
TGTRANS
Total Gateway Calls Where a Transit Record is Required
= LLTRANS + MLTRANS
TMSIRF
TMSI Reallocation Failures
MSCCP:TMSIRAT+MSCCP:TMSILAT-MSCCP:TMSIRSU
TOTBID
Total Bids (Mobile to Mobile, Mobile to Land, Land to Mobile
and Land to Land)
= MMBID + MLBID + LMBID + LLBID
TOTESTAB
Total Established Calls
= MMESTAB + MLESTAB + LMESTAB + LLESTAB
—sheet 6 of 31—
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
MCETABRT
All Mobile Calls Established Ratio (%)
= (MMESTAB+MLESTAB+LMESTAB+LLESTAB) /
(MMBID+MLBID+LMBID +LLBID) * 100
LMSUCCRT
Land to Mobile Calls Success Ratio (%)
= LMSUCC / LMBID * 100
LMETABRT
Land to Mobile Calls Established Ratio (%)
= LMESTAB / LMBID * 100
MLSUCCRT
Mobile to Land Calls Success Ratio (%)
= MLSUCC / MLBID * 100
MLETABRT
Mobile to Land Calls Established Ratio (%)
= MLESTAB / MLBID * 100
MMSUCCRT
Mobile to Mobile Calls Success Ratio (%)
= MMSUCC / MMBID * 100
MMETABRT
Mobile to Mobile Calls Established Ratio (%)
= MMESTAB / MMBID * 100
LLSUCCRT
Land to Land Calls Success Ratio (%)
= LLSUCC / LLBID * 100
LLETABRT
Land to Land Calls Established Ratio (%)
= LLESTAB / LLBID * 100
TOTGA
Total Incoming Gateway Calls
= SRICFU + SRIMSRN
TOTTMBID
Total Terminated Call Attempts
= MMBID + LMBID
—sheet 7 of 31—
GSM18/UMTS04
Table 2-8
Group
Name
Description
INCATM
PSTN to Local Mobile
= SRIMSRN - (MLSRIRN + LLSRIRN)
MTCABORI
Mobile Terminated Call Attempt From Other MSCs
= (MMBID + LMBID) - (SRIMSRN - (MLSRIRN + LLSRIRN) MMBID)
TMESTAB
Mobile Terminated Calls Established
= MMESTAB + LMESTAB
MTCAOTCF
Mobile Terminated Call Attempts other than Call Forwarded
= LMBID + MMBID - MMESTAB - LMESTAB MSCCFSS:GCFBINVO -MSCCFSS:GCFRYINV MSCCFSS:GCFRCINV
TOTMOBID
Mobile Originated Call Attempts
= MMBID + MLBID
MOBIDTL
Mobile Originated Call Attempts to PSTN
= MLBID + MLSRIRN
LLBIDOTH
Land to Land Call Attempts other than PSTN to Gateway or
transit billed
= LLBID - LLSRIRN - LLTRANS
TOTMBID
Mobile Call Attempts
= MMBID + MLBID + LMBID
MBIDPSUB
Mobile Call Attempts per 100 Subscribers
= (MMBID + MLBID + LMBID) / (VLR:SUBSREG +
VLR:SUBSREGR)
MSCSMS
SMMOFAIL
Short Message Service Mobile Originated Failures
MSCSMS:SMMOATT-MSCSMS:SMMOSUC
—sheet 8 of 31—
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
SMMOMMAF
Short Message Service Mobile Originated More Memory
Available Failures
MSCSMS:SMMOMMAA-MSCSMS:SMMOMMAS
SMMOSURT
Short Message Mobile-Originated Successes Rate (%)
= SMMOSUC / SMMOATT *100
SMMOIWRR
Short Message Mobile-Originated Interworking MSC Rejects
Rate (%)
= SMMOIWRJ / SMMOATT *100
SMMOSCRR
Short Message Mobile-Originated Service Center Rejects
Rate (%)
= SMMOSCRJ / SMMOATT *100
SMMOVLRR
Short Message Mobile-Originated MSC-VLR Rejects Rate
(%)
= SMMOVLRJ / SMMOATT *100
SMMOEXRT
Short Message Mobile-Originated Unexpected Errors Rate
(%)
= SMMOEXTC / SMMOATT *100
SMMOATPC
Short Message Mobile-Originated Attempts per 100 Calls
= SMMOATT / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
SMMOSUPC
Short Message Mobile-Originated Successes per 100 Calls
= SMMOSUC / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
SMMOIWRPC
per 100 Calls
= SMMOIWRJ / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
—sheet 9 of 31—
GSM18/UMTS04
Table 2-8
Group
Name
Description
SMMOSCRPC
Short Message Mobile-Originated Service Center Rejects
per 100 Calls
= SMMOSCRJ / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
SMMOVLRPC
Short Message Mobile-Originated MSC-VLR Rejects per 100
Calls
= SMMOVLRJ / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
SMMOEXPC
Short Message Mobile-Originated Unexpected Errors per
100 Calls
= SMMOEXTC / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
SMMTFAIL
Short Message Service Mobile Terminated Failures
MSCSMS:SMMTATT-MSCSMS:SMMTSUC
SMMTRPF
Short Message Service Mobile Terminated Relay layer
Protocol Failures
MSCSMS:SMMTRPA-MSCSMS:SMMTRPS
SMMTSURT
Short Message Mobile-Terminated Successes Rate (%)
= SMMTSUC / SMMTATT *100
SMMTABER
Short Message Mobile-Terminated Absent Subscriber Errors
Rate (%)
= SMMTABSB / SMMTATT *100
SMMTEXER
Short Message Mobile-Terminated TC1N/TR1N Expiry &
Unexpected Error Rate (%)
= SMMTEXTC / SMMTATT *100
—sheet 10 of 31—
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
SMMTVSRR
Short Message Mobile-Terminated MSC-VLR Reject Rate
(%)
= SMMTVLRJ / SMMTATT *100
SMMTMSRR
Short Message Mobile-Terminated MS Reject Rate (%)
= SMMTMSRJ / SMMTATT *100
SMMTPTOR
Short Message Mobile-Terminated Page Timeout Rate (%)
= SMMTPGTO / SMMTATT *100
SMMTQFRT
Short Message Mobile-Terminated Queue Full Rate (%)
= SMMTQFUL / SMMTATT *100
SMMTARPC
Short Message Mobile-Terminated Attempt per 100 Calls
= SMMTATT / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
SMMTSUPC
Short Message Mobile-Terminated Successes per 100 Calls
= SMMTSUC / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
SMMTABPC
Short Message Mobile-Terminated Absent Subscriber Errors
per 100 Calls
= SMMTABSB / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
SMMTEXPC
Short Message Mobile-Terminated TC1N/TR1N Expiry &
Unexpected Errors per 100 Calls
= SMMTEXTC / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
SMMTVSRPC
Short Message Mobile-Terminated MSC-VLR Rejects per
100 Calls
= SMMTVLRJ / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
GSM18/UMTS04
Table 2-8
Group
Name
Description
SMMTMSRPC
Short Message Mobile-Terminated MS Rejects per 100 Calls
= SMMTMSRJ / (MSCCP:MMBID +MSCCP: MLBID +
MSCCP:LMBID)*100
SMMTPTOPC
Short Message Mobile-Terminated Page Timeouts per 100
Calls
= SMMTPGTO / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
SMMTQFPC
Short Message Mobile-Terminated Queue Full per 100 Calls
= SMMTQFUL / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID)*100
MSCSMSMU
SMOEXRTU
Short Message Mobile-Originated Unexpected errors Rate
per MMU
MSCSMSMU:SMOEXCMU / MSCSMSMU:SMOATTMU *
100
SMOFAILU
Short Message Service Mobile Originated Failures per MMU
MSCSMSMU:SMOATTMU - MSCSMSMU:SMOSUCMU
SMOIWRRU
Rates per MMU
MSCSMSMU:SMOWRJMU / MSCSMSMU:SMOATTMU *
100
SMOMMAFU
Short Message Service Mobile Originated More Memory
Available Failures per MMU
MSCSMSMU:SMMMAAMU - MSCSMSMU:SMMMASMU
SMOSCRRU
Short Message Mobile Originated Service Centre Rejects
Rate per MMU
MSCSMSMU:SMSCRJMU / MSCSMSMU:SMOATTMU *
100
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
SMOSURTU
Short Message Mobile Originated Successes Rate per MMU
MSCSMSMU:SMOSUCMU / MSCSMSMU:SMOATTMU *
100
SMOVLRRU
Short Message Mobile Originated MSC-VLR Rejects Rate
per MMU
MSCSMSMU:SMOVLRMU / MSCSMSMU:SMOATTMU *
100
SMTABERU
Short Message Mobile Terminated Absent Subscriber Errors
Rate per MMU
MSCSMSMU:SMTBSBMU / MSCSMSMU:SMTATTMU * 100
SMTEXERU
Short Message Mobile Terminated TC1N/TR1N Expiry and
Unexpected Error Rate per MMU
MSCSMSMU:SMTEXCMU / MSCSMSMU:SMTATTMU * 100
SMTFAILU
Short Message Service Mobile Terminated Failures per MMU
MSCSMSMU:SMTATTMU - MSCSMSMU:SMTSUCMU
SMTMSRRU
Short Message Mobile Terminated MS Reject Rate per MMU
MSCSMSMU:SMTSRJMU / MSCSMSMU:SMTATTMU * 100
SMTPTORU
Short Message Mobile Terminated Page Timeout Rate per
MMU
MSCSMSMU:SMPGTOMU / MSCSMSMU:SMTATTMU * 100
SMTQFRTU
Short Message Mobile Terminated Queue Full Rate per MMU
MSCSMSMU:SMQFULMU / MSCSMSMU:SMTATTMU * 100
SMTRPFMU
Short Message Service Mobile Terminated Relay layer
Protocol Failures per MMU
MSCSMSMU:SMTRPAMU - MSCSMSMU:SMTRPSMU
GSM18/UMTS04
Table 2-8
Group
Name
Description
SMTSURTU
Short Message Mobile Terminated Successes Rate per MMU
MSCSMSMU:SMTSUCMU / MSCSMSMU:SMTATTMU * 100
SMTVSRRU
Short Message Mobile Terminated MSC-VLR Reject Rate
per MMU
MSCSMSMU:SMTVLRMU / MSCSMSMU:SMTATTMU * 100
STORE
TDSUSED
Data Store
= DSUSEDK + (DSUSEDM * 1024)
TPSUSED
Program Store
= PSUSEDK + (PSUSEDM * 1024)
TDSAVAIL
Data Available Store
= DSAVAILK + (DSAVAILM * 1024)
TPSAVAIL
Program Available Store
= PSAVAILK + (PSAVAILM * 1024)
TOTFREE
Available Store
= FREEKB + (FREEMB * 1024)
TOTSPARE
Spare Store
= SPAREKB + (SPAREMB * 1024)
TOTAPM
Total Addressable Physical Memory
= TOTALKB + (TOTALMB * 1024)
SUMPAGE
VLRSUBS
Number of VLR Subscribers
= VLR:SUBSREG + VLR:SUBSREGR
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
CPCAPUSD
Available Call Processing Capacity Used (%)
For CM switches:
= (BRSTAT:BRSCAP / 77) * 100
For XACORE switches:
= (XASTAT:XASUTIL/77) * 100
DSINUSE
Data Store Used (KBytes)
= STORE:DSUSEDK + (STORE:DSUSEDM * 1024)
IERMSCHR
Incoming Inter-MSC Handover Success Rate
HO2GTO2G:S2GIEMHO/HO2GTO2G:A2GIEMHO*100
PSINUSE
Program Store Used (KBytes)
= STORE:PSUSEDK + (STORE:PSUSEDM * 1024)
MMSUCCR
Mobile to Mobile Call Success Rate (%)
= (MSCCP:MMSUCC / MSCCP:MMBID) * 100
MLSUCCR
Mobile to Land Call Success Rate (%)
= (MSCCP:MLSUCC / MSCCP:MLBID) * 100
LMSUCCR
Land to Mobile Call Success Rate (%)
= (MSCCP:LMSUCC / MSCCP:LMBID) * 100
LLSUCCR
Land to Land Call Success Rate (%)
= (MSCCP:LLSUCC / MSCCP:LLBID) * 100
TOTSUCCR
Total Call Success Rate (%)
= ((MSCCP:MMSUCC + MSCCP:MLSUCC +
MSCCP:LMSUCC + MSCCP:LLSUCC) * 100) /
(MSCCP:MMBID + MSCCP:MLBID + MSCCP:LMBID +
MSCCP:LLBID)
GSM18/UMTS04
Table 2-8
Group
Name
Description
RAMSCHR
Intra-MSC Handover Success Rate
HO2GTO2G:S2GRAMAH/HO2GTO2G:A2GRAMAH*100
RAVLRLUR
Intra-MSC Location Update Success Rate (%)
= ((VLR:LURAVLR + VLR:LURAVLRR) * 100) /
(VLR:IAVLHAT + VLR:IAVLRAT)
SERMSCHR
Subsequent Inter-MSC Handover Success Rate
HO2GTO2G:S2GSBEMH/HO2GTO2G:A2GSBEMH*100
SHBMSCHR
Subsequent Handback Success Rate
HO2GTO2G:S2GSUBHB/HO2GTO2G:A2GSUBHB*100
FPGSUCCR
First Paging Success Rate (%)
= (sum VLR3:FPGSUCC) / (sum VLR3:FPGATT) * 100
AUTHSUCR
Authentication Success Rate (%)
= (VLR:AUTPSUC / VLR:AUTPATT) * 100
SMMOSUCR
Short Message Mobile-Originated Success Rate (%)
= (MSCSMS:SMMOSUC / MSCSMS:SMMOATT) * 100
SMMTSUCR
Short Message Mobile-Terminated Success Rate (%)
= (MSCSMS:SMMTSUC / MSCSMS:SMMTATT) * 100
VLRSUBS
Number of VLR Subscribers
VLR:SUBSREG+VLR:SUBSREGR
OERMSCHR
Outgoing Inter-MSC Handover Success Rate
= HO2GTO2G:S2GOEMHO / HO2GTO2G:A2GOEMHO *
100
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
TOTMSCHR
Total Call MSC Handover Success Rate
= (HO2GTO2G:S2GRAMAH + HO2GTO2G:S2GIEMHO +
HO2GTO2G:S2GOEMHO + HO2GTO2G:S2GSUBHB +
HO2GTO2G:S2GSBEMH) / (HO2GTO2G:A2GRAMAH +
HO2GTO2G:A2GIEMHO + HO2GTO2G:A2GOEMHO +
HO2GTO2G:A2GSUBHB + HO2GTO2G:A2GSBEMH) * 100
TRK
MOTSSURT
Mobile Originated Trunk Seizures Success Ratio (%)
= (INCATOT - INFAIL) / INCATOT *100
MTTSSURT
Mobile Terminated Trunk Seizures Success Ratio (%)
= (NATTMPT - OUTFAIL) / NATTMPT *100
VLR
TLUERVLR
Total Inter-VLR Location Updates
= (LUERVLR + LUERVLRR)
TLURAVLR
Total Intra-VLR Location Updates
= (LURAVLR + LURAVLRR)
TSUBSREG
Total no of Subscribers
= (SUBSREG + SUBSREGR)
TAIMSIAL
Total IMSI usage
= (TAIMSIIA + TAIMSILU)
TATMSIAL
Total TMSI usage on switch
= (TATMSIIA + TATMSILU)
TUIMSIAL
Total Unknown IMSI usage on switch
= ( TUIMSIIA + TUIMSILU)
TUTMSIAL
Total Unknown TMSI usage on switch
= (TUTMSIIA + TUTMSILU)
GSM18/UMTS04
Table 2-8
Group
Name
Description
TKIMSIIA
Total known IMSI usage on IMSI attach
= ( TAIMSIIA - TUIMSIIA)
TKIMSILU
Total known IMSI usage on location Update
= (TAIMSILU - TUIMSILU)
TKTMSIIA
Total known TMSI usage on IMSI attach
= (TATMSIIA - TUTMSIIA)
TKTMSILU
Total known TMSI usage on location Update
= (TATMSILU - TUTMSILU)
TKIMSIAL
Total known IMSI usage
= (TAIMSIIA - TUIMSIIA +TAIMSILU - TUIMSILU)
TKTMSIAL
Total known TMSI usage
= (TATMSIIA -TUTMSIIA + TATMSILU - TUTMSILU)
IAVLASAT
Total Intra-VLR location Update attempts
= (IAVLHAT + IAVLRAT)
IRVLASAT
Total Inter-VLR location Update attempts
= (IRVLHAT + IRVLRAT)
TACSVLR
Total active MSs in VLR
= (ACHSVLR + ACRSVLR)
TICSVLR
Total Inactive MSs in VLR
= (ICHSVLR + ICRSVLR)
FERVLRLH
Failed Inter-VLR location updates for Home Subscribers
= (IRVLHAT - LUERVLR)
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
FERVLRLR
Failed Inter-VLR location updates for Roaming Subscribers
= (IRVLRAT - LUERVLRR)
FRAVLRLH
Failed Intra-VLR location updates for Home Subscribers
= (IAVLHAT - LURAVLR)
FRAVLRLR
Failed Intra-VLR location updates for Roaming Subscribers
= (IAVLRAT - LURAVLRR)
FERVLRAS
Total failed Inter-VLR location updates
= (FERVLRLH + FERVLRLR)
FRAVLRAS
Total failed Intra-VLR location updates
= (FRAVLRLH + FRAVLRLR)
TOTFDR
Total forced de-registrations
= (FDRVLRA + FD1VLRH + FD2VLRH)
AUTPFAIL
Total authentification failures
= (AUTPATT - AUTPSUC)
FPGPSF
Total failed First Paging attempts
= (FPGPSAT - FPGPSSU)
PGRPSF
Total failed Paging retry attempts
= (PGRPSAT - PGRPSSU)
LUERVPSU
Location Updates Inter-VLR per 100 Subscribers
= (LUERVLR + LUERVLRR) / (SUBSREG + SUBSREGR)
*100
GSM18/UMTS04
Table 2-8
Group
Name
Description
SUPSUB
Supportable Subscribers
= (SUBSREG + SUBSREGR) * 77% /BRSTAT:BRSCAP
77% is the recommended maximum amount of CPU to be
used by Call Processing in a properly provisioned switch. See
“Base/Telecom Office Parameters Reference Manual” for
details.
LURAVPSU
Intra and Periodic Location Updates per 100 Subscribers
= (LURAVLR + LURAVLRR + PLUARAT) / (SUBSREG +
SUBSREGR) *100
LUERVLPF
Inter-VLR Location Updates Performance (%)
= (LURAVLR + LURAVLRR) / (IAVLHAT + IAVLRAT) *100
IAVLPSU
Intra-VLR Location Updates per 100 Subscribers
= (IAVLHAT + IAVLRAT) / (SUBSREG + SUBSREGR) *100
PLUPSU
Periodic Location Updates per 100 Subscribers
= PLUARAT / (SUBSREG + SUBSREGR) *100
IMSIAPF
International Mobile Subscriber Identity (IMSI) Attach
Performance (%)
= IMSIATT / TAIMSIIA *100
IMSIAPSU
IMSI Attach per 100 Subscribers
= TAIMSIIA / (SUBSREG + SUBSREGR) *100
IMSILUPF
Location Updates IMSI Performance (%)
= (TAIMSILU - TUIMSILU) / TAIMSILU *100
IMSILUSU
Location Updates with IMSI per 100 Subscribers
= TAIMSILU / (SUBSREG + SUBSREGR) *100
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
TMSILUPF
Location Updates with Temporary Mobile Subscriber Identity
(TMSI) per Performance (%)
= (TATMSILU - TUTMSILU) / TATMSILU *100
TMSILUSU
Location Updates with TMSI per 100 Subscribers
= TATMSILU / (SUBSREG + SUBSREGR) *100
GMULPF
Update Location to HLR Performance (%)
= GMAPMMGT:GMULRES / GMAPMMGT:GMULREQ
GMULPSU
Update Location to HLR per 100 Subscribers
= GMAPMMGT:GMULREQ / (SUBSREG + SUBSREGR)
*100
GMCLPF
Cancel Location to HLR Performance (%)
= GMAPMMGT:GMCLRES / GMAPMMGT:GMCLREQ
GMCLPSU
Cancel Location to HLR per 100 Subscribers
= GMAPMMGT:GMCLREQ / (SUBSREG + SUBSREGR)
*100
TOTLU
All Location Updates
= IAVLHAT + IRVLHAT + IRVLRAT + IAVLRAT
GMISDPF
Insert Subscriber Data Performance (%)
= GMAPSMGT:GMISDRES / GMAPSMGT:GMISDREQ *100
GMISDPC
Insert Subscriber Data per 100 Calls
= GMAPSMGT:GMISDREQ / (MSCCP:MMBID +
MSCCP:MLBID + MSCCP:LMBID) *100
GMDSDPF
Delete Subscriber Data Performance
= GMAPSMGT:GMDSDRES / GMAPSMGT:GMDSDREQ
GSM18/UMTS04
Table 2-8
Group
Name
Description
GMDSDPC
Delete Subscriber Data per 100 Calls
= GMAPSMGT:GMDSDREQ / (MSCCP:MMBID +
MSCCP:MLBID + MSCCP:LMBID)*100
PMSPF
Purge MS Performance (%)
= GMAPSMGT:PMSRES / GMAPSMGT:PMSREQ *100
PMSPC
Purge MS per 100 Calls
= GMAPSMGT:PMSREQ / (MSCCP:MMBID +
GMSPCPF
Send Parameter Call Data Performance (%)
= GMAPSMGT:GMSPCRES / GMAPSMGT:GMSPCREQ
*100
GMSPCPC
Send Parameter Call Data per 100 Calls
= GMAPSMGT:GMSPCREQ / (MSCCP:MMBID +
GMSPIPF
Send Parameter IMSI Inquiry Performance (%)
= GMAPSMGT:GMSPIRES / GMAPSMGT:GMSPIREQ *100
GMSPIPC
Send Parameter IMSI Inquiry per 100 Calls
= GMAPSMGT:GMSPIREQ / (MSCCP:MMBID +
SIDPF
Send ID Performance (%)
= GMAPSMGT:SIDRES / GMAPSMGT:SIDREQ *100
SIDPC
Send ID per 100 Calls
= GMAPSMGT:SIDREQ / (MSCCP:MMBID +
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
GMSPAPF
Send Parameter Authentication Performance (%)
= GMAPSMGT:GMSPARES / GMAPSMGT:GMSPAREQ
*100
GMSAPCPC
Send Parameter Authentication per 100 Calls
= GMAPSMGT:GMSPARES / (MSCCP:MMBID +
SAIPF
Send Authentication Info Performance (%)
= GMAPSMGT:SAIRES /GMAPSMGT:SAIREQ *100
SAIPC
Send Authentication Info per 100 Calls
= GMAPSMGT:SAIREQ / (MSCCP:MMBID +
AUTPSUPF
Authentications Performance (%)
=VLR:AUTPSUC / VLR:AUTPATT *100
AUTPPC
Authentications per 100 Calls
=VLR: AUTPATT / (MSCCP:MMBID + MSCCP:MLBID +
MSCCP:LMBID) *100
VLR3
FPGSUCPF
First Paging Performance (%)
= FPGSUCC / FPGATT *100
FPATTDM
First Paging Distribution Mix
= FPGATT / sum of all FPGATT *100
PGRSUCPF
Paging Retries Performance (%)
= PGRSUCC / PGRATT *100
PGRATTDM
Paging Retries Distribution Mix
= PGRATT / sum of all PGRATT *100
GSM18/UMTS04
Table 2-8
Group
Name
Description
FPGFAIL
Total failed First paging attempts per LAC
= (FPGPSAT - FPGPSSU)
PGRFAIL
Total failed Paging retry attempts per LAC
= (PGRPSAT - PGRPSSU)
attPageReqsPerL
ocationArea
Sum of first paging attempts and the no: of paging retries
issued at the MSC
FPGATT + PGRATT
succPageReqsPe
rLocationArea
This register gives the number of paging retries and the first
paging attempts per LAC successfully completed at the MSC
FPGSUCC + PGRSUCC
VLRMMU
attPageReqsPerL
ocationAreaMU
Attempted page Requests per Location Area per MMU
VLRMMU:FPGATTMU+VLRMMU:PGRATTMU
FPATTDMMU
First Paging Distribution Mix per MMU
VLRMMU:FPGATTMU/VLRMMU:FPGATTMU*100
FPGFAILMU
First Paging Failures per LAC per MMU
VLRMMU:FPGATTMU-VLRMMU:FPGSUCMU
FPGSUCPFMU
First Paging Performance per MMU
VLRMMU:FPGSUCMU/VLRMMU:FPGATTMU*100
PGRATTDMMU
Paging Retries Distribution Mix
VLRMMU:PGRATTMU/VLRMMU_SUN:PGRATTMU*100
PGRFAILMU
Paging Retry Failures per LAC per MMU
VLRMMU:PGRATTMU-VLRMMU:PGRSUCMU
PGRSUCPFMU
Paging Retries Performance per MMU
VLRMMU:PGRSUCMU/VLRMMU:PGRATTMU*100
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
succPageReqsPe
rLocationAreaMU
Successful Page Requests per Location Area per MMU
VLRMMU:FPGSUCMU+VLRMMU:PGRSUCMU
TLUEVLRU
This register keeps the count of the no:of location updates for
Inter-VLR home/roaming subscribers per MMU
LUEVLRMU + LERVLRMU
TLURVLRU
This register keeps the count of the no:of location updates for
Intra-VLR home/roaming subscribers per MMU
LURVLRMU + LUAVLRMU
TSUBREGU
Count of the no:of home/roaming Subscribers registered per
MMU
SUBREGMU + SUBSRGMU
TAMSIALU
Count of the total of IMSI usage during IMSI attach and/or
location update per MMU
TAISIAMU + TAISILMU
TATSIALU
Count of the total of TMSI usage during IMSI attach and/or
location update per MMU
TATSIAMU + TATSILMU
TUMSIALU
Count of the no:of unknown IMSI usage on IMSI attach and/
or location update per MMU
TUISIAMU + TUISILMU
TUTSIALU
Count of the total of unknown TMSI usage on IMSI attach
and/or location update per MMU
TUTSIAMU + TUTSILMU
TKIMSIAU
Count of the IMSI usage on IMSI attach per MMU without
considering the unknown IMSI usage
TAISIAMU - TUISAIMU
GSM18/UMTS04
Table 2-8
Group
Name
Description
TKMSILMU
Count of known and unknown IMSI usage on location update
per MMU
TAISIAMU + TUISILMU
TKTMSIAU
Count of the TMSI usage on IMSI attach per MMU without
considering the unknown TMSI usage
TATSIAMU - TUTSIAMU
TKMSTLMU
Count of the TMSI usage on Location Update attach per
MMU without considering the unknown TMSI usage
TATSILMU - TUTSILMU
TKIMSIALMU
Count of known IMSI usage during IMSI Attach and all IMSI
usage during Location update
( TAISIAMU - TUISIAMU) + (TAISILMU + TUISILMU)
TKTMSIALMU
Count of known TMSI usage during IMSI attach and Location
Update per MMU (unknown TMSI is not considered in both
cases)
( TATSIAMU -TUTSIAMU)+( TATSILMU-TUTSILMU)
IAVLASATMU
Count of total no:of Intra-VLR Location Update attempts from
home/roaming MS per MMU
IALHATMU + IALRATMU
IRVLASATMU
Total no:of Inter-VLR Location Update attempts from
roaming/home MS per MMU
IRLHATMU + IRLRATMU
TACSVLRMU
Number of active home and roaming (attached) MSes in the
VLR per MMU
AHSVLRMU + ARSVLRMU
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
TICSVLRMU
Number of home and roaming inactive (detached) subs in the
VLR per MMU
IHSVLRMU + IRSVLRMU
FERVLRLHMU
Total number of unsuccessful Inter-VLR Location Update
attempts from home MS per MMU
IRLHATMU - LUEVLRMU
FERVLRLRMU
Total number of unsuccessful Inter-VLR Location Update
attempts from roaming MS per MMU
IRLRATMU - LERVLRMU
FRAVLRLHMU
Total number of unsuccessful Intra-VLR Location Update
attempts from home MS per MMU
IALHATMU - LURVLRMU
FRAVLRLRMU
attempts from roaming MS per MMU
IALRATMU - LUAVLRMU
FERVLRASMU
Total number of unsuccessful Inter-VLR and Intra-VLR
Location Update attempts from home and roaming MS per
MMU
(IRLHATMU- LUEVLRMU)+(IRLRATMU- LERVLRMU)
FRAVLRASMU
attempts from home and roaming MS per MMU
(IALHATMU- LURVLRMU)+(IALRATMU-LUAVLRMU)
TOTFDRMU
Total no:of forced Subscriber De-registration from the VLR
via audit , HLR (Phase 1) and HLR (Phase 2) per MMU
FRVLRAMU + F1VLRHMU + F2VLRHMU
GSM18/UMTS04
Table 2-8
Group
Name
Description
AUTPFAILMU
Count of current no:of unsuccessful authentication requests
which are sent to the MSC
AUTPATMU - AUTPUCMU
FPGPSFMU
Counts the number of first paging attempts per switch which
were not successfully completed at the MSC.
FGPSATMU - FGPSSUMU
PGRPSFMU
Counts the number of paging retries per switch which were
not successfully completed at the MSC
PRPSATMU - PRPSSUMU
LUERVPSUMU
Rate at which location update is done at any time by the
subscribers under any particular VLR database(%)
((LUEVLRMU+LERVLRMU)/(SUBREGMU+SUBSRGMU)) *
100
LURAVPSUMU
Rate of location updates per total users (%)
(((LURVLRMU + LUAVLRMU)+PLURATMU )/
(SUBREGMU+ SUBSRGMU))*100
LUERVLPFMU
Rate of location upd from intra-vlr (home & roaming) (%)
((LURVLRMU + LUAVLRMU)/
(IALHATMU+IALRATMU))*100
IAVLPSUMU
Rate at which Intra-VLR location update attempts are done at
any time by the home/roaming subscribers under any
particular VLR database
((IALHATMU + IALRATMU) /(SUBREGMU+SUBSRGMU) )*
100
PLUPSUMU
Periodic LU attempts rate by the subscribers under any VLR
(%)
( PLURATMU / ( SUBREGMU + SUBSRGMU ) ) * 100.0
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
IMSIAPFMU
Rate at which IMSI attach is done per MMU (%)
(IMSATTMU/TAISIAMU )*100.0
IMSIAPSUMU
Rate of IMSI usage during IMSI attach by all subscribers
(home and roaming) under any VLR database(%)
(TAISIAMU / ( SUBREGMU+ SUBSRGMU))* 100
IMSILUPFMU
Total of all (known and unknown) IMSI usage during location
update / total of all IMSI usage during location updates (%)
((TAISILMU + TUISILMU )/TAISILMU )*100
IMSILUSUMU
Rate of all IMSI usage during location update by all
subscribers (home and roaming) under any VLR database
(%)
(TAISILMU / (SUBREGMU + SUBSRGMU)) * 100
TMSILUPFMU
Rate of known TMSI usage during location update (%)
((TATSILMU - TUTSILMU) / TATSILMU)*100
TMSILUSUMU
Rate of TMSI usage during location update by the total home
and roaming subscribers under any particular VLR database
(%)
( TATSILMU / (SUBREGMU+ SUBSRGMU) ) * 100
GMULPFMU
Rate of successful responses to Update Location requests
from an application within the Visitor Location Register (VLR)
(%)
(GMULREMU / GMULRQMU ) * 100
GMULPSUMU
Rate at which GSM MAP Update Location requests are done
by the home/roaming subscribers registered per MMU (%)
(GMULRQMU) / (SUBREGMU + SUBSRGMU) * 100
GSM18/UMTS04
Table 2-8
Group
Name
Description
GMCLPFMU
Gives a performance measure of the Cancel Location
operation can be determined (%)
(GMCLREMU/GMCLRQMU ) * 100
GMCLPSUMU
Measure of the no:of cancel location requests by total users
(home and roaming) under any VLR (%)
(GMCLRQMU /(SUBREGMU + SUBSRGMU ) ) * 100
TOTLUMU
Total no:of Intra-VLR and Inter-VLR location update attempts
from the home and roaming MS per MMU
(IALHATMU + IALRATMU) + ( IRLHATMU+IRLRATMU )
GMISDPFMU
Gives a performance measure of the Insert Subscriber Data
operation (%)
( GMISREMU / GMISRQMU ) * 100
GMDSDPFMU
Gives a performance measure of the Delete Subscriber Data
operation (%)
( GMDSREMU/ GMDSRQMU)*100
PMSPFMU
This register holds the number of PMS requests sent by the
VLR to the HLR (%)
(PMSRESMU/ PMSREQMU) * 100
GMSPCPFMU
Gives a performance measure of the Send Parameters (Call
Data) operation (%)
(GMSCREMU/ GMSCRQMU)*100
GMSPIPFMU
Gives a a performance measure of the Send Parameters
(IMSI Inquiry) operation (%)
(GMSIREMU / GMSIRQMU) * 100
SIDPFMU
Gives a performance measure of the Send Identification
operation (%)
(SIDRESMU / SIDREQMU) * 100
411-8111-803
Standard
01.06
May 2006
Table 2-8
Group
Name
Description
GMSPAPFMU
Gives a performance measure of the Send Parameters
(Authentication) operation (%)
(GMSAREMU/ GMSARQMU)*100
SAIPFMU
Gives a performance measure of the Send Authentication
Info operation (%)
( SAIRESMU / SAIREQMU) * 100
AUTPSUPFMU
Rate of current number of successful authentication requests
which are sent to the MSC over the total (current) no:of
authentication requests made (%)
(AUTPUCMU / AUTPATMU ) * 100
Note: Information about other HLRSUMPAGE registers not specified in
the Table 2-8 can be located in NTP 411-2831-814, GSM / UMTS
HLR100/200 Operational Measurements Reference Manual:
— Information about registers: PUSSRIN, PUSSRRQ, USSRIN,
USSRRQ, USSNIN, USSNRQ, USSDRA, and USSDTB is available
under OM group HLRUSSDT.
— Information about registers: ATMRQ and DTMRQ is available under
OM group HSTRACET.
— Information about registers: RRQUEST and PRQUEST is available
under OM group GHSBYACT.
— Information about registers: NETWORK, ADMIN, INTERNAL,
DISCARD, and LINKDIS is available under OM group HLRWORK.
— Information about register TRERROR is available under OM group
GHLRFREC.
— Information about registers: PSIRSRI and PSIRATI is available under
OM group HCMLMRT.
GSM18/UMTS04
The HLR Summary Report (see the Performance Management chapter of
NTP 411-8111-503) collects a set of HLR registers and gives a view of the
performance of the HLR switch.
Table 2-9
Correlated OMs related to G-SGSN
Group
Name
Formula
GprsMobilityManagement
PC03_2G_SGSN_Attach_Success_Rate
100 * MM.SuccGprsAttach / (MM.SuccGprsAttach +
VS.attachRejPacketNetworkFailure +
VS.attachRejSgsnCongestion )
PC04_2G_SGSN_Attach_Success_Rate_Network
100 * GprsMobilityManagement:VS.attachReqAccepted /
(GprsMobilityManagement:VS.attachReqAccepted +
GprsMobilityManagement:VS.attachRejSgsnCongestion +
GprsMobilityManagement:VS.attachRejPacketNetworkFailure +
GprsMobilityManagement:VS.attachRejMsgError)
PC04_2G_SGSN_Attach_Success_Rate_Nodal
GprsMobilityManagement:VS.attachRejNwkSgsnInternalError +
GprsMobilityManagement:VS.attachRejCngMapCResourceExhau
st + GprsMobilityManagement:VS.attachRejCngPtmsiCollision +
GprsMobilityManagement:VS.attachRejCngHlrcResourceExhaust
+ GprsMobilityManagement:VS.attachRejCngProcContextExhaust
+
GprsMobilityManagement:VS.attachRejCngLlcResourceExhaust)
PC04_2G_SGSN_Peak_Concurrent_Attached_Subscribers
GprsMobilityManagement:VS.peakAttachedSubscribers
PC04_2G_SGSN_Total_IRAU_Success_Rate_Network
100 * GprsMobilityManagement:MM.SuccInterSgsnRaUpdate /
(GprsMobilityManagement:MM.SuccInterSgsnRaUpdate +
GprsMobilityManagement:VS.irauRejMsgError +
GprsMobilityManagement:VS.irauRejPacketNetworkFailure +
GprsMobilityManagement:VS.irauRejSgsnCongestion +
GprsMobilityManagement:VS.irauRejIdNotDerivedPtmsiCollision)
—sheet 1 of 14—
411-8111-803
Standard
01.06
May 2006
Table 2-9
Group
Name
Formula
percentAttachRejected
GprsMobilityManagement::percentAttachRejected = 100 - (100 *
GprsMobilityManagement::attachesSuccessful /
(GprsMobilityManagement::attachesSuccessful +
GprsMobilityManagement::attachRejPacketNetworkFailure +
GprsMobilityManagement::attachRejSgsnCongestion))
GprsMobilityManagement_SUM
percentAttachRejected
100 - 100 *
GprsMobilityManagement_SUM:VS.attachReqAccepted /
(GprsMobilityManagement_SUM:VS.attachReqAccepted +
GprsMobilityManagement_SUM:VS.attachRejPacketNetworkFailur
e+
GprsMobilityManagement_SUM:VS.attachRejSgsnCongestion)
100 * GprsMobilityManagement_SUM:VS.attachReqAccepted /
e+
GprsMobilityManagement_SUM:VS.attachRejSgsnCongestion)
GprsMobilityManagement_SUM:VS.attachRejSgsnCongestion +
e + GprsMobilityManagement_SUM:VS.attachRejMsgError)
—sheet 2 of 14—
GSM18/UMTS04
Table 2-9
Group
Name
Formula
GprsMobilityManagement_SUM:VS.attachRejNwkSgsnInternalErr
or +
GprsMobilityManagement_SUM:VS.attachRejCngMapCResource
Exhaust +
GprsMobilityManagement_SUM:VS.attachRejCngPtmsiCollision +
GprsMobilityManagement_SUM:VS.attachRejCngHlrcResourceEx
haust +
GprsMobilityManagement_SUM:VS.attachRejCngProcContextExh
aust +
GprsMobilityManagement_SUM:VS.attachRejCngLlcResourceExh
aust)
GprsMobilityManagement_SUM:VS.peakAttachedSubscribers
100 *
GprsMobilityManagement_SUM:MM.SuccInterSgsnRaUpdate /
(GprsMobilityManagement_SUM:MM.SuccInterSgsnRaUpdate +
GprsMobilityManagement_SUM:VS.irauRejMsgError +
GprsMobilityManagement_SUM:VS.irauRejPacketNetworkFailure
+ GprsMobilityManagement_SUM:VS.irauRejSgsnCongestion +
GprsMobilityManagement_SUM:VS.irauRejIdNotDerivedPtmsiColli
sion)
—sheet 3 of 14—
411-8111-803
Standard
01.06
May 2006
Table 2-9
Group
Name
Formula
SessionManagement
PC03_2G_SGSN_Activation_Success_Rate
100 * (SM.SuccActPdpContext + VS.missingOrUnknownApn +
VS.reqServiceOptionNotSubscribed ) / (SM.SuccActPdpContext +
VS.missingOrUnknownApn + VS.reqServiceOptionNotSubscribed
+ VS.insufficientResources + VS.unknownPdpAddrOrPdpType +
VS.userAuthenticationsFailed + VS.activationRejectedByGgsn +
VS.activationRejectedUnspecified +
VS.serviceOptionTempOutOfOrder + VS.nsapiAlreadyUsed +
VS.semanticallyIncorrectMesage +
VS.invalidMandatoryInfoElement +
VS.msgTypeNotCompWithProtState +
VS.protocolErrorUnspecified )
100 * ( SM.SuccActPdpContext + VS.missingOrUnknownApn +
VS.reqServiceOptionNotSubscribed ) / ( SessionManagement,
SM.SuccActPdpContext + VS.missingOrUnknownApn +
VS.reqServiceOptionNotSubscribed + VS.insufficientResources
+VS.unknownPdpAddrOrPdpType + VS.userAuthenticationsFailed
+VS.activationRejectedByGgsn
+VS.activationRejectedUnspecified +
VS.serviceOptionTempOutOfOrder +
VS.semanticallyIncorrectMesage +
VS.invalidMandatoryInfoElement +
VS.msgTypeNotCompWithProtState +
VS.protocolErrorUnspecified)
PC03_2G_SGSN_Reliability
100 * ( 1 - (SM.AttDeactPdpContextSgsn / (
SM.AttDeactPdpContextSgsn + SM.AttDeactPdpContextMs +
SM.AttDeactPdpContextGgsn + VS.hlrInitDeacts ) )
—sheet 4 of 14—
GSM18/UMTS04
Table 2-9
Group
Name
Formula
percentPDPActivationRejected
SessionManagement::percentPDPActivationRejected = 100 - (100
* (SessionManagement::mobileInitActivations +
SessionManagement::missingOrUnknownApn) /
(SessionManagement::mobileInitActivations+
SessionManagement::missingOrUnknownApn +
SessionManagement::insufficientResources +
SessionManagement::unknownPdpAddrOrPdpType +
SessionManagement::userAuthenticationsFailed +
SessionManagement::activationRejectedByGgsn +
SessionManagement::activationRejectedUnspecified +
SessionManagement::reqServiceOptionNotSubscribed +
SessionManagement::serviceOptionTempOutOfOrder +
SessionManagement::semanticallyIncorrectMesage +
SessionManagement::invalidMandatoryInfoElement +
SessionManagement::msgTypeNotCompWithProtState +
SessionManagement::protocolErrorUnspecified))
PC04_2G_SGSN_Activation_Success_Rate_Nodal
100 * (SessionManagement:SM.SuccActPdpContextDyn +
SessionManagement:VS.msPrimPppPdpCActSuccess +
SessionManagement:VS.msPrimStaticPdpCActSuccess +
SessionManagement:SM.SuccActSecondPdpContext) /
((SessionManagement:SM.AttActPdpContextDyn +
SessionManagement:VS.msPrimPppPdpCActAttempts +
SessionManagement:VS.msPrimStaticPdpCActAttempts +
SessionManagement:SM.AttActSecondPdpContext) (SessionManagement:VS.msPrimActRejectedByGgsn +
SessionManagement:VS.msSecActRejectedByGgsn +
SessionManagement:VS.msPrimActGeInsufficientRes +
SessionManagement:VS.msSecActGeInsufficientRes +
SessionManagement:VS.msPrimActTunnelSetupFail +
SessionManagement:VS.msPrimActGgsnRestart +
SessionManagement:VS.msSecActGgsnRestart +
SessionManagement:VS.msPrimActDuplicateActivation +
SessionManagement:VS.msSecActDuplicateActivation +
SessionManagement:VS.msPrimActDetachReqActReject +
SessionManagement:VS.msSecActDetachReqActReject +
SessionManagement:VS.msPrimActInfoElemNonExistNotImpl +
SessionManagement:VS.msPrimActConditionalIeError))
—sheet 5 of 14—
411-8111-803
Standard
01.06
May 2006
Table 2-9
Group
Name
Formula
PC04_2G_SGSN_IRAU_Success_Rate_Active_PDP_Network
100 * (1 - (SessionManagement:VS.newSgsnIrauActivationFailures
+ SessionManagement:VS.newSgsnUpdPdpCtxtRspFailure SessionManagement:VS.newSgsnUpdPdpCFailSvcNotSupported
+ SessionManagement:VS.oldSgsnDeactDatapathFail +
SessionManagement:VS.oldSgsnDeactSendGeFail +
SessionManagement:VS.oldSgsnDeactGeDefaultHandling +
SessionManagement:VS.oldSgsnDeactNetworkFailure) /
(SessionManagement:VS.oldSgsnPdpCIrauTransferAttempts +
SessionManagement:VS.newSgsnPdpCtxtsIrauSuccess +
SessionManagement:VS.newSgsnIrauActivationFailures))
PC04_2G_SGSN_IRAU_Success_Rate_Active_PDP_Nodal
- SessionManagement:VS.newSgsnDelPdpCtxtRequest SessionManagement:VS.newSgsnCamelChangeOfPosFailure SessionManagement:VS.newSgsnGeGprsReleaseRequest SessionManagement:VS.newSgsnInvalidPdpCtxtsDropped SessionManagement:VS.newSgsnGgsnRestartRestoration SessionManagement:VS.newSgsnGeDefaultHandling +
SessionManagement:VS.newSgsnUpdPdpCFailNonExistant +
SessionManagement:VS.newSgsnUpdPdpCFailSystemFailure +
SessionManagement:VS.oldSgsnDeactDatapathFail +
SessionManagement:VS.oldSgsnDeactSendGeFail) /
—sheet 6 of 14—
GSM18/UMTS04
Table 2-9
Group
Name
Formula
PC04_2G_SGSN_PDP_Activation_Success_Rate_Network
SessionManagement:SM.AttActSecondPdpContext) (SessionManagement:VS.msPrimActDetachReqActReject +
SessionManagement:VS.msPrimActMissingOrUnknownApn +
SessionManagement:VS.msPrimActReqSvcOpNotSubscribed +
SessionManagement:VS.msSecActReqSvcOpNotSubscribed +
SessionManagement:VS.msPrimActUserAuthenticationFail +
SessionManagement:VS.msSecActUserAuthenticationFail +
SessionManagement:VS.msPrimActInvalidTiValue +
SessionManagement:VS.msSecActInvalidTiValue +
SessionManagement:VS.msPrimActSemIncorrectMsg +
SessionManagement:VS.msPrimActConditionalIeError +
SessionManagement:VS.msSecActConditionalIeError +
SessionManagement:VS.msSecActDuplicateActivation))
PC04_2G_SGSN_PS_Retainability_Network
100 * (1 - (SessionManagement:VS.sgsnDeactNoMsgSentToMs +
SessionManagement:VS.sgsnDeactNetworkFailure +
SessionManagement:VS.sgsnDeactReactivationRequested) /
(SessionManagement:VS.mobileInitDeacts SessionManagement:VS.msDeactFailures +
SessionManagement:VS.ggsnInitDeacts +
SessionManagement:VS.hlrInitDeactsExecuted +
SessionManagement:VS.sgsnDeactRegularPdpCtxtDeact +
SessionManagement:VS.sgsnDeactNoMsgSentToMs +
SessionManagement:VS.sgsnDeactReactivationRequested))
PC04_2G_SGSN_Peak_Active_Subscribers
SessionManagement:VS.peakActiveSubscribers
—sheet 7 of 14—
411-8111-803
Standard
01.06
May 2006
Table 2-9
Group
Name
Formula
PC04_2G_SGSN_Peak_Concurrent_Sessions
SessionManagement:VS.peakPdpContexts
PC04_2G_SGSN_Retainability_Nodal
SessionManagement:VS.sgsnDeactReactivationRequested SessionManagement:VS.sgsnDeactDetachReattach SessionManagement:VS.sgsnDeactImplicitDetach SessionManagement:VS.sgsnDeactReactReqGgsnRestart) /
((SessionManagement:VS.sgsnDeactNoMsgSentToMs +
SessionManagement:VS.sgsnDeactReactivationRequested SessionManagement:VS.sgsnDeactDetachReattach SessionManagement:VS.sgsnDeactImplicitDetach SessionManagement:VS.sgsnDeactReactReqGgsnRestart) +
(SessionManagement:VS.mobileInitDeacts SessionManagement:VS.msDeactFailures +
SessionManagement:VS.sgsnDeactDetachReattach +
SessionManagement:VS.sgsnDeactDupActRequest +
SessionManagement:VS.sgsnDeactReactReqGgsnRestart +
SessionManagement:VS.sgsnDeactImplicitDetach)))
—sheet 8 of 14—
GSM18/UMTS04
Table 2-9
Group
Name
Formula
SessionManagement_SUM
percentPDPActivationRejected
100 - 100 * (SessionManagement_SUM:VS.mobileInitActivations +
SessionManagement_SUM:VS.missingOrUnknownApn) /
(SessionManagement_SUM:VS.mobileInitActivations +
SessionManagement_SUM:VS.missingOrUnknownApn +
SessionManagement_SUM:VS.insufficientResources +
SessionManagement_SUM:VS.unknownPdpAddrOrPdpType +
SessionManagement_SUM:VS.userAuthenticationsFailed +
SessionManagement_SUM:VS.activationRejectedByGgsn +
SessionManagement_SUM:VS.activationRejectedUnspecified +
SessionManagement_SUM:VS.reqServiceOptionNotSubscribed +
SessionManagement_SUM:VS.serviceOptionTempOutOfOrder +
SessionManagement_SUM:VS.semanticallyIncorrectMesage +
SessionManagement_SUM:VS.invalidMandatoryInfoElement +
SessionManagement_SUM:VS.msgTypeNotCompWithProtState +
SessionManagement_SUM:VS.protocolErrorUnspecified)
100 * (SessionManagement_SUM:VS.mobileInitActivations +
SessionManagement_SUM:VS.reqServiceOptionNotSubscribed) /
(SessionManagement_SUM:VS.mobileInitActivations +
SessionManagement_SUM:VS.reqServiceOptionNotSubscribed +
SessionManagement_SUM:VS.insufficientResources +
SessionManagement_SUM:VS.unknownPdpAddrOrPdpType +
SessionManagement_SUM:VS.userAuthenticationsFailed +
SessionManagement_SUM:VS.activationRejectedByGgsn +
SessionManagement_SUM:VS.activationRejectedUnspecified +
SessionManagement_SUM:VS.serviceOptionTempOutOfOrder +
SessionManagement_SUM:VS.nsapiAlreadyUsed +
SessionManagement_SUM:VS.semanticallyIncorrectMesage +
SessionManagement_SUM:VS.invalidMandatoryInfoElement +
SessionManagement_SUM:VS.msgTypeNotCompWithProtState +
SessionManagement_SUM:VS.protocolErrorUnspecified)
—sheet 9 of 14—
411-8111-803
Standard
01.06
May 2006
Table 2-9
Group
Name
Formula
PC03_2G_SGSN_Retainability
100 * (1 - SessionManagement_SUM:VS.sgsnInitDeacts /
(SessionManagement_SUM:VS.sgsnInitDeacts +
SessionManagement_SUM:VS.mobileInitDeacts +
SessionManagement_SUM:VS.ggsnInitDeacts +
SessionManagement_SUM:VS.hlrInitDeacts))
100 * (SessionManagement_SUM:SM.SuccActPdpContextDyn +
SessionManagement_SUM:VS.msPrimPppPdpCActSuccess +
SessionManagement_SUM:VS.msPrimStaticPdpCActSuccess +
SessionManagement_SUM:SM.SuccActSecondPdpContext) /
((SessionManagement_SUM:SM.AttActPdpContextDyn +
SessionManagement_SUM:VS.msPrimPppPdpCActAttempts +
SessionManagement_SUM:VS.msPrimStaticPdpCActAttempts +
SessionManagement_SUM:SM.AttActSecondPdpContext) (SessionManagement_SUM:VS.msPrimActRejectedByGgsn +
SessionManagement_SUM:VS.msSecActRejectedByGgsn +
SessionManagement_SUM:VS.msPrimActGeInsufficientRes +
SessionManagement_SUM:VS.msSecActGeInsufficientRes +
SessionManagement_SUM:VS.msPrimActTunnelSetupFail +
SessionManagement_SUM:VS.msPrimActGgsnRestart +
SessionManagement_SUM:VS.msSecActGgsnRestart +
SessionManagement_SUM:VS.msPrimActDuplicateActivation +
SessionManagement_SUM:VS.msSecActDuplicateActivation +
SessionManagement_SUM:VS.msPrimActDetachReqActReject +
SessionManagement_SUM:VS.msSecActDetachReqActReject +
SessionManagement_SUM:VS.msPrimActInfoElemNonExistNotIm
pl + SessionManagement_SUM:VS.msPrimActConditionalIeError))
GSM18/UMTS04
Table 2-9
Group
Name
Formula
100 * (1 (SessionManagement_SUM:VS.newSgsnIrauActivationFailures +
SessionManagement_SUM:VS.newSgsnUpdPdpCtxtRspFailure SessionManagement_SUM:VS.newSgsnUpdPdpCFailSvcNotSup
ported +
SessionManagement_SUM:VS.oldSgsnDeactDatapathFail +
SessionManagement_SUM:VS.oldSgsnDeactSendGeFail +
SessionManagement_SUM:VS.oldSgsnDeactGeDefaultHandling +
SessionManagement_SUM:VS.oldSgsnDeactNetworkFailure) /
(SessionManagement_SUM:VS.oldSgsnPdpCIrauTransferAttempt
s + SessionManagement_SUM:VS.newSgsnPdpCtxtsIrauSuccess
+ SessionManagement_SUM:VS.newSgsnIrauActivationFailures))
100 * (1 (SessionManagement_SUM:VS.newSgsnIrauActivationFailures SessionManagement_SUM:VS.newSgsnDelPdpCtxtRequest SessionManagement_SUM:VS.newSgsnCamelChangeOfPosFailu
re SessionManagement_SUM:VS.newSgsnGeGprsReleaseRequest
- SessionManagement_SUM:VS.newSgsnInvalidPdpCtxtsDropped
- SessionManagement_SUM:VS.newSgsnGgsnRestartRestoration
- SessionManagement_SUM:VS.newSgsnGeDefaultHandling +
SessionManagement_SUM:VS.newSgsnUpdPdpCFailNonExistant
+
SessionManagement_SUM:VS.newSgsnUpdPdpCFailSystemFailu
re + SessionManagement_SUM:VS.oldSgsnDeactDatapathFail +
SessionManagement_SUM:VS.oldSgsnDeactSendGeFail) /
411-8111-803
Standard
01.06
May 2006
Table 2-9
Group
Name
Formula
SessionManagement_SUM:SM.AttActSecondPdpContext) (SessionManagement_SUM:VS.msPrimActDetachReqActReject +
SessionManagement_SUM:VS.msPrimActMissingOrUnknownApn
+
SessionManagement_SUM:VS.msPrimActReqSvcOpNotSubscrib
ed +
SessionManagement_SUM:VS.msSecActReqSvcOpNotSubscribe
d+
SessionManagement_SUM:VS.msPrimActUserAuthenticationFail
+ SessionManagement_SUM:VS.msSecActUserAuthenticationFail
+ SessionManagement_SUM:VS.msPrimActInvalidTiValue +
SessionManagement_SUM:VS.msSecActInvalidTiValue +
SessionManagement_SUM:VS.msPrimActSemIncorrectMsg +
pl + SessionManagement_SUM:VS.msPrimActConditionalIeError
+ SessionManagement_SUM:VS.msSecActConditionalIeError +
SessionManagement_SUM:VS.msSecActDuplicateActivation))
GSM18/UMTS04
Table 2-9
Group
Name
Formula
100 * (1 (SessionManagement_SUM:VS.sgsnDeactNoMsgSentToMs +
SessionManagement_SUM:VS.sgsnDeactNetworkFailure +
SessionManagement_SUM:VS.sgsnDeactReactivationRequested)
/
(SessionManagement_SUM:VS.mobileInitDeacts SessionManagement_SUM:VS.msDeactFailures +
SessionManagement_SUM:VS.hlrInitDeactsExecuted +
SessionManagement_SUM:VS.sgsnDeactRegularPdpCtxtDeact +
SessionManagement_SUM:VS.sgsnDeactNoMsgSentToMs +
)
SessionManagement_SUM:VS.peakActiveSubscribers
SessionManagement_SUM:VS.peakPdpContexts
411-8111-803
Standard
01.06
May 2006
Table 2-9
Group
Name
Formula
SessionManagement_SUM:VS.sgsnDeactReactivationRequested
- SessionManagement_SUM:VS.sgsnDeactDetachReattach SessionManagement_SUM:VS.sgsnDeactImplicitDetach SessionManagement_SUM:VS.sgsnDeactReactReqGgsnRestart)
/
((SessionManagement_SUM:VS.sgsnDeactNoMsgSentToMs +
- SessionManagement_SUM:VS.sgsnDeactDetachReattach SessionManagement_SUM:VS.sgsnDeactImplicitDetach SessionManagement_SUM:VS.sgsnDeactReactReqGgsnRestart)
+
(SessionManagement_SUM:VS.mobileInitDeacts SessionManagement_SUM:VS.msDeactFailures +
SessionManagement_SUM:VS.sgsnDeactDetachReattach +
SessionManagement_SUM:VS.sgsnDeactDupActRequest +
SessionManagement_SUM:VS.sgsnDeactReactReqGgsnRestart
+ SessionManagement_SUM:VS.sgsnDeactImplicitDetach)))
Relay_SUM
PC04_2G_SGSN_Packet_Discard_Rate_Nodal
100 * (Relay_SUM:VS.discPdusFromNetwork:summation +
SubNetworkDataConvergenceProtocol_SUM:VS.discardedNpdus
FromMs:summation) /
(SubNetworkDataConvergenceProtocol_SUM:VS.snPdusFromMs:
summation + Relay_SUM:GTP.InDataPktGn:summation)
GSM18/UMTS04
Table 2-10
Correlated OMs related to U-SGSN
Group
Name
Formula
100 * MM.SuccGprsAttach / ( VS.attachesWithImsi +
VS.attachesWithKnownPtmsi + VS.attachesWithUnknownPtmsi )
GprsMobilityManagement:VS.attachRejSgsnCongestion +
GprsMobilityManagement:VS.attachRejPacketNetworkFailure +
GprsMobilityManagement:VS.attachRejMsgError)
GprsMobilityManagement:VS.attachRejNwkSgsnInternalError +
GprsMobilityManagement:VS.attachRejCngMapCResourceExhau
st + GprsMobilityManagement:VS.attachRejCngPtmsiCollision +
GprsMobilityManagement:VS.attachRejCngHlrcResourceExhaust
+
GprsMobilityManagement:VS.attachRejCngProcContextExhaust)
GprsMobilityManagement:VS.peakAttachedSubscribers
100 * GprsMobilityManagement:MM.SuccInterSgsnRaUpdate /
(GprsMobilityManagement:MM.SuccInterSgsnRaUpdate +
GprsMobilityManagement:VS.irauRejMsgError +
GprsMobilityManagement:VS.irauRejPacketNetworkFailure +
GprsMobilityManagement:VS.irauRejSgsnCongestion +
GprsMobilityManagement:VS.irauRejIdNotDerivedPtmsiCollision)
—sheet 1 of 11—
411-8111-803
Standard
01.06
May 2006
Table 2-10
Group
Name
Formula
GprsMobilityManagement_SUM
100 * GprsMobilityManagement_SUM:MM.SuccGprsAttach /
(GprsMobilityManagement_SUM:VS.attachesWithImsi +
GprsMobilityManagement_SUM:VS.attachesWithKnownPtmsi +
GprsMobilityManagement_SUM:VS.attachesWithUnknownPtmsi)
GprsMobilityManagement_SUM:VS.attachRejSgsnCongestion +
e + GprsMobilityManagement_SUM:VS.attachRejMsgError)
GprsMobilityManagement_SUM:VS.attachRejNwkSgsnInternalErr
or +
GprsMobilityManagement_SUM:VS.attachRejCngMapCResource
Exhaust +
GprsMobilityManagement_SUM:VS.attachRejCngPtmsiCollision +
GprsMobilityManagement_SUM:VS.attachRejCngHlrcResourceEx
haust +
GprsMobilityManagement_SUM:VS.attachRejCngProcContextExh
aust)
GprsMobilityManagement_SUM:VS.peakAttachedSubscribers
100 *
GprsMobilityManagement_SUM:MM.SuccInterSgsnRaUpdate /
(GprsMobilityManagement_SUM:MM.SuccInterSgsnRaUpdate +
GprsMobilityManagement_SUM:VS.irauRejMsgError +
GprsMobilityManagement_SUM:VS.irauRejPacketNetworkFailure
+ GprsMobilityManagement_SUM:VS.irauRejSgsnCongestion +
GprsMobilityManagement_SUM:VS.irauRejIdNotDerivedPtmsiColli
sion)
—sheet 2 of 11—
GSM18/UMTS04
Table 2-10
Group
Name
Formula
SessionManagement
100 * (SM.SuccActPdpContext +
VS.actFailMissingOrUnknownApn) /
(SM.SuccActPdpContext + VS.actFailMissingOrUnknownApn +
VS.actFailSgsnInsufficientResources +
VS.actFailGgsnInsufficientResources + VS.actFailRejectedByGgsn
+ VS.actFailUnknownPdpAddrOrPdpType +
VS.actFailUserAuthentications)
PC03_3G_SGSN_Reliability
100 * ( 1 - VS.usgsnInitDeacts / ( VS.usgsnInitDeacts +
SM.AttDeactPdpContextGgsn + VS.hlrInitDeacts +
SM.AttDeactPdpContextMs )
SessionManagement:SM.AttActSecondPdpContext) (SessionManagement:VS.msPrimActRejectedByGgsn +
SessionManagement:VS.msSecActRejectedByGgsn +
SessionManagement:VS.msPrimActGeInsufficientRes +
SessionManagement:VS.msSecActGeInsufficientRes +
SessionManagement:VS.msPrimActTunnelSetupFail +
SessionManagement:VS.msPrimActGgsnRestart +
SessionManagement:VS.msSecActGgsnRestart +
SessionManagement:VS.msSecActDuplicateActivation +
SessionManagement:VS.msPrimActDetachReqActReject +
SessionManagement:VS.msPrimActRadioLinkDown +
SessionManagement:VS.msSecActRadioLinkDown +
SessionManagement:VS.msPrimActConditionalIeError))
—sheet 3 of 11—
411-8111-803
Standard
01.06
May 2006
Table 2-10
Group
Name
Formula
+ SessionManagement:VS.newSgsnUpdPdpCtxtRspFailure SessionManagement:VS.newSgsnUpdPdpCFailSvcNotSupported
+ SessionManagement:VS.oldSgsnDeactDatapathFail +
SessionManagement:VS.oldSgsnDeactSendGeFail +
SessionManagement:VS.oldSgsnDeactGeDefaultHandling +
SessionManagement:VS.oldSgsnDeactNetworkFailure) /
- SessionManagement:VS.newSgsnDelPdpCtxtRequest SessionManagement:VS.newSgsnCamelChangeOfPosFailure SessionManagement:VS.newSgsnGeGprsReleaseRequest SessionManagement:VS.newSgsnInvalidPdpCtxtsDropped SessionManagement:VS.newSgsnGgsnRestartRestoration SessionManagement:VS.newSgsnGeDefaultHandling +
SessionManagement:VS.newSgsnUpdPdpCFailNonExistant +
SessionManagement:VS.newSgsnUpdPdpCFailSystemFailure +
SessionManagement:VS.oldSgsnDeactDatapathFail +
SessionManagement:VS.oldSgsnDeactSendGeFail) /
—sheet 4 of 11—
GSM18/UMTS04
Table 2-10
Group
Name
Formula
SessionManagement:SM.AttActSecondPdpContext) (SessionManagement:VS.msPrimActDetachReqActReject +
SessionManagement:VS.msPrimActMissingOrUnknownApn +
SessionManagement:VS.msPrimActReqSvcOpNotSubscribed +
SessionManagement:VS.msSecActReqSvcOpNotSubscribed +
SessionManagement:VS.msPrimActUserAuthenticationFail +
SessionManagement:VS.msSecActUserAuthenticationFail +
SessionManagement:VS.msPrimActInvalidTiValue +
SessionManagement:VS.msSecActInvalidTiValue +
SessionManagement:VS.msPrimActSemIncorrectMsg +
SessionManagement:VS.msPrimActConditionalIeError +
SessionManagement:VS.msSecActConditionalIeError +
SessionManagement:VS.msSecActDuplicateActivation))
SessionManagement:VS.sgsnDeactReactivationRequested) /
(SessionManagement:SM.AttDeactPdpContextMs SessionManagement:VS.msDeactFailures +
SessionManagement:VS.sgsnDeactNoMsgSentToMs +
SessionManagement:VS.sgsnDeactReactivationRequested))
SessionManagement:VS.peakActiveSubscribers
—sheet 5 of 11—
411-8111-803
Standard
01.06
May 2006
Table 2-10
Group
Name
Formula
SessionManagement:VS.peakPdpContexts
SessionManagement:VS.sgsnDeactReactivationRequested SessionManagement:VS.sgsnDeactDetachReattach SessionManagement:VS.sgsnDeactImplicitDetach SessionManagement:VS.sgsnDeactNetFailRncFailure SessionManagement:VS.sgsnDeactReactReqGgsnRestart) /
((SessionManagement:VS.sgsnDeactNoMsgSentToMs +
SessionManagement:VS.sgsnDeactReactivationRequested SessionManagement:VS.sgsnDeactDetachReattach SessionManagement:VS.sgsnDeactImplicitDetach SessionManagement:VS.sgsnDeactNetFailRncFailure SessionManagement:VS.sgsnDeactReactReqGgsnRestart) +
(SessionManagement:SM.AttDeactPdpContextMs SessionManagement:VS.msDeactFailures +
SessionManagement:VS.sgsnDeactDetachReattach +
SessionManagement:VS.sgsnDeactDupActRequest +
SessionManagement:VS.sgsnDeactNetFailRncFailure +
SessionManagement:VS.sgsnDeactReactReqGgsnRestart +
SessionManagement:VS.sgsnDeactImplicitDetach)))
SessionManagement_SUM
100 * (SessionManagement_SUM:SM.SuccActPdpContext +
SessionManagement_SUM:VS.actFailMissingOrUnknownApn) /
(SessionManagement_SUM:SM.SuccActPdpContext +
SessionManagement_SUM:VS.actFailMissingOrUnknownApn +
SessionManagement_SUM:VS.actFailSgsnInsufficientResources
+
SessionManagement_SUM:VS.actFailGgsnInsufficientResources
+ SessionManagement_SUM:VS.actFailRejectedByGgsn +
SessionManagement_SUM:VS.actFailUnknownPdpAddrOrPdpTyp
e + SessionManagement_SUM:VS.actFailUserAuthentications)
—sheet 6 of 11—
GSM18/UMTS04
Table 2-10
Group
Name
Formula
PC03_3G_SGSN_Retainability
100 * (1 - SessionManagement_SUM:VS.usgsnInitDeacts /
(SessionManagement_SUM:VS.usgsnInitDeacts +
SessionManagement_SUM:SM.AttDeactPdpContextGgsn +
SessionManagement_SUM:VS.hlrInitDeacts +
SessionManagement_SUM:SM.AttDeactPdpContextMs))
SessionManagement_SUM:SM.AttActSecondPdpContext) (SessionManagement_SUM:VS.msPrimActRejectedByGgsn +
SessionManagement_SUM:VS.msSecActRejectedByGgsn +
SessionManagement_SUM:VS.msPrimActGeInsufficientRes +
SessionManagement_SUM:VS.msSecActGeInsufficientRes +
SessionManagement_SUM:VS.msPrimActTunnelSetupFail +
SessionManagement_SUM:VS.msPrimActGgsnRestart +
SessionManagement_SUM:VS.msSecActGgsnRestart +
SessionManagement_SUM:VS.msSecActDuplicateActivation +
SessionManagement_SUM:VS.msPrimActDetachReqActReject +
SessionManagement_SUM:VS.msPrimActRadioLinkDown +
SessionManagement_SUM:VS.msSecActRadioLinkDown +
pl + SessionManagement_SUM:VS.msPrimActConditionalIeError))
—sheet 7 of 11—
411-8111-803
Standard
01.06
May 2006
Table 2-10
Group
Name
Formula
100 * (1 (SessionManagement_SUM:VS.newSgsnIrauActivationFailures +
SessionManagement_SUM:VS.newSgsnUpdPdpCtxtRspFailure SessionManagement_SUM:VS.newSgsnUpdPdpCFailSvcNotSup
ported +
SessionManagement_SUM:VS.oldSgsnDeactDatapathFail +
SessionManagement_SUM:VS.oldSgsnDeactSendGeFail +
SessionManagement_SUM:VS.oldSgsnDeactGeDefaultHandling +
SessionManagement_SUM:VS.oldSgsnDeactNetworkFailure) /
100 * (1 (SessionManagement_SUM:VS.newSgsnIrauActivationFailures SessionManagement_SUM:VS.newSgsnDelPdpCtxtRequest SessionManagement_SUM:VS.newSgsnCamelChangeOfPosFailu
re SessionManagement_SUM:VS.newSgsnGeGprsReleaseRequest
- SessionManagement_SUM:VS.newSgsnInvalidPdpCtxtsDropped
- SessionManagement_SUM:VS.newSgsnGgsnRestartRestoration
- SessionManagement_SUM:VS.newSgsnGeDefaultHandling +
SessionManagement_SUM:VS.newSgsnUpdPdpCFailNonExistant
+
SessionManagement_SUM:VS.newSgsnUpdPdpCFailSystemFailu
re + SessionManagement_SUM:VS.oldSgsnDeactDatapathFail +
SessionManagement_SUM:VS.oldSgsnDeactSendGeFail) /
—sheet 8 of 11—
GSM18/UMTS04
Table 2-10
Group
Name
Formula
SessionManagement_SUM:SM.AttActSecondPdpContext) (SessionManagement_SUM:VS.msPrimActDetachReqActReject +
SessionManagement_SUM:VS.msPrimActMissingOrUnknownApn
+
SessionManagement_SUM:VS.msPrimActReqSvcOpNotSubscrib
ed +
SessionManagement_SUM:VS.msSecActReqSvcOpNotSubscribe
d+
SessionManagement_SUM:VS.msPrimActUserAuthenticationFail
+ SessionManagement_SUM:VS.msSecActUserAuthenticationFail
+ SessionManagement_SUM:VS.msPrimActInvalidTiValue +
SessionManagement_SUM:VS.msSecActInvalidTiValue +
SessionManagement_SUM:VS.msPrimActSemIncorrectMsg +
pl + SessionManagement_SUM:VS.msPrimActConditionalIeError
+ SessionManagement_SUM:VS.msSecActConditionalIeError +
SessionManagement_SUM:VS.msSecActDuplicateActivation))
—sheet 9 of 11—
411-8111-803
Standard
01.06
May 2006
Table 2-10
Group
Name
Formula
/
(SessionManagement_SUM:SM.AttDeactPdpContextMs SessionManagement_SUM:VS.msDeactFailures +
SessionManagement_SUM:VS.sgsnDeactNoMsgSentToMs +
)
SessionManagement_SUM:VS.peakActiveSubscribers
SessionManagement_SUM:VS.peakPdpContexts
GSM18/UMTS04
Table 2-10
Group
Name
Formula
- SessionManagement_SUM:VS.sgsnDeactDetachReattach SessionManagement_SUM:VS.sgsnDeactImplicitDetach SessionManagement_SUM:VS.sgsnDeactNetFailRncFailure SessionManagement_SUM:VS.sgsnDeactReactReqGgsnRestart)
/
((SessionManagement_SUM:VS.sgsnDeactNoMsgSentToMs +
- SessionManagement_SUM:VS.sgsnDeactDetachReattach SessionManagement_SUM:VS.sgsnDeactImplicitDetach SessionManagement_SUM:VS.sgsnDeactNetFailRncFailure SessionManagement_SUM:VS.sgsnDeactReactReqGgsnRestart)
+
(SessionManagement_SUM:SM.AttDeactPdpContextMs SessionManagement_SUM:VS.msDeactFailures +
SessionManagement_SUM:VS.sgsnDeactDetachReattach +
SessionManagement_SUM:VS.sgsnDeactDupActRequest +
SessionManagement_SUM:VS.sgsnDeactNetFailRncFailure +
SessionManagement_SUM:VS.sgsnDeactReactReqGgsnRestart
+ SessionManagement_SUM:VS.sgsnDeactImplicitDetach)))
Relay
100 * Relay:VS.discardedPdus / ( Relay:GTP.GtpuInDataPktIu +
Relay:GTP.InDataPktGn )
Relay_SUM
100 * Relay_SUM:VS.discardedPdus / (
Relay_SUM:GTP.GtpuInDataPktIu +
Relay_SUM:GTP.InDataPktGn )
411-8111-803
Standard
01.06
May 2006
Table 2-11
Correlated OMs related to GGSN
Group
Name
Formula
SM_Stats
PC03_GGSN_Nodal_Activation_Success_Rate
100 * ( SM_Stats:SM.SuccActPdpCtxt.Bgrd.Low +
SM_Stats:SM.SuccActPdpCtxt.Intact.Low +
SM_Stats:SM.SuccActPdpCtxt.Strm.Low +
SM_Stats:SM.SuccActPdpCtxt.Conv.Low +
SM_Stats:SM.SuccActPdpCtxt.Bgrd.Medium +
SM_Stats:SM.SuccActPdpCtxt.Intact.Medium +
SM_Stats:SM.SuccActPdpCtxt.Strm.Medium +
SM_Stats:SM.SuccActPdpCtxt.Conv.Medium +
SM_Stats:SM.SuccActPdpCtxt.Bgrd.High +
SM_Stats:SM.SuccActPdpCtxt.Intact.High +
SM_Stats:SM.SuccActPdpCtxt.Strm.High +
SM_Stats:SM.SuccActPdpCtxt.Conv.High ) / (
SM_Stats:VS.SM.AttActPdpCtxt SM_Stats:VS.SM.DupAttActPdpCtxt SM_Stats:SM.FailActPdpCtxt.219 SM_Stats:SM.FailActPdpCtxt.220 SM_Stats:SM.FailActPdpCtxt.209 SM_Stats:VS.SM.FailActPdpCtxt.SEME SM_Stats:VS.SM.FailActPdpCtxt.IEIN SM_Stats:SM.FailActPdpCtxt.193 SM_Stats:VS.SM.FailActPdpCtxt.OVLD SM_Stats:SM.FailActPdpCtxt.200 )
PC03_GGSN_Network_Activation_Success_Rate
SM_Stats:SM.SuccActPdpCtxt.Conv.High ) /
SM_Stats:VS.SM.AttActPdpCtxt
—sheet 1 of 8—
GSM18/UMTS04
Table 2-11
Group
Name
Formula
PC03_GGSN_Activations_Per_Second
( SM_Stats:SM.SuccActPdpCtxt.Bgrd.Low +
SM_Stats:SM.SuccActPdpCtxt.Conv.High ) / 900
PC03_GGSN_Peak_Concurrent_Sessions
SM_Stats:VS.SM.MaxNbrActPdpCtxt
( SM_Stats:SM.SuccActPdpCtxt.Bgrd.Low +
SM_Stats:SM.SuccActPdpCtxt.Conv.High ) / 900
PC04_GGSN_Network_Activation_Secondary_PDP_Context_Suc
cess_
Rate
100 * SM_Stats:VS.SM.SuccActSecPdpCtxt /
SM_Stats:VS.SM.AttActSecPdpCtxt
—sheet 2 of 8—
411-8111-803
Standard
01.06
May 2006
Table 2-11
Group
Name
Formula
SM_Stats:SM.SuccActPdpCtxt.Conv.High ) /
SM_Stats:VS.SM.AttActPdpCtxt
SM_Stats:SM.SuccActPdpCtxt.Conv.High ) / (
SM_Stats:VS.SM.AttActPdpCtxt SM_Stats:VS.SM.DupAttActPdpCtxt SM_Stats:SM.FailActPdpCtxt.219 SM_Stats:SM.FailActPdpCtxt.220 SM_Stats:SM.FailActPdpCtxt.209 SM_Stats:VS.SM.FailActPdpCtxt.SEME SM_Stats:VS.SM.FailActPdpCtxt.IEIN SM_Stats:SM.FailActPdpCtxt.193 SM_Stats:VS.SM.FailActPdpCtxt.OVLD SM_Stats:SM.FailActPdpCtxt.200 )
—sheet 3 of 8—
GSM18/UMTS04
Table 2-11
Group
Name
Formula
SM_Stats:VS.SM.MaxNbrActPdpCtxt
PC04_GGSN_Secondary_Activations_Per_Second
SM_Stats:VS.SM.SuccActSecPdpCtxt / 900
SM_Stats_SUM
100 * (SM_Stats_SUM:SM.SuccActPdpCtxt.Bgrd.Low +
SM_Stats_SUM:SM.SuccActPdpCtxt.Intact.Low +
SM_Stats_SUM:SM.SuccActPdpCtxt.Strm.Low +
SM_Stats_SUM:SM.SuccActPdpCtxt.Conv.Low +
SM_Stats_SUM:SM.SuccActPdpCtxt.Bgrd.Medium +
SM_Stats_SUM:SM.SuccActPdpCtxt.Intact.Medium +
SM_Stats_SUM:SM.SuccActPdpCtxt.Strm.Medium +
SM_Stats_SUM:SM.SuccActPdpCtxt.Conv.Medium +
SM_Stats_SUM:SM.SuccActPdpCtxt.Bgrd.High +
SM_Stats_SUM:SM.SuccActPdpCtxt.Intact.High +
SM_Stats_SUM:SM.SuccActPdpCtxt.Strm.High +
SM_Stats_SUM:SM.SuccActPdpCtxt.Conv.High) /
(SM_Stats_SUM:VS.SM.AttActPdpCtxt SM_Stats_SUM:VS.SM.DupAttActPdpCtxt SM_Stats_SUM:SM.FailActPdpCtxt.219 SM_Stats_SUM:SM.FailActPdpCtxt.220 SM_Stats_SUM:SM.FailActPdpCtxt.209 SM_Stats_SUM:VS.SM.FailActPdpCtxt.SEME SM_Stats_SUM:VS.SM.FailActPdpCtxt.IEIN SM_Stats_SUM:SM.FailActPdpCtxt.193 SM_Stats_SUM:VS.SM.FailActPdpCtxt.OVLD SM_Stats_SUM:SM.FailActPdpCtxt.200)
—sheet 4 of 8—
411-8111-803
Standard
01.06
May 2006
Table 2-11
Group
Name
Formula
100 * ( SM_Stats_SUM:SM.SuccActPdpCtxt.Bgrd.Low +
SM_Stats_SUM:SM.SuccActPdpCtxt.Conv.High ) /
SM_Stats_SUM:VS.SM.AttActPdpCtxt
( SM_Stats_SUM:SM.SuccActPdpCtxt.Bgrd.Low +
SM_Stats_SUM:SM.SuccActPdpCtxt.Conv.High ) / 900
SM_Stats_SUM:VS.SM.MaxNbrActPdpCtxt
—sheet 5 of 8—
GSM18/UMTS04
Table 2-11
Group
Name
Formula
( SM_Stats_SUM:SM.SuccActPdpCtxt.Bgrd.Low +
SM_Stats_SUM:SM.SuccActPdpCtxt.Conv.High ) / 900
PC04_GGSN_Network_Activation_Secondary_PDP_Context_Suc
cess_
Rate
100 * SM_Stats_SUM:VS.SM.SuccActSecPdpCtxt /
SM_Stats_SUM:VS.SM.AttActSecPdpCtxt
100 * ( SM_Stats_SUM:SM.SuccActPdpCtxt.Bgrd.Low +
SM_Stats_SUM:SM.SuccActPdpCtxt.Conv.High ) /
SM_Stats_SUM:VS.SM.AttActPdpCtxt
—sheet 6 of 8—
411-8111-803
Standard
01.06
May 2006
Table 2-11
Group
Name
Formula
100 * (SM_Stats_SUM:SM.SuccActPdpCtxt.Bgrd.Low +
SM_Stats_SUM:SM.SuccActPdpCtxt.Conv.High) /
(SM_Stats_SUM:VS.SM.AttActPdpCtxt SM_Stats_SUM:VS.SM.DupAttActPdpCtxt SM_Stats_SUM:SM.FailActPdpCtxt.219 SM_Stats_SUM:SM.FailActPdpCtxt.220 SM_Stats_SUM:SM.FailActPdpCtxt.209 SM_Stats_SUM:VS.SM.FailActPdpCtxt.SEME SM_Stats_SUM:VS.SM.FailActPdpCtxt.IEIN SM_Stats_SUM:SM.FailActPdpCtxt.193 SM_Stats_SUM:VS.SM.FailActPdpCtxt.OVLD SM_Stats_SUM:SM.FailActPdpCtxt.200)
SM_Stats_SUM:VS.SM.MaxNbrActPdpCtxt
PC04_GGSN_Secondary_Activations_Per_Second
SM_Stats_SUM:VS.SM.SuccActSecPdpCtxt / 900
perAPN_Stats
PC03_GGSN_Updates_Per_Second
( perAPN_Stats:SM.SuccUpdPdpCtxtMsAndSgsn.Apn +
perAPN_Stats:VS.SM.SuccUpdPdpCtxtGgsn.Apn ) / 900
PC03_GGSN_Deactivations_Per_Second
( perAPN_Stats:VS.SM.SuccDeactPdpCtxtMsAndSgsn.Apn +
perAPN_Stats:SM.SuccDeactPdpCtxtGgsn.Apn ) / 900
—sheet 7 of 8—
GSM18/UMTS04
Table 2-11
Group
Name
Formula
perAPN_Stats_SUM
( perAPN_Stats_SUM:SM.SuccUpdPdpCtxtMsAndSgsn.Apn +
perAPN_Stats_SUM:VS.SM.SuccUpdPdpCtxtGgsn.Apn ) / 900
( perAPN_Stats_SUM:VS.SM.SuccDeactPdpCtxtMsAndSgsn.Apn
+ perAPN_Stats_SUM:SM.SuccDeactPdpCtxtGgsn.Apn ) / 900
( perAPN_Stats_SUM:SM.SuccUpdPdpCtxtMsAndSgsn.Apn +
perAPN_Stats_SUM:VS.SM.SuccUpdPdpCtxtGgsn.Apn ) / 900
( perAPN_Stats_SUM:VS.SM.SuccDeactPdpCtxtMsAndSgsn.Apn
+ perAPN_Stats_SUM:SM.SuccDeactPdpCtxtGgsn.Apn ) / 900
GGSN_Overload_Stats
PC03_GGSN_CMC_P0_Resource_Utilization
GGSN_Overload_Stats:VS.Ovld.CmcCpuTot.HighestAvgPct
PC04_GGSN_CMC_P0_CPU_Resource_Utilization
GGSN_Overload_Stats:VS.Ovld.CmcCpuTot.HighestAvgPct
GGSN_Overload_Stats_SUM
PC03_GGSN_CMC_P0_Resource_Utilization
GGSN_Overload_Stats_SUM:VS.Ovld.CmcCpuTot.HighestAvgPct
PC04_GGSN_CMC_P0_CPU_Resource_Utilization
GGSN_Overload_Stats_SUM:VS.Ovld.CmcCpuTot.HighestAvgPct
—sheet 8 of 8—
Correlations for GGSN, SIG and SGSN domains require metrics calculated
for the entire Network Element (NE). The performance pipeline supports the
granularity reported by the Operational Measurement (OM) feed of the NEs,
which is often reported to the sub-component level. To support correlations at
the NE level for the performance dashboard, the inputs to the correlation
formulas will be summed across their sub-components to produce NE level
inputs.
411-8111-803
Standard
01.06
May 2006
HLR100 correlated OMs
2
Table 2-12 provides the following information:
• GSM 12.04 — This column lists the section of GSM12.04 where the
measurement is detailed, and the attribute name from GSM12.04, Annex
C. All arithmetic is based on actual DMS-OM registers or the correlated
GSM 12.04 attributes.
•
Internal name — This column lists the internal name of a multi-valued
GSM12.04 attribute.
•
Description & Definition — This column provides the description, or
expanded name, and the definition of the correlating HLR100 OM group
and corresponding register.
Note: All OM registers referenced below assume that the extension
registers have already been amalgamated.
Table 2-12
Correlated OMs (hlrMeasurementFunction1 hlrMeasurementFunction2) related to HLR100
GSM 12.04
Section
Internal Name
Description
B4.1.1
nbrOfCurrentMSsRoamingOutsideHPLM
N
Number of current MS’s Roaming outside
HPLMN
= GHLRROAM:INTLSUBS
B4.1.2
attReqForAuthSetsReceivedByHLRFromV
LRs
Attempted requests for Authentication
sets received by HLR from VLRs
= HSMG2:SAIREQS +
GHLRSMGT:SPAURQ
B4.1.3
succReturnedAuthSetsFromHLRToVLRs
Successful returned Authentication sets
from HLR to VLRs
= HSMG2:SAIRESL +
GHLRSMGT:SPAURES
B4.1.4
emptyResponsesForAuthSetsFromHLRTo
VLRs
Empty responses to request for
Authorization sets from HLR to VLRs.
= GHLRSMGT:EAUCSTS.
B4.1.5
attInsertSubDataService
Attempted insert subscriber data service
= GHLRSMGT:ISDRQ
—sheet 1 of 4—
GSM18/UMTS04
Table 2-12 (continued)
GSM 12.04
Section
Internal Name
Description
B4.1.6
succInsertSubDataService
Successful insert subscriber data service
= GHLRSMGT:ISDRES
B4.1.7
attLocationUpdate
Attempted Location Updates
= GHLRMMGT:LURQ:summation
B4.1.8
succLocationUpdate
Successful Location Updates
= GHLRMMGT:LURES
B4.1.9
attActSSRelatedOperationsInHLR
Attempted Activate SS operations in HLR
= HCISSOPS:ACTSSREQ:summation
B4.1.9
attDeactSSRelatedOperationsInHLR
Attempted Deactivate SS operations in
HLR
= HCISSOPS:DACSSREQ:summation
B4.1.9
attEraseSSRelatedOperationsInHLR
Attempted Erase SS operations in HLR
= HCISSOPS:ERASSREQ:summation
B4.1.9
attIntSSRelatedOperationsInHLR
Attempted Interrogate SS operations in
HLR
= HCISSOPS:INTSSREQ:summation
B4.1.9
attRegSSRelatedOperationsInHLR
Attempted Register SS operations in
HLR
= HCISSOPS:REGSSREQ:summation
B4.1.9
attRegPWSSRelatedOperationsInHLR
Register Password requests received by
the HLR
= HCISSOPS:RPWSSREQ:summation
B4.1.10
succActSSRelatedOperationsInHLR
Successful Activate SS operations in
HLR
= HCISSOPS:ACTSSRES:summation
—sheet 2 of 4—
411-8111-803
Standard
01.06
May 2006
GSM 12.04
Section
Internal Name
Description
B4.1.10
succDeactSSRelatedOperationsInHLR
Successful Deactivate SS operations in
HLR
=HCISSOPS:DACSSRES:summation
B4.1.10
succEraseSSRelatedOperationsInHLR
Successful Erase SS operations in HLR
=HCISSOPS:ERASSRES:summation
B4.1.10
succIntSSRelatedOperationsInHLR
Successful Interrogate SS operations in
HLR
=HCISSOPS:INTSSRES:summation
B4.1.10
succRegSSRelatedOperationsInHLR
Successful Register SS operations in
HLR
=HCISSOPS:REGSSRES:summation
B4.1.10
succRegPWSSRelatedOperationsInHLR
Register Password results processed by
the HLR
=HCISSOPS:RPWSSRES:summation
B4.1.11
attReqForSMRoutingInfo
Attempted request for SM routing
information
= HSMSOPS:SRMREQ:summation
B4.1.12
succReqForSMRoutingInfo
Successful request for SM routing
information
= HSMSOPS:SRMRES:summation
B4.1.3
attSMDeliveryStatusReportProcs
Attempted SM delivery status report
procedures
= HSMSOPS:RDSREQ:summation
B4.1.4
succSMDeliveryStatusReportProcs
Successful SM delivery status report
procedures
= HSMSOPS:RDSRES:summation
—sheet 3 of 4—
GSM18/UMTS04
GSM 12.04
Section
Internal Name
Description
B4.1.5
attNbrOfSendAlerts
Attempted number of send alerts
= HSMSOPS:ALRTREQ:summation +
HSMSOPS:ASCWREQ:summation
B4.1.6
succNbrOfSendAlerts
Successful number of send alerts
= HSMSOPS:ALRTRES:summation
B4.1.7
attReqForMSRN
Attempted request for MSRN
= GHLRCH:PRNRQ
B4.1.18
succReqForMSRN
Successful request for MSRN
= GHLRCH:PRNRES
attSSRelatedOperationsInHLR
= GHLRMMGT:ACTSSREQ:summation
+ GHLRMMGT:DACSSREQ:summation
+ GHLRMMGT:ERASSREQ:summation
+ GHLRMMGT:INTSSREQ:summation
+ GHLRMMGT:REGSSREQ:summation
+ GHLRMMGT:RPWSSREQ:summation
succSSRelatedOperationsInHLR
= GHLRMMGT:ACTSSRES:summation
+ GHLRMMGT:DACSSRES:summation
+ GHLRMMGT:ERASSRES:summation
+ GHLRMMGT:INTSSRES:summation
+ GHLRMMGT:REGSSRES:summation
+ GHLRMMGT:RPWSSRES:summation
—sheet 4 of 4—
411-8111-803
Standard
01.06
May 2006
MSC correlated OMs
2
Table 2-13 provides the following information:
• Internal name — This column lists the internal name of a multi-valued
GSM12.04 attribute.
•
expanded name, and the definition of the correlating MSC OM group and
corresponding register.
Table 2-13
Correlated OMs (mscMeasurementFunction) related to MSC
Internal Name
Description
nbrOfClassMarkUpdates
Number of class mark updates
=MSCCP:CMR2UPD
attMobileOriginatingCalls
Attempted mobile originating calls
=MSCCP:MMBID + MSCCP:MLBID
succMobileOriginatingCalls
Successful mobile originating calls
=MSCCP:MMSUCC + MSCCP:MLSUCC
ansMobileOriginatingCalls
Answered mobile originating calls
=MSCCP:MMESTAB + MSCCP:MLESTAB
attMobileTerminatingCalls
Attempted mobile terminating calls
=MSCCP:MMBID + MSCCP:LMBID
succMobileTerminatingCalls
Successful mobile terminating calls
=MSCCP:MMSUC + MSCCP:LMSUCC
ansMobileTerminatingCalls
Answered mobile terminating calls
=MSCCP:MMESTAB + MSCCP:LMESTAB
attMobileEmergencyCalls
Attempted Mobile Emergency calls
=MSCCP:MEEBID
succMobileEmergencyCalls
Successful Mobile Emergency calls
=MSCCP:MEESUCC
—sheet 1 of 4—
GSM18/UMTS04
Table 2-13
Internal Name
Description
ansMobileEmergencyCalls
Answered Mobile Emergency calls
=MSCCP:MEESTAB
attCipheringModeControlProcs
Attempted ciphering mode control procedures
=MSCCP:CIM1ATT + MSCCP:CIM2ATT
succCipheringModeControlProcs
Successful ciphering mode control procedures
=MSCCP:CIM1SUC + MSCCP:CIM2SUC
attInterrogationOfHLRsForRouting
Attempted interrogations of HLRs for routing
=GMAPCH:GMSRIREQ
attOpForMobileOriginatingPointToPointSMs
Attempted operations for mobile originating point
to point SMs
=MSCSMS:SMMOATT
succOpForMobileOriginatingPointToPointSMsg
Successful operations for mobile originating
point to point SMs
=MSCSMS:SMMOSUC
attOpForMobileTerminatingPointToPointSMs
Attempted operations for mobile terminating
point to point SMs
=MSCSMS:SMMTRPA
succOpForMobileTerminatingPointToPointSMs
Successful Operations for Mobile Terminating
Point to Point SMs
=MSCSMS:SMMTRPS
nbrOfTransCheckIMEIRequests
Number of transmitted check IMEI request
=GMAPEMGT:GMCIMREQ
nbrOfWhiteAnsInMSC
Number of white answers in MSC
=GMAPEMGT:GMCIMWHT
—sheet 2 of 4—
411-8111-803
Standard
01.06
May 2006
Table 2-13
Internal Name
Description
nbrOfGreyAnsInMSC
Number of grey answers in MSC
=GMAPEMGT:GMCIMGRY
nbrOfBlackAnsInMSC
Number of black answers in MSC
=GMAPEMGT:GMCIMBLK
nbrOfUnknownIMEIAnsInMSC
Number of unknown IMEI answers
=GMAPEMGT:GMCIMUNK
meanTimeToCallSetupService
Mean time to provide the CALL SETUP service
= GMEANTM:TTSUPDC +
GMEANTM:TTSUPVC/
GMEANTM:SUPDCCT + GMEANTM:SUPVCCT
meanTimeToLocationUpdateService
Mean time to provide the LOCATION UPDATING
service
= GMEANTM2:TTLUPIA +
GMEANTM2:TTLUPIR/ GMEANTM2:LUPIACT
+ GMEANTM2:LUPIRCT
transSubIdentifiedWithTMSI
Transactions on the MM-layer where subscriber
was identified with TMSI
=GMMLTRN:TMSIID
transSubIdentifiedWithIMSI
Transactions on the MM-layer where subscriber
was identified with IMSI
=GMMLTRN:IMSIID
attTMSIReallocations
Attempted TMSI re-allocations
=MSCCP3:TMSIRAT + MSCCP:TMSILAT
succTMSIReallocations
Successful TMSI re-allocation
=MSCCP3:TMSIRSU
—sheet 3 of 4—
GSM18/UMTS04
Table 2-13
Internal Name
Description
imsiDetachProcs
IMSI detach procedures
=VLR:IMSIDET
imsiAttachProcs
IMSI attach procedures
=VLR:IMSIATT
attOutgoingExternalIntraMSCHDOs
= HO2GTO2G:A2GRAMAH
succOutgoingExternalIntraMSCHDOs
= HO2GTO2G:S2GRAMAH
attIncomingInterMSCHDOs
= HO2GTO2G:A2GIEMHO
succIncomingInterMSCHDOs
= HO2GTO2G:S2GIEMHO
attOutgoingInterMSCHDOs
= HO2GTO2G:A2GOEMHO
succOutgoingInterMSCHDOs
= HO2GTO2G:S2GOEMHO
attSubsequentInterMSCHDOsMSCa
= HO2GTO2G:A2GSUBHB
succSubsequentInterMSCHDOsMSCa
= HO2GTO2G:S2GSUBHB
attSubsequentInterMSCHDOsMSCc
= HO2GTO2G:A2GSBEMH
succSubsequentInterMSCHDOsMSCc
= HO2GTO2G:S2GSBEMH
—sheet 4 of 4—
411-8111-803
Standard
01.06
May 2006
DMS-VLR correlated OMs
2
Table 2-14 and Table 2-15 provide the following information:
• Internal name — This column lists the internal name of a multi-valued
GSM12.04 attribute.
•
expanded name, and the definition of the correlating DMS-VLR OM
group and corresponding register.
Table 2-14
Correlated OMs (vlrMeasurementFunction) related to DMS-VLR
Internal Name
Description
attPageReqs
Attempted page requests
=VLR4:FPGPSAT + VLR4:PGRPSAT
succPageReqs
Successful page requests
=VLR4:FPGPSSU + VLR4:PGRPSSU
attReqForAuthSetsSentToHLR
Attempted requests for Authentication sets sent to HLR by
VLRs
=GMAPSMGT:SAIREQ
succReceivedAuthSetsFromHLR
Successful received Authentication sets from HLR to VLRs
=GMAPSMGT:SAIRES
emptyResponsesForAuthFromHLR
Empty responses to request for Authentication sets from
HLR to VLRs
=VLR:AUR2EMP + VLR:AUR1EMP
attAuthProcsInVLR
Attempted authentication procedures in VLR
=VLR:AUTPATT
succAuthProcsInVLR
Successful authentication procedures in the VLR
=VLR:AUTPSUC
attIntraVLRLocationUpdates
Attempted intra-VLR Location Updates
=VLR2:IAVLHAT + VLR2:IAVLRAT
—sheet 1 of 2—
GSM18/UMTS04
Table 2-14
Correlated OMs (vlrMeasurementFunction) related to DMS-VLR
Internal Name
Description
succIntraVLRLocationUpdates
Successful intra-VLR Location Updates
=VLR:LURAVLR + VLR:LURAVLRR
attInterVLRLocationUpdates
Attempted inter-VLR Location Updates
=VLR2:IRVLHAT + VLR2:IRVLRAT
succInterVLRLocationUpdates
Successful inter-VLR Location Updates
=VLR:LUERVLR + VLR:LUERVLRR
—sheet 2 of 2—
Table 2-15
Correlated OMs (vlrMeasurementFunction1) related to DMS-VLR
Internal Name
Description
attPageReqs
Attempted page requests
=VLR:FPGPSAT + VLR:PGRPSAT
succPageReqs
Successful page requests
=VLR:FPGPSSU + VLR:PGRPSSU
attReqForAuthSetsSentToHLR
Attempted requests for Authentication sets sent to HLR by
VLRs
=GMAPSMGT:SAIREQ
succReceivedAuthSetsFromHLR
Successful received Authentication sets from HLR to VLRs
=GMAPSMGT:SAIRES
emptyResponsesForAuthFromHLR
Empty responses to request for Authentication sets from
HLR to VLRs
=VLR:AUR2EMP + VLR:AUR1EMP
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 2-15
Correlated OMs (vlrMeasurementFunction1) related to DMS-VLR
Internal Name
Description
attAuthProcsInVLR
Attempted authentication procedures in VLR
=VLR:AUTPATT
succAuthProcsInVLR
Successful authentication procedures in the VLR
=VLR:AUTPSUC
attIntraVLRLocationUpdates
Attempted intra-VLR Location Updates
=VLR:IAVLHAT + VLR:IAVLRAT
succIntraVLRLocationUpdates
Successful intra-VLR Location Updates
=VLR:LURAVLR + VLR:LURAVLRR
attInterVLRLocationUpdates
Attempted inter-VLR Location Updates
=VLR:IRVLHAT + VLR:IRVLRAT
succInterVLRLocationUpdates
Successful inter-VLR Location Updates
=VLR:LUERVLR + VLR:LUERVLRR
—sheet 2 of 2—
GSM18/UMTS04
Billing OMs
2
OM group related information
The OM groups listed in Table 2-16 do not exist on the MSC. These groups
are fabricated from the billing stream by processes running on the SDM.
These processes comprise the Billing Statistics Application, which is part of
the OMC-S system.
The following terms are used in the discussion of Billing OMs:
• Prefix - A string of digits which are said to match a dialed digits, calling
number, called number or forward-to number field in a CDR if they are
the initial digits of the number. The allowed characters are ‘A’ - ‘E’, ‘#’,
‘*’, ‘0’ - ‘9’, where ‘#’ is a substitute for ‘A’, and ‘*’ is a substitute for
‘B’.
•
Prefix group - A set of prefixes which are given a name (tag) by the user
and which are reported as a group using the tag.
•
Destination - A list of prefix digits as dialed digits, calling number, called
number, or the combinations of calling number and one of dialed digits,
and called number.
•
Diagnostic group - A set of diagnostics which are given a name (tag) by
the user and which are reported as a group using the tag.
Table 2-16
OM groups derived from billing data
Group Name
(acronym)
Group Name
(expanded)
Reason
CDRDIAG
Diagnostics per CDR type.
Gives the number of occurrences of each user
defined set of diagnostics for each CDR type.
MSCBILL
MSC Billing Data
Provides data needed for GSM 12.04
compliance.
MSCBILL2
MSC Billing Data 2
Provides call statistics.
PREFIXDIAG
Diagnostics per User Defined
Prefix Groups
Gives the number of occurrences of each pair
of user defined prefix group and user defined
diagnostic group.
TERMREASON
Termination Reason
Provides statistics related to call termination.
Reported according to user defined sets of
termination reasons.
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 2-16
OM groups derived from billing data
Group Name
(acronym)
Group Name
(expanded)
Reason
TRAFFICDEST
Traffic Destination per Trunk
Provides statistics related to dialled digits,
calling, and called number usage. Reported
according to user defined sets of prefixes.
TRAFFICDEST2
Traffic Destination
Summaries
calling number, and called number usage.
Reported as summary data for user defined
sets of prefixes.
TRAFFICDEST3
Traffic Destination per
Selected Trunk
calling and called number usage, and incoming
and outgoing trunk group usage. Reported
according to user defined sets of prefixes and
trunk groups.
TRUNKIO
Trunk I/O Measurements
Provides statistics related to trunk usage.
—sheet 2 of 2—
OM Group: CDRDIAG
The CDRDIAG group collects counts of MO, MT, R, IT, and OT as well as
Incoming Gateway Call, and Outgoing Gateway Call records. It also collects
counts of IT and OT by directly counting CDR records of Incoming IntraPLMN Trunk and Outgoing Intra-PLMN Trunk records. Each record is
represented as a separate call type, and has its own row in the table.
CDRDIAG contains diagnostics information for the MO, MT, R, IT, OT, IG
and OG rows in the MSC CDR Statistics window.
Group structure
• Key Field: CDR type (MO, MT, R, IT, OT, IG or OG)
•
Info Field: Diagnostic group tag
•
Number of Tuples: Open ended, one for each combination of CDR type
and diagnostic group
Register list
• TOTAL - Total count of the combinations of CDR type and diagnostic
group
GSM18/UMTS04
Register TOTAL
Total
Register TOTAL is a peg register that counts the number of combinations of
CDR type and diagnostic group
Release history
Created for the GEM11 release of the OMC-S system.
OM Group: MSCBILL
This group counts occurrences of successful incoming external intra-MSC
handovers, attempted SMO forwarding and successful SMO forwarding. It
contributes to GSM 12.04 compliance for the OMC-S system.
It can be used to gauge the amount of handover and SM forwarding in the
system.
Group structure
• Key Field: None
•
Info Field: MSC Name
•
Number of Tuples: 1
Register list
• SIEIAMSC - Successful Incoming External Intra-MSC handovers
•
AMOSMF - Attempted MO SM Forwarding
•
SMOSMF - Successful MO SM Forwarding
Register AMOSMF
Attempted Mobile Originated Short Message Forwarding
Register AMOSMF is a peg register that counts the number of Mobile
Originated Short Message Forwarding attempts.
This register is pegged when a CDR with a structure code of 0004C is
encountered in the billing stream.
Release history
Register SIEIAMSC
Successful Incoming Externally-controlled Intra-MSC handovers
Register SIEIAMSC is a peg register that counts the number of successful
incoming handovers that are local to the MSC and controlled by it.
411-8111-803
Standard
01.06
May 2006
This register is pegged when a CDR is encountered which has two or more
LAC modules attached to the structured record, and for each transition between
LAC modules the following conditions are true:
• The Cell ID changes from one LAC module to the next
•
The trunk group and/or the trunk member changes
Release history
Register SMOSMF
Successful Mobile Originated Short Message Forwarding
Register SMOSMF is a peg register that counts the number of successful
Mobile Originated short message forwarding attempts.
This register is pegged when a CDR with the following characteristics is
encountered:
• Structure code = 10004C
•
SMS Result Code = default value of FFFFFC
Release history
OM Group: MSCBILL2
This group reports on various kinds of normally and abnormally terminated
calls, as well as statistics related to call duration and system operation. The
registers of this group collect counts of the number of successful, failed,
completed and non-completed calls, as well as accumulating data needed for
averages and percentages.
The MSCBILL2 group additionally collects counts of Incoming Gateway
Call, and Outgoing Gateway Call records. It also collects counts of Incoming
Intra-PLMN Trunk and Outgoing Intra-PLMN Trunk. Each record type is
represented as a separate call type, and has its own row in the MSCBILL2
group, and in the MSC CDR Statistics window.
MSCBILL2 counts the number of calls which go through a target MSC by
counting Mobile Originated Call, Incoming Intra-PLMN Trunk with valid
outgoing trunk group, Incoming Gateway Call with valid outgoing trunk
group, and Mobile Terminated Call record with valid incoming trunk group.
This is a change from previous behavior where MSCBILL2 was simply
providing a CDR count.
Group structure
• Key Field: Call type (SUM, MO, MT, R, IT, OT, IG, and OG)
•
Info Field: None
GSM18/UMTS04
•
Number of Tuples: 6
The tuples of this group are fixed in number and type. The tuple’s keyfield
indicates the call type being measured.
The SUM (Summary) tuple accumulates all counts from all other tuples.
Time is taken from the CDR and measured in tenths of a second. The time is
reported in seconds. Registers in the summary tuple generally have a higher
value than the sum of the values in the other tuples. The values in the
summary tuple registers are more accurate, because rounding errors are
minimized.
MO tuples capture data from Mobile Originated CDRs. This is pegged for every
MO CDR encountered with two exceptions:
• CDRs which have the Call Forwarding Indicator set
•
CDRs which have the Proprietary Extension indicator set
MT tuples capture data from Mobile Terminated CDRs. This is pegged for every
MT CDR encountered with two exceptions:
• CDRs which have the Call Forwarding Indicator set
•
R tuples capture data from Roaming CDRs. This is pegged for every Roaming
CDR encountered with the following exceptions:
• Roaming CDRs when either the Incoming Trunk Group or the Outgoing
Trunk Group fields are invalid
•
CDRs which have the Call Forwarding Indicator set
•
IT tuples capture data related to Incoming Trunk calls (derived from Mobile
Terminated CDRs).
OT tuples capture data related to Outgoing Trunk calls (derived from Mobile
Originated CDRs).
Note: All registers are pegged on MO, MT, R, IT, OT, IG, and OG except
TSST. TSST is only pegged on MO, MT, and R.
Register list
• TOTAL - Total Calls
411-8111-803
•
ANT - Answered and Normally Terminated
•
AAT - Answered and Abnormally Terminated
•
NNT - Not answered and Normally Terminated
Standard
01.06
May 2006
•
NAT - Not answered and Abnormally Terminated
•
INTC - International Call
•
NATC - National Call
•
TTTA - Total Time to Answer
•
TSST - Total System Setup Time
•
TTTD - Total Time to Disconnect
•
TCD - Total Call Duration
•
ACD - Placeholder register for the GUI.
•
OSST - Total occurrences of pegging system setup time that used to
calculate an average of system setup time.
•
TOTAL_CALL - The total of calls which are originated, terminated or
passed on a measured MSC.
•
TOTAL_TSST - The total of CDRs in which TSST is pegged in order to
calculate an average of TSST in the Summary Report Manager.
When the GUI displays the average time information, the averages are
calculated using the following formulas:
• Average of System Setup time (ASST) = MSCBILL2:TSST /
MSCBILL2:OSST
•
Average of Time to Answer (ATTA) = MSCBILL2:TTTA /
(MSCBILL2:ANT + MSCBILL2:AAT)
•
Average of Time to Disconnect (ATTD) =
MSCBILL2:TTTD / (MSCBILL2:NNT + MSCBILL2:NAT)
•
Average of Call Duration (ACD) = MSCBILL2:TCD *
10 / (MSCBILL2:ANT + MSCBILL2:AAT)
Register AAT
Answered and Abnormally Terminated
Register AAT is a peg register which counts the number of answered but
abnormally terminated call attempts as recorded in the billing stream. This
register is pegged under the following conditions:
• the Answer Time field is valid
•
the Cause For Termination field indicates abnormal termination
Release history
GSM18/UMTS04
Register ANT
Answered and Normally Terminated
Register ANT is a peg register that counts the number of answered and normally
terminated call attempts recorded in the CDR stream. This register is pegged
under the following conditions:
•
the Cause For Termination field indicates normal termination
Release history
Register INTC
International Call
Register INTC is a peg register which counts the number of calls to an
international number, as recorded in the billing stream. This register is pegged
• the Nature of Address Indicator part of the Numbering Plan Identifier
field indicates an International call
Release history
Register NAT
Not answered and Abnormally Terminated
Register NAT is a peg register which counts the number of unanswered calls
which were abnormally terminated, as recorded in the billing stream. This
• the Answer Time field is invalid (that is, call was not answered)
•
Release history
Register NATC
National Call
Register NATC is a peg register which counts the number of calls to a national
number, as recorded in the billing stream. This register is pegged under the
following conditions:
field indicates a National call
Release history
411-8111-803
Standard
01.06
May 2006
Register NNT
Not answered and Normally Terminated
Register NNT is a peg register which counts the number of unanswered calls
which were normally terminated, as recorded in the billing stream. This register
is pegged under the following conditions
•
Release history
Register TCD
Total Call Duration
Register TCD tells the operator the total call duration per VCN MSC.
Call Duration is defined as the disconnect time for a given CDR minus the
answer time for the same CDR. If the disconnect time is not valid, then the
answer time is subtracted from the release time.
The call times for a partial record are only valid for the segment of the call
represented by the partial record. For this reason the call duration is counted
for all partial records.
This register is pegged on the MO, MT, or R tuple when a Mobile Originated,
Mobile Terminated, or Roaming CDR is encountered with the following
characteristics:
• Answer time is valid
•
Either Disconnect Time or Release Time is valid
Release history
Register TOTAL
Total Calls
Register TOTAL is a peg register which counts the number of times the
particular call type was encountered in the billing stream.
Release history
Register TSST
Total System Setup Time
Register TSST tells the operator the total system setup time for the CDR
category.
GSM18/UMTS04
System Setup Time is defined as difference between the channel allocation
time and the facility seizure time.
characteristics:
• Channel allocation time is valid
•
Trunk seizure time is valid
•
If the record is a partial record, it must be the last one in the series
Release history
Register TTTA
Total Time To Answer
Register TTTA tells the operator the total time to answer of the related CDR
category, given in the tuple’s info field.
Time to answer is defined as Answer Time - Trunk Seizure Time.
This register is pegged when a CDR is encountered with the following
characteristics:
For Mobile Originated records:
•
•
For Mobile Terminated records:
•
•
For Roaming records:
•
•
Release history
411-8111-803
Standard
01.06
May 2006
Register TTTD
Total Time To Disconnect
Register TTTD tells the operator the total time to disconnect when a call is
not answered, per MSC.
The time to disconnect is defined as the difference between the Disconnect
Time field and the Trunk Seizure Time for the same CDR.
characteristics:
• Disconnect time is valid
•
•
•
Answer time is invalid
Release history
OM Group: PREFIXDIAG
The PREFIXDIAG group collects data for calls when both a destination tag
and diagnostic tag matches the CDR. PREFIXDIAG measures traffic for the
diagnostic codes, destinations (dialed digits, calling numbers, called numbers,
call forwarding numbers, and the combinations of calling numbers, and one
of dialed digits, called numbers, and call forwarding numbers), and call
origination (internal/external).
The register of this group collects counts of calls whose dialed digits (calling
numbers, called numbers, call forwarding numbers, or the combination of
calling numbers, and one of dialed digits, called numbers, and call forwarding
numbers) matches to one in the Destination Tag and whose diagnostic code
matches to one in the Diagnostic Tag.
Group structure
• Key Field: Prefix group tag
•
Info Field: Diagnostic group tag
•
Number of Tuples: Open ended, one for each combination of prefix group
and diagnostic group
Register list
• TOTAL - Counts the number of occurrences of prefix groups and
diagnostic groups combination
GSM18/UMTS04
Register TOTAL
Total
Register TOTAL is a peg register that counts the number of occurrences of a
combination of diagnostic group tags and prefix group tags.
Release history
OM Group: TERMREASON
The TERMREASON group collects data for calls on trunk groups if a call has
a diagnostic code matching one in a user specified list. This group measures
the number of failed calls, broken down by reason for termination, and
classifies data by diagnostic tags.
Data from the following records is collected to determine this: mobile
originated call, incoming intra-PLMN trunk with valid outgoing trunk group,
incoming gateway call with valid outgoing trunk group, and mobile
terminated call record with valid incoming trunk group. This group collects
traffic direction (incoming or outgoing) for each trunk group.
This group contains variable number of tuples. Each tuple represents
measurement for the combination of a trunk group, a Diagnostic tag, and a
traffic direction. A Diagnostic tag defines a list of diagnostic codes. The
registers of a tuple collect counts of calls whose diagnostic codes match to
one in the Diagnostic tag.
All information in the TERMREASON group is shown in the Cct Group
Summary window of the CEM browser.
Group structure
• Key Field: ADNUM
•
Info Field: Termination Reason group tag
•
Number of Tuples: Open ended, one for each combination of termination
code group tag and trunk group discovered in the billing stream.
Datafill
Table TRKGRP defines the trunk groups which can be found in the billing
stream.
Table CLLI provides the mapping between ADNUM from the CDR and
Trunk CLLI name, which is sent in the report.
Register list
• TOTAL- The count of call termination failures on a trunk group with the
call termination reason which is matched in a list of a diagnostic tag.
411-8111-803
Standard
01.06
May 2006
OM Group: TRAFFICDEST
Anything configured through the Dialed Digits Manager will affect the
TRAFFICDEST OM group. TRAFFICDEST will be created only after there
is at least one group tag created through the Dialed Digits Manager.
This group captures measurements related to customer specified digits. These
digits are the initial digits of either dialed digits, called number, or calling
number. TRAFFICDEST measures traffic for the combination of a trunk
group, destinations (dialed digits, calling numbers, called numbers, and the
combinations of calling numbers, and one of dialed digits, and called
numbers), and traffic direction.
The registers collect counts of successful, failed, completed and noncompleted from matched calls, and accumulate time data (time to answer,
system setup time, time to disconnect, and call duration) needed for
calculating averages and percentages.
This group can be used to find usage statistics by calling number, called
number, or dialled digits. A tuple will be created for each customer supplied
number as it is discovered in the billing stream. A tuple will be created for
each combination of trunk group and study number found in the billing
records.
The TRAFFICDEST group collects data on not only A-Interface trunk but
other trunk groups as well, and it also collects time data. TRAFFICDEST
collects data for calls when a destination tag matches a CDR. Data from the
following records is collected to determine this: mobile originated call,
incoming intra-PLMN trunk with valid outgoing trunk group, incoming
gateway call with valid outgoing trunk group, and mobile terminated call.
This group will collect direction (incoming or outgoing) on each trunk group.
Note: Time information is only collected for this group when using the
default mode.
Group structure
• Key Field: Prefix group tag defined by customer
•
Info Field: ADNUM
•
Number of Tuples: Open ended, one for each combination of prefix group
tag and trunk group discovered in the billing stream
Datafill
Table TRKGRP defines the trunk groups which may be found in the billing
stream.
GSM18/UMTS04
Register list
• TYPE - Call type (Dialled Digits, Called Number, Calling Number)
•
TOTAL_ACCESS - The total of matching calls which go through a trunk
group.
•
TOTAL_ORIGIN_ANS - The total of uses of a trunk group where a call is
answered.
•
TOTAL_ORIGIN_NO_ANS - The total of uses of a trunk group where a
call is not answered.
•
•
•
•
•
•
•
TTTA - Total Time To Answer
•
•
TTTD - Total Time To Disconnect
•
•
• Average of System Setup time (ASST) =
TRAFFICDEST:TSST / (TRAFFICDEST:TOTAL_ORIGIN_ANS +
TRAFFICDEST:TOTAL_ORIGIN_NO_ANS)
•
Average of Time to Answer (ATTA) =
TRAFFICDEST:TTTA / TRAFFICDEST:TOTAL_ORIGIN_ANS
•
TRAFFICDEST:TTTD / TRAFFICDEST:TOTAL_ORIGIN_NO_ANS
•
Average of Call Duration (ACD) =
TRAFFICDEST:TCD * 10 / (TRAFFICDEST:TOTAL_ACCESS TRAFFICDEST:NAT - TRAFFICDEST:NNT)
TRAFFICDEST:TOTAL_ORIGIN_ANS and
TRAFFICDEST:TOTAL_ORIGIN_NO_ANS are used for calculating the
average data, but not for displaying.
411-8111-803
Standard
01.06
May 2006
Register AAT
• Neither the Call Forwarding Indicator, or the Proprietary Extension
Indicator is on
•
the Answer Time field is valid
•
Release history
Register ANT
Indicator is on
•
•
Release history
Register INTC
International Call
Indicator is on
•
the Nature of Address Indicator part of the Numbering Plan Identifier
Release history
GSM18/UMTS04
Register NAT
Indicator is on
•
the Answer Time field is invalid (that is, call was not answered)
•
Release history
Register NATC
National Call
Register NATC is a peg register which counts the number of times the prefix,
specified by the tuple’s info field, matched on of the number fields in the CDR
and was a nationally significant number in that context (i.e., the NPI Nature of
Address Indicator == 2). This register is pegged under the following conditions:
Indicator is on
•
Release history
Register NNT
is pegged under the following conditions:
Indicator is on
•
•
Release history
Register TOTAL
Total Matches
particular call type was encountered in the billing stream.
411-8111-803
Standard
01.06
May 2006
Release history
Register TYPE
TYPE
Register TYPE is a register which indicates the particular call type
encountered in the CDR. It is a number which is converted to either Dialled
Digits, Called Number, or Calling Number when reported.
Release history
OM Group: TRAFFICDEST2
Anything configured through the Dialed Digits Manager will affect the
TRAFFICDEST2 OM group. TRAFFICDEST2 will be created only after
there is at least one group tag created through the Dialed Digits Manager.
The TRAFFICEDEST2 group collects data for calls when a destination tag
matches a CDR. Data from the following records is collected to determine
this: mobile originated call, incoming intra-PLMN trunk with valid outgoing
trunk group, incoming gateway call with valid outgoing trunk group, and
mobile terminated call.
TRAFFICEDEST2 will collect call origination (internal or external) on each
trunk group. The registers collect the number of successful, failed, completed
and non-completed calls, and accumulate time data (time to answer, system
setup time, time to disconnect, and call duration) needed for calculating
averages and percentages.
Group structure
• Key Field: Prefix group tag defined by customer
•
Info Field: None
•
Number of Tuples: Open ended, one for each prefix group tag discovered
in the billing stream
Register list
• TYPE - Call type (Dialled Digits, Called Number, Calling Number)
•
TOTAL - Total Matches
•
•
•
•
•
GSM18/UMTS04
•
•
•
•
•
•
TRAFFICDEST2:TSST / TRAFFICDEST2:TOTAL
•
TRAFFICDEST2:TTTA / (TRAFFICDEST2:ANT +
TRAFFICDEST2:AAT)
•
TRAFFICDEST2:TTTD / (TRAFFICDEST2:NNT +
TRAFFICDEST2:NAT)
•
TRAFFICDEST2:TCD * 10 / (TRAFFICDEST2:ANT +
TRAFFICDEST2:AAT)
Register AAT
Indicator is on
•
•
Release history
Register ANT
Indicator is on
411-8111-803
Standard
01.06
May 2006
•
•
Release history
Register INTC
International Call
Indicator is on
•
Release history
Register NAT
Indicator is on
•
•
Release history
Register NATC
National Call
Indicator is on
•
Release history
GSM18/UMTS04
Register NNT
Indicator is on
•
•
Release history
Register TCD
Total Call Duration
Register TCD tells the operator the total call duration per MSC.
characteristics:
•
•
If the record has a valid Incoming Trunk Group field, the IT tuple is also
pegged
•
If the record has a valid Outgoing Trunk Group field, the OT tuple is also
pegged
Release history
Register TOTAL
Total
Register TOTAL is a peg register that counts the number of matches for a
particular call type.
411-8111-803
Standard
01.06
May 2006
Release history
Register TSST
category.
characteristics:
•
•
•
pegged
•
pegged
Release history
Register TTTA
characteristics:
• Neither the Call Forwarding Indicator or the Proprietary Extension
Indicator is on
•
Answer time is valid
•
•
GSM18/UMTS04
•
pegged
•
•
•
pegged
•
•
•
pegged
Release history
Register TTTD
characteristics:
•
•
•
pegged
•
pegged
Release history
411-8111-803
Standard
01.06
May 2006
Register TYPE
TYPE
Register TYPE is a register which indicates the particular call type
encountered in the CDR. It is a number which is converted to either Dialled
Digits, Called Number, or Calling Number when reported.
Release history
OM Group: TRAFFICDEST3
TRAFFICDEST3 OM group measures traffic for a combination of incoming
and outgoing trunk groups and destinations.
The Destination tag will contain the following information which will be input
in the Dialed Digits Manager:
• Originated number (Calling number)
•
Destination number (Dialed Digits, Called, and Call Forwarding number)
•
Incoming Trunk group (CLLI)
•
Outgoing Trunk group (CLLI)
Group structure
• Key Field: Combination of Destination tag, origination number,
destination number, incoming trunk group (CLLI) and outgoing trunk
group (CLLI).
•
Info Field: None
•
Number of Tuples: Variable, each tuple represents measurements for the
combination of incoming and outgoing trunk groups, origination and
destination numbers, and Destination Tag.
Register list
The registers of a tuple collect counts of calls whose data match to one defined
in one of the Destination tags. From matched calls, it collects counts of call
successful, failed, completed and non-completed, and accumulate time data
needed for calculating averages:
• TYPE - Call Number Type (Dialed Digits, Calling Numbers, Called
Numbers, Call Forwarding Numbers, or the combination).
•
TOTAL_ACCESS - The total of matching calls which go through a trunk
group.
•
answered.
•
GSM18/UMTS04
•
ANT - The total of Answered, Normally Terminated calls.
•
AAT - The total of Answered, Abnormally Terminated calls.
•
NNT - The total of No Answered, Normally Terminated calls.
•
NAT - The total of No Answered, Abnormally Terminated calls.
•
INTC - The total of International calls.
•
NATC - The total of National calls.
•
TTTA - Total Time To Answer.
•
TSST - Total System Setup Time.
•
TTTD - Total Time To Disconnect.
•
OSST - Total occurrences of pegging System Setup time that used to
calculate an average of System Setup Time.
•
TCD - Total Call Duration.
•
TRAFFICDEST3:TSST / (TRAFFICDEST3:TOTAL_ORIGIN_ANS +
TRAFFICDEST3:TOTAL_ORIGIN_NO_ANS)
•
TRAFFICDEST3:TTTA / TRAFFICDEST3:TOTAL_ORIGIN_ANS
•
TRAFFICDEST3:TTTD /
TRAFFICDEST3:TOTAL_ORIGIN_NO_ANS
•
TRAFFICDEST3:TCD * 10 / (TRAFFICDEST3:TOTAL_ACCESS TRAFFICDEST3:NAT - TRAFFICDEST3:NNT)
Note: TRAFFICDEST3:TOTAL_ORIGIN_ANS,
TRAFFICDEST3:TOTAL_ORIGIN_NO_ANS and OSST are used for
only calculating the average data but not for displaying.
Release history
Created for the GEM17 release.
OM Group: TRUNKIO
The TRUNKIO group measures traffic for each trunk group.
Data from the following records is collected to determine this: mobile
Originated Call, Incoming Intra-PLMN Trunk with valid outgoing trunk
411-8111-803
Standard
01.06
May 2006
group, Incoming Gateway Call with valid outgoing trunk group, and Mobile
Terminated Call.
This group collects traffic direction (incoming or outgoing) on each trunk
group instead of incoming seizure and outgoing seizure.
Group structure
Key Field: ADNUM
Info Field: Direction
Number of Tuples: Open-ended, up to one for each trunk group on the switch
Datafill
Table TRKGRP defines the set of trunk groups which may be measured by
this group.
Register list
• TOTAL_ACCESS - The total of calls which go through a trunk group or
summation with the traffic direction.
•
answered.
•
•
•
•
•
•
•
•
•
•
•
•
OSST - Total occurrences of pegging system setup time that used to
calculate an average of system setup time.
•
GSM18/UMTS04
TRUNKIO:TSST / TRUNKIO:OSST
•
TRUNKIO:TTTA / TRUNKIO:TOTAL_ORIGIN_ANS
•
TRUNKIO:TTTD / TRUNKIO:TOTAL_ORIGIN_NO_ANS
•
TRUNKIO:TCD * 10 / (TRUNKIO:TOTAL_ACCESS - TRUNKIO:NAT
- TRUNKIO:NNT)
TRUNKIO:TOTAL_ORIGIN_ANS and
TRUNKIO:TOTAL_ORIGIN_NO_ANS are used for calculating the average
data, but not for displaying.
Register AAT
•
Release history
Register ANT
•
Release history
411-8111-803
Standard
01.06
May 2006
Register INTC
International Call
Release history
Register NAT
•
Release history
Register NATC
National Call
Release history
Register NNT
•
Release history
GSM18/UMTS04
Register TCD
Total Call Duration
Register TCD tells the operator the total call duration per MSC.
characteristics:
•
•
pegged
•
pegged
Release history
Register TOTAL
Total Matches
particular trunkgroup was encountered in the billing stream.
Release history
Register TSST
category.
characteristics:
411-8111-803
Standard
01.06
May 2006
•
•
•
pegged
•
pegged
Release history
Register TTTA
characteristics:
•
•
•
pegged
•
•
•
pegged
•
•
•
pegged
GSM18/UMTS04
Release history
Register TTTD
characteristics:
•
•
•
pegged
•
pegged
Release history
411-8111-803
Standard
01.06
May 2006
3-1
CEM logs
3
This chapter identifies the logs generated by the software components of the
MSC/HLR OMC-S Element Manager system. Log reports are video screen
displays or printouts that contain information vital to the efficient operation of
the Management System.
The OMC-S/CEM system uses a log system as a central facility to collect and
display information reported by various processes. The log system records
errors or other significant operational events as they occur.
The logs provide information similar to status and activity reports. This
information identifies possible software or hardware failure, test results,
changes in state, and other events that might affect the performance.
The system automatically produces the log reports and stores them in a
directory on the OMC-S/CEM system. The OMC-S/CEM system routes the
log reports to output devices such as printers or terminals.
A Trunk option allows the customer to control whether to route all Trunk logs
to an agent or not. The default value of the trunk parameter
“suppressTrunkLog” is ON. That is, all trunk logs are initially turned off. To
turn the trunk logs on, edit the file “rdaconfig” in /mscomc/<omc-s load>/
dat (where <omc-s Load> can be OMC-S_MSC, OMC-S_HLR or OMCS_TRI). Change the line suppressTrunkLog=ON to
suppressTrunkLog=OFF. Restart the FmPm application from sdmmtce.
The OMC-S does not receive logs if the OM report is activated from the
switch through the OMPRT table. That is, during the OM report dumping, no
activity from the switch is notified on the OMC-S platform since OMs take
priority and only when the OMs have completed their run to logutil, is the
element manager updated.
The operator can use the log reports to determine the efficiency operation of
the OMC-S/CEM system.
GSM18/UMTS04
3-2 CEM logs
Log information can:
• indicate changes in operational status or activity.
•
notify craftsperson that hardware or software faults have occurred.
•
indicate changes of state or any significant change that may effect the
performance of the OMC-S Element Manager.
•
indicates events associated with CEM user authorization.
How logs are defined
3
The Management System uses a data structure known as Integrated Event
Management (IEM) to define the different fields in an output report. Events,
as defined by IEM, are changes that affect the performance and service of the
system. The changes must be brought to the attention of the craftsperson. The
OMC-S log system fills this role by generating the appropriate logs.
How events are categorized
The output report system categorizes OMC-S events by class. The five classes
of events and the log number ranges assigned to the events are shown in Table
3-1.
Table 3-1
Event class definitions
Event Class
Number Range for
logs
Definition
Trouble
300 to 399
Indicates conditions that are departures from
normal within the VCN MSC.
Service Summary
400 to 499
Provides information concerning miscellaneous
events.
State Change
500 to 599
Indicates a state change of the reporting entity.
Information
600 to 899
Provides information related to system
performance.
Expert
900 to 999
Reserved for Nortel use.
Note: For this release, the OMC-S/CEM system only uses trouble and
informational logs.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-3
Log example
3
An output report (or log) contains two areas of information: a log header and
an identification area.
Figure 3-1
Example log
Header
Aug 1 18:53:47 crchh891 syslog: TMN303 MAJOR TBL Communication error
Status: Trouble raised
Location: Agent root(801)
Trouble: Communication error.
Action: Check for server process.
Identification
Log header
The top line of the log is known as the log header. Each output report, or log,
has a standard header that contains the following information:
• month, day, and time the log was generated
•
the node where the log occurred
•
log name and number
•
the severity of the log
•
the event type being reported
Log date and time
The system reports the date of the log in a month/day format. Using the 24hour clock, the system displays the time of the log as hours, minutes and
seconds.
Log name and number
The example in Figure 3-1 shows that the log name consists of a prefix and a
number. The “TMN” prefix indicates that the log is from the Management
System application. The “303” number indicates that the log is a trouble log
because it falls within the 300-399 number range.
Log severity and event type
The three severity levels for a log are Critical, Major, Minor or NONE. The
system assigns trouble logs with a major or minor severity level; the NONE
severity level is for informational logs.
Identification area
This area provides information about the location, description, and cause of
the problem. The log report may identify an action that can be taken by the
GSM18/UMTS04
3-4 CEM logs
user to correct the problem. For descriptions of the log report fields, refer to
Table 3-5.
Logs shown in this chapter
3
OMC-S/CEM system logs
The OMC-S/CEM system produces the logs in Table 3-2. “Informational”
type logs are customer logs and “trouble” type logs are maintenance logs.
Table 3-2
OMC-S/CEM system log summary
Log number
Location
Log type
Log name
OSA302
OMCS Security &
Administration
Minor Trouble
Invalid userid and password
OSA303
OMCS Security &
Administration
Major Trouble
Exceed login retries
OSA304
OMCS Security &
Administration
Major Trouble
Inaccessible ldap.config file
OSA305
OMCS Security &
Administration
Major Trouble
Ldap server Connection error
OSA306
OMCS Security &
Administration
Major Trouble
User Access Violation- Command
not Permitted
OSA307
OMCS Security &
Administration
Minor Trouble
Password expired. Need to change
password
OSA308
OMCS Security &
Administration
Minor Trouble
Change Password Failure
OSA602
OMCS Security &
Administration
Informational
Login Success
OSA603
OMCS Security &
Administration
Informational
Change Password Success
OSA604
OMCS Security &
Administration
Informational
Logout success
TMN301
dmsDataServer
Major Trouble
System error
TMN301
BACKUP System
Minor Trouble
Application error
—sheet 1 of 5—
411-8111-803
Standard
01.06
May 2006
CEM logs 3-5
Table 3-2
Log number
Location
Log type
Log name
TMN302
PM Archive
Major Trouble
System error
RD Agent
Major or
Critical Trouble
System error
CM Normalizer
Critical Trouble
System error
Log Normalizer
Critical Trouble
System error
RD Agent
Minor Trouble
Communication error
PM Agent
Major Trouble
Communication error
Normalization Layer
Critical Trouble
Communication error
CM Normalizer
Major Trouble
Communication error
CM Normalizer
Major Trouble
Connection error
FM Agent
Critical Trouble
Connection error
PM Agent
Critical Trouble
Connection error
RD Agent
Critical Trouble
Connection error
Log Normalizer
Major Trouble
Connection error
PM Archive
Major Trouble
Message format error
Normalization Layer
Major Trouble
PM Agent
Critical Trouble
Log Normalizer
Major Trouble
dmsDataServer
Major Trouble
Software error
RD Agent (RDA)
Major Trouble
Software error
PM Agent
Critical or
Major Trouble
Software error
TMN303
TMN304
TMN305
TMN306
—sheet 2 of 5—
GSM18/UMTS04
3-6 CEM logs
Table 3-2
Log number
Location
Log type
Log name
TMN307
dmsDataServer
Minor Trouble
Processing error
PM Archive
Minor Trouble
Processing error
PM Agent
Critical or
Minor Trouble
Processing error
FM Agent
Critical or
Minor Trouble
Processing error
RD Agent
Critical or
Minor Trouble
Processing error
Log Normalizer
Critical Trouble
Processing error
CM Normalizer
Critical Trouble
Processing error
TMN308
Normalization Layer
Minor Trouble
Correlation error
TMN309
Normalization Layer
Critical Trouble
Data server error
TMN310
PM Archive
Minor Trouble
Arithmetic overflow
Normalization Layer
Minor Trouble
Arithmetic overflow
dmsDataServer
Critical Trouble
Fatal error
PM Archive
Critical Trouble
Fatal error
Web Agent
Critical Trouble
Fatal error
TMN312
CM Normalizer
Critical Trouble
Process terminated
TMN313
CM Normalizer
Minor Trouble
State error
TMN314
Billing collector
Minor Trouble
FTAM connection down
TMN317
Log Normalizer
Minor Trouble
SIM Swapover Failure
TMN311
—sheet 3 of 5—
411-8111-803
Standard
01.06
May 2006
CEM logs 3-7
Table 3-2
Log number
Location
Log type
Log name
TMN318
PM Agent
Minor Trouble
Threshold crossed
Threshold Manager
Critical, Major
or Minor
Trouble
Threshold crossed
Threshold Manager
Critical, Major
or Minor
Trouble
Data Missing
TMN319
RD Agent
Minor Trouble
Resource Discovery Started
TMN341
Object Manager
Warning
LogNormDown
TMN342
Object Manager
Warning
CMNormDown
TMN343
Object Manager
Warning
OMNormDown
TMN600
CM Normalizer
Informational
TMN OK
Element Browser
Informational
TMN Initial state mapping
Log Normalizer
Informational
TMN OK
Web Agent
Informational
Information only
TMN601
PM Archive
Informational
File I/O info
TMN603
PM Agent
Informational
Connection status
CM Normalizer
Informational
Connection status
Log Normalizer
Informational
Connection status
dmsDataServer
Informational
Application status
BACKUP System
Informational
Application status
PM Archive
Informational
Application status
CM Normalizer
Informational
Application status
TMN605
RPC Server
Informational
Core Restart
TMN610
OMCS Adapter
Critical Trouble
Alarms Option
TMN614
Billing collector
Informational
FTAM connection up
TMN604
—sheet 4 of 5—
GSM18/UMTS04
3-8 CEM logs
Table 3-2
Log number
Location
Log type
Log name
TMN618
PM Agent
Informational
Threshold cleared
TMN619
RD Agent
Informational
Resource Discovery Completed
—sheet 5 of 5—
CEM logs generated by DS SunMC modules
The following table lists the logs generated by DS Sun MC modules at the
CEM. These alarms are raised in the Core Element Manager (CEM) when
error conditions are determined by modules running within the Sun MC agent
on the Data Server (DS). The association between the log number and the
specific module is given.There may be textual changes in the log as presented
at the CEM but their meaning remains unchanged. Multiple alarm conditions
at the DS generate only a single log at the CEM. It is assumed that access to
Sun MC will provide the operator with more detailed information concerning
the condition.
Note: Not all module alarms are mapped in the CEM. The mapping is
determined by the alarmmap-hlrds module. The content of this module
can be viewed from a Sun MC console and will mirror the content of
Table 3-3.
Table 3-3
Logs raised on the CEM by modules running within a DS Sun MC agent
Log number
Associated DS Sun
MC module
General description
CEMDS100
mialarms-hlrds
The module retrieves Management Information (MI) that
have been categorized by DS applications to be alarm
conditions.
The CEMDS100 alarm is raised if the Sun MC module
fails to retrieve the MI alarm data from the required DS
application.
Logs in the range 101-107 map to specific areas of
HLRPM functionality on the DS. These categories are
unchanged from the GSM17 release.
CEMDS101
mialarms-hlrds
Covers all Provisioning Routing MI alarms
CEMDS102
mialarms-hlrds
SLR Provisioning MI alarms
—sheet 1 of 3—
411-8111-803
Standard
01.06
May 2006
CEM logs 3-9
Table 3-3
Log number
Associated DS Sun
MC module
General description
CEMDS103
mialarms-hlrds
Bulk Service Provisioning (BSP) MI alarms
CEMDS104
mialarms-hlrds
Provisioning Data Links related MI alarms
CEMDS105
mialarms-hlrds
Relates to all configuration alarms raised against the
HLRPM.
CEMDS106
mialarms-hlrds
MSP Audit related MI alarms
CEMDS107
mialarms-hlrds
SLR Audit related MI alarms
CEMDS199
mialarms-hlrds
This Log will be displayed for an MI alarm that is raised
that does not fit the seven categories that give the Logs
as described above
CEMDS200
orastat2-hlrds
The Oracle statistics module monitor basic database
parameters that indicate it is functioning correctly. These
parameters include the user and table space counts
which are expected to be constant during normal
database operation. Alarms against all of the parameters
are mapped to the single CEMDS200 log.
CEMDS201
orastrm2-hlrds
The Oracle streams module monitors the replication of
database between mated DSs. Monitoring includes the
capture and apply queue sizes, apply error count and
apply error count. All alarms raised by the module map to
the single CEMDS201 alarm.
CEMDS202
procview2-hlrds
HLRPM processes are monitored by this module. If these
processes are not in their expected normal RUNNING
states, for example in TROUBLE or STOPPED, then this
single log will be displayed at the CEM
CEMDS203
kernel-reader
This Sun-provided module monitors various system
statistics. The various alarms generated by the module
running on the DS are mapped to this single log at the
CEM
CEMDS204
agent-stats
This Sun-provided module monitors the DSs Sun MC
agent statistics. Any alarms generated by this module
are mapped to this single log at the CEM
—sheet 2 of 3—
GSM18/UMTS04
3-10 CEM logs
Table 3-3
Log number
Associated DS Sun
MC module
General description
CEMDS205
process-table+oracle
The various Unix sub-processes associated with the
Oracle instance running on the DS are monitored by this
module. If the required number of each sub-processes
are not running then this log is raised at the CEM
CEMDS206
partitionsize-hlrds
The used capacity of each disk partition on the DS is
monitored and the single log is displayed at the CEM
when these partitions near capacity.
CEMDS207
oradir2-hlrds
Monitors the size of the Oracle database files (*.dbf) on
disk. Any alarm generated by this module at the DS will
map to this single log at the CEM.
CEMDS208
Config-Reader4unt
This Sun-provided module monitors various hardware
configuration information for the DS platform. This
information includes CPU, memory, disk and tape
devices, I/O controllers and temperature sensing. This
single log will be raised on the CEM when any alarm
condition is detected by this module
CEMDS209
raidsys-hlrds
The module will monitor the status the RAID array on the
DS platform. Monitoring is categorized into four areas;
disk, controller, power supply and I/O statistics. These
areas map to this single Log at the CEM
CEMDS210
procview2-hlrds
Failed to determine the provisioning state of the DS.
CEMDS301
procview2-hlrds
CEMDS302
orastat2-hlrds
These logs indicate that the module has failed to retrieve
the required data from the DS application. As such no
other alarm from this module can be considered as valid.
CEMDS303
orastrm2-hlrds
CEMDS600
Any module
If a specific DS alarm mapping for the CEM is not
provided then this default Log will be displayed at the
CEM
—sheet 3 of 3—
Note: See Local Applications/DS MI Active Alarms module on the Sun
MC for more information on CEMDS logs. For more information
concerning usage, please refer to NTP 411-2831-330 GSM / UMTS
HLR200 Data Server Operations and User Guide.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-11
CEM logs generated by mated pair monitor
The logs are generated by Mated Pair Monitor together with associated
alarms raising/lowering. These logs will be raised against the HLRStby
container on the two HLR nodes of the mated-pair when attributes related to
the mated pair indicate it is in an unsupported or misconfigured state. The
alarms listed below will only be raised against the HLRs when the Mated Pair
Monitor is configured to monitor them. If the mated-pair is removed from the
monitor, the alarms will be cleared.
Table 3-4
Logs raised by the mated pair monitor
Log number
Log name
Problem indicated
MON001
Autocutover Mode
Trouble
Raised when the Autocutover Mode of the two HLRs
making up the mated-pair is in an unsupported state
MON002
Autocutover On Trouble
Raised when the Autocutover On of the two HLRs
MON003
Autocutover State
Trouble
Raised when the Autocutover State of the two HLRs
MON004
Autocutover On/State
Trouble
Raised under certain combinations of Autocutover On
and Autocutover State
MON005
Standby On Trouble
Raised when the Standby On attributes of the two HLRs
MON006
Standby Mode Trouble
Raised when the Standby Mode of the two HLRs
MON007
HLR Mate Number
Trouble
Raised when the HLR number is not datafilled for the
mate
MON008
Mate Trouble
Raised when the mate HLR has been disconnected
from the CEM for a period of time
Note: Alarms MON001 - MON007 will be raised after the problem
caused the alarm exists for more than 1 minute. Alarm MON008 will be
raised after the problem caused the alarm exists for more than 90 seconds.
GSM18/UMTS04
3-12 CEM logs
Field descriptions
3
Table 3-5 provides descriptions of different fields that are displayed in logs
produced for the OMC-S/CEM system.
Table 3-5
OMC-S/CEM system log field descriptions
Field
Description
Action
Suggests a corrective action.
Description
Describes the nature of the problem.
Invocation Time
The time from which the new IMSI becomes active (only applies if the
option is set to USER).
Location
Identifies the software entity, user, and process ID that generated the
log.
NEW IMSI
The new or replacement International Mobile Subscriber Identity (IMSI)
OLD IMSI
The old or to be replaced IMSI.
Option
The SIM replacement option type.
Primary MSISDN
Identifies the primary MSISDN of the user.
Status
Identifies the status of the log:
•
Trouble Raised
•
Trouble Cleared
•
Trouble Continued
Table 3-6
Mated pair monitor log field descriptions
Field
Optionality
Type
Size
Values
Description
State
Mandatory,
Variable
Character
string
6-7
raised
Trouble state
cleared
Name1
Mandatory,
Variable
Character
string
1-30
—sheet 1 of 3—
411-8111-803
Standard
01.06
May 2006
Slice alias of the first
HLR in the mated pair
CEM logs 3-13
Table 3-6
Field
Optionality
Type
Size
Values
Description
Aco Mode1
Mandatory,
Variable
Character
string
6-7
monitor
AcoMode attribute
value on the first HLR
in the mated pair
active
Name2
Mandatory,
Variable
Character
string
1-30
Aco Mode2
Mandatory,
Variable
Character
string
6-7
Slice alias of the
second HLR in the
mated pair
monitor
active
Aco On1
Mandatory,
Variable
Character
string
2-3
yes
no
Aco On2
Mandatory,
Variable
Character
string
2-3
yes
no
Aco State1
Mandatory,
Variable
Character
string
10-15
aco_off
sls_cycling
AcoMode attribute
value on the second
AcoOn attribute value
on the first HLR in the
mated pair
AcoOn attribute value
on the second HLR in
the mated pair
AcoState attribute
in the mated pair
sls_evaluation
hrtbeat_sending
Aco State2
Mandatory,
Variable
Character
string
10-15
aco_off
sls_cycling
AcoState attribute
value on the second
sls_evaluation
hrtbeat_sending
Autocutover
flag
Optional,
Variable
Character
string
7-15
CUTOVER
NO CUTOVER
Sby On1
Mandatory,
Variable
Character
string
4-5
false
true
Indicates if cutover is
present on at least
one of the mated
HLRs
SbyOn attribute value
on the first HLR in the
mated pair
—sheet 2 of 3—
GSM18/UMTS04
3-14 CEM logs
Table 3-6
Field
Optionality
Type
Size
Values
Description
Sby On2
Mandatory,
Variable
Character
string
4-5
false
SbyOn attribute value
on the second HLR in
the mated pair
true
Sby Mode1
Mandatory,
Variable
Character
string
6-12
active
outofservice
SbyMode attribute
in the mated pair
standalone
Sby Mode2
Mandatory,
Variable
Character
string
6-12
active
outofservice
SbyMode attribute
value on the second
standalone
Validity flag
Mandatory,
Variable
Character
string
6-7
valid
invalid
Reason
Mandatory,
Variable
Character
string
10-40
resource
discovery in
progress
Flag shows if the
HLR’s
MateHLRNumber
attribute is datafilled
correctly
Reason of the trouble
generation
in service
—sheet 3 of 3—
CEMDS100
3
Alarm type:
MI Alarms Collection Unavailable
Severity:
Critical
SunMC module:
Local Applications/MI Alarms (also known as mialarms+all_alarms)
411-8111-803
Standard
01.06
May 2006
CEM logs 3-15
Explanation:
This alarm is raised when there is trouble with MI collection on the Data
Server node. This alarm can be viewed within the Sun MC console. It is part
of the ‘DS Active MI alarms’ module.
The reason may be one of the following:
• mireport is not available in the correct directory.
•
mihub is not running.
•
Sun MC agent must have permissions to access and execute an instance of
mireport.
Associated Data Server log:
None
CEMDS101
3
Alarm type:
Provisioning Routing MI Alarms
Alarm name:
.hlr-pm.provisioning_routing.<hlr>.connection_alarm
Severity:
User application dependent, normally Major.
SunMC module:
Explanation:
This alarm is raised when there is a connection problem between the HLRPM and the HLR.
• Connection attempt failed.
•
Connection lost.
•
Encryption key mismatch.
•
HLR ID mismatch.
•
Handshake not received.
•
Initial message was not a handshake.
GSM18/UMTS04
3-16 CEM logs
GHPM346
CEMDS102
3
Alarm type:
SLR Provisioning MI Alarms - CEMDS102
Alarm name:
.hlr-pm.slr_management.provisioning.db_connection_alarm
Severity:
Application dependent, normally Critical.
SunMC module:
Explanation:
This alarm is raised when a component of the dataserver, identified by the MI
path, does not have a connection to the Dataserver database.
• A connection cannot be made for the first time.
•
An open connection is dropped due to an internal database error, no
response is received for a message sent to the database or the database
connection managing application has an internal error.
GHPM342
Alarm name:
.hlr-pm.slr_management.provisioning.no_slr_connectivity_alarm
Severity:
User application dependent, normally Critical.
Explanation:
This alarm is raised when the Provisioning Manager looses connections to all
the configured SLRs.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-17
GHPM356
Alarm name:
.hlr-pm.slr_management.provisioning.hlrid_config.db_connection_alarm
Severity:
Explanation:
path, does not have a connection to the Dataserver database.
•
An opened connection is dropped due to an internal database error, no
GHPM342
Alarm name:
.hlrpm.slr_management.provisioning.hlrid_config.hlrid_inconsistency_alarm
Severity:
Explanation:
This alarm is raised when an inconsistency is detected between the Dataserver
user config file and the dataserver database that may be causing a loss of
service for subscribers.
• A subscriber mapping stored in the dataserver database is using a HLR ID
that is not present in the user config file.
•
A HLRID exists in the dataserver database but does not exist in user
configuration
GSM18/UMTS04
3-18 CEM logs
GHPM349
Alarm name:
.hlr-pm.slr_management.provisioning.<slr>.slr_recovery_alarm
Severity:
Explanation:
This alarm is raised when the database mapping recovery queue's size reaches
75%. This alarm is also raised when log reaches 90%.
GHPM345
Alarm name:
.hlr-pm.slr_management.provisioning.<slr>.slr_recovery_needed_alarm
Severity:
Explanation:
This alarm is raised in the following circumstances:
• The mapping recovery queue for an SLR has filled, making automatic
recovery impossible.
•
The SLR returns critical errors on attempt to process a request.
GHPM344
Alarm name:
.hlr-pm.slr_management.provisioning.<slr>.both_connections_lost_alarm
Severity:
Explanation:
This alarm is raised when both connections to an SLR are lost.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-19
GHPM343
CEMDS103
3
Alarm type:
BSP Source MI Alarms
Alarm name:
.hlr-pm.bulk_provisioning.sources.<sourcename>.file_transfer_alarm
Severity:
SunMC module:
Explanation:
This alarm indicates that the HLR-PM is unable to transfer a file belonging to
the stated source, for the stated reason. Failure can occur during transfer of
the input file into the HLR-PM, or transfer of the results or rejected file. This
alarm requires operator action to clear it, before the HLR-PM processing of
the stated source can continue.
The reason why the HLR-PM failed to transfer the file is one of the following:
• Cannot access Input directory.
•
Cannot access input file.
•
Cannot read from input file.
•
Cannot access transfer directory.
•
Cannot access output file in transfer directory.
•
Cannot write to output file in transfer directory.
•
Cannot move file to output directory.
•
Cannot connect to IP address.
•
Cannot logon to FTP server.
•
FTP internal error.
•
Cannot access local file.
•
Cannot read from local file.
•
Cannot write to local file.
GSM18/UMTS04
3-20 CEM logs
GHPM319
Alarm name:
.hlr-pm.bulk_provisioning.sources.<sourcename>.encryption_alarm
Severity:
Explanation:
This alarm indicates that the HLR-PM is unable to decrypt an input file or
encrypt an output file, for the source stated. This alarm requires operator
action to clear it, before the HLR-PM processing of the stated source can
continue.
The reason why the HLR-PM failed to encrypt or decrypt a file is one of the
following:
• Filter not present.
•
Filter does not have the correct permissions.
•
Filter failed with exit status.
•
Filter terminated by a signal.
•
Filter stopped by a signal.
•
Internal failure in system call.
GHPM321
Alarm name:
.hlr-pm.bulk_provisioning.sources.<sourcename>.source_recovery_alarm
Severity:
Explanation:
This alarm indicates the HLR-PM is unable to read or write to the recovery
file. This alarm requires operator action to clear it, before the HLR-PM
processing of the files across all sources can continue.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-21
The reason why the HLR-PM has a recovery problem is one of the following:
• Cannot access Recovery directory.
•
Cannot access recovery file.
•
Cannot write to recovery file.
GHPM322
Alarm name:
.hlr-pm.bulk_provisioning.sources.<sourcename>.polling_recovery_alarm
Severity:
Explanation:
The reason why the HLR-PM has a recovery problem is one of the following:
• Cannot access Recovery directory.
•
Cannot access recovery file.
•
Cannot write to recovery file.
GHPM322
Alarm name:
.hlr-pm.bulk_provisioning.sources.<sourcename>.polling_alarm
Severity:
Explanation:
GSM18/UMTS04
3-22 CEM logs
The reason why the HLR-PM failed to poll the input directory is one of the
following:
• Failed to get modification time on the input directory.
•
Failed to open the input directory.
•
Failed to read time for input file.
•
Failed to close the input directory.
GHPM323
CEMDS104
3
Alarm type:
Links MI Alarms
Alarm name:
.hlr-pm.links.<link_name>.link_problem_alarm
Severity:
SunMC module:
Explanation:
This alarm is raised when there is trouble with the link.
• A link which was in-service goes out-of-service.
•
A link cannot be brought in-service for the first time.
GHPM315
CEMDS105
3
Alarm type:
Configuration MI Alarms
Alarm name:
.hlr-pm.configuration.no_features_enabled_alarm
411-8111-803
Standard
01.06
May 2006
CEM logs 3-23
Severity:
User application dependent, normally Minor.
SunMC module:
Explanation:
This alarm is raised whenever the HLR-PM current user configuration
'features' are disabled.
'Features' are defined as the following areas of functionality:
• Provisioning Gateway
•
BSP Provisioning
•
MSP Data Links
•
Remote Data Server
GHPM303
Alarm name:
.hlr-pm.configuration.invalid_config_alarm
Severity:
Explanation:
This alarm is raised when the HLR-PM detects that the persistent copy of its
user configuration data file is invalid.
GHPM325
CEMDS106
3
Alarm type:
MSP Audit MI Alarms
Alarm name:
.hlr-pm.msp_audit.audit_file_problem_alarm
GSM18/UMTS04
3-24 CEM logs
Severity:
SunMC module:
Explanation:
This alarm is raised whenever an audit file cannot be created or cannot be
written to.
The reason that the MSP Message Audit file could not be created is one of the
following:
• Error creating new MSP Message audit file.
•
Error writing to MSP Message audit file.
GHPM333
CEMDS107
3
Alarm type:
SLR Audit MI Alarms
Alarm name:
.hlr-pm.slr_management.slr_audit.db_connection_alarm
Severity:
SunMC module:
Explanation:
path, does not have a connection to the Dataserver database
•
411-8111-803
An opened connection is dropped due to an internal database error, no
Standard
01.06
May 2006
CEM logs 3-25
GHPM342
Alarm name:
.hlr-pm.slr_management.slr_audit.audit_file_problem_alarm
Severity:
Explanation:
This alarm is raised whenever an slr audit file cannot be created or cannot be
written to.
The reason that the SLR Audit could not be created may be one of the following:
• Error creating new SLR audit file.
•
Error writing to SLR audit file.
GHPM355
CEMDS199
3
Alarm type:
Management Information (MI) Alarms
Alarm name:
.hlr-pm.<any sub-path>
Severity:
User application dependent, normally major or critical.
SunMC module:
Explanation:
This general MI alarm is raised for components that are not specifically
covered by the logs in the range CEMDS101 to CEMDS107 inclusive.
• Depends upon the exact MI against which the alarm is raised
None
GSM18/UMTS04
3-26 CEM logs
CEMDS200
3
Alarm type:
Database_Alarm
Severity:
Critical
SunMC module:
Oracle statistics (also known as orastat2-hlrds)
Explanation:
This module provides a summary of the key operational statistics for the
correct functional behaviour of the DS database (Oracle).
This alarm is raised when a either a serious problem or a worrying condition
has been detected with the DS database.
• Essential configuration within the database has been altered.
•
O/S files on which the database is dependant have been altered or
removed.
•
Internal errors have been detected.
•
The monitored Oracle parameters do not match the specified thresholds.
None
CEMDS201
3
Alarm type:
Replication Alarm for database
Severity:
Major/Critical
SunMC module:
Oracle streams statistics (also known as orastrm2-hlrds)
411-8111-803
Standard
01.06
May 2006
CEM logs 3-27
Explanation:
This module provides the statistics related to the replication of the DS
database (Oracle). This alarm is raised when replication between the Data
Server databases has either stopped or one site lags the other by too many
transactions.
• Errors have been encountered during application of received transactions.
•
Errors have been encountered during propagation of transactions.
•
Replication has stopped or aborted.
•
Replication is suffering from severe lag (i.e. the remote database is far
behind).
•
The monitored Oracle replication parameters do not match the required
alarm thresholds.
None
CEMDS202
3
Alarm type:
Process States alarms
Severity:
Minor/Critical
SunMC module:
Local Applications/Data Server Process States (also known as procview2hlrds)
Explanation:
The procview2-hlrds module provides an operational view of the DS
processes that have been registered with the process control system manager
(dsappctrl).
The module provides a read-only view of the processes states and
management of these processes must be carried out by some alternate means
(e.g. a telnet session).
The module raises Critical and Minor alarms. Critical for TROUBLE or
FAILED which are unexpected error states. Minor for STOPPED which could
be correct operation (the operator can stop a process by design) but is flagged
GSM18/UMTS04
3-28 CEM logs
to indicate that the condition is not really meant to persist for any length of
time i.e. its there as a reminder.
The alarm thresholds for the managed properties for this module are
initialized to values determined by Nortel. While these thresholds may be
modified by the user, it is recommended that they are left unchanged unless
directed by Nortel Support.
• If an alarm condition is met, the corresponding alarm is raised.
PCSM310, PCSM311
CEMDS203
3
Alarm type:
kernel-reader alarms
Severity:
Minor/Major/Critical
SunMC module:
Operating System/Kernel Reader (also known as kernel-reader)
Explanation:
Kernel-reader module monitors the Operating System on the Data Server.
• User statistics
411-8111-803
•
System Load statistics
•
Disk statistics
•
Filesystem statistics
•
CPU statistics
•
Memory usage statistics
•
Swap statistics
•
Streams statistics
•
I/O Error statistics
•
Kernel Memory Allocation
•
Software Rules
Standard
01.06
May 2006
CEM logs 3-29
None
CEMDS204
3
Alarm type:
SunMC Agent alarms
Severity:
SunMC module:
Local Applications/Agent Statistics (also known as agent-stats)
Explanation:
Agent-stats module monitors the SunMC Agent.
• Object Statistics
•
Commands Executed
•
Transactions Performed
•
Sun Management Center Process Statistics
•
Sun Management Center Total Process Statistics
None
CEMDS205
3
Alarm type:
Oracle Process alarms
Severity:
Alarms are all critical if process count <1
SunMC module:
Local Applications/Process monitoring [Oracle processes] (also known as
process-table)
GSM18/UMTS04
3-30 CEM logs
Explanation:
Process-table module provides an operational view of the oracle processes.
• Oracle Process Problem.
•
SunMC Process Monitoring (for oracle processes) outside limits.
None
CEMDS206
3
Alarm type:
Partition alarms
Severity:
Minor/Major/Critical Minor/Major/Critical are set at 85, 90 and 95% usage
respectively
SunMC module:
Local Applications/Partition Size (also known as partitionsize)
Explanation:
Partitionsize module provides monitoring of the partitions of the DS platform.
initialized to values determined by Nortel.
While these thresholds may be modified by the user, it is recommended that
they are left unchanged unless directed by Nortel Support.
• Partition Size module detects that a partition's capacity exceeded the set
threshold.
•
Alarm action for /var partition: The /var partition, which contains the
current and daily archived system log files, has an alarm action that is
invoked when the Error condition is detected. This action will remove the
oldest daily logs in an effort to increase the quantity of free space with the
aim of maintaining current logging at the expense of archived log data.
None
411-8111-803
Standard
01.06
May 2006
CEM logs 3-31
CEMDS207
3
Alarm type:
Oracle Directory alarms
Severity:
SunMC module:
Local Applications/Oracle Directory (also known as oradir2-hlrds)
Explanation:
Oradir2-hlrds module provides the means to view the content of a single
directory that match a specific file pattern. The directory and file pattern
match may be modified while the module is running if required however this
should not be necessary unless directed by Nortel Support.
initialized to values determined by Nortel. While these thresholds may be
modified by the user, it is recommended that they are left unchanged unless
directed by Nortel Support. Alarm thresholds may be set on the 'Size (bytes)'
data in the Directory Content table.
• Oracle Directory too large.
•
Oracle dbf (database file) file too large.
None
CEMDS208
3
Alarm type:
Hardware Problem alarms
Severity:
SunMC module:
Hardware/Config Reader (also known as Config-Reader4unt)
Explanation:
Config-Reader4unt module monitors the DS Hardware.
GSM18/UMTS04
3-32 CEM logs
• DS Hardware Problem. (System, CPU Units, Power Supply, SIMMS, Fan
etc.)
None
CEMDS209
3
Alarm type:
RAID alarms
Severity:
SunMC module:
Local Applications/RAID system (also known as raidsys-hlrds)
Explanation:
Raidsys-hlrds module provides monitoring of the RAID sub-system on the
DS.
• Errors in the logical drives
•
Errors in logical disks
•
Controller state or log messages
•
Power supply faults
•
Soft, hard and transport errors1
None
CEMDS210
3
Alarm type:
Severity:
Critical
411-8111-803
Standard
01.06
May 2006
CEM logs 3-33
SunMC module:
Explanation:
Procview2-hlrds module retrieves the Provisioning State for the Data Server.
If the data retrieval fails for any reason then this alarm is raised.
• The MI client mireport is not installed
•
mireport can not be executed
None
CEMDS301
3
Alarm type:
Severity:
Critical
SunMC module:
Explanation:
Procview2-hlrds module provides an operational view of the DS processes
that have been registered with the process control system manager
(dsappctrl).
This alarm is raised if the module can not determine these processes states.
• The module fails to execute its data acquisition correctly
•
If the application controller client dsappctrl has not been installed
•
dsappctrl can not be executed by the Sun MC monitoring agent
None
GSM18/UMTS04
3-34 CEM logs
CEMDS302
3
Alarm type:
Oracle statistics alarms
Severity:
Critical
SunMC module:
Local Applications/Oracle statistics (also known as orastat2-hlrds)
Explanation:
orastat2-hlrds module provides summary of the key operational statistics for
the correct functional behaviour of the DS database (Oracle). This alarm is
raised when the method to determine these statistics fails such that the data
available.
• Failure of the Sun MC monitoring agent data acquisition
•
If the Oracle sqlplus tool has not been installed
•
sqlplus can not be executed by the Sun MC monitoring agent
None
CEMDS303
3
Alarm type:
Oracle streams statistics alarms
Severity:
Critical
SunMC module:
Local Applications/Oracle streams statistics (also known as orastrm2-hlrds)
Explanation:
orastrm2-hlrds module provides the statistics related to the replication of the
DS database (Oracle). This alarm is raised when the monitoring mechanism
has failed so that these attributes can not be retrieved.
• Failure of the Sun MC monitoring agent data acquisition
411-8111-803
Standard
01.06
May 2006
CEM logs 3-35
•
If the Oracle sqlplus tool has not been installed
•
sqlplus can not be executed by the Sun MC monitoring agent
None
CEMDS600
3
Alarm type:
General Data Server alarm
Severity:
Critical
SunMC module:
This alarm may be associated with any module on the DS and is raised when
a more specific alarm is not applicable.
Explanation:
This alarm is associated with any alarm not covered by any of the other
specific alarms raised on the DS.
• Any alarm not logged with a specific CEM log
None
MON001
3
Name
Autocutover Mode Trouble
Example
MON001 Monitor : Autocutover mode trouble raised:
AcoMode[hlr1]=active ; AcoMode[hlr2]=monitor
MON001 Monitor : Autocutover mode trouble cleared:
AcoMode[hlr1]=active ; AcoMode[hlr2]=active
Overview
This alarm is raised by the Mated Pair Monitor. The MON001 alarm will be
raised based on the Autocutover Mode (AcoMode) of this HLR combined
GSM18/UMTS04
3-36 CEM logs
with the Autocutover Mode of its designated mate. If this combination
indicates that the mated-pair has been misconfigured, the alarm is raised. It
will be lowered when the configuration is changed so that the combined
AcoMode values indicate a properly configured mated-pair.
Format
MON001 Monitor : Autocutover mode trouble <State>:
AcoMode[<Name1>]=<Aco Mode1> ; AcoMode[<Name2>]=<Aco Mode2>
Action to be taken
If the two HLRs mentioned in the log are not a designated mated-pair, the
Mated Pair monitor may be configured incorrectly. Please remove the invalid
mated pair using the configCEMS tool.
If the HLRs are a designated mated-pair, the Autocutover Mode, which is
configured on each HLR in the GHLRPARM table is in an invalid combined
state for a properly operating mated-pair.
MON002
3
Name
Autocutover On Trouble
Example
MON002 MONITOR : Autocutover on trouble raised:
AcoOn[hlr1]=yes ; AcoOn[hlr2]=no
MON002 MONITOR : Autocutover on trouble cleared:
AcoOn[hlr1]=yes ; AcoOn[hlr2]=yes
Overview
raised based on the Autocutover On (AcoOn) of this HLR combined with the
Autocutover On of its designated mate. If this combination indicates that the
mated-pair has been misconfigured, the alarm is raised. It will be lowered
when the configuration is changed so that the combined AcoOn values
indicate a properly configured mated-pair.
Format
MON002 MONITOR : Autocutover on trouble <State>:
AcoOn[<Name1>]=<Aco On1> ; AcoOn[<Name2>]=<Aco On2>
Action to be taken
411-8111-803
Standard
01.06
May 2006
CEM logs 3-37
If the HLRs are a designated mated-pair, the Autocutover On, which is
MON003
3
Name
Autocutover State Trouble
Example
MON003 MONITOR : Autocutover state trouble raised:
AcoState[hlr1]=sls_evaluation ; AcoState[hlr2]=sls_evaluation
; NO CUTOVER
MON003 MONITOR : Autocutover on/state trouble cleared:
AcoState[hlr1]=sls_evaluation ; AcoState[hlr2]=hrtbeat_sending
Overview
raised based on the Autocutover Audit State (AcoState) of this HLR
combined with the Autocutover Audit State of its designated mate. If this
combination indicates that the mated-pair has been misconfigured, the alarm
is raised. It will be lowered when the configuration is changed so that the
combined AcoState values indicate a properly configured mated-pair.
Format
MON003 MONITOR : Autocutover state trouble <state>:
AcoState[<Name1>]=<Aco State1> ; AcoState[<Name2>]=<Aco
State2> ; [Cutover flag]
Action to be taken
If the HLRs are a designated mated-pair, the Autocutover State is in an invalid
combined state for a properly operating mated-pair.
MON004
3
Name
Autocutover On/State Trouble
GSM18/UMTS04
3-38 CEM logs
Example
MON004 MONITOR : Autocutover on/state trouble raised:
AcoState[hlr1]=aco_off ; AcoOn[hlr1]=yes ;
AcoState[hlr2]=aco_off ; AcoOn[hlr2]=yes
MON004 MONITOR : Autocutover on/state trouble cleared:
AcoState[hlr1]=aco_off ; AcoOn[hlr1]=no ;
AcoState[hlr2]=aco_off ; AcoOn[hlr2]=yes
Overview
raised based on the Autocutover On/Audit State (AcoOn/AcoState) of this
HLR combined with the Autocutover On/Audit State of its designated mate.
If this combination indicates that the mated-pair has been misconfigured, the
alarm is raised. It will be lowered when the configuration is changed so that
the combined AcoOn/AcoState values indicate a properly configured matedpair.
Format
MON004 MONITOR : Autocutover on/state trouble <state>:
AcoState[<Name1>]=<Aco State1> ; AcoOn[<Name1>]=<Aco On1> ;
AcoState[<Name2>]=<Aco State2> ; AcoOn[<Name2>]=<Aco On2>
Action to be taken
If the HLRs are a designated mated-pair, the Autocutover On/Audit State is in
an invalid combined state for a properly operating mated-pair.
MON005
3
Name
Standby On Trouble
Example
MON005 MONITOR : Standby on trouble raised: SbyOn[hlr1]=true ;
SbyOn[hlr2]=false
MON005 MONITOR : Standby on trouble cleared: SbyOn[hlr1]=false
; SbyOn[hlr2]=false
Overview
raised based on the Standby On (SbyOn) of this HLR combined with the
Standby On of its designated mate. If this combination indicates that the
411-8111-803
Standard
01.06
May 2006
CEM logs 3-39
when the configuration is changed so that the combined SbyOn values
Format
MON005 MONITOR : Standby on trouble <State>:
SbyOn[<Name1>]=<Sby On1> ; SbyOn[<Name2>]=<Sby On2>
Action to be taken
If the HLRs are a designated mated-pair, the Standby On, which is configured
on each HLR in the GHLRPARM table is in an invalid combined state for a
properly operating mated-pair.
MON006
3
Name
Standby Mode Trouble
Example
MON006 MONITOR : Standby mode trouble raised:
SbyMode[hlr1]=standalone ; SbyMode[hlr2]=standalone
MON006 MONITOR : Standby mode trouble cleared:
SbyMode[hlr1]=outofservice ; SbyMode[hlr2]=standalone
Overview
raised based on the Standby Mode (SbyMode) of this HLR combined with the
Standby Mode of its designated mate. If this combination indicates that the
when the configuration is changed so that the combined SbyMode values
Format
MON006 MONITOR : Standby mode trouble <State>:
SbyMode[<Name1>]=<Sby Mode1> ; SbyMode[<Name2>]=<Sby Mode2>
Action to be taken
GSM18/UMTS04
3-40 CEM logs
If the HLRs are a designated mated-pair, the Standby Mode, which is
MON007
3
Name
MateHLRNumber Trouble
Example
MON007 MONITOR : MateHLRNumber trouble raised: MateHLRNumber
is invalid.
MON007 MONITOR : MateHLRNumber trouble cleared: MateHLRNumber
is valid.
Overview
raised based on the Mate HLR Number (MateHLRNumber) of this HLR
combined with the HLRNumber of its designated mate. If MateHlrNumber of
this HLR does not contain HLRNumber of its designated mate, this indicates
that the mated-pair has been misconfigured, the alarm is raised. It will be
lowered when the configuration is changed so that the MateHLRNumber
value indicates a properly configured mated-pair.
Format
MON007 MONITOR : MateHLRNumber trouble <State>: MateHLRNumber
is <Validity flag>.
Action to be taken
If this HLR and HLR which is shown in Mate_Slice attribute associated with
the APPL_Container/HlrStby node are not a designated mated-pair, the
If the HLRs are a designated mated-pair, the MateHLRNumber, which is
configured on the HLR in the GHLRPARM table is invalid for a properly
operating mated-pair. The MateHLRNumber should correspond to the HLR
number in table OFCSTD of its mate.
MON008
3
Name
Mate Trouble
411-8111-803
Standard
01.06
May 2006
CEM logs 3-41
Example
MON008 MONITOR : Mate trouble raised: resource discovery in
progress.
MON008 MONITOR : Mate trouble cleared: in service.
Overview
raised to indicate that mated HLR slice temporally can not be monitored
properly. It will be lowered when the slice is returned to monitored state.
Format
MON008 MONITOR : Mate trouble <State>: <Reason>.
Action to be taken
If this HLR and HLR which name is shown in Mate_Slice attribute
(APPL_Container/HlrStby node) are not a designated mated-pair, the Mated
Pair monitor may be configured incorrectly. Please remove the invalid mated
pair using the configCEMS tool.
This log indicates that the CEM is experiencing difficulty monitoring the
mate for this HLR and possibly the mate slice is disconnected.
OSA302
3
Example
Oct 4 09:43:24 urc2y128 : OSA302 MINOR TBL Login Failure
Status: Trouble raised. Location: OMCS Security &
Administration Description: validateLogin - FAILURE logged
in. Login ID - ngo. CEM Server: EM Adapter. Source IP address:
47.209.103.28. Nickname : sdm. . Action: Check for valid
userid and password.
Overview
The OSA302 log reports a login failure due to either an invalid userid or
password. This is a TROUBLE log.
Format
<Date and Time> <Machine> : # <Log Tag> <Severity>
TBL <Trouble>
Status: <Trouble raised>
Location: <software_entity>
Description: <description_text>
Source IP address: <ip_address>
Nickname: <nickname>
Probable Cause: <cause_text>
Action: <text_description>
GSM18/UMTS04
3-42 CEM logs
OSA303
3
Example
Oct 4 09:50:47 urc2y128 : # OSA303 MAJOR TBL Login_Failure.
Status: Trouble raised. Location:
OMCS Security &
Administration . Description: validateLogin- Number of
consecutively failed login attempts exceed allowable limit.
Login ID- ngo. Nickname : sdm. CEM server: EMAdapter. Action:
Access to account ngo has been disabled. Contact the
administrator to reactivate account.
Oct 4 15:49:10 zrc2s0km : [ID 641697 local6.debug] # OSA303
MAJOR TBL Login Failure. Status: Trouble raised. Location:
OMCS Security & Administration Configuration Mismatch Browser security is OFF - node security is on . Action:
Reinstall browser with security.
Overview
The OSA303 log reports 2 specific events:
• a user account has been deactivated. This condition occurs because the
user has performed a series of unsuccessful login attempts. The series of
unsuccessful login attempts occurred consecutively and the number of
attempts exceeded a specific number set in the authentication server.
•
there was a security configuration mismatch between the Browser and
either the CEM Server or the SDM.
This is a TROUBLE log.
Format
TBL <Trouble>
OSA304
3
Example
Oct 4 09:53:31 urc2y128 : # OSA304 MAJOR TBL
Inaccessible_ldap.config_file Status: Trouble raised
Location:
OMCS Security & Administration Description : The
ldap.config file is inaccessible. Nickname : sdm. Action:
Check if ldap.config file exists in the appropriate directory.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-43
Overview
The OSA304 log reports the ldap.config file is inaccessible. This could be due
to the file permissions or ownership being set wrong or the file has been
deleted. This is a TROUBLE log.
Format
TBL <Trouble>
OSA305
3
Example
Oct 4 09:57:17 urc2y128 : # OSA305 MAJOR TBL Login_Failure.
Status: Trouble raised Location: OMCS Security &
Administration . Description: validateLogin - Login failure.
Can't connect to LDAP Server. . Nickname : sdm. CEM server:
EMAdapter. Check if LDAP Server is properly configured in
ldap.conf file.
Overview
The OSA305 log reports that either the CEM Server or the SDM cannot
connect to the LDAP Server. This could be due to either a network outage or
an improperly configured ldap.config file. This is a TROUBLE log.
Format
TBL <Trouble>
OSA306
3
Example
Oct 3 09:20:33 urc2y128 : # OSA306 MAJOR TBLCommand_is_not_permitted. Command name = taccess/
cacheDeRegisterTable~ADMIN~CUSTAB~-1 Status: Trouble raised
GSM18/UMTS04
3-44 CEM logs
Location:
OMCS Security & Administration. Nickname : sdm.
Description : Command is not permitted. User access violation.
Action : Check user's group. Groupsset = CT_User
Overview
The OSA306 log reports the user tried to execute a CEM function for which
the user does not have the proper permissions. This is a TROUBLE log.
Format
TBL <Trouble>
OSA307
3
Example
Oct 4 11:10:14 urc2y128 : OSA307 MINOR TBL Login Failure.
Status: Trouble raised. Location: OMCS Security &
Administration. Description: validateLogin - Login Failure User must change password. Login ID - ngo. CEM Server: EM
Adapter. Source IP address: 47.209.103.28. Nickname : sdm. .
Action: Change password
Overview
The OSA307 log reports 2 specific events:
• this is the first time that the user has logged in and the user must change
his password from the one provided by the administrator.
•
the user’s Password expired.
Format
TBL <Trouble>
411-8111-803
Standard
01.06
May 2006
CEM logs 3-45
OSA308
3
Example
Oct 4 13:33:52 urc2y128 : OSA308 MINOR TBL Change Password
Failure. Status: Trouble raised. Location: OMCS Security &
Administration. Description: changePassword: Failure. Login ID
- ngo. CEM Server: EM Adapter . Source IP address:
47.209.103.28. Nickname : sdm. Probable Cause: The length of
password is too short.. Action: Check the length of the new
password
Overview
The OSA308 log reports errors that occur when the user is specifying a new
password. A password can be rejected for any of the following reasons:
• Length of new password is too short
•
New password is the same as the old password
•
New password only contains alphanumeric characters
Format
TBL <Trouble>
OSA602
3
Example
Oct 4 09:40:46 urc2y128 : OSA602 NONE INFO Login Success
Location: OMCS Security & Administration Description:
validateLogin - SUCCESS logged in. Login ID - ngo. CEM Server:
EM Adapter. Source IP address: 47.209.103.28. Nickname : sdm .
Overview
The OSA602 log reports a successful login. This is an INFO log.
Format
<Date and Time> <Machine> : # <Log Tag> NONE
INFO <info_text>
GSM18/UMTS04
3-46 CEM logs
OSA603
3
Example
Oct 4 13:38:25 urc2y128 : OSA603 NONE INFO Change Password
Success. Location: OMCS Security & Administration.
Description: changePassword: Success. Login ID - ngo. CEM
Server: EM Adapter . Source IP address: 47.209.103.28.
Nickname : sdm.
Overview
The OSA603 log reports the user has successfully changed his password. This
is an INFO log.
Format
INFO <info_text>
OSA604
3
Example
Oct 4 13:38:25 urc2y128 : OSA604 NONE INFO Logout Success
Location: OMCS Security & Administration Description: Login
ID - ngo. CEM Server: EM Adapter. Source IP address:
47.209.103.28. Nickname : sdm.
Overview
The OSA604 log reports the user has logged out. This is an INFO log.
Format
INFO <info_text>
411-8111-803
Standard
01.06
May 2006
CEM logs 3-47
TMN301
3
Format
The following is the format for Log TMN301:
<Date and Time> <Machine> syslog: TMN301 <Severity> TBL
<Trouble>
Location: <software_entity> <user (process id)>
Description: <text_description>
Location
dmsDataServer
Name
Application Error
Explanation
Log TMN301 is generated when the application detects an internal error.
Report examples
Invalid OM Group in configuration
May 19 15:48:17 sdm syslog: TMN301 MAJOR TBL Application error
Status:
Trouble raised
Location:
DAL maint(19742)
Description: Could not initialize OM Access
Action:
Notify system administrator
Action
The system administrator should check the configuration of the TMN system
to ensure that only group names which are valid for the switch are used.
Location
BACKUP System
Name
Application Error
Explanation
Log TMN301 is generated when the automatic backup fails.
Report examples
Daily backup fails
May 19 15:48:17 sdm syslog: TMN301 MINOR TBL Application error
Status:
Trouble raised
Location:
BACKUP System root(28912)
GSM18/UMTS04
3-48 CEM logs
Description: Daily backup fails
Action:
Run backupmenu.ksh to set up daily backup job
Action
Run backupmenu.ksh to set up daily backup job.
Initialization error
May 19 15:48:17 sdm syslog: TMN301 MAJOR TBL Application error
Status:
Trouble raised
Location:
DAL maint(19742)
Description: Could not initialize OM Access
Action:
Notify system administrator
Action
The system could not initialize the OM Access subsystem. The administrator
should check the configuration of the SDM Base software, the connection to
the switch, and the SDM Base processes running on the switch.
TMN302
3
Format
<Trouble>
Location
PM Archive
Name
System error
Explanation
Log TMN302 generates when out of memory.
Report examples
Error opening file: <filename>
Nov 28 15:36:44 crchhe0a syslog: TMN302 MAJOR TBL System Error
Location: PM Archive
Description: Out of memory while writing data to archive
Action: Delete older data to free memory
Action
Delete older data to free memory.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-49
Location
RD Agent (RDA)
Name
System error
Explanation
Log TMN302 generates when a file I/O error occurred:
• no such file
•
file is empty
•
permission denial
•
memory allocation error
•
failed system call
Report examples
Error opening file: <filename>
Nov 28 15:36:44 crchhe0a syslog: TMN302 MAJOR TBL System Error
Location: RD Agent (RDA) root(222)
Description: Error opening file: <filename>
Action: Check file permission.
Action
Check the privilege. The privilege should be set to “755”, stands for read and
execute for all.
Cannot read the configuration file: <filename>
Nov 28 15:36:44 crchhe0a syslog: TMN302 CRIT TBL System Error
Description: Can not read the configuration file: <filename>
Action: Please check the privilege. The privilege should be
set to “550”, stands for read and execute for the user and
group.
Action
execute for the user and group.
Failed System Call: <filename>
Description: Failed System Call: <filename>
Action: Please contact Nortel personnel.
GSM18/UMTS04
3-50 CEM logs
Action
Contact Nortel personnel.
Output file <filename> could not be opened
Nov 28 15:36:44 crchhe0a
Location: RD Agent (RDA)
Description: Output file
Action: Please check the
set to “550”, stands for
group.
syslog: TMN302 CRIT TBL System Error
root(222)
<filename> could not be opened
privilege. The privilege should be
read and execute for the user and
Action
execute for the user and group.
rda config file missing: <filename>
Description: rda config file missing: <filename>
Action
File is Empty: <filename>
Description: File is empty: <filename>
Action
Error reading rda config file
Description: Error reading rda config file
Action
Unable to get hostname
411-8111-803
Standard
01.06
May 2006
CEM logs 3-51
Description: Unable to get hostname
Action
Location
CM Normalizer
Name
System error
Explanation
Log TMN302 generates when the CM Normalizer process starts.
Report examples
Cannot read config file: Init Config
Nov 28 15:36:44 crchhe0a syslog: TMN302 NONE INFO System Error
Location: CM Normalizer omcadmin(222)
Description: Cannot Read Config File: Init Config
Action: Check if InitconFig file exists and in correct format.
Action
Check if InitconFig file exists and if it’s in the correct format.
Location
Log Normalizer
Name
System error
Explanation
Log TMN302 is generated when a file I/O occurred:
• no such file
•
file is empty
•
permission denial
Report examples
Event file <filename> was not found..logNorm exiting
GSM18/UMTS04
3-52 CEM logs
Location: LOG Normalizer omcadmin(222)
Description: Event file <filename> was not found..logNorm
exiting
Action: Check path.
Action
Check the privilege and the location of the file. The privilege should be set to
“550”, stands for read and write for the user and group. The file should be
located in /mscomc/mapper/ directory.
Event file <filename> is empty..logNorm exiting
Description: Event file <filename> is empty..logNorm exiting
Action: Check path, file name and/or read write permission.
Action
Event file <filename> had errors..logNorm exiting
Description: Event file <filename> had errors..logNorm exiting
Action: Please look at the event file to check errors.
Action
Mapper file <filename> had errors...logNorm exiting
Location: LOG Normalizer
Description: Mapper file
exiting
Action: Check the mapper
omcadmin(222)
<filename> had errors...logNorm
file errors.
Action
Mapper file <filename> was not found...logNorm exiting
exiting
Action: Check path, file
411-8111-803
Standard
01.06
May 2006
omcadmin(222)
<filename> was not found...logNorm
name and/or read write permission.
CEM logs 3-53
Action
Mapper file <filename> is empty...logNorm exiting
Action: Check path, file
omcadmin(222)
<filename> is empty...logNorm exiting
name and/or read write permission.
Action
Could not open del rep file <filename>
Description: Could not open del rep file <filename>
Action: Check path, file name and/or read write permission.
Action
TMN303
3
Format
<Trouble>
Location
Normalization Layer
Name
Communication error
GSM18/UMTS04
3-54 CEM logs
Explanation
Log TMN303 generates when the communications used by the NL fail to
provide required services.
Report examples
Failed to register listen connection
Aug 1 18:53:47 crchh891 syslog: TMN303 CRIT TBL Communication
error
Location: Normalization Layer root(801)
Description: Failed to register listen connection
Action: Contact next level of support.
Action
If the problem is persistent, contact local support.
Location
Normalization Layer
Name
Communication error
Explanation
Log TMN303 generates when client cannot connect to server process.
Report examples
Communication error
Aug 1 18:53:47 crchh891 syslog: TMN303 MAJOR TBL Communication
error
Description: Communication error.
Action: Check for server process.
Action
Check for server process.
Location
RD Agent
Name
Communication error
411-8111-803
Standard
01.06
May 2006
CEM logs 3-55
Explanation
Log TMN303 generates when a process has trouble communicating with other
processes. The following descriptions display for this log:
• Could not send the “addrep all” message to SDM... logNorm exiting
•
Could not send the “format all” message to SDM... logNorm exiting
•
Could not send the “<a message>” message to SDM... logNorm exiting
•
Decode Switch Info msg Failed.
•
DMS Name not received from message.
•
Error receiving ...logNorm exiting
•
No message content
•
RD Normalization Layer needs re-discover. Exiting... :
•
RD Normalization Layer RRP proc died. Exiting... :
•
receiveSwitchInfo: Invalid fld ID: < fld id >
•
receiveMOIDelete: missing dms Name: < message >
•
receiveMOICreate: Field for node type missing: <message>
•
receiveMOICreate: Set name binding attr failed: <attr value>
•
receiveMOICreate: Unknown Attribute Field Id: <id>, Value: <value>
•
receiveMOICreate: Failed to set parent for route MOI: <MOI name>
•
receiveMOICreate: Failed to create MOI for: <MOI name>
•
receiveMOIAttribChange: missing dms Name: <message>
•
<proc name>: cannot find MOI: <MOI name>
•
reorder Route MOI’s-Delete 1BM MOI failed: <MOI name>
•
reorder Route MOI’s-Create 1BM MOI failed: <MOI name>
•
Unable to communicate with Agent
•
Unable to communicate with dmsDataServer
•
Unknown message id: < id >
•
Failed to set name binding attrib for route MOI:<MOI name>
Report example
Unable to send/receive message from client.
Nov 28 15:36:44 crchhe0a syslog: TMN303 MAJOR TBL
Communication Error
Location: FM Agent (FMA) root(222)
Description: Unable to send/receive message from client.
Action: Please refer to GR1162 document.
GSM18/UMTS04
3-56 CEM logs
Action
Location
CM Normalizer
Name
Communication error
Explanation
Report examples
Unable to communicate with agent
Nov 28 15:36:44 crchhe0a syslog: TMN303 NONE INFO
Communication error
Description: Unable to communicate with agent
Action: Restart agent.
Action
Restart agent.
TMN304
3
Format
<Trouble>
Location
FM Agent (FMA)
Name
Connection error
411-8111-803
Standard
01.06
May 2006
CEM logs 3-57
Explanation
Log TMN304 generates when a process has a trouble to connect to the server
process. The following descriptions display for this log:
• Data Access Layer is not available
•
RPC returns failure
•
Unable to connect to DataServer Process
•
FM socket connection lost: rc = <rc>
Report example
Socket connection is broken between FM agent and Log
Normalization layer.
Nov 28 15:36:44 crchhe0a syslog: TMN304 MAJOR TBL Connection
Error
Location: FM Agent
Description: Socket connection is broken between FM agent and
Log Normalization layer.
Action
FM socket connection lost: rc=<rc>
Nov 28 15:36:44 crchhe0a syslog: TMN304 CRITICAL TBL
Connection Error
Location: FM Agent (FMA) root (222)
Description: FM socket connection lost: rc=<rc>.
Action: Check FM logNorm procedure.
Action
Check FM logNorm procedure.
Location
CM Normalizer
Name
Connection error
Explanation
process.
GSM18/UMTS04
3-58 CEM logs
Report example
Socket connection is broken between FM agent and Log
Error
Location: CM Normalizer
Description: Socket connection is broken between agent and CM
Action
Location
PM Agent (PMA)
Name
Connection error
Explanation
•
RPC returns failure
•
•
PM received unknown msg: <msg buf>
•
PM socket connection lost: rc=<rc>
Report example
PM received unknown msg: <msg buf>
Nov 28 15:36:44 crchhe0a syslog: TMN304 MINOR TBL Connection
Error
Location: PM Agent (PMA) root (801)
Description: PM received unknown msg: <msg buf>
Action: Contact Nortel if this persists.
Action
PM socket connection lost: rc=<rc>
Connection Error
411-8111-803
Standard
01.06
May 2006
CEM logs 3-59
Description: PM socket connection lost:rc=<rc>.
Action: Check PM NL Server process.
Action
Check PM NL Server process.
Location
RD Agent (RDA)
Name
Connection error
Explanation
•
RPC returns failure
•
•
RD socket connection lost: rc <rc>
•
RD send msg failed: rc = <rc>
Report example
RD socket connection lost: rc<rc>
Connection Error
Description: RD socket connection lost: rc<rc>
Action: Contact Nortel personnel.
Action
RD send msg failed: rc<rc>
Connection Error
Description: RD send msg failed: rc=<rc>
Action: Check CM Normalizer process, exiting...
Action
Check CM Normalizer process, exiting.
GSM18/UMTS04
3-60 CEM logs
Location
Log Normalizer
Name
Connection Error
Explanation
Log TMN304 is generated by log Normalizer when it could not:
• send messages to the SDM’s OSF server process
•
receive message from the SDM’s OSF server process
•
send events to agent
Report examples
Error receiving...logNorm exiting
Error
Location: Log Normalizer omcamin (222)
Description: Error receiving...logNorm exiting
Action: SDM OSF server closed connection
Action
could not send the “<message>” message to SDM...logNorm
exiting
Error
Description: could not send the “<message>” message to
SDM...logNorm exiting
Action
could not send events to agent. Agent removed from output list.
Error
Description: could not send events to agent. Agent removed
from output list
Action: No agents connected..start an agent
411-8111-803
Standard
01.06
May 2006
CEM logs 3-61
Action
No agents connected, start an agent.
TMN305
3
Format
<Trouble>
Location
PM Archive
Name
Explanation
Log TMN305 generates when the archive process receives an invalid
message.
Report examples
Received invalid request for data
Mar 17 08:08:05 crchhb82 syslog: TMN305 MAJOR TBL Message
format error
Location: PM Archive root(801)
Description: Received invalid request for data
Action: Verify request and resend
Action
Contact the next level of support.
Received invalid request to store data
format error
Description: Received invalid request to store data
Action: Contact support.
Action
GSM18/UMTS04
3-62 CEM logs
Received invalid request to store error data
format error
Description: Received invalid request to store error data
Action: Contact support.
Action
Location
Normalization Layer
Name
Explanation
Log TMN305 generates when the NL (Normalization Layer) receives a badly
formatted message from one of it’s clients or servers.
Report examples
Unreadable DAL message type
Aug 1 18:53:47 crchh891 syslog: TMN305 MAJOR TBL Message
format error
Description: Unreadable DAL message type
Action
If the problem is persistent, contact the local support.
Location
PM Agent (PMA)
Name
Explanation
Log TMN305 generates when the process could not read and parse the
message it received.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-63
Report examples
Unreadable DAL message type
Aug 1 18:53:47 crchh891 syslog: TMN305 MINOR TBL Message
format error
Location: PM Agent (PMA)root(801)
Description: Message format error.
Action: Check for errors in the process that send the message
or try to resend the message.
Action
Check for errors in the process that send the message or try to resend the
message.
Could not parse message.
Aug 1 18:53:47 crchh891 syslog: TMN305 CRIT TBL Message format
error
Location: PM Agent(PMA)root(801)
Description: Message format error.
Action
Location
Log Normalizer
Name
Explanation
Log TMN305 is generated by Log Normalizer when it received a
misformatted log message. Usually it means that the OSF server is not
sending the logs in the internal format.
Report examples
Unknown log format. No mapping will be done for input <original
in put>.
Aug 1 18:53:47 crchh891 syslog: TMN305 CRIT TBL Message format
error
Location: PM Agent(PMA)root(801)
Description: Unknown log format. No mapping will be done for
input MSCA **TRK102 FEB28 11:47:59 0300 FLT GROUP_ALARM PRI10
14% BUSY.
GSM18/UMTS04
3-64 CEM logs
Action
TMN306
3
Format
<Trouble>
Location
dmsDataServer
Name
Software error
Explanation
Log TMN306 generates when a software error occurs. The specific problem
is given in the “Description” part of the body.
Report examples
Could not initialize table change notification service
Mar 17 08:08:05 crchhb82 syslog: TMN306 MAJOR TBL Software
error
Status:
Trouble raised
Location: dmsDataServer jhalpin(25094)
Description: Could not initialize table change notification
service
Action: Notify system administrator
Action
Location
RD Agent (RDA)
Name
Software error
411-8111-803
Standard
01.06
May 2006
CEM logs 3-65
Explanation
Log TMN306 generates when a process detects a message in the wrong
format.
Report examples
addSkeletonObj:Nullobj to add to skeleton, class: <class name>
Nov 28 15:36:44 crchhe0a syslog: TMN306 MAJOR TBL Software
error
Description: addSkeltonObj:NULLobj to add skeleton, class:
<class name>
Action: Please refer to GR1162 document
Action
Contact the Nortel personnel.
addSkeletonObj:Failed to allocate memory, class: <class name>
error
Description: addSkeletonObj:Failed to allocate memory, class:
<class name>
Action
Failed to allocate memory, class: <class name>
error
Description: Failed to allocate memory, class: <class name>
Action
addSkeletonObj:Skeleton Insertion failed, class: <class name>
error
Description: addSkeletonObj:Skeleton Insertion failed, class:
<class name>
Action
GSM18/UMTS04
3-66 CEM logs
deleteTMNMOI:Locate parent MOI failed: <MOI name>
error
Description: deleteTMNMOI:Locate parent MOI failed: <MOI name>
Action
deleteTMNMOI:Delete MOI failed: <MOI name>
error
Description: deleteTMNMOI:delete MOI failed: <MOI name>
Action
createMOI:Failed to get MOI for sup clsld: <superior MOI name>
error
Description: createMOI:Failed to get MOI for sup clsld: <super
MOI name>
Action
createMOI:Failed to insert MOI to Hash dict: <MOI name>
error
Description: createMOI:Failed to insert MOI to Hash dict: <MOI
name>
Action
removeRdMOIFromList:Unable to locate MOI from Hash dict:
<MOI name>
error
411-8111-803
Standard
01.06
May 2006
CEM logs 3-67
Description: removeRDMOIFromList:Unable to locate MOI from
Hash dict: <MOI name>
Action
removeRdMOIFromList:Unable to locate MOI in MOI list: <MOI
name>
error
Description: removeRDMOIFromList:Unable to locate MOI in MOI
list: <MOI name>
Action
updateRdMOIOnList:Unable to locate MOI from Hash dict: <MOI
name>
error
Description: updateRDMOIOnList:Unable to locate MOI from Hash
dict: <MOI name>
Action
updateRdMOIOnList:Unable to find MOI from MOI List with given
key: <MOI name>
error
Description: updateRDMOIOnList:Unable to find MOI from MOI
List with given key: <MOI name>
Action
initdmsMESwitchName: Empty skeleton list, check rdaconfig.dat
file: <switch name>
error
GSM18/UMTS04
3-68 CEM logs
Description: initdmsMESwitchName: Empty skeleton list, check
rdaconfig.dat file <switch name>
Action
createNetworkMOI:Failed to insert network obj to Hash dict: <MOI
name>
error
Description: createNetworkMOI:Failed to insert network obj to
Hash dict: <MOI name>
Action
Failed to insert system obj to Hash dict
error
Description: Failed to insert system obj to Hash dict
Action
createLogMOI:Failed to get parent for Log. hosts: <log name>
error
Description: createLogMOI:Failed to get parent for Log. hosts:
<log name>
Action
createLogMOI:Unable to build attribute for: <class name>
error
Description: createLogMOI:Unable to build attribute for:
<class name>
411-8111-803
Standard
01.06
May 2006
CEM logs 3-69
Action
createInitMOIs:Failed to get host name: <hostname>
error
Description: createInitMOIs:Failed to get host name:
<hostname>
Action
createInitMOIs:Failed to get host name: <hostname>
error
Description: createInitMOIs:Failed to get host name:
<hostname>
Action
createInitMOIs:Skeleton list is empty: <switch name>
error
Description: createInitMOIs:Skeleton list is empty: <switch
name>
Action
cleanEntireTree:Failed to get host name
Nov 28 15:36:44 crchhe0a syslog: TMN306 CRITICAL TBL Software
error
Description: cleanEntireTree:Failed to get host name
Action
GSM18/UMTS04
3-70 CEM logs
cleanEntireTree:Failed to get network MOI from hash dict.
error
Description: cleanEntireTree:Failed to get network MOI from
hash dict.
Action
cleanEntireTree:Remove IBM TMN network MOI failed
error
Description: cleanEntireTree:Remove IBM TMN network MOI failed
Action
setTMNAlarmSeverity:Failed to set: <attribute name>
error
Description: setTMNAlarmSeverity:Failed to set <attribute
name>
Action
decrementAlmSummary:propagation ERROR:critical
error
Description: decrementAlmSummary:propagation ERROR:critical
Action
decrementAlmSummary:propagation ERROR:major
error
411-8111-803
Standard
01.06
May 2006
CEM logs 3-71
Description: decrementAlmSummary:propagation ERROR:major
Action
decrementAlmSummary:propagation ERROR:minor
error
Description: decrementAlmSummary:propagation ERROR:minor
Action
decrementAlmSummary:propagation ERROR:warning
error
Description: decrementAlmSummary:propagation ERROR:warning
Action
decrementAlmSummary:propagation ERROR:pending
error
Description: decrementAlmSummary:propagation ERROR:pending
Action
decrementTMNNumOfChildren:ERROR in numberOfChildren
Attib: Zero reached.
error
Description: decrementTMNNumOfChildren: ERROR in
numberOfChildren Attrib: Zero reached.
Action
GSM18/UMTS04
3-72 CEM logs
Alarm mapping failed for:<alarm>
error
Description: Alarm mapping failed for: <alarm>
Action
FAILED MOIInfoList insertion:<MOI name>
error
Description: FAILED MOIInfoList insertion: <MOI name>
Action
getMOIPtrFromList:Failed to match parentId for MOI,
parentId:<parent id>
error
Description: getMOIPtrFromList:Failed to match parentId for
MOI, parentId <parent Id>
Action
getMOIPtrFromList:list is empty.
error
Description: getMOIPtrFromList:list is empty.
Action
getMOIFromList:Failed to match parentId for MOI,
parentId:<parent id>
error
411-8111-803
Standard
01.06
May 2006
CEM logs 3-73
Description: getMOIFromList:Failed to match parentId for MOI,
parentId <parent Id>
Action
getMOIFromList:list is empty.
error
Description: getMOIFromList:list is empty.
Action
FAILED MOIInfoList insertion:<MOI name>
error
Description: FAILED MOIInfoList insertion:<MOI name>
Action
FAILED to locate MOI from MOI List:<MOI name>
error
Description: FAILED to locate MOI from MOI List:<MOI name>
Action
Location
PM Agent
Name
Software error
GSM18/UMTS04
3-74 CEM logs
Explanation
Log TMN306 is generated when the agent fails to insert the newly created
scanner into ScannerList.
Report examples
Scanner list insertion failed
Oct 13 12:00:00 crchhb82 syslog: TMN306 MAJOR TBL Software
error
Location: PM Agent root(801)
Description: Scanner list insertion failed
Action
TMN307
3
Format
<Trouble>
Location
PM Archive
Name
Processing error
Explanation
Log TMN307 generates when a message cannot be processed because the
data in the message is inconsistent with archived data.
Report examples
Data already exists
Mar 17 08:08:05 crchhb82 syslog: TMN307 MINOR TBL Processing
error
Description: Data already exists
Action: Check switch time
411-8111-803
Standard
01.06
May 2006
CEM logs 3-75
Action
Verify that the data being requested makes sense. Verify that the switch time
is accurate.
Request does not match the stored data
error
Description: Request does not match the stored data
Action: Verify that data for the requested group is stored
Action
Verify that the data being requested makes sense. Verify that the switch time
is accurate.
Location
dmsDataServer
Name
Processing error
Explanation
Log TMN307 generates when a message cannot be processed because the
data in the message is inconsistent with archived data.
Report examples
Table Access error
error
Location: DAL maint(801)
Description: Error adding field to tuple request message
Action: Notify Nortel support
Action
An internal software error has occurred, no local action can be taken, and
Nortel support should be notified.
Location
PM Agent
Name
Processing Error
GSM18/UMTS04
3-76 CEM logs
Explanation
Log TMN307 generates when the agent could not properly process the
message received.
Report examples
Processing Error
Aug 1 18:53:47 crchh891 syslog: TMN307 MINOR TBL Processing
Error
Location: PM Agent (PMA) root(801)
Description: Processing Error.
Action: Check for errors during resource discovery process.
Make sure that the resources have been discovered
Action
Check for errors during resource discovery process. Make sure that the
resources have been discovered.
CMIP set failed for simpleScanner class
Oct 13 12:00:00 crchh82 syslog: TMN307 MINOR TBL Processing
Error
Description: CMIP set failed for simpleScanner class
Action: Please contact support.
Action
Contact support.
Set attribute failed for historyData objects
Oct 13 12:00:00 crchh82 syslog: TMN307 MINOR TBL Processing
Error
Description: Set attribute failed for historyData Objects
Action: Please contact support.
Action
Contact support.
Set scannerId attribute failed. Value is <scanner id>
Aug 1 18:53:47 crchh891 syslog: TMN307 CRITICAL TBL Processing
Error
Description: Set scannerId attribute failed. Value is <scanner
id>
Action
411-8111-803
Standard
01.06
May 2006
CEM logs 3-77
Set stopTime attribute failed. Value is <time>
Error
Description: Set stopTime attribute failed. Value is <time>
Action
Set measurementList attribute failed. Value is <data>
Error
Description: Set measurementList attribute failed. Value is
<data>
Action
Error
<data>
Action
Cannot create <MOI name> MOI from Hash dict.
Error
Description: Cannot create <MOI name> MOI from Hash dict.
Action
Failed to get parent <MOI name> MOI
Error
GSM18/UMTS04
3-78 CEM logs
Description: Failed to get parent<MOI name> MOI
Action
Failed to set hasPmData for parent <MOI name> MOI
Error
Description: Failed to set hasPmData for parent<MOI name> MOI
Action
Error
<data>
Action
Set stopTime attribute failed. Value is <time>
Error
Description: Set stopTime attribute failed. Value is <time>
Action
Location
FM Agent
Name
Processing Error
411-8111-803
Standard
01.06
May 2006
CEM logs 3-79
Explanation
Log TMN307 generates in the following scenarios:
• No Managed Object Instance (MOI) in the containment tree.
•
No object IDentifier (OID) defined in the oid.dat.
•
No OID string name associated with OID defined in the name.dat.
•
Fail to get the attribute.
•
Fail to get TMN attribute.
•
logNorm file’s had bad data
•
Failed to complete processing.
Report examples
Can not find MOI for: <MOI string> :
Nov 28 15:36:44 crchhe0a syslog: TMN307 MINOR TBL Processing
Error
Description: Can not find MOI for: <MOI string> :
Descriptions
The following descriptions display for this type of log:
• setTMNAttribute: Null MOI instance pointer: <MOI> :
•
setTMNAttribute: Send Attribute failed: rc :<rc> : <MOI> :
•
setTMNAttrib : Send Attribute failed. rc = <rc> :
•
getTMNAttrib:Null MOI instance pointer : <MOI> :
•
getTMNAttrib:resource get failed: attrib : <attr name> :rc = <rc> :
•
getAttrOID: Cannot recognize attribute : < attr name> :
•
Failed to get class object for class: <class> :
Action
Double check the MOI via the GSM/UMTS Element Manager. If the MOI
displays in the containment tree, there is a mismatch between the VCN and
the containment tree created in the agent. Redo the resource discover.
Can not find the OID for : <OID string> :
Can not find the name associated with <OID> :
Error
Description: Can not find MOI for : <MOI string> :
GSM18/UMTS04
3-80 CEM logs
Action
Ensure the OID is defined in the oid.dat under the dat directory. If the OID is
not defined, contact Nortel personnel to correct the problem. Restart the
agent.
Can not find the OID for the event type: <event>
Error
Description: Can not find OID for the event type: <event> :
Action
Please check the OID.dat file.
Can not find the OID for requiresManualClearParam
Error
Description: Can not find the OID for requiresManualClearParam
Action
Can not find the OID for probableCause
Error
Description: Can not find the OID for probableCause
Action
Can not find the OID for specificProblem
Error
Description: Can not find the OID for specificProblem
Action
411-8111-803
Standard
01.06
May 2006
CEM logs 3-81
Cannot find class name : <class> :
Error
Description: Can not find MOI for : <MOI string> :
Action
Ensure the name is defined in the name.dat under the dat directory for the
associated OID. If the name is not defined, please contact Nortel personnel to
correct the problem. Restart the agent.
Can not get the attribute for : <attribute string> :
Error
Description: Can not find the managed object instance.
Descriptions
The following descriptions display for this type of log:
• Add entry failed <class name> :
•
Attribute defined in rdaconfig does not exist in GDMO, class:< attr
name> :
•
Can not get the TMN attribute for : <attribute string> :
•
Failed to allocate memory, class: < attr name> :
•
getAttr: Cannot recognize attribute : < attr name> :
•
getTMNAttribute: failed:attrib not defined in tmnoid.h: <attr name> :
<MOI> :
•
getTMNAttrib:resource get failed: attrib not defined in GDMO : <attr
name> :
•
mapInitStateToAlarm:get attr failed : <attr name> :
•
Mapping information for <logName>has too few arguments for
<eventName> :
•
Mapping not yet available for state : <attr name> :
•
NULL obj to add to skeleton, class: < attr name> :
•
out of bound error for log <logName> at Position <position> :
•
Skeleton Insertion failed, class:< attr name> :
•
Trying to set unrecognized attribute: < attr name> :
•
Unable to complete Initialization :
GSM18/UMTS04
3-82 CEM logs
•
Unknown class key word in config file : <class> :
Action
Contact Nortel personnel for the following error scenarios:
• IBM function call
•
Hash directory
•
Message protocol
•
Alarm propagation
•
Alarm Mapping
•
GDMO definition
•
config.dat file problem
Location
RD Agent (RDA)
Name
Processing Error
Explanation
Log TMN307 generates when the agent could not properly process the
message received.
Report examples
Cannot find class name: <class name>
Error
Description: Cannot find class name: <class name>
Action
getAttr: Cannot recognize attribute: <attribute name> <MOI
name>
Error
Description: getAttr:Cannot recognize attribute: <attribute
name> <MOI name>
411-8111-803
Standard
01.06
May 2006
CEM logs 3-83
Action
Failed to get class object for class: <class name>
Error
Description: Failed to get class object for class: <class
name>
Action
Unknown class key word in config file: <class name>
Error
Description: Unknown class key word in config file: <class
name>
Action
addClassObj: Add entry failed <class name>
Error
Description: addClassObj: Add entry failed <class name>
Action
Attribute defined in rdaconfig does not exist in GDMO, class:
<class name>
Error
Description: Attribute defined in rdaconfig does not exist in
GDMO, class: <class name>
GSM18/UMTS04
3-84 CEM logs
Action
setTMNStates: failed to set attr: <attribute name> MOI = <MOI
name>
Error
Description: setTMNStates: failed to set attr: <attribute
name>MOI = <MOI name>
Action
setTMNStates: Failed to get attr: <attribute name>
Error
Description: setTMNStates: failed to set attr: <attribute
name>MOI = <MOI name>
Action
buildAndUpdateAttrib: state mapping failed: <attribute name>
Error
Description: buildAndUpdateAttrib: state mapping
failed:<attribute name>
Action
buildAndUpdateAttrib: set tmn states failed: <state list> <MOI
name>
Error
Description: buildAndUpdateAttrib: set tmn states
failed:<state list> <MOI name>
411-8111-803
Standard
01.06
May 2006
CEM logs 3-85
Action
sendMOINotification: Send Notif failed: rc: <rc>: <MOI name>
Error
Description: sendMOINotification: Send Notif failed:rc:<rc>:
<MOI name>
Action
deleteTMNMOI: Remove IBM TMN MOI failed: <MOI name>
Error
Description: deleteTMNMOI: Remove IBM TMN MOI failed:<MOI
name>
Action
initdmsMESwitchName: Failed to set attrib for dms ME: <switch
name>
Error
Description: initdmsMESwitchName: Failed to set attrib for dms
ME: <switch name>
Action
initdmsMESwitchName: First Element in rdconfig file is not
dmsManagedElement Class: <Class name>
Error
Description: initdmsMESwitchName: First Element in rdconfig
file is not dms ManagedElement Class: <Class name>
GSM18/UMTS04
3-86 CEM logs
Action
createNetworkMOI: Failed to set attrib for Network.host:
<hostname>
Error
Description: createNetworkMOI: Failed to set attrib for
Network.host: <hostname>
Action
createNetworkMOI: Unable to build attrib for : <class name>
Error
Description: createNetworkMOI: Unable to build attrib for:
<class name>
Action
createNetworkMOI: IBM createFromResource failed: <MOI name>
Error
Description: createNetworkMOI: IBM createFromResource failed:
<MOI name>
Action
createSystemMOI: Failed to set attrib for System.host:
<hostname>
Error
Description: createSystemMOI: Failed to set attrib for
System.host: <hostname>
411-8111-803
Standard
01.06
May 2006
CEM logs 3-87
Action
createSystemMOI: Unable to build attrib for: <class name>
Error
Description: createSystemMOI: Unable to build attrib for:
<class name>
Action
createSystemMOI: IBM createFromResource failed: <MOI name>
Error
Description: createSystemMOI: Failed to set attrib for
System.host: <hostname>
Action
createLogMOI: Failed to set attrib for Log.host: <log name>
Error
Description: createLogMOI: Failed to set attrib for Log.host:
<log name>
Action
createLogMOI: IBM cci cmip_create failed: <MOI name> :rc = <rc>
Error
Description: createLogMOI: IBM cci cmip_create failed: <MOI
name>: rc=<rc>
GSM18/UMTS04
3-88 CEM logs
Action
createSkeleton: Initialize Skeleton Failed: <switch name>
Error
Description: createSkeleton: Initialize Skeleton Failed:
<switch name>
Action
createSkeleton: Failed to create Skeleton MOI: <MOI name>
Error
Description: createSkeleton: Failed to create Skeleton MOI:
<MOI name>
Action
cannot get the TMN attribute for: alarmSummary Tabulation
Error
Description: cannot get the TMN attribute for: alarmSummary
Tabulation
Action: Please check the TMN attribute list for the node.
Action
Check the TMN attribute list for the node.
mapInitStateToAlarm: get attr failed: <attribute name>
Processing Error
Description: mapInitStateToAlarm:get attr failed: <attribute
name>
411-8111-803
Standard
01.06
May 2006
CEM logs 3-89
Action
Mapping not yet available for state: <attribute name>
Processing Error
Description: Mapping not yet available for state: <attribute
name>
Action
setTMNAttribute: Send Attribute failed: rc: <rc>: <MOI name>
Error
Description: setTMNAttribute: Send Attribute failed: rc:<rc>:
<MOI name>
Action
setTMNAttribute: Null MOI instance pointer: <MOI name>
Processing Error
Description: setTMNAttribute: Null MOI instance pointer: <MOI
name>
Action
getTMNAttributeByIndex: Null MOI instance pointer: <MOI name>
Processing Error
Description: getTMNAttributeByIndex: Null MOI instance
pointer: <MOI name>
GSM18/UMTS04
3-90 CEM logs
Action
getTMNAttributeByIndex: resource get failed: attrib: <attribute
name> :rc=<rc>
Processing Error
Description: getTMNAttributeByIndex: resource get failed:
attrib: <attribute name>: rc=<rc>
Action
getTMNAttributeByIndex: resource get failed: attrib not defined in
GDMO: <attribute name>
Processing Error
Description: getTMNAttributeByIndex: resource get failed:
attrib not defined in GDMO: <attribute name>
Action
receiveMOICreate: set name binding attr failed: <attribute name>
Error
Description: receiveMOICreate: set name binding attr failed:
<attribute name>
Action
reorderRouteMOIs: Cannot find MOI: <MOI name>
Error
Description: reorderRouteMOIs: Cannot find MOI: <MOI name>
411-8111-803
Standard
01.06
May 2006
CEM logs 3-91
Action
reorderRouteMOIs: Delete IBM MOI failed: <MOI name>
Error
Description: reorderRouteMOIs: Delete IBM MOI failed: <MOI
name>
Action
reorderRouteMOIs: Create IBM MOI failed: <MOI name>
Parent=<parent MOI name>
Error
Description: reorderRouteMOIs: Create IBM MOI failed: <MOI
name> Parent=<parent MOI name>
Action
omcLicenses not found.
Error
Description: omcLicenses not found
Action
PM License is invalid.
Error
Description: PM License is invalid.
Action
GSM18/UMTS04
3-92 CEM logs
FM License is invalid.
Error
Description: PM License is invalid.
Action
Cannot find the OID for requiresManualClearParam.
Error
Description: Cannot find the OID for requiresManualClearParam.
Action: Check the oid.dat file.
Action
Check the oid.dat file.
Cannot find the OID for specificProblem.
Error
Description: Cannot find the OID for specificProblem.
Action
Cannot find the OID for probableCause
Error
Description: Cannot find the OID for probableCause.
Action
Location
CM Normalizer
411-8111-803
Standard
01.06
May 2006
CEM logs 3-93
Name
Processing error
Explanation
Report examples
Unable to complete initialization
Nov 28 15:36:44 crchhe0a syslog: TMN307 NONE INFO TMN OK
Description: Unable to complete initialization
Action: Check initialization message from NE.
Action
Check initialization message from NE.
Location
Log Normalizer
Name
Processing error
Explanation
Log TMN307 is generated by Log Normalizer when there is/are:
• error(s) in mapping in the mapper file
•
there is error(s) in events formatting in the event file
Report examples
Event file <filename> had errors...logNorm exiting
Nov 28 15:36:44 crchhe0a syslog: TMN307 CRITICAL TBL TMN OK
Description: Event file <filename> had errors...logNorm
exiting
Action
The design logs will describe the specific problem. Contact Nortel personnel.
Mapper file <filename> had errors...logNorm exiting
Nov 28 15:36:44 crchhe0a syslog: TMN307 CRITICAL TBL TMN OK
Description: Mapper file <filename> had errors...logNorm
exiting
GSM18/UMTS04
3-94 CEM logs
Action
The design logs will describe the specific problem. Contact Nortel personnel.
TMN308
3
Format
<Trouble>
Location
Normalization Layer
Name
Correlation errors
Explanation
Log TMN308 generates when the NL cannot perform a requested correlation
for any reason.
Report examples
Unknown correlation requested
Aug 1 18:53:47 crchh891 syslog: TMN308 MINOR TBL Correlation
error
Description: Unknown correlation requested: “CUGSS”
Action
If the problem is persistent, contact local support.
TMN309
3
Format
<Trouble>
411-8111-803
Standard
01.06
May 2006
CEM logs 3-95
Location
Normalization Layer
Name
Data server error
Explanation
Log TMN309 generates when the NL cannot get the services it requires from
the DAL (Data Access Layer).
Report examples
OM Registration failed
Aug 1 18:53:47 crchh891 syslog: TMN309 CRIT TBL Data Server
error
Description: OM Registration failed
Action
If the problem persists, contact local support.
TMN310
3
Format
<Trouble>
Location
PM Archive
Name
Arithmetic overflow
Explanation
Log TMN310 generates when an additional overflow occurs when attempting
to accumulate hourly or daily data.
GSM18/UMTS04
3-96 CEM logs
Report examples
Overflow during accumulation
Mar 17 08:08:05 crchhb82 syslog: TMN310 MINOR TBL Arithmetic
overflow
Description: Overflow during accumulation
Action: Select shorter granularity period for group
Action
Select a shorter granularity period for the request.
Note: The correlations that result in negative values will generate an
overflow log even though it may not be an error in the VCN.
Location
Normalization layer
Name
Arithmetic overflow
Explanation
Log TMN310 generates when an arithmetic overflow occurs in correlation.
Report examples
Arithmetic overflow in correlation
Mar 17 08:08:05 crchhb82 syslog: TMN310 MINOR TBL Arithmetic
overflow
Location: Normalization layer root(801)
Description: Arithmetic overflow in correlation <OM group
name>
Action: Contact local support
Action
If problem persists, contact local support.
Note: The correlations that result in negative values will generate an
overflow log even though it may not be an error in the VCN.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-97
TMN311
3
Format
<Trouble>
Location
dmsDataServer
Name
Fatal error
Explanation
Log TMN311 generates when a fatal error occurs.
Report examples
Going down on signal 2
Mar 19 11:04:53 crchhb82 syslog: TMN311 CRIT TBL Fatal error
Status:
Trouble raised
Description: Going down on signal 2
Action: None
Action
If problem is persistent, notify local system administrator.
Location
PM Archive
Name
Received signal
Explanation
Log TMN311 generates when a signal is sent to the archive process, resulting
in process death.
Report examples
Received signal: SIGINT
GSM18/UMTS04
3-98 CEM logs
Description: Received signal: SIGINT
Action: Restart archiveServer process
Action
Restart the archive process.
Received signal: SIGTERM
Description: Received signal: SIGTERM
Action
Received signal: UNKNOWN
Description: Received signal: UNKNOWN
Action
Location
Web Agent
Name
Fatal error
Explanation
Log TMN311 generates when a fatal error occurs at initialization. Fatal errors
in these situations.
• When the webAgent’s TCP ports are not defined in the /etc/services file.
•
When the machines hostname cannot be determined.
•
When a new webAgent cannot be started because too many webAgents
are already running.
•
When the webAgent cannot communicate with the IBMcmip process.
Report examples
Failed to find the webagent port in /etc/services
Feb 20 10:16:20 crchyc9c syslog: TMN311 CRIT TBL Fatal error
Status:
Trouble raised
411-8111-803
Standard
01.06
May 2006
CEM logs 3-99
Location: Web Agent demars(32072)
Description: webagent port not defined in /etc/services
file.Exited.
Action: Check /etc/services for webagent port
Action
Check /etc/services for webagent port.
Failed to determine the hostname
Status:
Trouble raised
Description: Failed to start Web Agent; host name not found.
Action: Check host network setup
Action
Check host network setup.
Failed to start because too many WebAgents are running
Status:
Trouble raised
Description: Failed to start Web Agent; too many users.
Action: Reduce number of users
Action
Reduce number of users.
Failed to start because the WebAgents cannot communicate with
the IBMcmip process
Status:
Trouble raised
Description: Failed to start Web Agent; IBMcmip not up.
Action: Check status of IBMcmip.
Action
Check status of IBMcmip.
TMN312
3
Format
<Trouble>
GSM18/UMTS04
3-100 CEM logs
Location
CM Normalizer
Name
Process terminated
Explanation
Log TMN312 generates when the CM Normalizer process terminates.
Report examples
CM Normalizer Terminated
Nov 28 15:36:44 crchhe0a syslog: TMN312 MINOR TBL Process
Terminated
Description: CM Normalizer Terminated.
Action: Check previous logs.
Action
Try to bring SDM back in service.
TMN313
3
Format
<Trouble>
Location
CM Normalizer
Name
State error
Explanation
Log TMN313 generates when the SDM has a state error.
Report examples
SDM not in service
Nov 28 15:36:44 crchhe0a syslog: TMN313 MINOR TBL SDM state
error
411-8111-803
Standard
01.06
May 2006
CEM logs 3-101
Action: Check previous logs to find cause of termination.
Description: SDM not in service.
Action
Check previous logs to find cause of termination.
TMN314
3
Format
<Trouble>
Location
Billing collector
Name
FTAM connection down
Explanation
Log TMN314 generates when the FTAM connection is down.
Report examples
DIRLIS/GHOT tries to connect to FTAM and FTAM is down
Nov 28 15:36:44 crchhe0a syslog: TMN314 MINOR TBL FTAM
connection is down
Location: Billing collector maint (41146)
Action: Check is FTAM is in service.
Description: DIRLIS/GHOT stream starting up, establishing FTAM
connection..
Action
Check if FTAM is in service.
TMN317
3
Format
<Trouble>
GSM18/UMTS04
3-102 CEM logs
Location
LOG Normalizer
Name
SIM Swapover Failure
Explanation
Log TMN317 is generated by the SDM when a GHLR617 log is received from
the VCN MSC/HLR. This indicates that an unsuccessful attempt has been made
to perform swapover as part of Subscriber Identity Module (SIM) Replacement.
The swapover may have been triggered by either:
• the option being set to either USER or FIXED and the invocation time
being met
•
the option being set to USER and a location update being received for the
new IMSI
•
the operator forced the swapover using the ISWAP command of
HLRADMIN
This log indicates that an error has occurred within the VCN HLR and that
the swapover has not taken place.
TMN318
3
Format
<Trouble>
Location
PM Agent
Name
Threshold Crossed
411-8111-803
Standard
01.06
May 2006
CEM logs 3-103
Explanation
This log is generated when an OM violates any one of the three threshold
levels (critical, major, minor) set by the user. In W-NMS, an additional
threshold level "warning" is available and an alarm is raised for this level also.
Report example
thresholdData-MSCCP-currentData- thresholdCrossing BID 67.00
Oct 13 12:00:00 crchhb82 syslog: TMN318 MINOR TBL threshold
crossed
Description: threshold-Data-MSCCP-currentDatathresholdCrossing BID 67.00
Action: Check affected resource or adjust threshold values.
Action
Check affected resource or adjust threshold values.
Format
Alarm Header
NotifID = <NotifId>;
AlarmType = qualityofServiceAlarm;
Severity = <Severity>;
ProbCause = threshold crossed;
SpecificProblem =;
Date = <YYYY/MMM/DD-HH:MM:SS>;
Alarm Body
<NE Name><alarm severity represented by *>
TMN318(thresholdCrossed)
<MMMDD HH:MM:SS>UTC TBL PM threshold crossed
Location: Threshold Manager
Description:
NE: < NE Type NE Name>
Class: < Group Name>
Instance: < Resource Name>
Measurement: < Field Name>
Measurement Value: < Value of the field>
Direction: < Threshold Direction>
Raise Threshold: < Raise threshold value >
ClearThreshold: < Clear threshold value >
Action: None
Location
Threshold Manager
Name
Threshold Crossed
GSM18/UMTS04
3-104 CEM logs
Explanation
For positive thresholding, an alarm is generated when the field value goes
above the raise value and the alarm is cleared when the field value comes
below the clear value. This is reversed for negative thresholding.
For more information regarding TMN318, refer to the threshold mangement
section in GSM /UMTS Voice Core Network OAM User Guide, NTP 4118111-503.
Format
Alarm Header
NotifID = <NotifId>;
AlarmType = qualityofServiceAlarm;
Severity = <Severity>;
ProbCause = data missing;
SpecificProblem =;
Date = <YYYY/MMM/DD-HH:MM:SS>;
Alarm Body
<NE Name><alarm severity represented by *> TMN318(dataMissing)
<MMMDD HH:MM:SS>UTC TBL PM data missing
Location: Threshold Manager
Description:
NE: < NE Type NE Name>
Class: < Group Name>
Instance: < Resource Name>
Measurement: < Field Name>
Measurement Value: < Value of the field>
Direction: < Threshold Direction>
Raise Threshold: < Raise threshold value >
ClearThreshold: < Clear threshold value >
Action: None
Location
Threshold Manager
Name
Data Missing
Explanation
Threshold Manager generates data missing alarm when OM data does not
arrive for an element. It generates the alarm after waiting for one transfer
period and a configurable allowance time set for that element type.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-105
For more information regarding TMN318, refer to the threshold mangement
section in GSM /UMTS Voice Core Network OAM User Guide, NTP 4118111-503.
TMN319
3
Format
<Trouble>
Location
RD Agent (RDA) root (41560)
Name
Resource Discovery Started
Explanation
Log TMN319 is generated when the resource discovery has started.
Report examples
CM Normalizer process started
Nov 28 15:36:44 crchhe0a syslog: TMN319 MINOR TBL Resource
Discover Started
Description: Agent Resource Discovery Started:Tue Jun 15
15:32:32 1999 Switch Name:MSCI
Action: None
Action
None.
TMN341
3
Format
<Trouble>
GSM18/UMTS04
3-106 CEM logs
Location
Object Manager
Name
LogNormDown
Explanation
Log TMN341 generates when LogNorm is down.
Report examples
LogNormdown
Nov 28 15:36:44 crchhe0a syslog: TMN341 Warning LogNormdown
Status: Warning
Location: Object Manager
Description: LogNormdown
Action: No action required.
Action
No action required.
TMN342
3
Format
<Trouble>
Location
Object Manager
Name
CMNormDown
Explanation
Log TMN342 generates when CMNorm is down.
Report examples
LogNormdown
Status: Warning
411-8111-803
Standard
01.06
May 2006
CEM logs 3-107
Description: CMNormdown
Action
No action required.
TMN343
3
Format
<Trouble>
Location
Object Manager
Name
OMNormDown
Explanation
Log TMN343 generates when OMNorm is down.
Report examples
LogNormdown
Status: Warning
Description: LogNormdown
Action
No action required.
TMN600
3
Format
<Trouble>
GSM18/UMTS04
3-108 CEM logs
Location
CM Normalizer
Name
TMN OK
Explanation
Report examples
CM Normalizer process started
Nov 28 15:36:44 crchhe0a syslog: TMN600 NONE INFO TMN OK
Description: CM Normalizer process started
Action
None.
Location
Element Browser
Name
TMN Initial State Mapping
Explanation
This log is generated during resource discovery or in the case of the lost logs
when the VCN state is mapped to its corresponding alarm.
Report examples
Initial state mapped alarm cleared by propagation
Action
None.
Initial state mapped alarm
Action
None.
Alarm cleared because resource has been deleted
Action
None.
SDM out of service
Action
None.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-109
SDM return to service
Action
None.
Location
Log Normalizer
Name
TMN OK
Explanation
Log TMN600 is generated by Log Normalizer when:
• successfully started
•
it successfully sends delrep messages to SDM’s OSF server
Report examples
config Files’ path: <pathname>
Nov 28 15:36:44 crchhe0a syslog: TMN600 INFO TMN OK
Description: config Files’ path: <pathname>
Action
No action required.
Following message was sent to SDM’s OSF server-- <message>
Nov 28 15:36:44 crchhe0a syslog: TMN600 INFO TMN OK
Description: Following message was sent to SDM’s OSF server-delrep OMPR 221
Action
No action required.
Location
Web Agent
Name
Information only
GSM18/UMTS04
3-110 CEM logs
Explanation
Log TMN600 is generated to provide information to the user. Information logs
occur in these situations.
• When a restore from backup begins.
•
When a restore from backup fails.
•
When an incoming alarm has fields that must be truncated to fit in the
database.
•
When a webAgent CMIP object cannot be created.
•
The alarm database has an insertion state, which is either good or failed.
The alarm database is in state good, if the last insertion succeeded, or
failed, if the last insertion failed. An alarm is generated when the alarm
database insertion state transitions.
Report examples
a restore from backup begins
Feb 5 22:42:52 sdm syslog: TMN600 NONE INFO Information only
Location: Web Agent root(16142)
Description: performing restore
a restore from backup fails
Description: restore failed
when an incoming alarm has fields that must be truncated
Description: eventCode 68 too long - truncating
the webAgent’s CMIP object cannot be created
Description: Failed to create EFD; CMIP create failed 32
the alarm database insertion state toggles to good
Description: error(Database Alarm Insert Succeeded)
the alarm database insertion state toggles to failed
Description: error(Database Alarm Insert Failed:
notificationId out of order)
411-8111-803
Standard
01.06
May 2006
CEM logs 3-111
TMN601
3
Format
<Trouble>
Location
PM Archive
Name
File I/O info
Explanation
Log TMN601 generates if the version Summary file is not found, meaning
that the archive is empty. This is normal when starting the archive process for
the first time.
Report examples
Failed to open version summary file
Mar 17 08:08:05 crchhb82 syslog: TMN601 NONE INFO File IO info
Description: Failed to open version summary file. It will be
created with the first storage request.
Action
None.
TMN603
3
Format
<Trouble>
Location
PM Agent
Name
Connection status
GSM18/UMTS04
3-112 CEM logs
Explanation
Log TMN603 generates when the client loses connection with the server.
Report examples
Connection status
Aug 1 18:53:47 crchh891 syslog: TMN603 NONE INFO Connection
status
Location: PM Agent
Description: Connection status.
Action
None.
Location
CM Normalizer
Name
Connection status
Explanation
Report examples
New agent has connected to CM Normalizer
Nov 28 15:36:44 crchhe0a syslog: TMN603 CRITICAL Connection
status
Description: New agent has connected to CM Normalizer
Action
None.
Location
Log Normalizer
Name
Connection status
Explanation
Log TMN603 is generated by Log Normalizer when:
• the agent connects
•
411-8111-803
the agent closes connection
Standard
01.06
May 2006
CEM logs 3-113
•
could not connect to SDM’s OSF server
•
connection to SDM’s OSF server was established
Report examples
connected to agent
Nov 28 15:37:47 crchhe0a syslog: TMN603 INFO OK Connection
status
Location: LOG Normalizer omcadmin (222)
Description: connected to agent
Action
No action required.
Null input from agent -- closing connection
status
Description: Null input from agent -- closing connection
Action
No action required.
connected to SDM
status
Description: connected to SDM
Action
No action required.
Could not connect to SDM...trying
status
Description: Could not connect to SDM...trying
Action
No action required.
TMN604
3
Format
<Trouble>
GSM18/UMTS04
3-114 CEM logs
Location
BACKUP System
Name
Application status
Explanation
Log TMN604 generates when daily backup succeeds.
Report examples
Daily backup
Mar 20 07:34:35 crchhb82 syslog: TMN604 INFO Application
Status
Location: BACKUP System root(28986)
Description: Daily backup starts on Thu May 18 09:46:14 CDT
2000.Current backup device is set to /dev/rmt0. Backup
completed.fullbackup ended on Thu May 18 09:51:10 CDT 2000.
Please refer to /mscomc/tools/fullbackup.log for detailed
information. The next backup will be directed to rmt0. Please
remember to put a new tape into this tape drive.
Location
dmsDataServer
Name
Application status
Explanation
Log TMN604 generates when the state of an SDM API changes.
Report examples
DD and CM unavailable
Mar 20 07:34:35 crchhb82 syslog: TMN604 NONE INFO Application
Status
Description: DD and CM unavailable
Action
If the message indicates that the DD and/or CM are unavailable, check the
connection between machines, and ensure that the appropriate processes are
running. The DD may be unavailable simply because it’s downloading the
data dictionary from the switch, which is a normal part of operations.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-115
Location
PM Archive
Name
Application status
Explanation
Log TMN604 generates when a change in the transfer period or field list is
detected.
Report examples
Opening a new version directory due to transfer period or field
change
Mar 17 08:08:05 crchhb82 syslog: TMN604 NONE INFO Application
status
Description: Opening a new version directory due to transfer
period or field change
Action
None.
Location
CM Normalizer
Name
Application status
Explanation
Log TMN604 provides the status of the Element Manager application.
Report examples
SDM stat change received
Nov 28 15:36:44 crchhe0a syslog: TMN604 NONE INFO Application
Status information
Description: SDM stat change received.
Action
None.
GSM18/UMTS04
3-116 CEM logs
TMN605
3
Format
TMN605 <data> <time> <seq. no> INFO Last Core Restart Info
Location: RPC Server maint(pid)
Description: Last restart type: <type>, last restart time
<yyyy/mm/dd HH:MM:SS.000 A>
Location
RPC Server
Name
Core Restart
Explanation
Log TMN605 is an information log. Log TMN605 generates when the
rpcServer receives the return of getRestartTypeInfo. TMN605 shows the last
restart type and the restart time at Core.
Core restart type can be one of the following:
• warm restart
•
cold restart
•
reload restart
•
warm swact
•
cold swact
•
norestart swact
•
abort swact
•
unknown
The core restart will trigger cmNorm to restart. The Core restart information
will be retrieved as part of XAC-0 alarm status.
The rpcServer persists the last Core restart information that it has seen so far.
When it detects the last core restart information has changed, it generates
TMN605 logs. As result, TMN605 reports Core restart information when
CEM server is running during restart. TMN605 reports last Core restart
information when CEM server just starts.
At any time, the attribute, XA-Core configuration, on XAC-0 object can tell
the last core restart reason and restart time.
411-8111-803
Standard
01.06
May 2006
CEM logs 3-117
Report example
Reload Restart
MSCL TMN605 JUL16 15:40:47 1047 INFO Core Restart Info
Location: RPC Server maint(19950)
Description: Last restart type: reload restart, last restart
time: 2003/07/16 12:16:18.000 WED.
Action
None.
TMN610
3
Format
| | | | TMN610 | <date and time> | | | <reason>
Location
OMCS Adapter
Name
Alarms Option
Explanation
TMN610 is generated when coreDA loses connection to EMS or when
logNormalizer is disconnected.
The TMN610 generated by the coreDA for the LOA with objectManager
contains the server timeStamp. If the objectManager happens to be on the
SDM, or other server, there is a chance that LOA alarm might have a
timeStamp behind the timeStamp of the alarms coming from the
objectManager. In this scenario, the objectManger is sending alarms to NSP
after coreDA has sent the LOA alarm.
Report examples
| | | | TMN610 | Feb16 21:00:55 UTC | | | link disconnected
Action
None.
TMN614
3
Format
<Trouble>
GSM18/UMTS04
3-118 CEM logs
Location
Billing collector
Name
FTAM connection up
Explanation
Log TMN614 generates when the FTAM connection is up.
Report examples
DIRLIS/GHOT tries to connect to FTAM and FTAM is up
Nov 28 15:36:44 crchhe0a syslog: TMN614 FTAM connection is up
Status: FTAM up
Location: Billing collector maint (41146)
Action: None
Action
None.
TMN618
3
Format
<Trouble>
Location
PM Agent
Name
Threshold cleared
Explanation
This log is generated when a threshold alarm for an OM gets cleared.
Report examples
thresholdData-MCCP-currentData-thresholdCleared MMBID 67.00
status
Location: PM Agent root(801)
Description: thresholdData-MSCCP-currentData-thresholdCleared
411-8111-803
Standard
01.06
May 2006
CEM logs 3-119
MMBID 67.00
Action: None
Action
No action required.
TMN619
3
Format
<Trouble>
Location
RD Agent
Name
Resource Discover Completed
Explanation
Log TMN619 is generated when the Resource Discover is completed.
Report examples
Agent Resource Discovery Completed
Nov 28 15:36:44 crchhe0a syslog: TMN619 NONE INFO Resource
Discover Completed
Location: RD Agent (RDA)(41560)
Description: Agent Resource Discovery Completed: Tue Jun 15
16:03.10 1999 Switch Name:MSCI
GSM18/UMTS04
3-120 CEM logs
411-8111-803
Standard
01.06
May 2006
4-1
Logs index
4
Table 4-1 lists the voice core network logs collected by the OMC-S. These logs
raise or clear alarms shown in the OMC-S, and can be viewed within the OMCS alarm text.
• Log Name - appears in the "Log" column of the CEM GUI, indicating the
log that raised the alarm.
•
Log Header - provides a brief description of the log from the
documentation.
•
OMC-S Description - the probable cause of the alarm raised by the log.
•
Mapped - indicates when the log was added to the list of logs collected by
the OMC-S.
•
Manual Clear (Y / N) - specifies whether the log is manually or
automatically cleared. ‘Y’ means the log is manually cleared. ‘N’ means
the log is automatically cleared.
•
TMN600 Override (Y / N)- indicates if the log will be overwritten by
TMN600 when the CEM does a Remote Procedure Call (RPC).
The rpcServer retains the last Core restart information that it has seen thus
far and generates a TMN605 log when it detects that the last Core restart
information is changed. As result, for each core restart, rpcServer will
generate a TMN605 log to inform users. TMN605 reports the Core restart
type and restart time.
Note: The Last Core Restart also adds a log mapping of SDM700. SDM
Base Maintenance uses SDM700 log to report Core Restart.
Some alarms will be replaced with a TMN600 alarm when the CEM does
an RPC. This RPC is the calling of a DMS procedure from the SDM. The
RPC on the SDM sends a message to the corresponding RPC process on
the DMS with a process ID and input parameters. After the DMS process
is invoked, the result is sent back to the SDM.
Typically, an RPC is called to retrieve the real status of a particular node
on the DMS. It is done during the start up of the cmNorm and on a regular
GSM18/UMTS04
4-2 Logs index
30 minute audit cycle subsequent to the start up. An RPC is also invoked
by a certain number of logs for the purpose of getting a real time update.
The severity and the problem details for the alarms replaced with a
TMN600 alarm are not lost or changed.
Table 4-1
VCN Logs collected by OMC-S
Log
Name
Log Header
OMC-S Description
Mapped Manual TMN600
Clear
Override
(Y / N) (Y / N)
AP311
Memory_Test_Fault
memoryTestFault
< GEM12 Y
N
AP312
Port_Test_Fault
portTestFault
< GEM12 Y
N
AP313
Fault_Sync
syncStateChange
< GEM12 N
Y
AP314
SwAct_Fault
swactFault
< GEM12 Y
N
AP315
Jam_Fault
jamFault
< GEM12 Y
N
AP316
Image_Test_Fail
imageTestFail
< GEM12 Y
N
AP318
Mismatch_Recovery
syncStateChange
< GEM12 N
Y
AP319
Hardware_Datafill_Fault
hwDatafillFault
< GEM12 Y
N
AP320
SW_Trap
swTrap
< GEM12 Y
N
AP321
Low_Resource_Warning
lowResourceWarning
< GEM12 Y
N
AP322
Low_Spare_Warning
lowSpareWarning
< GEM12 Y
N
AP323
REx_Fault
rexFault
< GEM12 Y
N
AP324
Peripheral_Interrupt_Received
peripheralInterrupt
< GEM12 Y
N
AP501
Activity_State_Change
processorStateChange
< GEM12 N
Y
AP502
Card_State_Change
cardStateChange
< GEM12 N
Y
AP503
Sync_State_Change
< GEM12 N
N
AP504
Jam_State_Change
< GEM12 N
N
AP800
Threshold_Exceeded
thresholdCrossed
< GEM12 Y
N
AUDT105
TRUNK_RESET
dmsStateChange
< GEM12 N
Y
AUDT107
TRUNK_AUDIT_1
trunkAudit
< GEM12 Y
N
AUDT108
TRUNK_AUDIT_2
trunkAudit
< GEM12 Y
N
—sheet 1 of 50—
411-8111-803
Standard
01.06
May 2006
Logs index 4-3
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
AUDT109
TRUNK_AUDIT_3
dmsStateChange
< GEM12 N
Y
AUDT110
TRUNK_AUDIT_4
dmsStateChange
< GEM12 N
Y
AUDT112
RCVR_AUDIT_1
rcvrAudit
< GEM12 Y
N
AUDT113
RCVR_AUDIT_2
rcvrAudit
< GEM12 Y
N
AUDT114
RCVR_AUDIT_3
rcvrAudit
< GEM12 Y
N
AUDT116
TRUNK_AUDIT_6
trunkAudit
< GEM12 Y
N
AUDT117
TRUNK_AUDIT_7
trunkAudit
< GEM12 Y
N
AUDT128
DIGITAL_MODEM_AUDIT
modemAudit
< GEM12 Y
N
AUDT150
ANN_AUDIT_1
annAudit
< GEM12 Y
N
AUDT151
ANN_AUDIT_2
annAudit
< GEM12 Y
N
AUDT152
ANN_AUDIT_3
annAudit
< GEM12 Y
N
AUDT153
ANN_AUDIT_4
annAudit
< GEM12 Y
N
AUDT159
SVCTSUB_system_no_loaded
SVCTSUBmissing
< GEM12 Y
N
AUDT160
INVALID_FREE_SVCIRCUIT
invalidOperation
< GEM12 Y
N
AUDT161
SVCT_AUDIT_1
svctAudit
< GEM12 Y
N
AUDT162
SVCT_AUDIT_2
svctAudit
< GEM12 Y
N
AUDT163
SVCT_AUDIT_3
svctAudit
< GEM12 Y
N
AUDT166
BAD_TIMEODAY_ENTRY
badTODValue
< GEM12 Y
N
AUDT167
BAD_TODHEAD_ENTRY
badTODValue
< GEM12 Y
N
AUDT168
TOD_SYSTEM_SHUTDOWN
TODshutdown
< GEM12 Y
N
AUDT169
TOD_SYSTEM_SHUTDOWN
TODshutdown
< GEM12 Y
N
AUDT179
CCS7_MACHINE_
CONGESTION_AUDIT
c7CongestionAudit
< GEM12 Y
N
AUDT180
INVALID_FREE_FOR_
invalidOperation
< GEM12 Y
N
AUDT181
CF3P_AUDIT_1
cf3pAudit
< GEM12 Y
N
—sheet 2 of 50—
GSM18/UMTS04
4-4 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
AUDT182
CF3P_AUDIT_2
cf3pAudit
< GEM12 Y
N
AUDT183
CF3P_AUDIT_3
cf3pAudit
< GEM12 Y
N
AUDT191
INVALID_FREE_FOR_CF3P
invalidOperation
< GEM12 Y
N
AUDT192
CF6P_AUDIT_1
cf6pAudit
< GEM12 Y
N
AUDT193
CF6P_AUDIT_2
cf6pAudit
< GEM12 Y
N
AUDT194
CF6P_AUDIT_3
cf6pAudit
< GEM12 Y
N
AUDT197
MISSING_ROUTE
missingRoute
< GEM12 Y
N
AUDT205
DRAMAUDIT1
dramAudit
< GEM12 Y
N
AUDT206
DRAMAUDIT2
dramAudit
< GEM12 Y
N
AUDT207
DRAMAUDIT3
dramAudit
< GEM12 Y
N
AUDT619
Routeset_Congestion_Progress
congestionProgress
< GEM12 Y
N
AUDT620
Lk_Cngstn_Mismatch
congestionMismatch
< GEM12 Y
N
AUDT621
NONE
mismatchFound
< GEM12 Y
N
AUDT622
NONE
mismatchFound
< GEM12 Y
N
AUDT624
LK_RECOVERED_BY_AUDIT
linkRecovered
< GEM12 Y
N
AUDT628
SCCP_PM_Physical_Data_Audit dataAudit
< GEM12 Y
N
C7TU103
SEND_TO_LINK_MSG
LinkMsgINFO
< GEM12 Y
N
C7TU104
SEND_FROM_LINK_MSG
LinkMsgINFO
< GEM12 Y
N
C7TU105
SEND_FAILED_MSG
LinkMsgINFO
< GEM12 Y
N
C7TU106
INVALID_MESSAGE
InvalidMsg
< GEM12 Y
N
C7TU107
NO_ACK_MESSAGE
NoAckMsg
< GEM12 Y
N
C7TU109
C7TU_TRACING_ON
tracingINFO
< GEM12 Y
N
C7TU110
C7TU_TRACING_OFF
tracingINFO
< GEM12 N
N
C7TU201
ISUP_TRACE_MSG
ISUPMsgINFO
< GEM12 Y
N
—sheet 3 of 50—
411-8111-803
Standard
01.06
May 2006
Logs index 4-5
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
C7TU202
ISUP_INTERCEPTED_MSG
ISUPMsgINFO
< GEM12 Y
N
C7TU301
C7TU_TRAFFIC_RECEIVER
TUTrafficINFO
< GEM12 Y
N
C7TU302
C7TU_TRAFFIC_SENDER
TUTrafficINFO
< GEM12 Y
N
C7TU303
C7TU_TRAFFIC_ERROR
TUTrafficINFO
< GEM12 Y
N
C7UP102
REL_DUE_TO_ABNORMAL_
CONDTION
c7LinkFailure
< GEM12 Y
N
C7UP103
CIRCUIT_BLO/UBL
circuitBlocked
< GEM12 Y
N
C7UP104
GROUP_CIRCUIT_BLO/UBL
circuitBlocked
< GEM12 Y
N
C7UP105
UNSUCCESSFUL_CALL_
ATTEMPT
callEstablishmentError
< GEM12 Y
N
C7UP106
RESOURCE_UNAVAILABLE
resourceUnavailable
< GEM12 Y
N
C7UP107
ISUP_CONTINUITY_ALERT
callTreatmentFailure
< GEM12 Y
N
C7UP109
CQ_STATE_CHANGE
cqStateChange
< GEM12 Y
N
C7UP110
REMOTE_END_SENT_BAD_
MSG
< GEM12 Y
N
C7UP111
C7UP_TRUNK_TRBL
c7upTrunkTBL
< GEM12 Y
N
C7UP112
UNEXPECTED_C7UP_MSG
unexpectedC7UPMsg
< GEM12 Y
N
C7UP113
ISUP_MTC_TRBL
isupMaintTBL
< GEM12 Y
N
C7UP114
ISUP_ALERT
isupAlert
< GEM12 Y
N
C7UP115
ISUP_RESOURCES
isupResourcesFailure
< GEM12 Y
N
C7UP116
C7UP_TRUNKS_BLOCKED
c7upTrkBlock
< GEM12 Y
N
C7UP117
C7UP_TRUNKS_UNBLOCKED
c7upTrkBlock
< GEM12 N
N
C7UP118
INTERWORKING_MSG_
(TABLE_FAILMSG)
< GEM12 Y
N
C7UP119
2ND_GRP_MSG_NOT_RCVD
2ndGrpMsgMissing
< GEM12 Y
N
C7UP130
Hop_Counter_Expired
hopCounterExpired
< GEM12 Y
N
—sheet 4 of 50—
GSM18/UMTS04
4-6 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
C7UP301
Insuficient_HC_Value
insuficientHCValue
< GEM12 Y
N
CAP100
CAPACITY_SUMMARY
capacitySummary
GEM15
Y
N
CAP101
CAPACITY_DATA
capacityData
GEM15
Y
N
CAP102
CAPACITY_SCHEDMAP
capacitySchedMap
GEM15
Y
N
CAP103
CAPACITY_DETAIL
capacityDetail
GEM15
Y
N
CARR300 CARRIER
carrierFailureEvent
GEM13
N
N
CARR310 CARRIER
carrierFailureEvent
GEM13
N
N
CARR330 CARRIER
protectionSwitchINFO
GEM13
Y
N
CARR331 CARRIER
protectionSwitchFailure
GEM13
Y
N
CARR340 CARRIER
simplexAlarm
GEM13
Y
N
CARR341 CARRIER
simplexAlarm
GEM13
N
N
CARR500 CARRIER
carrierStateChange
GEM13
Y
Y
CARR501 CARRIER
carrierStateChange
GEM13
Y
Y
CARR510 CARRIER
carrierStateChange
GEM13
Y
Y
CARR511 CARRIER
carrierStateChange
GEM13
Y
Y
CARR512 CARRIER
carrierStateChange
GEM13
Y
Y
CARR800 CARRIER
opticalParamThresholdCrossed
GEM13
Y
N
CARR801 CARRIER
thresholdReset
GEM15
Y
N
CARR810 CARRIER
opticalParamThresholdCrossed
GEM13
N
N
CARR811 CARRIER
pmThresholdCrossed
GEM13
N
N
CCS101
Link_Failure
linkSyncStatusChange
< GEM12 N
Y
CCS102
Link_Sync
< GEM12 N
Y
CCS103
Persistent_Act_Timeout
< GEM12 Y
Y
CCS104
RPO_ON
remoteProcessorOut
< GEM12 N
Y
—sheet 5 of 50—
411-8111-803
Standard
01.06
May 2006
Logs index 4-7
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
CCS105
RPO_OFF
remoteProcessorRecovered
< GEM12 N
Y
CCS106
Link_Deactivated
< GEM12 N
Y
CCS107
Link_Test_Failed
c7LinkTestFailed
< GEM12 Y
Y
CCS108
Could_not_nail_up_link
nailupFailure
< GEM12 Y
N
CCS109
LINKSET_AVAILABLE
linksetStateChange
< GEM12 N
Y
CCS110
LINKSET_UNAVAILABLE
linksetStateChange
< GEM12 N
Y
CCS120
HSL_SLM_Report
linkPerformanceINFO
< GEM12 Y
N
CCS121
Minor_State_Change
unavailableLinkINFO
< GEM12 Y
N
CCS124
Link_Threshold
linkThresholdCrossed
< GEM12 Y
N
CCS125
Carrier_Threshold
carrierThresholdCrossed
< GEM12 Y
N
CCS145
MTP_Restart_Inititiated
MTPRestartInitiated
< GEM12 Y
N
CCS146
MTP_Restart_Status
MTPRestartInProgress
< GEM12 Y
N
CCS147
MTP_Restart_Terminated
MTPRestartCompleted
< GEM12 N
N
CCS151
Routeset_Offline
routeSetStateChange
< GEM12 N
Y
CCS152
Routeset_ManBusy
routeSetStateChange
< GEM12 N
Y
CCS153
Routeset_System_Busy
routeSetStateChange
< GEM12 N
Y
CCS154
Routeset_Unavailable
routeSetStateChange
< GEM12 N
Y
CCS155
Routeset_Available
routeSetStateChange
< GEM12 N
Y
CCS156
Link_Offline
linkStateChange
< GEM12 N
Y
CCS157
Link_ManBusy
linkStateChange
< GEM12 N
Y
CCS158
Link_System_Busy
linkStateChange
< GEM12 N
Y
CCS159
Link_Local_Inhibit_On
linkStateChange
< GEM12 N
Y
CCS160
Link_Remote_Inhibit_On
linkStateChange
< GEM12 N
Y
CCS161
Link_Local_Inhibit_Off
linkStateChange
< GEM12 N
Y
—sheet 6 of 50—
GSM18/UMTS04
4-8 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
CCS162
Lnk_Remote_Inhibit_Off
linkStateChange
< GEM12 N
Y
CCS163
Link_Available
linkStateChange
< GEM12 N
Y
CCS164
Link_Unavailable
linkStateChange
< GEM12 N
Y
CCS165
L3_Protocol_Violation
protocalViolation
< GEM12 Y
Y
CCS166
Route_Allowed
routeTrafficStateChange
< GEM12 N
Y
CCS167
Route_Restricted
minor
< GEM12 N
Y
CCS168
Route_Prohibited
routeTrafficStateChange
< GEM12 N
Y
CCS169
protocalViolation
< GEM12 Y
N
CCS170
invalidMsg
< GEM12 Y
N
CCS171
invalidMsg
< GEM12 Y
N
CCS172
Routeset_Congestion
congestion
< GEM12 Y
N
CCS173
Link_Congestion
congestion
< GEM12 Y
N
CCS174
Invalid_Point_Code
invalidPointCode
< GEM12 Y
N
CCS175
Routeset_Restricted
routeSetStateChange
< GEM12 N
Y
CCS180
PPC_Route_Member_Allowed
PPCMemberAvailabilityChange
< GEM12 N
N
CCS181
PPC_Route_Member_Restricted PPCMemberAvailabilityChange
< GEM12 Y
N
CCS182
PPC_Route_Member_Prohibited PPCMemberAvailabilityChange
< GEM12 Y
N
CCS183
PPC_Routeset_Member_
Unavailable
< GEM12 Y
N
CCS184
Unavailable
< GEM12 N
N
CCS185
Restrcited
< GEM12 Y
N
CCS186
Linkset_Impact_Summary
linksetImpactSummary
< GEM12 N
Y
CCS189
External_Router_Connection
extRouterStatusChange
< GEM12 Y
N
CCS191
External_Router_Unavailable
< GEM12 Y
N
—sheet 7 of 50—
411-8111-803
Standard
01.06
May 2006
Logs index 4-9
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
CCS192
External_Router_Available
< GEM12 N
N
CCS195
External_Router_Offline
< GEM12 Y
N
CCS196
External_Router_ManBusy
< GEM12 Y
N
CCS197
External_Router_System_Busy
< GEM12 Y
N
CCS199
CCS7_Link_Fail
ccs7LinkFailure
< GEM12 Y
N
CCS208
Remote_Point_Code_OFFL
pointCodeStatusChange
< GEM12 Y
N
CCS209
Remote_Point_Code_MBSY
pointCodeStatusChange
< GEM12 Y
N
CCS212
Remote_Subsystem_OFFL
warning
< GEM12 Y
N
CCS213
Remote_Subsystem_MBSY
remoteSubsysStateChange
< GEM12 Y
N
CCS214
Remote_Subsystem_INI
< GEM12 Y
N
CCS215
Remote_Subsystem_SBSY
< GEM12 Y
N
CCS216
Remote_Subsystem_Avail
< GEM12 N
N
CCS217
Local_Subsystem_OFFL
localSubsysStateChange
< GEM12 Y
N
CCS218
Local_Subsystem_MBSY
< GEM12 Y
N
CCS219
Local_Subsystem_SBSY
< GEM12 Y
N
CCS220
Local_Subsystem_INSV
< GEM12 N
N
CCS221
SST_for_Local_SS
SSTforlocalSubSystem
< GEM12 Y
N
CCS222
SSP_Unknown_Remote_SS
unknownSSPreceived
< GEM12 Y
N
CCS223
SSA_Unknown_Remoet_SS
unknownSSAreceived
< GEM12 Y
N
CCS224
No_reply_SST_Invd_CGPA
unableToSSTreply
< GEM12 Y
N
CCS225
PC_recently_deleted
pcDeleteFrmC7NETSSN
< GEM12 Y
N
CCS228
GT_Link_Msg-Net_Addr
invalidNetAddress
< GEM12 Y
N
CCS231
Local_Subsystem_ISTB
< GEM12 Y
N
CCS232
Lss_Instance_OFFL
localSSIStateChange
< GEM12 Y
N
—sheet 8 of 50—
GSM18/UMTS04
4-10 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
CCS233
Lss_Instance_MBSY
localSSIStateChange
< GEM12 Y
N
CCS234
Lss_Instance_SBSY
localSSIStateChange
< GEM12 Y
N
CCS235
Lss_Instance_Avail
localSSIStateChange
< GEM12 N
N
CCS236
Lss_Instance_ISTB
localSSIStateChange
< GEM12 Y
N
CCS238
Invalid_CSCC_Msg
invalidMsg
< GEM12 Y
N
CCS239
Inv_CSCC_LSS_Request
invalidMsg
< GEM12 Y
N
CCS240
Invalid_TFMI_Msg
invalidMsg
< GEM12 Y
N
CCS242
SCCP_Missing_Datafill
missingGTTYPE
< GEM12 Y
N
CCS245
UDTS_received
UDTSreceived
< GEM12 Y
N
CCS246
Route_on_PC_CDPA_received
UDTMsgWithCDPA
< GEM12 Y
N
CCS248
Data_Download
dataDownLoadFailure
< GEM12 Y
N
CCS249
Invd_Optnl_Parm_in_Msg
invalidOption
< GEM12 Y
N
CCS250
Local_SSI_Application_trouble
localSSIapplTrbl
< GEM12 Y
N
CCS251
Lss_Instance_Deload
localSSIStateChange
< GEM12 Y
N
CCS252
Local_Subsystem_DLD
< GEM12 Y
N
CCS253
Segmentation/Reassembly
segmentation/ReassemblyError
< GEM12 Y
N
CCS254
CM_Routing_Failure
routingFailure
< GEM12 Y
N
CCS255
SCCP_Routing_Failure
routingFailure
< GEM12 Y
N
CCS256
SCCP_Routing_Report
routingFaulureSummary
< GEM12 Y
N
CCS296
SCCP_Router_Trace
routingTrace
< GEM12 Y
N
CCS400
ILLP_Path_Failure
ILLPpathFailure
< GEM12 Y
N
CCS401
ILLP_Path_Recovery
ILLPpathRecovery
< GEM12 Y
N
CCS402
ILLP_Path_Failures
ILLPpathFailure
< GEM12 Y
N
CCS403
ILLP_Path_Recoveries
ILLPpathRecovery
< GEM12 Y
N
—sheet 9 of 50—
411-8111-803
Standard
01.06
May 2006
Logs index 4-11
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
CCS404
ILLP_Path_Not_Reported
ILLPpathNotReported
< GEM12 Y
N
CCS500
Screening_threshold
screeningThresholdCrossed
< GEM12 Y
N
CCS501
MSU_threshold
MSUthresholdCrossed
< GEM12 Y
N
CCS502
Screening_failure
screeningFault
< GEM12 Y
N
CCS503
Screening_error
screeningFault
< GEM12 Y
N
CCS504
Download_failure
tblOperationFailure
< GEM12 Y
N
CCS505
Screening_aborted
screeningFault
< GEM12 Y
N
CCS506
Screening_monitor
screeningINFO
< GEM12 Y
N
CCS601
System_Action
dataSyncFailure
< GEM12 Y
N
CCS751
CCS7_Server_Data_Audit
c7svrDataAudit
< GEM12 Y
N
CCS889
CCS7_Server_Overload
congestion
< GEM12 Y
N
CCS891
CCS7_Server_Unavailable
mmuStateChange
< GEM12 N
Y
CCS892
CCS7_Server_Available
mmuStateChange
< GEM12 N
Y
CCS895
CCS7_Server_OffLine
mmuStateChange
< GEM12 N
Y
CCS896
CCS7_Server_ManBusy
mmuStateChange
< GEM12 N
Y
CCS897
CCS7_Server_System_Busy
mmuStateChange
< GEM12 N
Y
CCS730
Routeset_Xlist_Mismatch
ddmAuditFailure
< GEM12 Y
N
CCS731
Route_Xlist_Mismatch
ddmAuditFailure
< GEM12 Y
N
CM100
CM_REPORT
cmDailySummary
< GEM12 Y
N
CM101
CM_STATUS
cmJamStateChange
< GEM12 Y
Y
CM102
CM_STATUS
cmSyncStatus
< GEM12 N
Y
CM103
HIGH_TRAP_RATE
highTrapRate
< GEM12 N
Y
CM176
CMMNT_ALARM_CLEARED
highTrapRate
< GEM12 N
Y
CM104
MC_STATUS_CHANGE
mcStatusChange
< GEM12 N
Y
GSM18/UMTS04
4-12 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
CM105
MC_STATUS_CHANGE
mcStatusChange
< GEM12 N
Y
CM106
MC_STATUS_CHANGE
mcStatusChange
< GEM12 N
Y
CM107
MC_STATUS_CHANGE
mcStatusChange
< GEM12 N
Y
CM108
MC_STATUS_CHANGE
mcStatusChange
< GEM12 N
Y
CM109
MC_STATUS_CHANGE
mcStatusChange
< GEM12 N
Y
CM110
MC_STATUS_CHANGE
mcStatusChange
< GEM12 N
Y
CM111
RUNNING_OUT_OF_MEMORY
outOfMemory
< GEM12 Y
Y
CM112
MEM_CARD_FAULT
memCardStateChange
< GEM12 Y
Y
CM113
MEM_CARD_IN_SERVICE_
TROUBLE
memCardStateChange
< GEM12 Y
Y
CM114
MEM_CARD_OK
memCardStateChange
< GEM12 N
Y
CM115
LOSS_OF_TOD_TIME
todFault
< GEM12 Y
Y
CM116
IMAGE_TEST_FAILED
imageTestResult
< GEM12 N
Y
CM117
IMAGE_TEST_PASSED
imageTestResult
< GEM12 N
Y
CM119
trap
< GEM12 Y
Y
CM120
cmRestart
< GEM12 Y
Y
CM121
REX_PASS
rexTestINFO
< GEM12 N
Y
CM122
REX_TEST
rexTestINFO
< GEM12 N
Y
CM123
LOW_SPARE_MINOR_
CONDITION
lowMemory
< GEM12 Y
Y
CM124
CPU_PASS
cpuStateChange
< GEM12 N
Y
CM125
CPU_TEST
cpuStateChange
< GEM12 N
Y
CM126
PRIMARY_AUTOLOAD_
DEVICE_CHANGE
primaryAutoldDeviceINFO
< GEM12 Y
Y
CM127
CM_SYNC_FAILURE
cmSyncStatus
< GEM12 N
Y
CM128
MC_LINKHIT_DATA
mcLinkFault
< GEM12 Y
Y
411-8111-803
Standard
01.06
May 2006
Logs index 4-13
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
CM129
TIME-OF-DAY_CLOCK_OUT_
OF_SERVICE
mcStatusChange
< GEM12 N
Y
CM130
SSC_STATUS_CHANGE
sscStatusChange
< GEM12 N
Y
CM131
INVALID_AUTOLOAD_ROUTE
autoloadFault
< GEM12 Y
Y
CM132
PMC-NODE_STATUS_CHANGE pmcStateChange
< GEM12 N
Y
CM133
< GEM12 N
Y
CM134
< GEM12 N
Y
CM135
< GEM12 N
Y
CM136
PMC-PORT_STATUS_CHANGE pmcStateChange
< GEM12 N
Y
CM137
< GEM12 N
Y
CM138
< GEM12 N
Y
CM140
PMC_LINK_HIT_DATA
pmcLinkFault
< GEM12 Y
Y
CM141
SPLIT_CM_MODE_FAULT
splitModeFault
< GEM12 Y
N
CM142
PMC-NODE_TEST_RESULT
pmcStateChange
< GEM12 N
Y
CM143
PMC-PORT_TEST_RESULT
pmcStateChange
< GEM12 N
N
CM144
SSC_ROUTE_SWITCH
sscRouteChange
< GEM12 Y
N
CM145
SSC_TEST_FAILURE
sscStatusChange
< GEM12 N
Y
CM146
REX_TEST_CLASS_DID_NOT_ rexResourceUnavailable
RUN
< GEM12 Y
N
CM147
PMC_XBUS_TEST_RESULT
xbusTestINFO
< GEM12 Y
Y
CM148
PMC_PORT_FAULTY_-
pmcStateChange
< GEM12 N
Y
CM149
PMC_SPLIT_STATUS_-
splitStatusINFO
< GEM12 Y
N
CM150
CM_SYNC_COMPLETE
cmSyncStatus
< GEM12 N
Y
CM151
DIRECT_LOADMATE_RESULT_ directLoadmateINFO
-
< GEM12 Y
N
GSM18/UMTS04
4-14 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
CM152
PERIPHERAL_INTERRUPT_
RECEIVED
cmSyncStatus
< GEM12 N
Y
CM153
TOD_TOLERANCE_AUDIT
timingProblem
< GEM12 Y
Y
CM154
REX_TEST_FAILED_SETUP
rexTestINFO
< GEM12 N
Y
CM155
IMAGE_TEST_INFO
imageTestResult
< GEM12 N
Y
CM157
INVENTORY_ERROR
inventoryMismatch
< GEM12 Y
N
CM158
LOW_SPARE_MAJOR_
CONDITION
lowMemory
< GEM12 Y
Y
CM159
CM_STATUS_CHANGE
cmSyncStatus
< GEM12 N
Y
CM160
CM_HW_MONITOR
hwMonitorReport
< GEM12 Y
N
CM162
PROCESSOR_CLOCK_FAULT
cpuStateChange
< GEM12 N
Y
CM163
E2A_LINK_FAULT
cpuStateChange
< GEM12 N
Y
CM164
PROCESSOR_MEMORY_FAULT memCardStateChange
< GEM12 N
Y
CM165
PROCESSOR_OPTION_
ERROR
processorOptionError
< GEM12 Y
Y
CM166
SRAM_CORRECTION
SRAMcorrection
< GEM12 Y
Y
CM167
SRAM_AUDIT_STATE_CHANGE SRAMauditStateChange
< GEM12 Y
Y
CM168
SRAM_MINOR_ALARM
SRAMalarm
< GEM12 Y
Y
CM169
SRAM_SYNC_PREVENTION
SRAMalarm
< GEM12 Y
Y
CM170
SRAM_COUNTER_CLEARED
SRAMcounterINFO
< GEM12 Y
Y
CM171
SRAM_SYNC_OVERRIDE
SRAMsyncOverride
< GEM12 Y
Y
CM172
SRAM_SWACT_OVERRIDE
SRAMswactOverride
< GEM12 Y
Y
CM173
SRAM_REX_OVERRIDE
SRAMrexOverride
< GEM12 Y
Y
CM174
INVALID_MEMORY_
CONFIGURATION
memConfigurationFault
< GEM12 Y
Y
CM175
STORE_APPROACHING_
MEMORY_LIMIT
outOfMemory
< GEM12 Y
Y
411-8111-803
Standard
01.06
May 2006
Logs index 4-15
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
CM176
CMMNT_ALARM_CLEARED
highTrapRate
< GEM12 N
Y
CM178
APPROACHING_SLM_LIMIT
SLMthresholdCrossed
< GEM12 Y
Y
CM179
CM_REX_GENERIC_REPORT
cmRexINFO
< GEM12 Y
N
CM180
EXCEEDED_SLM_LIMIT
SLMthresholdCrossed
< GEM12 Y
Y
CM181
STORE_ALLOCATOR_LIMIT_
REACHED
memAllocationFault
< GEM12 Y
Y
DDM101
dataLoadingFailure
< GEM12 Y
N
DDM106
auditFailure
< GEM12 Y
N
DDM107
omRetrievalFailure
< GEM12 Y
N
DDM108
softwareError
< GEM12 Y
N
DDM109
auditINFO
< GEM12 Y
N
DDM110
auditFailure
< GEM12 Y
N
ioError
< GEM12 Y
N
DDU201
dmsStateChange
< GEM12 N
Y
DDU202
dmsStateChange
< GEM12 N
Y
DDU203
dmsStateChange
< GEM12 N
Y
DDU204
dmsStateChange
< GEM12 N
Y
DDU205
dmsStateChange
< GEM12 N
Y
DDU208
equipmentMalfunction
< GEM12 Y
N
DDU209
dmsStateChange
< GEM12 N
Y
DDU210
incomingMsgOverload
< GEM12 Y
N
DDU211
dmsStateChange
< GEM12 N
Y
DDU212
diagnosticTestFailed
< GEM12 Y
N
DDU101
IO_ERROR
DDU213
Fault_Cleared
incomingMsgOverload
< GEM12 Y
N
DDU214
MISC
miscINFO
< GEM12 Y
N
GSM18/UMTS04
4-16 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
DIRP101
DIRP_FLOW_LOG
miscINFO
< GEM12 Y
Y
DISK101
VOLUME_DELETED
diskVolumeINFO
< GEM12 Y
N
DISK103
VOLUME_CREATED
diskVolumeINFO
< GEM12 Y
N
DISK301
Unable_to_open_disk
diskUnavailable
< GEM12 Y
N
DISK302
Unable_to_open_disk_volume
diskUnavailable
< GEM12 Y
N
DISK303
VFSM_error
VFSMerror
< GEM12 Y
N
DISK304
FD_error
FDerror
< GEM12 Y
N
DISK305
VOL1_error
VOL1error
< GEM12 Y
N
DPAC101
Controller_Error
miscINFO
< GEM12 Y
N
DPAC102
Software_Error
miscINFO
< GEM12 Y
N
DPAC103
dmsStateChange
< GEM12 N
Y
DPAC104
dmsStateChange
< GEM12 N
Y
DPAC105
Fault_Cleared
dmsStateChange
< GEM12 N
Y
DRM300
Low_Resource_Warning
lowResourceWarning
< GEM12 Y
N
DRM600
System_Action
miscINFO
< GEM12 Y
N
ENCP100 ENET_Integrity_Fault
IntegrityINFO
< GEM12 Y
N
ENCP101 ENET_Single_Ended_Integrity
IntegrityINFO
< GEM12 Y
N
ENCP102 ENET_Integrity_Diagnostics
IntegrityINFO
< GEM12 Y
N
ENCP103 ENET_Integrity_Audit
IntegrityAuditINFO
< GEM12 Y
N
ENCP131 Connection_Overwritten
ConnectionOverwritten
< GEM12 Y
N
ENCP132 Attempt_To_Overwritten
AttemptToOverwritten
< GEM12 Y
N
ENCP133 ENCP_Log_Audit
ENCPLogINFO
< GEM12 Y
N
ENCP134 Attempt_To_Reserve_
Unconnected
AttemptToReserv
< GEM12 Y
N
ENCP135 Illegal_Attempt_To_Reverse
IllegalAttempt
< GEM12 Y
N
411-8111-803
Standard
01.06
May 2006
Logs index 4-17
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
ENET100
dmsStateChange
< GEM12 N
Y
ENET101
dmsStateChange
< GEM12 N
Y
ENET102
dmsStateChange
< GEM12 N
Y
ENET103
dmsStateChange
< GEM12 N
Y
ENET104
dmsStateChange
< GEM12 N
Y
ENET105
dmsStateChange
< GEM12 N
Y
ENET106
dmsStateChange
< GEM12 N
Y
ENET107
dmsStateChange
< GEM12 N
Y
ENET108
dmsStateChange
< GEM12 N
Y
ENET110
ENET_Node_Test
< GEM12 Y
N
ENET111
ENET_Node_Test
< GEM12 Y
N
ENET113
ENET_System_Recovery
rtsOperationINFO
< GEM12 N
N
ENET114
ENET_Parallel_Recovery
Summary
< GEM12 Y
N
ENET120
Boot_File_Test
< GEM12 Y
N
ENET200
dmsStateChange
< GEM12 N
Y
ENET201
dmsStateChange
< GEM12 N
Y
ENET202
dmsStateChange
< GEM12 N
Y
ENET203
dmsStateChange
< GEM12 N
Y
ENET204
dmsStateChange
< GEM12 N
Y
ENET205
dmsStateChange
< GEM12 N
Y
ENET206
dmsStateChange
< GEM12 N
Y
ENET207
dmsStateChange
< GEM12 N
Y
ENET208
warning
< GEM12 N
Y
circuitPackFault
< GEM12 Y
N
ENET211
ENET_Card_Test
GSM18/UMTS04
4-18 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
ENET220
ENET_Matrix_Test
circuitPackFault
< GEM12 Y
N
ENET221
ENET_Matrix_Test
circuitPackFault
< GEM12 Y
N
ENET223
ENET_Ripple_Open
shelfProblem
< GEM12 Y
N
ENET230
ENET_Card_State_Checker_
result
< GEM12 Y
N
ENET300
dmsStateChange
< GEM12 N
Y
ENET301
dmsStateChange
< GEM12 N
Y
ENET302
dmsStateChange
< GEM12 N
Y
ENET303
dmsStateChange
< GEM12 N
Y
ENET304
dmsStateChange
< GEM12 N
Y
ENET305
dmsStateChange
< GEM12 N
Y
ENET306
dmsStateChange
< GEM12 N
Y
ENET307
dmsStateChange
< GEM12 N
Y
ENET308
dmsStateChange
< GEM12 N
Y
ENET309
dmsStateChange
< GEM12 N
Y
ENET310
ENET_PSide_Link_Test
circuitPackFault
< GEM12 N
N
ENET311
ENET_PSide_Link_Test
circuitPackFault
< GEM12 Y
N
ENET312
ENET_PSide_Link_Reswitching_ circuitPackFault
Me
< GEM12 Y
N
ENET313
ENET_PSide_Link_Message_
Path
circuitPackFault
< GEM12 Y
N
ENET315
ENET_PSide_MTCE_
Parameter_Change
mtceINFO
< GEM12 Y
N
ENET400
ENET_Control_Side_Link_Fault
c-sideLinkFault
< GEM12 Y
N
ENET401
ENET_Control_Side_Link_Test
c-sideLinkFault
< GEM12 Y
N
ENET402
ENET_Control_Side_Link_Fault
c-sideLinkFault
< GEM12 Y
N
411-8111-803
Standard
01.06
May 2006
Logs index 4-19
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
ENET403
ENET_Reference_Link_Switched referenceLinkINFO
< GEM12 Y
N
ENET404
Switch_Reference_Link_Failed
referenceLinkINFO
< GEM12 Y
N
ENET500
ENET_REX_Scheduled_Test
rexINFO
< GEM12 Y
N
ENET501
ENET_REX_Scheduling_by_
SREX_Controller
rexINFO
< GEM12 Y
N
ENET502
ENET_REX_Test_Unaable_to_
Run
rexINFO
< GEM12 Y
N
ENET503
ENET_REX_Test_Started
rexINFO
< GEM12 Y
N
ENET504
ENET_REX_Test_Passed
rexINFO
< GEM12 Y
N
ENET506
ENET_REX_Test_Aborted
rexINFO
< GEM12 Y
N
ENET507
ENET_REX_Test_Incomplete
rexINFO
< GEM12 Y
N
ENET508
ENET_REX_Test_Passed-With_ rexINFO
In_service
< GEM12 Y
N
ENET509
ENET_REX_Test_Unable_to_
Run
rexINFO
< GEM12 Y
N
ENET510
ENET_NODE_REX_Test
nodeRexINFO
< GEM12 Y
N
ENET511
ENET_NODE_REX_Test
nodeRexINFO
< GEM12 Y
N
ENET520
ENET_MATRIX_REX_Test
matrixRexINFO
< GEM12 Y
N
ENET521
ENET_MATRIX_REX_Test
matrixRexINFO
< GEM12 Y
N
ENET700
ENET_Command_Warnings_
Ignored
miscINFO
< GEM12 Y
N
EXT100
scanPointDetect
< GEM12 N
Y
EXT101
scanPointDetect
< GEM12 N
Y
EXT102
scanPointDetect
< GEM12 N
Y
EXT103
scanPointDetect
< GEM12 N
Y
EXT105
scanPointDetect
< GEM12 N
Y
EXT106
scanPointDetect
< GEM12 Y
Y
GSM18/UMTS04
4-20 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
EXT107
scanPointDetect
< GEM12 N
Y
EXT108
scanPointDetect
< GEM12 N
Y
EXT109
scanPointDetect
< GEM12 N
Y
FC0100
COMMUNICATION_
ESTABLISHED_TO_SDM
LAQ_connectionINFO
GEM15
Y
N
FC0101
COMMUNICATION_FAILED_
TO_SDM
LAQ_connectionINFO
GEM15
Y
N
FP300
Hardware_Fault
hardwareFault
< GEM12 Y
N
FP301
Hardware_Fault
hardwareFault
< GEM12 Y
N
FP304
Software_Error
softwareError
< GEM12 Y
N
FP305
Software_Error
softwareError
< GEM12 Y
N
FP351
Hardware_Fault
hardwareFault
< GEM12 Y
N
FP354
Mismatch_Fault
mismatchFault
< GEM12 Y
N
FP503
Device_State_Change
dmsStateChange
< GEM12 N
Y
FP504
SCSI_State_Change
dmsStateChange
< GEM12 N
Y
FP505
State_Change
stateChange
< GEM12 Y
N
FP552
Resource_State_Change
stateChange
< GEM12 N
Y
FP600
Audit_Action
auditINFO
< GEM12 Y
N
FP601
Software_Alarm
softwareError
< GEM12 Y
N
GHLR300 Overload_Onset
overloadOnset
< GEM12 Y
N
GHLR302 Overload_Abatement
overloadAbatement
< GEM12 N
N
GHLR303 Checksum_Validation_Failure
checksumValidationFailed
< GEM12 Y
N
GHLR304 AUC_Failure
AUCFailure
< GEM12 Y
N
GHLR305 Link_Overload_Detection_by_
HLR
congestion
< GEM12 Y
N
GHLR306 Resource_Limitation
softwareError
< GEM12 Y
N
411-8111-803
Standard
01.06
May 2006
Logs index 4-21
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
GHLR307 Resource_Audit
softwareError
< GEM12 Y
N
GHLR320 MAX_JRNL_BOUNCES_
exceeded
MAX_JRNL_BOUNCES_
exceeded
GEM15
Y
N
GHLR401 Hourly_Report
hlrSummary
< GEM12 Y
N
GHLR511 SDM_AC_Version_Rejected
SDMACversionMismatch
< GEM12 Y
N
GHLR611 Database_Journalling_Failed
journallingFailed
< GEM12 Y
N
GHLR612 GHLRVLR_Journalling_Failed
journallingFailed
< GEM12 Y
N
GHLR613 SYNCVLR_Required
syncVLRrequired
< GEM12 Y
N
GHLR616 Password_Journalling_Failed
journallingFailed
< GEM12 Y
N
GHLR624 OCIC_Journalling_failed
journallingFailed
< GEM12 Y
N
GHLR665 Table_GHLRVLR_Resource_
Limitation_Crossed
tblResourceThresholdCrossed
< GEM12 Y
N
GHLR684 Table_GHLRSGSN_Journalling_ fileError
Failed
< GEM12 Y
N
GHLR685 Table_GHLRSGSN_Resource_
limitation_Approached
resourceAtOrNearingCapacity
< GEM12 Y
N
GHLR687 Table_GHLRSGSN_journalled_
tupl...
journallingFailed
GEM15
Y
N
GHLR805 Standby_Processes_and_
Queues_Log
softwareProgramAbnormallyTerm < GEM12 Y
inated
N
GHLR690 Authentication_failure
AuthenticationFailureINFO
< GEM12 Y
N
GHLR691 Resynchronisation_report
ResynchronizationINFO
< GEM12 Y
N
GHLR692 Sequence_number_data
< GEM12 Y
N
GHLR807 Standby_Memory_Allocation
< GEM12 Y
N
GHLR811 Table_GHLRSIMR_Resource_
Limitation_Approached
< GEM12 Y
N
GHLR682 ATM/DTM_Messaging_Failure
communicationsSubsystemFailur < GEM12 Y
e
N
GSM18/UMTS04
4-22 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
GHLR801 Standby_System_Data_
Inconsistent
databaseError
< GEM12 Y
N
GHLR802 Standby_Service_Error
softwareError
< GEM12 Y
N
GHLR803 Standby_Maintenance_Error
communicationsProtocolError
< GEM12 Y
N
GHLR810 HLR_Database_OMs_Incorrect
databaseError
< GEM12 Y
N
GHLR817 Standby_Alarm_State
StandbyAlarmStateChange
GEM15
Y
N
GIWF300
Datafill_Fault
datafillMissing
GEM13
Y
N
GIWF301
Mismatch_Fault
datafillFault
GEM13
Y
N
GIWF600
System_Action
applFailedToRespond
GEM13
Y
N
GIWF601
System_Action
invalidMsg
GEM13
Y
N
GIWF602
Fail_Completion
failCompletion
GEM13
Y
N
GIWF620
Test_Call_Record
msc/iwfInterfaceINFO
GEM13
Y
N
GIWF630
Audit_Action
iwfAuditRPT
GEM13
Y
N
GIWF631
Audit_Action
gppAuditRPT
GEM13
Y
N
GMMU101 MMU_Minor_Log
mmuMinorProblem
GEM15
Y
N
GMMU102 MMU_Major_Log
mmuMajorProblem
GEM15
Y
N
GMMU103 MMU_Critical_Log
mmuCriticalProblem
GEM15
Y
N
GMMU104 MMU_TRAP/SWER
mmuTrap
GEM15
Y
N
GMSC300 Datafill_Fault
datafillMissing
< GEM12 Y
N
GMSC301 Resource_Unavailable
resourceUnavailable
< GEM12 Y
N
GMSC302 Datafill_Fault
datafillFault
< GEM12 Y
N
GMSC613 System_Action
failComplete
GEM15
Y
N
GMSC618 Malicious_Call_Trace
callDurationTooLong
GEM15
Y
N
GMSC620 MMU_Server_Available
dmsStateChange
GEM12
N
N
GMSC622 MMU_Server_Overload
dmsStateChange
GEM12
N
N
411-8111-803
Standard
01.06
May 2006
Logs index 4-23
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
GMSC621 MMU_Server_Pool_Available
dmsStateChange
GEM12
N
N
GMSC623 MMU_Server_Pool_Overload
dmsStateChange
GEM12
N
N
GMSC624 MMU_Server_Pool_Overload_
Hypothetically
dmsStateChange
GEM12
N
N
GMSC627 MMU_Server_Pool_Cleared_
hypothetically
dmsStateChange
GEM12
N
N
GMSC625 MMU_Hardware_Sparing_
violation
processorProblem
GEM12
Y
N
GMSC626 MMU_Dynamic_Data_Update_
Failure
processorProblem
GEM12
Y
N
GVAP310
Parm_pool_could_not_be_
extended
AutoProvisioningInfo
GEM15
Y
N
GVAP600
Pool_has_increased_in_size
GEM15
Y
N
GVAP650
Parm_changed_automation_
status
GEM15
Y
N
GVLR300 Resource_Unavailable
resourceUnavailable
< GEM12 Y
N
GVLR301 Resource_Unavailable
softwareError
< GEM12 Y
N
GVLR601 System_Action
systemINFO
< GEM12 Y
N
IOD101
dmsStateChange
< GEM12 N
Y
IOD102
dmsStateChange
< GEM12 N
Y
IOD103
dmsStateChange
< GEM12 N
Y
IOD104
dmsStateChange
< GEM12 N
Y
IOD105
dmsStateChange
< GEM12 N
Y
IOD106
dmsStateChange
< GEM12 N
Y
IOD107
dmsStateChange
< GEM12 N
Y
IOD108
dmsStateChange
< GEM12 N
Y
IOD109
dmsStateChange
< GEM12 N
Y
GSM18/UMTS04
4-24 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
IOD110
dmsStateChange
< GEM12 N
Y
IOD111
dmsStateChange
< GEM12 N
Y
IOD112
dmsStateChange
< GEM12 N
Y
IOD113
dmsStateChange
< GEM12 N
Y
IOD114
dmsStateChange
< GEM12 N
Y
IOD117
msgTransferDefect
< GEM12 Y
N
IOD118
msgTransferDefect
< GEM12 Y
N
IOD119
msgTransferDefect
< GEM12 Y
N
IOD120
mismatchFault
< GEM12 Y
N
IOD121
mismatchFault
< GEM12 Y
N
IOD122
iocTestINFO
< GEM12 Y
N
IOD123
MDN
iocTestINFO
< GEM12 Y
N
IOD124
SEQ
iocTestINFO
< GEM12 Y
N
IOD125
PAT
iocTestINFO
< GEM12 Y
N
IOD126
CLKSTS
iocTestINFO
< GEM12 Y
N
IOD127
IOCSTS
iocTestINFO
< GEM12 Y
N
IOD128
iocTestINFO
< GEM12 Y
N
IOD129
iocTestINFO
< GEM12 Y
N
iocTestINFO
< GEM12 Y
N
IOD201
dmsStateChange
< GEM12 N
Y
IOD202
dmsStateChange
< GEM12 N
Y
IOD203
dmsStateChange
< GEM12 N
Y
IOD204
dmsStateChange
< GEM12 N
Y
IOD205
dmsStateChange
< GEM12 N
Y
IOD130
IOM_TEST
411-8111-803
Standard
01.06
May 2006
Logs index 4-25
Table 4-1
Log
Name
OMC-S Description
Clear
Override
(Y / N) (Y / N)
IOD206
< GEM12 Y
N
IOD207
< GEM12 Y
N
IOD208
sanityTimeout
< GEM12 Y
N
IOD209
transientFault
< GEM12 Y
N
IOD210
< GEM12 Y
N
IOD211
mtdTestINFO
< GEM12 Y
N
< GEM12 Y
N
IOD213
mtdTestINFO
< GEM12 Y
N
IOD214
< GEM12 Y
N
IOD215
< GEM12 Y
N
IOD301
dmsStateChange
< GEM12 N
N
IOD302
dmsStateChange
< GEM12 N
N
IOD303
dmsStateChange
< GEM12 N
N
IOD304
dmsStateChange
< GEM12 N
N
IOD305
dmsStateChange
< GEM12 N
N
IOD306
consoleFault
< GEM12 Y
N
IOD307
iodTestINFO
< GEM12 Y
N
IOD308
consoleFault
< GEM12 Y
N
IOD309
iodTestINFO
< GEM12 Y
N
consoleFault
< GEM12 Y
N
IOD311
consoleFault
< GEM12 Y
N
IOD312
logDevicePbsy
< GEM12 Y
N
IOD313
logDevicePbsy
< GEM12 N
N
consoleFault
< GEM12 N
N
IOD212
IOD310
IOD315
Log Header
FS
FS
Fault_Cleared
GSM18/UMTS04
4-26 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
IOD600
TTY_SMDI_Audit_Report
smdiFailure
< GEM12 Y
N
IOD610
IOM_Load_Status
iomLoadINFO
< GEM12 Y
N
ISDN100
Terminal_Unavailable
terminalUnavailable
< GEM12 Y
N
ISDN101
Loop_Unavailable
loopUnavailable
< GEM12 Y
N
ISDN102
TEI_Removed
teiINFO
< GEM12 Y
N
ISDN103
Channel_Info
channelINFO
< GEM12 Y
N
ISDN104
Bd_Sync_Loss
bdSyncLoss
< GEM12 Y
N
ISDN105
PRA_Sync_Loss
PRASyncLoss
< GEM12 Y
N
ISDN106
D_Chnl_L1_Autonomous_Failed D-channelINFO
< GEM12 Y
N
ISDN107
TEI_Autonomous_Restore_
Failed
teiINFO
< GEM12 Y
N
ISDN108
TEI_Autonomous_Restored
teiINFO
< GEM12 Y
N
ISDN109
D_Chnl_L1_Autonomous_
Restored
D-channelINFO
< GEM12 Y
N
ISDN110
PRA_D-CHANNEL_STATUS
D-channelStatus
< GEM12 Y
N
ISDN111
PRA_D-CHANNEL_MAJOR_
ALARM
D-channelStatus
< GEM12 Y
N
ISDN112
PRA_D-CHANNEL_CRITICAL_
ALARM
D-channelStatus
< GEM12 Y
N
ISDN113
PRA_D-CHANNEL_MANUAL_
SWACT
D-channelStatus
< GEM12 Y
N
ISDN114
PRA_D-CHANNEL_
AUTONOMOUS_SWACT
D-channelStatus
< GEM12 Y
N
ISDN115
Subscription_limits_exceeded
communicationsProtocolError
< GEM12 Y
N
ISDN116
TEI_has_not_been_assigned
teiINFO
< GEM12 Y
N
ISDN118
PRA_Sync_Established
PRASyncLoss
< GEM12 Y
N
ISDN301
Layer_3_Protocol_Abnormaility
protocolINFO
< GEM12 Y
N
411-8111-803
Standard
01.06
May 2006
Logs index 4-27
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
ISDN302
Parameter_Downloading_
Abnormal
miscINFO
< GEM12 Y
N
ISDN304
Layer_2_Protocol_Abnormality
protocolINFO
< GEM12 Y
N
ITN315
IP_Table_Data_Mismatch
dataMismatch
< GEM12 Y
N
ITOC100
XA_ITOC
datafillError
< GEM12 Y
N
ITOC101
XA_ITOC
datafillError
< GEM12 Y
N
KTRK100
KTRK_REPORT
killerTrunkINFO
< GEM12 Y
N
limSystemINFO
< GEM12 Y
N
LMSC600
MFC111
Action
thresholdCrossed
< GEM12 Y
N
MM100
MISMATCH
mismatchINFO
< GEM12 Y
N
MM111
MM_RECOVERY
mismatchRecovery
< GEM12 Y
N
MM112
MM_RECOVERY
mismatchRecovery
< GEM12 Y
N
MM113
MM_RECOVERY
mismatchRecovery
< GEM12 Y
N
MOD101
BAD_MODULE_TABLE_OWNER softwareError
< GEM12 Y
Y
MOD129
BAD_PROCEDURE_
DESCRIPTOR
softwareError
< GEM12 Y
Y
MOD157
SEVERE_CHECKSUM_
DISCRPENCY
softwareError
< GEM12 Y
Y
MOD100
MODULE_TABLE_ADDRESS_
MISMATCH
addressMismatch
< GEM12 Y
N
MOD102
BAD_MODULE_TABLE_
STORE_TYPE
badStoreType
< GEM12 Y
N
MOD103
DIRECTORY_TABLE_SIZE_
MISMATCH
sizeMismatch
< GEM12 Y
N
MOD104
TABLE_SIZE_MISMATCH
sizeMismatch
< GEM12 Y
N
MOD105
TABLE_COUNT_ERROR
tableCounterError
< GEM12 Y
N
MOD106
TABLE_INITIAL_SIZE_OF_
ZERO
initSizeFault
< GEM12 Y
N
GSM18/UMTS04
4-28 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
MOD107
TABLE_SIZE_INCREMENT_OF_ tableIncrementFault
ZERO
< GEM12 Y
N
MOD108
BAD_SST_ENTRY
badSSTEntry
< GEM12 Y
N
MOD109
CONFLICTING_HEAD_
SEGMENT_ERROR
badHeadSegmentData
< GEM12 Y
N
MOD110
HEAD_SEGMENT_DATA_
ERROR
badHeadSegmentData
< GEM12 Y
N
MOD111
UNNAMED_MODULE
unnamedModule
< GEM12 Y
N
MOD112
BAD_EDITION_CODE
badEditionCode
< GEM12 Y
N
MOD113
CONFLICTING_MODULE_
STATUS_FLAG
badEntry
< GEM12 Y
N
MOD114
INVALID_MODULE_PACKAGE
wrongModulePackage
< GEM12 Y
N
MOD115
INVALID_MODULE_TYPE
wrongModuleType
< GEM12 Y
N
MOD116
BAD_DEFINITIONS_MODULE_ badDefinitions
ENTRY
< GEM12 Y
N
MOD117
BASE_REGISTER_SST_
MISMATCH
mismatchFault
< GEM12 Y
N
MOD118
BASE_REGISTER_USED_
TWICE
baseRegisterUsedTwice
< GEM12 Y
N
MOD119
PRIVATE_DATA_ERROR
privateDataError
< GEM12 Y
N
MOD120
USES_LIST_STRIDE_ERROR
strideError
< GEM12 Y
N
MOD121
DUPLICATE_USES_LIST_
REFERENCE
duplicateReferences
< GEM12 Y
N
MOD122
BAD_USES_LIST_REFERENCE badReference
< GEM12 Y
N
MOD123
USES_LIST_REFERENCE
moduleNotLoaded
< GEM12 Y
N
MOD124
BAD_PERPROCESS_USES_
LIST_REFERENCE
badReference
< GEM12 Y
N
MOD125
BAD_INTERPACKAGE_USES_
LIST_REF
missingReference
< GEM12 Y
N
411-8111-803
Standard
01.06
May 2006
Clear
Override
(Y / N) (Y / N)
Logs index 4-29
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
MOD126
BAD_USES_LIST_OFFSET
outOfRangeFault
< GEM12 Y
N
MOD127
BAD_PARENT_MODULE
outOfRangeFault
< GEM12 Y
N
MOD128
PROCEDURE_TABLE_ERROR
indexesMismatch
< GEM12 Y
N
MOD130
BAD_ENTRY_USAGE_FLAGS
badDataEntry
< GEM12 Y
N
MOD131
CONFLICTING_ENTRY_
USAGE_FLAGS
badDataEntry
< GEM12 Y
N
MOD132
BAD_ENTRY_PROCEDURE_
DESCRIPTOR
badDataEntry
< GEM12 Y
N
MOD133
INVALID_BASE_REGISTER_
STATUS
invalidType
< GEM12 Y
N
MOD134
USED_UNASSIGNED_BASE_
REGISTER
unassignedRegisterInUse
< GEM12 Y
N
MOD135
UNUSED_ASSIGNED_BASE_
REGISTER
assignedRegisterUnuse
< GEM12 Y
N
MOD136
DUPLICATE_ALIAS_ENTRY
duplicateAlias
< GEM12 Y
N
MOD137
BAD_ALIAS_ENTRY
badAlias
< GEM12 Y
N
MOD138
ALIAS_ENTRY_NOT_LOADED
moduleNotLoaded
< GEM12 Y
N
MOD139
DUPLICATE_IPL_ENTRY
duplicateIPL
< GEM12 Y
N
MOD140
BAD_IPL_ENTRY
badIPLEntry
< GEM12 Y
N
MOD141
IPL_ENTRY_NOT_LOADED
moduleNotLoaded
< GEM12 Y
N
MOD142
DUPLICATE_NEEDS_
REFERENCE
duplicateReference
< GEM12 Y
N
MOD143
BAD_NEEDS_REFERENCE
badReference
< GEM12 Y
N
MOD144
BAD_INTERPACKAGE_NEEDS_ badReference
REFERENCE
< GEM12 Y
N
MOD145
NEEDSIPL0_MISMATCH
mismatchFault
< GEM12 Y
N
MOD146
UNDEFINED_LOAD_INFO
invalidLoadINFO
< GEM12 Y
N
GSM18/UMTS04
4-30 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
MOD147
BAD_LOADINFO_TARGET_
PROCEDURE
invalidReference
< GEM12 Y
N
MOD148
INVALID_LOAD_INFO_
PROCESSING_TI
invalidLoadINFO
< GEM12 Y
N
MOD149
BAD_INITWITH_MASTER_
MODULE
badIndex
< GEM12 Y
N
MOD150
INITWITH_MASTER_MODULE_ badReference
NOT_LOAD
< GEM12 Y
N
MOD151
INITWITH_ONTO_NEEDED_
MODULE_IGNORED
doubleSpecification
< GEM12 Y
N
MOD152
DUPLICATE_INITWITH_
ASSOCATED_MODULE
moreThanOneINITWITH
< GEM12 Y
N
MOD153
BAD_INITWITH_ASSOCIATED_ unknownModule
MODULE
< GEM12 Y
N
MOD154
INITWITH_ASSOCIATED_
MODULE_NOT_LOADED
moduleNotLoaded
< GEM12 Y
N
MOD155
VALID_UNLOADED_ENTRY_
PROCEDURE
invalidData
< GEM12 Y
N
MOD156
SST_DISCREPANCY
sstDiscrepancy
< GEM12 Y
N
MOD158
CHECKSUM_DISCREPANCY
checksumFailure
< GEM12 Y
N
MOD159
INVALID_HEAD_SEGMENT_
STORETYPE
invalidHeadSegmentData
< GEM12 Y
N
MOD160
BILGE_MODULE_USES_
NONBILGE_MOD
invalidOperation
< GEM12 Y
N
MPC101
MPC_INFORMATION_REPORT mpcINFO
< GEM12 Y
N
MPC102
MPC_CONTROLLER_
REPORZT
mpcCtrlINFO
< GEM12 Y
N
MPC103
MPC_TRAPINFO_REPORT
mpcTrapINFO
< GEM12 Y
N
MPC104
MPC_AUDIT_REPORT
mpcAuditINFO
< GEM12 Y
N
411-8111-803
Standard
01.06
May 2006
Logs index 4-31
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
MPC105
MPC_CONFIGURATION_
CHANGE
mpcConfigINFO
< GEM12 Y
N
MPC106
MPC_PROCESS_REPORT
mpcProcINFO
< GEM12 Y
N
MPC201
MPC_FAST_APPLN_REPORT
mpcApplINFO
< GEM12 Y
N
MPC299
MPC_FAST_ERROR
mpcApplINFO
< GEM12 Y
N
MPC901
dmsStateChange
< GEM12 N
Y
MPC902
dmsStateChange
< GEM12 N
Y
MPC903
dmsStateChange
< GEM12 N
Y
MPC904
dmsStateChange
< GEM12 N
Y
MPC905
dmsStateChange
< GEM12 N
Y
MPC906
< GEM12 Y
N
MPC907
Fault_Cleared
< GEM12 Y
N
MPC908
MPC_LINK_STATUS
dmsStateChange
< GEM12 N
N
MS100
NODE_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS101
NODE_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS102
NODE_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS103
NODE_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS104
NODE
dmsStateChange
< GEM12 Y
N
MS105
MS_HW_MONITOR
hardwareMonitor
< GEM12 Y
N
MS208
FRNT_CARD
frontCardINFO
< GEM12 Y
N
MS238
BACK_CARD
backCardINFO
< GEM12 Y
N
MS248
SYSTEM_CARD
systemCardINFO
< GEM12 Y
N
MS260
INTERFACE_CARD_STATE_
CHANGE
dmsStateChange
< GEM12 N
Y
MS261
CHANGE
dmsStateChange
< GEM12 N
Y
GSM18/UMTS04
4-32 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
MS262
CHANGE
dmsStateChange
< GEM12 N
Y
MS263
dmsStateChange
< GEM12 N
Y
MS264
INTERFACE_CARD_STATE
dmsStateChange
< GEM12 N
Y
MS265
dmsStateChange
< GEM12 N
Y
MS266
dmsStateChange
< GEM12 N
Y
MS267
INTERFACE_CARD
dmsStateChange
< GEM12 N
Y
MS277
CHAIN_CARD
chainCardINFO
< GEM12 Y
N
MS280
CHNL_LINK_STATE_CHANGE
communicationsSubsystemFailur < GEM12 N
e
Y
MS281
e
Y
MS282
e
Y
MS283
e
Y
MS284
e
Y
MS285
e
Y
MS286
e
Y
MS287
CHNL_LINK
e
Y
MS300
PORT_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS301
PORT_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS302
PORT_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS303
PORT_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS304
PORT_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
411-8111-803
Standard
01.06
May 2006
Logs index 4-33
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
MS305
PORT_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS306
PORT_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS307
PORT
msPortINFO
< GEM12 Y
N
MS310
CHNL_LINK_PORT_STATE_
CHANGE
dmsStateChange
< GEM12 N
Y
MS311
CHANGE
dmsStateChange
< GEM12 N
Y
MS312
CHANGE
dmsStateChange
< GEM12 N
Y
MS313
CHANGE
dmsStateChange
< GEM12 N
Y
MS314
CHANGE
dmsStateChange
< GEM12 N
Y
MS315
CHANGE
dmsStateChange
< GEM12 N
Y
MS316
CHANGE
dmsStateChange
< GEM12 N
Y
MS317
CHNL_LINK_PORT
< GEM12 Y
N
MS318
CHNL_LINK_PORT_ST...
dmsStateChange
< GEM12 N
Y
MS320
IMSL_PORT_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS321
dmsStateChange
< GEM12 N
Y
MS322
dmsStateChange
< GEM12 N
Y
MS323
dmsStateChange
< GEM12 N
Y
MS324
dmsStateChange
< GEM12 N
Y
MS325
dmsStateChange
< GEM12 N
Y
MS326
dmsStateChange
< GEM12 N
Y
MS327
IMSL_PORT
softwareError
< GEM12 Y
N
MS400
FBUS_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
GSM18/UMTS04
4-34 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
MS401
FBUS_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS402
FBUS_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS403
FBUS_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS404
FBUS_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS405
FBUS_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS406
FBUS_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS407
FBUS
LFCRcvMsgFault
< GEM12 Y
N
MS408
FBUS_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS410
FBUS_TAP_STATE_CHANGE
dmsStateChange
< GEM12 N
Y
MS411
dmsStateChange
< GEM12 N
Y
MS412
dmsStateChange
< GEM12 N
Y
MS413
dmsStateChange
< GEM12 N
Y
MS414
dmsStateChange
< GEM12 N
Y
MS415
dmsStateChange
< GEM12 N
Y
MS417
FBUS_TAP
dmsStateChange
< GEM12 N
Y
MTCB100 Reqt_Dump
reqtElmntProblem
< GEM12 Y
N
MTCB101 Overflow_counters
overload
< GEM12 Y
N
MTCB102 Scratchpad_overflow
congestion
< GEM12 Y
N
MTCB104 Resource_Rel_by_audit
resourceReleased
< GEM12 Y
N
MTCB106 Lost_message
lossMessage
< GEM12 Y
N
MTCB107 Extramsg_overflow
outOfMemory
< GEM12 Y
N
MTCB109 Task_trap
trap
< GEM12 Y
N
MTCB110 User_type_initialization
systemINFO
< GEM12 Y
N
MTCB111 MTCBase_initialization
systemINFO
< GEM12 Y
N
411-8111-803
Standard
01.06
May 2006
Logs index 4-35
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
dmsStateChange
< GEM12 N
Y
dmsStateChange
< GEM12 N
Y
MTD103
dmsStateChange
< GEM12 N
Y
NODE300 Mismatch_Fault
mismatchFault
< GEM12 Y
N
NODE301 Hardware_Fault
hardwareFault
< GEM12 Y
N
NODE302 Software_Alarm
softwareError
< GEM12 Y
N
NODE323 REx_Fault
rexFault
< GEM12 Y
N
NODE326 Hardware_Fault
hardwareFault
< GEM12 Y
N
NODE450 REx_Test_Summary
rexSummary
< GEM12 Y
N
NODE500 Node_State_Change
nodeStateChange
< GEM12 N
Y
NODE600 System_Recovery_Action
INMRecovery
< GEM12 Y
N
NOP100
invalidArgument
< GEM12 Y
N
NOP101
operationSeqError
< GEM12 Y
N
NOP102
resourceUnavailable
< GEM12 Y
N
NOP103
systemProblem
< GEM12 Y
N
MTD101
MTD102
Fault_Cleared
NOP112
PTAE_(CMAP)
CMAPSessionINFO
< GEM12 Y
N
NOP113
PTAE_(CMAP)
CMAPSessionINFO
< GEM12 N
N
NOPT101 NC_STATE_CHANGE
nodeConnINFO
< GEM12 Y
N
NPAC100
GAS_SESSION_
SUCCESSFUL_START
GAS-SessionINFO
< GEM12 Y
N
NPAC101
GAS_SESSION_NORMAL_
TERMINATION.
GAS-SessionINFO
< GEM12 N
N
NPAC104
File_Transfer_Event
fileXfrINFO
< GEM12 Y
N
NPAC105
GAS_SESSION_
INITIIALIZATION_FAILED
GAS-SessionINFO
< GEM12 Y
N
GSM18/UMTS04
4-36 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
NPAC106
GAS_SESSION_ABNORMAL_
TERMINATION
GAS-SessionINFO
< GEM12 Y
N
NPAC107
GAS_File_Transfer_Event
GAS-xfrINFO
< GEM12 Y
N
NPAC108
GAS_File_Transfer_ERROR
GAS-xfrINFO
< GEM12 Y
N
NPAC110
L3_SUCCESSFUL_START
L3-operationINFO
< GEM12 Y
N
NPAC111
L3_NORMAL_TERMINATION
L3-operationINFO
< GEM12 Y
N
NPAC115
L3_INIT_FAILURE
L3-operationINFO
< GEM12 Y
N
NPAC116
L3_ABORT
L3-operationINFO
< GEM12 Y
N
NPAC125
6X91_LINKUP
6X91-LinkINFO
< GEM12 Y
N
NPAC126
6X91_LINKDOWN
6X91-LinkINFO
< GEM12 Y
N
NPAC128
6X91_-_SYSTEM_ERROR
6X91-SystemError
< GEM12 Y
N
NPAC200
MLG_INFO_LOG
MLG-OperationINFO
< GEM12 Y
N
NPAC201
MLG_LINKDN
MLG-OperationINFO
< GEM12 Y
N
NPAC202
MLG_MAJOR_ALARM
MLG-OperationINFO
< GEM12 Y
N
NPAC204
MULTILINK_RESET
multilinkReset
< GEM12 Y
N
incomingMsgOverLoad
< GEM12 Y
N
incomingMsgOverLoad
< GEM12 Y
N
incomingMsgOverLoad
< GEM12 Y
N
NPAC210
NPAC211
Cleared
NPAC212
NPAC550
NC_Status_Change
nodeConnINFO
< GEM12 N
N
NPAC551
RASL_Error_Report
RASL-ErrorINFO
< GEM12 N
N
NPAC999
NPAC_ERROR
NPAC-ErrorINFO
< GEM12 Y
N
PM100
DIAG
DIAG-TestFailure
< GEM12 Y
N
PM101
CHKSUM-TST
checksumTestFailure
< GEM12 Y
N
PM102
dmsStateChange
< GEM12 N
Y
PM103
dmsStateChange
< GEM12 N
Y
411-8111-803
Standard
01.06
May 2006
Logs index 4-37
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
PM104
dmsStateChange
< GEM12 N
Y
PM105
dmsStateChange
< GEM12 N
Y
PM106
dmsStateChange
< GEM12 N
Y
PM107
dmsStateChange
< GEM12 N
Y
PM108
PP-HARDWARE
dmsStateChange
< GEM12 N
Y
PM109
CARRIER
dmsStateChange
< GEM12 N
Y
PM110
CARRIER
setBERlimit
< GEM12 Y
Y
PM111
CARRIER
dmsStateChange
< GEM12 N
Y
PM113
PP-CONGESTION
congestion
< GEM12 Y
N
operationError
< GEM12 Y
N
PM114
PM115
PP-MISC-TBL
operationError
< GEM12 Y
N
PM116
PP-REPORT-DUMP
errorReportINFO
< GEM12 Y
N
operationError
< GEM12 Y
N
PM117
PM118
PP-MISC-TBL
operationError
< GEM12 Y
N
PM119
PP-INTEG-FLD
integrityFailure
< GEM12 Y
N
PM120
PP_ERROR_COUNTERS
errorCounterINFO
< GEM12 Y
N
PM122
PP-EXCPTN-RPT
exceptionINFO
< GEM12 Y
N
PM124
PP-MISC-TBL
operationError
< GEM12 Y
N
PM125
PP-HARDWARE
hardwareError
< GEM12 Y
N
PM126
PP-MISC-TBL
operationError
< GEM12 Y
N
PM127
CARRIER
linkOutOfService
< GEM12 Y
N
PM128
ISTB
dmsStateChange
< GEM12 N
Y
PM131
REX
dmsStateChange
< GEM12 N
Y
PM139
PPMBUFFS_LEVEL_CRITICAL
bufferLevelCrit
< GEM12 Y
N
GSM18/UMTS04
4-38 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
PM179
PM_HW_EXCEPTION_REPORT hwExceptionINFO
< GEM12 Y
N
PM180
PM_SW_EXCEPTION_REPORT swExceptionINFO
< GEM12 Y
N
PM185
PM_TRAP
trap
< GEM12 Y
N
PM186
CARRIER
dmsStateChange
< GEM12 Y
Y
PM187
CARRIER
dmsStateChange
< GEM12 N
Y
PM188
CARRIER
PM-SystemINFO
< GEM12 Y
N
PM189
PM_SW_Information_Report
PM-SystemINFO
< GEM12 Y
N
PM231
operationError
< GEM12 Y
N
PM232
operationError
< GEM12 Y
N
PM233
operationError
< GEM12 Y
N
PM234
operationError
< GEM12 Y
N
PM236
integrityFailure
< GEM12 Y
N
PM600
REX_Failed
rexTestFailure
< GEM12 Y
N
PM777
SUSPECTED_H/W_FAULT
hardwareDefect
< GEM12 Y
N
PRSM300 General_Trouble
systemTrouble
GEM12
Y
N
PRSM301 PRSM_File_Failure
fileOperationFailure
GEM12
Y
N
PRSM302 PRSM_File_Control_Problem
fileOperationFailure
GEM12
Y
N
PRSM360 File_Audit_Failure
fileAuditFailure
GEM12
Y
N
PRSM380 Automated_Process_Failure
automatedProcessFailure
GEM12
Y
N
PRSM381 Switch_Sanity_Failure
sanityFailure
GEM12
Y
N
RO101
SESSION_LOGON
remoteSessionINFO
< GEM12 Y
N
RO102
SESSION_LOGOFF
remoteSessionINFO
< GEM12 N
N
RO103
TRANS_ERROR
translateFailure
< GEM12 Y
N
RO104
ABNORMAL_TERMINATION
abnormalTermination
< GEM12 Y
N
411-8111-803
Standard
01.06
May 2006
Logs index 4-39
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
RO105
INVALID_STATE
invalidState
< GEM12 Y
N
SCU329
Alarm_Raised/Cleared
lossOfCommunication
GEM15
N
N
SCU356
Alarm_Raised/Cleared
simplexAlarm
GEM15
N
N
SCU500
State_change
SCU_OperationINFO
GEM15
Y
N
SDM550
Node_Status_Change
applStatusChange
< GEM12 N
Y
SDM650
SDM_Link_Report
linkMtcINFO
< GEM12 Y
N
SDMB300 SDM_BILLING_SYSTEM
billingSystemStatus
GEM12
Y
N
SDMB600 SDM_BILLING_SYSTEM
billingSystemStatus
GEM12
Y
N
SDMB310 SDM_BILLING_COMMS
communicationProblem
GEM12
Y
N
communicationProblem
GEM12
Y
N
SDMB315 SDM_BILLING_SOFT_ERROR
billingSoftwareError
GEM12
Y
N
billingSoftwareError
GEM12
N
N
SDMB316 SDM_BILLING_PROC_DEATH
billingProcDeath
GEM12
Y
N
SDMB320 SDM_BILLING_BACKUP
bkupThresholdCrossed
GEM12
N
N
GEM12
N
N
backupFileFault
GEM12
Y
N
backupFileINFO
GEM12
N
N
SDMB330 SDM_BILLING_CONFIG
sbaConfigProblem
GEM12
Y
N
sbaConfigProblem
GEM12
N
N
SDMB350 SDM_BILLING_CONTROL
sbaControlProblem
GEM12
Y
N
sbaControlProblem
GEM12
N
N
SDMB355 SDM_BILLING_DISK
thresholdCrossed
GEM12
N
N
communicationsFailure
GEM12
Y
N
communicationsFailure
GEM12
N
N
GSM18/UMTS04
4-40 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
streamCreationFailure
GEM12
Y
N
SDMB367 SDM_BILLING_MIB
MIBTrap
GEM12
Y
N
SDMB375 SDM_BILLING_FILE_
TRANSFER
fileTransfer
GEM12
N
N
TRANSFER
fileTransfer
GEM12
Y
N
transferMode
GEM12
Y
N
transferMode
GEM12
Y
N
TRANSFER_SCHEDULE
fileTransfer
GEM12
N
N
SDMB400 SDM_BILLING_SUMMARY
sbaSummary
GEM12
Y
N
streamStateChange
GEM12
N
Y
bkupVolNameChange
GEM12
Y
N
billingProcStatus
GEM12
Y
N
SDMB625 SDM_BILLING_RECOVERY
recoveringFile
GEM12
Y
N
SDMB667 SDM_BILLING_MIB
MIBvalueChangeINFO
GEM12
Y
N
SDMB820 BILLING_BACKUP
GEM12
N
N
SLM200
Command_Failure
SLM-CommandFailure
< GEM12 Y
N
SLM202
Command_Failure
SLM-CommandFailure
< GEM12 Y
N
SLM204
Command_Failure
SLM-CommandFailure
< GEM12 Y
N
SLM206
Device_Not_Responding
SLM-CommandFailure
< GEM12 Y
N
SLM400
RMS_REQUEST_OVERFLOW
RMS-RequestOverflow
< GEM12 Y
N
SLM401
SLM_STATUS_CHANGE
slmStateChange
< GEM12 N
Y
SLM402
SLM_STATUS_CHANGE
slmStateChange
< GEM12 N
Y
SLM403
SLM_STATUS_CHANGE
slmStateChange
< GEM12 N
Y
SLM404
SLM_STATUS_CHANGE
slmStateChange
< GEM12 N
Y
411-8111-803
Standard
01.06
May 2006
Logs index 4-41
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
SLM405
SLM_STATUS_CHANGE
slmStateChange
< GEM12 N
Y
SLM406
SLM_STATUS_CHANGE
slmStateChange
< GEM12 N
Y
SLM407
SLM_TEST_RESULT
testResultINFO
< GEM12 Y
N
SLM408
SLM_MAINTENANCE_
INFORMATION
maintenanceINFO
< GEM12 Y
N
SLM409
SLM_STATUS_CHANGE
slmStateChange
< GEM12 N
Y
SLM410
SLM_DAILY_AUDIT
auditINFO
< GEM12 Y
N
SOC300
Audit
softwareError
< GEM12 Y
N
SOC301
Audit
softwareError
< GEM12 Y
N
SOC302
Audit_Failure
softwareError
< GEM12 Y
N
SOC303
Audit_failure
softwareError
< GEM12 Y
N
SOC304
Audit
softwareError
< GEM12 Y
N
SOC305
Audit
softwareError
< GEM12 Y
N
SOC306
Audit_failure
softwareError
< GEM12 Y
N
SOC307
Audit
softwareError
< GEM12 Y
N
SOC308
Feature_trouble
softwareError
< GEM12 Y
N
SOC310
Audit
softwareError
< GEM12 Y
N
SOC311
Software_upgrade_transition
swUpgradeTransition
< GEM12 Y
N
SOC312
Audit
softwareError
< GEM12 Y
N
SOC313
Audit
softwareError
< GEM12 Y
N
SOC314
Audit
softwareError
< GEM12 Y
N
SOC315
Audit
softwareError
< GEM12 Y
N
SOC316
Audit
softwareError
< GEM12 Y
N
SOC317
Audit
softwareError
< GEM12 Y
N
SOC318
Audit
softwareError
< GEM12 Y
N
GSM18/UMTS04
4-42 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
SOC319
Audit
softwareError
< GEM12 Y
N
SOC320
Audit
softwareError
< GEM12 Y
N
SOC321
Audit
softwareError
< GEM12 Y
N
SOC322
Audit
softwareError
< GEM12 Y
N
SOC323
Audit
softwareError
< GEM12 Y
N
SOC324
Audit
softwareError
< GEM12 Y
N
SOC325
Audit
softwareError
< GEM12 Y
N
SOC326
Audit
softwareError
< GEM12 Y
N
SOC402
Usage_Exceeds_Threshold
usageThresholdCrossed
< GEM12 Y
N
SOC403
Current_Usage_Exceeds_Limit
< GEM12 Y
N
SOC404
SOC_Usage_Has_Overflowed
overflowError
< GEM12 Y
N
SOC502
State_transition
stateTransitionError
< GEM12 Y
N
SOC505
Key_Code_Rejected
keyCodeRejected
< GEM12 Y
N
SOC506
Spontaneous_state_transition
stateTransitionINFO
< GEM12 Y
N
SOC508
Threshold_Change_Failed
thresholdChangeFailure
< GEM12 Y
N
SOC509
Feature_Set_Option’s_State
optionStateChange
< GEM12 Y
N
SOC510
ONP_State_Change_Failed
ONPStateChangeFailure
< GEM12 Y
N
SOC600
ONP_feature_data_mismatch
dataMismatchFault
< GEM12 Y
N
SOC601
ONP_option_data_mmismatch
dataMismatchFault
< GEM12 Y
N
SOC604
SOC_reset_by_feature
SOCResetINFO
< GEM12 Y
N
SOC605
Current_Usage_Mismatch
usageMismatchFault
< GEM12 Y
N
SOC606
Illegal_Threshold
illegalThreshold
< GEM12 Y
N
SOC607
High_Water_Mark_Reset
resetHighWaterINFO
< GEM12 Y
N
SOC800
Usage_Has_Exceede_Threshold usageThresholdCrossed
< GEM12 Y
N
411-8111-803
Standard
01.06
May 2006
Logs index 4-43
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
SOC801
Usage_Has_Exceeded_Limit
< GEM12 Y
N
SOC802
Usage_Has_Overflowed
usageCounterOverflowed
< GEM12 Y
N
SOC803
Usage_Request_Refused
usageRequestRefused
< GEM12 Y
N
SOS100
Dump_Error
dumpOperationINFO
< GEM12 Y
Y
SOS101
Dump_complete
dumpOperationINFO
< GEM12 Y
Y
SOS102
PRIORITY_OPERATION
priorityOperationINFO
< GEM12 N
Y
setprivOperationINFO
< GEM12 Y
N
SOS103
SOS104
DISCARDED_SWERRS
discardedSwerrsINFO
< GEM12 Y
N
SOS105
DISCARDED_LOGS
discardedLogsINFO
< GEM12 Y
N
SOS107
EMER_MODE
emer_modeINFO
< GEM12 N
Y
remoteLoginINFO
< GEM12 Y
N
SOS109
SOS110
Dump_error
dumpOperationINFO
< GEM12 Y
Y
SOS111
Outgoing_msg_limit
reachOutgoingMsgLimitINFO
< GEM12 Y
N
SOS120
SRAM_operation
SRAMOperationINFO
< GEM12 Y
N
SOS130
FCB_pool_nearly_empty
FCBPoolCapacityINFO
< GEM12 Y
N
SOS131
FCB_pool_OK.
FCBPoolCapacityINFO
< GEM12 N
N
SOS132
General_SOS_Message
sosMsgINFO
< GEM12 Y
N
SOS602
Too_many_pools_allocated
poolsAllocationINFO
< GEM12 Y
N
SOS603
Time_of_Day_CLOCK_Change_ todClockChangeINFO
notification
< GEM12 Y
N
SOS604
DSTTABLE_is_empty
emptyDSTTableINFO
< GEM12 Y
Y
SOS605
Expired_DSTTABLE_requests
expiredDSTTableINFO
< GEM12 Y
Y
SOS701
Critical_Alarm
timeOfDayAlarm
GEM15
Y
N
SOS702
Major_Alarm
timeOfDayAlarm
GEM15
Y
N
SOS703
no_Alarm
timeOfDayAlarm
GEM15
Y
N
GSM18/UMTS04
4-44 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
SPM300
Device_Fault_Report
deviceFault
GEM13
Y
N
SPM310
ECHO_CANCELLER_REPORT
EchoCancellerINFO
GEM13
Y
N
SPM311
SW_Exception_Report
swException
GEM13
Y
N
SPM312
Trap
trap
GEM13
Y
N
SPM313
Fault
moduleInterfaceMemoryFault
GEM13
Y
N
SPM314
IMC
IMCstatus
GEM15
Y
N
SPM330
SPM_Datasync_Report
dataSyncTBL
GEM13
Y
N
SPM331
Failed_Device_Protection_Switch protectionSwitchFailure
GEM13
N
Y
SPM334
SPM_Clock_Perform_Out_Of_
Spec
outOfSpec
GEM13
N
Y
SPM335
Device_Spare
protectionSwitchFailure
GEM13
N
Y
SPM336
Clock_Range
voltageCntrlThresholdCrossed
GEM13
N
Y
SPM337
SPM_Has_Entered_Holdover
holdOver
GEM13
N
Y
SPM338
SPM_Has_Been_In_Holdover_
Over_24_Hours
holdOver24Hours
GEM13
N
Y
SPM339
Clock_Range
voltageCntrlThresholdCrossed
GEM13
N
Y
SPM340
CM_WarmSwact_SPM_Report
swactMsgFailure
GEM13
Y
N
SPM350
Resource_Alarm_State_
Changed
resourceExhaustion
GEM13
N
N
SPM500
Device_State_Change
deviceStateChange
GEM13
N
Y
SPM501
Sync_Operation_Mode_Change
clockModeChange
GEM13
Y
Y
SPM510
Sync_Reference_Switch
clockReferenceINFO
GEM13
Y
N
SPM600
MS_Mode_Changed
chgModeNotificationFailure
GEM13
Y
N
SPM630
Device_Protection_Switch
protectionSwitchINFO
GEM13
Y
Y
SPM637
SPM_Has_Exited_Holdover
holdOver
GEM13
N
Y
411-8111-803
Standard
01.06
May 2006
Logs index 4-45
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
SPM638
SPM_Has_Exited_24_Hour_
Holdover
holdOver24Hours
GEM13
N
Y
SPM650
deviceLoaderINFO
GEM13
Y
N
SPM651
deviceLoaderFailure
GEM13
Y
N
SPM660
EchoCancellerINFO
GEM13
Y
N
SPM661
EchoCancellerINFO
GEM13
Y
N
SPM700
SPM_Trunk_Subgroup_DDM_
Audit
ddmFailure
GEM13
Y
N
SPM701
Audit
ddmFailure
GEM13
N
N
SPM702
Audit
ddmFailure
GEM13
Y
N
SPM703
SPM_Trunk_Member_DDM_
Audit
ddmFailure
GEM13
Y
N
SPM704
SPM_Trunk_Member_DDM_
Audit
ddmFailure
GEM13
N
N
SPM705
SPM_PTS_Trunk_Maintenance
ddmFailure
GEM13
Y
N
SPM706
SPM_PTS_Trunk_Maintenance
ddmFailure
GEM13
N
N
SPM707
SPM_ISDNPARAMETER_DDM_ ddmFailure
Dynamic
GEM13
Y
N
SPM708
SPM_ISDNPARAMETER_DDM_ ddmFailure
Audit
GEM13
N
N
SPM709
SPM_ISDNPROT_DDM_
Dynamic_Update
ddmFailure
GEM13
Y
N
SPM710
SPM_ISDNPROT_DDM_Audit
ddmFailure
GEM13
N
N
initializationINFO
< GEM12 Y
N
SRC400
SRC500
SRC_Progress_Report
SRCProgressINFO
< GEM12 Y
N
SRC520
SRC_Status_Report
SRCStatusINFO
< GEM12 Y
N
SRC620
SRC_Trace_Log
SRCTrace
< GEM12 Y
N
GSM18/UMTS04
4-46 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
SRC660
Bad_return_code
badReturnCode
< GEM12 Y
N
SRC661
Unexpected_event
unexpectedEventINFO
< GEM12 Y
N
SSR600
Switch_Status_Report
switchStatus
< GEM12 Y
N
SYNC202 System_CNFG:_SYNC_Info
syncEventINFO
< GEM12 Y
Y
SYNC203 System_CNFG:_SYNC_Event_
Failure
syncEventINFO
< GEM12 Y
Y
SYNC205 Reference_CNFG:_SYNC_Info
syncEventINFO
< GEM12 Y
Y
SYNC206 Reference_CNFG:_SYNC_
Event_Failure
syncEventINFO
< GEM12 Y
Y
SYNC208 Reference_CNFG:_Sync_Info
syncEventINFO
< GEM12 Y
Y
SYNC209 Reference_CNFG:_Sync_Event_ syncEventINFO
Failure
< GEM12 Y
Y
TRK101
GROUP_ALARM
thresholdCrossed
< GEM12 N
Y
TRK102
GROUP_ALARM
thresholdCrossed
< GEM12 N
Y
TRK103
GROUP_ALARM
thresholdCrossed
< GEM12 N
Y
TRK104
GROUP_OK
thresholdCrossed
< GEM12 N
Y
TRK106
diagnosticTestINFO
< GEM12 Y
N
TRK107
diagnosticTestINFO
< GEM12 N
N
TRK108
diagnosticTestINFO
< GEM12 Y
N
TRK109
diagnosticTestINFO
< GEM12 Y
N
TRK110
LOCKOUT_ON
dmsStateChange
< GEM12 N
Y
TRK111
ROUTING_TRBL
routingFailure
< GEM12 Y
N
TRK112
LOCKOUT_OFF
dmsStateChange
< GEM12 N
Y
TRK113
TRUNK_TRBL
trk-trkCallFailure
< GEM12 Y
N
TRK114
DP_RECEP_TRBL
dialPulseTRBL
< GEM12 Y
N
TRK115
DP_PERM_SIG
dialPulseTRBL
< GEM12 Y
N
411-8111-803
Standard
01.06
May 2006
Logs index 4-47
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
TRK116
MF_RECEP_TRBL
multifrequencyTRBL
< GEM12 Y
N
TRK117
MF_PERM_SIG
multifrequencyTRBL
< GEM12 Y
N
TRK118
ANI_RECEP_TRBL
ANIreceptionTRBL
< GEM12 Y
N
TRK120
ONI_TROUBLE
ONIreceptionTRBL
< GEM12 Y
N
TRK121
OUTPULSING_TRBL
outpulsingTRBL
< GEM12 Y
N
TRK122
INTEGRITY_TRBL
integrityTRBL
< GEM12 Y
N
TRK123
PP_CC_COMMNCTN
pp-ccMsgingTRBL
< GEM12 Y
N
TRK124
TL102_ABORTED
trkTestAborted
< GEM12 Y
N
TRK125
TL102_PASSED
trkTestINFO
< GEM12 N
N
TRK126
TL102_FAILED
trkTestINFO
< GEM12 Y
N
TRK128
TL100_FAILED
trkTestINFO
< GEM12 Y
N
TRK129
TL100_FAILED
trkTestINFO
< GEM12 Y
N
TRK130
TL100_PASSED
trkTestINFO
< GEM12 N
N
TRK131
TL100_FAILED
trkTestINFO
< GEM12 Y
N
TRK132
TL103_PASSED
trkTestINFO
< GEM12 N
N
TRK133
TL103_FAILED
trkTestINFO
< GEM12 Y
N
TRK134
TL104_PASSED
trkTestINFO
< GEM12 N
N
TRK135
TL104_FAILED
trkTestINFO
< GEM12 Y
N
TRK136
TL104_FAILED
trkTestINFO
< GEM12 Y
N
TRK138
TRMT
treatmentINFO
< GEM12 Y
N
TRK139
TLNSS_PASSED
trkTestINFO
< GEM12 N
N
TRK140
TLNSS_FAILED
trkTestINFO
< GEM12 Y
N
TRK141
TLSYN_PASSED
trkTestINFO
< GEM12 N
N
TRK142
TLSYN_FAILED
trkTestINFO
< GEM12 Y
N
GSM18/UMTS04
4-48 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
TRK157
TL_LPA_ABORTED
trkTestINFO
< GEM12 Y
N
TRK158
TL_LPA_FAILED
trkTestINFO
< GEM12 Y
N
TRK162
OUTPULSING_TRBL
outpulsingTRBL
< GEM12 Y
N
TRK174
TL105_FAILED
trkTestINFO
< GEM12 Y
N
TRK175
TL105_FAILED
trkTestINFO
< GEM12 Y
N
TRK176
TL105_FAILED
trkTestINFO
< GEM12 Y
N
TRK177
TL105_FAILED
trkTestINFO
< GEM12 Y
N
TRK178
TL105_FAILED
trkTestINFO
< GEM12 Y
N
TRK182
DGT_RECEP_TRBL
digitoneTRBL
< GEM12 Y
N
TRK183
DGT_PERM_SIG
digitoneTRBL
< GEM12 Y
N
TRK213
TRUNK_TRBL
trunkTRBL
< GEM12 Y
N
TRK313
MFC_TRUNK_TRBL
trunkTRBL
< GEM12 Y
N
TRK355
IDLE_Q_CORRUPT
idleQCorrupt
< GEM12 Y
N
TRK424
CP_ERRORS_EXCEEDED
CPErrThresholdCrossed
< GEM12 Y
N
TRK882
INFO
thresholdCrossed
< GEM12 N
Y
X25110
L3_info
layer3INFO
< GEM12 Y
N
X25111
L3_error_detected
layer3Error
< GEM12 Y
N
XAC300
LowSM_(Low_Shared Memory)
lowXACSharedMemory
GEM12
N
Y
XAC302
LowPE_(Low_Processor_
Element)
lowPE
GEM12
N
Y
XAC303
MScomm_(Message_SwitchCommunication)
msCommFault
GEM12
N
Y
XAC304
TOD_(Time_Of_Day_Clock)
todFault
GEM12
N
Y
XAC305
RTIF_(Reset_Terminal_Interface) RTIFfault
GEM12
N
Y
XAC306
Disk
GEM12
N
Y
diskFault
411-8111-803
Standard
01.06
May 2006
Logs index 4-49
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
XAC307
Tape
tapeFault
GEM12
N
Y
XAC308
Image_Test_Report
imageTestResult
GEM12
Y
N
XAC309
AMDI_(ATM_Multinode_Data_
Inter...)
amdiFault
GEM15
N
Y
XAC310
MANB_ManB_(Card_Manual_
Busy)
cardManualBusy
GEM15
N
N
XAC312
IOP_(Input_Output_Processor_
Failed)
lowIOPFault
GEM12
N
Y
XAC320
XA-Core_Cardlist_Report
circuitPackFault
GEM12
Y
N
XAC321
WgSlot_(Shelf_Audit_Failure)
wrongSlot
GEM12
Y
N
XAC322
PETrbl_(Trouble)
processorElementTrbl
GEM12
N
Y
XAC323
SMTrbl_(Trouble)
sharedMemoryTrbl
GEM12
N
Y
XAC324
IOTrbl_(Trouble)
ioTrbl
GEM12
N
Y
XAC325
RIBKEY_Detected
RIBkey
GEM12
N
Y
XAC326
MS_Link_Configura...
msLinkMismatch
GEM12
Y
N
XAC327
WgSlot_(Card_Inserted_Into_
Wrong_Slot)
wrongSlot
GEM12
N
Y
XAC329
ETHR_(Ethernet)
dmsStateChange
GEM15
Y
Y
XAC330
FW_version_mismatch
FWmismatch
GEM15
N
N
XAC400
XA-Core_Summary_Report
xacDailySummary
GEM12
Y
N
XAC413
RExSch_(REx_Schedule_
Failure)
rexScheduleFailure
GEM12
N
N
XAC415
Routine_Exercise_(REx)_Report rexResultINFO
GEM12
Y
N
XAC418
Split_(Entry_to_Split_Mode_
Failed)
splitModeINFO
GEM12
Y
N
XAC600
LowSM_Condition_Cleared
lowXACSharedMemory
GEM12
N
Y
XAC601
MemLim_Condition_Cleared
memLimConditionINFO
GEM12
N
N
GSM18/UMTS04
4-50 Logs index
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
XAC602
LowPE_Condition_Cleared
lowPEFault
GEM12
N
Y
XAC603
MScomm_Alarm_Cleared
msCommFault
GEM12
N
Y
XAC604
TOD_Alarm_Cleared
todFault
GEM12
N
Y
XAC605
RTIF_Alarm_Cleared
RTIFfault
GEM12
N
Y
XAC606
Disk_Alarm_Cleared
diskFault
GEM12
N
Y
XAC607
Tape_Alarm_Cleared
tapeFault
GEM12
N
Y
XAC608
Image_(Test_Passed/Alarm_
Cleared)
imageTestResult
GEM12
Y
N
XAC609
AMDI_link_condition_cleared
amdiFault
GEM15
N
Y
XAC610
Returned_To_Service
cardInService
GEM12
N
Y
XAC612
IOP_Fault_Cleared
lowIOPFault
GEM12
N
Y
XAC613
RExSch_Alarm_Cleared
rexScheduleFailure
GEM12
N
N
XAC614
XATrap_Alarm_Cleared
trapINFO
GEM12
N
N
XAC615
REx_Started
rexResultINFO
GEM12
N
N
XAC618
Split_(Split_Mode_Entered)
splitModeINFO
GEM12
Y
N
XAC619
Split_Mode_Exited
splitModeINFO
GEM12
N
N
XAC622
PETrbl_Alarm_Cleared
processorElementTrbl
GEM12
N
Y
XAC623
SMTrbl_Alarm_Cleared
sharedMemoryTrbl
GEM12
N
Y
XAC624
IOTrbl_Alarm_Cleared
ioTrbl
GEM12
N
Y
XAC625
RIBKEY_Removed
RIBkey
GEM12
N
Y
XAC626
MS_Link_Configuration_
Mismatch
msLinkMismatch
GEM12
N
Y
XAC627
WgSlot_Cleared_-_Removed
wrongSlot
GEM12
N
Y
XAC628
XA-Core_Provisioning_Report
config
GEM15
Y
N
XAC629
Ethernet_link_condition_cleared
dmsStateChange
GEM15
Y
Y
411-8111-803
Standard
01.06
May 2006
Logs index 4-51
Table 4-1
Log
Name
Log Header
OMC-S Description
Clear
Override
(Y / N) (Y / N)
XAC630
No_FW_version_mismatch
FWversionINFO
GEM12
N
N
XAC631
FW_soaking_started
fwSoak
GEM15
Y
N
XAC632
FW_soaking_completed
fwSoak
GEM15
Y
N
XAC635
FW_soaking_in_progress
fwSoak
GEM15
Y
N
XAC640
Test_Report
manulTestINFO
GEM12
Y
N
XAC801
MemLim_(Memory_Limit)
memLimConditionINFO
GEM12
Y
N
XAC814
XATrap_(XA-Core_High_Trap_
Rate)
trapINFO
GEM12
Y
N
XACP300
Memory_Blocking_High
MemoryBlockingINFO
GEM15
Y
N
XACP500
Memory_Blocking_Normal
MemoryBlockingINFO
GEM15
Y
N
XACP600
Memory_Blocking_Summary
MemoryBlockingINFO
GEM15
Y
N
GSM18/UMTS04
4-52 Logs index
411-8111-803
Standard
01.06
May 2006
5-1
CEM browser icons
5
The purpose of this section is to:
• describe the rules which drive the colors of the icons presented in the
Core Element Manager
•
describe the colors and DMS state associated with the switch node
•
show the relationship between the icons presented in the Core Element
Manager and the MSC/HLR resources
General rules
5
Table 5-1 lists the association of the color and the DMS state of the switch
node to some of the general events that can occur with regards to the OMC-S
applications on the SDM/FT and the CEM browser.
Table 5-1|
General Rules
Scenario
Color
DmsState (as seen in
the Info Window)
A valid but incorrect IP address
is entered while adding a node.
The color of the node will be red, and it
will not have any sub nodes under it.
Disconnected
OMC-S browser loses
connection to the LAN.
a) If the switch is already discovered, the
color of the switch node and all the
resources under it changes to cyan.
Disconnected
b) If the switch is added after the
browser loses the LAN connectivity, the
color of the node will be red and it will
not have any sub nodes under it.
Disconnected
—sheet 1 of 3—
GSM18/UMTS04
5-2 CEM browser icons
Table 5-1|
General Rules (continued)
Scenario
Color
the Info Window)
SDM/FT is down.
Disconnected
b) If the switch is added after the SDM/
FT has gone down, the color of the node
will be red and it will not have any sub
nodes under it.
SDM/FT is offlined or busyed
from the switch.
b) If the switch is added after the SDM/
FT is offlined or busyed, the color of the
node will be red and it will not have any
sub nodes under it.
All the DS512 links between the
SDM/FT and the Switch are
down.
a) If the switch is already discovered the
color of the switch node changes to red
and the color of all the resources under it
changes to cyan.
b) If the switch is added after the DS512
links have gone down, the color of the
node will be red and it will not have any
sub nodes under it.
—sheet 2 of 3—
411-8111-803
Standard
01.06
May 2006
Disconnected
Disconnected
Disconnected
Unknown
Disconnected
CEM browser icons 5-3
Table 5-1|
General Rules (continued)
Scenario
Color
the Info Window)
Any of the OMC-S applications
except Agent,
TelnetFTPHandler and is
busyied from the SDM/FT.
Agent restarts
On reconnectivity to the agent all the
nodes are cleared and an IP node is
created with lightGray color indicating
cleared status. The switch will not be
discovered until the OMC-S application
is returned to service.
Disconnected
Cleared
b) If the switch is added after the OMC-S
application is busyied from the SDM/FT
the color of the node will be red and it
will not have any sub nodes under it.
Disconnected
If the Agent is busyed from the
SDM/FT.
a) If the switch is already discovered the
Disconnected
b) If the switch is added after the Agent
is busyed, the color of the node will be
red and it will not have any sub nodes
under it.
—sheet 3 of 3—
Terminal resources
5
Terminal resources represent MSC/HLR physical or logical resources (For
example, CM CPU card, or CCS7 route) that have no sub-resources.
Figure 5-1
Terminal resources icon
The color of terminal resource icons is determined by their alarm status.
These resources can have one, or more than one, attributes which have a
GSM18/UMTS04
bearing upon their alarm status (For example, FP CPU has two attributes
fpCPUDmsState and fpActState which can affect its alarm status). The alarm
status of these resources can also be affected by other higher severity alarms
raised by the switch against them (For example, CM can be in service with a
critical alarm due to a low memory alarm). At any particular instance of time
the value of the alarm status for a terminal resource is set to the worst of the
alarm severity of the attributes which affect its alarm status and the severity of
the alarms raised against that resource. A list of attributes for the resources,
which affect their alarm status and the mapping to corresponding alarm
severity is provided in following sections.
The text displayed on each icon indicates its node state. Please note that many
resources have more than one attribute, the legend always corresponds to the
attribute with a DmsState suffix on its name.
Performance management resources
5
Performance Management resources represent groupings of operational
measurements collected from the MSC or HLR.
Figure 5-2
Performance management resources icon
One or more of these icons may appear under a square container or barrel
container, representing data for that container. When more than one icon
appears under a container, each icon represents data for a unique physical or
logical component of the container.
The icons are always gray because they represent neither physical nor logical
resources. The objects indicate threshold crossings by raising a red flag above
the top left corner of the icon when an operational measurement represented
by the icon exceeds a threshold. The specific operational measurement that
exceeded the threshold is contained in the associated threshold alarm in the
Fault Management window.
Square containers
5
Square Containers represents MSC/HLR physical or logical resources (For
example, CM, or linkset) that have sub-resources.
Figure 5-3
Square container icon
411-8111-803
Standard
01.06
May 2006
There are two rules that are used to determine the color of the square container
icons:
• If the object has a DmsState attribute (For example, a LIM node), the
color of its icon is determined by its alarm status, similar to the terminal
resources.
•
If the object does not have a DmsState attribute (For example, the switch
node), the color of its icon is determined by its alarm status or by the
alarm status propagated up from its sub-resources, whichever is worse.
The alarm status propagation rules are as follows:
• The alarm status of a resource is one severity level less than the worst
severity level of its sub-resources (For example, if one or more subresources have critical alarm status, the alarm status of the resource will
be major). White indicates a pending state. This occurs when a container
has more than one resource with some being grey and the others being
light yellow (warning).
•
If all the sub-resources are at the same severity level, the alarm status of
the resource is same as that of its sub-resources (For example, if all the
sub-resources have critical alarm status the alarm status of the resource
will be critical).
In addition to their own color these containers also have a small triangle on
their bottom right corner (descendant alarm status) that indicates the alarm
status of the most degraded of all its sub-resources (of the entire sub-tree).
The state indicated on the square container follows the same rules that apply
to terminal resources.
Barrel containers
5
Barrel Containers are used to group switch resources in a way that will reduce
the number of icons displayed at any level of the OMC-S Element Manager
(For example, Trunkgroup_Container).
Figure 5-4
Barrel containers icon
The color of these icons is given by the alarm status propagation rules. No
state will be displayed on these icons. The descendant alarm status indicator
follows the same rules that apply to square containers.
GSM18/UMTS04
Link icons
5
Note: The colors for the icons in are default colors and are replaced by
actual colors based on the alarm status of the resources.
Table 5-2
Link Icons
Icon
Description
Link View Button, used to show/hide links
Link Bundle, used to indicate links (any of the supported link
types) between two NEs
Linkset links, used to represent linkset links between two
resources, also used as button in Link Editor Window to
show/hide linkset links
Routeset links, used to represent routeset links between two
resources, also used as button in Link Editor Window to
show/hide routeset links
Trunkgroup links, used to represent trunkgroup links between
two resources, also used as button in Link Editor Window to
show/hide trunkgroup links
IP/ Packet links, used to represent IP/Packet links between
two resources, also used as button in Link Editor Window to
show/hide IP/Packet links
Link End point, used to represent link end points in link view
411-8111-803
Standard
01.06
May 2006
Network element icons
5
Network Element (NE) icons are displayed on the lower left corner of the NE
icon. These icons represent the type of NE such as DMS based (Circuit) or
Passport based (Packet).
Table 5-3
NE Type Icons
Icon
Description
MSC
Tri-Node MSC
HLR
ATM Frame Relay End Office
ATM Frame Relay Generic
ATM Frame Relay Hub
ATM Frame Relay Line Terminating Equipment
ATM Frame Relay Mediation Device
ATM Frame Relay Multiplexer
ATM Frame Relay STP
—sheet 1 of 5—
GSM18/UMTS04
Table 5-3
NE Type Icons
Icon
Description
ATM Frame Relay Toll Gateway
ATM Frame Relay Toll Tandem
Circuit Switching End Office
Circuit Switching Generic
Circuit Switching Hub
Circuit Switching Line Terminating Equipment
Circuit Switching Mediation Device
Circuit Switching Multiplexer
Circuit Switching STP
Circuit Switching Toll Gateway
Circuit Switching Toll Tandem
—sheet 2 of 5—
411-8111-803
Standard
01.06
May 2006
Table 5-3
NE Type Icons
Icon
Description
IP Access
IP Bridge
IP Generic
IP Hub
IP Lan Regenerator
IP Line Terminating Equipment
IP Mediation Device
IP Multiplexer
IP Router
IP Signalling Gateway
IP STP
—sheet 3 of 5—
GSM18/UMTS04
Table 5-3
NE Type Icons
Icon
Description
IP Switch
IP Switch Router
IP Traffic Gateway
Multi Layer Access
Multi Layer Generic
Wireless Edge Cell Regenerator
Wireless Edge End Office
Wireless Edge Gateway
Wireless Edge Generic
Wireless Edge Hub
Wireless Edge Line Terminating Equipment
—sheet 4 of 5—
411-8111-803
Standard
01.06
May 2006
Table 5-3
NE Type Icons
Icon
Description
Wireless Edge Mediation Device
Wireless Edge Multiplexer
Wireless Edge Radio Cell Site Equipment
Wireless Edge X Connect
—sheet 5 of 5—
GSM18/UMTS04
411-8111-803
Standard
01.06
May 2006
6-1
Mapped resources
6
The purpose of this section is to show the resources that are currently being
mapped by the Core Element Manager
The OMC-S Application will discover, recover the initial state, monitor state
changes, and map the following DMS MSC/HLR resources.
The resources will be discovered at initialization time. Figure 6-1 describes
the top level component tree. Individual resources within each component are
described in the tables below.
Note: Resource state changes are displayed immediately. There may,
however, be a delay before sub-resource changes are displayed. This
occurs when a node state changes, but the Element Manager is not
immediately notified. The Element Manager must wait for the 1/2 hour
cmNorm audit before changes are noted.
The detail information on the top level component tree sections can be found
in the following sections:
• Application Subsystem
•
CCS Subsystem
•
CompCore
•
EXT
•
IOD
•
MS
•
NET
•
PM
•
Software Subsystem
•
Trunk Group Container
GSM18/UMTS04
6-2 Mapped resources
Figure 6-1
Top Level
XA-Core and MMU components
6
The location of new XA-Core and MMU components in the containment tree
is shown in Figure 6-2.
Figure 6-2
Component Layout
Note 1: The newly added resources are marked in bold text.
Note 2: GSM loads need not be configured for XA-Core or MMU. The
detection will be done from GSM table datafill and should be transparent
to the OMC-S operator.
Mobility management unit
The MMU layout is shown in Figure 6-3. The table involved in discovery of
these resources are LIUINV.
411-8111-803
Standard
01.06
May 2006
Mapped resources 6-3
Figure 6-3
MMU Layout
MMU-0 is a virtual MMU and does not have the same commands as the other
MMU resources. The MMU Pool related states and their values are listed
below in the Table 6-1.
Table 6-1
mobilityManagementPool
Class.Attribute
Attribute Value
Alarm Severity
mobilityManagementPool.actualLoadDmsState
critical
critical
major
major
cleared
cleared
unknown
indeterminate
critical
critical
major
major
cleared
cleared
unknown
indeterminate
mobilityManagementPool.hypotheticalLoadStatu
s
The MMU related states and their values are listed below in Table 6-2.
Table 6-2
mobilityManagementUnit
Class.Attribute
Attribute Value
Alarm Severity
mobilityManagementUni
t.actualLoadStatus
critical
critical
major
major
cleared
cleared
GSM18/UMTS04
Table 6-2
mobilityManagementUnit
Class.Attribute
mobilityManagementUni
t.mmuDmsState
411-8111-803
Standard
01.06
Attribute Value
Alarm Severity
unknown
indeterminate
ins
cleared
istb
minor
sysb
critical
manb
major
deld
warning
offl
warning
uneq
cleared
unknown
indeterminate
May 2006
XA Core
The XA Core layout is shown in Figure 6-4. The tables involved in the
discovery of these resources are XACINV and XASHELF.
Figure 6-4
XA Core Layout
Figure 6-5 shows the MultiCore layout.
Figure 6-5
MultiCore Layout
Note: Figure 6-5 depicts both CM and XACORE under COMPCORE.
This is an either/or situation. CM and XACORE (XAC) cannot
simultaneously reside in the same OMC-S resource tree. It must be one or
the other.
GSM18/UMTS04
The XA Core related states and their values are listed below in following
tables.
Table 6-3
Extended Architecture Core
Class.Attribute
Attribute Value
Alarm Severity
extendedArchitectureCo
re.xaAlarm
rextst
Minor
imgtst
Minor
upgrde
Minor
emlim
Minor
lowpe
Critical
Major
Minor
lowsm
Major
Minor
mscomm
Critical
Major
Minor
image
Critical
tod
Critical
Major
Minor
xatrap
Major
diskfl
Minor
rtiffl
Critical
Major
Minor
rexsch
Minor
imgsz
Minor
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-3
Extended Architecture Core (continued)
Class.Attribute
Attribute Value
Alarm Severity
tapefl
Minor
petrbl
Minor
lowiop
Minor
iotrbl
Minor
smtrbl
Minor
ribkey
Major
Minor
wgslot
Minor
power
Major
crdrts
cleared
noalarm
cleared
unknown
indeterminate
—sheet 2 of 2—
Table 6-4
xacSharedMemory
Class.Attribute
Attribute Value
Alarm Severity
xacSharedMemory.nod
eDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
splt
minor
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
GSM18/UMTS04
Table 6-5
processorElement
Class.Attribute
Attribute Value
Alarm Severity
processorElement.xaCa
rdDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
Class.Attribute
Attribute Value
Alarm Severity
inputOutputProcessor.x
aCardDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
Table 6-6
inputOutputProcessor
411-8111-803
Standard
01.06
May 2006
Table 6-7
coreMSInterConnect
Class.Attribute
Attribute Value
Alarm Severity
coreMSInterConnect.xa
CardDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
Class.Attribute
Attribute Value
Alarm Severity
remoteTerminalInterface
.xaCardDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
Table 6-8
remoteTerminalInterface
GSM18/UMTS04
Table 6-9
xacTape
Class.Attribute
Attribute Value
Alarm Severity
xacTape.xaCardDmsSta
teState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
Class.Attribute
Attribute Value
Alarm Severity
xacDisk.xaCardDmsSta
te
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
Table 6-10
xacDisk
411-8111-803
Standard
01.06
May 2006
Application subsystem
6
The APPL subsystem is for the Application (APPL). In the OMC-S Element
Manager it is represented as a container with resources: SDM, SBA, and
DRM.
Figure 6-6
Application Level
SDM
The SDM resources are discovered from table SDMINV.
Table 6-11
SDM
Class.Attribute
Attribute Value
Alarm Severity
supernodeDataManager.nodeDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
DRM
The DRM resource is for the Distributed Recording Manager (DRM). DRM
is a resource with two attributes: resourceIndicator and processState. DRM
GSM18/UMTS04
has resources that are application stream names (GCDR, GHOT, and IAA).
The DRM resources are discovered from table DRMAPPL.
Table 6-12
DRM
Class.Attribute
Attribute Value
Alarm Severity
distributedRecordingManagerTrans.resourceI
ndicator
cleared
cleared
activeReportableWarning
warning
activeReportableCritical
critical
activeReportableMajor
major
activeReportableMinor
minor
activeReportableIndeterminate
indeterminate
on
cleared
off
critical
unknown
indeterminate
cleared
cleared
warning
critical
major
minor
indeterminate
distributedRecordingManagerTrans.processSt
ate
distributedRecordingManager.resourceIndicat
or
411-8111-803
Standard
01.06
May 2006
Application stream resources
Application Streams are resources of type DRM. In the OMC-S Element
Manager they are represented as resources with two attributes: resourceSpace
and processStatus. The resources can be found in table DRMAPPL.
The second attribute of a recording stream, Process Status, has the value of
‘cleared’ when both the DRMTRANS process and the AMAPROC process
are up when intended to be running. The Process Status is set to
activeReportable-Major if either process is down. The DRMTRANS process
handles all recording streams whose ‘enabled’ field is set to Y in table
DRMTRANS. An AMAPROC process runs for each recording stream that
the alarm field is set to Y in the table CRSFMT. DRM301 is a software alarm
log with MAJOR alarm level. It is generated when either the DRMTRANS
process dies or the AMAPROC process dies for a recording stream which has
its alarm value set to Y in table CRSFMT. The alarm for Process Status is
manually cleared due to the lack of a clear log.
GSM18/UMTS04
CCS subsystem
6
The CCS subsystem is for the Common Channel Signaling (CCS). In the
OMC-S Element Manager it is represented as a container with two resources:
LKSET, and RTESET.
Figure 6-7
Common Channel Signaling
Link set
The LKSET resource is for the Link Set (LKSET). In the OMC-S Element
Manager it is represented as a resource with one attribute: linkSetDmsState.
The LKSET resources are discovered from table C7LKSET.
Table 6-13
LKSET Subsystem
Class.Attribute
Attribute Value
Alarm Severity
linkSet.linkSetDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
rinb
minor
linb
minor
unknown
indeterminate
Variable expansions
rinb - ls_remote_inhibit, OOS - SOME LINKS REMOTE INHIBIT
linb - ls_local_inhibit, OOS - SOME LINKS LOCAL INHIBIT
411-8111-803
Standard
01.06
May 2006
Link
The LINK resource is subset of the LKSET. In the OMC-S Element Manager
it is represented as a resource with one attribute: linkDmsState. The LINK
resources are discovered from table C7LINK.
Table 6-14
LINK
Class.Attribute
Attribute Value
Alarm Severity
link.linkDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
idl
cleared
rinb
minor
linb
minor
clb
minor
unknown
indeterminate
Variable expansions
clb - lt_ctrld_lk_blking, LINK MGMT BLOCKED
Route set
The RTESET resource is for the Route Set (RTESET). In the OMC-S
Element Manager it is represented as a resource with one attribute:
routeSetDmsState. The RTESET resources are discovered from table
C7RTESET.
Table 6-15
RTESET Subsystem
Class.Atribute
Attribute Value
Alarm Severity
routeSet.routeSetDmsState
ins
cleared
istb
minor
—sheet 1 of 2—
GSM18/UMTS04
Table 6-15
RTESET Subsystem (continued)
Class.Atribute
Attribute Value
Alarm Severity
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
—sheet 2 of 2—
Route
The ROUTE resource is a subset of the RTESET. In the OMC-S Element
Manager it is represented as a resource with one attribute: routeDmsState.
The ROUTE resources are discovered from table C7RTESET.
Table 6-16
ROUTE
Class.Attribute
Attribute Value
Alarm Severity
route.routeDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
transferAllowed
cleared
transferRestricted
minor
transferProhibited
critical
route.routeTrafficState
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-16
ROUTE (continued)
Class.Attribute
Attribute Value
Alarm Severity
noStat
warning
congested
minor
testFailed
warning
unknown
indeterminate
—sheet 2 of 2—
GSM18/UMTS04
CompCore
6
In the OMC-S Element Manager the compCore subsystem is represented as a
container with resources for the SuperNode. The resources are: EXTBLK,
MOD, MSCCP, CM, SOS, SWERR, HLR, Base_OM, TRAP, and VLR. The
value of the thresholdAlarmIndication is received from its children.
Note: There are OM groups represented under the logical containers for
compCore. However, not all OM groups are discussed in this chapter. For
further information regarding OM groups, refer to the OM chapter of this
NTP.
Figure 6-8
compCore (SuperNode)
EXTBLK
The EXTBLK resource is a sub-component of the compCore. The EXTBLK
represents the extension blocks in the DMS. In the OMC-S Element Manager
each resource underneath it has one attribute: thresholdAlarmIndication. The
thresholdAlarmIndication is set to True when the threshold is crossed;
otherwise it will be false.
411-8111-803
Standard
01.06
May 2006
MOD
The MOD resource represents the modules under DMS and checks for
module errors.
Table 6-17
MOD
Class.Attribute
Attribute Value
Alarm Severity
module.procedureDescriptor
cleared
cleared
critical
indeterminate
cleared
cleared
critical
indeterminate
cleared
cleared
major
indeterminate
module.moduleTableOwner
module.checksumDiscrepancy
MSCCP
The MSCCP subsystem is for the Mobile Switching Center Call Processing.
In the OMC-S Element Manager it is represented as a container with six subcontainers: GCBK, GPRP, MSCCPSRV, MSCBILL2, MLPP, and MSCLIDB.
These are multi-tuple OM groups in the GSM switch. The value of the
thresholdAlarmIndication attribute is received from its children. The MSCCP
subsystem also contains multiple Accumulated Current Data objects and
Extended Current Data objects which represent the single tuple OM
groups.The Extended Current Data is needed for thresholding and the
Accumulated Current Data is needed for scanner reports.The
thresholdAlarmIndication is set to True when the threshold is crossed;
otherwise it will be false.
GSM18/UMTS04
MSCCPSRV
MSC Call Processing Circuit-Switched Services is a logical container that
monitors data services on the MSC. It pegs circuit-switched call attempts and
successful calls.
GCBK
GSM Code Blocking is a logical container that measures the number of calls
blocked and passed by controls of type CBk.
GPRP
GSM Pre-Route Peg is a logical container that measures the number of calls
pegged by pre-route peg control.
MSCBILL2
This is a logical container that reports on terminated calls, as well as statistics
related to call duration and system operation.
MSCLIDB
This is a logical container that contains the MSC Line Information Database.
MPLL
This is a logical container that provides information on MLPP service
domains and users.
SOS
The SOS subsystem is for the Support Operating System. In the OMC-S
Element Manager it is represented as a container with three resources:
Console, DST, and Image Dump.
CONS
The Console resource represents the MMI information. In the OMC-S
priorityUser.
Table 6-18
CONS
Class.Attribute
Attribute Value
Alarm Severity
console.alarmStatus
cleared
cleared
warning
critical
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-18
CONS (continued)
Class.Attribute
console.priorityUserDmsState
Attribute Value
Alarm Severity
major
minor
indeterminate
on
minor
off
cleared
unknown
indeterminate
—sheet 2 of 2—
Image dump
The Image Dump resource will retrieve the state of the latest image dump. In
the OMC-S Element Manager it is represented as a resource with one
attribute: alarmStatus.
Table 6-19
Image Dump
Class.Attribute
Attribute Value
Alarm Severity
imageDump.alarmStatus
cleared
cleared
warning
critical
major
minor
indeterminate
GSM18/UMTS04
Daylight saving time
The initial State of the DST resource is not discovered. In the OMC-S
alarmStatus.
Table 6-20
DST
Class.Attribute
Attribute Value
Alarm Severity
daylightSavingTime.alarmStatus
cleared
cleared
warning
critical
major
minor
indeterminate
SWERR
Initial state for SWERRs (software error) are currently not discovered. See
Restriction/limitation section. The SWERR resource is a bin where SWERRS
are saved.
BRSTA
The BRSTA subsystem is a base OM group that represents the BRISC
Occupancy Status.
HLR
The hlrFunction represents a subset of HLR GSM12.04 compliant
performance measurements. The HLR subsystem is for the Home Location
Register.
AUCSTATS
A logical container representing the Authentication Center Statistic Resource.
GHLTMMGT
A logical container representing the GSM HLR Mobility Management
Resource.
411-8111-803
Standard
01.06
May 2006
HBOOSTER
A logical container containing the HLR Requests sent to the Booster
Resource.
HEXTSUB
A logical container containing the HLR Extension Service Supplementary
Service Provisioning Statistics.
HLRCAP
A logical container representing the HLR Capacity Resource.
HMWDSC
A logical container representing the HLR Message Waiting Data for Service
Centers Resource.
HSMSERR
A logical container representing the GSM HLR Short Message Service Errors
Resource.
HSMSOPS
A logical container representing the HLR Short Message Service Operations
Resource.
HSUBPRTN
A logical container representing HLR Subscriber Partition Provisioning
Statistics Resource.
SRINODE
A logical container representing Send Routing Information Per Node
Resource.
HSSERROR
A logical container representing HLR Supplementary Service Errors
Resource.
BASE_OM
The BASE_OM subsystem is a sub-component of the compCore. The
BASE_OM represents the base OM groups that do not already exist in
MSCCP, C7SP, CCS, or EXTBLK subsystem. In the OMC-S Element
Manager it is represented as a container with 4 sub-containers; each subcontainer represents a multi-tuple OM group. These containers are ANN,
C7ROUTER, CF3P, and TONES. They, in addition to the BASE_OM
container, contain one attribute, thresholdAlarmIndication, which is set on the
status of the thresholdAlarmIndication from their children. The BASE_OM
container also contains multiple Accumulated Current Data objects and
Extended Current Data objects which represent single tuple groups.The
Extended Current Data is needed for thresholding and the Accumulated
GSM18/UMTS04
Current Data is needed for scanner reports. BASE_OM subsystem is created
as part of the Performance Management enhancement.
ANN
A logical container representing the Announcements Resource.
C7ROUTER
A logical container representing the CCS7 Route Resource.
CF3P
A logical container representing the Three-port Conference Circuit Resource.
TONES
A logical container representing the Tones Resource.
TRAP
Initial state for traps are currently not discovered. See Restriction/limitation
section. The Trap resource is a bin where traps are saved.
VLR
The VLR resource is for the Visitor Location Register. This resource is a
Performance Management resource.
LAC
The LAC Subsystem is for the Location Area Code (LAC). In the OMC-S
thresholdAlarmIndication. The thresholdAlarmIndication is set to True when
the threshold is crossed; otherwise it will be false. The LAC resources are
discovered from table LAC.
CM
The CM resource only exists within the Super Node switch with a Brisc
processor platform. The CM subsystem is for the Computing Module (CM).
In the OMC-S Element Manager it is represented as a container with four
attributes: pmcStatus, mcStatus, drmStatus, and mtceStatus. It is a container
with six resources: CM_MNT, PMC-0, MEM-0/1, MC-0/1, CPU-0/1, and
SLM-0/1 (non SR70).
Table 6-21
CM
Class.Attribute
Attribute Value
Alarm Severity
computingModule.topAlmDmsState
imagecrit
critical
notodsflt
minor
—sheet 1 of 4—
411-8111-803
Standard
01.06
May 2006
Table 6-21
CM (continued)
Class.Attribute
Attribute Value
Alarm Severity
lowmemflt
minor
stralcflt
critical
cmtrapflt
major
cmemerflt
critical
mmnosync
warning
memcorflt
major
cmflt
major
cpuclkflt
major
procoptflt
minor
strammaj
major
rextst
minor
mcsbsy
critical
mcmbsy
major
mccbsy
warning
pmcflt
major
lowsprmaj
major
nosync
major
slmlimmaj
major
mmsync
cleared
rexflt
minor
memlim
minor
slmlimmin
minor
mctblflt
minor
autoldflt
warning
—sheet 2 of 4—
GSM18/UMTS04
Table 6-21
CM (continued)
Class.Attribute
computingModule.jamStatus
computingModule.cmSyncStatus
Attribute Value
Alarm Severity
imageminor
minor
pmctblflt
minor
memflt
major
srammin
minor
jinactflt
warning
lowsprflt
minor
memcfg
minor
rexschflt
minor
noburst
minor
e2alinkflt
minor
nosyncmin
warning
noovrflt
warning
ecconflt
warning
ins
cleared
unknown
indeterminate
jammed
warning
not_jammed
cleared
unknown
indeterminate
instep
cleared
eccon
warning
insync
cleared
no_override
warning
—sheet 3 of 4—
411-8111-803
Standard
01.06
May 2006
Table 6-21
CM (continued)
Class.Attribute
Attribute Value
Alarm Severity
nosync
major
split
warning
unknown
indeterminate
—sheet 4 of 4—
Variable expansions
sscf - rpc_ms_sscf, SSC providing timing to MC is down
todf - rpc_mc_todf, MC has one or more TODs faulty
tbl - rpc_mc_trouble, MC has trouble
cMemFlt - rpc_cm_mmi_cpu_mem_fault
e2aFlt - rpc_cm_mmi_e2a_fault
uTst - rpc_cm_mmi_under_test
iCrit - mnt_image_crti
spMj - mnt_lowspr_maj
iMin - mnt_image_min
lowspr - mnt_image_min
lowspr - mnt_lowspr
rexsch - mnt_rexsch
memcfg - mnt_memcfg
memlim - mnt_memlim
sMin -mnt_slmlim_min
sMaj - mnt_slmlim_maj
sCrit - mnt_stralc_crit
econ - rpc_sync_eccon, error correction - This occurs when the use of SYNC
with error corrections is permitted.
CM_MNT
The CM_MNT resource is a sub-component of the CM. In the OMC-S
mtceStatus.
Table 6-22
CM_MNT
Class.Attribute
Attribute Value
Alarm Severity
cmMaintenance.mtceDmsState
ins
cleared
iCrit
critical
lowmem
minor
—sheet 1 of 2—
GSM18/UMTS04
Table 6-22
CM_MNT (continued)
Class.Attribute
Attribute Value
Alarm Severity
trap
critical
sprMj
major
autold
warning
iMin
minor
lowspr
warning
rexsch
cleared
memcfg
cleared
memlim
warning
sMin
minor
sMaj
major
sCrit
critical
rexflt
minor
unknown
indeterminate
—sheet 2 of 2—
PMC-0
The P-side Message Controller (PMC) resource is a sub-component of the
CM. In the OMC-S Element Manager it is represented as a resource with one
attribute: mcStatus. The PMC container has two resources: Link-0/1. The
Link-0/1 have one attribute: pmcLinkStatus.
Table 6-23
PMC-0
Class.Attribute
Attribute Value
Alarm Severity
pMessageController.mcDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
sscf
minor
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-23
PMC-0 (continued)
Class.Attribute
Attribute Value
Alarm Severity
todf
minor
tbl
minor
unknown
indeterminate
—sheet 2 of 2—
Table 6-24
Link-0/1
Class.Attribute
Attribute Value
Alarm Severity
cmPmcLink.pmcLinkDmsState
ins
cleared
uneq
cleared
offl
warning
manb
major
sysb
critical
pbsy
warning
split
warning
istb
minor
unknown
indeterminate
Note: PMC links are shown as “ports” on MAPCI of DMS.
Memory-0/1
The MEM-0/1 resource is a sub-component of the CM. In the OMC-S
Element Manager it is represented as a container with one resource: Mem
Proc. Mem Proc is a sub-component with 1 resource: memoryDmsState
Table 6-25
Mem Proc
Class.Attribute
Attribute Value
Alarm Severity
cmMemoryModule.memoryDmsState
ins
cleared
istb
minor
rex
warning
—sheet 1 of 2—
GSM18/UMTS04
Table 6-25
Mem Proc (continued)
Class.Attribute
Attribute Value
Alarm Severity
fault
critical
cMemFlt
major
clkFlt
major
e2aFlt
critical
uTst
warning
noburst
minor
split
warning
resNA
minor
hwNtst
warning
uneq
cleared
unknown
indeterminate
—sheet 2 of 2—
MC-0/1
The MC-0/1 resource is for the Message Controller (MC). In the OMC-S
Element Manager it is represented as a container with two attributes:
mcStatus and sscStatus. The MC resources are discovered from table
CMSHELF. MC Resources are sub-components of the MC-0/1 resource with
two attributes: sscStatus and mcPortStatus.
Table 6-26
MC-0/1
Class.Attribute
Attribute Value
Alarm Severity
cmMessageController.sscStatus
ins
cleared
istb
minor
src_error
major
flt
critical
split
warning
uTst
warning
uneq
cleared
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-26
MC-0/1 (continued)
Class.Attribute
cmMessageController.mcDmsState
Attribute Value
Alarm Severity
unknown
indeterminate
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
sscf
minor
todf
minor
tbl
minor
unknown
indeterminate
—sheet 2 of 2—
Table 6-27
MC Resources
Class.Attribute
Attribute Value
Alarm Severity
cmMcLink.mcPortDmsState
ins
cleared
istb
minor
split
warning
oos
critical
unknown
indeterminate
GSM18/UMTS04
CPU-0/1
The CPU-0/1 resource is for the Central Processing Unit (CPU). In the OMCS Element Manager it is represented as a container with one attribute:
cpuDmsState. The CPU resources are discovered from table CMSHELF.
Table 6-28
CPU-0/1
Class.Attribute
Attribute Value
Alarm Severity
centralProcessingUnit.cpuDmsState
ins
cleared
istb
minor
rex
warning
fault
critical
cMemFlt
major
clkFlt
major
e2aFlt
critical
uTst
warning
noburst
minor
split
warning
resNA
minor
hwNtst
warning
uneq
cleared
unknown
indeterminate
SLM-0/1
The SLM-0/1 resource is for the System Load Module (SLM). In the OMC-S
Element Manager it is represented as a container with one attribute:
nodeDmsState. The SLM-0/1 resource has one sub-component: SLM
Devices. The slmDevice resource has one attribute: slmDeviceState. The
SLM resources are discovered from table SLM.
Table 6-29
SLM-0/1
Class.Attribute
Attribute Value
Alarm Severity
systemLoadModule.nodeDmsState
ins
cleared
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-29
SLM-0/1
Class.Attribute
Attribute Value
Alarm Severity
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
—sheet 2 of 2—
Table 6-30
SLM Devices
Class.Attribute
Attribute Value
Alarm Severity
slmTape.slmDeviceDmsState
ins
cleared
sysb
critical
istb
minor
manb
major
offl
warning
cbsy
warning
uneq
cleared
flt
warning
ctrFlt
minor
unSupp
cleared
unknown
indeterminate
ins
cleared
sysb
critical
istb
minor
manb
major
slmDisk.slmDeviceDmsState
—sheet 1 of 2—
GSM18/UMTS04
Table 6-30
SLM Devices (continued)
Class.Attribute
slmDevice.slmDeviceDmsState
Attribute Value
Alarm Severity
offl
warning
cbsy
warning
uneq
cleared
flt
warning
ctrFlt
minor
unSupp
cleared
unknown
indeterminate
ins
cleared
sysb
critical
istb
minor
manb
major
offl
warning
cbsy
warning
uneq
cleared
flt
warning
ctrFlt
minor
unSupp
cleared
unknown
indeterminate
—sheet 2 of 2—
Variable expansions
unSupp - rpc_slm_dev_unsupported
411-8111-803
Standard
01.06
May 2006
XAC
The XAC resource exists within the Super Node switch. It is a container with
additional sub-resources depending on system configuration.
XAC-0
The XAC-0 resource is a sub-component of XAC. In the OMC-S Element
Manager it is represented as a resource with xacSharedMemory,
inputOutProcessor, and processorElement. Each of these elements may
contain sub-resources depending on system configuration.
EXT
6
The EXT subsystem is for the External Container (EXT). In the OMC-S
Element Manager it is represented as a container with one resource, SWALM
Container.
Figure 6-9
EXT
Software alarm
The Software Alarm (SWALM) subsystem is a sub-component of EXT. In the
OMC-S Element Manager it is represented as a container with two resources:
SoftAlarm and ScanGroup. The SoftAlarm resources are discovered from
table SFWALARM.
Table 6-31
SoftAlarm
Class.Attribute
Attribute Value
Alarm Severity
softAlarm.alarmStatus
cleared
cleared
warning
—sheet 1 of 2—
GSM18/UMTS04
Table 6-31
SoftAlarm
Class.Attribute
Attribute Value
Alarm Severity
critical
major
minor
indeterminate
—sheet 2 of 2—
Scan group
The Scan Group subsystem is a sub-component of SWALM. In the OMC-S
Element Manager it is represented as a container with one resource:
scanPoint. The scanGroup resources are discovered from table ALMSC.
Scan Point
The scanPoint resource is a sub-component of the scanGroup. In the OMC-S
alarmStatus.
Table 6-32
scapPoint
Class.Attribute
Attribute Value
Alarm Severity
scanPoint.alarmStatus
cleared
cleared
warning
critical
major
minor
indeterminate
411-8111-803
Standard
01.06
May 2006
IOD
6
The IOD subsystem is for the Input/Output Device (IOD). In the OMC-S
Element Manager it is represented as a container with the resources of
iodProtocols, DIRP, and IOC.
Figure 6-10
Input Output Device
IOD
DIRP
AMA
iodProtocols
GHOT
OM
JF
GCDR
IOC’s
DDU
TTRF
DPACDEV
MAP
MTD
MPC
NX25
IOD protocols
The IOD Protocols (XFER, NX25, MLP, NOP) are resources with two
attributes:iodAlarmText and iodAlarmType.
Table 6-33
iodProtocol
Class.Attribute
Attribute Value
Alarm Severity
iodProtocol.iodAlarmType
noAlarm
cleared
minor
minor
major
major
crit
critical
unknown
indeterminate
DIRP
The Device Independent Recording Package (DIRP) subsystem directs data
automatically from the various administrative and maintenance facilities to
the appropriate recording devices. The DIRP resources are discovered from
GSM18/UMTS04
table DIRPSSYS. Alarms are manually cleared in the DIRP subsystem due to
the lack of DIRP clear logs.
Table 6-34
DIRP Subsystem
Class.Attribute
Attribute Value
Alarm Severity
dirpSubSys.alarmStatus
cleared
cleared
warning
critical
major
minor
indeterminate
Class.Attribute
Discovered State
Alarm Severity
deviceIndependentRecordingPkg.alarmStatus
cleared
cleared
warning
critical
major
minor
indeterminate
Table 6-35
DIRP
411-8111-803
Standard
01.06
May 2006
IOC
The IOC subsystem is for the Input Output Controller (IOC). The IOC
controls and provides access to devices connected to the switch. They connect
to the Message Switch (MS) directly and may provide links to serial devices
such as data units, modems, printer as well as provide x.25 link access.In the
OMC-S Element Manager it is represented as a resource with one attribute:
nodeDmsState. The IOC container has six resources: DDU, MTD, MAP,
MPC, DPACDEV, and NX25. The IOC resources are discovered from tables
IOC, MPC, MTD, DDU, NX25, TERMDEV, and DPACDEV.
Table 6-36
IOC Subsystem
Class.Attribute
Discovered State
Alarm Severity
inputOutputController.nodeDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
DDU
The Disk Drive Unit (DDU) resource is a sub-component of IOC. In the
OMC Element Manager it is represented as a resource containing two
attributes: iocPortStatus, and deviceDmsState.
Table 6-37
DDU
Class.Attribute
Attribute Value
Alarm Severity
diskDriveUnit.deviceDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
—sheet 1 of 2—
GSM18/UMTS04
Table 6-37
DDU (continued)
Class.Attribute
diskDriveUnit.iocPortStatus
Attribute Value
Alarm Severity
idl
cleared
ready
cleared
eod
warning
nRdy
warning
bab
minor
notMounted
warning
cbsy
warning
unknown
indeterminate
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
pbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
—sheet 2 of 2—
Variable expansions
eod - rpc_device_end_of_device, end of device
nRdy - rpc_device_not_ready_, device not ready
bab - rpc_device_icmo, device mounted detected of babbling
411-8111-803
Standard
01.06
May 2006
MTD
The Magnetic Tape Drive (MTD) resource is a sub-component of IOC. In the
OMC-S Element Manager it is represented as a resource containing two
attributes: iocPortStatus, tapeDmsState.
Table 6-38
MTD
Class.Attribute
Attribute Value
Alarm Severity
magneticTapeDrive.tapeDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
idl
cleared
ready
cleared
eot
warning
nRdy
warning
icmo
minor
cbsy
warning
unknown
indeterminate
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
pbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
magneticTapeDrive.iocPortStatus
GSM18/UMTS04
Variable expansions
icmo - incoming message overload, has different levels of alarms,
ISTb=Minor, SYSB=Major, Device node CMC port is shut down=Critical
MAP
The MAP resource is for console terminals. MAP is a sub-component of IOC.
In the OMC-S Element Manager it is represented as a resource contains two
attributes: iocPortStatus, termDmsState.
Table 6-39
MAP
Class.Attribute
Attribute Value
Alarm Severity
terminalDevice.termDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
disc
cleared
bab
minor
cbsy
warning
unknown
indeterminate
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
pbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
terminalDevice.iocPortStatus
411-8111-803
Standard
01.06
May 2006
MPC
The Multi-Protocol Controller (MPC) resource is a sub-component of IOC. In
the OMC-S Element Manager it is represented as a resource containing two
attributes: iocPortStatus, and deviceDmsState.
Table 6-40
MPC
Class.Attribute
Attribute Value
Alarm Severity
multiProtocolController.deviceDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
idl
cleared
ready
cleared
eod
warning
nRdy
warning
bab
minor
notMounted
warning
cbsy
warning
unknown
indeterminate
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
pbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
multiProtocolController.iocPortStatus
GSM18/UMTS04
DPACDEV
The Data Packet Device (DPACDEV) resource is a sub-component of IOC. In
the OMC-S Element Manager it is represented as a resource containing two
attributes: iocPortStatus, deviceDmsState.
Table 6-41
DPACDEV
Class.Attribute
Attribute Value
Alarm Severity
dataPacDevice.deviceDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
idl
cleared
ready
cleared
eod
warning
nRdy
warning
bab
minor
notMounted
warning
cbsy
warning
unknown
indeterminate
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
pbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
dataPacDevice.iocPortStatus
411-8111-803
Standard
01.06
May 2006
NX25
The Northern X.25 (NX25) resource is a sub-component of IOC. In the
OMC-S Element Manager it is represented as a resource containing two
attributes: iocPortStatus, deviceDmsState.
Table 6-42
NX25
Class.Attribute
Attribute Value
Alarm Severity
northernX25.deviceDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
idl
cleared
ready
cleared
eod
warning
nRdy
warning
bab
minor
notMounted
warning
cbsy
warning
unknown
indeterminate
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
pbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
northernX25.iocPortStatus
GSM18/UMTS04
MS
6
The MS Resource is for the Message Switch (MS). In the OMC-S Element
Manager it is represented as a container with 4 resources: clockAlarm,
daisyLinkDmsState, DmsState, and shelfState. The MS resources are
discovered from table MSINV.
Figure 6-11
Message Switch
MS
MS 0/1
DS512
Chains
Clock
Link 0/1
CMIC
DS-30
DS-512
Ports
Ports
Ports
Memory
PBUS
MSP
TBUSACC
TFI
Taps
Port
MS UNIT 0/1
In the OMC-S Element Manager the MS-0/1 are represented as a container
with one attribute: msDmsState. The MS is a container with 10 resources.
Table 6-43
MS-0/1
Class.Attribute
Attribute Value
Alarm Severity
messageSwitch.msDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
flt
warning
offl
warning
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-43
MS-0/1 (continued)
Class.Attribute
Attribute Value
Alarm Severity
uneq
cleared
unknown
indeterminate
—sheet 2 of 2—
DS-512 Chains
The DS-512 Chains subsystem is a sub-component of MS-0/1. In the OMC-S
Element Manager it is represented as a container with two attributes:
cpDmsState, daisyDmsState. It is represented as a container with two
resource: Link-0/1.
Table 6-44
DS-512 Chains
Class.Attribute
Attribute Value
Alarm Severity
msChainCard.cpDmsState
ins
cleared
uneq
cleared
cbsy
warning
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
ins
cleared
uneq
cleared
msChainCard.daisyDmsState
—sheet 1 of 2—
GSM18/UMTS04
Table 6-44
DS-512 Chains (continued)
Class.Attribute
Attribute Value
Alarm Severity
cbsy
warning
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
—sheet 2 of 2—
Variable expansions
dManb - cmap_daisy_manbusy
dSysb - cmap_daisy_sysbusy
redd - cmap_redundant
pbNA - cmap_pb_not_avail
Link-0/1
The link-0/1 subsystem is represented in the OMC-S Element Manager as a
resource with one attribute: daisyLinkDmsState. The Port resource is a subcomponent of LINK-0/1. It is a resource with one attribute: msPortDmsState.
Table 6-45
Link-0/1
Class.Attribute
Attribute Value
Alarm Severity
msLink.daisyLinkDmsState
ins
cleared
uneq
cleared
cbsy
warning
pbsy
warning
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-45
Link-0/1 (continued)
Class.Attribute
Attribute Value
Alarm Severity
offl
warning
sysb
critical
manb
major
flt
warning
istb
minor
mtce
warning
unknown
indeterminate
—sheet 2 of 2—
Table 6-46
Ports
Class.Attribute
Discovered State
Alarm Severity
msPort.msPortDmsState
ins
cleared
uneq
cleared
cbsy
warning
pbsy
warning
manb
major
sysb
critical
flt
warning
offl
warning
istb
minor
backup
warning
lbsy
warning
unknown
indeterminate
Variable expansions
lbsy - lmap_lbusy
GSM18/UMTS04
Clock
The Clock subsystem is a sub-component of MS. In the OMC-S Element
Manager it is represented as a resource with one attribute: clockAlarm.
Table 6-47
Clock
Class.Attribute
Discovered State
msClockCard.clockAlmDmsState
Alarm Severity
noAlarm
cleared
power
critical
heater
major
remClk
minor
sysClk
major
subSys
critical
cmu
minor
msp
minor
mate
minor
toMate
minor
mm
warning
tuner
warning
ext
major
alarm0
major
alarm1
major
beat
minor
unknown
indeterminate
CMIC
The Computing Module Interface Card (CMIC) subsystem is a subcomponent of MS. The CMIC is a card used by the message switch to act as
the interface with the computing module. The CMIC subsystem is
represented in the OMC-S Element Manager as a resource with one attribute:
411-8111-803
Standard
01.06
May 2006
cpDmsState. The Port resource is a sub-component of CMIC. It is a resource
with one attribute: msPortDmsState.
Table 6-48
CMIC
Class.Attribute
Discovered State
Alarm Severity
msCMICcard.cpDmsState
ins
cleared
uneq
cleared
cbsy
warning
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
DS-30
The DS-30 subsystem is a sub-component of MS. In the OMC-S Element
Manager it is represented as a resource with one attribute: cpDmsState. The
Port resource is a sub-component of DS-30. It is a resource with one attribute:
msPortDmsState.
Table 6-49
DS30
Class.Attribute
Attribute Value
Alarm Severity
msDS30Card.cpDmsState
ins
cleared
uneq
cleared
cbsy
warning
—sheet 1 of 2—
GSM18/UMTS04
Table 6-49
DS30 (continued)
Class.Attribute
Attribute Value
Alarm Severity
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
—sheet 2 of 2—
DS-512
The DS-512 subsystem is a sub-component of MS. In the OMC-S Element
Manager it is represented as a resource with one attribute: cpDmsState. The
Port resource is a sub-component of DS-512. It is a resource with one
attribute: msPortDmsState.
Table 6-50
DS512
Class.Attribute
Attribute Value
msDS512Card.cpDmsState
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Alarm Severity
ins
cleared
uneq
cleared
cbsy
warning
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
Table 6-50
DS512 (continued)
Class.Attribute
Attribute Value
Alarm Severity
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
—sheet 2 of 2—
PBUS
The Processor Bus (PBUS) sub-system is a sub-component of MS. It is used
by modules for processor communication. In the OMC-S Element Manager it
is represented as a resource with one attribute: cpDmsState.
Table 6-51
PBUS
Class.Attribute
Attribute Value
msPBusCard.cpDmsState
Alarm Severity
ins
cleared
uneq
cleared
cbsy
warning
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
GSM18/UMTS04
Memory
The Memory subsystem is a sub-component of MS. In the OMC-S Element
Manager it is represented as a resource with one attribute: cpDmsState.
Table 6-52
Memory
Class.Attribute
Discovered State
msMemoryCard.cpDmsState
Alarm Severity
ins
cleared
uneq
cleared
cbsy
warning
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
TBusAcc
The Transaction Bus Accumulator (TBusAcc) subsystem is a sub-component
of MS. It connects terminals to the NT1 for access to the ISDN. Messages are
transmitted from port to port over the T-bus. In the OMC-S Element Manager
it is represented as a resource with one attribute: cpDmsState.
Table 6-53
TBusAcc
Class.Attribute
Attribute Value
Alarm Severity
msTBusCard.cpDmsState
ins
cleared
uneq
cleared
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-53
TBusAcc (continued)
Class.Attribute
msTBusAccCard.cpDmsState
Attribute Value
Alarm Severity
cbsy
warning
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
ins
cleared
uneq
cleared
cbsy
warning
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
—sheet 2 of 2—
GSM18/UMTS04
MSP
The Message Switch Processor (MSP) subsystem is a sub-component of MS.
In the OMC-S Element Manager it is represented as a resource with one
attribute: cpDmsState.
Table 6-54
MSP
Class.Attribute
Attribute Value
Alarm Severity
msMSPcard.cpDmsState
ins
cleared
uneq
cleared
cbsy
warning
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
TFI
The T-Bus Frame Interface (TFI) subsystem is a sub-component of MS. In the
OMC-S Element Manager it is represented as a resource with two attributes:
cpDmsState and fbusDmsState. The Taps resource is a sub-component of
TFI. It is a resource with one attribute: fbusDmsState.
Table 6-55
TFI
Class.Attribute
Attribute Value
Alarm Severity
msTFIcard.cpDmsState
ins
cleared
uneq
cleared
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-55
TFI (continued)
Class.Attribute
msTFIcard.fbusDmsState
Attribute Value
Alarm Severity
cbsy
warning
manb
major
sysb
critical
dManb
major
dSysb
critical
flt
warning
offl
warning
istb
minor
redd
warning
mtce
warning
pbNA
minor
unknown
indeterminate
ins
cleared
cbsy
warning
manb
major
sysb
critical
flt
warning
offl
warning
istb
minor
uneq
cleared
mtce
warning
noStat
warning
unknown
indeterminate
—sheet 2 of 2—
GSM18/UMTS04
Table 6-56
Taps
Class.Attribute
Attribute Value
Alarm Severity
msTFItap.tfiDmsState
ins
cleared
cbsy
warning
manb
major
sysb
critical
flt
warning
offl
warning
istb
minor
uneq
cleared
mtce
warning
noStat
warning
unknown
indeterminate
Note: The attribute noStat indicates that the OMC-S did not discover the
state of a predefined resource because the resource did not exist on the
switch.
NET
6
The Network (NET) subsystem. In the OMC-S Element Manager it is
represented as a container with two resources: ENET-0/1 and the
enetMatrixCard. The ENET resources are discovered from table ENINV.
411-8111-803
Standard
01.06
May 2006
Figure 6-12
Network
enetPlane
Table 6-57
enetPlane
Class.Attribute
Attribute Value
Alarm Severity
enetPlane.enPlaneDmsState
ins
cleared
istb
minor
uneq
cleared
unknown
indeterminate
rexTest
warning
syslk
major
sysFlt
critical
sysBlk
critical
Variable expansions
syslk - rpc_enet_system_cslink, cbsy
GSM18/UMTS04
enetMatrixCard
The enetMatrixCard is a container which contains the enetMatrix resources.
The enetMatrix is a resource with one attribute: enetMatrixStatus
Table 6-58
enetMatrix
Class.Attribute
Attribute Value
Alarm Severity
enetMatrix.enetMatrixDmsState
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mUsed
warning
claimed
warning
unkStat
indeterminate
notAppl
warning
unknown
indeterminate
Variable expansions
cbsyins - rpc_en_cside_busy_insv, in service
cbsyoos - prc_en_cside_busy_oos, out of service
411-8111-803
Standard
01.06
May 2006
ENET-0/1
The ENET resource is for the Enhanced Network (ENET). In the OMC-S
Element Manager it is represented as a resource with attributes TBD (most
probably the nodeDmsState). ENET has sub-components of type enetShelf.
Table 6-59
ENET-0/1
Class.Attribute
Attribute Value
Alarm Severity
enhancedNetwork.nodeDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
enetShelf
The enetShelf resource has the following attributes: totalTrap, occInfo
(cpuOcc, totalOcc), loadName, systemStat, deload, and rpcTime (hour,
minute, second, dsUsed, dsTotal, dsAvail, percentdsUsed, psUsed, psTotal,
psAvail, percentpsUsed). enetShelf has nine sub-components:
enetPowerCard, enetXPoint, enetProcessor, enetClock, enetMsgLink,
enetRTIF, enetDS30, enetDS30DS512, and enetDS512. enetLinks can be a
subcomponent of enetMsgLink, enetDS30, enetDS30DS512, and enetDS512.
enetFibers may be subcomponents of enetDS30DS512 and enetDS512.
Table 6-60
enetShelf
Class.Attribute
Attribute Value
Alarm Severity
enetShelf.systemDmsState
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
—sheet 1 of 2—
GSM18/UMTS04
Table 6-60
enetShelf (continued)
Class.Attribute
Attribute Value
Alarm Severity
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
unknown
indeterminate
—sheet 2 of 2—
Table 6-61
enetPowerCard
Class.Attribute
Attribute Value
Alarm Severity
enetPowerCard.powerStatus
notAppl
warning
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
—sheet 1 of 3—
411-8111-803
Standard
01.06
May 2006
Table 6-61
enetPowerCard (continued)
Class.Attribute
enetPowerCard.cardDmsState
Attribute Value
Alarm Severity
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
unknown
indeterminate
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
—sheet 2 of 3—
GSM18/UMTS04
Table 6-61
enetPowerCard (continued)
Class.Attribute
Attribute Value
Alarm Severity
notAppl
warning
unknown
indeterminate
—sheet 3 of 3—
Table 6-62
enetXPoint
Class.Attribute
Attribute Value
Alarm Severity
enetXPoint.xptStatus
ins
cleared
sysb
major
manb
major
offl
warning
resUneq
cleared
cbsy
warning
mtce
warning
uneq
cleared
resIstb
minor
unknown
indeterminate
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
enetXPoint.cardDmsState
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-62
enetXPoint (continued)
Class.Attribute
Attribute Value
Alarm Severity
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
notAppl
warning
unknown
indeterminate
—sheet 2 of 2—
Table 6-63
enetProcessor
Class.Attribute
Attribute Value
Alarm Severity
enetProcessor.enetProcCpuStatus
ins
cleared
sysb
major
manb
major
offl
warning
resUneq
cleared
cbsy
warning
mtce
warning
uneq
cleared
resIstb
minor
unknown
indeterminate
ins
cleared
manb
major
sysb
major
enetProcessor.cardDmsState
—sheet 1 of 2—
GSM18/UMTS04
Table 6-63
enetProcessor (continued)
Class.Attribute
Attribute Value
Alarm Severity
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
notAppl
warning
unknown
indeterminate
—sheet 2 of 2—
Table 6-64
enetClock
Class.Attribute
Attribute Value
Alarm Severity
enetClock.cardDmsState
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-64
enetClock (continued)
Class.Attribute
Attribute Value
Alarm Severity
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
notAppl
warning
unknown
indeterminate
—sheet 2 of 2—
Table 6-65
enetMsgLink
Class.Attribute
Attribute Value
Alarm Severity
enetMsgLink.cardDmsState
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
—sheet 1 of 2—
GSM18/UMTS04
Table 6-65
enetMsgLink (continued)
Class.Attribute
Attribute Value
Alarm Severity
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
unknown
indeterminate
—sheet 2 of 2—
Table 6-66
enetRTIF
Class.Attribute
Attribute Value
Alarm Severity
enetRTIF.enetProcRtifStatus
ins
cleared
sysb
major
manb
major
offl
warning
resUneq
cleared
cbsy
warning
mtce
warning
uneq
cleared
resIstb
minor
unknown
indeterminate
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
enetRTIF.cardDmsState
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-66
enetRTIF (continued)
Class.Attribute
Attribute Value
Alarm Severity
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
notAppl
warning
unknown
indeterminate
—sheet 2 of 2—
Table 6-67
enetDS30
Class.Attribute
Attribute Value
Alarm Severity
enetDS30.enetDS30IntStatus
ins
cleared
sysb
major
manb
major
offl
warning
resUneq
cleared
cbsy
warning
mtce
warning
uneq
cleared
resIstb
minor
—sheet 1 of 2—
GSM18/UMTS04
Table 6-67
enetDS30 (continued)
Class.Attribute
enetDS30.cardDmsState
Attribute Value
Alarm Severity
unknown
indeterminate
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
notAppl
warning
unknown
indeterminate
—sheet 2 of 2—
Table 6-68
enetDS30DS512
Class.Attribute
Attribute Value
Alarm Severity
enetDS30DS512.enDS30DS512IntStatus
ins
cleared
sysb
major
—sheet 1 of 3—
411-8111-803
Standard
01.06
May 2006
Table 6-68
enetDS30DS512 (continued)
Class.Attribute
enetDS30DS512.cardDmsState
Attribute Value
Alarm Severity
manb
major
offl
warning
resUneq
cleared
cbsy
warning
mtce
warning
uneq
cleared
resIstb
minor
unknown
indeterminate
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
notAppl
warning
—sheet 2 of 3—
GSM18/UMTS04
Table 6-68
enetDS30DS512 (continued)
Class.Attribute
Attribute Value
Alarm Severity
unknown
indeterminate
—sheet 3 of 3—
Table 6-69
enetDS512
Class.Attribute
Attribute Value
Alarm Severity
enetDS512.cardDmsState
ins
cleared
manb
major
sysb
major
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
notAppl
warning
unknown
indeterminate
ins
cleared
sysb
major
enetDS512.enetDS512IntStatus
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-69
enetDS512 (continued)
Class.Attribute
Attribute Value
Alarm Severity
manb
major
offl
warning
resUneq
cleared
cbsy
warning
mtce
warning
uneq
cleared
resIstb
minor
unknown
indeterminate
—sheet 2 of 2—
Table 6-70
enetLink
Class.Attribute
Attribute Value
Alarm Severity
enetLink.enLinkDmsState
ins
cleared
manb
major
sysb
critical
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
—sheet 1 of 2—
GSM18/UMTS04
Table 6-70
enetLink (continued)
Class.Attribute
Attribute Value
Alarm Severity
claimed
warning
unkStat
indeterminate
notAppl
warning
unknown
indeterminate
—sheet 2 of 2—
Table 6-71
enetFiber
Class.Attribute
Attribute Value
Alarm Severity
enetFiber.enLinkDmsState
ins
cleared
manb
major
sysb
critical
cbsy
warning
cbsyins
cleared
cbsyoos
critical
pbsy
warning
uneq
cleared
offl
warning
istb
minor
fault
critical
lkIstb
minor
lkOos
critical
mtce
warning
mtceUsed
warning
claimed
warning
unkStat
indeterminate
notAppl
warning
unknown
indeterminate
411-8111-803
Standard
01.06
May 2006
PM
6
The PM subsystem is for the Peripheral Module (PM). In the OMC-S
Element Manager it is represented as a container the following resources: FP,
LIM, Series I, Series II, Series III and Series IV.
Figure 6-13
Peripheral Module
Series IV
PM
SPM
FP
Series III
LIM
EIU
Fbus 0/1
CTM DTM MTM
LIU7 SVR7 NIU 0/1
LIS1/2/3
Series I
Series II
Fbus 0/1
PDTC’s
HSCar
riers
TM8
CEM
spmModule
Fbus 0/1
DS30
Taps
Single Bus*
Taps
Triple Bus*
DS0
DS1
TTC
M20
NDSO
* Only the Single Bus or Triple Bus diagram (dependent upon configuration) will be present under the
LIM.
FP
The FP resource is for the File Processor (FP). In the OMC-S Element
Manager it is represented as a resource with four attributes: nodeDmsState,
fpPlaneAlarm, fpSyncState, and fpLevelDevice. The FP resources are
discovered from table APINV. The FP has two sub-components: fpPlane and
fpDevice.
GSM18/UMTS04
Figure 6-14
File Processor
fileProcessor
fpDevice
fpPlane
fpPortCard
fpCPU
fpPlink
fpDRAM
fpMsgCh
fpDABM
fpSCSI
Table 6-72
FP
Class.Attribute
Attribute Value
Alarm Severity
fileProcessor.fpDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
memlowflt
minor
trapflt
critical
cpuflt
major
clockflt
major
portflt
major
sprlowmaj
major
fileProcessor.fpPlaneAlarm
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-72
FP (continued)
Class.Attribute
fileProcessor.fpSyncState
Attribute Value
Alarm Severity
nosync
warning
rexfault
minor
porttbl
minor
memoryflt
major
cormemflt
major
jamflt
major
sprlowflt
minor
mmthresh
warning
noovr
warning
planeOk
cleared
planeNocomm
minor
planeUneq
cleared
planeOffl
warning
unknown
indeterminate
planeUnknown
indeterminate
inSync
cleared
syncNoHo
warning
outOfSync
major
splitMode
minor
syncOffl
warning
syncNotAppl
warning
unknown
indeterminate
—sheet 2 of 2—
GSM18/UMTS04
fpPlane
The fpPlane is a resource with two attributes: fpPlaneJamState and
fpPlaneRexFault. fpPlane has seven sub-components: fpPortCard, fpCPU,
fpPlink, fpDRAM, fpMsgCh, fpDABM, and fpSCSI.
Table 6-73
fpPlane
Class.Attribute
Attribute Value
Alarm Severity
fpPlane.fpPlaneJamDmsState
jammed
minor
nJam
cleared
notAppl
warning
unknown
indeterminate
noRex
minor
rex
cleared
notAppl
warning
unknown
indeterminate
Class.Attribute
Attribute Value
Alarm Severity
fpPortCard.fpPortDmsState
ins
cleared
istb
minor
istbSp
major
istbTp
critical
istb1Lk
major
istbLks
major
tpFlt
critical
fault
critical
tMip
minor
tSplit
minor
offl
warning
fpPlane.fpPlaneRexFault
Table 6-74
fpPortCard
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-74
fpPortCard (continued)
Class.Attribute
Attribute Value
Alarm Severity
uneq
cleared
unknown
indeterminate
—sheet 2 of 2—
Variable expansions
istbSp - rpc_dp_istb_split
istbTp - rpc_dp_istb_trap
tpFlt - rpc_dp_trap_fault
tMip - rpc_dp_trait_mip
tSplit - rpc_dp_trait_split
Table 6-75
fpCPU
Class.Attribute
Attribute Value
Alarm Severity
fpCPU.fpCPUDmsState
uTst
warning
split
warning
fault
critical
rAva
cleared
istb
minor
hwNtst
minor
uneq
cleared
rex
minor
clkFlt
minor
e2aFlt
minor
memFlt
minor
ins
cleared
noburst
minor
offl
warning
notAppl
warning
unknown
indeterminate
—sheet 1 of 2—
GSM18/UMTS04
Table 6-75
fpCPU
Class.Attribute
Attribute Value
Alarm Severity
fpCPU.fpActState
active
cleared
notActive
warning
notAppl
warning
unknown
indeterminate
—sheet 2 of 2—
Variable expansions
rAva - rpc_mmi_required_resources_unavail
Table 6-76
fpPlink
Class.Attribute
Attribute Value
Alarm Severity
fpPlink.fpPlinkDmsState
ins
cleared
intb
minor
sysb
critical
lkUnav
warning
manb
major
offl
warning
uTst
warning
uneq
cleared
mAva
cleared
mIstb
minor
mSysb
critical
rNrel
major
resSysb
critical
rReq
warning
resReq
warning
unknown
indeterminate
411-8111-803
Standard
01.06
May 2006
Variable expansions
lkUnav - rpc_ilm_link_unavailable
mAva - rpc_ilm_msgCh_closed_but_avail
mIstb - rpc_ilm_msgCh_closed_but_avail
mIstb - rpc_ilm_msgCh_closed_and_Istb
mSysb - rpc_ilm_msgCh_closed_and_SysB
rNrel - rpc_ilm_resource_is_unreliable
Table 6-77
fpDRAM
Class.Attribute
Attribute Value
Alarm Severity
fpDRAM.fpDRAMmemDmsState
uTst
warning
split
warning
fault
critical
rAva
cleared
istb
minor
hwNtst
minor
uneq
cleared
rex
minor
clkFlt
minor
e2aFlt
minor
memFlt
minor
ins
cleared
noburst
minor
offl
warning
notAppl
warning
unknown
indeterminate
GSM18/UMTS04
Table 6-78
fpMsgCh
Class.Attribute
Attribute Value
Alarm Severity
fpMsgCh.fpMsgChDmsState
ins
cleared
intb
minor
sysb
critical
lkUnav
warning
manb
major
offl
warning
uTst
warning
uneq
cleared
mAva
cleared
mIstb
minor
mSysb
critical
rNrel
major
resSysb
critical
rReq
warning
resReq
warning
unknown
indeterminate
Variable expansions
rNrel - rpc_ilm_resource_is_unreliable
Table 6-79
fpDABM
Class.Attribute
Attribute Value
Alarm Severity
fpDABM.fpDABMDmsState
uneq
cleared
offl
warning
manb
major
sysb
critical
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-79
fpDABM
Class.Attribute
Attribute Value
Alarm Severity
istb
minor
ins
cleared
unavail
warning
uTst
warning
dabmFlt
minor
absy
warning
unknown
indeterminate
—sheet 2 of 2—
Variable expansions
dabmFlt - rpc_fpd_dabm_fault, dabm faultl
Table 6-80
fpSCSI
Class.Attribute
Attribute Value
Alarm Severity
fpSCSI.fpScsiDmsState
uneq
cleared
offl
warning
manb
major
sysb
critical
istb
minor
ins
cleared
unavail
warning
uTst
warning
dabmFlt
minor
absy
warning
unknown
indeterminate
GSM18/UMTS04
fpDevice
The fpDevice is a resource with five attributes: fpScsiNum, fpDeviceNum,
fpDeviceStatus, fpDriveState, and fpUser.
Table 6-81
fpDevice
Class.Attribute
Attribute Value
Alarm Severity
fpDevice.fpDeviceStatus
uneq
cleared
offl
warning
manb
major
sysb
critical
istb
minor
ins
cleared
unavail
critical
uTst
warning
dabmFlt
minor
absy
warning
unknown
indeterminate
idl
cleared
mount
warning
tDisc
warning
tUnk
indeterminate
onLine
cleared
spinUp
warning
dDisc
warning
dUnk
indeterminate
notAppl
warning
unknown
indeterminate
fpDevice.fpDriveDmsState
Note: The value of fpDriveDmsState for fpDevice is shown as the DMS
state on the icon when the “DMS State” menu item is checked in the
Configuration Manager menu.
411-8111-803
Standard
01.06
May 2006
Variable expansions
tDisc - rpc_t_disconnected
tUnk - rpc_t_unknown
dDisc - rpc_d_disconnected
dUnk - rpc_d_unknown
LIM
The Link Interface Modules (LIM) subsystem is a sub-component of PM. In
the OMC-S Element Manager it is represented as a container with three
attributes: nodeDmsState, unit0, and unit1. The LIM container has one
resource (FBUS or LIS) dependent upon configuration. The FBUS resource is
present under the single bus configuration and the LIS resource is present
under the triple bus configuration. The LIM resources are discovered from
table LIMINV.
Table 6-82
LIM
Class.Attribute
Attribute Value
Alarm Severity
linkPeripheralProcessor.nodeDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
GSM18/UMTS04
FBUS-0/1
The FBUS-0/1 subsystem is for Frame Transfer Bus. It is present in the
containment tree for the single bus configuratoin. In the OMC-S Element
Manager it is represented as a resource with one attribute: mmiBusState. The
Tap resource is a sub-component of FBUS-0/1. It is a resource with one
attribute: fbusDmsState.
Table 6-83
FBUS-0/1
Class.Attribute
Attribute Value
Alarm Severity
linkInterfaceModuleBus.mmiBusDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
Class.Attribute
Attribute Value
Alarm Severity
linkInterfaceModuleTap.tapDmsState
ins
cleared
istb
minor
sysb
critical
busBsy
critical
manb
major
uneq
cleared
unknown
indeterminate
Table 6-84
Taps
411-8111-803
Standard
01.06
May 2006
LIS
The LIS resource is for the Link Interface Shelf. In the OMC-S Element
Manager it is represented as a resource with one attribute: mmiBusState. It is
present in the containment tree under the triple bus configuration. The Tap
resource is a sub-component of LIS.
LIU
The LIU resource is for the Link Interface Units (LIU). In the OMC-S
Element Manager it is represented as a container with one attribute:
nodeDmsState. The LIU container has resources that are of LIU type PMs
(EIU, LIU7, SVR7). The LIU resources are discovered from table LIUINV.
Table 6-85
LIU
Class.Attribute
Attribute Value
Alarm Severity
linkInterfaceUnit.nodeDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
GSM18/UMTS04
LIU type PMs
The LIU type PMs are a sub-components of LIU. In the OMC-S Element
Manager it is represented as a resource with one attribute: nodeDmsState. The
LIU resources are discovered from table LIUINV.
Table 6-86
LIU Type PMs
Class.Attribute
Attribute Value
Alarm Severity
ethernetInterfaceUnit.nodeDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
gsmProcessor.nodeDmsState
linkInterfaceUnit.nodeDmsState
networkInterfaceUnit.ltcDmsState
(LIU7, EIU, SVR7, GSMP,ELIU,HLIU,HSLR)
LTC
The Line Trunk Controller (LTC) resource is a sub-component of PM. The
LTC container has one or more of these types of resources: DTC, DTCI, and
PDTC. These sub-components are represented as resources with the eight
attributes: unit0Status, unit1Status, activeUnit, nodeDmsState, csOOS,
psOOS, unit0LoadProg, and unit1LoadProg. Each one of these resources has
associated resource sub-components such as pcmDS1, pcmD30, pcmTTC,
pcmM20, and pcmNDS0. The LTC resources are discovered from table
LTCINV.
Table 6-87
DTC/DTCI/PDTC
Class.Attribute
Attribute Value
Alarm Severity
lineTrunkController.unit0Status
ins
cleared
istb
minor
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-87
DTC/DTCI/PDTC (continued)
Class.Attribute
lineTrunkController.unit1Status
lineTrunkController.nodeDmsState
Attribute Value
Alarm Severity
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
—sheet 2 of 2—
GSM18/UMTS04
Table 6-88
pcmDS1
Class.Attribute
Attribute Value
Alarm Severity
pcmDS1.carrlinkDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
istb
minor
cbsy
warning
pbsy
warning
manbr
major
manbLL
major
pSysb
critical
sysbME
critical
sysbMNE
critical
unknown
indeterminate
Class.Attribute
Attribute Value
Alarm Severity
pcmD30.carrlinkDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
istb
minor
cbsy
warning
pbsy
warning
Table 6-89
pcmD30
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-89
pcmD30 (continued)
Class.Attribute
Attribute Value
Alarm Severity
manbr
major
manbLL
major
pSysb
critical
sysbME
critical
sysbMNE
critical
unknown
indeterminate
—sheet 2 of 2—
Table 6-90
pcmTTC
Class.Attribute
Attribute Value
Alarm Severity
pcmTTC.carrlinkDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
istb
minor
cbsy
warning
pbsy
warning
manbr
major
manbLL
major
pSysb
critical
sysbME
critical
sysbMNE
critical
unknown
indeterminate
GSM18/UMTS04
Table 6-91
pcmM20
Class.Attribute
Attribute Value
Alarm Severity
pcmM20.carrlinkDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
istb
minor
cbsy
warning
pbsy
warning
manbr
major
manbLL
major
pSysb
critical
sysbME
critical
sysbMNE
critical
unknown
indeterminate
Class.Attribute
Attribute Value
Alarm Severity
pcmNDS0.carrlinkDmsState
ins
cleared
sysb
critical
manb
major
offl
warning
uneq
cleared
istb
minor
cbsy
warning
pbsy
warning
Table 6-92
pcmNDS0
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-92
pcmNDS0 (continued)
Class.Attribute
Attribute Value
Alarm Severity
manbr
major
manbLL
major
pSysb
critical
sysbME
critical
sysbMNE
critical
unknown
indeterminate
—sheet 2 of 2—
Trunk module
The Trunk Module (TM) connects as many as 30 analog trunks to Switching
Network ports by means of a single duplicated speech/messaging link.In the
OMC-S Element Manager it is represented as a container with four resources:
Conference Trunk Module (CTM), Digital Trunk Module (DTM),
Maintenance Trunk Module (MTM), and Trunk Module 8 (TM8). These subcomponents of TM are represented with one attribute: nodeDmsState.
The TM resources are discovered from table TMINV.
Table 6-93
TM Resources
Class.Attribute
Attribute Value
Alarm Severity
trunkModule.nodeDmsState
ins
cleared
istb
minor
sysb
critical
manb
major
cbsy
warning
offl
warning
uneq
cleared
unknown
indeterminate
GSM18/UMTS04
SPM
6
The SPM related objects are included in the current OMC-S resource tree for
Fault Management. There are two types of objects. One is SPM circuit packet:
• Spectrum Peripheral Module (SPM)
•
Common Equipment Module (CEM)
•
OC-3 Interface Module (OC-3)
•
DLC Interface Module (DLC)
•
Digital Signaling Processor (DSP)
•
Voice Signaling Processor (VSP)
•
Other Resource Modules (RMs)
The other is high speed carrier associated with SPM.
The tree structure of those objects are shown in Figure 6-15.
Figure 6-15
SPM Components Layout
MSC/HLR
PM_Container
Series IV
SPM
HSCarriers
spmModule
CEM
CM is a primary object for resource discovery from the very beginning.
OMC-S supports xaCore since gem11. However, from this feature on, OMCS supports multiCore: cm and xaCore cannot reside in the same OMC-S
resource tree at the same time per switch. It has to be either CM or XACore
per switch. No new component is added for this support.
The layout of multiCore structure is shown in Figure 6-5.
411-8111-803
Standard
01.06
May 2006
Note: Figure 6-5 depicts both CM and XACORE under COMPCORE.
This is an either/or situation. CM and XACORE (XAC) cannot
simultaneously reside in the same OMC-S resource tree. It must be one or
the other
GSM18/UMTS04
Details of added components
The new SPM resources contain the following common attributes from the base
dmsEquipment class:
• equipmentId
•
replaceable
•
administrativeState
•
operationalState
•
alarmStatus
•
userLabel
•
availabilityStatus
•
oldestActiveLogTime
•
latestActiveLogTime
•
numberOfChildren
•
thresholdAlarmIndication
•
alarmSummaryTabulation
•
hasPmData
•
associated NodeList
•
userNote
SPM node
The OMC-S class spectrumPeripheralModule represents the SPM node. The
class attributes and their values are listed in Table 6-94.
Table 6-94
SPM
Class.Attribute
Attribute
Value
Alarm Severity
spectrumPeripheralModule.spmDmsSt
ate
uneq
cleared
sysb
critical
manb
major
offl
warning
istb
minor
ins
cleared
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-94
SPM (continued)
Class.Attribute
spectrumPeripheralModule.spmAlmSta
tus
spectrumPeripheralModule.spmClass
Attribute
Value
Alarm Severity
unknown
indeterminate
sysb
critical
manb
major
istb
minor
sysbna
critical
manbna
major
cotlow
minor
dtmflow
minor
ecanlow
minor
toneslow
minor
mflow
minor
cmrlow
minor
noAlarm
cleared
CP
N/A
IW
N/A
DA
N/A
—sheet 2 of 2—
These attributes provide basic information about SPM nodes. DMS table
MNNODE is used for initial discovery. SPM nodes are monitored by the audit
process and SPM logs after initial discovery.
GSM18/UMTS04
CEM
The class commonEquipmentModule is used to represent CEM in OMC-S.
The class attributes and their values are showed below.
Table 6-95
CEM
Class.Attribute
Attribute
Value
Alarm Severity
commonEquipmentModule.cemDmsSt
ate
uneq
cleared
sysb
critical
manb
major
offl
warning
istb
minor
ins
cleared
unknown
indeterminate
sysb
critical
manb
major
istb
minor
sysbna
critical
manbna
major
hldovr
major
hldovr24
major
vcxo70
minor
vcxo90
major
clkoos
major
noAlarm
cleared
unkown
indetermine
notAppl
cleared
acquire
minor
holdover
major
commonEquipmentModule.cemAlmSta
tus
commonEquipmentModule.cemSyncSt
ate
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Table 6-95
CEM (continued)
Class.Attribute
Attribute
Value
Alarm Severity
freerun
critical
sync
cleared
commonEquipmentModule.loadName
loadName
N/A
commonEquipmentModule.activeState
inact
N/A
act
N/A
—sheet 2 of 2—
These attributes provide the information about the CEM device status. DMS
table MNCKTPAK is used for initial discovery. The attributes are monitored
by the audit process and SPM logs.
SPM module
The class spmModule is a common OMC-S class for SPM modules: OC3,
DSP, VSP, DLC, STM, etc. The spmModule attributes and their values are
listed below.
Table 6-96
spmModule
Class.Attribute
Attribute
Value
Alarm Severity
spmModule.rmDmsState
uneq
cleared
sysb
critical
manb
major
offl
warning
cbsy
minor
istb
minor
ins
cleared
unknown
indeterminate
sysb
critical
manb
major
istb
minor
spmModule.rmAlmStatus
—sheet 1 of 2—
GSM18/UMTS04
Table 6-96
spmModule (continued)
Class.Attribute
Attribute
Value
Alarm Severity
protfail
critical
nospare
major
noAlarm
cleared
unknown
indeterminate
spmModule.loadName
loadName
N/A
spmModule.activeState
act
N/A
inact
N/A
working
warning
spare
warning
nospare
major
noAlarm
cleared
unknown
indeterminate
reverTive
N/A
non-revreTive
N/A
unknown
N/A
one_for_one
N/A
one_plus_one
N/A
m_for_n
N/A
unknown
indeterminate
grpName
N/A
spmModule.protRole
spmModule.protgrpAlarm
spmModule.protgrpMode
spmModule.protgrpSchema
spmModule.protgrpId
—sheet 2 of 2—
The attributes provide the information about the SPM modules’ device status.
DMS table MNCKTPAK is used for initial discovery. The attributes are
monitored by the audit process and SPM logs.
High speed carriers
Hierarchy structure of high speed carriers are shown in Figure 6-16.
411-8111-803
Standard
01.06
May 2006
Figure 6-16
HSCarriers Layout
SPM
OC3Ss
STS3Ls
hsCarrier
hsCarrier
DS1Ps
The OMC-S classes of high speed carriers, their attributes and values are
shown in Table 6-97, Table 6-98, Table 6-99, and Table 6-100. respectively.
Table 6-97
oc3Section (or STM1R)
Class.Attribute
Attribute
Value
Alarm Severity
oc3Section.hscarrDmsState
cbsy
warning
pbsy
warning
ins
cleared
manb
major
sysb
critical
uneq
cleared
—sheet 1 of 2—
GSM18/UMTS04
Table 6-97
oc3Section (or STM1R) (continued)
Class.Attribute
oc3Section.hscarrFailure
oc3Section.hscarrPM
oc3Section.circuitId
Attribute
Value
Alarm Severity
offl
warning
unknown
indeterminate
LOS
critical
LOF
critical
noAlarm
cleared
SEFS
minor
CV
minor
ES
minor
SES
minor
LBC
critical, major,
minor
OPT
critical, major,
minor
OPR
critical, major,
minor
noAlarm
cleared
integer
N/A
—sheet 2 of 2—
Table 6-98
STS3Line
Class.Attribute
Attribute
Value
Alarm Severity
sts3Line.hscarrDmsState
cbsy
warning
pbsy
warning
ins
cleared
manb
major
—sheet 1 of 2—
411-8111-803
Standard
01.06
May 2006
Class.Attribute
Attribute
Value
Alarm Severity
sysb
critical
uneq
cleared
offl
warning
unknown
indeterminate
AIS
minor
RFI
minor
SIMPLEX
critical
BERSF
minor
BERSD
minor
noAlarm
cleared
CV
minor
ES
minor
SES
minor
UAS
minor
PSC
minor
sts3Line.protgrpId
integer
N/A
sts3Line.circuitId
integer
N/A
sts3Line.hscarrFailure
sts3Line.hscarrPM
—sheet 2 of 2—
Table 6-99
hsCarrier=STS1/ STS3cP/VT15P/DS3P/STM1M/VC12P/VC4P/E1P
Class.Attribute
Attribute
Value
Alarm Severity
hsCarrier.hscarrDmsState
cbsy
warning
pbsy
warning
ins
cleared
manb
major
sysb
critical
GSM18/UMTS04
Class.Attribute
Attribute
Value
Alarm Severity
uneq
cleared
offl
warning
unknown
indeterminate
LOP
minor
AIS
minor
RFI
minor
PLM
minor
noAlarm
cleared
CV
minor
ES
minor
SES
minor
UAS
minor
CVFE
minor
ESFE
minor
SESFE
minor
UASFE
minor
integer
N/A
Class.Attribute
Attribute
Value
Alarm Severity
ds1Path.hscarrDmsState
cbsy
warning
pbsy
warning
ins
cleared
manb
major
sysb
critical
uneq
cleared
offl
warning
unknown
indeterminate
hsCarrier.hscarrFailure
hsCarrier.hscarrPM
hsCarrier.circuitId
Table 6-100
DS1Path
411-8111-803
Standard
01.06
May 2006
Class.Attribute
Attribute
Value
Alarm Severity
ds1Path.hscarrFailure
LOF
minor
AIS
minor
RAI
minor
noAlarm
cleared
CV
minor
ES
minor
SES
minor
CSS
minor
UAS
minor
AISS
minor
ON
N/A
OFF
N/A
ESF
N/A
SF
N/A
integer
N/A
ds1Path.hscarrPM
ds1Path.zeroCodeSprss
ds1Path.frmFormat
ds1Path.circuitId
The attributes provide the information about link status of high speed carriers.
DMS table MNHSCARR is used for initial discovery. The attributes are
monitored by the audit process and CARR logs.
Default action of alarms
All the alarms in this document can be datafilled as reportable or nonreportable. The logNormalizer will deliver logs only when alarms are
reportable. RPC will be used to monitor objects whenever alarms are nonreportable. The default datafills of alarms are shown in Table 6-101.
Default Datafill of Alarms
Table 6-101
Default Datafill of Alarm
Class Name
Alarm
Default Action
spectrumPeripheralModule
sysb
reportable
manb
reportable
—sheet 1 of 3—
GSM18/UMTS04
Table 6-101
Default Datafill of Alarm (continued)
commonEquipmentModule
spmModule
oc3Section
sts3Line
istb
reportable
sysbna
reportable
manbna
reportable
cotlow
reportable
dtmflow
reportable
ecanlow
reportable
toneslow
reportable
mflow
reportable
cmrlow
reportable
sysb
reportable
manb
reportable
istb
reportable
sysbna
reportable
manbna
reportable
hldovr
reportable
hldovr24
reportable
vcxo70
reportable
vcxo90
reportable
clkoos
reportable
sysb
reportable
manb
reportable
istb
reportable
protfail
reportable
nospare
reportable
LOS
reportable
LOF
reportable
SFBERX
reportable
SDBERX
reportable
—sheet 2 of 3—
411-8111-803
Standard
01.06
May 2006
Table 6-101
Default Datafill of Alarm (continued)
sts1Path
ds3Path.failure
ds1Path.failure
AIS
non-reportable
RFI
non-reportable
SIMPLEX
reportable
LOP
non-reportable
AIS
non-reportable
RFI
non-reportable
PLM
reportable
LOF
reportable
AIS
non-reportable
RAI
non-reportable
LOF
reportable
AIS
non-reportable
RAI
non-reportable
—sheet 3 of 3—
GSM18/UMTS04
Software subsystem
6
The Software subsystem in the OMC-S Element Manager it is represented as
a container with four resources: C7SP, CI, OM, MISC. The value of the
thresholdAlarmIndication is received from its children.
Figure 6-17
Software Subsystem
swSubSys
C7SP
CI
OM
MISC
Unmapped OM
ISUPCGRP
ISUPCONG
ISUPUSAG
TCAPERRS
TCAPUSAG
C7SP
The C7SP resource is for the C7 Signalling Processing (C7SP). In the OMCS Element Manager it is represented as a container with one attribute:
thresholdAlarmIndication. The thresholdAlarmIndication is set to True when
the threshold is crossed; otherwise it will be false. It is represented as a
container with 5 resources: ISUPCGRP, ISUPCONG, ISUPUSAG,
TCAPERRS, and TCAPUSAG. These resources represent OM groups under
DMS.
CI
The CI subsystem in the OMC-S Element Manager is represented as a
resource with one attribute: alarmStatus.
MISC
The MISC subsystem in the OMC-S Element Manager it is represented as a
resource with one attribute: alarmStatus.
OM
The OM resource is represented as a trunk OM container with one attribute:
alarmStatus. It is represented as a container with unmapped OM resources.
411-8111-803
Standard
01.06
May 2006
Trunk group container
6
The TRKGRP subsystem is for the Trunk Group (TRKGRP). The TRKGRP
subsystem contains 1 resource: CLLI NAME (trunkGrp). The TRKGRP
resources are discovered from table TRKGRP. The value of the
thresholdAlarmIndication is received from its children.
Figure 6-18
Trunk Groups
TRKGRP Container
trunk Grp
Trunk
Trunk group
In the OMC-S Element Manager the TrunkGrp is represented as a container
with three attributes: trkOccupState, thresholdAlarmIndication and
TrunkGroupType. Beginning in GEM10.1, miscellaneous trunk groups will
be discovered in addition to incoming, outgoing, and two-way trunk groups.
The thresholdAlarmIndication is set to True when the threshold is crossed;
otherwise it will be false. The TrunkGrp subsystem in the OMC-S Element
Manager is represented as a container with 1 resource: Trunk.
Table 6-102
TRKGRP
Class.Attribute
Attribute Value
Alarm Severity
trunkGroup.trkOccupDmsState
free
cleared
low
minor
medium
major
high
critical
unknown
indeterminate
Trunk
The TRKGRP subsystem is a sub-component of the TRKGRP. In the OMC-S
Element Manager it is represented as a resource with two attributes:
GSM18/UMTS04
trunkDmsState and thresholdAlarmIndication. The thresholdAlarmIndication
is set to True when the threshold is crossed; otherwise it will be false. The
TRUNK resources are discovered from table TRKMEM and it may take a
long time depending on the number of trunks. There are designer logs to
indicate the start and end for TRKGRP resource discovery.
Note: For GEM15 release, due to a missing table change notification in
table TRKGRP from the DMS, a newly added TRUNK can not be
relocated to the appropriate container.
Table 6-103
Trunk
Class.Attribute
Attribute Value
Alarm Severity
trunk.trunkDmsState
idl
cleared
ins
cleared
szd
cleared
sysb
critical
manb
major
cbsy
warning
istb
minor
inb
warning
uneq
cleared
nmb
major
pmb
major
rmb
minor
cfl
critical
lo
critical
del
cleared
ini
cleared
cpb
cleared
cpbdel
cleared
res
minor
unknown
indeterminate
411-8111-803
Standard
01.06
May 2006
Variable expansions
szd - tk_seized
inb - tk_offline
nmb - tk_nwm_busy
pmb - tk_pm_busy
rmb - tk_remote_busy
cfl - tk_carrier_fail
lo - tk_lockout
del - tk_deloaded
ini - tk_initialize
cpb - tk_cp_cusy_deload
res - tk_restricted_idle
Mapped resources for OM groups
6
Table 6-104
Mapping of U-SGSN OM groups
Group Name
DN (<Passport>)
AtmInterface
AtmIf
LogicalProcessor
LP
GprsDnsAgent
Def
SgsnAccountingServer
SAS
Link
OM_Container/Link_Container
MessageTransferPartLayer3
MTP3
SaalNni
SAALNNI
SignallingConnControlPart
SCCP
TcapOverloadControl
OM_Container/ TcapOverloadControl_Container
DownlinkBuffer
OM_Container/DownlinkBuffer_Container
UmtsLocationServices
OM_Container/ UmtsLocationServices_Container
MapClient
USC/MC
UmtsSrnsRelocation
OM_Container/ UmtsSrnsRelocation_Container
OM_Container/ GprsMobilityManagement_Container
GprsSupportNode
OM_Container/ GprsSupportNode_Container
GSM18/UMTS04
Table 6-104
Mapping of U-SGSN OM groups
Group Name
DN (<Passport>)
GtpC
USC/GTPC
HlrCache
OM_Container/HlrCache_Container
OverloadControl
OM_Container/ OverloadControl_Container
Ranap
OM_Container/Ranap_Container
SessionManagement
OM_Container/ SessionManagement_Container
Failures
OM_Container/Failures_Container
RelayLayer
OM_Container/RelayLayer_Container
UsgsnSubscriberControl
USC
UsgsnSubscriberDatapath
USD
MapStack
TCAP-13/MAP_$
IrauBuffer
OM_Container/IrauBuffer_Container
LargeBuffer
OM_Container/LargeBuffer_Container
MediumBuffer
OM_Container/MediumBuffer_Container
MiniBuffer
OM_Container/MiniBuffer_Container
ServiceSwitchingFunction
USC/SSF
SmallBuffer
OM_Container/SmallBuffer_Container
Ss7IpInterface
TCAP/SS7IPIF
TcapStack
TCAP
TrafficClass
OM_Container/TrafficClass_Container
XlargeBuffer
OM_Container/XlargeBuffer_Container
Table 6-105
Mapping of G-SGSN OM groups
Group Name
DN (<Passport>)
AtmInterface
AtmIf
411-8111-803
Standard
01.06
May 2006
Table 6-105
Group Name
DN (<Passport>)
BaseStationSystemApplPart
OM_Container/
BaseStationSystemApplPart_Container
CellId
OM_Container/CellId_Container
DownlinkBuffer
OM_Container/DownlinkBuffer_Container
Framer
OM_Container/Framer_Container
GprsDnsAgent
OM_Container/GprsDnsAgent_Container
GprsLocationServices
OM_Container/ GprsLocationServices_Container
OM_Container/ GprsMobilityManagement_Container
GprsPduBuffer
OM_Container/GprsPduBuffer_Container
GprsSubscriberControl
OM_Container/ GprsSubscriberControl_Container
GprsSubscriberDataPath
OM_Container/ GprsSubscriberDataPath_Container
GprsTunnelingProtocol
OM_Container/ GprsTunnelingProtocol_Container
GtpMgnt
OM_Container/GtpMgnt_Container
HlrCache
OM_Container/HlrCache_Container
IrauBuffer
OM_Container/IrauBuffer_Container
LargeBuffer
OM_Container/LargeBuffer_Container
LawfulInterceptAccessFunction
OM_Container/
LawfulInterceptAccessFunction_Container
LogicalLinkControl
OM_Container/ LogicalLinkControl_Container
LogicalProcessor
LP
MapClient
OM_Container/MapClient_Container
MapStack
OM_Container/MapStack_Container
MediumBuffer
OM_Container/MediumBuffer_Container
MiniBuffer
OM_Container/MiniBuffer_Container
NetworkServiceEntity
OM_Container/ NetworkServiceEntity_Container
GSM18/UMTS04
Table 6-105
Group Name
DN (<Passport>)
NetworkServiceVirtualConnection
OM_Container/
NetworkServiceVirtualConnection_Contai ner
NetworkServiceVirtualConnection
OM_Container/
NetworkServiceVirtualConnection_Contai ner
OverloadControl
OM_Container/ OverloadControl_Container
PointToPointBvc
OM_Container/ PointToPointBvc_Container
PrepaidShortMessageService
OM_Container/
PrepaidShortMessageService_Container
RelayLayer
OM_Container/RelayLayer_Container
ServiceControlPoint
OM_Container/ ServiceControlPoint_Container
ServiceSwitchingFunction
OM_Container/ ServiceSwitchingFunction_Container
SessionManagement
OM_Container/ SessionManagement_Container
SgsnAccountingServer
OM_Container/ SgsnAccountingServer_Container
ShortMessageService
OM_Container/ ShortMessageService_Container
SmallBuffer
OM_Container/SmallBuffer_Container
Ss7IpInterface
OM_Container/Ss7IpInterface_Container
Ss7IpInterface
OM_Container/Ss7IpInterface_Container
SubNetworkDataConvergenceProt ocol
OM_Container/
SubNetworkDataConvergenceProtocol_C ontainer
TcapStack
OM_Container/TcapStack_Container
TieredSubscription
OM_Container/ TieredSubscription_Container
TrafficClass
OM_Container/TrafficClass_Container
XlargeBuffer
OM_Container/XlargeBuffer_Container
411-8111-803
Standard
01.06
May 2006
Table 6-106
Mapping of GGSN Shasta OM groups
Group Name
DN (<Passport>)
Device_Stats
OM_Container/Device_Stats_Container
ISP_IP_Stats
OM_Container/ISP_IP_Stats_Container
Trunk_Stats
OM_Container/Trunk_Stats_Container
GGSN_Mem_Stats
OM_Container/ GGSN_Mem_Stats_Container
GGSN_Overload_Stats
OM_Container/ GGSN_Overload_Stats_Container
SM_Stats
OM_Container/SM_Stats_Container
perAPN_Stats
OM_Container/perAPN_Stats_Container
GTP_Data_Stats
OM_Container/ GTP_Data_Stats_Container
perCGF_Stats
OM_Container/perCGF_Stats_Container
GTP_ACCT_Stats
OM_Container/ GTP_ACCT_Stats_Container
IPSec_Stats
OM_Container/IPSec_Stats_Container
L2TP_IPSec_Stats
OM_Container/ L2TP_IPSec_Stats_Container
L2TP_Stats
OM_Container/L2TP_Stats_Container
RADIUS_ACCT_Stats
OM_Container/ RADIUS_ACCT_Stats_Container
Wireless_Services_Stats
OM_Container/ Wireless_Services_Stats_Container
SCP_Stats
OM_Container/SCP_Stats_Container
GRE_Stats
OM_Container/GRE_Stats_Container
perAPN_Ancillary_Stats
OM_Container/ perAPN_Ancillary_Stats_Container
perAPN_Data_Stats
OM_Container/ perAPN_Data_Stats_Container
MPLS_Stats
OM_Container/MPLS_Stats_Container
VRF_Stats
OM_Container/VRF_Stats_Container
GSM18/UMTS04
Table 6-107
Mapping of SIG OM groups
Group Name
DN (<Passport>)
STANDARD
STANDARD
Table 6-108
Mapping of AN OM groups
Group Name
DN (<Passport>)
AtmInterface
AtmIf
LogicalProcessor
LP
Table 6-109
Mapping of USP (HLR peripheral ) OM groups
Group Name
DN
ASPPathManagement
PM_Container/USP/USPOM_Container/
ASPPathManagement_Container
ASPPathTraffic
ASPPathTraffic_Container
ASPPathUtilization
ASPPathUtilization_Container
ATMDriverMessaging
PM_Container/USP/shelf-<shelfNum>/slot-<slotNum>
ATMLinkTraffic
ATMLinkTraffic_Container
BICCReceivedMessageCounts
CCS_Container/USP_LKSET_Container/<linksetName>
Carrier
PM_Container/USP/USPOM_Container/Carrier_Container
GatewayScreeningResults
GTTType
PM_Container/USP/USPOM_Container/GTTType_Container
ISUPReceivedMessageCounts
LinkFaultsandPerformance
411-8111-803
Standard
01.06
May 2006
Table 6-109
Group Name
DN
LinkManagement
LinkTraffic
LinksetUtilization
LogServer
NPDatabaseTotals
NPDatabaseTotals_Container
NPINAPTotals
NPNAPTotals_Container
NPLSSITotals
NPLSSITotals_Container
NPNETIDTotals
NPNETIDTotals_Container
NPServiceRuleTotals
NPServiceRuleTotals_Container
NPServiceTotals
NPServiceTotals_Container
NPSMITotals
NPSMITotals_Container
NPSRFTotals
NPSRFTotals_Container
NPTnTTotals
NPTnTTotals_Container
NPTransactionMgmtTotals
NPTransactionMgmtTotals_Container
RouteSetManagement
CCS_Container/USP_RTESET_Container/<routesetName>
RTCSanity
SAALLinkManagement
SAALLinkManagement_Container
SAALLinkTraffic
SAALLinkTraffic_Container
SCCPGTT
PM_Container/USP/USPOM_Container/SCCPGTT_Container
GSM18/UMTS04
Table 6-109
Group Name
DN
SCCPLocalSubsystem
SCCPLocalSubsystem_Container
SCCPLSSInstance
SCCPLSSInstance_Container
SCCPSystemTotals
SCCPSystemTotals_Container
SCTPManagementTrafficCounts
SLRDatabaseTotals
SLRDatabaseTotals_Container
SLRLSSITotals
SLRLSSITotals_Container
SLRMessageTypeTotals
SLRMessageTypeTotals_Container
SLRSMITotals
SLRSMITotals_Container
SpecialStudyTotals
SpecialStudyTotals_Container
SystemNodeState
SystemNodeState_Container
SystemTotals
SystemTotals_Container
TaskManagement
TUPReceivedMessageCounts
UDP
Table 6-110
Mapping of SLR / UNPM OM groups
Group Name
DN
ASPPathManagement
OM_Container/ASPPathManagement_Container
ASPPathTraffic
OM_Container/ASPPathTraffic_Container
411-8111-803
Standard
01.06
May 2006
Table 6-110
Group Name
DN
ASPPathUtilization
OM_Container/ASPPathUtilization_Container
ATMDriverMessaging
shelf-<shelfNum>/slot-<slotNum>
ATMLinkTraffic
OM_Container/ATMLinkTraffic_Container
CCS_Container/LINKSET_Container/<linksetName>
Carrier
OM_Container/Carrier_Container
GTTType
OM_Container/GTTType_Container
LinkManagement
LinkTraffic
LinksetUtilization
LogServer
NPDatabaseTotals
OM_Container/NPDatabaseTotals_Container
NPINAPTotals
OM_Container/NPNAPTotals_Container
NPLSSITotals
OM_Container/NPLSSITotals_Container
NPNETIDTotals
OM_Container/NPNETIDTotals_Container
NPServiceRuleTotals
OM_Container/NPServiceRuleTotals_Container
NPServiceTotals
OM_Container/NPServiceTotals_Container
NPSMITotals
OM_Container/NPSMITotals_Container
NPSRFTotals
OM_Container/NPSRFTotals_Container
NPTnTTotals
OM_Container/NPTnTTotals_Container
OM_Container/NPTransactionMgmtTotals_Container
RouteSetManagement
CCS_Container/ROUTESET_Container/<routesetName>
RTCSanity
GSM18/UMTS04
Table 6-110
Group Name
DN
SAALLinkManagement
OM_Container/SAALLinkManagement_Container
SAALLinkTraffic
OM_Container/SAALLinkTraffic_Container
SCCPGTT
OM_Container/SCCPGTT_Container
SCCPLocalSubsystem
OM_Container/SCCPLocalSubsystem_Container
SCCPLSSInstance
OM_Container/SCCPLSSInstance_Container
SCCPSystemTotals
OM_Container/SCCPSystemTotals_Container
SLRDatabaseTotals
OM_Container/SLRDatabaseTotals_Container
SLRLSSITotals
OM_Container/SLRLSSITotals_Container
OM_Container/SLRMessageTypeTotals_Container
SLRSMITotals
OM_Container/SLRSMITotals_Container
SpecialStudyTotals
OM_Container/SpecialStudyTotals_Container
SystemNodeState
OM_Container/SystemNodeState_Container
SystemTotals
OM_Container/SystemTotals_Container
TaskManagement
UDP
Table 6-111
Mapping of SGW ( MSC peripheral ) OM groups
Group Name
DN
ASMaster
PM_Container/USP/USPOM_Container/ASMaster_Container
ASPPathManagement
ASPPathManagement_Container
ASPPathTraffic
ASPPathTraffic_Container
411-8111-803
Standard
01.06
May 2006
Table 6-111
Group Name
DN
ASPPathUtilization
ASPPathUtilization_Container
ATMDriverMessaging
ATMLinkTraffic
ATMLinkTraffic_Container
Carrier
PM_Container/USP/USPOM_Container/Carrier_Container
GTTType
PM_Container/USP/USPOM_Container/GTTType_Container
LinkManagement
LinkTraffic
LinksetUtilization
LogServer
NPDatabaseTotals
NPDatabaseTotals_Container
NPINAPTotals
NPNAPTotals_Container
NPLSSITotals
NPLSSITotals_Container
NPNETIDTotals
NPNETIDTotals_Container
NPServiceRuleTotals
NPServiceRuleTotals_Container
NPServiceTotals
NPServiceTotals_Container
NPSMITotals
NPSMITotals_Container
GSM18/UMTS04
Table 6-111
Group Name
DN
NPSRFTotals
NPSRFTotals_Container
NPTnTTotals
NPTnTTotals_Container
NPTransactionMgmtTotals_Container
RouteSetManagement
CCS_Container/USP_RTESET_Container/<routesetName>
RTCSanity
SAALLinkManagement
SAALLinkManagement_Container
SAALLinkTraffic
SAALLinkTraffic_Container
SCCPGTT
PM_Container/USP/USPOM_Container/SCCPGTT_Container
SCCPLocalSubsystem
SCCPLocalSubsystem_Container
SCCPLSSInstance
SCCPLSSInstance_Container
SCCPSystemTotals
SCCPSystemTotals_Container
SLRDatabaseTotals
SLRDatabaseTotals_Container
SLRLSSITotals
SLRLSSITotals_Container
SLRMessageTypeTotals_Container
SLRSMITotals
SLRSMITotals_Container
SpecialStudyTotals
SpecialStudyTotals_Container
411-8111-803
Standard
01.06
May 2006
Table 6-111
Group Name
DN
SystemNodeState
SystemNodeState_Container
SystemTotals
SystemTotals_Container
TaskManagement
UDP
Table 6-112
Mapping of SGW (stand alone) OM groups
Group Name
DN
ASMaster
OM_Container/ASMaster_Container
ASPPathManagement
OMContainer/ASPPathManagement_Container
ASPPathTraffic
OMContainer/ASPPathTraffic_Container
ASPPathUtilization
OMContainer/ASPPathUtilization_Container
ATMDriverMessaging
ATMLinkTraffic
OMContainer/ATMLinkTraffic_Container
Carrier
OMContainer/Carrier_Container
GTTType
OMContainer/GTTType_Container
LinkManagement
LinkTraffic
LinksetUtilization
GSM18/UMTS04
Table 6-112
Group Name
DN
LogServer
NPDatabaseTotals
OMContainer/NPDatabaseTotals_Container
NPINAPTotals
OMContainer/NPINAPTotals_Container
NPLSSITotals
OMContainer/NPLSSITotals_Container
NPNETIDTotals
OMContainer/NPNETIDTotals_Container
NPServiceRuleTotals
OMContainer/NPServiceRuleTotals_Container
NPServiceTotals
OMContainer/NPServiceTotals_Container
NPSMITotals
OMContainer/NPSMITotals_Container
NPSRFTotals
OMContainer/NPSRFTotals_Container
NPTnTTotals
OMContainer/NPTnTTotals_Container
OMContainer/NPTransactionMgmtTotals_Container
RouteSetManagement
CCS_Container/ROUTESET_Container/<routesetName>
RTCSanity
SAALLinkManagement
OMContainer/SAALLinkManagement_Container
SAALLinkTraffic
OMContainer/SAALLinkTraffic_Container
SCCPGTT
OMContainer/SCCPGTT_Container
SCCPLocalSubsystem
OMContainer/SCCPLocalSubsystem_Container
SCCPLSSInstance
OMContainer/SCCPLSSInstance_Container
SCCPSystemTotals
OMContainer/SCCPSystemTotals_Container
SLRDatabaseTotals
OMContainer/SLRDatabaseTotals_Container
SLRLSSITotals
OMContainer/SLRLSSITotals_Container
OMContainer/SLRMessageTypeTotals_Container
SLRSMITotals
OMContainer/SLRSMITotals_Container
SpecialStudyTotals
OMContainer/SpecialStudyTotals_Container
411-8111-803
Standard
01.06
May 2006
Table 6-112
Group Name
DN
SystemNodeState
OMContainer/SystemNodeState_Container
SystemTotals
OMContainer/SystemTotals_Container
TaskManagement
UDP
GSM18/UMTS04
411-8111-803
Standard
01.06
May 2006
A-1
Index
A
A
D
Application(s)
OMC-S 1-12
Data Server 1-35
CEM support 1-39
restrictions and limitations 1-41
B
Billing Data OM groups 2-92
Billing OMs 2-92
Related information OM groups 2-92
C
CDRDIAG
OM group 2-93
CEM resources
Application subsystem 6-11
CCS subsystem 6-14
CompCore subsystem 6-18
EXT subsystem 6-35
IOD subsystem 6-37
MS subsystem 6-46
NET subsystem 6-58
PM subsystem 6-75
Software subsystem 6-108
SPM subsystem 6-94
Trunk group container subsystem 6-109
XA-Core and MMU 6-2
Correlated OMs 2-17
G-SGSN OM groups 2-48
hlrMeasurementFunction1 &
hlrMeasurementFunction2 2-81
MSC OM groups 2-17
MSCMeasurementFunction 2-85
U-SGSN OM groups 2-62, 2-73
vlrMeasurementFunction 2-89, 2-90
E
Element(s)
types of 1-5
Event class
definitions 3-2
Expert
class 3-2
H
HLR 200
CEM support 1-24
Data Server 1-35
Mated pair monitoring 1-27
memory application 1-26
Passport 8600 1-31
restrictions and limitations 1-41
SAM21 1-33
SLR 1-32
STORM 1-34
I
Icons
Barrel Containers 5-5
Link Icons 5-6
Network Element Icons 5-7
Performance Management Resources 5-4
rules 5-1
Square Containers 5-4
Terminal Resources 5-3
GSM18/UMTS04
A-2 Index
Information
class 3-2
Service Summary
class 3-2
SIM Replacement 3-102
SLR 1-32
State Change
class 3-2
STORM 1-34
Summary OMs 2-16
Sun MC 1-36
Supported OMs 2-2
MSC/VLR OM groups 2-2
Multi-tuple Base OM Groups 2-10
Multi-tuple HLR100 OM groups 2-14
Multi-tuple MSC/VLR OM groups 2-6
Single-tuple Base OM Groups 2-8
Single-tuple HLR100 OM groups 2-11
Single-tuple MSC OM groups 2-5
L
Log index 4-1
Log(s) ??–3-119
categorizing events 3-2
date and time 3-3
defining 3-2
event class definitions 3-2
example 3-3
field descriptions 3-12
header information 3-3
name and number 3-3
severity and event type 3-3
M
Major severity 3-3
MSC correlated OMs 2-85
MSCBILL
OM group 2-94
MSCBILL2
OM group 2-95
T
TERMREASON
OM group 2-102
TRAFFICDEST
OM group 2-103
TRAFFICDEST2
OM group 2-107
TRAFFICDEST3
OM group 2-113
Trouble
event class 3-2
TRUNKIO
OM group 2-114
O
OMC-S components 1-2
OMC-S/CEM system logs 3-1
P
PREFIXDIAG
OM group 2-101
U
R
USP 1-30
R4 BICN/BICC
CEM support 1-16
Passport OMs 1-17
provisioning wizards 1-17
V
VCN Logs collected by OMC-S 4-2
S
SAM21 1-33
SDM 1-6
OMC-S applications 1-12
Software 1-11
411-8111-803
Standard
01.06
May 2006
test
Family Product Manual Contacts Copyright Confidentiality Legal
OAM
Reference Manual
To order documentation from Nortel Networks Global Wireless Knowledge Services, call
(1) (877) 662-5669
To report a problem in this document, call
(1) (877) 662-5669
or send e-mail from the Nortel Networks Customer Training & Documentation World Wide Web site at
http://www.nortel.com/td
Copyright © 2004–2006 Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its
employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the
same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly
authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant.
* Nortel Networks, the Nortel Networks logo, the Globemark HOW the WORLD SHARES IDEAS, and Unified Networks are
trademarks of Nortel Networks. DMS, DMS-HLR, DMS-MSC, MAP, and SuperNode are trademarks of Nortel Networks. GSM is a
trademark of GSM MOU Association.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
Document number: 411-8111-803
Product release: GSM18/UMTS04
Document version: Standard 01.06
Date: May 2006
Originated in the United States of America

Reference Manual - WillowCherry.COM

Transcription

Similar documents

GSM Security Camera - Jablotron Security

Burglar Alarm Permit Form - Palm Beach County Sheriff`s Office

sensation

SPRAY PRODUCTS

Dome PoE H.264 - Atlantis-Land

ETRM Solutions - Primetech Systems Inc.

the new instrument for pilots chronospace

Shasta 5000 Broadband Service Node in the

Site Plan - City of Madison

Indonesian Diaspora Network Southern California