Base Station OMCH Self-recovery(SRAN9.0_Draft a)

SingleRAN

Base Station OMCH Self-recoveryFeature Parameter Description

Issue Draft A

Date 2014-01-20

HUAWEI TECHNOLOGIES CO., LTD.

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

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue Draft A (2014-01-20) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

Contents

1 About This Document..................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................1

2 Overview.........................................................................................................................................22.1 Introduction....................................................................................................................................................................22.2 Benefits...........................................................................................................................................................................2

3 Automatic Version Rollback.......................................................................................................33.1 Automatic Version Rollback for eGBTS/NodeB/eNodeB.............................................................................................43.2 Automatic Version Rollback for GBTS.........................................................................................................................4

4 Automatic Configuration Data Rollback..................................................................................54.1 Automatic Configuration Data Rollback for eGBTS/NodeB/eNodeB...........................................................................54.2 Automatic Configuration Data Rollback for GBTS.......................................................................................................6

5 Transmission Link Fault Rectification......................................................................................75.1 Transmission Link Fault Rectification for eGBTS/NodeB/eNodeB..............................................................................85.2 Transmission Link Fault Rectification for GBTS..........................................................................................................8

6 Related Features.............................................................................................................................9

7 Network Impact...........................................................................................................................10

8 Engineering Guidelines.............................................................................................................118.1 Engineering Guidelines for Automatic Version Rollback............................................................................................118.2 Engineering Guidelines for Automatic Configuration Data Rollback.........................................................................118.2.1 When to Use Automatic Configuration Data Rollback for eGBTS/NodeB/eNodeB................................................118.2.2 Required Information................................................................................................................................................118.2.3 Planning.....................................................................................................................................................................128.2.4 Deployment...............................................................................................................................................................128.2.4.1 Requirements..........................................................................................................................................................128.2.4.2 Data Preparation.....................................................................................................................................................128.2.4.3 Activation...............................................................................................................................................................138.2.4.4 Activation Observation...........................................................................................................................................148.2.4.5 Deactivation............................................................................................................................................................14

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription Contents


ii

8.2.5 Performance Monitoring............................................................................................................................................148.2.6 Parameter Optimization.............................................................................................................................................148.2.7 Troubleshooting.........................................................................................................................................................148.3 Engineering Guidelines for Transmission Link Fault Rectification.............................................................................148.3.1 When to Use Transmission Link Fault Rectification................................................................................................158.3.2 Required Information................................................................................................................................................158.3.3 Planning.....................................................................................................................................................................158.3.4 Deployment...............................................................................................................................................................158.3.4.1 Requirements..........................................................................................................................................................158.3.4.2 Data Preparation.....................................................................................................................................................158.3.4.3 Activation...............................................................................................................................................................158.3.4.4 Activation Observation...........................................................................................................................................178.3.4.5 Deactivation............................................................................................................................................................188.3.5 Performance Monitoring............................................................................................................................................188.3.6 Parameter Optimization.............................................................................................................................................188.3.7 Troubleshooting.........................................................................................................................................................18

9 Parameters.....................................................................................................................................19

10 Counters......................................................................................................................................21

11 Glossary.......................................................................................................................................22

12 Reference Documents...............................................................................................................23

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription Contents


iii

1 About This Document

1.1 ScopeThis document describes the Base Station OMCH Self-recovery feature. It consists of threefunctions: automatic version rollback, automatic configuration data rollback, and transmissionlink fault rectification.

1.2 Intended AudienceThis document is intended for personnel who:

l Need to understand the features described herein.l Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes, which are defined as follows:

l Feature changeChanges in features of a specific product version

l Editorial changeChanges in wording or addition of information that was not described in the earlier version

Draft A (2014-01-20)This document is created for SRAN9.0.

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 1 About This Document


1

2 Overview

2.1 IntroductionThe OM channel (OMCH for short) of base stations refers to the channel through which theeGBTS/NodeB/eNodeB communicates with the U2000 or the GBTS communicates with theBSC to exchange the operation and maintenance information about base stations.

If an OMCH interruption occurs, measures are taken remotely to recover the OMCH. Theserecovery measures include the following:

l Automatic version rollbackl Automatic configuration data rollbackl Transmission link fault rectification

2.2 BenefitsIf an OMCH interruption occurs, the Base Station OMCH Self-recovery feature reduces the needof onsite handling and thereby, saving costs and shortening the interruption time.

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 2 Overview


2

3 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 thatfor a GBTS. The details are described in the following sections.

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 3 Automatic Version Rollback


3

3.1 Automatic Version Rollback for eGBTS/NodeB/eNodeBAfter the software versions of NEs are upgraded, the NEs will be reset. After the NEs arerestarted, if the following faults occur, their software versions will be rolled back to the sourceversion and ALM-26255 Automatic Version Rollback will be reported:

l The NEs detect that the current version fails to be initialized.l The NEs detect that the OMCH of the current version has not been successfully connected

and the interruption lasts 30 minutes.

After the hot patch of an NE software version takes effect, if the following faults occur, the hotpatch will be rolled back to the original state and ALM-26255 Automatic Version Rollback willbe reported:

l The base station abnormally resets within ten minutes after the hot patch is activatedl The OMCH is disconnected within ten minutes after the hot patch is activated and then the

base station resets (for example, the transmission link fault rectification function istriggered).

3.2 Automatic Version Rollback for GBTSAfter a version upgrade, if the NE resets after running for less than five minutes and thisphenomenon occurs thrice, the software version will be automatically rolled back to the sourceversion and ALM-26255 Automatic Version Rollback will be reported.

The GBTS does not support the automatic version rollback of hot patch.

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 3 Automatic Version Rollback


4

4 Automatic Configuration Data Rollback

4.1 Automatic Configuration Data Rollback for eGBTS/NodeB/eNodeB

The automatic configuration data rollback function applies to the scenario where users want toroll back the configuration data about OMCH after data modification. This function does notrequire onsite handling. In some cases, for example, when the IP address, router, or IPsec addressis incorrectly modified, users can enable the automatic configuration data rollback function toavoid long OMCH interruptions and recovery failures.

To enable this function, run the MML command CFM CB to set AUTORBKSW to ENABLE(Enable) and specify the RBKTIME and RBKCONDITION parameters.

NOTE

The judgment of OMCH interruption in RBKCONDITION is made as follows: After the automaticconfiguration data rollback function is enabled, the OMCH interruption lasts more than five minutes beforethe period of time specified by RBKTIME expires.

When the automatic configuration data rollback is being enabled, the system backs up the currentconfiguration data.

l The period of time specified by RBKTIME has not expired.If the OMCH is normal after its configuration data is modified and users do not requirerollback in spite of an OMCH interruption, run the MML command MOD CB to disablethe automatic configuration data rollback function. This prevents the rollback of theconfiguration data in the case of an OMCH interruption.

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 4 Automatic Configuration Data Rollback


5

NOTE

Incorrect modification of certain data will not lead to immediate OMCH interruption. The OMCHinterruption occurs only after renegotiation with the peer NE about the modified data. Such data includesparameters in IPSECPROPOSAL, IKEPROPOSAL, and IKECFG MOs.Perform the followingoperations to resolve the preceding issue:

l Before the period of time specified by RBKTIME expires, if the OMCH works properly, run the MMLcommand MOD CB to disable the automatic configuration data rollback function after therenegotiation takes effect.

l After the period of time specified by RBKTIME expires, the automatic configuration data rollbackfunction cannot be triggered if the OMCH interruption occurs after renegotiation.

l Run the MML command DSP IKESA or DSP IPSECSA to query the time of the next renegotiation.

l If you run the MML command CFM CB to back up data before the renegotiation, the data may beincorrect even if the OMCH works properly.

Before the period of time specified by RBKTIME expires, if the base station resets and relatedconditions are met, the automatic configuration data rollback function will be triggered.

l The period of time specified by RBKTIME expires.

– If the OMCH works properly, the automatic configuration data rollback function willbe automatically disabled.

– If rollback conditions specified by the RBKCONDITION parameter are met,configuration data will be automatically rolled back to the backup data and ALM-26255Automatic Version Rollback will be reported. The base station resets and then disablesthe automatic configuration data rollback function.

NOTE

If ALM-26255 Automatic Version Rollback is reported with the value of alarm cause being ConfigurationData, this alarm is triggered by the automatic configuration data rollback function.

When this function is enabled on a batch of base stations, the external transmission link for some basestations may be continuously interrupted. If rollback conditions are met, the automatic configuration datarollback function will be triggered.

When an OMCH interruption is caused by the batch configuration of base stations, if the U2000 does notfinish the configuration after the period of time specified by RBKTIME expires. This function is triggeredonly after the batch configuration is finished, if rollback conditions 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 rollback conditions are met, the automatic configuration datarollback function will be triggered. At this time, if the board has not been activated, the rollback willfail. Therefore, users are advised to consider the time required for board activation (about ten minutes)when setting the RBKTIME parameter.

l After the period of time specified by RBKTIME expires, users need to reconfigure theautomatic configuration data rollback function if they want to enable this function.

When the configuration data of base stations is being modified, the configuration data ofperipheral NEs may also be modified. After the automatic configuration data rollback functionis enabled, the configuration data of base stations is rolled back. Meanwhile, the data ofperipheral NEs also needs to be rolled back to ensure a normal OMCH. Therefore, the datamodification of peripheral NEs during this period and the rollback methods must be obtained.

4.2 Automatic Configuration Data Rollback for GBTSThe GBTS does not support the automatic configuration data rollback function.

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 4 Automatic Configuration Data Rollback


6

5 Transmission Link Fault Rectification

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

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 5 Transmission Link Fault Rectification


7

5.1 Transmission Link Fault Rectification for eGBTS/NodeB/eNodeB

This function enables the base station to initiate a warm reset when an OMCH interruptionoccurs. The reset helps resolve certain issues and avoids onsite handling.

To enable the transmission link fault rectification function, run the MML command SETTLFRSWITCH with TLFRSWITCH set to ENABLE(Enable). If the base station cannot bemaintained due to OMCH interruption and services are interrupted for 45 minutes, the basestation automatically resets to rectify the fault. If the fault persists, the base station attempts torectify the fault in the same way after the service interruption lasts 480 minutes.

NOTE

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

5.2 Transmission Link Fault Rectification for GBTSAfter the OMCH between the GBTS and BSC is interrupted for 15 minutes, the base stationinitiates a warm reset to recover the faults and avoids onsite handling.

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

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 5 Transmission Link Fault Rectification


8

6 Related Features

Prerequisite FeaturesNone

Mutually Exclusive FeaturesNone

Impacted FeaturesNone

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 6 Related Features


9

7 Network Impact

System CapacityNone

Network PerformanceNone

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 7 Network Impact


10

8 Engineering Guidelines

8.1 Engineering Guidelines for Automatic Version RollbackThe automatic version rollback function is enabled by default and does not need to be configured.

NOTE

After the system triggers the automatic version rollback function, ALM-26255 Automatic Version Rollbackwill be reported.

8.2 Engineering Guidelines for Automatic ConfigurationData Rollback

The GBTS does not support the automatic configuration data rollback function.

The following sections describe the engineering guidelines for this function on an eGBTS/NodeB/eNodeB.

8.2.1 When to Use Automatic Configuration Data Rollback foreGBTS/NodeB/eNodeB

Modifying the radio configuration parameters does not lead to OMCH interruption, so theautomatic configuration data rollback function does not need to be enabled.

However, modifying the configuration data related to OMCH may cause continuous OMCHinterruption, which cannot be remotely recovered. You are advised to enable the automaticconfiguration data rollback function in this scenario.

Users are not advised to enable this function when performing operations onsite.

8.2.2 Required InformationEach time before enabling the automatic configuration data rollback function, users must collectthe modified data of peripheral NEs and corresponding rollback methods.

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 8 Engineering Guidelines


11

8.2.3 PlanningNone

8.2.4 Deployment

8.2.4.1 RequirementsNone

8.2.4.2 Data Preparation

MO Parameter Name Parameter ID Setting Notes

- AutomaticRollback Switch

AUTORBKSW

In scenarios where only the radioconfiguration parameters are modified, setthis switch to off.Set this switch to on when modifying theconfiguration data of base stations becauseit may cause continuous OMCHinterruptions and recovery failures.



12

MO Parameter Name Parameter ID Setting Notes

- Rollback Time RBKTIME Set the value of this parameter based on theactual situations.If this parameter is set to a too large value,the OMCH may be interrupted for a longtime (services may also be interrupted fora long time). If this parameter is set to a toosmall value, the automatic configurationdata rollback function cannot take mucheffect in data protection.Assume that this parameter is set to 240minutes. If users incorrectly configure aparameter 20 minutes after this function isenabled and the OMCH and services areinterrupted, the system will wait 220minutes before triggering this function.Such a long interruption affects userexperiences.Assume that this parameter is set to 10minutes. If users incorrectly configure aparameter after this function is enabledand the OMCH and services areinterrupted, the system will wait twominutes and determines whether theOMCH is continuously interrupted (TheOMCH is considered as interrupted if theinterruption lasts five minutes). In thissituation, the rollback conditions are notmet, so the system will not trigger theautomatic configuration data rollbackfunction.Therefore, users must reserve time formodifying the configuration and set theappropriate rollback time.

- RollbackCondition

RBKCONDITION

Set parameter to OMCH_FAULT(OMCH_FAULT) in most cases.

8.2.4.3 Activation

Using MML CommandsRun the MML command CFM CB to set the Automatic Rollback Switch, Rollback Time,and Rollback Condition parameters.



13

MML Command ExamplesCFM CB: MODE=UNFORCED, 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.

8.2.4.4 Activation Observation

Run the MML command DSP CB to query the value of Automatic Rollback Switch. If thisparameter is set to ENABLE(Enable), the automatic configuration data rollback function isenabled.

8.2.4.5 Deactivation

Using MML Commands

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

MML Command ExamplesMOD CB: NAME="Rollback CB 1", COMMENT="CB for Rollback", AUTORBKSW = DISABLE;

Using the CME

You cannot use the CME to configure this function.

8.2.5 Performance MonitoringNone

8.2.6 Parameter OptimizationNone

8.2.7 TroubleshootingNone

8.3 Engineering Guidelines for Transmission Link FaultRectification

The transmission link fault rectification function is enabled by default on a GBTS and does notneed to be configured.

The following sections describe the engineering guidelines for this function on an eGBTS/NodeB/eNodeB.



14

8.3.1 When to Use Transmission Link Fault RectificationIt is recommended that the transmission link fault rectification function be enabled.

8.3.2 Required InformationNone

8.3.3 PlanningNone

8.3.4 Deployment

8.3.4.1 RequirementsNone

8.3.4.2 Data PreparationMO Parameter

NameParameter ID Setting Notes

TLFRSWITCH

Transmission LinkFault RecoverSwitch

TLFRSWITCH

Set this parameter to ENABLE(Enable).

8.3.4.3 Activation

Using MML CommandsRun the MML command SET TLFRSWITCH to set the Transmission Link Fault RecoverSwitch parameter to ENABLE(Enable).

MML Command ExamplesSET TLFRSWITCH: TLFRSWITCH=ENABLE;

Using the CME to Perform Single ConfigurationOn the CME, set the parameters listed in the Data Preparation section. For instructions on howto perform the CME single configuration, see CME Single Configuration Operation Guide.

Using the CME to Perform Batch Configuration for Newly Deployed Base StationsEnter the data listed in Table 8-1 in a summary data file, which also contains other data for thenew base stations to be deployed. Then, import the summary data file into the CME for batchconfiguration.

Prepare the summary data file as follows:



15

l The managed objects (MOs) in Table 8-1are contained in a scenario-specific summary datafile. In this situation, set the parameters in the MOs, and then verify and save the file.

l Some MOs in Table 8-1 are not contained in a scenario-specific summary data file. In thissituation, customize a summary data file to include the MOs before you can set theparameters.

Table 8-1 Parameters related to the transmission link fault rectification function

MO Sheet in theSummary DataFile

Parameter Group Remarks

TLFRSWITCH User-defined sheet TLFRSWITCH Set this parameterto ENABLE(Enable).

For detailed instructions, see the following sections in 3900 Series Base Station InitialConfiguration Guide.

l For the NodeB, see section "Creating NodeB in Batches."l For the eNodeB, see section "Creating eNodeB in Batches."l For separate-MPT multimode base stations, see section "Creating Separate-MPT

Multimode Base Stations in Batches."l For co-MPT base stations, see section "Creating Co-MPT Base Stations in Batches."

NOTE

NodeBs refer to base stations configured with the WMPT or UMPT_U.

eNodeBs refer to base stations configured with LMPT or UMPT_L.

Co-MPT base stations refer to base stations configured with UMPT_GU, UMPT_GL, UMPT_UL, orUMPT_GUL. Such base stations incorporate functions of the eGBTS, NodeB, and eNodeB.

Separate-MPT multimode base stations refer to base stations where multiple modes are deployed ondifferent main control boards. For example, base stations configured with the GTMU and WMPT are namedseparate-MPT GU dual-mode base stations.

Using the CME to Perform Batch Configuration for Existing Base StationsBatch reconfiguration using the CME is the recommended method to activate a feature onexisting base stations. This method reconfigures all data, except neighbor relationships.

Step 1 Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or chooseAdvanced > Customize Summary Data File (CME client mode), to customize a summary datafile for batch configuration.

NOTE

For context-sensitive help on a current task in the client, press F1.

Step 2 Export the NE data saved on the CME to the customized summary data file. The CME menusfor co-MPT and separate-MPT base stations are different from that for single-mode base stations.

1. For a co-MPT base station, choose CME > SRAN Application > MBTS Application >Export Data > Export Base Station Summary Data (U2000 client mode) or CME >SRAN Application > MBTS Application > Export Data > Export Base Station



16

Summary Data (CME client mode), to export the NE data stored on the CME into thecustomized summary data file.

2. For a separate-MPT multimode base station or a single-mode GSM base station, chooseCME > GSM Application > Export Data > Export eGBTS Bulk Configuration Data(U2000 client mode), or choose GSM Application > Export Data > Export eGBTS BulkConfiguration Data (CME client mode), to export the eGBTS data stored on the CMEinto the customized summary data file.

3. For a separate-MPT multimode base station or a single-mode UMTS base station, chooseCME > UMTS Application > Export Data > Export Base Station Bulk ConfigurationData (U2000 client mode), or choose UMTS Application > Export Data > Export BaseStation Bulk Configuration Data (CME client mode), to export the UMTS data storedon the CME into the customized summary data file.

4. For a separate-MPT multimode base station or a single-mode LTE base station, chooseCME > LTE Application > Export Data > Export Base Station Bulk ConfigurationData (U2000 client mode), or choose LTE Application > Export Data > Export BaseStation Bulk Configuration Data (CME client mode), to export the eNodeB data storedon the CME into the customized summary data file.

Step 3 In the summary data file, set the parameters in the MOs listed in Table 8-1 and close the file.

Step 4 Import the summary data file into the CME. The CME menus for co-MPT and separate-MPTbase stations are different from that for single-mode base stations.

1. For a co-MPT base station, choose CME > SRAN Application > MBTS Application >Import Data > Import Base Station Summary Data (U2000 client mode) or CME >SRAN Application > MBTS Application > Import Data > Import Base StationSummary Data (CME client mode) to import the summary data file into the CME.

2. For a separate-MPT multimode base station or a single-mode GSM base station, chooseCME > GSM Application > Import Data > Import eGBTS Bulk Configuration Data(U2000 client mode), or choose GSM Application > Import Data > Import eGBTS BulkConfiguration Data (CME client mode), to import the summary data file into the CME.

3. For a separate-MPT multimode base station or a single-mode UMTS base station, chooseCME > UMTS Application > Import Data > Import Base Station Bulk ConfigurationData (U2000 client mode), or choose UMTS Application > Import Data > Import BaseStation Bulk Configuration Data (CME client mode), to import the summary data fileinto the CME.

4. For a separate-MPT multimode base station or a single-mode LTE base station, chooseCME > LTE Application > Import Data > Import Base Station Bulk ConfigurationData (U2000 client mode), or choose LTE Application > Import Data > Import BaseStation Bulk Configuration Data (CME client mode), to import the summary data fileinto the CME.

----End

8.3.4.4 Activation Observation

Run the MML command LST TLFRSWITCH to query the value of the Transmission LinkFault Recover Switch parameter. If the parameter is set to ENABLE(Enable), the transmissionlink fault rectification function is enabled.



17

8.3.4.5 Deactivation

Using MML CommandsRun the MML command SET TLFRSWITCH to set the Transmission Link Fault RecoverSwitch parameter to DISABLE(Disable).

MML Command ExamplesSET TLFRSWITCH: TLFRSWITCH=DISABLE;

Using the CME to Perform Batch ConfigurationBatch reconfiguration using the CME is the recommended method to deactivate a feature. Thismethod reconfigures all data, except neighbor relationships. Using this method to deactivate afeature is the same as to activate a feature. For details, see Using the CME to Perform BatchConfiguration for Existing Base Stations. Set the parameter, as shown in Table 8-2.

Table 8-2 Parameters related to the transmission link fault rectification function

MO Sheet in theSummary Data File

Parameter Group Remarks

TLFRSWITCH User-defined sheet TLFRSWITCH Set this parameter toDISABLE(Disable).

Using the CME to Perform Single ConfigurationOn the CME, set the parameters listed in the Data Preparation section. For instructions on howto perform the CME single configuration, see CME Single Configuration Operation Guide.

8.3.5 Performance MonitoringNone

8.3.6 Parameter OptimizationNone

8.3.7 TroubleshootingNone



18

9 Parameters

Table 9-1 Parameter description

Parameter ID NE MMLCommand

Feature ID Feature Name Description

TLFRSWITCH BTS3900,BTS3900WCDMA,BTS3900 LTE

SETTLFRSWITCHLSTTLFRSWITCH

None None Meaning:Indi-cates whether toenable thefunction ofclearing faultson atransmissionlink. If thisparameter is setto ENABLE, aBS attempts toclear a fault bymeans ofautomatic resetwhen the BScannot bemaintained(OMCH of theBS isdisconnected)and serviceinterruptionduration reaches45 minutes. Ifthe fault fails tobe cleared, theBS attempts toclear the faultagain in thesame way whenthe service

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 9 Parameters


19

Parameter ID NE MMLCommand

Feature ID Feature Name Description

interruptionduration reaches480 minutes. Ifthe fault fails tobe cleared afterthe two resets,the BS stopsperformingautomatic reset.The serviceinterruptionduration atwhich the BSautomaticallyresets has fixedvalues (45minutes and 480minutes) and isnotconfigurable.GUI ValueRange:DISABLE(Disable),ENABLE(Enable)Unit:NoneActual ValueRange:DISABLE, ENABLEDefaultValue:ENABLE(Enable)

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 9 Parameters


20

10 Counters

There are no specific counters associated with this feature.

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 10 Counters


21

11 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 11 Glossary


22

12 Reference Documents

1. 3900 Series Base Station Initial Configuration Guide

SingleRANBase Station OMCH Self-recovery Feature ParameterDescription 12 Reference Documents


23