High Risk Command List

BSC6910 UMTS High-Risk Command List
Note: This sheet is part of MML Command Reference. It provides a list of high-risk commands, and running any of these co
Command
ADD ACLRULE
ADD FILTMSG
ADD
PACKETFILTER
Function
Use this command to add an ACL rule.

Use this command to add the message
filtering rule which is used to check and
correct an incorrect message. This is for
device mainenance and test.
Use this command to enable packet filter on a
port so that IP data packets received on a port
can be filtered by ACL rules in the ACL that is
bound to the port. After packet filter is
enabled, if ACL rules are available in the ACL,
the port can process only unicast packets that
meet ACL rules and discard other packets. If
no ACL rules are available in the ACL, the port
does not filter packets.
ADD SUBRACK
Use this command to add a subrack during

system initialization and capacity expansion of
the system.
ADD UABLMSG
Use this command to add a debugging

message. Upon receiving a message, the
RNC compares the received message with the
debugging message according to matching
items, including the matching offset, matching
length, and matching content. If the matching
result is positive, the RNC modifies or discards
the received message. The RNC repeats
these operations before transmitting a
message.
Use this command to add the TCP IP

addresses for SOCKET communications
ADD UCBSADDR
between the Cell Broadcast Center (CBC) of
Cell Broadcast Service (CBS) and the RNC.
ADD UCBSMSG
Use this command to add a simplified CBS

message. This command is used for disaster
warning.
Use this command to add cell access

restriction parameters. Access restriction
prevents access channel overload. The
SIMs/USIMs of all the UEs are allocated with
one or more access classes. Sixteen access
classes AC 0-15 are provided and are
specified for the following scenarios:
ADD
- AC 0 ~ AC 9 --- All UEs
UCELLACCESSS
- AC10 --- Whether the UEs belonging to AC
TRICT
0-9 or without IMSI can access the network in
case of emergency calls
- AC11 --- For PLMN use
- AC12 --- Security services
- AC13 --- Public utilities
- AC14 --- Emergency services
- AC15 --- UEs in the PLMN
Use this command to add the parameters of
ADD
the manually triggered DSAC algorithm at the
UCELLDSACMAN cell level for the specified telecom
UALPARA
operator.The parameter of DSAC(Domain
Specific Access Restriction) is manual setting.
ADD
Add Parameters for Cell-orientated FACH
UCELLFACHCON
Congestion Control Algorithm.
GCTRL
ADD
Use this command to add cell-level PS fast
UCELLFSTDRMTI
dormancy timers.
MER
ADD
Use this command to add the Cell-oriented
UCELLINTERRAT
Inter-RAT DRD parameters.
DR
ADD
Add Cell-Orientated Queuing and Preemption
UCELLQUEUEPR
Algorithm Parameters.
EEMPT
ADD
Use this command to add activation time
UCELLRLACTTIM offset for cell synchronized radio link
E
reconfiguration.
ADD UCNNODE
Use this command to add a CN node.
ADD
UCNOPALLCELL
BLK
Use this command to add parameters for

quickly blocking all the cells of the designated
operator in the RNC and block the cells.
ADD
UFACHDYNTFS
Use this command to add the transport format

set (TFS) of a FACH.
ADD UNRNC
Use this command to add a neighboring RNC.
ADD
Use this command to add the parameters for
URNCALLCELLBL quickly blocking all the cells in the RNC and
K
block the cells.
Use this command to obtain and lock the

logical RNC control right for the RNC in Pool
ADD
feature. After this command is executed for a
URNCHOSTLOCK physical RNC, this RNC takes over the control
right of dual-homing NodeBs from the peer
physical RNC.
Use this command to add the basic

ADD
parameters of physical layer of a SCCPCH
USCCPCHBASIC
before cell activation.
BLK AAL2PATH
Use this command to block an AAL2 path.
BLK SUBSYS
Use this command to block a subsystem of

the UUP, NIU or UUEP type.
BLK UCELL
BLK UNODEB
CHG MEINSPARA
During cell or cell common channel

maintenance period, it is expected to release
the current users, and to prevent new users
from accessing in the cell. This could be done
by executing the MML command BLK UCELL.
1.When a cell is blocked, the previous
services in the cell are released and the cell is
unavailable.
2.A blocked cell can be unblocked using the
command "UBL UCELL".
Use this command to block the NodeB.
Use this command to change installed
parameters of the Management Entity.
DEA MTP3LKS
Use this command to deactivate an MTP3

signaling link set.
Use this command to deactivate an MTP3

signaling link. The BSC sends an STOP
message to the SAAL and releases the SAAL
DEA MTP3LNK
link to deactivate an MTP3 signalling link. The
BSC then changes the signalling link state to
deactivated.
Use this command to deactivate a cell, and
DEA UCELL
make the cell data unavaliable.
DEA UNODEB
Use this command to deact the NodeB.
Use this command to deactivate the SCCPCH
DEA USCCPCH
configuration information to invalidate the
related parameters.
Use this command to deactivate the
configuration of a typical traffic RAB.
RAB is used to identify the service the Access
DEA UTYPRAB
Stratum (AS) provides for the Non-Access
Stratum (NAS) to transfer user data between
the User Equipment (UE) and the Core
Network (CN).
Use this command to deactivate the
configuration of a typical Signaling Radio
Bearer (SRB).
DEA UTYPSRB
SRB is used to identify the service that the
Access Stratum (AS) provides for the NonAccess Stratum (NAS) to transfer signaling.
Use this command to forcibly reclaim the
NodeB control right from the local RNC for a
primary homing NodeB or a secondary homing
FOC
NodeB. After this command is executed, the
UDEHOSTNODEB NodeB control right shifts from the local RNC
to the peer RNC, and the host type of NodeB
is switched over to the secondary homing
NodeB.
FOC
UHOSTNODEB
Use this command to forcibly obtain the

NodeB control right over a secondary homing
NodeB or a primary homing NodeB. After this
command is executed, the NodeB control right
shifts from the peer RNC to the local RNC,
and the host type of NodeB is switched over
to the primary homing NodeB.
Use this command to preempt control rights of

a logical RNC when the RNC in Pool Node
Redundancy feature is enabled. After this
FOC UHOSTRNC command is executed on this physical RNC,
this physical RNC has the control rights of
dual-homing NodeBs and the peer physical
RNC releases the control rights.
HO UCELL
Use this command to hand over a cell forcibly.

During cell handover, existing connections will
be handed over to other cells.
INH BRD
Use this command to inhibit a board.
INH MTP3LNK
Use this command to inhibit an MTP3

signaling link.
INH N7DPC
Use this command to inhibit a DSP.
INH
STANDBYSCU
Use this command to inhibit the standby SCU

board.
INS ME
Use this command to install the Management

Entity.
LCK SCHTSK
Use this command to lock all scheduled tasks.
LOD RULELIB
Use this command to forcibly load the rule

library file in the active workspace of the OMU
to the flash primary area on the NIU board.
MOD ACLRULE
Use this command to modify an ACL rule.
MOD ADJNODE
Use this command to modify the configuration

information about a transport adjacent node.
MOD APPCERT
Use this command to set a device certificate

file for an application. Different applications
( only SSL is supported ) can be configured
with the same device certificate file or different
device certificate files.
MOD BRD
Use this command to change the board type

of a board whose board class is GPU, GCU,
INT or SCU.
MOD OMUIP
Use this command to modify the OMU IP

addresses.
MOD
PACKETFILTER
Use this command to modify packet filter

configurations of a port. After packet filter
configurations of a port are modified, if ACL
rules are available in the ACL, the port can
process only unicast packets that meet ACL
rules and discard other packets. If no ACL
rules are available in the ACL, the port does
not filter packets.
MOD SAALLNK
Use this command to modify the settings for

an SAAL link.
MOD
TRMFACTOR
Use this command to modify a factor table.

The activation factor determines the maximum
number of UEs that can access the network
that has a fixed bandwidth. The smaller the
activation factor is, the more UEs can access
the network. In addition, the possibility of
service congestion increases, and the user
experience deteriorates.
MOD TRMMAP
Use this command to modify a transport

resource mapping.
Modify the basic information of a cell, including

"Max transmit power of cell", "Num of
continuous in sync ind", "Num of continuous
MOD UCELL
out of sync ind", "Radio link failure timer
Length", and the transmit power of the
downlink common channels such as PSCH,
SSCH, PCPICH and BCH.
Use this command to modify the cell access
restriction information, including cell status,
cell reserved information and access control
information.
With such access control information
configured, operators can effectively avoid
access channel overload. The SIMs/USIMs of
all the UEs are allocated with one of the
Access Class 0~9. In addition, one or more
special access classes (Access Class 11~15)
might be allocated to the SIM/USIM storage
information of the UEs with high priority, as
MOD
shown below:
UCELLACCESSS 1. Access Class 15 --- PLMN Staff;
TRICT
2. Access Class 14 --- Emergency Services;
3. Access Class 13 --- Public Utilities;
4. Access Class 12 --- Security Services;
5. Access Class 11 --- For PLMN Use.Different
from Access Class 0~9 and 11~15, the control
information of Access Class 10 is sent to UEs
by means of air interface signalling, indicating
whether the UEs belonging to Access Class
0~9 or without IMSI can be accessed to the
network in case of emergency calls. For the
UEs with Access Class 11~15, they cannot
initiate the emergency calls when AccessClass
10 and Access Class 11~15 are all barred.
Use this command to modify the parameters

MOD
of the manually triggered DSAC (Domain
UCELLDSACMAN
Specific Access Control) algorithm at the cell
UALPARA
level for the specified telecom operator.
MOD
Modify Parameters for Cell-orientated FACH
UCELLFACHCON
GCTRL
MOD
Use this command to modify cell-level PS fast
UCELLFSTDRMTI
dormancy timers.
MER
MOD
Use this command to modify the Cell-oriented
UCELLINTERRAT
DR
MOD
UCELLQUEUEPR
EEMPT
MOD
UCELLRLACTTIM
E
MOD
UCNDOMAIN
Modify Cell-Orientated Queuing and

Preemption Algorithm Parameters.
Use this command to modify cell synchronized
radio link reconfiguration activation time offset.
Use this command to add the specific Non
Access Stratum (NAS) information and
Discontinuous Reception (DRX) cycle length
coefficient of Core Network (CN) domain.
The specific NAS information of Circuit
Switched (CS) domain is to provide Mobile
Station (MS) with accurate parameters related
to Mobility Management (MM) function. It has
2 octets, as shown below:
The specific NAS information of Packet
Switched (PS) domain is to provide MS with
accurate parameters related to GPRS Mobility
Management (GMM) function. It has 2 octets,
as shown below:
Where, the Routing Area Code (RAC) is used
to define a routing area in a location area. Its
fixed length is 1 octet (8 bits). The 8th bit is the
most significant bit, and the 1st bit is the least
significant bit.The Network Mode of Operation
(NMO) is expressed by 1 bit, 0 for NMO 1 and
1 for NMO 2.
MOD UCNNODE
Use this command to modify a CN node.
MOD
UCNOPERATOR
Use this command to modify a CN Operator.
Use this command to modify a UMTS operator

group. After the MOCN is deployed, a cell can
be configured with multiple operators. One cell
corresponds to one operator group. Each
operator group can be configured with one to
MOD
four available operators and zero to one
UCNOPERGROU common operator. Note that after ICR
P
demarcation is added, cells under a NodeB of
the Dedicated or RAN Sharing type can also
be configured with multiple operators. The
operators, however, must consist of the
primary or secondary operator and several
ICR operators.
MOD UNODEB
Use this command to modify NodeB

parameters.
MOD UNRNC
Use this command to modify a neighboring

RNC.
MOD
URNCBASIC
Use this command to modify RNC basic

Information.
MOD URNCMAP
Use this command to modify a mapping

between the logical RNC of the physical RNC
and another physical RNC.
MOD USCCPCH
Use this command to modify the

configurations of a SCCPCH.
Use this command to modify the basic

information of the typical Radio Access Bearer
(RAB).
MOD
UTYPRABBASIC Stratum (AS) provides for the Non-Access
Stratum (NAS) to transfer user data between
the User Equipment (UE) and the Core
Network
(CN).
Use
this command
to modify measurement
control parameters of the Dynamic Channel
Configuration Control (DCCC) algorithm.
These parameters are applicable to PS
domain Best Effort (BE) services, which are
relatively insensitive to the delay.
MOD
BE services transmit data whenever resources
UTYPRABDCCCM are available. BE services usually refer to
C
background or interactive services of PS
domain. This type of service has features such
as large probability of burst transmission of
service source data, great tolerance of
transmission delay, no requirements for
transmission rate, and low error rate of
transmission data.
Use this command to modify High Speed
MOD
Packet Access (HSPA) information for a
UTYPRABHSPA
typical Radio Access Bearer (RAB).
MOD
Use this command to modify HSUPA Power
UTYPRABHSUPA Control parameters for a typical Radio Access
PC
Bearer (RAB).
Use this command to modify typical RAB

Outer-Loop Power Control (OLPC)
parameters.
The OLPC algorithm adjusts the target values
MOD
for the inner-loop power control based on the
UTYPRABOLPC communication quality, such as the Block Error
Rate (BLER), Bit Error Rate (BER), and Frame
Error Rate (FER). Thus, the communication
requirements can always be fulfilled at the
minimum power.
Use this command to modify Radio Link
MOD
Control (RLC) parameters for a subflow of a
UTYPRABRLC
typical Radio Access Bearer (RAB), such as
RLC mode and RLC flow control parameters.
Modify semi-static Transport Format (TF)
parameters for a typical traffic Radio Access
Bearer (RAB).
1. Semi-static: Semi-static parameters are the
parameters whose values remain unchanged
after transport format sets of a transport
channel are set.
2. TTI: Transmission Time Interval. The MAC
layer transmits a Transport Block Set (TBS) to
or receives a TBS from a transport channel
MOD
every TTI. TTI is the processing time unit of
UTYPRABSEMIST the physical layer. It reflects the interleaving
ATICTF
degree and corresponds to the service delay
in the UTRAN.
3. Channel coding type: Both convolutional
code and Turbo code adopted by WCDMA are
high-performance, forward error-correcting
codes.
4. Rate matching attribute: It represents the
weight of processing (repeating or deleting)
data bits that is performed with channel coding
on the corresponding transport channel during
the rateparameters
matching process.
Modify
of the Time of Arrival (TOA)
window for a typical traffic Radio Access
Bearer (RAB).
A receiver window is configured in the
MOD
establishment and reconfiguration phases of
UTYPRABTOAW an RAB for downlink data frame reception.
This window is used to monitor whether data
frames are received. This command defines
the start point and end point of the receiver
window.
Use this command to modify basic information
of the typical Signaling Radio Bearer (SRB).
MOD
UTYPSRBBASIC Access Stratum (AS) provides to the Non
Access Stratum (NAS) for transfer of
signaling.
MOD
Modify Setting of AM RLC Parameters for
UTYPSRBDCHRN
CELL_DCH SRB on the RNC Side.
CRLC
MOD
UTYPSRBHSPA
Mod HSPA Information for a typical signalling.
MOD
Use this command to modify HSUPA Power
UTYPSRBHSUPA Control parameters for a typical Signaling
PC
Radio Bearer (SRB).
MOD
UTYPSRBOLPC
Use this command to modify typical SRB

OLPC parameters.
OLPC: Outer Loop Power Control. The OLPC
algorithm adjusts the target values for the
inner loop power control based on the
communication quality, such as the Block Error
Error Rate (FER) parameters. Thus, the
minimum power can always meet the
communication requirements.
MOD
UTYPSRBRLC
Modify the radio link control parameters of

typical signalling radio bearers.
Use this command to modify semi-static

Transport Format (TF) parameters for a typical
Signaling Radio Bearer (SRB).
1. Semi-static: The value of a semi-static
parameter remains unchanged during the time
when a transport channel exists.
2. TTI: Transmission Time Interval. The MAC
layer transmits a Transport Block Set (TBS) to
or receives a TBS from a transport channel
every TTI. TTI is the processing time unit of
the physical layer. It reflects the interleaving
MOD
degree and corresponds to the service delay
UTYPSRBSEMIST
in the UTRAN.
ATICTF
3. Channel coding type: Both convolutional
code and Turbo code adopted by WCDMA are
high-performance, forward error-correcting
codes. Typically, convolutional code is applied
to SRB control data bits to fulfill realtime data
transmission.
4. Rate matching attribute: It represents the
weight of processing (repeating or deleting)
data bits that is performed with channel coding
on the corresponding transport channel during
the rate matching process.
Use this command to modify time of arrival
window parameters for a typical signalling.
A receiver window is configured in the
establishment and reconfiguration phases of
MOD
an SRB for downlink data frame reception.
UTYPSRBTOAW
This window is used to monitor whether data
frames are received. This command defines
the start time and end time of the receiver
window.
OPR
FORCELOAD
Use this command to specify whether to

enable a board to forcibly load a backup
configuration data file.
The OMU starts a scheduled task at 03:57
every morning. A board reads memory data in
use and transmits it to the OMU, and the OMU
formats, compresses, and saves the data as a
file. This file will be forcibly loaded by a board
for service recovery.
REL UHOSTRNC
Use this command to release the control rights

of a logical RNC when the RNC in Pool Node
Redundancy feature is enabled. After the
command is executed on this physical RNC,
the physical RNC releases the control rights of
dual-homing NodeBs and the peer physical
RNC takes over the control rights.
RMV AAL2PATH
Use this command to remove an AAL2 path.
RMV AAL2RT
Use this command to remove an AAL2 route.
RMV ACLRULE
Use this command to remove an ACL rule.
RMV ADJMAP
Use this command to remove a transport

resource management (TRM) mapping from
an adjacent node.
RMV ADJNODE
Use this command to remove a transport

adjacent node.
RMV BRD
Use this command to remove a board. This

command is used on all types of boards
except the SCUb, SCUc,GCUa, GCGa,
GCUb, GCGb, EGPUa(RMP) and
EGPUb(RMP).
Use this command to remove a link from a

RMV ETHTRKLNK trunk group. This command is applicable to
the EXOUa, FG2c, GOUc and GOUe boards.
RMV EXTNODE
Use this command to remove an external

node. An external node indicates a base
station controller which exchanges data with
the local base station controller.
RMV GPS
Use this command to remove a GPS receiver.
RMV LOGRST
Remove log result information collected by

command "COL LOG".
RMV M3RT
Use this command to remove an M3UA route.
RMV ME
Use this command to delete a management

entity (ME).
RMV MTP3LNK
Use this command to remove an MTP3

signaling link.
RMV MTP3RT
Use this command to remove an MTP3

signaling route.
RMV OP
Use this command to remove an operator

account from the system.
RMV OPC
Use this command to remove an OSP.
RMV PATCH
Use this command to remove hot patches

from a specified board.
RMV
SNTPSRVINFO
Use this command to remove the information

of the SNTP server connected to the NE.
RMV SUBRACK
Use this command to remove a subrack.
RMV
TRUSTCERT
Use this command to remove the CA

certificate file or the CA certificate chain file
that has been added to the MBSC.
RMV UCBSAREA
RMV UCCP
RMV UCELL
RMV
UCELLCBSSAC
RMV
UCELLFACHCON
GCTRL
RMV
UCELLINTERRAT
DR
RMV
UCELLQUEUEPR
EEMPT
Use this command to remove the broadcast

area for simple CBS.
Use this command to remove a
CCP(Commuication Control Port) link.
Remove cell configuration parameters and
neighbor cell relation simultaneously.
Use this command to remove the Service Area
Code (SAC) of Cell Broadcast Service (CBS)
from a cell.
Remove Parameters for Cell-orientated FACH
Use this command to remove the Cell-oriented
Remove Cell-Orientated Queuing and
Preemption Algorithm Parameters.
RMV
Use this command to remove cell
UCELLRLACTTIM synchronized radio link reconfiguration
E
activation time offset.
Use this command to remove the specific Non
RMV
Access Stratum (NAS) information and
UCNDOMAIN
Discontinuous Reception (DRX) cycle length
coefficient of Core Network (CN) domain.
RMV UCNNODE
Use this command to remove a CN node.
RMV
UEXTNODEB
Use this command to remove the information

about an external NodeB.
RMV
UFACHDYNTFS
Use this command to remove the transport

format Set (TFS) of a FACH.
RMV
UIURGCONN
Use this command to remove an Iur-g

connection.
Use this command to remove a neighboring
RNC.
RMV UNRNC
RMV URNCBASIC
Use this command to remove RNC basic

information
RMV
URNCCBCPUID
Use this command to remove main CPUID of

RNC broadcast message.
RMV
Use this command to unlock the logical RNC
URNCHOSTLOCK control right for the RNC in Pool feature.
RMV URNCMAP
Use this command to remove mapping

between Logical RNC and Physical RNC.
RMV URNCPOOL
Use this command to remove a RNC POOL

Config Parameter.
RMV
Use this command to remove a RNC POOL
URNCPOOLMEM
member.
BER
RMV USAS
Remove SAS configure.
RMV USCCPCH
Use this command to remove a SCCPCH.
Remove the configuration of a typical traffic

RAB.
RMV UTYPRAB
Stratum (AS) provides to the Non Access
Stratum (NAS) for transfer of user data
between the User Equipment (UE) and the
Core
Network
(CN).
Remove
measurement
control parameters of
the Dynamic Channel Configuration Control
(DCCC) algorithm. These parameters are
applicable to PS domain Best Effort (BE)
services, which are relatively insensitive to the
delay.
RMV
BE is to transmit data with all efforts when
UTYPRABDCCCM resources are available. BE services usually
C
refer to background or interactive services of
PS domain. This type of service has features
such as large probability of burst transmission
of service source data, great tolerance of
transmission delay, no requirements for
transmission rate, and low error rate of
transmission data.
Remove dynamic transport format parameters
RMV
of typical RAB, including the number of
UTYPRABDYNTF
Transport Blocks (TBs) and the size of TB.
RMV
Remove HSPA information for a typical
UTYPRABHSPA service.
RMV
Use this command to remove the sub-flow
UTYPRABHSUPA HSUPA Power Control parameters of a typical
PC
traffic RAB.
Use this command to remove the sub-flow
OLPC parameters of a typical traffic RAB.
OLPC: Outer Loop Power Control. The OLPC
algorithm adjusts the target values for the
RMV
inner loop power control based on the
UTYPRABOLPC communication quality, such as the Block Error
Error Rate (FER) parameters. Thus, the
minimum power can always meet the
communication requirements.
RMV
UTYPRABRLC
Remove Radio Link Control (RLC) parameters

for a subflow of a typical Radio Access Bearer
(RAB), such as RLC mode and RLC flow
control parameters.
Use this command to remove the semi-static

transport format parameters of typical RAB,
including the transmission time interval, the
rate matching attribute, the size of CRC, the
channel code type and the coding rate.
RMV
Semi-static parameter: Semi-static parameters
UTYPRABSEMIST are the parameters whose values remain
ATICTF
unchanged after transport format sets of a
transport channel are set.
This command can be executed only when the
typical parameters are deactivated. If this
command is executed, the parameter cannot
be activated.
Use this command to remove a typical RAB
sub-flow.
RMV
Typical RAB can be divided into several subUTYPRABSUBFL flow to transmit user data. For example, three
OW
sub-flows can be configured for AMR speech
service. Only one sub-flow is needed for each
of other services.
RMV
UTYPRABTOAW
RMV UTYPSRB
Use this command to remove time window

parameters for a typical service.
To receive the DL data frames, a receiving
window is configured at the service setup and
reconfiguration phases for monitoring whether
the data frames are received within this
window. The start point and end point are
configured here.
Remove the configuration of a typical
Access Stratum (AS) provides to the Non
signaling.
After this command is executed, the
configuration related to the specified typical
SRB is removed completely.
RMV
Remove AM RLC Parameters from
UTYPSRBDCHRN
CELL_DCH SRB on the RNC Side.
CRLC
Use this command to remove the dynamic
transport format parameters of typical SRB.
Dynamic transport format parameters: specify
the number and size of transport blocks
recorded to the dynamic transport format to be
removed.
RMV
UTYPSRBDYNTF Access Stratum (AS) provides to the Non
signaling.
typical SRB are deactivated. If this command
is executed, the typical SRB cannot be
activated.
RMV
Remove HSPA information for a typical
UTYPSRBHSPA signalling.
Use this command to remove the HSUPA
Power Control parameters of a typical
RMV
UTYPSRBHSUPA
PC
signaling.
After this command is executed, the related
OLPC configuration of the specified typical
Remove the Outer Loop Power Control
(OLPC) parameters of a typical Signaling
Radio Bearer (SRB).
RMV
UTYPSRBOLPC Access Stratum (NAS) for transfer of
signaling.
After this command is executed, the related
OLPC configuration of the specified typical
RMV
UTYPSRBRLC
Use this command to remove the typical SRB

RLC parameters.
Use this command to remove the semi-static

transport format parameters of typical SRB,
including the transmission time interval, the
rate matching attribute, the size of CRC, the
channel code type and the coding rate..
RMV
Semi-static parameter: the parameter whose
UTYPSRBSEMIST
value does not change in the duration of the
ATICTF
existence of the transport channel.
typical SRB are deactivated. If this command
is executed, the typical SRB cannot be
activated.
Use this command to remove time window
parameters for a typical signaling.
To receive the DL data frames, a receiving
RMV
window is configured at the signaling setup
UTYPSRBTOAW and reconfiguration phases for monitoring
whether the data frames are received within
this window. The start point and end point are
configured here.
RST AAL2PATH
Use this command to reset an AAL2 path.
RST BRD
Use this command to reset boards.
RST BSC
Use this command to reset all the subracks in

the entire RNC system .
RST DB
Use this command to reset database on the

OMU.
RST FAN
RST GPS
Use this command to reset the specified fan

box.
Use this command to reset the GPS receiver.
RST JTGBRD
This command is used to reset a specified

board forcibly through JTAG.
RST ME
Use this command to reset the Management

Entity.
RST OMU
Use this command to reset the software or

hardware of the OMU.
RST
OMUMODULE
Use this command to reset the specified OMU

module.
RST PWR
RST SAU
RST SUBRACK
Use this command to reset the specified

power allocation monitoring unit.
Use this command to reset the software or
hardware of the SAU.
Use this command to reset the specified

subrack.
RST SUBSYS
Use this command to reset a specified

subsystem.
RST UIU
Use this command to reset the Iu interface.
RST UIUR
Use this command to reset an Iur interface.

This is one of the methods to clear the fault of
the Iur interface.
RST UNODEB
Use this command to reset a NodeB on the

RNC side when the remote OM channel of the
NodeB is faulty but the signaling channel
works properly.
RTR ME
Use this command to restore data and files of

the Management Entity.
SET
ATMBRDBIND
SET
BRDBIND2ME
When an AAL2PATH is being configured over

the Iu-CS, Iur, or NNI_AAL2SWITCH
interface, the system binds the ATM interface
board that carries the AAL2PATH to a GPU
board. The GPU board manages the
AAL2PATH. If the GPU board is faulty, the
AAL2PATH becomes unavailable. In this case,
use this command to bind this ATM interface
board to another GPU board. An ATM
interface board can be bound only to one GPU
board. After this command is executed, the
system ends the binding relationship between
the ATM interface board and the faulty GPU
board.
Use this command to set the binding
relationship between a management entity
(ME) and an GASP board.
SET CONNTYPE
Use this command to set the connection type

that the NE supports.
SET CTFTST
Use this command to set the type of

certification test.
SET ETHSWITCH
SET FACFG
Use this command to set the fault diagnosis

parameters.
Use this command to set the basic information
about the fault analysis center.
SET
FCCOMMPARA
Use this command to set common parameters

for flow control.
SET FCCPUTHD
Use this command to set CPU usage

thresholds for flow control.
SET
FCMSGQTHD
Use this command to set packet queue usage

thresholds for flow control.
SET
FTPCLTPORT
Use this command to set the range of the data

ports on the FTP client.
SET FTPSSRV
Use this command to set the security policy of

the FTP server.
Use this command to set the configuration

SET
information about the interface board selfINFBRDRESCFG
healing.
SET LOGCFG
Use this command to set the log record mode

of an OMU process.
SET LOGLIMIT
Use this command to set the storage limit of

the operation log and security log.
SET
MIXSCUPORT
Use this command to set the attributes of SCU

panel ports when the SCUb board is replaced
by the SCUc board, the SCUc board is
replaced by the SCUb board. When an SCU
panel port is enabled or disabled by using this
command, the alarm function of this port is
enabled or disabled simultaneously.
SET NODE
Use this command to set information for a

local node, which uniquely indicates the local
base station controller.
Use this command to set whether to check the

version of the service awareness rule library
file and to specify the version to check. This
SET RULELIBVER
helps a U2000 operator that has the right to
operate the SG_0 command group monitor
the service awareness rule library.
SET SCHTSKSW
Use this command to set the status of a

scheduled task to ENABLED or DISABLED.
SET SCUPORT
Use this command to configure the panel port

of the SCU board. When the panel port on the
SCU board is enabled or disabled by running
this command, the alarm function of this port
is also enabled or disabled.
SET SLFSLVSW
Use this command to set the OMU self-healing

switch.
SET
Use this command to set SS7 patch switch
SS7PATCHSWITC
parameters.
H
SET
SSLAUTHMODE
Use this command to set the SSL

authentication mode of the NE.
SET SUBNET
SET TIME
SET TZ
Use this command to set the subnet number

of the internal IP address of the RNC.
By default, the subnet number is 172 and the
extended subnet number is 16. If the subnet
number of the internal IP address conflicts
with the subnet number of the external IP
address of the RNC, you can use this
command to modify the internal subnet
number.
Use this command to set the OMU's time.
Use this command to set the time zone and

daylight saving time to ensure a correct local
time for the current system.
Use this command to set Call Attempts Per

Second(CAPS) Control Parameters.
In the case of extreme traffic impact, a mass
of resources(including radio resource and
SET
transmission bandwidth) are occupied by
UCALLSHOCKCT processing RRC CONNECTION REQUEST,
RL
which causes no sufficient resource to process
RAB ASSIGNMENT REQ. That leads to most
call procedure fails.
RNC will take flow control on RRC to maintain
steady call traffic by CAPS control algorithm.
SET
UCHRSCOPE
Use this command to set the applicable scope

of the cell-oriented CHR switch.
SET
Use this command to set UE timers and
UCONNMODETIM
constants in connected mode.
ER
Use this command to set the mode for

SET
adjusting the CP and UP subsystems and
UCPUPFLEXCFG
related parameters.
Use this command to set the basic parameters

of the DSAC (Domain Specific Access
Control ) algorithm at the RNC level.The
DSAC feature works as follows. When a CN
SET
node enters into the overload congestion
UDSACAUTOALG
state, the RNC controls the access in the
O
domain(s) of the node operator. In this way,
the RNC helps to prevent the congestion on
the CN node from deteriorating and to ensure
the network stability and security.
SET
Use this command to set the RNC-oriented
UEVENTCHRCTR switch for reporting call history records (CHRs)
L
in event blocks.
SET
UEVENTCHRSWI
TCH
SET UGTPU
SET
UIDLEMODETIME
R
Use this command to set the event CHR

process switch.
Set GTP-U configuration attributes.
Use this command to set UE timers and
constants in idle mode.
Use this command to set Iu interface RAN

SET
application part (RANAP) timers and counters,
UIUTIMERANDNU including "Times of resending reset message
M
to CN", "TRafc", "TRatc", "CN protection
timer", "TigOR", and "TinTR".
SET
Use this command to set the KPI self-healing
UKPISELFCUREP
parameters for the RNC.
ARA
Set the logical channel priority for each traffic
class.
SET ULOCHPRIO
Logical channel priority indicates the priority of
a signaling Radio Bearer (RB) of a single UE.
SET UMRCTRL
Use this command to set RNC parameters

related to the collecting of measurement
reports used in network performance analysis,
network planning, network optimization, and
call history analysis.
SET UMRSCOPE
This command is used to set RNC-level or

cell-level MR switches.
SET
UNODEPARA
Use this command to set local node

parameter.
Use this command to set Iu-Flex or MOCN

SET
support flag according to CN domain of a
UOPERATORCFG CNOPERATOR, NNSF timer length,NRI
PARA
length, NullNRI and set domain information
update switch.
SET
Use this command to set RNC operator
UOPERATORSHA
sharing mode.
RINGMODE
SET
UPOOLFLOWCT
RLPARA
Use this command to set parameters related

to the RNC in Pool Control-Plane & UserPlane Load Sharing Isolation function.
SET
Use this command to set RNC in Pool controlUPOOLLOADSHA plane and user-plane load sharing
REPARA
parameters.
SET
UPOOLRELIABILI
TYPARA
SET
UPSINACTTIMER
SET
URNCCBPARA
SET
URNCCHRSCOP
E
Use this command to set the switch for

enabling the RNC in Pool feature and the
related parameters.
Use this command to set PS user inactive
detecting timer.
Use this command to set internal CBS
parameter.
Use this command to set the applicable scope
of the RNC-oriented CHR switch.
SET
Use this command to set the RNC-level MR
URNCMRSCOPE scope control switch.
SET
URNCPOOLCFG
CTRL
Use this command to set the mode for

synchronizing RNC in Pool configuration data.
SET
Use this command to set the RNC time
URNCTIMEPARA parameters.
SET
USERVFCPRIO
Use this command to set service flow control

priority.
SET
USTATETIMER
Use this command to set the state protection

timers of calling process.
SET UTGPSCP
Use this command to set transmission gap

pattern sequence combination parameters. In
compressed mode, the RNC gets the
transmission gap pattern sequence based on
the [CM cell type] parameter of the best cell.
SET UUEA
SET UUIA
Use this command to set the UMTS

Encryption Algorithms (UEAs) supported by an
RNC. According to the protocol, the RNC
supports only two encryption algorithms
currently, UEA0 and UEA1. UEA0: Not
encrypted. UEA1: f8 encryption algorithm.
Use this command to set the UMTS Integrity
Algorithm (UIA) supported by an RNC.
According to the protocol, the RNC supports
only UIA1 currently, that is f9 integrity
protection algorithm(f9 means a kind of
integrity protection algorithm).
SET
Use this command to set the load sharing
UUSERPLNSHAR
parameters for the user plane.
EPARA
STP BATCHFILE
Use this command to stop the execution of the

current batch file.
STP DATASYNC
Use this command to stop data

synchronization between a pair of active and
standby OMUs.
STP SCHTSK
Use this command to stop a scheduled task.
STP UPGRADE
Use this command to stop the upgrade server.
STP UPSRV
Use this command to manually stop OMU

operating system (OS) patch installation
server.
Use this command to bind a static ARP entry.

When an ARP fault occurs on the transport
network or transmission equipment, a static
ARP entry is bound to temporarily rectify the
ARP fault. This command takes effect only
within the specified time, and the bound static
STR INTARPBIND
ARP entry is automatically deleted when the
time expires. This command is executed only
during transport network fault troubleshooting
to reduce the service interruption duration.
This command is suitable for the FG2c,
GOUc, GOUe, or EXOUa board.
STR
OMUPXESRV
Start OMU PXE(Preboot Execution

Environment) service.
SWP BRD
Use this command to forcibly switch over the

specified active and standby boards. After this
command is run, the active board is switched
over to the standby status and is reset, while
the standby board is switched over to the
active status.
SWP
MBSCMODE
Use this command to switch the working mode

of the NE.
SWP OMU
Use this command to switch over the active

and standby OMUs.
SWP OMUAREA
Use this command to switch over the working

area of the OMU.
SWP SAUAREA
Use this command to switch over the working

area of the SAU.
SYN BRDAREA
Use this command to forcibly load the files in

the active or standby workspace of the OMU
to the respective workspace of a board.
UNI ME
Use this command to uninstall the

Management Entity.
UPD FAN
Use this command to update the fan box

software in specified subrack.
UPD JTGCPLD
Upgrades the CPLD through JTAG(Joint Test

Action Group).
UPD PWR
Use this command to update the power

allocation monitoring unit software in specified
subrack.
Command List
t provides a list of high-risk commands, and running any of these commands will severely affect or even interrupt ongoing services or se
Note
1. If the ACL binds the port using the "ADD PACKETFILTER" command, "Destination IP Address" in the configured
ACL rules must be set to the IP address of the board configured with the port corresponding to "ACL ID". If the
board is configured in active/standby mode, "Destination IP Address" can also be set to the IP address of the active
or standby board.
2. After an ACL rule is added, the port binding the ACL can process packets that meet the ACL rule.
The execution of this command affects services. Run this command under the guide of an engineer from Huawei
Customer Service Center.
None
1. The MPS is configured by the system itself. However, you can run MML commands to move the MPS to another
subrack.
2. Before adding a subrack, ensure that the cabinet where the subrack is added exists, for details about how to add
subracks, see the following section: Product Documentation > RAN Reconfiguration Guide for BSC6910 > Adding a
Board or a Subrack.
3. The actual board type in the subrack must be consistent with the configured type. The subrack number of the
Main Processing Subrack(MPS) and the Extended Processing Subrack(EPS) must be consistent with that
indicated by the DIP switches.
4. After a subrack is added, the "SET SCUPORT" command must be executed to enable the ports on the SCU
board in the MPS.
5. Data configured when the system is in ineffective mode does not take effect in boards. You can run the "SET
CFGDATAEFFECTIVE" command to set the system to effective mode.
6. If the system is in effective mode, the data configuration takes effect after the added subrack is reset by running
the "RST SUBRACK" command.
7. The subrack must be installed in the corresponding cabinet. Otherwise, the cabinet power management is
affected. The relation between the parameter "Subrack No." and the parameter "Cabinet No." is described as
follows: "Cabinet No." = "Subrack No."/3. "Cabinet No." is the quotient of that formula.
8. To add a subrack whose type is EPS, ensure that a Y-shaped clock cable is connected to the subrack.
Otherwise, services on the subrack will be affected.
Adding a debugging message will interrupt ongoing services. Therefore, perform this operation under the guidance
of Huawei technical personnel.
1. The IP address of the RNC is configured by running the "ADD DEVIP" command at the transport layer.
2. If IP address of the RNC is not in the same subnet as that of the CBC, an IP route is needed.
3. The CBSADDR can not be configured when excuted "ADD URNCCBCPUID",and it can be configured unless
excute "RMV URNCCBCPUID".
4. The default values of "RNCIPADDR" and "RNCIPADDR2" are 255.255.255.255, which is an invalid IP address.
That is, the default setting for these parameters is the same as when they are left blank.
5. When the CBS server is configured to work in independent mode, the CBS server requires one CP subsystem.
Under this circumstance, "SECONDCBCFLAG" is set to OFF. When the CBS server is configured to work in
active/standby mode, the CBS server requires two CP subsystems. Under this circumstance, "SECONDCBCFLAG"
is set to ON. The number of CP subsystems required by CBS servers must be less than or equal to the total
number of CP subsystems.
1. If there are UCS2 characters in broadcast messages, set Coding Scheme to UCS2.
2. After this command is executed, the disaster warning message will be sended.
1. Emergency call services are allowed in any cell not barred, even if the cell is reserved. If it is necessary to
restrict emergency call services, "Access class 10 barred indicator" should be set as BARRED. In this case, the
UEs allocated with Access Class 0~9 or without IMSI cannot originate emergency calls in the cell. If the access
class 10 and 11~15 barred indicators are all set as barred, the UEs allocated with Access Class 11~15 are not
allowed to originate emergency calls.
2. The cell must be deactivated before the command is executed.
If the "CsRestriction" or "PsRestriction" is set to TRUE, executing this command imposes access restrictions on the
CS or PS domain.
If RNC-level and cell-level FACH congestion control parameters are both set, the values of cell-level FACH
congestion control parameters prevail. If you need to reconfigure a cell-level parameter, note that other cell-level
parameters in this command must inherit the values of their RNC-level parameters. For RNC-level parameters, see
the Parameter Relationship columns.
Alert information for this risky command: This command is only used to configure the Automatic Congestion
Handler feature. When this feature is enabled, the RNC automatically executes this command. Therefore, manual
execution of this command is not recommended.
None
When RNC-level and cell-level inter-RAT retry control parameters are both set, the values of cell-level parameters
prevail. When you need to reconfigure a cell-level parameter, note that other cell-level parameters in this command
must inherit the values of their corresponding RNC-level parameters. For the RNC-level parameters for each
parameter, see the Parameter Relationship column.
1.If RNC-level and cell-level Queuing and Preemption Algorithm Parameters are both set, the values of cell-level
Queuing and Preemption Algorithm Parameters prevail. If you need to reconfigure a cell-level parameter, note that
other cell-level parameters in this command must inherit the values of their RNC-level parameters. For RNC-level
parameters, see the Parameter Relationship columns.
2. Alert information for this risky command: This command is only used to configure the Automatic Congestion
If the parameters in this command are inappropriately set, call drops or access failures occur.
reallocate UEs to the corresponding CNs based on the mapping between the CN ID and the IMSI to avoid errors.
The setting of "CNId" must be consistent between the RNC and CN. If "CNId" on the CN is set to 5, "CNId" on the
RNC must also be set to 5.
3. When the Iu Flex function is enabled, a maximum of 32 CN nodes can be configured in each CN domain, which
can be either the CS domain or the PS domain. In addition, "CNProtclVer" for these CN nodes must be set to R5 or
later.
4. After "CNProtclVer" is set, "SupportCRType" will be displayed.
(1) When "CNProtclVer" is R99, "SupportCRType" can be CR527_SUPPORT or CR527_NOT_SUPPORT.
(4) When "CNProtclVer" is R6 or later, "SupportCRType" is invalid.
CR527, CR528, and CR529 correspond to R99, R4, and R5 respectively. Their contents are the same.The
extension IEs are added to RB and SRB mapping on transport channels in messages
RANAP_RELOCATION_REQUEST and RANAP_RELOCATION_REQUIRED on the Iu interface. The extension
IEs are HSDSCH and EDCH ID.
The modification of CR type will modify relocation message IEs, and affect the coding and decoding procedures of
RANAP_RELOCATION_REQUEST and RANAP_RELOCATION_REQUIRED on the Iu interface during static
relocation. Before testing static relocation, check whether the CN protocol version supports this CR type. If so, the
RNC protocol version must support it; if not, the RNC cannot support it. If the protocol versions are inconsistent
between the CN and the RNC, decoding fails when both of the following conditions are met:
-The RNC receives a RANAP_RELOCATION_REQUEST message or the CN receives a
RANAP_RELOCATION_REQUIRED message.
-The value of the Relocation Type information element (IE) in the two messages is UE not involved in relocation of
SRNS.
Then, the RNC or CN returns a RANAP_ERROR_INDICATION message.
5. When "CNDomainId" is set to CS_DOMAIN, "Switch3GPP25415CR0125" is displayed. When this switch is
turned on, the maximum bit rate (MBR) for the reverse direction is included in the ACK message specific to the
IuUP rate control procedure for AMR services. When this switch is turned off, the MBR for the current direction is
included in the preceding message. If the setting of this switch on the RNC side is inconsistent with that on the CN
side, exceptions will occur in the IuUP rate control procedure, leading to deteriorated CS speech quality. Before
setting this switch, check whether the CN protocol version supports 3GPP25415CR0125. If yes, the RNC protocol
version must also support this CR. If no, the RNC protocol version cannot support this CR.
6. The five parameters "Dpx", "NI", "SPCBITS", "OPCSPDF" and "DPCSPDF" can be set in three ways:
(1) All the five parameters are set, and mandatory subsidiary parameters are set as required.
(2) Among the five parameters, only the "Dpx" parameter is not set, and mandatory subsidiary parameters are set
1.The
function of quickly blocking all the cells only can chose one of the following methods: quickly bolcking all the
as required.
cells
the RNC
or quickly
blocking
all theiscells
(3) Ininmain
RNC,("ADD
amongURNCALLCELLBLK")
the five parameters, only
the "Dpx"
parameter
set.of the designated operator in the
RNC("ADD
UCNOPALLCELLBLK").
That
means
the
MML
command
"ADD
URNCALLCELLBLK"
and "ADD
7. The settings of the optional parameters "NI", "SPCBITS", "OPCSPDF", and
"SPC" in this command
must be
UCNOPALLCELLBLK"
can
not
executed
in
the
same
time.
consistent with those in the "ADD OPC" command.
2.The
blocking
all the cells
of the
designatedand
operator
RNC
only permit
the cells
8. Thefunction
settings of
of quickly
the optional
parameters
"Dpx",
"DPCSPDF",
"DPC"ininthe
this
command
musttobeblock
consistent
with
of
one
operator
in
the
same
time.
those in the "ADD N7DPC" command.
3.
Running
this command
will maketothe
belonging
to in
thenetwork
operator
fail to establish
service under
thethe
domain
9. This
command
can be executed
setusers
parameters
used
planning
and interconnection
with
CN.
which
is chosen
on LMT. settings affect network access.
Inappropriate
parameter
Adding a transport format (TF) will affect the calculation of the CTFC of the SCCPCH bearing this FACH, which
may adversely affect services. Therefore, the SCCPCH CTFC should be calculated again after a new TF is added
("ADD USCCPCHTFC","RMV USCCPCHTFC").
1. Presently up to 278 neighboring RNC can be added to one RNC. Up to 128 neighboring RNC can be added to
one Logical RNC.
2. The IUR interface cannot be used when the "Dpx" is not filled between this RNC and the neighboring RNC.
3. The transmission bearer type set in this command should be the same as the corresponding adjacent node's
transmission bearer type, which is set by using command "ADD ADJNODE".
4. If "Dpx" needs to be set, the five parameters "Dpx", "NI", "SPCBITS", "OPCSPDF" and "DPCSPDF" can be set
in three ways:
(2) Among the five parameters, only "Dpx" is not set, and mandatory subsidiary parameters are set as required.
(3) In main RNC, among the five parameters, only "Dpx" is set.
5. The settings of the optional parameters "NI", "SPCBITS", "OPCSPDF", and "SPC" in this command must be
6. The settings of the optional parameters "Dpx", "DPCSPDF", and "DPC" in this command must be consistent with
7. When NRNCID is set to a value greater than 4095, RESERVED_SWITCH_12_BI32 under the "RsvSwitch12"
parameter in the "SET UALGORSVPARA" command must be set to 1. Otherwise, the success rates of cross-Iur
handovers
and SRNS
relocations
1.
The function
of quickly
blocking decrease.
all the cells only can chose one of the following methods: quickly bolcking all the
cells in the RNC ("ADD URNCALLCELLBLK") or quickly blocking all the cells of the designated operator in the
RNC("ADD UCNOPALLCELLBLK"). That means the MML command "ADD URNCALLCELLBLK" and "ADD
UCNOPALLCELLBLK" can not executed at the same time.
2. Running this command will make the users in the RNC fail to establish service under the domain which is
chosen on LMT.
1. This command is an emergency measure to switch over the logical RNC control right to the backup RNC only
when the switchover fails using the FOC UHOSTRNC or REL UHOSTRNC command. After this command is
executed for the backup RNC to obtain and lock the logical RNC control right, the FOC UHOSTRNC or REL
UHOSTRNC command does not work on either the master or backup RNC.
2. This command cannot be executed simultaneously for the master and backup RNCs. Otherwise, the control right
is switched over to the configured master RNC.
3. This command takes effect only when manual redundancy mode is used.
4. After this command is executed, ALM-22307 RNC in Pool Function Unavailable is reported. Contact Huawei
technical support to resolve the failure to manually switch over the logical RNC control right, and then run the RMV
URNCHOSTLOCK command to unlock the control right. If this alarm is not reported following the ADD
URNCHOSTLOCK command execution, contact Huawei technical support.
5. This command does not apply to the GU mode.
1. Based on the product specifications, it is recommended that the CCPCHs in a cell be identified as follows:
1)The ID of the PSCH is 0.
2)The ID of the SSCH is 1.
3)The ID of the PCPICH is 2.
4)The ID of the PCCPCH is 3.
5)The ID of the PRACH #1 is 4. The ID of the corresponding AICH is 6.
6)The ID of the SCCPCH #1 is 8. The ID of the corresponding PICH is 10.
7)The ID of the SCCPCH #2 is 9.
2. In order that a downlink in a cell can transmit in diversity (whether open loop or closed loop), the CPICH in the
cell should have the 2-antenna transmit configuration.
3. Based on the Spreading Factor (SF), the number of pilot bits (Npilot) and the number of Transport Format
Combination Indicator bits (NTFCI), the slot format of a SCCPCH can be determined. For their relationships, refer
to the following table:
4. Note that if TFCI bits are not present, Discontinuous Transmission (DTX) should be used instead for the TFCI
field.
5. The number of Transport Format Combinations (TFCs) is limited by the parameter "CTFC Length of TFCS".
"CTFC Length of TFCS" is hard to be modified after the SCCPCH is set up. The number of TFCs should be
planned before the SCCPCH is set up.
The blocked AAL2 path cannot carry new services. The existing services are not affected.
1. The type and blocking status of a subsystem can be queried by running the "LST SUBSYS" command.
2. A subsystem can be unblocked by running the "UBL SUBSYS" command.
3. When this command is executed with "Operator Type" set to BYPOS, all the subsystems with the type of UUP,
NIU or UUEP in the board are blocked. If there is no subsystem with the type of UUP, NIU or UUEP in the board,
the command fails to be executed.
4. When this command is executed with "Operator Type" set to BYSSN, the command fails to be executed if the
specified subsystem is not of the UUP, NIU or UUEP type.
5. If a subsystem of the UUP type is blocked, the system automatically reallocates the cells processed by this
subsystem to another subsystem of the UUP type. This does not affect the ongoing services and new services will
no longer be allocated to the blocked subsystem.
6. If a subsystem of the NIU type is blocked, the system automatically interrupts the service awareness function on
the subsystem.
7. If a subsystem of the UUEP type is blocked, ongoing Seamless Crystal Voice services are not affected and new
Seamless Crystal Voice services will no longer be allocated to the blocked subsystem.
1. There are three block priorities: high, normal and low.

2. High priority: Blocking a cell immediately.
3. Normal priority: Blocking a cell once there are no CELL_DCH and CELL_FACH users in it within a specified
time, or blocking it even if there are some users when the specified time expires.
4. Low priority: Blocking a cell when there are no CELL_DCH and CELL_FACH users in the cell.
Running this command will make the NODEB unavailable.

1. Running this command will cause the ME to be reset.
2. The IP addresses specified by "External network fixed IP 1" and "External network fixed IP 2" must be planned
and unused.
3. To delete the IP addresses specified by "External network fixed IP 1" and "External network fixed IP 2", set the
two parameters to 0.0.0.0.
1. Activated state means that at least one link in the link set is in activated state. Deactivated state means that each
link in the link set is not in activated state, and at least one link in the link set is in deactivated state.
2. Running this command will interrupt all the services carried on links in the deactivated MTP3 signaling link set.
Therefore, run this command with caution.
3. Running this command will make the DSP corresponding to the signalling link set unavailable. Therefore, run this
command with caution.
After an MTP3 signaling link in an MTP3 signaling link set is deactivated, load of other links in the same signaling
link set will be increased. If too many MTP3 signaling links of one Destination Signaling Point (DSP) are
deactivated, then, other links of this DSP will be congested. As a result, services related to this DSP will be
affected. If the last available link is deactivated, the all services will be interrupted.
None
Running this command will make the NODEB unavailable.
When a cell is activated, the prerequisite of removing a SCCPCH is that after removing this SCCPCH, the cell has
at least one activated SCCPCH which is carrying at least one PCH and one FACH.
1.Before executing this command, ensure that the typical traffic RAB is activated successfully.
2.Running this command deactivates the configurations of a typical traffic RAB. Once the configurations of a typical
traffic RAB are deactivated, these configurations cannot be allocated to a service whose traffic class is the same as
that included in these configurations. Moreover, since these configurations are deactivated, new services will fail to
be set up if the RNC cannot map a data rate onto the data rate assigned by the CN.
1.Before running this command, ensure that the typical SRB is activated.
2.Running this command deactivates the configurations of a typical SRB. After this, UEs to be allocated with these
configurations cannot access the network.
1. If you execute this command on the local RNC and execute the "FOC UHOSTNODEB" command on the peer
RNC, the control rights of the NodeB are switched from the local RNC to the peer one and ongoing services on the
NodeB are interrupted.
2. If this command is executed when the peer RNC is faulty (see "ADD URNCPOOL"), the primary homing NodeB
is switched over to the secondary homing NodeB, but the control rights of the NodeB cannot be switched over to
the peer RNC.
1. The NodeB must exist and must be the secondary homing NodeB or the primary homing NodeB.
2. If you execute this command on the local RNC and execute the "FOC UDEHOSTNODEB" command on the peer
RNC, the control rights of the NodeB are switched from the peer RNC to the local RNC and ongoing services on
the NodeB are interrupted.
3. If this command is executed when the local RNC is faulty (see "ADD URNCPOOL"), the secondary homing
NodeB is switched over to the primary homing NodeB, but the control rights of the NodeB cannot be switched over
to the local RNC.
1. This command can be executed only on the master RNC or backup RNC of a logical RNC. The command
execution causes online users to experience call drop.
2. You are not advised to execute this command on the logical RNC that is not mapped to another physical RNC by
running the "ADD URNCMAP" command.
3. You are not advised to execute this command on the logical RNC where "Redundancy Type" in the "ADD
URNCMAP" or "ADD URNCBASIC" command is set to NO_BACKUP.
4. This operation will preempt control rights of logical RNC.
1.To hand over a cell forcibly, there must be at least two cells in the system, and handover of multiple cells in the
same system cannot be implemented simultaneously.
2.If target cell parameter is not complete,the system will deal with the case as blind handover when blind handover
flag is true,or do nothing when the flag is false.
3.Forcible handover between different intra-frequency 3G cells is not supported.
4.Running this command causes UEs in the current cell to be forcibly handed over to other cells, which increases
the risk of call drops.
5.Due to the complex radio environment, this command cannot ensure that all the UEs in the current cell can be
handed over to other cells.
1. This command cannot be used to inhibit the boards of the SCU or OMU type.
2. The inhibition leads to the unavailability of a board. The board status shown in the output of the "DSP BRD"
command is inhibitiveand the device panel indicate that the board is blocked faulty. You must use such commands
with caution.
3. The inhibited board can be uninhibited by running the "UIN BRD" command.
4. To query the inhibitive status of a board, you can run the "LST BRD" command.
5. After a board is inhibited, the counter value for the board is unreliable in the first measurement period.
1. If there is only one MTP3 signaling link available to a DSP, you cannot inhibit this link. You can query all the
signaling links under "Signalling link set index" and "Operation state" of those signaling links by running the "LST
MTP3LNK" command and "DSP MTP3LNK" command, respectively.
2. After an MTP3 signaling link in an MTP3 signaling link set is inhibited, load of other links in the same signaling
link set will be increased. If too many MTP3 signaling links of one Destination Signaling Point (DSP) are inhibited,
then, other links of this DSP will be congested. As a result, services related to this DSP will be affected.
3. If the MTP3 signaling link is unavailable, you cannot inhibit or uninhibit this link. Otherwise, the actual link status
is inconsistent with the configured link status.
1. This command inhibits the DSP on the SCCP layer without affecting the services carried on the MTP3 link. To
enable the DSP, use the "UIN N7DPC" command.
2. If this command is executed successfully, all SCCP-related services to this DSP fail.
3. This command cannot inhibit the MGW signaling point.
After the active SCU board is reset, the inhibition of the standby SCU board is automatically uninhibited and the
1. The "INS ME" command is used to install an ME. Execution of this command is time-consuming.
subrack is reset because the active and standby SCU boards are resetting.
2. The value of the "OS Installed Package" parameter specifies the name of the OS installation package under the
relative path /mbsc/upgrade. For example, if the save path for the OS installation package is
/mbsc/upgrade/EulerLinuxV100R001C10B010-LXC.zip, set this parameter to EulerLinuxV100R001C10B010LXC.zip; if the save path is /mbsc/upgrade/guestos/EulerLinuxV100R001C10B010-LXC.zip, set this parameter to
guestos/EulerLinuxV100R001C10B010-LXC.zip. Multiple OS installation packages are separated by commas (,). If
this parameter is not specified, the system searches for the required OS installation package from application
installation packages.
3. The value of the "Application Installed Package" parameter must contain complete version information, such as
ECO6910V100R004C10.
4. The value of the "Work Mode" parameter must be consistent with the active/standby mode of the host OMU.
5. When the "Work Mode" parameter is set to DUAL(Double), the "External network fixed IP 1" and "External
network fixed IP 2" parameter must be both specified or neither specified.
6. The IP addresses specified by "External network fixed IP 1" and "External network fixed IP 2" must be planned
and unused.
7. For the ECO6910 ME, you do not need to specify the "MESUBNETIP" and "MESUBNETMASK" for internal
communication.For a non-ECO6910 ME, you must specify the "MESUBNETIP" and "MESUBNETMASK" for
internal communication, and the specified parameters cannot conflict with the IP addresses or network segments of
1.
the scheduled
tasks are locked in auto-unlock mode (that is, Auto Unlock Switch is set to ON), they will be
theIfBSC
or other MEs.
unlocked automatically one day later.
2. If the scheduled tasks are locked in non-auto-unlock mode (that is, Auto Unlock Switch is set to OFF), they will
be always locked and will not be unlocked automatically.
3. Running this command will disable all the tasks from being performed at a scheduled time.
1. CPU usage increases during board rule library loading after this command is executed. When the current CPU
usage is higher than 50% and the CPU usage exceeds a flow control threshold after this command is executed, the
flow control is triggered. When the CPU usage is excessively high, services are interrupted. Exercise caution when
performing this operation.
2. During the forced loading, the host is not reset and the current running program is not impacted.
3. If multiple subracks load rule library at the same time, some boards may fail to load. Run this command again on
these boards to reload rule library.
1. If the ACL binds the port using the "ADD PACKETFILTER" command, "Destination IP Address" in the configured
ACL rules must be set to the IP address of the board configured with the port corresponding to "ACL ID". If the
board is configured in active/standby mode, "Destination IP Address" can also be set to the IP address of the active
or
standby
board.the command for boards whose board class is GPU, note the following:
1. When
running
2.
If
an
ACL
modified,
the portwhose
binding
the ACL
can process
only
packets
thatbemeet
the modified
ACLthe
rule.
1) The boardrule
typeisof
a GPU board,
logical
function
type is not
RMP,
cannot
changed
by running
1.In this command, the values of parameters "Adjacent Node Type", "Transport Type", and "Is Root Node" must be
"RUN BATCHFILE" command in effective mode.
consistent with those configured in the "ADD ADJNODE" command. You cannot modify those parameter settings
2. When running the command for boards whose board class is GCU, note the following:
by running this command. To modify those parameter settings, run the "RMV ADJNODE" add "ADD ADJNODE"
1) The GCUa is configured by default. The GCUa/GCUb does not support the GPS while the GCGa/GCGb
command.
supports the GPS.
2. When "Adjacent Node Type" is IUB or UNI_AAL2SWITCH and "Transport Type" is ATM or ATM_IP, you can
2) After the board type of a board is changed, check whether the new board type matches the board hardware.
modify "SAAL link No." and "Qaal2 Protocol Version".
3) Check whether a GPS is configured for a board before changing the board type of the board from GCGa/GCGb
3. When "Adjacent Node Type" is IUR, IUCS, or NNI_AAL2SWITCH and "Transport Type" is ATM, you can modify
to GCUa/GCUb using this command. If yes, remove the GPS using the "RMV GPS" command before changing the
"Qaal2 Protocol Version".
board type.
4)
If the the
board
type administrator
of a board is changed
from
GCUa/GCUb to GCGa/GCGb or from GCGa/GCGb to
1. Only
system
can run this
command.
GCUa/GCUb,
theaboard
of the corresponding
active/standby
board will be
changed
at the
same time.
2. Before setting
devicetype
certificate
file that is being
used by an application,
add
the device
certificate
file by
5)
If the the
board
typeCERTMK"
of a boardcommand.
is changed from GCUa to GCUb, from GCUb to GCUa, from GCGa to GCGb or from
running
"ADD
GCGb to GCGa, the board type of the corresponding active/standby board will remain unchanged. If the board
whose type is to be changed works in active/standby mode and the board is an active board, it is recommended
that the "SWP BRD" command be executed to switch over the active and standby boards. Change the board type
until the new active and standby boards work properly. This is to prevent any impact of command execution on the
ongoing services.
6) A board will reset after its board type is changed. Then, the services carried over the board are affected.
Therefore, exercise caution when running this command.
3. When running the command for boards whose board class is INT, note the following:
1) If the board type of a board is changed from GOUc to GOUe or from GOUe to GOUc, the board type of the
corresponding active/standby board will remain unchanged. If the board whose type is to be changed works in
active/standby mode and the board is an active board, it is recommended that the "SWP BRD" command be
executed to switch over the active and standby boards. Change the board type until the new active and standby
boards work properly. This is to prevent any impact of command execution on the ongoing services.
2) A board will reset after its board type is changed. Then, the services carried over the board are affected.
4. When running the command for boards whose board class is SCU, note the following:
1) If an EXOUa board in a subrack is configured in slot 14, 15, 26, or 27, the active SCU board in the subrack
cannot be changed from SCUc to SCUb.
2) After this command is executed, the SCU board whose board type is changed automatically resets, and services
on the SCU board are affected. Therefore, exercise caution when running this command.
3) In effective mode, [BRD:SN] must be specified. After this command is executed, the type of the board in the
specified slot is changed. In ineffective mode, the types of both the active board and the standby board are
changed after this command is executed regardless of whether [BRD:SN] is specified.
4) For an EPS, after the SCU type is changed from SCUb to SCUc by running the "MOD BRD" command, ports 0,
1, 2, and 3 on the SCUc board are enabled and the other ports are disabled by default. If you do not need to use
ports 0, 1, 2, and 3, run the "SET SCUPORT" command to disable these ports. If you do not disable these ports,
ALM-20227 Communication Between Subracks Faulty will be reported. Likewise, after the SCU type is changed
from SCUc to SCUb by running the "MOD BRD" command, ports 8 and 9 of the SCUb board are enabled and the
other ports are disabled by default. If you do not need to use ports 8 and 9, run the "SET SCUPORT" command to
disable these ports. If you do not disable these ports, ALM-20227 Communication Between Subracks Faulty will be
1. You can execute this command only after logging in to the OMU by using the local commissioning Ethernet port.
reported. For the MPS, after the SCU type is changed by running the "MOD BRD" command, all ports of the SCU
After this command is executed successfully, the OMU board will reset.
board are disabled by default. If you need to use a port, run the "SET SCUPORT" command to enable the port.
2. Only "INNERCARD", "EXTERCARD", "EXTERCARDMASK", "GATEWAY", and "BACKUPCARDIP" of the active
5) If SCU boards are faulty, run the "INH STANDBYSCU" command to inhibit the faulty boards. After the "MOD
OMU can be modified when OMUs are configured in active/standby mode.
BRD" command is executed, run the "UIN STANDBYSCU" command to uninhibit these boards.
3. After the OMU software starts, it automatically updates the first two network segments of the internal fixed IP
6) If the types of the active and standby SCU boards in a subrack are different, do not export configuration data
address and internal virtual IP address according to the configured network segments. You can query the
MML scripts by running the "EXP CFGMML" command nor export configuration data BCP files by running the "EXP
configured network segments by running the "LST SUBNET" command.
CFGBCP" command. If configuration data MML scripts by running the "EXP CFGMML" command in the preceding
scenario and are subsequently executed, configuration data after the script execution will be inconsistent with that
before the script exporting. If configuration data BCP files are exported by running the "EXP CFGBCP" command in
the preceding scenario and are subsequently executed, configuration data after the file execution will be
inconsistent
with that before the script exporting.
None
7) In effective mode, this command cannot be executed to change the type of the active SCU board.
5. The board whose board class is NIU cannot be modified in this version.
1. The SAAL link to be modified must exist, and the interface type cannot be modified.
2. Whatever the interface type is, the following constraints should be fulfilled:
RSPTMR > POLLTMR + 100;
RSPTMR > KEEPTMR + 100;
STATLEN is odd number.
3. When the interface type is NNI, the following constraints should be fulfilled:
CCTMR + 2 * POLLTMR <= 2000;
COMTMR2 * 1000 > COMTMR3 * (N1 + 2) + RSPTMR.
4. The parameters "TX traffic record index" and "RX traffic record index" must be set to the same value.
5. Running this command will interrupt the services related to the link. Therefore, run this command with caution.
6. Modifying an SAAL link interrupts the services carried on the link.
1. The factor table with index 0 is the default table in the RNC, and it cannot be modified.
2. User experience will be affected and KPIs will be degraded if a parameter except Remark is changed
improperly,Therefore, run this command with caution.
1. The transport resource mappings to be modified must be the default transport resource mappings or have been
configured by running the "ADD TRMMAP" command.
2. "Interface Type" and "Transport Type" cannot be modified.
3. User experience will be affected and KPIs will be degraded if a parameter except Remark is changed improperly.
Therefore, run this command with caution.
4. Ensure that the specified type of the path exists and is available by using "DSP AAL2PATH".
5. After mapping between services and DSCPs is changed, new DSCPs take effect after the services are
reestablished.
6. The primary path and the secondary path of the same traffic must be different from each other.
1. "PCPICH transmit power" should not be modified if the intra-frequency load balance algorithm(which is
configured by "MOD UCELLALGOSWITCH") is not closed.
2. PCPICH power must be between the Max and Min got by command "LST UPCPICH".
3. The mappings between the value ranges into which the configured S-CPICH transmit power falls and the actual
S-CPICH transmit power are as follows: ([-5,150], 0), ([-15,-6], -10), ([-25,-16], -20), ([-35,-26], -30), ([-45,-36], -40),
([-55,-46], -50), ([-350,-56], -60). The value range of the configured power is from -350 to 150.
1. [Intra-freq cell reselection indicator] and [Time barred] are valid only when [Cell barred indicator] is set as barred.
2. Emergency call services are allowed in any cell not barred, even if the cell is reserved. If it is necessary to
restrict emergency call services, [Access class 10 barred indicator] should be set as BARRED. Thus, the UEs
allocated with Access Class 0~9 or without IMSI cannot originate emergency calls in the cell. If the access class 10
and 11~15 barred indicators are all set as BARRED, the UEs allocated with Access Class 11~15 are not allowed to
originate emergency calls.
3. If the "IsAccessClassnBarred" is set to BARRED, executing this command enables the RNC to reject the access
requests of UEs whose access classes are n.
If the "CsRestriction" or "PsRestriction" is set to TRUE, executing this command imposes access restrictions on the
CS or PS domain.
None
When RNC-level and cell-level inter-RAT retry control parameters are both set, the values of cell-level parameters
prevail. When you need to reconfigure a cell-level parameter, note that other cell-level parameters in this command
must inherit the values of their corresponding RNC-level parameters. For the RNC-level parameters for each
parameter, see the Parameter Relationship column.
If the parameters in this command are inappropriately set, call drops or access failures occur.
None
3. When the Iu Flex function is enabled, a maximum of 32 CN nodes can be configured in each CN domain, which
can be either the CS domain or the PS domain. In addition, "CNProtclVer" for these CN nodes must be set to R5 or
later.
4. After "CNProtclVer" is set, "SupportCRType" will be displayed.
(4) When "CNProtclVer" is R6 or later, "SupportCRType" is invalid.
CR527, CR528, and CR529 correspond to R99, R4, and R5 respectively. Their contents are the same.The
extension IEs are added to RB and SRB mapping on transport channels in messages
RANAP_RELOCATION_REQUEST and RANAP_RELOCATION_REQUIRED on the Iu interface. The extension
IEs are HSDSCH and EDCH ID.
The modification of CR type will modify relocation message IEs, and affect the coding and decoding procedures of
RANAP_RELOCATION_REQUEST and RANAP_RELOCATION_REQUIRED on the Iu interface during static
relocation. Before testing static relocation, check whether the CN protocol version supports this CR type. If yes, the
RNC protocol version must support it; if not, the RNC cannot support it. If the protocol versions are inconsistent
between the CN and the RNC, decoding fails when both of the following conditions are met:
-The RNC receives a RANAP_RELOCATION_REQUEST message or the CN receives a
RANAP_RELOCATION_REQUIRED message.
-The value of the Relocation Type information element (IE) in the two messages is UE not involved in relocation of
SRNS.
Then, the RNC or CN returns a RANAP_ERROR_INDICATION message.
5. When "CNDomainId" is set to CS_DOMAIN, "Switch3GPP25415CR0125" is displayed. When this switch is
turned on, the maximum bit rate (MBR) for the reverse direction is included in the ACK message specific to the
IuUP rate control procedure for AMR services. When this switch is turned off, the MBR for the current direction is
included in the preceding message. If the setting of this switch on the RNC side is inconsistent with that on the CN
side, exceptions will occur in the IuUP rate control procedure, leading to deteriorated CS speech quality. Before
setting this switch, check whether the CN protocol version supports 3GPP25415CR0125. If yes, the RNC protocol
version must also support this CR. If no, the RNC protocol version cannot support this CR.
6. The five parameters "Dpx", "NI", "SPCBITS", "OPCSPDF" and "DPCSPDF" can be set in three ways:
(2) Among the five parameters, only the "Dpx" parameter is not set, and mandatory subsidiary parameters are set
as required.
Changing
MNC
and MCC
of an
operator will
cause
call drops
of all admitted
(3) In mainthe
RNC,
among
the five
parameters,
only
the "Dpx"
parameter
is set. users served by this operator.
Changing
the
MNC
and
MCC
of
the
primary
operator
invalidates
the
license
file.
This in
impact
will take effect
7. The settings of the optional parameters "NI", "SPCBITS", "OPCSPDF", and
"SPC"
this command
must after
be
the
RNC
is
restarted.
9.
This
can be
used
in network
planning
andadded
interconnection
the CN.
The
CNcommand
operator index
toexecuted
be addedtotoset
theparameters
CN operator
group
must exist.It
can be
through thewith
command
Inappropriate
parameter settings
"ADD
UCNOPERATOR"
ahead ofaffect
time. network access.
When an operator is added to or removed from an operator group, the licenses of the cells that belong to the
operators in the operator group change because different operators may have different licenses.
Cells that belong to the operators in the operator group will be removed and then reestablished. If the license for
any of the following features becomes unavailable, the cell reestablishment fails, or the cell is successfully
reestablished but the corresponding feature becomes unavailable:
Satellite transmission, MOCN, RAN sharing, CBS, HSDPA, HSUPA, HSPA+ features, and RNC in Pool.
1. The cell's HSDPA, HSUPA function must be inactive when the NODEB's protocol version is modified to R99 or
R4.The cell's EFACH, MIMO function must be inactive when the NODEB's protocol version is modified to lower
than R7.
2. RNC POOL feature is not supported in BSC6910. therefore, Parameter HOSTTYPE can not be modified with
PRIMHOST or SECHOST.
1. If "Dpx" needs to be set, the five parameters "Dpx", "NI", "SPCBITS", "OPCSPDF" and "DPCSPDF" can be set
in three ways:
(2) Among the five parameters, only "Dpx" is not set, and mandatory subsidiary parameters are set as required.
(3) In main RNC, among the five parameters, only "Dpx" is set.
2. The settings of the optional parameters "NI", "SPCBITS", "OPCSPDF", and "SPC" in this command must be
4. When the value of the "IurExistInd" parameter is changed from FALSE to TRUE, configure the DSP or OSP at
the same time. Alternatively, configure the Dpx.
1. The setting of "Source ATM address" can be changed in ineffective mode only.
2. All logical RNCs carried on the same physical RNC must have the same "source ATM address".
3. If "Redundancy Type" and "Load Sharing Type" are already set to MASTER(MASTER), their settings cannot be
modified.
4. If "Redundancy Type" and "Load Sharing Type" are not set to MASTER(MASTER), they cannot be changed to
MASTER(MASTER).
5. Before changing the setting of "Redundancy Type" from BACKUP(BACKUP) to NO_BACKUP(NO_BACKUP),
remove all NodeBs under the logical RNC.
6. UEs that are undergoing load sharing will experience call drops if you run this command and change the value of
"Load Sharing Type" from OVERFLOW to NO_OVERFLOW in effective mode. To prevent call drops, you are
advised to run the "SET UPOOLLOADSHAREPARA" command and disable the load sharing function before
running the command.
7. This operation may affect the services of online UEs.
This operation will modify mapping between logical RNC and physical RNC.
1. If "Redundancy Type" and "Load Sharing Type" are already set to MASTER(MASTER), their settings cannot be
modified.
2. If "Redundancy Type" and "Load Sharing Type" are not set to MASTER(MASTER), they cannot be changed to
MASTER(MASTER).
3. In load sharing scenarios, execution of this command with "LoadSharingType" set to NO_OVERFLOW leads to
call drops on UEs that are undergoing load sharing. Therefore, it is recommended that load sharing be disabled by
running the "SET UPOOLLOADSHAREPARA" command before the execution of this command.
4. In redundancy scenarios, if ALM-22307 RNC in Pool Function Unavailable is generated with cause "Inconsistent
Configurations of the Mapping Between Logical RNCs and Physical Nodes" after this command is executed and
the backup RNC has the current control rights, the master and backup RNCs both will have the control rights. As a
result, services on all base stations and cells are interrupted. Therefore, run the "FOC UHOSTRNC" command for
the master RNC to obtain the control rights before running the "MOD URNCMAP" command on both RNCs to
1.
Based
the Spreading Factor (SF), the number of pilot bits (Npilot) and the number of Transport Format
modify
theonmapping.
Combination Indicator bits (NTFCI), the slot format of a SCCPCH can be determined. For their relationships, refer
to the following table:
2. Note that if TFCI bits are not present, Discontinuous Transmission (DTX) should be used instead for the TFCI
field.
3. The number of Transport Format Combinations (TFCs) is limited by the parameter "CTFC Length of TFCS".
"CTFC Length of TFCS" is hard to be modified after the SCCPCH is set up. The number of TFCs should be
planned before the SCCPCH is set up.
Running this command modifies a typical traffic RAB's basic information that has been set. Once the basic
information of a typical traffic RAB is modified, the configurations of this typical traffic RAB will not be used during
service reconfiguration. Moreover, since the basic information is modified, new services will fail to be set up if the
RNC cannot map a data rate onto the data rate assigned by the CN.
Running this command modifies the settings of dynamic channel configuration parameters for the typical service
and affects the dynamic channel configuration function.
Running this command modifies HSPA parameter settings for the typical service, which decreases the data rate of
HSPA service.
1.Running this command modifies the settings of HSUPA outer-loop-power-control parameters for the typical
service and affects HSUPA data transmission quality.
2."MaxSirtargetForExtLRate" >= "MinSirtarget".
1.Running this command modifies the settings of outer-loop-power-control parameters for the typical service and
will affect data transmission quality.
2."EdchTarRetrNumForExtLRate" <= "MaxEdchRetransNum".
1.The basic information of the typical RAB must have been configured by the "ADD UTYPRABRLC" command. In
addition, the RLC parameters of the service subflow of the typical RAB must have been configured by the "ADD
UTYPRABRLC" command.
2.Running this command modifies RLC parameters that have been set for a subflow of a typical traffic RAB, which
affects data scheduling.
1.Before executing this command, ensure that the related semi-static TF parameters of the typical traffic RAB are
configured through the "ADD UTYPRABSEMISTATICTF" command.
2.Running this command modifies a typical traffic RAB's semi-static Transport Format (TF) parameters that have
been set, which decreases the UE data rate.
1.Before executing this command, ensure that the related TOA window parameters are configured through the
"ADD UTYPRABTOAW" command.
2.Running this command modifies a typical traffic RAB's parameters related to the Time of Arrival (TOA) window.
This affects frame transmission between the RNC and NodeB when RABs are being set up and reconfigured.
Running this command modifies the settings of basic parameters for the typical signaling and affects UE access.
The "MOD UTYPSRBDCHRNCRLC" command does not support parameters being set to the UM mode and
therefore, the value UM in the "RlcMode" parameter is reserved for future extension.
1.3GPP TS25.331 specifies that: If the UTRAN modifies the RLC size for SRB2 on any reconfiguration message or
Cell Update Confirm message, the UE behaviour is unspecified in this version of the specification. Therefore, the
RLC size for SRB2 must be the same on the HSPA, FACH, and DCH. Otherwise, the RLC size for SRB2 will vary,
depending on which channel is chosen. The varied RLC size will eventually cause call drops.
2.Running this command modifies the HSPA parameter settings for the typical signaling and will affect network
access of UEs whose signaling is to be carried on HSPA channels.
1.Running this command modifies the settings of HSUPA outer-loop-power-control parameters for the typical
signaling and affects network access of UEs whose signaling is to be carried on HSUPA channels.
2."MaxSirtargetForExtLRate" >= "MinSirtarget".
Running this command modifies the settings of outer-loop-power-control parameters for the typical signaling and
affects UE access.
1.The Delivery Order of the SRB RLC parameters cannot be configured. The delivery must be in sequence. Or
else, there will be a signalling order error, which results in inconsistency between the network side and UE side.
2.The maximum number of resets (MAX_RST) of RLC AM is fixed to 1. There is no need to configure it. See
TS25.331CR1029R1.
3.Running this command modifies the RLC parameter settings for the typical signaling and affects UE access.
1.Before executing this command, ensure that the typical SRB semi-static TF parameters have been configured
through the "ADD UTYPSRBSEMISTATICTF" command.
2.Running this command modifies the settings of semi-static transport format parameters for the typical signaling
and affects UE access.
1.Before executing this command, ensure that the time window parameters for typical signaling are configured
through the "ADD UTYPSRBTOAW" command.
2.Running this command modifies FP synchronization window settings for the typical signaling and affects UE
access.
1.Execution of this command causes a board to load the previously backup configuration data file after it resets.
2.When setting Force Board Load Switch to ON(ON), run the "RST BSC" command to reset the base station
controller.
3.The OMU saves configuration data file generated within two days. Users can force a board to load the
configuration file backed up at 03:57 of today or yesterday. Configuration data files backed up in the early morning
of today or yesterday are saved in the Mainarea of the active OMU\bin\fam\datafilenow or Mainarea of the active
OMU\bin\fam\datafilebefore directories, respectively.
4.If Force Board Load Switch has been set to ON(ON) before 03:57 of today, the configuration data file backed up
yesterday or the day before yesterday will be loaded.
5.If Force Board Load Switch has been set to ON(ON) and a configuration command was executed from the file
backup time to the current time, a board will load the configuration data file backed up today or yesterday after it
resets, and ALM-20736 Data Inconsistency Between OMU and Host will be generated.
6.If Force Board Load Switch is set to ON(ON) in any of the following scenarios, a board will load the configuration
data file in the Mainarea of the active OMU\bin\fam directory after it resets.
a.The base station controller starts working for the first time and it never backs up board configuration data.
b.After board configuration data is backed up, the board type is changed.
c.The backup configuration data file is deleted by mistake, or it is manually replaced or damaged.
1. This command can be executed only on the master RNC or backup RNC of a logical RNC. The command
execution causes online users to experience call drop.
2. You are not advised to execute this command on the logical RNC that is not mapped to another physical RNC by
running the "ADD URNCMAP" command.
3. You are not advised to execute this command on the logical RNC where "Redundancy Type" in the "ADD
URNCMAP" or "ADD URNCBASIC" command is set to NO_BACKUP.
4. This operation will release control rights of logical RNC.
1. When an AAL2 path is removed, the Virtual Channel Link Continuity Check (VCL CC) or VCL Performance
Monitoring (PM) activated for this path is deactivated.
2. Removing an AAL2 path interrupts the services carried on the path.
Removing an AAL2 route interrupts the services carried on the route.
1. If the ACL binds the port using the "ADD PACKETFILTER" command and an ACL rule is removed, the port
cannot process unicast packets that meet the ACL rule. If no ACL rule is available in the ACL after an ACL rule is
removed, the port does not filter packets.
1. After mapping between services and DSCPs is changed, new DSCPs take effect after the services are
reestablished.
2. Removing the mapping onto an adjacent node interrupts the services carried on the adjacent node.
1. The adjacent node to be removed must exist, and the lower-level adjacent nodes are already removed. You can
query whether the adjacent node exists by running the "LST ADJNODE" command.
2. The paths under the adjacent node to be removed are removed. You can query whether any path exists under
the adjacent node by running the "LST AAL2PATH" command.
3. If the adjacent node to be removed is of the ATM type, the AAL2RT paths under the adjacent node are removed.
You can query whether any AAL2 route under the adjacent node exists by running the "LST AAL2RT" command.
4. If the "ISIPPOOL" parameter for an adjacent node is set to "YES", removing the adjacent node interrupts the
services carried on the node.
1. The board is unavailable after the removal. You must use this command with caution.
2. After a GPU board is removed by running this command, the BSC6910 automatically adjusts backup resources
and enters the internal configuration state. In this case, follow-up executions of this command can succeed only
after the BSC6910 leaves the internal configuration state.
3. After a board is removed, the counter values for the board are unreliable in the last measurement period.
4. Before deleting an SAU board, check whether the board to be deleted functions as the SAU center. If yes, this
board cannot be deleted. If you want to delete the board that functions as the SAU center, run the "SET
SAUCENTER" command to change the board to non-SAU center, and then delete this board.
5. For details about how to remove boards, see the following section: Product Documentation > RAN
Reconfiguration Guide for BSC6910> Removing a Board or a Subrack.
6. If the FlexCfgMode parameter in the "SET UCPUPFLEXCFG" command is set to ManualMode, some cells may
be out of service when the following conditions are met:
1) Number of CP subsystems - 14 x Percentage of CP subsystems < (Number of CP subsystems + Number of UP
subsystems) x Minimum percentage of CP subsystems.
2) The "RMV BRD" command is executed to remove an EGPUa/EGPUb board.
where
Number of CP subsystems, Number of UP subsystems, Percentage of CP subsystems, and Minimum percentage
of CP subsystems are displayed in the "DSP UCPUPFLEXCFG" command output.
None
1. If this external node is involved in RNC mapping by running the "ADD URNCMAP" command, this external node
can be removed only after it is detached from RNC mapping by running the "RMV URNCMAP" command.
2. If this external node has been configured with an Iur-p control port by running the "ADD IURPLKS" command,
this external node can be removed only after the configured Iur-p control port is removed by running the "RMV
IURPLKS" command.
1. The GPS can only be removed after three minutes when the "ADD GPS" command is run.
2. The removal of the GPS receiver will result in the failure of providing the location service.
None
1. If the last M3UA route associated with a destination entity is removed, the destination entity will be inaccessible.
2. If one of the M3UA routes associated with a destination entity is removed, the services directed to the
destination entity will be affected.
Removing the ME interrupts ME services.
1. After an MTP3 signaling link in an MTP3 signaling link set is removed, load of other links in the same signaling
link set will be increased. If too many MTP3 signaling links of one Destination Signaling Point (DSP) are removed,
then, other links of this DSP will be congested. As a result, services related to this DSP will be affected or even
interrupted.
2. If the last MTP3 link in an MTP3 link set is removed, the MTP3 link set will be inaccessible.
1. If the last MTP3 route associated with a destination entity is removed, the destination entity will be inaccessible.
2. If one of the MTP3 routes associated with a destination entity is removed, the services directed to the destination
entity will be affected.
1. Only the system administrator "admin", the operator with the Administrator level, and custom operator who has
been authorized with such commands have the authority to execute this command.
2. The operator account is not case sensitive and it cannot be omitted.
3. The administrator accounts (admin) that are configured during the system installation cannot be removed.
4. After an operator account is removed, the operator using the account is forced to exit.
After the OSP is removed, the transport layer of the RNC cannot work normally. To add an OSP, use the "ADD
OPC" command.
1. Running this command causes the function of board hot patches to be unavailable. Therefore, run this command
only if necessary.
2. If all the hot patches are removed, operation succeeds. If one or several hot patches fail to be removed,
operation fails. You are recommended to remove such hot patches again.
3. If you run this command with "Operation type" set to Step_by_Step for a board, its hot patch status is updated
on the board, not in the OMU database. However, if the board resets later, the hot patch status on the board will
become consistent with the recorded hot patch status specific to the board in the OMU database.
1. After the information of the SNTP server is removed, the time of the NE will be inaccurate.
2. If "IP" is not specified, the information of all the SNTP servers is removed.
3. The IP address to removed is IP address of the SNTP server added through the "ADD SNTPSRVINFO"
command. The IP address cannot be set to a special address such as 0.0.0.0 or 127.0.0.1.
1. If the subrack to remove is connected to other subracks, you need to reconnect these subracks to subracks that
are not to be removed.
2. Before removing a subrack, run the "DSP PANELPORT" command to query to which port this subrack is
connected on the SCU in the upper level subrack. After removing the subrack, run the "SET SCUPORT" command
as soon as possible to disable the corresponding port on the SCU in the upper level subrack. Otherwise, services
may be damaged. After the port is disabled, you must manually clear any alarm involving the removed subrack.
3. Services will be affected after this command is executed.
4. If an EPS is configured, the MPS cannot be removed.
5. For details about how to remove subracks, see the following section: Product Documentation > RAN
Reconfiguration Guide for BSC6910 > Removing a Board or a Subrack.
1. Only the system administrator can run this command.
2. Certificate File Name: You are advised to specify this parameter using only ASCII characters. The file name
cannot contain any of the following characters: \/:*?"<>|@#!%^&[]'. The file name cannot start or end with a period
(.). The file name can not be all blank. The file name (case-insensitive and suffix excluded) cannot be any of the
following: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9,
LPT1,LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, or LPT9.
3. Do not delete the CA certificate if it is the only CA certificate in the system.
After this command is executed, users in a deleted area cannot receive disaster alert messages.
Execution of this command leads to call drops of UEs on the CCP.
None
1. Only after the CBS SAC has been added to this cell can the removal succeed.
2. After this command is executed, the SAC corresponding to the cell will be deleted and therefore users in the
SAC cannot receive cell broadcasting messages.
None
1. When the cell is in active state, the cell synchronized radio link reconfiguration activation time offset can not be
removed.
2. This operation may cause call drops or access failures in the specified cell.
1. A CN domain to be removed must have been configured.
2. After this command is executed, the information about the CN domain will be deleted and therefore CS or PS
services are interrupted.
1. A CN node to be removed must have been configured.
2. After this command is executed, the RNC cannot visit this CN node or this node is invisible despite the status of
lower layer links.
Removing an external NodeB interrupts the calls that are initiated by UEs in the CELL_DCH state under the NodeB
and are forwarded to the overflow RNC for load sharing.
Removing a transport format (TF) will affect the calculation of the CTFC of the SCCPCH bearing the FACH, which
may adversely affect services. Therefore, the SCCPCH CTFC should be calculated again after a TF is removed
("ADD USCCPCHTFC","RMV USCCPCHTFC").
After this command is executed, the common measurements on and information exchange with the specified
neighboring BSC will be terminated, and the Iur-g interface becomes unavailable.
1. The neighboring RNC have been configured.
2. After this command is executed, the neighboring RNC will be removed, adversely affecting inter-Iur handovers.
1. Before removing MBSC basic information, remove the information which depends on the MBSC basic
information such as mapping between logical RNC and physical RNC, neighboring RNC, CN node, iur-g interface
connectionm, and NodeB. You can check whether the information has been removed by running the following
commands: "LST URNCMAP", "LST UNRNC", "LST UCNNODE", "LST UIURGCONN" and "LST UNODEB".
2. This operation will make the service of RNC unavailable.
Before removing a main CPUID of RNC broadcast message for an operator, check whether a simplified CBS
message has been added for the operator using the "ADD UCBSMSG" command. If yes, run the "RMV
UCBSMSG" command to remove the message first.
After this command is executed, the CBS function of the associated operator will be unavailable.
1. Run this command only after you have confirmed that Huawei technical support has resolved the failure to
manually switch over the logical RNC control right.
2. This command does not apply to the GU mode.
This operation will remove mapping between logical RNC and physical RNC.
1.In load sharing scenarios, execution of this command leads to call drops on UEs that are undergoing load
sharing. Therefore, it is recommended that load sharing be disabled by running the "SET
UPOOLLOADSHAREPARA" command before the execution of this command.
2. In redundancy scenarios, if ALM-22307 RNC in Pool Function Unavailable is generated with cause "Inconsistent
Configurations of the Mapping Between Logical RNCs and Physical Nodes" after this command is executed and
the backup RNC has the current control rights, the master and backup RNCs both will have the control rights. As a
result, services on all base stations and cells are interrupted. Therefore, run the "FOC UHOSTRNC" command for
the master RNC to obtain the control rights before running the "RMV URNCMAP" command on both RNCs to
remove the mapping.
1. The RNC POOL to be removed must be configured.
2. If RNCPOOLMEMBER parameters are configured, it needs to delete relative RNCPOOLMEMBER information
by executing RMV RNCPOOLMEMBER.
3. After this command is executed, the RNC POOL function will be unavailable.
1. A RNC POOL index must have been configured.
2. The "Nrnc ID" must have been configured.
3. After this command is executed, the RNC POOL function will be unavailable.
After this command is executed, positioning services will be unavailable.
1.When a cell is activated, the prerequisite of removing a SCCPCH is that after removing this SCCPCH, the cell
has at least one activated SCCPCH which is bearing at least one PCH and one FACH.
2.Please be careful to remove a SCCPCH. If there is no SCCPCH in a cell, UEs on non-dedicated channels will
experience call drops or will not be controlled, and new users cannot access the cell.
3.When a SCCPCH carried CELLCMBCH is to be removed, the CELLCMBCH configuration must be removed first.
4.Please remove the SCCPCH as follow order:remove FACHLOCH,FACHDYNTFS,FACH and SCCPCH.
Running this command removes the configurations of the typical traffic RAB and affects service setup.
1.Before executing this command, ensure that the related DCCC algorithm measurement control parameters are
configured through the "ADD UTYPRABDCCCMC" command.
2.Before executing this command, ensure that the related typical RAB configurations are disabled.
3.Running this command removes the settings of dynamic channel configuration parameters for the typical traffic
RAB and affects service setup.
Running this command removes dynamic transport format settings for the typical traffic RAB and affects service
setup.
Running this command removes HSPA parameter settings for the typical traffic RAB and affects HSPA service
setup.
Running this command removes the settings of HSUPA outer-loop-power-control parameters for the typical service
and affects service setup.
1.Before executing this command, ensure that the basic information of the typical traffic RAB must have been
configured through the "ADD UTYPRABBASIC" and "ADD UTYPRABSUBFLOW" command. In addition, the subflow OLPC parameters of the typical traffic RAB must have been configured through the "ADD UTYPRABOLPC"
command.
2.Running this command removes the settings of outer-loop-power-control parameters for the typical service and
affects service setup.
1.Before executing this command, ensure that the basic information of the typical traffic RAB must have been
configured through the "ADD UTYPRABBASIC" and "ADD UTYPRABSUBFLOW" command. In addition, the subflow OLPC parameters of the typical traffic RAB must have been configured through the "ADD UTYPRABOLPC"
command.
2.Running this command removes the settings of outer-loop-power-control parameters for the typical service and
affects service setup.
1.Before executing this command, ensure that the typical RAB semi-static TF parameters have been configured
through the "ADD UTYPRABSEMISTATICTF" command.
2.Running this command removes semi-static transport format settings of the typical RAB and affects service
setup.
1.Before executing this command, ensure that the typical service parameters corresponding sub-flows are
configured through the "ADD UTYPRABSUBFLOW" command.
2.Running this command removes subflow parameter settings for the typical RAB and affects service setup.
1.Before executing this command, ensure that the time window parameters for typical services are configured
through the "ADD UTYPRABTOAW" command.
2.Running this command removes FP synchronization parameter settings for the typical service and affects service
setup.
1.Before executing this command, ensure that the related typical SRB information is configured through the "ADD
UTYPSRBBASIC" command.
2.Running this command removes all parameter settings for the typical signaling and affects UE access.
The "RMV UTYPSRBDCHRNCRLC" command does not support parameters being set to the UM mode and
therefore, the value UM in the "RlcMode" parameter is reserved for future extension.
1.Before executing this command, ensure that the typical SRB dynamic TF parameters have been configured
through the "ADD UTYPSRBDYNTF" command.
2.Running this command removes the settings of dynamic transport format parameters for the typical signaling and
affects UE access.
Running this command removes HSPA parameter settings for the typical signaling and affects UE access.
1.Before executing this command, ensure that the basic information of the typical SRB is configured through the
command "ADD UTYPSRBBASIC" and that the related HSUPAPC information is configured through the "ADD
UTYPSRBHSUPAPC" command.
2.Running this command removes the settings of HSUPA outer-loop-power-control parameters for the typical
signaling and affects UE access.
Running this command removes the settings of outer-loop-power-control parameters for the typical signaling and
affects UE access.
1.Before executing this command, ensure that the basic information of the corresponding SRB and the SRB
corresponding logical channel RLC parameters must have been configured through the "ADD UTYPSRBBASIC"
and "ADD UTYPSRBRLC" command.
2.Running this command removes RLC parameter settings for the typical signaling and affects UE access.
1.Before executing this command, ensure that the typical SRB semi-static TF parameters have been configured
through the "ADD UTYPSRBSEMISTATICTF" command.
2.Running this command removes semi-static transport format settings for the typical signaling and affects UE
access.
Running this command removes FP synchronization parameter settings for the typical signaling and affects UE
access.
1. You can use this command to remove an AAL2 connection in an AAL2 path or all AAL2 connections to an
This
is a high-risk
adjacent
node. MML command. Pay attention to the following precautions before running this command:
Impact
on System:
2. The reset
interrupts services carried on the AAL2 path.
1.
the boards
workID
in is
active/standby
the
the active
board
leads to active/standby
3. If
When
AAL2 path
set to 0, CID mode,
must be
setreset
to itsofdefault
value
0. Otherwise,
this commandswitchover.
may fail. If the
standby board is faulty, the active board can be reset only when "force" is set to YES, and services are interrupted
after the active board is reset. If the board works in independent mode, services are interrupted if the board is
reset.
2. It takes certain time for the fault to be detected after a board reset. Therefore, do not perform data configuration
during the 15s after a board reset. If you perform data configuration during this period, data on the OMU and the
host board may become inconsistent.
3. After a board is reset, the counter value for the board is unreliable in the first measurement period. If an active
board is reset, the counter values for both the active and standby boards are unreliable in the first measurement
period.
4. When the active SCU board is reset, if the standby SCU board is inhibited, the standby SCU board will be
automatically uninhibited and the subrack is reset because the active and standby SCU boards are resetting.
Command Restrictions:
1. If a configuration command is executed and the configured data needs to take effect on a faulty board (excluding
boards that are prohibited or not in position), the command execution will fail to prevent data inconsistency
between the OMU and the host board. You can run the "DSP BRD" command to query the status of a board.
2. If data configuration needs to be performed when a board is faulty, run the "INH BRD" command to inhibit the
faulty board.
3. For the boards in active/standby mode, if you reset the active board during the standby board initialization and
the initialization backup does not complete within five minutes, then the active board reset fails.
This
is a high-risk
command.
Pay
attention
to the following
precautionsmode,
beforeresetting
running this
command:
4. When
two SCU MML
boards
of different
types
are configured
in active/standby
the active
SCU board
Impact
on the
System:
will cause
subrack to automatically reset. To manually reset a subrack, run the "RST SUBRACK" command. Do
1.
this command
interrupts
the ongoing
services.
notRunning
reset a subrack
by resetting
the active
and standby
SCU boards in it.
2. After this command is executed, the counter values for the objects under the RNC are unreliable in the first
measurement period.
1. Run this command only after system is set to effective mode; otherwise, the configuration data does not take
effect.
2. The system loads all the subracks after reset. When multiple subracks need to be loaded, the MPS subrack is
loaded by the system, and then the EPS subrack is loaded.
3. When RNC in Pool is applied, the base station controllers cannot reset by the BSCID value, but by the NENAME
value.
4. If the RST BSC command execution fails, run this command again after the previously reset subrack works
properly. Otherwise, services may be damaged.
This command is a highly risky command. Before running this command, read the following precautions.
Impact on the System:
1. If both active and standby OMUs are configured, running this command will cause the data synchronization
between the active and standby OMUs to fail. The data synchronization recovers within 5 minutes.
Limitations:
1. If only one OMU is configured, a message is displayed indicating that the standby OMU cannot be reset.
During the reset, both of the rotational speed regulation and fault management functions become ineffective for the
fan box and fans are running at a fixed rotation speed.
During
the
reset, the
GPS
receiver Pay
cannot
provide
services.
This
is a
high-risk
MML
command.
attention
tolocating
the following
precautions before running this command:
Impact on System:
1. Resetting a board that works in active/standby mode leads to active/standby switchover, and services are
interrupted if the standby board is faulty. Resetting a board that works in independent mode leads to service
interruption.
2. It takes certain time for the fault to be detected after a board reset. Therefore, do not perform data configuration
during the 15s after a board reset. If you perform data configuration during this period, data on the OMU and the
host board may become inconsistent.
3. After a board is reset, the counter value for the board is unreliable in the first measurement period. If an active
board is reset, the counter values for both the active and standby boards are unreliable in the first measurement
period.
1. Do not reset a board that is downloading software; otherwise, data in the board flash may be destroyed.
2. If a configuration command is executed and the configured data needs to take effect on a faulty board (excluding
boards that are prohibited or not in position), the command execution will fail to prevent data inconsistency
between the OMU and the host board. You can run the "DSP BRD" command to query the status of a board.
3. If data configuration needs to be performed when a board is faulty, run the "INH BRD" command to inhibit the
faulty board.
4. The
OMU,
SAU,
and active
SCU boards
do not support
this to
operation.
1.
Running
this
command
will cause
the connection
of the ME
be temporarily interrupted.
2. The value of the "Target ME" depends on the active/standby relationship of the host OMU board where the ME
to be reset is located.
1. When the OMU is being reset, the connection between the maintenance client and the OMU is disconnected,
causing operation and maintenance to be interrupted.
2. If the reset type is SOFT, the OMU software is reset, and the interruption duration is within 5 minutes. If the reset
type is HARD, the OMU hardware is reset, and the interruption duration is within 10 minutes.
Limitations:
1. If only one OMU is configured, a message is displayed indicating that the standby OMU cannot be reset.
1. Resetting an OMU module interrupts the services on the OMU module. The interruption duration is within 4
minutes.
Limitations:
1. When the ems_gate or weblmt module is reset, the response report cannot be sent to client if this command is
successfully executed.
During the reset, the fault management function becomes ineffective for the power allocation monitoring unit.
1. If the reset type is SOFT, the SAU software is reset. If the reset type is HARD, the SAU hardware is reset.
2. When multiple SAUs are configured, all the SAUs will be reset if the subrack number and slot number are not
specified.
This is a high-risk MML command. Pay attention to the following precautions before running this command:
Impact on System:
1. The reset of a subrack will interrupt all the ongoing services.
2. After a subrack is reset, the counter values for the objects under the subrack are unreliable in the first
measurement period.
1. Run this command only after system is set to effective mode; otherwise, the configuration data does not take
effect.
This is a high-risk MML command. Pay attention to the following precautions before running this command:
Impact on System:
1. If two subsystems work in active/standby mode and the active one is reset, the active/standby switch over is
triggered. If the standby subsystem is faulty, the active subsystem is not allowed to be reset by default. In this case,
the active subsystem can be reset only when "force" is set to YES. Services will be interrupted during the reset.
Resetting a subsystem working in independent mode interrupts services. The work mode of a subsystem can by
queried by running the "LST SUBSYS" command. If the command output is NULL, the subsystem works in
independent mode.
2. Do not perform any data configuration within 10-15 seconds after a subsystem is reset; otherwise, data
inconsistency occurs.
1. This command cannot be executed on a subsystem of a board that works in active/standby mode.
2. This command cannot be executed on a subsystem of an FG2c/GOUc/GOUe/AOUc/UOIc/EXOUa board.
3. This command cannot be executed on a subsystem of the NDM/URSCA type.
4. The command fails to be executed if the specified subsystem number does not exist.
5. If two subsystems work in active/standby mode and the active one is reset, the active subsystem fails to be reset
if the standby subsystem is during initialization and the initialization backup is not complete within 5 minutes.
This command is a risky command. Before you run this command, read the following precautions:
Impact on System:
Running this command resets the Iu interface. Consequently, online UEs carried on the CN nodes that are reset
experience call drops. The reset takes one minute, and during this period of time these CN nodes are unavailable.
Command execution restriction:
None.
This command is a risky command. Before you run this command, read the following precautions:
Impact on System:
Running this command resets the Iur interface. Consequently, the data transmission on the Iur interface is
interrupted, and online UEs that have only Iur connections experience call drops. Therefore, exercise caution when
running this command.
Command execution restriction:
None.
This is a high-risk MML command. Pay attention to the following precautions before running this command.
Impact on Services:
Running this command will reset the NodeB. In a multimode base station, the NodeB reset will interrupt services on
the GSM and LTE sides.
1. After this command is executed, the ME will be reinstalled.
2. Only the configuration data, license files, certificate files, counter definition files, and registry files of the ME are
restored.
3. ME restoration typically takes less than 30 minutes.
4. After the restoration is complete, run the "CHK MECFG" command to start the configuration resource
consistency check between the host and built-in NEs.
1. Running this command temporarily interrupts the services carried on the ATM interface board.
2. The second GPU board to which the ATM interface board is bound must work properly.
3. Its logical function type must be UCUP.
1. One ME can be bound to multiple GASP boards.

2. If "MEID" is set to 255, the GASP board is used by all management entities (MEs). If "MEID" is set to a value
ranging from 1 to 4, the GASP board is used by a specified management entity (ME).
If the value of the CONNTYPE parameter changes from ALL to ONLY_SSL, all the existing non-SSL connections
will be interrupted but all the existing SSL connections will remain unaffected. In addition, the value change does
not affect communication between an NE and the LMT.
Before changing the value of the CONNTYPE parameter from ALL to ONLY_SSL, you are advised to convert all
the existing non-SSL connections into SSL connections to prevent connection interruption.
Before changing the value of the CONNTYPE parameter from ALL to ONLY_SSL, ensure that the following
conditions are met. Otherwise, the connections between the OMU and clients such as the U2000 cannot be
established:
(1) Run the "DSP APPCERT" command to check that the status of the effective device certificate is normal.
(2) Run the "DSP TRUSTCERT" command to check that the status of at least one CA certificate or certificate chain
is
1. normal.
This command can be executed only when system work in ineffective mode.
2. After running this command, run the RST BSC command to reset the system so that the configuration takes
effect.
3. Before running this command, ensure that the RNC operates normally and the ports are available.
4. Services are interrupted during the NEBS certification test.
This command is used to set switches for enhanced board communication reliability. It is recommended that you
use the default values for the parameters. Contact Huawei engineers if you want to modify.
None
1. The flow control function can be implemented only when the switch of the entire subsystem and the switch of the
corresponding flow control item are enabled.
2. When the CPU usage or the usage of the message queue reaches the threshold and the flow control switch is
set to ON, the system automatically controls the flow.
3. The CPU usage threshold or the message queue usage threshold is subject to the following rule: 100 >= control
threshold of a flow control function > restore threshold of this flow control function.
4. The priority of the critical threshold is higher than the priorities of the special thresholds of other functions. That
is, when the CPU usage reaches the "CPU Critical Threshold" or the usage of the message queue reaches the
"MSG Critical Threshold", its control mechanism takes effect first. When the CPU usage does not reach the "CPU
Critical Threshold" or the usage of the message queue does not reach the "MSG Critical Threshold", the thresholds
of other usages take effect.
5. The flow controls of the message queue usage and the CPU usage are independent. The minimal flow in the
two flow controls is the allowed flow in the system.
1. When the CPU usage reaches the threshold and the flow control switch is set to ON, the system automatically
controls the flow.
2. The CPU usage threshold is subject to the following rule: 100 >= control threshold of a flow control function >
restore threshold of this flow control function.
4. If the threshold for a flow control item is set to a value less than or equal to the restoration threshold for this flow
control item, this flow control item does not take effect.
1. When the usage of the message queue reaches the threshold, the flow control occurs only if the corresponding
flow control switch is set to ON.
2. The message queue usage threshold is subject to the following rule: 100 >= control threshold of a flow control
function > restore threshold of this flow control function.
4. If the threshold for a flow control item is set to a value less than or equal to the restoration threshold for this flow
control item, this flow control item does not take effect.
1. You should run the "RST OMU" command after the settings to restart active and standby OMUs, and thus to
validate the settings.
1. The modified value of the "ENCRYMODE" parameter takes effect only after the FTP server is restarted by the
"RST OMUMODULE" command.
2. If the FTP server is run by a user other than the root user, after "DFTPORTSWT" is changed from
CUSTOMPORT to DEFAULTPORT using this command, the FTP server will automatically reset to validate this
setting.
3. When "ENCRYMODE" is set to PLAINTEXT, the FTP server connects to the FTP client in the plaintext mode,
leading to security risks.
Running this command will affect the self-healing function on an interface board. If you want to configure the selfhealing function, contact Huawei Customer Service Center.
1. The value of the Process Message Log Switch parameter automatically changes to DISABLE 40 minutes after
the parameter is set to ENABLE.
2. System performance will be affected if Process Message Log Switch is set to ENABLE. Therefore, you are
advised to turn on the switch during fault location and to turn off the switch immediately after the fault location is
complete.
1. Only the administrator has the authority to execute this command.
2. The deletion time limit is the operation time of the OMU rather than an absolute time.
3. If the operation time of the system exceeds the set time limit, the logs before the time limit are deleted
This
is a high-risk
MML
command.
attention
to the
following
precautions
before
runningautomatically.
this command:
automatically.
If the
number
of logsPay
exceeds
the set
count
limit, the
earlier logs
are deleted
Impact on System:
1. Disabling the port between the current subrack and the lower-level subrack will affect the communication
between the two subracks and cause the lower-level subrack to be faulty.
1. All the ports on the SCUb/SCUc board that is located in the MPS are disabled by default. If an EPS is
configured, enable the interconnection port on the SCUb board in the MPS for interconnection with the EPS.
2. For the SCUb board in an EPS, only ports 8 and 9 can be connected to a higher-layer subrack and only ports 10
and 11 can be connected to a lower-layer subrack if the subracks work in the chain topology. For the SCUc board
in an EPS, ports 0, 1, 2, and 3 can be connected to 40GE ports of a higher-layer subrack, ports 8 and 9 can be
connected to 10GE ports of a higher-layer subrack, ports 4, 5, 6, and 7 can be connected to 40GE ports of a lowerlayer subrack, and ports 10 and 11 can be connected to 10GE ports of a lower-layer subrack.
3. If this command is executed on port 0, 1, 8, or 9 on the SCUb board in an EPS, only the alarm reporting function
on the board is disabled and inter-subrack communication is not affected. If this command is executed on port 0, 1,
2, 3, 8, or 9 on the SCUc board in an EPS, only the alarm reporting function on the board is disabled and intersubrack communication is not affected.
4. On SCUc boards, ports 4 to 7 cannot be enabled simultaneously with ports 8 to 11.
5. This command is used to set the attributes of ports on the SCU board panel in the specified slot.
6. Port 6/7 of the SCUb board cannot be used for inter-subrack connections.
7. For SCUc boards, Port No. must be specified before Port switch is set to OPEN(Open).
8. For the SCUc board, if ports 8 and 9 are used for inter-subrack connections and these two ports are normal,
ports 4 to 7 cannot negotiate with the peer-end subrack. Ports 4 to 7 can successfully negotiate with the peer-end
subrack only when ports 8 and 9 are faulty.
1. The value of the "NID" parameter in the "SET NODE" command cannot be the same as the value of the "ENID"
parameter in the "ADD EXTNODE" command.
2. The value of the "NNAME" parameter in the "SET NODE" command cannot be the same as the value of the
"ENNAME" parameter in the "ADD EXTNODE" command.
3. A local physical RNC with a node ID of 65535 cannot be set as an external RNC to another RNC by running the
"ADD EXTNODE" command. In addition, setting another RNC as an external RNC to such a local physical RNC by
running the "ADD EXTNODE" command is not recommended.
4. Running this command to change the value of Node Id will cause call drops and cause UE access failures when
the RNC in Pool feature is activated.
5. In RNC in Pool networking, when running this command to change the value of Node Id, you should also change
the external nodes and RNC mapping configured for other physical nodes. Otherwise, the load sharing and node
redundancy functions are affected.
6. Running this command to change the value of Node Id will cause the started UMTS tracing and monitoring tasks
to become invalid. You can stop these tasks and then restart them after the execution of this command.
1. This command only be executed on the EMS.

2. This command only be executed by the U2000 operator that has the right to operate the SG_0 command group.
1. Either "Task ID" or "Task Name" must be specified.

2. Only the system administrator and the network administrator have the authority to execute this command.
3. If the ENF parameter is set to DISABLED, scheduled tasks cannot start.
1. All the ports on the SCUb/SCUc board that is located in the MPS are disabled by default. If an EPS is
configured, enable the interconnection port on the SCUb board in the MPS for interconnection with the EPS.
2. For the SCUb board in an EPS, only ports 8 and 9 can be connected to a higher-layer subrack and only ports 10
and 11 can be connected to a lower-layer subrack if the subracks work in the chain topology. For the SCUc board
in an EPS, ports 0, 1, 2, and 3 can be connected to 40GE ports of a higher-layer subrack, ports 8 and 9 can be
connected to 10GE ports of a higher-layer subrack, ports 4, 5, 6, and 7 can be connected to 40GE ports of a lowerlayer subrack, and ports 10 and 11 can be connected to 10GE ports of a lower-layer subrack.
3. If this command is executed on port 0, 1, 8, or 9 on the SCUb board in an EPS, only the alarm reporting function
on the board is disabled and inter-subrack communication is not affected. If this command is executed on port 0, 1,
2, 3, 8, or 9 on the SCUc board in an EPS, only the alarm reporting function on the board is disabled and intersubrack communication is not affected.
4. You can perform settings in batches by running this command for SCUb boards. If the subrack number, port
number, and port switch are specified, you can modify the attributes of a specified port on an SCUb board. If only
the subrack number and port switch are specified, you can modify the attributes of all ports on the specified SCUb
board. If the attributes of a port on an SCUb board cannot be modified, batch setting does not take effect on this
port. For SCUc boards, you can perform settings in batches by running this command when the port switch is
turned off cannot perform settings in batches by running this command when the port switch is turned on. When
the port switch is turned on, [SCUPORT:PN] must be specified.
5. On SCUc boards, ports 4 to 7 cannot be enabled simultaneously with ports 8 to 11.
6. For the active and standby SCU boards, if you set the attributes of the port on one SCU board, those of the port
onIfthe
boards are
alsoisset.
1.
theother
mainSCU
Self-healing
Switch
set to OFF, the settings of sub Self-healing Switch do not change, but become
7. Port 6/7 of the SCUb board cannot be used for inter-subrack connections.
ineffective.
8.
"SET
command
cannot
if an SCUb
board Switch
and an will
SCUc
board
are automatically
configured in
2. The
When
the SCUPORT"
main Self-healing
Switch
is setbe
to executed
OFF, the main
Self-healing
be set
to ON
active/standby
mode
in
a
subrack.
To
set
the
attributes
of
ports
on
these
two
SCU
boards,
run
the
"SET
after 24 hours and other switches remain unchanged.
MIXSCUPORT"
command.Switch is set to ON, the settings of sub Self-healing Switch can be effective.
3.
If the main Self-healing
9. When
For thethe
SCUc
board, if Switch
ports 8 for
andOMU
9 areProcess
used forisinter-subrack
thesethe
twoactive
portsand
are standby
normal,
4.
Self-healing
set to ON, theconnections
switchover and
between
ports 4 istotriggered
7 cannotifnegotiate
the peer-end
subrack.
Ports
to consecutive
7 can successfully
negotiate
with the peer-end
OMUs
the OMUwith
processes
become
abnormal
for410
times within
30 minutes.
subrack
when ports 8Switch
and 9 for
areMemory
faulty. Overload is set to ON and the physical memory or virtual memory
5.
Whenonly
the Self-healing
occupied by an OMU process exceeds the specified threshold, the process will be restarted, the specifications are
as follows:
a). When the physical memory occupied by the configure or stat process exceeds 3 GB or the physical memory
occupied by any other process exceeds 2 GB, these OMU processes will be restarted.
b). When the virtual memory occupied by the alarm or maintain process exceeds 2 GB, the virtual memory
occupied by the configure process exceeds 3 GB, or the virtual memory occupied by any other process exceeds
3.9 GB, these OMU processes will be restarted.
6. When the Self-healing Switch for Ethernet Adapter Traffic Monitoring is set to ON, the OMU automatically
restarts if no packages are received or sent for eight minutes in the external or internal network.
7. The switchover between the active and standby OMUs is triggered if the following conditions are met:
a).The self-healing switch for abnormal active-OMU reset is set to ON.
b).The standby OMU detects that the active OMU has been abnormally reset for three times within 24 hours.
c).The synchronization between active OMU data and standby OMU data is normal.
8. When the Self-healing Switch for Database Disk Cleanup is set to ON, the OMU triggers the database disk
cleanup if the disk space occupied by the database used by the OMU exceeds 2 GB and the remaining space of
the logical disk where the database is located accounts for less than 15% of all space.
9. The operation and maintenance is interrupted during the active OMU restart.
10. If the Self-healing Switch for Disk IO Overload parameter is set to ON and the load of the OMU disk IO exceeds
the specified threshold, IO flow control (decreasing the frequency or speed of the OMU reading or writing the disk)
is triggered. The specifications are described as follows:
If the OMU runs the Windows operating system:
(1) IO flow control is triggered when both of the following conditions are met:
a).The IO usage is greater than or equal to 90%.
b).The length of the queue waiting for IO operations is greater than or equal to 10.
(2) IO flow control is stopped when either of the following conditions is met:
a).The IO usage is less than or equal to 80%.
b).The length of the waiting queue is less than or equal to 2.
If the OMU runs the Linux operating system:
(1) IO flow control is triggered when both of the following conditions are met:
a).The IO usage is greater than or equal to 90%.
b).The average wait time for IO operations is greater than or equal to 150 ms.
(2)
IO flow
control
is stopped
when either
of the following
conditions
is met: services. Therefore, run this command
Running
this
command
with improper
parameter
settings will
affect ongoing
a).The
IO
usage
is
less
than
or
equal
to
80%.
with caution.
b).The
averagethe
wait
timeoffor
IOAUTHMODE
operations isparameter
less than or
equal
to 90
Before
changing
value
the
from
NONE
to ms.
PEER, ensure that the following conditions
are met. Otherwise, the connections between the OMU and clients such as the U2000 cannot be established:
(1) Run the "DSP APPCERT" command to check that the status of the effective device certificate is normal.
(2) Run the "DSP TRUSTCERT" command to check that the status of at least one CA certificate or certificate chain
is normal.
1. This command can be executed only when system is in ineffective mode.

2. After this command is executed, run the "RST OMU" command to perform a soft reset on the active and standby
OMU boards. During an OMU warm reset, only modules on the OMU are reset but not the OMU hardware. The
active and standby OMU boards are not switched over, regardless of which one comes first during the warm reset.
You are advised to first reset the standby OMU board and then the active OMU board.
3. After system have switched to effective mode, power cycle all subracks to reset them for reloading.
4. Subnet network begins with the network segment of *.EXSUBNET and *.(EXSUBNET+1).
1. Whether to use the daylight saving time is determined by the local law. The corresponding parameters are
clearly defined in the local law if the daylight saving time is used. You can also define the daylight saving time;
None
however, this is not recommended.
2. After the daylight saving time is set, the time associated with DST in an MML report, alarm, or log indicates a
daylight saving time. For example, "2005-07-01 15:50:25 DST" is displayed. However, when it is not the daylight
saving time, no DST appears even if the daylight saving time is set. For example, "2005-07-01 15:50:25" is
displayed.
3. The repeated or missed time due to the DST transition may affect the services in the system. Therefore, when
setting the DST, you are recommended to set the DST transition time in the early morning when the traffic is
comparatively light. The scheduled task shall not be set to the DST transition time. Otherwise, the scheduled task
may be executed twice or not be executed at the transition day.
4. If the start date or end date of daylight saving time is set to DATE, you cannot set the start date or end date to
February 29. The reason is that the local time cannot be translated to the daylight saving time in a leap year as
February 29 does not exist.
5. If the start date or end date of daylight saving time is set to DATEWEEK, then you must set the benchmark day
to (n-6) or earlier, where n represents the last day of the month. For example, the last day in October is 31. Then,
the benchmark day must be set to 25 (31-6) or earlier. If the date is set to Tuesday in or after the week of October
26, it is invalid in 2005 because the date exceeds the month scope; while in 2006, it is October 31, a valid day.
Therefore, you must abide this specification to ensure that the setting is valid in each year.
6. The start month and end month of the daylight saving time must be different.
7. The current time is out of the range from "DST change point-DST offset" or "DST change point+DST offset".
1. If a small number of RRC connection requests per second (see "SysAmrRrcNum", "CellAmrRrcNum", and
"NBAmrRrcNum") are allowed, executing this command will cause false flow control. As a result, user experience
deteriorates.
2. If "CapsFcCpuTrigThd" < "CapsFcCpuRelThd", RNC will use recommended value of these two parameters.
1.After this command is executed, the ongoing network optimization performed based on performance call history
record (PCHR) logs will be affected, for example, Nastar data analysis.
2.The cell-level "CHRScopeCtrl" takes effect only when the RNC-level "CHRScopeCtrl" is set to
DEPEND_CELL_SWITCH. The RNC-level "CHRScopeCtrl" can be set through the "SET UCHRSCOPE" and "SET
URNCCHRSCOPE" commands.
1. The "T302" broadcasted in SIB1 will be set by formula "T302 = Roundup{ [Timer T302] + 2*[IUB Trans Delay]}",
where [Timer T302] is the value set by "SET UCONNMODETIMER"; [IUB Trans Delay] is the IUB transport delay
set by "ADD UNODEB", and the calculated result will be round up to 100, 200, 400, 600, 800, 1000, 1200, 1400,
1600, 1800, 2000, 3000, 4000, 6000, or 8000ms.
2. According to 25331 CR 1990, T317 will never expire.
3. All parameters in this command are advanced parameters. To modify any parameter, contact Huawei Customer
Service Center for technical support.
4. If the parameters in this command are inappropriately set, services of online UEs are affected.
5. Both T314 and T315 must be set to 0, or the value of T315 must be greater than the value of N302 multiplied by
that of T302. Otherwise, the PS service drop rate may increase.
1. When the "FlexCfgMode" parameter is set to ManualMode, changing the value of the "CPProportionInTotal"
parameter will cause online users to experience call drops.
2. The value of the "FlexCfgMode" parameter can be changed as follows: from ManualMode to AutoMode,
AutoMode to ManualMode, AutoMode to FrozenMode, FrozenMode to AutoMode. The value of this parameter
cannot be changed as follows: from ManualMode to FrozenMode, FrozenMode to ManualMode. Note that when
the value of the "FlexCfgMode" parameter is changed from AutoMode to ManualMode, the "CPProportionInTotal"
parameter cannot be specified. Otherwise, the "SET UCPUPFLEXCFG" command fails to be executed.
3. When the value of the "FlexCfgMode" parameter changes from AutoMode to ManualMode, do not change the
value of the "CPProportionInTotal" parameter. Otherwise, a large number of CP and UP subsystems will be
adjusted.
4. When "FlexCfgMode" is set to ManualMode, the maximum proportion of CP subsystems that can be added or
removed at a time is 10%. The current proportion of CP subsystems can be queried by running the "LST
UCPUPFLEXCFG" command. The greater the change in the value of "CPProportionInTotal", the longer the
command execution time is (up to 15 minutes).
5. When "FlexCfgMode" is set to ManualMode, "CPProportionInTotal" must be set based on the values of
"Minimum percentage of CP subsystems" and "Maximum percentage of CP subsystems" in the output of the "DSP
UCPUPFLEXCFG" command and on the value of "CP PROPORTION IN TOTAL" in the output of the "LST
UCPUPFLEXCFG" command. In addition, the value must meet the following conditions:
1) If the value of "CP PROPORTION IN TOTAL" is less than the value of "Minimum percentage of CP subsystems",
"CPProportionInTotal" must be set to value greater than or equal to that of "CP PROPORTION IN TOTAL" and at
the same time less than or equal to that of "Maximum percentage of CP subsystems".
2) If "CP PROPORTION IN TOTAL" is set to a value within the range from "Minimum percentage of CP
subsystems" to "Maximum percentage of CP subsystems", "CPProportionInTotal" must be set to a value within the
same range.
3) If the value of "CP PROPORTION IN TOTAL" is greater than the value of "Maximum percentage of CP
subsystems", "CPProportionInTotal" must be set to a value greater than or equal to that of "Minimum percentage of
CP subsystems" and at the same time less than that of "CP PROPORTION IN TOTAL".
If
is executed
to modify
the
setting ofincrease
a parameter,
parameter
setting
takes effect on cells
6.this
Thecommand
CPU usage
of some boards
may
drastically
duringthe
thenew
execution
of this
command.
one by one at the interval specified by the "AcIntervalOfCells" parameter. If the automatic DSAC algorithm has
taken effect on a cell, system information update will not be immediately triggered. It will be triggered after a period
specified by the "AcRstrctIntervalLen" parameter.
1. VIP users are not limited by the "User Sampling Rate".

2. To report a CHR event block, you need to enable the CHR switch for the related cell by using the "SET
UCHRSCOPE" command.
3. After this command is executed, the ongoing network optimization performed based on performance call history
4. Logs recorded by Huawei RAN devices are Huawei property. The contents and structures of these logs are
subject to change without notice upon release of a software package or software patch. If these logs are disclosed
to a third party, Huawei is no longer obligated to provide technical support or change notices.
1. If the average CPU usage on an SPU in an RNC exceeds 60%, you are advised to turn off the "Event CHR
Process Switch".
2. This operation may affect ongoing network optimization performed based on performance call history record
(PCHR)
logs.to protocol parameters impacts the signalling processing. Only qualified personnel can use this
Modification
command.
If the parameters in this command are inappropriately set, network access is affected.
1. The timer TRafc "RafcTmr" can negotiate with the timer TRatr used to respond to RNC reset of the CN node, so
that the RNC can get the reset response from the CN node in time. For the configuration, refer to the following:
"Trafc" * ("Times of resending reset message to CN" + 1) > CN's "Timer T(Ratr)";
2. The timer TRatc can negotiate with the timer TRafr used to wait for the reset response from RNC of the CN
node, so that the RNC can get the reset response from the CN node in time. For the configuration, refer to the
following:
"Tratc" < CN node's "Timer T(Rafr)" * ("Times of resending reset message from CN" + 1);
3. The CN protection timer is mainly used in such a situation. When a intermittent link failure occurs between the
RNC and the CN node, the RNC does not release all signaling connections to the CN node at once. After the timer
expires, the RNC releases them if they are still not recovered.
4. "TinTR" must be set greater than "TigOR".
When any of the KPIs has deteriorated, running this command leads to an SPU reset.
Running this command changes logical channel priority settings, which affects data scheduling.
when setting the MR collecting period and disable the MR collecting function to minimize the impact on the CP
subsystem CPU if MR data is not required. When this period is set to 12s, the CP subsystem CPU usage increases
by about 10% if all types of MRs from all cells under the RNC are reported; when this period is set to 2s, the CP
subsystem CPU usage increases by about 25%. If the CP subsystem CPU usage exceeds the value of "MRCTHD"
in the "SET FCCPUTHD" command, MR-based flow control is triggered, that is, all UEs stop reporting the MRs to
ensure that normal services are not affected until the CP subsystem CPU usage is lower than the recovery
threshold for MR-based flow control specified by the "MRCTHD" parameter in the "SET FCCPUTHD" command.
2.It is good practice to reduce the number of MR-enabled cells, which is set by running the "SET UMRSCOPE"
command, to minimize the impact on the CP subsystem CPU. When the MR collecting period is set to 2s, set the
number of MR-enabled cells less than 300; when the MR collecting period is set to 12s, set the number less than
1500.
3.When the MR collecting function is enabled, it is good practice to disable the MRs over Iub and Uu in the CHR
standard event block, which are set by RRC_MEAS_RPRT of "UuMsgLogSwitch1" and
NBAP_DEDIC_MEAS_RPRT of "IubMsgLogSwitch" in the "SET UEVENTCHRCTRL" command. This is to
minimize the impact of MRs and PCHRs on the CP subsystem CPU.
4.When the MR collecting function is enabled, it is good practice to adjust the UE sampling rate in the CHR to 10%
or lower, which is set by "UserSampleRate" in the "SET UEVENTCHRCTRL" command. This is to minimize the
impact of MRs and PCHRs on the CP subsystem CPU.
5.Enabling the MR collecting function increases the UTRAN signaling traffic. As a result, transmission congestion is
more likely to occur on the control plane of the Uu and Iub interfaces. If the period of collecting MRs is set to 2s,
the Iub Compression Control Protocol (CCP) bandwidth of the NodeB involved in MR collections must be extended
by at least 350 kbit/s.
6.When the AGPS MR collecting function is enabled, you are advised to set the GPS_NAVGMODEL switch to 0
under the UE-based A-GPS Data Send Switch parameter "UeBasAgpsAssDataSwitch" by running the "SET
USMLC"
command.
Bymeasurement
doing so, the report
size ofcollecting
the AGPSfunction
measurement
control
message
is reduced,
the impact
on
1.In
the cell
where the
is enabled,
load
congestion
is more likely
to occur
delay
subsequent
downlink
signaling
as of
thesignaling
RB Setup
message)
is increase.
minimized, and KPIs (such as the RAB
on theofUu
and Iub control
plane
and the(such
number
messages
will
access
success
rate) do not deteriorate.
2.Enabling
the measurement
report collecting function for a specified area will increase the CPU usage.
7.Logs
recorded
RAN
devices
are Huawei
The "SET
contents
and structures of
these logs
are
3.This command by
canHuawei
be used
to set
the RNC-level
MRproperty.
switch. The
URNCMRSCOPE"
command
can
also be
subject
without notice
upon The
release
of parameter
a softwaresetting
package
or software patch. If these logs are disclosed
used
to to
setchange
the RNC-level
MR switch.
latest
prevails.
to athe
third
party, Huawei
is no longer
provide
technical support
or change
4.If
ScopeType
parameter
is set obligated
to ByRnc to
and
the MRScopeCtrl
parameter
is set notices.
to ON or OFF, the switch
controlling whether all cells under the RNC send the MR is set to ON or OFF, and the setting of the MRScopeCtrl
parameter when ScopeType is set to ByCellId does not take effect.
5.If the ScopeType parameter is set to ByRnc and the MRScopeCtrl parameter is set to DEPEND_CELL_SWITCH,
the setting of the MRScopeCtrl parameter when ScopeType is set to ByCellId takes effect.
None
1. Only when the Iu-Flex, MOCN or Iu-Flex&MOCN function is supported, the "NNSfTmr" and NRI length becomes
effective.
2. When the Iu-Flex function is supported, the protocol version of configured CN nodes must be R5 or later than
R5.
3. When the MOCN or Iu-Flex&MOCN function is supported, the protocol version of configured CN nodes must be
R6 or later than R6.
4. When the Iu-Flex or Iu-Flex&MOCN function is supported, "NullNRI" value must be configured.
5. When the Iu-Flex function for one CN domain is unsupported, the number of configured CN nodes of the CN
operator for the CN domain cannot exceed 1.
6. When the CS information function "CsInfoUpdFlag" is supported, the CS information update protection timer
"CsInfoUpdTmr" becomes effective.
7. When the PS information function "PsInfoUpdFlag" is supported, the PS information update protection timer
"PsInfoUpdTmr" becomes effective.
8. After this command is executed, operator parameters will be changed and therefore some services cannot be
accessed.
1. Make sure that the RNC have only one CnOperator when you want to set
"RANSharingSupport"/"MOCNSupport" to No.
2. You cannot set "RANSharingSupport"/"MOCNSupport" to Yes at one time.
3. After this command is executed, RNC sharing mode parameters will be changed and therefore some services
cannot be accessed.
4. The PLMN_ACCEPT_BY_DL_DT_SWITCH under the "MocnControlSwitch2" parameter takes effect only when
the End_Reroute_CN_No Response_SWITCH under the "MocnControlSwitch2" parameter is set to OFF.
5. When setting switches of MOCN-related functions, ensure that the license-controlling MOCN initialization
package or cell-level license-controlling MOCN introduction package has been enabled for the secondary operator.
-To enable the license-controlling MOCN initialization package, run the following command:
SET LICENSE: SETOBJECT=UMTS, OperatorType=SEC, FUNCTIONSWITCH4=MOCN_PACKAGE-1;
-To enable the cell-level license-controlling MOCN introduction package, run the either of the following commands:
ADD UCELLLICENSE: CellId=xx, FuncSwitch1=MOCN_INTRODUCE_PACK_SWITCH-1;
MOD UCELLLICENSE: CellId=xx, FuncSwitch1=MOCN_INTRODUCE_PACK_SWITCH-1;
Before setting the "LoadSharePropCtrlSwitch" parameter to MANUALMODE, run the "LST URNCMAP" command
to query the value of the "LoadShareRscRelatCap" parameter for each logical RNC. The "LoadShareRscRelatCap"
parameter specifies the weight in overflow RNC resource occupation for a logical RNC. Running the "SET
UPOOLFLOWCTRLPARA" command will cause changes in the values of counters under the RAB.NODESHARE
and RRC.NODESHARE measurement units.
If you run this command to disable the Control-plane load sharing function, UEs involved in the ongoing load
sharing procedure will experience call drops.
After this command is executed, the statistical results of the KPI self-healing function for the RNC in Pool Load
Sharing feature are recalculated.
None
RNC external CBS cannot work if the "CBSwitch" is on.
1. After this command is executed, the ongoing network optimization performed based on performance call history
1.Starting the MR collecting function for all cells under the RNC increases the amount of data transmitted on the
control plane, thereby increasing the possibility of control plane congestion over the Uu and Iub interfaces.
2.This command is used to set the RNC-level MR switch. The "SET UMRSCOPE" command can also be used to
set the RNC-level MR switch. The latest parameter setting prevails.
1. You cannot change the data synchronization mode from Manual configuration to Auto synchronization for the
master RNC.
2. If the Data Synchronization Mode parameter is set to Auto Synchronization, logical data on the master RNC will
be automatically synchronized with that on the backup RNC and overflow RNC.
3. If the Data Synchronization Mode parameter is set to Manual Configuration, RNC in Pool data consistency
requires manual operations, otherwise it may cause service failures.
None
Running this command to modify flow control priorities for services deteriorates service KPIs and causes CPU
overload on devices when the system is heavily loaded. For example, reducing the flow control priority for CS
services deteriorates CS service KPIs while raising the flow control priority for PS services exacerbates the CPU
overload situation on devices when the system is heavily loaded.
This command is valid when the Service FC Priority Configuration Switch is set to ON in MML command SET
FCSW.
1. The retransmit mechanism will be used if the signaling is sent by adopting RLC UM on Uu interface during
channel handover.In this case, the setting of the corresponding waiting response timer for UE does not work.(For
example, when the channel change from DCH to FACH or the channel change from FACH to DCH, the timer does
not work.)
The retransmit timer is 2 seconds. The RB reconfig message will retransmit three times when the timer is out.
2. This parameter is in units of milliseconds, seconds, and minutes.
3. All parameters in this command are advanced parameters. To modify any parameter, contact Huawei Customer
Service Center for technical support.
4. If the parameters in this command are inappropriately set, call drops or access failures occur.
1. Each combination of parameters, such as [CM cell type], [CM method] and [Compressed mode measure type],
must be configured with related data.
2. For the compressed mode associated with the inter-frequency measurement, the related parameter
configuration interface is displayed after [CM cell type], [CM method] and [Compressed mode measure type] are
configured.
3. For the compressed mode associated with the inter-RAT measurement or with inter-frequency and inter-RAT
measurements, the related parameter configuration interface is displayed after [CM cell type], [CM method],
[Compressed mode measure type], and [Compressed mode purpose], [Compressed mode purpose B] or
[Compressed mode purpose C] are configured.
4. [Compressed mode purpose], [Compressed mode purpose B], and [Compressed mode purpose C] correspond
to three sequences, each of which applies to a type of measurement.
After this command is executed, the encryption algorithm supported by the RNC will be changed and therefore
service encryption is affected. For example, encryption algorithm inconsistency will result in speech noise.
1. There must be integrity protection in safe mode. At present, only one algorithm UIA1 is supported. Therefore, the
CN, RNC, and UE are all required to support UIA1.
2. After this command is executed, the integrity protection algorithm supported by the RNC will be changed and
therefore some services cannot be accessed.
If the parameters in this command are inappropriately set, load imbalance occurs on the user plane and the traffic
on the user plane is affected.
1. Only the administrator can execute this command.
2. After this command is executed, the commands that are already executed in batches cannot be rolled back, and
the commands that are not still executed cannot be executed.
1. This command cannot be executed when a single OMU is configured.
2. After this command is executed, a standby OMU stops synchronizing data with the related active OMU. If the
data on the active OMU changes, data on the active OMU will become inconsistent with data on the standby OMU.
A follow-up active/standby switchover will cause data loss.
3. After data synchronization between a pair of active and standby OMUs stops, you can run the "STR DATASYNC"
command to manually restart data synchronization between them.
1. If "Task ID" and "Task Name" are specified simultaneously or one of the parameters is specified, the scheduled
task is stopped according to the task name or task number. If no parameter is specified, all the scheduled tasks are
stopped.
2. The task with the ID greater than or equal to 100 is a system scheduled task.
3. Only the system administrator and the network administrator have the authority to execute this command.
You can run the STP UPGRADE command to stop the upgrade server manually when it fails to be stopped. The
upgrade tool automatically stops the upgrade server after the upgrade is complete in normal conditions. Do not run
this command during an upgrade. Otherwise, the upgrade will fail.
The OMU OS patch installation tool automatically stops the OMU OS patch installation server in normal conditions.
You can run the STP UPSRV command to stop the server when it fails to quit. Do not run this command during
patch installation. Otherwise, the patch installation will fail.
1. This command is a risky command. If the ARP entry configuration is incorrect or the MAC address of the nexthop equipment changes, services on an interface board will be interrupted. When using this command, contact
Huawei Customer Service Center for help.
2. When a static APR entry is bound to an aggregation trunk group, if the interface boards work in active/standby
mode, the slot number is the same as the board logical slot number. In other cases, the slot number is the same as
the board physical number.
3. If the value of "MAC Address" is the same as that of an interface board port, or the value of "IP Address" is
included in the ARP entry, a static ARP entry cannot be bound.
4. The IP address to bind must be on the same network segment as the IP address of an interface board port or a
trunk group, and the two IP addresses must be different.
5. This command is a maintenance command. The static ARP entry will be automatically deleted when the time
expires or the interface board receives ARP packets from the next-hop transmission equipment.
6. If interface boards work in active/standby mode, after interface board switchover, the expiration time of a static
ARP is calculated again.
7. A maximum of 32 static ARP entries can be bound to a stand-alone interface board or active and standby
interface boards.
1. The OMU PXE service cannot be enabled when both the OS versions and OMU software versions for the active
OMU are the same as those for the standby OMU.
2. After this command is executed and the operating system is installed successfully, the system automatically
disables OMU PXE service. If the operating system and software need to be reinstalled, run this command again to
enable OMU PXE service, thereby preventing the operating system and software from being repeatedly installed.
3. When you restart the software process by running the RST OMUMODULE command or manually reset the
OMU, the running OMU PXE service automatically stops.
4. If the automatic installation progress of the standby OMU is greater than or equal to 50%, the active OMU
cannot detect the installation of the standby OMU. In this situation, if related processes become abnormal or the
communication between the active and standby OMUs is interrupted, the reported installation progress may be
inconsistent with the actual installation progress. If the progress times out, run the DSP OMU command to query
the value of Operational state of the standby OMU. If the value is Standby normal, the standby OMU has been
installed successfully.
2. Running of this command may break the link temporarily or interrupt the ongoing services.
3. The GCUa/GCGa/GCUb/GCGb board is a clock board, the clock is initialized after the board is started. Normally,
the clock initialization takes about 25 minutes, and the time may differ according to the network conditions.
The board switchover during the clock initialization may fail in the following case, and the message "Clock is
initializing, swap Board is not allowed" is returned after the "SWP BRD" command is executed.
1) The reference clock source of the standby board is unavailable.
2) The current clock source is not locked.
3) The current clock source is locked for less than 10 minutes.
After a switchover is complete, the switchover can be performed again after the clock is initialized (about 25
minutes). The clock state can be viewed through the "DSP CLK" command.
4. If the boards are not backed up, the switchover cannot be performed. The backup state can be viewed by
running the "DSP BKP" command.
5. If the board does not have a standby board, the switchover cannot be performed.
6. If an alarm of major or higher severity exists in the standby board, an Standby board reject swap message may
be returned. In this case, clear the alarm on the standby board according to the alarm handling suggestion before
running the command.
7. The swap protection is started after board startup and can last about 3 minutes, depending on the board class.
Protection period could persist some time after data backup status becomes fine. The full configured board may
take more time as the data backup period is longer.
8. Before running this command on an SCU in the MPS, check whether any of the following alarms are reported for
the communication between the standby SCU and the active OMU. If yes, clear the alarm according to the online
help before running this command; otherwise, the host boards will be disconnected from the OMU after this
command is executed.
1) ALM-20223 Communication Between GE Switching Board and OMU Faulty.
2) ALM-20228 GE Link Between GE Switching Board and Service Board Faulty.
9. After the boards are switched over, the counter values for the active and standby boards are unreliable in the
first measurement period.
10. It takes certain time for the fault to be detected after a board reset. Meanwhile, the active board will become the
standby board and then become faulty after an active and standby board switchover. Therefore, do not perform
data configuration during the 15s after a board switchover. If you perform data configuration during this period, data
on the OMU and the host board may become inconsistent.
11. If a configuration command is executed and the configured data needs to take effect on a faulty board
(excluding boards that are prohibited or not in position), the command execution will fail to prevent data
1.
Before this command
is executed,
can run
the You
"CHK
MODEDATA"
command
to checktowhether
thestatus of
inconsistency
between the
OMU and you
the host
board.
can
run the "DSP
BRD" command
query the
conditions
a board. of the mode switchover are satisfied.
2.
thisconfiguration
command is needs
executed,
need to run
thea "RST
command
to perform
soft resettooninhibit
the active
12.After
If data
to beyou
performed
when
boardOMU"
is faulty,
run the "INH
BRD" acommand
the
and
faultystandby
board. OMUs to validate the working mode after the switchover. Do not perform any configuration operations
before
the "RST
Otherwise,
data for
other
modes
take effect.
13. Thisrunning
command
cannotOMU".
be executed
to switch
over
the working
SCU boards
in awill
subrack
where an SCUb board and an
3.
Afterboard
this command
is executed,
you need to
download the new license file to the OMU by running the "DLD
SCUc
are configured
in active/standby
mode.
LICENSE" command and then activate the license file by running the "ACT LICENSE" command.
1. This command can be executed only when the active and standby OMUs work properly and the Ethernet
adapters and hard disk on the standby OMU are normal. In addition, this command can be executed when at least
one of the following conditions are met:
(1) The data synchronization between the active and standby OMUs is normal when the versions of the active and
standby OMUs are the same.
(2) The version of the active OMU is different from that of the standby OMU.
(3) A failure switchover occurs between the active and standby OMUs.
2. Stop running configuration commands before running this command.
3. After this command is executed successfully, the active and standby switchover is performed and the ongoing
services are interrupted for a short time.
4. After this command is executed successfully, initial data synchronization between the active and standby OMUs
is started if the versions of the active and standby OMUs are the same. Five minutes later, realtime data
synchronization is started.
5. If a built-in NE is configured and the active/standby status of the built-in OMU is the same as that of the host
OMU, running this command will cause inconsistency in the active/standby status between the built-in OMU and
the host OMU. If "DualStatBindSW" in the "SET OMUPARA" command is set to ON for the host NE, the built-in
OMU triggers an automatic active/standby OMU switchover when the switchover conditions are met.
1. Switching the working area of the OMU changes the version and data of the OMU and disrupts the services on
the OMU.
2. In dual-server mode, to keep the data of the standby OMU consistent with those of the active OMU, you should
ensure that the following conditions are met before running this command:
(1) The active and standby OMUs work normally.
(2) No other users log in to the system.
(3) The data is not modified within five minutes.
(4) The data synchronization is normal.
3. To keep normal OMU switchover, you should ensure that the standby working area is normally installed.
4. Before running this command, you should ensure that no other operations are performed on the OMU.
5. After the switchover of the active and standby working areas of the active OMU, run the "RST BSC" command to
reset the BSC so that the OMU data is consistent with the host data.
6. If you want to switch over workspaces for a pair of active and standby OMUs, you must switch over the active
and standby workspaces of the standby OMU first and then the active and standby workspaces of the active OMU.
7. This command can be executed only during software upgrades or rollbacks.
8. Before running this command, run the "LST SUBNET" command to query the values of "SUBNET" and
"EXSUBNET". After this command is executed successfully, run the "LST SUBNET" command to query the values
of "SUBNET" and "EXSUBNET" again. If the queried values are different before and after the command execution,
run the "SET SUBNET" command to set these two parameters to the values before the switching.
9. After the OMU workspace is switched to a version earlier than V100R017C00SPC500 by running this command,
if the password of user admin was not changed before the switching, the password remains unchanged; otherwise,
the
passwordthe
of working
user admin
restored
to changes
the password
set before
mbsc@com.
1. Switching
areaisof
the SAU
the version
and delivery,
data of the
SAU and disrupts the services on
10.
If
the
active
workspace
version
is
V100R017C00
or
later
and
the
standby
workspace version is earlier than
the SAU.
V100R017C00,
after
theswitchover,
password of
user
db_user
is changed
in the active
workspace,
thisSAU
command
cannot be
2. To keep normal
SAU
you
should
ensure
that the standby
working
area of the
is normally
executed.
If
this
command
is
executed
in
the
preceding
scenario,
the
OMU
workspaces
will
become
abnormal.
installed.
3. Before running this command, you should ensure that no other operations are performed on the SAU.
4. When multiple SAUs are configured, the work areas of all the SAUs will be switched over if the subrack number
and slot number are not specified.
1. As running this command disrupts the services, you are advised to use this command with caution.
2. After you run this command with the "Area flag" parameter set to PRIMARY on a board with patches installed,
the patch information is removed from this board. If the board attempts to perform a self-restart later, these patches
cannot be installed. Therefore, you must run the "RMV PATCH" command to remove these patches and then run
the "INS PATCH" command to reinstall these patches after you run the "SYN BRDAREA" command with the "Area
flag" parameter set to PRIMARY. You can run the "LST PATCH" command to query the patch status.
1. The ME will be completely uninstalled after the "UNI ME" command is executed. Therefore, exercise caution
when running this command.
2. If this command is executed for an ME that does not exist, the command execution will succeed.
3. If the MEs work in active/standby mode, ensure that the active and standby OMUs work properly when you
uninstall the MEs. If the standby OMU is abnormal, the command execution will time out and only the ME on the
active OMU will be uninstalled.
1. Executing this command takes around 15 minutes. During the software upgrade, do not reset the fan box or the
active SCU installed in the same subrack as the fan box. Otherwise, the software upgrade will fail.
2. This command will reset the fan box. Exercise caution when performing this operation.
1. Only one Joint Test Action Group (JTAG) operation can be performed in a time within a subrack.
2.Running the "UPD JTGCPLD" command will cause the board to be unavailable for 5-15 minutes. Exercise
caution when running this command.
3. If the EOMUa boards work in active/standby mode, run this command to upgrade the CPLD of the standby
EOMUa board. Then, run the "SWP OMU" command to switch over the active and standby EOMUa boards. After
that, run this command to upgrade the CPLD of the original active EOMUa board.
1.Executing this command takes around 15 minutes. During the software upgrade, do not reset the power
allocation monitoring unit or the SCU installed in the same subrack as the power allocation monitoring unit.
Otherwise, the software upgrade will fail.
2.This command will reset power allocation monitoring unit. Exercise caution when performing this operation.

High Risk Command List

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

High Risk Command List

Transféré par

Droits d'auteur :

Formats disponibles

BSC6910 UMTS High-Risk Command List

Use this command to add an ACL rule.

Use this command to add a subrack during

Use this command to add a debugging

Use this command to add the TCP IP

Use this command to add a simplified CBS

Use this command to add cell access

Use this command to add a CN node.

Use this command to add parameters for

Use this command to add the transport format

Use this command to add a neighboring RNC.

Use this command to obtain and lock the

Use this command to add the basic

Use this command to block an AAL2 path.

Use this command to block a subsystem of

During cell or cell common channel

Use this command to deactivate an MTP3

Use this command to deactivate an MTP3

Use this command to forcibly obtain the

Use this command to preempt control rights of

Use this command to hand over a cell forcibly.

Use this command to inhibit a board.

Use this command to inhibit an MTP3

Use this command to inhibit a DSP.

Use this command to inhibit the standby SCU

Use this command to install the Management

Use this command to lock all scheduled tasks.

Use this command to forcibly load the rule

Use this command to modify an ACL rule.

Use this command to modify the configuration

Use this command to set a device certificate

Use this command to change the board type

Use this command to modify the OMU IP

Use this command to modify packet filter

Use this command to modify the settings for

Use this command to modify a factor table.

Use this command to modify a transport

Modify the basic information of a cell, including

Use this command to modify the parameters

Modify Cell-Orientated Queuing and

Use this command to modify a CN node.

Use this command to modify a CN Operator.

Use this command to modify a UMTS operator

Use this command to modify NodeB

Use this command to modify a neighboring

Use this command to modify RNC basic

Use this command to modify a mapping

Use this command to modify the

Use this command to modify the basic

Use this command to modify typical RAB

Mod HSPA Information for a typical signalling.

Use this command to modify typical SRB

Modify the radio link control parameters of

Use this command to modify semi-static

Use this command to specify whether to

Use this command to release the control rights

Use this command to remove an AAL2 path.

Use this command to remove an AAL2 route.

Use this command to remove an ACL rule.

Use this command to remove a transport

Use this command to remove a transport

Use this command to remove a board. This

Use this command to remove a link from a

Use this command to remove an external