NSP Centralized Configuration Manager Release 1.0 Date issued January 2008 Document reference & release version TR-IAS Ed 1.0 These presentation materials describe Tekelec's present plans to develop and make available to its customers certain products, features and functionality. Tekelec is only obligated to provide those deliverables specifically included in a written agreement signed by Tekelec and customer. Training documentation Notes 1

Centralized Configuration Manager Training Manual This Training Manual is in accordance with IAS system Issued January Copyright © 2008 TEKELEC France. All rights reserved In accordance with its policy of constant product improvement, TEKELEC France reserves the right to change the information in this manual without notice. No part of this manual may be photocopied or reproduced in any form without the prior written permission of TEKELEC France. Software license notice Your license agreement with TEKELEC France specifies the permitted and prohibited uses of the product. Any unauthorized duplication or use of IAS system, in whole or in part, in print or in any other storage and retrieval system, is prohibited. Trademarks All product names mentioned are trademarks of their respective owners. In USIn France 5200 Paramount ParkwayParc de la Mer Rouge Morrisville, NC E rue Salomon Grumbach (USA) Mulhouse Cedex (France) Tel: Tel: Training documentation ‘07 | 2 Notes 2

Class outline  This class is intended to provide you with an full introduction to the Centralized Configuration Manager as well as an understanding of its basic concepts and operations.  Class Outline includes the following sections: - About the Class Lesson Objectives - Introducing Centralized Configuration Manager (CCM) Aim of the Centralized Configuration Manager - Centralized Configuration Manager Concepts IAS System architecture Key Concepts CCM Navigation  Network elements  Network views Sessions introduction Network views link based Network views session based  IAS system elements - Perspectives details - Lesson review Training documentation ‘07 | 3 Notes 3

About the class After this class you will : Have a global view of the Centralized Configuration Manager (CCM) architecture Know the main principles of the CCM Know the equipments compliant with CCM (inter-platform operability) Training documentation ‘07 | 4 Notes 4

Introducing Centralized Configuration Manager Training documentation ‘07 | 5 Notes 5

Aim of the Centralized Configuration Manager Centralized Configuration Central database with all configuration information Can be shared with all the applications Permits to avoid duplication Centralized Configuration Manager (CCM) Web based interface integrated in NSP for IAS administration Integrated in NSP 3.0 Replace System Management for Next Generation platform only An internal System Management for legacy platform configuration is integrated into the CCM Manage IAS as a single entity Training documentation ‘07 | 6 Notes Note : - Legacy equipment (like MSW, ICP, DS…) continues to be administered via a System Management (SM) included in the CCM - Next generation platforms like IXP can interact with legacy equipment like MSW, but with some limitations (see version compatibility) - Next Generation platforms are : IMF3.0, PMF2.2, IXP2.0 and the future releases. 6

Aim of the Centralized Configuration Manager Centralized Configuration Manager (CCM) : Has the capability to connect to the legacy equipment and collect information for a display and use into the NSP The collected information related to the legacy platform are used by other NSP applications like : xDR Browser, ProAlarm, ProPerf… Training documentation ‘07 | 7 Notes Platform CCM Compatibility : Next Generation and Legacy platform IMF 3.0/PMF 2.1 are fully compatible. The IMF/PMF application can be discovered and configured by CCM. IXP 2.0 : the IXP application and the xDR sessions are configured using the SM that is a part of the NSP system and can be discovered and displayed by CCM application. IXP 2.0 will be supported in future releases of CCM. The current release includes, a version of SM is embedded with NSP that supports full configuration of the IXP. IMF 2.2 or prior, PMF 2.0 or prior, MSW 10.0 or prior: the XMF or MSW applications and the network elements are configured using the existing Windows based SMsupplied as a part of the system and can be discovered by CCM. Legacy ICP 5 or prior : The ICP application is configured using the Windows based SM supplied with the system and can be discovered by CCM. Data Server 3.2 or prior : The DS application and the xDR sessions are configured using the existing SM supplied as a part of the system and can be discovered by CCM. DWH : All the existing legacy applications continue to support DWH. NextGen applications will use IXP. 7

Centralized Configuration Manager Concepts Training documentation ‘07 | 8 Notes 8

IAS System Architecture Legacy & Next Generation platforms Training documentation ‘07 | 9 Notes 9

Key concepts Central Configuration Manager (CCM) IAS system configuration can be divided into 2 categories : Data Acquisition and Processing  Probes configuration  Routing of the PDUs to the xDR builders  Set up of the xDR builders  KPI generation  (….) IAS System Administration  Configuration of the sites  Configuration of the IAS servers (hosts)  Set up of security and permissions  (….) Training documentation ‘07 | 10 Notes 10

CCM Navigation Based on 4 types of Perspectives Network Elements Network Views IAS Elements or xDR Related Elements Training documentation ‘07 | 11 Notes 11

CCM Navigation Network Elements Represent the monitored network Based on a Node hierarchy Represent any network equipment Can have several Signaling Points  SS7 Can have several IP addresses  IP A node contains Linkset, Gb Links or IP Stream Each linkset will appear twice 1 time under its LSP et 1 time under its OSP Linksets contain Links All the elements are automatically discovered for an IMF and have to be created manually for a PMF For PMF the links have to be correlated to an interface and a timeslot in the IAS Elements level Training documentation ‘07 | 12 Notes LSP : Local Signaling Point OSP: Opposite Signaling Point 12

CCM Navigation Network Views Represent a logical view of the system Can either be Session based or Link based Can be grouped in different levels Integrate the MSR (multi session request) For legacy platform compatibility A Session is a group of data of same nature xDR session : contains xDR of same nature, for example ISUP, GPRS Gn, … Session type : capture, reconstitution and statistic Multi-session : Can group several sessions of same nature Dictionaries : Each protocol needs an associated dictionary in order to define each field of the xDRs Protocols : Possibility to display in NSP all the protocols monitored with the current configuration Stacks : A stack is a set of protocol. There are 3 main kinds of stacks : ETSI, ANSI, CHINA Training documentation ‘07 | 13 Notes MSRs appear into the sessions list into xDR Browser and can be launched directly from xDR Browser. 13

CCM Navigation Network Views : Link based Permits to group links in a logical order Per Protocol (ISUP, INAP, …) Per type of traffic (Roaming, Carrier, Corporate, …) … Is necessary to define the Data Flows in the IAS Elements Replace the Linksets lists of System Management (for IMF 2.0 and MSW) Network Views : Session based Permits to create logical views per session (MSR like) Per site - Business Unit Per customer Per operator … Used as Input by the Next Generation application Only ProTrace V4 at the moment Training documentation ‘07 | 14 Notes 14

CCM Navigation IAS System Elements Represent the physical layer of the system Manage the equipments under a Site hierarchy Site can be physical (geographical) or logical A site contains Host (Servers) Sub-Systems (IMF,PMF, IXP) Under each Host or Sub-System there is an Application Permit to discover the session on IXP/DS or the Eagle elements (PC, Linkset, …) Provide the configuration functions for next generation IMF and PMF (Data Flow, Filters, …) Training documentation ‘07 | 15 Notes 15

Perspectives in details Training documentation ‘07 | 16 Notes 16

Perspectives in details Monitored network elements Network elements can be : Nodes : Element of the customer network (SSP like SGSN) Signaling Points (SS7 point code or IP address) Linksets (group of SS7 links only) Links (SS7 link or Gb link (GPRS)) Network elements need to be declared in the CCM because number of applications will use them Network elements are added to the centralized database by making : For legacy platform : A synchronization with the data collectors (IMF,PMF or MSW), declared in a Host and we talk about the Managed Objects For Next generation platform : A manual creation of each individual network elements is needed for NG PMF2.2 Training documentation ‘07 | 17 Notes 17

Perspectives in details Network views Network views are describing a logical group of elements in an IAS system 2 types of network views : Session based network views  xDR sessions can be grouped to create a view of the network Link based network views  Links (SS7, Gb, IP) can be grouped to create a view of the network  Are used to associate linksets, links and IP streams to Dataflows Network views are designed to be the primary mechanism to select data set in the IAS system Next-Gen applications like ProTrace and ProDiag use network views Training documentation ‘07 | 18 Notes 18

Perspectives in details IAS system elements The IAS platform is composed of many various applications that need to be configured to perform their functions Legacy platform are still configured using the System Management (SM) Next generation platform (IMF, PMF and IXP) are configured using the Centralized Configuration Manager (CCM) In the CCM, some principle elements need to be declared in order to configure the servers Sites Hosts Applications (MSW, ICP, DS) Subsystems (IMF, PMF, IXP) Global Data & Parameters Training documentation ‘07 | 19 Notes 19

Perspectives in details IAS system elements : “Sites” and “Hosts” declaration A site represent a logical location where IAS applications are located An IAS application can run on :  a single server  a group of servers is considered as a subsystem Using the CCM, you define the multiple sites: Each declared site can have only one type of subsystem (like IMF, IXP…) For this reason, a physical location where several subsystem of same type are installed, needs several sites to be created If the site contains an IMF subsystem, it can only monitor one EAGLE STP A Host refers to a server on which runs an IAS application Using the CCM, you define the multiple hosts: Create a host for each IAS server (assign an administration IP address to it) One site can contain multiple hosts Training documentation ‘07 | 20 Notes Sites Sites represent logical locations where an IAS application is located. An IAS application either runs on a single server or it may be distributed over a group of servers (referred to as a subsystem). Using CCM, you define the sites. When you create a site, follow these two rules: There can be at most one of each type of subsystem for a given site. For example, you can have one IMF subsystem and one IXP subsystem in a site, but you cannot have one IMF subsystem and two IXP subsystems in the same site. For this reason, a physical location where IAS equipment runs needs to be represented in CCM by multiple sites. If the site contains an IMF subsystem, it can only monitor one Eagle STP. Hosts A host refers to a server that runs an IAS application. For each IAS server in a site, the user creates a host in CCM. Therefore, one site can contain multiple hosts 20

Perspectives in details IAS system elements : “Applications” declaration An application refers to an IAS software running on a host The application can be “discovered” after the host has been created in the CCM The “discover” initiate a communication with the server to load the information from the host Then the information loaded are stored into the centralized database Training documentation ‘07 | 21 Notes Applications An application refers to an IAS software component running on a host. Examples of applications include ICP, Data Server, MSW, IMF, PMF, etc. The IAS platform includes management agents that enable CCM to discover the application. After the host is added, you can issue the command to discover the applications running on the host. At that time the CCM communicates with the server to gather the application information from the host and store it in the centralized database. You must provide an administration IP address for the host when you are creating the host. This is the address that the management agent running on the host listens to. In order for application discovery to succeed, you must enter the correct management address as the administration IP address of this host. 21

Perspectives in details Applications are all the softwares manageable by NSP DataServers : Proprietary database containing sessions (reconstitution,capture,statistics) DataWareHouses : Oracle Database containing sessions (reconstitution,capture,statistics) MSWs : Timestamp the MSUs and group them by protocol. Send some network and system alarms to NSP Proalarm IMFs : Timestamp the MSUs and group them by protocol. Send some network and system alarms to NSP Proalarm ICPs : Create the xDRs with the MSUs by protocol. Send some system alarms to NSP Proalarm Training documentation ‘07 | 22 Notes 22

Perspectives in details Applications are all the softwares manageable by NSP PMFs : Timestamp the MSUs and group them by protocol. Send some network and system alarms to NSP Proalarm IXPs : Create the xDRs with the MSUs by protocol, store xDRs/MSUs into sessions on an Oracle Database. Send alarms to ProAlarm NSP All applications : Display all the previous applications together Training documentation ‘07 | 23 Notes 23

Perspectives in details IAS system elements : “Subsystems” declaration 2 type of IAS applications are existing : Stand alone application that are running on only 1 server (ICP, DS) Clustered application that are running on several server (IMF, PMF,IXP) Anyway, they behave as a single entity The possible applications that runs as subsystem are : XMF Next Gen (IMF or PMF) XMF Legacy (IMF or PMF) IXP Next Gen or Legacy DataWareHouse (DWH) Training documentation ‘07 | 24 Notes 24

Perspectives in details IAS system elements : “Subsystems” declaration Primary, backup and ancillary instances Application that runs as subsystem have an instance running on it  An instance running as primary on the primary server  A back up or ancillary instance on the other servers Discovery of the various application When discovering the first application belonging to the subsystem, that application is designated as primary When discovering other applications belonging to the same subsystem, these applications are designated as ancillary or back up CCM gives the possibility to switch the roles of the server only if :  Applications have been discovered in the wrong order  The primary server is down and the backup server needs to be switched as primary Training documentation ‘07 | 25 Notes 25

Lesson Review Q - What is a session ? Q - What is an application ? Q - What is a site? And what is a host ? Q - Can we have several applications running on a single host ? Q - Why must MSW be defined in the NSP Platform ? Q - What are stacks ? Q - What are dictionaries ? Training documentation ‘07 | 26 Notes 26