MSOFTX3000 ATCA Platform Data Configuration of Hardware and Module Groups-20090622-B-1.0
MSOFTX3000 ATCA Platform Data Configuration of Hardware and Module Groups-20090622-B-1.0
WG000204 Data
Configuration of Hardware
and Module Groups
ISSUE1.0
www.huawei.com
Chapter 5 Questions
ATCA
ADD BRD
A module group type specifies the number of modules, module type, and the
information about the CPU core to which the modules are bound.
Module group type is a class that has multiple objects, that is, module groups.
Standard module group types are predefined in the system. You can run the
LST PGTYPE command to query the module groups of a module group type.
You can also self-define a module group type by specifying the ratio of
modules, relation between CPU cores and modules, and CPU usage ratio of
different modules bound to the same core.
Using a self-defined module group type is risky. You can self-define a module
group type for the existing network only after analysis and test that confirm
the module group type does not affect system reliability and performance.
General
General Control Unit
Control Unit TMSC
200 (you are
101 (you are Control Unit
advised to configure
advised to VMSC Control Unit 100 (a
a maximum of one
configure two 200 (a module module
pair of this module VMSC Control Unit
General Control pairs of this group for
groups for each 100 (a module group for
Unit 100 (you are module groups expanding
subrack; if the PTU group for expanding expanding the
advised to for each the GMSC,
is configured, the VMSC)
configure a pair of subrack of the VMSC and TMSC or
configure this
this module GMSC/TMSC supporting VoBB large-
module group
groups for each running subscribers) capacity
according to the
subrack of the broadband VMSC)
actual requirements)
Description VMSC) signaling)
Module VCU100
GCU101 GCU200 VCU200 TCU100
Group GCU100
Core 1 CCU CCU CCU CCU CCU CCU CCU CCU SCU CCU CCU
Core 2 CCU CCU CCU CCU CCU CCU CCU CCU SCU CCU CCU
Core 3 CCU CCU CCU CCU CCU CCU CCU CCU SCU CCU CCU
Core 4 CCU CCU CCU CCU PTU CCU CCU CCU CCU CCU CCU
VDB(40 BSG(60% VDB(40%
Core 5 %) ) BSG ) BSG(60%) CCU CCU CCU CCU CCU CCU
VDB(40 BSG(60% VDB(40% VDB(40% VDB(40% BSG(60%
Core 6 HUAWEI
%) TECHNOLOGIES
) BSGCO., LTD. ) HUAWEI BSG(60%)
Confidential) Page 11
BSG(60%) ) ) CCU CCU
Standard module group GCU100
(General Control Unit 100)
Composition of module group
GCU100=8CCU+2VDB+2BSG+1CDB+1IFM
Every two CCU modules share a CPU core. The VDB module and BSG module
share a CPU core. The CDB module and the IFM module each occupies a CPU
core.
Configuration principle
Configuration principle
GCU101 is used in TMSCs and GMSCs. You are advised to configure a pair of
GCU101s for every half subrack. Configure GCU101s in slots 0 and 1 in the left half of
the subrack and in slots 12 and 13 in the right half of the subrack fixedly. If slots 12
and 13 are occupied by the XPTU/INU, configure GCU101s in slots 10 and 11.
Configuration principle
GCU200 is used in VMSCs and GMSCs that run narrowband signaling and support
interception and PTU IN codec. You are advised to configure a pair of GCU200s for
each subrack of the VMSC. You are advised to configure a maximum of a pair of
GCU200s for each subrack of the GMSC. You are advised to configure the GCU200s
in slots 0 and 1 in each subrack of the GMSC or VMSC.
Configuration principle
VCU100 is used in narrowband and broadband capacity expansion of the VMSC.
Configuration principle
VCU200 is used for capacity expansion of the VMSC that supports VoBB or VoBB
subscribers.
Configuration principle
TCU100 is used for capacity expansion of the GMSC or TMSC. It can also be used for
capacity expansion of the large-capacity VMSC to improve the traffic processing
capability of the CCU module and the signaling transfer capability of the BSG module.
If the ratio of modules in all module groups preset in the system does
not match the traffic model of an office, you can self-define a module
group type with a proper ratio of modules.
You can self-define up to five module group types. To self-define a
module group type, run the SET PGTYPE command to set the ratio of
modules, relation between CPU cores and modules, and CPU usage
ratio of different modules bound to the same core.
Running the SET PGTYPE command to define a module group type is
risky. You can run the SET PGTYPE command to define a module
group type for the existing network only after analysis and test that
confirm the module group type does not affect system reliability and
performance.
Chapter 5 Questions
1. The module groups suitable for the GMSC are GCU100, GCU101, and GCU200, among
which GCU101 does not support the interception function, and GCU100 and GCU101 do not
support the PTU function.
2. You are advised to configure two pairs of basic module groups for each subrack. One pair of
basic module groups supports the PTU and interception (require VDB), and the other pair of
basic module groups runs pure broadband applications or broadband and narrowband
applications without supporting the PTU and interception. One pair of basic module groups
that support the interception (require VDB) is enough for the whole MSOFTX3000 system.
3. If the MSOFTX3000 must support the PTU and interception, configure a pair of basic module
groups that support the PTU and interception (require VDB). Then, configure module groups
for capacity expansion according to the principle described in point 2. If the boards configured
occupy more than half of the subrack, configure another pair of basic module groups that do
not support the PTU and interception (require VDB).
4. If the MSOFTX3000 is not required to support the PTU and interception, configure a pair of
basic module groups that run pure broadband applications or broadband and narrowband
applications without supporting the PTU and interception for each subrack. Then, configure
module groups for capacity expansion according to the principle described in point 2. If the
boards configured occupy more than half of the subrack, configure another pair of basic
module groups that run pure broadband applications or broadband and narrowband
applications without supporting the PTU and interception.
5. Calculate the number of required CCU modules based on the number of trunk circuits or the
amount of traffic. Expand the capacity by adding TCU100s. Then, check whether the number
of BSG modules is sufficient. If not, add more TCU100s.
1. When adding a new subrack, configure the GCU100 for the first pair of boards.
You are advised to configure the GCU100 in slots 0 and 1.
2. For other capacity expansion, configure VCU100s evenly in the left half and right
half of the subrack. Do not configure VCU100s in the slots for the iGWB.
1. When adding a new subrack, configure the GCU100 for the first pair of boards.
You are advised to configure the GCU100 in slots 0 and 1. Configure GCU101 for
the first pair of boards configured in the right half of the subrack. You are advised to
configure the GCU101 in slots 12 and 13.
2. For other capacity expansion, configure TCU100s evenly in the left half and right
half of the subrack. Do not configure TCU100s in the slots for the iGWB.
1. When adding a new subrack, configure the GCU101 for the first pair of boards.
You are advised to configure the GCU101 in slots 0 and 1. Configure GCU101 for
the first pair of boards in the right half of the subrack. You are advised to configure
the GCU101 in slots 12 and 13.
2. For other capacity expansion, configure TCU100s evenly in the left half and right
half of the subrack. Do not configure TCU100s in the slots for the iGWB.
1. When adding a new subrack, configure the GCU101 for the first pair of boards.
You are advised to configure the GCU101 in slots 0 and 1. Configure GCU101 for
the first pair of boards in the right half of the subrack. You are advised to configure
the GCU101 in slots 12 and 13.
2. For other capacity expansion, configure TCU100s evenly in the left half and right
half of the subrack.
Chapter 5 Questions
Step Command
Step 4 is optional. You are not advised to run the SET PGTYPE
command to self-define module group types.
Configuration script:
ADD RACK: RN=0, RNM="RACK0", POSNUM=0, ROWNUM=0, COLNUM=0,
MOG="PUBLIC";
The boards where the system reliability management units (SRMUs) are located must
be added first. Before adding a board, run the ADD SUBRACK command to add a
subrack and specify the slot numbers of the SRMUs.
Before adding the boards where the SRMUs are located, make sure that at least one of
the two slots specified for the SRMUs in a subrack is installed with a board and the
board is working properly.
The module group type must match the board type. All service modules must be loaded
on the UPBA0.
The back boards are specified together with the front boards. Different back boards
have different numbers and types of ports. Select back boards based on the
requirements of front boards.
Chapter 5 Questions
//Add a rack.
ADD RACK: RN=0, RNM="RACK0", POSNUM=0, ROWNUM=0, COLNUM=0;
//Add a subrack.
ADD SUBRACK: SRN=0, RN=4, PN=0, SBVER=T8261, SWFBRDT=SWU1, SWBBRDT=SWI0;
//Add boards.
ADD BRD: METYPE=COMMON, FBRDHTYP=UPBA1, APPTYPE=OMU;
ADD BRD: SRN=0, SN=0, METYPE=MSOFTX, FBRDHTYP=UPBA0, BBRDHTYP=USI1, APPTYPE=MSX;
ADD BRD: SRN=0, SN=1, METYPE=MSOFTX, FBRDHTYP=UPBA0, BBRDHTYP=USI1, APPTYPE=MSX;
ADD BRD: SRN=0, SN=2, METYPE=MSOFTX, FBRDHTYP=UPBA0, BBRDHTYP=USI1, APPTYPE=MSX;
ADD BRD: SRN=0, SN=3, METYPE=MSOFTX, FBRDHTYP=UPBA0, BBRDHTYP=USI1, APPTYPE=MSX;
USE ME:MEID=5;
//Add module groups.
ADD PG: SRN=0, SN=0, ASSSLOT=2, PGTYPE=GCU100;
ADD PG: SRN=0, SN=1, ASSSLOT=3, PGTYPE=RSV0;
//Add the information about the FE port.
ADD IPADDR: IPNAME="ATCAIP", SRN=0, SN=1, PORTID=BACK5, IPVER=IPV4,
IP4="161.66.3.40", NETMASK="255.255.255.0", ARPDETECT=NEIGH, RFC=OPEN,
LFC=OPEN;
//Set service dispatch ability.
SET SPA: MN=1000, SA=BSSAP-1&RANAP-1&GS-1&MAP-1&CAP-1&INAP-1;
SET SPA: MN=1001, SA=BSSAP-1&RANAP-1&GS-1&MAP-1&CAP-1&INAP-1;
SET SCTPPARA: CHKSUMTYPE=CRC32;
Chapter 5 Questions