Engineering Guide 1

Title page

Alcatel-Lucent 9959 Networ Net work k Perf erform ormanc ance e Opt Optimi imizer zer | M4 Engineering Guide npoengg 3BK174465123PGZZA Issu Is sue e 22 | Fe Febr brua uary ry 20 2012 12

Alcatel-Lucent – Proprietary Use pursuant to applicable agreements

Legal notice Legal notice

Alcatel, Lucent, Alcatel-Lucent and the the Alcatel-Lucent logo logo are trademarks of Alcatel-Lucent. All other trademarks are the the property of their respective respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility responsibility for inaccuracies contained herein. Copyright © 2012 Alcatel-Lucent. All rights reserved. reserved. Contains proprietary/trade secret information information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside Alcatel-Lucent without its written authorization. Not to be used or disclosed except in accordance with applicable agreements.


Legal notice Legal notice

Alcatel, Lucent, Alcatel-Lucent and the the Alcatel-Lucent logo logo are trademarks of Alcatel-Lucent. All other trademarks are the the property of their respective respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility responsibility for inaccuracies contained herein. Copyright © 2012 Alcatel-Lucent. All rights reserved. reserved. Contains proprietary/trade secret information information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside Alcatel-Lucent without its written authorization. Not to be used or disclosed except in accordance with applicable agreements.


Contents

Preface Purpose ............................ xi .............................................................. ................................................................... ................................................................. .............................................................. .............................................................. ................................ xi Reason for reissue ............................... xi ................................................................ ................................................................... ............................................................... ............................................................. ......................................... ......... xi Document pertinence ................................. xi .................................................................. .................................................................. .............................................................. .............................................................. ................................... .. xi Audience ............................. xii ............................................................... ................................................................... ................................................................ .............................................................. .......................................................... ........................... xii Assumed knowledge ............................. xii ............................................................... ................................................................... ................................................................ .............................................................. ................................... .... xii Product names ............................ xii .............................................................. ................................................................... ................................................................. .............................................................. ............................................... ................. xii How to comment ............................... xii ................................................................. ................................................................... .............................................................. .............................................................. .......................................... ......... xii

1

NPO Architecture Overview .............................. 1-1 ............................................................... .................................................................. ................................................................ .............................................................. ....................................................... ........................ 1-1 Presentation ............................. 1-1 .............................................................. .................................................................. ................................................................. .............................................................. .................................................. .................... 1-1

2

NPO hardware solutions Overview .............................. 2-1 ............................................................... .................................................................. ................................................................ .............................................................. ....................................................... ........................ 2-1 NPO without WCT or PCMD option .............................. 2-1 ............................................................... .................................................................. ................................................................ ................................. 2-1 NPO with WCT option ................................ 2-4 .................................................................. ................................................................... .............................................................. ........................................................ ........................... 2-4 NPO with PCMD option ............................ 2-6 .............................................................. ................................................................... ................................................................. ......................................................... ......................... 2-6 NPO with WCT and PCMD P CMD option ............................. 2-8 ............................................................... ................................................................... ................................................................ .................................... ..... 2-8 NPO X86 hardware description ................................. 2-9 ................................................................... ................................................................... ............................................................. ....................................... ........... 2-9 SPARC Servers .............................. 2-11 ................................................................ ................................................................... ............................................................... .............................................................. ......................................... ......... 2-11 Citrix server requirements .............................. 2-14 ............................................................... .................................................................. ................................................................ ................................................... .................... 2-14 Automatic Storage Management ............................. 2-14 .............................................................. ................................................................... ................................................................. ...................................... ....... 2-14

................................................................................................... ................................................................. .............................................................. .............................................................. ................................................................... .................................................................. ................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO iii npoengg M4 Use pursuant to applicable agreements Issue Issu e 22 Febr February uary 2012

Contents ....................................................................................................................................................................................................................................

3

Hardware availability Overview ...................................................................................................................................................................................... 3-1 3-1 Hardware redundancy strategy ............................................................................................................................................ 3-1 3-1 NPO nominal and recovery mode ....................................................................................................................................... 3-4 3-4 SAM redundancy support ...................................................................................................................................................... 3-5 3-5 NPO redundancy ....................................................................................................................................................................... 3-5 3-5

4

Capacity considerations Overview ...................................................................................................................................................................................... 4-1 4-1 Overview ...................................................................................................................................................................................... 4-1 4-1 Number of users ........................................................................................................................................................................ 4-2 4-2 Maximum number of MME .................................................................................................................................................. 4-3 4-3 2G dimensioning information .............................................................................................................................................. 4-3 4-3 3G dimensioning information .............................................................................................................................................. 4-4 4-4 4G dimensioning information .............................................................................................................................................. 4-4 4-4 Multi-techno dimensioning ................................................................................................................................................... 4-4 4-4

5

Miscellaneous Overview ...................................................................................................................................................................................... 5-1 5-1 Discontinued hardware ........................................................................................................................................................... 5-1 5-1 Minimum throughput requirements ................................................................................................................................... 5-1 5-1 Interface information ............................................................................................................................................................... 5-2 5-2 Hardware partitioning ............................................................................................................................................................ 5-6 5-6

6

Platform Upgrades and Changes Overview ...................................................................................................................................................................................... 6-1 6-1 Procedures involving a single machine ............................................................................................................................ 6-1 6-1 Procedures involving two machines .................................................................................................................................. 6-2 6-2

7

Maintenance Backup / Restore Overview ...................................................................................................................................................................................... 7-1 7-1 Scope ............................................................................................................................................................................................. 7-1 7-1

.................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO iv Use pursuant to applicable agreements npoengg M4 Issue 22 February 2012

Contents ....................................................................................................................................................................................................................................

Policy and scheduling .............................................................................................................................................................. 7-2 7-2 Backup/restore solution on Solaris ..................................................................................................................................... 7-2 7-2 Backup/restore solution on Linux ....................................................................................................................................... 7-4 7-4

8

Client Overview ...................................................................................................................................................................................... 8-1 8-1 Configuration ............................................................................................................................................................................. 8-1 8-1

9

Network Time Synchronization Overview ...................................................................................................................................................................................... 9-1 9-1 Overview ...................................................................................................................................................................................... 9-1 9-1 About NTP functionality ........................................................................................................................................................ 9-2 9-2 Compatibility .............................................................................................................................................................................. 9-3 9-3 Time source selections ............................................................................................................................................................ 9-3 9-3 Redundancy and resiliency .................................................................................................................................................... 9-3 9-3 Default behavior of WMS or NPO main server under outage conditions ............................................................ 9-3 9-3 Recommended NTP architecture ......................................................................................................................................... 9-4 9-4 Using public time sources over internet ........................................................................................................................... 9-4 9-4 NTP accuracy and network design requirements .......................................................................................................... 9-5 9-5 NTP resource usage considerations .................................................................................................................................... 9-5 9-5

10

Remote NPO Installation Overview ................................................................................................................................................................................... 10-1 10-1 Remote installation using ILO ........................................................................................................................................... 10-1 10-1

.................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO v npoengg M4 Use pursuant to applicable agreements Issue 22 February 2012

Contents ....................................................................................................................................................................................................................................

.................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO vi Use pursuant to applicable agreements npoengg M4 Issue 22 February 2012

List of tables

2-1

Configurations based on HP hardware 2G/MPM (recommended for new deployment) - NPO without WCT or PCMD option ......................................................................................................................... 2-3 2-3

2-2

Configurations based on HP hardware 3G/4G (recommended for new deployment) - NPO without WCT or PCMD option ......................................................................................................................................... 2-3 2-3

2-3

Configurations based on existing SPARC hardware M4000 and T5220 - NPO without WCT or PCMD option ........................................................................................................................................................... 2-4 2-4

2-4

Configurations based on HP hardware (recommended for new deployment) - NPO with WCT option .......................................................................................................................................................................... 2-6 2-6

2-5

Configurations based on existing SPARC hardware M4000 and T5220 - NPO with WCT option 2-6 ................................................................................................................................................................................. 2-62-6

2-6

Configurations based on HP hardware (recommended for new deployment) - NPO with PCMD option .......................................................................................................................................................................... 2-7 2-7

2-7

Configurations based on existing SPARC hardware M4000 and T5220 - NPO with PCMD option 2-7 ................................................................................................................................................................................. 2-72-7

2-8

Configurations based on HP hardware (recommended for new deployment) - NPO with WCT and PCMD option ........................................................................................................................................................... 2-8 2-8

2-9

Configurations based on existing SPARC hardware M4000 and T5220 - NPO with WCT and PCMD option ........................................................................................................................................................... 2-8 2-8

6-1

One-machine upgrade scenarios .......................................................................................................................... 6-1 6-1

6-2

Two-machine upgrade scenarios .......................................................................................................................... 6-2 6-2

7-1

Database backup table ............................................................................................................................................. 7-2 7-2

7-2

Application backup table ........................................................................................................................................ 7-2 7-2

.................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO vii npoengg M4 Use pursuant to applicable agreements Issue 22 February 2012

List of tables ....................................................................................................................................................................................................................................

.................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO viii Use pursuant to applicable agreements npoengg M4 Issue 22 February 2012

List of figures

2-1

NPO without auxiliary server ............................................................................................................................... 2-2 2-2

2-2

NPO with auxiliary server ...................................................................................................................................... 2-3 2-3

2-3

NPO with WCT support (48K configuration) ................................................................................................. 2-5

2-4

NPO with WCT support (1500 cells configuration) ..................................................................................... 2-5

2-5

NPO with PCMD support (48K configuration) .............................................................................................. 2-7

2-6

System controller connectivity ........................................................................................................................... 2-12 2-12

2-7

M4000 with System controller and ST2540 connectivity ........................................................................ 2-13

.................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO ix npoengg M4 Use pursuant to applicable agreements Issue 22 February 2012

List of figures ....................................................................................................................................................................................................................................

.................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO x Use pursuant to applicable agreements npoengg M4 Issue 22 February 2012

Preface Preface

Purpose

This document provides detailed information about: •

The engineering rules for the NPO Servers

•

OAM Server hardware/software requirements

•

Backup and restore

•

Remote access

•

Other OAM engineering information for the NPO.

Reason for reissue

Refer to the following Editions for a list of technical and editorial updates to the current guide. In Edition 22

First official release of document for Release M4.1 R7 ML2 In Edition 21

First official release of document for Release M4.1 R7 ML In Edition 20

First official release of document for Release M4.1 R7. In Edition 02

Improvements done for Backup/Restore on Linux/Solaris. In Edition 01

First official release of document for Release M4.1. Document pertinence

This document applies to NPO M4.1.

................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary xi Use pursuant to applicable agreements

Alcatel-Lucent 9959 NPO npoengg M4 Issue 22 February 2012

Preface ....................................................................................................................................................................................................................................

Audience

This document is intended for: •

Network engineers

•

Installation engineers

•

Network & System Administrators.

Assumed knowledge

You must be familiar with: •

Oracle hardware

•

HP hardware

Product names

The generic term NPO refers to all NPO types. When a case applies to a specific NPO, the type of NPO is clearly indicated. How to comment

.................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO xii Use pursuant to applicable agreements npoengg M4 Issue 22 February 2012

1

NPO Architecture 1

Overview Purpose

This section provides an overview of the NPO architecture. Contents Presentation

1-1

Presentation The NPO offers a full range of multi-standard QoS Monitoring and radio network optimization facilities: •

Powerful Graphical User Interface supporting all efficient use of the NPO functions

•

QoS analysis

•

QoS decrease cause diagnosis

•

Radio resource configuration tuning

•

Cartographic telecom management

•

Manage hardware inventory

•

Customizing

This product includes a powerful Oracle database containing performance measurements and calculated indicators. The NPO is an option that offers a full range of QoS Monitoring and radio network optimization facilities. It requires a dedicated server in the LAN with access to applications from a PC Client. The NPO retrieves the counters files available in the Alcatel-Lucent OMC. The loading of PM files is managed continuously according the availability of the files within the OMC server. In addition, the Network configuration (topology) is uploaded from the WMS server. The NPO provides two options that impact the hardware configuration: •

The NPO PCMD option (for LTE)

................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary 1-1 Use pursuant to applicable agreements


Presentation

NPO Architecture

....................................................................................................................................................................................................................................

This option is used for processing the PCMD data coming from the MME. •

The NPO WCT option (for W-CDMA) This option is used for processing the CTN/CFT call trace data coming from the RNC (via the WMS).

The NPO runs on the: • •

Solaris SPARC server, based on Sun V490, T5220 and M4000. HP X86 RedHat Linux server (starting from NPO 4.1), based on HP DL380 G7 and DL580 G7.

The NPO supports OMCs managing: •

GSM network (OMC-R)

•

W-CDMA network (WMS)

•

LTE network (SAM) Note: For LTE network 1 NPO for 1 SAM is the only supported case.

.................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO 1-2 Use pursuant to applicable agreements npoengg M4 Issue 22 February 2012

2

NPO hardware solutions 2

Overview Purpose

This chapter presents an overview of the hardware and is not intended to be directly used for ordering. Refer to the Product Configuration List (PCL) for ordering information. Contents NPO without WCT or PCMD option

2-1

NPO with WCT option

2-4

NPO with PCMD option

2-6

NPO with WCT and PCMD option

2-8

NPO X86 hardware description

2-9

SPARC Servers

2-11

Citrix server requirements

2-14

Automatic Storage Management

2-14

NPO without WCT or PCMD option This section applies to GSM, W-CDMA or LTE. The NPO is composed of: •

•

A main server This server supports the oracle database and the reporting functions. One optional QoS auxiliary server. This server hosts the loading process that converts 3GPP PM files into a format that can be directly loaded into NPO Oracle tables.

Only the main server stores data. The auxiliary servers only store files while they are being loaded. The backup and restore procedure only applies to the main server.



NPO without WCT or PCMD option

NPO hardware solutions

....................................................................................................................................................................................................................................

Note: The following rules apply: • •

•

•

•

•

Cells can be a mix of 3G and 4G cells Users refers to concurrent users using the analysis desktop. Use of the external export interface is not considered when counting concurrent users. The HP hardware is dimensioned to support more users than SPARC (for the same number of cells). The HP is dimensioned with extra disk space as compared to the SPARC, to handle more future growth. Assuming a standard rack of 42U, it is always possible to put two NPO systems in the same rack. If the SAM has an auxiliary server, the NPO retrieves PM from the SAM auxiliary server and CM from the SAM main server.

The following figures show the NPO with and without an auxiliary server. Figure 2-1 NPO without auxiliary server




....................................................................................................................................................................................................................................

Figure 2-2 NPO with auxiliary server

Refer to the following tables for specific information about the various configurations. Table 2-1

Configurations based on HP hardware 2G/MPM (recommended for new deployment) - NPO without WCT or PCMD option

Configuration

Users

Main server

Auxiliary server QoS

Auxiliary server WCT

Auxiliary server PCMD

Total power

Total height

4000 cells, QoS only

15

1 HP small

0

0

0

850W

2U


15

1 HP small MPM

0

0

0

850W

2U


45

1 HP medium

0

0

0

1135W

4U


120

1 HP XL

1 HP aux

0

0

3169W

14U

Table 2-2

Configurations based on HP hardware 3G/4G (recommended for new deployment) - NPO without WCT or PCMD option

Configuration

Users

Main server




Total power

Total height


15

1 HP small

0

0

0

850W

2U

.................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO 2-3 npoengg M4 Use pursuant to applicable agreements Issue 22 February 2012



.............................................................. ............................. ................................................................... ................................................................. ............................................................. ................................................................ ................................................................... ..................................... ....

Table 2-2 2-2

Configurations Configura tions based based on HP HP hardware hardware 3G/4G 3G/4G (recom (recommended mended for new deployment deplo yment)) - NPO NPO without without WCT or PCMD PCMD option option (cont (continued) inued)

Configuration

Users

Main server




Total power

Total height


45

1 HP medium

0

0

0

1135W

4U


120

1 HP XL

1 HP aux

0

0

3169W

14U

Table 2-3 2-3

Configurations Configura tions based based on existing existing SP SPARC hardware hardware M4000 M4000 and T5220 NPO without WCT or PCMD option

Configuration

Users

Main server




Total power

Total height


5

1

0

0

0

625W

2U

0

0

0

893W

8U

0

0

0

1007W

10U

T5220 9000 cells, QoS only

27

1 M4000-2


38

1 M4000-4

NPO with WCT option Note: This section is applicable only to W-CDMA.

The W-CDMA W-CDMA Call Trace Trace (WCT) option allows the NPO to upload CTN and CFT call traces from the WMS and process them. When this option is activated, two additional modules start on the NPO server: •

•

The WCT Controller Controller retrieves the list of CTN/C CTN/CFT FT files to be uploaded from the WMS The WCT loader (referred to as LOLA) processes the CTN/CFT file.

For a 1500 cells configuration, the additional module runs on the same server. Above 1500 cells, this WCT loader must run on a dedicated auxiliary server(s): one auxiliary server per 24000 cells. The following figures show the different types of WCT support.

.............................................................. ............................. ................................................................... ................................................................. ............................................................. ................................................................ ................................................................... ..................................... .... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO 2-4 Use pursuant to applicable agreements npoengg M4 Issue Issu e 22 Febr February uary 2012


NPO with WCT option

................................................................. ................................ ................................................................... .............................................................. .............................................................. ................................................................... .................................................................. ...................................

Figure Figur e 2-3 NPO with WCT suppor supportt (48K configur configuration) ation)

Figure Figur e 2-4 NPO with WCT support support (1500 cells cells configurat configuration) ion)

Refer to the following tables for specific information about the various configurations.

................................................................................................... ................................................................. .............................................................. .............................................................. ................................................................... .................................................................. ................................... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO 2-5 npoengg M4 Use pursuant to applicable agreements Issue Issu e 22 Febr February uary 2012

NPO with WCT option


.............................................................. ............................. ................................................................... ................................................................. ............................................................. ................................................................ ................................................................... ..................................... ....

Table 2-4 2-4

Configurations Configura tions based based on HP HP hardware hardware (recom (recommende mended d for new new deployment) - NPO with WCT option

Configuration

Users

Main server




Total power

Total height

1500 cells, QoS + WCT

7

1 HP small

0

0

0

850W

2U


45

1 HP medium

0

1 HP aux

0

1985W

4U


120

1 HP XL

1 HP aux

2 HP aux

0

4869W

14U

Table 2-5 2-5

Configurations Configura tions based based on existing existing SP SPARC hardware hardware M4000 M4000 and T5220 NPO with WCT option

Configuration

Users

Main server




Total power

Total height


27

1

0

1 HP aux

0

1693W

10U

18000 cells, QoS + WCT only

38

0

1 HP aux

0

1807W

12U

M4000-2 1 M4000-4

NPO with PCMD option Note: This section is applicable only to LTE.

Compared to the regular NPO, the NPO PCMD requires: •

•

A conn connection ection to the MME (from both the NPO main server and the NPO auxil auxiliary iary servers) For 12K cells and above, NPO auxiliary server(s) dedicated to PCMD.

The following figure shows the different types of PCMD support.

.............................................................. ............................. ................................................................... ................................................................. ............................................................. ................................................................ ................................................................... ..................................... .... Alcatel-Lucent – Proprietary Alcatel-Lucent 9959 NPO 2-6 Use pursuant to applicable agreements npoengg M4 Issue Issu e 22 Febr February uary 2012



....................................................................................................................................................................................................................................

Figure 2-5 NPO with PCMD support (48K configuration)

Refer to the following tables for specific information about the various configurations. Table 2-6

Configurations based on HP hardware (recommended for new deployment) - NPO with PCMD option

Configuration

Users

Main server




Total power

Total height

1500 cells, QoS + PCMD

7

1 HP small

0

0

0

850W

2U


45

1 HP medium

0

0

1 HP aux

1985W

6U

48000 cells, QoS + WCT or PCMD

120

1 HP XL

1 HP aux

2 HP aux

0

4869W

18U

Table 2-7

Configurations based on existing SPARC hardware M4000 and T5220 NPO with PCMD option

Configuration

Users

Main server




Total power

Total height


27

1

0

0

1 HP aux

1693W

10U

M4000-2




....................................................................................................................................................................................................................................

Table 2-7

Configurations based on existing SPARC hardware M4000 and T5220 NPO with PCMD option (continued)

Configuration

Users

Main server




Total power

Total height

18000 cells, QoS + PCMD only

38

1

0

0

1 HP aux

1807W

12U

M4000-4

NPO with WCT and PCMD option An auxiliary server must be dedicated to either PCMD or WCT. Refer to the following tables for specific information about the supported configurations. Table 2-8

Configurations based on HP hardware (recommended for new deployment) - NPO with WCT and PCMD option

Configuration

Users

Main server


Auxiliary server WCT or PCMD

Total power

Total height

1500 cells, QoS + WCT + PCMD

7

1 HP small

0

0

850W

2U


45

1 HP medium

0

2 HP aux

1985W

10U


120

1 HP XL

0

3 HP aux (assuming 24K LTE cells and 24K W-CDMA cells)

4869W

18U

Table 2-9

Configurations based on existing SPARC hardware M4000 and T5220 NPO with WCT and PCMD option

Configuration

Users

Main server



Total power

Total height


7

1 HP small

0

0

850W

2U


45

1 HP medium

0

2 HP aux

1985W

10U


NPO with WCT and PCMD option


....................................................................................................................................................................................................................................

Table 2-9

Configurations based on existing SPARC hardware M4000 and T5220 NPO with WCT and PCMD option (continued)

Configuration

Users

Main server



Total power

Total height


120

1 HP XL

0

3 HP aux (assuming 24K LTE cells and 24K W-CDMA cells)

4869W

18U

NPO X86 hardware description For a better performance, it is recommended to use the X86 servers which are based on the new HP Generation 7 processor units. HP DL 380

The DL380 G7 configuration consists of three base configurations: •

DL 380 small configuration

•

Medium configuration.

•

Auxiliary configuration.

The differences between the servers concerns the number of processors used, RAM memory or the external disk array connection. All of the DL380 G7 server are Intel based processor servers that are part of HP Generation 7 servers. DL 380 S Base hardware CPU

1 * 2.93 GHz Xeon X5670 Processors

RAM

36 GB

Hard disk

12 * 600GB 6G SAS 10K internal disk

Note: This hardware is the same as the HP auxiliary server but with only one CPU. The server height is 2U. The power needed is 850W. DL 380 M Base hardware CPU



NPO X86 hardware description


....................................................................................................................................................................................................................................

Base hardware RAM

72 GB

Hard disk

12 * 300GB 6G SAS 10K internal disk 2*200GB 3G SATA 2.5in internal disk SSD HP 2600 Disk Enclosure, 12*600-GB

The server height is 4U (2U for the DL380 itself and 2U for the disk bay). The power needed is 1135W (850W for DL380 itself, 285W for the disk bay). DL 380 Aux Base hardware CPU


RAM

36 GB

Hard disk

12 * 300GB 6G SAS 10K internal disk

HP DL 580 v2

The DL580 server includes one XLarge configuration based on the Intel processor and includes an external disk array. The estimated database size for the Oracle database is 5 Tb for 48000 cells. The NPO also requires additional disk space for various other files. Base hardware CPU

4 * 2.26 GHz Xeon E7-4830 Processors

RAM

256 GB

Hard disk

2 * 300GB 6G SAS 10K internal disk 6 * 200GB 3G SATA 2.5in internal disk SSD HP 2600 Disk Enclosure, 48*600-GB

The server height is 12U (4U for the DL580 itself and 4 * 2U for the disk bays). The power needed is 1179W for DL580 and 285W for each disk bay, therefore the total power is 2319W.


SPARC Servers


....................................................................................................................................................................................................................................

SPARC Servers SUN SPARC ENTERPRISE T5220

The SPARC Enterprise T5220 configuration features one 8 Core 1.4GHz UltraSPARC T2 processor. If requested, the SPARC T5220 server can be equipped with an optional USB LCD flat display option with keyboard. Base hardware CPU

1 * 1400 MHz UltraSPARC T2 8 core Processors

RAM

16 GB

Hard disk

8 x 146 GB Internal Disk Drives

The server height is 2U and the power consumption is 624 W. T5220 connectivity

In addition to its Quad Ethernet Interface Cards, the T5220 server uses its ILOM card to manage and configure the system. Integrated Lights Out Manager (ILOM) is system management firmware that provides a browser-based web interface and a command-line interface, as well as a Syslog interface, an SNMP user interface and an IPMI user interface. The T5220 SP-ILOM card has a 100-BASE-T Ethernet connection; 1 cable is required. It requires one IP address and no redundancy is available in the XSCF controller card. (The Serial link on the controller card can still be reached though a console server).


SPARC Servers


....................................................................................................................................................................................................................................

Figure 2-6 System controller connectivity

SUN SPARC M4000

The SPARC M4000 configuration depends on the number of processors used or on the amount of RAM memory. It is possible to attach an external disk array single or dual. SUN SPARC M4000-2 Base hardware CPU

2 * 2500 MHz quad core SPARC 64 VII Processors

RAM

32 GB

Hard disk

2 * 300GB 10K-RPM 2.5” SAS internal disk ST2540 Rack Ready external disk controller tray, 12*300-GB

SUN SPARC M4000-4 Base hardware CPU

2 * 2500 MHz quad core SPARC 64 VII Processors

RAM

64 GB


SPARC Servers


....................................................................................................................................................................................................................................

Base hardware Hard disk

2 * 300GB 10K-RPM 2.5” SAS internal disk ST2540 Rack Ready external disk controller tray, 24*300-GB ST2501 SAS Expansion Array

Prerequisites for M4000 installation

For Windows PCs: • •

•

A USB to serial adaptor must be used if a serial port is not available on the PC The workstation must be installed in the same subnetwork as the server, when the Ethernet port is connected Configure the HyperTerminal.

For M4000 machines, reserve four IP addresses: • •

One for the M4000 ETH0 port The IP network must be different from 192.168.128.x which is reserved for disk array configuration and cannot be used for other purposes

•

One for the M4000 ETH1 M4000 port, to connect to Storage TEK 2540

•

One for the XSCF Ethernet port

•

One for the workstation Ethernet port.

M4000 connectivity

The M4000 can be connected to a ST2540 and it also uses its “ILOM” card to manage and configure the system. Figure 2-7 M4000 with System controller and ST2540 connectivity


SPARC Servers


....................................................................................................................................................................................................................................

Citrix server requirements The following table displays the minimum server requirements for the Citrix server. Base hardware CPU

2*2cores CPU for 6 users 2*4cores CPU for 12 users

RAM

8GB RAM for 6 users 16GB RAM for 12 users

Bandwidth requirements

> 256Kb/s

OS

Windows 2008 + RDS+ Citrix XenApp Windows 2003 + TSE + Citrix Presentation Server

Automatic Storage Management Automatic Storage Management (ASM) is a new feature that was introduced in Oracle 10g to simplify the storage of Oracle data files, control files and log files. ASM simplifies the administration of Oracle related files by allowing the administrator to reference disk groups rather than individual disks and files which are managed by ASM. The ASM functionality is an extension of the Oracle Managed Files (OMF). The new ASM functionality can be used in combination with existing raw and cooked file systems, along with OMF and manually managed files. The ASM functionality is controlled by an ASM instance. This is not a full database instance, just the memory structures and as such is very small and lightweight. The main components of ASM are disk groups, each of which comprise several physical disks that are controlled as a single unit. The physical disks are known as ASM disks, while the files that reside on the disks are know as ASM files. The locations and names for the files are controlled by ASM, but user-friendly aliases and directory structures can be defined for ease of reference. In summary, ASM provides the following functions: •

Manages groups of disks, called disk groups.

•

Manages disk redundancy within a disk group.

•

Provides near-optimal I/O balancing without any manual tuning.

•

•

Enables management of database objects without specifying mount points and filenames. Supports large files.




....................................................................................................................................................................................................................................

The following table lists the hardware that has ASM and the hardware that does not. With ASM

Without ASM

M4000 (4CPU and 24 disks) installed for 3G and 4G only

All other SUN platforms

V490 Cluster All HP Platforms




....................................................................................................................................................................................................................................


3

Hardware availability 3

Overview Purpose

This chapter describes the hardware availability used in the NPO. Contents Hardware redundancy strategy

3-1

NPO nominal and recovery mode

3-4

SAM redundancy support

3-5

NPO redundancy

3-5

Hardware redundancy strategy SUN SPARC ENTERPRISE T5220

Sun Enterprise T5220 servers incorporate the following key features to increase RAS: Redundancy and hot-swap components

• •

Reduced parts count that contributes to better overall stability and reliability of the platform

•

Processors thread and core off-lining and built-in RAID capabilities

•

Parity protection and error correction capabilities

•

Integrated Lights Out Management (ILOM) service processor to ease remote management and provide considerable administrative flexibility

•

Superior energy efficiency

•

Robust virtualization technology

•

Comprehensive fault management.



Hardware redundancy strategy

Hardware availability

....................................................................................................................................................................................................................................

Hot Plug-able Components and Dynamic Reconfiguration

Sun Enterprise T5220 servers support the hot-plug of chassis mounted hard drives, and the hot-swap of redundant fan units and power supplies. For systems configured with redundant components, administrators can utilize software commands to remove and replace disks, power supplies, and fan units while the system continues to operate. T5220 also supports RAID capabilities. Power Supply Redundancy

The system features two hot-swappable power supplies, either of which is capable of handling the system’s entire load. Thus, the system provides N+1 redundancy, allowing the system to continue operating should one of the power supplies or its AC power source fail. Integrated Lights Out Management for Simplified Remote Serviceability

The Integrated Lights Out Management (ILOM) service processor is a system controller built into all T5220 servers, facilitating remote system management, simplifying administration, and speeding maintenance tasks. The ILOM circuitry runs independent of the server, using the server’s standby power. Therefore, ILOM firmware and software continue to function when the server operating system goes offline or when the server is powered off. ILOM monitors the following T5220 server conditions: •

CPU temperature conditions

•

Hard drive status

•

Enclosure thermal conditions

•

Fan speed and status

•

Power supply status

•

Voltage conditions

•

Solaris watchdog, boot time-outs and automatic server restart events.

ILOM provides administrators with the capability to monitor and control T5220 servers over a dedicated Ethernet connection and supports secure shell (SSH), Web, and Integrated Platform Management Interface (IPMI) access. ILOM functions can also be accessed through a dedicated serial port for connection to a terminal or terminal server. SUN SPARC M4000

To deliver reliability, availability and serviceability, the Sun Enterprise M4000 offers the following features: • •

• •

Supports redundant configurations and active replacement of power supplies and fans. Periodically performs memory patrol to detect memory software errors and stuck-at faults, (Memory patrol) Supports redundant configurations, mirroring, and active replacement of disks XSCF (detailed below) collection of fault information, and preventive maintenance using different types of warnings




.................................................................................................................................................................................................................................... •

•

•

Shortens the downtime by using automatic system reboot and time taken for system startup Status LEDs mounted on the main components and the operator panel to display which active components need replacement Centralized systematic monitoring, such as with SNMP.

Power Supply Redundancy

The system features two (M4000) hot-swappable power supplies, either of which is capable of handling the system’s entire load. Thus, the system provides N+1 redundancy, allowing the system to continue operating should one of the power supplies or its AC power source fail. eXtended System Control Facility Unit (XSCFU)

The eXtended System Control Facility Unit (XSCFU) is a service processor that operates and administrates the M4000. The XSCFU diagnoses and starts the entire server, configures domains, offers dynamic reconfiguration, as well as detects and notifies various failures. The XSCFU enables standard control and monitoring function through network. Using this function enables starts, settings, and operation managements of the server from remote locations. The XSCFU uses the eXtended System Control Facility (XSCF) firmware to provide the following functions: • •

•

Controls and monitors the main unit hardware Monitors the Solaris Operating System (Solaris OS), power-on self-test (POST), and the OpenBoot PROM Controls and manages the interface for the system administrator (such as a terminal console)

•

Administrators device information

•

Controls remote messaging of various events

The XSCF firmware provides the following system control and monitoring interfaces: • •

Serial port through which the command-line interface (XSCF shell) can be used Two LAN ports. These are: –

XSCF shell

–

XSCF Web (browser-based user interface)

HP DL380 HP Integrated Lights-Out

HP Integrated Lights-Out (iLO) simplifies server setup, health monitoring, power and thermal control, and lights-out remote administration of the server. HP iLO functions without additional software and can be accessed from any location via a web browser. For full set of ILO features consult the following HP web page:




....................................................................................................................................................................................................................................

http://h18013.www1.hp.com/products/servers/management/remotemgmt.html

HP iLO works hand-in-hand with HP Systems Insight Manager, Insight Control and Insight Dynamics for servers. Power Supply Redundancy

The system features two (DL380) hot-swappable power supplies, either of which is capable of handling the system’s entire load. HP DL580 HP Integrated Lights-Out

HP Integrated Lights-Out (iLO) simplifies server setup, health monitoring, power and thermal control, and lights-out remote administration of the server. HP iLO functions without additional software and can be accessed from any location via a web browser. For full set of ILO features consult the following HP web page: http://h18013.www1.hp.com/products/servers/management/remotemgmt.html

HP iLO works hand-in-hand with HP Systems Insight Manager, Insight Control and Insight Dynamics for servers. Power Supply Redundancy

The system features four (DL580) hot-swappable power supplies, either of which is capable of handling the system’s entire load.

NPO nominal and recovery mode The NPO can support different QoS granularity periods depending on NE capabilities to provide raw data. In the case of an exceptional outage or anomaly with the NPO (e.g.: link cut, server unavailability) during a certain period, a large number of QoS files may be expected and waiting for processing by the NPO at the next establishment of the system. In such conditions, a period of recovery is observed to enable the NPO to reach its nominal mode. The period of recovery depends of several conditions, including the period of outage, the quantity of observation files (such as the number of network element and the granularity), the type of the machines, etc... The recovery time also includes the normal recovery plus the consolidation period. In the recovery mode, the data recovered is from the current day but also if necessary from the last day or the last two days. If normal consolidation (nightly consolidation for day 1) is terminated in less than 3 hours (configurable value), then a recovery consolidation is triggered if needed. If several days are in recovery, then the recovery consolidation is performed on the more recent day (from day 2 to day 15). If normal consolidation failed, recovery consolidation is not launched.


NPO nominal and recovery mode


....................................................................................................................................................................................................................................

In the case of manual file management with the WMS (33282 - Manual collection and mediation of counters files feature) due to missing periods observed in the NPO (e.g.: a rare condition where the network element has not sent a file, or in the case of file corruption, etc...), the files can be managed by the NPO within a maximum period of three days in the past.

SAM redundancy support The two IP addresses of SAM are declared as SAM data sources during NPO commissioning. If one SAM is unavailable, the NPO automatically connects to the other one.

NPO redundancy Two (or more) NPO can be connected to the same SAM: •

•

•

• Both collect data from SAM active and stand by. NPO manage internally a list of files already loaded , it use that to avoid loading the same file twice from SAM main and space. Both NPO are “active” and can be used at any given time. The operator can connect to either one. Both can use different versions and different hardware.

The following figure shows the potential configurations.



NPO redundancy

....................................................................................................................................................................................................................................


4

Capacity considerations 4

Overview Purpose

This chapter provides an overview of NPO dimensioning and capacity. Contents Overview

4-1

Number of users

4-2

Maximum number of MME

4-3

2G dimensioning information

4-3


4-4


4-4

Multi-techno dimensioning

4-4

Overview The dimensioning of the NPO to the appropriate hardware mainly depends on the network capacity in term of maximum “reference cells”: •

•

The Total Number of “Reference Cell” to determine the right NPO model is as follows: [0.75* nb of 2G cells + 1 * nb of 3G cells + 1 * nb of 4G Cells] The maximum of OMC server is limited to 5 for UMTS and LTE and 12 for GSM..



Number of users

Capacity considerations

....................................................................................................................................................................................................................................

Number of users The following table shows the number of potential users for each configuration. Configuration names

Users

Supported features

Hardware

NPO HP-S

15

ALL, except PCMD/WCT

DL380 G7-1/Main

NPO HP-S/CT

15

ALL

DL380 G7-1/Main

NPO HP-M

45


DL380 G7-2/Main + D2600

NPO HP-M/CT

45

ALL

DL380 G7-2/Main + D2600 + DL380 G7-2/Aux

NPO HP-XL

120


DL580 G7-4/Main + 4 D2600 + DL380 G7-2/Aux

NPO HP-XL/CT

120


DL580 G7-4/Main + 4 D2600 + 3 DL380 G7-2/Aux

NPO T5220

5


T5220

NPO M4000-2

27


M4000-2-32Gb + ST2540-12

NPO M4000-4

38


M4000-4 + ST2540-24

NPO M4000-2000-GSM

8


M4000-2-16Gb-NoHBA

NPO M4000-6000-GSM

18


M4000-2-16Gb-HBA + ST2540-6

NPO M4000-24000-GSM

50


M4000-4 + ST2540-12

MPM HP-S


Maximum number of MME


....................................................................................................................................................................................................................................

Maximum number of MME The following table provides the maximum number of MME supported by HP configurations, as per Traffic model Configuration names

Max number of MME

NPO HP S

2

NPO HP M

6

NPO HP XL

12

2G dimensioning information The following table provides an overview of 2G dimensioning information. Storage duration Data type

Object type

Hourly

Daily

Weekly

Monthly

GSM

N7SL , BSC_MFS_ LAPD, BEARERCHANNEL GPU_ ECELL2G

16D

93D

13W

3M

ADJ, AIC

1D

93D

13W

3M

GROUP_ SPRMST, GROUP_ SPRMS

0D

16D

1W

1M

All other types

32D

400D

58W

25M




....................................................................................................................................................................................................................................


Object type

Hourly

Daily

Weekly

Monthly

W-CDMA

All

21D

400D

58W

25M


Object type

Hourly

Daily

Weekly

Monthly

LTE

All

32D

400D

58W

25M

Note: Granularity Period for eNodeB is 15 minutes.

Multi-techno dimensioning The following rules apply: • •

1 reference cell = 1 W-CDMA cell = 1 LTE cell = 1.33 GSM cells Only two technologies are supported at the same time by NPO: NPO 2G+3G or 3G+4G or 2G+4G but not NPO 2G+3G+4G.


5

Miscellaneous 5

Overview Purpose

This chapter provides information about: •

Discontinued hardware

•

Minimum throughput requirements

•

Interface information

•

Hardware partitioning

Contents Discontinued hardware

5-1


5-1


5-2


5-6

Discontinued hardware Minimum throughput requirements The maximum deadline for file availability in the NPO, including loading, must be in general under one third of the configured General Permanent Observation (GPO) period. This one third GPO is an absolute period within which file transfers occur continuously, including regular pooling activity, file parsing, and the loading of data within the NPO oracle database. With regard to the pure file transfer activity, the duration usually takes 10% of the one third GPO. To guarantee the NPO's performance with regards to basic recovery scenarios (for example, missing data, loss of connection that implies managing more data within a same GPO), the quantity of data to be managed by the NPO has to be double accordingly.




Miscellaneous

....................................................................................................................................................................................................................................

As a consequence, the General Minimum throughput requirement for a nominal NPO usage is defined as follows: General Minimum throughput requirements (in kbps) =

= Size of the RNC i observation file (in kiloBytes) under a given configuration (e.g.: 185 kiloBytes for each RNC with CP3 configured with 100 dNodeB2U BTS) Srnc

i

= Number of RNC i Sbts i = Size of the BTS i observation file under a given configuration (e.g.: 6 kiloBytes for each dNodeB2U BTS configured with about 3 cells)

Nbrnc

i

Nbbts

i

= Number of BTS

GPO: The minimum general permanent observation period (in seconds) configured on the

BTS Network elements (e.g.: 900 seconds).

Interface information Note: The default gateway is always set on the OAM interface in both single and multiple interface environments. Alcatel-Lucent provides the opportunity to configure the IP and netmask for the NE and BR interfaces. The NPO installation procedure does not customize additional routing specific to the customer network. This will be configured by customer after installation. Within NPO

The following figure provides an overview of the interfaces within the NPO.



Miscellaneous

....................................................................................................................................................................................................................................

The following table provides detailed information about each interface. Interface

Between

Protocol

Bandwidth

(a) NPO client

NPO client<=>Main server

CORBA, HTTP, HTTPS

The Minimum Throughput Requirement per NPO Client is 1 Mbps. For network constraints in term of bandwidth capabilities, a SOC (server of client, e.g. Citrix) solution should be considered. To comply with the throughput requirement, every client should be connected to an Ethernet switch through a 100/1000Mbps connection.

(b) toward aux server

NPO main server<=>NPO aux server

CORBA, HTTP, HTTPS, SFTP

1Gb/s is needed

(c) Backup (optional)

NPO main server<=>central backup

Depend on backup server.

10 Gb interface is required for fast backup. Minimum 1Gb interface for backup.



Miscellaneous

....................................................................................................................................................................................................................................

Between NPO, SAM and MME

The OAM servers, including the NPO, must be located within the same Ethernet LAN that operates at Giga bits Ethernet and the 1000 Mbps capabilities must be extended to all the Routing Switches. The files are compressed. This requirement covers: •

Communication between the NPO main server and auxiliary server

•

Communication between the NPO and the SAM.

The following figure provides an overview of the interfaces between the NPO, SAM and MME.

The following table provides detailed information about each interface. Interface

Protocol

Bandwidth

(a) SAM<=>NPO aux

SFTP, SSH

PM file: 180 kB/eNB (3 cells/eNB) So 3.2 MB/s for 48K cells



Miscellaneous

....................................................................................................................................................................................................................................

Interface

Protocol

Bandwidth

(b) MME<=>NPO aux

SCP, SSH

(Only when the PCMD option is used) PCMD file: 250 MB at BH (per minute, per MME) Bandwidth : 4MB/s/MME (at BH)

NPO Server IP address requirements for DL580/DL380

These requirements apply to all servers (NPO main/NPO auxiliary). Interface

Function

Eth0 – OAM interface

Connects the server to OMC/XMS/SAM Connects the server to the NPO client PC Connects the NPO server to the AUX server This interface is mandatory.

Eth1

B/R interface for backup operations on a server located in the same network as the IP of this interface This interface is optional.

Eth2

NE interface is used to connect the server to the MME This interface is optional

ILO3

For remote connection on the server

The following table lists the four different NIC configuration possibilities according to the configured network interfaces. Configuration type

Network interfaces

NIC configuration I

Eth0 – OAM interface Eth1 – B/R interface Eth2 – NE interface

NIC configuration II

Eth0 – OAM interface and B/R interface Eth2 – NE interface

NIC configuration III

Eth0 – OAM interface and NE interface Eth1 – B/R interface

NIC configuration IV

Eth0 – OAM interface which is configured and/or linked. This server is also NR and B/R interface.



Miscellaneous

....................................................................................................................................................................................................................................

The ILO3 interface must be configured from the machine's BIOS. NPO Server IP address requirements for M4000/T5220 Server

Address requirements

T5220

Non IPMP: 1 Ethernet interface used With IPMP: 2 Ethernet interface used

M4000

ASM - IPMP: 2 Ethernet interfaces used non IPMP: 1 Ethernet interface used with ASM - PMP: 3 Ethernet interfaces used non IPMP: 2 Ethernet interfaces used

Non SAN is out of the scope of this document.

Hardware partitioning Note: For a complete description of the configurations, refer to the Product Configuration Level. For Linux Server

Redundancy

FS Type

Mount point / Data Group

Partition size (GB)

DL380 G7-1/Main (NPO HP-S)

RAID 1

Ext3

/

25

Ext3

/boot

0.2

Ext3

/var

10

swap

20

Ext3

/alcatel

225

RAID 0

Ext3

/alcatel/backup

1043

RAID 1+ 0

Ext3

/alcatel/temp

200

ASM

DATA

582



Miscellaneous

....................................................................................................................................................................................................................................

Server

Redundancy

FS Type


Partition size (GB)

DL380 G7-2/Main + D2600 (NPO HP-M)

RAID 1

Ext3

/

25

Ext3

./boot

0.2

Ext3

/var

10

swap

20

Ext3

/alcatel

225

RAID 0

Ext3

/alcatel/backup

1564

RAID 1 + 0

ASM

RECOVERY

521

RAID 1

Ext3

/alcatel/ssd

30

ASM

REDO

80

ASM

/alcatel/temp

200

Ext3

DATA

2929

Ext3

/

25

Ext3

/boot

0.2

Ext3

/var

10

swap

20

Ext3

/alcatel

245

Ext3

/alcatel/ssd

200

ASM

REDO

80

RAID 0

Ext3

/alcatel/backup

6258

RAID 1 + 0

ASM

RECOVERY

2086

RAID 1 + 0

ASM

DATA

6258

RAID 1 + 0

Ext3

/alcatel/temp

1043

RAID 1

Ext3

/boot

0.2

RAID 5

Ext3

/var

10

swap

20

Ext3

/

470

Ext3

/alcatel

2500

RAID 1+ 0

DL580 G7-4/Main + 4 D2600 (NPO HP-XL)

RAID 1

RAID 1 + 0

DL380 G7-2/Aux



Miscellaneous

....................................................................................................................................................................................................................................

For Solaris Server


Partition size

NPO T5220

/

20 GB mirror of two slices on internal disks

swap


/usr


/var


/alcatel


/alcatel/oracle/oradata


/alcatel/temp

-

/


swap


/usr


/var


/alcatel



1.6 TB mirror on external storage

/alcatel/temp

200 GB mirror on external storage

NPO M4000-2



Miscellaneous

....................................................................................................................................................................................................................................

Server


Partition size

NPO M4000-4

/


swap


/usr


/var


/alcatel




/alcatel/temp


/


swap


/usr

-

/var

-

/alcatel




/alcatel/temp

-

/


swap


/usr


/var


/alcatel




/alcatel/temp


NPO M4000-2000-GSM

NPO M4000-6000-GSM



Miscellaneous

....................................................................................................................................................................................................................................

Server


Partition size

NPO M4000-24000-GSM

/


swap


/usr


/var


/alcatel




/alcatel/temp



6

6 latform Upgrades and P Changes

Overview Purpose

This chapter describes the upgrade procedures on same hardware and platform changes procedure with hardware and OS changes Contents Procedures involving a single machine

6-1

Procedures involving two machines

6-2

Procedures involving a single machine The procedures that are performed on a single machine can be classified in the following three categories: migration procedures, when the machine is initially running one major release (M3), and at the end of the upgrade procedure the machine is running a newer major release (M4). This procedure is currently available for machines running the Solaris OS only.

•

•

software replacement procedures , when the machine is initially running one minor release (M4Rx) and at the end of the upgrade procedure the machine is running a newer minor release (M4Ry). These procedures are available for machines running both Solaris OS and Linux OS. hardware upgrade procedures , when additional memory and/or CPU's are added to the current hardware configuration. Refer to the Product Configuration Level document for information on possible hardware upgrades.

•

Table 6-1

One-machine upgrade scenarios

Operating System

Initial state

Final state

Solaris

M3

M4

Document to be used

NPO Migrate Software on Same Hardware on Solaris OS (../npomig/index.htm)



Procedures involving a single machine

Platform Upgrades and Changes

....................................................................................................................................................................................................................................

Table 6-1

One-machine upgrade scenarios (continued) M4

M4

M4

M4, hardware upgraded1,2,

NPO Software Replacement on Solaris OS (../nposwrs/index.htm) NPO Change Hardware on Same Software version, on Solaris OS (../npohwcs/index.htm)

3

Linux

M4

M4

M4

M4, hardware upgraded1,4

NPO Software Replacement on Linux (../nposwrl/index.htm) NPO Change Hardware on Same Software version, on Linux OS (../npohwcl/index.htm)

Note:

1. The software version of the machine does not change after this kind of upgrade. 2. Possible hardware upgrades: CPU upgrade, memory upgrade 3. The upgrade from M4000-2 CPU to M4000-4 CPU on the same machine is not supported. The upgrade from M4000-2 CPU to M4000-4 CPU is possible when the source and the target of the upgrade are two different machines (see next chapter). 4. Possible hardware upgrades: CPU upgrade, motherboard upgrade.

Procedures involving two machines When two machines are involved into an upgrade procedure, the NPO running on one machine (called source) is moved to another machine (called target ). Depending on the operating systems running on the two machines, the following cases may appear. •

Source machine is running the Solaris OS, target machine is running the Solaris OS.

•

Source machine is running the Linux OS, target machine is running the Linux OS.

•

Source machine is running the Solaris OS, target machine is running the Linux OS.

Table 6-2

Two-machine upgrade scenarios

Source and target running

Same O/S

Source machine

Target machine

M4 Solaris

M4 Solaris

1,2

1,2

M4 Solaris, M4000-4 CPU2


Document to be used

NPO Change Hardware on Same Software version, on Solaris OS (../npohwcs/index.htm) NPO Change Hardware on Same Software version, on Solaris OS (../npohwcs/index.htm)




....................................................................................................................................................................................................................................

Table 6-2

Different O/S

Two-machine upgrade scenarios

(continued)

M3 Solaris1

M4 Solaris, M4000-4 CPU

Migrate Software Across Different Hardware Platforms (../npomigl/index.htm)

M4 Solaris1,3



M4 Linux4

M4 Linux5


M3 Solaris

M4 Linux


M4 Solaris3

M4 Linux3


Note:

1. Hardware is any supported configuration, except the M4000-4 CPU. 2. The source and target machines are running the same minor release of the NPO software. 3. The source and target machines do not need to run the same minor release of the NPO software. Additional restrictions may apply, though - check the corresponding method for details. 4. NPO redundancy: main machine. 5. NPO redundancy: spare machine.




....................................................................................................................................................................................................................................


7

7 aintenance Backup / M Restore

Overview Purpose

This chapter describes the available backup and restore solutions. Contents Scope

7-1

Policy and scheduling

7-2

Backup/restore solution on Solaris

7-2

Backup/restore solution on Linux

7-4

Scope The NPO platform provides administration services for data backup and restore via tape (or via the network drive). There are two possible backup modes: • •

Manual (the backup executes immediately). Automatic (the backup is executed according to a planned schedule with automatic repetitions (by day, week, month or year periodicity).

In both modes, the backup is done without NPO interruption.



Policy and scheduling

Maintenance Backup / Restore

....................................................................................................................................................................................................................................

Policy and scheduling A backup and restore policy consists of the production of the best NPO image in order to restore the system in any type of disaster scenarios and in the best timing delay. In the case of an Oracle database crash or anomaly, the restoration of the NPO essential data is enough. In the case of a software crash, the complete NPO image (essential and system) becomes useful to avoid the re-installation of the whole NPO application. The restore time is approximately twice as long as the backup.

Backup/restore solution on Solaris This section describes the following backup/restore tasks performed for NPO data and application backup: •

NPO data backup on tape with Oracle Secure Backup (OSB), an additional software delivered by Alcatel-Lucent

•

NPO data backup on local disk.

•

NPO application backup.

The following table lists the database backup information. Table 7-1

Database backup table

Method

Supported (non ASM)

M4000-4 ASM

2xV490 ASM

NPO Data Backup/Restore on Tape

YES

NO

NO

NPO Data Backup/Restore on Local Disk

YES

YES

NO

Only if there is enough disk space to support the database export.

The following table lists the application backup information. Table 7-2

Application backup table

Method

Supported (non ASM)

M4000-4 ASM

2xV490 ASM

Application backup via media manager

YES

YES

NO

Note: If stored customer indicators are created, the customer indicator dictionary must be exported. It will be required during the restore.

During the restore procedure, the NPO is not available until the end on the procedure.




....................................................................................................................................................................................................................................

The following recommendations apply: • •

•

One of the backup/restore solutions software must be used. NPO data backup is an online backup so can be performed without stopping the application. But it may impact I/O thus degrading slightly NPO performances. As a consequence, it is not recommended to perform the data backup at the user activity peak. The Incremental Backup is mandatory to be scheduled every day, except on the Full Backup day. The Incremental Backup can be launched only if at least one full backup was performed on the server.

•

Incremental Backup is available only for NPO data backup.

•

Full Backup is scheduled for Sunday at 10:00.

•

Incremental Backup is scheduled from Monday to Saturday at 20:00.

•

•

The restore procedure is performed in order from the last Full Backup until the latest Incremental Backup. Application Backup should be performed every time the software or the hardware configuration is changed.

NPO data backup/restore on tape

The proposed solution is based on the Oracle Secure Backup package. This is supported for legacy SPARC systems only, and it is limited to the tape capacity (800 Gb meaning 10000 cells maximum). NPO data backup is an online backup and can be performed without stopping the application. Incremental backup is also supported. NPO data backup/restore on local disk

The backup is written on the local disk of the NPO main server. There is a command line script to do it. This script can be scheduled via the usual Unix scheduler ( cron). Then, it is possible to save it on any external remote server or external media, using the preferred customer method. Only local disks are supported; using NFS in particular is not supported because of the high bandwidth needed and the wide variation in NFS performance. Incremental backup is also supported. The backups created on disk are available until made obsolete by newer backups. Once a new backup is available older backups are purged. The possibility to create compressed backupsets is offered. The compressed backupsets will be smaller in size, but the time needed to complete the backup is likely to be longer than the time needed to complete a non-compressed backup.




....................................................................................................................................................................................................................................

NPO application backup/restore

The NPO data is not included in the application backup. The NPO data must be backed up using a supported means of backup. The application backup of the NPO machine offers an alternative to an installation from scratch in the case of a disaster. This procedure does not cover the database. Only full backups are possible.

Backup/restore solution on Linux This section describes the following backup/restore tasks performed for NPO data and application backup: •

NPO data backup on disk..

•

NPO application backup.

The following recommendations apply: •

The Incremental Backup is mandatory to be scheduled every day, except on the Full Backup day. The Incremental Backup can be launched only if at least one full backup was performed on the server.

•

Full Backup is scheduled for Sunday at 10:00.

•

Incremental Backup is scheduled from Monday to Saturday at 20:00.

•

Incremental Backup is available only for NPO data backup.

•

•

The restore procedure is performed in order from the last Full Backup until the latest Incremental Backup. Application Backup should be performed every time the software or the hardware configuration is changed.

NPO application backup/restore

The NPO database is not included in the application backup. The NPO data must be backed up using a supported means of backup. The application backup of the NPO machine offers an alternative to an installation from scratch in the case of a disaster. To successfully perform this task, make sure that the free space on /alcatel/backup partition is greater than 30 GB. This procedure does not cover the database. Only full backups are possible. NPO data backup/restore

The NPO data backup and restore solution is complementary to the application backup/restore solution. The NPO data backup creates a backup set of the NPO database (Oracle) and the NPO users (CSA) inside the /alcatel/backup/data directory on a local partition of the Linux NPO machine. The contents of the /alcatel/backup/data directory should be backed up on a separate backup server.




....................................................................................................................................................................................................................................

The backups created on disk are available until made obsolete by newer backups. Once a new backup is available older backups are purged. The possibility to create compressed backupsets is offered. The compressed backupsets will be smaller in size, but the time needed to complete the backup is likely to be longer than the time needed to complete a non-compressed backup.




....................................................................................................................................................................................................................................


8

Client 8

Overview Purpose

This chapter describes the Windows PC client hardware requirements for the NPO. Contents Configuration

8-1

Configuration The following table lists the Windows PC requirements for the NPO application. Base hardware CPU

1 CPU Pentium 4, 2.8 GHz (512 KB cache) or 1 CPU core 2 duo or Core 2 Quad or higher

RAM

2 GB or higher

Hard disk

40 GB disk or higher (At least 1 GB free minimum in C Partition)

Ethernet board

100/1000 Mb/sec Ethernet boards

Software

Operating System

Windows XP (English) Service Pack 2 or 4 or Windows Vista Or Windows 7 (32 bit and 64 bit only for NPO 4.1)

Other Applications

Microsoft Office 2003 NPO M4.1 : Java JRE and JDK 6.0 must also be installed Firefox browser is supported also. The application will run much better on Firefox then Internet Explorer.



Client

Configuration

....................................................................................................................................................................................................................................


9

9 etwork Time N Synchronization

Overview Purpose

This chapter describes the Network Time Synchronization (NTS) functions. Contents Overview

9-1

About NTP functionality

9-2

Compatibility

9-3

Time source selections

9-3

Redundancy and resiliency

9-3

Default behavior of WMS or NPO main server under outage conditions

9-3

Recommended NTP architecture

9-4

Using public time sources over internet

9-4

NTP accuracy and network design requirements

9-5

NTP resource usage considerations

9-5

Overview Proper time synchronization is useful and should be considered mandatory in order to adequately support the requirements for: •

Accounting/billing CDRs

•

Network and fault management

•

Efficient troubleshooting and support

•

Security and audit logs

•

Performance counter correlation.

The Network Time Protocol (NTP) is the main protocol used in the Alcatel-Lucent Wireless OAM network to synchronize the time of day (TOD) on servers and the NEs together. The same level of support is for WMS or NPO. ................................................................................................................................................................................................................................... Alcatel-Lucent – Proprietary 9-1 Use pursuant to applicable agreements


Network Time Synchronization

About NTP functionality

....................................................................................................................................................................................................................................

About NTP functionality The is composed of servers and clients that exchange information about their system time. The NTP is based on client-server and master-slave architecture. The WMS or NPO implementation of the NTP is in Unicast mode (more accurate and secure than broadcast mode) where the NTP client actually initiates the time information exchange. After a NTP client sends a request to the server, the server sends back a time stamped response, along with information such as its accuracy and stratum (see below). The NTP client receives the time response from a NTP server (or servers), and uses the information to calibrate its clock. The NTP client determines how far its clock is off and slowly adjusts its time to line up with that of the NTP servers. Adjustments are based on many time exchanges, and involve filtering and weighting as defined in the protocol. In order to increase accuracy, corrections are applied on the client side to eliminate skewing cause by networking latency. The NTP client estimates travelling time and remote processing time once it receives the packet from the NTP server. NTP algorithms assume that the one-way travelling between the NTP server and client is half of the total round trip delay (minus remote processing time). Given that this assumption is not always 100% accurate, it is generally accepted that as the travel time to and from the server increases, the probability of loss of accuracy increases. In the context of NTP, the stratum is the number of NTP server levels relative to a reference clock that is considered as the most accurate time for a given network. Stratum-1 is considered to be the most accurate level (for example, a GPS type transceiver with an NTP interface). Clients which synchronize on stratum-1 servers are considered stratum-2. Some nodes (such as the WMS or NPO servers which are based on Solaris) can offer both the NTP client and server functionality. Clients using stratum-2 servers become themselves stratum-3 and so on. The higher the stratum number is, the less accurate the synchronization is considered to be. Note that local time zone settings are outside of the scope of the NTP. These settings must be set locally on each device.



Compatibility

....................................................................................................................................................................................................................................

Compatibility NTP version 3 must be deployed as part of the UMTS OAM solution. NTP V3 (RFC 1305) is the most popular version (and the default for most devices). Implementation of NTP usage within the UMTS network is straightforward since support for the NTP already exists on NEs and servers; this includes the RNC. All Solaris based OAM servers also support the NTP, including the WMS or NPO main servers, client server and Unix clients.

Time source selections It is not within the scope of this document to propose recommended vendors or types of Stratum 1 server; however, considering the accuracy requirements, GPS type time servers meet the requirements and are simple to operate/maintain at acceptable cost levels.

Redundancy and resiliency Redundancy is essential in the NTP configuration. The NTP clients (this includes intermediary servers such as the WMS or NPO servers) must connect to at least two lower stratum NTP servers (Primary Main Server or Secondary Main, stratum-1 GPS NTP if available...), and this number can be increased to three or four. The recommendation of having one GPS type NTP server co-located in each ROC (with a minimum total of two available to the WMS or NPO main server) must be considered, specifically when there is local legislation on the accuracy of the timestamps for billing. Following the above recommendations will minimize brief connectivity outages.

Default behavior of WMS or NPO main server under outage conditions In the rare situation of outage of the main server time sources (NTS down, loss of connectivity), the WMS Main Server will continue to distribute the time based on its own internal clock which will still be corrected based on the trend (drift correction) that was established when it was synchronized. This configuration ensures that all devices stay synchronized amongst themselves for logging purposes (security and troubleshooting). Some testing done shows that a Solaris server which was previously synchronized can drift by typically 100 msec per day (with less typical values being around 400 msec/day). This WMS or NPO main server default behavior needs to be weighed against time accuracy requirements for billing. Should the time synchronization requirements for the NEs involved in billing be tight (1 second or less from national standards), it could be considered to change this behavior. Alternate behavior under this situation would be for



Default behavior of WMS or NPO main server under outage conditions

....................................................................................................................................................................................................................................

the main server to stop distributing time when it has lost contact to lower level stratum synchronization sources. Under this situation the NEs will generate alarms for loss of time synchronization.

Recommended NTP architecture It is recommended to use the WMS or NPO Main server as the central point for distributing the time throughout the network. The main advantage of using the main server is that it must have connectivity to all the NEs or EMSs managed by a ROC which require time synchronization. To ensure accurate distribution, the main server must get the time from all the time sources available in the overall wireless network (up to three or four, if possible). This limits the OAM traffic between different operating centres as well as simplifying firewall rule management, since only the WMS or NPO main server would get the time of other servers outside of the NOC.

Using public time sources over internet There is no engineering requirement to have Internet connectivity from the OAM network and this is something that would normally be avoided. Should an Internet public source be used as a time reference, it is recommended to build an intermediary stratum server somewhere off the OAM network (bastion NTP server). Specific attention must be paid to the security of this server. As a minimum, this intermediary server must have peering and remote configuration/monitoring disabled. Standard NTP access control ( ntp.conf file) restricts all NTP communications to the servers involved in the configuration (i.e. the NTP servers on the Internet side and the WMS or NPO main server if this server is the main time distribution point). The optional key and encoding features of NTP could be considered to authenticate the source. NTP time sources available on the Internet normally charge a monthly fee for such services but would offer a guarantied level of accuracy. If guarantied accuracy servers are not used, it would be recommended to use three or four sources off the Internet so that this intermediary time server can take advantage of the rich NTP algorithms to determine if some servers are inaccurate or incorrect. Firewalls should also be used and if these also allow flow control, it should be assumed that the maximum rate is one packet per minute. This may offer some protection from denial of service attacks.



NTP accuracy and network design requirements

....................................................................................................................................................................................................................................

NTP accuracy and network design requirements A key driver for synchronization accuracy requirement is billing. Typical billing accuracy requirements may vary from one country to another; but are typically of +-1 second from national time standards. It has been demonstrated that the upper bound of typical synchronization error achieved using the NTP in unicast mode is around 50 msec (or 25% of average round trip time in between servers/clients accumulated to stratum-1 source). Note that this is the accuracy of the time at the System/OS level (there can actually be some extra internal delays on a server or an NE in associating a time stamp on an event). This estimate is based on the fact that the actual OAM network design follows two standard engineering guidelines which ensure optimal NTP accuracy: •

Symmetrical transport times in between the server and client

•

Avoid sustained congestion conditions.

With regard to time accuracy convergence, after initially starting the NTP processes, it may take several minutes, or even up to an hour to adjust a system's time to the ultimate degree of accuracy. To avoid long stabilization times, it is possible to perform an initial manual adjustment to the local clock before starting the NTP processes.

NTP resource usage considerations Considering the flow of fault and performance information on the OAM network, NTP communication is negligible. CPU resource consumption of NTP on Solaris servers is also negligible. Requirements on local time zone settings

Local time zone settings are outside of the scope of the NTP. The NTP only synchronizes time at a lower level (similar to GMT or UTC). Regional time specificities such as time zones and daylight savings time (DST) are normally set on each node, NE or server. Wireless network nodes as well as the WMS or NPO components deal with time zone in different manner, by sending different levels of information. Because of this, the following recommendations and requirements are made in order to simplify network management. Note that the network management function is normally facilitated when time stamps related to events can easily be correlated together. Preferred recommendations

The time settings on all NEs, OAM servers and clients must be identical (all set to UTC, or all set to a single time zone). Note that having the clients set to a different time zone than that of the OAM server can be a source of unsupported issues relative to the accurate display of time in alarms and in reports.



NTP resource usage considerations

....................................................................................................................................................................................................................................

Alternative proposal

The following alternative proposal takes into account important considerations which are required when NEs are already integrated into a billing system. In all cases, the CDR's time information is always based on local NE time. Impacts on changing the time or time zone on the NEs need to be adequately assessed. If the time or time zone is changed, this could require corrective measures at the billing system level. In addition to the legal aspects of time stamp accuracy requirements in billing, subscribers may require exact time stamps if they are used to listing events on their bills. Billing considerations may negatively impact following the recommendations in this document. In such a situation, an alternative to the preferred recommendations would be to keep some NEs set to their actual time zones (i.e. actual local times are set on NEs spawning in multiple time zones). This alternative proposal is not the preferred one from an operational point of view given that the correlation of time related information will be more complex. When no impacts are identified to billing, the preferred time zone recommendations (NEs and OAM system set to a single time zone) must be followed. The following recommendations and notes apply to this alternative: •

• •

UMTS Access networks do not generate billing CDRs. Therefore, they must follow the preferred time zone recommendations (homogeneous single time zone setting). Given that UMTS Access RNC and NODE B deal with time offsets in very different manners, any deviation from this recommendation for UMTS access network will create inconsistent time stamp information and will complicate network management. The WMS or NPO Client must be set to the same time zone as the OAM servers. The consequences of choosing this alternate strategy is that correlation of time information of nodes in different time zones will be not be as straightforward as when they are all in the same time zone.


10

Remote NPO Installation 10

Overview Purpose

This chapter is a general overview on the possibility of Linux NPO remote installation using Integrated Lights-Out interface (ILO). This feature is available on HP servers. Contents Remote installation using ILO

10-1

Remote installation using ILO Remote installation is useful and should be used when operator has no direct access to the HP Linux server. It applies for these situations: •

Server installation of Linux NPO main

•

Server installation of Linux AUX

•

Software Replacement of Linux NPO main

•

Software Replacement of Linux AUX server

For details on how to remotely install NPO main and AUX servers please follow the procedures: •

Install HP and Sun X4170 Servers from DVDs

•

NPO Install Auxiliary Servers

•

NPO Software Replacement on Linux

•

NPO Software Replacement on Auxiliary Servers



Engineering Guide 1

Recommend Documents