BSC6810 V200R009 Features (O&M Aspect)

7/27/2019 BSC6810 V200R009 Features (O&M Aspect)

http://slidepdf.com/reader/full/bsc6810-v200r009-features-om-aspect 1/47

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved

www.huawei.com

Internal

BSC6810 V200R009

Features (OAM)

BSC6810V200R009




Transmission Backup

IP-Based Transmission over Iub, Iur, and Iu Interfaces

Alarm/Performance Management

DHCP Server

Transmission Resource Management

Bulk Configuration Management

Data Synchronization Between Dual Servers/Security Monitoring




Transmission Backup

Transmission backup is to perform board backup and port backup to ensurereliable transmission. With PIU board backup and port backup enabled, smoothboard or port changeover would happen without interrupting services if any boardor port should fail. The transmission backup feature falls into:

Board backup

E1/T1 port backup

Optical port backup

FE/GE port backup

Load sharing among FE/GE ports




Type of Interface BoardAbbreviation Full Spelling Silkscreen Bar Code

(For Quotation and

Production)

AEUa RNC 32-port ATM over E1/T1/J1 interface Unit

REV: a

AEUa WP11AEUa

AOUa RNC 2-port ATM over channlized Optical STM-

1/OC-3 Interface Unit REV: a

AOUa WP11AOUa

UOIa RNC 4-port ATM/Packet over Unchannlized

Optical STM-1/OC-3c Interface unit REV: a

UOIa WP11UOIa

PEUa RNC 32-port Packet over E1/T1/J1 Interface

Unit REV: a

PEUa WP11PEUa

FG2a RNC packet over electronic 8-port FE or 2-port

GE ethernet Interface unit REV: a

FG2a WP11FG2a

GOUa RNC 2-port packet over Optical GE ethernet

Interface Unit REV: a

GOUa WP11GOUa




Backup of Interface Board

board and port backup binding

Using a Y-shaped E1/T1 cable to

connect the local to the peer

Preventing single-point failures

through board backup

Renegotiating the Inverse Multiplexing

over ATM (IMA) or Point-to-Point

Protocol/Multilink Point-to-Point Protocol

(PPP/MLPPP) link with the peer after a

board changeover

AEU/PEU:

NodeB 1

AEU AEU

NodeB 2

0

7

8

15

16

23

24

31

0

7

8

15

16

23

24

31

Active Standby

Y-shaped E1

Y-shaped E1





board and port backup apart

Supporting optical port backup and performing

an optical port changeover in case of a failure of a

single optical port

AOU boards: Supporting 1:1 backup

UOI boards: Supporting 1:1 and 1+1backup

Optical port backup based on G.841

Operating optical ports in two optional modes:

Synchronous Digital Hierarchy (SDH) and

Synchronous Optical Network (SONET)

UOI/AOU:

NodeB

AOU

1

0

AOU

1

0E1*N

Active Standby

155-Mbit/s optical fiber


http://slidepdf.com/reader/full/bsc6810-v200r009-features-om-aspect 7/47HUAWEI TECHNOLOGIES CO., LTD. All rights reserved


FG2/GOU:



board backup port no backup






Board and port swap together

Transmitting and receiving data on the ports of the active board, processing services on the activeboard, and maintaining the standby board as a mirror backup of the active board

Disallowing port level changeover and load sharing between Ethernet ports

Performing a board changeover without interrupting services in case of a failure of a port

In this mode, Ethernet IP will be used to terminate both control and user plane data, DEVIP can’t beused.

FG2/GOU:

NodeB1

FG2

0FG2

1

23

4

6

5

7

0

1

23

4

6

5

7

NodeB2

Standby Active

Ethernet






Using the logical IP address of the FG2/GOU as the user plane address and control planeaddress

Supporting port backup between active and standby boards and load sharing betweenactive ports

Performing a port changeover from the active to the standby in case of a failure of a singleport

Ensuring both board reliability and transmission reliability

FG2/GOU:

NodeB1

FG2

0FG2

1

23

4

6

5

7

0

1

23

4

6

5

7

NodeB2

IP

Active Standby

Data network





board backup port no backupUsing the logical IP address of the FG2/GOU as the user plane address and control plane address

Disallowing port backup, treating all ports on the standby board as independent entities, andconfiguring independent IP addresses and properties for them

Supporting load sharing and route forwarding on each port on the standby board

Stopping load sharing on the port in case of a failure of a single port and resuming load sharing onthe port after the recovery of the port

FG2/GOU:

NodeB1

FG2

0

FG2

1

2

3

4

6

5

7

0

1

2

3

4

6

5

7

NodeB2

IP

Active Standby




Transmission Backup



DHCP Server







Data flow in the BSC6810 is described in the next page

Please refer to other courses for Detailed configuration

IP-Based Transmission



HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 13

IP data stream processing

GE switch

SCUa

User traffic process board

(DPUb)

IP

MAC

PHY

UoIP

U-plane process

Signaling process board

(SPUa)

IP

MAC

PHY

UoIPSignaling process

Node B/ Cell

management

SCTP

PHY(E1T1,SDH)

PPP

IP

UDP

PHY(FE,GE)

MAC

IP

UDP

PHY(GE)

MAC

IP

UoIP

GTPU GTPU

SCTP Agent SCTP Agent

PIU

PIE FG2/GOU

USER PLANE CONTROL PLANE




Transmission Backup



DHCP ServerTransmission Resource Management



Content




Alarm Management

V200R009 retains the alarm management mechanism of V100RXXX. As compared with

V100RXXX, V200R009 makes some enhancements and meets some additional serviceability

requirements.

The main control board can use the Joint Test Action Group (JTAG) function to detect a

service board. The Multi-Service Access (MUSA) platform can detect a board through a serial

port. V200R009 can recognize more board states than V100RXXX. The JTAG function can

detect whether a board is unplugged. The emulation panel can indicate that the board is not

installed when a board is unplugged. In 100RXXX, however, the emulation panel displayed a

board as faulty no matter whether the board was unplugged or reset.




Alarm Management

The degree of alarm correlation and alarm mask is raised. The alarms associated with the

Signaling ATM Adaptation Layer (SAAL) and SCTP links on an Iub interface are masked. A

SAAL link alarm can result from a UNILNK fault, an IMALNK fault, or a FRAATM fault. A

SCTP link alarm can result from a FE/GE fault or a PPP/MP fault. In V100, tremendous

upper layer alarms are reported to the user interface or other specified nodes in case of an

intermittent lower layer transmission failure. V200R009 masks the upper layer alarms,

freeing you from worrying about the various unnecessary alarms and focusing your attention

on the real alarms. V200R009 prevents the unnecessary alarms from being reported to the

BAM, thus mitigating the burden on the BAM.




Performance Management

In V200R009, the PIU boards collect all transmission link related indexes and upload them to the BAM, and

maintains more transport layer traffic statistics indexes than V100RXXX. It supports:

SDH, IMA, and User Network Interface (UNI) related indexes on the physical layer

ATM Adaptation Layer Type 2 (AAL2) and ATM Adaptation Layer Type 5 (AAL5) related indexes on the ATM layer PPP and MLPPP related indexes on the link layer

User plane and control plane related indexes on the IP layer

BAM PFM

SCUa

FTP

PFM

PIU

VOS

BSP

CFG

Function interface

Message interface




Transmission Backup



DHCP Server







DHCP Server

On an ATM-based Iub interface, the Operation, Administration and Maintenance (OAM)

information is carried on an IPoA channel. The NodeB obtains its IP address and OAM serverand establishes the OAM channel through Bootstrap Protocol (BOOTP). As the BOOTP server,

the RNC uniquely identifies the NodeB through a Permanent Virtual Circuit (PVC). On an IP-

based transmission network, however, a NodeB can obtain its IP address and OAM server and

establishes the OAM channel on the Iub interface through Dynamic Host Configuration Protocol

(DHCP).

DHCP is defined in RFCs 1533, 1534, 1541, and 1542. It reduces the host configurationcomplexity on a TCP/IP network through dynamic IP address assignment. The IP address

assignment is an important part of an IP solution on an IP Radio Access Network (RAN). The IP

addresses can be configured either manually beforehand or automatically. At present, the RAN

devices do not support automatic IP address assignment. They only support static IP address

assignment.

A DHCP server exists on an PIU board. Each PIU needs to assign IP addresses with an infinitelease time to the associated NodeBs. The DHCP server also needs to configure and maintain the

IDs and IP addresses of the NodeBs. The relevant commands include: ADD EMSIP, ADD

NODEBIP, ADD NODEBESN, ADD PPPLNK, ADD ETHIP, ADD MPGRP, and ADD MPLNK.




DHCP Process

Server (RNC) NodeB

DHCP Discover, including the gateway

address

DHCP Offer, including the IP address of

the Iub interface, mask, and serveraddress

DHCP Request, including the obtained IP

address (or the IP address of the Iub

interface) and the options to obtain

DHCP Ack , including the extended

options

DHCP

relay




DHCP Server

The way a DHCP server communicates with a NodeB varies with the port connecting theNodeB to the DHCP server. A NodeB connected to the PIU on a FE port uses its

electronic serial number (ESN) on the main control board as its ID to send a DHCP

request. The PIU then assigns an IP address to the NodeB by the NodeB ESN. For a

NodeB connected to the PIU on a PPP/MP port the DHCP server first looks up the

NodeB by the PPP/MP port. The DHCP server looks up the NodeB by the NodeB ESN if

it fails to find the NodeB by the PPP/MP port.




Transmission Backup



DHCP ServerTransmission Resource Management







Overview of TRM and TRM Improvements over

V100

Admission Policies and Resource Allocation





TRM (Transmission Resource Management):

Transmission Resource Management (TRM) manages the transmission resources for the

Iub, Iur, and Iu interfaces. This include ATM-based and IP-based transmission resources.

TRM performs the following functions:

Managing the physical layer resource as logical transmission resources and

serve the radio layer applications.

Handling resource application, modification, and release for upper layers.

Monitors the usage of the transmission resources in real time and reports any

possible congestion to upper layers for resource scheduling.

Real timely check the QoS status of transmission resources like availability and

transit delay. (for example, by pinging for IP-based transmission resources).

Provides fully distributed resource management.

Overview of TRM – General




TRM is deployed on SPU board.

The TRM modules are synchronized so that the transmission resources of the entireRNC can be shared in a distributed manner.

Overview of TRM – General

TRM 1

TRM 2

TRM N

Upper Layer

1. Resource application, modification, and release

2. Congestion generation and congestion elimination messages

3. Resource fault indication (for example, indication

of a interface board fault)

TRM poolResource related

notification

Physical layer

carrying

transmission

Active detection

O&M

Configuration

and

maintenance




The user plane resources on the Iub, Iur, and Iu-CS interfaces include the AAL2 resourcesfor ATM-based transmission and the User Datagram Protocol (UDP) resources for IP-based transmission.

An AAL2 path is configured by using an MML command. The path type options include:

RT R99, NRT R99, RT HSDPA, NRT HSDPA, RT HSUPA, NRT HSUPA. They

correspond to Constant Bit Rate (CBR), Real Time Variable Bit Rate (RT VBR),

Non-Real Time Variable Bit Rate (NRT VBR), and Unspecified Bit Rate (UBR) PVC

on the lower layer.

An IP path concept is introduced to manage IP transmission resources. An IP path is a

logical path determined by the local and peer IP addresses. It is also configured by using

an MML command. It can be configured with a bandwidth and type. The bandwidth isused for admission control. The type is used for mapping between service and transport

layers. According to actual networking, the RNC can set proper policies and select

proper transmission resources to carry services.

Overview of TRM – AAL2 Path and IP Path




In terms of TRM, V200 shows the following major improvements over V100R008:

QoS path

Adjacent node

Port controller

2-level resource group

Enhancement in mapping between transmission resources and services

Separation of control and resource SPU boards on an Iub interface

Improvements over V100R008




An IP QoS path is an IP path with an IP QoS priority.

ADD IPPATH: PATHT=QOSPATH, VLANFlAG=DISABLE, PATHCHK=DISABLED;

ADD TRMMAP: ITFT=IUB_IUR_IUCS, TRANST=IP, CCHPRIPATH=QOS_IP_AF4,

SRBPRIPATH=QOS_IP_EF;

Improvements over V100R008 – QoS Path




V200R009 uses an adjacent node (ADJNODE) to unifiedly identify all transmission

resources between an RNC and its peer (NodeB, QAAL2 switch, or a peer over an Iur,

Iu-CS, or Iu-PS interface), including ATM and IP resources.

The ADJNODE configuration incorporates the AAL2ADJNODE configuration and

IPNODE configuration designed in V100.

An ADJNODE identifies a logical combination of transmission resources. All

associated AAL2 paths and IP paths must be added to the configured

ADJNODE. No bandwidth capacity or congestion threshold is configured for an ADJNODE. The

bandwidth capacity and congestion threshold of an ADJNODE depends on the

bandwidth capacities and congestion thresholds of the paths on the ADJNODE. ADD ADJNODE: NODET=IUB, TMI=0, FTI=0;

Improvements over V100R008 – Adjacent Node




V200 configures control SPU to physical port. The port can be a UNI, IMA, FRAC, or

ETHER port. When a port is configured, the port controller is specified.

A port controller has a bandwidth, that is, the available user plane bandwidth taking the

bandwidth reserved for the control plane.

ADD PORTCTRLER: CTRLSN=4, CTRLSSN=3;

Improvements over V100R008 – Port Controller




V200 manages and utilizes transmission resources by separating control SPU andresource SPU. The control SPU is responsible for the link setup signaling. The resource

SPU is responsible for managing all resources on a port. The control SPU needs to

apply for resources from the resource SPU. The control SPU and the resource SPU can

be on either the same or different SPU boards.

With respect to TRM, there appear the concepts of control TRM and resource TRM. The

control TRM is responsible for receiving resource applications from upper layers and

selecting the SPU boards to which the resources belong. The resource TRM is

responsible for allocating and recycling all path resources carried on a specific port.

Improvements over V100R008 – Separation of Control SPUand Resource SPU on an Iub Interface




An Iub interface needs to carry different services on multiple PVCs of different types.

They usually share the lower physical layer because the Iub interface is deficient in

transmission resources. This requires ATM overbooking. ATM overbooking allows each

PVC to utilize up to the physical layer bandwidth. To ensure the quality of admitted

services, the sum of the bandwidths allocated to the multiple PVCs for admission control

shall not exceed the physical layer bandwidth. This is the function of group bandwidth

management.

In V200, a resource group is totally a logical concept. It does not correspond to ports.

V200 provides group bandwidth management for two levels of hub NodeBs.

Improvements over V100R008 – 2-Level Resource Group




In V100R008 resource mapping is based on transmission resources.

V200R009 configures primary and secondary paths by service. The following lists some contents of a TRMMAP table.

Improvements over V100R008 – Enhancement in Mapping Between

Transmission Resources and Services





Overview of TRM and TRM Improvements over V100

Admission Policies and Resource Allocation





Admission Policies

In V200R009, the admission policies can vary with scenarios.

Admission by configured bandwidth: All resource applications can be approved if the available bandwidth permit.

Typical application scenarios: common channel setup on an Iub interface, Radio

Resource Control (RRC) connection setup

Admission by reserved handover bandwidth:

The bandwidth to apply for cannot exceed the difference between the available

bandwidth and the reserved handover bandwidth. That is, a certain amount of bandwidth

is reserved for handover.

Typical application scenarios: Radio Access Bearer (RAB) setup and modification on an

Iub interface, F2D, F2H, D2H

Admission by preset congestion threshold:

The bandwidth to apply for cannot exceed the difference between the available

bandwidth and the bandwidth reserved for congestion avoidance. That is, a certain

amount of bandwidth is reserved for congestion avoidance.




Transmission Backup

IP-Based Transmission over Iur, Iur, and Iu Interfaces


DHCP Server







Dynamic Batch Configuration – General

One can execute a configuration script file offline. When switched tothe online mode, the BAM immediately packs all data modificationrecords in a command frame and sends the command frame to theRNC host. The RNC host then puts all the records in the commandframe into effect without affecting services. This is dynamic batchconfiguration.




User

Bam

Send MML Commands

Execute MML commands

Send executing results

SET ONLINE: SRN=ALL, ET=NOW;

RNC Host

Send configuration bin messages

Implement data configuration

Send response messages

Construct bin messages and cache

Send executing result

Dynamic Batch Configuration – Procedure




Select whether to enable Dynamic Batch Configuration when you want to modify allsubracks offline. If you do not enable Dynamic Batch Configuration, the RNC proceeds

as it does in V100. If you enable Dynamic Batch Configuration, the RNC starts the

procedure of Dynamic Batch Configuration.

Dynamic Batch Configuration – Implementation




After the bulk configuration, use the SET ONLINE command to switch to the online mode and

select whether to put the data into effect now.

If you want to put the data into effect later, the RNC proceeds as it does in V100. You can putthe data into effect by resetting the system.

If you put the data into effect now, the BAM generates a command frame of Dynamic BatchConfiguration and sends the command frame to the RNC host. The RNC host then puts allthe records in the command frame into effect without affecting services.

Dynamic Batch Configuration – Implementation




The offline commands cannot be executed in the Dynamic BatchConfiguration mode.

At most 1,000 MML commands can be executed at one time in the DynamicBatch Configuration mode.

The RNC can be set to the offline mode and can implement Dynamic Batch

Configuration only when the data is consistent between the BAM and RNChost. The RNC can be set to the offline mode but cannot implementDynamic Batch Configuration if the data on the BAM is different from that onthe RNC host.

Dynamic Batch Configuration – Points for Attention




Transmission Backup



DHCP Server







Enhancements in Data Synchronization Between Dual Servers

V100 uses the SQL Server replication mechanism to synchronize databetween dual BAM servers. The customer service engineers may have manycomplaints about this method of data synchronization.

It takes a fairly long time of almost 40 minutes to finish the initial datasynchronization. The dual BAM servers have to wait about 40 minutes to swapagain after a swap.

The data synchronization between the dual BAM servers is prone to problemsthat are not readily soluble.

The data synchronization is a very complicated mechanism. Some problemswith data synchronization are even beyond Microsoft's power.

The data synchronization mechanism has many restrictions and is

inconvenient for development. V200 optimizes the mechanism of the data synchronization between dual BAM

servers. In V200, Huawei throws away the SQL Server replication mechanismand uses a self-developed data synchronization mechanism instead.





The standby BAM initiates a data synchronization request.

The active BAM locks the database. It backs up the database in a file. It then unlocks thedatabase and returns an acknowledgement message to the standby BAM. All accesses tothe database are blocked during the lock period. The lock period lasts approximately 15seconds in full RNC configuration. The lock occurs and blocks accesses only when thestandby BAM initiates a data synchronization request. The influence is very small.

After unlocking the database, the active BAM records all accesses to the database in

sequence. The standby BAM uses the File Transfer Protocol (FTP) to obtain the database backup file.

The standby BAM locks the database. It restores the database from the backup file and thenunlocks the database. Up to now, the initial data synchronization ends.

The standby BAM regularly obtains the database operation commands from the active BAMand executes these commands on its own database. In this way, the standby BAM is

synchronized with the active BAM in real time. To prevent data discrepancy, the active and standby BAM servers perform an initial data

synchronization and start a new data synchronization process at 4:00 a.m. every morning.

The initial data synchronization procedures can be viewed by using the STR DATASYNC command.





As a result,

The time required for initial data synchronization is controlled within

two minutes. Test shows that the initial data synchronization consumes

90 seconds in full configuration and less than 60 seconds in initial

configuration.

The real-time synchronization occurs at an interval of one second.

Normally all data modifications are synchronized to the standby BAM

in real time.

The simplified data synchronization process is easy to control.




Enhancements in Security Monitoring

In V100, the Bamservice restarts the server immediately when theSecuritymanager fails. In V200, the Bamservice first attempts torestart the Securitymanager when the Securitymanager fails. TheBamservice restarts the server only when the Securitymanager failsfive times within 30 minutes.

V200 supports soft resetting and hard resetting. The soft resetting

is to reset the BAM software without resetting the server. The hardresetting is to reboot the computer.

V200 allows you to decide whether to reset the active BAM or toreset the standby BAM.



www.huawei.com

Thank You

Documents

BSC6810 V200R009 Features (O&M Aspect)