G TM Iprb&Bipb&Lapd Board Backup Function r1.0

You might also like

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 28

IPRB&BIPB&LAPD Board Backup Function

Target Group: Technical Support Engineers Issued by GU Product Support Dept.

Version Description
Version
R1.0

Date
2011-3-14

Author
Cai Kai

Reviewed by
Liu Guanghua

Revision Record
Null

Reference:
1. ZXG10 BSS IPRB&BIPB&LAPD Board Backup Function Application Guide

Purpose of the course


Introduce the backup function principle of boards Introduce how to perform board backup

Contents

Introduction Technical Description Parameter configuration

Applicable Versions

iBSC V6.20.614C and the later versions all support the board backup function.

Introduction

New boards supporting the backup function:


Configure DSP supporting TDM

BIPBDSP
Both types of DSP can be configured on the same BIPB

BIPB
Configure DSP supporting IP

IPRBDSP

LAPD

perform backup by taking the CPU as the sub-unit

Introduction

IPRBDSP

When the IPRBDSP fails, the related services will be interrupted. Back up related cells and TRXs on the faulty DSP to another IPRB DSP working normally in 20 seconds, thus to make services go on normally.

BIPBDSP

The connection relation has been configured on iOMCR. The underlying platform processes calculation and synchronization of the connection data. Hence, the underlying platform will also be involved to back up both types of boards. Support backup by the sub-unit (DSP) iBSC determines which backup DSPs to be connected when the active ones become faulty. The platform sends the result of connection success to iBSC so that iBSC can update data status and synchronize the data accordingly.

LAPD
The backup principle is the same with that of the BIPBDSP.

Contents

Introduction Technical Description Parameter configuration

Technical Description

Backup function of the BIPB board (BIPBDSP)

Connection relation between PCM timeslots and BIPBDSP timeslots over the Abis interface is configured on the iOMCR. The connection information is saved in the R_CONNNECT table. Calculation and synchronization of the connection information are both completed by the 3G platform database. The backup BIPBDSPs are not available for iOMCR to configure connection relation. It is just used for active/standby changeover of the board. To perform active/standby changeover, the database sub-system of iBSC is in a normal BIPBDSP backup sub-unit table. Select a proper backup BIPBDSP, and then notify the platform to connect the DSP. The backup BIPBDSP is just for temporary use. When the original active DSP is recovered, it should be changed over to work as the active board again.

Technical Description

Backup function of the LAPD board


The platform database is responsible for calculation and synchronization of LAPD connection information. Hence, for the current system architecture, the backup function of the LAPD board is similar to that of the BIPBDSP board. The sub-unit of the LAPD board is CPU, which is different from that of the BIPB board. Each LAPD board is configured with 4 CPUs. When a CPU of the LAPD board fails, the system will change over to the corresponding standby CPU of the LAPD board. For CPU switchover, the sub-units of the active/standby CPU should be in one-to-one correspondence. When the CPU1 working as the active CPU fails, the whole LAPD board cannot run normally. In this case, it is necessary to replace the LAPD board. When the LAPD board works as the interface board, it does not support the back up function.

Technical Description

Backup function of the LAPD board


LAPD LAPD Active LAPD Standby LAPD

CPU1 CMP3 CPU2

CPU1 CMP3 CPU2

CPU3 CMP4 CPU4

CPU3 CMP4 CPU4

Technical Description

IPRB board backup function (IPRBDSP)

Since the correspondence relation between the TRX group and IPRBDSP are dynamically set by the OMP instead of the OMCR, it is unnecessary to specify sub-units for the board backup on OMCR. After active/standby changeover, even if the faulty DSP recovers, it will not change over to work as the active one so as to avoid service interruption. After data synchronization with iBSC, iBSC will dynamically set the correspondence relation between TRX group and IPRBDSP. When a DSP fails, the corresponding TRX group will be allocated to the normal IPRBDSP.

Technical Description

IPRB Board Backup Function (IPRBDSP)


GROUP1 GROUP2 GROUPn TRX1 TRX1 TRX1

TRX2

TRX2

TRX2

TRXi

TRXi

TRXi

Select a DSP DSP dynamically

a DSP since the previous one fails

DSP Re-select

DSP1

DSP2

DSP3

DSPm-2

DSPm-1

DSPm

Contents

Introduction Technical Description Parameter configuration

Parameter Configuration

BIPBDSP changeover related parameter configuration


Configuring BIPB fault detection timer

Configuring auto slave-to-master and time bit map

Time bit map of BIPB sub-unit slave to master: The BIPB sub-unit has performed active/standby changeover. When the previous active one recovers, the system will perform slave to master changeover automatically according to the time bit map. Value range: [0, 23]; By default, the value is 3 (hours).

Parameter Configuration

Slave to master threshold


CS traffic threshold of slave to master (SToMTraffic Thrs_0): Slave to master will not happen under the following condition: 1) For the Gigabit platform, if the number of current CS/PS connections of the sub-unit is greater than SToMTrafficThrs_0/100*496; 2) For 100M platform, if the number of current CS/PS connections of the subunit is greater than SToMTrafficThrs_0/100*240 The threshold is just for version 614cP001) PS traffic threshold of slave to master (SToMTraffic Thrs_1) : Please set the threshold in the same way of setting SToMTraffic Thrs_0.

Parameter Configuration

Backup configuration of the BIPB DSP

Parameter Configuration

Dynamic data management query the active/standby configuration of the BIPB

Parameter Configuration

Dynamic data management BIPBDSP changeover

Parameter Configuration

Configuring parameters for IPRBDSP switchover


Configuring TRX group

Configuring a timer for BIPB fault detection

Parameter Configuration

Adjust the TRX group to the designed DSP TRX group IPRBDSP query

Parameter Configuration

Parameter configuration related to LPAD changeover


Board configuration

Parameter Configuration

Parameter configuration about LPAD changeover


LAPD changeover related timers

Set the backup function

Parameter Configuration

LPAD CPU manual changeover

Parameter Configuration

Query the active/standby status of the LPAD CPU

Parameter Configuration

BIPB: please configure the backup DSP manually. If possible, please add a BIPB board in the same subrack for the backup board. If there is no slot available, please set an idle DSP as the backup DSP. LAPD: One CPU supports 128 links with the backup function (it supports 64 links previously). The backup board can be not configured in the neighbor slot, but should be in the same subrack. There should be no more than 32 sites and 128 links configured on each CPU. IPRB: 1. For version 614, a DSP can support 28 TRXs under the Gigabit platform, and 16 TRXs under the 100M platform. 2. For version 615, , a DSP can support 35 TRXs under the Gigabit platform, and 16 TRXs under the 100M platform. 3. One TRX group corresponds with one DSP. The number of TRXs included in each TRX group should be configured manually to balance it within TRX groups. 4. Supports cross-subrack IPRB board backup function

Review

For iBSC V6.20.614C and its later versions, which boards support the backup function? For different versions of IPRBDSP, how many TRXs can be supported by each DSP under the Gigabit platform and the 100M platform respectively?

You might also like