Base Station OMCH Self-Recovery (SRAN10.1 - 01)

SingleRAN
Base Station OMCH Self-recovery

Feature Parameter Description
Issue 01
Date 2015-03-23
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2016. 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 (2015-03-23) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
SingleRAN
Base Station OMCH Self-recovery Feature Parameter
Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 2
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between Base Station Types....................................................................................................................... 3
2 Overview......................................................................................................................................... 5
2.1 Definition........................................................................................................................................................................5
2.2 Benefits........................................................................................................................................................................... 5
3 Technical Description...................................................................................................................6
3.1 Automatic Version Rollback...........................................................................................................................................6
3.2 Automatic Configuration Data Rollback........................................................................................................................ 7
3.3 Transmission link fault rectification............................................................................................................................... 8
4 Related Features...........................................................................................................................10
5 Network Impact........................................................................................................................... 11
6 Engineering Guidelines............................................................................................................. 12
6.1 Automatic Version Rollback.........................................................................................................................................12
6.2 Engineering Guidelines for Automatic Configuration Data Rollback......................................................................... 12
6.2.1 When to Use Automatic Configuration Data Rollback............................................................................................. 12
6.2.2 Required Information................................................................................................................................................ 13
6.2.3 Planning..................................................................................................................................................................... 13
6.2.4 Deployment............................................................................................................................................................... 13
6.2.4.1 Requirements.......................................................................................................................................................... 13
6.2.4.2 Data Preparation..................................................................................................................................................... 13
6.2.4.3 Precautions..............................................................................................................................................................14
6.2.4.4 Activation............................................................................................................................................................... 15
6.2.4.5 Activation Observation...........................................................................................................................................15
6.2.4.6 Deactivation............................................................................................................................................................15
6.2.5 Performance Monitoring............................................................................................................................................15
6.2.6 Parameter Optimization............................................................................................................................................. 15
6.2.7 Troubleshooting......................................................................................................................................................... 15
6.3 Engineering Guidelines for Transmission Link Fault Rectification.............................................................................16
Issue 01 (2015-03-23) Huawei Proprietary and Confidential ii

SingleRAN
Description Contents
6.3.1 When to Use Transmission Link Fault Rectification.................................................................................................16

6.3.2 Required Information................................................................................................................................................ 16
6.3.3 Planning..................................................................................................................................................................... 16
6.3.4 Deployment............................................................................................................................................................... 16
6.3.4.1 Requirements.......................................................................................................................................................... 16
6.3.4.2 Data Preparation..................................................................................................................................................... 16
6.3.4.3 Precautions..............................................................................................................................................................16
6.3.4.4 Activation............................................................................................................................................................... 17
6.3.4.5 Activation Observation...........................................................................................................................................17
6.3.4.6 Deactivation............................................................................................................................................................17
6.3.5 Performance Monitoring............................................................................................................................................18
6.3.6 Parameter Optimization............................................................................................................................................. 18
6.3.7 Troubleshooting......................................................................................................................................................... 18
7 Parameters..................................................................................................................................... 19
8 Counters........................................................................................................................................ 21
9 Glossary......................................................................................................................................... 22
10 Reference Documents............................................................................................................... 23
Issue 01 (2015-03-23) Huawei Proprietary and Confidential iii

SingleRAN
Description 1 About This Document
1 About This Document
1.1 Scope
This document describes the Base Station OMCH Self-recovery feature, including its
technical principles, related features, network impact, and engineering guidelines. It consists
of four functions:
l Automatic version rollback
l Automatic configuration data rollback
l Transmission link fault rectification
Table 1-1 lists the definitions of all kinds of macro base stations.
Table 1-1 Base station definitions

Base Station Definition
Name
GBTS A base station configured with a GTMU, GTMUb, or GTMUc and

maintained through a base station controller.
eGBTS A base station configured with a GTMUb, UMPT_G, or UMDU_G and

directly maintained by the element management system (EMS).
NodeB A base station configured with a WMPT, UMPT_U, or UMDU_U.
eNodeB A base station configured with an LMPT, UMPT_L, UMPT_T,

UMDU_L, or UMDU_T.
Issue 01 (2015-03-23) Huawei Proprietary and Confidential 1

SingleRAN
Base Station Definition

Name
Co-MPT A base station configured with a UMPT_GU, UMDU_GU, UMPT_GL,

multimode base UMDU_GL, UMPT_GT, UMDU_GT, UMPT_UL, UMDU_UL,
station UMPT_UT, UMDU_UT, UMPT_LT, UMDU_LT, UMPT_GUL,
UMDU_GUL, UMPT_GUT, UMDU_GUT, UMPT_ULT, UMDU_ULT,
UMPT_GLT, UMDU_GLT, UMPT_GULT, or UMDU_GULT. A co-
MPT multimode base station functionally corresponds to any physical
combination of eGBTS, NodeB, and eNodeB. For example, a co-MPT
multimode base station configured with a UMPT_GU or UMDU_GU
functionally corresponds to the physical combination of eGBTS and
NodeB.
NOTE
Unless otherwise specified, the descriptions and examples of the UMPT in a co-
MPT base station also apply to the UMDU in a co-MPT base station.
Separate-MPT A base station on which each mode uses its separate main control board.
multimode base For example, a base station configured with a GTMU and WMPT is
station called a separate-MPT GSM/UMTS dual-mode base station.
NOTE
A UMDU cannot be used in a separate-MPT base station.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein.
l 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
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
SRAN10.1 01 (2015-03-23)
Compared with Draft A (2015-02-10) of SRAN10.1, 01 (2015-03-23) of SRAN10.1 includes
the following changes.

SingleRAN
Change Change Description Parameter

Type Change
Feature After a GBTS upgrade, the automatic version rollback None

change function will be triggered if either of the following
conditions is met:
l The OML of the current version has not been
successfully connected and the GBTS has been reset for
three times.
l The OML of the current version has not been
successfully connected and the interruption has lasted
30 minutes.
For details, see 3.1 Automatic Version Rollback.
Editorial None None

change
SRAN10.1 Draft A (2015-02-10)

Compared with Issue 02 (2014-05-30) of SRAN9.0, Draft A (2015-02-10) of SRAN10.1
includes the following changes.
Change Change Description Parameter

Type Change
Feature Changed the service interruption duration for triggering the None
change transmission link fault rectification function from 45
minutes to 30 minutes for an eGBTS/NodeB/eNodeB. For
details, see 3.3 Transmission link fault rectification.
Editorial None None

change
1.4 Differences Between Base Station Types

Definition
The macro base stations described in this document refer to 3900 series base stations. These
base stations work in GSM, UMTS, or LTE mode, as listed in the "Scope" section.
The LampSite base stations described in this document refer to distributed base stations that
provide indoor coverage. These base stations work in UMTS or LTE mode but not in GSM
mode.
The micro base stations described in this document refer to all integrated entities that work in
UMTS or LTE mode but not in GSM mode. Descriptions of boards, cabinets, subracks, slots,
and RRUs do not apply to micro base stations.
The following table defines the types of micro base stations.

SingleRAN
Base Station Model RAT
BTS3202E LTE FDD
NOTE
The co-MPT and separate-MPT applications are irrelevant to single-mode micro base stations.
Feature Support by Macro, Micro, and LampSite Base Stations

None
Function Implementation in Macro, Micro, and LampSite Base Stations

None

SingleRAN
Description 2 Overview
2 Overview
2.1 Definition
The OM channel (OMCH for short) of a base station refers to the channel through which the
eGBTS/NodeB/eNodeB communicates with the U2000 or the GBTS communicates with the
BSC to exchange operation and maintenance information about base stations.
If an OMCH is interrupted, measures are taken remotely to recover the OMCH. These
recovery measures include the following:
l Automatic version rollback
l Automatic configuration data rollback
l Transmission link fault rectification
2.2 Benefits
If an OMCH interruption occurs, the Base Station OMCH Self-recovery feature reduces the
need for onsite handling. This therefore shortens the interruption time and saves costs.

SingleRAN
Description 3 Technical Description
3 Technical Description
3.1 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 version for an NE has been upgraded, the NE will reset. After the NE has
restarted, its software version will be rolled back to the source version and ALM-26255
Automatic Version Rollback will be reported if one of the following faults occurs:
l The NE detects that the initialization of the current version fails.

l The NE detects that the OMCH of the current version has not been successfully
connected, and the interruption has lasted 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 system abnormally resets within ten minutes after the hot patch is activated.
l The OMCH is continuously disconnected within ten minutes after the hot patch is
activated, and the system resets before the OMCH recovery process starts (for example,
the transmission link fault rectification function is triggered).
Automatic Version Rollback for GBTS

After the software version for an NE has been upgraded, the NE will reset. After the NE has
restarted, its software version will be rolled back to the source version and ALM-26255
Automatic Version Rollback will be reported if one of the following faults occurs:
l The NE detects that the OML of the current version remains disconnected, and the NE
has reset for three times.
l The NE detects that the OML of the current version has not been successfully connected,
and the interruption has lasted 30 minutes.

SingleRAN
The GBTS does not support automatic version rollback of hot patches.
3.2 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 or router 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 CFM CB command is used to enable the automatic configuration data rollback
function, the system saves the current configuration data to the new configuration baseline
(CB) created by this command and then the timer specified by RBKTIME starts. The data
modification must be completed before the timer expires.
For the existing 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 parameter is reconfigured, the system will restart the timing(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 has been modified or recovers to the
normal state after an interruption, and users do not require rollback regardless 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 case of an OMCH interruption.
NOTE
Incorrect modification of certain data will not lead to an 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 of the peer NE.
If the base station resets and related conditions are met before the period of time specified by
RBKTIME expires, 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.

SingleRAN
NOTE
The OMCH is considered faulty when it is interrupted and detected within five minutes.
– If the rollback conditions are not met, the system waits five more minutes before
making a decision again. The remaining rollback time is five minutes and the timer
restarts. After the five minutes expire,
- If rollback conditions specified by the parameter RBKCONDITION are met, the
base station resets and 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, then this alarm was triggered by the automatic configuration data rollback
function.
When this function is enabled on a batch of base stations, the external transmission link may be
continuously interrupted. If rollback conditions are met when the timer specifying the rollback time
expires, the automatic configuration data rollback function will be triggered for these base stations. For
an OMCH interruption 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, and 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 yet 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 the function.
The configuration data of peripheral NEs may be modified when the configuration data of
base stations is being modified. After the automatic configuration data rollback function has
been successfully triggered, the configuration data of base stations is rolled back. At the same
time, the data of peripheral NEs may also need to be rolled back to ensure a normal OMCH.
Therefore, the data modification of peripheral NEs during this period and the rollback
methods should be obtained.
Automatic Configuration Data Rollback for GBTS

The GBTS does not support the automatic configuration data rollback function.
3.3 Transmission link fault rectification

The working principles of the automatic remote OMCH establishment function for an
eGBTS/NodeB/eNodeB are different from those for a GBTS. The details are described in the
following sections.

SingleRAN
Transmission Link Fault Rectification for an eGBTS/NodeB/eNodeB

This function enables a base station to initiate a warm reset when both the OMCH and
services are interrupted. The reset helps resolve certain issues and avoid onsite handling.
If a base station cannot be maintained due to an interrupted OMCH and services have been
interrupted for 30 minutes, the base station automatically resets to rectify the fault. If the fault
persists, the base station will initiate another reset after an interval of 480 minutes. If the two
resets still cannot rectify the fault, the base station will not reset again.
NOTE
The base station initiates the first reset when the following conditions are met:
l Both the OMCH and services are interrupted because the user modifies configuration data.
l The interruption lasts 180 minutes.
The base station automatically resets at a fixed interval (30, 180, or 480 minutes), which cannot be
manually set.
If the conditions for clearing transmission link faults are met, the base station does not reset
automatically when local maintenance connection is normal. If the local maintenance connection is
interrupted later, and both the OMCH and services are interrupted, the base station resets immediately.
This function is enabled by default. If the function is disabled, run the MML command SET
TLFRSWITCH with TLFRSWITCH set to ENABLE(Enable).
Transmission Link Fault Rectification for GBTS

After the OML between the GBTS and BSC has been interrupted for 15 minutes, the GBTS
initiates a warm reset to rectify the fault, which helps avoid onsite handling.
This function is not under switch control and is enabled by default.
NOTE
In this function, the GBTS can reset for an infinite number of times.

SingleRAN
Description 4 Related Features
4 Related Features
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None

SingleRAN
Description 5 Network Impact
5 Network Impact
System Capacity
None
Network Performance
None

SingleRAN
Description 6 Engineering Guidelines
6 Engineering Guidelines
6.1 Automatic Version Rollback

The automatic version rollback function is not under switch control and is enabled by default.
NOTE
After a base station triggers the automatic version rollback function, ALM-26255 Automatic Version
Rollback will be reported and the base station will reset. Services will be interrupted during the reset.
In a multimode base station where multiple modes share a board such as a main control board, all modes
involved will be affected when the main control board resets.
The default length of the rollback timer for a GBTS is 30 minutes. The length can be modified by setting
the OMLFailRollbackPolicy parameter in the MML command SET BTSOTHPARA. This parameter
specifies the policy for version rollback when the OML between a GBTS and the BSC fails to be set up
after the GBTS is upgraded. The parameter has the following values: 30min(30min), 60min(60min),
120min(120min), and NOTROLLBACK(NOTROLLBACK). Note that modification of this
parameter is permanently valid.
6.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.
6.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.

SingleRAN
6.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.
6.2.3 Planning
None
6.2.4 Deployment
6.2.4.1 Requirements
None
6.2.4.2 Data Preparation

MO Parameter Name Parameter ID Setting Notes
- Automatic AUTORBKS In scenarios where only the radio

Rollback Switch W 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.

SingleRAN
MO Parameter Name Parameter ID Setting Notes
- 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. If the modification
cannot be completed within 30 minutes,
you can run the MOD CB command to
reconfigure the rollback time in advance.
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.
- Rollback RBKCONDI Set this parameter to

Condition TION OMCH_FAULT(OMCH_FAULT) in
most cases.
If this parameter is set to
OMCH_AND_SERVICE_FAULT(OM
CH_AND_SERVICE_FAULT), the
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 whereas services are normal, the
function will not be triggered.
6.2.4.3 Precautions
After the system successfully triggers the automatic configuration data rollback function, the
base station will reset, during which services are temporarily interrupted.

SingleRAN
In a multi-mode base station with multiple modes sharing a single board, for example, a co-
MPT multi-mode base station, resetting the base station or the common board on any mode
affects the services of other modes.
6.2.4.4 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.
6.2.4.5 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.
6.2.4.6 Deactivation
Using MML Commands

Run the MML command MOD CB to set the Automatic Rollback Switch parameter to
DISABLE(Disable).

MOD CB: NAME="Rollback CB 1", COMMENT="CB for Rollback", AUTORBKSW = DISABLE;
Using the CME

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

None
6.2.6 Parameter Optimization

None
6.2.7 Troubleshooting
None

SingleRAN
6.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.
6.3.1 When to Use Transmission Link Fault Rectification

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

None
6.3.3 Planning
None
6.3.4 Deployment
6.3.4.1 Requirements
None
6.3.4.2 Data Preparation

MO Parameter Parameter ID Setting Notes
Name
TLFR Transmission TLFRSWITC Set this parameter to ENABLE(Enable).

SWIT Link Fault H
CH Recover Switch
6.3.4.3 Precautions
After the system successfully triggers the automatic configuration data rollback function, the
base station will reset, during which services are temporarily interrupted.
In a multi-mode base station with multiple modes sharing a single board, for example, a co-
MPT multi-mode base station, resetting the base station or the common board on any mode
affects the services of other modes.

SingleRAN
6.3.4.4 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 Configuration

This feature can be activated using the CME. This section uses the eNodeB as an example.
For detailed operations, see CME-based Feature Configuration or the CME online help (press
F1 in an active CME window).
Configuration CME Online Help

Type
Single configuration CME Management > CME Guidelines > Getting Started with
the CME > Introduction to Data Configuration Operations
Batch eGBTS CME Management > CME Guidelines > GSM Application
configuration Management > Base Station Related Operations > Importing
and Exporting eGBTS Data for Batch Reconfiguration
Batch NodeB CME Management > CME Guidelines > UMTS Application
configuration Management > NodeB Related Operations > Importing and
Exporting NodeB Data for Batch Configuration
Batch eNodeB CME Management > CME Guidelines > LTE Application
configuration Management > eNodeB Related Operations > Importing and
Exporting eNodeB Data for Batch Configuration
6.3.4.5 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.
6.3.4.6 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;

SingleRAN
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
6-1.
Table 6-1 Parameters related to the transmission link fault rectification function
MO Sheet in the Parameter Group Remarks
Summary Data File
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.
6.3.5 Performance Monitoring

None
6.3.6 Parameter Optimization

None
6.3.7 Troubleshooting
None

SingleRAN
Description 7 Parameters
7 Parameters
Table 7-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
TLFRS TLFRS SET None None Meaning: Indicates whether to enable the function of
WITCH WITCH TLFRS clearing faults on a transmission link. If this parameter
WITCH is set to ENABLE, a BS attempts to clear a fault by
LST means of automatic reset when the BS cannot be
TLFRS maintained (OMCH of the BS is disconnected) and
WITCH service interruption duration reaches 30 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 (30 minutes and 480 minutes) and is not
configurable.
GUI Value Range: DISABLE(Disable),
ENABLE(Enable)
Unit: None
Actual Value Range: DISABLE, ENABLE
Default Value: ENABLE(Enable)

SingleRAN
Description 7 Parameters
MO Parame MML Feature Feature Description

ter ID Comma ID Name
nd
DHCPS SWITC SET WRFD- NodeB Meaning: Indicates whether to enable detection of
W H DHCPS 031101 Self- automatic establishment of the remote maintenance
W discover channel.
LOFD-0 y Based
LST 02004 / GUI Value Range: DISABLE(Disable),
DHCPS on IP ENABLE(Enable)
TDLOF Mode
W D-00200 Unit: None
4 Self- Actual Value Range: DISABLE, ENABLE
configur
GBFD-1 ation Default Value: ENABLE(Enable)
18601
GBFD-1 Abis
18611 over IP
Abis IP
over
E1/T1

SingleRAN
Description 8 Counters
8 Counters
There are no specific counters associated with this feature.

SingleRAN
Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN
Description 10 Reference Documents
10 Reference Documents
1. 3900 Series Base Station Initial Configuration Guide


Base Station OMCH Self-Recovery (SRAN10.1 - 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Base Station OMCH Self-Recovery (SRAN10.1 - 01)

Uploaded by

Copyright:

Available Formats

SingleRAN

Base Station OMCH Self-recovery

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2015-03-23) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

Issue 01 (2015-03-23) Huawei Proprietary and Confidential ii

6.3.1 When to Use Transmission Link Fault Rectification.................................................................................................16

Issue 01 (2015-03-23) Huawei Proprietary and Confidential iii

1 About This Document

Table 1-1 Base station definitions

GBTS A base station configured with a GTMU, GTMUb, or GTMUc and

eGBTS A base station configured with a GTMUb, UMPT_G, or UMDU_G and

NodeB A base station configured with a WMPT, UMPT_U, or UMDU_U.

eNodeB A base station configured with an LMPT, UMPT_L, UMPT_T,

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 1

Base Station Definition

Co-MPT A base station configured with a UMPT_GU, UMDU_GU, UMPT_GL,

1.2 Intended Audience

1.3 Change History

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 2

Change Change Description Parameter

Feature After a GBTS upgrade, the automatic version rollback None

Editorial None None

SRAN10.1 Draft A (2015-02-10)

Change Change Description Parameter

Editorial None None

1.4 Differences Between Base Station Types

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 3

Base Station Model RAT

BTS3202E LTE FDD

Feature Support by Macro, Micro, and LampSite Base Stations

Function Implementation in Macro, Micro, and LampSite Base Stations

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 4

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 5

3.1 Automatic Version Rollback

Automatic Version Rollback for eGBTS/NodeB/eNodeB

l The NE detects that the initialization of the current version fails.

Automatic Version Rollback for GBTS

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 6

3.2 Automatic Configuration Data Rollback

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 7

If the automatic configuration data rollback function is manually or automatically disabled,

Automatic Configuration Data Rollback for GBTS

3.3 Transmission link fault rectification

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 8

Transmission Link Fault Rectification for an eGBTS/NodeB/eNodeB

Transmission Link Fault Rectification for GBTS

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 9

Mutually Exclusive Features

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 10

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 11

6.1 Automatic Version Rollback

6.2 Engineering Guidelines for Automatic Configuration

6.2.1 When to Use Automatic Configuration Data Rollback

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 12

6.2.2 Required Information

6.2.4.2 Data Preparation

- Automatic AUTORBKS In scenarios where only the radio

Issue 01 (2015-03-23) Huawei Proprietary and Confidential 13

MO Parameter Name Parameter ID Setting Notes

- Rollback Time RBKTIME Users should estimate in advance the