Base Station OMCH Self-Recovery (SRAN11.1 - 02)

SingleRAN
SRAN11.1
Base Station OMCH Self-recovery

Feature Parameter Description
Issue 02
Date 2016-07-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2018. 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 02 (2016-07-30) 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.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between Base Station Types....................................................................................................................... 3
2 Overview......................................................................................................................................... 4
2.1 Definition........................................................................................................................................................................4
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........................................................................................................................... 9
3.4 Automatic OM Channel Establishment.......................................................................................................................... 9
3.5 Automatic Recovery of OM Channel Running Data....................................................................................................11
4 Related Features...........................................................................................................................13
5 Network Impact........................................................................................................................... 14
6 Engineering Guidelines............................................................................................................. 15
6.1 Automatic Version Rollback.........................................................................................................................................15
6.2 Automatic Configuration Data Rollback...................................................................................................................... 15
6.2.1 When to Use.............................................................................................................................................................. 15
6.2.2 Required Information................................................................................................................................................ 16
6.2.3 Planning..................................................................................................................................................................... 16
6.2.4 Deployment............................................................................................................................................................... 16
6.2.4.1 Requirements.......................................................................................................................................................... 16
6.2.4.2 Data Preparation..................................................................................................................................................... 16
6.2.4.3 Precautions..............................................................................................................................................................17
6.2.4.4 Activation............................................................................................................................................................... 18
6.2.4.5 Activation Observation...........................................................................................................................................18
6.2.4.6 Deactivation............................................................................................................................................................18
6.2.5 Performance Monitoring............................................................................................................................................18
6.2.6 Parameter Optimization............................................................................................................................................. 18
Issue 02 (2016-07-30) Huawei Proprietary and Confidential ii

SingleRAN
Description Contents
6.2.7 Possible Issues........................................................................................................................................................... 18

6.3 Transmission Link Fault Rectification......................................................................................................................... 18
6.3.1 When to Use.............................................................................................................................................................. 19
6.3.3 Planning..................................................................................................................................................................... 19
6.3.4 Deployment............................................................................................................................................................... 19
6.3.4.1 Requirements.......................................................................................................................................................... 19
6.3.4.3 Precautions..............................................................................................................................................................19
6.3.4.4 Activation............................................................................................................................................................... 19
6.3.4.6 Deactivation............................................................................................................................................................20
6.3.7 Possible Issues........................................................................................................................................................... 21
6.4 Automatic OM Channel Establishment........................................................................................................................ 21
6.4.1 When to Use.............................................................................................................................................................. 21
6.4.3 Planning..................................................................................................................................................................... 21
6.4.4 Deployment............................................................................................................................................................... 21
6.4.4.1 Requirements.......................................................................................................................................................... 21
6.4.4.3 Precautions..............................................................................................................................................................22
6.4.4.4 Activation............................................................................................................................................................... 22
6.4.4.6 Deactivation............................................................................................................................................................23
6.4.7 Possible Issues........................................................................................................................................................... 24
6.5 Automatic Recovery of OM Channel Running Data....................................................................................................24
7 Parameters..................................................................................................................................... 25
8 Counters........................................................................................................................................ 27
9 Glossary......................................................................................................................................... 28
10 Reference Documents............................................................................................................... 29
Issue 02 (2016-07-30) 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
l Automatic OM channel establishment
l Automatic recovery of OM channel running data
For definitions of base stations described in this document, see section "Base Station
Products" in SRAN Networking and Evolution Overview Feature Parameter Description.
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
Issue 02 (2016-07-30) Huawei Proprietary and Confidential 1

SingleRAN
SRAN11.1 02 (2016-07-30)
Compared with Issue 01 (2016-02-29) of SRAN11.1, Issue 02 (2016-07-30) of SRAN11.1
includes the following changes.
Change Change Description Parameter

Type Change
Feature Added the function of automatic recovery of OM channel None

change running data. For details, see 2.1 Definition, 3.5
Automatic Recovery of OM Channel Running Data,
and 6.5 Automatic Recovery of OM Channel Running
Data.
Editorial Revised the description in 3.4 Automatic OM Channel None

change Establishment.
SRAN11.1 01 (2016-02-29)
This issue does not include any changes.
SRAN11.1 Draft A (2015-12-30)

Compared with Issue 01 (2015-03-23) of SRAN10.1, Draft A (2015-12-30) of SRAN11.1
includes the following changes.
Change Change Description Parameter

Type Change
Feature Added the GTMUc board to the eGBTS. None

change Added descriptions about the mapping between scenarios
and recovery measures. For details, see 2.1 Definition.
Added descriptions about the automatic OM channel
establishment function and the engineering guidelines.
For details, see 3.4 Automatic OM Channel
Establishment and 6.4 Automatic OM Channel
Establishment, respectively.
Added descriptions about the delayed establishment
function to automatic OM channel establishment. For
details, see Automatic OM Channel Establishment for
eGBTS/NodeB/eNodeB.
Added the version rollback policy for the GBTS to the
automatic version rollback function. For details, see 6.1
Automatic Version Rollback.
Editorial Updated the description about the automatic version None

change rollback function for a GBTS. For details, see Automatic
Version Rollback for GBTS.
Revised the description in 6 Engineering Guidelines.

SingleRAN
1.4 Differences Between Base Station Types

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 remote maintenance channel (abbreviated as OM channel) 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 OM channel is interrupted, measures are taken to recover the OM channel. These
recovery measures include the following:
l Automatic version rollback
l Automatic configuration data rollback
l Transmission link fault rectification
l Automatic OM channel establishment
l Automatic recovery of OM channel running data
The following figure shows the recovery measures in different scenarios.

SingleRAN
Description 2 Overview
Figure 2-1 Measures taken to recover the interrupted OM channel in different scenarios
Automatic version rollback: After an upgrade of base station software, the software version of
NEs is automatically rolled back to the source version, when rollback conditions are met, to
recover the OM channel.
Automatic configuration data rollback: Users enable the automatic configuration data rollback
function before modifying the data related to the OM channel. If the OM channel
continuously disconnects after the modification when the timer specifying the rollback time
expires, the base station automatically resets and rolls the configuration data back to the data
before modification to recover the OM channel.
Transmission link fault rectification: After this function is enabled, the base station initiates a
reset to recover the faulty OM channel when the OM channel and services are both
interrupted.
Automatic OM channel establishment: After this function is enabled, the base station obtains
the OM channel information through the DHCP Detect process when automatic OM channel
establishment conditions are met to recover the OM channel.
Automatic recovery of OM channel running data: The OM channel running data collected
while the OM channel works properly is used to restore the OM channel.
For details about each function, see the following chapters.
2.2 Benefits
If an OM channel interruption occurs, the Base Station OMCH Self-recovery feature reduces
the need for onsite handling, and therefore shortens the interruption time and saves costs.

SingleRAN
Description 3 Technical Description
3 Technical Description
3.1 Automatic Version Rollback

This function is not under switch control and is enabled by default.
Automatic Version Rollback for eGBTS/NodeB/eNodeB

After the software version for a base station has been upgraded, the base station will reset.
After the base station 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 base station detects that the initialization of the current version fails.
l The base station detects that the OM channel of the current version has not been
successfully connected, and the interruption has lasted 30 minutes.
After the hot patch of a base station 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.
l The OM channel is continuously disconnected within ten minutes after the hot patch is
activated, and the base station resets before the OM channel recovery process starts (for
example, the transmission link fault rectification function is triggered).
Automatic Version Rollback for GBTS

After the software version for a base station has been upgraded, the base station will reset.
After the base station 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 base station detects that the initialization of the current version fails.
l The base station detects that the OM channel of the current version has not been
successfully connected, and the interruption has lasted 30 minutes.
The GBTS does not support automatic version rollback of hot patches.

SingleRAN
3.2 Automatic Configuration Data Rollback

Automatic Configuration Data Rollback for eGBTS/NodeB/eNodeB
If you are concerned that inappropriate data modification may cause long OM channel
interruptions and recovery failures (for example, when the IP address, IPsec address, or router
is incorrectly modified), you can enable the automatic configuration data rollback function
before modifying the data related to the OM channel. This function can roll back the
configuration data, which reduces the need for site visits.
NOTE
It is recommended that this function be disabled when the data related to the OM channel is locally
modified. Otherwise, the automatic configuration data rollback function may be triggered as a result of
an OM channel 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 base station 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 complete 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 complete 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 base station will restart the timing (the remaining rollback time
can be queried by running the MML command DSP CB).
l The period of time specified by RBKTIME has not expired.

If the OM channel 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
OM channel 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 OM channel interruption.
NOTE
Incorrect modification of certain data will not immediately lead to an immediate OM channel
interruption because the modification must be renegotiated with the peer NE. Such data includes
parameters in IPSECPROPOSAL, IKEPROPOSAL, and IKECFG MOs. The settings of these
parameters must be consistent with those 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 base station will automatically disable this function after the rollback
is complete.

SingleRAN
NOTE
The OM channel is considered faulty when it is interrupted and the interruption is detected
within five minutes.
– If the rollback conditions are not met, the base station 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 OM channel 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 OM
channel 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 was triggered by the automatic configuration data rollback
function.
The automatic configuration data rollback will be triggered when the following conditions are met:
l The automatic configuration data rollback function is enabled on a batch of base stations.
l The external transmission link is continuously interrupted.
l Rollback conditions are met when the timer specifying the rollback time expires.
For an OM channel 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 base station 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,

the automatic configuration data rollback function needs to be reconfigured if it is required.
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 OM
channel. 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.

SingleRAN
3.3 Transmission Link Fault Rectification

The working principles of this function for an eGBTS/NodeB/eNodeB are different from
those for a GBTS. The details are described in the following sections.
Transmission Link Fault Rectification for an eGBTS/NodeB/eNodeB

This function enables a base station to initiate a reset when both the OM channel and services
are interrupted. The reset helps resolve certain issues and avoid onsite handling.
If the OM channel and services have been interrupted for 30 or 180 minutes (only in the
scenario where the base station starts DHCP detection after a false deletion of the OMCH
MO), 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
l The OM channel and service interruption duration (30, 180, or 480 minutes) that triggers an
automatic reset will be prolonged by a random value of 0 to 10 minutes. The time when an
automatic reset is triggered cannot be manually configured.
l If the local maintenance connection is normal, the base station will not perform transmission link
fault rectification. If the local maintenance connection is interrupted later, and both the OM channel
and services are interrupted, the base station resets immediately.
l 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 OM channel between the GBTS and BSC has been interrupted for 15 minutes, the
GBTS initiates a reset to rectify the fault, which helps avoid onsite handling.
NOTE
In this function, the GBTS can reset for an infinite number of times.
3.4 Automatic OM Channel Establishment

The automatic OM channel establishment function allows a base station to recover the OM
channel through the DHCP Detect process.
The DHCP Detect process is classified into:
1. Recovery process of some OM channel-related parameters (DHCP Listen)
– Scenario: non-IPsec networking or IPsec networking where the DHCP channel is
not protected by IPsec
– Prerequisite: The OM channel is disconnected.
– This recovery does not affect services.
– Scope: IP address and binding route of the OM channel
2. Recovery process of all OM channel-related parameters (DHCP Detect)

SingleRAN
– Scenario: IP transmission
– Prerequisite: Both the OM channel and services are interrupted.
– Scope: all parameters that are related to the OM channel at the physical layer, data
link layer, and network layer. This type of recovery requires detection on all ports.
NOTE
l These two DHCP detection-based recoveries have the same protocol process. For details, see the
DHCP process in Automatic OMCH Establishment Feature Parameter Description.
l In IP layer 3 networking, the DHCP detection depends on the DHCP Relay function configured for
the transmission network.
The working principles of this function for an eGBTS/NodeB/eNodeB are different from
those for a GBTS. The details are described in the following sections.
Automatic OM Channel Establishment for eGBTS/NodeB/eNodeB

1. Recovery process of some OM channel-related parameters (DHCP Listen)
This process is supported by the base station by default and has no switch control. The
base station can perform this process when the OM channel is interrupted or services are
normal.
2. Recovery process of all OM channel-related parameters (DHCP Detect)
If any of the following conditions is met when the switch for the automatic OM channel
establishment function is enabled, the automatic OM channel establishment will be triggered
after the OM channel and services have been interrupted for ten minutes.
l The OM channel is interrupted because the OMCH MO is modified.
l The OM channel is interrupted after configuration other than the OMCH MO is
modified, and the transmission link fault rectification is triggered.
l An abnormal reset unrelated to transmission links occurs, such as a power-on reset or
upgrade-led reset.
l The interruption lasts longer than the duration specified by the DELAYTIME parameter
in the SET DHCPDETECT command.
NOTE
l In transmission network reconstruction scenarios, the SET DHCPDETECT command can be

executed before the reconstruction to set the Detect delay time that is reserved for recovery
when the reconstruction is interrupted.
l During the reconstruction, the OM channel will be recovered after the Detect delay time
expires no matter whether the base station configuration is modified.
l The SET DHCPDETECT command is a maintenance command and will not take effect after
the base station is restarted. This command is not recommended for routine maintenance.
l The SET DHCPSW command has been used to set DHCPSW.DELAYSW to
ENABLE(Enable), and the OM channel and services have been interrupted for two
hours.
NOTE
l The delayed reestablishment switch specified by DHCPSW.DELAYSW is used when the OM

channel and services are both interrupted during routine Ethernet transmission maintenance.
l The automatic OM channel establishment triggered by the delayed reestablishment switch is
initiated on the Ethernet port after both the OM channel and services have been interrupted for
two hours. The two-hour duration is reserved for recovery in case of network interruptions and
is not configurable.

SingleRAN
l Risks and impact of the recovery process of all OM channel-related parameters:

– After the OM channel recovers through the DHCP Detect process, the element
management system (EMS) needs to re-deliver the new channel configuration to the
base station to restore services.
– If a base station is disconnected due to a fault of the bearer network, the base
station, when performing the DHCP Detect process, cannot restore services
immediately after the bearer network recovers. Services can only be restored after
the automatic OM channel establishment is complete.
– In separate-MPT multimode co-transmission scenarios or base station cascading
scenarios, if a base station is disconnected due to a fault of the bearer network,
services of other modes or cascaded base stations will be interrupted when the
disconnected base station performs the DHCP Detect process.
NOTE
l The automatic OM channel establishment function is enabled by default. If this function is disabled,
run the MML command SET DHCPSW with SWITCH set to ENABLE(Enable).
l For details about the automatic OM channel establishment function, see chapter 3 "IP-based
Automatic OMCH Establishment" in Automatic OMCH Establishment Feature Parameter
Description.
Automatic OM Channel Establishment for a GBTS

After the OM channel between the GBTS and BSC has been interrupted for 15 minutes, the
GBTS initiates a reset. If the OM channel remains interrupted after the reset, the GBTS
triggers the automatic OM channel establishment function.
3.5 Automatic Recovery of OM Channel Running Data

Automatic Recovery of OM Channel Running Data for an eGBTS/NodeB/
eNodeB
The OM channel running data that is collected while the OM channel works properly, instead
of data obtained from the remote DHCP server, is used to restore the OM channel. During the
automatic recovery, the base station configuration data will not take effect. If the recovery
fails, the base station configuration data will take effect.
This function is triggered in the following scenarios:
l After configuration modification, the OM channel is disconnected and services are

interrupted. The automatic OM channel establishment function can be triggered whereas
data cannot be obtained from the DHCP server.
l Both the OM channel and services are interrupted after configuration modification, and
the automatic OM channel establishment function cannot be triggered.
l The base station enters the minimum configuration state (that is, the minimum
configuration file released with the NE software is activated).The automatic OM channel
establishment function can be triggered after the base station reset whereas data cannot
be obtained from the DHCP server.

SingleRAN
NOTE
l When a user has logged in to the base station, for example, through Web LMT, this function does not
take effect.
Risks and impact:

l In separate-MPT multimode co-transmission scenarios or base station cascading
scenarios, if a base station is disconnected due to the faulty bearer network, services of
other modes or cascaded base stations will be interrupted when the disconnected base
station uses the function of automatic recovery of OM channel running data.
l If a base station is disconnected due to the faulty bearer network, the base station, when
using the function of automatic recovery of OM channel running data, cannot restore
services immediately after the bearer network recovers. Services can only be restored
after the automatic recovery of OM channel running data is complete.
l After the data recovery, the running data of the remote maintenance channel may be
inconsistent with the configuration data because only the running data has been
recovered, and the base station reports ALM-25902 Remote Maintenance Link Running
Data and Configuration Mismatch. In this case, the correct configuration data must be
delivered to the base station so that services can be restored.
l During the automatic recovery, the OM IP address and interface IP address of the OM
channel in the normal state are used. If any of these two IP addresses has been allocated
to another NE, this function will incur an IP address conflict.
The GBTS does not support the function of automatic recovery of OM channel running data.

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 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

Modifying the radio configuration parameters does not lead to OM channel interruption, so
the automatic configuration data rollback function does not need to be enabled.
However, modifying the configuration data related to OM channel may cause continuous OM
channel interruption, which cannot be remotely recovered. It is recommended that the
automatic configuration data rollback function be enabled in this scenario.
It is recommended that this function be disabled when the data related to the OM channel is
locally modified. Otherwise, the automatic configuration data rollback function may be
triggered as a result of an OM channel 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 Parameter ID Setting Notes
Name
- Automatic AUTORBKSW In scenarios where only the radio

Rollback Switch configuration parameters are modified
and the OM channel is not affected, turn
off this switch.
Turn on this switch when modifying the
configuration data of base stations
because it may cause continuous OM
channel interruptions and recovery
failures.

SingleRAN

Name
- 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 complete within
30 minutes. If the modification cannot be
complete within 30 minutes, run the
MOD CB command to reconfigure the
rollback time in advance.
If this parameter is set to a value too
large, the OM channel may be
interrupted for a long time (services may
also be interrupted for a long time). If
this parameter is set to a value too small,
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 OM channel and
services are interrupted, the system will
wait 220 minutes before triggering this
function. Such a long interruption affects
user experience.
- Rollback RBKCONDITI Set this parameter to

Condition ON OMCH_FAULT(OMCH_FAULT) in
most cases.
If this parameter is set to
OMCH_AND_SERVICE_FAULT(OM
CH_AND_SERVICE_FAULT), the
automatic configuration data rollback
function will be triggered after the
rollback time expires only when the OM
channel and all service channels are
faulty. If an OM channel interruption
occurs whereas services are normal, the
automatic configuration data rollback
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 multimode base station with multiple modes sharing a single board, for example, a co-
MPT multimode base station, resetting the base station or the common board on any mode
affects the services of other modes.
6.2.4.4 Activation
l Using MML commands
Run the MML command CFM CB or MOD CB to set the Automatic Rollback Switch,
Rollback Time, and Rollback Condition parameters.
l 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;
l 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 has
been enabled.
6.2.4.6 Deactivation
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;
l 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 Possible Issues

None
6.3 Transmission Link Fault Rectification

The transmission link fault rectification function is enabled by default and does not need to be
configured.

SingleRAN
NOTE
l When the transmission link fault rectification function is successfully triggered, the involved base
station is reset and services are temporarily interrupted during the reset.
l In a multimode base station where multiple modes share a board such as a main control board,
services of other modes are also affected if the base station of one mode is reset. For example, base
stations of other modes are also reset and the shared board is reset.
6.3.1 When to Use

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

None
6.3.3 Planning
None
6.3.4 Deployment
None

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 transmission link fault rectification function, the
base station will reset, during which services are temporarily interrupted.
In a multimode base station with multiple modes sharing a single board, for example, a main
control board, resetting the base station or the main control board may affect other modes.
6.3.4.4 Activation
Run the MML command SET TLFRSWITCH to set the Transmission Link Fault
Recover Switch parameter to ENABLE(Enable).
SET TLFRSWITCH: TLFRSWITCH=ENABLE;
l Using the CME

SingleRAN
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 CME Management > CME Guidelines > Getting Started

configuration 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

Run the MML command LST TLFRSWITCH to query the value of Transmission Link
Fault Recover Switch. If this parameter is set to ENABLE(Enable), the transmission link
fault rectification function has been enabled.
Run the MML command SET TLFRSWITCH to set Transmission Link Fault
Recover Switch to DISABLE(Disable).
SET TLFRSWITCH: TLFRSWITCH=DISABLE;
l 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. The method of
deactivating a feature is the same as the method of activating a feature. For details, see
Using the CME. Set the parameter listed 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 TLFRSWITCH Set this parameter

to
DISABLE(Disable
).

SingleRAN
l Using the CME to perform single configuration
On the CME, set the parameter listed in Table 6-1. For instructions on how to perform the
CME single configuration, see CME Single Configuration Operation Guide.

None

None

None
6.4 Automatic OM Channel Establishment

The automatic OM channel establishment function is enabled on a GBTS by default and is not
controlled by a switch. The following sections describe the engineering guidelines for
deploying the function on an eGBTS/NodeB/eNodeB.
6.4.1 When to Use

It is recommended that the automatic OM channel establishment function be enabled in all
scenarios.

None
6.4.3 Planning
None
6.4.4 Deployment
The deployment requirements vary depending on the OM channel networking:
l For the deployment requirements in non-IPsec networking, see section 3.3.2.3

"Configuration Requirements for the DHCP Server" and section 3.3.2.6 "Configuration
Requirements for NEs" in Automatic OMCH Establishment Feature Parameter
Description.
l For the deployment requirements in IPsec networking where the DHCP and OM packets
are protected by IPsec and other packets are completely or partially protected by IPsec,
see section 3.3.3.3 "Configuration Requirements for the Public DHCP Server", section
3.3.3.6 "Configuration Requirements for the Internal DHCP Server", and section

SingleRAN
3.3.3.10 "Configuration Requirements for Network Equipment" in Automatic OMCH

Establishment Feature Parameter Description.
l For the deployment requirements in IPsec networking where the DHCP packets are not
protected by IPsec, OM packets are protected by IPsec, and other packets are completely
or partially protected by IPsec, see section 3.3.4.3 "Configuration Requirements for the
Internal DHCP Server" and section 3.3.4.4 "Configuration Requirements for Network
Equipment" in Automatic OMCH Establishment Feature Parameter Description.
l For the deployment requirements in IPsec networking where the DHCP and OM packets
are not protected by IPsec, service and signaling packets are protected by IPsec, and
other packets are completely or partially protected by IPsec, see section 3.3.5.3
"Configuration Requirements for the Internal DHCP Server" and section 3.3.5.4
"Configuration Requirements for Network Equipment" in Automatic OMCH
l For the deployment requirements in separate-MPT multimode base stations, see section
3.4.3 "Configuration Requirements for the DHCP Server" and section 3.4.4
"Configuration Requirements for Network Equipment" in Automatic OMCH

Name
DHCPSW OMCH Auto- SWITCH Set this parameter to ENABLE(Enable).

Establishment
Switch
6.4.4.3 Precautions
In scenarios where the starting of an eGBTS/NodeB/eNodeB fails for several consecutive
times, the base station uses the minimum configuration instead of the current configuration to
trigger the automatic OM channel establishment function.
6.4.4.4 Activation
This function is enabled by default. If this function is disabled, perform the following
operations to enable it:

Run the MML command SET DHCPSW to set the OMCH Auto-Establishment
Switch parameter to ENABLE(Enable).
SET DHCPSW: SWITCH=ENABLE;
l Using the CME

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).

SingleRAN
Configuration CME Online Help

Type
Single CME Management > CME Guidelines > Getting Started

configuration 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

Run the MML command LST DHCPSW to query the value of OMCH Auto-Establishment
Switch. If this parameter is set to ENABLE(Enable), the automatic OM channel
establishment function has been enabled.
Run the MML command SET DHCPSW to set OMCH Auto-Establishment Switch to
DISABLE(Disable).
SET DHCPSW: SWITCH=DISABLE;
l 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. The method of
deactivating a feature is the same as the method of activating a feature. For details, see
Using the CME. Set the parameter listed in Table 6-2.
Table 6-2 Parameter related to the automatic OM channel establishment function
MO Sheet in the Parameter Group Remarks

Summary Data
File
DHCPSW User-defined SWITCH Set this parameter

to
DISABLE(Disable
).
l Using the CME to perform single configuration

SingleRAN
On the CME, set the parameter listed in Table 6-2. For instructions on how to perform the
CME single configuration, see CME Single Configuration Operation Guide.

None

None

None
6.5 Automatic Recovery of OM Channel Running Data

The function of automatic recovery of OM channel running data is not under switch control
and is enabled by default.
After a base station has successfully restored the OM channel by triggering this function, the
base station reports ALM-25902 Remote Maintenance Link Running Data and Configuration
Mismatch.
Run the DSP DHCPRLST command to query the running status of the base station, and then
restore services and clear the alarm based on the queried status.
l If the status is "establishing the OM channel", use either of the following methods for
rectification:
– Run the DLD CFGFILE command to deliver the correct configuration file to the
base station, and then the ACT CFGFILE command to trigger a base station reset.
– Run related commands to correct all the incorrect configurations by referring to the
alarm help and then the ACT DHCPCFG command to activate the OM channel
configurations.
l If the status is "normal", use either of the following methods for rectification:
– Run the DLD CFGFILE command to deliver the correct configuration file to the
base station, and then the ACT CFGFILE command to trigger a base station reset.
– Run related commands to correct all the incorrect configurations by referring to the
alarm help so that the alarm is cleared.

SingleRAN
Description 7 Parameters
7 Parameters
Table 7-1 Parameters

Parame NE MML Feature Feature Description
ter ID Comma ID Name
nd
TLFRS BTS390 SET None None Meaning: Indicates whether to enable the function of
WITCH 0, TLFRS clearing faults on a transmission link. If this parameter
BTS390 WITCH is set to ENABLE, a BS attempts to clear a fault by
0 LST means of automatic reset when the BS cannot be
WCDM TLFRS maintained (OMCH of the BS is disconnected) and
A, WITCH service interruption duration reaches 30 minutes. If
BTS390 the fault fails to be cleared, the BS attempts to clear
0 LTE 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)
DELAY BTS390 SET None None Meaning: Indicates whether to enable the function of
SW 0, DHCPS reestablishing the base station's remote maintenance
BTS390 W channel after a specified period.
0 LST GUI Value Range: DISABLE(Disable),
WCDM DHCPS ENABLE(Enable)
A, W
BTS390 Unit: None
0 LTE Actual Value Range: DISABLE, ENABLE
Default Value: DISABLE(Disable)

SingleRAN
Description 7 Parameters
Parame NE MML Feature Feature Description

ter ID Comma ID Name
nd
SWITC BTS390 SET WRFD- NodeB Meaning: Indicates whether to enable detection of
H 0, DHCPS 031101 Self- automatic establishment of the remote maintenance
BTS390 W discover channel.
0 LOFD-0 y Based
LST 02004 / GUI Value Range: DISABLE(Disable),
WCDM DHCPS on IP ENABLE(Enable)
A, TDLOF Mode
W D-00200 Unit: None
BTS390
0 LTE 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 (SRAN11.1 - 02)

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 (SRAN11.1 - 02)

Uploaded by

Copyright:

Available Formats

SingleRAN

Base Station OMCH Self-recovery

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2016-07-30) Huawei Proprietary and Confidential i

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

Issue 02 (2016-07-30) Huawei Proprietary and Confidential ii

6.2.7 Possible Issues........................................................................................................................................................... 18

Issue 02 (2016-07-30) Huawei Proprietary and Confidential iii

1 About This Document

l Automatic version rollback

1.2 Intended Audience

l Need to understand the features described herein.

1.3 Change History

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 1

Change Change Description Parameter

Feature Added the function of automatic recovery of OM channel None

Editorial Revised the description in 3.4 Automatic OM Channel None

SRAN11.1 Draft A (2015-12-30)

Change Change Description Parameter

Feature Added the GTMUc board to the eGBTS. None

Editorial Updated the description about the automatic version None

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 2

1.4 Differences Between Base Station Types

Function Implementation in Macro, Micro, and LampSite Base Stations

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 3

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 4

For details about each function, see the following chapters.

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 5

3.1 Automatic Version Rollback

Automatic Version Rollback for eGBTS/NodeB/eNodeB

Automatic Version Rollback for GBTS

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 6

3.2 Automatic Configuration Data Rollback

l The period of time specified by RBKTIME has not expired.

l The period of time specified by RBKTIME expires.

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 7

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

Automatic Configuration Data Rollback for GBTS

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 8

3.3 Transmission Link Fault Rectification

Transmission Link Fault Rectification for an eGBTS/NodeB/eNodeB

Transmission Link Fault Rectification for GBTS

3.4 Automatic OM Channel Establishment

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 9

Automatic OM Channel Establishment for eGBTS/NodeB/eNodeB

l In transmission network reconstruction scenarios, the SET DHCPDETECT command can be

l The delayed reestablishment switch specified by DHCPSW.DELAYSW is used when the OM

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 10

l Risks and impact of the recovery process of all OM channel-related parameters:

Automatic OM Channel Establishment for a GBTS

This function is not under switch control and is enabled by default.

3.5 Automatic Recovery of OM Channel Running Data

This function is triggered in the following scenarios:

l After configuration modification, the OM channel is disconnected and services are

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 11

Risks and impact:

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 12

Mutually Exclusive Features

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 13

Issue 02 (2016-07-30) Huawei Proprietary and Confidential 14

6.1 Automatic Version Rollback