Pre Sales Communications

Table of contents 1. INTRODUCTION AND OBJECTIVE... 4 2. FOREWORD... 4 3. THE SOLUTIONS... 4 3.1. ACTIVE REDUNDANCY... 4 3.1.1. Operating principle... 6 3.1.1.1. Switchover to the backup server... 6 3.1.1.2. Return to the main server... 6 3.1.2. Advantages and disadvantages... 7 3.1.2.1. Advantages... 7 3.1.2.2. Disadvantages... 7 3.2. PASSIVE REDUNDANCY... 8 3.2.1. Operating principle... 10 3.2.1.1. Backup... 10 3.2.1.2. Switchover to the redundant server... 10 3.2.1.2.1. Backup mode switchover... 10 3.2.1.2.2. On demand switchover... 10 3.2.2. Advantages and disadvantages... 11 3.2.2.1. Advantages... 11 3.2.2.2. Disadvantages... 11 4. CHOOSING A SOLUTION... 12 4.1. THE TYPES OF PCX TO MANAGE... 12 4.2. THE SWITCHOVER MODE... 12 4.3. THE CHOICE OF MODULES TO PROTECT... 12 5. ORDERING PROCEDURE... 14 5.1. PASSIVE REDUNDANCY... 14 5.2. ACTIVE REDUNDANCY... 14 END OF DOCUMENT... 14 ESD / Pre Sales / JMB 2/14 October 2009 Ed04

DOCUMENT UPDATE ED2: Separate Accounting and Directory modules (page 5) ED3: Directory replication replaced by LDIFF file transfert. Due to that, back to common server for Accounting and Directory. 4200 Office is not any more managed. ED4: Directory replication available from R5.1 ESD / Pre Sales / JMB 3/14 October 2009 Ed04

1. Introduction and Objective Reliability, effectiveness, and management continuity are important factors in a communications server solution. A redundant server solution not only offers a means of continuous OmniPCX management when an OmniVista 4760 or its link is deactivated, it also provides the means to maintain the information in the server. In this document, the goal of ensuring a level of protection in order to guarantee management continuity is addressed by reviewing the factors involved and by describing the process of constructing a redundant OmniVista 4760 server solution. 2. Foreword Before deciding on a protection solution for the OmniVista 4760, it is necessary to have the following information: The DATA environment in which the 4760 server is located The PCX that must be managed The level of protection required by the customer for each module present in the 4760 server This information makes it possible to design and implement the solution that corresponds most closely to the customer's requirements. The remainder of this document describes in detail the protection solutions, the choice of the most appropriate customer solution, and the process to follow in order to provide it. 3. The solutions In an environment where it is necessary to manage more than 5,000 subscribers, the 4760 server implementation includes a RAID 5 disk protection system. In addition to this system, two other protection solutions can be proposed: Active redundancy Passive redundancy Each solution described below is based on server duplication. 3.1. Active redundancy This solution consists of running the two 4760 servers in parallel. Each server is associated with a reference PCX 1. In this arrangement, each server retrieves the information originating from the PCXs. This acquisition mode cannot be used for OmniPCX Office; this is because at present, they can only be administered via a single OmniVista 4760. 1 Only one 4760 server can be declared in the ACTIS sheet for an OmniPCX Enterprise or 4400. ESD / Pre Sales / JMB 4/14 October 2009 Ed04

In normal operating mode, except for PCX creation and the modification of their IP addresses, administration is performed on one of the 4760 servers. This server will be called the main server. The second server is called the backup server, because the master/slave approach is necessary to update directory administrative data between the 4760 servers. The administrative data from the Enterprises directory is entered on the main server. Using the replication between directories 2 mode, the main server will update the administrative data on the backup server. The replication is available from OmniVista 4760 R5.1 only. To avoid regenerating report definitions on the backup server and the main server, the 4760 servers are able to store report definitions on a remote server (belonging to the customer). If the reports are not be stored; they will have to be generated again. Actions to perform on both 4760 servers: Addition of a PCX or modification of a node IP address. All the configuration actions of the 4760 server itself: Creation, modification, deletion of metering/tracking parameters, profile management, alarms re-routing, code book export, partial backup/restore of the metering/tracking database, etc. Whether this solution is implemented or not, it is possible to perform the backup/restore functions on each 4760 server. OmniVista 4760 «Main» server Enterprise directory OmniVista 4760 «Backup» sever Enterprise directory Update Synchronization Alarms Reports from the different modules Remote server OmniPCX Enterprise OmniPCX 4400 Functional diagram illustrating active redundancy 2 Copies the directory entries from a master server to a slave server. In the slave server, access to the entries is read-only (marked as belonging to the master server). ESD / Pre Sales / JMB 5/14 October 2009 Ed04

3.1.1. Operating principle Each night, both 4760 servers synchronize with the PCXs (retrieval of metering/tracking tickets and traffic observation counters). On each server, retrieval of each PCX object model makes it possible to automatically update: The Enterprise directory (last name, first name, cost center). The topology (networks, sub-networks, nodes, shelves, boards). The metering/tracking data (cost center, sets, attendants, trunk groups). At regular intervals (e.g. once every half-day), the main server updates the directory to the backup server. To prevent the creation of duplicated reports, the new 3 report definitions are exported to the remote server. The alarms are received in real time on both 4760s via the permanent IP link or RMA (from R2.0). 3.1.1.1. Switchover to the backup server When the main server is deactivated, the manager connects to the backup server via its 4760 client (by changing the URL or the server address), and the backup server becomes operational for each module. However, for the Directory module, only consultation 4 actions will be possible during deactivation of the main server. The new report definitions generated during this time must be exported to the remote server. Any configuration actions on the backup server must be carefully noted so that they can be repeated as soon as possible on the main server. 3.1.1.2. Return to the main server When the main server is reactivated, the data from the OmniPCX Enterprises will automatically be retrieved by an automatic synchronization. This data will be retrieved provided the server is activated during the conservation period 5 for the metering/tracking tickets and the traffic observation counters in the OmniPCX Enterprise systems. The new report definitions generated on the backup server will be retrieved on the remote server. If configuration actions have been performed on the backup server, they must be repeated on the main server. 3 This does not apply to predefined reports. 4 The URL address for consultation of the Enterprise directory must be modified manually on each 4059 attendant PC. 5 This period can be defined in the PCX (maximum 30 days). ESD / Pre Sales / JMB 6/14 October 2009 Ed04

3.1.2. Advantages and disadvantages 3.1.2.1. Advantages OmniPCX Enterprise data is always up-to-date on both servers. When the main server is reactivated, the update of PCX data is performed automatically via the daily synchronization. It is easy to switch over from the main server to the backup server and vice versa. The active redundancy solution makes it possible to adapt redundancy only for the modules that the customer wishes to protect (e.g. only protect the accounting module of a main server configured as Start Pack). 3.1.2.2. Disadvantages Requires duplication of the OmniVista 4760 licenses (see chapter 5.2, discount request). Duplicated input of configuration actions on the 4760 server. OmniPCX Office is not covered by this solution. ESD / Pre Sales / JMB 7/14 October 2009 Ed04

3.2. Passive redundancy This solution consists in providing a clone of the initial server. All the installation parameters are identical: IP address, Domain name, PC name, backup directory. All the OmniVista 4760 information is regularly saved on a server belonging to the customer. When one server replaces another, the database is restored from the customer server which contains the backup. For protection, the new report definitions (alarms, metering/tracking, traffic observation) will also be saved on the customer server. The concept of an active server and a redundant server depends solely on whether or not it is present in the customer's IP network. When the redundant server is activated (put in place in the IP network), it becomes the active server, and once the problem has been solved in the original active server, will become the redundant server once again. In order to keep and control the licenses, the servers must be swapped every 20 days. OmniVista 4760 «Active» server OmniVista 4760 «Redundant» server 1 Replacement of the server 2 Restoration 3 Synchronization Backup 4760 database Definition of reports OmniPCX Office OmniPCX Enterprise Archiving of the tickets (if OXO et 4200) Backup server Functional diagram of passive redundancy The OmniVista 4760 application is installed in the redundant server, but this server is not operational. Updates between the active server and the redundant server will be performed when necessary by backup and restore of the 4760 database. Backup of the database concerns: The Directory databases (system and enterprise) The Alarms and Metering/Tracking databases. The Metering database contains the metering tickets (call detail records), and the counters for traffic observation and Voice over IP ESD / Pre Sales / JMB 8/14 October 2009 Ed04

All the reports for alarms, metering/tracking, traffic observation and Voice over IP The object models (MIB) for the PCXs The 4760 server administration files (including the license file). When the redundant server is activated, any difference between the active server' database, when deactivated and the content of the last backup will be lost, in particular: The new administrative data in the Enterprise Directory The entries created manually meanwhile in the Enterprise Directory The new report definitions that have not been saved (alarms, metering, traffic observation) The new reports generated Modifications and creations in administration of the server, etc. The OmniPCX Enterprise data will be updated by an action called Global Synchronization. 6 This action makes it possible to retrieve the differences between the tickets, the traffic observation counters and Voice over IP counters and subscriber actions (creation, modification, deletion). NB: If the OmniVista 4760 must perform accounting for OmniPCX Office, ticket archiving 7 must be performed 8. 6 Must be done for all the OmniPCX Enterprise or 4400 systems on all the networks managed via OmniVista 4760. 7 Modification of the archive period to be modified (the previous day); this needs to be taken into account when recalculating the cost. 8 Archiving can be done manually or scheduled for automatic operation. ESD / Pre Sales / JMB 9/14 October 2009 Ed04

3.2.1. Operating principle 3.2.1.1. Backup At regular programmable intervals, a 4760 database backup 9 and tickets archiving 10 are performed from the active server to the backup server. At the end of each backup, a result file (.log) is generated, 11 making it possible to see whether the backup has been successful. NB: To allow swapping, the backup will be carried out every 20 days. 3.2.1.2. Switchover to the redundant server This switchover is performed when one of two types of events take place: A crash or a problem on the active server: This type of switchover will be called a Backup mode switchover. Cyclical swapping of the servers: This type of switchover will be called an On demand switchover. 3.2.1.2.1. Backup mode switchover When necessary, the active server is disconnected from the IP network, and the redundant server is activated (connected to IP). The backup is downloaded 12 onto the redundant server by means of a manual command. When the download has finished, total synchronization of all the OmniPCX Enterprises must be activated manually. If the server is managing OmniPCX Offices, the restoration of the metering tickets from these PCXs must be carried out for the period between the date of the last backup and the current date. Tickets retrieved by the previously active server but not archived will be lost. Once all the operations described above have been performed, the redundant server becomes operational (active). 3.2.1.2.2. On demand switchover This type of switchover must be performed every 20 days. Before disconnecting the active server, the manager performs a backup of the database. Once this has been done, the active server is disconnected from the IP network, and the redundant server is activated (connected to IP). 9 During the backup, the 4760 server is no longer operational. 10 If the 4760 is managing or metering of the OmniPCX Offices, the archiving must be performed every day. 11 The average duration of a backup is approximately 50 minutes. 12 The duration of downloading is equivalent to the duration of backup, i.e. approximately 50 minutes. During loading, the server is not operational. ESD / Pre Sales / JMB 10/14 October 2009 Ed04

The backup is downloaded13 onto the redundant server by means of a manual command. After this operation, the redundant server becomes operational (active). An immediate backup and download make it possible to maintain all the data. 3.2.2. Advantages and disadvantages 3.2.2.1. Advantages The OmniVista 4760 licenses are re-used on the redundant server. Both servers can become the active server or redundant server in turn (no concept of main server). No need to repeat input of 4760 database parameters. 3.2.2.2. Disadvantages This solution requires rigorous planning of backups and manual actions to make the redundant server operational. Requires switchover of the 4760 servers at regular intervals. Requires the use of one of the customer's servers as a backup server. Due to the identical IP address, both servers must be placed in a network environment that allows this type of addressing. For the OmniPCX Office, metering tickets for the period between the start of the day and the time when the active server is deactivated are lost. 14 13 The duration of downloading is equivalent to the duration of backup, i.e. approximately 50 minutes. During loading, the server is not operational. 14 Only on the day the active 4760 server is deactivated. ESD / Pre Sales / JMB 11/14 October 2009 Ed04

4. Choosing a Solution The choice is determined by several criteria. In order of importance, these criteria are: The types of PCX to manage The switchover mode The choice of modules to protect This method applies to a single-server 4760. If for reasons of capacity (number of subscribers >30,000), the 4760 architecture require a multi-server type of architecture, and these solutions apply to each server. 4.1. The types of PCX to manage This is often decisive for choosing the solution. If the server has to administer OmniPCX Offices, only the passive redundancy solution can be proposed. In the case of OmniPCX Enterprises, the choice of solution will be determined by the protection mode. When the 4760 server is managing a single OmniPCX Enterprise, only passive redundancy can be proposed, because two 4760 servers cannot be ordered for the same OmniPCX 4400/Enterprise. 4.2. The switchover mode If the type of PCX does not make it obligatory to choose passive redundancy, or if the geographical location of the redundant server makes it impossible to have the same IP address, the switchover mode becomes the decisive criterion when choosing the solution. As seen in the description of the redundancy solutions, passive redundancy requires manual actions, and does not allow immediate switchover to an operational mode. Certain customers may feel that these constraints are too restrictive. On the other hand, active redundancy makes it obligatory to enter certain data twice, and does not allow the use of the entire directory during the switchover phase to the backup server. In addition, duplicate licenses must be acquired (see chapter 5.2, discount request) with additional server requirements in case of redundancy modules (Accounting and Directory). 4.3. The choice of modules to protect There are two typical cases: Total protection (all the modules): In this case, both redundancy solutions can be considered. ESD / Pre Sales / JMB 12/14 October 2009 Ed04

Partial protection (some of the modules): In this case, the active redundancy solution must be proposed. To make this choice, you must determine, with the customer, the level of protection the customer wants to provide for each module. The 4760 server modules can be grouped in three levels of protection: "High level Metering/Traffic observation, ticket collector, Directory "Medium level Alarms/Topology However this module may be considered extremely important in a case where the customer provides a range of services for its customers (carrier services). "Low level Configuration Unlike the other modules, there is no configuration database resident in the 4760 server; each PCX has its own database, and the 4760 server only carries out actions on these databases. Workaround solutions can be provided to ensure management continuity actions: The system console of each PCX Web access on the HTTP server of each OmniPCX Enterprise or Office An e-config client for the OmniPCX Enterprise A PM5 or OMC client for the OmniPCX Office ESD / Pre Sales / JMB 13/14 October 2009 Ed04

5. Ordering procedure 5.1. Passive redundancy If Alcatel supplies the server PC, two complete server PCs must be ordered in ACTIS, including: PC pack, keyboard, display for the 4760 server (see additional hardware/server for applications: platforms). The Business Partner or the customer must order two server PCs if they supply the servers. 5.2. Active redundancy Use an ACTIS sheet 15 for an OmniPCX Enterprise or 4400 to define the configuration of the backup server by: Checking the modules that must be protected Transferring the options configured in the main server Adding the modem(s) for PPP connections, if necessary NB: Remember the order for each server the Business Partner or the customer is supplying. Submit a discount request to Marketing 4760 (sylvie.mehl@alcatel.fr) for the licenses for the redundant server. This request will be sent by e-mail with the order reference of the main server as well as the detailed cost sheet for the backup server. If redundancy of the Directory is requested (replication), a PCS request of OmniVista 4760 must be made. If you have reactions or comments to make about this document, please send an e-mail to enterprise.presalesfeedback@alcatel.fr with the title of this document and the subject. End of document 15 Sheet other than the sheet used to order the main 4760 server. ESD / Pre Sales / JMB 14/14 October 2009 Ed04