Professional Documents
Culture Documents
D02112 A1 OMC User Interface
D02112 A1 OMC User Interface
Global Star Solutions ULC reserves the right to revise this documentation and to make changes in content from time to time
without obligation on the part of Global Star Solutions ULC to provide notification of such revision or change.
Global Star Solutions ULC provides this documentation without warranty of any kind, either implied or expressed, including, but
not limited to, the implied warranties of merchantability and fitness for a particular purpose. Star Solutions may make
improvements or changes in the product(s) and/or the program(s) described in this documentation at any time.
If you are a United States government agency, then this documentation and the software described herein are provided to you
subject to the following:
United States Government Legend: All technical data and computer software is commercial in nature and developed solely at
private expense. Software is delivered as Commercial Computer Software as defined in DFARS 252.227-7014 (June 1995) or as a
commercial item as defined in FAR 2.101(a) and as such is provided with only such rights as are provided in Star Solutions's
standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR
252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion
of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, this
User Guide.
Star Solutions, the Star Solutions logo, iCell, Softexchange, Sonata, Sonata Access Tandem, Sonata HLR, Sonata IP, Sonata MSC,
Sonata WLL, and Telos are registered trademarks or trademarks of Global Star Solutions ULC and its subsidiaries.
Intel and Pentium are registered trademarks of the Intel Corporation or its subsidiaries in the United States and other countries.
Microsoft, Windows, Windows NT, and NetMeeting are registered trademarks of Microsoft Corporation. Sun, Java, and Solaris
are trademarks or registered trademarks of Sun Microsystems, Inc. Oracle is a registered trademark of Oracle Corporation. HP,
HP-UX, and HP Openview are trademarks or registered trademarks of the Hewlett-Packard Company. UTStarcom, the
UTStarcom logo, MovingMedia, mSwitch, and Total Control are registered trademarks or trademarks of UTStarcom, Inc. and its
subsidiaries.
Other brand and product names may be registered trademarks or trademarks of their respective holders.
CONTENTS
1 OMC OVERVIEW
Operations and Maintenance Center Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19
OMC Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20
Management Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20
System Architecture- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 21
A ACRONYMS
INDEX
LIST OF TABLES
Table 1 Text Convention Descriptions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13
Table 2 Notice Icon Descriptions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13
Table 3 Windows hosts File Paths - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 26
Table 4 OMC Navigator Menus - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
Table 5 Right-click Menu Options - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
Table 6 Network Object Icons - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35
Table 7 System Status Icons - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37
Table 8 Object Status Icons - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38
Table 9 Software Status Icons - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 39
Table 10 Active Alarms Fields - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50
Table 11 Alarm Details Fields - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50
Table 12 Operations for Non-Integer Fields - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 66
Table 13 OMC Security Objects - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 72
Table 14 User Role Management Objects - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 74
Table 15 Privilege Levels for Roles - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 75
Table 16 Archive Management Task Parameters - - - - - - - - - - - - - - - - - - - - - - - - - - - 82
Table 17 List of Acronyms - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 87
LIST OF F IGURES
Figure 1 Core Voice Network Document Map - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16
Figure 2 OMC Welcome Screen - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27
Figure 3 Login Screen - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 32
Figure 4 Status Bar Detail - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 32
Figure 5 OMC Navigator Elements - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Figure 6 Root Object and Network Elements - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35
Figure 7 Software Objects - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36
Figure 8 Object Status Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38
Figure 9 Software Status Icons - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 39
Figure 10 Log Management Window - System logs - - - - - - - - - - - - - - - - - - - - - - - - - 43
Figure 11 Log Management Window - Operation logs - - - - - - - - - - - - - - - - - - - - - - - 44
Figure 12 Log Management Window - History Session - - - - - - - - - - - - - - - - - - - - - - - 45
Figure 13 System Log Search Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 46
Figure 14 System Log Filter Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 47
Figure 15 Active Alarms Display - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52
Figure 16 Alarm Notifications Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54
Figure 17 Audible Alarms Settings Screen - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55
Figure 18 Example of an OMC Performance Menu - - - - - - - - - - - - - - - - - - - - - - - - - - 57
Figure 19 Example of a CPU Utilization Performance Screen - - - - - - - - - - - - - - - - - - - 57
Figure 20 Example of Swap Utilization Report Screen - - - - - - - - - - - - - - - - - - - - - - - - 58
Figure 21 Example of a Report Save Screen - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 58
Figure 22 OMC Navigator Window - Database Table Icons - - - - - - - - - - - - - - - - - - - - 62
Figure 23 OMC Table Configuration Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 63
Figure 24 Example of a Large Table - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 65
Figure 25 Sorting Instances 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 65
Figure 26 Sorting Instances 2 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 66
Figure 27 Applying Filter - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 67
Figure 28 Results of a Filter - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 67
Figure 29 Instance of Filtered Results - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 68
Figure 30 Modifying Instances - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 68
Figure 31 Key Icon - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 68
Figure 32 Add MO Domain window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 73
Figure 33 Security Management Window - View Roles - - - - - - - - - - - - - - - - - - - - - - - 76
Figure 34 Security Management Window - View Users - - - - - - - - - - - - - - - - - - - - - - 78
Figure 35 Modify User Window - Access Type Tab - - - - - - - - - - - - - - - - - - - - - - - - - - 79
Figure 36 Archive Management Screen - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 82
Figure 37 Archive Management Add Task Screen - - - - - - - - - - - - - - - - - - - - - - - - - - - 82
This guide is intended for network architects, designers, operations and support
engineers responsible for the design, development, and maintenance of wireless
voice and data communications networks.
Conventions This guide contains text conventions, notices, figures, and screen captures.
Convention Description
Text represented as a This typeface represents text appearing on a terminal
screen display screen, for example login:.
Text represented as user This typeface represents commands entered by the
entry. user, for example, cd $HOME.
Text represented as menu, This typeface represents all menu, sub-menu, tab, and
sub-menu, tab, and field field names within procedures, for example:
names On the File menu, click New.
Text represented by This typeface represents a required variable, for example:
<variable> <filename>
Figures and Screen Captures This guide provides figures and screen captures as examples. These examples
contain sample data. This data may vary from the actual data on an installed
system.
Related Documentation The documentation is divided into Core Voice Network documentation and
Access Network documentation.
Core Voice Network Figure 1 maps the relationships between the Core Voice Network documents and
Documents therefore the order in which to read the documents.
For example, to operate and maintain the Signaling Server (SSVR), the document
map suggests reading the documents in the following order:
1 Core Voice Network Overview
2 Any relevant release notes
3 OMC User Interface Guide (this guide)
4 Core Voice Network Operations, Maintenance, and Provisioning Guide
5 Signaling Server Application Guide
The Core Voice Network Operations, Maintenance, and Provisioning Guide and
the OMC User Interface Guide (this guide) contain common procedures and
information for all Core Voice Network nodes (except for the Call Conference
Server and IMG), and should be read prior to reading the node-specific guides.
The node-specific guides are:
MSC Server Provisioning Guide, which contains the MSC-specific tables and
how to provision them.
MSC Server Operations and Maintenance Guide, which contains the
MSC-specific procedures for operating and maintaining the MSC Server, such
as procedures related to upper layer call processing protocols, Call Detail
Records (CDR), and MSC-specific alarms.
HLR and Authentication Center Guide, which contains all HLR-specific
provisioning, operations and maintenance procedures, and HLR-specific
alarms etc.
Signaling Server and Signaling Server Application Guide, which contains a
description of the Signaling Server Application and the various configurations
that accommodate the application. This guide contains SS7 operations and
maintenance procedures, SS7 alarm information, and operations and
maintenance procedures specific to the Signaling Server (SSVR) NE.
Access Server (MRF) Guide, which contains a description of the tones and
announcements available to the MSC, a description of the Media Resource
Function (MRF), and operations, maintenance, and provisioning procedures
specific to the Access Server.
Lawful Intercept Server Guide, which contains a description of the Lawful
Intercept Service, the components that are involved the service, and the
operations, maintenance, and provisioning specific to the Lawful Intecept
Server and Service.
The Call Conference Server Guide does not use the OMC or the common
operations and procedures that the other core nodes use. The guide contains a
description of the Call Conference Server, a description of the three-way call
functionality, and operations, maintenance, and provisioning procedures specific
to the Call Conference Server.
Access Network Documents The Access Network documents are covered in the iCell All IP Radio Access
Network Overview.
SIP Radio Access Network Refer to the SIP Radio Access Network Guide.
Documents
Third-Party Products For information about third-party products (for example, Solaris and Windows),
refer to the documentation distributed with that product.
Technical Support The Star Solutions Product Support Team delivers the support services required
for business and professional needs. Our product experts deliver Tier 1, 2 and 3
technical support directly to new and contract-entitled customers including the
following services:
Basic Support Package: Non-emergency technical support
Premium Support Package: 24 hours a day, 7 days a week, and 365 days a year
Emergency technical support
The Star Solutions Service Guide outlines the specific details for obtaining
technical support. The guide is available from a sales account manager. Refer to
the Service Guide for services and options specific to individual support plans,
including guidelines for problem severity and the technical resolution escalation
process.
Obtaining Technical Star Solutions maintains a global presence through its Technical Response and
Assistance Service Centers. These centers are available for technical telephone support to
entitled customers during normal business hours.
Warranty Support Star Solutions provides its customers warranty support per the terms of the Star
Solutions Warranty Statement for their equipment. Customers who require
warranty support should contact the Star Solutions Customer Service Center as
specified in the customer service guide or at:
http://www.starsolutions.com/service-support
Please include the name and part number of the guide being referenced. If
applicable, provide the chapter and page number.
Operations and The Operations and Maintenance Center (OMC) is a scalable Element
Maintenance Center Management solution for Star Solutions products. It provides centralized Element
Overview Management for distributed systems and components through a web-based user
interface.
The OMC runs in a client-server configuration. The server runs on the Sun
Microsystems Solaris 8 operating system; the client runs in Microsoft Windows
2000 or XP, or a UNIX workstation, using an Internet browser. The client, or OMC
user interface, allows the user to view network alarms, performance statistics,
network configuration, and security information.
The OMC operator uses the client, a web-based user interface (the OMC Console)
to view network alarms, performance statistics, and accounting information and
perform network and security configuration for the following Core Voice Network
elements:
MSC
HLR
Signaling Server (SSVR)
Access Server (MRF)
Lawful Intercept Server
The OMC Console allows for alarm and performance statistics monitoring for
these network elements:
iCell Base Station Controller (BSC)
iCell Base Transceiver Station (BTS)
S-RAN
Provisioning Server
The Call Conference Server and Media / Signaling Gateway (MG/SG) do not use
the OMC user interface.
The OMC Console is a Java-based application launched from a web server. The
web server is on TCP port 6688.
OMC Features This release of the Sonata OMC supports the following features:
Web-based user interface
Automatic client-side software installation
Configuration management interface for provisioning network elements
Security management
User action logging
Support for up to 10 simultaneous users
Comprehensive element and network management features - refer to
Management Features
The OMC Console can be deployed on a separate Windows 2000 or XP machine
or a UNIX workstation.
Management Features The OMC Console provides access to the following management features:
Network Management - The OMC manages all devices and network resources
on the Star Solutions Sonata network. OMC users see a unified network-wide
view of all system objects.
Logical grouping of network elements - Network Elements can be grouped
and sub-grouped on the OMC display to provide for easier management.
Performance Management visual interfaces - Collect and display statistics
with easy-to use intuitive and data sensitive interfaces. The basic OMC
performance management includes statistic graphing and reports that enable
operators optimize network resource usage and quality of service. The OMC
provides basic performance statistics such as system health, call processing
and mobility management status for the MSC Server, Signaling Server, Media
and Signaling Gateways, and base stations.
Real-time alarms and events - the OMC Fault Management Interface provides
real-time alarms and events, a method for acknowledging and manually
clearing alarms, audible alarms, and alarm display filtering.
Access Control and Security management strategy - User Role and Domain
Management provides access control via flexible privilege management
functions for users. It offers customizable authority-specific and domain
specific management.
Security management includes password controlled access to the OMC
console, and operations and session logging which tracks all user actions on
the OMC. User actions include logging in and out of the OMC console, NE
operations, and table changes.
OMC Log Management - The OMC includes OMC Server system errors and
warnings, operations logging to track user activities, and session logging.
The OMC Console, or Client, is the user interface to the Operations and
Maintenance Center (OMC) Server. This chapter describes the installation
procedure for the OMC Console.
Installation Overview The OMC console runs on Microsoft Windows 2000, XP or Sun Solaris
workstations and uses one of the browser platforms as follows.
Netscape 4.7 and above
Microsoft Internet Explorer 5.0 and above
To install the OMC Server, refer to the Core Voice Network Installation and Initial
Configuration Guide.
Installing the OMC Console To install the OMC Console on a Windows 2000 or Windows XP computer,
for Windows complete the following the installation tasks:
Before You Begin
Run the Installation Wizard
Ensure the Java Web Start (1.4.2 or later) is running on your computer. If not,
refer to Download and Install Java Web Start for Windows
Before logging in to the OMC Console several settings on the client PC must be
modified.
Table 3 shows the hosts file path for various Windows operating systems.
The <host name> is the host machine name for the OMC server application. Do
not use the OMC Server's IP address.
Note that the Java Web Start installation option will only appear if you do not
already have Java installed on your machine.
2 In the "Welcome to OMC Console" page, under "Start Here!--Install Java Web
Start", click Java Web Start 1.2.
3 To specify the folder path to download the Java Web Start 1.2 file, follow the
instructions on the dialog boxes to save the file to a location on your hard disk or
network.
4 When the download completes, click Close.
When complete, if a ReadMe file appears, click the Back button on your browser
to return to the Welcome page.
To start the OMC Console, refer to Starting the OMC Console, in Chapter 3
Operating the OMC Console.
Installing the OMC Console To install the OMC console on a Sun Solaris based computer :
for Solaris
Download Java Web Start for Solaris
Install the OMC Console For Solaris
Download Java Web Start for To download Java Web Start on Sun Solaris based computers:
Solaris
2 The <host name> is the host machine name for the OMC server application.
3 On the "Welcome to OMC Console" page, click Java Web Start 1.0.1.
4 Follow the instructions on the dialog boxes to save the file to a location on your
hard disk or network.
5 From the command prompt, create the $HOME/javaws directory, and type cd
$HOME/javaws to change to this path.
6 Unzip into the file you downloaded in step 4.
Be sure to note of the value for the path contained in the variable
$JAVA_HOME:echo $JAVA_HOME
Install the OMC Console For To install the OMC Console for Sun Solaris based computers:
Solaris
1 From a UNIX shell prompt, run the ./install/sh script.
2 Read the agreement displayed on the screen. Type Yes to accept the agreement
and proceed with the installation.
3 When prompted for path of Java, enter the path as noted
4 Close all instances of your Web browser.
To start the OMC Console, refer to Starting the OMC Console in Chapter 3,
Operating the OMC Console.
Starting the OMC Console Refer to Starting the OMC Console in Chapter 3, Operating the OMC Console.
This chapter describes operating procedures for the OMC Console and introduces
important graphical elements and concepts.
This chapter describes all of the procedures that may be available to a user. The
actual operating procedures that a user has access to depends on their assigned
role and associated privileges. Refer to Chapter 6, OMC User and Security
Management for information on roles and privileges.
Starting the OMC Console The OMC is a Java-based application launched from a web server. The web server
is on TCP port 6688. For example: http://hostname:6688/omc/omc.html
When starting the OMC, remember to use the OMC server's hostname not its
IP address.
To start the OMC Console:
1 Start up your web browser (Netscape or Internet Explorer), then navigate to the
following URL:
http://<host name>:6688/omc/omc.html
3 On the Login screen, type the User Name and Password, then click Login. The
OMC Navigator screen displays.
If the OMC fails to launch, follow the directions at the bottom of the OMC
Welcome Screen.
The OMC applet downloads the configuration information for all of the managed
network elements (NE) and displays the NEs on the OMC Navigator screen.
Status Bar When the OMC Console has started, the OMC Navigator window displays. Notice
the status bar at the bottom of OMC Console window. Refer to Figure 5 for the
location of the status bar.
The status bar displays:
A message whenever connection to the OMC Server is established or lost.
Information on cleared alarms. For additional information, see Clearing
Alarms in Chapter 4, Network Element Alarms and Performance Monitoring.
The status bar displays the most recent message. To display earlier messages,
click the icon on the right side of the status bar. The 20 most recent messages for
the session are displayed; earlier messages are discarded.
OMC Navigator Menus The OMC Navigator screen displays File, Fault, Security, and Schedule
menus. Table 4 describes the functions of these menus...
Table 4 OMC Navigator Menus
Menu Description
File>Print Print the content of the active screen
File>Exit Close and exit the OMC Console
Fault>Show Alarms Displays all active alarms and alarm details for
any item on the screen.
Fault>Audible Settings Configure audible alarms settings These filter
alarms events by the severity level.
Security>Log Management Display the Log Management screen. Refer to
Managing OMC Logs.
Security>Users and Privilege Set up user accounts. Refer to Chapter 6, OMC
User and Security Management.
Security>Current User Information Monitor current users. Refer to Chapter 6,
OMC User and Security Management.
Schedule>Upgrade
Right-Click Menus Depending on the object selected in the navigation tree, the right-click menu
options vary as shown in Table 5.
Table 5 Right-click Menu Options
OMC Navigator After logging in to the OMC Console, the OMC Navigator screen appears. This
screen contains a navigation tree.
To navigate the tree, click the key icon to expand and collapse tree branches. The
key icon appears beside an object only if there are other objects under it.
Application Pane
Navigation Tree
Database
Table
Window
Status
Bar
Root Object At the top of the tree is the root object, in the format <name>=config. This object
is defined during installation.
Network
Elements /
Objects
Network Element Objects Under the root object are the various network element objects. They represent the
managed network elements (NEs) in your network. Table 6 shows the icons that
represent each network object.
S-RAN
Provisioning Server
Mobility Server
Software Objects Under some network element objects (for example, MSC, HLR, SSVR), software
objects appear. Software objects are processes, database tables, or protocol
stacks that define the NE's configuration.
Keyicon
clickto
collapse
Software
Objects
Software objects can also have a parent-child relationship with other software
objects. A sphere icon, for example, indicates a parent object. Click the key icon
to expand or collapse the object. Software objects at the lowest level use the
folder icon.
Instances
Within software objects are instances that contain configuration values such as
parameters, table entries or XML elements.
Status Icons There are two types of status icons: system and object.
System Status Icons The system status icon is displayed in the bottom left of the OMC Console
window. It indicates the status of the network connection between the OMC
Server and OMC Console. Table 7 describes the meaning of each system status
icon.
Object Status Icons Objects in the navigation tree can be either active or pending. Active objects are
communicating normally with the network element (MSC, HLR, or CONX) and do
not have a border around their icon.
Pending objects are not communicating with the network element and show a
border around their icon. Objects are pending if:
A network element has been configured in the OMC Console but the NE has
not been installed, or the network connections between the OMC Server and
the equipment have not been established.
The hardware proxy has not been set up on the NE correctly.
Figure 8 shows an example of two active object, a pending object and a disabled
object. Table 8 describes the meaning of each icon.
Grey Check Mark The network element has been enabled, started,
has accepted the configuration from the OMC
Server, and is the standby element (if in an
active-standby pair).
Cyan border Data is being uploaded from the proxy to the OMC
Server. You cannot expand the object until the
upload has completed.
This applies to the MSC Server network object
only.
Red border The OMC Server sent configuration data to the
network object, but the network object refused
the configuration.
Software Status Icons Software status icons appear in the Status field of a software instance as
shown in Figure 9. Table 9 describes the meaning of each software status
icon.
Figure 9 Software Status Icons
Icon Description
The OMC Server and the network object
accept the configuration.
Icon Description
The OMC Server accepted the
configuration data, and is waiting for the
network object to accept the
configuration.
The OMC Server sent configuration data to
the network object, but the network
object refused the configuration.
A red X reflects a serious condition that
requires corrective action. Refer to the
appropriate Operations and Maintenance
Guide.
Network Element Group The OMC organizes Network Elements (NE) into groups. The user can:
Configuration Create an NE group
Add NEs to the group
Modify an NE
Move an NE to another group
Remove an NE from the group
A group is useful if there are sub-networks within the larger network. For
example, if there are a number of MSCs which serve different geographical areas,
a group can be created for each geographical area which would include the NEs
related to this area and to the MSC (BSC, Access Server, etc.).
The root object (which defaults to config=telos) can contain both NEs and
Groups. A Group can, in turn, contain NEs as well as other Groups.
4 Complete the fields in the table as appropriate for the new NE.
5 Click Submit.
Modifying a Network Element Some of the basic parameters that describe an NE may be modified depending on
the type of NE.
For an MSC, SS, HLR, Access Server, and Lawful Intercept Server, these
parameters are:
hostname
administrationState - can be set to start or stop, which is the equivalent of the
cpu_start and cpu_stop commands issued directly on the NE. While
this command is in progress, the NE will appear with a gray border.
For a BTS and BSC, the parameters that can be modified are:
versioninfo
hostname
To modify an NE:
1 Start the OMC Console. See Starting the OMC Console.
2 Right-click the NE.
3 Select Configuration -> Modify.
4 Click Yes.
Managing OMC Logs The traceability functionality of OMC operations helps the management and
maintenance of system administrators. To maintain adequate traceability, the
system automatically enables log management when the OMC starts running,
recording all processes and operator actions as necessary.
Logs are categorized by severity level, where the levels are from 1 to 6, with 1
being the most severe and 6 being the least severe.
The log management module provides an archival method for both log files and
databases. You can customize their backup strategies and perform manual
backup operations.
Session Logs - keeps a history of all user sessions - all logout activities by user
name, including where the user logged in from, login and logout time, and
total session time. Logs include:
User Name
Logout Type (Logout normally, Logout for too-long idle, Logout forcedly,
Logout for client exception)
User's IP address
Login time
Logout Time
Session Time
5 Click any column header to sort logs by that field. An arrow shows which field is
being used to sort the logs and whether the logs are sorted in ascending or
descending order.
6 Select Page Size at the top of the window and change the number of logs
displayed in the window, from the drop-down list.
7 Click Refresh at the top of the window to display any new logs.
5 Click any column header to sort logs by that field. An arrow shows which field is
being used to sort the logs and whether the logs are sorted in ascending or
descending order.
6 Select Page Size at the top of the window and change the number of logs
displayed in the window, from the drop-down list.
7 Click Refresh at the top of the window to display any new logs.
5 Click any column header to sort logs by that field. An arrow shows which field is
being used to sort the logs and whether the logs are sorted in ascending or
descending order.
6 Select Page Size at the top of the window and change the number of logs
displayed in the window, from the drop-down list.
7 Click Refresh at the top of the window to display any new logs.
Searching for Logs There is a search feature which allows an operator to search for OMC logs by
a number of fields. The fields used for searching depend on the type of log
(System, Operation, or Session).
Logout Type
Login/Logout Time
4 Select one of more search criteria by selecting a criteria value from the
drop-down lists, or by entering values into the search criteria fields.
5 Click Search.
6 To reset the search criteria, click Reset, then repeat steps 4 and 5.
Filtering System and System and Operation logs can be filtered by Log Level (1-6).
Operation Logs
To Filter the System and Operation Logs:
1 View the logs. Refer to Managing System Logs, Managing Operation Logs, or
Managing OMC Session Logs.
2 Select the Log Management menu, then select the Log Filter menu item, or
select the Log Filter icon under the menu bar.
The Set Log Filter Policy window appears. Figure 14 shows an example of the Log
Filter window.
3 Select a log level from 1 to 6 from the drop-down menu in the System Log / Log
Level field.
4 Select a log level from 1 to 6 from the drop-down menu in the Operation Log /
Log Level field.
Logs with a level greater than, or equal to, the selected level will be displayed
from now on during this user session.
5 Click OK.
Backing up the Logs The logs can be exported to a .csv or .xml file as a backup. You can also print
the logs by selecting Print from the File menu.
This chapter describes all of the procedures available to the user. The actual
operating procedures that a user has access to depends on their assigned role
and associated privileges. Refer to Chapter 6, OMC User and Security
Management for information on roles and privileges.
Network Element Alarms The OMC Console allows the operator to monitor faults reported by NEs and
Management managed objects in near real time. The OMC Console dynamically updates the list
of alarms in the Active Alarms Display, which includes essential information such
as network element identifier (ID), the alarm severity, time of occurrence, alarm
description, probable cause, and acknowledged state.
Alarm Categories The alarms are categorized into levels, with pre-defined colored icons for each
level.
service-affecting fault. For example, a minor alarm is reported when the detected
alarm condition is not currently degrading the capacity of the managed object.
No service degradation has yet been detected, but if the situation persists, it will
cause a degradation in service.
Once the operator acknowledges an alarm, the alarm's icon changes to indicate
that the alarm has been acknowledged. The alarm is updated with the operator's
user name, and the time of acknowledgement.
Active Alarms The Active Alarms section of the Active Alarms Display contains a list and general
information for all current alarms. Table 10 describes the alarm detail fields.
Field Description
Managed Object Class Represents the equipment that the alarm is raised on.
Managed Object Instance Specific managed object that the fault has occurred on.
Notification ID Unique alarm identifier of the NE sending the alarm.
Severity Critical, Major, Minor, Warning, or Indeterminate.
Probable Cause Probable cause.
Time Time alarm was raised.
Event Type Alarm category.
Alarm Details The Alarm Details section of the Active Alarms Display contains information
about a selected alarm. This information is for viewing only and cannot be edited.
Table 11 describes the alarm detail fields. By default, the Alarm Details section is
visible. However, you can hide the Alarm Details section by clicking the arrow
icon next to Alarm Details. Click the icon to display the details again.
Field Description
Notification ID Unique alarm identifier of the NE sending the alarm.
Field Description
Event type Category of alarm:
Communications alarm
Quality of service alarm
Processing error alarm
Equipment alarm
Environmental alarm
NE name Name of the NE sending the alarm.
Correlated notifications Alarm names that are related to this alarm. For
example, if this alarm clears a different alarm, then the
other alarm is a correlated alarm.
Specific problem Information on the probable cause of the alarm.
Threshold Applies only to threshold alarms. Threshold alarms are
those that are generated after an nth time, or when a
threshold is crossed.
Contains any of the following threshold parameters:
Triggered threshold - Identifier of the threshold
attribute that caused the alarm.
Threshold value - As a gauge or counter.
Observed value - Value of the gauge or counter that
crossed the threshold.
Arm time - time at which the threshold was reset.
Trend indication The current severity trend of the NE reporting the
alarm.
Proposed repair action Instructions for possible corrective action.
Additional text Alarm information sent from the network element
originating the alarm.
Acknowledged by Name of the user who acknowledged the alarm.
Host name Name of the host machine.
Acknowledged at Date and time the alarm was acknowledged.
Acknowledgement Text Explanatory text entered by the user when
acknowledging the alarm.
4 Click the Managed Object Class column header to sort the alarms.
5 Click any alarm in the list to display more information about the alarm including
any acknowledgment details and proposed repair action.
6 Use the scroll bars to locate all alarms raised on the target NE.
7 Review any unresolved alarms.
8 Report any new alarms (all severities) to Fault Management personnel for
resolution.
9 Keep the Active Alarms Display window open.
Clearing Alarms Alarms may be cleared by removing the condition that is causing the alarm or
manually clearing the alarm.
Viewing Recently Cleared Recently cleared alarms, as well as status messages, are displayed in the status
Alarms bar at the bottom of the OMC Console.
The status bar displays the most recently cleared alarm. To see a list of cleared
alarms (automatically cleared and manually cleared), then click the icon on the
right side of the status bar.
Displaying Related Alarms Alarms that are related are called correlated alarms. For example, if the
temperature critical alarm clears a second alarm (temperature too high) then the
second alarm is a correlated alarm.
The Correlated notifications field in the Alarms Details section contains the related
alarms for a selected alarm.
3 Browse the list of Active Alarms to find alarms with those Notification IDs.
Exporting the Active You can export the Active Alarms List to a file that can be viewed with a text
Alarms List editor. You can also export a detailed alarms list, which contains all the active
alarms plus the detailed alarm fields.
Setting Audible Alarms Audible alarms can be disabled for an OMC Console session. They are
automatically enabled when an OMC Console session is started.
Filtering Audible Alarms Alarms that produce an audible signal may be filtered by severity level. For
example, only critical alarms can produce an audible signal if desired.
Network Element The OMC Interface allows the user to monitor performance and statistics on the
Performance Statistics NEs.
The Core NEs: MSC, HLR, Access Server, and Signaling Server, display five
common sets of performance statistics on the OMC as follows:
CPU Utilization (%):
CPU user utilization
CPU system utilization
CPU IO utilization
CPU idle utilization
Memory Utilization (KB):
Total memory
Free memory
Swap Utilization (KB):
Total swap disk
Free swap disk
Disk I/O (%)
Network I/O (num of packages)
The BSC and BTS display one common set of performance statistics on the OMC:
Device Resources:
CPU Usage
Memory Usage
Each NE also displays NE-specific performance statistics on the OMC. Refer to the
appropriate NE Operations and Maintenance guide for a description of the
statistics specific to that NE. The LIS does not display any performance statistics
in this release.
For each set of performance statistics, the OMC provides 24-hour or 60-day
historic graphs from 5-minute to multi-day intervals, and hourly reports.
The user can also export performance statistics reports to a file from the OMC.
5 Using the tabs at the bottom of the performance screen, click each sub-type of
statistic to select or de-select the statistics displayed on the graph.
6 Select the report interval by clicking on the From: and To: filter tabs.
7 Click Fetch.
8 Export the report by selecting the File menu, and then Export to File. The Save
screen appears as shown in Figure 21.
Figure 21 Example of a Report Save Screen
9 Type the name of the file to save to in the File Name prompt area.
10 Click Save.
Viewing and Provisioning Database tables appear as software objects (represented by a folder icon) in the
Tables Using the OMC OMC Navigator window. Refer to Figure 22. This section describes how to view
and provision database tables.
Viewing Tables To view a table, right-click the folder icon that represents the table in the OMC
Navigator window.
Large tables (those with more than 500 records) will appear to be empty when
displayed, since it takes a long time to fetch all the records. Refer to Viewing
Large Tables for how to view the records in these tables.
The database table window contains three sections as shown in Figure 23:
An instance section that lists each row of data in the table.
A filter section that applies a filter to the instances (or table rows).
Add/Delete and Modify tabs that add, delete, or modify rows of data.
There are a number of common tasks for working with database tables regardless
of which node the database table applies to. These are:
Viewing tables
Sorting table rows
Using filters
Adding table rows
Sonata Core Voice NetworkRelease 4.5.3OMC User InterfaceGuide
Part Number D02112 Rev A1 | November 2008
64 Chapter 5: Provisioning Tables Using the OMC Console
The OMC displays the table rows in the Instances section of the window.
Viewing Large Tables Some tables have a large number of instances (rows) which causes the OMC to
take a long time to get the information from the NE. If the number of instances is
large, then the OMC displays an empty table with an extra filter tab, called Fetch
Instances. The maximum number of instances that can be displayed or fetched at
one time is defined at installation time. This is usually 500, or 1000 for the ISUP
/ Circuit table. The user fetches a subset of instances by specifying criteria
based on field values or ranges of values.
Specifying the criteria works in the same was as filtering instances. Refer to
Filtering Table Rows for how to specify the fetch criteria.
Sorting Table Rows A user can sort table rows (instances) by any field except the Status field.
Filtering Table Rows The filter section allows a user to filter table rows (instances) by field values.
For integer fields, a user can specify a particular integer value, or a range of
values. For example, for a range of 2 through 8 (including 2 and 8), specify 2..8
For a range x..y, this must be true: x <= y. A range of 8..2 would display an error
message when applying the filter.
For non-integer fields, use wildcards or a logical OR, as described in the following
table.
For non-integer fields, the filter is case-sensitive. For example, a filter of "TEST"
will not display values of "test"
To Apply a Filter:
1 Right-click the folder icon that represents the table in the OMC Navigator
window..
2 In the Filter section of the table window, enter the values or ranges of values for
the OMC to filter. For example, to view only those cp-ports that have a group
value of 16, enter 16 in the group field of the Filter section as shown in Figure 27.
3 Click Apply filter. The results are displayed in the Instances section as shown in
Figure 28.
Clearing a Filter
To clear a filter and display all the instances:
1 Click Clear filter
2 Click Apply filter
Modifying Table Rows Modify a row by changing field values, or use a filter and then apply changes to
all of the displayed rows.
If a field must have a unique value, an error message displays when trying to set
instances to have the same value.
Key fields cannot be modified. Key fields have a key icon next to their name as
shown in Figure 31.
Configuration changes to most fields in the database tables take effect as soon as
the change is applied (runtime configuration). Changes to some other fields
require that the node application be stopped and then restarted.
Fields that are grayed out on the OMC Console cannot be changed unless the
node application is stopped. Restart the application after making the database
change.
Database table fields that are configurable at runtime and those that require
restart can change based on upgrades and patches. Consult the Release Notes for
any changes to database tables as a result of patches or upgrades.
This chapter describes OMC user privileges and security policies that protect
network resources.
OMC Access Control Access control is a service feature used to permit or deny use of the components
Overview of a system. Access control defines or restricts the rights of individuals or
application programs to read or write data to or from the system. The goal is to
limit access to system resources only to authorized users, programs, processes, or
other systems.
Security Management Objects The Security Management system uses security objects to perform functions
such as monitoring user activities and restricting the range of IP addresses that
users can access.
For example, to create a user who can only view information on the HLR, create a
domain with only the HLR in it. Then create a role with read-only privileges on
the new HLR domain. Then create a user and assign the new user to the
read-only HLR role.
Managed Object Domain Under the Security menu in the OMC Navigator, use the OMC Managed Object
Management Domains (MO Domain) menu to add, modify, delete, and view MO Domains. The
domain creation process assigns network elements (NE) to an MO Domain.
The OMC has a default MO Domain, the Global Domain, which is created during
installation of the OMC Server. This domain includes all objects that the OMC
manages.
Roles and Users OMC User Management enables you to assign one or more roles to each user,.
The role determines the specific tasks that the user can perform.
User actions are logged in the Operation logs on the OMC. Refer to Managing
Operation Logs for information on user action logging.
User Role Management Table 14 describes User-Role-Management objects in the OMC interface.
Objects
Table 14 User Role Management Objects
User-Role-Management Object Description
Management privileges Defines user tasks that can be performed and assigned
as management privileges.
There are three types of privileges (refer to Privileges):
Admin
Operation
View
Management domain A group of subordinate system objects that fall within
a scope that OMC security manages.
Role A collection of management privileges and domains
that defines a users management scope within OMC.
The operations that users may perform are restricted
to their assigned management domains.
User The OMC operator's system account. The operator's
management privilege and management domain are
defined by their assigned role.
The system maintains all user information within the OMC interface. The OMC
administrator has authority over all functions.
Privileges
The Administrator role has the following privileges as well as all of the
Admin, Operator, and View privileges listed in Table 15:
Add/Delete NE
Add/Modify/Delete users
Add MO Domains
Add Roles
Add/Modify/Delete NE Groups
Change password for other users
Import/Export and Backup/Restore
Config/Control Data
There are three possible privilege levels on the OMC for new roles. These are
described in Table 15.
Table 15 Privilege Levels for Roles
The System Administrator can use the root account to add new users to the
Administrator role (with Admin privileges) and create new roles for users with
Admin, Operator, or View privileges.
a Click the key beside All Function Modules to expand the available privileges.
b Click the boxes beside either All Privileges, or click the box(es) beside Admin,
Operation, and/or View to select one or more of these privileges.
Note that selection of a higher privilege requires selection of the lower privileges.
I.e. If you select Admin, you must also select the Operation and View privileges.
10 Click OK.
11 Select a Session Timeout Duration (between 5 and 150 minutes) for the user's
session. By unchecking the Session Timeout Duration box, the user's session will
never timeout.
12 Check the box next to Restrict Duplicate User Sessions if desired.
13 Check the box next to User must change password at first logon if the user will
be required to select their own password.
14 Select an appropriate role in the Available Roles list and move it to the Assigned
Roles list. Repeat for all roles that this user should have.
15 Select the Access Type tab.
The window shown in Figure 35 appears.
Figure 35 Modify User Window - Access Type Tab
16 Select the access type from the drop-down menu in the Access Type field.
Access types include No Limit, IP Address, Access Time, or IP Address and Access
Time to limit the access that the user has to the system.
17 If IP Address or IP Address and Access Time was selected to restrict the user by IP
address, enter the IP address range or ranges in the Start IP Address and End IP
Address fields. Then click Add.
18 If Access Time or IP Address and Access Time was selected to restrict the user by
day and time of day, enter the day or days to allow access and the time range.
Then click Add.
19 Select the Contact Information tab.
Locking Users A user account can be locked to deny access temporarily, instead of having to
delete the user and then re-add the user later.
The State displayed for the User moves from Normal to Locked.
The State displayed for the User moves from Locked to Normal.
Displaying Current User The Security - Current User Information window displays the current user's
Information information, including user name, client IP address, login time, last access time,
session remaining time, and total session time. Idle sessions can be closed and
the maximum number of concurrent sessions can be set.
Archive Management Archive management adds the capability to view user or system logs from the
previous day, week, month.
Field Description
Archive Cycle Archive cycle is the
periodicity of the
execution of task. (ie daily,
weekly, monthly)
Start Moment When to start archiving
logs.
File Format XML or CSV.
Originator Username (automatic)
Originating Time Time (automatic)
File Directory Where to put the archived
logs.
The file directory must be manually cleaned up regularly to avoid filling up the
disk.
Appendix A Acronyms
ACRONYMS
A
Acronym Definition
BSC Base Station Controller
BSS Base Station Subsystem
BTS Base Transceiver Station
CDR Call Detail Record
CLI Command-Line Interface
CPU Central Processing Unit
ESD Electro-Static Discharge
HLR Home Location Register
IMG Intelligent Media Gateway
IN Intelligent Network
IP Internet Protocol
MGW Media Gateway
MRF Media Resource Function
MSC Mobile Switching Center
OMC Operation and Maintenance Center
PC Personal Computer
SGW Signaling Gateway
SNMP Simple Network Management Protocol
SS7 Signaling System Seven
SSVR Signaling Server
TCP Transmission Control Protocol or Test Coordination
Procedure
URL Uniform Resource Locator
XML Extensible Markup Language
operation 42
A I filter 46
access control icons manage 44
in OMC 71 network objects 35 search 45
Access Server 36 object status 37 session 43
alarms 20 software status 39 manage 44
acknowledged at 51 system status 37 search 45
acknowledged by 51 installing the OMC console for Solaris system 42
acknowledgement text 51 Java Web Start 28 filter 46
active alarms display 50, 52 installing the OMC console for Windows manage 43
additional text 51 before you begin 25 search 45
correlated notifications 51, 53 display resolution 26
critical 49 hosts file 26
host name 51 Java Web Start 27 P
indeterminate 50 temporary internet files 26 performance management 20
major 49 instances 36 performance statistics
minor 49 CPU utilization 55
NE name 51 disk I/O 56
notification ID 50 J memory utilization 56
proposed repair action 51 Java 20, 31 monitoring 56
specific problem 51 Java Web Start 27, 28 network I/O 56
threshold 51 swap utilization 56
trend indication 51 Provisioning Server 19, 35
warning 50 L
launch OMC console 31
Lawful Intercept Server 36 R
C roles
comprehensive management functions 20 admin 75
config.prop M creating 76
OMC user and group configuration 74 Media Resource Function 36 deleting 77
configuration memory utilization modifying 77
runtime configuration 69 performance statistics 56 operator 75
configuration file MO domain view 75
config.prop 74 creating 72 viewing 75
contacting definition 72 runtime configuration
technical documentation department 18 modifying 73 changes to database tables 69
CONX 36 viewing 72
CPU utilization Mobile Switching Center Server 35
performance statistics 55 Mobility Server 35 S
monitoring security management 20
performance statistics 56 Signaling and Media Gateways 35
D S-RAN 19, 35
disk I/O swap utilization
performance statistics 56 N performance statistics 56
network I/O
performance statistics 56
H T
Home Location Register 35 tables
hosts file O adding rows 67
modify 26 OMC logs applying filter 66
paths 26 backup 47 deleting rows 67
modifying rows 68
sorting rows 65
viewing 62
TCP port 20, 31
technical support
hours 17
website 17
Telsec 36
U
users
creating 78
current information 81
deleting 80
locking 80
modifying 80
roles 74
user roler management 74
viewing 77
W
warranty support 18
X
XML files 31