Professional Documents
Culture Documents
01
Date
2013-05-04
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2013-05-04)
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Product Version
The following table lists the product versions related to this document.
Product Name
Product Version
BSC6910
V100R015C00
BTS3900
V100R008C00
The mapping single-mode
base station versions are:
l GBTS: V100R015C00
l eGBTS: V100R015C00
BTS3900A
BTS3900L
BTS3900AL
DBS3900
Intended Audience
This document is intended for:
l
Maintenance engineers
Organization
1 Change in the GBSS Capacity Monitoring Guide (BSC6910-Based)
Issue 01 (2013-05-04)
ii
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
The section provides information about the changes in different document versions of GBSS
Capacity Monitoring Guide (BSC6910-Based).
2 System Capacity Data Collection
This section describes how to collect, monitor, and analyze measurement results of performance
counters related to GBSS capacity on the M2000 client.
3 Capacity Counter Categories and Capacity Problem Locating Methods
This chapter describes key performance counters related to all capacity resources and provides
the methods for identifying and troubleshooting resource bottleneck.
4 Radio Resource Monitoring
Monitoring radio resources involves monitoring the loads of PCHs, SDCCHs, TCHs, and
PDCHs.
5 Equipment Resource Monitoring
Monitoring equipment resources involves monitoring the loads of EGPUa/EXPUa boards,
interface boards, and inter-subrack BSC communication resources.
6 Transmission Resource Monitoring
Monitoring transmission resources involves monitoring the loads of A, Gb, and Abis interface
transmission resources.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates a hazard with a high level or medium level of risk
which, if not avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not
avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
Issue 01 (2013-05-04)
iii
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Convention
Description
Boldface
Italic
Courier New
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Italic
[]
{ x | y | ... }
[ x | y | ... ]
{ x | y | ... }*
[ x | y | ... ]*
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
>
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Issue 01 (2013-05-04)
iv
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Key 1, Key 2
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 01 (2013-05-04)
Action
Description
Click
Double-click
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Contents
Contents
About This Document.....................................................................................................................ii
1 Change in the GBSS Capacity Monitoring Guide (BSC6910-Based)..................................1
2 System Capacity Data Collection...............................................................................................3
3 Capacity Counter Categories and Capacity Problem Locating Methods...........................4
3.1 Capacity Counter Categories..........................................................................................................................................5
3.2 Capacity Monitoring and Problem Locating Methods...................................................................................................9
3.2.1 Methods for Locating Capacity Problems...................................................................................................................9
3.2.2 Methods for Troubleshooting Capacity Problems.....................................................................................................10
Issue 01 (2013-05-04)
vi
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
01 (2013-05-04)
This is the first commercial release of GBSS14.0.
Compared with issue Draft A (2013-02-27) of GBSS14.0, this issue includes the following new
topics:
l
Compared with issue Draft A (2013-02-27) of GBSS14.0, this issue includes the following
incorporate changes:
Content
Description
Compared with issue Draft A (2013-02-27) of GBSS14.0, this issue excludes the following new
topics:
Issue 01 (2013-05-04)
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Draft A (2013-02-27)
This is the Draft A release of GBSS15.0.
Issue 01 (2013-05-04)
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
This section describes how to collect, monitor, and analyze measurement results of performance
counters related to GBSS capacity on the M2000 client.
Prerequisites
l
You have logged in to the M2000 client. The M2000 client communicates with NEs
properly.
Context
For the ease of daily capacity load monitoring, collect measurement results of performance
counters on the M2000. The performance counters are measured in a 15-minute, 60-minute, or
24-hour measurement period. In normal cases, you are advised to analyze 60-minute traffic
statistics measured in peak hours every day and use an Excel file to make a graph of the capacity
load trend.
NOTE
l For details about how to collect performance counters and monitor the counters in real time, see
"Performance Management" in the M2000 online help.
l Peak hours in a day refer to the time when the BSC traffic volume reaches the maximum.
Procedure
Step 1 On the M2000 client, register a user-defined measurement task for collecting measurement
results of capacity-related counters.
Step 2 On the M2000 client, periodically collect the measurement results.
Step 3 Analyze and evaluate the measurement results by using the methods and standards provided in
this document. In addition, provide an analysis report on capacity monitoring.
----End
Issue 01 (2013-05-04)
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Issue 01 (2013-05-04)
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
CAUTION
l With the network development, network capacity is dynamically changing. Therefore, the
capacity expansion specifications for capacity-related counters are changeable. If a new
service is deployed or a new charging policy is used, the traffic model and number of
subscribers may change abruptly. This leads to a sudden change in the loads of network
capacity resources. In this situation, you are advised to predict and analyze the changes and
determine the capacity optimization solution for the network where traffic volume increases
rapidly, a new service needs to be deployed, or a new charging policy is used. Contact local
Huawei engineers if you require capacity evaluation and optimization services, including
capacity prediction, evaluation, adjustment, and expansion.
l The capacity expansion specifications described in this document are defined for the network
with a stable increase in the traffic volume and for reference only. These specifications can
be customized according to the actual situation.
l The capacity expansion specifications described in this section are lower than the actual alarm
generation thresholds so that capacity problems can be located in advance.
Counter
Capacity Expansion
Specification
2%
or
PCH load
70%
2%
2%
3%
Resource
Counter
Capacity Expansion
Specification
70%
Issue 01 (2013-05-04)
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Resource
Counter
Capacity Expansion
Specification
TC load of UP subsystem
70%
70%
70%
60%
0.01%
Counter
Capacity Expansion
Specification
l Flex Abis:
3%
Congestion Rate of
Dynamic Resource
Assignment (16 kbit/s)
or
Congestion Rate of
Dynamic Resource
Assignment (8 kbit/s)
l Non-Flex Abis:
3%
Percentage of failed
application attempts of
Abis timeslots because of
no idle timeslot (in nonFlex Abis mode)
Issue 01 (2013-05-04)
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Counter
Capacity Expansion
Specification
A over IP (Signaling)
Receive bandwidth
requirement/Bandwidth
allocated by the transport
bearer network
70%
or
Transmit bandwidth
requirement/Bandwidth
allocated by the transport
bearer network
A over IP (Traffic)
Forward Bandwidth
Allocated to IP Transport
Adjacent Node/Bandwidth
allocated by the bearer
network
70%
or
Backward Bandwidth
Allocated to IP Transport
Adjacent Node/Bandwidth
allocated by the bearer
network
or
Mean Receive Rate of the
FEGE Ethernet Port/
Bandwidth of the physical
Ethernet port
or
Mean Transmit Rate of the
FEGE Ethernet Port/
Bandwidth of the physical
Ethernet port
Issue 01 (2013-05-04)
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Resource
Counter
Capacity Expansion
Specification
Gb over IP
Forward Bandwidth
Allocated to IP Transport
Adjacent Node/Bandwidth
allocated by the bearer
network
70%
or
Backward Bandwidth
Allocated to IP Transport
Adjacent Node/Bandwidth
allocated by the bearer
network
or
Mean Receive Rate of the
FEGE Ethernet Port/
Bandwidth of the physical
Ethernet port
or
Mean Transmit Rate of the
FEGE Ethernet Port/
Bandwidth of the physical
Ethernet port
6.4.2 Abis over IP
Forward Bandwidth
Allocated to IP Transport
Adjacent Node/Bandwidth
allocated by the bearer
network
70%
or
Backward Bandwidth
Allocated to IP Transport
Adjacent Node/Bandwidth
allocated by the bearer
network
or
Mean Receive Rate of the
FEGE Ethernet Port/
Bandwidth of the physical
Ethernet port
or
Mean Transmit Rate of the
FEGE Ethernet Port/
Bandwidth of the physical
Ethernet port
Issue 01 (2013-05-04)
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Issue 01 (2013-05-04)
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
NOTE
The analysis report on the capacity problem is provided after capacity data collection and analysis are
complete.
10
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
The BSS capacity resources are correlated because of resource sharing. Insufficiency in a certain
type of resource unnecessarily indicates resource insufficiency in the entire BSS. Some capacity
problems can be resolved by resource adjustment and optimization, and others require capacity
expansion. Before expanding capacity, you are advised to comprehensively analyze related
resources. Table 3-5 lists the recommended solutions to common capacity problems.
For example, TCHs, PDCHs, and SDCCHs can be mutually converted. Therefore, insufficiency
in TCHs, PDCHs, or SDCCHs unnecessarily requires capacity expansion. If SDCCHs are
insufficient, you can decrease the number of TCHs or enable the dynamic SDCCH conversion
function. If SDCCHs, TCHs, and PDCHs are insufficient at the same time, comprehensively
analyze the three types of channels and determine whether the problem can be resolved by
channel optimization. If the problem persists, perform capacity expansion on the BSS.
Overall capacity evaluation is necessary especially for the networks where the traffic volume
increases rapidly and before a new charging policy is used. Based on the capacity evaluation,
formulate a feasible plan for monitoring network capacity and detecting resource insufficiency.
Table 3-5 Solutions to common capacity problems
If...
Then...
PCHs are
overloaded
SDCCHs are
congested
TCHs are
congested
PDCHs are
congested
2. Add TRXs.
Issue 01 (2013-05-04)
The control
plane (CP) is
overloaded
CS service
processing
boards are
overloaded
PS service
processing
boards are
overloaded
Transmission
resources are
overloaded
11
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
NOTE
If the BSC has been fully configured and board expansion is required, add a BSC.
Issue 01 (2013-05-04)
12
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Issue 01 (2013-05-04)
13
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
PCH loadThis counter is a calculation counter, which reflects the percentage of paging
times to the PCH paging capability. The formula for calculating the PCH load is as follows:
PCH load = (A330: Delivered Paging Messages for CS Service + A331: Delivered Paging
Messages for PS Service)/PCH paging capability x 100%
where, the PCH paging capability provides a basis for planning location areas (LAs)
because paging messages are sent on a basis of LA. The formula for calculating the PCH
paging capability is as follows:
PCH paging capability = [(Number of CCCH blocks - Number of CCCH blocks reserved
for AGCH) x Time for sending a BCCH multiframe] x Paging message combination
efficiency x Um interface usage between paging groups x 3600
NOTE
Impact on System
l
Issue 01 (2013-05-04)
Call MSs are paged on PCHs. In the GSM system, paging is performed on a basis of location
area (LA). If the actual paging volume in an LA exceeds the theoretical PCH paging
capacity, PCHs become congested and even overloaded. This decreases the paging success
rate and deteriorates user experience.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
The BSS reports ALM-21822 Cell PCH Congestion when PCHs in a cell are congested.
Recommended Measures
l
Enable the GBFD-511503 Dynamic Multiple CCCH feature to expand the PCH capacity.
Impact on System
GSM signaling services are carried on SDCCHs. An MS needs to occupy an SDCCH each time
the MS initiates an SMS, performs a location update, or sets up a call. If SDCCHs are insufficient,
an MS fails to initiate SMS, a calling MS cannot access the network, and a called MS cannot
respond. SDCCHs are vital to process services, and therefore normal operation of SDCCHs
needs to be preferentially ensured. In normal cases, enable the dynamic SDCCH conversion
function to ensure that SDCCHs are sufficient.
Recommended Measures
l
Expand TRX capacity if SDCCHs, TCHs and PDCHs are all congested at the same time
or SDCCHs are still congested after the dynamic SDCCH conversion function is enabled.
Issue 01 (2013-05-04)
15
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Impact on System
If TCHs are insufficient, CS services have difficulties accessing the network. This greatly
deteriorates user experience.
Recommended Measures
l
Enable TCHHs and lower the threshold for enabling TCHHs. Note that the voice quality
of TCHHs is a little poorer than that of TCHFs.
Issue 01 (2013-05-04)
Uplink TBF Congestion Rate: This counter provides the percentage of TBF establishment
failures on the uplink due to insufficient resources.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
16
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Downlink TBF Congestion Rate: This counter provides the percentage of TBF
establishment failures on the downlink due to insufficient resources.
Impact on System
If PDCHs are insufficient, the GPRS/EDGE service rate decreases, and even some MSs cannot
process PS services.
Recommended Measures
l
The PDCH proportion threshold for a cell is set to a small value, and therefore few
TCHs can be converted to PDCHs. As a result, PDCHs are insufficient but some TCHs
are idle during peak hours. In this situation, increase the PDCH proportion threshold.
2.
The channels in a cell are insufficient, and therefore TCHs and PDCHs are insufficient
for processing services during peak hours. In this situation, optimize related
parameters or expand TRX capacity.
Check the following counters to determine the root causes for insufficient PDCHs:
Percentage of PDCH application failures due to the limited PDCH proportion threshold
= R9395: Number of PDCH Application failures For CELL PDCH Ratio Thresh/R9393:
Number Of PDCH Application Attempts
Percentage of PDCH application failures due to no TCH available = R9394: Number
of PDCH Application Failures due to no Convertable TCHs/R9393: Number Of PDCH
Application Attempts
If the PDCH proportion threshold is set to a value that is too small, increase the threshold.
If TCHs and PDCHs in a cell are insufficient during peak hours, expand TRX capacity.
Issue 01 (2013-05-04)
17
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Issue 01 (2013-05-04)
18
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
The EGPUa or EXPUa board is used to process services on the GSM BSC control plane and user plane.
For details about the functions of the EGPUa or EXPUa board, see Technical Specifications of the EGPUa
Board and Technical Specifications of the EXPUa Board, respectively.
Impact on System
l
When the CPU becomes overloaded, the BSC triggers the flow control during which paging
messages or channel request messages are discarded. This results in access problems. If
the CPU is severely overloaded, a large number of subscribers cannot access the network.
When this occurs, the BSS automatically forbids maintenance activities such as collecting
logs and obtaining traffic statistics files.
If the CPU of the EGPUa or EXPUa board becomes overloaded, the BSS reports
ALM-20256 CPU Overload.
Recommended Measures
Monitor the CPU load on the EGPUa or EXPUa board based on the value of the AR9720:
Average CPU Usage of the CPU counter during peak hours of a day. You are advised to:
l
Expand EGPUa or EXPUa boards when the value of this counter exceeds 70% during peak
hours for successive three or more days on a network with slow service growth.
Analyze capacity requirements and formulate a capacity expansion solution when the value
of this counter exceeds 50% on a network with rapid service growth.
Issue 01 (2013-05-04)
19
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
l If the EGPUa or EXPUa board functions as the GCUP, the maximum traffic volume supported by an
EGPUa or EXPUa board is 6250 Erl.
l If the EGPUa or EXPUa board functions as the GCUP and works in resource pool mode, you are
advised to configure at least two EGPUa or EXPUa boards for a BSC6910.
Impact on System
Insufficient CS resources cause call setup failures, severely deteriorating user experience. This
is because CS resources of the UP subsystem are used to process speech coding and decoding.
Recommended Measures
Expand EGPUa or EXPUa boards.
Issue 01 (2013-05-04)
20
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
NOTE
l If the EGPUa or EXPUa board functions as the GCUP, the maximum number of PDCHs supported by
an EGPUa or EXPUa board is 3000.
l If the EGPUa or EXPUa board functions as the GCUP and works in resource pool mode, you are
advised to configure at least two EGPUa or EXPUa boards for a BSC6910.
Impact on System
If EGPUa or EXPUa boards which processes PS services are insufficient, some PDCHs cannot
be activated. This causes a decrease in PS service rate and difficult access.
Recommended Measures
Expand EGPUa or EXPUa boards.
21
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Impact on System
l
If the forwarding load over an interface is too high, the BSS may discard some messages.
This deteriorates the quality of service (QoS) of CS and PS services.
If the forwarding load of an interface board is too high, the BSS reports ALM-20275
Forwarding Overload of An Interface Board.
Recommended Measures
Expand the capacity of interface boards.
The inter-subrack BSC communication bandwidth is 40 Gbit/s when active and standby
SCUb boards are configured.
Peak inter-subrack traffic usage > 60% (Prewarning and analysis is required.)
Average inter-subrack traffic usage > 40% (Prewarning and analysis is required.)
Inter-subrack packet loss rate > 0.01% (Prewarning and analysis is required.)
Issue 01 (2013-05-04)
22
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Impact on System
l
If the forwarding load over an interface is too high, the BSS may discard some messages.
This deteriorates the quality of service (QoS) of CS and PS services. The Main Processing
Subrack (MPS) is connected to the Extended Processing Subrack (EPS) using the port trunk
group on the SCU panel. When the inter-subrack BSC communication capacity is close to
the overload threshold, the QoS of CS and PS services and network KPIs deteriorate, and
the BSS becomes unstable.
If the actual link bandwidth usage of the port trunk group on the SCU panel exceeds the
congestion threshold (70%) or the packet loss rate over a link exceeds the congestion
threshold (0.02%) for 5 minutes or longer, the BSS reports ALM-20277 Communication
Congestion Between Subracks.
Recommended Measures
The inter-subrack BSC communication capacity seldom becomes overloaded. If this occurs,
contact Huawei maintenance engineers for in-depth analysis and troubleshooting.
Issue 01 (2013-05-04)
23
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Issue 01 (2013-05-04)
24
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
l SCTP links have no bandwidth configurations. Therefore, when STCP links are used, monitor the
bandwidth resources occupied by SCTP links and check whether the transmission resources on the
bearer network meet the bandwidth requirements.
Impact on System
l
SS7 link overload causes congestion and packet loss. This affects the signaling procedure
and CS service processing.
If SCTP links are congested, the BSS reports ALM-21542 SCTP Link Congestion.
Recommended Measures
Add SCTP links. To ensure the control plane reliability, configure SCTP links in load sharing
mode. The configuration rule is as follows:
1.
2.
At least one SCTP link is configured for each pair of EGPUa/EXPUa boards.
3.
A maximum of one SCTP link is configured for each subsystem on a EGPUa/EXPUa board.
Issue 01 (2013-05-04)
25
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Load of the Ethernet port = [T7123: Mean Receive Rate of the FEGE Ethernet Port]/
Bandwidth of the physical Ethernet port, or [T7128: Mean Transmit Rate of the FEGE
Ethernet Port]/Bandwidth of the physical Ethernet port
NOTE
l In IP transmission mode, the BSC and BTS are configured with FE or GE ports and use 100 or 1000
MHz transmission bandwidth.
l The bandwidth allocated by the bearer network refers to the bandwidth allocated by the A interface
backbone network.
Impact on System
l
Insufficient circuit transmission resources on the A interface lead to circuit assignment and
call setup failures. This deteriorates user experience.
If the load of physical ports exceeds the alarm threshold, the BSS reports ALM-21583 Port
Congestion.
Recommended Measures
l
Issue 01 (2013-05-04)
Ask the bearer network vendor to increase the network capacity when the load of the bearer
network exceeds 70%.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
26
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Expand interface boards when the load of the Ethernet port exceeds 70%.
6.3 Gb over IP
Related Counters
In IP transmission mode, the BSC and BTS are configured with FE or GE ports and use 100 or
1000 MHz transmission bandwidth. This basically meets the actual bandwidth requirements.
Therefore, whether the transmission resources allocated by the bearer network meet
requirements is the focus of capacity monitoring in IP transmission mode.
The load of Gb transmission resources is indicated by the following counters:
l
T7123: Mean Receive Rate of the FEGE Ethernet Port This counter provides the
receive rate of an FE or GE Ethernet port at the data link layer within a measurement period.
It indicates the data flow on an FE or GE Ethernet port at the data link layer.
T7128: Mean Transmit Rate of the FEGE Ethernet Port This counter provides the
transmit rate of an FE or GE Ethernet port at the data link layer within a measurement
period. It indicates the data flow on an FE or GE Ethernet port at the data link layer.
[T7123: Mean Receive Rate of the FEGE Ethernet Port/Bandwidth of the physical Ethernet
port] > 70%
[T7128: Mean Transmit Rate of the FEGE Ethernet Port/Bandwidth of the physical
Ethernet port] > 70%
l In IP transmission mode, the BSC and BTS are configured with FE or GE ports and use 100 or 1000
MHz transmission bandwidth.
Impact on System
l
Insufficient transmission resources on the Gb interface lead to a low GPRS or EDGE service
rate and even network access failures.
If the load of physical ports exceeds the alarm threshold, the BSS reports ALM-21583 Port
Congestion.
Issue 01 (2013-05-04)
27
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Recommended Measures
In Gb over IP mode, the BSC interface board capacity is generally sufficient. Therefore, focus
on the transmission resources allocated by the bearer network on the Gb interface. You are
advised to:
l
Expand Gb interface boards when the following condition is met: [T7123: Mean Receive
Rate of the FEGE Ethernet Port]/Bandwidth of the physical Ethernet port > 70%, or [T7128:
Mean Transmit Rate of the FEGE Ethernet Port]/Bandwidth of the physical Ethernet port
> 70%.
Ask the bearer network vendor to increase the network capacity when the following
condition is met: [T6519: Forward Bandwidth Allocated to IP Transport Adjacent Node/
Bandwidth allocated by the bearer network] > 70%, or [T6520: Backward Bandwidth
Allocated to IP Transport Adjacent Node/Bandwidth allocated by the bearer network] >
70%.
Apply for a license for the Gb over IP mode and ensure that license resources are sufficient.
Related Counters
In Flex Abis mode, all Abis TDM timeslots on the BTS can be dynamically allocated. When
the BTS receives a CS or PS service request, Abis timeslots are allocated based on the
actual requirements in real time. In this mode, the load of Abis transmission resources is
indicated by the following counters:
RR2752: Congestion Rate of Dynamic Resource Assignment (16 kbit/s)This counter
provides the congestion rate of dynamic allocation of 16 kbit/s Abis resources.
RR2751: Congestion Rate of Dynamic Resource Assignment (8 kbit/s)This counter
provides the congestion rate of dynamic allocation of 8 kbit/s Abis resources.
Impact on System
Insufficient transmission resources on the Abis interface lead to network access failures.
This deteriorates user experience.
Recommended Measures
Expand transmission resources over the Abis interface.
Issue 01 (2013-05-04)
28
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
Related Counters
In non-Flex Abis mode, Abis timeslots, except idle Abis timeslots, bear one-to-one mapping
with the TCHs and PDCHs. Therefore, Abis timeslot capacity expansion is required if TCH
and PDCH capacity expansion is performed. In this mode, the usage of idle Abis timeslots
is indicated by the following counters:
Percentage of Abis timeslot application failures due to no idle timeslot (in non-Flex Abis
mode) = [R9109: Number of Unsuccessful Application Attempts of Abis Timeslot Because
of No Idle Timeslot]/[R9101: Number of Application Attempts of Abis Timeslot]
Impact on System
Insufficient transmission resources on the Abis interface lead to difficulties in improving
the PS service rate.
Recommended Measures
Expand transmission resources over the Abis interface.
T7123: Mean Receive Rate of the FEGE Ethernet Port This counter provides the
receive rate of an FE or GE Ethernet port at the data link layer within a measurement period.
It indicates the data flow on an FE or GE Ethernet port at the data link layer.
T7128: Mean Transmit Rate of the FEGE Ethernet Port This counter provides the
transmit rate of an FE or GE Ethernet port at the data link layer within a measurement
period. It indicates the data flow on an FE or GE Ethernet port at the data link layer.
[T7123: Mean Receive Rate of the FEGE Ethernet Port/Bandwidth of the physical Ethernet
port] > 70%
[T7123: Mean Receive Rate of the FEGE Ethernet Port/Bandwidth of the physical Ethernet
port] > 70%
Issue 01 (2013-05-04)
29
GBSS15.0
GBSS Capacity Monitoring Guide (BSC6910-Based)
l In IP transmission mode, the BSC and BTS are configured with FE or GE ports and use 100 or 1000
MHz transmission bandwidth.
Impact on System
l
Insufficient transmission resources on the Abis interface decrease PS service rate, degrade
voice quality and even lead to network access failures.
If the load of physical ports exceeds the alarm threshold, the BSS reports ALM-21583 Port
Congestion.
Recommended Measures
l
Expand Abis interface boards when the following condition is met: [T7123: Mean Receive
Rate of the FEGE Ethernet Port/Bandwidth allocated by the bearer network] > 70%, or
[T7123: Mean Receive Rate of the FEGE Ethernet Port/Bandwidth allocated by the bearer
network] > 70%
Focus on checking whether the bandwidth allocated by the IP bearer network is sufficient.
Ask the bearer network vendor to increase the network capacity when the following
condition is met: [T6519: Forward Bandwidth Allocated to IP Transport Adjacent Node/
Bandwidth allocated by the bearer network] > 70%, or [T6520: Backward Bandwidth
Allocated to IP Transport Adjacent Node/Bandwidth allocated by the bearer network] >
70%.
Issue 01 (2013-05-04)
30