ono100410 imanager nastar v600r010 system overview issue1.10

www.huawei.com

Copyright © 2012 Huawei Technologies Co., Ltd. All rights reserved.

iManager Nastar V600R010 System Overview


Contents1. Introduction2. Architecture3. Typical Configurations4. Technical Specifications

Page3


Background Traditional network analysis methods:

Monitoring alarm information Analyzing performance reports

Nastar obtains the following data and analyze them: Measurement reports of radio links Pilot frequency measurement strength indicator Neighboring cell measurement data Uplink interference data User call history records

Page4


Position of Nastar in the Network

Page5

GSM BSC wi th SAU

CDMA BSC wi th SAU

UMTS RNC wi th SAU

LTE

M2000 Nastar server

Nastar cl i ent

The Nastar server, eSAU, LTE SAU, and M2000/ OMC must be i n the same l ocal area network (LAN), and thei r I P addresses must be on the same network segment.

SAU pre-processes the data and sends them to M2000.

TD-SCDMA RNC wi th SAU


Functions of Nastar Coverage analysis (also called MR analysis in the GSM network) Neighboring cell analysis Uplink interference analysis Frequency analysis Pilot pollution analysis Network geographic observation Cell performance analysis Cell fault analysis Service analysis - PS service resource analysis Service analysis - network geographic observation Complaint analysis support VIP analysis Terminal performance analysis

Page6


Application Scenarios Network planning and optimization

Nastar can be used to analyze coverage, neighboring cells, frequencies, uplink interference and etc. to locate network problems.

Network operation Nastar can be used to analyze subscriber complaints,

and thus facilitates network problem handling. It also analyzes VIP KPIs, and thus helps to monitor the network quality of VIPs and improves customer satisfaction.

Page9



Page10


Hardware Architecture

Page11

HP DL 580 HP DL 980

ATAE cluster


Software Architecture

Page12



Page13


Contents3. Typical Configurations

3.1 Overview of Configuration Scenarios3.2 Typical Configurations of the Nastar System (ATAE)3.3 Typical Configurations of the Nastar System (PC

Server)3.4 Configuration Requirements of Nastar Client

Page14


Equivalent NE

Page15

Equivalent NEs RAN

GSM UMTS LTE

1 equivalent NE 125 TRXs 62.5 cells 20 eNodeBs

100 equivalent NEs

12,500 TRXs

6,250 cells 2,000 eNodeBs

400 equivalent NEs

50,000 TRXs

25,000 cells

-

800 equivalent NEs

100,000 TRXs

50,000 cells

-

Maximum specification in a single system

100,000 TRXs (800 equivalent NEs)

50,000 cells (800 equivalent NEs)

2,000 eNodeBs (100 equivalent NEs)


Deployment scenarios of the Nastar system

Page16

Existing Scenarios

Deployment of Nastar V600R010

M2000 forms

Nastar Not adding new services

Adding new services

SUN Not deployed

ATAEThe Nastar and the eSAU are deployed in an independent cabinet.

ATAE Not deployed

ATAE •In the case of a large network (800 equivalent NEs), the Nastar and the eSAU are deployed in an independent cabinet. •In the case of a small network (400 equivalent NEs), the Nastar and the eSAU are deployed in the existing M2000 cabinet.

SUN Deployed on the PC Server

The Nastar and the eSAU are deployed on the existing PC Server.

ATAE The Nastar and the eSAU are deployed in an independent cabinet.

ATAE Deployed on the PC Server

The Nastar and the eSAU are deployed on the existing PC Server.

ATAE •In the case of a large network (800 equivalent NEs), the Nastar and the eSAU are deployed in an independent cabinet. •In the case of a small network (400 equivalent NEs), the Nastar and the eSAU are deployed in the existing M2000 cabinet.


Contents3. Configurations

3.1 Overview of Configuration Scenarios3.2 Typical Configurations of the Nastar System

(ATAE)3.3 Typical Configurations of the Nastar System (PC

Server)3.4 Configuration Requirements of Nastar Client

Page17


Configuration Strategies for Different Network Scales

Page18

Network Scale Server Hardware Configuration

400 equivalent NEs

Nastar blade *3Pcs: two service blades (one master blade and one standby blade) and one database blade eSAU blade *4Pcs: Two service blades (one master blade and one standby blade) and two database blades LTE SAU blade *1Pcs: one master service blade NOTE: The Nastar and eSAU share one service blade.

800 equivalent NEs

Nastar blade *4Pcs: three service blades (one master blade, one slave blade, and one standby blade) and one database bladeeSAU blade *7Pcs: three service blades (two master blades and one standby blade) and four database blades LTE SAU blade *1Pcs: one master service blade NOTE: The Nastar and eSAU share one service blade.


Typical Configurations of the Server 400 Equivalent Nes

The 28 blades in the ATAE subracks can be deployed in multiple systems at the same time, such as the Nastar, the eSAU, and the LTE SAU, to manage the systems in a centralized manner.

800 Equivalent Nes The 56 blades in the ATAE subracks can be deployed in

multiple systems at the same time, such as the Nastar, the eSAU, and the LTE SAU, to manage the systems in a centralized manner.

Page19



3.1 Overview of Configuration Scenarios3.2 Typical Configurations of the Nastar System

(ATAE)3.3 Typical Configurations of the Nastar System (PC

Server)3.4 Typical Software Configuration of Nastar System

Page21


Typical hardware configurations of the Nastar (PC Server)

Scene Configuration Object Configuration Requirement

400 equivalent NEs

Nastar server (HP DL580)

Server type: HP DL580G7 CPU: 4 x 2.0GHz E7-4820 or above (eight-core) Memory: 8 x 4 GB Hard disk: 8 x 300 GB (RAID 5 + hotspare) Tape drive: HP LTO4 SAS card: 1 Integrated NIC (four ports) Accessories: DVD

800 equivalent NEs

Nastar server (HP DL980)

Server type: HP DL980G7 CPU: 8 x 1.86GHz E7-4807 (six-core) Memory: 16 x 4 GB Hard disk: 2 x 300 GB (RAID 1+0) S2600 Storage Array (12 x 600 GB) + D120S Disk Management Enclosure (12 x 600 GB) (RAID1+0 + hotspare) Tape drive: 1 x HP LTO4 NIC: Integrated NIC (four ports) + 1000 M NIC (four ports) 1Port 8Gb Fibre HBA: 2 SAS card: 1 Accessories: DVD

Page22




Server)3.4 Typical Software Configuration of Nastar System

Page23


Typical Hardware Configuration of Nastar Server (HP DL580)

object

Configuration requirement

Nastar server

Server type: HP DL580CPU: 4 * Xeon 2.13 GHz (four-core)Memory: 4 * 4GBHard disk: 8 * 300GB (RAID 5)Tape drive: HP LTO4Ethernet adaptor: 2Accessories: DVD

Page24


Ports on the DL580 Server

Page25

Port

Description

eth0 Ethernet port 1 identified on the server. This port is used to connect to the external network.The server obtains required data through this port, and the client logs in to the server through this port.

SAS SAS port. This port is used to connect to a tape drive.The tape drive obtains data from the server and backs up the obtained data through this port.

iLO2 Remote management port.You can use this port to remotely manage the server through the Graphic User Interface (GUI).


Connecting Signal Cables of Servers

Page26


Disk partitioning planning of the server (DL580)

Page27

Hard Disk

Partition Type

Mounting Point

Size Description

6 x 300 GB

Swap partition

Swap 8GB Swap partition

Primary partition

/ 80GB Root partition.

Primary partition

/dev 1GB Partition for the device file data.

Primary partition

/boot 2GB Boot partition.

The remaining hard disk space is the primary or extended partition of the raw Ox8E Linux LVM device that is not initialized.


Host Name and IP Address Planning of Devices(DL580)

Page28

Device

Host Name

Ethernet Port

IP Address

Subnet Mask

Gateway IP Address

Description

Server

nassvr eth0Ethernet port 1 identified on the server

192.168.8.11

255.255.255.0

192.168.8.1

Service IP address of the Nastar (for connecting to the Internet)


Typical Hardware Configuration of Nastar Server (HP DL980)

object

Configuration requirement

Nastar server

•Server type: HP DL980G7 •CPU: 8 x 1.86GHz E7-4807 (six-core) •Memory: 16 x 4GB •Hard disk: 2 x 300 GB •S2600 Storage Array (12 x 450 GB or 12 x 600 GB) + D120S Disk Management Enclosure (12 x 450 GB or 12 x 600 GB) •Tape drive: 1×HP LTO4 •NIC: Integrated NIC (four ports)+ 1000M NIC (four ports) •1Port 8Gb Fibre HBA: 2 •SAS card: 1 •Accessories: DVD

Page29


Ports on the DL980 Server

Page30


Structure of S2600

Page31

S2600-STEZ08S26F-S2600 Disk Array (8*4G FC connetor,4GB Memory,220V AC,12*450G 15K SAS Harddisk,4*10m Optical Fiber)

S2600 Front Panel


Ports on the S2600 Disk Array

Page32

Port DescriptionEthernet Port

Ethernet port. This port is used to connect to the internal network. You can manage disk arrays through this port.

Fiber Fiber port. This is used to connect to the server.MGNT Local management port of disk arrays.

You can manage disk arrays by using the serial cables delivered with the disk arrays through this port.


Connecting Signal Cables(DL980)

Page33


Connecting the Network Cables Within the Cabinet(DL980)

Page34


Disk Partition Planning of the Server (DL980)

Page35

No.

Partition Directory

Partition Type

Mounting Point

Size Description

1 /dev/cciss/c0d0p1 Primary partition

/boot 2 GB Boot partition.

/dev/cciss/c0d0p2 Swap partition swap 64 GB Swap partition.

/dev/cciss/c0d0p3 Primary partition

/ 200 GB Root partition.

2 Mirroring disk of the first hard diskStorage Frame Partition Directory

Size Description

•The 22 disks, that is, the disks in slot 0 to slot 11 in the control frame and those in slot 0 to slot 9 on the cascaded frame are configured as RAID 1 + 0. •The disks in slot 10 and slot 11 in the cascaded frame are configured as hot spare.

/dev/sda 700 GB Volume name: oss_v0

/dev/sdb 700 GB Volume name: oss_v1

/dev/sdc 700 GB Volume name: oss_v2

/dev/sdd 700 GB Volume name: oss_v3

/dev/sde 700 GB Volume name: oss_v4

/dev/sdf 700 GB Volume name: oss_v5

Partition planning of the S2600 disk array

Disk partition planning of the server (DL980)


Host Name and IP Address Planning of Devices(DL980)

Page36

Device

Ethernet Port Function

Ethernet Port Name

IP Address Gateway IP Address

Subnet Mask

Host Name

Server Service Ethernet port

Eth0 192.168.8.11 192.168.8.1

255.255.255.0

nassvreth1

Maintenance Ethernet port

eth3 192.168.11.139

192.168.11.1

255.255.255.0

Ethernet port for managing the server remotely

iLO3 Set the IP address, subnet mask, and gateway as required.

Disk array

Ethernet port for maintaining disk arrays

Ethernet port (controller A)

192.168.11.39

192.168.11.1

255.255.255.0

-

Ethernet port (controller B)

192.168.11.40

192.168.11.1

255.255.255.0




Server)3.4 Typical Software Configuration of Nastar

System

Page37


Typical Software Configuration of Nastar

Configuration Object

Configuration Item

Configuration Requirement

Nastar server

Operating system SUSE Linux10 SP3 (X86_64)Database Oracle 11.1.0.7gNastar application software

Nastar system software

Nastar client

Operating system Windows 2000 Professional SP4 or later Windows XP Professional SP1 or laterWindows 7 Professional 64bit

Nastar application software

Nastar client softwareMicrosoft Office 2003 or a later version

Page38



Page39


Management Capability of Nastar

Item Management CapabilityNumber of carriers supported by the Nastar

≤ 400 equivalent NEs (for HP DL580 server)≤ 800 equivalent NEs (for HP DL980 server)≤ 800 equivalent NEs (for ATAE cluster system)

Number of cell groups supported by the Nastar

≤ 100 (for all the types of the server)

Page40

Thank youwww.huawei.com

ono100410 imanager nastar v600r010 system overview issue1.10

Documents