eRAN

V100R017C10

Reconfiguration Guide

Issue 04
Date 2023-03-25

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2023. 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: https://www.huawei.com
Email: support@huawei.com

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. i

eRAN
Reconfiguration Guide Contents

Contents

1 eRAN Reconfiguration Guide................................................................................................1

1.1 Changes in eRAN Reconfiguration Guide....................................................................................................................... 2
1.2 Introduction to eRAN Reconfiguration............................................................................................................................ 4
1.2.1 Definition of eRAN Reconfiguration..............................................................................................................................4
1.2.2 General Prerequisites.......................................................................................................................................................... 6
1.2.3 Transmission Configuration Models.............................................................................................................................. 6
1.2.4 Introduction to the Reconfiguration Tools.................................................................................................................. 7
1.3 General Operation Guide................................................................................................................................................... 15
1.3.1 MAE-Deployment Operation Guide............................................................................................................................ 15
1.3.2 Running MML Commands on the LMT..................................................................................................................... 18
1.3.3 Running MML Commands on the MAE-Access...................................................................................................... 19
1.4 Reconfiguration Scenario Overview............................................................................................................................... 22
1.5 Cell Data Reconfigurations................................................................................................................................................ 33
1.5.1 Adding an FDD/NB-IoT Cell (Common Scenarios)................................................................................................ 33
1.5.1.1 Scheme Overview.......................................................................................................................................................... 33
1.5.1.2 Engineering Preparation.............................................................................................................................................. 36
1.5.1.3 Engineering Implementation..................................................................................................................................... 42
1.5.1.4 Engineering Verification.............................................................................................................................................. 45
1.5.1.5 Engineering Rollback.................................................................................................................................................... 46
1.5.2 Adding an FDD Cell (Dual-Carrier Capacity Expansion Scenarios)..................................................................47
1.5.2.1 Scheme Overview.......................................................................................................................................................... 47
1.5.2.2 Engineering Preparation.............................................................................................................................................. 50
1.5.2.3 Engineering Implementation..................................................................................................................................... 54
1.5.2.4 Engineering Verification.............................................................................................................................................. 56
1.5.2.5 Engineering Rollback.................................................................................................................................................... 57
1.5.3 Adding a TDD Cell (Common Scenarios).................................................................................................................. 58
1.5.3.1 Scheme Overview.......................................................................................................................................................... 58
1.5.3.2 Engineering Preparation.............................................................................................................................................. 61
1.5.3.3 Engineering Implementation..................................................................................................................................... 66
1.5.3.4 Engineering Verification.............................................................................................................................................. 69
1.5.3.5 Engineering Rollback.................................................................................................................................................... 70
1.5.4 Adding a TDD Cell (Multi-Carrier Capacity Expansion Scenarios)................................................................... 70
1.5.4.1 Scheme Overview.......................................................................................................................................................... 70

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
Reconfiguration Guide Contents

1.5.4.2 Engineering Preparation.............................................................................................................................................. 74

1.5.4.3 Engineering Implementation..................................................................................................................................... 79
1.5.4.4 Engineering Verification.............................................................................................................................................. 81
1.5.4.5 Engineering Rollback.................................................................................................................................................... 82
1.5.5 Adding an Indoor Distributed Cell (TDD)................................................................................................................. 82
1.5.5.1 Scheme Overview.......................................................................................................................................................... 83
1.5.5.2 Engineering Preparation.............................................................................................................................................. 85
1.5.5.3 Engineering Implementation..................................................................................................................................... 90
1.5.5.4 Engineering Verification.............................................................................................................................................. 92
1.5.5.5 Engineering Rollback.................................................................................................................................................... 92
1.5.6 Changing the Cell Bandwidth....................................................................................................................................... 93
1.5.6.1 Scheme Overview.......................................................................................................................................................... 93
1.5.6.2 Engineering Preparation.............................................................................................................................................. 97
1.5.6.3 Engineering Implementation................................................................................................................................... 101
1.5.6.4 Engineering Verification............................................................................................................................................ 103
1.5.6.5 Engineering Rollback.................................................................................................................................................. 104
1.5.7 Changing the TX/RX Mode of a Cell.........................................................................................................................105
1.5.7.1 Scheme Overview........................................................................................................................................................ 105
1.5.7.2 Engineering Preparation............................................................................................................................................ 109
1.5.7.3 Engineering Implementation................................................................................................................................... 114
1.5.7.4 Engineering Verification............................................................................................................................................ 116
1.5.7.5 Engineering Rollback.................................................................................................................................................. 117
1.5.8 Changing the Coverage Radius of a Cell................................................................................................................ 118
1.5.8.1 Scheme Overview........................................................................................................................................................ 118
1.5.8.2 Engineering Preparation............................................................................................................................................ 118
1.5.8.3 Engineering Implementation................................................................................................................................... 120
1.5.8.4 Engineering Verification............................................................................................................................................ 121
1.5.8.5 Engineering Rollback.................................................................................................................................................. 122
1.5.9 Changing the EARFCNs of a Cell............................................................................................................................... 123
1.5.9.1 Scheme Overview........................................................................................................................................................ 123
1.5.9.2 Engineering Preparation............................................................................................................................................ 124
1.5.9.3 Engineering Implementation................................................................................................................................... 126
1.5.9.4 Engineering Verification............................................................................................................................................ 128
1.5.9.5 Engineering Rollback.................................................................................................................................................. 128
1.5.10 Changing the PCI of a Cell........................................................................................................................................ 129
1.5.10.1 Scheme Overview......................................................................................................................................................129
1.5.10.2 Engineering Preparation......................................................................................................................................... 130
1.5.10.3 Engineering Implementation................................................................................................................................ 132
1.5.10.4 Engineering Verification..........................................................................................................................................133
1.5.10.5 Engineering Rollback............................................................................................................................................... 134
1.5.11 Changing the Cell ID................................................................................................................................................... 135
1.5.11.1 Scheme Overview......................................................................................................................................................135

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
Reconfiguration Guide Contents

1.5.11.2 Engineering Preparation......................................................................................................................................... 136

1.5.11.3 Engineering Implementation................................................................................................................................ 138
1.5.11.4 Engineering Verification..........................................................................................................................................140
1.5.11.5 Engineering Rollback............................................................................................................................................... 140
1.5.12 Changing the Local Cell ID........................................................................................................................................ 141
1.5.12.1 Scheme Overview......................................................................................................................................................141
1.5.12.2 Engineering Preparation......................................................................................................................................... 142
1.5.12.3 Engineering Implementation................................................................................................................................ 143
1.5.12.4 Engineering Verification..........................................................................................................................................144
1.5.12.5 Engineering Rollback............................................................................................................................................... 145
1.5.13 Changing the TAC......................................................................................................................................................... 145
1.5.13.1 Scheme Overview......................................................................................................................................................146
1.5.13.2 Engineering Preparation......................................................................................................................................... 146
1.5.13.3 Engineering Implementation................................................................................................................................ 148
1.5.13.4 Engineering Verification..........................................................................................................................................150
1.5.13.5 Engineering Rollback............................................................................................................................................... 150
1.5.14 Changing the Neighboring Cell Parameters........................................................................................................151
1.5.14.1 Scheme Overview......................................................................................................................................................151
1.5.14.2 Engineering Preparation......................................................................................................................................... 152
1.5.14.3 Engineering Implementation................................................................................................................................ 154
1.5.14.4 Engineering Verification..........................................................................................................................................156
1.5.14.5 Engineering Rollback............................................................................................................................................... 156
1.5.15 Changing the Intra-Frequency Handover Offset............................................................................................... 157
1.5.15.1 Scheme Overview......................................................................................................................................................157
1.5.15.2 Engineering Preparation......................................................................................................................................... 157
1.5.15.3 Engineering Implementation................................................................................................................................ 159
1.5.15.4 Engineering Verification..........................................................................................................................................160
1.5.15.5 Engineering Rollback............................................................................................................................................... 161
1.5.16 Changing the Cell Power........................................................................................................................................... 162
1.5.16.1 Scheme Overview......................................................................................................................................................162
1.5.16.2 Engineering Preparation......................................................................................................................................... 165
1.5.16.3 Engineering Implementation................................................................................................................................ 169
1.5.16.4 Engineering Verification..........................................................................................................................................170
1.5.16.5 Engineering Rollback............................................................................................................................................... 171
1.5.17 Changing a Cell to SFN Mode (Intra-BBU)......................................................................................................... 172
1.5.17.1 Scheme Overview......................................................................................................................................................173
1.5.17.2 Engineering Preparation......................................................................................................................................... 176
1.5.17.3 Engineering Implementation................................................................................................................................ 182
1.5.17.4 Engineering Verification..........................................................................................................................................184
1.5.17.5 Engineering Rollback............................................................................................................................................... 184
1.5.18 Changing a Cell to SFN Mode (Inter-BBU)..........................................................................................................185
1.5.18.1 Scheme Overview......................................................................................................................................................185

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
Reconfiguration Guide Contents

1.5.18.2 Engineering Preparation......................................................................................................................................... 189

1.5.18.3 Engineering Implementation................................................................................................................................ 199
1.5.18.4 Engineering Verification..........................................................................................................................................201
1.5.18.5 Engineering Rollback............................................................................................................................................... 202
1.5.19 Binding Baseband Equipment.................................................................................................................................. 203
1.5.19.1 Scheme Overview......................................................................................................................................................203
1.5.19.2 Engineering Preparation......................................................................................................................................... 205
1.5.19.3 Engineering Implementation................................................................................................................................ 207
1.5.19.4 Engineering Verification..........................................................................................................................................207
1.5.19.5 Engineering Rollback............................................................................................................................................... 208
1.5.20 Enabling Automatic Binding of Baseband Equipment ................................................................................... 209
1.5.20.1 Scheme Overview......................................................................................................................................................209
1.5.20.2 Engineering Preparation......................................................................................................................................... 210
1.5.20.3 Engineering Implementation................................................................................................................................ 212
1.5.20.4 Engineering Verification..........................................................................................................................................214
1.5.20.5 Engineering Rollback............................................................................................................................................... 214
1.5.21 Changing the Baseband Equipment for a Cell................................................................................................... 215
1.5.21.1 Scheme Overview......................................................................................................................................................215
1.5.21.2 Engineering Preparation......................................................................................................................................... 218
1.5.21.3 Engineering Implementation................................................................................................................................ 220
1.5.21.4 Engineering Verification..........................................................................................................................................221
1.5.21.5 Engineering Rollback............................................................................................................................................... 221
1.5.22 Changing the Uplink-Downlink Subframe Configuration (TDD)................................................................. 222
1.5.22.1 Scheme Overview......................................................................................................................................................222
1.5.22.2 Engineering Preparation......................................................................................................................................... 223
1.5.22.3 Engineering Implementation................................................................................................................................ 225
1.5.22.4 Engineering Verification..........................................................................................................................................227
1.5.22.5 Engineering Rollback............................................................................................................................................... 227
1.5.23 Changing the Special Subframe Configuration (TDD).................................................................................... 227
1.5.23.1 Scheme Overview......................................................................................................................................................228
1.5.23.2 Engineering Preparation......................................................................................................................................... 228
1.5.23.3 Engineering Implementation................................................................................................................................ 230
1.5.23.4 Engineering Verification..........................................................................................................................................232
1.5.23.5 Engineering Rollback............................................................................................................................................... 232
1.5.24 Adjusting Association Relationships Between Cells and RF Modules........................................................ 233
1.5.24.1 Scheme Overview......................................................................................................................................................233
1.5.24.2 Engineering Preparation......................................................................................................................................... 234
1.5.24.3 Engineering Implementation................................................................................................................................ 237
1.5.24.4 Engineering Verification..........................................................................................................................................239
1.5.24.5 Engineering Rollback............................................................................................................................................... 239
1.5.25 Deleting a Cell............................................................................................................................................................... 240
1.5.25.1 Scheme Overview......................................................................................................................................................240

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. v

eRAN
Reconfiguration Guide Contents

1.5.25.2 Engineering Preparation......................................................................................................................................... 242

1.5.25.3 Engineering Implementation................................................................................................................................ 244
1.5.25.4 Engineering Verification..........................................................................................................................................247
1.5.25.5 Engineering Rollback............................................................................................................................................... 247
1.5.26 Co-BBP 4T4R and 8T8R Cells.................................................................................................................................... 248
1.5.26.1 Scheme Overview......................................................................................................................................................248
1.5.26.2 Engineering Preparation......................................................................................................................................... 249
1.5.26.3 Engineering Implementation................................................................................................................................ 251
1.5.26.4 Engineering Verification..........................................................................................................................................253
1.5.26.5 Engineering Rollback............................................................................................................................................... 254
1.6 Base Station Data Reconfigurations............................................................................................................................ 255
1.6.1 Changing the eNodeB from Independent Operator Mode to RAN Sharing with Common Carrier
Mode.............................................................................................................................................................................................. 255
1.6.1.1 Scheme Overview........................................................................................................................................................ 255
1.6.1.2 Engineering Preparation............................................................................................................................................ 259
1.6.1.3 Engineering Implementation................................................................................................................................... 264
1.6.1.4 Engineering Verification............................................................................................................................................ 265
1.6.1.5 Engineering Rollback.................................................................................................................................................. 266
1.6.2 Changing the eNodeB from Independent Operator Mode to RAN Sharing with Dedicated Carrier
Mode.............................................................................................................................................................................................. 268
1.6.2.1 Scheme Overview........................................................................................................................................................ 268
1.6.2.2 Engineering Preparation............................................................................................................................................ 271
1.6.2.3 Engineering Implementation................................................................................................................................... 276
1.6.2.4 Engineering Verification............................................................................................................................................ 277
1.6.2.5 Engineering Rollback.................................................................................................................................................. 278
1.6.3 Changing the eNodeB from Independent Operator Mode to Hybrid RAN Sharing Mode................... 280
1.6.3.1 Scheme Overview........................................................................................................................................................ 280
1.6.3.2 Engineering Preparation............................................................................................................................................ 283
1.6.3.3 Engineering Implementation................................................................................................................................... 289
1.6.3.4 Engineering Verification............................................................................................................................................ 291
1.6.3.5 Engineering Rollback.................................................................................................................................................. 292
1.6.4 Adding a Neighboring eNodeB.................................................................................................................................. 293
1.6.4.1 Scheme Overview........................................................................................................................................................ 293
1.6.4.2 Engineering Preparation............................................................................................................................................ 297
1.6.4.3 Engineering Implementation................................................................................................................................... 302
1.6.4.4 Engineering Verification............................................................................................................................................ 303
1.6.4.5 Engineering Rollback.................................................................................................................................................. 304
1.6.5 Changing the eNodeB Names.................................................................................................................................... 305
1.6.5.1 Scheme Overview........................................................................................................................................................ 305
1.6.5.2 Engineering Preparation............................................................................................................................................ 306
1.6.5.3 Engineering Implementation................................................................................................................................... 307
1.6.5.4 Engineering Verification............................................................................................................................................ 308
1.6.5.5 Engineering Rollback.................................................................................................................................................. 308

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. vi

eRAN
Reconfiguration Guide Contents

1.6.6 Changing the eNodeB ID..............................................................................................................................................308

1.6.6.1 Scheme Overview........................................................................................................................................................ 308
1.6.6.2 Engineering Preparation............................................................................................................................................ 309
1.6.6.3 Engineering Implementation................................................................................................................................... 312
1.6.6.4 Engineering Verification............................................................................................................................................ 313
1.6.6.5 Engineering Rollback.................................................................................................................................................. 316
1.6.7 Adjusting the PLMN....................................................................................................................................................... 316
1.6.7.1 Scheme Overview........................................................................................................................................................ 316
1.6.7.2 Engineering Preparation............................................................................................................................................ 318
1.6.7.3 Engineering Implementation................................................................................................................................... 322
1.6.7.4 Engineering Verification............................................................................................................................................ 324
1.6.7.5 Engineering Rollback.................................................................................................................................................. 325
1.7 Device Data Reconfigurations........................................................................................................................................ 326
1.7.1 Replacing the Main Control Board When No SeGW Is Deployed .................................................................326
1.7.1.1 Scheme Overview........................................................................................................................................................ 326
1.7.1.2 Engineering Preparation............................................................................................................................................ 335
1.7.1.3 Engineering Implementation................................................................................................................................... 344
1.7.1.4 Engineering Verification............................................................................................................................................ 348
1.7.1.5 Engineering Rollback.................................................................................................................................................. 349
1.7.2 Replacing the Main Control Board When an SeGW Is Deployed ..................................................................350
1.7.2.1 Scheme Overview........................................................................................................................................................ 350
1.7.2.2 Engineering Preparation............................................................................................................................................ 359
1.7.2.3 Engineering Implementation................................................................................................................................... 369
1.7.2.4 Engineering Verification............................................................................................................................................ 373
1.7.2.5 Engineering Rollback.................................................................................................................................................. 375
1.7.3 Replacing BBPs................................................................................................................................................................. 375
1.7.3.1 Scheme Overview........................................................................................................................................................ 375
1.7.3.2 Engineering Preparation............................................................................................................................................ 377
1.7.3.3 Engineering Implementation................................................................................................................................... 384
1.7.3.4 Engineering Verification............................................................................................................................................ 388
1.7.3.5 Engineering Rollback.................................................................................................................................................. 389
1.7.4 Changing CPRI Ports for RF Modules....................................................................................................................... 390
1.7.4.1 Scheme Overview........................................................................................................................................................ 390
1.7.4.2 Engineering Preparation............................................................................................................................................ 393
1.7.4.3 Engineering Implementation................................................................................................................................... 397
1.7.4.4 Engineering Verification............................................................................................................................................ 398
1.7.4.5 Engineering Rollback.................................................................................................................................................. 399
1.7.5 Adding or Deleting an RF Module............................................................................................................................ 400
1.7.5.1 Scheme Overview........................................................................................................................................................ 400
1.7.5.2 Engineering Preparation............................................................................................................................................ 408
1.7.5.3 Engineering Implementation................................................................................................................................... 416
1.7.5.4 Engineering Verification............................................................................................................................................ 424

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. vii

eRAN
Reconfiguration Guide Contents

1.7.5.5 Engineering Rollback.................................................................................................................................................. 424

1.7.6 Transmission Capacity Expansion from One LMPT Board to LMPT + UMPT Boards (Mode 1) (TDD)
(IPv4 Transmission Only)........................................................................................................................................................ 425
1.7.6.1 Scheme Overview........................................................................................................................................................ 426
1.7.6.2 Engineering Preparation............................................................................................................................................ 427
1.7.6.3 Engineering Implementation................................................................................................................................... 428
1.7.6.4 Engineering Verification............................................................................................................................................ 431
1.7.6.5 Engineering Rollback.................................................................................................................................................. 432
1.7.7 Transmission Capacity Expansion from One LMPT Board to LMPT + UMPT Boards (Mode 2) (TDD)
(IPv4 Transmission Only)........................................................................................................................................................ 433
1.7.7.1 Scheme Overview........................................................................................................................................................ 433
1.7.7.2 Engineering Preparation............................................................................................................................................ 434
1.7.7.3 Engineering Implementation................................................................................................................................... 436
1.7.7.4 Engineering Verification............................................................................................................................................ 442
1.7.7.5 Engineering Rollback.................................................................................................................................................. 442
1.7.8 Transmission Capacity Expansion from One UMPT Board to Two UMPT Boards (FDD/NB-IoT) (IPv4
Transmission Only).................................................................................................................................................................... 443
1.7.8.1 Scheme Overview........................................................................................................................................................ 443
1.7.8.2 Engineering Preparation............................................................................................................................................ 446
1.7.8.3 Engineering Implementation................................................................................................................................... 450
1.7.8.4 Engineering Verification............................................................................................................................................ 452
1.7.8.5 Engineering Rollback.................................................................................................................................................. 453
1.7.9 Signaling Capacity Expansion from One UMPT to One Primary UMPT + One Extension UMPT/LMPT
(IPv4 Transmission Only)........................................................................................................................................................ 455
1.7.9.1 Scheme Overview........................................................................................................................................................ 455
1.7.9.2 Engineering Preparation............................................................................................................................................ 458
1.7.9.3 Engineering Implementation................................................................................................................................... 461
1.7.9.4 Engineering Verification............................................................................................................................................ 463
1.7.9.5 Engineering Rollback.................................................................................................................................................. 464
1.7.10 Signaling Capacity Expansion from One LMPT to One Primary UMPT + One Extension LMPT (IPv4
Transmission Only).................................................................................................................................................................... 465
1.7.10.1 Scheme Overview......................................................................................................................................................465
1.7.10.2 Engineering Preparation......................................................................................................................................... 467
1.7.10.3 Engineering Implementation................................................................................................................................ 471
1.7.10.4 Engineering Verification..........................................................................................................................................473
1.7.10.5 Engineering Rollback............................................................................................................................................... 474
1.8 Interface and Link Data Reconfigurations................................................................................................................. 475
1.8.1 Adding an MME Connection....................................................................................................................................... 475
1.8.1.1 Scheme Overview........................................................................................................................................................ 476
1.8.1.2 Engineering Preparation............................................................................................................................................ 483
1.8.1.3 Engineering Implementation................................................................................................................................... 491
1.8.1.4 Engineering Verification............................................................................................................................................ 493
1.8.1.5 Engineering Rollback.................................................................................................................................................. 495
1.8.2 Adding an S-GW Connection...................................................................................................................................... 496

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. viii

eRAN
Reconfiguration Guide Contents

1.8.2.1 Scheme Overview........................................................................................................................................................ 496

1.8.2.2 Engineering Preparation............................................................................................................................................ 503
1.8.2.3 Engineering Implementation................................................................................................................................... 511
1.8.2.4 Engineering Verification............................................................................................................................................ 513
1.8.2.5 Engineering Rollback.................................................................................................................................................. 513
1.8.3 Replacing an MME......................................................................................................................................................... 514
1.8.3.1 Scheme Overview........................................................................................................................................................ 515
1.8.3.2 Engineering Preparation............................................................................................................................................ 524
1.8.3.3 Engineering Implementation................................................................................................................................... 532
1.8.3.4 Engineering Verification............................................................................................................................................ 534
1.8.3.5 Engineering Rollback.................................................................................................................................................. 536
1.8.4 Replacing an S-GW.........................................................................................................................................................537
1.8.4.1 Scheme Overview........................................................................................................................................................ 537
1.8.4.2 Engineering Preparation............................................................................................................................................ 543
1.8.4.3 Engineering Implementation................................................................................................................................... 551
1.8.4.4 Engineering Verification............................................................................................................................................ 552
1.8.4.5 Engineering Rollback.................................................................................................................................................. 553
1.8.5 Replacing the MAE......................................................................................................................................................... 554
1.8.5.1 Scheme Overview........................................................................................................................................................ 554
1.8.5.2 Engineering Preparation............................................................................................................................................ 558
1.8.5.3 Engineering Implementation................................................................................................................................... 563
1.8.5.4 Engineering Verification............................................................................................................................................ 565
1.8.5.5 Engineering Rollback.................................................................................................................................................. 565
1.8.6 Changing the Local Maintenance IP Address........................................................................................................ 566
1.8.6.1 Scheme Overview........................................................................................................................................................ 566
1.8.6.2 Engineering Preparation............................................................................................................................................ 567
1.8.6.3 Engineering Implementation................................................................................................................................... 569
1.8.6.4 Engineering Verification............................................................................................................................................ 570
1.8.6.5 Engineering Rollback.................................................................................................................................................. 571
1.8.7 Changing the Device IP Address (Old Model)...................................................................................................... 572
1.8.7.1 Scheme Overview........................................................................................................................................................ 572
1.8.7.2 Engineering Preparation............................................................................................................................................ 580
1.8.7.3 Engineering Implementation................................................................................................................................... 588
1.8.7.4 Engineering Verification............................................................................................................................................ 591
1.8.7.5 Engineering Rollback.................................................................................................................................................. 591
1.8.8 Changing the IPv4/IPv6 Address (New Model).................................................................................................... 593
1.8.8.1 Scheme Overview........................................................................................................................................................ 593
1.8.8.2 Engineering Preparation............................................................................................................................................ 602
1.8.8.3 Engineering Implementation................................................................................................................................... 612
1.8.8.4 Engineering Verification............................................................................................................................................ 615
1.8.8.5 Engineering Rollback.................................................................................................................................................. 616
1.8.9 Changing the IP Address of a Clock Server............................................................................................................617

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. ix

eRAN
Reconfiguration Guide Contents

1.8.9.1 Scheme Overview........................................................................................................................................................ 617

1.8.9.2 Engineering Preparation............................................................................................................................................ 624
1.8.9.3 Engineering Implementation................................................................................................................................... 628
1.8.9.4 Engineering Verification............................................................................................................................................ 629
1.8.9.5 Engineering Rollback.................................................................................................................................................. 631
1.8.10 Changing the SCTP Link Number (for IPv4 Transmission Only).................................................................. 632
1.8.10.1 Scheme Overview......................................................................................................................................................632
1.8.10.2 Engineering Preparation......................................................................................................................................... 633
1.8.10.3 Engineering Implementation................................................................................................................................ 637
1.8.10.4 Engineering Verification..........................................................................................................................................639
1.8.10.5 Engineering Rollback............................................................................................................................................... 639
1.8.11 Removing an X2 Interface......................................................................................................................................... 640
1.8.11.1 Scheme Overview......................................................................................................................................................640
1.8.11.2 Engineering Preparation......................................................................................................................................... 643
1.8.11.3 Engineering Implementation................................................................................................................................ 645
1.8.11.4 Engineering Verification..........................................................................................................................................647
1.8.11.5 Engineering Rollback............................................................................................................................................... 648
1.8.12 Modifying the Ethernet Port Number (Old Model)......................................................................................... 650
1.8.12.1 Scheme Overview......................................................................................................................................................650
1.8.12.2 Engineering Preparation......................................................................................................................................... 656
1.8.12.3 Engineering Implementation................................................................................................................................ 663
1.8.12.4 Engineering Verification..........................................................................................................................................664
1.8.12.5 Engineering Rollback............................................................................................................................................... 665
1.8.13 Modifying the Ethernet Port Number (New Model)........................................................................................666
1.8.13.1 Scheme Overview......................................................................................................................................................666
1.8.13.2 Engineering Preparation......................................................................................................................................... 668
1.8.13.3 Engineering Implementation................................................................................................................................ 672
1.8.13.4 Engineering Verification..........................................................................................................................................673
1.8.13.5 Engineering Rollback............................................................................................................................................... 674
1.8.14 MME Dual-homing Reconfiguration......................................................................................................................675
1.8.14.1 Scheme Overview......................................................................................................................................................675
1.8.14.2 Engineering Preparation......................................................................................................................................... 678
1.8.14.3 Engineering Implementation................................................................................................................................ 681
1.8.14.4 Engineering Verification..........................................................................................................................................683
1.8.14.5 Engineering Rollback............................................................................................................................................... 684
1.8.15 Changing the Transmission Mode from Link Mode to Endpoint Mode (Only for IPv4 Transmission)
......................................................................................................................................................................................................... 684
1.8.15.1 Scheme Overview......................................................................................................................................................685
1.8.15.2 Engineering Preparation......................................................................................................................................... 688
1.8.15.3 Engineering Implementation................................................................................................................................ 693
1.8.15.4 Engineering Verification..........................................................................................................................................695
1.8.15.5 Engineering Rollback............................................................................................................................................... 696
1.8.16 Adding an eCoordinator Connection (Only for IPv4 Transmission)............................................................ 697

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. x

eRAN
Reconfiguration Guide Contents

1.8.16.1 Scheme Overview......................................................................................................................................................697

1.8.16.2 Engineering Preparation......................................................................................................................................... 702
1.8.16.3 Engineering Implementation................................................................................................................................ 707
1.8.16.4 Engineering Verification..........................................................................................................................................708
1.8.16.5 Engineering Rollback............................................................................................................................................... 709
1.8.17 Replacing an eCoordinator (Only for IPv4 Transmission).............................................................................. 710
1.8.17.1 Scheme Overview......................................................................................................................................................710
1.8.17.2 Engineering Preparation......................................................................................................................................... 715
1.8.17.3 Engineering Implementation................................................................................................................................ 720
1.8.17.4 Engineering Verification..........................................................................................................................................721
1.8.17.5 Engineering Rollback............................................................................................................................................... 722
1.8.18 Optimizing the Transmission Configuration Model.......................................................................................... 723
1.8.18.1 Scheme Overview......................................................................................................................................................723
1.8.18.2 Engineering Preparation......................................................................................................................................... 726
1.8.18.3 Engineering Implementation................................................................................................................................ 728
1.8.18.4 Engineering Verification..........................................................................................................................................729
1.8.18.5 Engineering Rollback............................................................................................................................................... 729
1.9 Security Networking Data Reconfigurations............................................................................................................ 730
1.9.1 Changing the Transport Network from Non-Security Mode to PKI Security Mode (Old Model).......730
1.9.1.1 Scheme Overview........................................................................................................................................................ 730
1.9.1.2 Engineering Preparation............................................................................................................................................ 735
1.9.1.3 Engineering Implementation................................................................................................................................... 742
1.9.1.4 Engineering Verification............................................................................................................................................ 744
1.9.1.5 Engineering Rollback.................................................................................................................................................. 745
1.9.2 Changing the Transport Network from Non-Security Mode to PKI Security Mode (New Model).....747
1.9.2.1 Scheme Overview........................................................................................................................................................ 748
1.9.2.2 Engineering Preparation............................................................................................................................................ 754
1.9.2.3 Engineering Implementation................................................................................................................................... 763
1.9.2.4 Engineering Verification............................................................................................................................................ 765
1.9.2.5 Engineering Rollback.................................................................................................................................................. 766
1.9.3 Changing the Transport Network from Non-Security Mode to PSK Security Mode (Old Model)......768
1.9.3.1 Scheme Overview........................................................................................................................................................ 769
1.9.3.2 Engineering Preparation............................................................................................................................................ 771
1.9.3.3 Engineering Implementation................................................................................................................................... 775
1.9.3.4 Engineering Verification............................................................................................................................................ 777
1.9.3.5 Engineering Rollback.................................................................................................................................................. 777
1.9.4 Changing the Transport Network from Non-Security Mode to PSK Security Mode (New Model)....778
1.9.4.1 Scheme Overview........................................................................................................................................................ 779
1.9.4.2 Engineering Preparation............................................................................................................................................ 781
1.9.4.3 Engineering Implementation................................................................................................................................... 786
1.9.4.4 Engineering Verification............................................................................................................................................ 788
1.9.4.5 Engineering Rollback.................................................................................................................................................. 788

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. xi

eRAN
Reconfiguration Guide Contents

1.9.5 Changing the Security Mode from PSK to PKI...................................................................................................... 789

1.9.5.1 Scheme Overview........................................................................................................................................................ 789
1.9.5.2 Engineering Preparation............................................................................................................................................ 796
1.9.5.3 Engineering Implementation................................................................................................................................... 804
1.9.5.4 Engineering Verification............................................................................................................................................ 806
1.9.5.5 Engineering Rollback.................................................................................................................................................. 807
1.9.6 Changing a Single IPsec Tunnel to an IPsec Tunnel Pair (Only for IPv4 Transmission)......................... 809
1.9.6.1 Scheme Overview........................................................................................................................................................ 809
1.9.6.2 Engineering Preparation............................................................................................................................................ 812
1.9.6.3 Engineering Implementation................................................................................................................................... 816
1.9.6.4 Engineering Verification............................................................................................................................................ 817
1.9.6.5 Engineering Rollback.................................................................................................................................................. 818
1.9.7 Changing a Single Virtual Route to Active/Standby Static IP Route.............................................................819
1.9.7.1 Scheme Overview........................................................................................................................................................ 819
1.9.7.2 Engineering Preparation............................................................................................................................................ 822
1.9.7.3 Engineering Implementation................................................................................................................................... 826
1.9.7.4 Engineering Verification............................................................................................................................................ 828
1.9.7.5 Engineering Rollback.................................................................................................................................................. 828
1.9.8 Replacing an SeGW........................................................................................................................................................ 829
1.9.8.1 Scheme Overview........................................................................................................................................................ 830
1.9.8.2 Engineering Preparation............................................................................................................................................ 833
1.9.8.3 Engineering Implementation................................................................................................................................... 838
1.9.8.4 Engineering Verification............................................................................................................................................ 839
1.9.8.5 Engineering Rollback.................................................................................................................................................. 839
1.9.9 Adjusting the VLAN........................................................................................................................................................ 840
1.9.9.1 Scheme Overview........................................................................................................................................................ 841
1.9.9.2 Engineering Preparation............................................................................................................................................ 842
1.9.9.3 Engineering Implementation................................................................................................................................... 845
1.9.9.4 Engineering Verification............................................................................................................................................ 846
1.9.9.5 Engineering Rollback.................................................................................................................................................. 846
1.9.10 Changing the VLAN Mode from VLAN Group to Single VLAN (Only for IPv4 Transmission)........... 847
1.9.10.1 Scheme Overview......................................................................................................................................................847
1.9.10.2 Engineering Preparation......................................................................................................................................... 849
1.9.10.3 Engineering Implementation................................................................................................................................ 851
1.9.10.4 Engineering Verification..........................................................................................................................................852
1.9.10.5 Engineering Rollback............................................................................................................................................... 853
1.9.11 Changing the VLAN Mode from Single VLAN to Interface VLAN (Only for IPv4 Transmission)...... 854
1.9.11.1 Scheme Overview......................................................................................................................................................854
1.9.11.2 Engineering Preparation......................................................................................................................................... 856
1.9.11.3 Engineering Implementation................................................................................................................................ 860
1.9.11.4 Engineering Verification..........................................................................................................................................862
1.9.11.5 Engineering Rollback............................................................................................................................................... 862

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. xii

eRAN
Reconfiguration Guide Contents

1.10 Reconfigurations Dedicated to the LampSite Solution....................................................................................... 864

1.10.1 Adding a pRRU-Aggregation Cell............................................................................................................................864
1.10.1.1 Scheme Overview......................................................................................................................................................864
1.10.1.2 Engineering Preparation......................................................................................................................................... 867
1.10.1.3 Engineering Implementation................................................................................................................................ 877
1.10.1.4 Engineering Verification..........................................................................................................................................879
1.10.1.5 Engineering Rollback............................................................................................................................................... 879
1.10.2 Combining pRRU-Aggregation Cells...................................................................................................................... 880
1.10.2.1 Scheme Overview......................................................................................................................................................880
1.10.2.2 Engineering Preparation......................................................................................................................................... 885
1.10.2.3 Engineering Implementation................................................................................................................................ 887
1.10.2.4 Engineering Verification..........................................................................................................................................889
1.10.2.5 Engineering Rollback............................................................................................................................................... 889
1.10.3 Splitting a pRRU-Aggregation Cell......................................................................................................................... 890
1.10.3.1 Scheme Overview......................................................................................................................................................890
1.10.3.2 Engineering Preparation......................................................................................................................................... 894
1.10.3.3 Engineering Implementation................................................................................................................................ 898
1.10.3.4 Engineering Verification..........................................................................................................................................900
1.10.3.5 Engineering Rollback............................................................................................................................................... 901
1.10.4 Reconstructing pRRU-Aggregation Cells to a Pico SFN Cell..........................................................................902
1.10.4.1 Scheme Overview......................................................................................................................................................902
1.10.4.2 Engineering Preparation......................................................................................................................................... 904
1.10.4.3 Engineering Implementation................................................................................................................................ 908
1.10.4.4 Engineering Verification..........................................................................................................................................910
1.10.4.5 Engineering Rollback............................................................................................................................................... 910
1.10.5 Adjusting pRRU Transmit Power............................................................................................................................. 911
1.10.5.1 Scheme Overview......................................................................................................................................................911
1.10.5.2 Engineering Preparation......................................................................................................................................... 913
1.10.5.3 Engineering Implementation................................................................................................................................ 916
1.10.5.4 Engineering Verification..........................................................................................................................................918
1.10.5.5 Engineering Rollback............................................................................................................................................... 920
1.10.6 Sharing BBUs Between Macro and LampSite Base Stations......................................................................... 921
1.10.6.1 Scheme Overview......................................................................................................................................................921
1.10.6.2 Engineering Preparation......................................................................................................................................... 924
1.10.6.3 Engineering Implementation................................................................................................................................ 930
1.10.6.4 Engineering Verification..........................................................................................................................................932
1.10.6.5 Engineering Rollback............................................................................................................................................... 932
1.10.7 Adding an LAA Cell...................................................................................................................................................... 933
1.10.7.1 Scheme Overview......................................................................................................................................................933
1.10.7.2 Engineering Preparation......................................................................................................................................... 936
1.10.7.3 Engineering Implementation................................................................................................................................ 942
1.10.7.4 Engineering Verification..........................................................................................................................................943

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. xiii

eRAN
Reconfiguration Guide Contents

1.10.7.5 Engineering Rollback............................................................................................................................................... 944

1.10.8 Adding an RFA Cell...................................................................................................................................................... 945
1.10.8.1 Scheme Overview......................................................................................................................................................945
1.10.8.2 Engineering Preparation......................................................................................................................................... 947
1.10.8.3 Engineering Implementation................................................................................................................................ 952
1.10.8.4 Engineering Verification..........................................................................................................................................953
1.10.8.5 Engineering Rollback............................................................................................................................................... 954
1.11 Configuration References.............................................................................................................................................. 955
1.11.1 Setting the eNodeB Maintenance Mode.............................................................................................................. 955
1.11.2 Using the Batch Reconfiguration Mode of the MAE-Deployment to Prepare Data............................. 957
1.11.3 Preparing Data in GUI Mode.................................................................................................................................... 958
1.11.4 Delivering Data to Base Stations and Activating the Data............................................................................ 958
1.11.5 Falling Back Configuration Data............................................................................................................................. 958
1.11.6 Cell Types and Networking Restrictions of the LampSite Solution............................................................. 958

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. xiv

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1 eRAN Reconfiguration Guide

Overview
This document provides guidelines for eRAN reconfiguration. eRAN
reconfigurations consist of cell data reconfiguration, eNodeB data reconfiguration,
device data reconfiguration, interface and link data reconfiguration, security
networking data reconfiguration, and reconfigurations dedicated to the LampSite
solution. For details about how to configure an eNodeB before it is put into
operation, see 3900 & 5900 Series Base Station Initial Configuration Guide. For
details about feature activation and reconfiguration, see eRAN feature
documentation.

NOTE

Reconfiguration scenarios are not distinguished between FDD, NB-IoT, and TDD in this
document. If distinction is required, FDD, NB-IoT, and TDD are used to indicate the distinction.

Product Versions
The following table lists the product versions related to this document.

Product Name Solution Version Product Version

3900 series base stations eRAN17.1 V100R017C10

5900 series base stations

Intended Audience
This document is intended for:
● Network planning engineers
● Network operators
● System engineers

Organization
1.1 Changes in eRAN Reconfiguration Guide

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

This section describes the changes in eRAN Reconfiguration Guide.

1.2 Introduction to eRAN Reconfiguration
This section defines eRAN reconfiguration and describes the general prerequisites,
transmission configuration model, and tools for eRAN reconfiguration.
1.3 General Operation Guide
This section provides guides for the MAE-Deployment and MML command
operations, either of which can be used for reconfiguration.
1.4 Reconfiguration Scenario Overview
This section describes the typical reconfiguration scenarios and the reconfiguration
methods and tools recommended in these scenarios.
1.5 Cell Data Reconfigurations
This section describes how to reconfigure cells served by eNodeBs in typical
scenarios.
1.6 Base Station Data Reconfigurations
This chapter describes how to reconfigure base station data in typical scenarios.
1.7 Device Data Reconfigurations
This section describes how to reconfigure eNodeB device data in typical scenarios.
1.8 Interface and Link Data Reconfigurations
This section describes how to reconfigure eNodeB interface and link data in typical
scenarios.
1.9 Security Networking Data Reconfigurations
This section describes how to reconfigure eNodeB security networking data in
typical scenarios.
1.10 Reconfigurations Dedicated to the LampSite Solution
This section provides guidelines for typical reconfigurations related to the
LampSite solution, including solutions for connections between RHUBs and
RRU3230E/RRU3930E/pRRU in LampSite topologies.
1.11 Configuration References
This chapter provides the reference documents for data configuration. If you want
to view all the check rules of NE data, obtain the file on the Consistency Check
page.

1.1 Changes in eRAN Reconfiguration Guide

This section describes the changes in eRAN Reconfiguration Guide.

04 (2023-03-25)
This is the fourth commercial release.

Compared with Issue 03 (2022-02-25) of V100R017C10, this issue does not include
any new topics.

Compared with Issue 03 (2022-02-25) of V100R017C10, this issue includes the

following changes.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 2

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topic Change Description

1.11.6 Cell Types and Updated the networking restrictions of the

Networking Restrictions of LampSite solution.
the LampSite Solution

Compared with Issue 03 (2022-02-25) of V100R017C10, this issue does not

exclude any topics.

03 (2022-02-25)
This is the third commercial release.

Compared with Issue 02 (2021-04-30) of V100R017C10, this issue does not include
any new topics.

Compared with Issue 02 (2021-04-30) of V100R017C10, this issue includes the

following changes.

Topic Change Description

1.8.18.2 Engineering Added descriptions about how to manually

Preparation back up NE data on the OSS and modified
1.8.18.5 Engineering Rollback descriptions about configuration data
rollback.

Compared with Issue 02 (2021-04-30) of V100R017C10, this issue does not

exclude any topics.

02 (2021-04-30)
This is the second commercial release.

Compared with Issue 01 (2021-03-05), this issue does not include any new topics.

Compared with Issue 01 (2021-03-05), this issue includes the following changes.

Topic Change Description

1.7.1 Replacing the Main Added the description of the navigation path
Control Board When No on the MAE-Deployment for reconfiguring
SeGW Is Deployed multimode base stations.
1.7.2 Replacing the Main
Control Board When an SeGW
Is Deployed

Compared with Issue 01 (2021-03-05), this issue does not exclude any topics.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 3

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

01 (2021-03-05)
This is the first commercial release.

Compared with Draft A (2020-12-29), this issue does not include any new topics
or changes, or exclude any topics.

Draft A (2020-12-29)
This is a draft.

Compared with Issue 03 (2020-07-27) of V100R016C10, this issue does not include
any new topics.

Compared with Issue 03 (2020-07-27) of V100R016C10, this issue includes the

following changes.

Topic Change Description

Entire document Changed the GPS to GNSS.

Compared with Issue 03 (2020-07-27) of V100R016C10, this issue excludes the

following information:

● WMPT
● Adding an SO Link

1.2 Introduction to eRAN Reconfiguration

This section defines eRAN reconfiguration and describes the general prerequisites,
transmission configuration model, and tools for eRAN reconfiguration.

1.2.1 Definition of eRAN Reconfiguration

This section describes the definition and document scope of eRAN reconfiguration.

Definition
eRAN reconfiguration refers to the data addition, deletion, or modification after
an eRAN system is put into use. An eRAN system includes at least one eNodeB.
Data analysis of live networks and networking schemes after eRAN
reconfiguration are determined based on actual network conditions.

eRAN reconfiguration may be required for either of the following purposes:

● Network capacity expansion: The live network is adjusted to accommodate

increased traffic volume and provide services for more UEs.
● Network reconstruction: The live network is adjusted and optimized due to
changes of network structure.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 4

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Document Scope
Figure 1-1 shows the scope of this document.

Figure 1-1 Scope of this document

1. Reconfiguration evaluation: Before network reconfiguration, you must

evaluate the live network to find out the bottleneck of the network and
determine whether to carry out a reconfiguration.
2. Reconfiguration scheme design: Plan and design the target topology, required
equipment, and equipment connections based on site conditions.
3. Engineering preparation: Collect required information and prepare software,
hardware, license files, security certificates, and configuration data.
4. Engineering implementation: Implement reconfiguration, including hardware
adjustment and data activation.
5. Engineering verification: Check whether the reconfiguration is successful. If
the reconfiguration is successful, no further action is required. If the
reconfiguration fails, engineering rollback is required.
6. Engineering rollback: Roll back the network to its original configuration state.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 5

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

This document does not include Reconfiguration evaluation and Reconfiguration scheme
design. It includes only engineering preparation, engineering implementation, engineering
verification, and engineering rollback after the reconfiguration scheme has been determined.

1.2.2 General Prerequisites

This section describes the general prerequisites for eRAN reconfiguration.
● The eNodeB communicates with the MAE or LMT normally, and you have
logged in to the MAE or LMT.
● Information about the status of cells and alarms has been recorded. You must
ensure that the status of cells does not change and no new alarms are
generated after eRAN reconfiguration.
● You have read the following documents: technical specification documents
under the Technical Description node, hardware description documents
under the Hardware Description node, hardware maintenance documents
under the Hardware Maintenance node, and feature parameter description
documents under the Function Description node.

1.2.3 Transmission Configuration Models

This section describes the background of transmission configuration model
adjustment and types of transmission configuration models.

Background
As network traffic volume increases, network transmission scenarios become
increasingly complicated. For example, transmission ports or boards need to be
adjusted to support inter-board functions. The traditional transmission network
configuration is complicated and struggles to meet the requirement for fast
deployment on the live network. Therefore, a new transmission configuration
model is introduced to decouple transmission configurations from physical devices
to simplify operations.

Types of Transmission Configuration Models

Transmission configuration models include a new model and an old model. The
Transmission Configuration Mode parameter in the GTRANSPARA MO controls
which model to take effect.
Old Model
When this parameter is set to OLD, the old model is used. The transmission model
contains location information such as cabinet, subrack, and slot numbers.
Transmission configurations are bound to boards. IPv4 and IPv6 configuration
objects above the IP layer are independent of each other.
New Model
When this parameter is set to NEW, the new model is used. In the new model, the
transmission model is decoupled from the device model. That is, the transmission
configuration does not contain unnecessary information such as cabinet, subrack,
and slot numbers. IPv4 and IPv6 configuration objects above the IP layer are

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 6

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

combined. This model facilitates the expansion of new transmission functions and
requires fewer transmission configuration parameters.
NOTE

● Compared with the old model, the new model adds the INTERFACE MO at the data link
layer to isolate the upper layers from the physical layer. In this way, the transmission
configuration objects are decoupled from the physical devices.
● Unlike the old model, in the new model, when a transmission link is configured or a
transmission board or port is changed, the information such as the cabinet number, subrack
number, slot number, and subboard type does not need to be configured for objects on other
layers except those on the physical layer and link layer.
● The new model applies to base stations except for GBTS and Pico base stations.

1.2.4 Introduction to the Reconfiguration Tools

This section describes the tools used for eRAN reconfiguration, as well as their
characteristics and application scenarios.
Table 1-1 describes the tools for eRAN reconfiguration.

Table 1-1 Reconfiguration tools

Tool Reconf Applica Characteristic Configuration
igurat ble Operation
ion Scenari
Mode o

LMT MML Reconfi Data of only one NE is 1.3.2 Running MML

comm guring to be reconfigured Commands on the LMT
ands one NE locally.

MAE- MML Batch Data of one or more 1.3.3 Running MML

Access comm configu NEs is to be Commands on the MAE-
ands ration reconfigured remotely. Access

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 7

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Tool Reconf Applica Characteristic Configuration

igurat ble Operation
ion Scenari
Mode o

MAE- GUI Reconfi Data of only one NE is 1. Select an eNodeB

Deplo guring to be reconfigured. from the left pane of
yment one NE the planned data area.
The object navigation
tree is displayed in the
lower left part of the
window.
2. In the object
navigation tree, click
the Search tab and
input the MO you
want to configure. The
system automatically
finds the
corresponding MOs.
3. Select the MO to be
configured from
search results and
enter the planned
data in the right pane.
For detailed
operations, see section
Introduction to Data
Configuration
Operations in the
MAE-Access online
help.
4. Verify data accuracy.
There are many
verification methods.
You need to select one
as required. For details
about the verification
methods, see the
description of the data
verification procedure
in 1.3.1 MAE-
Deployment
Operation Guide.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 8

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Tool Reconf Applica Characteristic Configuration

igurat ble Operation
ion Scenari
Mode o

Batch Batch Data of multiple NEs is 1. Use a summary data

reconf NE to be reconfigured. file to collect data on
igurati configu Users can reconfigure the live network.
on ration the data of NEs of a. Prepare a summary
multiple versions at the data file for batch
same time.a configuration.
a. On the menu
bar, choose
Advanced >
Data
Management >
Customize
Summary Data
File. A dialog
box is displayed
for you to open
the summary
data file.
b. Select the
following
options in
sequence:
Select Default.
If a single-mode
base station is to
be reconfigured,
select NodeB/
eNodeB Bulk
Configuration
and eNodeB.
If a co-MPT base
station
(including a co-
MPT base
station where
only one RAT is
enabled) is to be
reconfigured,
select Co-MPT
BTS Bulk
Configuration
and LTE.
Select a base
station version.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 9

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Tool Reconf Applica Characteristic Configuration

igurat ble Operation
ion Scenari
Mode o

c. Click OK to
enable the
function of
customizing a
summary data
file. Click
and select a
scenario-based
template. The
system
automatically
customizes the
parameter
names
contained in the
template into
the summary
data file. Then,
save the
summary data
file to a local PC.
For detailed
customization
operations, see
section
Customizing a
Summary Data
File for Batch
eNodeB
Configuration
in the MAE-
Access online
help.b
b. Based on the
parameter names
in the summary
data file, export the
eNodeB data to be
reconfigured from
the planned data
area to the
summary data file.
On the menu bar of
the planned data
area, choose LTE
Application >

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 10

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Tool Reconf Applica Characteristic Configuration

igurat ble Operation
ion Scenari
Mode o

Network
Adjustment >
Export Base
Station Bulk
Configuration
Data to start the
data export.
2. Open the local
summary data file, fill
out the file as
planned, and then
close the file.
3. Import the
reconfigured summary
data file into the
system to complete
batch reconfiguration
of eNodeB data.
On the menu bar of
the planned data area,
choose LTE
Application >
Network Adjustment
> Import Base
Station Bulk
Configuration Data
to start the data
import.
For detailed import
and export operations,
see section Importing
and Exporting
eNodeB Data for
Batch Configuration
in the MAE-Access
online help.
4. Verify data accuracy.
There are many
verification methods.
You need to select one
as required. For details
about the verification
methods, see the
description of the data
verification procedure
in 1.3.1 MAE-

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 11

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Tool Reconf Applica Characteristic Configuration

igurat ble Operation
ion Scenari
Mode o

Deployment
Operation Guide.

Bulk Batch ● Data of multiple NEs In the left pane of the

modifi configu is to be reconfigured, planned data area, right-
cation ration and a data value is click eNodeBs you want
center the same for these to configure and choose
NEs. Batch Modification
● You can modify Center to reconfigure
parameters of only data in batches. For
one MO at a time. detailed operations, see
section Reconfiguring
LTE Configuration
Parameters in Batches
in the MAE-Access online
help.

Applyi Batch ● Data of multiple NEs On the menu bar, choose

ng configu is to be reconfigured, Advanced > Data
templ ration and a data value is Management > Apply
ates the same for these Template to apply
NEs. templates. For detailed
● You can modify operations, see Applying
parameters of Templates in the MAE-
multiple MOs at a Access online help.
time.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 12

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Tool Reconf Applica Characteristic Configuration

igurat ble Operation
ion Scenari
Mode o

Radio Batch The neighbor 1. On the menu bar,

data configu relationship-related choose LTE
planni ration data is to be Application >
ng file reconfigured. Network Adjustment
> Export Radio
Network Planning
Data to start
exporting the radio
network planning data
from the system into a
file.
2. Edit data in the file
based on the prepared
data. Then, close the
file.
3. On the menu bar of
the planned data area,
choose LTE
Application >
Network Adjustment
> Import Radio
Network Planning
Data. A dialog box is
displayed for you to
import planned radio
data. Import the data
from the file into the
system.
For detailed
operations, see
Importing and
Exporting Radio
Network Planning
Data in the MAE-
Access online help.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 13

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Tool Reconf Applica Characteristic Configuration

igurat ble Operation
ion Scenari
Mode o

ID/ Batch The names and IDs of 1. On the menu bar,

Name configu eNodeBs, cell IDs, local choose LTE
modifi ration cell IDs, and cell names Application >
cation are to be reconfigured. Network Adjustment
> Export ID/Name
Adjustment Data to
start exporting the
eNodeB name and ID,
cell ID, local cell ID,
and cell name from
the system to a file.
2. Edit data in the file
based on the prepared
data. Then, close the
file.
3. On the menu bar,
choose LTE
Application >
Network Adjustment
> Import ID/Name
Adjustment Data to
start data import from
the file to the system.
4. Verify data accuracy.
There are many
verification methods.
You need to select one
as required. For details
about the verification
methods, see the
description of the data
verification procedure
in 1.3.1 MAE-
Deployment
Operation Guide.
For detailed import and
export operations, see
section Importing and
Exporting Names and
IDs in the MAE-Access
online help.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 14

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Tool Reconf Applica Characteristic Configuration

igurat ble Operation
ion Scenari
Mode o

Planni Batch ● Transmission 1. On the menu bar,

ng file modific configuration models choose Advanced >
ation of of multiple NEs are Network
transmi to be reconfigured. Enhancement >
ssion ● This reconfiguration Reconstruction
configu mode is applicable Express.
ration when the 2. In the Scenario area,
models transmission select Transmission
configuration model Configuration Model
is to be changed. Conversion.
3. Click Export Default
Template to obtain
the template, plan
data, and fill in the
template.
4. In Planning Data

Table, click to
upload the filled
template and click
Execute.

a: For the MOs that can be reconfigured in batches, see the Parameter List file.
To obtain the file, choose Advanced > Data Management > Download
Reference Files on the MAE-Deployment, set the filter criteria, and obtain the
Parameter List file.
b: You can customize only "List" sheets. Customize a unique "List" sheet for each
MO.

1.3 General Operation Guide

This section provides guides for the MAE-Deployment and MML command
operations, either of which can be used for reconfiguration.
MML command operations are performed on the LMT or MAE-Access.

1.3.1 MAE-Deployment Operation Guide

In reconfiguration scenarios, you can prepare and activate data by using the MAE-
Deployment. This section describes the operation process for preparing data by
using the MAE-Deployment. For details about how to activate data, see the
description of remote operations in the engineering implementation section in
each scenario.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 15

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

The functions supported by the MAE-Deployment vary with versions.

Prerequisites
NEs have been connected to the MAE and the configuration data has been
collected.

Procedure
When preparing data by using the MAE-Deployment, the operation process is the
same in each reconfiguration scenario but the reconfiguration mode is different.
Figure 1-2 shows the process for preparing data. Table 1-2 describes the process.

Figure 1-2 MAE-Deployment operation process

NOTE

When preparing eRAN data by using MAE-Deployment functions, you can press F1 or click
to view the online help for the detailed function operations and introduction.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 16

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-2 MAE-Deployment operation process

Procedure Description

Start the
MAE- On the MAE, click and then choose Deployment to start
Deployment the MAE-Deployment.
.

Create a Create a planned data area before configuring data. The

planned subsequent operations are performed in this area.a
data area. 1. On the menu bar, choose Area Management > Planned Area
> Planned Area Management. The page for managing
planned data areas is displayed.
2. Click Create in the upper right area. The dialog box for
creating a planned data area is displayed.
For details about how to create a planned data area, click
in the upper right corner to obtain the online help.

Reconfigure Prepare data using different MAE-Deployment functions based

datab. on the reconfiguration scenario. The most common function is
batch reconfiguration. The MAE-Deployment provides the
following reconfiguration functions. For detailed operations, see
the section related to data preparation in each scenario.
● Batch configuration:
– Batch reconfiguration
– Radio data planning file
– ID/Name modification
● Single base station configuration: GUI-based configuration

Verify After data reconfiguration is complete, verify the data to ensure

configuratio data accuracy.
n data. On the menu bar of the planned data area, choose Advanced >
Data Management > Check NE Data to start verification. For
detailed operations, click to obtain the online help.
When verifying configuration data, modify configuration data as
prompted until the verification succeeds.

Export Export the configuration data from the MAE-Deployment as

configuratio scripts and activate it.c
n scripts On the menu bar of the planned data area, choose Area
and activate Management > Planned Area > Export Incremental Scripts to
data. export configuration scripts.
For detailed operations, see Exporting Incremental Scripts from
a Planned Data Area in the MAE-Access online help.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 17

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure Description

a: To create GBTSs, NodeBs, or multimode base stations, you need to add the
base station controllers managing these base stations to the planned data area
after you create a planned data area.
b: For an LTE base station, the navigation path on the MAE-Deployment for
data reconfiguration is LTE Application on the menu bar. For a multimode base
station, the navigation path on the MAE-Deployment for data reconfiguration is
SRAN Application on the menu bar.
c: If the OMCH will be disconnected in the reconfiguration scenario, you are
advised to export the full base station script during the script export. The
operation portal is as follows: Choose Advanced > Data Management > Export
NE Files in the current or planned data area.

1.3.2 Running MML Commands on the LMT

The LMT is used to maintain only one eNodeB. The data configuration scripts can
be delivered and activated when you run batch MML command scripts on the
LMT. Using the LMT facilitates quick reconfiguration of a single eNodeB.

Prerequisites
● The eNodeB and LMT communicate with each other properly.
● You have logged in to the LMT and obtained the batch execution permissions.

Context
When the parameter settings of an MML command depend on the output of
other MML commands, the MML commands must be executed batch by batch.

Procedure
Step 1 On the LMT, click Batch. The Local Maintenance Terminal window is displayed,
and the Batch tab page is displayed within the window.
Step 2 Copy and paste the MML command scripts to be executed in sequence to area 1,
as shown in Figure 1-3.

Figure 1-3 Area for executing MML command scripts in batches

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 18

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 3 Click Go. All the MML command scripts in area 1 will be executed one by one.

----End

1.3.3 Running MML Commands on the MAE-Access

You can run MML commands on the MAE-Access to configure base stations. You
can reconfigure one or more base stations that have connected to the MAE at a
time by running batch MML command scripts on the MAE-Access.

Prerequisites
● The eNodeB and MAE communicate with each other properly.
● You have logged in to the MAE and are authorized to run MML commands.

Context
● If file upload or download is required, it must be performed on each base
station one by one.
● If multiple base stations are reconfigured simultaneously, the software
versions and parameters to be reconfigured must be the same.

Procedure

Step 1 On the MAE, click and then choose Access to start the MAE-Access.
Step 2 From the main menu of the MAE-Access, choose Maintenance > MML
Command.
Step 3 In the left pane, select a base station type. In the navigation tree, select the NEs to
be reconfigured, as shown in Figure 1-4.
NOTE

Multiple NEs of the same version can be selected at a time.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 19

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-4 Selecting NEs

Step 4 In the window shown in Figure 1-4, click Script Mode to enter the script mode.
Step 5 In the right pane, enter or copy and paste the MML commands to be executed in
sequence to area 1, as shown in Figure 1-5.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 20

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-5 Entering MML commands

Step 6 Click Save and download the script. Then click Create Task to create a task.
Step 7 In the New Task dialog box, enter a task name. Choose Other > MML Script in
the Task Type area. Set Execution Type, and click Next. Figure 1-6 shows the
settings.

Figure 1-6 Creating a task (1)

Step 8 Set the time or period to execute the task and click Next.
Step 9 In the displayed dialog box, select the script to be executed, set Run Mode, Error-
Execution Mode, and Execution Results, and click Finish. Figure 1-7 shows the
settings.
The Task Management window appears, displaying all MML script tasks.
If Status and Execution Result are Finished and Successful, respectively, all MML
scripts are successfully executed. If Execution Result is Failed or Partly

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 21

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Successful, click the task and view the failed NEs and MML scripts in the Result
Information area or execution result file.

Figure 1-7 Creating a task (2)

----End

1.4 Reconfiguration Scenario Overview

This section describes the typical reconfiguration scenarios and the reconfiguration
methods and tools recommended in these scenarios.
● Table 1-3 lists the recommended reconfiguration modes and tools for cell
data reconfigurations.
● Table 1-4 lists the recommended reconfiguration modes and tools for base
station data reconfigurations.
● Table 1-5 lists the recommended reconfiguration modes and tools for device
data reconfigurations.
● Table 1-6 lists the recommended reconfiguration modes and tools for
interface and link data reconfigurations.
● Table 1-7 lists the recommended reconfiguration modes and tools for security
networking data reconfigurations.
● Table 1-8 lists the recommended reconfiguration modes and tools for
reconfigurations dedicated to the LampSite solution.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 22

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-3 Cell data reconfigurations

Scenario Recommended Recommended Recommended
Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.5.1 Adding an GUI Batch MAE-Deployment

FDD/NB-IoT Cell reconfiguration
(Common
Scenarios)

1.5.2 Adding an GUI Batch MAE-Deployment

FDD Cell (Dual- reconfiguration
Carrier Capacity
Expansion
Scenarios)

1.5.3 Adding a GUI Batch MAE-Deployment

TDD Cell reconfiguration
(Common
Scenarios)

1.5.4 Adding a GUI Batch MAE-Deployment

TDD Cell (Multi- reconfiguration
Carrier Capacity
Expansion
Scenarios)

1.5.5 Adding an GUI Batch MAE-Deployment

Indoor reconfiguration
Distributed Cell
(TDD)

1.5.6 Changing GUI Batch MAE-Deployment

the Cell reconfiguration
Bandwidth

1.5.7 Changing GUI Batch MAE-Deployment

the TX/RX Mode reconfiguration
of a Cell

1.5.8 Changing GUI Batch MAE-Deployment

the Coverage reconfiguration
Radius of a Cell

1.5.9 Changing Radio data Radio data MAE-Deployment

the EARFCNs of a planning file planning file
Cell

1.5.10 Changing Radio data Radio data MAE-Deployment

the PCI of a Cell planning file planning file

1.5.11 Changing ID/Name ID/Name MAE-Deployment

the Cell ID modification modification

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 23

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Scenario Recommended Recommended Recommended

Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.5.12 Changing ID/Name ID/Name MAE-Deployment

the Local Cell ID modification modification

1.5.13 Changing Radio data Radio data MAE-Deployment

the TAC planning file planning file

1.5.14 Changing Radio data Radio data MAE-Deployment

the Neighboring planning file planning file
Cell Parameters

1.5.15 Changing GUI Batch MAE-Deployment

the Intra- reconfiguration
Frequency
Handover Offset

1.5.16 Changing GUI Batch MAE-Deployment

the Cell Power reconfiguration

1.5.17 Changing GUI Batch MAE-Deployment

a Cell to SFN reconfiguration
Mode (Intra-
BBU)

1.5.18 Changing GUI Batch MAE-Deployment

a Cell to SFN reconfiguration
Mode (Inter-
BBU)

1.5.19 Binding GUI Batch MAE-Deployment

Baseband reconfiguration
Equipment

1.5.20 Enabling GUI Batch MAE-Deployment

Automatic reconfiguration
Binding of
Baseband
Equipment

1.5.21 Changing GUI Batch MAE-Deployment

the Baseband reconfiguration
Equipment for a
Cell

1.5.22 Changing GUI Batch MAE-Deployment

the Uplink- reconfiguration
Downlink
Subframe
Configuration
(TDD)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 24

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Scenario Recommended Recommended Recommended

Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.5.23 Changing GUI Batch MAE-Deployment

the Special reconfiguration
Subframe
Configuration
(TDD)

1.5.24 Adjusting GUI Batch MAE-Deployment

Association reconfiguration
Relationships
Between Cells
and RF Modules

1.5.25 Deleting a GUI Batch MAE-Deployment

Cell reconfiguration

1.5.26 Co-BBP GUI Batch MAE-Deployment

4T4R and 8T8R reconfiguration
Cells

Table 1-4 Base station data reconfigurations

Scenario Recommended Recommended Recommended
Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.6.1 Changing GUI Batch MAE-Deployment

the eNodeB from reconfiguration
Independent and radio data
Operator Mode planning file
to RAN Sharing
with Common
Carrier Mode

1.6.2 Changing GUI Batch MAE-Deployment

the eNodeB from reconfiguration
Independent and radio data
Operator Mode planning file
to RAN Sharing
with Dedicated
Carrier Mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 25

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Scenario Recommended Recommended Recommended

Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.6.3 Changing GUI Batch MAE-Deployment

the eNodeB from reconfiguration
Independent and radio data
Operator Mode planning file
to Hybrid RAN
Sharing Mode

1.6.4 Adding a GUI Batch MAE-Deployment

Neighboring reconfiguration
eNodeB and radio data
planning file

1.6.5 Changing ID/Name ID/Name MAE-Deployment

the eNodeB modification modification
Names

1.6.6 Changing ID/Name ID/Name MAE-Deployment

the eNodeB ID modification modification

1.6.7 Adjusting GUI Batch MAE-Deployment

the PLMN reconfiguration

Table 1-5 Device data reconfigurations

Scenario Recommended Recommended Recommended
Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.7.1 Replacing Main control Main control MAE-Deployment

the Main Control board and port board and port
Board When No number number
SeGW Is reconfiguration reconfiguration
Deployed

1.7.2 Replacing Main control Main control MAE-Deployment

the Main Control board and port board and port
Board When an number number
SeGW Is reconfiguration reconfiguration
Deployed

1.7.3 Replacing GUI Batch MAE-Deployment

BBPs reconfiguration

1.7.4 Changing GUI Batch MAE-Deployment

CPRI Ports for RF reconfiguration
Modules

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 26

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Scenario Recommended Recommended Recommended

Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.7.5 Adding or GUI Batch MAE-Deployment

Deleting an RF reconfiguration
Module

1.7.6 MML MML MAE-Access

Transmission
Capacity
Expansion from
One LMPT Board
to LMPT + UMPT
Boards (Mode 1)
(TDD) (IPv4
Transmission
Only)

1.7.7 MML MML MAE-Access

Transmission
Capacity
Expansion from
One LMPT Board
to LMPT + UMPT
Boards (Mode 2)
(TDD) (IPv4
Transmission
Only)

1.7.8 GUI Batch MAE-Deployment

Transmission reconfiguration
Capacity
Expansion from
One UMPT Board
to Two UMPT
Boards (FDD/NB-
IoT) (IPv4
Transmission
Only)

1.7.9 Signaling MML commands Batch MAE-Deployment

Capacity reconfiguration
Expansion from
One UMPT to
One Primary
UMPT + One
Extension UMPT/
LMPT (IPv4
Transmission
Only)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 27

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Scenario Recommended Recommended Recommended

Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.7.10 Signaling MML commands Batch MAE-Deployment

Capacity reconfiguration
Expansion from
One LMPT to
One Primary
UMPT + One
Extension LMPT
(IPv4
Transmission
Only)

Table 1-6 Interface and link data reconfigurations

Scenario Recommended Recommended Recommended
Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.8.1 Adding an GUI Batch MAE-Deployment

MME Connection reconfiguration

1.8.2 Adding an GUI Batch MAE-Deployment

S-GW reconfiguration
Connection

1.8.3 Replacing GUI Batch MAE-Deployment

an MME reconfiguration

1.8.4 Replacing GUI Batch MAE-Deployment

an S-GW reconfiguration

1.8.5 Replacing GUI Batch MAE-Deployment

the MAE reconfiguration

1.8.6 Changing GUI Batch MAE-Deployment

the Local reconfiguration
Maintenance IP
Address

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 28

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Scenario Recommended Recommended Recommended

Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.8.7 Changing ● MML ● MML ● LMT if the IP

the Device IP commands if commands if address to be
Address (Old the IP address the IP address changed is
Model)/1.8.8 to be changed to be changed used as an
Changing the is used as an is used as an address for
IPv4/IPv6 address for address for remote
Address (New remote remote maintenance
Model) maintenance maintenance ● MAE-
● Batch ● Batch Deployment if
reconfiguration reconfiguration the IP address
if the IP if the IP to be changed
address to be address to be is not used as
changed is not changed is not an address for
used as an used as an remote
address for address for maintenance
remote remote
maintenance maintenance

1.8.9 Changing GUI Batch MAE-Deployment

the IP Address of reconfiguration
a Clock Server

1.8.10 Changing Batch Batch MAE-Deployment

the SCTP Link reconfiguration reconfiguration
Number (for IPv4
Transmission
Only)

1.8.11 Removing GUI Batch MAE-Deployment

an X2 Interface reconfiguration

1.8.12 Modifying ● MML ● MML ● LMT if the

the Ethernet Port commands if commands if Ethernet port
Number (Old the Ethernet the Ethernet to be changed
Model)/1.8.13 port to be port to be is used as a
Modifying the changed is changed is port for remote
Ethernet Port used as a port used as a port maintenance
Number (New for remote for remote ● MAE-
Model) maintenance maintenance Deployment if
● Batch ● Batch the Ethernet
reconfiguration reconfiguration port to be
if the Ethernet if the Ethernet changed is not
port to be port to be used as a port
changed is not changed is not for remote
used as a port used as a port maintenance
for remote for remote
maintenance maintenance

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 29

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Scenario Recommended Recommended Recommended

Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.8.14 MME GUI Batch MAE-Deployment

Dual-homing reconfiguration
Reconfiguration

1.8.15 Changing GUI Batch MAE-Deployment

the Transmission reconfiguration
Mode from Link
Mode to
Endpoint Mode
(Only for IPv4
Transmission)

1.8.16 Adding an GUI Batch MAE-Deployment

eCoordinator reconfiguration
Connection
(Only for IPv4
Transmission)

1.8.17 Replacing GUI Batch MAE-Deployment

an eCoordinator reconfiguration
(Only for IPv4
Transmission)

1.8.18 Planning file Planning file MAE-Deployment

Optimizing the
Transmission
Configuration
Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 30

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-7 Security networking data reconfigurations

Scenario Recommended Recommended Recommended
Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.9.1 Changing GUI Batch MAE-Deployment

the Transport reconfiguration
Network from
Non-Security
Mode to PKI
Security Mode
(Old Model)/
1.9.2 Changing
the Transport
Network from
Non-Security
Mode to PKI
Security Mode
(New Model)

1.9.3 Changing GUI Batch MAE-Deployment

the Transport reconfiguration
Network from
Non-Security
Mode to PSK
Security Mode
(Old Model)/
1.9.4 Changing
the Transport
Network from
Non-Security
Mode to PSK
Security Mode
(New Model)

1.9.5 Changing GUI Batch MAE-Deployment

the Security reconfiguration
Mode from PSK
to PKI

1.9.6 Changing a MML commands MML commands MAE-Access

Single IPsec
Tunnel to an
IPsec Tunnel Pair
(Only for IPv4
Transmission)

1.9.7 Changing a GUI Batch MAE-Deployment

Single Virtual reconfiguration
Route to Active/
Standby Static IP
Route

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 31

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Scenario Recommended Recommended Recommended

Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.9.8 Replacing GUI Batch MAE-Deployment

an SeGW reconfiguration

1.9.9 Adjusting GUI Batch MAE-Deployment

the VLAN reconfiguration

1.9.10 Changing GUI Batch MAE-Deployment

the VLAN Mode reconfiguration
from VLAN
Group to Single
VLAN (Only for
IPv4
Transmission)

1.9.11 Changing GUI Batch MAE-Deployment

the VLAN Mode reconfiguration
from Single
VLAN to
Interface VLAN
(Only for IPv4
Transmission)

Table 1-8 Reconfigurations dedicated to the LampSite solution

Scenario Recommended Recommended Recommended

Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.10.1 Adding a GUI Batch MAE-Deployment

pRRU- reconfiguration
Aggregation Cell

1.10.2 Combining GUI Batch MAE-Deployment

pRRU- reconfiguration
Aggregation
Cells

1.10.3 Splitting a GUI Batch MAE-Deployment

pRRU- reconfiguration
Aggregation Cell

1.10.4 GUI Batch MAE-Deployment

Reconstructing reconfiguration
pRRU-
Aggregation
Cells to a Pico
SFN Cell

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 32

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Scenario Recommended Recommended Recommended

Mode for One NE Mode for Batch Tool
Reconfiguration NE
Reconfiguration

1.10.5 Adjusting GUI Batch MAE-Deployment

pRRU Transmit reconfiguration
Power

1.10.6 Sharing MML commands MML commands MAE-Access

BBUs Between
Macro and
LampSite Base
Stations

1.10.7 Adding an GUI Batch MAE-Deployment

LAA Cell reconfiguration

1.10.8 Adding an GUI Batch MAE-Deployment

RFA Cell reconfiguration

1.5 Cell Data Reconfigurations

This section describes how to reconfigure cells served by eNodeBs in typical
scenarios.

1.5.1 Adding an FDD/NB-IoT Cell (Common Scenarios)

This section describes how to add an FDD/NB-IoT cell.

1.5.1.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adding an FDD/NB-IoT cell.

Application Scenario
● There are weak-signal areas or coverage holes in the current base station
coverage, requiring an additional cell to supplement coverage.
● As the traffic increases, the existing cell capacity cannot meet the traffic
demand of CEUs. In this situation, the coverage areas of the existing cell must
be reduced and an additional cell is required.
● The operator uses a new frequency band.

Reconfiguration Impact
When an RRU chain or ring is moved to a new baseband processing unit (BBP),
the cells that are set up on this RRU chain or ring become unavailable for use.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 33

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme
Determine the reconfiguration scheme for adding an FDD/NB-IoT cell to an
existing site according to the following table.

Table 1-9 Scheme options

If... Then...

Baseband resources are insufficient Add BBPs.

RF resources are insufficient ● Add RF modules and antenna line

devices (ALDs) on the existing RRU
chain or ring.
● Add an RRU chain or ring, and then
add RF modules and ALDs.

A BBP to which RF modules are Modify the position of the BBP where
connected is changed the RRU chain or ring is set up.

The downtilt of an antenna needs to Add a remote electrical tilt (RET)

be remotely adjusted antenna.

Link quality is imbalanced between the Add a tower-mounted amplifier

uplink and the downlink, uplink (TMA).
coverage is limited, or the uplink
attenuation from the antenna to the
RF module is excessively large

The numbers of TX and RX channels in 1. Add a sector without creating the

a sector are inconsistent default sector equipment.
2. Add a set of sector equipment.

NOTICE

● When a new RF module and an existing RF module are configured in hybrid

mode in an FDD network, the RF modules must comply with the hybrid
configuration principles. For details, see section Hardware > Combined-RRU/
RFU-Sector Cells in Cell Management Feature Parameter Description.
● In an LTE network, hybrid configuration refers to connecting two RF modules
operating in the same frequency band to the same BBP. The RF modules serve
one sector and provide larger capacity. For example, two 2T2R RRUs are
configured to serve a 4T4R cell.

The reconfiguration procedure for adding an FDD/NB-IoT cell is illustrated in

Figure 1-8.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 34

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-8 Adding an FDD/NB-IoT cell

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 35

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Figure 1-9 shows an example of the topology changes after a BBP and an RF
module are added.

Figure 1-9 Topologies before and after the reconfiguration

1.5.1.2 Engineering Preparation

This section describes the engineering preparation for adding an FDD/NB-IoT cell,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-10 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 36

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-10 Information to be collected

Information Description

Base station model Model of the base station to which an FDD/NB-IoT cell
is to be added, for example, DBS3900

BBP model Model of the BBP, for example, UBBP

RF module type Type of the RF module to be added, for example, LRRU,

MRRU, LRFU, or MRFU

Topology If an RF module is to be added, the following

information needs to be collected:
● The CPRI topology for RF modules, for example, the
chain or ring topology
● The insertion position of the RF module to be added,
for example, in the chain or at the tail of the chain

Antenna equipment Models of the remote electrical tilt (RET) antenna and
tower-mounted amplifier (TMA)

Sector information ● Number of antennas in the sector

● TX/RX mode of the sector

Cell information Basic information about the cell to be added, for

example, the bandwidth, EARFCN, duplex mode,
reference signal power, and TX/RX mode of the cell

NOTE

Before the reconfiguration, run the DSP TXBRANCH, DSP RXBRANCH or DSP RRU command
to query the capability of the RF module. This is to ensure that the EARFCN, bandwidth,
and power of the cell are still within the capability range of the RF module after the
reconfiguration.

Hardware Preparation
Table 1-11 describes the hardware to be prepared.

Table 1-11 Hardware to be prepared

If... Then...

BBPs are insufficient Add BBPs.

RF resources are Add RF modules, CPRI cables, ALDs, and optical

insufficient modules.

An RET antenna Add a remote control unit (RCU) and antenna interface
needs to be standards group (AISG) multi-wire cables.
configured

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 37

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

A TMA is to be Add a TMA and jumpers.

configured

Software Preparation
If the RET antenna or TMA to be added needs to be upgraded, acquire the latest
software and data from the vendors.

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Table 1-12 Data preparation for adding an FDD cell

SN Oper MO Configuration Reference

ation

1 Add RU (using MML For details about parameter

commands)/BBP (using the settings, see Base Station
MAE-Deployment) Cabinets and Subracks
(Including the BBU Subrack)
Configuration Feature
Parameter Description.
2 Add RRUCHAIN For details about parameter
settings, see RF Unit and
3 Add RRU/RFU Topology Management Feature
Parameter Description.
4 Add RET For details about parameter
settings, see ALD Management
Feature Parameter Description.
5 Modi AntennaPort/RetPort Change the value of ALD
fy Power Switch to ON.

6 Add TMA For details about parameter

settings, see ALD Management
Feature Parameter Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 38

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Oper MO Configuration Reference

ation

7 Add Sector For details about parameter

settings, see Cell Management
Feature Parameter Description.
8 Modi RRUCHAIN Move the RRU chain or ring to
fy the new BBP.

9 Add SectorEqm For details about parameter

settings, see Cell Management
10 Add Cell Feature Parameter Description.
11 Add eUCellSectorEqm

12 Add CellOp

Table 1-13 Data preparation for adding an NB-IoT cell

SN Oper MO Configuration Reference
ation

1 Add RU (using MML For details about parameter

commands)/BBP (using the settings, see Base Station
MAE-Deployment) Cabinets and Subracks
(Including the BBU Subrack)
Configuration Feature
Parameter Description.
2 Add RRUCHAIN For details about parameter
settings, see RF Unit and
3 Add RRU/RFU Topology Management
Feature Parameter
Description.
4 Add RET For details about parameter
settings, see ALD
Management Feature
Parameter Description.
5 Modi AntennaPort/RetPort Change the value of ALD
fy Power Switch to ON.

6 Add TMA For details about parameter

settings, see ALD
Management Feature
Parameter Description.
7 Add Sector For details, see NB-IoT Basics
(FDD) Feature Parameter
Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 39

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Oper MO Configuration Reference

ation

8 Modi RRUCHAIN Move the RRU chain or ring

fy to the new BBP.

9 Add SectorEqm For details, see NB-IoT Basics

(FDD) Feature Parameter
10 Add ● If the added NB-IoT cell is a Description.
STAND_ALONE cell or a
GUARD_BAND cell, add a Cell
MO directly.
● If the added NB-IoT cell is
deployed in LTE in-band
mode, add the corresponding
FDD Cell and CellRbReserve
MOs first.

11 Add PRB

12 Add EuPrbSectorEqm

13 Add CnOperatorTa

14 Add CellOp

15 Add MmeCapInfo

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario-specific template being "Adding an FDD Cell" or
"Adding an NB-IoT Cell"). For details, see the interactive operation guide
1.11.2 Using the Batch Reconfiguration Mode of the MAE-Deployment to
Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 40

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

MML Configuration Script Example

In the following example, a UBBP, an RRU chain, an RRU, an RET antenna, and a
TMA are added.
NOTE

If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

Scenario 1: Adding an FDD cell

/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="*****", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="*************";
/*Adding a UBBP*/
ADD BRD: SN=0, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-1&LTE_TDD-0&NBIOT-0;
/*Adding an RRU chain*/
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=3, HPN=0;
/*Adding an RRU*/
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=LRRU, RS=LO, RN="60", RXNUM=2,
TXNUM=2;
/*Adding an RET antenna*/
ADD RET: DEVICENO=0, DEVICENAME="RET1", CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
POLARTYPE=SINGLE, SCENARIO=REGULAR;
/*Turning on the ALD power supply switch*/
MOD RETPORT: CN=0, SRN=60, SN=0, PWRSWITCH=ON;
/*Adding a TMA*/
ADD TMA: DEVICENO=1, DEVICENAME="TMA1", CTRLCN=0, CTRLSRN=60, CTRLSN=0, SUBUNITNUM=1,
VENDORCODE="hw", SERIALNO="hw";
/*Adding a sector (If multiple RATs of a co-MPT base station share the same SECTOR MO, common data for
these RATs is configured here and the command needs to be executed once. Before running the RMV
SECTOR command, ensure that the SECTOR MO is no longer used by any RAT.)*/
ADD SECTOR: sectorId=0, antNum=2, ant1Cn=0, ant1Srn=60, ant1Sn=0, ant1N=R0A, ant2Cn=0, ant2Srn=60,
ant2Sn=0, ant2N=R0B, createSectorEqm=FALSE;
/*Adding sector equipment*/
ADD SECTOREQM: sectorEqmId=0, sectorId=0, antNum=2, ant1Cn=0, ant1Srn=60, ant1Sn=0, ant1N=R0A,
antType1=RXTX_MODE, ant2Cn=0, ant2Srn=60, ant2Sn=0, ant2N=R0B, antType2=RXTX_MODE;
/*Adding a cell*/
ADD CELL: LocalCellId=0, CellName="0", FreqBand=7, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3000,
UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=0, PhyCellId=0, FddTddInd=CELL_FDD,
RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R;
/*Adding sector equipment for the cell*/
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
/*Adding operator information for the cell*/
ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
/*Activating the new cell*/
ACT CELL: LocalCellId=0;

Scenario 2: Adding an NB-IoT cell

/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="*****", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="*************";
/*Adding a UBBP*/
ADD BRD:CN=0,SRN=0,SN=3,BT=UBBP,BBWS=GSM-0&UMTS-0&LTE_FDD-1&LTE_TDD-0&NBIOT-1;
/*Adding an RRU chain*/
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=3, HPN=0;
/*Adding an RRU*/
ADD
RRU:CN=0,SRN=61,SN=0,TP=TRUNK,RCN=0,PS=0,RT=MRRU,RS=MO,RXNUM=2,TXNUM=2,ALMPROCSW=ON;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 41

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Adding an RET antenna*/

ADD RET: DEVICENO=0, DEVICENAME="RET1", CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
POLARTYPE=SINGLE, SCENARIO=REGULAR;
/*Turning on the ALD power supply switch*/
MOD RETPORT: CN=0, SRN=60, SN=0, PWRSWITCH=ON;
/*Adding a TMA*/
ADD TMA: DEVICENO=1, DEVICENAME="TMA1", CTRLCN=0, CTRLSRN=60, CTRLSN=0, SUBUNITNUM=1,
VENDORCODE="hw", SERIALNO="hw";
/*Adding a sector (If multiple RATs of a co-MPT base station share the same SECTOR MO, common data for
these RATs is configured here and the command needs to be executed once. Before running the RMV
SECTOR command, ensure that the SECTOR MO is no longer used by any RAT.)*/
ADD SECTOR: sectorId=0, antNum=2, ant1Cn=0, ant1Srn=60, ant1Sn=0, ant1N=R0A, ant2Cn=0, ant2Srn=60,
ant2Sn=0, ant2N=R0B, createSectorEqm=FALSE;
/*Adding sector equipment*/
ADD SECTOREQM: sectorEqmId=0, sectorId=0, antNum=2, ant1Cn=0, ant1Srn=60, ant1Sn=0, ant1N=R0A,
antType1=RXTX_MODE, ant2Cn=0, ant2Srn=60, ant2Sn=0, ant2N=R0B, antType2=RXTX_MODE;
/*The MML command examples for adding cells of different types are listed here.*/
/*Adding a cell whose deployment mode is GUARD_BAND or STAND_ALONE*/
ADD CELL:LOCALCELLID=1,CELLNAME="CELL_NBIOT", NbCellFlag=TRUE, CellId=1, PhyCellId=1,
FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE,
TxRxMode=2T2R;
/*Adding a PRB for a cell whose deployment mode is STAND_ALONE*/
ADD PRB: LocalCellId=1, PrbId=0, DeployMode=STAND_ALONE, FreqBand=8, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=3550, DlFreqOffset=NEG_0DOT5;
/*Adding a PRB for a cell whose deployment mode is GUARD_BAND*/
ADD PRB: LocalCellId=1, PrbId=0, DeployMode=GUARD_BAND, FreqBand=8, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=3550, DlFreqOffset=POS_0, LteBandWidth=LTE_SYSTEM_BW_20M, LteDlEarfcn=3550;
/*Adding an FDD cell before adding a cell whose deployment mode is IN_BAND*/
ADD CELL: LocalCellId=0, CellName="0", NbCellFlag=FALSE, FreqBand=8, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=3550, UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=0, PhyCellId=0,
FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R;
/*Reserving RBs from the FDD cell for a cell whose deployment mode is IN_BAND*/
ADD CELLRBRESERVE: LocalCellId=0, Index=3, RbRsvMode=NB_DEPLOYMENT,
RbRsvType=DOWNLINK_MODE, RbRsvStartIndex=19, RbRsvEndIndex=19;
/*Adding a cell whose deployment mode is IN_BAND*/
ADD CELL: LocalCellId=1, CellName="1", NbCellFlag=TRUE,
CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1;&COVERAGE_LEVEL_2-1;, CellId=1,
PhyCellId=0,FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE,
TxRxMode=2T2R;
ADD PRB: LocalCellId=1, PrbId=0, DeployMode=IN_BAND, FreqBand=8, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=3540, DlFreqOffset=POS_0, LteCellId=0;
/*Adding operator information for the cell*/
ADD CELLOP: LocalCellId=1, TrackingAreaId=0;
/*Adding the MME feature configuration information, indicating whether the MME supports NB-IoT, and
whether the NB-IoT MME supports LTE services*/
ADD MMECAPINFO: MmeCapCfgId=0, S1CfgType=S1_CFG, S1Id=0, NbCiotEpsOptCap=CP_UP,
NbLteSupportCap=SUPPORT;
/*Adding sector equipment for the PRB*/
ADD EUPRBSECTOREQM: LocalCellId=1, PrbId=0, SectorEqmId=0;
/*Activating the new cell*/
ACT CELL: LocalCellId=1;

1.5.1.3 Engineering Implementation

This section describes the engineering implementation for adding an FDD/NB-IoT
cell, including prerequisites, context, and procedure.

Prerequisites
Information for adding an FDD/NB-IoT cell has been collected, hardware,
software, and configuration data are ready, and the license file is available in the
save path on the FTP server.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 42

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Insert the BBP into the subrack. For details about the operation, see
Maintaining the Case-Structured BBU > Replacing the LBBP or
Replacing the UBBP in the BBU Hardware Maintenance Guide.
b. Install an optical module. For details about the operation, see the
corresponding Replacing the Optical Module section in the BBU
Hardware Maintenance Guide. For example, for details about how to
install an optical module on a case-structured BBU, see Replacing the
Optical Module.
c. Install an RF module.

▪ If an RRU is to be added, install the RRU according to the

instructions in the corresponding installation guide.

▪ If an RFU is to be added, install the RFU according to the instructions

in section Replacing an RFU in 3900 & 5900 Series Base Station
Maintenance Guide.
d. Install the antenna system. For details, see Antenna Installation.
● Remote Operations
NOTE

If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
– Using the MAE-Deployment:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
Example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 43

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iv. (Optional) If an RRU is inserted into an existing RRU chain or ring,

block all cells served by the RRUs following this RRU on the chain or
ring.
Run the BLK CELL command with Cell admin state set to
CELL_HIGH_BLOCK.
v. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
vi. Activate the new cell.
Run the ACT CELL command.
Example: ACT CELL: LocalCellId=0;
vii. Unblock cells.
Run the UBL CELL command.
viii. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Run the following commands to back up and export the
configuration file. The configuration file can be used to roll back the
base station configurations to the original state, if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. (Optional) If an RRU is inserted into an existing RRU chain or ring,
block all cells served by the RRUs following this RRU on the chain or
ring.
Run the BLK CELL command with Cell admin state set to
CELL_HIGH_BLOCK.
iv. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
v. Unblock cells.
Run the UBL CELL command.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 44

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

vi. After data reconfiguration is complete, set the eNodeB maintenance

mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.5.1.4 Engineering Verification

This section describes how to verify the addition of an FDD/NB-IoT cell.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 3 Run the LST CELL command to check whether the cell information is the same as
planned.

If the cell information is not the same as planned, perform the following steps:

If... Then...

The reconfiguration is
performed on the MAE-
Deployment
Check whether the cell information in the modified data file is the
same as planned:
● If they are different, modify the configuration data file again and
import it into the system. Then perform the operations in
Engineering Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the data is
imported into the system or delivered to the base station. In this
situation, contact Huawei technical support or dial the Huawei
technical support hotline.

The reconfiguration is
performed by using MML
commands
Check whether the parameter settings in the script are correct:
● If they are incorrect, modify the parameters in the script. Run the
RMV CELL command to delete the cell. Then run the ADD CELL
command to add a cell again.
● If they are correct, contact Huawei technical support or dial the
Huawei technical support hotline.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 45

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.1.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the cable connections.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 46

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 4 Verify that engineering rollback is successful according to instructions in 1.5.1.4

Engineering Verification.

----End

1.5.2 Adding an FDD Cell (Dual-Carrier Capacity Expansion

Scenarios)
This section describes how to add an FDD cell for dual-carrier capacity expansion.

1.5.2.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adding an FDD cell for dual-
carrier capacity expansion.

Application Scenario
● As the traffic increases, the existing cell capacity cannot meet the traffic
demand of cell edge users (CEUs). In this situation, cells must be added to
expand the capacity.
● The operator uses a new frequency band.

Reconfiguration Impact
When the RRU chain/ring topology is changed to the load sharing topology, a
breakpoint must be set on the chain/ring. Before the breakpoint is set, the cells
served by the RRUs on the RRU chain/ring must be deactivated.

Reconfiguration Scheme
NOTE

● The RRU must support multiple carriers.

● The bandwidth supported by the RRU must be greater than the sum of the two cells'
bandwidths after the expansion.

Determine the reconfiguration scheme for adding an FDD cell to an existing site
for dual-carrier capacity expansion according to the following table.

Table 1-14 Scheme options

If... Then...

Baseband resources are insufficient ● Add a BBP.

● Replace the BBP with a BBP that
supports a larger number of cells.
For details about how to replace a
BBP, see 1.7.3 Replacing BBPs.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 47

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

CPRI resources are insufficient ● Add an optical fiber for a load

sharing topology to add CPRI
resources.
● Change an optical module to
increase the CPRI bandwidth.
● Change the CPRI compression mode
to a higher compression rate for the
cells served by the RRUs on the
RRU chain/ring to support two
carriers.

Figure 1-10 shows the reconfiguration procedure for adding an FDD cell for dual-
carrier capacity expansion.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 48

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-10 Procedure for adding an FDD cell for dual-carrier capacity expansion

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 49

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Figure 1-11 shows the topologies before and after the reconfiguration.

Figure 1-11 Topologies before and after the reconfiguration

1.5.2.2 Engineering Preparation

This section describes the engineering preparation for adding an FDD cell for dual-
carrier capacity expansion, including information collection and preparation of
hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-15 describes the information to be collected for FDD dual-carrier capacity
expansion.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 50

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-15 Information to be collected

Information Description

BBP model Model of the BBP, for example, UBBP

Topology CPRI topology for RF modules, for example, the chain or

inter-board load sharing topology

Cell information Basic information about cells, for example, the

bandwidth, EARFCN, duplex mode, reference signal
power, and TX/RX mode of the cells.

Sector equipment Information about sector equipment of the cells,

information of cells including sector equipment ID, reference signal power,
and baseband equipment

NOTE

Before the reconfiguration, run the DSP TXBRANCH, DSP RXBRANCH or DSP RRU command
to query the capability of the RF module. This is to ensure that the EARFCN, bandwidth,
and power of the cell are still within the capability range of the RF module after the
reconfiguration.

Hardware Preparation
Table 1-16 describes the hardware to be prepared before adding an FDD cell for
dual-carrier capacity expansion.

Table 1-16 Hardware to be prepared

If... Then...

Baseband resources ● Prepare a new BBP for the cell to be added based on
are insufficient the board specifications.
● Check whether the cell to be added can be served by
the same BBP as the existing cells. If not, prepare a
new BBP.

CPRI resources are ● Prepare new CPRI cables.

insufficient, and ● Prepare new optical modules.
hardware must be
added or replaced

Software Preparation
N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 51

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

License File Preparation

If the license file is to be updated, a new license file is required. If a cell is to be
added, apply for a cell-specific license. If a new carrier is to be added to existing
RRUs, apply for the multi-carrier license.

Security Certificate Preparation

N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Table 1-17 Data preparation for FDD dual-carrier capacity expansion

SN Ope MO Configuration Reference

ratio
n

1 Add RU (using MML Set the Board Type parameter.

commands)/BBP For details about parameter settings, see
(using the MAE- Base Station Cabinets and Subracks
Deployment) (Including the BBU Subrack)
Configuration Feature Parameter
Description.
2 Modi RRUCHAIN Change the CPRI topology type to a ring
fy topology in either of the following ways:
● Connect the two ends of the ring to
the two CPRI ports on the same BBP.
● Connect the two ends of the ring to
the CPRI ports on two BBPs.

3 Add Cell For details about parameter settings, see

Cell Management Feature Parameter
4 Add eUCellSectorEqm Description.
5 Add BASEBANDEQM If the BBPs need to be specified for the
cells, bind the baseband equipment to
6 Modi eUCellSectorEqm the cells.
fy

7 Add CellOp For details about parameter settings, see

Cell Management Feature Parameter
Description.
8 Modi PDSCHCfg Perform this step if the maximum
fy transmit power for the two cells exceeds
the RRU capacity after a new cell is
added.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 52

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario-specific template being "Adding an FDD Cell (Dual-
Carrier Capacity Expansion Scenarios)"). For details, see the interactive
operation guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

Assume that a new UBBP board is required and the RRU chain/ring must be
modified, the MML configuration scripts are as follows:

NOTE

If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="*****", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="*************";
/*Adding a UBBP*/
ADD BRD: SN=2, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-0&NBIOT-0&NR-1;
/*Modifying the RRU chain/ring*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0;
MOD RRUCHAIN: RCN=0, TT=LOADBALANCE, HSRN=0, HSN=2, HPN=0, TSRN=0, TSN=3, TPN=0;
MOD RRUCHAIN: RCN=0, BRKPOS1=255, BRKPOS2=255;
/*Adding a cell*/
ADD CELL: LocalCellId=1, CellName="0", FreqBand=7, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3000,
UlBandWidth=CELL_BW_N50, DlBandWidth=CELL_BW_N50, CellId=1, PhyCellId=1, FddTddInd=CELL_FDD,
RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T2R;
/*Adding sector equipment for the cell*/
ADD EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=0;
/*(Optional) Binding the baseband equipment to the cells if the BBPs need to be specified for the cells*/
ADD BASEBANDEQM: BASEBANDEQMID=2, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=2;
ADD BASEBANDEQM: BASEBANDEQMID=3, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=3;
MOD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, BaseBandEqmId=2;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 53

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

MOD EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=0, BaseBandEqmId=3;

/*Adding operator information for the cell*/
ADD CELLOP: LocalCellId=1, TrackingAreaId=0;
/*(Optional) Modifying PDSCH configuration if the maximum transmit power for the two cells exceeds the
RRU capacity after a new cell is added*/
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=152;
/*Activating the new cell*/
ACT CELL: LocalCellId=1;

1.5.2.3 Engineering Implementation

This section describes the engineering implementation for adding an FDD cell for
dual-carrier capacity expansion, including prerequisites, context, and procedure.

Prerequisites
Hardware, software, license files, and data required for FDD dual-carrier capacity
expansion are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Insert the BBP into the subrack. For details about the operation, see
Maintaining the Case-Structured BBU > Replacing the LBBP or
Replacing the UBBP in the BBU Hardware Maintenance Guide.
b. Install an optical module. For details about the operation, see the
corresponding Replacing the Optical Module section in the BBU
Hardware Maintenance Guide. For example, for details about how to
install an optical module on a case-structured BBU, see Replacing the
Optical Module.
c. Install a CPRI optical fiber. For details, see Installing a CPRI Optical
Fiber in the installation guide of the corresponding RRU.
● Remote Operations
– Using the MAE-Deployment:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 54

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iii. Import a new license file.

Run the INS LICENSE command.
Example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
iv. (Optional) If an RRU is inserted into an existing RRU chain or ring,
block all cells served by the RRUs following this RRU on the chain or
ring.
Run the BLK CELL command with Cell admin state set to
CELL_HIGH_BLOCK.
v. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
vi. Activate the new cell.
Run the ACT CELL command.
Example: ACT CELL: LocalCellId=0;
vii. Unblock cells.
Run the UBL CELL command.
viii. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Block cells.
Run the BLK CELL command with Cell admin state set to
CELL_HIGH_BLOCK.
iv. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 55

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

v. Unblock cells.
Run the UBL CELL command.
vi. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.5.2.4 Engineering Verification

This section describes how to verify the reconfiguration of adding an FDD cell for
dual-carrier capacity expansion.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 3 Run the LST CELL command to check whether the cell information is the same as
planned.

If the cell information is not the same as planned, perform the following steps:

If... Then...

The reconfiguration is
performed on the MAE-
Deployment
Check whether the cell information in the modified data file is the
same as planned:
● If they are different, modify the configuration data file again and
import it into the system. Then perform the operations in
Engineering Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the data is
imported into the system or delivered to the base station. In this
situation, contact Huawei technical support or dial the Huawei
technical support hotline.

The reconfiguration is
performed by using MML
commands
Check whether the parameter settings in the script are correct:
● If they are incorrect, modify the parameters in the script. Run the
RMV CELL command to delete the cell. Then run the ADD CELL
command to add a cell again.
● If they are correct, contact Huawei technical support or dial the
Huawei technical support hotline.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 56

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

----End

1.5.2.5 Engineering Rollback

If the reconfiguration fails, the eNodeB configuration can be rolled back to the
original state.

Procedure
Step 1 Roll back the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 57

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful by following the procedure described
in 1.5.4.4 Engineering Verification.

----End

1.5.3 Adding a TDD Cell (Common Scenarios)

This section describes how to add a TDD cell.

1.5.3.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adding a TDD cell.

Application Scenario
● There are weak-signal areas or coverage holes in the current base station
coverage, requiring an additional cell to supplement coverage.
● As the traffic increases, the existing cell capacity cannot meet the traffic
demand of CEUs. In this situation, the coverage areas of the existing cell must
be reduced and an additional cell is required.
● The operator uses a new frequency band.

Reconfiguration Impact
When an RRU chain or ring is moved to a new BBP, the cells that are set up on
this RRU chain or ring are unavailable.

NOTE

After a cell is added, neighboring cell information related to this new cell must be configured on
the neighboring eNodeB based on the network plan.

Reconfiguration Scheme
Determine the reconfiguration scheme for adding a TDD cell to an existing site
according to the following table.

Table 1-18 Scheme options

If... Then...

The baseband resources are Add a BBP.

insufficient

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 58

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The RF resources are insufficient ● Use the unused channels on an

installed RRU to set up a cell.
● Add an RRU chain or ring, and then
add an RRU and ALDs to the RRU
chain or ring.

The RF resources are sufficient ● Use the unused channels on an

installed RRU to set up a cell. For
example, if a carrier has already
been set up on the R0A and R0B
channels of a 4-channel RRU,
another carrier can be set up on the
R0C and R0D channels, which
jointly serve one sector.
● Check whether the CPRI resources
of the RRU are sufficient. If they are
insufficient:
– Add an optical fiber for a load
sharing topology to add CPRI
resources.
– Change an optical module to
increase the CPRI bandwidth.
– Change the CPRI compression
mode for the existing cells. For
example, only one carrier can be
set up on an 8T8R RRU chain
without CPRI compression. An
additional carrier requires an
optical fiber and load sharing
topology.

The antenna tilt is required to be Add an RET antenna.

remotely adjustable

The TDD cell to be added must Turn on the beamforming algorithm

support beamforming switch for the cell.

Figure 1-12 shows the reconfiguration procedure for adding a TDD cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 59

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-12 Procedure for adding a TDD cell

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 60

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Use adding a BBP and an RF module as an example. Figure 1-13 shows the
topologies before and after the reconfiguration.

Figure 1-13 Topologies before and after the reconfiguration

1.5.3.2 Engineering Preparation

This section describes the engineering preparation for adding a TDD cell, including
information collection and preparation of hardware, software, license files, security

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 61

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

certificates, and data. It also describes the data preparation mode and provides
MML configuration script examples.

Information Collection
Table 1-19 describes the information to be collected before adding a TDD cell.

Table 1-19 Information to be collected

Information Description

Base station model Model of the eNodeB to which the TDD cell is to be
added, for example, DBS3900 LTE

BBP model Model of the BBP, for example, UBBP

RF module type Type of the RF module to be added, for example, LRRU,

MRRU, or MPMU

Topology ● CPRI topology for RF modules, for example, the star,

chain, or inter-board load sharing topology
● Position of a new RF module in the CPRI topology,
for example, the chain tail

Antenna equipment Type of the RET antenna

Sector information Number of antennas, channel numbers, cabinet number,

subrack number, slot number, and port number of the
RRU in a sector

Sector equipment Channel numbers of the transmit and receive antennas,

information and the transmit and receive mode of the antennas in
the sector equipment

Cell information ● Basic information about the cells, for example, the
bandwidth, EARFCN, and duplex mode
● Multi-RRU combination mode, for example, single
RRU mode, two-RRU combination mode, cell
combination mode, or single frequency network
(SFN)

Sector equipment Information about sector equipment of the cells,

information of the including sector equipment ID, reference signal power,
cell and baseband equipment

NOTE

Before the reconfiguration, run the DSP TXBRANCH, DSP RXBRANCH or DSP RRU command
to query the capability of the RF module. This is to ensure that the EARFCN, bandwidth,
and power of the cell are still within the capability range of the RF module after the
reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 62

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Hardware Preparation
Table 1-20 describes the hardware to be prepared for adding a TDD cell.

Table 1-20 Hardware to be prepared

If... Then...

BBPs are insufficient ● Prepare a new BBP for the cell to be added based on
the board specifications.
● Check whether the cell to be added can be served by
the same BBP as the existing cells. If not, install a
new BBP. For the constraints on binding cells with
baseband equipment, see Binding Baseband
Equipment. For example, cells with different
subframe configurations cannot be served by one
BBP. To add a cell with a different subframe
configuration, a new BBP must be installed.

RF resources are ● Add RRUs for coverage holes and weak coverage
insufficient areas based on the network plan.
● Check whether capacity expansion can be achieved
on the RRUs in use, based on the bandwidth and
frequencies supported by the RRUs. If the carriers
provided by the existing RRUs are insufficient, add
RRUs. If there are sufficient RRUs, check whether the
CPRI resources are sufficient. If the CPRI resources are
insufficient, change the CPRI compression mode or
add a CPRI optical fiber and an optical module.
● Prepare RF-related hardware, including RF units, CPRI
optical fibers, antennas, and optical modules.

An RET antenna Prepare RCUs, AISG multi-wire cables, and jumpers

needs to be
configured

Software Preparation
If the RET to be added needs to be upgraded, acquire the latest software and data
from the vendor.

License File Preparation

If the license file is to be updated, a new license file is required. For the cell to be
added, apply for a cell-specific license. If an RRU is added, apply for an RF-related
hardware license. If a new carrier is to be added to existing RRUs, apply for the
multi-carrier license.

Security Certificate Preparation

N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 63

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Table 1-21 Data preparation for adding a TDD cell

SN Ope MO Configuration Reference
ratio
n

1 Add RU (using MML Set the Board Type parameter.

commands)/BBP ● With Board Type set to LBBP: If the
(using the MAE- TDD cell must support beamforming,
Deployment) set Work Mode to TDD_ENHANCE.
If the TDD cell must support MIMO,
set Work Mode to TDD.
● With Board Type set to UBBP: Set
Base Band Work Standard to
LTE_TDD(LTE TDD).
For details about parameter settings, see
Base Station Cabinets and Subracks
(Including the BBU Subrack)
Configuration Feature Parameter
Description.
2 Add RRUCHAIN For details about parameter settings, see
RF Unit and Topology Management
3 Add RRU Feature Parameter Description.
If RF resources are sufficient but CPRI
resources are insufficient, change the
topology of the RRU chain to load
sharing to increase the CPRI bandwidth.

4 Add RET For details about parameter settings, see

ALD Management Feature Parameter
Description.
5 Modi ANTENNAPORT/ Set ALD Power Switch to ON.
fy RETPORT

6 Add SECTOR For details, see Cell Management

Feature Parameter Description.
7 Add SECTOREQM

8 Add Cell

9 Add eUCellSectorEqm

10 Add CellOp

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 64

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario-specific template being "Adding a TDD Cell (Common
Scenarios)") and a radio data planning file. The details are as follows:
NOTE

● Use the batch reconfiguration mode of the MAE-Deployment to add BBP, RRUCHAIN,
RRU, RET, AntennaPort or RetPort, Sector, and SECTOREQM MOs.
● Use the radio data planning file to add the Cell, eUCellSectorEqm, and CellOp MOs.

a. Use the batch reconfiguration mode to add BBP, RRUCHAIN, RRU, RET,
AntennaPort or RetPort, and Sector MOs. For details, see the interactive
operation guide 1.11.2 Using the Batch Reconfiguration Mode of the
MAE-Deployment to Prepare Data.
b. Export a cell template.
i. In the Main View navigation tree in the left pane of the planned
data area, select a cell of the eNodeB. The cell is used as a reference
for the cell to be added.
ii. Right-click the cell, save it as a cell template, and record the cell
name.
c. Use the radio data planning file to add the Cell and CellOp MOs.
i. On the menu bar, choose LTE Application > Network Adjustment >
Export Radio Network Planning Data to start exporting the radio
network planning data from the system into the radio data planning
file.
ii. Fill information into the file in the same sequence listed in the data
configuration table. Fill the name of the cell mentioned in b into the
CellTemplate column in the Cell sheet. If the information about the
operator of the new cell is different from that of the reference cell
mentioned in b, fill information into the CellOp and CnOperatorTa
sheets. Otherwise, do not fill information into these sheets. After
completing the information, close the file.
iii. On the menu bar of the planned data area, choose LTE Application
> Network Adjustment > Import Radio Network Planning Data. In
the displayed Import Radio Network Planning Data dialog box,
import the data in the radio data planning file into the system.
d. Turn on the beamforming algorithm switch for the cell.
If the beamforming algorithm switch is turned off for the reference cell
mentioned in Export a cell template and must be turned on for the new
cell, use the batch reconfiguration mode of the MAE-Deployment to
modify the configuration in batches after the cell is added using the radio
data planning file. For details, see descriptions about the batch
configuration mode of the MAE-Deployment.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 65

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

Assume that a BBP, RRU chain/ring, RRU, and RET antenna are to be added. The
MML configuration scripts are as follows:
/*Exporting the current license file and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="user", PWD="*****", DIR="ftproot/", FN="
LIC_LTE_ON.dat";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN=" LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="
user", PWD="****";
/*Adding a BBP (use a UBBP as an example)*/
ADD BRD:SN=2,BT=UBBP,BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1,CCNE=OFF;
/*Adding an RRU chain*/
ADD RRUCHAIN:RCN=0,TT=CHAIN,BM=COLD,HSN=2,HPN=0;
/*Adding an RRU*/
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK,RCN=0, PS=0, RT=MRRU, RS=LO, RN="60", RXNUM=4,
TXNUM=4;
/*Adding an RET antenna*/
ADD RET: DEVICENO=0, DEVICENAME="RET1", CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
POLARTYPE=SINGLE, SCENARIO=REGULAR;
/*Turning on the ALD power supply switch*/
MOD RETPORT: CN=0, SRN=60, SN=0, PWRSWITCH=ON;
/*Adding a sector*/
ADD SECTOR:SECTORID=0,SECNAME="0",LOCATIONNAME="0",
USERLABEL="0",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,AN
T2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=60,ANT3SN=0,ANT3N=R0C,ANT4CN=0,ANT4SRN=60,ANT4SN=0,
ANT4N=R0D,CREATESECTOREQM=TRUE,SECTOREQMID=0;
/*Adding sector equipment*/
ADD SECTOREQM:SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1CN=0,
ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N
=R0B,ANTTYPE2=RXTX_MODE,ANT3CN=0,ANT3SRN=60,ANT3SN=0,ANT3N=R0C,ANTTYPE3=RXTX_MODE,A
NT4CN=0,ANT4SRN=60,ANT4SN=0,ANT4N=R0D,ANTTYPE4=RXTX_MODE;
/*Adding a cell*/
ADD CELL: LocalCellId=0, CellName="0", FreqBand=38, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=38000,
UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=0, PhyCellId=0, FddTddInd=CELL_TDD,
SubframeAssignment=SA1, SpecialSubframePatterns=SSP7, EuCellStandbyMode=ACTIVE,
RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=4T4R;
/*Adding sector equipment for the cell*/
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;
/*Adding operator information for the cell*/
ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
/*Activating the added cell*/
ACT CELL: LocalCellId=0;

1.5.3.3 Engineering Implementation

This section describes the engineering implementation for adding a TDD cell,
including prerequisites, context, and procedure.

Prerequisites
Hardware, software, license files, and data for adding a TDD cell are ready.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 66

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Insert the BBP into the subrack. For details about the operation, see
Maintaining the Case-Structured BBU > Replacing the LBBP or
Replacing the UBBP in the BBU Hardware Maintenance Guide.
b. Install an optical module. For details about the operation, see the
corresponding Replacing the Optical Module section in the BBU
Hardware Maintenance Guide. For example, for details about how to
install an optical module on a case-structured BBU, see Replacing the
Optical Module.
c. Install an RF module. For details about the operation, see the installation
guide for RRUs.
d. Install a CPRI optical fiber. For details, see Installing a CPRI Optical
Fiber in the installation guide of the corresponding RRU.
e. Install the antenna system. For details, see Antenna Installation.
● Remote Operations
– Using the MAE-Deployment:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
Example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
iv. Run the following commands to back up and export the
configuration file. The configuration file can be used to roll back the
base station configurations to the original state, if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 67

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

2) To export the configuration file, run the ULD CFGFILE command.

Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
v. (Optional) If an RRU is inserted into an existing RRU chain or ring,
block all cells served by the RRUs following this RRU on the chain or
ring.
Run the BLK CELL command with Cell admin state set to
CELL_HIGH_BLOCK.
vi. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
vii. Activate the new cell.
Run the ACT CELL command.
Example: ACT CELL: LocalCellId=0;
viii. Unblock cells.
Run the UBL CELL command.
ix. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Run the following commands to back up and export the
configuration file. The configuration file can be used to roll back the
base station configurations to the original state, if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. (Optional) If an RRU is inserted into an existing RRU chain or ring,
block all cells served by the RRUs following this RRU on the chain or
ring.
Run the BLK CELL command with Cell admin state set to
CELL_HIGH_BLOCK.
iv. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 68

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

You can import or export the license file for only one NE at a time.
v. Unblock cells.
Run the UBL CELL command.
vi. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.5.3.4 Engineering Verification

This section describes how to verify the addition of a TDD cell.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.
Step 3 Run the LST CELL command to check whether the cell information is the same as
planned.
If the cell information is not the same as planned, perform the following steps:

If... Then...

The reconfiguration is
performed on the MAE-
Deployment
Check whether the cell information in the modified data file is the
same as planned:
● If they are different, modify the configuration data file again and
import it into the system. Then perform the operations in
Engineering Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the data is
imported into the system or delivered to the base station. In this
situation, contact Huawei technical support or dial the Huawei
technical support hotline.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 69

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The reconfiguration is
performed by using MML
commands
Check whether the parameter settings in the script are correct:
● If they are incorrect, modify the parameters in the script. Run the
RMV CELL command to delete the cell. Then run the ADD CELL
command to add a cell again.
● If they are correct, contact Huawei technical support or dial the
Huawei technical support hotline.

----End

1.5.3.5 Engineering Rollback

If the reconfiguration fails, the eNodeB configuration can be rolled back to the
original state.

Procedure
Step 1 Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration Data.

NOTICE

The activation of configuration data mentioned in 1.5.3.3 Engineering

Implementation is performed step by step. If the preceding step fails, the
configuration in the next step cannot be performed. You need to roll back to the
original configuration according to Step 1.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the cable connections.

Step 4 Check whether the engineering rollback is successful by following the operations
described in 1.5.3.4 Engineering Verification.

----End

1.5.4 Adding a TDD Cell (Multi-Carrier Capacity Expansion

Scenarios)
This section describes how to add a TDD cell for multi-carrier capacity expansion.

1.5.4.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adding a TDD cell for multi-
carrier capacity expansion.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 70

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Application Scenario
● As the traffic increases, the existing cell capacity cannot meet the traffic
demand of cell edge users (CEUs). In this situation, cells must be added to
expand the capacity.
● The operator uses a new frequency band.

Reconfiguration Impact
When an RRU chain/ring is changed to a load sharing topology, a breakpoint must
be set on the chain/ring. The cells set up on the RRU chain/ring must be
deactivated before the breakpoint is set.

Reconfiguration Scheme
Determine the reconfiguration scheme for adding a TDD cell to an existing site for
multi-carrier capacity expansion according to the following table.

Table 1-22 Scheme options

If... Then...

Baseband resources are insufficient ● Add a BBP.

● Use a BBP with higher specifications
to replace the BBP in use to
increase the number of cells
supported by the BBP. For details
about how to replace a BBP, see
1.7.3 Replacing BBPs.

CPRI resources are insufficient ● Add an optical fiber for a load

sharing topology to add CPRI
resources.
● Change an optical module to
increase the CPRI bandwidth.
● Change the CPRI compression mode
to a higher compression rate for the
cells served by the RRUs on the
RRU chain/ring to support more
carriers.

Automatic neighbor relation (ANR) is Configure neighboring cell information

disabled in static mode. For details about how
to modify neighboring cell
information, see 1.5.4.4 Engineering
Verification.

Figure 1-14 shows the reconfiguration procedure for adding a TDD cell for multi-
carrier capacity expansion.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 71

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-14 Procedure for adding a TDD cell for multi-carrier capacity expansion

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 72

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Unused channels on an installed RRU can be used to set up cells for capacity expansion. For
example, if a carrier has already been set up on the R0A and R0B channels of a 4-channel RRU,
another carrier can be set up on the R0C and R0D channels, which jointly serve one sector. For
detailed operations, see 1.5.3 Adding a TDD Cell (Common Scenarios).

Topology Change
Use adding a BBP board and CPRI optical fiber as an example. Figure 1-15 shows
the topologies before and after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 73

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-15 Topologies before and after the reconfiguration

1.5.4.2 Engineering Preparation

This section describes the engineering preparation for adding a TDD cell for multi-
carrier capacity expansion, including information collection and preparation of
hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 74

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Collection
Table 1-23 describes the information to be collected for TDD multi-carrier
capacity expansion.

Table 1-23 Information to be collected

Information Description

BBP model Model of the BBP, for example, UBBP

Topology CPRI topology for RF modules, for example, the star,

chain, or inter-board load sharing topology

Cell information ● Basic information about the cells, for example, the
bandwidth, EARFCN, and duplex mode
● Cell combination mode, for example, single RRU
mode, two-RRU combination mode, cell combination,
or SFN

Sector equipment Information about sector equipment of the cells,

information of the including sector equipment ID, reference signal power,
cells and baseband equipment

NOTE

Before the reconfiguration, run the DSP TXBRANCH, DSP RXBRANCH or DSP RRU command
to query the capability of the RF module. This is to ensure that the EARFCN, bandwidth,
and power of the cell are still within the capability range of the RF module after the
reconfiguration.

Hardware Preparation
Table 1-24 describes the hardware to be prepared before adding a TDD cell for
multi-carrier capacity expansion.

Table 1-24 Hardware to be prepared

If... Then...

BBPs are insufficient ● Prepare a new BBP for the cell to be added based on
the board specifications.
● Check whether the cell to be added can be served by
the same BBP as the existing cells. If not, prepare a
new BBP. For related constraints, see 1.5.19 Binding
Baseband Equipment. For example, cells with
different subframe configurations cannot be served
by one BBP. To add a cell with a different subframe
configuration, a new BBP must be installed.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 75

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

CPRI resources are ● Prepare new CPRI cables.

insufficient, and ● Prepare new optical modules.
hardware must be
added or replaced

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required. If a cell is to be
added, apply for a cell-specific license. If a new carrier is to be added to existing
RRUs, apply for the multi-carrier license.

Security Certificate Preparation

N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Table 1-25 Data preparation for TDD multi-carrier capacity expansion

SN Ope MO Configuration Reference
ratio
n

1 Add RU (using MML Set the Board Type parameter.

commands)/BBP ● With Board Type set to LBBP: If the
(using the MAE- TDD cell must support beamforming,
Deployment) set Work Mode to TDD_ENHANCE.
If the TDD cell must support MIMO,
set Work Mode to TDD.
● With Board Type set to UBBP: Set
Base Band Work Standard to
LTE_TDD(LTE TDD).
For details about parameter settings, see
Base Station Cabinets and Subracks
(Including the BBU Subrack)
Configuration Feature Parameter
Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 76

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

2 Modi RRUCHAIN If RF resources are sufficient but CPRI

fy resources are insufficient, change the
topology of the RRU chain to load
sharing to increase the CPRI bandwidth.

3 Add Cell For details, see Cell Management

Feature Parameter Description.
4 Add eUCellSectorEqm

5 Add CellOp

6 Modi PDSCHCfg/ Change the Reference signal power

fy eUCellSectorEqm value.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario-specific template being "Adding a TDD Cell (Multi-
carrier Capacity Expansion Scenarios)") and a radio data planning file. The
details are as follows:
NOTE

● Use the batch configuration mode of the MAE-Deployment to add the BBP and
RRUCHAIN MOs.
● Use the radio data planning file to add the Cell, CellOp and CnOperatorTa MOs, and
add neighboring cell information.
● Use the batch configuration mode of the MAE-Deployment to modify the Reference
signal power parameter.

a. Use the batch reconfiguration mode to add the BBP and RRUCHAIN
MOs. For details, see the interactive operation guide 1.11.2 Using the
Batch Reconfiguration Mode of the MAE-Deployment to Prepare
Data.
b. Export a cell template.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 77

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. In the Main View navigation tree in the left pane of the planned
data area, select a cell of the eNodeB. The cell is used as a reference
for the cell to be added.
ii. Right-click the cell, save it as a cell template, and record the cell
name.
c. Use the radio data planning file to add the Cell, CellOp and
CnOperatorTa MOs, and add neighboring cell information.
i. On the menu bar, choose LTE Application > Network Adjustment >
Export Radio Network Planning Data to start exporting the radio
network planning data from the system into the radio data planning
file. If ANR is disabled, add intra-frequency, inter-frequency, and
external neighboring cell information, and export the information
about the neighboring cells to be modified.
ii. Fill information into the file in the same sequence listed in the data
configuration table. Fill the name of the cell mentioned in b into the
CellTemplate column in the Cell sheet. If the information about the
operator of the new cell is different from that of the reference cell
mentioned in b, fill information into the CellOp and CnOperatorTa
sheets. Otherwise, do not fill information into these sheets. After
completing the information, close the file.
iii. On the menu bar of the planned data area, choose LTE Application
> Network Adjustment > Import Radio Network Planning Data. In
the displayed Import Radio Network Planning Data dialog box,
import the data in the radio data planning file into the system.
d. Modify the Reference signal power parameter in batch configuration
mode.
i. On the menu bar, choose LTE Application > Network Adjustment >
Export Base Station Bulk Configuration Data. Select the eNodeB
version and the eNodeB to be modified. Select Custom MOC. For a
common cell, select PDSCHCfg. For an SFN or combined cell, select
eUCellSectorEqm.
ii. Select parameters to be modified, and export the eNodeB data to be
modified to the summary data file. Save the summary data file on
the local PC.
iii. Open the summary data file saved on the local PC, and fill the file
following the data preparation procedure. Then, save and close the
file.
iv. On the menu bar, choose LTE Application > Network Adjustment >
Import Base Station Bulk Configuration Data. Import the
reconfigured summary data file into the system to complete batch
reconfiguration of eNodeB data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 78

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

MML Configuration Script Example

Assume that a new UBBP board is required and the RRU chain/ring must be
modified. Then, the MML configuration scripts are as follows:
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="user", PWD="*****", DIR="ftproot/", FN="
LIC_LTE_ON.dat";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN=" LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="
user", PWD="****";
/*Adding a BBP (use a UBBP as an example)*/
ADD BRD:SN=2,BT=UBBP,BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1,CCNE=OFF;
/*Setting a breakpoint for the RRU chain, which is required for a load sharing topology*/
MOD RRUCHAIN:RCN=0,BRKPOS1=0;
/*Changing the topology of the RRU chain to the load sharing topology, and remove the breakpoint for the
RRU chain*/
MOD RRUCHAIN:RCN=0,TT=LOADBALANCE,HSRN=0,HSN=3,HPN=0,TSRN=0,
TSN=2,TPN=0,BRKPOS1=255,BRKPOS2=255;
/*Adding a cell*/
ADD CELL: LocalCellId=1, CellName="1", FreqBand=38, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=38000,
UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=1, PhyCellId=1, FddTddInd=CELL_TDD,
SubframeAssignment=SA1, SpecialSubframePatterns=SSP7, EuCellStandbyMode=ACTIVE,
RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=4T4R;
/*Adding sector equipment for the cell*/
ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=0;
/*Adding operator information for the cell*/
ADD CELLOP: LocalCellId=1, TrackingAreaId=0;
/*Modifying the reference signal power*/
MOD PDSCHCFG: LocalCellId=1, ReferenceSignalPwr=122;
/*Activating the added cell*/
ACT CELL: LocalCellId=1;

1.5.4.3 Engineering Implementation

This section describes the engineering implementation for adding a TDD cell for
multi-carrier capacity expansion, including prerequisites, context, and procedure.

Prerequisites
Hardware, software, license files, and data required for TDD multi-carrier capacity
expansion are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Insert the BBP into the subrack. For details about the operation, see
Maintaining the Case-Structured BBU > Replacing the LBBP or
Replacing the UBBP in the BBU Hardware Maintenance Guide.
b. Install an optical module. For details about the operation, see the
corresponding Replacing the Optical Module section in the BBU

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 79

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Hardware Maintenance Guide. For example, for details about how to

install an optical module on a case-structured BBU, see Replacing the
Optical Module.
c. Install a CPRI optical fiber. For details, see Installing a CPRI Optical
Fiber in the installation guide of the corresponding RRU.
● Remote Operations
– Using the MAE-Deployment:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
Example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
iv. (Optional) If an RRU is inserted into an existing RRU chain or ring,
block all cells served by the RRUs following this RRU on the chain or
ring.
Run the BLK CELL command with Cell admin state set to
CELL_HIGH_BLOCK.
v. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
vi. Activate the new cell.
Run the ACT CELL command.
Example: ACT CELL: LocalCellId=0;
vii. Unblock cells.
Run the UBL CELL command.
viii. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 80

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ii. Run the following commands to back up and export the

configuration file. The configuration file can be used to roll back the
base station configurations to the original state, if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Block cells.
Run the BLK CELL command with Cell admin state set to
CELL_HIGH_BLOCK.
iv. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
v. Unblock cells.
Run the UBL CELL command.
vi. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.5.4.4 Engineering Verification

This section describes how to verify the reconfiguration of adding a TDD cell for
multi-carrier capacity expansion.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 3 Run the LST CELL command to check whether the cell information is the same as
planned.

If the cell information is not the same as planned, perform the following steps:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 81

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The reconfiguration is Check whether the cell information in the modified data file is the
performed on the MAE- same as planned:
Deployment ● If they are different, modify the configuration data file again and
import it into the system. Then perform the operations in
Engineering Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the data is
imported into the system or delivered to the base station. In this
situation, contact Huawei technical support or dial the Huawei
technical support hotline.

The reconfiguration is Check whether the parameter settings in the script are correct:
performed by using MML ● If they are incorrect, modify the parameters in the script. Run the
commands RMV CELL command to delete the cell. Then run the ADD CELL
command to add a cell again.
● If they are correct, contact Huawei technical support or dial the
Huawei technical support hotline.

----End

1.5.4.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the cable connections.

Step 4 Verify that engineering rollback is successful by following the procedure described
in 1.5.4.4 Engineering Verification.

----End

1.5.5 Adding an Indoor Distributed Cell (TDD)

This section describes how to add an indoor distributed cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 82

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.5.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adding an indoor distributed
cell.

Application Scenario
There are weak-signal areas or coverage holes in some residential areas due to
building obstacles, which results in poor user experience. Additional cells are
usually set up to improve the coverage for buildings where signals are obstructed.
However, inter-cell interference occurs. In this case, indoor distributed cells are
introduced to turn originally interfering signals from different cells into multi-path
signals from one cell, increasing the signal to interference plus noise ratio (SINR)
at the cell edge, decreasing the number of handovers between cells and the
proportion of areas with low SINR values, and improving user experience at the
cell edge.

Reconfiguration Impact
The reconfiguration will deactivate the RRUs serving the original cell, and service
drops will occur for UEs served by the original cell.

Reconfiguration Scheme
Determine the reconfiguration scheme for adding an indoor distributed cell to an
existing site according to the following table.

Table 1-26 Scheme options

If... Then...

BBPs are insufficient ● Add BBPs.

● Add CPRI connections.

RRUs are insufficient 1. Add CPRI chains or rings.

2. Add RF modules.

Figure 1-16 shows the reconfiguration procedure for adding an indoor distributed
cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 83

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-16 Procedure for adding an indoor distributed cell

NOTE

● Adding a cell: Set the Mode of Multi-RRU Cell parameter to CELL_COMBINATION. If

existing cells are used for reconfiguration, remove the redundant cells.
● Adding baseband equipment: If the RRU that directly connected to the BBP has more
than 12 channels, CPRI ports converge on the backplane. You are advised to bind the
baseband equipment to prevent baseband resource fragments.
● Adding sector equipment groups: If existing cells are used for reconfiguration, remove
redundant sector equipment and bind baseband equipment.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 84

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Use adding two UBBP boards to configure two indoor distributed cells as an
example. Figure 1-17 shows the topologies before and after the reconfiguration.

Figure 1-17 Topologies before and after the reconfiguration

1.5.5.2 Engineering Preparation

This section describes the engineering preparation for adding an indoor distributed
cell, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Information Collection
Table 1-27 describes the information to be collected before adding an indoor
distributed cell.

Table 1-27 Information to be collected

Information Description

Cell information ● Basic information about the cell to be added,

including RAT, Flag of Multi-RRU Cell, and Mode of
Multi-RRU Cell
● TX/RX mode of the cell, for example, 1T1R or 2T2R

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 85

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Protocol type Type of the protocol to be modified for a base station,

for example, TDL_IR or CPRI

RF module type Type of an RF module to be added, for example, LRRU

or MRRU

Topology Topology for RF modules (if new RF modules are

added), for example, the star or chain topology

Sector equipment ● Sector equipment ID

● Reference signal power, indicating the reference
signal power of the RRU in the sector equipment

Baseband equipment Cabinet, subrack, and slot numbers of the BBP and
baseband equipment number. The indoor distributed
cell does not support inter-BBP configuration, and each
baseband equipment must be configured to the
specified BBP.

NOTE

Before the reconfiguration, run the DSP TXBRANCH, DSP RXBRANCH or DSP RRU command
to query the capability of the RF module. This is to ensure that the EARFCN, bandwidth,
and power of the cell are still within the capability range of the RF module after the
reconfiguration.

Hardware Preparation
Table 1-28 describes the hardware to be prepared.

Table 1-28 Hardware to be prepared

If... Then...

The BBPs are Prepare new BBPs.

insufficient

The RRUs are Prepare new RF modules.

insufficient

Software Preparation
N/A

License File Preparation

Prepare a new license file if the license in use cannot meet requirements.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 86

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Security Certificate Preparation

N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Table 1-29 Data preparation for adding an indoor distributed cell

SN Ope MO Configuration Reference

ratio
n

1 Add RU For details about parameter settings, see

Base Station Cabinets and Subracks
(Including the BBU Subrack)
Configuration Feature Parameter
Description.
2 Modi RRUCHAIN For details about parameter settings, see
fy RF Unit and Topology Management
Feature Parameter Description.
3 Add RRU

4 Add SECTOR For details, see Cell Management

Feature Parameter Description.
5 Add SECTOREQM

6 Add Cell Set the Mode of Multi-RRU Cell

parameter to CELL_COMBINATION.

7 Add BASEBANDEQM Configure baseband equipment on each

BBP.

8 Add eUCellSectorEqm For details, see Cell Management

Feature Parameter Description.
Bind the eUCellSectorEqm and
BASEBANDEQM MOs to the cell to be
planned based on the target
networking.

9 Activ Cell -
ate

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 87

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the batch configuration mode of the MAE-Deployment. For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

If the currently used license file does not meet the requirements, reload a license
file. If the currently used license file meets the requirements, directly add an
indoor distributed cell.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="user", PWD="*****", DIR="ftproot/", FN="
LIC_LTE_ON.dat";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN=" LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="
user", PWD="****";
/*Adding a UBBP*/
ADD BRD: SN=1, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-0&NBIOT-0&NR-1
ADD BRD: SN=2, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-0&NBIOT-0&NR-1
/*Adding RRU chains or rings*/
ADD RRUCHAIN: RCN=1, TT=CHAIN, HSN=2, HPN=0;
ADD RRUCHAIN: RCN=2, TT=CHAIN, HSN=2, HPN=1;
ADD RRUCHAIN: RCN=3, TT=CHAIN, HSN=2, HPN=2;
ADD RRUCHAIN: RCN=4, TT=CHAIN, HSN=2, HPN=3;
ADD RRUCHAIN: RCN=5, TT=CHAIN, HSN=2, HPN=4;
ADD RRUCHAIN: RCN=6, TT=CHAIN, HSN=2, HPN=5;
ADD RRUCHAIN: RCN=7, TT=CHAIN, HSN=1, HPN=0;
ADD RRUCHAIN: RCN=8, TT=CHAIN, HSN=1, HPN=1;
ADD RRUCHAIN: RCN=9, TT=CHAIN, HSN=1, HPN=2;
/*Adding RRUs*/
ADD RRU:CN=0,SRN=60,SN=0,TP=TRUNK,RCN=1,PS=0,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=61,SN=0,TP=TRUNK,RCN=2,PS=0,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=62,SN=0,TP=TRUNK,RCN=3,PS=0,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=63,SN=0,TP=TRUNK,RCN=4,PS=0,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=64,SN=0,TP=TRUNK,RCN=5,PS=0,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=65,SN=0,TP=TRUNK,RCN=6,PS=0,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=66,SN=0,TP=TRUNK,RCN=1,PS=1,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=67,SN=0,TP=TRUNK,RCN=2,PS=1,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=68,SN=0,TP=TRUNK,RCN=3,PS=1,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=69,SN=0,TP=TRUNK,RCN=4,PS=1,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=70,SN=0,TP=TRUNK,RCN=5,PS=1,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=71,SN=0,TP=TRUNK,RCN=6,PS=1,RT=MRRU, RS=TL,RXNUM=1,TXNUM=1;
ADD RRU:CN=0,SRN=72,SN=0,TP=TRUNK,RCN=7,PS=0,RT=LRRU, RS=TDL,RXNUM=2,TXNUM=2;
ADD RRU:CN=0,SRN=73,SN=0,TP=TRUNK,RCN=8,PS=0,RT=LRRU, RS=TDL,RXNUM=2,TXNUM=2;
ADD RRU:CN=0,SRN=74,SN=0,TP=TRUNK,RCN=9,PS=0,RT=LRRU, RS=TDL,RXNUM=2,TXNUM=2;
ADD RRU:CN=0,SRN=75,SN=0,TP=TRUNK,RCN=7,PS=1,RT=LRRU, RS=TDL,RXNUM=2,TXNUM=2;
ADD RRU:CN=0,SRN=76,SN=0,TP=TRUNK,RCN=8,PS=1,RT=LRRU, RS=TDL,RXNUM=2,TXNUM=2;
ADD RRU:CN=0,SRN=77,SN=0,TP=TRUNK,RCN=9,PS=1,RT=LRRU, RS=TDL,RXNUM=2,TXNUM=2;
/*Adding sectors in scenarios where RRUs are combined in pairs*/
ADD SECTOR:SECTORID=1,ANTNUM=2,ANT1CN=0,ANT1SRN=60,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=66,ANT2SN=0,ANT2N=R0A,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=2,ANTNUM=2,ANT1CN=0,ANT1SRN=61,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=67,ANT2SN=0,ANT2N=R0A,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=3,ANTNUM=2,ANT1CN=0,ANT1SRN=62,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=68,ANT2SN=0,ANT2N=R0A,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=4,ANTNUM=2,ANT1CN=0,ANT1SRN=63,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=69,ANT2SN=0,ANT2N=R0A,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=5,ANTNUM=2,ANT1CN=0,ANT1SRN=64,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=70,ANT2SN=0,ANT2N=R0A,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=6,ANTNUM=2,ANT1CN=0,ANT1SRN=65,ANT1SN=0,

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 88

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ANT1N=R0A,ANT2CN=0,ANT2SRN=71,ANT2SN=0,ANT2N=R0A,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=7,ANTNUM=2,ANT1CN=0,ANT1SRN=72,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=72,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=8,ANTNUM=2,ANT1CN=0,ANT1SRN=73,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=73,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=9,ANTNUM=2,ANT1CN=0,ANT1SRN=74,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=74,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=10,ANTNUM=2,ANT1CN=0,ANT1SRN=75,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=75,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=11,ANTNUM=2,ANT1CN=0,ANT1SRN=76,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=76,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=FALSE;
ADD SECTOR:SECTORID=12,ANTNUM=2,ANT1CN=0,ANT1SRN=77,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=77,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=FALSE;
/*Adding sector equipment*/
ADD SECTOREQM:SECTOREQMID=1, SECTORID=1, ANTNUM=2,ANT1CN=0,
ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=66,ANT2SN=0,ANT2N
=R0A,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=2, SECTORID=2, ANTNUM=2,ANT1CN=0,
ANT1SRN=61,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=67,ANT2SN=0,ANT2N
=R0A,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=3, SECTORID=3, ANTNUM=2,ANT1CN=0,
ANT1SRN=62,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=68,ANT2SN=0,ANT2N
=R0A,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=4, SECTORID=4, ANTNUM=2,ANT1CN=0,
ANT1SRN=63,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=69,ANT2SN=0,ANT2N
=R0A,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=5, SECTORID=5, ANTNUM=2,ANT1CN=0,
ANT1SRN=64,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=70,ANT2SN=0,ANT2N
=R0A,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=6, SECTORID=6, ANTNUM=2,ANT1CN=0,
ANT1SRN=65,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=71,ANT2SN=0,ANT2N
=R0A,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=7, SECTORID=7, ANTNUM=2,ANT1CN=0,
ANT1SRN=72,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=72,ANT2SN=0,ANT2N
=R0B,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=8, SECTORID=8, ANTNUM=2,ANT1CN=0,
ANT1SRN=73,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=73,ANT2SN=0,ANT2N
=R0B,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=9, SECTORID=9, ANTNUM=2,ANT1CN=0,
ANT1SRN=74,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=74,ANT2SN=0,ANT2N
=R0B,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=10,SECTORID=10,ANTNUM=2,ANT1CN=0,
ANT1SRN=75,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=75,ANT2SN=0,ANT2N
=R0B,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=11,SECTORID=11,ANTNUM=2,ANT1CN=0,
ANT1SRN=76,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=76,ANT2SN=0,ANT2N
=R0B,ANTTYPE2=RXTX_MODE;
ADD SECTOREQM:SECTOREQMID=12,SECTORID=12,ANTNUM=2,ANT1CN=0,
ANT1SRN=77,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=77,ANT2SN=0,ANT2N
=R0B,ANTTYPE2=RXTX_MODE;
/*Adding cells with the Flag of Multi-RRU Cell parameter set to BOOLEAN_TRUE and the Mode of Multi-
RRU Cell parameter set to CELL_COMBINATION*/
ADD CELL:LOCALCELLID=1,CELLNAME="1",FREQBAND=38,
ULEARFCNCFGIND=NOT_CFG,DLEARFCN=38000,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW
_N100,CELLID=1,PHYCELLID=1,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPA
TTERNS=SSP5,ROOTSEQUENCEIDX=1,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFG
IND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_TRUE,MULTIRRUCELLMO
DE=CELL_COMBINATION,TXRXMODE=2T2R;
ADD CELL:LOCALCELLID=2,CELLNAME="2",FREQBAND=38,
ULEARFCNCFGIND=NOT_CFG,DLEARFCN=38000,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW
_N100,CELLID=2,PHYCELLID=2,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPA
TTERNS=SSP5,ROOTSEQUENCEIDX=1,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFG
IND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_TRUE,MULTIRRUCELLMO
DE=CELL_COMBINATION,TXRXMODE=2T2R;
/*Adding baseband equipment*/
ADD BASEBANDEQM:BASEBANDEQMID=1,BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL,SN1=1;
ADD BASEBANDEQM:BASEBANDEQMID=2,BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL,SN1=2;
ADD BASEBANDEQM:BASEBANDEQMID=3,BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL,SN1=3;
/*Adding sector equipment for the cells*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 89

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=1, BASEBANDEQMID=2;

ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=2, BASEBANDEQMID=2;
ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=3, BASEBANDEQMID=2;
ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=4, BASEBANDEQMID=2;
ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=5, BASEBANDEQMID=2;
ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=6, BASEBANDEQMID=2;
ADD EUCELLSECTOREQM:LOCALCELLID=2,SECTOREQMID=7, BASEBANDEQMID=1;
ADD EUCELLSECTOREQM:LOCALCELLID=2,SECTOREQMID=8, BASEBANDEQMID=1;
ADD EUCELLSECTOREQM:LOCALCELLID=2,SECTOREQMID=9, BASEBANDEQMID=1;
ADD EUCELLSECTOREQM:LOCALCELLID=2,SECTOREQMID=10, BASEBANDEQMID=1;
ADD EUCELLSECTOREQM:LOCALCELLID=2,SECTOREQMID=11, BASEBANDEQMID=1;
ADD EUCELLSECTOREQM:LOCALCELLID=2,SECTOREQMID=12, BASEBANDEQMID=1;
/*Activating the cells*/
ACT CELL: LocalCellId=1;
ACT CELL: LocalCellId=2;

1.5.5.3 Engineering Implementation

This section describes the engineering implementation for adding an indoor
distributed cell, including prerequisites, context, and procedure.

Prerequisites
● Related information, license files, and data are ready.
● When an indoor distributed cell is set to a low speed cell, the LBBPd supports
a maximum of six pieces of sector equipment, with each sector equipment
supporting a maximum of two 1T1R RRUs or one 2T2R RRU. That is, the BBP
supports a maximum of 12 1T1R RRUs or six 2T2R RRUs.
● When an indoor distributed cell is not set to a low speed cell, the LBBPd
supports a maximum of three pieces of sector equipment, with each sector
equipment supporting a maximum of two 1T1R or 2T2R RRUs.
● The indoor distributed cell does not support inter-BBP cell combination.
Therefore, a cell can be connected only to one baseband equipment.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Insert the BBP into the subrack. For details, see Maintaining the Case-
Structured BBU > Adding BBU Components in BBU Hardware
Maintenance Guide.
b. Install an RF module. For details about the operation, see the installation
guide for RRUs.
c. Install a CPRI optical fiber. For details, see Installing a CPRI Optical
Fiber in the installation guide of the corresponding RRU.
● Remote Operations
– Using the MAE-Deployment:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 90

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. To prevent unnecessary alarms from being generated during

reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. If the currently used license file does not meet the requirements,
reload a license file. If the currently used license file meets the
requirements, go to 3.
1) Run the ULD LICENSE command to back up the currently used
license file.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="user", PWD="*****", DIR="ftproot/",
FN="LIC_LTE_ON.dat";
2) Run the INS LICENSE command to import a new license.
Example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="user", PWD="****";
iii. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
iv. Activate the cell. Run the ACT CELL command.
Example: ACT CELL: LocalCellId=0;
v. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Use the MAE-Access to deliver the configuration scripts prepared in
Data Preparation to the base station and activate the scripts on the
base station. For details, see 1.3.3 Running MML Commands on the
MAE-Access.
NOTE

If the currently used license file does not meet the requirements, reload a license
file. You can import or export the license file for only one NE at a time.
iii. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 91

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.5.4 Engineering Verification

This section describes how to verify the addition of an indoor distributed cell.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If the value of Cell instance state is Uninstall, check the cell configuration, cell
reference signal power configuration, or hardware based on the value of Reason
for latest state change in the command output.
Step 3 Run the LST CELL command to check whether the values of Flag of Multi-RRU
Cell, Mode of Multi-RRU Cell, and Cell transmission and reception mode are
the same as planned.
Step 4 Run the LST EUCELLSECTOREQM command to check whether the values of
Sector equipment ID and Reference signal power are the same as planned.
If the cell information is not the same as planned, perform the following steps:

If... Then...

The reconfiguration is Check whether the cell information in the modified data file is the
performed on the MAE- same as planned:
Deployment ● If they are different, modify the configuration data file again and
import it into the system. Then perform the operations in
Engineering Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the data is
imported into the system or delivered to the base station. In this
situation, contact Huawei technical support or dial the Huawei
technical support hotline.

The reconfiguration is Check whether the parameter settings in the script are correct:
performed by using MML ● If they are incorrect, modify the parameters in the script. Run the
commands RMV CELL command to delete the cell. Then run the ADD CELL
command to add a cell again.
● If they are correct, contact Huawei technical support or dial the
Huawei technical support hotline.

----End

1.5.5.5 Engineering Rollback

If the reconfiguration fails, the eNodeB configuration can be rolled back to the
original state.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 92

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration Data.
Step 2 (Optional) Import the pre-reconfiguration license file if the license is updated.
Run the INS LICENSE command.
Example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.dat", FLG=NO,
MODE=IPV4, IP="10.161.18.69", USR="user", PWD="****";
Step 3 Restore the cable connections.
Step 4 Verify that engineering rollback is successful by following the procedure described
in 1.5.5.4 Engineering Verification.

----End

1.5.6 Changing the Cell Bandwidth

This section describes how to change the cell bandwidth.

1.5.6.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the cell bandwidth.

Application Scenario
The current bandwidth is less than 20 MHz and cannot meet service requirements
due to the growing number of subscribers.

Reconfiguration Impact
After the bandwidth of a cell is changed, the cell automatically resets to make the
configuration take effect. During the reset, the cell cannot provide services.
In addition, the original reference signal transmit power may mismatch the new
bandwidth, which leads to a cell setup failure. Therefore, users need to change this
power using the PDSCHCfg MO.

Reconfiguration Scheme
Determine the reconfiguration scheme for changing the cell bandwidth according
to the following table.

Table 1-30 Scheme options

If... Then...

Capacity of the old BBPs is insufficient Add new BBPs.

The maximum bandwidth supported Replace RF modules.

by the old RF modules is low

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 93

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The type or the transmit (TX) and Modify the RF module information.
receive (RX) mode of the old RF
module and that of the new RF
module are different

The EARFCNs of the cell are beyond Modify the EARFCNs.

those supported by the new
bandwidth

NOTICE

● When a new RF module and an existing RF module are configured in hybrid

mode in an FDD network, the RF modules must comply with the hybrid
configuration principles. For details, see section Hardware > Combined-RRU/
RFU-Sector Cells in Cell Management Feature Parameter Description.
● In an LTE network, hybrid configuration refers to connecting two RF modules
operating in the same frequency band to the same BBP. The RF modules serve
one sector and provide larger capacity. For example, two 2T2R RRUs are
configured to serve a 4T4R cell.

NOTE

When the 20 MHz cell bandwidth cannot meet service requirements, another cell can be added.
For details about how to add a cell, see 1.5.1 Adding an FDD/NB-IoT Cell (Common
Scenarios) or 1.5.3 Adding a TDD Cell (Common Scenarios).

Figure 1-18 shows the reconfiguration procedure using the MAE-Deployment.

Figure 1-19 shows the reconfiguration procedure using MML commands.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 94

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-18 Changing the cell bandwidth (using the MAE-Deployment)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 95

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-19 Changing the cell bandwidth (using MML commands)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 96

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
N/A

1.5.6.2 Engineering Preparation

This section describes the engineering preparation for changing the cell
bandwidth, including information collection and preparation of hardware,
software, license files, security certificates, and data. It also describes the data
preparation mode and provides MML configuration script examples.

Information Collection
Table 1-31 describes the information to be collected for data preparation.

Table 1-31 Information to be collected

Information Description

Cell information It includes the local cell ID, as well as uplink and
downlink bandwidths of the new cell. It also
includes the BBP for the cell and its work mode
(for an LBBP) or baseband work standard (for a
UBBP).
If the EARFCNs of the cell need to be changed,
the uplink and downlink EARFCNs of the new cell
should also be obtained.

Information about the new If RF units are replaced, the following information
RF units about the new RF units should be obtained:
● Radio access technology (RAT), for example,
FDD and TDD
● RF unit type, such as the LRFU, MRFU, LRRU,
MRRU, or MPMU
● TX/RX mode, such as 2T2R or 2T4R

NOTE

Before the reconfiguration, run the DSP TXBRANCH, DSP RXBRANCH or DSP RRU command
to query the capability of the RF module. This is to ensure that the EARFCN, bandwidth,
and power of the cell are still within the capability range of the RF module after the
reconfiguration.

Hardware Preparation
Table 1-32 describes the hardware to be prepared.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 97

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-32 Information about the hardware

If... Then...

Capacity of the old BBPs is insufficient Add BBPs.

Transmission rate of the old optical Add optical modules.

modules is insufficient

The maximum bandwidth supported Add RF modules.

by the old RF modules is low

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare.
The following table lists the data to be prepared.

Table 1-33 Data preparation for changing the cell bandwidth

Rec SN Ope MO Configuration Reference

onfi rati
gura on
tion
Mod
e

MAE 1 Add BBP Set the Board Type parameter to

- LBBP or UBBP.
Depl ● If it is set to LBBP, set Work
oym Mode to the actual work mode.
ent
● If it is set to UBBP, set Base Band
Work Standard to the actual
work standard.
For details about parameter settings,
see Base Station Cabinets and
Subracks (Including the BBU
Subrack) Configuration Feature
Parameter Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 98

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO Configuration Reference

onfi rati
gura on
tion
Mod
e

2 Mod RRUCHAIN Move the RRU chain or ring to the

ify new BBP.

3 Mod RRU/RFU Set RRU type, Number of RX

ify channels, and Number of TX
channels to target values.

4 Mod Cell ● Change the values of Frequency

ify band, Uplink EARFCN, and
Downlink EARFCN to target
values. Configuration of the
uplink EARFCN is optional.
● Change the values of Uplink
bandwidth and Downlink
bandwidth to target values.

MM 1 Dea Cell -
L ctiva
com te
man
ds 2 Add RU Set the Board Type parameter to
LBBP or UBBP.
● If it is set to LBBP, set Work
Mode to the actual work mode.
● If it is set to UBBP, set Base Band
Work Standard to the actual
work standard.
For details about parameter settings,
see Base Station Cabinets and
Subracks (Including the BBU
Subrack) Configuration Feature
Parameter Description.
3 Mod RRUCHAIN Set breakpoints on the chain or ring
ify as follows:
● For a chain topology, only one
breakpoint is required and its
position is 0.
● For a ring topology, two
breakpoints should be set. The
first breakpoint position is 0 and
the second is the RRU level
number.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 99

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO Configuration Reference

onfi rati
gura on
tion
Mod
e

4 Mod RRUCHAIN Move the RRU chain or ring to the

ify new BBP.

5 Mod RRUCHAIN Change the values of BreakPoint

ify Position1 and BreakPoint Position2
to 255 to disable the breakpoints on
the RRU chain or ring.

6 Mod RRU/RFU Change the value of the RRU type.

ify ● Change the parameter value to
any other RRU type for RRUs.
● Change the parameter value to
any other RFU type for RFUs.
For details about parameter settings,
see RF Unit and Topology
Management Feature Parameter
Description.
7 Mod Cell ● Change the values of Frequency
ify band, Uplink EARFCN, and
Downlink EARFCN to target
values. Configuration of the
uplink EARFCN is optional.
● Change the values of Uplink
bandwidth and Downlink
bandwidth to target values.

8 Acti Cell -
vate

Data Preparation Mode

NOTE

Changing cell EARFCNs involves the synchronization of external cell information. To update
the information about external cells at the same time when the cell EARFCNS are changed,
you are advised to use the MAE-Deployment-provided "radio data planning file". For details
about how to change cell EARFCNs, see 1.5.9 Changing the EARFCNs of a Cell.

Data preparation can be performed using the MAE-Deployment or MML

commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 100

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Changing the Cell Bandwidth"). For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following MML configuration script example, the LRRU is used.
NOTE

● Since a radio planning data file is recommended for modifying cell EARFCNs, this MML
configuration example script does not contain steps for changing cell EARFCNs. For details
about how to change cell EARFCNs, see 1.5.9 Changing the EARFCNs of a Cell.
● If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Deactivating the cell*/
DEA CELL: LocalCellId=0;
/*In FDD: Adding a BBP in slot 3 */
ADD BRD: SN=3, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-1&LTE_TDD-0;
/*In TDD: Adding a BBP in slot 3 */
ADD BRD: SN=3, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1;
/*Setting a breakpoint on the RRU chain or ring*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0;
/*Changing the position of the RRU chain or ring head to optical port 0 in slot 3*/
MOD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=3, HPN=0;
/*Disabling the breakpoint on the RRU chain or ring*/
MOD RRUCHAIN: RCN=0, BRKPOS1=255;
/*Changing the RRU type*/
MOD RRU: CN=0, SRN=60, SN=0, RT=LRRU;
/*Changing both the uplink and downlink bandwidths of the cell to 20 MHz (CELL_BW_N100)*/
MOD CELL: LocalCellId=0, UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100;
/*Activating the cell*/
ACT CELL: LocalCellId=0;

1.5.6.3 Engineering Implementation

This section describes the engineering implementation for changing the
bandwidth of a cell, including prerequisites, context, and procedure.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 101

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Prerequisites
The information, hardware, and data required for changing the cell bandwidth are
ready. The license file has been placed in the specified path of the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Insert a new BBP into the corresponding slot. Connect the RF unit for
which the cell bandwidth needs to be changed to the new BBP.
b. Install an optical module. For details about the operation, see the
corresponding Replacing the Optical Module section in the BBU
Hardware Maintenance Guide. For example, for details about how to
install an optical module on a case-structured BBU, see Replacing the
Optical Module.
c. Install an RF module.

▪ If an RRU is to be added, install the RRU according to the

instructions in the corresponding installation guide.

▪ If an RFU is to be added, install the RFU according to the instructions

in section Replacing an RFU in 3900 & 5900 Series Base Station
Maintenance Guide.
● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.
The BBP needs to be reset after bandwidth modification in the following scenarios:
● The cell is deployed on the LBBPd3 whose Work Mode is set to FDD_NBIOT.
● The cell is deployed on the UBBPd5 or UBBPd6 whose Base Band Work Standard
supports both LTE_FDD and NBIOT.

i. To prevent unnecessary alarms from being generated during

reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 102

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",

USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
v. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.5.6.4 Engineering Verification

This section describes how to verify the change of the cell bandwidth.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 103

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

If any of these alarms is reported and the cause is "CPRI bandwidth allocation
failure due to CPRI fragment", run the commands BLK CPRIPORT and UBL
CPRIPORT to block and unblock the BBP optical port in the RRU chain or ring for
this cell.

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 3 Run the LST CELL command to check whether the uplink and downlink cell
bandwidths are the same as planned.

If the uplink and downlink cell bandwidths are not the same as planned, check
whether the parameter settings in the script are correct.

● If they are incorrect, modify the parameters. Then run the MOD CELL
command to change the uplink and downlink cell bandwidths again.
● If they are correct, contact Huawei technical support or dial the Huawei
technical support hotline.

----End

1.5.6.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Replace the RF unit with the original one before the reconfiguration.

Step 2 Restore the cable connections.

Step 3 Restore the configuration data.

● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 104

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ii. Run the ACT CFGFILE command to activate the original

configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 4 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 5 Verify that engineering rollback is successful according to instructions in 1.5.6.4

Engineering Verification.

----End

1.5.7 Changing the TX/RX Mode of a Cell

This section describes how to change the TX/RX mode of a cell.

1.5.7.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the TX/RX mode of a
cell.

Application Scenario
● Cell capacity does not meet service requirements.
● Weak-coverage areas or coverage holes exist in the cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 105

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Impact
After changing the TX/RX mode of a cell, you must reset the cell to make the
configuration take effect. During the reset, the cell cannot provide services.

Reconfiguration Scheme
Determine the reconfiguration scheme for changing the TX/RX mode of a cell
according to the following table.

Table 1-34 Scheme options

If... Then...

RF resources are insufficient ● Add RF modules and ALDs on the

existing RRU chain or ring.
● Add an RRU chain or ring, and then
add RF modules and ALDs.

An RET antenna has been configured Modify the RET antenna configuration.

An RRU has been added, and the Replace the antenna connected to the
number of antenna channels is less RRU. The number of antenna channels
than that of the RRU channels must be greater than that of RRU
channels.

A TMA has been configureda Change the TMA configuration

a: For TDD, TMA is not required.

NOTICE

● When a new RF module and an existing RF module are configured in hybrid

mode in an FDD network, the RF modules must comply with the hybrid
configuration principles. For details, see section Hardware > Combined-RRU/
RFU-Sector Cells in Cell Management Feature Parameter Description.
● In an LTE network, hybrid configuration refers to connecting two RF modules
operating in the same frequency band to the same BBP. The RF modules serve
one sector and provide larger capacity. For example, two 2T2R RRUs are
configured to serve a 4T4R cell.

Figure 1-20 shows the reconfiguration procedure for changing the TX/RX mode of
a cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 106

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-20 Changing the TX/RX mode of a cell

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 107

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Use adding a 2T2R RF module and combining it with another 2T2R RF module to
serve a 4T4R cell as an example. Figure 1-21 shows the topologies before and
after the reconfiguration.

Figure 1-21 Topologies before and after the reconfiguration

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 108

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.7.2 Engineering Preparation

This section describes the engineering preparation for changing the TX/RX mode
of a cell, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Information Collection
Table 1-35 describes the information to be collected for data preparation.

Table 1-35 Information to be collected

Information Description

Base station model Model of the base station for which the TX/RX mode of
a cell is to be changed, for example, DBS3900

RF module type Type of the RF module to be added, for example, LRRU,

MRRU, MPMU, LRFU, or MRFU

Topology formed by If RF modules are to be added, the following

RF modules information needs to be collected:
● The CPRI topology for RF modules, for example, the
chain topology
● The position of a new RRU in the CPRI topology, for
example, the chain tail

Antenna equipment ● Whether RET antennas and TMAs have been

configured
● Number of channels provided by the antenna

Sector information ● Number of antennas in the sector

● TX/RX mode of the sector

Cell information TX/RX mode of a cell, for example, 4T4R

Hardware Preparation
Table 1-36 describes the hardware to be prepared.

Table 1-36 Hardware to be prepared

If… Then...

RF resources are RF modules, CPRI cables, and optical modules are

insufficient required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 109

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation
If the RET antenna or TMA to be added needs to be upgraded, acquire the latest
software and data from the vendors.

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Table 1-37 Data preparation for changing the TX/RX mode of a cell (FDD/TDD
cell)
SN Ope MO Configuration Reference
ratio
n

1 Add RRUCHAIN For details about parameter settings, see

RF Unit and Topology Management
2 Add RRU/RFU Feature Parameter Description.
3 Modi RET Set RET Type to MULTI_RET and set
fy Number of RET Subunits to the actual
number of RET subunits.

4 Modi TMA Set Number of TMA Subunits to the

fy actual number of TMA subunits.

5 Modi SECTOR Set Antenna Number to the number of

fy antennas added to or deleted from a
sector. For example, if a sector is
configured with two antennas before
the modification and four antennas
after the modification, set Operational
Mode to ADD, and set Antenna
Number to 2.

6 Deac Cell -
tivat
e

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 110

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

7 Modi SECTOREQM Set Antenna Number to the number of

fy antennas added to or deleted from a
sector and set the TX/RX mode of each
antenna. For example, if a sector is
configured with two antennas before
the modification and four antennas
after the modification, set Operational
Mode to ADD, and set Antenna
Number to 2.

8 Modi Cell Set Cell transmission and reception

fy mode and CRS Port Number to the
target values. For details about how to
set the CRS Port Number parameter,
see MIMO Feature Parameter
Description in eRAN Feature
Documentation.
9 Activ Cell -
ate

Table 1-38 Data preparation for changing the TX/RX mode of a cell (NB-IoT cell)
SN Ope MO Configuration Reference
ratio
n

1 Add RRUCHAIN For details about parameter settings, see

RF Unit and Topology Management
2 Add RRU/RFU Feature Parameter Description.
3 Modi RET Set RET Type to MULTI_RET and set
fy Number of RET Subunits to the actual
number of RET subunits.

4 Modi TMA Set Number of TMA Subunits to the

fy actual number of TMA subunits.

5 Deac Cell -
tivat
e

6 Dele SECTOR -
te

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 111

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

7 Modi ● If the NB-IoT cell is Set Cell transmission and reception

fy a STAND_ALONE mode and CRS Port Number to the
cell or a GUARD- target values.
BAND cell, modify
the Cell MO
directly.
● If the NB-IoT cell is
an IN-BAND cell,
modify the Cell
MO of the
associated LTE FDD
cell.

8 Add SECTOR and -

SECTOREQM

9 Activ Cell -
ate

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

● If you use the MAE-Deployment for the reconfiguration, perform 1 through 6 to prepare
data 1 and 7 through 9 to prepare data 2. Deliver both data 1 and data 2 in sequence to an
eNodeB during engineering implementation.
● Before using the MAE-Deployment to prepare data, ensure that data in the planned data
area is consistent with that in the current data area. If the data is inconsistent, you can
choose Area Management > Planned Area > Synchronize Planned Area NEs from the
menu bar to synchronize data from the current data area to the planned data area. Then,
perform the following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Changing the TX/RX Mode of a Cell"). For
details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 112

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

MML Configuration Script Example

NOTE

If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

In the following example, you need to add an RRU and RRU chain/ring, change
the configurations of the RET antenna and TMA, and change the TX/RX mode of a
TDD/FDD cell to 4T4R.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding an RRU chain*/
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=0, HPN=0;
/*Adding an RRU*/
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=LRRU, RS=LO, RN="60", RXNUM=2,
TXNUM=2;
/*Changing the configuration of an RET antenna*/
MOD RET: DEVICENO=0, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=MULTI_RET, SUBUNITNUM=2,
POLARTYPE=SINGLE, SCENARIO=REGULAR;
/*Changing the configuration of the TMA for FDD*/
MOD TMA: DEVICENO=1, CTRLCN=0, CTRLSRN=60, CTRLSN=0, SUBUNITNUM=2;
/*Adding two antennas to the sector*/
MOD SECTOR: sectorId=0, opMode=ADD, antNum=2, ant1Cn=0, ant1Srn=60, ant1Sn=0, ant1N=R0A,
ant2Cn=0, ant2Srn=60, ant2Sn=0, ant2N=R0B;
/*Deactivating the cell*/
DEA CELL: LocalCellId=0;
/*Adding two antennas to sector equipment*/
MOD SECTOREQM: sectorEqmId=0, opMode=ADD, antNum=2, ant1Cn=0, ant1Srn=60, ant1Sn=0,
ant1N=R0A, antType1=RXTX_MODE, ant2Cn=0, ant2Srn=60, ant2Sn=0, ant2N=R0B, antType2=RXTX_MODE;
/*Changing the TX/RX mode of the cell to 4T4R*/
MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_4, TxRxMode=4T4R;
/*Activating the cell*/
ACT CELL: LocalCellId=0;

In the following example, you need to change the configurations of the RET
antenna and TMA and change the TX/RX mode of an NB-IoT cell to 2T2R.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Changing the configuration of an RET antenna*/
MOD RET: DEVICENO=0, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=MULTI_RET, SUBUNITNUM=2,
POLARTYPE=SINGLE, SCENARIO=REGULAR;
/*Changing the configuration of a TMA*/
MOD TMA: DEVICENO=1, CTRLCN=0, CTRLSRN=60, CTRLSN=0, SUBUNITNUM=2;
/*Deactivating the cell*/
/*If the cell is in IN_BAND deployment mode, you also need to deactivate the corresponding FDD cell (DEA
CELL: LocalCellId=0); otherwise, you only need to deactivate the NB-IoT cell.*/
DEA CELL: LocalCellId=1;
/*Removing the sector and sector equipment from the cell*/
RMV SECTOREQM: SECTOREQMID=1;
RMV SECTOR: SECTORID=1;
/*Adding a sector and a set of sector equipment to the cell*/
ADD SECTOR: SECTORID=1, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0,
ANT2SRN=60, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=1;
/*Changing the TX/RX mode of the cell to 2T2R*/
/*If the cell is in IN_BAND deployment mode, you also need to change the TX/RX mode of the
corresponding FDD cell (MOD CELL: LocalCellId=0, NbCellFlag=FALSE, TxRxMode=2T2R); otherwise, you
only need to change the TX/RX mode of the NB-IoT cell.*/
MOD CELL: LocalCellId=1, NbCellFlag=TRUE, TxRxMode=2T2R;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 113

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Activating the cell*/

ACT CELL: LocalCellId=1;

1.5.7.3 Engineering Implementation

This section describes the engineering implementation for changing the TX/RX
mode of a cell, including prerequisites, context, and procedure.

Prerequisites
The information, hardware, software, and data required for changing the TX/RX
mode of a cell are ready. The license file has been placed in the specified path of
the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Install an RF module.

▪ If an RRU is to be added, install the RRU according to the

instructions in the corresponding installation guide.

▪ If an RFU is to be added, install the RFU according to the instructions

in section Replacing an RFU in 3900 & 5900 Series Base Station
Maintenance Guide.
b. Install an optical module. For details about the operation, see the
corresponding Replacing the Optical Module section in the BBU
Hardware Maintenance Guide. For example, for details about how to
install an optical module on a case-structured BBU, see Replacing the
Optical Module.
c. (Optional) Replace antennas if the original antennas have less TX and RX
channels than those required by the modified cells. For details about how
to install antennas, see Antenna Installation.
● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 114

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ii. Back up the license file in use to the MAE server.

Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
Example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
iv. Deliver data 1 to the eNodeB and activate the data. For details, see
the interactive operation guide Delivering Data to Base Stations
and Activating the Data.
v. Deliver data 2 to the eNodeB and activate the data. For details, see
the interactive operation guide Delivering Data to Base Stations
and Activating the Data.
vi. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Run the following commands to back up and export the
configuration file. The configuration file can be used to roll back the
base station configurations to the original state, if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 115

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.7.4 Engineering Verification

This section describes how to verify the change of the TX/RX mode of a cell.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 3 Run the LST SECTOR and LST SECTOREQM commands to verify that the sector
antenna configuration is the same as planned. Then, run the LST CELL command
to verify that the Cell transmission and reception mode value is the same as
planned.

If the sector antenna configuration or the Cell transmission and reception mode
value is not the same as planned, perform the following operations:

If... Then...

The reconfiguration is Check whether the number of antennas and the TX/RX mode of cells
performed on the MAE- in the modified configuration data file are the same as planned:
Deployment ● If they are different, modify the configuration data file again and
import it into the system. Then perform the operations in
Engineering Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the data is
imported into the system or delivered to the base station. In this
situation, contact Huawei technical support or dial the Huawei
technical support hotline.

The reconfiguration is Check whether the number of antennas and the TX/RX mode of cells
performed by using MML in the script are correct:
commands ● If they are incorrect, modify the number of antennas, the TX/RX
mode of cells, and CRS port number in the script. Then, run the
MOD SECTOR, MOD SECTOREQM, and MOD CELL command to
change the Antenna Number, Cell transmission and reception
mode, and CRS Port Number again.
● If they are correct, contact Huawei technical support or dial the
Huawei technical support hotline.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 116

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.7.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the cable connections.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 117

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 4 Verify that engineering rollback is successful according to instructions in 1.5.7.4

Engineering Verification.

----End

1.5.8 Changing the Coverage Radius of a Cell

This section describes how to change the coverage radius of a cell.

1.5.8.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the coverage radius of
a cell.

Application Scenario
● The network topology is changed.
● Overshoot coverage occurs.
NOTE

The coverage radius of an NB-IoT cell cannot be changed.

Reconfiguration Impact
After the coverage radius of a cell is changed, the cell automatically resets for the
configuration to take effect. During the reset, the cell cannot provide services.

NOTE

● Increasing the radius of a cell will extend its coverage but may cause interference on
neighboring eNodeBs. In this case, network optimization is required.
● Decreasing the radius of a cell may change its neighbor relationships and affect UE
handovers. In this case, network optimization is required.

Reconfiguration Scheme
To change the coverage radius of a cell, you only need to change the value of Cell
radius in the corresponding Cell MO to the target value.
NOTE

In TDD scenarios, if more than three physical cells are established on a UBBPd8 or more than six
physical cells are established on a UBBPd9, set Cell radius to a value less than or equal to 9896
m.

Topology Change
N/A

1.5.8.2 Engineering Preparation

This section describes the engineering preparation for changing the coverage
radius of a cell, including information collection and preparation of hardware,

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 118

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

software, license files, security certificates, and data. It also describes the data
preparation mode and provides MML configuration script examples.

Information Collection
Table 1-39 describes the information to be collected for data preparation.

Table 1-39 Information to be collected

Information Description

Cell information The cell information contains the local cell ID and the
new radius of the cell.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-40 Data preparation for changing the coverage radius of a cell

SN Oper MO Configuration Reference

ation

1 Modi Cell Set Cell radius to the target

fy value.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 119

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Changing the Coverage Radius of a Cell"). For
details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The MML command configuration script is as follows:
/*Changing the coverage radius to 50,000 m*/
MOD CELL: LocalCellId=0, CellRadius=50000;

1.5.8.3 Engineering Implementation

This section describes the engineering implementation for changing the coverage
radius of a cell, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
– Using the MAE-Deployment:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 120

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ii. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
iii. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Run the following commands to back up and export the
configuration file. The configuration file can be used to roll back the
base station configurations to the original state, if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.5.8.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the coverage
radius of a cell.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 121

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 3 Run the LST CELL command to check whether the coverage radius of the cell is
the same as planned.
If the cell radius is not the same as planned, check whether the parameter settings
in the script are correct.
● If they are incorrect, modify the parameter settings. Then run the MOD CELL
command to change the cell radius again.
● If they are correct, contact Huawei technical support or dial the Huawei
technical support hotline.

----End

1.5.8.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 122

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.5.8.4

Engineering Verification.

----End

1.5.9 Changing the EARFCNs of a Cell

This section describes how to change the E-UTRA absolute radio frequency
channel numbers (EARFCNs) of a cell.

1.5.9.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the EARFCNs of a cell.

Application Scenario
● The current EARFCNs of the cell are inappropriate.
● The operator needs to re-plan frequency resources.

Reconfiguration Impact
After the EARFCNs of a cell are changed, the cell automatically resets to make the
configuration take effect. During the reset, the cell cannot provide services.

Reconfiguration Scheme
Figure 1-22 shows the reconfiguration procedure for changing the EARFCNs of a
cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 123

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-22 Changing the EARFCNs of a cell

Neighboring cells are reconfigured by deleting redundant or incorrect neighboring

cells and adding new neighboring cells based on the network plan.

Topology Change
N/A

1.5.9.2 Engineering Preparation

This section describes the engineering preparation for changing the EARFCNs of a
cell, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode.

Information Collection
Table 1-41 describes the information to be collected for data preparation.

Table 1-41 Information to be collected

Information Description

Cell information It includes the local cell ID and the new uplink and
downlink EARFCNs.

Neighboring cell It includes information about intra-frequency and inter-

information frequency neighboring cells. After the cell EARFCNs are
changed, delete incorrect neighbor relationships and
add new neighbor relationships based on the network
plan.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 124

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before the reconfiguration, run the DSP TXBRANCH, DSP RXBRANCH or DSP RRU command
to query the capability of the RF module. This is to ensure that the EARFCN, bandwidth,
and power of the cell are still within the capability range of the RF module after the
reconfiguration.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-42 Data preparation for changing EARFCNs

SN Ope MO Configuration Reference

ratio
n

1 Modi ● FDD/TDD: Cell Change the values of Uplink EARFCN

fy ● NB-IoT: PRB and Downlink EARFCN to target values.
Configuration of the uplink EARFCN is
optional.

2 Modi EutranIntraFreqNCell ● When the MAE-Deployment is used

fy for reconfiguration, cell EARFCNs-
related parameters will be
3 Modi EutranInterFreqNCell automatically changed to the target
fy values. No operation is required.
4 Modi EutranInterNFreq ● When MML commands are used for
fy reconfiguration, manually configure
related parameters.
5 Modi EutranExternalCell
fy

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 125

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

To update the information about external cells at the same time when the cell
EARFCNS are changed, you are advised to use the MAE-Deployment-provided
"radio data planning file".

NOTE

● The MAE-Deployment-provided "radio data planning file" supports automatic update of the
information about external cells when cell-related parameters are modified.
● To ensure that the associated parameters of the external cells in the current data area are
automatically synchronized, choose Advanced > System > Options on the menu bar of the
main window. The setting function is started. On the Cell Parameter Auto-Synchronization
Policy tab page, select Auto synchronize cell parameters in the entire network and click
OK. For details about the parameter auto-synchronization policy, see section Setting System
Options in the MAE-Access online help.
● Before using the MAE-Deployment to prepare data, ensure that data in the planned data
area is consistent with that in the current data area. If the data is inconsistent, you can
choose Area Management > Planned Area > Synchronize Planned Area NEs from the
menu bar to synchronize data from the current data area to the planned data area. Then,
perform the following operations.

The data preparation using the MAE-Deployment-provided "radio data planning

file" is as follows:

1. On the menu bar, choose LTE Application > Network Adjustment > Export
Radio Network Planning Data to start exporting the radio network planning
data from the system into the radio data planning file.
2. Edit data in the file based on the prepared data. Then, close the file.
3. On the menu bar of the planned data area, choose LTE Application >
Network Adjustment > Import Radio Network Planning Data. A dialog box
is displayed for you to import planned radio data. Import the data from the
file into the system.
For detailed import and export operations, see section Importing and
Exporting Planned Radio Data in the MAE-Access online help.

1.5.9.3 Engineering Implementation

This section describes the engineering implementation for changing the EARFCNs
of a cell, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 126

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
● Local Operations
N/A
● Remote Operations
To update the information about external cells at the same time when the cell
EARFCNS are changed, you are advised to use the MAE-Deployment-provided
"radio data planning file". Perform the following steps:
a. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Run the LST GLOBALPROCSWITCH command to query the values of the
following parameters: The Switch of X2 setup by SON, Peer Request
Based X2 Delete Switch, X2 SON Delete Switch, Interface Setup Policy
Switch, The Timer of X2 delete by SON, and X2-based Neighboring
Cell Configuration Update Switch.

▪ Skip this step if the The Timer of X2 delete by SON parameter is 0,

the LTE_NR_X2_SON_SETUP_SW option of the Interface Setup
Policy Switch parameter is deselected, and the options of all the
other preceding parameters are deselected.

▪ If The Timer of X2 delete by SON parameter is not 0, the

LTE_NR_X2_SON_SETUP_SW option of the Interface Setup Policy
Switch parameter is selected, or the options of all the other
preceding parameters are selected, run the MOD
GLOBALPROCSWITCH command to set the The Timer of X2 delete
by SON parameter to 0 and deselect all these options. Example:
MOD GLOBALPROCSWITCH: X2SonSetupSwitch=OFF,
X2SonDeleteTimer=0, PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2USAGE
_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-0,
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_NCELL
_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD_FREQ_CFG_SW-0&UPT_
EXTERNALCELLBAND_CFG_SW-0,
InterfaceSetupPolicySw=X2_SON_INTER_OP_SETUP_FBD_SW-1&LT
E_NR_X2_SON_SETUP_SW-0;
c. Run the LST ENODEBALGOSWITCH command to check whether the
options of ANR algorithm switch are selected.

▪ If all the options of this parameter are deselected, skip this step.

▪ If any option is selected, run the MOD ENODEBALGOSWITCH

command with all options of the ANR algorithm switch parameter
deselected. Example: MOD ENODEBALGOSWITCH:
AnrSwitch=IntraRatEventAnrSwitch-0&IntraRatFastAnrSwitch-0&I
ntraRatAnrAutoDelSwitch-0&UtranEventAnrSwitch-0&GeranEven
tAnrSwitch-0&UtranFastAnrSwitch-0&GeranFastAnrSwitch-0&Cd
maFastAnrSwitch-0&UtranAutoNrtDeleteSwitch-0&GeranAutoNr
tDeleteSwitch-0&CdmaAutoNrtDeleteSwitch-0&CdmaEventAnrS
witch-0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 127

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

d. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
e. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
f. Restore the settings of the options changed in b and c.

----End

1.5.9.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the EARFCNs
of a cell.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 3 Run the LST CELL command to check whether the cell uplink EARFCN and
downlink EARFCN are the same as planned.

If the uplink or downlink EARFCN of the cell is not the same as planned, check
whether the uplink or downlink EARFCN in the modified configuration data file is
the same as planned.

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.5.9.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 128

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Roll back the configuration data.
● Using the MAE-Deployment: For detailed operations, see the interactive
operation guide Rolling Back Configuration Data.
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.5.9.4

Engineering Verification.

----End

1.5.10 Changing the PCI of a Cell

This section describes how to change the physical cell identifier (PCI) of a cell.

1.5.10.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the PCI of a cell.

Application Scenario
● The physical network topology is changed.
● A PCI conflict occurs between cells.

Reconfiguration Impact
After the PCI of a cell is changed, the cell automatically resets to make the
configuration take effect. During the reset, the cell cannot provide services.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 129

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme
To change the PCI, you only need to change the value of Physical cell ID in the
Cell MO to the target value.

NOTE

● You are advised to use the MAE-Deployment-provided "radio data planning file" to perform
the reconfiguration. In this mode, after you reconfigure the PCI of a cell, the external
neighboring cell information of this cell will be automatically updated on the neighboring
eNodeBs.
● If a cell deployed in in-band mode is to be modified, you must deactivate both the
corresponding FDD cell and NB-IoT cell, and then change their PCIs and activate them again.

Topology Change
N/A

1.5.10.2 Engineering Preparation

This section describes the engineering preparation for changing the PCI of a cell,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode.

Information Collection
Table 1-43 describes the information to be collected for data preparation.

Table 1-43 Information to be collected

Information Description

Cell information The cell information contains the local cell ID and the
new PCI.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 130

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation
The following table lists the data to be prepared.

Table 1-44 Data preparation for changing the PCI of a cell

SN Ope MO Configuration Reference

ratio
n

1 Modi Cell Change Physical cell ID to the target

fy value.

2 Modi EutranExternalCell ● When the MAE-Deployment is used

fy for reconfiguration, PCI-related
parameters will be automatically
changed to the target values. No
operation is required.
● When MML commands are used for
reconfiguration, manually configure
related parameters.

Data Preparation Mode

To update the information about external cells at the same time when the PCI of
the cell is changed, you are advised to use the MAE-Deployment-provided "radio
data planning file".

NOTE

● The MAE-Deployment-provided "radio data planning file" supports automatic update of the
information about external cells when cell-related parameters are modified.
● To ensure that the associated parameters of the external cells in the current data area are
automatically synchronized, choose Advanced > System > Options on the menu bar of the
main window. The setting function is started. On the Cell Parameter Auto-Synchronization
Policy tab page, select Auto synchronize cell parameters in the entire network and click
OK. For details about the parameter auto-synchronization policy, see section Setting System
Options in the MAE-Access online help.
● Before using the MAE-Deployment to prepare data, ensure that data in the planned data
area is consistent with that in the current data area. If the data is inconsistent, you can
choose Area Management > Planned Area > Synchronize Planned Area NEs from the
menu bar to synchronize data from the current data area to the planned data area. Then,
perform the following operations.

The data preparation using the MAE-Deployment-provided "radio data planning

file" is as follows:
1. On the menu bar, choose LTE Application > Network Adjustment > Export
Radio Network Planning Data to start exporting the radio network planning
data from the system into the radio data planning file.
2. Edit data in the file based on the prepared data. Then, close the file.
3. On the menu bar of the planned data area, choose LTE Application >
Network Adjustment > Import Radio Network Planning Data. A dialog box

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 131

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

is displayed for you to import planned radio data. Import the data from the
file into the system.
For detailed import and export operations, see section Importing and
Exporting Planned Radio Data in the MAE-Access online help.

1.5.10.3 Engineering Implementation

This section describes the engineering implementation for changing the PCI of a
cell, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
To update the information about external cells at the same time when the PCI
of the cell is changed, you are advised to use the MAE-Deployment-provided
"radio data planning file". Perform the following steps:
a. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Run the LST GLOBALPROCSWITCH command to query the values of the
following parameters: The Switch of X2 setup by SON, Peer Request
Based X2 Delete Switch, X2 SON Delete Switch, Interface Setup Policy
Switch, The Timer of X2 delete by SON, and X2-based Neighboring
Cell Configuration Update Switch.

▪ Skip this step if the The Timer of X2 delete by SON parameter is 0,

the LTE_NR_X2_SON_SETUP_SW option of the Interface Setup
Policy Switch parameter is deselected, and the options of all the
other preceding parameters are deselected.

▪ If The Timer of X2 delete by SON parameter is not 0, the

LTE_NR_X2_SON_SETUP_SW option of the Interface Setup Policy
Switch parameter is selected, or the options of all the other
preceding parameters are selected, run the MOD
GLOBALPROCSWITCH command to set the The Timer of X2 delete
by SON parameter to 0 and deselect all these options. Example:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 132

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

MOD GLOBALPROCSWITCH: X2SonSetupSwitch=OFF,

X2SonDeleteTimer=0, PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2USAGE
_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-0,
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_NCELL
_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD_FREQ_CFG_SW-0&UPT_
EXTERNALCELLBAND_CFG_SW-0,
InterfaceSetupPolicySw=X2_SON_INTER_OP_SETUP_FBD_SW-1&LT
E_NR_X2_SON_SETUP_SW-0;
c. Run the LST ENODEBALGOSWITCH command to check whether the
options of ANR algorithm switch are selected.

▪ If all the options of this parameter are deselected, skip this step.

▪ If any option is selected, run the MOD ENODEBALGOSWITCH

command with all options of the ANR algorithm switch parameter
deselected. Example: MOD ENODEBALGOSWITCH:
AnrSwitch=IntraRatEventAnrSwitch-0&IntraRatFastAnrSwitch-0&I
ntraRatAnrAutoDelSwitch-0&UtranEventAnrSwitch-0&GeranEven
tAnrSwitch-0&UtranFastAnrSwitch-0&GeranFastAnrSwitch-0&Cd
maFastAnrSwitch-0&UtranAutoNrtDeleteSwitch-0&GeranAutoNr
tDeleteSwitch-0&CdmaAutoNrtDeleteSwitch-0&CdmaEventAnrS
witch-0;
d. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
e. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
f. Restore the settings of the options changed in b and c.

----End

1.5.10.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the PCI of a
cell.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 133

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 3 Run the LST CELL command to check whether the value of Physical cell ID is the
same as planned.

If the Physical Cell ID is not the same as planned, check whether the Physical
Cell ID in the modified configuration data file is the same as planned:

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.5.10.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Roll back the configuration data.
● Using the MAE-Deployment: For detailed operations, see the interactive
operation guide Rolling Back Configuration Data.
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 134

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 2 Verify that engineering rollback is successful according to instructions in 1.5.10.4

Engineering Verification.

----End

1.5.11 Changing the Cell ID

This section describes how to change the ID of a cell.

1.5.11.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the cell ID.

Application Scenario
The previous cell ID plan is inappropriate, and a new plan is required.

Reconfiguration Impact
After the ID of a cell is changed, the cell automatically resets to make the
configuration take effect. During the reset, the cell cannot provide services.

Reconfiguration Scheme
NOTE

If the current cell serves as a neighboring cell of another intra-site cell, the value of Cell ID
cannot be modified.
● MAE-Deployment-based reconfiguration scheme
To change the cell ID, you only need to change Cell ID in the Cell MO to the
target value.
NOTE

You are advised to use the MAE-Deployment-provided "ID/Name modification" function.

After a cell ID is changed using the "ID/Name modification" function, the information
about this cell and the external cell information of the adjacent cells are automatically
updated.
● MML-based reconfiguration scheme
a. Delete the intra-site cells with the local cell configured as their intra-
frequency neighboring cell from the EutranIntraFreqNCell MOs.
b. Delete the intra-site cells with the local cell configured as their inter-
frequency neighboring cell from the EutranInterFreqNCell MOs.
c. Delete the cluster cell configurations corresponding to the local cell from
the ClusterCell MO.
d. Delete the neighboring cells for SRS measurement with the local cell
configured as the local CSPC cell from the CspcCellSrsMeasNCell MOs.
e. Change the Cell ID parameter in the Cell MO to the target value.
f. Add intra-site cells with the local cell configured as their intra-frequency
neighboring cell to the EutranIntraFreqNCell MOs.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 135

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

g. Add intra-site cells with the local cell configured as their inter-frequency
neighboring cell to the EutranInterFreqNCell MOs.
h. Add the cluster cell configurations corresponding to the local cell to the
ClusterCell MO.
i. Add the neighboring cells for SRS measurement with the local cell
configured as the local CSPC cell to the CspcCellSrsMeasNCell MOs.

NOTE

The previous operations are dedicated to the local eNodeB. If the cell is an external cell of
other eNodeBs, you need to manually update the Cell ID parameter in the
EutranExternalCell MOs of these eNodeBs or the eNodeBs can use the X2 messages to
automatically update their neighboring cell lists (NCLs).

Topology Change
N/A

1.5.11.2 Engineering Preparation

This section describes the engineering preparation for changing the cell ID,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-45 describes the information to be collected for data preparation.

Table 1-45 Information to be collected

Information Description

Cell information The cell information contains the local cell ID and the
new cell ID.

Neighboring cell The neighboring cell information includes information

information about intra- and inter-frequency neighboring cells.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 136

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-46 Data preparation for changing the cell ID

SN Ope MO Configuration Reference

ratio
n

1 Modi Cell Change Cell ID to the target value.

fy

2 Modi EutranIntraFreqNCell ● When the MAE-Deployment is used

fy for reconfiguration, cell ID-related
parameters will be automatically
3 Modi EutranInterFreqNCell changed to the target values. No
fy operation is required.
4 Modi EutranExternalCell ● When MML commands are used for
fy reconfiguration, manually configure
related parameters.

Data Preparation Mode

To update the information about the external cells of other eNodeBs at the same
time, you are advised to use the MAE-Deployment-provided "ID/Name
modification".

NOTE

● The MAE-Deployment-provided "ID/Name modification" supports automatic update of the

information about the external cells of other eNodeBs when the cell ID is changed.
● To ensure that the associated parameters of the external cells in the current data area are
automatically synchronized, choose Advanced > System > Options on the menu bar of the
main window. The setting function is started. On the Cell Parameter Auto-Synchronization
Policy tab page, select Auto synchronize cell parameters in the entire network and click
OK. For details about the parameter auto-synchronization policy, see section Setting System
Options in the MAE-Access online help.
● Before using the MAE-Deployment to prepare data, ensure that data in the planned data
area is consistent with that in the current data area. If the data is inconsistent, you can
choose Area Management > Planned Area > Synchronize Planned Area NEs from the
menu bar to synchronize data from the current data area to the planned data area. Then,
perform the following operations.

Data preparation of this method is as follows:

1. On the menu bar, choose LTE Application > Network Adjustment > Export
ID/Name Adjustment Data to start exporting the radio network planning
data from the system into a file.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 137

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

2. Edit data in the file based on the prepared data. Then, close the file.
3. On the menu bar of the planned data area, choose LTE Application >
Network Adjustment > Import ID/Name Adjustment Data. A dialog box is
displayed for you to import planned radio data. Import the data from the file
into the system.
For detailed import and export operations, see the MAE-Access online help.

MML Configuration Script Example

If an intra-frequency or inter-frequency neighboring cell exists, remove it first.
/*Removing the intra-frequency E-UTRAN neighbor relationship with cell 2*/
RMV EUTRANINTRAFREQNCELL: CELLID=2;
/*Removing the inter-frequency E-UTRAN neighbor relationship with cell 2*/
RMV EUTRANINTERFREQNCELL: CELLID=2;
/*Removing cell 2 from the cluster*/
RMV CLUSTERCELL:CLUSTERID=1,MCC="460",MNC="01",ENODEBID=1,CELLID=2;
/*Removing cell 2 as a neighboring cell of the CSPC cell for SRS measurement*/
RMV
CSPCCELLSRSMEASNCELL:MCC="460",MNC="01",ENODEBID=1,CELLID=2,NCELLMCC="460",NCELLMNC="01
",NCELLENODEBID=2,NCELLID=100;
/*Modifying the cell ID*/
MOD CELL: LOCALCELLID=0, CELLID=200;
/*Adding an intra-frequency neighboring E-UTRAN cell*/
ADD EUTRANINTRAFREQNCELL: LOCALCELLID =1, MCC="460", MNC="20", ENODEBID=255, CELLID=200;
/*Adding an inter-frequency neighboring E-UTRAN cell*/
ADD EUTRANINTERFREQNCELL: LOCALCELLID =1, MCC="460", MNC="20", ENODEBID=255, CELLID=200;
/*Adding cell 200 to the cluster*/ ADD
CLUSTERCELL:CLUSTERID=1,MCC="460",MNC="01",ENODEBID=1,CELLID=200; /*Adding a neighboring cell
for SRS measurement for CSPC cell 200*/ ADD
CSPCCELLSRSMEASNCELL:MCC="460",MNC="01",ENODEBID=1,CELLID=200,NCELLMCC="460",NCELLMNC="
01",NCELLENODEBID=2,NCELLID=100;

1.5.11.3 Engineering Implementation

This section describes the engineering implementation for changing the cell ID,
including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 138

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

To update the information about the external cells of other eNodeBs at the
same time, you are advised to use the MAE-Deployment-provided "ID/Name
modification". Perform the following steps:
a. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Run the LST GLOBALPROCSWITCH command to query the values of the
following parameters: The Switch of X2 setup by SON, Peer Request
Based X2 Delete Switch, X2 SON Delete Switch, Interface Setup Policy
Switch, The Timer of X2 delete by SON, and X2-based Neighboring
Cell Configuration Update Switch.

▪ Skip this step if the The Timer of X2 delete by SON parameter is 0,

the LTE_NR_X2_SON_SETUP_SW option of the Interface Setup
Policy Switch parameter is deselected, and the options of all the
other preceding parameters are deselected.

▪ If The Timer of X2 delete by SON parameter is not 0, the

LTE_NR_X2_SON_SETUP_SW option of the Interface Setup Policy
Switch parameter is selected, or the options of all the other
preceding parameters are selected, run the MOD
GLOBALPROCSWITCH command to set the The Timer of X2 delete
by SON parameter to 0 and deselect all these options. Example:
MOD GLOBALPROCSWITCH: X2SonSetupSwitch=OFF,
X2SonDeleteTimer=0, PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2USAGE
_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-0,
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_NCELL
_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD_FREQ_CFG_SW-0&UPT_
EXTERNALCELLBAND_CFG_SW-0,
InterfaceSetupPolicySw=X2_SON_INTER_OP_SETUP_FBD_SW-1&LT
E_NR_X2_SON_SETUP_SW-0;
c. Run the LST ENODEBALGOSWITCH command to check whether the
options of ANR algorithm switch are selected.

▪ If all the options of this parameter are deselected, skip this step.

▪ If any option is selected, run the MOD ENODEBALGOSWITCH

command with all options of the ANR algorithm switch parameter
deselected. Example: MOD ENODEBALGOSWITCH:
AnrSwitch=IntraRatEventAnrSwitch-0&IntraRatFastAnrSwitch-0&I
ntraRatAnrAutoDelSwitch-0&UtranEventAnrSwitch-0&GeranEven
tAnrSwitch-0&UtranFastAnrSwitch-0&GeranFastAnrSwitch-0&Cd
maFastAnrSwitch-0&UtranAutoNrtDeleteSwitch-0&GeranAutoNr
tDeleteSwitch-0&CdmaAutoNrtDeleteSwitch-0&CdmaEventAnrS
witch-0;
d. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
e. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 139

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see Setting the Maintenance Mode of the eNodeB to

NORMAL.
f. Restore the settings of the options changed in b and c.
----End

1.5.11.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the cell ID.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.
Step 3 Run the LST CELL command to check whether the value of Cell ID is the same as
planned.
If the value of Cell ID is not the same as planned, check whether the value of Cell
ID in the modified configuration data file is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.5.11.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Roll back the configuration data.
● Using the MAE-Deployment: For detailed operations, see the interactive
operation guide Rolling Back Configuration Data.
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 140

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: DSP ROLCFGINFO: OT=BYINFO;

b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.5.11.4

Engineering Verification.

----End

1.5.12 Changing the Local Cell ID

This section describes how to change the local cell ID.

1.5.12.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the local cell ID.

Application Scenario
The previous local cell ID plan is inappropriate, and a new plan is required.

Reconfiguration Impact
After the local cell ID is changed, the cell automatically resets to make the
configuration take effect. During the reset, the cell cannot provide services.

Reconfiguration Scheme
To change the local cell ID, change the value of Local Cell ID in the Cell MO to
the target value.
NOTE

You are advised to use the MAE-Deployment-provided "ID/Name modification" function. After a
local cell ID is changed using the "ID/Name modification" function, the eNodeB automatically
updates information about the external cells of the cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 141

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
N/A

1.5.12.2 Engineering Preparation

This section describes the engineering preparation for changing the local cell ID,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode.

Information Collection
Table 1-47 describes the information to be collected for data preparation.

Table 1-47 Information to be collected

Information Description

Cell information The cell information includes the original and new local
cell IDs.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-48 Data preparation for changing the local cell ID

SN Ope MO Configuration Reference

ratio
n

1 Modi Cell Change Local Cell ID to the target

fy value.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 142

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

You are advised to use the MAE-Deployment-provided "ID/Name modification" to
update the information about the external cells of other eNodeBs at the same
time.

NOTE

● The MAE-Deployment-provided "ID/Name modification" supports automatic update of the

information about the external cells of other eNodeBs when the cell ID is changed.
● To ensure that the associated parameters of the external cells in the current data area are
automatically synchronized, choose Advanced > System > Options on the menu bar of the
main window. The setting function is started. On the Cell Parameter Auto-Synchronization
Policy tab page, select Auto synchronize cell parameters in the entire network and click
OK. For details about the parameter auto-synchronization policy, see section Setting System
Options in the MAE-Access online help.
● Before using the MAE-Deployment to prepare data, ensure that data in the planned data
area is consistent with that in the current data area. If the data is inconsistent, you can
choose Area Management > Planned Area > Synchronize Planned Area NEs from the
menu bar to synchronize data from the current data area to the planned data area. Then,
perform the following operations.

Data preparation of this method is as follows:

1. On the menu bar, choose LTE Application > Network Adjustment > Export
ID/Name Adjustment Data to start exporting the radio network planning
data from the system into a file.
2. Edit data in the file based on the prepared data. Then, close the file.
3. On the menu bar of the planned data area, choose LTE Application >
Network Adjustment > Import ID/Name Adjustment Data. A dialog box is
displayed for you to import planned radio data. Import the data from the file
into the system.
For detailed import and export operations, see the MAE-Access online help.

1.5.12.3 Engineering Implementation

This section describes the engineering implementation for changing the local cell
ID, including application scenario, reconfiguration impact, reconfiguration scheme,
and topology change.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 143

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
● Local Operations

N/A
● Remote Operations

Using the MAE-Deployment:

a. To prevent unnecessary alarms from being generated during

reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
c. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.5.12.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the local cell
ID.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 3 Run the LST CELL command and check whether the value of Local Cell ID is the
same as planned.

If the value of Local Cell ID is not the same as planned, check whether the value
of Local Cell ID in the modified configuration data file is the same as planned.

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 144

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.5.12.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Roll back the configuration data.
● Using the MAE-Deployment: For detailed operations, see the interactive
operation guide Rolling Back Configuration Data.
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.5.12.4

Engineering Verification.

----End

1.5.13 Changing the TAC

This section describes how to change the tracking area code (TAC).

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 145

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.13.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the TAC.

Application Scenario
The previous TAC plan is inappropriate, and a new plan is required.

Reconfiguration Impact
After the TAC of a cell is changed, the cell automatically resets to make the
configuration take effect. During the reset, the cell cannot provide services.

Reconfiguration Scheme
If any options of the ANR algorithm switch parameter are selected, run the MOD
ENODEBALGOSWITCH command to deselect the options. Then, change Tracking
area code in the CnOperatorTa and EutranExternalCell MOs to the target value.
After the change is complete, run the MOD ENODEBALGOSWITCH command to
restore the settings of ANR algorithm switch.

NOTE

In RAN sharing with common carrier mode, the cell operators must have the same TAC.
Therefore, both TACs must be changed at the same time. Only the MAE-Deployment supports
change of both TACs at the same time.

Topology Change
N/A

1.5.13.2 Engineering Preparation

This section describes the engineering preparation for changing the TAC, including
information collection and preparation of hardware, software, license files, security
certificates, and data. It also describes the data preparation mode.

Information Collection
Table 1-49 describes the information to be collected for data preparation.

Table 1-49 Information to be collected

Information Description

Tracking area Includes the operator ID and the new TAC.

information

Cell operator Includes the local cell ID and tracking area ID.
information

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 146

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

E-UTRAN VoIP Includes the mobile country code (MCC), mobile

service handover network code (MNC), and TAC.
blacklist

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-50 Data preparation for changing the TAC

SN Ope MO Configuration Reference

ratio
n

1 Modi CnOperatorTa Change Tracking area code to the

fy target value.

2 Modi EutranExternalCell Change Tracking area code to the

fy target value.
● When the MAE-Deployment is used
for reconfiguration, TAC-related
parameters will be automatically
changed to the target values. No
operation is required.
● When MML commands are used for
reconfiguration, manually configure
related parameters.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 147

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If an EutranVoipHoBlkList MO is configured, remove the original value of the Tracking area

code parameter and then add the target value.

Data Preparation Mode

You are advised to use the MAE-Deployment-provided "radio data planning file".
The data preparation using the "radio data planning file" is as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

1. On the menu bar, choose LTE Application > Network Adjustment > Export
Radio Network Planning Data to start exporting the radio network planning
data from the system into the radio data planning file.
2. Edit data in the file based on the prepared data. Then, close the file.
3. On the menu bar of the planned data area, choose LTE Application >
Network Adjustment > Import Radio Network Planning Data. A dialog box
is displayed for you to import planned radio data. Import the data from the
file into the system.
For detailed import and export operations, see section Importing and
Exporting Planned Radio Data in the MAE-Access online help.

1.5.13.3 Engineering Implementation

This section describes the engineering implementation for changing the TAC,
including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
a. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 148

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For detailed operations, see Setting the eNodeB Maintenance Mode to

Expand Status.
b. Run the LST GLOBALPROCSWITCH command to query the values of the
following parameters: The Switch of X2 setup by SON, Peer Request
Based X2 Delete Switch, X2 SON Delete Switch, Interface Setup Policy
Switch, The Timer of X2 delete by SON, and X2-based Neighboring
Cell Configuration Update Switch.

▪ Skip this step if the The Timer of X2 delete by SON parameter is 0,

the LTE_NR_X2_SON_SETUP_SW option of the Interface Setup
Policy Switch parameter is deselected, and the options of all the
other preceding parameters are deselected.

▪ If The Timer of X2 delete by SON parameter is not 0, the

LTE_NR_X2_SON_SETUP_SW option of the Interface Setup Policy
Switch parameter is selected, or the options of all the other
preceding parameters are selected, run the MOD
GLOBALPROCSWITCH command to set the The Timer of X2 delete
by SON parameter to 0 and deselect all these options. Example:
MOD GLOBALPROCSWITCH: X2SonSetupSwitch=OFF,
X2SonDeleteTimer=0, PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2USAGE
_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-0,
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_NCELL
_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD_FREQ_CFG_SW-0&UPT_
EXTERNALCELLBAND_CFG_SW-0,
InterfaceSetupPolicySw=X2_SON_INTER_OP_SETUP_FBD_SW-1&LT
E_NR_X2_SON_SETUP_SW-0;
c. Run the LST ENODEBALGOSWITCH command to check whether the
options of ANR algorithm switch are selected.

▪ If all the options of this parameter are deselected, skip this step.

▪ If any option is selected, run the MOD ENODEBALGOSWITCH

command with all options of the ANR algorithm switch parameter
deselected. Example: MOD ENODEBALGOSWITCH:
AnrSwitch=IntraRatEventAnrSwitch-0&IntraRatFastAnrSwitch-0&I
ntraRatAnrAutoDelSwitch-0&UtranEventAnrSwitch-0&GeranEven
tAnrSwitch-0&UtranFastAnrSwitch-0&GeranFastAnrSwitch-0&Cd
maFastAnrSwitch-0&UtranAutoNrtDeleteSwitch-0&GeranAutoNr
tDeleteSwitch-0&CdmaAutoNrtDeleteSwitch-0&CdmaEventAnrS
witch-0;
d. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
e. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
f. Restore the settings of the options changed in b and c.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 149

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.13.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the TAC.

Procedure
Step 1 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.
Step 2 Run the LST CNOPERATORTA and LST EUTRANEXTERNALCELL commands and
verify that the value of Tracking area code is the same as planned.
If it is not the same as planned, check whether the value of Tracking area code in
the modified configuration data file is the same as planned:
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.5.13.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Roll back the configuration data.
● Using the MAE-Deployment: For detailed operations, see the interactive
operation guide Rolling Back Configuration Data.
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 150

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.5.13.4

Engineering Verification.

----End

1.5.14 Changing the Neighboring Cell Parameters

This section describes how to change the neighboring cell parameters.

1.5.14.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the neighboring cell
parameters.

Application Scenario
The previous neighboring cell parameter plan is inappropriate, and a new plan is
required.

Reconfiguration Impact
After you change the neighboring cell parameters, the handover target cell will be
changed.

Reconfiguration Scheme
If any options of the ANR algorithm switch parameter are selected, run the MOD
ENODEBALGOSWITCH command to deselect the options. After neighboring cell
parameters are modified, run the MOD ENODEBALGOSWITCH command to
restore the settings of ANR algorithm switch.

To change the neighboring cell parameters, modify the corresponding

neighboring-cell-related MOs of E-UTRAN, UTRAN, CDMA2000, and GERAN cells.
The MOs that need to be modified in different modes are as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 151

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● E-UTRAN: EutranIntraFreqNCell, EutranInterFreqNCell, EutranExternalCell,

EutranInterNFreq, EutranNFreqRanShare, IntraFreqBlkCell, InterFreqBlkCell,
and EutranExternalCellPlmn
● UTRAN: UtranNFreq, UtranRanShare, UtranExternalCell,
UtranExternalCellPlmn, and UtranNCell
● CDMA2000: Cdma2000Nfreq, Cdma20001XrttExtCell, Cdma2000HrpdExtCell,
Cdma20001XrttNCell, Cdma2000HrpdNCell, and Cdma2000BandClass
● GERAN: GeranNfreqGroup, GeranRanShare, GeranNfreqGroupArfcn,
GeranExternalCell, GeranNcell, and GeranExternalCellPlmn

Topology Change
N/A

1.5.14.2 Engineering Preparation

This section describes the engineering preparation for changing the neighboring
cell parameters, including information collection and preparation of hardware,
software, license files, security certificates, and data. It also describes the data
preparation mode.

Information Collection
Table 1-51 describes the information to be collected for data preparation.

Table 1-51 Information Collection

Information Description

Neighboring cell Neighboring cell parameters include the new

parameters parameters of the MOs to be changed.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 152

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation
Based on the planned neighboring cell parameters, prepare data listed in the
following table.

Table 1-52 Data preparation for changing the neighboring cell parameters
SN Op MO Category MO Configuration
er Reference
ati
on

1 M Neighboring E- EutranIntraFreqNCell Change the

odi UTRAN cell corresponding
fy EutranInterFreqNCell parameters to the
EutranExternalCell target values based on
the neighboring cell
EutranInterNFreq parameter plan.

EutranNFreqRanShare

IntraFreqBlkCell

InterFreqBlkCell

EutranExternalCellPlmn

2 M Neighboring UtranNFreq
odi UTRAN cell
fy UtranRanShare

UtranExternalCell

UtranExternalCellPlmn

UtranNCell

3 M Neighboring Cdma2000Nfreq
odi CDMA2000 cell
fy Cdma20001XrttExtCell

Cdma2000HrpdExtCell

Cdma20001XrttNCell

Cdma2000HrpdNCell

Cdma2000BandClass

4 M Neighboring GeranNfreqGroup
odi GERAN cell
fy GeranRanShare

GeranNfreqGroupArfcn

GeranExternalCell

GeranNcell

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 153

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Op MO Category MO Configuration
er Reference
ati
on

GeranExternalCellPlmn

Data Preparation Mode

You are advised to use the MAE-Deployment-provided "radio data planning file".
The data preparation using the "radio data planning file" is as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

1. On the menu bar, choose LTE Application > Network Adjustment > Export
Radio Network Planning Data to start exporting the radio network planning
data from the system into the radio data planning file.
2. Edit data in the file based on the prepared data. Then, close the file.
3. On the menu bar of the planned data area, choose LTE Application >
Network Adjustment > Import Radio Network Planning Data. A dialog box
is displayed for you to import planned radio data. Import the data from the
file into the system.
For detailed import and export operations, see section Importing and
Exporting Planned Radio Data in the MAE-Access online help.

1.5.14.3 Engineering Implementation

This section describes the engineering implementation for changing the
neighboring cell parameters, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operation

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 154

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

N/A
● Remote Operation
a. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Run the LST GLOBALPROCSWITCH command to query the values of the
following parameters: The Switch of X2 setup by SON, Peer Request
Based X2 Delete Switch, X2 SON Delete Switch, Interface Setup Policy
Switch, The Timer of X2 delete by SON, and X2-based Neighboring
Cell Configuration Update Switch.

▪ Skip this step if the The Timer of X2 delete by SON parameter is 0,

the LTE_NR_X2_SON_SETUP_SW option of the Interface Setup
Policy Switch parameter is deselected, and the options of all the
other preceding parameters are deselected.

▪ If The Timer of X2 delete by SON parameter is not 0, the

LTE_NR_X2_SON_SETUP_SW option of the Interface Setup Policy
Switch parameter is selected, or the options of all the other
preceding parameters are selected, run the MOD
GLOBALPROCSWITCH command to set the The Timer of X2 delete
by SON parameter to 0 and deselect all these options. Example:
MOD GLOBALPROCSWITCH: X2SonSetupSwitch=OFF,
X2SonDeleteTimer=0, PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2USAGE
_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-0,
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_NCELL
_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD_FREQ_CFG_SW-0&UPT_
EXTERNALCELLBAND_CFG_SW-0,
InterfaceSetupPolicySw=X2_SON_INTER_OP_SETUP_FBD_SW-1&LT
E_NR_X2_SON_SETUP_SW-0;
c. Run the LST ENODEBALGOSWITCH command to check whether the
options of ANR algorithm switch are selected.

▪ If all the options of this parameter are deselected, skip this step.

▪ If any option is selected, run the MOD ENODEBALGOSWITCH

command with all options of the ANR algorithm switch parameter
deselected. Example: MOD ENODEBALGOSWITCH:
AnrSwitch=IntraRatEventAnrSwitch-0&IntraRatFastAnrSwitch-0&I
ntraRatAnrAutoDelSwitch-0&UtranEventAnrSwitch-0&GeranEven
tAnrSwitch-0&UtranFastAnrSwitch-0&GeranFastAnrSwitch-0&Cd
maFastAnrSwitch-0&UtranAutoNrtDeleteSwitch-0&GeranAutoNr
tDeleteSwitch-0&CdmaAutoNrtDeleteSwitch-0&CdmaEventAnrS
witch-0;
d. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
e. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 155

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see Setting the Maintenance Mode of the eNodeB to

NORMAL.
f. Restore the settings of the options changed in b and c.
----End

1.5.14.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the
neighboring cell parameters.

Context
Modifying the EutranInterFreqNCell MO is used as an example to describe how
to verify the reconfiguration. You can also run the LST commands to check other
MOs.

Procedure
Step 1 Run the LST EUTRANINTERFREQNCELL command and verify that the value is the
same as planned.
If the value is not the same as planned, check whether the value in the modified
configuration data file is the same as planned:
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.5.14.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Roll back the configuration data.
● Using the MAE-Deployment: For detailed operations, see the interactive
operation guide Rolling Back Configuration Data.
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 156

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.5.14.4

Engineering Verification.

----End

1.5.15 Changing the Intra-Frequency Handover Offset

This section describes how to change the intra-frequency handover offset of a cell.

1.5.15.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the intra-frequency
handover offset.

Application Scenario
The previous intra-frequency handover offset plan is inappropriate, and a new
plan is required.

Reconfiguration Impact
No impact

Reconfiguration Scheme
When you change the intra-frequency handover offset, change Intrafreq
handover offset in the IntraFreqHoGroup MO to the target value.

Topology Change
N/A

1.5.15.2 Engineering Preparation

This section describes the engineering preparation for changing the intra-
frequency handover offset, including information collection and preparation of

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 157

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-53 describes the information to be collected for data preparation.

Table 1-53 Information to be collected

Information Description

Intra-frequency Includes the local cell ID and intra-frequency handover

handover parameter parameter group ID.
group information

Intra-frequency Includes a new intra-frequency handover offset.

handover offset
information

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-54 Data preparation for changing the intra-frequency handover offset

SN Ope MO Configuration Reference

ratio
n

1 Modi IntraFreqHoGroup Change Intrafreq handover offset to

fy the target value.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 158

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Changing the Intra-Frequency Handover Offset").
For details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, the value of the Intrafreq handover offset parameter is
changed to 2. The MML configuration script is as follows:
/*Changing the intra-frequency handover offset to 2*/
MOD INTRAFREQHOGROUP: LocalCellId=0, IntraFreqHoGroupId=9, IntraFreqHoA3Offset=2;

1.5.15.3 Engineering Implementation

This section describes the engineering implementation for changing the intra-
frequency handover offset, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 159

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

N/A
● Remote Operations
– Using the MAE-Deployment:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
iii. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Run the following commands to back up and export the
configuration file. The configuration file can be used to roll back the
base station configurations to the original state, if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.5.15.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the intra-
frequency handover offset.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 160

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Run the LST INTRAFREQHOGROUP command and verify that the value of
Intrafreq handover offset(0.5dB) is the same as planned.

If it is not the same as planned, check whether Intrafreq handover offset in the
modified configuration data file is the same as planned.

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.5.15.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 161

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.5.15.4

Engineering Verification.

----End

1.5.16 Changing the Cell Power

This section describes how to change the power of a cell.

1.5.16.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the power of a cell.

Application Scenario
The cell power needs to be changed due to the network plan change.

Reconfiguration Impact
No impact

Reconfiguration Scheme
Determine the reconfiguration scheme for changing the cell power according to
the following table.

Table 1-55 Scheme options

Cell Type Reconfiguration Scheme

Common FDD/TDD cell Change the values of Reference signal

power and PB in the PDSCHCfg MO
to the target values.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 162

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cell Type Reconfiguration Scheme

NB-IoT cell Change the value of Reference signal

power in the PDSCHCfg MO or
Reference Signal Power in the
EuPrbSectorEqm MO to the target
value.

Single frequency network (SFN) cell ● If Reference signal power in the

eUCellSectorEqm MO is set to
Combined cell 32767:
1. Change the values of Reference
signal power and PB in the
PDSCHCfg MO to the target
values.
● If Reference signal power in the
eUCellSectorEqm MO is not set to
32767:
1. Change the value of Reference
signal power in the
eUCellSectorEqm MO to the
target value.
2. Change the value of PB in the
PDSCHCfg MO to the target
value.

MPRU_AGGREGATION (LampSite) cell ● If Reference signal power in the

EuSectorEqmGroup MO is set to
32767:
1. Change the values of Reference
signal power and PB in the
PDSCHCfg MO to the target
values.
● If Reference signal power in the
EuSectorEqmGroup MO is not set
to 32767:
1. Change the value of Reference
signal power in the
EuSectorEqmGroup MO to the
target value.
2. Change the value of PB in the
PDSCHCfg MO to the target
value.

Inter-eNodeB SFN cell Change the value of Reference signal

power in the SfnAuxResBind MO to
the target value.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 163

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

● Change the FDD/TDD cell power according to the descriptions of the Reference signal
power and PB parameters in the PDSCHCfg MO and the Reference signal power
parameter in the eUCellSectorEqm MO in 3900 & 5900 Series Base Station MO and
Parameter Reference. The change should be performed based on the maximum RRU
transmit power and the cell bandwidth. You can run the DSP TXBRANCH command to query
the maximum RRU transmit power.
● Change the NB-IoT cell power according to the descriptions of the Reference signal power
parameter in the PDSCHCfg MO or the Reference signal power parameter in the
eUCellSectorEqm MO in 3900 & 5900 Series Base Station MO and Parameter Reference. The
change should be performed based on the maximum RRU transmit power of the NB-IoT cell.
For the maximum RRU transmit power supported by an NB-IoT cell, see the RRU technical
specifications in RRU Technical Specifications.
● After the FDD/TDD cell power is changed, the original cell bandwidth may not match the
new reference signal transmit power. As a result, the cell cannot be established. To change
the cell bandwidth, perform operations by referring to 1.5.6 Changing the Cell Bandwidth.

Figure 1-23 Changing the FDD/TDD cell power

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 164

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-24 Changing the NB-IoT cell power

Topology Change
N/A

1.5.16.2 Engineering Preparation

This section describes the engineering preparation for changing the power of a
cell, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Information Collection
Table 1-56 describes the information to be collected for data preparation.

Table 1-56 Information to be collected

Information Description

Cell information Includes the local cell ID and the new

cell power.

Cell sector equipment information Indicates the sector equipment

information in a cell whose reference
signal power is to be changed.

PRB sector equipment information Indicates the sector equipment

information in a PRB whose reference
signal power is to be changed.

SFN auxiliary eNodeB resource Indicates the sector equipment

information of cells whose reference
signal power is to be changed in an
auxiliary eNodeB involved in an SFN
cell. NB-IoT cells are not involved.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 165

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before the reconfiguration, run the DSP TXBRANCH, DSP RXBRANCH or DSP RRU command
to query the capability of the RF module. This is to ensure that the EARFCN, bandwidth,
and power of the cell are still within the capability range of the RF module after the
reconfiguration.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-57 Data preparation for changing the FDD/TDD cell power

SN Ope MO Configuration Reference

ratio
n

1 Modi PDSCHCfg ● If the cell is a common cell: Change

fy the values of the Reference signal
power and PB parameters to the
target values.
● If the cell is a non-common cell:
– When the cell is a multi-MPRU
(LampSite) cell, change the value
of the PB parameter to the target
value.
– When the cell is an SFN cell or a
combined cell, change the value of
the PB parameter to the target
value.

2 Modi EuSectorEqmGroup If the cell is a non-common cell:

fy ● When the cell is a multi-MPRU
(LampSite) cell, change the value of
the Reference signal power
parameter to the target value.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 166

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

3 Modi eUCellSectorEqm If the cell is a non-common cell:

fy ● When the cell is a multi-MPRU
(LampSite) cell, change the value of
the Reference signal power
parameter to the target value.
● When the cell is an SFN cell or a
combined cell, change the value of
the Reference signal power
parameter to the target value.

4 Modi SfnAuxResGrpBind If the cell is a non-common cell:

fy ● When the cell is an inter-eNodeB SFN
cell and the auxiliary cell is a
LampSite cell, change the value of
Reference signal power in the
SfnAuxResGrpBind MO to the target
value on the auxiliary eNodeB to
change the reference signal power of
the sector equipment group for the
auxiliary eNodeB.

5 Modi SfnAuxResBind If the cell is a non-common cell:

fy ● When the cell is an inter-eNodeB SFN
cell and the auxiliary cell is not a
LampSite cell, change the value of
Reference signal power in the
SfnAuxResBind MO to the target
value to change the reference signal
power of the sector equipment for
the auxiliary eNodeB.

Table 1-58 Data preparation for changing the NB-IoT cell power
SN Ope MO Configuration Reference
ratio
n

1 Modi PDSCHCfg Change the value of the Reference

fy signal power parameter to the target
value.

2 Modi EuPrbSectorEqm Change the value of the Reference

fy Signal Power parameter to the target
value.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 167

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Changing the Cell Power"). For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

NOTE

If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

In the following information, an FDD/TDD SFN cell is used as an example to

describe the MML-based configuration script used for data preparation:
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Modifying the sector equipment information in a cell with Reference signal power set to 184*/
MOD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, ReferenceSignalPwr=184;
/*Changing the cell power with PB set to 1*/
MOD PDSCHCFG: LocalCellId=0, Pb=1;

In the following information, an NB-IoT cell is used as an example to describe the

MML-based configuration script used for data preparation:
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Modifying the cell power with Reference signal power set to 220*/
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=220;
/*Modifying the sector equipment information in a PRB with Reference Signal Power set to 220*/
MOD EUPRBSECTOREQM: LocalCellId=0, PrbId=0, SectorEqmId=0, ReferenceSignalPwr=220;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 168

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

● The MOD EUCELLSECTOREQM command can be used to modify the power of only multi-
RRU cells.
● For multi-RRU cells, the value of the ReferenceSignalPwr parameter in the PDSCHCfg MO
takes effect only when the ReferenceSignalPwr parameter in the eUCellSectorEqm MO is
set to 32767.

In the following information, an inter-eNodeB SFN cell (where the auxiliary cell is
not a LampSite cell) is used as an example to describe the MML-based
configuration script used for data preparation:
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Changing the value of Reference signal power in the SfnAuxResBind MO*/
MOD SFNAUXRESBIND:SECTOREQMID=1,ENODEBID=100, LOCALCELLID=0,REFERENCESIGNALPWR=100;

1.5.16.3 Engineering Implementation

This section describes the engineering implementation for changing the power of
a cell, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready, and the license file is
available in the save path on the FTP server.

NOTE

Before using the MAE-Deployment to modify both the antenna mode and the reference signal
power for a cell, run the DEA CELL command to deactivate the cell. Then, activate the script on
the MAE-Deployment.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the license file in use must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 169

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. To prevent unnecessary alarms from being generated during

reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
iii. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Run the following commands to back up and export the
configuration file. The configuration file can be used to roll back the
base station configurations to the original state, if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.5.16.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the cell
power.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 170

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 3 Verify whether the changed parameter values are the same as planned.
● For a common cell, run the LST PDSCHCFG command to verify that the
values of Reference signal power and PB are the same as planned.
● For a multi-MPRU (LampSite) cell, run the LST EUCELLSECTOREQM, LST
EUSECTOREQMGROUP, and LST PDSCHCFG commands to verify that the
values of Reference signal power and PB are the same as planned.
● For an SFN cell or a combined cell, run the LST EUCELLSECTOREQM and LST
PDSCHCFG commands to verify that Reference signal power and PB are the
same as planned.
● For an inter-eNodeB SFN cell (the auxiliary cell is a LampSite cell), run the
LST SFNAUXRESGRPBIND command to verify that the value of Reference
signal power is the same as planned.
● For an inter-eNodeB SFN cell (the auxiliary cell is not a LampSite cell), run
the LST SFNAUXRESBIND command to verify that the value of Reference
signal power is the same as planned.

If they are not the same as planned, check whether the Reference signal power
and PB values in the script are correct:

● If the two parameter values are incorrect, reconfigure them and then run the
MOD PDSCHCFG or MOD EUCELLSECTOREQM command to change the
values of Reference signal power and PB to the target values.
● If they are correct, contact Huawei technical support or dial the Huawei
technical support hotline.

----End

1.5.16.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 2 Restore the configuration data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 171

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 3 Verify that engineering rollback is successful according to instructions in 1.5.16.4

Engineering Verification.

----End

1.5.17 Changing a Cell to SFN Mode (Intra-BBU)

This section describes how to change a cell from non-SFN mode to intra-BBU SFN
mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 172

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.17.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing a cell from non-SFN
mode to intra-BBU SFN mode.

Application Scenario
There is interference among cells. After the cells are changed to SFN mode, the
original interfering signals are changed to a multi-path strengthened signal. This
increases the SINR at the cell edge, decreases the proportion of areas with low
SINR values, and improves user experience at the cell edge.

Reconfiguration Impact
After cells are changed from non-SFN mode to intra-BBU SFN mode, RRUs in the
SFN cell will be deactivated and service drops occur on UEs served by original
cells.

Reconfiguration Scheme
Determine the reconfiguration scheme for changing a cell from non-SFN mode to
intra-BBU SFN mode according to the following table.

Table 1-59 Scheme options

If... Then...

BBPs are insufficient Add BBPs and CPRI connections.

RRUs are insufficient Add CPRI chains or rings and RRUs.

The neighbor relationship is changed Update the network planning of

after the cell is changed to the SFN neighboring cells. To replan
mode neighboring cells, see section
"Changing the Neighboring Cell
Parameters."

PCI conflict with a neighboring cell
occurs after the cell is changed to the
SFN mode
Update the PCI planning. If the PCI of
the local cell and that of a neighboring
cell are the same, change the PCI of
the neighboring cell. For details, see
section "Changing the PCI of a Cell"
(not involving NB-IoT cells).

NOTE

● A cell is deactivated after being changed from non-SFN mode to SFN mode. You are advised
to manually deactivate the cell, and then activate the cell manually.
● The MultiRruCellMode parameter should be reconfigured. That is, remove the redundant
cells if you want to reconfigure existing cells.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 173

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-25 shows the reconfiguration procedure for changing a cell from non-
SFN mode to SFN mode.

Figure 1-25 Procedure for changing a cell from non-SFN mode to SFN mode (FDD/TDD cell)

NOTE

In TDD, SFN supports the bandwidth of 10 MHz and 20 MHz. For an LBBPc, only one 20 MHz
4T4R cell or three 10 MHz 4T4R cells are supported. Specification inconsistency may generate
baseband resource fragments. Therefore, if an SFN cell with 10 MHz bandwidth is deployed on
an LBBPc, the sector baseband equipment and primary baseband equipment must be bound to
prevent baseband resource fragments. 8T8R cells cannot be deployed on LBBPc boards. If an
8T8R SFN cell exists, the sector baseband equipment and primary baseband equipment must be
bound to prevent baseband resource fragments.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 174

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-26 Procedure for changing a cell from non-SFN mode to SFN mode (NB-
IoT cell)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 175

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Figure 1-27 shows the topologies before and after the reconfiguration.

Figure 1-27 Topologies before and after the reconfiguration

1.5.17.2 Engineering Preparation

This section describes the engineering preparation for changing a cell from non-
SFN mode to SFN mode, including information collection and preparation of
hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-60 describes the information to be collected before changing a cell from
non-SFN mode to SFN mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 176

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-60 Information to be collected

Information Description

Cell information Basic information about the cell to be added, such as

RAT, Flag of Multi-RRU Cell, Sector equipment
number of SFN cell, and Mode of Multi-RRU Cell
TX/RX mode of the cell, for example, 4T4R
● In FDD, SFN cells support 1T1R, 2T2R, 2T4R, or 4T4R.
● In NB-IoT, SFN cells support 1T1R or 2T2R.
● In TDD, SFN cells support 4T4R, 8T8R, or both of
them.

BBP model Model of the BBP, for example, UBBP

RF module type Type of the RF module to be added, for example, MRRU

Topology If an RF module is to be added, collect information

about the CPRI topology for RF modules, for example,
the star topology.
The SFN can be in the star or chain topology in
FDD/NB-IoT.
The SFN must be in the star topology in TDD.

Sector equipment ● Sector equipment ID

● Reference signal power, indicating the reference
signal power of the RRU in the sector equipment

Hardware Preparation
Table 1-61 describes the hardware to be prepared for changing a cell from non-
SFN mode to SFN mode.

Table 1-61 Hardware to be prepared

If... Then...

BBPs are insufficient Add BBPs as required.

RF resources are Add RF modules as required.

insufficient

Software Preparation
N/A

License File Preparation

Prepare a new license file if the currently used license cannot meet requirements.
The number of SFN-related licenses to be applied for must be the same as that of

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 177

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

the sector equipment pieces in the SFN cell. Table 1-62 describes the license
control items to be prepared.

Table 1-62 License control items related to the SFN

License Control Applicable RAT License Function
Item

Cell License(per FDD/NB- Controls the number of cells.

Cell) IoT/TDD

Carrier FDD/TDD Controls the cell bandwidth. Each RRU

Bandwidth(per serves one cell.
5MHz)

Resource FDD/NB- Controls the number of resource blocks

Block(per RB) IoT/TDD (RBs).

BB Receive FDD/TDD Controls the baseband receive channel.

Channel(per
Channel)

RF Transmit FDD/TDD Controls the RF transmit channel.

Channel(per
Channel)

DL 2x2 FDD/NB- Controls downlink 2x2 MIMO.

MIMO(per Cell) IoT/TDD

UL 2x2 MU- FDD/NB- Controls uplink 2x2 MU-MIMO.

MIMO IoT/TDD

DL 4x2 MIMO FDD/TDD Controls downlink 4x2 MIMO.

UL 4-Antenna FDD/TDD Controls uplink 4-antenna receive diversity.

Receive
Diversity(per
Cell)

UL 2x4 MU- FDD/TDD Controls uplink 2x4 MU-MIMO.

MIMO(per Cell)

Single TDD Controls single-stream beamforming.

Streaming
Beamforming(p
er Cell)

Dual streaming TDD Controls dual-stream beamforming.

Beamforming

MU- TDD Controls MU-beamforming.

Beamforming(p
er Cell)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 178

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

License Control Applicable RAT License Function

Item

UL Interference FDD/TDD Controls uplink interference rejection

Rejection combining (IRC).
Combining(per
Cell)

P2P FDD/TDD Controls P2P throttling.

Throttling(per
Cell)

CPRI FDD/TDD Controls CPRI compression.

Compression(pe
r Cell)

SFN(per Cell) FDD/NB- Controls SFN.

IoT/TDD

Adaptive SFN/ FDD/TDD Controls adaptive SFN/SDMA (per cell).

SDMA(per Cell)

Inter-BBP SFN FDD/NB- Controls inter-BBP SFN.

IoT/TDD

Inter-BBU SFN FDD/TDD Controls inter-BBU SFN. This license must

be applied for in inter-eNodeB SFN
networking.

Inter-BBP FDD/TDD Controls inter-BBP adaptive SFN/SDMA.

Adaptive SFN/
SDMA

Inter-BBU FDD/TDD Controls inter-BBU adaptive SFN/SDMA.

Adaptive SFN/ This license must be applied for in inter-
SDMA eNodeB SFN networking.

Security Certificate Preparation

N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 179

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-63 Data preparation for changing a cell to intra-BBU SFN mode
SN Ope MO Configuration Reference
ratio
n

1 Deac Cell -
tivat
e

2 Dele Cell Delete redundant cells.

te

3 Add RU (using MML For details about parameter settings, see

commands)/BBP Base Station Cabinets and Subracks
(using the MAE- (Including the BBU Subrack)
Deployment) Configuration Feature Parameter
Description.
4 Add BASEBANDEQM -

5 Modi RRUCHAIN For details about parameter settings, see

fy RF Unit and Topology Management
Feature Parameter Description.
6 Add RRU/RFU

7 Modi SECTOR For details about parameter settings, see

fy Cell Management Feature Parameter
Description.
8 Add SECTOREQM

9 Modi Cell Set the Mode of Multi-RRU Cell

fy parameter to SFN and set the Sector
equipment number of SFN cell
parameter to the target value.

10 Modi eUCellSectorEqm For details about parameter settings, see

fy Cell Management Feature Parameter
Description.
11 Activ Cell -
ate

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:
● Using the batch configuration mode of the MAE-Deployment. For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 180

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

If the currently used license file does not meet the requirements, reload a license
file. If the currently used license file meets the requirements, directly change the
cells from non-SFN mode to SFN mode.
Before the modification, ensure that the SrsCfgInd parameter is set to
BOOLEAN_TRUE(True).
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="user", PWD="*****", DIR="ftproot/", FN="
LIC_LTE_ON.dat";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN=" LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="
user", PWD="****";
/*Deactivating the cells*/
DEA CELL:LOCALCELLID=0;
DEA CELL:LOCALCELLID=1;
DEA CELL:LOCALCELLID=2;
/*Removing redundant cells*/
RMV CELL:LOCALCELLID=1;
RMV CELL:LOCALCELLID=2;

If BBPs are insufficient, perform the following operations:

/*Adding a UBBP*/
ADD BRD: SN=2, BT=UBBP, BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-0&NBIOT-0&NR-1;
/*Adding baseband equipment*/
ADD BASEBANDEQM:BASEBANDEQMID=3,BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL,SN1=3;

If RF resources are insufficient, perform the following operations:

/*Adding an RRU chain or ring*/
ADD RRUCHAIN: RCN=1, TT=CHAIN, HSN=3, HPN=0;
/*Adding an RRU in FDD/TDD*/
ADD RRU: CN=0, SRN=60, SN=0, RCN=1, PS=0, RT=MRRU, RS=TDL, RN="60", RXNUM=4, TXNUM=4;
/*Adding an RRU in NB-IoT*/
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=1, RT=MRRU, RS=MO, RXNUM=2, TXNUM=2,
MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF;
/*Adding a sector in FDD/TDD*/
ADD SECTOR:SECTORID=0,SECNAME="0",LOCATIONNAME="0",
USERLABEL="0",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,AN
T2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=60,ANT3SN=0,ANT3N=R0C,ANT4CN=0,ANT4SRN=60,ANT4SN=0,
ANT4N=R0D,CREATESECTOREQM=FALSE,SECTOREQMID=0;
/*Adding sector equipment in FDD/TDD*/
ADD
SECTOREQM:SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,
ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANTTYPE2=RXTX_MODE,ANT3SR
N=60,ANT3SN=0,ANT3N=R0C,ANTTYPE3=RXTX_MODE,ANT4SRN=60,ANT4SN=0,ANT4N=R0D,ANTTYPE4=RX
TX_MODE;
/*Adding a sector and sector equipment in NB-IoT*/
ADD SECTOR: SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0,
ANT2SRN=60, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=0;
/*Modifying a cell with the Flag of Multi-RRU Cell parameter set to BOOLEAN_TRUE and the Mode of Multi-
RRU Cell parameter set to SFN*/
MOD CELL:LOCALCELLID=0,MULTIRRUCELLFLAG=BOOLEAN_TRUE,
MULTIRRUCELLMODE=SFN,SECTOREQMNUM=3;
/*Adding sector equipment for a cell*/
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=2, BASEBANDEQMID=3;
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=3, BASEBANDEQMID=3;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 181

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Adding the binding relationship between the sector equipment and the NB-IoT PRB*/
ADD EUPRBSECTOREQM: LocalCellId=0, SectorEqmId=2, PrbId=0;
ADD EUPRBSECTOREQM: LocalCellId=0, SectorEqmId=3, PrbId=0;
/*If the neighboring cell relationship is changed after the cell is changed to the SFN mode, updating the
network planning of neighboring cells. To replan neighboring cells, see section "Changing the Neighboring
Cell Parameters."*/
/*If a neighboring cell PCI conflict occurs after the cell is changed to the SFN mode, updating the PCI
planning. If the PCI of the local cell and that of the neighboring cell are the same, change the PCI of the
neighboring cell. For details, see "Changing the PCI of a Cell."*/
/*Activating the cell*/
ACT CELL: LocalCellId=0;

1.5.17.3 Engineering Implementation

This section describes the engineering implementation for changing a cell from
non-SFN mode to intra-BBU SFN mode, including prerequisites, context, and
procedure.

Prerequisites
Related information, license files, and data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Insert the BBP into the subrack. For details, see Maintaining the Case-
Structured BBU > Adding BBU Components > Replacing the LBBP or
Replacing the UBBP in BBU Hardware Maintenance Guide.
b. Install an RF module. For details about the operation, see the installation
guide for RRUs.
c. Install a CPRI optical fiber. For details, see Installing a CPRI Optical
Fiber in the installation guide of the corresponding RRU.
● Remote Operations
Using the MAE-Deployment:

NOTE

If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

a. To prevent unnecessary alarms from being generated during

reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Back up the license file in use to the MAE server.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 182

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Run the ULD LICENSE command.

Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
c. Import a new license file.
Run the INS LICENSE command.
Example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
d. Deactivate the cell. Run the DEA CELL command.
Example: DEA CELL: LocalCellId=0;
e. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
f. Run the ACT CELL command to activate the cell.
Example: ACT CELL:LocalCellId=0;
g. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

Using MML commands

a. To prevent unnecessary alarms from being generated during

reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Run the following commands to back up and export the configuration
file. The configuration file can be used to roll back the base station
configurations to the original state, if the reconfiguration fails.
i. To back up the configuration file, run the BKP CFGFILE command.
ii. To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
d. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 183

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.17.4 Engineering Verification

This section describes how to verify the reconfiguration for changing a cell from
non-SFN mode to SFN mode.

Procedure
Step 1 Run the DSP CELL command to check whether the value of Cell instance state is
Normal for the cell.
If the value of Cell instance state is Uninstall, check the cell configuration, cell
reference signal power configuration, or hardware based on the value of Reason
for latest state change in the command output.
Step 2 Run the LST CELL command to check whether the values of Flag of Multi-RRU
Cell, Mode of Multi-RRU Cell, and Cell transmission and reception mode are
the same as planned.
Step 3 Run the LST EUCELLSECTOREQM command to check whether the values of
Sector equipment ID and Reference signal power are the same as planned.
Step 4 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
----End

1.5.17.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Context
The cell capacity mode remains unchanged after the SFN cell is reconstructed. To
use a different cell capacity mode, change the value of CellCapacityMode
parameter.

Procedure
Step 1 Roll back the reconfiguration data.
● Using the MAE-Deployment:
The MAE-Deployment generates configuration rollback scripts when exporting
incremental configuration scripts. Configuration rollback scripts simplify data
rollback on the live network.
a. On the menu bar, choose Area Management > Planned Area > Export
Incremental Scripts to start the wizard of exporting scripts. Then, select
Launch Script Executor in the wizard to activate exported scripts for
data to take effect on the live network. For detailed operations, see
section Exporting Incremental Scripts from a Planned Data Area in the
MAE-Access online help.
b. Click the Summary tab in the Script Executor window.
c. Select a project whose data needs to be rolled back and right-click it. For
detailed operations, see section Fallback Based on Configuration Steps
in the MAE-Access online help.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 184

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license is updated.
Run the INS LICENSE command. Example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="user", PWD="****";
Step 3 Restore the cable connections.
Step 4 Verify that engineering rollback is successful according to instructions in 1.5.17.4
Engineering Verification.

----End

1.5.18 Changing a Cell to SFN Mode (Inter-BBU)

This section describes how to change a cell from non-SFN mode to inter-BBU SFN
mode.

1.5.18.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing a cell from non-SFN
mode to inter-BBU SFN mode.

Application Scenario
There is interference among cells. After the cells are changed to SFN mode, the
original interfering signals are changed to a multi-path strengthened signal. This
increases the SINR at the cell edge, decreases the proportion of areas with low

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 185

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SINR values, and improves user experience at the cell edge. If the cells that are
interfered with are served by different base stations, adjustment of cable
connections for the RRUs is not required after a cell is changed from non-SFN
mode to inter-BBU SFN mode.

Reconfiguration Impact
After cells are changed from non-SFN mode to inter-BBU SFN mode, RRUs in the
SFN cell will be deactivated and service drops occur on UEs served by original
cells.

Reconfiguration Scheme
Determine the reconfiguration scheme for changing a cell from non-SFN mode to
inter-BBU SFN mode according to the following table.

Table 1-64 Scheme options

If... Then...

- Install a USU3900 or a USU3910. For details about

how to install a USU3900, see USU3900
Installation Guide. For details about how to install
a USU3910, see USU3910 Installation Guide.

The main control board is
an LMPT in TDD
Replace the main control board by referring to
1.7.6 Transmission Capacity Expansion from
One LMPT Board to LMPT + UMPT Boards
(Mode 1) (TDD) (IPv4 Transmission Only) and
1.7.7 Transmission Capacity Expansion from
One LMPT Board to LMPT + UMPT Boards
(Mode 2) (TDD) (IPv4 Transmission Only)

BBPs are insufficient ● Add BBPs.

● Add CPRI connections.

RF resources are 1. Add CPRI chains or rings.

insufficient 2. Add RF modules.

- Configure the USU3900 or the USU3910. For

The neighbor relationship
is changed after the cell is
changed to the SFN mode
details about the software configuration of the
USU3900, see USU3900 Initial Configuration
Guide. For details about the software
configuration of the USU3910, see USU3910 Initial
Configuration Guide.
Update the network planning of neighboring cells.
To replan neighboring cells, see section "Changing
the Neighboring Cell Parameters."

PCI conflict with a Update the PCI planning. If the PCI of the local
neighboring cell occurs cell and that of a neighboring cell are the same,
after the cell is changed to change the PCI of the neighboring cell. For details,
the SFN mode see section "Changing the PCI of a Cell".

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 186

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

● A cell is deactivated after being changed from non-SFN mode to SFN mode. You are advised
to manually deactivate the cell to be changed and then activate the SFN cell manually.
● For details about how to configure the USU3900, see USU3900 Initial Configuration Guide.
● For details about how to configure the USU3910, see USU3910 Initial Configuration Guide.
● If the main control board is a UMPT in TDD, it does not need to be replaced.

Figure 1-28 shows the reconfiguration procedure for changing a cell from non-
SFN mode to SFN mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 187

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-28 Procedure for changing a cell from non-SFN mode to SFN mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 188

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Figure 1-29 shows the topologies before and after the reconfiguration.

Figure 1-29 Topologies before and after the reconfiguration

1.5.18.2 Engineering Preparation

This section describes the engineering preparation for changing a cell from non-
SFN mode to inter-BBU SFN mode, including information collection and
preparation of hardware, software, license files, security certificates, and data. It
also describes the data preparation mode and provides MML configuration script
examples.

Information Collection
Table 1-65 describes the information to be collected before changing a cell from
non-SFN mode to inter-BBU SFN mode.

Table 1-65 Information to be collected

Information Description

Cell information Basic information about the cell to be added, such as

RAT, Flag of Multi-RRU Cell, Sector equipment
number of SFN cell, and Mode of Multi-RRU Cell
TX/RX mode of the cell, for example, 4T4R
● In FDD, SFN cells support 1T1R, 2T2R, 2T4R, or 4T4R.
● In TDD, SFN cells support 4T4R, 8T8R, or both of
them.

Base station model Model of the base station to be changed, for example,
DBS3900

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 189

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

BBP model Model of the BBP, for example, LBBPc, LBBPd, or UBBP

RF module type Type of the RF module to be added, for example, MRRU

Topology If an RF module is to be added, collect information

about the CPRI topology for RF modules, for example,
the star topology.
● The SFN can be in the star or chain topology in FDD.
● The SFN must be in the star topology in TDD.

Sector information ● Sector equipment ID

● Reference signal power, indicating the reference
signal power of the RRU in the sector equipment

USU configuration Equipment information about the managed element

information (ME)/switch main processing and transmission unit
(SMPT)/universal cascaded interface unit (UCIU)/
universal interconnection extension unit (UCXU), and
transmission information about the operation and
maintenance channel (OMCH) and device IP address

Open datalink If the USU3900 is to be installed, collect the ODI

interface (ODI) information. Interconnected eNodeBs and USUs must be
information configured with equipment ODI information.

Port configuration If the USU3900 is to be installed, collect the port

configuration information. The interconnected ports on
the boards used for connecting eNodeBs and USUs must
be enabled.

Auxiliary eNodeB ID of the auxiliary eNodeB that indicates the cell

binding information resource allocation

Auxiliary eNodeB Information about the auxiliary eNodeB sector bound to

sector binding the cell served by the primary eNodeB, such as Sector
information equipment ID and Reference signal power

Auxiliary eNodeB The information is the same as that for adding common
standby cell FDD cells or adding common TDD cells. Set Cell
information Standby Mode to STANDBY.

eX2 If the USU3910 is to be installed, collect the eX2

configuration information. For details, see eX2 Self-
Management Feature Parameter Description.

Hardware Preparation
Table 1-66 describes the hardware to be prepared before changing a cell from
non-SFN mode to inter-BBU SFN mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 190

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-66 Hardware to be prepared

If... Then...

BBPs are insufficient Add BBPs as required.

RF resources are Add RF modules as required.

insufficient

Prepare the hardware listed in Table 1-67 before binding the cell to an auxiliary
eNodeB.

Table 1-67 Hardware to be prepared

If... Then...

Inter-BBU connection ● Add a USU3900 and related boards. For details about
is required the installation and cable connection, see USU3900
Installation Guide.
● Add a USU3910 and related boards. For details about
the installation and cable connection, see USU3910
Installation Guide.
The SFN mode is Replace the BBP with an LBBPd or UBBP. Replace the
required MPT with a UMPT.

Software Preparation
N/A

License File Preparation

Prepare a new license file if the license in use cannot meet requirements. Licenses
for SFN cells are applied in intra-BBU mode instead of inter-BBU mode. For details
about licenses, see Changing a Cell from Non-SFN Mode to Intra-BBU SFN
Mode > Engineering Preparation > "License File Preparation". Table 1-68
describes the license differences between the intra-BBU SFN and inter-BBU SFN.

Table 1-68 Licenses to be prepared

License Control Item Description

Inter-BBU SFN Controls inter-BBU SFN. This license must be applied for
in inter-BBU SFN networking.

Inter-BBU Adaptive Controls inter-BBU adaptive SFN/SDMA. This license

SFN/SDMA must be applied for in inter-BBU SFN networking.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 191

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Security Certificate Preparation

N/A

Data Preparation
Perform the following steps to prepare data:
Primary eNodeB:
Prerequisite: (Optional) If an LMPT is installed in the BBU in TDD, the LMPT must
be replaced. For details, see 1.7.6 Transmission Capacity Expansion from One
LMPT Board to LMPT + UMPT Boards (Mode 1) (TDD) (IPv4 Transmission
Only) and 1.7.7 Transmission Capacity Expansion from One LMPT Board to
LMPT + UMPT Boards (Mode 2) (TDD) (IPv4 Transmission Only). If a UMPT is
installed in the BBU, skip this operation.

Table 1-69 Data preparation (primary eNodeB)

SN Ope MO Configuration Reference
ratio
n

1 Deac Cell -
tivat
e

2 Dele Cell Remove the Cell MOs to remove

te redundant cells to be combined.

3 Dele eUCellSectorEqm Remove the eUCellSectorEqm MOs to

te remove the sector equipment of
redundant cells to be combined.

4 Add RU (using MML For details about parameter settings, see

commands)/BBP Base Station Cabinets and Subracks
(using the MAE- (Including the BBU Subrack)
Deployment) Configuration Feature Parameter
Description.
5 Modi RRUCHAIN For details about parameter settings, see
fy RF Unit and Topology Management
Feature Parameter Description.
6 Add RRU/RFU

7 Add SECTOREQM For details about parameter settings, see

Cell Management Feature Parameter
Description.
8 Modi Cell Set the Mode of Multi-RRU Cell
fy parameter to SFN and set the Sector
equipment number of SFN cell
parameter to the target value.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 192

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

9 Add eUCellSectorEqm For details about parameter settings, see

Cell Management Feature Parameter
Description.

10a Modi EQUIPMENT Modify the EQUIPMENT MO with Open

fy DU Interface ID configured as planned.

11a Modi CASCADEPORT Modify the CASCADEPORT MO with

fy Switch set to ON(On) based on the
cable connections.

12b Confi - Configure the transmission over the eX2

gure interface. For details, see eX2 Self-
the Management Feature Parameter
trans Description.
missi
on
over
the
eX2
inter
face

13 Add CellAuxEnbBind Set Slave site eNodeB ID for the

auxiliary eNodeB to which the cell is
bound.

a: Perform this operation only when the eNodeB is connected to a USU3900.

b: Perform this operation only when the eNodeB is connected to a USU3910.

USU3900:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 193

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-70 Data preparation (USU3900)

SN Ope MO Configuration Reference
ratio
n

1 Confi - For details about the software

gure configuration, see USU3900 Initial
USU Configuration Guide.
equi
pme
nt
and
trans
missi
on
data

2 Modi EQUIPMENT Modify the EQUIPMENT MO with Open

fy DU Interface ID configured as planned.

3 Modi CASCADEPORT Modify the CASCADEPORT MO with

fy Switch set to ON(On) based on the
cable connections.

Auxiliary eNodeB:

Table 1-71 Data preparation (auxiliary eNodeB)

SN Ope MO Configuration Reference
ratio
n

1 Deac Cell -
tivat
e

2 Dele Cell Remove the Cell MOs to remove

te redundant cells to be combined. The
standby cell can be retained.

3 Dele eUCellSectorEqm Remove the eUCellSectorEqm MOs to

te remove the sector equipment of
redundant cells to be combined. The
standby sector equipment can be
retained.

4 Add RU (using MML For details about parameter settings, see

commands)/BBP Base Station Cabinets and Subracks
(using the MAE- (Including the BBU Subrack)
Deployment) Configuration Feature Parameter
Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 194

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

5 Modi RRUCHAIN For details about parameter settings, see

fy RF Unit and Topology Management
Feature Parameter Description.
6 Add RRU/RFU

7a Modi EQUIPMENT Modify the EQUIPMENT MO with Open

fy DU Interface ID configured as planned.

8a Modi CASCADEPORT Modify the CASCADEPORT MO with

fy Switch set to ON(On) based on the
cable connections.

9b Confi - Configure the transmission over the eX2

gure interface. For details, see eX2 Self-
the Management Feature Parameter
trans Description.
missi
on
over
the
eX2
inter
face

10 Add SfnAuxResBind 1. Add the SfnAuxResBind MO.

Configure Main eNodeB ID and
Main eNodeB Local cell ID that are
bound to the sector equipment.
2. Add the SfnAuxResBind MO and
configure Main eNodeB Local cell
ID.

11 Add - For details about the data configuration,

stan see Adding an FDD Cell or Adding a
dby TDD Cell. Set Cell Standby Mode to
cells STANDBY.
for
the
auxil
iary
eNo
deB

12 Activ Cell -
ate

a: Perform this operation only when the eNodeB is connected to a USU3900.

b: Perform this operation only when the eNodeB is connected to a USU3910.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 195

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

● Using the batch configuration mode of the MAE-Deployment (eNodeB). For

details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the batch configuration mode of the MAE-Deployment (USU):
a. On the menu bar, choose Advanced > Data Management > Customize
Summary Data File. Select a summary data file mapping the version of
the USU to be configured and whose type is Bulk Configuration. The
batch configuration data file customization function is started.
b. On the menu bar, choose Advanced > Data Management > Export Auto
Deployment Data. The data export function is started to export the
existing NE data from the system to the customized summary file.
c. Fill in the summary file according to the data preparation procedure, and
then close the file.
d. On the menu bar, choose USU Application > Network Deployment >
Import Base Station Summary Data to import the data from the
summary data file into the system.
● Using the MAE-Deployment GUI (eNodeB): For details, see the interactive
operation guide Preparing Data in GUI Mode.
● Using the MAE-Deployment GUI (USU):
a. In the Main View navigation tree in the left pane of the planned data
area, select a USU.
b. Click the Search tab and enter the MO to be configured. The system
automatically searches for the MO.
c. Select the MO to be configured from search results and enter the
planned data in the right pane.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The sample scenario is described as follows:
● BBU 0 is configured for the primary eNodeB, and BBU 1 is configured for the
auxiliary eNodeB.
● Cells 0 to 2 served by BBU 0 and cells 0 and 1 served by BBU 1 are combined
to form an SFN cell.
● RRU 63 that is added to BBU 0 is combined to serve the SFN cell.

Figure 1-30 shows the topology before the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 196

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-30 Topology before the reconfiguration

Figure 1-31 shows the topology after the reconfiguration.

Figure 1-31 Topology after the reconfiguration

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 197

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If the currently used license file does not meet the requirements, reload a license
file. If the currently used license file meets the requirements, directly change the
cells from non-SFN mode to SFN mode.
Before the modification, ensure that the SrsCfgInd parameter is set to
BOOLEAN_TRUE.
/*Exporting the license file from the eNodeB and saving it to the E:\ftp folder*/
ULD LICENSE: MODE=IPV4, IP="192.169.2.16", USR="admin", PWD="admin", DIR="E:\ftp",
FN="LIC_LTE_ON.dat";
/*Importing a new license file*/
INS LICENSE: DIR="E:\luoyuan\eRAN3.0\B108", FN="LIC_LTE_ON.dat", FLG=NO, MODE=IPV4,
IP="192.169.2.16", USR="admin", PWD="admin";

Primary eNodeB:
/*Deactivating the cells*/
DEA CELL: LocalCellId=0;
DEA CELL: LocalCellId=1;
DEA CELL: LocalCellId=2;
/*Removing the cells*/
RMV CELL: LocalCellId=1;
RMV CELL: LocalCellId=2;
/*Adding a board in FDD*/ ADD BRD: SN=2, BT=LBBP, WM=FDD;
/*Adding a board in TDD*/ ADD BRD: SN=2, BT=LBBP, WM=TDD_ENHANCED;
/*Adding an RRU chain or ring*/
ADD RRUCHAIN: RCN=3, TT=CHAIN, HSRN=0, HSN=2, HPN=0;
/*Adding an RRU*/
ADD RRU: CN=0, SRN=63, SN=0, RCN=3, PS=0, RT=MRRU, RS=TDL, RN="rru3", RXNUM=4, TXNUM=4;
/*Adding a sector*/
ADD SECTOR:SECTORID=3,ANTNUM=4,ANT1CN=0,ANT1SRN=63,ANT1SN=0,
ANT1N=R0A,ANT2CN=0,ANT2SRN=63,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=63,ANT3SN=0,ANT3N
=R0C,ANT4CN=0,ANT4SRN=63,ANT4SN=0,ANT4N=R0D,CREATESECTOREQM=FALSE;
/*Adding sector equipment*/
ADD SECTOREQM:SECTOREQMID=3,SECTORID=3,ANTNUM=4,ANT1CN=0,
ANT1SRN=63,ANT1SN=0,ANT1N=R0A,ANTTYPE1=RXTX_MODE,ANT2CN=0,ANT2SRN=63,ANT2SN=0,ANT2N
=R0B,ANTTYPE2=RXTX_MODE,ANT3CN=0,ANT3SRN=63,ANT3SN=0,ANT3N=R0C,ANTTYPE3=RXTX_MODE,A
NT4CN=0,ANT4SRN=63,ANT4SN=0,ANT4N=R0D,ANTTYPE4=RXTX_MODE;
/*Adding the cell sector equipment by combining the three existing RRUs and the new RRU*/
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=1;
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=2;
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=3;
/*Setting the cell to an SFN cell with six sets of sector equipment*/
MOD CELL:MULTIRRUCELLFLAG=BOOLEAN_TRUE,MULTIRRUCELLMODE=SFN, SECTOREQMNUM=6;
/*Setting the switch for the interconnection port on the baseband processing unit when the USU3900 is
installed*/
SET CASCADEPORT: CN=0, SRN=0, SN=2, PN=6, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=6, SW=ON;
/*Setting the switch for the interconnection port on the main control board when the USU3900 is installed*/
SET CASCADEPORT: CN=0, SRN=0, SN=6, PN=8, SW=ON;
/*Adding the auxiliary eNodeB binding ID*/
ADD SFNCELLBIND: LocalCellId=0, eNodeBId=101;

Auxiliary eNodeB:
/*Deactivating the cells*/
DEA CELL: LocalCellId=0;
DEA CELL: LocalCellId=1;
/*Removing the cells*/
RMV CELL: LocalCellId=0;
RMV CELL: LocalCellId=1;
/*Setting the ID for inter-base-station connection when the USU3900 is installed*/
SET EQUIPMENT: ODIID=101;
/*Setting the switch for the interconnection port on the baseband processing unit when the USU3900 is
installed*/
SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=6, SW=ON;
/*Setting the switch for the interconnection port on the main control board when the USU3900 is installed*/
SET CASCADEPORT: CN=0, SRN=0, SN=6, PN=8, SW=ON;
/*Adding records about the secondary cell resource binding relationships*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 198

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD SFNAUXRESBIND:SECTOREQMID=0,ENODEBID=100,LOCALCELLID=0;
ADD SFNAUXRESBIND:SECTOREQMID=1,ENODEBID=100,LOCALCELLID=0;
/*Adding a standby cell in FDD*/ ADD CELL:LOCALCELLID=0,CELLNAME="0",FREQBAND=38,
ULEARFCNCFGIND=NOT_CFG,DLEARFCN=38000,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW
_N100,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCF
GIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFL
AG=BOOLEAN_FALSE,TXRXMODE=4T4R,EUCELLSTANDBYMODE=STANDBY;
/*Adding a standby cell in TDD*/ ADD CELL:LOCALCELLID=0,CELLNAME="0",FREQBAND=38,
ULEARFCNCFGIND=NOT_CFG,DLEARFCN=38000,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW
_N100,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPA
TTERNS=SSP7,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFG
IND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,TXRXMODE=4T4R,
EUCELLSTANDBYMODE=STANDBY;
/*Changing the active cell to a standby cell*/
MOD CELL:LOCALCELLID=0,EUCELLSTANDBYMODE=STANDBY;

:
/*Setting the eNodeB initial configuration to minimum configuration mode*/
SET LOCALIP: IP="172.21.241.134", MASK="255.255.255.0";
/*Configuring boards and RF modules*/
ADD BRD: CN=0, SRN=0, SN=3, BT=UCXU;
ADD BRD: CN=0, SRN=0, SN=2, BT=UCXU;
ADD BRD: CN=0, SRN=0, SN=5, BT=UCIU;
/*Configuring transmission parameters*/
ADD ETHPORT: SN=7, SBT=BASE_BOARD, PA=COPPER, SPEED=AUTO, DUPLEX=AUTO;
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=0, IP="8.10.10.60", MASK="255.255.255.255";
ADD IPRT: SN=7, SBT=BASE_BOARD, DSTIP="0.0.0.0", DSTMASK="0.0.0.0", RTTYPE=NEXTHOP,
NEXTHOP="80.3.101.1";
ADD OMCH:IP="8.10.10.65",MASK="255.255.255.255",PEERIP="172.166.1.251",
PEERMASK="255.255.255.255",BEAR=IPV4,BRT=NO,CHECKTYPE=NONE;
/*Configuring time information*/
SET TIMESRC: TIMESRC=NTP;
ADD NTPC: MODE=IPV4, IP="172.166.1.205", PORT=123, SYNCCYCLE=60, AUTHMODE=PLAIN;
SET MASTERNTPS: MODE=IPV4, IP="172.166.1.205";
SET TZ: ZONET=GMT+0800, DST=NO;
/*Setting the ID of ODI for inter-eNodeB connection*/
SET EQUIPMENT: ODIID=102;
/*Setting the switches for the interconnection ports on the UCXUs*/
SET CASCADEPORT: CN=0, SRN=0, SN=2, PN=0, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=0, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=3, PN=1, SW=ON;
/*Setting the switches for the interconnection ports on the UCIU*/
SET CASCADEPORT: CN=0, SRN=0, SN=5, PN=0, SW=ON;
SET CASCADEPORT: CN=0, SRN=0, SN=5, PN=1, SW=ON;

Primary eNodeB:
/*If the neighboring cell relationship is changed after the cell is changed to the SFN mode, update the
network planning of neighboring cells. To replan neighboring cells, see section "Changing the Neighboring
Cell Parameters."*/
/*If a neighboring cell PCI conflict occurs after the cell is changed to the SFN mode, update the PCI
planning. If the PCI of the local cell and that of the neighboring cell are the same, change the PCI of the
neighboring cell. For details, see "Changing the PCI of a Cell".*/
ACT CELL:LOCALCELLID=0;

1.5.18.3 Engineering Implementation

This section describes the engineering implementation for changing a cell from
non-SFN mode to inter-BBU SFN mode, including prerequisites, context, and
procedure.

Prerequisites
Related information, license files, and data are ready for changing a cell from non-
SFN mode to inter-BBU SFN mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 199

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Insert the BBP into the subrack. For details, see Maintaining the Case-
Structured BBU > Adding BBU Components > Replacing the LBBP or
Replacing the UBBP in BBU Hardware Maintenance Guide.
b. Install an RF module. For details about the operation, see the installation
guide for RRUs.
c. Install a CPRI optical fiber. For details, see Installing a CPRI Optical
Fiber in the installation guide of the corresponding RRU.
● Remote Operations

Using the MAE-Deployment:

NOTE

If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

a. To prevent unnecessary alarms from being generated during

reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
c. Import a new license file.
Run the INS LICENSE command.
Example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
d. Deactivate the cell. Run the DEA CELL command.
Example: DEA CELL: LocalCellId=0;
e. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
f. Activate the cell. Run the ACT CELL command.
Example: ACT CELL:LocalCellId=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 200

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

g. After data reconfiguration is complete, set the eNodeB maintenance

mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

Using MML commands:

a. To prevent unnecessary alarms from being generated during

reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Run the following commands to back up and export the configuration
file. The configuration file can be used to roll back the base station
configurations to the original state, if the reconfiguration fails.
i. To back up the configuration file, run the BKP CFGFILE command.
ii. To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
d. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.5.18.4 Engineering Verification

This section describes how to verify the reconfiguration for changing a cell from
non-SFN mode to inter-BBU SFN mode.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command to verify that the value of Cell instance state is
Normal and that of Work Status of all RRUs is Normal.

If the value of Cell instance state is Uninstall, check the cell configuration, cell
reference signal power configuration, or hardware based on the value of Reason
for latest state change in the command output.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 201

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If the value of Word Status is not Normal, rectify the fault based on the error
message.

----End

1.5.18.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Context
The cell capacity mode remains unchanged after the SFN cell is reconstructed. To
use a different cell capacity mode, change the value of CellCapacityMode
parameter.

Procedure
Step 1 Restore the configuration data.
● Using the MAE-Deployment:
The MAE-Deployment generates configuration rollback scripts when exporting
incremental configuration scripts. Configuration rollback scripts simplify data
rollback on the live network.
a. On the menu bar, choose Area Management > Planned Area > Export
Incremental Scripts to start the wizard of exporting scripts. Then, select
Launch Script Executor in the wizard to activate exported scripts for
data to take effect on the live network. For detailed operations, see
section Exporting Incremental Scripts from a Planned Data Area in the
MAE-Access online help.
b. Click the Summary tab in the Script Executor window.
c. Select a project whose data needs to be rolled back and right-click it. For
detailed operations, see section Fallback Based on Configuration Steps
in the MAE-Access online help.
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 202

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license is updated.
Run the INS LICENSE command. Example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="user", PWD="****";
Step 3 Restore the cable connections.
Step 4 Verify that engineering rollback is successful according to instructions in 1.5.18.4
Engineering Verification.

----End

1.5.19 Binding Baseband Equipment

This section describes how to plan the baseband resource pool and bind baseband
equipment for a cell.

1.5.19.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for binding baseband equipment for
a cell.

Application Scenario
● Cells with different subframe configurations, uplink and downlink cyclic prefix
(CP) configurations, or frame offsets must be established on different BBPs.
For example, 4T4R and 2T2R cells each with 20 MHz bandwidth are set up in
slot 2 of the same BBU, as shown in Figure 1-32. The 4T4R cells are
configured with normal CP and the 2T2R cells are configured with extended
CP. If all 2T2R cells are activated first, none of the 4T4R cells can be activated.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 203

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-32 Typical scenario

In this scenario, consider the following schemes:

– If all 2T2R cells are set up in slot 1, all 4T4R cells can be activated.
– If all 2T2R cells are still set up in slot 2 and all 4T4R cells are set up in
slot 1 by using the backplane, one 4T4R cell cannot be activated because
the backplane transmission resources between slots 1 and 2 are limited.
– If some 2T2R cells are still set up in slot 2 while other 2T2R cells are set
up in slot 1, none of the 4T4R cells can be activated because cells with
different types of uplink and downlink CPs cannot be set up on the same
BBP.
NOTE

For details about the backplane transmission resources between BBPs, see CPRI Sharing
Feature Parameter Description.
● The backplane supports a maximum of 10 channels for single-carrier data
transmission between two BBPs. If cells require more than 10 channels,
contention for baseband resources occurs and some cells cannot be activated.
To prevent this problem, all cells must be bound to baseband equipment.
● In low speed scenarios, if 2T2R cells and 4T4R cells are served by the same
UBBP, the cells must be bound to baseband equipment.
● If a base station has more than two BBPs, among which there are LBBPd
boards, all cells in low-speed indoor distributed scenarios must be bound to
baseband equipment on the same BBP.
● In indoor distributed system scenarios, the MultiRruCellMode parameter
must be set to CELL_COMBINATION(Cell Combination) for all cells even if
only one RRU is deployed.

Reconfiguration Impact
When a cell bound to baseband equipment is activated, resources are selected for
it only from the bound baseband equipment. If a cell is not bound to baseband
equipment, resources on the directly-connected BBP are preferentially selected. If
the directly-connected BBP is unavailable, another BBP is automatically allocated.
You are advised to bind all cells with baseband equipment. In this way, cells not

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 204

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

bound to baseband equipment will not occupy baseband resources allocated for
cells with baseband equipment bound.

Reconfiguration Scheme
● Add baseband equipment.
● Add sector equipment and bind cells with baseband equipment. If
reconfiguration of existing sector equipment is required, reconfigure the
sector equipment and bind cells with baseband equipment.

Topology Change
N/A

1.5.19.2 Engineering Preparation

This section describes the engineering preparation for binding baseband
equipment for a cell, including information collection and preparation of
hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-72 describes the information to be collected before binding baseband
equipment for a cell.

Table 1-72 Information to be collected

Information Description

Cell information Cell ID and information about the cell sector equipment
group

Information about Baseband equipment ID and BBP slot number

baseband equipment

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 205

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation
The following table lists the data to be prepared.

Table 1-73 Data preparation for binding baseband equipment for a cell

SN Ope MO Configuration Reference

ratio
n

1 Add BASEBANDEQM One BBP can be added to only one piece

of baseband equipment.

2 Add eUCellSectorEqm/ If sector equipment already exists,

EuPrbSectorEqm reconfigure existing sector equipment
directly. For details about the
recommended parameter settings, see
Cell Management Feature Parameter
Description. Bind the eUCellSectorEqm/
EuPrbSectorEqm and BASEBANDEQM
MOs to the cell to be planned based on
the target networking.

3 Activ Cell -
ate

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Binding Baseband Equipment"). For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

/*Adding baseband equipment*/
ADD BASEBANDEQM:BASEBANDEQMID=1,BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL,SN1=1;
ADD BASEBANDEQM:BASEBANDEQMID=2,BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL,SN1=2;
/*Adding sector equipment for cells*/
ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=1, BASEBANDEQMID=1;
ADD EUCELLSECTOREQM:LOCALCELLID=2,SECTOREQMID=2, BASEBANDEQMID=2;
/*Reconfiguring sector equipment for the cells*/
MOD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=1,BASEBANDEQMID=1;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 206

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

MOD EUCELLSECTOREQM:LOCALCELLID=2,SECTOREQMID=2,BASEBANDEQMID=1;
/*Activating the cells*/
ACT CELL: LocalCellId=1;
ACT CELL: LocalCellId=2;

1.5.19.3 Engineering Implementation

This section describes the engineering implementation for binding baseband
equipment for a cell, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
a. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
c. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.5.19.4 Engineering Verification

This section describes how to verify the reconfiguration for binding baseband
equipment for a cell.

Procedure
Step 1 Run the DSP CELL command to check whether the cabinet, subrack, and slot
where the cell is configured are the same as planned.
Step 2 Run the LST EUCELLSECTOREQM command to check whether Sector equipment
ID is the same as planned.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 207

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.5.19.5 Engineering Rollback

If the reconfiguration fails, it can be rolled back to the original state before the
reconfiguration.

Procedure
Step 1 Restore the configuration data.
● Using the MAE-Deployment:
The MAE-Deployment generates configuration rollback scripts when exporting
incremental configuration scripts. Configuration rollback scripts simplify data
rollback on the live network.
a. On the menu bar, choose Area Management > Planned Area > Export
Incremental Scripts to start the wizard of exporting scripts. Then, select
Launch Script Executor in the wizard to activate exported scripts for
data to take effect on the live network. For detailed operations, see
section Exporting Incremental Scripts from a Planned Data Area in the
MAE-Access online help.
b. Click the Summary tab in the Script Executor window.
c. Select a project whose data needs to be rolled back and right-click it. For
detailed operations, see section Fallback Based on Configuration Steps
in the MAE-Access online help.
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 208

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 Verify that engineering rollback is successful according to instructions in

Engineering Verification.

----End

1.5.20 Enabling Automatic Binding of Baseband Equipment

This section describes how to enable automatic baseband equipment binding for a
cell.

1.5.20.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for enabling automatic baseband
equipment binding for a cell.

Application Scenario
In a networking scenario where a single BBU is connected to different RRUs and
antennas and serves multiple cell types, a cell may be established on different
BBPs before and after board reset or software upgrade, resulting in different cell
performances. To prevent this problem, bind baseband equipment for a cell. It is
recommended that automatic baseband equipment binding be enabled to simplify
the baseband equipment binding operation.

NOTE

● You can determine whether the baseband equipment can be automatically bound or must
be manually bound to a cell by querying the value of the Auto Config Flag parameter.
● The baseband equipment that has been manually bound to a cell is not affected after
automatic baseband equipment binding is performed.

Reconfiguration Impact
When a cell bound to baseband equipment is activated, resources are selected for
it preferentially from the bound baseband equipment. If the activation repetitively
fails within a period (10 minutes by default), resources are selected for it from
other baseband equipment.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 209

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Disable automatic baseband equipment binding before site deployment, capacity

expansion, or site reconstruction. In this situation, the eNodeB preferentially uses
the BBP on which a cell is established as the baseband equipment for the cell.
After reconfiguration for site deployment, capacity expansion, or site
reconstruction, it is recommended that automatic baseband equipment binding be
enabled. The eNodeB automatically binds the cell to baseband equipment.

Reconfiguration Scheme
Figure 1-33 shows the reconfiguration procedure for enabling automatic binding
of baseband equipment for a cell.

Figure 1-33 Procedure for enabling automatic binding of baseband equipment for
a cell

NOTE

● Automatic baseband equipment binding enables binding of baseband resources specified by

the EuSectorEqmGroup, EuCellSectorEqm, and SfnAuxResBind MOs.
● During cell activation, if the BBP is not added to baseband equipment, automatic baseband
equipment binding for the cell does not take effect.

Topology Change
N/A

1.5.20.2 Engineering Preparation

This section describes the engineering preparation for enabling automatic binding
of baseband equipment for a cell, including information collection and preparation

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 210

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

of hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-74 describes the information to be collected before enabling automatic
binding of baseband equipment.

Table 1-74 Information to be collected

Information Description

Cell information Includes cell ID and information about the cell sector
equipment group.

Information about Includes baseband equipment ID and BBP slot number.

baseband equipment

Information about Includes the information about the BBP resource

the BBP resource automatic configuration switch.
automatic
configuration switch

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-75 Data preparation for enabling automatic baseband equipment binding

SN Ope MO Configuration Reference

ratio
n

1 Add BASEBANDEQM A BBP must be added to only one piece

of baseband equipment.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 211

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

2 Add eUCellSectorEqm If sector equipment already exists,

reconfigure existing sector equipment
directly. For details about the
recommended parameter settings, see
Cell Management Feature Parameter
Description. Bind the eUCellSectorEqm/
EuPrbSectorEqm and BASEBANDEQM
MOs to the cell to be planned based on
the target networking.

3 Activ Cell -
ate

4 Modi eNodeBResModeAlgo Set the BbpResAutoConfigSw

fy parameter to ON(ON).

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Enabling Automatic Binding of Baseband
Equipment"). For details, see the interactive operation guide 1.11.2 Using the
Batch Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

/*Adding baseband equipment (BBPs must be added to baseband equipment)*/
ADD BASEBANDEQM:BASEBANDEQMID=2,BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL,SN1=2;
/*Modifying the configuration of sector equipment of a cell with AutoCfgFlag set to AUTO_MODE_CFG*/
MOD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, AutoCfgFlag=AUTO_MODE_CFG;
/*Activating the cell*/
ACT CELL: LocalCellId=0;
/*Enabling automatic configuration of baseband resources*/
MOD ENODEBRESMODEALGO: BbpResAutoConfigSw=ON;

1.5.20.3 Engineering Implementation

This section describes the engineering implementation for enabling automatic
binding of baseband equipment for a cell, including prerequisites, context, and
procedure.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 212

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations
– Using the MAE-Deployment:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
iii. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Run the following commands to back up and export the
configuration file. The configuration file can be used to roll back the
base station configurations to the original state, if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 213

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.5.20.4 Engineering Verification

This section describes how to verify the reconfiguration for enabling automatic
binding of baseband equipment for a cell.

Procedure
Step 1 Run the DSP CELL command to check whether the cabinet, subrack, and slot
where the cell is configured are the same as planned.
Step 2 After the BbpResAutoConfigSw parameter is set to ON(ON), baseband
equipment will be automatically bound within 5 minutes. Therefore, 5 minutes
after automatic baseband equipment binding is enabled, run the LST
EUCELLSECTOREQM command to check whether Sector equipment ID is the
same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
----End

1.5.20.5 Engineering Rollback

If the reconfiguration fails, it can be rolled back to the original state before the
reconfiguration.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 214

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",

USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that engineering rollback is successful according to instructions in

Engineering Verification.

----End

1.5.21 Changing the Baseband Equipment for a Cell

This section describes how to plan the baseband resource pool and change the
baseband equipment for a cell.

1.5.21.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the baseband
equipment for a cell.

Application Scenario
● Cells with different subframe configurations, uplink and downlink cyclic prefix
(CP) configurations, or frame offsets must be established on different BBPs.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 215

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For example, 4T4R and 2T2R cells each with 20 MHz bandwidth are set up in
slot 2 of the same BBU, as shown in Figure 1-34. The 4T4R cells are
configured with normal CP and the 2T2R cells are configured with extended
CP. If all 2T2R cells are activated first, none of the 4T4R cells can be activated.

Figure 1-34 Typical scenario

In this scenario, consider the following schemes:

– If all 2T2R cells are set up in slot 1, all 4T4R cells can be activated.
– If all 2T2R cells are still set up in slot 2 and all 4T4R cells are set up in
slot 1 by using the backplane, one 4T4R cell cannot be activated because
the backplane transmission resources between slots 1 and 2 are limited.
– If some 2T2R cells are still set up in slot 2 while other 2T2R cells are set
up in slot 1, none of the 4T4R cells can be activated because cells with
different types of uplink and downlink CPs cannot be set up on the same
BBP.
NOTE

For details about the backplane transmission resources between BBPs, see CPRI Sharing
Feature Parameter Description.
● The backplane supports a maximum of 10 channels for single-carrier data
transmission between two BBPs. If cells require more than 10 channels,
contention for baseband resources occurs and some cells cannot be activated.
To prevent this problem, all cells must be bound to baseband equipment.
● In low speed scenarios, if 2T2R cells and 4T4R cells are served by the same
UBBP, the cells must be bound to baseband equipment.
● If a base station has more than two BBPs, among which there are LBBPd
boards, all cells in low-speed indoor distributed scenarios must be bound to
baseband equipment on the same BBP.
● In indoor distributed system scenarios, the MultiRruCellMode parameter
must be set to CELL_COMBINATION(Cell Combination) for all cells even if
only one RRU is deployed.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 216

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Impact
When a cell bound to baseband equipment is activated, resources are selected for
it only from the bound baseband equipment. If a cell is not bound to baseband
equipment, resources on the directly-connected BBP are preferentially selected. If
the directly-connected BBP is unavailable, another BBP is automatically allocated.
You are advised to bind all cells with baseband equipment. In this way, cells not
bound to baseband equipment will not occupy baseband resources allocated for
cells with baseband equipment bound.
When the baseband equipment of a cell is changed, the cell will be reestablished
to make the reconfiguration take effect.

Reconfiguration Scheme

If reconfiguration of existing sector equipment is required, reconfigure the sector

equipment, during which cells are bound to baseband equipment.

Topology Change
Figure 1-35 shows the topologies before and after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 217

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-35 Topologies before and after the reconfiguration

1.5.21.2 Engineering Preparation

This section describes the engineering preparation for changing the baseband
equipment for a cell, including information collection and preparation of
hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 218

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Collection
Table 1-76 describes the information to be collected before changing the
baseband equipment for a cell.

Table 1-76 Information to be collected

Information Description

Cell information Includes the cell ID and information about the cell
sector equipment group.

Information about Includes the baseband equipment ID and BBP slot

baseband equipment number.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-77 Data preparation for binding the baseband equipment for a cell

SN Ope MO Configuration Reference

ratio
n

1 Add eUCellSectorEqm/ If sector equipment already exists,

EuPrbSectorEqm reconfigure existing sector equipment
directly. For details about the
recommended parameter settings, see
Cell Management Feature Parameter
Description. Bind the eUCellSectorEqm/
EuPrbSectorEqm and BASEBANDEQM
MOs to the cell to be planned based on
the target networking.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 219

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Binding Baseband Equipment"). For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

/*Reconfiguring the baseband equipment of sector equipment for cells*/
MOD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=1,BASEBANDEQMID=1;
MOD EUCELLSECTOREQM:LOCALCELLID=2,SECTOREQMID=2,BASEBANDEQMID=1;

1.5.21.3 Engineering Implementation

This section describes the engineering implementation for changing the baseband
equipment for a cell, including prerequisites, context, and procedure.

Prerequisites
Related information and data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
a. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion mode.
For detailed operations, see Setting the eNodeB Maintenance Mode to
Expand Status.
b. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 220

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

c. After data reconfiguration is complete, set the eNodeB maintenance

mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.5.21.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the baseband
equipment for a cell.

Procedure
Step 1 Run the DSP CELL command to check whether the cabinet, subrack, and slot
where the cell is configured are the same as planned.
Step 2 Run the LST EUCELLSECTOREQM command to check whether Sector equipment
ID is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.5.21.5 Engineering Rollback

If the reconfiguration fails, the eNodeB configuration can be rolled back to the
original state before the reconfiguration.

Procedure
Step 1 Restore the configuration data.
● Using the MAE-Deployment:
The MAE-Deployment generates configuration rollback scripts when exporting
incremental configuration scripts. Configuration rollback scripts simplify data
rollback on the live network.
a. On the menu bar, choose Area Management > Planned Area > Export
Incremental Scripts to start the wizard of exporting scripts. Then, select
Launch Script Executor in the wizard to activate exported scripts for
data to take effect on the live network. For detailed operations, see
section Exporting Incremental Scripts from a Planned Data Area in the
MAE-Access online help.
b. Click the Summary tab in the Script Executor window.
c. Select a project whose data needs to be rolled back and right-click it. For
detailed operations, see section Fallback Based on Configuration Steps
in the MAE-Access online help.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 221

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 Verify that engineering rollback is successful according to instructions in

Engineering Verification.

----End

1.5.22 Changing the Uplink-Downlink Subframe Configuration

(TDD)
This section describes how to change the uplink-downlink subframe configuration.

1.5.22.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the uplink-downlink
subframe configuration.

Application Scenario
The requirements for data rates in the uplink and downlink vary in different
scenarios.

Reconfiguration Impact
After the uplink-downlink subframe configuration is changed, service drops occur
and the previous preamble format may not match the new uplink-downlink
subframe configuration, resulting in a cell setup failure. To solve these problems,
you must change the value of Preamble format in the Cell MO.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 222

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If the new uplink-downlink subframe configuration is different from that of an

intra-frequency neighboring cell under a neighboring eNodeB, network
interference increases. In this case, change the uplink-downlink subframe
configuration of the intra-frequency neighboring cell accordingly.

Reconfiguration Scheme
Changing the uplink-downlink subframe configuration will cause cell deactivation.
You are advised to manually deactivate the cell before the reconfiguration and
then activate the cell manually. Figure 1-36 shows the procedure for changing the
uplink-downlink subframe configuration.

Figure 1-36 Procedure for changing the uplink-downlink subframe configuration

Topology Change
N/A

1.5.22.2 Engineering Preparation

This section describes the engineering preparation for changing the uplink-
downlink subframe configuration, including information collection and preparation
of hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-78 describes the information to be collected before changing the uplink-
downlink subframe configuration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 223

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-78 Information to be collected

Information Description

Cell information Includes the RAT, uplink-downlink subframe

configuration, and special subframe configuration.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

If the currently used license file does not meet the requirements, prepare a new
license file.

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-79 Data preparation for changing the uplink-downlink subframe

configuration (TDD)

SN Ope MO Configuration Reference

ratio
n

1 Deac Cell -
tivat
e

2 Modi Cell Change the value of Subframe

fy assignment to the target value.

3 Activ Cell -
ate

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 224

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

● Using the batch configuration mode of the MAE-Deployment. For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

If the currently used license file does not meet the requirements, reload a license
file. If the currently used license file meets the requirements, directly change the
uplink-downlink subframe configuration.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="user", PWD="****", DIR="ftproot/",
FN="LIC_LTE_ON.dat";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="user", PWD="****";
/*Deactivating the cell*/
DEA CELL: LocalCellId=0;
/*Changing the uplink-downlink subframe configuration to SA5*/
MOD CELL: LocalCellId=0, FddTddInd=CELL_TDD, SubframeAssignment=SA5,
SpecialSubframePatterns=SSP7, EUCELLSTANDBYMODE=ACTIVE;
/*Activating the cell*/
ACT CELL: LocalCellId=0;

1.5.22.3 Engineering Implementation

This section describes the engineering implementation for changing the uplink-
downlink subframe configuration, including prerequisites, context, and procedure.

Prerequisites
Related information, license files, and data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 225

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Using the MAE-Deployment:

i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For details, see Setting the eNodeB Maintenance Mode to Expand
Status.
ii. If the currently used license file does not meet the requirements,
reload a license file. If the currently used license file meets the
requirements, go to 3.
1) Back up the currently used license file by running the ULD
LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="user", PWD="****", DIR="ftproot/",
FN="LIC_LTE_ON.dat";
2) Import the new license file by running the INS LICENSE
command.
Example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="user", PWD="****";
iii. Deliver the data prepared in Data Preparation to the eNodeB and
activate the data on the eNodeB. For details, see the interactive
operation guide Delivering Data to Base Stations and Activating
the Data.
iv. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
ii. Use the MAE-Access to deliver the configuration scripts prepared in
Data Preparation to the base station and activate the scripts on the
base station. For details, see 1.3.3 Running MML Commands on the
MAE-Access.
NOTE

If the currently used license file does not meet the requirements, reload a license
file. You can import or export the license file for only one NE at a time.
iii. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 226

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.22.4 Engineering Verification

This section describes how to verify a cell uplink-downlink subframe configuration
change.

Procedure
Step 1 Run the DSP CELL command to check whether the value of Cell instance state is
Normal for the cell.
If the value of Cell instance state is Uninstall, check the cell configuration, cell
reference signal power configuration, or hardware based on the value of Reason
for latest state change in the command output.
Step 2 Run the LST CELL command to check whether the value of Subframe assignment
is the same as planned.
Step 3 Verify that ALM-29240 Cell Unavailable is not reported.

----End

1.5.22.5 Engineering Rollback

If the reconfiguration fails, it can be rolled back to the original state before the
reconfiguration.

Procedure
Step 1 Roll back the reconfiguration data.
● Using the MAE-Deployment: For detailed operations, see the interactive
operation guide Rolling Back Configuration Data.
● Using MML commands:
a. Run the DLD CFGFILE command to download the original configuration
file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="",
ENCRYPTMODE=UNENCRYPTED;
b. Run the ACT CFGFILE command to activate the original configuration
file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Verify that engineering rollback is successful according to instructions in 1.5.22.4
Engineering Verification.

----End

1.5.23 Changing the Special Subframe Configuration (TDD)

This section describes how to change the special subframe configuration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 227

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.5.23.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the special subframe
configuration.

Application Scenario
The requirements for the maximum coverage radius of a cell vary in different
scenarios.

Reconfiguration Impact
After the special subframe configuration is changed, service drops occur and the
previous uplink and downlink cyclic prefix lengths may not match the new special
subframe configuration, resulting in a cell setup failure. To solve these problems,
you must change the uplink and downlink cyclic prefix lengths in the Cell MO.

Reconfiguration Scheme
Changing the special subframe configuration will cause cell deactivation. You are
advised to manually deactivate the cell before the reconfiguration and then
activate the cell manually. Figure 1-37 shows the procedure for changing the
special subframe configuration.

Figure 1-37 Procedure for changing the special subframe configuration

Topology Change
N/A

1.5.23.2 Engineering Preparation

This section describes the engineering preparation for changing the special
subframe configuration, including information collection and preparation of

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 228

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-80 describes the information to be collected before changing the special
subframe configuration.

Table 1-80 Information to be collected

Information Description

Cell information Includes the RAT, uplink-downlink subframe

configuration, and special subframe configuration.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

If the currently used license file does not meet the requirements, prepare a new
license file.

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-81 Data preparation for changing the special subframe configuration
(TDD)

SN Ope MO Configuration Reference

ratio
n

1 Deac Cell -
tivat
e

2 Modi Cell Change the value of Special subframe

fy patterns to the target value.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 229

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

3 Activ Cell -
ate

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

● Using the batch configuration mode of the MAE-Deployment. For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

If the currently used license file does not meet the requirements, reload a license
file. If the currently used license file meets the requirements, directly change the
special subframe configuration.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="user", PWD="****", DIR="ftproot/",
FN="LIC_LTE_ON.dat";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="user", PWD="****";
/*Deactivating the cell*/
DEA CELL: LocalCellId=0;
/*Changing the special subframe configuration to SSP4*/
MOD CELL: LocalCellId=0, FddTddInd=CELL_TDD, SubframeAssignment=SA1,
SpecialSubframePatterns=SSP4, EUCELLSTANDBYMODE=ACTIVE;
/*Activating the cell*/
ACT CELL: LocalCellId=0;

1.5.23.3 Engineering Implementation

This section describes the engineering implementation for changing the special
subframe configuration, including prerequisites, context, and procedure.

Prerequisites
Related information, license files, and data are ready.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 230

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
– Using the MAE-Deployment:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For details, see Setting the eNodeB Maintenance Mode to Expand
Status.
ii. If the currently used license file does not meet the requirements,
reload a license file. If the currently used license file meets the
requirements, go to 3.
1) Back up the currently used license file by running the ULD
LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="user", PWD="****", DIR="ftproot/",
FN="LIC_LTE_ON.dat";
2) Import the new license file by running the INS LICENSE
command.
Example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="user", PWD="****";
iii. Deliver the data prepared in Data Preparation to the eNodeB and
activate the data on the eNodeB. For details, see the interactive
operation guide Delivering Data to Base Stations and Activating
the Data.
iv. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
ii. Use the MAE-Access to deliver the configuration scripts prepared in
Data Preparation to the base station and activate the scripts on the
base station. For details, see 1.3.3 Running MML Commands on the
MAE-Access.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 231

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the currently used license file does not meet the requirements, reload a license
file. You can import or export the license file for only one NE at a time.
iii. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.5.23.4 Engineering Verification

This section describes how to verify the special subframe configuration change.

Procedure
Step 1 Run the DSP CELL command to check whether the value of Cell instance state is
Normal for the cell.
If the value of Cell instance state is Uninstall, check the cell configuration, cell
reference signal power configuration, or hardware based on the value of Reason
for latest state change in the command output.
Step 2 Run the LST CELL command to check whether the value of Special subframe
patterns is the same as planned.
Step 3 Verify that ALM-29240 Cell Unavailable is not reported.

----End

1.5.23.5 Engineering Rollback

If the reconfiguration fails, it can be rolled back to the original state before the
reconfiguration.

Procedure
Step 1 Roll back the reconfiguration data.
● Using the MAE-Deployment: For detailed operations, see the interactive
operation guide Rolling Back Configuration Data.
● Using MML commands:
a. Run the DLD CFGFILE command to download the original configuration
file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="",
ENCRYPTMODE=UNENCRYPTED;
b. Run the ACT CFGFILE command to activate the original configuration
file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 232

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Run the INS LICENSE command.

Step 3 Verify that engineering rollback is successful according to instructions in 1.5.23.4
Engineering Verification.

----End

1.5.24 Adjusting Association Relationships Between Cells and

RF Modules
This section describes how to adjust association relationships between cells and RF
modules.

1.5.24.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adjusting association
relationships between cells and RF modules.

Application Scenario
The binding relationships between cells and sector equipment are inconsistent
with the planned ones.

Reconfiguration Impact
Cell services become unavailable during the adjustment of association
relationships between cells and RF modules.

Reconfiguration Scheme
Figure 1-38 shows the procedure for adjusting association relationships between
cells and RF modules.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 233

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-38 Procedure for adjusting association relationships between cells and RF
modules

Topology Change
N/A

1.5.24.2 Engineering Preparation

This section describes the engineering preparation for adjusting association
relationships between cells and RF modules, including information collection and
preparation of hardware, software, license files, security certificates, and data. It
also describes the data preparation mode and provides MML configuration script
examples.

Information Collection
Table 1-82 describes the information to be collected for data preparation.

Table 1-82 Information to be collected

Information Description

Sector information Includes the cabinet number, subrack number, slot

number, and channel number of a sector antenna.

Sector equipment Includes the cabinet number, subrack number, slot

information number, channel number, and RX/TX mode of sector
equipment.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 234

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Cell sector equipment Includes the ID of the cell sector equipment.

information

Cell information Basic information about the cell to be added, for

example, the bandwidth, EARFCN, duplex mode,
reference signal power, and TX/RX mode of the cell

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Table 1-83 Data preparation for adjusting association relationships between cells
and RF modules
SN Ope MO Configuration Reference
ratio
n

1 Deac Cell —
tivat
e

2 Dele eUCellSectorEqm Delete the existing binding relationships

te between cells and sector equipment.
For details about parameter settings, see
Cell Management Feature Parameter
Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 235

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

3 Add eUCellSectorEqm Add binding relationships between cells

and sector equipment.
For details about parameter settings, see
Cell Management Feature Parameter
Description.
4 Activ Cell —
ate

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Adding an FDD Cell"). For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

This section describes the MML command script for data preparation by using the
adjustment of association relationships between cells 0 and 1 and RF modules as
an example.
NOTE

If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="*****", DIR="ftproot/",
FN="LIC_LTE_ON.xml";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 236

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="*************";
/*Deactivating the cells*/
DEA CELL: LocalCellId=0;
DEA CELL: LocalCellId=1;
/*Deleting the existing binding relationships between cells and sector equipment*/
RMV EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=1;
RMV EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=0;
/*Adding binding relationships between cells and sector equipment*/
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0;
ADD EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=1;
/*Activating the cells*/
ACT CELL: LocalCellId=0;
ACT CELL: LocalCellId=1;

1.5.24.3 Engineering Implementation

This section describes the engineering implementation for adjusting the
association relationships between cells and RF modules, including prerequisites,
context, and procedure.

Prerequisites
Related information, hardware, software, and configuration data are ready, and
the license file is available in the save path on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations
NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 237

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",

USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deactivate the cell.
Run the DEA CELL command.
Example: DEA CELL: LocalCellId=0; DEA CELL: LocalCellId=1;
v. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
vi. Activate the cell.
Run the ACT CELL command.
Example: ACT CELL: LocalCellId=0; ACT CELL: LocalCell Id=1;
vii. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Deactivate the cell.
Run the DEA CELL command.
Example: DEA CELL: LocalCellId=0; DEA CELL: LocalCellId=1;
iv. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
v. Activate the cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 238

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Run the ACT CELL command.

Example: ACT CELL: LocalCellId=0; ACT CELL: LocalCell Id=1;
vi. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.5.24.4 Engineering Verification

This section describes how to verify that the adjustment of association
relationships between cells and RF modules is successful.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

----End

1.5.24.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 239

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful according to instructions in 1.5.24.4

Engineering Verification.

----End

1.5.25 Deleting a Cell

This section describes how to delete a cell.

1.5.25.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for deleting a cell.

Application Scenario
A cell is not required any more.

Reconfiguration Impact
When a cell is deleted, the services carried by the cell are unavailable.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 240

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme

Figure 1-39 Procedure for deleting a cell

Topology Change
Use deleting a BBP and an RRU as an example. Figure 1-40 shows the topologies
before and after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 241

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-40 Topologies before and after the reconfiguration

1.5.25.2 Engineering Preparation

This section describes the engineering preparation for deleting a cell, including
information collection and preparation of hardware, software, license files, security
certificates, and data. It also describes the data preparation mode and provides
MML configuration script examples.

Information Collection
Table 1-84 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 242

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-84 Information to be collected

Information Description

Cell information Includes the local cell ID of the cell to be deleted.

Neighboring cell Includes information about intra-frequency, inter-

information frequency, and inter-RAT neighboring cells.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Table 1-85 Data preparation for deleting a cell

SN Ope MO Configuration Reference

ratio
n

1 Dele Cell ● Delete the local cell ID.

te ● Delete neighboring cell data of the
given cell.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. MAE-Deployment-based data preparation is recommended to delete
cells under a base station or multiple base stations in batches. The two data
preparation modes are described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 243

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the MAE-Deployment to delete cells in batches:
a. On the menu bar, choose LTE Application > Network Adjustment >
Delete Cells in Batches. A dialog box is displayed for you to select cells.
b. Select the cells to be deleted.
c. Click Delete. In the displayed dialog box for you to confirm the deletion,
click OK.
d. The system starts to delete cells.
e. You can view the result in the task information list.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The following provides examples for deleting a cell.
/*Deleting all neighboring cell data of a cell*/
RMV CELLNRT: LocalCellId=0;
/*Deleting the cell*/
RMV CELL: LocalCellId=0;

1.5.25.3 Engineering Implementation

This section describes the engineering implementation for deleting a cell,
including prerequisites, context, and procedure.

Prerequisites
Information and configuration data for deleting a cell are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
– Using the MAE-Deployment:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 244

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the LST GLOBALPROCSWITCH command to query the values of
the following parameters: The Switch of X2 setup by SON, Peer
Request Based X2 Delete Switch, X2 SON Delete Switch, Interface
Setup Policy Switch, The Timer of X2 delete by SON, and X2-
based Neighboring Cell Configuration Update Switch.
○ Skip this step if the The Timer of X2 delete by SON parameter
is 0, the LTE_NR_X2_SON_SETUP_SW option of the Interface
Setup Policy Switch parameter is deselected, and the options of
all the other preceding parameters are deselected.
○ If The Timer of X2 delete by SON parameter is not 0, the
LTE_NR_X2_SON_SETUP_SW option of the Interface Setup
Policy Switch parameter is selected, or the options of all the
other preceding parameters are selected, run the MOD
GLOBALPROCSWITCH command to set the The Timer of X2
delete by SON parameter to 0 and deselect all these options.
Example: MOD GLOBALPROCSWITCH:
X2SonSetupSwitch=OFF, X2SonDeleteTimer=0,
PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2US
AGE_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-
0,
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_N
CELL_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD_FREQ_CFG_SW
-0&UPT_EXTERNALCELLBAND_CFG_SW-0,
InterfaceSetupPolicySw=X2_SON_INTER_OP_SETUP_FBD_SW-
1&LTE_NR_X2_SON_SETUP_SW-0;
iii. Run the LST ENODEBALGOSWITCH command to check whether the
options of ANR algorithm switch are selected.
○ If all the options of this parameter are deselected, skip this step.
○ If any option is selected, run the MOD ENODEBALGOSWITCH
command with all options of the ANR algorithm switch
parameter deselected. Example: MOD ENODEBALGOSWITCH:
AnrSwitch=IntraRatEventAnrSwitch-0&IntraRatFastAnrSwitch
-0&IntraRatAnrAutoDelSwitch-0&UtranEventAnrSwitch-0&Ge
ranEventAnrSwitch-0&UtranFastAnrSwitch-0&GeranFastAnrS
witch-0&CdmaFastAnrSwitch-0&UtranAutoNrtDeleteSwitch-
0&GeranAutoNrtDeleteSwitch-0&CdmaAutoNrtDeleteSwitch
-0&CdmaEventAnrSwitch-0;
iv. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 245

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Using MML commands:

i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the LST GLOBALPROCSWITCH command to query the values of
the following parameters: The Switch of X2 setup by SON, Peer
Request Based X2 Delete Switch, X2 SON Delete Switch, Interface
Setup Policy Switch, The Timer of X2 delete by SON, and X2-
based Neighboring Cell Configuration Update Switch.
○ Skip this step if the The Timer of X2 delete by SON parameter
is 0, the LTE_NR_X2_SON_SETUP_SW option of the Interface
Setup Policy Switch parameter is deselected, and the options of
all the other preceding parameters are deselected.
○ If The Timer of X2 delete by SON parameter is not 0, the
LTE_NR_X2_SON_SETUP_SW option of the Interface Setup
Policy Switch parameter is selected, or the options of all the
other preceding parameters are selected, run the MOD
GLOBALPROCSWITCH command to set the The Timer of X2
delete by SON parameter to 0 and deselect all these options.
Example: MOD GLOBALPROCSWITCH:
X2SonSetupSwitch=OFF, X2SonDeleteTimer=0,
PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2US
AGE_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-
0,
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_N
CELL_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD_FREQ_CFG_SW
-0&UPT_EXTERNALCELLBAND_CFG_SW-0,
InterfaceSetupPolicySw=X2_SON_INTER_OP_SETUP_FBD_SW-
1&LTE_NR_X2_SON_SETUP_SW-0;
iii. Run the LST ENODEBALGOSWITCH command to check whether the
options of ANR algorithm switch are selected.
○ If all the options of this parameter are deselected, skip this step.
○ If any option is selected, run the MOD ENODEBALGOSWITCH
command with all options of the ANR algorithm switch
parameter deselected. Example: MOD ENODEBALGOSWITCH:
AnrSwitch=IntraRatEventAnrSwitch-0&IntraRatFastAnrSwitch
-0&IntraRatAnrAutoDelSwitch-0&UtranEventAnrSwitch-0&Ge
ranEventAnrSwitch-0&UtranFastAnrSwitch-0&GeranFastAnrS
witch-0&CdmaFastAnrSwitch-0&UtranAutoNrtDeleteSwitch-
0&GeranAutoNrtDeleteSwitch-0&CdmaAutoNrtDeleteSwitch
-0&CdmaEventAnrSwitch-0;
iv. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 246

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",

USR="ftpuser", PWD="***********", DIR="ftproot/";
v. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
vi. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.5.25.4 Engineering Verification

This section describes how to verify the reconfiguration of deleting a cell.

Procedure
Step 1 Run the LST CELL command to check whether the cell exists.
● If the cell still exists, delete the corresponding MO based on the cause
displayed in the RMV CELL command output.
● If the cause displayed in the RMV CELL command output indicates an
exception, contact Huawei technical support or dial the Huawei technical
support hotline.

----End

1.5.25.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 247

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ii. Run the ACT CFGFILE command to activate the original

configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.5.25.4

Engineering Verification.
----End

1.5.26 Co-BBP 4T4R and 8T8R Cells

This section describes how to establish 4T4R and 8T8R cells on a BBP.

1.5.26.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for establishing 4T4R and 8T8R cells
on a BBP.

Application Scenario
The UBBPd9/UBBPea is used, and 4T4R and 8T8R cells need to be established on
the same BBP to save baseband resources.

Reconfiguration Impact
During establishment of 4T4R and 8T8R cells on the same BBP, the BBP
automatically resets, and baseband resources are reallocated. In this case, cells
that have been established on the BBP cannot provide services.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 248

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme
The following figure shows the procedure for establishing 4T4R and 8T8R cells on
a BBP.

Figure 1-41 Procedure for establishing 4T4R and 8T8R cells on a BBP

1. Run the MOD ENODEBRESMODEALGO command with the

TddBbpResDeployAlgo parameter set to RESOURCE_PRIMARY.
2. Run the ADD BASEBANDEQM command to bind each UBBP to a piece of
baseband equipment.
3. Run the MOD EUCELLSECTOREQM command to bind a cell to the baseband
equipment.
The number of cells bound to a piece of baseband equipment must be less
than or equal to the maximum number of TX/RX channels supported by the
BBP. Only the UBBPd9 and UBBPea can be used in this scenario.
– Generally, the UBBPd9 supports a maximum of three 8T8R cells or six
4T4R cells. In co-BBP scenarios, the UBBPd9 supports a maximum of
three 4T4R cells or 8T8R cells.
– Generally, the UBBPea supports a maximum of six 8T8R cells or twelve
4T4R cells. In co-BBP scenarios, the UBBPea supports a maximum of six
4T4R cells or 8T8R cells.

Topology Change
N/A

1.5.26.2 Engineering Preparation

This section describes the engineering preparation for establishing 4T4R and 8T8R
cells on a BBP, including information collection and preparation of hardware,

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 249

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

software, license files, security certificates, and data. It also describes the data
preparation mode and provides MML configuration script examples.

Information Collection
Table 1-86 describes the information to be collected for data preparation.

Table 1-86 Information to be collected

Item Description

BBP information Includes the BBP model.

Cell information Includes the information about cells that have been
established on the BBP and their TX/RX modes.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure in
Scheme Overview. The following table lists the data to be prepared.

Table 1-87 Data to be prepared

SN Ope MO Configuration Reference

ratio
n

1 Modi eNodeBResModeAlgo Set the TddBbpResDeployAlgo

fy parameter to RESOURCE_PRIMARY.
For details about parameter settings, see
Base Station Cabinets and Subracks
(Including the BBU Subrack)
Configuration Feature Parameter
Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 250

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

2 Add BASEBANDEQM One BBP can be added to only one piece

of baseband equipment.

3 Modi eUCellSectorEqm Bind 4T4R and 8T8R cells to the same

fy baseband equipment.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch configuration mode of the MAE-Deployment: For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

Assume that a new UBBP and LRRU are used. Then, the MML configuration scripts
are as follows:
/*Modifying the baseband resource allocation algorithm for TDD cells to RESOURCE_PRIMARY*/
MOD ENODEBRESMODEALGO: TddBbpResDeployAlgo=RESOURCE_PRIMARY;
/*Adding baseband equipment*/
ADD BASEBANDEQM: BASEBANDEQMID=3, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=3;
/*Modifying the configuration of sector equipment for the cells*/
MOD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, BaseBandEqmId=3;
MOD EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=1, BaseBandEqmId=3;

1.5.26.3 Engineering Implementation

This section describes the engineering implementation for establishing 4T4R and
8T8R cells on a BBP, including prerequisites, context, and procedure.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 251

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Prerequisites
Related information, hardware, software, and configuration data are ready for
establishing 4T4R and 8T8R cells on a BBP.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
c. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
d. Deliver the configuration data to the eNodeB and activate the data. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
e. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Using MML commands:
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 252

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
d. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.5.26.4 Engineering Verification

This section describes how to verify the establishment of co-BBP 4T4R and 8T8R
cells.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command to check whether the value of Cell instance state is
Normal for the cell.
● If Cell instance state is Uninstall, check the cell configuration or hardware
based on the value of Reason for latest state change in the command
output.
● Check whether the 4T4R and 8T8R cells are established on the same BBP. If
no, adjust the configurations and bind cells to the appropriate baseband
equipment.
Step 3 Run the LST CELL command to check whether the cell information is the same as
planned.
If the cell information is not the same as planned, perform the following steps:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 253

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The reconfiguration is
performed on the MAE-
Deployment
Check whether the cell information in the modified data file is the
same as planned:
● If they are different, modify the configuration data file again and
import it into the system. Then perform the operations in
Engineering Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the data is
imported into the system or delivered to the base station. In this
situation, contact Huawei technical support or dial the Huawei
technical support hotline.

The reconfiguration is
performed by using MML
commands
Check whether the parameter settings in the script are correct:
● If they are incorrect, modify the parameters in the script. Run the
RMV CELL command to delete the cell. Then run the ADD CELL
command to add a cell again.
● If they are correct, contact Huawei technical support or dial the
Huawei technical support hotline.

----End

1.5.26.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 254

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: DSP ROLCFGINFO: OT=BYINFO;

ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Verify that engineering rollback is successful according to instructions in 1.5.26.4

Engineering Verification.

----End

1.6 Base Station Data Reconfigurations

This chapter describes how to reconfigure base station data in typical scenarios.

1.6.1 Changing the eNodeB from Independent Operator Mode

to RAN Sharing with Common Carrier Mode
This section describes how to change the eNodeB from independent operator
mode to RAN sharing with common carrier mode.

1.6.1.1 Scheme Overview

This section describes the prerequisites, application scenario, reconfiguration
impact, reconfiguration scheme, and topology change for changing the eNodeB
from independent operator mode to RAN sharing with common carrier mode.

Prerequisites
If a new operator does not use the EPC of the existing operator, the EPC of the
new operator must be configured to provide basic EPC functions.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 255

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Application Scenario
To share the license fee for spectrum or reduce network deployment costs, an
operator wants to share the eNodeB hardware resource and spectrum resource
with other operators.

Reconfiguration Impact
After the change of the base station sharing mode, the base station must be reset
to make the configuration take effect. During the reset, the base station cannot
provide services.

Reconfiguration Scheme
If the MME is to be shared by multiple operators, add multiple public land mobile
networks (PLMNs) to the MME before adjusting the eNodeB configuration. If the
MME is not to be shared by multiple operators, add an EPC and ensure that the
route between the new EPC and the eNodeB is reachable and working properly.
Determine the reconfiguration scheme for changing the eNodeB from
independent operator mode to RAN sharing with common carrier mode according
to the following table.

Table 1-88 Scheme options

If... Then...

The new operator ● Add connections to the MME and S-GW of the new
and the existing operator. For details, see 1.8.1.1 Scheme Overview in
operator do not Adding an MME Connection and 1.8.2.1 Scheme
share the EPC Overview in Adding an S-GW Connection.
● If the parameters used by the new operator for SCTP
link self-setup are different from those used by the
existing operator, add a new SCTP parameter
template.

The proportion of Configure the proportion of the number of users

the number of users allocated to each operator.
allocated to each
operator needs to be
limited

The proportion of Turn on the switch for setting specific RAN sharing
RBs allocated to modes.
each operator needs
to be limited

The traffic Set the traffic sharing mode to be operator-specific and

proportion allocated configure the proportion of licensed traffic allocated to
to each operator each operator.
needs to be limited

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 256

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The neighboring cells Add an external E-UTRAN cell. After the external cell is
of the cells under the added, the eNodeB automatically adds the cell to the list
eNodeB have of neighboring E-UTRAN cells when a handover to the
changed cell is performed.

The neighboring cell Add a PLMN list for the external E-UTRAN cell and set
works in RAN the MCC and MNC of the secondary operator of the
sharing with eNodeB serving the neighboring cell.
common carrier
mode

Figure 1-42 shows the reconfiguration procedure for changing the eNodeB from
independent operator mode to RAN sharing with common carrier mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 257

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-42 Procedure for changing the eNodeB from independent operator mode
to RAN sharing with common carrier mode

Topology Change
Use the scenario where the new operator does not share the EPC with the existing
operator as an example. Figure 1-43 shows the topologies before and after the
reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 258

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-43 Topologies before and after the reconfiguration

1.6.1.2 Engineering Preparation

This section describes the engineering preparation for changing the eNodeB from
independent operator mode to RAN sharing with common carrier mode, including
information collection and preparation of hardware, software, license files, security
certificates, and data. It also describes the data preparation mode and provides
MML configuration script examples.

Information Collection
Table 1-89 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 259

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-89 Information to be collected

Information Description

New operators The information includes the following:

● Number of operators involved in RAN sharing
● Operator types
● Operator names
● MCC and MNC of each operator
● Policy of sharing the number of users, number of RBs,
and traffic for each operator

Connections to the The information includes the following:

MMEs of new ● Route to each new MME, involving the device IP
operators address of the eNodeB, next-hop IP address of the
eNodeB, destination IP address (signaling IP address
of the MME), subnet mask, and route priority
● Local port number of each new MME

Connections to the Route to each new S-GW, involving the device IP address
S-GWs of new of the eNodeB, next-hop IP address of the eNodeB,
operators destination IP address (service IP address of the S-GW),
subnet mask, and route priority

Neighboring cells of External cells and neighbor relationships

new operators

Hardware Preparation
Prepare the hardware described in Table 1-90.

Table 1-90 Hardware to be prepared

If... Then...

A new operator and Prepare cables between the eNodeB and the router
the existing operator closest to the eNodeB along the route from the eNodeB
do not share the EPC to the new MME and S-GW. The cables can be Ethernet
cables or optical fibers, depending on the router type.

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 260

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Certificate Preparation
N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Table 1-91 Data preparation for changing the eNodeB from independent operator
mode to RAN sharing with common carrier mode
SN Ope MO Configuration Reference
ratio
n

1 Modi ENodeBSharingMode Set the eNodeB sharing mode

fy parameter to Shared Frequency
Sharing Mode.

2 Add CnOperator Add a CnOperator MO for each new

operator.

3 Add S1 Configure an S1 MO for each new

operator, and add connections to the
MME and S-GW of each new operator.
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

4 Add SCTPTEMPLATE Set the parameters used by each new

operator for SCTP link self-setup.
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

5 Add LicenseSharingPolicy Set the maximum proportion of the

number of users allocated to each new
operator.

6 Add CnOperatorTa Add a TAC for each new operator.

7 Modi CellAlgoSwitch Change the value of RAN Sharing

fy Mode Switch to ON.

8 Add CellOp Set the proportions of uplink and

downlink RBs allocated to each operator.

9 Modi LicRatio Set the Traffic Sharing Type parameter

fy to DEDICATE.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 261

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

10 Add LicRatioSharePolicy Set the licensed uplink and downlink

traffic proportions for each operator and
the percentage of available resources
one operator can share with other
operators.

11 Add EutranExternalCell Add external cells of the eNodeB.

12 Add EutranExternalCellPlm Add the MCC and MNC of a secondary

n operator involved in RAN sharing with
common carrier.

Data Preparation Mode

You can prepare data using the MAE-Deployment or MML commands. You are
advised to use the batch reconfiguration mode or the radio data planning file of
the MAE-Deployment for batch configuration. The MAE-Deployment GUI is
recommended for configuring a single base station. The four data preparation
modes are described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the MAE-Deployment batch reconfiguration mode (with the name of

the scenario-specific template being "Changing from Independent Operator
Mode to RAN Sharing with Common Carriers"): For details, see the interactive
operation guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
Deployment to Prepare Data.
● Using the MAE-Deployment-provided radio data planning file
a. On the menu bar, choose LTE Application > Network Adjustment >
Export Radio Network Planning Data to start exporting the radio
network planning data from the system into the radio data planning file.
b. Edit data in the file based on the prepared data. Then, close the file.
c. On the menu bar of the planned data area, choose LTE Application >
Network Adjustment > Import Radio Network Planning Data. A dialog
box is displayed for you to import planned radio data. Import the data
from the file into the system.
For detailed import and export operations, see section Importing and
Exporting Planned Radio Data in the MAE-Access online help.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 262

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands. Prepare MML configuration scripts based on the

preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, the new operator shares the EPC with the existing
operator, and you need to configure the proportions of the number of users,
traffic, uplink and downlink RBs allocated to each operator, as well as a
neighboring cell working in RAN sharing with common carrier mode.
NOTE

● This example does not include the scripts for adding an MME connection and an S-GW
connection. For these scripts, see Adding an MME Connection > Engineering Preparation >
MML Configuration Script Example and Adding an S-GW Connection > Engineering
Preparation > MML Configuration Script Example.
● If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
● You must reset the base station after changing its sharing mode. You are advised to reset the
base station after other MML commands are executed. If a multimode base station is to be
reconfigured, you need to reset the application.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Changing the RAN sharing mode to RAN sharing with common carrier*/
MOD ENODEBSHARINGMODE: ENodeBSharingMode=SHARED_FREQ;
/*Adding a new operator*/
ADD CNOPERATOR: CnOperatorId=1, CnOperatorName="TEST",
CnOperatorType=CNOPERATOR_SECONDARY, Mcc="460", Mnc="01";
/*Adding an S1 MO*/
ADD S1: S1Id=0, CnOperatorId=1, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=0, UpEpGroupId=0;
/*Adding an SCTP parameter template*/
ADD SCTPTEMPLATE: SCTPTEMPLATEID=0, SWITCHBACKFLAG=ENABLE;
/*Setting the proportions of both operators' maximum number of users to 50%*/
ADD LICENSESHARINGPOLICY: CnOperatorId=0, MaxUserNumRate=50;
ADD LICENSESHARINGPOLICY: CnOperatorId=1, MaxUserNumRate=50;
/*Adding a TAC 33 for the new operator*/
ADD CNOPERATORTA: TrackingAreaId=1, CnOperatorId=1, Tac=33;
/*Changing the value of RanShareModeSwitch to ON*/
MOD CELLALGOSWITCH: LocalCellId=0, RanShareModeSwitch=ON;
/*Setting the proportions of both uplink and downlink RBs to 50% for the operator*/
ADD CELLOP: LocalCellId=0, TrackingAreaId=1, OpUlRbUsedRatio=50, OpDlRbUsedRatio=50;
/*Setting the traffic sharing mode to DEDICATE*/
MOD LICRATIO: TrafficSharingType=DEDICATE;
/*Setting the proportions of both operators' traffic to 50%, and setting the proportion of traffic that one
operator can share with the other to 10%*/
ADD LICRATIOSHAREPOLICY: CnOperatorId=0, TrfRatio=50, TrfSharingRatio=10;
ADD LICRATIOSHAREPOLICY: CnOperatorId=1, TrfRatio=50, TrfSharingRatio=10;
/*Adding an external E-UTRAN cell*/
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="01", eNodeBId=526302, CellId=10, DlEarfcn=3350,
UlEarfcnCfgInd=NOT_CFG, PhyCellId=390, Tac=33;
/*Adding PLMN information for the external E-UTRAN cell*/
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="01", eNodeBId=526302, CellId=10, ShareMcc="460",
ShareMnc="00";
/*Resetting the base station*/
RST BTSNODE:;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 263

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.6.1.3 Engineering Implementation

This section describes the engineering implementation for changing the eNodeB
from independent operator mode to RAN sharing with common carrier mode,
including prerequisites, context, and procedure.

Prerequisites
● Information, hardware, software, and data for changing the eNodeB from
independent operator mode to RAN sharing with common carrier mode are
ready, and the license file is available in the save path on the FTP server.
● If a new operator does not share the EPC with the existing operator, the EPC
of the new operator has been configured to provide basic functions.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

(Optional) Connect the cables between the eNodeB and the new MME and S-
GW if the new operator does not share the EPC with the existing operator.
● Remote Operations
– Using the MAE-Deployment:
NOTE

● If the license file needs to be updated, the active license file must be backed up
and a new license file must be imported into the base station. If the license file
does not need to be updated, the backup and import operations are not required.
● If the iSStar is used to deliver the scripts, the reconfiguration takes effect only
after the base station is reset. Therefore, you need to run the RST APP command
to reset the base stations in batches after the scripts are delivered.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 264

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For example: INS LICENSE: DIR="ftproot/",

FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.6.1.4 Engineering Verification

This section describes how to verify the change from independent operator mode
to RAN sharing with common carrier mode.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 265

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.
Step 3 Verify that the eNodeB properly communicates with the EPC of the new operator.
For details, see 1.8.1.4 Engineering Verification in Adding an MME Connection
and 1.8.2.4 Engineering Verification in Adding an S-GW Connection.
Step 4 On the main menu of the MAE-Access, choose Monitor > Signaling Trace >
Signaling Trace Management. Then, choose LTE > Application Layer > Uu
Interface Trace from the navigation tree on the left to start a Uu interface tracing
task. In the tracing result, verify that the SIB1 message sent from the cell under
the eNodeB contains the PLMN information of both the new and existing
operators.
If the PLMN information is incomplete, check whether the PLMN information of
the operators in the configuration data file is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
Step 5 Enable UEs of each operator to perform tests to verify that the UEs can
successfully access the network.
If any UE cannot pass the test, check whether the cell is normal.
● If the cell fails to be established, the eNodeB reports an alarm. If this
happens, clear the alarm according to the instructions in 3900 & 5900 Series
Base Station Alarm Reference.
● If the cell is successfully established, contact Huawei technical support or dial
the Huawei technical support hotline.

----End

1.6.1.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 266

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. Run the DLD CFGFILE command to download the original

configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the cable connections.
Step 4 Verify the engineering rollback.
1. Verify that no cell-related alarm is reported, such as ALM-29240 Cell
Unavailable and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.
2. Run the DSP CELL command. Verify that Cell instance state is Normal for
the cell.
If Cell instance state is Uninstall, check the cell configuration or hardware
based on the value of Reason for latest state change in the command
output.
3. On the main menu of the MAE-Access, choose Monitor > Signaling Trace >
Signaling Trace Management. Then, choose LTE > Application Layer > Uu

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 267

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Interface Trace from the navigation tree on the left to start a Uu interface
tracing task. In the tracing result, verify that the SIB1 message sent from the
cell under the eNodeB contains the PLMN information of only the existing
operator.

If PLMN information of other operators is contained, run the LST

CNOPERATOR, LST CNOPERATORTA, and LST CELLOP commands to check
whether there are other operators.

– If there are other operators, run the RMV CELLOP, RMV

CNOPERATORTA, and/or RMV CNOPERATOR commands to remove the
operators.
– If there are no other operators, contact Huawei technical support or dial
the Huawei technical support hotline.

----End

1.6.2 Changing the eNodeB from Independent Operator Mode

to RAN Sharing with Dedicated Carrier Mode
This section describes how to change the eNodeB from independent operator
mode to RAN sharing with dedicated carrier mode.

1.6.2.1 Scheme Overview

This section describes the prerequisites, application scenario, reconfiguration
impact, reconfiguration scheme, and topology change for changing the eNodeB
from independent operator mode to RAN sharing with dedicated carrier mode.

Prerequisites
If a new operator does not use the EPC of the existing operator, the EPC of the
new operator must be configured to provide basic EPC functions.

Application Scenario
To reduce network deployment and maintenance costs, multiple operators with
dedicated carriers share eNodeB hardware resources.

Reconfiguration Impact
After the change from independent operator mode to RAN sharing with dedicated
carrier mode, you must reset the eNodeB make the configuration take effect.
During the reset, the eNodeB cannot provide services.

Reconfiguration Scheme
If the MME is shared by multiple operators, add multiple PLMNs to the MME
before adjusting the eNodeB configuration. If the MME is not shared by multiple
operators, add an EPC and ensure that the route between the new EPC and the
eNodeB is reachable and working properly.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 268

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Determine the reconfiguration scheme for changing the eNodeB from

independent operator mode to RAN sharing with dedicated carrier mode
according to the following table.

Table 1-92 Scheme options

If... Then...

The new operator ● Add connections to the MME and S-GW of the new
and the existing operator. For details, see 1.8.1.1 Scheme Overview in
operator do not Adding an MME Connection and 1.8.2.1 Scheme
share the EPC Overview in Adding an S-GW Connection.
● If the parameters used by the new operator for SCTP
link self-setup are different from those used by the
existing operator, add a new SCTP parameter
template.

The proportion of Configure the proportion of the number of users

the number of users allocated to each operator.
allocated to each
operator needs to be
limited

The traffic Set the traffic sharing mode to be operator-specific and

proportion allocated configure the proportion of licensed traffic allocated to
to each operator each operator.
needs to be limited

The neighboring cells Add an external E-UTRAN cell. After the external cell is
of the cells under the added, the eNodeB automatically adds the cell to the list
eNodeB have of neighboring E-UTRAN cells when a handover to the
changed cell is performed.

The neighboring cell Add a PLMN list for the external E-UTRAN cell and set
works in RAN the MCC and MNC of the secondary operator of the
sharing with eNodeB serving the neighboring cell.
common carrier
mode

NOTE

For details about how to add a cell for a new operator, see 1.5.1 Adding an FDD/NB-IoT Cell
(Common Scenarios) or 1.5.3 Adding a TDD Cell (Common Scenarios).
Figure 1-44 shows the reconfiguration procedure for changing the eNodeB from
independent operator mode to RAN sharing with dedicated carrier mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 269

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-44 Procedure for changing the eNodeB from independent operator mode
to RAN sharing with dedicated carrier mode

Topology Change
Use the scenario where the new operator does not share the EPC with the existing
operator as an example. Figure 1-45 shows the topologies before and after the
reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 270

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-45 Topologies before and after the reconfiguration

1.6.2.2 Engineering Preparation

This section describes the engineering preparation for changing the eNodeB from
independent operator mode to RAN sharing with dedicated carrier mode,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Before data preparation, collect the information required for adding a cell. For
details, see Adding an FDD/NB-IoT Cell > Engineering Preparation >
Information Collection or Adding a TDD Cell > Engineering Preparation >
Information Collection. In addition, collect the information listed in Table 1-93.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 271

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-93 Information to be collected

Information Description

New operators The information includes the following:

● Number of operators involved in RAN sharing
● Operator types
● Operator names
● MCC and MNC of each operator
● Policy of sharing the number of users, number of RBs,
and traffic for each operator

Connections to the The information includes the following:

MMEs of new ● Route to each new MME, involving the device IP
operators address of the eNodeB, next-hop IP address of the
eNodeB, destination IP address (signaling IP address
of the MME), subnet mask, and route priority
● Local port number of each new MME

Connections to the Route to each new S-GW, involving the device IP address
S-GWs of new of the eNodeB, next-hop IP address of the eNodeB,
operators destination IP address (service IP address of the S-GW),
subnet mask, and route priority

Neighboring cells of External cells and neighbor relationships

new operators

Hardware Preparation
Before changing the eNodeB from independent operator mode to RAN sharing
with dedicated carrier mode, prepare the hardware for adding a cell according to
Adding an FDD/NB-IoT Cell > Engineering Preparation > Hardware
Preparation or Adding a TDD Cell > Engineering Preparation > Hardware
Preparation. In addition, prepare the hardware according to Table 1-94.

Table 1-94 Hardware to be prepared

If... Then...

A new operator and Prepare cables between the eNodeB and the router
the existing operator closest to the eNodeB along the route from the eNodeB
do not share the EPC to the new MME and S-GW. The cables can be Ethernet
cables or optical fibers, depending on the router type.

Software Preparation
If the RET antenna or TMA to be added needs to be upgraded, acquire the latest
software and data from the vendors.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 272

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

License File Preparation

If the license file is to be updated, a new license file is required.

Certificate Preparation
N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Table 1-95 Data preparation for changing the eNodeB from independent operator
mode to RAN sharing with dedicated carrier mode

SN Operation MO Configuration Reference

1 Modify ENodeBSharingM Set the eNodeB sharing mode

ode parameter to Separate Frequency
Sharing Mode.

2 Add CnOperator Add a CnOperator MO for each new

operator.

3 Add CnOperatorTa Add a TAC for each new operator.

4 Add S1 Configure an S1 MO for each new

operator, and add connections to the
MME and S-GW of each new
operator.
For details, see LTE and NR NSA S1
and X2 Self-Management Feature
Parameter Description.

5 Add SCTPTEMPLATE Set the parameters used by each

new operator for SCTP link self-
setup.
For details, see LTE and NR NSA S1
and X2 Self-Management Feature
Parameter Description.

6 Add Cell Add cells for each new operator. For

details, see Adding an FDD Cell >
Engineering Preparation > Data
Preparation or Adding a TDD Cell >
Engineering Preparation > Data
Preparation.

7 Add LicenseSharingPo Set the maximum proportion of the

licy number of users allocated to each
operator.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 273

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Operation MO Configuration Reference

8 Modify LicRatio Set the Traffic Sharing Type

parameter to DEDICATE.

9 Add LicRatioSharePo- Set the licensed uplink and downlink

licy traffic proportions for each operator
and the percentage of available
resources one operator can share
with other operators.

10 Add EutranExternalCe Add external cells of the eNodeB.

ll

11 Add EutranExternalCe Add the MCC and MNC of a

llPlmn secondary operator involved in RAN
sharing with common carrier.

Data Preparation Mode

You can prepare data using the MAE-Deployment or MML commands. You are
advised to use the batch reconfiguration mode or the radio data planning file of
the MAE-Deployment for batch configuration. The MAE-Deployment GUI is
recommended for configuring a single base station. The four data preparation
modes are described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the MAE-Deployment batch reconfiguration mode (with the name of

the scenario-specific template being "Changing from Independent Operator
Mode to RAN Sharing with Dedicated Carriers"): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment-provided radio data planning file
a. On the menu bar, choose LTE Application > Network Adjustment >
Export Radio Network Planning Data to start exporting the radio
network planning data from the system into the radio data planning file.
b. Edit data in the file based on the prepared data. Then, close the file.
c. On the menu bar of the planned data area, choose LTE Application >
Network Adjustment > Import Radio Network Planning Data. A dialog
box is displayed for you to import planned radio data. Import the data
from the file into the system.
For detailed import and export operations, see section Importing and
Exporting Planned Radio Data in the MAE-Access online help.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 274

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, the new operator does not share the EPC with the
existing operator, and you need to configure the proportions of the number of
users, traffic, uplink and downlink RBs allocated to each operator, as well as a
neighboring cell working in RAN sharing with common carrier mode.
NOTE

● This example does not include the scripts for adding an MME connection and an S-GW
connection. For these scripts, see Adding an MME Connection > Engineering Preparation >
MML Configuration Script Example and Adding an S-GW Connection > Engineering
Preparation > MML Configuration Script Example.
● This example does not include the script for adding a cell. For the script, see Adding an
FDD/NB-IoT Cell > Engineering Preparation > MML Configuration Script Example or
Adding a TDD Cell > Engineering Preparation > MML Configuration Script Example.
● If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
● You must reset the base station after changing its sharing mode. You are advised to reset the
base station after other MML commands are executed. If a multimode base station is to be
reconfigured, you need to reset the application.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Changing the base station sharing mode to RAN sharing with dedicated carrier*/
MOD ENODEBSHARINGMODE: ENodeBSharingMode=SEPARATED_FREQ;
/*Adding an operator for the base station*/
ADD CNOPERATOR: CnOperatorId=1, CnOperatorName="TEST",
CnOperatorType=CNOPERATOR_SECONDARY, Mcc="460", Mnc="01";
/*Adding a TAC 33 for the new operator*/
ADD CNOPERATORTA: TrackingAreaId=1, CnOperatorId=1, Tac=33;
/*Adding an S1 MO*/
ADD S1: S1Id=0, CnOperatorId=1, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=0, UpEpGroupId=0;
/*Adding an SCTP parameter template*/
ADD SCTPTEMPLATE: SCTPTEMPLATEID=0, SWITCHBACKFLAG=ENABLE;
/*Setting the proportions of both operators' maximum number of users to 50%*/
ADD LICENSESHARINGPOLICY: CnOperatorId=0, MaxUserNumRate=50;
ADD LICENSESHARINGPOLICY: CnOperatorId=1, MaxUserNumRate=50;
/*Setting the traffic sharing mode to DEDICATE*/
MOD LICRATIO: TrafficSharingType=DEDICATE;
/*Setting the proportions of both operators' traffic to 50%, and setting the proportion of traffic that one
operator can share with the other to 10%*/
ADD LICRATIOSHAREPOLICY: CnOperatorId=0, TrfRatio=50, TrfSharingRatio=10;
ADD LICRATIOSHAREPOLICY: CnOperatorId=1, TrfRatio=50, TrfSharingRatio=10;
/*Adding an external E-UTRAN cell*/
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="01", eNodeBId=526302, CellId=10, DlEarfcn=3350,
UlEarfcnCfgInd=NOT_CFG, PhyCellId=390, Tac=33;
/*Adding PLMN information for the external E-UTRAN cell*/
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="01", eNodeBId=526302, CellId=10, ShareMcc="460",
ShareMnc="00";
/*Resetting the base station*/
RST BTSNODE:;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 275

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.6.2.3 Engineering Implementation

This section describes the engineering implementation for changing the eNodeB
from independent operator mode to RAN sharing with dedicated carrier mode,
including prerequisites, context, and procedure.

Prerequisites
● Information for changing the eNodeB from independent operator mode to
RAN sharing with dedicated carrier mode has been collected, hardware,
software, and configuration data are ready, and the license file is available in
the save path on the FTP server.
● If a new operator does not share the EPC with the existing operator, the EPC
of the new operator has been configured to provide basic functions.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
(Optional) Connect the cables between the eNodeB and the new MME and S-
GW if the new operator does not share the EPC with the existing operator.
● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 276

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iv. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.6.2.4 Engineering Verification

This section describes how to verify the change from independent operator mode
to RAN sharing with dedicated carrier mode.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 277

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.
Step 3 Verify that the eNodeB properly communicates with the EPC of the new operator.
For details, see 1.8.1.4 Engineering Verification in Adding an MME Connection
and 1.8.2.4 Engineering Verification in Adding an S-GW Connection.
Step 4 On the main menu of the MAE-Access, choose Monitor > Signaling Trace >
Signaling Trace Management. Then, choose LTE > Application Layer > Uu
Interface Trace from the navigation tree on the left to start a Uu interface tracing
task. In the tracing result, verify that the SIB1 message sent from the cell under
the eNodeB contains the PLMN information of both the new and existing
operators.
If the PLMN information is incomplete, check whether the PLMN information of
the operators in the configuration data file is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
Step 5 Enable UEs of each operator to perform tests to verify that the UEs can
successfully access the network.
If any UE cannot pass the test, check whether the cell is normal.
● If the cell fails to be established, the eNodeB reports an alarm. If this
happens, clear the alarm according to the instructions in 3900 & 5900 Series
Base Station Alarm Reference.
● If the cell is successfully established, contact Huawei technical support or dial
the Huawei technical support hotline.

----End

1.6.2.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 278

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",

USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the cable connections.
Step 4 Verify the engineering rollback.
1. Verify that no cell-related alarm is reported, such as ALM-29240 Cell
Unavailable and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.
2. Run the DSP CELL command. Verify that Cell instance state is Normal for
the cell.
If Cell instance state is Uninstall, check the cell configuration or hardware
based on the value of Reason for latest state change in the command
output.
3. On the main menu of the MAE-Access, choose Monitor > Signaling Trace >
Signaling Trace Management. Then, choose LTE > Application Layer > Uu
Interface Trace from the navigation tree on the left to start a Uu interface
tracing task. In the tracing result, verify that the SIB1 message sent from the

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 279

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

cell under the eNodeB contains the PLMN information of only the existing
operator.
If the SIB1 message contains PLMN information of other operators, run the
LST CNOPERATOR, LST CNOPERATORTA, and LST CELLOP commands to
check whether there are other operators.
– If there are other operators, run the RMV CELLOP, RMV
CNOPERATORTA, or/and RMV CNOPERATOR commands to remove the
operators.
– If there are no other operators, contact Huawei technical support or dial
the Huawei technical support hotline.

----End

1.6.3 Changing the eNodeB from Independent Operator Mode

to Hybrid RAN Sharing Mode
This section describes how to change the eNodeB from independent operator
mode to hybrid RAN sharing mode.

1.6.3.1 Scheme Overview

This section describes the prerequisites, application scenario, reconfiguration
impact, reconfiguration scheme, and topology change for changing the eNodeB
from independent operator mode to hybrid RAN sharing mode.

Prerequisites
If a new operator does not use the EPC of the existing operator, the EPC of the
new operator must be configured to provide basic EPC functions.

Application Scenario
In hybrid RAN sharing mode, there are multiple frequencies. These frequencies can
be shared or exclusively occupied by multiple operators. All the following
conditions must be met before hybrid RAN sharing is enabled:
● The physical base station works on two or more frequencies.
● At least one frequency is shared among multiple operators.
● Two or more frequencies have different primary PLMNs.
Hybrid RAN sharing offers the following benefits:
● Compared with RAN sharing with common carrier, hybrid RAN sharing allows
multiple cells to have different primary PLMN IDs.
● Compared with RAN sharing with dedicated carrier, hybrid RAN sharing allows
multiple operators to share the same cell.

Reconfiguration Impact
After the change of the base station sharing mode, the base station must be reset
to make the configuration take effect. During the reset, the base station cannot
provide services.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 280

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme
Determine the reconfiguration scheme for changing the eNodeB from
independent operator mode to hybrid RAN sharing mode according to the
following table.

Table 1-96 Scheme options

If... Then...

The new operator ● Add connections to the MME and S-GW of the new
and the existing operator. For details, see 1.8.1.1 Scheme Overview in
operator do not Adding an MME Connection and 1.8.2.1 Scheme
share the EPC Overview in Adding an S-GW Connection.
● If the parameters used by the new operator for SCTP
link self-setup are different from those used by the
existing operator, add a new SCTP parameter
template.

The proportion of Configure the proportion of the number of users

the number of users allocated to each operator.
allocated to each
operator needs to be
limited

The proportion of Turn on the switch for setting specific RAN sharing
RBs allocated to modes.
each operator needs
to be limited

The traffic Set the traffic sharing mode to be operator-specific and

proportion allocated configure the proportion of licensed traffic allocated to
to each operator each operator.
needs to be limited

The neighboring cells Add an external E-UTRAN cell. After the external cell is
of the cells under the added, the eNodeB automatically adds the cell to the list
eNodeB have of neighboring E-UTRAN cells when a handover to the
changed cell is performed.

The neighboring cell Add a PLMN list for the external E-UTRAN cell and set
works in RAN the MCC and MNC of the secondary operator of the
sharing with eNodeB serving the neighboring cell.
common carrier
mode

NOTE

For details about how to add a cell for a new operator, see 1.5.1 Adding an FDD/NB-IoT Cell
(Common Scenarios) or 1.5.3 Adding a TDD Cell (Common Scenarios).
Figure 1-46 shows the reconfiguration procedure for changing the eNodeB from
independent operator mode to hybrid RAN sharing mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 281

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-46 Procedure for changing the eNodeB from independent operator mode
to hybrid RAN sharing mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 282

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Use the scenario where the new operator does not share the EPC with the existing
operator as an example. Figure 1-47 shows the topologies before and after the
reconfiguration.

Figure 1-47 Topologies before and after the reconfiguration

1.6.3.2 Engineering Preparation

This section describes the engineering preparations for changing the eNodeB from
independent operator mode to hybrid RAN sharing mode, including information
collection and preparation of hardware, software, license files, security certificates,
and data. It also describes the data preparation mode and provides MML
configuration script examples.

Information Collection
Before data preparation, collect the information required for adding a cell. For
details, see Adding an FDD/NB-IoT Cell > Engineering Preparation >
Information Collection or Adding a TDD Cell > Engineering Preparation >
Information Collection. In addition, collect information listed in Table 1-97.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 283

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-97 Information to be collected

Information Description

New operators The information includes the following:

● Number of operators involved in RAN sharing
● Operator types
● Operator names
● MCC and MNC of each operator
● Policy of sharing the number of users, number of RBs,
and traffic for each operator

Connections to the The information includes the following:

MMEs of new ● Route to each new MME, involving the device IP
operators address of the eNodeB, next-hop IP address of the
eNodeB, destination IP address (signaling IP address
of the MME), subnet mask, and route priority
● Local port number of each new MME

Connections to the Route to each new S-GW, involving the device IP address
S-GWs of new of the eNodeB, next-hop IP address of the eNodeB,
operators destination IP address (service IP address of the S-GW),
subnet mask, and route priority

Neighboring cells of External cells and neighbor relationships

new operators

Hardware Preparation
Prepare the hardware for adding a cell according to Adding an FDD/NB-IoT Cell
> Engineering Preparation > Hardware Preparation or Adding a TDD Cell >
Engineering Preparation > Hardware Preparation. In addition, prepare the
hardware listed in Table 1-98.

Table 1-98 Hardware to be prepared

If... Then...

A new operator and Prepare cables between the eNodeB and the router
the existing operator closest to the eNodeB along the route from the eNodeB
do not share the EPC to the new MME and S-GW. The cables can be Ethernet
cables or optical fibers, depending on the router type.

Software Preparation
If the RET antenna or TMA to be added needs to be upgraded, acquire the latest
software and data from the vendors.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 284

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
according to Table 1-99.

Table 1-99 Data preparation for changing the eNodeB from independent operator
mode to hybrid RAN sharing mode

SN Ope MO Configuration Reference

ratio
n

1 Add CnOpSharingGroup Set a RAN sharing operator group to

which the existing operator belongs.
If the RAN sharing operator group
includes multiple operators, secondary
operators need to be set for the group.
When using MML commands, you need
to run both the ADD
CNOPSHARINGGROUP and ADD
SECONDARYOP2GROUP commands.

2 Modi Cell Set the CN Operator Sharing Group ID

fy to the ID of the previously configured
RAN sharing operator group.

3 Modi ENodeBSharingMode Set the eNodeB sharing mode

fy parameter to HYBRID_SHARED(Hybrid
RAN Sharing).

4 Add CnOperator Add a CnOperator MO for each new

operator.

5 Add CnOpSharingGroup Set one or more RAN sharing operator

groups to which the new operators
belong.
If a RAN sharing operator group
includes multiple operators, secondary
operators need to be set for the group.
When using MML commands, you need
to run both the ADD
CNOPSHARINGGROUP and ADD
SECONDARYOP2GROUP commands.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 285

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

6 Add CnOperatorTa Configure a TAC for each new operator.

7 Add S1 Configure an S1 MO for each new

operator, and add connections to the
MME and S-GW of each new operator.
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

8 Add SCTPTEMPLATE Set the parameters used by each new

operator for SCTP link self-setup.
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

9 Modi S1 Change the relationships between

fy existing S1 MOs and
CnOpSharingGroup MOs.

10 Modi X2 Change the relationships between

fy existing X2 MOs and
CnOpSharingGroup MOs.

11 Add LicenseSharingPolicy Set the maximum proportion of the

number of users allocated to each
operator.

12 Modi CellAlgoSwitch Change the value of RAN Sharing

fy Mode Switch to ON.

13 Add CellOp Set the proportions of uplink and

downlink RBs allocated to each operator.

14 Add LicRatio Set the Traffic Sharing Type parameter

to DEDICATE.

15 Add LicRatioSharePolicy Set the licensed uplink and downlink

traffic proportions for each operator and
the percentage of available resources
one operator can share with other
operators.

16 Modi CellAccess Set the Plmn Broadcast Mode

fy parameter as planned.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 286

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

17 Modi GlobalProcSwitch Set the Different Operator With Same

fy MMEC Switch parameter.
You are advised to set the Different
Operator With Same MMEC Switch
parameter to OFF(Off), that is, set a
unique MMEC for each MME in a TA.
The purpose is to ensure that each UE in
a shared cell has a unique S-TMSI
(which consists of MMEC and M-TMSI,
where M-TMSI is a random value).
MMEs in a TA may belong to different
operators, and therefore MMECs need to
be negotiated among the operators.

18 Add EutranExternalCell Add external cells of the eNodeB.

19 Add EutranExternalCellPlm Add the MCC and MNC of a secondary

n operator involved in RAN sharing.

Data Preparation Mode

You can prepare data using the MAE-Deployment or MML commands. You are
advised to use the batch reconfiguration mode or the radio data planning file of
the MAE-Deployment for batch configuration. The MAE-Deployment GUI is
recommended for configuring a single base station. The four data preparation
modes are described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the MAE-Deployment batch reconfiguration mode (with the name of

the scenario-specific template being "Changing from Independent Operator
Mode to Hybrid RAN Sharing Mode"): For details, see the interactive
operation guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
Deployment to Prepare Data.
● Using the MAE-Deployment-provided radio data planning file
a. On the menu bar, choose LTE Application > Network Adjustment >
Export Radio Network Planning Data to start exporting the radio
network planning data from the system into the radio data planning file.
b. Edit data in the file based on the prepared data. Then, close the file.
c. On the menu bar of the planned data area, choose LTE Application >
Network Adjustment > Import Radio Network Planning Data. A dialog

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 287

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

box is displayed for you to import planned radio data. Import the data
from the file into the system.
For detailed import and export operations, see section Importing and
Exporting Planned Radio Data in the MAE-Access online help.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

Data Preparation Mode

In the following example, the new operator does not share the EPC with the
existing operator, and you need to configure the proportions of the number of
users, traffic, uplink and downlink RBs allocated to each operator, as well as a
neighboring cell working in RAN sharing with common carrier mode.
NOTE

● This example does not include the scripts for adding an MME connection and an S-GW
connection. For these scripts, see Adding an MME Connection > Engineering Preparation >
MML Configuration Script Example and Adding an S-GW Connection > Engineering
Preparation > MML Configuration Script Example.
● This example does not include the script for adding a cell. For the script, see Adding an
FDD/NB-IoT Cell > Engineering Preparation > MML Configuration Script Example or
Adding a TDD Cell > Engineering Preparation > MML Configuration Script Example.
● If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
● You must reset the base station after changing its sharing mode. You are advised to reset the
base station after other MML commands are executed. If a multimode base station is to be
reconfigured, you need to reset the application.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a multi-operator-shared RAN sharing operator group to which the existing operator belongs*/
ADD CNOPSHARINGGROUP: CnOpSharingGroupId=0, PrimaryOperatorId=0;
/*Adding the existing cell to RAN sharing operator group 0*/
MOD CELL: LocalCellId=0, CnOpSharingGroupId=0;
/*Changing the base station sharing mode to hybrid RAN sharing*/
MOD ENODEBSHARINGMODE: ENodeBSharingMode=HYBRID_SHARED;
/*Adding an operator*/
ADD CNOPERATOR: CNOPERATORID=1, CNOPERATORNAME="FIXED",
CNOPERATORTYPE=CNOPERATOR_SECONDARY, MCC="460",MNC="02";
/*Adding a secondary operator to RAN sharing operator group 0*/
ADD SECONDARYOP2GROUP: CnOpSharingGroupId=0, SecondaryOperatorId=1;
/*Adding an operator-dedicated RAN sharing operator group to which the new operator belongs*/
ADD CNOPSHARINGGROUP: CnOpSharingGroupId=1, PrimaryOperatorId=1;
/*Adding a TAC 33 for the new operator*/
ADD CNOPERATORTA: TrackingAreaId=1, CnOperatorId=1, Tac=33;
/*Adding an S1 MO*/
ADD S1: S1Id=0, CnOperatorId=1, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=0, UpEpGroupId=0,
CnOpSharingGroupId=0;
/*Adding an SCTP parameter template*/
ADD SCTPTEMPLATE: SCTPTEMPLATEID=0, SWITCHBACKFLAG=ENABLE;
/*Changing the relationships between existing S1 MOs and CnOpSharingGroup MOs*/
MOD S1: S1Id=0, CnOpSharingGroupId=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 288

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Changing the relationships between existing X2 MOs and CnOpSharingGroup MOs*/

MOD X2: X2Id=3, CnOpSharingGroupId=0;
/*Setting the proportions of both operators' maximum number of users to 50%*/
ADD LICENSESHARINGPOLICY: CnOperatorId=0, MaxUserNumRate=50;
ADD LICENSESHARINGPOLICY: CnOperatorId=1, MaxUserNumRate=50;
/*Changing the value of RanShareModeSwitch to ON*/
MOD CELLALGOSWITCH: LocalCellId=0, RanShareModeSwitch=ON;
/*Setting the proportions of both uplink and downlink RBs to 50%*/
ADD CELLOP: LocalCellId=0, TrackingAreaId=1, OpUlRbUsedRatio=50, OpDlRbUsedRatio=50;
/*Setting the traffic sharing mode to DEDICATE*/
MOD LICRATIO: TrafficSharingType=DEDICATE;
/*Setting the proportions of both operators' traffic to 50%, and setting the proportion of traffic that one
operator can share with the other to 10%*/
ADD LICRATIOSHAREPOLICY: CnOperatorId=0, TrfRatio=50, TrfSharingRatio=10;
ADD LICRATIOSHAREPOLICY: CnOperatorId=1, TrfRatio=50, TrfSharingRatio=10;
/*Setting the PLMN broadcast mode of the cell to RR_MODE*/
MOD CELLACCESS: LocalCellId=0, BroadcastMode=RR_MODE;
/*Prohibiting multiple operators involved in RAN sharing from having the same MMEC*/
MOD GLOBALPROCSWITCH: DiffOpWithSameMmecSwitch=OFF;
/*Adding an external E-UTRAN cell*/
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="01", eNodeBId=526302, CellId=10, DlEarfcn=3350,
UlEarfcnCfgInd=NOT_CFG, PhyCellId=390, Tac=33;
/*Adding PLMN information for the external E-UTRAN cell*/
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="01", eNodeBId=526302, CellId=10, ShareMcc="460",
ShareMnc="00";
/*Resetting the base station*/
RST BTSNODE:;

1.6.3.3 Engineering Implementation

This section describes the engineering implementation for changing the eNodeB
from independent operator mode to hybrid RAN sharing mode, including
prerequisites, context, and procedure.

Prerequisites
● Information for changing the eNodeB from independent operator mode to
hybrid RAN sharing mode has been collected, hardware, software, and
configuration data are ready, and the license file is available in the save path
on the FTP server.
● (Optional) If a new operator does not share the EPC with the existing
operator, the EPC of the new operator has been configured to provide basic
functions.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

(Optional) Connect the cables between the eNodeB and the new MME and S-
GW if the new operator does not share the EPC with the existing operator.
● Remote Operations

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 289

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Using the MAE-Deployment:

NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 290

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iv. After the reconfiguration is complete, set the eNodeB maintenance

mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.6.3.4 Engineering Verification

This section describes how to verify the change from independent operator mode
to hybrid RAN sharing mode.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.
Step 3 Verify that the eNodeB properly communicates with the EPC of the new operator.
For details, see 1.8.1.4 Engineering Verification in Adding an MME Connection
and 1.8.2.4 Engineering Verification in Adding an S-GW Connection.
Step 4 On the main menu of the MAE-Access, choose Monitor > Signaling Trace >
Signaling Trace Management. Then, choose LTE > Application Layer > Uu
Interface Trace from the navigation tree on the left to start a Uu interface tracing
task. In the tracing result, verify that the SIB1 message sent from the cell under
the eNodeB contains the PLMN information of both the new and existing
operators.
If the PLMN information is incomplete, check whether the PLMN information of
the operators in the configuration data file is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
Step 5 Enable UEs of each operator to perform tests to verify that the UEs can
successfully access the network.
If any UE cannot pass the test, check whether the cell is normal.
● If the cell fails to be established, the eNodeB reports an alarm. If this
happens, clear the alarm according to the instructions in 3900 & 5900 Series
Base Station Alarm Reference.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 291

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● If the cell is successfully established, contact Huawei technical support or dial

the Huawei technical support hotline.

----End

1.6.3.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 292

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the cable connections.
Step 4 Verify the engineering rollback.
1. Verify that no cell-related alarm is reported, such as ALM-29240 Cell
Unavailable and ALM-29243 Cell Capability Degraded.
If any cell-related alarm has been reported, clear the alarm according to
instructions in 3900 & 5900 Series Base Station Alarm Reference.
2. Run the DSP CELL command. Verify that Cell instance state is Normal for
the cell.
If Cell instance state is Uninstall, check the cell configuration or hardware
based on the value of Reason for latest state change in the command
output.
3. On the main menu of the MAE-Access, choose Monitor > Signaling Trace >
Signaling Trace Management. Then, choose LTE > Application Layer > Uu
Interface Trace from the navigation tree on the left to start a Uu interface
tracing task. In the tracing result, verify that the SIB1 message sent from the
cell under the eNodeB contains the PLMN information of only the existing
operator.
If the SIB1 message contains PLMN information of other operators, run the
LST CNOPERATOR, LST CNOPERATORTA, and LST CELLOP commands to
check whether there are other operators.
– If there are other operators, run the RMV CELLOP, RMV
CNOPERATORTA, and/or RMV CNOPERATOR commands to remove the
operators.
– If there are no other operators, contact Huawei technical support or dial
the Huawei technical support hotline.

----End

1.6.4 Adding a Neighboring eNodeB

This section describes how to add a neighboring eNodeB for an eNodeB.

1.6.4.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adding a neighboring base
station for an eNodeB.

Application Scenario
The capacity or coverage of a base station cannot meet the service requirement
and therefore a neighboring base station is required.

Reconfiguration Impact
No impact

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 293

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme
When adding a neighboring base station, you must configure the parameters
related to neighboring E-UTRAN cells and information about X2 self-setup. After
the information about X2 self-setup is configured, X2 link self-setup will be
triggered when an S1-based handover is performed for the first time.
Figure 1-48 shows the reconfiguration procedure for adding a neighboring base
station. Determine the reconfiguration scheme according to the following table.

Table 1-100 Scheme options

If… Then...

A new device IP address (old model)/ Add a device IP address (old model) /
IPv4 address (new model)/IPv6 IPv4 address (new model) / IPv6
address (new model) is used for address (new model).
connection with the new base station

No route is available between the local Add a route from the local eNodeB to
eNodeB and the new base station the new base station.

SCTP parameters for the new X2 link Add an SCTP parameter template.
are different from those for other links

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 294

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-48 Configuration procedure for adding a neighboring base station

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 295

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-49 Configuration procedure for adding a neighboring base station

NOTE

MOs related to neighboring cells are as follows:

EutranIntraFreqNCell, EutranInterFreqNCell, EutranExternalCell, EutranInterNFreq,
IntraFreqBlkCell, InterFreqBlkCell, EutranExternalCellPlmn, and EutranNFreqRanShare

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 296

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
The topology of an eNodeB changes when an X2 link from this eNodeB to a
neighboring base station is added. Figure 1-50 shows the topologies before and
after the reconfiguration.

Figure 1-50 Topologies before and after the reconfiguration

1.6.4.2 Engineering Preparation

This section describes the engineering preparation for adding a neighboring
eNodeB for an eNodeB, including information collection and preparation of
hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-101 describes the information to be collected for data preparation.

Table 1-101 Information to be collected

Information Description

Neighboring eNodeB Including:

● Frequency
● Bandwidth
● PLMN
● Physical cell identifier
● Cell identifier

Port number of the -

SCTP host

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 297

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Routing information ● Local device IP address (old model) / IPv4 address

of the X2 link (new model) / IPv6 address (new model) and next-
hop IP address
● IP address of the peer eNodeB or the gateway

Hardware Preparation
Prepare the hardware listed in Table 1-102 before reconfiguration.

Table 1-102 Hardware to be prepared

Hardware Description

eNodeB All devices in an eNodeB

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-103 Data preparation for adding a neighboring eNodeB for an eNodeB

SN Ope MO Configuration Reference

ratio
n

1 Add IPv4: DEVIP For details, see IP eRAN Engineering

Guide Feature Parameter Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 298

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

2 Add IPv4: IPRT/SRCIPRTa For details, see IP eRAN Engineering

Guide Feature Parameter Description.
3 Modi GlobalProcSwitch Set The Switch of X2 setup by SON to
fy ON(On).

4 Add SCTPTEMPLATE For details, see LTE and NR NSA S1 and

X2 Self-Management Feature Parameter
5 Add SCTPHOST Description.
6 Add USERPLANEHOST

7 Add EPGROUP

8 Add X2

9 Add EutranIntraFreqNCell Add information about the new eNodeB

based on actual conditions.
10 Add EutranInterFreqNCell

11 Add EutranExternalCell

12 Add EutranInterNFreq

13 Add IntraFreqBlkCell

14 Add InterFreqBlkCell

15 Add EutranExternalCellPlm
n

16 Add EutranNFreqRanShare

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Table 1-104 Data preparation for adding a neighboring eNodeB for an eNodeB
SN Ope MO Configuration Reference
ratio
n

1 Add IPv4: IPADDR4 For details, see IP eRAN Engineering

IPv6: IPADDR6 Guide Feature Parameter Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 299

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

2 Add IPv4: IPROUTE4/ For details, see IP eRAN Engineering

SRCIPROUTE4a Guide Feature Parameter Description.
IPv6: IPROUTE6

3 Modi GlobalProcSwitch Set The Switch of X2 setup by SON to

fy ON(On).

4 Add SCTPTEMPLATE For details, see LTE and NR NSA S1 and

X2 Self-Management Feature Parameter
5 Add SCTPHOST Description.
6 Add USERPLANEHOST

7 Add EPGROUP

8 Add X2

9 Add EutranIntraFreqNCell Add information about the new eNodeB

based on actual conditions.
10 Add EutranInterFreqNCell

11 Add EutranExternalCell

12 Add EutranInterNFreq

13 Add IntraFreqBlkCell

14 Add InterFreqBlkCell

15 Add EutranExternalCellPlm
n

16 Add EutranNFreqRanShare

a: To simplify configurations when one IPv4 address maps multiple destination

IPv4 addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. To configure base stations in batches, you are advised to use the batch
reconfiguration mode of the MAE-Deployment (for 1 through 8) and the MAE-
Deployment-provided radio data planning file (for 9 through 16). To configure a
single base station, you are advised to using the MAE-Deployment GUI. The four
data preparation modes are described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 300

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Adding a Neighboring eNodeB"): For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment-provided radio data planning file
a. On the menu bar, choose LTE Application > Network Adjustment >
Export Radio Network Planning Data to start exporting the radio
network planning data from the system into the radio data planning file.
b. Edit data in the file based on the prepared data. Then, close the file.
c. On the menu bar of the planned data area, choose LTE Application >
Network Adjustment > Import Radio Network Planning Data. A dialog
box is displayed for you to import planned radio data. Import the data
from the file into the system.
For detailed import and export operations, see section Importing and
Exporting Planned Radio Data in the MAE-Access online help.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The following part uses the scenario where a device IP address, an IP route, and
an SCTP parameter template need to be added as an example to describe the
MML configuration for setting up an X2 link during neighboring eNodeB addition.
Parameter settings for configuring neighboring cells are not provided here.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
/*Adding a device IP address used for communicating with the new eNodeB*/
ADD DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.1.203", MASK="255.255.255.0";
/*Adding an IP route from the local eNodeB to the new eNodeB*/
ADD IPRT:RTIDX=3, SN=7, SBT=BASE_BOARD, DSTIP="192.168.3.3", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.1.1", MTUSWITCH=OFF;
/*Setting The method of X2 setup by SON to X2_OVER_S1*/
MOD GLOBALPROCSWITCH:X2SonLinkSetupType=X2_OVER_S1;
/*Adding an SCTP parameter template*/
ADD SCTPTEMPLATE:SCTPTEMPLATEID=0, SWITCHBACKFLAG=ENABLE;
/*Adding an SCTP host*/
ADD SCTPHOST:SCTPHOSTID=16, IPVERSION=IPv4, SIGIP1V4=" 192.168.1.203",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=1600, SCTPTEMPLATEID=0;
/*Adding a user-plane host*/
ADD USERPLANEHOST:UPHOSTID=16, IPVERSION=IPv4, LOCIPV4="192.168.1.203", IPSECSWITCH=DISABLE;
/*Adding an endpoint group and then adding the user-plane host and the SCTP host to the group*/
ADD EPGROUP:EPGROUPID=16;
ADD SCTPHOST2EPGRP:EPGROUPID=16, SCTPHOSTID=16;
ADD UPHOST2EPGRP:EPGROUPID=16, UPHOSTID=16;
/*Adding an X2 object and configuring the mapping between the X2 object and the endpoint group*/
ADD X2:X2Id=1, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=16, UpEpGroupId=16;

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 301

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Adding a device IP address used for communicating with the new eNodeB*/
SET ETHPORT:CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
ADD INTERFACE:ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD IPADDR4:ITFID=0, IP="192.168.1.203", MASK="255.255.255.0";
/*Adding an IP route from the local eNodeB to the new eNodeB*/
ADD IPROUTE4:RTIDX=3, DSTIP="192.168.3.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.1.1", MTUSWITCH=OFF;
/*Setting The method of X2 setup by SON to X2_OVER_S1*/
MOD GLOBALPROCSWITCH:X2SonLinkSetupType=X2_OVER_S1;
/*Adding an SCTP parameter template*/
ADD SCTPTEMPLATE:SCTPTEMPLATEID=0, SWITCHBACKFLAG=ENABLE;
/*Adding an SCTP host*/
ADD SCTPHOST:SCTPHOSTID=16, IPVERSION=IPv4, SIGIP1V4=" 192.168.1.203",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=1600, SCTPTEMPLATEID=0;
/*Adding a user-plane host*/
ADD USERPLANEHOST:UPHOSTID=16, IPVERSION=IPv4, LOCIPV4="192.168.1.203", IPSECSWITCH=DISABLE;
/*Adding an endpoint group and then adding the user-plane host and the SCTP host to the group*/
ADD EPGROUP:EPGROUPID=16;
ADD SCTPHOST2EPGRP:EPGROUPID=16, SCTPHOSTID=16;
ADD UPHOST2EPGRP:EPGROUPID=16, UPHOSTID=16;
/*Adding an X2 object and configuring the mapping between the X2 object and the endpoint group*/
ADD X2:X2Id=1, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=16, UpEpGroupId=16;

1.6.4.3 Engineering Implementation

This section describes the engineering implementation for adding a neighboring
eNodeB for an eNodeB, including prerequisites, context, and procedure.

Prerequisites
The information and data required for adding a neighboring eNodeB are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
iii. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 302

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see Setting the Maintenance Mode of the eNodeB to

NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.6.4.4 Engineering Verification

This section describes how to verify the addition of a neighboring eNodeB.

Procedure
Step 1 Enable a UE to perform the network accessing test and initiate a handover to the
newly added neighboring eNodeB. After the handover succeeds, run the DSP X2
command. Check the value of X2 Interface State and the expected value is
Normal.
If the value of X2 Interface State is not Normal, perform the following
operations:
1. Check whether the device IP address of the neighboring eNodeB can be
pinged from the device IP address of the X2 interface.
– If the IP address cannot be pinged, go to Step 1.2.
– If the IP address can be pinged, go to Step 1.3.
2. Check the SCTP configuration, including the IP route from the local eNodeB to
the neighboring eNodeB, and whether the Ethernet port mode and rate of the
local eNodeB are the same as those of the neighboring eNodeB.
– If the configuration is incorrect, modify the configuration.
– If the configuration is correct, go to Step 1.4.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 303

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

3. Check whether the value of Peer SCTP Port No. for the SCTP link is the actual
SCTP port number of the neighboring eNodeB.
– If they are different, modify the configuration.
– If they are the same, go to Step 1.4.
4. Check the configuration of the devices between the local eNodeB and the
neighboring eNodeB.
– If the configurations or cable connections are incorrect, modify the
configurations or reconnect the cables.
– If the configurations or cable connections are correct, contact Huawei
technical support or dial the Huawei technical support hotline.
Step 2 Run LST EUTRANINTERNFREQ, LST EUTRANEXTERNALCELL, LST
EUTRANEXTERNALCELLPLMN, LST EUTRANINTRAFREQNCELL, and LST
EUTRANINTERFREQNCELL to verify that the changed parameter values are the
same as planned.
If the values are not the same as planned, check whether the values in the
modified configuration data file are the same as planned:
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.6.4.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 304

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that the rollback has succeeded by referring to operations in 1.6.4.4
Engineering Verification.

----End

1.6.5 Changing the eNodeB Names

This section describes how to change the eNodeB names.

1.6.5.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the eNodeB names.

Application Scenario
The previous eNodeB name plan is inappropriate and a new plan is required.

Reconfiguration Impact
No impact

Reconfiguration Scheme
Rename base stations on the MAE-Access by modifying NE attribute in batches.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 305

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
N/A

1.6.5.2 Engineering Preparation

This section describes the engineering preparation for changing the eNodeB
names, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode.

Information Collection
Table 1-105 describes the information to be collected for data preparation.

Table 1-105 Information Collection

Information Description

eNodeB information The eNodeB information includes the eNodeB IDs as

well as the original and the new eNodeB names.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Prepare the IDs, original names, and new names of eNodeBs to be renamed.

NOTE

For co-MPT multimode base stations:

● NEName is common data. It needs to be adjusted only once and the modification takes
effect for all RATs.
● FunctionName is dedicated to each RAT and needs to be separately configured for each
RAT.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 306

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

N/A

1.6.5.3 Engineering Implementation

This section describes the engineering implementation for changing the eNodeB
names, including prerequisites, context, and procedure.

Prerequisites
Information for changing the eNodeB names has been collected, and
configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
Using the MAE:
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Open the Batch Modify NEs window.

▪ , choose Topology > Batch Modify NEs. Then, the Batch Modify
NEs window is displayed.
c. In the Batch Modify NEs window, click the check box before the eNodeBs
to be renamed, click Query in the lower left corner of the window. After
information about the eNodeB is displayed, click Export in the lower right
corner of the window to export the eNodeB attribute file to the local PC.
The eNodeB attribute file is named similar to the following: Batch
Modify NEs_20140514_110441.csv.
d. Open the eNodeB attribute file, change the eNodeB names in the Name
column to the new names, and save the file as a new one with another
name.
e. Click Import in the lower right of the Batch Modify NEs window to
import the renamed eNodeB attribute file.
f. On the main menu of the MAE-Deployment, choose Area Management
> Current Area > Synchronize NEs to synchronize base station
information to the current data area.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 307

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

g. On the main menu of the MAE-Deployment, choose Area Management

> Planned Area > Synchronize Planned Area NEs to synchronize base
station information to the planned data area.
h. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.6.5.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the eNodeB
names.

Procedure
Step 1 Run the LST ENODEBFUNCTION command and verify that the value of eNodeB
Function Name is the same as planned.
● If it is not the same as planned, perform the operations in Engineering
Implementation again. If the problem persists, contact Huawei technical
support or dial the Huawei technical support hotline.
● If it is the same as planned, the eNodeB is successfully renamed.

----End

1.6.5.5 Engineering Rollback

If the name of a renamed eNodeB needs to be changed back, the eNodeB name
can be rolled back to its original name.

Procedure
Step 1 Perform the rollback. Import the eNodeB attribute file before renaming to change
the eNodeB name back to its original name by referring to e in Engineering
Implementation.

Step 2 Verify that engineering rollback is successful according to instructions in 1.6.5.4

Engineering Verification.

----End

1.6.6 Changing the eNodeB ID

This section describes how to change the eNodeB ID.

1.6.6.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the eNodeB ID.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 308

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Application Scenario
The previous eNodeB ID plan is inappropriate and a new plan is required.

Reconfiguration Impact
After the base station ID is changed, the MAE-Deployment activates the changed
data on the live network. When the activation takes effect, the application resets
to make the reconfiguration take effect. During the reset, the eNodeB cannot
provide services.

Reconfiguration Scheme
To modify an eNodeB ID, you need to change the eNodeB ID value in the
eNodeBFunction MO to the target value.
● If a CaGroupCell MO has been configured on the eNodeB, the eNodeB ID
parameter value in this MO is accordingly changed to the target value.
● If the eNodeB ID parameter in any of the following MOs configured on a
neighboring eNodeB references the eNodeB ID parameter in the
eNodeBFunction MO, the eNodeB ID parameters in these MOs are
accordingly changed to the target value:
– SfnAuxResBind
– EutranExternalCell
– EutranIntraFreqNCell
– EutranInterFreqNCell
– EutranExternalCellPlmn
● Use the customized batch configuration template to modify parameters in the
following MOs if involved:
– CellAuxEnbBind
– SfnAuxResGrpBind
– CspcCellSrsMeasNCell
– ClusterCell
– SfnEdgeRruRelation

Topology Change
N/A

1.6.6.2 Engineering Preparation

This section describes the engineering preparation for changing the eNodeB ID,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode.

Information Collection
Table 1-106 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 309

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-106 Information Collection

Information Description

eNodeB information The eNodeB information includes the original and new
eNodeB IDs.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Prepare data listed in the following table.

Table 1-107 Data preparation for changing the eNodeB ID

SN Ope MO Configuration Reference

ratio
n

1 Modi eNodeBFunction Change the value of eNodeB ID to the

fy target value.

2 Modi CaGroupCell The value of eNodeB ID is accordingly

fy changed to the target value.

3 Modi EutranExternalCell on
fy a neighboring eNodeB

4 Modi EutranIntraFreqNCell
fy on a neighboring
eNodeB

5 Modi EutranInterFreqNCell
fy on a neighboring
eNodeB

6 Modi EutranExternalCellPlm
fy n on a neighboring
eNodeB

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 310

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

7 Modi X2BlackWhiteList on a
fy neighboring eNodeB

8 Modi SfnAuxResBind on the Change the value of Main eNodeB ID to

fy auxiliary eNodeB the target value.

9 Modi CellAuxEnbBind Change the value of Slave site eNodeB

fy ID to the target value.

10 Modi SfnAuxResGrpBind Change the value of Main eNodeB ID to

fy the target value.

11 Modi CspcCellSrsMeasNCell Change the value of eNodeB ID to the

fy target value.

12 Modi ClusterCell Change the value of eNodeB ID to the

fy target value.

13 Modi SfnEdgeRruRelation Change the value of eNodeB ID to the

fy target value.

Data Preparation Mode

You are advised to use the MAE-Deployment-provided "ID/Name modification".
Data preparation of this method is as follows:
NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
To prepare data using the MAE-Deployment, choose Advanced > System > Options. In the
displayed Options dialog box, choose Cell Parameter Auto-Synchronization Policy in the left
pane and then select the Auto synchronize cell parameters in the entire network check box
in the right pane. Then click OK.

1. On the menu bar, choose LTE Application > Network Adjustment > Export
ID/Name Adjustment Data to start exporting the eNodeB name and ID, cell
ID, local cell ID, and cell name from the system to a file.
2. In the ID Modification Of eNodeB sheet of the file, modify the eNodeB ID
parameter value of the eNodeB to the target value. Then, save the
modification and close the file.
3. On the menu bar, choose LTE Application > Network Adjustment > Import
ID/Name Adjustment Data to start data import from the file to the system.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 311

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If some neighboring base stations of the base station are not provided in the planned area
during the data import, a prompt indicating that NEs are missed will be displayed on the
system and provides the NE names because the Auto synchronize cell parameters in the
entire network check box has been selected. In this case, choose Area Management >
Planned Area > Planned Area Management to open the modified planned area. Add the
eNodeBs whose parameters need to be changed accordingly to the planned area. Then,
repeat steps 1 to 3.

For detailed import and export operations, see section Importing and Exporting
Names and IDs in the MAE-Access online help.

NOTE

If the reconfiguration is performed using MML commands, remove all MOs related to the
original eNodeB ID first, and then add the removed MOs one by one with eNodeB ID changed
to the target value. For details about how to add and remove an MO, see the MML command
reference.

1.6.6.3 Engineering Implementation

This section describes the engineering implementation for changing the eNodeB
ID, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
Using the MAE-Deployment:
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Run the LST GLOBALPROCSWITCH command to query the values of the
following parameters: The Switch of X2 setup by SON, Peer Request
Based X2 Delete Switch, X2 SON Delete Switch, Interface Setup Policy
Switch, The Timer of X2 delete by SON, and X2-based Neighboring
Cell Configuration Update Switch.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 312

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

▪ Skip this step if the The Timer of X2 delete by SON parameter is 0,

the LTE_NR_X2_SON_SETUP_SW option of the Interface Setup
Policy Switch parameter is deselected, and the options of all the
other preceding parameters are deselected.

▪ If The Timer of X2 delete by SON parameter is not 0, the

LTE_NR_X2_SON_SETUP_SW option of the Interface Setup Policy
Switch parameter is selected, or the options of all the other
preceding parameters are selected, run the MOD
GLOBALPROCSWITCH command to set the The Timer of X2 delete
by SON parameter to 0 and deselect all these options. Example:
MOD GLOBALPROCSWITCH: X2SonSetupSwitch=OFF,
X2SonDeleteTimer=0, PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2USAGE
_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-0,
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_NCELL
_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD_FREQ_CFG_SW-0&UPT_
EXTERNALCELLBAND_CFG_SW-0,
InterfaceSetupPolicySw=X2_SON_INTER_OP_SETUP_FBD_SW-1&LT
E_NR_X2_SON_SETUP_SW-0;
c. Run the LST ENODEBALGOSWITCH command to check whether the
options of ANR algorithm switch are selected.

▪ If all the options of this parameter are deselected, skip this step.

▪ If any option is selected, run the MOD ENODEBALGOSWITCH

command with all options of the ANR algorithm switch parameter
deselected. Example: MOD ENODEBALGOSWITCH:
AnrSwitch=IntraRatEventAnrSwitch-0&IntraRatFastAnrSwitch-0&I
ntraRatAnrAutoDelSwitch-0&UtranEventAnrSwitch-0&GeranEven
tAnrSwitch-0&UtranFastAnrSwitch-0&GeranFastAnrSwitch-0&Cd
maFastAnrSwitch-0&UtranAutoNrtDeleteSwitch-0&GeranAutoNr
tDeleteSwitch-0&CdmaAutoNrtDeleteSwitch-0&CdmaEventAnrS
witch-0;
d. Deliver the configuration data to the base station and activate the data.
For details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
e. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
f. Restore the settings of the options changed in b and c.
----End

1.6.6.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the eNodeB
ID.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 313

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Run the LST ENODEBFUNCTION command on the eNodeB and verify that the
value of eNodeB ID is the same as planned.
If the value of eNodeB ID is not the same as planned, check whether the value of
eNodeB ID in the modified configuration data file is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
Step 2 Run the LST CAGROUPCELL command on the eNodeB and verify the value of
eNodeB ID is the same as planned.
If the value of eNodeB ID is not the same as planned, check whether the value of
eNodeB ID in the modified configuration data file is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
Step 3 Run the LST EUTRANEXTERNALCELL command on a neighboring eNodeB to
verify that the value of eNodeB ID is the same as planned.
If the value of eNodeB ID is not the same as planned, check whether the value of
eNodeB ID in the modified configuration data file is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
Step 4 Run the LST EUTRANINTRAFREQNCELL command on a neighboring eNodeB to
verify that the value of eNodeB ID is the same as planned.
If the value of eNodeB ID is not the same as planned, check whether the value of
eNodeB ID in the modified configuration data file is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 314

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 5 Run the LST EUTRANINTERFREQNCELL command on a neighboring eNodeB to

verify that the value of eNodeB ID is the same as planned.

If the value of eNodeB ID is not the same as planned, check whether the value of
eNodeB ID in the modified configuration data file is the same as planned.

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

Step 6 Run the LST EUTRANEXTERNALCELLPLMN command on a neighboring eNodeB

to verify that the value of eNodeB ID is the same as planned.

If the value of eNodeB ID is not the same as planned, check whether the value of
eNodeB ID in the modified configuration data file is the same as planned.

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

Step 7 Run the LST SFNAUXRESBIND command to verify that the value of Main eNodeB
ID is the same as planned.

If the value of Main eNodeB ID is not the same as planned, check whether the
value of Main eNodeB ID in the modified configuration data file is correct.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

Step 8 Verify that ALM-29201 S1 Interface Fault is not generated.

If the alarm is generated after the reconfiguration, the new eNodeB ID may be in
conflict with another eNodeB ID. Check whether the new eNodeB ID is in conflict
with another eNodeB ID.
● If it is not in conflict with another eNodeB ID, clear the alarm by referring to
3900 & 5900 Series Base Station Alarm Reference.
● If it is in conflict with another eNodeB ID, plan the eNodeB ID and modify the
configuration data file again. Import the configuration file into the system.
Then perform Engineering Implementation again to deliver the
configuration data to the eNodeB and activate the data.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 315

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.6.6.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Roll back the configuration data.

Use the MAE-Deployment to roll back the configuration data.

Step 2 Verify that engineering rollback is successful according to instructions in 1.6.6.4

Engineering Verification.

----End

1.6.7 Adjusting the PLMN

This section describes how to adjust the PLMN.

1.6.7.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adjusting the PLMN.

Application Scenario
The previous PLMN plan is inappropriate and a new plan is required.

Reconfiguration Impact
After the PLMN is adjusted, the base station needs to be reset to make the
reconfiguration take effect. During the reset, the base station cannot provide
services.

Reconfiguration Scheme
Before adjusting the eNodeB configuration, change the PLMN to the target value
on the MME connecting to the eNodeB, so that the PLMN configuration on the
eNodeB and that on the MME are the same.

A PLMN consists of MCC and MNC, which are key in X2BlackWhiteList,

EutranExternalCellPlmn, EutranIntraFreqNCell, EutranInterFreqNCell,
EutranExternalCell, and EutranNFreqRanShare MOs. These MOs must be
removed before you change the PLMN and then added back after the PLMN
change. You are advised to modify these MOs in batches using the MAE-
Deployment.

Parameter values in the following MOs can be changed automatically based on

their related MOs:

● EutranExternalCell
● EutranIntraFreqNCell

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 316

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● EutranInterFreqNCell
● EutranExternalCellPlmn
● EutranNFreqRanShare
Use the customized batch configuration template to modify parameters in the
following MOs if involved:
● SCTPPEER
● USERPLANEPEER
● SCTPLNK
● X2AutoSetupOperator
● X2BlackWhiteList
● ClusterCell
● CspcCellSrsMeasNCell
● SfnEdgeRruRelation
● SpidHPlmnList
● NCellPlmnList
Figure 1-51 shows the reconfiguration procedure using the MAE-Deployment.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 317

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-51 Procedure for adjusting the PLMN

Topology Change
N/A

1.6.7.2 Engineering Preparation

This section describes the engineering preparation for adjusting the PLMN,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-108 describes the information to be collected before the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 318

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-108 Information to be collected

Information Description

Neighboring cell Indicates the intra- and inter-frequency neighboring

information cells where the PLMN that needs to be changed.

Operator information Includes the MNCs and MCCs before and after the
PLMN is changed, external cell PLMN list, RAN sharing
information of neighboring frequencies, and X2 blacklist
and whitelist.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-109 Data preparation for adjusting the PLMN

SN Ope MO Configuration Reference

ratio
n

1 Modi SCTPPEER Change the PLMN information in the

fy Remote ID and User Label parameters
to the target value. These parameters
2 Modi USERPLANEPEER include the information about the
fy shared MNC and shared MCC.

3 Modi SCTPLNK Change the PLMN information in the

fy Description Info parameter to the
target value. This parameter includes
the information about the shared MNC
and shared MCC.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 319

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

4 Modi X2AutoSetupOperator Change the Mobile network code and

fy Mobile country code parameter values
to the target values.
5 Modi CnOperator
fy

6 Modi X2BlackWhiteList
fy

7 Modi EutranExternalCellPlm Change the Mobile network code,

fy n Mobile country code, Share mobile
country code, and Share mobile
network code parameter values to the
target values.

8 Modi EutranIntraFreqNCell Change the Mobile network code and

fy Mobile country code parameter values
to the target values.
9 Modi EutranInterFreqNCell
fy

10 Modi EutranExternalCell
fy

11 Modi EutranNFreqRanShare
fy

12 Modi ClusterCell
fy

13 Modi CspcCellSrsMeasNCell
fy

14 Modi SfnEdgeRruRelation
fy

15 Modi SpidHPlmnList
fy

16 Modi NCellPlmnList
fy

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 320

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the batch configuration mode of the MAE-Deployment. For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.

NOTICE

To adjust the PLMN, you must select Auto synchronize cell parameters in a
planned area in Settings > Deployment > Cell Parameter Auto-
Synchronization Policy on the MAE. Otherwise, data verification will fail
after data is imported using the batch configuration mode.

NOTE

The parameter values of the EutranExternalCellPlmn, EutranIntraFreqNCell,

EutranInterFreqNCell, EutranExternalCell, and EutranNFreqRanShare MOs are changed by
the MAE-Deployment automatically based on their related MOs and do not require
manual configuration. If the parameters of any other MO are to be modified, modify them
by using the batch configuration mode.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In this example, the MCC of the PLMN remains 460 and the MNC is changed from
01 to 20.
If an intra-frequency or inter-frequency neighboring cell exists, remove the
neighbor relationship first.
/*Removing the intra-frequency E-UTRAN neighbor relationship with cell 2*/
RMV EUTRANINTRAFREQNCELL: CELLID=2;
/*Removing the inter-frequency E-UTRAN neighbor relationship with cell 2*/
RMV EUTRANINTERFREQNCELL: CELLID=2;
/*Removing cell 2 from the HPLMN to which SPID-specific UEs are allowed to be handed over*/
RMV SPIDHPLMNLIST:STARTSPID=1,ENDSPID=4,MCC="460",MNC="01";
/*Removing cell 2 from the neighboring cell PLMN list*/
RMV NCELLPLMNLIST:MCC="460",MNC="01",RATTYPE=EUTRAN;
/*Adding a list of HPLMNs to which SPID-specific UEs are allowed to be handed over*/
ADD SPIDHPLMNLIST:STARTSPID=1,ENDSPID=4,MCC="460",MNC="20";
/*Adding a neighboring cell PLMN list with the value of the PlmnListType parameter being the same as that
in the removed MO*/
ADD NCELLPLMNLIST:MCC="460",MNC="20",RATTYPE=EUTRAN,PLMNLISTTYPE=WHITE_LIST;
/*Adding an intra-frequency neighboring E-UTRAN cell*/
ADD EUTRANINTRAFREQNCELL: LOCALCELLID =1, MCC="460", MNC="20", ENODEBID=255, CELLID=200;
/*Adding an inter-frequency neighboring E-UTRAN cell*/
ADD EUTRANINTERFREQNCELL: LOCALCELLID =1, MCC="460", MNC="20", ENODEBID=255, CELLID=200;
/*Modifying the SCTP peer*/
MOD
SCTPPEER:SCTPPEERID=0,PN=1090,REMOTEID="eNB:MCC_460MNC_20LTEinOneeeNBID_460MNC_20-2",USE
RLABEL="SigPlanePeer";
/*Modifying the user-plane peer*/
MOD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, PEERIPV4="195.168.1.29";
/*Adding information about an operator that supports X2 self-setup*/
ADD X2AUTOSETUPOPERATOR: Mcc="460", Mnc="20";
/*Removing information about an operator that supports X2 self-setup*/
RMV X2AUTOSETUPOPERATOR: Mcc="460", Mnc="01";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 321

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Adding a blacklist and a whitelist for the X2 interface*/

ADD X2BLACKWHITELIST: MCC="460", MNC="20", ENodeBId=255, X2ListType=X2_BLACK_LIST_TYPE;
/*Removing the blacklist and whitelist for the X2 interface*/
RMV X2BLACKWHITELIST: MCC="460", MNC="01", ENodeBId=255;
/*Modifying the operator information*/
MOD CNOPERATOR:CNOPERATORID=0,CNOPERATORNAME="LTE", MCC="460",MNC="20";
/*Adding the PLMN list for an external cell*/
ADD EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="20", eNodeBId=255, CellId=1, ShareMcc="460",
ShareMnc="21";
/*Removing the PLMN list of an external cell*/
RMV EUTRANEXTERNALCELLPLMN: Mcc="460", Mnc="01", eNodeBId=255, CellId=1, ShareMcc="460",
ShareMnc="02";
/*Adding an external E-UTRAN cell*/
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=255, CellId=1, DlEarfcn=3000,
UlEarfcnCfgInd=CFG, UlEarfcn=21000, PhyCellId=1, Tac=1;
/*Removing an external E-UTRAN cell*/
RMV EUTRANEXTERNALCELL: Mcc="460", Mnc="01", eNodeBId=255, CellId=1;
/*Adding the information about an operator that shares a neighboring E-UTRAN frequency with other
operators*/
ADD EUTRANNFREQRANSHARE: LocalCellId=0, DlEarfcn=1234, Mcc="460", Mnc="20",
CellReselPriorityCfgInd=NOT_CFG;
/*Removing the information about an operator that shares a neighboring E-UTRAN frequency with other
operators*/
RMV EUTRANNFREQRANSHARE: LocalCellId=0, DlEarfcn=1234, Mcc="460", Mnc="01"; /*Removing a cell
from the cell cluster*/ RMV CLUSTERCELL:CLUSTERID=1,MCC="460",MNC="01",ENODEBID=1,CELLID=1; /
*Removing the neighboring cell relationship of the local CSPC cell for SRS measurement*/ RMV
CSPCCELLSRSMEASNCELL:MCC="1",MNC="460",ENODEBID=1,CELLID=1,NCELLMCC="460",NCELLMNC="1",
NCELLENODEBID=2,NCELLID=2; /*Adding a cell to the cell cluster*/ ADD
CLUSTERCELL:CLUSTERID=1,MCC="460",MNC="20",ENODEBID=1,CELLID=1; /*Adding a neighboring cell (for
SRS measurement) for the local CSPC cell*/ ADD
CSPCCELLSRSMEASNCELL:MCC="460",MNC="20",ENODEBID=1,CELLID=1,NCELLMCC="460",NCELLMNC="20
",NCELLENODEBID=2,NCELLID=2; /*Modifying the relationship between RRUs in edges of neighboring SFN
cells*/ MOD SFNEDGERRURELATION:LOCALCELLID=1,SECTOREQMID=1,MCC="460",MNC="20";
/*Resetting the base station*/
RST BTSNODE:;

1.6.7.3 Engineering Implementation

This section describes the engineering implementation for adjusting the PLMN,
including prerequisites, context, and procedure.

Prerequisites
Required information and data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations

Using the MAE-Deployment:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 322

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Run the LST GLOBALPROCSWITCH command to query the values of the
following parameters: The Switch of X2 setup by SON, Peer Request
Based X2 Delete Switch, X2 SON Delete Switch, Interface Setup Policy
Switch, The Timer of X2 delete by SON, and X2-based Neighboring
Cell Configuration Update Switch.

▪ Skip this step if the The Timer of X2 delete by SON parameter is 0,

the LTE_NR_X2_SON_SETUP_SW option of the Interface Setup
Policy Switch parameter is deselected, and the options of all the
other preceding parameters are deselected.

▪ If The Timer of X2 delete by SON parameter is not 0, the

LTE_NR_X2_SON_SETUP_SW option of the Interface Setup Policy
Switch parameter is selected, or the options of all the other
preceding parameters are selected, run the MOD
GLOBALPROCSWITCH command to set the The Timer of X2 delete
by SON parameter to 0 and deselect all these options. Example:
MOD GLOBALPROCSWITCH: X2SonSetupSwitch=OFF,
X2SonDeleteTimer=0, PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2USAGE
_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-0,
X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0&MOD_NCELL
_CFG_SW-0&DEL_NCELL_CFG_SW-0&ADD_FREQ_CFG_SW-0&UPT_
EXTERNALCELLBAND_CFG_SW-0,
InterfaceSetupPolicySw=X2_SON_INTER_OP_SETUP_FBD_SW-1&LT
E_NR_X2_SON_SETUP_SW-0;
c. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
d. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
e. Deliver the configuration data to the eNodeB and activate the data. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
f. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 323

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see Setting the Maintenance Mode of the eNodeB to

NORMAL.

Using MML commands:

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
d. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.6.7.4 Engineering Verification

This section describes how to verify the reconfiguration for adjusting the PLMN.

Procedure
Step 1 Verify that no cell-related alarm has been reported.

If any alarm has been reported, clear the alarm according to instructions in 3900
& 5900 Series Base Station Alarm Reference.

Step 2 Check the eNodeB configuration.

On the MAE-Access or LMT, export the configuration file in the XML format after
the reconfiguration. Check whether the reconfiguration is the same as planned.

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 324

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
----End

1.6.7.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 325

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 2 Restore the physical connections.

Step 3 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 4 Verify that engineering rollback is successful according to instructions in
Engineering Verification.

----End

1.7 Device Data Reconfigurations

This section describes how to reconfigure eNodeB device data in typical scenarios.

1.7.1 Replacing the Main Control Board When No SeGW Is

Deployed
This section describes how to replace a main control board when no SeGW is
deployed.

NOTE

Unless otherwise specified, UMPT herein represents all UMPT boards.

5900 series base stations do not support any scenario involving LMPT boards. If such a scenario
exists, adjust it based on site requirements.

1.7.1.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for replacing a main control board.

Application Scenario
A main control board needs to be replaced if it cannot meet service requirements.
The transmission interface capabilities and attributes vary with the main control
board types. Therefore, during board replacement, reconfigure data based on
different schemes.

Reconfiguration Impact
After replacing the main control board, you must power off and power on the
base station to make the configuration take effect. During the operation, the base
station cannot provide services.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 326

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme
NOTE

● After the main control board is replaced, the Media Access Control (MAC) address of the
board is changed. If the MAC address is used by the transport network, inform the transport
network maintenance personnel of the change and ask them to modify the configurations.
● After the main control board is replaced, the default password of the default LMT account
used for locally logging in to base stations varies between versions. For details, see section
"Logging In to and Logging Out of the LMT" in 3900 & 5900 Series Base Station LMT User
Guide.

Table 1-110 UMPT scheme options

Replaceme Transmission Transmission Transmission Board Type
nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

UMPTa/ Electrical port Electrical ports ● Adjustment Set the Board

UMPTb- 0 0 and 2 is not Specification
>UMPTe/ required if parameter to
UMPTg/ port 0 is UMPTe/
UMPTga still used UMPTg/
after the UMPTga.
board
replacemen
t.
● The
correspondi
ng port
number in
transmissio
n-related
MOs needs
to be
changed to
2 if port 2
is used
after the
board
replacemen
t.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 327

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

Optical port 1 Optical ports 1 ● Adjustment

and 3 is not
required if
port 1 is
still used
after the
board
replacemen
t.
● The
correspondi
ng port
number in
transmissio
n-related
MOs needs
to be
changed to
3 if port 3
is used
after the
board
replacemen
t.

LMPT- Optical port 0 Optical port 1 Change the ● Set the

>UMPTa/ corresponding Board Type
UMPTba port number parameter
in to UMPT.
transmission- ● Set the
related MOs Board
to 1. Specificati
Electrical port Electrical port Change the on
1 0 corresponding parameter
port number to
in UMPTa/b.
transmission-
related MOs
to 0.

Electrical port Electrical port Adjustment is

0 0 not required.

Optical port 1 Optical port 1 Adjustment is

not required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 328

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

LMPT- Optical port 0 Optical ports 1 Change the ● Set the

>UMPTe/ and 3 corresponding Board Type
UMPTg/ port number parameter
UMPTgaa in to UMPT.
transmission- ● Set the
related MOs Board
to 1 or 3. Specificati
Electrical port Electrical ports Change the on
1 0 and 2 corresponding parameter
port number to UMPTe/
in UMPTg/
transmission- UMPTga.d
related MOs
to 0 or 2.

Electrical port Electrical ports ● Adjustment

0 0 and 2 is not
required if
port 0 is
still used
after the
board
replacemen
t.
● The
correspondi
ng port
number in
transmissio
n-related
MOs needs
to be
changed to
2 if port 2
is used
after the
board
replacemen
t.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 329

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

Optical port 1 Optical ports 1 ● Adjustment

and 3 is not
required if
port 1 is
still used
after the
board
replacemen
t.
● The
correspondi
ng port
number in
transmissio
n-related
MOs needs
to be
changed to
3 if port 3
is used
after the
board
replacemen
t.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 330

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

UMPTa/ Electrical port Electrical ports ● Adjustment ● Set the

UMPTb- 0 0 and 1 is not Board Type
>LMPTc required if parameter
port 0 is to LMPT.
still used ● Set the
after the Board
board Specificati
replacemen on
t. parameter
● The to null
correspondi character
ng port string.
number in
transmissio
n-related
MOs needs
to be
changed to
1 if port 1
is used
after the
board
replacemen
t.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 331

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

Optical port 1 Optical ports 0 ● Adjustment

and 1 is not
required if
port 0 is
still used
after the
board
replacemen
t.
● The
correspondi
ng port
number in
transmissio
n-related
MOs needs
to be
changed to
1 if port 1
is used
after the
board
replacemen
t.

UMPTe- Electrical ports Electrical ports Adjustment is Set the Board

>UMPTg/ 0 and 2 0 and 2 not required. Specification
UMPTga parameter to
Optical ports 1 Optical ports 1 Adjustment is UMPTg/
and 3 and 3 not required. UMPTga.

UMPTga- Electrical ports Electrical ports Adjustment is Set the Board

>UMPTg 0 and 2 0 and 2 not required. Specification
parameter to
Optical ports 1 Optical ports 1 Adjustment is UMPTg.
and 3 and 3 not required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 332

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

a: If the LMPT is configured with two optical ports or two electrical ports, and
the next-hop IP addresses of the two ports are not in the same VLAN, data
needs to be reconfigured for the network after the LMPT is replaced with a
UMPT. Then, perform the reconfiguration according to the reconfiguration
scheme in the preceding table.
b: Transmission-port-related MOs include:
● IPv4: old model
The Transmission Configuration Mode parameter in the GTRANSPARA MO
is set to OLD.
ETHPORT, DOT1X, IPPATH, CFMMEP, RSCGRP, IP2RSCGRP, RSCGRPALG,
PORTSECURITY, LR, EP2RSCGRP, DEVIP, ETHOAM3AH, ETHTRK, and
ETHTRKLNK
● IPv4: new model
The Transmission Configuration Mode parameter in the GTRANSPARA MO
is set to NEW.
ETHPORT, DOT1XAUTH, IPPATH, CFMLOCALMEP, IPRSCGRP, PORTSECURITY,
PORTLR, ETH3AH, ETHTRUNK, ETHTRUNKLNK, INTERFACE, LOOPBACK,
ETHCIPORT, LLDP, LSWPORT, and BACKTUNNEL
● IPv6:
ETHPORT, DOT1XAUTH, CFMLOCALMEP, IPRSCGRP, PORTSECURITY, PORTLR,
INTERFACE, LOOPBACK, and LLDP
c: The maximum transmission bandwidth supported by the UMPT is greater
than that supported by the LMPT. If the sum of transmission bandwidths of
logical resource groups configured on the old UMPT is greater than the
maximum transmission bandwidth supported by the new LMPT and the
bandwidth configuration is not changed, logical resource groups cannot be
generated when the UMPT is replaced with the LMPT. As a result, IP paths
become unusable and services are affected. In this scenario, bandwidth
configurations must be replanned. The LMPT supports only IPv4 transmission.
d: The LMPT supports only the BBU3900, and the UMPTg does not support the
BBU3900. Therefore, the BBU also needs to be replaced when replacing an
LMPT with a UMPTg. Data cannot be directly reconfigured for the replacement
of an LMPT with a UMPTg. Perform the following steps to reconfigure data:
1. Replace the LMPT with a UMPTe.
2. Replace the UMPTe with a UMPTg and replace the BBU with a BBU5900 or
BBU3910.
● Set the Board Type parameter in the MPT MO to UMPTg.
● Change the Subrack Type parameter in the SUBRACK MO to BBU3910 or
BBU5900.

Topology Change
The topology changes when the LMPT using optical port 0 or electrical port 1 is
replaced with a UMPT. The topology does not change when the LMPT using

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 333

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

optical port 1 or electrical port 0 is replaced with a UMPT or when the UMPT is
replaced with an LMPT.
Use the scenario where an LMPT using optical port 0 is replaced with a UMPT
using optical port 1 as an example. Figure 1-52 shows the topologies before and
after the reconfiguration.

Figure 1-52 Topology Change

Use the scenario where an LMPT using electrical port 1 is replaced with a UMPTg
using electrical port 2 as an example. Figure 1-53 shows the topologies before
and after the reconfiguration.

Figure 1-53 Topologies before and after the reconfiguration

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 334

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.7.1.2 Engineering Preparation

This section describes the engineering preparation for replacing a main control
board when no SeGW is deployed, including information collection and
preparation of hardware, software, license files, security certificates, and data. It
also describes the data preparation mode.

Information Collection
Table 1-111 describes the information to be collected for data preparation.

Table 1-111 Information to be collected

Information Description

Configuration data The latest configuration data that is manually exported

file of the original before the reconfiguration. For details, see Exporting
main control board Deployment Lists and Configuration Files of Base
Stations in 3900 & 5900 Series Base Station Initial
Configuration Guide.

Hardware Preparation
Prepare the hardware listed in Table 1-112.

Table 1-112 Hardware to be prepared

If... Then...

A UMPTa/UMPTb Prepare an LMPT.

needs to be replaced
with an LMPT

An LMPT needs to be Prepare a UMPT and a local maintenance adapter.

replaced with a
UMPTa

A UMPTa/UMPTb Prepare a UMPTe/UMPTg/UMPTga

needs to be replaced
with a UMPTe/
UMPTg/UMPTga

A UMPTe needs to be Prepare a UMPTg/UMPTga.

replaced with a
UMPTg/UMPTga

A UMPTga needs to Prepare a UMPTg.

be replaced with a
UMPTg

a: If an LMPT needs to be replaced with a UMPTg, you need to replace the

BBU3900 with a BBU3910 or BBU5900 first.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 335

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation
If the version of the new main control board is different from that of the main
control board to be replaced, collect information about the software version of the
main control board to be replaced.

License File Preparation

Keep a new license ready if no license file is loaded to the new main control
board, the control items in the license file cannot meet service requirements, or
the license has expired.

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Old Model

Table 1-113 Data preparation for replacing a main control board

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

Repl 1 Mod MPT ● Set the Board Type parameter

ace ify to UMPT.
an ● Change the value of the Board
LMP Specification parameter.
T
with – If the board is replaced with
a a UMPTa/UMPTb, set the
UM Board Specification
PT. parameter to UMPTa/b.
– If the board is replaced with
a UMPTe/UMPTga, set the
Board Specification
parameter to UMPTe/
UMPTga.
– If the board is replaced with
a UMPTg, data cannot be
reconfigured directly and
you need to perform the
operations described in
Note. This is because the
LMPT supports only the
BBU3900, but the UMPTg
does not support the
BBU3900.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 336

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

2 Mod ETHPORT If the board is replaced with a

ify UMPTa/UMPTb:

3 Mod DOT1X ● If optical port 0 on the LMPT is

ify used, set the Port No.
parameter to 1.
4 Mod IPPATH ● If electrical port 1 on the LMPT
ify is used, set the Port No.
5 Mod CFMMEP parameter to 0.
ify If the board is replaced with a
UMPTe:
6 Mod RSCGRP
ify ● If optical port 0 on the LMPT is
used, set the Port No.
7 Mod IP2RSCGRP parameter to 1 or 3.
ify
● If electrical port 1 on the LMPT
8 Mod RSCGRPALG is used, set the Port No.
ify parameter to 0 or 2.

9 Mod PORTSECURITY
ify

10 Mod LR
ify

11 Mod EP2RSCGRP
ify

12 Mod DEVIP
ify

13 Mod ETHOAM3AH
ify

14 Mod ETHTRK
ify

15 Mod ETHTRKLNK
ify

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTe/UMPTg/
a UMPTga.
UM
PTa/ 2 Mod ETHPORT ● Modification is not required if
UM ify the transmission port is not
PTb changed after the board
3 Mod DOT1X replacement.
with ify
a
UM

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 337

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

PTe/ 4 Mod IPPATH ● The corresponding port

UM ify number in transmission-related
PTg/ MOs needs to be set to 2 if
UM 5 Mod CFMMEP port 2 is used after the board
PTga ify replacement.
. 6 Mod RSCGRP ● The corresponding port
ify number in transmission-related
MOs needs to be changed to 3
7 Mod IP2RSCGRP if port 3 is used after the board
ify replacement.
8 Mod RSCGRPALG
ify

9 Mod PORTSECURITY
ify

10 Mod LR
ify

11 Mod EP2RSCGRP
ify

12 Mod DEVIP
ify

13 Mod ETHOAM3AH
ify

14 Mod ETHTRK
ify

15 Mod ETHTRKLNK
ify

Repl 1 Mod MPT ● Set the Board Type parameter

ace ify to LMPT.
a ● Set the Board Specification
UM parameter to null character
PTa/ string.
UM
PTb
with
an
LMP
T.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 338

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTg/UMPTga.
a
UM
PTe
with
a
UM
PTg/
UM
PTga
.

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTg.
a
UM
PTga
with
a
UM
PTg.

Note: You are advised to use the MAE-Deployment, which supports automatic
update of the corresponding port number in the associated MOs when a port
number of the main control board is changed. For details, see iMaster MAE
Product Documentation > Operation and Maintenance > MAE-Deployment
Operation and Maintenance > MAE-Deployment Guidelines > Changing
Base Station MPT Boards and Ports.

New Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 339

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-114 Data preparation for replacing a main control board

Cha SN Ope MO Configuration Reference
nge rati
Mod on
el

Repl 1 Mod MPT ● Set the Board Type parameter

ace ify to UMPT.
an ● Change the value of the Board
LMP Specification parameter.
T
with – If the board is replaced with
a a UMPTa/UMPTb, set the
UM Board Specification
PT. parameter to UMPTa/b.
– If the board is replaced with
a UMPTe/UMPTga, set the
Board Specification
parameter to UMPTe/
UMPTga.
– If the board is replaced with
a UMPTg, data cannot be
reconfigured directly and
you need to perform the
operations described in
Note. This is because the
LMPT supports only the
BBU3900, but the UMPTg
does not support the
BBU3900.

2 Mod ETHPORT If the board is replaced with a

ify UMPTa/UMPTb:
● If optical port 0 on the LMPT is
3 Mod ETHCIPORT
used, set the Port No.
ify
parameter to 1.
4 Mod INTERFACE ● If electrical port 1 on the LMPT
ify is used, set the Port No.
parameter to 0.
5 Mod LOOPBACK
ify If the board is replaced with a
UMPTe:
6 Mod DOT1XAUTH ● If optical port 0 on the LMPT is
ify used, set the Port No.
parameter to 1 or 3.
7 Mod IPPATH
ify ● If electrical port 1 on the LMPT
is used, set the Port No.
8 Mod CFMLOCALMEP parameter to 0 or 2.
ify If the board is replaced with a
UMPTg:
9 Mod LLDP
ify

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 340

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

10 Mod IPRSCGRP Data cannot be reconfigured

ify directly and you need to perform
the operations described in Note.
11 Mod BACKTUNNEL This is because the LMPT supports
ify only the BBU3900, but the UMPTg
does not support the BBU3900.
12 Mod PORTSECURITY
ify

13 Mod PORTLR
ify

14 Mod LSWPORT
ify

15 Mod ETH3AH
ify

16 Mod ETHTRUNK
ify

17 Mod ETHTRUNKLNK
ify

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTe/UMPTg/
a UMPTga.
UM
PTa/ 2 Mod ETHPORT ● Modification is not required if
UM ify the transmission port is not
PTb changed after the board
3 Mod ETHCIPORT replacement.
with ify
a ● The corresponding port
UM 4 Mod INTERFACE number in transmission-related
PTe/ ify MOs needs to be set to 2 if
UM port 2 is used after the board
PTg/ 5 Mod LOOPBACK replacement.
UM ify ● The corresponding port
PTg number in transmission-related
6 Mod DOT1XAUTH
a. MOs needs to be changed to 3
ify
if port 3 is used after the board
7 Mod IPPATH replacement.
ify

8 Mod CFMLOCALMEP
ify

9 Mod LLDP
ify

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 341

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

10 Mod IPRSCGRP
ify

11 Mod BACKTUNNEL
ify

12 Mod PORTSECURITY
ify

13 Mod PORTLR
ify

14 Mod LSWPORT
ify

15 Mod ETH3AH
ify

16 Mod ETHTRUNK
ify

17 Mod ETHTRUNKLNK
ify

Repl 1 Mod MPT ● Set the Board Type parameter

ace ify to LMPT.
a ● Set the Board Specification
UM parameter to null character
PTa/ string.
UM
PTb
with
an
LMP
T.

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTg/UMPTga.
a
UM
PTe
with
a
UM
PTg/
UM
PTg
a.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 342

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTg.
a
UM
PTg
a
with
a
UM
PTg.

Note: You are advised to use the MAE-Deployment, which supports automatic
update of the corresponding port number in the associated MOs when a port
number of the main control board is changed. For details, see iMaster MAE
Product Documentation > Operation and Maintenance > MAE-Deployment
Operation and Maintenance > MAE-Deployment Guidelines > Changing
Base Station MPT Boards and Ports.

NOTE

● To replace the LMPT with a UMPTg, perform the following steps:

1. Replace the LMPT with a UMPTe.
2. Replace the UMPTe with a UMPTg and replace the BBU with a BBU5900 or
BBU3910.
● Set the Board Type parameter in the MPT MO to UMPTg.
● Change the Subrack Type parameter in the SUBRACK MO to BBU3910 or
BBU5900.
● The ESN changes after the BBU is replaced. You need to apply for a new license.

Data Preparation Mode

Use the "Export/Import MPT and Port No. Adjustment Data" mode and batch
reconfiguration mode on the MAE-Deployment. The "Export/Import MPT and Port
No. Adjustment Data" mode is recommended.

● The procedure for the "Export/Import MPT and Port No. Adjustment Data"
mode is as follows:
a. On the MAE-Deployment menu bar, choose LTE Application > Network
Adjustment > Export MPT and Port No. Adjustment Data to start the
data export.
b. Select a base station version and base stations to be reconfigured, and
then export the related data.
c. Enter the new MPT board type and new port number in the exported file
based on the plan.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 343

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

d. On the MAE-Deployment menu bar, choose LTE Application > Network

Adjustment > Import MPT and Port No. Adjustment Data to start the
data import.
e. Import the modified file.
● Use the batch reconfiguration mode of the MAE-Deployment (with the name
of the scenario-specific template being "Replacing the Main Control Board
When No SeGW Is Deployed"). For details, see the interactive operation guide
1.11.2 Using the Batch Reconfiguration Mode of the MAE-Deployment to
Prepare Data.
NOTE

● Before using the MAE-Deployment to prepare data, ensure that data in the planned
data area is consistent with that in the current data area. If the data is inconsistent, you
can choose Area Management > Planned Area > Synchronize NEs from the menu bar
to synchronize data from the current data area to the planned data area. Then, perform
the following operations.
● You are advised to use the MAE-Deployment, which supports automatic update of the
corresponding port number in the associated MOs when a port number of the main
control board is changed. For details, see iMaster MAE Product Documentation >
Operation and Maintenance > MAE-Deployment Operation and Maintenance >
MAE-Deployment Guidelines > Changing Base Station MPT Boards and Ports.
● When using the MAE-Deployment for data reconfiguration for a multimode base
station, choose SRAN Application on the menu bar.

1.7.1.3 Engineering Implementation

This section describes the engineering implementation for replacing a main
control board, including prerequisites, context, and procedure.

Prerequisites
Hardware, software, license file, and configuration data for replacing a main
control board are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.
Replacing a main control board requires cooperation of remote and local
operations. Figure 1-54 shows the procedure for replacing a main control board.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 344

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-54 Procedure for replacing a main control board

Procedure
Step 1 (Remote operation) Set the eNodeB maintenance mode to the expand status.

To prevent unnecessary alarms from being generated during reconfiguration, set

the eNodeB maintenance mode to expansion mode.

For details, see Setting the eNodeB Maintenance Mode to Expand Status.

Step 2 Back up the license file and configuration data file of the current main control
board.
● (Remote operation) Use the MAE-Access to back up the license file and
configuration data file. The files can be used for restoring the base station to
the pre-reconfiguration status if the reconfiguration fails.
a. Back up the license file in use to the MAE-Access server.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 345

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Run the ULD LICENSE command.

For example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
b. Run the following commands on the MAE-Access to back up and export
the configuration file. The configuration file can be used to restore the
base station to the pre-reconfiguration status if the reconfiguration fails.
i. To back up the configuration file, run the BKP CFGFILE command.
ii. To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
● (Local operation) Use the LMT to back up the license file and configuration
data file. In scenarios where configuration data is not modified, the files are
used for data activation on the LMT.
a. Start the FTP server.
b. Back up the license in use to the LMT PC.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="192.169.2.16", USR="admin",
PWD="*****", DIR="ftproot/", FN="D:\FTP",
FN="lic_21021127229TAA016583_1396364568622_1.xml";
c. Back up the configuration data file and export the file to the LMT PC. The
save path is the FTP server directory set in Step 2.a (local operation).
i. Run the BKP CFGFILE command to back up the configuration data
file.
ii. Run the ULD CFGFILE command to export the configuration data
file.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
Step 3 (Remote operation) Synchronize data to the planned data area.
● If configuration data does not need to be modified, synchronize the data to
the planned data area first. On the menu bar of the MAE-Deployment, choose
Area Management > Planned Area > Synchronize Planned Area NEs to
synchronize the data in the current data area to the planned data area.
● If the MAE-Deployment is used to reconfigure data, data synchronization is
not required. Otherwise, the reconfigured data will be replaced by the original
data after synchronization.
Step 4 (Local operation) Power off the base station and remove the main control board
to be replaced.
Step 5 (Local operation) Install the new main control board and power on the base
station.
Step 6 (Remote operation. Perform this step if the configuration data is to be activated
using the MAE-Access.) Remove the original base station from the main topology.
● On the menu bar of the MAE-Access, choose Topology > Main Topology.
● Right-click the base station to be removed and choose Delete from the
shortcut menu.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 346

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● In the displayed Confirm dialog box, click Yes.

● In the displayed Deletion Result dialog box, verify that Result is Succeeded,
and then click Close.

Step 7 (Remote operation. Perform this step if the configuration data is to be activated
using the MAE-Access.) Export the base station deployment list and configuration
data file.

For details, see step 6 in References > Exporting Deployment Lists and
Configuration Files of Base Stations in 3900 & 5900 Series Base Station
Commissioning Guide. Click Switch to the Auto Deployment window. The
system automatically switches to the auto-deployment window, creates a
commissioning task, and adds the base station to the main topology.

NOTE

Deployment lists are required if configuration data is to be activated using the MAE-Access.
The deployment lists must be exported by using the MAE-Deployment.

Step 8 (Remote operation) Check whether the transport network supports automatic
establishment of the OM channel.

To learn the requirements for the transport network to support automatic

establishment of the OM channel, see Commissioning a Newly Deployed Base
Station > MAE-based Commissioning > Preparation > Checking a Transport
Network in 3900 & 5900 Series Base Station Commissioning Guide.

Step 9 Activate the configuration data.

When activating the configuration data, you need to activate the software for the
old main control board if the software versions of the old and new main control
boards are different. If the license needs to be updated, you must use the new
commercial license file.

● (Remote operation) Activate the configuration data through the MAE-Access

and MAE-Deployment.
a. Upload the original base station's software package to the MAE server.
For details, see Commissioning a Newly Deployed Base Station > MAE-
based Commissioning > Preparation > Uploading the Software
Package in 3900 & 5900 Series Base Station Commissioning.
b. Upload the license file to the MAE server. For details, see Commissioning
a Newly Deployed Base Station > MAE-based Commissioning >
Preparation > Uploading a Commissioning License (When LTE/NR
Services Are to Be Enabled) in 3900 & 5900 Series Base Station
Commissioning Guide.
c. Bind the ESN.
A commissioning task has been created in Step 7. Select this
commissioning task of replacing the main control board from the
commissioning task list. Double-click the cell recording the ESN and
change the value to the current ESN of the base station.
d. Start the commissioning task. For details, see Commissioning a Newly
Deployed Base Station > MAE-based Commissioning > Preparation >
Starting an NE Commissioning Task in 3900 & 5900 Series Base Station
Commissioning Guide.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 347

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

e. Check whether the eNodeB is working properly. For details, see

Commissioning a Newly Deployed Base Station > MAE-based
Commissioning > Remote Operations > Acquiring an NE
Commissioning Verification Report in 3900 & 5900 Series Base Station
Commissioning Guide.
f. Verify that the commissioning task is complete. For details, see
Commissioning a Newly Deployed Base Station > MAE-based
Commissioning > Remote Operations > Confirming that Auto
Deployment Tasks Are Completed in 3900 & 5900 Series Base Station
Commissioning Guide.
● (Local operation) Activate the configuration data on the LMT.
a. Log in to the LMT and disable the DHCP function. For details, see
Commissioning a Newly Deployed Base Station > LMT+MAE-based
Commissioning > Local Operations > Logging In to the LMT and
Disabling the DHCP Function in 3900 & 5900 Series Base Station
Commissioning Guide.
b. Configure the FTP server. If the FTP server to be configured is provided by
a third party or does not have a Huawei-issued device certificate, set the
FTPCLT.ENCRYMODE parameter to Plaintext.
c. Download and activate the software and configuration data and install
the license file. For details, see Commissioning a Newly Deployed Base
Station > LMT+MAE-based Commissioning > Local Operations >
Loading the Software, Data Configuration File, and Commissioning
License by Using the LMT in 3900 & 5900 Series Base Station
Commissioning Guide.
NOTE

To locally log in to the LMT after configuration data is activated, use the local maintenance
IP address of the old main control board but the login account and password of the new
main control board.

Step 10 (Remote operation. Perform this step if the configuration data is to be activated
using the MAE-Access.) Delete the commissioning task on the MAE-Access.
1. On the MAE-Access, choose SON > Auto Deployment to open the Auto
Deployment window.
2. Right-click the commissioning task to be deleted and choose Delete from the
shortcut menu.
3. In the displayed confirmation dialog box, click Yes.
Step 11 (Remote operation) Set the eNodeB maintenance mode to the normal status on
the MAE-Access.
When the reconfiguration is complete, set the eNodeB maintenance mode to
Normal.
For details, see Setting the Maintenance Mode of the eNodeB to NORMAL.

----End

1.7.1.4 Engineering Verification

This section describes how to verify the replacement of a main control board.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 348

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 2 Run the DSP OMCH command to check whether the status of the OM channel
between the eNodeB and the new MAE-Access is normal.

If OM Channel Status is not Normal, perform the following steps:

1. From the main menu on the MAE-Access, choose Topology > Main Topology
to check whether the eNodeB is in connection. If it is, contact Huawei
technical support or dial the Huawei technical support hotline. If it is not, go
to Step 2.2.
2. Check the modified configuration file to check whether the ports in non-
secure networking are the same as planned.
– If they are different, modify the configuration data file again and import
it into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
– If they are the same, an error has occurred when the data is imported
into the system or delivered to the base station. In this situation, contact
Huawei technical support or dial the Huawei technical support hotline.

Step 3 Run LST commands to check whether the values of related parameters in the MOs
are changed as planned. For details about the MOs and parameters, see
Engineering Preparation > Data Preparation.

If Port No. values are not changed as planned, check whether the ports in the
modified configuration data file are the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

Step 4 Verify that ALM-25880 Ethernet Link Fault is not reported.

If ALM-25880 Ethernet Link Fault is reported, clear the alarm according to

instructions in 3900 & 5900 Series Base Station Alarm Reference.

----End

1.7.1.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 349

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Power off the base station and remove the new main control board.
Step 2 Insert the original main control board and power on the base station.
All information such as the software and data configuration file before the
reconfigurations are stored on the original main control board. The base station is
automatically rolled back to its original status after the original main control
board is inserted.
Step 3 Check whether the engineering rollback is successful by referring to 1.7.1.4
Engineering Verification.

----End

1.7.2 Replacing the Main Control Board When an SeGW Is

Deployed
This section describes how to replace the main control board in secure networking
scenarios (with PSK or PKI enabled).

NOTE

Unless otherwise specified, UMPT herein represents all UMPT boards.

5900 series base stations do not support any scenario involving LMPT boards. If such a scenario
exists, adjust it based on site requirements.

1.7.2.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for replacing a main control board.

Application Scenario
A main control board needs to be replaced if it cannot meet service requirements.
The transmission interface capabilities and attributes vary with the main control
board types. Therefore, during board replacement, reconfigure data based on
different schemes.

Reconfiguration Impact
After replacing the main control board, you must power off and power on the
base station to make the configuration take effect. During the operation, the base
station cannot provide services.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 350

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme
NOTE

● After the main control board is replaced, the Media Access Control (MAC) address of the
board is changed. If the MAC address is used by the transport network, inform the transport
network maintenance personnel of the change and ask them to modify the configurations.
● After the main control board is replaced, the default password of the default LMT account
used for locally logging in to base stations varies between versions. For details, see section
"Logging In to and Logging Out of the LMT" in 3900 & 5900 Series Base Station LMT User
Guide.

Table 1-115 UMPT scheme options

Replaceme Transmission Transmission Transmission Board Type
nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

UMPTa/ Electrical port Electrical ports ● Adjustment Set the Board

UMPTb- 0 0 and 2 is not Specification
>UMPTe/ required if parameter to
UMPTg/ port 0 is UMPTe/
UMPTga still used UMPTg/
after the UMPTga.
board
replacemen
t.
● The
correspondi
ng port
number in
transmissio
n-related
MOs needs
to be
changed to
2 if port 2
is used
after the
board
replacemen
t.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 351

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

Optical port 1 Optical ports 1 ● Adjustment

and 3 is not
required if
port 1 is
still used
after the
board
replacemen
t.
● The
correspondi
ng port
number in
transmissio
n-related
MOs needs
to be
changed to
3 if port 3
is used
after the
board
replacemen
t.

LMPT- Optical port 0 Optical port 1 Change the ● Set the

>UMPTa/ corresponding Board Type
UMPTba port number parameter
in to UMPT.
transmission- ● Set the
related MOs Board
to 1. Specificati
Electrical port Electrical port Change the on
1 0 corresponding parameter
port number to
in UMPTa/b.
transmission-
related MOs
to 0.

Electrical port Electrical port Adjustment is

0 0 not required.

Optical port 1 Optical port 1 Adjustment is

not required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 352

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

LMPT- Optical port 0 Optical ports 1 Change the ● Set the

>UMPTe/ and 3 corresponding Board Type
UMPTg/ port number parameter
UMPTgaa in to UMPT.
transmission- ● Set the
related MOs Board
to 1 or 3. Specificati
Electrical port Electrical ports Change the on
1 0 and 2 corresponding parameter
port number to UMPTe/
in UMPTg/
transmission- UMPTga. d
related MOs
to 0 or 2.

Electrical port Electrical ports ● Adjustment

0 0 and 2 is not
required if
port 0 is
still used
after the
board
replacemen
t.
● The
correspondi
ng port
number in
transmissio
n-related
MOs needs
to be
changed to
2 if port 2
is used
after the
board
replacemen
t.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 353

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

Optical port 1 Optical ports 1 ● Adjustment

and 3 is not
required if
port 1 is
still used
after the
board
replacemen
t.
● The
correspondi
ng port
number in
transmissio
n-related
MOs needs
to be
changed to
3 if port 3
is used
after the
board
replacemen
t.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 354

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

UMPTa/ Electrical port Electrical ports ● Adjustment ● Set the

UMPTb- 0 0 and 1 is not Board Type
>LMPTc required if parameter
port 0 is to LMPT.
still used ● Set the
after the Board
board Specificati
replacemen on
t. parameter
● The to null
correspondi character
ng port string.
number in
transmissio
n-related
MOs needs
to be
changed to
1 if port 1
is used
after the
board
replacemen
t.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 355

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

Optical port 1 Optical ports 0 ● Adjustment

and 1 is not
required if
port 0 is
still used
after the
board
replacemen
t.
● The
correspondi
ng port
number in
transmissio
n-related
MOs needs
to be
changed to
1 if port 1
is used
after the
board
replacemen
t.

UMPTe- Electrical ports Electrical ports Adjustment is Set the Board

>UMPTg/ 0 and 2 0 and 2 not required. Specification
UMPTga parameter to
Optical ports 1 Optical ports 1 Adjustment is UMPTg/
and 3 and 3 not required. UMPTga.

UMPTga- Electrical ports Electrical ports Adjustment is Set the Board

>UMPTg 0 and 2 0 and 2 not required. Specification
parameter to
Optical ports 1 Optical ports 1 Adjustment is UMPTg.
and 3 and 3 not required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 356

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Replaceme Transmission Transmission Transmission Board Type

nt Scheme Port Before Port After Port Reconfigurati
Replacement Replacement Adjustmentb on

a: If the LMPT is configured with two optical ports or two electrical ports, and
the next-hop IP addresses of the two ports are not in the same VLAN, data
needs to be reconfigured for the network after the LMPT is replaced with a
UMPT. Then, perform the reconfiguration according to the reconfiguration
scheme in the preceding table.
b: Transmission-port-related MOs include:
● IPv4: old model
The Transmission Configuration Mode parameter in the GTRANSPARA MO
is set to OLD.
ETHPORT, DOT1X, IPPATH, CFMMEP, RSCGRP, IP2RSCGRP, RSCGRPALG,
PORTSECURITY, LR, EP2RSCGRP, DEVIP, ETHOAM3AH, ETHTRK, and
ETHTRKLNK
● IPv4: new model
The Transmission Configuration Mode parameter in the GTRANSPARA MO
is set to NEW.
ETHPORT, DOT1XAUTH, IPPATH, CFMLOCALMEP, IPRSCGRP, PORTSECURITY,
PORTLR, ETH3AH, ETHTRUNK, ETHTRUNKLNK, INTERFACE, LOOPBACK,
ETHCIPORT, LLDP, LSWPORT, and BACKTUNNEL
● IPv6:
ETHPORT, DOT1XAUTH, CFMLOCALMEP, IPRSCGRP, PORTSECURITY, PORTLR,
INTERFACE, LOOPBACK, and LLDP
c: The maximum transmission bandwidth supported by the UMPT is greater
than that supported by the LMPT. If the sum of transmission bandwidths of
logical resource groups configured on the old UMPT is greater than the
maximum transmission bandwidth supported by the new LMPT and the
bandwidth configuration is not changed, logical resource groups cannot be
generated when the UMPT is replaced with the LMPT. As a result, IP paths
become unusable and services are affected. In this scenario, bandwidth
configurations must be replanned. The LMPT supports only IPv4 transmission.
d: The LMPT supports only the BBU3900, and the UMPTg does not support the
BBU3900. Therefore, the BBU also needs to be replaced when replacing an
LMPT with a UMPTg. Data cannot be directly reconfigured for the replacement
of an LMPT with a UMPTg. Perform the following steps to reconfigure data:
1. Replace the LMPT with a UMPTe.
2. Replace the UMPTe with a UMPTg and replace the BBU with a BBU5900 or
BBU3910.
● Set the Board Type parameter in the MPT MO to UMPTg.
● Change the Subrack Type parameter in the SUBRACK MO to BBU3910 or
BBU5900.

Topology Change
The topology changes when the LMPT using optical port 0 or electrical port 1 is
replaced with a UMPT. The topology does not change when the LMPT using

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 357

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

optical port 1 or electrical port 0 is replaced with a UMPT or when the UMPT is
replaced with an LMPT.
Use the scenario where an LMPT using optical port 0 is replaced with a UMPT
using optical port 1 as an example. Figure 1-55 shows the topologies before and
after the reconfiguration.

Figure 1-55 Topology Change

Use the scenario where an LMPT using electrical port 1 is replaced with a UMPTg
using electrical port 2 as an example. Figure 1-56 shows the topologies before
and after the reconfiguration.

Figure 1-56 Topologies before and after the reconfiguration

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 358

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.7.2.2 Engineering Preparation

This section describes the engineering preparation for replacing a main control
board when an SeGW is deployed, including information collection and
preparation of hardware, software, license files, security certificates, and data. It
also describes the data preparation mode.

Information Collection
Table 1-116 describes the information to be collected for data preparation.

Table 1-116 Information to be collected

Information Description

Configuration data The latest configuration data that is manually exported

file of the original before the reconfiguration. For details, see Exporting
main control board Deployment Lists and Configuration Files of Base
Stations in 3900 & 5900 Series Base Station Initial
Configuration Guide.

Hardware Preparation
Prepare the hardware listed in Table 1-117.

Table 1-117 Hardware to be prepared

If... Then...

A UMPTa/UMPTb Prepare an LMPT.

needs to be replaced
with an LMPT

An LMPT needs to be Prepare a UMPT and a local maintenance adapter.

replaced with a
UMPTa

A UMPTa/UMPTb Prepare a UMPTe/UMPTg/UMPTga

needs to be replaced
with a UMPTe/
UMPTg/UMPTga

A UMPTe needs to be Prepare a UMPTg/UMPTga.

replaced with a
UMPTg/UMPTga

A UMPTga needs to Prepare a UMPTg.

be replaced with a
UMPTg

a: If an LMPT needs to be replaced with a UMPTg, you need to replace the

BBU3900 with a BBU3910 or BBU5900 first.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 359

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation
If the version of the new main control board is different from that of the main
control board to be replaced, collect information about the software version of the
main control board to be replaced.

License File Preparation

Keep a new license ready if no license file is loaded to the new main control
board, the control items in the license file cannot meet service requirements, or
the license has expired.

Security Certificate Preparation

Ensure that the operator CA-issued certificate is ready.

Data Preparation
The following table lists the data to be prepared.

Old Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 360

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-118 Data preparation for replacing a main control board

Cha SN Ope MO Configuration Reference
nge rati
Mod on
el

Repl 1 Mod MPT ● Set the Board Type parameter

ace ify to UMPT.
an ● Change the value of the Board
LMP Specification parameter.
T
with – If the board is replaced with
a a UMPTa/UMPTb, set the
UM Board Specification
PT. parameter to UMPTa/b.
– If the board is replaced with
a UMPTe/UMPTga, set the
Board Specification
parameter to UMPTe/
UMPTga.
– If the board is replaced with
a UMPTg, data cannot be
reconfigured directly and
you need to perform the
operations described in
Note. This is because the
LMPT supports only the
BBU3900, but the UMPTg
does not support the
BBU3900.

2 Mod ETHPORT If the board is replaced with a

ify UMPTa/UMPTb:

3 Mod DOT1X ● If optical port 0 on the LMPT is

ify used, set the Port No.
parameter to 1.
4 Mod IPPATH ● If electrical port 1 on the LMPT
ify is used, set the Port No.
5 Mod IPSECBIND parameter to 0.
ify If the board is replaced with a
6 Mod CFMMEP UMPTe:
ify ● If optical port 0 on the LMPT is
used, set the Port No.
7 Mod RSCGRP parameter to 1 or 3.
ify
● If electrical port 1 on the LMPT
8 Mod IP2RSCGRP is used, set the Port No.
ify parameter to 0 or 2.

9 Mod RSCGRPALG
ify

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 361

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

10 Mod PORTSECURITY
ify

11 Mod LR
ify

12 Mod EP2RSCGRP
ify

13 Mod DEVIP
ify

14 Mod ETHOAM3AH
ify

15 Mod ETHTRK
ify

16 Mod ETHTRKLNK
ify

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTe/UMPTg/
a UMPTga.
UM
PTa/ 2 Mod ETHPORT ● Modification is not required if
UM ify the transmission port is not
PTb changed after the board
3 Mod DOT1X replacement.
with ify
a ● The corresponding port
UM 4 Mod IPPATH number in transmission-related
PTe/ ify MOs needs to be changed to 2
UM if port 2 is used after the board
PTg/ 5 Mod IPSECBIND replacement.
UM ify ● The corresponding port
PTga number in transmission-related
6 Mod CFMMEP
. MOs needs to be changed to 3
ify
if port 3 is used after the board
7 Mod RSCGRP replacement.
ify

8 Mod IP2RSCGRP
ify

9 Mod RSCGRPALG
ify

10 Mod PORTSECURITY
ify

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 362

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

11 Mod LR
ify

12 Mod EP2RSCGRP
ify

13 Mod DEVIP
ify

14 Mod ETHOAM3AH
ify

15 Mod ETHTRK
ify

16 Mod ETHTRKLNK
ify

Repl 1 Mod MPT ● Set the Board Type parameter

ace ify to LMPT.
a ● Set the Board Specification
UM parameter to null character
PTa/ string.
UM
PTb
with
an
LMP
T.

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTg/UMPTga.
a
UM
PTe
with
a
UM
PTg/
UM
PTga
.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 363

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTg.
a
UM
PTga
with
a
UM
PTg.

Note: You are advised to use the MAE-Deployment, which supports automatic
update of the corresponding port number in the associated MOs when a port
number of the main control board is changed. For details, see iMaster MAE
Product Documentation > Operation and Maintenance > MAE-Deployment
Operation and Maintenance > MAE-Deployment Guidelines > Changing
Base Station MPT Boards and Ports.

New Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 364

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-119 Data preparation for replacing a main control board

Cha SN Ope MO Configuration Reference
nge rati
Mod on
el

Repl 1 Mod MPT ● Set the Board Type parameter

ace ify to UMPT.
an ● Change the value of the Board
LMP Specification parameter.
T
with – If the board is replaced with
a a UMPTa/UMPTb, set the
UM Board Specification
PT. parameter to UMPTa/b.
– If the board is replaced with
a UMPTe/UMPTga, set the
Board Specification
parameter to UMPTe/
UMPTga.
– If the board is replaced with
a UMPTg, data cannot be
reconfigured directly and
you need to perform the
operations described in
Note. This is because the
LMPT supports only the
BBU3900, but the UMPTg
does not support the
BBU3900.

2 Mod ETHPORT If the board is replaced with a

ify UMPTa/UMPTb:
● If optical port 0 on the LMPT is
3 Mod ETHCIPORT
used, set the Port No.
ify
parameter to 1.
4 Mod INTERFACE ● If electrical port 1 on the LMPT
ify is used, set the Port No.
parameter to 0.
5 Mod LOOPBACK
ify If the board is replaced with a
UMPTe:
6 Mod DOT1XAUTH ● If optical port 0 on the LMPT is
ify used, set the Port No.
parameter to 1 or 3.
7 Mod IPPATH
ify ● If electrical port 1 on the LMPT
is used, set the Port No.
8 Mod CFMLOCALMEP parameter to 0 or 2.
ify If the board is replaced with a
UMPTg:
9 Mod LLDP
ify

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 365

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

10 Mod IPRSCGRP Data cannot be reconfigured

ify directly and you need to perform
the operations described in Note.
11 Mod BACKTUNNEL This is because the LMPT supports
ify only the BBU3900, but the UMPTg
does not support the BBU3900.
12 Mod PORTSECURITY
ify

13 Mod PORTLR
ify

14 Mod LSWPORT
ify

15 Mod ETH3AH
ify

16 Mod ETHTRUNK
ify

17 Mod ETHTRUNKLNK
ify

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTe/UMPTg/
a UMPTga.
UM
PTa/ 2 Mod ETHPORT ● Modification is not required if
UM ify the transmission port is not
PTb changed after the board
3 Mod ETHCIPORT replacement.
with ify
a ● The corresponding port
UM 4 Mod INTERFACE number in transmission-related
PTe/ ify MOs needs to be set to 2 if
UM port 2 is used after the board
PTg/ 5 Mod LOOPBACK replacement.
UM ify ● The corresponding port
PTg number in transmission-related
6 Mod DOT1XAUTH
a. MOs needs to be changed to 3
ify
if port 3 is used after the board
7 Mod IPPATH replacement.
ify

8 Mod CFMLOCALMEP
ify

9 Mod LLDP
ify

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 366

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

10 Mod IPRSCGRP
ify

11 Mod BACKTUNNEL
ify

12 Mod PORTSECURITY
ify

13 Mod PORTLR
ify

14 Mod LSWPORT
ify

15 Mod ETH3AH
ify

16 Mod ETHTRUNK
ify

17 Mod ETHTRUNKLNK
ify

Repl 1 Mod MPT ● Set the Board Type parameter

ace ify to LMPT.
a ● Set the Board Specification
UM parameter to null character
PTa/ string.
UM
PTb
with
an
LMP
T.

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTg/UMPTga.
a
UM
PTe
with
a
UM
PTg/
UM
PTg
a.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 367

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Cha SN Ope MO Configuration Reference

nge rati
Mod on
el

Repl 1 Mod MPT Set the Board Specification

ace ify parameter to UMPTg.
a
UM
PTg
a
with
a
UM
PTg.

Note: You are advised to use the MAE-Deployment, which supports automatic
update of the corresponding port number in the associated MOs when a port
number of the main control board is changed. For details, see iMaster MAE
Product Documentation > Operation and Maintenance > MAE-Deployment
Operation and Maintenance > MAE-Deployment Guidelines > Changing
Base Station MPT Boards and Ports.

NOTE

● To replace the LMPT with a UMPTg, perform the following steps:

1. Replace the LMPT with a UMPTe.
2. Replace the UMPTe with a UMPTg and replace the BBU with a BBU5900 or
BBU3910.
● Set the Board Type parameter in the MPT MO to UMPTg.
● Change the Subrack Type parameter in the SUBRACK MO to BBU3910 or
BBU5900.
● The ESN changes after the BBU is replaced. You need to apply for a new license.

Data Preparation Mode

Use the "Export/Import MPT and Port No. Adjustment Data" mode and batch
reconfiguration mode on the MAE-Deployment. The "Export/Import MPT and Port
No. Adjustment Data" mode is recommended.

● The procedure for the "Export/Import MPT and Port No. Adjustment Data"
mode is as follows:
a. On the MAE-Deployment menu bar, choose LTE Application > Network
Adjustment > Export MPT and Port No. Adjustment Data to start the
data export.
b. Select a base station version and base stations to be reconfigured, and
then export the related data.
c. Enter the new MPT board type and new port number in the exported file
based on the plan.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 368

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

d. On the MAE-Deployment menu bar, choose LTE Application > Network

Adjustment > Import MPT and Port No. Adjustment Data to start the
data import.
e. Import the modified file.
● Use the batch reconfiguration mode of the MAE-Deployment (with the name
of the scenario-specific template being "Replacing the Main Control Board
When an SeGW Is Deployed"). For details, see the interactive operation guide
1.11.2 Using the Batch Reconfiguration Mode of the MAE-Deployment to
Prepare Data.
NOTE

● Before using the MAE-Deployment to prepare data, ensure that data in the planned
data area is consistent with that in the current data area. If the data is inconsistent, you
can choose Area Management > Planned Area > Synchronize NEs from the menu bar
to synchronize data from the current data area to the planned data area. Then, perform
the following operations.
● You are advised to use the MAE-Deployment, which supports automatic update of the
corresponding port number in the associated MOs when a port number of the main
control board is changed. For details, see iMaster MAE Product Documentation >
Operation and Maintenance > MAE-Deployment Operation and Maintenance >
MAE-Deployment Guidelines > Changing Base Station MPT Boards and Ports.
● When using the MAE-Deployment for data reconfiguration for a multimode base
station, choose SRAN Application on the menu bar.

1.7.2.3 Engineering Implementation

This section describes the engineering implementation for replacing a main
control board, including prerequisites, context, and procedure.

Prerequisites
Hardware, software, license file, and configuration data for replacing a main
control board are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.
Replacing a main control board requires cooperation of remote and local
operations. Figure 1-57 shows the procedure for replacing a main control board.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 369

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-57 Procedure for replacing a main control board

Procedure
Step 1 (Remote operation) Set the eNodeB maintenance mode to the expand status.

To prevent unnecessary alarms from being generated during reconfiguration, set

the eNodeB maintenance mode to expansion mode.

For details, see Setting the eNodeB Maintenance Mode to Expand Status.

Step 2 Back up the license file and configuration data file of the current main control
board.
● (Remote operation) Use the MAE-Access to back up the license file and
configuration data file. The files can be used for restoring the base station to
the pre-reconfiguration status if the reconfiguration fails.
a. Back up the license file in use to the MAE-Access server.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 370

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Run the ULD LICENSE command.

For example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
b. Run the following commands on the MAE-Access to back up and export
the configuration file. The configuration file can be used to restore the
base station to the pre-reconfiguration status if the reconfiguration fails.
i. To back up the configuration file, run the BKP CFGFILE command.
ii. To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
● (Local operation) Use the LMT to back up the license file and configuration
data file. In scenarios where configuration data is not modified, the files are
used for data activation on the LMT.
a. Start the FTP server.
b. Back up the license in use to the LMT PC.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="192.169.2.16", USR="admin",
PWD="*****", DIR="ftproot/", FN="D:\FTP",
FN="lic_21021127229TAA016583_1396364568622_1.xml";
c. Back up the configuration data file and export the file to the LMT PC. The
save path is the FTP server directory set in Step 2.a (local operation).
i. Run the BKP CFGFILE command to back up the configuration data
file.
ii. Run the ULD CFGFILE command to export the configuration data
file.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
Step 3 (Remote operation) Synchronize data to the planned data area.
● If configuration data does not need to be modified, synchronize the data to
the planned data area first. On the menu bar of the MAE-Deployment, choose
Area Management > Planned Area > Synchronize Planned Area NEs to
synchronize the data in the current data area to the planned data area.
● If the MAE-Deployment is used to reconfigure data, data synchronization is
not required. Otherwise, the reconfigured data will be replaced by the original
data after synchronization.
Step 4 (Local operation) Power off the base station and remove the main control board
to be replaced.
Step 5 (Local operation) Install the new main control board and power on the base
station.
Step 6 (Remote operation. Perform this step if the configuration data is to be activated
using the MAE-Access.) Remove the original base station from the main topology.
● On the menu bar of the MAE-Access, choose Topology > Main Topology.
● Right-click the base station to be removed and choose Delete from the
shortcut menu.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 371

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● In the displayed Confirm dialog box, click Yes.

● In the displayed Deletion Result dialog box, verify that Result is Succeeded,
and then click Close.

Step 7 (Remote operation. Perform this step if the configuration data is to be activated
using the MAE-Access.) Export the base station deployment list and configuration
data file.

For details, see step 6 in References > Exporting Deployment Lists and
Configuration Files of Base Stations in 3900 & 5900 Series Base Station
Commissioning Guide. Click Switch to the Auto Deployment window. The
system automatically switches to the auto-deployment window, creates a
commissioning task, and adds the base station to the main topology.

NOTE

Deployment lists are required if configuration data is to be activated using the MAE-Access.
The deployment lists must be exported by using the MAE-Deployment.

Step 8 (Remote operation) Check whether the transport network supports automatic
establishment of the OM channel.

To learn the requirements for the transport network to support automatic

establishment of the OM channel, see Commissioning a Newly Deployed Base
Station > MAE-based Commissioning > Preparation > Checking a Transport
Network in 3900 & 5900 Series Base Station Commissioning Guide.

Step 9 Activate the configuration data.

When activating the configuration data, you need to activate the software for the
old main control board if the software versions of the old and new main control
boards are different. If the license needs to be updated, you must use the new
commercial license file.

● (Remote operation) Activate the configuration data through the MAE-Access

and MAE-Deployment.
a. Upload the original base station's software package to the MAE server.
For details, see Commissioning a Newly Deployed Base Station > MAE-
based Commissioning > Preparation > Uploading the Software
Package in 3900 & 5900 Series Base Station Commissioning.
b. Upload the license file to the MAE server. For details, see Commissioning
a Newly Deployed Base Station > MAE-based Commissioning >
Preparation > Uploading a Commissioning License (When LTE/NR
Services Are to Be Enabled) in 3900 & 5900 Series Base Station
Commissioning Guide.
c. Bind the ESN.
A commissioning task has been created in Step 7. Select this
commissioning task of replacing the main control board from the
commissioning task list. Double-click the cell recording the ESN and
change the value to the current ESN of the base station.
d. Start the commissioning task. For details, see Commissioning a Newly
Deployed Base Station > MAE-based Commissioning > Preparation >
Starting an NE Commissioning Task in 3900 & 5900 Series Base Station
Commissioning Guide.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 372

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

e. Check whether the eNodeB is working properly. For details, see

Commissioning a Newly Deployed Base Station > MAE-based
Commissioning > Remote Operations > Acquiring an NE
Commissioning Verification Report in 3900 & 5900 Series Base Station
Commissioning Guide.
f. Verify that the commissioning task is complete. For details, see
Commissioning a Newly Deployed Base Station > MAE-based
Commissioning > Remote Operations > Confirming that Auto
Deployment Tasks Are Completed in 3900 & 5900 Series Base Station
Commissioning Guide.
● (Local operation) Activate the configuration data on the LMT.
a. Log in to the LMT and disable the DHCP function. For details, see
Commissioning a Newly Deployed Base Station > LMT+MAE-based
Commissioning > Local Operations > Logging In to the LMT and
Disabling the DHCP Function in 3900 & 5900 Series Base Station
Commissioning Guide.
b. Configure the FTP server. If the FTP server to be configured is provided by
a third party or does not have a Huawei-issued device certificate, set the
FTPCLT.ENCRYMODE parameter to Plaintext.
c. Download and activate the software and configuration data and install
the license file. For details, see Commissioning a Newly Deployed Base
Station > LMT+MAE-based Commissioning > Local Operations >
Loading the Software, Data Configuration File, and Commissioning
License by Using the LMT in 3900 & 5900 Series Base Station
Commissioning Guide.
NOTE

To locally log in to the LMT after configuration data is activated, use the local maintenance
IP address of the old main control board but the login account and password of the new
main control board.

Step 10 (Remote operation. Perform this step if the configuration data is to be activated
using the MAE-Access.) Delete the commissioning task on the MAE-Access.
1. On the MAE-Access, choose SON > Auto Deployment to open the Auto
Deployment window.
2. Right-click the commissioning task to be deleted and choose Delete from the
shortcut menu.
3. In the displayed confirmation dialog box, click Yes.
Step 11 (Remote operation) Set the eNodeB maintenance mode to the normal status on
the MAE-Access.
When the reconfiguration is complete, set the eNodeB maintenance mode to
Normal.
For details, see Setting the Maintenance Mode of the eNodeB to NORMAL.
----End

1.7.2.4 Engineering Verification

This section describes how to verify the replacement of the main control board
when an SeGW is deployed on the network.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 373

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Verify that ALM-25880 Ethernet Link Fault is not reported.

If ALM-25880 Ethernet Link Fault is reported, clear the alarm according to

instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run LST commands to check whether the values of related parameters in the MOs
are changed as planned. For details about the MOs and parameters, see
Engineering Preparation > Data Preparation.

If Port No. values are not changed as planned, check whether the ports in the
modified configuration data file are the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

Step 3 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 4 Run the DSP IKESA command. Verify that the SA status in both phases is Ready|
StayAlive.

If the IKE SA status is not Ready|StayAlive, perform the following steps:

1. Check whether the port number in MOs related to secure networking is

correct in the modified configuration data file.
– If the port number is correct, go to Step 4.2.
– If the port number is incorrect, modify the configuration data file and
perform the operations in Engineering Implementation again to deliver
the data to the base station and then activate the data.
2. Check whether the PSK or PKI is used.
– If the PKI is used, go to Step 4.3.
– If the PSK is used, contact Huawei technical support or dial the Huawei
technical support hotline.
3. Run the DSP TRUSTCERT and DSP APPCERT commands to check the status
of the operator-issued device certificate and CA certificate.
– If the status is normal, contact Huawei technical support or dial the
Huawei technical support hotline.
– If the status is abnormal, apply for the certificates again by following
Engineering Implementation > Procedure.

Step 5 Run the DSP OMCH command to check whether the status of the OM channel
between the eNodeB and the new MAE-Access is normal.

If OM Channel Status is not Normal, perform the following steps:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 374

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1. From the main menu on the MAE-Access, choose Topology > Main Topology
to check whether the eNodeB is in connection. If it is, contact Huawei
technical support or dial the Huawei technical support hotline. If it is not, go
to Step 5.2.
2. Check the modified configuration file to check whether the ports in non-
secure networking are the same as planned.
– If they are different, modify the configuration data file again and import
it into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
– If they are the same, an error has occurred when the data is imported
into the system or delivered to the base station. In this situation, contact
Huawei technical support or dial the Huawei technical support hotline.

----End

1.7.2.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Power off the base station and remove the new main control board.
Step 2 Insert the original main control board and power on the base station.
All information such as the software and data configuration file before the
reconfigurations are stored on the original main control board. The base station is
automatically rolled back to its original status after the original main control
board is inserted.
Step 3 Verify that engineering rollback is successful according to instructions in 1.7.2.4
Engineering Verification.

----End

1.7.3 Replacing BBPs

This section describes how to replace a BBP in a 3900 or 5900 series base station.

NOTE

5900 series base stations do not support any scenario involving LBBP boards. If such a scenario
exists, adjust it based on site requirements.

1.7.3.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for replacing the BBP.

Application Scenario
● The BBP in use is faulty and must be replaced with one in another model.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 375

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● The BBP running on the live network does not meet service requirements.
Therefore, the BBP needs to be upgraded.
NOTE

For details about how to replace a BBP with a BBP of the same type, see BBU Hardware
Maintenance Guide.

Reconfiguration Impact
After replacing the BBP, you must power off and then power on the BBP to make
the configuration take effect. During the operation, all the cells established on the
BBP cannot provide services.

Reconfiguration Scheme
NOTE

● When the UBBP is used in multimode concurrence scenarios, you also need to configure the
UBBP for other modes. For details, see the corresponding reconfiguration guides:
● GSM: GBSS Reconfiguration Guide for BSC6900 or GBSS Reconfiguration Guide for
BSC6910
● UMTS: RAN Reconfiguration Guide for BSC6900 or RAN Reconfiguration Guide for
BSC6910
● If CPRI convergence is enabled on the BBP to be replaced, adhere to the following principles
when the BBP is replaced:
● In LBBPc+LBBPc convergence mode, the convergence is implemented only between two
LBBPc boards with one installed in slot 2 or 3.
● In LBBPc+LBBPd convergence mode, CPRI ports on multiple LBBPc boards can be
converged on one LBBPd. In addition, only the CPRI ports on the LBBPd in slot 2 or 3
can connect to RF modules.
● If CPRI compression is implemented on an LBBPd, the LBBPd cannot be replaced with an
LBBPc because the LBBPc does not support CPRI compression.

Reconfiguration schemes of replacing BBPs are as follows:

Table 1-120 Scheme options

If... Then...

An LBBPd is replaced Check the value of Indication of PRACH

with an LBBPc Configuration Index in the RACHCfg MO:
● If this parameter is set to CFG(Configure), set
PRACH Configuration Index to the target value,
ensuring that the values of PRACH Configuration
Index for all cells in the same eNodeB are unique.
● If this parameter is set to NOT_CFG(Not
configure), no change is required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 376

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

An LBBPc is replaced ● Change the values of Board Type to UBBP(UBBP)

with a UBBP and Base Band Work Standard to LTE_FDD(LTE
FDD) or LTE_TDD(LTE TDD) in the BBP MO.
● Modify Delta shift in the PUCCHCfg MO:
– If Delta shift is set to 2, change it to 1.
– If Delta shift is set to 1 or 3, no change is
required.

An LBBPd is replaced Change the values of Board Type to UBBP(UBBP) and

with a UBBP Base Band Work Standard to LTE_FDD(LTE FDD) or
LTE_TDD(LTE TDD) in the BBP MO.

A UBBP is replaced Change the values of Board Type to LBBP(LBBP) and

with an LBBPd Work Mode to FDD(Frequency Division Duplex) in
the BBP MO.

A UBBPem is replaced Change the value of Board Specification to UBBPf1 or

with a UBBPf1 or UBBPg4 in the BBP MO.
UBBPg4

The existing BBP is ● Check the value of Uplink hopping type in the
replaced with a CellUlschAlgo MO:
UBBPg The value must be HOPPING_OFF.
● Check the values of Uplink cyclic prefix length and
Downlink cyclic prefix length in the Cell MO.
The values must be NORMAL_CP.
● Check whether any CoProcRes MO is associated
with the BASEBANDEQM MO. If there is such a
CoProcRes MO, the value of the Work Mode
parameter in the MO must meet the following
requirements:The COORDINATING_PROCESSING
option must be selected, and the
BASEBAND_PROCESSING option must be deselected.

Topology Change
N/A

1.7.3.2 Engineering Preparation

This section describes the engineering preparation for replacing the BBP, including
information collection and preparation of hardware, software, license files, security
certificates, and data. It also describes the data preparation mode and provides
MML configuration script examples.

Information Collection
Table 1-121 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 377

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-121 Information to be collected

Information Description

The delta shift of Determine whether to modify the delta shift of the new
cells of the BBP to be BBP based on the information.
replaced

The PRACH Constraints on the setting of PRACH configuration

configuration index indexes are different for the LBBPd and the LBBPc.
of cells of the BBP to
be replaced

The number of the -

slot where the BBP to
be replaced is located

The maximum Check whether the new BBP supports the establishment
number of cells that of cells of such a quantity.
can be established on
the BBP to be
replaced

Hardware Preparation
Prepare a new BBP.

Software Preparation
If the software version of the new BBP does not match that of the base station,
collect and upload the software version of the base station to the MAE-Access.

After the upload is completed, the base station will automatically supplement the
software version of the BBP when the remote maintenance channel between the
base station and the MAE-Access is normal.

License File Preparation

● To replace an LBBP with a UBBP in LTE FDD: Apply for WDMS0UFMLF00
UBBP First-Mode license (LTE FDD) or WDMS0UMMLF00 UBBP Multi-Mode
license (LTE FDD), and update the license file.

Scenario License to Be Applied For

LTE FDD only base WDMS0UFMLF00 UBBP First-Mode License (LTE

station FDD)

LTE FDD+LTE TDD WDMS0UFMLF00 UBBP First-Mode License (LTE

FDD)

GSM+UMTS+LTE WDMS0UMMLF00 UBBP Multi-Mode license (LTE

FDD, GSM+LTE FDD, FDD)
and UMTS+LTE FDD

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 378

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Scenario License to Be Applied For

For a multimode WDMS0UFMLF00 UBBP First-Mode License (LTE

base station, the FDD)
UBBP for each
mode is unique.

– For an LTE FDD only base station, apply for the WDMS0UFMLF00 UBBP
First-Mode license (LTE FDD).
– For a multimode base station:

▪ If the base station is in LTE FDD+LTE TDD mode, apply for

WDMS0UFMLF00 UBBP First-Mode license (LTE FDD) for the UBBP
in LTE FDD mode.

▪ If the base station is in GSM+UMTS+LTE FDD, GSM+LTE FDD, or

UMTS+LTE FDD mode, a UBBP can be configured to work in multiple
modes or in a specific single mode. If the UBBP works in multiple
modes including the LTE FDD mode, apply for WDMS0UMMLF00
UBBP Multi-Mode license (LTE FDD). If the UBBP works only in LTE
FDD mode, apply for WDMS0UFMLF00 UBBP First-Mode license (LTE
FDD).
● To replace an LBBP with a UBBP in LTE TDD: Apply for LT1SUMMLFL01 UBBP
First-Mode license (LTE TDD) or LT1SUMMLFL00 UBBP Multi-Mode license
(LTE TDD), and update the license file.
– For an LTE TDD only base station, apply for the LT1SUMMLFL01 UBBP
First-Mode license (LTE TDD).
– For a multimode base station:

▪ If the base station is in LTE FDD+LTE TDD mode, apply for

LT1SUMMLFL01 UBBP First-Mode license (LTE TDD) for the UBBP in
LTE TDD mode.

▪ If the base station is in GSM+UMTS+LTE TDD, GSM+LTE TDD, or

UMTS+LTE TDD mode, a UBBP can be configured to work in multiple
modes or in a specific single mode. If the UBBP works in multiple
modes including the LTE TDD mode, apply for LT1SUMMLFL00 UBBP
Multi-Mode license (LTE TDD). If the UBBP works only in LTE TDD
mode, apply for LT1SUMMLFL01 UBBP First-Mode license (LTE TDD).
● The license file update is not required when a UBBPd is replaced with a
UBBPe.
● The license file update is not required when an LBBPc is replaced with an
LBBPd or when an LBBPd is replaced with an LBBPc.
● The license file update is not required when a UBBP is replaced with an LBBPd
in LTE FDD.
● When a UBBPg is used to replace a LBBPc/LBBPd/UBBPd/UBBPe, the following
new license items are required:
– For FDD:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 379

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

License License Item Licensing Principle

Item ID

LT1SUBBP UBBP Massive MIMO
MMOB Operating Bandwidth
1*20MHz License (FDD)
For the UBBPg, apply for license units based on the
baseband bandwidth of cells established on each
BBP. For each 20 MHz cell adopting eCPRI
transmission, one license unit is required. If the
bandwidth of a cell is less than 20 MHz, the cell
bandwidth is regarded as 20 MHz. For each 20
MHz cell adopting CPRI transmission, apply for two
license units. If the bandwidth of a cell is less than
20 MHz, the cell bandwidth is regarded as 20 MHz.

LT1SUBBP UBBP Massive MIMO One license unit is required for every 16 baseband
MMEC Extended Channel 1*16T16R TX channels except the 16 default baseband TX
License (FDD) channels per massive MIMO cell on the UBBPg.

LT1SUBBPA UBBP Antenna Bandwidth Calculate the total bandwidth supported by a

B00 3*20MHz*2T2R License (FDD) UBBPg with the following formula: Total
bandwidth supported by a UBBPg = Number of
common cells established on the UBBPg x 20 MHz
x Number of logical channels. One license unit is
required for the bandwidth of 3 x 20 MHz x 2T2R.
The number of logical channels is equal to the
larger value of TX or RX mode; if the larger value is
an odd number, it is rounded up to the nearest
integer.

– For TDD:
License License Item Licensing Principle
Item ID

LT4SUB UBBP Massive MIMO For the UBBPfw1/UBBPf3/UBBPg,

BPMMB Operating Bandwidth apply for license units based on the
D 1*20MHz License(per baseband bandwidth of cells
20MHz)(TDD) established on each BBP. For each 20
MHz cell adopting eCPRI
transmission, one license unit is
required. If the bandwidth of a cell is
less than 20 MHz, the cell
bandwidth is regarded as 20 MHz.
For each 20 MHz cell adopting CPRI
transmission, apply for two license
units. If the bandwidth of a cell is
less than 20 MHz, the cell
bandwidth is regarded as 20 MHz.

LT4SUB UBBP Massive MIMO One license unit is required for every
BPMMC Extended Channel 16 baseband TX channels except the
N 1*16T16R License 16 default baseband TX channels per
(TDD) massive MIMO cell on the UBBPfw1/
UBBPf3/UBBPg.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 380

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

License License Item Licensing Principle

Item ID

LT4SAN UBBP Antenna Calculate the total bandwidth

TBADT Bandwidth supported by a UBBPg with the
D 3*20MHz*2T2R following formula: Total bandwidth
License (TDD) supported by a UBBPg = Number of
common cells established on the
UBBPg x 20 MHz x Number of
logical channels. One license unit is
required for the bandwidth of 3 x 20
MHz x 2T2R. The number of logical
channels is equal to the larger value
of TX or RX mode; if the larger value
is an odd number, it is rounded up to
the nearest integer.

– For NB-IoT:

License License Item Licensing Principle

Item ID

LT1SUB UBBP antenna Calculate the total bandwidth

BPABM bandwidth 3x200 supported by a UBBPg with the
0 kHzx2T2R license following formula: Total bandwidth
(NB-IoT) supported by a UBBPg = Number of
NB-IoT cells established on the
UBBPg x 200 kHz x 2T2R. One
license unit is required for the
bandwidth of 3 x 200 kHz x 2T2R.
The number of logical channels is
equal to the maximum number of
TX or RX channels; if the value is an
odd number, it is rounded up to the
nearest integer.

Security Certificate Preparation

N/A

Data Preparation
Prepare data based on the scheme described in Reconfiguration Scheme. The
following table lists the data to be prepared.

NOTE

● For a co-MPT base station, configure the BBP only once and configure baseband equipment
by RAT separately.
● For a separate-MPT base station, multiple modes cannot share one BBP. Perform
configurations separately according to the procedure of expanding BBPs for each RAT.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 381

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-122 Data preparation for replacing BBPs

SN Ope MO Configuration Reference

ratio
n

1 Modi PUCCHCfg Set Delta shift to the target value for all
fy cells served by the BBP.
● If Delta shift is set to 2, change it to
1.
● If Delta shift is set to 1 or 3, no
change is required.

2 Modi RACHCfg Check the value of Indication of PRACH

fy Configuration Index in the RACHCfg
MO:
● If this parameter is set to
CFG(Configure), set PRACH
Configuration Index to the target
value for all cells served by the BBP,
ensuring that the values of PRACH
Configuration Index for all cells in
the same eNodeB are unique.
● If this parameter is set to
NOT_CFG(Not configure), no
change is required.

3 Modi BBP ● If the LBBP is replaced with a UBBP,

fy set Board Type to UBBP(UBBP) and
set Base Band Work Standard as
required.
● If the UBBP is replaced with an
LBBPd, set Board Type to
LBBP(LBBP) and Work Mode to
FDD(Frequency Division Duplex).

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 382

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Replacing BBPs"). For details, see the interactive
operation guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, the LBBPd serves only one cell and needs to be replaced
by an LBBPc.
/*Modifying the PRACH configuration index*/
MOD RACHCFG: LocalCellId=0, PrachConfigIndexCfgInd=CFG, PrachConfigIndex=6;

In the following example, an LBBPc is replaced with a UBBP.

/*Exporting the current license file and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Changing the BBP type to UBBP in FDD*/ MOD BBP: CN=0, SRN=0, SN=0, TYPE=UBBP,
BBWS=GSM-0&UMTS-0&LTE_FDD-1&LTE_TDD-0&NBIOT-0&NR-0;
/*Changing the BBP type to UBBP in TDD*/ MOD BBP: CN=0, SRN=0, SN=0, TYPE=UBBP,
BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1&NBIOT-0&NR-0;
/*Modifying the cyclic shift interval*/
MOD PUCCHCFG: LocalCellId=0, DeltaShift=DS1_DELTA_SHIFT;

In the following example, an LBBPd is replaced with a UBBP.

/*Exporting the current license file and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Changing the BBP type to UBBP in FDD*/ MOD BBP: CN=0, SRN=0, SN=0, TYPE=UBBP,
BBWS=GSM-0&UMTS-0&LTE_FDD-1&LTE_TDD-0&NBIOT-0&NR-0;
/*Changing the BBP type to UBBP in TDD*/ MOD BBP: CN=0, SRN=0, SN=0, TYPE=UBBP,
BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1&NBIOT-0&NR-0;

In the following example, a UBBPem is replaced with a UBBPf1.

/*Exporting the current license file and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Changing the board type of the BBP from UBBPem to UBBPf1*/
MOD BBP: CN=0, SRN=0, SN=0, TYPE=UBBP,BRDSPEC="UBBPf1",
BBWS=GSM-0&UMTS-0&LTE_FDD-0&LTE_TDD-1&NBIOT-0&NR-0;

In the following example, the UBBP that serves only one cell is replaced with an
LBBPd in LTE FDD.
/*Changing the board type of the BBP to LBBP*/
MOD BBP: CN=0, SRN=0, SN=0, TYPE=LBBP, WM=FDD;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 383

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.7.3.3 Engineering Implementation

This section describes the engineering implementation for replacing the BBP,
including prerequisites, context, and procedure.

Prerequisites
Information for replacing BBPs has been collected, and hardware, software and
configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Using the MAE-Deployment (capacity expansion)
NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
All the steps are remote operations except f.

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
c. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
d. Block a BBP.
Run the BLK BRD command with Block Type set to
IMMEDIATE(Immediate).
e. Deactive the cells on the BBP to be replaced.
Run the DEA CELL command to deactivate the cells bound to the BBP by
configuring the eUCellSectorEqm or EuSectorEqmGroup MO.
Example: DEA CELL: LocalCellId=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 384

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

f. (Local operation) Replace the BBP.

For details, see section "Replacing the UBBP" in BBU Hardware
Maintenance Guide. Connect cables to the new BBP according to the
cable connection scheme of the original BBP.
NOTE

If the software version of the new BBP does not match the software version of the
base station, the base station automatically supplements a software package from
the MAE-Access after the new BBP is installed without the need of a manual upgrade.
g. Deliver the configuration data to the eNodeB and activate the data. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
h. Unblock a BBP.
Run the UBL BRD command.
i. Activate the cells that are deactivated due to BBP replacement.
Run the ACT CELL command to activate the cells that are deactivated in
step e.
Example: ACT CELL: LocalCellId=0;
j. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Using the MAE-Deployment (replacement of a faulty board)
NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
All the steps are remote operations except f.
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
c. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
d. Deactive the cells on the BBP to be replaced.
Run the DEA CELL command to deactivate the cells bound to the BBP by
configuring the eUCellSectorEqm or EuSectorEqmGroup MO.
Example: DEA CELL: LocalCellId=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 385

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

e. Power off the BBP to be replaced.

Run the OPR BRDPWR command to power off the BBP.
Example: OPR BRDPWR: CN=0, SRN=0, SN=2, SW=OFF;

f. (Local operation) Replace the BBP.

For details, see section "Replacing the UBBP" in BBU Hardware
Maintenance Guide. Connect cables to the new BBP according to the
cable connection scheme of the original BBP.
NOTE

If the software version of the new BBP does not match the software version of the
base station, the base station automatically supplements a software package from
the MAE-Access after the new BBP is installed without the need of a manual upgrade.
g. Deliver the configuration data to the eNodeB and activate the data. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
h. Power on the new BBP.
Run the OPR BRDPWR command to power on the BBP.
Example: OPR BRDPWR: CN=0, SRN=0, SN=2, SW=ON;

i. Activate the cells that are deactivated due to BBP replacement.

Run the ACT CELL command to activate the cells that are deactivated in
step e.
Example: ACT CELL: LocalCellId=0;
j. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Using MML commands (capacity expansion):
NOTE

All the steps are remote operations except step 5.

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Block a BBP.
Run the BLK BRD command with Block Type set to
IMMEDIATE(Immediate).
d. Deactive the cells on the BBP to be replaced.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 386

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Run the DEA CELL command to deactivate the cells bound to the BBP by
configuring the eUCellSectorEqm or EuSectorEqmGroup MO.
Example: DEA CELL: LocalCellId=0;
e. (Local operation) Replace the BBP.
For details, see section "Replacing the UBBP" in BBU Hardware
Maintenance Guide. Connect cables to the new BBP according to the
cable connection scheme of the original BBP.
NOTE

If the software version of the new BBP does not match the software version of the
base station, the base station automatically supplements a software package from
the MAE-Access after the new BBP is installed without the need of a manual upgrade.
f. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
g. Unblock a BBP.
Run the UBL BRD command.
h. Activate the cells that are deactivated due to BBP replacement.
Run the ACT CELL command to activate the cells that are deactivated in
step 4.
Example: ACT CELL: LocalCellId=0;
i. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Using MML commands (replacement of a faulty board):
NOTE

All the steps are remote operations except step 5.

a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Deactive the cells on the BBP to be replaced.
Run the DEA CELL command to deactivate the cells bound to the BBP by
configuring the eUCellSectorEqm or EuSectorEqmGroup MO.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 387

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: DEA CELL: LocalCellId=0;

d. Power off the BBP to be replaced.
Run the OPR BRDPWR command to power off the BBP.
Example: OPR BRDPWR: CN=0, SRN=0, SN=2, SW=OFF;
e. (Local operation) Replace the BBP.
For details, see section "Replacing the UBBP" in BBU Hardware
Maintenance Guide. Connect cables to the new BBP according to the
cable connection scheme of the original BBP.
NOTE

If the software version of the new BBP does not match the software version of the
base station, the base station automatically supplements a software package from
the MAE-Access after the new BBP is installed without the need of a manual upgrade.
f. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
g. Power on the new BBP.
Run the OPR BRDPWR command to power on the BBP.
Example: OPR BRDPWR: CN=0, SRN=0, SN=2, SW=ON;
h. Activate the cells that are deactivated due to BBP replacement.
Run the ACT CELL command to activate the cells that are deactivated in
step c.
Example: ACT CELL: LocalCellId=0;
i. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.7.3.4 Engineering Verification

This section describes how to verify the replacement of BBPs.

Procedure
Step 1 Ensure that no BBP-related alarms are generated.
If any alarm is reported, clear the alarm according to instructions in 3900 & 5900
Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 388

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 3 Run the LST PUCCHCFG command and verify that the value of Delta shift is the
same as planned.
If Delta shift is not set to the modified value, view the modified configuration
data file to check whether the value is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
Step 4 Run the LST RACHCFG command and verify that the value of PRACH
Configuration Index is the same as planned.
If the value PRACH Configuration Index is not the same as planned, view the
modified configuration data file to check whether the value of PRACH
Configuration Index is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.7.3.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Remove the new BBP and its CPRI cables.
Step 2 Insert the replaced BBP and connect the CPRI cables to the BBP as the original
networking.
Step 3 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 389

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ii. Run the ACT CFGFILE command to activate the original

configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 4 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 5 Verify that engineering rollback is successful according to instructions in 1.7.3.4

Engineering Verification.

----End

1.7.4 Changing CPRI Ports for RF Modules

This section describes how to change common public radio interface (CPRI) ports
for RF modules.

1.7.4.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing CPRI ports for RF
modules.

Application Scenario
● The board configuration scheme of the BBU has changed, and the slot of a
BBP connecting to the RF modules has changed.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 390

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● An RF module on live networks does not meet service requirements and

needs to be replaced by another RF module to provide larger capacity or
coverage.

Reconfiguration Impact
During the CPRI port change, no cells served by the chain or ring where the RF
module is located can provide services.

Reconfiguration Scheme
Figure 1-58 shows the reconfiguration procedure using the MAE-Deployment.
Figure 1-59 shows the reconfiguration procedure using MML commands.

Figure 1-58 Procedure for changing CPRI ports for RF modules using the MAE-
Deployment

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 391

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-59 Procedure for changing CPRI ports for RF modules using MML
commands

Topology Change
The CPRI port numbers are changed in the network after the CPRI port change.
Use the scenario where the head CPRI port of a ring topology is changed from one
BBP to another BBP as an example. Figure 1-60 shows the topologies before and
after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 392

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-60 Topologies before and after the reconfiguration

1.7.4.2 Engineering Preparation

This section describes the engineering preparation for changing CPRI ports for RF
modules, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Information Collection
Table 1-123 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 393

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-123 Information to be collected

Information Description

CPRI topology of the RF module Chain or ring topology supported in

the LTE network

CPRI port number after the Slot number of the BBP and the CPRI
reconfiguration port number

CPRI port number before the Slot number of the BBP and the CPRI
reconfiguration port number, which are required for
engineering rollback

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

NOTE

Adjusting the CPRI port connected to an RF module affects the services of the converged party
when a separate-MPT multimode base station works in CPRI MUX scenarios. Therefore, the data
configuration of the converged party needs to be adjusted accordingly. For detailed operations,
see section related to changing CPRI ports for RF modules in Reconfiguration Guide of each RAT.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 394

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-124 Data preparation for changing CPRI ports for RF modules
Rec SN Ope MO Configuration Reference
onfi rati
gura on
tion
Mod
e

MAE 1 Mod RRUCHAIN Set breakpoints for the RRU chain or ring:
- ify ● Chain: Set only one breakpoint for a
Depl chain with the BreakPoint Position1 set
oym to 0.
ent
● Ring: Set two breakpoints for a ring with
the BreakPoint Position1 parameter set
to 0 and the BreakPoint Position2
parameter set to the RRU level number.

2 Mod RRUCHAIN When the CPRI ports after reconfiguration

ify are located on the same BBP:
● Chain: Change Head Port No. to the
target value.
● Ring: Change Head Port No. and (or)
Tail Port No. to the target values based
on whether the adjusted CPRI port
numbers are head port numbers and (or)
tail port numbers.

When the CPRI ports after reconfiguration

are located on different BBPs:
● Chain: Change Head Slot No. and Head
Port No. to the target values.
● Ring: Change Head Slot No. and (or)
Tail Slot No. as well as Head Port No.
and (or) Tail Port No. to the target
values based on whether the adjusted
CPRI port numbers are head port
numbers and (or) tail port numbers.

3 Mod RRUCHAIN Change the values of BreakPoint Position1

ify and (or) BreakPoint Position2 to 255 to
remove the breakpoints on the RRU chain or
ring.

MM 1 Mod RRUCHAIN Set breakpoints for the RRU chain or ring:

L ify ● Chain: Set only one breakpoint for a
com chain with the BreakPoint Position1 set
man to 0.
ds
● Ring: Set two breakpoints for a ring with
the BreakPoint Position1 parameter set
to 0 and the BreakPoint Position2
parameter set to the RRU level number.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 395

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO Configuration Reference

onfi rati
gura on
tion
Mod
e

2 Mod RRUCHAIN When the CPRI ports after reconfiguration

ify are located on the same BBP:
● Chain: Change Head Port No. to the
target value.
● Ring: Change Head Port No. and (or)
Tail Port No. to the target values based
on whether the adjusted CPRI port
numbers are head port numbers and (or)
tail port numbers.

When the CPRI ports after reconfiguration

are located on different BBPs:
● Chain: Change Head Slot No. and Head
Port No. to the target values.
● Ring: Change Head Slot No. and (or)
Tail Slot No. as well as Head Port No.
and (or) Tail Port No. to the target
values based on whether the adjusted
CPRI port numbers are head port
numbers and (or) tail port numbers.

3 Mod RRUCHAIN Change the values of BreakPoint Position1

ify and (or) BreakPoint Position2 to 255 to
remove the breakpoints on the RRU chain or
ring.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario-specific template being "Changing CPRI Ports for RF
Modules"): For details, see the interactive operation guide 1.11.2 Using the
Batch Reconfiguration Mode of the MAE-Deployment to Prepare Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 396

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, the topology of the CPRI ports is a ring, the head CPRI
port with the ring number 0 is changed from port 0 in slot 2 to port 0 in slot 3,
the tail CPRI port is changed from port 1 in slot 2 to port 1 in slot 3, and the
number of RRU cascading levels is 2.
/*Setting the first and second breakpoints of the RRU ring to 0 and 2, respectively*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0, BRKPOS2=2;
/*Modifying the numbers of the CPRI ports connecting the RRUs*/
MOD RRUCHAIN: RCN=0, TT=RING, BM=COLD, HSN=3, HPN=0, TSN=3, TPN=1;
/*Removing the breakpoints of the RRU ring*/
MOD RRUCHAIN: RCN=0, BRKPOS1=255, BRKPOS2=255;
/*Resetting the RF module with CN, SRN, and SN set to the cabinet number, subrack number, and slot
number of the RF module. respectively*/
RST BRD: CN=0, SRN=60, SN=0;

1.7.4.3 Engineering Implementation

This section describes the engineering implementation for changing CPRI ports for
RF modules, including prerequisites, context, and procedure.

Prerequisites
Information and data for changing the CPRI ports for RF modules are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. (Optional) If the RF modules need to be connected to another CPRI port
with the BBP position unchanged, remove the CPRI cable from the
original port and connect it to the new port.
b. (Optional) If the RF modules need to be connected to another CPRI port
with the BBP position changed, remove the BBP from the original slot
and install it in the new slot.
● Remote Operations
– Using the MAE-Deployment (MO-based):
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 397

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see 1.11.1 Setting the eNodeB Maintenance Mode.

ii. Deliver the data that you have prepared when and before changing
the CPRI port where an RF module is connected to the base station
and activate the data. For details, see the interactive operation guide
Delivering Data to Base Stations and Activating the Data.
iii. Deliver the data that you have prepared after changing the CPRI port
where an RF module is connected to the base station and activate
the data. For details, see the interactive operation guide Delivering
Data to Base Stations and Activating the Data.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

NOTE

During script activation, you are advised to activate the incremental scripts for
changing the CPRI port to which an RF module is connected, and then activate the
incremental scripts for deleting breakpoints after physical topology adjustment.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.7.4.4 Engineering Verification

This section describes how to verify the changes of CPRI ports for RF modules.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 398

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Verify that no BBP-related and RF-module-related alarms have been generated.
If any alarm is reported, clear the alarm according to instructions in 3900 & 5900
Series Base Station Alarm Reference.
Step 2 Check whether ALM-26246 BBU CPRI Line Rate Negotiation Abnormal is
reported.
If ALM-26246 BBU CPRI Line Rate Negotiation Abnormal is reported, clear the
alarm according to the instructions in 3900 & 5900 Series Base Station Alarm
Reference.
Step 3 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

----End

1.7.4.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 (Optional) If the RF modules need to be connected to another CPRI port with the
BBP position unchanged, remove the CPRI cable from the new port and connect it
to the original port.
Step 2 (Optional) If the RF modules need to be connected to another CPRI port with the
BBP position changed, remove the BBP from the new slot and install it in the
original slot.
Step 3 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 399

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. Run the DSP ROLCFGINFO command to query the configuration

rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 4 Verify that engineering rollback is successful according to instructions in 1.7.4.4

Engineering Verification.

----End

1.7.5 Adding or Deleting an RF Module

This section describes how to add or delete an RF module.

1.7.5.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology changes for adding or deleting an RF
module.

Application Scenario
● You need to add RF modules to expand the capacity or coverage when RF
modules on the live network cannot meet service requirements.
● You need to delete RF modules to meet the requirements of service
adjustment on the live network.

Reconfiguration Impact
● When you add or delete an RF module, no cells served by the chain or ring
where the RF module is located can provide services.
● After you delete an RF module, services supported by the module are
unavailable.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 400

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme
Figure 1-61 and Figure 1-62 show the reconfiguration procedures using the MAE-
Deployment. Figure 1-63 and Figure 1-64 show the reconfiguration procedures
using MML commands.

Figure 1-61 Reconfiguration procedure for adding an RF module to a chain or ring

(MAE-Deployment)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 401

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-62 Reconfiguration procedure for deleting an RF module from a chain or

ring (MAE-Deployment)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 402

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-63 Reconfiguration procedure for adding an RF module to a chain or ring

(MML commands)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 403

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-64 Reconfiguration procedure for deleting an RF module from a chain or

ring (MML commands)

Topology Change
Scenario 1: Add an RF module to a new RRU chain or ring. Use adding an RRU to
a chain topology as an example. Figure 1-65 shows the topologies before and
after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 404

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-65 Topologies before and after the reconfiguration (chain topology)

Scenario 2: Add or delete an RF module in an existing RRU chain or ring: Add or

delete an RF module in the chain head or center when the CPRI topology is chain.
Figure 1-66 shows the topology changes before and after the reconfiguration
when an RRU is added to the chain head.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 405

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-66 Topologies before and after the reconfiguration (chain topology)

Scenario 3: Add or delete an RF module in an existing RRU chain or ring: Add or

delete an RF module in the chain tail when the CPRI topology is chain. Figure
1-67 shows the topology changes before and after the reconfiguration when an
RRU is added to the chain tail.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 406

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-67 Topologies before and after the reconfiguration (chain topology)

Scenario 4: Add or delete an RF module in an existing RRU chain or ring: Add or

delete an RF module when the CPRI topology is ring. Figure 1-68 shows the
topology changes before and after the reconfiguration when an RRU is added.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 407

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-68 Topologies before and after the reconfiguration (ring topology)

Scenario 5: RF modules can be deleted but cannot be added when the CPRI
topology is load sharing.

1.7.5.2 Engineering Preparation

This section describes the engineering preparation for adding or deleting an RF
module, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 408

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Collection
Table 1-125 describes the information to be collected for data preparation.

Table 1-125 Information to be collected

Information Description

RF module information Includes the RRU model and supported

frequency band.

CPRI topology of the RF module Includes chain, ring, and load-sharing

topologies in the LTE network.

Hardware Preparation
Before you add or delete an RF module, you need to prepare the hardware listed
in Table 1-126.

Table 1-126 Hardware to be prepared

If... Then...

An RF module needs to be added Add a new RF module.

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

NOTE

● When an RF module for multiple RATs is added to a co-MPT base station, the data in the
following table is the common data of all RATs and needs to be configured only once.
● When an RF module for multiple RATs is added to a separate-MPT base station, the data in
the following table needs to be configured separated for each RAT and common parameters
must be set consistently.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 409

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-127 Data preparation for adding an RF module

Rec SN Ope MO/MML Configuration Reference
onfi rati
gura on
tion
Mod
e

MAE 1 Add RRUCHAIN Add an RRU chain or ring before you add RF
- modules to the RRU chain or ring.
Depl For details about parameter settings, see RF
oym Unit and Topology Management Feature
ent Parameter Description.
2 Mod RRUCHAIN When adding RF modules to an existing
ify RRU chain or ring:
● If RRUs are deployed in a ring topology,
skip this operation.
● If RRUs are not deployed in a ring
topology, set breakpoints for the RRU
chain or ring.
– You do not need to set breakpoints for
the RRU chain or ring when adding an
RF module to the chain tail.
– In the following situations, you need
to set breakpoints of the RRU chain or
ring:
– Add an RF module in the chain
header or center: Set a breakpoint
by setting BreakPoint Position1 to
0.

3 Mod CPRIPORT When adding RF modules to an existing

ify RRU chain or ring:
● If RRUs are not deployed in a ring
topology, skip this operation.
● If RRUs are deployed in a ring topology,
block the CPRI ports at the ring header
and tail.

4a Add RRU/RFU For details about parameter settings, see RF

Unit and Topology Management Feature
Parameter Description.
5 Mod RRUCHAIN If a breakpoint has been set for the RRU
ify chain or ring, restore the breakpoint by
setting BreakPoint Position1 to 255.

6 Mod CPRIPORT If a CPRI port in the RRU ring or chain has

ify been blocked, unblock the CPRI port.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 410

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO/MML Configuration Reference

onfi rati
gura on
tion
Mod
e

MM 1 Add ADD Add an RRU chain or ring before you add RF

L RRUCHAIN modules to the RRU chain or ring.
com For details about parameter settings, see RF
man Unit and Topology Management Feature
ds Parameter Description.
2 Mod MOD When adding RF modules to an existing
ify RRUCHAIN RRU ring or chain, set breakpoints of the
RRU ring or chain based on the following
rules:
You do not need to set breakpoints for the
RRU chain or ring when adding an RF
module to the chain tail.
In the following situations, you need to set
breakpoints of the RRU chain or ring:
● Add an RF module in the chain header or
center: Set a breakpoint by setting
BreakPoint Position1 to 0.
● Add an RF module in the ring topology:
Set two breakpoints by setting
BreakPoint Position1 to 0 and
BreakPoint Position2 to the RRU level
number.

3 Add ADD RRU For details about parameter settings, see RF

Unit and Topology Management Feature
Parameter Description.
4 Mod MOD Restore the breakpoints of the RRU chain or
ify RRUCHAIN ring if you have set the breakpoints of the
RRU chain or ring.
● If you have set a breakpoint, set
BreakPoint Position1 to 255.
● If you have set two breakpoints, set
BreakPoint Position1 and BreakPoint
Position2 to 255.

a: Using the MAE-Deployment (MO-based): When adding an RF module to a

position on the RXU ring or in the RXU chain header or center, you need to
modify the location IDs of the RF modules following this position.
Note: When the MAE-Deployment is used, item 1 to item 4 are data
preparations performed before and during RF module addition, and item 5 and
item 6 are data preparations performed after RF module addition.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 411

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-128 Data preparation for deleting an RF module

Rec SN Ope MO/MML Configuration Reference
onfi rati
gura on
tion
Mod
e

MAE 1 Mod RRUCHAIN ● If RRUs are deployed in a ring topology,

- ify skip this operation.
Depl ● If RRUs are not deployed in a ring
oym topology, set breakpoints for the RRU
ent chain or ring.
– In the following situations, you do not
need to set breakpoints of the RRU
chain or ring.
– Delete an RF module at the chain
tail.
– Delete an RF module in the load-
sharing topology.
– In the following situations, you need
to set breakpoints of the RRU chain or
ring:
– Delete an RF module in the chain
header or center: Set a breakpoint
by setting BreakPoint Position1 to
0.

2 Mod CPRIPORT ● If RRUs are not deployed in a ring

ify topology, skip this operation.
● If RRUs are deployed in a ring topology,
block the CPRI ports at the ring header
and tail.

3a Dele RRU/RFU For details about parameter settings, see RF

te Unit and Topology Management Feature
Parameter Description.
4 Mod RRUCHAIN If a breakpoint has been set for the RRU
ify chain or ring, restore the breakpoint by
setting BreakPoint Position1 to 255.

5 Mod CPRIPORT If a CPRI port in the RRU ring or chain has

ify been blocked, unblock the CPRI port.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 412

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO/MML Configuration Reference

onfi rati
gura on
tion
Mod
e

MM 1 Mod MOD Set breakpoints for the RRU chain or ring.

L ify RRUCHAIN In the following situations, you do not need
com to set breakpoints of the RRU chain or ring.
man
ds ● Delete an RF module at the chain tail.
● Delete an RF module in the load-sharing
topology.
In the following situations, you need to set
breakpoints of the RRU chain or ring:
● Delete an RF module in the chain header
or center: Set a breakpoint by setting
BreakPoint Position1 to 0.
● Delete an RF module in the ring
topology: Set two breakpoints by setting
BreakPoint Position1 to 0 and
BreakPoint Position2 to the RRU level
number.

2 Dele RMV RRU For details about parameter settings, see RF

te Unit and Topology Management Feature
Parameter Description.
3 Mod MOD Restore the breakpoints of the RRU chain or
ify RRUCHAIN ring if you have set the breakpoints of the
RRU chain or ring.
● If you have set a breakpoint, set
BreakPoint Position1 to 255.
● If you have set two breakpoints, set
BreakPoint Position1 and BreakPoint
Position2 to 255.

a: Using the MAE-Deployment (MO-based): When deleting an RF module at a

position on the RXU ring or in the RXU chain header or center, you need to
modify the location IDs of the RF modules following this position.
Note: When the MAE-Deployment is used to prepare data, item 1 to item 3 are
data preparations performed before RF module deletion, and item 4 and item 5
are data preparations performed during and after RF module deletion.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. To configure base stations in batches, you are advised to use the MAE-
Deployment batch reconfiguration mode. To configure a single base station, you
are advised to use the MAE-Deployment GUI (based on device panel).

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 413

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
When reconfiguring a single base station through the MAE-Deployment GUI, you can use either
the MO-based or the device-panel-based method. To simplify operations, the device-panel-
based method is recommended. MO-related data preparation is not involved in this method. For
detailed operations, see Procedure > Remote Operations > Using the MAE-Deployment
(based on the device panel on the GUI) in Engineering Implementation.
● Using the batch configuration mode of the MAE-Deployment:
NOTE

The following MAE-Deployment operations are performed to prepare script files for later
engineering implementation. When adding or deleting RF modules, you need to export two
incremental script files separately based on the following rules:
● When adding RF modules:
1. Based on step 1 through step 4 in Table 1-127, export the incremental script file
used before and during RF module addition.
2. Based on step 5 and step 6 in Table 1-127, export the incremental script file used
after RF module addition.
● When deleting RF modules:
1. Based on step 1 through step 3 in Table 1-128, export the incremental script file
used before and during RF module deletion.
2. Based on step 4 and step 5 in Table 1-128, export the incremental script file used
after RF module deletion.

a. On the menu bar, choose LTE Application > Network Adjustment >
Export Base Station Bulk Configuration Data to start the data export
function. The Export Base Station Bulk Configuration Data dialog box
is displayed.
b. Select the base station for which you want to add or delete an RF
module, and click Next.
c. Set Export By to Custom MOC, select the MO to be configured, and click
Next to export the batch reconfiguration file.
d. Open the exported file, modify related data as required, save the file, and
close it.
e. On the menu bar, choose LTE Application > Network Adjustment >
Import Base Station Bulk Configuration Data to start the data import
function. The Import Base Station Bulk Configuration Data dialog box
is displayed.
f. Select the modified batch reconfiguration file and click Next.
g. Select the base station for which you want to add or delete an RF
module, and click Next. After the operation is successful, click Finish.
h. In the left pane, select the base station for which you want to add or
delete an RF module, right-click the base station, and choose Check Data
from the shortcut menu. In the lower part, check verification results and
correct configuration data errors until the verification is successful.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 414

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. On the menu bar, choose Area Management > Planned Area > Export
Incremental Scripts to export incremental configuration scripts to the
base station.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

Scenario 1: Add RF modules to a new RRU chain or ring. The following describes
MML configuration scripts for data preparation when the CPRI topology is chain.
/*Adding an RRU chain (The CPRI topology is a chain.)*/
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=3, HPN=0;
/*Adding an RRU by running this command*/
ADD RRU: CN=0, SRN=61, SN=0, TP=TRUNK, RCN=1, PS=0, RT=LRRU, RS=LO, RXNUM=2, TXNUM=2;

Scenario 2: Add RF modules to or delete RF modules from an existing RRU ring or

chain. The following describes MML configuration scripts for data preparation
when the CPRI topology is chain, the RRU level is two, and you need to add or
delete an RRU in the chain header.
/*(1) Adding an RRU to the chain header (the CPRI topology is chain and the RRU level is two.)*/
/*Setting a breakpoint of the RRU chain by setting BreakPoint Position1 to 0*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0;
/*Adding an RRU by running this command*/
ADD RRU: CN=0, SRN=61, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=LO, RXNUM=2, TXNUM=2;
/*Restoring the breakpoint of the RRU chain or ring*/
MOD RRUCHAIN: RCN=0, BRKPOS1=255;
/*(2) Deleting the RRU from the chain header (the CPRI topology is chain and the RRU level is two.)*/
/*Setting a breakpoint of the RRU chain by setting BreakPoint Position1 to 0*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0;
/*Deleting an RRU by running this command*/
RMV RRU: CN=0, SRN=61, SN=0;
/*Restoring the breakpoint of the RRU chain or ring*/
MOD RRUCHAIN: RCN=0, BRKPOS1=255;

Scenario 3: Add RF modules to or delete RF modules from an existing RRU ring or

chain. The following describes MML configuration scripts for data preparation
when the CPRI topology is chain and you need to add or delete an RRU in the
chain tail.
/*(1) Adding an RRU to the chain tail (the CPRI topology is chain.)*/
/*Adding an RRU by running this command*/
ADD RRU: CN=0, SRN=61, SN=0, TP=TRUNK, RCN=0, PS=2, RT=MRRU, RS=LO, RXNUM=2, TXNUM=2;
/*(2) Deleting the RRU from the chain tail (the CPRI topology is chain.)*/
/*Deleting an RRU by running this command*/
RMV RRU: CN=0, SRN=61, SN=0;

Scenario 4: Add RF modules to or delete RF modules from an existing RRU ring or

chain. The following describes MML configuration scripts for data preparation
when the CPRI topology is ring, the RRU level is two, and you need to add or
delete an RRU in the chain or ring.
/*(1) Adding an RRU to the chain or ring (the CPRI topology is ring and the RRU level is two.)*/
/*Setting breakpoints of the RRU ring by setting BreakPoint Position1 to 0 and BreakPoint Position2 to 2*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0, BRKPOS2=2;
/*Adding an RRU by running this command*/
ADD RRU: CN=0, SRN=61, SN=0, TP=TRUNK, RCN=0, PS=2, RT=MRRU, RS=LO, RXNUM=2, TXNUM=2;
/*Restoring the breakpoint of the RRU chain or ring*/
MOD RRUCHAIN: RCN=0, BRKPOS1=255, BRKPOS2=255;
/*(2) Deleting the RRU from the chain or ring (the CPRI topology is ring and the RRU level is two.)*/
/*Setting breakpoints of the RRU ring by setting BreakPoint Position1 to 0 and BreakPoint Position2 to 2*/
MOD RRUCHAIN: RCN=0, BRKPOS1=0, BRKPOS2=2;
/*Deleting an RRU by running this command*/
RMV RRU: CN=0, SRN=61, SN=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 415

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Restoring the breakpoint of the RRU chain or ring*/

MOD RRUCHAIN: RCN=0, BRKPOS1=255, BRKPOS2=255;

Scenario 5: The following describes MML configuration scripts for data preparation
when the CPRI topology is load-sharing and you need to remove an RRU.
/*Deleting an RRU by running this command*/
RMV RRU: CN=0, SRN=61, SN=0;

1.7.5.3 Engineering Implementation

This section describes the engineering implementation for adding or deleting an
RF module, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. For details about how to add or delete an RRU, see RRU Hardware
Maintenance Guide.
b. For details about how to add or delete an RFU, see section "Replacing an
RFU" in 3900 & 5900 Series Base Station Maintenance Guide.
● Remote Operations
– Using the MAE-Deployment (MO-based):
i. To prevent unnecessary alarms from being generated during
reconfiguration, set the eNodeB maintenance mode to expansion
mode.
For detailed operations, see Setting the eNodeB Maintenance
Mode to Expand Status.
ii. Deliver the data that you have prepared used before and during RF
module addition or deletion to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
iii. Deliver the data that you have prepared used after RF module
addition or deletion to the base station and activate the data. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
iv. After data reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For detailed operations, see Setting the Maintenance Mode of the
eNodeB to NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 416

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

During script activation, you are advised to activate the incremental scripts for adding
or deleting RF modules, and then activate the incremental scripts for restoring
breakpoints after hardware reconfiguration.
– Using the MAE-Deployment (based on the device panel on the GUI):

▪ Adding an RF module:
1) In the left pane of the planned data area, right-click a physical
base station and choose Device Panel from the shortcut menu.
The device panel is displayed in the right pane, as shown in
Figure 1-69.

Figure 1-69 Device panel

1 Device navigation tree. The cabinet

navigation tree is in the upper part
and the RF module navigation tree is
in the lower part.

After you select the cabinet, subrack,

or RF unit in the device navigation
tree, the device panel of the selected
device is displayed in area 2.

2 Cabinet, subrack, and board

configuration area.

2) (Optional) Add an RF module to the newly added RRU chain or

ring.
1) Add an RXU chain/ring.
1) In the lower left part of the device panel, right-click
TOPO and choose Add Chain from the shortcut menu.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 417

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

2) Based on the planned data, set the related information

such as the number and networking mode of the RXU
chain/ring and the port on the board to which the RXU
chain/ring head is connected.
3) Click OK. The configured RXU chain/ring is displayed
under the TOPO node.
2) Add an RF board.
1) In the lower left part of the device panel, right-click a
configured RXU chain/ring, and choose Add Board >
Board Type from the shortcut menu. A dialog box is
displayed for you to add an RF board.
2) Set the working mode and other related attributes for
the RF board.
3) Click OK.
3) Deliver the data for adding RF modules to the base station
and activate the data.
On the menu bar, choose Area Management > Planned
Area > Export Incremental Scripts to export configuration
scripts.
For detailed function operations and introduction, press F1
on the MAE-Deployment or click to view section
Exporting Incremental Scripts from a Planned Data Area
in the online help.
3) (Optional and required when you need to add RF units on the
RXU ring or in the middle of the RXU chain during RXU chain/
ring capacity expansion) Add RF units to the RXU ring or in the
middle of the RXU chain.
○ Add an RF unit in the middle of the RXU chain.
1) On the RXU Topology tab page, select the board
connected to the RXU chain from the Interface board
drop-down list.
2) On the RXU Topology tab page, right-click the RXU
chain for which you want to set breakpoints, and
choose Set Break Point from the shortcut menu.
3) Right-click a position after the breakpoint where you
want to add a board and choose Add Board > Board
Type from the shortcut menu. A dialog box is displayed
for you to add an RF board.
4) Set the working mode and other related attributes for
the RF board.
5) Click OK.
6) Export the incremental scripts for adding RF boards.
On the menu bar, choose Area Management >
Planned Area > Export Incremental Scripts to export
configuration scripts.
For detailed function operations and introduction, press
F1 on the MAE-Deployment or click to view section

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 418

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Exporting Incremental Scripts from a Planned Data

Area in the online help.
7) On the RXU Topology tab page, right-click a configured
breakpoint and choose Cancel Break Point from the
shortcut menu.
8) Export the incremental scripts for deleting breakpoints.
On the menu bar of the planned data area, choose
Area Management > Planned Area > Export
Incremental Scripts. Then, export configuration scripts.
For detailed function operations and introduction, press
F1 on the MAE-Deployment or click to view section
Exporting Incremental Scripts from a Planned Data
Area in the online help.

NOTE

During script activation, you are advised to activate the

incremental scripts for adding RF boards, and then activate the
incremental scripts for deleting breakpoints after hardware
reconfiguration.
○ Add an RF unit on the RXU ring.
1) On the device panel, right-click the board where the
RXU ring is located and choose Properties from the
shortcut menu. A dialog box is displayed for you to set
properties.
2) On the CPRI Port tab page, set Administrative Status
for ports at the RXU ring head and tail to Blocked and
click OK.
3) On the RXU Topology tab page, select the board
connected to the RXU ring from the Interface board
drop-down list.
4) On the RXU Topology tab page, right-click the RXU
ring for which you want to set breakpoints, and choose
Set Break Point from the shortcut menu.
5) Set start and end positions of two breakpoints and click
OK.
6) Right-click a position between two breakpoints where
you want to add a board and choose Add Board >
Board Type from the shortcut menu. A dialog box is
displayed for you to add an RF board.
7) Set the working mode and other related attributes for
the RF board.
8) Click OK.
9) On the RXU Topology tab page, right-click a configured
breakpoint and choose Cancel Break Point from the
shortcut menu.
10) Export the incremental scripts for adding RF boards.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 419

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

On the menu bar, choose Area Management >

Planned Area > Export Incremental Scripts to export
configuration scripts.
For detailed function operations and introduction, press
F1 on the MAE-Deployment or click to view section
Exporting Incremental Scripts from a Planned Data
Area in the online help.
11) On the device panel, right-click the board where the
RXU ring is located and choose Properties from the
shortcut menu. A dialog box is displayed for you to set
properties.
12) On the CPRI Port tab page, set Administrative Status
for ports at the RXU ring head and tail to Unblocked
and click OK.
13) Export the incremental scripts for unblocking the
management status of CPRI ports.
On the menu bar, choose Area Management >
Planned Area > Export Incremental Scripts to export
configuration scripts.
For detailed function operations and introduction, press
F1 on the MAE-Deployment or click to view section
Exporting Incremental Scripts from a Planned Data
Area in the online help.

NOTE

During script activation, you are advised to activate the

incremental scripts for adding RF boards, and then activate the
incremental scripts for unblocking the management status of
CPRI ports after hardware reconfiguration.

▪ Deleting an RF module:
1) In the left pane of the planned data area, right-click a base
station you want to configure and choose Device Panel from
the shortcut menu. The device panel is displayed in the right
pane, as shown in Figure 1-70.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 420

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-70 Device panel

Area 1 Device navigation tree. The cabinet navigation tree

is in the upper part and the RF module navigation
tree is in the lower part.
After you select the cabinet, subrack, or RF unit in
the device navigation tree, the device panel of the
selected device is displayed in area 2.

Area 2 Cabinet, subrack, and board configuration area.

2) (Optional) Delete an independent RF module.

1) In the lower part of area 1, right-click the RF module you
want to delete in the topology view and choose Delete
from the shortcut menu. A confirmation dialog box is
displayed.
2) Click Yes. The system starts to delete the RF module.
3) Deliver the data for removing RF modules to the base
station and activate the data.
On the menu bar, choose Area Management > Planned
Area > Export Incremental Scripts to export configuration
scripts.
For detailed function operations and introduction, press F1
on the MAE-Deployment or click to view section
Exporting Incremental Scripts from a Planned Data Area
in the online help.
3) (Optional) To delete an RF module from the RXU ring or in the
middle of the RXU chain, you need to set breakpoints on the
RXU chain or ring.
○ Remove an RF module in the middle of the RXU chain.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 421

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1) On the RXU Topology tab page, select the board

connected to the RXU chain from the Interface board
drop-down list.
2) On the RXU Topology tab page, right-click the RXU
chain from which you want to delete an RF module,
and choose Set Break Point from the shortcut menu.
3) In the lower part of area 1, right-click the RF module
you want to delete in the topology view and choose
Delete from the shortcut menu. A confirmation dialog
box is displayed.
4) Click Yes. The system starts to delete the RF module.
5) Export the incremental scripts for deleting RF modules.
On the menu bar, choose Area Management >
Planned Area > Export Incremental Scripts to export
configuration scripts.
For detailed function operations and introduction, press
F1 on the MAE-Deployment or click to view section
Exporting Incremental Scripts from a Planned Data
Area in the online help.
6) On the RXU Topology tab page, right-click a configured
breakpoint and choose Cancel Break Point from the
shortcut menu.
7) Export the incremental scripts for deleting breakpoints.
On the menu bar, choose Area Management >
Planned Area > Export Incremental Scripts to export
configuration scripts.
For detailed function operations and introduction, press
F1 on the MAE-Deployment or click to view section
Exporting Incremental Scripts from a Planned Data
Area in the online help.
NOTE

During script activation, you are advised to activate the incremental

scripts for deleting RF modules, and then activate the incremental
scripts for removing breakpoints after hardware reconfiguration.
○ Remove an RF module from the RXU ring.
1) On the device panel, right-click the board where the
RXU ring is located and choose Properties from the
shortcut menu. A dialog box is displayed for you to set
properties.
2) On the CPRI Port tab page, set Administrative Status
for ports at the RXU ring head and tail to Blocked and
click OK.
3) On the RXU Topology tab page, right-click the RXU
ring from which you want to delete an RF module, and
choose Set Break Point from the shortcut menu.
4) Set start and end positions of two breakpoints and click
OK.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 422

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

5) In the lower part of area 1, right-click the RF module

you want to delete in the topology view and choose
Delete from the shortcut menu. A confirmation dialog
box is displayed.
6) Click Yes. The system starts to delete the RF module.
7) On the RXU Topology tab page, right-click a configured
breakpoint and choose Cancel Break Point from the
shortcut menu.
8) Export the incremental scripts for deleting RF modules.
On the menu bar, choose Area Management >
Planned Area > Export Incremental Scripts to export
configuration scripts.
For detailed function operations and introduction, press
F1 on the MAE-Deployment or click to view section
Exporting Incremental Scripts from a Planned Data
Area in the online help.
9) On the device panel, right-click the board where the
RXU ring is located and choose Properties from the
shortcut menu. A dialog box is displayed for you to set
properties.
10) On the CPRI Port tab page, set Administrative Status
for ports at the RXU ring head and tail to Unblocked
and click OK.
11) Export the incremental scripts for unblocking the
management status of CPRI ports.
On the menu bar, choose Area Management >
Planned Area > Export Incremental Scripts to export
configuration scripts.
For detailed function operations and introduction, press
F1 on the MAE-Deployment or click to view section
Exporting Incremental Scripts from a Planned Data
Area in the online help.

NOTE

During script activation, you are advised to activate the incremental

scripts for deleting RF modules, and then activate the incremental
scripts for removing breakpoints after hardware reconfiguration.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 423

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

2) Run the ULD CFGFILE command to export the configuration file.

For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.7.5.4 Engineering Verification

This section describes how to verify that an RF module is added or deleted.

Procedure
Step 1 Verify that no RF-module-related alarms have been generated.
If any alarm is reported, clear the alarm according to instructions in 3900 & 5900
Series Base Station Alarm Reference.
Step 2 Verify that ALM-26236 RRU Cascading Levels and Configuration Mismatch,
ALM-26238 RRU Network Topology Type and Configuration Mismatch,
ALM-26246 BBU CPRI Line Rate Negotiation Abnormal, or ALM-26501 RF Unit
Optical Module or Electrical Port Not Ready is not reported.
If any preceding alarm is reported, clear the alarm according to instructions in
3900 & 5900 Series Base Station Alarm Reference.
Step 3 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

----End

1.7.5.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 If you have added an RF module, you need to remove the added RF module and
restore the CPRI topology to the status before the reconfiguration.
Step 2 If you have deleted an RF module, you need to insert the deleted RF module into
the original slot and restore the CPRI topology to the status before the
reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 424

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 3 Restore the configuration data.

● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 4 Verify that engineering rollback is successful according to instructions in 1.7.5.4

Engineering Verification.

----End

1.7.6 Transmission Capacity Expansion from One LMPT Board

to LMPT + UMPT Boards (Mode 1) (TDD) (IPv4 Transmission
Only)
This section describes how to expand transmission capacity from one LMPT board
to LMPT + UMPT boards.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 425

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.7.6.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for expanding transmission capacity
from one LMPT board to LMPT + UMPT boards.

Application Scenario
To implement BBU interconnection, a UMPT needs to be configured for each
existing BBU that uses an LMPT as the main control board. The UMPT functions as
the main control board, and the LMPT functions as the transmission board to
share transmission loads with the UMPT.

NOTE

The UMPTe and the LMPT cannot be installed in the same BBU. Only the UMPTa/UMPTb can be
installed in the same BBU with the LMPT.

NOTE

If the old transmission configuration model is used for the LMPT before reconfiguration, the old
model is still used after the transmission capacity expansion from one LMPT board to LMPT +
UMPT boards.
If the new transmission configuration model is used for the LMPT before reconfiguration, the
new model is used after the transmission capacity expansion from one LMPT board to LMPT +
UMPT boards.

Reconfiguration Impact
● During the reconfiguration, the MAE-Access is disconnected from the NE.
● During the reconfiguration, the services on the eNodeB become unusable.

Reconfiguration Scheme
Hardware adjustment is required during the transmission capacity expansion from
one LMPT board to LMPT + UMPT boards. A UMPT is installed in slot 6 in the
BBU. The LMPT and the cables connected to it are the same as those before the
reconfiguration.

Topology Change
Figure 1-71 shows the BBU hardware configuration before and after the
reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 426

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-71 Hardware configuration before and after the reconfiguration

1.7.6.2 Engineering Preparation

This section describes the engineering preparation for expanding transmission
capacity from one LMPT board to LMPT + UMPT boards, including information
collection and preparation of hardware, software, license files, security certificates,
and data. It also describes the data preparation mode.

Information Collection
Table 1-129 describes the information to be collected before transmission capacity
expansion.

NOTE

● Old model: The Transmission Configuration Mode parameter in the GTRANSPARA MO

is set to OLD.
● New model: The Transmission Configuration Mode parameter in the GTRANSPARA
MO is set to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 427

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-129 Information to be collected

Information Description

Local IP in the A new IP address must be planned as the Local IP

OMCH MO parameter value in the OMCH MO.
This IP address and the device IP address (old model)/
IPv4 address (new model) in slot 7 must be on the
same network segment but differ from each other.

License file The license file for the LMPT must be uploaded.

Configuration file The configuration file on the LMPT must be uploaded.

Hardware Preparation
Table 1-130 describes the hardware to be prepared before data reconfiguration.

Table 1-130 Hardware to be prepared

New Hardware Quantity

UMPT One board for each BBU

Software Preparation
Prepare software in the target version for the UMPT. The software version must be
the same as that of the LMPT.

License File Preparation

Prepare a new license file if the license file in use needs to be updated.

Security Certificate Preparation

N/A

Data Preparation
N/A

Data Preparation Mode

N/A

1.7.6.3 Engineering Implementation

This section describes the engineering implementation for expanding transmission
capacity from one LMPT board to LMPT + UMPT boards, including prerequisites,
context, and procedure. Configuration data can be adjusted locally or remotely.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 428

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Prerequisites
Information and data required for the transmission capacity expansion are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
Step 1 On the MAE-Access, upgrade the LMPT software and export its configuration file
and license file. You do not need to upgrade the software if the LMPT is operating
in the target version.
1. Upgrade the BBU with the LMPT as the main control board to the target
version before reconfiguring the hardware. For details, see the eNodeB
upgrade guide.
2. Back up the license file in use on the MAE-Access as follows: Choose License
> NE License Management > Stand-Alone > NE License Maintenance > NE
License Maintenance Operation > Back Up License File.
3. Download the license file from the MAE-Access to the local PC as follows:
Choose License > NE License Management > Stand-Alone > NE License
Maintenance > NE License Maintenance Operation > Obtain Backup
License File.
4. Run the ADD BRD command to add a UMPT in slot 6.
Step 2 On the LMT, activate the UMPT configuration file and upgrade the UMPT
software.
1. Connect the LMT to the UMPT in slot 6. (The default IP address for local
maintenance of the UMPT is 192.168.0.49.) For details about how to connect
the LMT to the UMPT, see Getting Started with the LMT > Logging In to
and Exiting the LMT in 3900 & 5900 Series Base Station LMT User Guide. For
details about troubleshooting for LMT usage, see FAQ in 3900 & 5900 Series
Base Station LMT User Guide.
2. Configure the FTP server on the PC where the LMT is installed. Save the
backup LMPT configuration file in the FTP folder. Run the DLD CFGFILE
command to import the backup LMPT configuration file into the UMPT and
run the ACT CFGFILE command with Effect Type set to AFTER_RESET to
activate the configuration file.
Example:
DLD CFGFILE: MODE=IPV4, IP="197.12.11.220", USR="admin",
PWD="*****", FN="CFGDATA.XML", ENCRYPTMODE=UNENCRYPTED;
ACT CFGFILE: EFT=AFTER_RESET;
3. Run the DSP BRDVER command to query the information about the board
version. If the software is not in the target version, go to Step 2.5. If the
software is in the target version, skip Step 2.5.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 429

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example:

DSP BRDVER:;
4. (Optional) Prepare the preconfiguration script file based on the eNodeB
hardware configuration by referring to References > Preparing a Pre-
configuration Script in 3900 & 5900 Series Base Station Commissioning Guide.
5. (Optional) Run the DLD SOFTWARE command with Download by Config
Flag set to CFG(Download by configuration) and Delay Download Flag set
to NO(Not Delay Download) to download the software in the target version.
Run the LST SOFTWARE command to check whether the software in the
standby workspace is in the target version. If not, download the software
again. If yes, run the ACT SOFTWARE command to activate the software.

Example:

LST SOFTWARE:;

ACT SOFTWARE: OT=NE, SV="BTS3900 V100R009C00SPC050";

NOTE

Ensure that the version (including the patch version) of the UMPT is the same as that
of the LMPT.
6. Three minutes after the UMPT in slot 6 resets, connect the LMT to the UMPT.
(The local maintenance IP address of the UMPT is the same as that of the
LMPT.)
7. Run MML commands to add a UMPT in slot 6, remove the OMCH from slot 7,
add an OMCH to slot 6, and enable the ARP proxy function for the Ethernet
port that uses the IP address of the board in slot 7.

Example:

Old Model

/*Adding a UMPT in slot 6 (the board will reset)*/

ADD BRD: SN=6, BT=UMPT;

/*Removing the OMCH from slot 7*/

RMV OMCH:FLAG=MASTER;

/*Adding an OMCH to slot 6 with the new IP address*/

ADD
OMCH:IP="177.12.12.150",MASK="255.255.255.0",PEERIP="177.16.22.34",P
EERMASK="255.255.255.0",BEAR=IPV4,BRT=NO;

/*Enabling the ARP proxy function for the Ethernet port that uses the IP
address of the board in slot 7 (The operation fails because there is no board
installed in slot 7. However, the configuration takes effect.) */

SET ETHPORT: SN=7, SBT=BASE_BOARD, PA=COPPER, SPEED=AUTO,

DUPLEX=AUTO, ARPPROXY=ENABLE;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 430

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

The ETHPORT.ARPPROXY parameter will be deleted in later versions. In the current

version, this parameter is configurable but the DISABLE value always takes effect.
Therefore, avoid using this parameter.

New Model
8. Run the SET MNTMODE command to set Maintenance Mode of the eNodeB
to ExpandStatus1.

Example:

SET MNTMODE: MNTMode=ExpandStatus1;

Step 3 Onsite operation: Reconfigure hardware.

1. Insert the prepared UMPT in slot 6. This step triggers an active/standby
switchover of the main control boards. After this step is performed, the UMPT
becomes active, and the LMPT becomes standby.
2. (Optional) If the system uses the GNSS clock source, remove the GNSS
antenna connected to the LMPT and connect it to the UMPT. On the MAE-
Access, run the RMV GNSS command to remove the GNSS clock link from
slot 7 and run the ADD GNSS command to add a GNSS clock link to slot 6.

Example:

RMV GNSS:;

ADD GNSS: SRN=0, SN=6;

NOTE

If the system uses the RGPS clock source, skip this step.

Step 4 Operation on the MAE-Access: Reconfigure data.

1. Select the NE on the MAE-Access topology, change its remote maintenance IP
address to the value of Local IP in the OMCH MO.
2. Install the license file downloaded from the MAE-Access for the UMPT. To
install the license file, choose License > NE License Management > Stand-
Alone > NE License Maintenance > NE License Maintenance Operation >
Load License File on the MAE-Access.

----End

1.7.6.4 Engineering Verification

This section describes how to verify the transmission capacity expansion from one
LMPT board to LMPT + UMPT boards.

Procedure
Step 1 Check whether a new alarm is reported.

Example:

● ALM-25886 IP Path Fault

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 431

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● ALM-25901 Remote Maintenance Link Failure

● ALM-25888 SCTP Link Fault
● ALM-26263 IP Clock Link Failure
● ALM-26266 Time Synchronization Failure
● ALM-25899 BFD Session Fault
● ALM-29201 S1 Interface Fault
● ALM-29204 X2 Interface Fault

If any alarm is reported, clear the alarm according to instructions in 3900 & 5900
Series Base Station Alarm Reference.

Step 2 After data reconfiguration is complete, set the eNodeB maintenance mode to
NORMAL. For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.7.6.5 Engineering Rollback

If the reconfiguration fails, the eNodeB configuration can be rolled back to the
original state.

Procedure
Step 1 Check the maintenance mode of the eNodeB. If it is NORMAL, go to Step 2.
Otherwise, go to Step 3.

Step 2 Set the maintenance mode of the eNodeB to EXPAND. For details, see Setting the
eNodeB Maintenance Mode to Expand Status.

Step 3 Run the MOD PEERMODE command to clear the standby status of the LMPT. The
LMPT resets.

Step 4 Remove the UMPT from slot 6. The LMPT in slot 7 resets and functions as the
active board.

NOTICE

If the LMPT in slot 7 does not function as the active board 5 minutes after the
UMPT is removed, perform the following operations:
1. Remove the LMPT from slot 7 and install it in slot 6, and wait until it functions
as the active board.
2. After the LMPT functions as the active board, remove it from slot 6 and install
it back in slot 7. Then, the LMPT functions properly.

Step 5 On the MAE-Access, change the remote maintenance IP address to the IP address
before reconfiguration.

Step 6 Run the MML command to remove the UMPT from slot 6.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 432

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 7 Set the maintenance mode of the eNodeB to NORMAL. For details, see Setting
the Maintenance Mode of the eNodeB to NORMAL.

----End

1.7.7 Transmission Capacity Expansion from One LMPT Board

to LMPT + UMPT Boards (Mode 2) (TDD) (IPv4 Transmission
Only)
This section describes how to change the transmission mode of an existing BBU.
Compared with mode 1, an Ethernet cable between the UMPT and the switch is
added in mode 2.

1.7.7.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for expanding transmission capacity
from one LMPT board to LMPT + UMPT boards.

Application Scenario
To implement BBU interconnection, a UMPT needs to be configured for each
existing BBU that uses an LMPT as the main control board. The UMPT functions as
the main control board, and the LMPT functions as the transmission board to
share transmission loads with the UMPT.

NOTE

The UMPTe and the LMPT cannot be installed in the same BBU. Only the UMPTa/UMPTb can be
installed in the same BBU with the LMPT.

NOTE

If the old transmission configuration model is used for the LMPT before reconfiguration, the old
model is still used after the transmission capacity expansion from one LMPT board to LMPT +
UMPT boards.
If the new transmission configuration model is used for the LMPT before reconfiguration, the
new model is used after the transmission capacity expansion from one LMPT board to LMPT +
UMPT boards.

Reconfiguration Impact
● During the reconfiguration, the MAE-Access is disconnected from the NE.
● During the reconfiguration, the services on the eNodeB become unusable.

Reconfiguration Scheme
Hardware adjustment is required during the transmission capacity expansion from
one LMPT board to LMPT + UMPT boards. The UMPT is installed in slot 6 in the
BBU and cables are connected. The LMPT and the cables connected to it are the
same as those before the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 433

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Figure 1-72 shows the BBU hardware configuration before and after the
reconfiguration.

Figure 1-72 Hardware configuration before and after the reconfiguration

1.7.7.2 Engineering Preparation

This section describes the engineering preparation for expanding transmission
capacity from one LMPT board to LMPT + UMPT boards, including information
collection and preparation of hardware, software, license files, security certificates,
and data. It also describes the data preparation mode.

Information Collection
Table 1-131 describes the information to be collected before transmission capacity
expansion.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 434

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the old transmission configuration model is used for the LMPT before reconfiguration, the
old model is still used after the transmission capacity expansion from one LMPT board to
LMPT + UMPT boards.
If the new transmission configuration model is used for the LMPT before reconfiguration,
the new model is used after the transmission capacity expansion from one LMPT board to
LMPT + UMPT boards.

Table 1-131 Information to be collected

Information Description

Local IP in the active A new IP address must be planned as the Local IP

OMCH MO parameter value in the active OMCH MO.
This IP address and the device IP address (old model)/
IPv4 address (new model) in slot 7 must be on the
same network segment but differ from each other.

DEVIP (old model)/ A new IP address needs to be planned as the device IP

IPADDR4 (new address (old model)/IPv4 address (new model) of the
model) UMPT in slot 6.
This IP address and the device IP address (old model)/
IPv4 address (new model) configured in slot 7 must be
on different network segments.

License file The license file for the LMPT must be uploaded.

Configuration file The configuration file on the LMPT must be uploaded.

Hardware Preparation
Table 1-132 describes the hardware to be prepared before data reconfiguration.

Table 1-132 Hardware to be prepared

New Hardware Quantity

UMPT One board for each BBU

Network cable One

Software Preparation
Prepare software in the target version for the UMPT. The software version must be
the same as that of the LMPT.

License File Preparation

Prepare a new license file if the license file in use needs to be updated.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 435

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Security Certificate Preparation

N/A

Data Preparation
N/A

Data Preparation Mode

N/A

1.7.7.3 Engineering Implementation

This section describes the engineering implementation for expanding transmission
capacity from one LMPT board to LMPT + UMPT boards, including prerequisites,
context, and procedure. Configuration data can be adjusted locally or remotely.

Prerequisites
Information and data required for the transmission capacity expansion are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
Step 1 On the MAE-Access, upgrade the LMPT software and export its configuration file
and license file.
1. Upgrade the BBU with the LMPT as the main control board to the target
version before reconfiguring the hardware. For details, see the eNodeB
upgrade guide.
2. Back up the license file in use on the MAE-Access as follows: Choose License
> NE License Management > Stand-Alone > NE License Maintenance > NE
License Maintenance Operation > Back Up License File.
3. Download the license file from the MAE-Access to the local PC as follows:
Choose License > NE License Management > Stand-Alone > NE License
Maintenance > NE License Maintenance Operation > Obtain Backup
License File.
4. Run the ADD BRD command to add a UMPT in slot 6.
Step 2 On the LMT, activate the UMPT configuration file, and upgrade the UMPT
software.
1. Connect the LMT to the UMPT in slot 6. (The default IP address for local
maintenance of the UMPT is 192.168.0.49.) For details about how to connect
the LMT to the UMPT, see Getting Started with the LMT > Logging In to
and Exiting the LMT in 3900 Series Base Station LMT User Guide. For details

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 436

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

about troubleshooting for LMT usage, see FAQ in 3900 Series Base Station
LMT User Guide.
2. Configure the FTP server on the PC where the LMT is installed. Save the
backup LMPT configuration file in the FTP folder. Run the DLD CFGFILE
command to import the backup LMPT configuration file to the UMPT and run
the ACT CFGFILE command with Effect Type set to AFTER_RESET to activate
the configuration file.
Example:
DLD CFGFILE: MODE=IPV4, IP="197.12.11.220", USR="admin",
PWD="*****", FN="CFGDATA.XML", ENCRYPTMODE=UNENCRYPTED;
ACT CFGFILE: EFT=AFTER_RESET;
3. Run the DSP BRDVER command to query the information about the board
version. If the software is not in the target version, go to Step 2.5. If the
software is in the target version, skip Step 2.5.
Example:
DSP BRDVER:;
4. (Optional) Prepare the preconfiguration script file based on the eNodeB
hardware configuration by referring to References > Preparing a Pre-
configuration Script in 3900 & 5900 Series Base Station Commissioning Guide.
5. (Optional) Run the DLD SOFTWARE command with Download by Config
Flag set to CFG(Download by configuration) and Delay Download Flag set
to NO(Not Delay Download) to download the software in the target version.
Run the LST SOFTWARE command to check whether the software in the
standby workspace is in the target version. If not, download the software
before the reconfiguration again. If yes, run the ACT SOFTWARE command to
activate the software.
Example:
LST SOFTWARE:;
ACT SOFTWARE: OT=NE, SV="BTS3900 V100R009C00SPC050";

NOTE

Ensure that the version (including the patch version) of the UMPT is the same as that
of the LMPT.
6. Three minutes after the UMPT in slot 6 resets, connect the LMT to the UMPT.
(The local maintenance IP address of the UMPT is the same as that of the
LMPT.)
7. Run MML commands to add a UMPT in slot 6, remove the OMCH from slot 7,
add the active OMCH to slot 6, and enable the ARP proxy function for the
Ethernet port that uses the IP address of the board in slot 7.
Example:
Old Model
/*Adding a UMPT in slot 6 (the board will reset)*/
ADD BRD: SN=6, BT=UMPT;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 437

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Removing the OMCH from slot 7*/

RMV OMCH:FLAG=MASTER;
/*Adding the active OMCH to slot 6 with the new IP address*/
ADD
OMCH:IP="177.12.12.150",MASK="255.255.255.0",PEERIP="177.16.22.34",P
EERMASK="255.255.255.0",BEAR=IPV4,BRT=NO;
/*Enabling the ARP proxy function for the Ethernet port that uses the IP
address of the board in slot 7 (The operation fails because there is no board
installed in slot 7. However, the configuration takes effect.) */
SET ETHPORT: SN=7, SBT=BASE_BOARD, PA=COPPER, SPEED=AUTO,
DUPLEX=AUTO, ARPPROXY=ENABLE;

NOTE

The ETHPORT.ARPPROXY parameter will be deleted in later versions. In the current

version, this parameter is configurable but the DISABLE value always takes effect.
Therefore, avoid using this parameter.

New Model
/*Adding a UMPT in slot 6 (the board will reset)*/
ADD BRD: SN=6, BT=UMPT;
/*Removing the OMCH from slot 7*/
RMV OMCH:FLAG=MASTER;
/*Adding the active OMCH to slot 6 with the new IP address*/
ADD
OMCH:IP="177.12.12.150",MASK="255.255.255.0",PEERIP="177.16.22.34",P
EERMASK="255.255.255.0",BEAR=IPV4,BRT=NO;
/*Enabling the ARP proxy function for the INTERFACE MO that uses the IPv4
address of the board in slot 7*/
MOD INTERFACE: ITFID=1, ARPPROXY= ENABLE;
8. Run MML commands to add a device IP address, an S1 interface, an IP path,
and a standby OMCH for the UMPT in slot 6.
Old Model
/*Adding a device IP address for the board in slot 6*/
ADD DEVIP: SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, IP="177.12.11.131",
MASK="255.255.255.0";
The S1 interface can be added in endpoint or link mode.
– Endpoint mode
/*Adding an SCTP parameter template*/
ADD SCTPTEMPLATE: SCTPTEMPLATEID=16,
SWITCHBACKFLAG=ENABLE;
/*Adding an SCTP host*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 438

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD SCTPHOST: SCTPHOSTID=16, IPVERSION=IPv4,

SIGIP1V4="177.12.11.131", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=1024, SCTPTEMPLATEID=16;
/*Adding an endpoint group*/
ADD EPGROUP: EPGROUPID=16;
/*Adding the SCTP host to the endpoint group*/
ADD SCTPHOST2EPGRP:EPGROUPID=16,SCTPHOSTID=16;
/*Adding a user-plane host*/
, IPSECSWITCH=DISABLEADD USERPLANEHOST: UPHOSTID=16,
IPVERSION=IPv4, LOCIPV4="177.12.11.131", IPSECSWITCH=DISABLE;
/*Adding the user-plane host to the endpoint group*/
ADD UPHOST2EPGRP: EPGROUPID=16, UPHOSTID=16;
/*Adding an S1 object*/
ADD S1: S1Id=1, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG,
CpEpGroupId=16, UpEpGroupId=16;
– Link mode
/*Adding an SCTP link to slot 6*/
ADD SCTPLNK: SCTPNO=1, SN=6, LOCIP="177.12.11.131",
LOCPORT=2910, PEERIP="177.12.180.10", PEERPORT=2910,
AUTOSWITCH=ENABLE;
/*Adding a control port bearer*/
ADD CPBEARER:
CPBEARID=1,BEARTYPE=SCTP,LINKNO=1,FLAG=MASTER;
/*Adding an S1 interface*/
ADD S1INTERFACE: S1InterfaceId=1, S1CpBearerId=1, CnOperatorId=0;
/*Adding an IP path to slot 6*/
ADD IPPATH: PATHID=1, SN=6, SBT=BASE_BOARD, PT=ETH,
JNRSCGRP=DISABLE, LOCALIP="177.12.11.131",
PEERIP="177.12.164.100", ANI=0, APPTYPE=S1, PATHTYPE=ANY;
/*Adding the application type of the IP path*/
ADD ENODEBPATH:IPPATHID=1,APPTYPE=S1;
/*Adding a standby OMCH to slot 6*/
ADD OMCH: FLAG=SLAVE, IP="177.12.11.131", MASK="255.255.255.0",
PEERIP="10.71.22.34", PEERMASK="255.255.255.0", BEAR=IPV4, BRT=NO;
/*Adding an IP route to slot 6*/
ADD IPRT: SN=6, SBT=BASE_BOARD, DSTIP="177.12.180.0",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="177.12.11.1";
ADD IPRT: SN=6, SBT=BASE_BOARD, DSTIP="177.12.164.0",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="177.12.11.1";
ADD IPRT: SN=6, SBT=BASE_BOARD, DSTIP="10.0.0.0",
DSTMASK="255.0.0.0", RTTYPE=NEXTHOP, NEXTHOP="177.12.11.1";
For details about how to configure sector- and cell-related parameters, see
3900 & 5900 Series Base Station Initial Configuration (Using MML

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 439

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Commands) > Initially Configuring a Single eNodeB Using MML

Commands > Configuring Radio Data in 3900 & 5900 Series Base Station
Initial Configuration Guide.
New Model
/*Adding a device IP address to the board in slot 6*/
SET ETHPORT: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PN=0, PORTID=1;
ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1,
VRFIDX=0;
ADD IPADDR4: ITFID=0, IP="177.12.11.131", MASK="255.255.255.0";
/*Adding an IP route*/
ADD IPROUTE4: RTIDX=0, DSTIP="177.12.180.0",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="177.12.11.1";
ADD IPROUTE4: RTIDX=1, DSTIP="177.12.164.0",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="177.12.11.1";
ADD IPROUTE4: RTIDX=2, DSTIP="10.0.0.0", DSTMASK="255.0.0.0",
RTTYPE=NEXTHOP, NEXTHOP="177.12.11.1";
The S1 interface can be added in endpoint or link mode.
– Endpoint mode
/*Adding an SCTP parameter template*/
ADD SCTPTEMPLATE: SCTPTEMPLATEID=16,
SWITCHBACKFLAG=ENABLE;
/*Adding an SCTP host*/
ADD SCTPHOST: SCTPHOSTID=16, IPVERSION=IPv4,
SIGIP1V4="177.12.11.131", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=1024, SCTPTEMPLATEID=16;
/*Adding an endpoint group*/
ADD EPGROUP: EPGROUPID=16;
/*Adding the SCTP host to the endpoint group*/
ADD SCTPHOST2EPGRP:EPGROUPID=16,SCTPHOSTID=16;
/*Adding a user-plane host*/
, IPSECSWITCH=DISABLEADD USERPLANEHOST: UPHOSTID=16,
IPVERSION=IPv4, LOCIPV4="177.12.11.131", IPSECSWITCH=DISABLE;
/*Adding the user-plane host to the endpoint group*/
ADD UPHOST2EPGRP: EPGROUPID=16, UPHOSTID=16;
/*Adding an S1 object*/
ADD S1: S1Id=1, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG,
CpEpGroupId=16, UpEpGroupId=16;
– Link mode
/*Adding an SCTP link*/
ADD SCTPLNK: SCTPNO=1, LOCIP="177.12.11.131", LOCPORT=2910,
PEERIP="177.12.180.10", PEERPORT=2910, AUTOSWITCH=ENABLE;
/*Adding a control port bearer*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 440

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD
CPBEARER:CPBEARID=1,BEARTYPE=SCTP,LINKNO=1,FLAG=MASTER;
/*Adding an S1 interface*/
ADD S1INTERFACE: S1InterfaceId=1, S1CpBearerId=1, CnOperatorId=0;
/*Adding an IP path*/
ADD IPPATH: PATHID=1, TRANSCFGMODE=NEW,
JNIPRSCGRP=DISABLE, BPT=ETH, PORTID=1,
LOCALIP="177.12.11.131", PEERIP="177.12.164.100", ANI=0,
APPTYPE=S1, PATHTYPE=ANY;
/*Adding the application type of the IP path*/
ADD ENODEBPATH:IPPATHID=1,APPTYPE=S1;

/*Adding a standby OMCH*/

ADD OMCH: FLAG=SLAVE, IP="177.12.11.131", MASK="255.255.255.0",

PEERIP="10.71.22.34", PEERMASK="255.255.255.0", BEAR=IPV4, BRT=NO;

For details about how to configure sector- and cell-related parameters, see
3900 & 5900 Series Base Station Initial Configuration (Using MML
Commands) > Initially Configuring a Single eNodeB Using MML
Commands > Configuring Radio Data in 3900 & 5900 Series Base Station
Initial Configuration Guide.
9. Run the SET MNTMODE command to set Maintenance Mode of the eNodeB
to ExpandStatus1.

Example:

SET MNTMODE: MNTMode=ExpandStatus1;

Step 3 Onsite operation: Reconfigure hardware.

1. Insert the prepared UMPT in slot 6. This step triggers an active/standby
switchover of the main control boards. After this step is performed, the UMPT
becomes active, and the LMPT becomes standby.
2. (Optional) If the system uses the GNSS clock source, remove the GNSS
antenna connected to the LMPT and connect it to the UMPT. On the MAE-
Access, run the RMV GNSS command to remove the GNSS clock link from
slot 7 and run the ADD GNSS command to add a GNSS clock link to slot 6.

Example:

RMV GNSS:;

ADD GNSS: SRN=0, SN=6;

NOTE

If the system uses the RGPS clock source, skip this step.

Step 4 Operation on the MAE-Access: Reconfigure data.

1. On the MAE-Access topology, change the active remote maintenance IP
address to the Local IP parameter value (177.12.12.150) in the OMCH MO,
and change the standby remote maintenance IP address to the new device IP
address of the board in slot 6 (177.12.11.131) for the selected NE.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 441

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

2. Install the license file downloaded from the MAE-Access for the UMPT. To
install the license file, choose License > NE License Management > Stand-
Alone > NE License Maintenance > NE License Maintenance Operation >
Load License File on the MAE-Access.

----End

1.7.7.4 Engineering Verification

This section describes how to verify the transmission capacity expansion from one
LMPT board to one LMPT board plus one UMPT board.

Procedure
Step 1 Check whether a new alarm is reported.

Example:

● ALM-25886 IP Path Fault

● ALM-25901 Remote Maintenance Link Failure
● ALM-25888 SCTP Link Fault
● ALM-26263 IP Clock Link Failure
● ALM-26266 Time Synchronization Failure
● ALM-25899 BFD Session Fault
● ALM-25891 IKE Negotiation Failure
● ALM-29201 S1 Interface Fault
● ALM-29204 X2 Interface Fault

If any alarm is reported, clear the alarm according to instructions in 3900 & 5900
Series Base Station Alarm Reference.

Step 2 After data reconfiguration is complete, set the eNodeB maintenance mode to
NORMAL. For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.7.7.5 Engineering Rollback

If the reconfiguration fails, the eNodeB configuration can be rolled back to the
original state.

Procedure
Step 1 Check the maintenance mode of the eNodeB. If it is NORMAL, go to Step 2.
Otherwise, go to Step 3.

Step 2 Set the maintenance mode of the eNodeB to EXPAND. For details, see Setting the
eNodeB Maintenance Mode to Expand Status.

Step 3 Run the MOD PEERMODE command to clear the secondary status of the LMPT.
The LMPT resets.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 442

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 4 Remove the UMPT from slot 6. The LMPT in slot 7 resets and functions as the
active board.

NOTICE

If the LMPT in slot 7 does not function as the active board 5 minutes after the
UMPT is removed, perform the following operations:
1. Remove the LMPT from slot 7 and install it in slot 6, and wait until it functions
as the active board.
2. After the LMPT functions as the active board, remove it from slot 6 and install
it back in slot 7. Then, the LMPT functions properly.

Step 5 On the MAE-Access, change the active remote maintenance IP address to the IP
address before reconfiguration, and remove the standby remote maintenance IP
address.

Step 6 Run the MML command to remove the UMPT from slot 6.

Step 7 Set the maintenance mode of the eNodeB to NORMAL. For details, see Setting
the Maintenance Mode of the eNodeB to NORMAL.

----End

1.7.8 Transmission Capacity Expansion from One UMPT Board

to Two UMPT Boards (FDD/NB-IoT) (IPv4 Transmission Only)
This section describes how to expand transmission capacity from one UMPT board
to two UMPT boards.

1.7.8.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for expanding transmission capacity
from one UMPT board to two UMPT boards.

Application Scenario
You can expand transmission capacity from one UMPT board to two UMPT boards
if the traffic that flows over the eNodeB configured with a single UMPT board
cannot meet service requirements.

Currently, the UMPTb board is used for LTE. The total uplink and downlink
throughput supported by UMPTb+UMPTb can reach 4 Gbit/s.

NOTE

If the old transmission configuration model is used for the UMPT before reconfiguration, the old
model is still used after the transmission capacity expansion to two UMPT boards.
If the new transmission configuration model is used for the UMPT before reconfiguration, the
new model is still used after the transmission capacity expansion to two UMPT boards.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 443

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Impact
No impact

Reconfiguration Scheme
Figure 1-73 shows the reconfiguration procedure for expanding the transmission
capacity of an eNodeB from one UMPT board to two UMPT boards.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Figure 1-73 Procedure for transmission capacity expansion from one UMPT board
to two UMPT boards

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 444

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-74 Procedure for transmission capacity expansion from one UMPT board
to two UMPT boards

NOTE

If a base station is configured with two UMPT boards, digital-certification-based secure

networking cannot be set up on both boards simultaneously.

Topology Change
After a new UMPT board is added, two UMPT boards must be connected to
different ports of transmission equipment to ensure transmission throughput.
Assume that two UMPT boards are connected to two different ports on the same
switch and router. Figure 1-75 shows the topologies before and after the
reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 445

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-75 Topologies before and after the reconfiguration

1.7.8.2 Engineering Preparation

This section describes the engineering preparation for expanding transmission
capacity from one UMPT board to two UMPT boards, including information
collection and preparation of hardware, software, license files, security certificates,
and data. It also describes the data preparation mode and provides MML
configuration script examples.

Information Collection
Table 1-133 describes the information to be collected for data preparation.

NOTE

● Old model: The Transmission Configuration Mode parameter in the GTRANSPARA MO

is set to OLD.
● New model: The Transmission Configuration Mode parameter in the GTRANSPARA
MO is set to NEW.

Table 1-133 Information to be collected

Information Description

Device IP address (old Includes the device IP address (old model)/IPv4

model)/IPv4 address (new address (new model), subnet mask, and the
model) of the new UMPT physical port number in use.
board

Information about the Includes the local device IP address (old model)/
route from the new UMPT IPv4 address (new model) and the next-hop IP
board to the S-GW address.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 446

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

VLAN ID for the new -

UMPT board

ID of the endpoint group -

to which the new user-
plane host is to be added

Hardware Preparation
Table 1-134 describes the hardware to be prepared before expanding transmission
capacity from one UMPT board to two UMPT boards.

Table 1-134 Hardware to be prepared

Hardware Description

UMPT board The UMPT board model must be the same as the
model of the existing UMPT board installed on the
base station.

Cables used to connect The cables can be optical fibers or network cables,
the eNodeB and the peer depending on the type of the peer device.
device

Software Preparation
N/A

License File Preparation

To add a UMPT board to expand the capacity, you need to apply for the
LT1S0THROU00 Throughput Capacity(per Mbps)(FDD) license units with a
capacity of 4000 Mbit/s. Therefore, you need to update the license file.

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 447

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-135 Data preparation for transmission capacity expansion from one UMPT
board to two UMPT boards
SN Ope MO Configuration Reference
ratio
n

1 Add RU (using MML For details about parameter settings, see

commands)/MPT Base Station Cabinets and Subracks
(using the MAE- (Including the BBU Subrack)
Deployment) Configuration Feature Parameter
Description.
2 Add DEVIP The gateway IP addresses that the two
UMPT boards are connected to must be
3 Add SRCIPRT located on different network segments.
4 Add VLANMAP For details, see IP eRAN Engineering
Guide Feature Parameter Description.
5 Add USERPLANEHOST For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

6 Modi EPGROUP Add the new user-plane host to the

fy endpoint group.

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Table 1-136 Data preparation for transmission capacity expansion from one UMPT
board to two UMPT boards
SN Ope MO Configuration Reference
ratio
n

1 Add RU (using MML For details about parameter settings, see

commands)/MPT Base Station Cabinets and Subracks
(using the MAE- (Including the BBU Subrack)
Deployment) Configuration Feature Parameter
Description.
2 Modi ETHPORT The gateway IP addresses that the two
fy UMPT boards are connected to must be
located on different network segments.
3 Add INTERFACE
For details, see IP eRAN Engineering
4 Add IPADDR4 Guide Feature Parameter Description.
5 Add SRCIPROUTE4

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 448

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

6 Add USERPLANEHOST For details, see LTE and NR NSA S1 and

X2 Self-Management Feature Parameter
Description.

7 Modi EPGROUP Add the new user-plane host to the

fy endpoint group.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Transmission Capacity Expansion from One
UMPT Board to Two UMPT Boards"). For details, see the interactive operation
guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The following provides examples for transmission capacity expansion from one
UMPT board to two UMPT boards.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a UMPT board in slot 6*/
ADD BRD: CN=0, SRN=0, SN=6, BT=UMPT;
/*Adding a device IP address for port 1 with the subnet mask of 255.255.255.0*/
ADD DEVIP: SN=6, SBT=BASE_BOARD, PT=ETH, PN=1, IP="182.169.0.33", MASK="255.255.255.0";
/*Adding a source IP route from the new UMPT board to the S-GW*/
ADD SRCIPRT: SRCRTIDX=0, SN=6, SBT=BASE_BOARD, SRCIP="182.169.0.33", RTTYPE=NEXTHOP,
NEXTHOP="182.169.0.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group with the next-
hop IP address of 182.169.0.1 and subnet mask of 255.255.255.255*/
ADD VLANMAP: NEXTHOPIP="182.169.0.1", MASK="255.255.255.255", VLANMODE=SINGLEVLAN,

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 449

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

VLANID=110, SETPRIO=DISABLE;
/*Adding a user-plane host*/
ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="182.169.0.33", IPSECSWITCH=DISABLE, ;
/*Adding the user-plane host to the endpoint group*/
ADD UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1;

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a UMPT board in slot 6*/
ADD BRD: CN=0, SRN=0, SN=6, BT=UMPT;
/*Setting Ethernet port 1*/
SET ETHPORT: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PN=1, PORTID=1;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD VLANMAP: NEXTHOPIP="182.169.0.1", MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
VLANID=110, SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=110, VRFIDX=0;
/*Adding an IPv4 address with the subnet mask of 255.255.255.0*/
ADD IPADDR4: ITFID=0, IP="182.169.0.33", MASK="255.255.255.0";
/*Adding a source IP route from the new UMPT board to the S-GW*/
ADD SRCIPROUTE4: SRCRTIDX=0, SRCIP="182.169.0.33", RTTYPE=NEXTHOP, NEXTHOP="182.169.0.1",
MTUSWITCH=OFF;
/*Adding a user-plane host*/
ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="182.169.0.33", IPSECSWITCH=DISABLE, ;
/*Adding the user-plane host to the endpoint group*/
ADD UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1;

1.7.8.3 Engineering Implementation

This section describes the engineering implementation for expanding transmission
capacity from one UMPT board to two UMPT boards, including prerequisites,
context, and procedure.

Prerequisites
Information for expanding the transmission capacity from one UMPT board to two
UMPT boards has been collected, and the hardware, license file, and configured
data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 450

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

a. Insert the new UMPT board into the subrack.

b. Connect the transmission port of the new UMPT board to the gateway.
● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 451

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iv. After the reconfiguration is complete, set the eNodeB maintenance

mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.7.8.4 Engineering Verification

This section describes how to verify transmission capacity expansion from one
UMPT board to two UMPT boards.

Procedure
Step 1 Verify that the following alarms are not reported:

● ALM-26205 BBU Board Maintenance Link Failure

● ALM-25880 Ethernet Link Fault
If any alarm is reported, clear the alarm according to instructions in 3900 &
5900 Series Base Station Alarm Reference.

Step 2 Run the DSP BRD command and check whether there is an entry for the new
UMPT board.

If there is no entry for the new UMPT board, perform the following operations:

If… Then...

The reconfiguration Check whether the configuration data file is the same as
is performed on the planned.
MAE-Deployment ● If they are different, modify the configuration data
file again and import it into the system. Then perform
the operations in Engineering Implementation again
to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the
data is imported into the system or delivered to the
base station. In this situation, contact Huawei
technical support or dial the Huawei technical support
hotline.

MML commands are Check whether parameter settings are correct in the
used for MML command script.
reconfiguration ● If they are incorrect, modify the parameters in the
script and perform the operations in Engineering
Implementation again to deliver the data to the
eNodeB and activate it.
● If they are correct, contact Huawei technical support
or dial the Huawei technical support hotline.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 452

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 3 Run the DSP DEVIP (old model)/DSP IPADDR4 (new model) command and check
whether there is an entry for the new device IP address (old model)/IPv4 address
(new model).
If there is no entry for the new device IP address (old model)/IPv4 address (new
model), perform the following operations:

If… Then...

The reconfiguration Check whether the configuration data file is the same as
is performed on the planned.
MAE-Deployment ● If they are different, modify the configuration data
file again and import it into the system. Then perform
the operations in Engineering Implementation again
to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the
data is imported into the system or delivered to the
base station. In this situation, contact Huawei
technical support or dial the Huawei technical support
hotline.

MML commands are Check whether parameter settings are correct in the
used for MML command script.
reconfiguration ● If they are incorrect, modify the parameters in the
script and perform the operations in Engineering
Implementation again to deliver the data to the
eNodeB and activate it.
● If they are correct, contact Huawei technical support
or dial the Huawei technical support hotline.

Step 4 Enable a UE to repeatedly access the network and trace S1 interface messages.
When the same S-GW is selected for two consecutive times, ensure that the local
IP addresses of the two UMPT boards are alternatively allocated for the links
carrying the user plane.
If they are not alternatively allocated, contact Huawei technical support or dial the
Huawei technical support hotline.

----End

1.7.8.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 453

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands:

– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Remove the newly added UMPT board, and restore hardware cable connections.

Step 4 Check whether the engineering rollback is successful.

● Verify that the following alarms are not generated.
– ALM-26205 BBU Board Maintenance Link Failure
– ALM-25880 Ethernet Link Fault
If any alarm is reported, clear the alarm according to instructions in 3900
& 5900 Series Base Station Alarm Reference.
● Run DSP BRD to check whether there is an entry for the new UMPT board.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 454

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If there is an entry for the new UMPT board, contact Huawei technical
support or dial the Huawei technical support hotline.

----End

1.7.9 Signaling Capacity Expansion from One UMPT to One

Primary UMPT + One Extension UMPT/LMPT (IPv4
Transmission Only)
This section describes how to expand a base station from one UMPT to one
primary UMPT + one extension UMPT/LMPT to improve signaling capacity.

NOTE

5900 series base stations do not support any scenario involving LMPT boards. If such a scenario
exists, adjust it based on site requirements.

1.7.9.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for expanding a base station from
one UMPT to one primary UMPT + one extension UMPT/LMPT to improve
signaling capacity.

Application Scenario
NOTE

The UMPTe and the LMPT cannot be installed in the same BBU. Only the UMPTa/UMPTb can be
installed in the same BBU with the LMPT.

One UMPT is configured for a base station currently and the signaling capacity of
the base station cannot meet service requirements. To improve signaling capacity,
the base station can be expanded from one UMPT to one primary UMPT + one
extension UMPT/LMPT.

NOTE

The transmission configuration model of the base station remains unchanged after the
reconfiguration.

Reconfiguration Impact
No impact

Reconfiguration Scheme
Adjust hardware and configurations when you expand a base station from one
UMPT to one primary UMPT + one extension UMPT/LMPT to improve signaling
capacity. The original UMPT and transmission cables remain unchanged when you
insert the extension board into a slot other than the slot for the primary UMPT.
You also need to set Prefer Signal Extend Switch to ON when expanding a base
station from one UMPT to one primary UMPT + one extension LMPT to improve
signaling capacity.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 455

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the hardware capability of the new UMPT is higher than that of the existing UMPT (for
example, the hardware capability of the UMPTe is higher than that of the UMPTb), perform the
steps for replacing the main control board first as described in 1.7.1 Replacing the Main
Control Board When No SeGW Is Deployed and 1.7.2 Replacing the Main Control Board
When an SeGW Is Deployed .
If more than 18 cells or more than 96 X2 links have been configured for a base station, the base
station cannot be expanded from one UMPT to one primary UMPT + one extension LMPT for
signaling capacity improvement.

Topology Change
Figure 1-76 shows the topologies before and after signaling capacity expansion
from one UMPT to one primary UMPT + one extension UMPT.

Figure 1-76 Topologies before and after the reconfiguration (signaling capacity
expansion from one UMPT to one primary UMPT + one extension UMPT)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 456

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-78 shows the topologies before and after signaling capacity expansion
from one UMPT to one primary UMPT + one extension LMPT.

Figure 1-77 Topologies before and after the reconfiguration (signaling capacity
expansion from one UMPT to one primary UMPT + one extension LMPT)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 457

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-78 Topologies before and after the reconfiguration (signaling capacity
expansion from one UMPT to one primary UMPT + one extension LMPT)

1.7.9.2 Engineering Preparation

This section describes the engineering preparation for expanding a base station
from one UMPT to one primary UMPT + one extension UMPT/LMPT to improve
signaling capacity, including information collection and preparation of hardware,
software, license files, security certificates, and data. It also describes the data
preparation mode and provides MML configuration script examples.

Information Collection
Table 1-137 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 458

eRAN
Reconfiguration Guide
Table 1-137 Information to be collected
Information
Deployment types of the primary
UMPT and the extension UMPT/LMPT
Value of the Prefer Signal Extend
Switch parameter of the
GLOBALPROCSWITCH MO
Software version of the primary UMPT
Software version of the extension
UMPT/LMPT
Hardware Preparation
Table 1-138 describes the hardware you need to obtain before expanding a base
station from one UMPT to one primary UMPT + one extension UMPT/LMPT to
improve signaling capacity.
Table 1-138 Hardware to be prepared
If...
A base station is expanded from one
UMPT to one primary UMPT + one
extension UMPT to improve signaling
capacity
A base station is expanded from one
UMPT to one primary UMPT + one
extension LMPT to improve signaling
capacity
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Description
The deployment type of the primary
UMPT must be the same as that of the
extension board.
-
If the board type of the extension
UMPT/LMPT is different from that of
the primary UMPT and automatic
software supplement fails, you need to
manually supplement software.
Therefore, you need to obtain the
software version of the primary UMPT
in advance. When automatic software
supplement fails, the output of the
DSP BRD command shows that the
value of Operational State for the
extension UMPT/LMPT is Disabled.
The software version of the extension
UMPT/LMPT must be within N-2 (N
indicates the software version of the
primary UMPT).
Then...
Prepare one UMPT.
Prepare one LMPT.
459
eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation
If the board type of the extension UMPT/LMPT is different from that of the
primary UMPT and automatic software supplement fails, you need to manually
supplement software. Therefore, you need to obtain the version of the software
that the base station runs in advance.

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Table 1-139 Data preparation for signaling capacity expansion from one UMPT to
one primary UMPT + one extension UMPT/LMPT

SN Ope MO Configuration Reference

ratio
n

1 Add RU (using MML ● When you expand a base station

commands)/MPT from one UMPT to one primary
(using the MAE- UMPT + one extension UMPT, insert
Deployment) the extension UMPT into a slot other
than the slot for the primary UMPT.a
● When you expand a base station
from one UMPT to one primary
UMPT + one extension LMPT, insert
the extension LMPT into a slot other
than the slot for the primary UMPT.
For details about parameter settings, see
Base Station Cabinets and Subracks
(Including the BBU Subrack)
Configuration Feature Parameter
Description.
2 Modi BrdResAssignment If Board Resource Assignment Mode is
fy set to MODE3 for the primary or
extension UMPTe, Board Resource
Assignment Mode must be also set to
MODE3 for the other UMPTe board.

3 Modi GlobalProcSwitch When you expand a base station from

fy one UMPT to one primary UMPT + one
extension LMPT, set Prefer Signal
Extend Switch to ON.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 460

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

a: When the original UMPT is reused and installed in the slot not for the
primary UMPT and parameters are configured after the board installation, run
the MOD PEERMODE command with RAT set to LTE or LTE_TDD to ensure the
functionality of the extension UMPT.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment (batch
reconfiguration mode and GUI) or MML commands. You are advised to configure
base stations in batches using the MAE-Deployment batch reconfiguration mode
or configure a single base station using MML commands. The three data
preparation modes are described as follows:

● Using the MAE-Deployment batch reconfiguration mode (with the name of

the scenario-specific template being "Signaling Capacity Expansion from One
UMPT to One Primary UMPT + One Extension UMPT/LMPT"): For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data
area is consistent with that in the current data area. If the data is inconsistent, you can
choose Area Management > Planned Area > Synchronize Planned Area NEs from the
menu bar to synchronize data from the current data area to the planned data area. Then,
perform the following operations.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The following example shows the MML configuration script for data preparation
when an eNodeB is expanded from one UMPT (slot 7) to one primary UMPT (slot
7) + one extension LMPT (slot 6):
/*Adding an LMPT as an extension board*/
ADD BRD: SN=6, BT=LMPT;
/*Setting PreferSigExtend to ON when you expand the eNodeB from one UMPT to one primary UMPT to
one extension LMPT*/
MOD GLOBALPROCSWITCH: PreferSigExtend=ON;

1.7.9.3 Engineering Implementation

This section describes the engineering implementation for expanding a base
station from one UMPT to one primary UMPT + one extension UMPT/LMPT to
improve signaling capacity, including prerequisites, context, and procedure.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 461

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Prerequisites
You have obtained the information, hardware, software, and data required for
expanding a base station from one UMPT to one primary UMPT + one extension
UMPT/LMPT to improve signaling capacity, and have placed the license file to the
specified directory on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

To expand the base station from one UMPT to one primary UMPT + one
extension UMPT/LMPT, insert the extension UMPT/LMPT into a slot other
than the slot for the primary UMPT.
● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
iii. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 462

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iii. Use the MAE-Access to deliver the batch configuration scripts

prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. (Optional) Supplement software.
NOTE

If the board type of the extension UMPT/LMPT is different from that of the
primary UMPT and automatic software supplement fails, you need to manually
supplement software using the MAE or the local web LMT. When automatic
software supplement fails, the output of the DSP BRD command shows that the
value of Operational State for the extension UMPT/LMPT is Disabled.
To supplement software on the MAE, run the SPL SOFTWARE
command. Example: SPL
SOFTWARE:MODE=IPV4,IP="10.141.16.55",USR="ftpuser",PWD="*
****",DIR="/export/home/sysm/ftproot/ROSA/Software/
BTS3900_5900 V100R0XXCXXSPCXXX",SDL=YES;
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.7.9.4 Engineering Verification

This section describes how to verify that a base station is successfully expanded
from one UMPT to one primary UMPT + one extension UMPT/LMPT to improve
signaling capacity.

Procedure
Step 1 Check that no related alarm (for example, ALM-26205 BBU Board Maintenance
Link Failure) is reported. If any related alarm is reported, clear the alarm
according to the instructions in 3900 & 5900 Series Base Station Alarm Reference.
Step 2 Run the DSP BRD command and check whether the value of Availability Status
for the extension UMPT/LMPT in the command output is Normal.
If the value of Availability Status is Communication lost or Starting up, run the
DSP SOFTSTATUS command to query the status of the base station software, and
then check whether the activation progress of the extension UMPT/LMPT is
included in Result of NE software management status query.
● If it is, software is being supplemented from the MAE to the extension UMPT/
LMPT.
● If it is not, check whether a correct software version is available and the FTP
software is correctly configured on the MAE. If a correct software version is
available and the FTP software is correctly configured, contact Huawei
technical support or dial the Huawei technical support hotline.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 463

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 3 During peak hours, subscribe to and obtain the counters L.SIG.Board.CallAttempt
and L.SIG.Board.CallAttempt.Max under the measurement object eNodeB Board
Call Processing Measurement through the MAE. If the values of the two counters
for the extension UMPT/LMPT are not zero, the extension board has started
processing signaling data and the signaling capacity expansion is successful.
NOTE

L.SIG.Board.CallAttempt indicates the number of call processing times in a board and

L.SIG.Board.CallAttempt.Max indicates the maximum number of call processing times in a
board.

----End

1.7.9.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state. To reduce the impact of an engineering rollback on services, you
are advised to perform the engineering rollback during off-peak hours.

Procedure
Step 1 Check the maintenance mode of the eNodeB. If it is NORMAL, go to Step 2.
Otherwise, go to Step 3.
Step 2 Set the maintenance mode of the eNodeB to EXPAND. For details, see Setting the
eNodeB Maintenance Mode to Expand Status.
Step 3 Restore the configuration data.
● Using MML commands: Delete the extension UMPT or LMPT through the
MAE.
a. Run the following commands by following the instructions provided in
1.3.3 Running MML Commands on the MAE-Access:

▪ The extension UMPT or LMPT is installed in slot 6: RMV BRD:SN=6;

▪ The extension UMPT or LMPT is installed in slot 7: RMV BRD:SN=7;

b. Run the MOD GLOBALPROCSWITCH command to restore the value of
PreferSigExtend if you have expanded the base station from one UMPT
to one primary UMPT + one extension LMPT.
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 464

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 4 Remove the new extension UMPT/LMPT and restore hardware cable connections.
Step 5 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.
Step 6 Set the maintenance mode of the eNodeB to NORMAL. For details, see Setting
the Maintenance Mode of the eNodeB to NORMAL.
----End

1.7.10 Signaling Capacity Expansion from One LMPT to One

Primary UMPT + One Extension LMPT (IPv4 Transmission
Only)
This section describes how to expand an eNodeB from one LMPT to one primary
UMPT + one extension LMPT to improve signaling capacity.

NOTE

5900 series base stations do not support any scenario involving LMPT boards. If such a scenario
exists, adjust it based on site requirements.

1.7.10.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for expanding an eNodeB from one
LMPT to one primary UMPT + one extension LMPT to improve signaling capacity.

Application Scenario
NOTE

The UMPTe and the LMPT cannot be installed in the same BBU. Only the UMPTa/UMPTb can be
installed in the same BBU with the LMPT.

Currently, only one LMPT is configured for an eNodeB and the signaling capacity
of the eNodeB cannot meet service requirements. To improve signaling capacity,

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 465

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

the eNodeB can be expanded from one LMPT to one primary UMPT + one
extension LMPT. To do so, the main control board needs to be replaced before an
extension board is added.

Reconfiguration Impact
When replacing the main control board, you must power off and power on the
eNodeB to make the configuration take effect. During the operation, the eNodeB
cannot provide services.

Reconfiguration Scheme
During the signaling capacity expansion from one LMPT to one primary UMPT +
one extension LMPT, you need to reconfigure software and hardware. Figure 1-79
shows the reconfiguration process.

Figure 1-79 Reconfiguration process of the signaling capacity expansion from one
LMPT to one primary UMPT + one extension LMPT

NOTE

● If more than 18 cells or more than 96 X2 links are configured for an eNodeB, the eNodeB
cannot be expanded from one LMPT to one primary UMPT + one extension LMPT for
signaling capacity improvement.
● When the primary LMPT of an eNodeB is running properly, do not insert a UMPT into a slot
other than the slot for the primary LMPT. Otherwise, the eNodeB cannot provide services.

Topology Change
Figure 1-80 shows the topologies before and after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 466

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-80 Topologies before and after the reconfiguration (signaling capacity
expansion from one LMPT to one primary UMPT + one extension LMPT)

1.7.10.2 Engineering Preparation

This section describes the engineering preparation for expanding an eNodeB from
one LMPT to one primary UMPT + one extension LMPT to improve signaling
capacity, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Information Collection
Table 1-140 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 467

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-140 Information to be collected

Information Description

Data configuration file of the original The latest configuration data must be
LMPT manually exported before the
reconfiguration.

Deployment types of the LMPT to be The deployment type of the LMPT to

replaced and the extension LMPT be replaced must be the same as that
of the extension LMPT.

Value of the Prefer Signal Extend -

Switch parameter of the
GLOBALPROCSWITCH MO

Software version of the LMPT to be ● Before you replace the LMPT of an

replaced eNodeB with a UMPT, you need to
obtain the version of the software
that the eNodeB runs.
● When you add an extension board
to improve signaling capacity, you
need to manually supplement
software if automatic software
supplement fails. Therefore, you
need to obtain the version of the
software that the NE runs in
advance. When automatic software
supplement fails, the output of the
DSP BRD command shows that the
value of Operational State for the
extension LMPT is Disabled.

Software version of the extension The software version of the extension

LMPT LMPT must be within N-2 (N indicates
the software version of the primary
UMPT).

Hardware Preparation
Table 1-141 describes the hardware you need to obtain before expanding an
eNodeB from one LMPT to one primary UMPT + one extension LMPT to improve
signaling capacity.

Table 1-141 Hardware to be prepared

If... Then...

- Prepare one UMPT and a maintenance

adapter cable.

You need to use a new LMPT as the Prepare one LMPT.

extension board

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 468

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

You are advised to use a new LMPT (not the original LMPT replaced with a UMPT) as the
extension board. Otherwise, you need to perform operations described in the sections related to
replacing the main control board during an engineering rollback.

Software Preparation
Obtain the version of the software that the eNodeB runs.

License File Preparation

When you replace the original LMPT with a UMPT, obtain a new license if no
license file is loaded to the UMPT, the control items in the license file cannot meet
service requirements, or the license has expired.

Security Certificate Preparation

When you replace the original LMPT with a UMPT (in security networking), obtain
the CA certificate from the telecom operator.

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare.
The data preparation for the signaling capacity expansion from one LMPT to one
primary UMPT + one extension LMPT consists of two parts: replacing the original
LMPT with a UMPT and adding an extension LMPT.
● Data preparation for replacing the original LMPT with a UMPT:
– In non-security networking, see the following section: Replacing the
Main Control Board When No SeGW Is Deployed > Engineering
Preparation > Data Preparation.
– In security networking, see the following section: Replacing the Main
Control Board When an SeGW Is Deployed > Engineering Preparation
> Data Preparation.
● Data preparation for adding an extension LMPT:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 469

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-142 Data preparation for adding an extension LMPT

SN Ope MO Configuration Reference
ratio
n

1 Add RU (using MML Insert the extension LMPT into a slot

commands)/MPT other than the slot for the main control
(using the MAE- board.
Deployment) For details about parameter settings, see
Base Station Cabinets and Subracks
(Including the BBU Subrack)
Configuration Feature Parameter
Description.
2 Modi GlobalProcSwitch When you expand an eNodeB from one
fy LMPT to one primary UMPT + one
extension LMPT, set Prefer Signal
Extend Switch to ON.

Data Preparation Mode

The data preparation for the signaling capacity expansion from one LMPT to one
primary UMPT + one extension LMPT consists of two parts: replacing the original
LMPT with a UMPT and adding an extension LMPT.
● Data preparation mode of replacing the original LMPT with a UMPT (the
MAE-Deployment-based batch reconfiguration mode is recommended):
– In non-security networking, see the following section: Replacing the
Main Control Board When No SeGW Is Deployed > Engineering
Preparation > Data Preparation Mode.
– In security networking, see the following section: Replacing the Main
Control Board When an SeGW Is Deployed > Engineering Preparation
> Data Preparation Mode.
● Data preparation mode of adding an extension LMPT:
The data preparation for adding an extension LMPT can be performed using
the MAE-Deployment (batch reconfiguration mode or GUI) or MML
commands. You are advised to configure base stations in batches using the
MAE-Deployment batch reconfiguration mode or configure a single base
station using MML commands. The three data preparation methods are as
follows:
– Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Adding an Extension LMPT Board for
Signaling Capacity Expansion"). For details, see the interactive operation
guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
Deployment to Prepare Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 470

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned
data area is consistent with that in the current data area. If the data is inconsistent,
you can choose Area Management > Planned Area > Synchronize Planned Area
NEs from the menu bar to synchronize data from the current data area to the
planned data area. Then, perform the following operations.
– Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
– Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML
configuration script examples.

MML Configuration Script Example

The following example shows the MML configuration script for adding an
extension LMPT when an eNodeB is expanded from one LMPT to one primary
UMPT (slot 7) + one extension LMPT (slot 6).
/*Adding an LMPT as the extension board*/
ADD BRD: SN=6, BT=LMPT;
/*Setting PreferSigExtend to ON when you expand the eNodeB from one LMPT to one primary UMPT + one
extension LMPT*/
MOD GLOBALPROCSWITCH: PreferSigExtend=ON;

1.7.10.3 Engineering Implementation

This section describes the engineering implementation for expanding an eNodeB
from one LMPT to one primary UMPT + one extension LMPT to improve signaling
capacity, including prerequisites, context, and procedure.

Prerequisites
You have obtained the information, hardware, software, and data required for
expanding an eNodeB from one LMPT to one primary UMPT + one extension
LMPT to improve signaling capacity, and have placed the license file to the
specified directory on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.
The signaling capacity expansion from one LMPT to one primary UMPT + one
extension LMPT consists of two parts: replacing the original LMPT with a UMPT
and adding an extension LMPT. The expansion involves local operations and
remote operations. Figure 1-81 shows the expansion process.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 471

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-81 Engineering implementation process of the signaling capacity

expansion from one LMPT to one primary UMPT + one extension LMPT

Procedure
Step 1 (Remote operation) Set the eNodeB maintenance engineering mode to the
expand status.

To avoid reporting of alarms generated during reconfiguration, set the eNodeB

engineering maintenance mode to expand status.

For detailed operations, see Setting the eNodeB Maintenance Mode to Expand
Status.

Step 2 (Local operation + Remote operation) Replace the original LMPT with a UMPT.
● In non-security networking, see the following: Replacing the Main Control
Board When No SeGW Is Deployed > Engineering Implementation >
Procedure.
● In secure networking, see the following: Replacing the Main Control Board
When an SeGW Is Deployed > Engineering Implementation > Procedure.

Step 3 (Local operation) Insert an extension LMPT into the slot other than the slot for the
main control board.

Step 4 (Remote operation) Add the extension LMPT.

● Using the MAE-Deployment: Deliver the prepared data to the base station
and activate the data. For details, see the interactive operation guide
Delivering Data to Base Stations and Activating the Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 472

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands:

a. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
b. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
c. (Optional) Supplement software.
NOTE

If automatic software supplement fails, you need to manually supplement software

through the MAE-Access or the web LMT. When automatic software supplement fails,
the output of the DSP BRD command shows that the value of Operational State for
the extension LMPT is Disabled.

Step 5 (Remote operation) Set the maintenance engineering mode of the eNodeB to
Normal after the reconfiguration is complete. For detailed operations, see Setting
the Maintenance Mode of the eNodeB to NORMAL.

----End

1.7.10.4 Engineering Verification

This section describes how to verify that an eNodeB is successfully expanded from
one LMPT to one primary UMPT + one extension LMPT to improve signaling
capacity.

Procedure
Step 1 Verify that the reconfiguration for replacing the original LMPT with a UMPT is
successful.
● In non-security networking, see the following section: Replacing the Main
Control Board When No SeGW Is Deployed > Engineering Verification >
Procedure.
● In security networking, see the following section: Replacing the Main
Control Board When an SeGW Is Deployed > Engineering Verification >
Procedure.
Step 2 Verify that the reconfiguration for adding an extension LMPT is successful.
1. Check that no related alarm (for example, ALM-26205 BBU Board
Maintenance Link Failure) is reported. If any related alarm is reported, clear
the alarm by following the instructions provided in 3900 & 5900 Series Base
Station Alarm Reference.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 473

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

2. Run the DSP BRD command and check whether the value of Availability
Status for the extension LMPT in the command output is Normal.
If the value of Availability Status is Communication lost or Starting up, run
the DSP SOFTSTATUS command to query the status of the eNodeB software,
and then check whether the activation progress of the extension LMPT is
included in Result of NE software management status query.
– If yes, software is being supplemented from the MAE-Access.
– If no, check whether a correct software version is available and the FTP
software is correctly configured on the MAE-Access. If a correct software
version is available and the FTP software is correctly configured, contact
Huawei technical support or dial the Huawei technical support hotline.
Step 3 During peak hours, subscribe to and obtain the counters L.SIG.Board.CallAttempt
and L.SIG.Board.CallAttempt.Max under the measurement object eNodeB Board
Call Processing Measurement through the MAE-Access. If the value of the either
of the counters for the extension LMPT is not zero, the extension LMPT has started
processing signaling data and the signaling capacity expansion is successful.

----End

1.7.10.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state. To reduce the impact of an engineering rollback on services, you
are advised to perform the engineering rollback during off-peak hours.

Procedure
Step 1 (Remote operation) Check the maintenance mode of the base station. If it is
NORMAL, go to Step 2. Otherwise, go to Step 3.
Step 2 (Remote operation) Set the maintenance mode of the eNodeB to EXPAND. For
details, see Setting the eNodeB Maintenance Mode to Expand Status.
Step 3 (Local operation) Remove the extension LMPT.
Step 4 (Local operation) Power off the base station and remove the new UMPT.
Step 5 (Local operation) Insert the original LMPT and power on the base station.
All information such as the software and data configuration file before the
signaling capacity expansion is stored on the original LMPT. The base station is
automatically rolled back to its original status after the original LMPT is inserted.

NOTE

If the original LMPT is used as the extension board during the signaling capacity expansion, you
need to replace the new UMPT with another LMPT. For detailed operations, see 1.7.1 Replacing
the Main Control Board When No SeGW Is Deployed or 1.7.2 Replacing the Main Control
Board When an SeGW Is Deployed .

Step 6 (Local operation) Restore hardware cable connections.

Step 7 (Remote operation) Verify that the engineering rollback is successful.
1. Verify that ALM-25880 Ethernet Link Fault is not reported.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 474

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If ALM-25880 Ethernet Link Fault is reported, clear the alarm by following

the instructions provided in 3900 & 5900 Series Base Station Alarm Reference.
2. Run the DSP CELL command. Verify that Cell instance state is Normal for
the cell.
If Cell instance state is Uninstall, check the cell configuration or hardware
based on the value of Reason for latest state change in the command
output.
3. In security networking scenarios (including PSK and PKI), run the DSP OMCH
command to check whether the status of the OMCH between the eNodeB
and the MAE-Access is Normal.
If OM Channel Status is not Normal, perform the following steps:
a. From the main menu on the MAE-Access, choose Topology > Main
Topology to check whether the eNodeB is in connection. If it is, contact
Huawei technical support or dial the Huawei technical support hotline. If
it is not, go to Step 7.3.b.
b. Check the modified data file to check whether the ports in non-secure
networking are correctly configured:

▪ If the configuration is incorrect, modify the configuration data file

and perform the operations in Engineering Implementation again
to deliver the data to the base station and activate the data.

▪ If the configuration is correct, an error has occurred during the

configuration data download or activation. In this situation, contact
Huawei technical support or dial the Huawei technical support
hotline.
Step 8 (Remote operation) Set the maintenance mode of the eNodeB to NORMAL. For
details, see Setting the Maintenance Mode of the eNodeB to NORMAL.
----End

1.8 Interface and Link Data Reconfigurations

This section describes how to reconfigure eNodeB interface and link data in typical
scenarios.

1.8.1 Adding an MME Connection

This section describes how to add an MME connection.

Prerequisites
● Data has been configured for the MME to be added.
● Data has been configured for the transport network between the eNodeB and
the new MME.

Context
This section describes only operations on the eNodeB side after the MME is added.
The MME is an NE on the core network side. The operations and information

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 475

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

related to the MME are described in the associated MME manual. For example,
whether an MME needs to be added, information about the hardware, software,
license files, and security certificates required on the core network side as well as
operations such as hardware and software installation, license loading, and
security certificate activation.

1.8.1.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adding an MME connection.

Application Scenario
● The MME cannot meet service requirements.
● The transmission networking mode for the eNodeB is changed to MME
pooling.

Reconfiguration Impact
No impact

Reconfiguration Scheme
Determine the reconfiguration scheme for adding an MME connection according
to the following table.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-143 Scheme options

If… Then...

The new MME connection requires a Add a device IP address.

new device IP address

No route is available between the Add a route from the eNodeB to the
eNodeB and the new MME new MME and the corresponding
VLANMAP MO.

NOTE

The network segment on which the eNodeB is located can be calculated based on the values of
Mask and IP Address of the corresponding Ethernet port.

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 476

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-144 Scheme options

If… Then...

The new MME connection requires a Add a device IPv4/IPv6 address.

new device IPv4/IPv6 address

No route is available between the Add a route from the eNodeB to the
eNodeB and the new MME new MME and the corresponding
VLANMAP MO.

No IPv6 route is available between the Add an IPv6 route between the
eNodeB and the new MME eNodeB and the new MME.

NOTE

The network segment on which the eNodeB is located can be calculated based on the values of
Mask and IP Address of the corresponding Ethernet port.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 477

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-82 Procedure for adding an MME connection in endpoint mode (IPv4)

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 478

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-83 Procedure for adding an MME connection in endpoint mode (IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 479

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-84 Procedure for adding an MME connection in endpoint mode (IPv6)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 480

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Figure 1-85 Procedure for adding an MME connection in link mode

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 481

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-86 Procedure for adding an MME connection in link mode (IPv4)

Topology Change
Figure 1-87 shows the topologies before and after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 482

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-87 Topologies before and after the reconfiguration

1.8.1.2 Engineering Preparation

This section describes the engineering preparation for adding an MME connection,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-145 and Table 1-147 describe the information to be collected for data
preparation.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-145 Information to be collected (endpoint mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the MME

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the MME

MME signaling IP Indicates the peer IP address of an SCTP link, which is

address an S1 signaling link automatically set up by the eNodeB.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 483

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

MME port number Peer port number of the SCTP link automatically
established by the eNodeB

Information about ID of the endpoint group to which the SCTP peer is to

the endpoint group be added

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Table 1-146 Information to be collected (endpoint mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask (IPv4)/prefix length (IPv6), and route
eNodeB to the MME priority.

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN as well as the INTERFACE MO where the VLAN is
route from the to be configured.
eNodeB to the MME

MME signaling IP Indicates the peer IP address of an SCTP link, which is

address an S1 signaling link automatically set up by the eNodeB.

MME port number Peer port number of the SCTP link automatically
established by the eNodeB

Information about ID of the endpoint group to which the SCTP peer is to

the endpoint group be added

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Table 1-147 Information to be collected (link mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the MME

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 484

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the MME

MME signaling IP Indicates the peer IP address of an SCTP link, which is

address an S1 signaling link set up by the eNodeB.

MME port number Peer port number of the SCTP link automatically
established by the eNodeB

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-148 Information to be collected (link mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the MME

Information about Includes the INTERFACE MO for the VLAN and the
the VLAN for the VLAN ID
route from the
eNodeB to the MME

MME signaling IP Indicates the peer IP address of an SCTP link, which is

address an S1 signaling link set up by the eNodeB.

MME port number Peer port number of the SCTP link automatically
established by the eNodeB

Hardware Preparation
Prepare the hardware listed in Table 1-149.

Table 1-149 Hardware to be prepared

Hardware Description

Cables used to Cables connecting the eNodeB to the closest router

connect the eNodeB between the eNodeB and the MME to be added. The
and a router cables can be Ethernet cables or optical fibers,
depending on the peer router.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 485

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-150 Data preparation for adding an MME connection in endpoint mode

SN Ope MO Configuration Reference

ratio
n

1 Add IPv4: DEVIP For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add SCTPHOST For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
3 Add EPGROUP Description.
4 Modi EPGROUP
fy

5 Add IPv4: IPRT/SRCIPRTa For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
6 Add IPv4: VLANMAP Description.

7 Add SCTPPEER For details, see LTE and NR NSA S1 and

X2 Self-Management Feature Parameter
8 Modi EPGROUP Description.
fy

9 Add S1

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

New Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 486

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-151 Data preparation for adding an MME connection in endpoint mode

SN Ope MO Configuration Reference

ratio
n

1 Add INTERFACE For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPv4: (optional) For details, see LTE and NR NSA S1 and
VLANMAP X2 Self-Management Feature Parameter
IPv6: N/A Description.

3 Add IPv4: IPADDR4

IPv6: IPADDR6

4 Add IPv4: IPROUTE4/

SRCIPROUTE4a
IPv6: IPROUTE6

5 Add SCTPHOST For details, see LTE and NR NSA S1 and

X2 Self-Management Feature Parameter
6 Add EPGROUP Description.
7 Modi EPGROUP
fy

8 Add SCTPPEER

9 Modi EPGROUP
fy

10 Add S1

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-152 Data preparation for adding an MME connection (link mode)

SN Ope MO Configuration Reference

ratio
n

1 Add DEVIP For details, see IP eRAN Engineering

Guide Feature Parameter Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 487

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

2 Add SCTPLNK For details, see LTE and NR NSA S1 and

X2 Self-Management Feature Parameter
3 Add CPBEARER Description.
4 Modi S1Interface
fy

5 Add IPRT/SRCIPRTa For details, see IP eRAN Engineering

Guide Feature Parameter Description.
6 Add VLANMAP

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Table 1-153 Data preparation for adding an MME connection (link mode)

SN Ope MO Configuration Reference

ratio
n

1 Add INTERFACE For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add (Optional) VLANMAP

3 Add IPADDR4

4 Add IPROUTE4/
SRCIPROUTE4a

5 Add SCTPHOST For details, see LTE and NR NSA S1 and

X2 Self-Management Feature Parameter
6 Add CPBEARER Description.
7 Modi S1
fy

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 488

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario-specific template being "Adding an MME Connection
(Endpoint)" or Adding an MME Connection (Link)): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, an IP route is added.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid long-term service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. Example: CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;

NOTE

If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
● Endpoint mode
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address used for communicating with the new MME*/
ADD DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="135.25.221.110", MASK="255.255.255.0";
/*Adding an SCTP host*/
ADD SCTPHOST:SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="135.25.221.110",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=2912, SCTPTEMPLATEID=0;
/*Adding an endpoint group with the ID of 1*/
ADD EPGROUP: EPGROUPID=1;
/*Adding the new SCTP host to the endpoint group*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 489

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD SCTPHOST2EPGRP: EPGROUPID=1, SCTPHOSTID=0;

/*Adding an IP route from the eNodeB to the MME*/
ADD IPRT:RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="192.168.3.3", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.221.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.221.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=
101,SETPRIO=DISABLE;
/*Adding an SCTP peer*/
ADD SCTPPEER: SCTPPEERID=0, IPVERSION=IPv4, SIGIP1V4="140.3.3.3", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=2918, USERLABEL="MME-192.168.3.3";
/*Adding the new SCTP peer to the endpoint group*/
ADD SCTPPEER2EPGRP: EPGROUPID=1, SCTPPEERID=0;
/*Adding an S1 object*/
ADD S1:S1ID=1,CNOPERATORID=0,EPGROUPCFGFLAG=CP_CFG,CPEPGROUPID=1;
New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Setting Ethernet port 0*/
SET ETHPORT:CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD
VLANMAP:NEXTHOPIP="192.168.221.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=
101,SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;
/*Adding an IPv4 address used for communicating with the new MME*/
ADD IPADDR4:ITFID=0, IP="135.25.221.110", MASK="255.255.255.0";
/*Adding an SCTP host*/
ADD SCTPHOST:SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="135.25.221.110",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=2912, SCTPTEMPLATEID=0;
/*Adding an endpoint group with the ID of 1*/
ADD EPGROUP:EPGROUPID=1;
/*Adding the new SCTP host to the endpoint group*/
ADD SCTPHOST2EPGRP:EPGROUPID=1, SCTPHOSTID=0;
/*Adding an IP route from the eNodeB to the MME*/
ADD IPROUTE4:RTIDX=0, DSTIP="192.168.3.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.221.1", MTUSWITCH=OFF;
/*Adding an SCTP peer*/
ADD SCTPPEER:SCTPPEERID=0, IPVERSION=IPv4, SIGIP1V4="140.3.3.3", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=2918, USERLABEL="MME-192.168.3.3";
/*Adding the new SCTP peer to the endpoint group*/
ADD SCTPPEER2EPGRP:EPGROUPID=1, SCTPPEERID=0;
/*Adding an S1 object*/
ADD S1:S1ID=1,CNOPERATORID=0,EPGROUPCFGFLAG=CP_CFG,CPEPGROUPID=1;
● Link mode
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address used for communicating with the new MME*/
ADD DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="135.25.221.110", MASK="255.255.255.0";
/*Adding an SCTP link*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 490

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD SCTPLNK: SCTPNO=1, SN=7, LOCIP="135.25.221.110", SECLOCIP="0.0.0.0", LOCPORT=2912,

PEERIP="140.3.3.3", SECPEERIP="0.0.0.0", PEERPORT=2918, AUTOSWITCH=ENABLE;
/*Adding a CP bearer*/
ADD CPBEARER: CPBEARID=1, BEARTYPE=SCTP, LINKNO=1, FLAG=MASTER;
/*Adding an S1 interface*/
ADD S1INTERFACE: S1InterfaceId=1, S1CpBearerId=1, CnOperatorId=0;
/*Adding an IP route from the eNodeB to the MME*/
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="192.168.3.3", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.221.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD VLANMAP:
NEXTHOPIP="192.168.221.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SETPRI
O=DISABLE;

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Setting Ethernet port 0*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD VLANMAP: NEXTHOPIP="192.168.221.1", MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
VLANID=101, SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;
/*Adding an IPv4 address used for communicating with the new MME*/
ADD IPADDR4: ITFID=0, IP="135.25.221.110", MASK="255.255.255.0";
/*Adding an IP route from the eNodeB to the MME*/
ADD IPROUTE4: RTIDX=0, DSTIP="192.168.3.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.221.1", MTUSWITCH=OFF;
/*Adding an SCTP link*/
ADD SCTPLNK: SCTPNO=1, LOCIP="135.25.221.110", SECLOCIP="0.0.0.0", LOCPORT=2912,
PEERIP="140.3.3.3", SECPEERIP="0.0.0.0", PEERPORT=2918, AUTOSWITCH=ENABLE;
/*Adding a CP bearer*/
ADD CPBEARER: CPBEARID=1, BEARTYPE=SCTP, LINKNO=1, FLAG=MASTER;
/*Adding an S1 interface*/
ADD S1INTERFACE: S1InterfaceId=1, S1CpBearerId=1, CnOperatorId=0;

1.8.1.3 Engineering Implementation

This section describes the engineering implementation for adding an MME
connection, including prerequisites, context, and procedure.

Prerequisites
Information for adding an MME connection has been collected, configuration data
is ready, and the license file is available in the save path on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 491

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
● Local Operations

Connect the eNodeB to a router. The router must be the closest one between
the eNodeB and the MME to be added.
● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the LST GLOBALPROCSWITCH command to query the values of
the options of The Switch of S1-MME Configuration by SON
parameter.
○ If the values of the options are Off, skip this step.
○ If the values of the options are On, run the MOD
GLOBALPROCSWITCH command with the options of The
Switch of S1-MME Configuration by SON deselected. Example:
MOD GLOBALPROCSWITCH:
S1MMESonSwitch=S1MMESonSetupSwitch-0&S1MMESonDel
eteSwitch-0;
iii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iv. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
v. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
vi. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
vii. Restore the values of the switches changed in ii.
– Using MML commands:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 492

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.8.1.4 Engineering Verification

This section describes how to verify the reconfiguration for adding an MME
connection.

Procedure
Step 1 Verify that no new alarms are reported.
If a new alarm is reported, clear the alarm according to the instructions in 3900 &
5900 Series Base Station Alarm Reference.
Step 2 Run the LST SCTPLNK command. Check whether there is an SCTP link between
the eNodeB and the new MME. If the peer IP address of the SCTP link is the
signaling IP address of the new MME, an SCTP link exists between the eNodeB
and the new MME.
If the peer IP address of the SCTP link is not the signaling IP address of the new
MME, perform the following steps.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 493

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The reconfiguration is
performed on the
MAE-Deployment
View the modified configuration data file and check
whether the peer IP address is the same as the
signaling IP address of the new MME:
● If they are different, modify the configuration data
file again and import it into the system. Then
perform the operations in Engineering
Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the
data is imported into the system or delivered to the
base station. In this situation, contact Huawei
technical support or dial the Huawei technical
support hotline.

The reconfiguration is
performed by using
MML commands
Check whether the peer IP address in the script is the
same as the signaling IP address of the new MME:
● If they are different, modify the parameter settings
in the script. Then run the MOD SCTPPEER
command to change the peer IP address to the
correct value.
● If they are the same, contact Huawei technical
support or dial the Huawei technical support
hotline.

Step 3 Run the DSP SCTPLNK command to check whether the value of SCTP Link Status
for the link between the eNodeB and the new MME is Up.
If the value of SCTP Link Status is Down, perform the following steps:
1. Perform a ping operation on the route from the device IP address of the
eNodeB to the signaling IP address of the MME (old model)/IPv4 address
(new model)/IPv6 address (new model).
– If the ping operation fails, go to Step 3.2.
– If the ping operation is successful, go to Step 3.3.
2. Check whether the SCTP link configurations are correct. Specifically, check
whether the IP route from the eNodeB to the MME is correct and whether the
port mode and port rate of the Ethernet port on the eNodeB are the same as
those on the peer device.
– If the configuration is incorrect, modify the configuration.
– If the configuration is correct, go to Step 3.4.
3. Check whether the value of Peer SCTP Port No. for the SCTP link is the same
as the SCTP port number of the new MME.
– If they are different, modify the configurations.
– If they are the same, go to Step 3.4.
4. Check the configurations of the device between the eNodeB and MME.
– If the configurations or cable connections are incorrect, modify the
configurations or cable connections.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 494

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– If the configurations or cable connections are correct, contact Huawei

technical support or dial the Huawei technical support hotline.
Step 4 Enable a UE to access the network. Check whether the access is successful.
If the UE fails to access the network, check the cell status.
● If the cell fails to be established, the eNodeB reports an alarm. If this
happens, clear the alarm according to the instructions in 3900 & 5900 Series
Base Station Alarm Reference
● If the cell is successfully established, contact Huawei technical support or dial
the Huawei technical support hotline.

----End

1.8.1.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 495

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the physical connections.
Step 4 Verify that engineering rollback is successful according to instructions in 1.8.1.4
Engineering Verification.

----End

1.8.2 Adding an S-GW Connection

This section describes how to add an S-GW connection.

Prerequisites
● Data has been configured for the new S-GW.
● Data has been configured for the transport network between the eNodeB and
the new S-GW.

Context
This section describes only operations on the eNodeB side after the S-GW is
added. The S-GW is an NE on the core network side. The operations and
information related to the S-GW are described in the associated S-GW manual.
For example, whether an S-GW needs to be added, information about the
hardware, software, license files, and security certificates required on the core
network side as well as operations such as hardware and software installation,
license loading, and security certificate activation.

1.8.2.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adding an S-GW connection.

Application Scenario
The existing S-GW cannot meet the service requirements.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 496

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Impact
No impact

Reconfiguration Scheme
Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-154 Scheme options

If… Then...

The new S-GW connection requires a Add a device IP address.

new device IP address

No route is available between the Add a route from the eNodeB to the
eNodeB and the new S-GW new S-GW and the corresponding
VLANMAP MO.

NOTE

The network segment on which the eNodeB is located can be calculated based on the values of
Mask and IP Address of the corresponding Ethernet port.

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-155 Scheme options

If… Then...

The new S-GW connection requires a Add an IPv4/IPv6 address.

new IPv4/IPv6 address

No route is available between the Add a route from the eNodeB to the
eNodeB and the new S-GW new S-GW and an interface VLAN or
the corresponding VLANMAP MO.

NOTE

The network segment on which the eNodeB is located can be calculated based on the values of
Mask and IP Address of the corresponding Ethernet port.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 497

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-88 Procedure for adding an S-GW connection in endpoint mode (IPv4)

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 498

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-89 Procedure for adding an S-GW connection in endpoint mode (IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 499

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-90 Procedure for adding an S-GW connection in endpoint mode (IPv6)

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 500

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-91 Procedure for adding an S-GW connection in link mode

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 501

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-92 Procedure for adding an S-GW connection in link mode

Topology Change
Figure 1-93 shows the topologies before and after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 502

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-93 Topologies before and after the reconfiguration

1.8.2.2 Engineering Preparation

This section describes the engineering preparation for adding an S-GW connection,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-156 and Table 1-158 describe the information to be collected for data
preparation.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-156 Information to be collected (endpoint mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the S-GW

Information about Includes the interface VLAN or the next-hop IP address

the VLAN for the of the VLAN and the VLAN ID.
route from the
eNodeB to the S-GW

Service IP address of Peer IP address of an S1 service link automatically set

the S-GW up by the eNodeB

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 503

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Device IP address of Device IP address used for communication with external

the eNodeB devices

Information about ID of the endpoint group to which the user-plane peer is

the endpoint group to be added

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Table 1-157 Information to be collected (endpoint mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask (IPv4)/prefix length (IPv6), and route
eNodeB to the S-GW priority.

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the S-GW

Service IP address of Peer IP address of an S1 service link automatically set

the S-GW up by the eNodeB

eNodeB IPv4 address IPv4 address used for communication with external
devices

Information about ID of the endpoint group to which the user-plane peer is

the endpoint group to be added

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Table 1-158 Information to be collected (link mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the S-GW

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 504

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the S-GW

Service IP address of Peer IP address of an S1 service link set up by the

the S-GW eNodeB

Device IP address of Device IP address used for communication with external

the eNodeB devices

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Table 1-159 Information to be collected (link mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the S-GW

Information about Includes the interface VLAN or the next-hop IP address

the VLAN for the of the VLAN and the VLAN ID.
route from the
eNodeB to the S-GW

Service IP address of Peer IP address of an S1 service link set up by the

the S-GW eNodeB

IPv4/IPv6 address of IPv4/IPv6 address used for communication with external

the eNodeB devices

Hardware Preparation
Prepare the hardware listed in Table 1-160.

Table 1-160 Hardware to be prepared

Hardware Description

Cables used to connect the eNodeB
and a router
Cables connecting the eNodeB to the
closest router between the eNodeB
and the S-GW to be added. The cables
can be Ethernet cables or optical
fibers, depending on the peer router.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 505

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Determine the data to be prepared based on the reconfiguration procedure. The
following table lists the data to be prepared.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Table 1-161 Data preparation for adding an S-GW connection in endpoint mode
SN Ope MO Configuration Reference
ratio
n

1 Add IPv4: DEVIP For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add USERPLANEHOST For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
3 Add EPGROUP Description.
4 Modi EPGROUP
fy

5 Add IPv4: IPRT/SRCIPRTa For details, see IP eRAN Engineering

Guide Feature Parameter Description.
6 Add IPv4: VLANMAP

7 Add USERPLANEPEER For details, see LTE and NR NSA S1 and

X2 Self-Management Feature Parameter
8 Modi EPGROUP Description.
fy

9 Add S1

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 506

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-162 Data preparation for adding an S-GW connection in endpoint mode
SN Ope MO Configuration Reference
ratio
n

1 Add INTERFACE For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPv4: (optional)
VLANMAP
IPv6: N/A

3 Add IPv4: IPADDR4

IPv6: IPADDR6

4 Add IPv4: IPROUTE4/

SRCIPROUTE4a
IPv6: IPROUTE6

5 Add USERPLANEHOST For details, see LTE and NR NSA S1 and

X2 Self-Management Feature Parameter
6 Add EPGROUP Description.
7 Modi EPGROUP
fy

8 Add USERPLANEPEER

9 Modi EPGROUP
fy

10 Add S1

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Table 1-163 Data preparation for adding an S-GW connection in link mode
SN Ope MO Configuration Reference
ratio
n

1 Add DEVIP For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPPATH For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
3 Add eNodeBPath Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 507

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

4 Add IPRT/SRCIPRTa For details, see IP eRAN Engineering

Guide Feature Parameter Description.
5 Add VLANMAP

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-164 Data preparation for adding an S-GW connection in link mode

SN Oper MO Configuration Reference

ation

1 Add INTERFACE For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add (Optional) VLANMAP

3 Add IPADDR4

4 Add IPROUTE4/ For details, see LTE and NR NSA S1

SRCIPROUTE4a and X2 Self-Management Feature
Parameter Description.
5 Add IPPATH

6 Add eNodeBPath

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 508

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Use the batch reconfiguration mode of the MAE-Deployment (with the name
of the scenario-specific template being "Adding an S-GW Connection
(Endpoint)" or "Adding an S-GW Connection (Link)"): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands. Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, an IP route is added.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid long-term service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. Example: CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;

NOTE

If the license file needs to be updated, the license file in use must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
● Endpoint mode
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address used for communicating with the new S-GW*/
ADD DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.223.110", MASK="255.255.255.0";
/*Adding a user-plane host*/
ADD USERPLANEHOST:UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.223.110",
IPSECSWITCH=DISABLE;
/*Adding an endpoint group with the ID of 1*/
ADD EPGROUP:EPGROUPID=1;
/*Adding the new user-plane host to the endpoint group*/
ADD UPHOST2EPGRP:EPGROUPID=1, UPHOSTID=0;
/*Adding an IP route from the eNodeB to the S-GW*/
ADD IPRT:RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="192.168.3.3", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.223.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.223.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=
101,SETPRIO=DISABLE;
/*Adding a user-plane peer*/
ADD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, PEERIPV4="192.168.3.3",
IPSECSWITCH=DISABLE, USERLABEL="SGW:192.168.3.3";
/*Adding the new user-plane peer to the endpoint group*/
ADD UPPEER2EPGRP:EPGROUPID=1, UPPEERID=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 509

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Adding an S1 object*/
ADD S1:S1ID=1,CNOPERATORID=0,EPGROUPCFGFLAG=UP_CFG,UPEPGROUPID=1;

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Setting Ethernet port 0*/
SET ETHPORT:CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD
VLANMAP:NEXTHOPIP="192.168.223.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=
101,SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;
/*Adding a device IP address used for communicating with the new S-GW*/
ADD IPADDR4:ITFID=0, IP="192.168.223.110", MASK="255.255.255.0";
/*Adding an IP route from the eNodeB to the S-GW*/
ADD IPRT:RTIDX=0, DSTIP="192.168.3.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.223.1", MTUSWITCH=OFF;
/*Adding a user-plane host*/
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.223.110",
IPSECSWITCH=DISABLE;
/*Adding an endpoint group with the ID of 1*/
ADD EPGROUP:EPGROUPID=1;
/*Adding the new user-plane host to the endpoint group*/
ADD UPHOST2EPGRP:EPGROUPID=1, UPHOSTID=0;
/*Adding a user-plane peer*/
ADD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, PEERIPV4="192.168.3.3",
IPSECSWITCH=DISABLE, USERLABEL="SGW:192.168.3.3";
/*Adding the new user-plane peer to the endpoint group*/
ADD UPPEER2EPGRP:EPGROUPID=1, UPPEERID=0;
/*Adding an S1 object*/
ADD S1:S1ID=1,CNOPERATORID=0,EPGROUPCFGFLAG=UP_CFG,UPEPGROUPID=1;

● Link mode
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address used for communicating with the new S-GW*/
ADD DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.223.110", MASK="255.255.255.0";
/*Adding an IP path*/
ADD IPPATH:PATHID=1, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE,
LOCALIP="192.168.223.110", PEERIP="192.168.3.3", PATHTYPE=ANY;
/*Adding the application type of the IP path*/
ADD ENODEBPATH: IpPathId=1, AppType=S1;
/*Adding an IP route from the eNodeB to the S-GW*/
ADD IPRT:RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="192.168.3.3", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.223.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.223.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=
101,SETPRIO=DISABLE;

New Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 510

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

The Transmission Configuration Mode parameter in the GTRANSPARA MO is

set to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Setting Ethernet port 0*/
SET ETHPORT:CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD
VLANMAP:NEXTHOPIP="192.168.223.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=
101,SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;
/*Adding a device IP address used for communicating with the new S-GW*/
ADD IPADDR4:ITFID=0, IP="192.168.223.110", MASK="255.255.255.0";
/*Adding an IP route from the eNodeB to the S-GW*/
ADD IPROUTE4:RTIDX=0, DSTIP="192.168.3.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.223.1", MTUSWITCH=OFF;
/*Adding an IP path*/
ADD IPPATH:PATHID=1, TRANSCFGMODE=NEW, JNIPRSCGRP=DISABLE, BPT=ETH, ORTID=1,
LOCALIP="192.168.223.110", PEERIP="192.168.3.3", PATHTYPE=ANY;
/*Adding the application type of the IP path*/
ADD ENODEBPATH: IpPathId=1, AppType=S1;

1.8.2.3 Engineering Implementation

This section describes the engineering implementation for adding an S-GW
connection, including prerequisites, context, and procedure.

Prerequisites
Information for adding an S-GW connection has been collected, configuration
data is ready, and the license file is available in the save path on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
Connect the eNodeB to the closest router between the eNodeB and the S-GW
to be added.
● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 511

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the LST GTRANSPARA command to query the value of
Endpoint Object Auto-configure Switch.
○ If the value is Disable, skip this step.
○ If the value is Enable, run the SET GTRANSPARA command with
Endpoint Object Auto-configure Switch set to DISABLE.
Example: SET GTRANSPARA: EPOBJAUTOCFGSW=DISABLE;
iii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iv. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
v. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
vi. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
vii. Restore the values of the switches changed in ii.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 512

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.8.2.4 Engineering Verification

This section describes how to verify the reconfiguration for adding an S-GW
connection.

Procedure
Step 1 Verify that ALM-25952 User Plane Path Fault is not reported.
If ALM-25952 User Plane Path Fault is reported, clear the alarm according to the
instructions in 3900 & 5900 Series Base Station Alarm Reference.
Step 2 Run the LST USERPLANEPEER command to verify that the value of User Plane
Peer ID of one IP path is the same as the service IP address of the new S-GW.
If they are different, check whether the transmission configuration is correct.
● If it is incorrect, modify it.
● If it is correct, contact Huawei technical support or dial the Huawei technical
support hotline.
Step 3 Enable a UE to access the network. Check whether the access is successful.
If the UE fails to access the network, check the cell status.
● If the cell fails to be established, the eNodeB reports an alarm. If this
happens, clear the alarm according to the instructions in 3900 & 5900 Series
Base Station Alarm Reference
● If the cell is successfully established, contact Huawei technical support or dial
the Huawei technical support hotline.

----End

1.8.2.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 513

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands:

– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful according to instructions in 1.8.2.4

Engineering Verification.

----End

1.8.3 Replacing an MME

This section describes how to replace an MME.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 514

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Prerequisites
Data for the transport network between the eNodeB and the new MME has been
configured.

1.8.3.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for replacing an MME.

Application Scenario
An MME needs to be replaced when the EPC topology changes.

Reconfiguration Impact
The eNodeB disconnects from the old MME during MME replacement before a
connection to the new MME is set up. Therefore, services carried on the old S1 link
are interrupted.

Reconfiguration Scheme
Determine the reconfiguration scheme for replacing an MME according to the
following table.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-165 Scheme options

If… Then...

During the The device IP Add a device IP address on the eNodeB.

addition of a address of the
new MME eNodeB cannot
connection meet
requirements
when both old
and new MMEs
exist

No route is Add a route from the eNodeB to the new

available between MME.
the eNodeB and
the new MME

During the A new IP route is Remove the route from the eNodeB to the
removal of added when a old MME.
the old MME new MME
connection connection is
added

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 515

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If… Then...

A new device IP Remove the device IP address

address is added corresponding to the old MME.
when a new MME
connection is
added

Note: The network segment on which the eNodeB is located can be calculated
based on the values of Mask and IP Address of the corresponding Ethernet
port.

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-166 Scheme options

If… Then...

During the The IPv4/IPv6 Add an IPv4/IPv6 address on the eNodeB.

addition of a address of the
new MME eNodeB cannot
connection meet requirements
when both old and
new MMEs exist

No route is Add a route from the eNodeB to the new

available between MME.
the eNodeB and
the new MME

During the A new IPv4/IPv6 Remove the route from the eNodeB to
removal of route is added the old MME.
the old MME when a new MME
connection connection is
added

A new IPv4/IPv6 Remove the IPv4/IPv6 address

address is added corresponding to the old MME.
when a new MME
connection is
added

Note: The network segment on which the eNodeB is located can be calculated
based on the values of Mask (IPv4)/Prefix Length (IPv6) and IP Address
(IPv4)/IPv6 Address (IPv6) of the corresponding Ethernet port.

Old Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 516

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Figure 1-94 Procedure for replacing an MME in endpoint mode (IPv4)

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 517

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-95 Procedure for replacing an MME in endpoint mode (IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 518

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-96 Procedure for replacing an MME in endpoint mode (IPv6)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 519

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 520

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-97 Procedure for replacing an MME in link mode

New Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 521

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 522

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-98 Procedure for replacing an MME in link mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 523

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
N/A

1.8.3.2 Engineering Preparation

This section describes the engineering preparation for replacing an MME, including
information collection and preparation of hardware, software, license files, security
certificates, and data. It also describes the data preparation mode and provides
MML configuration script examples.

Information Collection
Table 1-167 and Table 1-169 describe the information to be collected for data
preparation.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-167 Information to be collected (endpoint mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the MME

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the MME

MME signaling IP Peer IP address of an SCTP link, which is an S1 signaling

address link automatically set up by the eNodeB.

MME port number Peer port number of the SCTP link automatically
established by the eNodeB

Device IP address of IP address used for communication with external

the eNodeB devices

Control plane Includes:

information of the S1 ● SCTP host
interface
● SCTP peer

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 524

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-168 Information to be collected (endpoint mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask (IPv4)/prefix length (IPv6), and route
eNodeB to the MME priority.

Information about Includes the interface VLAN or the next-hop IP address

the VLAN for the of the VLAN and the VLAN ID.
route from the
eNodeB to the MME

MME signaling IP Indicates the peer IP address of an SCTP link, which is

address an S1 signaling link automatically set up by the eNodeB.

MME port number Peer port number of the SCTP link automatically
established by the eNodeB

Device IPv4 address IPv4 address used for communication with external
of the eNodeB devices

Control plane Includes:

information of the S1 ● SCTP host
interface
● SCTP peer

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Table 1-169 Information to be collected (link mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the MME

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the MME

MME signaling IP Indicates the peer IP address of an SCTP link, which is

address an S1 signaling link set up by the eNodeB.

MME port number Peer port number of the SCTP link automatically
established by the eNodeB

Device IP address of IP address used for communication with external

the eNodeB devices

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 525

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Control plane Includes:

information of the S1 ● SCTP link
interface
● CP bearer
● S1 interface

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Table 1-170 Information to be collected (link mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the MME

Information about Includes the interface VLAN or the next-hop IP address

the VLAN for the of the VLAN and the VLAN ID.
route from the
eNodeB to the MME

MME signaling IP Indicates the peer IP address of an SCTP link, which is

address an S1 signaling link set up by the eNodeB.

MME port number Peer port number of the SCTP link automatically
established by the eNodeB

IPv4/IPv6 address of IPv4/IPv6 address used for communication with external

the eNodeB devices

Control plane Includes:

information of the S1 ● SCTP link
interface
● CP bearer
● S1 interface

Hardware Preparation
Prepare the hardware listed in Table 1-171.

Table 1-171 Hardware to be prepared

Hardware Description

MME -

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 526

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedures, determine the data you need to prepare.
Data preparations for replacing an MME involve the preparation for adding a new
MME connection and that for removing the old MME connection.
NOTE

This document does not describe how to configure the new MME. For details, see MME-related
documentation.
● For data preparation for adding a new MME connection, see Adding an MME
Connection > Engineering Preparation > Table 1-150 or Table 1-152.
● For data preparation for removing the old MME connection, see the following
table.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-172 Data preparation for removing an old MME connection in endpoint
mode

SN Ope MO Configuration Reference

ratio
n

1 Dele IPv4: VLANMAP If a new IP route is added when a new

te MME connection is added, remove the
IP route from the eNodeB to the old
2 Dele IPv4: IPRT MME and the corresponding VLANMAP
te MO.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
3 Dele S1 If a new device IP address is added
te when a new MME connection is added,
remove the old S1 object.
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 527

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

4 Modi EPGROUP Remove the SCTP peer corresponding to

fy the old MME.

5 Dele SCTPPEER For details, see LTE and NR NSA S1 and

te X2 Self-Management Feature Parameter
Description.

6 Modi EPGROUP If a new device IP address is added

fy when a new MME connection is added,
remove the SCTP host corresponding to
7 Dele SCTPHOST the old MME.
te
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

8 Dele EPGROUP If a new device IP address is added

te when a new MME connection is added,
remove the endpoint group
corresponding to the old MME.
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

9 Dele IPv4: DEVIP If a new device IP address is added

te when a new MME connection is added,
remove the device IP address
corresponding to the old MME.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-173 Data preparation for removing an old MME connection in endpoint
mode

SN Ope MO Configuration Reference

ratio
n

1 Dele IPv4: VLANMAP If a new IP route is added when a new

te IPv6: N/A MME connection is added, remove the
IP route from the eNodeB to the old
MME and the corresponding VLANMAP
MO.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 528

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

2 Dele IPv4: IPROUTE4 For details, see IP eRAN Engineering

te IPv6: IPROUTE6 Guide Feature Parameter Description.

3 Dele S1 If a new device IP address is added

te when a new MME connection is added,
remove the old S1 object.
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

4 Modi EPGROUP Remove the SCTP peer corresponding to

fy the old MME.

5 Dele SCTPPEER For details, see LTE and NR NSA S1 and

te X2 Self-Management Feature Parameter
Description.

6 Modi EPGROUP If a new device IP address is added

fy when a new MME connection is added,
remove the SCTP host corresponding to
7 Dele SCTPHOST the old MME.
te
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

8 Dele EPGROUP If a new device IP address is added

te when a new MME connection is added,
remove the endpoint group
corresponding to the old MME.
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

9 Dele IPv4: IPADDR4 If a new IPv4/IPv6 address is added

te IPv6: IPADDR6 when a new MME connection is added,
remove the IPv4/IPv6 address and the
10 Dele INTERFACE INTERFACE MO corresponding to the
te old MME.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 529

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch configuration mode of the MAE-Deployment: For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
NOTE

The following MAE-Deployment operations are performed to prepare script files for later
engineering implementation. When replacing an MME, you need to export two incremental
scripts based on the following descriptions.
● Export the incremental script for adding an MME connection by following Adding an
MME Connection > Engineering Preparation > Table 1-150 or Table 1-152. (The
name of the scenario-specific template is "Adding an MME Connection".)
● Export the incremental script for removing the old MME connection by referring to
Table 1-172 or Table 1-173 in this section. (The name of the scenario-specific template
is "Removing the old MME Connection".)
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The following provides the scripts for adding an MME connection, checking the S1
interface status, and removing the old MME connection.

If OMCH parameters are modified by mistake, the OMCH may be disconnected

and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";

1. Add an MME connection. For the script, see Adding an MME Connection
(Endpoint Mode) or Adding an MME Connection (Link Mode) >
Engineering Preparation > MML Configuration Script Example.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 530

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

2. Check whether the S1 interface works properly.

DSP S1INTERFACE:;

3. Remove the old MME connection.

– Endpoint mode
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA
MO is set to OLD.
/*Removing the next-hop VLAN mapping relationship for the IP route between the eNodeB and
the old MME (the next-hop IP address for the old VLAN mapping is 192.168.221.2)*/
RMV VLANMAP:NEXTHOPIP="192.168.221.2", MASK="255.255.255.0";
/*Removing the IP route from the eNodeB to the old MME*/
RMV IPRT:RTIDX=0;
/*Removing the old S1 MO with the S1 ID of 0*/
RMV S1:S1Id=0;
/*Removing the SCTP peer corresponding to the old MME from the endpoint group*/
RMV SCTPPEER2EPGRP: EPGROUPID=0, SCTPPEERID=0;
/*Removing the SCTP peer corresponding to the old MME*/
RMV SCTPPEER:SCTPPEERID=0;
/*Removing the SCTP host corresponding to the old MME from the endpoint group*/
RMV SCTPHOST2EPGRP:EPGROUPID=0, SCTPHOSTID=0;
/*Removing the SCTP host corresponding to the old MME*/
RMV SCTPHOST:SCTPHOSTID=0;
/*Removing the endpoint group corresponding to the old MME*/
RMV EPGROUP:EPGROUPID=0;
/*Removing the device IP address corresponding to the old MME*/
RMV DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.3.109";

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA
MO is set to NEW.
/*Removing the next-hop VLAN mapping relationship for the IP route between the eNodeB and
the old MME (the next-hop IP address for the old VLAN mapping is 192.168.221.2)*/
RMV VLANMAP:NEXTHOPIP="192.168.221.2", MASK="255.255.255.0";
/*Removing the IP route between the eNodeB and the old MME (the next-hop IP address of the
original route is 192.168.221.2 and the route index is 0)*/
RMV IPROUTE4:RTIDX=0;
/*Removing the old S1 MO with the S1 ID of 0*/
RMV S1:S1Id=0;
/*Removing the SCTP peer corresponding to the old MME from the endpoint group*/
RMV SCTPPEER2EPGRP: EPGROUPID=0, SCTPPEERID=0;
/*Removing the SCTP peer corresponding to the old MME*/
RMV SCTPPEER:SCTPPEERID=0;
/*Removing the SCTP host corresponding to the old MME from the endpoint group*/
RMV SCTPHOST2EPGRP:EPGROUPID=0, SCTPHOSTID=0;
/*Removing the SCTP host corresponding to the old MME*/
RMV SCTPHOST:SCTPHOSTID=0;
/*Removing the endpoint group corresponding to the old MME*/
RMV EPGROUP:EPGROUPID=0;
/*Removing the IPv4 address corresponding to the old MME*/
RMV IPADDR4:ITFID=0, IP="192.168.3.109";
/*Removing the interface for the IPv4 address corresponding to the old MME*/
RMV INTERFACE:ITFID=1;

– Link mode
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA
MO is set to OLD.
/*Removing the next-hop VLAN mapping relationship for the IP route between the eNodeB and
the old MME (the next-hop IP address for the old VLAN mapping is 192.168.221.2)*/
RMV VLANMAP:NEXTHOPIP="192.168.221.2", MASK="255.255.255.0";
/*Removing the IP route from the eNodeB to the old MME*/
RMV IPRT:RTIDX=0;
/*Removing the old S1Interface MO with the S1 Interface ID of 0*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 531

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

RMV S1INTERFACE:S1InterfaceId=0;
/*Removing the old CP bearer with the CP Bear No. of 0*/
RMV CPBEARER:CPBEARID=0, FLAG=MASTER;
/*Removing the SCTP link corresponding to the old MME*/
RMV SCTPLNK:SCTPNO=0;
/*Removing the device IP address corresponding to the old MME*/
RMV DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.3.109";

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA
MO is set to NEW.
/*Removing the next-hop VLAN mapping relationship for the IP route between the eNodeB and
the old MME (the next-hop IP address for the old VLAN mapping is 192.168.221.2)*/
RMV VLANMAP:NEXTHOPIP="192.168.221.2", MASK="255.255.255.0";
/*Removing the IP route from the eNodeB to the old MME*/
RMV IPROUTE4:RTIDX=0;
/*Removing the old S1Interface MO with the S1 Interface ID of 0*/
RMV S1INTERFACE:S1InterfaceId=0;
/*Removing the old CP bearer with the CP Bear No. of 0*/
RMV CPBEARER:CPBEARID=0, FLAG=MASTER;
/*Removing the SCTP link corresponding to the old MME*/
RMV SCTPLNK:SCTPNO=0;
/*Removing the device IP address corresponding to the old MME*/
RMV IPADDR4:ITFID=0, IP="192.168.3.109";
/*Removing the interface for the IPv4 address corresponding to the old MME*/
RMV INTERFACE:ITFID=1;

1.8.3.3 Engineering Implementation

This section describes the engineering implementation for replacing an MME,
including prerequisites, context, and procedure.

Prerequisites
● Information and data for replacing an MME are ready, and the license file is
available in the save path on the FTP server.
● The cutover to the new MME is successful, and the new MME can collaborate
with EPC equipment such as the HSS and S-GW.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Connect the eNodeB to the new MME.
b. Configure the intermediate equipment between the eNodeB and the new
MME.
● Remote Operations
– Using the MAE-Deployment:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 532

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the LST GLOBALPROCSWITCH command to query the values of
the options of The Switch of S1-MME Configuration by SON
parameter.
○ If the values of the options are Off, skip this step.
○ If the values of the options are On, run the MOD
GLOBALPROCSWITCH command with the options of The
Switch of S1-MME Configuration by SON deselected. Example:
MOD GLOBALPROCSWITCH:
S1MMESonSwitch=S1MMESonSetupSwitch-0&S1MMESonDel
eteSwitch-0;
iii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iv. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
v. Deliver the data for adding an MME connection (in endpoint mode
or link mode) and activate it on the eNodeB. For detailed operations,
see Delivering Data to Base Stations and Activating the Data.
vi. Run the DSP S1INTERFACE command to check the S1 status. If the
S1 interface works properly, go to the next step. Otherwise, see the
description of ALM-29201 S1 Interface Fault for troubleshooting.
vii. Deliver the data for removing an old MME connection (in endpoint
mode or link mode) and activate it on the eNodeB.
On the menu bar, choose Area Management > Planned Area >
Export Incremental Scripts to start the wizard of exporting scripts.
Then, select Launch Script Executor in the wizard to activate
exported scripts for data to take effect on the live network. For
detailed operations, see section Exporting Incremental Scripts from
a Planned Data Area in the MAE-Access online help.
viii. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 533

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ix. Restore the values of the switches changed in ii.

– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Deliver the script for adding an MME connection (in endpoint mode
or link mode) and activate it on the eNodeB:
Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. Run the DSP S1INTERFACE command to check the S1 status. If the
S1 interface works properly, go to the next step. Otherwise, see the
description of ALM-29201 S1 Interface Fault for troubleshooting.
v. Deliver the script for removing an old MME connection (in endpoint
mode or link mode) and activate it on the eNodeB:
Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
vi. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.8.3.4 Engineering Verification

This section describes how to verify the reconfiguration for replacing an MME.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 534

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Verify that no new alarms are reported.
If a new alarm is reported, clear the alarm according to the instructions in 3900 &
5900 Series Base Station Alarm Reference.
Step 2 Run the LST SCTPLNK command. Check whether there is an SCTP link between
the eNodeB and the new MME. If the peer IP address of the SCTP link is the
signaling IP address of the new MME, an SCTP link exists between the eNodeB
and the new MME.
If the peer IP address of the SCTP link is not the signaling IP address of the new
MME, perform the following steps.
If... Then...

The reconfiguration is
performed on the
MAE-Deployment
View the modified configuration data file and check
whether the peer IP address is the same as the
signaling IP address of the new MME:
● If they are different, modify the configuration data
file again and import it into the system. Then
perform the operations in Engineering
Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the
data is imported into the system or delivered to the
base station. In this situation, contact Huawei
technical support or dial the Huawei technical
support hotline.

The reconfiguration is
performed by using
MML commands
Check whether the peer IP address in the script is the
same as the signaling IP address of the new MME:
● If they are different, modify the parameter settings
in the script. Then run the MOD SCTPPEER
command to change the peer IP address to the
correct value.
● If they are the same, contact Huawei technical
support or dial the Huawei technical support
hotline.

Step 3 Run the DSP SCTPLNK command to check whether the value of SCTP Link Status
for the link between the eNodeB and the new MME is Up.
If the value of SCTP Link Status is Down, perform the following steps:
1. Perform a ping operation on the route from the device IP address of the
eNodeB to the signaling IP address of the MME (old model)/IPv4 address
(new model)/IPv6 address (new model).
– If the ping operation fails, go to Step 3.2.
– If the ping operation is successful, go to Step 3.3.
2. Check whether the SCTP link configurations are correct. Specifically, check
whether the IP route from the eNodeB to the MME is correct and whether the

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 535

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

port mode and port rate of the Ethernet port on the eNodeB are the same as
those on the peer device.
– If the configuration is incorrect, modify the configuration.
– If the configuration is correct, go to Step 3.4.
3. Check whether the value of Peer SCTP Port No. for the SCTP link is the same
as the SCTP port number of the new MME.
– If they are different, modify the configurations.
– If they are the same, go to Step 3.4.
4. Check the configurations of the device between the eNodeB and MME.
– If the configurations or cable connections are incorrect, modify the
configurations or cable connections.
– If the configurations or cable connections are correct, contact Huawei
technical support or dial the Huawei technical support hotline.
Step 4 Enable a UE to access the network. Check whether the access is successful.
If the UE fails to access the network, check the cell status.
● If the cell fails to be established, the eNodeB reports an alarm. If this
happens, clear the alarm according to the instructions in 3900 & 5900 Series
Base Station Alarm Reference
● If the cell is successfully established, contact Huawei technical support or dial
the Huawei technical support hotline.

----End

1.8.3.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 536

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. Run the DSP ROLCFGINFO command to query the configuration

rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful according to instructions in 1.8.3.4

Engineering Verification.

----End

1.8.4 Replacing an S-GW

This section describes how to replace an S-GW.

Prerequisites
Data for the transport network between the eNodeB and the new S-GW has been
configured.

1.8.4.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for replacing an S-GW.

Application Scenario
An S-GW needs to be replaced when the EPC topology changes.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 537

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Impact
The eNodeB disconnects from the old S-GW during S-GW replacement before a
connection to the new S-GW is set up. Therefore, services carried on the old S1
link are interrupted.

Reconfiguration Scheme
Figure 1-99 and Figure 1-102 show the reconfiguration procedures for replacing
an S-GW. Determine the reconfiguration scheme for replacing an S-GW according
to the following table.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Table 1-174 Scheme options

If… Then...

The device IP address of the eNodeB Add a device IP address on the

cannot meet requirements when both eNodeB.
old and new S-GWs exist

No route is available between the Add a route from the eNodeB to the
eNodeB and the new S-GW new S-GW and the corresponding
VLANMAP MO.

A new device IP address has been ● Change the IP address of the user-
added plane host to the new device IP
address.
● Remove the old device IP address
after data reconfiguration is
completed.

A new IP route has been added Remove the route from the eNodeB to
the old S-GW.

Note: The network segment on which the eNodeB is located can be calculated
based on the values of Mask and IP Address of the corresponding Ethernet
port.

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 538

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-175 Scheme options

If… Then...

The IPv4/IPv6 address of the eNodeB Add an IPv4/IPv6 address on the

cannot meet requirements when both eNodeB.
old and new S-GWs exist

No route is available between the Add a route from the eNodeB to the
eNodeB and the new S-GW new S-GW and the corresponding
VLANMAP MO.

A new IPv4/IPv6 address has been ● Change the IP address of the user-
added plane host to the new IPv4/IPv6
address.
● Remove the old IPv4/IPv6 address
after data reconfiguration is
completed.

A new IP route has been added Remove the route from the eNodeB to
the old S-GW.

Note: The network segment on which the eNodeB is located can be calculated
based on the values of Mask (IPv4)/Prefix Length (IPv6) and IP Address
(IPv4)/IPv6 Address (IPv6) of the corresponding Ethernet port.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 539

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-99 Procedure for replacing an S-GW in endpoint mode (IPv4)

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 540

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-100 Procedure for replacing an S-GW in endpoint mode (IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 541

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-101 Procedure for replacing an S-GW in endpoint mode (IPv6)

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Figure 1-102 Procedure for replacing an S-GW in link mode

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 542

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-103 Procedure for replacing an S-GW in link mode

Topology Change
N/A

1.8.4.2 Engineering Preparation

This section describes the engineering preparation for replacing an S-GW,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-176 and Table 1-177 describe the information to be collected for data
preparation.

Table 1-176 Information to be collected (endpoint mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask (IPv4)/prefix length (IPv6), and route
eNodeB to the S-GW priority.

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the S-GW

Service IP address of Peer IP address of an S1 service link automatically set

the S-GW up by the eNodeB

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 543

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Device IP address Device IP address (old model)/IPv4 address (new

(old model)/IPv4 model)/IPv6 address (new model) used for
address (new communication with external devices
model)/IPv6 address
(new model) of the
eNodeB

User-plane Includes:
information of the S1 ● User-plane host
interface
● User-plane peer

Information about ID of the endpoint group to which the user-plane peer is

the endpoint group to be added

Table 1-177 Information to be collected (link mode)

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the S-GW

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the S-GW

Service IP address of Peer IP address of an S1 service link automatically set

the S-GW up by the eNodeB

Device IP address Device IP address (old model)/IPv4 address (new

(old model)/IPv4 model) used for communicating with external devices
address (new model)
of the eNodeB

User-plane Includes:
information of the S1 ● IP path
interface
● eNodeB IP path

Hardware Preparation
Prepare the hardware listed in Table 1-178.

Table 1-178 Hardware to be prepared

Hardware Description

S-GW -

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 544

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

NOTE

This document does not describe how to configure the new S-GW. For details, see S-GW-related
documentation.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Table 1-179 Data preparation for replacing an S-GW in endpoint mode

SN Ope MO Configuration Reference
ratio
n

1 Add IPv4: DEVIP For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPv4: IPRT/SRCIPRTa

3 Add IPv4: VLANMAP

4 Modi USERPLANEHOST Change the local IP address to the new

fy device IP address.

5 Modi USERPLANEPEER Change the peer IP address to the

fy service IP address of the new S-GW.

6 Dele IPv4: IPRT/SRCIPRT Remove the IP route used for

te communication with the old S-GW.

7 Dele IPv4: DEVIP Remove the device IP address for

te communicating with the old S-GW.

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 545

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-180 Data preparation for replacing an S-GW in endpoint mode

SN Ope MO Configuration Reference

ratio
n

1 Add INTERFACE For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPv4: IPADDR4
IPv6: IPADDR6

3 Add IPv4: IPROUTE4/

SRCIPROUTE4a
IPv6: IPROUTE6

4 Add IPv4: Add a VLANMAP

MO when you
configure a VLAN
based on VLAN
mapping.
IPv6: N/A

5 Modi USERPLANEHOST Change the local IP address to the new

fy IPv4/IPv6 address.

6 Modi USERPLANEPEER Change the peer IP address to the

fy service IP address of the new S-GW.

7 Dele IPv4: IPROUTE4/ Remove the IPv4/IPv6 route used for

te SRCIPROUTE4 communication with the old S-GW.
IPv6: IPROUTE6

8 Dele IPv4: IPADDR4 Remove the IPv4/IPv6 address used for

te IPv6: IPADDR6 communication with the old S-GW.

9 Dele INTERFACE If the INTERFACE MO for the IP address

te that the eNodeB uses to communicate
with the old S-GW has no IP address
configured, delete this INTERFACE MO.

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 546

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-181 Data preparation for replacing an S-GW in link mode

SN Ope MO Configuration Reference

ratio
n

1 Add DEVIP For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPRT/SRCIPRTa

3 Add VLANMAP

4 Modi IPPATH Change the local IP address to the new

fy device IP address.

5 Dele IPRT/SRCIPRT Remove the IP route used for

te communication with the old S-GW.

6 Dele DEVIP Remove the device IP address for

te communicating with the old S-GW.

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-182 Data preparation for replacing an S-GW in link mode

SN Ope MO Configuration Reference

ratio
n

1 Add INTERFACE For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPADDR4

3 Add IPROUTE4/
SRCIPROUTE4a

4 Add Add a VLANMAP MO

when you configure a
VLAN based on VLAN
mapping.

5 Modi IPPATH Change the local IP address to the new

fy IPv4 address.

6 Dele IPROUTE4/ Remove the IPv4 route used for

te SRCIPROUTE4 communication with the old S-GW.

7 Dele IPADDR4 Remove the IPv4 route used for

te communication with the old S-GW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 547

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

8 Dele INTERFACE If the INTERFACE MO for the IP address

te that the eNodeB uses to communicate
with the old S-GW has no IP address
configured, delete this INTERFACE MO.

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Replacing an S-GW"): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, a device IP address and a route need to be added.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 548

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
● Endpoint mode
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address*/
ADD DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.3.110", MASK="255.255.255.0";
/*Adding an IP route from the eNodeB to the new S-GW*/
ADD IPRT: RTIDX=1, SN=7, SBT=BASE_BOARD, DSTIP="192.168.3.3", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.3.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.3.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=10
1,SETPRIO=DISABLE;
/*Modifying the configuration of the user-plane host of the S1 interface*/
MOD USERPLANEHOST:UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.3.110";
/*Modifying the configuration of the user-plane peer of the S1 service (that is, changing the service IP
address over the S1 interface to the service IP address of the new S-GW)*/
MOD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, PEERIPV4="192.168.3.3";
/*Removing the IP route from the eNodeB to the old S-GW with the Route Index of 0*/
RMV IPRT:RTIDX=0;
/*Removing the old device IP address*/
RMV DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.3.109";
New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO
is set to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Setting Ethernet port 0*/
SET ETHPORT:CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD
VLANMAP:NEXTHOPIP="192.168.3.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=10
1,SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;
/*Adding an IPv4 address*/
ADD IPADDR4:ITFID=0, IP="192.168.3.110", MASK="255.255.255.0";
/*Adding an IPv4 route from the eNodeB to the new S-GW*/
ADD IPROUTE4: RTIDX=1, DSTIP="192.168.3.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.3.1", MTUSWITCH=OFF;
/*Modifying the configuration of the user-plane host of the S1 interface*/
MOD USERPLANEHOST:UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.3.110";
/*Modifying the configuration of the user-plane peer of the S1 service (that is, changing the service IP
address over the S1 interface to the service IPv4 address of the new S-GW)*/
MOD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, PEERIPV4="192.168.3.3";
/*Removing the IPv4 route from the eNodeB to the old S-GW with the Route Index of 0*/
RMV IPROUTE4:RTIDX=0;
/*Removing the old IPv4 address*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 549

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

RMV IPADDR4:ITFID=0, IP="192.168.3.109";

/*Removing the interface for the old IPv4 address*/
RMV INTERFACE:ITFID=1;

● Link mode
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address*/
ADD DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.3.110", MASK="255.255.255.0";
/*Adding an IP route from the eNodeB to the new S-GW*/
ADD IPRT: RTIDX=1, SN=7, SBT=BASE_BOARD, DSTIP="192.168.3.3", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.3.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.3.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=10
1,SETPRIO=DISABLE;
/*Changing the local and peer IP addresses of an IP path*/
MOD IPPATH:PATHID=0, SN=7, LOCALIP="192.168.3.110", PEERIP="192.168.3.3";
/*Removing the IP route from the eNodeB to the old S-GW with the Route Index of 0*/
RMV IPRT:RTIDX=0;
/*Removing the old device IP address*/
RMV DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.3.109";

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO
is set to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Setting Ethernet port 0*/
SET ETHPORT:CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD
VLANMAP:NEXTHOPIP="192.168.3.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=10
1,SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;
/*Adding an IPv4 address*/
ADD IPADDR4:ITFID=0, IP="192.168.3.110", MASK="255.255.255.0";
/*Adding an IPv4 route from the eNodeB to the new S-GW*/
ADD IPROUTE4: RTIDX=1, DSTIP="192.168.3.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.3.1", MTUSWITCH=OFF;
/*Changing the local and peer IP addresses of an IP path*/
MOD IPPATH:PATHID=0, TRANSCFGMODE=NEW, JNIPRSCGRP=DISABLE, BPT=ETH, PORTID=1,
LOCALIP="192.168.3.110", PEERIP="192.168.3.3";
/*Removing the IPv4 route from the eNodeB to the old S-GW with the Route Index of 0*/
RMV IPROUTE4:RTIDX=0;
/*Removing the old IPv4 address*/
RMV IPADDR4:ITFID=0, IP="192.168.3.109";
/*Removing the interface for the old IPv4 address*/
RMV INTERFACE:ITFID=1;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 550

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.4.3 Engineering Implementation

This section describes the engineering implementation for replacing an S-GW,
including prerequisites, context, and procedure.

Prerequisites
● Information for replacing an S-GW has been collected, configuration data is
ready, and the license file is available in the save path on the FTP server.
● The cutover to the new S-GW is successful, and the new S-GW can
collaborate with EPC equipment such as the HSS and MME.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

Connect the eNodeB to the new S-GW.

● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the LST GTRANSPARA command to query the value of
Endpoint Object Auto-configure Switch.
○ If the value is Disable, skip this step.
○ If the value is Enable, run the SET GTRANSPARA command with
Endpoint Object Auto-configure Switch set to DISABLE.
Example: SET GTRANSPARA: EPOBJAUTOCFGSW=DISABLE;
iii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iv. Import a new license file.
Run the INS LICENSE command.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 551

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For example: INS LICENSE: DIR="ftproot/",

FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
v. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
vi. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
vii. Restore the value of the switch changed in ii.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.8.4.4 Engineering Verification

This section describes how to verify the reconfiguration for replacing an S-GW.

Procedure
Step 1 Verify that ALM-25952 User Plane Path Fault is not reported.

If ALM-25952 User Plane Path Fault is reported, clear the alarm according to the
instructions in 3900 & 5900 Series Base Station Alarm Reference.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 552

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 2 Run the LST USERPLANEPEER command to verify that the value of User Plane
Peer ID of one IP path is the same as the service IP address of the new S-GW.
If they are different, check whether the transmission configuration is correct.
● If it is incorrect, modify it.
● If it is correct, contact Huawei technical support or dial the Huawei technical
support hotline.
Step 3 Enable a UE to access the network. Check whether the access is successful.
If the UE fails to access the network, check the cell status.
● If the cell fails to be established, the eNodeB reports an alarm. If this
happens, clear the alarm according to the instructions in 3900 & 5900 Series
Base Station Alarm Reference
● If the cell is successfully established, contact Huawei technical support or dial
the Huawei technical support hotline.

----End

1.8.4.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 553

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful according to instructions in 1.8.4.4

Engineering Verification.

----End

1.8.5 Replacing the MAE

This section describes how to replace the MAE (including changing the IP address
of the MAE).

Prerequisites
Data has been configured for the transport network between the eNodeB and the
new MAE.

1.8.5.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for replacing the MAE.

Application Scenario
The MAE needs to be replaced when the deployment of the MAE and base station
changes.

Reconfiguration Impact
The OM channel between the eNodeB and the old MAE is disconnected during
MAE replacement before an OM channel is set up between the eNodeB and the
new MAE. As a result, the eNodeB is not managed by any MAE.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 554

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme
Figure 1-104 shows the reconfiguration procedure for replacing the MAE.
Determine the reconfiguration scheme according to the following table.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-183 Scheme options

If… Then...

The device IP addresses of Add device IP addresses on the eNodeB.

the existing eNodeB cannot
meet requirements when
both old and new MAEs
exist

No route is available Add a route from the eNodeB to the new MAE
between the eNodeB and and the corresponding VLANMAP MO.
the new MAE

A new IP route has been Remove the route between the eNodeB and the
added old MAE.

A new device IP address Remove the old device IP address.

has been added

Note: The network segment on which the eNodeB is located can be calculated
based on the values of Mask and IP Address of the corresponding Ethernet
port.

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-184 Scheme options

If... Then...

The current VLAN of the Add a VLAN interface on the base station.
base station does not meet
requirements when both old
and new MAEs exist

The IPv4/IPv6 address of the Add an IPv4/IPv6 address on the eNodeB.

eNodeB cannot meet
requirements when both old
and new MAEs exist

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 555

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

No route is available Add a route from the eNodeB to the new MAE
between the eNodeB and and the corresponding VLANMAP MO.
the new MAE

A new IPv4/IPv6 route has Remove the route between the eNodeB and the
been added old MAE.

A new IPv4/IPv6 address has Remove the old IPv4/IPv6 address.

been added

A VLAN interface has been Remove the old VLAN interface.

added and no IPv6 address
on original interface is in
use

Note: The network segment on which the eNodeB is located can be calculated
based on the values of Mask (IPv4)/Prefix Length (IPv6) and IP Address
(IPv4)/IPv6 Address (IPv6) of the corresponding Ethernet port.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Figure 1-104 Reconfiguration procedure for replacing the MAE (IPv4)

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 556

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-105 Reconfiguration procedure for replacing the MAE (IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 557

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-106 Reconfiguration procedure for replacing the MAE (IPv6)

NOTE

If the original MAE is faulty, you need to set the route mask to 32 bits in the blind-start base
station deployment list on the target MAE. After the OM channel is established, perform the
replacement according to the normal process.

Topology Change
N/A

1.8.5.2 Engineering Preparation

This section describes the engineering preparation for replacing the MAE,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-185 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 558

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-185 Information to be collected

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask (IPv4)/prefix length (IPv6), and route
eNodeB to the new priority.
MAE

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the new
MAE

IP address and ● If the new MAE uses multi-server load-sharing (SLS),

subnet mask (IPv4)/ you need to obtain the IP address and subnet mask
prefix length (IPv6) (IPv4)/prefix length (IPv6) of the network segment
of the new MAE where the new master MAE server is located. The
master, slave, and standby servers of the MAE are
located on the same network segment.
● If the new MAE does not use SLS, you need to obtain
the IP address and subnet mask (IPv4)/prefix length
(IPv6) of the new MAE.

eNodeB version Includes the eNodeB version number and mediation

information software version number.

Hardware Preparation
Prepare the hardware listed in Table 1-186.

Table 1-186 Hardware to be prepared

Hardware Description

MAE server If no new MAE has been deployed, prepare the server
for deploying the MAE.

Software Preparation
Prepare the software listed in Table 1-187 before replacing the MAE.

Table 1-187 Software to be prepared

Software Description

MAE software If no new MAE has been deployed, prepare the MAE
software compatible with the eNodeB for deploying the
MAE.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 559

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Description

NE mediation The NE mediation software provides the access

software adaption function for different NEs and versions. With
NE mediation software, the MAE can obtain and
recognize data reported by NEs through their interfaces.

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

NOTE

This document does not describe how to configure the new MAE. For details, see MAE-related
documentation.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Table 1-188 Data preparation for replacing the MAE

SN Ope MO Configuration Reference

ratio
n

1 Add IPv4: DEVIP For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPv4: IPRT/SRCIPRTa ● If the new MAE uses multi-server
load-sharing (SLS), set Destination
3 Add IPv4: VLANMAP IP to the IP address of the network
segment where the master MAE
server is located.
● If the new MAE does not use SLS, set
Destination IP to the IP address of
the new MAE.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
4 Modi OMCH Set Peer IP to the IP address of the new
fy MAE.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 560

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

5 Dele IPv4: IPRT/SRCIPRT Delete the IP route used for

te communicating with the old MAE.

6 Dele IPv4: DEVIP Remove the device IP address used for

te communicating with the old MAE.

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-189 Data preparation for replacing the MAE

SN Ope MO Configuration Reference

ratio
n

1 Add IPv4: IPADDR4 For details, see IP eRAN Engineering

IPv6: IPADDR6 Guide Feature Parameter Description.

2 Add IPv4: IPROUTE4/ ● If the new MAE uses multi-server

SRCIPROUTE4a load-sharing (SLS), set Destination
IPv6: IPROUTE6 IP to the IP address of the network
segment where the master MAE
3 Add IPv4: (optional) server is located.
VLANMAP ● If the new MAE does not use SLS, set
IPv6: N/A Destination IP to the IP address of
the new MAE.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
4 Modi OMCH Set Peer IP to the IP address of the new
fy MAE.

5 Dele IPv4: IPROUTE4/ Remove the IP route used for

te SRCIPROUTE4 communicating with the old MAE.
IPv6: IPROUTE6

6 Dele IPv4: IPADDR4 Remove the IPv4/IPv6 address used for

te IPv6: IPADDR6 communicating with the old MAE.

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 561

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Replacing the U2000"): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, a device IP address and a route need to be added.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
/*Adding a device IP address*/
ADD DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="172.31.13.18", MASK="255.255.255.0";
/*Adding a route from the eNodeB to the new MAE-Access*/
ADD IPRT:RTIDX=1, SN=7, SBT=BASE_BOARD, DSTIP="10.148.36.103", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="172.31.13.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="172.31.13.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SET
PRIO=DISABLE;
/*Modifying an OM channel*/
MOD OMCH: FLAG=MASTER, IP="172.31.13.18", MASK="255.255.255.0", PEERIP="10.148.36.103",
PEERMASK="255.255.0.0", BEAR=IPV4, BRT=YES, RTIDX=1, BINDSECONDARYRT=NO,
CHECKTYPE=AUTO_UDPSESSION, UDPSN=1, USERLABEL=NONE;
/*Removing the IP route from the eNodeB to the old MAE-Access with the Route Index being 0*/
RMV IPRT:RTIDX=0;
/*Removing the old device IP address*/
RMV DEVIP:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="172.31.13.15";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 562

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.
/*Setting Ethernet port 0*/
SET ETHPORT:CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD VLANMAP:NEXTHOPIP= NEXTHOPIP="172.31.13.1", MASK="255.255.255.255",
VLANMODE=SINGLEVLAN, VLANID=101, SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;
/*Adding an IP address*/
ADD IPADDR4:ITFID=0, IP="172.31.13.18", MASK="255.255.255.0";
/*Adding a route from the eNodeB to the new MAE-Access*/
ADD IPROUTE4:RTIDX=1, DSTIP="10.148.36.103", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="172.31.13.1", MTUSWITCH=OFF;
/*Modifying an OM channel*/
MOD OMCH: FLAG=MASTER, IP="172.31.13.18", MASK="255.255.255.0", PEERIP="10.148.36.103",
PEERMASK="255.255.0.0", BEAR=IPV4, BRT=YES, RTIDX=1, BINDSECONDARYRT=NO,
CHECKTYPE=AUTO_UDPSESSION, UDPSN=1, USERLABEL=NONE;
/*Removing the IP route from the eNodeB to the old MAE-Access with the Route Index being 0*/
RMV IPROUTE4:RTIDX=0;
/*Removing the old IPv4 address*/
RMV DEVIP:ITFID=0, IP="172.31.13.15";

1.8.5.3 Engineering Implementation

This section describes the engineering implementation for replacing the MAE,
including prerequisites, context, and procedure.

Prerequisites
Information, software, and data required for replacing the MAE are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

NOTICE

To reduce the time when the eNodeB is disconnected from the MAE, set up the
OM channel between the eNodeB and the new MAE first, and then disconnect the
OM channel between the eNodeB and the old MAE.

Procedure
● Local Operations
a. (Optional) Deploy a new MAE if no new MAE has been deployed.
b. Connect the base station to the new MAE.
● Remote Operations

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 563

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

a. Back up the configuration file that can be used to restore the eNodeB if
the reconfiguration fails.
i. On the menu bar of the MAE-Access, choose Maintenance > Backup
Management > NE Backup.
ii. In the left navigation tree of the NE Backup window, choose
eNodeB to select an eNodeB whose configuration file is to be backed
up.
iii. Click Backup to back up the configuration file to the FTP server.
iv. After the backup succeeds, click Upload to OSS Server to download
the backup configuration file to the local PC.
b. Deliver the data to the eNodeB and then activate the data.

▪ Using the MAE-Deployment:

1) Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being
reported during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
2) Back up and export the configuration file. The configuration file
can be used to roll back configurations to the original state, if
the reconfiguration fails.
1) Run the BKP CFGFILE command to back up the
configuration file.
2) Run the ULD CFGFILE command to export the configuration
file.
For example: ULD CFGFILE: MODE=IPV4,
IP="10.169.18.69", USR="ftpuser", PWD="***********",
DIR="ftproot/";
3) Deliver the configuration data to the eNodeB and activate the
data. For details, see the interactive operation guide Delivering
Data to Base Stations and Activating the Data.
4) After the reconfiguration is complete, set the eNodeB
maintenance mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB
to NORMAL.

▪ Using MML commands:

1) Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being
reported during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
2) Back up and export the configuration file. The configuration file
can be used to roll back configurations to the original state, if
the reconfiguration fails.
1) Run the BKP CFGFILE command to back up the
configuration file.
2) Run the ULD CFGFILE command to export the configuration
file.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 564

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For example: ULD CFGFILE: MODE=IPV4,

IP="10.169.18.69", USR="ftpuser", PWD="***********",
DIR="ftproot/";
3) Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to
the base station and activate the scripts on the base station. For
details, see 1.3.3 Running MML Commands on the MAE-
Access.
4) After the reconfiguration is complete, set the eNodeB
maintenance mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB
to NORMAL.

----End

1.8.5.4 Engineering Verification

This section describes how to verify the reconfiguration for replacing the MAE.

Procedure
Step 1 Verify that no ALM-25901 Remote Maintenance Link Failure has been reported.

If ALM-25901 Remote Maintenance Link Failure is reported, clear the alarm

according to the instructions in 3900 & 5900 Series Base Station Alarm Reference.

----End

1.8.5.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Prerequisites
● The original configuration file is available on the FTP server.
● The eNodeB is communicating with the FTP server properly.

Context
If the reconfiguration fails, the OM channel will be disconnected. Therefore, the
engineering rollback can be performed only on the local LMT.

Procedure
Step 1 Restore the configuration data.
● On the LMT, download and activate the original configuration file.
a. Run DLD CFGFILE to download the configuration file to the eNodeB.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 565

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

b. Run ACT CFGFILE to activate the configuration file.

Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Roll back the configuration data using the one-click blind configuration
rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 Restore the physical connections.

Step 3 Verify that engineering rollback is successful according to instructions in 1.8.5.4

Engineering Verification.

----End

1.8.6 Changing the Local Maintenance IP Address

This section describes how to change the local maintenance IP address.

1.8.6.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the local maintenance
IP address.

Application Scenario
The previous local maintenance IP address plan is inappropriate and a new plan is
required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 566

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Impact
When you change the local maintenance IP address, the eNodeB stops
communicating with the LMT. After the reconfiguration, use the new local
maintenance IP address to log in to the LMT.

Reconfiguration Scheme
To change the local maintenance IP address, change IP Address and Mask of the
LOCALIP MO (IPv4) or IPv6 Address and Prefix Length of the LOCALIP6 MO
(IPv6) to the target values.

Topology Change
N/A

1.8.6.2 Engineering Preparation

This section describes the engineering preparation for changing the local
maintenance IP address, including information collection and preparation of
hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-190 describes the information to be collected for data preparation.

Table 1-190 Information to be collected

Information Description

Base station Base station identification (BS ID).

information

Local maintenance Includes the new local maintenance IPv4 address and
IPv4 information subnet mask.

Local maintenance New local maintenance IPv6 address. The IPv6 address
IPv6 information type must be a link-local address.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 567

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Security Certificate Preparation

N/A

Data Preparation
Prepare data listed in the following table.

Table 1-191 Data preparation for changing the local maintenance IP address
SN Ope MO Configuration Reference
ratio
n

1 Modi IPv4: LOCALIP Change the values of IP Address and

fy IPv6: LOCALIP6 Mask (IPv4) or IPv6 Address and Prefix
Length (IPv6) to the target values.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario-specific template being "Changing the Local
Maintenance IP Address"): For details, see the interactive operation guide
1.11.2 Using the Batch Reconfiguration Mode of the MAE-Deployment to
Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, the local IP address and subnet mask are changed to
192.168.0.49 and 255.255.255.0, respectively.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 568

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

automatic rollback switch of the CB by running the CFM CB command before

configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Change the local IP address to 192.168.0.49.*/
SET LOCALIP: IP="192.168.0.49", MASK="255.255.255.0";

1.8.6.3 Engineering Implementation

This section describes the engineering implementation for changing the local
maintenance IP address, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
iii. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 569

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1) Run the BKP CFGFILE command to back up the configuration

file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.8.6.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the local
maintenance IP address.

Procedure
Step 1 Run the LST LOCALIP command to check whether the values of IP Address and
Mask are the same as planned for IPv4 transmission.

If the values of IP Address and Mask are not the same as planned, view the
modified configuration data file to check whether they are the same as planned.

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

Run the LST LOCALIP6 command to check whether the value of IPv6 Address is
the same as planned for IPv6 transmission.

If the value of IPv6 Address is not the same as planned, check whether the value
of IPv6 Address in the modified configuration data file is the same as planned.

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 570

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.6.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.8.6.4

Engineering Verification.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 571

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.7 Changing the Device IP Address (Old Model)

This section describes how to change a device IP address (old model).

NOTE

This task is applicable only when the TRANSCFGMODE parameter in the GTRANSPARA MO is
set to OLD.

1.8.7.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing a device IP address.

Application Scenario
The previous device IP address plan is inappropriate and a new plan is required.

Reconfiguration Impact
● If the device IP address to be changed is the OM IP address, the MAE-Access
and MAE-Deployment will be disconnected from the NE after the old OM
channel becomes invalid and before the new OM channel is set up.
● If the device IP address to be changed is used for service transmission, the
service link (for example, an S1 or X2 interface) using this IP address will be
reestablished. During the reestablishment, services on the link will be
interrupted.
● If the device IP address to be changed is used for IPsec negotiations, an IPsec
renegotiation is required. During the renegotiation, services on the IPsec
tunnel will be interrupted.
● If related IP information is not completely modified on other NEs and the to-
be-reconstructed base station when you change the device IP address,
network loop may occur.

Reconfiguration Scheme
The following information describes how to reconfigure the device IP address for a
multimode base station (MBTS).
● If the device IP address to be changed is shared by all RATs in a co-MPT
MBTS, such as the OM IP address, the IP Address in the DEVIP MO needs to
be changed only once. After the device IP address is changed, the MOs that
reference this IP address must be modified on the base station side, including
the OMCH, IPPATH, SCTPLNK, USERPLANEHOST, and SCTPHOST. In addition,
the device IP address must be changed to the new one on the peer devices,
such as the MAE-Access, base station controller, and MME/S-GW.
● The method of changing the device IP address for the separate-MPT MBTS is
the same as that for a single-mode base station. When IP co-transmission is
adopted:
– If the IP address is changed on the RAT that does not provide
transmission, the route from the RAT that provides transmission to the
RAT that does not provide transmission needs to be changed. That is,
change the "Destination IP Address" to the new IP address.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 572

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– If co-transmission through panel interconnection is adopted and the IP

address of the interconnected port providing transmission is changed, the
route from the RAT that provides transmission to the peer RAT needs to
be changed, that is, change the "Next Hop IP Address" to the new IP
address.
NOTE

● For details about how to change IP addresses for GSM, see GBSS Reconfiguration Guide for
BSC6900.
● For details about how to change IP addresses for UMTS, see RAN Reconfiguration Guide for
BSC6900.
● For details about how to change IP addresses for LTE, see this section. You must also modify
related IP information on other NEs and the to-be-reconstructed base station when changing
the device IP address.

The reconfiguration schemes using the MAE-Deployment and using MML

commands are different because you cannot directly change a device IP address
using MML commands.
NOTE

● If the device IP address to be changed is the OM IP address, change the OM IP address to

the new device IP address for the eNodeB on the MAE-Access after the eNodeB
reconfiguration is completed.
● If the device IP address is used for X2 links and the value of the SCTP Peer ID parameter in
the SCTPPEER MO is the same as the peer base station ID, use the MAE-Deployment to
perform batch configuration to automatically update the configurations on the peer base
station. No manual operation is required.

The DEVIP MO shares associations and configuration restrictions with many MOs.
If the DEVIP MO is modified, these MOs must also be modified. The following
figure shows the associations and restrictions between these MOs.

Figure 1-107 MOs related to the DEVIP MO (IPv4)

MOs highlighted in blue They reference the DEVIP MO.

MOs highlighted in green They share configuration restrictions with the

DEVIP MO.

MOs highlighted in gray They share both reference relationships and

configuration restrictions with the DEVIP MO.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 573

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

One-way arrows They indicate association relationships.

When the MAE-Deployment is used, change the corresponding parameters in

the MOs listed in Table 1-192 and Table 1-193 to the new device IP address.
● Endpoint mode

Table 1-192 Reconfiguration schemes for changing a device IP address (MAE-

Deployment, in endpoint mode)
If... Then...

- Change the device IP address.

DEVIP

The device IP address is used for Change the next-hop IP address of the
an IP route, and the new and old IP route to the new gateway IP address.
device IP addresses are not on IPRT/SRCIPRTa
the same network segment

The device IP address is used for Change the next-hop IP address in the
an IP route, and the new and old VLANMAP MO to the new gateway IP
device IP addresses are not on address.
the same network segment VLANMAP

The device IP address is used for Modify the S1-link-related parameters.

an S1 link ● SCTPHOSTb
● USERPLANEHOST

The device IP address is used for Modify the X2-link-related parameters.

an X2 link ● SCTPHOST
● USERPLANEHOST

An IP path has been configured Modify the information about the IP

path.
IPPATH

The device IP address is used for Modify the OMCH.

the OMCH OMCH

The device IP address is used for Modify the IP clock link.

an IP clock link IPCLKLNK

A link that uses the device IP Modify the BFD session.

address supports Bidirectional BFDSESSION
Forwarding Detection (BFD)

The device IP address is used for Modify the IPsec-related parameters.

IPsec negotiation ● IKEPEER
● ACLRULE

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 574

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.
b: In endpoint mode, an S1 interface is automatically set up after its peer is
manually configured. In addition, if the slot number of the board where the
local IP address is located changes after the SCTPHOST MO is modified, the
eNodeB automatically removes and then sets up an S1 interface. If S1
Configuration Type in an MmeCapInfo MO is set to S1INTERFACE_CFG
and the S1 interface associated with S1 Interface ID in the MmeCapInfo
MO is automatically removed and then set up, the MmeCapInfo MO
corresponding to the S1 interface is also removed. As a result, the new S1
interface is not associated with any MmeCapInfo MO. In this case, you
need to reconfigure and associate the new S1 interface with the
MmeCapInfo MO.

● Link mode

Table 1-193 Reconfiguration schemes for changing a device IP address (MAE-

Deployment, in link mode)
If... Then...

- Change the device IP address.

DEVIP

The device IP address is used for Change the next-hop IP address of the
an IP route, and the new and old IP route to the new gateway IP address.
device IP addresses are not on IPRT/SRCIPRTa
the same network segment

The device IP address is used for Change the next-hop IP address in the
an IP route, and the new and old VLANMAP MO to the new gateway IP
device IP addresses are not on address.
the same network segment VLANMAP

The device IP address is used for Modify the S1-link-related parameters.

an S1 link ● SCTPLNK
● IP Path

The device IP address is used for Modify the X2-link-related parameters.

an X2 link ● SCTPLNK
● IPPATH

The device IP address is used for Modify the OMCH.

the OMCH OMCH

The device IP address is used for Modify the IP clock link.

an IP clock link IPCLKLNK

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 575

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

A link that uses the device IP Modify the BFD session.

address supports Bidirectional BFDSESSION
Forwarding Detection (BFD)

The device IP address is used for Modify the IPsec-related parameters.

IPsec negotiation ● IKEPEER
● ACLRULE

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

Table 1-194 and Table 1-195 describe the reconfiguration scheme using MML
commands.
● Endpoint mode

Table 1-194 Reconfiguration schemes for changing a device IP address (MML

commands, in endpoint mode)
If... Then...

- Add a device IP address by running the

following command:
ADD DEVIP

The new and old device IP Modify the services that use the device
addresses are not on the same IP address by running the following
network segment command:
ADD VLANMAPa

The device IP address is used for Modify the services that use the device
an IP route IP address by running the following
command:
ADD IPRT/ADD SRCIPRTb

The device IP address is used for Modify the services that use the device
an S1 link IP address by running the following
commands:
MOD SCTPHOSTc
MOD USERPLANEHOST

The device IP address is used for Modify the services that use the device
an X2 link IP address by running the following
commands:
MOD SCTPHOST
MOD USERPLANEHOST

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 576

eRAN
Reconfiguration Guide
If...
The device IP address is used for
the OMCH
The device IP address is used for
an IP clock link
A link that uses the device IP
address supports BFD
The device IP address is used for
IP PM sessions
The device IP address is used for
TWAMP
The device IP address is used for
IPsec negotiation
The device IP address is used for
an IP route
The new and old device IP
addresses are not on the same
network segment
- Remove the device IP address by
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
Modify the services that use the device
IP address by running the following
command and change the NE's IP
address on the MAE-Access:
MOD OMCH
Modify the services that use the device
IP address by running the following
commands:
RMV IPCLKLINK
ADD IPCLKLINK
Modify the services that use the device
IP address by running the following
command:
MOD BFDSESSION
Modify the services that use the device
IP address by running the following
commands:
RMV IPPMSESSION
ADD IPPMSESSION
Modify the services that use the device
IP address by running the following
commands:
MOD TWAMPCLIENT
MOD TWAMPRESPONDER
Modify the services that use the device
IP address by running the following
commands:
MOD IKEPEER
MOD ACLRULE
Remove the MOs that reference the
device IP address by running the
following command:
RMV IPRT/RMV SRCIPRTb
Remove the MOs that reference the
device IP address by running the
following command:
RMV VLANMAP
running the following command:
RMV DEVIP
577
eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

a: After running the command, you must perform a connectivity test for the
next-hop gateway. You can perform the next step only after the connectivity
test is passed.
b: To simplify configurations when one device IP address maps multiple
destination IP addresses, you are advised to configure the source IP route.
c: In endpoint mode, an S1 interface is automatically set up after its peer is
manually configured. In addition, if the slot number of the board where the
local IP address is located changes after the SCTPHOST MO is modified, the
eNodeB automatically removes and then sets up an S1 interface. If S1
Configuration Type in an MmeCapInfo MO is set to S1INTERFACE_CFG
and the S1 interface associated with S1 Interface ID in the MmeCapInfo
MO is automatically removed and then set up, the MmeCapInfo MO
corresponding to the S1 interface is also removed. As a result, the new S1
interface is not associated with any MmeCapInfo MO. In this case, you
need to reconfigure and associate the new S1 interface with the
MmeCapInfo MO.

● Link mode

Table 1-195 Reconfiguration schemes for changing a device IP address (MML

commands, in link mode)
If... Then...

- Add a device IP address by running the

following command:
ADD DEVIP

The new and old device IP Modify the services that use the device
addresses are not on the same IP address by running the following
network segment command:
ADD VLANMAPa

The device IP address is used for Modify the services that use the device
an IP route IP address by running the following
command:
ADD IPRT/ADD SRCIPRTb

The device IP address is used for Modify the services that use the device
an S1 link IP address by running the following
commands:
MOD SCTPLNK
MOD IPPATH

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 578

eRAN
Reconfiguration Guide
If...
The device IP address is used for
an X2 link
The device IP address is used for
the OMCH
The device IP address is used for
an IP clock link
A link that uses the device IP
address supports BFD
The device IP address is used for
IP PM sessions
The device IP address is used for
TWAMP
The device IP address is used for
IPsec negotiation
The device IP address is used for
an IP route
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
Modify the services that use the device
IP address by running the following
commands:
MOD SCTPLNK
MOD IPPATH
Modify the services that use the device
IP address by running the following
command and change the NE's IP
address on the MAE-Access:
MOD OMCH
Modify the services that use the device
IP address by running the following
commands:
RMV IPCLKLINK
ADD IPCLKLINK
Modify the services that use the device
IP address by running the following
command:
MOD BFDSESSION
Modify the services that use the device
IP address by running the following
commands:
RMV IPPMSESSION
ADD IPPMSESSION
Modify the services that use the device
IP address by running the following
commands:
MOD TWAMPCLIENT
MOD TWAMPRESPONDER
Modify the services that use the device
IP address by running the following
commands:
MOD IKEPEER
MOD ACLRULE
Remove the MOs that reference the
device IP address by running the
following command:
RMV IPRT/RMV SRCIPRTb
579
eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The new and old device IP Remove the MOs that reference the
addresses are not on the same device IP address by running the
network segment following command:
RMV VLANMAP

- Remove the device IP address by

running the following command:
RMV DEVIP

a: After running the command, you must perform a connectivity test for the
next-hop gateway. You can perform the next step only after the connectivity
test is passed.
b: To simplify configurations when one device IP address maps multiple
destination IP addresses, you are advised to configure the source IP route.

Topology Change
N/A

1.8.7.2 Engineering Preparation

This section describes the engineering preparation for changing a device IP
address, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Information Collection
Table 1-196 describes the information to be collected for data preparation.

Table 1-196 Information to be collected

Information Description

Base station Base station identification (BS ID).

information

Device IP address ● New device IP address and subnet mask

information ● Next-hop IP address
● Next-hop VLAN mapping

Hardware Preparation
N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 580

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Data to be prepared is listed in the following tables.
● MAE-Deployment, in endpoint mode

Table 1-197 Data preparation for changing a device IP address (MAE-

Deployment, in endpoint mode)

SN Ope MO Configuration Reference

rati
on

1 Mod DEVIP Change IP Address and Mask to their

ify target values.

2 Mod IPRT/SRCIPRTa ● For IPRT, change Next Hop IP to

ify the IP address of the gateway for
the new device IP address.
● For SRCIPRT, change Source IP
Address to the new device IP
address and Next Hop IP to the IP
address of the gateway for the new
device IP address.

3 Mod VLANMAP Change Next Hop IP to the IP address

ify of the gateway for the new device IP
address.

4 Mod SCTPHOST Change First Local IP Address or

ify Second Local IP Address to the
target value.

5 Mod USERPLANEHOST Change Local IP Address to the

ify target value.

6 Mod IPPATH If an IP path has been configured,

ify change Local IP address to the target
value.

7 Mod OMCH Change Local IP and Local Mask to

ify their target values.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 581

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

rati
on

8 Mod IPCLKLNK Change Client IPv4 to the target

ify value.

9 Mod BFDSESSION Change Source IP to the target value.

ify

10 Mod IKEPEER Change Local IP Address to the

ify target value.

11 Mod ACLRULE Change Source IP to the target value.

ify

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

● MAE-Deployment, in link mode

Table 1-198 Data preparation for changing a device IP address (MAE-

Deployment, in link mode)
SN Ope MO Configuration Reference
rati
on

1 Mod DEVIP Change IP Address and Mask to their

ify target values.

2 Mod IPRT/SRCIPRTa ● For IPRT, change Next Hop IP to

ify the IP address of the gateway for
the new device IP address.
● For SRCIPRT, change Source IP
Address to the new device IP
address and Next Hop IP to the IP
address of the gateway for the new
device IP address.

3 Mod VLANMAP Change Next Hop IP to the IP address

ify of the gateway for the new device IP
address.

4 Mod SCTPHOST Change First Local IP Address or

ify Second Local IP Address to the
target value.

5 Mod IPPATH Change Local IP Address to the

ify target value.

6 Mod OMCH Change Local IP and Local Mask to

ify their target values.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 582

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

rati
on

7 Mod IPCLKLNK Change Client IPv4 to the target

ify value.

8 Mod BFDSESSION Change Source IP to the target value.

ify

9 Mod IKEPEER Change Local IP Address to the

ify target value.

10 Mod ACLRULE Change Source IP to the target value.

ify

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

● MML commands, in endpoint mode

Table 1-199 Data preparation for changing a device IP address (MML

commands, in endpoint mode)
S Operati Operat MML Command Configuration
N on Type ion Reference

1 Add a Run ADD DEVIP Change the referenced

new the device IP address to the
device MML new device IP address
IP comma and retain other data
address. nd unchanged.

2 Modify Run ADD VLANMAP

the the ADD IPRT/ADD
services MML SRCIPRTa
that use comma
the nd MOD SCTPHOST
device MOD
IP USERPLANEHOST
address. MOD OMCH
RMV IPCLKLINK
ADD IPCLKLINK
MOD BFDSESSION
RMV IPPMSESSION
ADD IPPMSESSION
MOD TWAMPCLIENT
MOD
TWAMPRESPONDER

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 583

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

S Operati Operat MML Command Configuration

N on Type ion Reference

3 Modify Run MOD IKEPEER Change Local IP Address

the IKE the to the new device IP
peer MML address.
and ACL comma
rule. nd MOD ACLRULE Change Source IP
Address or Destination
IP Address to the new
device IP address.

4 Remove Run RMV IPRT/RMV If the device IP address is

the the SRCIPRT used for an IP route,
MOs MML remove the MOs that
that comma reference the device IP
referenc nd address.
e the
device RMV VLANMAP If the new and old device
IP IP addresses are not on
address. the same network
segment, remove the
MOs that reference the
device IP address.

5 Remove Run RMV DEVIP Remove the old device IP

the old the address.
device MML
IP comma
address. nd

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

● MML commands, in link mode

Table 1-200 Data preparation for changing a device IP address (MML

commands, in link mode)
S Operati Operat MML Command Configuration
N on Type ion Reference

1 Add a Run ADD DEVIP Change the referenced

new the device IP address to the
device MML new device IP address
IP comma and retain other data
address. nd unchanged.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 584

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

S Operati Operat MML Command Configuration

N on Type ion Reference

2 Modify Run ADD VLANMAP

the the ADD IPRT/ADD
services MML SRCIPRTa
that use comma
the nd MOD SCTPLNK
device MOD IPPATH
IP MOD OMCH
address.
RMV IPCLKLINK
ADD IPCLKLINK
MOD BFDSESSION
RMV IPPMSESSION
ADD IPPMSESSION
MOD TWAMPCLIENT
MOD
TWAMPRESPONDER

3 Modify Run MOD IKEPEER Change Local IP Address

the IKE the to the new device IP
peer MML address.
and ACL comma
rule. nd MOD ACLRULE Change Source IP
Address or Destination
IP Address to the new
device IP address.

4 Remove Run RMV IPRT/RMV If the device IP address is

the the SRCIPRT used for an IP route,
MOs MML remove the MOs that
that comma reference the device IP
referenc nd address.
e the
device RMV VLANMAP If the new and old device
IP IP addresses are not on
address. the same network
segment, remove the
MOs that reference the
device IP address.

5 Remove Run RMV DEVIP Remove the old device IP

the old the address.
device MML
IP comma
address. nd

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 585

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

The recommended reconfiguration methods are as follows:
● If the device IP address to be changed is not the OM IP address, using the
MAE-Deployment for batch reconfiguration is recommended.
● If the device IP address to be changed is used for the X2 interface and it is
expected that the reference to this IP address at the peer base station can be
automatically updated, using the MAE-Deployment for batch reconfiguration
is recommended.
● If the device IP address to be changed is the OM IP address, the MAE-Access
and MAE-Deployment will be disconnected from the NE during data delivery
and activation. As a result, the incremental scripts cannot be executed on the
MAE-Deployment. In this case, the reconfiguration using MML commands is
recommended.
Prepare data for each reconfiguration method as follows:
NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Changing a Device IP Address"). For details, see
the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

● Endpoint mode
In the following example, the device IP address needs to be changed from
192.168.7.186 to 192.168.7.166 and the address is referenced by the MOs
SCTPHOST, USERPLANEHOST, OMCH, IPRT, and IPCLKLNK.
If OMCH parameters are modified by mistake, the OMCH may be
disconnected and cannot be restored within a long period of time. To avoid
service unavailability due to the OMCH disconnection, you are advised to turn
on the automatic rollback switch of the CB by running the CFM CB command
before configuring data. For example, CFM CB: MODE=UNFORCED,
NAME="CB1", COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Adding a device IP address*/
ADD DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, IP="192.168.7.166",
MASK="255.255.252.0";
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD VLANMAP: NEXTHOPIP="192.168.7.1", MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
VLANID=101, SETPRIO=DISABLE;
/*Adding an IP route*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 586

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*If multiple IP routes are associated with the device IP address, add all the associated IP routes.*/
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="172.169.1.5", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.7.1", MTUSWITCH=OFF;
/*Modifying an SCTP host*/
MOD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="192.168.7.166";
/*Modifying a user-plane host*/
MOD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.7.166";
/*Modifying an OM channel*/
MOD OMCH: FLAG=MASTER, IP="192.168.7.166";
/*Modifying an IP clock link*/
RMV IPCLKLINK:;
/*Adding an IP clock link*/
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, CIP="192.168.7.166", SIP="192.168.49.249",
PROFILETYPE=1588V2;
/*Modifying a BFD session*/
MOD BFDSESSION: SN=7, BFDSN=0, SRCIP="192.168.7.166";
/*Removing an IP PM session*/
RMV IPPMSESSION: IPPMSN=0;
ADD IPPMSESSION: IPPMSN=0, IPPMTYPE=THREE_TUPLE, BINDPATH=NO, LOCALIP="192.168.7.166",
PEERIP="192.168.1.166";
/*Modifying the TWAMP configuration*/
MOD TWAMPCLIENT: CLIENTID=0, LOCALIP="192.168.1.166";
MOD TWAMPRESPONDER: RESPONDERID=0, LOCALIP="192.168.1.166";
/*If the IP address to be changed is used for IPsec negotiations, perform the following steps:*/
/*Changing the local IP address of the IKE peer to the new device IP address*/
MOD IKEPEER: PEERNAME="ike", LOCALIP="192.168.7.166";
/*If the device IP address is the Source IP Address in the ACLRULE MO referenced by the IPSECBIND
MO, perform the following steps: */
/*All ACLRULE MOs that meet the preceding conditions need to be modified.*/
/*Modifying the ACL rules by changing the Source IP Address or Destination IP Address that references
this IP address to the new device address*/
MOD ACLRULE: ACLID=3000, RULEID=1, SIP="192.168.7.166";
MOD ACLRULE: ACLID=3100, RULEID=1, DIP="192.168.7.166";
/*Removing the IP route*/
/*If multiple IP routes are associated with the device IP address, remove all the associated IP routes.
To query the IP routes associated with the device IP address, run the DSP IPRT command.*/
RMV IPRT: RTIDX=0;
/*Removing a next-hop VLAN mapping relationship with the next-hop IP address of the VLAN
mapping being 192.168.0.1 and the subnet mask being 255.255.255.255*/
RMV VLANMAP: NEXTHOPIP="192.168.0.1", MASK="255.255.255.255";
/*Removing the device IP address*/
RMV DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.7.186";
● Link mode
In the following example, the device IP address needs to be changed from
192.168.7.186 to 192.168.7.166 and the address is referenced by the MOs
IPPATH, SCTPLNK, OMCH, IPRT, and IPCLKLNK.
If OMCH parameters are modified by mistake, the OMCH may be
disconnected and cannot be restored within a long period of time. To avoid
service unavailability due to the OMCH disconnection, you are advised to turn
on the automatic rollback switch of the CB by running the CFM CB command
before configuring data. For example, CFM CB: MODE=UNFORCED,
NAME="CB1", COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Adding a device IP address*/
ADD DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, IP="192.168.7.166",
MASK="255.255.252.0";
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD VLANMAP: NEXTHOPIP="192.168.7.1", MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
VLANID=101, SETPRIO=DISABLE;
/*Adding an IP route*/
/*If multiple IP routes are associated with the device IP address, add all the associated IP routes.*/
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, SBT=BASE_BOARD, DSTIP="172.169.1.5",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="192.168.7.1", MTUSWITCH=OFF;
/*Modifying an SCTP link*/
MOD SCTPLNK: SCTPNO=0, LOCIP="192.168.7.166";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 587

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Modifying an IP path*/
MOD IPPATH: PATHID=0, SN=7, LOCALIP="192.168.7.166";
/*Modifying an OM channel*/
MOD OMCH: FLAG=MASTER, IP="192.168.7.166";
/*Modifying an IP clock link*/
RMV IPCLKLINK:;
/*Adding an IP clock link*/
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, CIP="192.168.7.166", SIP="192.168.49.249",
PROFILETYPE=1588V2;
/*Modifying a BFD session*/
MOD BFDSESSION: SN=7, BFDSN=0, SRCIP="192.168.7.166";
/*Removing an IP PM session*/
RMV IPPMSESSION:IPPMSN=0;
ADD IPPMSESSION: IPPMSN=0, IPPMTYPE=THREE_TUPLE, BINDPATH=NO, LOCALIP="192.168.7.166",
PEERIP="192.168.1.166";
/*Modifying the TWAMP configuration*/
MOD TWAMPCLIENT: CLIENTID=0, LOCALIP="192.168.1.166";
MOD TWAMPRESPONDER: RESPONDERID=0, LOCALIP="192.168.1.166";
/*If the IP address to be changed is used for IPsec negotiations, perform the following steps:*/
/*Changing the local IP address of the IKE peer to the new device IP address*/
MOD IKEPEER: PEERNAME="ike", LOCALIP="192.168.7.166";
/*If the device IP address is the Source IP Address in the ACLRULE MO referenced by the IPSECBIND
MO, perform the following steps: */
/*All ACLRULE MOs that meet the preceding conditions need to be modified.*/
/*Modifying the ACL rules by changing the Source IP Address or Destination IP Address that references
this IP address to the new device address*/
MOD ACLRULE: ACLID=3000, RULEID=1, SIP="192.168.7.166";
MOD ACLRULE: ACLID=3100, RULEID=1, DIP="192.168.7.166";
/*Removing the IP route*/
/*If multiple IP routes are associated with the device IP address, remove all the associated IP routes.
To query the IP routes associated with the device IP address, run the DSP IPRT command.*/
RMV IPRT: RTIDX=0;
/*Removing a next-hop VLAN mapping relationship with the next-hop IP address of the VLAN
mapping being 192.168.0.1 and the subnet mask being 255.255.255.255*/
RMV VLANMAP: NEXTHOPIP="192.168.0.1", MASK="255.255.255.255";
/*Removing the device IP address*/
RMV DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.7.186";

1.8.7.3 Engineering Implementation

This section describes the engineering implementation for changing a device IP
address, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
If the device IP address to be changed is the OM IP address, run MML
commands on the LMT to deliver the data to the base station and then
activate the data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 588

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the LMT to deliver the batch configuration script prepared according
to Engineering Preparation > Data Preparation to the base station and
activate the script on the base station. For details, see 1.3.2 Running
MML Commands on the LMT.
d. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
e. (Optional) If the device address is used for an OM channel, change the
OM IP address of the NE to the new IP address on the MAE-Access.
i. On the menu bar of the MAE-Access, choose Topology > Main
Topology.
ii. In the navigation tree on the left, select the eNodeB.
iii. In the right pane, right-click the eNodeB and choose Property from
the shortcut menu.
iv. In the displayed NE Properties dialog box, set IP Address 1 to the
new device IP address. Then, click OK.
● Remote Operations
If the device IP address to be changed is not the OM IP address, use the MAE-
Deployment to deliver the data to the base station and activate the data.
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Select a proper method to modify device IP addresses according to the
following table:

If... Then...

S1 needs to be configured in Perform c.

endpoint mode

X2 needs to be configured in Perform d.

endpoint mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 589

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

eX2 needs to be configured in Perform e.

endpoint mode

c. Run the LST GLOBALPROCSWITCH command to query the values of the

options of The Switch of S1-MME Configuration by SON parameter.

▪ If the values of the options are Off, skip this step.

▪ If the values of the options are On, run the MOD

GLOBALPROCSWITCH command with the options of The Switch of
S1-MME Configuration by SON deselected. Example: MOD
GLOBALPROCSWITCH:
S1MMESonSwitch=S1MMESonSetupSwitch-0&S1MMESonDeleteS
witch-0;
d. Run the LST GLOBALPROCSWITCH command to query the settings of
The Switch of X2 setup by SON, Peer Request Based X2 Delete Switch,
and The Timer of X2 delete by SON(min) and check whether the
options of X2 SON Delete Switch are selected.

▪ If The Timer of X2 delete by SON(min) is 0 and all the values of

the other preceding parameters or options are OFF or deselected,
skip this step.

▪ If The Timer of X2 delete by SON(min) is not 0 or any of the other

preceding parameters or options is ON or selected, run the MOD
GLOBALPROCSWITCH command with The Timer of X2 delete by
SON(min) set to 0, all the values set to OFF, and all options
deselected. Example: MOD GLOBALPROCSWITCH:
X2SonSetupSwitch=OFF, X2SonDeleteTimer=0,
PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2USAGE
_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-0;
e. Run the LST GLOBALPROCSWITCH command to check whether the
options of eX2 Auto Delete Switch and eX2 Auto Setup Switch are
selected.

▪ If all the options are deselected, skip this step.

▪ If any option is selected, run the MOD GLOBALPROCSWITCH

command with all options of these two parameters deselected.
Example: MOD GLOBALPROCSWITCH:
eX2AutoDeleteSwitch=BASED_ON_EX2FAULT-0,
eX2AutoSetupSwitch=BASED_ON_EX2_IDEAL_MODE-0&BASED_O
N_EX2_NON_IDEAL_MODE-0;
f. Deliver the configuration data to the eNodeB and activate the data. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
g. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 590

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

h. Restore the settings of the switches changed in c, d, or e.

----End

1.8.7.4 Engineering Verification

This section describes how to verify the reconfiguration for changing a device IP
address.

Procedure
Step 1 Verify that no related alarm is reported.

For example:

● ALM-25886 IP Path Fault

● ALM-25901 Remote Maintenance Link Failure
● ALM-25888 SCTP Link Fault
● ALM-26263 IP Clock Link Failure
● ALM-26266 Time Synchronization Failure
● ALM-25899 BFD Session Fault
● ALM-25891 IKE Negotiation Failure
● ALM-29201 S1 Interface Fault
● ALM-29204 X2 Interface Fault

If any alarm is reported, clear the alarm according to the instructions in 3900 &
5900 Series Base Station Alarm Reference.

Step 2 Run the LST DEVIP command. Verify that IP Address and Mask are the same as
planned.

If the values of IP Address and Mask are inconsistent with the plan, view the
modified configuration data file to check whether they are consistent with the
plan.

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.8.7.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 591

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Context
If the changed device IP address is for remote maintenance, a rollback cannot be
performed. The rollback of a device IP address that is not used for remote
maintenance is as follows:

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.8.7.4

Engineering Verification.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 592

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.8 Changing the IPv4/IPv6 Address (New Model)

This section describes how to change an IPv4/IPv6 address (new model).

NOTE

This task is applicable only when the TRANSCFGMODE parameter in the GTRANSPARA MO is
set to NEW.

1.8.8.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing an IPv4/IPv6 address.

Application Scenario
The previous IPv4/IPv6 address plan is inappropriate and a new plan is required.

Reconfiguration Impact
● If the IPv4/IPv6 address to be changed is the OM IP address, the MAE-Access
and MAE-Deployment will be disconnected from the NE after the old OM
channel becomes invalid and before the new OM channel is set up.
● If the IPv4/IPv6 address to be changed is used for service transmission, the
service link (for example, an S1 or X2 link) using this IP address will be
reestablished. During the reestablishment, services on the link will be
interrupted.
● If the IPv4/IPv6 address to be changed is used for IPsec negotiations, an IPsec
renegotiation is required. During the renegotiation, services on the IPsec
tunnel will be interrupted.
● If related IP information is not completely modified on other NEs and the to-
be-reconstructed base station when you change the IPv4/IPv6 address,
services will become unavailable for use.

Reconfiguration Scheme
The following information describes how to reconfigure the IPv4/IPv6 address for
a multimode base station (MBTS).
● If the IP address to be changed is shared by all RATs in a co-MPT MBTS, such
as the OM IP address, the IP Address in the DEVIP MO needs to be modified
only once. After the IP address is changed, the MOs that reference this IP
address must be modified on the base station side, including the OMCH,
IPPATH, SCTPLNK, USERPLANEHOST, and SCTPHOST. In addition, the IP
address must be changed to the new one on the peer devices, such as the
MAE-Access, base station controller, and MME/S-GW.
● The method of changing the IPv4/IPv6 address for the separate-MPT MBTS is
the same as that for a single-mode base station. When IP co-transmission is
adopted:
– If the IP address is changed on the RAT that does not provide
transmission, the route from the RAT that provides transmission to the
RAT that does not provide transmission needs to be changed. That is,
change the "Destination IP Address" to the new IP address.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 593

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– If co-transmission through panel interconnection is adopted and the IP

address of the interconnected port providing transmission is changed, the
route from the RAT that provides transmission to the peer RAT needs to
be changed, that is, change the "Next Hop IP Address" to the new IP
address.
NOTE

● For details about how to change IP addresses for GSM, see GBSS Reconfiguration Guide for
BSC6900.
● For details about how to change IP addresses for UMTS, see RAN Reconfiguration Guide for
BSC6900.
● For details about how to change IP addresses for LTE, see this section. You must also modify
related IP information on other NEs and the to-be-reconstructed base station when changing
the IP address.

The reconfiguration schemes using the MAE-Deployment and using MML

commands are different because you cannot directly change an IPv4/IPv6 address
using MML commands.
NOTE

● If the IPv4/IPv6 address to be changed is an OM IP address, set the OM IP address to the

new IPv4/IPv6 address for the eNodeB on the MAE-Access after the eNodeB reconfiguration.
● If the IPv4/IPv6 address is used for X2 links and the value of the SCTP Peer ID parameter in
the SCTPPEER MO is the same as the peer base station ID, use the MAE-Deployment to
perform batch reconfiguration to automatically update the IPv4/IPv6 address referenced by
the peer base stations. No manual operation is required.

IPv4/IPv6 addresses share associations and configuration restrictions with many

MOs. If the IPv4/IPv6 address is changed, these MOs must also be modified. The
following figure shows the associations and restrictions between these MOs.

Figure 1-108 MOs related to the IPADDR4 MO (IPv4)

MOs highlighted in blue They reference the IPADDR4 MO.

MOs highlighted in green They share configuration restrictions with the

IPADDR4 MO.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 594

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

MOs highlighted in gray They share both reference relationships and

configuration restrictions with the IPADDR4
MO.

One-way arrows They indicate association relationships.

Figure 1-109 MOs related to the IPADDR6 MO (IPv6)

MOs highlighted in blue They reference the IPADDR6 MO.

MOs highlighted in green They share configuration restrictions with the

IPADDR6 MO.

One-way arrows They indicate association relationships.

When the MAE-Deployment is used, change the corresponding parameters in

the MOs listed in Table 1-201 and Table 1-202 to the new IP address.
● Endpoint mode

Table 1-201 Reconfiguration scheme for changing an IPv4/IPv6 address

(MAE-Deployment, in endpoint mode)
If... Then...

A new VLAN is required Plan a new VLAN.

INTERFACE

- Change the IPv4/IPv6 address.

IPv4: IPADDR4
IPv6: IPADDR6

The IPv4/IPv6 address is used for
an IP route and the new IP
address is not on the same
network segment as the original
IP address
Change the next-hop IP address of the
IP route to the new gateway IP address.
IPv4: IPROUTE4/SRCIPROUTE4a
IPv6: IPROUTE6

The IPv4/IPv6 address is used for Change the next-hop IP address in the
an IP route and the new IP VLANMAP MO to the new gateway IP
address is not on the same address.
network segment as the original IPv4: VLANMAP
IP address
IPv6: N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 595

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The IPv4/IPv6 address is used for Modify the S1-link-related parameters.

an S1 link ● SCTPHOSTb
● USERPLANEHOST

The IPv4/IPv6 address is used for Modify the X2-link-related parameters.

an X2 link ● SCTPHOST
● USERPLANEHOST

An IP path has been configured Modify the information about the IP

path.
IPPATH

The IPv4/IPv6 address is used for Modify the OMCH.

the OMCH OMCH

The IPv4/IPv6 address is used for Modify the IP clock link.

an IP clock link IPCLKLNK

A link that uses the IPv4 address Modify the BFD.

supports BFD IPv4: BFD
IPv6: N/A

The IPv4/IPv6 address is used for Modify the IPsec-related parameters.

IPsec negotiation ● IKEPEER
● ACLRULE (IPv4)/ACLRULE6 (IPv6)

a: To simplify configurations when one IPv4 address maps multiple

destination IP addresses, you are advised to configure the source IPv4 route.
b: In endpoint mode, an S1 interface is automatically set up after its peer is
manually configured. In addition, if the slot number of the board where the
local IP address is located changes after the SCTPHOST MO is modified, the
eNodeB automatically removes and then sets up an S1 interface. If S1
Configuration Type in an MmeCapInfo MO is set to S1INTERFACE_CFG
and the S1 interface associated with S1 Interface ID in the MmeCapInfo
MO is automatically removed and then set up, the MmeCapInfo MO
corresponding to the S1 interface is also removed. As a result, the new S1
interface is not associated with any MmeCapInfo MO. In this case, you
need to reconfigure and associate the new S1 interface with the
MmeCapInfo MO.

● Link mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 596

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-202 Reconfiguration schemes for changing an IPv4 address (MAE-

Deployment, in link mode)
If... Then...

- Change the IPv4 address.

IPADDR4

The IPv4 address is used for an
IP route and the new IP address
is not on the same network
segment as the original IP
address
Change the next-hop IP address of the
IP route to the new gateway IP address.
IPROUTE4/SRCIPROUTE4a

The IPv4 address is used for an
IP route and the new IP address
is not on the same network
segment as the original IP
address
Change the next-hop IP address in the
VLANMAP MO to the new gateway IP
address.
VLANMAP

The IPv4 address is used for an Modify the S1-link-related parameters.

S1 link ● SCTPLNK
● IP Path

The IPv4 address is used for an Modify the X2-link-related parameters.

X2 link ● SCTPLNK
● IPPATH

The IPv4 address is used for the Modify the OMCH.

OMCH OMCH

The IPv4 address is used for an Modify the IP clock link.

IP clock link IPCLKLNK

A link that uses the IPv4 address Modify the BFD.

supports BFD BFD

The IPv4 address is used for Modify the IPsec-related parameters.

IPsec negotiation ● IKEPEER
● ACLRULE

a: To simplify configurations when one IPv4 address maps multiple

destination IP addresses, you are advised to configure the source IPv4 route.

Table 1-203 and Table 1-204 describe the reconfiguration scheme using MML
commands.
● Endpoint mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 597

eRAN
Reconfiguration Guide
Table 1-203 Reconfiguration schemes for changing an IPv4/IPv6 address
(MML commands, in endpoint mode)
If...
- Add an IPv4/IPv6 address by running the
The new and old device IP
addresses are not on the same
network segment
The IPv4/IPv6 address is used for
an IP route
The IPv4/IPv6 address is used for
an S1 link
The IPv4/IPv6 address is used for
an X2 link
The IPv4/IPv6 address is used for
the OMCH
The IPv4/IPv6 address is used for
an IP clock link
A link that uses the IPv4 address
supports BFD
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
following command:
IPv4: ADD IPADDR4
IPv6: ADD IPADDR6
Modify the services that use the IPv4/
IPv6 address by running the following
command:
ADD VLANMAP/ADD INTERFACEa
Modify the services that use the IPv4/
IPv6 address by running the following
command:
IPv4: ADD IPROUTE4/ADD
SRCIPROUTE4b
IPv6: ADD IPROUTE6
Modify the services that use the IPv4/
IPv6 address by running the following
commands:
MOD SCTPHOSTc
MOD USERPLANEHOST
Modify the services that use the IPv4/
IPv6 address by running the following
commands:
MOD SCTPHOST
MOD USERPLANEHOST
Modify the services that use the IPv4/
IPv6 address by running the following
command and change the NE's IP
address on the MAE-Access
MOD OMCH
Modify the services that use the IPv4/
IPv6 address by running the following
commands:
RMV IPCLKLINK
ADD IPCLKLINK
Modify the services that use the IPv4/
IPv6 address by running the following
command:
IPv4: MOD BFD
IPv6: N/A
598
eRAN
Reconfiguration Guide
If...
The IPv4 address is used for an
IP PM session
The IPv4 address is used for
TWAMP
The IPv4/IPv6 address is used for
IPsec negotiation
The IPv4/IPv6 address is used for
an IP route
The new and old device IP
addresses are not on the same
network segment
- Remove the IPv4/IPv6 address by
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
Modify the services that use the IPv4/
IPv6 address by running the following
commands:
IPv4:
RMV IPPMSESSION
ADD IPPMSESSION
IPv6: N/A
Modify the services that use the IPv4/
IPv6 address by running the following
commands:
IPv4:
MOD TWAMPCLIENT
MOD TWAMPRESPONDER
IPv6: N/A
Modify the services that use the IPv4/
IPv6 address by running the following
command:
IPv4/IPv6: MOD IKEPEER
IPv4: MOD ACLRULE
IPv6: MOD ACLRULE6
Remove the MOs that reference the
IPv4/IPv6 address by running the
following command:
IPv4: RMV IPROUTE4/RMV
SRCIPROUTE4b
IPv6: RMV IPROUTE6
Remove the MOs that reference the
IPv4/IPv6 address by running the
following command:
IPv4: RMV VLANMAP
IPv6: N/A
running the following command:
IPv4: RMV IPADDR4/RMV INTERFACE
IPv6: RMV IPADDR6/RMV INTERFACE
599
eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

a: After running the command, you must perform a connectivity test for the
next-hop gateway. You can perform the next step only after the connectivity
test is passed. Only the ADD INTERFACE command is available for use for
IPv6 transmission and dual stack transmission.
b: To simplify configurations when one IPv4 address maps multiple
destination IP addresses, you are advised to configure the source IPv4 route.
c: In endpoint mode, an S1 interface is automatically set up after its peer is
manually configured. In addition, if the slot number of the board where the
local IP address is located changes after the SCTPHOST MO is modified, the
eNodeB automatically removes and then sets up an S1 interface. If S1
Configuration Type in an MmeCapInfo MO is set to S1INTERFACE_CFG
and the S1 interface associated with S1 Interface ID in the MmeCapInfo
MO is automatically removed and then set up, the MmeCapInfo MO
corresponding to the S1 interface is also removed. As a result, the new S1
interface is not associated with any MmeCapInfo MO. In this case, you
need to reconfigure and associate the new S1 interface with the
MmeCapInfo MO.

● Link mode

Table 1-204 Reconfiguration scheme for changing an IPv4 address (MML

commands, in link mode)
If... Then...

- Add an IPv4 address by running the

following command:
ADD IPADDR4

The new and old device IP Modify the services that use the IPv4
addresses are not on the same address by running the following
network segment command:
ADD VLANMAP/ADD INTERFACEa

The IPv4 address is used for an Modify the services that use the IPv4
IPv4 route address by running the following
command:
ADD IPROUTE4/ADD SRCIPROUTE4b

The IPv4 address is used for an Modify the services that use the IPv4
S1 link address by running the following
commands:
MOD SCTPLNK
MOD IPPATH

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 600

eRAN
Reconfiguration Guide
If...
The IPv4 address is used for an
X2 link
The IPv4 address is used for the
OMCH
The IPv4 address is used for an
IP clock link
A link that uses the IPv4 address
supports BFD
The IPv4 address is used for an
IP PM session
The IPv4 address is used for
TWAMP
The IPv4 address is used for
IPsec negotiation
The IPv4 address is used for an
IP route
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
Modify the services that use the IPv4
address by running the following
commands:
MOD SCTPLNK
MOD IPPATH
Modify the services that use the IPv4
address by running the following
command and change the NE's IP
address on the MAE-Access:
MOD OMCH
Modify the services that use the IPv4
address by running the following
commands:
RMV IPCLKLINK
ADD IPCLKLINK
Modify the services that use the IPv4
address by running the following
command:
MOD BFD
Modify the services that use the IPv4
address by running the following
commands:
RMV IPPMSESSION
ADD IPPMSESSION
Modify the services that use the IPv4
address by running the following
commands:
MOD TWAMPCLIENT
MOD TWAMPRESPONDER
Modify the services that use the IPv4
address by running the following
commands:
MOD IKEPEER
MOD ACLRULE
Remove the MOs that reference the IPv4
address by running the following
command:
RMV IPROUTE4/RMV SRCIPROUTE4
601
eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The new and old device IP Remove the MOs that reference the IPv4
addresses are not on the same address by running the following
network segment command:
RMV VLANMAP

- Remove the IPv4 address by running the

following command:
RMV IPADDR4/RMV INTERFACE

a: After running the command, you must perform a connectivity test for the
next-hop gateway. You can perform the next step only after the connectivity
test is passed. Only the ADD INTERFACE command is available for use for
IPv6 transmission and dual stack transmission.
b: To simplify configurations when one IPv4 address maps multiple
destination IP addresses, you are advised to configure the source IPv4 route.

Topology Change
N/A

1.8.8.2 Engineering Preparation

This section describes the engineering preparation for changing an IPv4/IPv6
address, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Information Collection
Table 1-205 describes the information to be collected for data preparation.

Table 1-205 Information to be collected

Information Description

Base station Base station identification (BS ID).

information

IPv4/IPv6 address ● New IPv4 address and its subnet mask

information ● New IPv6 address and its prefix length
● Interface and VLAN to which the new IPv4/IPv6
address belongs
● Next-hop IP address
● VLANMAP

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 602

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Data to be prepared is listed in the following tables.
● MAE-Deployment, in endpoint mode

Table 1-206 Data preparation for changing an IPv4/IPv6 address (MAE-

Deployment, in endpoint mode)

SN Ope MO Configuration Reference

rati
on

1 Mod IPv4: ETHPORT/ Optional:

ify INTERFACE Change Port ID in the ETHPORT MO
IPv6: INTERFACE to the target value.
Create a new INTERFACE MO.

2 Mod IPv4: IPADDR4 Change IP Address and Mask (IPv4)/

ify IPv6: IPADDR6 Prefix Length (IPv6) to the target
values.

3 Mod IPv4: IPROUTE4/ Change Next Hop IP to the IP address

ify SRCIPROUTE4a of the gateway for the new IPv4/IPv6
IPv6: IPROUTE6 address.

4 Mod IPv4: (optional) Change Next Hop IP to the IP address

ify VLANMAP of the gateway for the new IPv4
IPv6: N/A address.

5 Mod SCTPHOST Change First Local IP Address or

ify Second Local IP Address to the
target value.

6 Mod USERPLANEHOST Change Local IP Address to the

ify target value.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 603

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

rati
on

7 Mod IP Path If an IP path has been configured,

ify change Local IP address to the target
value.

8 Mod OMCH Change Local IP/Local IPv6 Address

ify and Local Mask (IPv4) to the target
values.

9 Mod IPCLKLNK Change Client IPv4/Client IPv6 to the

ify target value.

10 Mod IPv4: BFD Change Source IP to the target value.

ify IPv6: N/A

11 Mod IPv4: IPPMSESSION Change LOCALIP to the target value.

ify IPv6: N/A

12 Mod IPv4: TWAMPCLIENT

ify IPv6: N/A

13 Mod IPv4:
ify TWAMPRESPONDER
IPv6: N/A

14 Mod IKEPEER Change LOCALIP to the target value.

ify

15 Mod IPv4: ACLRULE Change Source IP Address to the

ify IPv6: ACLRULE6 target value.

a: To simplify configurations when one IPv4 address maps multiple

destination IP addresses, you are advised to configure the source IPv4 route.

● MAE-Deployment, in link mode

Table 1-207 Data preparation for changing an IPv4 address (MAE-

Deployment, in link mode)

SN Opera MO Configuration Reference

tion

1 Modify IPADDR4 Change IP Address and Mask to

their target values.

2 Modify IPROUTE4/ Change Next Hop IP to the IP

SRCIPROUTE4a address of the gateway for the new
IPv4 address.
3 Modify VLANMAP

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 604

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Opera MO Configuration Reference

tion

4 Modify SCTPLNK Change First Local IP Address or

Second Local IP Address to the
target value.

5 Modify IP Path Change Local IP Address to the

target value.

6 Modify OMCH If an IP path has been configured,

change Local IP to the target value.

7 Modify IPCLKLNK Change Client IPv4 to the target

value.

8 Modify BFD Change Client IPv4 to the target

value.

9 Modify IKEPEER Change Source IP to the target

value.

10 Modify ACLRULE Change Source IP to the target

value.

a: To simplify configurations when one IPv4 address maps multiple

destination IP addresses, you are advised to configure the source IPv4 route.

● MML commands, in endpoint mode

Table 1-208 Data preparation for changing an IPv4/IPv6 address (MML

commands, in endpoint mode)
SN Opera Opera MML Command Configuration Reference
tion tion
Type

1 Add a Runni IPv4: ADD Add a new VLAN.

VLAN. ng VLANMAP/ADD
MML INTERFACE
comm IPv6: SET
ands ETHPORT/ADD
INTERFACE

2 Add Runni IPv4: ADD IPADDR4 Change the referenced

an ng IPv6: ADD IPADDR6 IPv4/IPv6 address to the
IPv4/ MML new IPv4/IPv6 address
IPv6 comm and retain other data
addres ands unchanged.
s.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 605

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Opera Opera MML Command Configuration Reference

tion tion
Type

3 Modif Runni IPv4:

y the ng ADD VLANMAP
servic MML
es comm ADD IPROUTE4/ADD
that ands SRCIPROUTE4a
use MOD SCTPHOST
the MOD
IPv4/ USERPLANEHOST
IPv6
addres MOD OMCH
s. RMV IPCLKLINK
ADD IPCLKLINK
MOD BFD
RMV IPPMSESSION
ADD IPPMSESSION
MOD TWAMPCLIENT
MOD
TWAMPRESPONDER
IPv6:
ADD IPROUTE6
MOD SCTPHOST
MOD
USERPLANEHOST
RMV IPCLKLINK
ADD IPCLKLINK

4 Modif Runni MOD IKEPEER Change the Local IP

y the ng Address to the new IPv4/
IKE MML IPv6 address.
peer comm
and ands IPv4: MOD ACLRULE Change the Source IP
ACL IPv6: MOD ACLRULE6 Address or Destination
rule. IP Address to the new
IPv4/IPv6 address.

5 Remo Runni IPv4: RMV If the IPv4/IPv6 address is

ve the ng IPROUTE4/RMV used by an IP route,
MOs MML SRCIPROUTE4a remove the route.
that comm IPv6: RMV IPROUTE6
refere ands
nce
the
IPv4/
IPv6

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 606

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Opera Opera MML Command Configuration Reference

tion tion
Type

addres IPv4: RMV VLANMAP If the new IP address is

s. IPv6: N/A not on the same network
segment as the old IP
address, remove the
VLANMAP MO.

6 Remo Runni IPv4: RMV IPADDR4 Remove the old IPv4/IPv6

ve the ng IPv6: RMV IPADDR6 address.
old MML
IPv4/ comm
IPv6 ands
addres
s.

7 Remo Runni IPv4: RMV INTERFACE If no IP address is

ve the ng IPv6: RMV INTERFACE configured on the
interfa MML interface where the old
ce. comm IPv4/IPv6 address resides,
ands remove this interface.

a: To simplify configurations when one IPv4 address maps multiple

destination IP addresses, you are advised to configure the source IPv4 route.

● MML commands, in link mode

Table 1-209 Data preparation for changing an IPv4 address (MML

commands, in link mode)
SN Operatio Oper MML Command Configuration
n Type ation Reference

1 Add an Runn ADD IPADDR4 Change the referenced

IPv4 ing IPv4 address to the new
address. MML IPv4 address and retain
com other data unchanged.
man
ds

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 607

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Operatio Oper MML Command Configuration

n Type ation Reference

2 Modify Runn ADD VLANMAP

the ing ADD IPROUTE4/ADD
services MML SRCIPROUTE4a
that use com
the IPv4 man MOD SCTPLNK
address. ds MOD IPPATH
MOD OMCH
RMV IPCLKLINK
ADD IPCLKLINK
MOD BFD
RMV IPPMSESSION
ADD IPPMSESSION
MOD TWAMPCLIENT
MOD
TWAMPRESPONDER

3 Modify Runn MOD IKEPEER Change Local IP

the IKE ing Address to the new
peer and MML IPv4 address.
ACL rule. com
man MOD ACLRULE Change Source IP
ds Address or Destination
IP Address to the new
IPv4 address.

4 Remove Runn ADD IPROUTE4/ADD If the IPv4 address is

the MOs ing SRCIPROUTE4a used by an IP route,
that MML remove the route.
reference com
the IPv4 man RMV VLANMAP If the new IP address is
address. ds not on the same
network segment as the
old IP address, remove
the VLANMAP MO.

5 Remove Runn RMV IPADDR4/RMV Remove the old IPv4

the old ing INTERFACE address.
IPv4 MML If no IP address is
address. com configured on the
man interface where the old
ds IPv4 address resides,
remove this interface.

a: To simplify configurations when one IPv4 address maps multiple

destination IP addresses, you are advised to configure the source IPv4 route.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 608

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

The recommended reconfiguration methods are as follows:
● If the IPv4/IPv6 address to be changed is not the OM IP address, using the
MAE-Deployment for batch reconfiguration is recommended.
● If the IPv4/IPv6 address to be changed is used for the X2 interface and it is
expected that the reference to this IPv4/IPv6 address at the peer base station
can be automatically updated, using the MAE-Deployment for batch
reconfiguration is recommended.
● If the IPv4/IPv6 address to be changed is the OM IP address, the MAE-Access
and MAE-Deployment will be disconnected from the NE during data delivery
and activation. As a result, the incremental scripts cannot be executed on the
MAE-Deployment. In this case, the reconfiguration using MML commands is
recommended.
Prepare data for each reconfiguration method as follows:
NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Changing a IPv4 Address"). For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

● Endpoint mode
In the following example, the IPv4 address needs to be changed from
192.168.7.186 to 192.168.7.166 and the new IPv4 address is referenced by
the MOs SCTPHOST, USERPLANEHOST, OMCH, IPRT, and IPCLKLNK.
If OMCH parameters are modified by mistake, the OMCH may be
disconnected and cannot be restored within a long period of time. To avoid
service unavailability due to the OMCH disconnection, you are advised to turn
on the automatic rollback switch of the CB by running the CFM CB command
before configuring data. For example, CFM CB: MODE=UNFORCED,
NAME="CB1", COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Setting Ethernet port 0*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD VLANMAP: NEXTHOPIP="192.168.7.1" , MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
VLANID=101, SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 609

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;

/*Adding an IPv4 address*/
ADD IPADDR4: ITFID=0, IP="192.168.7.166", MASK="255.255.252.0";
/*Adding an IP route*/
/*If multiple IP routes are associated with the IPv4 address, add all the associated IP routes.*/
ADD IPROUTE4: RTIDX=0, DSTIP="172.169.1.5", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.7.1", MTUSWITCH=OFF;
/*Modifying an SCTP host*/
MOD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="192.168.7.166";
/*Modifying a user-plane host*/
MOD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.7.166";
/*Modifying an OM channel*/
MOD OMCH: FLAG=MASTER, IP="192.168.7.166";
/*Modifying an IP clock link*/
RMV IPCLKLINK:;
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, CIP="192.168.7.166", SIP="192.168.49.249",
PROFILETYPE=1588V2;
/*Modifying the BFD configuration*/
MOD BFD: BFDSN=0, SRCIP="192.168.7.166";
/*Modifying the IP PM session*/
RMV IPPMSESSION: IPPMSN=0;
ADD IPPMSESSION: IPPMSN=0, IPPMTYPE=THREE_TUPLE, BINDPATH=NO, LOCALIP="192.168.7.166",
PEERIP="192.168.1.166";
/*Modifying the TWAMP configuration*/
MOD TWAMPCLIENT: CLIENTID=0, LOCALIP="192.168.1.166";
MOD TWAMPRESPONDER: RESPONDERID=0, LOCALIP="192.168.1.166";
/*If the IP address to be changed is used for IPsec negotiations, perform the following steps:*/
/*Changing the local IP address of the IKE peer to the new IPv4 address*/
MOD IKEPEER: PEERNAME="ike", LOCALIP="192.168.7.166";
/*If Source IP Address in the ACLRULE MO referenced by the IPSECBINDITF MO is this IPv4 address,
perform the following steps: */
/*All ACLRULE MOs that meet the preceding conditions need to be modified.*/
/*Modifying the ACL rules by changing the "Source IP Address" or "Destination IP Address" that
references this IP address to the new IPv4 address*/
MOD ACLRULE: ACLID=3000, RULEID=1, SIP="192.168.7.166";
MOD ACLRULE: ACLID=3100, RULEID=1, DIP="192.168.7.166";
/*Removing the IPv4 route*/
/*If multiple IP routes are associated with the IPv4 address, remove all the associated IP routes. To
query the IP routes associated with the IPv4 address, run the DSP IPROUTE4 command.*/
RMV IPROUTE4: RTIDX=0;
/*Removing a next-hop VLAN mapping relationship with the next-hop IP address of the VLAN
mapping being 192.168.0.1 and the subnet mask being 255.255.255.255*/
RMV VLANMAP: NEXTHOPIP="192.168.0.1", MASK="255.255.255.255";
/*Removing the IPv4 address*/
RMV IPADDR4: ITFID=1, IP="192.168.7.186";
/*Removing the INTERFACE MO if no IP address is configured on this MO where the old IPv4 address
resides*/
RMV INTERFACE: ITFID=1;

In the following example, the IPv6 address needs to be changed from

2010::121 to 2010::221 and the new IPv6 address is referenced by the MOs
SCTPHOST, USERPLANEHOST, OMCH, IPRT, and IPCLKLNK.
If OMCH parameters are modified by mistake, the OMCH may be
disconnected and cannot be restored within a long period of time. To avoid
service unavailability due to the OMCH disconnection, you are advised to turn
on the automatic rollback switch of the CB by running the CFM CB command
before configuring data. For example, CFM CB: MODE=UNFORCED,
NAME="CB1", COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Setting Ethernet port 0*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=1, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=1003, IPV6SW=ENABLE;
/*Adding an IPv6 address*/
ADD IPADDR6: IPADDR6ID="1", ITFID=1, IPV6="2010::221", PFXLEN=64;
/*Adding an IPv6 route*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 610

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*If multiple IP routes are associated with the IPv6 address, add all the associated IP routes.*/
ADD IPROUTE6: RTIDX=1, DSTIP="2193:1:50::", PFXLEN=64, RTTYPE=NEXTHOP, NEXTHOP="2010::3";
/*Modifying an SCTP host*/
MOD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv6, SIGIP1V6="2010::221";
/*Modifying a user-plane host*/
MOD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv6, MULTICASTLISTENERSW=DISABLE,
LOCIPV6="2010::221";
/*Modifying an OM channel*/
MOD OMCH: FLAG=MASTER, BEAR=IPV6, IP6="2010::221";
/*Modifying an IP clock link*/
RMV IPCLKLINK:;
ADD IPCLKLINK: LN=0, ICPT=PTP, SN=7, CNM=UNICAST, IPMODE=IPV6, CIPV6="2010::221",
SIPV6="2010::100", DELAYTYPE=E2E, PROFILETYPE=1588V2;
/*If Source IP Address in the ACLRULE6 MO referenced by the IPSECBINDITF MO is this IPv6 address,
perform the following steps: */
/*All ACLRULE6 MOs that meet the preceding conditions need to be modified.*/
/*Modifying the ACL rules by changing the "Source IP Address" or "Destination IP Address" that
references this IP address to the new IPv4 address*/
MOD ACLRULE6: ACLID=3000, RULEID=1, SIP="2010::221";
MOD ACLRULE6: ACLID=3001, RULEID=1, DIP="2010::221";
/*Removing the IPv6 route*/
/*If multiple IP routes are associated with the IPv6 address, remove all the associated IP routes. To
query the IP routes associated with the IPv6 address, run the DSP IPROUTE6 command.*/
RMV IPROUTE6: RTIDX=0;
/*Removing the IPv6 address*/
RMV IPADDR6: IPADDR6ID="0";
/*Removing the INTERFACE MO if no IP address is configured on this MO where the old IPv6 address
resides*/
RMV INTERFACE: ITFID=0;
● Link mode
In the following example, the IPv4 address needs to be changed from
192.168.7.186 to 192.168.7.166 and the new IPv4 address is referenced by
the MOs IPPATH, SCTPLNK, OMCH, IPRT, and IPCLKLNK.
If OMCH parameters are modified by mistake, the OMCH may be
disconnected and cannot be restored within a long period of time. To avoid
service unavailability due to the OMCH disconnection, you are advised to turn
on the automatic rollback switch of the CB by running the CFM CB command
before configuring data. For example, CFM CB: MODE=UNFORCED,
NAME="CB1", COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Setting Ethernet port 0*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=1, VRFIDX=0;
ADD VLANMAP: NEXTHOPIP="192.168.7.1" , MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
VLANID=101, SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;
/*Adding an IPv4 address*/
ADD IPADDR4: ITFID=0, IP="192.168.7.166", MASK="255.255.252.0";
/*Adding an IPv4 route*/
/*If multiple IP routes are associated with the IPv4 address, add all the associated IP routes.*/
ADD IPROUTE4: RTIDX=0, DSTIP="172.169.1.5", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.7.1", MTUSWITCH=OFF;
/*Modifying an SCTP link*/
MOD SCTPLNK: SCTPNO=0, LOCIP="192.168.7.166";
/*Modifying an IP path*/
MOD IPPATH: PATHID=0, TRANSCFGMODE=NEW, JNIPRSCGRP=DISABLE, BPT=ETH, PORTID=1,
LOCALIP="192.168.7.166";
/*Modifying an OM channel*/
MOD OMCH: FLAG=MASTER, IP="192.168.7.166";
/*Modifying an IP clock link*/
RMV IPCLKLINK:;
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, CIP="192.168.7.166", SIP="192.168.49.249",
PROFILETYPE=1588V2;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 611

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Modifying the BFD configuration*/

MOD BFD: BFDSN=0, SRCIP="192.168.7.166";
/*Modifying the IP PM session*/
RMV IPPMSESSION:IPPMSN=0;
ADD IPPMSESSION: IPPMSN=0, IPPMTYPE=THREE_TUPLE, BINDPATH=NO, LOCALIP="192.168.7.166",
PEERIP="192.168.1.166";
/*Modifying the TWAMP configuration*/
MOD TWAMPCLIENT: CLIENTID=0, LOCALIP="192.168.1.166";
MOD TWAMPRESPONDER: RESPONDERID=0, LOCALIP="192.168.1.166";
/*If the IP address to be changed is used for IPsec negotiations, perform the following steps:*/
/*Changing the local IP address of the IKE peer to the new IPv4 address*/
MOD IKEPEER: PEERNAME="ike", LOCALIP="192.168.7.166";
/*If Source IP Address in the ACLRULE MO referenced by the IPSECBINDITF MO is this IPv4 address,
perform the following steps: */
/*All ACLRULE MOs that meet the preceding conditions need to be modified.*/
/*Modifying the ACL rules by changing the "Source IP Address" or "Destination IP Address" that
references this IP address to the new IPv4 address*/
MOD ACLRULE: ACLID=3000, RULEID=1, SIP="192.168.7.166";
MOD ACLRULE: ACLID=3100, RULEID=1, DIP="192.168.7.166";
/*Removing the IPv4 route*/
/*If multiple IP routes are associated with the IPv4 address, remove all the associated IP routes. To
query the IP routes associated with the IPv4 address, run the DSP IPROUTE4 command.*/
RMV IPROUTE4: RTIDX=0;
/*Removing a next-hop VLAN mapping relationship with the next-hop IP address of the VLAN
mapping being 192.168.0.1 and the subnet mask being 255.255.255.255*/
RMV VLANMAP: NEXTHOPIP="192.168.0.1", MASK="255.255.255.255";
/*Removing the IPv4 address*/
RMV IPADDR4: ITFID=1, IP="192.168.7.186";
/*Removing the INTERFACE MO if no IP address is configured on this MO where the old IPv4 address
resides*/
RMV INTERFACE: ITFID=1;

1.8.8.3 Engineering Implementation

This section describes the engineering implementation for changing an IPv4/IPv6
address, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
If the IPv4/IPv6 address to be changed is an OM IP address, you are advised
to run MML commands on the LMT to deliver the data to the eNodeB and
then activate the data.
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 612

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the LMT to deliver the batch configuration script prepared according
to Engineering Preparation > Data Preparation to the base station and
activate the script on the base station. For details, see 1.3.2 Running
MML Commands on the LMT.
d. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
e. (Optional) If the IPv4/IPv6 address is used for an OM channel, change
the OM IP address of the NE to the new IPv4/IPv6 address on the MAE-
Access.
i. On the menu bar of the MAE-Access, choose Topology > Main
Topology.
ii. In the navigation tree on the left, select the eNodeB.
iii. In the right pane, right-click the eNodeB and choose Property from
the shortcut menu.
iv. In the displayed NE Properties dialog box, set IP Address 1 to the
new IPv4/IPv6 address, and then click OK.
● Remote Operations

If the IPv4/IPv6 address to be changed is not an OM IP address, you are

advised to use the MAE-Deployment to deliver the data to the base station
and then activate the data.

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Select a proper method to change IPv4/IPv6 addresses according to the
following table:

If You Need to... Then...

Configure S1 using the endpoint Perform c.

mode

Configure X2 using the endpoint Perform d.

mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 613

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If You Need to... Then...

Configure eX2 using the endpoint Perform e.

mode

c. Run the LST GLOBALPROCSWITCH command to query the values of the

options of The Switch of S1-MME Configuration by SON parameter.

▪ If the values of the options are Off, skip this step.

▪ If the values of the options are On, run the MOD

GLOBALPROCSWITCH command with the options of The Switch of
S1-MME Configuration by SON deselected. Example: MOD
GLOBALPROCSWITCH:
S1MMESonSwitch=S1MMESonSetupSwitch-0&S1MMESonDeleteS
witch-0;
d. Run the LST GLOBALPROCSWITCH command to query the settings of
The Switch of X2 setup by SON, Peer Request Based X2 Delete Switch,
and The Timer of X2 delete by SON(min) and check whether the
options of X2 SON Delete Switch are selected.

▪ If The Timer of X2 delete by SON(min) is 0 and all the values of

the other preceding parameters or options are OFF or deselected,
skip this step.

▪ If The Timer of X2 delete by SON(min) is not 0 or any of the other

preceding parameters or options is ON or selected, run the MOD
GLOBALPROCSWITCH command with The Timer of X2 delete by
SON(min) set to 0, all the values set to OFF, and all options
deselected. Example: MOD GLOBALPROCSWITCH:
X2SonSetupSwitch=OFF, X2SonDeleteTimer=0,
PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2USAGE
_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-0;
e. Run the LST GLOBALPROCSWITCH command to query the settings of
the options of the eX2 Auto Delete Switch and eX2 Auto Setup Switch
parameters.

▪ If the options are deselected, go to the next step.

▪ If any option is selected, run the MOD GLOBALPROCSWITCH

command with the options deselected. Example: MOD
GLOBALPROCSWITCH:
eX2AutoDeleteSwitch=BASED_ON_EX2FAULT-0,
eX2AutoSetupSwitch=BASED_ON_EX2_IDEAL_MODE-0&BASED_O
N_EX2_NON_IDEAL_MODE-0;
f. Deliver the configuration data to the eNodeB and activate it. For details,
see the interactive operation guide Delivering Data to Base Stations
and Activating the Data.
g. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 614

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

h. Restore the settings of the switches changed in c, d, or e.

----End

1.8.8.4 Engineering Verification

This section describes how to verify the reconfiguration for changing IPv4/IPv6
addresses.

Procedure
Step 1 Verify that no related alarms have been reported.
For example:
● ALM-25886 IP Path Fault
● ALM-25901 Remote Maintenance Link Failure
● ALM-25888 SCTP Link Fault
● ALM-25952 User Plane Path Fault
● ALM-25954 User Plane Fault
● ALM-26263 IP Clock Link Failure
● ALM-26266 Time Synchronization Failure
● ALM-25899 BFD Session Fault
● ALM-25891 IKE Negotiation Failure
● ALM-29201 S1 Interface Fault
● ALM-29204 X2 Interface Fault
If any alarm is reported, clear the alarm by referring to 3900 & 5900 Series Base
Station Alarm Reference.
Step 2 Run the LST IPADDR4 command to check whether the values of IP Address and
Mask are the same as planned for IPv4 transmission.
If the values of IP Address and Mask are not the same as planned, view the
modified configuration data file to check whether they are the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
Run the LST IPADDR6 command to check whether the values of IPv6 Address and
Prefix Length are the same as planned for IPv6 transmission.
If the values of IPv6 Address and Prefix Length are not the same as planned,
view the modified configuration data file to check whether they are the same as
planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 615

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.8.8.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Context
If the changed IPv4/IPv6 address is used as an OM IP address, a rollback cannot
be performed. The rollback of an IPv4/IPv6 address that is not used as an OM IP
address is as follows.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 616

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.8.8.4

Engineering Verification.

----End

1.8.9 Changing the IP Address of a Clock Server

This section describes how to change the IP address of a clock server.

Prerequisites
Data for the transport network between the eNodeB and the modified clock server
has been configured.

1.8.9.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the IP address of a
clock server.

Application Scenario
● An eNodeB needs to be connected to another clock server when the serving
clock server becomes unusable.
● The IP address of the serving clock server needs to be changed because of
network replanning.

Reconfiguration Impact
The eNodeB cannot synchronize with the clock source and handovers within the
cells of the eNodeB may be affected during the change of the IP address of the
clock server.

Reconfiguration Scheme
Figure 1-110 and Figure 1-113 show the reconfiguration procedures for changing
the IP address of a clock server. Determine the reconfiguration scheme according
to the following table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 617

eRAN
Reconfiguration Guide
Table 1-210 Scheme options
If…
No route is available between the
eNodeB and the new clock server
(MML command) The clock work
mode is manual and the clock source
is the IP clock before reconfiguration
(MML command) The Clock Working
Mode is changed to Auto
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
Old Model
The Transmission Configuration
Mode parameter in the GTRANSPARA
MO is set to OLD.
Add a route from the eNodeB to the
new clock server and the
corresponding VLANMAP MO.
New Model
The Transmission Configuration
Mode parameter in the GTRANSPARA
MO is set to NEW.
● IPv4: Add an IPv4 route from the
eNodeB to the new clock server and
the corresponding VLANMAP MO.
● IPv6: Add an IPv6 route from the
eNodeB to the new clock server.
Change the clock working mode to
Auto so that operators can remove the
old IP clock link and add a new IP
clock link.
Change the Clock Working Mode to
Manual.
618
eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-110 Procedure for changing the IP address of a clock server using the
MAE-Deployment (IPv4)

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 619

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-111 Procedure for changing the IP address of a clock server using the
MAE-Deployment (IPv4)

Figure 1-112 Procedure for changing the IPv6 address of a clock server using the
MAE-Deployment (IPv6)

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 620

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-113 Procedure for changing the IP address of a clock server using MML
commands (IPv4)

New Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 621

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Figure 1-114 Procedure for changing the IP address of a clock server using MML
commands (IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 622

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-115 Procedure for changing the IP address of a clock server using MML
commands (IPv6)

Topology Change
N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 623

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.9.2 Engineering Preparation

This section describes the engineering preparation for changing the IP address of a
clock server, including information collection and preparation of hardware,
software, license files, security certificates, and data. It also describes the data
preparation mode and provides MML configuration script examples.

Information Collection
Table 1-211 describes the information to be collected for data preparation.

Table 1-211 Information to be collected

Information Description

IPv4 address of the new clock server Includes the IPv4 address and subnet
mask.

IPv6 address of the new clock server Includes the IPv6 address and prefix
length.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

NOTE

The clock server setting is common data for a co-MPT multimode base station (MBTS). You only
need to reconfigure the clock server once, and the configuration takes effect for all RATs of the
MBTS.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 624

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-212 Data preparation for changing the IP address of a clock server
Rec SN Ope MO Configuration Reference
onfi rati
gura on
tion
Mod
e

MAE 1 Mod IPCLKL Change the IP address to that of the new clock
- ify NK server.
Depl
oym 2 Mod IPv4: Change Destination IP to the IP address of the
ent ify IPRT/ new clock server.
SRCIPR
Ta

MM 1 Mod TASM Change Clock Working Mode to AUTO(Auto).

L ify
com
man 2 Dele IPCLKL -
ds te NK

3 Add IPCLKL For details, see "Clock over IP (FDD)" > "Data
NK Preparation" in Synchronization Feature
Parameter Description.
4 Add IPv4: For details, see IP eRAN Engineering Guide
IPRT/ Feature Parameter Description.
SRCIPR
Ta

5 Add IPv4:
VLAN
MAP

6 Mod TASM Change Clock Working Mode to

ify MANUAL(Manual) and set Selected Clock
Source to IP Clock.

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 625

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-213 Data preparation for changing the IP address of a clock server
Rec SN Ope MO Configuration Reference
onfi rati
gura on
tion
Mod
e

MAE 1 Mod IPCLKLNK Change the IP address to

- ify that of the new clock server.
Depl
oym 2 Mod IPv4: IPROUTE4/ Change Destination IP to
ent ify SRCIPROUTE4a the IP address of the new
IPv6: IPROUTE6 clock server.

MM 1 Mod TASM Change Clock Working

L ify Mode to AUTO(Auto).
com
man 2 Dele IPCLKLNK -
ds te

3 Add IPCLKLNK For details, see "Clock over

IP (FDD)" > "Data
Preparation" in
Synchronization Feature
Parameter Description.
4 Add IPv4: IPROUTE4/ For details, see IP eRAN
SRCIPROUTE4a Engineering Guide Feature
IPv6: IPROUTE6 Parameter Description.

5 Add IPv4: VLANMAP

IPv6: N/A

6 Mod TASM Change Clock Working

ify Mode to
MANUAL(Manual) and set
Selected Clock Source to IP
Clock.

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 626

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario-specific template being "Changing the IP Address of a
Clock Server"). For details, see the interactive operation guide 1.11.2 Using
the Batch Reconfiguration Mode of the MAE-Deployment to Prepare
Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, the clock working mode is manual, and the device IP
address of the eNodeB is not on the same network segment as the IP address of
the new clock server.

If OMCH parameters are modified by mistake, the OMCH may be disconnected

and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.
/*Setting the clock working mode to Auto*/
SET CLKMODE:MODE=AUTO;
/*Removing the old IP clock link*/
RMV IPCLKLINK:;
/*Adding a new IP clock link with the server IP address set to the IP address of the new clock server*/
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, IPMODE=IPV4, CIP="172.31.13.241", SIP="192.168.0.128",
PROFILETYPE=1588V2;
/*Adding an IP route toward the new clock server*/
ADD IPRT:RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="192.168.0.128", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="172.31.13.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="172.31.13.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SET
PRIO=DISABLE;
/*Setting Clock Working Mode to MANUAL and Selected Clock Source to IPCLK*/
SET CLKMODE:MODE=MANUAL, CLKSRC=IPCLK, SYNMODE=OFF;

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 627

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Setting Clock Working Mode to AUTO*/

SET CLKMODE:MODE=AUTO;
/*Removing the old IP clock link*/
RMV IPCLKLINK:;
/*Adding a new IP clock link with the server IP address set to the IP address of the new clock server*/
ADD IPCLKLINK:ICPT=PTP, SN=7, CNM=UNICAST, IPMODE=IPV4, CIP="172.31.13.241", SIP="192.168.0.128",
PROFILETYPE=1588V2;
/*Adding an IP route toward the new clock server*/
ADD IPROUTE4:RTIDX=0, DSTIP="192.168.0.128", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="172.31.13.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group when the
VLANMAP MO is used to configure a VLAN*/
ADD
VLANMAP:NEXTHOPIP="172.31.13.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SET
PRIO=DISABLE;
/*(Optional) Adding an INTERFACE MO in which Interface Type is VLAN*/
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=71, VLAN=101, VRFIDX=0;
/*Setting Clock Working Mode to MANUAL and Selected Clock Source to IPCLK*/
SET CLKMODE:MODE=MANUAL, CLKSRC=IPCLK, SYNMODE=OFF;

1.8.9.3 Engineering Implementation

This section describes the engineering implementation for changing the IP address
of a clock server, including prerequisites, context, and procedure.

Prerequisites
● Related information and configuration data are ready.
● The new clock server has been configured and connected to the eNodeB.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
N/A
● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
iii. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 628

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Using MML commands:

i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.8.9.4 Engineering Verification

This section describes how to verify the modification of the IP address of a clock
server.

Procedure
Step 1 Verify that the following alarms have not been reported:
● ALM-26262 External Clock Reference Problem
● ALM-26263 IP Clock Link Failure
● ALM-26264 System Clock Unlocked

If any alarm is reported, clear the alarm following the instructions in 3900 & 5900
Series Base Station Alarm Reference.
Step 2 Run the LST IPCLKLINK command to check whether the Server IPv4/IPv6 is the
same as the IP address of the new clock server.

If they are different, check whether the Server IP of the IP clock link in the
configuration data file is the same as the IP address of the new clock server.

● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 629

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.
Step 3 Run the DSP IPCLKLINK command, and verify that the value of Link Available
State is Available and the value of Link Active State is Activated.
If the value of Link Available State is Unavailable, ping the IP address of the
clock server to check whether the route between the device IP address (old
model)/IPv4 address (new model)/IPv6 address (new model) of the eNodeB and
the IP address of the clock server is normal.

If... Then...

The IP address is Check whether the IP route toward the clock server is
unreachable. correctly configured.
● If the IP route is correctly configured,
– IPv4 scenarios: Run RMV IPRT (old model)/RMV
IPROUTE4 (new model) to remove the IP route
first, and then run ADD IPRT (old model)/ADD
IPROUTE4 (new model) to add a correct IP route.
– IPv6 scenarios: Run MOD IPROUTE6/ADD
IPROUTE6.
● If the IP route is correctly configured, check whether
the physical link between the eNodeB and the IP
clock server is normal.
– If it is abnormal, adjust the physical connection.
– If it is normal, contact Huawei technical support
or dial the Huawei technical support hotline.

The IP address is Contact local Huawei technical support engineers or

reachable dial the Huawei technical support hotline.

If the value of Link Active State is Deactivated, run the LST CLKMODE
command to check whether the value of Clock Working Mode is Manual and the
value of Selected Clock Source is IP Clock or check whether the value of Clock
Working Mode is Auto.
If... Then...

No Run the SET CLKMODE command to change the value

of Clock Working Mode or Selected Clock Source.

Yes Contact local Huawei technical support engineers or

dial the Huawei technical support hotline..

Step 4 Run the DSP CLKSTAT command. Wait for more than 10 minutes, and check
whether the value of PLL Status is Locked.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 630

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If it is not Locked, contact Huawei technical support or dial the Huawei technical
support hotline.

----End

1.8.9.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 631

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 2 Verify that engineering rollback is successful according to instructions in 1.8.9.4

Engineering Verification.
----End

1.8.10 Changing the SCTP Link Number (for IPv4 Transmission

Only)
This section describes how to change an SCTP link number.

1.8.10.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing an SCTP link number.
This task is applicable only to IPv4 transmission.

Application Scenario
● SCTP link numbers need to be replanned.
● The self-setup SCTP link numbers in endpoint configuration mode do not
meet requirements.

Reconfiguration Impact
A service link (such as S1 or X2) needs to be reestablished when the SCTP link
number is changed. During the reestablishment, services on the link will be
interrupted.

Reconfiguration Scheme
Figure 1-116 shows the reconfiguration procedure using the MAE-Deployment.
Figure 1-117 shows the reconfiguration procedure using MML commands.
NOTE

Run LST SCTPLNK to query the Auto Config Flag value to determine whether the SCTP link is
set up automatically or manually.
● If the Auto Config Flag value is Manual Created, the SCTP link is set up manually.
● If the Auto Config Flag value is Auto Created, the SCTP link is set up automatically.
This scenario is used when the SCTP link is set up manually.

Figure 1-116 Changing an SCTP link number (using the MAE-Deployment)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 632

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-117 Changing an SCTP link number (using the MML commands)

Topology Change
N/A

1.8.10.2 Engineering Preparation

This section describes the engineering preparation for changing an SCTP link
number, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Information Collection
Table 1-214 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 633

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-214 Information to be collected

Information Description

Information of the local end of the Includes the device IP address (old
SCTP link model)/IPv4 address (new model) and
port number of the local end

Information of the peer end of the Includes the IP address and port
SCTP link number of the peer end

Information about the objects that Includes the S1/X2 object ID, S1/X2
reference the SCTP link interface ID, and CP bearer number

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Table 1-215 Data preparation for changing an SCTP link number

Rec SCT SN Op MO Configuration Reference

onfi P erat
gur Lin ion
atio k
n Set
Mo up
de Mo
de

MA - 1 Mo SCTPLNK Change the value of Link No. to the

E- dify target value.
Dep
loy 2 Mo CPBEARER Change the value of Link No. to the
me dify target value.
nt

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 634

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SCT SN Op MO Configuration Reference

onfi P erat
gur Lin ion
atio k
n Set
Mo up
de Mo
de

MM Aut 1 Del S1 or X2 Remove the S1 or X2 object for which

L om ete this SCTP link is set up.
com atic
ma setu 2 Add SCTPLNK Change the SCTP link number to the
nds p target value and set other parameters
to the same values as the old SCTP
link.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
3 Add S1 or X2 For details, see LTE and NR NSA S1
and X2 Self-Management Feature
Parameter Description.

Ma 1 Del S1Interface or Remove the S1 or X2 interface

nua ete X2Interface associated with the old SCTP link.
l
setu 2 Del CPBEARER Remove the CP bearer that references
p ete the old SCTP link.

3 Del SCTPLNK Remove the old SCTP link.

ete

4 Add SCTPLNK Change the SCTP link number to the

target value and set other parameters
to the same values as the old SCTP
link.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
5 Add CPBEARER Add a CP bearer that references the
new SCTP link.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
6 Add S1Interface or For details, see LTE and NR NSA S1
X2Interface and X2 Self-Management Feature
Parameter Description.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. It is recommended that the MAE-Deployment batch reconfiguration
mode be used. The two data preparation modes are described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 635

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Changing an SCTP Link Number"). For details,
see the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, the number of the SCTP link over the S1 interface set up
automatically or manually is changed to 100.

If OMCH parameters are modified by mistake, the OMCH may be disconnected

and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

● If the SCTP link is set up automatically:

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to OLD.
/*Removing the S1 object*/
RMV S1:S1Id=0;
/*Adding an SCTP link with the Link No. of 100*/
ADD SCTPLNK:SCTPNO=100, SN=7, LOCIP="192.168.200.110", LOCPORT=2918, PEERIP="192.168.3.3",
PEERPORT=2918, AUTOSWITCH=ENABLE;
/*Adding the associated S1 object*/
ADD S1:S1Id=0, CnOperatorId=03, CpEpGroupId=0, UpEpGroupId=0;

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO
is set to NEW.
/*Removing the S1 object*/
RMV S1:S1Id=0;
/*Adding an SCTP link with the Link No. of 100*/
ADD SCTPLNK:SCTPNO=100, LOCIP="192.168.200.110", LOCPORT=2918, PEERIP="192.168.3.3",
PEERPORT=2918, AUTOSWITCH=ENABLE;
/*Adding the associated S1 object*/
ADD S1:S1Id=0, CnOperatorId=03, CpEpGroupId=0, UpEpGroupId=0;

● If the SCTP link is set up manually:

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is
set to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 636

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Removing the S1 interface*/

RMV S1INTERFACE:S1InterfaceId=0;
/*Removing the CP bearer*/
RMV CPBEARER:CPBEARID=0, FLAG=MASTER;
/*Removing the old SCTP link*/
RMV SCTPLNK:SCTPNO=0;
/*Adding an SCTP link with the Link No. of 100*/
ADD SCTPLNK:SCTPNO=100, SN=7, LOCIP="192.168.200.110", LOCPORT=2918, PEERIP="192.168.3.3",
PEERPORT=2918, AUTOSWITCH=ENABLE;
/*Adding a CP bearer*/
ADD CPBEARER:CPBEARID=0, BEARTYPE=SCTP, LINKNO=100, FLAG=MASTER;
/*Adding an S1 interface*/
ADD S1INTERFACE:S1InterfaceId=0, S1CpBearerId=0, CnOperatorId=03;

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO
is set to NEW.
/*Removing the S1 interface*/
RMV S1INTERFACE:S1InterfaceId=0;
/*Removing the CP bearer*/
RMV CPBEARER:CPBEARID=0, FLAG=MASTER;
/*Removing the old SCTP link*/
RMV SCTPLNK:SCTPNO=0;
/*Adding an SCTP link with the Link No. of 100*/
ADD SCTPLNK:SCTPNO=100, LOCIP="192.168.200.110", LOCPORT=2918, PEERIP="192.168.3.3",
PEERPORT=2918, AUTOSWITCH=ENABLE;
/*Adding a CP bearer*/
ADD CPBEARER:CPBEARID=0, BEARTYPE=SCTP, LINKNO=100, FLAG=MASTER;
/*Adding an S1 interface*/
ADD S1INTERFACE:S1InterfaceId=0, S1CpBearerId=0, CnOperatorId=03;

1.8.10.3 Engineering Implementation

This section describes the engineering implementation for changing an SCTP link
number, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 637

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see 1.11.1 Setting the eNodeB Maintenance Mode.

ii. Run the LST GLOBALPROCSWITCH command to query the values of
the options of The Switch of S1-MME Configuration by SON
parameter.
○ If the values of the options are Off, skip this step.
○ If the values of the options are On, run the MOD
GLOBALPROCSWITCH command with the options of The
Switch of S1-MME Configuration by SON deselected. Example:
MOD GLOBALPROCSWITCH:
S1MMESonSwitch=S1MMESonSetupSwitch-0&S1MMESonDel
eteSwitch-0;
iii. Run the LST GLOBALPROCSWITCH command to query the settings
of The Switch of X2 setup by SON, Peer Request Based X2 Delete
Switch, and The Timer of X2 delete by SON(min) and check
whether the options of X2 SON Delete Switch are selected.
○ If The Timer of X2 delete by SON(min) is 0 and all the values
of the other preceding parameters or options are OFF or
deselected, skip this step.
○ If The Timer of X2 delete by SON(min) is not 0 or any of the
other preceding parameters or options is ON or selected, run the
MOD GLOBALPROCSWITCH command with The Timer of X2
delete by SON(min) set to 0, all the values set to OFF, and all
options deselected. Example: MOD GLOBALPROCSWITCH:
X2SonSetupSwitch=OFF, X2SonDeleteTimer=0,
PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2US
AGE_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-
0;
iv. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
vi. Restore the settings of the switches changed in ii and iii.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 638

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",

USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.8.10.4 Engineering Verification

This section describes how to verify the change of an SCTP link number.

Procedure
Step 1 Verify that the following alarms have not been reported:
● ALM-25888 SCTP Link Fault
● ALM-29201 S1 Interface Fault
● ALM-29204 X2 Interface Fault
If any alarm is reported, clear the alarm following the instructions in 3900 & 5900
Series Base Station Alarm Reference.
Step 2 Run LST SCTPLNK to verify that the SCTP Link No. value is the same as planned.
If the SCTP link number is not the same as planned, check whether the SCTP link
number in the configuration data file is the same as planned.
● If they are different, modify the configuration data file again and import it
into the system. Then perform the operations in Engineering
Implementation again to deliver the data to the base station and then
activate it.
● If they are the same, an error has occurred when the data is imported into the
system or delivered to the base station. In this situation, contact Huawei
technical support or dial the Huawei technical support hotline.

----End

1.8.10.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 639

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands:

– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that the rollback has succeeded by referring to operations in 1.8.10.4
Engineering Verification.

----End

1.8.11 Removing an X2 Interface

This section describes how to remove an X2 interface.

1.8.11.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for removing an X2 interface.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 640

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Application Scenario
An original neighboring eNodeB is removed, and the corresponding X2 interface
becomes invalid.

Reconfiguration Impact
No impact

Reconfiguration Scheme
Determine the reconfiguration scheme for removing an X2 interface according to
the following table.

Table 1-216 Scheme options

If... Then...

The command output of DSP Select a reconfiguration scheme

X2INTERFACE shows that the Auto applicable to an automatically created
Config Flag value is Auto Created X2 interface.

The command output of DSP Select a reconfiguration scheme

X2INTERFACE shows that the Auto applicable to a manually created X2
Config Flag value is Manual Created interface.

The IP path ID value in a Remove the IP path of the operator.

CnOperatorIpPath MO is the same as
the Path ID value in an IPPATH MO
corresponding to the X2 interface to
be removed

The IP Path ID value in an Remove the application type of the IP

eNodeBPath MO is the same as the path.
Path ID value in an IPPATH MO
corresponding to the X2 interface to
be removed

Figure 1-118 shows the reconfiguration procedure for removing an X2 interface.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 641

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-118 Removing an X2 interface

Topology Change
Figure 1-119 shows the topologies before and after the reconfiguration.

Figure 1-119 Topologies before and after the reconfiguration

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 642

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.11.2 Engineering Preparation

This section describes the engineering preparation for removing an X2 interface,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-217 describes the information to be collected for data preparation.

Table 1-217 Information to be collected

Information Description

SCTP peer ID SCTP peer ID of the X2 interface to be removed, which

needs to be collected if the X2 interface is
automatically set up

User-plane peer ID User-plane peer ID of the X2 interface to be removed,

which needs to be collected if the X2 interface is
automatically set up

X2 interface ID ID of the X2 interface to be removed, which needs to

be collected if the X2 interface is manually set up

CP bearer number CP bearer number of the X2 interface to be removed,

which needs to be collected if the X2 interface is
manually set up

SCTP link number SCTP link number of the X2 interface to be removed,

which needs to be collected if the X2 interface is
manually set up

IP path ID IP path ID of the X2 interface to be removed, which

needs to be collected if the X2 interface is manually set
up

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 643

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Table 1-218 Data preparation for removing an X2 interface

X2 SN Ope MO Configuration Reference
Inte rati
rfac on
e
Setu
p
Mod
e

Auto 1 Mod EPGROUP Remove the SCTP peer and user-plane

mati ify peer of the X2 interface from the
cally endpoint group.

2 Dele SCTPPEER Remove the SCTP peer of the X2

te interface.

3 Dele USERPLANEPE Remove the user-plane peer of the X2

te ER interface.

Man 1 Dele X2Interface Remove the X2 interface.

ually te

2 Dele CPBEARER Remove the CP bearer that references

te the X2 interface.

3 Dele SCTPLNK Remove the SCTP link of the X2 interface.

te

4 Dele CnOperatorIpP Remove the operator's IP path whose IP

te ath path ID value is the same as the Path ID
value in an IPPATH MO corresponding to
the X2 interface.

5 Dele eNodeBPath Remove the application type of an IP

te path whose IP Path ID value is the same
as the Path ID value in an IPPATH MO
corresponding to the X2 interface.

6 Dele IPPATH Remove the IP paths of the X2 interface.

te

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 644

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Removing an X2 Interface"). For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The following provides examples for removing automatically and manually created
X2 interfaces.

If OMCH parameters are modified by mistake, the OMCH may be disconnected

and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

● Example for removing an automatically created X2 interface:

/*Removing the SCTP peer of the X2 interface from the endpoint group*/
RMV SCTPPEER2EPGRP: EPGROUPID=3, SCTPPEERID=16;
/*Removing the user-plane peer of the X2 interface from the endpoint group*/
RMV UPPEER2EPGRP: EPGROUPID=3, UPPEERID=16;
/*Removing the SCTP link of the X2 interface*/
RMV SCTPPEER: SCTPPEERID=16;
/*Removing the IP path of the X2 interface*/
RMV USERPLANEPEER: UPPEERID=16;

● Example for removing a manually created X2 interface, during which the IP

path of the operator and the application type of the IP path also need to be
removed:
/*Removing the X2 interface*/
RMV X2INTERFACE: X2InterfaceId=16;
/*Removing the CP bearer*/
RMV CPBEARER: CPBEARID=3, FLAG=MASTER;
/*Removing the SCTP link*/
RMV SCTPLNK: SCTPNO=3;
/*Removing the IP path of the operator*/
RMV CNOPERATORIPPATH: IpPathId=3;
/*Removing the application type of the IP path*/
RMV ENODEBPATH: IpPathId=3;
/*Removing the IP path*/
RMV IPPATH: PATHID=3;

1.8.11.3 Engineering Implementation

This section describes the engineering implementation for deleting an X2
interface, including prerequisites, context, and procedure.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 645

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the LST GLOBALPROCSWITCH command to query the settings
of The Switch of X2 setup by SON, Peer Request Based X2 Delete
Switch, and The Timer of X2 delete by SON(min) and check
whether the options of X2 SON Delete Switch are selected.
○ If The Timer of X2 delete by SON(min) is 0 and all the values
of the other preceding parameters or options are OFF or
deselected, skip this step.
○ If The Timer of X2 delete by SON(min) is not 0 or any of the
other preceding parameters or options is ON or selected, run the
MOD GLOBALPROCSWITCH command with The Timer of X2
delete by SON(min) set to 0, all the values set to OFF, and all
options deselected. Example: MOD GLOBALPROCSWITCH:
X2SonSetupSwitch=OFF, X2SonDeleteTimer=0,
PeerReqBasedX2DelSwitch=OFF,
X2SonDeleteSwitch=BASED_ON_X2FAULT-0&BASED_ON_X2US
AGE_WITH_NEGO-0&BASED_ON_X2USAGE_WITHOUT_NEGO-
0;
iii. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
v. Restore the settings of the switches changed in ii.
– Using MML commands:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 646

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.8.11.4 Engineering Verification

This section describes how to verify the removal of an X2 interface.

Procedure
Step 1 (Optional) If the X2 interface is automatically set up, run the LST EPGROUP
command to verify that there is no SCTP peer or user-plane peer.

If there is an SCTP peer or user-plane peer, perform the following steps:

If... Then...

The reconfiguration is Check whether the data configuration file is the same
performed on the as planned.
MAE-Deployment ● If they are different, modify the configuration data
file again and import it into the system. Then
perform the operations in Engineering
Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the
data is imported into the system or delivered to the
base station. In this situation, contact Huawei
technical support or dial the Huawei technical
support hotline.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 647

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The reconfiguration is Check whether the parameters in MML scripts are

performed by using correct.
MML commands ● If they are incorrect, modify the parameters in the
MML scripts and perform the operations in
Engineering Implementation again to deliver the
data to the eNodeB and activate it.
● If they are correct, contact Huawei technical support
or dial the Huawei technical support hotline.

Step 2 (Optional) If the X2 interface is manually set up, run the DSP X2INTERFACE
command to verify that there is no X2 interface information.
If there is interface information, perform the following steps:

If... Then...

The reconfiguration is Check whether the data configuration file is the same
performed on the as planned.
MAE-Deployment ● If they are different, modify the configuration data
file again and import it into the system. Then
perform the operations in Engineering
Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the
data is imported into the system or delivered to the
base station. In this situation, contact Huawei
technical support or dial the Huawei technical
support hotline.

The reconfiguration is Check whether the parameters in MML scripts are

performed by using correct.
MML commands ● If they are incorrect, modify the parameters in the
MML scripts and perform the operations in
Engineering Implementation again to deliver the
data to the eNodeB and activate it.
● If they are correct, contact Huawei technical support
or dial the Huawei technical support hotline.

----End

1.8.11.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Context
The reconfiguration aims to delete unnecessary data and prevent invalid alarms. If
the reconfiguration fails, the redundant information is not removed completely;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 648

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

however, ongoing services are not affected. Therefore, engineering rollback is not
recommended in this case. The following operations can be performed when the
X2 interface needs to be restored.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that the rollback has succeeded by referring to operations in 1.8.11.4
Engineering Verification.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 649

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.12 Modifying the Ethernet Port Number (Old Model)

This section describes how to modify an Ethernet port number (old model).

1.8.12.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for modifying an Ethernet port
number.

Application Scenario
The previously planned Ethernet port numbers are inappropriate and a new plan is
required.

Reconfiguration Impact
● If the Ethernet port to be changed is used as a port for remote maintenance,
the MAE-Access and MAE-Deployment are disconnected from the NE after
the old OM channel becomes invalid and before the new OM channel is set
up.
● If the Ethernet port number to be changed is used for service transmission,
service link (such as S1 or X2) reestablishment is required. During the
reestablishment, services on the link will be interrupted.
● If the Ethernet port number to be changed is used for IP Security (IPsec)
negotiation, IPsec renegotiation is required. During the renegotiation, services
on the IPsec tunnel will be interrupted.

Reconfiguration Scheme
The reconfiguration schemes using the MAE-Deployment and using MML
commands are different because you cannot directly remove device IP addresses
associated with the Ethernet port number using MML commands.
The reconfiguration scheme using the MAE-Deployment is as follows:
1. Remove all device IP addresses associated with the old Ethernet port number
2. Add all original device IP addresses and associate them with the new Ethernet
port number
3. Modify the attributes, rate, and duplex mode of the new Ethernet port
number and make them consistent with those of the old Ethernet port
number.
Table 1-219 and Table 1-220 describe the reconfiguration scheme using MML
commands.
● Endpoint mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 650

eRAN
Reconfiguration Guide
Table 1-219 Reconfiguration scheme for modifying the Ethernet port number
(MML commands, in endpoint mode)
If...
The IP route is set up on the old
Ethernet port
An S1 link is set up on the old
Ethernet port
An X2 link is set up on the old
Ethernet port
An OM channel is set up on the
old Ethernet port
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
Remove the MOs associated with the
old Ethernet port number by running
the following command:
RMV IPRT
Remove the MOs associated with the
old Ethernet port number by running
the following commands:
1. RMV S1INTERFACE
2. RMV CPBEARER
3. RMV SCTPHOST
4. RMV UPHOST2EPGRP
5. RMV USERPLANEHOST
6. (Optional) RMV
CNOPERATORIPPATH if an IP path
has been associated with an operator
7. (Optional) RMV ENODEBPATH if an
IP path has been associated with an
eNodeB
8. (Optional) RMV IPPATH if an IP path
has been configured
Remove the MOs associated with the
old Ethernet port number by running
the following commands:
1. RMV X2
2. RMV SCTPHOST2EPGRP
3. RMV SCTPHOST
4. RMV UPHOST2EPGRP
5. RMV USERPLANEHOST
6. (Optional) RMV
CNOPERATORIPPATH if an IP path
has been associated with an operator
7. (Optional) RMV ENODEBPATH if an
IP path has been associated with an
eNodeB
8. (Optional) RMV IPPATH if an IP path
has been configured
Remove the MOs associated with the
old Ethernet port number by running
the following command:
RMV OMCH
651
eRAN
Reconfiguration Guide
If...
An IP clock link is set up on the
old Ethernet port
A link set up on the old Ethernet
port supports BFD
The old Ethernet port number is
used for IPsec negotiation and
the local IP address of the IKE
peer is not 0.0.0.0
- Remove all device IP addresses
- Add all original device IP addresses and
The new Ethernet port is used to
bear an IP route
The new Ethernet port is used to
bear an S1 link
The new Ethernet port is used to
bear an X2 link
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
Remove the MOs associated with the
old Ethernet port number by running
the following command:
RMV IPCLKLINK
Remove the MOs associated with the
old Ethernet port number by running
the following command:
RMV BFDSESSION
Set the local IP address of the IKE peer
to 0.0.0.0 by running the following
command: MOD IKEPEER
associated with the old Ethernet port
number by running the following
command:
RMV DEVIP
associate them with the new Ethernet
port number by running the following
command:
ADD DEVIP
Add services that use the new Ethernet
port by running the following command:
ADD IPRT
Add services that use the new Ethernet
port by running the following
commands:
1. ADD SCTPHOST
2. ADD SCTPHOST2EPGRP
3. ADD USERPLANEHOST
4. ADD UPHOST2EPGRP
5. ADD S1
Add services that use the new Ethernet
port by running the following
commands:
1. ADD SCTPHOST
2. ADD SCTPHOST2EPGRP
3. ADD USERPLANEHOST
4. ADD UPHOST2EPGRP
5. ADD X2
652
eRAN
Reconfiguration Guide
If...
The new Ethernet port is used to
bear an OM channel
An IP clock link is set up on the
new Ethernet port
The new Ethernet port is used to
bear a link that supports BFD
The new Ethernet port is used
for IPsec negotiation
● Link mode
Table 1-220 Reconfiguration scheme for modifying the Ethernet port number
(MML commands, in link mode)
If...
The IP route is set up on the old
Ethernet port
An S1 link is set up on the old
Ethernet port
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
Add services that use the new Ethernet
port by running the following command:
ADD OMCH
Add services that use the new Ethernet
port by running the following command:
ADD IPCLKLINK
Add services that use the new Ethernet
port by running the following command:
ADD BFDSESSION
Change IP addresses corresponding to
the IKE peer and ACL rules to the old
device IP addresses by running the
following commands:
1. MOD IKEPEER
2. MOD ACLRULE
Then...
Remove the MOs associated with the
old Ethernet port number by running
the following command:
RMV IPRT
Remove the MOs associated with the
old Ethernet port number by running
the following commands:
1. RMV S1INTERFACE
2. RMV CPBEARER
3. RMV SCTPLNK
4. (Optional) RMV
CNOPERATORIPPATH if an IP path
has been associated with an operator
5. (Optional) RMV ENODEBPATH if an
IP path has been associated with an
eNodeB
6. (Optional) RMV IPPATH if an IP path
has been configured
653
eRAN
Reconfiguration Guide
If...
An X2 link is set up on the old
Ethernet port
An OM channel is set up on the
old Ethernet port
An IP clock link is set up on the
old Ethernet port
A link set up on the old Ethernet
port supports BFD
The old Ethernet port number is
used for IPsec negotiation and
the local IP address of the IKE
peer is not 0.0.0.0
- Remove all device IP addresses
- Add all original device IP addresses and
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
Remove the MOs associated with the
old Ethernet port number by running
the following commands:
1. RMV X2INTERFACE
2. RMV CPBEARER
3. RMV SCTPLNK
4. RMV IPPATH
5. (Optional) RMV
CNOPERATORIPPATH if an IP path
has been associated with an operator
6. (Optional) RMV ENODEBPATH if an
IP path has been associated with an
eNodeB
7. (Optional) RMV IPPATH if an IP path
has been configured
Remove the MOs associated with the
old Ethernet port number by running
the following command:
RMV OMCH
Remove the MOs associated with the
old Ethernet port number by running
the following command:
RMV IPCLKLINK
Remove the MOs associated with the
old Ethernet port number by running
the following command:
RMV BFDSESSION
Set the local IP address of the IKE peer
to 0.0.0.0 by running the following
command:
MOD IKEPEER
associated with the old Ethernet port
number by running the following
command:
RMV DEVIP
associate them with the new Ethernet
port number by running the following
command:
ADD DEVIP
654
eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The new Ethernet port is used to Add services that use the new device IP
bear an IP route address by running the following
command:
ADD IPRT

The new Ethernet port is used to Add services that use the new device IP
bear an S1 link address by running the following
commands:
1. ADD SCTPLNK
2. ADD IPPATH
3. ADD ENODEBPATH
4. ADD CNOPERATORIPPATH
5. ADD CPBEARER
6. ADD S1INTERFACE

The new Ethernet port is used to Add services that use the new device IP
bear an X2 link address by running the following
commands:
1. ADD SCTPLNK
2. ADD IPPATH
3. ADD ENODEBPATH
4. ADD CNOPERATORIPPATH
5. ADD CPBEARER
6. ADD X2INTERFACE

The new Ethernet port is used to Add services that use the new device IP
bear an OM channel address by running the following
command:
ADD OMCH

An IP clock link is set up on the Add services that use the new device IP
new Ethernet port address by running the following
command:
ADD IPCLKLINK

The new Ethernet port is used to Add services that use the new device IP
bear a link that supports BFD address by running the following
command:
ADD BFDSESSION

The new Ethernet port is used Change IP addresses corresponding to

for IPsec negotiation
the IKE peer and ACL rules to the old
device IP addresses by running the
following commands:
1. MOD IKEPEER
2. MOD ACLRULE

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 655

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
N/A

1.8.12.2 Engineering Preparation

This section describes the engineering preparation for modifying an Ethernet port
number, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Information Collection
Table 1-221 describes the information to be collected for data preparation.

Table 1-221 Information to be collected

Information Description

Base station information Base station identification (BS ID).

Ethernet port number New Ethernet port number.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Data to be prepared is listed in the following tables.

● MAE-Deployment

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 656

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-222 Data preparation for modifying the Ethernet port number (MAE-
Deployment)

SN Ope MO Configuration Reference

rati
on

1 Dele DEVIP Remove all device IP addresses

te associated with the old Ethernet port
number.

2 Add DEVIP Add device IP addresses and set the

Ethernet port number to the new
Ethernet port number. Other
information remains unchanged.

● MML commands, in endpoint mode

Table 1-223 Data preparation for modifying the Ethernet port number (MML
commands, in endpoint mode)

SN Operation MML Command Configuration

Type Reference

1 Remove the RMV IPRT -

MOs RMV S1
associated
with the old RMV X2
Ethernet RMV
port number. SCTPHOST2EPGRP
RMV SCTPHOST
RMV UPHOST2EPGRP
RMV
USERPLANEHOST
(Optional if an IP
path has been
associated with an
operator) RMV
CNOPERATORIPPATH
(Optional if an IP
path has been
associated with the
eNodeB) RMV
ENODEBPATH
(Optional if an IP
path has been
configured) RMV
IPPATH
RMV OMCH
RMV BFDSESSION

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 657

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Operation MML Command Configuration

Type Reference

2 Modify the MOD IKEPEER Set the local IP address

IKE peer. to 0.0.0.0.

3 Remove the RMV DEVIP Remove all device IP

device IP addresses associated
address. with the old Ethernet
port number.

4 Add a device ADD DEVIP Add all original device

IP address. IP addresses, associate
them with the new
5 Add services ADD IPRT Ethernet port number,
that use the ADD SCTPHOST and set the Ethernet
new port number to the
Ethernet ADD
SCTPHOST2EPGRP new Ethernet port
port. number. Other
ADD information remains
USERPLANEHOST unchanged.
ADD UPHOST2EPGRP
ADD S1
ADD X2
ADD OMCH
ADD IPCLKLINK
ADD BFDSESSION

6 Modify the MOD IKEPEER Set the local IP address

IKE peer and to the original device
ACL rule. IP address.

7 Modify the SET ETHPORT Make them consistent

attributes, with those of the old
rate, and Ethernet port number.
duplex mode
of the new
Ethernet
port number.

● MML commands, in link mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 658

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Operation MML Command Configuration

Type Reference

1 Remove the RMV IPRT -

MOs RMV S1INTERFACE
associated
with the old RMV CPBEARER
Ethernet port RMV SCTPLNK
number. (Optional) RMV
CNOPERATORIPPATH
if an IP path has been
associated with an
operator
(Optional) RMV
ENODEBPATH if an IP
path has been
associated with an
eNodeB
(Optional) RMV
IPPATH if an IP path
has been configured
RMV OMCH
RMV BFDSESSION

2 Modify the MOD IKEPEER Set the local IP

IKE peer. address to 0.0.0.0.

3 Remove the RMV DEVIP Remove all device IP

device IP addresses associated
address. with the old Ethernet
port number.

4 Add device IP ADD DEVIP Add all original device

addresses. IP addresses, associate
them with the new
5 Add services ADD IPRT Ethernet port number,
that use the ADD SCTPLNK and set the Ethernet
device IP port number to the
address. ADD IPPATH
new Ethernet port
ADD ENODEBPATH number. Other
ADD information remains
CNOPERATORIPPATH unchanged.
ADD CPBEARER
ADD S1INTERFACE
ADD OMCH
ADD IPCLKLINK
ADD BFDSESSION

6 Modify the MOD IKEPEER Set the local IP

IKE peer and address to the original
ACL rule. device IP address.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 659

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Operation MML Command Configuration

Type Reference

7 Modify the SET ETHPORT Make them consistent

attributes, with those of the old
rate, and Ethernet port number.
duplex mode
of the new
Ethernet port
number.

Data Preparation Mode

The recommended reconfiguration methods are as follows:
● If the Ethernet port to be changed is not used as a port for remote
maintenance, you are advised to use the MAE-Deployment for batch
reconfiguration.
● If the number of the Ethernet port to be changed is used for an X2 link and it
is expected to update the device IP address referenced by the peer base
station automatically, you are advised to use the MAE-Deployment for batch
reconfiguration.
● If the number of the Ethernet port to be changed is used as a port for remote
maintenance, the MAE will be disconnected from the NE during data delivery
and activation, resulting in execution failure of incremental scripts on the
MAE-Deployment. Therefore, you are advised to use MML commands.
Prepare data for each reconfiguration method as follows:
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Changing the Ethernet Port Number"). For
details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

● Endpoint mode
In the following example, the Ethernet port number is changed from 0 to 1,
the Ethernet port number is associated with only one device IP address
192.168.7.186, and this IP address is referenced by the MOs SCTPHOST,
USERPLANEHOST, OMCH, IPRT, and IPCLKLNK.
If OMCH parameters are modified by mistake, the OMCH may be
disconnected and cannot be restored within a long period of time. To avoid
service unavailability due to the OMCH disconnection, you are advised to turn
on the automatic rollback switch of the CB by running the CFM CB command
before configuring data. For example, CFM CB: MODE=UNFORCED,

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 660

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NAME="CB1", COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,

RBKCONDITION=OMCH_FAULT;.
/*Removing the IP route*/
/*There may be more than one route related to this device IP address. Remove all IP routes related to
the device IP address. You can run the DSP IPRT command to query routes related to the device IP
address.*/
RMV IPRT: RTIDX=0;
/*If the device IP address is used for an S1 link, run the RMV S1 command. If the device IP address is
used for an X2 link, run the RMV X2 command. In the following example, the RMV S1 command is
executed.*/
/*Removing the S1 object*/
RMV S1: S1Id=0;
/*Removing the SCTP host from the endpoint group*/
RMV SCTPHOST2EPGRP: EPGROUPID=0, SCTPHOSTID=0;
/*Removing the SCTP host*/
RMV SCTPHOST: SCTPHOSTID=0;
/*Removing the user-plane host from the endpoint group*/
RMV UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;
/*Removing a user-plane host*/
RMV USERPLANEHOST: UPHOSTID=0;
/*If an IP path has been configured and the IP path has been associated with an operator or eNodeB,
run the following commands:*/
/*Removing the associations of the IP path with the operator and eNodeB and then the IP path*/
RMV CNOPERATORIPPATH: IpPathId=0;
RMV ENODEBPATH: IpPathId=0;
RMV IPPATH: PATHID=0;
/*Removing the OM channel*/
RMV OMCH: FLAG=MASTER;
/*Removing the IP clock link*/
RMV IPCLKLINK: LN=0;
/*Removing the BFD session*/
RMV BFDSESSION: SN=7, BFDSN=0;
/*If the IP address to be changed is used for IPsec negotiation and the local IP address of the IKE peer
is not 0.0.0.0, perform the following operations:*/
/*Setting the local IP address of the IKE peer to 0.0.0.0*/
MOD IKEPEER: PEERNAME="ike", LOCALIP="0.0.0.0";
/*Removing the device IP address*/
RMV DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.7.186";
/*Adding a device IP address*/
ADD DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, IP="192.168.7.166",
MASK="255.255.252.0";
/*Adding an IP route*/
/*If multiple IP routes are associated with the device IP address, add all the associated IP routes.*/
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="172.169.1.5", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.7.1";
/*Adding an SCTP host*/
ADD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="192.168.7.166",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=1024, SCTPTEMPLATEID=0;
/*Adding the SCTP host to the endpoint group*/
ADD SCTPHOST2EPGRP: EPGROUPID=0, SCTPHOSTID=0;
/*Adding a user-plane host*/
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.7.186",
IPSECSWITCH=DISABLE;
/*Adding the user-plane host to the endpoint group*/
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;
/*If the device IP address is used for an S1 link, run the ADD S1 command. If the device IP address is
used for an X2 link, run the ADD X2 command. In the following example, the ADD S1 command is
executed.*/
/*Adding an S1 object*/
ADD S1: S1Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=0, UpEpGroupId=0;
/*Adding an OM channel*/
ADD OMCH: IP="192.168.7.186", MASK="255.255.255.0", PEERIP="10.141.142.253",
PEERMASK="255.255.255.0", BEAR=IPV4, SN=7, SBT=BASE_BOARD, BRT=NO;
/*Adding an IP clock link*/
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, CIP="192.168.7.186", SIP="192.168.49.249",
PROFILETYPE=1588V2;
/*Adding a BFD session*/
ADD BFDSESSION: SN=7, BFDSN=0, SRCIP="192.168.1.186", DSTIP="192.168.7.187", HT=SINGLE_HOP,
DSCP=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 661

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If the IKE peer was modified, perform the following operations:/*Changing the local IP address of the
IKE peer to the new device IP address*/MOD IKEPEER: PEERNAME="ike", LOCALIP="192.168.7.186";

● Link mode
In the following example, the Ethernet port number is changed from 0 to 1,
the Ethernet port number is associated with only one device IP address
192.168.7.186, and this IP address is referenced by MOs SCTPHOST,
USERPLANEHOST, OMCH, IPRT, and IPCLKLNK.
If OMCH parameters are modified by mistake, the OMCH may be
disconnected and cannot be restored within a long period of time. To avoid
service unavailability due to the OMCH disconnection, you are advised to turn
on the automatic rollback switch of the CB by running the CFM CB command
before configuring data. For example, CFM CB: MODE=UNFORCED,
NAME="CB1", COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Removing the IP route*/
/*There may be more than one route related to this device IP address. Remove all IP routes related to
the device IP address. You can run the DSP IPRT command to query routes related to the device IP
address.*/
RMV IPRT: RTIDX=0;
/*Removing the S1 interface*/
RMV S1INTERFACE: S1InterfaceId=0;
/*Removing the CP bearer*/
RMV CPBEARER: CPBEARID=0, FLAG=MASTER;
/*Removing the SCTP link*/
RMV SCTPLNK: SCTPNO=0;
/*If an IP path has been configured and the IP path has been associated with an operator or eNodeB,
run the following commands:*/
/*Removing the associations of the IP path with the operator and eNodeB and then the IP path*/
RMV CNOPERATORIPPATH: IpPathId=0;
RMV ENODEBPATH: IpPathId=0;
RMV IPPATH: PATHID=0;
/*Removing the OM channel*/
RMV OMCH: FLAG=MASTER;
/*Removing the IP clock link*/
RMV IPCLKLINK: LN=0;
/*Removing the BFD session*/
RMV BFDSESSION: SN=7, BFDSN=0;
/*If the IP address to be changed is used for IPsec negotiation and the local IP address of the IKE peer
is not 0.0.0.0, perform the following operations:*/
/*Setting the local IP address of the IKE peer to 0.0.0.0*/
MOD IKEPEER: PEERNAME="ike", LOCALIP="0.0.0.0";
/*Removing the device IP address*/
RMV DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.7.186";
/*Adding a device IP address*/
ADD DEVIP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, IP="192.168.7.186",
MASK="255.255.252.0";
/*Adding an IP route*/
/*If multiple IP routes are associated with the device IP address, add all the associated IP routes.*/
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="172.169.1.5", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.7.1";
/*Adding an SCTP link*/
ADD SCTPLNK: SCTPNO=0, CN=0, SRN=0, SN=7, LOCIP="192.168.7.186", LOCPORT=2911,
PEERIP="172.169.1.5", PEERPORT=2910, AUTOSWITCH=ENABLE, DESCRI="";
/*Adding an IP path and associating the IP path with an operator and eNodeB*/
ADD IPPATH: PATHID=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE,
LOCALIP="192.168.7.186", PEERIP="172.169.2.3", ANI=0, APPTYPE=S1, PATHTYPE=ANY;
ADD ENODEBPATH: IpPathId=0, AppType=S1;
ADD CNOPERATORIPPATH: IpPathId=0, CnOperatorId=0;
/*Adding a CP bearer*/
ADD CPBEARER: CPBEARID=0, BEARTYPE=SCTP, FLAG=MASTER;
/*Adding an S1 interface*/
ADD S1INTERFACE: S1InterfaceId=0, S1CpBearerId=0, CnOperatorId=0, MmeRelease=Release_R9;
/*Adding an OM channel*/
ADD OMCH: IP="192.168.7.186", MASK="255.255.255.0", PEERIP="10.141.142.253",

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 662

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

PEERMASK="255.255.255.0", BEAR=IPV4, SN=7, SBT=BASE_BOARD, BRT=NO;

/*Adding an IP clock link*/
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, CIP="192.168.7.186", SIP="192.168.49.249",
PROFILETYPE=1588V2;
/*Adding a BFD session*/
ADD BFDSESSION: SN=7, BFDSN=0, SRCIP="192.168.1.186", DSTIP="192.168.7.167", HT=SINGLE_HOP,
DSCP=0;
If the IKE peer was modified, perform the following operations:
/*Changing the local IP address of the IKE peer to the new device IP address*/
MOD IKEPEER: PEERNAME="ike", LOCALIP="192.168.7.186";

1.8.12.3 Engineering Implementation

This section describes the engineering implementation for modifying an Ethernet
port number, including prerequisites, context, and procedure.

Prerequisites
Related information and configuration data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

If the Ethernet port whose number is to be changed is used as a port for

remote maintenance, you are advised to run MML commands on the LMT to
deliver the data to the eNodeB and then activate the data.

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the LMT to deliver the batch configuration script prepared according
to Engineering Preparation > Data Preparation to the base station and
activate the script on the base station. For details, see 1.3.2 Running
MML Commands on the LMT.
d. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 663

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see Setting the Maintenance Mode of the eNodeB to

NORMAL.
● Remote Operations

If the Ethernet port whose number is to be changed is not used as a port for
remote maintenance, you are advised to use the MAE-Deployment to deliver
the data to the base station and then activate the data.

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Deliver the configuration data to the eNodeB and activate the data. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
c. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.8.12.4 Engineering Verification

This section describes how to verify the modification of an Ethernet port number.

Procedure
Step 1 Verify that no related alarm is reported.

For example:

● ALM-25886 IP Path Fault

● ALM-25901 Remote Maintenance Link Failure
● ALM-25888 SCTP Link Fault
● ALM-26263 IP Clock Link Failure
● ALM-26266 Time Synchronization Failure
● ALM-25899 BFD Session Fault
● ALM-25891 IKE Negotiation Failure
● ALM-29201 S1 Interface Fault
● ALM-29204 X2 Interface Fault

If any alarm is reported, clear the alarm according to the instructions in 3900 &
5900 Series Base Station Alarm Reference.
Step 2 Run the DSP ETHPORT command to verify that all device IP addresses associated
with the old Ethernet port number have been associated with the new Ethernet
port number.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 664

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.12.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Roll back the Ethernet port connection.

Step 3 Verify that engineering rollback is successful by following the instructions provided
in 1.8.12.4 Engineering Verification.
----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 665

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.13 Modifying the Ethernet Port Number (New Model)

This section describes how to modify an Ethernet port number (new model).

1.8.13.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for modifying an Ethernet port
number.

Application Scenario
The previously planned Ethernet port numbers are inappropriate and a new plan is
required.

Reconfiguration Impact
● If the Ethernet port to be changed is used as a port for remote maintenance,
the MAE-Access and MAE-Deployment are disconnected from the NE after
the old OM channel becomes invalid and before the new OM channel is set
up.
● If the Ethernet port number to be changed is used for service transmission,
the service link (such as S1 or X2) reestablishment is required. During the
reestablishment, services on the link will be interrupted.
● If the Ethernet port number to be changed is used for IPsec negotiations, an
IPsec renegotiation is required. During the renegotiation, services on the IPsec
tunnel will be interrupted.

Reconfiguration Scheme
The reconfiguration schemes using the MAE-Deployment and using MML
commands are different because you cannot directly remove device IP addresses
associated with the Ethernet port number using MML commands.

The reconfiguration scheme using the MAE-Deployment is as follows:

IPv4:

1. Remove all device IP addresses associated with the old Ethernet port number.
2. Add all original device IP addresses and associate them with the new Ethernet
port number.
3. Modify the attributes, rate, and duplex mode of the new Ethernet port
number and make them consistent with those of the old Ethernet port
number.

IPv6:

1. Modify the attributes of the new Ethernet port number.

2. Modify the interface.

Table 1-224 and Table 1-225 describe the reconfiguration scheme using MML
commands.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 666

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Endpoint mode

Table 1-224 Reconfiguration scheme for modifying the Ethernet port number
(MML commands, in endpoint mode)
SN Step MML Command

1 Set the port ID of the new Ethernet SET ETHPORT

port.

2 Change the port ID of the old MOD INTERFACE

Ethernet port to the port ID of the
new Ethernet port in the INTERFACE
MO.

● Link mode

Table 1-225 Reconfiguration scheme for modifying the Ethernet port number
(MML commands, in link mode)
SN Step MML Command

1 Set the port ID of the new Ethernet SET ETHPORT

port.

2 (Optional) If CnOperatorIpPath, 1. (Optional) RMV

eNodeBPath, and IPPATH have CNOPERATORIPPATH if
been configured, remove the MOs an IP path has been
associated with the old Ethernet associated with an
port number. operator
2. RMV ENODEBPATH if an
IP path has been
associated with an
eNodeB
3. RMV IPPATH if an IP path
has been configured

3 Change the port ID of the old MOD INTERFACE

Ethernet port to the port ID of the
new Ethernet port in the INTERFACE
MO.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 667

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Step MML Command

4 (Optional) If CnOperatorIpPath, 1. ADD

eNodeBPath, and IPPATH have CNOPERATORIPPATH if
been removed, add services that use an IP path has been
the new Ethernet port. associated with an
operator
2. ADD ENODEBPATH if an
IP path has been
associated with an
eNodeB
3. ADD IPPATH if an IP path
has been configured

Topology Change
N/A

1.8.13.2 Engineering Preparation

This section describes the engineering preparation for modifying an Ethernet port
number, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also describes the data preparation
mode and provides MML configuration script examples.

Information Collection
Table 1-226 describes the information to be collected for data preparation.

Table 1-226 Information to be collected

Information Description

Base station information Base station identification (BS ID).

Ethernet port number New Ethernet port number.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 668

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Security Certificate Preparation

N/A

Data Preparation
Data to be prepared is listed in the following tables.
● MAE-Deployment

Table 1-227 Data preparation for modifying the Ethernet port number (MAE-
Deployment, IPv4)
SN Ope MO Configuration Reference
rati
on

1 Dele IPADDR4 Remove all IPv4 addresses associated

te with the old Ethernet port number.

2 Add IPADDR4 Add IPv4 addresses and set the

Ethernet port number to the new
Ethernet port number. Other
information remains unchanged.

Table 1-228 Data preparation for modifying the Ethernet port number (MAE-
Deployment, IPv6)
SN Ope MO Configuration Reference
rati
on

1 Mod ETHPORT Change the attributes and port ID in

ify the ETHPORT MO to the target
values.

2 Mod INTERFACE Change the port ID of the MO to the

ify target value.

● MML commands, in endpoint mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 669

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-229 Data preparation for modifying the Ethernet port number (MML
commands, in endpoint mode)
SN Ope MML Command Configuration Reference
rati
on
Typ
e

1 Set SET ETHPORT Change other attributes and port ID in

the the ETHPORT MO to the target
port values.
ID
of
the
new
Ethe
rnet
port.

2 Cha MOD INTERFACE Change the value of Port ID to the

nge target value.
the
port
ID
of
the
old
Ethe
rnet
port
to
the
port
ID
of
the
new
Ethe
rnet
port
in
the
INT
ERF
ACE
MO.

● MML commands, in link mode

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 670

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-230 Data preparation for modifying the Ethernet port number (MML
commands, in link mode)
SN Operation Type MML Command

1 Set the port ID of the new Ethernet SET ETHPORT

port.

2 Remove the MOs associated with (Optional) RMV

the old Ethernet port number.
CNOPERATORIPPATH if an
IP path has been associated
with an operator
(Optional) RMV
ENODEBPATH if an IP path
has been associated with an
eNodeB
(Optional) RMV IPPATH if
an IP path has been
configured

3 Change the port ID of the old MOD INTERFACE

Ethernet port to the port ID of the
new Ethernet port in the INTERFACE
MO.

4 Add services that use the device IP ADD IPPATH

address. ADD ENODEBPATH
ADD CNOPERATORIPPATH

Data Preparation Mode

The recommended reconfiguration methods are as follows:
● If the Ethernet port to be changed is not used as a port for remote
maintenance, you are advised to use the MAE-Deployment for batch
reconfiguration.
● If the number of the Ethernet port to be changed is used for an X2 link and it
is expected to update the device IP address referenced by the peer base
station automatically, you are advised to use the MAE-Deployment for batch
reconfiguration.
● If the number of the Ethernet port to be changed is used as a port for remote
maintenance, the MAE will be disconnected from the NE during data delivery
and activation, resulting in execution failure of incremental scripts on the
MAE-Deployment. Therefore, you are advised to use MML commands.
Prepare data for each reconfiguration method as follows:
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Changing the Ethernet Port Number"). For
details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 671

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands: Prepare MML configuration scripts based on the

preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

Endpoint mode
In the following example, the Ethernet port number is changed from 0 to 1, the
Ethernet port number is associated with only one device IP address 192.168.7.186,
and this IP address is referenced by the MOs SCTPHOST, USERPLANEHOST,
OMCH, IPRT, and IPCLKLNK.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Setting the port ID of the new Ethernet port*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=1, PORTID=1;
/*Changing the port ID of the old Ethernet port to the port ID of the new Ethernet port in the INTERFACE
MO*/
MOD INTERFACE: ITFID=0, PORTID=1

1.8.13.3 Engineering Implementation

This section describes the engineering implementation for modifying an Ethernet
port number, including prerequisites, context, and procedure.

Prerequisites
The information and data required for modifying the Ethernet port number are
ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operation
If the number of the Ethernet port to be changed is used as a port for remote
maintenance, you are advised to run MML commands on the LMT to deliver
the data to the eNodeB and then activate the data.
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 672

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see 1.11.1 Setting the eNodeB Maintenance Mode.

b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the LMT to deliver the batch configuration script prepared according
to Engineering Preparation > Data Preparation to the base station and
activate the script on the base station. For details, see 1.3.2 Running
MML Commands on the LMT.
d. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Remote Operation
If the Ethernet port whose number is to be changed is not used as a port for
remote maintenance, you are advised to use the MAE-Deployment to deliver
the data to the base station and then activate the data.
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Deliver the configuration data to the eNodeB and activate it. For details,
see the interactive operation guide Delivering Data to Base Stations
and Activating the Data.
c. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.8.13.4 Engineering Verification

This section describes how to verify the modification of an Ethernet port number.

Procedure
Step 1 Verify that no related alarms have been reported.
For example:
● ALM-25886 IP Path Fault
● ALM-25901 Remote Maintenance Link Failure
● ALM-25888 SCTP Link Fault
● ALM-25952 User Plane Path Fault

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 673

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● ALM-25954 User Plane Fault

● ALM-26263 IP Clock Link Failure
● ALM-26266 Time Synchronization Failure
● ALM-25899 BFD Session Fault
● ALM-25891 IKE Negotiation Failure
● ALM-29201 S1 Interface Fault
● ALM-29204 X2 Interface Fault

If any alarm is reported, clear the alarm by referring to 3900 & 5900 Series Base
Station Alarm Reference.
Step 2 Run the DSP ETHPORT command to verify that all device IP addresses associated
with the old Ethernet port number have been associated with the new Ethernet
port number.

----End

1.8.13.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 674

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Roll back the Ethernet port connection.

Step 3 Verify the engineering rollback by referring to the procedures in 1.8.13.4
Engineering Verification.

----End

1.8.14 MME Dual-homing Reconfiguration

This section describes how to reconfigure an MME to configure two SCTP links
between the MME and eNodeB.

Prerequisites
● Two IP addresses have been configured for the MME.
● There are two SCTP links between the eNodeB and MME. The two SCTP links
function as a backup for each other.

Context
This chapter describes operations on the eNodeB side for configuring two SCTP
links between an MME and eNodeB. The MME is an NE on the core network side.
The operations and information related to the MME are described in the
associated MME manual. For example, whether an MME needs to be added,
information about the hardware, software, license files, and security certificates
required on the core network side as well as operations such as hardware and
software installation, license loading, and security certificate activation.

1.8.14.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for MME dual-homing.

Application Scenario
● Multiple links have been configured between an MME and an eNodeB.
● The transmission networking scheme of an eNodeB needs to be changed from
a single link to MME dual-homing.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 675

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Impact
During MME dual-homing reconfiguration, services will be interrupted for less
than 1 minute because S1 negotiation restarts. You are advised to perform the
reconfiguration when the traffic is light.

Reconfiguration Scheme
Figure 1-120 shows the procedure for configuring MME dual-homing.
NOTE

If the eNodeB operates in link transmission mode, change the transmission mode to endpoint
mode before the reconfiguration.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Figure 1-120 Procedure for configuring MME dual-homing in endpoint mode

(IPv4)

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 676

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-121 Procedure for configuring MME dual-homing in endpoint mode

(IPv4)

Figure 1-122 Procedure for configuring MME dual-homing in endpoint mode

(IPv6)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 677

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Figure 1-123 shows the topologies before and after the reconfiguration.

Figure 1-123 Topologies before and after the reconfiguration

1.8.14.2 Engineering Preparation

This section describes the engineering preparation for MME dual-homing
reconfiguration, including information collection and preparation of hardware,
software, license files, security certificates, and data. It also describes the data
preparation mode and provides MML configuration script examples.

Information Collection
Table 1-231 describes the information to be collected before adding an MME
connection on the eNodeB side.

Table 1-231 Information to be collected

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask (IPv4)/prefix length (IPv6), and route
eNodeB to the MME priority.

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the MME

Control-plane IP Peer IP address of an SCTP link, which is an S1 signaling

address of the MME link automatically set up by the eNodeB.

MME port number Peer port number of the SCTP link automatically
established by the eNodeB

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 678

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-232 Data preparation for MME dual-homing reconfiguration

SN Ope MO Configuration Reference
ratio
n

1 Add IPv4: IPRT/SRCIPRTa Add an IP route from the eNodeB to the

(old model)/ MME with the Destination IP
IPROUTE4/ parameter set to the control-plane IP
SRCIPROUTE4b (new address of the MME.
model) For details, see LTE and NR NSA S1 and
IPv6: IPADDR6 (new X2 Self-Management Feature Parameter
model) Description.

2 Add IPv4: VLANMAP

IPv6: N/A

3 Modi SCTPLNK Add the second IP address for the peer

fy of SCTP link, by setting the Second Peer
IP Address parameter to the standby
control-plane IP address of the MME. Do
not modify the other parameters.
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 679

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

4 Modi SCTPPEER Add the second IP address for the MME,

fy by setting the Second Peer IP Address
parameter to the standby control-plane
IP address of the MME. Do not modify
the other parameters.
For details, see LTE and NR NSA S1 and
X2 Self-Management Feature Parameter
Description.

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.
b: To simplify configurations when one IPv4 address maps multiple destination
IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "MME Dual-belonging Reconfiguration"). For
details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following example of MML
configuration scripts.

MML Configuration Script Example

In the following example, an IP route is added.

If OMCH parameters are modified by mistake, the OMCH may be disconnected

and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

NOTE

License file update is not involved in this scenario.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 680

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.
/*Adding a second IP route from the eNodeB to MME*/
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="192.168.3.3", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.3.1";
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.3.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SET
PRIO=DISABLE;
/*Modifying the information of the SCTP peer*/
MOD SCTPPEER:SCTPPEERID=0, IPVERSION=IPv4, SIGIP2V4="192.168.3.3",
USERLABEL="192.168.3.3&192.168.3.3";

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.
/*Adding a second IP route from the eNodeB to MME*/
ADD IPROUTE4: RTIDX=0, DSTIP="192.168.3.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.3.1";
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.3.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SET
PRIO=DISABLE;
/*(Optional) Configuring the VLAN when the Interface Type is VLAN*/
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=71, VLAN=101, VRFIDX=0;
/*Modifying the information of the SCTP peer*/
MOD SCTPPEER:SCTPPEERID=0, IPVERSION=IPv4, SIGIP2V4="192.168.3.3",
USERLABEL="192.168.3.3&192.168.3.3";

1.8.14.3 Engineering Implementation

This section describes the engineering implementation for MME dual-homing
reconfiguration, including prerequisites, context, and procedure.

Prerequisites
Information and data for the second IP address of the MME are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations

Using the MAE-Deployment:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 681

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
c. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
d. Deliver the configuration data to the eNodeB and activate the data. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
e. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
Using MML commands:
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
d. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 682

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see Setting the Maintenance Mode of the eNodeB to

NORMAL.

----End

1.8.14.4 Engineering Verification

This section describes how to verify the MME dual-homing reconfiguration.

Procedure
Step 1 Verify that no cell-related alarm has been reported.

If any alarm has been reported, clear the alarm according to instructions in 3900
& 5900 Series Base Station Alarm Reference.
Step 2 Run the DSP SCTPLNK command to check whether there is a second control-
plane peer IP address for the SCTP link between the eNodeB and the MME.

If the second peer IP address of the SCTP link is different from the control-plane IP
address of the MME, perform the following steps:

If... Then...

The reconfiguration is View the modified data file to check whether the
performed on the second peer IP address is the same as the second
MAE-Deployment control-plane IP address of the MME:
● If they are different, modify the configuration data
file again and import it into the system. Then
perform the operations in Engineering
Implementation again to deliver the data to the
base station and then activate it.
● If they are the same, an error has occurred when the
data is imported into the system or delivered to the
base station. In this situation, contact Huawei
technical support or dial the Huawei technical
support hotline.

The reconfiguration is Check whether the second peer IP address in the script
performed by using is the same as the second control-plane IP address of
MML commands the MME:
● If they are different, modify the parameters in the
script. Run the MOD SCTPPEER command to
change the peer IP address.
● If they are the same, contact Huawei technical
support or dial the Huawei technical support
hotline.

Step 3 Ping the second control-plane IP address of the MME.

If it cannot be pinged, check whether the SCTP link configuration is correct,

including the IP route from the eNodeB to the MME.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 683

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The configuration is Modify the configuration.

incorrect

The configuration is Check the configurations and cable connections of the

correct intermediate devices between the eNodeB and MME:
● If the configurations are incorrect or the cables are
disconnected, modify the configurations or
reconnect the cables.
● If the configurations or cable connections are
correct, contact Huawei technical support or dial the
Huawei technical support hotline.

----End

1.8.14.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Roll back the reconfiguration data.
● Using MML commands:
a. Run the DLD CFGFILE command to download the original configuration
file.
For example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="",
ENCRYPTMODE=UNENCRYPTED;
b. Run the ACT CFGFILE command to activate the original configuration
file.
For example: ACT CFGFILE: EFT=IMMEDIATELY;
Step 2 Restore the physical connections.
Step 3 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 4 Verify that engineering rollback is successful according to instructions in
Engineering Verification.

----End

1.8.15 Changing the Transmission Mode from Link Mode to

Endpoint Mode (Only for IPv4 Transmission)
This section describes how to change the transmission mode from link mode to
endpoint mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 684

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.15.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the transmission mode
from link mode to endpoint mode.

Application Scenario
Currently, link mode is used for transmission over the S1 or X2 interface for most
eNodeBs. However, transmission links need to be manually configured in this
mode while the endpoint mode supports self-setup of transmission links. Endpoint
mode will be commonly used in the future.

Reconfiguration Impact
When configuring endpoint mode, the KPIs on the live network are not affected.
When removing IP paths in the existing link mode, UEs on the live network will be
disconnected from and then re-access the network, affecting the service drop rate
and throughput in the cell.

Reconfiguration Scheme
The transmission mode can be changed from link mode to endpoint mode
separately for the S1 and X2 links. The following describes how to separately
change the transmission modes of an S1 link and an X2 link from link mode to
endpoint mode.
● Reconfiguring an S1 link
Figure 1-124 shows the procedure for configuring endpoint mode for an S1
link.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 685

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-124 Configuring endpoint mode for an S1 link

S1 interfaces include the S1 interface on the control plane (S1-C) and S1

interface on the user plane (S1-U). Either the S1-C or S1-U interface or both
of them can be changed from link mode to endpoint mode. As shown in the
preceding figure, the S1-C cannot be automatically set up in either link or
endpoint mode. All parameters must be set manually in both modes.
When configuring endpoint mode, the following MOs must be configured:
EPGROUP, SCTPTEMPLATE, SCTPHOST, SCTPPEER, USERPLANEHOST,
USERPLANEPEER, and S1. The S1-C interface and S1-U interface must be
bound to the EPGROUP MO by running the ADD SCTPHOST2EPGRP, ADD
SCTPPEER2EPGRP, and ADD UPHOST2EPGRP commands. Then, the
EPGROUP MO needs to be bound to the S1 MO.
Remove the IPPATH, eNodeBPath, and CnOperatorIpPath MOs used by the
S1 link because they are no longer used in endpoint mode. Otherwise, alarms
may be reported.
NOTE

Removing existing S1 interfaces will cause online UEs to disconnect from the network.
When S1 interfaces become normal after the reconstruction, UEs can re-access the
network.
● Reconfiguring an X2 link

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 686

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-125 shows the procedure for configuring endpoint mode for an X2
link.

Figure 1-125 Configuring endpoint mode for an X2 link

X2 interfaces include the X2 interface on the control plane (X2-C) and X2

interface on the user plane (X2-U). Either the X2-C or X2-U interface or both
of them can be changed from link mode to endpoint mode. In most cases,
both X2-C and X2-U interfaces are changed from link mode to endpoint
mode. This is because there are many X2 interfaces between eNodeBs and the
neighbor relationship of eNodeBs may change. The endpoint mode facilitates
X2 link self-setup.
When configuring endpoint mode, the following MOs must be configured:
EPGROUP, SCTPTEMPLATE, SCTPHOST, SCTPPEER, USERPLANEHOST,
USERPLANEPEER, and X2. The X2-C interface and X2-U interface must be
bound to the EPGROUP MO by running the ADD SCTPHOST2EPGRP, ADD
SCTPPEER2EPGRP, and ADD UPHOST2EPGRP commands. Then, the
EPGROUP MO needs to be bound to the X2 MO.
Remove the IPPATH, eNodeBPath, and CnOperatorIpPath MOs used by the
X2 link because they are no longer used in endpoint mode. Otherwise, alarms
may be reported.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 687

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
N/A

1.8.15.2 Engineering Preparation

This section describes the engineering preparation for changing the transmission
mode from link mode to endpoint mode, including information collection and
preparation of hardware, software, license files, security certificates, and data. It
also describes the data preparation mode and provides MML configuration script
examples.

Information Collection
Table 1-233 describes the information to be collected before the reconfiguration.

Table 1-233 Information to be collected

Information Description

IPPATH IP path information of the network that needs to be

reconstructed

S1Interface S1 interface information that needs to be collected in

scenarios where the S1 interface transmission mode is
changed

X2Interface X2 interface information that needs to be collected in

scenarios where the X2 interface transmission mode is
changed

CPBEARER CP bearer associated to the S1 interface and X2

interface

Local IP addresses Local IP addresses of the link that needs to be

reconstructed, including the signaling and service IP
addresses

Peer MME Peer MME IP addresses of the link to be reconstructed

information in scenarios where the S1 interface transmission mode
is changed

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 688

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-234 Data preparation for changing the transmission mode from link mode
to endpoint mode

SN Ope MO Configuration Reference

ratio
n

1 Dele S1Interface Delete S1Interface used in link mode.

te

2 Dele CPBEARER Delete CPBEARER used in link mode.

te

3 Dele SCTPLNK Delete SCTPLNK used in link mode.

te

4 Dele CnOperatorIpPath Delete CnOperatorIpPath used in link

te mode.

5 Dele eNodeBPath Delete eNodeBPath used in link mode.

te

6 Dele IPPATH Delete IPPATH used in link mode.

te

7 Add EPGROUP For details, see LTE and NR NSA S1 and

X2 Self-Management Feature Parameter
8 Add SCTPTEMPLATE Description.
9 Add SCTPHOST

10 Add SCTPPEER

11 Add USERPLANEHOST

12 Add USERPLANEPEER

13 Add SCTPHOST2EPGRP

14 Add SCTPPEER2EPGRP

15 Add UPHOST2EPGRP

16 Add UPPEER2EPGRP

17 Add S1

18 Add X2

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 689

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

Data preparation can be performed using the MAE-Deployment or MML

commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario-specific template being "Changing the Transmission
Mode From Link Mode to Endpoint Mode"): For details, see the interactive
operation guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

● Changing the transmission mode of the S1 interface from link mode to
endpoint mode
In the following example, the eNodeB connects to both MME 0 (IP address:
192.168.180.10) and MME 1 (IP address: 192.168.64.200), and transmission
modes on both the control plane and user plane are changed.
If OMCH parameters are modified by mistake, the OMCH may be
disconnected and cannot be restored within a long period of time. To avoid
service unavailability due to the OMCH disconnection, you are advised to turn
on the automatic rollback switch of the CB by running the CFM CB command
before configuring data. For example, CFM CB: MODE=UNFORCED,
NAME="CB1", COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="user", PWD="*****", DIR="ftproot/",
FN="LIC_LTE_ON.dat";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="user", PWD="****";
/*(Control plane) Removing the SCTPLNK, CPBEARER, and S1Interface MOs of the S1 interface whose
transmission mode needs to be changed from link mode to endpoint mode*/
RMV S1INTERFACE: S1InterfaceId=***;
RMV CPBEARER: CPBEARID=***, FLAG=MASTER;
RMV SCTPLNK: SCTPNO=***;
/*(User plane) Removing the IPPATH, eNodeBPath, and CnOperatorIpPath MOs of the S1 interface
whose transmission mode needs to be changed from link mode to endpoint mode*/
RMV CNOPERATORIPPATH:IPPATHID=***;
RMV ENODEBPATH:IPPATHID=***;
RMV IPPATH:PATHID=***;
/*Adding endpoint groups. It is recommended that each MME be configured with a unique endpoint

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 690

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

group. For example, the following two endpoint groups are configured for two MMEs, respectively. In
addition, the S1 interface and X2 interface must be configured with different endpoint groups.*/
ADD EPGROUP: EPGROUPID=0;
ADD EPGROUP: EPGROUPID=1;
/*(Control plane) Adding an SCTP parameter template. Multiple SCTP links can share one SCTP
parameter template. For example, if the transmission on the X2 interface adopts the endpoint mode,
the transmission on the S1 interface also uses this SCTP parameter template. Note that the
configuration of parameters in the SCTPLNK MO in link mode must be the same as those in the
SCTPTEMPLATE MO. Otherwise, the SCTP links cannot share an SCTP parameter template, and
another SCTP parameter template must be added.*/
ADD SCTPTEMPLATE:SCTPTEMPLATEID=0,SWITCHBACKFLAG=ENABLE;
/*(Control plane) Adding an SCTP host. Each operator can use only one SCTP host. The SCTP port
number is configured based on the network plan and must be configured for the X2 interface and S1
interface separately. In addition, the value of the SCTPHOSTID parameter must be unique, and the IP
address and the SCTP port number must be the same as those in the SCTPLNK MO in link mode. For
example, the SCTP host with an ID of 0 is used for S1 interface.*/
ADD SCTPHOST: SCTPHOSTID=0, IPVERSION=IPv4, SIGIP1V4="192.168.15.61",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=36412, SCTPTEMPLATEID=0;
/*(Control plane) Adding SCTP peers. The SCTP port number is configured based on the network plan.
An SCTP peer must be configured for each MME with the IP address, port number, and other
configurations being the same as those in the SCTPLNK MO in link mode. The value of the
SCTPPEERID parameter configured for the S1 interface cannot be the same as that for the X2
interface. Otherwise, the SCTPPEER MO configured for the X2 interface will be replaced.*/
ADD
SCTPPEER:SCTPPEERID=100,IPVERSION=IPv4,SIGIP1V4="192.168.180.10",SIGIP1SECSWITCH=DISABLE,S
IGIP2SECSWITCH=DISABLE,PN=36412;
ADD
SCTPPEER:SCTPPEERID=101,IPVERSION=IPv4,SIGIP1V4="192.168.64.200",SIGIP1SECSWITCH=DISABLE,S
IGIP2SECSWITCH=DISABLE,PN=36412;
/*(Control plane) Adding the SCTP host to the endpoint groups corresponding to the connected
MMEs. One operator uses the same SCTP host.*/
ADD SCTPHOST2EPGRP: EPGROUPID=0, SCTPHOSTID=0;
ADD SCTPHOST2EPGRP: EPGROUPID=1, SCTPHOSTID=0;
/*(Control plane) Adding the SCTP peers to the endpoint groups. Each operator can reference only
one SCTP host.*/
ADD SCTPPEER2EPGRP:EPGROUPID=0,SCTPPEERID=100;
ADD SCTPPEER2EPGRP:EPGROUPID=1,SCTPPEERID=101;
/*(User plane) Adding a user-plane host. The user-plane hosts connected to different S-GWs can be
the same or different. If the transmission on the X2 interface is in endpoint mode and the S1 interface
and X2 interface share the local IP address, the USERPLANEHOST MO does not need to be added.*/
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.15.61",
IPSECSWITCH=DISABLE;
/*(User plane) Add the user-plane host to the corresponding endpoint groups. Different endpoint
groups can be configured with the same or different user-plane hosts.*/
ADD UPHOST2EPGRP:EPGROUPID=0,UPHOSTID=0;
ADD UPHOST2EPGRP:EPGROUPID=1,UPHOSTID=0;
/*Adding S1 objects with the S1 objects associated with the operator (operator information needs to
be configured in advance), control-plane endpoint groups, and user-plane endpoint groups. In this
step, set the MME Selection Priority parameter based on the network plan. Multiple S1 interfaces
must be configured for an eNodeB connecting to multiple MMEs. The End Point Group Config Flag
parameter controls whether to configure the endpoint mode for transmission on the user plane,
control plane, or both the user plane and control plane.*/
ADD S1: S1Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=0, UpEpGroupId=0;
ADD S1: S1Id=1, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=1, UpEpGroupId=1;

NOTE

The USERPLANEPEER MOs are automatically generated on the user plane and added to
the EPGROUP MOs. Manual configuration is not required.
● Changing the transmission mode of the S1 interface from link mode to
endpoint mode on the user plane
If the change is performed only on the user plane, skip the operations on the
control plane in the previous steps. Note that the End Point Group Config
Flag parameter in the S1 MO must be set to UP_CFG.
If OMCH parameters are modified by mistake, the OMCH may be
disconnected and cannot be restored within a long period of time. To avoid

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 691

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

service unavailability due to the OMCH disconnection, you are advised to turn
on the automatic rollback switch of the CB by running the CFM CB command
before configuring data. For example, CFM CB: MODE=UNFORCED,
NAME="CB1", COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="user", PWD="*****", DIR="ftproot/",
FN="LIC_LTE_ON.dat";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="user", PWD="****";
/*Adding an endpoint group. The S1 interface and X2 interface must be configured with different
endpoint groups.*/
ADD EPGROUP: EPGROUPID=0;
/*(User plane) Adding a user-plane host. The user-plane hosts connected to different S-GWs can be
the same or different. If the transmission on the X2 interface is in endpoint mode and the S1 interface
and X2 interface share the local IP address, the USERPLANEHOST MO does not need to be added.*/
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="192.168.15.61",
IPSECSWITCH=DISABLE;
/*(User plane) Adding the user-plane host to the corresponding endpoint group*/
ADD UPHOST2EPGRP:EPGROUPID=0,UPHOSTID=0;
/*Adding an S1 object with the S1 object associated with the operator (operator information needs to
be configured in advance), control-plane endpoint group, and user-plane endpoint group. In this step,
set the MME Selection Priority parameter based on the network plan. Multiple S1 interfaces must be
configured for an eNodeB connecting to multiple MMEs. The End Point Group Config Flag parameter
must be set to UP_CFG. It controls whether to configure the endpoint mode for transmission on the
user plane, control plane, or both the user plane and control plane.*/
ADD S1: S1Id=0, CnOperatorId=0, EpGroupCfgFlag= UP_CFG, UpEpGroupId=0;
/*(User plane) Removing the IPPATH, eNodeBPath, and CnOperatorIpPath MOs whose transmission
modes are changed from link mode to endpoint mode*/
RMV CNOPERATORIPPATH:IPPATHID=***;
RMV ENODEBPATH:IPPATHID=***;
RMV IPPATH:PATHID=***;

● Changing the transmission mode of the X2 interface from link mode to

endpoint mode
If the X2 interfaces are automatically created before an upgrade, the
transmission on the X2 interfaces is automatically upgraded to the endpoint
mode after being upgraded to the target version. No reconfiguration is
required. In the following example, the transmission modes on both the X2
control plane and X2 user plane are changed from link mode to endpoint
mode, because the transmission mode change only on the X2 control plane or
user plane is not a common practice on the live network.
If OMCH parameters are modified by mistake, the OMCH may be
disconnected and cannot be restored within a long period of time. To avoid
service unavailability due to the OMCH disconnection, you are advised to turn
on the automatic rollback switch of the CB by running the CFM CB command
before configuring data. For example, CFM CB: MODE=UNFORCED,
NAME="CB1", COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="user", PWD="*****", DIR="ftproot/",
FN="LIC_LTE_ON.dat";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.dat", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="user", PWD="****";
/*(Control plane) Removing the SCTPLNK, CPBEARER, and S1Interface MOs whose transmission
modes are changed from link mode to endpoint mode*/
RMV S1INTERFACE: S1InterfaceId=***;
RMV CPBEARER: CPBEARID=***, FLAG=MASTER;
RMV SCTPLNK: SCTPNO=***;
/*(User plane) Removing the IPPATH, eNodeBPath, and CnOperatorIpPath MOs whose transmission

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 692

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

modes are changed from link mode to endpoint mode*/

RMV CNOPERATORIPPATH:IPPATHID=***;
RMV ENODEBPATH:IPPATHID=***;
RMV IPPATH:PATHID=***;
/*Adding an endpoint group. The S1 interface and X2 interface must be configured with different
endpoint groups. For example, the endpoint group with an ID of 200 is used for the X2 interface.*/
ADD EPGROUP: EPGROUPID=200;
/*(Control plane) Adding an SCTP parameter template. Multiple SCTP links can share one SCTP
parameter template. For example, if the transmission on the S1 interface adopts the endpoint mode,
the transmission on the X2 interface also uses this SCTP parameter template. Note that the
configuration of parameters in the SCTPLNK MO in link mode must be the same as those in the
SCTPTEMPLATE MO. Otherwise, the SCTP links cannot share an SCTP parameter template, and
another SCTP parameter template must be added.*/
ADD SCTPTEMPLATE:SCTPTEMPLATEID=0,SWITCHBACKFLAG=ENABLE;
/*(Control plane) Adding an SCTPHOST MO. All operators can use only one SCTP host for the X2
interface. The SCTP port number is configured based on the network plan and must be configured for
the X2 interface and S1 interface separately. In addition, the combination of the IP address and
SCTPHOSTID must be unique, and the IP address and the SCTP port number must be the same as
those in the SCTPLNK MO in link mode. For example, the SCTP host with an ID of 200 is used for the
X2 interface.*/
ADD SCTPHOST: SCTPHOSTID=200, IPVERSION=IPv4, SIGIP1V4="192.168.15.61",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=36422, SCTPTEMPLATEID=0;
/*(Control plane) Adding an SCTP peer. The SCTP port number is configured based on the network
plan. An SCTP peer must be configured for each MME. The configurations, such as the IP address and
port number, must be the same as those in the SCTPLNK MO in link mode. The value of the
SCTPPEERID parameter configured for the S1 interface cannot be the same as that for the X2
interface.*/
ADD
SCTPPEER:SCTPPEERID=100,IPVERSION=IPv4,SIGIP1V4="192.168.180.10",SIGIP1SECSWITCH=DISABLE,S
IGIP2SECSWITCH=DISABLE,PN=36412;
/*(Control plane) Adding the SCTP host for the X2 interface to the endpoint group*/
ADD SCTPHOST2EPGRP: EPGROUPID=200, SCTPHOSTID=200;
/*(User plane) Adding a user-plane host. The user-plane host can be shared by or added separately
for the S1 interface and X2 interface. If the transmission on the S1 interface adopts the endpoint
mode and the S1 interface and X2 interface share the local IP address, the USERPLANEHOST MO
does not need to be added.*/
ADD USERPLANEHOST: UPHOSTID=200, IPVERSION=IPv4, LOCIPV4="192.168.15.61",
IPSECSWITCH=DISABLE;
/*(User plane) Adding the user-plane host to the corresponding endpoint group. Different endpoint
groups can be configured with the same or different user-plane hosts.*/
ADD UPHOST2EPGRP:EPGROUPID=200,UPHOSTID=0;
/*Adding an X2 object with the X2 object associated with the operator (operator information needs to
be configured in advance), control-plane endpoint group, and user-plane endpoint group. The End
Point Group Config Flag parameter must be set to CP_UP_CFG. It controls whether to configure the
endpoint mode for transmission on the user plane, control plane, or both the user plane and control
plane.*/
ADD X2: X2Id=0, CnOperatorId=0, EpGroupCfgFlag=CP_UP_CFG, CpEpGroupId=200, UpEpGroupId=200;

NOTE

The USERPLANEPEER MOs are automatically generated on the user plane and added to
the EPGROUP MOs. Manual configuration is not required.

1.8.15.3 Engineering Implementation

This section describes the engineering implementation for changing the
transmission mode from link mode to endpoint mode, including prerequisites,
context, and procedure.

Prerequisites
Hardware, software, license files, and data for changing the transmission mode
are ready.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 693

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations

Using the MAE-Deployment:

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
c. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml",
FLG=NO, MODE=IPV4, IP="10.161.18.69", USR="ftpuser",
PWD="***********";
d. Deliver the configuration data to the eNodeB and activate the data. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
e. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

Using MML commands:

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 694

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
d. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.8.15.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the
transmission mode from link mode to endpoint mode.

Procedure
Step 1 Verify that no new alarm has been reported.
If any alarm has been reported, clear the alarm according to instructions in 3900
& 5900 Series Base Station Alarm Reference.
Step 2 (Optional) If the transmission mode has been reconfigured on the control plane,
run the DSP S1 or DSP X2 command to check whether the value of each S1
Interface State or X2 Interface State parameter is Normal.
● If the parameter value is Normal, the reconfiguration is successful.
● If the parameter value is not Normal, check whether the status of the SCTP
link associated with the S1 interface or X2 interface is normal.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 695

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The status of the The SCTP link fails to set up. In this case, check
SCTP link is whether the peer IP address of the SCTP link is set
abnormal to the expected IP address of the MME or eNodeB.
– If the peer IP address of the SCTP link is
incorrect, modify the IP address in the SCTPPEER
MO.
– If the peer IP address of the SCTP link is correct,
contact Huawei technical support or dial the
Huawei technical support hotline.

The status of the The S1 interface fails to be set up. In this case, check
SCTP link is normal whether the CN Operator ID and MME Release
parameters in the S1 MO are set to the same values
as those in the associated S1Interface MO.
– If they are different, modify the parameters to
ensure consistency.
– If they are the same, contact Huawei technical
support or dial the Huawei technical support
hotline.

Step 3 (Optional) If the transmission mode has been reconfigured on the user plane, run
the LST EPGROUP command to check whether the value of the User Plane Peer
List parameter includes the USERPLANEPEER ID. After an IP path is removed and a
UE accesses the network, the USERPLANEPEER MO will be automatically
generated and added to the User Plane Peer List parameter. If no UE accesses the
network, the queried value of User Plane Peer List parameter is NULL.
● If the value of User Plane Host List is not NULL, the user-plane host is ready
and the reconfiguration is successful.
● If the value of User Plane Host List is NULL, run the ADD UPHOST2EPGRP
command to add the USERPLANEHOST MO to the EPGROUP MO.

----End

1.8.15.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Roll back the reconfiguration data.
● Using MML commands:
a. Run the DLD CFGFILE command to download the original configuration
file.
For example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="",
ENCRYPTMODE=UNENCRYPTED;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 696

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

b. Run the ACT CFGFILE command to activate the original configuration

file.
For example: ACT CFGFILE: EFT=IMMEDIATELY;

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Verify that engineering rollback is successful according to instructions in

Engineering Verification.

----End

1.8.16 Adding an eCoordinator Connection (Only for IPv4

Transmission)
This section describes how to add a connection (Se interface) between the
eNodeB and eCoordinator.

Prerequisites
● Required data has been configured on the eCoordinator.
● Data has been configured for the transport network between the eNodeB and
the eCoordinator.

Context
This section describes the operations required for adding a connection to the
eCoordinator on the eNodeB side. The operations related to the hardware,
software, license file, and security certificates about the eCoordinator are
described in the associated eCoordinator manual.

1.8.16.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adding an Se interface for the
eNodeB.

Application Scenario
An Se interface needs to be configured in the eNodeB to connect to the
eCoordinator for related feature activation.

Reconfiguration Impact
No impact

Reconfiguration Scheme
Figure 1-126 shows the reconfiguration procedure for adding an Se interface.
Determine the reconfiguration scheme according to the following table.

Old Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 697

eRAN
Reconfiguration Guide
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
Table 1-235 Scheme options
If...
The new Se interface does not share
the SCTP host with other existing
interfaces such as S1 and X2
The SCTP host of the new Se interface
requires a new device IP address
No route is available between the
eNodeB and the eCoordinator SCTP
address
The user plane of the Se interface
needs to be configured
The new Se interface does not share
the user-plane host with other existing
interfaces such as S1 and X2
The user plane of the new Se interface
requires a new device IP address
No route is available between the
eNodeB and the eCoordinator user
plane
New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.
Table 1-236 Scheme options
If...
The new Se interface does not share
the SCTP host with other existing
interfaces such as S1 and X2
The SCTP host of the new Se interface
requires a new device IPv4 address
No route is available between the
eNodeB and the eCoordinator SCTP
address
Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd.
1 eRAN Reconfiguration Guide
Then...
Add an SCTP host for the Se interface.
Add a device IP address.
Add an SCTP route from the eNodeB
to the eCoordinator SCTP address and
the corresponding VLANMAP MO.
Add user-plane host and peer
configurations of the Se interface.
Add a user-plane host for the Se
interface.
Add a device IP address.
Add a route from the eNodeB to the
eCoordinator user-plane address and
the corresponding VLANMAP MO.
Then...
Add an SCTP host for the Se interface.
Add an IPv4 address.
Add a route from the eNodeB to the
eCoordinator SCTP address and the
corresponding VLANMAP MO or
INTERFACE MO in which the interface
type is VLAN.
698
eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

The user plane of the Se interface Add user-plane host and peer
needs to be configured configurations of the Se interface.

The new Se interface does not share Add a user-plane host for the Se
the user-plane host with other existing interface.
interfaces such as S1 and X2

The user plane of the new Se interface Add an IPv4 address.

requires a new device IPv4 address

No route is available between the
eNodeB and the eCoordinator user
plane
Add a route from the eNodeB to the
eCoordinator user-plane address and
the corresponding VLANMAP MO or
INTERFACE MO in which the interface
type is VLAN.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 699

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-126 Procedure for adding an eCoordinator

New Model

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 700

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Figure 1-127 Procedure for adding an eCoordinator

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 701

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Figure 1-128 shows the topologies before and after the reconfiguration.

Figure 1-128 Topologies before and after the reconfiguration

1.8.16.2 Engineering Preparation

This section describes the engineering preparation for adding an eCoordinator
connection, including information collection and preparation of hardware,
software, license files, security certificates, and data. It also describes the data
preparation mode and provides MML configuration script examples.

Information Collection
Table 1-237 describes the information to be collected for data preparation.

Table 1-237 Information to be collected

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the
eCoordinator

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the
eCoordinator

IP address and port Includes the IP address and port number of the SCTP
number of the SCTP peer over the Se interface of the eNodeB.
host of the
eCoordinator

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 702

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

User-plane IP address Includes the peer IP address (old model)/IPv4 address

(old model)/IPv4 (new model) of the Se interface user plane on the
address (new model) eNodeB.
of the eCoordinator

Device IP address of Includes the device IP address used for communication

the eNodeB with external devices.

SCTP port number of Includes the port number of the SCTP host of the Se
the Se interface on interface on the eNodeB.
the eNodeB

Information about Includes the ID of the endpoint group to which the user-
the endpoint group plane host, user-plane peer, SCTP host, and SCTP peer
need to be added.

Hardware Preparation
Prepared the hardware listed in Table 1-238.

Table 1-238 Hardware to be prepared

Hardware Description

Cables used to Cables connecting the eNodeB to the closest router

connect the eNodeB between the eNodeB and the eCoordinator. The cables
and a router can be Ethernet cables or optical fibers, depending on
the peer router.

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 703

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-239 Data preparation for adding an eCoordinator connection

SN Ope MO Configuration Reference
ratio
n

1 Add DEVIP (old model)/ For details, see IP eRAN Engineering

IPADDR4 (new model) Guide Feature Parameter Description.
2 Add SCTPHOST For details about parameter settings, see
"Configuring Transport Data" > "IP
3 Add USERPLANEHOST over FE/GE (Non-Secure Networking)"
4 Add EPGROUP in 3900 & 5900 Series Base Station
Initial Configuration Guide.
5 Modi EPGROUP
fy

6 Add IPRT/SRCIPRTa (old For details, see IP eRAN Engineering

model)/IPROUTE4/ Guide Feature Parameter Description.
SRCIPROUTE4b (new
model)

7 Add VLANMAP or
INTERFACE in which
the interface type is
VLAN

8 Add SCTPPEER For details about parameter settings, see

"Configuring Transport Data" > "IP
9 Add USERPLANEPEER over FE/GE (Non-Secure Networking)"
10 Modi EPGROUP in 3900 & 5900 Series Base Station
fy Initial Configuration Guide.

11 Add ECO

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.
b: To simplify configurations when one IPv4 address maps multiple destination
IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 704

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Adding an eCoordinator connection"): For
details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, an IP route is added.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address for communicating with the eCoordinator*/
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="135.25.221.110", MASK="255.255.255.0";
/*Adding an SCTP host*/
ADD SCTPHOST: SCTPHOSTID=21, IPVERSION=IPv4, SIGIP1V4="192.168.223.110",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=36422, SCTPTEMPLATEID=0;
/*Adding a user-plane host*/
ADD USERPLANEHOST: UPHOSTID=21, IPVERSION=IPv4, LOCIPV4="192.168.223.110",
IPSECSWITCH=DISABLE;
/*Adding an endpoint group with the ID of 21*/
ADD EPGROUP: EPGROUPID=21;
/*Adding the new SCTP host to the endpoint group*/
ADD SCTPHOST2EPGRP: EPGROUPID=21, SCTPHOSTID=21;
/*Adding an IP route from the eNodeB to the eCoordinator*/
ADD IPRT: RTIDX=10, SN=7, SBT=BASE_BOARD, DSTIP="192.168.3.3", DSTMASK="255.255.255.255",

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 705

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

RTTYPE=NEXTHOP, NEXTHOP="192.168.223.1", MTUSWITCH=OFF;

/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.221.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SE
TPRIO=DISABLE;
/*Adding an SCTP peer*/
ADD SCTPPEER: SCTPPEERID=21,IPVERSION=IPv4, SIGIP1V4="192.168.3.3", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=58090;
/*Adding a user-plane peer*/
ADD USERPLANEPEER: UPPEERID=21, IPVERSION=IPv4, PEERIPV4="192.168.3.3", IPSECSWITCH=DISABLE,
USERLABEL="eCO:192.168.3.3";
/*Adding the new SCTP peer to the endpoint group*/
ADD SCTPPEER2EPGRP: EPGROUPID=21, SCTPPEERID=21;
/*Adding the new user-plane peer to the endpoint group*/
ADD UPPEER2EPGRP: EPGROUPID=21, UPPEERID=21;
/*Adding configurations about the eCoordinator*/
ADD ECO: ECOID=0, EPGROUPCFGFLAG=CP_UP_CFG, CPEPGROUPID=21, UPEPGROUPID=21;

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Setting an Ethernet port*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=0;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=0, VRFIDX=0;
ADD VLANMAP:
NEXTHOPIP="192.168.221.1",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SETPRIO=DIS
ABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=0, VLANID=101, VRFIDX=0;
/*Adding an IPv4 address for communicating with the eCoordinator*/
ADD IPADDR4: ITFID=0, IP="135.25.221.110", MASK="255.255.255.0";
/*Adding an IPv4 route from the eNodeB to the eCoordinator*/
ADD IPROUTE4: RTIDX=10, DSTIP="192.168.3.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.223.1", MTUSWITCH=OFF;
/*Adding an SCTP host*/
ADD SCTPHOST: SCTPHOSTID=21, IPVERSION=IPv4, SIGIP1V4="192.168.223.110",
SIGIP1SECSWITCH=DISABLE, SIGIP2SECSWITCH=DISABLE, PN=36422, SCTPTEMPLATEID=0;
/*Adding a user-plane host*/
ADD USERPLANEHOST: UPHOSTID=21, IPVERSION=IPv4, LOCIPV4="192.168.223.110",
IPSECSWITCH=DISABLE;
/*Adding an endpoint group with the ID of 21*/
ADD EPGROUP: EPGROUPID=21;
/*Adding the new SCTP host to the endpoint group*/
ADD SCTPHOST2EPGRP: EPGROUPID=21, SCTPHOSTID=21;
/*Adding an SCTP peer*/
ADD SCTPPEER: SCTPPEERID=21,IPVERSION=IPv4, SIGIP1V4="192.168.3.3", SIGIP1SECSWITCH=DISABLE,
SIGIP2SECSWITCH=DISABLE, PN=58090;
/*Adding a user-plane peer*/
ADD USERPLANEPEER: UPPEERID=21, IPVERSION=IPv4, PEERIPV4="192.168.3.3", IPSECSWITCH=DISABLE,
USERLABEL="eCO:192.168.3.3";
/*Adding the new SCTP peer to the endpoint group*/
ADD SCTPPEER2EPGRP: EPGROUPID=21, SCTPPEERID=21;
/*Adding the new user-plane peer to the endpoint group*/
ADD UPPEER2EPGRP: EPGROUPID=21, UPPEERID=21;
/*Adding configurations about the eCoordinator*/
ADD ECO: ECOID=0, EPGROUPCFGFLAG=CP_UP_CFG, CPEPGROUPID=21, UPEPGROUPID=21;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 706

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.8.16.3 Engineering Implementation

This section describes the engineering implementation for adding an eCoordinator
connection, including prerequisites, context, and procedure.

Prerequisites
Information and data required for adding an eCoordinator connection are ready,
and the required license file is available in the save path on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
Connect the eNodeB and the route that is nearest to the eNodeB between the
eNodeB and eCoordinator.
● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 707

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see Setting the Maintenance Mode of the eNodeB to

NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.8.16.4 Engineering Verification

This section describes how to verify the reconfiguration for adding an
eCoordinator connection.

Procedure
Step 1 Run the LST SCTPPEER command to verify that the value of First Peer IP Address
in one entry is the same as the IP address of the SCTP host on the eCoordinator.

If they are different, check whether the transmission configuration is correct.

● If it is incorrect, modify it.

● If it is correct, contact Huawei technical support or dial the Huawei technical
support hotline.

Step 2 Run the LST USERPLANEPEER command to verify that the value of Peer IP
Address in one record is the same as the user-plane IP address of the
eCoordinator.

If they are different, check whether the transmission configuration is correct.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 708

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● If it is incorrect, modify it.

● If it is correct, contact Huawei technical support or dial the Huawei technical
support hotline.

Step 3 Run the DSP ECO command to check whether the value of ECO Interface CP
Bearer State is Normal.

If the value ECO Interface CP Bearer State is Abnormal, check whether

ALM-25888 SCTP Link Fault is reported. If the alarm is reported, clear the alarm
according to 3900 & 5900 Series Base Station Alarm Reference.

Step 4 Verify that ALM-25952 User Plane Path Fault is not reported.

If ALM-25952 User Plane Path Fault is reported, clear the alarm according to the
instructions in 3900 & 5900 Series Base Station Alarm Reference.

----End

1.8.16.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 709

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful according to instructions in 1.8.16.4

Engineering Verification.

----End

1.8.17 Replacing an eCoordinator (Only for IPv4 Transmission)

This section describes how to replace an eCoordinator.

Prerequisites
● Required data has been configured on the new eCoordinator.
● Data has been configured for the transport network between the eNodeB and
the new eCoordinator.

1.8.17.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for replacing the eCoordinator that
the eNodeB is connected to.

Application Scenario
Network deployment has changed, and the eCoordinator that an eNodeB is
connected to needs to be replaced.

Reconfiguration Impact
During eCoordinator replacement, the eNodeB disconnects from the old
eCoordinator before setting up a connection to the new eCoordinator, and
therefore services carried on the old Se interface are interrupted.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 710

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Scheme
Figure 1-129 shows the reconfiguration procedure for replacing the eCoordinator
that the eNodeB is connected to. Determine the reconfiguration scheme according
to the following table.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Table 1-240 Scheme options

If... Then...

The eNodeB requires a new IP address Add a device IP address on the

to communicate with the new eNodeB.
eCoordinator

No route is available between the Add a route from the eNodeB to the
eNodeB and the new eCoordinator new eCoordinator and the
corresponding VLANMAP MO.

Information about the SCTP host of Modify information about the SCTP
the Se interface needs to be modified host.
because the eNodeB uses a new IP
address to communicate with the new
eCoordinator

Information about the user-plane host Modify information about the user-
of the Se interface needs to be plane host.
modified because the eNodeB uses a
new IP address to communicate with
the new eCoordinator

The route between the eNodeB and Remove the IP route.

the old eCoordinator is no longer used

The local IP address used by the Remove the device IP address.

eNodeB to communicate with the old
eCoordinator is no longer used

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Table 1-241 Scheme options

If... Then...

The eNodeB requires a new IP address Add an IPv4 address on the eNodeB.
to communicate with the new
eCoordinator

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 711

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

No route is available between the
eNodeB and the new eCoordinator
Add a route from the eNodeB to the
new eCoordinator and the
corresponding VLANMAP MO or
INTERFACE MO in which the interface
type is VLAN.

Information about the SCTP host of Modify information about the SCTP
the Se interface needs to be modified host.
because the eNodeB uses a new IP
address to communicate with the new
eCoordinator

Information about the user-plane host Modify information about the user-
of the Se interface needs to be plane host.
modified because the eNodeB uses a
new IP address to communicate with
the new eCoordinator

The route between the eNodeB and Remove the IPv4 route.
the old eCoordinator is no longer used

The local IP address used by the Remove the IPv4 address.

eNodeB to communicate with the old
eCoordinator is no longer used

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 712

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-129 Procedure for replacing an eCoordinator

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 713

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-130 Procedure for replacing an eCoordinator

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 714

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
N/A

1.8.17.2 Engineering Preparation

This section describes the engineering preparation for replacing an eCoordinator,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-242 describes the information to be collected for data preparation.

Table 1-242 Information to be collected

Information Description

Information about Includes the next-hop IP address, destination IP address,

the route from the subnet mask, and route priority.
eNodeB to the new
eCoordinator

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the new
eCoordinator

IP address and port Includes the IP address and port number of the SCTP
number of the SCTP peer over the Se interface of the eNodeB.
host of the new
eCoordinator

User-plane IP address Includes the IP address of the user-plane peer over the
of the new Se interface of the eNodeB.
eCoordinator

Device IP address Include the device IP address (old model)/IPv4 address

(old model)/IPv4 (new model) used for communicating with external
address (new model) devices.
of the eNodeB

Information about Includes the ID of the endpoint group to which the user-
the endpoint group plane host, user-plane peer, SCTP host, and SCTP peer
of the Se interface need to be added.

Hardware Preparation
Prepared the hardware listed in Table 1-243.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 715

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-243 Hardware to be prepared

Hardware Description

Cables used to Cables connecting the eNodeB to the closest router

connect the eNodeB between the eNodeB and the new eCoordinator. The
and a router cables can be Ethernet cables or optical fibers,
depending on the peer router.

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-244 Data preparation for adding an eCoordinator connection

SN Ope MO Configuration Reference

ratio
n

1 Add DEVIP For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPRT/SRCIPRTa For details, see IP eRAN Engineering
Guide Feature Parameter Description.
3 Add VLANMAP

4 Modi SCTPHOST Change the IP address of the SCTP host

fy to the new device IP address.

5 Modi SCTPPEER Change the peer IP address to the IP

fy address of the SCTP host of the new
eCoordinator.

6 Modi USERPLANEHOST Change the IP address of the user-plane

fy host to the new device IP address.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 716

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

7 Modi USERPLANEPEER Change the peer IP address to the user-

fy plane IP address of the new
eCoordinator.

8 Dele IPRT/SRCIPRTa Remove the IP route used for

te communicating with the original
eCoordinator.

9 Dele DEVIP Remove the device IP address used for

te communicating with the original
eCoordinator.

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Table 1-245 Data preparation for adding an eCoordinator connection

SN Oper MO Configuration Reference
ation

1 Add IPADDR4 For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPROUTE4/ For details, see IP eRAN Engineering
SRCIPROUTE4a Guide Feature Parameter Description.

3 Add VLANMAP or INTERFACE

in which the interface
type is VLAN

4 Modi SCTPHOST Change the IP address of the SCTP

fy host to the new IPv4 address.

5 Modi SCTPPEER Change the peer IP address to the IP

fy address of the SCTP host of the new
eCoordinator.

6 Modi USERPLANEHOST Change the IP address of the user-

fy plane host to the new IPv4 address.

7 Modi USERPLANEPEER Change the peer IP address to the

fy user-plane IP address of the new
eCoordinator.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 717

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Oper MO Configuration Reference

ation

8 Delet IPROUTE4/ Remove the IPv4 route used for

e SRCIPROUTE4a communicating with the original
eCoordinator.

9 Delet IPADDR4 Remove the IPv4 address used for

e communicating with the original
eCoordinator.

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Adding an eCoordinator connection"): For
details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, an IP route is added.

If OMCH parameters are modified by mistake, the OMCH may be disconnected

and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 718

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address used for communicating with the new eCoordinator*/
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="135.25.221.110", MASK="255.255.255.0";
/*Adding an IP route from the eNodeB to the new eCoordinator*/
ADD IPRT: RTIDX=21, SN=7, SBT=BASE_BOARD, DSTIP="192.168.5.3", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.225.1", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD VLANMAP: NEXTHOPIP="192.168.225.1", MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
VLANID=101, SETPRIO=DISABLE;
/*Modifying the SCTP host*/
MOD SCTPHOST: SCTPHOSTID=21, SIGIP1V4="192.168.225.110";
/*Modifying the information of the SCTP peer*/
MOD SCTPPEER:SCTPPEERID=21, SIGIP1V4="192.168.5.3";
/*Modifying the user-plane host*/
MOD USERPLANEHOST:UPHOSTID=21, LOCIPV4="192.168.225.110";
/*Modifying the information about the user-plane peer*/
MOD USERPLANEPEER: UPPEERID=21, PEERIPV4="192.168.5.3", USERLABEL="eCO:192.168.5.3";
/*Removing the route from the eNodeB to the original eCoordinator*/
RMV IPRT: RTIDX=10;
/*Removing the device IP address used for communicating with the original eCoordinator*/
RMV DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.223.110";

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Setting an Ethernet port*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=0;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=0, VRFIDX=0;
ADD VLANMAP: NEXTHOPIP="192.168.225.1", MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
VLANID=101, SETPRIO=DISABLE;
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=0, VLANID=101, VRFIDX=0;
/*Adding an IPv4 address for communicating with the new eCoordinator*/
ADD IPADDR4: ITFID=0, IP="135.25.221.110", MASK="255.255.255.0";
/*Adding an IPv4 route from the eNodeB to the new eCoordinator*/
ADD IPROUTE4: RTIDX=21, DSTIP="192.168.5.3", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.225.1", MTUSWITCH=OFF;
/*Modifying the SCTP host*/
MOD SCTPHOST: SCTPHOSTID=21, SIGIP1V4="192.168.225.110";
/*Modifying the information about the SCTP peer*/
MOD SCTPPEER:SCTPPEERID=21, SIGIP1V4="192.168.5.3";
/*Modifying the user-plane host*/
MOD USERPLANEHOST:UPHOSTID=21, LOCIPV4="192.168.225.110";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 719

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Modifying the information about the user-plane peer*/

MOD USERPLANEPEER: UPPEERID=21, PEERIPV4="192.168.5.3", USERLABEL="eCO:192.168.5.3";
/*Removing the route from the eNodeB to the original eCoordinator*/
RMV IPROUTE4: RTIDX=10;
/*Removing the IPv4 address used for communicating with the original eCoordinator*/
RMV IPADDR4: ITFID=1, IP="192.168.223.110";

1.8.17.3 Engineering Implementation

This section describes the engineering implementation for replacing an
eCoordinator, including prerequisites, context, and procedure.

Prerequisites
Information and data required for replacing an eCoordinator are ready, and the
required license file is available in the save path on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
Connect the eNodeB and the route that is nearest to the eNodeB between the
eNodeB and the new eCoordinator.
● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 720

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iv. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.8.17.4 Engineering Verification

This section describes how to verify the reconfiguration for replacing an
eCoordinator.

Procedure
Step 1 Run the LST SCTPPEER command to verify that the value of First Peer IP Address
in one entry is the same as the IP address of the SCTP host on the new
eCoordinator.
If they are different, check whether the transmission configuration is correct.
● If it is incorrect, modify it.
● If it is correct, contact Huawei technical support or dial the Huawei technical
support hotline.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 721

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 2 Run the LST USERPLANEPEER command to verify that the value of Peer IP
Address in one record is the same as the user-plane IP address of the new
eCoordinator.
If they are different, check whether the transmission configuration is correct.
● If it is incorrect, modify it.
● If it is correct, contact Huawei technical support or dial the Huawei technical
support hotline.
Step 3 Run the DSP ECO command to check whether the value of ECO Interface CP
Bearer State is Normal.
If the value ECO Interface CP Bearer State is Abnormal, check whether
ALM-25888 SCTP Link Fault is reported. If the alarm is reported, clear the alarm
according to 3900 & 5900 Series Base Station Alarm Reference.
Step 4 Verify that ALM-25952 User Plane Path Fault is not reported.
If ALM-25952 User Plane Path Fault is reported, clear the alarm according to the
instructions in 3900 & 5900 Series Base Station Alarm Reference.

----End

1.8.17.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 722

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the physical connections.
Step 4 Verify that engineering rollback is successful according to instructions in 1.8.17.4
Engineering Verification.

----End

1.8.18 Optimizing the Transmission Configuration Model

This section describes how to optimize the transmission configuration model.

1.8.18.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for optimizing the transmission
configuration model.

Application Scenario
The traditional transmission network configuration is complicated and struggles to
meet the requirement for fast deployment on the live network. Therefore, the
transmission configuration model needs to be optimized to simplify operations.

Reconfiguration Impact
During the optimization of the transmission configuration model, the
corresponding transmission links will be interrupted, and the services carried on
these transmission links will be interrupted for 3 to 10 minutes.

Reconfiguration Scheme

The transmission configuration model can be optimized in the following ways:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 723

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1. Change the transmission configuration model from an old model to a new

model. Cancel the need for configuring the cabinet, subrack, and slot numbers
during the transmission configuration.
2. Optimize the VLAN for a base station using the new transmission
configuration model to make it support IPv6.
3. Change the transmission configuration model from an old model to a new
model and optimize the VLAN.
The transmission configuration model can be changed for multiple base stations
simultaneously. It is recommended the model be changed for a maximum of 500
base stations in a batch.

NOTE

The base station transmission model cannot be changed from the new model to the old
model.

Restrictions:
1. Changing the transmission configuration model from an old model to a new
model does not apply to a GSM base station that uses the GTMU as a main
control board.
2. Restrictions on the VLAN optimization scheme are as follows:
– The following boards do not support this scheme: GTMUb, CMPT, UTRP2,
UTRP3, UTRP4, UTRP9, UTRPa, UCIU, ULPU, CMSU, CBPU, UCCU, and
UBBP.
– This scheme is not supported if L2 packet filtering is configured but the
VLAN ID corresponding to L2 packet filtering does not contain the VLAN
IDs of the VLANMAP, VLANCLASS, and SUBNETVLAN MOs. The specific
configuration scenarios are as follows:

▪ The value of the ACTION parameter of the L2 ACLRULE MO

referenced by packet filtering is DENY, and the VLAN corresponding
to the L2 ACLRULE MO has the VLANMAP and VLANCLASS MOs.

▪ The value of the ACTION parameter of the L2 ACLRULE MO

referenced by packet filtering is DENY, the VLAN corresponding to
the L2 ACLRULE MO does not have the VLANMAP or VLANCLASS
MO, and the value of the MB parameter of packet filtering is DENY.

▪ The value of the ACTION parameter of the L2 ACLRULE MO

referenced by packet filtering is PERMIT, the VLAN corresponding to
the L2 ACLRULE MO does not have the VLANMAP or VLANCLASS
MO, and the value of the MB parameter of packet filtering is DENY.

▪ Only packet filtering is configured but an ACLRULE MO is not, and

the value of the MB parameter of packet filtering is DENY.
3. VLAN optimization is not supported in the following scenario: The
NEXTHOPIP parameter values in the VLANMAP MO are included in the
subnet (that is, the NEXTHOPIP parameter values of N VLANMAP MOs are
in the same network segment as the DEVIP MO, N is greater than or equal to
2, there are inclusion relationships between NEXTHOPIP and MASK
parameter values) but the VLANID parameter values are different. Figure 1
and Figure 2 show the details.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 724

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-131 Local-end network segment containing the next-hop network

segment

Figure 1-132 Next-hop network segment containing the local-end network

segment

4. VLAN optimization is not supported in the following scenario: The VLANID

parameters of the VLANCLASS MOs are set to different values. In this case,
different VLAN IDs are set for different types of services (based on application
layer packets). Figure 3 shows the details.

Figure 1-133 Scenario not supporting VLAN optimization

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 725

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

5. VLAN optimization is not supported in the eMBMS scenario where a VLAN is

configured for IGMP packets.
6. VLAN optimization is not supported if there is no device IP address in the
same network segment as the NEXTHOPIP parameter value of the
VLANMAP MO. (The configuration is incorrect if there is no such device IP
address.)
7. VLAN optimization is not supported if different VLANMAP MOs are
configured with the same VLAN ID but different VRF indexes.
8. VLAN optimization is not supported if IPsec tunnel pairs are used.
9. When the local IP address of the IKEPEER is 0.0.0.0, VLAN optimization is
under the following restrictions:
– When the local IP address of the IKEPEER MO is 0.0.0.0, only one
transmission port can be provided and the port is an ETH port on the
board where the IKE is located.
– VLAN optimization is not supported if the REDIRECTSW parameter of the
IKEPEER MO is set to ON and the local IP address of the IKEPEER MO is
0.0.0.0.
10. VLAN optimization is not supported if the peer IP address of the IKEPEER MO
has multiple routes (active and standby routes and balanced routes) before
the reconstruction and VLAN IDs of the VLANMAP MOs corresponding to the
next hops of the routes are different from each other.
11. VLAN optimization is not supported if a VLANMAP MO is configured for the
lower-level base station in base station cascading scenarios. Otherwise,
services on the lower-level base station may be interrupted, or the related OM
link may be disconnected. (In normal scenarios, you do not need to configure
the VLANMAP MOs for the lower-level base stations. VLAN configurations are
needed only on the higher-level base station.) You can use the LLDP function
on the FMA to check whether base stations are cascaded.
12. VLAN optimization is not supported if a VLANMAP MO is configured for the
panel not providing the transmission port in panel interconnection scenarios.
Otherwise, services of the RAT not providing the transmission port may be
interrupted, and the related OM link may be disconnected. (In normal
scenarios, you do not need to configure the VLANMAP MOs for the RATs not
providing the transmission port. VLAN configurations are needed only for the
RAT providing the transmission port.) You can use the LLDP function on the
FMA to check whether panels are interconnected.

Topology Change
N/A

1.8.18.2 Engineering Preparation

This section describes the engineering preparation for changing the transmission
configuration model from an old model to a new model, including information
collection and preparation of hardware, software, license files, security certificates,
and data. It also describes the data preparation mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 726

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Collection
Information to be collected describes the information to be collected for data
preparation.

Table 1-246 Information to be collected

Information Description

Base station information Name of the base station whose

transmission configuration model
needs to be changed

Whether VLAN optimization is VLAN optimization requires that the

supported by the VLAN of the peer
device connected to the base station if
VLAN optimization is required for the
base station
same VLAN ID be configured for the
interconnected device (switch or
router) to send and receive data.
Before implementing VLAN
optimization for the base station
whose transmission configuration
model needs to be changed, run the
STR VLANDETECTION command to
check the configuration of the
interconnected device.
● If the value of VLAN
Reconstruction Switch is Yes in the
command output, VLAN
optimization can be implemented
for the base station whose
transmission configuration model
needs to be changed.
● If the value of VLAN
Reconstruction Switch is No in the
command output, you need to
modify the configurations of the
base station or the peer device.
Otherwise, the base station may be
disconnected and services may be
interrupted.

Hardware Preparation
N/A

Software Preparation
eRAN15.1 or a later version, and the corresponding MAE-Access and MAE-
Deployment software versions

License File Preparation

N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 727

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Security Certificate Preparation

N/A

Data Preparation
● Back up NE data manually on the OSS for the base station whose
transmission configuration model needs to be changed. For details, see
Operation and Maintenance > MAE-Access Operation and Maintenance >
Security Management > Data Management > Backing Up and Restoring
NE Data > Manually Backing Up NE Data in the MAE product
documentation.
● Obtain the configuration data of the base station whose transmission
configuration model needs to be changed.
On the MAE-Access, right-click the NE whose transmission configuration
model needs to be changed, and choose Synchronize NE Configuration Data
from the shortcut menu to synchronize data of the NE.
● Enter the input options for changing the transmission configuration model:
– Name of the base station whose transmission configuration model needs
to be changed
– Scheme of optimizing the transmission configuration model. The
optimization schemes include:
i. Change the transmission configuration model from an old one to a
new one.
ii. Optimize the VLAN for a base station using the new transmission
configuration model.
iii. Change the transmission configuration model from an old model to
a new model and optimize the VLAN.

Data Preparation Mode

Use the Reconstruction Express function of the MAE-Deployment to change the
transmission configuration model.

1.8.18.3 Engineering Implementation

This section describes the engineering implementation for changing the
transmission configuration model from an old model to a new model, including
prerequisites, context, and procedure. Only remote operations are supported.

Prerequisites
Information and data required for changing the transmission configuration model
are available.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 728

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Remote Operations describe the operations that must be performed on the

operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
Remote Operations (Using the MAE-Deployment)

Step 1 On the menu bar, choose Advanced > Network Enhancement > Reconstruction
Express.

Step 2 Click Export Default Template to obtain the template.

Step 3 In the exported template, enter the name of the NE whose transmission
configuration model needs to be optimized and the sequence number of the
optimization scheme.

Step 4 In Planning Data Table, click to upload the filled template and click Execute.

After that, the import result is displayed in the task information pane in the upper

right area of the home page. (You can also click in the upper right area of the
home page to open the task information pane.)

If the import succeeds, you can expand the task and download the script.

If the import fails, you can expand the task and download the error report. You
can modify the data according to the error information and import the template
again.

Step 5 On the menu bar, choose Advanced > System > Script Executor to import the
script downloaded in the previous step and load the project.

Step 6 Select the loaded project and activate it.

----End

1.8.18.4 Engineering Verification

This section describes how to verify the change of the transmission configuration
model.

Procedure
Run the LST GTRANSPARA command to check the value of the Transmission
Configuration Mode parameter. If the parameter value is New, the transmission
configuration model is successfully changed.

1.8.18.5 Engineering Rollback

For details about configuration data rollback, see Operation and Maintenance >
MAE-Access Operation and Maintenance > Security Management > Data
Management > Backing Up and Restoring NE Data > Restoring NE Data in the
MAE product documentation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 729

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.9 Security Networking Data Reconfigurations

This section describes how to reconfigure eNodeB security networking data in
typical scenarios.

1.9.1 Changing the Transport Network from Non-Security

Mode to PKI Security Mode (Old Model)
This section describes how to change the transport network from non-security
mode to public key infrastructure (PKI) security mode (old model).

Prerequisites
● The PKI-supported security gateway (SeGW) has been deployed, the secure
networking (IPsec, which is short for Internet Protocol Security) and PKI
parameters and the route from the SeGW to the eNodeB have been
configured, and the eNodeB service and OMCH are normal.
● The Certificate Authority (CA) server has been deployed, and configurations
are complete, such as those on the security certificate of the CA server and
the route from the CA server to the eNodeB.

1.9.1.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the transport network
from non-security mode to PKI security mode.

Application Scenario
The operator requires the transport network to operate in PKI security mode
instead of non-security mode.

Reconfiguration Impact
When the transport network is changed from non-security mode to PKI security
mode, transmission links that enter the security network (protected transmission
links) and services carried on these links will be interrupted.

Reconfiguration Scheme
Figure 1-134 and Figure 1-135 show the reconfiguration procedures for changing
the transport network from non-security mode to PKI security mode. Determine
the reconfiguration scheme for changing the transport network from non-security
mode to PKI security mode according to the following table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 730

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-247 Scheme options

If... Then...

A new device IP Add a device IP address. It is recommended that a

address is required for device IP address not used by any service be added.
IKE negotiation

A new device IP Add a device IP address.

address is required for It is required that the eNodeB use this IP address to
applying for an communicate with the CA server through the non-
operator-issued security domain during the reconfiguration.
security certificate
MAE-Deployment is
used for
reconfiguration
Unified encryption is
used
The CA server is
located in the non-
security domain

A new device IP Add a device IP address.

address is required for When the CA server is in the security domain, it is
updating operator- required that the eNodeB use this IP address to
issued security communicate with the CA server through the security
certificates domain. When the CA server is in the non-security
Unified encryption or domain, it is required that the eNodeB use this IP
separate encryption is address to communicate with the CA server through
used the non-security domain.
The CA server is
located in the security
or non-security
domain

No route is available Add a route from the eNodeB to the SeGW and the
between the eNodeB corresponding VLANMAP MO.
and SeGW

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 731

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

● The two encryption modes are as follows:

● In separate encryption, data on the OM channel is encrypted in SSL mode but does not
enter the secure networking (IPsec) tunnel.
● In unified encryption, data on the OM channel is encrypted in SSL mode and enters the
secure networking (IPsec) tunnel.
● Device IP addresses are not required for applying for the operator-issued device certificate in
the following situations:
● If the eNodeB can communicate with the CA server only through the security domain,
the reconfiguration cannot be performed using the MAE-Deployment.
● When reconfiguration is performed using MML commands, the operator-issued security
certificates can be applied for only in offline mode.
● When the separate encryption mode is used and the CA server is in the non-security
domain, the local IP address of the OM channel is recommended for applying for the
operator's certificates.
● The local IP address of the OM channel is recommended for updating the operator-issued
security certificates when the CA server is in the security domain and the unified encryption
mode is used or when the CA server is in the non-security domain and the separate
encryption mode is used. In this case, you do not need to add a device IP address for
updating the certificates.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 732

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-134 Procedure for changing the transport network from non-security
mode to PKI security mode (using the MAE-Deployment, IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 733

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-135 Procedure for changing the transport network from non-security
mode to PKI security mode (using MML commands, IPv4)

Topology Change
Figure 1-136 shows the topologies before and after the reconfiguration.
NOTE

If the operator-issued security certificate needs to be requested or updated, the eNodeB will
access the CA server to apply for or update the certificate.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 734

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-136 Topologies before and after the reconfiguration

1.9.1.2 Engineering Preparation

This section describes the engineering preparation for changing the transport
network from non-security mode to PKI security mode, including information
collection and preparation of hardware, software, license files, security certificates,
and data. It also describes the data preparation mode and provides MML
configuration script examples.

Information Collection
Table 1-248 describes the information to be collected for data preparation.

Table 1-248 Information to be collected

Information Description

IKE proposal Includes the name, encryption algorithm, and integrity

algorithm of the IKE proposal, and the life cycle of the
IKE security association (SA).

Local IKE basic Includes the local IKE name, IKE version, and
information negotiation mode.

Access control rule Used for data flows that require secure networking
(IPsec) protection.

Secure networking Includes the name, encapsulation mode, encryption

(IPsec) proposal algorithm, and authentication algorithm of the secure
networking (IPsec) proposal.

Secure networking Includes the IKE proposal name, IPsec proposal name,
(IPsec) policy access control list (ACL) ID, and IPsec SA life cycle.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 735

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

IP address of the Used to establish secure networking (IPsec) tunnels.

SeGW

Information about Includes all the next-hop IP addresses from the eNodeB
the route to the to the SeGW.
SeGW

CA server Includes the CA name and the CA server URL.

information

Information about Includes all the next-hop IP addresses from the eNodeB
the routes to the CA to the CA server.
server

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the SeGW

Information about
the VLAN for the
route from the
eNodeB to the CA
server

Information about Includes the common name, issuer, signature algorithm,

the security key size, usage, local name, and local IP address of the
certificate request file device certificate.

NOTE

In IPv4 scenarios, the policy for processing a data flow protected by secure networking (IPsec) is
as follows:
● The route of the data flow is a route of the next hop type, and the outbound port is the
outbound port bound to the secure networking (IPsec) policy.
● If the data flow matches the IPv4 access control rule and the action is "permit", the flow is
protected by secure networking (IPsec). If the data flow matches the IPv4 access control
rule and the action is "deny", the flow is not protected by secure networking (IPsec). If the
data flow does not match the IPv4 access control rule, the flow is not protected by secure
networking (IPsec).

Hardware Preparation
Prepare the hardware listed in Table 1-249.

Table 1-249 Hardware to be prepared

Hardware Description

SeGW A firewall or router that complies with the secure

networking (IPsec) protocol

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 736

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Hardware Description

CA server An operator's CA server. It is used for issuing operator-

issued security certificates to eNodeBs.

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

● Operator device certificate
● Operator trust certificate
If an operator issues its root trust certificate to Huawei, this certificate can be
preconfigured on the eNodeB as the trust certificate.

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Table 1-250 Data preparation for changing the transport network from non-
security mode to PKI security mode

Rec SN Ope MO or MML Configuration Reference

onfi rati Command
gura on
tion
Mod
e

MAE 1 Add DEVIPa For details, see IP eRAN Engineering Guide

- Feature Parameter Description.
Depl
oym 2 Add IPRT/ Add an IP route to the CA server.
ent SRCIPRTb For details, see IP eRAN Engineering Guide
Feature Parameter Description.
3 Add IPRT/ Add an IP route to the SeGW.
SRCIPRTb For details, see IP eRAN Engineering Guide
Feature Parameter Description.
4 Add VLANMAP For details, see IP eRAN Engineering Guide
Feature Parameter Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 737

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO or MML Configuration Reference

onfi rati Command
gura on
tion
Mod
e

5 Add IKEPROPOSA For details, see IPsec Feature Parameter

L Description.
6 Add IKEPEER

7 Add IKECFG

8 Add ACL

9 Add ACLRULE

10 Add IPSECPROPO
SAL

11 Add IPSECPOLICY

12 Add TRUSTCERT For details, see PKI Feature Parameter

Description.
13 Mod CERTREQ
ify

14 Add CA

15 Add CERTMK

16 Mod APPCERT Change the device certificate in use to the

ify operator-issued device certificate.

17 Add IPSECBIND For details, see IPsec Feature Parameter

Description.
MM 1 Add DEVIPa For details, see IP eRAN Engineering Guide
L Feature Parameter Description.
com
man 2 Add IPRT/ Add an IP route to the CA server.
ds SRCIPRTb For details, see IP eRAN Engineering Guide
Feature Parameter Description.
3 Add IPRT/ Add an IP route to the SeGW.
SRCIPRTb For details, see IP eRAN Engineering Guide
Feature Parameter Description.
4 Add VLANMAP For details, see IP eRAN Engineering Guide
Feature Parameter Description.
5 Add IKEPROPOSA For details, see IPsec Feature Parameter
L Description.
6 Add IKEPEER

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 738

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO or MML Configuration Reference

onfi rati Command
gura on
tion
Mod
e

7 Add IKECFG

8 Add ACL

9 Add ACLRULE

10 Add IPSECPROPO
SAL

11 Add IPSECPOLICY

12 Run DLD -
the CERTFILE
MM
L
com
man
d

13 Add TRUSTCERT For details, see PKI Feature Parameter

Description.
14 Mod CERTREQ
ify

15 Add CA

16 Run CRE -
the CERTREQFIL
MM E
L
com
man
d

17 Run ULD You need to use the device certificate

the CERTFILE request file to directly apply for the
MM operator-issued device certificate from the
L operator. Perform the following operations
com only after you have obtained the operator-
man issued device certificate.
d

18 Run DLD -
the CERTFILE
MM
L
com
man
d

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 739

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO or MML Configuration Reference

onfi rati Command
gura on
tion
Mod
e

19 Add CERTMK For details, see PKI Feature Parameter

Description.
20 Mod APPCERT Change the device certificate in use to the
ify operator-issued device certificate.

21 Add IPSECBIND For details, see IPsec Feature Parameter

Description.
a: If the eNodeB uses different device IP addresses to perform IKE negotiation,
apply for the operator-issued security certificate, and update the operator-issued
security certificate, you need to add device IP addresses, the number of which is
based on the number of IP addresses.
b: To simplify configurations when one device IP address maps multiple
destination IP addresses, you are advised to configure the source IP route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. If the eNodeB can communicate with the CA server through the non-
security domain, you are advised to use the batch configuration mode of the
MAE-Deployment to configure base stations in batches or to use the MAE-
Deployment GUI to configure a single base station. If the eNodeB can
communicate with the CA server only through the security domain, you can only
use MML commands. The three data preparation modes are described as follows:
NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario-specific template being "Changing the Transport
Network from Non-Security Mode to PKI Security Mode"): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 740

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

MML Configuration Script Example

In the following example, an IP address for applying for the operator-issued
security certificate does not need to be added, the local IP address of the OM
channel is used as the IP address for updating the certificate, and the eNodeB is
not on the same network segment as the SeGW.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address for performing IKE negotiation*/
ADD DEVIP:SN=7,SBT=BASE_BOARD,PT=ETH,PN=0,IP="192.168.53.6",MASK="255.255.255.0";
/*Adding an IP route to the CA server*/
ADD IPRT:RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="10.148.25.179", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Adding an IP route to the SeGW*/
ADD IPRT:RTIDX=1, SN=7, SBT=BASE_BOARD, DSTIP="192.168.54.7", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.53.110",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,
SETPRIO=DISABLE;
/*Adding an IKE proposal*/
ADD IKEPROPOSAL: PROPID=1, ENCALG=AES128, AUTHALG=SHA256, AUTHMETH=IKE_RSA_SIG,
DHGRP=DH_GROUP15;
/*Adding an IKE peer*/
ADD IKEPEER: PEERNAME="ikepeer", PROPID=1, IKEVERSION=IKE_V2, EXCHMODE=AGGRESSIVE,
IPVERSION=IPV4, IDTYPE=FQDN, REMOTEIP="192.168.54.7", REMOTENAME="segw", DPD=PERIODIC,
LOCALIP="192.168.53.6";
/*Setting basic IKE configurations*/
SET IKECFG:IKELNM="s-segw";
/*Adding an ACL*/
ADD ACL: ACLID=3007, ACLDESC="ipsec";
/*Adding an ACL rule*/
/*In separate encryption mode, the SIP in the ACL rule must not contain the local IP address of the OM
channel. In unified encryption mode, the SIP in the ACL rule must contain the local IP address of the OM
channel.*/
ADD ACLRULE:ACLID=3007, RULEID=1, PT=IP, SIP="0.0.0.9", SWC="255.255.255.0", DIP="0.0.0.0",
DWC="255.255.255.255", MDSCP=NO;
/*Adding an IPsec proposal*/
ADD IPSECPROPOSAL: PROPNAME="ipsecprop", TRANMODE=ESP;
/*Adding an IPsec policy*/
ADD IPSECPOLICY: SPGN="ipsecpol", SPSN=1, ACLTYPE=IPV4, ACLID=3007, PROPNAME="ipsecprop",
PEERNAME="ikepeer", LTCFG=LOCAL;
/*Downloading the operator's trust certificate*/
DLD CERTFILE:IP="172.21.241.98", USR="admin", PWD="*****", SRCF="operator.pem", DSTF="operator.pem";
/*It takes approximately 30s to download the operator's trust certificate. You cannot perform the
subsequent operations before the download is completed.*/
/*Save the following MML commands as another script file. Run these commands only after the value of

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 741

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Status changes to Succeeded in the execution result of the DLD CERTFILE command (indicating that the
operator's trust certificate is downloaded successfully.)*/
/*Adding the operator's trust certificate*/
ADD TRUSTCERT:CERTNAME="operator.pem";
/*Modifying the registration information used to create the certificate request*/
MOD CERTREQ: COMMNAME=ESN, COUNTRY="CN", ORG="huawei", ORGUNIT="huawei",
STATEPROVINCENAME="guangdong", LOCALITY="shenzhen",
KEYUSAGE=DATA_ENCIPHERMENT-1&DIGITAL_SIGNATURE-1&KEY_AGREEMENT-1&KEY_ENCIPHERMENT-1,
SIGNALG=SHA256, KEYSIZE=KEYSIZE2048, LOCALNAME="s-segw", LOCALIP="192.168.53.6";
/*Adding a certificate authority. (The local IP address of the OM channel is used as the IP address for
updating the operator's certificate.)*/
ADD CA:CANAME="C = CN,S = guangdong,O = huawei,CN = aksz", URL="http://10.148.25.179:8080";
/*Generating a device certificate request file*/
CRE CERTREQFILE:FILENAME="cert.req",REQMODE=NEW;
/*Uploading the device certificate request file*/
ULD CERTFILE:IP="172.21.241.193", USR="admin", PWD="*****", SRCF="cert.req", DSTF="cert.req";
/*You need to use the device certificate request file to directly apply for the operator-issued device
certificate from the operator. So, save the following MML commands as another script file and perform the
following operations only after you have obtained the operator-issued device certificate.*/
/*Downloading the operator-issued device certificate*/
DLD CERTFILE:IP="172.21.241.193",USR="admin",PWD="*****",SRCF="opkidev.pem",DSTF="opkidev.pem";
/*It takes approximately 30s to download the operator-issued device certificate. You cannot perform the
subsequent operations before the download is completed.*/
/*Save the following MML commands as another script file. Run these commands only after the value of
Status changes to Succeeded in the execution result of the DLD CERTFILE command (indicating that the
operator-issued device certificate is downloaded successfully.)*/
/*Adding the operator-issued device certificate*/
ADD CERTMK:APPCERT="opkidev.pem";
/*Changing the device certificate in use to the operator-issued device certificate*/
MOD APPCERT:APPTYPE=IKE, APPCERT="opkidev.pem";
/*Binding the IPsec policy group*/
ADD IPSECBIND: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, SPGN="ipsecpol";

1.9.1.3 Engineering Implementation

This section describes the engineering implementation for changing the
networking mode from non-secure to PKI security mode, including prerequisites,
context, and procedure.

Prerequisites
The information, hardware, security certificates, and data for changing the
transport network from non-security mode to PKI security mode are ready. The
license file is available in the save path on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 742

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Local Operations
N/A
– Remote Operations
Use the MAE-Deployment to deliver the data to the base station and
then activate the data.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the following commands on the MAE-Access to back up and
export the configuration file. The configuration file can be used to
restore the base station to the pre-reconfiguration status if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iv. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
v. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
vi. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Using MML commands:
– Local Operations
Run MML commands on the LMT to deliver the data to the base station
and then activate the data.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the following commands on the LMT to back up and export the
configuration file. The configuration file can be used to restore the
base station if the reconfiguration fails.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 743

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1) To back up the configuration file, run the BKP CFGFILE

command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Use the LMT to deliver the batch configuration script prepared
according to Engineering Preparation > Data Preparation to the
base station and activate the script on the base station. For details,
see 1.3.2 Running MML Commands on the LMT.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Remote Operations
N/A
----End

Follow-up Procedure
After the Procedure is completed, change the next-hop IP address of the router
that connects to the SeGW in the transport network to the IP address of the
SeGW. The IP address setting allows the eNodeB to establish IPsec tunnels with
the SeGW for protecting the communication data between the eNodeB and the
CN as well as MAE. This changes the transport network from non-security mode
to PKI security mode.

1.9.1.4 Engineering Verification

This section describes how to verify the change of the transport network from
non-security mode to PKI security mode.

Procedure
Step 1 Verify that ALM-25891 IKE Negotiation Failure is not reported.
If ALM-25891 IKE Negotiation Failure is reported, clear the alarm according to
the instructions in 3900 & 5900 Series Base Station Alarm Reference.
Step 2 Run the DSP APPCERT command to check whether the device certificate in use is
the operator-issued device certificate.
If it is not the operator-issued device certificate, run the DSP CERTMK command
to check whether the operator-issued device certificate is available.
● If it is available, run the MOD APPCERT command to replace the device
certificate in use with the operator-issued device certificate.
● If it is unavailable, run the REQ DEVCERT command to apply for an operator-
issued device certificate. Then run the command to replace the device
certificate in use with the operator-issued device certificate.
Step 3 Run the DSP TRUSTCERT command to check whether the operator's trust
certificate is included in the command output and Status is Normal.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 744

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If the operator's trust certificate is not included in the command output or Status
is not Normal, run the LST TRUSTCERT command to check whether the
operator's trust certificate is configured.
● If it is configured, run the RMV TRUSTCERT command to delete the
configuration. Run the DLD CERTFILE command to download an operator's
trust certificate again. Then, run the ADD TRUSTCERT command to add the
operator's trust certificate.
● If it is not configured, run the DLD CERTFILE command to download an
operator's trust certificate. Then, run the ADD TRUSTCERT command to add
the operator's trust certificate.
Step 4 Run the LST CA command to check whether the current certificate authority is
correctly configured. That is, Certificate Authority Name and Certificate
Authority URL are the same as the real name of the certificate authority and the
real URL of the CA server, respectively.
If the configurations are incorrect, perform the following steps to modify the
certificate authority configurations:
1. Run the RMV CA command to remove the original certificate authority.
2. Run the ADD CA command to add a correct certificate authority.

----End

1.9.1.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Remote rollback
If the OM channel is interrupted due to reconfiguration failures and secure
PnP can be performed for the bearer network, the OM channel can be
automatically set up in a secure manner. Perform the following steps to check
whether the bearer network meets the following secure PnP conditions:
a. Check whether the configurations of the bearer network devices such as
the public DHCP server, router, and SeGW meet secure PnP requirements.
For details about secure PnP requirements for bearer network devices, see
the corresponding configuration requirements in Automatic OMCH
Establishment Feature Parameter Description.
b. Check whether the DHCP configuration and route configuration of the
MAE exist and are consistent with the configurations of the current
bearer network.
If the configurations do not exist or are inconsistent with the current
bearer network, reconfigure the DHCP and route of the MAE to ensure
that they are consistent with the configurations of the current bearer
network.
For details about requirements and preparations for MAE DHCP and
route configurations, see the corresponding configuration requirements in

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 745

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Automatic OMCH Establishment Feature Parameter Description. For

details about how to configure DHCP for the MAE, see Managing the
DHCP Information about Base Stations and Starting/Stopping VLAN
Detecting in the MAE-Access online help. For details about how to
configure the MAE route, see Setting the Routes of the MAE Server in
MAE Administrator Guide.
After the OM channel resumes, perform the following operations to remotely
roll back the configuration data:
a. On the MAE-Access, run DLD CFGFILE to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run ACT CFGFILE to activate the original configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Local rollback
If the OM channel is interrupted but the bearer network does not meet secure
PnP requirements, the configuration data can only be rolled back locally using
the LMT.
a. On the LMT, run DLD CFGFILE to download the original configuration
file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run ACT CFGFILE to activate the original configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Roll back the configuration data using the one-click blind configuration
rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 746

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the transport network.

Step 4 Verify that the engineering rollback is successful.

1. Run the DSP CELL command. Verify that Cell instance state is Normal for
the cell.

If Cell instance state is Uninstall, check the cell configuration or hardware

based on the value of Reason for latest state change in the command
output.
2. Verify that no ALM-25901 Remote Maintenance Link Failure is reported.

If ALM-25901 Remote Maintenance Link Failure is reported, clear the alarm

according to the instructions in 3900 & 5900 Series Base Station Alarm
Reference.
----End

1.9.2 Changing the Transport Network from Non-Security

Mode to PKI Security Mode (New Model)
This section describes how to change the transport network from non-security
mode to PKI security mode (new model).

Prerequisites
NOTE

In the new model (when TRANSCFGMODE in the GTRANSPARA MO is set to NEW), only
the reconstruction for which the mode is interface VLAN and the IPSECBINDMODE
parameter of the IKECFG MO is SINGLE is supported.
● The PKI-supported security gateway (SeGW) has been deployed, the Internet
Protocol Security (IPsec) and PKI parameters and the route from the SeGW to
the eNodeB have been configured, and the eNodeB service and OMCH are
normal.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 747

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● The Certificate Authority (CA) server has been deployed, and configurations
are complete, such as those on the security certificate of the CA server and
the route from the CA server to the eNodeB.
● The next hop from the eNodeB to the SeGW and that from the eNodeB to the
CA belong to the same VLAN.

1.9.2.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the transport network
from non-security mode to PKI security mode.

Application Scenario
The operator requires the transport network to operate in PKI security mode
instead of non-security mode.

Reconfiguration Impact
When the transport network is changed from non-security mode to PKI security
mode, transmission links that enter the security network (protected transmission
links) and services carried on these links will be interrupted.

Reconfiguration Scheme
Figure 1-137 and Figure 1-139 show the reconfiguration procedures for changing
the transport network from non-security mode to PKI security mode. Determine
the reconfiguration scheme for changing the transport network from non-security
mode to PKI security mode according to the following table.

Table 1-251 Scheme options

If... Then...

A new IPv4/IPv6 address is required for Add an IPv4/IPv6 address. It is

IKE negotiation recommended that a device IP address
not used by any service be added.

A new IPv4/IPv6 address is required for Add an IPv4/IPv6 address.

applying for an operator-issued It is required that the eNodeB use this
security certificate IP address to communicate with the
MAE-Deployment is used for CA server through the non-security
reconfiguration domain during the reconfiguration.
Unified encryption is used
The CA server is located in the non-
security domain

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 748

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If... Then...

A new IPv4/IPv6 address is required for Add an IPv4/IPv6 address.

applying for an operator-issued
security certificate
Unified encryption or separate
encryption is used
The CA server is located in the security
or non-security domain
When the CA server is in the security
domain, it is required that the eNodeB
use this IP address to communicate
with the CA server through the
security domain. When the CA server is
in the non-security domain, it is
required that the eNodeB use this IP
address to communicate with the CA
server through the non-security
domain.

No route is available between the Add a route from the eNodeB to the
eNodeB and SeGW SeGW and the corresponding
VLANMAP MO.

NOTE

● The two encryption modes are as follows:

● In separate encryption, data on the OM channel is encrypted in SSL mode but does not
enter the secure networking (IPsec) tunnel.
● In unified encryption, data on the OM channel is encrypted in SSL mode and enters the
secure networking (IPsec) tunnel.
● IPv4/IPv6 addresses are not required for applying for the operator-issued device certificate in
the following situations:
● If the eNodeB can communicate with the CA server only through the security domain,
the reconfiguration cannot be performed using the MAE-Deployment.
● When reconfiguration is performed using MML commands, the operator-issued security
certificates can be applied for only in offline mode.
● When the separate encryption mode is used and the CA server is in the non-security
domain, the local IP address of the OM channel is recommended for applying for the
operator-issued security certificates.
● The local IP address of the OM channel is recommended to be used as the IPv4/IPv6 address
for updating the operator-issued security certificates when the unified encryption mode is
used and the CA server is in the security domain or when the separate encryption mode is
used and the CA server is in the non-security domain. Therefore, an IPv4/IPv6 address for
updating the operator-issued security certificates does not need to be added.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 749

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-137 Procedure for changing the transport network from non-security
mode to PKI security mode (using the MAE-Deployment, IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 750

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-138 Procedure for changing the transport network from non-security
mode to PKI security mode (using the MAE-Deployment, IPv6)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 751

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-139 Procedure for changing the transport network from non-security
mode to PKI security mode (using MML commands, IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 752

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-140 Procedure for changing the transport network from non-security
mode to PKI security mode (using MML commands, IPv6)

Topology Change
Figure 1-141 shows the topologies before and after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 753

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the operator-issued security certificate needs to be requested or updated, the eNodeB will
access the CA server to apply for or update the certificate.

Figure 1-141 Topologies before and after the reconfiguration

1.9.2.2 Engineering Preparation

This section describes the engineering preparation for changing the transport
network from non-security mode to PKI security mode, including information
collection and preparation of hardware, software, license files, security certificates,
and data. It also describes the data preparation mode and provides MML
configuration script examples.

Information Collection
Table 1-252 describes the information to be collected for data preparation.

Table 1-252 Information to be collected

Information Description

Internet Key Includes the name, encryption algorithm, and integrity

Exchange (IKE) algorithm of the IKE proposal, and the life cycle of the
proposal IKE security association (SA).

Local IKE information Includes the local IKE name, IKE version, and
negotiation mode.

Access control rule Used for data flows that require IPsec protection.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 754

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

IPsec proposal Includes the name, encapsulation mode, encryption

algorithm, and authentication algorithm of the IPsec
proposal.

IPsec policy Includes the IKE proposal name, IPsec proposal name,
access control list (ACL) ID, and IPsec SA life cycle.

IP address of the Used for establishing IPsec tunnels.

SeGW

Information about Includes all the next-hop IP addresses from the eNodeB
the route to the to the SeGW.
SeGW

CA server Includes the CA name and the CA server URL.

information

Information about Includes all the next-hop IP addresses from the eNodeB
the routes to the CA to the CA server.
server

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
routes from the
eNodeB to the SeGW

Information about
the VLAN for the
route from the
eNodeB to the CA
server

Information about Includes the common name, issuer, signature algorithm,

the security key size, usage, local name, and local IP address of the
certificate request file device certificate.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 755

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

● IPv4 access control rules use ACL/ACLRULE, and IPv6 access control rules use ACL6/
ACLRULE6.
● In IPv4 scenarios, the policy for processing IPsec data flows is as follows:
● The route of the data flow is a route of the next hop type, and the outbound port is the
outbound port bound to the IPsec policy.
● If the data flow matches the IPv4 access control rule and the action is "permit", IPsec is
performed. If the data flow matches the IPv4 access control rule and the action is
"deny", IPsec is not performed. If the data flow does not match the IPv4 access control
rule, IPsec is not performed.
● In IPv6 scenarios, the policy for processing IPsec data flows is as follows:
● The route of the data flow is a route of the interface type, and the interface is the
TUNNELITF bound to the IPsec policy.
● If the data flow matches the IPv6 access control rule and the action is "permit", IPsec
will be performed. If the data flow matches the IPv6 access control rule and the action
is "deny", IPsec will not be performed. If the data flow does not match the IPv6 access
control rule, packets will be discarded.
● The IPSECBIND6 MO is used for IPv6 policy information binding.

Hardware Preparation
Prepare the hardware listed in Table 1-253.

Table 1-253 Hardware to be prepared

Hardware Description

SeGW Supports the firewall or router that complies

with the IPsec protocol.

CA server An operator's CA server. It is used for issuing

operator-issued security certificates to eNodeBs.

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

● Operator device certificate
● Operator trust certificate
If an operator issues its root trust certificate to Huawei, this certificate can be
preconfigured on the eNodeB as the trust certificate.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 756

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Table 1-254 Data preparation for changing the transport network from non-
security mode to PKI security mode
Rec SN Ope MO or MML Configuration Reference
onfi rati Command
gura on
tion
Mod
e

MAE 1 Add IPv4: For details, see IP eRAN Engineering Guide

- IPADDR4a Feature Parameter Description.
Depl IPv6:
oym
IPADDR6a
ent
2 Add IPv4: Add an IP route to the CA server.
IPROUTE4/ For details, see IP eRAN Engineering Guide
SRCIPROUTE Feature Parameter Description.
4b
IPv6:
IPROUTE6

3 Add IPv4: Add an IP route to the SeGW.

IPROUTE4/ For details, see IP eRAN Engineering Guide
SRCIPROUTE Feature Parameter Description.
4b
IPv6:
IPROUTE6

4 Add IKEPROPOSA For details, see IPsec Feature Parameter

L Description.
5 Add IKEPEER

6 Add IKECFG

7 Add IPv4: ACL

IPv6: ACL6

8 Add IPv4:
ACLRULE
IPv6:
ACLRULE6

9 Add IPSECPROPO
SAL

10 Add IPSECPOLICY

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 757

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO or MML Configuration Reference

onfi rati Command
gura on
tion
Mod
e

11 Add TRUSTCERT For details, see PKI Feature Parameter

Description.
12 Mod CERTREQ
ify

13 Add CA

14 Add CERTMK

15 Mod APPCERT Change the device certificate in use to the

ify operator-issued device certificate.

16 Add IPv4: N/A For details, see IPsec Feature Parameter

IPv6: Description.
TUNNELITF

17 Add IPv4: N/A

IPv6:
IPROUTE6

18 Add IPv4: N/A

IPv6:
INTERFACE

19 Add IPSECBIND

MM 1 Add IPv4: For details, see IP eRAN Engineering Guide

L IPADDR4a Feature Parameter Description.
com IPv6:
man
IPADDR6a
ds
2 Add IPv4: Add an IP route to the CA server.
IPROUTE4/ For details, see IP eRAN Engineering Guide
SRCIPROUTE Feature Parameter Description.
4b
IPv6:
IPROUTE6

3 Add IPv4: Add an IP route to the SeGW.

IPROUTE4/ For details, see IP eRAN Engineering Guide
SRCIPROUTE Feature Parameter Description.
4b
IPv6:
IPROUTE6

4 Add IKEPROPOSA For details, see IPsec Feature Parameter

L Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 758

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO or MML Configuration Reference

onfi rati Command
gura on
tion
Mod
e

5 Add IKEPEER

6 Add IKECFG

7 Add IPv4: ACL

IPv6: ACL6

8 Add IPv4:
ACLRULE
IPv6:
ACLRULE6

9 Add IPSECPROPO
SAL

10 Add IPSECPOLICY

11 Run DLD -
ning CERTFILE
MM
L
com
man
ds

12 Add TRUSTCERT For details, see PKI Feature Parameter

Description.
13 Mod CERTREQ
ify

14 Add CA

15 Run CRE -
ning CERTREQFIL
MM E
L
com
man
ds

16 Run ULD You need to use the device certificate

ning CERTFILE request file to directly apply for the
MM operator-issued device certificate from the
L operator. Perform the following operations
com only after you have obtained the operator-
man issued device certificate.
ds

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 759

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO or MML Configuration Reference

onfi rati Command
gura on
tion
Mod
e

17 Run DLD -
ning CERTFILE
MM
L
com
man
ds

18 Add CERTMK For details, see PKI Feature Parameter

Description.
19 Mod APPCERT Change the device certificate in use to the
ify operator-issued device certificate.

20 Add IPv4: N/A For details, see IPsec Feature Parameter

IPv6: Description.
TUNNELITF

21 Add IPv4: N/A

IPv6:
IPROUTE6

22 Add IPv4: N/A

IPv6:
INTERFACE

23 Add IPSECBIND

a: If the eNodeB uses different IPv4/IPv6 addresses to perform IKE negotiation,

apply for the operator-issued device certificate, and update the operator-issued
device certificate, you need to add IPv4/IPv6 addresses, the number of which is
based on the number of IP addresses.
b: To simplify configurations when one IPv4 address maps multiple destination
IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. If the eNodeB can communicate with the CA server through the non-
security domain, you are advised to use the batch configuration mode of the
MAE-Deployment to configure base stations in batches or to use the MAE-
Deployment GUI to configure a single base station. If the eNodeB can
communicate with the CA server only through the security domain, you can only
use MML commands. The three data preparation modes are described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 760

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario-specific template being "Changing the Transport
Network from Non-Security Mode to PKI Security Mode"): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, an IP address for applying for the operator-issued
security certificate does not need to be added, the local IP address of the OM
channel is used as the IP address for updating the certificate, and the eNodeB is
not on the same network segment as the SeGW.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";

IPv4 transmission:
/*Adding an IPv4 address for performing IKE negotiation*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, TAGGED=ENABLE, VLANID=101, VRFIDX=0;
ADD IPADDR4: ITFID=0, IP="192.168.53.6", MASK="255.255.255.0";
/*Adding an IPv4 route to the CA server*/
ADD IPROUTE4: RTIDX=0, DSTIP="10.148.25.179", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Adding an IPv4 route to the SeGW*/
ADD IPROUTE4: RTIDX=1, DSTIP="192.168.54.7", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Adding an IKE proposal*/
ADD IKEPROPOSAL: PROPID=1, ENCALG=AES128, AUTHALG=SHA256, AUTHMETH=IKE_RSA_SIG,

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 761

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

DHGRP=DH_GROUP15;
/*Adding an IKE peer*/
ADD IKEPEER: PEERNAME="ikepeer", PROPID=1, IKEVERSION=IKE_V2, EXCHMODE=AGGRESSIVE,
IPVERSION=IPV4, IDTYPE=FQDN, REMOTEIP="192.168.54.7", REMOTENAME="segw", DPD=PERIODIC,
LOCALIP="192.168.53.6";
/*Setting basic IKE configurations*/
SET IKECFG: IKELNM="s-segw";
/*Adding an ACL*/
ADD ACL: ACLID=3007, ACLDESC="ipsec";
/*Adding an ACL rule*/
/*In separate encryption mode, the SIP in the ACL rule must not contain the local IP address of the OM
channel. In unified encryption mode, the SIP in the ACL rule must contain the local IP address of the OM
channel.*/
ADD ACLRULE: ACLID=3007, RULEID=1, PT=IP, SIP="0.0.0.9", SWC="255.255.255.0", DIP="0.0.0.0",
DWC="255.255.255.255", MDSCP=NO;
/*Adding an IPsec proposal*/
ADD IPSECPROPOSAL: PROPNAME="ipsecprop", TRANMODE=ESP;
/*Adding an IPsec policy*/
ADD IPSECPOLICY: SPGN="ipsecpol", SPSN=1, ACLTYPE=IPV4, ACLID=3007, PROPNAME="ipsecprop",
PEERNAME="ikepeer", LTCFG=LOCAL;
/*Downloading the operator's trust certificate*/
DLD CERTFILE: IP="172.21.241.98", USR="admin", PWD="*****", SRCF="operator.pem",
DSTF="operator.pem";
/*It takes approximately 30s to download the operator's trust certificate. You cannot perform the
subsequent operations before the download is completed.*/
/*Save the following MML commands as another script file. Run these commands only after the value of
Status changes to Succeeded in the execution result of the DLD CERTFILE command (indicating that the
operator's trust certificate is downloaded successfully.*/
/*Adding the operator's trust certificate*/
ADD TRUSTCERT: CERTNAME="operator.pem";
/*Modifying the registration information used to create the certificate request*/
MOD CERTREQ: COMMNAME=ESN, COUNTRY="CN", ORG="huawei", ORGUNIT="huawei",
STATEPROVINCENAME="guangdong", LOCALITY="shenzhen", KEYUSAGE=DATA_ENCIPHERMENT-1,
SIGNALG=SHA256, KEYSIZE=KEYSIZE2048, LOCALNAME="s-segw", LOCALIP="192.168.53.6";
/*Adding a certificate authority. (The local IP address of the OM channel is used as the IP address for
updating the operator's certificate.)*/
ADD CA: CANAME="C = CN,S = guangdong,O = huawei,CN = aksz", URL="http://10.148.25.179:8080";
/*Generating a device certificate request file*/
CRE CERTREQFILE:FILENAME="cert.req",REQMODE=NEW;
/*Uploading the device certificate request file*/
ULD CERTFILE: IP="172.21.241.193", USR="admin", PWD="*****", SRCF="cert.req", DSTF="cert.req";
/*You need to use the device certificate request file to directly apply for the operator-issued device
certificate from the operator. So, save the following MML commands as another script file and perform the
following operations only after you have obtained the operator-issued device certificate.*/
/*Downloading the operator-issued device certificate*/
DLD CERTFILE:IP="172.21.241.193",USR="admin",PWD="*****",SRCF="opkidev.pem",DSTF="opkidev.pem";
/*It takes approximately 30s to download the operator-issued device certificate. You cannot perform the
subsequent operations before the download is completed.*/
/*Save the following MML commands as another script file. Run these commands only after the value of
Status changes to Succeeded in the execution result of the DLD CERTFILE command (indicating that the
operator-issued device certificate is downloaded successfully.*/
/*Loading the operator-issued device certificate*/
ADD CERTMK:APPCERT="opkidev.pem";
/*Changing the device certificate in use to the operator-issued device certificate*/
MOD APPCERT: APPTYPE=IKE, APPCERT="opkidev.pem";
/*Binding the IPsec policy group to an interface*/
ADD IPSECBINDITF: IPSECBINDITFID=1, SPGN="ipsecpol", ITFID=0;

IPv6 transmission:
/*Adding an IPv6 address for performing IKE negotiation*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
ADD INTERFACE: ITFID=1, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=1003, IPV6SW=ENABLE;
ADD IPADDR6: IPADDR6ID="1", ITFID=1, IPV6="2010::221", PFXLEN=64;
/*Adding a loopback IPv6 address for performing IKE negotiation*/
ADD LOOPBACK: PORTID=0, SN=7;
ADD INTERFACE: ITFID=2, ITFTYPE=NORMAL, PT=LOOPINT, PORTID=0, IPV6SW=ENABLE;
ADD IPADDR6: IPADDR6ID="2", ITFID=2, IPV6="2010:1:10:10:10::221", PFXLEN=128;
/*Adding a tunnel interface for performing IKE negotiation*/
ADD TUNNELITF: PORTID=0, MODE=IPSEC_IPV6, LOCALIP6="2010::221", REMOTEIP6="2002:812::8111:1";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 762

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD INTERFACE: ITFID=3, ITFTYPE=NORMAL, PT=TUNNELITF, PORTID=0, IPV6SW=ENABLE;

/*Adding an IPv6 route to the SeGW*/
ADD IPROUTE6: RTIDX=1, DSTIP="2002:812::8111:1", PFXLEN=128, RTTYPE=NEXTHOP, NEXTHOP="2010::3";
/*Adding an IPv6 route to the core network*/
ADD IPROUTE6: RTIDX=2, DSTIP="2193:1:50::", PFXLEN=64, RTTYPE=IF, ITFID=3;
ADD IPROUTE6: RTIDX=2, DSTIP="2193:100:50::", PFXLEN=64, RTTYPE=IF, ITFID=3;
/*Adding an IKE proposal*/
ADD IKEPROPOSAL: PROPID=1, ENCALG=AES128, AUTHALG=SHA256, AUTHMETH=IKE_RSA_SIG,
DHGRP=DH_GROUP15;
/*Adding an IKE peer*/
ADD IKEPEER: PEERNAME="ikepeer", PROPID=1, IKEVERSION=IKE_V2, IPVERSION=IPV6, IDTYPE=IPV6,
DPD=PERIODIC, CERTSOURCE=APPCERT;
/*Setting basic IKE configurations*/
SET IKECFG: IKELNM="s-segw";
/*Adding an IPv6 ACL*/
ADD ACL6: ACLID=3000, ACLDESC="ipsec";
/*Adding an IPv6 ACL rule*/
/*In separate encryption mode, the SIP in the IPv6 access control rule must not contain the local IP address
of the OMCH. In unified encryption mode, the SIP in the IPv6 access control rule must contain the local IP
address of the OMCH.*/
ADD ACLRULE6: ACLID=3000, RULEID=1, PT=IP6, SIP="2010:1:10:10:10::221", SPFXLEN=128,
DIP="2193:1:50::1", DPFXLEN=128, MDSCP=NO;
ADD ACLRULE6: ACLID=3000, RULEID=2, PT=IP6, SIP="2010:1:10:10:10::221", SPFXLEN=128,
DIP="2193:100:50::10", DPFXLEN=128, MDSCP=NO;
/*Adding an IPsec proposal*/
ADD IPSECPROPOSAL: PROPNAME="ipsecprop", TRANMODE=ESP;
/*Adding an IPsec policy*/
ADD IPSECPOLICY: SPGN="ipsecpol", SPSN=1, ACLTYPE=IPV6, ACLID=3000, PROPNAME="ipsecprop",
PEERNAME="ikepeer", PFS=PFS_GROUP20, LTCFG=LOCAL;
/*Downloading the operator's trust certificate*/
DLD CERTFILE: MODE=IPV4, IP="172.21.241.98", USR="admin", PWD="*****", SRCF="operator.pem", DSTF="
operator.pem ", CT=TRUSTCERT;
/*It takes approximately 30s to download the operator's trust certificate. You cannot perform the
subsequent operations before the download is completed.*/
/*Save the following MML commands as another script file. Run these commands only after the value of
Status changes to Succeeded in the execution result of the DLD CERTFILE command (indicating that the
operator's trust certificate is downloaded successfully.*/
/*Adding the operator's trust certificate*/
ADD TRUSTCERT: CERTNAME="operator.pem";
/*Modifying the registration information used to create the certificate request*/
MOD CERTREQ: LOCALNAME="s-segw", LOCALIP6="2010::221";
/*Adding a certificate authority. (The local IP address of the OM channel is used as the IP address for
updating the operator's certificate.)*/
ADD CA: CANAME="CN=www.ejbca.com,O=EJBCA,C=CN", IPVERSION=IPV6, URL="http://[2010::164:1]:8080/
ejbca/publicweb/cmp/EJBCA_GCY", MODE=CFG_UPD_SIP, UPDSIP6="2010::221", CERTREQSW=DEFAULT;
/*Applying for an operator-issued device certificate from the server*/
REQ DEVCERT: CANAME="CN=www.ejbca.com,O=EJBCA,C=CN", APPCERT="opkidev.pem";
/*Changing the device certificate in use to the operator-issued device certificate*/
MOD APPCERT: APPTYPE=IKE, APPCERT="opkidev.pem";
/*Binding the IPsec policy group to an interface*/
ADD IPSECBINDITF: IPSECBINDITFID=0, SPGN="ipsecpol", ITFID=3;
/*Querying the status of the IPsec SA*/
DSP IPSECSA:;

1.9.2.3 Engineering Implementation

This section describes the engineering implementation for changing the
networking mode from non-secure to PKI security mode, including prerequisites,
context, and procedure.

Prerequisites
The information, hardware, security certificates, and data for changing the
transport network from non-security mode to PKI security mode are ready. The
license file is available in the save path on the FTP server.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 763

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
– Local Operations
N/A
– Remote Operations
Use the MAE-Deployment to deliver the data to the base station and
then activate the data.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the following commands on the MAE-Access to back up and
export the configuration file. The configuration file can be used to
restore the base station to the pre-reconfiguration status if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
data file.
2) Run the ULD CFGFILE command to export the configuration
data file.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iv. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
v. Deliver the configuration data to the base station and activate it. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 764

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

vi. After the reconfiguration is complete, set the eNodeB maintenance

mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Using MML commands:
– Local Operations
Run MML commands on the LMT to deliver the data to the base station
and then activate the data.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the MML commands on the LMT to back up and export the
configuration file. The configuration file can be used to restore the
base station if the reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Use the LMT to deliver the batch configuration script prepared
according to Engineering Preparation > Data Preparation to the
base station and activate the script on the base station. For details,
see 1.3.2 Running MML Commands on the LMT.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Remote Operations
N/A

----End

Follow-up Procedure
After the Procedure is completed, change the next-hop IP address of the router
that connects to the SeGW in the transport network to the IP address of the
SeGW. The IP address setting allows the eNodeB to establish IPsec tunnels with
the SeGW for protecting the communication data between the eNodeB and the
CN as well as MAE. This changes the transport network from non-security mode
to PKI security mode.

1.9.2.4 Engineering Verification

This section describes how to verify the change of the transport network from
non-security mode to PKI security mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 765

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Verify that ALM-25891 IKE Negotiation Failure is not reported.

If ALM-25891 IKE Negotiation Failure is reported, clear the alarm according to

the instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP APPCERT command to check whether the device certificate in use is
the operator-issued device certificate.

If it is not the operator-issued device certificate, run the DSP CERTMK command
to check whether the operator-issued device certificate is available.

● If it is available, run the MOD APPCERT command to replace the device

certificate in use with the operator-issued device certificate.
● If it is unavailable, run the REQ DEVCERT command to apply for an operator-
issued device certificate. Then run the command to replace the device
certificate in use with the operator-issued device certificate.

Step 3 Run the DSP TRUSTCERT command to check whether the operator's trust
certificate is included in the command output and Status is Normal.

If the operator's trust certificate is not included in the command output or Status
is not Normal, run the LST TRUSTCERT command to check whether the
operator's trust certificate is configured.

● If it is configured, run the RMV TRUSTCERT command to delete the

configuration. Run the DLD CERTFILE command to download an operator's
trust certificate again. Then, run the ADD TRUSTCERT command to add the
operator's trust certificate.
● If it is not configured, run the DLD CERTFILE command to download an
operator's trust certificate. Then, run the ADD TRUSTCERT command to add
the operator's trust certificate.

Step 4 Run the LST CA command to check whether the current certificate authority is
correctly configured. That is, Certificate Authority Name and Certificate
Authority URL are the same as the real name of the certificate authority and the
real URL of the CA server, respectively.

If the configurations are incorrect, perform the following steps to modify the
certificate authority configurations:

1. Run the RMV CA command to remove the original certificate authority.

2. Run the ADD CA command to add a correct certificate authority.

----End

1.9.2.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 766

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Remote rollback
If the OM channel is interrupted due to reconfiguration failures and secure
PnP can be performed for the bearer network, the OM channel can be
automatically set up in a secure manner. Perform the following steps to check
whether the bearer network meets the following secure PnP conditions:
a. Check whether the configurations of the bearer network devices such as
the public DHCP server, router, and SeGW meet secure PnP requirements.
For details about secure PnP requirements for bearer network devices, see
the corresponding configuration requirements in Automatic OMCH
Establishment Feature Parameter Description.
b. Check whether the DHCP configuration and route configuration of the
MAE exist and are consistent with the configurations of the current
bearer network.
If the configurations do not exist or are inconsistent with the current
bearer network, reconfigure the DHCP and route of the MAE to ensure
that they are consistent with the configurations of the current bearer
network.
For details about requirements and preparations for MAE DHCP and
route configurations, see the corresponding configuration requirements in
Automatic OMCH Establishment Feature Parameter Description. For
details about how to configure DHCP for the MAE, see Managing the
DHCP Information about Base Stations and Starting/Stopping VLAN
Detecting in the MAE-Access online help. For details about how to
configure the MAE route, see Setting the Routes of the MAE Server in
MAE Administrator Guide.
After the OM channel resumes, perform the following operations to remotely
roll back the configuration data:
a. On the MAE-Access, run DLD CFGFILE to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run ACT CFGFILE to activate the original configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Local rollback
If the OM channel is interrupted but the bearer network does not meet secure
PnP requirements, the configuration data can only be rolled back locally using
the LMT.
a. On the LMT, run DLD CFGFILE to download the original configuration
file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run ACT CFGFILE to activate the original configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Roll back the configuration data using the one-click blind configuration
rollback function.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 767

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

a. Run the DSP ROLCFGINFO command to query the configuration rollback

information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the transport network.
Step 4 Verify that the engineering rollback is successful.
1. Run the DSP CELL command. Verify that Cell instance state is Normal for
the cell.
If Cell instance state is Uninstall, check the cell configuration or hardware
based on the value of Reason for latest state change in the command
output.
2. Verify that no ALM-25901 Remote Maintenance Link Failure is reported.
If ALM-25901 Remote Maintenance Link Failure is reported, clear the alarm
according to the instructions in 3900 & 5900 Series Base Station Alarm
Reference.
----End

1.9.3 Changing the Transport Network from Non-Security

Mode to PSK Security Mode (Old Model)
This section describes how to change the transport network from non-security
mode to pre-shared key (PSK) security mode (old model).

Prerequisites
The PSK-supported security gateway (SeGW) has been deployed, data related to
IPsec and PSK has been configured, and the eNodeB services and OM channels are
both normal.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 768

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.9.3.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the transport network
from non-security mode to PSK security mode.

Application Scenario
The operator requires the transport network to operate in PSK mode instead of
non-security mode.

Reconfiguration Impact
When the transport network is changed from non-security mode to PSK security
mode, transmission links that enter the security network (protected transmission
links) and services carried on these links will be interrupted.

Reconfiguration Scheme
Figure 1-142 shows the reconfiguration procedure for changing the transport
network from non-security mode to PSK security mode. Determine the
reconfiguration scheme for changing the transport network from non-security
mode to PSK security mode according to the following table.

Table 1-255 Scheme options

If... Then...

The device IP address used for IKE Add a device IP address. It is

negotiation is not configured recommended that the device IP
address that does not carry services be
used.

No route is available between the Add a route from the eNodeB to the
eNodeB and the SeGW SeGW and the corresponding
VLANMAP MO.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 769

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-142 Procedure for changing the transport network from non-security
mode to PSK security mode (IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 770

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Figure 1-143 shows the topologies before and after the reconfiguration.

Figure 1-143 Topologies before and after the reconfiguration

1.9.3.2 Engineering Preparation

This section describes the engineering preparation for changing the transport
network from non-security mode to PSK mode, including information collection
and preparation of hardware, software, license files, security certificates, and data.
It also describes the data preparation mode and provides MML configuration
script examples.

Information Collection
Table 1-256 describes the information to be collected for data preparation.

Table 1-256 Information to be collected

Information Description

Internet Key Includes the name, encryption algorithm, and integrity

Exchange (IKE) algorithm of the IKE proposal, and the life cycle of the
proposal IKE security association (SA).

Local IKE information Includes the local IKE name, pre-shared key, IKE version,
and negotiation mode.

Access control rule Used for data flows that require IPsec protection.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 771

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

IPsec proposal Includes the name, encapsulation mode, encryption

algorithm, and authentication algorithm of the IPsec
proposal.

IPsec policy Includes the IKE proposal name, IPsec proposal name,
access control list (ACL) ID, and IPsec SA life cycle.

IP address of the Used for establishing IPsec tunnels.

SeGW

Information about Includes all the next-hop IP addresses from the eNodeB
the route from the to the SeGW.
eNodeB to the SeGW

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
route from the
eNodeB to the SeGW

NOTE

In IPv4 scenarios, the policy for processing a data flow protected by secure networking
(IPsec) is as follows:
● The route of the data flow is a route of the next hop type, and the outbound port is
the outbound port bound to the secure networking (IPsec) policy.
● If the data flow matches the IPv4 access control rule and the action is "permit", the
flow is protected by secure networking (IPsec). If the data flow matches the IPv4
access control rule and the action is "deny", the flow is not protected by secure
networking (IPsec). If the data flow does not match the IPv4 access control rule, the
flow is not protected by secure networking (IPsec).

Hardware Preparation
Prepare the hardware listed in Table 1-257.

Table 1-257 Hardware to be prepared

Hardware Description

SeGW Supports the firewall or router that complies

with the IPsec protocol.

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 772

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Table 1-258 Data preparation for changing the transport network from non-
security mode to PSK security mode
SN Oper MO Configuration Reference
ation

1 Add DEVIP For details, see IP eRAN Engineering

Guide Feature Parameter Description.
2 Add IPRT/SRCIPRTa Add an IP route from the eNodeB to
the SeGW.
3 Add VLANMAP
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
4 Add IKEPROPOSAL For details, see IPsec Feature
Parameter Description.
5 Add IKEPEER

6 Add IKECFG

7 Add ACL

8 Add ACLRULE

9 Add IPSECPROPOSAL

10 Add IPSECPOLICY

11 Add IPSECBIND

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 773

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario-specific template being "Changing the Transport
Network from Non-Security Mode to PSK Security Mode"): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, an IPv4 address used for performing IKE negotiation
needs to be added, and the eNodeB is not on the same network segment as the
SeGW.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address for performing IKE negotiation*/
ADD DEVIP:SN=7,SBT=BASE_BOARD, PT=ETH,PN=0,IP="192.168.53.6",MASK="255.255.255.0";
/*Adding an IP route from the eNodeB to the SeGW*/
ADD IPRT:RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="192.168.54.7", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.53.110",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,
SETPRIO=DISABLE;
/*Adding an IKE proposal*/
ADD IKEPROPOSAL: PROPID=1, ENCALG=AES128, AUTHALG=SHA256, AUTHMETH= PRE_SHARED_KEY,
DHGRP=DH_GROUP15;
/*Adding an IKE peer*/
ADD IKEPEER: PEERNAME="ikepeer", PROPID=1, IKEVERSION=IKE_V2, EXCHMODE=AGGRESSIVE,
IPVERSION=IPV4, IDTYPE=FQDN, REMOTEIP="192.168.54.7", REMOTENAME="segw", DPD=PERIODIC,
LOCALIP="192.168.53.6";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 774

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Setting basic IKE configurations*/

SET IKECFG:IKELNM="s-segw";
/*Adding an ACL*/
ADD ACL:ACLID=3007, ACLDESC="ipsec";
/*Adding an ACL rule*/
ADD ACLRULE:ACLID=3007, RULEID=1, PT=IP, SIP="0.0.0.9", SWC="255.255.255.0", DIP="0.0.0.0",
DWC="255.255.255.255", MDSCP=NO;
/*Adding an IPsec proposal*/
ADD IPSECPROPOSAL:PROPNAME="ipsecprop", TRANMODE=ESP;
/*Adding an IPsec policy*/
ADD IPSECPOLICY: SPGN="ipsecpol", SPSN=1, ACLTYPE=IPV4, ACLID=3007, PROPNAME="ipsecprop",
PEERNAME="ikepeer", LTCFG=LOCAL;
/*Binding the IPsec policy group*/
ADD IPSECBIND:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, SPGN="ipsecpol";

1.9.3.3 Engineering Implementation

This section describes the engineering implementation for changing the transport
network from non-security mode to PSK security mode, including prerequisites,
context, and procedure.

Prerequisites
The information, hardware, security certificates, and data for changing the
transport network from non-security mode to PSK security mode are ready. The
license file is available in the save path on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
– Local Operations
N/A
– Remote Operations
Use the MAE-Deployment to deliver the data to the base station and
then activate the data.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the following commands on the MAE-Access to back up and
export the configuration file. The configuration file can be used to

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 775

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

restore the base station to the pre-reconfiguration status if the

reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iv. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
v. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
vi. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Using MML commands:
– Local Operations
Run MML commands on the LMT to deliver the data to the base station
and then activate the data.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the following commands on the LMT to back up and export the
configuration file. The configuration file can be used to restore the
base station if the reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Use the LMT to deliver the batch configuration script prepared
according to Engineering Preparation > Data Preparation to the
base station and activate the script on the base station. For details,
see 1.3.2 Running MML Commands on the LMT.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 776

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For details, see Setting the Maintenance Mode of the eNodeB to

NORMAL.
– Remote Operations
N/A
----End

Follow-up Procedure
After the Procedure is completed, change the next-hop IP address of the router
that connects to the SeGW in the transport network to the IP address of the
SeGW. The IP address setting allows the eNodeB to establish IPsec tunnels with
the SeGW for protecting the communication data between the eNodeB and the
CN as well as MAE. This changes the transport network from non-security mode
to PSK security mode.

1.9.3.4 Engineering Verification

This section describes how to verify the changing of the transport network from
non-security mode to PSK security mode.

Procedure
Step 1 Verify that ALM-25891 IKE Negotiation Failure is not reported.
If ALM-25891 IKE Negotiation Failure is reported, clear the alarm according to
the instructions in 3900 & 5900 Series Base Station Alarm Reference.

----End

1.9.3.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Context
If the reconfiguration fails, the OM channel will be disconnected. Therefore, the
engineering rollback can be performed only on the local LMT.

Procedure
Step 1 Restore the configuration data.
● On the LMT, download and activate the original configuration file.
a. Run the DLD CFGFILE command to download the configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run the ACT CFGFILE command to activate the configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Roll back the configuration data using the one-click blind configuration
rollback function.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 777

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

a. Run the DSP ROLCFGINFO command to query the configuration rollback

information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the physical connections.
Step 4 Verify that the engineering rollback is successful.
1. Run the DSP CELL command. Verify that Cell instance state is Normal for
the cell.
If Cell instance state is Uninstall, check the cell configuration or hardware
based on the value of Reason for latest state change in the command
output.
2. Verify that no ALM-25901 Remote Maintenance Link Failure is reported.
If ALM-25901 Remote Maintenance Link Failure is reported, clear the alarm
according to the instructions in 3900 & 5900 Series Base Station Alarm
Reference.
----End

1.9.4 Changing the Transport Network from Non-Security

Mode to PSK Security Mode (New Model)
This section describes how to change the transport network from non-security
mode to PSK security mode (new model).

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 778

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Prerequisites
NOTE

In the new model (when TRANSCFGMODE in the GTRANSPARA MO is set to NEW), only
the reconstruction for which the VLAN mode is interface VLAN and the IPSECBINDMODE
parameter of the IKECFG MO is SINGLE is supported.

The PSK-supported security gateway (SeGW) has been deployed, data related to
IPsec and PSK has been configured, and the eNodeB services and OM channels are
both normal.

1.9.4.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the transport network
from non-security mode to PSK security mode.

Application Scenario
The operator requires the transport network to operate in PSK mode instead of
non-security mode.

Reconfiguration Impact
When the transport network is changed from non-security mode to PSK security
mode, transmission links that enter the security network (protected transmission
links) and services carried on these links will be interrupted.

Reconfiguration Scheme
Figure 1-144 shows the reconfiguration procedures for changing the transport
network from non-security mode to PSK security mode. Determine the
reconfiguration scheme according to the following table.

Table 1-259 Scheme options

If... Then...

An IPv4/IPv6 address used for IKE Add an IPv4/IPv6 address. An IPv4/IPv6

negotiation has not been configured address that has not carried services is
recommended.

No route is available between the Add a route from the eNodeB to the
eNodeB and the SeGW SeGW and the corresponding
VLANMAP MO.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 779

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-144 Procedure for changing the transport network from non-security
mode to PSK security mode (IPv4)

Figure 1-145 Procedure for changing the transport network from non-security
mode to PSK security mode (IPv6)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 780

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Figure 1-146 shows the topologies before and after the reconfiguration.

Figure 1-146 Topologies before and after the reconfiguration

1.9.4.2 Engineering Preparation

This section describes the engineering preparation for changing the transport
network from non-security mode to PSK mode, including information collection
and preparation of hardware, software, license files, security certificates, and data.
It also describes the data preparation mode and provides MML configuration
script examples.

Information Collection
Table 1-260 describes the information to be collected for data preparation.

Table 1-260 Information to be collected

Information Description

Internet Key Includes the name, encryption algorithm, and integrity

Exchange (IKE) algorithm of the IKE proposal, and the life cycle of the
proposal IKE security association (SA).

Local IKE information Includes the local IKE name, pre-shared key, IKE version,
and negotiation mode.

Access control rule Used for data flows that require IPsec protection.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 781

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

IPsec proposal Includes the name, encapsulation mode, encryption

algorithm, and authentication algorithm of the IPsec
proposal.

IPsec policy Includes the IKE proposal name, IPsec proposal name,
access control list (ACL) ID, and IPsec SA life cycle.

IP address of the Used for establishing IPsec tunnels.

SeGW

Information about Includes all the next-hop IP addresses from the eNodeB
the route from the to the SeGW.
eNodeB to the SeGW

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
routes from the
eNodeB to the SeGW

NOTE

In IPv4 scenarios, the policy for processing a data flow protected by secure networking
(IPsec) is as follows:
● The route of the data flow is a route of the next hop type, and the outbound port is
the outbound port bound to the secure networking (IPsec) policy.
● If the data flow matches the IPv4 access control rule and the action is "permit", the
flow is protected by secure networking (IPsec). If the data flow matches the IPv4
access control rule and the action is "deny", the flow is not protected by secure
networking (IPsec). If the data flow does not match the IPv4 access control rule, the
flow is not protected by secure networking (IPsec).

Hardware Preparation
Prepare the hardware listed in Table 1-261.

Table 1-261 Hardware to be prepared

Hardware Description

SeGW Supports the firewall or router that complies

with the IPsec protocol.

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 782

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Table 1-262 Data preparation for changing the transport network from non-
security mode to PSK security mode

SN Oper MO Configuration Reference

ation

1 Add IPv4: IPADDR4 For details, see IP eRAN Engineering

IPv6: IPADDR6 Guide Feature Parameter Description.

2 Add IPv4: IPRT/SRCIPRTa Add an IP route from the eNodeB to

IPv6: IPROUTE6 the SeGW.
For details, see IP eRAN Engineering
3 Add IPv4: VLANMAP Guide Feature Parameter Description.
IPv6: N/A

4 Add IKEPROPOSAL For details, see IPsec Feature

Parameter Description.
5 Add IKEPEER

6 Add IKECFG

7 Add IPv4: ACL

IPv6: ACL6

8 Add IPv4: ACLRULE

IPv6: ACLRULE6

9 Add IPSECPROPOSAL

10 Add IPSECPOLICY

11 Add IPv4: N/A

IPv6: TUNNELITF

12 Add IPv4: N/A

IPv6: IPROUTE6

13 Add IPv4: N/A

IPv6: INTERFACE

14 Add IPSECBIND

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 783

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario-specific template being "Changing the Transport
Network from Non-Security Mode to PSK Security Mode"): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, an IP address used for performing IKE negotiation needs
to be added, and the eNodeB is not on the same network segment as the SeGW.

If OMCH parameters are modified by mistake, the OMCH may be disconnected

and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";

IPv4 transmission:
/*Adding an IPv4 address for performing IKE negotiation*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, TAGGED=ENABLE, VLANID=101, VRFIDX=0;
ADD IPADDR4: ITFID=0, IP="192.168.53.6", MASK="255.255.255.0";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 784

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Adding an IPv4 route from the eNodeB to the SeGW*/

ADD IPROUTE4: RTIDX=1, DSTIP="192.168.54.7", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Adding an IKE proposal*/
ADD IKEPROPOSAL: PROPID=1, ENCALG=AES128, AUTHALG=SHA256, AUTHMETH= PRE_SHARED_KEY,
DHGRP=DH_GROUP15;
/*Adding an IKE peer*/
ADD IKEPEER: PEERNAME="ikepeer", PROPID=1, IKEVERSION=IKE_V2, EXCHMODE=AGGRESSIVE,
IPVERSION=IPV4, IDTYPE=FQDN, REMOTEIP="192.168.54.7", REMOTENAME="segw", PKEY="ssegw",
DPD=PERIODIC, LOCALIP="192.168.53.6";
/*Setting basic IKE configurations*/
SET IKECFG: IKELNM="s-segw";
/*Adding an ACL*/
ADD ACL: ACLID=3007, ACLDESC="ipsec";
/*Adding an ACL rule*/
ADD ACLRULE: ACLID=3007, RULEID=1, PT=IP, SIP="0.0.0.9", SWC="255.255.255.0", DIP="0.0.0.0",
DWC="255.255.255.255", MDSCP=NO;
/*Adding an IPsec proposal*/
ADD IPSECPROPOSAL: PROPNAME="ipsecprop", TRANMODE=ESP;
/*Adding an IPsec policy*/
ADD IPSECPOLICY: SPGN="ipsecpol", SPSN=1, ACLTYPE=IPV4, ACLID=3007, PROPNAME="ipsecprop",
PEERNAME="ikepeer", LTCFG=LOCAL;
/*Binding the IPsec policy group to an interface*/
ADD IPSECBINDITF: IPSECBINDITFID=1, SPGN="ipsecpol", ITFID=0;

IPv6 transmission:
/*Adding an IPv6 address for performing IKE negotiation*/
SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
ADD INTERFACE: ITFID=1, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=1003, IPV6SW=ENABLE;
ADD IPADDR6: IPADDR6ID="1", ITFID=1, IPV6="2010::221", PFXLEN=64;
/*Adding a loopback IPv6 address for performing IKE negotiation*/
ADD LOOPBACK: PORTID=0, SN=7;
ADD INTERFACE: ITFID=2, ITFTYPE=NORMAL, PT=LOOPINT, PORTID=0, IPV6SW=ENABLE;
ADD IPADDR6: IPADDR6ID="2", ITFID=2, IPV6="2010:1:10:10:10::221", PFXLEN=128;
/*Adding a tunnel interface for performing IKE negotiation*/
ADD TUNNELITF: PORTID=0, MODE=IPSEC_IPV6, LOCALIP6="2010::221", REMOTEIP6="2002:812::8111:1";
ADD INTERFACE: ITFID=3, ITFTYPE=NORMAL, PT=TUNNELITF, PORTID=0, IPV6SW=ENABLE;
/*Adding an IPv6 route to the SeGW*/
ADD IPROUTE6: RTIDX=1, DSTIP="2002:812::8111:1", PFXLEN=128, RTTYPE=NEXTHOP, NEXTHOP="2010::3";
/*Adding an IPv6 route to the core network*/
ADD IPROUTE6: RTIDX=2, DSTIP="2193:1:50::", PFXLEN=64, RTTYPE=IF, ITFID=3;
ADD IPROUTE6: RTIDX=2, DSTIP="2193:100:50::", PFXLEN=64, RTTYPE=IF, ITFID=3;
/*Adding an IKE proposal*/
ADD IKEPROPOSAL: PROPID=1, ENCALG=AES128, AUTHALG=SHA256, AUTHMETH=IKE_RSA_SIG,
DHGRP=DH_GROUP15;
/*Adding an IKE peer*/
ADD IKEPEER: PEERNAME="ikepeer", PROPID=1, IKEVERSION=IKE_V2, IPVERSION=IPV6, IDTYPE=IPV6,
DPD=PERIODIC, CERTSOURCE=APPCERT;
/*Setting basic IKE configurations*/
SET IKECFG: IKELNM="s-segw";
/*Adding an IPv6 ACL*/
ADD ACL6: ACLID=3000, ACLDESC="ipsec";
/*Adding an IPv6 ACL rule*/
ADD ACLRULE6: ACLID=3000, RULEID=1, PT=IP6, SIP="2010:1:10:10:10::221", SPFXLEN=128,
DIP="2193:1:50::1", DPFXLEN=128, MDSCP=NO;
ADD ACLRULE6: ACLID=3000, RULEID=2, PT=IP6, SIP="2010:1:10:10:10::221", SPFXLEN=128,
DIP="2193:100:50::10", DPFXLEN=128, MDSCP=NO;
/*Adding an IPsec proposal*/
ADD IPSECPROPOSAL: PROPNAME="ipsecprop", TRANMODE=ESP;
/*Adding an IPsec policy*/
ADD IPSECPOLICY: SPGN="ipsecpol", SPSN=1, ACLTYPE=IPV6, ACLID=3000, PROPNAME="ipsecprop",
PEERNAME="ikepeer", PFS=PFS_GROUP20, LTCFG=LOCAL;
/*Binding the IPsec policy group to an interface*/
ADD IPSECBINDITF: IPSECBINDITFID=0, SPGN="ipsecpol", ITFID=3;
/*Querying the status of the IPSec SA*/
DSP IPSECSA:;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 785

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.9.4.3 Engineering Implementation

This section describes the engineering implementation for changing the transport
network from non-security mode to PSK security mode, including prerequisites,
context, procedure, and follow-up procedure.

Prerequisites
The information, hardware, security certificates, and data for changing the
transport network from non-security mode to PSK security mode are ready. The
license file is available in the save path on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
– Local Operations
N/A
– Remote Operations
Use the MAE-Deployment to deliver the data to the base station and
then activate the data.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the following commands on the MAE-Access to back up and
export the configuration file. The configuration file can be used to
restore the base station to the pre-reconfiguration status if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 786

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",

USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iv. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
v. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
vi. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Using MML commands:
– Local Operations
Run MML commands on the LMT to deliver the data to the base station
and then activate the data.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the following commands on the LMT to back up and export the
configuration file. The configuration file can be used to restore the
base station if the reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Use the LMT to deliver the batch configuration script prepared
according to Engineering Preparation > Data Preparation to the
base station and activate the script on the base station. For details,
see 1.3.2 Running MML Commands on the LMT.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Remote Operations
N/A
----End

Follow-up Procedure
After the Procedure is completed, change the next-hop IP address of the router
that connects to the SeGW in the transport network to the IP address of the

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 787

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SeGW. The IP address setting allows the eNodeB to establish IPsec tunnels with
the SeGW for protecting the communication data between the eNodeB and the
CN as well as MAE. This changes the transport network from non-security mode
to PSK security mode.

1.9.4.4 Engineering Verification

This section describes how to verify the change of the transport network from
non-security mode to PSK security mode.

Procedure
Step 1 Verify that ALM-25891 IKE Negotiation Failure is not reported.

If ALM-25891 IKE Negotiation Failure is reported, clear the alarm according to

the instructions in 3900 & 5900 Series Base Station Alarm Reference.

----End

1.9.4.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Context
If the reconfiguration fails, the OM channel will be disconnected. Therefore, the
engineering rollback can be performed only on the local LMT.

Procedure
Step 1 Restore the reconfiguration data.
● On the LMT, download and activate the original configuration file.
a. Run the DLD CFGFILE command to download the configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run the ACT CFGFILE command to activate the configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Roll back the configuration data using the one-click blind configuration
rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 788

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that the engineering rollback is successful.

1. Run the DSP CELL command. Verify that Cell instance state is Normal for
the cell.

If Cell instance state is Uninstall, check the cell configuration or hardware

based on the value of Reason for latest state change in the command
output.
2. Verify that no ALM-25901 Remote Maintenance Link Failure is reported.

If ALM-25901 Remote Maintenance Link Failure is reported, clear the alarm

according to the instructions in 3900 & 5900 Series Base Station Alarm
Reference.
----End

1.9.5 Changing the Security Mode from PSK to PKI

This section describes how to change the security mode from PSK to PKI.

Prerequisites
● Data related to secure networking (IPsec) and PKI has been configured, and
the base station services and OM channel are normal.
● The CA server has been deployed, and configurations are complete, such as
those on the security certificate of the CA server and the route from the CA
server to the eNodeB.

1.9.5.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the security mode
from PSK to PKI.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 789

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Application Scenario
The operator requires the use of PKI to enhance transmission security.

Reconfiguration Impact
When the security mode of transmission links is changed to PKI, the transmission
links and services carried on these links will be interrupted.

Reconfiguration Scheme
Figure 1-147 and Figure 1-149 show the reconfiguration procedure for changing
the security mode from PSK to PKI. Determine the reconfiguration scheme for
changing the security mode from PSK to PKI according to the following table.

Table 1-263 Scheme options

If… Then...

A new device IP address is required for Add a device IP address.

applying for an operator-issued It is required that the eNodeB use this
security certificate IP address to communicate with the
MAE-Deployment is used for CA server through the non-security
reconfiguration domain during the reconfiguration.
Unified encryption is used
The CA server is located in the non-
security domain

A new device IP address is required for Add a device IP address.

updating operator-issued security
certificates
Unified encryption or separate
encryption is used
The CA server is located in the security
or non-security domain
When the CA server is in the security
domain, it is required that the eNodeB
use this IP address to communicate
with the CA server through the
security domain. When the CA server is
in the non-security domain, it is
required that the eNodeB use this IP
address to communicate with the CA
server through the non-security
domain.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 790

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

● The two encryption modes are as follows:

● In separate encryption, data on the OM channel is encrypted in SSL mode but does not
enter the IPsec tunnel.
● In unified encryption, data on the OM channel is encrypted in SSL mode and enters the
IPsec tunnel.
● Device IP addresses are not required for applying for the operator-issued device certificate in
the following situations:
● If the eNodeB can communicate with the CA server only through the security domain,
the reconfiguration cannot be performed using the MAE-Deployment.
● When reconfiguration is performed using MML commands, the operator-issued security
certificates can be applied for only in offline mode.
● When the separate encryption mode is used and the CA server is in the non-security
domain, the local IP address of the OM channel is recommended for applying for the
operator-issued security certificates.
● The local IP address of the OM channel is recommended for updating the operator-issued
security certificates when the CA server is in the security domain and the unified encryption
mode is used or when the CA server is in the non-security domain and the separate
encryption mode is used. In this case, you do not need to add a device IP address for
updating the certificates.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 791

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-147 Procedure for changing the transmission security mechanism from
PSK to PKI (using the MAE-Deployment, IPv4)

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Figure 1-148 Procedure for changing the transmission security mechanism from
PSK to PKI (using the MAE-Deployment)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 792

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 793

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-149 Procedure for changing the transmission security mechanism from
PSK to PKI (using MML commands, IPv4)

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 794

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-150 Procedure for changing the transmission security mechanism from
PSK to PKI (using MML commands)

Topology Change
Figure 1-151 shows the topologies before and after the reconfiguration.
NOTE

If the operator-issued security certificate needs to be requested or updated, the eNodeB will
access the CA server to apply for or update the certificate.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 795

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-151 Topologies before and after the reconfiguration

1.9.5.2 Engineering Preparation

This section describes the engineering preparation for changing the security mode
from PSK to PKI, including information collection and preparation of hardware,
software, license files, security certificates, and data. It also describes the data
preparation mode and provides MML configuration script examples.

Information Collection
Table 1-264 describes the information to be collected for data preparation.

Table 1-264 Information to be collected

Information Description

Device certificate Device certificate request file. This file includes the
information common name, issuer, signature algorithm, key size,
usage, local name, and local IP address.

CA server information Includes the CA name and the CA server URL.

Information about the Includes all the next-hop IP addresses from the eNodeB
routes to the CA to the CA server.
server

Information about the Includes the next-hop IP address and VLAN ID of the
VLAN for the route VLAN.
from the eNodeB to
the CA server

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 796

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Hardware Preparation
Prepare the hardware listed in Table 1-265.

Table 1-265 Hardware to be prepared

Hardware Description

SeGW A firewall or router that complies with the secure

networking (IPsec) protocol

CA server An operator's CA server. It is used for issuing operator-

issued security certificates to eNodeBs.

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

● Operator device certificate
● Operator trust certificate
If an operator issues its root trust certificate to Huawei, this certificate can be
preconfigured on the eNodeB as the trust certificate.

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Table 1-266 Data preparation for changing the security mode from PSK to PKI

Rec SN Ope MO Configuration Reference

onfi rati
gura on
tion
Mod
e

MAE 1 Add IPv4: DEVIPa For details, see IP eRAN

- Engineering Guide Feature
Depl Parameter Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 797

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO Configuration Reference

onfi rati
gura on
tion
Mod
e

oym 2 Add IPRT/SRCIPRTb Add an IP route to the CA server.

ent For details, see IP eRAN
3 Add VLANMAP
Engineering Guide Feature
Parameter Description.
4 Add TRUSTCERT For details, see PKI Feature
Parameter Description.
5 Mod CERTREQ
ify

6 Add CA

7 Add CERTMK

8 Mod APPCERT Change the device certificate in

ify use to the operator-issued device
certificate.

9 Mod IKEPROPOSAL Change the value of

ify Authentication Method to
IKE_RSA_SIG.

MM 1 Add DEVIPa Add an IP route to the CA server.

L For details, see IP eRAN
com Engineering Guide Feature
man Parameter Description.
ds
2 Add IPRT/SRCIPRTb For details, see IP eRAN
Engineering Guide Feature
3 Add VLANMAP Parameter Description.

4 Add TRUSTCERT For details, see PKI Feature

Parameter Description.
5 Mod CERTREQ
ify

6 Add CA

7 Run CRE CERTREQFILE -

the
MM
L
com
man
d

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 798

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO Configuration Reference

onfi rati
gura on
tion
Mod
e

8 Run ULD CERTFILE You need to use the device

the certificate request file to directly
MM apply for the operator-issued
L device certificate from the
com operator. Perform the following
man operations only after you have
d obtained the operator-issued
device certificate.

9 Run DLD CERTFILE -

the
MM
L
com
man
d

10 Add CERTMK For details, see PKI Feature

Parameter Description.
11 Mod APPCERT Change the device certificate in
ify use to the operator-issued device
certificate.

12 Mod IKEPROPOSAL Change the value of

ify Authentication Method to
IKE_RSA_SIG.

a: If the eNodeB uses different device IP addresses to perform IKE negotiation,

apply for the operator-issued security certificate, and update the operator-issued
security certificate, you need to add device IP addresses, the number of which is
based on the number of IP addresses.
b: To simplify configurations when one device IP address maps multiple
destination IP addresses, you are advised to configure the source IP route.

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 799

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-267 Data preparation for changing the security mode from PSK to PKI
Rec SN Ope MO Configuration Reference
onfi rati
gura on
tion
Mod
e

MAE 1 Add IPv4: IPADDR4a For details, see IP eRAN

- Engineering Guide Feature
IPv6: IPADDR6a
Depl Parameter Description.
oym
ent 2 Add IPv4: IPROUTE4/ Add an IP route to the CA server.
SRCIPROUTE4b For details, see IP eRAN
IPv6: IPROUTE6 Engineering Guide Feature
Parameter Description.
3 Add TRUSTCERT For details, see PKI Feature
Parameter Description.
4 Mod CERTREQ
ify

5 Add CA

6 Add CERTMK

7 Mod APPCERT Change the device certificate in

ify use to the operator-issued device
certificate.

8 Mod IKEPROPOSAL Change the value of

ify Authentication Method to
IKE_RSA_SIG.

MM 1 Add IPv4: IPADDR4a For details, see IP eRAN

L Engineering Guide Feature
IPv6: IPADDR6a
com Parameter Description.
man
ds 2 Add IPv4: IPROUTE4/ Add an IP route to the CA server.
SRCIPROUTE4b For details, see IP eRAN
IPv6: IPROUTE6 Engineering Guide Feature
Parameter Description.
3 Add TRUSTCERT For details, see PKI Feature
Parameter Description.
4 Mod CERTREQ
ify

5 Add CA

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 800

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Rec SN Ope MO Configuration Reference

onfi rati
gura on
tion
Mod
e

6 Run CRE CERTREQFILE -

the
MM
L
com
man
d

7 Run ULD CERTFILE You need to use the device

the certificate request file to directly
MM apply for the operator-issued
L device certificate from the
com operator. Perform the following
man operations only after you have
d obtained the operator-issued
device certificate.

8 Run DLD CERTFILE -

the
MM
L
com
man
d

9 Add CERTMK For details, see PKI Feature

Parameter Description.
10 Mod APPCERT Change the device certificate in
ify use to the operator-issued device
certificate.

11 Mod IKEPROPOSAL Change the value of

ify Authentication Method to
IKE_RSA_SIG.

a: If the eNodeB uses different IPv4/IPv6 addresses to perform IKE negotiation,

apply for the operator-issued device certificate, and update the operator-issued
device certificate, you need to add IPv4/IPv6 addresses, the number of which is
based on the number of IP addresses.
b: To simplify configurations when one IPv4 address maps multiple destination
IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. If the eNodeB can communicate with the CA server through the non-

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 801

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

security domain, you are advised to use the batch configuration mode of the
MAE-Deployment to configure base stations in batches or to use the MAE-
Deployment GUI to configure a single base station. If the eNodeB can
communicate with the CA server only through the security domain, you can only
use MML commands. The three data preparation modes are described as follows:
NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario-specific template being "Changing the Security Mode
from PSK to PKI"): For details, see the interactive operation guide 1.11.2
Using the Batch Reconfiguration Mode of the MAE-Deployment to
Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, an IP address for applying for the operator-issued
security certificate does not need to be added and the local IP address of the OM
channel is used as the IP address for updating the certificate.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding a device IP address*/
ADD DEVIP:SN=7,SBT=BASE_BOARD,PT=ETH,PN=0,IP="192.168.53.6",MASK="255.255.255.0";
/*Adding an IP route to the CA server*/

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 802

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD IPRT:RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="10.148.25.179", DSTMASK="255.255.255.255",

RTTYPE=NEXTHOP, NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.53.110",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,
SETPRIO=DISABLE;
/*Downloading the operator's trust certificate*/
DLD CERTFILE:IP="172.21.241.98", USR="admin", PWD="*****", SRCF="operator.pem", DSTF="operator.pem";
/*It takes approximately 30s to download the operator's trust certificate. You cannot perform the
subsequent operations before the download is completed.*/
/*Save the following MML commands as another script file. Run these commands only after the value of
Status changes to Succeeded in the execution result of the DLD CERTFILE command (indicating that the
operator's trust certificate is downloaded successfully.)*/
/*Adding the operator's trust certificate*/
ADD TRUSTCERT:CERTNAME="operator.pem";
/*Modifying the registration information used to create the certificate request*/
MOD CERTREQ: COMMNAME=ESN, COUNTRY="CN", ORG="huawei", ORGUNIT="huawei",
STATEPROVINCENAME="guangdong", LOCALITY="shenzhen",
KEYUSAGE=DATA_ENCIPHERMENT-1&DIGITAL_SIGNATURE-1&KEY_AGREEMENT-1&KEY_ENCIPHERMENT-1,
SIGNALG=SHA256, KEYSIZE=KEYSIZE2048, LOCALNAME="s-segw", LOCALIP="192.168.53.6";
/*Adding a certificate authority*/
ADD CA:CANAME="C = CN,S = guangdong,O = huawei,CN = aksz", URL="http://10.148.25.179:8080";
/*Generating a device certificate request file*/
CRE CERTREQFILE:FILENAME="cert.req",REQMODE=NEW;
/*Uploading the device certificate request file*/
ULD CERTFILE:IP="172.21.241.193", USR="admin", PWD="*****", SRCF="cert.req", DSTF="cert.req";
/*You need to use the device certificate request file to directly apply for the operator-issued device
certificate from the operator. So, save the following MML commands as another script file and perform the
following operations only after you have obtained the operator-issued device certificate.*/
/*Downloading the operator-issued device certificate*/
DLD CERTFILE:IP="172.21.241.193",USR="admin",PWD="*****",SRCF="opkidev.pem",DSTF="opkidev.pem";
/*It takes approximately 30s to download the operator-issued device certificate. You cannot perform the
subsequent operations before the download is completed.*/
/*Save the following MML commands as another script file. Run these commands only after the value of
Status changes to Succeeded in the execution result of the DLD CERTFILE command (indicating that the
operator-issued device certificate is downloaded successfully.)*/
/*Loading the operator-issued device certificate*/
ADD CERTMK:APPCERT="opkidev.pem";
/*Changing the device certificate in use to the operator-issued device certificate*/
MOD APPCERT:APPTYPE=IKE, APPCERT="opkidev.pem";
/*Changing the authentication method for the IKE proposal*/
MOD IKEPROPOSAL: PROPID=1, AUTHMETH=IKE_RSA_SIG;

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Adding an IPv4 address*/
SET ETHPORT:CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=1;
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=1, TAGGED=ENABLE, VLANID=101, VRFIDX=0;
ADD IPADDR4:ITFID=0, IP="192.168.53.6", MASK="255.255.255.0";
/*Adding an IPv4 route to the CA server*/
ADD IPROUTE4:RTIDX=0, DSTIP="10.148.25.179", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Downloading the operator's trust certificate*/
DLD CERTFILE:IP="172.21.241.98", USR="admin", PWD="*****", SRCF="operator.pem", DSTF="operator.pem";
/*It takes approximately 30s to download the operator's trust certificate. You cannot perform the
subsequent operations before the download is completed.*/
/*Save the following MML commands as another script file. Run these commands only after the value of
Status changes to Succeeded in the execution result of the DLD CERTFILE command (indicating that the
operator's trust certificate is downloaded successfully.)*/
/*Adding the operator's trust certificate*/
ADD TRUSTCERT:CERTNAME="operator.pem";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 803

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Modifying the registration information used to create the certificate request*/

MOD CERTREQ: COMMNAME=ESN, COUNTRY="CN", ORG="huawei", ORGUNIT="huawei",
STATEPROVINCENAME="guangdong", LOCALITY="shenzhen",
KEYUSAGE=DATA_ENCIPHERMENT-1&DIGITAL_SIGNATURE-1&KEY_AGREEMENT-1&KEY_ENCIPHERMENT-1,
SIGNALG=SHA256, KEYSIZE=KEYSIZE2048, LOCALNAME="s-segw", LOCALIP="192.168.53.6";
/*Adding a certificate authority*/
ADD CA:CANAME="C = CN,S = guangdong,O = huawei,CN = aksz", URL="http://10.148.25.179:8080";
/*Generating a device certificate request file*/
CRE CERTREQFILE:FILENAME="cert.req",REQMODE=NEW;
/*Uploading the device certificate request file*/
ULD CERTFILE:IP="172.21.241.193", USR="admin", PWD="*****", SRCF="cert.req", DSTF="cert.req";
/*You need to use the device certificate request file to directly apply for the operator-issued device
certificate from the operator. So, save the following MML commands as another script file and perform the
following operations only after you have obtained the operator-issued device certificate.*/
/*Downloading the operator-issued device certificate*/
DLD CERTFILE:IP="172.21.241.193",USR="admin",PWD="*****",SRCF="opkidev.pem",DSTF="opkidev.pem";
/*It takes approximately 30s to download the operator-issued device certificate. You cannot perform the
subsequent operations before the download is completed.*/
/*Save the following MML commands as another script file. Run these commands only after the value of
Status changes to Succeeded in the execution result of the DLD CERTFILE command (indicating that the
operator-issued device certificate is downloaded successfully.)*/
/*Loading the operator-issued device certificate*/
ADD CERTMK:APPCERT="opkidev.pem";
/*Changing the device certificate in use to the operator-issued device certificate*/
MOD APPCERT:APPTYPE=IKE, APPCERT="opkidev.pem";
/*Changing the authentication method for the IKE proposal*/
MOD IKEPROPOSAL: PROPID=1, AUTHMETH=IKE_RSA_SIG;

1.9.5.3 Engineering Implementation

This section describes the engineering implementation for changing the
transmission security mechanism from PSK to PKI, including prerequisites, context,
and procedure.

Prerequisites
The information, hardware, security certificates, and data for changing the
transmission security mechanism from PSK to PKI are ready. The license file is
available in the save path on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.
– Local Operations
N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 804

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Remote Operations
Use the MAE-Deployment to deliver the data to the base station and
then activate the data.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the following commands on the MAE-Access to back up and
export the configuration file. The configuration file can be used to
restore the base station to the pre-reconfiguration status if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.
2) To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iv. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
v. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
vi. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Using MML commands:
– Local Operations
Run MML commands on the LMT to deliver the data to the base station
and then activate the data.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the following commands on the LMT to back up and export the
configuration file. The configuration file can be used to restore the
base station if the reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 805

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

2) To export the configuration file, run the ULD CFGFILE command.

Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Use the LMT to deliver the batch configuration script prepared
according to Engineering Preparation > Data Preparation to the
base station and activate the script on the base station. For details,
see 1.3.2 Running MML Commands on the LMT.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Remote Operations
N/A
----End

1.9.5.4 Engineering Verification

This section describes how to verify the changing of the transmission security
mechanism from PSK to PKI.

Procedure
Step 1 Run the DSP APPCERT command to check whether the device certificate in use is
the operator-issued device certificate.
If it is not the operator-issued device certificate, run the DSP CERTMK command
to check whether the operator-issued device certificate is available.
● If it is available, run the MOD APPCERT command to replace the device
certificate in use with the operator-issued device certificate.
● If it is unavailable, run the REQ DEVCERT command to apply for an operator-
issued device certificate. Then run the command to replace the device
certificate in use with the operator-issued device certificate.
Step 2 Run the DSP TRUSTCERT command to check whether the operator's trust
certificate is included in the command output and Status is Normal.
If the operator's trust certificate is not included in the command output or Status
is not Normal, run the LST TRUSTCERT command to check whether the
operator's trust certificate is configured.
● If it is configured, run the RMV TRUSTCERT command to delete the
configuration. Run the DLD CERTFILE command to download an operator's
trust certificate again. Then, run the ADD TRUSTCERT command to add the
operator's trust certificate.
● If it is not configured, run the DLD CERTFILE command to download an
operator's trust certificate. Then, run the ADD TRUSTCERT command to add
the operator's trust certificate.
Step 3 Run the LST CA command to check whether the current certificate authority is
correctly configured. That is, Certificate Authority Name and Certificate
Authority URL are the same as the real name of the certificate authority and the
real URL of the CA server, respectively.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 806

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If the configurations are incorrect, perform the following steps to modify the
certificate authority configurations:

1. Run the RMV CA command to remove the original certificate authority.

2. Run the ADD CA command to add a correct certificate authority.

----End

1.9.5.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Remote rollback
If the OM channel is interrupted due to reconfiguration failures and secure
PnP can be performed for the bearer network, the OM channel can be
automatically set up in a secure manner. Perform the following steps to check
whether the bearer network meets the following secure PnP conditions:
a. Check whether the configurations of the bearer network devices such as
the public DHCP server, router, and SeGW meet secure PnP requirements.
For details about secure PnP requirements for bearer network devices, see
the corresponding configuration requirements in Automatic OMCH
Establishment Feature Parameter Description.
b. Check whether the DHCP configuration and route configuration of the
MAE exist and are consistent with the configurations of the current
bearer network.
If the configurations do not exist or are inconsistent with the current
bearer network, reconfigure the DHCP and route of the MAE to ensure
that they are consistent with the configurations of the current bearer
network.
For details about requirements and preparations for MAE DHCP and
route configurations, see the corresponding configuration requirements in
Automatic OMCH Establishment Feature Parameter Description. For
details about how to configure DHCP for the MAE, see Managing the
DHCP Information about Base Stations and Starting/Stopping VLAN
Detecting in the MAE-Access online help. For details about how to
configure the MAE route, see Setting the Routes of the MAE Server in
MAE Administrator Guide.
After the OM channel resumes, perform the following operations to remotely
roll back the configuration data:
a. On the MAE-Access, run DLD CFGFILE to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run ACT CFGFILE to activate the original configuration file.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 807

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: ACT CFGFILE: EFT=IMMEDIATELY;

● Local rollback
If the OM channel is interrupted but the bearer network does not meet secure
PnP requirements, the configuration data can only be rolled back locally using
the LMT.
a. On the LMT, run DLD CFGFILE to download the original configuration
file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run ACT CFGFILE to activate the original configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Roll back the configuration data using the one-click blind configuration
rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the transport network.
Step 4 Verify that engineering rollback is successful according to instructions in 1.9.5.4
Engineering Verification.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 808

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.9.6 Changing a Single IPsec Tunnel to an IPsec Tunnel Pair

(Only for IPv4 Transmission)
This section describes how to change a single IPsec tunnel to an IPsec tunnel pair
when an IPsec policy group and an IKE entity exist.

Prerequisites
A security gateway (SeGW) has been added. The IPsec and public key
infrastructure (PKI) parameters have been configured for the new SeGW, and the
eNodeB service and OMCH are normal.

1.9.6.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing a single IPsec tunnel
to an IPsec tunnel pair.

Application Scenario
The operator requires the use of an IPsec tunnel pair to enhance transmission
network security.

Reconfiguration Impact
No impact

Reconfiguration Scheme
Figure 1-152 shows the reconfiguration procedure for changing a single IPsec
tunnel to an IPsec tunnel pair. Determine the reconfiguration scheme according to
the following table.

Table 1-268 Scheme options

If... Then...

The local IP address of the Change the local IP address of the original IKE
original IKE peer is 0.0.0.0 peer to the actual device IP address.

Each of the IPsec tunnel pair Bind the added IPsec tunnel to IPsec security
uses one port policy group.

The IPsec tunnel pair uses only Do not bind the added IPsec tunnel to IPsec
one port security policy group.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 809

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-152 Procedure for changing a single IPsec tunnel to an IPsec tunnel pair

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 810

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-153 Procedure for changing a single IPsec tunnel to an IPsec tunnel pair

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 811

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Figure 1-154 shows the topologies before and after the reconfiguration.

Figure 1-154 Topologies before and after the reconfiguration

1.9.6.2 Engineering Preparation

This section describes the engineering preparation for changing a single IPsec
tunnel to an IPsec tunnel pair, including information collection and preparation of
hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-269 describes the information to be collected for data preparation.

Table 1-269 Information to be collected

Information Description

IPsec policy group Includes the IKE proposal name, IPsec proposal name,
information access control list (ACL) ID, and IPsec SA life cycle.

Local IKE information Includes the local IKE name, pre-shared key, IKE
version, and negotiation mode.

Information about the Includes the IP address and subnet mask of the new
routes from the SeGW and the next-hop IP address of the routes.
eNodeB to the new
SeGW

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 812

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Information about the Includes the next-hop IP address and VLAN ID of the
VLAN for the route VLAN.
from the eNodeB to
the new SeGW

Hardware Preparation
Prepare the hardware listed in Table 1-270.

Table 1-270 Hardware to be prepared

Hardware Description

SeGW Supports the firewall or router that complies with the

IPsec protocol.

Software Preparation
N/A

License File Preparation

If the license file is to be updated, a new license file is required.

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 813

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-271 Data preparation for changing a single IPsec tunnel to an IPsec
tunnel pair

SN Ope MO Configuration Reference

ratio
n

1 Modi IKEPEER Change the local IP address of the

fy original IKE peer to the actual device IP
address.

2 Add IKEPEER For details, see IPsec Feature Parameter

Description.
3 Add IPSECPOLICY

4 Add IPSECBIND

5 Add IPRT/SRCIPRTa For details, see IP eRAN Engineering

Guide Feature Parameter Description.
6 Add VLANMAP

7 Add IPSECDTNL Add an IPsec tunnel pair.

For details, see IPsec Feature Parameter
Description.
a: To simplify configurations when one device IP address maps multiple
destination IP addresses, you are advised to configure the source IP route.

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Table 1-272 Data preparation for changing a single IPsec tunnel to an IPsec
tunnel pair

SN Ope MO Configuration Reference

ratio
n

1 Modi IKEPEER Change the local IP address of the

fy original IKE peer to the actual device IP
address.

2 Add INTERFACE For details, see IP eRAN Engineering

Guide Feature Parameter Description.
3 Add IKEPEER For details, see IPsec Feature Parameter
Description.
4 Add IPSECPOLICY

5 Add IPSECBIND

6 Add IPROUTE4/ For details, see IP eRAN Engineering

SRCIPROUTE4a Guide Feature Parameter Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 814

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

7 Add IPSECDTNL Add an IPsec tunnel pair.

For details, see IPsec Feature Parameter
Description.
a: To simplify configurations when one IPv4 address maps multiple destination
IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

In this scenario, the configuration by running MML commands is recommended.
Prepare MML configuration scripts based on the preceding data preparation
procedure and the following example of MML configuration scripts.

MML Configuration Script Example

In the following example, each of the two IPsec tunnels is set up on one port, and
the PSK authentication mode is used.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.

NOTE

If the license file needs to be updated, the active license file must be backed up and a new
license file must be imported into the base station. If the license file does not need to be
updated, the backup and import operations are not required.

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Modifying the original IKE peer*/
MOD IKEPEER:PEERNAME="ikepeer1", LOCALIP="192.168.53.13";
/*Adding an IP address*/
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.54.14", MASK="255.255.255.0";
/*Adding an IKE peer*/
ADD IKEPEER: PEERNAME="ikepeer2", PROPID=2, IKEVERSION=IKE_V2, EXCHMODE=AGGRESSIVE,
IPVERSION=IPV4, IDTYPE=FQDN, REMOTEIP="192.168.54.8", REMOTENAME="segw", DPD=PERIODIC,
LOCALIP="192.168.54.14";
/*Adding an IPsec policy*/
ADD IPSECPOLICY: SPGN="ipsecpol2", SPSN=1, ACLTYPE=IPV4, ACLID=3007, PROPNAME="ipsecprop",

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 815

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

PEERNAME="ikepeer2", LTCFG=LOCAL;
/*Binding an IPsec policy group to a port*/
ADD IPSECBIND:SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, SPGN="ipsecpol2";
/*Adding an IP route from the eNodeB to the new SeGW*/
ADD IPRT: RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="192.168.54.8", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.54.110", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.54.110",MASK="255.255.255.0",VLANMODE=SINGLEVLAN,VLANID=101,SET
PRIO=DISABLE;
/*Adding an IPsec tunnel pair*/
ADD IPSECDTNL: DUALID=1, MSPGN="ipsecpol1", MSPSN=1, SSPGN="ipsecpol2", SSPSN=1,
BFDDTCTSW=OFF, IPSECSWITCHBACK=OFF;

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE:MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE:DIR="ftproot/", FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Modifying the original IKE peer*/
MOD IKEPEER:PEERNAME="ikepeer1", LOCALIP="192.168.53.13";
/*Adding an interface*/
ADD INTERFACE:ITFID=1, ITFTYPE=VLAN, PT=ETH, PORTID=1, TAGGED=ENABLE, VLANID=101, VRFIDX=0;
ADD IPADDR4: ITFID=1, IP="192.168.54.14", MASK="255.255.255.0";
/*Adding an IKE peer*/
ADD IKEPEER: PEERNAME="ikepeer2", PROPID=2, IKEVERSION=IKE_V2,
EXCHMODE=AGGRESSIVE,IPVERSION=IPV4, IDTYPE=FQDN, REMOTEIP="192.168.54.8",
REMOTENAME="segw", DPD=PERIODIC, LOCALIP="192.168.54.14";
/*Adding an IPsec policy*/
ADD IPSECPOLICY:SPGN="ipsecpol2", SPSN=1, ACLTYPE=IPV4, ACLID=3007, PROPNAME="ipsecprop",
PEERNAME="ikepeer2", LTCFG=LOCAL;
/*Binding an IPsec policy group to an interface*/
ADD IPSECBINDITF:IPSECBINDITFID=2, SPGN="ipsecpol2", ITFID=1;
/*Adding an IP route from the eNodeB to the new SeGW*/
ADD IPROUTE4: RTIDX=1, DSTIP="192.168.54.8", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.54.110", MTUSWITCH=OFF, PREF=100;
/*Adding an IPsec tunnel pair*/
ADD IPSECDTNL: DUALID=1, MSPGN="ipsecpol1", MSPSN=1, SSPGN="ipsecpol2", SSPSN=1,
BFDDTCTSW=OFF, IPSECSWITCHBACK=OFF;

1.9.6.3 Engineering Implementation

This section describes the engineering implementation for changing the tunnel
mode from a single IPsec tunnel to an IPsec tunnel pair, including prerequisites,
context, and procedure.

Prerequisites
The information, hardware, and data for changing the tunnel mode from a single
IPsec tunnel to an IPsec tunnel pair are ready. The license file is available in the
save path on the FTP server.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 816

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Remote Operations describe the operations that must be performed on the

operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Deploy a new SeGW, connect it to the EPC and MAE.
b. Connect another port (which does not carry the original IPsec tunnel) to
the new SeGW.
● Remote Operations

The "MML command" mode on the MAE-Access is recommended for remote

operation. The following describes only this mode.

a. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Run the following commands on the MAE-Access to back up and export
the configuration file. The configuration file can be used to restore the
base station to the pre-reconfiguration status if the reconfiguration fails.
i. To back up the configuration file, run the BKP CFGFILE command.
ii. To export the configuration file, run the ULD CFGFILE command.
Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
c. Use the MAE-Access to deliver the batch configuration scripts prepared in
Engineering Preparation > Data Preparation to the base station and
activate the scripts on the base station. For details, see 1.3.3 Running
MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
d. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.9.6.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the tunnel
mode from a single IPsec tunnel to an IPsec tunnel pair.

Context
The link that carries the active or standby tunnel is functional.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 817

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

Both the active and standby IPsec tunnels must be verified during the engineering
verification. The procedures for verifying the active and standby tunnels are the same. You
must verify the active tunnel and then the standby tunnel according to the instructions
provided in Procedure.

Procedure
Step 1 Verify that ALM-29240 Cell Unavailable or ALM-25901 Remote Maintenance
Link Failure is not reported.
If ALM-29240 Cell Unavailable or ALM-25901 Remote Maintenance Link
Failure is reported, clear the alarm according to the instructions in 3900 & 5900
Series Base Station Alarm Reference.
Step 2 Run the DSP IPSECDTNL command to check whether Current Used IPSec Policy
is Master IPSec Policy/Slave IPSec Policy.
If the parameter value is not Master IPSec Policy or Slave IPSec Policy, perform
the following operations:
1. Run the DSP ETHPORT command to check whether Port Status of the
Ethernet port bearing the physical link of the active channel is Up. If yes,
proceed to Step 2.2. If no, the attributes of the Ethernet port may be
incorrect. In this case, run the SET ETHPORT command to modify the Port
Attribute parameter value. If the problem persists after the port attributes
are modified, proceed to Step 2.2.
2. Run the LST IPRT command to check whether the route configuration of the
active tunnel is correct. If it is correct, contact Huawei technical support or
dial the Huawei technical support hotline. If it is incorrect, run the RMV IPRT
command to delete the incorrect route. Then run the ADD IPRT command to
add the correct route of the active tunnel. If the problem persists after the
route is modified, contact Huawei technical support or dial the Huawei
technical support hotline.

----End

1.9.6.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● On the MAE-Access, download and activate the original configuration file.
a. Run the DLD CFGFILE command to download the configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run the ACT CFGFILE command to activate the configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 818

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Roll back the configuration data using the one-click blind configuration
rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful according to instructions in 1.9.6.4

Engineering Verification.

----End

1.9.7 Changing a Single Virtual Route to Active/Standby Static

IP Route
This section describes how to change a single virtual route to active/standby static
IP route.

Prerequisites
The standby route has been deployed, and related data has been configured.

1.9.7.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing a single virtual route
to active/standby static routes.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 819

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Application Scenario
When the transport network does not adopt Virtual Router Redundancy Protocol
(VRRP), a single virtual route needs to be changed to active/standby static routes
for the eNodeB to ensure transmission reliability.

Reconfiguration Impact
No impact

Reconfiguration Scheme
Figure 1-155 shows the reconfiguration procedure for changing a single virtual
route to active/standby static routes.
NOTE

The two new routes must have higher priorities than the old route toward the original VRRP
virtual address. Of the two new routes, the active route must have a higher priority than the
standby route.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Figure 1-155 Procedure for changing a single virtual route to active/standby static
routes (IPv4)

New Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 820

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-156 Procedure for changing a single virtual route to active/standby static
routes (IPv4)

Figure 1-157 Procedure for changing a single virtual route to active/standby static
routes (IPv6)

Topology Change
Figure 1-158 shows the topology changes related to the reconfiguration by using
the modification of the route to the MME as an example.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 821

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-158 Topologies before and after the reconfiguration

1.9.7.2 Engineering Preparation

This section describes the engineering preparation for changing a single virtual
route to active/standby static routes, including information collection and
preparation of hardware, software, license files, security certificates, and data. It
also describes the data preparation mode and provides MML configuration script
examples.

Information Collection
Table 1-273 describes the information to be collected for data preparation.

Table 1-273 Information to be collected

Information Description

Information about Includes the next-hop IP address and subnet mask

the new active route (IPv4)/prefix length (IPv6) of the active route.

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
new active route

Information about Includes the next-hop IP address and subnet mask of

the new standby the standby route.
route

Information about Includes the next-hop IP address and VLAN ID of the

the VLAN for the VLAN.
new standby route

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 822

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Information about Includes the next-hop IP address and subnet mask of

the old route toward the old route.
the original VRRP
virtual address

BFD session Includes the BFD session IDs and DSCP values of the
information (old active and standby routes.
model)/Bidirectional
Forwarding Detection
information (new
model)

Hardware Preparation
Prepare the hardware listed in Table 1-274.

Table 1-274 Hardware to be prepared

Hardware Description

Cables used to connect the eNodeB The cables can be Ethernet cables or
and a router optical fibers, depending on the peer
router.

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Old Model

The Transmission Configuration Mode parameter in the GTRANSPARA MO is set

to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 823

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-275 Data preparation for changing a single virtual route to active/standby
static routes
SN Ope MO Configuration Reference
ratio
n

1 Add IPRT Add active and standby IP routes. The

two routes have higher priorities than
2 Add (Optional) VLANMAP the old route toward the original VRRP
virtual address. The active route has a
higher priority than the standby route.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
3 Add BFDSESSION Add two BFD sessions for the new active
and standby routes.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
4 Dele IPRT Delete the old IP route toward the
te original VRRP virtual address.

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Table 1-276 Data preparation for changing a single virtual route to active/standby
static routes
SN Ope MO Configuration Reference
ratio
n

1 Add IPv4: IPROUTE4 Add active and standby IP routes. The

IPv6: IPROUTE6 two routes have higher priorities than
the old route toward the original VRRP
2 Add IPv4: VLANMAP or virtual address. The active route has a
INTERFACE in which higher priority than the standby route.
Interface Type is For details, see IP eRAN Engineering
VLAN Guide Feature Parameter Description.
IPv6: INTERFACE

3 Add BFD Add two BFD sessions for the new active
and standby routes.
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
4 Dele IPv4: IPROUTE4 Delete the old IP route toward the
te IPv6: IPROUTE6 original VRRP virtual address.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 824

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario-specific template being "Changing a Single Virtual
Route to Active/Standby Static IP Route"). For details, see the interactive
operation guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, the priority of the old route toward the original VRRP
virtual address is 60.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
/*Adding a new active route that has a higher priority than the old route toward the original VRRP virtual
address*/
ADD IPRT:RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="10.148.36.103", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.81.54.7", MTUSWITCH=OFF, PREF=20;
/*Adding a new standby route that has a higher priority than the old route toward the original VRRP virtual
address but a lower priority than the new active route*/
ADD IPRT:RTIDX=1, SN=7, SBT=BASE_BOARD, DSTIP="10.148.36.103", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.81.53.7", MTUSWITCH=OFF, PREF=30;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group for the new
active route*/
ADD
VLANMAP:NEXTHOPIP="192.81.54.7",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SET
PRIO=DISABLE;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group for the new

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 825

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

standby route*/
ADD
VLANMAP:NEXTHOPIP="192.81.53.7",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=102,SET
PRIO=DISABLE;
/*Adding a BFD session for the active route*/
ADD BFDSESSION:SN=7, BFDSN=0, SRCIP="192.81.54.6", DSTIP="192.81.54.7", HT=SINGLE_HOP, DSCP=63;
/*Adding a BFD session for the standby route*/
ADD BFDSESSION:SN=7, BFDSN=1, SRCIP="192.81.53.6", DSTIP="192.81.53.7", HT=SINGLE_HOP, DSCP=63;
/*Removing the old route toward the original VRRP virtual address with the Route Index of 3*/
RMV IPRT:RTIDX=3;

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.
/*Adding a new active route that has a higher priority than the old route toward the original VRRP virtual
address*/
ADD IPROUTE4:RTIDX=0, DSTIP="10.148.36.103", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.81.54.7", MTUSWITCH=OFF, PREF=20;
/*Adding a new standby route that has a higher priority than the old route toward the original VRRP virtual
address but a lower priority than the new active route*/
ADD IPROUTE4:RTIDX=1, DSTIP="10.148.36.103", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.81.53.7", MTUSWITCH=OFF, PREF=30;
/*Setting an Ethernet port*/
SET ETHPORT:CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=0, PORTID=0;
/*Adding an interface (the VLANMAP MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=NORMAL, PT=ETH, PORTID=0, VRFIDX=0;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group for the new
active route*/
ADD
VLANMAP:NEXTHOPIP="192.81.54.7",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,SET
PRIO=DISABLE;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group for the new
standby route*/
ADD
VLANMAP:NEXTHOPIP="192.81.53.7",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=102,SET
PRIO=DISABLE;
/*Adding interfaces (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=0, VLANID=101, VRFIDX=0;
ADD INTERFACE:ITFID=1, ITFTYPE=VLAN, PT=ETH, PORTID=0, VLANID=102, VRFIDX=0;
/*Adding a BFD for the active route*/
ADD BFD:SN=7, BFDSN=0, SRCIP="192.81.54.6", DSTIP="192.81.54.7", HT=SINGLE_HOP, DSCP=63;
/*Adding a BFD for the standby route*/
ADD BFD:BFDSN=1, SRCIP="192.81.53.6", DSTIP="192.81.53.7", MYDISCREAMINATOR =1, HT=SINGLE_HOP,
DSCP=63;
/*Removing the old route toward the original VRRP virtual address with the Route Index of 3*/
RMV IPROUTE4:RTIDX=3;

1.9.7.3 Engineering Implementation

This section describes the engineering implementation for changing a single
virtual route to active/standby static routes, including prerequisites, context, and
procedure.

Prerequisites
Information and configuration data for changing a single virtual route to active/
standby static routes are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 826

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Remote Operations describe the operations that must be performed on the

operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

Connect the eNodeB to a router.

● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
iii. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 827

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.9.7.4 Engineering Verification

This section describes how to verify the change from a single virtual route to
active/standby static routes.

Procedure
Step 1 Disable the active route (for example, by running RMV IPRT (old model) / RMV
IPROUTE4 (new model) to remove the active route), and check whether the
standby route is automatically enabled.
Run DSP IPRT (old model) / DSP IPROUTE4 (new model) to check whether the
standby route is in use and the active route is not.
If the standby route does not take effect, check whether its configurations are
correct:
● If they are not correct, modify the configurations of the standby route.
● If they are correct, contact Huawei technical support or dial the Huawei
technical support hotline.
Step 2 Verify that the services carried on the standby route are normal.
If the services are abnormal, for example, a remote maintenance link, S1 link, X2
link, or clock link is abnormal, check whether the following alarms are reported:
ALM-25901 Remote Maintenance Link Failure, ALM-29201 S1 Interface Fault,
ALM-29204 X2 Interface Fault, and ALM-26262 External Clock Reference
Problem.
● If any of the preceding alarms is reported, clear the alarm according to the
instructions in 3900 & 5900 Series Base Station Alarm Reference.
● If no alarm is reported, contact Huawei technical support or dial the Huawei
technical support hotline.

NOTICE

After the verification, restore the active route. For example, if you have removed
the active route, run ADD IPRT (old model) / DSP IPROUTE4 (new model) to add
the active route after the verification.

----End

1.9.7.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 828

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands:

– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Restore the physical connections.

Step 3 Verify that engineering rollback is successful according to instructions in 1.9.7.4

Engineering Verification.

----End

1.9.8 Replacing an SeGW

This section describes how to replace a security gateway (SeGW).

Prerequisites
● An IP address has been configured for the new SeGW, and the routes to the
eNodeB, MAE-Access, and core network have been configured.
● An IKE and IPsec have been configured for the new SeGW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 829

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● The trust certificate and device certificate of the operator have been loaded
on the new SeGW if the PKI security mode is used.
● The routes to the eNodeB have been modified on the MAE-Access and core
network if the next hops from the MAE-Access and core network to the
eNodeB have changed.

1.9.8.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for replacing an SeGW.

Application Scenario
The networking of an operator is adjusted and an eNodeB needs to be connected
to a new SeGW.

Reconfiguration Impact
The transport links protected by the old SeGW will be broken, and services carried
on the links will be interrupted.

Reconfiguration Scheme
Figure 1-159 shows the reconfiguration procedure for replacing an SeGW.
Determine the reconfiguration scheme according to the following table.

Table 1-277 Scheme options

If… Then...

No route is available between the Add a route from the eNodeB to the
eNodeB and the new SeGW new SeGW and the corresponding
VLANMAP MO.

An IKE peer name has been configured Change the IKE peer name to the
on the eNodeB, the local SeGW ID type is FQDN of the new SeGW.
a fully qualified domain name (FQDN),
and the FQDN of the new SeGW is
different from that of the old SeGW

The value of the Destination IP for the Remove the route from the eNodeB
route from the eNodeB to the old SeGW to the old SeGW.
is the IP address of the old SeGW but not
the IP address of the network segment
where the old SeGW is located

NOTE

Removing the route from the eNodeB to the old SeGW prevents redundant data. However, if the
Destination IP value configured for the route from the eNodeB to the old SeGW is the IP
address of the network segment where the old SeGW is located, do not remove this route
because the eNodeB may use this IP address to communicate with other devices on the network
segment.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 830

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Figure 1-159 Procedure for replacing an SeGW (IPv4)

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 831

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-160 Procedure for replacing an SeGW (IPv4)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 832

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-161 Procedure for replacing an SeGW (IPv6)

Topology Change
N/A

1.9.8.2 Engineering Preparation

This section describes the engineering preparation for replacing an SeGW,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-278 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 833

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-278 Information to be collected

Information Description

IP address of the new Includes the IP address and subnet mask (IPv4)/prefix
SeGW length (IPv6).

Local ID type of the The following two types are available:

new SeGW ● Fully qualified domain name (FQDN). If the local ID
type is an FQDN, obtain also the local FQDN of the
new SeGW.
● IP. If the local ID type is IP, obtain the IP address of
the new SeGW.

Information about the Required for configuring the route from the eNodeB to
next hop from the the new SeGW.
eNodeB to the new
SeGW

Hardware Preparation
Before reconfiguration, prepare the hardware listed in Table 1-279.

Table 1-279 Hardware to be prepared

Hardware Description

SeGW Supports the firewall or router that complies

with the IPsec protocol.

Software Preparation
N/A

License Preparation
N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 834

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-280 Data preparation for replacing an SeGW

SN Ope MO Configuration Reference
ratio
n

1 Add IPRT/SRCIPRTa Add an IP route from the eNodeB to the

new SeGW.
2 Add IPv4: VLANMAP
For details, see IP eRAN Engineering
Guide Feature Parameter Description.
3 Modi IKEPEER ● Change Remote IP Address to the IP
fy address of the new SeGW.
● If the peer IKE name has been
configured on the eNodeB, the local
SeGW ID type is an FQDN, and the
FQDN of the new SeGW is different
from that of the old SeGW, you also
need to change Remote Name to
the FQDN of the new SeGW.

4 Dele IPRT/SRCIPRTa Remove the route from the eNodeB to

te the old SeGW.

a: To simplify configurations when one device IP address maps multiple

destination IP addresses, you are advised to configure the source IP route.

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.
The following table describes the data preparation for replacing an SeGW when
the IPSec Bind Mode parameter in the IKECFG MO is set to SINGLE(Single).

Table 1-281 Data preparation for replacing an SeGW

SN Ope MO Configuration Reference
ratio
n

1 Modi (Optional) INTERFACE Add an IP route from the eNodeB to the

fy new SeGW.

2 Add IPv4: VLANMAP For details, see IP eRAN Engineering

Guide Feature Parameter Description.
IPv6: N/A

3 Add IPv4: (optional)

IPADDR4
IPv6: (optional)
IPADDR6

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 835

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Ope MO Configuration Reference

ratio
n

4 Add IPv4: IPROUTE4/

SRCIPROUTE4a
IPv6: IPROUTE6

5 Modi IKEPEER ● Change Remote IP Address to the IP

fy address of the new SeGW.
● If the peer IKE name has been
configured on the eNodeB, the local
SeGW ID type is an FQDN, and the
FQDN of the new SeGW is different
from that of the old SeGW, you also
need to change Remote Name to
the FQDN of the new SeGW.

6 Modi (Optional) Change the interface to which an IPsec

fy IPSECBINDITF policy group is bound by binding the
IPsec policy group to a new VLAN
interface.

7 Dele IPv4: IPROUTE4/ Remove the route from the eNodeB to

te SRCIPROUTE4a the old SeGW.
IPv6: IPROUTE6

a: To simplify configurations when one IPv4 address maps multiple destination

IP addresses, you are advised to configure the source IPv4 route.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Replacing an SeGW"): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 836

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands: Prepare MML configuration scripts based on the

preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, the eNodeB and new SeGW are not on the same
network segment, the IKE peer name needs to be modified, and the route from
the eNodeB to the old SeGW needs to be removed.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
Old Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to OLD.
/*Adding an IP route from the eNodeB to the new SeGW*/
ADD IPRT:RTIDX=1, SN=7, SBT=BASE_BOARD, DSTIP="192.168.52.7", DSTMASK="255.255.255.255",
RTTYPE=NEXTHOP, NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.53.110",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID=101,
SETPRIO=DISABLE;
/*Changing the remote IP address and remote name of the IKE peer*/
MOD IKEPEER:PEERNAME="enb", REMOTEIP="192.168.52.7", REMOTENAME="newsegw";
/*Removing the IP route from the eNodeB to the old SeGW with the Route Index of 0*/
RMV IPRT:RTIDX=0;

New Model
The Transmission Configuration Mode parameter in the GTRANSPARA MO is set
to NEW.
● In the following example, the IPSec Bind Mode parameter in the IKECFG MO
is set to SINGLE(Single), and VLAN mapping is used.
/*Adding an IP route from the eNodeB to the new SeGW*/
ADD IPROUTE4:RTIDX=1, DSTIP="192.168.52.7", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Adding an entry of mapping from a next-hop IP address to a single VLAN or VLAN group*/
ADD
VLANMAP:NEXTHOPIP="192.168.53.110",MASK="255.255.255.255",VLANMODE=SINGLEVLAN,VLANID
=101,SETPRIO=DISABLE;
/*Changing the remote IP address and remote name of the IKE peer*/
MOD IKEPEER:PEERNAME="enb", REMOTEIP="192.168.52.7", REMOTENAME="newsegw";
/*Removing the IP route from the eNodeB to the old SeGW with the Route Index of 0*/
RMV IPROUTE4:RTIDX=0;
● In the following example, the IPSec Bind Mode parameter in the IKECFG MO
is set to SINGLE(Single), and a VLAN sub-interface is used.
/*Adding an interface (the INTERFACE MO is used to configure a VLAN)*/
ADD INTERFACE:ITFID=1, ITFTYPE=VLAN, PT=ETH, PORTID=1, VLANID=101, VRFIDX=0;
ADD IPADDR4:ITFID=1, IP="192.168.53.6", MASK="255.255.255.0";
/*Adding an IP route from the eNodeB to the new SeGW*/
ADD IPROUTE4:RTIDX=1, DSTIP="192.168.52.7", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP,
NEXTHOP="192.168.53.110", MTUSWITCH=OFF;
/*Changing the remote IP address and remote name of the IKE peer*/
MOD IKEPEER:PEERNAME="enb", REMOTEIP="192.168.52.7", REMOTENAME="newsegw";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 837

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Changing the interface to which an IPsec policy group is bound*/

MOD IPSECBINDITF:IPSECBINDITFID=0, ITFID=1;
/*Removing the IP route from the eNodeB to the old SeGW with the Route Index of 0*/
RMV IPROUTE4:RTIDX=0;

1.9.8.3 Engineering Implementation

This section describes the engineering implementation for replacing an SeGW,
including prerequisites, context, and procedure.

Prerequisites
The information, hardware, and data for replacing an SeGW are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. Connect the eNodeB to the new SeGW.
● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
iii. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Run the following commands on the MAE-Access to back up and
export the configuration file. The configuration file can be used to
restore the base station to the pre-reconfiguration status if the
reconfiguration fails.
1) To back up the configuration file, run the BKP CFGFILE
command.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 838

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

2) To export the configuration file, run the ULD CFGFILE command.

Example: ULD CFGFILE: MODE=IPV4, IP="192.169.2.16",
USR="admin", PWD="*****";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.9.8.4 Engineering Verification

This section describes how to verify the replacement of an SeGW.

Procedure
Step 1 Verify that ALM-25891 IKE Negotiation Failure is not reported.

If ALM-25891 IKE Negotiation Failure is reported, clear the alarm according to

the instructions in 3900 & 5900 Series Base Station Alarm Reference.

Step 2 Run the DSP IKESA command to check whether the value of SA Flag is Ready|
StayAlive for each entry. In addition, check whether the number of ACL rules for
which User Display Phase is Phase2 (indicating that the IPsec SA is established) is
the same as the number of ACL rules planned for IPsec SA establishment. Then,
check whether Rule ID is unique and not NULL.

Step 3 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.

If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.

Step 4 Verify that ALM-25886 IP Path Fault is not reported.

If ALM-25886 IP Path Fault is reported, clear the alarm according to the

instructions in 3900 & 5900 Series Base Station Alarm Reference.

----End

1.9.8.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Context
If the reconfiguration fails, the OM channel will be disconnected. Therefore, the
engineering rollback can be performed only on the local LMT.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 839

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Restore the configuration data.
● On the LMT, download and activate the original configuration file.
a. Run the DLD CFGFILE command to download the configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run the ACT CFGFILE command to activate the configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Roll back the configuration data using the one-click blind configuration
rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 Restore the physical connections.

Step 3 Verify that engineering rollback is successful according to instructions in 1.9.8.4

Engineering Verification.

----End

1.9.9 Adjusting the VLAN

This section describes how to adjust the VLAN.

Prerequisites
● The VLAN division for associated transport devices has been completed.
● The VLAN for the switch connected directly to the eNodeB has been adjusted.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 840

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.9.9.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for adjusting the VLAN.

Application Scenario
Transmission VLANs are re-planned, and VLANs to which transmission links belong
and the VLAN priorities need to be reconfigured.

Reconfiguration Impact
During VLAN adjustment, the associated transmission channels are disconnected,
and therefore ongoing services are interrupted. For example:
● When the VLAN to which an OM channel belongs is adjusted, the base
station will be disconnected from the OSS.
● When the VLAN to which an S1 interface belongs is adjusted, the S1 interface
will become unusable.
● When the VLAN to which an X2 interface belongs is adjusted, the X2 interface
will become unusable.
● When the VLAN to which an IP clock link belongs is adjusted, the IP clock link
will become unusable.

Reconfiguration Scheme
Figure 1-162 shows the reconfiguration procedure for adjusting a VLAN.
Determine the reconfiguration scheme according to the following table.

Table 1-282 Scheme options (IPv4 Transmission)

If... Then...

The VLAN mode is VLAN group and Modify the settings of the VLANCLASS
IPv4 transmission is used and VLANMAP MOs.

The VLAN mode is single VLAN and Modify only the settings of the
IPv4 transmission is used VLANMAP MO.

IPv6 transmission is used Change the VLAN ID.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 841

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-162 Procedure for adjusting a VLAN (IPv4)

Figure 1-163 Procedure for adjusting a VLAN (IPv6)

Topology Change
N/A

1.9.9.2 Engineering Preparation

This section describes the engineering preparation for adjusting the VLAN,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also describes the data preparation mode
and provides MML configuration script examples.

Information Collection
Table 1-283 describes the information to be collected for data preparation.

Table 1-283 Information to be collected

Information Description

VLAN ID ID of the adjusted VLAN

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 842

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Description

Next-hop IP address Next-hop IP address of the eNodeB toward the adjusted

VLAN.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

NOTE

For a co-MPT MBTS, if all RATs share the same VLAN, you only need to modify the VLAN data
once, and the modification takes effect for all RATs.

Table 1-284 Data preparation for adjusting a VLAN (IPv4 transmission)

SN Ope MO Configuration Reference
ratio
n

1 Modi VLANCLASS Change the values of VLAN Group No.,

fy Traffic Type, VLAN ID, and VLAN
Priority to the target values.

2 Modi VLANMAP Change the values of VLAN Group No.,

fy VLAN ID, and VLAN Priority to the
target values.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 843

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-285 Data preparation for adjusting a VLAN (IPv6 transmission)

SN Ope MO Configuration Reference

ratio
n

1 Modi INTERFACE Change VLAN ID to the target value.

fy

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.
● Using the batch reconfiguration mode of the MAE-Deployment (with the
name of the scenario being "Adjusting the VLAN"): For details, see the
interactive operation guide 1.11.2 Using the Batch Reconfiguration Mode of
the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

In the following example, you need to change the OM VLAN with the VLAN mode
set to VLAN group mode.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
/*Modifying the mapping between the traffic type OM_HIGH and the VLAN priority*/
MOD VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM_HIGH, VLANID=3, VLANPRIO=3;
/*Modifying the mapping between the traffic type OM_LOW and the VLAN priority*/
MOD VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM_LOW, VLANID=3, VLANPRIO=3;
/*Modify the settings of the VLANMAP MO.*/
MOD VLANMAP: NEXTHOPIP="172.31.13.1", MASK="255.255.255.255", VLANMODE=VLANGROUP,
VLANGROUPNO=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 844

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.9.9.3 Engineering Implementation

This section describes the engineering implementation for adjusting the VLAN,
including prerequisites, context, and procedure.

Prerequisites
The information and data for adjusting the VLAN are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
If MML commands are used for reconfiguration, run MML commands on the
LMT to deliver the prepared data to the eNodeB and then activate the data.
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
b. Back up and export the configuration file. The configuration file can be
used to roll back configurations to the original state, if the
reconfiguration fails.
i. Run the BKP CFGFILE command to back up the configuration file.
ii. Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
c. Use the LMT to deliver the batch configuration script prepared according
to Engineering Preparation > Data Preparation to the base station and
activate the script on the base station. For details, see 1.3.2 Running
MML Commands on the LMT.
d. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
● Remote Operations
If the MAE-Deployment is used for reconfiguration, use the MAE-Deployment
to deliver the prepared data to the base station and activate it.
a. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 845

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

b. Deliver the configuration data to the eNodeB and activate the data. For
details, see the interactive operation guide Delivering Data to Base
Stations and Activating the Data.
c. After the reconfiguration is complete, set the eNodeB maintenance mode
to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.9.9.4 Engineering Verification

This section describes how to verify the reconfiguration for adjusting a VLAN.

Procedure
● If the OM VLAN has been adjusted:
a. Verify that no ALM-25901 Remote Maintenance Link Failure is
reported.
If ALM-25901 Remote Maintenance Link Failure is reported, clear the
alarm according to the instructions in 3900 & 5900 Series Base Station
Alarm Reference.
● If the service VLAN has been adjusted:
a. Verify that no ALM-29201 S1 Interface Fault, ALM-29204 X2 Interface
Fault, or ALM-26262 External Clock Reference Problem is reported.
If any of the preceding alarms is generated, check whether the VLAN
configuration is correct:

▪ If it is incorrect, modify the VLAN configuration.

▪ If it is correct, clear the alarm according to the instructions in 3900 &

5900 Series Base Station Alarm Reference.
----End

1.9.9.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 846

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",

USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.9.9.4

Engineering Verification.

----End

1.9.10 Changing the VLAN Mode from VLAN Group to Single

VLAN (Only for IPv4 Transmission)
This section describes how to change the VLAN mode from VLAN group to single
VLAN.

1.9.10.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the VLAN mode from
VLAN group to single VLAN.

Application Scenario
The VLAN mode is re-planned: changing from VLAN group to single VLAN. The
VLAN groups meet both of the following conditions:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 847

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

In each VLAN group, all service types are mapped to the same VLAN ID. That is,
the service types are not isolated using VLANs. Throughout the VLAN groups, each
service type is assigned a unique differentiated services code point (DSCP) value,
or service types with an identical DSCP value are assigned the same VLAN priority.

Reconfiguration Impact
Adjusting the VLAN mode from VLAN group to single VLAN will interrupt the
involved transmission paths and ongoing services. For example:
● When the VLAN to which an OM channel belongs is adjusted, the base
station will be disconnected from the OSS.
● When the VLAN to which an S1 interface belongs is adjusted, the S1 interface
will become unusable.
● When the VLAN to which an X2 interface belongs is adjusted, the X2 interface
will become unusable.
● When the VLAN to which an IP clock link belongs is adjusted, the IP clock link
will become unusable.

Reconfiguration Scheme
NOTE

The number of VLAN priorities configured for the eNodeB must be less than or equal to the
number of VLAN priorities supported by the user equipment.

Figure 1-164 shows the reconfiguration procedure for changing the VLAN mode
from VLAN group to single VLAN.

Figure 1-164 Procedure for changing the VLAN mode

Topology Change
N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 848

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.9.10.2 Engineering Preparation

This section describes the engineering preparation for changing the VLAN mode
from VLAN group to single VLAN, including information collection and preparation
of hardware, software, license files, security certificates, and data. It also describes
the data preparation mode and provides MML configuration script examples.

Information Collection
Table 1-286 describes the information to be collected for data preparation.

Table 1-286 Information to be collected

Information Description

VLAN ID The VLAN ID of each VLAN.

Priorities of The DSCP values of user data, signaling, high-priority

differentiated services OM data, low-priority OM data, and other data in the
code points (DSCPs) original VLAN group, and the mapping VLAN priorities.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

NOTE

For a co-MPT MBTS, if all RATs share the same VLAN, you only need to modify the VLAN data
once, and the modification takes effect for all RATs.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 849

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-287 Data preparation for changing the VLAN mode from VLAN group to
single VLAN

SN Ope MO Configuration Reference

ratio
n

1 Modi DSCPMAP Set Differentiated Service Codepoint

fy and VLAN Priority to the target values
for service types except for the other
data type based on configurations of the
original VLAN group.
Set the VLAN priority for services with
Traffic Type set to Other Data to the
default VLAN priority of the eNodeB.

2 Modi VLANMAP ● Set VLAN Mode to Single VLAN.

fy ● Set VLAN ID to the target value.
● Set Set VLAN Priority to Disable.

3 Rem VLANCLASS -
ove

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Changing the VLAN Mode from VLAN Group to
Single VLAN"): For details, see the interactive operation guide 1.11.2 Using
the Batch Reconfiguration Mode of the MAE-Deployment to Prepare
Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The MML configuration script is as follows:

If OMCH parameters are modified by mistake, the OMCH may be disconnected

and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 850

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,

RBKCONDITION=OMCH_FAULT;.
/*Changing the mapping between DSCP values and VLAN priorities*/
SET DSCPMAP: DSCP=25, VLANPRIO=3;
SET DSCPMAP: DSCP=35, VLANPRIO=4;
SET DSCPMAP: DSCP=55, VLANPRIO=6;
SET DSCPMAP: DSCP=48, VLANPRIO=5;
SET DSCPMAP: DSCP=40, VLANPRIO=4;
SET DSCPMAP: DSCP=58, VLANPRIO=7;
/*Changing the mapping between the next-hop IP address and the VLAN with VLAN ID of 1*/
MOD VLANMAP: NEXTHOPIP="10.10.10.10", MASK="255.255.255.255", VLANMODE=SINGLEVLAN,
VLANID=1, SETPRIO=DISABLE;
/*Removing the original VLAN group*/
RMV VLANCLASS:;

1.9.10.3 Engineering Implementation

This section describes the engineering implementation for changing the VLAN
mode, including prerequisites, context, and procedure.

Prerequisites
The information and data for changing the VLAN mode are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
iii. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 851

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.9.10.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the VLAN
mode from VLAN group to single VLAN.

Procedure
● If the OM VLAN has been adjusted:
a. Verify that no ALM-25901 Remote Maintenance Link Failure is
reported.

If ALM-25901 Remote Maintenance Link Failure is reported, clear the

alarm according to the instructions in 3900 & 5900 Series Base Station
Alarm Reference.
● If the service VLAN has been adjusted:
a. Verify that no ALM-29201 S1 Interface Fault, ALM-29204 X2 Interface
Fault, or ALM-26262 External Clock Reference Problem is reported.

If any of the preceding alarms is generated, check whether the VLAN

configuration is correct:

▪ If it is incorrect, modify the VLAN configuration.

▪ If it is correct, clear the alarm according to the instructions in 3900 &

5900 Series Base Station Alarm Reference.
----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 852

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.9.10.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Context
If the VLAN where the OM channel locates fails to be reconfigured, the OM
channel will be disconnected. Then, engineering rollback can be performed only by
running MML commands on the local LMT. If the service VLAN mode fails to be
reconfigured, engineering rollback can be performed on the MAE-Deployment or
by running MML commands on the MAE-Access.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 853

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify that engineering rollback is successful according to instructions in 1.9.10.4

Engineering Verification.

----End

1.9.11 Changing the VLAN Mode from Single VLAN to

Interface VLAN (Only for IPv4 Transmission)
This section describes how to change the VLAN mode from single VLAN to
interface VLAN.

1.9.11.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology change for changing the VLAN mode from
single VLAN to interface VLAN.

Prerequisites
Before the reconstruction, check whether the configuration of a single VLAN
meets the following conditions: After the VLAN mode is changed to interface
VLAN, the number of used VLAN priorities cannot exceed the number of VLAN
priorities supported by the customer network equipment.
NOTE

● Generally, the customer equipment supports eight VLAN priorities. In this case, this
condition check can be ignored.
● The next hops of multiple VLANMAP MOs cannot be on the same network segment.
● The GTMUb/UTRP/UCCU/UBBPe does not support interface VLANs.
● In IPsec scenarios, the LMPT supports only four INTERFACE MOs whose Interface Type
is set to VLAN. The LMPT supports only four VLAN interfaces.

Application Scenario
The VLAN configuration mode of the base station is single VLAN, and the
configurations of a single VLAN meet the requirements for reconstructing a single
VLAN to an interface VLAN. See the following table for details.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 854

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-288 Application scenarios

Scenario Is Reconstruction Supported?

There is a unique device IP address that is on Yes

the same network segment as the next-hop
address in the VLANMAP MO.

The values of the Next Hop IP parameter in No

the N VLANMAP MOs are on the same
network segment as the device IP address. (N
is greater than or equal to 2.)

Reconfiguration Impact
Adjusting the VLAN mode from single VLAN to interface VLAN will interrupt the
involved transmission paths and ongoing services. For example:
● When the VLAN to which an OM channel belongs is adjusted, the base
station will be disconnected from the OSS.
● When the VLAN to which an S1 interface belongs is adjusted, the S1 interface
will become unusable.
● When the VLAN to which an X2 interface belongs is adjusted, the X2 interface
will become unusable.
● When the VLAN to which an IP clock link belongs is adjusted, the IP clock link
will become unusable.

Reconfiguration Scheme
Figure 1-165 shows the reconfiguration procedure for changing the VLAN mode
from single VLAN to interface VLAN.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 855

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-165 Procedure for changing the VLAN mode from single VLAN to
interface VLAN

Topology Change
N/A

1.9.11.2 Engineering Preparation

This section describes the engineering preparation for changing the VLAN mode
from single VLAN to interface VLAN mode, including information collection and
preparation of hardware, software, license files, security certificates, and data. It
also describes the data preparation mode and provides MML configuration script
examples.

Information Collection
Table 1-289 describes the information to be collected for data preparation.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 856

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-289 Information to be collected

Information Description

Next-hop IP address Next-hop IP address and subnet mask configured in the

and subnet mask VLANMAP MO

DEVIP Find the device IP address that is on the same network

segment as the next-hop IP address in the VLANMAP
MO.

ETHPORT Find the Ethernet port to which the device IP address

belongs.

VLAN ID VLAN ID configured in the VLANMAP MO

Way of setting the ● SETPRIO configured in the VLANMAP MO: This

VLAN priority parameter indicates whether to set a priority for a
single VLAN.
● When this parameter is set to ENABLE, the VLAN
priority is configured in the current VLANMAP MO.
● When this parameter is set to DISABLE, the VLAN
priority is determined according to the mappings
between DSCPs and VLAN priorities. The mappings
can be configured using the SET DSCPMAP
command.

DSCP priority DSCP priority

VLAN priority VLAN priority configured in the VLANMAP MO

The following table lists the information collected based on the preceding table.
You need to check whether the collected information meets the reconstruction
requirements.

● There is a unique device IP address that is on the same network segment as

the next-hop address in the VLANMAP MO.
● After the VLAN mode is changed to interface VLAN, the number of VLAN
priorities in use should be no more than that of the VLAN priorities supported
by customer network equipment.

Table 1-290 Collected information

Next Hop IP and IP1/MASK1 IP2/MASK2

Mask in the
VLANMAP MO

DEVIP That Is on the IP11/MASK1 IP22/MASK1

Same Network
Segment as the Next
Hop IP in the
VLANMAP MO

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 857

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ETHPORT to Which a ETHPORT1 ETHPORT2

DEVIP Belongs

VLAN ID Configured 10 11
in the VLANMAP MO

VLAN Priority DISABLE/ENABLE DISABLE/ENABLE

Configured in the
VLANMAP MO

VRF Index, 0/1/1 0/1/1

Differentiated
Service Codepoint,
and VLAN Priority in
the DSCPMAP MO

VLAN Priority 2 3
Configured in the
VLANMAP MO

Hardware Preparation
The GTMUb/UTRP/UCCU/UBBPe does not support interface VLANs.
The LMPT supports only four VLAN interfaces.

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
Based on the reconfiguration procedure, determine the data you need to prepare
and prepare the data according to the following table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 858

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-291 Data preparation for changing the VLAN mode from single VLAN to
interface VLAN
Dat MO Setting Notes Data Source Command
a Reference
Type

Port ETH This parameter is User planning SET ETHPORT

ID POR mandatory and
T must be unique.

Diffe DSC Generate a User planning ADD

renti P2P DSCP-to-PCP DSCP2PCPMAP
ated CPM mapping table ADD
servi AP based on the DSCP2PCPREF
ces VLAN priorities
code before the
poin reconstruction,
t and then set the
and mappings
VLA between DSCPs
N and VLAN
prior priorities.
ity

VLA INTE Based on the User planning ADD INTERFACE

N ID RFA VLAN ID
CE configured in the
VLANMAP MO,
create an
INTERFACE MO
in which the
interface type is
VLAN, and then
associate the
INTERFACE MO
with the
DSCP2PCPMAP
MO.

IPv4 IPAD Add the IP User planning ADD IPADDR4

addr DR4 address
ess configured in the
ETHPORT MO to
the INTERFACE
MO.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 859

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

GUI to reconfigure a single base station. The three data preparation modes are
described as follows:
● Use the batch reconfiguration mode of the MAE-Deployment (with the name
of the scenario-specific template being "Changing the VLAN Mode from
Single VLAN to Interface VLAN"): For details, see the interactive operation
guide 1.11.2 Using the Batch Reconfiguration Mode of the MAE-
Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The following is an example of the MML configuration script for data preparation.
If OMCH parameters are modified by mistake, the OMCH may be disconnected
and cannot be restored within a long period of time. To avoid service
unavailability due to the OMCH disconnection, you are advised to turn on the
automatic rollback switch of the CB by running the CFM CB command before
configuring data. For example, CFM CB: MODE=UNFORCED, NAME="CB1",
COMMENT="Launch", AUTORBKSW=ENABLE, RBKTIME=60,
RBKCONDITION=OMCH_FAULT;.
//Removing the original VLAN configurations
RMV DSCPMAP: VRFIDX=0;
RMV VLANMAP: NEXTHOPIP="192.168.2.100", MASK="255.255.255.0";
RMV DEVIP: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, IP="192.168.2.10";
//Setting Transmission Configuration Mode to NEW
SET GTRANSPARA: TRANSCFGMODE=NEW;
//Setting the port ID of the Ethernet port (Determine the Ethernet port of the unique device IP address that
is on the same network segment as the next-hop IP address defined in the VLANMAP MO in advance.)
SET ETHPORT: PORTID=0, CN=0, SRN=0, SN=7, SBT=BASE_BOARD;
//Generating a DSCP-to-PCP mapping table based on the VLAN priorities before the reconstruction, and
then setting the mappings between DSCPs and VLAN priorities
ADD DSCP2PCPMAP: DSCP2PCPMAPID=0;
ADD DSCP2PCPREF: DSCP2PCPMAPID=0, DSCP2PCPREF.DSCP=0, DSCP2PCPREF.PCP=0;
//Creating an INTERFACE MO in which the interface type is VLAN based on the VLAN ID configured in the
VLANMAP MO, and then associating the INTERFACE MO with the DSCP2PCPMAP MO
ADD INTERFACE: ITFID=0, ITFTYPE=VLAN, PT=ETH, PORTID=0, VLAN=10, DSCP2PCPMAPID=0, VRFIDX=0,
MTU4=1500, ARPPROXY=ENABLE;
//Adding the IP address configured in the ETHPORT MO to the INTERFACE MO
ADD IPADDR4: ITFID=0, IP="192.168.2.10", MASK="255.255.255.0", VRFIDX=0;

1.9.11.3 Engineering Implementation

This section describes the engineering implementation for changing the VLAN
mode, including prerequisites, context, and procedure.

Prerequisites
The information and data for changing the VLAN mode are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 860

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Remote Operations describe the operations that must be performed on the

operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations
– Using the MAE-Deployment:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Deliver the configuration data to the eNodeB and activate the data.
For details, see the interactive operation guide Delivering Data to
Base Stations and Activating the Data.
iii. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 861

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.9.11.4 Engineering Verification

This section describes how to verify the reconfiguration for changing the VLAN
mode from single VLAN to interface VLAN.

Procedure
● Check whether the VLAN configurations are correct.
a. Run the LST DSCP2PCPMAP command to query the configurations of the
mappings between DSCPs and VLAN priorities.
Expected result: The configurations of the mappings between DSCPs and
VLAN priorities are consistent with the planned data.
b. Run the LST INTERFACE command to query VLAN configurations.
Expected result: The VLAN configurations are consistent with the planned
data.
c. Run the LST IPADDR4 command to query IPv4 address configurations.
Expected result: The IPv4 address configurations are consistent with the
planned data.
● If the OM VLAN has been adjusted:
a. Verify that no ALM-25901 Remote Maintenance Link Failure is
reported.
If ALM-25901 Remote Maintenance Link Failure is reported, clear the
alarm according to the instructions in 3900 & 5900 Series Base Station
Alarm Reference.
● If the service VLAN has been adjusted:
a. Verify that no ALM-29201 S1 Interface Fault, ALM-29204 X2 Interface
Fault, or ALM-26262 External Clock Reference Problem is reported.
If any of the preceding alarms has been reported, check whether the
VLAN configurations are correct.

▪ If they are incorrect, modify the VLAN configurations.

▪ If it is correct, clear the alarm according to the instructions in 3900 &

5900 Series Base Station Alarm Reference.
----End

1.9.11.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Context
If the VLAN where the OM channel locates fails to be reconfigured, the OM
channel will be disconnected. Then, engineering rollback can be performed only by
running MML commands on the LMT. If the service VLAN mode fails to be
reconfigured, engineering rollback can be performed on the MAE-Deployment or
by running MML commands on the MAE-Access.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 862

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 Verify the engineering rollback by referring to the procedures in 1.9.11.4

Engineering Verification.

----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 863

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.10 Reconfigurations Dedicated to the LampSite

Solution
This section provides guidelines for typical reconfigurations related to the
LampSite solution, including solutions for connections between RHUBs and
RRU3230E/RRU3930E/pRRU in LampSite topologies.

1.10.1 Adding a pRRU-Aggregation Cell

This section describes how to add a pRRU-aggregation cell.

1.10.1.1 Scheme Overview

This section describes the application scenario, reconfiguration impact, topology
change, and the reconfiguration scheme of adding a pRRU-aggregation cell.

Application Scenario
With the development of mobile network, indoor communications quality must be
improved to provide better user experience. The LampSite solution provides indoor
coverage for densely populated and closed areas, such as office buildings,
subways, residential communities, and shopping malls, to ensure good user
experience. pRRUs are used to provide radio coverage for indoor areas. pRRUs are
connected to RHUBs using Ethernet cables. RHUBs are then connected to the
baseband processing units (BBP) in the BBU using optical fibers.

Reconfiguration Impact
Reconfiguration of the chain or ring topologies causes the cells on the chain or
ring unavailable.
When the pRRU added is a pRRU3911, if the new cell operates at a band that
does not take effect, the pRRU3911 will be reset for the band to take effect when
the cell is activated (by running the ACT CELL command), interrupting services of
cells working on other bands.

Topology Change
Use the addition of an RHUB, a BBP, pRRUs, and a pRRU-aggregation cell as an
example. Figure 1-166 shows the topologies before and after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 864

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-166 Topologies before and after adding a pRRU-aggregation cell (intra-
RHUB networking)

Use the addition of a pRRU-aggregation cell served by two RHUBs and 16 pRRUs,
and the addition of a BBP as an example. Figure 1-167 shows the topologies
before and after the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 865

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-167 Topologies before and after adding a pRRU-aggregation cell (inter-
RHUB networking)

Reconfiguration Scheme
Determine the reconfiguration scheme based on conditions:
● Add BBPs and CPRI connections if the BBPs are insufficient. Add a BBP under
either of the following conditions:
– The baseband resources are insufficient.
– LampSite cells and macro cells share the BBU. There is no BBP specific to
LampSite cells.
NOTE

If no baseband equipment is specified for LampSite cells, the eNodeB automatically

allocates different BBPs to LampSite cells and macro cells when allocating baseband
resources.
If the customer configures LampSite cells and macro cells on the same BBP, the type
of cells to be established later report cell setup failures.
● Add RHUBs and CPRI connections if the RHUBs are insufficient.
● Add CPRI links and pRRUs.
● Add sectors.
● Add sector equipment.
● Add a cell with MultiRruCellMode set to
MPRU_AGGREGATION(MPRU_AGGREGATION).
● Add a sector equipment group for the cell based on the target network.
● Change the reference signal power of the cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 866

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Add an operator for the cell.

● Activate the cell.
Figure 1-168 shows the procedure for adding a pRRU-aggregation cell.

Figure 1-168 Procedure for adding a pRRU-aggregation cell

1.10.1.2 Engineering Preparation

This section describes the engineering preparation for adding a pRRU-aggregation
cell, including information collection and preparation of hardware, software,
license files, security certificates, and data. It also provides an example of MML
configuration scripts.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 867

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Collection
Table 1-292 describes the information to be collected before adding a pRRU-
aggregation cell.

Table 1-292 Information collection

Information Description

Cell information ● Basic information about the cell to be added

● TX and RX mode. In an FDD or NB-IoT network,
pRRU-aggregation cells support 1T1R or 2T2R mode.
In a TDD network, pRRU-aggregation cells support
only 2T2R mode.

BBP type ● The type of the BBPs. For example, the UBBP.
● LBBP working mode. pRRU-aggregation cells support
TDD, NBIOT, or FDD.
● UBBP baseband work standard. pRRU-aggregation
cells support LTE_TDD(LTE TDD), NBIOT, or
LTE_FDD(LTE FDD).

RF unit ● Types of newly added RF units. pRRU-aggregation

cells support only the MPMU.
● Connections between pRRUs and RHUBs

Network topology Network topology of pRRU-aggregation cellsa

Sector equipment Value of the Sector Equipment Group ID and Sector

group equipment ID parameters in the EuSectorEqmGroup
MO

Reference signal pRRU reference signal power

power

a: pRRU-aggregation cells support only the chain topology. Set Topo Position to
BRANCH(BRANCH).

Hardware Preparation
Table 1-293 describes the hardware to be prepared for adding a pRRU-
aggregation cell in addition to the new pRRUs, related cables, and optical
modules.

Table 1-293 Hardware to be prepared

If... Then...

BBPs are insufficient Add new XBBPs.

RHUBs are Add new RHUBs and related cables and optical
insufficient modules.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 868

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation
N/A

License File Preparation

Prepare a new license file if the license in use cannot meet requirements. Table
1-294 describes the license control items to be prepared.

Table 1-294 License control items to be prepared (1)

License Control Item Description

Cell License(per Cell) Controls the number of cells.

Carrier Controls the cell bandwidth.

Bandwidth(per
5MHz)

Resource Block(per Controls resource blocks (RBs).

RB)

BB Receive Controls the baseband receive channel.

Channel(per
Channel)

RF Transmit Controls the RF transmit channel.

Channel(per
Channel)

Table 1-295 describes the LampSite license control items to be prepared based on
network requirements.

Table 1-295 License control items to be prepared (2)

License Control Item Description

Intra-BBU Baseband Controls the intra-BBU baseband sharing per cell.

Sharing (2T)(per
Cell)

CPRI Controls the CPRI compression.

Compression(per
Cell)

Security Certificate Preparation

N/A

Data Preparation
Prepare data listed in the following table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 869

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-296 Data preparation for adding a pRRU-aggregation cell

SN Oper MO Configuration Reference
ation

1 Add RU (using MML -

commands)/BBP (using the
MAE-Deployment)

2 Add RHUB

3 Add RRUCHAIN

4 Add RRU

5 Add Sector

6 Add SECTOREQM

7 Add Cell Set MultiRruCellFlag to

BOOLEAN_TRUE(True) and
MultiRruCellMode to
MPRU_AGGREGATION(MPRU
_AGGREGATION). In the
LampSite solution,
MultiRruCellMode must be
set to
MPRU_AGGREGATION(MPRU
_AGGREGATION).
In NB-IoT networks, set
NbCellFlag to NBIOT.

8 Add EuSectorEqmGroup Add sector equipment groups

based on network
requirements. Configure the
sector equipment of pRRUs
that serve one cell in the same
sector equipment group.a

9 Add PDSCHCfg Modify the PDSCHCfg MO

with ReferenceSignalPwr set
to, for example, -81(0.1dBm).

10 Modi CellOp -
fy

11 Activ Cell
ate

a: In the LampSite solution, the mapping between SectorEqm and Cell must be
specified using the EuSectorEqmGroup MO.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 870

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Deployment to reconfigure base stations in batches and use the MAE-Deployment

GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario-specific template being "Adding a pRRU-Aggregation
Cell"): For details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The following lists the MML configuration scripts for adding RHUBs, pRRUs, BBPs,
and a pRRU-aggregation cell. If the current license cannot meet the requirements,
load a new license file. If the current license meets the requirements, directly add
a pRRU-aggregation cell.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/", FN="
LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN=" LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*(FDD) Adding a BBP working in FDD*/ ADD BRD: SN=3, BT=LBBP, WM=FDD;
/*(TDD) Adding a BBP working in TDD*/ ADD BRD: SN=3, BT=LBBP, WM=TDD;
/*Adding baseband equipment*/
ADD BASEBANDEQM:BASEBANDEQMID=2, BASEBANDEQMTYPE=ULDL,
UMTSDEMMODE=NULL,SN1=2,SN2=3;
/*Adding an RRU chain or ring for RHUBs*/
ADD RRUCHAIN: RCN=30, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=3, HPN=0;
/*Adding RHUBs*/
ADD RHUB: CN=0, SRN=60, RCN=30, PS=0, RN="slot_3_0_0";
ADD RHUB: CN=0, SRN=70, RCN=30, PS=1, RN="slot_3_0_1";
ADD RHUB: CN=0, SRN=80, RCN=30, PS=2, RN="slot_3_0_2";
ADD RHUB: CN=0, SRN=90, RCN=30, PS=3, RN="slot_3_0_3";
/*Adding an RRU chain or ring for pRRUs*/
ADD RRUCHAIN: RCN=61, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=0;
ADD RRUCHAIN: RCN=62, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=1;
ADD RRUCHAIN: RCN=63, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=2;
ADD RRUCHAIN: RCN=64, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=3;
ADD RRUCHAIN: RCN=65, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=4;
ADD RRUCHAIN: RCN=66, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=5;
ADD RRUCHAIN: RCN=67, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=6;
ADD RRUCHAIN: RCN=68, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=7;
ADD RRUCHAIN: RCN=71, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=70, HSN=0, HPN=0;
ADD RRUCHAIN: RCN=72, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=70, HSN=0, HPN=1;
ADD RRUCHAIN: RCN=73, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=70, HSN=0, HPN=2;
ADD RRUCHAIN: RCN=74, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=70, HSN=0, HPN=3;
ADD RRUCHAIN: RCN=75, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=70, HSN=0, HPN=4;
ADD RRUCHAIN: RCN=76, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=70, HSN=0, HPN=5;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 871

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD RRUCHAIN: RCN=77, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=70, HSN=0, HPN=6;

ADD RRUCHAIN: RCN=78, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=70, HSN=0, HPN=7;
ADD RRUCHAIN: RCN=81, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=80, HSN=0, HPN=0;
ADD RRUCHAIN: RCN=82, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=80, HSN=0, HPN=1;
ADD RRUCHAIN: RCN=83, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=80, HSN=0, HPN=2;
ADD RRUCHAIN: RCN=84, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=80, HSN=0, HPN=3;
ADD RRUCHAIN: RCN=85, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=80, HSN=0, HPN=4;
ADD RRUCHAIN: RCN=86, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=80, HSN=0, HPN=5;
ADD RRUCHAIN: RCN=87, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=80, HSN=0, HPN=6;
ADD RRUCHAIN: RCN=88, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=80, HSN=0, HPN=7;
ADD RRUCHAIN: RCN=91, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=90, HSN=0, HPN=0;
ADD RRUCHAIN: RCN=92, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=90, HSN=0, HPN=1;
ADD RRUCHAIN: RCN=93, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=90, HSN=0, HPN=2;
ADD RRUCHAIN: RCN=94, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=90, HSN=0, HPN=3;
ADD RRUCHAIN: RCN=95, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=90, HSN=0, HPN=4;
ADD RRUCHAIN: RCN=96, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=90, HSN=0, HPN=5;
ADD RRUCHAIN: RCN=97, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=90, HSN=0, HPN=6;
ADD RRUCHAIN: RCN=98, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=90, HSN=0, HPN=7;
/*Adding pRRUs in FDD*/
ADD RRU: CN=0, SRN=61, SN=0, TP=BRANCH, RCN=61, PS=0, RT=MPMU, RS=FDL, RN="RRU61",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=62, SN=0, TP=BRANCH, RCN=62, PS=0, RT=MPMU, RS=FDL, RN="RRU62",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=63, SN=0, TP=BRANCH, RCN=63, PS=0, RT=MPMU, RS=FDL, RN="RRU63",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=64, SN=0, TP=BRANCH, RCN=64, PS=0, RT=MPMU, RS=FDL, RN="RRU64",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=65, SN=0, TP=BRANCH, RCN=65, PS=0, RT=MPMU, RS=FDL, RN="RRU65",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=66, SN=0, TP=BRANCH, RCN=66, PS=0, RT=MPMU, RS=FDL, RN="RRU66",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=67, SN=0, TP=BRANCH, RCN=67, PS=0, RT=MPMU, RS=FDL, RN="RRU67",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=68, SN=0, TP=BRANCH, RCN=68, PS=0, RT=MPMU, RS=FDL, RN="RRU68",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=71, SN=0, TP=BRANCH, RCN=71, PS=0, RT=MPMU, RS=FDL, RN="RRU71",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=72, SN=0, TP=BRANCH, RCN=72, PS=0, RT=MPMU, RS=FDL, RN="RRU72",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=73, SN=0, TP=BRANCH, RCN=73, PS=0, RT=MPMU, RS=FDL, RN="RRU73",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=74, SN=0, TP=BRANCH, RCN=74, PS=0, RT=MPMU, RS=FDL, RN="RRU74",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=75, SN=0, TP=BRANCH, RCN=75, PS=0, RT=MPMU, RS=FDL, RN="RRU75",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=76, SN=0, TP=BRANCH, RCN=76, PS=0, RT=MPMU, RS=FDL, RN="RRU76",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=77, SN=0, TP=BRANCH, RCN=77, PS=0, RT=MPMU, RS=FDL, RN="RRU77",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=78, SN=0, TP=BRANCH, RCN=78, PS=0, RT=MPMU, RS=FDL, RN="RRU78",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=81, SN=0, TP=BRANCH, RCN=81, PS=0, RT=MPMU, RS=FDL, RN="RRU81",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=82, SN=0, TP=BRANCH, RCN=82, PS=0, RT=MPMU, RS=FDL, RN="RRU82",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=83, SN=0, TP=BRANCH, RCN=83, PS=0, RT=MPMU, RS=FDL, RN="RRU83",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=84, SN=0, TP=BRANCH, RCN=84, PS=0, RT=MPMU, RS=FDL, RN="RRU84",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=85, SN=0, TP=BRANCH, RCN=85, PS=0, RT=MPMU, RS=FDL, RN="RRU85",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=86, SN=0, TP=BRANCH, RCN=86, PS=0, RT=MPMU, RS=FDL, RN="RRU86",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=87, SN=0, TP=BRANCH, RCN=87, PS=0, RT=MPMU, RS=FDL, RN="RRU87",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=88, SN=0, TP=BRANCH, RCN=88, PS=0, RT=MPMU, RS=FDL, RN="RRU88",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=91, SN=0, TP=BRANCH, RCN=91, PS=0, RT=MPMU, RS=FDL, RN="RRU91",
RXNUM=0, TXNUM=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 872

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD RRU: CN=0, SRN=92, SN=0, TP=BRANCH, RCN=92, PS=0, RT=MPMU, RS=FDL, RN="RRU92",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=93, SN=0, TP=BRANCH, RCN=93, PS=0, RT=MPMU, RS=FDL, RN="RRU93",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=94, SN=0, TP=BRANCH, RCN=94, PS=0, RT=MPMU, RS=FDL, RN="RRU94",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=95, SN=0, TP=BRANCH, RCN=95, PS=0, RT=MPMU, RS=FDL, RN="RRU95",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=96, SN=0, TP=BRANCH, RCN=96, PS=0, RT=MPMU, RS=FDL, RN="RRU96",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=97, SN=0, TP=BRANCH, RCN=97, PS=0, RT=MPMU, RS=FDL, RN="RRU97",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=98, SN=0, TP=BRANCH, RCN=98, PS=0, RT=MPMU, RS=FDL, RN="RRU98",
RXNUM=0, TXNUM=0;
/*Adding pRRUs in TDD*/
ADD RRU: CN=0, SRN=61, SN=0, TP=BRANCH, RCN=61, PS=0, RT=MPMU, RS=TDL, RN="RRU61",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=62, SN=0, TP=BRANCH, RCN=62, PS=0, RT=MPMU, RS=TDL, RN="RRU62",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=63, SN=0, TP=BRANCH, RCN=63, PS=0, RT=MPMU, RS=TDL, RN="RRU63",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=64, SN=0, TP=BRANCH, RCN=64, PS=0, RT=MPMU, RS=TDL, RN="RRU64",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=65, SN=0, TP=BRANCH, RCN=65, PS=0, RT=MPMU, RS=TDL, RN="RRU65",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=66, SN=0, TP=BRANCH, RCN=66, PS=0, RT=MPMU, RS=TDL, RN="RRU66",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=67, SN=0, TP=BRANCH, RCN=67, PS=0, RT=MPMU, RS=TDL, RN="RRU67",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=68, SN=0, TP=BRANCH, RCN=68, PS=0, RT=MPMU, RS=TDL, RN="RRU68",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=71, SN=0, TP=BRANCH, RCN=71, PS=0, RT=MPMU, RS=TDL, RN="RRU71",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=72, SN=0, TP=BRANCH, RCN=72, PS=0, RT=MPMU, RS=TDL, RN="RRU72",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=73, SN=0, TP=BRANCH, RCN=73, PS=0, RT=MPMU, RS=TDL, RN="RRU73",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=74, SN=0, TP=BRANCH, RCN=74, PS=0, RT=MPMU, RS=TDL, RN="RRU74",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=75, SN=0, TP=BRANCH, RCN=75, PS=0, RT=MPMU, RS=TDL, RN="RRU75",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=76, SN=0, TP=BRANCH, RCN=76, PS=0, RT=MPMU, RS=TDL, RN="RRU76",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=77, SN=0, TP=BRANCH, RCN=77, PS=0, RT=MPMU, RS=TDL, RN="RRU77",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=78, SN=0, TP=BRANCH, RCN=78, PS=0, RT=MPMU, RS=TDL, RN="RRU78",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=81, SN=0, TP=BRANCH, RCN=81, PS=0, RT=MPMU, RS=TDL, RN="RRU81",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=82, SN=0, TP=BRANCH, RCN=82, PS=0, RT=MPMU, RS=TDL, RN="RRU82",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=83, SN=0, TP=BRANCH, RCN=83, PS=0, RT=MPMU, RS=TDL, RN="RRU83",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=84, SN=0, TP=BRANCH, RCN=84, PS=0, RT=MPMU, RS=TDL, RN="RRU84",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=85, SN=0, TP=BRANCH, RCN=85, PS=0, RT=MPMU, RS=TDL, RN="RRU85",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=86, SN=0, TP=BRANCH, RCN=86, PS=0, RT=MPMU, RS=TDL, RN="RRU86",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=87, SN=0, TP=BRANCH, RCN=87, PS=0, RT=MPMU, RS=TDL, RN="RRU87",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=88, SN=0, TP=BRANCH, RCN=88, PS=0, RT=MPMU, RS=TDL, RN="RRU88",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=91, SN=0, TP=BRANCH, RCN=91, PS=0, RT=MPMU, RS=TDL, RN="RRU91",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=92, SN=0, TP=BRANCH, RCN=92, PS=0, RT=MPMU, RS=TDL, RN="RRU92",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=93, SN=0, TP=BRANCH, RCN=93, PS=0, RT=MPMU, RS=TDL, RN="RRU93",
RXNUM=0, TXNUM=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 873

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD RRU: CN=0, SRN=94, SN=0, TP=BRANCH, RCN=94, PS=0, RT=MPMU, RS=TDL, RN="RRU94",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=95, SN=0, TP=BRANCH, RCN=95, PS=0, RT=MPMU, RS=TDL, RN="RRU95",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=96, SN=0, TP=BRANCH, RCN=96, PS=0, RT=MPMU, RS=TDL, RN="RRU96",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=97, SN=0, TP=BRANCH, RCN=97, PS=0, RT=MPMU, RS=TDL, RN="RRU97",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=98, SN=0, TP=BRANCH, RCN=98, PS=0, RT=MPMU, RS=TDL, RN="RRU98",
RXNUM=0, TXNUM=0;
/*Adding sectors*/
ADD SECTOR: SECTORID=61, ANTNUM=2, ANT1CN=0, ANT1SRN=61, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=61, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=62, ANTNUM=2, ANT1CN=0, ANT1SRN=62, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=62, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=63, ANTNUM=2, ANT1CN=0, ANT1SRN=63, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=63, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=64, ANTNUM=2, ANT1CN=0, ANT1SRN=64, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=64, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=65, ANTNUM=2, ANT1CN=0, ANT1SRN=65, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=65, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=66, ANTNUM=2, ANT1CN=0, ANT1SRN=66, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=66, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=67, ANTNUM=2, ANT1CN=0, ANT1SRN=67, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=67, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=68, ANTNUM=2, ANT1CN=0, ANT1SRN=68, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=68, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=71, ANTNUM=2, ANT1CN=0, ANT1SRN=71, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=71, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=72, ANTNUM=2, ANT1CN=0, ANT1SRN=72, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=72, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=73, ANTNUM=2, ANT1CN=0, ANT1SRN=73, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=73, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=74, ANTNUM=2, ANT1CN=0, ANT1SRN=74, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=74, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=75, ANTNUM=2, ANT1CN=0, ANT1SRN=75, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=75, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=76, ANTNUM=2, ANT1CN=0, ANT1SRN=76, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=76, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=77, ANTNUM=2, ANT1CN=0, ANT1SRN=77, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=77, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=78, ANTNUM=2, ANT1CN=0, ANT1SRN=78, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=78, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=81, ANTNUM=2, ANT1CN=0, ANT1SRN=81, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=81, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=82, ANTNUM=2, ANT1CN=0, ANT1SRN=82, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=82, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=83, ANTNUM=2, ANT1CN=0, ANT1SRN=83, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=83, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=84, ANTNUM=2, ANT1CN=0, ANT1SRN=84, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=84, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=85, ANTNUM=2, ANT1CN=0, ANT1SRN=85, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=85, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=86, ANTNUM=2, ANT1CN=0, ANT1SRN=86, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=86, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=87, ANTNUM=2, ANT1CN=0, ANT1SRN=87, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=87, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=88, ANTNUM=2, ANT1CN=0, ANT1SRN=88, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=88, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=91, ANTNUM=2, ANT1CN=0, ANT1SRN=91, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=91, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=92, ANTNUM=2, ANT1CN=0, ANT1SRN=92, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=92, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=93, ANTNUM=2, ANT1CN=0, ANT1SRN=93, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=93, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=94, ANTNUM=2, ANT1CN=0, ANT1SRN=94, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=94, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=95, ANTNUM=2, ANT1CN=0, ANT1SRN=95, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=95, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 874

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD SECTOR: SECTORID=96, ANTNUM=2, ANT1CN=0, ANT1SRN=96, ANT1SN=255, ANT1N=R0A,

ANT2CN=0, ANT2SRN=96, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=97, ANTNUM=2, ANT1CN=0, ANT1SRN=97, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=97, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=98, ANTNUM=2, ANT1CN=0, ANT1SRN=98, ANT1SN=255, ANT1N=R0A,
ANT2CN=0, ANT2SRN=98, ANT2SN=255, ANT2N=R0B, CREATESECTOREQM=FALSE;
/*Adding sector equipment*/
ADD SECTOREQM: SECTOREQMID=61, SECTORID=61, ANTNUM=2, ANT1CN=0, ANT1SRN=61,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=61, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=62, SECTORID=62, ANTNUM=2, ANT1CN=0, ANT1SRN=62,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=62, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=63, SECTORID=63, ANTNUM=2, ANT1CN=0, ANT1SRN=63,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=63, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=64, SECTORID=64, ANTNUM=2, ANT1CN=0, ANT1SRN=64,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=64, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=65, SECTORID=65, ANTNUM=2, ANT1CN=0, ANT1SRN=65,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=65, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=66, SECTORID=66, ANTNUM=2, ANT1CN=0, ANT1SRN=66,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=66, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=67, SECTORID=67, ANTNUM=2, ANT1CN=0, ANT1SRN=67,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=67, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=68, SECTORID=68, ANTNUM=2, ANT1CN=0, ANT1SRN=68,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=68, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=71, SECTORID=71, ANTNUM=2, ANT1CN=0, ANT1SRN=71,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=71, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=72, SECTORID=72, ANTNUM=2, ANT1CN=0, ANT1SRN=72,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=72, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=73, SECTORID=73, ANTNUM=2, ANT1CN=0, ANT1SRN=73,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=73, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=74, SECTORID=74, ANTNUM=2, ANT1CN=0, ANT1SRN=74,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=74, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=75, SECTORID=75, ANTNUM=2, ANT1CN=0, ANT1SRN=75,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=75, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=76, SECTORID=76, ANTNUM=2, ANT1CN=0, ANT1SRN=76,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=76, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=77, SECTORID=77, ANTNUM=2, ANT1CN=0, ANT1SRN=77,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=77, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=78, SECTORID=78, ANTNUM=2, ANT1CN=0, ANT1SRN=78,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=78, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=81, SECTORID=81, ANTNUM=2, ANT1CN=0, ANT1SRN=81,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=81, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=82, SECTORID=82, ANTNUM=2, ANT1CN=0, ANT1SRN=82,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=82, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=83, SECTORID=83, ANTNUM=2, ANT1CN=0, ANT1SRN=83,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=83, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=84, SECTORID=84, ANTNUM=2, ANT1CN=0, ANT1SRN=84,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=84, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=85, SECTORID=85, ANTNUM=2, ANT1CN=0, ANT1SRN=85,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=85, ANT2SN=255,

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 875

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=86, SECTORID=86, ANTNUM=2, ANT1CN=0, ANT1SRN=86,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=86, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=87, SECTORID=87, ANTNUM=2, ANT1CN=0, ANT1SRN=87,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=87, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=88, SECTORID=88, ANTNUM=2, ANT1CN=0, ANT1SRN=88,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=88, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=91, SECTORID=91, ANTNUM=2, ANT1CN=0, ANT1SRN=91,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=91, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=92, SECTORID=92, ANTNUM=2, ANT1CN=0, ANT1SRN=92,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=92, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=93, SECTORID=93, ANTNUM=2, ANT1CN=0, ANT1SRN=93,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=93, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=94, SECTORID=94, ANTNUM=2, ANT1CN=0, ANT1SRN=94,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=94, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=95, SECTORID=95, ANTNUM=2, ANT1CN=0, ANT1SRN=95,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=95, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=96, SECTORID=96, ANTNUM=2, ANT1CN=0, ANT1SRN=96,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=96, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=97, SECTORID=97, ANTNUM=2, ANT1CN=0, ANT1SRN=97,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=97, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=98, SECTORID=98, ANTNUM=2, ANT1CN=0, ANT1SRN=98,
ANT1SN=255, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=98, ANT2SN=255,
ANT2N=R0B, ANTTYPE2=RXTX_MODE;
/*Adding a cell with MultiRruCellFlag set to BOOLEAN_TRUE and MultiRruCellMode set to
MPRU_AGGREGATION in FDD*/
ADD CELL: LocalCellId=1, CellName="1", FreqBand=1, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=500,
UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=1, PhyCellId=1, FddTddInd=CELL_FDD,
RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION, CPRICompression=NORMAL_COMPRESSION, TxRxMode=2T2R;
/*Adding a cell with MultiRruCellFlag set to BOOLEAN_TRUE and MultiRruCellMode set to
MPRU_AGGREGATION in NB-IoT*/
ADD CELL: LocalCellId=1, CellName="1", NbCellFlag=TRUE, FreqBand=1, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=500, UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=1, PhyCellId=1,
FddTddInd=CELL_FDD, RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION, CPRICompression=NORMAL_COMPRESSION, TxRxMode=2T2R;
/*Adding a cell with MultiRruCellFlag set to BOOLEAN_TRUE and MultiRruCellMode set to
MPRU_AGGREGATION in TDD*/
ADD CELL: LocalCellId=1, CellName="1", FreqBand=38, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=38000,
UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=1, PhyCellId=1, FddTddInd=CELL_TDD,
SubframeAssignment=SA2, SpecialSubframePatterns=SSP5, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION, CPRICompression=NORMAL_COMPRESSION, TxRxMode=2T2R;
/*Adding sector equipment groups and adding sector equipment to the sector equipment groups*/
ADD EUSECTOREQMGROUP: LOCALCELLID=1, SECTOREQMGROUPID=60, BASEBANDEQMID=2;
ADD EUSECTOREQMGROUP: LOCALCELLID=1, SECTOREQMGROUPID=70, BASEBANDEQMID=2;
ADD EUSECTOREQMGROUP: LOCALCELLID=1, SECTOREQMGROUPID=80, BASEBANDEQMID=2;
ADD EUSECTOREQMGROUP: LOCALCELLID=1, SECTOREQMGROUPID=90, BASEBANDEQMID=2;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=60, SECTOREQMID=61;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=60, SECTOREQMID=62;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=60, SECTOREQMID=63;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=60, SECTOREQMID=64;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=60, SECTOREQMID=65;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=60, SECTOREQMID=66;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=60, SECTOREQMID=67;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=60, SECTOREQMID=68;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 876

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=70, SECTOREQMID=71;

ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=70, SECTOREQMID=72;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=70, SECTOREQMID=73;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=70, SECTOREQMID=74;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=70, SECTOREQMID=75;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=70, SECTOREQMID=76;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=70, SECTOREQMID=77;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=70, SECTOREQMID=78;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=80, SECTOREQMID=81;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=80, SECTOREQMID=82;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=80, SECTOREQMID=83;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=80, SECTOREQMID=84;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=80, SECTOREQMID=85;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=80, SECTOREQMID=86;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=80, SECTOREQMID=87;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=80, SECTOREQMID=88;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=90, SECTOREQMID=91;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=90, SECTOREQMID=92;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=90, SECTOREQMID=93;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=90, SECTOREQMID=94;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=90, SECTOREQMID=95;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=90, SECTOREQMID=96;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=90, SECTOREQMID=97;
ADD EUSECTOREQMID2GROUP: LOCALCELLID=1, SECTOREQMGROUPID=90, SECTOREQMID=98;
/*Changing the reference signal power of the cell served by pRRUs*/
MOD PDSCHCFG: LocalCellId=1, ReferenceSignalPwr=-81;
/*Adding operator information for the cell*/
ADD CELLOP: LocalCellId=1, TrackingAreaId=0;
/*Activating the cell*/
ACT CELL: LocalCellId=1;

1.10.1.3 Engineering Implementation

This section describes the engineering implementation of adding a pRRU-
aggregation cell, including local and remote operations.

Prerequisites
The required information, license file, and configuration data file are available.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local operations
a. Install the BBPs in the BBU.
b. Install the RHUBs. For details, see LampSite Installation Guide.
c. Install the pRRUs. For details, see LampSite Installation Guide.
d. Install the CPRI optical fibers and cables. For details, see LampSite
Installation Guide.
● Remote operations
– Using the MAE-Deployment:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 877

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 878

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iv. After the reconfiguration is complete, set the eNodeB maintenance

mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.10.1.4 Engineering Verification

This section describes how to verify whether a pRRU-aggregation cell is
successfully added.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If a cell-related alarm is reported, clear it according to instructions in 3900 & 5900
Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command to check whether Cell instance state is Normal.
If Cell instance state is Uninstall, check cell configuration data, cell reference
signal power, or hardware based on the value of Reason for latest state change
in the command output.
Step 3 Run the LST CELL command to check whether the values of Flag of Multi-RRU
Cell, Mode of Multi-RRU Cell, and Cell transmission and reception mode are
consistent with the configuration data.

----End

1.10.1.5 Engineering Rollback

If the reconfiguration fails, it can be rolled back to the original configuration.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 879

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful according to instructions in 1.10.1.4

Engineering Verification.

----End

1.10.2 Combining pRRU-Aggregation Cells

This section describes how to combine pRRU-aggregation cells.

1.10.2.1 Scheme Overview

This section describes the application scenario, reconfiguration impact, topology
change, and the reconfiguration scheme of combining pRRU-aggregation cells.

Application Scenario
To improve indoor network coverage, signal strength in coverage holes and weak
coverage areas must be enhanced. pRRUs can be used to provide radio coverage.
When there is a small number of UEs, multiple pRRU-aggregation cells can be
combined to form one pRRU-aggregation cell to reduce inter-cell interference
while saving baseband equipment resources.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 880

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

In FDD: A pRRU-aggregation cell can be connected to multiple RHUBs on the same CPRI link. An
eNodeB supports a maximum of four-layer cascaded RHUBs. One RHUB can serve a maximum
of two LTE cells that are also served by another RHUB. Inter-RHUB RF combination is not
supported for other LTE cells served by this RHUB. An RHUB can be connected to a maximum of
eight pRRUs, and a maximum of 16 pRRUs can be aggregated to serve one pRRU-aggregation
cell. If more than 16 pRRUs are aggregated, another pRRU-aggregation cell is required.
In TDD: RF combination of pRRUs connected to different RHUBs is not supported. An eNodeB
supports a maximum of four cascaded RHUBs. An RHUB can be connected to a maximum of
eight pRRUs, and a maximum of eight pRRUs can be aggregated to serve one pRRU-
aggregation cell. If more than eight pRRUs are aggregated, another RHUB and another pRRU-
aggregation cell are required.

Reconfiguration Impact
When pRRUs are added for an existing pRRU-aggregation cell, the cell must be
deactivated, which interrupts services in the cell.

Topology Change
Use configuring pRRUs for an existing pRRU-aggregation cell as an example.
Figure 1-169 and Figure 1-170 show the topologies before and after the
reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 881

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-169 Topologies before and after combining pRRU-aggregation cells

(intra-RHUB networking)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 882

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 883

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-170 Topologies before and after combining pRRU-aggregation cells (inter-RHUB
networking)

Reconfiguration Scheme
The reconfiguration procedure is as follows:
1. Deactivate the cells.
2. Delete the redundant cells.
3. Reconfigure the sector equipment group. Add sector equipment to the target
sector equipment group.
4. Activate the cell.
Figure 1-171 shows the procedure for combining pRRU-aggregation cells.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 884

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-171 Procedure for combining pRRU-aggregation cells

1.10.2.2 Engineering Preparation

This section describes the engineering preparation for combining pRRU-
aggregation cells, including information collection and preparation of hardware,
software, license files, security certificates, and data. It also provides an example
of MML configuration scripts.

Information Collection
Table 1-297 describes the information to be collected before combining pRRU-
aggregation cells.

Table 1-297 Information collection

Information Description

Network topology If RF units need to be added, pRRUs support only chain

topologies.

Sector equipment Value of the Sector Equipment Group ID and Sector

group equipment ID parameters in the EuSectorEqmGroup
MO

Hardware Preparation
None

Software Preparation
N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 885

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

License File Preparation

If pRRUs are configured for existing pRRU-aggregation cells, a new license is not
required.

Security Certificate Preparation

N/A

Data Preparation
Perform the operations listed in the following table.

Table 1-298 Data preparation for combining pRRU-aggregation cells

SN Oper MO Configuration Reference
ation

1 Deac Cell -
tivat
e

2 Delet Cell Delete the Cell MOs to delete

e redundant cells. The sector
equipment groups of
redundant cells are
automatically deleted when
the cells are deleted.

3 Modi EuSectorEqmGroup Add sector equipment groups

fy based on network
requirements. Configure the
sector equipment of pRRUs
that serve one cell in the same
sector equipment group.

4 Activ Cell -
ate

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 886

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario-specific template being "Combining pRRU-Aggregation
Cells"): For details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

The following lists the MML configuration scripts for combining four pRRU-
aggregation cells into one pRRU-aggregation cell. If the current license cannot
meet the requirements, load a new license file. If the current license meets the
requirements, directly combine pRRU-aggregation cells.
/*Deactivating cells*/
DEA CELL: LocalCellId=0;
DEA CELL: LocalCellId=1;
DEA CELL: LocalCellId=2;
DEA CELL: LocalCellId=3;
/*Removing cells*/
RMV CELL:LOCALCELLID=0;
RMV CELL:LOCALCELLID=2;
RMV CELL:LOCALCELLID=3;
/*Modifying sector equipment groups and adding sector equipment to the sector equipment groups*/
ADD EUSECTOREQMID2GROUP:LOCALCELLID=1,SECTOREQMGROUPID=1, SECTOREQMID=1;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=1,SECTOREQMGROUPID=1, SECTOREQMID=3;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=1,SECTOREQMGROUPID=1, SECTOREQMID=4;
/Activate the cell*/
ACT CELL: LocalCellId=1;

1.10.2.3 Engineering Implementation

This section describes the engineering implementation of combining pRRU-
aggregation cells, including local and remote operations.

Prerequisites
Related information, license files, and data are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations

N/A
● Remote Operations

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 887

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Using the MAE-Deployment:

NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 888

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iv. After the reconfiguration is complete, set the eNodeB maintenance

mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.10.2.4 Engineering Verification

This section describes how to verify whether pRRU-aggregation cells are
successfully combined.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If a cell-related alarm is reported, clear it according to instructions in 3900 & 5900
Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command to check whether Cell instance state is Normal.
If Cell instance state is Uninstall, check cell configuration data, cell reference
signal power, or hardware based on the value of Reason for latest state change
in the command output.
Step 3 Run the LST EUSECTOREQMID2GROUP command to check whether the values of
Sector Equipment Group ID and Sector equipment ID are consistent with the
configuration data.

----End

1.10.2.5 Engineering Rollback

If the reconfiguration fails, it can be rolled back to the original configuration.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 889

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful according to instructions in 1.10.2.4

Engineering Verification.

----End

1.10.3 Splitting a pRRU-Aggregation Cell

This section describes how to split a pRRU-aggregation cell.

1.10.3.1 Scheme Overview

This section describes the application scenario, reconfiguration impact, topology
change, and the reconfiguration scheme of splitting a pRRU-aggregation cell.

Application Scenario
With the population increases in office buildings, subways, residential
communities, shopping malls, traffic volumes in these areas grow rapidly. pRRU-
aggregation cell splitting increases the number of carriers, improving the system
capacity.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 890

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Reconfiguration Impact
A cell must be deactivated during cell splitting, which causes service interruption
for the cell.

Topology Change
Use adding a BBP to split a pRRU-aggregation cell as an example. Cell 2 is served
by the BBP installed in slot 3. Figure 1-172 and Figure 1-173 show the topologies
before and after splitting a pRRU-aggregation cell.

Figure 1-172 Topologies before and after splitting a pRRU-aggregation cell (intra-
RHUB networking)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 891

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 892

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-173 Topologies before and after splitting a pRRU-aggregation cell (inter-
RHUB networking)

Reconfiguration Scheme
The reconfiguration procedure is as follows:
1. Deactivate the cell.
2. (Optional) Add BBPs, CPRI connections, and baseband equipment if the BBPs
are insufficient.
3. Delete the sector equipment ID that is involved in cell splitting from the
sector equipment group.
4. Add a cell with MultiRruCellMode set to
MPRU_AGGREGATION(MPRU_AGGREGATION).
5. Add a sector equipment group for the cell. Add a sector equipment group for
the newly added cell based on the target network requirements. Bind the
sector equipment group to the newly added BBP.
6. Change the reference signal power of the cell.
7. Add a cell operator.
8. Activate the cells.
Figure 1-174 shows the procedure for splitting a pRRU-aggregation cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 893

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-174 Procedure for splitting a pRRU-aggregation cell

1.10.3.2 Engineering Preparation

This section describes the engineering preparation for splitting a pRRU-
aggregation cell, including information collection and preparation of hardware,
software, license files, security certificates, and data. It also provides an example
of MML configuration scripts.

Information Collection
Table 1-299 describes the information to be collected before splitting a pRRU-
aggregation cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 894

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-299 Information collection

Information Description

Cell information ● Basic information about the cell to be added,

including mode, Flag of Multi-RRU Cell, and Mode
of Multi-RRU Cell.
● TX and RX mode. In FDD scenarios, pRRU-
aggregation cells support 1T1R or 2T2R mode. In
TDD scenarios, pRRU-aggregation cells support only
2T2R mode.

BBP type ● Type of the BBP, such as LBBPc and LBBPd.

● BBP working mode. pRRU-aggregation cells support
FDD or TDD.

Sector equipment Value of the Sector Equipment Group ID and Sector

group equipment ID parameters in the EuSectorEqmGroup
MO.

Baseband equipment BBP information of each sector equipment group.

Reference signal pRRU reference signal power.

power

Hardware Preparation
Table 1-300 describes the hardware to be prepared for splitting a pRRU-
aggregation cell.

Table 1-300 Hardware to be prepared

If... Then...

BBPs are insufficient Add required BBPs.

Software Preparation
N/A

License File Preparation

Prepare a new license file if the currently used license cannot meet requirements.
Table 1-301 describes the license control items to be prepared.

Table 1-301 License control items to be prepared (1)

License Control Item Description

Cell License(per Cell) Controls the number of cells.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 895

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

License Control Item Description

Carrier Controls the cell bandwidth. Each RRU serves one cell.
Bandwidth(per
5MHz)

Resource Block(per Controls RBs.

RB)

BB Receive Controls the baseband receive channel.

Channel(per
Channel)

RF Transmit Controls the RF transmit channel.

Channel(per
Channel)

Table 1-302 describes the license control items to be prepared based on network
requirements.

Table 1-302 License control items to be prepared (2)

License Control Item Description

Intra-BBU Baseband Controls the intra-BBU baseband sharing per cell.

Sharing (2T)

CPRI Controls the CPRI compression.

Compression(per
Cell)

Security Certificate Preparation

N/A

Data Preparation
Prepare data listed in the following table.

Table 1-303 Data preparation for splitting a pRRU-aggregation cell

SN Oper MO Configuration Reference
ation

1 Deac Cell -
tivat
e

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 896

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Oper MO Configuration Reference

ation

2 Add RU (using MML

commands)/BBP (using the
MAE-Deployment)

3 Modi EuSectorEqmGroup Delete the sector equipment ID

fy that is involved in cell splitting
from the sector equipment
group.

4 Add Cell Add the Cell MO with

MultiRruCellMode set to
MPRU_AGGREGATION(MPRU
_AGGREGATION) and
TxRxMode set to 2T2R.

5 Add EuSectorEqmGroup Add sector equipment groups

based on network
requirements. Configure the
sector equipment of pRRUs
that serve one cell in the same
sector equipment group.

6 Modi PDSCHCfg Set ReferenceSignalPwr to,

fy for example, -81 (unit: 0.1
dBm).

7 Add CellOp -

8 Activ Cell
ate

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario-specific template being "Splitting a pRRU-Aggregation
Cell"): For details, see the interactive operation guide 1.11.2 Using the Batch
Reconfiguration Mode of the MAE-Deployment to Prepare Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 897

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

If the current license cannot meet the requirements, load a new license file. If the
current license meets the requirements, directly split pRRU-aggregation cells.
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/", FN="
LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN=" LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="**********";
/*Deactivating the cell*/
DEA CELL: LocalCellId=1;
/*(FDD) Adding a BBP in FDD*/ ADD BRD: SN=3, BT=LBBP, WM=FDD;
/*(TDD) Adding a BBP in TDD*/ ADD BRD: SN=3, BT=LBBP, WM=TDD;
/*Adding baseband equipment in TDD*/ ADD BASEBANDEQM:BASEBANDEQMID=3,
BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL,SN1=3;
/*Deleting sector equipment that is involved in cell splitting from the sector equipment group*/
RMV EUSECTOREQMID2GROUP:LOCALCELLID=1,SECTOREQMGROUPID=1, SECTOREQMID=5;
RMV EUSECTOREQMID2GROUP:LOCALCELLID=1,SECTOREQMGROUPID=1, SECTOREQMID=6;
RMV EUSECTOREQMID2GROUP:LOCALCELLID=1,SECTOREQMGROUPID=1, SECTOREQMID=7;
RMV EUSECTOREQMID2GROUP:LOCALCELLID=1,SECTOREQMGROUPID=1, SECTOREQMID=8;
/*Adding a cell with MultiRruCellFlag set to BOOLEAN_TRUE and MultiRruCellMode set to
MPRU_AGGREGATION in FDD*/
ADD CELL: LocalCellId=2, CellName="2", FreqBand=1, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=500,
UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=2, PhyCellId=2, FddTddInd=CELL_FDD,
RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION, CPRICompression=NORMAL_COMPRESSION, TxRxMode=2T2R;
/*Adding a cell with MultiRruCellFlag set to BOOLEAN_TRUE and MultiRruCellMode set to
MPRU_AGGREGATION in TDD*/
ADD CELL: LocalCellId=2, CellName="2", FreqBand=41, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=40240,
UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=2, PhyCellId=2, FddTddInd=CELL_TDD,
SubframeAssignment=SA2, SpecialSubframePatterns=SSP5, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION, CPRICompression=NORMAL_COMPRESSION, TxRxMode=2T2R;
/*Specifying that cell 2 is served by the BBP installed in slot 3 and adding sector equipment to the sector
equipment group after splitting*/
ADD EUSECTOREQMGROUP:LOCALCELLID=2,SECTOREQMGROUPID=2;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=2,SECTOREQMGROUPID=2, SECTOREQMID=5;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=2,SECTOREQMGROUPID=2, SECTOREQMID=6;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=2,SECTOREQMGROUPID=2, SECTOREQMID=7;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=2,SECTOREQMGROUPID=2, SECTOREQMID=8;
/*Changing the reference signal power of the cell served by pRRUs*/
MOD PDSCHCFG: LocalCellId=2, ReferenceSignalPwr=-81;
/*Adding operator information for the cell*/
ADD CELLOP: LocalCellId=2, TrackingAreaId=0;
/*Activating the cells*/
ACT CELL: LocalCellId=1;
ACT CELL: LocalCellId=2;

1.10.3.3 Engineering Implementation

This section describes the engineering implementation of splitting a pRRU-
aggregation cell, including local and remote operations.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 898

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Prerequisites
Related information, license files, and data are ready.
● Each BBP supports a maximum of six pRRU-aggregation cells.
● When the optical port on an LBBPd connects to an RHUB, cells that are served
by another LBBPd or LBBPc can be aggregated to the LBBPd through the
backplane.
● If multiple LBBPd boards connect to an RHUB over optical ports and LBBPc
boards are installed, an LBBPc can connect to only one LBBPd for data
transmission to serve cells.
● When an LBBPc connects to an RHUB over the optical port, cells cannot be
established on LBBPd or other LBBPc boards.
● An RHUB supports a maximum of four cells.
● The maximum rate on a single optical fiber reaches 9.8 Gbit/s.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local Operations
a. (Optional) Insert BBPs into the subracks.
NOTE

This step is performed only when more BBPs are required.

● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 899

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

For example: INS LICENSE: DIR="ftproot/",

FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.10.3.4 Engineering Verification

This section describes how to verify whether a pRRU-aggregation cell is
successfully split.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If a cell-related alarm is reported, clear it according to instructions in 3900 & 5900
Series Base Station Alarm Reference.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 900

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 2 Run the DSP CELL command to check whether Cell instance state is Normal.
If Cell instance state is Uninstall, check cell configuration data, cell reference
signal power, or hardware based on the value of Reason for latest state change
in the command output.
Step 3 Run the LST CELL command to check whether the values of Flag of Multi-RRU
Cell, Mode of Multi-RRU Cell, and Cell transmission and reception mode are
consistent with the configuration data.

----End

1.10.3.5 Engineering Rollback

If the reconfiguration fails, it can be rolled back to the original configuration.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 901

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful according to instructions in 1.10.3.4

Engineering Verification.

----End

1.10.4 Reconstructing pRRU-Aggregation Cells to a Pico SFN

Cell
This section describes how to reconstruct pRRU-aggregation cells to a pico SFN
cell.

1.10.4.1 Scheme Overview

This section describes the application scenario, reconfiguration impact, topology
change, and reconfiguration scheme of reconstructing pRRU-aggregation cells to a
pico SFN cell.

Application Scenario
Inter-cell interference occurs if there are multiple pRRU-aggregation cells. If they
are reconstructed to a pico SFN cell, their originally interfering signals turn into
multi-path signals in one cell. This increases SINRs at the cell edge, reduces the
proportion of low SINRs, and improves user experience at the cell edge.

Reconfiguration Impact
When pRRU-aggregation cells are reconstructed to a pico SFN cell, the cells must
be deactivated, which causes service interruption for the cells.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 902

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Use the reconstruction of pRRU-aggregation cells that are served by multiple
RHUBs to a pico SFN cell as an example. Figure 1-175 shows the topologies
before and after the reconfiguration.

Figure 1-175 Topologies before and after the reconfiguration

Reconfiguration Scheme
Reconfigure as follows:
● Deactivate cells to be reconstructed.
● Delete redundant cells except the cell that is to be used as the pico SFN cell
after reconstruction. The sector equipment groups of redundant cells are
automatically deleted when the cells are deleted.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 903

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Add a cell, and use the cell as the pico SFN cell. Set MultiRruCellMode to
MPRU_AGGREGATION(MPRU_AGGREGATION). If an existing cell is to be
used as the pico SFN cell, you do not need to add a cell.
● Add sector equipment groups for the cell.
● Change the reference signal power of the cell.
● Activate the cell.
Figure 1-176 shows the procedure for reconstructing pRRU-aggregation cells to a
pico SFN cell.

Figure 1-176 Procedure for reconstructing pRRU-aggregation cells to a pico SFN

cell

1.10.4.2 Engineering Preparation

This section describes the engineering preparation for reconstructing pRRU-
aggregation cells to a pico SFN cell, including information collection and
preparation of hardware, software, license files, security certificates, and data. It
also provides an example of MML configuration scripts.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 904

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Collection
Table 1-304 describes the information to be collected before reconstructing pRRU-
aggregation cells to a pico SFN cell.

Table 1-304 Information collection

Information Description

Cell information ● Basic information about the cell, including mode and
settings of Flag of Multi-RRU Cell and Mode of
Multi-RRU Cell
● TX and RX mode. In an FDD or NB-IoT network,
pRRU-aggregation cells support 1T1R or 2T2R mode.
In a TDD network, pRRU-aggregation cells support
only 2T2R mode.

Sector equipment Sector equipment group IDs and sector equipment IDs
group for the sector equipment groups

Reference signal pRRU reference signal power

power

Hardware Preparation
None

Software Preparation
N/A

License File Preparation

Prepare a new license file if the currently used license cannot meet requirements.
When pRRU-aggregation cells are reconstructed to form a pico SFN cell, SFN-
related license control items are required. Table 1-305 describes the license
control items to be prepared.

Table 1-305 Licenses to be prepared

License Control Item Description

SFN(per Cell) Controls the SFN.

Security Certificate Preparation

N/A

Data Preparation
Prepare data listed in the following table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 905

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-306 Data preparation for reconstructing pRRU-aggregation cells to a pico

SFN cell

SN Oper MO Configuration Reference

ation

1 Deac Cell -
tivat
e

2 Delet Cell Delete redundant cells based

e on the target network
topology.

3 Add Cell If there is no target pico SFN

cell, add a cell with
MultiRruCellMode set to
MPRU_AGGREGATION(MPRU
_AGGREGATION) and
TxRxMode set to 1T1R or
2T2R.

4 Add EuSectorEqmGroup Add sector equipment groups

and bind them to the pico SFN
cell based on the target
network topology.

5 Modi PDSCHCfg Set ReferenceSignalPwr to,

fy for example, -81 (unit: 0.1
dBm).

6 Activ Cell -
ate

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Reconstructing pRRU-Aggregation Cells to a Pico
SFN Cell"): For details, see the interactive operation guide 1.11.2 Using the
Batch Reconfiguration Mode of the MAE-Deployment to Prepare Data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 906

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

If the current license cannot meet the requirements, load a new license file. If the
current license meets the requirements, directly reconstruct pRRU-aggregation
cells to a pico SFN cell.
/*Exporting the license file in use and saving it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/", FN="
LIC_LTE_ON.xml";
/*Importing a new license file from the ftproot folder on the MAE server*/
INS LICENSE: DIR="ftproot/", FN=" LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********";
/*Deactivating the cells*/
DEA CELL: LocalCellId=0;
DEA CELL: LocalCellId=1;
DEA CELL: LocalCellId=2;
/*Removing the cells*/
RMV CELL:LOCALCELLID=0;
RMV CELL:LOCALCELLID=1;
RMV CELL:LOCALCELLID=2;
/*Adding a cell with MultiRruCellFlag set to BOOLEAN_TRUE and MultiRruCellMode set to
MPRU_AGGREGATION in FDD*/
ADD CELL: LocalCellId=3, CellName="3", FreqBand=1, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=500,
UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=3, PhyCellId=3, FddTddInd=CELL_FDD,
RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION, CPRICompression=NORMAL_COMPRESSION, TxRxMode=2T2R;
/*Adding a cell with MultiRruCellFlag set to BOOLEAN_TRUE and MultiRruCellMode set to
MPRU_AGGREGATION in NB-IoT*/
ADD CELL: LocalCellId=3, CellName="3", NbCellFlag=TRUE, FreqBand=1, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=500, UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=3, PhyCellId=3,
FddTddInd=CELL_FDD, RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION, CPRICompression=NORMAL_COMPRESSION, TxRxMode=2T2R;
/*Adding a cell with MultiRruCellFlag set to BOOLEAN_TRUE and MultiRruCellMode set to
MPRU_AGGREGATION in TDD*/
ADD CELL: LocalCellId=3, CellName="3", FreqBand=41, UlEarfcnCfgInd=NOT_CFG, DlEarfcn=40240,
UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=3, PhyCellId=3, FddTddInd=CELL_TDD,
SubframeAssignment=SA2, SpecialSubframePatterns=SSP5, RootSequenceIdx=0,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION, CPRICompression=NORMAL_COMPRESSION, TxRxMode=2T2R;
/*Adding sector equipment groups and adding sector equipment to the sector equipment groups*/
ADD EUSECTOREQMGROUP:LOCALCELLID=3,SECTOREQMGROUPID=0;
ADD EUSECTOREQMGROUP:LOCALCELLID=3,SECTOREQMGROUPID=1;
ADD EUSECTOREQMGROUP:LOCALCELLID=3,SECTOREQMGROUPID=2;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=0, SECTOREQMID=0;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=0, SECTOREQMID=1;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=0, SECTOREQMID=2;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=0, SECTOREQMID=3;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=0, SECTOREQMID=4;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=0, SECTOREQMID=5;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=0, SECTOREQMID=6;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=0, SECTOREQMID=7;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=1, SECTOREQMID=8;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=1, SECTOREQMID=9;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=1, SECTOREQMID=10;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=1, SECTOREQMID=11;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=2, SECTOREQMID=12;
ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=2, SECTOREQMID=13;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 907

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=2, SECTOREQMID=14;

ADD EUSECTOREQMID2GROUP:LOCALCELLID=3,SECTOREQMGROUPID=2, SECTOREQMID=15;
/*Changing the reference signal power of the cell served by pRRUs*/
MOD PDSCHCFG: LocalCellId=3, ReferenceSignalPwr=-81;
/*Activating the cell*/
ACT CELL: LocalCellId=3;

1.10.4.3 Engineering Implementation

This section describes the engineering implementation of reconstructing pRRU-
aggregation cells to a pico SFN cell, including local and remote operations.

Prerequisites
Related information, license files, and data are ready.

● In FDD: A maximum of six pRRU-aggregation cells can be combined to form

one pico SFN cell. In TDD: A maximum of seven pRRU-aggregation cells can
be combined to form one pico SFN cell.
● In FDD: A primary LBBPc, LBBPd1, or LBBPd2 supports a maximum of three
pRRU-aggregation cells that are combined to form one pico SFN cell. In TDD:
A primary LBBPc supports a maximum of three pRRU-aggregation cells that
are combined to form one pico SFN cell.
● In FDD: A primary LBBPd3 supports a maximum of six pRRU-aggregation cells
that are combined to form one pico SFN cell. In TDD: A primary LBBPd
supports a maximum of seven pRRU-aggregation cells that are combined to
form one pico SFN cell.
● In FDD: pRRU-aggregation cells with a bandwidth of 5 MHz, 10 MHz, 15
MHz, or 20 MHz can be combined to form one pico SFN cell. In TDD: pRRU-
aggregation cells with a bandwidth of 20 MHz can be combined to form one
pico SFN cell while those with a bandwidth of 10 MHz cannot be combined to
form one pico SFN cell.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local operations
a. Install the BBPs in the BBU.
● Remote operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 908

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 909

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.10.4.4 Engineering Verification

This section describes how to verify whether pRRU-aggregation cells are
successfully reconstructed to a pico SFN cell.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.
If a cell-related alarm is reported, clear it according to instructions in 3900 & 5900
Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command to check whether Cell instance state is Normal.
If Cell instance state is Uninstall, check cell configuration data, cell reference
signal power, or hardware based on the value of Reason for latest state change
in the command output.
Step 3 Run the LST CELL command to check whether the values of Flag of Multi-RRU
Cell, Mode of Multi-RRU Cell, and Cell transmission and reception mode are
consistent with the configuration data.
Step 4 Run the LST EUSECTOREQMGROUP command to check whether the value of
Sector Equipment Group ID is consistent with the configuration data.
----End

1.10.4.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 910

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: DSP ROLCFGINFO: OT=BYINFO;

ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the physical connections.
Step 4 Verify that engineering rollback is successful according to instructions in 1.10.4.4
Engineering Verification.

----End

1.10.5 Adjusting pRRU Transmit Power

This section describes how to adjust pRRU transmit power.

1.10.5.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology changes for adjusting pRRU transmit power.

Application Scenario
In LampSite scenarios, indoor signal leakage and inter-cell interference are severe.
Therefore, pRRU transmit power requires adjustment to alleviate indoor signal
leakage and interference and improve the flexibility of LampSite network design
and network optimization.

Reconfiguration Impact
For pRRUs installed next to windows, signal leakage from inside to outside can be
reduced.
In the overlapping area between two cells, interference at cell edges can be
reduced.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 911

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
The network topology does not need to be adjusted; only LampSite cell
configurations need to be adjusted for pRRU transmit power adjustment.

Reconfiguration Scheme
You can adjust pRRU transmit power using the following two methods:

● Adjusting the reference signal power of a sector equipment group

– Run the DSP TXBRANCH command to query the dynamic information
about RRU/RFU transmit channels. Check Maximum Output Power of
TX Unit (Single Carrier)(0.1dBm) of each pRRU to obtain the minimum
value.
– Run the MOD EUSECTOREQMGROUP command to adjust the Reference
signal power parameter of the sector equipment group. The transmit
power corresponding to Reference signal power must be smaller than
the minimum value of Maximum Output Power of TX Unit (Single
Carrier)(0.1dBm) among all pRRUs indicated in the DSP TXBRANCH
command output.
– Activate the cell.
NOTE

In LampSite scenarios, you can adjust sector equipment group power. One sector
equipment group contains a maximum of 16 pRRUs. When you adjust sector
equipment group power, transmit power of pRRUs in the same sector equipment
group are adjusted to the same value.
Calculate the corresponding transmit power based on Reference signal power of the
sector equipment. For details, see Maximum Transmit Power of a Cell in Cell
Management Feature Parameter Description.
Figure 1-177 shows the process of adjusting the transmit power of pRRUs in
a sector equipment group in batches.

Figure 1-177 Process of adjusting the transmit power of pRRUs in a sector

equipment group in batches

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 912

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Adjusting the transmit power of a pRRU by changing the reference signal

power of the sector equipment in a cell:
– Query the Reference signal power parameter value specified in the
PDSCHCfg MO.
– Add an eUCellSectorEqm MO with the Reference signal power
parameter specified. The value of the Reference signal power parameter
must be less than or equal to that of Reference signal power in the
PDSCHCfg MO.
– Activate the cell.
NOTE

Before the adjustment, check whether all sector equipment has been added to the cell
sector equipment group. If no, add sector equipment to the cell sector equipment
group.
Calculate the corresponding transmit power based on Reference signal power of the
sector equipment. For details, see Maximum Transmit Power of a Cell in Cell
Management Feature Parameter Description.
In LampSite scenarios, the ADD EUCELLSECTOREQM or MOD EUCELLSECTOREQM
command cannot be used to bind baseband equipment to a cell. Even if they are
executed, the configurations do not take effect. In this case, only the ADD
EUSECTOREQMGROUP or MOD EUSECTOREQMGROUP command can be used.
Figure 1-178 shows the process of adjusting the transmit power of a pRRU by
configuring the sector equipment of a cell.

Figure 1-178 Process of adjusting the transmit power of a pRRU by

configuring the sector equipment of a cell

1.10.5.2 Engineering Preparation

This section describes the engineering preparation for adjusting pRRU transmit
power, including information collection and preparation of hardware, software,
license files, certificates, and data. It also describes the data preparation mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 913

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Collection
Table 1-307 describes the information to be collected before adjusting pRRU
transmit power.

Table 1-307 Information collection

Information Description

Cell information Basic information about a cell, including the cell

bandwidth and settings of Cell transmission and
reception mode, Flag of Multi-RRU Cell, and Mode of
Multi-RRU Cell

Sector equipment Sector Equipment Group ID in the EuSectorEqmGroup

group MO

Sector equipment in Sector Equipment ID in the eUCellSectorEqm MO

a sector equipment
group

Reference signal Reference signal power in the PDSCHCfg MO.

power

Maximum transmit You can run the DSP TXBRANCH command to query
power supported by the dynamic information about RRU/RFU transmit
each pRRU channels. Then, check Maximum Output Power of TX
Unit (Single Carrier)(0.1dBm) of each pRRU and use
the minimum value.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

pRRU transmit power adjustment is performed in an existing pRRU-aggregation
cell. No additional licenses are required.

Security Certificate Preparation

N/A

Data Preparation
● When you adjust the transmit power of pRRUs by using the
EuSectorEqmGroup MO, prepare data by performing the following
operations:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 914

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

a. Run the DSP TXBRANCH command. Check Maximum Output Power of

TX Unit (Single Carrier)(0.1dBm) of each pRRU to obtain the minimum
value.
b. Run the MOD EUSECTOREQMGROUP command to reconfigure
Reference signal power. The transmit power corresponding to
Reference signal power must be smaller than the minimum value of
Maximum Output Power of TX Unit (Single Carrier)(0.1dBm) among
all pRRUs indicated in the DSP TXBRANCH command output.
c. Activate the cell.
● When you adjust the transmit power of a pRRU by using the
eUCellSectorEqm MO, prepare data by performing the following operations:
a. Query the Reference signal power parameter value specified in the
PDSCHCfg MO.
b. Add an eUCellSectorEqm MO. The reference signal power in the
PDSCHCfg MO is used by the pRRU. Set Reference signal power to the
target value (less than or equal to the reference signal power specified in
the PDSCHCfg MO).
c. Activate the cell.

Data Preparation Mode

Data preparation can be performed using the MAE-Deployment or MML
commands. You are advised to use the batch reconfiguration mode of the MAE-
Deployment to reconfigure base stations in batches and use the MAE-Deployment
GUI to reconfigure a single base station. The three data preparation modes are
described as follows:

● Using the batch reconfiguration mode of the MAE-Deployment (with the

name of the scenario being "Adjusting pRRU Transmit Power"): For details,
see the interactive operation guide 1.11.2 Using the Batch Reconfiguration
Mode of the MAE-Deployment to Prepare Data.
● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.
● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

MML Configuration Script Example

Adjusting the Transmit Power of pRRUs in a Sector Equipment Group in
Batches

For example, the cell bandwidth is 20 MHz and you need to adjust the pRRU
transmit power of sector equipment group 1 in a pRRU-aggregation cell.
/*Querying the maximum transmit power supported by each pRRU in the sector equipment group. Assume
that the maximum transmit power is 200 (unit: 0.1 dBm).
DSP TXBRANCH:;
/*Setting the reference signal power of the sector equipment group*/
MOD EUSECTOREQMGROUP: LocalCellId=0, SectorEqmGroupId=1, ReferenceSignalPwr=-108;
/*Activating the cell*/
ACT CELL: LocalCellId=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 915

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Adjusting the Transmit Power of a pRRU by Using the Sector Equipment of a

Cell

Adjust the transmit power of a pRRU to a valid value. For example, the cell
bandwidth is 20 MHz and you need to adjust the transmit power of pRRU 61 in a
pRRU-aggregation cell.
/*Querying the reference signal power in the PDSCHCFG MO. Assume that the reference signal power is -98
(unit: 0.1 dBm)./
LST PDSCHCFG: LocalCellId=0;
/*Adding sector equipment to the cell and setting the reference signal power*/
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=61, ReferenceSignalPwr=-108;
/*Activating the cell*/
ACT CELL: LocalCellId=0;

Adjust the transmit power of all pRRUs to valid values. For example, the cell
bandwidth is 20 MHz and you need to adjust the transmit power of pRRUs 61 to
68 in a pRRU-aggregation cell.
/*Querying the reference signal power in the PDSCH configuration. Assume that the reference signal power
is -98 (unit: 0.1 dBm).
LST PDSCHCFG: LocalCellId=0;
/*Adding sector equipment to the cell and setting the reference signal power*/
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=61, ReferenceSignalPwr=-108;
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=62, ReferenceSignalPwr=-108;
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=63, ReferenceSignalPwr=-118;
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=64, ReferenceSignalPwr=-118;
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=65, ReferenceSignalPwr=-128;
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=66, ReferenceSignalPwr=-128;
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=67, ReferenceSignalPwr=-138;
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=68, ReferenceSignalPwr=-138;
/*Activating the cell*/
ACT CELL: LocalCellId=0;

1.10.5.3 Engineering Implementation

This section describes the engineering implementation of adjusting pRRU transmit
power, including local and remote operations.

Prerequisites
The pRRUs whose transmit power requires adjustment have been added to the
pRRU-aggregation cell.

Data required for adjusting pRRU transmit power is ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local operations

N/A

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 916

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Remote operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
iii. Import a new license file.
Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 917

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

1.10.5.4 Engineering Verification

This section describes how to verify that pRRU transmit power is correctly
adjusted.

Procedure
● Adjusting the pRRU transmit power by using a sector equipment group
a. Run the LST EUSECTOREQMGROUP command to verify that the value of
Reference signal power of the sector equipment group is consistent with
the configuration data. Calculate the corresponding transmit power based
on Reference signal power of the sector equipment. For details, see
Maximum Transmit Power of a Cell in Cell Management Feature
Parameter Description. Calculate the pRRU transmit power based on
Reference signal power. The calculated value is the expected pRRU
transmit power.
b. On the MAE-Access, choose Monitor > Signaling Trace > Signaling
Trace Management. In the navigation tree, select Trace Type > Base
Station Device and Transport > Device Monitoring, and double-click
RRU/RFU/BRU Output Power Monitoring. In the displayed dialog box,
select an NE and specify the cabinet number, subrack number, and slot
number of the pRRU to start pRRU transmit power monitoring.
c. Enable a UE at the cell center to perform downlink FTP services, and
check the pRRU transmit power.

▪ If the pRRU transmit power does not equal the expected value, check
whether the downlink cell throughput reaches the peak value. If the
downlink throughput does not reach the peak value, increase the
traffic volume or use more UEs to perform downlink FTP services.

▪ If the downlink cell throughput reaches the peak value but the pRRU
transmit power is not as expected, check whether the configuration
in the configuration data file is correct.
○ If the configuration is incorrect, modify the configuration data
file and perform the operations in Engineering Implementation
again to deliver the data to the base station and activate it.
○ If the configuration is correct, an error has occurred during the
configuration data download or activation. In this situation,
contact Huawei technical support or dial the Huawei technical
support hotline.
● Adjusting the transmit power of a pRRU by using the sector equipment of a
cell

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 918

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

a. Run the LST EUCELLSECTOREQM command to check whether the

Reference signal power parameter value of the pRRU is correctly
configured. Calculate the expected pRRU transmit power based on the
Reference signal power parameter value. Calculate the corresponding
transmit power based on Reference signal power of the sector
equipment. For details, see Maximum Transmit Power of a Cell in Cell
Management Feature Parameter Description.
b. On the MAE-Access, choose Monitor > Signaling Trace > Signaling
Trace Management. In the navigation tree, select Trace Type > Base
Station Device and Transport > Device Monitoring, and double-click
RRU/RFU/BRU Output Power Monitoring. In the displayed dialog box,
select an NE and specify the cabinet number, subrack number, and slot
number of the pRRU to start pRRU transmit power monitoring.
c. Enable a UE at the cell center to perform downlink FTP services, and
check the pRRU transmit power.

▪ If the pRRU transmit power does not equal the expected value, check
whether the downlink cell throughput reaches the peak value. If the
downlink throughput does not reach the peak value, increase the
traffic volume or use more UEs to perform downlink FTP services.

▪ If the downlink cell throughput reaches the peak value but the pRRU
transmit power does not equal the expected value, check whether
the configuration is correct.
○ If the configuration is incorrect, modify the configuration data
file and perform the operations in Engineering Implementation
again to deliver the data to the base station and activate it.
○ If the configuration is correct, an error has occurred during the
configuration data download or activation. In this situation,
contact Huawei technical support or dial the Huawei technical
support hotline.
● Adjusting the transmit power of all pRRUs by using the sector equipment of a
cell
a. Run the LST EUCELLSECTOREQM command to check whether the
Reference signal power parameter value of the pRRU is correctly
configured. Calculate the expected pRRU transmit power based on the
Reference signal power parameter value. Calculate the corresponding
transmit power based on Reference signal power of the sector
equipment. For details, see Maximum Transmit Power of a Cell in Cell
Management Feature Parameter Description.
b. Run the DSP CELL command to check the Maximum transmit
power(0.1dBm) parameter value.
When the Reference signal power parameters of all pRRUs are set to
valid values, the Maximum transmit power(0.1dBm) parameter
indicates the maximum transmit power of these pRRUs.
c. On the MAE-Access, choose Monitor > Signaling Trace > Signaling
Trace Management. In the navigation tree, select Trace Type > Base
Station Device and Transport > Device Monitoring, and double-click
RRU/RFU/BRU Output Power Monitoring. In the displayed dialog box,
select an NE and specify the cabinet number, subrack number, and slot
number of the pRRU to start pRRU transmit power monitoring.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 919

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

d. Enable a UE at the cell center to perform downlink FTP services, and

check the pRRU transmit power.

▪ If the pRRU transmit power does not equal the expected value, check
whether the downlink cell throughput reaches the peak value. If the
downlink throughput does not reach the peak value, increase the
traffic volume or use more UEs to perform downlink FTP services.

▪ If the downlink cell throughput reaches the peak value but the pRRU
transmit power is not as expected, check whether the configuration
in the configuration data file is correct.
○ If the configuration is incorrect, modify the configuration data
file and perform the operations in Engineering Implementation
again to deliver the data to the base station and activate it.
○ If the configuration is correct, an error has occurred during the
configuration data download or activation. In this situation,
contact Huawei technical support or dial the Huawei technical
support hotline.
----End

1.10.5.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 920

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Restore the physical connections.

Step 4 Verify that engineering rollback is successful according to instructions in 1.10.5.4

Engineering Verification.

----End

1.10.6 Sharing BBUs Between Macro and LampSite Base

Stations
This section describes how to share BBUs between macro and LampSite base
stations.

1.10.6.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology changes for sharing BBUs between macro
and LampSite base stations.

Application Scenario
BBUs can be shared between macro and LampSite base stations and you can
reuse an existing macro base station or deploy a new macro base station.

Reconfiguration Impact
No impact

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 921

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

● This section describes the hardware installation and data configuration for LampSite base
stations. The hardware to be added for a LampSite base station includes MPTs, BBPs, RHUBs,
and pRRUs. Data configuration for a LampSite base station is dedicated to the added
hardware. Neither hardware installation nor data configuration affects services of the macro
base station.
● In the scenario of sharing a BBU between a macro and a LampSite base station, the software
package in use must be a multimode_ALL software package that is applicable to both a
macro and LampSite base stations, for example, BTS3900_5900
V100R016C10SPCxxx_ALL(Software).7z.

Topology Change

Figure 1-179 Topologies before and after the reconfiguration

Reconfiguration Scheme
Figure 1-180 shows the reconfiguration procedure for sharing BBUs between
macro and LampSite base stations. Determine the reconfiguration scheme
according to the following table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 922

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-308 Information collection

If... Then...

Transmission ● Replace main control boards by referring to 1.7.1

resources are Replacing the Main Control Board When No SeGW
insufficient and more Is Deployed or 1.7.2 Replacing the Main Control
main control boards Board When an SeGW Is Deployed .
are needed (co-MPT) ● Add main control boards by referring to 1.7.6
Transmission Capacity Expansion from One LMPT
Board to LMPT + UMPT Boards (Mode 1) (TDD)
(IPv4 Transmission Only), 1.7.7 Transmission
Capacity Expansion from One LMPT Board to
LMPT + UMPT Boards (Mode 2) (TDD) (IPv4
Transmission Only), or 1.7.8 Transmission Capacity
Expansion from One UMPT Board to Two UMPT
Boards (FDD/NB-IoT) (IPv4 Transmission Only).

Signaling capacity is Add main control boards by referring to 1.7.9 Signaling

insufficient and more Capacity Expansion from One UMPT to One Primary
main control boards UMPT + One Extension UMPT/LMPT (IPv4
are needed (co-MPT) Transmission Only) or 1.7.10 Signaling Capacity
Expansion from One LMPT to One Primary UMPT +
One Extension LMPT (IPv4 Transmission Only).

More main control Configure the new MPTs and the related devices as well
boards are needed as the related transmission and radio data, by referring
(separate-MPT) to 3900 & 5900 Series Base Station Initial Configuration
Guide.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 923

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-180 Procedure for configuration to share BBUs between macro and
LampSite base stations

1.10.6.2 Engineering Preparation

This section describes the engineering preparation for sharing BBUs between
macro and LampSite base stations, including information collection and
preparation of hardware, software, license files, certificates, and data. It also
describes the data preparation mode.

Information Collection
Table 1-309 describes the information to be collected before the reconfiguration.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 924

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-309 Information collection

Information Description

Cell information ● Basic information about the cell to be added

● TX and RX mode. In an FDD or NB-IoT network,
pRRU-aggregation cells support 1T1R or 2T2R mode.
In a TDD network, pRRU-aggregation cells support
only 2T2R mode.

BBP type ● The type of the BBPs. For example, the UBBP.
● LBBP working mode. pRRU-aggregation cells support
TDD, NBIOT, or FDD.
● UBBP baseband work standard. pRRU-aggregation
cells support LTE_TDD(LTE TDD), NBIOT, or
LTE_FDD(LTE FDD).

RF unit ● Types of newly added RF units. pRRU-aggregation

cells support only the MPMU.
● Connections between pRRUs and RHUBs

Network topology Network topology of pRRU-aggregation cellsa

Sector equipment Value of the Sector Equipment Group ID and Sector

group equipment ID parameters in the EuSectorEqmGroup
MO

Reference signal pRRU reference signal power

power

a: pRRU-aggregation cells support only the chain topology. Set Topo Position to
BRANCH(BRANCH).

Hardware Preparation
Table 1-310 shows the hardware to be prepared before the reconfiguration.

Table 1-310 Hardware to be prepared

Added Hardware Description

BBP ● If no baseband equipment is specified for LampSite

cells, the eNodeB automatically allocates different
BBPs to LampSite cells and macro cells when
allocating baseband resources.
● If you configure LampSite cells and macro cells on
the same BBP, establishment of the type of cells
established later fails.

MPT If baseband resources are insufficient, add MPTs. For

details, see 1.7 Device Data Reconfigurations.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 925

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Added Hardware Description

RHUBs, pRRUs, For the maximum allowed number of RHUBs and

related cables, and pRRUs, see LampSite Solution Description.
optical modules

Software Preparation
N/A

License File Preparation

N/A

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Table 1-311 Data preparation for sharing BBUs between macro and LampSite
base stations

SN Oper MO Configuration Reference

ation

1 Add RU -

2 Add MPT

3 Add RRUCHAIN

4 Add RHUB

5 Modif RRU
y

6 Add SECTOR

7 Add SectorEqm

8 Add Cell Set the MultiRruCellFlag parameter to

BOOLEAN_TRUE(True), and the
MultiRruCellMode parameter to
MPRU_AGGREGATION(MPRU_AGGREG
ATION). In the LampSite solution,
MultiRruCellMode must be set to
MPRU_AGGREGATION(MPRU_AGGREG
ATION).

9 Add CellOp -

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 926

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Oper MO Configuration Reference

ation

10 Modif PDSCHCfg Set the reference signal power for the

y cell, for example, to -81 (unit: 0.1 dBm).

11 Add EuSectorEqmGroup Add sector equipment groups based on

the target network topology. Add the
sector equipment of pRRUs that serve
one cell to the same sector equipment
group. a

12 Activa Cell -
te

a: In the LampSite solution, the mapping between SectorEqm and Cell must be
specified using the EuSectorEqmGroup MO.

Data Preparation Mode

Using MML commands: Prepare MML configuration scripts based on the preceding
data preparation procedure and the following MML configuration script examples.

MML Configuration Script Example

The following example provides configuration scripts to add macro and LTE
LampSite cells. The LBBP is used as an example.
/*Adding BBPs*/
ADD BRD: SN=0, BT=LBBP;/* for macro cells
ADD BRD: SN=2, BT=LBBP;/* for LTE LampSite cells
/*Binding a BBP to the cells*/
/*Binding the BBP to the macro cell*/
ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=DEM_2_CHAN,
SN1=0;
/*Binding the BBP to the LampSite cell*/
ADD BASEBANDEQM: BASEBANDEQMID=2, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=DEM_2_CHAN,
SN1=2;
/*Adding RRU chains*/
/*Adding an RRU chain for the macro cell*/
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=0, HPN=0;
/*Adding an RRU chain for the RHUB*/
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, AT=PEERPORT, HSRN=0, HSN=3, HPN=0;
/*Implementing four-level RHUB cascading for the LampSite cell*/
ADD RHUB: CN=0, SRN=61, RCN=1, PS=0, RN="RHUB1";
ADD RHUB: CN=0, SRN=62, RCN=1, PS=1, RN="RHUB2";
ADD RHUB: CN=0, SRN=63, RCN=1, PS=2, RN="RHUB3";
ADD RHUB: CN=0, SRN=64, RCN=1, PS=3, RN="RHUB4";
/*Adding RRU chains for the pRRUs*/
ADD RRUCHAIN: RCN=21, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=61, HSN=0, HPN=0;
ADD RRUCHAIN: RCN=22, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=61, HSN=0, HPN=4;
ADD RRUCHAIN: RCN=23, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=62, HSN=0, HPN=0;
ADD RRUCHAIN: RCN=24, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=62, HSN=0, HPN=4;
ADD RRUCHAIN: RCN=25, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=63, HSN=0, HPN=0;
ADD RRUCHAIN: RCN=26, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=63, HSN=0, HPN=3;
ADD RRUCHAIN: RCN=27, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=63, HSN=0, HPN=4;
ADD RRUCHAIN: RCN=28, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=63, HSN=0, HPN=7;
ADD RRUCHAIN: RCN=29, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=64, HSN=0, HPN=0;
ADD RRUCHAIN: RCN=30, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=64, HSN=0, HPN=1;
ADD RRUCHAIN: RCN=31, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=64, HSN=0, HPN=2;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 927

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD RRUCHAIN: RCN=32, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=64, HSN=0, HPN=3;

ADD RRUCHAIN: RCN=33, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=64, HSN=0, HPN=4;
ADD RRUCHAIN: RCN=34, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=64, HSN=0, HPN=5;
ADD RRUCHAIN: RCN=35, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=64, HSN=0, HPN=6;
ADD RRUCHAIN: RCN=36, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=64, HSN=0, HPN=7;
/*Adding RRUs*/
/*Adding an RRU for the macro cell*/
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRRU, RS=LO, RN="Macro_L_RRU",
RXNUM=2, TXNUM=2;
/*Adding multiple pRRU3901 devices for the LampSite cell*/
ADD RRU: CN=0, SRN=101, SN=0, TP=BRANCH, RCN=21, PS=0, RT=MPMU, RS=UL, RN="pRRU_1",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=102, SN=0, TP=BRANCH, RCN=22, PS=0, RT=MPMU, RS=UL, RN="pRRU_2",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=103, SN=0, TP=BRANCH, RCN=23, PS=0, RT=MPMU, RS=UL, RN="pRRU_3",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=104, SN=0, TP=BRANCH, RCN=24, PS=0, RT=MPMU, RS=UL, RN="pRRU_4",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=105, SN=0, TP=BRANCH, RCN=25, PS=0, RT=MPMU, RS=UL, RN="pRRU_5",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=106, SN=0, TP=BRANCH, RCN=26, PS=0, RT=MPMU, RS=UL, RN="pRRU_6",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=107, SN=0, TP=BRANCH, RCN=27, PS=0, RT=MPMU, RS=UL, RN="pRRU_7",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=108, SN=0, TP=BRANCH, RCN=28, PS=0, RT=MPMU, RS=UL, RN="pRRU_8",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=109, SN=0, TP=BRANCH, RCN=29, PS=0, RT=MPMU, RS=UL, RN="pRRU_9",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=110, SN=0, TP=BRANCH, RCN=30, PS=0, RT=MPMU, RS=UL, RN="pRRU_10",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=111, SN=0, TP=BRANCH, RCN=31, PS=0, RT=MPMU, RS=UL, RN="pRRU_11",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=112, SN=0, TP=BRANCH, RCN=32, PS=0, RT=MPMU, RS=UL, RN="pRRU_12",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=113, SN=0, TP=BRANCH, RCN=33, PS=0, RT=MPMU, RS=UL, RN="pRRU_13",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=114, SN=0, TP=BRANCH, RCN=34, PS=0, RT=MPMU, RS=UL, RN="pRRU_14",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=115, SN=0, TP=BRANCH, RCN=35, PS=0, RT=MPMU, RS=UL, RN="pRRU_15",
RXNUM=0, TXNUM=0;
ADD RRU: CN=0, SRN=116, SN=0, TP=BRANCH, RCN=36, PS=0, RT=MPMU, RS=UL, RN="pRRU_16",
RXNUM=0, TXNUM=0;
/*Adding sectors*/
/*Adding a sector for the macro cell*/
ADD SECTOR: SECTORID=60, SECNAME="Macro_L_RRU", LOCATIONNAME="Macro", ANTNUM=2,
ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B,
CREATESECTOREQM=FALSE;
/*Adding sectors for the LampSite cell*/
ADD SECTOR: SECTORID=101, ANTNUM=4, ANT1CN=0, ANT1SRN=101, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=101, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=101, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=101, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=102, ANTNUM=4, ANT1CN=0, ANT1SRN=102, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=102, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=102, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=102, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=103, ANTNUM=4, ANT1CN=0, ANT1SRN=103, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=103, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=103, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=103, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=104, ANTNUM=4, ANT1CN=0, ANT1SRN=104, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=104, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=104, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=104, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=105, ANTNUM=4, ANT1CN=0, ANT1SRN=105, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=105, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=105, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=105, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=106, ANTNUM=4, ANT1CN=0, ANT1SRN=106, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=106, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=106, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=106, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=107, ANTNUM=4, ANT1CN=0, ANT1SRN=107, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=107, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=107, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=107, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 928

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ADD SECTOR: SECTORID=108, ANTNUM=4, ANT1CN=0, ANT1SRN=108, ANT1SN=0, ANT1N=R0A,

ANT2CN=0, ANT2SRN=108, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=108, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=108, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=109, ANTNUM=4, ANT1CN=0, ANT1SRN=109, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=109, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=109, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=109, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=110, ANTNUM=4, ANT1CN=0, ANT1SRN=110, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=110, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=110, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=110, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=111, ANTNUM=4, ANT1CN=0, ANT1SRN=111, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=111, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=111, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=111, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=112, ANTNUM=4, ANT1CN=0, ANT1SRN=112, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=112, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=112, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=112, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=113, ANTNUM=4, ANT1CN=0, ANT1SRN=113, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=113, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=113, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=113, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=114, ANTNUM=4, ANT1CN=0, ANT1SRN=114, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=114, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=114, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=114, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=115, ANTNUM=4, ANT1CN=0, ANT1SRN=115, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=115, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=115, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=115, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOR: SECTORID=116, ANTNUM=4, ANT1CN=0, ANT1SRN=116, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=116, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=116, ANT3SN=0, ANT3N=R0A,
ANT4CN=0, ANT4SRN=116, ANT4SN=0, ANT4N=R0B, CREATESECTOREQM=FALSE;
/*Adding sector equipment*/
/*Adding sector equipment for the macro cell*/
ADD SECTOREQM: SECTOREQMID=60, SECTORID=60, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=0,
ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
/*Adding sector equipment for the LampSite cell*/
/*Adding sector equipment for the LTE LampSite cell that works in 2T2R mode and is served by 1.8 GHz
pRRU3901 devices in slot 2*/
ADD SECTOREQM: SECTOREQMID=2101, SECTORID=101, ANTNUM=2, ANT1CN=0, ANT1SRN=101,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=101, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2102, SECTORID=102, ANTNUM=2, ANT1CN=0, ANT1SRN=102,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=102, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2103, SECTORID=103, ANTNUM=2, ANT1CN=0, ANT1SRN=103,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=103, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2104, SECTORID=104, ANTNUM=2, ANT1CN=0, ANT1SRN=104,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=104, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2105, SECTORID=105, ANTNUM=2, ANT1CN=0, ANT1SRN=105,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=105, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2106, SECTORID=106, ANTNUM=2, ANT1CN=0, ANT1SRN=106,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=106, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2107, SECTORID=107, ANTNUM=2, ANT1CN=0, ANT1SRN=107,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=107, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2108, SECTORID=108, ANTNUM=2, ANT1CN=0, ANT1SRN=108,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=108, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2109, SECTORID=109, ANTNUM=2, ANT1CN=0, ANT1SRN=109,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=109, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2110, SECTORID=110, ANTNUM=2, ANT1CN=0, ANT1SRN=110,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=110, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2111, SECTORID=111, ANTNUM=2, ANT1CN=0, ANT1SRN=111,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=111, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2112, SECTORID=112, ANTNUM=2, ANT1CN=0, ANT1SRN=112,

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 929

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=112, ANT2SN=2, ANT2N=R0B,

ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2113, SECTORID=113, ANTNUM=2, ANT1CN=0, ANT1SRN=113,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=113, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2114, SECTORID=114, ANTNUM=2, ANT1CN=0, ANT1SRN=114,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=114, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2115, SECTORID=115, ANTNUM=2, ANT1CN=0, ANT1SRN=115,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=115, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
ADD SECTOREQM: SECTOREQMID=2116, SECTORID=116, ANTNUM=2, ANT1CN=0, ANT1SRN=116,
ANT1SN=2, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=116, ANT2SN=2, ANT2N=R0B,
ANTTYPE2=RXTX_MODE;
/*Adding cells*/
/*Adding a 20 MHz macro LTE cell with the EARFCN 1649 in band 3*/
ADD CELL: LocalCellId=0, CellName="LampSite_96pRRU_Macro", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1649, UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=0, PhyCellId=300,
FddTddInd=CELL_FDD, RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE,
TxRxMode=2T2R;
/*Changing the RS power to 182 x 0.1 mw*/
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=182, Pb=1;
/*Adding operator information for the cell*/
ADD CELLOP: LocalCellId=0, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
/*Adding sector equipment for the cell*/
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=60;
/*Activating the macro cell*/
ACT CELL: LocalCellId=0;
/*Adding a 20 MHz LampSite LTE cell with the EARFCN 1650 in band 3*/
ADD CELL: LocalCellId=2, CellName="Lampsite_96pRRU_LTEband3", FreqBand=3, UlEarfcnCfgInd=NOT_CFG,
DlEarfcn=1650, UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, CellId=2, PhyCellId=302,
FddTddInd=CELL_FDD, RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION, CpriEthCompressionRatio=4_TO_1,
CPRICompression=NORMAL_COMPRESSION, TxRxMode=2T2R;
/*Adding operator information for the LampSite LTE cell*/
ADD CELLOP: LocalCellId=2, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
/*Changing the RS power for the LampSite LTE cell (which is usually -78 x 0.1 mw)*/
MOD PDSCHCFG: LocalCellId=2, ReferenceSignalPwr=-78;
/*Adding a sector equipment group for the LampSite LTE cell*/
ADD EUSECTOREQMGROUP: LocalCellId=2, SectorEqmGroupId=1, BaseBandEqmId=2;
/*Adding the sector equipment for the LampSite LTE cell to the sector equipment group*/
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2101;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2102;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2103;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2104;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2105;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2106;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2107;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2108;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2109;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2110;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2111;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2112;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2113;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2114;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2115;
ADD EUSECTOREQMID2GROUP: LocalCellId=2, SectorEqmGroupId=1, SectorEqmId=2116;
/*Activating the LampSite LTE cell*/
ACT CELL: LocalCellId=2;

1.10.6.3 Engineering Implementation

This section describes the engineering implementation of performing
reconfiguration for BBU sharing between macro and LampSite base stations,
including local and remote operations.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 930

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Prerequisites
Information and data for sharing BBUs between macro and LampSite base
stations are ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local operations
a. Install the BBPs in the BBU.
b. Install the RHUBs. For details, see LampSite Installation Guide.
c. Install the pRRUs. For details, see LampSite Installation Guide.
d. Install the CPRI optical fibers and cables. For details, see LampSite
Installation Guide.
● Remote Operations
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
----End

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 931

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

1.10.6.4 Engineering Verification

This section describes how to verify the reconfiguration for BBU sharing between
macro and LampSite base stations.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

If a cell-related alarm is reported, clear it according to instructions in 3900 & 5900

Series Base Station Alarm Reference.

Step 2 Run the DSP CELL command to check whether Cell instance state is Normal.

If Cell instance state is Uninstall, check cell configuration data, cell reference
signal power, or hardware based on the value of Reason for latest state change
in the command output.

Step 3 Run the LST CELL command to check whether the values of Flag of Multi-RRU
Cell, Mode of Multi-RRU Cell, and Cell transmission and reception mode are
consistent with the configuration data.

----End

1.10.6.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Roll back the reconfiguration data.
● Using MML commands: traditional method
a. Run the DLD CFGFILE command to download the original configuration
file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run the ACT CFGFILE command to activate the original configuration
file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.
a. Run the DSP ROLCFGINFO command to query the configuration rollback
information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 932

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the physical connections.
Step 4 Verify that engineering rollback is successful according to instructions in 1.10.6.4
Engineering Verification.

----End

1.10.7 Adding an LAA Cell

This section describes how to add a licensed assisted access (LAA) cell.

1.10.7.1 Scheme Overview

This section describes the application scenario, reconfiguration impact,
reconfiguration scheme, and topology changes for adding an LAA cell.

Application Scenario
As MBB services expand, users demand more bandwidths and higher throughputs
from radio networks. LAA has been introduced to maximize utilization of cheap
license-free spectrum resources to provide higher service rates and to enhance
user experience. This technology allows LTE networks to use license-free bands to
offload traffic from cellular networks, while maintaining the same UE mobility and
QoS as those provided by the licensed spectrum. LAA also helps operators reduce
the cost of expanding LTE spectrum and improve the downlink UE throughput and
MBB experience.

Reconfiguration Impact
No impact

Topology Change
LAA cells are added in the following scenarios:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 933

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● One LTE cell + one LAA cell

Figure 1-181 One LTE cell + one LAA cell

● One LTE cell + two LAA cells

In this scenario, it is recommended that the spacing between the central
frequencies of the two configured LAA cells be 19.8 MHz (for example, 5150
MHz and 5169.8 MHz).

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 934

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-182 One LTE cell + two LAA cells

● Two LTE cells + one LAA cell

For two LTE cells for which downlink 2CC aggregation is implemented, only
one LAA cell needs to be added to implement downlink 3CC aggregation. For
details, see Carrier Aggregation Feature Parameter Description.

Reconfiguration Scheme
Figure 1-183 shows the reconfiguration procedure for adding an LAA cell.
Determine the reconfiguration scheme according to the following table.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 935

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-183 Procedure for adding an LAA cell

1.10.7.2 Engineering Preparation

This section describes the engineering preparation for adding an LAA cell including
information collection and preparation of hardware, software, license files,
certificates, and data. It also describes the data preparation mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 936

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Information Collection
Table 1-312 describes the information to be collected before the reconfiguration.

Table 1-312 Information to be collected

Information Description

Before adding an LAA cell,
familiarize yourself with
the local laws and
regulations on unlicensed
spectrum, including the
range of spectrum to use
and requirements for
coexistence technologies.
Policies for allocating license-free spectrum may
vary with regions. Contact the local authority of
radio spectrum for more information. For
coexistence technologies, LBT is mandatory in
some countries or regions and therefore Cell
ON/OFF cannot be used for deploying LAA cells.

Check whether the To support LAA cells, LampSite base stations

hardware supports LAA require the BBU3910/BBU5900, pRRU3911, and
cells. RHUB3918.

Hardware Preparation
N/A

Software Preparation
N/A

License File Preparation

For details, see Licensed Assisted Access Feature Parameter Description and Carrier
Aggregation Feature Parameter Description.

Security Certificate Preparation

N/A

Data Preparation
The following table lists the data to be prepared.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 937

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-313 Data preparation for adding an LAA cell

SN Oper MO Configuration Reference
ation

1 Add Cell ● Set Work mode to LAA(License

Assisted Access).
● Set Frequency band to 252. An
optimal value will be automatically
selected using FCS.
● Set Downlink EARFCN to 255244. An
optimal value will be automatically
selected using FCS.
● Set Uplink EARFCN indication to
NOT_CFG(Not configure).
● Set Cell transmission and reception
mode to 2T2R.
● Set Flag of Multi-RRU Cell to
BOOLEAN_TRUE(True).
● Set Mode of Multi-RRU Cell to
MPRU_AGGREGATION(MPRU_AGGR
EGATION).
● Set Downlink bandwidth to
CELL_BW_N100(20M).
For parameter setting notes, see "Data
Preparation" in Licensed Assisted Access
Feature Parameter Description.
2 Modif CellSiMap Set Cell System Information Switch to
y DlOnlyCellSiSwitch(DlOnlyCellSiSwitc
h).
For parameter setting notes, see "Data
Preparation" in Licensed Assisted Access
Feature Parameter Description.
3 Modif CellAlgoSwitch Set FCS mode to AUTO(AUTO).
y For parameter setting notes, see "Data
Preparation" in Licensed Assisted Access
Feature Parameter Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 938

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Oper MO Configuration Reference

ation

4 Add CellLaaFcsPara ● For the first frequency range, it is

recommended that the FCS Start
Frequency be set to 5150 and the
FCS Stop Frequency be set to 5250.
● For the second frequency range, it is
recommended that the FCS Start
Frequency be set to 5725 and the
FCS Stop Frequency be set to 5850.
● It is recommended that FCS
Interference Threshold be set to -80
(in the unit of dBm).
For parameter setting notes, see "Data
Preparation" in Licensed Assisted Access
Feature Parameter Description.
5 Add CellLaaCoexistPara ● Set Coexist mode to
DYNAMIC_DUTY(DYNAMIC_DUTY).
● Set High Interference Duty
Threshold to 70.
● Set High Interference Duration
Threshold to 600 (in the unit of
second).
For parameter setting notes, see "Data
Preparation" in Licensed Assisted Access
Feature Parameter Description.
6 Modif CellAlgoSwitch Turn on the frequency-based CA
y configuration switch and set the CA
private band combination supported by
7 Add PrivateCaBandComb the base station. For parameter setting
notes, see Data Preparation in Carrier
Aggregation Feature Parameter
Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 939

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Oper MO Configuration Reference

ation

8 Modif CaMgtCfg ● Set Cell Level CA Algorithm Switch

y to ON(On).
● If the LTE PCell is an SFN cell, it is
recommended that LAA Carrier
Aggregation A1 RSRP Threshold be
set to a value greater than the
default value based on operator
network plans. For example, -90.
● If the LTE PCell is an SFN cell, it is
recommended that LAA Carrier
Aggregation A2 RSRP Threshold be
set to a value greater than the
default value based on operator
network plans. For example, -95.
For parameter setting notes, see "Data
Preparation" in Licensed Assisted Access
Feature Parameter Description.
9 Add PccFreqCfg Set PCC Downlink EARFCN to the
planned value.
For parameter setting notes, see "Data
Preparation" in Licensed Assisted Access
Feature Parameter Description.
10 Add SccFreqCfg ● Set PCC Downlink EARFCN to the
planned value.
● Set SCC Downlink EARFCN.
– If this parameter is set to 255144,
the corresponding LAA SCell works
on the 252 MHz frequency band in
the downlink.
– If this parameter is set to 260894,
the corresponding LAA SCell works
on the 255 MHz frequency band in
the downlink.
For parameter setting notes, see "Data
Preparation" in Licensed Assisted Access
Feature Parameter Description.
11 Activa Cell -
te

Data Preparation Mode

● Using MML commands: Prepare MML configuration scripts based on the
preceding data preparation procedure and the following MML configuration
script examples.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 940

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

MML Configuration Script Example

The following example provides the MML configuration script of data preparation
for adding an LAA cell for an LTE cell to implement DL 2CC CA.
/*(LampSite) Adding an LAA cell*/ ADD CELL: LocalCellId=1, CellName="5G Cell", FreqBand=252,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=255244, UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100,
CellId=1, PhyCellId=85, FddTddInd=CELL_FDD, RootSequenceIdx=95,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, TxRxMode=2T2R, WorkMode=LAA, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION;
/*Setting FcsMode to AUTO*/
MOD CELLALGOSWITCH: LocalCellId=1, FCSMODE=AUTO;
/*Setting the FCS scanning range and detection threshold*/
ADD CELLLAAFCSPARA: LocalCellId=1, FCSSTARTFREQ=5150, FCSSTOPFREQ=5250, FCSINTERFTHD=-80;
ADD CELLLAAFCSPARA: LocalCellId=1, FCSSTARTFREQ=5725, FCSSTOPFREQ=5850, FCSINTERFTHD=-80;
/*Setting the coexistence mode*/
ADD CELLLAACOEXISTPARA: LocalCellId=1, CoexistMode=DYNAMIC_DUTY;
/*Turning on the frequency-based CA configuration switch*/
MOD ENODEBALGOSWITCH: CaAlgoSwitch=FreqCfgSwitch-1;
/*Setting the CA private band combination*/
ADD PRIVATECABANDCOMB: PrivateCaCombId=0, MaxAggregatedBw=40, BwCombSetId=0,
CombBand1Id=1,
CombBand1Bw=Bandwidth_1_4M-0&Bandwidth_3M-0&Bandwidth_5M-1&Bandwidth_10M-1&Bandwidth_15
M-1&Bandwidth_20M-1, CombBand2Id=252,
CombBand2Bw=Bandwidth_1_4M-0&Bandwidth_3M-0&Bandwidth_5M-0&Bandwidth_10M-0&Bandwidth_15
M-0&Bandwidth_20M-1;
/*Turning on the LAA CA downlink switch for the PCell*/
MOD CAMGTCFG: LocalCellId=0, CellCaAlgoSwitch=LaaCaDlSwitch-1;
/*Setting the PCC frequency*/
ADD PCCFREQCFG: PccDlEarfcn=123;
/*Setting the SCC frequencies*/
ADD SCCFREQCFG: PccDlEarfcn=123, SccDlEarfcn=255144;
ADD SCCFREQCFG: PccDlEarfcn=123, SccDlEarfcn=260894;
/*Setting the LAA CA A1/A2 threshold*/
MOD CAMGTCFG: LocalCellId=1, LaaCarrAggrA1ThdRsrp=-98, LaaCarrAggrA2ThdRsrp=-105;
/*(Optional) Activating the cells, including the PCell and the SCell*/
ACT CELL: LocalCellId=0;
ACT CELL: LocalCellId=1

The following example provides the MML configuration script of data preparation
for adding an LAA cell for an LTE cell to implement downlink 2CC aggregation.
/*(LampSite) Adding an LAA cell*/ ADD CELL: LocalCellId=1, CellName="5G Cell1", FreqBand=252,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=255244, UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100,
CellId=1, PhyCellId=85, FddTddInd=CELL_FDD, RootSequenceIdx=95,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, TxRxMode=2T2R, WorkMode=LAA, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION; ADD CELL: LocalCellId=2, CellName="5G Cell2", FreqBand=252,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=255442, UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100,
CellId=2, PhyCellId=86, FddTddInd=CELL_FDD, RootSequenceIdx=95,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, TxRxMode=2T2R, WorkMode=LAA, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION;
/*Setting FcsMode to AUTO*/
MOD CELLALGOSWITCH: LocalCellId=1, FCSMODE=AUTO;
MOD CELLALGOSWITCH: LocalCellId=2, FCSMODE=AUTO;
/*Setting the FCS scanning range and detection threshold*/
ADD CELLLAAFCSPARA: LocalCellId=1, FCSSTARTFREQ=5150, FCSSTOPFREQ=5250, FCSINTERFTHD=-80;
ADD CELLLAAFCSPARA: LocalCellId=1, FCSSTARTFREQ=5725, FCSSTOPFREQ=5850, FCSINTERFTHD=-80;
ADD CELLLAAFCSPARA: LocalCellId=2, FCSSTARTFREQ=5150, FCSSTOPFREQ=5250, FCSINTERFTHD=-80;
ADD CELLLAAFCSPARA: LocalCellId=2, FCSSTARTFREQ=5725, FCSSTOPFREQ=5850, FCSINTERFTHD=-80;
/*Setting the coexistence mode*/
ADD CELLLAACOEXISTPARA: LocalCellId=1, CoexistMode=DYNAMIC_DUTY;
ADD CELLLAACOEXISTPARA: LocalCellId=2, CoexistMode=DYNAMIC_DUTY;
/*Turning on the frequency-based CA configuration switch*/
MOD ENODEBALGOSWITCH: CaAlgoSwitch=FreqCfgSwitch-1;
/*Setting the CA private band combination*/
ADD PRIVATECABANDCOMB: PrivateCaCombId=1, MaxAggregatedBw=60, BwCombSetId=0,

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 941

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

CombBand1Id=1,
CombBand1Bw=Bandwidth_1_4M-0&Bandwidth_3M-0&Bandwidth_5M-1&Bandwidth_10M-1&Bandwidth_15
M-1&Bandwidth_20M-1, CombBand2Id=252,
CombBand2Bw=Bandwidth_1_4M-0&Bandwidth_3M-0&Bandwidth_5M-0&Bandwidth_10M-0&Bandwidth_15
M-0&Bandwidth_20M-1, CombBand3Id=252,
CombBand3Bw=Bandwidth_1_4M-0&Bandwidth_3M-0&Bandwidth_5M-0&Bandwidth_10M-0&Bandwidth_15
M-0&Bandwidth_20M-1;
/*Turning on the LAA CA downlink switch for the PCell*/
MOD CAMGTCFG: LocalCellId=0, CellCaAlgoSwitch=LaaCaDlSwitch-1;
/*Setting the PCC frequency*/
ADD PCCFREQCFG: PccDlEarfcn=123;
/*Setting the SCC frequencies*/
ADD SCCFREQCFG: PccDlEarfcn=123, SccDlEarfcn=255144;
ADD SCCFREQCFG: PccDlEarfcn=123, SccDlEarfcn=260894;
/*Setting the LAA CA A1/A2 threshold*/
MOD CAMGTCFG: LocalCellId=1, LaaCarrAggrA1ThdRsrp=-98, LaaCarrAggrA2ThdRsrp=-105;
MOD CAMGTCFG: LocalCellId=2, LaaCarrAggrA1ThdRsrp=-98, LaaCarrAggrA2ThdRsrp=-105;
/*(Optional) Activating the cells, including the PCell and the SCells*/
ACT CELL: LocalCellId=0;
ACT CELL: LocalCellId=1;
ACT CELL: LocalCellId=2;

1.10.7.3 Engineering Implementation

This section describes how to add an LAA cell locally and remotely.

Prerequisites
The information needed for adding an LAA cell is ready.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Remote Operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 942

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iii. Import a new license file.

Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.10.7.4 Engineering Verification

This section describes how to verify the addition of an LAA cell.

Procedure
Step 1 Verify that no cell-related alarm is reported, such as ALM-29240 Cell Unavailable
and ALM-29243 Cell Capability Degraded.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 943

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

If a cell-related alarm is reported, clear it according to instructions in 3900 & 5900

Series Base Station Alarm Reference.
Step 2 Run the DSP CELL command. Verify that Cell instance state is Normal for the
cell.
If Cell instance state is Uninstall, check the cell configuration or hardware based
on the value of Reason for latest state change in the command output.
Step 3 Check the following items. For details, see the section related to activation
verification in Licensed Assisted Access Feature Parameter Description.
1. Run the DSP CELLLAAFCSPARA command.
– When an LAA cell is added for one LTE cell to implement DL 2CC CA or
for two LTE cells to implement DL 3CC CA, and the LAA cell works on a
frequency with the minimal interference duty cycle, FCS is successfully
implemented.
– When two LAA cells are added for one LTE cell to implement DL 3CC CA,
and the two LAA cells work on a frequency within 40 MHz and with the
minimal interference duty cycle, and the interval between the two
frequencies is smaller than 19.8 MHz, FCS is successfully implemented.
2. If the network serves CA UEs and the L.Traffic.User.LteLaaCA.PCell.DL.Avg and
L.Thrp.bits.DL.LteLaaCAUser counters are not 0, CA is successfully enabled for
LAA cells. If these two counters are constantly 0, CA fails to be enabled for
LAA cells.
3. If the target LAA cells are set as the SCells in the RRC_CONN_RECFG message,
CA is successfully enabled for LAA cells.
4. If the L.Laa.ChannelShared.Used counter is not 0, Cell ON/OFF is successfully
implemented.

----End

1.10.7.5 Engineering Rollback

If the reconfiguration fails, the base station configuration can be rolled back to
the original state.

Procedure
Step 1 Roll back the reconfiguration data.
● Using MML commands: traditional method
a. Run the DLD CFGFILE command to download the original configuration
file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/", FN="ENBCFG.XML",
ENCRYPTMODE=UNENCRYPTED;
b. Run the ACT CFGFILE command to activate the original configuration
file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
● Using MML commands: Roll back the configuration data using the one-click
blind configuration rollback function.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 944

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

a. Run the DSP ROLCFGINFO command to query the configuration rollback

information.
Example: DSP ROLCFGINFO: OT=BYINFO;
b. Run the ROL CFGDATA command to roll back the configuration data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;
NOTE

▪ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.

▪ Blind configuration recovery is supported only when the Configuration Rollback

Switch is set to ON. The default value is ON. You can run the DSP ROLCFGSW
command to query the value of this parameter.

▪ Using the one-click blind configuration rollback function to roll back configuration
data may cause other data reconfigurations made at the same time to be rolled
back. Therefore, determine whether such impact is acceptable before you perform
the rollback.

▪ Only data backed up in one period can be rolled back. The start time at which the
system can recover data is the time of the last full database backup, and the end
time is the latest time recorded in the incremental record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.

Run the INS LICENSE command.

Step 3 Verify that engineering rollback is successful according to instructions in 1.10.6.4

Engineering Verification.

----End

1.10.8 Adding an RFA Cell

This section describes how to add a radio frequency access (RFA) cell.

1.10.8.1 Scheme Overview

This section describes the application scenario, reconfiguration impact, topology
change, and the reconfiguration scheme of adding an RFA cell.

Application Scenario
With the development of mobile network, indoor network performance must be
improved to provide better user experience. Indoor coverage must be provided in
densely populated and closed areas, such as office buildings, subways, residential
communities, and shopping malls, to ensure good user experience. The RFA
solution can be used to provide remote radio coverage for users in multi-vendor
networks and networks deployed and shared by multiple operators.

Reconfiguration Impact
No impact

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 945

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Topology Change
Assuming that an RHUB, pRRUs, an extend radio frequency card (ERC), a BBP, and
an RFA cell are added, Figure 1-184 shows the topologies before and after the
reconfiguration.

Figure 1-184 Topologies before and after adding an RFA cell (intra-RHUB)

NOTE

● The source base station serving the RFA cell must be independent. The LTE cell cannot cover
the same area as the RFA cell.
● The source base station must use RRUs instead of pRRUs.

Reconfiguration Scheme
Figure 1-185 shows the procedure for adding an RFA cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 946

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-185 Procedure for adding an RFA cell

NOTE

If the networking of new cells is consistent with that of original cells (on the same pRRU or
RRU), run the ADD RFACELLSECTOREQMGRP command to bind the new cells to the original
sector equipment group.

1.10.8.2 Engineering Preparation

This section describes the engineering preparation for adding an RFA cell,
including information collection and preparation of hardware, software, license
files, security certificates, and data. It also provides an example of MML
configuration scripts.

Information Collection
Table 1-314 describes the information to be collected before adding an RFA cell.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 947

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Table 1-314 Information Collection

Item Description

Cell information ● Basic information about the cell to be added, such as

RAT, frequency, and bandwidth
● TX and RX mode: RFA cells support 1T1R, 1T2R, or
2T2R mode.

Operating frequency For example, 900 MHz or 1800 MHz

band of the ERC

BBP type ● The type of the BBPs. For example, the UBBP.

MPT type For example, UMPTb1 or UMPTb2

RF module ● Type of the RF modules to be added

● Connections between pRRUs and RHUBs

Network topology Network topology of RFA cells

Sector equipment Value of the Sector Equipment Group ID and Sector

group equipment ID parameters in the EuSectorEqmGroup
MO

Hardware Preparation
Table 1-315 describes the hardware to be prepared for adding an RFA cell in
addition to the new pRRUs, related cables, and optical modules.

Table 1-315 Hardware to be prepared

If... Then...

BBPs are insufficient Add new BBPs.

— Connect the new RF module to the ERC based on

different frequency bands.

The maximum Add a new RHUB3918 (the maximum distance from the
bandwidth supported first-level RHUB to the last-level RHUB is 3 km),
by original RF pRRU5913, related cables, and optical modules.
modules is low

The transmission rate Add new optical modules.

of the original optical
modules is
insufficient

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 948

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Software Preparation

Table 1-316 Required software

Item Description

MAE-Access -
mediation

Software package Activating an RFA cell requires software package

supporting RFA supporting RFA.

License File Preparation

Prepare a new license file if the currently used license cannot meet requirements.
Table 1-317 describes the license control items to be prepared.

Table 1-317 License control items to be prepared

License Control Item Description

RF Access Bandwidth Controls the RF access bandwidth of LampSite pRRUs.

for LampSite pRRU
(per 5MHz per
pRRU)

Security Certificate Preparation

N/A

Data Preparation
Perform steps according to the following table.

Table 1-318 Data preparation for adding an RFA cell

SN Oper MO Configuration Reference

ation

1 Add RU (using MML ● Set Config Type to MERC.

commands)/BBP (using ● Set Board Type to UBBP
the MAE-Deployment)

2 Add RHUB -

3 Add RRUCHAIN -

4 Add RRU Set RF Unit Working Mode to a

value supporting RFA.

5 Add Sector -

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 949

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

SN Oper MO Configuration Reference

ation

6 Add SectorEqm -

7 Add RFAEqm -

8 Add Application Set Application Type to RFA.

9 Add RFAFunction -

10 Add RFACellSectorEqmGrp

11 Add RFAOperator -

12 Add RFALoCell ● Check the TX/RX mode. RFA cells

support 1T1R, 1T2R, and 2T2R. a
● Check the basic information of
the cell, such as RAT, frequency,
and bandwidth.

13 Add CellRFAEqm -

14 Add RFACellOperator -

15 Modi RFCPORT ● Run the MOD RFCPORT

fy command to modify the Power
Attenuation parameter of the
port on the RF card.
● Run the STR PORTPWRADJUST
command to adjust the port
power and ensure that the input
RF signal power for the RF port
meets the port power
requirements.

16 Activ RFALoCell -
ate

a: If a 2T2R LTE cell is deployed in RFA mode, both ERC ports of the LTE cell
must receive signals. If only one port receives signals, power calibration fails on
the other port without signal input.

Data Preparation Mode

NOTE

Before using the MAE-Deployment to prepare data, ensure that data in the planned data area is
consistent with that in the current data area. If the data is inconsistent, you can choose Area
Management > Planned Area > Synchronize Planned Area NEs from the menu bar to
synchronize data from the current data area to the planned data area. Then, perform the
following operations.

● Using the MAE-Deployment GUI. For details, see the interactive operation
guide Preparing Data in GUI Mode.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 950

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

● Using MML commands: Prepare MML configuration scripts based on the

preceding data preparation procedure and the following MML configuration
script examples.

Example of MML Configuration Scripts

MML scripts for adding an RFA cell are as follows:
/*Exporting the current license file in use and save it to the ftproot folder on the MAE server*/
ULD LICENSE: MODE=IPV4, IP="10.161.18.69", USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";
/*Adding an ERC*/
ADD BRD: SN=0, BT=MERC;
/*Adding a UBBP*/
ADD BRD: SN=3, BT=UBBP, BBWS=UMTS-1&LTE_FDD-1&LTE_TDD-1&NBIOT-1;

/*Adding an RRU chain*/

ADD RRUCHAIN: RCN=30, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=3, HPN=0;
/*Adding an RHUB*/
ADD RHUB: CN=0, SRN=60, RCN=30, PS=0;
/*Adding an RRU branch chain*/
ADD RRUCHAIN: RCN=70, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=60, HSN=0, HPN=0;
/*Adding an RRU*/
ADD RRU: CN=0, SRN=70, SN=0, TP=BRANCH, RCN=70, PS=0, RT=MPMU, RS=ULFTDR, RXNUM=2,
TXNUM=2, MNTMODE=NORMAL, RFTXSIGNDETECTSW=OFF;

/*Adding a sector*/
ADD SECTOR: SECTORID=70, ANTNUM=2, ANT1CN=0, ANT1SRN=70, ANT1SN=0, ANT1N=R0A, ANT2CN=0,
ANT2SRN=70, ANT2SN=0, ANT2N=R0B, CREATESECTOREQM=FALSE;
/*Adding sector equipment*/
ADD SECTOREQM: SECTOREQMID=70, SECTORID=70, ANTCFGMODE=ANTENNAPORT, ANTNUM=2,
ANT1CN=0, ANT1SRN=70, ANT1SN=0, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=70,
ANT2SN=0, ANT2N=R0B, ANTTYPE2=RXTX_MODE;

/*Adding RFA equipment*/

/*Adding 2T2R RFA equipment*/
ADD RFAEQM: RFAEQMID=0, PORTNUM=2, CN1=0, SRN1=0, SN1=0, PN1=0, DLULMODE1=ULDL, CN2=0,
SRN2=0, SN2=0, PN2=1, DLULMODE2=ULDL;
/*Adding 1T2R RFA equipment*/ ADD RFAEQM: RFAEQMID=1, PORTNUM=2, CN1=0, SRN1=0, SN1=0,
PN1=0, DLULMODE1=ULDL, CN2=0, SRN2=0, SN2=0, PN2=1, DLULMODE2=UL;
/*Adding 1T1R RFA equipment*/
ADD RFAEQM: RFAEQMID=3, PORTNUM=1, CN1=0, SRN1=0, SN1=0, PN1=0, DLULMODE1=ULDL;

/*Adding an RFA application*/

ADD APP: AID=1, AT=RFA, AN="RFAAPP", APPMNTMODE=NORMAL;

/*Adding the RFA function*/

ADD RFAFUNCTION: RFAFunctionName="RFAFunction", ApplicationRef=1, RFAId=0;
/*Adding an operator*/
ADD RFAOPERATOR: RFAOperatorId=0;

/*Adding a cell*/
/*Adding an LTE cell*/
ADD RFALOCELL: LocalCellId=0, CellName="RFALOCELL", AccessStandard=LTE_FDD, FreqBand=3,
Dlearfcn="1300", BandWidth=BW_20M, CellRadius=14500, TxRxMode=2T2R;
/*Adding a UMTS cell*/ ADD RFALOCELL: LocalCellId=1, CellName="RFALOCELL", AccessStandard=UMTS,
FreqBand=1, Dlearfcn="10575-10600", BandWidth=BW_10M, CellRadius=14500, TxRxMode=1T2R;
/*Adding a GSM cell*/
ADD RFALOCELL: LocalCellId=2, CellName="RFALOCELL", AccessStandard=GSM, FreqChannel=E-GSM900,
Dlearfcn="92-94-96-98", CellRadius=14500, TxRxMode=1T1R;

/*Adding cell RFA equipment*/

ADD CELLRFAEQM: LocalCellId=0, RFAEqmId=0;
/*Adding an RFA cell sector equipment group*/
ADD RFACELLSECTOREQMGRP: LocalCellId=4, SectorEqmGroupId=0;
/*Adding operator information for an RFA cell*/
/*Adding operator information for an LTE cell*/
ADD RFACELLOP: LocalCellId=0, RFAOperatorId=0;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 951

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

/*Adding operator information for a UMTS cell/ ADD RFACELLOP: LocalCellId=1, RFAOperatorId=0;
/*Adding operator information for a GSM cell*/
ADD RFACELLOP: LocalCellId=2, RFAOperatorId=0;

/*Setting the port attenuation amount*/

MOD RFCPORT: CN=0, SRN=0, SN=0, PN=0, PWRATTENUATION=-100;
/*Starting power adjustment for a port*/
STR PORTPWRADJUST: CN=0, SRN=0, SN=0, PN=0;
/*Activating the cell*/
ACT RFALOCELL: LocalCellId=0;

1.10.8.3 Engineering Implementation

This section describes the engineering implementation of adding an RFA cell,
including local and remote operations.

Prerequisites
The required information, license file, and configuration data file are available.

Context
● Local Operations describe the operations that must be performed onsite,
such as hardware installation and operations on the LMT.
● Remote Operations describe the operations that must be performed on the
operation and maintenance center (OMC), such as adjusting parameters
using the MAE-Access or MAE-Deployment.

Procedure
● Local operations
a. Install the BBP and ERC in the BBU.
b. Install the RHUBs. For details, see LampSite Installation Guide.
c. Install the pRRUs. For details, see LampSite Installation Guide.
d. Install the CPRI optical fibers and cables. For details, see LampSite
Installation Guide.
● Remote operations
– Using the MAE-Deployment:
NOTE

If the license file needs to be updated, the active license file must be backed up and a
new license file must be imported into the base station. If the license file does not
need to be updated, the backup and import operations are not required.

i. Set the eNodeB maintenance mode to expand status before

reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up the license file in use to the MAE server.
Run the ULD LICENSE command.
Example: ULD LICENSE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="LIC_LTE_ON.xml";

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 952

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

iii. Import a new license file.

Run the INS LICENSE command.
For example: INS LICENSE: DIR="ftproot/",
FN="LIC_LTE_ON_100.xml", FLG=NO, MODE=IPV4,
IP="10.161.18.69", USR="ftpuser", PWD="***********";
iv. Deliver the configuration data to the base station and activate the
data. For details, see the interactive operation guide Delivering Data
to Base Stations and Activating the Data.
v. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.
– Using MML commands:
i. Set the eNodeB maintenance mode to expand status before
reconfiguration to prevent unnecessary alarms from being reported
during the reconfiguration.
For details, see 1.11.1 Setting the eNodeB Maintenance Mode.
ii. Back up and export the configuration file. The configuration file can
be used to roll back configurations to the original state, if the
reconfiguration fails.
1) Run the BKP CFGFILE command to back up the configuration
file.
2) Run the ULD CFGFILE command to export the configuration file.
For example: ULD CFGFILE: MODE=IPV4, IP="10.169.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/";
iii. Use the MAE-Access to deliver the batch configuration scripts
prepared in Engineering Preparation > Data Preparation to the
base station and activate the scripts on the base station. For details,
see 1.3.3 Running MML Commands on the MAE-Access.
NOTE

You can import or export the license file for only one NE at a time.
iv. After the reconfiguration is complete, set the eNodeB maintenance
mode to NORMAL.
For details, see Setting the Maintenance Mode of the eNodeB to
NORMAL.

----End

1.10.8.4 Engineering Verification

This section describes how to verify whether an RFA cell is successfully added.

Procedure
Step 1 Confirm that no related alarm is reported, and handle the alarm according to the
suggestions.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 953

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Step 2 Run the DSP RFALOCELL command to check whether Cell instance state is
Normal.
If Cell instance state is Uninstall, check cell configuration data, cell reference
signal power, or hardware based on the value of Reason for latest state change
in the command output.
Step 3 Run the LST RFALOCELL command to check whether the values of Signal Mode,
Frequency Channel, Frequency Band, Downlink EARFCN, and Cell Transmission
And Reception Mode are the same as planned.

----End

1.10.8.5 Engineering Rollback

If the reconfiguration fails, it can be rolled back to the original configuration.

Procedure
Step 1 Restore the configuration data.
● Use the MAE-Deployment to roll back the configuration data. For detailed
operations, see the interactive operation guide Rolling Back Configuration
Data.
● Using MML commands:
– Method 1: Roll back the configuration data using the traditional method.
i. Run the DLD CFGFILE command to download the original
configuration file.
Example: DLD CFGFILE: MODE=IPV4, IP="10.161.18.69",
USR="ftpuser", PWD="***********", DIR="ftproot/",
FN="ENBCFG.XML", ENCRYPTMODE=UNENCRYPTED;
ii. Run the ACT CFGFILE command to activate the original
configuration file.
Example: ACT CFGFILE: EFT=IMMEDIATELY;
– Method 2: Roll back the configuration data using the one-click blind
configuration rollback function.
i. Run the DSP ROLCFGINFO command to query the configuration
rollback information.
Example: DSP ROLCFGINFO: OT=BYINFO;
ii. Run the ROL CFGDATA command to roll back the configuration
data.
Example: ROL CFGDATA: RT=BYTRANSID, ROLTRANSID=38;

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 954

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

○ The configuration rollback function is applicable only to the following main

control boards: UMPTa/UMPTb/UMPTe/UMPTg/UMPTga/UMDU/SMPT/UEFU.
○ Blind configuration recovery is supported only when the Configuration
Rollback Switch is set to ON. The default value is ON. You can run the DSP
ROLCFGSW command to query the value of this parameter.
○ Using the one-click blind configuration rollback function to roll back
configuration data may cause other data reconfigurations made at the same
time to be rolled back. Therefore, determine whether such impact is
acceptable before you perform the rollback.
○ Only data backed up in one period can be rolled back. The start time at
which the system can recover data is the time of the last full database
backup, and the end time is the latest time recorded in the incremental
record table.

Step 2 (Optional) Import the pre-reconfiguration license file if the license file is updated.
Run the INS LICENSE command.
Step 3 Restore the physical connections.
Step 4 Verify that engineering rollback is successful according to instructions in 1.10.8.4
Engineering Verification.

----End

1.11 Configuration References

This chapter provides the reference documents for data configuration. If you want
to view all the check rules of NE data, obtain the file on the Consistency Check
page.

1.11.1 Setting the eNodeB Maintenance Mode

Before reconfiguring a base station, set its maintenance mode to a customized
expand status or TESTING to avoid alarms generated during the reconfiguration.
After the data reconfiguration is complete, set the maintenance mode to
NORMAL.
The maintenance mode of an eNodeB running properly is NORMAL.

NOTE

● For a co-MPT base station, you can set the maintenance mode to TESTING for the specified
RAT. For an LTE RRU/RFU, you can change its maintenance mode to TESTING.
● For a co-MPT base station, the maintenance mode of only one NE can be reconfigured and
the reconfiguration takes effect on the entire base station. Reconfiguring the maintenance
mode of an NE takes effect only on this RAT.
● For a separate-MPT base station, maintenance modes of the NEs must be reconfigured
separately and the reconfiguration of an NE affects only the NE.

Setting the eNodeB Maintenance Mode to Expand Status

● On the MAE-Access:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 955

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

– Set a single eNodeB on the MAE-Access as follows:

i. On the MAE-Access, choose Maintenance > Maintenance Mode.
ii. (This step is optional. Perform the operation if the eNodeB does not
have a customized expand status.)

1) In the Maintenance Mode window, click at the upper-left

corner, and then at the upper-right corner to set the
maintenance mode.
2) In the New Maintenance Mode dialog box, set NE
Maintenance Mode, OSS Maintenance Mode, Remarks, and
then click OK.
For example, set NE Maintenance Mode to EXPANDSTATUS1
and OSS Maintenance Mode to Reconfiguration.

iii. Click at the upper-left corner of the Maintenance Mode

window.
iv. In the Set Maintenance Mode dialog box, select the NE or RRU/RFU
to be configured. Set NE maintenance mode to a customized
expand status, and set the execution time. Click OK to complete the
setting.
NOTE

For a co-MPT base station, you can also select the gNodeBFunction,
eNodeBFunction, NodeBFunction, or GBTSFunction node to specify the
maintenance mode for the RAT.
v. In the displayed Confirm dialog box, click Yes.
vi. The configuration progress is displayed. When the progress reaches
100%, click Close.
– Set eNodeBs in batches on the MAE-Access as follows:
i. On the MAE-Access, choose Maintenance > Maintenance Mode.
ii. (This step is optional. Perform the operation if the eNodeB does not
have a customized expand status.)

1) In the Maintenance Mode window, click at the upper-left

corner, and then at the upper-right corner to set the
maintenance mode.
2) In the New Maintenance Mode dialog box, set NE
Maintenance Mode, OSS Maintenance Mode, Remarks, and
then click OK.
For example, set NE Maintenance Mode to EXPANDSTATUS1
and OSS Maintenance Mode to Reconfiguration.
iii. In the NE list, set eNodeB maintenance mode to a customized
expand status.

iv. Click to import the NE list.

v. The configuration progress is displayed. When the progress reaches
100%, click Close.
● On the LMT:

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 956

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

You can specify Start Time and End Time of the maintenance mode as required.
– Run the SET MNTMODE command to set the NE maintenance mode to a
customized expand status.
– Run the MOD RRU command with Maintenance Mode set to
TESTING(TESTING) for an RF module.
– Run the MOD APP command with Application Maintenance Mode set
to TESTING(TESTING) for an RAT of a co-MPT base station.

On the alarm console, the eNodeB does not report the alarms that are generated
during the reconfiguration.

Setting the Maintenance Mode of the eNodeB to NORMAL

● On the MAE-Access:
– Set a single eNodeB on the MAE-Access as follows:
i. On the MAE-Access, choose Maintenance > Maintenance Mode.

ii. Click at the upper-left corner of the Maintenance Mode

window.
iii. In the Set Maintenance Mode dialog box, select the NE to be
configured. Set NE Mode to NORMAL. Click OK to complete the
setting.
iv. In the displayed Confirm dialog box, click Yes.
v. The configuration progress is displayed. When the progress reaches
100%, click Close.
– Set eNodeBs in batches on the MAE-Access as follows:
i. On the MAE-Access, choose Maintenance > Maintenance Mode.
ii. In the NE list, set the maintenance mode to NORMAL(NORMAL).

iii. Click to import the NE list.

iv. The configuration progress is displayed. When the progress reaches
100%, click Close.
● On the LMT:
– Run the SET MNTMODE command for an NE or the MOD RRU
command for an RF module with Maintenance Mode set to
NORMAL(NORMAL).
– Run the MOD APP command with Application Maintenance Mode set
to NORMAL for an RAT of a co-MPT base station.

The alarms that are not cleared during the reconfiguration will be displayed on
the alarm console after the eNodeB enters the normal state.

1.11.2 Using the Batch Reconfiguration Mode of the MAE-

Deployment to Prepare Data

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 957

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

If the current browser does not support the playback of this tutorial, please try another
browser.
● Watch online
● Click to download

1.11.3 Preparing Data in GUI Mode

NOTE

If the current browser does not support the playback of this tutorial, please try another
browser.
● Watch online
● Click to download

1.11.4 Delivering Data to Base Stations and Activating the

Data

NOTE

If the current browser does not support the playback of this tutorial, please try another
browser.
● Watch online
● Click to download

1.11.5 Falling Back Configuration Data

NOTE

If the current browser does not support the playback of this tutorial, please try another
browser.
● Watch online
● Click to download

1.11.6 Cell Types and Networking Restrictions of the LampSite

Solution

Cell Type
● pRRU-aggregation cell: A pRRU-aggregation cell is served by one or multiple
pRRUs whose RF signals are combined on one RHUB. A pRRU-aggregation
cell, which is a logical 2T2R cell, is configured with one sector equipment
group. As shown in Figure 1-186, cell 0 is a pRRU-aggregation cell that is
served by one pRRU, and cell 1 is a pRRU-aggregation cell that is served by
eight pRRUs. As shown in Figure 1-187, cell 0 is a pRRU-aggregation cell
served by one pRRU, and cell 1 is a pRRU-aggregation cell served by 16
pRRUs that are connected to two RHUBs.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 958

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

NOTE

In FDD or NB-IoT: An eNodeB supports the RF combination of four-layer cascaded

RHUBs on the same CPRI link and supports the pRRU-aggregation cells each served by
a maximum of 16 pRRUs. An eNodeB, however, does not support the setup of a pRRU-
aggregation cell across different CPRI links. One RHUB can serve a maximum of two
LTE cells that are also served by another RHUB. Only intra-RHUB RF combination is
supported for other LTE cells served by this RHUB.

Figure 1-186 pRRU-aggregation cell networking (1)

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 959

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-187 pRRU-aggregation cell networking (2)

● Pico SFN cell: A Pico SFN cell includes multiple pRRU-aggregation cells
working on the same frequency. Each pRRU-aggregation cell is equivalent to
a 2T2R cell. A pico SFN cell consists of multiple 2T2R cells. As shown in Figure
1-188, cell 2 is a pico SFN cell that consists of three pRRU-aggregation cells.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 960

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-188 Pico SFN cell networking

● SFN cell: In the single-frequency networking scenario, multiple RRUs (TDD:

4T4R; FDD: 2T2R; NB-IoT: 2T2R) serve one SFN cell. As shown in Figure
1-189, cell 3 is an SFN cell that is served by four RRUs (TDD: 4T4R; FDD:
2T2R; NB-IoT: 2T2R).

Figure 1-189 SFN cell

● Outdoor cell: In the LampSite networking scenario, RHUBs are connected to

Book RRUs (RRU3230E or RRU3930E) over optical ports. The specifications
and configuration solutions of these RRUs are the same as those of pRRUs. In
reconfigurations dedicated to the LampSite solution, pRRU cells are used as
examples to describe how to reconfigure Book RRUs.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 961

eRAN
Reconfiguration Guide 1 eRAN Reconfiguration Guide

Figure 1-190 Outdoor cell

LampSite Networking Restrictions

● For details about the cell bandwidths supported by the LampSite solution, see
Cell Management and SFN in eRAN Feature Documentation.
● For details about networking restrictions of the LampSite solution, see
LampSite Solution Description.

Issue 04 (2023-03-25) Copyright © Huawei Technologies Co., Ltd. 962