Base Station OMCH Self-Recovery (SRAN9.0 - 01)

SingRAN
Base Station OMCH Self-recovery

Feature Parameter Description
Issue
01
Date
2014-04-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2014-04-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
SingRAN
Base Station OMCH Self-recovery Feature Parameter
Description
Contents
Contents
1 About This Document..................................................................................................................1
1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
1.4 Differences Between Base Station Types.......................................................................................................................2
2 Overview.........................................................................................................................................3
2.1 Introduction....................................................................................................................................................................3
2.2 Benefits...........................................................................................................................................................................3
3 Automatic Version Rollback.......................................................................................................4

4 Automatic Configuration Data Rollback..................................................................................5
5 Transmission Link Fault Rectification......................................................................................8
6 Related Features.............................................................................................................................9
7 Network Impact...........................................................................................................................10
8 Engineering Guidelines.............................................................................................................11
8.1 Engineering Guidelines for Automatic Version Rollback............................................................................................11
8.2 Engineering Guidelines for Automatic Configuration Data Rollback.........................................................................11
8.2.1 When to Use Automatic Configuration Data Rollback.............................................................................................11
8.2.2 Required Information................................................................................................................................................11
8.2.3 Planning.....................................................................................................................................................................12
8.2.4 Deployment...............................................................................................................................................................12
8.2.5 Performance Monitoring............................................................................................................................................14
8.2.6 Parameter Optimization.............................................................................................................................................14
8.2.7 Troubleshooting.........................................................................................................................................................14
8.3 Engineering Guidelines for Transmission Link Fault Rectification.............................................................................14
8.3.1 When to Use Transmission Link Fault Rectification................................................................................................14
8.3.2 Required Information................................................................................................................................................14
8.3.3 Planning.....................................................................................................................................................................14
8.3.4 Deployment...............................................................................................................................................................14
8.3.5 Performance Monitoring............................................................................................................................................18
8.3.6 Parameter Optimization.............................................................................................................................................18
Issue 01 (2014-04-30)

ii
SingRAN
Description
Contents
8.3.7 Troubleshooting.........................................................................................................................................................18
9 Parameters.....................................................................................................................................19
10 Counters......................................................................................................................................20
11 Glossary.......................................................................................................................................21
12 Reference Documents...............................................................................................................22
Issue 01 (2014-04-30)

iii
SingRAN
Description
1 About This Document
About This Document
1.1 Scope
This document describes the Base Station OMCH Self-recovery feature. It consists of three
functions: automatic version rollback, automatic configuration data rollback, and transmission
link fault rectification.
1.2 Intended Audience

This document is intended for personnel who:
l
Need to understand the features described herein.
Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l
Feature change
Changes in features of a specific product version
Editorial change
Changes in wording or addition of information that was not described in the earlier version
SRAN9.0 01 (2014-04-30)
This issue includes the following changes.
Issue 01 (2014-04-30)
Change Type
Change Description
Parameter Change
Feature change
None
None

SingRAN
Description
1 About This Document
Change Type
Change Description
Parameter Change
Editorial change
Revised the following sections:
None
l 3 Automatic Version
Rollback
l 4 Automatic Configuration
Data Rollback
l 8.2 Engineering Guidelines
for Automatic
Configuration Data
Rollback
SRAN9.0 Draft A (2014-01-20)

This document is created for SRAN9.0.
1.4 Differences Between Base Station Types

The features described in this document are implemented in the same way on micro, macro, and
LampSite base stations.
Issue 01 (2014-04-30)

SingRAN
Description
2 Overview
Overview
2.1 Introduction
The OM channel (OMCH for short) of base stations refers to the channel through which the
eGBTS/NodeB/eNodeB communicates with the U2000 or the GBTS communicates with the
BSC to exchange the operation and maintenance information about base stations.
If an OMCH interruption occurs, measures are taken remotely to recover the OMCH. These
recovery measures include the following:
l
Automatic version rollback
Automatic configuration data rollback
Transmission link fault rectification
2.2 Benefits
If an OMCH interruption occurs, the Base Station OMCH Self-recovery feature reduces the need
of onsite handling and thereby, saving costs and shortening the interruption time.
Issue 01 (2014-04-30)

SingRAN
Description
3 Automatic Version Rollback
Automatic Version Rollback
The automatic version rollback function is not under switch control and is enabled by default.
The working principles of this function for an eGBTS/NodeB/eNodeB are different from that
for a GBTS. The details are described in the following sections.
Automatic Version Rollback for eGBTS/NodeB/eNodeB

After the software versions of NEs are upgraded, the NEs will be reset. After the NEs are
restarted, if one of the following faults occurs, their software versions will be rolled back to the
source version and ALM-26255 Automatic Version Rollback will be reported:
l
The NEs detect that the current version fails to be initialized.
The NEs detect that the OMCH of the current version has not been successfully connected
and the interruption lasts 30 minutes.
After the hot patch of an NE software version takes effect, if one of the following faults occurs,
the hot patch will be rolled back to the original state and ALM-26255 Automatic Version
Rollback will be reported:
l
The base station abnormally resets within ten minutes after the hot patch is activated
The OMCH is continuously disconnected within ten minutes after the hot patch is activated
and then the base station resets before the OMCH recovery (for example, the transmission
link fault rectification function is triggered).
Automatic Version Rollback for GBTS

After a version upgrade, if the NE resets after running for less than five minutes and this
phenomenon occurs thrice, the software version will be automatically rolled back to the source
version and ALM-26255 Automatic Version Rollback will be reported.
The GBTS does not support the automatic version rollback of hot patch.
Issue 01 (2014-04-30)

SingRAN
Description
4 Automatic Configuration Data Rollback
Automatic Configuration Data Rollback
Automatic Configuration Data Rollback for eGBTS/NodeB/eNodeB

If you are concerned that data modification may cause long OMCH interruptions and recovery
failures (for example, when the IP address, router, or IPsec address is incorrectly modified), you
can enable the automatic configuration data rollback function before modifying the data related
to the OMCH. This function can roll back the configuration data, which reduces the need for
site visits.
NOTE
Users are not advised to enable this function when locally modifying the data related to the OMCH.
Otherwise, the automatic configuration data rollback function may be triggered as a result of an OMCH
interruption.
To enable this function, run the MML command CFM CB to set AUTORBKSW to ENABLE
(Enable) and specify the RBKTIME and RBKCONDITION parameters.
When the automatic configuration data rollback is being enabled, the system backs up the current
configuration data and then the timer specified by RBKTIME starts. The data modification must
have been completed before the timer expires. If an OMCH interruption occurs after the timer
expires, the automatic configuration data rollback function cannot be triggered.
For the existing configuration baseline (CB), you can also run the MML command MOD CB
to enable the automatic configuration data rollback function. If the configuration cannot be
completed before the period of time specified by RBKTIME expires, run the MML command
MOD CB to reconfigure the rollback parameters. If AUTORBKSW is set to ENABLE
(Enable) and the RBKTIME parameteris reconfigured, the system will restart the timing(you
can run the MML command DSP CB to query the remaining rollback time).
l
The period of time specified by RBKTIME has not expired.

If the OMCH is normal after its configuration data is modified or recovers to the normal
state after an interruption, and users do not require rollback in spite of an OMCH
interruption, run the MML command MOD CB to disable the automatic configuration data
rollback function. This prevents the rollback of the configuration data in the case of an
OMCH interruption.
Issue 01 (2014-04-30)

SingRAN
Description
NOTE
Incorrect modification of certain data will not lead to immediate OMCH interruption. The OMCH
interruption occurs only after renegotiation with the peer NE about the modified data. Such data includes
parameters in IPSECPROPOSAL, IKEPROPOSAL, and IKECFG MOs. Configuration of these
parameters must be consistent with that on the peer NE.
Before the period of time specified by RBKTIME expires, if the base station resets and related
conditions are met, the automatic configuration data rollback function still takes effect after the
reset.
l
The period of time specified by RBKTIME expires.

If rollback conditions specified by the parameter RBKCONDITION are met, the base
station resets, data configuration is rolled back to the corresponding CB used to enable
this function, and ALM-26255 Automatic Version Rollback alarm is reported. The
system will automatically disable this function after the rollback is complete.
NOTE
The OMCH is considered faulty when it is interrupted for five consecutive minutes.
If the rollback conditions are not met, the system waits five minutes before making a
decision again. The remaining rollback time is five minutes and the timing restarts. After
the five minutes expire,
- If rollback conditions specified by the parameter RBKCONDITION are met, the base
station resets, data configuration is rolled back to the corresponding CB used to enable
this function. If the rollback succeeds, the base station disables this function.
- If rollback conditions are not met (for example, the OMCH is normal or has recovered
to the normal state), the base station disables this function.
If the RBKCONDITION parameter is set to OMCH_AND_SERVICE_FAULT
(OMCH_AND_SERVICE_FAULT), the automatic configuration data rollback
function will be triggered only when the OMCH and all service channels are faulty.
NOTE
If ALM-26255 Automatic Version Rollback is reported with the value of alarm cause being Configuration
Data, this alarm is triggered by the automatic configuration data rollback function.
When this function is enabled on a batch of base stations, the external transmission link for some base
stations may be continuously interrupted. If rollback conditions are met when the timer specifying the
rollback time expires expires, the automatic configuration data rollback function will be triggered for these
base stations.When an OMCH interruption is caused by the batch configuration of base stations, if the
U2000 does not finish the configuration after the period of time specified by RBKTIME expires. This
function is triggered only after the batch configuration is finished, if rollback conditions specified by
RBKCONDITION are still met.
When users run the ADD BRD command to add a board during the batch configuration of base stations,
the board may be automatically activated. If the timer specifying the rollback time expires, but the board
has not been activated, the system will determine whether to trigger the automatic configuration data
rollback function based on the rollback conditions after the board has been activated.
If the automatic configuration data rollback function is manually or automatically disabled, users
need to reconfigure the automatic configuration data rollback function if they want to enable
this function.
When the configuration data of base stations is being modified, the configuration data of
peripheral NEs may also be modified. After the automatic configuration data rollback function
is successfully triggered, the configuration data of base stations is rolled back. Meanwhile, the
data of peripheral NEs may also need to be rolled back to ensure a normal OMCH. Therefore,
Issue 01 (2014-04-30)

SingRAN
Description
the data modification of peripheral NEs during this period and the rollback methods must be
obtained.
Automatic Configuration Data Rollback for GBTS

The GBTS does not support the automatic configuration data rollback function.
Issue 01 (2014-04-30)

SingRAN
Description
5 Transmission Link Fault Rectification
Transmission Link Fault Rectification
The working principles of the transmission link fault rectification function for an eGBTS/NodeB/
eNodeB are different from that for a GBTS. The details are described in the following sections.
Transmission Link Fault Rectification for eGBTS/NodeB/eNodeB

This function enables the base station to initiate a warm reset when an OMCH interruption and
service interruption occur. The reset helps resolve certain issues and avoids onsite handling.
To enable the transmission link fault rectification function, run the MML command SET
TLFRSWITCH with TLFRSWITCH set to ENABLE(Enable). If the base station cannot be
maintained due to OMCH interruption and services are interrupted for 45 minutes, the base
station automatically resets to rectify the fault. If the fault persists, the base station attempts to
rectify the fault in the same way after the service interruption lasts 480 minutes.
NOTE
Run the LST TLFRSWITCH command to query the value of TLFRSWITCH.
Transmission Link Fault Rectification for GBTS

After the OMCH between the GBTS and BSC is interrupted for 15 minutes, the base station
initiates a warm reset to recover the faults and avoids onsite handling.
This function is not under switch control and is enabled by default.
Issue 01 (2014-04-30)

SingRAN
Description
6 Related Features
Related Features
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None
Issue 01 (2014-04-30)

SingRAN
Description
7 Network Impact
Network Impact
System Capacity
None
Network Performance
None
Issue 01 (2014-04-30)

10
SingRAN
Description
8 Engineering Guidelines
Engineering Guidelines
8.1 Engineering Guidelines for Automatic Version Rollback

The automatic version rollback function is enabled by default and does not need to be configured.
NOTE
After the system triggers the automatic version rollback function, ALM-26255 Automatic Version Rollback
will be reported.
8.2 Engineering Guidelines for Automatic Configuration

Data Rollback
The GBTS does not support the automatic configuration data rollback function.
The following sections describe the engineering guidelines for this function on an eGBTS/
NodeB/eNodeB.
8.2.1 When to Use Automatic Configuration Data Rollback

Modifying the radio configuration parameters does not lead to OMCH interruption, so the
automatic configuration data rollback function does not need to be enabled.
However, modifying the configuration data related to OMCH may cause continuous OMCH
interruption, which cannot be remotely recovered. You are advised to enable the automatic
configuration data rollback function in this scenario.
Users are not advised to enable this function when locally modifying the data related to the
OMCH. Otherwise, the automatic configuration data rollback function may be triggered as a
result of an OMCH interruption.
8.2.2 Required Information

Each time before enabling the automatic configuration data rollback function, users must collect
the modified data of peripheral NEs and corresponding rollback methods.
Issue 01 (2014-04-30)

11
SingRAN
Description
8.2.3 Planning
None
8.2.4 Deployment
Requirements
None
Data Preparation
MO
Parameter Name
Parameter ID
Setting Notes
Automatic
Rollback Switch
AUTORBKS
W
In scenarios where only the radio

configuration parameters are modified, set
this switch to off.
Set this switch to on when modifying the
configuration data of base stations because
it may cause continuous OMCH
interruptions and recovery failures.
Rollback Time
RBKTIME
Users should estimate in advance the

required time for modifying the
configuration in order to set appropriate
rollback time. If this parameter is set to 30
minutes according to your estimation, the
modification must be completed within 30
minutes. Otherwise, if an OMCH
interruption occurs after the period of time
expires, the automatic configuration data
rollback function cannot be triggered.
Set the value of this parameter based on the
actual situations.
If this parameter is set to a too large value,
the OMCH may be interrupted for a long
time (services may also be interrupted for
a long time). If this parameter is set to a too
small value, the automatic configuration
data rollback function cannot take much
effect in data protection.
Assume that this parameter is set to 240
minutes. If users incorrectly configure a
parameter 20 minutes after this function is
enabled and the OMCH and services are
interrupted, the system will wait 220
minutes before triggering this function.
Such a long interruption affects user
experiences.
Issue 01 (2014-04-30)

12
SingRAN
Description
MO
Parameter Name
Parameter ID
Setting Notes
Rollback
Condition
RBKCONDI
TION
Set this parameter to OMCH_FAULT

(OMCH_FAULT) in most cases.
If this parameter is set to
OMCH_AND_SERVICE_FAULT
(OMCH_AND_SERVICE_FAULT),
the automatic configuration data rollback
function will be triggered after the time
specified by RBKTIME expires only
when the OMCH and all service channels
are faulty. If an OMCH interruption occurs
while services are normal, the automatic
configuration data rollback function will
not be triggered.
Activation
Using MML Commands
Run the MML command CFM CB or MOD CB to set the Automatic Rollback Switch,
Rollback Time, and Rollback Condition parameters.
MML Command Examples

CFM CB: MODE=UNFORCED, NAME="Rollback CB 1", COMMENT="CB for Rollback", AUTORBKSW
= ENABLE, RBKTIME=30, RBKCONDITION=OMCH_FAULT;
MOD CB: NAME="Rollback CB 1", COMMENT="CB for Rollback", AUTORBKSW = ENABLE,
RBKTIME=30, RBKCONDITION=OMCH_FAULT;
Using the CME

You cannot use the CME to configure this function.
Activation Observation
Run the MML command DSP CB to query the value of Automatic Rollback Switch. If this
parameter is set to ENABLE(Enable), the automatic configuration data rollback function is
enabled.
Deactivation
Using MML Commands
Run the MML command MOD CB to set the Automatic Rollback Switch parameter to
DISABLE(Disable).

MOD CB:
Issue 01 (2014-04-30)
NAME="Rollback CB 1", COMMENT="CB
for Rollback", AUTORBKSW = DISABLE;

13
SingRAN
Description
Using the CME

You cannot use the CME to configure this function.
8.2.5 Performance Monitoring

None
8.2.6 Parameter Optimization

None
8.2.7 Troubleshooting
None
8.3 Engineering Guidelines for Transmission Link Fault

Rectification
The transmission link fault rectification function is enabled by default on a GBTS and does not
need to be configured.
The following sections describe the engineering guidelines for this function on an eGBTS/
NodeB/eNodeB.
8.3.1 When to Use Transmission Link Fault Rectification

It is recommended that the transmission link fault rectification function be enabled.
8.3.2 Required Information

None
8.3.3 Planning
None
8.3.4 Deployment
Requirements
None
Issue 01 (2014-04-30)

14
SingRAN
Description
Data Preparation
MO
Parameter
Name
Parameter ID
Setting Notes
TLFR
SWIT
CH
Transmission Link
Fault Recover
Switch
TLFRSWITC
H
Set this parameter to ENABLE(Enable).
Activation
Using MML Commands
Run the MML command SET TLFRSWITCH to set the Transmission Link Fault Recover
Switch parameter to ENABLE(Enable).

SET TLFRSWITCH: TLFRSWITCH=ENABLE;
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the Data Preparation section. For instructions on how
to perform the CME single configuration, see CME Single Configuration Operation Guide.
Using the CME to Perform Batch Configuration for Newly Deployed Base Stations
Enter the data listed in Table 8-1 in a summary data file, which also contains other data for the
new base stations to be deployed. Then, import the summary data file into the CME for batch
configuration.
Prepare the summary data file as follows:
l
The managed objects (MOs) in Table 8-1are contained in a scenario-specific summary data
file. In this situation, set the parameters in the MOs, and then verify and save the file.
Some MOs in Table 8-1 are not contained in a scenario-specific summary data file. In this
situation, customize a summary data file to include the MOs before you can set the
parameters.
Table 8-1 Parameters related to the transmission link fault rectification function
Issue 01 (2014-04-30)
MO
Sheet in the
Summary Data
File
Parameter Group
Remarks
TLFRSWITCH
User-defined sheet
TLFRSWITCH
Set this parameter

to ENABLE
(Enable).

15
SingRAN
Description
For detailed instructions, see the following sections in 3900 Series Base Station Initial
Configuration Guide.
l
For the NodeB, see section "Creating NodeB in Batches."
For the eNodeB, see section "Creating eNodeB in Batches."
For separate-MPT multimode base stations, see section "Creating Separate-MPT

Multimode Base Stations in Batches."
For an eGBTS or a co-MPT base stations, see section "Creating Co-MPT Base Stations in
Batches."
NOTE
eGBTS refers to a base station deployed with UMPT_G.

NodeBs refer to base stations configured with the WMPT or UMPT_U.
eNodeBs refer to base stations configured with LMPT or UMPT_L.
Co-MPT base stations refer to base stations configured with UMPT_GU, UMPT_GL, UMPT_UL, or
UMPT_GUL. Such base stations incorporate functions of the eGBTS, NodeB, and eNodeB.
Separate-MPT multimode base stations refer to base stations where multiple modes are deployed on
different main control boards. For example, base stations configured with the GTMU and WMPT are named
separate-MPT GU dual-mode base stations.
Using the CME to Perform Batch Configuration for Existing Base Stations
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing base stations. This method reconfigures all data, except neighbor relationships.
Step 1 Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose
Advanced > Customize Summary Data File (CME client mode), to customize a summary data
file for batch configuration.
NOTE
For context-sensitive help on a current task in the client, press F1.
Step 2 Export the NE data saved on the CME to the customized summary data file. The CME menus
for co-MPT and separate-MPT base stations are different from that for single-mode base stations.
1.
For a co-MPT base station, choose CME > SRAN Application > MBTS Application >
Export Data > Export Base Station Summary Data (U2000 client mode) or CME >
SRAN Application > MBTS Application > Export Data > Export Base Station
Summary Data (CME client mode), to export the NE data stored on the CME into the
customized summary data file.
2.
For a separate-MPT multimode base station or a single-mode GSM base station, choose
CME > GSM Application > Export Data > Export eGBTS Bulk Configuration Data
(U2000 client mode), or choose GSM Application > Export Data > Export eGBTS Bulk
Configuration Data (CME client mode), to export the eGBTS data stored on the CME
into the customized summary data file.
3.
For a separate-MPT multimode base station or a single-mode UMTS base station, choose
CME > UMTS Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose UMTS Application > Export Data > Export Base
Station Bulk Configuration Data (CME client mode), to export the UMTS data stored
on the CME into the customized summary data file.
4.
For a separate-MPT multimode base station or a single-mode LTE base station, choose
CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Issue 01 (2014-04-30)

16
SingRAN
Description
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base
Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored
on the CME into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 8-1 and close the file.
Step 4 Import the summary data file into the CME. The CME menus for co-MPT and separate-MPT
base stations are different from that for single-mode base stations.
1.
For a co-MPT base station, choose CME > SRAN Application > MBTS Application >
Import Data > Import Base Station Summary Data (U2000 client mode) or CME >
SRAN Application > MBTS Application > Import Data > Import Base Station
Summary Data (CME client mode) to import the summary data file into the CME.
2.
For a separate-MPT multimode base station or a single-mode GSM base station, choose
CME > GSM Application > Import Data > Import eGBTS Bulk Configuration Data
(U2000 client mode), or choose GSM Application > Import Data > Import eGBTS Bulk
Configuration Data (CME client mode), to import the summary data file into the CME.
3.
For a separate-MPT multimode base station or a single-mode UMTS base station, choose
CME > UMTS Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose UMTS Application > Import Data > Import Base
Station Bulk Configuration Data (CME client mode), to import the summary data file
into the CME.
4.
For a separate-MPT multimode base station or a single-mode LTE base station, choose
CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base
Station Bulk Configuration Data (CME client mode), to import the summary data file
into the CME.
----End
Activation Observation
Run the MML command LST TLFRSWITCH to query the value of the Transmission Link
Fault Recover Switch parameter. If the parameter is set to ENABLE(Enable), the transmission
link fault rectification function is enabled.
Deactivation
Using MML Commands
Run the MML command SET TLFRSWITCH to set the Transmission Link Fault Recover
Switch parameter to DISABLE(Disable).

SET TLFRSWITCH: TLFRSWITCH=DISABLE;
Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature. This
method reconfigures all data, except neighbor relationships. Using this method to deactivate a
feature is the same as to activate a feature. For details, see Using the CME to Perform Batch
Configuration for Existing Base Stations. Set the parameter, as shown in Table 8-2.
Issue 01 (2014-04-30)

17
SingRAN
Description
Table 8-2 Parameters related to the transmission link fault rectification function
MO
Sheet in the
Summary Data File
Parameter Group
Remarks
TLFRSWITCH
User-defined sheet
TLFRSWITCH
Set this parameter to

DISABLE(Disable).
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the Data Preparation section. For instructions on how
to perform the CME single configuration, see CME Single Configuration Operation Guide.
8.3.5 Performance Monitoring

None
8.3.6 Parameter Optimization

None
8.3.7 Troubleshooting
None
Issue 01 (2014-04-30)

18
SingRAN
Description
9 Parameters
Parameters
Table 9-1 Parameter description

Parame
ter ID
NE
MML
Comma
nd
Feature
ID
Feature
Name
Description
TLFRS
WITCH
BTS390
0,
BTS390
0
WCDM
A,
BTS390
0 LTE
SET
TLFRS
WITCH
None
None
Meaning: Indicates whether to enable the function of

clearing faults on a transmission link. If this parameter
is set to ENABLE, a BS attempts to clear a fault by
means of automatic reset when the BS cannot be
maintained (OMCH of the BS is disconnected) and
service interruption duration reaches 45 minutes. If the
fault fails to be cleared, the BS attempts to clear the fault
again in the same way when the service interruption
duration reaches 480 minutes. If the fault fails to be
cleared after the two resets, the BS stops performing
automatic reset. The service interruption duration at
which the BS automatically resets has fixed values (45
minutes and 480 minutes) and is not configurable.
LST
TLFRS
WITCH
GUI Value Range: DISABLE(Disable), ENABLE

(Enable)
Unit: None
Actual Value Range: DISABLE, ENABLE
Default Value: ENABLE(Enable)
Issue 01 (2014-04-30)

19
SingRAN
Description
10 Counters
10
Counters
There are no specific counters associated with this feature.
Issue 01 (2014-04-30)

20
SingRAN
Description
11 Glossary
11
Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
Issue 01 (2014-04-30)

21
SingRAN
Description
12
1.
Issue 01 (2014-04-30)
12 Reference Documents
Reference Documents
3900 Series Base Station Initial Configuration Guide

22

Base Station OMCH Self-Recovery (SRAN9.0 - 01)

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Base Station OMCH Self-Recovery (SRAN9.0 - 01)

Enviado por

Direitos autorais:

Formatos disponíveis

SingRAN

Base Station OMCH Self-recovery

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

3 Automatic Version Rollback.......................................................................................................4

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1 About This Document

About This Document

1.2 Intended Audience

Need to understand the features described herein.

Work with Huawei products

1.3 Change History

Huawei Proprietary and Confidential

1 About This Document

Revised the following sections:

SRAN9.0 Draft A (2014-01-20)

1.4 Differences Between Base Station Types

Huawei Proprietary and Confidential

Automatic version rollback

Automatic configuration data rollback

Transmission link fault rectification

Huawei Proprietary and Confidential

3 Automatic Version Rollback

Automatic Version Rollback

Automatic Version Rollback for eGBTS/NodeB/eNodeB

The NEs detect that the current version fails to be initialized.

Automatic Version Rollback for GBTS

Huawei Proprietary and Confidential

4 Automatic Configuration Data Rollback

Automatic Configuration Data Rollback

Automatic Configuration Data Rollback for eGBTS/NodeB/eNodeB

The period of time specified by RBKTIME has not expired.

Huawei Proprietary and Confidential

4 Automatic Configuration Data Rollback

The period of time specified by RBKTIME expires.

Huawei Proprietary and Confidential

4 Automatic Configuration Data Rollback

Automatic Configuration Data Rollback for GBTS

Huawei Proprietary and Confidential

5 Transmission Link Fault Rectification

Transmission Link Fault Rectification

Transmission Link Fault Rectification for eGBTS/NodeB/eNodeB

Run the LST TLFRSWITCH command to query the value of TLFRSWITCH.

Transmission Link Fault Rectification for GBTS

Huawei Proprietary and Confidential

Mutually Exclusive Features

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

8.1 Engineering Guidelines for Automatic Version Rollback

8.2 Engineering Guidelines for Automatic Configuration

8.2.1 When to Use Automatic Configuration Data Rollback

8.2.2 Required Information

Huawei Proprietary and Confidential

In scenarios where only the radio

Users should estimate in advance the

Huawei Proprietary and Confidential

Set this parameter to OMCH_FAULT

MML Command Examples