This describes how to add a GEIUB or GOIUB in the GMPS or GEPS and configure its attributes. The GEIUB and GOIUB are responsible for the E1/T1 transmission and STM-1 transmission on the Abis interface respectively.
Scenario | BSC initial configuration and BSC capacity expansion |
Mandatory/Optional | Mandatory |
The subrack has idle slots to hold the GEIUB and GOIUB.
Parameter |
Example |
Source |
---|---|---|
Board Type |
GEIUB |
BSC internal planning |
Work Mode |
E1 |
BSC internal planning |
Active/Standby Mode |
Selected |
BSC internal planning |
Load Key |
Server |
BSC internal planning |
Parameter |
Example |
Source |
---|---|---|
Board Type |
GOIUB |
BSC internal planning |
Work Mode |
E1 |
BSC internal planning |
Active/Standby Mode |
Selected |
BSC internal planning |
Load Key |
Server |
BSC internal planning |
Tributary Numbering |
HuaWei mode |
Negotiation with the peer |
TX J0 Byte |
MGW SDH DEFAULT (character string) |
Negotiation with the peer |
Expect RX J0 Byte |
MGW SDH DEFAULT (character string) |
Negotiation with the peer |
TX J1 Byte |
MGW SDH DEFAULT (character string) |
Negotiation with the peer |
Expect RX J1 Byte |
MGW SDH DEFAULT (character string) |
Negotiation with the peer |
TX J2 Byte |
MGW SDH DEFAULT (character string) |
Negotiation with the peer |
Expect RX J2 Byte |
MGW SDH DEFAULT (character string) |
Negotiation with the peer |
TX Frame Format |
CRC4_MULTIFRAME |
Negotiation with the peer |
RX Frame Format |
CRC4_MULTIFRAME |
Negotiation with the peer |
When the parameter Optical Interface Standard is set to SONET, you must configure the following parameters: High Order Path 1 TX J1 Byte, High Order Path 1 Expect RX J1 Byte, High Order Path 2 TX J1 Byte, High Order Path 2 Expect RX J1 Byte, High Order Path 3 TX J1 Byte, and High Order Path 3 Expect RX J1 Byte.
The procedures for configuring the GEIUB and GOIUB are the same. The following procedure takes how to add a pair of active/standby GEIUBs in the GMPS as an example.