Hello, dear.
You can refer to the information for more information about GTMU.
GTMUEQUIPMENT
+-CABINET
+-SUBRACK
+-GTMU
+-CPRIPORT[6~6]
+-SFP[6~6]
+-USB[1~1] DescriptionThe GTMU MO performs main controlling, switching, and transmission, and provides clock sources and ports for receiving and sending GSM RF signals. This MO applies only to GSM. Effective ScenarioImmediately Relations Between MOsBase class: RU Possible parents: SUBRACK Possible children: CPRIPORT[6~6];SFP[6~6];USB[1~1] Relation with the CPRIPORT,BBP,BRI,RHUB,CXU MOs: [Co-MPT,NodeB,eGBTS,eNodeB]If ADMINISTRATIVESTATE in the CPRIPORT MO is set to BLOCKED, a BBP, BRI, GTMU, MDU, RHUB, or CXU with CXUTYPE set to RMU must be configured in the slot specified by CN, SRN, and SN in the CPRIPORT MO.
Relation with the SUBRACK MO: [Co-MPT,NodeB,eGBTS,eNodeB]The MPT, GTMU, BBP, UCIU, USCU, BRI, TRP, or UCCU MO cannot be configured under a SUBRACK MO with TYPE set to BLADEBBU. [Co-MPT,NodeB,eNodeB]The GTMU, UCIU, UCCU, BRI or TRP cannot be configured under a SUBRACK MO with TYPE set to BBU5900.
Relation with the RRUCHAIN,BBP,BRI MOs: [Co-MPT,NodeB,eGBTS,eNodeB]In the RRUCHAIN MO, when TT is set to RING and the combination of HCN, HSRN, and HSN is not the same as the combination of TCN, TSRN, and TSN, this RRUCHAIN cannot be configured on the BRI, GTMU, or BBP with TYPE set to GBBP.
Relation with other boards in the BBU subrack: [Co-MPT,NodeB,eGBTS,eNodeB]A unique combination is necessary for the following parameters: 1. CN, SRN, and SN in the GTMU MO; 2. CN, SRN, and SN in the TRP MO; 3. CN, SRN, and SN in the UCIU MO; 4. CN, SRN, and SN in the MPT MO.
Relation with the IPRT,MPT,OMCH MOs: [Co-MPT,NodeB,eGBTS,eNodeB]When a GTMU MO with TYPE set to GTMU exists, and an MPT MO with TYPE set to UMPT does not exist, and only one OMCH MO exists, for any two IPRT MOs of a base station in the same routing domain, if their RTIDX is set to a value different from that of RTIDX or SECONDARYRTIDX in the OMCH MO, and RTTYPE and IFT in any one of the IPRT MO are set to IF and TUNNEL, respectively, DSTIP in the two IPRT MOs must be set to different values. When a GTMU MO with TYPE set to GTMU exists, and an MPT MO with TYPE set to UMPT does not exist, and more than one OMCH MO exists, for any two IPRT MOs of a base station in the same routing domain, if their RTIDX is set to a value different from that of RTIDX or SECONDARYRTIDX in the OMCH MO with FLAG set to MASTER and is set to a value different from that of RTIDX or SECONDARYRTIDX in the OMCH with FLAG set to SLAVE, and RTTYPE and IFT in any one of the IPRT MO are set to IF and TUNNEL, respectively, DSTIP in the two IPRT MOs must be set to different values. When a GTMU MO with TYPE set to GTMU does not exists, or an MPT MO with TYPE set to UMPT exists, or an OMCH MO does not exist, for any two IPRT MOs of a base station in the same routing domain, if RTTYPE and IFT in any one of the IPRT MO are set to IF and TUNNEL, respectively, DSTIP in the two IPRT MOs must be set to different values.
Relation with the BBP,BRI,RHUB,CXU,RRUCHAIN MOs: [Co-MPT,NodeB,eNodeB]For an RRUCHAIN MO with TT set to CHAIN and AT set to a value other than PEERPORT, or an RRUCHAIN MO with TT set to RING or LOADBALANCE, the following MO must have been configured: 1. A BBP, BRI, GTMU, RHUB, MDU, or CXU with CXUTYPE set to RMU must have been configured. The board location is specified by HCN, HSRN, and HSN in the RRUCHAIN MO. 2. For an RRUCHAIN MO with TT set to a value other than CHAIN, a BBP MO, BRI MO, GTMU MO, RHUB MO, MDU MO, or CXU MO with CXUTYPE set to RMU must have been configured. The board location is specified by TCN, TSRN, and TSN in the RRUCHAIN MO.
Relation with the AAL2ADJNODE,MPT,APPLICATION MOs: Relation with the SDHJ0J1,MPT,APPLICATION MOs: Relation with the STM1,MPT,APPLICATION MOs: Relation with the IMALNK,MPT,APPLICATION MOs: Relation with the IMAGRP,MPT,APPLICATION MOs: Relation with the SAALLNK,MPT,APPLICATION MOs: Relation with the AAL2NODE,MPT,APPLICATION MOs: Relation with the AAL2PATH,MPT,APPLICATION MOs: Relation with the UNILNK,MPT,APPLICATION MOs: Relation with the FRAATM,MPT,APPLICATION MOs: Relation with the TREELNKPVC,MPT,APPLICATION MOs: Relation with the IP2RSCGRP6,MPT,APPLICATION MOs: Relation with the ACL6,MPT,APPLICATION MOs: Relation with the ACLRULE6,MPT,APPLICATION MOs: Relation with the IKEPEER6,MPT,APPLICATION MOs: Relation with the IPSECBIND6,MPT,APPLICATION MOs: Relation with the IPSECPOLICY6,MPT,APPLICATION MOs: Relation with the IPITF6,MPT,APPLICATION MOs: Relation with the IPPATH6,MPT,APPLICATION MOs: Relation with the IPRT6,MPT,APPLICATION MOs: Relation with the OMCH6,MPT,APPLICATION MOs: Relation with the DEVIP6,MPT,APPLICATION MOs: Relation with the ACLRULE,MPT,APPLICATION MOs: Relation with the CPBEARER,MPT,APPLICATION MOs: Relation with the IPPATH,MPT,APPLICATION MOs: Relation with the SCTPLNK,MPT,APPLICATION MOs: Relation with the ACL,MPT,APPLICATION MOs: Relation with the BFDSESSION,MPT,APPLICATION MOs: Relation with the CFMBNDIP,MPT,APPLICATION MOs: Relation with the CFMMA,MPT,APPLICATION MOs: Relation with the CFMMD,MPT,APPLICATION MOs: Relation with the CFMMEP,MPT,APPLICATION MOs: Relation with the CFMRMEP,MPT,APPLICATION MOs: Relation with the DEVIP,MPT,APPLICATION MOs: Relation with the DLFLOWCTRLPARA,MPT,APPLICATION MOs: Relation with the DOT1X,MPT,APPLICATION MOs: [Co-MPT,eGBTS]The number of DOT1X MOs is 0 when the following conditions are met: The Application MO is configured with AT set to GBTS. The GTMU MO is configured with TYPE set to GTMU and BRDSPEC not set to "GTMUc" (case insensitive) or null. The DOT1X MO is not configured with TYPE set to UMPT. [Co-MPT,eGBTS]The number of DOT1X MOs does not exceed 48 when the following conditions are met: The Application MO is configured with AT set to GBTS. The GTMU MO is configured with TYPE set to GTMU and BRDSPEC set to "GTMUc" (case insensitive) or null. The DOT1X MO is not configured with TYPE set to UMPT.
Relation with the DSCPMAP,MPT,APPLICATION MOs: Relation with the E1T1,MPT,APPLICATION MOs: Relation with the E1T1BEAR,MPT,APPLICATION MOs: [Co-MPT,eGBTS]The number of E1T1BEAR MOs is 0 when the Application MO with AT set to GBTS and the GTMU MO with TYPE set to GTMU are configured but the MPT MO with TYPE set to UMPT is not configured. [Co-MPT,eGBTS]The number of E1T1BEAR MOs with MODE set to ATM is 0 when the Application MO with AT set to GBTS and the GTMU MO with TYPE set to GTMU are configured but the MPT MO with TYPE set to UMPT is not configured.
Relation with the EP2RSCGRP,MPT,APPLICATION MOs: Relation with the EPGROUP,MPT,APPLICATION MOs: Relation with the ETHOAM3AH,MPT,APPLICATION MOs: Relation with the ETHPORT,MPT,APPLICATION MOs: Relation with the ETHTRK,MPT,APPLICATION MOs: Relation with the ETHTRKLNK,MPT,APPLICATION MOs: Relation with the HAGRP,MPT,APPLICATION MOs: Relation with the IPPATHRT,MPT,APPLICATION MOs: Relation with the IPPMSESSION,MPT,APPLICATION MOs: Relation with the IPRT,MPT,APPLICATION MOs: Relation with the MPGRP,MPT,APPLICATION MOs: Relation with the MPLNK,MPT,APPLICATION MOs: Relation with the PACKETFILTER,MPT,APPLICATION MOs: Relation with the PPPLNK,MPT,APPLICATION MOs: Relation with the PRI2QUE,MPT,APPLICATION MOs: Relation with the RSCGRP,MPT,APPLICATION MOs: [Co-MPT,eGBTS]The number of RSCGRP MOs whose RSCGRPID are not AUTOPORT must be less than or equal to 16 when the Application MO with AT set to GBTS and the GTMU MO with TYPE set to GTMU are configured but the MPT MO with TYPE set to UMPT is not configured. [Co-MPT,eGBTS]The number of RSCGRP MOs with BEAR set to ATM is 0 when the Application MO with AT set to GBTS and the GTMU MO with TYPE set to GTMU are configured but the MPT MO with TYPE set to UMPT is not configured.
Relation with the RSCGRPALG,MPT,APPLICATION MOs: Relation with the SCTPHOST,MPT,APPLICATION MOs: Relation with the SCTPLNK6,MPT,APPLICATION MOs: Relation with the SCTPPEER,MPT,APPLICATION MOs: Relation with the SUBIF,MPT,APPLICATION MOs: Relation with the SUBNETVLAN,MPT,APPLICATION MOs: Relation with the ULFLOWCTRLPARA,MPT,APPLICATION MOs: Relation with the USERPLANEPEER,MPT,APPLICATION MOs: Relation with the OMCH,MPT,APPLICATION MOs: Relation with the DNSSRV,MPT,APPLICATION MOs: Relation with the IKEPEER,MPT,APPLICATION MOs: Relation with the IPSECPOLICY,MPT,APPLICATION MOs: Relation with the IPSECBIND,ACLRULE,IPSECPOLICY,MPT,APPLICATION MOs: [Co-MPT,eGBTS]When the Application MO with AT set to GBTS and the GTMU MO with TYPE set to GTMU are configured but the MPT MO with TYPE set to UMPT is not configured, the maximum of ACLRULE with ACTION set to PERMIT which are referenced by IPSECBIND on one board is 128.
Relation with the SECURITYPEER,MPT,APPLICATION MOs: Relation with the IFIP,MPT,APPLICATION MOs: Relation with the SECTOR,MPT,NODE MOs: [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 12 sectors when it is configured with the GTMU board(the specification is configured as GTMUb) but not the UMPT board. [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 48 sector antennas when it is configured with the GTMU board(the specification is configured as GTMUb) but not the UMPT board. [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 108 sectors when it is configured with the GTMU board(the specification is not configured as GTMUb) but not the UMPT board. [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 288 sector antennas when it is configured with the GTMU board(the specification is not configured as GTMUb) but not the UMPT board.
Relation with the SECTOREQM,MPT,NODE MOs: [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 24 sets of sector equipment when it is configured with the GTMU board(the specification is configured as GTMUb) but not the UMPT board. [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 120 sector equipment antennas when it is configured with the GTMU board(the specification is configured as GTMUb) but not the UMPT board. [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 108 sets of sector equipment when it is configured with the GTMU board(the specification is not configured as GTMUb) but not the UMPT board. [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 288 sector equipment antennas when it is configured with the GTMU board(the specification is not configured as GTMUb) but not the UMPT board.
Relation with the BASEBANDEQM,MPT,NODE MOs: [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 5 uplink baseband equipment when it is configured with the GTMU board (the specification is configured as GTMUb) but not the UMPT board. [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 5 sets of downlink baseband equipment when it is configured with the GTMU board (the specification is configured as GTMUb) but not the UMPT board. [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 24 sets of uplink baseband equipment when it is configured with the GTMU board (the specification is not configured as GTMUb) but not the UMPT board. [Co-MPT,eGBTS]A DBS3900, BTS3900, BTS3900A, BTS3900L, or BTS3900AL working in non-concurrent multiple modes supports a maximum of 12 sets of downlink baseband equipment when it is configured with the GTMU board (the specification is not configured as GTMUb) but not the UMPT board.
Relation with the STATICMACITEM,MPT,APPLICATION MOs: Relation with the DIRECTIPSECBLKLST,MPT,APPLICATION MOs: Relation with the BBP,BRI,RRUCHAIN MOs: [eGBTS]For an RRUCHAIN MO with TT set to CHAIN and AT set to a value other than PEERPORT, or an RRUCHAIN MO with TT set to RING or LOADBALANCE, the following MO must have been configured: 1. A BBP, BRI, GTMU, or CXU with CXUTYPE set to RMU must have been configured. The board location is specified by HCN, HSRN, and HSN in the RRUCHAIN MO. 2. For an RRUCHAIN MO with TT set to a value other than CHAIN, a BBP, BRI, GTMU, or CXU with CXUTYPE set to RMU must have been configured. The board location is specified by TCN, TSRN, and TSN in the RRUCHAIN MO.
Related ParametersTable 1 describes the parameters related to this MO. Table 1 Related parametersParameter | Description |
|---|
| Cabinet No. | Indicates the cabinet number of the GSM main control and transmission board. | | Subrack No. | Indicates the subrack number of the GSM main control and transmission board. | | Slot No. | Indicates the slot number of the GSM main control and transmission board. | | Board Type | Indicates the type of the board. | | Administrative State | Indicates the administrative state of the board. The administrative state of the board can be blocked, unblocked, or shutting down. This parameter is valid only for baseband processing boards and RF modules, and the value of this parameter is NULL for all other types of boards. | | Duration of the shutting down state | Indicates the scheduled duration before a board is blocked. | | Block Type | Indicates the block type of the board. IMMEDIATE (Immediate) means that the board is blocked and services carried on the board are interrupted immediately after the command is executed. SHUTDOWN (Shutdown) means that the board is blocked when no service is carried on the board. DELAY (Delay) means that the board is blocked and services carried by the board are interrupted after a scheduled duration. | | Board Specification | Indicates the type of a board. If this parameter is not specified, the base station and CME check board configurations based on the maximum specifications of a configured board. If this parameter is specified, the base station and CME check board configurations based on the specifications of the specified board so that the CME can identify incorrect configurations before delivering configurations to the base station. This parameter must be specified based on the actual hardware type of the board. For example, if the hardware type of a board is UMPTa, this parameter can be set to UMPTa or UMPTa/b. If the hardware type of a board is UMPTb, this parameter can be set to UMPTb or UMPTa/b. If the configured type of a board is WMPT or LMPT or this parameter is not specified, the value of this parameter is NULL. The values are case insensitive. | | Alarm Status(from RU) | Indicates the alarm status of the board hardware, which can be set to Normal, Warning, Minor, Major, or Critical. | | Operational State(from RU) | Indicates the operational state of the board, which can be set to Enabled or Disabled. Enabled indicates that services can be carried on the board. Disabled indicates that no service can be carried on the board. | | Availability Status(from RU) | Indicates the physical status of a board, which can be Uninstalled, Starting up, Normal, Inconsistent, Unconfigured, Power off, Fault, Communication lost, In test, or the combination of multiple states. For example, if a board is not configured and fails to communicate with the main control and transmission board, the availability status of the board is "Unconfigured, Communication lost." If a board is under management of the peer end, the availability status of the board may be Starting up, Communication lost, or Fault. | | Electronic Label(from RU) | Indicates the electronic label, which is a text file with a maximum of 2 KB used to record the manufacturing information about equipment such as the board, sub-board, and optical module. "BoardType" indicates the type of the board. "BarCode" indicates the bar code of the board and is the same as the code labeled on the board. "Item" indicates the BOM code. "Description" indicates the board description in English. "Manufactured" indicates the manufacturing date of the board. "VendorName" indicates the name of the vendor providing the board. "IssueNumber" indicates the board hardware version. "CLEICode" indicates the common language equipment indicator (CLEI) code of the board. "BOM" indicates the fine-grained item code of the board. | | Type(from RU) | Indicates the type of the board or the cabinet. | | Serial Number(from RU) | Indicates the bar code of the board or the cabinet. | | Description(from RU) | Indicates the description about the services and functions provided by the board or the cabinet. | | Date of Manufacture(from RU) | Indicates the manufacturing date of the board or the cabinet. | | Vendor(from RU) | Indicates the manufacturer of the board or the cabinet. | | Issue Number(from RU) | Indicates the issue number of the board. | | Config Type(from RU) | Indicates the type of a board. | | Board Temperature(from RU) | Indicates the temperature of a board. | | HPA Temperature(from RU) | Indicates the temperature of the power amplifier. A power amplifier is a component on an RF module. If there is no power amplifier on an RF module, this value is null. | | DEVTYPE(from RU) | Indicates the type of the device. | | Software Version(from RU) | Indicates the software version of the board. | | Hardware Version(from RU) | Indicates the hardware version of the board. | | BootROM Version(from RU) | Indicates the BootROM version of the board. | | WorkMode(from RU) | Indicates the working mode of the board. Value SINGLEOM indicates that the GTMU works as the main control board and provides the main control, transmission, and RF port functions. Value EVOLUTION indicates that the GTMU works as the evolved board and provides the transmission and RF port functions. NORMAL indicates that the main control and transmission board works in normal mode. TDS-EVOLUTION indicates that the main control and transmission board works in TDS evolution mode. NULL is displayed for boards other than GTMU or when the working mode cannot be queried. | Related CountersTable 2 describes the counters related to this MO. Thanks!
|
