411-8111-503 05 02 PDF

411-8111-503
GSM / UMTS
Voice Core Network
OAM User Guide
GSM18/UMTS04 Preliminary 05.02 March 2005
DRAFT
test
GSM / UMTS
Voice Core Network
OAM User Guide
Document number: 411-8111-503

Product release: GSM18/UMTS04
Document version: Preliminary 05.02
Date: March 2005
Copyright Country of printing Confidentiality Legal statements Trademarks
Copyright © 1996–2005 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 © 1996–2005 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-503 Preliminary 05.02 March 2005

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 so-
called "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.
GSM / UMTS Voice Core Network OAM User Guide 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: jloup@gzip.org
Mark Adler: madler@alumni.caltech.edu

v
Publication history
March 2005
GSM18/UMTS04, Preliminary, 05.02. This release of the document includes:
• additional review comments
• updated Configuration Management wizard information
• updated Fault Management toolbar description
• added information on alarm timestamps
• updated Performance Manager and Summary Report information
December 2004
GSM18/UMTS04, Draft, 05.01. The document was divided into three separate
NTPs. The following information has been added: NSS18/UMTS04 software
changes.
October 2004
NSS17/UMTS03 Revision 04.16. This Standard release of the document is
created for the NSS17/UMTS03 software release and includes:
• updated Mass Export information
September 2004
• updated Configuration Management information
August 2004
created for the NSS17/UMTS03 software release and includes additional
review comments.

vi Publication history
June 2004
• updated Ports and Services lists
• updated Performance Management information
• addition of Secure Shell installation information
• updated managed nodes configuration procedures and associated
parameters information
April 2004
NSS17/UMTS03 Revision 04.12. This Preliminary release of the document is
• updated BICC Configuration Wizards
• updated Performance Management information
February 2004
NSS17/UMTS03 Revision 04.11. This release of the document is created for
the NSS17/UMTS03 software release and includes additional review
comments and updated BICC information.
February 2004
the NSS17/UMTS03 software release. This release includes additional review
comments.
December 2003
the NSS17/UMTS03 software release. This release includes updated Mass
Export information.
October 2003
the NSS17/UMTS03 software release. This release includes the addition of
GSM BICC functionality and the following changes:
• Addition of BICC Configuration Wizards
• Updated Mass Export information
• Addition of OM Correlation Editor

Publication history vii
September 2003
the NSS17/UMTS03 software release. This release includes separating the
document into two volumes.
September 2003
review comments and updated Configuration Management Wizard
information.
September 2003
review comments and the following changes:
• Updated Ports and Services lists
• Telnet/FTP Pass Through on SDM
• Updated Mass Export information
August 2003
SDM and CEM server configuration and maintenance procedures.
July 2003
created for the NSS17/UMTS03 software release. This release includes the
addition of review comments and the following NSS17/UMTS03 software
changes:
• Updated Sun Management Center information
• CEM GUI Enhancements
• Addition of CEM Ports and Services lists
• CEM support for Univity HLR
June 2003
addition of review comments and the following NSS17/UMTS03 software
changes:
• CEM Security Enhancements

viii Publication history
• CEM support for R4 BICN

• Updated MDM information
April 2003
NSS17/UMTS03 Revision 04.01. This Draft release of the document is created
for the NSS16/UMTS03 software release. This release includes the addition of
review comments and the following NSS17/UMTS03 software changes:
• New Layout Management features in the File menu
• Addition of R4 BICN provisioning in the Configuration Manager
interface
• New AutoLogin feature for MAP, Telnet, and FTP in the Tools menu
• Addition of SSH protocols for secure MAP, Telnet, and FTP
January 2003
addition of review comments, CR changes.
July 2002
addition of review comments, CR changes.
July 2002
NSS16/UMTS03 Revision 03.01. This Draft release of the document is created
for the NSS16/UMTS03 software release. This release includes the addition of
review comments, CR changes, and the following NSS16/UMTS03 software
changes:
• Introduction of Call Trace feature
• Introduction of USP functionality
May 2002
NSS15/UMTS02 v 2.0 Revision 02.05. This second Preliminary release of
the document is created for the NSS15/UMTS02 software release. This
release includes the addition of review comments and CR changes.
April 2002
NSS15/UMTS02 v 2.0 Revision 02.04. This Preliminary release of the
document is created for the NSS15/UMTS02 software release. This release
includes the addition of review comments and CR changes.

Publication history ix
March 2002
NSS15/UMTS02 v 2.0 Revision 02.03. This release of the document is
addition of review comments and CR changes.
February 2002
NSS15/UMTS02 v 2.0 Revision 02.02. This draft release of the document is
addition of review comments and CR changes.
November 2001
NSS15/UMTS02 v 2.0 Revision 02.01. This draft release of the document is
addition of review comments and the following UMTS 02 software changes:
• New Add Server feature at the File Menu interface
• Addition of Customizable OM Window at the Performance Manager
interface
• Updates to Installation chapter to reflect software upgrades
October 2001
UMTS01/NSS14 v 1.2 Revision 01.08. This Standard release of the
document is created for the UMTS01/NSS14 software release. This release
includes the addition of review comments.
September 2001
UMTS01/NSS14 v 1.2 Revision 01.07. This Preliminary release of the
document was created for the UMTS01/NSS14 software release. This release
includes the addition of review comments.
August 2001
documentation was created for the UMTS01/NSS14 software release. This
release includes the following changes:
• XA-Core and MMU information
• New screen shots
• Mass Export function moved from System Administration to Performance
Management
• New Tools menu bar

x Publication history
July 2001
release includes technical review comments, IT2 features, and the following
changes:
• Add section on installing Element Manager from a Sun platform.
• Add new installation procedure for Element Manager.
• Add HLR Summary Report.
• Add HLR SUMPAGE registers.
• Add Configuration Management Wizard and new Table Editor interface.
July 2001
UMTS01/NSS14 v 1.1. Revision 01.04. This Preliminary release of the
release includes technical review comments and the following changes:
• Revised formula for XACore switch.
• Miscellaneous shortcut keys for the Element Manager were modified.
June 2001
release includes technical review comments and the following changes:
• Addition of hlrMeasurementFunct under the HLR container in the
compCore SuperNode.
May 2001
release includes technical review comments.
April 2001
documentation was created for the UMTS01/NSS14 software release.

xi
Contents 1
About this document xxvii

Notice of design intent and enhancement xxvii
Audience for this document xxvii
Organization of this document xxviii
Indication of hypertext links xxix
Related documents xxix
Cancellation index xxx
Software release applicability xxx
GSM18/UMTS04 Product Computing Module Loads xxx
Getting started 1-1

Start the Core Element Manager application 1-2
Element Manager on-line help files on a workstation 1-2
Start the Element Manager installed on a PC workstation 1-2
Start the Element Manager installed on a Sun workstation 1-2
Start the Element Manager from a Sun or PC using Java Web Start 1-3
Start the Element Manager from an NSP using Java Web Start 1-3
CEM user login (security) window 1-3
User account lock-out policy 1-5
Core Element Manager window structure 1-6
Status bar 1-7
Element Manager Menu Bar 1-8
Keyboard shortcuts 1-13
Copy and paste 1-16
CEM within Wireless Network Management System (W-NMS) 1-17
W-NMS related documents 1-17
Open CEM browser from NSP Resource browser 1-17
View the network element icons 1-17
Display NSP information 1-19
Icons show alarm information 1-21
Open the Alarm Manager window 1-21
Open the Element Manager window 1-22
Open the Performance Manager window 1-22
Open the Summary Report Window 1-23
Open the Threshold Manager 1-23
Open the Configuration Manager 1-24
Launching of SAM21 EM from CEM GUI 1-24

xii Contents
Launching of STORM EM from CEM GUI 1-24

CEM security 1-24
LDAP and SSL supported 1-25
Integration of CEM login with other network nodes 1-26
User group access control 1-27
Transparent user preferences 1-27
Automatic login capability for Telnet, FTP and MAP sessions 1-28
Secure Shell access between CEM browser and any SSH Server 1-28
Security alarms 1-28
CEM restrictions and limitations 1-29
File menu 2-1

Display a new window 2-2
Layout management 2-2
New layout 2-3
Open layout 2-3
Show layout 2-4
Save layout 2-4
Layout management window 2-5
Layout management restrictions and limitations 2-10
Set up the network display 2-11
Add an element 2-13
Relocate an element 2-16
Disconnect/reconnect an element 2-16
Remove an element 2-17
Rename or change the location of an element 2-18
Exclude element(s) 2-18
Find NE 2-18
Display the Info log 2-20
Transparent user preferences 2-22
Transparent user preferences for W-NMS users 2-24
Export alarm data 2-25
Export alarm by format 2-25
Export alarm data by date 2-30
Configuration management 3-1

Configuration management restrictions and limitations 3-2
Configuration Manager toolbar 3-2
Configuration Menu 3-4
Drill Up/Drill Down 3-7
Information on elements 3-7
Set a Background Image 3-12
Clear the background image 3-13
Arrange icons 3-13
Information bubble 3-14
Pop-up menus for node manipulation 3-15
Configuration Management Window 3-15
Reshaping region nodes 3-16
Workspaces and sorting items 3-17
Physical mode 3-20

Contents xiii
Logical mode 3-22

Icon mode 3-22
List mode 3-26
Pin mode 3-27
Shelf level display 3-28
Find carriers and linksets 3-29
Support storage, setting, and retrieval of notes for nodes 3-29
Integration with performance management 3-30
Print support for the configuration management panel window 3-30
DMS table configuration 3-30
Security 3-31
Table Editor 3-32
Table Editor menus 3-45
Help Menu 3-46
Table Access Editor limitations 3-46
Configuration management wizards 3-47
Wizards for R4 provisioning 3-49
Add Trunk Group Wizard 3-50
Delete Trunk Group Wizard 3-61
Add BICN Trunk Group Wizard 3-67
Add BICN Trunk Members Wizard 3-83
Add MGW Wizard 3-91
Delete MGW Wizard 3-95
BICN Audit Wizard 3-99
Add CFIWF Trunk Group Wizard 3-105
Delete CFIWF Trunk Group Wizard 3-119
Migrate Trunks to MGW Wizard 3-124
Add BICC Trunk Group Wizard 3-147
Delete BICC Trunk Group wizard 3-149
Add MGWPOOL wizard 3-150
Delete MGWPOOL Wizard 3-152
Recovery Wizard 3-153
Fallback Wizard 3-156
MDM 3-162
MDM toolset launch from CEM GUI 3-162
MDM configuration tool launch from CEM GUI 3-163
Remote MDM configuration 3-167
Fault management 4-1

Fault management window 4-2
Fault menu 4-3
Fault management toolbar 4-4
Histograms 4-10
Alarm list box display 4-11
Alarm timestamps 4-12
Alarm list box column descriptions 4-13
Alarm status colors 4-14
Clearing alarms 4-15
Display Info Windows from the alarm list 4-16
Filters and Actions 4-18

xiv Contents
Filters tab 4-19

Drop-down list boxes 4-22
User-defined filters list box 4-25
Actions tab 4-27
Combinations tab 4-31
Performance management 5-1

Performance management restrictions and limitations 5-2
Performance menu 5-4
Historical OMs versus current OMs 5-5
Performance Manager 5-6
Performance Manager menu bar 5-7
OM selection area 5-8
Data display area 5-9
OM report editing area 5-14
OM templates 5-17
Create an instant OM data query 5-21
Create a new OM report 5-22
PM Dashboard window 5-23
Data collection 5-27
Plug-in parser capability 5-27
Support for 3GPP 5-27
Support for different time zones 5-27
MDP data collector 5-28
USP/SLR/UNPM/SGW data collector 5-28
GGSN data collector 5-29
SIG data collector 5-29
ArchiveAdmin tool 5-30
Launch ArchiveAdmin tool 5-30
Quit from ArchiveAdmin tool 5-30
ArchiveAdmin menu 5-30
Change retention period of archive 5-31
Mass export 5-32
Export of ACT102 and CAP logs 5-33
Change maximum number of files per transfer 5-39
OM archive backup 5-40
Summary Report window 5-41
Billing to OM GUI 5-43
Dialed Digits Manager 5-47
Diagnostic Manager 5-55
Performance summary report 5-59
Call statistics from billing 5-62
Threshold Manager window 5-67
Threshold Manager features 5-69
How to view and set thresholds 5-70
Nortel defined thresholds for GPRS SGSN 5-71
Threshold alarm (TMN318) format 5-72
Threshold management restrictions and limitations 5-73
Data Notification 5-73
Mass Export 5-74

Contents xv
Supported OM groups 5-77

Profile Editor 5-93
Mass export status table 5-96
Mass export file name protocol 5-98
Mass export file format 5-99
Network element associated types 5-101
Mass export back up files 5-101
Export profiles 5-102
Limit to individual selected groups 5-104
Customizable OM window 5-105
OM Correlation Editor 5-106
Single-tuple correlations 5-108
Multi-tuple correlations 5-108
Components of the OM Correlation Editor GUI 5-109
Export 5-110
Get All Correlations 5-110
Edit tab pane 5-111
Apply tab pane 5-116
OM Correlation Editor restrictions and limitations 5-118
Call trace 6-1

Call trace menu 6-1
Activate/deactivate trace 6-1
Restrictions and limitations 6-2
Call trace activate/deactivate menu bar 6-3
Call trace activate/deactivate window tabs 6-5
Manage trace records 6-22
Manage trace records menu bar 6-23
Manage trace records toggle buttons 6-24
Manage trace records filter field 6-25
Manage trace records histogram 6-26
Manage trace records summary list 6-28
Delete trace records 6-29
View trace record window 6-29
Call trace record examples 6-32
Disable query to HLR 6-46
Tools 7-1
Tools menu 7-1
Messaging 7-2
Maintenance commands 7-4
@componentInstance macro 7-6
USP/SLR maintenance action 7-8
Construct maintenance commands 7-11
Add, delete and edit maintenance commands 7-12
Use Encryption 7-13
Set AutoLogin 7-14
MAP 7-14
MAP automatic login 7-14
File menu 7-16

xvi Contents
Preferences menu 7-17

Automatic posting of the node 7-17
Telnet Interface 7-18
Telnet automatic login 7-19
Configuration of Telnet session timeout value 7-21
Maintenance command example 7-21
Error messages 7-26
Using the Telnet command 7-26
FTP interface 7-28
FTP automatic login 7-29
Configuration of FTP session timeout value 7-30
FTP window 7-31
Local system and remote system 7-32
Transfer file options 7-33
FTP console 7-33
FTP access configuration 7-34
SSH suite 7-34
SSH (Telnet) 7-35
Secure MAP login 7-40
SFTP 7-40
SCP 7-42
Key generation 7-46
USP Visual Basic GUI 7-53
USP Java GUI 7-55
Restrictions and limitations 7-56
Administration management 8-1

Administration Manager 8-1
Status monitoring 8-1
SDM/FT selection list 8-3
Data lists 8-3
Logical volume list 8-3
Applications list 8-4
Communication link list 8-4
Force Out 8-4
Limitations 8-5
Server application management 8-5
Menu bar 8-6
Information window 8-6
Application states 8-7
Application management commands 8-7
Application management status 8-8
Command line interface 8-9
Change CEM password 8-10
Change CEM password error windows 8-11
CEM password complexity 8-12
System initiated change of the CEM password 8-13
User initiated change of the CEM password 8-13
Group Access Control 8-13
User groups 8-14

Contents xvii
Configure Group Access Control window 8-17

Group Access Control in a W-NMS environment 8-23
On-line help 9-1

Element Manager Help menu 9-1
Help Info window 9-3
Help User’s Guide 9-4
Annotations 9-5
Search 9-12
Help in the Performance Manager menu 9-14
Help using (?) 9-15
Index A-1
Figures
Figure 1-1 CORE Element Manager banner 1-3
Figure 1-2 CEM User Login window 1-4
Figure 1-3 Element Manager main window 1-7
Figure 1-4 Waiting 1-7
Figure 1-5 Messages 1-8
Figure 1-6 Element Manager Menu bar 1-8
Figure 1-7 Element Manager File menu 1-9
Figure 1-8 Element Manager Fault menu 1-10
Figure 1-9 Element Manager Configuration menu 1-10
Figure 1-10 Element Manager Performance Menu 1-11
Figure 1-11 Element Manager Call Trace menu 1-11
Figure 1-12 Element Manager Tools menu 1-12
Figure 1-13 Element Manager Administration menu 1-12
Figure 1-14 Element Manager Help menu 1-13
Figure 1-15 Copy option from pop-up 1-16
Figure 1-16 Wireless filter group 1-18
Figure 1-17 Details 1-20
Figure 1-18 NSP Resource Browser pop-up menu 1-21
Figure 1-19 Alarms Manager window 1-22
Figure 1-20 Performance Manager window 1-23
Figure 2-1 File menu 2-2
Figure 2-2 Open layout window 2-4
Figure 2-3 Layout management window 2-5
Figure 2-4 Region pop-up menu 2-8
Figure 2-5 Info window 2-8
Figure 2-6 Server pop-up menu 2-9
Figure 2-7 IP Node / Slice pop-up menu 2-10
Figure 2-8 Network Element pop-up menu 2-10
Figure 2-9 Example MSC/HLR network layout 2-12
Figure 2-10 MSC/HLR element 2-13
Figure 2-11 Add element 2-13
Figure 2-12 Example hosts files (WindowsNT) 2-14
Figure 2-13 Select Server 2-15
Figure 2-14 Add Server 2-15
Figure 2-15 Move Node window 2-16

xviii Contents
Figure 2-16 Disconnect confirmation 2-17

Figure 2-17 Reconnect confirmation 2-17
Figure 2-18 Remove Node window 2-18
Figure 2-19 Find NE window 2-19
Figure 2-20 Find NE window pop-up menu 2-20
Figure 2-21 Info log window 2-21
Figure 2-22 Preferences General tab option 2-22
Figure 2-23 User preferences for functionality under the Tools menu 2-24
Figure 2-24 CEM preferences window in W-NMS environment 2-25
Figure 2-25 Export alarm menu 2-26
Figure 2-26 Export alarm window 2-27
Figure 2-27 Sample alarm data file in full format 2-28
Figure 2-28 Sample alarm data file in histogram (text) format 2-29
Figure 2-29 Sample alarm data file in component list (text) format 2-30
Figure 2-30 Export Alarm Database by Date 2-30
Figure 3-1 Configuration manager tool bar 3-3
Figure 3-2 Configuration menu options 3-6
Figure 3-4 CM window with background image 3-12
Figure 3-5 Set Background 3-13
Figure 3-6 Information bubble with the number of sub-elements 3-14
Figure 3-7 Reshaping Region Nodes Pop-up Menu 3-16
Figure 3-8 Reshaping option menu 3-16
Figure 3-9 Configuration Management Window Pop-up Menu 3-18
Figure 3-10 Workspace Name Window 3-19
Figure 3-11 Workspace Name Window 3-20
Figure 3-12 Configuration Management window in physical mode 3-21
Figure 3-13 Configuration Management window in logical mode 3-22
Figure 3-14 Configuration Management window in icon mode 3-22
Figure 3-15 Configuration Management window in list mode 3-26
Figure 3-16 Configuration Management window in pin mode 3-27
Figure 3-17 Pinned Nodes 3-28
Figure 3-18 Shelf level display of message switch for DMS 3-29
Figure 3-19 Configuration menu options 3-31
Figure 3-20 Default User Login screen 3-32
Figure 3-21 Table Access Editor 3-33
Figure 3-22 Table Access Editor toolbar 3-34
Figure 3-23 Table drop down menu 3-35
Figure 3-24 Display tuples 3-36
Figure 3-25 Tuple table 3-36
Figure 3-26 Pop-up menu view 3-37
Figure 3-27 Tuple pop-up menu 3-38
Figure 3-28 Export tuple 3-39
Figure 3-29 Add Tuple Window 3-40
Figure 3-30 Changing Tuple window 3-41
Figure 3-31 Sub-tuple 3-44
Figure 3-32 Table Editor File menu 3-45
Figure 3-33 Table Access Info Log 3-45
Figure 3-34 Help menu 3-46
Figure 3-35 Main wizard interface 3-48
Figure 3-36 Select target node screen 3-50

Contents xix
Figure 3-37 User ID screen 3-51

Figure 3-38 CLLI prompt 3-51
Figure 3-39 Add CLLI tuple 3-52
Figure 3-40 Add Trunk Group 3-53
Figure 3-41 Select the Direction and CICPOOL 3-53
Figure 3-42 Trunk Subgroup Number 3-54
Figure 3-43 Defining trunk members 3-55
Figure 3-44 Card Code screen 3-56
Figure 3-45 Signalling Type screen 3-57
Figure 3-46 Translation System screen 3-57
Figure 3-47 Translation Name screen 3-58
Figure 3-48 Billing Destination Number screen 3-58
Figure 3-49 Trunk C7UP Timer screen 3-59
Figure 3-50 Submit tuples 3-60
Figure 3-51 Target node screen 3-61
Figure 3-52 User ID verification 3-62
Figure 3-53 User ID verification error 3-62
Figure 3-54 Network type selection 3-63
Figure 3-55 Trunk group selection 3-63
Figure 3-56 Busy/Offline prompt 3-64
Figure 3-57 Submit window 3-65
Figure 3-58 Successful submission 3-66
Figure 3-59 Select Target Node 3-67
Figure 3-60 User ID Verification 3-68
Figure 3-61 Select Passport Node 3-69
Figure 3-62 Passport User ID Verification 3-70
Figure 3-63 Initial Add Trunk Name Screen shot 3-71
Figure 3-64 After clicking the ‘Show Info...’ Button 3-72
Figure 3-65 Typing in a CLLI Name 3-73
Figure 3-66 Add Table CLLI entries 3-74
Figure 3-67 Adding Trunk Group Type Screen shot 3-75
Figure 3-68 Signalling Type Screen shot 3-75
Figure 3-69 Translation System Screenshot 3-76
Figure 3-70 Translation Name Screenshot 3-76
Figure 3-71 Billing DN Screenshot 3-77
Figure 3-72 Adding Table TRKSGRP Screenshot 3-78
Figure 3-73 Trunk Protocol Screenshot 3-78
Figure 3-74 Trunk C7UP Timer Name Screen shot 3-79
Figure 3-75 Add Table TRKMEM Tuples 3-80
Figure 3-76 Initial Submit Tuple Screenshot 3-81
Figure 3-77 Completion of Submit Tuple 3-82
Figure 3-82 Select Trunk Subgroup 3-87
Figure 3-83 Add Table TRKMEM Tuples 3-89
Figure 3-84 Target Node Screenshot 3-91
Figure 3-85 User ID/Password Verification Screenshot 3-92
Figure 3-86 Passport Node Name 3-92

xx Contents
Figure 3-88 Add GWINV Table Tuple 3-94

Figure 3-89 Select a Target Node 3-95
Figure 3-91 Select MGW to be removed 3-97
Figure 3-92 Submit Tuple 3-98
Figure 3-97 MGW Audit 3-104
Figure 3-98 Selecting a Target MSC 3-105
Figure 3-99 DMS Login 3-106
Figure 3-100 Selecting a Passport Node 3-106
Figure 3-101 Passport Login 3-107
Figure 3-102 Defining a CIWF CLLI 3-107
Figure 3-104 Define Trunk Group Type 3-109
Figure 3-105 Defining Trunk Subgroup Number 3-109
Figure 3-106 Defining Table TRKMEM entries 3-110
Figure 3-107 Define MIWF CLLI 3-111
Figure 3-109 Adding Trunk Group Type 3-112
Figure 3-110 Defining trunk sub-group number 3-113
Figure 3-111 Defining table TRKMEM entries 3-114
Figure 3-112 Configuring CFIWFMAP table tuple 3-115
Figure 3-113 Submit Tuples display 3-116
Figure 3-114 Submitting Tuples 3-117
Figure 3-115 Completion of Submit Tuples 3-118
Figure 3-116 Selecting a Target Node 3-120
Figure 3-118 CFIWFMAP tuple selection 3-121
Figure 3-119 INB prompt message 3-121
Figure 3-120 Submit tuples display 3-122
Figure 3-121 Completion of Submit Tuples 3-123
Figure 3-122 Select a target MSC 3-124
Figure 3-123 DMS Login 3-125
Figure 3-124 Trunk Migration Strategy Selection 3-126
Figure 3-125 Select trunk group 3-127
Figure 3-126 Select the trunk members 3-128
Figure 3-127 Select the range of members 3-129
Figure 3-128 Select the carrier to be migrated 3-130
Figure 3-129 Carrier circuits that will be migrated is displayed 3-131
Figure 3-130 Select the Passport 3-132
Figure 3-131 Login to the Passport 3-133
Figure 3-132 Select the VSP 3-134
Figure 3-133 Select the Brag 3-135
Figure 3-134 Carrier - Passport/MGW/Brag combination displayed 3-136
Figure 3-135 Trunk Migration Approach 3-137
Figure 3-136 INB the trunk members 3-137
Figure 3-137 Tuples ready to be submitted (tuples not displayed) 3-138
Figure 3-138 Tuples ready to be submitted (tuples displayed) 3-139

Contents xxi

Figure 3-141 Submit completed successfully 3-142
Figure 3-142 DMOPRO based Migration 3-143
Figure 3-143 DMOPRO filename 3-144
Figure 3-144 Example of DMOPRO file generated 3-145
Figure 3-145 Select a file to recover 3-154
Figure 3-147 Fallback file 3-157
Figure 3-149 Submit tuples 3-159
Figure 3-150 Submit Tuples (tuples displayed) 3-160
Figure 3-151 Fallback successfully completed 3-161
Figure 3-152 Launch MDM Toolset 3-163
Figure 3-153 MDM Configuration Tool 3-165
Figure 4-1 Fault Management window - stand-alone mode 4-3
Figure 4-2 Fault menu 4-4
Figure 4-3 Toolbar - stand-alone mode 4-5
Figure 4-4 Toolbar - server mode 4-5
Figure 4-5 Histogram 4-10
Figure 4-6 Right click on alarm 4-12
Figure 4-7 Alarm info window 4-17
Figure 4-8 Custom Filters & Actions Panel window 4-18
Figure 4-9 Severity box 4-22
Figure 4-10 Notes box 4-23
Figure 4-11 Element box 4-23
Figure 4-12 Resources box 4-24
Figure 4-13 Acknowledged-by box 4-24
Figure 4-14 Cleared-by box 4-24
Figure 4-15 Logs box 4-24
Figure 4-16 Single-Selection Pop-Up Menu 4-25
Figure 4-17 Pop-Up Menu with Include Enabled 4-26
Figure 4-18 Pop-Up Menu for Multiple Filter Selections 4-27
Figure 4-19 Actions Tab 4-28
Figure 4-20 File chooser window 4-29
Figure 4-21 Single Selection Pop-Up Menu 4-30
Figure 4-22 Multiple-selection pop-up menu 4-31
Figure 4-23 Combinations tab 4-32
Figure 4-24 Selected Filter field and drop-down list 4-34
Figure 4-25 Selected Action drop-down list 4-35
Figure 4-26 Pop-up menu when single item is selected 4-36
Figure 4-27 Multiple-selection pop-up menu 4-37
Figure 5-1 Performance Menu Options 5-5
Figure 5-3 Data display pop-up menu & Options submenu 5-12
Figure 5-4 Data display pop-up menu & Threshold submenu - thresholds not
displayed 5-13
Figure 5-5 Data display pop-up menu & Threshold submenu - thresholds
displayed 5-14
Figure 5-6 Report Tree Pop-up Menu 5-16
Figure 5-7 Template pop-up menu 5-18

xxii Contents
Figure 5-8 Apply Template to NEs 5-19

Figure 5-9 PM Dashboard Window 5-23
Figure 5-10 Dashboard pop-up menu 5-24
Figure 5-11 Legend window 5-25
Figure 5-12 Report menu options 5-26
Figure 5-13 Customize Dashboard Color window 5-26
Figure 5-14 ArchiveAdmin Main Menu 5-31
Figure 5-15 Retention setting menu 5-31
Figure 5-16 Change Monthly Retention Value 5-31
Figure 5-17 Change Daily Retention Value 5-32
Figure 5-18 Change Hourly Retention Value 5-32
Figure 5-19 Mass Export Menu 5-33
Figure 5-20 ACT102 Log Example 5-34
Figure 5-21 CAP101 Log Example 5-34
Figure 5-22 Show Profiles 5-35
Figure 5-23 Add a profile 5-36
Figure 5-24 Delete a profile 5-37
Figure 5-25 Modify a profile 5-38
Figure 5-26 Reset Export 5-39
Figure 5-27 Change Maximum number of file transfer per export period 5-39
Figure 5-28 Summary Report window 5-41
Figure 5-29 Summary Report window with switch data 5-42
Figure 5-30 Info GUI for Ombill Configuration 5-44
Figure 5-31 Summary Report window 5-47
Figure 5-32 Dialed Digits Manager window 5-48
Figure 5-33 Relationship between Calling Number, Called Number and Forward-To
Number 5-49
Figure 5-34 Trunk Configuration GUI 5-53
Figure 5-35 Update Notification for Dialed Digits Manager 5-55
Figure 5-36 Diagnostic Manager window 5-56
Figure 5-37 Performance Summary report window 5-59
Figure 5-38 Threshold window 5-67
Figure 5-39 Data Notifications window 5-74
Figure 5-40 Mass Export Window 5-75
Figure 5-41 Profile Editor to Help User Edit A Profile 5-94
Figure 5-42 Profile Editor Has pop-up Menu to Help User Select OMs 5-95
Figure 5-43 Profile View shows profile and its export sources information 5-96
Figure 5-44 Network Element View shows network element related sources and its
export profiles 5-97
Figure 5-45 Launch profile editor 5-97
Figure 5-46 Mass Export File Name Protocol for GEM17 5-98
Figure 5-47 Mass Export File Name Protocol for GEM16 5-98
Figure 5-48 Back-up Mass Export File Name Protocol 5-99
Figure 5-49 Tab Mass Export File Header 5-100
Figure 5-50 Tab Mass Export File 5-100
Figure 5-51 CSV Mass Export File Header 5-101
Figure 5-52 CSV Mass Export File 5-101
Figure 5-53 Customize OM Window 5-105
Figure 5-54 OM Correlation Editor - Edit tab pane 5-108
Figure 5-55 Pop-up menu for user defined correlation - left table 5-113
Figure 5-56 Pop-up menu for user defined correlation - right table 5-113

Contents xxiii
Figure 5-57 Pop-up menu for Nortel defined correlation - right table 5-113
Figure 5-58 Delete confirmation 5-114
Figure 5-59 OM Correlation Editor - using the Show command to display a long
definition 5-115
Figure 5-60 Save confirmation 5-116
Figure 5-61 OM Correlation Editor - Apply tab pane 5-117
Figure 6-1 Accessing Call Trace 6-1
Figure 6-2 Call Trace Activate/Deactivate window 6-2
Figure 6-3 Non Call Trace User Error Window 6-2
Figure 6-4 Print menu options 6-3
Figure 6-5 IMSI Print Report 6-4
Figure 6-6 About Call Trace 6-5
Figure 6-7 IMSI tab 6-6
Figure 6-8 Deactivation confirmation prompt 6-7
Figure 6-9 IMSI Activate Trace window 6-8
Figure 6-10 Foreign Subscriber prompt 6-9
Figure 6-11 MSISDN tab 6-10
Figure 6-12 MSISDN Activate Trace window 6-11
Figure 6-13 Trunk tab 6-13
Figure 6-14 Trunk Activate Trace window 6-14
Figure 6-15 PSTN tab panel 6-16
Figure 6-16 PSTN Activate Trace window 6-17
Figure 6-17 Blank IMSI warning 6-18
Figure 6-18 Blank MSISDN warning 6-18
Figure 6-19 Blank Trunk ID warning 6-19
Figure 6-20 Blank PSTN Number warning 6-19
Figure 6-21 Blank Trace Reference warning 6-19
Figure 6-22 Activated IMSI warning 6-20
Figure 6-23 Activated MSISDN warning 6-20
Figure 6-24 Activated Trunk ID warning 6-20
Figure 6-25 Activated PSTN warning 6-21
Figure 6-26 Network Element warning 6-21
Figure 6-27 Range Input warning 6-21
Figure 6-28 Incomplete Range warning 6-22
Figure 6-29 Overlapping Range warning 6-22
Figure 6-30 Manage Trace Records window 6-23
Figure 6-31 No records export warning 6-24
Figure 6-32 Example of Filtering text string 6-26
Figure 6-33 Example of Filtering results 6-26
Figure 6-34 Selecting tracking of Trace records 6-27
Figure 6-35 Histogram X and Y axis 6-27
Figure 6-36 Manage Trace Records summary list 6-28
Figure 6-37 View Trace Record window 6-30
Figure 6-38 Notes text box with buttons 6-31
Figure 6-39 Example of Notes indication 6-32
Figure 6-40 Location Update CTR Example 6-33
Figure 6-41 Setup CTR Example 6-34
Figure 6-42 Answer CTR Example 6-35
Figure 6-43 Disconnect CTR Example 6-35
Figure 6-44 Redirection CTR Example 6-36
Figure 6-45 CISS CTR Example 6-37

xxiv Contents
Figure 6-46 Detach CTR Example 6-38

Figure 6-47 Call Hold CTR Example 6-38
Figure 6-48 Call Retrieve CTR Example 6-39
Figure 6-49 Call Waiting CTR Example 6-39
Figure 6-50 Call Barring CTR Example 6-40
Figure 6-51 Explicit Call Transfer CTR Example 6-41
Figure 6-52 Multi Party CTR Example 6-42
Figure 6-53 SMS CTR Example 6-43
Figure 6-54 Intercepted Call Failure CTR Example 6-44
Figure 6-55 Classmark Update CTR Example 6-45
Figure 6-56 Handover CTR Example 6-45
Figure 6-57 Activate Trace window 6-46
Figure 7-1 Tools menu options 7-1
Figure 7-2 Messages window 7-3
Figure 7-3 Maintenance Commands window 7-5
Figure 7-4 VC4 Component 7-7
Figure 7-5 Final Help Command 7-8
Figure 7-6 Use Encryption menu item 7-13
Figure 7-7 MAP submenu 7-14
Figure 7-8 MAP Login window 7-15
Figure 7-9 Telnet submenu 7-18
Figure 7-10 Telnet Login Host Information window 7-19
Figure 7-11 Telnet Login window 7-20
Figure 7-12 Configure Telnet Timeout Value Window 7-21
Figure 7-13 Select MGW node 7-22
Figure 7-14 Establish telnet session 7-23
Figure 7-15 MGW login 7-24
Figure 7-16 Invoke pop-Up menu 7-25
Figure 7-17 Command response 7-26
Figure 7-18 Select telnet command 7-27
Figure 7-19 FTP submenu 7-28
Figure 7-20 FTP Login Host Information window 7-29
Figure 7-21 FTP Login window 7-30
Figure 7-22 Configure Telnet Timeout Value Window 7-31
Figure 7-23 File transfer interface window 7-32
Figure 7-24 SSH suite submenu 7-35
Figure 7-25 SSH (Telnet) window 7-36
Figure 7-26 SSH (Telnet) session 7-37
Figure 7-27 SSH (Telnet) window 7-39
Figure 7-28 SFTP window 7-40
Figure 7-29 SFTP window (Sun Solaris Platform) 7-42
Figure 7-30 SCP window 7-43
Figure 7-31 SCP window with System Navigator 7-45
Figure 7-32 PuTTY Key Generator 7-47
Figure 7-33 New key 7-48
Figure 7-34 Enter passphrase window 7-49
Figure 7-35 Existing key window 7-50
Figure 7-36 Copying the key information 7-51
Figure 7-37 SSH key generator window 7-52
Figure 7-38 xterm window 7-52
Figure 7-39 USP Visual Basic GUI 7-54

Contents xxv
Figure 7-40 Launch GUI window 7-54

Figure 7-41 USP login window 7-55
Figure 7-42 USP Java GUI 7-55
Figure 8-1 Administration menu 8-1
Figure 8-2 Administration manager main window 8-2
Figure 8-3 Force Out window 8-4
Figure 8-4 Application Management tool 8-6
Figure 8-5 Application Management commands 8-8
Figure 8-6 ManB Confirmation Window 8-8
Figure 8-7 Command Line Interface 8-9
Figure 8-8 Change CEM Password window 8-10
Figure 8-9 Configure Group Access Control Window 8-18
Figure 8-10 File Menu 8-18
Figure 8-11 Help Menu 8-19
Figure 8-12 Group Access Control Pop-Up Menu 8-20
Figure 9-1 Help menu 9-2
Figure 9-2 Core Element Manager Version window 9-2
Figure 9-4 Help window 9-4
Figure 9-5 Nortel globemark 9-4
Figure 9-6 Annotation icon 9-5
Figure 9-7 Adding an annotation 9-5
Figure 9-8 Adding HTML text to annotation 9-6
Figure 9-9 Verify HTML 9-6
Figure 9-10 HTML parsing errors 9-7
Figure 9-11 Help window with annotation list 9-8
Figure 9-12 Web icon 9-8
Figure 9-13 Annotation in pop-up window without using HTML formatting 9-9
Figure 9-14 Annotation in pop-up window using HTML formatting 9-9
Figure 9-15 Delete icon 9-9
Figure 9-16 Delete annotation 9-10
Figure 9-17 Import icon 9-10
Figure 9-18 Import annotation file 9-10
Figure 9-19 Replace annotation file 9-11
Figure 9-20 Export icon 9-11
Figure 9-21 Export annotation file 9-12
Figure 9-22 Search window 9-13
Figure 9-23 Found items 9-14
Figure 9-25 Performance management window with query button 9-15
Tables
Table 1-1 CEM User Login Error Windows 1-4
Table 1-2 List of keyboard shortcuts 1-13
Table 1-3 Miscellaneous shortcuts 1-14
Table 3-1 Configuration manager tool bar icon descriptions 3-3
Table 3-2 Info window buttons 3-8
Table 3-3 DMS attributes 3-9
Table 3-4 Element icons 3-23
Table 3-5 Table GWINV Datafill 3-95

xxvi Contents
Table 3-6 Table TRKGRP Datafill 3-119

Table 3-7 Table TRKSGRP Datafill 3-119
Table 3-8 Table TRKMEM Datafill 3-119
Table 3-9 Table CFIWFMAP Datafill 3-119
Table 3-10 Table C7TRKMEM before migration 3-146
Table 3-11 Table TRKMEM before migration 3-146
Table 3-12 Table TRKMEM after migration 3-146
Table 3-13 Table C7TRKMEM after migration 3-146
Table 3-14 Command line MDM Configuration Tool 3-165
Table 4-1 Toolbar icon descriptions 4-5
Table 4-2 Alarm list box column descriptions 4-13
Table 4-3 Alarm status colors 4-14
Table 5-1 Predefined Thresholds for GPRS SGSN 5-71
Table 5-2 OM Groups Supported by Mass Export 5-77
Table 6-1 Manage Trace Records toggle buttons’ descriptions 6-24
Table 7-1 Maintenance commands window fields and buttons 7-6
Table 7-2 File menu options 7-16
Table 7-3 Preferences Menu Options 7-17
Table 8-1 Change CEM Password window Fields and Buttons 8-10
Table 8-2 Change CEM Password Error Windows 8-11
Procedures
Procedure 1-1 Launch CEM GUI from different NEs without closing CEM GUI after
the NE being launched 1-19
Procedure 1-2 Launch CEM GUI from different NEs 1-19
Procedure 2-1 Add a MSC/HLR element to the network 2-13
Procedure 2-2 Add a Server to the network 2-15
Procedure 2-3 Remove an element from the network 2-18
Procedure 2-4 Set Export Path 2-27
Procedure 3-1 Configure automated scripts 3-167
Procedure 3-2 Unix file configuration 3-168
Procedure 5-1 Enable ACT102 and CAP Logs on the Switch 5-33
Procedure 5-2 Add a destination group 5-51
Procedure 5-3 Replace a destination group 5-51
Procedure 5-4 Delete a destination group 5-51

xxvii
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, 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 Networks
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.

xxviii 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.
• VCN knowledge - Required to understand the hierarchy of the 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:
• Getting Started - An introduction to the windows, menus, and tool bars of
the Core Element Manager.
• File menu - A description of the procedures for designing the network,
adding and removing a network element, and exporting log and OM data
files.
• Configuration management - A description of Configuration
Management, including the icons in the Configuration Management
window.
• Fault management - A description of Fault Management, including alarm
statuses and colors.
• Performance Management - A description of Performance, including the
graphs and reports produced.
• Call Trace - A description of Call Trace, including activating call trace
and managing call trace records.
• Tools - Instructions for using the Tools menu with the Element Manager.
• Administration Management - A description of the Administration
Manager which monitors the status of the SDMs in the network.
• Help - Information on using the CEM on-line help system.

About this document xxix
• 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.
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 Administration, Maintenance &
Troubleshooting Guide, NTP 411-8111-937
• GSM /UMTS Voice Core Network OAM Reference Manual, NTP 411-
8111-803
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, 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-2231-
455
• GSM / UMTS HLR100 / 200 Office Parameters Reference Manual, NTP
411-2831-455
• GSM / UMTS MSC MAP Commands Reference Manual, NTP 411-2231-
809
• GSM / UMTS HLR100 / 200 MAP Commands Reference Manual, NTP
411-2831-809

xxx About this document
Refer to the following documents for more information on the Wireless

Network Management System:
• Wireless Network Management System Administrator Guide, NTP 411-
5221-305
• Wireless Network Management System Operator Guide, NTP 411-5221-
505
• Wireless Network Management System Global Overview, NTP 411-8111-
502
Some publications of the DMS-100 Family contain information that may

relate to the subjects in this publication. For current listing of DMS-100
NTPs, refer to 297-8991-001, DMS-10 and DMS-100 Product
Documentation Directory.
Cancellation index
With the many changes occurring in product documentation due to the
introduction of PCLs, refer to 297-8991-002, DMS-10 and DMS-100
Cancellation Cross-Reference Directory, for a listing of cancelled NTPs and
the appropriate replacement NTPs.
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
& CEM), and MG18 (Media Gateway) software.

About this document xxxi
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)
• XPM20
• CBM18
• USP10.0
• SN07
• Passport v3.7
• SP20 (North America market)
• SP17.2 (International market)
• Media Gateway (MG) PCR6.1
• GSM18/UMTS04 DRUs

xxxii About this document

1-1
Getting started 1
This chapter is an introduction to the CORE Element Manager (CEM)
application and discusses the following subjects:
• starting the Element Browser on the PC and the Sun workstations
• structure of the Element Manager application window
• status bar
• the Element Manager menu bar
• keyboard shortcuts
• cut and paste functions
• open the Element Manager from the Network Server Protocol (NSP)
browser
• CEM security
• restrictions and limitations

1-2 Getting started
Start the Core Element Manager application 1

The Core Element Manager (CEM) application is used to monitor the status and
performance of voice core (switch) nodes in the Nortel Operations
Management Center (OMC) network. The Element Manager can be installed
either as an application on a PC or SUN workstation, or as a server
application on the CORE Element Manager (CEM) Server, a separate OMC
network node for gathering status and performance information.
If the Element Manager application software is installed on the workstation, it

can work in either of two OMC network configurations. If there is a CEM
Server in the network, the CEM Server accesses the SDMs in the network,
and the Element Manager workstation software accesses the CEM Server. If
there is no CEM Server in the network, the Element Manager accesses the
SDMs in the network directly for their status and performance information.
In networks having a CEM Server, a network browser using Java Web Start
on a Sun workstation, PC workstation or W-NMS NSP can access the
Element Manager server application on the CEM Server. In this configuration,
the Element Manager application software is not installed on the workstation
or NSP.
Element Manager on-line help files on a workstation

If you are going to use the On-line Help files directly from the CD-ROM,
rather than install them on the workstation, insert the applicable CD-ROM in
the drive before starting the Element Manager. This does not apply if you are
using Java Web Start.
Start the Element Manager installed on a PC workstation

To start the Core Element Manager application under Windows NT, Windows
2000, or Windows XP, click the Start button, go to Programs, click the
Element Manager folder, then click the Element Manager 17-xxx icon. If
a shortcut has been created, you may double click it.
The Core Element Manager banner is displayed (Figure 1-1), followed by the
Element Browser, showing the Element Manager main window (Figure 1-3).
Start the Element Manager installed on a Sun workstation

To start the Core Element Manager application on a Sun workstation, use the
command:
# /opt/nortel/mgr/<ElementMgr17-xxx>/sunMgr.sh.
The CORE Element Manager banner is displayed (Figure 1-1), followed by the

Getting started 1-3
Start the Element Manager from a Sun or PC using Java Web Start
Open the Internet Explorer or Netscape browser. Enter the web address
supplied by the network administrator. Example:
http://<server hostname>:8080/CEM/current_CEM
Click on Launch GUI.
Start the Element Manager from an NSP using Java Web Start
The Element Manager can also be launched from the Network Services
Platform (NSP) GUI. Launch instructions are similar to those of the Java Web
Start for the Element Manager.
Figure 1-1
CORE Element Manager banner
CEM user login (security) window

If security was chosen when the Element Manager was installed, the CEM
User Login window (Figure 1-2) is displayed with the user invokes the CEM
Browser. Enter your login name, password, and SDM name or server name to
authenticate. Changing the CEM password is explained in section “Change
CEM password” on page 8-10.

1-4 Getting started
Figure 1-2
CEM User Login window
CEM user login error windows

Table 1-1 describes the possible error windows that may be displayed if the
login verification is unsuccessful. Once the error message is acknowledged,
the user can reattempt login.
Table 1-1
CEM User Login Error Windows
Error Message Explanation
Login Failed: Invalid UserID or Password This error message is displayed when the userid
or the password entered is not valid. Upon
acknowledging this message, the user may
reattempt login by entering the valid userid and
password or attempt to login as another user.
User authenticated successfully but <userID> This error message is displayed when the userid
does not belong to any CEM defined Groups or the password entered is valid but there are no
group privileges defined for that user in the
security server. Upon acknowledging this
message, the user may attempt to login as
another user.
—sheet 1 of 2—

Getting started 1-5
Table 1-1
CEM User Login Error Windows
Login Failed: Failed to Connect This error message is displayed when the
connection with the validation server cannot be
established. Upon acknowledging this message,
the user may reattempt login by entering another
validation server name or reattempt login at a
later time.
Invalid Validation Server This error message is displayed when the

validation server name entered does not exist in
the DNS and therefore no connection can be
attempted with the validation server. Upon
acknowledging this message, the user may
reattempt login by entering another validation
server name.
Login Failed: Password retry number exceeded This error message is displayed when the user
has exceeded the max login attempts allowed by
the account lockout policy enforced by the LDAP
Directory Server or the DCE Security Server.
Upon acknowledging the message, the user may
or may not be able to attempt login right away.
The users ability to attempt login again depends
on the account policy enforced by the LDAP
Directory Server or the DCE Security Server.
Login Failed due to Password Expiration This error message is displayed when the login
attempting user’s password has expired. Upon
acknowledging this message, the user is
provided with the Change password screen to
change the current password. This scenario is
termed as “System Initiated Change Password”.
—sheet 2 of 2—
User account lock-out policy

It is possible to enable account lockout which will lockout the user after a
specific number of failed login attempts. The maximum number of failed
login attempts allowed is configurable. Once the user is locked out, the access
to the account can only be gained after the administrator has reset the account
and provides the user with a new password.

1-6 Getting started
Core Element Manager window structure 1

The Element Manager (EM) main window (Figure 1-3) includes:
• Status bar
• Tool bar
• Menu bar
• Fault Management (FM) tool bar, table, and histogram: The FM on the
SDM receives the logs from the DMS MSC/HLR, filters some of the logs,
converts some of the logs into TMN event format and originates TMN
logs of its own.
• Configuration Management (CM) tool bar and window: The CM uses a
graphic representation to display the network elements and identifies their
administrative status and availability. The CM performs the following
functions:
— allows a connection to any element in the network
— retrieves node and link information through the SDM table access
function
— discovers the initial state of the resources using RPC for the DMS
MSC/HLR
— builds the containment tree by mapping the nodes, links, and trunks
received from the managed element to their corresponding Managed
Object Instances (MOIs)
— provides resource information in either a graphic or tabular format
— updates the user interface as changes occur
— allows network element tables to be viewed and edited
• Performance manager (PM) windows (appear when you click one of the
options in the Performance menu): The PM shows supported Operational
Measurements (OMs) of DMS MSC/HLR elements. An OM is an
empirical statistical tabulation gathered to measure performance of a
particular aspect of the TMN network or one of its components. Some
OMs are a composite of basic OMs, formed by performing arithmetic
operations on them. OMs provide the operating company with switch
performance managements, traffic measurements and service data. The
PM performs the following functions:
— OM collection and storage
— GSM Standard 12.04 support
— OM study definition
— OM display
— Thresholding

Getting started 1-7
— Sum page with billing OMs

— Export alarm data
— Mass export of OMs
Figure 1-3
Element Manager main window
Status bar
The status bar at the bottom of the Element Manager main window indicates
status of the element manager (Figure 1-4).
• Waiting - The waiting message indicates that the Element Manager is

waiting for a reply from the CEM application on the SDM.
Figure 1-4
Waiting

1-8 Getting started
• Number Message - The numbered message (Figure 1-5) indicates that the
Element Manager is processing messages on its queue from an SDM.
Figure 1-5
Messages
If the input alarm rate from all connected SDMs is above 14 alarms per
second and sustained for a period longer than a day, and the Element Manager
is looking at the SDMs from which the alarms are coming, the Element
Manager warns the user of this situation by showing a red status bar at the
bottom of its window with a count of how may messages are back-logged in
its queue. If this red bar is displayed for an extended time, the Element
Manager will most likely run out of memory and freeze.
If this condition is seen, disconnect the SDM that is producing such a large
volume of alarms. Or try switching the view by drilling into a SDM that is not
producing so many alarms to see if the backlog dissipates.
Element Manager Menu Bar

The Element Manager menu bar includes the following menu items:
• File
• Fault
• Configuration
• Performance
• Call Trace
• Tools
• Administration
• Help
Figure 1-6
Element Manager Menu bar
For information on the menu bar options, refer to the sections that follow and
to the corresponding chapters of this manual.

Getting started 1-9
File menu
The File menu (Figure 1-7) allows you to manipulate the Element Manager
windows and export or print alarm data. For more information, refer to
Chapter 2, “File menu” of this manual.
Figure 1-7
Element Manager File menu

1-10 Getting started
Fault menu
The Fault menu (Figure 1-8) allows you to manipulate how alarm and state
information about DMS MSC/HLR elements is displayed. For more
information, refer to Chapter 4, “Fault management” of this manual.
Figure 1-8
Element Manager Fault menu
Configuration menu
The Configuration menu shown in Figure 1-9 allows you to determine how
configuration and state information is displayed. For more information, refer
to Chapter 3, “Configuration management” of this manual.
Figure 1-9
Element Manager Configuration menu

Getting started 1-11
Performance menu
The Performance menu (Figure 1-10) allows you to choose one of six
performance applications. For more information, refer to Chapter 5,
“Performance management” of this manual.
Figure 1-10
Element Manager Performance Menu
Call Trace menu

The Call Trace menu (Figure 1-11) allows you to activate or deactivate call
trace based on a subscriber’s IMSI or MSISDN, a PRI or ETSI Trunk ID, or a
PSTN number. For more information, refer to Chapter 6, “Call trace” of this
manual.
Figure 1-11
Element Manager Call Trace menu

Tools menu
The Tools menu (Figure 1-12) allows you to do some things on the network
that you cannot do any other way. For more information, refer to Chapter 7,
“Tools” of this manual.
Figure 1-12
Element Manager Tools menu
Administration menu
The Administration menu (Figure 1-13) allows you to open the
Administration Manager or the Server Application Management system. It
also allows for a Force Out option. Administration Management monitors the
status of the SDMs in the system. For more information, refer to Chapter 8,
“Administration management” of this manual.
Figure 1-13
Element Manager Administration menu

Help menu
The Help menu (Figure 1-14) tells you how to use the Element Manager
viewer, and how to use help. For more information, refer to Chapter 9, “On-
line help” of this document.
Figure 1-14
Element Manager Help menu
Keyboard shortcuts 1
You can use keyboard shortcuts to access menu items in the Element
Manager. The tables below show a list of keyboard shortcuts supported in the
Element Manager.
Table 1-2
List of keyboard shortcuts
Menu Menu item Shortcut
Menu File menu ALT + F
Fault menu ALT + U
Configuration menu ALT + C
Performance menu ALT + P
Tools menu ALT + T
Administration menu ALT + A
Help menu ALT + H
File Close Ctrl + O
Info Log Ctrl + I
Exit Ctrl + E
Fault Hide Ctrl + F
Acknowledge Alarm Ctrl + K
—sheet 1 of 2—

Table 1-2
List of keyboard shortcuts
Menu Menu item Shortcut
Configuration Hide Ctrl + N
Info Window Ctrl + W
DrillUp (select node ESC

above current node)
DrillDown (select node ENTER

below current node)
Table Access Ctrl + A
Wizard Ctrl + Z
Performance Performance Manager Ctrl + P
Summary Report Ctrl + S
Threshold Manager Ctrl + T
Data Notification Ctrl + G
Customize OM Groups Ctrl + B
Tools Commands Window Ctrl + D
—sheet 2 of 2—
Miscellaneous shortcuts in Table 1-3 apply only to the node selected.

Table 1-3
Miscellaneous shortcuts
Description Shortcut
Select next node ENTER
Select previous node ESC
Select first node HOME
Select last node END
—sheet 1 of 2—

Table 1-3
Miscellaneous shortcuts
Description Shortcut
Drill Up (select node above current ESC

node)
Drill Down (select node below current ENTER

node)
Scroll up configuration management PAGE UP

area
Scroll down configuration management PAGE DOWN

area
Node whose name starts with this letter KEY corresponding to a letter
(ignoring case)
—sheet 2 of 2—

Copy and paste 1

You can copy text between a MAPCI window, a Telnet window, a FTP window,
a Configuration Manager Info window, a Fault Manager alarm Info window or
Node Info window, and a text application window outside the Element Manager.
• To copy, highlight the text, the right-click the mouse to display the pop-up
menu and click Copy.
Figure 1-15
Copy option from pop-up
• To paste, place the cursor where you want the text to be, then right-click
the mouse to display the pop-up menu and click Paste.

CEM within Wireless Network Management System (W-NMS) 1

W-NMS related documents
Refer to the following documents for more information on W-NMS NSP:
• Wireless Network Management System Administrator Guide, NTP 411-
5221-305
• Wireless Network Management System Operator Guide, NTP 411-5221-
505
• Wireless Network Management System Global Overview, NTP 411-8111-
502
Open CEM browser from NSP Resource browser

Voice Core Networks MSC and HLR management is integrated into the W-
NMS Network Service Platform (NSP).
The operator can launch Element Manager from within the NSP Browser
window if the Network Elements (NEs) are displayed. This allows an
operator to view the physical and logical resources within the NE and to view
the OSI states and other attributes for each sub-component. The user can also
launch Performance Manager, Summary Report and Threshold Manager.
View the network element icons

To display the wireless MSC or HLR element icons, select
View>Filters>Wireless or click the Wireless checkbox located at the bottom
of the NSP Resource Browser window (see Figure 1-16).

Figure 1-16
Wireless filter group

Display NSP information

To display NSP information for an NE, click on the NE to highlight, then
click on “Details” located at the bottom of the Resource Browser window. See
Figure 1-17.
Procedure 1-1
Launch CEM GUI from different NEs without closing CEM GUI after the NE
being launched
Step Action
1 Open NSP GUI and choose a NE (for example: NE1). Right click on
that NE to launch CEM GUI from NSP GUI.
2 There is only NE1 and Security.
3 Choose another NE (for example: NE2). Right click on that NE to

launch CEM GUI from NSP.
4 There is NE1, NE2, and Security.
5 This procedure is complete.
Procedure 1-2
Launch CEM GUI from different NEs
Step Action
1 Open NSP GUI and choose a NE (for example: NE1). Right click on
that NE to launch CEM GUI from NSP GUI.
2 There is only NE1 and Security.
3 Close CEM GUI.
4 Choose another NE (for example: NE2). Right click on that NE to

launch CEM GUI from NSP.
5 There is only NE2, and Security.
6 This procedure is complete.
Note: The Data Server (DS) is supported only by the primary Main
Server in the W-NMS environment.

Figure 1-17
Details

Icons show alarm information

Each MSC or HLR NE node icon can show information regarding alarms. In
Figure Figure 1-18, the node icon located on the right side of the screen
displays the highest alarm reference color. In this example, it is red.
The number in the bubble is the number of the highest alarms. In this
example, it is 41 Critical alarms.
Figure 1-18
NSP Resource Browser pop-up menu
Open the Alarm Manager window

To show the Alarm Manager window and display the alarms, right-click on
the node icon and select Show alarms (see Figure 1-18).
In Figure 1-19, the Alarm Manager window shows alarms for the node
selected. You can filter the alarms by several means, including severity and
acknowledged.

Figure 1-19
Alarms Manager window
Open the Element Manager window

Right-click on a node in the NSP Resource Browser to display the pop-up
menu (see Figure 1-18). From this menu, you can open the Element Manager,
Performance Manager, Summary Report, or Threshold Manager for the
selected node. Select CEM > Open to open the Element Manager just as it is
launched from the desktop.
Open the Performance Manager window

To open the Performance Manager from the NSP Resource Browser, right-
click on the node and select CEM > Performance Manager (see Figure 1-
18).

In Figure 1-20, the Performance Manager screen is displayed.
Figure 1-20
Performance Manager window
Open the Summary Report Window

To open the Summary Report from the NSP Resource Browser, highlight on
the node and select CEM > Summary Report. See Figure 1-18.
Open the Threshold Manager

To open the Threshold Manager from the NSP Resource Browser, right-click
on and node and select CEM > Threshold Manager. See Figure 1-18.

Open the Configuration Manager

To open the Configuration Manager from the NSP Resource Browser, right-
click on and node and select CEM > Configuration Manager. See Figure 1-
18.
Launching of SAM21 EM from CEM GUI 1

In SN06, the SAM21 EM can be launched via the webstart. Thus, the SAM21
EM will be started via calling a web browser with appropriate web page
address. The server for this EM runs on the CMT server. The Java Web Start
must be installed in the client machine for this feature to work.
Proxy settings for the Internet browser must be disabled for SAM21 GUI
launching. The following proxy changes need to be made before launching the
HLR200 GUI:
1. Go to the Tools menu and select “Internet Options.”
2. Go to the Connections tab and press the “LAN Settings” button.
3. Make sure that in the Proxy server content panel area “Use a Proxy server
for your LAN (These settings will not apply to dial-up or VPN
connections.)” the check box is unchecked.
Launching of STORM EM from CEM GUI 1

The STORM EM is a web browser based tool. Thus this EM can be launched
similar to SAM21 EM. Unlike SAM21 EM, the server runs on the STORM
itself, thus you need to configure web server on CMT server for a proxy
server.
CEM security 1
Prior to GEM16, no login was required on the CEM Browser. In GEM16, a
security framework was introduced which required the user to log in using a
login id and a password.
Note: Refer to GSM / UMTS Voice Core Network OAM Administration,

Maintenance & Troubleshooting Guide, NTP 411-8111-937 for detailed
CEM security information and procedures.
The user’s credentials are authenticated by an LDAP Directory Server or a

DCE Security Server. The CEM Browser can only be accessed by a user after
a successful login. Once logged into the CEM Browser, if the user wants to
access one of the other nodes in the network by invoking the MAP, Telnet, or
FTP tool, a second login was always required for that specific node.

Login information such as the user ID and the password are sensitive
information that needs to be protected when being transported over the network.
There are five possible connections over which the login credentials are
transported:
1. Connection between the NSP desktop and the NDS Server.
Securing the connection between the NSP desktop and the NDS Server in
the W-NMS environment depends on the security mechanism supported
by NSP. Refer to the NSP documentation for further information
regarding security mechanisms supported in NSP.
2. Connection between the OMC-S browser and the SDM/FT.
The connection between the OMC-S browser and the SDM/FT is not
secured but the login user ID and password are encrypted when passed
between the OMC-S browser and the SDM-FT.
The Telnet and the FTP sessions from the OMC-S browser to the SDM/
FT are also not supported over secure connection.
3. Connection between the OMC-S browser and the OMC-S Server.
The connection between the OMC-S browser and the OMC-S Server is
also not secured but the login user ID and password are encrypted when
passed between the OMC-S browser and the OMC-S Server.
4. Connection between the SDM/FT or the OMC-S Server and the IDS
Server.
The IDS has a configuration option for enabling Secure Socket Layer
(SSL) communication. Setting this option provides a secure connection
between the IDS and an SSL enabled client running on the SDM/FT or
the OMC-S Server. This option does require a certificate from a
recognized Certificate Authority to be installed on IDS.
5. Connection between the SDM/FT and the MSC
The connection between the SDM/FT and MSC is over DS-512 private
network link. This link is internal and is not externally accessible.
LDAP and SSL supported

CEM security is compliant with Network Service Platform (NSP) Framework
3.2 (FW3.2) third party bundle. CEM security is designed for and tested on
NSP-FW3.2 sever. Any attempt to integrate the CEM security software with
LDAP/SSL other than the versions and/or vendors stated below are not
supported.

LDAP:
• Vendor: Sun (Formerly SunONE)
• Software: SunONE Directory Server (Formerly NDS)
• Version: 5.1
• Build Number: 2001.326.2401
SSL:
• Vendor: OpenSSH (www.openssl.org)
• Software: OpenSSL
• Version: 0.9.6.c
• Module in Apache package: mod_SSL 2.8.6-1.3.23
Note: The LDAP and SSL are required to be installed and configured
following the NSP-FW3.2 installation and configuration in order for the
CEM security to work properly.
Integration of CEM login with other network nodes

Automatic login is accessible when the user is logged into the CEM browser
and invokes the following tools under the Tools menu:
• MAP to log into the MSC or the HLR100.
• Telnet to log into the SDM/FT, the CEM Server.
• Telnet to log into any other node in the network with which the login
credentials can automatically be exchanged.
• FTP to access/put files on the SDM/FT, the CEM Server.
• FTP to access/put files on any other node in the network with which the
login credentials can automatically be exchanged.
Note: Due to the use of PuTTY and OpenSSH (which are freeware SSH
Clients) on the CEM Browser, the automatic login functionality is not
available for the SSH tool set.
The user is allowed to save their login credentials for a specific node on the
CEM System so that the next login attempt into that node can be performed
automatically by the CEM browser. The login credentials are actually saved
on the CEM Servers, which are added into the CEM System. It is therefore
necessary to enter the CEM Server as the validation server on the initial CEM
login window in order to facilitate the retrieval of the credentials from the
given Server.
When no login credentials are previously saved on the CEM System for that
node and for that user, a login dialog is provided to the user to manually enter

the login credentials. On the manual login screen, the user is given the option
to save the login credentials entered.
If the automatic login fails for any reason, the user will have to re-enter the
user ID and password when prompted by the server or re-attempt the
automatic login by terminating the current session and restarting a new
session.
User group access control

With User Group Access Control functionality, the CEM Administration is
capable of setting functional privileges on a per group basis. The user’s ability
to perform a given operation is restricted based on the user’s classification
defined in the LDAP Directory Server or the DCE Security Server.
The CEM administrator can configure the operational privileges on a per user
group basis for each of the nodes added into the CEM System. Each user
group is defined in the LDAP Directory Server or the DCE Security Server.
This functionality is only supported for the nodes where the corresponding
SDM/FT is in CEM Server configuration and the CEM Server is running the
GEM17 CEM Software.
Note: This is not supported for the nodes where the corresponding SDM/
FT is in standalone configuration.
Users can be classified as CMUser, FMUser, PMUser, CTUser, or an

Observer Only (any combination of these user types is allowed). If the user is
classified as a CMUser, FMUser, PMUser or CTUser, then the Observer
privileges are automatically granted to that user. If the user is classified as
Observer Only, then they are restricted to perform only observer functions.
Once the user classification is assigned in the user’s profile on the LDAP
Directory Server or the DCE Security Server, the user has the same
operational privileges on all of the DMS nodes in the Network.
For more information, refer to Chapter 8, “Administration management” of

this manual.
Transparent user preferences

Transparent User Preferences allow users to login from any CEM Client
workstation and still be able to operate with their specific GUI configuration
setup.
The user’s preferences are stored on the CEM Server. At login time, the User
Preferences for that specific user are retrieved from the CEM Server (entered
as the validation server on the login window) and applied to the user’s CEM
Browser. This functionality allows the user to login from any CEM Client
Workstation and still be able to operate with their specific configuration
setup.

For more information, refer to Chapter 2, “File menu” of this manual.
Automatic login capability for Telnet, FTP and MAP sessions

A new menu item under the Tools menu sets the automatic login on or off. If
the automatic login is set, then a login window is displayed to the user to enter
the login credentials.
Telnet, FTP and MAP all utilize TCP/IP protocol for accessing remote nodes.
The Users login credentials are transferred over the network in plain text. To
avoid this security problem, data must be encrypted before transmission.
For more information, refer to Chapter 7, “Tools” of this manual.
Secure Shell access between CEM browser and any SSH Server
Upon successful login, the user is able to select secure shell access under
tools menu.
For more information, refer to Chapter 7, “Tools” of this manual.
Security alarms
The OMC-S system generates security alarms to draw the immediate attention
of the administrator to a potential security problem or a suspicious activity. The
occurrence of following events triggers a security alarm to be generated:
• Maximum number of consecutive unsuccessful login attempts in a single
login session.
• Successful and unsuccessful attempts to gain permissions or assume the
identity of another user.
The security alarm generated by the OMC-S contains following information:

• Date
• Time
• Service or program used for access (such as login, rlogin, etc.)
• Success/Failure
• Login ID
• Device
• Access attempt counter
• Source and Destination address

CEM restrictions and limitations 1

Take note of some of the restrictions and limitations:
1. There is a limit on the number of nodes that can be managed by the
Element Manager.
2. Histograms are not applicable to user defined filters.
3. Automatic login on nodes other than the MSC, HLR100, SDM/FT and the
CEM Server could not always be possible due to inability to exchange the
login credentials with the remote host after establishing the connection.
4. Automatic login may not be possible if standalone SDM/FT is used as the
validation server and the login credentials are not previously saved locally
on the CEM Browser machine.
5. Automatic login is not possible with PuTTY and OpenSSH applications
due to the inability to programmatically pass login credentials to these
applications.
6. Configuration of Group Access Control is supported only for the Network
Elements that are associated with SDM/FTs that are configured to be in
server mode and are connected to GEM17 CEM Servers. These CEM
Servers have to be added into the current CEM Browser prior to being to
set up the Group Access privileges.
7. User preferences can only be saved on GEM17 CEM Servers.
8. User preferences can only be retrieved from the validation server if the it
is a GEM17 CEM Server and if the current user’s preferences are
previously saved on it.
9. Transparent User preferences is not supported when the CEM browser is
installed with no security.
10. Since OpenSSH is open source code and it is owned by the OpenBSD
project. Nortel will not fix any bugs that are identified in or associated
with this software. Nortel only provides technical assistance in terms of
troubleshooting. If problems are identified in the OpenSSH software, the
problem will be reported to the OpenSSH organization for possible
resolution.
11. Since PuTTY is open source code and it is owned by the PuTTY project.
Nortel will not fix any bugs that are identified in or associated with this
software. Nortel only provides technical assistance in terms of
troubleshooting. If problems are identified in the PuTTY software, the
problem will be reported to the PuTTY organization for possible
resolution.
12. Although Nortel is deploying PuTTY and OpenSSH as part of the CEM
System, it is the responsibility of the customer to manage the
authentication methods and credentials used in conjunction with these
applications.

13. The CEM server cannot be configured as the DCE master server as the
same time. This configuration will cause the DCE cell unstable and some
of the DCE’s functionality will not work correctly
14. The SDM cannot be configured as the validation server while the security
in ‘ldap.config’ is set to ‘DCE’ mode. Due to issues with the DCE in the
AIX platform, this configuration may causing the EMAdapter to core
dump occasionally and unexpectedly.
15. The OpenSSH server only differentiates the passkey base on the protocol
(i.e., SSH1 and SSH2) at the connection time. The OpenSSH server does
not distinguish the connection request based on key type (i.e., rsa1, rsa2,
or dsa). Since rsa1 belongs to the SSH1 protocol family and both rsa2 and
dsa belongs to the SSH2 protocol family, the user will get a login error if
they attempt to use the rsa1 key and declare it as either rsa2 or dsa.
However, the user will not get the same error message if they declare rsa2
as dsa or vice versa because, as stated earlier, both rsa2 and dsa are in the
same protocol family.
16. When the SSH organization first introduced SSH2 protocol, dsa was the
only key type to use for this new protocol (SSH2). The rsa2 key type has a
higher level of encryption compared to dsa. Since some older systems
already used the dsa key type, the SSH organization supports both rsa2
and dsa key types in SSH2 protocol.
17. Generic table editing for Media Gateway is not supported.
18. The R4 wizards do not support the HLR.
19. There is no table-change notification in the Media Gateway wizards for
Media Gateway tables.
20. There is a limit on how many Passports are supported on one MDM (there
is a limit of 256 VSP cards in the GWINV table).
21. When an network element’s IP address is changed, often CEM does not
get notified of or detect the change without the applicable MDM FMDR
process or the CEM Device Manager or Object Manager being restarted.
22. If a Passport has been down for more than two hours before the CEM GUI
starts, then the historical OM data of this Passport is stored in the archive
server and is not available for query until the Passport re-connects with
MDP.
23. The CEM online help is not available to users for SIG, GGSN and SGSN
network elements.
24. The alarm state of the MTP resources will be set to ‘unknown’ because
USP has MTP alarms pegged against card resources.
25. Probable cause of the USP alarms are not available to CEM. Thus, most
alarm’s probable cause are set to ’probableCauseUnknown’. The

exception is a software error log which would have ’softwareError’ as the

probable cause.
26. Acknowledgement and unacknowledgement of alarms and logs are not
propagated to the USP. It is self contained in the CEM.
27. Manual clear of the manually clearable USP alarms is not propagated to
the USP. It is self contained in the CEM.
28. Manual clear of non-manually clearable USP alarms is not allowed.
29. Only certain USP tables can provide table change notification (TCN) to
CEM in USP8.1 or above; even more limited in USP8.0. CEM will
perform periodic audit to synchronize the discovered resources that
cannot provide TCNs.
30. A USP name change will result in rediscovery of the device and its
alarms.
31. By using the configCEMS tool to update the managed USPs will result in
the removal of the previously managed USPs from CEM and CEM will
start afresh managing the USPs specified in the update.
32. Hard drives are not visible on the USP shelf in CEM GUI due to USP
interface not able to provide the info.
33. USP alarms on ‘HardDrive1’ and ‘HardDrive2’ are raised against slot 12
and 15 on shelf 0, respectively; different from the USP side because slot
13 and 16 on shelf 0 are not provisioned.
34. Only maximum of 6 concurrent telnet/CLI sessions per RTC can be
opened on the USP. If CEM cannot connect into the USP based device
and if the NE name is previously known or not visible until the connection
is established, the NE will be shown as in ‘unknown state’.
35. Maintenance action on the USP can only be performed when the targeted
telnet session is opened and passed user ID/password validation.
36. Resources related to OM groups have no associated maintenance actions.
37. USP GUI needs to be installed on the PC in order to support connection to
USP based devices; Java GUI for USP10.0.
38. Java GUI will have to be provisioned with the USP IP addresses prior to
requesting in-context launch; else the Java GUI could not perform in-
context launch.
39. Upgrade can only be detected when the USP is upgrading from a USP8.0
release.
40. While the USP is in upgrade mode from USP7, CEM will not be able to
manage the device until it is finished.
41. Performance Management Summary Report is not supported for USP.

42. The dataCollector requires a valid FTP username and password on the
USP; without these, OM transfer will fail.
43. There is a 5-minute delay introduced by the dataCollector from the time
the USP writes an OM report to the time the dataCollector transfers the
report to the archive, in order to ensure the USP report is completely
written before FTP occurs. This assumes that the clocks are in-sync on the
CEM Server and USP; if they are not, this delay could decrease/increase.

2-1
File menu 2
The File menu allows you to open, disconnect, and reconnect Element Manager
windows. It also allows you to export or print alarm data. The File menu includes
the following commands:
• Display a New Window
• Layout management
• Display a New Layout
• Display the Info Log
• Set up the network display
• Add an element or server to the network display
• Remove an element from the network display
• Relocate an element from one network path to another
• Change the location of an element
• Disconnect/Reconnect an element
• Close windows
• Set Preferences
• Export alarm data
• Print alarm data
• Exit Element Manager
Note: On the Unix platform, after you exit the Element Manager
application, wait 15 seconds before running it again. This allows x-
resources to be released properly.

2-2 File menu
Figure 2-1
File menu
Display a new window 2

The New Window option in the File menu (Figure 2-1) allows you to display
up to 5 windows for the application. By having multiple windows, you can
view different components of the managed network’s hierarchy at the same
time. Each window and its display can be manipulated independently.
Layout management 2
Layout management enables users to create custom layouts which contain
Network Elements (NEs) specific to their interest. It also allows users to
create different layouts based on type of NEs, region where NEs are located,
or by any reasonable choice. Apart from the configuration of NEs, the
backdrop images if set for any level of the CEM browser, position of the
nodes, and other user settings are also saved as part of the layout. Layout
management allows users to have multiple configurations, or layouts, of NEs.
The layouts can be stored on the user’s local machine, PC or Sun workstation,
or a CEM Server so that they can be shared with other users.
Each layout can contain NEs which are in stand alone mode as well as those
being managed by a Sun Server. By default a layout is empty, NEs can then be
added to the layout. Existing NEs in a layout can be disconnected or excluded

File menu 2-3
from CEM. If a Sun Server is added to the CEM, all of the NEs managed by
the server are automatically added to the layout and the users can remove
specific NEs which are not of their interest.
Note: The CEM browser by default will display the layout last visited by
the user.
The layout menu options are:

• New Layout
• Open Layout
• Show Layout
• Save Layout
• Exclude Element(s)
Node aggregation is the ability to merge, or group, components from multiple

network elements and have them appear as components of a single network
element or a region. For example, a USP can be displayed as a component
under an MSC or HLR (network element), or multiple passports can be
aggregated into a single wireless gateway (region).
Layout Management only supports grouping NEs already added to the CEM
browser in the user defined region. The NEs can be configured into a
particular region at the time of installing the slices pertaining to the NEs on
the CEM server.
Note: Node aggregation under a single network element, or a slice, is

predefined and cannot be changed by layout management. For example,
an MSC/HLR with USP as a subcomponent would fall in this category,
whereas managing an HLR Complex region which consists of HLR200,
Data Server, PP8600, and SLR nodes can be achieved by layout
management.
New layout
This File menu option creates a new layout and clears the current layout being
displayed in the CEM browser by removing all the NEs, CEM servers, their
corresponding alarms and histograms.
Open layout
This File menu option displays a file browser window (see Figure 2-2) from
which the user can select from a list of layouts previously saved on either a
local machine or a remote CEM server.

2-4 File menu
Figure 2-2
Open layout window
Show layout
This File menu option displays the Layout Management window for the
current layout displayed in CEM browser. The Layout Management window
consists of all the NEs, their current status and their paths displayed in a
tabular format.
Save layout
This File menu option displays a file browser window prompting the user to
enter a name for the layout and select a location to save the layout file.

File menu 2-5
Layout management window

A Layout Management window (Figure 2-3) is provided which lists all of the
NEs and servers connected to the CEM in a tabular format and the user can
select the NEs to be included or excluded from the CEM browser. The Layout
Management window by default will display the layout last visited by the user
which shows NEs and servers included/excluded in the layout. The CEM
browser’s display will reflect what is shown in the Layout Management
window. In other words, it will only display the NEs and servers that are
included in the layout.
Note: At least one CEM server has to present in the layout in order to
save the layout file remotely. Layouts will have to be stored locally on PC
or Sun Workstation running the CEM browser in case of networks
consisting of only Stand Alone Mediation Devices (SDM/FTs or MDMs).
Figure 2-3
Layout management window
The Layout Management window consists of the following components:

• NE List - shows all the NEs, IP nodes, servers, region nodes included/
excluded in the layout and their alarm status.

2-6 File menu
• NE Information Panel - consists of two tabs:

— General - displays information about the selected NEs in the included
NEs list.
— Annotation - displays a text area where the user can enter a note
regarding the NE which gets saved on the Sun Server, or mediation
device in case of a Stand Alone configuration. This note is broadcast
to all of the CEM browsers connected and is displayed in the
Annotation tab for the NE.
Note: This tab is only applicable to NE nodes and is not displayed for
nodes representing Regions, IP nodes, or servers.
The NE List is displayed in a tabular tree format which consist of the following
columns:
• Network Element - network element along with the path to the network
element displayed as a tree structure.
• Status - current alarm status or excluded state of an NE or Server.
• Region - path of the NE or Server in the CEM browser.
The titles of the Layout Management window and the CEM browser are set to
the name of the layout saved by the user.
The File Menu consists of the following menu items:

• New Layout - creates a new layout, clears the current layout by removing
all the nodes from layout management window and configuration
management area of CEM Browser. It also clears all the alarms and
histograms from the fault management area.
• Open Layout - displays a file browser dialog for the user to select from a
list of previously saved layout files on local machine or private and shared
folders of a remote CEM server.
• Save Layout - displays a file browser dialog prompting the user to enter a
name for the layout and select a location where the layout has to be saved.
• Merge Layout - displays a file browser dialog for the user to pick a layout
file to be merged with the current layout, NEs of both the layouts will be
displayed in the layout management window and configuration
management area. If there are duplicate entries, the NEs from the current
layout will be preserved and the ones from the new layout will be ignored.
• Add Element - displays an “Add Switch” dialog, wherein the user will be
prompted to enter the NE/Server IP address and the path/region the NE/
Server has to be placed. This is similar to “Add Element” in the main
window.
• Relocate Element(s) -displays a dialog that prompts the user to enter the
new Region/Path of the NE or server.

File menu 2-7
• Disconnect Element(s) - drops the connection to the NE/Server selected.

• Reconnect Element(s) - reconnects to the disconnected NE/Server.
• Exclude Element(s) - removes the selected NE(s) from the main window
of the CEM browser including its corresponding alarms and histograms
but is still kept in the layout management window with status marked as
excluded, so that users can later include the NE if they want to.
• - adds the selected excluded NE(s) back to the CEM
Include Element(s)
browser and connects to them to get the current status, alarms and
histograms.
• Remove Element(s) -
removes the selected NE/Server from the Layout
Management window and the main window of the CEM browser.
• Close - closes the Layout Management window.
Save Layout
Layout files can be saved in public and private directories on the remote Sun
Server or on the local machine, PC or Sun workstation, on which the CEM
browser is running. If there are existing layouts, the CEM browser by default
will display the last visited layout. If for some reason the layout file is not
accessible, an error message is displayed to notify the user of the reason.
Merge Layout
The existing layout being displayed in the Layout Management window can
be merged with a layout. The layout can be selected from the local PC or Sun
workstation running the CEM browser or private/shared directories on a
particular CEM Server.
Region pop-up menu

The region pop-up menu (Figure 2-4) is only applicable to region nodes
displayed in the Layout Management window. The pop-up menu for a region
node supports the following menu options:
• Find - displays the selected region node in the configuration management
panel of the CEM browser.
• Info - displays the Info window (Figure 2-5) for the selected region node.
• Relocate - relocates a selected region to a given region/path.
• Disconnect - disconnects the selected region and all the NEs and servers
located in it. This menu option is only available if the selected region is
not already disconnected.
• Reconnect - reconnects the disconnected region and all the NEs and
servers in it. This menu option is only available if the selected region is
already disconnected.
• Remove - removes the region and all the NEs and servers in the selected
region.

2-8 File menu
Figure 2-4
Region pop-up menu
Figure 2-5
Info window
Server pop-up menu

The server pop-up menu (Figure 2-6) is only applicable to the server nodes
displayed in the Layout Management window. The pop-up menu for a server
node supports the following menu options:
• Find - displays the selected server node in the configuration management
• Info - displays the Info window (Figure 2-5) for the selected server node.
• Relocate - relocates and selected server to a given region/path.
• Exclude -
excludes the selected server from the configuration
management area of the CEM browser, this sets the state of the server

File menu 2-9
node to excluded in the Layout Management window, this menu item is

only available if the selected server is not already excluded.
• Include - adds the selected server to the configuration management area of
the CEM browser, and sets the state of the server node to its alarm status
in the Layout Management window.
• Disconnect - disconnects the selected server node and removes all the
NEs managed by the server from the CEM browser, this menu item is
only available if the selected server is not already disconnected.
• Reconnect - reconnects the selected server, this menu item is only
available if the selected server is already disconnected.
• Remove - removes the selected server node from the CEM browser.
Figure 2-6
Server pop-up menu
IP node / slice pop-up menu

The IP node / slice pop-up menu (Figure 2-7) is only applicable to the IP node
or slice node displayed in the Layout Management Window. The pop-up menu
for an IP node or slice supports the following menu items:
• Find - displays the selected IP (slice) node in the configuration
management panel of the CEM browser.
• Info- displays the Info window (Figure 2-5) for the selected IP (slice)
node.
• Relocate - relocates and selected IP (slice) node to a given region/path.
• Exclude - excludes the selected IP (slice) node from the configuration
management area of the CEM browser, this sets the state of the node
excluded in the Layout Management Window, this menu item is only
available if the selected Server is not already excluded.

2-10 File menu
• Include - adds the selected IP (slice) node to the configuration

management area of the CEM browser, and sets the state of the node to its
alarm status in the Layout Management window.
• Disconnect - disconnects the selected IP (slice) node and removes all the
NEs managed by the node from the CEM browser, this menu item is only
available if the selected node is not already disconnected.
• Reconnect - reconnects the selected IP (slice) node, this menu item is only
available if the selected node is already disconnected.
Figure 2-7
IP Node / Slice pop-up menu
Network element pop-up menu

The network element pop-up menu (Figure 2-8) is only applicable to an NE
node displayed in the Layout Management window. The pop-up menu for an
NE node supports the following menu options:
• Find - displays the selected NE node in the Configuration Management
• Info - displays the Info window (Figure 2-5) for the selected NE node.
Figure 2-8
Network Element pop-up menu
Layout management restrictions and limitations

• The layout files are not synchronized across the OMC-S servers.

File menu 2-11
• Layout files are stored on a local machine, PC or Sun Workstation, in case

of networks consisting of only Stand Alone SDM/FTs.
• Layout Management is not supported by ASCII interface.
• Layout Management does not support isolation of components under
aggregated nodes like USP or individual Passports into a layout, they can
only be relocated, disconnected, or excluded as a group.
Set up the network display 2

When setting up the network display, you must first have an idea of how the
network hierarchy is structured. It is helpful to have a list of the different
switch names, to be monitored from the Core Element Manager (CEM). Once
you have a list of switches, map out how you want to organize the network.
Note: This application uses TCP/IP connections between PCs/SUNs

running the CEM software and SDMs associated with the switches that
each PC/SUN is monitoring. An Element Manager can be connected to up
to 20 switches and a switch can be accessed by only 10 element managers
at the same time.
Figure 2-9 shows an example of a network layout established for the

Southwestern area of the United States. The Southwestern network contains
switches located in the states of Texas, Oklahoma, and Louisiana.
• Texas is divided into two regions: North and South. Each region has two
DMS MSC switches. Texas South has an HLR switch.
• Oklahoma has two DMS MSC switches.
• Louisiana has two DMS MSC switches and an HLR switch.

2-12 File menu
Figure 2-9
Example MSC/HLR network layout

File menu 2-13
Add an element 2
The Add Element option allows you to identify either an element or server to
be monitored. Before the Element Manager can monitor an element, you must
identify the SDM and MSC/HLR SDM element, or server, and you must
specify where you want to position the element in the network hierarchy. The
Element Manager identifies the hierarchy of the element based on the path to
element that you enter in the Add Element window. You may also optionally
enter any type of notes you would like to have associated with this element.
The notes will be visible in the Info Window (see Configuration menu) for
that element.
To add a MSC/HLR element see Procedure 2-1.
Procedure 2-1
Add a MSC/HLR element to the network
1 From the File menu, select the Add Element option and select MSC/HLR to add an element
for monitoring. See Figure 2-10.
Figure 2-10
MSC/HLR element
2 The Add Switch window appears (see Figure 2-11).

Figure 2-11
Add element
3 In the SDM IP Address field, enter the telco side IP address or alias of the SDM connected
to the element. For example, 47.186.79.9. If a hostname or alias has been created in the
hosts file (WindowsNT: c:\winnt\system32\drivers\etc\hosts: Sun: \etc\hosts) you can
substitute the hostname or alias. The IP address cannot appear on more than one line. In the

2-14 File menu
hosts file (Figure 2-12), either the SDM hostname or the switch alias will reference the SDM
IP address, and can be used as the element label.
Figure 2-12
Example hosts files (WindowsNT)
# Copyright (c) 1993-1995 Microsoft Corp.

#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows NT.
# This file contains the mappings of IP addresses to host names. Each entry
# should be kept on an individual line. The IP address should be placed in the
# first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a ‘ # ‘ symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
# SDM IP SDM hostname Switch alias
47.104.89.173 urc2d07a MSCA # Southwest/Texas/North

47.104.88.34 urc2d081 MSCB # comment
47.104.88.32 urc2d021 MSCE # comment
......
=========================================================
4 In the Path to Node field, enter the path name of the element in the network layout. For
example, in the path to MSCa is Southwest/Texas/North
5 Click OK.
6 Repeat this procedure for each element.

File menu 2-15
A Server can also be added for monitoring. To add a Server, see

Procedure 2-2.
Procedure 2-2
Add a Server to the network
1 From the File menu, select the Add Element option and select Server to add a Server for
monitoring. See Figure 2-13.
Figure 2-13
Select Server
2 The Add Server window appears (see Figure 2-14).

Figure 2-14
Add Server
3 In the Server IP Address field, enter the IP address or alias of the Server connected to the
element. For example, 47.186.79.9. If a hostname or alias has been created in the hosts file
(WindowsNT: c:\winnt\system32\drivers\etc\hosts: Sun: \etc\hosts) you can substitute the
hostname or alias. The IP address cannot appear on more than one line.

2-16 File menu
Relocate an element 2
This feature allows you to change the network path of an element. To launch
this application, select Relocate Element under the File menu (Figure 2-1).
This opens the Move Element window (Figure 2-15) where you enter the new
element path.
Figure 2-15
Move Node window
Note: The region/path of a CEM Server managed element can also be set
while configuring the corresponding slice on the CEM Server. The node
corresponding to the slice will appear in this region/path on the CEM
browser.
However, if the node is relocated by a user manually from the CEM

browser using the "Relocate" option on the node, then the path/region set
on the CEM Server while reconfiguring a slice is ignored and the path/
region set on the browser will take precedence. This is only for the CEM
browser on which the slice node is manually relocated. Other CEM
browsers in which the slice node is not relocated manually will update to
the new region/path of the slice set while reconfiguring the slice.
Disconnect/reconnect an element 2
This feature is a type of flow control mechanism provided by the Element
Manager. You can disconnect a switch from being monitored to reduce
congestion, and thereafter none of the OA&M information for that switch will
be processed by the Element Manager. You can also reconnect to the switch.
If no elements have been disconnected, the reconnect element option is not
available. Once an element has been disconnected, the reconnect option
becomes available. To perform either operation, select the element and then
select either Disconnect Element(s) or Reconnect Element(s). Once selected a
confirmation window displays (Figure 2-16 and Figure 2-17).
Elements can also be disconnected or reconnected via a pop-up menu available

in the Configuration Management window (see “Configuration Management
Window” on page 3-15) with the following menu items:
• Disconnect: The disconnect menu item can be used to disconnect a
managed slice from the CEM server. If this menu item is invoked from a

File menu 2-17
region icon, all slices below the region will be disconnected. If this menu
item is invoked from the slice icon, only that slice will be disconnected.
As there can be many slices under a region, the disconnect menu item will
always be enabled on a region icon. The disconnect menu item will be
disabled on a slice icon if that slice is already disconnected.
• Reconnect: The reconnect menu item can be used to reconnect a managed
slice to the CEM server. If this menu item is invoked from a region icon,
all slices below the region will be reconnected. If this menu item is
invoked from the slice icon, only that slice will be reconnected. As there
can be many slices under a region, the reconnect menu item will always
be enabled on a region icon. The reconnect menu item will be disabled on
a slice icon if that slice is already connected.
Figure 2-16
Disconnect confirmation
Figure 2-17
Reconnect confirmation
Note: You can only disconnect the element in the network display. The
physical elements within the element cannot be reconfigured by the
Element Manager.
Remove an element 2
The Remove Element option removes the element from monitoring by
Element Manager display.
To remove an element or server from the network display, use Procedure 2-3.

2-18 File menu
Procedure 2-3
Remove an element from the network
1 In the Configuration Management window, highlight the element to be removed.
2 From the File menu, select the Remove Element option. The Confirm window appears (see
Figure 2-18).
Figure 2-18
Remove Node window
3 Select Yes to confirm.

4 Repeat this procedure for each element.
Rename or change the location of an element 2

To rename or change the location of an element, you must first remove the
existing element (Procedure 2-3) and then add the new element (Procedure 2-
1).
Note: You can only change the location of the elements in the network
display. The physical elements within the element cannot be reconfigured
by the element manager.
Exclude element(s) 2
This File menu option excludes the selected NE(s) and CEM server(s) from
the CEM browser. The excluded NEs and CEM servers are still displayed in
the Layout Management window.
Find NE 2
This File menu option opens a Find NE window (Figure 2-19) displaying a list
of all the connected Network Elements along with their Type, Region, Alarm
State, NE Release, Slice, Server IP and Mediation Device IP. The Find NE
window can also be accessed from the pop-up menu on the CM panel when
the user right clicks on a selected NE.

File menu 2-19
Figure 2-19
Find NE window
In the Find NE window, the user can select a specific NE and right click on it
to display a pop-up menu (Figure 2-20). This pop-up menu has the following
options:
• Locate NE - locates specific NE on the CM panel.
• Performance Manager - shortcut to open the Performance Manager.
• Threshold Manager - shortcut to open the Threshold Manager.
• Telnet - shortcut to open a Telnet session.
• Map - shortcut to open a MAP session.
Note: These same menu options are available from the File menu on the
Find NE window.

2-20 File menu
Figure 2-20
Find NE window pop-up menu
When the user selects a particular NE in the table, right clicks and selects the
pop-up menu option “Locate NE”. That specific NE is located on the CM
panel of the main Element Manager window.
There is also a filtering of NE option available to the user, similar to the

expression matcher that is used in the info log, debug log and call trace
windows. The user can enter a match criteria and the NE list is filtered based
on the match. The expression matcher supports and, or, not operations as well
as parenthesis.
Display the Info log 2

To display a history of the OMC-S Element Manager application session,
select the Info Log option from the File menu. The Info Log window shows
the status in the system and any errors (Figure 2-21).

File menu 2-21
Figure 2-21
Info log window
Click Clear to clear the current status log. Click Close to close the Info Log
window. Click Save to save the text in the Info Log window to a file. A Save
dialog box opens to help you choose a path and name a file to receive the log
data.
To filter the data in the Info Log window, you can enter a search string and click
Match. Only the logs matching the criteria specified in the search string are
displayed. The search string can include both specific identifiers and Boolean
logic (and, or, and not). For example:
• all - shows all the logs
• localhost - shows only the logs which have localhost in them
• sdmip_ip - shows all the up messages for a specific sdmip
• sdm_ip and up - shows all the up messages for sdmip
• Not sdm_ip - shows all the messages except for a specific sdmip
Note: sdmip1 or sdmip2 - shows all the messages for sdmip1 or sdmip2
Replace sdm_ip in the above examples by the IP address or host name of
the SDM.

2-22 File menu
Transparent user preferences 2

Transparent User Preferences means that the user is able to access their
configuration preferences on any Client Workstation used to log into the
CEM System. This functionality is facilitated by options provided on the
Preference window. This window can be invoked by selecting the Preferences
menu item under the File Menu on the main menu bar.
Note: User preferences can only be saved on CEM Servers, or W-NMS

Main Servers, that are running a GEM17 or later version of CEM
Software.
In the Preference window (Figure 2-22), the user preferences are divided into
four sets of preferences: General, FM Panel, CM Panel and Tools preferences.
Figure 2-22
Preferences General tab option
On the General Tab (Figure 2-22), transparent user preferences can be modified
by the following check box:
• Save Preferences On All Servers - selecting this option indicates that the
user wishes to store their preference information on all of the CEM
Servers currently added in the CEM Browser and on the validation server

File menu 2-23
indicated during the current CEM Browser login. When this option is
selected, the Save Preferences On Validation Server option is
automatically selected as well. When this option is deselected and the
Save Preferences On Validation Server is selected, then the user
preferences are stored locally on the validation server only.
• Save Preferences On Validation Server - when this option is selected, the
user’s preferences will be stored locally only and will only be available on
that particular workstation. When this option is deselected, the Save
Preferences On All Servers option is automatically deselected.
When upgrading from GEM17, if the user had selected the option Save
Preferences On All Servers in GEM17, the default setting in the current release
would automatically be as follows:
• Save Preferences On Validation Server selected.
• Save Preferences On All Servers selected.
When upgrading from GEM17, if the user had not selected the option Save
Preferences On All Servers in GEM17, the default setting in the current release
would be as follows:
• Save Preferences On All Servers deselected.
• Save Preferences On Validation Server deselected.
On the Tools tab (Figure 2-23), transparent user preferences can be modified
by the following four check boxes:
• Save Auto Login State - Check marking this box indicates that the current
setting of the AutoLogin option under the Tools menu need to be saved as
the user preference.
• Save Telnet Login Credentials - Check marking this box indicates that the
login credentials entered during the Telnet Session initiated during the
current CEM Browser session should be saved permanently (until they are
modified the next time) in the CEM System. The saved telnet login
credentials can be retrieved in the next CEM Browser session.
• Save FTP Login Credentials - Check marking this box indicates that the
login credentials entered during the FTP Session initiated during the
current CEM Browser session should be saved permanently (until they are
modified the next time) in the CEM System. The saved ftp login
credentials can be retrieved in the next CEM Browser session.
• Save MAP Login Credentials - Check marking this box indicates that the
login credentials entered during the MAP Session initiated during the
current CEM Browser session should be saved permanently in the CEM
System. The saved map login credentials can be retrieved in the next
CEM Browser session.

2-24 File menu
Figure 2-23
User preferences for functionality under the Tools menu
Transparent user preferences for W-NMS users

A preference option labelled Save Preferences on Main Server is provided on
the CEM Preferences window (see Figure 2-24) for the user to have their
preferences stored locally and remotely on the W-NMS Main server based on
the user ID entered in the W-NMS login window and to retrieve the remotely
stored preferences when CEM is launched. If the user does not choose this
option, then the preferences are stored locally only. In this case, when the
CEM is launched again from the W-NMS GUI, locally stored preferences are
retrieved.
It is necessary for the user to choose the Save Preference On Main Server
option in order to achieve the capability of retrieving their preferences when
using any other W-NMS client workstation.
Note: The Save Preferences On All Servers option is not applicable in the
W-NMS environment and therefore not available on the CEM Preferences
window.

File menu 2-25
Figure 2-24
CEM preferences window in W-NMS environment
Export alarm data 2

There are two methods of exporting alarm data:
• Export alarm data by format - the intended destination of the data is the
workstation currently running the Element Manager
• Export alarm data by date - the intended destination of the data is the
SDM where the alarm data is being generated.
Export alarm by format

The Export submenu on the File menu (Figure 2-25) allows you to specify the
portion of the alarm database you want to send, the format you want to send it
in, and a file name and path for the alarm data. The Export menu without
options is used to set the export path.

2-26 File menu
Figure 2-25
Export alarm menu
Use to set the export file name and path every time you choose to export
alarm data by format.

File menu 2-27
Procedure 2-4
Set Export Path
1 If the directory where you want to store the alarm data file does not exist, create it before
beginning the Export command. Make a note of the directory name and path.
2 Select the File>Export. Select from the options displayed to export the portion of the data
you want in the format you want.
3 The Export Alarm window appears (Figure 2-26). In the Export Alarm window, select the
path name (including the drive name) where you want the export data file to be created and
click OK. For example c:\data.
Figure 2-26
Export alarm window
The default filename is type-mm-dd-hh-mm, where type can be alarms,

histogram or compList, and mm-dd-hh-mm is the exporting time in month-
day-hour-minute format.
You can change the name of the alarm data file. Do not include an extension
in the filename. The export function automatically appends the .txt extension
to the filename. Click Save.
If Excel Format is not checked, filename.txt contains alarm data in text

format. If Excel format is checked, filename.txt contains alarm data in tab-
separated format. You can open it with either Microsoft Excel or Microsoft
Access to generate a user-defined report.

2-28 File menu
The output of Excel Format includes an additional file, filename.txt.info,

which includes the information regarding the filter criteria applied on the
exported alarm data.
The Export submenu includes the following options:

• Excel Format allows you to choose the format for the data. You can send
data in just normal text or send data in both normal text and excel format.
Note: When Excel Format is selected, a check mark toggles and the File
menu closes. Open the Export command again to select Alarm Data
(Headers) or Alarm Data (Full).
• Alarm Data (Headers) sends just the header information of the alarms
displayed in the FM window (according to the filtering criteria).
• Alarm Data (Full) sends the full text (Figure 2-27) of the alarms displayed
in the FM window (according to the filtering criteria).
Note: Every full alarm is queried from the SDM, so it may take a while to
finish.
Figure 2-27
Sample alarm data file in full format
Alarm For <MSCI/LKSET_Container/ANSIIN/ANSIIN-0>:

=====================================================
NotifID = 175898; AlarmType = communicationsAlarm;
Severity = minor; ProbCause = c7LinkFailure;
MSCI * CCS103 JAN18 13:33:13 9560 FLT Persistent Act Timeout

Link =ANSIIN 0
Resource = LIU7 303
OverWritten by:
NotifID = 175981;AlarmType = communicationsAlarm
Severity = minor;ProbCause = c7LinkFailure;
MSCI*CCS103 JAN18 13:41:43 9649 FLT Persistent Act Timeout

Link = ANSIIN 0
• Histogram (Text) sends the histogram, in text format, (Figure 2-28)

currently displayed on the FM (according to the filtering criteria).
• Component List (Text) sends a list of components (Figure 2-29) currently
displayed in the CM window, along with their alarm summary and alarm
status, to the user-specified file (the export path).

File menu 2-29
Figure 2-28
Sample alarm data file in histogram (text) format

2-30 File menu
Figure 2-29
Sample alarm data file in component list (text) format
Component List at Thu Mar 25 11:39:20 CST 1999
Parent Node: root
Name State Alarm Sub Alarms
=========================================================================
=====
Export alarm data by date

The Alarm Data by Date option allows you to export the alarms by date.
The SDM generates a text file which allows you to import the data into an
Excel spreadsheet. Figure 2-30 provides an example of export by date.
Figure 2-30
Export Alarm Database by Date

File menu 2-31
An operator can login to Tools->FTP as user ID “omcadmin” or “guest” to

retrieve the export file.

2-32 File menu

3-1
Configuration management 3
The Element Manager displays complete information for each target network
element and its subordinate elements. The W-NMS NSP GUI displays
information about the entire network.
The Configuration Management function allows you to manage network

elements (MSC and HLR) within a voice core network. The Configuration
Management identifies the configuration and status of the network when it is
initialized. The network elements are arranged according to the network
hierarchy.
The configuration display is updated automatically by the Configuration

Manager maintaining consistency between the Element Manager display and
its managed objects.
The Configuration Manager includes the following features:

• Physical, Logical, icon, or List views from the Element Manager
• Pin and Unpin nodes
• nodes sorted by name or severity
• find carriers and linksets
• saving and retrieving of notes for nodes
• integration with performance management
• threshold management information in the info window for PM resources
(last Value: Critical, Major, Minor)
• Performance Management information in the info window for PM
resources (pmCurrentData)
• Print support for CM window
Each feature will be covered later in this chapter.

3-2 Configuration management
Configuration management restrictions and limitations 3

• The Configuration Management view is scaled to fit on a page when
printed.
• Pinned nodes cannot be explored.
• Configuration management of USP is not supported in CEM GUI‘s
Configuration Management windows. USP GUI is the tool for
provisioning.
Configuration Manager toolbar 3

The toolbar (Figure 3-1) contains buttons that allow you to view the levels of
a network either in a textual or graphical format. Buttons that display
information about network elements or manually clear an alarm are also
available. See Table 3-1 for icon descriptions.

Figure 3-1
Configuration manager tool bar
Table 3-1
Configuration manager tool bar icon descriptions
Icon Name Description
Drill up to This button allows you to view the parent level of

parent element you select. This button is disabled when
there are no parent elements.
Drill down to This button allows you to show the children within
children the element you select. If there are no children
within the element, this button is disabled.
Node This button displays an information box for the

Information element you select. The information box contains
items such as attribute names and values. This
option is disabled if no node is selected.
Physical view This button displays the physical view for the current
level.
Logical view Displays the logical view for the current level.
Graphics This button causes the Configuration Management

view window to display the network elements as icons.
List view This button causes the Configuration Management

window to list the network elements in a textual
tabular format.
—sheet 1 of 2—

Table 3-1
Configuration manager tool bar icon descriptions
Pin The buttons displays the pin view, if there are any
pinned nodes.
Printer This button prints the view of the current level.
—sheet 2 of 2—
Note: The alarm state of CCS7 Message Transport Part (MTP) resources
will be set to ‘unknown’ because USP and SLR nodes do not report this
information at the present time.
Configuration Menu 3
Figure 3-2 identifies the display options available from the Configuration menu:
• Hide —hides or shows the Configuration Management window. A check
mark in the menu confirms Hide.
• Drill Up — displays the next hierarchy level up the current element.
• Drill Down — displays the next hierarchy level down a selected element.
• Info Window — displays a window describing a selected element.
• Color Nodes by — displays nodes in color by either Alarm Severity or
Propagated Severity.
— Alarm Severity: nodes that have an alarm are colored. They are
colored by the value of their alarm status attribute. This will cause
container nodes and region nodes to be grey as they have no alarms on
them. Color Nodes by Alarm Severity is the new default mode of
operation.
MDM/DMS nodes are colored based on their most severe alarm
status; alarm status is not propagated to parents. The child indicator
color will reflect the color of the highest alarm under them.
— Propagated Severity: nodes are colored by their propagated severity if

the node has such an attribute (MDM nodes have this attribute, DMS
nodes do not). If they do not have this attribute, they are colored by

their alarm status attribute. This will cause container nodes to be

colored even if they have no alarms on them.
MDM nodes are colored based on the color given to that node by the
MDM. DMS nodes uses the traditional rules for alarm severity
propagation. The algorithm for setting the alarm status attribute on a
DMS container node is that the alarm status is set to a severity level
one below that of the alarm status of its worst child unless all children
have the same status in which case it is set to that status.
Regardless of whether nodes are colored by Alarm Severity or Propagated

Severity, the OMC-S Server nodes are colored at all times using the
traditional propagated severity rules. As the Server nodes do not get
alarms, they are colored based on process status. The propagation corner
uses the traditional rules.
When Element Manager is launched from an NSP:
— the ‘Color Nodes By’ options are only available for the raw feed.
— if color changes are applied in the NSP GUI, the user must always exit
out of the CEM GUI then restart the CEM GUI for the alarm severity
color change(s) to be applied. The user must use the File menu then
select Exit to close the GUI before restarting it. If the CEM GUI is
closed using the ‘X’ button, the color change(s) will not be applied
when restarted as the CEM GUI was not completely closed.
• Set Background — displays a background in the CM panel.
• Clear Background — removes the background.
• Clear Layout — moves the icons to the last saved positions.
• Set Default Login Id - allows entry of the default DMS user id and
password to verify for all connected DMS nodes.
• Clear Default Login Id - clears the default DMS user id and password
being used for all connected DMS node.
— Clear Non MDM Default Login Id
— Clear MDM Default Login Id
• Table Access - brings up the Table Editor interface.
• Wizard - brings up the main CM Wizard interface.

Figure 3-2
Configuration menu options

Drill Up/Drill Down

When a node is selected and the drill down button is pressed, a drill down is
preformed on the selected node. A drill down causes the selected node to
become the top-level format node and is displayed as the last node in the
parent panel. The child nodes of the selected node are displayed in the CM
panel. By selecting nodes and using the drill down button, the user can
traverse from the top level region nodes down to the final terminal nodes.
The drill up, or back, button preforms the reverse operation of the drill down
button causing the view to start at a higher level.
The user can also navigate by double clicking on nodes. This method of
navigation is not the same as drilling up and down on the nodes. A double
click will open a node if it is closed or close a node if it is open. If the view is
set to iconic or list, the level will change on the double click to show the
opened node's children. However if the view is logical or physical, the child
nodes may be displayed without a level change.
Note: A double click on a terminal node that can be posted on a MAPCI

screen will open the MAPCI window and post the node.
Information on elements
To view the attributes of an element in an Info Window, select the element in
icon or list mode and select either the Info button in the tool bar or the Info
Window menu item from the Configuration menu. The Information Window
for the selected element is displayed (see Figure 3-3).
The user can access the visible attributes by clicking on the folder containing
those attributes.

Figure 3-3
Info window
Table 3-2
Info window buttons
Button Description
Ok Accepts the data
Datafill Displays new generic Table Editor
Save Saves the data
Delete Deletes the data
Print Sends the full tree to the printer
File Saves the data to a file

The Info Window identifies the attributes (see Table 3-3) that are assigned to
the element. These attributes are updated dynamically as the Element
Manager monitors the node.
Note: Digital Multiplex System (DMS) refers to the MSC/HLR.

Table 3-3
DMS attributes
Status Description
administrativeState The administrative state of the element: locked or unlocked
alarmStatus The status of the selected element. If the children of the parent
element have multiple alarms of a different severity, the status of the
parent element represents the status that is one less severe than the
most critical status (unless all children have the same status).
alarmSummaryTabulation A summary of the critical, major, and minor alarms for the element.
Prior to GEM17, only alarms of children were tabulated.
availabilityStatus Additional TMN state information regarding the resource: offline,

under test, or functionally degraded.
Class The object class of the element.
DMS State The state of an entity on the DMS, rather than the representation of
that state in terms of TMN states. Both perspectives on the state of
the entity are represented in each object. DMS state is provided by
the attributes: nodeDmsState, linkSetDmsState, etc.
equipmentId The name of the object instance (for all types of DMS equipment).
linkSetId The name of the link set object instance. Corresponding to the CLLI of
the link set.
linkSetDmsState The DMS state of the link set.
localSubsystemStatus The status of the local SS7 subsystems.
managedFunctionId The name of the object instances for the mscCallProcessing,

vlrProcessing, hlrProcessing, and c7SignallingProcessing object
classes.
Name The name of the element.
networkId The name of the object instance for the network class.
nodeDmsState The DMS state of objects representing DMS equipment.
numberOfChildren The number of children contained within the element.
—sheet 1 of 3—

Table 3-3
DMS attributes
Status Description
operationalState The operational state of the entity: enabled or disabled. If the entity is
completely unable to function, the operationalState is disabled.
Otherwise, the value is enabled.
plane0State, plane1State The DMS state on the DMS of plane 0 on an ENET shelf. The
Element Manager may be out of sync with the DMS during major
maintenance processes. The maximum insync period is 30 minutes.
pSideState The state of the internal links from the CM message controller to the
(cMmessageController) peripheral modules, through the ENET.
remoteSubsystemStatus The DMS status of the remote SS7 subsystems with which the DMS
is communicating.
replaceable Whether or not an equipment component is a field replaceable unit.

For example, an individual card may be a field replaceable unit, while
another piece of equipment is not directly replaceable--being a
component of a larger unit which is replaceable.
routeId The name of the route. The format is the CLLI of the containing route
set concatenated with a “-” and the number of this route. For example,
the third route in the TORRTSET route set will be named
“TORRTSET-2”. (Numbering of routes begins with 0.)
routeDmsState The DMS state of a route on the DMS.
routeSetDmsState The DMS state of a route set on the DMS.
routeTrafficState The traffic state of a route on the DMS.
systemId The instances of the system object in the agent.
linkSetId The names a link set corresponding to the CLLI of the linkSet on the
DMS. When used in the route object, this attribute identifies the
linkSet which corresponds to that route.
unknownStatus When this value is set to true, other status attributes may not be
accurate (up-to-date).
userLabel The table tuple for this entity on the DMS.
carrierState The state of the T1 carrier associated with the peripheral module
which includes this attribute.
cmSynState Whether the units of the CM (CPU-0 and CPU-1) are currently
(computingModule) synchronized.
—sheet 2 of 3—

Table 3-3
DMS attributes
Status Description
cSidePortState An aggregate view of the state of the ports on the ENET used to
(enhancedNetwork) communicate with the computing module (that is, the C-side ports).
cSideStatus (LIM, LIU, The state of the links used to communicate between the listed nodes
C7SignallingProcessing,cM and the CM, through the ENET.
messageController)
fBusState (LIU) The state of the f-bus within the LIU.
hasPMdata Whether or not a resource object has performance measurement

(C7SignallingProcessing) data associated with it.
msPortStatus (linkset, This represents an aggregate view of the status of the ports on the
messageSwitch) message switch.
pSidePortState An aggregate view of the state of the ports used to communicate with
(cMmessageController, the peripheral modules (i.e. the P-side ports).
enhancedNetwork)
rpcStatus The status of the remote SS7 Point Codes the DMS is communicating
(C7SignallingProcessing) with.
thresholdAlarmIndication Whether or not a performance management threshold alarm is

currently active on this resource or its children.
—sheet 3 of 3—

Set a Background Image

The Set Background option in the Configuration menu allows you to display
bitmap graphic images as the background of the Configuration Management
window (Figure 3-4). This option is available in iconic view only. You can set
a different background image for each network level. For example, you may
want to use a country map at the network level, a city map at the switch level,
and a switch diagram at the element level.
Figure 3-4
CM window with background image
The background images must be in GIF (.gif) or JPEG (.jpg) format. The
image files can reside in any directory. The Manager/backdrops directory is
the default directory for the Element Manager background files.

To specify an image for a specific network level, drill down to the level and
select the Set Background option. Select the image filename from the list and
click Open.
Figure 3-5
Set Background
Clear the background image

The Clear Background option in the File menu removes the graphics that have
been set as a background for the current level of Configuration Management
window.
Arrange icons
You may want to place the element icons in a specific location on the screen.
To move an icon within the Configuration Management window, select the

icon, press and hold the Shift key and drag the icon to the new location.
To move all the nodes back to their home position, de-select the nodes and
select Clear Layout from the Configuration menu.
To move a single node back to its home position, select the node and select
Clear Layout for the Configuration menu.

To move all the nodes back to their home position, de-select the nodes and
select Clear Layout in the Configuration menu. If the layout of the nodes is
lost when re-sizing the Element Manager window, select Clear Layout in the
Configuration menu to reset the node positions, then re-arrange them to your
requirements.
When exiting the Element Manager application, always save your changes.
This will save the new location of your icons.
Information bubble
You can activate information bubbles in the Configuration Management
window by clicking on an element using the middle mouse key (Figure 3-6).
Figure 3-6
Information bubble with the number of sub-elements
Note: If the link between the SDM and Element Manager goes down, all
nodes appear in cyan (status unavailable). When this happens, the
information bubble displays the status of the node before the link went
down.
The items displayed in the bubble depend on what type of element is selected:
• Alarm status - The line on whether the element contains sub-elements or
not, this status may be the status of the element itself, or may reflect the
highest severity alarm status of a sub-element.
• Availability status - This line is displayed only for elements which have an
availability status.
• Location - This status is displayed only for switch elements.
• Software version of the NE
Note: When the information bubble for an SDM is activated, the software
version displayed in the information bubble is the software version of the
CEM Server and not the SDM.

• Number of sub-alarms - This reports the total number of alarms on sub-

elements at the highest level of criticality. For example, a TRK_GRP
container with 10 Critical sub-alarms and 50 Warning sub-alarms reports
10C+ (where C=Critical, M=Major, m=minor, W=Warning) only. The
lower severity Warning alarm count is not reported.
• Number of sub-nodes - The total number of sub-nodes for this element.
Pop-up menus for node manipulation

Pop-up menus with MAP commands can be displayed for some nodes by
right-clicking on the icon. The menu items in the pop-up menu include some
of the same commands available for that node in the MAPCI system. You can
see this by opening a MAP display to the switch element this node belongs.
Be sure to check the Target MAP checkbox. Then click a command such as
post bsy, offl, or rts (if available). You will see in the MAP display the results
of drilling down the MAP command structure and issuing a post command at
the prompt. The results are similar for other commands (if available).
Some of the pop-up menus contain menu items that disconnect or reconnect
the selected element. Refer to “Disconnect/reconnect an element” on page 2-
16 for more information.
Configuration Management Window 3

The Configuration Management window can be displayed in one of several
modes:
• Physical
• Logical
• Iconic
• List
• Pinned nodes
By default, the Configuration Manager chooses the appropriate view for a

particular level.

Reshaping region nodes

The border around the region or circular nodes can be reshaped in physical
mode view.
When the right mouse button is clicked on the region (circular) nodes in
physical mode, a pop-up menu (Figure Figure 3-7) is displayed which
contains a Reshape command.
Figure 3-7
Reshaping Region Nodes Pop-up Menu
When the Reshape menu item is selected, the region node and border around
it is clear and the user can then give the desired shape to the node. While
reshaping the node, a different set of actions are supported by the pop-up
menu (Figure 3-8), which can be launched by clicking the right mouse button.
Figure 3-8
Reshaping option menu
These actions are as listed below:

• Undo - cancels only the previous draw action
• Done - sets the shape of the region node to the current shape drawn
• Default - resets the shape of the region node to the default which is a
square

• Abort - cancels the reshaping of the node, and sets the shape of the region
node to the previously saved shape and not the default.
Note: Reshaping of the nodes is only allowed for region or circular nodes
and can be performed only in physical mode. Also curved lines are not
supported for the shape of the region node.
Workspaces and sorting items

The nodes displayed in physical, logical and icon mode of the Configuration
Management window can be sorted by the following criteria:
• Add Workspace
• Sort By Name - sorts the nodes in alphabetical order
• Sort By Severity - sorts the nodes based on the severity of the nodes
Note: When icons appear on both sides of the parent node, each side is
sorted independently.
These options are available from a pop-up menu (Figure 3-9) which is
displayed by right-clicking in an empty region of the Configuration
Management window.

Figure 3-9
Configuration Management Window Pop-up Menu
Note: This menu is not displayed in List Mode of the Configuration

Management Window.
The nodes displayed in List Mode can be sorted by double clicking on the
header of the column. The sort order can be reversed by double clicking on
the header of the column again.
Workspaces
Workspaces allow the user to group NEs, Servers, or sub components of NEs
into a user defined region. This allows the user to manage only the specific
resources in which they are interested. When a component is added to a
workspace, an exact copy of the component is created and placed in the work
space, and any change in the alarm status of the component is reflected in the
workspace as well as in the original path.

Note: Workspaces are part of a layout and are saved upon exit along with
the layout information and are restored when a layout is opened.
The difference between the concept of workspaces and layout management are:
• Components or resources under an NE cannot be isolated in layout
management.
• The elements in a workspace are just copies of original elements and
removal of elements from a workspace will not affect the elements in the
original path.
A workspace can be added by selecting “Add Work Space” menu item from
the pop-up menu on the background of the Configuration Management panel
(Figure 3-10).
This will display a dialog prompting the user to enter the name of the
workspace.
Figure 3-10
Workspace Name Window
The pop-up menu for a resource, which can be displayed by clicking the right
mouse button on the resource, contains an “Add To” menu which lists all the
workspaces created. The resource can be added to a workspace by selecting
the work space from this menu.

Figure 3-11
Workspace Name Window
WARNING:
A server or standalone SDM cannot be added directly
to a workspace with the add menu commands as it
must be first added to a region and then added to a
workspace with the “Go to Workspace” menu item. If
the region name entered when adding the node
happens to match an existing workspace name, the
region will be added as a region node and not try to
put the node under the matching workspace. The end
result will be a region and a workspace with the same
name appearing in the GUI.
Physical mode
The Physical mode identifies Network elements in the logical view, with the
exception of Trunks, which are shown as icons. (Figure 3-12) This is the
default setting.

Figure 3-12
Configuration Management window in physical mode

Logical mode
The logical mode identifies the network elements in a logical block format
(Figure 3-13).
Figure 3-13
Configuration Management window in logical mode
Icon mode
The icon mode displays the element of the network as icons.
Figure 3-14
Configuration Management window in icon mode

Icon shapes
The icon that appears is based on the type of element that the system
identifies. Table 3-4 identifies the icons for the different types of network
elements.
Table 3-4
Element icons
Icon Type of Element
Manager - This icon is usually the top level component in the

CEM browser display.
Node or region - This icon identifies the top layer of the network
hierarchy. From here, you can add a switch or region with the
Add Node command from the File menu. For more information
on adding or removing a node, refer to Chapter 1, “Getting
started”
CEM/W-NMS NSP Server
Mediation Device - For example: SDM/FT or MDM.
MDM Server
DMS Managed Element (Circuit)
—sheet 1 of 3—

Table 3-4
Element icons
MDM Management Element (Packet)
Process Group that contains software application processes.
Process
Terminal Node that does not have any sub-components.
Resource that has sub-components.
Logical container - This icon is created by the CEM browser to

group a specific type of resources and does not correspond to
any real equipment.
Trunk Group Resource
—sheet 2 of 3—

Table 3-4
Element icons
Security - A resource to which all the logs related to the user

login are mapped.
Performance Management resources - This icon represents

groupings of operational measurements (OMs) collected from the
MSC or HLR. 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.
—sheet 3 of 3—
Note: The colors for the icons in the above table are default colors and
are replaced by actual colors based on the alarm status of the resources.
Icon colors
When there is an alarm associated with a resource, the color of the resource
changes. This alarm could be a state change alarm (for example, from in
service to manual busy), a non-state change alarms (for example, test result
failed), or a propagation of alarms from its children (if it’s a logical
container). The colors are further determined by the rules explained in GSM /
UMTS Voice Core Network OAM Reference Manual, NTP 411-8111-803.

List mode
The list mode identifies the network elements in a table format (Figure 3-15).
Figure 3-15
Configuration Management window in list mode
The list mode format identifies the following:

• Alarm — alarms occurring on the element
• Element — the name of the element
• State — the state of the element
• Sub Alarms — the number and types of alarms associated with the
element’s children (sub-elements)
Note: Sub-Alarms only indicates the critical, major and minor alarms.

Resize columns
To resize a column in the list window, drag the list header of the column to the
right of the column you want to resize. All columns to the right of the selected
column will move.
Sort items in the column

Items are sorted in alphabetical or numerical order. If you double click a
sorted item, it will reverse the sort order. To sort items listed in a column,
double-click on the list header.
Note: All sorting is case sensitive, where A-Z is sorted before a-z.
For multiple selection sorting, first select the second sorting criteria with the
sorting preference then select the primary sorting criteria with the sorting
preference.
Pin mode
The pin mode identifies the network elements in a pinned/unpinned format
(Figure 3-16).
Figure 3-16
Configuration Management window in pin mode
Pin mode allows you to filter the nodes displayed in the configuration
management area. Pinning keeps a node in place when the parent node is
closed. When the node is unpinned, and the parent node is closed, the node
disappears. If the parent node remains open, the node remains displayed. As
the name implies this view only displays the pinned nodes in the
configuration management area.
Pinning allows you to separate a group of nodes of interest. These nodes may
be from the same switch or from different switches. The pinned nodes are
displayed with a “Pin” image drawn on top of them as shown in Figure 3-17.

Figure 3-17
Pinned Nodes
If the user drills down manually to a node at level four, all of the parent nodes
are open. Pinning and unpinning of the terminal node does not close the
parent nodes.
If, however, a find and pin menu item is used to find a node, then the terminal
node is shown with all parent nodes closed. If the node at level three is then
manually opened and the terminal node (level four) is unpinned, then the
parent node at level two will close as it was never manually opened. This
causes nodes at levels three and four to close as the level two node is closed.
This is pinning to force a node to show even though a parent node is closed.
Once a pinned node is unpinned and one of its parents is closed, it too will be
closed.
Shelf level display

Shelf Level Management is aimed at extracting and displaying the hardware
layout of the network element components. Figure 3-18 displays the Shelf
Level display of a Message Switch for a DMS node.
In the case of DMS based network elements, shelf and shelf row position
information can be obtained from the hardware inventory tables. They usually
contain the floor, row, frame position, frame type, frame number, shelf
position and pec information. The CEM browser arranges the resources in a
shelf based on these attributes.
Shelf Level Display is only available for components under MS, ENET, XA
Core, PM (Series III & Series IV), SLR Shelf-0 and SAM21 containers. Shelf
Level Display can only be viewed when the Physical View is selected from
the Configuration Management panel. When one of the above supported
components is opened in physical view, the shelf and the cards on the shelf
are displayed.

If a level for a resource has cards on two physical sides (for example: front
and back), they are displayed one below the other in the Configuration
Management panel.
All the operations pertaining to a resource like opening a MAP terminal and
executing maintenance commands, filtering the alarms for a particular
resource, and viewing histograms are supported for Shelf Level Display in
physical view.
Figure 3-18
Shelf level display of message switch for DMS
Find carriers and linksets

This functionality is based on the connectivity rules. You are provided with
the ability to find a corresponding carrier for a trunk or an LIU for a linkset.
Support storage, setting, and retrieval of notes for nodes

The notes for the node are saved on the SDM and are visible to all the users
looking at that switch. The user is provided with a mechanism to modify the
note at any time. The node carrying a note will have a graphical indication.
The notes for the nodes are stored locally on the PC. They are not shared
amongst other users and also the note was created when a node was added and
thereafter there was no way to modify the note.

Integration with performance management

Some of the aspects regarding the access of the performance management
information which can be obtained directly from the configuration management
window are:
• display threshold management information for PM resources in the Info
window (example: Last Value - Critical, Major, Minor).
• display performance management information for the PM resources in the
info window (example: pmCurrentData).
Print support for the configuration management panel window

You can print the view displayed in the configuration management window.
Note: The nodes which are already drilled down and are displayed on the
left hand side of the configuration management area will not be printed.
DMS table configuration 3

Configuration management for the DMS nodes is not simply resource
management. With this release, configuration capabilities are introduced as
part of configuration management. Table configuration refers to the
management of datafill/resource setup, changes, and deletions on DMS
nodes.
Table Configuration functionality is separated into two areas: Table Editor

and a Configuration Management Wizard.
The Configuration menu (Figure 3-19) allows you to manipulate how

configuration and state information is displayed.

Figure 3-19
Configuration menu options
The Configuration menu includes the following two Table Configuration

commands:
• Table Access
• Wizard
Security
As a security measure, when you select either one of the Table Configuration
commands, you must enter a DMS user ID and password at the Default User
Login screen (Figure 3-20) in order to access DMS datafill. When a user logs
in using this interface, the ID and password become the default ID and
password. When the user clicks OK, the Element Manager attempts to verify
the user ID and password on all connected DMS nodes. The Clear Default
Login Id screen clears the default DMS user ID and password being used for
all connected DMS nodes.

Figure 3-20
Default User Login screen
Table Editor
In the Nortel DMS, a data file used to configure a portion of the system is
known as a table. In those tables, a record is known as a tuple. The
information in a table is known as datafill.
The Table Editor performs all table editing functions such as reading, adding,
changing, and deleting tuples. It can create new tuples, and copy and paste
tuple(s) from one DMS node to another. It provides a direct way to edit
datafill without using the MAPCI interface. The Table Editor displays
multiple DMS nodes that the Element Browser is currently monitoring.
Tables for each node are dynamically discovered and displayed when a node
is selected.
The Table Editor (Figure 3-21) consists of:

• The Table Editor window menu bar
• The Table Editor window toolbar
• The Table Keys list - displays the keys for the tuples in tables and sub-
tables in a tree format
• The Table Editor desktop - provides a workspace to view, edit, and add
tuples

Figure 3-21
Table Access Editor
The Table Editor supports viewing and editing of all tables listed in table
CUSTAB except for tables GCALLINT, GCALLTRCE, GHLRTRCE, and
PSTKTRCE.
Table Editor toolbar

The Table Editor window toolbar provides two drop down boxes (Switch and
Table). The Switch drop down box only displays the nodes which are being
monitored by the Element Manager and which are connected to SDMs
installed with GEM14 or above OMC-S software. Switches are added to the
drop down box via the Element Manager. The font color of the switch name
in the Switch drop down box signifies the status of the switch.
DMS access is checked each time a node is selected from the drop down box.
The Table drop down box displays the list of tables automatically discovered
when a node is selected.
The Table Editor toolbar(Figure 3-22) supports the following options:

Figure 3-22
Table Access Editor toolbar
• Switch drop down box - displays the switches being monitored.

• Table drop down box - displays the tables that can be viewed or edited for
a selected switch.
• Show button - downloads keys of the selected table for the selected switch
from the cache on the SDM/FT and displays them in the table keys list.
• Refresh button - downloads the keys of the selected table for the selected
switch directly from the switch, cached on the SDM/FT and displays them
in the table key list.
• Help button - displays the help document on the selected table.
• Print button - prints the Table Access Editor window.
The Switch drop down box allows the user to change the current user ID
(Change User) and to clear the user ID and remove the tuple, table, and switch
nodes from the display (Hide).
The Table drop down box (Figure 3-23) provides the following capabilities:
• Refresh - performs the same function as Refresh button in the tool bar.
• Select All - selects all the tuples for the table.
• Paste Tuple(s) - adds the tuples copied from the table editor desktop to the
selected table.
• Add Tuple - launches the Add Tuple window. From here the user can
either display or delete tuples.
• Sort - sorts the tuples in alphabetical order when Alphabetical is selected,
or by the order in which they were received from the OMC-S application
on SDM when Default is selected.
• Hide - removes the selected table and all the tuple keys from display.
• Help - displays help for the selected table.

Figure 3-23
Table drop down menu
Displaying tuples
Selecting the Display Tuples option (Figure 3-24) shows the tuples selected
from the table keys list in a tabular format (Figure 3-25). Functionality is
obtained by using the shift key.

Figure 3-24
Display tuples
Figure 3-25
Tuple table

Table datafill can be retrieved automatically through the Table Editor as long
as the SDM load connected to the target node is at least GEM14. When a
resource is in view in the configuration management panel, right clicking on
the resource pops up a menu with Datafill as one of its options (Figure 3-26).
By clicking this menu item, a new instance of the generic table editor is
brought up along with the associated tuple.
Figure 3-26
Pop-up menu view
Another way to start the Table Editor is through the Info window of a
resource.
The header of the tuple table consists of all the field names grouped
appropriately. The key and non-key fields are grouped separately.
Once a tuple is selected, a pop-up menu (Figure 3-27) displays the following
options:
• Add - launches the Add Tuple window.
• Change - launches the Change Tuple window. This menu item is disabled
if multiple tuples are selected.
• Delete - deletes the selected tuple(s).
• Copy - copies the selected tuple(s) to the system clipboard.
• Hide - removes the selected tuple(s) from the tuple table.
• Help - launches the help document for the table. This menu item is
disabled if multiple tuples are selected.

Figure 3-27
Tuple pop-up menu
In addition to the selected tuple pop-up menu, the user has two toolbar
options, File and Edit. Once File is selected, the user can either export (Figure
3-28) the displayed tuples to a specified file, or close the tuple table. Exported
tuple fields are separated by tabs with empty fields represented by a dash.
Tuples can be exported in text format or tab separated files can be opened into
an Excel format. Edit provides the ability to copy selected tuples to the
system clipboard or paste previously copied tuples to the table.

Figure 3-28
Export tuple
Add tuples
Launch the Add Tuple window (Figure 3-29) by selecting the Add Tuple
menu item for a table node from the Table Keys list or by selecting the Add
menu item from the pop-up menu for a tuple in a tuple table window.
The new values entered for the fields are indicated in red.
• Close - cancels the changes made to the fields and closes the window.
• Reset Field - resets the value of the selected field to its original value.
• Reset All - resets the values of all the fields to their original values.
• Add Tuple - sends the add tuple request to the OMC-S application on the
SDM.

Figure 3-29
Add Tuple Window
Changing tuples
The Change Tuple window (Figure 3-30) can be launched by selecting the
Change menu item from the pop-up menu for a selected tuple or by double
clicking on a tuple in a tuple table window.
The current value for a selected field of a tuple displays at the bottom. The
modified values for the fields are indicated in red. Values are not displayed for
folder nodes and fields representing sub-tables.

Figure 3-30
Changing Tuple window
From this window, the following options are available:

• Reset Field - resets the value of the selected field.
• Reset All - resets the values of all the fields.
• Change Tuple - sends the change tuple request to the OMC-S application
on the SDM.
• Close - closes the window and displays a warning dialog if the changes
are not submitted.
The results of the change tuple operation are displayed in a dialog box and are
also logged to the Table Access Info Log window.
Note: A nil change (submission of a tuple without any changes) is

considered a valid operation.

Table error codes

Below are two lists of possible error codes depending on the type of operation
attempted (read, add, change, delete).
Read error codes:

• cTAI_SOFTWARE_VERSION_NOT_SUPPORTED
• cTAI_SOFTWARE_ERR
• cTAI_OUT_OF_SDM_RESOURCES
• cTAI_OUT_OF_CM_RESOURCES
• cTAI_SDM_PROCESSING_FAILURE
• cTAI_TA_SERVICES_NOT_AVAILABLE
• cTAI_DATA_DICTIONARY_UNAVALIABLE
• cTAI_TUPLE_DELETED
• cTAI_ACCESS_DENIED
• cTAI_CM_FA_CONVERSION_FAIL
• cTAI_SDM_CONVERSION_FAIL - tuple field format is incorrect
• cTAI_KEY_NOT_FOUND
• cTAI_END_OF_TABLE_REACHED
• cTAI_TOP_OF_TABLE_REACHED
• cTAI_TC_LOBICAL_TABLE_ERROR - unexpected DMS processing
error
• cTAI_TC_BAD_FIELD
• cTAI_TC_INCOMPATIBLE_ERROR
• cTAI_TC_BAD_KEY_ERROR
• cTAI_TC_OUT_OF_TUPLE_SPACE_ERROR
• cTAI_TC_INCONSISTENT_DATA_ERROR
• cTAI_TC_ACCESS_ERROR
• cTAI_TC_NOT_IMPLEMENTED_ERROR
• cTAI_TC_NOT_POSSIBLE_ERROR
• cTAI_TABLE_CONTROL_ERROR
• cTAI_CM_UNAVAILABLE
• cTAI_SUBTABLE_ERROR
• cTAI_BAD_TUPLE_KEY_ERROR

• cTAI_CM_PROCESSING_ERROR - CM not in sync or image dump in

progress
• cTAI_CM_TRANSMIT_BUFFER_FULL
• cTAI_SDM_TRANSMIT_BUFFER_FULL
• Add, change, or delete error codes:
• cTAI_SUCCESS
• cTAI_SOFTWARE_VERSION_NOT_SUPPORTED
• cTAI_SOFTWARE_ERR
• cTAI_OUT_OF_SDM_RESOURCES
• cTAI_SDM_PROCESSING_FAILURE
• cTAI_TA_SERVICES_NOT_AVAILABLE
• cTAI_DATA_DICTIONARY_UNAVALIABLE
• cTAI_ACCESS_DENIED
• cTAI_CM_FA_CONVERSION_FAIL
• cTAI_SDM_CONVERSION_FAIL - tuple field format is incorrect
• cTAI_KEY_NOT_FOUND
• cTAI_TUPLE_ALREADY_EXISTS
• cTAI_DUPLICATE_TABLE_NAME
• cTAI_TC_LOBICAL_TABLE_ERROR - unexpected DMS processing
error
• cTAI_TC_BAD_FIELD
• cTAI_TC_INCOMPATIBLE_ERROR
• cTAI_TC_BAD_KEY_ERROR
• cTAI_TC_OUT_OF_TUPLE_SPACE_ERROR
• cTAI_TC_INCONSISTENT_DATA_ERROR
• cTAI_TC_ACCESS_ERROR
• cTAI_TC_NOT_IMPLEMENTED_ERROR
• cTAI_TC_NOT_POSSIBLE_ERROR
• cTAI_TABLE_CONTROL_ERROR
• cTAI_UNKNOWN_STATE
• cTAI_CM_UNAVAILABLE
• cTAI_VERIFY_PROC_FAILURE
• cTAI_SUBTABLE_ERROR

• cTAI_BAD_TUPLE_KEY_ERROR
• cTAI_CM_PROCESSING_ERROR - CM not in sync or image dump in
progress
• cTAI_CM_TRANSMIT_BUFFER_FULL
• cTAI_INVALID_DATA_CHG_REQUESTOR
• cTAI_JOURNAL_FILE_UNAVAILABLE
• cTAI_BUILD_JOURNAL_FILE_FAILURE
Sub-tuples
Sub-tuples are displayed under the folder representing the main tuple. The
procedure to add, change, or delete a sub-tuple is similar to that of a head
tuple. Select the sub-tuple (Figure 3-31) and an Add Tuple window for the
sub-tuple is displayed.
Figure 3-31
Sub-tuple

Table Editor menus

The Table Editor has two menu options (File and Help). The File menu
(Figure 3-32) supports the same options as the toolbar with the following
exceptions:
Figure 3-32
Table Editor File menu
• Info Log - displays the Table Access Info Log window which contains a
log of the table access operations performed along with the results. Add,
change, and delete messages (and results) sent to the OMC-S Element
Manager are logged to this window.
• Close - closes the Table Access Editor window.
Figure 3-33
Table Access Info Log

Help Menu
The Help menu displays an on-line Element Browser User’s Guide and
provides on-line help.
Figure 3-34
Help menu
Table Access Editor limitations

The following limitations are imposed on the Table Access Editor window to
save on memory and resource usage:
• Number of Table Editor Windows - the maximum number of Table
Access Editor windows that can be launched from the Element Browser is
1. A dialog box displays when this number is exceeded.
• Number of tuples - the maximum number of tuples that can be displayed
in a single Table Access Editor window is set to 10000. A dialog box
displays when this number is exceeded. If the number of tuples is less
than 10000, the table can be read; however, partial tables cannot be read.
The maximum number of tuples per Tuple Table is 1000. Exceeding that
number removes tuples from the beginning of the list.
• Number of Table Editor Desktop Windows - the maximum number of
windows that can be launched within a single Table Access Editor
Desktop is set to 20. A dialog box displays once this number is exceeded.
• The Table Editor is not notified of table schema changes. The list
containing a valid range of values for some fields will not updated. The
table has to read again in order to obtain the updated schema. For
example, the Add Tuple window for table TRKGRP contains a CLLI field
whose available values display at the bottom. If a new CLLI is added, this
list will not be updated. Table TRKGRP has to be read again and a new
Add Tuple window has to be launched to see the updated values for the
field CLLI.
• Configuration Management does not get notified of table changes when
tuples that do not go through DMS table control are added, changed, or
deleted. This results in some tables not being updated when these events
happen. For example, when a maintenance trunk is added to table
TRKGRP; a new tuple in TRKSGRP is added, but the DMS node does
not notify Configuration Management.

Configuration management wizards 3

Configuration Management Wizards apply commonly configured tables into
wizards and makes table maintenance much easier. Configuration files drive
the display of the windows. An example of a commonly needed datafill is
trunk configuration. The wizard guides the user through datafilling the tables
in ordered sequence. Additional information regarding the datafill may be
accessed through the More Info option. The Configuration Wizard also offers
on-line help and easier deletion of datafill.
Several wizards related to trunk configuration are available:

• Provisioning trunk group by defining the CLLI to the trunk members
involved for trunk types, GSM, MAINT, TL, and PET. For PET trunks,
only CCS7 ISUP, FST, and ISTD signalling type are supported. The tables
to be configured on the DMS node are CLLI, TRKGRP, TRKSGRP, and
TRKMEM.
• Provisioning trunk members including a wizard for adding maintenance
trunks. The table to be configured on the DMS node is TRKMEM.
• Unprovisioning trunk group in tables related to trunk group configuration.
• Unprovisioning trunk members.
• Provisioning and unprovisioning of tables related to the CCS7 Message
Transport Part (MTP) is also provided. The tables to be configured on the
DMS node are C7LKSET, C7LINK, and C7RTESET.
• Provisioning and unprovisioning of tables related to the CCS7 User Part
(CSUP) is provided. The tables to be configured on the DMS node are
ISUPDEST and C7TRKMEM.
To configure CCS7 trunks first, use the Add Trunk Group wizard, followed by
the Add CCS7 MTP wizard, followed by the Add CCS7 User Part wizard.
The main interface window (Figure 3-35) provides the user with a list of
wizards.

Figure 3-35
Main wizard interface
The user selects the wizard by double-clicking the list item or selecting the
list item and clicking the Start button. Only one wizard can be started per
browser at any time.
When each wizard is brought up, there are several buttons in each interface that
guide the user. On the bottom of the CM Wizard box, the following buttons
appear:
• Cancel - cancels the wizard
• Back - returns user to the previous frame
• Next - verifies the current entry and continues to the next frame

On the top right area of each frame, sometimes the ‘?’ button is visible to select.
The ‘?’ button brings up on-line help on the DMS table of interest
On the center right area of each frame, sometimes the following button is visible
to select.
• Show Info... - displays related table datafill for the user to identify the
right datafill to enter.
• Hide Info - turns the display off what the ‘Show Info...’ data is displaying.
When entering each frame, sometimes it is required that the wizard retrieve
information from the target node. In these situation, a working progress
indicator is displayed that it is in the process of waiting for completion of this
retrieval. Only upon completion, the wizard will allow to continue.
The user at any time has the option to cancel the wizard or go back to the
previous frame except when in the midst of submitting tuples to the target
node.
Wizards for R4 provisioning

R4 wizards use configuration files to drive the display of the windows. The
wizard guides the user to datafill the tables of consequence in ordered
sequence and the values that the fields of the table may have. When necessary,
additional information through the ‘More Info’ option is available to identify
the correct datafill to enter. On-line help will also be available in the wizard
for user to access. The wizard will also make deletion of some datafill much
easier. If the wizard fails to configure a table, a log will be generated
indicating the error reported and recorded in the info log window and the log
file, wizard.log, under the “dat” directory on the user’s workstation.
The following wizards related to R4 trunk configuration are available in this

release:
• Provisioning trunk group by defining the CLLI to the trunk members. For
R4 trunks, only CCS7 ISUP, FST, and ISTD signalling type are supported.
The tables to be configured on the DMS node are CLLI, TRKGRP,
TRKSGRP, and TRKMEM.
• Provisioning trunk members including a wizard for adding maintenance
trunks. The table to be configured on the DMS node is TRKMEM.
• Unprovisioning trunk group in tables related to trunk group configuration.
• Unprovisioning trunk members.
• Provisioning trunk groups for BICC. The tables to be configured on the
DMS node are CLLI, TRKGRP, TRKSGRP, ISUPDEST, TRKOPTS and
GBCIC.

• Provisioning Media Gateway pools. The table to be configured on the

DMS node is MGWPOOL.
• Unprovisioning BICC trunk groups in tables related to BICC trunk group
configuration.
• Unprovisioning Media Gateway pools.
Add Trunk Group Wizard

This wizard allows users with less DMS datafill experience to datafill trunk
groups quickly and easily. The wizard adds tuples to the following tables
CLLI, CLLIMTCE, TRKNAME, TRKGRP, TRKSGRP, and TRKMEM.
When the user selects this wizard, a list of available DMS nodes is displayed
and the user is asked which DMS node is to be added to the trunk group
(Figure 3-36). A list of available DMS nodes displays. After the user selects a
node, the Next button is enabled. The user then clicks Next to continue with
the configuration.
Figure 3-36
Select target node screen
A check box allows a user to select another user ID and password for this
function. The wizard prompts the user for a user ID and password when there
is no default user ID and login was unsuccessful (Figure 3-37).

Figure 3-37
User ID screen
Once the User ID and Password have been verified, the wizard prompts the
user for a CLLI name (Figure 3-38).
Figure 3-38
CLLI prompt
Clicking on the Show Info button displays a list of CLLI names on the target
node. Once a CLLI name is entered, the wizard tries to find the closest match
to the name entered and displays the name in the CLLI list. The user can turn
off the CLLI display by clicking the No Info button. When a name is entered,
the Next button becomes enabled. However, if the name chosen already

exists, the wizard displays a dialog box indicating the problem and prohibits
the user from continuing.
When the user enters a new CLLI name and clicks on the next button, the
following screen appears.
Figure 3-39
Add CLLI tuple
The CLLI values are displayed. The user has the option of changing the
values entered (including the Admin Number). The Admin Number is a
unique number assigned by the wizard. Changing the Admin Number does
not guarantee that the addition of the CLLI will succeed. The ? button brings
up table CLLI documentation.
Once the information is correct, click on the Finish button to datafill table
CLLI or the Next button to continue with the next trunk group configuration.
Note: Currently available wizards cannot pick up from this point later
once the wizard submits the datafill addition.
Clicking on the Next button displays the following screen (Figure 3-40).

Figure 3-40
Add Trunk Group
This screen prompts the user for the trunk group type. The ? button brings up
table TRKGRP documentation.
If the user selects GSM, PET or MAINT as the Trunk Group type, the Finish
button will be disabled. Clicking on the Next button will display Figure 3-41
prompting the user for the direction and CICPOOL for the trunk group.
Figure 3-41
Select the Direction and CICPOOL

Trunk group types

At this point, the user selects the Finish button to only datafill up to table CLLI
and TRKGRP. Based on the selected Trunk Group Type, clicking the Next
button displays various screens. The available trunk types are:
• GSM
• TL
• MAINT
• PET
If the selected group type is GSM, Figure 3-42 displays and prompts the user
for the Trunk Subgroup Number.
Figure 3-42
Trunk Subgroup Number
If the Trunk Group Type is not PET, the user selects the Finish button to only
datafill up to table CLLI, TRKGRP, and TRKSGRP. If the user later decides
to continue adding trunk members from the trunk group, he selects the Add
Trunks or Add Maintenance Trunks wizard to add members.
If the group type is TL, clicking the Next button directs the user to the
following screen. Figure 3-43 also appears and the indicated steps are
performed.

Figure 3-43
Defining trunk members
This screen prompts the user for the peripheral name, number, circuit, and the
number of timeslots to allocate to members. The ? button brings up table
TRKMEM documentation. The Show Info button brings up the list of
available peripherals.
The Number of timeslots to add field contains a list of available timeslots on

the selected circuit and peripheral. The list changes based on the circuit and
peripheral selected. Choose the number listed to advance to the next frame.
After the fields are filled, the user can continue selecting other circuits and
peripherals to add. When the user is finished adding trunk members, he clicks
on Finish to start the tuple submission stage; the final step of the wizard.

If the selected Trunk Group Type was MAINT, the wizards directs the user to
enter the card code for this group (Figure 3-44). Once the Next button is
selected, the wizard prompts the user to define the trunk group members.
Note: If a trunk group of type MAINT is added, then the following error
message displays:
CTAI_VERIFY_PROC_ERROR: Datafill TRKSGRP before
TRKGRP.
If this occurs, keep the Add Trunk Group window open and manually add the
tuple to table TRKSGRP with the desired datafill in the MAP interface. Then,
click on the BACK button and submit the tuples to tables TRKGRP and
TRKMEM.
Figure 3-44
Card Code screen
Selecting Trunk Group Type PET prompts the user to add a Signaling Type
for the group (Figure 3-45).

Figure 3-45
Signalling Type screen
Once the Signaling Type is entered, the wizard prompts the user for the
Translation System and Name (Figure 3-46 and Figure 3-47).
Figure 3-46
Translation System screen

Figure 3-47
Translation Name screen
Clicking on the Next button prompts the user for a billing destination number
(Figure 3-48).
Figure 3-48
Billing Destination Number screen
At this point in the wizard, if the Trunk Group Type is PET and the signalling
type is C7UP, the user enters the trunk protocol timer (Figure 3-49).

Figure 3-49
Trunk C7UP Timer screen

Submit tuples
Once tuples are added and configured, they are submitted (Figure 3-50).
Figure 3-50
Submit tuples
Clicking the Submit button begins the addition of each tuple and displays the
addition results. The user cannot go back to the previous frame and cancel the
wizard. If for any reason the submission is unsuccessful, the failure is brought
up in a dialog box and is noted in the log window of the browser. This
information along with a time stamp is stored in the wizard.log file and the
process halts. The user can return to the previous window, enter new data, and
re-submit the tuple.

Delete Trunk Group Wizard

This wizard deletes BICC trunk group datafill by entering a few entries. This
section gives a snapshot of the frames that the user will be encountering to
delete a trunk group from tables CLLI, TRKGRP, TRKSGRP, TRKOPTS and
GBCIC. This wizard does not verify the existence of the trunk group in other
tables due to the large number of tables to filter through to find all
occurrences.
Note: If a trunk group of MAINT is to be deleted, then the following

error message displays:
CTAI_VERIFY_PROC_ERROR: Datafill TRKSGRP before
TRKGRP.
Keep the Delete Trunk Group window open, and manually delete the
tuple from the table TRKSGRP in the MAP interface. Then, click on the
BACK button and submit the tuples to tables TRKGRP and TRKMEM
for deletion.
After the tuple is deleted from TRKMEM, the user can delete it from table
TRKSGRP within MAPCI and proceed with the trunk group deletion
using the Delete Trunk Group wizard or the Table Editor.
When the Delete Trunk Group wizard begins, it queries for a DMS node. A
list of nodes is available from the pull-down list.
Figure 3-51
Target node screen
Once a node is selected, the Next button becomes active. The user then clicks
Next to continue with the deletion. As with the adding of trunk group wizard,
if the user has not been verified on the target DMS node, the user ID

verification interface (Figure 3-52) is displayed. Once the user enters a user
ID and password, the Next button is enabled. The user then clicks Next to
verify the user ID and password. If successful, the wizard continues with the
deletion. If not, a dialog box (Figure 3-53) will appear indicating
unsuccessful verification. The wizard will not continue to the next interface
until the user ID and password combination is successfully verified.
Figure 3-52
User ID verification
Figure 3-53
User ID verification error
Once identification has been established, the user is asked to select a network
type from a pull-down list (Figure 3-54). The user then clicks Next to
continue.

Figure 3-54
Network type selection
The user is given a pull-down list of CLLI names and selects the CLLI name
of the trunk group to be deleted. Once a CLLI name is selected and data
retrieval completed, the Next button is enabled to allow the user to advance to
the next window. The ? button is displayed to allow the user to bring up on-
line help on table CLLI.
Figure 3-55
Trunk group selection

The wizard directs the user to busy and offline the trunk group (Figure 3-56)
if it has not been offlined already. Only click on Next when the trunk group
has been offlined.
Figure 3-56
Busy/Offline prompt
The user is then presented with the list of tables that the wizard found to
contain the trunk group chosen (Figure 3-57). Clicking the More Info... button
displays the table and keys to be deleted.

Figure 3-57
Submit window
When the user clicks the Submit button, the wizard deletes each tuple and
displays the results of the deletion (Figure 3-58). Once begun, the process
cannot be cancelled.

Figure 3-58
Successful submission
If for any reason the deletion is unsuccessful, the reason for the failure is
brought up in a dialog box and is noted in the log window of the browser. The
submitted tuple and the failure reason along with a time stamp are stored in
the wizard.log file and the process halts. The user can return to the previous
windows, enter new data, and re-submit the tuple for deletion.
Upon successful submission, the Close button is enabled for the user to click
to close the wizard.

Add BICN Trunk Group Wizard

This wizard allows users who do not have a lot of DMS datafill experience to
datafill trunk group by entering a few entries. The following sections will give
a snapshot of the screens that the user will be prompted with to add trunk
groups from table CLLI, TRKGRP, TRKSGRP, and TRKMEM. The user has
the ability to datafill only a subset of these tables if desired. However, the
wizard does not have the ability to pick up what is configured if the user
chooses to only datafill up to the TRKGRP class.
Target node
This interface queries the user to select which DMS node the user is
interested in adding trunk group. A list of DMS nodes is available to the user
for selection. When the user selects a node, the ‘Next’ button is enabled. The
user then clicks ‘Next’ to continue with the configuration.
The check box is for a user who has already entered a default user id and
password through the main browser menu but wishes to use another user id
and password for write access to these tables. The default is not to enable this
check box. The user will still be prompted for user id and password if no
default user id and password is set or successfully logged in.
Figure 3-59
Select Target Node

If the user has not enter a user id and password to be verified on the DMS
node selected previously, or if the user wants to enter another user id and
password, this interface will be displayed. Otherwise, the interface in the next
section is displayed.
This interface queries the user for the user id and password to be verified on
the target DMS node. Once the user enters a user id and password, the ‘Next’
button is enabled. The user then clicks ‘Next’ to verify the user id/password.
If successful, the wizard will continue with the configuration. If not, a dialog
box will appear to indicate unsuccessful verification. The wizard will not
continue to the next interface until the user id/password combination is
successfully verified.
Figure 3-60
User ID Verification

Passport node name

This interface queries the user for the Passport node the user is interested in.
A list of Passport nodes is available to the user for selection. When the user
selects a node, the ‘Next’ button is enabled. The user then clicks ‘Next’ to
continue with the configuration. The user will be prompted for user id and
password.
Figure 3-61
Select Passport Node
Passport user ID verification

This interface queries the user for the user id and password to be used to
verify on the target Passport node. Once the user enters a user id and
password, the ‘Next’ button is enabled. The user then clicks ‘Next’ to verify
the user id/password. If successful, the wizard continue with the
configuration. If not, a dialog box will appear to indicate unsuccessful
verification.
Note: The wizard will not continue to the next interface until the user id/
password combination is successfully verified.

Figure 3-62
Passport User ID Verification
Add CLLI name

The user is prompted for the CLLI name. At the same time, the frame is
retrieving the CLLI names on the target node for verification and displaying
them in this frame. Before the completion of the retrieval, a working progress
indicator will be displayed at the bottom of the frame.
The ‘?’ button is displayed to allow the user to bring up on-line help on table
‘CLLI’.

Figure 3-63
Initial Add Trunk Name Screen shot
By clicking ‘Show Info...’, the list of CLLI names on the target node is
displayed. The user can use this list to determine if the name they chose has
already been used.

Figure 3-64
After clicking the ‘Show Info...’ Button
To hide the info panel that is shown, click the ‘Hide Info’ button.
When the list of CLLI is displayed and by entering a CLLI name, the wizard
will try to find the closest match to the name entered and highlight a name in
the CLLI list. The user has the option to turn off the display of the CLLI list
by clicking ‘No Info’ button. When the name is entered, the ‘Next’ button is
enabled for the user to continue on. However, if the name chosen already
exists, the wizard will pop up a dialog box indicating the problem and will not
allow the user to continue until a unique name is entered.

Figure 3-65
Typing in a CLLI Name
Add Table CLLI tuple

In this screen, the user is given the values that will be filled on table CLLI.
The user is given a chance to change the values entered. The admin number is
also changeable but is advised not to because it is a unique number that has
already been determined by the wizard. Changing the admin number does not
guarantee that the addition of the CLLI will succeed. The user is encouraged
to change the ‘reserved trunk group size’ and ‘admin info’ as needed. ‘?’
button is available for user to bring up table CLLI documentation.
At this point, the user can select the ‘Finish’ button to only datafill table CLLI
and not continue on. Refer to “Submit tuple(s)” on page 3-81, if ‘Finish’ is
selected. Be advised that the currently available wizards cannot pick up from
this point later once the wizard submits the datafill addition.
By selecting the ‘Next’ button, the wizard continues with the next trunk group
configuration.

Figure 3-66
Add Table CLLI entries
Add Table TRKGRP tuple

In this screen, the user is prompted for the trunk group type to configure. The
‘?’ button is available for user to bring up table TRKGRP documentation.
At this point, the user can select the ‘Finish’ button to only datafill up to table
CLLI and TRKGRP and not continue on. Refer to “Submit tuple(s)” on page
3-81, if ‘Finish’ is selected. Be advised that the current available wizards
cannot pick up from this point later once the wizard submits the datafill
addition.

Figure 3-67
Adding Trunk Group Type Screen shot
Based on the selection, the wizard will take the user to different screens.
• ‘GSM’ type - the wizard continues to “Add Table TRKSGRP tuple” on
page 3-77.
• ‘PET’ type - the wizard continues to “Add signalling type” on page 3-75.
Add signalling type

In this screen after the user has chosen ‘PET’ type, the user is expected to
enter the signalling type for the group. The ‘?’ button is available for user to
bring up table TRKSGRP documentation.
Figure 3-68
Signalling Type Screen shot

Add translation system and name

In the following 2 screens when the trunk group type is ‘PET’, the user is
prompted for the translation system and name. The ‘?’ button is available for
user to bring up table TRKSGRP documentation.
Figure 3-69
Translation System Screenshot
Figure 3-70
Translation Name Screenshot
Add billing destination number

In this screen when the trunk group type is ‘PET’, the user is prompted to
enter the Billing DN. The ‘?’ button is available for the user to bring up table
TRKSGRP documentation.
CLLI and TRKGRP and not continue on. Refer to “Submit tuple(s)” on page

3-81, if ‘Finish’ is selected. Be advised that the current available wizards

cannot pick up from this point later once the wizard submitted the datafill
addition.
Figure 3-71
Billing DN Screenshot
Add Table TRKSGRP tuple

In this screen, the user is prompted for the trunk subgroup number to use. The
‘?’ button is available for user to bring up table TRKSGRP documentation.
At this point if the trunk group type is not ‘PET’, the user can select the
‘Finish’ button to only datafill up to table CLLI, TRKGRP, and TRKSGRP.
Refer to “Submit tuple(s)” on page 3-81, if ‘Finish’ is selected. If the user
later decides to continue adding trunk members from the trunk group added,
the user can select the ‘Add Trunks’ or ‘Add Maintenance Trunks’ wizard to
add members.
If the group type is not ‘PET’, clicking the ‘Next’ button will direct the user
to “Passport node name” on page 3-69.

Figure 3-72
Adding Table TRKSGRP Screenshot
Add trunk protocol

In this screen when the trunk group type is ‘PET’ and the signalling type is
‘C7UP’, the user is prompted to enter the trunk protocol. The ‘?’ button is
available for the user to bring up table TRKSGRP documentation.
Figure 3-73
Trunk Protocol Screenshot
Add C7UP timer name

In this screen when the trunk group type is ‘PET’ and signalling type is
‘C7UP’, the user is prompted to enter the trunk protocol timer. The ‘?’ button
is available for the user to bring up table TRKSGRP documentation.
CLLI, TRKGRP, and TRKSGRP. Refer to “Submit tuple(s)” on page 3-81, if
‘Finish’ is selected. If the user later decides to continue adding trunk

members from the trunk group added, the user can select the ‘Add Trunk
Members’ wizard to add members.
Figure 3-74
Trunk C7UP Timer Name Screen shot
Add Table TRKMEM tuples

In this screen, the user is prompted for the MGW Id, Carrier Numbers, and
the number of timeslots to allocate the members on. The ‘?’ button is
available for the user to bring up table TRKMEM documentation.
The ‘Show Info...’ button is available to bring the list of MGW Id’s and a list
of Carrier Numbers on the selected MGW is available for use.
The ‘Number of timeslots to add:’ entry contains a list of number of available

timeslots on the selected MGW. The user should choose the number listed to
be able to advance to the next frame.
After the entries are filled, the user has the option to continue selecting other
circuit and peripheral to add members by clicking ‘Next’. This will bring up
the same interface to add additional members on a different circuit and/or
peripheral. When the user is finished with adding trunk members, the user
selects ‘Finish’ to start the tuple submission stage; the final step of the wizard.
Before the next frame can be brought up when the ‘Next’ or ‘Finish’ button is
selected, the wizard will verify the number of timeslots on the selected circuit
is available.

Figure 3-75
Add Table TRKMEM Tuples

Submit tuple(s)
In this screen, the user is given the tables that the tuples will be added. The
‘More Info...’ button is available to list the tuple(s) to be added.
Figure 3-76
Initial Submit Tuple Screenshot
By clicking the ‘Submit’ button, the wizard starts the addition of the each
tuple and displays the result of the addition. At this point, the user cannot go
back to the previous frame or cancel the wizard. When all tuples have been
submitted, the ‘Close’ button is enabled to close the wizard.
If for any reason a tuple addition is unsuccessful, the reason for the failure is
displayed in a dialog box and also noted in the log window of the browser.
The submitted tuple and the failed reason along with the time stamp are also
stored in the ‘wizard.log’ file. The wizard will not continue with the submit
operation. The user has the ability to traverse back to the window that
generates the tuple that failed and re-enter different data and submit the tuple

to the target element again. The user will not be able to traverse back beyond
the window that generates the failed tuple.
Figure 3-77
Completion of Submit Tuple

Add BICN Trunk Members Wizard

This wizard allows users who do not have a lot of DMS datafill experience to
datafill trunk group by entering a few entries. The following sections will give
a snapshot of the screens that the user will be prompted for to add trunk
member groups from table TRKMEM. The user has the ability to datafill only
a subset of these tables if desired.
Target node
This interface queries the user to select the DMS node the user is interested in
adding to a trunk group. A list of DMS nodes is available to the user for
selection. When the user selects a node, the ‘Next’ button is enabled. The user
then clicks ‘Next’ to continue with the configuration.
The check box is for user who has already entered a default user id and
password through the main browser menu but wish to use another user id and
password for write access to these tables. The default is not to enable this
check box. The user will still be prompted for user id and password if no
default user id and password is set or successfully logged in.
Figure 3-78
Select Target Node

node selected previously or wish to enter another user id and password, this
interface will be displayed. Otherwise, the interface in the next section is
displayed.
verify on the target DMS node. Once the user enters a user id and password,
the ‘Next’ button is enabled. The user then clicks ‘Next’ to verify the user id/
password. If successful, the wizard continue with the configuration. If not, a
dialog box will appear to indicate unsuccessful verification. The wizard will
not continue to the next interface until the user id/password combination is
successfully verified.
Figure 3-79

Passport node name

This interface queries the user to select the Passport node the user is interested
in. A list of Passport nodes is available to the user for selection. When the
user selects a node, the ‘Next’ button is enabled. The user then clicks ‘Next’
to continue with the configuration. The user will be prompted for user id and
password.
Figure 3-80

verification. The wizard will not continue to the next interface until the user
id/password combination is successfully verified.

Figure 3-81
Select trunk subgroup

This interface queries the target node for the list of trunk subgroups. When
the user selects a subgroup, the ‘Next’ button is enabled. The user then clicks
‘Next’ to continue with the configuration.

Figure 3-82
Select Trunk Subgroup

Add Table TRKMEM tuples

In this screen, the user is prompted for the M GW Id, Carrier Numbers, and
the number of timeslots to allocate the members on. ‘?’ button is available for
user to bring up table TRKMEM documentation.
‘Show Info...’ button is available to bring the list of MGW Id’s and a list of
Carrier Numbers on the selected MGW available for use.
‘Number of timeslots to add:’ entry contains a list of number of available

timeslots on the selected MGW. The user should choose the number listed to
be able to advance to the next frame.
circuit and peripheral to add members by clicking ‘Next’. This will bring up
the same interface to add additional members on a different circuit and/or
peripheral. When the user is finished with adding trunk members, the user
selects ‘Finish’ to start the tuple submission stage; the final step of the wizard.
Before the next frame can be brought up when the ‘Next’ or ‘Finish’ button is
selected, the wizard will verify the number of timeslots on the selected circuit
is available.

Figure 3-83
Add Table TRKMEM Tuples

Submit tuple(s)
In this screen, the user is given the tables that the tuples will be added. ‘More
Info...’ button is available to list the tuple(s) to be added.
By clicking ‘Submit’ button, the wizard starts the addition of the each tuple
and displays the result of the addition. At this point, the user cannot go back
to the previous frame or cancel the wizard. When all tuples have been
If for some reason any tuple addition is unsuccessful, the reason of the failure
is brought up in a dialog box and also noted in the log window of the browser.

Add MGW Wizard

This wizard allows user who does not have a lot of DMS datafill experience to
datafill MGW on the MSC by entering a few entries. Following will give a
snapshot of the screens that the user will be prompted for to add R4 MGW
from table GWINV.
The MGWs are provisioned within the MSC by data filling relevant
information in the table GWINV. The ‘ADD R4 MGW’ Wizard is used to
accomplish the above.
The following gives a step by step procedure to provision a MGW using the
Wizard tool (snapshots of the screens that the user will be prompted for when
adding the MGW information to the table GWINV is added here for clarity):
• Target Node - This interface queries the user which DMS node the user is
interested in adding the MGW. The user will need to select a node from
the list of DMS nodes provided by the Wizard tool.
Figure 3-84
Target Node Screenshot

• User ID Verification - This interface queries the user for the User ID and
password to be used to verify on the target DMS node.
Figure 3-85
User ID/Password Verification Screenshot
• Passport Node Name - This interface queries the user which Passport
node the user is interested in. The user needs to select from the list of
Passport nodes provided by the Wizard tool.
Figure 3-86
Passport Node Name

• Passport User ID Verification - This interface queries the user for the
user ID and password to be used to verify on the target Passport node.
Figure 3-87
• Add GWINV table tuple - The user is prompted to select the Node
Name, Node Number, MID, PROTOCOL, TRANS and INACT to datafill
a tuple in the table GWINV. The user can continue to datafill another
tuple in the table by just clicking on Next. When the user selects Finish,
the submission stage of the tuples start.

Figure 3-88
Add GWINV Table Tuple
• Submit Tuple - In this screen, the user is given the table the tuple will be
added. By clicking the Submit button, the wizard starts the addition of the
tuple(s) to the table and displays the result of the addition.
For reference and added insight provided in Table 3-5 are a couple sample
tuples for table GWINV.

Note: The data is fictitious and not based on any real customer datafill.
Table 3-5
Table GWINV Datafill
GWID MID PROTOCOL TRANS INACT MGWINFO
MGW 0 MGW_TRK1 H248 UDP 10 $
MGW 5 MGW_CNF1 H248 UDP 10 (47 103 129 60 8000)$
Delete MGW Wizard

This wizard removes datafill for MGW from the table GWINV.
The ‘Delete MGW’ wizard is used to remove the MGW datafill from table
GWINV. The following shows the sequence of screens that the user will
encounter while executing the wizard:
interested in removing MGW. A list of DMS nodes is available to the user
for selection.
Figure 3-89
Select a Target Node
Password to be sued to verify on the target DMS node.

Figure 3-90

• Remove GWINV Table Tuple - In this interface, the user is prompted to

select the GWID.
Figure 3-91
Select MGW to be removed
• Submit Tuple - In this interface, the user is given the table that the tuple
will be removed from.

Figure 3-92
Submit Tuple

BICN Audit Wizard

This wizard checks for all the inconsistencies of the MGW datafill in tables
TRKMEM and GWINV. The user selects the DMS that they want to audit
first and then needs to select a list of passport nodes. The audit will be
accurate if the user can select the list of all the passport nodes connected to
the DMS.
This wizard audits the DMS datafill against the MGW’s datafill and shows all
the inconsistencies in TRKMEM and GWINV tables. The user selects the
DMS that he wants to audit first and then need to select a list of passport
nodes. The audit will be accurate if the user can select the list of all the
passport nodes that the DMS is connected to.Following will give a snapshot
of the screens that the user will be prompted for to audit DMS BICN datafill.
The following sections will describe the sequence of frames the user will
encounter.
Target node
This interface queries the user which DMS node the user is interested in
auditing. A list of DMS nodes is available to the user for selection. When the
user selects a node, the ‘Next’ button is enabled. The user then clicks ‘Next’
to continue with the configuration.
password for write access to these tables. Default is not to enable this check
box. The user will still be prompted for user id and password if no default
user id and password is set or successfully logged in.

Figure 3-93
Select Target Node
interface will be brought up. Otherwise, the interface in the next section is
brought up. This interface queries the user for the user id and password to be
used to verify on the target DMS node. Once the user enters a user id and

Figure 3-94
Passport node name

This interface queries the user which Passport node the user is interested in. A
list of Passport nodes is available to the user for selection. When the user
selects a node, the ‘Next’ button is enabled. The user then clicks ‘Next’ to
continue with the configuration. The user will be prompted for user id and
password.

Figure 3-95

password, the ‘Next’ and ‘Finish’ buttons are enabled. Click either ‘Next’ or
‘Finish’ to verify the user id/password. If successful, the wizard continue with
the configuration. If not, a dialog box will appear to indicate unsuccessful
id/password combination is successfully verified.If successful and the user
had clicked ‘Next’, passport node name interface is displayed so that the user
can select another passport. If successful and the user had clicked ‘Finish’ the
audit interface is continued.

Figure 3-96
MGW audit
This interface audits all the MGW datafill in TRKMEM and GWINV tables.
TRKMEM table inconsistencies can be seen by clicking ‘Show trkmem
inconsistencies’ button and GWINV table inconsistencies can be seen by
clicking ‘Show GWINV inconsistencies’. The inconsistencies in these tables
mean that datafill for those tuples on DMS is not right.

Figure 3-97
MGW Audit

Add CFIWF Trunk Group Wizard

This wizard allows a user to provision CFIWF trunk groups and their
members.
The Connection fabric Interworking Function (CFIWF) allows interworking

between XPM/SPM-based trunks and MGw-based trunks. This is the case of
hybrid calls where one agency of the call is hosted by a MGw and the other
agency of the call is served by XPM/SPM on the ENET connection fabric.
The ‘Add CFIWF Trunk Group’ wizard is used to provision the CFIWF
trunks. This wizard queries the user for an XPM/SPM and a MGw to setup
CFIWF trunks. The pair trunk members are setup and then added to the table
CFIWFMAP.
The following gives a step by step procedure to provision the CFIWF trunk
groups and its members.
• Target Node - This interface displays a list of available DMS nodes to the
user.
Figure 3-98
Selecting a Target MSC

• User ID Verification - This interface queries the user for a user ID and
password that is verified on the target DMS node.
Figure 3-99
DMS Login
• Passport Node Name - This interface displays a list of available Passport

nodes to the user.
Figure 3-100
Selecting a Passport Node

• Passport User ID Verification - This interface queries the user for the
user ID and password to access the selected Passport node.
Figure 3-101
Passport Login
• Defining a CIWF CLLI - This interface prompts the user for a CLLI
name for the CIWF side.
Figure 3-102
Defining a CIWF CLLI

• Add Table CLLI Tuple (CIWF side) - In this interface, the default
values that will be added to the table CLLI is displayed. The user can
either modify them (if needed) or continue with the trunk group
configuration by clicking on the NEXT button.
Figure 3-103

• Add Table TRKGRP Tuple (CIWF side) - This interface prompts the
user to enter the trunk group type to configure. The default trunk group
for CFIWF trunks is “BICNCFIWF”.
Figure 3-104
Define Trunk Group Type
• Add Table TRKSGRP Tuple (CIWF side) - This interface prompts the
user for the trunk subgroup number to use.
Figure 3-105
Defining Trunk Subgroup Number
• Add Table TRKMEM Tuples (CIWF side) - This interface allows a

user to define TRKMEM table entries. The user selects a “Peripheral
Name” (DTC or SPM), Peripheral Number, and Circuit Number for the
trunk.

Figure 3-106
Defining Table TRKMEM entries

• Defining a MIWF CLLI - This interface prompts the user for a CLLI
name for the MIWF side.
Figure 3-107
Define MIWF CLLI
• Add Table CLLI Tuple (MIWF side) - In this interface, the default
values that will be added to the table CLLI is displayed. The user can
either modify them (if needed) or continue with the trunk group
configuration by clicking on the NEXT button.

Figure 3-108
• Add Table TRKGRP Tuple (MIWF side) - In this interface, the user is
prompted for the trunk group type to configure. The default trunk group
for CFIWF trunks is “BICNCFIWF”.
Figure 3-109
Adding Trunk Group Type

• Add Table TRKSGRP Tuple (MIWF side) - This interface prompts the
user to enter the trunk sub-group number.
Figure 3-110
Defining trunk sub-group number
• Add Table TRKMEM Tuples (MIWF side) - This interface allows the
user to define the TRKMEM table entries. The user selects a MGW name,
MGW number, Carrier Number and Number of timeslots to add.

Figure 3-111
Defining table TRKMEM entries

• Add Table CFIWFMAP Tuple - This interface allows the user to specify
the “FROM GROUP” CLLI for table CFIWFMAP. The options displayed
in the pull-down menu are the CIWF and MIWF CLLIs that the user
selected.
Figure 3-112
Configuring CFIWFMAP table tuple
• Submit Tuples - This interface displays the tables that will be modified.
By clicking the ‘Submit’ button, the wizard starts the addition of each
tuple and displays the result of the addition.

Figure 3-113
Submit Tuples display

Figure 3-114 shows the successful configuration of the CFIWF trunks.
Figure 3-114
Submitting Tuples

Figure 3-115
Completion of Submit Tuples

Given below is example CFIWF Trunk group related datafill:

Table 3-6
Table TRKGRP Datafill
GRPKEY GRPINFO
MGW0MIWF1 BICNCFIWF 0 NPDGP NCRT MIDL MIWF
MGW0CIWF1 BICNCFIWF 0 NPDGP NCRT MIDL CIWF
Table 3-7
Table TRKSGRP Datafill
SGRPKEY CARDCODE SGRPVAR
MGW0CIWF1 0 DS1SIG BICNCFIWF
MGW0MIWF1 0 DS1SIG BICNCFIWF
Table 3-8
Table TRKMEM Datafill
CLLI EXTRKNUM SGRP MEMVAR
MGW0CIWF1 1 0 DTC 1 0 1
MGW0CIWF1 2 0 DTC 1 0 2
MGW0MIWF1 1 0 MGW 0 2 1
MGW0MIWF1 2 0 MGW 0 2 2
Table 3-9
Table CFIWFMAP Datafill
FROMGRP TOGRP
MGW0CIWF1 MGW0MIWF1
Delete CFIWF Trunk Group Wizard

This wizard allows a user to delete a currently provisioned CFIWF trunk
group and its members.
Once all the migrated T1s are backed-out, the CFIWF trunks are deleted. The
‘DELETE CFIWF TRUNK GROUP’ wizard is used to delete the CFIWF trunk
groups and its members. The following describes the sequence of GUI
interfaces that the user will encounter while executing the wizard:
interested in removing the CFIWF trunks.

Figure 3-116
Selecting a Target Node
Password to be used to verify on the target node.
Figure 3-117

• Table CFIWFMAP Tuple Selection - In this interface, the user is

prompted to select a CFIWFMAP table entry.
Figure 3-118
CFIWFMAP tuple selection
• INB Prompt Message - This interface prompts the user to INB the
selected trunk group.
Figure 3-119
INB prompt message

• Submit Tuples - This interface displays the tables that will be modified.
Figure 3-120
Submit tuples display
By clicking the ‘Submit’ button, the wizard starts the deletion of each tuple
and displays the result of the action.

Figure 3-121
Completion of Submit Tuples

Migrate Trunks to MGW Wizard

The ‘Migrate Trunks To MGW’ wizard supports the migration of existing
XPM/SPM based trunks to MGW based trunks. This migration takes place in
conjunction with the physical move of carriers from the XPM or SPM to the
MGW.
An operator may select trunks to migrate by choosing one of the following

methods:
• A peripheral module and range of carriers
• A trunk group and range of members
• A range of CICs
Each of these approaches has a common set of interfaces at the beginning and
at towards the end of the migration - the interfaces common to these
approaches are explicitly indicated as such.
The step by step migration procedure is given below:
• Target Node - In this interface the user is prompted to select a DMS node.
Figure 3-122
Select a target MSC
Password that is verified on the target DMS node. Once the user enters a
User ID and Password, the ‘Next’ button is enabled. The user then clicks
‘Next’ to authenticate the User ID and Password. If successful, the wizard
continues with the provisioning. If not, a dialog box is displayed to

indicate an unsuccessful verification. The wizard will not continue to the

next interface until the user id/password combination is successfully
verified.
Figure 3-123
DMS Login
• Migration Strategy Selection - In this interface, the user is asked to

select one of the two trunk migration strategies:
— Trunk group CLLI and range of members
— Range of CICs based on routeset

Figure 3-124
Trunk Migration Strategy Selection
Note: If there are PSTN trunks and BSS trunks in a given remote market,
the PSTN trunks are migrated first, followed by the BSS trunks. This is
due to the backhaul requirements of the PSTN verses that of the Ater
interface.
• Trunk Group and Range of Members - If the user chooses to select a

trunk group and range of members, the following steps will be
encountered:
The user is asked to select a trunk group from the list of trunk group CLLIs

Figure 3-125
Select trunk group

The user is given the option to select all the members or a range of members
in the selected trunk group.
Figure 3-126
Select the trunk members
Note: When BSS trunks in a remote market is being migrated, it is

preferable to migrate T1s without signalling links. Once its migration is
successful, we then migrate T1s with signalling links. The migration of
T1s with signalling links requires some extra steps to be performed in
addition to the generic migration procedure.
• Range of CICs based on Routeset - If the user chooses to select a range

of CICs, the following steps will be encountered:
The user is asked to select a range of CICs to migrate from the list of CICs
provided by the tool after querying table C7TRKMEM.

Figure 3-127
Select the range of members
Based on the tuples retrieved from the table C7TRKMEM, identify the trunk
member CLLI + member number of each selected trunk.
• MGW Circuit Selection - In this interface, the user is asked to choose the
carrier that needs to be migrated to the desired Passport/MGW/Brag
combination. The following shows the sequence of screens that the user
will encounter.
In this screen, the user is prompted to select the carrier he wishes to migrate.

Figure 3-128
Select the carrier to be migrated

This screen below shows the TRKMEMs that will be migrated based on the
carrier selected earlier. This screen will be seen when you click on the “Show
TRKMEMs” check box.
Figure 3-129
Carrier circuits that will be migrated is displayed

In this screen, the user is asked to select the Passport to which the circuits are
to be migrated.
Figure 3-130
Select the Passport

In this screen, the user is asked to login to the Passport:
Figure 3-131
Login to the Passport
In this screen, the user is asked to select the MGW to which the circuits are to
be migrated.

Figure 3-132
Select the VSP
In this screen, the user is asked to select the brag the circuits need to be
migrated to. Please note that only the active brags on the MGW are displayed

by the wizard. The type of the brag (GSM, PET etc) is also displayed for
reference.
Figure 3-133
Select the Brag
Once the carrier and its destination Passport/MGW/brag combination is

selected, click on the ‘ADD’ button. If more carriers are to be migrated,

follow the sequence of steps shown under step 6. When done, click on the
‘NEXT’ button.
Figure 3-134
Carrier - Passport/MGW/Brag combination displayed

• Trunk Migration Approach - In this screen, the user is prompted to select

the approach by which the trunk migration needs to proceed.
Figure 3-135
Trunk Migration Approach
• Wizard Based Migration - If the wizard based migration is selected, the

user will encounter the following screenshots. This implies the migration
is being executed right away.
— BSY Trunk members - All the trunk members are busied by the user.
— INB Trunk members - The trunk members are then INBed by the
user.
Figure 3-136
INB the trunk members

— Submit Tables - In this interface, the trunk member datafill is

removed from table C7TRKMEM by the wizard. The datafill is then
modified in table TRKMEM for the trunk groups whose respective
trunk members have been removed from the table C7TRKMEM
earlier. The Wizard finally adds the original CICs back to the table
C7TRKMEM.
Note: Make sure the trunk groups are mapped correctly for a MGW
routing.
Figure 3-137
Tuples ready to be submitted (tuples not displayed)

Figure 3-138
Tuples ready to be submitted (tuples displayed)

Figure 3-139
Submitting Tuples

Figure 3-140
Submitting Tuples

Figure 3-141
Submit completed successfully

— If Wizard based Migration is in progress, please continue the

migration activity by proceeding to (step#) section •, on page 145
• DMOPRO Based Migration - The user has opted to generate the
DMOPRO files and perform the migration at a later time. [To add notes
later]. In this screen, the user will be prompted to specify filename for the
DMOPRO file to be generated.
Figure 3-142
DMOPRO based Migration

Figure 3-143
DMOPRO filename
Once the filename are specified, the DMOPRO files will be generated.

Figure 3-144
Example of DMOPRO file generated
TABLE C7TRKMEM
QUIT
TABLE TRKMEM
REP M_TEST 0 0 MGW 3 1 1
QUIT
TABLE C7TRKMEM
QUIT
Once the DMOPRO files are generated, the migration can be performed at a
later time. This DMOPRO approach was being implemented to gain time for
the migration activity during the migration window time frame. If DMOPRO
based Migration is in progress, you are done with the process of collecting the
DMOPRO files. Please do not perform any of the steps mentioned below.
• Reconfigure Physical Connections - Physical connections are moved in

the remote market to cause the traffic to be sent via OC3 into the Media
Gateway.
Note: Support need to be provided by the customer to re-arrange physical
connections.
• Bring circuits back into service - The user then brings a couple of
individual circuits into service and verifies if they function correctly on
the new packet fabric. The CIC Isolation Tool is used to test individual
circuits on the new fabric. This tool is used to verify if the migration
worked correctly. Once the individual circuits pass the basic call testing,
the user brings all the circuits into service. Once the circuits are RTSed,
please ensure they come into service at the MAP level.
Note: The CIC Isolation Tool can be used only if T1 by T1 migration is
performed. If the whole BSC is migrated (when the BSC does not support
multiple transcoders), we do not use the tool to verify if the migration is
successful.

A sample of the table C7TRKMEM and table TRKMEM datafill are shown
here for reference.
Pre-migration
Table 3-10
Table C7TRKMEM before migration
MEMKEY CIC
BSSP1CP1 1 1
BSSP1CP1 2 2
BSSP1CP1 3 3
Table 3-11
Table TRKMEM before migration
BSSP1CP 1 0 DTC 0 0 1
Post-Migration
Table 3-12
Table TRKMEM after migration
BSSP1CP 1 0 MGW 0 0 1
Table 3-13
Table C7TRKMEM after migration
MEMKEY CIC
BSSP1CP1 1 1
BSSP1CP1 2 2
BSSP1CP1 3 3

Add BICC Trunk Group Wizard

datafill trunk group by entering a few entries. The user will be prompted to
add trunk group from table CLLI, TRKGRP, TRKSGRP, ISUPDEST,
TRKOPTS and GBCIC. The user has the ability to datafill only a subset of
these tables if desired. However, the wizard does not have the ability to pick
up what is configured before if the user chooses to only datafill up to the
TRKGRP class.
encounter.
Target node
adding trunk group. A list of DMS nodes is available to the user for selection.
When the user selects a node, the ‘Next’ button is enabled. The user then
clicks ‘Next’ to continue with the configuration.
If the user has not entered a user id and password to be verified on the DMS
Add CLLI name

The user is prompted for the CLLI name. At the same time, the frame is
retrieving the CLLI names on the target node for verification and display in
this frame. Before the completion of the retrieval, a working progress
indicator will be displayed at the bottom of the frame.
‘CLLI’.

By clicking ‘Show Info...’, the list of CLLI names on the target node is
displayed. The user can use this list to determine if the name he/she chooses
has not already been used.
To hide the info panel that is shown, click the ‘Hide Info’ button.
When the list of CLLI is displayed and by entering a CLLI name, the wizard
will try to find the closest match to the name entered and highlight a name in
the CLLI list. The user has the option to turn off the display of the CLLI list
by clicking ‘No Info’ button. When the name is entered, the ‘Next’ button is
enabled for the user to continue on. However, if the name chosen already
exists, the wizard will pop up a dialog box indicating the problem and will not
allow the user to continue until a unique name is entered.
Add Table CLLI tuple

In this screen, the user is given the values that will be filled on table CLLI.
The user is given a chance to change the values entered. The admin number is
also changeable but is advised not to because it is a unique number that has
already been determined by the wizard. Changing the admin number does not
guarantee that the addition of the CLLI will succeed. The user is encouraged
to change the ‘reserved trunk group size’ and ‘admin info’ if the user find
them not of desired entry. ‘?’ button is available for user to bring up table
CLLI documentation.
By selecting the ‘Next’ button, the wizard continues with the next trunk group
configuration.
Add signalling type

In this screen, the user is expected to enter the signalling type for the group.
‘?’ button is available for user to bring up table TRKSGRP documentation.
Add translation system and name

In these screens, the user is prompted for the translation system and name. ‘?’
button is available for user to bring up table TRKSGRP documentation.
Add billing destination number

In this screen, the user is prompted to enter the Billing DN. ‘?’ button is
available for user to bring up table TRKSGRP documentation.
Add Table TRKSGRP tuple

In this screen, the user is prompted for the trunk subgroup number to use. ‘?’
button is available for user to bring up table TRKSGRP documentation.
Add trunk protocol

In this screen when signalling type is ‘C7UP’, the user is prompted to enter
the trunk protocol. ‘?’ button is available for user to bring up table TRKSGRP
documentation.

Add C7UP timer name

In this screen when the signalling type is ‘C7UP’, the user is prompted to
enter the trunk protocol timer. ‘?’ button is available for user to bring up table
TRKSGRP documentation.
Add Table ISUPDEST tuples

In this screen, the user is prompted for the C7 routeset number. ‘?’ button is
available for user to bring up table ISUPDEST documentation.
Add Table TRKOPTS tuples

In this screen, the user is prompted for the option. ‘?’ button is available for
user to bring up table TRKOPTS documentation.
Add Table GBCIC tuples

In this scree, the user is prompted for the range of CICs. “?” button is
available for the user to bring up the table GBCIC documentation.
CLLI, TRKGRP, TRKSGRP, ISUPDEST, TRKOPTS and GBCIC.
Delete BICC Trunk Group wizard

This wizard deletes BICC trunk group datafill by entering a few entries.
Following will give a snapshot of the frames that the user will be
encountering to delete a trunk group from table CLLI, TRKGRP, TRKSGRP,
TRKOPTS and GBCIC. Note the wizard does not verify the existence of the
trunk group in other tables due to the large number of tables to filter through
to find all occurrences. The following sections will describe the sequence of
frames each user will encounter.
Target node
deleting trunk group. A list of DMS nodes is available to the user for
then clicks ‘Next’ to continue with the deletion. As with the adding of trunk
group wizard, if the user has not been verified on the target DMS node, the
user id interface described in “4.1.2.2 User ID Verification” section is
displayed. By avoiding duplicating the same description here, please refer
that section for more information.
Trunk Group name query

The user is given a list of CLLI names and the user selects the CLLI name of
the trunk group to be deleted. Once selected and data retrieval has completed,
the ‘Next’ button is enabled to allow the user to advance to the next frame.
‘CLLI’.

Busy and offline prompt

The wizard requests the user to busy and offline the trunk group through other
interface if it has not been off-lined already. Only select ‘Next’ when the
trunk group has been off-lined.
Submit tuple
The user is presented with the list of tables that the wizard found to contain
the trunk group chosen. By clicking the ‘More Info...’ button displays the
table and keys to be deleted.
By clicking ‘Submit’ button, the wizard starts the deletion of the each tuple
and displays the result of the deletion. At this point, the user cannot go back
to the previous frame and cancel the wizard. When all tuples have been
If for some reason any deletion is unsuccessful, the reason of the failure is
brought up in a dialog box and also noted in the log window of the browser.
generates the tuple that failed and re-select different data and submit them to
the target element again.
Add MGWPOOL wizard

datafill MGWPOOL by entering a few entries. Following will give a snapshot
of the screens that the user will be prompted for to add media gateway pools
from table MGWPOOL. The following sections will describe the sequence of
frames the user will encounter.
Target node
adding trunk group. A list of DMS nodes is available to the user for selection.
When the user selects a node, the ‘Next’ button is enabled. The user then
clicks ‘Next’ to continue with the configuration.

C7 routeset name query

The user is given a list of C7 routeset names and the user selects the C7
routeset name to be added. Once selected and data retrieval has completed,
the ‘Next’ button is enabled to allow the user to advance to the next frame.
‘C7RTESET’.
Add Media Gateways

In this screen, the user is prompted for the Node name and MGW Id. ‘?’
button is available for user to bring up table MGWPOOLS documentation.
‘Show Info...’ button is available to bring the list of MGW Id’s available on
the selected Passport.
Media gateways to add by clicking ‘Next’. This will bring up the same
interface to add additional Media gateways. When the user is finished with
adding media gateways, the user selects ‘Finish’ to start the tuple submission
stage; the final step of the wizard.
Submit tuple(s)
In this screen, the user is given the table that the tuples will be added. ‘More
Info...’ button is available to list the tuple(s) to be added.
By clicking ‘Submit’ button, the wizard starts the addition of the each tuple
and displays the result of the addition. At this point, the user cannot go back
to the previous frame or cancel the wizard. When all tuples have been
If for some reason any tuple addition is unsuccessful, the reason of the failure

Delete MGWPOOL Wizard

datafill MGW on the MSC by entering a few entries. Following will give a
snapshot of the screens that the user will be prompted for to remove media
gateway pools from table MGWPOOL.
encounter.
Target node
removing MGWPOOL. A list of DMS nodes is available to the user for
then clicks ‘Next’ to continue with the configuration.
Remove MGWPOOL table tuple

In the following screen the user is prompted to select C7 routeset name. ‘?’
button is available for user to bring up table MGWPOOL documentation.
When the user selects C7 routeset name, the ‘finish’ button is enabled. When
the user selects ‘finish’, the submission stage of the tuple starts.
Submit tuple
In this screen, the user is given the table that the tuple will be removed form.
‘More Info...’ button is available to list the tuple to be removed.
By clicking ‘Submit’ button, the wizard starts the deletion of the tuple and
displays the result of the deletion. At this point, the user cannot go back to the
previous frame or cancel the wizard. When the tuple has been submitted, the
‘Close’ button is enabled to close the wizard.

If for some reason any tuple deletion is unsuccessful, the reason of the failure
Recovery Wizard
This wizard 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 on whether the tuple has been successfully
submitted or not. The Recovery wizard lists the created recovery files. When
a file is selected this recovery wizard will submit all the unsuccessful tuples in
that file.
In the middle of the migration procedure, if some unforeseen issue arises and
interrupts the datafill process, the ‘Recover’ wizard is used to resubmit the
datafill. This wizard recovers if any wizard failed to submit the tuples
successfully.
Whenever a wizard submits datafill changes to the DMS, a recovery file is

created will all the tuples. This file will also contain information if the tuples
were successfully submitted or not.
The Recover wizard displays a list of recover files created. The Recover
wizard provides two radio buttons: Lexicographical and Chronological. The
user can sort the "Existing Recovery Filenames" either Lexicographically
(Alphabetically) or Chronological (in order of time stamp).Once a recover file
is selected by the user, this wizard will resubmit all the unsuccessful tuples in
that recover file.
The following gives the sequence of GUI interfaces the user will encounter
while executing the Recover wizard:
• Recovery File - This interface will list all the recover files that the user
can select.

Figure 3-145
Select a file to recover
• Target User ID Verification - This interface queries the user for the User
ID and Password to be sued to verify on the target DMS node. The DMS
node or the target node is picked up from the recover file.

Figure 3-146
• Submit Tuple - In this interface, the user is given the table that the tuple
will be removed from or added to. By clicking the ‘Submit’ button, the
wizard starts add/delete of the tuple and displays the result of the addition/
deletion.

Fallback Wizard
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 of the fallback files created. When
a file is selected this wizard will submit all the fallback tuples in that file.
The Fallback wizard is used to fallback any wizard datafill after the datafill
has been submitted. During the pre-migration datafill process and migration
process, when a wizard submits datafill changes to the DMS, a fallback file is
created will all the tuples.
The Fallback wizard lists all the fallback files created. The Fallback wizard
provides two radio buttons: Lexicographical and Chronological. The user can
sort the "Existing Recovery Filenames" either Lexicographically
(Alphabetically) or Chronological (in order of time stamp). When the user
selects a fallback file, this wizard will fallback on all the tuple changes in the
fallback file.
The following sections describe the sequence of frames the user will
encounter while using the Fallback wizard.
• Fallback File - This interface will list all the fallback files that the user
can select. The user selects a file from the list.

Figure 3-147
Fallback file
• Target User ID Verification - This interface queries the user for the User
ID and Password to be used to verify on the target DMS node. The DMS
node or the target node is picked up from the fallback file.

Figure 3-148
• Submit Tuple - In this interface the user is given the table that the tuple
will be removed from or added to. By clicking on the ‘Submit’ button, the
wizard starts add/delete of the tuple and displays the result of the addition/
deletion.At this point, the user cannot cancel the fallback wizard.

Figure 3-149
Submit tuples

Figure 3-150
Submit Tuples (tuples displayed)

Figure 3-151
Fallback successfully completed
General migration fallback procedure

The Fallback wizard is used for this procedure. As mentioned earlier, the wizard
lists the fallback files created during the pre-migration datafill and migration
process. The following lists the order in which the fallback files need to be
selected to undo the migration performed earlier.
1. The user needs to BSY and INB the trunk members that were migrated
earlier for MGW routing.
2. From the list of fallback files, select the ‘Migrate_Trunks_To_MGW.dat’
file.
3. Login to the DMS or target node using User ID and password. The DMS
node is picked up from the fallback file by the wizard.
4. Click the ‘Submit’ button to revert the migration process executed earlier.
5. Bring the trunk members back into service. Initially a few individual
circuits can be brought into service and tested using the CIC Isolation

Tool. Once the basic call testing passes, all the circuits can be brought into
service. Once all the circuits are RTSed, please ensure they come into
service at the MAP level.
MDM 3
If the CEM application is configured in Server mode and an MDM is co-
resident on the CEM Server, it is possible to launch some MDM applications
from the CEM GUI. This applies to CEM when it is by itself or when it is
collocated with W-NMS.
In order for the MDM to show up in the CM panel of the CEM Browser, the
MDM needs to be configured as a CEM slice on the CEM Server. When the
user right-clicks an MDM node in the CEM Browser CM panel, a drop-down
menu appears with (node-specific) maintenance commands in the top half of
the menu, and MDM launching commands in the bottom half of the menu
(i.e. "Launch MDM toolset"). The user then selects the MDM application
they would like to launch, and the application will become available.
There are some special considerations that need to be addressed in order for
the MDM launch to work correctly:
1. The MDM applications are unix-based only. If the CEM Browser used to
launch the MDM resides on a Windows PC, then an active X-Server of
some sort is required on the PC to display the unix applications. After the
MDM application launch, the application will show up automatically in
the Xserver.
2. The CEM Server must have privileges to export a DISPLAY to the target
unix environment (X-server on PC, or the SUN workstation)
3. The DISPLAY setting of the target unix environment must be set for a
DISPLAY that ends in ":0.0".
MDM toolset launch from CEM GUI

The MDM toolset can be launched from CEM GUI when CEM is by itself or
when CEM is collocated with W-NMS. To open the MDM toolset from the
CEM Browser, right-click on any MDM switch level node icon and select
Launch MDM Toolset. See Figure 3-152.

Figure 3-152
Launch MDM Toolset
Other MDM tools can also be launched by right-clicking on any MDM

Passport switch level node (with Node attribute value equaling 137 or 138)
icon and then select Launch MDM Toolset, Launch MDM Data Viewer or
Launch MDM Nodal Provisioning.
MDM configuration tool launch from CEM GUI

The MDM configuration tool of the MDM Device Manager performs the
following functions:
• displays how the current grouping, exclusion, and re-naming data is
configured.
• modifies grouping, exclusion, and re-naming data for the MDM Device
Manager.

• loads in new configurations.
The MDM Configuration tool is launched from the main server by using the
following steps:
1. Access the server’s bin directory from the main server. For example:
/opt/nortel/data/coreEMS/nodes/server/bin
2. Set the display to sh;
3. Run ./MDMConfig to start the GUI application of the MDM Configuration
tool.
4. Edit the configuration data.
5. Save the changes. CEM will activate the new configuration within 30
seconds after it has been saved.
Note 1: A restart is not required, but the MDM Configuration tool has the
‘-restart’ command line option available to restart CEM processes when
needed.
Note 2: When changing the grouping of a Passport, active alarms will be

re-raised underneath the new configuration and the alarms underneath the
old configuration will be cleared. This same behavior applies when
Passports ares excluded from being managed by CEM and later included.
Figure 3-153 is an example of the MDM Configuration Tool for the MDM
Device Manager.

Figure 3-153
MDM Configuration Tool
In Figure 3-153, the first column (Exclude), the fourth (Group Type), the fifth
(Group Name), and the sixth (Application Type), are editable. The last
column (Active), displays whether the NE displayed is currently a MDM
managed element.
Table 3-14 lists the commands necessary to run a command line MDM
Configuration Tool.
Table 3-14
Command line MDM Configuration Tool
Command Description
./MDMConfig -listNodes [-nickName Lists all the MDM managed EM type nodes,
<nickName>] which allows excluding, including, grouping, or
renaming.
—sheet 1 of 2—

Table 3-14
Command line MDM Configuration Tool (continued)
Command Description
./MDMConfig -listCurrentData [- Lists all MDM elements which are currently

nickName <nickName>] grouped, renamed, and excluded.
./MDMConfig -exclude [-nickName Excludes a node from MDM managed nodes list.
<nickName>] <elementType>
<elementName>
./MDMConfig -include [-nickName Restates a node excluded from MDM managed

<nickName>] <elementType> nodes list.
<elementName>
./MDMConfig -merge [-nickName Adds one or more MDM elements to a group.

<nickName>] <groupType> <groupName>
<elementType1> <elementName1>
<elementType2> <elementName2>...
./MDMConfig -unmerge [-nickName Removes one or more MDM elements from a

<nickName>] <groupType> <groupName> group.
<elementType1> <elementName1>
<elementType2> <elementName2>...
./MDMConfig -rename [-nickName Renames an MDM element to its application type.

<originalElementName> <newName>
./MDMConfig -undoRename [-nickName Revokes the rename command.

<originalElementName>
./MDMConfig -restart [-noprompt] - Restarts the CEM applications once the new
nickName <nickName> entries are saved.
—sheet 2 of 2—
Use the command option [-nickName <nickName>] only when there are
multiple MDM Device Manager nodes installed on the server.
Note: Re-start the Device Manager and the Object Manager processes to
activate all configuration changes made using the above commands.
In the MDM Configuration tool, the MDM monitored nodes lists are not
guaranteed to automatically update. To ensure update of the nodes lists,
manually issue the following command:
./MDMConfig -listNodes

This command retrieves an updated MDM monitored nodes list from the
MDM Servers.
Remote MDM configuration

Configuration of CEM with a remote MDM is only supported when CEM is
collocated with W-NMS. There are two configuration methods available for
remote MDM configuration. These include automated shell scripts and
manual configuration of Unix files. Both methods require root privileges on
the remote MDM host.
Note: The remote MDM feature uses remsh. Activate this command
before launching MDM remotely.
Automated scripts
Follow Procedure 3-1 to configure automated scripts for remote MDM
launch.
Procedure 3-1
Configure automated scripts
Step Action
1 On the CEM Sun server, use the configCEMS tool to set the device type
to MDM. Enter the IP address of the remote machine running the MDM in
the Target SDM/MDM ip address field.
Note: When running the MDM on the same server as the OMC-S, enter
127.0.0.1 in the Target SDM/MDM ip address field.
2 When the configCEMS tool finishes, it generates a remoteMDMscript and

stores it at the following location:
/opt/nortel/shell/coreEMS/export/remoteMDMscripts
3 Transfer the script to the remote MDM host machine using E-mail, ftp, or
tar on to floppy.
4 Once the script is transferred, login to the remote MDM host system as
root, and cd to the directory containing the remoteMDMscripts.
5 Ensure the script has executable permissions. Enter:

chmod +x remoteMDMscripts
6 Enter:
<directory path>/remoteMDMscripts
where <directory path> equals the results from the pwd command.
7 End of procedure.

There is no generated output for a successful script execution. If problems

with the script occur, an error message appears indicating what happened.
Note: The script needs to be executed only once and can be run from any
directory the administrator chooses. /tmp is an acceptable location.
Unix file configuration

Follow Procedure 3-2 to configure unix files for manual MDM launch.
Procedure 3-2
Unix file configuration
Step Action
1 On the remote MDM machine, login as root.
2 At the end of the /etc/hosts.equiv file, add the following:

+ <hostname> nortel
where the hostname is the hostName of the CEM Server and nortel is
the user name of all Server Processes.
3 Create a user nortel if one doesn’t exist. In the home directory of user
nortel, create a file named .rhosts with the following line as content:
+ <hostname> nortel
4 On the OMC-S Server, use the configCEMS tool to set the device type to
MDM. Enter the IP address of the remote machine running the MDM in
the Target SDM/MDM ip address field.
5 When running the MDM on the same server as the OMC-S, enter
127.0.0.1 in the Target SDM/MDM ip address field.
6 To determine if the configuration was performed correctly, launch a

remsh. Enter:
remsh <remoteMDMhost>
If a shell is launched with a password prompt, the configuration was
successful.
7 End of procedure.

4-1
Fault management 4
The Fault Management (FM) function displays logs of alarm, or fault events,
that occur within the network usually within a switch node. These alarms, or
events, may have an impact on the overall service of the network element. To
aid you in correcting any problems with a network element, the Fault
Management function gives you information about the element so you can
perform further maintenance operations.
To help manage the alarms or events that occur within the network, Fault
Management provides the following capabilities:
• displays alarms for a specific switch node. When a repeated alarm occurs
for the same problem and the same resource, the most current alarm is
shown. The previous alarms are kept as cleared alarms.
• displays a time-based histogram of alarm activity for time periods of 1 to
30 day. By default, the retention period is 30 days for uncleared alarms
and 7 days for cleared alarms.
• displays alarms by alarm type (active, cleared, manual, and/or cleared
manual alarms)
• displays alarms by selected severities (Critical, Major, Minor, Warning,
unknown, information or any combination)
• displays the element color to reflect the current alarm status
• displays alarms for specific filters, and causes specific actions to happen
• provides alarm notifications as they occur within the underlying resources
• exports alarm data to file
• prints alarm data to paper
• provides filter criteria for alarms
• provides online help for alarms
• provides actions triggered by alarms

4-2 Fault management
The Element Manager may show alarms that are not shown in other systems,
such as MAPCI.
WARNING:
There is a known issue in respect to troubleshooting time
synchronization issues. Alarm information sent to either
CEM or W-NMS may not be in synchronization with what
can be found in MAPCI on the MSC.
Note: The CCA alarms generated after CEM applications start will be
displayed in the CEM GUI. After a restart of CEM applications, the
highest level of CCA alarms will be displayed as TMN600 in the CEM
GUI.
Fault management window 4

Fault management is controlled using a combination of interfaces. The switch
node to monitor is selected in the usual way in the Configuration
Management window (see Chapter 3, “Configuration management”).
The Histogram and its interface is used to control the time span of displayed
alarms.
The Alarm box is used to display the fields of the alarms to display, and the
order to display individual alarms. The Fault menu and the Fault toolbar work
together as the interface to accomplish this.
The FM window provides several ways for you to control and refine the list of
alarms displayed in the alarm list scroll box (see Figure 4-1) and the
histogram view.
Note: In the W-NMS environment, there is a Manage Alarms button on

the Fault toolbar that allows the user to change the priority of an alarm.

Figure 4-1
Fault Management window - stand-alone mode
To display a list of columns to show or hide, right-click on any heading in the

Alarm list. A check mark beside a column heading indicates it is in the
display. Click on any heading to take it out of the display.
To change the width of any column, place the arrow over the right edge of the
heading until a double-arrow appears. Then drag the edge to resize the
column.
To sort the Alarm list by any of the columns, double-click in the heading of
that column. An arrow appears showing whether it is sorted in ascending or
descending order. To change the order, double-click in the heading again.
Fault menu 4
Figure 4-2 identifies the options available in the Fault menu. The Fault menu
allows you to perform the following:
• manipulate how alarm and state information about MSC/HLR elements is
displayed
• manually acknowledge and clear alarm
• narrow down the field of which alarms to display

Figure 4-2
Fault menu
• Hide - hides or shows the FM window. A check mark in the menu

confirms hide
• Zoom in - allows you to zoom in into a histogram
• Zoom out - allows you to zoom out of the histograms selected
• Acknowledge Alarm - acknowledges the selected active alarm and enter a
free-text note for each alarm
• Clear Manual Alarm - clears all instances of a selected alarm
• Clear Manual Alarms on Node - clears manual alarms only for the
selected node
• Clear Manual Alarms on Subtree - clears manual alarms on and below the
selected node
• Clear All Alarms on Node - clears all alarms only for the selected node
• Filters and Actions - allows you to create additional filters for the display
of specific alarms and/or assign an action to the occurrence of an alarm
To access the commands of the Fault menu without the use of the mouse,
press F10.
Fault management toolbar 4

The Fault Manager toolbar contains an alarm count, buttons that allow you to
choose the types of alarms to display, buttons that allow you to choose the
level of criticality to display, buttons to choose the time period for which
alarms are displayed, and buttons that allow you to view the levels of a
network either in a textual or graphical format.
The toolbar display boxes and buttons can be grouped in seven classes.

Figure 4-3
Toolbar - stand-alone mode
Figure 4-4
Toolbar - server mode
Table 4-1
Toolbar icon descriptions
Alarms count Count of the alarms contained in the alarm

list.
Manage Allows the user to change the priority of an

alarms alarm or put the system into a maintenance
mode, delaying alarm delivery. This button
is only available in the W-NMS
environment.
Cleared Displays non-manual history alarms in the

alarms alarm list.
Active alarms Displays non-manual current alarms in the

alarm list.
Manual Displays manual history alarms in the

cleared alarm list.
alarms
—sheet 1 of 3—

Table 4-1
Manual Displays manual current alarms in the

current alarm list.
alarms
Critical Displays critical alarms in the alarm list.

alarms
Major alarms Displays major alarms in the alarm list.
Minor alarms Displays minor alarms in the alarm list.
Warning Displays warning alarms in the alarm list.

alarms
Unknown Unknown alarms occur when the true state

alarms of the equipment cannot be discovered.
Info logs Displays informational logs in the alarm list

and these logs can be manually cleared.
—sheet 2 of 3—

Table 4-1
Zoom In Zoom Zooms in into the histogram and displays

histograms and alarms for a particular day
or days (one day minimum).
Zooms out of the histogram to display

Zoom Out histograms and alarms for multiple days
(maximum of 30 days).
Selected Node Selected Displays only alarms that match the

Filter Node Filter selected component in the CM panel. If no
component is selected, no alarms are
shown instead a message is displayed in
the fault list to indicate that no alarms meet
the filter criteria.
Subtree Filter Subtree Filter Displays alarms that match the selected
component and all of its subtending
components. If no component is selected,
no alarms are shown.
Inactive Action Identifies whether actions are inactive or

active. This is a global setting to turn on or
off all actions. Individual actions can be
turned on or off from the Filters and Actions
window.
Active
—sheet 3 of 3—
The toolbar has buttons in which you can choose how to display the alarms
For example, Active alarms, Cleared alarms, Active Manual alarms, Cleared
Manual alarms in any combination or all at once.
The Severity buttons allow you to select critical, major, minor, warning, or
unknown alarm types in any combination or all at once.

The zoom in and out buttons allow you to view pre-defined histogram
information.
The selected node and subtree filter buttons affect how alarms are filtered in
relation to the selected component in the CM panel. The buttons are mutually
exclusive if one is selected the other is automatically deselected. If neither of
the buttons is selected, all the alarms for the NE or region are displayed.
These settings are remembered between the GUI sessions so the user can
select and control the alarm filtering behavior.
Note: The default when the GUI is first launched is to have no filtering
enabled so all alarms will be shown. This functionality is the same in a
CEM standalone configuration as in an NSP launched configuration.
The drop-down list works in conjunction with the Configuration Management

panel and the Filters and Actions Fault Management menu item to further refine
what alarms are displayed in the alarm list scroll box and the histogram view.
The drop-down list in the Fault Management area offers the following choices:
• Unfiltered - Selections in the Configuration view are ignored. (default)
Note: When the “Unfiltered” option is selected and no switch node is
selected, filtering is turned off. That is, the FM window will display the
alarms of all the switches. However, if a switch node (or any switch
element from any drill down level) is selected, the FM window will
display the alarms for that particular switch.
• Custom - Only alarms matching the criteria defined and enabled in the
Filters and Actions menu and the checkboxes will be displayed in the
alarm list. Drop-down box selections may be used to further refine the
alarm list. Drop-down boxes and custom filters are additive, meaning that
when “custom” is selected in the drop-down list the alarm list will be
modified by the state of the drop-down boxes and active custom filters.
Note that custom filters will have no effect on the histogram view, which
will continue to report alarms based on the status of the drop-down boxes
only.
Note: In order to display the alarms that match the criteria defined in the
Filters and Actions list, you have to either click on the element that was
specified on the criteria list or background area in the Configuration
Management area. Do not select an element other than the defined
element or alarms will not be displayed.
Note: The Fault Management function supports up to 30 days or up to

10,000 alarms (whichever comes first).

There are various ways to view alarms:

• To view only the currently active alarms, select the Alarms Active and
Manual Active buttons, and at least one severity checkbox.
• To view only the cleared alarms, select the Alarms Cleared and Manual
Cleared buttons and at least one severity checkbox.
• To view only current manual logs, select the Manual Cleared button and at
least one severity checkbox.
• To view only cleared information logs, select the Manual Cleared button
and at least one severity checkbox.
• To view current and cleared alarms and information logs, select the
Alarms Active and Cleared buttons and the Manual Active and Cleared
buttons and one or more severity checkboxes.
• To view all alarms of critical status, select the Critical button, Alarms
Active, Alarms Cleared, Manual Active, and Manual Cleared buttons.
• To view all alarms of major status, select the Major button, Alarms
• To view all alarms of minor status, select the Minor button, Alarms
• To view all alarms of warning status, select the Warning button, Alarms
• To view all alarms of information status, select the Info button, Alarms
• Any combination of status buttons can be selected simultaneously.
• The selection showing in the drop-down list window will also affect the
above combinations.
All these settings are preserved for each window when the Element Manager
is shut down and are restored when the Element Manager is restarted. Some of
the settings which are saved are:
• name of the window
• position of the windows on the screen
• size of the window
• states of the FM and CM panels
• alarm filter options
• tracking state

Histograms
The FM window contains a histogram (Figure 4-5) which gives an overview
of the selected type of alarm activity occurring in a selected period (maximum
of seven days for cleared alarms and 30 days for uncleared alarms).
The Histogram works in conjunction with the other alarm selection controls
on the FM window, including the Filter selection drop-down list box. You can
see, for example, all Critical and Major alarms which are also Active or
Cleared occurring within the selected time period for a selected node.
Figure 4-5
Histogram
Histogram time periods

There are two time periods seen in the histogram display. The first is the
Histogram view time period, and the second is the Alarm list time period.
The length of the Histogram view time period responds to the Zoom In and
Zoom Out buttons on the FM tool bar. Vertical stack bars appear, with widths
representing 15 minutes to four hours.
Arrows on the left and right-hand sides of the histogram display can be used
to select any date for viewing. A single click on the left-hand arrow moves
back one day. A single click on the right-hand arrow moves forward one day.
When the tracking button (T) on the right side of the histogram is selected, the
thumb will continuously track the current time, causing the most recent
alarms meeting criteria to be displayed in the alarm list box. Tracking only
applies to the Selected Node Filter. It is not possible to track on the Subtree
Filter as there would be too many alarms in a subtree view as it can apply to
NEs or regions.
The Selected Node Filter tracking view will automatically change the time
scale to display the time between the first and last alarm. The times are taken
from the attributes on the node that is selected. If the time range is larger than
the selected zoom setting, the zoom setting will be expanded to match the
time range. If the time range is less than the zoom setting, the zoom setting
will be left unchanged at the user specified level. For example if the setting is
at a two day view and a node is selected that has alarms that span three days,
the zoom will be changed to the next available setting of four days. If the node
selected only had alarms that spanned one day, the zoom setting is left
unchanged at the two day view.

Click in the Histogram and it displays two vertical lines, representing the
beginning and end of the Alarm list time period. Each of the lines can be
dragged to change the length of the displayed time period. The size of the
time period ranges from 15 minutes to four hours in increments of status bar
widths. If a blue background is displayed, the Element Manager is performing
resource discovery on the alarms. Wait, and when the blue disappears, the
alarms have all been found.
The Histogram header displays the time period of the Alarm list view, the
exact date and time of the Alarm list view, and the number of alarms in that
time period. The time period of the Alarm list view in the Histogram is also
the time period of the alarms appearing in the Alarm list scroll box. Also,
there is a maximum of 1000 logs per element. If alarms you are expecting are
not showing in the Alarm list, check the Histogram time period selected.
Histogram stack bars

When you make checkbox selections for the type of alarms to view, the
histogram display shows color-coded stacked bars to indicate the number of
alarms of each type which occur within the selected day.
The Histogram is not affected by the custom filters defined via the Filters and
Actions menu item. When Custom (from the choice box) is chosen, the
histogram shows the same values as if the Unfiltered choice box is chosen.
At the left-hand side of the histogram, a scale, initially calibrated at 0 - 40,

serves as an indicator of the number of alarms being represented by the
stacked bars. Each stack represents a 15 minute period. The scale
automatically re-calibrates if the maximum number of alarms to display on
any stacked bar exceeds 40.
Alarm list box display 4

Select one or more alarms in the Alarm list box and right-click while the
alarm(s) are selected. A pop-up menu will display and the user can choose a
command to perform one of the following:
• Acknowledge an alarm
• Unacknowledge an alarm
• Clear an alarm
• Find the resource (node) for an alarm
• Find and pin/unpin the resource for an alarm
• Launch an Info window for the resource corresponding to an alarm
• Launch a Help window containing information on the selected alarm

Figure 4-6
Right click on alarm
Alarm timestamps
The timestamps on the alarms are set by the objectManager with the time
when objectManager received the alarms. For the SNMP MDM nodes, the
timestamp of an alarm is propagated from the MDM server which means that
the timestamp of the alarm is the time when the MDM server received the
alarm. For the other nodes, the alarms have the CEM server time.
Not all SNMP based device use the server time zone to set the alarm timestamp.
The device exceptions are:
• BG - Border Gateway
• MLC - Location Server
• MNM - MetaSolv Network Mediation
• VPN - Contivity Virtual Private Network
The alarm timestamp for these devices will instead propagate CEM’s received
timestamp since the time zone of these devices cannot be determined. All
other SNMP devices will propagate the original alarm timestamp in the server
time zone.

Alarm list box column descriptions

The alarm list box displays information for each alarm in the columns for
each field identified in Table 4-2.
Table 4-2
Alarm list box column descriptions
Field Description
A Identifies the status of the alarm. For more information on

alarms, refer to the Alarms section of this chapter.
N Displays the note icon when a user adds an annotation or note

to the alarm.
Element Identifies the switch node of the alarm.
Resource Identifies the node element where the alarm occurred.
Date/Time Identifies the date and time the alarm occurred.
Cleared Time Identifies the time this alarm was cleared.
Acknowledged Identifies the user that acknowledged the alarm.

By
Ack Time Identifies the time the alarm was acknowledged.
Cleared By Identifies the user or the log that cleared this alarm.
Log Identifies the log that reported the alarm.
Probable Identifies the probable cause of the alarm.

Cause

Alarm status colors

A specific color identifies each alarm status (see Table 4-3). As the status of
the alarm changes in the MSC /HLR, the color of the icon changes in the
Configuration Manager and the color of the icon in the A column of the Fault
Management Alarm list box changes. Table 4-3 identifies the different alarm
statuses and colors used in the Fault and Configuration Management window.
Table 4-3
Alarm status colors
Color Definition
Gray The alarms on the element have been

cleared.
Light A condition exists and may become worse

yellow if not corrected.
Yellow A minor alarm has occurred.This type of

alarm indicates that there has been a
minor loss of system functionality. This
type of alarm does not have a major
impact on the system.
Orange A major alarm has occurred. This type of

major loss of system functionality.
Red A critical alarm has occurred.This type of

critical loss of system functionality.
Cyan The current node state is unknown,

typically due to connection loss. In this
case, the attributes on the node reflect the
last known state of the node.
White A container has nodes with no alarms and

the other nodes have a warning.
An M inside the icon indicates a manual alarm.

If any element is cyan, the following is true:
• DMS State in the information window is “disconnected”
• None of the other states will be displayed
• Information will not be displayed in info bubbles

Clearing alarms
When the system displays an alarm, you must take the appropriate action to
correct the problem. Corrective actions may require hardware or software
maintenance performed from the switch. After you correct the problem,
depending on the alarm type, the system automatically clears the alarm. If the
Fault Management window is currently in the Current view, the cleared alarm
disappears. To view the cleared alarm again, select the Cleared Alarms button
on the tool bar.
Note 1: For information on clearing alarms, refer to NTP 411-3001-543,

Base/Telecom Alarm Clearing Procedures, Volumes 1 and 2.
Note 2: To enter commands at the MAPCI interface from the Element

Manager, refer to the Using MAP section of the System Administration
chapter of this manual.
The “Clear All Alarms on Node” option is not enabled for USP, UNPM or
SLR nodes. Manual clear of active alarms for USP, UNPM and SLR
components will be ignored because USP, UNPM and SLR do not allow this
action on their devices.
Manual clears
There are some alarms that you must clear manually. The manual clear alarms
have an M over the alarm status.
To remove the problem reported by the manual clear alarm, right-click on the
alarm in the Alarm list and select the Clear Alarm command, or select the
Clear Manual Alarm option from the Fault menu (see Figure 4-2).
To clear manual alarms on a node, select a node from the Configuration

Management area then select “Clear Manual Alarms on Node” from the Fault
menu. This will only clear manual alarms on the selected node.
To clear manual alarms on a node and all the nodes below, select a node from
the Configuration Management area then select “Clear Manual Alarms on
Subtree” from the Fault menu.
To clear all alarms on a node, select a node from the Configuration

Management area then select “Clear All Alarms on Node” from the Fault
menu (see Figure 4-2). This will clear all alarms (manually and automatically
cleared) on the selected node.
Note: Automatic alarms are re-issued if they are still in effect.

Manual clear alarm display

Because of the potential of duplicate numerous alarms, measures are taken to
avoid cluttering the Alarm list while it is set to display current alarms (alarms
that have not been cleared). When a new alarm is received, the Fault Manager
assesses the new alarm by determining if it shares important information with
the existing alarms in the Alarm list. If the new alarm meets the criteria, the
existing is moved from the current category to the history category and the
new alarm is displayed in its place.
The existing alarm which is moved into the history category is considered
cleared by the new, redundant alarm. You will see the name of the alarm in the
Cleared By column.
Display Info Windows from the alarm list

Double-click an alarm in the alarm list to display an Info window (Figure 4-7)
which contains detailed information about the selected alarm. Notice that the
Info window also allows you to input your own notes about the alarm. The
OK button dismisses the window. The Save button causes the notes to be
saved before dismissing the window. The Delete button deletes the open note.
The Print button sends the full alarm text and the alarm note, if any, to the
printer. The Help button requests help on the log.

Figure 4-7
Alarm info window

Filters and Actions 4

The user-defined Custom Filters & Actions area (Figure 4-8) consists of a set
of three tabbed panes inside a single window; the Filters pane, the Actions
pane, and the Combinations pane. Each pane is selected by clicking on its title
in the tab bar at the top of the window.
Figure 4-8
Custom Filters & Actions Panel window
Filters are cumulative. When a user-defined filter is selected from the filters
list on the FM panel, it is applied only to those alarms passing any previous
filters selected directly on the FM panel. For example, if a user selected to see
only Critical alarms from the FM panel then also selected a user-defined filter
from the filter list, the alarms displayed would have to pass the Critical filter
first, then pass the named filter before being displayed in the FM panel alarm
list.
Only a single instance of the Custom Filters & Actions area can be launched
for each workstation. If the Custom Filters & Actions area is already open on
a PC, then it is accessible form any Element Manager and from the Windows
task bar.

Filters tab
The Filters tab (as shown in Figure 4-8) allows you to:
• display a list of saved filter definitions
• create new filter definitions
• modify existing filter definitions
• concatenate two or more filter definitions into a third
• delete one or more existing definitions
When a new filter is created or an existing filter is modified or deleted the

change is automatically propagated to the main FM Panel drop-down filter
list box. This list box displays the current list of filter names available to be
applied to the alarm list on the FM Panel window.
The Filters tab includes:

• Filter name field
• Filter definition field
• Status field
• a series of push-buttons used to add or change logic items in the Filter
definition field, undo or redo entries in the Filter definition field, and save
or clear the contents of the Filter definition field
• a series of drop-down list boxes may be used to select items to add to the
Filter definition field
• a multi-selection scrollable Saved filters list box containing the name and
specification of all saved filters
Filter name field

To create a new filter, enter an non-existent filter name in the Name field. To
change an existing filter definition, enter the name of the existing filter. See
the section Save button and the Name field.
Filter definition field

This field serves as the construction area for creating a new filter or
modifying an existing one. You cannot directly edit this field. Items are added
or removed using the push buttons and drop-down list boxes.
Status field
The status field displays an error message or explanation when invalid
selections are made to add to the Filter definition area.
Selection buttons
Several Selection buttons (as shown in Figure 4-8) are available to the user on
the Filters tab. These buttons are automatically enabled or disabled depending

on the text currently in the Filter definition field. If a particular button is not
currently a valid choice it is disabled and cannot be selected. These buttons
automatically re-enable themselves when their use becomes appropriate.
Parentheses “()” button

The parentheses button allows you to create filters containing logical
groupings. Parentheses can be nested to a maximum of five levels deep.
To add parentheses to a statement, first press and hold the left mouse button in
the Filter definition field and drag to select all or part of the items to be
included. It is not necessary to select entire items. Selecting part of an item
will automatically expand the parentheses to include the entire item.
A minimum of three items must be selected in the Filter definition field at

once. The selection must include at least two drop down list box selections
and one or more intervening logical operators (and, or, and not, or not). When
the mouse button is released, the parentheses button will be activated.
Pressing the parentheses button when appropriate text is selected in the Filter
definition area causes the system to insert a pair of open and closed
parentheses around the selected text.
If you choose items that are invalid selections for parentheses, an error
message appears in the status bar area explaining the problem.
Parentheses have the highest logical precedence. Logic inside parentheses

will always be evaluated before logic outside of parentheses.
The undo and redo buttons can be used to remove or re-add sets of
parentheses in a single operation.
And/Or/Not logical operator buttons

The logical operator buttons can be used to add logic to a filter. These buttons
are only enabled when their use is appropriate based on the filter definition
entered so far.
These operators follow logical rules. From highest precedence to lowest, the
rules are:
• Parentheses have the highest precedence - items within parentheses are
always evaluated first
• Logical And
• Logical Or
• Logical Not

When a logical operator or set of parentheses is added to a filter definition

validity checking is automatically performed on each drop-down list box. List
box choices which would be invalid based on the logic already defined in the
Filter definition field are disabled. When the system determines that choices
from a drop-down list box category become valid they are re-enabled. Some
examples:
• Sev=Critical AND Sev=Major is invalid because an alarm cannot be both
Critical and Major at the same time.
• Sev=Critical OR Sev=Major is a valid statement which will select all
alarms which are either of Critical severity or Major severity.
This pattern is followed for all other drop-down list boxes as well. For
example, Note=No-Note AND Note=Has-Note is invalid, etc.
The Not button may be used on its own without a preceding “and” or “or” only
if it is the first item entered in the Filter definition area. For example, the
following are valid filters:
• Not Sev=Critical
• Not (Sev=Critical And Note=Has-Note)
Statements such as:

• Sev=Critical Not Sev=Major
are invalid statements because “not” must be preceded by “and or “or” when
it is not the first item in the filter.
Undo/Redo buttons
These buttons allow you to undo or redo changes made to the Filter definition
field one at a time. The only exception to this is for parentheses - where each
set is removed in one operation. Note that the text enclosed by the parentheses
is not removed along with the parentheses. Each text item requires a separate
Undo/Redo operation of its own.
Following an undo or redo operation the contents of the Filter definition field
will be logically consistent though possibly logically incomplete. As undo
and redo actions are performed, validity checking occurs on each logical
operator button and drop-down list box item. Selections which would be
invalid (based on the contents of the Filter definition field following the undo
or redo) are disabled.
When items are added to the Filter definition field either by an Include or
Edit, they are first parsed and added one item at a time to the existing undo
and redo history. This allows a step-by-step undo of the addition just as
though it were entered by making selections.

Clear button
The clear button erases the contents of the Filter definition field, the name
field, and clears the current undo and redo histories.
Save button and the Name field

This button saves the filter currently displayed in the Filter definition field. If
the user has entered a name in the name field before the save, a prompt will
ask for verification of that name. If no name has been entered in the name
field the user will be prompted to enter a name for the filter.
Duplicate filter names are not allowed. If the selected name already exists in
the filter list, a warning message will be displayed. Changing an existing filter
definition has down-stream effects. If a combination has been defined that
contains the filter the definition of the combination will change to contain the
new filter definition. If that combination is currently active it will be
immediately deactivated.
Newly saved filters are automatically propagated to the FM Panel filter list as
well as the Combinations pane filter list. Filters are saved between Browser
sessions on a per user basis.
Drop-down list boxes

The drop-down list boxes (as shown in Figure 4-8) are where you select the
components to include in a filter. When a choice is made in any of these boxes
it is immediately appended to any text already in the Filter definition field.
A few of these list boxes can be edited to add and remove components. Any
additions or deletions made to the contents of a list box during an Element
Manager session are automatically saved on a per user basis.
Severity Box
The severity box (Figure 4-9) contains a non-editable list of all available
alarm severity choices.
Figure 4-9
Severity box

Notes box
The Notes box (Figure 4-10) contains a non-editable list of choices for Has-
Notes, No-Notes.
Figure 4-10
Notes box
Element box
The Element box (Figure 4-11) automatically determines the names of all
elements connected to the Element Browser. It automatically adds those
elements to the list of choices available in the element box list. If an element
goes off-line, that choice is automatically removed from the list.
Figure 4-11
Element box
The element box is also completely editable. Element names can be added to
the list by selecting the input area of the element box and entering a new
name. The Browser need not be connected to the element in order to add it to
the list. Elements can be deleted from the list by selecting them so that they
appear in the input area and pressing the delete key. Duplicate entries are not
allowed in the list. All changes are saved on a per user basis.

Resources box
The Resources box (Figure 4-12) contains an editable list that is initially
unpopulated. You can add or delete resources from the drop-down list.
Resources are NOT automatically added to the list by the system. Duplicate
entries are not allowed. All changes are saved on a per user basis.
Figure 4-12
Resources box
Acknowledged-by and Cleared-by boxes

These two boxes work identically (see Figure 4-13 and Figure 4-14). Both are
editable boxes which allow you to add, modify, or delete user ids from the list.
Each box also comes pre-populated with Any. When Any is added to a filter
definition, it indicates that an alarm will pass the filter if it has been cleared or
acknowledged by any user ID. This choice cannot be deleted and is always
available for selection. Changes are saved between sessions on a per user
basis.
Figure 4-13
Acknowledged-by box
Figure 4-14
Cleared-by box
Log box
The log box (Figure 4-15) is initially unpopulated. You may add specific logs
to this list as needed.
Figure 4-15
Logs box

User-defined filters list box

The user-defined filters scrollable list box contains a list of all previously
saved filter definitions created in this Element Manager workstation. Filters
created in other Element Manager windows are visible in this list.
When a single filter is selected in the list, the right-mouse button displays a
pop-up menu which allows users to edit, rename, or delete the selected filter.
See Figure 4-16.
Figure 4-16
Single-Selection Pop-Up Menu
If text exists in the Filter definition field and it is valid to do so, the Include
option will also be enabled on the pop-up menu (Figure 4-17). Selecting the
Include option causes the currently selected filter to be appended to the text in
the Filter definition field. In this way, two or more filter definitions can be
combined to create a more complex filter.

Figure 4-17
Pop-Up Menu with Include Enabled
The saved filter definition list box allows you to select two or more
contiguous (use shift-click) or non-contiguous filters from the list. A right-
mouse click on multiple selections presents a pop-up menu allowing users to
delete all the selected filters at once (Figure 4-18).
If a filter definition that is currently associated with a combination is deleted

the combination will also be deleted. A warning message gives you the
opportunity to escape.

Figure 4-18
Pop-Up Menu for Multiple Filter Selections
Actions tab
The Actions tab (Figure 4-19) is where you can define and save actions to be
performed when an alarm passes an associated filter. Actions cannot be
executed (with the exception of test) without first being associated with a
filter definition on the Combinations tab.

Figure 4-19
Actions Tab
The Actions tab consists of:

• Action Name field
• Action Text field
• Arguments field
• Multi-selection scrollable list box
• Include Alarm Radio button group
• Select, Save, Clear, and Test buttons
Action name field

This is an editable field used to display the name of the action currently in the
action definition field.
Action text field

This is a user-editable field used to define action specifications. This field
requires the full path and filename of an executable file.
Arguments field
This is a user-editable field used to define any parameters required by the
executable file specified in the Action Text field.

Select button
The select button invokes a file chooser window and dialog box which can be
used to find a file containing an executable program or command file to be
invoked by the action. Only Windows NT executable and command files are
displayed. Users can select any file of type “exe”, “cmd”, or “bat” to define an
action. Clicking the select button in the file chooser adds the selected path and
filename to the definition field on the Action tab. Clicking the Cancel button
exits without selecting an executable file.
Figure 4-20
File chooser window
Include logs radio buttons

The Include Logs buttons allow you to specify whether or not alarms should
be appended to the action statement.
Save button
This button allows users to save the action definition currently in the Action
text definition field, the name (if entered) in the name field, and the include
log choice. If no name exists in the name field users will be prompted to enter
one. If the name already exists in the saved actions list box, a dialog box
informs users that this change will be propagated to any combinations that use
this action - and DEACTIVATE those combinations immediately.
User-defined actions list box

This is a scrollable multi-selection list box containing the name, definition,
and log inclusion status of all previously saved actions.

The +Logs field contains “Y” when alarms are to be appended to the action
definition.
The Name field displays the names of all saved actions.
The Specification field displays saved action definitions.
Right-click on an action definition, and select a command in the pop-up menu

to edit, rename, test, or delete the selected action.
Figure 4-21
Single Selection Pop-Up Menu
Selecting edit in the pop-up menu causes the currently selection action to be
copied to the action definition field where it is editable by the user. The action
name is copied to the name field, and the include log choice is selected in the
radio button box. Users can change any of these items.
Selecting rename in the pop-up menu prompts the user for a new name for the
currently selected action. If the new name already exists in the action list and
is not identical to the current name, the user is warned that an action by this
name already exists. Changing an existing action definition has down-stream
effects. Changes will be propagated to any combinations using this actions,
and DEACTIVATE those combinations immediately. If the user continues,
the action will be saved under the new name, the previously saved action
using that name will be lost, and the action defined with the original name
will be removed from the list.

Selecting test from the pop-up menu copies the definition of the currently
selected item to the action definition, name, and include logs fields, executes
the action one time, and displays the detailed command string in the status
field. Currently, result codes from the Windows NT operating system are not
returned in the status field.
All saved changes to the Actions defined in the actions list are automatically
propagated to the Combinations Pane and are immediately available. Actions
are saved between Browser sessions on a per user basis.
Multi-selection pop-up menu

The saved actions list box allows multiple selections of contiguous (use shift-
click) or non-contiguous items (Figure 4-22). If multiple rows are selected a
right-mouse click in the list box will invoke a menu allowing users to delete
the selected rows. Note that edit, rename, and test are not available when
multiple actions have been selected.
Figure 4-22
Multiple-selection pop-up menu
Combinations tab
A combination represents a relationship between an action and a filter. The
Combinations tab (Figure 4-23) is used to tie filters and actions together into a
combination definition which can be invoked whenever an alarm is received
which passes the filter definition.

For this reason, if a filter or action that is used in a combination is deleted that
combination will be automatically deleted as well since it no longer defines a
valid filter/action pair.
To guard against unintended results, changed combinations are always

automatically reset to inactive status and must be manually activated by the
user. Users should take care when deleting or renaming actions and filters
because of these down-stream effects on combinations.
The Combinations tab consists of the following components:

• Combination name field
• Active radio buttons
• Repeat radio buttons
• Selected filter field and drop-down list
• Selected action field and drop-down list
• Clear button
• Save button
• Scrollable multi-selection list box of saved combinations
Figure 4-23
Combinations tab

Combination name field

You may enter a new combination name in this field. When editing a
previously saved combination this field will display the original combination
name.
Clear button
The clear button erases the contents of all the fields, except the user-defined
combination.
Saved button and the name field

The Save button saves the current combination definition. If no name was
entered in the Name field, it prompts the user to enter a name for the filter.
If the selected name already exists in the combination list, a message box
warns the user of the consequences of changing an existing combination
definition. In particular, if that combination is currently active, it will be
immediately DEACTIVATED.
All newly saved combinations are immediately visible in the combinations

tab list. Combinations are saved between Element Manager sessions on a per-
user basis.
Active radio buttons

This set of buttons is used to specify whether the combination should be
active (yes) or inactive (no).
Repeat radio buttons

These radio buttons are used to specify whether the combination should
execute each time an alarm passing the filter is received (yes), or only when
the first alarm passing the filter is received (no).
Selected filter field and drop-down list

This field is used to select a filter to associate with this combination. The
selected filter appears in the field (Figure 4-24). As filters are defined and
saved in the Filters tab, they are automatically added to this list and are
available immediately for selection. Deleted filters are immediately removed
from this list. Renamed filters are immediately renamed. This list is not user-
editable.

Figure 4-24
Selected Filter field and drop-down list

Selected action field and drop-down list

This list box is used to select an action to associate with this combination. The
selected Action list appears in this field (Figure 4-25). As actions are defined
and saved in the Actions tab they are automatically added to this list and are
available for immediate selection. Deleted actions are immediately removed
from this list. Renamed actions are immediately renamed. this list is not user-
editable.
Figure 4-25
Selected Action drop-down list
User-defined combinations list box

The user-defined combinations scrollable list box contains a list of all
previously saved combinations created in this Element Manager workstation.
Combinations created in other Element Manager windows are visible in this
list. The fields display combination name, active status, repeat status,
associated filter, and associated action.
The user-defined combinations list box allows users to select two or more
contiguous (shift-click) or non-contiguous (ctrl-click) combinations from the
list. A right-mouse click on one of these multiple selections displays a pop-up
menu. To activate, deactivate, or delete all the selected combinations at once,
select the command. The commands edit and rename are not available when
multiple actions have been selected.

Single selection pop-up menu

When only a single row has been selected in the multi-selection list box, a
right-mouse click inside the box will invoke a pop-up menu allowing users to
activate, deactivate, edit, rename, or delete the selected combination. See
Figure 4-26.
Figure 4-26
Pop-up menu when single item is selected
Selecting Activate from the pop-up menu immediately activates the selected
combination, Deactivate immediately deactivates the selected combination,
and Edit copies information from the selected combination into the editing
areas at the top of the window.
Rename causes a dialog box to appear prompting users for a new name for the
selected combination. If the new name matches a previously saved name
already in the list, users are asked if they wish to overwrite the existing entry.
If so, all data from the combination originally called by the new name is
overwritten by the data from the selected row. The entry originally selected
for rename is then removed from the list.
Selecting delete causes the selected combination to be permanently deleted.

Associated filter and action definitions are NOT deleted.

Multiple selection pop-up menu

When multiple contiguous or non-contiguous combinations are selected, a
pop-up menu can be invoked by pressing the right-mouse button inside the list
box. See Figure 4-27. For multiple selections users may activate, deactivate,
or delete the selected combinations.
Figure 4-27
Multiple-selection pop-up menu
Selecting Activate immediately activates the selected combinations,

Deactivate immediately deactivates the selected combinations, and Delete
immediately deletes the selected combinations. Actions and filters defined for
deleted combinations are NOT deleted.


5-1
Performance management 5
The Operational Measurements (OM) system provides the operating company
with the following measurements for the network elements:
• switch performance measurements
• traffic measurements
• service data
The user can view OM records to ensure that the network element operates at
its fullest potential with optimum efficiency. OM data is transferred from the
switch every transfer period, such as every 15 or 30 minutes.
Note: For more information on collected OMs, refer to the GSM/UMTS

Voice Core Network OAM Reference Manual, NTP 411-8111-803.
The Performance Management (PM) function in the Element Manager window

does the following:
• Provides capability to query and graph OM data for managed devices
• Allows the query and display of up to 32 x 8 OMs from multiple switches
in one window
• Allows exports and mass exports of OMs to files in two formats, the
original switch text format, or a tab-delimited format for use by third-
party applications such as spreadsheets or graphing utilities
• Sends the output display to printer
• Allows OM threshold settings
• Displays summary reports on a network elements
• Displays billing statistics and provides online help for OM groups and
fields (billing OMs)

5-2 Performance management
Performance management restrictions and limitations 5

1. In the Correlation editor for CEM server and standalone SDM, the
"Apply" button is used to submit newly defined correlations and
the"Delete" menu item in the right mouse button pop-up menu to delete
correlations instead of using "Save" and "Submit" buttons. The "Save"
and "Submit" buttons are disabled when any slice in GEM17 CEM server
or standalone SDM is selected. Also, any fields from multiple tuple OM
groups cannot be selected in the correlation definition.
2. In the Performance Manager window, Threshold Manager window and
OM Correlation Editor window, different colors are used to indicate that
the OM register is a correlated OM and is available for query (in blue), or
is a correlated OM but cannot be calculated (in red). Also different fonts
are used to tell user whether the OM has current data (in plain font), or has
only historical data (in italic font). These features are not available to the
following NEs:
— stand-alone NEs.
— NEs with release earlier than GEM17.1.
— logic NEs _ALL_NES_<DataType> in the Threshold Manager
window.
3. In the Dialed Digits Manager and Diagnostic Manager windows, the Info
button does not support stand-alone SDM and any NE slices represented
in GEM17.0 or earlier CEM server because the previous version of
Billing Manager, which is running on these machines, is not implemented
for the feature of the configuration GUI. The Info button is grayed out.
4. Any NE which does not have OM data stored in CEM Archive server in
the last 30 days will not be displayed in the Performance Manager
window, Threshold Manager window and OM Correlation Editor window.
5. Any OM groups or resources which do not have associated OM data
stored in CEM Archive server in the last 30 days will not be displayed in
the Performance Manager window, or Threshold Manager window.
6. The last OM report time for each NE and each data source type will not be
available if a new OM report was received in the last 3 days.
7. The availability of the easy-access graph to be brought up is dependent
upon the transfer period of the switch being known to the Element
Manager. Without the transfer period being known, the threshold values
may not be represented correctly.
8. The availability of the easy-access graph that is brought up from the Fault
Management interface is restricted so that no more than four graphs can
be opened at any given time. These include those brought up through the
Performance Manager interface.

9. Thresholds shown on the graph are the values currently set in the SDM/
FT. The history of the threshold value changes is not available.
10. Thresholds shown on the graph will not be displayed on a particular
resource, if it no longer exists.
11. Resources are not shown in the PM interfaces until data is available for
them in the Archive (for example, an OM report has arrived containing the
particular resource and its data); consequently, the list in the New Study
interface or the Threshold Manager interface may not be in-sync with the
resources listed in the Configuration Management window.
12. If the last OM report is unknown to the Element Manager, it will use the
current PC/SUN time rounded back to the nearest transfer period as the
time period to retrieve the resource list for display in the New Study
interface or the Threshold Manager interface. Typically, the timestamp of
the last OM report is only unknown to the Manager when no data is stored
in the archive.
13. Switch Format mass export does not support Billing OM groups as the
billing to OM conversion happens after dmsDataServer and Switch format
mass export occurs from Data Server. Users will not be able to export
Billing to OM (BOM) groups using Switch Format sessions, but they will
get these groups through Tab Format mass export. If a user tries to export
ALL GROUPS using Switch Format, they will be able to export DMS
Groups and not BOM groups.
14. For the Server configuration, up to 100 user-defined destination tags can
be defined at any one time in the Dialed Digits Manager.
15. For the standalone configuration, up to 30 user-defined destination tags
can be defined at any one time in the Dialed Digits Manager.
16. For the standalone configuration, up to 300 digits may be assigned, total,
within the Dialed Digits Manager. These can be in any combination of the
30 user-defined destination tags.
17. For the Server configuration, up to 500 digits may be assigned, total,
within the Dialed Digits Manager. These can be in any combination of the
100 user-defined destination tags.
18. Up to 10 user-defined diagnostic groups can be defined at any one time in
the Diagnostic Manager. This value is configurable.
19. The number of diagnostics allowed in each group is limited by the number
of diagnostics available.
20. Because the Billing Manager on the SDM/FT for the standalone
configuration, or on the server for the Server configuration, can only keep
track of one set of destination tags from any given Manager, it is advised
that one Manager input all the destination tags of interest, so as not to
overwrite another Manager’s data.

21. User defined reports cannot be performed across multi-tuple groups.

22. The USP-based NEs report an offset to GMT. Although theses NEs have
the ability to send some daylight savings time information, it is
inadequate for all time zones. Therefore, daylight savings time is not
supported for these NEs.
23. 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.
24. In the Dialed Digits Manager, both the incoming and outgoing trunk
group fields cannot be set with any combinations of “All” and “Don’t
care” in because of CPU capability. The maximum number of pairs of
incoming/outgoing trunk groups is 225 pairs for each destination tag
group.
25. There is no CDR record holding information of incoming and outgoing
trunk groups both of which are A-Interface trunk group. Therefore, if A-
Interface trunk group is set for both of incoming and outgoing trunk group
fields in Dialed Digits Manager, TRAFFICDEST3 OM group cannot
collect any data for this destination tag group.
26. If “All” is set for one of incoming or outgoing trunk group field and A-
Interface trunk group is set for the other trunk group field,
TRAFFICDEST3 OM group will miss data for A-Interface to A-Interface
calls.
27. If “Normal” for Valid CDR Types in Billing Collector and “Enhanced” for
CDR Collecting Mode in Billing Manager are configured, then IT and OT
fields in MSCBILL2 and CDRDIAG will be missed. Billing Manager in
“Enhanced” mode will not collect IT and OT data from Mobile Originated
Call and Mobile Terminated Call records.
28. If trunk groups are changed in MSC, the Trunk Configuration window
displaying trunk groups for setting for TRAFFICDEST3 needs to be
closed and re-opened in order to update a list of trunk groups.
Performance menu 5
The Performance Management (PM) section of the element manager consists
of several graphical components and screens that allow the end user to manage
a MSC/VLR or HLR.
The Performance Management (PM) menu of the OMC-S Element Manager
allows access to five applications to view the network operational
measurements (OMs). The Performance menu consists of five commands.
Figure 5-1 identifies the display options available from the Performance
menu.

Figure 5-1
Performance Menu Options
The Performance menu options are:

• Performance Manager - opens the interface that maintains the studies that
the user creates and generates the initial display of the requested study.
• Summary Report - opens the interface that lists the switches of interest in
a tree structure, displaying data from the previous day.
• Billing OM - contains a submenu with two options: Dialed Digits
Manager and Diagnostic manager.
• Threshold Manager - opens the interface that facilitates the configuration
of thresholds for OM fields and groups.
• Data Notification - opens the interface that allows you to view the data
arrival notifications from switches
• Mass Export - opens the interface that allows you to maintain the Mass
Export function
• Customizable OM Window - opens the interface that allows you to make
a selection of OM groups to be collected.
• OM Correlation Editor - opens the interface that creates or modifies
correlated OM Groups which consist of functions as fields.
Historical OMs versus current OMs 5

Different fonts are used to display the historical OM groups/resources list and
the current OM groups/resources list for any GEM17.1 or later server NEs in
the Performance Manager, Threshold Manager and OM Correlation Editor.
The historical list includes all the OM groups/resources from collected data in
last two months. The current list is defined as the list of OM groups/resources
from collected data in the current UTC day, or from collected data in the
previous UTC day if no data is collected in the current UTC day and it is
within the first hour of the current UTC day. The current groups/resources is
displayed in plain font and the rest of the list is in italic font.

Note: For nodes earlier than GEM17.1 and stand-alone NEs, the
displayed groups listed in the three windows are the groups that the user
intends to collect and the resources list contains all resources in the last
two hours from the last OM report time. In this case, all the OM groups/
resources list are displayed in plain font.
Performance Manager 5
Bring up the Performance Manager by selecting the Performance Manager
menu option from the Performance menu in the Element Manager window
(Figure 5-1).
The Performance Manager is used for the following two reasons:

• to provide a convenient way for OM data query, graphing the OM data in
display, and add/set threshold for the displayed OM. In this window, user
can query selected OMs for 30 days and display them in graph format or
in text format instantly. No need to create PM Study, nor need to select
collecting period or granularity for data query, their value will be set and
adjusted automatically by the window.
• to provide a interface for user to add/delete and edit PM Data Reports. A
Data Report is defined as follows: a data report is a set of (up to 32)
charts. A chart is a set of (up to 8) OMs. An OM is defined by
combination of a NE name, a OM group name of the NE, a measurement
field name of the group and resource name for the group if the group is a
multi-tuple group.
The Performance Manager window (Figure 5-2) consists of the following

components:
• Top Panel -- OM selection area
• Center Panel -- data display area
• Bottom Panel -- PM Data Report editing area
Note: The PM window is dynamically updated when new data comes in

and when thresholds are set.

Figure 5-2
Performance Manager menu bar

Note: All the operations in the Performance Manager window and
Performance Dashboard window can only be performed by CEM PM
users.
There are two menus on the Performance Manager menu bar:

• File - contains three menu items:
— Close - closes the Performance Manager window.
• Report

— Load Report - displays the Open Reports window where the user can
select an existing report available in the local, private and shared
folders. Shared folders can only be accessed if the user is a CEM
Administration user.
— Merge Report - displays the Merge Reports window where the user
can select an existing report available in the local, private and shared
— Save Report - displays the Save Reports window where the user can
save the report in the following: the local, private and shared folders.
Shared folders can only be accessed if the user is a CEM
— Delete Report - displays the Delete Reports window where the user
can delete a report currently available in the local, private or shared
— Set Color - displays the Customize Dashboard window where the user
can modify the color scheme and apply it to all open Dashboard
windows. Refer to “Customize the Dashboard window color scheme”
on page 5-25 for more information.
• Help - contains two menu items
— MSC OM Reference Manual - opens the Help window.
— USP OM Reference Manual - opens the Help window.
— HLR OM Reference Manual - opens the Help window.
— SLR OM Reference Manual - opens the Help window.
OM selection area
The OM selection area provides user a list of collected operational
measurement (OM) in categories for each managed network elements. The
user can use them to select their choice of OMs to query.
The OM Selection area consists of:

• Managed Element Tree: displays a tree of all available PM Managed
Network Elements (NEs).
— PM Managed NEs include: MSC, HLR and MSC/HLR switches,
HLR200 node, Passport or any re-named/grouped Passport node, SLR
node.
— An available PM Managed NE is a PM Managed NE which is visible
in CM containment tree, has established connection to PM Archive
Server and also currently has data stored in the query for the last 30
days.

• Collected OM Tree: displays OM Group names and their field names

under different categories for the selected network element. The detailed
text description for each group name or field name is displayed as a tool
tip when the cursor linger over that component.
The availableOMGroups category is displayed for each data source type

and this category contains all the group names for which the archive
server has stored data in the last 30 days. In the case of HLR200 case, two
categories named HLR are displayed: availableOMGroups and
USP:availableOMGroups.
Groups and Fields listed under the categories are colored. While blue
groups/fields means that the groups/fields are user defined, the red ones
currently cannot be queried because of some of the resources in the
definition of the fields are not available. Different fonts are used to
distinguish OMs with current data (plain font) or OMs with only
historical data (italic font). Refer to “Historical OMs versus current OMs”
on page 5-5 for additional information.
• Resources Tree: shows all the device resources associated with the
selected OM group if any.
Users can view additional details on the selected correlations in the Performance
Manager window by doing any of the following:
1. Double click on any Correlated OM fields (blue colored), a new OM
Correlation Editor Window is launched. In this window, the selected field
definition is displayed. User can view or edit the definition if needed.
2. In the OM selection Panel of Performance Manager window, when a
correlated OM is selected, the graph of the correlated OM data is
displayed in the Data display panel;
3. Right mouse click on the graph brings up a pop-up menu. In this menu, a
new sub-menu “Show Correlation” is added. Two menu items are
included in the sub-menu: “Definition” and “Related OMs”;
4. When “Definition” is selected, a new OM Correlation Editor Window is
launched and the definition of the correlation is displayed in the window;
5. When “Related OMs” is selected, a new Dashboard window is launched.
In this window, all the OMs involved in the definition are displayed is one
or more charts.
The OM data of the selected measurement is displayed in the data display

area.
Data display area

After selecting a network element name from managed element tree, a field
name from the collected OM tree and a resource name from resources tree if

any, a query is send to PM server for the selected measurement data and the
data will be displayed in the Data Display Area. The time stamp for each data
point is the start time for each transfer period.
The Data Display area consists of the following:

• Tool Bar
• Instant PM Graphing
• Time Control Bar
Tool bar
The tool bar contains icons that provide more options to control the data display:
• Graph type - by clicking on the Graph type button, the graph will be
displayed in line type.
• Bar type - by clicking on the Bar type button, the graph will be displayed
in bar type.
• Data table - by selecting Data table button, the OM data display format is
switched from graph to table.
• Print view - click on the Printer button to send the current view in the
display area to printer.
• Export Data - click on the Export Data button to save the current view to a
file locally.
• Show in Excel - click on the Show in Excel button to have the OM data
displayed in Excel where the Excel file contains the data, data displayed
in graph type and data displayed in bar type.
• Add to Chart - click on the Add To Report button to make the current OM
to be added into the selected PM report. For details on how to edit or
create a PM report, see “OM report editing area” on page 5-14.
Instant PM graphing
Instant Performance Management (PM) graphing is provided in the
Performance Manager window. By using instant PM graphing, the user can:
• query and graph the current day’s performance data by selecting an OM in
the OM selection area. The granularity of the data displayed is the transfer
interval on the network element. The time stamp for each data point is the
start time for each transfer period.
Note: Text format is also available for viewing.
• view the previous day’s performance data, by using the Forward and
Backward buttons on the graphing panel. The moving interval is one day.
The retention time for OM data stored in Archive server is configurable
(default is 30 days).

• use the Zoom In and Zoom Out buttons on the graphing panel to display
(graph or text): 1 day, 2 days, 4 days, 7 days, 14 days or 30 days of
measurements data. The granularity of the displayed OM data is
automatically adjusted when the graph zoomed in/out: for 1 day, 2 days
view, the granularity of the data is transfer-period; for 4 days, 7 days and
14 days view, the granularity of the data is set to be hourly; for 30 days
OM display, the granularity of the data is daily.
• add, set and display thresholds for the displayed OM in the same graph.
Note: The PM graph window does not support negative values for display
of threshold. All negative values are forced to zero.
• export displayed performance data to local file and send displayed

performance data to a printer.
• view short help for OM groups and fields through tool tip.
• view online help for more detailed description of OM groups and fields.
Note: The Graphing and Data Notification windows both display data
using the start time of the interval. Due to this, all data for a day has the
same date stamp.
The PM graph display can be modified by using the following items:

• data point: the user can get the data point values by moving along the plot
on the graph.
• 3-state button: the small button in the beginning the graph title has 3
states: make plot active, hide plot, and show plot. The user can switch
from state to state by clicking on the button. This is very useful when
multiple plots are displayed in the same chart.
• Threshold type and state icons: there are three threshold type icons
displayed at the end of the graph title. These icons represent the status of
ALL_NES threshold, ALL_Resources threshold and per resource
threshold.
— ALL_NES Threshold icon: if ALL_NES threshold is set on this slice
for this data type, the icon is colored. To show the ALL_NES
threshold value, click on this icon. The text on the left hand side of the
icons shows whether the threshold setting is enabled.
— ALL_Resources Threshold icon: if ALL_Resources threshold is set
on this slice for this data type, the icon is colored. To show the
ALL_Resources threshold value, click on this icon. The text on the
left hand side of the icons shows whether the threshold setting is
enabled.
— per resource Threshold icon: if per resource threshold is set on this
OM, the icon is colored. To show the threshold value, click on this

icon. The text on the left hand side of the icons shows whether the
threshold setting is enabled.
• click and drag: by clicking and dragging on the graph area, a user can get
a closer look at the data points in the area. Double clicking on the graph
will bring the graph back to the default look.
• double click on a plot: double clicking on a select plot brings up a new
window which displays only the selected plot.
• threshold alarm indication: the fact of that there is a threshold alarm
raised against the OM displayed is indicated by a colored boarder around
the graph, where the color is the same as the severity of the alarm.
• pop-up menu: the pop-up menu (Figure 5-3) provided on the graph gives
the user some very convenient ways to control the way the graph is
displayed and to manipulate thresholds. There are two different pop-up
menus: the menu when thresholds are not displayed and the menu when
thresholds are displayed. The pop-up menu is brought up by right clicking
in the graph and contains the following:
— Show Correlation: this option is only displayed when a correlated OM
is selected.
– Definition: opens the OM Correlation Editor window to display
the correlation definition.
– Related OMs: opens a Dashboard window to display the graphs of
the OMs used in the correlation.
— Options: to display the graph as data points, connected lines, in bar
type or in line type.
– Bar Chart
– Show Points
– Show Lines
Figure 5-3
Data display pop-up menu & Options submenu
— Enlarge: opens a Chart window containing only the Data Display area
from the Performance Manager window.
Note: Double clicking on the graph in the PM window will also open a
Chart window containing only the Data Display area from the PM
window.

— Goto: the main Element Manager window reappears configured to

display alarms associated with the network element selected in the
Performance Manager window.
— Threshold: (options when Thresholds are not displayed)
– Add Positive/Add Negative: to add threshold lines into the graph.
A set of enabled default threshold lines are added when one of
these menu items is selected.
A user can modify the threshold value or move the threshold lines
in two different ways. The first option is for the user to left click
on the threshold line associated with the raise threshold value,
then two small arrow icons will appear on the raise threshold value
line and on the clear threshold value line. The user can then left
click on the icons to drag the line to reset the threshold value
individually, or left click anywhere between the band and drag to
move the value of both raise and clear value together.
The second option for a user to modify the threshold value is to

double click on the threshold line associated with the raise
threshold value to bring up an input dialog window. The user then
inputs the value and clicks the OK button.
Figure 5-4
Data display pop-up menu & Threshold submenu - thresholds not displayed
— Threshold: (options when Thresholds are displayed)

– Disable: to disable the threshold setting for the OM.
– Remove: to remove the threshold setting for the OM.
– Revert: to revert the threshold value back to the original threshold
setting.
– Submit: to submit the threshold value to the PM server.

Figure 5-5
Data display pop-up menu & Threshold submenu - thresholds displayed
Time control bar

Since the data display contains the current day’s data by default, the time control
bar can be used to view previous days data, or multiple days data.
• change time interval -by clicking on the left or right arrow, the displayed
area will display previous day’s data or next day’s data.
• zoom in/out - by clicking on zoom out or zoom in icon, the display area
will display 2 days, 4 days, 7 days, 14 days and 30 days data instead of
default one day’s data. When the number of days data displayed changes,
the granularity of the data changes automatically. If one day’s data
displayed, the granularity of the displayed data is transfer interval. When
2 day’s or 4 day’s or 7 days data displayed, the granularity of the
displayed data is hourly. The granularity changes to daily when 30 days
data is displayed.
• tracking - by the “T” button on the time control bar, the display time of the
graph will be set to be the last day of OM data arrival.
OM report editing area

An OM (Operational Measurement) Report consists of a set of OM Charts
(up to 32). A OM Chart consists of a set of (up to 8) OMs, where an OM is
defined as a combination of the OM group name with an associated resource
name and a field name.
Note: All 8 measurements in a Chart can be from different NEs.
All the saved PM studies from previous releases are converted to a new PM
Report with the following changes:
• each study is converted to one new report named by study’s name.
• if the study has less than 8 OMs, then all 8 OMs will be put into one chart
named chart-0; otherwise, put the next 8 OMs into the second chart called
chart-1, and so on.

• all the start time, stop time and granularity interval information in the
study are discarded.
The Performance Manager window allows the user to:

• create a new report/template.
• edit existing reports/templates.
• apply a template to any NEs of the same type to get a new report.
• launch the PM Dashboard window to show the currently selected PM
Report/Chart in the window.
• save all the reports/templates defined. If the reports/templates are saved to
a CEM Server, then it can be shared with other CEM users.
By using the PM Data Reporting, a user can:

• display and compare performance data of multiple OMs (up to 8) in one
graph/table.
• add, set and display threshold for selected OMs in the graph.
• create/delete, edit and save a Data Report.
• view up to 32 charts/tables in one report window.
This area consists of a few components to manage and to display PM reports:

• Reports Tree Table - shows a table of defined PM reports and how they
may displayed in the PM Report window if it is launched.
— First column: shows the defined PM Reports tree. There are three
main branches in the tree. All the defined templates are displayed
under the template node and all the defined reports are under the
report node. Under each report/template node, a list of chart nodes are
displayed and all the actual measurements are shown under a chart
node.
A pop-up menu (Figure 5-6) can be invoked by selecting any tree node
of the Report Tree, then click on the right mouse button. The details of
the menu items on the pop-up menu is discussed in the following:

Figure 5-6
Report Tree Pop-up Menu
— New Report/Template/Chart menu item on the pop-up menu allows

users to create a new Report, new Template or a new Chart under the
selected node. The New Template option contains a submenu (Figure
5-7) with the following options:
– Simple Template
– Comparable Template
— Cut menu item on the pop-up menu allows users to delete the selected
report, chart or measurement.
— Rename menu item allows users to rename a report or a chart from the
given default name to a desired name.
— Copy and Paste menu item allows user to copy and paste a report or a
chart or a measurement from one branch to another.
— Show menu item on the pop-up menu allows user to show the selected
Measurement on the data display panel, or to launch a Dashboard
window displaying the selected report or chart.
• Second column: the color of the measurements in the tree shows the color
of the graph for each measurement in the Dashboard Window, if it is
launched. The color is assigned to a measurement by the GUI.
• Third Column: shows the NE name to which measurement is associated
with it. When the NE is currently in an unavailable state, text of the NE
name is displayed in light-blue color. In the case of templates, this column
shows the data type of this template.
The created data reports can be saved to the local disk as well as a private, or
shared, folder on the CEM server. Only a user in the administration group can
save to the shared directory on the server. All users can then load reports from
the shared directory.

Note: All the changes done for the PM Reports are auto-saved to the local
disk when the Performance Manager window is closed.
Alarm on threshold uses the time stamp on an arriving OM report to

determine whether the OM report is newer than the last one. OM reports that
arrive out of time sequence are ignored. When a new OM report arrives, the
time stamp on the OM report, the transfer interval on the OM report and the
time of its arrival are saved. A free running timer wakes up periodically and
compares the current time to the saved arrival time. If the difference between
the saved arrival time and the current time is greater than two times the saved
transfer interval, Alarm on Threshold deems that data is missing and raises an
alarm. The subsequent arrival of a new OM report will immediately clear the
alarm. If no new OM reports arrive for a period of 24 hours, Alarm on
Threshold deems that the NE is no longer being collected and clears all
alarms derived from the last OM report and discards its copy of the report.
Note: In the case of minor changes, such as setting the clock back several
hours, the typical behavior would be to raise a "Data Missing" alarm until
the OM reports catch up with where they left off prior to the change.
OM templates
An OM Template is a special type of abstract OM reporting, in which all the
OMs are from the same data source type and they all have an editable NE
name. If a user needs to create a similar OM report for multiple NEs, then the
user can choose to create an OM template first and then apply the template to
the multiple NEs. The limitation for the "apply operation" is that an OM with
multi-tuple groups is "blindly applied" to the user selected NE. This means
that even if the resource does not exist in the selected NE, the OM would still
apply to the NE, but no data will show when the report is displayed.
Note: This basic OM template definition is also referred to as a Simple

Template.
Comparable template
A Comparable Template provides a user with an easy way to compare OM
data from multiple network devices. A Comparable Template contains up to
32 charts and each charts only has one measurement. Applying a Comparable
template to multiple NEs (up to 8) will create a report which contains the
same number of charts as the template, but each chart contains all the OMs
obtained from applying the OM to all the NEs.
Create a new template

To create a new template, the user needs to:
1. Right click mouse button on the TEMPLATE node in the OM report Tree
of the Performance Manager window, which brings up a pop-up menu
(Figure 5-7).

Figure 5-7
Template pop-up menu
2. Select the “New Template” sub-menu, then select “Simple Template” or

“Comparable Template” menu item as the type of the new template.
3. A new template should be created and added in the bottom of the OM
report tree.
4. Select the new template node and click on the right mouse button to bring
up the pop-up menu on the node.
5. Select “Rename” menu item on the newly created report node, then type
in the report name as you wish.
6. On the same menu, selected “New Chart” menu item on this new template
node, then a new chart is added under the template. Edit the chart name as
in step 3 and 4.
7. Select this chart node and follow the above steps to add any desired
measurements for this chart.
8. After all the desired OMs are added into the template, select the template
node and click on the right mouse button to bring up the pop-up menu on
the node (Figure 5-8).
9. Select the "Apply to" menu item from the pop-up menu, the "Apply
Template" window should be launched with a list of NEs of the same
type.

Figure 5-8
Apply Template to NEs
10. Select all the NEs from the "Apply Template" window, then click the
"Apply" button.
11. A new OM Report node under the PM report tree for each NE selected
should be displayed.
12. Select the new report node just created, then select "Rename" menu item
to finish up the OM Report editing or select “Show” menu item to display
the data.
Nortel defined templates

There is a list of Nortel Defined Comparable Templates which provide a user
with capabilities to query, display and compare Performance Summary
Report data conveniently.
In the following, we list all the Nortel Defined Templates. These templates are
loaded in the OM Report Tree of Performance Manager window when the
window is initialized, they can be applied to any devices of the same type so
that desired OM report can be easily generated. Those templates are not
editable.
1. MSC_PerformanceSummary. The following OMs are in the template
(all the fields in SUMPAGE group):
— AUTHSUCR
— CPCAPUSD
— DSINUSE
— FPGSUCCR
— IERMSCHR

— LLSUCCR
— MLSUCCR
— MMSUCCR
— OERMSCHR
— PSINUSE
— RAMSCHR
— RAVLRLUR
— SERMSCHR
— SHBMSCHR
— SMMOSUCR
— SMMTSUCR
— TOTMSCHR
— TOTSUCCR
2. HLR_PerformanceSummary. The following OMs are in the template
(part of the fields in HLRSUMPAGE groups):
— ADMIN
— ATMRQ
— DISCARD
— DTMRQ
— HLRACTSSREQ
— HLRAUCERR
— HLRAUCOVLD
— HLRAUCREQ
— HLRAUCRQ
— HLRAUCTOUT
— HLRCRRPRN
— HLRDACSSREQ
— HLRERASSREQ
— HLRINTSSREQ
— HLRLURQ
— HLROCRR
— HLRREQSSREQ

— HLRFSMR
— HLRPWSSREQ
— HLRRSMDR
— HLRSMSR
— HLRULNOISD
— INTERNAL
— NETWORK
— TRERROR
— USSDRA
— USSDTB
— USSNIN
— USSNRQ
— USSRIN
— USSRRQ
Create an instant OM data query

Using Performance Manager window, a user can follow the following procedure
to create a instant OM data query:
1. In the managed element tree panel, select the NE from the tree. The
available OM categories appear in the Collected OM panel. All the groups
are currently available for query are in the CollectedOMGroups or
<sourceType>:AvailableOMGroups category.
2. Expand the selected category, the OM group names appear as the children
under the selected category.
3. Expand the selected group node in the tree, the fields for the selected
group appear under the group node and the resources for the group
appears in the Resources panel, if any.
4. Select a field for your query.
5. Select a resource for your query, if any.
6. After this point, the query is sent to PM server for the today’s data.
7. The user can use the graph control bar to query any previous day’s data or
use Tracking to query the last OM report day’s data.

Create a new OM report

By using Performance Manager window, user can follow the following
procedure to create a New OM report:
1. Select the top level node of the Report Tree; then click on the right mouse
button, a pop-up menu is invoked.
2. Select “New” menu item from pop-up menu of the “Report” node, a new
report is added into the report tree.
3. Select the new report node and click on the right mouse button to bring up
the pop-up menu on the node.
4. Select “Rename” menu item on the newly created report node, then type
in the report name as you wish.
5. On the same menu, selected “New” menu item on this new report node,
then a new chart is added under the report. Edit the chart name as in step 3
and 4.
6. Selected this chart node and follow the following step 7-12 to add any
desired measurement for this chart.
7. In the managed element tree panel, select any NE from the tree. The
collected OM categories appear in the Collected OM panel.
10. Select a field for your query.
11. Select a resource for your query, if any.
12. Click on “Add To Report” button to add the selected measurement into the
report.
13. Repeat the step 5 and step 12 until all the OMs you wish are added into a
few charts in your report.
14. Select the new report node just created, then select “Show” menu item in
the pop-up menu. A new PM Dashboard window is launched with the
report displayed.
If a user needs to create a similar OM report for multiple NEs, then follow the
steps listed under “Create a new template” on page 5-17 to create a template
first and then apply the template to multiple NEs to get multiple OM Reports
easily.

PM Dashboard window
As mentioned in the above section, a PM Report is a collection of PM Charts
(up to 32). A PM Chart contains a list of Measurements (up to 8), where a
Measurement is defined as a combination of NE name, data source type, OM
group name with an associated resource name and a field name. The PM
Dashboard window provides the user with a very flexible way to display
multiple measurements in multiple Charts in one window.
The PM Dashboard window (Figure 5-9) is launched through the

Performance Manager window. When the “Show” menu item is selected from
pop-up menu on a report or a chart, the selected report, or chart, is displayed
in a PM Dashboard window.
Figure 5-9
PM Dashboard Window
Note: The Dashboard window is dynamically updated when new data

comes in and when thresholds are set.
In the Launched Dashboard window, the following components are displayed:

• List of Display Panels (described in “Data display area” on page 5-9) are
displayed one by one in a scrollable pane. Each Display Panel
corresponds to a chart defined the given report and each displays multiple

plots corresponding to the measurements list defined in the chart. All the
functionalities described in“Data display area” on page 5-9, are available
in the Panel also.
Double clicking on any selected plot in a chart launches a window which
only displays the selected plot.
• Tool Bar: as described in “Tool bar” on page 5-10, this Tool Bar provide
controls on all the Data Display Panes in the window.
• Time Control Bar: as described in “Time control bar” on page 5-14, this
time control bar provide controls on all the data display panes in the
window. One difference here is that “Tracking” button is not available
here since it does not make sense for multiple OMs. Since the initial time
setting on the bar is current day. So all the data display panes will display
OM data for current day.
• Pop-up menu: provided on the graph, this pop-up menu (Figure 5-10)
gives the user ways to control the way the graph is displayed. The pop-up
menu is brought up by right clicking in the graph and contains the
following:
Figure 5-10
Dashboard pop-up menu
— Options: to display the graph as data points, connected lines, in bar

type or in line type.
– Bar Chart
– Show Points
– Show Lines
— Legend: opens a new window (Figure 5-11) containing measurement
names. Selecting or deselecting a measurement name makes the
measurement be displayed or hidden from the graph.

Figure 5-11
Legend window
Note: When more than one graph is displayed in the Dashboard window,
double clicking on an individual graph will open a new isolated
Dashboard window.
From the Dashboard window, users can conveniently view correlated OM

definitions and data of all the OMs involved in the definition for GEM17.1 or
later server NEs only.
1. Using the small color buttons in the top-left corner of a chart to make the
Correlated OM the active line on the chart, if there are multiple lines in
the chart.
2. Follow options 3 - 5 from “OM selection area” on page 5-8 to show
definition and related OMs data.
Customize the Dashboard window color scheme

A CEM user can pick any preferred 8 colors as a customized color scheme
and apply it to all the PM Dashboard. The customized color schema is saved
in a local file for the user and will be automatically picked up when the same
user starts CEM Performance applications later.
To customize Dashboard color scheme, user need to:

1. Open the Performance Manager window from CEM Main window.
2. Select the “Report” menu in Performance Manager window, then select
the “Set Color” menu item to bring up a “Customize Dashboard Color”
window. See Figure 5-12 and Figure 5-13.
3. Select any radio buttons to choose which color needs to be changed.
4. Select any favorite color from the color panel.
5. Click the “Save & Apply” button to save the changed color scheme and
apply it to all the open Dashboard windows.
6. To switch back to the default color schema, click the “Default Color”
button to preview it and then click the “Save & Apply” button to save the
setting;
7. To cancel any changes before saving, click the “Cancel” button.

Figure 5-12
Report menu options
Figure 5-13
Customize Dashboard Color window

Data collection 5
Data collection is consolidated into a single extendable processes which
forwards data for archival and thresholding without storing intermediate
results.
Plug-in parser capability

Data collection can be easily extended with a dynamically linked library in
order to integrate a new NE type into CEM. This library reads data from a
proprietary source/format and passes the data to the rest of the program. The
data is then sent for archival and thresholding.
This framework allows new parsers to be added easily while providing

additional features with no additional development. These features include
user-defined collection, user-defined metrics, thresholding, accumulation and
mass export.
Support for 3GPP

Each Data Collector (for Passport, USP, SLR, UNPM, GGSN, and SIG)
converts field names into 3GPP field names. In most cases, this means placing
a “VS.” in front of the field name, as most fields are vendor-specific, rather
than having been defined in a Standard.
Note: DMS OMs are not converted or displayed with 3GPP prefixes.
User-defined correlations are outside of the scope of 3GPP. If the user wishes
to see these OMs in 3GPP format, they must define the field name
appropriately.
Support for different time zones

Each data collector has a configuration file where an offset or time zone can
be configured for each NE in the data feed. These configuration files should
not be modified.
If no time zone or offset is configured, the data collector uses the time zone of
the server. All data is converted to GMT prior to storage and is displayed in
the time zone of the GUI. This includes data that is graphed and the
timestamp shown in the Data Arrival Notification window. The time that a
threshold is raised is based on the server time, but is shown in the time zone of
the GUI (as are other alarms).
In the Mass Export window, timestamps are displayed in the Server’s time
zone. The only exception is if no files have yet been exported for the session.
In this case, the Network Element View panel displays the time of the last
OM report. This time is the start time based on the PC’s time zone.

Note 1: The USP-based NEs (HLR200, SLR, UNPM) report an offset to

GMT. Although theses NEs have the ability to send some daylight savings
time information, it is inadequate for all time zones. Therefore, daylight
savings time is not supported for these NEs.
Note 2: As default, the server time zone will be used to derive the default
UTC offset for Passports. The offset is used to obtain the GMT timestamp
for Passport alarms. The Universal Time (UTC) offset can be changed if
the offset parameter in FTDM, MDM Passport Communication Manager,
service is changed. The changed UTC offset should be the same in time as
the offset for FDTM.
MDP data collector

The MDP Data Collector is integrated with Passport type discovery in Fault
Management. The end result is that Passports are organized by types in the
GUI.
When Passports are grouped in Fault Management, this information is also

reflected in the PM GUI. Passport data is collected for each shelf
independently, however, and each shelf has its own data arrival notification.
The MDP Data Collector supports filtering by group. Operators can use the
Customizable OMs window to filter or re-activate group collection for each
Passport. By default, all Passport data is collected.
Note 1: Although passport metrics do not have the concept of groups, the
DMS concept has been extended to all types of NEs managed by CEM
Performance Management. In Passports, a group is defined by a type of
subcomponent, so the “LogicalProccessor” group contains metrics from
all the Logical Processors on the Passport Shelf.
Note 2: The MDP Data Collector only collects data from MDP. No
statistical data is collected from MDM itself.
USP/SLR/UNPM/SGW data collector

The USP Data Collector supports the Customizable OMs window. All
counters are collected by default. The CEM gathers the USP/SLR/UNPM/
SGW OM reports on a periodic basis (default is 30 minutes) and stores this
data into its archive.
Although the same Data Collector collects data for USP, SLR, UNPM and
SGW NEs, the representation of this data in the GUI is different. USP data
appears as part of the HLR200 itself, whereas SLR and UNPM data is directly
under the name of the SLR or UNPM NE.

GGSN data collector

The GGSN Data Collector processes comma-separated-value (CSV) files
from the GGSN. It also supports the Customizable OMs window. All counters
are collected by default.
The GGSN Data Collector (GDC) receives files from the ASCII Data
Collector (ADC) in its incoming directory (/opt/nortel/data/coreEMS/
GGSNdata).The ADC is responsible for collecting the CSV files from the
GGSN node(s) and must be configured to deposit the GGSN CSV files into
the “/opt/nortel/data/coreEMS/GGSNdata” directory. The GDC will check
this directory once every minute and make these files immediately available
to the GDI for processing.
Any unrecognized files found in the GDC input directory is held for up to 30
minutes, after which they are removed. The typical situation for this to occur
requires a node to be added to the ADC before Fault Management operations
have discovered the node. Only nodes known to Fault Management will have
CSV files processed. Once Fault Management changes propagate to the GDC,
the files will be processed for that node. The 30 minute delay is provided to
allow for this type of configuration delay.
The default configuration of the GDC will process files at 7, 22, 37, and 52
minutes after the hour. This works for both 15 and 30 minute OM collection
intervals with a 7 minute grace period to allow the ADC complete gathering
all period related data. Although unlikely to be necessary, this timing can be
changed in the appropriate GGSN configuration file (/opt/nortel/data/
coreEMS/nodes/<Main Server name>/dataCollectorGSNS/dat/
GSNSParser.dat). Information on changing this cycle is found in the
comments of this configuration file.
SIG data collector

The SIG Data Collector processes files from the SIG, and supports the
Customizable OMs Window. All counters are collected by default.
The SDC (SIG Data Collector) receives files from the ADC in its incoming
directory (/opt/nortel/data/coreEMS/SIGdata). The ADC is responsible for
collecting the OM files from the SIG node(s) and must be configured to
deposit the SIG OM files into the “/opt/nortel/data/coreEMS/SIGdata”
directory. The SDC will check this directory once every minute and make
these files immediately available to the SDI for processing.
The ADC must be configured to append the node name at the end of the SIG
data files. This suffix is critical as this is used by the SDC to determine the
correct node to associate a data file with.

Any unrecognized files found in the SDC input directory is held for up to 30
minutes, after which they are removed. The typical situation for this to occur
requires a node to be added to the ADC before Fault Management operations
have discovered the node (only nodes known to Fault Management will have
OM files processed). Once Fault Management changes propagate to the SDC,
the files will be processed for that node. The 30 minute window is provided to
allow for this type of configuration delay.
Note: The default configuration of the SDC will process files every
minute.
There is a configuration file for the SDC at “/opt/nortel/data/coreEMS/nodes/

<Main Server name>/dataCollectorGSNS/dat/GSNSParser.dat”. This file
provides an optional UTC Offset field that provides a value, in seconds, that is
added to the time found in the OM files to convert the nodal time to UTC.
Without this, all times are taken to be local.
ArchiveAdmin tool 5
The archiveAdmin tool resides with dataProcessor in CEM server:
/opt/nortel/data/coreEMS/nodes/<slicename>/dataProcessor/bin
It provides ASCII user interface to configure export profile and to query or set
retention period of archive.
Launch ArchiveAdmin tool

A launch script, archiveAdmin.start, is in dataProcessor directory:
/opt/nortel/data/coreEMS/nodes/<slicename>/dataProcessor/bin
To launch archiveAdmin tool, use the launch script and give its slice name:
cd /opt/nortel/data/coreEMS/nodes/<slicename>/dataProcessor/
bin
./archiveAdmin.start <slicename>
Quit from ArchiveAdmin tool

At menu level, type 0 will quit from current menu.
Inside dialog, type q/Q will quit from current dialog.
ArchiveAdmin menu
ArchiveAdmin has three menus: main menu, retention setting menu and mass
export menu.

Figure 5-14
ArchiveAdmin Main Menu
ARCHIVEADMIN TOOLS
------------------------------------------
1. RETENTION PERIOD SETTING
2. SHOW/DELETE/ADD EXPORT SESSIONS
3. SET MAX NUMBER OF FILE TRANSFER
0. QUIT
Please select your choice (0-3):
Change retention period of archive

Three types of retention can be changed via archiveAdmin tool:
• change monthly retention value
• change daily retention value
• change hourly retention value
Figure 5-15
Retention setting menu
RETENTION SETTING MENU

------------------------------------------
1. MONTHLY RETENTION SETTING
2. DAILY RETENTION SETTING
3. HOURLY RETENTION SETTING
0. EXIT THIS MENU
Please select your choice (0-3):
Figure 5-16
Change Monthly Retention Value

------------------------------------------
0. EXIT THIS MENU
Please select your choice (0-3): 1
The current setting for monthly data = 3 files
Would you like to set a new retention value of monthly data now (Y/N)? [Y] y
Please enter new value ( 1 < number of files < 61 ) [Q=Quit]: 20

setArWriterAttributeReply: SET -- Set attribute value successfully
New number of files for monthly data is 20
Press <Enter> to return to RETENTION SETTING menu...

Figure 5-17
Change Daily Retention Value
------------------------------------------
0. EXIT THIS MENU
The current setting for daily data = 24 files
Would you like to set a new retention value of daily data now (Y/N)? [Y] y

New number of files for daily data is 20
Figure 5-18
Change Hourly Retention Value

------------------------------------------
0. EXIT THIS MENU
The current setting for hourly data = 4 files
Would you like to set a new retention value of hourly data now (Y/N)? [Y] y

New number of files for hourly data is 20
Mass export
The archiveAdmin tool can used to show, add, delete or modify tab mass
export profiles. It can also be used to reset exports on dataProcessor. The user
interface of adding a profile is kept the same as GEM17 or older
archiveAdmin.

Figure 5-19
Mass Export Menu
MASS EXPORT MENU
------------------------------------------
1. SHOW CURRENT EXPORT SESSIONS
2. DELETE ALL EXPORT SESSIONS
3. DELETE AN EXPORT SESSION
4. ADD AN EXPORT SESSION
5. MODIFY AN EXPORT SESSION
0. EXIT THIS MENU
Please select your choice (0-5) [Q=Quit]:
Starting in GEM17, archiveAdmin tool supports to export all groups from all
NEs. It also supports export CAP logs from DMS nodes.
Export of ACT102 and CAP logs

Mass Export Configuration has an option of exporting ACT102/CAP logs
which are emitted from the switch. These logs are generated by selecting Yes
from the Mass Export Configuration menu. ACT102/CAP logs will appear in
the beginning of the export file. These logs can be exported only if the user
selects All Groups or if the user selects the Xfer export reporting period.
Note: ACT (Activity) logs were renamed to CAP (Capacity) logs for XA-
Core switches. These logs can still be set in the OM reports and have the
same significance as the Activity logs.
ACT102/CAP logs are generated every 15 minutes after they are activated in
the switch. If the switch transfer period is 15 minutes, then you will receive
one ACT102/CAP log in the export file, two for a 30 minute transfer period
and four for a 60 minute transfer period. In order to receive the ACT102/CAP
logs along with the OM data files, these logs need to be enabled on the switch
by following the steps in Procedure 5-1.
Mass Export Configuration allows for the export of all CAP logs activated
from the MAPCI;MTC;CAPACITY level. Specifically, CAP101 log is
generated by selecting YES from the Mass Export Configuration menu. The
CAP101 log outputs all information (using three logs) in 5 minute
information blocks. Figure 5-21 provides an example of a CAP101 log report.
Procedure 5-1
Enable ACT102 and CAP Logs on the Switch
1 Login to the switch.
2 Type the following command: mapci;mtc;CAPACITY;StrtLog and press Enter.
3 Answer YES to the following question:

Do you wish for the logs to be left on after quitting? Please confirm
("YES", "Y", "NO", or "N")
4 These logs can be viewed on the switch by typing the following commands at the switch prompt
at least 30 minutes after turning on the logs:
• logutil
• open CAP
5 All the generated CAP logs (CAP100, CAP101, CAP103) will be listed.
Figure 5-20 provides an example of an ACT102 log report.
Figure 5-20
ACT102 Log Example
MSCE ACT102 FEB14 14:13:01 0590 INFO ACTIVITY_SUMMARY
Summary: Catmp/hr 0 Lorig 0 Torig 0 ToAnn 0

Cpocc 1% Conctr 0% 0AvgDel Oms 095%lim Oms
PAvgDel Oms P95%lim Oms BAvgDel 12ms B95%lim 25ms
RTrip Om Origdeny 0 Inefdeny 0 CPloovfl 0
Cpsuic 0 CPtrap 0 LCMdtsr 0% LMdtsr 0%
Figure 5-21
CAP101 Log Example
AUG16 16:53:19 2900 INFO CAPACITY_DATA
11:CATMP/HR 120000 UTIL75 ENGCATMP160000 MAXCATMP200000
COMPLEX120 ENGLEVEL BELOW CCOVRLD OFF PESC NO

Figure 5-22
Show Profiles
Please select your choice (0-5) [Q=Quit]: 1
CURRENT EXPORT PARAMETERS

Number of sessions : 2
--------------------------------------
Export Parameters for session : 1
The session name for session 1: profile2

The reporting period for session 1: SWITCH
The file format for session 1: TAB
The hours of backup for session 1: 1
The IP address for session 1: 47.104.87.55
The path for session 1: /opt/nortel/data/user/nortel/
Total number of export NEs for session 1: 3
Export Information for session 1:
Export source: BOM-MSCY
Export groups: ALL_GROUPS
Last export report: 2003/08/07 04:01
Export source: LOG-MSCY
Export groups: CAPLOGS
Export source: TRI-MSCY
ACT102/CAP LOG status: REQUIRED

The path for session 2: /opt/nortel/data/users/nortel
ACT102/CAP LOG status: NOT REQUIRED
Press <Enter> to return to MASS EXPORT menu...

Figure 5-23
Add a profile
Enter session name for session 3: [profile1] profile
Enter IP address for session 3: 47.104.87.55
You input "47.104.87.55". Is this correct (Y/N)? [Y] y
Enter Login ID for session 3: nortel
You input "nortel". Is this correct (Y/N)? [Y] y
Enter Password for session 3 (hidden):

Reenter Password:
Enter Remote directory for session 3: /opt/nortel/data/users/nortel

The directory path for session 3 is /opt/nortel/data/users/nortel
You input "/opt/nortel/data/users/nortel". Is this correct (Y/N)? [Y]
Enter the hours of backup for session 3

(0< hours of backup < 49): [1] 2
You input "2". Is this correct (Y/N)? [Y]
Enter the file format required for session 3

(2 - Tab Format, 3 - CSV Format): [2]
Would you like to export all groups in a transfer period for all NEs?
[Report period will be set to switch transfer period for EXPORT ALL] (Y/N)? [Y]
Would you like to get Capacity (ACT/CAP) logs in the export file?
[the logs should be enabled in the switch] (Y/N): [N] y
setExportReply: UPDATE -- Added export session: profile.

Figure 5-24
Delete a profile
Which session do you want to delete? (1 - 3): 3
The session name for session 3: profile

Export source: LOG-MSCY
Export groups: CAPLOGS
Last export report: <Not available>
ACT102/CAP LOG status: REQUIRED
Last export report: <Not available>
You want to delete export session 3: profile. Is this correct (Y/N)? [N] y
setExportReply: UPDATE -- delete export session: profile.

Figure 5-25
Modify a profile
Which session do you want to modify? (1 - 2): 2

ACT102/CAP LOG status: NOT REQUIRED
Enter IP address for session 2: [47.104.87.55] 47.104.87.54
You input "47.104.87.54". Is this correct (Y/N)? [Y] y
Enter Login ID for session 2: nortel

You input "nortel". Is this correct (Y/N)? [Y]
Enter Password for session 2 (hidden):

Reenter Password:
Enter Remote directory for session 2: [/opt/nortel/data/users/nortel]

The directory path for session 2 is /opt/nortel/data/users/nortel
You input "/opt/nortel/data/users/nortel". Is this correct (Y/N)? [Y]
Enter the hours of backup for session 2

(0< hours of backup < 49): [1] 2
Enter the file format required for session 2

(2 - Tab Format, 3 - CSV Format): [2] 3
Would you like to export all groups in a transfer period for all NEs?
[Report period will be set to switch transfer period for EXPORT ALL] (Y/N)?
Would you like to get Capacity (ACT/CAP) logs in the export file?
[the logs should be enabled in the switch] (Y/N): [N]
setExportReply: UPDATE -- Modified export session: profile3.

Figure 5-26
Reset Export
MASS EXPORT MENU
------------------------------------------
1. SHOW CURRENT EXPORT SESSIONS
2. DELETE ALL EXPORT SESSIONS
3. DELETE AN EXPORT SESSION
4. ADD AN EXPORT SESSION
5. MODIFY AN EXPORT SESSION
0. EXIT THIS MENU
Do you really want to DELETE ALL export sessions (Y/N)? [N] y

exportResetReply: RESET -- Remove all export sessions.
CURRENT EXPORT PARAMETERS

Number of sessions : 0
Press <Enter> to return to MASS EXPORT menu...
Change maximum number of files per transfer

The archiveAdmin tool allows user to change maximum number of files
transferred per export period.
Figure 5-27
Change Maximum number of file transfer per export period
ARCHIVEADMIN TOOLS
------------------------------------------
1. RETENTION PERIOD SETTING
2. SHOW/DELETE/ADD EXPORT SESSIONS
3. SET MAX NUMBER OF FILE TRANSFER
0. QUIT
Connect to dataProcessor, please wait ...
The current setting for number of files per transfer = 11
Would you like to set a new number of files per transfer now (Y/N)? [Y] y

setMassExportAttributeReply: SET -- Configuration file is updated!
New number of files per transfer is 12
Press <Enter> to return to MAIN menu...

OM archive backup 5
On the SDM/FT, if the logical volume containing the archive directory
becomes full, all future OM data will not be saved. To prevent filling up the
disk and losing OM data, you must manually backup and delete this data as
space becomes an issue.
To increase disk space on the SDM/FT, an archive directory can be backed up

to tape and then deleted (except for the current archive). When backing up the
archive directory to tape, backup the “archive.<version>” directory and all its
subdirectories. After the archive directory is copied to tape, the directories
and files for that archive may then be deleted. If you have a need to backup
and delete the current archive, first open a new archive in the archiveAdmin
Tool. After the new archive is created, backup and delete the previous archive
version.
Note 1: Files for Groups EXT, TRK, and VLR3 use more space than
other group files. This is due to the larger number of tuples in these
groups.
Note 2: If any user other than “maint” manually backups the archive, the
ownership and permissions of the archive need to be preserved
(permission/ownership).

Summary Report window 5

The Summary Report window (see Figure 5-28) is launched from the
performance menu of the management application. The Summary Report
window contains the performance summary specific to the switch type.
Figure 5-28
Summary Report window
The Summary Report lists the switches of interest in a tree structure. When
expanding one of these tree nodes, the switch names are displayed. When a
switch is selected, data from the previous day is retrieved and displayed in the
report area (see Figure 5-29). When a switch that is not already selected under
a report node is selected, data based on the interval and the time stamp is
retrieved. Display data of another time frame by selecting the switch and
changing the time by modifying the interval or time and clicking on the Query
button.
Note: Click the Query button only once and wait for the information to
display. You might have to wait several seconds to a few minutes.
Clicking on the Query button more than once may slow the process.

Figure 5-29
Summary Report window with switch data
The Measurement Period list box is provided to select daily interval, busy hour
and a set of interval hours which indicate from what time to what time:
• to get the daily data, input date you want in the Date text box and select
Daily (Universal Time) in the Measurement Period list box. Click the
Query button.
• to get data for Busy hour if the busy hour function is available, input date
you want in the Date text box and select BusyHr in the Measurement
Period list box. Click the Query button.
• to get data between hours, input date you want in the Date text box and
select one of intervals in the Measurement Period list box. Click the
Query button.
• the Universal Time in the Measurement Period list box means that the
date in the Date text box is based on the Coordinated Universal Time that
is Zero hours UTC is midnight in Greenwich, England. The Universal
Time is applied only for the Daily data.
• the Local Time in the Measurement Period list box means that the date in
the Date text box and the interval in the Measurement Period list box are
based on the local time of your CEM GUI machine. The Local Time is
applied for the Busy hour and the hourly interval.

If a user submits new configuration data (Group tag and its digits, or
Diagnostic tag and its codes), all other Dialed Digits Manager or Diagnostic
Manager sessions opened by other users will have their configuration data
updated automatically without invoking the refresh function. If one more user
is modifying, he will be notified for the update notification and the Managers
will not be updated automatically. The user will have options to select
whether they refresh data or keep modifying their configuration data.
A race condition occurs if two users modify and submit data at the same time,
data arriving at the Billing Manager later will be stored and the data that
arrived earlier will be wiped out. If the race condition occurs, the first arrival
will be accepted and the second arrival will be rejected. The user whose
submission is rejected will be notified of the rejection and the Managers will
not update automatically. The user will have options to select whether they
refresh data or keep modifying their configuration data.
Billing to OM GUI
The Billing to OM (BOM) GUI provides windows to edit configuration and
to display BOM statistics. There are two windows for configuration edit:
Dialed Digits Manager and Diagnostic Manager.
Dialed Digits Manager GUI and Diagnostic Manager GUI both provide an
information button represented with an “info” icon for viewing the
configurations of ombill (Billing Manager and Billing Collector). The info
window is launched by clicking the “Info” button on the Dialed Digits
Manager GUI (see Figure 5-32) or the Diagnostic Manager GUI.
Note: The Info button is only supported for CEM Server mode and is
disabled, or grayed out, in Stand-alone mode.

Figure 5-30
Info GUI for Ombill Configuration
The BOM Configuration GUI provides view functions for configuration items
of Billing Manager and Billing Collector. The GUI also shows the versions of
GSM CDR, Billing Collector and Billing Manager.
Billing to OM supports the following additional billing records: Incoming

Intra-PLMN Trunk, Outgoing Intra-PLMN Trunk, Incoming Gateway Call,
and Outgoing Gateway Call. The data obtained from the additional billing
records provides more complete and detailed statistics for Inter-MSC Trunk
traffic, as well as fully supporting the GMSC.
BOM can operate in two modes:

• first (default) mode - BOM relies on Incoming and Outgoing Intra-PLMN
Trunk records. Note that these are optional records. If the DMS is not
configured to produce these records, no data is collected for inter-MSC
traffic. This mode does not collect inter-MSC traffic from Mobile
Originated or Mobile Terminated records.
• second mode - All data is collected from Mobile Originated and
Terminated records in this mode. BOM collects some inter-MSC statistics
from Mobile Originated and Mobile Terminated records, but the
information is not complete. For BOM to operate in this mode, an SDM
configuration file must first be modified and BOM restarted.

Note: Where applicable, the average time to disconnect will be updated

only if a call is not answered. If the call is answered, average time to
answer is updated.
Billing Collector
The configuration of the valid CDR types specifies a set of CDR record types
which Billing Collector selects from an SBA billing file and sends to Billing
Managers. The Billing Collector configuration items are:
• GSM CDR version
• Billing Collector version
• Billing Collector CDR Mode: Enhanced/Normal
A set of valid CDR types defined as “Normal” Billing Collector CDR
Mode are:
— Mobile Originated Call record

— Mobile Terminated Call record
— Roaming Call record
— Short Message Service
— Mobile Originated record
A set of valid CDR types defined in “Enhanced” Billing Collector CDR

Mode are:

— Incoming Gateway Call record
— Outgoing Gateway Call record
— Incoming Intra-PLMN Trunk record
— Outgoing Intra-PLMN Trunk record
• Data Compression: ON/OFF
The Data Compression specifies whether data is compressed when Billing
Collector sends CDR records to Billing Manager. If a Billing Manager is
located on a remote node, compressing data is efficient for the
transmission. If a Billing Manager is located in the same node as a Billing
Collector is located, compressing data is not efficient. Therefore, in the

standalone mode where a Billing Manager is located in the same node, the
Data Compression is set with OFF as default. In the server mode where a
Billing Manager is located in a remote node, the Data Compression is set
with ON as default.
• Compression Buffer Size: (Integer number)

The Compression Buffer Size specifies the size of a buffer into which
compressed CDR records are stored. The size of the buffer will be
between 4096 and 1,000,000. The default size will be 65536 bytes.
• Compression Level: (Level 1 - 9)

The Compression Level specifies how data is compressed. The greater the
level is set, the more data is compressed. To compress data more takes
more CPU power. The default value will be 6.
Billing Manager
The Billing Manager configuration items are:
• Billing Manager version
• Billing Manager CDR Collecting Mode: Enhanced/Normal
The Billing Manager CDR Collecting Mode specifies how to collect

information from CDR records.
“Normal” Billing Manager CDR Collecting Mode collects data from four
CDR record types:

“Enhanced” Billing Manager CDR Collecting Mode collects data from

eight CDR record types:

— Incoming Gateway Call record
— Outgoing Gateway Call record
— Incoming Intra-PLMN Trunk record

— Outgoing Intra-PLMN Trunk record

Note: If some information is not available because the SDM is not

connected to MSC and Compression Data is OFF, it will show “Not
Available”.
Dialed Digits Manager

The Dialed Digits Manager allows you to set up a group of digits through
destination group tags. Each tag can contain more than one destination code.
Having more than one code, enables the billing manager on the SDM/CEM
server to collect reports based on each tag, rather than on individual
destination codes. The Dialed Digits Manager is launched from the
Configuration menu option in the Summary Report window.
To open the Dialed Digits Manager window, select Performance > Summary
Report > Configuration > Dialed Digits Manager in the Element Manager
window.
Note: Dialed Digits Manager can also be launched by selecting

Performance > Billing OM > Dialed Digits Manager in the Element
Manager window.
Figure 5-31
Summary Report window

Figure 5-32
Dialed Digits Manager window
After you have entered digits in the Dialed Digits Manager window and
submitted them to the Billing Manager, you can generate results in the
Destination Summary report. The Dialed Digits Manager window allows you
to add, replace or delete digits and/or group tags (see Figure 5-32). A Status/
Information box displays status and warning messages in the Dialed Digits
Manager.
Note: When the billing manager application is busy and the information
button is clicked, the following error message is displayed: “Timed out
and no reply message received. Please check the Billing Manager state.”
Call number options

The Dialed Digits Manager supports the following call number types:
• Calling Number
• Called Number

• Dialed Digits
• Forward-To Number
• Calling Number, Called Number pair
• Calling Number, Dialed Digits pair
• Calling Number, Forward-To Number pair
Note: The term “Forward-To number” is defined as the number

redirected to by making Call Forwarding (see Figure 5-33). The Forward-
To Numbers function is operated the same as the original call number
types such as Dialed Digits.
Figure 5-33
Relationship between Calling Number, Called Number and Forward-To Number
Calls Call Forwards

A B C
Calling Number Called Number Forward-to Number
The Calling-Destination numbers are selected by a check box “Destination

Numbers”. Once the check box is checked, a user can create group tags as the
Calling-Destination numbers. Dialed Digits, Calling Numbers, Called
Numbers, and Forward-To Numbers radio buttons are disabled. Once some
numbers are input in the Digits text box, the check box is disabled but a
Destination Number type can be changed by selecting radio buttons. If a user
selects Dialed Digits (or some other) radio button and enters a number in the
Digits text box, then the Destination check box is disabled.
Only one selection may be made for each destination tag. One or more
numbers are entered for the first four selections. One or more pairs of
numbers are entered for the final three selections. For each pair, both numbers
must match the CDR (AND relationship). However, the tag will be pegged if
any of the pairs match the CDR (OR relationship).
When Forward-To Number is selected, Billing to OM (BOM) checks for the

Call Forwarding Indicator on each Mobile Terminated Call record. If the
indicator is on and the number matches the Forward-To Number, BOM
collects information from this record.
The collected data is displayed on the Destination Summary window in the

Element Manager.
Note: There is a limitation on the collection of Call Forwarding statistics

on a per-trunk group basis. If the call is mobile originated and the Call

Forwarding indicator is on, the originating and terminating trunk groups

are not included in the CDR. Therefore, BOM does not collect Trunk
Group statistics for destination tags containing either a Call Forward
number, or a Calling Number, Call Forward number pair.
Prevention of Subset Digits

The Dialed Digits Manager prevents the user from entering subset digits in
the Digits text box. For example, if the tag contains the digits 972 and 9720,
and the CDR matched 9720, this CDR will not be counted twice for the tag.
If a user inputs a number which is a subset of numbers already input, the

Dialed Digits Manager does not store the number, but instead displays an
error message. If a user inputs a number whose subset number have already
been input, the Dialed Digits Manager prompts the user to select one number
and discard another.
When BOM is upgraded from a previous version, all subset numbers in a

single destination tag are removed. For example, if a tag has the numbers 972,
9720, 97212, and 97245, only 972 is retained.
Group tags
While connected to a Billing Manager, you can add (Procedure 5-2), replace
(Procedure 5-3), or delete (Procedure 5-4) a destination group.
For the standalone configuration, up to 30 user-defined destination tags can

be defined at any one time. Up to 300 digits may be assigned, total, within the
Dialed Digits Manager. These can be in any combination of the 30 user-
defined destination tags.
Note: Empty group tags will not be stored.
For Server-based configurations (such as CEM Server or W-NMS), users can

define up to 100 destination tags and up to 500 digits can be assigned within
the Dialed Digits Manager. For the Server-based solution, there is no specific
limit on the quantity of numbers in a specific destination tag, as long as the
limit across all tags is not exceeded.
To create a group tag for Calling-Destination numbers, two numbers need to

be input for Calling number and destination number. A comma is used to
separate two numbers in the Digits text box. For example, if you want 972 as
calling number and 214 as called number, then “972, 214” should be typed on
the Digits text box.

Procedure 5-2
Add a destination group
1 Enter a destination group tag in the group tag text field.
2 Press Enter or the Add button. The group tag is added to the end of the list and is highlighted.
This also allows editing of the group options and the prefixes in the digits list.
3 Check the Per Circuit-group Statistics checkbox if these statistics are desired.
4 Select the destination type from the radio button group (Dialed Digits, Calling Numbers, Called
Numbers or Forward-to-number).
5 Enter digit sets the same way you entered group tags.
6 Repeat as needed.
7 Submit changes when finished.
Procedure 5-3
Replace a destination group
1 Select a group tag to replace in the group tag list.
2 Highlight the group tag name in the group tag text field, and type the new name over it.
3 Click on the Replace button. The group tag name is overwritten with the new group tag name
5 Digit sets are replaced the same way you replaced the digits list.
Procedure 5-4
Delete a destination group
1 Select a group tag in the group tag list.
2 Click on the Delete button. The group tag and all associated digit sets are deleted.
4 Digit sets are deleted the same way you deleted the digits list, with the exception that multiple
digit sets can be selected for deletion.
When the same group tag name is input in the Group Tag text box, non-
supported characters, a duplicate number, or a subset number are input in the
Digits text box, the warning message will appear in status/information box. If
a user inputs superset number, then the dialog box will appear to prompt a
user to select either number.
Note: A group tag entered without any associated prefixes, will be

thrown out at the Billing Manager on the SDM. It will not show up when
a refresh is performed on the Dialed Digits Manager.
The Per Circuit-group Statistics checkbox will determine whether an entry is

made in the TRAFFICDEST2 billing OM group for the given group tag. This
will determine the reports available for this group tag under the Summary
Report window. If the checkbox is not checked, the Destination Circuit Group

Summary report will show no per-circuit group data for this group tag. Data
may still be available for other group tags on this machine, if this checkbox is
checked for those groups.
Please note that the list of reports is static in the Summary Report window.
Checking or un-checking the Per Circuit-group Statistics checkbox will not
alter the list of reports, only the data available within the Destination Circuit
Group Summary report.
Configuring trunks
The Dialed Digits Manager supports configuration of Incoming and Outgoing
Trunks for a group tag. The button “Configure Trunk..” supports this in
Dialed Digits Manager. The trunk configuration is used to collect the
TRAFFICDEST3 billing OM group in the Billing Manager.
TRAFFICDEST3 is collected only if the Billing Manager and Billing
Collector are in enhanced mode.
To select incoming and outgoing trunk groups for a group tag, the “Configure
Trunk..” button needs to be clicked. When the button is clicked, a new
window, “Trunk Configuration,” is displayed. This GUI has two lists:
“Incoming Trunk List” and “Outgoing Trunk List”. To select a pair of
incoming and outgoing trunks, the user needs to select one or more trunks
from each list and then click the “Select” button. When the “Select” button is
clicked, the pair appears in the “Incoming and Outgoing Trunk Pair” table.
All combinations of trunk groups selected in the Incoming Trunk list and
trunk groups selected in the Outgoing Trunk list are generated and displayed
on the Trunk Pair Table in the right hand side. If there are some pairs which
have already been in the Trunk Pair list, they will not be generated again to
avoid duplications.
Note: To select multiple trunk groups in the list use normal methods such
as Shift key, Ctrl key and dragging the mouse.
The number of selected pairs is displayed in the title of the Trunk Pair table. If
the number of pairs in the Trunk Pair list exceeds the maximum number of
pairs for one group tag, the Apply button will be disabled until the number is
reduced to the maximum number. The maximum number of pairs is 225. This
provides users a more efficient method to generate trunk group pairs.
A pair can be de-selected by selecting the pair to be removed then clicking the
“De-Select” button, or right clicking on the selected pair then selecting “De-
Select” from the pop-up menu. To apply the selected incoming and outgoing
trunk pair for the group tag, the user needs to click the “Apply” button and
this returns the user to the Dialed Digits Manager window. A similar
procedure can be done for configuring trunks for other group tags. When the
“Submit” button of Dialed Digits Manager is clicked, these settings are
reflected.

If trunk groups are changed in MSC, the Trunk Configuration GUI needs to
be closed and re-opened in order to update a list of trunk groups. If trunk
groups in destination tag groups which are already set and/or submitted do
not exist in a new list of trunk groups, the “Trunk Configuration” GUI (Figure
5-34) will inform a user to delete non-existing trunk groups from destination
tags by displaying them in the color red.
Figure 5-34
Trunk Configuration GUI
The Billing Manager will not collect any data by processing multiple CDR
records simultaneously. If the Forward-to number is set in the Dialed Digits
Manager to measure the TRAFFICDEST3 OM group for the call forwarding,
the following settings in the Dialed Digits Manager will not affect
measurement:
• Incoming trunk group and outgoing trunk group fields are set to “CLLI,”
not “Don’t Care.”
• Incoming or outgoing trunk group is set to “All”.
Note: For more information on TRAFICDEST3, refer to the section

“Performance summary report” on page 5-59.
Dialed digits
You must create a group tag before you can add digits. You can add dialed
digits for a given switch, by first selecting a Switch Name from the drop down
menu.

If there are any dialed digits for that switch they will be displayed in the area
below. To add a number, type the number in the Digits text field above the
Add, Replace and Delete buttons. After you have entered the pre-fix or
specific phone number, click on the Add button. Click on the Submit button to
accept your entry.
If you have entered anything other than what is on the phone key pad (1, 2, 3,
4, 5, 6, 7, 8, 9, 0, *, #), a dialog box will appear informing you that an invalid
entry was made.
To replace a number, click on a number in the dialed digits list. The number
will appear in the text field below the Add, Replace and Delete buttons.
Change the number by entering the new number and clicking on the Replace
button. Click on the Submit button to accept your entry. To delete a number,
highlight a number in the list. The number will appear in the text field. Click
on the Delete button. Click on the Submit button to accept your entry. The
Refresh button will return the screen to the original condition or to the point
of the last entry submitted. For example, if you added, replaced or deleted
several numbers without clicking on the Submit button, and then you clicked
on the Refresh button, anything you added, replaced or deleted would not
have taken effect. Instead the list will appear as when you first entered the
Dialed Digits Manager window.
Modified configuration data

If a user submits new configuration data (Group tag and its digits, or
Diagnostic tag and its codes), all other Dialed Digits Manager or Diagnostic
Manager opened by the other users will update configuration data
automatically without invoking the refresh function. If one more user is
modifying, he will be notified for the update notification and the Managers
will not update automatically. The user will have options to select whether to
refresh data or keep modifying the configuration data.

Figure 5-35
Update Notification for Dialed Digits Manager
Diagnostic Manager
The Diagnostic Manager allows call diagnostics to be grouped to a diagnostic
tag. Diagnostic groups already being collected can be viewed and addition,
modification, and removal of these tags can be performed. Modifying
diagnostic tags will cause inaccurate data collection on the modified data for
the daily analysis; therefore, modification is discouraged.

A diagnostic group consists of one or more diagnostics. For example, it could

be a group such as resource unavailable, which may consist of circuit
unavailable and resources unavailable, unspecified diagnostics. The diagnostics
appear as descriptions rather than diagnostic code. There are two ways to open
the Diagnostic Manager window, select:
• Performance>Summary Report>Configuration>Diagnostics Manager in
the Element Manager window.
• Performance>Billing OM>Diagnostic Manager in the Element Manager
window.
Figure 5-36
Diagnostic Manager window
Add a diagnostic tag

The Add button adds call diagnostics to a user defined diagnostic tag. The
following criteria must be met for a successful addition to occur:
• An element must be selected for the Add button to be selectable.
• A unique name must be entered for the Diagnostic Tag.
• At least one Diagnostic Code must be selected.
• A connection to the specified element must be established.
Follow the steps below to add a diagnostic tag:

1. Select a Network Element name from the Element list box.

2. Type a diagnostic name in the Diagnostic Tag text box.

3. Click the Add button to insert the name into a list box below.
4. Select the Diagnostic codes to be included in the Available Diagnostic
Codes list box.
5. Click the “<<“ button to insert them into the Selected Diagnostic Codes
list box. If you need to remove selected diagnostic codes, select the codes
in the Selected Diagnostic Codes list box and click the “>>” button.
6. Repeat step 2 to step 5 to add more diagnostic tags.
7. Click the Submit button to send the BOM server a new diagnostic
configuration.
Delete a diagnostic tag

The Delete button removes the user defined diagnostic tag and the associated
diagnostic codes. The following criteria must be satisfied for a successful
removal to occur:
• An element must be selected.
• A defined tag must be selected for the Remove button to be selectable.
Follow the steps below to delete a diagnostic tag:

2. Select a diagnostic tag to delete from the list box below the Diagnostic
Tag text box.
3. Click the Delete button.
4. Repeat step 2 to step 3 to delete more diagnostic tags.
configuration.
Rename a diagnostic tag

Follow the steps below to rename a diagnostic tag:
2. Select a diagnostic tag to rename from the list box below the Diagnostic
Tag text box.
3. Modify a name in the Diagnostic Tag text box.
4. Click the Replace button.
5. Repeat step 2 to step 4 to rename more diagnostic tags.
configuration.

Modify selections of diagnostic codes

Allows the addition and removal of diagnostic codes for a particular user
defined diagnostic tag. The following criteria must be satisfied for successful
modification to occur:
• There must be an element selected.
• There must be a defined tag selected for the Modify button to be
selectable.
• A modification to the existing data must be made for the request to be sent
to the specified element.
Follow the steps below to modify selections of diagnostic codes:

2. Select a diagnostic tag to modify from the list box below the Diagnostic
Tag text box.
3. To add more diagnostic codes, select codes in the Available Diagnostic
Codes list box and click the “<<“ button.
4. To remove diagnostic codes, select codes in the Selected Diagnostic
Codes list box and click the “>>” button.
5. Repeat step 2 to step 4 to modify more diagnostic tags.
configuration.
Submit diagnostic configurations

The Submit button submits all configurations for the selected Network
Element on the GUI to the BOM server.
Refresh diagnostic configurations

The Refresh button reverts the diagnostic configuration for the selected
Network Element back to the last submitted configuration. The last submitted
configuration may be one other operator submitted.
The following criteria must be met for a successful refresh to occur:

• An element must be selected for the Refresh button to be selectable.
Close Diagnostic Manager

The Close button closes the Diagnostic Manager without submitting data. If
some data was added or modified, a dialog box will appear to confirm that the
user wants to close the Diagnostic Manager.

Status/Information Box
The Status/Information Box informs the user about success/failure of submit,
warning invalid input, etc.
Note: When the billing manager application is busy and the information
button is clicked, the following error message is displayed: “Timed out
and no reply message received. Please check the Billing Manager state.”
Performance summary report

One of the reports you can generate is the Performance Summary report
(Figure 5-37).
Figure 5-37
Performance Summary report window
The MSC or HLR element, year, month and day are selected using the text
fields. Daily interval, busy hour, or a set of interval hours which indicate from
what time to what time is selected using the Measurement Period list box.
To get the daily data, input a date into the Date text box and select Daily
(Universal Time) from the Measurement Period list box. Click the Query
button.

To get data for Busy hour if the busy hour function is available, input a date
into the Date text box and select BusyHr from the Measurement Period list
box. Click the Query button.
To get data between hours, input a date into the Date text box and select one
of the intervals from the Measurement Period list box. Click the Query
button.
The Universal Time in the Measurement Period list box means that the date in
the Date text box is based on the Coordinated Universal Time where Zero
hours UTC is midnight in Greenwich, England. The Universal Time is
applied only for the Daily data.
The Local Time in the Measurement Period list box means that the date in the
Date text box and the interval in the Measurement Period list box are based on
the local time of the user’s CEM GUI machine. The Local Time is applied for
the Busy hour and the hourly interval.
After clicking the Query button, the table is populated with the attributes and
values for the specified time. The summary data can be exported to a file by
pressing the “Export” button.
Note: The listed items are measurements from the group SUMPAGE.
Refer to the chapter “Correlated, Supported, and Billing OMs” for a list of
the SUMPAGE measurements.
The Summary Report displays the billing to OM Group TRAFFICDEST3

under the category “Dest Ckt Detail Summary”. The TRAFFICDEST3 has
additional fields to display both the incoming and outgoing trunk group as
well as the destination tag names.
For each destination tag name, TRAFFICDEST3 will collect data on calls
whose incoming and outgoing Trunk Group match to ones defined in the
destination tag name. The collected data are as follows:
• Incoming Trunk Group name
• Outgoing Trunk Group name
• Total Calls
• Answered, Normally Terminated
• Answered, Abnormally Terminated
• No Answered, Normally Terminated
• No Answered, Abnormally Terminated
• International Calls
• National Calls

• Average Time to Answer

• Average System Setup Time
• Average Time to Disconnect
• Average Call Duration
• Total Call Duration
The incoming and outgoing trunk group fields can be set with “Don’t Care”
or “All” instead of trunk group (CLLI) name.
If “Don’t Care” is set into the origination and/or destination number fields,
then TRAFFICDEST3 will collect data without checking the origination and/
or destination number in billing records. The Summary Report will not
display the origination/destination numbers if “Don’t Care” is set.
If “Don’t Care” is set for the incoming or outgoing trunk group fields, then
TRAFICDEST3 will collect data without checking the incoming or outgoing
trunk groups in the billing records respectively. If “Don’t Care” is set, trunk
group names will not be displayed.
If “All” is set into the incoming or outgoing trunk group fields, not both of
them, then TRAFICDEST3 will collect data with any incoming or outgoing
trunk groups in billing records. If “All” is set, all trunk group names which are
collected during some interval time will be displayed.

Call statistics from billing

You can generate the following billing statistics reports:
• MSC CDR statistics
• Circuit group summary
• Destination summary
• Destination circuit group summary
• Destination circuit detail summary
You can rearrange the columns in the multi-column list of the Billing OM
report area. However, if diagnostic tags are not defined for the selected
switch, the column order of the diagnostic columns is lost and they are placed
at the end of the multi-column list when the next retrieval with diagnostic
information is available.
Note 1: Sub-columns inside the diagnostic column for MSC CDR

Statistics, Ckt Group Summary and Destination Summary cannot be
reordered.
Note 2: The default order of the columns in any of the call statistics
reports will be restored when the Summary Manager window is closed
and opened.
Only one timestamp and interval entry is applicable to all billing OM report
requests. Interval, Date, and Stop Time entries represent all the billing OM
report request timestamp. For example, 1999/10/10 00:00 is set for MSC
CDR Statistic report. When selecting the Ckt Group Statistics report, the
same timestamp, 1999/10/10 00:00, is used to retrieve the data.
When the Daily interval is selected, the report is based on the 24 hour period
for the time range of the Date field at 00:00 time to 00:00 time of the next day.
When a report is re-selected, the Summary Manager re-displays the report.

The Summary Manager does not retrieve the data based on the timestamp and
interval entries that may have changed on the panel. To request the report
based on the changed timestamp and interval entries, click the “Query” button
after the report is re-displayed. This is only applicable when a report has been
previously requested. If the selected report has never been requested before,
the Summary Manager retrieves the data based on the entered timestamp and
interval.

MSC CDR statistics

MSC CDR statistics display call-related statistics.
Note: The default order of the columns in MSC CDR Statistics report is
restored every time the Summary Report window is closed and opened.
The following information is presented in the individual call type table:

• CDR Type (MO, MT, Roaming, Ictrk Calls, Ogtrk Calls, Incoming
Gateway, Outgoing Gateway)
• Call Type Total
• Total Calls (Originated, Terminated OR Passed)
• No answer, Normally Terminated
• No answer, Abnormally Terminated
• International
• National
• Average Time To Answer (seconds)
• Average System Setup Time (seconds)
• Average Time To Disconnect (seconds)
• Average Call Duration (seconds)
• Total Call Duration (hours)
• Diagnostic Groups
Circuit group summary

The circuit group statistics report displays circuit group statistics. Each
Circuit Group is split into two rows for directions - incoming and outgoing.
Note: The default order of the columns in Circuit Group Summary report
is restored every time the Summary Report window is closed and opened.
The following information is presented in the circuit group statistics data table:
• Circuit Group Name (CLLI)
• Direction
• Total
• No answer, Normally Terminated

• No answer, Abnormally Terminated

• Total International Calls
• Total National Calls
• Average Time to Answer (seconds)
• Average Time to Disconnect (seconds)
• Total Call Duration (seconds)
• Diagnostic Groups
Destination summary
The destination summary report is based on the destination group of interest
that is input through the Dialed Digits Manager.
Note: The default order of the columns in Destination Summary report is

restored every time the Summary Report window is closed and opened.
All of the following counts indicate the number of times the customer supplied
prefix appeared as the initial digits of the following:
• Destination
• Call Origination
• Call type
• Total
• Answered, normally terminated
• Answered, abnormally terminated
• No answer, normally terminated
• No answer, abnormally terminated
• International call
• National call
• Average time to answer (seconds)
• Average system setup time (seconds)
• Average time to disconnect (seconds)
• Average call duration (seconds)
• Total call duration (hours)
• Diagnostic groups

Destination circuit group summary

The destination circuit group summary report displays destination code
statistics for each circuit group. Each Circuit Group is split into two rows for
directions which indicates an incoming or outgoing traffic.
Note: The default order of the columns in Destination Circuit Group

Summary report is restored every time the Summary Report window is
closed and opened.
• Destination
• Circuit group name and type
• Traffic Direction
• Type
• Total
• Answered, normally terminated
• Answered, abnormally terminated
• No answer, normally terminated
• No answer, abnormally terminated
• International call
• National call
Destination circuit detail summary

The destination circuit detail summary report displays destination code
statistics for each circuit detail. Each Circuit Group is split into two rows for
directions which indicates an incoming or outgoing traffic.
Note: The default order of the columns in Destination Circuit Detail

Summary report is restored every time the Summary Report window is
closed and opened.
The Summary Report displays the billing to OM Group TRAFFICDEST3

under the category “Dest Ckt Detail Summary”. The TRAFFICDEST3 has

additional fields to display the origination and destination numbers, and both
the incoming and outgoing trunk group as well as the destination tag names.
• Destination
• Incoming Circuit Group
• Outgoing Circuit Group
• Call Type
• Total
• No Answer, Normally Terminated
• No Answer, Abnormally Terminated
• International
• National

Threshold Manager window 5

The Threshold Manager window supports the arm - disarm type of thresholding.
Band value is required for arm-disarm type of thresholding. Upper value and
lower value for all severities.
Figure 5-38
Threshold window
The Threshold Manager window displays all the groups, resources and fields
associated with an element. It also provides an editable interface for entering
the warning, minor, major, critical threshold values and direction for every
field. The interface for enabling or disabling thresholding for any field is also
provided. The layout of the threshold window is shown in Figure 5-38.
Threshold Management supports the following capabilities:

• Threshold alarms have separate raise and clear values. 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. This feature

prevents alarms from frequently raising and clearing if the field value
fluctuates around the threshold value.
• Thresholds can be set for all NEs of the same type under each managed
“slice.” This means that a threshold can be set across all Passports of a
certain type managed by a single MDM installation. They cannot be set
across all MSCs or HLRs, however, as these are managed individually.
• Threshold alarms are throttled when the number of threshold alarms
crosses a configurable maximum. There are two configurable values - one
is for the managed “slice” and the other one is for each element type.
Generation of alarms is stopped when the number of alarms of an element
crosses the limit set for the element type. This number gets reset upon
data arrival. Generation of alarms is throttled when the total number of
threshold alarms for a slice crosses it’s maximum limit. This number gets
reset after a configurable period. Throttling of alarm generation issues
another QOS alarm reporting threshold is throttled.
• Threshold Manager windows in other GUIs update automatically when
threshold values are changed.
• Each resource can have multiple threshold alarms for different fields. The
alarm text contains the field information. Alarms containing multiple field
crossings are no longer raised.
• The user can set warning level threshold value.
• Thresholding can be done on correlated groups/fields.
• Threshold Manager generates an 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.
Note 1: The time a threshold alarm is raised is always based on the Server
time and time zone.
Note 2: Server restarts reset the raise/clear state of a threshold alarm. If a

threshold alarm is still active but the OM value has fallen below the raise
value (but is still above the clear value), a restart will cause the alarm to be
cleared.
Note 3: For performance reasons, the OM data is not mapped to each

resource; only the threshold alarms are mapped. Consequently, the option
to open the threshold window directly from the resource object has been
removed.

Threshold Manager features

There are several Threshold manager features:
• A time stamp of the last OM report time is part of the Threshold Summary
table title, which gives users the information on which collecting interval
the "current data" was gathered. This time stamp in the table title is
updated whenever a new OM report is received.
• When no OM data has been received in last 24 hours, the Threshold
Summary table will be empty and the table title displayed will be the
message "no report is received in last 24 hours."
• A “Current Value” column in the threshold list displays the
measurements’ current values.
• A “Direction” column, displays whether the set threshold is a positive or
negative threshold.
• An “ALL RESOURCES” value can be set for a field for each group. If the
user sets a threshold for a field using the “ALL RESOURCES’ resource,
the Agent side will assign this value for each resource with that field and
within the selected group. If a specific value is set for the same field on a
particular resource, the specific value will override the “ALL
RESOURCES” value. Take note that if the actual setting of this value
occurs on the Agent side of the application, and the values may not be
reflected on the threshold table the user is viewing.
• An hourglass is shown to indicate that the application is waiting when a
response to a message is being sought.
• All the severity values have Raise value and Clear value. For NEs from
releases prior to GEM17, the Raise and Clear values are set to be the
same.
• Warning threshold value columns were added in GEM17. For NEs from
releases prior to GEM17, the warning values are set to be the same as
minor value.
• Set threshold for all the NEs of the same type under each “slice” is
supported. In the case of ALL_NE_<sourceType> node, the threshold
setting is applied to ALL_RESOURCES for selected OM group.
• Active thresholding are high lighted with colors.
• The “Apply” button is used for submitting all. The values applied per
apply are not displayed.
• The “Reset” button causes the field values to go back to the original
values.

How to view and set thresholds

Using the Threshold Manager window, the user can follow the following
procedure to set threshold:
1. In the managed element tree panel, select the NE from the tree. The user
can selected ALL_NE_<sourceType> node to set threshold for all NEs of
the same type under the slice.
2. The available OM categories appear in the Collected OM panel. All the
groups are currently available for query are in the CollectedOMGroups or
<sourceType>:AvailableOMGroups category. In case
ALL_NE_<sourceType> node is selected in the step 1, the groups list
displayed will be the intersection of the groups in
<sourceType>:AvailableOMGroups from all the NEs of this type.
5. Select a resource for your query, if any. In the case of setting threshold for
all resources for the selected OM group, ALL_RESOURCES node should
be selected.
6. All the current threshold settings for the selected group and resource
should be displayed in the Threshold Summary table.
7. Select the row you wish to editing in the table, the row should displayed in
the Threshold Editing table in the bottom of the window.
8. Edit the value in the Threshold Editing table, then click Apply button to
submit the change to server to activate the change.

Nortel defined thresholds for GPRS SGSN
Table 5-1
Predefined Thresholds for GPRS SGSN
# Threshold Details
1 Network Elements: ALL GPRS SGSN
GroupName: GprsMobilityManagement
Resources: ALL
Field: percentAttachRejected
Raise & Clear value for Critical severity: 25
Raise & Clear value for Major Severity: 15
Raise & Clear value for Minor Severity: 5
Raise & Clear value for Warning Severity: 5
Direction: Positive
Threshold Status: Disabled (default)
GroupName: SessionManagement
Resources: ALL
Field: percentPDPActivationRejected
Direction: Positive
—sheet 1 of 2—

Table 5-1
Predefined Thresholds for GPRS SGSN
# Threshold Details
GroupName: SessionManagement
Resources: ALL
Field: VS.percentPDPActivationRejectedV4
Direction: Positive
—sheet 2 of 2—
Threshold alarm (TMN318) format

The following is the format of a threshold alarm:
Alarm Header:
NotifID = <NotifId>;
AlarmType = qualityofServiceAlarm;
Severity = <Severity>;
ProbCause = thresholdCrossed;
SpecificProblem =;
Date = <YYYY/MMM/DD-HH:MM:SS>;
Alarm Body:
<NE Name><DMS style alarm severity represented by *> TMN318
<MMMDD HH:MM:SS>UTC TBL PM threshold crossed
Status: Trouble raised
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
This is a change from the previous release where a single threshold alarm was
raised per object and the Measurement attribute was a list of field names
whose alarm condition matched the overall severity.
Note: With the previous threshold format, the contents of the alarm could
become stale. This occurred when new fields on the same resource cross
thresholds of the same severity as the original alarm. The previous format
will continue to be received until the Server upgrade is complete.
Threshold management restrictions and limitations

• Only 4 threshold manager interfaces may be opened at a time, per
Element Manager client.
• Threshold alarms are throttled when the number of threshold alarms
crosses a configurable maximum. There are two configurable values: one
for the managed “slice” and one for each element type. The generation of
alarms is stopped when the number of alarms of an element crosses the
limit set for the element type. This number gets reset upon data arrival.
The generation of alarms is throttled when the total number of threshold
alarms for a slice crosses its maximum limit. This number gets reset after
a configurable period. The throttling of alarm generation issues another
QOS alarm reporting threshold is throttled.
• Resources added or deleted on the switch may not be immediately
apparent in the threshold manager interface.
• By default, all thresholds are set to a “positive” direction.
• If the user sets an “ALL RESOURCES” threshold, every resource
containing that threshold will employ the “ALL RESOURCES” setting,
unless a threshold is specifically set for that field within a particular
resource. In that case, the specifically-set threshold will be used.
• A threshold may be positive or negative but not both.
• If a negative OM threshold is set, and an unknown value (-1) exists in the
OM Report for that OM, the threshold will appear to have been crossed.
• The Threshold crossing will always be calculated from the time it is set.
The thresholding process is not going to query the old data to support time
based thresholds.
Data Notification 5
The Data Notifications window (Figure 5-39) displays the last OM report
time for each CEM managed “slice” for each data source type since the

Element Manager was started. The user can clear the display or close this
window.
Figure 5-39
Data Notifications window
Mass Export 5
Launch Mass Export by selecting Mass Export from the Performance menu of
the Performance Element Manager (Figure 5-1). Once Mass Export is
launched, the Export Status window appears (Figure 5-40). Only one Export
Status window can be opened per Element Manager window.
The Export Status window allows the user to configure profiles and
destinations. These profiles and destinations are stored locally and can be
retrieved and used for mass export. Up to four export profiles are supported
per mass export with the exception that only one export profile that exports
CAP/ACT102 logs is supported.

Figure 5-40
Mass Export Window
Mass Export supports two transfer methods: FTP and copy. If the destination
is remote, FTP is used to transfer export files to the target machine. If the
destination is local, copy is used to copy files to the target directory.
The Mass Export window supports up to 12 transfer files per report period.
Any extra files will be backed up first and then appended on the ship list at the
next report transfer time until it exceeds the hours of back up. The number of
transfer files per report period can be modified by using archiveAdmin.
Note: The archiveAdmin tool on the Sun Server supports only export
profiles of all NEs and all groups. Specific groups can be selected from
the GUI to be exported. Users should not attempt to use the archiveAdmin
tool to modify configurations with specific group lists, or they will reset
that configuration to collect all groups.
The user ID and password entered with export profile information are
encrypted by nortel proprietary encryption method. The encrypted user ID
and password are encoded by java encode convention.
Mass Export window supports the same set of network elements as

archiveServer supports. For DMS types of network elements, mass export
supports CAP/ACT102 logs tab format export. CAP/ACT102 logs can be
exported by one Mass Export/archiveServer at transfer interval or hourly
interval. If CAP/ACT102 logs are not available, it outputs “No log is

generated in this interval”. If the connection to the SDM exportLog process

fails, mass export will not produce an export log file. Instead, it generates a
TMN307 log.
Note: Switch mass export is intended only to provide data originally

produced by a DMS switch, whereas other formats (tab, csv) are fully
integrated with CEM. Correlated data, either by user-defined correlations
or Nortel-defined correlations, are not available in Switch mass export.

Supported OM groups
Table 5-2
OM Groups Supported by Mass Export
OM Group Name Description Parent Correlation Group

ACRJ Anonymous Call Rejection ACRJ
AMA Automatic Message Accounting Summary AMA
ANN Announcements ANN
AOCSS Advice of Charge AOCSS
APOCCS Application Processor Node System Counts APOCCS
APSYS Application Processor Node System Counts APSYS
ASSFTRAF CAMEL Call Traffic for ASSF ASSFTRAF
ASUFBUS Application-Specific Unit Frame Transport Bus ASUFBUS

ASUMEMUT ASU Memory Utilization ASUMEMUT
AUCSTATS Authentication Center Statistics AUCSTATS
BICNANNC BICN Announcements BICNANNC
BICNTONE BICN Tones BICNTONE
BILLING Billing BILLING
C7CMSRTE CCS7 CM Server Routing C7CMSRTE
C7GTLNK C7GTLNK
C7GTWSCR CCS7 Gateway Screening C7GTWSCR
CCS7 Gateway Signaling Connection Control
C7GWSCCP Part C7GWSCCP
C7HSLAL1 C7HSLAL
C7HSLAL2 C7HSLAL
C7HSLATM C7HSLATM
C7HSLCAR C7HSLCAR
C7LINK1 CCS7 Link Group 1 C7LINK
C7LINK4 C7LINK
C7LKSET CCS7 Link Set C7LKSET
C7LPP CCS7 Link Peripheral Processor C7LPP
C7LPP2 CCS7 Link Peripheral Processor 2 C7LPP
C7MTP CCS7 Message Transfer Part C7MTP
C7MTPRES CCS7 MTP Restart C7MTPRES
C7ROUTE CCS7 Route C7ROUTE
C7ROUTE2 CCS7 Route 2 C7ROUTE
C7ROUTER CCS7 Router Information C7ROUTER
C7RTESET CCS7 Routeset C7RTESET
CCS7 Signaling Connection and Control Part
C7SCCP Status C7SCCP

Table 5-2

C7SCCPCO CCS7 SCCP Connection Oriented C7SCCPCO
CCS7 SCCP Extended Unit Data and Services
C7SCCPX Messages C7SCCPX
C7SERVER CCS7 Server C7SERVER
C7SROUTE CCS7 Server Routing C7SROUTE
CALLINT Call Interception CALLINT
CAMMCSI CAMEL M-CSI CAMMCSI
CAPAFRF CAMEL Operations (ASSF - FRF) CAPAFRF
CAMEL Call Processing for O-CSI, T-CSI, and
CAPCALLP Hotline CAPCALLP
CAPCTAS Specific CAMEL Call-Type Analysis CAPCTAS
CAPDCSI CAMEL Dialed Service CSI CAPDCSI
CAPDCSI2 CAMEL Dialed Service CSI CAPDCSI
CAPERR CAMEL Errors CAPERR
CAPNCSI CAMEL Network Service CSI CAPNCSI
CAPNCSI2 CAMEL Network Service CSI CAPNCSI
CAPOCSI CAMEL Originating CSI CAPOCSI
CAPOCSI2 CAMEL Originating CSI CAPOCSI
CAPOEDP CAMEL O-BCS Events CAPOEDP
CAPSFAF CAMEL Operations (SCF - ASSF) CAPSFAF
CAPSFCF Internal IP-Related CAP Operations (SCF - SSF) CAPSFCF
CAPSFRF Internal IP-Related CAP Operations (SSF - SRF) CAPSFRF

CAPTCSI CAMEL Terminating CSI CAPTCSI
CAPTCSI2 CAMEL Terminating CSI CAPTCSI
CAPTEDP CAMEL T-BCS Events CAPTEDP
CAPTRAF CAMEL Traffic for O-CSI, T-CSI, and Hotline CAPTRAF
CBK Code Block Group CBK
CF3P Three-Port Conference Circuits CF3P
CF6P Six-Port Conference Bridge Circuits CF6P
CIDBOM Call Interception Database CIDBOM
CLINTMMU Call Interception on the MMU CLINTMMU
Calling Line Identification Supplementary
CLISS Services CLISS
Connected Line Identification Supplementary
CLOSS services CLOSS
CAMEL Subscriber Call to CAMEL Subscriber
CMLTOCML Call Processing CMLTOCML

Table 5-2

CAMEL Mobile Originated Short Message
CMOSCMU Service (MMU) CMOSCMU
CMOSCMU2 Service (MMU) CMOSCMU
CMOSCSI Service CMOSCSI
CMOSCSI2 Service CMOSCSI
CP Call Processing Software Resources CP
CP2 Call Processing Software Resources 2 CP
CP2MMU Call Processing Software Resources 2 MMU CPMMU
CPADPRBK CPIPP Address Pair Block CPADPRBK
CPMMU Call Processing Software Resources MMU CPMMU
Call Recording Stream Primary Recording Unit
CPRPL2SZ Pool 2 Size CPRPL2SZ
CPUSTAT Central Processing Unit Status CPUSTAT
CRDBOM Call Reference Database CRDBOM
CSL Console Device Maintenance Summary CSL
Call Recording Stream Secondary Recording
CSRPL1SZ Unit Pool 1 Size CSRPL1SZ
CUGSS Closed User Group Supplementary Services CUGSS
DAISGEN General Data Access/Informatoin Services DAISGEN
DCM Digital Carrier Module Maintenance Summary DCM

Table 5-2

DCSIERR Errors for CAMEL Dialed Service CSI DCSIERR
DDU Disk Drive Unit File and Mainenance Work DDU
DRM Distributed Recording Management DRM
Digital Signal Processor Resource Module
DSPRMAN Management DSPRMAN
DUTLGEN DMS Universal Transport Layer DUTLGEN
EACARR Equal Access Carrier EACARR
Equal Access Traffic Separation Measurements
EATSMS System EATSMS
ECANRMAN Echo Canceller Resource Management ECANRMAN
EIUETHER Ethernet Interface Unit Ethernet EIUETHER
Enhanced Multi-Level Precedence and
EMLPPSS Preemption Supplementary Services EMLPPSS
ENETMAT Enhanced Network Matrix Card ENETMAT
ENETOCC Enhanced Network Occupancy ENETOCC
ENETPLNK Enhanced Network Peripheral Side Links ENETPLNK
ENETSYS Enhanced Network System Card ENETSYS
ESUP Digital Echo Suppressor ESUP
ETSI Call Handling Dialogue Initiator on the
ETCHIMMU MMU ETCHIMMU
ETSI Call Handling Dialogue Responder on the
ETCHRMMU MMU ETCHRMMU
ETSI Equipment Management Dialogue Initiator
ETEQIMMU on the MMU ETEQIMMU
ETSI Equipment Management Dialogue
ETEQRMMU Responder on the MMU ETEQRMMU
ETSI Fault Recovery Dialogue Initiator on the
ETFRIMMU MMU ETFRIMMU
ETSI Fault Recovery Dialogue Responder on the
ETFRRMMU MMU ETFRRMMU
ETSI Mobility Management Dialogue Initiator on
ETMMIMMU the MMU ETMMIMMU
ETSI Mobility Management Dialogue Responder
ETMMRMMU on the MMU ETMMRMMU
ETSICHI ETSI Call Handling Dialogue Initiator ETSICHI
ETSICHR ETSI Call Handling Dialogue Responder ETSICHR
ETSIEQI ETSI Equipment Management Dialogue Initiator ETSIEQI

ETSI Equipment Management Dialogue
ETSIEQR Responder ETSIEQR
ETSIFRI ETSI Fault Recovery Dialogue Initiator ETSIFRI

Table 5-2

ETSIFRR ETSI Fault Recovery Dialogue Responder ETSIFRR
ETSI Subscriber Information Dialogue Initiator on
ETSIIMMU the MMU ETSIIMMU
ETSIMMI ETSI Mobility Management Dialogue Initiator ETSIMMI
ETSIMMR ETSI Mobility Management Dialogue Responder ETSIMMR

ETSI Subscriber Information Dialogue
ETSIRMMU Responder on the MMU ETSIRMMU
ETSISII ETSI Subscriber Information Dialogue Initiator ETSISII

ETSI Subscriber Information Dialogue
ETSISIR Responder ETSISIR
ETSISMGI ETSI Subscriber Management Dialogue Initiator ETSISMGI

ETSI Subscriber Management Dialogue
ETSISMGR Responder ETSISMGR
ETSISMSI ETSI Short Message Service Dialogue Initiator ETSISMSI

ETSI Short Message Service Dialogue
ETSISMSR Responder ETSISMSR
ETSISSI ETSI Supplementary Services Dialogue Initiator ETSISSI

ETSI Supplementary Services Dialogue
ETSISSR Responder ETSISSR
ETSI Subscriber Management Dialogue Initiator
ETSMGIMU on the MMU ETSMGIMU
ETSI Subscriber Management Dialogue
ETSMGRMU Responder on the MMU ETSMGRMU
ETSI Short Message Service Dialogue Initiator
ETSMSIMU on the MMU ETSMSIMU
ETSI Short Message Service Dialogue
ETSMSRMU Responder on the MMU ETSMSRMU
ETSI Supplementary Services Dialogue Initiator
ETSSIMMU on the MMU ETSSIMMU
ETSI Supplementary Services Dialogue
ETSSRMMU Responder on the MMU ETSSRMMU
EVGCS Emergency Voice Group Call Service EVGCS
EXHOCA MSC External Handover Cause EXHOCA
EXHOCAMU MSC External Handover Cause on the MMU EXHOCAMU
EXNDINV External Node Inventory EXNDINV
EXT Extension Blocks EXT
FBTRAFF Frame Transport Bus Platform Traffic FBTRAFF

Table 5-2

Feature Processing Framework Huge Auxiliary
FHUGAXBK Blocks FHUGAXBK
Feature Processing Framework Large Auxiliary
FLRGAXBK Blocks FLRGAXBK
Feature Processing Framework Medium
FMDMAXBK Auxiliary Blocks FMDMAXBK
File Procesor Dual-Access Buffer Memory
FPDABM Counts FPDABM
FPDEVICE File Processor Storage Device Counts FPDEVICE
FPFMSGS FPF Messages FPFMSGS
FPSCSI File Processor SCSI Bus Counts FPSCSI
FPXLMSGB FPF Extra Large Message Blocks FPXLMSGB
FRDCNTL Fraud Control FRDCNTL
FSMLAXBK FPF Small Auxiliary Blocks FSMLAXBK
FTAM File Transfer Access and Management FTAM
FTROM FTROM
FTRQ Feature Queuing Software Resources FTRQ
FXLGAXBK FPF Extra Large Auxiliary Blocks FXLGAXBK
G7SCCP GSM CCS7 Signalling Connection Control Part G7SCCP

G7SCCPCO GSM CCS7 SCCP Connection Oriented G7SCCPCO
G7SCCPX GSM CCS7 SCCP Extension Services G7SCCPX
GACODE GSM Account Code GACODE
GCBK GSM Code Blocking GCBK
GCISBXBK GSM CI Sub Extension Block GCISBXBK
GELIDOMG GSM Emergency Location Identification GELIDOMG
GSM Emergency Location Identification on
GELIDOMU MMUs GELIDOMU
GGSNAURS GGSN Addresses Usage Related Statistics GGSNAURS
GGSNERR GGSNERR
GGSNLSST GGSN List Size Statistics GGSNLSST
GGSNNURS GGSN Numbers Usage Related Statistics GGSNNURS
GGSNOPS GGSNOPS
GHLRADM GSM HLR Administrative GHLRADM
GHLRADM2 GSM HLR Administrative 2 GHLRADM
GHLRADM3 GSM HLR Administrative 3 GHLRADM
GHLRBS GSM HLR Basic Services GHLRBS
GHLRCCS7 GSM HLR CCS7 GHLRCCS7
GHLRCH GSM HLR Call Handling Transactions GHLRCH

Table 5-2

GHLRCOS GSM HLR Class of Service GHLRCOS
GHLRFREC GSM HLR Fault Recovery GHLRFREC
GHLRLCST GSM HLR LSC Transitions GHLRLCST
GHLRMMGT GSM HLR Mobility Management GHLRMMGT
GHLRODB GSM HLR Operator Determined Barring GHLRODB
GHLRODBT GSM HLR Operator Determined Barring Traffic GHLRODBT

GHLRROAM GSM HLR Roaming GHLRROAM
GSM HLR Subscriber Identity Module
GHLRSIMR Replacement GHLRSIMR
GHLRSMGT GSM HLR Subscriber Management GHLRSMGT
GHLRSMS GSM HLR Short Message Service GHLRSMS
GHLRSSCB GSM HLR Supplementary Service Call Barring GHLRSSCB

GSM HLR Supplementary Service Call
GHLRSSCF Forwarding GHLRSSCF
GHLRSSCW GSM HLR Supplementary Service Call Waiting GHLRSSCW

GHLRSSPW GSM HLR Register Password GHLRSSPW
GHSBYACT GSM HLR Standby Activity GHSBYACT
GHSBYADM GSM HLR Standby Administrative GHSBYADM
GHSBYSTA GSM HLR Standby Statistics Acting GHSBYSTA
GHSBYSTS GSM HLR Standby Statistics Standby GHSBYSTS
GHUSSDV1 GHUSSDV1
GINAP GSM Intelligent Network Application Protocol GINAP
GINAP2 GSM Intelligent Network Application Protocol GINAP
GSM Intelligent Network Application Protocol on
GINAP2MU the MMU GINAPMMU
GINAP3 GSM Intelligent Network Application Protocol GINAP
GINAP3MU the MMU GINAPMMU
GINAPMMU the MMU GINAPMMU
GINAPXBK GSM INAP Extension Blocks GINAPXBK
GLCSOMG GSM Location Services GLCSOMG
GLCSOMG2 GSM Location Services GLCSOMG
GLCSOMG3 GSM Location Services GLCSOMG
GLCSOMU GSM Location Services on the MMU GLCSOMU
GLCSOMU2 GSM Location Services on the MMU GLCSOMU

Table 5-2

GLCSOMU3 GSM Location Services on the MMU GLCSOMU
GLMSMOMG GSM LMU-SMLC Messaging GLMSMOMG
GLMSMOMU GSM LMU-SMLC Messaging on the MMU GLMSMOMU
GMAMSXBK GSM MAP MSC Extension Blocks GMAMSXBK
GMAPCH GSM Mobile Application Part Call Handling GMAPCH
GMAPCH2 GSM Mobile Application Part Call Handling GMAPCH
GSM Mobile Application Part Equipment
GMAPEMGT Management GMAPEMGT
GMAPFREC GSM Mobile Application Part Fault Recovery GMAPFREC
GSM Mobile Application Part Mobility
GMAPMMGT Management GMAPMMGT
GSM Mobile Application Part Subscriber
GMAPSMGT Management GMAPSMGT
GSM Mobile Application Part Short Message
GMAPSMS Service GMAPSMS
GSM Mobile Application Part Supplementary
GMAPSS Services GMAPSS
GSM Mobile Application Part Supplementary
GMAPSS2 Services GMAPSS
GMAPTR GSM MAP Tracing GMAPTR
GMASCXBK GSM MAP SCCP Extension Blocks GMASCXBK
GMAVLXBK GSM MAP VLR Extension Blocks GMAVLXBK
GMCH2MMU GSM MAP Call Handling on the MMU GMCHMMU
GMCHMMU GSM MAP Call Handling on the MMU GMCHMMU
GMEAN2MU GSM MAP Call Handling on the MMU GMEANTMU
GMEANTM GSM Mean Time GMEANTM
GMEANTM2 GSM Mean Time GMEANTM
GMEANTMU GSM Mean Time on the MMU GMEANTMU
GMEMGTMU GSM MAP Equipment Management on the MMU GMEMGTMU

GMFREMMU GSM MAP Fault Recovery on the MMU GMFREMMU
GMGIFMMU GSM Gs Interface for MMUs GMGIFMMU
GSM Mobility Management Layer Transactions
GMMLTRMU on the MMU GMMLTRMU
GMMLTRN GSM Mobility Management Layer Transactions GMMLTRN

GSM MAP Mobility Management Oms on the
GMMMGTMU MMU GMMMGTMU
GMPSCGRP GSM MAP Screening Table Group GMPSCGRP

Table 5-2

GSM MAP Subscriber Management Oms on the
GMSMGTMU MMU GMSMGTMU
GMSMSMMU GSM MAP Short Message Service on the MMU GMSMSMMU
GMSS2MMU GSM MAP Supplementary Services on the MMU GMSSMMU
GMSSMMU GSM MAP Supplementary Services on the MMU GMSSMMU

GMTRMMU GSM MAP Tracing on the MMU GMTRMMU
GPLOMGR GSM Perform Location OM Group GPLOMGR
GPLOMMU GSM Perform Location Oms on the MMU GPLOMMU
GPRP GSM Pre-Route Peg GPRP
GPRSMMGT GPRS Mobility Management GPRSMMGT
GPSLOMGR GSM Provide Subscriber Location OM Group GPSLOMGR
GSM Provide Subscriber Location Oms on the
GPSLOMMU MMU GPSLOMMU
GSBARMMU GSM Services Barred on the MMU GSBARMMU
GSLROMGR GSM Subscriber Location Report GSLROMGR
GSLROMMU GSM Subscriber Location Report on the MMU GSLROMMU

GSMECT GSM Explicit Call Transfer GSMECT
GSMGSITF GSM Gs Interface GSMGSITF
GSMLERRS GSM Link Interface Unit (LIU) Errors GSMLERRS
GSMLUSAG GSM Link Interface Unit Usage GSMLUSAG
GSMMCT GSMMCT
gsmomtrk GSM OM Trunk gsmomtrk
GSMOVLD GSM Overload GSMOVLD
GSMPLERR GSM Per Link Interface Unit (LIU) Error GSMPLERR
GSMPLUSG GSM Per Link Interface Unit (LIU) Usage GSMPLUSG
GSMSCOMG GSM SMLC-MS Messaging GSMSCOMG
GSMSCOMU GSM SMLC-MS Messaging on the MMU GSMSCOMU
GSMSGBKS GSM Messages Block GSMSGBKS
GSMUSSD GSM Unstructured Suplementary Data GSMUSSD
GSRVCBAR GSM Services Barred GSRVCBAR
GTASOM GSM Traffic Analysis System GTASOM
GTID GTID
GUBZOMMU USSD Billing Zone Query on the MMU GUBZOMMU
GSM Unstructured Suplementary Data on the
GUSSDMMU MMU GUSSDMMU

Table 5-2

H248PERF H.248 Performance H248PERF
H2G2G2MU 2G to 2G Handover Oms on the MMU H2G2G2MU
H324SRV H324 Service Type H324SRV
H3PCCMSG HLR Memory Extension CM Message H3PCCMSG
H3PCCPU HLR Memory Extension CPU H3PCCPU
H3PCMEM HLR Memory Extension Memory H3PCMEM
H3PCMSG HLR Memory Extension Message H3PCMSG
H3PCNSC HLR Memory Extension Node Subscriber Counts H3PCNSC

HACCOUNT HLR Accounting Code Provisioning Options HACCOUNT
HBOOSTER HLR Requests sent to Booster HBOOSTER
HCAMLAIH HLR Camel Traffic (detailed) HCAMLAIH
HLR Call Independent Supplementary Services
HCISSOPS Operations GHLRMMGT
HCMLMPT HLR CAMEL Miscellaneous Provider Traffic HCMLMPT
HCMLMPT2 HLR CAMEL Miscellaneous Provider Traffic HCMLMPT
HCMLMRT HLR CAMEL Miscellaneous Requester Traffic HCMLMRT

HLR Closed User Group Send Routing
HCUGSRI Information Traffic HCUGSRI
HCUGSUB HLR Closed User Group Subscription Data HCUGSUB
HDBOM HDBOM
HDESIGN HLR Design HDESIGN
HEQACCS HLR Equal Access HEQACCS
HEvtProv HEvtProv
HLR Extension Service Supplementary Service
HEXTSUB Provisioning Statistics HEXTSUB
HISTAT GSM HLR Subscriber IMSI Status HISTAT
HLDSSMMU MSC Call Hold Supplementary Services HLDSSMMU
HLRCAMEL GSM HLR CAMEL Subscription Data HLRCAMEL
HLRCAML2 GSM HLR CAMEL Subscription Data 2 HLRCAMEL
HLRCAMLT HLR CAMEL Traffic HLRCAMLT
HLRCAP HLR Capacity HLRCAP
HLRDUALI HLR Dual IMSI HLRDUALI
HLREXTT HLR Extension Services Traffic HLREXTT
HLRFM HLR Follow Me HLRFM
HLRGPRS HLR GPRS Subscription Data HLRGPRS
HLRHB HLR HotBill HLRHB

Table 5-2

HLRIN HLR Intelligent Network HLRIN
HLRINT HLR Intelligent Network Traffic HLRINT
HLRMAPT GSM HLR MAP Traffic HLRMAPT
HLRMISCH HLR Miscellaneous Call Handling HLRMISCH
HLRORT GSM HLR Optimal Routing Traffic HLRORT
HLR Send Routing Information Proprietary
HLRSRIPT Traffic HLRSRIPT
HLRTRACE HLR Subscriber Call Trace HLRTRACE
HLR Unstructured Supplementary Services Data
HLRUSSDT Traffic HLRUSSDT
HLRWORK HLR Work-load Handling HLRWORK
HMWDSC HLR Message Waiting Data for service Centers HMWDSC

HO2G2GMU 2G to 2G Handover Oms on the MMU HO2G2GMU
HO2GT2G2 2G to 2G Handover Oms HO2GTO2G
HO2GTO2G 2G to 2G Handover Oms HO2GTO2G
GSM HLR Operator Determined Barring for
HODBMISC ODBMISC categories HODBMISC
HOPRMXBK Handover Parm Extension Blocks HOPRMXBK
HOPTMMGT HLR Optimized Mobility Management GHLRMMGT
HREGSUB HLR Regional Subscription HREGSUB
HROUTING HLR Request Routing HROUTING
HSMG2 HLR Subscriber Management for Phase 2 HSMG2
HSMSERR HLR Short Message Service Errors HSMSERR
HSMSOPS HLR Short Message Service Operations HSMSOPS
HSSERROR HLR Supplementary Service Errors HSSERROR
HSTRACET HLR Home Subscriber Trace Traffic HSTRACET
HSUBPRTN HLR Subscriber Partition Provisioning Statistics HSUBPRTN

HSUBSMWD HLR Subscribers Message Waiting Data HSUBSMWD
HTR HTR
HLR Visitor Location Register Subscriber
HVLRSMGT Management GHLRMMGT

Table 5-2

IN1SUM Number Services Code Call Summary IN1SUM
INTSEP Interactive Services Evaluation Platform INTSEP
IOC I/O Controller Maintenance Summary IOC
IOSYS I/O System IOSYS
ISDD Incoming Start-to-Dial Delay ISDD
ISDN User Part (ISUP) Circuit Group
ISUPCGRP Availability ISUPCGRP
ISUPCKTA ISUP Circuit Availability ISUPCKTA
ISUPCONG ISUP Congestion ISUPCONG
ISUPCONN ISUP Connection Performance ISUPCONN
ISUPERRS ISUP Errors ISUPERRS
ISUPOVLD ISUP System Overload Control ISUPOVLD
ISUPUSAG ISUP Utilization ISUPUSAG
LCSLRD Location Services Location Related Data LCSLRD
Location Services Location Related Data on
LCSLRDMU the MMU LCSLRDMU
LMD Local and Remote Line Module Traffic LMD
Local Message Switch Central Processing Unit
LMSCPUST Status LMSCPUST
LMSMEM Local Message Switch Memory LMSMEM
LOGS Log Messages LOGS
M2GHO2MU 2G MSC Handover per MMU M2GHO2MU
M3GHO2MU 3G MSC Handover per MMU M3GHO2MU
MACHCONG Machine Congestion MACHCONG
MCLUSTER Mobile Cluster Termination MCLUSTER
MDMCTRLB MDM Control Blocks MDMCTRLB
MLPP MLPP
MNPOMGRP Mobile Number Portability OM Group MNPOMGRP
MPCBASE Multi-Protocol Controller Base Software MPCBASE
MPCFASTA Multi-Protocol Controller Fast Applications MPCFASTA
MPCLINK2 Multi-Protocol Controller Link 2 MPCLINK2
MPCLINK3 Multi-Protocol Controller Link 3 MPCLINK3
MSC Multi-Party Supplementary Services on
MPTSSMMU the MMU MPTSSMMU
MS Message Switch Summary MS
MSC2GHO2 2G MSC Handover MSC2GHO2
MSC3GHO2 3G MSC Handover MSC3GHO2

Table 5-2

MSCCALLR MSC Call Re-establishment MSCCALLR
MSCCBSS MSC Call Barring Supplementary Services MSCCBSS
MSCCFSS MSC Call Forwarding Supplementary Services MSCCFSS

MSCCNAM MSC Calling Name Delivery MSCCNAM
MSCCP MSC Call Processing MSCCP
MSCCP2 MSC Call Processing MSCCP
MSCCP3 MSC Call Processing MSCCP
MSCCP3MU MSC Call Processing on the MMU MSCCP3MU
MSCCPSRV MSC Call Processing Circuit-Switched Services MSCCPSRV

MSCCRMMU MSC Call Re-establishment on the MMU MSCCRMMU
MSCCWTSS MSC Call Waiting Supplementary Services MSCCWTSS
MSCDSRV MSC Data Services MSCDSRV
MSCEXTSS MSC Extension Service Supplementary Services MSCEXTSS

MSCGCS MSC Group Call Services MSCGCS
MSCHAIN Message Switch Chain MSCHAIN
MSCHLDSS MSC Call Hold Supplementary Services MSCHLDSS
MSCHNLK Message Switch Channelized Link MSCHNLK
MSCHO MSC Call Handover MSCHO
MSCHO2 MSC Call Handover MSCHO
MSCHO2MU MSC Call Handover on the MMU MSCHOMMU
MSCHOMMU MSC Call Handover on the MMU MSCHOMMU
MSCLIDBQ MSC Line Information Database Query MSCLIDBQ
MSCMPTSS MSC Multi-Party Supplementary Services MSCMPTSS
MSCRLT MSC Release Link Trunk MSCRLT
MSCSMS MSC Short Message Services MSCSMS
MSCSMSMU MSC Short Message Services on the MMU MSCSMSMU
MSCTRACE MSC Subscriber Trace MSCTRACE
MSCTRMMU MSC Subscriber Trace on the MMU MSCTRMMU
MSCUPLNK MSC VGCS Uplink Requests MSCUPLNK
MSFBUS Message Switch Frame Transport Bus MSFBUS
MSFBUSTP Message Switch Frame Transport Bus Taps MSFBUSTP
MSGPSOC MSGPSOC
MTU Magnetic Tape Unit Maintenance Summary MTU
Non-Computing Module Node Central
NCMCPUST Processing Unit Status NCMCPUST

Table 5-2

NCSIERR Errors for CAMEL Network Service CSI NCSIERR
8-port 64-Kbps Non-Multiplexed Digital
NDS0CARR Voice/Data Carriers NDS0CARR
NEMASAPL NEMASAPL
NIUFBUS Network Interface Unit Frame Transport Bus NIUFBUS
NIUMEMUT Network Interface Unit Memory Utilization NIUMEMUT
Network Message Controller Maintenance
NMC Summary NMC
NMTCLINK Node Maintenance Link Measurements NMTCLINK
NMTCNODE Node Maintenance Node Measurements NMTCNODE
NMTCTYPE Node Maintenance Type Measurements NMTCTYPE
NMTCUNIT Node Maintenance Unit Measurements NMTCUNIT
Local Number Portability Automatic Code
NPACGGRP Gapping NPACGGRP
NPSUM Local Number Portability Service Call Summary NPSUM

NSEPENMC NS/EP Calls Exempted from MNCs NSEPENMC
NSEPPROG NS/EP Trunk Queue NSEPPROG
NSEPSRVC NS/EP Service NSEPSRVC
NSEPTTDQ NS/EP TTID Queuing Group NSEPTTDQ
NWMFRRCT Network Management Flexible Reroute NWMFRRCT
Network Management Flexible Reroutes for
NWMFRRTG Trunk Groups NWMFRRTG
Network Management Selective Incoming Load
NWMSILC Control NWMSILC
NWMTGCNT Network Managment Trunk Group Control NWMTGCNT
OCSIERR Errors for CAMEL Originating CSI OCSIERR
ODB ODB
OFFBDIN Off-Board IN Access OFFBDIN
OFZ Office Traffic Summary OFZ
OFZ2 Office traffic Summary 2 OFZ
OTS Office Traffic Summary OTS
PCMCARR CCITT DS30 Carrier Maintenance Summary PCMCARR
PERMEXTO PERM EXT OM Group PERMEXTO
PETCUT PET Customer Unauthorized Treatment PETCUT
PM Peripheral Module Maintenance Summary PM
Peripheral Module Single Unit Maintenance
PM1 Summary PM

Table 5-2

Dual Unit Peripheral Module Maintenance
PM2 Summary PM
PMOVLD Peripheral Module Overload PMOVLD
PMTYP Peripheral Module Type PMTYP
PRAFAC Primary Rate Access Facility PRAFAC
PRP Pre-Route Peg PRP
RADR Receiver Attachment Delay Recorder RADR
RCH Resume Call Handling RCH
RCVR Receiver Service Circuits RCVR
RMANCMR RMANCMR
ROAPPL Remote Operation Service Application ROAPPL
ROMISC Remote Operation Service Office Wide ROMISC
RRTE Re-Route Control RRTE
RTEASUM Real Time Tool Equal Access Summary RTEASUM
RTFEAT Real Time Tool Feature Activations RTFEAT
RTLTSUM RTLTSUM
SGSNSMGT SGSN Subscriber Management SGSNSMGT
SLLNK SL-100 Outgoing Data Link SLLNK
SLLNKINC SL-100 Incoming Data Link SLLNKINC
Software Maintenance Critical Application
SMCOM Operational measurements SMCOM
Software Maintenance General Operational
SMGENOM Measurements SMGENOM
SMLCPPGP SMLC Peer to Peer Group SMLCPPGP
Software Maintenance Non-Critical Application
SMNCOM OMs SMNCOM
SOTS Supplementary Office Traffic Summary SOTS
SPMACT SPMACT
SPMUSAGE SPMUSAGE
SRINODE Send Routing Information Per Node SRINODE
STN Special Tones STN
STORE Data and Program Store Usage STORE
SVCT Service Circuits SVCT
SYSPERF System Performance SYSPERF
TCAPCXBK TCAP Component Extension Blocks TCAPCXBK
TCAPERRS Transaction Capabilities Application Part Errors TCAPERRS

Internal IP-Related CAP Operations (SCF-SSF)
TCAPSFCF for T_CSI TCAPSFCF

Table 5-2

Internal IP-Related CAP Operations (SSF-SRF)
TCAPSFRF for T_CSI TCAPSFRF
TCAPUSAG Transaction Capabilities Application Part Usage TCAPUSAG

TCSIERR Errors for CAMEL Terminating CSI TCSIERR
TFACGGRP Toll-Free Automatic Code Gapping TFACGGRP
TFCANA Traffic Separation/Traffic Analysis TFCANA
TFSUM Toll Free Service Call Summary TFSUM
TM Trunk Module Maintenance Summary TM
TONES Tones Group TONES
TRK Trunk Group TRK
TRMTCM Treatment Customer Miscellaneous TRMTCM
TRMTCM2 Treatment Customer Miscellaneous 2 TRMTCM
TRMTCU Treatment Customer Unauthorized TRMTCU
TRMTCU2 Treatment Customer Unauthorized 2 TRMTCU
TRMTCU3 Treatment Customer Unauthorized 3 TRMTCU
TRMTER Treatment Equipment-Related TRMTER
TRMTFR Treatment Feature-Related TRMTFR
TRMTFR2 Treatment Feature-Related 2 TRMTFR
TRMTFR3 Treatment Feature-Related 3 TRMTFR
TRMTPR Treatment Protocol-Related TRMTPR
TRMTRS Treatment Resource Shortage TRMTRS
TRNK2 TRK
TS Time Switch TS
TTCCARR TTC Carrier TTCCARR
UBZOMGRP USSD Billing Zone Query UBZOMGRP
UTR Universal Tone Receiver UTR
VLR Visitor Location Register VLR
VLR2 Visitor Location Register VLR
VLR2MMU Visitor Location Register on the MMU VLRMMU

Table 5-2

VLRMMU Visitor Location Register on the MMU VLRMMU
WPSSSRVC WPS Service WPSSSRVC
XACORE XACORE
XACPOM XACPOM
XACSRVC XACSRVC
XASTAT XA-Core Occupancy Status XASTAT
XPMLNK XMS-Based Peripheral Module Link XPMLNK
XPMMSGOC XPMMSGOC
XPMOCC XPMOCC
XPMOVLD XPMOVLD
Not all OM groups are listed individually for tab/csv mass export. Some OM
groups are combined into a Parent Correlation Group for export. Table 5-2
specifies the associated Parent Correlation Group for each OM group listed.
Profile Editor
The Profile Editor window (Figure 5-41) has group selection, export format
selection and destination information sections. The main purpose of this
window is to help user edit a profile.

Figure 5-41
Profile Editor to Help User Edit A Profile
The file menu has the following menu items:

• New: create an empty profile
• Load: load most recently, up 10 profiles from local disk
• Save: save profile to local disk and add to status table for user to enable it
• Close: close the window and go back to status table

Figure 5-42
Profile Editor Has pop-up Menu to Help User Select OMs
The editor window has buttons:

• Reset: reset profile to the original state
• Save: save profile to local disk and add to status table for user to enable it
The editor window has pop-up menu to when users select an item in OM
selection panel, and right click mouse:
• Apply selection to this region: apply select or de-select this item to the
region based on NE type if selected item is a NE element, or based on
name otherwise.
• Apply selection to all regions: apply select or de-select this item to all
regions based on NE type if selected item is a NE element, or based on
name otherwise.

Mass export status table

The mass export status table shows currently working profiles and let user
enable newly added profile from profile Editor window.
Export Status window

The status table window has two views:
• profile view shows profiles and its export source information.
• network element view shows network element related export sources and
its profile information.
Each view has two panels:

• profile information panel shows overall working profiles status and
destination information
• export source panel shows, export source related information, NE type
and name, and latest export time stamp.
Figure 5-43
Profile View shows profile and its export sources information

Figure 5-44
Network Element View shows network element related sources and its export profiles
Figure 5-45
Launch profile editor

Export Status menu

The Export Status window has File and Actions menu.
File menu has two buttons:

• Start Editor: select Archive Export Profile or Switch Export Profile to
start Editor window
• Close: close the status table
Action menu and pop-up menu on profile information panel have the same set
of buttons:
• New: bring up Profile Editor Window with empty selection
• Edit: select a disabled profile from table, edit button will bring up Profile
Editor with selected profile
• Enable/Disable: toggle between enable or disable selected profile
• Delete: delete selected profile
Sort function
Users can sort the Mass Export GUI tables by clicking on the table header. A
click will sort table ascent and shift click will sort table descent. However,
when the table data changes, the tables lose the sorted order.
Mass export file name protocol

Mass export file name protocol shortens the file name.
Figure 5-46
Mass Export File Name Protocol for GEM17
Export File Name = <Tab|Csv>_<Report Period in Minutes>_<Network Element Type>_<Network

Element Name><yyyymmddHHMM>.<profile name>
For example:
Tab_30_TRI_MSCY20030617230.profile1
Figure 5-47
Mass Export File Name Protocol for GEM16
Export File Name = OM_Data_<Tab/Switch>_format_<Network Element Name>_<Element/

Billing><yyyymmddHHMMSS.exportdest><export identity>
File Name Field Rules:

• Name fields are separated by underscore.
• Report Period field is 2 digit field. It may have a value of 15, 30, 60.

• Network Element Type field has node type. No underscore is allowed to

be part of type name. It may have a value of MSC, HLR, TRI, SLR, USP,
BOM, LOG, etc...
• Network Element Name field has node clli name. It can be free format.
• Field yyyymmhhHHMM is OM report start time. The yyyy represents
year. The mm represents month (01 - 12). The hh represents day. The HH
represents hours. The MM represents minutes (00, 15, 30, 45).
Figure 5-48
Back-up Mass Export File Name Protocol
Backup Export File Name = <Export File Name>. bak.<no. of backup in this profile
For example:
Tab_30_TRI_MSCY200306171230.profile1.bak.1
Back up Rules:
• The number of back up files is determined by hours of backup. The hour
of back up can be configured by GUI or archiveAdmin tool.
• The maximum hours of back up is set to 48 hours. It begins at OM report
start time.
• The suffix 0 indicates the most recent back up.
Mass export file format

There are two types of file formats based on field separators: tab and comma
(csv). The user is chooses a format when configuring a profile. Each export
report consists of a header and body. For the header format, see Figure 5-49
and Figure 5-51. For the body format, see Figure 5-50 and Figure 5-52.
The start time and stop time of the header are in GMT time. Conversion to
GMT may either be accomplished from information received from the NE, or
approximated using the Server time zone as described previously. The start
time in the file name matches the start time in the file. The delta GMT is the
difference (in seconds) between the NE time (or Server time) and GMT. This
value can be added to the GMT start time to get the start time in the NEs (or
Servers) time zone.
Note: The Mass Export GUI also displays a “latest export” time. This is
the time that the last file was transferred from the Server, and is always
presented in the Server’s time zone.
Within the body of either tab or csv files, each OM group starts with the group
name and fields names.

For multi tuple groups in tab format, subsequent lines consist of resource
names and register values. For single tuple groups in tab format, the resource
name is empty and the subsequent line consists only of field values.
In csv file format, the resource name combines the Network Element name
and resource name of multi tuples OM group, or the Network Element name
only in single tuple OM groups.
Note: CSV file format is not supported for mass export if the SDM is in
stand-alone mode.
For both tab and csv formats, two blank lines separate file header and file
body, and one blank line separates groups.
Figure 5-49
Tab Mass Export File Header
Network Element NAME: <tab> <NE clli name>

Network Element INFO: <tab> <NE load info>
Associated Types: <tab><type><tab><type>
DELTA GMT: <tab> <NE time zone offset in seconds>
START TIME: <tab> <yyyy/mm/dd HH:MM>
STOP TIME: <tab> <yyyy/mm/dd HH:MM>
REPORT PERIOD: <tab> <MM>
Figure 5-50
Tab Mass Export File
Header
Multi tuple group:

<GroupName><delimiter> [ <field name> <delimiter> ]
<Resource Name ><delimiter> [value of field <delimiter> ]
Single tuple group:

<GroupName><delimiter> [ <field name> <delimiter> ]
<delimiter> [value of field <delimiter> ]

Figure 5-51
CSV Mass Export File Header
Network Element NAME, Network Element INFO,Associated Types,DELTA GMT, START TIME,
STOP TIME, REPORT PERIOD
<NE clli name>, <load info>, <type>,<NE timezone offset>,<yyyy/mm/dd HH:MM>,<yyyy/mm/

dd HH:MM>,<MM>
Figure 5-52
CSV Mass Export File
Header
<Group Name> <delimiter> [ <field name> <delimiter>]

<Resource Name> <delimiter> [ <value of field> <delimiter>]
Network element associated types

An NE may have associated types. For example, in a MSC/USP/BOM combo
slice, the MSC mass export file will have NE type MSC and associated types
USP and BOM. The USP mass export file will have NE type USP and
associated types MSC and BOM. The BOM mass export file will have NE
type BOM and associated type MSC and USP.
In an MSC standalone slice, the MSC mass export file will have NE type
MSC and associated types NA which means there are no associated types for
this NE.
The NE name will stay the same for all associated types.
Mass export back up files

Switch format mass export files are backed up to the following directory:
/mscomc/gemCommon/dat/archive on the SDM. Tab format mass export files
are backed up to the following directory:
/mscomc/OMC_S/archive/dat/archive on the SDM.
If export files fail to ftp to their destination, mass export backs up the files in
the following directory: /opt/nortel/data/coreEMS/data/<slicename>/
exportElementPM/.
For switch mass export:

number of backup files = backup hours/transfer time

For archive mass export:

number of backup files = (backup hours/transfer time) + 1
The maximum number of back up hours is 48 hours. Any files that failed to
transfer to the destination will be backed up first and appended on the transfer
list at the next report transfer time until it exceeds the hours of back up.
Export profiles
The Mass Export GUI and the archiveAdmin tool both manage export
profiles.
Profile states
A shown profile can be in one of the following states:
• ENABLED: a profile is working
Enabled profiles are held by CEM server. The server will export OM
groups according to the profiles. Only NORMAL_USER can disable the
profile.
• DISABLED: a profile is disabled

The user creates profiles using profile editor. Those profiles are stored in
local disk. When mass export is initializing, it exams those local profiles.
If they are not in enabled profile list and export slices are subset of
discovered PM slices, Mass Export GUI will show them in status table as
disabled profiles.
• WARNING: a profile has export troubles

The Mass Export GUI has export tracker to monitor export status. For
example, profile1 has report period 30 minutes, the export tracker will
check its export time stamps every 30 minutes to make suer it has new
time stamp. If the export tracker found that the export time stamp did not
get update, it shown warning icon and message ‘miss <first missing
export time stamp>’ in status table.
Warning profiles indicate something is wrong in the CEM server. One of

the processes could be down or the network has problems.
• DISABLING: a profile is in middle of disabling (see Transient Profile

information below)
• ENABLING: a profile is in middle of enabling (see Transient Profile
information below)
Transient Profile
Sometimes mass export calls DISABLING or ENABLING states a transient
state. The user uses the action menu to enable or disable a profile. The Mass

Export GUI will send down requests to servers. The profile enters a transient
state.
Some servers may reject Mass Export GUI’s request or some replies may loss
in network. The profile will return to its original state. Those information
display in NE tables. In Profile View, user clicks the profile in profile table,
request results show in NE table below. In Network Element View, user can
see server’s reply in NE table and only those servers that accept the request
have the profile in profile table below. It is recommended to use Profile View
to enable or disable a profile so that user can view the result easily.
The Mass Export GUI has acknowledgment tracker to track acknowledgment

of requests. The acknowledgement timer is set to 60 seconds. When the timer
is expired and the reply has not yet arrived, time out message will display at
NE tables. If all the servers reject the request, or all the request are time out,
the acknowledgment tracker will set the original state to the profile.
Those profile states are known to GUI only. On the server side, a profile has
only one state: enabled. A disable message will cause server to delete the
profile.
Available profile action menu items

Profile action menu has items: show, edit, enable/disable, delete. The user can
access action menu items by using menu bar’s menu or pop-up menu.
Not all of action menu items are available for any selected profile. A menu item
is enabled based on the state of profile:
• Enabled or warning profile has items: show, enable/disable
• Disabled profile has all items: show, edit, enable/disable, delete
• Transient profile has least item: show.
Broadcast messages
In a GEM17.1 server, data process implements broadcast messages of
"exportInfoChanged" and "exportReset". Only archiveAdmin Tool is allowed
to reset export profiles.
When user is using archiveAdmin tool or Mass Export GUI, the application
notifies user that export profile list is changed upon receiving those broadcast
messages. If a profile is added to the system, it will add to profile list. If a
profile is deleted from the system, archiveAdmin tool will delete the profile.
Mass Export GUI will delete the profile and its clones (profiles has the same
name) and query servers again. Mass Export GUI does the same thing when it
receives exportReset message.

Duplicate profile name

The profile name should be unique through the system. The server will reject
a profile if its name has been used by other profile.
The Mass Export displays profile based on profile name cross slices. For
example, profile1 can have export group list a from slices1 and group list b
from slices2. In Profile view, click profile1 on status info table, it shows
export information of slice1 and slice2 in NE table. In NE view, click slice1
or slice2, it shows profile1 in profile table.
When user uses Mass Export GUI or archiveAdmin Tool to configure a

profile, the tool makes sure that the profile name is unique in its system.
It may happen that two different profiles have the same name, especially if
user configured profiles by mixed use of archiveAdmin tools and GUI.
If Mass Export detects a profile has the same name as other profile but
different export properties, e.g., destination information, file format, report
period, etc. The Mass Export will clone the profile name and assign to the
profile: <profile>~<number>. It also shows warning messages at bottom. The
mass export will repair profile name up to 9 profiles.
This clone profile name is known only to the GUI. It can still be shown,
disabled, delete, or edit. The Mass Export will change profile name when user
edits the profile
The user should avoid to use the same profile name when profiles have
different properties. Repairing profile names will slow Mass Export GUI
dramatically.
Limit to individual selected groups

Since exporting individual selected groups is much slower than exporting all
groups at down stream processes, the Mass Export GUI limits a maximum of
50 individual selected groups per profile.
OM groups are classified into categories based on the nature of the group.
OM groups from a GEM17.1 server can be in category
<source_type>:CollectedOMgroups or <source_type>:fCorrelationGroups.
OM groups from GEM17 or older server can be in category:
<source_type>:CollectedOMgroups, BillingOMgroups or USPgroups.
Select ALL_GROUPS is in term of down stream process. Groups are broken

into several categories at Mass Export GUI. ALL_GROUPS does not mean
the groups from one category in Mass Export GUI, rather it could be groups
from multiple categories.

A warning window will pop-up when the user selects more than 50 individual
groups. The window will provide hints as to what should be selected to get
ALL_GROUPS from down stream processes point of view.
Customizable OM window 5
The Customizable OM window allows the user to select and manipulate
which OM groups are to be collected. Launch this window by selecting
Customizable OM Window from the Performance menu (Figure 5-1).
Figure 5-53
Customize OM Window
The Customizable OM window (Figure 5-53) consists of the following parts:

• PM Managed Elements Panel: this panel displays all the PM Managed
Elements in a tree, same as Performance Manager Window.
• Customizing Collected OMs Panel: this panel is used to move Collected/
NonCollected OMs list to NonCollected/Collected OMs list. In case the

archive is collecting multiple OM data source types, each tabbed panel

displays the groups list from one data source type.
The Total groups list (collected plus non-collected) includes all the OM
groups known to the CEM data collection servers. The Collected groups
list contains the OM groups the user intends to collect, and the Non-
collected groups list containing all the groups which are in the Total
groups list but not in Collected groups list.
Note: The current Collected groups list may not be the same as the
groups list displayed in the Performance Manager window since the
groups list in Performance Manager window contains all the groups
which have stored data in the Archive server in last 30 days.
• Buttons:
— Apply: by clicking this button, the Collected/NonCollected OMs are
sent to the server.
— Default: by clicking this button, the Collected/NonCollected OMs list
are updated with the default Collected/NonCollected OM lists.
— Refresh: by clicking this button, the Collected/NonCollected OMs list
are updated with the current Collected/NonCollected OM lists from
the server.
— Close: closes the window.
OM Correlation Editor 5
Operational Measurement Correlation Editor Graphical User Interface (OM
Correlation Editor GUI) provides an interface to create or modify correlated
OM Groups which consists of functions as fields. These correlated OM
groups are available for graphing, thresholding and mass export.
A correlation consists of a name, NE types, versions, functions, and copied

input. A correlation name need not be unique, but for a given a combination
of name, NE type, and version there must be only one correlation that satisfies
that criteria.
The name of a correlation is used as the group name in the output. The list of
NE types determines to which NE types the correlation may be applied. The
list of versions determines to which version the correlation applies. A special
version of default indicates that this correlation may be applied to any
versions not specified in other correlations of the same name and NE type.
Functions consist of a name, and a list of operators and operands. The name is
used as the name of the resulting column. The operators and operands are
applied in reverse-polish notation (stack based). An operand is a field, a scalar
value, or a field that is to be summed across all of the tuples and then applied

to each of the tuples as a scalar. An operator is add, subtract, multiply, divide

or calculate percent ( +, -, *, /,% ).
User defined correlations make use of NE type and allow the following:
• Creation of new correlated groups consisting of functions whose inputs
are fields from single-tuple groups. These correlated groups are
distinguished by NE type.
• Creation of new correlated groups, each with functions consisting of
inputs from one multi-tuple group. The correlated group retains the same
name as the original multi-tuple group.
• Correlations only need to be defined once and then they can be applied
multiple times. Once a user defines correlations, the user can apply the
correlations to several proper NE nodes by simply selecting the
correlation name.
• Augmentation of Nortel’s correlations.
ATTENTION
For information on Nortel defined correlations, refer to the GSM/UMTS
Voice Core Network OAM Reference Manual, NTP 411-8111-803.
The OM Correlation Editor GUI (Figure 5-54) is launched by selecting the

“OM Correlation Editor” menu option from the Performance menu in the
Element Manager GUI.

Figure 5-54
OM Correlation Editor - Edit tab pane
Single-tuple correlations
Single-tuple correlations are created by taking inputs as raw fields from other
single-tuple groups. The field is selected from the OM selection area and
based on the selection all the multi-tuple groups are disabled. For single-tuple
correlations, a blue icon along with the label “Single-Tuple Correlation
Definition” is displayed in the “Correlation Definition” area. The correlated
field can be added as an extension field in the group used in the correlation
definition or it can be used to create a new single-tuple group.
Note: For GEM16 or earlier servers, all the correlations are treated as
single-tuple.
Multi-tuple correlations
Multi-tuple correlations are created by taking inputs as raw fields from a
multi-tuple group. Once the field is selected from a multi-tuple group, all the

other OM groups (both multi-tuple and single-tuple) are disabled for

selection. The red icon along with the label “Multi-Tuple Correlation
Definition” is displayed in the “Correlation Definition” area. The correlated
field can be added as an extension field in the existing multi-tuple group or it
can be used for creating a new correlated multi-tuple group.
Note: The correlations cannot be defined with inputs from groups of

different source types. For example, the function cannot have an input
from both BOM:AvailableOMGroups and TRI:AvailableOMGroups.
A user-defined correlation always has a version of default and augmented

correlations applied to the same versions and NE types to which the original
correlation applies.
These correlations are saved in files called UserCorrelations.txt and

UserAugmentations.txt.
Components of the OM Correlation Editor GUI

The window consists of two tab panes, Edit tab and Apply tab, and three
menus: File, Tool and Help.
The File menu consists of the following menu items:

• Export - saves the selected correlations into a file with either Global format
or Local format. The file format is the same as the format stored in the
CEM server.
• Close - closes the OM Correlation Editor window.
The Tool menu contains only one menu item, Get All Correlations....
The Help menu consists of the following menu items:

• MSC OM Reference Manual - displays the MSC OM help documentation.
• USP OM Reference Manual - displays the USP OM help documentation.
• HLR OM Reference Manual - displays the HLR OM help documentation.
• SLR OM Reference Manual - displays the SLR OM help documentation
The Edit tab pane consists of four components:

• First Panel - NE node and OM Selection area
• Second Panel - Correlation Definition area
• Third Panel - List of user and nortel defined correlations
• Forth Panel - Status/Info display area

The Apply tab pane consists of three components:

• First Panel - NE node selection area and OM group/field display area
• Second Panel - Correlation selection area
• Third Panel - Status/Info display area
Export
To store correlations into a file:
1. Select the group names or the field names from the bottom table in the
Edit tab pane to save.
2. Select Export & a file format (Global format / Local format) from the File
menu. A Save dialog box appears.
3. Follow the dialog box to save data into a file.
Get All Correlations

The Get All Correlations... option under the Tool menu collects all correlations
separately located in NE nodes and saves them in one location in the CEM
server which the Global Correlation Manager manages. These correlations
can be applied to any proper NE nodes, which have not had those
correlations, without spending time to edit the correlations again.
Note: The Get All Correlations... command is disabled when working

with GEM17 or earlier NE nodes and standalone SDM nodes.
The Get All Correlations... command collects all correlations applied to each
slice whose version is higher than GEM17. Once all correlations are
collected, a user can save them by using the Save button. Refer to “Save
button” on page 5-115 for more information. If some slices are in BSY or are
down, then the command will not collect correlations from those slices.
After collecting correlations, you may see an error in the correlation table at
the bottom. It indicates that the correlation is conflicted with the same group
name and field name, but different correlation definitions. This is fixed by
deleting some fields and/or groups. These fields are shown with multiple rows
in the right table. After fixing all errors by deleting correlations, the Save
button can be used to save all correlations. After saving all correlations, these
correlations can be used to apply to any NE nodes in the Apply tab pane.
Correlations cannot be submitted until all errors are fixed.
Note: The Get All Correlations... command may delete some correlations
that were edited for GEM18 because this function will collect all
correlations from NE nodes, but not from the Global Correlation Manager
in the GEM18 CEM server.

Edit tab pane

The Edit tab pane (Figure 5-54) is a place to create, modify, and save
correlated OM groups.
When working with GEM18 CEM server, newly defined correlations can be
submitted to multiple NEs at once. All correlations defined by users are saved
and applied to NEs in a more convenient way.
Create a new correlation

To create a new correlated OM group perform the following steps:
1. Select one NE node in Network Elements window in the upper-left. All
correlations previously defined and Nortel defined correlations are then
shown in the table in the lower left corner of the window.
2. When you click a row of the table, all fields defined for the selected
correlation are shown in the table in the lower right corner of the window.
3. Extend a file holder in Collected OMs list until you see field names. A
text description for each group name or field name is displayed as a tool
tip when the cursor linger over that component.
Note: Fields displayed in blue cannot be added to the correlation
definition as they are Nortel defined correlations.
4. Click a field name and the selected field name is shown in the Correlation
Definition area in the middle. Also NE type and Group name of the
selected field are shown in the NE types text box and Group Names
combo box.
5. Click one of operator buttons (+, -, *, /, or %) and the selected operator is
shown in the Correlation Definition area. You can also click on the ( )
button which can be used to enclose valid arithmetic expressions for
evaluation.
The % operator makes the definition a percentage. To apply the %

operator for a whole definition, click % button and the entire definition is
parenthesized and multiplied by 100. To apply the % operator for a part of
a definition, highlight a part you want to apply and click % button. An
error message will be displayed in the Status/Information box if the
highlighted part is not valid.
6. Click a field name again or input some number in the constant box.
7. Click the Enter button. The selected field name or number is shown in the
Correlation Definition area.
8. Now you can type in a field name in the Field Name text box before
clicking the Apply button.
9. If you want to have a Tool tip, type description for this field in the Tool
Tip description text box before clicking the Apply button.

10. To add more in the Correlation Definition, repeat the above steps to add
field names and operators.
The following buttons perform different actions on the correlation definition:

• <-- - deletes the last term in the Correlation Definition. When a close
parenthesis is deleted by the backspace button, the matching open
parenthesis is deleted too.
• Undo - provided for undoing the actions.
• Redo - provided for redoing the actions.
• Clear - clears the Correlation Definition.
• Apply - places an editing correlation to the table of correlations instead of
submitting the new correlation to the selected NE node. The new
correlation added into the table is highlighted.
• Cancel - cancels the edit operation for the existing user defined
correlation.
You can make a new name in the Group Name combo box for a new
correlation.
Note: There is a limitation for naming a new correlation and field. The
maximum length of the name is 80. Available characters are a-z, A-Z, 0-9,
and _.
After editing correlations and storing them into the correlation table, you can
save them in the CEM server so that other operators can use them.
Note: For NE nodes in GEM17.0 CEM server and standalone SDM

nodes, the Save and Submit buttons are disabled.
A user can apply correlations to preferred NE nodes in the Apply tab pane
after saving correlations defined in the Edit tab pane. Refer to “Apply tab
pane” on page 5-116 for more information.
Pop-up menus
All the changes done for the correlation table are saved at the server.
There are some pop-up menus which can be launched by clicking the right
mouse button in the Correlation table.
For a user defined correlation, there are two pop-up menus. One has two
commands, Edit and Delete, in the left table where NE types, Version, and
Group name are displayed. The other pop-up menu has three commands:
Edit, Copy and Delete, in the right table that displays Field name, Field
definition, and Tool tip description.

Figure 5-55
Pop-up menu for user defined correlation - left table
Figure 5-56
Pop-up menu for user defined correlation - right table
For a Nortel defined correlation, there is no pop-up menu in the left table, but
in the right table there is a pop-up menu with two commands: Show and
Copy.
Figure 5-57
Pop-up menu for Nortel defined correlation - right table
The Delete command in the pop-up menu deletes a selected item. When a
group name is selected in the left table and delete command is executed, the
group name is deleted after the user confirms that it needs to be deleted
(Figure 5-58). When a field name is selected in the right table and the delete
command is executed, the selected field name is deleted. If the deleted field
name is the last field name under the selected group name, then the group
name will be deleted too.

Figure 5-58
Delete confirmation
The Edit, Copy, and Show commands fill the Correlation editing area with
data of selected group name or field name.
To change a field name shown in the right table:

1. Select a field name you want to modify.
2. Click the right mouse button on it to get a pop-up menu.
3. Select the Edit command.
All data for a selected correlation/function are displayed in the editing area.
Also a correlation definition and tool tip description can be modified here.
Since a group name cannot be changed by this edit command, the group name
combo box is disabled.
To change a group name, use the Edit command in a pop-up menu in the left
side of the correlation table. This command allows a user to change only a
group name.
Note: Users are not allowed to modify the Nortel defined correlations, so
there is no Edit command for the Nortel defined correlations.
To add a new field by modifying an existing field:

1. Click the right mouse button in the right table to get a pop-up menu.
2. Select the Copy command. It fills the editing area with the data of the
existing field.
3. Modify the data as needed.
4. Type in a new field name.
5. Click the Apply button and the new field name is added in the right table.
If the field name is not changed, then no new field name is added but your
other modifications are applied.
The Copy command can also be used to augment a Nortel defined correlation.
This allows a user to add a new field under the Nortel defined correlation.

The Show command displays long correlation definitions which are too long
to display in the Correlation table. The Show command for Nortel defined
correlations only displays data of the selected field name. All components for
editing correlations are disabled, so no data can be changed here.
Figure 5-59
OM Correlation Editor - using the Show command to display a long definition
Save button
The Save button invokes the Save function to save all of correlations created
in the Edit tab pane into files in the CEM server. All saved correlations can be
applied to proper NE nodes in the Apply tab pane. A confirmation dialog box
(Figure 5-60) appears to confirm that the user wants to save data.

Figure 5-60
Save confirmation
Note: When a GEM17.0 or earlier NE node or standalone SDM node are

selected in the Edit tab pane, the Save button is disabled. To submit or
delete a correlation, use the Apply button and the Delete command in the
pop-up menu on the right table.
Refresh button
The Refresh button makes all data revert to previously saved data. All
unsaved correlations are discarded after executing the refresh button. A
confirmation dialog box appears to confirm that the user wants to refresh data.
Apply tab pane

The Apply tab pane is a place to submit correlations created in the Edit tab
pane to selected NE nodes.
When you select a NE node from the list of Network Elements, all
correlations already assigned to that node are shown in the Selected
Correlations list box and all available correlations for NE type of the selected
node are shown in the Available Correlations list box.
The << button moves a selected correlation from the Available Correlations
list to the Selected Correlations list. When you select a correlation in the
Available Correlations list, the << button becomes enabled. When a
correlation is deselected, the << button goes back to disabled.
The >> button moves a selected correlation from the Selected Correlations list
to the Available Correlations list. When you select a correlation in the
Selected Correlations list, the >> button becomes enabled. When a correlation
is deselected, the >> button goes back to disabled.
The Submit button submits all correlations in the Selected Correlations list to
the selected NE node.

Figure 5-61
OM Correlation Editor - Apply tab pane
When the Submit button is pressed, a confirmation dialog box appears to

confirm that the user does want to submit the selected correlations. If the Yes
button is selected, then the selected correlations are submitted. If the No
button is selected, then the selected correlations are not submitted. After
submitting successfully, the correlations in the Selected Correlations list are
sorted by Group names.
If there are some correlations in the Selected Correlations list which have
already been deleted in the Edit tab pane, those correlations will not be shown
in the Selected Correlations list after submitting successfully. If some
correlations, not new correlations, in the Edit tab pane are modified or deleted
and those correlations need to be applied to NE nodes, click the Submit
button for each affected NE node in order to update those correlations in the
NE nodes.

Note: For GEM17.0 or earlier NE nodes and standalone SDM nodes, the
Submit button is disabled. To submit data for these nodes, use the Apply
button in the Edit tab pane.
The Refresh button makes all the data revert to the previously submitted data.
If there are no available correlations for the NE type of a selected NE node

and no assigned correlations to the selected NE node, then no correlations are
displayed in either the Selected Correlations and Available Correlations lists.
If multiple NE nodes are selected with different NE types, then all user
defined correlations which are defined for at least one of the selected NE
types are shown in the Available Correlations list.
OM Correlation Editor restrictions and limitations

1. When a user defines a new correlation for an NE, this correlation will
automatically be applied to all other NEs of the same type under the same
slice. A user cannot define distinguishable correlations for a specific NE if
there are NEs of the same type under the same slice.
2. A user cannot define a new correlation definition using any correlations
that were defined by Nortel or other users. These correlations are
displayed in blue in the OM Correlation Editor.
3. For GEM17.0 NE nodes and NE nodes for stand-alone SDM, any fields
from multiple tuple OM groups will be rejected while the user is editing a
correlation definition in the Edit tab.

6-1
Call trace 6
Call Trace is a feature that generates call trace records using the Nortel
Supernode Data Manage-Fault Tolerant (SDM/FT) and the Nortel Mobile
Switching Center/Home Location Register (MSC/HLR).
Call trace is activated through the Element Manager browser. The SDM/FT
layer receives the data and activates the trace on the HLR100 or the MSC.
The MSC generates a Call Trace Record (CTR) and delivers it to the SDM/FT
layer. The SDM/FT layer formats the CTR into a call trace record (CTR) and
stores it on the SDM/FT in the Call Trace Database. It also forwards the CTR,
in real-time, to the connected Element Manager browsers in the network.
Call trace menu 6

Call Trace is accessed from the Element Manager browser main menu.
Selecting Call Trace opens a drop-down menu (Figure 6-1) with three
options: Activate/Deactivate Trace, Manage Trace Records and Disable
Query to HLR.
Figure 6-1
Accessing Call Trace
Activate/deactivate trace 6
Activate/Deactivate Trace allows the user to begin or end the tracing of
selected calls. Selecting Activate/Deactivate Trace from the Call Trace drop-
down menu opens the Call Trace Activate/Deactivate window shown in
Figure 6-2.

6-2 Call trace
Figure 6-2
Call Trace Activate/Deactivate window
The Call Trace Activate /Deactivate window contains a menu bar, tabbed
sections, a status window, and selection buttons.
Restrictions and limitations

• If a Call Trace Activate/Deactivate window is already open and the user
attempts to open another Call Trace Activate/Deactivate window, the
already opened Call Trace Activate/Deactivate window is displayed.
• Only users who have security clearance can invoke Call Trace Activate/
Deactivate. Users who login as observer and attempt to invoke Call Trace
will see the Non Call Trace User Error window shown in Figure 6-3.
Figure 6-3
Non Call Trace User Error Window

Call trace 6-3
Call trace activate/deactivate menu bar

The menu bar contains two options: File and Help. Selecting File opens a
drop-down menu with options to print or close. Under Print, there are four
print options corresponding to the four tabs (Figure 6-4), International Mobile
Subscriber Identity (IMSI), Mobile Station International ISDN Number
(MSISDN), Trunk, and Public Switching Telephone Network (PSTN).
Figure 6-4
Print menu options
Selecting one of these options prints the information as it appears under the
corresponding tab. Figure 6-5 is an example of an IMSI print.

6-4 Call trace
Figure 6-5
IMSI Print Report
This report printed at Thu May 16 07:26:09 CDT 2002
IMSI : 505023501205000
Status : Active
Network Element : GSMVSOS
Trace Reference : 1234
BSS Record Type : Basic
MSC Record Type : Basic
Invoking Event : MOC, MTC, SMS MO, SMS MT, SS, Location
Updates, IMSI attach/detach
__________________________________________
IMSI : 505023501205001
Status : Active
Network Element : GSMVSOS
Trace Reference : 333
BSS Record Type : Radio
MSC Record Type : Basic
Invoking Event : MOC, MTC, SMS MO, SMS MT, SS, Location
Updates, IMSI attach/detach
__________________________________________
Under the Help option, there are two sub-items: User’s Guide and About Call
Trace. Selecting User’s Guide opens an on-line help manual. About Call
Trace provides the current version number of the Element Browser Call Trace
feature being used. See Figure 6-6.

Call trace 6-5
Figure 6-6
About Call Trace
Call trace activate/deactivate window tabs

The following four tabs appear in the Call Trace Activate/Deactivate window:
• IMSI - Allows activation of call trace based on the subscriber’s
International Mobile Subscriber Identity. This tab also allows deactivation
of any previously activated IMSI based calls.
• MSISDN - Allows activation of call trace based on the subscriber’s
Mobile Station International ISDN Number. This tab also allows
deactivation of any previously activated MSISDN based calls.
• TRUNK - Allows activation of call trace based on the Trunk ID. It allows
deactivation of any previously activated Trunk ID based calls.
• PSTN - Allows activation of call trace based on a Public Switching
Telephone Network number. This also allows deactivation of any
previously activated PSTN based calls.
IMSI tab panel

Selecting the IMSI tab displays a list of all activations based on the
subscriber’s IMSI (Figure 6-7). This list includes all current, pending, and
failed activations. An empty list indicates no existing, pending, or failed trace
activations on any of the defined Network Elements.

6-6 Call trace
Figure 6-7
IMSI tab
The IMSI tab window contains the following seven fields:

• Status - Indicates if the corresponding activation is in active (black text),
pending (blue text), or failed (red text) mode.
• Network Element - Contains the name of the MSC or the HLR100 on
which that particular trace was activated.
• IMSI - Contains the Subscriber’s IMSI.
• Trace Reference - Contains a unique trace reference number for that
particular IMSI.
• BSS Record Type - Describes the type of records to be collected on the
BSS.
• MSC Record Type - Describes the type of records to be collected on the
MSC.
• Invoking Events - Describes the invoking events for a collected trace
record for the given IMSI in the MSC or the BSS.

Call trace 6-7
There are three buttons located at the bottom of the IMSI tab panel. These
buttons are:
• Activate - opens the Activate Trace window.
• Deactivate - This button is enabled when one or more activations are
selected from the given list. Once the activations are selected and the
Deactivate button is clicked, a prompt appears verifying the deactivation
selection (Figure 6-8). Clicking the Yes button deactivates the selection
from the corresponding Network Elements. Selected activations with a
failed status are deleted from the list and no longer exist in the system.
Figure 6-8
Deactivation confirmation prompt
• Close - closes the Call Trace Activate/Deactivate window.
IMSI Activate Trace window

Clicking on the Activate button in the Call Trace Activate/Deactivate window
brings up the Activate Trace window (Figure 6-9) which allows entering of
trace activation related data.

6-8 Call trace
Figure 6-9
IMSI Activate Trace window
Note: Right-clicking on an active IMSI on the Call Trace Activate/

Deactivate window brings up a pop-up menu which also allows for
activation or deactivation of the call trace feature.
The IMSI Activate Trace window contains five fields:

• IMSI - Used to enter the Subscriber’s IMSI. This field accepts a
maximum of 15 numeric characters. The IMSI is validated at the HLR
when all of the other fields are datafilled and the OK button is pressed.
• Trace Reference - Used to enter an identifier, that when combined with
the given IMSI, uniquely identifies an individual active trace within the
network. This field accepts a maximum of 5 numeric characters. The
value of the entered numeric value cannot exceed 65535.
• BSS Record Type - This field allows for the selection of the BSS record
type to be collected. The choices are Basic, Handover, Radio, and No
Trace.
• MSC Record Type - This field allows for the selection of the MSC record
type to be collected. The choices are Basic and No Trace.

Call trace 6-9
• Invoking Event - This field allows for the selection for an invoking event
for a selected trace record. The choices are:
— MOC, MTC, SMS-MO, SMS-MT, SS, Location Updates, IMSI
Attach/Detach;
— MOC, MTC, SMS-MO, SMS-MT, SS only;
— Location Updates, IMSI Attach/Detach.
Once the desired values have been entered and the OK button clicked, the
system verifies that all of the fields have a value. If either the IMSI or Trace
Reference field is left blank, a warning message displays. The types of
warning messages are discussed in detail later in this chapter.
Note: Clicking the Cancel button at any time discards any entered data
and closes the Activate Trace window.
Upon verification of the datafill, the system sends the IMSI and its related
data to the HLR100 for activation. The HLR100 automatically accepts home
subscriber IMSIs. If the IMSI belongs to a foreign subscriber, a prompt
appears for activating the trace as a foreign subscriber (Figure 6-10).
Figure 6-10
Foreign Subscriber prompt
MSISDN tab panel

Selecting the MSISDN tab displays a list of all activations based on the
subscriber’s MSISDN (Figure 6-11). This list includes all current, pending,
and failed activations. Failed activations are viewable as long as the browser
remains open. Once the browser is closed, the failed activations are deleted
from the system and will not display again.
An empty list indicates no existing, pending, or failed trace activations on any

of the defined Network Elements.

6-10 Call trace
Figure 6-11
MSISDN tab
The MSISDN tab window contains the following five fields:

• Network Element - Contains the name of the MSC on which that
particular trace activated.
• MSISDN - Contains the Subscriber’s MSISDN.
• Trace Reference - Contains a unique trace reference number for that
particular MSISDN.
• Invoking Events - Describes the invoking events for a collected trace
record for the given MSISDN on the MSC.
There are three buttons located at the bottom of the MSISDN tab panel. These
buttons are:
Deactivate button is clicked, a prompt appears verifying deactivation

Call trace 6-11
MSISDN activate trace window

Clicking on the Activate button brings up the Activate Trace window (Figure
6-12) which allows entering of trace activation related data.
Figure 6-12
MSISDN Activate Trace window
Note: Right-clicking on an active MSISDN on the MSISDN tab panel

brings up a pop-up menu allowing for activation or deactivation.
The MSISDN Activate Trace window contains four fields:

• MSISDN - Used to enter the Subscriber’s MSISDN. This field accepts a
maximum of 15 numeric characters.
• Trace Reference - Used to enter an identifier, that when combined with
the given MSISDN, uniquely identifies an individual active trace within
the network. This field accepts a maximum of 5 numeric characters. The
value of the entered numeric value cannot exceed 65535.
• Invoke Event - Allows for the selection for an invoking event for a
selected trace record. The choices are:
— MOC, MTC, SMS-MO, SMS-MT, SS, Location Updates, IMSI
Attach, IMSI Detach;
— MOC, MTC, SMS-MO, SMS-MT, SS only;
— Location Updates, IMSI Attach, IMSI Detach only.

6-12 Call trace
• This window also contains a field for selecting the Network Element on
the MSC. The Network Element: MSC List provides a list of available
MSCs in the network. More than one MSC may be selected.
system verifies that all of the fields have a value. If either the MSISDN or
Trace Reference field is left blank, or the Network Element is absent, a
warning message appears. These warning messages are described in detail
later in this chapter.
Upon verification of the datafill, the system sends the MSISDN and its related
data to the MSC for activation.
Trunk tab panel

Selecting the Trunk tab displays a list of all activations based on the
subscriber’s Trunk ID (Figure 6-13). This list includes all current, pending,
and failed activations. An empty list indicates no existing, pending, or failed
trace activations on any of the defined Network Elements.

Call trace 6-13
Figure 6-13
Trunk tab
The Trunk tab window contains the following five fields:

• Network Element - Contains the name of the MSC or the HLR100 on
which that particular trace was activated.
• Trunk ID - Contains the PRI_ETSI or ETSI-ISUP Trunk ID.
• Trace Reference - Contains the unique identifier for a given Trunk ID.
• Range to Trace- Lists the range(s) of the trunk member in the group for
call tracing. If All is selected, the text string Selected all trunk member
displays in this field.
There are three buttons located at the bottom of the Trunk tab panel. These
buttons are:

6-14 Call trace

Trunk activate trace window

Clicking on the Activate button brings up the Trunk Activate Trace window
(Figure 6-14) which allows entering of trace activation related data.
Figure 6-14
Trunk Activate Trace window
Note: Right-clicking on an active Trunk ID on the Trunk tab panel brings

up a pop-up menu allowing for activation or deactivation.

Call trace 6-15
At the top of the Trunk Activate Trace window is a field for Trunk ID. This
field is used to enter the PRI-ISUP or an ETSI-ISUP Trunk ID. A maximum
of 18 alphanumeric characters, including underscore, can be entered in this
field.
The next field is Trace Reference. This field is used to enter an identifier, that
when combined with the given Trunk ID, uniquely identifies an individual
active trace within the network. This field accepts a maximum of 5 numeric
characters. The value of the numeric input cannot exceed 65535.
There are two options for Range value. Choosing All activates traces on all
Trunk members in this group. When Range is selected, the From and To fields
are enabled. These fields accept an input value from 0 to 9999. Up to 10
ranges are allowed. The All and Range fields are mutually exclusive. Only
one may be selected for each trace.
The From field value cannot exceed that of the To field value and no
overlapping ranges are allowed. For each additional range, both the From and
To fields must contain data. If only one trunk member needs to be traced, set
both fields to the same value.
The last field is the Network Element: MSC List. This provides a drop-down
list of the available MSCs in the Network.
system verifies that all of the fields have a value. If data is missing from any
of the fields, the Network Element is absent, or range values are incorrect,
warning messages appear. The types of warning messages are discussed in
detail later in this chapter.
Upon verification of the datafill, the system sends the Trunk ID and its related
data to the MSC for activation.
PSTN tab panel

Selecting the PSTN tab displays a list of all activations based on the
subscriber’s PSTN (Figure 6-15). This list includes all current, pending, and
failed activations. An empty list indicates no existing, pending, or failed trace
activations on any of the defined Network Elements.

6-16 Call trace
Figure 6-15
PSTN tab panel
The PSTN tab window contains the following five fields:

• Network Element - Contains the name of the MSC on which that
particular trace was activated.
• PSTN Number - Contains the Subscriber’s PSTN number being traced.
• Trace Reference - Contains an identifier, that when combined with the
given PSTN, uniquely identifies an individual active trace within the
network.
• PSTN Trace Represents - This field displays the origin of the PSTN
Number selected.
There are three buttons located at the bottom of the Trunk tab panel. These
buttons are:

Call trace 6-17
PSTN trace window

Clicking on the Activate button brings up the PSTN Activate Trace window
(Figure 6-16) which allows entering of PSTN number based trace related
data.
Figure 6-16
PSTN Activate Trace window
Note: Right-clicking on an active PSTN number on the PSTN tab panel

brings up a pop-up menu allowing for activation or deactivation.
At the top of the PSTN Activate Trace window is a field for the PSTN
number. This field is used to enter the PSTN number on which the trace is to
be performed. A maximum of 15 numeric characters can be entered in this
field.
The next field is “Trace Reference.” This field is used to enter an identifier
that, when combined with the given PSTN number, uniquely identifies an
individual active trace within the network. This field accepts a maximum of 5
numeric characters. The value of the numeric input cannot exceed 65535.
The “PSTN Trace Represents” field allows for the selection of the number to
be traced. The drop-down menu includes: Calling Number, Called Number, or
Both Numbers.

6-18 Call trace
The last field is the “Network Element: MSC List.” This field provides a
drop-down list of the MSCs in the Network.
system verifies that all of the fields have a value. If data is missing from any
of the fields or the Network Element is absent, warning messages appear. The
types of warning messages are discussed in detail later in this chapter.
Upon verification of the datafill, the system sends the PSTN number and its
related data to the MSC for activation.
Call trace activate/deactivate warning messages

The following warning messages (Figure 6-17, Figure 6-18, Figure 6-19, and
Figure 6-20) appear when activating call trace from any of the tab panels and
the IMSI, MSISDN, Trunk ID, or PSTN Number fields are left blank.
Figure 6-17
Blank IMSI warning
Figure 6-18
Blank MSISDN warning

Call trace 6-19
Figure 6-19
Blank Trunk ID warning
Figure 6-20
Blank PSTN Number warning
The following warning message (Figure 6-21) appears when activating call
trace from any of the tab panels and the Trace Reference Number is left blank.
Figure 6-21
Blank Trace Reference warning
The following warning messages (Figure 6-22, Figure 6-23, Figure 6-24, and
Figure 6-25) appear when activating call trace from any of the tab panels and
the requested trace is already active.

6-20 Call trace
Figure 6-22
Activated IMSI warning
Figure 6-23
Activated MSISDN warning
Figure 6-24
Activated Trunk ID warning

Call trace 6-21
Figure 6-25
Activated PSTN warning
The following error message (Figure 6-26) appears when activating call trace
from the MSISDN, Trunk ID, or PSTN Number tab and the Network Element
is absent.
Figure 6-26
Network Element warning
The following warning messages display when activating call trace on a

Trunk ID and no range is selected (Figure 6-27), an incomplete range is given
(Figure 6-28), or an overlapping range is provided (Figure 6-29).
Figure 6-27
Range Input warning

6-22 Call trace
Figure 6-28
Incomplete Range warning
Figure 6-29
Overlapping Range warning
Manage trace records 6

Selecting Manage Trace Records from the Call Trace drop-down menu opens
the Manage Trace Records window shown in Figure 6-30.
Note: If a Manage Trace Records window is already open and the user
attempts to open another Manage Trace Records window, the already
opened Manage Trace Records window is displayed.

Call trace 6-23
Figure 6-30
Manage Trace Records window
The Manage Trace Records window contains a summary list of all current
records existing within the Call Trace system. This list represents the trace
records generated by the MSCs in the network along with the corresponding
SDM/FTs that successfully delivered the records to the Element Manager
browser.
The Manage Trace Records window consists of a menu bar, a record count
display, IMSI, MSISDN, Trunk, and PSTN toggle buttons, a Filter field, the
records summary table, and a histogram located at the bottom of the screen.
A pop-up menu is available in this window by clicking on the right mouse

button. The pop-up menu has two options: Delete and View.
Manage trace records menu bar

The menu bar contains two options: File and Help. Selecting File opens a drop-
down menu with the following options:
• Export - Retrieves all of the existing trace records in the system and stores
them in a file on the OMC-S Network Element Manager server. If there
are no existing records, a warning message displays (Figure 6-31)
indicating that there are no records to be exported.

6-24 Call trace
Figure 6-31
No records export warning
• Print - Prints all existing trace records directly to the designated printer. If
no records exist in the system, a message displays indicating there are no
records to print.
• Close - Closes the window and exits the user from the Manage Trace
Records function.
Selecting Help from the Manage Trace Records menu bar opens a drop-down
menu with the following options:
• About Manage Trace Records - Displays up the version window.
• User’s Guide - Displays an on-line help manual.
A records count display appears directly below the menu bar. This display
provides a count of all trace records for a given date and time range.
Manage trace records toggle buttons

Below the menu bar in the Manage Trace Records window are six toggle
buttons. Table 6-1 provides a description of each of the buttons.
Table 6-1
Manage Trace Records toggle buttons’ descriptions
IMSI Depressing this button removes any existing

IMSI related trace records from the
displayed list and disables the display of any
new IMSI related trace records listings.
MSISDN Depressing this button removes any existing

MSISDN related trace records from the
new MSISDN related trace record listings.
—sheet 1 of 2—

Call trace 6-25
Table 6-1
Manage Trace Records toggle buttons’ descriptions
Trunk Depressing this button removes any existing

Trunk ID related trace records from the
new Trunk ID related trace record listings.
PSTN Depressing this button removes any existing

PSTN related trace records from the
new PSTN related trace record listings.
Zoom In Depressing this button zooms in on the

histogram, decreasing the date range.
Zoom Out Depressing this button zooms out on the

histogram increasing the date range.
—sheet 2 of 2—
Manage trace records filter field

On the same line as the toggle buttons is a Filter field. This field allows the
user to enter a text string that filters out and displays only the trace records
that contain the matching string. The filter string is compared against all of
the fields. The Filter field is case sensitive. Once the desired text is entered in
the field, pressing the Enter button begins the filtering process.
For example, entering Disconnect in the Filter field allows only trace records
with the word Disconnect in the record to be displayed. Figure 6-32 and
Figure 6-33 illustrate the filtering process.

6-26 Call trace
Figure 6-32
Example of Filtering text string
Figure 6-33
Example of Filtering results
Manage trace records histogram

The Manage Trace Records histogram controls the traced record display that
appears in the Manage Trace Records summary list.

Call trace 6-27
The arrows to the far left and right of the histogram area adjust the date and
time range for the trace records display.
To display a summary list, depress the T toggle button and drag the
rectangular box located in the histogram area until it encompasses the stacked
bar representing call trace records. See Figure 6-34.
Figure 6-34
Selecting tracking of Trace records
The X axis represents the date and time range selected for call trace records.
The Y axis represents the number of records generated for the selected time
frame. See Figure 6-35.
Figure 6-35
Histogram X and Y axis

6-28 Call trace
Once the date and time range is selected, the summary list appears in the
Manage Trace Records window summary area. From here, users can view the
list of existing call trace records within the call trace system.
Manage trace records summary list

The Manage Trace Records summary (Figure 6-36) provides a listing of all
trace records generated using the criteria specified in the Manage Trace
Records histogram.
Figure 6-36
Manage Trace Records summary list
The Manage Trace Records summary list contains the following seven fields:
• T - Indicates the activation type The four types of activation are color
coded to match the toggle buttons located below the menu bar.
— I - Subscriber’s IMSI. This activation is also indicated with a
background color of blue.
— M - Subscriber’s MSISDN. This activation is also indicated with a
background color of green.
— T - Trunk ID. This activation is also indicated with a background
color of yellow.

Call trace 6-29
— P - PSTN Number. This activation is also indicated with a background

color of pink.
• N - Indicates if any notes are attached to the corresponding record.
• Network Element - Indicates the Network Element name, such as the
MSC name, where the corresponding trace record was generated.
• Traced Party ID - Indicates the identity of the traced entity. The value of
this field is based upon the activation type.
• Date-Time - Indicates the date and time of the corresponding MSC
generated trace record.
• Trace Reference - Indicates the trace reference associated with the
corresponding trace activation for the generated record.
• Event - Indicates the event type for the generated trace record.
Delete trace records

The Delete option is to delete the selected record(s). One or more records can
be selected and deleted at a time. Once the record(s) is selected, right-clicking
displays a pop-up menu with two selections: Delete and View. Select Delete
to remove the selected record(s).
View trace record window

The View Trace Record window allows the user to view the full content of the
selected record. This option is disabled if no record is selected or if multiple
records are selected.
To access this window, select a record from the Manage Trace Records
summary list. Once the record is selected, right-click to display the pop-up
menu. Selecting View opens up the Trace Record Window (Figure 6-37).
Note: Double-clicking on the record also brings up the Trace Records

window.

6-30 Call trace
Figure 6-37
View Trace Record window

Call trace 6-31
View trace record window fields

The View Trace Record window provides detailed information on the selected
record. This window also provides a text box for any notes the user wishes to
enter concerning the selected record. Under the Notes text box are five
selection buttons (Figure 6-38).
Figure 6-38
Notes text box with buttons
The five buttons enable the following functions:

• OK - Initiates the closing of the window. If there are any unsaved notes, a
prompt appears giving the user the option to save the notes.
• Save Notes - Saves notes entered in the Notes text box. This button is only
enabled when notes have been entered into the text box. Once the notes
are saved, they become part of the Trace Record and are indicated by a
yellow box with the letter N in the Notes column. (Figure 6-39)

6-32 Call trace
Figure 6-39
Example of Notes indication
• Delete Notes - Deletes notes entered in the Notes text box. This button is
only enabled when notes have been entered into the text box or previously
entered notes are displayed.
• Print - Prints the entire displayed record and any associated notes.
• Help - Not active at this time.
Call trace record examples

Call Trace Records are formatted as per the GSM 12.08 specification. Call
Trace Record (CTR) examples are shown below. The content of the CTR will
depend on the particular call scenario and the availability of data received
from the MSC.

Call trace 6-33
Figure 6-40
Location Update CTR Example
Header:
tracedParty [0]: MSISDN: 61411215075
tracedReference [1]: 1
omcID [3]: 45678
mscBssTraceType [4]: 0x00
startTime [8]: 2002-08-12 15:56:58.071
endTime [9]: 2002-08-12 15:56:58.071
recordingEntity [10]: 614181000000
traceEventRecords [11]:
invokingEvent [0]: Location Update
servedIMSI [1]: 505024101215075
location [19]:
Traced Party Location [1]: LAC: 301 Cell ID/SAC: 6
Other Party location [2]: Not Available
msClassmark [22]: 1F 00 FF FF FF FF
startTime [31]: 2002-08-12 15:56:58.071
endTime [32]: 2002-08-12 15:56:58.071
eventNumber [33]: 0000
sequenceNumber [12]: 1000
recordReason [13]: Location Update type - 00

6-34 Call trace
Figure 6-41
Setup CTR Example
Header:
tracedParty [0]: PSTN_DN: 61410315000
omcID [3]:
startTime [8]: 2002-08-12 09:00:33.007
endTime [9]: 2002-08-12 09:00:33.007
invokingEvent [0]: PSTN Terminated Call
callingcalledNumber [4]:
callingNumber [1]: Calling Num: 61410316100#E.164#Internatio
Number
calledNumber [2]: Called Num: 61410315000#E.164#National Num
translatedNumber [7]: #None#Others
originalCalledNumber [12]: 61410315000#E.164#National Number
roamingNumber [13]: #None#Others
networkTKGP [14]: incoming: ETSIISUPS1-2
basicService [15]: Telephony
location [19]:
Traced Party Location [1]: Not Available
Other Party Location [2]: Not Available
startTime [31]: 2002-08-12 09:00:33.007
endTime [32]: 2002-08-12 09:00:33.007
eventNumber [33]: 9F7F
recordReason [13]: Setup

omcID [3]:
startTime [8]: 2002-08-12 09:00:33.007
endTime [9]: 2002-08-12 09:00:33.007
invokingEvent [0]: PSTN Terminated Call
callingNumber [1]: Calling Num: 61410316100#E.164#Internat
Number
calledNumber [2]: Called Num: 61410315000#E.164#National N
translatedNumber [7]: #None#Others
originalCalledNumber [12]: 61410315000#E.164#National Number
roamingNumber [13]: #None#Others
networkTKGP [14]: incoming: ETSIISUPS1-2
location [19]:

Call trace 6-35
Figure 6-42
Answer CTR Example
Header:
omcID [3]:
startTime [8]: 2002-08-12 09:13:13.074
endTime [9]: 2002-08-12 09:13:13.074
invokingEvent [0]: PSTN Originated Call
callingNumber [1]: Original Calling Num:
61410315010#E.164#International Number
calledNumber [2]: Called Num: 61410315000#E.164#National N
connectedNumber [8]: #None#Others
networkTKGP [14]: outgoing: ETSIISUPP-1
location [19]:
startTime [31]: 2002-08-12 09:13:13.074
endTime [32]: 2002-08-12 09:13:13.074
eventNumber [33]: 108F
recordReason [13]: Answer
Figure 6-43
Disconnect CTR Example
Header:
omcID [3]:
startTime [8]: 2002-08-12 09:11:17.061
endTime [9]: 2002-08-12 09:11:17.061
invokingEvent [0]: PSTN Originated Call
location [19]:
startTime [31]: 2002-08-12 09:11:17.061
endTime [32]: 2002-08-12 09:11:17.061
eventNumber [33]: FF7F
recordReason [13]: Disconnect

6-36 Call trace
Figure 6-44
Redirection CTR Example
Header:
transactionID [2]: 0
omcID [3]: 45678
startTime [8]: 2002-08-12 16:24:47.057
endTime [9]: 2002-08-12 16:24:47.057
invokingEvent [0]: MSISDN Terminated Call
servedIMSI [1]: 505024101215001
callingcalledNumber [4]: Original Calling Num:
61411215000#E.164#International Number
forwardedToNumber [9]: 61411215002#E.164#International Number
redirectingNumber [11]: 61411215001#E.164#International Number
originalCalledNumber [12]: 61411215001#E.164#International Number
location [19]:
ssInformation [20]:
supplServicesUsed [1]: CFNRy
ssAction [3]: invocation (5)
msClassmark [22]: 1F 02 20 10 FF FF
startTime [31]: 2002-08-12 16:24:47.057
endTime [32]: 2002-08-12 16:24:47.057
recordReason [13]: Redirection

Call trace 6-37
Figure 6-45
CISS CTR Example
Header:
omcID [3]: 45678
startTime [8]: 2002-08-12 16:22:10.012
endTime [9]: 2002-08-12 16:22:10.012
invokingEvent [0]: ssAction (CISS)
servedIMSI [1]: 505024101215042
location [19]:
ssInformation [20]:
supplServicesUsed [1]: CFU
basicServices [2]: Speech Transmission
ssAction [3]: CISS Operation: Register Supplemen
Service.
ssParameters [4]: Forwarded to Number 61411215043#Un
fined#Subscriber
ssActionResult [5]: Return Result Value: Normal Cleari
ssActionResult [5]: Return Error Code: Nil Error
basicServices [2]: Service 1 Speech Transmission
ssActionResult [5]: Operative, Provisioned, Registered
Active
ssInvokeId [6]: 10
msClassmark [22]: 1F 03 20 10 00 FF
startTime [31]: 2002-08-12 16:22:10.012
endTime [32]: 2002-08-12 16:22:10.012
recordReason [13]: CISS

6-38 Call trace
Figure 6-46
Detach CTR Example
Header:
omcID [3]: 45678
startTime [8]: 2002-08-12 16:31:37.012
endTime [9]: 2002-08-12 16:31:37.012
invokingEvent [0]: IMSI Detach
servedIMSI [1]: 505024101215052
location [19]:
msClassmark [22]: 1F 00 FF FF FF FF
startTime [31]: 2002-08-12 16:31:37.012
endTime [32]: 2002-08-12 16:31:37.012
eventNumber [33]: 0000
recordReason [13]: Detach
Figure 6-47
Call Hold CTR Example
Header:
omcID [3]: 45678
startTime [8]: 2002-08-12 16:33:10.003
endTime [9]: 2002-08-12 16:33:10.003
invokingEvent [0]: MSISDN Originated Call
servedIMSI [1]: 505024101215070
location [19]:
startTime [31]: 2002-08-12 16:33:10.003
endTime [32]: 2002-08-12 16:33:10.003
recordReason [13]: Call Hold

Call trace 6-39
Figure 6-48
Call Retrieve CTR Example
Header:
omcID [3]: 45678
startTime [8]: 2002-08-12 16:33:41.072
endTime [9]: 2002-08-12 16:33:41.072
servedIMSI [1]: 505024101215070
location [19]:
startTime [31]: 2002-08-12 16:33:41.072
endTime [32]: 2002-08-12 16:33:41.072
recordReason [13]: Call Retrieve
Figure 6-49
Call Waiting CTR Example
Header:
omcID [3]: 45678
startTime [8]: 2002-08-12 16:35:39.025
endTime [9]: 2002-08-12 16:35:39.025
servedIMSI [1]: 505024101215070
location [19]:
startTime [31]: 2002-08-12 16:35:39.025
endTime [32]: 2002-08-12 16:35:39.025
recordReason [13]: Call Waiting

6-40 Call trace
Figure 6-50
Call Barring CTR Example
Header:
omcID [3]: 45678
startTime [8]: 2002-08-12 16:38:32.030
endTime [9]: 2002-08-12 16:38:32.030
servedIMSI [1]: 505024101215070
location [19]:
ssInformation [20]:
supplServicesUsed [1]: Bar Outgoing
startTime [31]: 2002-08-12 16:38:32.030
endTime [32]: 2002-08-12 16:38:32.030
recordReason [13]: Call Barring

Call trace 6-41
Figure 6-51
Explicit Call Transfer CTR Example
Header:
omcID [3]: 45678
startTime [8]: 2002-08-12 16:42:33.089
endTime [9]: 2002-08-12 16:42:33.089
servedIMSI [1]: 505024101216070
location [19]:
ssInformation [20]:
supplServicesUsed [1]: ECT
ssInvokeId [6]: 10
msClassmark [22]: 1F 02 40 10 FF FF
startTime [31]: 2002-08-12 16:42:33.089
endTime [32]: 2002-08-12 16:42:33.089
eventNumber [33]: A18F
recordReason [13]: Call Transfer

6-42 Call trace
Figure 6-52
Multi Party CTR Example
Header:
omcID [3]: 45678
startTime [8]: 2002-08-12 16:47:28.066
endTime [9]: 2002-08-12 16:47:28.066
servedIMSI [1]: 505024101215066
callingcalledNumber [4]: Calling Num: 61411215066#E.164#Internation
Number
location [19]:
ssInformation [20]:
supplServicesUsed [1]: Three Party Call
ssInvokeId [6]: 10
startTime [31]: 2002-08-12 16:47:28.066
endTime [32]: 2002-08-12 16:47:28.066
eventNumber [33]: E18F
recordReason [13]: Multi Party

Call trace 6-43
Figure 6-53
SMS CTR Example
Header:
tracedParty [0]: IMSI: 505021120313001
omcID [3]: 5432
mscBssTraceType [4]: 0xFF
startTime [8]: 2002-07-01 12:30:45.009
endTime [9]: 2002-07-01 12:30:45.009
recordingEntity [10]: 123456789ABCDE123456789ABCDE
invokingEvent [0]: Mobile Originated Call (MOC)
servedIMSI [1]: 505021120313001
servedMSISDN [3]: 61411002133001#X.121#No number present,
through call to carrier
callingcalledNumber [4]: Original Calling Num:
535353535353535353535353535353#X.121#No number present, cut-through call
carrier
location [19]:
msClassmark [22]: 35 30 35 30 35 30
startTime [31]: 2002-07-01 12:30:45.009
endTime [32]: 2002-07-01 12:30:45.009
recordReason [13]: SMS

6-44 Call trace
Figure 6-54Intercepted Call Failure CTR Example

Header:
omcID [3]: 5432
startTime [8]: 2002-07-01 12:30:45.090
endTime [9]: 2002-07-01 12:30:45.090
servedIMSI [1]: 505021120313001
servedMSISDN [3]: 61411002133001#E.164#test line test co
callingNumber [1]: Calling Num:
636363636363636363636363636363#E.164#test line test code
calledNumber [2]: Called Num:
translatedNumber [7]: 536363636363636363636363636363#E.164#t
line test code
redirectingNumber [11]: Redirect From Num:
redirectingNumber [11]: Redirect To Num:
roamingNumber [13]: 020304301761412001020304301761#Unde-
fined#Unknown
networkTKGP [14]: incoming: Not Available outgoing: NETWO
TRUNKGROU-5745
basicService [15]: Data PDS
location [19]:
ssInformation [20]:
supplServicesUsed [1]: All
ssInvokeId [6]: 65283
msClassmark [22]: 35 30 35 30 35 30
callTermDiagnostics [23]: 00 81 91
Cause-text: User busy
mstartTime [31]: 2002-07-01 12:30:45.090
endTime [32]: 2002-07-01 12:30:45.090
recordReason [13]: Intercepted Call Fail

Call trace 6-45
Figure 6-55
Classmark Update CTR Example
Header:
omcID [3]: 5432
startTime [8]: 2002-07-01 12:30:45.011
endTime [9]: 2002-07-01 12:30:45.011
servedIMSI [1]: 505021120313001
servedMSISDN [3]: 61411002133001#E.164#National Number
location [19]:
msClassmark [22]: 35 30 35 30 35 30
startTime [31]: 2002-07-01 12:30:45.011
endTime [32]: 2002-07-01 12:30:45.011
recordReason [13]: Classmark Update
Figure 6-56
Handover CTR Example
Header:
omcID [3]: 5432
startTime [8]: 2002-07-01 12:30:45.044
endTime [9]: 2002-07-01 12:30:45.044
servedIMSI [1]: 505021120313001
servedMSISDN [3]: 61411002133001#E.164#No number present,
through call to carrier
location [19]:
msClassmark [22]: 35 30 35 30 35 30
startTime [31]: 2002-07-01 12:30:45.044
endTime [32]: 2002-07-01 12:30:45.044
recordReason [13]: Handover

6-46 Call trace
Disable query to HLR 6

Select Disable Query to HLR from the Call Trace drop-down menu and then
opens the Activate Trace window. The Activate Trace window displays the
MSCs in the Network Element list. The provisioning request is sent to the
selected MSC(s) without involving the HLR. The IMSI is provisioned as a
Foreign Subscriber on the MSC.
Figure 6-57
Activate Trace window
If the Disable Query to HLR option is not selected, then the HLRs are listed
under Network Element and the provisioning request is sent to the selected
HLR(s). The activation request is sent to the HLR first and if the IMSI is not
present in the HLR database, then the operator is asked for confirmation if the
IMSI needs to be provisioned as a Foreign Subscriber. This is the default
behavior of the CT GUI.
The Disable Query to HLR option can also be saved as a user preference
when the operator exits the CEM GUI. The Save Call Trace Settings option
under the General preferences saves the settings updated by the user.

7-1
Tools 7
The Core Element Manager (CEM) can launch additional tools that allow you
to interface with managed DMS Core elements: Mobile Services switching
Center (MSC) or Home Locator Register (HLR), the Universal Signalling
Point (USP), and CS2000 Succession elements: Audio Provisioning Server
(APS), Gateway Controller (GWC), Universal Audio Server (UAS), Line
Maintenance Manager (LMM), Trunk Maintenance Manager (TMM).
Tools menu 7
Figure 7-1 shows the Tools menu.
Figure 7-1
Tools menu options
The selections on the Tools menu allow you to:

• Messaging - Send messages to all users connected to an SDM, a managed
Core element, or other nodes on the network.
• Maintenance Commands - Issue pre-defined maintenance commands for
each type of managed Core element. You can modify the listed commands
for each Core element. Export and import of maintenance command files
for a particular resource or for all the resources.

7-2 Tools
• Use Encryption - Toggle on and off encryption for MAP, Telnet, and FTP
connections.
• Set AutoLogin -
Toggle on and off the automatic login for MAP, Telnet,
and FTP connections.
• MAP - Launch multiple Maintenance and Administration Position (MAP)
command interfaces (CIs) to monitor and control the Core elements.
• Telnet - Launch Telnet interfaces to managed Core elements, SDMs and
other hosts.
• FTP - Launch FTP interfaces to managed Core elements, SDMs and other
hosts.
• SSH Suite - Lists options of SSH protocols for establishing secure Telnet,
FTP, and MAP sessions between the CEM Client Workstation and a
remote host.
• USP Visual Basic GUI -
Manage USP OA&M functions. (PC Element
Manager only). Supports USPs/SLRs that are based on USP8.0 or earlier.
• USP Java GUI - Manage USP OA&M functions. (PC Element Manager
only). Supports USPs/SLRs that are based on USP8.1 or higher.
Messaging 7
The Messaging window is launched by selecting Messaging from the Tools
menu (Figure 7-1). This window (Figure 7-2) allows users to send messages
to all users connected to a selected node.

Tools 7-3
Figure 7-2
Messages window
Nodes are selected one at a time from the list of connected nodes in the Send
to Users On drop-down menu. Below the Send to Users On drop-down menu
is a blank area for typing the message.
At the top of the Messages window is a menu bar with two options: File and
Help.
The File submenu includes the following items:

• Send - Send the message and close the window.
• Save - Open a Save As box for you to choose a destination and filename.
• Print - Print the message.
• Clear All - Clears all messages in the history portion of the Messages
window.
• Close - Close the window without saving or sending.
Selecting Help links you to the on-line User Guide at the location that details
the Messaging function.

7-4 Tools
To clear one message, select a message and right click on it. A pop-up menu
appears. Click on Clear.
Just below the menu bar is an area to display all or some of the messages that
have been sent. Message filters, in the form of character strings, may be
entered in the blank Filter Messages text box. Only those messages that
contain the filter are displayed.
At the top of this message display box are five category headings. You can
drag the division lines between categories and change the size of each
column. The messages can be sorted by any of the categories, in ascending or
descending order. There is an arrowhead in the heading selected for sorting,
pointed up or down, depending on the order chosen.
Note: The maximum length for a message typed in at the Messages

window is 70 characters.
Maintenance commands 7
The Maintenance Commands window is launched by selecting a network
element in the Configuration Manager, and then either selecting the
Maintenance Commands menu item in the Tools menu (Figure 7-1) or
pressing Ctrl+D.
Selecting Help is links you to the on-line User Guide at the location that
details the Maintenance Commands window to aid you in constructing
complicated maintenance commands based on the attribute available in the
Info window for a node.
The Maintenance commands menu has three submenu items (see Figure 7-3):
• Commands Window - Launches the Maintenance Commands window
• Export Maintenance Commands - Launches a File dialog which takes the
name of a file to which the maintenance commands for all the resources in
the Element Manager should be saved
• Import Maintenance Commands - Launches a File dialog which prompts
you to enter the name of the file from which the maintenance commands
should be imported into the Element Manager.

Tools 7-5
Figure 7-3
Maintenance Commands window
The icon displayed at the left side in the Maintenance Commands window
represents the node currently selected in the configuration area of the CEM
browser. This is dynamically updated when a different node is selected in the
configuration area.
The Maintenance Commands list box allows you to enter or edit maintenance
commands for an element and execute them dynamically. The list box
displays the maintenance commands available for the selected node. This list
is dynamically updated when a different node is selected in the configuration
are of the CEM browser.
When a command is selected from the list, the Menu Command and the Actual
Command for the entry selected are displayed in the text fields to the right of
the list.
By default, the commands rts, busy, post and offline are supplied for all the
nodes in a file, where applicable. On start-up the commands are read from the
file and the command lists for the nodes are populated.

7-6 Tools
After doing a post on certain nodes, the response may be longer than a single
screen. In that case, the MAP prompts you with “more...”. Press ENTER to
display the next screen of information.
Table 7-1
Maintenance commands window fields and buttons
Item Definition
Menu Command box Displays the Menu command, the descriptive name of the maintenance
Command, for a node. This field is displayed when a user selects a
command from the list, and it can be edited and cleared when New button
is clicked.
Actual Command box Displays the Actual command to be executed on the MAP session for a
node selected. This field can be edited and cleared when New button is
clicked.
New button Clears the Menu command and Actual command text areas, and allows
the user to enter a new command for a selected node.
Delete button Allows the user to select a command from the list and remove it.
Apply button Saves the Menu command and Actual command and immediately displays
them. It also updates the pop-up menu for that node.
OK button Closes the Maintenance Commands window, prompting the user to save
any unsaved information (if the apply button was not selected) before
closing the window.
Cancel button Clears changes in the window.
Done button Closes the window.
Import button Imports maintenance commands for a resource from a file into the
Element Manager.
Export button Exports the maintenance commands for a resource from the Element
Manager to a file.
Help button Launches the On-line Help window and the loads the section of the User
Guide which explains in detail the procedure to add commands using the
attributes of the node available in the “Info Window”.
@componentInstance macro
The @componentInstance macro creates the component name that will be
sent to the MGW when a maintenance command is selected and should only
be used with MGW components. This macro is implemented because
components can appear in multiple places in the component hierarchy and

Tools 7-7
hard-coding the location and using the existing @unitNumber,

@parentUnitNumber, and @superParentUnitNumber is impractical.
For example, if the user selects the VC4 component illustrated in Figure 7-4,
the macro will generate the string “LP/15 SDH/0 VC4/0”.
Figure 7-4
VC4 Component
VC4 Component
The final command sent to the MGW node will be “help LP/15 SDH/0 VC4/
0” as show in Figure 7-5.

7-8 Tools
Figure 7-5
Final Help Command
Help
Command
USP/SLR maintenance action

The USP/SLR Maintenance Action re-uses the behavior of existing DMS
maintenance actions. This requires that a telnet session be brought up and
user validation passes.

Tools 7-9
For user convenience, a ‘telnet’ menu item will be available on the pop-up menu
of the USP components. The components that will have the ‘Telnet’ menu item
are:
• USP/SLR
• UNPM
• routeset
• linkset-group
• combined-linkset
• linkset
• link
• slot
To perform maintenance action on the targeted USP,SLR or UNPM device, a

targeted telnet session needs to be up and user ID/password validation passed.
The CEM browser provides pop-up menu options for available maintenance
actions on USP and UNPM resources in the GUI containment tree. Users can
select a specific maintenance action and the command will be posted to an
opened telnet session of the specified USP or UNPM. This is similar to how
the DMS commands are executed in the CEM GUI.
The following are the maintenance actions on USP components that are
supported through the pop-up menu items which often do not require additional
data in order to perform the action:
• shelf component
— post
• slot (card) component
— post (show)
— lock
— unlock
— offline
— load
— swact
• routeset component
— post (show)
— activate
— de-activate

7-10 Tools
• linkset-group component
— post (show)
• combined-linkset component
— post (show)
• linkset component
— post (show)
— activate
— de-activate
• link (SLC) component
— post (show)
— activate
— de-activate
— inhibit
— uninhibit
— test
Note 1: Only maintenance action on the slot and routeset components can
be performed when the USP is on USP7 load because USP7 telnet
interface cannot recognized actions for the other components.
Note 2: Resources related to OM groups do not have maintenance actions

available.
UNPM network elements share with SLR network elements a list of

manageable elements in an CEM management slice. The following are the
maintenance actions on UNPM components that are supported through the pop-
up menu items which often do not require additional data in order to perform
the action:
• shelf component
— post
• slot (card) component
— post
— lock
— unlock
— load
— offline

Tools 7-11
— swact
• routeset component
— post
— activate
— de-activate
• combined-linkset component
— post
• linkset-group component
— post
• linkset component
— post
— activate
— de-activate
• link (SLC) component
— post
— activate
— de-activate
— inhibit
— uninhibit
— test
Construct maintenance commands

The following wildcard characters can be used in constructing maintenance
commands:
• * or @nodename - identifies the selected node name.
• # or @unit number - identifies the selected node unit member.
Note: A unit number is the number displayed in the node name after the
‘_’ (minus sign).
• @unitnumber[n] - identifies the nth field of the unit number, if the

unitnumber is comprised of more than one number separated by ‘-’
(minus sign).

7-12 Tools
Note: This is useful for nodes like “DAT-0-2” under “FP”, where
@unitnumber [1] can be used to identify “fpScsiNum” which is ‘0’ and
@unitnumber[2] can be used to identify “fpDeviceNum” which is “2”.
• @parentnodename - identifies the selected node parent’s node name.

• @parentunitnumber - identifies the selected node parent’s unit number.
• @superparentunitnumber - identifies the selected node super parent’s unit
number.
• @trunkgrouptype - identifies the type of trunk group (C7ttp or ttp) this is
used only for the trunk groups and trunk elements.
• @attribute - identifies the value of the selected nodes particular attribute
listed in the Info window for the node.
Note: attribute should be replaced by the appropriate attribute name for
the selected node. For example, @fpDevicenum, @fpScsiNum.
• @mscdkey[n] - identifies the nth field of a selected node mscdkey.

Note: The mscdkey is displayed in the Info window for a node. Only the
attributes displayed in the Info window can be used to make up
maintenance commands.
Add, delete and edit maintenance commands

Procedure 7-1
Add a Maintenance command
1) From the Configuration Manager window, select the network element to
receive the command.
2) From the Tools menu, select Maintenance Commands. The Maintenance

Commands window appears (see Figure 7-3). Select the New option from the
Maintenance Command window menu.
3) In the Menu Command field, provide a descriptive name of the command.
4) In the Actual Command field, enter the actual command to be entered at the
command prompt. Refer to the “Construct maintenance commands” section.
5) Select Apply.
6) Select Done.
Note: The commands are stored per class. Once you add a command for a
particular element, it applies for all the elements of the same type or class
name.
Procedure 7-2
Delete a Maintenance command

Tools 7-13


Commands window appears (see Figure 7-3). Select the command or
commands that you want to delete from the Maintenance Command window
menu.
3) Select Delete.
4) Select Done.
Procedure 7-3
Edit a Maintenance command

Commands window appears (see Figure 7-3). Select the command that you
want to edit from the Maintenance Command window menu.
3) In the Menu Command field, edit the command.
4) In the Actual Command field, edit the command. Refer to the “Construct
maintenance commands” section.
5) Select Apply.
6) Select Done.
Use Encryption 7
When connecting through MAP, Telnet, or FTP to managed Core elements,
Use Encryption (Figure 7-6) determines whether the information sent is to be
encrypted or not.
Figure 7-6
Use Encryption menu item
The Use Encryption tool includes the following sub-menus:

• MAP/FTP to CM— The information to be exchanged with the SDM
through the MAPCI application will be encrypted, otherwise the
information is exchanged in plain text.
• Telnet/FTP to SDM — The information exchanged with the SDM through
the Telnet application is encrypted, otherwise the information is
exchanged in plain text.

7-14 Tools
• Telnet/FTP to Server — Some information exchanged with the SDM

through the FTP applications is encrypted, otherwise the information is
exchanged in plain text. The Element Manager currently does not support
encryption of information exchanged with hosts other than SDM.
Note: In FTP applications only the FTP commands, including the user ID
and password are encrypted, whereas the information exchanged on the
data port is not encrypted.
Set AutoLogin 7
When connecting through MAP, Telnet, or FTP to managed Core elements, Set
AutoLogin enables the automatic login functionality. Clicking on Set
AutoLogin in the Tools menu (Figure 7-1) toggles the automatic login on and
off. When there is a checkmark preceding the Set AutoLogin option, the
automatic login is enabled.
The following sections apply when Set AutoLogin is enabled: “MAP

automatic login” on page 7-14, “Telnet automatic login” on page 7-19, and
“FTP automatic login” on page 7-29.
MAP 7
For each Core element, you can display a standard MAP interface and
manually enter the commands at each command level. The MAP submenu is
shown in Figure 7-7.
Figure 7-7
MAP submenu
When logging into the MAP command interface (CI), the standard Core
element security is enforced. Therefore, prior to accessing the MAP interface,
your system administrator must assign you a valid user name and password
for that Core element.
MAP automatic login

The MAP Login dialog is displayed when the user selects a DMS node on the
CM Panel and initiates a MAP session. When there are no login credentials
previously saved on the CEM System for the selected DMS node, then the
MAP Login dialog is displayed with blanks fields, except the Host field. If
there are login credentials saved in the CEM System, the MAP Login window
is displayed with pre-filled values.

Tools 7-15
Figure 7-8
MAP Login window
The MAP Login window (Figure 7-8) contains the following:

• Host - This field is not editable. The IP address or the hostname of the
selected node.
• Userid1 - This is the field where the user enters the first login id.
• Password1 - This is the field where the user enters the password that goes
corresponds to the first user ID.
• Userid2 - This is the field where the user enters the second login id.
corresponds to the second user ID.
• Userid3 - This is the field where the user enters the third login id.
corresponds to the third user ID.
• Save Login Credentials - This check box field allows the user to indicate
whether the credentials entered in that dialog box need to be saved. The
credentials will be saved for the current CEM Browser session. To save

7-16 Tools
the credentials permanently in the CEM System, the user has to invoke the
Preferences window (refer to “Transparent user preferences” on page 2-
22) and check mark the “Save Login Credentials” checkbox under the
Tools tab.
• OK - When this button is clicked, following verifications are performed:
— The first user ID and password fields should have a value in it. It
cannot be empty. If this field is empty, an error message will be
displayed.
— If second user ID is entered then second password has to be entered. If
this field is empty, an error message will be displayed.
— If second password is entered then the second user ID has to be
entered. If this field is empty, an error message will be displayed.
— If third user ID is entered then third password has to be entered. If this
field is empty, an error message will be displayed.
— If third password is entered then the third user ID has to be entered. If
this field is empty, an error message will be displayed.
— If third user ID and password should not be allowed if second user ID
and password are left empty. If this field is empty, an error message
will be displayed.
• Cancel - When this button is clicked, the dialog and the MAP session
window closes.
File menu
The File menu is located on the MAP and Telnet windows ().
Table 7-2
File menu options
File Menu Definition

Options
Start Allows you to start the recording of the messages

recording displayed in the window. When this option is selected, a
file dialog is launched. Specify the name of the file to
which messages have to be written. You can also select
the directory where the file has to be placed.
Stop Allows you to stop recording messages to the file

recording previously specified.
Hide Allows you to hide the window.
—sheet 1 of 2—

Tools 7-17
Table 7-2
File menu options
File Menu Definition

Options
Logout Allows you to logout from the session and close the
window.
—sheet 2 of 2—
Preferences menu
The Preferences menu is located on the MAP and Telnet windows (Table 7-3).
Table 7-3
Preferences Menu Options
Preferences Definition
Menu
Options
Terminal Allows you to change the number of rows that can be set
Rows for the terminal. Supported values are 24, 48, 100, 200,
and 400 rows. The default number of rows set for a
terminal is 200.
Smaller Font Allows you to reduce the font size of the text displayed in
the terminal by a decremental value of 1 pixel.
Larger Font Allows you to increase the font size of the text displayed
in the terminal by an incremental value of 1 pixel.
Foreground Allows you to select the color of the content displayed in

the terminal from a list of various colors.
Background Allows you to select the color of the background of the

terminal from a list of various colors.
Note: Terminal Preferences are only valid for the current session of the
CEM browser and are not restored when the CEM browser is restarted.
Automatic posting of the node

When a leaf node is double clicked, a MAP window is opened, and you can
login. If there is a MAP window open and you have already logged in and the
window is selected as Target MAP, then double-clicking on the leaf node will
post the node. This automatic posting takes place only if the leaf node has a
command with the descriptive name post (case insensitive).

7-18 Tools
A node may have several post commands which represent different ways of
posting a node. These post commands have unique descriptive names. Only
the post command is executed when a node is double-clicked: Other post
commands can only be executed by selecting them from the pop-up menu for
the node.
Telnet Interface 7
The Telnet submenu appears as shown in Figure 7-9.
Figure 7-9
Telnet submenu
The Telnet function includes the following:

• At most, five Telnet windows can be launched to remote machines
including the SDM, per user session.
• The maximum number of Telnet to XA-Core connections is restricted by
the TCPCONN field in table IPHOST.
• A Telnet window can be launched by selecting a menu item from the
Telnet submenu.
• If the menu item selected is labelled with the host name of the remote
machine to which Telnet connection is opened, the Telnet window for the
host is brought to the foreground.
• Each labelled menu item in the Telnet submenu consists of the host name
of the remote machine to which Telnet connection is opened, and the user-
id used to open the Telnet connection, and the submenu row number.
• If a menu item is shown as Untitled-N, where ‘N’ represents the submenu
row number, which can be 0, 1, 2, 3, or 4; it can be selected to launch a
new Telnet window.
• The Telnet submenu labels are automatically updated as and when new
Telnet windows are launched, or the existing Telnet windows are closed.
• The Telnet window looks similar to the MAP window, and uses the same
mechanism, except the following differences:
— The Target MAP radio button is not available for the Telnet windows.
— Commands cannot be automatically sent to the Telnet windows.

Tools 7-19
• If a node is selected in the Configuration Manager is associated with an

NE, CEM Server or a mediation device, the Telnet window restricts the
operator to log into the host corresponding to that node. If a host is not
associated with the node, the host field is left blank and the operator has to
supply the host name/IP address. For example:
— If the node selected is a DMS based node, the Telnet window defaults
the host to SDM/FT.
— If the node represents a CEM Server, the host field is defaulted to
hostname/IP address of the CEM Server.
— If the node is a USP/SLR component, the Telnet window defaults the
host to the active host of USP/SLR.
Note: In the case of DMS nodes, even though the associated host is Core,
the Telnet host defaults to the mediation device which is SDM/FT.
Telnet automatic login

The Telnet Host Information dialog is displayed on the Telnet session window
when the user has not selected a node on the CM Panel prior to initiating the
Telnet session. If an IP node has been selected on the CM Panel then this
dialog is not displayed; instead the Telnet Login dialog, with or without saved
login credentials) is displayed.
The Telnet Host Information Login window (Figure 7-10) contains the
following:
• Host - This is a field where the user enters the IP address or the hostname
of the Telnet Server (machine that the user wants to connect to).
• OK - When this button is clicked, the following verification is performed:
— The Host field should have a value in it. It cannot be empty. An error
message will be displayed if the Host field is empty.
• Cancel - When this button is clicked, the dialog and the Telnet session
window closes.
Figure 7-10
Telnet Login Host Information window
The Telnet Login dialog can be displayed when the login credentials for the
selected host are previously saved on the CEM System, or when the user

7-20 Tools
manually enters the login credentials for the selected host and wants to save it
on the CEM System. If the automatic telnet login fails, an Automatic Telnet
Login Failure window is displayed and the user has to enter the login
credentials manually on the selected host. If the automatic telnet login on the
selected host fails, the error message “You entered an invalid login name or
password” is displayed and the user will be asked to login manually.
Figure 7-11
Telnet Login window
The Telnet Login window (Figure 7-11) contains the following:

• Host - This field is not editable. The IP address or the hostname of the
selected node if the node on the CM Panel was selected prior to initiating
the Telnet session, or the host information entered in the Telnet Host
Information dialog is displayed in this field.
• User ID - This is the field where the user enters the telnet login id.
• Password - This is the field where the user enters the password.
• Save Login Credentials - This checkbox field allows the user to indicate
whether the credentials entered in that dialog box need to be saved in
memory for the remainder of the CEM browser session. To save the
credentials permanently in the CEM system, the user has to invoke the
Tools tab.
• OK - When this button is clicked, the following verifications are
performed:
— The user ID field should have a value in it. It cannot be empty. If the
user ID field is empty, an error message will be displayed.

Tools 7-21
— The password field should have a value in it. It cannot be empty. If the
password field is empty, an error message will be displayed.
• Cancel - When this button is clicked, the dialog and the Telnet session
window closes.
Configuration of Telnet session timeout value

PC users can set the Telnet session timeout value for any new sessions
initiated by that user. The user can set the timeout value by selecting the
Telnet submenu under the Tools menu. The user then selects the “Configure
Telnet Session Timeout Value” submenu item. The Configure Telnet Timeout
Value window (Figure 7-12) is displayed. The default timeout value is 10
minutes. The OMC-S System verifies the user’s input and stores it into the
user preferences file which is based on the user ID used on the PC Login.
Figure 7-12
Configure Telnet Timeout Value Window
An error message will be displayed for the following possible errors:

• timeout value is empty
• invalid timeout value
• timeout value input string is too long
Maintenance command example

This section provides an example of how an operator would send a
maintenance command to a MGW node. This example uses the “Time”
command. Sending any other maintenance command follows the same pattern
with different responses.
First, select an available MGW node as show in Figure 7-13.

7-22 Tools
Figure 7-13
Select MGW node
Select MG
Node
Next, establish a telnet session by selecting an available telnet session from

the Tools->Telnet->Telnet Sessions menu as show in Figure 7-14.

Tools 7-23
Figure 7-14
Establish telnet session
Select Available
Telnet Session
The operator will then supply a valid MGW user name and password as

7-24 Tools
Figure 7-15
MGW login
After the telnet session is established, the operator can then invoke the MG
pop-up menu and display the available maintenance commands.

Tools 7-25
Figure 7-16
Invoke pop-Up menu
Right Mouse Click

MG Node
Select Command
From List
Finally, the telnet window will be brought to the front and the command
results displayed for the operator as shown in Figure 7-16.

7-26 Tools
Figure 7-17
Command response
Error messages
An error message will be displayed to the user if there is no telnet terminal
open to the selected MGW node or if the terminal is not selected as
“Targeted”.
Using the Telnet command

The Telnet command allows users to open a telnet window with out using the
“Tools” menu.

Tools 7-27
First, select an available MGW node as show in Figure 7-13.
The operator then invokes the MGW pop-up menu and selects the “Telnet”
command as shown in Figure 7-18.
Figure 7-18
Select telnet command
Select Telnet
Command
The operator will then supply a valid MGW user name and password as

7-28 Tools
After the telnet session is established, maintenance commands can be selected

and the results displayed in the window opened by the Telnet command.
FTP interface 7
The File Transfer Protocol (FTP) submenu appears as shown in Figure 7-19.
Figure 7-19
FTP submenu
The FTP function includes the following:

• At most, three FTP windows can be launched per user session to remote
machines including the CM and SDM.
• An FTP window (shown in Figure 7-23) is launched by selecting a menu
item from the FTP submenu. If the menu item selected reads “Untitled-N”
then a new FTP window is created, otherwise the FTP window for the
host represented by the menu item is brought to the foreground.
• Each labelled menu item in the FTP submenu consists of the host name of
the remote machine to which FTP connection is opened, the user-id used
to open the FTP connection and the submenu row number.
• If a menu item is shown as “Untitled-N”, where ‘N’ represents the row
number, which can be 0, 1, or 2, it can be selected to launch a new FTP
window.
• The FTP submenu labels are automatically updated when new FTP
windows are launched, or the existing FTP windows are closed.If a node
selected in the Configuration Manager is associated with an NE, CEM
Server or a mediation device, the FTP window restricts the operator to log
into the host corresponding to that node. If a host is not associated with
the node, the host field is left blank and the operator has to supply the
hostname/IP address. For example:
— If the node selected is a DMS based node, the FTP window defaults
the host to Core.
— If the node selected represents a CEM Server, the host field defaults to
the hostname/IP address of the CEM Server.
— If the node selected is a USP/SLR component, the FTP window
defaults the host to the active host of the USP/SLR.

Tools 7-29
FTP automatic login

The FTP Login Host Information dialog (see Figure 7-20) is displayed on the
FTP session window when the user has clicked on the Connect button on the
bottom of the FTP session window and a node on the CM Panel was not
selected prior to initiating the FTP session. If an IP node had been selected on
the CM Panel and the Connect button is clicked, this dialog is not displayed;
instead the FTP Login dialog (see Figure 7-21) is displayed.
Figure 7-20
FTP Login Host Information window
The FTP Login Host Information window (Figure 7-20) contains the following:
• Host - This is the field where the user enters the IP address or the
hostname of the FTP Server (machine that the user wants to connect to).
— The Host field should have a value in it. It cannot be empty. If this
• Cancel -
When this button is clicked, the dialog and the Telnet session
window closes.
The FTP Login dialog is displayed when the login credentials for the selected
host are previously saved on the CEM System or when the user manually
enters the login credentials for the selected host and wants to save it on the
CEM System. If the automatic FTP login fails, the user will need to click on
the Connect button, manually enter the user ID and Password, and click on
the OK button.

7-30 Tools
Figure 7-21
FTP Login window
The FTP Login window (Figure 7-21) contains the following:

• Host - This field is not editable and contains either the IP address or the
hostname of a selected node, or the host information entered in the FTP
Host Information dialog box.
• User ID - This is the field where the user enters the FTP login id.
• Password - This is the field where the user enters the password.
• Save Login Credentials - This check box field allows the user to indicate
whether the credentials entered in that dialog box need to be saved. The
credentials will be saved for the current CEM Browser session. To save
the credentials permanently in the CEM System, the user has to invoke the
Tools tab.
— The user ID field should have a value in it. It cannot be empty. If this
— The password field should have a value in it. It cannot be empty. If this
• Cancel - When this button is clicked, the dialog of the FTP Login window
closes.
Configuration of FTP session timeout value

PC users can set the FTP session timeout value for any new sessions initiated
by that user. The user can set the timeout value by selecting the FTP submenu
under the Tools menu. The user then selects the Configure FTP Session

Tools 7-31
Timeout Value submenu item. The Configure FTP Timeout Value window
(Figure 7-12) is displayed. The default timeout value is 10 minutes. The
OMC-S System verifies the user’s input and stores it into the user preferences
file which is based on the user ID used on the PC Login.
Figure 7-22
Configure Telnet Timeout Value Window
An error message will be displayed for the following possible errors:

• timeout value is empty
• invalid timeout value
• timeout value input string is too long
FTP window
The FTP window consists of various panes, which provide user the ability to
perform various operations supported by the FTP protocol.
The FTP window is shown in Figure 7-23.

7-32 Tools
Figure 7-23
File transfer interface window
The various regions of the FTP window are illustrated in detail in the
following sections.
Local system and remote system

The Local System pane is shown to the left side of the FTP window. The Remote
System pane is shown to the right side of the FTP window. Each side includes
the local current directory, a list of files in that directory, and a column of
buttons.
• The current directory displays the full path to the current directory on the
local or remote machine. This field gets updated as the user changes
directory.

Tools 7-33
• The local file window which displays the files and directories in the
current directory of the local or remote machine. The pane is provided
with a scroll bar.
• The file or directory displayed in the local file window is highlighted
when it is selected. A double click on a directory drills down and displays
the contents of the directory and updates the current directory.
The buttons are associated with the operations that can be performed on a local
or remote machine:
• List Vols Button - (Remote System only) Launches a window with
complete list of SLM and DDU volumes on the DMS node. This is only
applicable to File Transfers to and from DMS nodes.
• ChgDir Button - Allows you to change the current directory.
• MkDir Button - Allows you to create a directory in the present working
directory.
• Rename Button - Allows you to rename a file or a directory.
• Delete Button - Allows you to select files or directories and delete them.
• Refresh Button - Allows you to get a fresh copy of the contents displayed.
The actions corresponding to these buttons are performed only if the user has
the right permissions to execute the actions.
Transfer file options

There are two buttons with arrows between the Local System and Remote
System panes which allow you to transfer files between the local and remote
machine.
• Put Button “==>” - Transfers the file selected in the local file browser to
the remote machine.
• Get Button “<==” - Transfers the file selected in the remote file browser to
the local machine.
Below the Local System and Remote System panes are two radio buttons
(mutually exclusive) which allow you to select the mode in which the files will
be transferred:
• ASCII - Sets the mode to ASCII.
• Binary - Sets the mode to Binary.
FTP console
This text area at the bottom of the FTP window, displays the messages sent by
the remote machine after every operation is performed. From these messages,
you can determine the status of the FTP connection to the remote machine.

7-34 Tools
You can also type FTP commands manually and execute them. The FTP
commands that are supported can be displayed by entering “?” or “help” in
the FTP console.
Below the FTP Console are the following buttons:

• Connect - Launches the Login Interface to connect to a remote machine.
• Disconnect - Closes the FTP connection between the local and remote
machines.
• Hide - Hides the FTP window.
• Close - Closes the FTP connection and destroys the FTP window.
FTP access configuration

To use the FTP window, FTP access information has to be configured on the
CM. The following are the minimum conditions needed for the FTP window.
• The configuration management (CM) tuple in the IPHOST table has to be
datafilled before opening FTP connection to CM.
• The number of FTP client connections, FTP server connections, and TCP
connections have to be increased appropriately.
• The number of FTP to XA-Core connections is limited to 10. This is
further restricted by the FTPSVCON field in table IPHOST.
• The number of FTP from XA-Core connections is restricted by the
FTPCLCON field in table IPHOST.
• The number of TCP connections in the IPHOST table has to be at least the
number of FTP client connections plus the number of FTP Server
connections. That is, if the number of FTP client connections is increased
by 10 and the number of FTP server connections is increased by 10 then
the number of ICP connections has to be increased by 20. For example, if
the CM tuple in the IPHOST table reads as: TCP Connections ->25 FTP
Client Connections->0 FTP Server Connections-> 0, it should be changed
to TCP Connections ->45 FTP Client Connections->10 FTP Server
Connections->10 to allow 10 FTP CM users, from one or more OMC-S
Browsers.
SSH suite 7
The SSH Suite (Figure 7-24), as part of the CEM browser, provides series of
Graphic User Interface (GUI) windows that allow the user to access different
SSH services from the CEM browser. The SSH Suite, which is available in Sun
Solaris and MS-Windows (i.e. Windows NT/2000/XP) platforms, provides the
following services:
• SSH (Telnet): Secured Telnet and Secured MAP Login through
“passthru”
• SFTP: Secured FTP

Tools 7-35
• SCP: Secured Copy (Replacement of RCP)

• Key Generation: Generate the user’s key for authentication
The user can invoke different SSH services (i.e. SSH Telnet, SFTP, etc.) from
the CEM browser by going to the main menu of the CEM browser and
selecting ‘Tools’, then ‘SSH Suite’, then selecting one of the items on the
submenu. The CEM Browser only supports user (i.e. manual) initiated SSH
sessions.
Figure 7-24
SSH suite submenu
In the MS Windows environment, the CEM Browser is enhanced to invoke

the PuTTY suite of client applications; whereas, in the Solaris environment,
the CEM Browser invokes the OpenSSH client application suite.
Establishing an SSH secured MAP session directly with the DMS is not
currently supported. However, an SSH user initiated MAP session can be
established through the use of the SDM “Passthru” functionality. To utilize
this “Passthru” functionality, a “passthru” account must be established on the
SDM. With the use of SSH, the user logs in as CMuser (no password
required), the SDM automatically connects this SSH session to CM. The user
must then be authenticated by the CM by entering a valid user ID and
password. After successful authentication, a MAP session is established. For
this MAP session, the communications between the CEM Browser and the
SDM/FT is secured by SSH and communications between the SDM/FT and
the CM is internal and remains safely hidden from the outside world.
To securely retrieve a file from the DMS, the user must first FTP the file from
the DMS to the SDM/FT. This step should be done from an SSH secured
MAP session. The user can then use SFTP or SCP to retrieve the file from the
SDM/FT. To securely send a file to the DMS, the user will first transfer the
file to the SDM/FT using SFTP or SCP. The file can then be moved to the
DMS by logging into the CM (from and SSH secured MAP session) and
using FTP to transfer the file from the SDM/FT to the DMS.
SSH (Telnet)
SSH Telnet provides a secured way to logon to the remote node. The user can
use either a passkey or a password as the login authentication mechanism.
Once the login is successful, then all commands issued from the client’s
terminal will be encrypted before sending to the server and will be decrypted

7-36 Tools
at the server site. SSH Telnet is meant to replace legacy non-secure ‘telnet’
and ‘rlogin’ applications.
SSH (Telnet) window (MS Windows Platform)

The SSH (Telnet) window (Figure 7-25) allows the user to input all
information that is required to start an ssh session from PuTTY.
Figure 7-25
SSH (Telnet) window
The SSH (Telnet) window contains the following:

• Mandatory fields:
— Remote Server Host Name: The host name or IP address of the remote
server.
— User Name: User name to log on the remote system.
• Conditional Fields:
Note: If the user chooses not to enter any data in the ‘Path to the Key
File’ text field, then the application will automatically use a password as
login authentication.
— Path to the Key File: Full path to the key file stored on PC.
— Key and Protocol type: Protocol to be used based on the selected key.
– rsa1
– rsa2
– dsa

Tools 7-37
If all input information from the SSH (Telnet) was validated successfully, the
SSH session will be started in a command prompt window. Figure 7-26 shows
an SSH session connected to a server. From this command prompt window,
the user can issue the telnet command just like a normal telnet session.
Figure 7-26
SSH (Telnet) session
When user clicks on the ‘Browse’ button located below the ‘Path to File’ text
field, the system navigator window will pop up. Using this window, the user
can browse their local hard drive to select the key file. The navigator window
for the key will be preset to filter with file extension “.PPK”
The Warning windows that may be displayed are as follows:

• No Host Name Input - This window displays when user clicks the OK
button in the SSH (Telnet) window without entering the host name.

7-38 Tools
• No User Name Input - This window displays when user clicks the OK
button in the SSH (Telnet) window without entering the host name.
• No Key’s Protocol Selected - This window displays when user clicks the
OK button in the SSH (Telnet) window without selecting the Key and
Protocol type.
SSH (Telnet) window (Sun Solaris Platform)
The SSH (Telnet) window (Figure 7-27) allows user to input all information
that is required to start an SSH session from OpenSSH. This window contains
the following:
• Remote Server Host Name: The host name or IP address of the remote
server.
• User Name: User name to log on the remote system.
Note: By default, OpenSSH will automatically try the authentication in
the following order: 1) rsa2 2) dsa 3)UNIX password. Hence, there is no
need for user to select protocol if the CEM browser is running in Sun
Solaris platform.

Tools 7-39
Figure 7-27
SSH (Telnet) window
If all input information from SSH (Telnet) window was validated

successfully, the SSH session will be started in an xterm. From this xterm
window, the user can issue the telnet commands just like a normal telnet
session.

• No Host Name Input
This window displays when user clicks the OK button in the SSH (Telnet)
window without entering the host name.
• No User Name Input


7-40 Tools
Secure MAP login

Secure MAP login allows the user to SSH telnet to the SDM using the SDM as
a pass through platform to telnet directly to the CM or XA-Core. The secure
MAP login requires the following configuration in the SDM.
• Create the pass through user.
• Install the SSH key file in the SDM. This involves generating the SSH key
file and copy the key file into /home/<pass through user home>/ssh/
authorized_keys (or authorized_keys2).
The switch login ID and password will be required to log on to the CM/XA-
Core.
SFTP
SFTP provides a secured way to transfer files from/to the remote host. The
user can use either passkey or user password as login authentication
mechanism.Once the login is successful, all FTP commands issued from the
client’s terminal will be encrypted before being sent to the server and will be
decrypted at the server site. The SFTP application is meant to replace the
legacy ‘ftp’ application, which is unsecured. The CEM browser provides
SFTP access on MS-Windows platforms as well as Sun Solaris platforms.
SFTP window (MS Windows Platform)

The SFTP window allows a user to input all information that is required to
start a secured FTP session from PuTTY.
Figure 7-28
SFTP window

Tools 7-41
The SFTP window contains the following:

• Mandatory Fields:
server.
• Optional Fields:
Note 1: If the user chooses not to enter any data in the ‘Path to the Key
File’ text field, the application will automatically use password as login
authentication.
— Key and Protocol type: Protocol used based on the key selected.
– rsa
– dsa
Note 2: The protocol selected from this list and the protocol used when
the key is generated must be the same.
Note 3: PUTTY only supports dsa and rsa2 for PSFTP.
When the user clicks on the ‘Browse’ button which is located below the ‘Path
to File’ text field, the system navigator window will pop up. Using this
window, the user can browse their local hard drive to select the key file. The
navigator window for the key will be preset to filter with file extension
“.PPK”.
If all the input information from the SFTP window was validated
successfully, the secured FTP session will be started in a command prompt
window. From this command prompt window, the user can issue FTP
commands just like a normal FTP session.



7-42 Tools
SFTP window (Sun Solaris Platform)

The SFTP window allows user to input all information that is required to start
a secured FTP session from OpenSSH.
If all the input information from the SFTP window was validated
successfully, the secured FTP session will be started in a xterm. From this
xterm, the user can issue FTP commands just like a normal FTP session.
Figure 7-29
SFTP window (Sun Solaris Platform)


SCP
SCP provides a secured way to copy files from/to the remote host. The user
can use either a passkey or a password as the login authentication mechanism.
Once the login is successful, all SCP commands issued from the client’s site
will be encrypted before being sent to the server and will be decrypted at the
server site. The SCP application is meant to replace the legacy ‘rcp’
application, which is unsecured.
SCP window (MS Window Platform)

The SCP window (Figure 7-30) allows the user to input all information that is
required to start a secured copy session from PuTTY.

Tools 7-43
Figure 7-30
SCP window
The SCP window contains the following:

server.
— Path to local file: If this is a ‘Copy to Server’ operation, then this is the
full path to the local file that will be copied to the server site.
Otherwise, this is the path to the local directory where the file from
the server will be copied.
• Conditional Fields:
— Path to remote file: If this is a ‘Copy to server’ operation, then this is
the full path to a directory at server site where the local file will be
copied. Otherwise, this is a full path at the server site from where this
file will be retrieved.

7-44 Tools
Note: If user chooses not to enter any data in the ‘Path to the Key File’
text field, the application will automatically use a password as login
authentication.
— Key and Protocol type: Protocol to be used based on the key selected.
– rsa1
– rsa2
– dsa

This window displays when the user clicks the ‘Copy from Server’ or
‘Copy to Server’ button in the SCP window without entering the host
name.

‘Copy to Server’ button in the SCP window without entering the user
name.
• No Path to Local File Input

‘Copy to Server’ button in the SCP window without entering the path to
the local file/directory.
• No path to remote file input

This window displays when the user clicks the ‘Copy from Server’ button
in the SCP window without entering the path to the remote file/directory.
SCP window (Sun Solaris Platform)

The SCP window allows the user to input all information that is required to
start a secured copy session from OpenSSH.

Tools 7-45
Figure 7-31
SCP window with System Navigator
This window contains the following:

server.
— Path to local file: If this is a ‘Copy to Server’ operation, then this is the
full path to the local file that will be copied to the server site.
Otherwise, this is the path to the local directory where the file from
the server will be copied.
• Conditional Field:
— Path to remote file: If this is a ‘Copy to server’ operation, then this is
the full path to a directory at server site where the local file will be
copied. Otherwise, this is a full path at the server site from where this
file will be copied to the local directory.

7-46 Tools

‘Copy to Server’ button in the SCP window without entering the host
name.

‘Copy to Server’ button in the SCP window without entering the user
name.
• No Path to Local File Input

‘Copy to Server’ button in the SCP window without entering the path to
the local file/directory.
• No path to remote file input

This window displays when the user clicks the ‘Copy from Server’ button
in the SCP window without entering the path to the remote file/directory.
Key generation
The key generator for SSH on MS-Windows will be done through the PuTTY
Key Generator, a third party software key generation utility. Figure 7-32
shows the PuTTY Key Generator window invoked from the CEM browser.

Tools 7-47
Figure 7-32
PuTTY Key Generator
Generate a new key

1. From the CEM main menu select Tools -> SSH Suite -> Key Generation
to invoke the PuTTY Key Generator window (Figure 7-32).
2. From the ‘Parameters’ frame, select the ‘Type of Key to Generate’ (i.e.,
SSH1 (RSA), SSH2 (RSA), or SSH2 (DSA)).
3. From the ‘Actions’ frame, click the ‘Generate’ button and follow the
instruction from the window. This will generate a new key in the window
(Figure 7-33).

7-48 Tools
Figure 7-33
New key
4. Enter/Confirm key passphrase. (optional)

5. From the ‘Actions’ frame click ‘Save public key’ to save the public key in
a directory.
6. From the ‘Actions’ frame, click ‘Save private key’ to save the private key
in a directory. A warning window will be displayed if no ‘Key passphrase’
is given.
The public and private keys should be saved in the same directory.
In order to prevent the system from unwanted hacking, the user should always
supply a passphrase for every generated key.
A limitation on PuTTY reading the path in Windows is that the path to the
public key and private key directory should not contain the ‘ ‘ (white space
character). If there one or more ‘ ‘ characters in the path where the keys are
saved, the user will see an error message stating that there is an ‘Invalid port
number.’
Load the existing key

1. Start the CEM browser in windows platform.

Tools 7-49
2. From the menu, select ‘Tools’ -> ‘SSH Suite’ -> ‘Key Generation’. As the
result, the ‘PuTTY Key Generator’ for windows will be started (Figure 7-
32).
3. From the ‘Actions’ frame, click the ‘Load’ button to start the navigator
window. Navigate to the directory where the private key has been saved
and open the designated private key.
4. If there is a passphrase associated with this key, user will be prompted to
enter the passphrase (Figure 7-34).
Figure 7-34
Enter passphrase window
5. As the result, the key will be loaded into the key ‘PuTTy Key Generator’
window (Figure 7-35).

7-50 Tools
Figure 7-35
Existing key window
Install the SSH key into UNIX server

Prerequisites:
— Openssh has already been installed in the destination server (i.e.,
SDM or CEM Server).
— User who uses this key is a valid UNIX user in the destination server.
1. Follow steps in section “Generate a new key” on page 7-47 or in section

“Load the existing key” on page 7-48 to load the content of the key into
the text display area in the PuTTY Key Generator window (Figure 7-32).
2. From the text display area in the PuTTY Key Generator window,
highlight all the text. Right click to bring up the menu and select ‘Copy’
in the menu. This will copy the key’s text onto the window’s clipboard
(Figure 7-36).

Tools 7-51
Figure 7-36
Copying the key information
3. Logon to the UNIX server.

4. ‘cd’ to $HOME/.ssh directory.
5. For the SSH1 (RSA) key, ‘vi’ the file ‘authorized_keys’ and paste the
key’s text into the content of this file.
6. For the SSH2 (RSA) or SSH2 (DSA) key, ‘vi’ the file ‘authorized_keys2’
and paste the key’s text into the content of this file.
Note 1: The key’s text needs to be continuously in one line.
Note 2: The keys will be stored in the keys file (i.e., authorized_keys or
authorized_keys2) one line per key.
Note 3: If there is an existing key file, the best way to handle the new key
is to append the key at the end of the key file.
Sun Solaris platform

The passkey generation on Sun Solaris will be done through OpenSSH’s
‘ssh-keygen’. To invoke the Key Generator window, the user will select from
the CEM main menu Tools -> SSH Suite -> Key Generation.

7-52 Tools
Figure 7-37
SSH key generator window
The user needs to supply the Pass Phrase and select the key type at the Key
Generator window and click the ‘OK’ button (Figure 7-37).
As the result, an xterm window will pop up and prompt the user for the path
to save the key file. By default, the key file will be saved at $HOME/.ssh
(Figure 7-38).
Figure 7-38
xterm window
Note 1: The Pass Phrase must be at least five characters in length.

Tools 7-53
Note 2: If the Pass Phrase field is emptied, the key will still be generated.
This key can be installed in any SSH server. Once the key is installed, the
user can login on to the server without authentication.
WARNING:
It is a security risk to generate the key without a Pass
Phrase.
Note 3: Always use the default directory to save the generated key. In the
Sun Solaris platform, the OMC-S SSH Suite was designed to look for the
key in the default directory. If there is an existing key of the same type, the
old key will be overwritten.
The ‘No Key Type Selected’ Warning window may be displayed.
Install the Pass Key

1. Start a ‘xterm’ on the console and ‘cd’ to the ‘$HOME/.ssh’ directory.
2. ‘ftp’ the id_[key type].pub to the destination server (i.e., SDM or CEM
server) and put it in ‘/tmp’ directory.
3. ‘telnet’ to the destination server and ‘cd’ to $HOME/.ssh directory.
4. At the UNIX prompt, type ‘cat /tmp/id_[key type].pub >>
authorized_keys2’ and press <Enter>.
5. Now, the key is ready to be used.
SSH Directory/File Permission in UNIX

For the SSH in the server to work properly, do:
• Ensure permission of the $HOME/.ssh directory is set to 700. The UNIX
command for this is ‘chmod 700 $HOME/.ssh’.
• Ensure permission of the key files (i.e., authorized_keys and
authorized_keys2) is set to 600. The command for this is ‘chmod 600
$HOME/.ssh/authorized_keys(2)’.
USP Visual Basic GUI 7

The Element Manager provides operational, administration, maintenance, and
performance (OAM&P) management of the Universal Signalling Point (USP)
as follows:
• configuration management and maintenance through the USP Visual
Basic GUI or USP Java GUI.
• fault management by managing USP alarms in the OMC-S alarm list.
• performance management through storage and retrieval of USP
performance data.

7-54 Tools
USP Visual Basic GUI only supports USPs/SLRs that are based on USP8.0 or
earlier. USPs/SLRs that are based on USP8.1 or higher require launching of
the USP Java GUI.
The USP Visual Basic GUI is launched by selecting USP Visual Basic GUI in
the Tools Menu (Figure 7-39).
Figure 7-39
USP Visual Basic GUI
Note: The USP Visual Basic GUI software must be installed on the
workstation before launching it from the Element Manager. Refer to NTP
411-8111-937 for details.
When Launch is selected, the Launch GUI window is displayed as shown in

Figure 7-40.
Figure 7-40
Launch GUI window
Note: The USP Visual Basic GUI and the SESM Manager items are visible
only on the Windows-based PC workstation.
The command to launch the USP Visual Basic GUI is saved and displayed in
the Enter Command window. You can change the command before clicking
the OK button.
This window is not displayed after the first time, if the Don’t ask again box is
checked. The Launch GUI window is displayed again when the command to
launch is not executed, even if the Don’t ask again box has been checked.
Clicking the OK button launches the USP Login window, as shown in Figure
7-41.

Tools 7-55
Figure 7-41
USP login window
This USP Login window prompts you for your User ID and Password. It then
allows you to select a site from the Site drop-down box. Finally, it allows you
to click the Connect button and connect to the selected site.
USP Java GUI 7

The USP Java GUI supports USPs/SLRs that are based on USP8.1. The USP
Java GUI is launched by selecting USP Java GUI in the Tools Menu (Figure 7-
42) or from the pop-up menu of a USP8.1 or USP10.0 component in the CEM
GUI. The USP10.0 GUI must be installed on the same PC-based or Sun
workstation as the CEM GUI in order to provide support for USP8.1 or
USP10.0 releases.
Note: USPs/SLRs that are based on USP8.0 or earlier require launching

of the USP Visual Basic GUI from the Tools menu of the CEM GUI
(Figure 7-39).
Figure 7-42
USP Java GUI
When a component on a USP8.1 or higher is chosen, an in-context launch can

be performed with the USP Java GUI. Clicking the right mouse button on a
USP based component will display a pop-up menu including the menu item,
Launch USP Java GUI, will be shown.

7-56 Tools
Note: The menu item will not be shown if the USP based device is not of
load 8.1 or higher.
If the table ID is available, the launched GUI will bring up the associated
table after user validation passes. The user only needs to select Retrieve
button on the GUI to retrieve the table contents. If the table ID is not
available, then in-context launch displays the user validation window with the
device already selected.
If a USP GUI is running and launched by CEM GUI, every attempt will be
made to re-use the existing GUI when the device of interest is the same as the
one the GUI is connected to.
Restrictions and limitations 7

• Mass Export in switch format is not supported for USP OM groups, but
Mass Export in tab format is supported for USP OM groups.
• Report definitions are not customizable for SLR groups.
• Configuration management for the USP and SLR is not supported in the
CEM GUI. USP GUI is the tool to utilize for provisioning.
• The Visual Basic USP GUI is not supported on WindowsNT and
WindowsXP.
• The maximum number of USPs that can be managed by CEM in the
network is the same as the HLRs.
• Only one USP can appear beneath an HLR node.
• USP only allows a maximum of 6 connections per RTC into their Log
Exporter interface.
• Management of USP occurs on the OMC-S server. SDM stand-alones
cannot manage a USP.
• A user ID and password needs to be setup on the USP and entered during
configuration of the OMC-S in order for component discovery to be
successful and alarm reception to occur.
• The OMC-S OAM solution for USP is different from LPP/LIU7 on the
HLR. Functionalities that used to exist on the LPP/LIU7 may be lost or
not reported at a detailed level.
• Discovery is only available on the card and routeset resources for USP7.0,
and only card and most MTP resources for USP8.0 or above.
• Alarms from USP are reported against the system or card level nodes.
• Routeset and linkset alarms are reported against the system or card level
components.

Tools 7-57
• Any alarm that cannot correlate to a discovered object will be put in the
MISCELLANEOUS container of the USP object tree.
• No initial resource state is available through the USP interface.
• All Swerr and Info logs clear when re-synchronization of the alarm is
performed.
• If no card or routeset is retrieved from the USP interface, the associated
containers will not be created in the object model.
• Synchronization of alarms on the OMC-S can be completed only when
the heartbeat or info/swerr log is received by the CEM.
• USP Performance Management provides a different set of counters than
those available on the DMS.
• By using the configuration tool to update the managed SLRs will result in
the removal of the previously managed SLRs and start fresh to manage
the SLRs specified in the new update.
• USP GUI needs to be installed on the PC in order to support connection to
USP based devices; Java GUI for USP8.1, Visual Basic GUI for USP8.0
or earlier load.
• Java GUI will have to be provisioned with the USP/SLR/UNPM IP
addresses prior to requesting in-context launch; else the Java GUI could
not perform in-context launch.
• Visual Basic USP GUI does not have the ability to perform in-context
launch.

7-58 Tools

8-1
Administration management 8
Administration Manager 8
The Administration Manager is accessed through the main menu bar (see
Figure 8-1). The administration manager can also be invoked through the
pop-up menu on the SDM node in CM area. It consists of a number of
graphical components and screens which allows you to monitor the status of
the SDMs in the system.
Figure 8-1
Administration menu
The user interface consists of the main monitor window, which displays the
status of the currently selected SDM and allows you to switch the view to
another SDM. The background color changes to indicate state.
Status monitoring
The Administration Manager main window (see Figure 8-2) consists of a list
of monitored SDMs on the left side of the window, and a status display area
beside that.

8-2 Administration management
Figure 8-2
Administration manager main window
When the Administration Manager is first started, it connects with all SDM
machines that the user has requested (using the “Add SDM” menu option),
and creates an entry in the SDM List for each.
If the SDM is selected in the APPL level in the CM panel, and the user selects
“Administration Manager” from the pop-up menu on the SDM, then the
Administration Manager will automatically select the chosen SDM in the list.
Otherwise, the first SDM that responds to the Administration Manager’s
request for the information is shown.
If the status of any monitored SDM changes because of a problem condition,

the list entry associated with that SDM will change color. The color scheme
applies to both the Administration Manager window and the Server Application
Management window. The relevant color schemes are:
• In Service - Light gray
• ManB - Orange
• SysB, Fail - Red

• Logical volume over threshold - Red

• Unknown - Cyan
• ISTB and CBSY - Yellow
• OFFL - Light yellow
Note: When the connection to the SDM is lost, for example when offline
or manbusy, then the status color is cyan which indicates an unknown
status.
The label associated with the problem area in the status display will also turn
the same color. For example, if one of the logical volumes exceeds its
threshold, the entry associated with that SDM will turn red.
Note: Failure to address the volume threshold alarms immediately could

result in loss of data.
The following sections describe the individual items in this window.
SDM/FT selection list

The list along the left side of the Administration Manager window (the SDM
List) is used to select which SDM to view. By default, the first item is selected
at startup. Only the data associated with the currently selected item (SDM) is
displayed. To view data from another SDM, you must select on the list item
associated with that machine.
If there is a problem with one of the SDM machines being monitored by this
window, the list item associated with the SDM will change color.
Data lists
There are three data lists in the display area for each SDM. Each list has a
label at its top left corner, which identifies the data being displayed in the list.
Logical volume list

The first list in the window displays the current levels of usage for configured
logical volumes. The configuration for the program will specify which logical
volumes to monitor and give a threshold for each one. The “Logical Volume”
list shows the mount point for the volume, the current level of use for the
volume, and the threshold that was configured by the administrator.
When the amount of space being used in a logical volume meets or exceeds
the threshold level, the numbers under the level and threshold columns turn
red. When all monitored logical volumes are below their thresholds, the
numbers will turn black (normal).

When the SDM is split-mode, sysdump0 and sysdump1, system dump

devices, are used. When they are not used, a default level value of “-1” is
shown.
Applications list
The second list in the window displays the current state of the system’s
applications. Each application consists of one or more processes.
Communication link list

This list shows the status of communications between the selected SDM and
various other machines on the network.
Force Out 8
The Force Out window is launched by selecting Force Out from the
Administration drop-down menu (Figure 8-1).
The Force Out window (Figure 8-3) contains File and Help drop-down
menus. Selecting File allows a user to print or close the window. Selecting
Help opens an online User’s Guide.
Figure 8-3
Force Out window
The Force Out window contains two tabs: Users and Elements. The Users tab
provides a list of users, host connected from, and the date and time of the
connection. The Elements tab contains the Element ID, the host connected
from, and the date and time of the connection. Users can be forced out from
either tab.

To force out a user from the Users tab view, select a node from the
Configuration Management panel. This displays a lists of users for that node.
Highlight the user to be forced out and then right-click. This removes the
selected user from the node.
To force out a user from the Elements tab view, select a user to get a list of
elements, highlight the desired element and then right-click.
Note: If a user who launched CEM from the W-NMS GUI is forced out
of the managed feed and they want to get the managed feed again, the user
must exit CEM by using File -> Close and then re-open the CEM window
from the W-NMS GUI.
Limitations
• Remote users cannot be forced out.
• Force out does not allow certain features when:
— GEM17 GUI is connected to a GEM15 Stand Alone SDM
— GEM16 GUI is connected to a GEM15 Stand Alone SDM
• The features which are not supported in the above circumstances are:
— showing the CEM login user names
— showing any users connected since and connected from user ID
Server application management 8

The Application Management Tool window (Figure 8-4) is launched by
selecting Server Application Management from the Administration drop-
down menu (Figure 8-1), or from the Sun Server by changing the directory to
/opt/nortel/data/coreEMS/nodes/server/bin and issuing the command,
applman which is linked to the latest version of the Application Management
software.
Note: From the Sun Server, users control only applications on the server.
From the Element Browser, users control applications of all servers added
to the browser.
Server Application Management ensures that core software processes are

running and provides a mechanism for starting or stopping processes.

Figure 8-4
Application Management tool
Menu bar
The Application Management Tool window menu bar offers two options:
• Close - exits the Application Management interface.
• Action - allows the user to Rts, ManB, or OffL an application.
Information window
The information window provides the user with the following application
information:
• Application Name - displays the application name in a hierarchical
structure.
• Process ID - displays the process ID of the application that is running on
the server.
• Version - displays the software version of the application, after the
application has begun.
• State - displays the current status of the application.
• InSv/ManB/Fail Time - displays the time when the application is started,
stopped, or the time it fails.
• Service Ports - displays the service names and port numbers that the
application will listen on.

Application states
An application can exist in one of the following states:
• InSv (In Service) - indicates the application is functioning properly.
• IsTb (In Service Trouble) - indicates part of the application functionality
is not working.
• ManB (Manual Busy) - indicates the application has been manually
halted.
• Fail - indicates the application has been abnormally terminated and cannot
be restarted.
• OffL (Off Line) - indicates the application is not running.
The ManB state is a transitional state between InSv/IsTb and Fail/OffL. To

return a failed application back to service, manually busy the application first,
and then return-to-service the application.
One or more applications form a package. The state of the package depends on
the state of all related applications. For example:
• If all applications of a package are in the same state, then the state of the
package is the same as its applications.
• If one or more applications are in the IsTb state, the state of the package is
IsTb.
• If one or more applications have died or are busied, and at least one other
is still running, the state of the package is IsTb.
• If one or more applications have died and the rest are all busied, the state
of the package is Fail.
Process Control attempts to restart failed processes every 15 minutes.
Application management commands

This section explains how to change the status of applications. To manual
busy, return-to-service, or offline an application, select the application from
the information window, by clicking on it and select ManB/Rts/OffL from the
pop-up menu (Figure 8-5). This action also applies to a package of
applications. For the user to be able to perform these commands, the user has
to be defined as a CEMAdminUser in the LDAP/DCE Security Server (refer
to NTP 411-8111-511 for more information).

Figure 8-5
Application Management commands
This action can also be performed using the Action drop-down menu from the
menu bar.
Once ManB is selected, a prompt appears confirming the action. The ManB
confirmation window is shown in (Figure 8-6). When ManB, an application
has a default grace period of 60 seconds to finish its current process.
Figure 8-6
ManB Confirmation Window
Application management status

If the connection between the server process control and Application
Management is lost, a Lost Connection to Process Control message
displays at the bottom of the information window and changing the
application status is not an option.
If the connection between the Element Manager Browser and the server is
lost, a Lost Connection to the Server message displays at the bottom of the
information window and all application states on that server will be shown as
Unknown.

Command line interface

To launch the command line interface, change the directory on the OMC-S
server to /opt/nortel/data/coreEMS/nodes/server/bin/ and issue the
command, applman -c.
Command line interface layout

The command line interface displays the application name, process ID,
software version, current state, and application in-service/manbusy/failed
time (Figure 8-7). The current root line on top of the interface displays the
current top level node opened for display. The status line displays the
software status and the command line provides for command entry.
Figure 8-7
Command Line Interface
***Nortel Network Process Control Tool v. 15.1 ***

Current root: /OMC-S/urc2d012-sanity
Application name Process ID Version State InSv/ManB/Fail Time
-------------------------------------------------------------------------------
EMAdapter 18196 GEM15 ManB 2002/02/20 09:36
OSSConvertor 18197 GEM15 InSv 2002/02/18 16:58
archive 597 GEM15 InSv 2002/02/18 16:58
cmNorm 2753 GEM15 InSV 2002/02/19 14:18
logNormalizer 18209 GEM15 InSv 2002/02/19 13:26
objectManager 18209 GEM15 InSv 2002/02/18 16:58
omBill 18213 GEM15 InSv 2002/02/18 16:58
tableAccessProxy 28007 GEM 15 InSv 2002/02/19 16:08
Status >
Command > busy omBill
Command line interface commands

Command line interface commands include:
• help - shows all available commands and syntax
• exit - quits the command interface
• rts <appl/pkg> - returns application/package to service
• busy <appl/pkg> - manually busies an application/package
• offl <appl/pkg> off-lines an application/package
• up - moves up one package level
• down <pkg> - opens the package for display
• refresh - refreshes and displays current application status
Note: The screen does not refresh automatically.

Change CEM password 8

Users may change their CEM password at any time by selecting Change CEM
Password from the Administration drop-down menu (Figure 8-1).
Figure 8-8
Change CEM Password window
The Change CEM Password window contains the items listed in Table 8-1.
Table 8-1
Change CEM Password window Fields and Buttons
Item Definition
Current Password This is a required field where the user’s

box current password is entered.
New Password box This is a required field where the user

enters the new password. The new
password entered will not be displayed;
each letter of the password will be
displayed as an ‘*.’
Confirm New This is a required field where the user

Password box enters the new password for
confirmation. The confirmation
password entered will also not be
displayed; each letter of the password
will be displayed as an ‘*.’
OK button Clicking this button initiates the

password change via the Server name
entered in the Server field on the CEM
Login window.
—sheet 1 of 2—

Table 8-1
Change CEM Password window Fields and Buttons
Item Definition
Cancel button Clicking this button cancels the user’s

attempt to change the current
password. The Change CEM Password
window closes and the user is required
to attempt login again.
—sheet 2 of 2—
Change CEM password error windows

Table 8-2 describes the possible error windows that may be displayed if the
CEM password change is unsuccessful. Once the error message is
acknowledged, the user can reattempt to change the current password.
Table 8-2
Change CEM Password Error Windows
Invalid Current Password! This error message is display when an incorrect current
password is entered in the Current Password field. Upon
acknowledging the message, the user may enter the
correct Current Password.
Password Change Failed: Invalid This error message is displayed when the new password
Password Syntax entered does not comply with password syntax policy
enforced by the LDAP Directory Server or the DCE
Security Server. Upon acknowledging the message, the
user may enter a new password that complies with the
password syntax policy.
Password Change Failed: Invalid This error message is displayed when the new password
Password Length entered does not comply with password syntax policy
enforced by the LDAP Directory Server or the DCE
Password Change Failed: Password This error message is displayed when the new password
should not be trivial, e.g. zero-length, entered does not comply with password syntax policy
userId=password enforced by the LDAP Directory Server or the DCE
—sheet 1 of 2—

Table 8-2
Change CEM Password Error Windows
New Password cannot be empty! The error message is displayed when the new password
field is empty.Upon acknowledging the message, the user
may the new password that complies to the password
syntax policy.
New Password and Confirmation This error message is displayed when the confirmation
Password do not match! password does not match the new password entered. The
confirmation password has to match the new password.
Upon acknowledging the message, the user enter in the
new password again in the Confirm New Password field.
Password Change Failed: Password This error message is displayed when the new password
can not be the same as previous entered in the Change Password dialog window exists in
password the password history. Upon acknowledging the message,
the user enter in the new password that has not does not
exist in the password history. The number of passwords
that can be stored in the password history can be
configured on the LDAP Server or on the DCE Security
Server.
Password Change Failed: User is not This error message is displayed when the user attempts to
allowed to change password change his/her password and the configuration on the
LDAP Server or the DCE Security Server is set to User not
permitted to change password. For the users to be able to
change their passwords, the security server should be
configured to enable this functionality.
—sheet 2 of 2—
CEM password complexity

The password for logging into the OMC-S Browser shall meet the following
levels of complexity:
1. The password shall consist of a minimum number of characters which can
be configured by the User Database Administrator.
2. The password shall consist of a combination of alphanumeric and special
characters.
3. The password shall not be the same as the user id.
4. The password shall expire after a specific number of days.The expiration
period can be configured by the User Database Administrator.
5. Previous passwords shall not be reused. Previous passwords to be
excluded from reuse are stored in a password history repository. The
number of passwords stored in the password history can be configured by
the User Database Administrator.

The OMC-S system will respond appropriately to any error indications when
the password complexity described above has not been followed at the time of
user changing the password.
The OMC-S system will utilize the necessary User Database commands to
authenticate a user and will respond appropriately to any error indications
with respect to the user authentication.
System initiated change of the CEM password

The CEM Change Password window is displayed when the user attempts to
log into the CEM with an expired password. The CEM System determines
that the user’s password had expired and displays this window in order for the
user to change the current password. The new password has to comply to the
designated password policy on the Directory Server (in case of CEM in
LDAP environment) or the DCE Security Server (in case of CEM in DCE
environment).
User initiated change of the CEM password

This is a functionality provided to the user to change the current password
prior to its expiration. The user can attempt to change the CEM password
once he/she has successfully logged into the CEM browser. A sub-menu item
is provided under the Administration menu item for this purpose. Once the
CEM Change Password window is displayed, the user is able to change the
current password.
Group Access Control 8

The functionality of Group Access Control is a privileged function only
permitted to the CEMAdminUser. The initiating this functionality has to be
defined as a CEMAdminUser in the LDAP/DCE Security Server.
The Group Access Control menu item is displayed under the Administration
menu (Figure 8-1). Clicking on this menu item displays the Configure Group
Access Control window.
Restricting the operations a particular user can perform on a Network

Element is implemented by defining the “User Classification” such as
CMUser, PMUser, FMUser, etc. in the user’s profile on the LDAP Directory
Sever or the DCE Security Server. These User Classifications apply to that
user on all of the Network Elements added into the CEM System.
Group Access Control allows an administrator to configure the types of

operations that are allowed on each of the Network Elements added into the
CEM System by users belonging to Customer Defined Groups. The users in a
particular Group can potentially have different operation privileges on each of
the Network Elements.

Groups can either be defined by the customer or can simply be a single User
Classification. A Customer Defined Group consists of a combination of User
Classifications and Network Elements (i.e. a series of User Classifications are
associated with one or more Network Elements). The operator privileges
defined by a User Classification are fixed and cannot be modified.
User groups
FMUser
For users belonging to this User Classification, the CEM System
automatically sets the operation privileges to permit access to all Fault
Management and all Observer Functions on all of the Network Elements
added into the CEM System.
Fault Management functions permitted to a FMUser:

• Manually clear an alarm.
• Acknowledge an alarm.
• Add notes associated with the given alarm.
CMUser
automatically sets the operation privileges to permit access to all
Configuration Management and all Observer Functions on all of the Network
Elements added into the CEM System. Of course, this only applies to
Network Elements that permit Configuration Management from the CEM
System.
Configuration Management functions permitted to a CMUser:

• Issue a table access command to read or change a DMS table.
• Add notes associated with the given component.
PMUser
automatically sets the operation privileges to permit access to all Performance
Management and all Observer Functions on all of the Network Elements
Performance Management functions permitted to a PMUser:

• Register an operational measurement for collection.
• Set up the export data needed to export OMs.
• Set the thresholds for the given OM group.
• Issue a billing manager command.

CTUser
automatically sets the operation privileges to permit access to all Call Trace
and all Observer Functions on all of the DMS Nodes added into the CEM
System.
Call Trace function permitted to a CTUser:

• Activate a Trace.
• Deactivate a Trace.
• Delete Trace Records.
• View Trace Records.
• Add / Delete Notes associated with the given Trace Record.
Observer
automatically sets the operation privileges to permit access to all Observer
Functions only on all of the Network Elements added into the CEM System.
An Observer is a more restricted User Classification than those previously
described.
Fault Management functions permitted to an Observer:

• Retrieve all alarms between the given times. The active info and severity
fields can be used to filter the returned alarms. For example, a user can
request only active critical alarms.
• Retrieve an alarm based on its id.
• Retrieve all active alarms.
• Get a histogram of the alarm activity for the given path. If the path is /, the
histogram of the all alarms will be returned.
Configuration Management functions permitted to an Observer:

• Get all components below the given path.
• Register for notifications from components below the given path. The
notifications sent will only be for registered paths. If no registration is
ever issued all notifications are sent.
• De-register from getting notifications from components below the given
path.
Performance Management functions permitted to an Observer:

• Get a list of resources for the given OM group.
• Get the operational measurements for the given group.
• Get Archived Resources.

• Get the list of collected operational measurements.

• Get the list of operational measurements that are currently not being
collected.
• Get the information about the Network Element. This is the type and
version and name of the switch.
• Get the export settings.
• Get the thresholds for the given OM group.
• Get the thresholds for the given group.
Call Trace function permitted to an Observer:

• View Trace Records
CEMAdminUser
automatically sets the administration privileges to permit the access to all the
Observer and administrative functions on the CEM System.
Administrative Functions permitted to the CEMAdminUser:

• Configuration of the user operating privileges on the Network Elements
• Server System Administration which involves administration of the CEM
Applications (processes) running on the CEM Server.
Groups must first be defined on the LDAP Directory Server or the DCE
Security Server and then the Group must be correlated to a particular user. On
the LDAP Directory Server, the Group names are first added to the Group
Organizational Unit. The correlation of a Group to a User is then
accomplished by defining the Group as a value of the attribute “ou” belonging
to that user.
Example
UserA has the user classification as CMUser, FMUser. These classifications
are values assigned to the attribute “ou” in the UserA profile.
On a LDAP Server, Groups have to be defined on the LDAP Server under the
Group Domain:
CMUser is defined
FMUser is defined
PMUser is defined
CTUser is defined
Observer is defined
CEMAdminUser is defined
GroupA is defined

GroupB is defined
GroupC is defined
UserA has the group classification as CMUser, GroupA, GroupB which

means that all the operation privileges set for users of CMUser, Group A and
Group B apply to UserA. CMUser, GroupA and GroupB would therefore be
the values assigned to the attribute “ou” in UserA’s profile.
On the DCE Security Server, the correlation between the Group and the User
belonging to the particular Group is established by defining the individual
user as a principle of that Group.
The Group privileges established by the CEM administrator are saved on all
of the CEM Servers. These privileges go into effect when the user belonging
to the Group logs into the CEM Browser and establishes connection with the
DMS-nodes corresponding to CEM Servers.
If the user is already logged into the CEM Browser and has established
connections with the DMS nodes prior to the CEM administrator modifying
the privileges for that user’s Group, the user shall maintain its prior privileges
until the user re-establishes the connections with the DMS-node by either
logging out completely from the CEM browser and logging in again or
disconnecting the connection to the DMS node in the existing login session
and then reconnecting to the DMS-node.
Configure Group Access Control window

The Configure Group Access Control window (Figure 8-9) allows the user to
view/set/modify the current setting for allowing users of a defined Group to
perform certain functions on each of the Network Elements added into the
current CEM Browser.

Figure 8-9
Configure Group Access Control Window
Configure Group Access Control window menu bar

The menu bar offers the following menu selections: File Help.
The File menu (Figure 8-10) contains the following item:

• Close - Closes the window and the user exits from the Configuration of
Group Access Control functionality.
Figure 8-10
File Menu
The Help menu (Figure 8-11) contains the following items:

• About Group Access Control - Provides information about the Group
Access Control.
• User’s Guide - Display the user guide.

Figure 8-11
Help Menu
Field descriptions
• Group Name - This is the field that indicates the name of the Group as
defined in the LDAP Server or the DCE Security Server.
• Region - This is the field that the region in which the corresponding
Network Element(s) are defined.
• Network Elements - This is the field that indicates the Network Element
name, for example, the MSC name, HLR100 name, SGSN name etc., on
which the corresponding access privileges apply.
• FM Functions - This is the field that indicates whether or not Fault
Management functions are allowed on the corresponding Network
Elements. The values in this field can be either ‘Y’ indicating that the FM
functions and all the Observer functions are allowed or ‘N’ indicating that
the FM functions and all the Observer functions are not allowed.
• CM Functions - This is the field that indicates whether or not
Configuration Management functions are allowed on the corresponding
Network Elements. The values in this field can be either ‘Y’, indicating
that the CM functions and all the Observer functions are allowed or ‘N’,
indicating that the CM functions and all the Observer functions are not
allowed.
• PM Functions - This is the field that indicates whether or not
Performance Management functions are allowed on the corresponding
Network Elements. The values in this field can be either ‘Y’, indicating
that the PM functions and all the Observer functions are allowed or ‘N’,
indicating that the PM functions and all the Observer functions are not
allowed.
• CT Functions - This is the field that indicates whether or not Call Trace
functions are allowed on the corresponding Network Elements. The
values in this field can be either ‘Y’, indicating that the PM functions and
all the Observer functions are allowed or ‘N’, indicating that the PM
functions and all the Observer functions are not allowed.
• Observer Only Functions - This is the field that indicates whether or not
Call Trace functions are allowed on the corresponding Network
Elements. The values in this field can be either ‘Y’, indicating that the PM
functions and all the Observer functions are allowed or ‘N’, indicating
that the PM functions and all the Observer functions are not allowed.

• Filter - This is the field where the user may enter a string that will filter
out and only display the list of Group Access Information that have that
matching string in any of the above fields.
Pop-up menu
A pop-up menu is available on the Configure Group Access Control window
(Figure 8-9) which can be displayed by clicking on the right mouse button. The
items in the Pop-Up menu are enabled only if the one or more rows are selected
prior to initiating the display of the menu.
Figure 8-12
Group Access Control Pop-Up Menu
The pop-up menu contains the following options:

• Allow FM Functions - allows restricted Fault Management Functions
and all Observer Functions to be performed on the Network Element(s)
indicated in the selected row(s) by the users belonging to Group(s)
indicated in the selected row(s).
• Allow CM Functions - allows restricted Configuration Management
Functions and all Observer Functions to be performed on the Network
Element(s) indicated in the selected row(s) by the users belonging to
Group(s) indicated in the selected row(s).
• Allow PM Functions - allows restricted Performance Management

• Allow CT Functions - allows restricted Call Trace Functions and all

Observer Functions to be performed on the Network Element(s) indicated
in the selected row(s) by the users belonging to Group(s) indicated in the
selected row(s).
• Allow Observer Functions Only - allows only the Observer Functions to
be performed on the Network Element(s) indicated in the selected row(s)
by the users belonging to Group(s) indicated in the selected row(s).
• Disallow FM Functions - disallows restricted Fault Management
• Disallow CM Functions - disallows restricted Configuration
Management Functions and all Observer Functions to be performed on
the Network Element(s) indicated in the selected row(s) by the users
belonging to Group(s) indicated in the selected row(s).
• Disallow PM Functions - disallows restricted Performance Management
• Disallow CT Functions - disallows restricted Call Trace Functions and
all Observer Functions to be performed on the Network Element(s)
• Disallow Observer Functions Only - disallows Observer Only Functions
to be performed on the Network Element(s) indicated in the selected
row(s) by the users belonging to Group(s) indicated in the selected row(s).
Even though this option is selected, if the FM, CM, PM, or CT functions
are set to ‘Y’, the users belonging to the Group(s).

Button functionality
Down at the bottom of the Configure Group Access Control window (Figure
8-9), there are radio buttons which can be set, or not set, by an Administrative
user to allow or disallow the appropriate functions.
Note: None of the radio buttons have an effect until the Apply button is
clicked. The settings of the radio buttons only affect the selected row(s).
When none of radio buttons are set and Apply button is clicked, then the
users belonging Groups indicated in the selected row(s) would be not be
permitted to do any CEM functionality.
• Allow FM Functions - This is a radio button: when set, implies that the
restricted Fault Management Functions and all Observer Functions are to
be permitted on the Network Element(s) indicated in the selected row(s)
When not set, implies that the restricted Fault Management Functions and
all Observer Functions are not to be permitted on the Network Element(s)
• Allow CM Functions - This is a radio button: when set, implies that the
restricted Fault Management Functions and all Observer Functions are to
be permitted on the Network Element(s) indicated in the selected row(s)
When not set, implies that the restricted Fault Management Functions and
all Observer Functions are not to be permitted on the Network Element(s)
• Allow PM Functions - This is a radio button: when set, implies that the
restricted Performance Management Functions and all Observer
Functions are to be permitted on the Network Element(s) indicated in the
selected row(s) by the users belonging to Group(s) indicated in the
selected row(s).
When not set, implies that the restricted Performance Management

Functions and all Observer Functions are not to be permitted on the
Network Element(s) indicated in the selected row(s) by the users
belonging to Group(s) indicated in the selected row(s).
• Allow CT Functions - This is a radio button: when set, implies that the
restricted Call Trace Functions and all Observer Functions are to be
permitted on the Network Element(s) indicated in the selected row(s) by
the users belonging to Group(s) indicated in the selected row(s).
When not set, implies that the restricted Call Trace Functions and all

Observer Functions are not to be permitted on the Network Element(s)

• Allow Observer Functions Only - This is a radio button: when set,
implies that Observer Only Functions are to be permitted on the Network
Group(s) indicated in the selected row(s). When this button is set, all of
the other radio button are un-set automatically.
When not set, implies that Observer Only Functions are not to be
permitted on the Network Element(s) indicated in the selected row(s) by
the users belonging to Group(s) indicated in the selected row(s).
• Apply - This button is to apply the setting indicated by the radio buttons
to the selected row(s).
• Save - This button is to submit the Group Access Control information into
the CEM system.
• Close - Closes the Group Access Control window.
Error/status messages
• A Warning window is displayed information regarding whether or not the
Group Access Control information could be saved successfully on the
given server in the Current CEM System.
• A Confirm window is displayed when the user attempts to close the
Group Access Control window without first attempting to Save the
information
Group Access Control in a W-NMS environment

Group Access Control configured within the W-NMS GUI does not affect the
operations performed within CEM. CEM operations are controlled by the
access control setup within the CEM System.
The W-NMS user privileges will be based on the Group names assigned to the
“ou” attribute in their LDAP profile. The “ou” attribute can have the value of
any of the predefined Groups such as CMUser, PMUser, FMUser, CTUser,
CEMAdminUser or Observer. It can also have value of any other customer
defined groups.
Note: A W-NMS User that is defined to be a CEMAdminUser (“ou”

assigned a value of “CEMAdminUser”) will be able to configure Group
Access Control within the CEM System.


9-1
On-line help 9
The OMC-S Element Manager contains several on-line help facilities,
designed to provide you with the information you need, when you need it,
without leaving the application you are working in. You can find information
automatically, according to where you are in the tool.
The information accessed through on-line help contains the information on

the latest release available. If you are running an older release, you may see
information accessed through on-line help that does not match the release you
are running. You will see the logs pertaining to the latest release.
Note: The CEM online help is not available to users for SIG, GGSN and
SGSN network elements.
Help can be accessed one of four ways:

• selecting Help from the Element Manager menu bar
• selecting Help from an Alarm Info window
• clicking on the (?) button in a Performance Management window
• selecting Help from the Performance Manager menu bar
The following paragraphs describe the four ways to access Help.
Element Manager Help menu 9

The Help menu (Figure 9-1) has three items:
• On Version
• User’s Guide
• Help on help.

9-2 On-line help
Figure 9-1
Help menu
The following paragraphs describe the individual items in the Help menu.
On Version...
Selecting “On Version...” will display a window (Figure 9-2) showing the
details about the version of the Core Element Manager being used. To close
the window, click anywhere on the window.
Figure 9-2
Core Element Manager Version window
User’s Guide
Selecting “User’s Guide” allows online viewing of the OMC-S Element
Manager User Guide. When you click on “User’s Guide” from the Help
menu, it will take you to the beginning of the OMC-S Element Manager
User’s Guide in the Help facility.
Help on Help
Selecting “Help on help” opens the Help facility if it is not already open.

On-line help 9-3
Help Info window 9

Double-clicking an alarm in the Fault Management window brings up an Info
window (Figure 9-3).
Figure 9-3
Info window
Click on the Help button at the bottom of the Info window to open the Help
window and show help for the selected alarm.

9-4 On-line help
Help User’s Guide 9

The Help window (Figure 9-4) has buttons on its toolbar that allow you to
navigate Help pages (backward and forward), print, set up the page, add and
delete annotations and import and export annotations.
Figure 9-4
Help window
By moving the cursor over the buttons you can see the function for each
button. The left pane of the window contains the table of contents and search
facility. You can navigate to any of the items in the table of contents by
clicking on it. The right pane of the window displays a page of help content.
Note: The Help window toolbar will display a spinning Nortel globemark
(Figure 9-5) to indicate when a page is loading.
Figure 9-5
Nortel globemark

On-line help 9-5
Annotations
Annotations are user-defined notes which can be added to supplement the
help content. They are displayed to the user in a pop-up web browser window.
Only one annotation is allowed per page.
Note: Annotation functionality is unavailable when Element Manager is

launched from NSP using Java Web Start.
Note: Although multiple annotations can be exported and stored in the

DAT directory, only one can be selected at a time.
Add or edit an annotation

To add a new annotation or edit an existing annotation, click on the annotation
icon (Figure 9-6) on the Help window toolbar.
Figure 9-6
Annotation icon
An annotation dialog box is displayed. Type your note and click “Save”.
Figure 9-7 provides an example. Be aware that the pop-up web browser
window will display the annotation as HTML text.
Note: You can use Ctrl-x to cut, Ctrl-c to copy and Ctrl-v to paste from
the system clipboard.
Figure 9-7
Adding an annotation

9-6 On-line help
The text formatting such as line breaks may not be reflected in the pop-up
web browser window (see Figure 9-13).
HTML tags can be entered into the annotation to enable text formatting
(Figure 9-8).
Figure 9-8
Adding HTML text to annotation
To check the correctness of the HTML text, click on the “Verify HTML”. If
the HTML text is correct, a “Verify HTML” message box appears (Figure 9-
9).
Figure 9-9
Verify HTML
If the HTML text is incorrect, an “HTML parsing errors” box appears (Figure
9-10).

On-line help 9-7
Figure 9-10
HTML parsing errors
If the HTML text is correct, the text formatting will be reflected in the pop-up
web browser window (see Figure 9-14).
View the annotation list

To view all existing annotations, click on the annotation icon (Figure 9-11).
All existing annotations are then listed in the left pane of the help window. To
view an annotated help page, click on an annotation in the list and the affected
help will appear in the right pane of the window.

9-8 On-line help
Figure 9-11
Help window with annotation list
View an existing annotation

If a help page has an annotation, the web icon (Figure 9-12) will be
accessible. Click on the web icon. The note is displayed in a pop-up web
browser window. For an example of an annotation without using HTML
formatting, see Figure 9-13. For an example of an annotation using HTML
formatting, see Figure 9-14.
Figure 9-12
Web icon

On-line help 9-9
Figure 9-13
Annotation in pop-up window without using HTML formatting
Figure 9-14
Annotation in pop-up window using HTML formatting
Delete annotation
To delete the annotation, click on the delete icon (Figure 9-15).
Figure 9-15
Delete icon
A “Delete annotation” dialog box is displayed (Figure 9-16).

9-10 On-line help
Figure 9-16
Delete annotation
Import annotation
The import annotation icon (Figure 9-17) allows you to import an annotation
from outside the OMC-S Element Manager. Click on the import icon.
Figure 9-17
Import icon
Go to the directory containing the file you want to import (Figure 9-18).
Figure 9-18
Import annotation file
Select the file and click Open.

On-line help 9-11
Note: You can only have one annotation per file. If you already have an
annotation file for the current page and you import an annotation, a dialog
box will prompt you to confirm replacing an existing annotation file
(Figure 9-19).
Figure 9-19
Replace annotation file
Export annotation
You can export an annotation to a directory by clicking on the export icon
(Figure 9-20).
Figure 9-20
Export icon
Locate the directory to export the annotation file, specify a file name for the
export file and click on Save (Figure 9-21).

9-12 On-line help
Figure 9-21
Export annotation file
Search
The Help system uses a full-text search engine which not only retrieves files
with matching text but also ranks the “hits” according to the number of items
found.
To access the search panel, click on the search icon (Figure 9-22). To initiate a
search, type the search text in the “Find” field and press Return. Multiple
terms may be specified by separating them with commas or spaces in the
“Find” field.

On-line help 9-13
Figure 9-22
Search window

9-14 On-line help
Figure 9-23
Found items
The number returned in the left column indicates the number of times the
query was matched in the listed topic.
The red circle indicates the ranking of the matches for that topic. There are
five possible rankings, ranging from a completely filled circle indicating the
best matches to a completely empty circle indicating the least applicable
matches.
Items found are highlighted in the right pane of the window.
Help in the Performance Manager menu

Help can be accessed from the Performance Manager window (Figure 9-24).
The Help menu allows you to select “MSC OM Reference Manual” and the
“HLR OM Reference Manual”.

On-line help 9-15
Figure 9-24
Help using (?)

Another way to access help is to click on the (?) button on the following
Performance Management windows: Performance Manager (Figure 9-25),
New Study, Threshold Manager, and Graph Manager. You will automatically
be shown to the section of Help that pertains to the selected item in the list.
Figure 9-25
Performance management window with query button

9-16 On-line help

A-1
Index A
A C
Action(s) 4-18 Call Trace 1-8
icons 4-7 Cancellation index xxx
Alarm 3-26 CEM Security 1-24
Alarm data Change CEM Password 8-10
export 2-25 Group Access Control 8-13
Alarm Severity 3-4 User Login Window 1-3
Alarm(s) 4-11 Clear Default Login Id 3-5
clearing 4-15 Clear Layout 3-5
manual clear 4-15 Cleared by 4-13
status colors and letters 4-14 Color Nodes by 3-4
Annotation 9-5 Configuration 1-8
add or edit 9-5 menu 1-10, 3-3
delete 9-9 menu options 1-10, 3-6, 3-31
export 9-11 Configuration Management
import 9-10 window 1-6, 3-7
view existing 9-8 in list mode 3-21, 3-22, 3-26, 3-27
view list 9-7
Application(s) D
start 1-2 Drill down 3-3
Drill up 3-3
B DrillDown 3-4
Background DrillUP 3-4
clear 3-5
set 3-5 E
background image Element(s)
clear 3-13 information window 3-7
format 3-12 Execute 7-17
set 3-12
F
Fault 1-8
menu 1-10
Fault Management
window 1-6

A-2 Index
File 1-8 P
menu 1-9 Performance 1-8
Filter(s) 4-18 Propogated Severity 3-4
H R
Help Region 3-23
menu 9-1
search 9-12
Hide 3-4 S
Set Background 3-12
Set Default Login Id 3-5
I State 3-26
icon(s) Sub Alarms 3-26
arrange 3-13
Info 3-4
Info Log 2-20 T
Information bubble tool bar 1-6, 3-2, 4-4
with the number of sub-elements 3-14 icon descriptions 3-3, 4-5
L W
Log(s) Window(s)
informational 2-20 display 2-2
M
MAP
commands
adding 7-12, 7-13
menu bar 1-6
N
Network
example layout 2-12
setup 2-11

test
Family Product Manual Contacts Copyright Confidentiality Legal
GSM / UMTS
Voice Core Network
OAM User Guide
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.nortelnetworks.com/td
Copyright © 1996–2005 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-503
Product release: GSM18/UMTS04
Document version: Preliminary 05.02
Date: March 2005
Originated in the United States of America

411-8111-503 05 02 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

411-8111-503 05 02 PDF

Uploaded by

Copyright:

Available Formats

411-8111-503

GSM18/UMTS04 Preliminary 05.02 March 2005

Document number: 411-8111-503

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright © 1996–2005 Nortel Networks, All Rights Reserved

NORTEL NETWORKS CONFIDENTIAL

Copyright notice/license for Perl

“Copyright Holder” is whoever is named in the copyright or copyrights for

“You” is you, if you're thinking about copying or distributing this Package.

411-8111-503 Preliminary 05.02 March 2005

Usenet or an equivalent medium, or placing the modifications on a

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

7. C subroutines (or comparably compiled subroutines in other languages)

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

411-8111-503 Preliminary 05.02 March 2005

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

411-8111-503 Preliminary 05.02 March 2005

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

• CEM support for R4 BICN

411-8111-503 Preliminary 05.02 March 2005

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

411-8111-503 Preliminary 05.02 March 2005

About this document xxvii

Getting started 1-1

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

Launching of STORM EM from CEM GUI 1-24

File menu 2-1

Configuration management 3-1

411-8111-503 Preliminary 05.02 March 2005

Logical mode 3-22

Fault management 4-1

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

Filters tab 4-19

Performance management 5-1

411-8111-503 Preliminary 05.02 March 2005

Supported OM groups 5-77

Call trace 6-1

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

Preferences menu 7-17

Administration management 8-1

411-8111-503 Preliminary 05.02 March 2005

Configure Group Access Control window 8-17

On-line help 9-1

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

Figure 2-16 Disconnect confirmation 2-17

411-8111-503 Preliminary 05.02 March 2005

Figure 3-37 User ID screen 3-51

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

Figure 3-88 Add GWINV Table Tuple 3-94

411-8111-503 Preliminary 05.02 March 2005

Figure 3-139 Submitting Tuples 3-140

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

Figure 5-8 Apply Template to NEs 5-19

411-8111-503 Preliminary 05.02 March 2005

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

Figure 6-46 Detach CTR Example 6-38

411-8111-503 Preliminary 05.02 March 2005

Figure 7-40 Launch GUI window 7-54

GSM / UMTS Voice Core Network OAM User Guide GSM18/UMTS04

Table 3-6 Table TRKGRP Datafill 3-119

411-8111-503 Preliminary 05.02 March 2005