BSC6900 Communication Matrix (V900R019C10 - 04) (XLS) - EN

BSC6900 V900R019C10
Communication Matrix
Issue 04
Date 2018/01/15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2018. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of
Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the commercial contract made between Huawei and the
customer. All or partial products, services and features described in this document may not be within the purchased scope or
the usage scope. Unless otherwise agreed by 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.
Huawei Technologies Co., Ltd.

Huawei Industrial Base
Bantian, Longgang
Address:
Shenzhen 518129
People's Republic of China
Web site: http://www.huawei.com
Email: support@huawei.com
Purpose
This document describes BSC6900 product communication matrix.
Intended Audience
This document is intended for:
● Network planners
● System engineers
● Field engineers
● Shift operators
● Network operators
● Administration engineers
Structure
Source Device Name of the source device
Source IP IP address of the source device
Source Port Number of the source port or source port number range
Destination Name of the destination device
Destination IP IP address of the destination device
Address
Destination Port Number of the destination port or destination port number range, indicating the port providing listening servic
Protocol Protocols involved. Protocols used at the transport layer, such as TCP, UDP, and SCTP
Port Description Details of the services provided on the port.
Is Listening Port Whether the listening port can be changed on the Web UI or the CLI
Configurable
Authentication Authentication mode on the port, for example, using a user name and password
Mode
Encryption Mode Encryption mode used on the port
Plane Plane of the port, such as the OM plane, the control plane, the user plane, or shared by the three planes
Version Product version corresponding to the listening port
Special Scenario Special scenario where the port is applied to
In the section of "OMU<->FTP server/client", the ports used for communication between OMU and FTP serv
In the section of "OMU<->U2000", the ports used for communication between OMU and U2000 server are d
In the section of "OMU<->eCoordinator", the ports used for communication between OMU and eCoordinator
In the section of "OMU<->OMU", the ports used for communication between OMU and OMU are described.
In the section of "OMU<->Maintenance and Test Tool", the ports used for communication between OMU and
In the section of "Ports shielded externally in the current version", the ports shielded externally in the current
In the section of "DHCP Server/Relay", the ports used for DHCP relay function between controller and other
In the section of "BSC/RNC<->Base Station", the ports used for communication between controller and Base
In the section of "BSC/RNC<->CN", the ports used for communication between controller and SGSN/MSC/M
In the section of "BSC/RNC<->BSC/RNC", the ports used for communication between controller and control
Others In the section of "BSC/RNC<->SMLC/SAS", the ports used for communication between controller and SML
Center)/SAS(Standalone A-GPS SMLC)
In the section of "BSC/RNC<->CBC are described.
Server", the ports used for communication between controller and CBC
In the section of "BSC/RNC<->AC", the ports used for communication between controller and AC(Access Co
In the section of "BSC/RNC<->Transmission Equipment", the ports used for communication between control
In the section of "BSC/RNC<->eCoordinator", the ports used for the ECO6910 performs network optimizatio
In the section of "OMU<->Certificate server of the operator", the ports used for communication between OM
Section "SAU<->U2000" describes the port used for the communication between the SAU and U2000 server.
Section "SSH client <-> SAU" describes the port used for the communication between the SSH client and SA
Section "U2000 Trace Server <-> SAU" describes the port used for the communication between the U2000 T
Section "Shielded port on the current SAU" describes the port shielded from external services in the current v
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd. 3
Section "SAU <-> MySQL database" describes the port between the current SAU and MySQL database.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates m
Issue Date
04 2018-1-15
03 2017-10-10
02 2017-06-29
01 2017-03-08
Draft A 2016-12-31

ument describes BSC6900 product communication matrix.
ument is intended for:

k planners
engineers
ngineers
perators
k operators
stration engineers
the source device

s of the source device
of the source port or source port number range
the destination device
s of the destination device
of the destination port or destination port number range, indicating the port providing listening services
involved. Protocols used at the transport layer, such as TCP, UDP, and SCTP
f the services provided on the port.
the listening port can be changed on the Web UI or the CLI
cation mode on the port, for example, using a user name and password
on mode used on the port

he port, such as the OM plane, the control plane, the user plane, or shared by the three planes
ersion corresponding to the listening port
cenario where the port is applied to
tion of "OMU<->FTP server/client", the ports used for communication between OMU and FTP server/client are described.
tion of "OMU<->U2000", the ports used for communication between OMU and U2000 server are described.
tion of "OMU<->eCoordinator", the ports used for communication between OMU and eCoordinator are described.
tion of "OMU<->OMU", the ports used for communication between OMU and OMU are described.
tion of "OMU<->Maintenance and Test Tool", the ports used for communication between OMU and the maintenance and test tool are
tion of "Ports shielded externally in the current version", the ports shielded externally in the current version are described.
tion of "DHCP Server/Relay", the ports used for DHCP relay function between controller and other NE are described.
tion of "BSC/RNC<->Base Station", the ports used for communication between controller and Base Station are described.
tion of "BSC/RNC<->CN", the ports used for communication between controller and SGSN/MSC/MGW are described.
tion of "BSC/RNC<->BSC/RNC", the ports used for communication between controller and controller are described.
tion of "BSC/RNC<->SMLC/SAS", the ports used for communication between controller and SMLC(Serving Mobile Location
AS(Standalone A-GPS SMLC)
tion of "BSC/RNC<->CBC are described.
Server", the ports used for communication between controller and CBC are described.
tion of "BSC/RNC<->AC", the ports used for communication between controller and AC(Access Controller) are described.
tion of "BSC/RNC<->Transmission Equipment", the ports used for communication between controller and the transmission equipment are
tion of "BSC/RNC<->eCoordinator", the ports used for the ECO6910 performs network optimization management on the BSC/RNC.
tion of "OMU<->Certificate server of the operator", the ports used for communication between OMU and CA/CRL certificate server of the
SAU<->U2000" describes the port used for the communication between the SAU and U2000 server.
SSH client <-> SAU" describes the port used for the communication between the SSH client and SAU.
U2000 Trace Server <-> SAU" describes the port used for the communication between the U2000 Trace Server and SAU.
Shielded port on the current SAU" describes the port shielded from external services in the current version.
SAU <-> MySQL database" describes the port between the current SAU and MySQL database.
between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Description
Compared with issue 03 (2017-10-10) of V900R019C10, this issue includes the following changes:
Added:
·Added the port used by the OMU Installation Tool. For details, see OMU > Maintenance Tool.
·Supplemented the debugging Ethernet port between the active and standby OMUs. For details, see OMU >
OMU.
Modifiled:
Modified the encryption mode from SSL to SSL/TLS for ports. Specifically, the SSL-capable ports also support
TLS.
Deleted: None.
Added: None.
Modifiled: Modified the Port range and Description for the Device of SGSN and RNC, which are listed in the
section BSC/RNC<->CN.
Deleted: None.
Added: Added ports of SAU (FTP client) port and OMU(TFTP client) port.
Modifiled: Modified the Port range of SNTP server to be same with MML ADD SNTPSRVINFO.
Deleted: Deleted the ports of SAU <-> MySQL Database and Shielded port on the current SAU.
Compared with issue Draft A (2016-12-31) of V900R019C10, this issue does not include any changes.
Added: Descriptions about the SAU communication matrix
Modifiled: None
Deleted: None

Source Device Source IP Address Source Port
OMU<->FTP server/client Debugging IP address

of the OMUof the FTP
IP address
FTP client External
client fixed IP 1024~65535
Debugging IP address
address of the OMU
of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 21
address of the OMU
External virtual IP
OMU address
Debuggingof the OMU
IP address 1024~65535
Determined
IP address by the FTP
FTP server External
server fixed IP server
address of the OMU
External virtual IP
OMU address of the OMU 20
IP address of the FTP
FTP client client
Debugging IP address 1024~65535
of the OMU
FTP client External
address of the OMU
External virtual IP
OMU address of the
Debugging OMU
IP address 25001~30000
Determined
of the OMU
IP address of the FTP by the FTP
FTP server External
server fixed IP server
address of the OMU
External virtual IP
OMU address of the OMU 20001~25000
IP address of the TFTP
TFTP client client 1024~65535
OMU of the OMU 69
TFTP client client 1024~65535
Debugging IP address of
OMU the OMU 51000~51050
OMU<->U2000
IP address of the
U2000 server U2000 server 123~65534
External virtual IP
IP address of the
U2000 server U2000 server 1024~65535
External virtual IP 6000,
OMU address of the OMU 8000 (SSL)
IP address of the
U2000 server U2000 server 1024~65535
Huawei Proprietary and Confidential 8

Copyright © Huawei Technologies Co., Ltd.
IP address of the
U2000 server U2000 server 1024~65535
IP address of the
U2000 server U2000 server 1024~65535
IP address of the
U2000 server U2000 server 1024~65535
External virtual IP
IP address of the
U2000 server U2000 server 514
IP address of the
U2000 server U2000 server 1024~65535
External virtual IP
Active OMU address of the OMU 4443 (SSL)
OMU<->OMU External fixed IP

address of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 20
address of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 20001~25000
address of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 1024~65535
address of the OMU
External virtual IP
External fixed IP
Master OMU of the OMU 67
Standby OMU External fixed IP
of the OMU 68
address of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 20001~25000
address of the OMU
External virtual IP
OMU<->Maintenance and Test Tool

of the OMUof the LMT
IP address
LMT client External
address of the OMU
OMU address of theaddress
Debugging IP OMU 443 (SSL)
of the OMU
IP address of the
Remote desktop (local computer) External fixed IP
remote desktop 1024~65535
address of the OMU
External virtual IP
OMU address of the
Debugging OMU
IP address 3389
of the OMU
IP address of the SSH
Secure Shell (SSH) client (local computer) External
address of the OMU
External virtual IP
IP address of the
NetEco server NetEco server 1024~65535
IP address of the
NetEco server NetEco server 1024~65535
OMU IP address
address of of
thethe local
OMU 8006 (SSL)
computer with the
remote upgrade tool
Remote upgrade tool External
installed fixed IP 6000,
1024~65535
address of the OMU 6088,
External virtual IP 8000(SSL),
IP address of the alarm
Alarm forwarding system forwarding system 1024~65535
IP address of the
Vendor Network Probe
VNP (VNP) client 1024~65535
External virtual IP
OMU External
BSC localfixed IP
IP address 8200 (SSL)
address of the OMU
External virtual IP
IP address of the
OfficeScan server OfficeScan server 1024~65535
IP address of the local
PC accommodating the
Driver upgrade tool driver upgrade tool 1024~65535
USB disk tool USB disk tool 1024~65535

OMU Installation Tool OMU Installation Tool 1024~65535

OMU IP address
address of of
thethe
OMUlocal 8000 (SSL)
board replacement
Board replacement tool tool 1024~65535
Ports shielded externally in the current
version
Client IP address of the client 1024~65535
DHCP Server/Relay
BTS
NodeB 0.0.0.0 68

IP address of the BTS
BSC IP
IP address
address of
of the
the BSC
RNC NodeB
IP address of the RNC 67
BTS IP address of the
NodeB device with the DHCP
Device with the DHCP relay function enabled relay function enabled 67
BSC IP address of the BSC
RNC IP address of the RNC 67
IP address of the
U2000 server U2000 server 67
BSC/RNC<->Base Station
IP address of the
NodeB NodeB 1024~65535
eGBTS eGBTS IP address 1024-65535
BSC BSC IP address 1024-65535
RNC IP address of the RNC 4096~12287,

1024~65535
37253,
excluding
BTS IP address of the BTS 4500
BSC IP address of the BSC 5000~64967

IP address of the 1024~17919,
RNC IP address of the RNC 5000~64967
BTS IP address of the BTS 12288~28673

BTS IP address of the BTS 65043
BSC IP address of the BSC 65043

RNC (client) IP address of the RNC 65041
NodeB (server) NodeB 7, 65040
NodeB (client) NodeB 65041
RNC (server) IP address of the RNC 7, 65040
NodeB NodeB 65042
RNC IP
IP address
address of
of the
the RNC 64968~64983
eGBTS
eGBTS IP address of the
RNC IP
IP address
address of
of the
the RNC 64984~64999
eGBTS
RNC IP
IP address
address of
of the
the RNC 5201~6225
eGBTS
NodeB NodeB 1~65535
BSC IP address of the BSC 862,
RNC IP
IP address
address of
of the
the RNC 1024~65535
eGBTS Determined
eGBTS IP address of the by the peer
NodeB NodeB device
BSC/RNC<->CN
MSC IP address of the MSC
SGSN IP address of the SGSN 1024~65535
Determined
SGSN IP address of the SGSN by the SGSN
SGSN IP address of the SGSN 1214~2001,

0~65535
2005~3783,
3786~4783,

Determined
MGW IP address of the MGW by the MGW
Determined
MGW IP address of the MGW by the MGW
SGSN IP address of the SGSN Determined
MSC IP address of the MSC by the peer
MGW IP address of the MGW device
SGSN IP address of the SGSN
MGW IP address of the MGW 1~65535
BSC/RNC<->BSC/RNC

RNC IP address of the RNC 65061, 65062

BSC/RNC<->SMLC/SAS IP address of the SAS

IP address of the
SAS(Standalone A-GPS SMLC) serving mobile
SMLC(Serving Mobile Location Center) location center (SMLC) 1024~65535
BSC/RNC<->CBC Server
IP address of the RAN
RAN CBC CBC 3452

IP address of the GSM
GSM CBC CBC 0~65535
BSC/RNC<->AC
AC(Access Controller) IP address of the AC 0~65535
BSC/RNC<->Transmission Equipment IP address of the

bearer network device Determined
Bearer network device IP address of the peer by the peer
Peer device device device
RNC IP
IP address
address of
of the
the RNC 49152~65535
RNC IP
IP address
address of
of the
the RNC -
bearer network device
Bearer network device IP address of the peer
Peer device device -
RNC IP
IP address
address of
of the
the RNC 64968~64983

RNC IP
IP address
address of
of the
the RNC 64984~64999
RNC IP
IP address
address of
of the
the RNC 5201~6225
bearer network device
Bearer network device IP address of the peer
Peer device device 1~65535
RNC IP
IP address
address of
of the
the RNC 1024~65535
BSC/RNC<->eCoordinator

IP address of the
ECO6910 ECO6910 1024~65535

IP address of the
ECO6910 ECO6910
Debugging IP address 1024~65535
of the OMU
OMU<->Certificate server of the operator External fixed IP
address of the OMU
External virtual IP Determined
OMU address of the OMU by the
1024~65535
Debugging
IP address of IPthe
address operator's CA
of the OMUCA
operator's certificate
CA certificate server of the operator External fixed
certificate IP
server server
address of the OMU
External virtual IP Determined
OMU address of the OMU by the
1024~65535
IP address of the operator's CRL
operator's CRL certificate
CRL certificate server of the operator certificate server server
SAU <-> U2000

IP address of the
U2000 (FTP server) U2000 server 1024–65535
SAU (FTP client) IP address of the SAU 25000–30000
SSH client <-> SAU

IP address of the SSH
SSH client client 1024–65535
U2000 Trace Server <-> SAU

IP address of the
U2000 Trace Server U2000 Trace Server 1024–65535
IP address of the
U2000 Trace Server U2000 Trace Server 1024–65535

Destination
Destination Destination IP
Port Protocol
Device Address
Debugging IP address (Listening)
of the OMU
External fixed IP
address of the OMU
External virtual IP
OMU address of the OMU 21 TCP
FTP client client
Debugging IP address 1024~65535 TCP
IP address Determined by
FTP server External
server fixed IP the FTP server TCP
address of the OMU
External virtual IP
OMU address
Debuggingof the OMU
IP address 1024~65535 TCP
IP address
FTP client External
client fixed IP 1024~65535 TCP
address of the OMU
of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 20 TCP
address of the OMU
External virtual IP
OMU address of the
Debugging OMU
IP address 25001~30000 TCP
of the OMU
FTP client External
address of the OMU
External virtual IP
OMU address of the OMU 20001~25000 TCP
IP address of the FTP Determined by
FTP server server the FTP server TCP
OMU of the OMU 69 UDP
TFTP client client 1024~65535 UDP
Debugging IP address of
OMU the OMU 51000~51050 UDP
TFTP client client 1024~65535 UDP
External virtual IP
OMU address of the OMU 123 UDP
IP address of the
U2000 server U2000 server 123~65534 UDP
OMU address of the OMU 8000 (SSL) TCP
IP address of the
U2000 server U2000 server 1024~65535 TCP

IP address of the
IP address of the
IP address of the
IP address of the
IP address of the
U2000 server U2000 server 514 UDP
External virtual IP
OMU address of the OMU 1024~65535 UDP
External virtual IP
Active OMU address of the OMU 4443 (SSL) TCP
IP address of the
External fixed IP
address of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 20001~25000 TCP
address of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 20 TCP
address of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 21 TCP
address of the OMU
External virtual IP
External fixed IP
Standby Debugging IP address
OMU of the OMU 68 UDP
Master OMU External fixed IP
of the OMU 67 UDP
address of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 25001~30000 TCP
address of the OMU
External virtual IP

of the OMU
External fixed IP
address of the OMU
OMU address of the
Debugging OMU
IP address 443 (SSL) TCP
of the OMUof the LMT
IP address
LMT client External
address of the OMU
External virtual IP
Remote
desktop Debugging IP address
(local of the OMU
IP address of the
computer) External fixed IP
remote desktop 1024~65535 TCP
address of the OMU
External virtual IP
SSH client
(local IP address of the SSH
computer) client 1024~65535 TCP
NetEco IP address of the
server NetEco server 1024~65535 TCP
NetEco IP address of the
server External fixed IP
NetEco server 6000,
1024~65535 TCP
External virtual IP 8000 (SSL),
OMU IP address
address of of
thethe local
OMU 8088 (SSL) TCP
computer with the
Remote remote upgrade tool
upgrade tool installed 1024~65535 TCP
Alarm
forwarding IP address of the alarm
system forwarding system 1024~65535 TCP
External virtual IP
OMU BSC local IP address 8200 (SSL) TCP
IP address of the VNP
VNP client 1024~65535 TCP
OfficeScan IP address of the
server External fixed
OfficeScan IP
server 1024~65535 TCP
address of the OMU
External virtual IP
Driver PC accommodating the
upgrade tool driver upgrade tool 1024~65535 TCP
USB disk tool USB disk tool 1024~65535 TCP

OMU IP address of the local
Installation PC accommodating the
Tool USB disk tool 1024~65535 TCP
Board IP address of the local
replacement PC accommodating the
tool board replacement
Debugging IP tool
address 1024~65535 TCP
of the OMU
External fixed IP
Debugging IP
address of theaddress
OMU
of the OMU
External virtual IP
OMU External
address fixed
of the IP
OMU 111 UDP
address of the OMU
of the OMU
External virtual IP
OMU External
address fixed
of the IP
OMU 111 TCP
address of the OMU
of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 135 TCP
address of the OMU
of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 139 TCP
address of the OMU
of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 445 TCP
address of the OMU
of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 515 TCP
address of the OMU
of the OMU
External virtual IP
OMU External
address fixed
of the IP
OMU 1025 TCP
address of the OMU
of the OMU
External virtual IP
OMU External
address fixed
of the IP
OMU 1723 TCP
address of the OMU
of the OMU
External virtual IP
OMU External
address fixed
of the IP
OMU 137 UDP
address of the OMU
of the OMU
External virtual IP
OMU External
address fixed
of the IP
OMU 138 UDP
address of the OMU
of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 445 UDP
address of the OMU
of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 500 UDP
address of the OMU
of the OMU
External virtual IP
OMU External fixed
address of the IP
OMU 1701 UDP
address of the OMU
External virtual IP

RNC IP address of the RNC 67 UDP

BTS
NodeB 0.0.0.0
IP address of the BTS 68 UDP
Device
BSC with IP
IP address
address of
of the
the BSC
the
RNC DHCP NodeB
IP address of the RNC 67 UDP
relay IP address of the
function device with the DHCP
enabled relay function enabled 67 UDP
IP address of the
U2000 server U2000 server 67 UDP
RNC IP address of the RNC 1024~65535 SCTP
BSC BSC IP address 1024-65535 SCTP
eGBTS eGBTS IP address 1024-65535 SCTP

IP address of the
NodeB NodeB 1024~65535 SCTP
BSC IP address of the BSC 5000~64967 UDP

4096~12287,
37253,
BTS IP address of the BTS excluding 4500 UDP
RNC IP address of the RNC 5000~64967 UDP

IP address of the 1024~17919,
NodeB NodeB 30000~46895 UDP
BTS IP address of the BTS 12288~28673 UDP

NodeB NodeB 65010 UDP
BSC IP address of the BSC 65043 UDP
BTS IP address of the BTS 65043 UDP

NodeB NodeB 7, 65040 UDP
RNC IP address of the RNC 7, 65040 UDP
NodeB IP address
NodeB of the 6002 UDP
eGBTS
RNC IP
IP address
address of
of the
the RNC 64968~64983 UDP
eGBTS
RNC IP
IP address
address of
of the
the RNC 64984~64999 UDP
eGBTS
NodeB NodeB 1~65535 TCP
RNC IP
IP address
address of
of the
the RNC 5201~6225 TCP
eGBTS
eGBTS IP address of the Determined by
NodeB NodeB the peer device TCP
RNC IP address of the RNC 1024~65535 TCP

SGSN IP address of the SGSN 1024~65535 SCTP
SGSN IP address of the SGSN 1214~2001,

0~65535 UDP
2005~3783,
3786~4783,
SGSN IP address of the SGSN 0~65535 UDP

Determined by
MGW IP address of the MGW the MGW UDP
RNC IP address of the RNC 2002, 2004 UDP
MGW IP address of the MGW 2002, 2004 UDP

MSC IP address of the MSC Determined by
MGW IP address of the MGW the peer device UDP
SGSN
MSC IP address of the BSC
MGW IP address of the RNC 64968~64983 UDP
MGW IP address of the MGW the peer device UDP
MGW IP address of the MGW 1~65535 TCP
MGW IP address of the MGW the peer device TCP
RNC IP address of the RNC

BSC IP address of the BSC 1024~65535 SCTP



RNC IP
IP address
address of
of the
the SAS
RNC 1024~65535 SCTP
IP address of the
SAS serving mobile location
SMLC center (SMLC) 1024~65535 SCTP
RNC IP address of the RNC 3452 TCP

IP address of the RAN
RAN CBC CBC 3452 TCP
BSC IP address of the BSC 0~65535 TCP

IP address of the GSM
GSM CBC CBC 0~65535 TCP
AC IP address of the AC 0~65535 UDP

Bearer
RNC IP
IP address
address of
of the
the RNC 3784 UDP
network bearer network device
device IP address of the peer
Peer device device 3784 UDP
Bearer
RNC IP
IP address
address of
of the
the RNC 4784 UDP
Bearer
Peer device IP address of the
device 4784 UDP
Peer device device - ICMP
Bearer
RNC IP
IP address
address of
of the
the RNC - ICMP
Bearer
Peer device IP address of the
device 49152~65535 UDP
device IP address of the peer Determined by
Peer device device the peer device UDP

Bearer IP address of the
Peer device device the peer device UDP
Bearer
RNC IP
IP address
address of
of the
the RNC 64984~64999 UDP
Peer device device 1~65535 TCP
Bearer
RNC IP
IP address
address of
of the
the RNC 5201~6225 TCP
Peer device device the peer device TCP
IP address of the
ECO6910 ECO6910 1024~65535 SCTP

IP address of the
ECO6910 ECO6910 1024~65535 SCTP
BSC IP address of the BSC 1024~65535 SCTP
Determined by
CA certificateDebugging
IP address of IPthe
address the operator's
server of the of the OMU
operator's CA CA certificate
operator External fixed
certificate IP
server server TCP
address of the OMU
External virtual IP
CRL
OMU address of the OMU Determined
1024~65535by TCP
certificate Debugging
IP address of IPthe
address the operator's
server of the of the OMUCRL
operator's CRL certificate
operator External fixed
certificate IP
server server TCP
address of the OMU
External virtual IP
30070,
IP address of the SAU 30170
SAU server server (SSL) TCP
U2000 IP address of the U2000 21 TCP
IP address of the SAU

SAU server server 22 TCP

30090,
6006,

Is
Listenin Authent
Encryption
Port Description g Port ication
Mode
Configu Mode
rable
Functioning as the FTP server, the OMU board
responds to requests from the FTP client. Port 21 is User
used for FTP transmission control. The transmission name/p
Functioning
modes of theasFTP theand
FTPFTPSserver, arethebothOMU board
supported. YES assword SSL/TLS
responds to requests from the FTP client. Port 21 is User
Functioning
used for FTPas the FTP client,
transmission the OMU
control. board
The transmission name/p
performs FTP transmission control.
modes of the FTP and FTPS are both supported. The destination YES assword SSL/TLS
port used
Functioning forasFTP connection control is determined User
Functioning
by theboard as the
FTP server.
FTP
the The server
FTP transmission
client, thein active
OMU mode, the
board
modes of the name/p
OMU
performs actively responds
FTP transmission to requests
control. The source from FTP
port
FTP and
clients, FTPS
performsare both
FTP supported.
data transmission, and YES assword SSL/TLS
used for FTP as
Functioning connection
the FTP servercontrolinisactive
determined
mode, by User
uploads
the FTP and downloads
server. The software
transmission and logs.
modes of Thethe
the FTP name/p
OMU board actively
transmission modes responds
the FTPto
of server requests
and from
FTPS mode,
are FTP
both
Functioning
and FTPS
clients, areas
performs the
both FTP
supported.
FTP data in passive
transmission, and the YES assword SSL/TLS
supported.
OMU board passively responds to requests User
uploads
Port 20 is and
thedownloads
default data software
port of and
the logs.
FTPand The FTP
from
server and name/p
clients, performs
transmission modesFTP data
of aserver
the transmission,
FTPinand FTPS mode,
are both
Functioning
cannot be
uploads and as the FTP
shielded
downloadsby firewall.
software passive
and logs. The the YES assword SSL/TLS
supported.
OMU board passively responds to requests from User
transmission
Port 20 is the modes
default of the port
data FTP and
of theFTPS are
FTPand bothFTP
server and name/p
clients,
supported.performs FTP data transmission,
cannot be
uploads andshielded
downloadsby a software
firewall. and logs. The YES assword SSL/TLS
In the view of
Functioning as security,
the FTP you are advised
client, to enable User
transmission modes
the FTP transmission of the FTPthe
detection andOMUFTPS
function
board
onarethe
both name/p
performs
supported. FTP data transmission using these ports
firewall
and for FTP
uploads anddata transmission.
downloads software and YES assword SSL/TLS
In the view of
Functioning as security,
the FTP you are
client, advised
the OMU to logs.
boardenable The User
transmission modes
the FTP transmission of the FTP and
detection function FTPS are
on the both name/p
performs
supported. FTP data transmission using these ports
firewall
and for FTP
uploads anddata transmission.
downloads software and logs. The YES assword SSL/TLS
In the view of security, you are advised to enable User
transmission modes of the FTP and
the FTP transmission detection function on the FTPS are both name/p
supported.
firewall for FTP data transmission. YES assword SSL/TLS
In the view of security, you are advised to enable User
the FTP transmission detection function on the name/p
firewall for FTP data transmission. YES assword SSL/TLS
Functioning as the TFTP server, the OMU board
responds to requests from the TFTP client. Port 69 is
used for TFTP transmission control. NO N/A N/A
Functioning as the TFTP server, the OMU board
responds to requests from the TFTP client. Port 69 is
used for TFTP transmission control. NO N/A N/A
Functioning as the TFTP server, the OMU board uses these
ports to transmit TFTP data, such as downloading OS files
and product software. NO N/A N/A
Functioning as the TFTP server, the OMU board uses these
ports to transmit TFTP data, such as downloading OS files
and product software. NO N/A N/A
The destination port is used for communication
between the OMU and the U2000 server functioning
as an SNTP server to synchronize the OMU time with
The source time.
the U2000 port is used
This port forcan
communication
be configuredbetween
as an
the OMU and
SSL-encrypted the U2000
port. server functioning as an YES N/A SSL/TLS
The destination ports are used for
SNTP server to synchronize the OMU time with the communication
between
U2000 time. the This
OMUport andcan the be U2000 server as
configured to maintain
an SSL-
the OMU.
encrypted The
port.MML command transfers by accessing YES N/A SSL/TLS
The source ports are used for communication
the port. User
between
Port 6000the OMU
is an and the U2000
unencrypted access server
port,to
and maintain
port name/p
the OMU. The MML command
8000 is an SSL-encrypted access port. transfers by accessing NO assword SSL/TLS
the port. User
The
Port destination ports are used
6000 is an unencrypted for communication
access port, and port name/p
between the OMU and the
8000 is an SSL-encrypted access port. U2000 server to report NO assword SSL/TLS
alarms. User
Port 6001 is an unencrypted access port, and port name/p
8001 is an SSL-encrypted access port. NO assword SSL/TLS

The source ports are used for communication
between the OMU and the U2000 server to report
The destination ports are used for communication
alarms. User
between
Port 6001the is anOMU and the U2000
port,to andmaintain
port name/p
the OMU.
8001source The binary
is an SSL-encrypted message access transfers
port. by NO assword SSL/TLS
The ports
accessing the port. are used for communication User
between
Port 6006the is anOMU and the U2000
port,to andmaintain
port name/p
the OMU. The binary message
8006 is an SSL-encrypted access port. transfers by NO assword SSL/TLS
accessing the port. User
The
between the OMU and
8006 is an SSL-encrypted access port.the U2000 server to NO assword SSL/TLS
synchronize configuration data. User
The
Port source
6099 isports are used foraccess
an unencrypted communication
port, and port name/p
between the OMU and
8099 is an SSL-encrypted access port.the U2000 server to NO assword SSL/TLS
synchronize configuration data. User
The
between the OMU and
8099 is an SSL-encrypted access port.the U2000 server to report NO assword SSL/TLS
performance messages. User
The
Port source
16002 is ports are used for communication
an unencrypted access port, and port name/p
between the OMU
18002 is an SSL-encrypted and the U2000 accessserver
port. to report NO assword SSL/TLS
performance messages. User
The U2000 server functions as the port of the
SyslogCollectorDM service which provides the
Syslog listening function. NO N/A N/A
The U2000 server functions as the port of the
SyslogCollectorDM service which provides the
Syslog listening function. NO N/A N/A
The destination port is used to check the validity of
Functioning as the FTP
certificates between theserver
U2000 in and
activethemode,
OMU and the is
OMU board actively
encrypted using SSL. responds to requests from the NO N/A SSL/TLS
The client
FTP source(the portpeeris used
OMU), to check
performs the FTP
validity
dataof
Functioning asand
certificates between
transmission, thesynchronizes
FTPtheserver
U2000 in data
active
and the
andmode,
OMU the is
files and
OMU board
encryptedthe
between actively
using
activeSSL. and standby OMU boards. the
responds to requests from NO N/A SSL/TLS
FTP client (the
If both the source and peer OMU), performs
destination FTP data
devices are OMU
transmission, and synchronizes
boards, the OMU boards work in active/standby data and files
between
mode. the active and standby OMU boards. User
If both
Port 20the
is thesource
defaultanddata destination
port of the devices are OMU
FTP server and name/p
boards,
cannot the
be OMU
shielded boards
by a work
firewall.in active/standby YES assword N/A
Functioning
mode. as the FTP server, the OMU board User
responds
Port 20 is therequests
to default data from portthe FTP client
of the FTP(the peer
server and name/p
OMU).
If two
cannot Port
OMU
be 21 is
boards
shielded usedare
by for FTP
configured,
a transmission
firewall. the control.
destination YES assword N/A
Functioning
If both as theand
the source FTP destination
server, the devices
OMU board arelocal
OMU User
port is used
responds to for communication
requests from the between
FTP the
client (the peer
boards,
OMU and the OMU boards work in active/standby name/p
OMU).
mode. Portthe 21peer
is usedOMU. forTheFTP destination
transmission ports on
control. YES assword N/A
both OMUs must be enabled.
If both the source and destination devices are OMU User
If both the
boards, thesource
OMU boardsand destination devices are OMU
work in active/standby name/p
boards,
mode. the OMU boards work in active/standby YES assword N/A
Functioning
mode. as the FTP server in passive mode, the
OMU board passively
Port 11775 is a port inside responds the BSCto requests
and is not from the
The
FTP master
client
encrypted. OMU
(the peerserves
OMU), as the DHCP
performs server,
FTP data and NO N/A N/A
Functioning
the standby as
transmission, OMU theserves
and FTP server
synchronizesas the inDHCP
passive
data mode,
client.
and filesThe the
OMU
between board
DHCP port the passively
is used
active for
andresponds
automatically
standby to requests
OMU installing from
boards.and thethe
The
FTP master
client
operating OMU
(the peerserves
OMU), as the DHCP
performs server,
FTP data
In
thethe viewsystem
standby ofOMU for the
security, youstandby
as are
OMU. to enable
the advised
YES N/A N/A
transmission,
the FTP and serves
transmission synchronizes
detection
DHCP
data and
function
client.
onfilesThe
thethe
DHCP port
between theis used
active for
and automatically
standby OMU installing
boards.
firewall
operating forsystem
FTP data fortransmission.
the standby OMU. to enable YES N/A N/A
In the view
If both of security,
the source you
and destination are advised
devices are OMU User
the FTP transmission detection
boards, the OMU boards work in active/standby function on the name/p
firewall
mode. for FTP data transmission. YES assword N/A
If both the source and destination devices are OMU User
boards, the OMU boards work in active/standby name/p
mode. YES assword N/A

The destination port is used for the OMU to set up
an encrypted connection with the LMT client so that
users can maintain a BSC using a browser. User
The
Port source port iswith
80 complies used for the
HTTP, andOMU
portto setcomplies
443 up an name/p
encrypted connection with the LMT client so that
with Hypertext Transfer Protocol Secure (HTTPS). NO assword SSL/TLS
users can maintain a BSC using a browser. User
Port 80 complies with HTTP, and port 443 complies name/p
with Hypertext Transfer Protocol Secure (HTTPS). NO assword SSL/TLS
User
The destination port is used for remote desktop name/p
access in the Windows operating system (OS). NO assword N/A
User
The source port is used for remote desktop access name/p
in the Windows OS. NO assword N/A
The destination port is an SSH-encrypted access User
port used to receive remote access requests from name/p
the SSH client to the OMU. NO assword SSH
The source port is an SSH-encrypted access port User
used to receive remote access requests from the name/p
The
SSH NetEco
client toaccesses
the OMU. port 6000 or 8000 of the OMU NO assword SSH
for MML command authentication. User
The
8000NetEco accesses port access
is an SSL-encrypted 6000 orport. 8000 of the OMU NO assword SSL/TLS
for MML command authentication. User
The
Port destination
alarm
6000 is forwardingports are
an unencrypted systemused isfor
access the OMU
a component
port, and toof the
port name/p
The NetEco
receive
offline
8000 istool data server
sent accesses
from
on the LMT andaccess
an SSL-encrypted the port
remote 6006
is usedport. upgradeor
to forward8006tool of
to
alarm NO assword SSL/TLS
the OMU forabinary
implement
information, remote
alarm message
boxupgrade.
control transmission.
information and User
The
Port source
alarm
6006
6000 is
andports
forwarding
an are
unencrypted
6088 isused
system
an foraccess
the
is
unencrypted a OMU
component
port,to and
receive
access of the
port
port, name/p
alarm
The
data box
NetEco
sent status
server
from between
theLMTaccesses
remote the portOMU
upgrade 6006 and
tool the
orto8006alarmof
offline
8006
and
box. is
port tool
an on
8000
If a connectionthe
SSL-encrypted
and 8088
fromandis is
access
an used to
port. forward
SSL-encrypted
the transmission.
LMT to the alarm box is alarm
access NO assword SSL/TLS
the OMU
implement a
information, for binary
remote
alarm message
boxupgrade.
control information and User
port.6006start
required, is the
an6088 alarm
unencrypted forwarding
access system.
port, and The
port name/p
Port
alarm
If the6000box
U2000 and
status
or another is
between an unencrypted
the
proxy OMU
server and access
acts theas port,
alarm
a proxy
alarm
8006
and portforwarding
is an8000 and system
SSL-encrypted 8088 iscommunicates
access
an port.
SSL-encrypted with the
access NO assword SSL/TLS
box.
of theIfover
OMU a connection
maintenance
a network from
and the tool
test
interface LMTand to
for the alarm
service
with the box is
access,
alarm User
port.
required,
the source start the
IP address alarm forwarding system. The
box
If theover
U2000a serial port. is proxy
the virtual IP address of the name/p
alarm
U2000
The or theor
forwarding
destination IP another
system
address
ports are of theserver
communicates
used proxy
forfor
acts
server. as athe
with
communication
proxy NO assword SSL/TLS
of
OMU the maintenance
overthe a network and test
interface tool
and service
with the alarm access, User
between
the destination OMU and
IPport.
address the is alarm forwarding
the virtual system
IP address of name/p
box
and over
for a serial
reporting the alarm box control information
the U2000
The source or the are
ports IP address
used forofcommunication
the proxy server. NO assword SSL/TLS
to implement the audible and visual alarm function.
between
Port 6100the is anOMU and the alarm
unencrypted access forwarding
port, andsystem port
and
8100 is an SSL-encrypted access port. information
for reporting the alarm box control NO N/A SSL/TLS
to implement the audible and visual alarm function.
The
access port, and port
between the OMU and
8100 is an SSL-encrypted access the VNP toport.
implement the NO N/A SSL/TLS
information collection function.
The
Port source
6200 isports are used foraccess
an unencrypted communication
port, and port
between the OMU and
8200 is an SSL-encrypted access the VNP toport.
implement the NO N/A SSL/TLS
information collection function.
The
access port, and port
between
8200 is an SSL-encrypted access upgrade
the OMU and the driver port. tool. NO N/A SSL/TLS
Port 6000 is an
The
The source
source ports
unencrypted port
accessisare
used used
port, for
forand communication
communication
port 8000 is an between
SSL-
between
the OfficeScan
encrypted the OMU
access serverport.and client. upgrade tool.
and the driver YES N/A SSL/TLS
Ifports
the U2000 Portor6000another is anproxy server
The
The destination
destination
unencrypted accessport isare
used
port, used
and for
forport communication
communication
8000 is an SSL-
acts
between
betweenas a the
proxy
the OMU of the
OfficeScanandmaintenance
the USB and
server Diskand Tool.test tool for
client. YES N/A SSL/TLS
encrypted access
service access, the Port port.
source IP address is the virtual IP User
If the 6000 isanother
an unencrypted
The
accesssource
address port, ports
of theand U2000are U2000
port used
or the
8000
or
for
is communication
IPan address proxy
of theserver
SSL-encrypted proxy name/p
acts
betweenas a
server. port. the OMU and the USB Disk Tool.test tool for
proxy of the maintenance and NO assword SSL/TLS
access
service access, the Port destination
If the U2000 or another6000proxy is IP
anaddress
unencrypted
server
is the
acts as of
a
User
virtual IP
access address
port, and port of the U2000
8000 is an orSSL-encrypted
the IP address name/p
proxy
the proxy of the maintenance
server. and test tool for service NO assword SSL/TLS
access
access,port.the source IP address is the virtual IP User
address ofU2000
If the the U2000 or another
or the proxy
IP address server of acts as a
the proxy name/p
proxy
server. of the maintenance and test tool for service NO assword SSL/TLS
access, the destination IP address is the virtual IP User
address of the U2000 or the IP address of the proxy name/p
server. NO assword SSL/TLS

between the OMU and the OMU Installation Tool.
Port 6000 is an
The source ports
unencrypted accessare port,
usedandfor communication
port 8000 is an SSL-
between
encryptedthe OMU port.
access and the OMU Installation Tool.
If the U2000Port 6000 is proxy
or another an server
unencrypted access port, and port
acts as a proxy of the maintenance and test 8000 is antool
SSL-
for
encrypted access port.
service access, the source IP address is the virtual IP User
address of the U2000If the U2000
or theor IP another
address proxy
of theserver
proxy name/p
acts as a proxy of the maintenance and test tool for
server. NO assword SSL/TLS
service access, the destination IP address is the User
The destination
virtual IP address ports
of theareU2000
used by the IP
or the OMU to
address of name/p
receive data
the proxy server.from the board replacement tool and to NO assword SSL/TLS
export its configuration data. User
The
Port source
6000 isports are used byaccess
an unencrypted the OMU to and
port, receive
port name/p
data from the board replacement
8000 is an SSL-encrypted access port. tool and to export NO assword SSL/TLS
its configuration data. User
The OMU that runs the Suse Linux OS provides the
client with the destination port used for remote
procedure call (RPC). The external services provided
The OMU
by the that runsport
destination the Suse
have Linux OS provides
been shielded the
in the
client with the
current version. destination port used for remote NO N/A SSL/TLS
procedure call (RPC). The external services provided
by the destination port have been shielded in the
The destination
current version. port functions as the port for NO N/A SSL/TLS
Microsoft remote procedure call in the Window OS.
The
The destination
external servicesport functions
providedas bythe
theport for
destination
Microsoft NetBIOS Name service (file
port have been shielded in the current version. and printer NO N/A SSL/TLS
sharing) in the Window OS. The external services
provided by the destination port have been shielded
The destination
in the port functions as the port for
current version. NO N/A SSL/TLS
Microsoft-DS service in the Window OS. The external
services provided by the destination port have been
The destination
shielded port functions
in the current version.as the port for NO N/A SSL/TLS
printing the server in the Window OS. The external
The destination
services provided port
by is
theused for security
destination portmechanism
have been
in the Microsoft Window
shielded in the current version. OS. The destination port is NO N/A SSL/TLS
used for local security and login policy. The external
The destination
services provided port
by functions as the port
the destination port have
for Point-
been
to-Point Tunneling Protocol
shielded in the current version. (PPTP) routing and NO N/A SSL/TLS
remote access. The external services provided by
the destination port have been shielded in the
The destination
current version. port functions as the port for name NO N/A SSL/TLS
parsing by the NetBIOS in the Windows OS. The
external services provided by the destination port
The
havedestination
been shielded portinfunctions
the current as the port for
version. NO N/A N/A
NetBIOS datagram service in the Window OS. The
external services provided by the destination port
The
havedestination
been shielded portinfunctions
the current as the port for
version. NO N/A N/A
Microsoft-DS service in the Window OS. The external
The destination
shielded port functions
in the current version.as the port for NO N/A N/A
process lsass.exe service in the Window OS. The
The destination
external servicesport is used
provided byfortheLayer 2 Tunneling
destination port
Protocol
have been shielded in the current version. in the
(L2TP) routing and remote access NO N/A N/A
Window OS. The external services provided by the
destination port have been shielded in the current
The destination port is used for NAT-T routing and
version. NO N/A N/A
remote access in the Window OS. The external
shielded in the current version. NO N/A N/A
The destination port is used to transmit DHCP

packets between the BSC and the BTS, and ports on
both side must be enabled. The controller can
function as the DHCP server of the BTS or NodeB. NO N/A N/A

The destination port is used to transmit DHCP
packets between the BSC and the BTS, and ports on
both side must be enabled. The controller can
function as the DHCP server of the BTS or NodeB. NO N/A N/A
The destination port is used to receive DHCP
packets sent from the BTS or NodeB. NO N/A N/A
The destination port is used to receive DHCP
packets sent from the BTS or NodeB. NO N/A N/A
The controller supports the DHCP relay function and
relays the DHCP request packets from the base
station to the U2000 server. NO N/A N/A
The controller supports the DHCP relay function and
relays
Data isthe DHCP request
transmitted between packets from the
the NodeB to base
the
station to the U2000 server.
controller over both the source and destination NO N/A N/A
ports on the Iub signaling links, NCP links, and CCP
links.
·
The ports need to be negotiated between the
Ports
source onandboth sides are ports
destination used for the eGBTS and
by configuring the BSC
to transmit
data. data over CSLs and RSLs. YES N/A N/A
Ports
source on both sides are portsused for the eGBTS and the BSC
Data
to is and
transmit
destination
transmitted
data over between
CSLs
by configuring
the
and NodeB to the
RSLs.
data.
controller over both YES N/A N/A
The ports need to bethe source and
negotiated destination
between the
ports on the Iub signaling links,
source and destination ports by configuring NCP links, andtheCCP
links.
data. YES N/A N/A
source and destination ports by configuring the
The
data.BTS and the controller communicate with each YES N/A N/A
other on the user plane over both the source and
destination
The NodeB ports.
and The port number ranges from
The
5000BTS and
to 64967. thethe controller
controller communicate
communicate withwith
each NO N/A N/A
each other on the user plane over
other on the user plane over both the source andboth the source
and destination
destination ports.ports.
The The destination
source port port ranges
number number
The NodeB
ranges from and
5000 the tocontroller
64967. communicate
The source port with
from 5000
each other to
on64967.
the user plane over both the source NO N/A N/A
number ranges from 30000 to 46895 when the
and
GBTS destination
and NodeBports. shareThe port
an IP number
address; ranges from
otherwise, the
5000 to 64967. The destination port
source port number ranges from 1024 to 17919. number ranges NO N/A N/A
from 30000 to 46895 when the GBTS and NodeB
The
shareBTS an and the controller
IP address; otherwise,exchange maintenance
the destination port
plane and control plane
number ranges from 1024 to 17919. signaling on the operation NO N/A N/A
and maintenance link (OML), extended maintenance
link (EML), and the layer 2 management link (L2ML)
The
overBTS
bothand thethe controller
source exchange maintenance
and destination ports. NO N/A N/A
plane and control plane signaling on the OML, EML,
The
and BTS
L2MLorover NodeBboth andthethe controller
source multiplex data
and destination
packets
ports. to improve transmission efficiency when NO N/A N/A
they perform AbisMUX/FPMUX over both the source
The
and BTS or NodeB
destination and Port
ports. the controller
65010 is themultiplex
UDP data
packets to improve transmission
destination port for the data packets. efficiency when NO N/A N/A
they perform AbisMUX/FPMUX over both the source
The
and BTS or NodeB
destination and Port
ports. the controller
65010 is themonitor
UDP the
quality of service (QoS) of
destination port for the data packets.transmission links after NO N/A N/A
they successfully implement IPPM negotiation over
The
bothBTS
the or NodeB
source and and the controller
destination ports.monitor the is
Port 65020
QoS of transmission links after
the UDP destination port for data packets. they successfully NO N/A N/A
implement IPPM negotiation over both the source
and destination ports. Port 65020 is the UDP
destination port for data packets. NO N/A N/A
The BTS use this port to verify whether the backup
Abis link is available for the Abis transmission
backup enhancement feature. NO N/A N/A
The BTS use this port to verify whether the backup
Abis link is available for the Abis transmission
backup enhancement feature. NO N/A N/A

The ports are used for UDP echo ping continuity
check between the controller and the BTS or NodeB.
The controller initiates the UDP ping check, and the
The
baseports areperforms
station used for aUDP echo ping continuity
loopback. YES N/A N/A
The controller initiates the UDP ping check, and the
The
baseports areperforms
station used for aUDP echo ping continuity
loopback. YES N/A N/A
The base station initiates the UDP ping check, and
The ports are used
the controller for UDP
performs echo ping continuity
a loopback. YES N/A N/A
The base station initiates the UDP ping check, and
The ports are used
the controller for UDP
performs ping check between the
a loopback. YES N/A N/A
controller and the BTS or NodeB. The controller
initiates the UDP ping check, and the base station
The ports aare
performs used for UDP ping check between the
loopback. NO N/A N/A
controller and the BTS or NodeB. The controller
initiates the UDP ping check, and the base station
performs a loopback. NO N/A N/A
The controller sends UDP packets to the BTS or
The
NodeB,source
andports are or
the BTS used for the
NodeB controller
extracts VLANwhich
IDs
functions as the client
from the received packets. to check the Two-Way Active NO N/A N/A
Measurement Protocol with the peer device. The
The destination
destination portsports are used for
are negotiated the controller
between the
which functions as the client to check
controller and the peer device using the theTCP.
Two-Way NO N/A N/A
Active Measurement Protocol with the peer device.
The
The source
source ports
ports are
are used for thebetween
negotiated controller which
the
functions
controller and the peer device using the TCP. Active
as the server to check the Two-Way NO N/A N/A
The destination
between the
which
controller and the peer device using thethe
functions as the server to check Two-Way
TCP. NO N/A N/A
The source ports are negotiated between the
controller and the peer device using the TCP. NO N/A N/A
The source ports are used for the controller which
functions as the client to check the Two-Way Active
Measurement Protocol with the peer device. NO N/A N/A
The destination ports are used for the controller
which functions as the client to check the Two-Way
Active Measurement Protocol with the peer device. NO N/A N/A
The source port is used for the controller which
functions as the server to check the Two-Way Active
The destination port is used for the controller which
The SGSN and the controller transmit Iu-PS user
The
planeSGSN
Signaling and
dataover the Iu-CS,
the controller
encapsulated transmit
Iu-PS,
according to Iu-PS
A, IuPC or Lbuser
GTPU protocol
plane
over data
interface encapsulated
bothisthetransmitted
source and according
between to GTPU
the MSC,
destination protocol
ports.SGSN,
over
For both
SAS,the the
or G-PDU,
SMLC and source and destination
theRequest,
Echo controller over ports.
both the
Signaling
For the and
source over
G-PDU, the
EchoIu-CS,
destination Iu-PS,and
Request,
ports. and
Supported
A, IuPC or Lb
Supported YES N/A N/A
Extension Headers
interface isHeaders Notification
transmitted between messages,
the MSC, theSGSN,
Extension
destination UDP portNotification messages, the
SAS, or SMLC
destination UDPand thenumber
port number
is 2152.
controller
is 2152,
For the
over both
and the
the
Echo
Response
The SGSN and
and Error
the
and destination Indication
controller
ports. messages,
transmit data the
to each YES N/A N/A
source UDP
destination port port
UDP number is determined
number is determined by the
byRNC.
the
other
For theover
Echothe Gb interface
Response and using
Error both the source
Indication
RNC,and
and the source
destination ports.UDP
Theport
SGSNnumber
and is 2152.
the controller
messages,
The the the
SGSN select
and destination
controllerUDP port number
transmit data toiseach NO N/A N/A
randomly
determined by ports
the from
SGSN, their
and therespective
source UDP port
other over the
configured UDP Gb interface
port number using both the
segments. source
The ranges
number
and is 2152.ports. The SGSN and the controller
destination
of the UDP destination port number are 1214~2001, NO N/A N/A
randomly
2005~3783, select ports fromand
3786~4783, their respective The
4785~65000.
configured UDP port number segments.
range of the UDP source port number is from The ranges
0 to
of the
65535. UDP source port number are 1214~2001, YES N/A N/A
2005~3783, 3786~4783, and 4785~65000. The
range of the UDP destination port number is from 0
to 65535. YES N/A N/A

During the communication between the MGW and
the controller over both the source and destination
ports, the user plane uses the Real-time Transport
During
Protocolthe communication
(RTP). The destination between theUDP
port for MGW and
packets
the
uses controller
anlueven over both the source and destination
On the
ports, or Anumber
thepackets
user interface,
plane
and the
the MGW UDP destination
RTP.performs UDP port
for RTCP
multiplex for usesuses
packets to
the
animprove
odd number.TheThat
destination
transmission is, the
port
RTCPfor UDP
port packets
number uses
is the an port
RTP evennumber
numberplus and1.the NO N/A N/A
efficiency
UDPthe after
destination itport
successfully
for the
RTCP implements
packets usesUDPan odd
On lu
multiplexingor A interface,
negotiation withMGW performs UDP
number. That
multiplex for is, the RTCP
packets to portthe
improve
controller
number is the
transmission
over
RTP
both the source
port number plusand1. destination ports. Port 2002 is NO N/A N/A
efficiency
the UDP port after
foritcommon
successfully implements
UDPMUX packets, UDP
and
multiplexing negotiation with the
port 2004 is the UDP port for UDPMUX packets controller over with
both the source and header.
an RTP-compressed destination ports. Port 2002 is NO N/A N/A
the UDP port for common UDPMUX packets, and
The
port source
2004 isports
the UDPare used for UDPMUX
port for the controller which
packets with
functions as the client
an RTP-compressed header. to check the Two-Way Active NO N/A N/A
The destination
between the
which functions as the client to
controller and the peer device using the check theTCP.
Two-Way NO N/A N/A
The
The source
source ports
ports areare used for thebetween
negotiated controllerthewhich
functions
controller and the peer device using the TCP. Active
as the server to check the Two-Way NO N/A N/A
The destination
between the
which
TCP. NO N/A N/A
The ports are used for control plane data

transmission
When RNC inoverPoolthe Iur interface
is enabled, betweenRNCs
two physical RNCsin
and Iur-g interface between the BSC and RNC.
the pool transmit control plane data over both the YES N/A N/A
source andare
The ports destination ports. The
used to transmit Iur-p
user signaling
plane data on
uses
the a
Iur proprietary
interface protocol
between and
RNCs. therefore is NO N/A N/A
The ports are used
encapsulated for the
into UDP controller
packets. whichon
The RNCs functions
both
as the client/server to check the Two-Way Active
side randomly select ports in their respective port
Measurement
number segment. Protocol with the peer device. The NO N/A N/A
ports which does not function as the client/server
are negotiated between the controller and the peer
device using the TCP. NO N/A N/A
The ports are used for the controller which functions
as the client/server to check the Two-Way Active
The ports are used to transmit user-plane data over
the Iur-p interface. NO N/A N/A
When RNC in Pool is enabled, the Iu/Iur control
plane data is transmitted in the Iur-p interface,
which is encapsulated into UDP packets. NO N/A N/A
The ports are used to transmit user-plane data
through a tunnel over the Iur-p interface between
two physical RNCs in a pool. NO N/A N/A
The ports are used to detect transmission
interruption using the UDP ping over the Iur-p
interface between two physical RNCs in a pool. NO N/A N/A

The ports are used to detect transmission quality
using the IPPM over the Iur-p interface between two
physical RNCs in a pool. NO N/A N/A
Signaling over the Iu-CS, Iu-PS, A, IuPC or Lb

interface is transmitted between the MSC, SGSN,
SAS, or SMLC and the controller over both the
Signaling
source and over the Iu-CS,
destination Iu-PS, A, IuPC or Lb
ports. YES N/A N/A
interface is transmitted between the MSC, SGSN,
SAS, or SMLC and the controller over both the
source and destination ports. YES N/A N/A
The RNC and the RAN CBC transmit signaling over

the Iu-BC interface using both the source and
destination ports. The source and destination port
The RNC and
numbers the RAN
are fixed CBC transmit signaling over
to 3452. NO N/A N/A
the Iu-BC interface using both the source and
destination ports. The source and destination port
The BSC and fixed
numbers are GSM CBC transmit signaling to each
to 3452. NO N/A N/A
other through both the source and destination ports.
The port number must be configured after the
The BSC andby
negotiation GSM CBC
both transmit signaling to each
sides. YES N/A N/A
other through both the source and destination ports.
The port number must be configured after the
negotiation by both sides. YES N/A N/A
The ports are used for signaling exchange between

the BSC and the AC in the Intelligent Wi-Fi Detection
and Selection feature. The port number must be
The ports are
configured used
after thefor signaling exchange
negotiation between YES
by both sides. N/A N/A
the BSC and the AC in the Intelligent Wi-Fi Detection
and Selection feature. The port number must be
configured after the negotiation by both sides. YES N/A N/A
The destination ports are used for continuity check

between the controller and the peer device. Port
3784 is the UDP destination port for the single-hop
The
BFD.destination ports are used for continuity check NO N/A N/A
3784 is the UDP destination port for the single-hop
The
BFD.destination port is used for continuity check NO N/A N/A
4784 is the UDP destination port for the multi-hop
The
BFD.destination port is used for continuity check NO N/A N/A
4784 is the UDP destination port for the multi-hop
BFD. NO N/A N/A
The ports are used for Ping check between the
controller and the bearer network device or the peer
NE. NO N/A N/A
The ports are used for Ping or TraceRT check
between the controller and the bearer network
The controller
device usesNE.
or the peer the UDP to check the continuity NO N/A N/A
with the bearer network device or the peer NE hop
The source
by hop and ports are used
implements thefor the controller
TraceRT which
function. The
functions as the client to check
source port is randomly allocated. the Two-Way Active NO N/A N/A
The destination
between the
which functions as the client to check
controller and the peer device using the theTCP.
Two-Way NO N/A N/A

The destination
between the
which
TCP. NO N/A N/A
The ECO6910 functioning as the SCTP server

performs network optimization management on the
RNC functioning as the SCTP client. YES None None
RNC functioning as the SCTP client. YES None None
BSC functioning as the SCTP client. YES None None
ECO6910
The OMU functioning
functioning as theasCertificate
the SCTP server
Management
performs(CMP)
Protocol network
V2 optimization
client performs management
equipment on the
BSC functioning
certificate as theor
application SCTP client.
update with the CA YES None None
certificate server of the operator functioning as the
The
CMPOMU functioning as the Certificate Management
V2 server.
Protocol
The default portV2
(CMP) ofclient performs equipment
the destination port is 80 and
certificate application or
443. Port 80 is not encrypted update
andwith
portthe
443CAis Certifica
certificate
encrypted. server of the operator functioning as the YES tion SSL/TLS
CMP V2 server.
The
The OMU functioning
default port of theassource
the Lightweight Directory
port is 80 and 443. Root
Certifica
Access Protocol (LDAP) client performs certificate
Port 80 is not encrypted and port 443 is encrypted. YES Distingu
tion SSL/TLS
revocation list update with the CRL certificate server ish
The OMU
of the functioning
operator as theas
functioning Lightweight Directory
the LDAP server. The Root
Name/P
Access Protocol (LDAP)
default port is 389. client performs certificate YES Distingu
assword SSL/TLS
revocation list update with the CRL certificate server ish
of the operator functioning as the LDAP server. The Name/P
default port is 389. YES assword SSL/TLS
This port is used for JSON-based communication

between the EBC and SAU of the U2000. Port 30070 Challen
is a non-encrypted port and port 30170 is an SSL ge/resp
encrypted port. No onse SSL/TLS
Used by the U2000 as an FTP server (working in the PASV User
mode) to respond to data transfer requests of an FTP client name/pa
for uploading and downloading software and logs. No ssword SSL/TLS
This port is opened for the SAU to receive SSH User

access requests from the client in order to maintain name/p
the SAU. No assword SSL/TLS

This port is used for JSON-based communication
between the U2000 Trace Server and the SAU. Port Challen
30090 is a non-encrypted port and port 30190 is an ge/resp
This port is used
SSL encrypted for stream data transmission
port. No onse SSL/TLS
between the U2000 Trace Server and the SAU. Port Challen
6006 is a non-encrypted port and port 8006 is an ge/resp
SSL encrypted port. No onse SSL/TLS

Plane Version Special Scenario
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance V900R0
All
plane 19C10S
versions N/A
PC520
Maintenance V900R0
and
plane 19C10S
later N/A
PC520
Maintenance V900R0
and
plane 19C10S
later N/A
PC520
V900R0
and
19C10S
Management plane later N/A
PC520
and
Management plane later N/A
Port 123 of the OMU starts
to provide services after you
have added the information
Maintenance All Port 123
of the of the
SNTP OMU starts
server
plane to provide services
versions (SNTPSRVINFO). after you
have added the information
Maintenance All of the SNTP server
plane versions (SNTPSRVINFO).
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A

Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane V900R0
versions N/A
14C00
Maintenance and
plane V900R0
later N/A
14C00
Maintenance and
plane V900R0
later N/A
15C01
Maintenance and
plane V900R0
later N/A
15C01
Maintenance and
plane later N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane V900R0
versions N/A
19C10
Maintenance and
plane V900R0
later N/A
19C10
Maintenance and
plane later N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A

Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions For Windows OS only
Maintenance All
Maintenance All
plane versions For Linux OS only
Maintenance All
plane versions For Linux OS only
Maintenance All The NetEco applies to
plane versions GBSS12.0 and later.
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All Port 6200 or port 8200 (SSL-
plane V900R0
versions encrypted)
N/A starts to provide
12C03 listening services after you
Maintenance and Port
have6200 or VNP
added port information
8200 (SSL-
plane V900R0
later encrypted)
(GVNPADDR).starts to provide
12C03 listening services after you
Maintenance and have added VNP information
plane later (GVNPADDR).
Maintenance All
Maintenance All
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane versions N/A

Maintenance All
plane versions N/A
Maintenance V900R0
All
plane 12C01
versions N/A
and
Maintenance V900R0
later
plane 12C01
versions N/A
and
Maintenance later
plane versions N/A
Maintenance All
plane versions For Suse Linux OS only
Maintenance All
plane versions For Suse Linux OS only
Maintenance All
Maintenance All
Maintenance All
Maintenance All
Maintenance All
Maintenance All
Maintenance All
Maintenance All
Maintenance All
Maintenance All
Maintenance All
Maintenance All
Maintenance All
plane versions N/A

Maintenance All
plane versions N/A
Maintenance All
plane versions N/A
Maintenance All
plane V900R0
versions N/A
15C00
Maintenance and
plane V900R0
later N/A
15C00
Maintenance and
plane later N/A
All
Control plane V900R0
versions N/A
15C00
and
later N/A
15C00
and
Control plane later N/A
All
Control plane versions N/A
All
User plane versions N/A
All
All
All
Maintenance
plane All
Maintenance
plane All
All
All
Maintenance All
plane versions N/A
Maintenance All
plane V900R0
versions N/A
14C00
Maintenance and Abis transmission backup
plane V900R0
later enhancement feature
14C00
Maintenance and Abis transmission backup
plane later enhancement feature

V900R0
15C00
and
User plane V900R0
later N/A
15C00
and
User plane V900R0
later N/A
15C00
and
User plane V900R0
later N/A
15C00
and
User plane V900R0
later N/A
13C00
and
User plane V900R0
later N/A
13C00
and
User plane later N/A
Maintenance All
User
planeplane V900R0
versions N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
plane later N/A
All
All
User plane
Control plane
Maintenance All
User
planeplane versions N/A
Control plane
Maintenance All
User
Control plane
Maintenance All
User
Control plane
Maintenance All
plane versions N/A

All
All
All
All
User
User plane
plane V900R0
versions N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
plane later N/A
All
All
User plane V900R0
versions N/A
15C00
and
User plane
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
plane V900R0
later N/A
15C01
and
User plane V900R0
later N/A
15C00
and
later N/A
15C01
and
User plane V900R0
later N/A
15C01
and

V900R0
15C01
and
All
All
All
All
All
All
V900R0
15C00
and
later N/A
15C00
and
Control plane later N/A
User plane
Control plane
Maintenance All
User
Control plane
Maintenance All
User
Control plane
Maintenance All
User
Control plane
Maintenance All
User
Control plane
Maintenance All
User
Control plane
Maintenance All
User
Control plane
Maintenance All
User
planeplane V900R0
versions N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
plane later N/A

User plane V900R0
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
User
planeplane V900R0
later N/A
Control plane 15C01
Maintenance and
plane later N/A
V900R0
16C00
and
later None
16C00
and
later None
16C00
and
later None
16C00
and
Control plane later None
V900R0
16C00
Maintenance and
plane V900R0
later None
16C00
Maintenance and
plane V900R0
later None
16C00
Maintenance and
plane V900R0
later None
16C00
Maintenance and
plane later None
All
OM versions None
All
OM versions None
All
OM versions None

All
OM versions None
All
OM versions None


BSC6900 Communication Matrix (V900R019C10 - 04) (XLS) - EN

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BSC6900 Communication Matrix (V900R019C10 - 04) (XLS) - EN

Hochgeladen von

Copyright:

Verfügbare Formate

BSC6900 V900R019C10

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential

ument is intended for:

the source device

on mode used on the port

Huawei Proprietary and Confidential

OMU<->FTP server/client Debugging IP address

Huawei Proprietary and Confidential 8

OMU<->OMU External fixed IP

OMU<->Maintenance and Test Tool

Huawei Proprietary and Confidential 9

Huawei Proprietary and Confidential 10

External virtual IP 6000,

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Client IP address of the client 1024~65535

Huawei Proprietary and Confidential 11

eGBTS eGBTS IP address 1024-65535

BSC BSC IP address 1024-65535

RNC IP address of the RNC 4096~12287,

BSC IP address of the BSC 5000~64967

RNC IP address of the RNC 5000~64967

BTS IP address of the BTS 12288~28673

BSC IP address of the BSC 4502~4649

BTS IP address of the BTS 65043

BSC IP address of the BSC 65043

Huawei Proprietary and Confidential 12

RNC IP address of the RNC 0~65535

SGSN IP address of the SGSN 1214~2001,

Huawei Proprietary and Confidential 13

RNC IP address of the RNC 5000~64967

RNC IP address of the RNC 4100~4499

RNC IP address of the RNC 5000~64967

RNC IP address of the RNC 65061, 65062

RNC IP address of the RNC 65060

RNC IP address of the RNC 65042~65043

Huawei Proprietary and Confidential 14

BSC/RNC<->SMLC/SAS IP address of the SAS

RNC IP address of the RNC 3452

BSC IP address of the BSC 0~65535

AC(Access Controller) IP address of the AC 0~65535

BSC IP address of the BSC 4900~4999

BSC/RNC<->Transmission Equipment IP address of the

Huawei Proprietary and Confidential 15

RNC IP address of the RNC 1024~65535

BSC IP address of the BSC 1024~65535

SAU <-> U2000

SAU (FTP client) IP address of the SAU 25000–30000

SSH client <-> SAU