SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

download SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

of 5

Transcript of SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

  • 8/20/2019 SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

    1/9

    Confidential & Proprietary 1/9

    SOL iD OM C V.1.5

    SOLiD OMCV1.5

    SOLiD Technologies, Inc.

  • 8/20/2019 SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

    2/9

    Confidential & Proprietary 2/9

    SOL iD OM C V.1.5

    Contents

    1. INTRODUCTION .......................................................................................................................... 3

    2. OPERATION MODES .................................................................................................................. 4

    2.1 SMS M ODE ........................................................................................................................................................ 5

    2.2 SNMP M ODE ..................................................................................................................................................... 5

    3. SERVER FUNCTION .................................................................................................................... 5

    3.1 OMC SERVER INFORMATION ........................................................................................................................... 6

    3.2 C LIENT C ONNECTION ......................................................................................................................................... 6

    3.3 M ODEM C ONNECTION ...................................................................................................................................... 7

    3.4 D ATABASE M ANAGEMENT ................................................................................................................................. 7

    4. CLIENT FUNCTION ..................................................................................................................... 7

    4.1 U SER A UTHENTICATION ..................................................................................................................................... 8

    4.2 R EPEATER S TATUS R EPORT ................................................................................................................................ 8

    4.3 A LARM LEVEL M ANAGEMENT .......................................................................................................................... 9

    4.4 R EPEATER M ANAGEMENT .................................................................................................................................. 9

    5. TROUBLE TICKETS ...................................................................................................................... 9

  • 8/20/2019 SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

    3/9

    Confidential & Proprietary 3/9

    SOL iD OM C V.1.5

    1. Introduction

    OMC (Operating & Maintenance Center) is a system to manage, control and monitor repeaterslocated at remote sites. It provides a real- time alarm of the repeater’s problems and/or errors

    through wireless or wired network. Typical configuration of OMC system is shown in Figure 1

    where wireless modem is used for connecting OMC system and repeaters.

    Figure 1 . OMC system configuration

    The OMC consists of Server and Client modules as described in Figure 1 and Figure 2.

    The OMC Server receives data from the repeater either regularly or occasionally through SMS

    or PPP and then stores it at a database after allocating it per category. It also transmits data to

    the client upon the client’s request.

    At the request of the service operator, the OMC Server can be connected with the Operator’s

    NMS server using SNMP.

    Based on the amount of repeaters in operation, the OMC Server can have up to 8 modems for

    load balancing function and it can be connected with up to 10 Clients managed at a central or

    regional level.

  • 8/20/2019 SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

    4/9

    Confidential & Proprietary 4/9

    SOL iD OM C V.1.5

    Figure 2 . OMC Server-Client configuration

    Communication between OMC Server and Client is described in Figure 2. Server and Client

    communicate via TCP/IP and the Database uses MS-SQL. TNMS is a proprietary module used

    to manage TProtocol designed by SOLiD.

    OMC server and client have following hardware and software requirements.

    Server

    H/W

    Intel Xeon Quad Core 2.0GHz or better

    Memory :2 GB or greater

    HDD : 250 GB or bigger

    S/WMS Windows Server 2008

    MS-SQL Server 2005

    Client

    H/WIntel Core 2 Duo 2.0 GHz or better

    Memory : 2 GB or greater

    S/W MS Windows XP Professional or newerMicrosoft Office Excel

    2. Operation Modes

    There are two operation modes of SMS and SNMP. The default mode is SMS which have clear

    advantages over SNMP in that no wired network set-up is required by leveraging wireless

    modem connection and it can be used regardless of repeater locations.

    Physical Layer

    TCP / IP

    MSSQL

    TNMS

    OMC Server

    Physical Layer

    TCP / IP

    MSSQL

    TNMS

    OMC Client

  • 8/20/2019 SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

    5/9

    Confidential & Proprietary 5/9

    SOL iD OM C V.1.5

    2.1 SMS Mode

    This mode is the simplest and the ideal solution for the remote sites where there is no wiredconnection to the repeaters. It utilizes wireless modems to have connection between OMC

    server and repeaters.

    It also has high data reliability by combining PPP together with SMS and has remote download

    capabilities.

    Figure 3 . SMS (+ PPP) Mode

    2.2 SNMP Mode

    SNMP is the most common management protocol used in data networks. It assumes always-

    on IP network connectivity that makes it fit to the network where wired IP network can be used

    as communication path between OMC and repeaters. Typical applications for SNMP may

    include in-building and urban area.

    SNMP features high data transfer reliability, real-time monitoring and control and no restrictions

    for repeater installation. The typical disadvantage of this mode is that it may accompany

    additional costs to run SNMP client on the repeaters. Usually it requires more processing

    hardware and OS installation.

    SNMP is provided based on customer needs.

    3. Server FunctionFigure 4 below shows typical window snapshot for OMS server.

  • 8/20/2019 SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

    6/9

    Confidential & Proprietary 6/9

    SOL iD OM C V.1.5

    Figure 4. OMC Server – System Information Window

    3.1 OMC server Information

    You can check OMC Server capacity, CPU and main memory usage history and [System],

    [Database], [Backup] hard disk usage. Additionally, it provides OMC Server O/S version, IP

    address, hostname, database connectivity, number of connected clients, FTP server status,

    number of connected FTP clients and registered modem connection status.

    Furthermore, OMC Server log-in time, DB server connected time, Client log on/off time,

    database server sign-in users and repeater status reports are stored to allow the user to define

    and examine problems.

    3.2 Client Connection

    A single server can link up to 10 clients allowing regional management. Repeater status and

    alarms will be reported in real time from the server to each client.

    1

    2

    3

    45

  • 8/20/2019 SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

    7/9

    Confidential & Proprietary 7/9

    SOL iD OM C V.1.5

    Additionally, client ’ s IP address, hostname, user ID, connected time and other relevant data

    are easily manageable while preventing any problems.

    3.3 Modem Connection

    A single server can connect up to 8 modems. After registering the details with assigning the

    communication port and telephone number, modems can be managed.

    3.4 Database Management

    Data sizes and save sequences for all alarms & events can be configured.

    4. Client FunctionFigure 5 below shows typical window snapshot for OMS client.

  • 8/20/2019 SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

    8/9

    Confidential & Proprietary 8/9

    SOL iD OM C V.1.5

    Figure 5. OMC Clients – Main Window

    4.1 User Authentication

    User authentication requires an IP address, user ID and password to log on. There are 5

    different user levels: root manager, central manager, central user, local manager and local user.

    Root Manager: Controls and manages all levels & features.

    Central Manager: Controls and manages entire departments, databases and repeaters.

    Central User: Controls and manages entire departments and repeaters

    Local Manager: Controls and manages assigned local departments, databases and

    repeaters.

    Local User: Controls and manages assigned local departments and repeaters.

    4.2 Repeater Status Report

    You can manage each repeater and report its status by type. Reports can be converted to MS

    Excel format.

    1

    2

    3

    4

    5

    6

    7

    8

  • 8/20/2019 SOLiD SOLiD OMC White Paper_v1.5OMC White Paper_v1.5

    9/9

    Confidential & Proprietary 9/9

    SOL iD OM C V.1.5

    4.3 Alarm Level Management

    The root manager can change alarm levels by repeater type. Alarm levels are critical, major,minor and ignore.

    4.4 Repeater Management

    Repeaters can be controlled by alarm masks, client status or control window. Repeaters can

    be added, deleted or changed using the repeater management window and by saving the

    default values, repeaters can be easily re-installed.

    System lock function will prevent non-authorized users from accessing the system.

    5. Trouble Tickets

    If a repeater alarm occurs, an SMS will be sent to a registered telephone number of assigned

    person with the following messages.

    (Alarm)-> [repeater Name]-Alarm has been generated

    (Restart)-> [repeater Name]-Restarted

    (Communication Fail)-> [repeater Name]-Communication Fail