This describes how to add a GFGUG in the GMPS/GEPS and configure its attributes. The GFGUG implements the IP transmission on the Gb interface for the BSC.
Scenario | BSC initial configuration and BSC capacity expansion |
Mandatory/Optional | Optional. The GFGUG is configured when the Gb over IP mode is adopted. |
When the GFGUG is used to implement the Gb over IP mode, the device IP address and the port IP address must be configured. The device IP address and the port IP address can implement end-to-end communication separately.
You can choose the port IP address or device IP address for communication on the Software Parameter tab page of BSC Attributes.
When the BSC is configured with two GFGUGs, you can set Net Mode to Inter-Board Active/Standby or Inter-Board load sharing to improve networking reliability. When the BSC is configured with only one GFGUG (Independent mode), you can configure routes to guarantee networking reliability.
In active/standby mode, the IP addresses of related ports must be configured on the same network segment. In load sharing mode, if the BSC performs communication through device IP addresses, then the two boards for load sharing must use the same device IP address. Regardless of whether device IP addresses or port IP addresses are used for communication, port IP addresses must be on different network segments.
Besides the configuration of the networking mode, you can configure BFD link detection and ARP link detection to improve system reliability. You can either ARP link detection or BFD link detection on one port. ARP link detection is available when NEs at one end of the ARP link support the ARP link detection. BFD link detection, however, is available only when NEs at both ends of the BFD link support the BFD link detection.
The following procedure takes how to configure a GFGUG in the GMPS as an example.
Parameter |
Example |
Source |
|
---|---|---|---|
Subrack No. |
0 |
BSC internal planning |
|
Slot No. |
18 |
BSC internal planning |
|
FuncType |
Gb interface board |
BSC internal planning |
|
Board Type |
GFGUG |
BSC internal planning |
|
Net Mode |
Inter-Board Active/Standby |
BSC internal planning |
|
Port Type |
FE |
BSC internal planning |
|
Load Key |
Server |
BSC internal planning |
|
Device IP address |
IP Address |
172.16.125.4 |
Negotiation with the peer end |
Subnet Mask |
255.255.255.0 |
Negotiation with the peer end |
|
Port IP address |
Port No. |
0 |
Negotiation with the peer end |
IP Address Index |
0 |
Negotiation with the peer end |
|
Ip Address |
172.16.5.4 |
Negotiation with the peer end |
|
Standby Ip Address |
172.16.5.44 |
Negotiation with the peer end |
|
Subnet Mask |
255.255.255.0 |
Negotiation with the peer end |
|
BSC route |
Destination IP Address |
172.16.124.25 |
Negotiation with the peer end |
Subnet Mask |
255.255.255.0 |
Negotiation with the peer end |
|
Gateway IP Address |
172.16.5.1 |
Negotiation with the peer end |
|
BFD Detect |
Port No. |
0 |
BSC internal planning |
IP Address Index |
0 |
Negotiation with the peer end |
|
Peer IP |
172.16.5.6 |
Negotiation with the peer end |
|
ARP link detection |
Port No. |
0 |
BSC internal planning |
IP Address Index |
0 |
Negotiation with the peer end |
|
Peer IP Address |
172.16.5.8 |
Negotiation with the peer end |