IP RAN Deployment Guide

March 25, 2018 | Author: Dhananjaya Mandal | Category: Quality Of Service, Computer Network, Multiprotocol Label Switching, Ip Address, Network Switch


Comments



Description

EhuDocument Code Intended Audience Department INTERNAL WCDMA UMTS Maintenance Dept Product Name WCDMA RNC&NodeB Product Version V200R0010 Document Version IPRAN Deployment Guide V210 Prepared by Transport Team of Maintenance Dept UMTS Date 2008-08-25 Reviewed by Transport Team of Maintenance Dept UMTS Date 2008-08-25 Reviewed by Transport Team of Maintenance Dept UMTS Date 2008-08-25 Approved by Date Huawei Technologies Co., Ltd. All rights reserved INTERNAL IPRAN Deployment Guide Revision Record Date Revision Version Description Author 2008-06-16 V1.0 Initial draft Transport Team of UMTS Maintenance Dept 2008-08-01 V1.1 Modified on the basis of test and review results Transport Team of UMTS Maintenance Dept 2008-08-21 V1.2 Modified on the basis of review results by Maintenance Dept Transport Team of UMTS Maintenance Dept INTERNAL IPRAN Deployment Guide Contents 2008-09-14 Huawei Confidential Page 2 of 133 ...................13 Table 2..............................................................13 Table 2.................................INTERNAL IPRAN Deployment Guide Tables Table 2..................................1Hardware requirements .15 2008-09-14 Huawei Confidential Page 3 of 133 ...................4Functions of NodeB IP transmission boards ................3Comparison of RNC IP interface boards .................2Version requirement .........................................................................................................12 Table 2......... ........94 Figure 1...................18E1-based IP planning ...................................................60 Figure 1..................16 Figure 1.29 Figure 1....16IP RAN hybrid transport networking .............................................................................................................Iub...........60 Figure 1.....................................31 Figure 1..........9L3 networking of RNC directly connecting to one router ...1PPP frame format .6SDH-based IPRAN L2 networking ...............47 Figure 1........................................................93 Figure 1...4Principle of multi-home ................................59 Figure 1...........................INTERNAL IPRAN Deployment Guide Figures Figure 1....................8 Figure 1.........................................28 Figure 1...............23IP protocol stack of IU-PS interface...............11L3 networking with the load sharing .....26IUPS data planning ......................................25 Figure 1.7MSTP-based IPRAN L2 networking ........................27 Figure 1..................30 Figure 1......................10L3 networking of RNC directly connecting to two routers ................52 Figure 1......................24 Figure 1...........18 Figure 1.........19Dual stack transport networking.............8 Figure 1................5PDH/SDH-based IPRAN L2 networking ................21IP address planning for layer 3 networking over Ethernet.........20ATM configuration planning............................................................................93 Figure 1...........................................26 Figure 1.............................3Position of the M3UA in each interface protocol stack ..........................................................2IPHC compression range ...........59 Figure 1.........................................................................................................................................................................92 Figure 1.................24 Figure 1.....42 Figure 1......................17IP planning of Ethernet-based L3 networking .....14 Iub interface protocol stack ...........................................................................................................8Data network-based IPRAN L2 networking .......................................53 Figure 1..............................................................22IP address planning for layer 2 networking over Ethernet.......................................53 Figure 1...................24IP protocol stack of IU-CS interface..............................13IPRAN networking in the ATM/IP dual-stack transport ......................15IP planning of Ethernet-based L3 networking ................................................................................................................................................................................Iub...........................................................................25IP protocol stack of IUR interface..............95 2008-09-14 Huawei Confidential Page 4 of 133 ............12IPRAN networking in the hybrid transport .................27PSP-IPSP transfer networking .............................................................. ......113 Figure 1.....................................121 Figure 1.............INTERNAL IPRAN Deployment Guide Figure 1...................28ASP-SGP direct connection networking ...............37General process of NodeB remote software debug ......................29ASP-SGP transfer networking ..............................123 2008-09-14 Huawei Confidential Page 5 of 133 .........................36Initial address application in the scenario using the DHCP Relay ...................104 Figure 1..................................................33Maintaining the NodeB directly by the M2000 ............................................................122 Figure 1................................100 Figure 1................96 Figure 1.....32Maintaining NodeB by the M2000 Through the RNC...........116 Figure 1..................122 Figure 1.....30IUCS data planning ...............................96 Figure 1..................34Initial address application in the scenario without using DHCP Relay ............................35Server-Client networking with using the Relay ............................................31IUR data planning ................................................................... the Iub.INTERNAL IPRAN Deployment Guide IPRAN Deployment Guide Keywords: IPRAN. The network construction cost is saved. basic configuration procedure. IPPATH Abstract: This document describes the basic principle. deployment preparation. principles and configurations of the DHCP remote debugging of the WCDMA IPRAN. The information in this document is for the internal use only and cannot be used as the basis for the reply to a customer or Market Dept. precautions.1 Introduction to the V210 IPRAN In V210. Acronyms and Abbreviations: Abbreviations Full Name PPP Point-to-Point Protocol DHCP Dynamic Host Configuration Protocol OSPF Open Shortest Path First RIP Route Information Protocol ISIS Intermediate SystemIntermediate System WFQ Weighted Fair Queuing Chapter 1 Overview 1. the IP network provides a variety of access modes and provides the sufficient transport bandwidth for high speed data services (for example. PPP. SCTP. In addition. basic networking. An operator can use the existing IP networks for the transport expansion. Iur. HSDPA). 2008-09-14 Huawei Confidential Page 6 of 133 . FE. and Iu interfaces are carried over the IP transport network. Command //At the RNC side: ADD IPPATH: FPMUX=YES. 3. SN=6. Protocol The FP MUX is the protocol defined by Huawei. Hence. MAXFRAMELEN=270. TIMER=1. Principles The frame protocol multiplexing (FPMUX) multiplexes several small FP PDU frames (sub-frame) that should be transmitted independently to one UDP/IP frame header. the new IPRAN functions in the V210 are as follows: 1. the transport efficiency increases. After the FP MUX is enabled. FRAMELEN=270. SUBFRAMELEN=127.1 FP MUX 1. By default. the FP MUX is disabled. FPMUXSWITCH=ENABLE.INTERNAL IPRAN Deployment Guide With the comparison to V18 and V29. As a result. FPTIME=2.1. SUBFRLEN=127. the default parameters are as follows:  FPMux maximum sub frame length (SUBFRAMELEN)=127Bytes  FPMux maximum multiplexing frame length (FRAMELEN)=127Bytes  Multiplexing maximum delay (TIMER) = 1ms 2008-09-14 Huawei Confidential Page 7 of 133 . a number of UDP/IP headers are saved. PT=ETH. The FP MUX is applicable to only the user plane in the IPRAN Iub interface. SBT=BASE_BOARD. By default. the FP MUX is disabled. 2. After the FP MUX is enabled. JNRSCGRP=DISABLE. the default parameters are as follows:  FPMux maximum sub frame length (SUBFRLEN)=127Bytes  FPMux maximum multiplexing frame length (MAXFRAMELEN)=127Bytes  Multiplexing maximum delay (FPTIME) =2ms // At the NodeB side: ADD IPPATH: SRN=0.  IP Header Compression (IPHC): The IPHC compresses the IP/UDP header of the PPP frame.1.1 PPP frame format The PPP frame header compression algorithm implements the following:  Address and control field compression (ACFC): The address and control field is the constant value (0XFF03) and is not transported every time.2 IPRAN Header Compression 1.  Protocol field compression (PFC): The PFC can compress two-byte protocol field to one byte. Figure 1. it indicates that the protocol field is two bytes in length. For example. If the LSB is 1. the subsequent packet address and control fields can be compressed. Compression range PPP header IPheader UDP header Application data PPPtail Figure 1. The system judges whether the protocol field is one byte or two bytes according to the last significant bit (LSB) of the first byte in the protocol field. the first byte of the protocol field is 0x00.INTERNAL IPRAN Deployment Guide 1. it can be compressed. After the PPP link is configured with the Link Control Protocol (LCP).2 IPHC compression range 2008-09-14 Huawei Confidential Page 8 of 133 . it indicates that the protocol field is only one byte in length. If the LSB is 0. Principles The IPRAN header compression improves the transport efficiency by compressing partial fields of PPP frames. The compresser uses it to compress the packet header. By default. Protocol  ACFC: RFC 1661  PFC: RFC 1661  IPHC: RFC 2507 and RFC 3544 3. Principles At present. PFC=Enable.  At the NodeB side: ADD PPPLNK: IPHC=ENABLE. Terms: Context: It is the status table of the synchronization maintenance of the same packet stream by the compresser and decompresser. Command  At the RNC side: ADD PPPLNK: MUX=Disable. 2) If the header context of the packet stream is established at both ends of a link. the RNC supports the ARP detection and BFD detection for detecting the transport link from the RNC to the peer equipment:  Address resolution protocol (ARP) detection The system determines the continuity of the link according to the response of the 2008-09-14 Huawei Confidential Page 9 of 133 . The decompresser uses it to recover the compressed packet header. IPHC=UDP/IP_HC. The header field changed according to the designated mode can be replaced by fewer bits. 2. ACFC=Enable. The original header can be recovered according to the context and changed fields. three algorithms are enabled.1. By default. only the changed header field and the corresponding context tag are transferred. ACFC=ENABLE. three algorithms are enabled.INTERNAL IPRAN Deployment Guide IPHC principles: 1) The header field remaining unchanged is not carried in each packet that is sent.3 IPRAN Fault Detection 1. 1. PFC=ENABLE. The detection starts at one single end.  When the active and standby ports are detected at the same time. Every the fixed duration. 2008-09-14 Huawei Confidential Page 10 of 133 . The system deletes the route whose detection address is the next hop. the IP address of the active and standby ports should not be on the same network segment. only active port detection. and active/standby port simultaneous detection. The destination address of the packet is the peer address to be detected.  The detection state is related to the port state. The ARP detection is applicable to only the direct connection detection whose both ends are on the same network segment. The RNC determines the continuity of the link by judging whether the response from the destination address is received.  The detection state is related to the port state. The system deletes the route whose detection address is the next hop. The active/standby port simultaneous detection is not supported. At present. Only the active port is detected. which is the same as the ARP detection. without depending on the peer equipment. The features of the SBFD are as follows:  The both ends must start at the same time. Features of the ARP detection are as follows:  The ARP is the basic protocol. The upper layer service selects other available channels. The V210 RNC implements the single-hop BFD (SBFD) and multi-hop BFD (MBFD):  SBFD: The SBFD is applicable to only the direct connection detection whose both ends are on the same network segment. only the asynchronous mode is supported. The upper layer service selects other available channels. The port switchover is triggered if a fault is detected.INTERNAL IPRAN Deployment Guide peer equipment by sending ARP requests to the peer equipment. the RNC constructs an ARP request packet to send to the network. The port switchover is triggered if a fault is detected.  Bidirectional forwarding detection (BFD) The method of the BFD detecting the link continuity: The system originates the handshake packets from both ends and determines the link continuity according to the handshake result (success or failure).  The ARP detection supports the independent port detection.  The independent port detection is supported. The detection duration at both ends must be configured to be equivalent.  The detection state is not associated. 3) Independent port detection STR GATEWAYCHK: SRN=0.10". GATEWAY="100.255.10.0". Commands By default. BAKIP="100.10. ARPRETRY=3. BAKGATEWAY="100. the peer IP address and any local IP address should not be on the same network segment.10". BAKMASK="255. 2.255. The features of the MBFD are as follows:  The both ends must start at the same time.  The MBFD does not depend on a port. Protocol ARP protocol and BFD protocol 3. or MBFD is disabled. SN=14. GATEWAY="100.10. MODE=INDPORT.10. PN=0. The IP (DEVIP or ETHIP) of the active and standby boards can be used as the local address of the multi-hop BFD. ARPTIMEOUT=3. ARPTIMEOUT=3. If a fault is detected. SN=14.10. Default parameters of the ARP detection:  ARPTIMEOUT: 300 ms 2008-09-14 Huawei Confidential Page 11 of 133 .10.10.10. 2) Active port detection STR GATEWAYCHK: SRN=0.  ARP detection (three modes) 1) Active/standby port simultaneous detection STR GATEWAYCHK: SRN=0. The detection duration at both ends must be configured to be equivalent.20". ARP detection. At present. ARPRETRY=3. MODE=REDPORT. PN=0. only an alarm is reported. In addition. ARPRETRY=3. ARPTIMEOUT=3. CHKTYPE=ARP.20".20. only the asynchronous mode is supported. SN=14.INTERNAL IPRAN Deployment Guide  MBFD: The MBFD is applicable to the non direct connection end-to-end detection in the scenario where signals pass more than one network nodes. GATEWAY="100. CHKTYPE=ARP.10". SBFD. CHKTYPE=ARP. MODE=PRIMARYCHKONLY. PN=0.20. MINRXINT=30.10. MINTXINT=30.20".10. MINTXINT=30. CHKTYPE=SBFD. MBFDLOCALIP="100. Table 2. 2) Active port detection STR GATEWAYCHK: SRN=0. SN=14.20".2.10.20. CHKTYPE=MBFD. PN=0. The symbol '√' indicates that the NE is required.10".10.10. GATEWAY="100.2 Availability 1.INTERNAL IPRAN Deployment Guide  ARPRETRY: 3 times  SBFD 1) Independent port detection STR GATEWAYCHK: SRN=0. MINTXINT=30. Table 1-1 lists the data configuration requirements for these NEs. BFDDETECTCOUNT=3 The default parameters of the BFD are as follows:    Min interval of BFD packet send (MINTXINT): 30 ms Min interval of BFD packet receive (MINTXINT): 30 ms BFDDETECTCOUNT: 3 times 1. SN=14. MINRXINT=30. SN=14.20". and CN.20.10. BFDDETECTCOUNT=3. MODE=INDPORT. GATEWAY="100.1 Hardware requirements IP feature requirement NodeB RNC CN Data configuration √ √ Hardware requirements WMPT/UTRP PEUa/POUa/UOIa_IP/FG2a/GOUa 2008-09-14 Huawei Confidential √ Page 12 of 133 .1 Requirements for NEs The IP feature requires the coordination of the NodeB. PN=0. MINRXINT=30. BFDDETECTCOUNT=3. MODE=PRIMARYCHKONLY. RNC. CHKTYPE=SBFD. GATEWAY="100.  MBFD STR GATEWAYCHK: SRN=0. INTERNAL IPRAN Deployment Guide 1. Iu-BC.3 Other Support 1.2. the corresponding IP interface boards should be added at the RNC and NodeB sides. Iur.3 Comparison of RNC IP interface boards Board Type FG2a Description  Enabling IP over Ethernet  Providing eight FE ports and two GE electrical ports  Providing IP over FE/GE  Supporting interfaces such as Iu-CS. and Iub 2008-09-14 Huawei Confidential Page 13 of 133 .2 Version requirement Product Supporting Version RNC BSC6810 BSC6810V200R010C01B051 and later NodeB DBS3836 V200R010C01B040 and later BTS3836/ BTS3836A V200R010C02B040 and later CME M2000 1.2 Supporting Versions Table 2. Iu-PS. Table 2. At the RNC side. RNC side If the IP RAN feature is required. the interface boards supporting the IP interface are as follows:  FG2a: RNC packet over electronic 8-port FE or 2-port GE Ethernet Interface unit REV:a  GOUa: RNC 2-port packet over Optical GE Ethernet Interface Unit REV:a  PEUa: RNC 32-port Packet over E1/T1/J1 Interface Unit REV:a  UOIa_IP: RNC 4-port Packet over Unchannelized Optical STM-1/OC-3c Interface unit REV:a  POUa: RNC 2-port packet over channelized Optical STM-1/OC-3 Interface Unit REV:a The following table describes the features and functions of these boards.2. and Iub  Supporting IP over E1/T1/J1  Providing 32 channels of IP over PPP/MLPPP over E1/T1  Providing 128 PPP links or 64 MLPPP groups. each MLPPP group containing 8 MLPPP links  Providing the fractional IP function  Providing the timeslot cross-connection  Obtaining clock signals from the Iu interface and exporting timing signals to the GCUa/GCGa board UOIa_IP  Exporting timing signals to the NodeB  Supporting interfaces such as Iu-CS. 64 MLPPP groups are provided. Iur.INTERNAL IPRAN Deployment Guide GOUa PEUa  Enabling IP over Ethernet  Providing two GE optical ports  Providing IP over GE  Supporting interfaces such as Iu-CS. and Iub  Obtaining clock signals from the Iu interface and exporting the clock signals to the GCUa/GCGa board POUa  Exporting clock signals to the NodeB  Providing two optical interfaces over channelized optical STM-1/OC-3 transmission based on IP protocols  Supporting IP over E1/T1 over SDH/SONET  Providing Multi-Link PPP. boards supporting the IP transmission at the NodeB side are as follows: 2008-09-14 Huawei Confidential Page 14 of 133 . and Iub  Providing 4 unchannelized STM-1/OC-3c optical interfaces  Supporting IP over SDH/SONET  Supporting PPP (LCP/NCP/IPCP)/PPPMUX protocol  Supporting interfaces such as Iu-CS. Iu-PS. At the NodeB side: In V210. and in T1 transmission mode.  Providing 126 E1s or 168 T1s  Supporting interfaces such as Iu-CS. Iur. 42 MLPPP groups are provided. In E1 transmission mode. Iur. and Iub  Obtaining clock signals from the Iu interface and exporting the clock signals to the GCUa/GCGa board  Exporting timing signals to the NodeB 2. Iur. Iu-BC. Iu-BC. Iu-PS.  Universal Transmission Processing unit (UTRP): Provides 8 E1s/T1s. one FE electrical port. The board supports ATM and IP protocols. The following table describes the functions of these boards.4 Functions of NodeB IP transmission boards Board Type WMPT Description Supporting IP over Ethernet and IP over E1/T1/J1 Providing one 4-channel E1 port. and one FE optical port Providing 8-channel IP over PPP/MLPPP over E1/T1 Providing 8 PPP links or 4 MLPPP groups (each MLPPP group contains up to eight MLPPP links) Providing Fractional IP function Providing the timeslot cross-connection function Supporting the line clock extraction Supporting the Iub interface Supporting IP over E1/T1/J1 Providing 8-channel E1/T1 interfaces UTRP Providing 16-channel IP over PPP/MLPPP over E1/T1 Providing 16 PPP links or 4 MLPPP groups (each MLPPP group contains up to 16 MLPPP links) Providing Fractional IP function Providing the timeslot cross-connection function Supporting the line clock extraction Supporting the Iub interface 2008-09-14 Huawei Confidential Page 15 of 133 . Table 2.INTERNAL IPRAN Deployment Guide  WCDMA Main Processing & Transmission unit board (WMPT): Provides one 4-channel E1 port. Supports ATM and IP. one FE electrical port. and one FE optical port. Their messages are transparently transmitted in the M3UA protocol layer as the SCCP payload. TUP.1 M3UA Figure 1. and SCCP messages. The M3UA is applicable to the transmission of the SS7 protocol between the SoftSwitch and signaling gateway (SG).3 Position of the M3UA in each interface protocol stack 2. ISUP. The M3UA provides the conversion between the signaling point code (SPC) and IP address. including but not limited to. DPC.1.INTERNAL IPRAN Deployment Guide Chapter 2 Introduction to Basic Protocols 2. Concepts related to the M3UA: Application server (AS): It serves the logical entity of specific routing keywords. The AS processes the call procedure of all SCN trunks identified by SS7 SIO. and CIC.1 Principles and Relevant Concepts MTP3 User Adaption Layer (M3UA): It is the adaption layer protocol of MTP level-3 users. one or two are in the active state. among them. The M3UA supports the transmission of MTP level-3 user message in the IP network. The AS contains a group of unique AS process. 2008-09-14 Huawei Confidential Page 16 of 133 . OPC. The RANAP is the SCCP user protocol. When a media stream flows from the PS network to the SCN. TUP. or broadcast process of the signaling gateway. and transfers the packed service to the packet-based network. One ASP contains one SCTP endpoint and may be configured to process signaling services in one or more ASs. the IPSP is the same as the ASP. and between IPSPs  Supporting the redundancy protection (active/standby connection or load sharing) between the SG and MGC (or the database in the IP network). or SCCP)  Supporting the seamless interaction of the same MTP3 user protocol in different networks (for example. the system implements the reversal procedure. load-sharing. backup.2 Functions of the M3UA Functions of the M3UA are as follows:  Supporting the transport of all MTP3 user message (ISUP. SCTP stream mapping. 2. Media gateway (MG): When a media stream flows from the SCN to the PS network. Switched Circuit Network (SCN): It is the network carrying services by using the channel with the pre-defined bandwidth. instead of SG services. Signaling gateway process (SGP): It is an instance of the signaling gateway process. and between IPSPs  Supporting the interworking capability of the MTP3 network management function and address translation mapping (SS7<->IP)  Supporting the redundancy management. Essentially.INTERNAL IPRAN Deployment Guide Application server process (ASP): It is the process instance of the AS. Media gateway controller (MGC): The MGC is responsible for processing the resource registration and management on the MG. The SGP is the activation. Signaling gateway (SG): It is the signaling proxy for receiving and sending signaling messages at the edge between the SS7 network and IP network. the MG terminates the SCN media stream and packs media data (if media data is not based on the data packet form). the interaction between the ISUP in the SCN and the ISUP in the IP network)  Supporting the SCTP connection and service management between the SG and MGC (or the database in the IP network). The IPSP uses the point to point M3UA.1. and 2008-09-14 Huawei Confidential Page 17 of 133 . One ASP functions as one active or standby process of the AS. IP server process (IPSP): It is the process instance based on the IP application. the transmission path is related to the destination IP address and the source IP address. a path is determined by the destination address and source address.4 Principle of multi-home Path: It is the route of data transmission. The SCTP supports the 2008-09-14 Huawei Confidential Page 18 of 133 .3 Protocol RFC 3332 2. Figure 1.2 SCTP For the SCTP principles.1. This section describes the multi-homed SCTP.INTERNAL IPRAN Deployment Guide congestion control  Supporting the seamless network management interaction and active connection control 2.1 Principles of Multi-Homed SCTP The multi-homed SCTP means that one device has multiple IP addresses.2. In the IP network.4 Configuration Sequence at the RNC Side The configuration sequence at the RNC side is as follows: (OPC --> N7DPC )--> M3LE --> M3DE --> M3LKS --> M3RT --> M3LNK 2. Actually. see V18 Deployment Guide.1. 2. and the peer system has IP 1 and IP 2. and TRACERT. When the active path is unreachable or the retransmission is required. the system does not send the heartbeat actively. see the RFC2960.4 Multi-homed SCTP Endpoints". UDP. the system selects one active path (active source address and active destination address) for the transport. When one is unavailable. In the case of multiple destination addresses. only two maintenance paths are available. PPP. the endpoint is considered as the multi-homed endpoint. 2. 2. that is. Maintenance path: At present. As shown in Figure 2-2. In the case of the connection setup. In the path that is not maintained. see " 6. Active destination address: The Path is maintained by maintaining the state of the destination address. The active destination address is preferred for sending data.3 Others For the principles of the TCP.2 SCTP Dual-Homed Mechanism Supported by the RNC The multi-homed SCTP supported by V210 RNC refers to two local addresses and two peer addresses. if multiple transport addresses are used as the destination address. NAT. one active destination address is maintained. VLAN.INTERNAL IPRAN Deployment Guide multi-home. see V18 Deployment Guide. 2008-09-14 Huawei Confidential Page 19 of 133 . another path is used. the local system has IP A and IP B.2. 2.2. Multi-homed endpoint: In one endpoint. ARP.3 Protocol For the relevant protocol. multiple IP addresses can be used for the transport. For the dual-homed SCTP. the system finds the next available path through sending the heartbeat. The conservative policy is used. Port backup mode  FG2a and GOUa boards 2008-09-14 Huawei Confidential Page 20 of 133 . the RNC automatically originates the switchover of the active/standby boards. one board is active and the other is standby. without configuring the port backup. When the active board is faulty. the RNC automatically originates the switchover of the active/standby ports. When the active board is faulty.1 Backup Mode at the RNC Side Two backup modes are available in the RNC: board backup and port backup  Board backup In the board backup mode. The service can be processed by the active board or by active and standby boards. If Backup is set to Yes. the board is in the active/standby mode and the port is in the load sharing mode).1. the board backup applies. 1. Board backup mode With the comparison to V29. the RNC automatically originates the switchover of active/standby board. 2. You can set the board backup relation by running ADD BRD. Services are transported through the active port only. one port is active and the other is standby.1 V2 Backup Policy 3.  Port backup In the port backup mode. the board backup and port backup in V210 are independent. If only the board backup is configured. When the active port is faulty. In the board backup mode. one board is active and the other is standby.INTERNAL IPRAN Deployment Guide Chapter 3 Introduction to the Networking 3. The service can be processed by the active board or by active and standby boards (that is. the board is switched over only when the board is faulty. or board and port backup. If the data traffic of the optical interface is large. K2 Mode. the Board and port backup bonding is reduced in the IP interface board for the backup mode in V210. 3. Impact on the system by the switchover When the FG2a/GOUa adopts the board backup without the port backup. The existing service is not interrupted. If the port backup is not configured and only the board backup is configured. With the comparison to V29. one optical port is active. When the FG2a/GOUa adopts the board backup and port backup. The active optical port is responsible for receiving and transmitting data. When FG2a/GOUa boards are set to the board backup.  UOIa_IP and POUa boards When the UOIa is in the board backup mode. run SET MSP. the switchover of the active/standby board has the slight impact on the data transport. WTR Time (required only when Revertive type is set to REVERTIVE). the board backup and port load-sharing mode applies.INTERNAL IPRAN Deployment Guide When the active/standby slots in the RNC subrack are configured with two FG2a/GOUa boards.port not backup. The existing service is not interrupted. In the case of the MSP 1+1 backup of the optical port in the UOIa board. and only Board and port backup apart and the board backup and port load sharing mode are available in V210. When the optical interface of the UOIa is in MSP 1:1 backup. MSP attributes include Revertive type. you can configure the FE/GE port backup by running ADD ETHREDPORT. the corresponding optical ports (for example. To set the relevant attributes of the MSP backup. The settings of these parameters must be consistent with those at the peer end through negotiation. the switchover of the active/standby board has not impact on existing services. one optical interface is active and the other is standby. and the other optical port is standby. and only the active optical port receives data. 2008-09-14 Huawei Confidential Page 21 of 133 . The data processing of the backup mode: The active and standby optical ports send data at the same time. the switchover of the active/standby UOIa board has the slight impact on the data transport. SDSF Priority. The backup mode is MSP 1:1 or MSP 1+1 (single end or dual ends). two FG2a/GOUa boards can be set to Board backup. optical port 0 in the active board and optical port 0 in the standby board) in active/standby UOIa are also backed up. and Backup mode. 2 NodeB Side 1. E1 has the LOS alarm and the FE port is DOWN) and a physical link is available in the standby board. In the case of the switchover. run LST IUBGRP in the LMT. NodeB supports only the board backup mode. the board can be switched over. The specific configuration modes are as follows: 2008-09-14 Huawei Confidential Page 22 of 133 . the active and standby boards are restarted. only the CME can be used to generate the configuration file. the service is interrupted. without supporting the port backup mode In the board backup mode. If the board is not configured to the active/standby mode. data is configured and processed only in the active board. To query the current board mode. When all used physical links in the active board is in the unavailable state (For example.INTERNAL IPRAN Deployment Guide 3. the standby board is upgraded to the active board. When the configurations of the active board are loaded to the standby board. In the configuration of the board backup mode. and the standby board is in the monitoring status. you can perform configurations by running commands.1. In the case of the switchover. INTERNAL IPRAN Deployment Guide 3.2 Common Networking Modes 3. The RNC is 2008-09-14 Huawei Confidential Page 23 of 133 .1 Layer-2 Networking Mode The RNC is connected to the NodeB (Iub interface) through the LAN.2. The RNC is connected to the RNC (Iur interface) through the LAN. The active/standby PEUa board is connected to the peer equipment through the Yshaped E1/T1 cable. The data is 2008-09-14 Huawei Confidential Page 24 of 133 . the following network modes are available: 1. The interface address of each NE is on the same network segment. IP over SDH (Iub interface) Figure 1. 2. According to the transport media. IP over E1/T1 over PDH/SDH (Iub interface) Figure 1.INTERNAL IPRAN Deployment Guide connected to the SGSN (Iu interface) through the LAN. The data is transmitted in the IP over MLPPP or PPP over E1/T1 mode.  Backup mode: The PEUa is set to active/standby board by running ADD BRD.  The NodeB can obtain the line clock over E1/T1. The NodeB accesses the transport network through the E1/T1.6 SDH-based IPRAN L2 networking  The RNC accesses the transport network through the channelized STM-1 on the POUa.  The RNC and NodeB use the header compression algorithm to improve the transport efficiency.5 PDH/SDH-based IPRAN L2 networking  The RNC and NodeB access the transport network through the E1/T1. 3. 2008-09-14 Huawei Confidential Page 25 of 133 .  Transport efficiency: Multiple NodeBs share the VC Trunk bandwidth to use the transport network resources to the maximum extent.1p/q to schedule the QoS of different services. The NodeB accesses the transport network through the FE electrical port or optical port. or obtain the clock source from the GPS/IP Clock Server.1p/q.  The NodeB can extract the clock from the MSTP network over E1/T1. and VLAN Priority.  Backup mode: The FG2a/GOUa is set to the active/standby board.INTERNAL IPRAN Deployment Guide transmitted in IP over MLPPP or PPP over E1/T1 mode.  The RNC and NodeB use the header compression algorithm to improve the transport efficiency. The data is transmitted in the IP over Ethernet mode.  QoS: The RNC and NodeB support the mapping of IEEE 802. DSCP. The transport network supports the IEEE 802. The optical interface in the board is set to MSP 1:1 or MSP 1+1 backup mode.7 MSTP-based IPRAN L2 networking  The RNC accesses the MSTP network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board. port backup (Board and port backup apart) or board backup while the port in the load-sharing mode.  Backup mode: The POUa is set to the active/standby board by running ADD BRD.  NodeB can obtain the line clock over E1/T1. MSTP-based IP networking (Iub interface) Figure 1. and L2 support IEEE 802. The RNC is connected to the RNC (Iur interface) through the L2 data network.  QoS: The RNC. RNC directly connecting to one router The RNC is connected to the NodeB (Iub interface) through the L3 switching network.INTERNAL IPRAN Deployment Guide 4.2 Layer-3 Networking Modes 1. support the VLAN and VLAN priorities for the QoS scheduling of the data network.05% 3. Data network-based IP networking (IUB/IUR/IUCS/IUPS) The RNC is connected to the NodeB (Iub interface) through the L2 data network.1p/q. 2008-09-14 Huawei Confidential Page 26 of 133 . packet loss ratio < 0. The RNC is connected to the SGSN (Iu interface) through the L2 data network. NodeB. core network equipment. that is. jitter < 15ms. Figure 1.2. port backup (board backup separated from port backup) or board backup while the port in the load-sharing mode. The NodeB/NRNC/MGW/SGSN accesses the L2 data network through the FE electrical port or optical port.  The NodeB can extract the clock from the ATM transport network over E1/T1.8 Data network-based IPRAN L2 networking  The RNC accesses the data network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board.  Backup mode: The FG2a/GOUa is set to the active/standby board. The data network must meet the requirements: delay <40ms. or obtain the clock source from the GPS/IP Clock Server. The interface address of the interconnected NE is on the same network segment.  Backup mode: The FG2a/GOUa is in the board backup and port backup. MPLS Diffserv. jitter < 15ms.  QoS: The RNC. The interface address of each NE is in different network segments. NodeB. and core network equipment support the mapping of IEEE 802.1p/q. Figure 1. The NodeB/NRNC/MGW/SGSN accesses the transport network through the FE electrical port or optical port. The data network supports the MPLS TE. and VLAN Priority. One VLAN interface address is configured as the RNC gateway.9 L3 networking of RNC directly connecting to one router  The RNC accesses the data network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board. The data network must meet the requirements: delay <40ms. IP Diffserv. The active and standby ports are connected to two ports of one router/L3 switch.05% 2008-09-14 Huawei Confidential Page 27 of 133 . The data is transmitted in the IP over Ethernet mode. The two ports in the router/L3 switch are configured in the same VLAN. and VLAN COS to schedule the service QoS. packet loss ratio < 0. or obtain the clock source from the GPS/IP Clock Server. DSCP. The RNC is connected to the RNC (Iur interface) through the L3 switching network.  The NodeB can extract the clock over E1/T1.INTERNAL IPRAN Deployment Guide The RNC is connected to the SGSN (Iu interface) through the L3 switching network.  Backup mode: The FG2a/GOUa is in the board backup and port backup. Two ports of the active and standby PE are configured in the same VLAN.  QoS: The RNC. RNC directly connecting to two routers Figure 1. The NodeB/NRNC/MGW/SGSN accesses the transport network through the FE electrical port or optical port. or obtain the clock source from the GPS/IP Clock Server. The data network supports the MPLS TE. with the configuration of the VRRP. The VRRP virtual IP (IP-0) functions as the RNC gateway. packet loss ratio < 0.  The NodeB can extract the clock over E1/T1. IP Diffserv.10 L3 networking of RNC directly connecting to two routers  The RNC accesses the data network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board. The active and standby ports of RNC are respectively connected to two ports of the active and standby PEs. The active and standby ports of the RNC share one IP address (IP1-1). The RNC is connected to the data transport network through the PE. and VLAN Priority.INTERNAL IPRAN Deployment Guide 2. The board backup and port backup are independent of each other. MPLS Diffserv. The data network must meet the requirements: delay <40ms. DSCP. and VLAN COS to schedule the QoS of different services. The data is transmitted in the IP over Ethernet mode.1p/q.05% 2008-09-14 Huawei Confidential Page 28 of 133 . and core network equipment support the mapping of IEEE 802. NodeB. jitter < 15ms. Two ports in the FG2a/GOUa are respectively configured with the IP address.  Route with the load sharing: Multiple different NEXTHOP routes exist in the network segment to the same destination. The data network supports the MPLS TE. with the corresponding gateway in the interconnected router/L3 switch. NodeB.  The NodeB can extract the clock over E1/T1.  The load sharing is in the load sharing mode to ensure the correct time sequence of user flows. The NodeB/NRNC/MGW/SGSN accesses the transport network through the FE electrical port or optical port. DSCP.  Through the routing configuration. 2008-09-14 Huawei Confidential Page 29 of 133 . and core network equipment support the mapping of IEEE 802. Load sharing Figure 1. The double bandwidths are obtained with the reliability guarantee of the board and transport. or obtain the clock source from the GPS/IP Clock Server.  Traffic in the route with the load sharing is distributed on average.1p/q. and VLAN Priority. The data is transmitted in the IP over Ethernet mode.  Backup mode: The FG2a/GOUa is in the board backup and the port is in the load sharing mode.  QoS: The RNC.11 L3 networking with the load sharing  The RNC accesses the data network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board. the IP load sharing is implemented between any active FE/GE ports.INTERNAL IPRAN Deployment Guide 3. Two ports of the active and standby boards in the load sharing are connected to two routers/L3 switch. PEUa/POS/UOI_IP is the board backup. and VLAN COS to schedule the QoS of different services.INTERNAL IPRAN Deployment Guide MPLS Diffserv.  The RNC accesses the data network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board. with the port backup or port load sharing mode. RNC and NodeB access the TDM transport network over E1/T1.  Backup mode: The FG2a/GOUa is in the board backup. The data is transmitted in IP over Ethernet mode. Ethernet). packet loss ratio < 0.12 IPRAN networking in the hybrid transport . jitter < 15ms. 2008-09-14 Huawei Confidential Page 30 of 133 . The data is transmitted in IP over MLPPP/PPP over E1/T1 mode.Iub  The Iub interface uses the transport network of different QoSs to carry services of different QoSs: The service with high QoS is transported through the dedicated line. The NodeB/NRNC/MGW/SGSN accesses the transport network through the FE electrical port or optical port.  The NodeB can extract the clock through additionally over E1/T1.  The control plane and real-time services and OM services are transported through the TDM with the high QoS.05% 3.2. The service with low QoS is transported through the low cost transport network (for example.  Non real-time services are transported through the data network with low QoS. IP Diffserv.3 Hybrid Transport Networking TDMnetwork Datanetwork Figure 1. The data network must meet the requirements: delay <40ms. the IP transport network can be extended. The RNC accesses the data network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board.4 ATM/IP Dual-Stack Transport Networking Figure 1.3.13 IPRAN networking in the ATM/IP dual-stack transport . The NodeB/NRNC/MGW/SGSN accesses the transport network through the FE electrical port or optical port. 3) After the active/standby Ethernet ports are configured.1 RNC 1) In the separate mode. The data is transmitted in IP over Ethernet mode  The NodeB can extract the clock over E1/T1.INTERNAL IPRAN Deployment Guide 3. The RNC and NodeB access the TDM transport network through the E1/T1. the corresponding 2008-09-14 Huawei Confidential Page 31 of 133 .  Backup mode: see L2 data networking and L3 data networking. 3.Iub  When the bandwidth in the original ATM networking is deficient (in the case of the HSDPA/HSUPA).  QoS: The control plane and real-time services and OM services are transported through the ATM.  The RNC and NodeB access the data transport network through the new IP interface board.3 Backup Constraint 3.2. the route must be configured in even slots.  The original ATM networking remains unchanged. The non real-time service is transported through the IP. The transport cost is saved and the bandwidth is improved. 2) The backup mode should not be configured in odd slots. Chapter 4 V210 IPRAN Key Configurations 4.1 RNC Side 1. Command: SET ETHPORT  Set the VLAN tag attribute of the Ethernet port The VLAN tag attribute of the Ethernet port cannot be set. The gateway continuity check can be started. the service is interrupted in the case of the switchover.3.1. 4) The backup port should not be used. NDTI does not support. //Set the FE port of the FG2 board to Auto negotiation or forced 100M/Full. Hence. By default. the slot with the smaller ID in the backup group is the active board in the initial configuration. By default.1 Relevant Settings of the IPRAN 4. the setting is HYBRID. data is configured only in the active board. 5) When at least either of the active and standby ports is configured with IP or port control. 3. 3) In the backup mode. two ports are not allowed to be configured as the active and standby ports. 2) The code backup is performed in the NodeB.  Set the work mode of the FE/GE port: The work mode at both ends for the interconnection must be consistent. Set the Ethernet port attribute. 2008-09-14 Huawei Confidential Page 32 of 133 .INTERNAL IPRAN Deployment Guide ports of the active/standby boards function as the active/standby ports.2 NodeB: 1) Boards supporting the board backup: V210: WMPT/UTRP V110: NUTI/HBBU. 47 5 48 . Set the MTU. //Set the GE port of the GOUa board to non-auto negotiation. PTYPE=FE/GE. MTU=1500. SET ETHPORT: SRN=0. PTYPE=FE. SET ETHPORT: OAMFLOWBW=0. BRDTYPE=GOU. PN=0. SN=14. The default mapping relation is as follows: 2008-09-14 DSCP VLAN Priority 0-7 0 8 . PTYPE=FE/GE. FESPEED=100M. BRDTYPE=FG2. The default value is 1000M/FULL. SET ETHPORT: SRN=0. BRDTYPE=FG2/GOU. PN=0. //Set the GE port of the GOUa board to Auto negotiation. The value can be changed according to the planning of the current network. SN=14.55 6 56 . PTYPE=GE. By default. the value is 1000M/FULL. By default. BRDTYPE=GOU. SET ETHPORT: AUTO=DISABLE. PN=0.39 4 40 . VLANPRI=X. //The work mode of the GE port of the FG2 board cannot be configured. Command: SET DSCPMAP SET DSCPMAP: DSCP=X. BRDTYPE=FG2.23 2 24 . the value is 1500 bytes. AUTO=DISABLE. SN=14.INTERNAL IPRAN Deployment Guide SET ETHPORT: SRN=0. DUPLEX=Full. the value is 0%. BRDTYPE=FG2/GOU. 2. SN=14.  SRN=0.  SN=14. PTYPE=FE. SRN=0. SN=14. which cannot be modified. SET ETHPORT: SRN=0. Set the percentage of the OAM minimum assurance bandwidth to the port bandwidth. By default. PTYPE=GE. AUTO=ENABLE. AUTO=ENABLE.63 7 Huawei Confidential Page 33 of 133 . PN=0.31 3 32 . Set the mapping between the DSCP and VLAN PRI.15 1 16 . OAMFLOWDSCP=X. Q2MINDSCP= XX. but transported through private queues. Q3MINDSCP= XX. The default setting is as follows: The mapping between the DSCP value range and Q0-Q5 is as follows: DSCP QUEUE ID 40 .63 0 32 . The priorities of each queue are different. the DSCP of 2008-09-14 Huawei Confidential Page 34 of 133 . By default.15 4 0-7 5 Note: 1) The IP port types include Ethernet port.39 1 24 . the value is OFF. 2) Q0MINDSCP . SN=14. Set the DSCP value of the OAM flow SET QUEUEMAP: SRN=0. Q0 features the highest priority. 2) If the minimum assurance bandwidth switch of the OAM flow is enabled. Q5 features the lowest priority.Q4MINDSCP must meet the following conditions: Q0MINDSCP > Q1MINDSCP > Q2MINDSCP > Q3MINDSCP > Q4MINDSCP 4. Set the mapping between the queue of the IP type port and the DSCP SET QUEUEMAP: Q0MINDSCP=XX. MP group. OAMMINBWKEY=ON.INTERNAL IPRAN Deployment Guide 3. Note: 1) The OAM flow cannot be transported through Q0-Q5. PPP link. Each IP type port has six service data queues.23 3 8 . Q4MINDSCP= XX. and IP logical port. Q1MINDSCP= XX.31 2 16 . VLANFlAG=ENABLE. VLANID=X. Set the corresponding DSCP of the IPPATH and whether to enable the VLAN. ADD IPPATH: PATHT=X.X.X". Default configurations: DSCP=62. The VLAN is not enabled. the following two purposes are achieved by running this command: 1) IP packets sending to the destination IP address are labeled with the designated VLAN 2008-09-14 Huawei Confidential Page 35 of 133 . VLANID=X. The default setting is as follows: IPPATH Type DSCP HQ_RT 46 LQ_RT 34 HQ_NRT 18 LQ_NRT 10 HQ_HSDPART 38 LQ_HSDPART 30 HQ_HSDPANRT 14 LQ_HSDPANRT 4 HQ_HSUPART 36 LQ_HSUPART 28 HQ_HSUPANRT 12 LQ_HSUPANRT 0 HQ_QOSPATH Null LQ_QOSPATH The value is determined according to the configuration in the TRMMAP. Set the corresponding DSCP of the SCTP link and whether to enable the VLAN. 6.X. DSCP=X. 5. ADD SCTPLNK: DSCP=X. VLANID=X. If the VLAN is not enabled in Steps 5 and 6. Add the mapping between the destination IP and VLANID ADD VLANID: IPADDR="X.INTERNAL IPRAN Deployment Guide the designated OAM flow should not be identical with the DSCP value of any IPPATH. VLANID Flag Disable Disable Disable Disable Disable Disable Disable 7. VLANFlAG=ENABLE. AF12 DSCP=X. AF42 DSCP=X. AF22 DSCP=X. AF33 DSCP=X. TRANST=IP.2 NodeB Side 1.INTERNAL IPRAN Deployment Guide ID. AF23 DSCP=X. AF21 DSCP=X. BEDSCP=X. AF31 DSCP=X. 8. 2) ARP request packets of the destination IP address are labeled with the designated VLAN ID. Set the Ethernet port attribute Command: SET ETHPORT Set the work mode of the FE port: The work mode at both ends for the interconnection must be consistent. AF13 DSCP=X. AF11 DSCP=X. AF41 DSCP=X.1. 2008-09-14 Huawei Confidential Page 36 of 133 . AF43 DSCP=X. AF32 DSCP=X. The default mapping relation is as follows: PHB DSCP EF AF4 AF3 AF2 AF1 46 AF43 38 AF42 36 AF41 34 AF33 30 AF32 28 AF31 26 AF23 22 AF22 20 AF21 18 AF13 14 AF12 12 AF11 10 BE 0 4. EFDSCP=X. Set the mapping between the PHB and DSCP ADD TRMMAP: ITFT=IUB_IUR_IUCS/IUPS. 4) HSDPA Data from the RNC to the NodeB is the downloaded data.DSCP Signal Priority Value range: 0 .7: when PRIRULE is IPPRECEDENCE.7: when PRIRULE is IPPRECEDENCE.INTERNAL IPRAN Deployment Guide 2. The DSCP settings are determined by the RNC. 0 . 2) Common channel The common channel transports control information. data from the RNC to the NodeB is transmitted through the DSCP on the RT PATH. service. with the higher priority. For services in the common channel. OM Priority Value range: 0 .63: when PRIRULE is DSCP. The priority is equivalent to the NCP/CCP data. The DSCP value of the HSDPA_IPPATH configured by the RNC determines the DSCP for the data transmitting. Set the priority of the signaling and OM Command: SET DIFPRI Related parameters are as follows: Name Description Priority Rule Value range: IPPRECEDENCE. When the connection is established. the RNC notifies the NodeB. The data returned from the NodeB to the RNC is transmitted through the DSCP of the Signal Priority by running SET DIFPRI. and DSCP values are as follows: 1) Iub interface signaling data Signaling data over Iub interface is transported with SCTP. The flow control information frame returned from the NodeB to the RNC is uploaded by using the DSCP value of the Signal Priority configured by running SET DIFPRI. 5) HSUPA The data from the NodeB to the RNC and data from the RNC to the NodeB are transmitted by using the DSCP value sent in the case of the RNC link setup. 2008-09-14 Huawei Confidential Page 37 of 133 . The sending of the DSCP priority in the SCTP protocol package is determined by the DSCP in the Signaling Priority type by running SET DIFPRI. The relations between the signaling. 3) R99 service (user voice and PS network access data) The NodeB sends the DSCP priority of these UDP packages.63: when PRIRULE is DSCP. 0 .  TRAFFIC=SIG. INSTAG=ENABLE.INTERNAL IPRAN Deployment Guide 6) OM maintenance data The OM maintenance data is transported through the TCP. The IPPRECEDENCE is labeled by using the priority field in the type of service (TOS) field in the IP header. 3. It corresponds to USERDATA class by running the command SET VLANCLASS. SET VLANCLASS: VLANGROUPNO=X. VLANPRIO=X. the VLANIDs vary with protocol types. It applies to data of common channels. The recommended configuration is DSCP. Set the configuration between the DSCP and VLAN Command: SET VLANCLASS In the VLAN configurations. PS network access. DSCP range: [A. the local UDP port number is in the legal range of the NodeB. The DSCP is configured according to the DSCP value of the Diffserv.B) Specific value: I PPRECEDENCE DSCP 0 000000~001000 1 001000~010000 2 010000~011000 3 011000~100000 4 100000~101000 5 101000~110000 6 110000~111000 7 111000~111111 2) The SIG precedence is configured to be consistent with the DSCP value of the SCTP in the RNC. Precautions for the configuration: 1) Priority Rule: It has two options: IPPRECEDENCE and DSCP. VLANID=X. The NodeB distinguishes according to the following rules:  Protocol type = SCTP: Iub interface signaling data includes only the NCP/CCP data. Correspond to the SIG class by running the command SET VLANCLASS. The sending of the DSCP priority in the packages is determined by the DSCP in the OM type by running SET DIFPRI. In addition. and H download. One IPPRECEDENCE corresponds to a range of the DSCP value. 2008-09-14 Huawei Confidential Page 38 of 133 . Protocol type = UDP: Voice. INSTAG=ENABLE. It corresponds to the OM class by running the command SET VLANCLASS.14.14. VLANPRIO=X. It corresponds to OTHER class by running the command SET VLANCLASS. VLANPRIO=1. TRAFFIC=USERDATA. SET VLANCLASS: VLANGROUPNO=X. VLANID=X. the uplink control frame of the HSDPA use the DSCP value of the SIG type by running the command SET DIFPRI. TRAFFIC=OTHER. VLANMODE=SINGLEVLAN. It is other applications (for example. all data with the same next hop address is labeled with the VLAN. It corresponds to the OM class by running the command SET VLANCLASS. Hence.13.INTERNAL IPRAN Deployment Guide SET VLANCLASS: VLANGROUPNO=X. INSTAG=ENABLE. 2008-09-14 Huawei Confidential Page 39 of 133 . The configuration methods are as follows: 1) All data is labeled with the same VLAN. When running the command ADD VLANMAP. VLANID=100. The value is treated as other types. VLANID=X. TRAFFIC=OM.13. Protocol type = TCP: Data of OM management and maintenance. The signaling uses the SCTP. VLANPRIO=0. 2) Label different VLANs according to data types When running the command ADD VLANMAP. and DHCP.  Protocol type = UDP: The local UDP port number is not in the legal range of the NodeB. INSTAG=ENABLE. the VLANs should be set respectively. The uplink frame of the common channel and the uplink control frame of the HSDPA use the UDP. ADD VLANMAP: VLANGROUPNO=0. INSTAG=ENABLE. According to the correspondence between the service and DSCP. run SET VLANCLASS. select VLANGRP for the VLANMODE. TRACERT).15". VLANPRIO=X. SET VLANCLASS: VLANGROUPNO=X. 4. VLANID=X. Set the VLAN based on the next hop (V210) Command: ADD VLANMAP Set the VLANID based on the next hop (V210). uplink frame of the common channel. ICMP.  SRVPRIO=X. ARP. but not limited to.15". NEXTHOPIP="12. VLANMODE=VLANGROUP. That is. Protocol type = Others: Includes. the signaling at the NodeB side. ADD VLANMAP: NEXTHOPIP="12. To set the VLAN in the VLANGRP. select the single VLAN for the VLANMODE. VLANID=2. 4. Note: V110 does not support the label of the VLAN based on the next hop. Enable the VLANTAG by running the command SET ETHPORT.INTERNAL IPRAN Deployment Guide 5. VLANPRIO=5. VLAN configuration of the signaling: SET VLANCLASS: VLANGROUPNO=0. the command ADD VLANMAP does not apply. Then. Constraints of RNC IP address network segment: 1. user plane IP address.*. RNC internal subnet segment. INSTAG=ENABLE.255. TRAFFIC=USERDATA. All Ethernet port address (ETHIP) in the RNC interface board should not be on the same network segment.1 Constraints of RNC IP Address The interface IP address.*. 4. use one value in the DSCP range corresponding to the IPPRCEDENCE by running the command SET VLANCLASS.2. run the command SET VLANCLASS. SIGPRI=48.*. The configuration method is the same as that by running the command SET VLANCLASS in V210. 127. RNC debug subnet segment (by running the command SET SUBNET. The default network segment is 192). VLAN configuration of the uplink frame of the common channel and the uplink control frame of the HSDPA SET VLANCLASS: VLANGROUPNO=0. OMPRI=20. The device IP address (DEVIP) of the same interface board in the RNC should not be on the same network segment.2 Constraint and Restrictions of IP Address and Configuration This section describes current constraints on the IP transport configurations. TRAFFIC=SIG.255. Example SET DIFPRI: PRIRULE=DSCP. and M2000 network segment. INSTAG=ENABLE.255. VLANPRIO=6. VLANID=100. data is planned according to the constraints. In the networking.*. The device IP address (DEVIP) and ETHIP of the same interface board in the RNC 2008-09-14 Huawei Confidential Page 40 of 133 . BAM internal/external network segment. 2. SRVPRIO=48. If the priority rule by running the command SET DIFPRI is IPPRECEDENCE. and control plane IP address should not be 0.*. therefore. 255.*. 3. which can be on the same network segment.x (internal restricted address in the RAN6.255. The local IP address of the MLPPP group and PPPLNk should not be the same as the local address in the RNC. The local address should not be the same as the configured interface address in the NodeB.1. 4. user plane address. 127.22. local/peer IP address of the MLPPP group. The peer addresses such as the MLPPP group and PPPLNK should not be the same as the configured address in the NodeB. and 10. The addresses of different interfaces should not be on the same network segment.*.*. 5. SCTP link peer address) in the RNC.0 NodeB). 255. PPP port IP address. ETH gateway. IPPATH peer address. Chapter 5 Example of Iub Interface Configuration 5. and the device IP address) in the RNC.2.*. The Ethernet port IP address should not be the same as the configured IP address (including local/peer IP address of the PPP link. 6.255.INTERNAL IPRAN Deployment Guide should not be on the same network segment. The peer address should not be the same as the local address in the RNC.1 Version Description RNC version: V210060 2008-09-14 Huawei Confidential Page 41 of 133 . The interface address and the maintenance address may be on the same network segment. Ethernet port IP address. or maintenance address should not be 0. ETH port address. Constraints of NodeB IP address network segment: One interface can be configured with up to four IP addresses. local/peer IP address of the MLPPP group.2 Constraints of NodeB IP Address The NodeB interface address. The device IP address should not be the same as the configured IP address (including local/peer IP address of the PPP link.*.*. and logical IP address) in the RNC. 4.*.255. or the same as the peer address (for example. control plane address. Figure 1. or IP hybrid transport The IP transport solutions vary with transport networks used in the Iub interface. Data is configured from the control plane to the user plane.INTERNAL IPRAN Deployment Guide 5. that is. the compliant sequence in adding Iub interface data should be consistent with the protocol structure. from the lower layer to the upper layer.3 Data Planning In the case of the IP transport.2 IUB Interface Protocol Stack In the case of the Iub over IP. 2008-09-14 Huawei Confidential Page 42 of 133 . private line-based transport. Before configuring IP-based Iub interface data.14 Iub interface protocol stack 5. the interconnected data (unless otherwise specified) of the Iub interface is obtained through the negotiation between the RNC and the NodeB. The following figure shows IP-based protocol stack of the Iub interface. confirm the following information: • L2 networking or L3 networking • Ethernet-based transport. 1/24 10.2/24 Master address/slave address - - FE Interface port type data Gateway address board IP IP IP port Network planning 2. Data planning of control plane Data Item NCP RNC NodeB IUB congestion control switch OFF OFF NodeB Max Hsdpa User Number 3840 3840 58080 9000 Local SCTP Port No.3. For the data planning of PPP/MLPPP.1 Data Planning in L2 Networking This section describes the data planning in the case of the use of the FE.INTERNAL IPRAN Deployment Guide 5. 1.10.2/24 Second address - - local 2008-09-14 IP Huawei Confidential Data Source Negotiation data Page 43 of 133 . SCTP signaling link Server mode Client SPU Slot No.10. Data planning of physical layer and data link layer Data Item RNC Side NodeB Data Source FG2/GOUa WMPT Internal planning 10.10. 0 - SPU Subsystem No.10. 0/18/0 0/6/0 Port IP address/subnet mask 10. 0 - DSCP 62 62 First local IP address 10./Port No.10.10.10.3.10.10.10.10.3. backup No Internal planning Subrack No. see section 7.1/24 Network planning Whether to backup/backup mode Yes/Board backup.10.2/24 10./Slot No.1/24 10. 10. 0 0 SPU Slot No. and port No. Yes/18/20 - Local IP address/subnet mask 10.INTERNAL IPRAN Deployment Guide Whether to bind Yes/18/20 logical port/logical port slot No.2/24 Huawei Confidential Negotiation data IPv4 Port type 2008-09-14 Data Source Network planning Page 44 of 133 . Data planning of user plane Data Item RNC NodeB name RNC8-BBU1 BBU1 Transport Neighbor Node ID 1 1 IP Protocol Version IP path 1 NodeB IPv4 Network planning Negotiation data Eth Eth IP Path flag 1 1 PATH Type RT RT Whether to bind logical port/logical port slot No.10. and port No.2/24 Second address - - local IP Whether to bind Yes/18/20 logical port/logical port slot No.10.10.10.1/24 10. CCP 58080 9001 SCTP signaling link Server mode Client Port No. 0 - SPU Subsystem No. and port No. - Whether to VLAN/VLAN ID 10 add 10 3. - Whether to VLAN/VLAN ID 10 add 10 Local SCTP Port No.1/24 10.10.10.10. 0 - DSCP 62 62 First local IP address 10. 2/24 Use VLAN or not/Enabled VLAN ID YES/VLAN10 YES/VLAN10 PATH check flag ENABLE - Check IP address 10.1/24 10.2/24 - DSCP 46 46 Transmit (kbps) bandwidth 20000 20000 Receive (kbps) bandwidth 20000 20000 FPMUX Enable NO NO Port type Eth Eth IP Path flag 2 2 PATH type NRT NRT Whether to bind logical port/logical port slot No.10.INTERNAL IPRAN Deployment Guide Data Item IP path2 IP path 3 RNC NodeB Use VLAN or not/Enabled VLAN ID YES/VLAN10 YES/VLAN10 PATH check flag ENABLE - Check IP address 10. Yes/18/20 - Local IP address/subnet mask 10.2/24 - DSCP 18 18 Transmit (kbps) bandwidth 20000 20000 Receive (kbps) bandwidth 20000 20000 FPMUX Enable NO NO Port type Eth Eth IP Path flag 3 3 PATH type HSDPANRT HSDPANRT Whether to bind logical port/logical port slot No.10.10.10.10. and port No.10.10.10. Yes/18/20 - 2008-09-14 Huawei Confidential Data Source Internal planning Negotiation data Network planning Internal planning Negotiation data Page 45 of 133 . and port No. 10.10. Data planning of management plane Data Item 2008-09-14 RNC NodeB Huawei Confidential Data Source Page 46 of 133 .INTERNAL IPRAN Deployment Guide Data Item IP path 4 RNC NodeB Local IP address/subnet mask 10.1/24 10.10. and port No.10.10.10. Yes/18/20 - Local IP address/subnet mask 10.10.10.10.10.2/24 - DSCP 10 10 Transmit (kbps) bandwidth 20000 20000 Receive (kbps) bandwidth 20000 20000 NO NO FPMUX Enable Data Source Network planning Internal planning Negotiation data Network planning Internal planning 4.10.10.1/24 10.2/24 - DSCP 10 10 Transmit (kbps) bandwidth 20000 20000 Receive (kbps) bandwidth 20000 20000 FPMUX Enable NO NO Port type Eth Eth IP Path flag 4 4 PATH type HSUPANRT HSUPANRT Whether to bind logical port/logical port slot No.2/24 Use VLAN or not/Enabled VLAN ID YES/VLAN10 YES/VLAN10 PATH check flag ENABLE - Check IP address 10.2/24 Use VLAN or not/Enabled VLAN ID YES/VLAN10 YES/VLAN10 PATH check flag ENABLE - Check IP address 10. IP addresses planning The following figure shows the Ethernet-based IP planning.3.10.242/24 network IP address - IP address M2000 Server - of 10. enable the ARP proxy function of the interface) - Interface IP address at NodeB side 10. Figure 1.10. The DEVIP should not be configured and used.2/24 at RNC side - Interface IP address 10.10.10.161. and indicates only the configuration and usage of the DEVIP.1/24 Gateway IP address 10.10.10.10.215.2 Data Planning in L3 Networking 1. In the example.3/24 (If NodeB OMIP and the interface IP are on the same network segment.215.INTERNAL IPRAN Deployment Guide OMIP address at NodeB side 10.10.10. the ETHIP of the FG2 can be used directly.2/24 Gateway IP address at NodeB side 10. If the load-sharing mode is not used and only one IP address is used at the RNC side.15 IP planning of Ethernet-based L3 networking 2008-09-14 Huawei Confidential Page 47 of 133 . the DEVIP used in the SCTP and IPPATH local address is optional.10.1/24 at RNC side - BAM external 10.230/24 Network planning 5.161. 1/26 16.16.10.16.10.INTERNAL IPRAN Deployment Guide 2.16.16.16.10. 0/18/0 0/6/0 Port IP address/subnet mask 10. Data planning of control plane RNC Data Item IUB congestion switch NodeB control OFF OFF NodeB Max Hsdpa User Number 3840 3840 Port 58080 9000 SCTP signaling link mode Server Client SPU Slot No.10.2/26 Master address/slave address - - IP IP Data Source port Network planning 3.10. 0 - SPU No./Slot No./Port No.16. SCTP Subsystem DSCP First local address IP 10. backup Subrack No.100/26 16.1/26 Network planning No Internal planning Backup/backup mode Yes/Board backup. Data planning of physical layer and data link layer Data Item FE por t dat a RNC Side Interface type board Gateway address IP NodeB FG2/GOUa WMPT Internal planning 10.10.2/26 Second address IP - - local 2008-09-14 Huawei Confidential Data Source Negotiation data Page 48 of 133 .2/26 16. 0 - 62 62 NCP Local No. 16.2/26 Second address IP - - Whether to bind logical port/logical port slot No. 0 - SPU No. port 58080 9001 SCTP signaling link mode Server Client Port No. Yes/18/20 - Whether to add VLAN/VLAN ID - - Local No. Yes/18/20 - 2008-09-14 Huawei Confidential Negotiation data Page 49 of 133 .10. 0 0 SPU Slot No.10.100/26 16.INTERNAL IPRAN Deployment Guide CCP Whether to bind logical port/logical port slot No. 0 - 62 62 SCTP Subsystem DSCP First local address IP 10.16. Yes/18/20 - Whether to add VLAN/VLAN ID - - local 4. and port No. and port No. Data planning of user plane RNC Data Item IP path 1 NodeB Data Source NodeB name RNC8-BBU1 BBU1 Transport Neighbor Node ID 1 1 IP Protocol Version IPv4 IPv4 Network planning Port type Eth Eth IP Path flag 1 1 Negotiation data PATH Type RT RT Whether to bind logical port/logical port slot No. and port No. 100/26 16.16.16.10.100/26 16.10. Yes/18/20 - Local IP address/subnet mask 10.INTERNAL IPRAN Deployment Guide Data Item 10.16.2/26 Use VLAN or not/Enabled VLAN ID - - PATH check flag ENABLE - Check IP address 16.2/26 - DSCP 46 46 bandwidth 20000 20000 Receive bandwidth (kbps) 20000 20000 FPMUX Enable NO NO Port type Eth Eth IP Path flag 2 2 PATH type NRT NRT Whether to bind logical port/logical port slot No. and port No.16.16.10.16.10.16.2/26 - DSCP 18 18 bandwidth 20000 20000 Receive bandwidth (kbps) 20000 20000 FPMUX Enable NO NO Port type Eth Eth IP Path flag 3 3 PATH type HSDPANRT HSDPANRT Whether to bind logical port/logical port slot No.16.2/26 Use VLAN or not/Enabled VLAN ID - - PATH check flag ENABLE - Check IP address 16. and port No. Yes/18/20 - Transmit (kbps) IP path 3 NodeB Local IP address/subnet mask Transmit (kbps) IP path2 RNC 2008-09-14 Huawei Confidential Data Source Network planning Internal planning Negotiation data Network planning Internal planning Negotiation data Page 50 of 133 . 16.16.16.16. Data planning of management plane Data Item 2008-09-14 RNC NodeB Huawei Confidential Data Source Page 51 of 133 .16.100/26 16.16.16.2/26 Use VLAN or not/Enabled VLAN ID - - PATH check flag ENABLE - Check IP address 16. Yes/18/20 - Local IP address/subnet mask 10.16. and port No.2/26 - DSCP 10 10 bandwidth 20000 20000 Receive bandwidth (kbps) 20000 20000 FPMUX Enable NO NO Port type Eth Eth IP Path flag 4 4 PATH type HSUPANRT HSUPANRT Whether to bind logical port/logical port slot No.INTERNAL IPRAN Deployment Guide Data Item NodeB Local IP address/subnet mask 10.10.10.2/26 - DSCP 10 10 bandwidth 20000 20000 Receive bandwidth (kbps) 20000 20000 FPMUX Enable NO NO Transmit (kbps) IP path 4 RNC Transmit (kbps) Data Source Network planning Internal planning Negotiation data Network planning Internal planning 5.10.10.2/26 Use VLAN or not/Enabled VLAN ID - - PATH check flag ENABLE - Check IP address 16.100/26 16. IP addresses planning The RNC and NodeB (3X1) access the SDH optical transport network through the Add/Drop Multiplexer (ADM) respectively. The RNC is connected to the NodeB through the SDH or Plesiochronous Digital Hierarchy (PDH) transport network. E1/T1 NodeB1 ADM PDH/SDH ADM E1/T1 BSC6800 Ethernet Figure 1.1/26 Gateway IP address 10. signaling and real-time services are transmitted through the PPP.10. the RNC and NodeB access the Ethernet (L3 networking).16. enable the ARP proxy function of the interface) - Interface IP address at NodeB side 16.9/26 (If NodeB OMIP and the interface IP are on the same network segment.215.215.161.16.161. Meanwhile.230/24 Network planning 5.10.10.9.10.2/26 at RNC side - BAM external 10. 1.9.INTERNAL IPRAN Deployment Guide OMIP address at NodeB side 9.16.1/26 at RNC side - Interface IP address 10.2/26 Gateway IP address at NodeB side 16.16 IP RAN hybrid transport networking 2008-09-14 Huawei Confidential Page 52 of 133 .3. and BE services are transmitted through the FE.242/24 network IP address - IP address M2000 Server - of 10.16.3 Data Planning of Hybrid Transport Networking In the case of the hybrid transport. 16. Data planning of physical layer and data link layer Data Item FE port data RNC Side NodeB Data Source Interface board type FG2/GOUa WMPT Internal planning Gateway IP address 10.10.2/26 16. Figure 1./Port No.1/26 Network planning Backup/backup mode Yes/Board backup separated from port backup No Subrack No. Figure 1.10.10.18 E1-based IP planning 2.16.INTERNAL IPRAN Deployment Guide The following figure shows the Ethernet-based IP planning.16.10. 0/18/0 0/12/0 Port address/subnet mask 10.16.2/26 2008-09-14 IP Huawei Confidential Internal planning Network planning Page 53 of 133 .1/26 16./Slot No.17 IP planning of Ethernet-based L3 networking The following figure shows the E1-based IP planning. /Slot No. SPU No.13.13.13. 0/14/0 0/12/0 MLPPP group No.1/24 13.2/24 Network planning Bearer timeslot TS1&TS2&TS3 TS1&TS2&TS3 Negotiation data &TS4&TS5&TS6 &TS4&TS5&TS6 Link data Internal planning The settings are not required when the RNC uses UOI_IP and POUa.13./E1T1 Port No.1/24 13.2/24 Second address IP - - local 2008-09-14 Huawei Confidential Data Source Negotiation data Page 54 of 133 . 3. - - PPP/MLPPP link No.13. Subsystem DSCP First local address IP 13. subnet mask 13.INTERNAL IPRAN Deployment Guide Data Item RNC Side Master address/slave address IP IP NodeB - - Data Source PPP Interface board type PEU/UOI_IP/POUa WMPT /MLPPP Gateway IP address - - Link PPP Subrack No. 0 0 Local IP address.13. SCTP SPU Slot No.13.13. Data planning of control plane RNC Data Item NCP NodeB Iub congestion control switch OFF OFF NodeB Hsdpa Number Max User 3840 3840 Port 58080 9000 SCTP signaling link mode Server Client 0 - 0 - 62 62 Local No. 13. port 58080 9001 SCTP signaling link mode Server Client Port number 0 0 0 - 0 - 62 62 SCTP SPU Slot No. and port No.13. - - Whether to add VLAN/VLAN ID - - Local No.13.2/24 Second address IP - - Whether to bind logical port/logical port slot No.INTERNAL IPRAN Deployment Guide CCP Whether to bind logical port/logical port slot No. - - Whether to add VLAN/VLAN ID - - local 4.1/24 13. and port No. SPU No. and port No. - - 2008-09-14 Huawei Confidential Negotiation data Page 55 of 133 . Subsystem DSCP First local address IP 13. Data planning of user plane RNC Data Item IP path 1 NodeB Data Source NodeB name RNC8-BBU1 BBU1 Transport neighbor node flag 1 1 IP protocol version IPv4 IPv4 Network planning Port type PPP PPP IP Path flag 1 1 Negotiation data PATH type RT RT Whether to bind logical port/logical port slot No.13. 16.10.2/26 - DSCP 18 18 Transmit (kbps) bandwidth 20000 20000 Receive (kbps) bandwidth 20000 20000 FPMUX Enable NO NO Port type Eth Eth IP Path flag 3 3 PATH type HSDPANRT HSDPANRT 2008-09-14 Huawei Confidential Data Source Network planning Internal planning Negotiation data Network planning Internal planning Negotiation data Page 56 of 133 .13.13.2/26 Use VLAN or not/Enabled VLAN ID - - PATH check flag ENABLE - Check IP address 16.2/24 Use VLAN or not/Enabled VLAN ID - - PATH check flag ENABLE - Check IP address 13.16.13. Yes/18/20 - Local IP address/subnet mask 10.2/24 - DSCP 46 46 Transmit (kbps) bandwidth 1800 1800 Receive (kbps) bandwidth 1800 1800 FPMUX Enable NO NO Port type Eth Eth IP Path flag 2 2 PATH type NRT NRT Whether to bind logical port/logical port slot No.INTERNAL IPRAN Deployment Guide Data Item IP path2 IP path 3 RNC NodeB Local IP address/subnet mask 13.10. and port No.16.16.1/24 13.100 /26 16.13.13.13. 100/26 16.10.16. Data planning of management plane Data Item RNC 2008-09-14 NodeB Huawei Confidential Data Source Page 57 of 133 .10. and port No. Yes/18/20 - Local IP address/subnet mask 10.2/26 - DSCP 10 10 Transmit (kbps) bandwidth 20000 20000 Receive (kbps) bandwidth 20000 20000 NO NO FPMUX Enable Data Source Network planning Internal planning Negotiation data Network planning Internal planning 5.16.16.10.INTERNAL IPRAN Deployment Guide Data Item IP path 4 RNC NodeB Whether to bind logical port/logical port slot No.16.2/26 - DSCP 10 10 Transmit (kbps) bandwidth 20000 20000 Receive (kbps) bandwidth 20000 20000 FPMUX Enable NO NO Port type Eth Eth IP Path flag 4 4 PATH type HSUPANRT HSUPANRT Whether to bind logical port/logical port slot No.16.10.16.100/26 16.2/26 Use VLAN or not/Enabled VLAN ID - - PATH check flag ENABLE - Check IP address 16. and port No.16.16.2/26 Use VLAN or not/Enabled VLAN ID - - PATH check flag ENABLE - Check IP address 16. Yes/18/20 - Local IP address/subnet mask 10. Data services produce decreasing benefits for telecom operators.9/26 (If NodeB OMIP and the interface IP are on the same network segment. In addition to the guarantee of services. especially with the introduction of HSDPA and HSUPA. Therefore. 2008-09-14 Huawei Confidential Page 58 of 133 .215.16.161. In such a situation. The transmission based on ATM over E1.10.INTERNAL IPRAN Deployment Guide OMIP address at NodeB side - 9.242/24 network IP address - IP address M2000 Server - of 10. enable the ARP proxy function of the interface) Interface IP address at NodeB side 16.9. Note: The transmission paths carrying different services are configurable (depending on the data planning). and signaling services have a relatively low requirement for the bandwidth and high requirement for the QoS.2/26 at RNC side - BAM external 10.16.1/26 Gateway IP address 10.  BE services and HSDPA/HSUPA services have a relatively high requirement for the bandwidth and low requirement for the QoS. the telecom operators are eager for a low-cost Iub transmission solution.16. ATM/IP dual stack transport is introduced.2/26 Gateway IP address at NodeB side 16. ATM/IP dual stack transport protects the investment of the existing ATM networks.230/24 Network planning 5. Based on the Quality of Service (QoS) and bandwidth requirements. there is an increasing demand for bandwidth on the Iub interface.16. ATM/IP dual stack transport implements data transmission as follows:  Voice. is expensive.9.1/26 at RNC side - Interface IP address 10. Such services are transmitted on IP networks. and meets the requirements of telecom operators for highly efficient and low-cost networks and for flexible networking.161.3. streaming. reduces the impact of IP transport on the ongoing services on the ATM networks. Such services are transmitted on ATM networks. however.4 Data Planning of Dual Stack Transport Networking With the development of data services.215.10.10. this transport reduces costs of data transmission on the Iub interface.10. streaming. Networking Planning Note: This configuration is based on the following scenarios: On the RNC side. and the R99 non-real-time (NRT). The NodeB is connected to the ATM and IP networks through its ATM and IP interface boards respectively. or UOIa (UOI_IP). The services of low QoS requirements. are transmitted on the IP network. and HSUPA services are transmitted on the IP network. channelized STM-1 port. are transmitted on the ATM network. POUa.  The IP interface board can be an FG2a. or OC-3C port. Figure 1. the AOUa serves as the ATM interface board and the FG2a serves as the IP interface board. The signaling. 2.19 Dual stack transport networking To support this networking mode. channelized STM-1 port. or OC-3C port. AOUa.  The ATM interface board can be an AEUa. the related parameters should be modified in the configuration. and OM services are transmitted on the ATM network. Networking Description The ATM/IP dual stack transport enables hybrid transport of services that have different QoS requirements. such as voice. an RSS or RBS of the RNC is configured with both ATM and IP interface boards. Figure 1. such as HSDPA and HSUPA. It is connected to the ATM network through the E1/T1 port.INTERNAL IPRAN Deployment Guide 1. R99 real-time (RT). It is connected to the IP network through the Ethernet port. For dual backup channels of signaling and OM services. or UOIa (UOI_ATM).20 ATM configuration planning 2008-09-14 Huawei Confidential Page 59 of 133 . GOUa. The services of high QoS requirements. HSDPA. E1/T1 port. and signaling. 22 IP address planning for layer 2 networking over Ethernet  Data Planning at the Physical Layer and Data Link Layer Data planning for ATM transport 2008-09-14 Huawei Confidential Page 60 of 133 .21 IP address planning for layer 3 networking over Ethernet Figure 1.INTERNAL IPRAN Deployment Guide Figure 1. INTERNAL IPRAN Deployment Guide Data planning for layer 3 networking Data planning for layer 2 networking 2008-09-14 Huawei Confidential Page 61 of 133 INTERNAL IPRAN Deployment Guide  Data Planning on the Control Plane  Data Planning on the User Plane 2008-09-14 Huawei Confidential Page 62 of 133 INTERNAL IPRAN Deployment Guide 2008-09-14 Huawei Confidential Page 63 of 133 INTERNAL IPRAN Deployment Guide 2008-09-14 Huawei Confidential Page 64 of 133 . INTERNAL IPRAN Deployment Guide  Data Planning on the Management Plane 2008-09-14 Huawei Confidential Page 65 of 133 . the port IP f the RNC interface board and the NodeB IP are on the same network segment. If the interconnected device is in the auto negotiation mode. FC=ON. 1. The FE port is 0. BRDTYPE=FG2. PN=0. see section 7.1 Configuration of Layer-2 Networking In the case of the L2 networking. The binding between the board backup and port backup is used. Parameter Description: AUTO Auto negotiation or not FESPEED FE port rate 2008-09-14 This parameter is determined according to the device interconnected to the RNC. This parameter is designated according to the rate of the peer Huawei Confidential Page 66 of 133 .3. the RNC port is set to non auto negotiation mode. 2.4. For the configuration of PPP link. //Set the Ethernet port attributes. PTYPE=FE. SET ETHPORT: SRN=0.INTERNAL IPRAN Deployment Guide 5. the RNC port is also in the auto negotiation mode.4. Otherwise. Perform the configuration in the RNC in the MML  Configure the physical layer data. Connect the network cable.4 Configuration Procedures at RNC Side Version in the configuration example: RNC uses V210060 5. FESPEED=100M. The GE port must be in the auto negotiation mode. FCINDEX=1. FLOWCTRLSWITCH=ON. The FE port of the RNC and the FE port interconnected to the RNC must be set to 100M/FULL. SN=18. MTU=1500. AUTO=DISABLE. OAMFLOWBW=1. DUPLEX=Full. Label of hardware connection: The FG2 board of the RNC is in slot 18/19 in subrack 0. 2008-09-14 NodeBId=1.255. //Data link layer data should not be configured in the FE/GE port.2".1". VLANFlAG=ENABLE. IPADDR="10. LOGPORTSN=18.10. SSN=0. CNOPINDEX=0. The local IP is the FE IP of the RNC interface board.1/24. SWITCHBACKFLAG=YES.10.10.10. VLANID=10. PEERPORTNO=9001.10. //Add NodeB and algorithm parameters. NodeB algorithm parameter.  SN=18. LOGPORTNO=20.0". SRN=0.10.1". DUPLEX Work mode Half duplex: Data packets cannot be transmitted when the system is receiving data packets. and the other is used for the CCP. SCTPLNKN=1. LPN=20. LOGPORTFLAG=YES. SSN=0. SN=0. CnOpIndex=0. see the negotiation data table. MODE=SERVER. APP=NBAP. the value is 100M/1000M.INTERNAL IPRAN Deployment Guide device.10. ADD SCTPLNK: SRN=0. MASK="255. BWADJ=OFF. transport neighbor node. Huawei Confidential Page 67 of 133 . ADD LGCPORT: SRN=0. one is used for the NCP. Generally.10. The peer IP is the FE IP of the NodeB interface board. TnlBearerType=IP_TRANS. LOGPORTSN=18. MODE=SERVER. VLANFlAG=ENABLE. The RNC selects the server mode.10. ADD NODEB: NodeBName="RNC8-BBU1". ADD ETHIP: SRN=0. LOCIPADDR1="10. SharingSupport=NON_SHARED.  LPNSN=18.2".10. and Iub port data (NCP link and CCP link). LOCIPADDR1="10. the parameter is set to Full duplex. SWITCHBACKFLAG=YES. For the port number. IPTYPE=PRIMARY. Add the configuration of the data link layer. PEERIPADDR1="10. CIR=313. //Add the logical port. APP=NBAP. SSN=0. LOGPORTFLAG=YES. //At least two SCTP links are available. including SCTP signaling link. Generally. PN=0.255. IPTRANSAPARTIND=NOT_SUPPORT. Full duplex: The system can receive and transmit data at the same time. ADD SCTPLNK: SRN=0.10. LOGPORTNO=20. RSCMNGMODE=EXCLUSIVE. //Add the IP address of the Ethernet port. PEERPORTNO=9000. PNSN=18. VLANID=10. FLOWCTRLSWITCH=ON.1". SN=0. NodeB basic information. The IP address of the RNC interface board is 10. SCTPLNKN=2. PEERIPADDR1="10. Add the control plane data. SN=0. PN=0.10. NODET=IUB. SRBPRIPATH=HQ_IPRT. PSSTRMPRIPATH=HQ_IPRT. CSCONVSECPATH=NULL. AF11DSCP=10. REMARK="IUB". HUBKGSECPATH=HQ_IPHDNRT. AF23DSCP=22. HDSTRMPRIPATH=HQ_IPRT. HDBKGSECPATH=NULL. AF41DSCP=34. TRANST=IP. HDSRBPRIPATH=HQ_IPRT. HDCONVPRIPATH=HQ_IPRT. HDSRBSECPATH=NULL. PSLOWINTERACTSECPATH=HQ_IPRT. 2008-09-14 Huawei Confidential Page 68 of 133 . NODEBID=1. CARRYLNKT=SCTP. ADD TRMMAP: TMI=1. HUHIGHINTERACTPRIPATH=HQ_IPHUNRT.INTERNAL IPRAN Deployment Guide ADD NODEBALGOPARA: NodeBLdcAlgoSwitch=IUB_LDR-1&LCG_CREDIT_LDR-1. the transport bandwidth is used effectively. AF42DSCP=36. AF13DSCP=14. //Add the mapping relation of transport resources to map services with different QoS to the corresponding transport channels. PSHIGHINTERACTPRIPATH=HQ_IPNRT. PSMIDINTERACTPRIPATH=HQ_IPNRT. PSHIGHINTERACTSECPATH=HQ_IPRT. CCHPRIPATH=HQ_IPRT. ADD NCP: NODEBNAME="RNC8-BBU1". VOICEDL=70. HDHIGHINTERACTSECPATH=HQ_IPHUNRT. HDCONVSECPATH=NULL. AF21DSCP=18. HUCONVSECPATH=NULL. AF31DSCP=26. SRBUL=15. AF22DSCP=20. TRANST=IP. NAME="NODEB1". VOICESECPATH=NULL. CSCONVDL=100. HUHIGHINTERACTSECPATH=HQ_IPHDNRT. GENCCHDL=70. HUBKGPRIPATH=HQ_IPHUNRT. SRBDL=15. PSCONVSECPATH=NULL. PSLOWINTERACTPRIPATH=HQ_IPNRT. GENCCHUL=70. CSCONVPRIPATH=HQ_IPRT. EFDSCP=46. ADD ADJNODE: ANI=1. NodeBHsupaMaxUserNum=3840. VOICEPRIPATH=HQ_IPRT. HUSRBPRIPATH=HQ_IPRT. HUSRBSECPATH=NULL. CSSTRMPRIPATH=HQ_IPRT. CCHSECPATH=NULL. //Add the link of the NodeB control port. HDMIDINTERACTSECPATH=HQ_IPHUNRT. //Add the transport neighbor node. HUMIDINTERACTSECPATH=HQ_IPHDNRT. HDMIDINTERACTPRIPATH=HQ_IPHDNRT. BEDSCP=0. HDHIGHINTERACTPRIPATH=HQ_IPHDNRT. ADD FACTORTABLE: FTI=1. AF32DSCP=28. In this way. SCTPLNKN=1. AF12DSCP=12. PSSTRMSECPATH=HQ_IPRT. PSCONVPRIPATH=HQ_IPRT. PSBKGPRIPATH=HQ_IPNRT. PSBKGSECPATH=HQ_IPRT. ITFT=IUB_IUR_IUCS. HULOWINTERACTPRIPATH=HQ_IPHUNRT.  Configure the mapping relation of transport resources and activity factor table. HUCONVPRIPATH=HQ_IPRT. ADD CCP: NODEBNAME="RNC8-BBU1". PN=0. HDLOWINTERACTSECPATH=HQ_IPHUNRT. CSSTRMSECPATH=NULL. CARRYLNKT=SCTP. HUSTRMPRIPATH=HQ_IPRT. AF33DSCP=30. AF43DSCP=38. MBMSCCHDL=100. //Add the activity factor table. VOICEUL=70. SCTPLNKN=2. NodeBHsdpaMaxUserNum=3840. HDBKGPRIPATH=HQ_IPHDNRT. HUSTRMSECPATH=NULL. SRBSECPATH=NULL. PSMIDINTERACTSECPATH=HQ_IPRT. HULOWINTERACTSECPATH=HQ_IPHDNRT. HUMIDINTERACTPRIPATH=HQ_IPHUNRT. Designate the activity factor for different services to multiplex transport resources. HDSTRMSECPATH=NULL. 255".10. ECHOIP="10. VLANID=20. VLANFlAG=ENABLE.255. CTRLSN=0. PEERIPADDR="10. PEERMASK="255. including port controller.255. RXBW=20000. PATHID=4.255".2". LPN=20.1". PATHCHK=ENABLED. VLANFlAG=ENABLE. PEERMASK="255.10.10. HDSRBDL=50. CARRYFLAG=LGCPORT.10.10. CTRLSSN=0. HUSTRMUL=100.1". VLANFlAG=ENABLE.10.10. IP route. ADD PORTCTRLER: SRN=0. ADD IPPATH: ANI=1. PATHCHK=ENABLED. HDBKGDL=100. PATHT=HQ_NRT.2".  Add user plane data. VLANID=10. CNOPINDEX=0.10. FPMUX=NO. LPNSN=18. ECHOIP="10. DSCP=10. CARRYFLAG=LGCPORT. CNMNGMODE=EXCLUSIVE. TXBW=20000. DSCP=10. DSCP=18. VLANID=20. PATHT=HQ_HSDPANRT.10.255". LPN=20.10. PATHT=HQ_RT.2". RXBW=20000. ADD IPPATH: ANI=1.10.2".10. FTI=1.1".10. PEERIPADDR="10. SN=18.255. FE bearer: add transport resources of port 0 of FG2 board in slot 18 to manage and control the SPU subsystem.2".10. VLANID=10. IPADDR="10. HUSRBUL=50. PSCONVDL=70.10. //Add the IP PATH: the unit is kbps.10.255. FPMUX=NO.255". PEERIPADDR="10.255. PSCONVUL=70. HUCONVUL=70. PSINTERDL=100. TMISLV=1. FPMUX=NO. HDSTRMDL=100. PATHID=1. HUINTERUL=100. TMIBRZ=1.2". ADD IPPATH: ANI=1. PSBKGDL=100. IP PATH. ADD IPPATH: ANI=1. CSSTRMDL=100. HDCONVDL=70. IPADDR="10. PSSTRMDL=100. CARRYEN=0.10. TMIGLD=1. PSSTRMUL=100. TXBW=20000. RXBW=20000. LPNSN=18. PT=ETHER. LPN=20. PATHCHK=ENABLED. VLANFlAG=ENABLE. PATHCHK=ENABLED. LPNSN=18. PEERMASK="255. LPNSN=18. PSINTERUL=100.255.255.10.10. PATHID=3. PSBKGUL=100. IPADDR="10.2".10. CSSTRMUL=100. CARRYFLAG=LGCPORT. and transport resource group.10.10. ADD ADJMAP: ANI=1. HDINTERDL=100.2".255. 2008-09-14 Huawei Confidential Page 69 of 133 .INTERNAL IPRAN Deployment Guide CSCONVUL=100. Route should not be added in the case of L2 networking.10. PATHID=2. PEERMASK="255. //Configure the mapping of transport resources of neighbor nodes. CARRYFLAG=LGCPORT. PATHT=HQ_HSUPANRT. ECHOIP="10. FPMUX=NO. ECHOIP="10. LPN=20.  Add the O&M channel. RXBW=20000. //Add the port controller.1". TXBW=20000. PEERIPADDR="10.10. TXBW=20000. DSCP=46. HUBKGUL=100. IPADDR="10. 10. Ethernet port IP address. The FE port is 0. ADD NODEBIP: NODEBID=1. IPADDR="10.2".192".3".255.100".  Add the configuration of the data link layer. NBTRANTP=IPTRANS_IP. including SCTP signaling link. CNOPINDEX=0.230".232". MASK="255.4.  LPNSN=18. The device IP address should not be the same as the configured IP address in the RNC (including local/peer IP address of the PPP link. BWADJ=OFF. ADD DEVIP: SRN=0.0". IPGATEWAYIP="10. SN=18. NBIPOAMIP="10. local/peer IP address of the MLPPP group. 1. IPPATH peer address. IPSRN=0.  Configure the physical layer data.10. Packets are forwarded to the NodeB through a router. IPLPN=20. 2008-09-14 Huawei Confidential Page 70 of 133 . IPLOGPORTFLAG=YES.255. you should add the device IP address of the board.10. ADD ETHIP: SRN=0.10. Perform the configuration in the RNC in the MML. RSCMNGMODE=EXCLUSIVE. Label of hardware connection: The FG2 board is in slot 18/19 in subrack 0. PNSN=18. FLOWCTRLSWITCH=ON. PN=0.215.10. NBIPOAMMASK="255.255. //Data link layer data should not be configured in the FE/GE port. PN=0.2 Configuration of Layer-3 Networking The port IP of the RNC interface board and the NodeB IP belong to different network segments. NodeB basic information. BAMMASK="255.255. Connect E1 cable or Ethernet cables.INTERNAL IPRAN Deployment Guide Add the NodeB IP address for the operation and maintenance. and Iub port data (NCP link and CCP link).0".161. 2.255.10.255. SN=18. IPADDR="10.215. The board backup separated from the port backup is used. Add the IP attributes of the NE management system: The EMSIP is the access IP of the M2000.10. SCTP link peer address).2". 5.255. Difference from the L2 networking: When physical layer data is configured. MASK="255. ADD LGCPORT: SRN=0.10.255. ADD EMSIP: EMSIP="10. //Add the logical port.0".192".255. neighbor node. Add the control plane data. CIR=313.255.161. NodeB algorithm parameter. LPN=20. MASK="255. BAMIP="10. IPSN=18. AF33DSCP=30. 2008-09-14 Huawei Confidential Page 71 of 133 . PSHIGHINTERACTPRIPATH=HQ_IPNRT.10. ADD NODEBALGOPARA: NodeBLdcAlgoSwitch=IUB_LDR-1&LCG_CREDIT_LDR-1. PSCONVSECPATH=NULL. In this way. LOGPORTNO=20. The local IP is the FE IP of the RNC interface board. PEERIPADDR1="16. SharingSupport=NON_SHARED. CSSTRMSECPATH=NULL.100". SCTPLNKN=2. TRANST=IP. CCHPRIPATH=HQ_IPRT. CnOpIndex=0. APP=NBAP. ADD ADJNODE: ANI=1. CARRYLNKT=SCTP. ITFT=IUB_IUR_IUCS. TRANST=IP. LOGPORTFLAG=YES. SN=0.10. NodeBHsupaMaxUserNum=3840. SN=0. NodeBId=1. //Add the link of the NodeB control port. CSCONVSECPATH=NULL. PEERIPADDR1="16. PEERPORTNO=9000.2". PSMIDINTERACTPRIPATH=HQ_IPNRT. CCHSECPATH=NULL. ADD NODEB: NodeBName="RNC8-BBU1". SN=0. see the negotiation data table.16. AF23DSCP=22. and the other is used for the CCP. ADD SCTPLNK: SRN=0. For the port number.16. PSMIDINTERACTSECPATH=HQ_IPRT. AF22DSCP=20. SRBPRIPATH=HQ_IPRT. AF43DSCP=38.10. SSN=0. PN=0.  Configure the mapping relation of transport resources and activity factor table. PEERPORTNO=9001. LOCIPADDR1="10. ADD SCTPLNK: SRN=0. NAME="NODEB1". NodeBHsdpaMaxUserNum=3840.100". SWITCHBACKFLAG=YES. MODE=SERVER. SRN=0. AF31DSCP=26. LOCIPADDR1="10. //Add the transport neighbor node. CSSTRMPRIPATH=HQ_IPRT. SSN=0. ADD TRMMAP: TMI=1. AF12DSCP=12. SRBSECPATH=NULL. VOICESECPATH=NULL. ADD NCP: NODEBNAME="RNC8-BBU1". IPTRANSAPARTIND=NOT_SUPPORT. AF11DSCP=10. //Add the mapping relation of transport resources to map services with different QoS to the corresponding transport channels. TnlBearerType=IP_TRANS. //Add NodeB and algorithm parameters. AF41DSCP=34.16. BEDSCP=0. VLANFlAG= DISABLE. CARRYLNKT=SCTP. LOGPORTNO=20. one is used for the NCP. AF32DSCP=28. NODET=IUB. SCTPLNKN=1. VOICEPRIPATH=HQ_IPRT. ADD CCP: NODEBNAME="RNC8-BBU1". PSSTRMSECPATH=HQ_IPRT. SCTPLNKN=1. PSHIGHINTERACTSECPATH=HQ_IPRT. SCTPLNKN=2. NODEBID=1. SWITCHBACKFLAG=YES. APP=NBAP. LOGPORTSN=18.16. AF13DSCP=14. EFDSCP=46. PSSTRMPRIPATH=HQ_IPRT.INTERNAL IPRAN Deployment Guide //At least two SCTP links are available. PSCONVPRIPATH=HQ_IPRT. CSCONVPRIPATH=HQ_IPRT.2". AF42DSCP=36. MODE=SERVER. The peer IP is the FE IP of the NodeB interface board. The RNC selects the server mode. SSN=0. LOGPORTSN=18.10. AF21DSCP=18. LOGPORTFLAG=YES. the transport bandwidth is used effectively. VLANFlAG=DISABLE. RXBW=20000. HUCONVSECPATH=NULL. HDBKGDL=100.255. HDHIGHINTERACTPRIPATH=HQ_IPHDNRT. PEERMASK="255. CTRLSSN=0. TMIBRZ=1. //Add the port controller. HUHIGHINTERACTSECPATH=HQ_IPHDNRT.  Add user plane data. //Add the IP PATH: the unit is kbps.100".255". HUSRBSECPATH=NULL. TXBW=20000. HUBKGSECPATH=HQ_IPHDNRT. CNMNGMODE=EXCLUSIVE. HDINTERDL=100. PEERIPADDR="16. ADD ADJMAP: ANI=1. //Add the activity factor table. HUHIGHINTERACTPRIPATH=HQ_IPHUNRT. PSBKGUL=100. HUSTRMSECPATH=NULL. PSCONVDL=70.255.10. LPNSN=18. REMARK="IUB". HDSTRMDL=100. ECHOIP="16. HDSRBDL=50. PSSTRMDL=100. SRBDL=15. CARRYFLAG=LGCPORT. HDMIDINTERACTSECPATH=HQ_IPHUNRT. PSBKGSECPATH=HQ_IPRT. HUMIDINTERACTPRIPATH=HQ_IPHUNRT. HDCONVPRIPATH=HQ_IPRT. SRBUL=15. CSCONVUL=100. PATHID=1. IPADDR="10. PATHT=HQ_RT. HUSTRMUL=100. CSSTRMDL=100. HUINTERUL=100. IP PATH. VOICEDL=70. MBMSCCHDL=100. FE bearer: add transport resources of port 0 of FG2 board in slot 18 to manage and control the SPU subsystem. HDSRBSECPATH=NULL. HDBKGSECPATH=NULL. HULOWINTERACTPRIPATH=HQ_IPHUNRT.16. HUCONVUL=70. ADD IPPATH: ANI=1. //Configure the mapping of transport resources of neighbor nodes. HUSRBPRIPATH=HQ_IPRT.2". DSCP=46. HDMIDINTERACTPRIPATH=HQ_IPHDNRT. 2008-09-14 Huawei Confidential Page 72 of 133 . HDLOWINTERACTSECPATH=HQ_IPHUNRT. HDSTRMPRIPATH=HQ_IPRT. HDCONVSECPATH=NULL. PSSTRMUL=100. HDBKGPRIPATH=HQ_IPHDNRT. HDSTRMSECPATH=NULL. VOICEUL=70. including port controller. PT=ETHER. Designate the activity factor for different services to multiplex transport resources. CSSTRMUL=100.10.16. CSCONVDL=100. TMISLV=1.16. ADD PORTCTRLER: SRN=0. GENCCHDL=70.16. FTI=1. CTRLSN=0. HDCONVDL=70. and transport resource group. HUBKGPRIPATH=HQ_IPHUNRT. PSBKGPRIPATH=HQ_IPNRT. HULOWINTERACTSECPATH=HQ_IPHDNRT. FPMUX=NO.2". PSLOWINTERACTSECPATH=HQ_IPRT. LPN=20. ADD FACTORTABLE: FTI=1.INTERNAL IPRAN Deployment Guide PSLOWINTERACTPRIPATH=HQ_IPNRT. GENCCHUL=70. HUCONVPRIPATH=HQ_IPRT. HUSTRMPRIPATH=HQ_IPRT. SN=18. HDSRBPRIPATH=HQ_IPRT. IP route. PSINTERDL=100. TMIGLD=1. HUBKGUL=100. CNOPINDEX=0. PSBKGDL=100. HUMIDINTERACTSECPATH=HQ_IPHDNRT. VLANFlAG=DISABLE. CARRYEN=0. PSCONVUL=70. HDHIGHINTERACTSECPATH=HQ_IPHUNRT. PATHCHK=ENABLED. PSINTERUL=100. HUSRBUL=50. 215. SN=18. MASK="255. Through the route configuration. ADD IPRT: SRN=0.255.16. TXBW=20000. Add the IP attributes of the NE management system: The EMSIP is the access IP of the M2000. PEERIPADDR="16.2".2". TXBW=20000. ECHOIP="16.16.9.255.16. PEERIPADDR="16.0".16. ADD IPPATH: ANI=1. NBTRANTP=IPTRANS_IP.2". PATHID=4. IPGATEWAYIP="10. FPMUX=NO. DESTIP="16.2".2".0".161. use the FG2a board and port backup. DSCP=18. CARRYFLAG=LGCPORT.3 Configuration of Hybrid Transport Networking The port IP of the RNC interface board and the NodeB IP belong to different network segments. PATHID=2. CARRYFLAG=LGCPORT. LPNSN=18. IPSN=18. DSCP=10. VLANFlAG= DISABLE.9".10. PEERMASK="255. LPN=20. PEERIPADDR="16..161. NBIPOAMMASK="255.16. BAMIP="10.1". FPMUX=NO.255".16. RXBW=20000.100". IPADDR="10.255. LPN=20.2". LPNSN=18.255. LPNSN=18.10. the IP load sharing can be implemented between any two active FE/GE ports. PATHT=HQ_HSUPANRT. VLANFlAG= DISABLE. ADD EMSIP: EMSIP="10. Add the NodeB IP address for the operation and maintenance.255.255". NEXTHOP="10.16. Packets are forwarded to the NodeB through a router.2". PATHCHK=ENABLED. ADD IPPATH: ANI=1. DSCP=10.16.16.10. ECHOIP="16.255. PEERMASK="255. NBIPOAMIP="9.1".16. PATHT=HQ_NRT. PATHCHK=ENABLED. ADD NODEBIP: NODEBID=1.230". with the switchover separation mode.255.100". PATHCHK=ENABLED.10.255. IPLOGPORTFLAG=YES.0". Support the port independent switchover. MASK="255. TXBW=20000. RXBW=20000.215.255.10. In the case of the FE bearer.16. VLANFlAG= DISABLE.10.  Add the O&M channel.232". 5. PATHT=HQ_HSDPANRT.255. IPLPN=20. PEERMASK="255.16.4. //Add the user plane route. FPMUX=NO.16.10.INTERNAL IPRAN Deployment Guide ADD IPPATH: ANI=1. PATHID=3.255. IPADDR="10.100".9.255.255".0". RXBW=20000. The dual reliabilities (board and transport) are provided.10. IPADDR="10. IPSRN=0.16. LPN=20. ECHOIP="16. CARRYFLAG=LGCPORT. 2008-09-14 Huawei Confidential Page 73 of 133 . BAMMASK="255. PRIORITY=HIGH.10. The FG2a/GOUa board backup and port load sharing mode can be used.255.255.10. 0 E1 pair (E1 is numbered from 0). IPADDR="10.  LPNSN=18. MODE=SERVER. For the port number.13. No. ADD LGCPORT: SRN=0.255. Label of hardware connection: The PEU board of the RNC is in slot 14/15 in subrack 0. MASK="255.  Add the logical port. local/peer IP address of the MLPPP group. transport neighbor node.INTERNAL IPRAN Deployment Guide 1. SCTPLNKN=1. The FG2 is in slot 18/19 of subrack 0. PPPLNKN=0. SN=18. The configuration is not required in the case of E1 bearer.13.255.255. you should add the device IP address of the board.10.0 E1 is used.10.10. ADD SCTPLNK: SRN=0. and Iub port data (NCP link and CCP link). 2008-09-14 Huawei Confidential Page 74 of 133 . The PPP LINK is carried over No. PN=0. NodeB basic information.2". SN=14.2". FLOWCTRLSWITCH=ON. PEERIPADDR="13. CNOPINDEX=0. The peer IP is the peer IP of the RNC PPP link. The local IP is the local IP of the RNC PPP link. PNSN=18.255. SN=14.  Configure the physical layer data. and the other is used for the CCP. one is used for the NCP. SSN=0.13. SCTP link peer address). Run DSP E1T1:SRN=0. //At least two SCTP links are available. Difference from the L2 networking: When physical layer data is configured. SN=18. DS1=0. AUTHTYPE=NO_V.192". Perform the configuration in the RNC in the MML. and BE services are transmitted through the FE.192". ADD DEVIP: SRN=0. SN=0.13. RSCMNGMODE=EXCLUSIVE. The device IP address should not be the same as the configured IP address in the RNC (including local/peer IP address of the PPP link. ADD PPPLNK: SRN=0. The RNC selects the server mode.255. IPADDR="10. //Add the PPP links. Signaling and real-time services are transmitted through the PPP. and the FE port is 0.1".10. BT=AEU/PEU.0". LPN=20. that is. Add the control plane data. BWADJ=OFF. CIR=313. NodeB algorithm parameter. PPPMUX=Disable. to observe the E1 state. APP=NBAP. see the negotiation data table. IPPATH peer address. DS1=0.255. 2. ADD ETHIP: SRN=0. TSBITMAP=TS1-1&TS2-1&TS3-1&TS41&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-1&TS13-1&TS14-1&TS151&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&TS24-1&TS251&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1. Connect E1 cables or Ethernet cables. PN=0. Ethernet port IP address. including SCTP signaling link. IPADDR="13.100". MASK="255. MASK="255. 13. AF12DSCP=12. NAME="NODEB1". SN=0. //Add NodeB and algorithm parameters. PSMIDINTERACTSECPATH=HQ_IPRT. the transport bandwidth is used effectively. PEERIPADDR1="13. AF31DSCP=26. AF33DSCP=30.13. SharingSupport=NON_SHARED. PSLOWINTERACTSECPATH=HQ_IPRT. TRANST=IP. HDLOWINTERACTSECPATH=HQ_IPHUNRT. AF11DSCP=10. SRN=0. NODET=IUB. HUSRBPRIPATH=HQ_IPRT. ADD CCP: NODEBNAME="RNC8-BBU1". LOCIPADDR1="13. AF41DSCP=34. SRBSECPATH=NULL. PSLOWINTERACTPRIPATH=HQ_IPNRT.13. LOGPORTFLAG=NO. NodeBId=1. HDMIDINTERACTSECPATH=HQ_IPHUNRT.INTERNAL IPRAN Deployment Guide LOCIPADDR1="13.13.13.13. CSCONVPRIPATH=HQ_IPRT.1". SCTPLNKN=2. HDSRBSECPATH=NULL. CSCONVSECPATH=NULL. NodeBHsupaMaxUserNum=3840. ADD NODEB: NodeBName="RNC8-BBU1". ITFT=IUB_IUR_IUCS.13. ADD TRMMAP: TMI=1. VOICESECPATH=NULL. HDBKGSECPATH=NULL. TRANST=IP. AF43DSCP=38. BEDSCP=0. MODE=SERVER. AF21DSCP=18. VOICEPRIPATH=HQ_IPRT. HDCONVPRIPATH=HQ_IPRT. SSN=0. NodeBHsdpaMaxUserNum=3840. PSHIGHINTERACTPRIPATH=HQ_IPNRT. PSCONVPRIPATH=HQ_IPRT. HDHIGHINTERACTPRIPATH=HQ_IPHDNRT. 2008-09-14 Huawei Confidential Page 75 of 133 . HUSRBSECPATH=NULL. SCTPLNKN=1. SSN=0.2". AF13DSCP=14. AF22DSCP=20. SRBPRIPATH=HQ_IPRT. PSSTRMSECPATH=HQ_IPRT. VLANFlAG=DISABLE. CCHSECPATH=NULL. HDCONVSECPATH=NULL. PEERPORTNO=9000. In this way. //Add the mapping relation of transport resources to map services with different QoS to the corresponding transport channels. SCTPLNKN=2. PSCONVSECPATH=NULL. SN=0. EFDSCP=46. CCHPRIPATH=HQ_IPRT. CARRYLNKT=SCTP. CSSTRMPRIPATH=HQ_IPRT.  Configure the mapping relation of transport resources and activity factor table.2". AF23DSCP=22. PSBKGPRIPATH=HQ_IPNRT. HDMIDINTERACTPRIPATH=HQ_IPHDNRT. CARRYLNKT=SCTP. ADD ADJNODE: ANI=1. TnlBearerType=IP_TRANS. IPTRANSAPARTIND=NOT_SUPPORT. PSMIDINTERACTPRIPATH=HQ_IPNRT. ADD NCP: NODEBNAME="RNC8-BBU1". HDSRBPRIPATH=HQ_IPRT. HDSTRMSECPATH=NULL. NODEBID=1. SWITCHBACKFLAG=YES. ADD NODEBALGOPARA: NodeBLdcAlgoSwitch=IUB_LDR-1&LCG_CREDIT_LDR-1. AF42DSCP=36. VLANFlAG= DISABLE. LOGPORTFLAG=NO.13. APP=NBAP. CSSTRMSECPATH=NULL. SWITCHBACKFLAG=YES. HDBKGPRIPATH=HQ_IPHDNRT. PEERPORTNO=9001. PSSTRMPRIPATH=HQ_IPRT. PN=0. ADD SCTPLNK: SRN=0. AF32DSCP=28. CnOpIndex=0. //Add the link of the NodeB control port. PSHIGHINTERACTSECPATH=HQ_IPRT. HDSTRMPRIPATH=HQ_IPRT. //Add the transport neighbor node. PSBKGSECPATH=HQ_IPRT.1". HDHIGHINTERACTSECPATH=HQ_IPHUNRT. PEERIPADDR1="13. TMIGLD=1. //Add the IP PATH: the unit is kbps. HDCONVDL=70. VOICEDL=70. CTRLSN=0. ADD ADJMAP: ANI=1.2".2". HUCONVSECPATH=NULL. SRBUL=15. HUHIGHINTERACTSECPATH=HQ_IPHDNRT. CTRLSN=2. CSSTRMDL=100. ADD PORTCTRLER: SRN=0.10. FE bearer: add transport resources of port 0 of FG2 board in slot 18 to manage and control the SPU subsystem. TMISLV=1. PT=ETHER.255". HUSTRMPRIPATH=HQ_IPRT. PSSTRMDL=100. CTRLSSN=0.100".  Add user plane data.255. CSCONVDL=100. CARRYEN=0. HDSRBDL=50. FPMUX=NO. CARRYFLAG=NULL.10. TXBW=1800.13. HUCONVUL=70. PEERIPADDR="13.13. IP PATH. Huawei Confidential IPADDR="10. E1 bearer: add transport resources of port 0 of the PEU board in slot 14 to manage and control the SPU subsystem. including port controller. HULOWINTERACTPRIPATH=HQ_IPHUNRT. FTI=1. HDINTERDL=100. PSSTRMUL=100. Route should not be added in the case of L2 networking.13. PATHT=HQ_NRT. ADD IPPATH: ANI=1. //Configure the mapping of transport resources of neighbor nodes. IP route. SN=14. PSINTERUL=100. REMARK="IUB". SN=18. RXBW=1800. MBMSCCHDL=100. CNMNGMODE=EXCLUSIVE. PSCONVUL=70. ADD IPPATH: ANI=1. PATHCHK=ENABLED. HUSTRMUL=100. CSSTRMUL=100.13. HUINTERUL=100. PT=PPP. HULOWINTERACTSECPATH=HQ_IPHDNRT. HUHIGHINTERACTPRIPATH=HQ_IPHUNRT. HUBKGPRIPATH=HQ_IPHUNRT. CTRLSSN=0. PEERMASK="255. 2008-09-14 PATHID=2. ADD FACTORTABLE: FTI=1.INTERNAL IPRAN Deployment Guide HUCONVPRIPATH=HQ_IPRT. HUBKGSECPATH=HQ_IPHDNRT. PATHID=1. and transport resource group. ECHOIP="13.13. //Add the activity factor table. CARRYPPPN=0. VLANFlAG=DISABLE. ADD PORTCTRLER: SRN=0. PSBKGDL=100. HUSRBUL=50. HUBKGUL=100.13. TMIBRZ=1. HUMIDINTERACTPRIPATH=HQ_IPHUNRT. DSCP=46.1". //Add the port controller. PSINTERDL=100. IPADDR="13. HUSTRMSECPATH=NULL. PSBKGUL=100. CNOPINDEX=0. HDSTRMDL=100. GENCCHUL=70. PATHT=HQ_RT. PSCONVDL=70.255. GENCCHDL=70. Page 76 of 133 . CSCONVUL=100. SRBDL=15. VOICEUL=70. Designate the activity factor for different services to multiplex transport resources. HDBKGDL=100. HUMIDINTERACTSECPATH=HQ_IPHDNRT. 230".255. ADD IPPATH: ANI=1.2". LPNSN=18. TXBW=20000.INTERNAL IPRAN Deployment Guide PEERIPADDR="16.255. IPSN=18. FPMUX=NO. MASK="255.10. MASK="255.16.0". NBIPOAMIP="9. PEERMASK="255.2". 1. RXBW=20000. SN=18. PEERMASK="255.16. RXBW=20000.255. The backup mode is “board backup independent of port backup”. //Add the user plane route. PATHCHK=ENABLED. Add the IP attributes of the NE management system: The EMSIP is the access IP of the M2000. NBTRANTP=IPTRANS_IP. IPSRN=0.255. PRIORITY=HIGH. IPADDR="10.232".2".1". RXBW=20000. R99 RT. PATHT=HQ_HSUPANRT.2". ADD IPRT: SRN=0.10.4. CARRYFLAG=LGCPORT.100".1". 2008-09-14 Huawei Confidential Page 77 of 133 . and the FG2 is placed in slot 18 and 19 of subrack 0.100". FPMUX=NO.16. CARRYFLAG=LGCPORT. PEERIPADDR="16.215. ADD IPPATH: ANI=1.161.9.10. PATHCHK=ENABLED. DESTIP="16. and the R99 NRT. PATHID=4.2".10. Connecting E1 Cables and Ethernet Cables The hardware connections are as follows: The AOU of the RNC is placed in slot 14 of subrack 0.16.16.255. DSCP=18.255. VLANFlAG= DISABLE. BAMIP="10. ADD NODEBIP: NODEBID=1. and OM services are transmitted on the ATM network. Add the NodeB IP address for the operation and maintenance. LPN=20. ECHOIP="16.0". FPMUX=NO.255. ADD EMSIP: EMSIP="10.215.255. DSCP=10. IPLOGPORTFLAG=YES.161. PATHCHK=ENABLED.255".2".255. and HSUPA services are transmitted on the IP network. TXBW=20000. VLANFlAG= DISABLE. ECHOIP="16. PEERIPADDR="16. ECHOIP="16.16. BAMMASK="255.16. The FE port number is 0.255".255.16.16.10. TXBW=20000. LPNSN=18. IPADDR="10. PEERMASK="255. 5.16.16.0".2". LPNSN=18.255".4 Configuration of Dual Stack Transport Networking The signaling.0".9". HSDPA.255.16. VLANFlAG= DISABLE. NBIPOAMMASK="255.255.10.10.16. NEXTHOP="10.255. LPN=20. PATHID=3. IPGATEWAYIP="10.9.10. LPN=20. PATHT=HQ_HSDPANRT. DSCP=10.  Add the O&M channel.255. CARRYFLAG=LGCPORT.16. IPLPN=20. ADD IMALNK: SRN=0. CARRYT=IMA. SET E1T1: SRN=0. ADD ATMTRF: TRFX=130. ADD ATMTRF: TRFX=100. TXTRFX=100. SCRAMBLESW=ON. LNKT=E1_CRC4_MULTI_FRAME. ADD SAALLNK: SRN=0. SSN=0. SN=14. PCR=32. Add SAAL links. IMAGRPN=0. WORKMODE=E1.1. ADD SAALLNK: SRN=0. SSN=0. SAALLNKN=2. CARRYSRN=0. RXTRFX=100. ADD ATMTRF: TRFX=120. PCR=104. They are terminated at SPUa subsystem 0 of slot 0 in subrack 0. SN=14. IMAGRPN=0. ADD IMALNK: SRN=0. CARRYSN=14. BT=AOU. (1) Configure the parameters related to ATM transport  Configure the physical layer and data link layer //Set E1/T1 link parameters. REMARK="for R99 RT". DLYGB=10. CDVT=1024. ST=CBR. IMALNKN=1. You can run the command DSP E1T1: SRN=0. //Add the SAAL link carrying the NCP. SAALLNKT=UNI. Perform the configuration in the RNC in the MML. UT=KBIT/S. SAALLNKT=UNI. IMAGRPN=0. 2008-09-14 Huawei Confidential Page 78 of 133 . ADD ATMTRF: TRFX=102. //Add an IMA group and IMA links. IMALNKN=2. LS=ALL. UT=KBIT/S. BT=AOU. REMARK="for IPOA OM". CARRYVPI=1. SN=0. CARRYVPI=1. CARRYT=IMA. //Add the SAAL link carrying the CCP. PCR=3808. REMARK="for IUB ALCAP". BT=AOU. IMAVER=V1. SN=0. CARRYSRN=0. CARRYT=IMA. SAALLNKN=1. REMARK="for IUB CCP". MBS=1000. PCR=208. SN=14. TXFRAMELEN=D128. CARRYVCI=34. SAALLNKN=0. CARRYVCI=35. The SAAL links are numbered from 0 through 2. to view the E1 state. CARRYIMAGRPN=0. CDVT=1024. SCR=1821. ST=RTVBR. MCR=64. IMAID=0. SSN=0. UT=KBIT/S. //Add ATM traffic records. FLOWCTRLSWITCH=ON. RXTRFX=101. ST=CBR.  Add the data on the Iub control plane. MINLNKNUM=1.. SN=14. ADD IMAGRP: SRN=0. SN=0. UT=KBIT/S. CARRYIMAGRPN=0. CDVT=1024. //Add the SAAL link carrying the ALCAP. SN=14. ST=UBR_PLUS. REMARK="for IUB NCP". CDVT=1024. ADD ATMTRF: TRFX=101. CDVT=1024. ST=CBR. CARRYSRN=0. UT=KBIT/S. TXTRFX=101.INTERNAL IPRAN Deployment Guide 2. ADD SAALLNK: SRN=0. CARRYSN=14. TXTRFX=120. ADD AAL2RT: NSAP="H'45000006582414723F0000000000000000000000". //Add a port controller. ADDTORSCGRP=NO. SAALLNKN=2. 2008-09-14 Huawei Confidential Page 79 of 133 . NodeBProtclVer=R6. CARRYT=IMA. CARRYLNKT=SAAL. PT=IMA. CTRLSSN=0. OWNERSHIP=YES. CARRYIMAGRPN=0. TRANST=ATM_IP. IPTRANSAPARTIND=NOT_SUPPORT. NodeBId=1. //Add a NodeB and its algorithm parameters. CARRYVPI=1. IsROOTNODE=YES. CARRYLNKT=SAAL.255. RXTRFX=120.7". CARRYIMAGRPN=0. ADD CCP: NODEBNAME=" RNC8-BBU1". PN=0. ADD ADJNODE: ANI=1. TXTRFX=102. CARRYF=0. RXTRFX=120. ADD NODEB: NodeBName="RNC8-BBU1". The adjacent node ID is 0 and the interface type is Iub. SN=14. SSN=0. NODEBID=1. SAALLNKN=0.7. ADD NCP: NODEBNAME="RNC8-BBU1". SharingSupport=NON_SHARED. CARRYT=IMA. NodeBHsdpaMaxUserNum=3840. SRN=0. RscMngMode=SHARE.7. NodeBLdcAlgoSwitch=IUB_LDR1&NODEB_CREDIT_LDR-0&LCG_CREDIT_LDR-1. CnOpIndex=0.  Add the data on the Iub user plane. ADD DEVIP: SRN=0. CARRYVCI=40. CARRYIMAGRPN=0. PT=RT. Nsap="H'45000006582414723F0000000000000000000000". CARRYIMAGRPN=0. SN=2. CARRYT=IMA. CARRYSN=14.1". ADD AAL2PATH: ANI=1.  Add the data on the Iub management plane.7.7. RXTRFX=130. NodeBHsupaMaxUserNum=3840. ADD PORTCTRLER: SRN=0. //Add the data on the Iub interface. SAALLNKN=1. CARRYSN=14. ADD AAL2PATH: ANI=1. TnlBearerType=ATMANDIP_TRANS. SRN=0. SAALLNKT=UNI. MASK="255.7. SSN=0. CTRLSN=2. ADDTORSCGRP=NO. NAME="RNC8-BBU1". CARRYIMAGRPN=0. //Add AAL2 paths to the NodeB. ADD IPOAPVC: IPADDR="7. TXTRFX=120. CARRYVCI=36. PEERT=IUB. ADD NODEBALGOPARA: NodeBName="RNC8-BBU1". //Add the IP address of a device board. PT=RT. CARRYVPI=1.7. //Add an IPoA PVC. SN=14. CARRYF=0. PATHID=2. ANI=1. CARRYVPI=1. PEERIPADDR="7. QAAL2VER=CS2. PATHID=1. //Add an adjacent node (NodeB1) on the Iub interface.255. //Add an AAL2 route to the NodeB. RXTRFX=102. NODET=IUB. CARRYVCI=41. CARRYVPI=1. CARRYVCI=33. TXTRFX=130. IPADDR="7.0". RTX=1.1".INTERNAL IPRAN Deployment Guide CARRYSN=14. SN=2. SRBSECPATH=NULL. HULOWINTERACTPRIPATH=HQ_IPHUNRT. HUBKGSECPATH=HQ_IPHDNRT. BAMIP="10. Add the mapping between transmission resources and service types. AF23DSCP=22. PSLOWINTERACTSECPATH=HQ_IPRT. PSHIGHINTERACTPRIPATH=HQ_IPNRT. AF33DSCP=30. MASK="255. PSLOWINTERACTPRIPATH=HQ_IPNRT. (Through this task. HUSTRMSECPATH=NULL. HDBKGPRIPATH=HQ_IPHDNRT. HUMIDINTERACTPRIPATH=HQ_IPHUNRT. CNOPINDEX=0. HDSTRMSECPATH=NULL. AF43DSCP=38.1".192". HUHIGHINTERACTPRIPATH=HQ_IPHUNRT. AF22DSCP=20. PN=0.232". NBATMOAMIP="7.INTERNAL IPRAN Deployment Guide //Add the OM IP address of the NodeB.255. ATMGATEWAYIP="7. //Add an activity factor table to specify activity factors for each traffic class.215.) ADD TRMMAP: TMI=1. HDCONVPRIPATH=HQ_IPRT. HUCONVPRIPATH=HQ_IPRT. PSSTRMSECPATH=HQ_IPRT. PSCONVPRIPATH=HQ_IPRT. SN=18. CSSTRMPRIPATH=HQ_IPRT. VOICEPRIPATH=HQ_IPRT. HUCONVSECPATH=NULL.0".255.161. HDMIDINTERACTSECPATH=HQ_IPHUNRT. AF32DSCP=28. AF31DSCP=26.10. CSCONVPRIPATH=HQ_IPRT. ATMSRN=0. HUSRBPRIPATH=HQ_IPRT.7". ATMSN=14. BEDSCP=0.215. MASK="255.7. LPN=20. ADD NODEBIP: NODEBID=1. PSMIDINTERACTSECPATH=HQ_IPRT. AF11DSCP=10. AF21DSCP=18.7.7". HDHIGHINTERACTPRIPATH=HQ_IPHDNRT. VOICESECPATH=NULL.255. (EMSIP is the IP address of the M2000. CSCONVSECPATH=NULL. NBATMOAMMASK="255. AF13DSCP=14. NBTRANTP=ATMTRANS_IP. (2) Configure the parameters related to IP transport  Layer 2 networking //Add the IP address of an Ethernet port. HUSRBSECPATH=NULL. ADD ETHIP: SRN=0. HUSTRMPRIPATH=HQ_IPRT.255. BAMMASK="255. //Add the IP address of the element management system (EMS).255. //Add a logical port. HDHIGHINTERACTSECPATH=HQ_IPHUNRT. PSBKGSECPATH=HQ_IPRT. PNSN=18. HDMIDINTERACTPRIPATH=HQ_IPHDNRT. TRANST=ATM_IP.161.7. 2008-09-14 Huawei Confidential Page 80 of 133 . PSSTRMPRIPATH=HQ_IPRT.0". PSMIDINTERACTPRIPATH=HQ_IPNRT. HDLOWINTERACTSECPATH=HQ_IPHUNRT. RSCMNGMODE=EXCLUSIVE. ITFT=IUB_IUR_IUCS. FLOWCTRLSWITCH=ON. AF41DSCP=34. CIR=313. PSBKGPRIPATH=HQ_IPNRT. IPADDR="10. HULOWINTERACTSECPATH=HQ_IPHDNRT. PSCONVSECPATH=NULL. HDSRBPRIPATH=HQ_IPRT.7.255. HDBKGSECPATH=NULL. LPNSN=18. HUBKGPRIPATH=HQ_IPHUNRT.255.230".10. HUMIDINTERACTSECPATH=HQ_IPHDNRT.0". CCHPRIPATH=HQ_IPRT. (Through this task. AF42DSCP=36. HDSRBSECPATH=NULL. PSHIGHINTERACTSECPATH=HQ_IPRT. HUHIGHINTERACTSECPATH=HQ_IPHDNRT. BWADJ=OFF. HDCONVSECPATH=NULL. AF12DSCP=12. ADD LGCPORT: SRN=0. PN=0. CSSTRMSECPATH=NULL. thus improving the bandwidth efficiency. CCHSECPATH=NULL. the services of different QoS requirements are mapped onto different channels. HDSTRMPRIPATH=HQ_IPRT. EFDSCP=46.) ADD EMSIP: EMSIP="10.255. SRBPRIPATH=HQ_IPRT. //Configure the TRM mapping and activity factor table. ADD IPPATH: ANI=1. IPADDR="10.1".10. PATHT=HQ_NRT. PSINTERDL=100. SN=18. SRBDL=15. VLANFlAG= DISABLE. TXBW=20000.255". DSCP=18. GENCCHDL=70. PEERMASK="255.2". CNMNGMODE=EXCLUSIVE. //Add the data on the user plane (including adding a port controller. PATHID=1. ADD VLANID: SRN=0. IPADDR="10. PN=0.10. RXBW=20000.2". CARRYFLAG=LGCPORT. PEERIPADDR="10. VOICEUL=70. The SPU subsystem is added on port 0 of the FG2 in slot 18. ADD PORTCTRLER: SRN=0. SRBUL=15. MASK="255. CSSTRMUL=100. TMIGLD=1. the local and peer IP addresses of the MLPPP group.2". HUBKGUL=100. PT=ETHER. TMISLV=1. PSSTRMUL=100.2". PATHID=2.10. PSSTRMDL=100. CSSTRMDL=100.1".10.10.255.10.255. ADD IPPATH: ANI=1. CSCONVDL=100. GENCCHUL=70. the peer IP address of the IP path.100".10. CSCONVUL=100. FPMUX=NO. PEERMASK="255. CNOPINDEX=0.10.255.INTERNAL IPRAN Deployment Guide the transmission resources can be multiplexed. ADD ETHIP: SRN=0. PSBKGUL=100. VOICEDL=70.255. PEERMASK="255. HDCONVDL=70.255. IPADDR="10. SN=18. HDSRBDL=50. PSINTERUL=100. SN=18. IPADDR="10.255". DSCP=12.10. PEERIPADDR="10. HDSTRMDL=100. HDBKGDL=100.10. VLANID=100. RXBW=20000.10. IP paths. ECHOIP="10. and the device IP address cannot be the same as any IP address configured on the RNC( include the local and peer IP addresses of the PPP link.255. IPADDR="10. LPNSN=18.10.255.) ADD FACTORTABLE: FTI=1.10. ECHOIP="10.10. ECHOIP="10.2". PSCONVUL=70. MASK="255.10. layer 3 networking requires the device IP address of a board to be added. ADD ADJMAP: ANI=1. PSBKGDL=100. CARRYFLAG=LGCPORT. TXBW=20000. FPMUX=NO.10. //Add IP paths (traffic unit: kbit/s). DSCP=10. HUSRBUL=50. the IP address of the Ethernet port.10.192". //Add the TRM mapping on the adjacent node.10. ADD DEVIP: SRN=0.10.2". 2008-09-14 Huawei Confidential Page 81 of 133 . LPNSN=18.2". HUSTRMUL=100. TXBW=20000.255".255.10. //Add a VLAN. MBMSCCHDL=100. PATHCHK=ENABLED.10. CTRLSN=0. PATHT=HQ_HSUPANRT.255. VLANFlAG= DISABLE. IPADDR="10. PATHID=3. PSCONVDL=70.192". CTRLSSN=0.10. //Add a port controller. and the peer IP address of the SCTP link).10. LPN=20.  Layer 3 networking //Configure the data at the physical layer. FTI=1. FPMUX=NO. LPN=20. ADD IPPATH: ANI=1. SN=18. CARRYFLAG=LGCPORT. CARRYEN=0.2".1". PEERIPADDR="10. and an IP route). LPNSN=18. PATHCHK=ENABLED. VLANFlAG= DISABLE. REMARK="IUB". HUINTERUL=100. TMIBRZ=1. PATHCHK=ENABLED. //Add a logical port. Different from layer 2 networking.255. HDINTERDL=100.10. HUCONVUL=70. LPN=20. RXBW=20000. PATHT=HQ_HSDPANRT. PSBKGSECPATH=HQ_IPRT. HDSTRMSECPATH=NULL. PSCONVSECPATH=NULL. PSCONVUL=70. BWADJ=OFF. AF42DSCP=36. EFDSCP=46. CNOPINDEX=0. PSSTRMUL=100. HUSTRMSECPATH=NULL. PSINTERDL=100. HDSTRMDL=100. //Add a port controller. CNOPINDEX=0.) ADD TRMMAP: TMI=1. HUHIGHINTERACTPRIPATH=HQ_IPHUNRT. HUSTRMPRIPATH=HQ_IPRT. ITFT=IUB_IUR_IUCS. CSCONVUL=100. //Add an activity factor table to specify activity factors for each traffic class. AF43DSCP=38.) ADD FACTORTABLE: FTI=1. HDCONVPRIPATH=HQ_IPRT. HDLOWINTERACTSECPATH=HQ_IPHUNRT. FTI=1. CSSTRMDL=100. HUBKGUL=100. AF23DSCP=22. GENCCHDL=70. HDSRBDL=50. HDSRBSECPATH=NULL. PSHIGHINTERACTPRIPATH=HQ_IPNRT. HULOWINTERACTSECPATH=HQ_IPHDNRT. PSBKGDL=100. HUCONVPRIPATH=HQ_IPRT. AF31DSCP=26. VOICESECPATH=NULL. TMIBRZ=1. PSBKGPRIPATH=HQ_IPNRT. CSSTRMSECPATH=NULL. HUBKGPRIPATH=HQ_IPHUNRT. PSBKGUL=100. SRBPRIPATH=HQ_IPRT. AF41DSCP=34. and an IP route). PSCONVDL=70. CNMNGMODE=EXCLUSIVE. HUMIDINTERACTSECPATH=HQ_IPHDNRT. thus improving the bandwidth efficiency. GENCCHUL=70. SRBSECPATH=NULL. ADD ADJMAP: ANI=1. RSCMNGMODE=EXCLUSIVE. SRBUL=15. (Through this task. HDCONVSECPATH=NULL. CSCONVPRIPATH=HQ_IPRT. HUSRBSECPATH=NULL. AF32DSCP=28. SRBDL=15. IP paths. PN=0. VOICEPRIPATH=HQ_IPRT. TMISLV=1. HUSRBPRIPATH=HQ_IPRT. HUSTRMUL=100. FLOWCTRLSWITCH=ON. HDBKGSECPATH=NULL. PNSN=18. AF13DSCP=14. (Through this task. HUMIDINTERACTPRIPATH=HQ_IPHUNRT. HULOWINTERACTPRIPATH=HQ_IPHUNRT. LPN=20. HUSRBUL=50. AF11DSCP=10. PSHIGHINTERACTSECPATH=HQ_IPRT. HUCONVSECPATH=NULL. CIR=313. CCHPRIPATH=HQ_IPRT. //Add the TRM mapping on the adjacent node. CSCONVSECPATH=NULL. the transmission resources can be multiplexed. AF21DSCP=18. HDHIGHINTERACTPRIPATH=HQ_IPHDNRT. HUCONVUL=70. HUBKGSECPATH=HQ_IPHDNRT. PSSTRMPRIPATH=HQ_IPRT. AF22DSCP=20. HUHIGHINTERACTSECPATH=HQ_IPHDNRT. HDMIDINTERACTPRIPATH=HQ_IPHDNRT. Add the mapping between transmission resources and service types. PSSTRMSECPATH=HQ_IPRT. TRANST=ATM_IP. TMIGLD=1. the services of different QoS requirements are mapped onto different channels. VOICEUL=70. PSSTRMDL=100. //Configure the TRM mapping and activity factor table. MBMSCCHDL=100. HDMIDINTERACTSECPATH=HQ_IPHUNRT. HDCONVDL=70. //Add the data on the user plane (including adding a port controller. CCHSECPATH=NULL. The SPU subsystem is added on FE port 0 of the FG2 in slot 18.INTERNAL IPRAN Deployment Guide ADD LGCPORT: SRN=0. PSMIDINTERACTSECPATH=HQ_IPRT. CSCONVDL=100. HDSTRMPRIPATH=HQ_IPRT. PSLOWINTERACTSECPATH=HQ_IPRT. BEDSCP=0. PSMIDINTERACTPRIPATH=HQ_IPNRT. HDSRBPRIPATH=HQ_IPRT. PSLOWINTERACTPRIPATH=HQ_IPNRT. HDHIGHINTERACTSECPATH=HQ_IPHUNRT. HDINTERDL=100. 2008-09-14 Huawei Confidential Page 82 of 133 . CSSTRMPRIPATH=HQ_IPRT. LPNSN=18. VOICEDL=70. HDBKGPRIPATH=HQ_IPHDNRT. PSINTERUL=100. REMARK="IUB". PSCONVPRIPATH=HQ_IPRT. HUINTERUL=100. AF33DSCP=30. HDBKGDL=100. AF12DSCP=12. CSSTRMUL=100. LPNSN=18. SET ETHPORT: SRN=0. VLANFlAG= DISABLE. MASK="255.255. SIGPRI=62. PT=ETH.2".255.255.10.2".  Configure the VLAN and service priority.1".16. PN=0.10. PEERIPADDR="16. LPN=20.1 Configuration of Layer-2 Networking  Configure the physical layer data. SN=18. PRIORITY=HIGH. //Set the priority of the signaling and OM.100". FPMUX=NO.10.2". PATHT=HQ_NRT.16.10.255. LPN=20. DUPLEX=FULL. PEERMASK="255.16. VLANFlAG= DISABLE. ARPPROXY=ENABLE.INTERNAL IPRAN Deployment Guide ADD PORTCTRLER: SRN=0.192". CARRYFLAG=LGCPORT.16.255.10.16.16. CTRLSSN=0.16. SN=6. PATHCHK=ENABLED.2". IPADDR="10. PATHT=HQ_HSDPANRT. //Add IP paths (traffic unit: kbit/s).2". TXBW=20000. PATHID=2.255. SET DIFPRI: PRIRULE=DSCP.10. PEERMASK="255.255. SPEED=100M.255.0". PATHT=HQ_HSUPANRT. IPADDR="10. VLANFlAG= DISABLE. CARRYFLAG=LGCPORT.100".2". TXBW=20000.10. 2008-09-14 Huawei Confidential Page 83 of 133 .10. MASK="255. NEXTHOP="10. //Set the mapping group of the VLAN priorities. PT=ETHER.255. IPADDR="10. OMPRI=46. ECHOIP="16. DESTIP="16. PN=0. DSCP=18. PATHCHK=ENABLED.255". FPMUX=NO. FERDT=100.2". DSCP=12 . ADD IPPATH: ANI=1. //Add the IP address of the Ethernet port. DSCP=10. SBT=BASE_BOARD. CARRYFLAG=LGCPORT. CTRLSN=0.2". TXBW=20000. CARRYEN=0.10.16. //Add an IP route on the user plane. RXBW=20000.10. RXBW=20000. SN=18. LPN=20. LPNSN=18. SN=6. 5. MTU=1500.16. ADD IPPATH: ANI=1.255". FERAT=100.16. PEERIPADDR="16. RXBW=20000. IP="10.10.255.16.255". //Set the Ethernet port attributes.5 Configuration Procedures at NodeB Side 5.16.10. SBT=BASE_BOARD.16.2/24. ECHOIP="16. ADD IPPATH: ANI=1. PEERMASK="255. FPMUX=NO.100". PEERIPADDR="16.16. PATHCHK=ENABLED. The IP address of the NodeB FE port is 10. LPNSN=18. ADD DEVIP: SRN=0. PATHID=1. ADD IPRT: SRN=0.5. PATHID=3. ECHOIP="16. INTERNAL IPRAN Deployment Guide //Set the VLAN priority of the signaling plane. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=SIG, INSTAG=ENABLE, VLANID=10, VLANPRIO=7; //Set the VLAN priority of the maintenance plane. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM, INSTAG=ENABLE, VLANID=10, VLANPRIO=5; //Set the VLAN priority of other types of data. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=OTHER, INSTAG=ENABLE, VLANID=10, VLANPRIO=5; //Set the VLAN priority of the data plane. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=62, INSTAG=ENABLE, VLANID=10, VLANPRIO=7; SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=46, INSTAG=ENABLE, VLANID=10, VLANPRIO=5; SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=18, INSTAG=ENABLE, VLANID=10, VLANPRIO=2; SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=10, INSTAG=ENABLE, VLANID=10, VLANPRIO=1; //Add the next hop VLAN mapping. ADD VLANMAP: NEXTHOPIP="10.10.10.1", VLANMODE=VLANGROUP, VLANGROUPNO=0;  Add the control plane data. //Add at least two SCTP links, one is used for the NCP, and the other is used for the CCP. ADD SCTPLNK: SCTPNO=1, SRN=0, SN=6, LOCIP="10.10.10.2", LOCPORT=9000, PEERIP="10.10.10.1", PEERPORT=58080; ADD SCTPLNK: SCTPNO=2, SRN=0, SN=6, LOCIP="10.10.10.2", LOCPORT=9001, PEERIP="10.10.10.1", PEERPORT=58080; //Add the link of the NodeB control port. ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=1; ADD IUBCP: CPPT=CCP, CPPN=0, BEAR=IPV4, LN=2; 2008-09-14 Huawei Confidential Page 84 of 133 INTERNAL IPRAN Deployment Guide  Add the user plane data. //Add the transport resource group. ADD RSCGRP: SRN=0, SN=6, BEAR=IPV4, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=0, TXBW=20000, RXBW=20000; //Add the IP PATH (At the RNC side, two IP PATHs with the same DSCP are available, respectively corresponding to HSDPA and HSUPA. At the NodeB side, one IP PATH of the HSPA should be added). ADD IPPATH: PATHID=1, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=0, NODEBIP="10.10.10.2", RNCIP="10.10.10.1", TFT=RT, DSCP=46, RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=2, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=0, NODEBIP="10.10.10.2", RNCIP="10.10.10.1", TFT=NRT, DSCP=18, RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=3, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=0, NODEBIP="10.10.10.2", RNCIP="10.10.10.1", TFT=HSPA_NRT, DSCP=10, RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE;  Add the O&M channel. Add the NodeB IP address for the operation and maintenance. ADD OMCH: IP="10.10.10.3", MASK="255.255.255.0", PEERIP="10.161.215.230", PEERMASK="255.255.255.0", BEAR=IPV4, SRN=0, SN=6, SBT=BASE_BOARD, BRT=YES, DSTIP="10.161.215.0", DSTMASK="255.255.255.0", RT=NEXTHOP, NEXTHOP="10.10.10.1"; 5.5.2 Configuration of Layer-3 Networking  Configure the physical layer data. //Set the Ethernet port attributes. SET ETHPORT: SRN=0, SN=6, SBT=BASE_BOARD, PN=0, MTU=1500, SPEED=100M, DUPLEX=FULL, ARPPROXY=ENABLE, FERAT=100, FERDT=100; //Add the IP address of the Ethernet port. The IP address of the NodeB FE port is 16.16.16.2/26. 2008-09-14 Huawei Confidential Page 85 of 133 INTERNAL IPRAN Deployment Guide ADD DEVIP: SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, IP="16.16.16.2", MASK="255.255.255.192";  Add the control plane data. //Configure the DSCP of the signaling plane and maintenance plane. SET DIFPRI: PRIRULE=DSCP, SIGPRI=62, OMPRI=46; //Add at least two SCTP links, one is used for the NCP, and the other is used for the CCP. ADD SCTPLNK: SCTPNO=1, SRN=0, SN=6, LOCIP="16.16.16.2", LOCPORT=9000, PEERIP="10.10.10.100", PEERPORT=58080; ADD SCTPLNK: SCTPNO=2, SRN=0, SN=6, LOCIP="16.16.16.2", LOCPORT=9001, PEERIP="10.10.10.100", PEERPORT=58080; //Add the link of the NodeB control port. ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=1; ADD IUBCP: CPPT=CCP, CPPN=0, BEAR=IPV4, LN=2;  Add the user plane data. //Add the transport resource group. ADD RSCGRP: SRN=0, SN=6, BEAR=IPV4, SBT=BASE_BOARD, PT=ETH, PN=0, RSCGRPID=0, TXBW=20000, RXBW=20000; //Add the IP PATH (At the RNC side, two IP PATHs with the same DSCP are available, respectively corresponding to HSDPA and HSUPA. At the NodeB side, one IP PATH of the HSPA should be added). ADD IPPATH: PATHID=1, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=0, NODEBIP="16.16.16.2", RNCIP="10.10.10.100", TFT=RT, DSCP=46, RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=2, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=0, NODEBIP="16.16.16.2", RNCIP="10.10.10.100", TFT=NRT, DSCP=18, RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=3, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=0, NODEBIP="16.16.16.2", RNCIP="10.10.10.100", TFT=HSPA_NRT, DSCP=10, RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0, 2008-09-14 Huawei Confidential Page 86 of 133 215. PEERIP="13.255. PPPLNKN=0. SBT=BASE_BOARD.10.192". PT=ETH.1". Add the NodeB IP address for the operation and maintenance.2".161.0". SBT=BASE_BOARD.255.INTERNAL IPRAN Deployment Guide FPMUXSWITCH=DISABLE.16. AUTH=NONAUTH.255. //Add the PPP link. PN=0. BRT=YES. NEXTHOP="16.255. SET ETHPORT: SRN=0. SN=6.255. BEAR=IPV4.10. RTTYPE=NEXTHOP.0". PN=0.9. SN=6.5.1". //Set the Ethernet port attributes. DSTMASK="255. SN=6.0". NEXTHOP="16. SIGPRI=62.255. IP="10.255. SBT=BASE_BOARD. SPEED=100M. SN=7. CLKM=SLAVE. SBT=BASE_BOARD. OMPRI=46. 5. ADD OMCH: IP="9. PEERIP="10.16.13. ADD DEVIP: SRN=0.16.13. //Add the IP address of the Ethernet port.10.0". PEERMASK="255. SRN=0. SET DIFPRI: PRIRULE=DSCP. DUPLEX=FULL.255.13.16.9. SBT=BASE_BOARD.192".16. SN=6. MASK="255.255. SBT=BASE_BOARD. TSN=TS1&TS2&TS3&TS4&TS5&TS6&TS7&TS8&TS9&TS10&TS11&TS12&TS13&TS14&TS1 5&TS16&TS17&TS18&TS19&TS20&TS21&TS22&TS23&TS24&TS25&TS26&TS27&TS28&TS 29&TS30&TS31.  Add the O&M channel.9". //Set E1/T1 work mode. LOCALIP="13.3 Configuration of Hybrid Transport Networking  Add the physical layer configuration. LNCODE=HDB3. SN=6. ARPPROXY=DISABLE. FERDT=100.10. //Configure the DSCP of the signaling plane and maintenance plane. MASK="255.255. The IP address of the NodeB FE port is 16.  Add the control plane data. DSTMASK="255.0". ADD IPRT: SRN=0.1". FRAME=E1_CRC4_MULTI_FRAME.13. MTU=1500. DSTIP="10.2".  Route should be added in the case of L3 networking. ADD PPPLNK: SRN=0.16. FERAT=100. DSTIP="10. IPMASK="255.215. SET E1T1WORKMODE: SRN=0.161. 2008-09-14 Huawei Confidential Page 87 of 133 . PN=0.0".2/26.255.255. RT=NEXTHOP.230". NODEBIP="16. BEAR=IPV4. SRN=0. RSCGRPID=0. PT=PPP. DSCP=10. SBT=BASE_BOARD. respectively corresponding to HSDPA and HSUPA. ADD IPPATH: PATHID=3. //Add the link of the NodeB control port. RTTYPE=NEXTHOP. RXBW=1800. TXCBS=10000000. TFT=HSPA_NRT. NEXTHOP="16.INTERNAL IPRAN Deployment Guide //Add at least two SCTP links.10. BEAR=IPV4.13. two IP PATHs with the same DSCP are available. TXEBS=0. //Add the IP PATH (At the RNC side. RXBW=20000. SBT=BASE_BOARD. LOCPORT=9000. RSCGRPID=0.13.10.0".2". PN=0. PT=ETH. BEAR=IPV4. SBT=BASE_BOARD.1". At the NodeB side. TXBW=20000. JNRSCGRP=ENABLE. SBT=BASE_BOARD.13. NODEBIP="16. CPPN=0. RXBW=20000. SRN=0. SN=6.1".13.  Add the user plane data.16. //Route should be added in the case of L3 networking. SRN=0. SRN=0. //Add the transport resource group.16. PT=ETH.16. RNCIP="10. ADD SCTPLNK: SCTPNO=2.255. LN=2. DSTMASK="255. SN=6. RXBW=20000. one IP PATH of the HSPA should be added). RSCGRPID=0.13. SRN=0. PEERIP="13. 2008-09-14 Huawei Confidential Page 88 of 133 .255. RNCIP="10.0". and the other is used for the CCP. TXCBS=900000. RNCIP="13. SN=6. LN=1. SBT=BASE_BOARD. TXBW=1800. PEERPORT=58080.2". SN=6.16. RXBW=1800.13.2".13. TFT=RT.13. SBT=BASE_BOARD.2".10. ADD IPRT: SRN=0.10. RSCGRPID=1. RSCGRPID=1. NODEBIP="13. SN=6. LOCIP="13. ADD IUBCP: CPPT=CCP. ADD IPPATH: PATHID=2. TXEBS=0.13. SN=6. SN=6. LOCPORT=9001. ADD IPPATH: PATHID=1. TXCBS=10000000. TXBW=1800. PT=ETH. one is used for the NCP.10. DSCP=18.2".13. FPMUXSWITCH=DISABLE. DSTIP="10. TXBW=20000. ADD SCTPLNK: SCTPNO=1. PEERPORT=58080. TXBW=20000. TXEBS=0.2". BEAR=IPV4.13. PEERIP="13. ADD IUBCP: CPPT=NCP.16.16. ADD RSCGRP: SRN=0. PT=PPP.13. ADD RSCGRP: SRN=0. FPMUXSWITCH=DISABLE. LOCIP="13.1". PN=0. TFT=NRT. JNRSCGRP=ENABLE. JNRSCGRP=ENABLE. DSCP=46. SN=6.10.2".1". SN=7. //Add the SAAL link carrying the NCP. SBT=BASE_BOARD. 2008-09-14 Huawei Confidential Page 89 of 133 . SN=7. VPI=1.9. MASK="255. SBT=BASE_BOARD. BEAR=IPV4. SBT=BASE_BOARD.161. //Add an IMA group and IMA links.9".0".255. SN=6.255. SET E1T1WORKMODE: SRN=0. //Add the SAAL link carrying the CCP.255. VCI=35. JNRSCGRP=DISABLE. SBT=BASE_BOARD. SRN=0.4 Configuration of Dual Stack Transport Networking 1. //Add the NodeB IP address for the operation and maintenance. SBT=BASE_BOARD. IMALNKN=0.0".230". DSTIP="10. SN=7.215.  Configuration the control plane data //Add SAAL links. DSTMASK="255.255. PN=0. LNCODE=HDB3.16. 5.192".255. SN=7. IMAGRPN=2. PCR=104. ADD IMALNK: SRN=0. PEERMASK="255. SBT=BASE_BOARD. PCR=208. FRAME=E1_CRC4_MULTI_FRAME. PT=IMA. ADD SAALLNK: SAALNO=2. ADD SAALLNK: SAALNO=0.16. ADD SAALLNK: SAALNO=1. IMALNKN=0. ADD OMCH: IP="9. ADD IMALNK: SRN=0. FRMLEN=D128.9.215. PT=IMA. SRN=0. //Add the SAAL link carrying the ALCAP.1. CLKM=SLAVE. BRT=YES.255. VER=V1. SN=7. ST=CBR. IMAGRPSBT=BASE_BOARD. IMAGRPN=1. SN=7. ADD IMAGRP: SRN=0. PT=IMA. SRN=0. SBT=BASE_BOARD.161. NEXTHOP="16. ST=CBR. VPI=1.0". PN=0. MINLNK=1. PEERIP="10. Configure the Parameters Related to ATM Transport  Configuration the physical layer data //Set the working mode of E1/T1 links. JNRSCGRP=DISABLE. SRN=0. IMAGRPN=0. VCI=34. IMAGRPSBT=BASE_BOARD. PN=0.1".5.INTERNAL IPRAN Deployment Guide  Add the O&M channel. SN=7. RT=NEXTHOP. SBT=BASE_BOARD. MASK="255. VCI=33. FERDT=100. FLAG=MASTER.255. SBT=BASE_BOARD. VPI=1. FLAG=MASTER. PCR=3808. LN=2. CDVT=10240. JNRSCGRP=DISABLE. PEERMASK="255.2". PN=0.255. PN=0. PATHID=2. SBT=BASE_BOARD. SBT=BASE_BOARD.192". SBT=BASE_BOARD. //Add the IP address of an Ethernet port. PT=IMA. ST=UBR+. SCR=1821. ST=RTVBR. ADD IUBCP: CPPT=CCP.7". PEERIP="7. VCI=40. ST=RTVBR. RCR=3807. 2008-09-14 Huawei Confidential Page 90 of 133 . PN=0.255. //Add the IP address of the NodeB to serve as an OM channel. IP="10. JNRSCGRP=DISABLE. 2.0". JNRSCGRP=DISABLE. SBT=BASE_BOARD.0". MASK="255. SPEED=100M. SN=6. PAT=RT. SN=6. BEAR=ATM.7. SN=7.INTERNAL IPRAN Deployment Guide JNRSCGRP=DISABLE. CPPN=0.7. SBT=BASE_BOARD. Configure the Parameters Related to IP Transport (1)To configure the parameters for the layer 2 networking. ARPPROXY=DISABLE. SN=7. SRN=0. SRN=0. ADD AAL2PATH: NT=LOCAL. DUPLEX=FULL. ADD IUBCP: CPPT=NCP. PAT=RT. MBS=1000. VCI=41. PT=IMA. LN=1.255.7. MBS=1000. VPI=1. VPI=1. ADD AAL2PATH: NT=LOCAL. SET ETHPORT: SRN=0.255.  Add an OM channel.  Add the data on the user plane ADD IPPATH: PATHID=1. BEAR=ATM. ADD DEVIP: SRN=0.7. PCR=32. MTU=1500. VPI=1. PN=0. VCI=36. FERAT=100. //Add the data on the Iub interface. PT=ETH. PATHID=1. RCR=3807. PCR=3808. PT=ETH. SN=7.255.10. ST=CBR. SRN=0. BEAR=ATM. LN=0. PN=0. SN=6. ADD OMCH: IP="7. CDVT=10240. ADDR="H'45000006582414723F0000000000000000000000". SCR=1821. //Add the data on the user plane ADD AAL2NODE: NT=LOCAL. SRN=0. do as follows:  Add the configuration at the physical layer //Set the attributes for an Ethernet port.1". PT=IMA.10. 16.  Configure a VLAN ADD VLANMAP: NEXTHOPIP="10. 2008-09-14 Huawei Confidential Page 91 of 133 . TFT=NRT. SRN=0. VLANID=100. ADD IPPATH: PATHID=2. SBT=BASE_BOARD. RNCIP="10. VLANPRIO=2. SET VLANCLASS: VLANGROUPNO=0. PT=ETH.16.255. RNCIP="10.10. ADD IPPATH: PATHID=1. SET VLANCLASS: VLANGROUPNO=0. //Add IP paths. INSTAG=ENABLE. TXEBS=0.  Add the data on the user plane. PT=ETH. TFT=HSPA_NRT. NODEBIP="10.10. SN=6.10. TXCBS=10000000. VLANPRIO=1.2". INSTAG=ENABLE. FPMUXSWITCH=DISABLE.10. TXEBS=0.1". DSTIP="10. SBT=BASE_BOARD. TXBW=20000.192".10. //Add an IP route.1". PT=ETH.2". NODEBIP="10. RXBW=20000.10. VLANGROUPNO=0.16. TXEBS=0. NODEBIP="16.255.2".16. do as follows: ADD DEVIP: SRN=0. RXBW=20000.2". SET VLANCLASS: VLANGROUPNO=0. SN=6.. SBT=BASE_BOARD.10.10. TXBW=20000. PT=ETH. DSCP=18.10.255. MASK="255. TRAFFIC=USERDATA. (2)To configure the parameters for the layer 3 networking.2".16. SBT=BASE_BOARD. PN=0.10. RXBW=20000.2". SRVPRIO=18. SN=6.10. IP="16. DSTMASK="255. VLANPRIO=3.0". TXBW=20000.16. RXBW=20000. SRN=0. JNRSCGRP=DISABLE. VLANMODE=VLANGROUP. TXCBS=10000000. SN=6.10. TFT=HSPA_NRT. FPMUXSWITCH=DISABLE. JNRSCGRP=DISABLE. TRAFFIC=USERDATA.10.192". FPMUXSWITCH=DISABLE. TRAFFIC=OTHER. SRN=0.255. DSCP=10. TXCBS=10000000. NODEBIP="16. DSCP=18. VLANID=100.10. TFT=NRT. INSTAG=ENABLE.16. NEXTHOP="16.1". ADD IPRT: SRN=0. DSCP=10. TXBW=20000.16. SRVPRIO=10. TXEBS=0.INTERNAL IPRAN Deployment Guide JNRSCGRP=DISABLE. RTTYPE=NEXTHOP. RNCIP="10. TXCBS=10000000. SBT=BASE_BOARD.2". RNCIP="10. FPMUXSWITCH=DISABLE. VLANID=100. SN=6.1". ADD IPPATH: PATHID=2.10.10. JNRSCGRP=DISABLE. INTERNAL IPRAN Deployment Guide Chapter 6 Example of IU/IUR Interface Configuration 6. 6.2 IU/IUR Interface Protocol Stack Figure 1.23 IP protocol stack of IU-PS interface 2008-09-14 Huawei Confidential Page 92 of 133 . The configuration of the IUCS is based on the RNC210 052.1 Version Description The configurations of IUPS and IUR are based on the RNC210 051. 24 IP protocol stack of IU-CS interface Figure 1.INTERNAL IPRAN Deployment Guide Figure 1.25 IP protocol stack of IUR interface 2008-09-14 Huawei Confidential Page 93 of 133 . IPTYPE=PRIMARY.255.129".26 IUPS data planning 6.18.3. OAMFLOWBW=0.65. PN=0. 6.154) S G S N Router Gateway IP : 172.2 Configuring Physical Layer Data  Set the Ethernet port attribute //Set the Ethernet port attributes to ensure the consistency of the FE port attribute between the RNC and the interconnected device.62.31. The device IP is used as the local address of the SCTPLNK and IPPATH. FCINDEX=0. FE IP: 172. 18) 202. //Add the device IP address of the board.3. BRDTYPE=GOU. SN=24. Figure 6-4 shows specific IP addresses. The value is optional.243. //Add the IP address of the Ethernet port. PN=0.3 Adding Control Plane Data of Iu-PS Interface General configuration procedures: 2008-09-14 Huawei Confidential Page 94 of 133 .123.3.3 Procedures of IU PS Configuration (IP) 6. MASK="255. FLOWCTRLSWITCH=ON.18.255. SN=24. MTU=1500.INTERNAL IPRAN Deployment Guide 6.201 Figure 1.248". AUTO=ENABLE.134/29 G G S N User IP: 172.(153. IPADDR="172.1 IP Addresses Planning Note: This section describes the IP address planning by using the GOU board in Slot 24 in Subrack 0 as an example. ADD ETHIP: SRN=0.16.18.129/29 G O U Sig IP: 172.16.62.(14. SET ETHPORT: SRN=0.62.16. CROSSIPFLAG=UNAVAILABLE. DSCP=62. LOGPORTFLAG=NO.62. RTOINIT=1000. Note:  PSP-IPSP transfer networking A I PSP 0xA75 B I PSP 0xB85 C I PSP 0xC95 Figure 1.27 PSP-IPSP transfer networking 2008-09-14 Huawei Confidential Page 95 of 133 . BEARTYPE=M3UA.123. CHKSUMTYPE=CRC32. DPCT=IUPS. SN=2. NEIGHBOR=YES. PEERIPADDR1="172. MAXPATHRETR=2.154". APP=M3UA. MTU=1500. LOCIPADDR1="172. ADD SCTPLNK:SRN=0. //Run ADD M3LE to add one M3UA local entity. DSCP=62. CHKSUMTX=NO. DPC=H'000515.INTERNAL IPRAN Deployment Guide (OPC --> N7DPC )--> M3LE --> M3DE --> M3LKS --> M3RT --> M3LNK //Run ADD SCTPLNK to add one SCTP signaling link. RTOALPHA=12. CROSSIPFLAG=UNAVAILABLE.18. LOGPORTFLAG=NO. ADD N7DPC: DPX=3. ADD M3LE: LENO=0. CHKSUMTYPE=CRC32. CHKSUMRX=NO. PEERPORTNO=8625. NAME="ROC HW SGSN". CHKSUMRX=NO. RTOBETA=25. HBINTER=1000. ADD SCTPLNK:SRN=0. SLSMASK=B0000. run the command for multiple times. RTCONTEXT=4294967295. NAME="ROC_RNC12". MAXPATHRETR=2. //Run ADD N7DPC to add one DPC. STP=OFF. RTOINIT=1000. SWITCHBACKHBNUM=10. RTOMIN=1000. ENTITYT=M3UA_IPSP. MODE=CLIENT. LOCPTNO=8525. MAXASSOCRETR=4. LOCPTNO=8526. HBINTER=1000. VLANFLAG=DISABLE. SN=4. To add more SCTP links. SWITCHBACKHBNUM=10.153". Set Work mode to Client/SERVER (the SGSN is Server and the RNC is Client). SCTPLNKN=1. RTOMIN=1000. RTOMAX=3000. SCTPLNKN=0. Set Application Type to M3UA. CHKSUMTX=NO. MODE=CLIENT. SSN=1.16. RTOALPHA=12. PROT=ITUT. RTOMAX=3000.18. PEERPORTNO=8626. LOCIPADDR1="172. APP=M3UA. VLANFLAG=DISABLE. SWITCHBACKFLAG=YES.129". RTOBETA=25. SWITCHBACKFLAG=YES.123. PEERIPADDR1="172.129". SSN=2.62. MAXASSOCRETR=4. MTU=1500.16. To configure three channels. ADD M3DE: DENO=3. and C) entities exist. ENTITYT=M3UA_IPSP. //Run ADD M3LKS to add the M3UA link set. Otherwise. their DPCs use the UMG as the proxy. ADD M3LKS: SIGLKSX=3.INTERNAL IPRAN Deployment Guide Three M3 (A. Huawei Confidential Page 96 of 133 . B functions as the proxy. B. DPX=3. B corresponds to 0xB85. C corresponds to 0xC95. PDTMRVALUE=5. set Signaling Link Mask to B0111. A is connected to C through the transfer in B. A corresponds to 0xA75. LNKSLSMASK=B1111. NAME="to ROC HW SGSN". If B is the UMG with the connection of NEs. RTCONTEXT=4294967295. the scenario is applied seldom. To implement the M3UA link load sharing.29 ASP-SGP transfer networking //Run ADD M3DE to add one M3UA destination entity. or through one direct connection line. NAME="ROC HW SGSN". LENO=0. TRAMODE=M3UA_LOADSHARE_MOD.28 ASP-SGP direct connection networking In this networking mode. WKMODE=M3UA_IPSP.  ASP-SGP transfer networking A ASP 0xA75 B SGP SS7 C SS7 0xB85 0xC95 Figure 1. 2008-09-14 DENO=3. do as follows:  ASP-SGP direct connection networking A ASP B SGP 0xB85 0xA75 Figure 1. AF22DSCP=18. DPX=3. NAME="to ROC HW SGSN". Set Node type to IUPS. ADD TRMMAP:TMI=6. run the command for multiple times. To add more M3UA links. 6. SN=4. To add more mapping records. SSN=2. AF13DSCP=10. CNLOADSTATUS=NORMAL. CNDOMAINID=PS_DOMAIN. Signaling Link Mask should be set to B0111 by running the command ADD M3LKS. AF43DSCP=38. SN=2. AF31DSCP=30. ADD CNNODE: CNOPINDEX=0. AF21DSCP=18. NODET=IUPS. SRN=0. AF33DSCP=30. SIGLNKID=0. ADD M3RT: DENO=3. AVAILCAP=65535. NMO=MODE2. SIGLNKID=1. Set IU trans bearer type to IP_TRANS. AF12DSCP=10. AF11DSCP=10. TNLBEARERTYPE=IP_TRANS. AF42DSCP=38. NAME="ROC HW SGSN". it is recommended that Signaling Route Mask should be set to B1000 by running the command ADD N7DPC. SRN=0.4 Adding the Mapping Relation of Transport Resources of Neighbor Nodes //Run ADD TRMMAP to add one mapping relation record between a transport and a service. ADD M3LNK:SIGLKSX=3. LNKREDFLAG=M3UA_MASTER_MOD. LNKREDFLAG=M3UA_MASTER_MOD. //Run ADD FACTORTABLE to add one activity factor record. AF23DSCP=18. NAME="to ROC HW SGSN_0". //Run ADD CNNODE to add the CN node. ADD ADJNODE:ANI=3. Transport type to IP. The two items are required by running ADD ADJNODE. Note: The two items are mandatory. CNPROTCLVER=R6. TRANST=IP. run the command for multiple times. //Run ADD M3RT to add the M3UA route. PRIORITY=0. SGSNFLG=YES. SSN=1. ADD M3LNK:SIGLKSX=3. CNID=1. DPX=3. CNDOMAINID=PS_DOMAIN. EFDSCP=46. PRIORITY=0. Set CN domain ID to PS_DOMAIN. //Run ADD M3LNK to add the M3UA link. NAME="to ROC HW SGSN_1". ADD CNDOMAIN: DRXCYCLELENCOEF=6. PRIORITY=0. AF32DSCP=30. 2008-09-14 Huawei Confidential Page 97 of 133 . BEDSCP=0. AF41DSCP=38.INTERNAL IPRAN Deployment Guide Note: To implement the signaling route load sharing. SCTPLNKN=0. //Run ADD ADJNODE to add one transport neighbor node. SCTPLNKN=1.3. Set CN domain ID to PS_DOMAIN. //Run ADD CNDOMAIN to add the CN domain. SIGLKSX=3. ITFT=IUPS. PATHT=HQ_QOSPATH. CARRYFLAG=NULL.255. PSCONVDL=70.129". CARRYEN=0. PERIOD=5. SRBDL=15. BWDCONGCLRBW=0. PATHID=4. BWDCONGBW=0. ECHOIP="202. //Run ADD ADJMAP to add one activity factor record to configure the corresponding transport resource mapping table for different levels of subscribers. PSBKGUL=100.201". FPMUX=NO.18. ADD PORTCTRLER: SRN=0. HDCONVDL=70.16". PEERMASK="255. HDSRBDL=50.255.16. GENCCHDL=70. BWDHORSVBW=0. SRBUL=15. //Run ADD IPPATH to add one IP PATH. RXBW=5088. PATHT=HQ_QOSPATH. PERIOD=5. PT=ETHER.18. CHECKCOUNT=5.255".31. PERIOD=5. PATHCHK=ENABLED. HDINTERDL=100.255. RXBW=5088.16. FWDHORSVBW=0. IPADDR="172.65. VOICEDL=70.5 Adding User Plane Data of Iu-PS Interface //Run ADD PORTCTRLER to add transport resources for the designated port to manage and control the SPUa subsystem. VOICEUL=70. FWDCONGBW=0. PSCONVUL=70.14". PSINTERDL=100. PATHCHK=ENABLED. BWDHORSVBW=0. BWDCONGBW=0. run the command for multiple times. BWDHORSVBW=0.16.31. FWDCONGCLRBW=0. FWDCONGCLRBW=0. 6.255. FWDCONGBW=0. HUCONVUL=70. RXBW=1000000.3.16. CSSTRMUL=100. FWDCONGCLRBW=0. TMISLV=6. FWDHORSVBW=0. PEERMASK="255. FWDCONGBW=0. ECHOIP="172. HDBKGDL=100. GENCCHUL=70.255". FWDCONGCLRBW=0. 2008-09-14 Huawei Confidential Page 98 of 133 . BWDCONGBW=0. HUSTRMUL=100. CHECKCOUNT=5. CTRLSN=2. PATHT=HQ_QOSPATH.243. TMIBRZ=6. PATHID=3.255".18. IPADDR="172. HDSTRMDL=100. ADD ADJMAP: ANI=3. ECHOIP="172. FTI=6. CSCONVDL=100. PSBKGDL=100. ICMPPKGLEN=64. TXBW=5088.255. FPMUX=NO. CSSTRMDL=100. ADD IPPATH: ANI=3. To add more IP PATHs. BWDHORSVBW=0. PEERIPADDR="202. TXBW=1000000.62. HUBKGUL=100. TXBW=5088. PEERIPADDR="172.201".243. FWDHORSVBW=0. CARRYFLAG=NULL. VLANFLAG=DISABLE.129".62. HUSRBUL=50. PSSTRMDL=100. TMIGLD=6. MBMSCCHDL=100. BWDCONGCLRBW=0. PSINTERUL=100.129". BWDCONGBW=0. ICMPPKGLEN=64. CTRLSSN=2. BWDCONGCLRBW=0. VLANFLAG=DISABLE.14". IPADDR="172.65. CSCONVUL=100. FWDCONGBW=0. PEERIPADDR="172. ADD IPPATH:ANI=3. CARRYFLAG=NULL.255. VLANFLAG=DISABLE. HUINTERUL=100.16".INTERNAL IPRAN Deployment Guide ADD FACTORTABLE:FTI=6. PEERMASK="255. BWDCONGCLRBW=0.31. REMARK="FOR RNC12 IUPS USER". SN=24. PATHID=0. and configure the activity factor table. CNMNGMODE=SHARE. ADD IPPATH: ANI=3. PSSTRMUL=100. PATHCHK=ENABLED.62. FPMUX=NO. FWDHORSVBW=0.31. REMARK="For NSN RNC4". ADD IPRT: SRN=0. PRIORITY=HIGH.16.31. DESTIP="172.16". BWDHORSVBW=0.62.123. FWDCONGBW=0.255. PRIORITY=HIGH.134". BWDCONGCLRBW=0. MASK="255. FWDCONGCLRBW=0. PRIORITY=HIGH. ADD IPRT: SRN=0.255.18.134". ADD IPRT: SRN=0.255".16. //Run ADD IPRT to add the IP route in the user plane (the user plane route is optional and is configured when L3 networking is used between the RNC and the CS). SN=24. PATHID=5. DESTIP="172. NEXTHOP="172. TXBW=5088. ADD IPRT: SRN=0. REMARK="For NSN RNC3".18.255.134". PERIOD=5.62.134".18".1 IP Addresses Planning Note: This section describes the IP address planning by using the GOU board in Slot 14 in Subrack 0 as an example.62. MASK="255. DESTIP="172. PRIORITY=HIGH.255". IPADDR="172. PEERIPADDR="172. 2008-09-14 Huawei Confidential Page 99 of 133 .62.18. ECHOIP="172.255.255. FWDHORSVBW=0.18".16.31. PATHCHK=ENABLED. NEXTHOP="172.31.255.255. CHECKCOUNT=5.18. Figure 6-4 shows specific IP addresses. VLANFLAG=DISABLE. SN=24. SN=24.255". PEERMASK="255.31.255.153".255.31. SN=24.255. DESTIP="172. MASK="255.18.255". ADD IPPATH: ANI=3.16. NEXTHOP="172.129".123. MASK="255.255. FPMUX=NO. DESTIP="172. MASK="255. REMARK="to ROC HW SGSN CP_0".INTERNAL IPRAN Deployment Guide CHECKCOUNT=5.4 Procedures of IU CS Configuration (IP) 6.134". REMARK="For NSN RNC5".255". NEXTHOP="172.14". ICMPPKGLEN=64. ADD IPRT: SRN=0.16.4.62. PATHT=HQ_QOSPATH. //Add the signaling plane route.16.16.18". 6. SN=24.62.255".18. BWDCONGBW=0. REMARK="to ROC HW SGSN CP_1". PRIORITY=HIGH. NEXTHOP="172.255. CARRYFLAG=NULL. RXBW=5088.154". ICMPPKGLEN=64. INTERNAL IPRAN Deployment Guide User IP FE IP M G W : 10 .210 .1 .52 G O U DEV IP : 10 .210 .1 .37 Router M S C Gateway IP : 10 .210 .1 .49 /29 : 10 .210 .1 .4 5 /30 (Sig ) 10 .210 .1 .4 1 /30 (User ) Sig IP : 10 .210 .1 .69 Figure 1.30 IUCS data planning 6.4.2 Configuration of Physical Layer Data For configurations of other boards such as UOI, POU, and PEU, see the initial configuration guide. //Run SET ETHPORT to set the Ethernet port attributes. SET ETHPORT: SRN=0, SN=14, BRDTYPE=GOU, PN=0, MTU=1500, AUTO=DISABLE, FC=OFF, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=0; //Run ADD ETHIP to add the IP address of the Ethernet port. ADD ETHIP: SRN=0, SN=14, PN=0, IPADDR="10.210.1.52", MASK="255.255.255.248"; IPTYPE=SECOND, IPINDEX=1, // (Optional) Run ADD DEVIP to add the device IP address of the board. ADD DEVIP: SRN=0, SN=14, IPADDR="10.210.1.45", MASK="255.255.255.252"; ADD DEVIP: SRN=0, SN=14, IPADDR="10.210.1.41", MASK="255.255.255.252"; Note: The device IP is used as the local address of the SCTPLNK and IPPATH. 6.4.3 Adding Control Plane Data of Iu-CS Interface General configuration procedures: (OPC --> N7DPC )--> M3LE --> M3DE --> M3LKS --> M3RT --> M3LNK //Run ADD SCTPLNK to add one SCTP signaling link. To add more SCTP links, run the command for multiple times. Set Work mode to Client/SERVER (the RNC is Client). Set Application Type to M3UA. 2008-09-14 Huawei Confidential Page 100 of 133 INTERNAL IPRAN Deployment Guide ADD SCTPLNK:SRN=0, SN=2, SSN=0, SCTPLNKN=0, MODE=CLIENT, APP=M3UA, DSCP=62, LOCPTNO=5000, LOCIPADDR1="10.210.1.45", PEERIPADDR1="10.210.1.69", PEERPORTNO=5000, LOGPORTFLAG=NO, RTOMIN=1000, RTOMAX=3000, RTOINIT=1000, RTOALPHA=12, RTOBETA=25, HBINTER=1000, MAXASSOCRETR=4, MAXPATHRETR=2, CHKSUMTX=NO, CHKSUMRX=NO, CHKSUMTYPE=CRC32, MTU=1500, VLANFLAG=ENABLE, VLANID=102, CROSSIPFLAG=UNAVAILABLE, SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=10; ADD SCTPLNK:SRN=0, SN=2, SSN=1, SCTPLNKN=1, MODE=CLIENT, APP=M3UA, DSCP=62, LOCPTNO=5002, LOCIPADDR1="10.210.1.45", PEERIPADDR1="10.210.1.69", PEERPORTNO=5002, LOGPORTFLAG=NO, RTOMIN=1000, RTOMAX=3000, RTOINIT=1000, RTOALPHA=12, RTOBETA=25, HBINTER=1000, MAXASSOCRETR=4, MAXPATHRETR=2, CHKSUMTX=NO, CHKSUMRX=NO, CHKSUMTYPE=CRC32, MTU=1500, VLANFLAG=ENABLE, VLANID=102, CROSSIPFLAG=UNAVAILABLE, SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=10; //Run ADD N7DPC to add one DPC. To add more DPCs, run the command for multiple times. ADD N7DPC: DPX=0, DPC=H'000972, SLSMASK=B0000, NEIGHBOR=YES, NAME="MSC1", DPCT=IUCS_RANAP, STP=OFF, PROT=ITUT, BEARTYPE=M3UA; ADD N7DPC: DPX=1, DPC=H'000973, SLSMASK=B0000, NEIGHBOR=YES, NAME="MGW4M01", DPCT=IUCS_ALCAP, STP=OFF, PROT=ITUT, BEARTYPE=M3UA; //Run ADD M3LE to add one M3UA local entity. ADD M3LE: LENO=0, NAME="RNC4M01"; ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295, //Run ADD M3DE to add one M3UA destination entity. ADD M3DE: DENO=0, LENO=0, DPX=0, RTCONTEXT=4294967295, NAME="IUCS-MSC1"; ENTITYT=M3UA_IPSP, //Run ADD M3LKS to add the M3UA link set. ADD M3LKS: SIGLKSX=0, TRAMODE=M3UA_LOADSHARE_MOD, NAME="IUCS-MSC1"; DENO=0, LNKSLSMASK=B1111, WKMODE=M3UA_IPSP, PDTMRVALUE=5, Note: To implement the signaling route load sharing, it is recommended that Signaling Route Mask should be set to B1000 by running the command ADD N7DPC. Signaling Link Mask should be set to B0111 by running the command ADD M3LKS. //Run ADD M3RT to add the M3UA route. 2008-09-14 Huawei Confidential Page 101 of 133 INTERNAL IPRAN Deployment Guide ADD M3RT: DENO=0, SIGLKSX=0, PRIORITY=0, NAME="IUCS-RANP1"; //Run ADD M3LNK to add the M3UA link. To add more M3UA links, run the command for multiple times. ADD M3LNK:SIGLKSX=0, SIGLNKID=0, SRN=0, SN=2, SSN=0, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="CS1-0"; SCTPLNKN=0, ADD M3LNK:SIGLKSX=0, SIGLNKID=1, SRN=0, SN=2, SSN=1, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="CS1-1"; SCTPLNKN=1, //Run ADD ADJNODE to add one transport neighbor node. Set Node type to IUCS, Transport type to IP. ADD ADJNODE: ANI=1700, NAME="MGW4M01", NODET=IUCS, DPX=1, TRANST=IP; //Run ADD CNDOMAIN to add the CN domain. Set CN Domain Flag to CS_DOMAIN. ADD CNDOMAIN: CNDOMAINID=CS_DOMAIN, DRXCYCLELENCOEF=6; T3212=10, ATT=ALLOWED, //Run ADD CNNODE to add the CN node. Set CN domain Flag to CS_DOMAIN. Set IU trans bearer type to IP_TRANS. ADD CNNODE: CNOPINDEX=0, CNID=1, CNDOMAINID=CS_DOMAIN, DPX=0, CNPROTCLVER=R5, SUPPORTCRTYPE=CR529_SUPPORT, CNLOADSTATUS=NORMAL, AVAILCAP=1000, TNLBEARERTYPE=IP_TRANS, RTCPSWITCH=OFF; 6.4.4 Adding the Mapping Relation of Transport Resources of Neighbor Nodes //Run ADD TRMMAP to add one mapping relation record between the transport and service. To add more mapping records, run the command for multiple times. ADD TRMMAP:TMI=1, ITFT=IUB_IUR_IUCS, TRANST=IP, EFDSCP=46, AF43DSCP=38, AF42DSCP=36, AF41DSCP=34, AF33DSCP=30, AF32DSCP=28, AF31DSCP=26, AF23DSCP=22, AF22DSCP=20, AF21DSCP=18, AF13DSCP=14, AF12DSCP=12, AF11DSCP=10, BEDSCP=0, CCHPRIPATH=HQ_IPRT, CCHSECPATH=NULL, SRBPRIPATH=HQ_IPRT, SRBSECPATH=NULL, VOICEPRIPATH=HQ_IPRT, VOICESECPATH=NULL, CSCONVPRIPATH=HQ_IPRT, CSCONVSECPATH=NULL, CSSTRMPRIPATH=HQ_IPRT, CSSTRMSECPATH=NULL, PSCONVPRIPATH=HQ_IPRT, PSCONVSECPATH=NULL, PSSTRMPRIPATH=HQ_IPRT, PSSTRMSECPATH=NULL, PSHIGHINTERACTPRIPATH=HQ_IPNRT, PSHIGHINTERACTSECPATH=NULL, PSMIDINTERACTPRIPATH=HQ_IPNRT, PSMIDINTERACTSECPATH=NULL, PSLOWINTERACTPRIPATH=HQ_IPNRT, PSLOWINTERACTSECPATH=NULL, PSBKGPRIPATH=HQ_IPNRT, PSBKGSECPATH=NULL, HDSRBPRIPATH=HQ_IPHDRT, HDSRBSECPATH=NULL, 2008-09-14 Huawei Confidential Page 102 of 133 CNMNGMODE=SHARE. //Run ADD IPPATH to add one IP PATH. PSBKGUL=100.1. HDBKGDL=100. BWDCONGCLRBW=0. HDMIDINTERACTSECPATH=NULL. TMIBRZ=1. CSSTRMDL=100. HDSRBDL=50. HUINTERUL=100. ADD PORTCTRLER: SRN=0. 6. FWDCONGCLRBW=0. ADD FACTORTABLE:FTI=1. CTRLSSN=0. HUMIDINTERACTSECPATH=NULL. CSCONVDL=100. The two items are required by running the command ADD ADJMAP. and configure the activity factor table. HUCONVPRIPATH=HQ_IPHURT. PSCONVUL=70. CSCONVUL=100. Page 103 of 133 . BWDCONGBW=0.4.210. ADD ADJMAP: ANI=1700. PATHT=RT. TMIGLD=1. PSBKGDL=100. HUBKGPRIPATH=HQ_IPHUNRT. SN=14. FWDCONGBW=0. REMARK="IUCS". GENCCHUL=70. HDLOWINTERACTSECPATH=NULL. HDHIGHINTERACTPRIPATH=HQ_IPHDNRT. HULOWINTERACTSECPATH=NULL. PSINTERDL=100. PT=ETHER. CSSTRMUL=100. HUCONVSECPATH=NULL. PSSTRMUL=100. SRBDL=15. HUSTRMPRIPATH=HQ_IPHURT. PSCONVDL=70. SRBUL=15. HUSRBPRIPATH=HQ_IPHURT. HDMIDINTERACTPRIPATH=HQ_IPHDNRT. HDBKGSECPATH=NULL. HDCONVSECPATH=NULL. PSSTRMDL=100. To add more IP PATHs. //Run ADD FACTORTABLE to add one activity factor record. run the command for multiple times. HUCONVUL=70. GENCCHDL=70. MBMSCCHDL=100. HDSTRMPRIPATH=HQ_IPHDNRT. Note: The two items are mandatory. HUHIGHINTERACTSECPATH=NULL. VOICEUL=70. PATHID=0. BWDHORSVBW=0. HDSTRMSECPATH=NULL.INTERNAL IPRAN Deployment Guide HDCONVPRIPATH=HQ_IPHDRT. HUSRBSECPATH=NULL. Huawei Confidential IPADDR="10. HUBKGSECPATH=NULL. HDLOWINTERACTPRIPATH=HQ_IPHDNRT. HDCONVDL=70. HUSRBUL=50. HUBKGUL=100. HUSTRMUL=100.41". PSINTERUL=100. HDINTERDL=100. HUMIDINTERACTPRIPATH=HQ_IPHUNRT. HDSTRMDL=100. //Run ADD ADJMAP to add one activity factor record to configure the corresponding transport resource mapping table for different levels of subscribers. CTRLSN=2.5 Adding User Plane Data of Iu-CS Interface //Run ADD PORTCTRLER to add transport resources for the designated port to manage and control the SPUa subsystem. HDBKGPRIPATH=HQ_IPHDNRT. VOICEDL=70. HULOWINTERACTPRIPATH=HQ_IPHUNRT. CARRYEN=0. HUHIGHINTERACTPRIPATH=HQ_IPHUNRT. FTI=1. TMISLV=1. ADD IPPATH: 2008-09-14 ANI=1700. HDHIGHINTERACTSECPATH=NULL. FWDHORSVBW=0. HUSTRMSECPATH=NULL. ECHOIP="10.1.65/29 G O U Other RNC Router G O U Gateway IP: 172. CHECKCOUNT=5. PATHCHK=ENABLED.248". BWDCONGCLRBW=0.18. MASK="255.18. MASK="255.210.37".31 IUR data planning 6.5.73". PRIORITY=HIGH.70/29 Figure 1.2 Configuration of Physical Layer Data For configurations of other boards such as UOI.INTERNAL IPRAN Deployment Guide PEERIPADDR="10. BWDHORSVBW=0. POU.1.62.32".255. REMARK="MGW4M01". RXBW=1000000.210. //Add the user plane route. 6.1. NEXTHOP="10.210.49". SN=14.62.1 IP Addresses Planning Note: This section describes the IP address planning by taking the GOU board in Slot16 of Subrack 0 as an example.5.37". REMARK="MSC1". VLANID=101. FWDCONGBW=0. TXBW=1000000.255. BWDCONGBW=0. NEXTHOP="10.64".65/29 FE IP: 172. SN=14. //Run ADD IPRT to add the IP route (it is configured when L3 networking is used between the RNC and the CS).255. ADD IPRT: SRN=0. FWDCONGCLRBW=0. DSCP=46. //Add the signaling plane route. DESTIP="10. PRIORITY=HIGH. FE IP: 172.210.30.1.255. ADD IPRT: SRN=0.210. FWDHORSVBW=0. and PEU.248". PEERMASK="255. ICMPPKGLEN=64.18.210.248".255.5 Procedures of IUR Configuration (IP) 6. 2008-09-14 Huawei Confidential Page 104 of 133 . PERIOD=5. VLANFLAG=ENABLE.1. DESTIP="10. see the initial configuration guide.1.255. SLSMASK=B0000.18. run the command for multiple times. //Run ADD NRNC to add the neighbor RNC information. BRDTYPE=GOU. SSN=3. DPCT=IUR. Note: The device IP is used as the local address of the SCTPLNK and IPPATH. DPC=H'000579. For the type.18. PN=0. //Run ADD ETHIP to add the IP address of the Ethernet port. SET ETHPORT: SRN=0. SUPPIURCCH=NO. MODE=SERVER. PN=0.255. //Run ADD N7DPC to add one DPC. SWITCHBACKFLAG=YES. RTOALPHA=12. SWITCHBACKHBNUM=10.65".INTERNAL IPRAN Deployment Guide //Run SET ETHPORT to set the Ethernet port attributes. IUREXISTIND=TRUE. CHKSUMRX=NO. PEERIPADDR1="172. SHOTRIG=CS_SHO_SWTICH-1&HSPA_SHO_SWITCH1&NON_HSPA_SHO_SWTICH-1.30. ADD ETHIP: SRN=0. DSCP=62. SCTPLNKN=0. STP=OFF. DSCRIND=FALSE. AUTO=ENABLE. IURHSUPASUPPIND=OFF. select the IUR interface. IURHSDPASUPPIND=OFF. FCINDEX=0. OAMFLOWBW=0. RTOINIT=1000. RTOMAX=3000. RTOMIN=1000. SERVICEIND=SUPPORT_CS_AND_PS. PEERPORTNO=9000. IPTYPE=PRIMARY. ADD SCTPLNK:SRN=0. VLANFLAG=DISABLE. FLOWCTRLSWITCH=ON. SN=2. //Run ADD M3DE to add one M3UA destination entity. NEIGHBOR=YES.248". 2008-09-14 Huawei Confidential Page 105 of 133 . RNCPROTCLVER=R6.18. DPX=11. CHKSUMTYPE=CRC32. HHORELOCPROCSWITCH=DL_DCCH_SWITCH-0&IUR_TRG_SWITCH-0.3 Adding Control Plane Data of Iur Interface General configuration procedures: (OPC --> N7DPC)--> M3LE --> M3DE --> M3LKS --> M3RT --> M3LNK //Run ADD SCTPLNK to add one SCTP signaling link. BEARTYPE=M3UA. PROT=ITUT. ADD NRNC: NRNCID=11. STATEINDTMR=20. HHOTRIG=OFF.5.65".62. Set Application Type to M3UA. MTU=1500. // (Optional) Run ADD DEVIP to add the device IP address of the board. SN=16. APP=M3UA. Set Work mode to Client/SERVER (the RNC is Client). CHKSUMTX=NO. HBINTER=1000. MAXASSOCRETR=4.65".62. MTU=1500. RTOBETA=25. TNLBEARERTYPE=IP_TRANS. ADD N7DPC: DPX=11. 6. NAME="HW RNC11". CROSSIPFLAG=UNAVAILABLE. LOCIPADDR1="172. IPADDR="172. MASK="255. To add more SCTP links. LOGPORTFLAG=NO.255. SN=16. MAXPATHRETR=2. DENO=11. CSCONVSECPATH=NULL. WKMODE=M3UA_IPSP. SCTPLNKN=0. SSN=3. SIGLKSX=11. run the command for multiple times. CCHSECPATH=NULL. 2008-09-14 Huawei Confidential Page 106 of 133 . //Run ADD M3LKS to add the M3UA link set. PSCONVPRIPATH=HQ_IPRT. AF11DSCP=10. AF22DSCP=20. PSHIGHINTERACTPRIPATH=HQ_IPNRT. Signaling Link Mask should be set to B0111 by running the command ADD M3LKS. AF13DSCP=14. //Run ADD M3RT to add the M3UA route. AF41DSCP=34. SIGLNKID=0. SN=2. AF12DSCP=12. ADD M3LKS: SIGLKSX=11. Set Node type to IUCS. ADD ADJNODE: ANI=11. To add more mapping records. LNKSLSMASK=B1111. CSCONVPRIPATH=HQ_IPRT. ITFT=IUB_IUR_IUCS. SRBSECPATH=NULL. ADD M3LNK:SIGLKSX=11. PRIORITY=0. To add more M3UA links. VOICEPRIPATH=HQ_IPRT. AF31DSCP=26. ADD TRMMAP:TMI=1. NAME="M3RT BETWEEN RNC12 AND RNC 11". SRN=0. Transport type to IP.INTERNAL IPRAN Deployment Guide ADD M3DE: DENO=11. PSSTRMSECPATH=NULL. AF23DSCP=22. //Run ADD M3LNK to add the M3UA link. SRBPRIPATH=HQ_IPRT. NAME="Route from RNC12 To RNC11". TRANST=IP. TRAMODE=M3UA_LOADSHARE_MOD. PSCONVSECPATH=NULL. LNKREDFLAG=M3UA_MASTER_MOD. PDTMRVALUE=5. AF32DSCP=28. AF21DSCP=18. it is recommended that Signaling Route Mask should be set to B1000 by running the command ADD N7DPC. CSSTRMPRIPATH=HQ_IPRT. CSSTRMSECPATH=NULL. TRANST=IP. NAME="RNC12 To RNC 11". set Signaling Link Mask to B0111.5. RTCONTEXT=4294967295. PRIORITY=0. LENO=0. DPX=11. NAME="RNC11 DE". AF42DSCP=36. DPX=11. 6.4 Adding the Mapping Relation of Transport Resources of Neighbor Nodes //Run ADD ADJNODE to add one transport neighbor node. ENTITYT=M3UA_IPSP. To implement the M3UA link load sharing. Note: To implement the signaling route load sharing. NAME="to ROC_RNC11". EFDSCP=46. Adding the Mapping Relation of Transport Resources of Neighbor Nodes //Run ADD TRMMAP to add one mapping relation record between a transport and a service. NODET=IUR. VOICESECPATH=NULL. PSSTRMPRIPATH=HQ_IPRT. run the command for multiple times. CCHPRIPATH=HQ_IPRT. AF43DSCP=38. ADD M3RT: DENO=11. AF33DSCP=30. BEDSCP=0. PSCONVDL=70.5. PSINTERDL=100. HDSTRMSECPATH=NULL. FWDHORSVBW=0. TMIBRZ=1. VOICEUL=70. SRBDL=15. PT=ETHER. ADD PORTCTRLER: SRN=0. CSSTRMUL=100. HDHIGHINTERACTPRIPATH=HQ_IPHDNRT. HDLOWINTERACTSECPATH=NULL. GENCCHDL=70. CTRLSN=4. CNMNGMODE=SHARE. TMISLV=1. HUHIGHINTERACTPRIPATH=HQ_IPHUNRT. PSMIDINTERACTSECPATH=NULL. HUBKGSECPATH=NULL. and configure the activity factor table. FWDCONGCLRBW=0. ADD FACTORTABLE:FTI=1. CSCONVUL=100. HDCONVPRIPATH=HQ_IPHDRT. HUBKGPRIPATH=HQ_IPHUNRT. CSSTRMDL=100. VOICEDL=70. //Run ADD ADJMAP to add one activity factor record to configure the corresponding transport resource mapping table for different levels of subscribers. HDSRBSECPATH=NULL. HUSRBSECPATH=NULL. 6. //Run ADD FACTORTABLE to add one activity factor record. 2008-09-14 Huawei Confidential Page 107 of 133 . HULOWINTERACTSECPATH=NULL. PSCONVUL=70. HDBKGSECPATH=NULL. BWDHORSVBW=0. CTRLSSN=0. HDCONVSECPATH=NULL. HDLOWINTERACTPRIPATH=HQ_IPHDNRT. HDBKGPRIPATH=HQ_IPHDNRT. HUCONVUL=70. HDINTERDL=100. HDCONVDL=70. HUMIDINTERACTSECPATH=NULL. GENCCHUL=70. HDHIGHINTERACTSECPATH=NULL. SN=16. Note: 4 and 5 are mandatory.INTERNAL IPRAN Deployment Guide PSHIGHINTERACTSECPATH=NULL. SRBUL=15. HDSRBPRIPATH=HQ_IPHDRT. HDSTRMDL=100. CSCONVDL=100. The two items are required by running the command ADD ADJMAP. HDBKGDL=100. HUSTRMPRIPATH=HQ_IPHURT. PSBKGDL=100. HUSTRMUL=100. PSBKGPRIPATH=HQ_IPNRT. PSMIDINTERACTPRIPATH=HQ_IPNRT. REMARK="IUCS". PSBKGUL=100. TMIGLD=1. PSINTERUL=100. HUBKGUL=100. PSLOWINTERACTSECPATH=NULL. HDSRBDL=50. HUSTRMSECPATH=NULL. HUSRBUL=50. ADD ADJMAP: ANI=11. HDSTRMPRIPATH=HQ_IPHDNRT. HDMIDINTERACTPRIPATH=HQ_IPHDNRT. MBMSCCHDL=100. BWDCONGBW=0. HULOWINTERACTPRIPATH=HQ_IPHUNRT. FTI=1. PSBKGSECPATH=NULL. PSLOWINTERACTPRIPATH=HQ_IPNRT. HDMIDINTERACTSECPATH=NULL. PSSTRMDL=100. CARRYEN=0. HUCONVPRIPATH=HQ_IPHURT. HUHIGHINTERACTSECPATH=NULL. BWDCONGCLRBW=0. HUINTERUL=100. PSSTRMUL=100. HUMIDINTERACTPRIPATH=HQ_IPHUNRT. HUSRBPRIPATH=HQ_IPHURT.5 Adding User Plane Data of Iur Interface //Run ADD PORTCTRLER to add transport resources for the designated port to manage and control the SPUa subsystem. HUCONVSECPATH=NULL. FWDCONGBW=0. 70". PATHID=0.65". ICMPPKGLEN=64.18.18. Each ETH PORT using the Iu-PS interface is configured with one IP PATH. FWDCONGCLRBW=0. BWDHORSVBW=0. TXBW=1000000. PRIORITY=HIGH. REMARK="IUR IPRT BETWEEN RNC12 AND RNC11". enable the PING detection function of the IP PATH. SN=16. PERIOD=5. To add more IP PATHs.18. FWDHORSVBW=0. Difference of the configuration specifications between the M3UA and IuCS: The RNC is the Client of the IPSP. DESTIP="172.1 Configuration Specifications of Control Plane (IUPS-IP) 1.6 IU/IUR Configuration Specifications 6. CHECKCOUNT=5. PEERMASK="255. MASK="255. 6. the IP PATH bandwidth is set to the transport bandwidth. If the peer device supports the function. NEXTHOP="172.255. //Route of user plane and signaling plane (Peer signaling and user plane address are normalized) ADD IPRT: SRN=0.255.18. The type is QoS PATH. IPADDR="172. run the command for multiple times. RXBW=1000000. PATHCHK=ENABLED.255.30. BWDCONGBW=0. FPMUX=NO. //Run ADD IPRT to add the IP route (it is optional and configured when L3 networking is used between the RNC and the CS).INTERNAL IPRAN Deployment Guide //Run ADD IPPATH to add one IP PATH. FWDCONGBW=0.255". BWDCONGCLRBW=0. The SGSN is the Server of the IPSP.30. CARRYFLAG=NULL.2 Configuration Specifications of User Plane (IUPS-IP) 1. 4.255. PATHT=HQ_QOSPATH. 2. Other rules are the same as those of the Iu-CS. 3.62.6. 2.62. The SCCP timer configuration specification is the same as that of the IuCS.30.6. Configure the bandwidth for the IP PATH. the IP PATH bandwidth is configured to the port bandwidth. ECHOIP="172.18.65". ADD IPPATH:ANI=11. If the middle transport bandwidth is smaller than the port bandwidth.255".65". PEERIPADDR="172. VLANFLAG=DISABLE. 6. The port controller should distribute ports used in each subrack to all 2008-09-14 Huawei Confidential Page 108 of 133 . If the transport bandwidth is not limited.65". negotiate with the peer system about the M3LE route context of the RNC. all SCTP links corresponding to the M3UA should be set to dual home (each end uses two IPs). If the peer device supports the function. The type is QoS PATH. If the SCTP link is Client. the M3UA is also the Client. Each ETH PORT using the Iu-CS interface is configured with one IP PATH. 2. the M3UA is also the Server. 2. the IP PATH bandwidth is 2008-09-14 Huawei Confidential Page 109 of 133 .6. 3. If the middle transport bandwidth is smaller than the port bandwidth. 5. Configuration personnel should pay attention to this in the case of the negotiation of the work mode of the SCTP/M3UA with the peer system (in the IPSP-IPSP networking. 3.INTERNAL IPRAN Deployment Guide SPU subsystems on average. enable the PING detection function of the IP PATH. Note: If the peer system requires that the RNC must carry the route context in ASP ACTIVE message. It is recommended that the context of the M3UA local entity route should be set to 4294967295 (all F). the M3UA link in the Client mode originates the link establishment of the M3UA link). 6. Configure the bandwidth for the IP PATH. For the reliability.6. 4.3 Configuration Specifications of Control Plane (IUCS-IP) 1. Note: If the peer system requires the negotiation. the work mode of the linkset is configured to IPSP. The load-sharing mode is recommended (the active/standby flag of initialized bearer service of the M3UA link is the master mode). The service mode of the M3UA linkset requires the negotiation with the peer system. If the M3LE/M3DE is configured according to Table 2. The precedence of all links in the linkset must be the same. set the destination entity route context according to the route context provided by the peer system. 6. If the SCTP link used by the M3UA is the Server. RNC V29 binds the Client/Server of the M3UA with the Client/Server of the SCTP. if the peer system supports the SCTP dual-home. The context of the destination entity route should be set to 4294967295 (all F).4 Configuration Specifications of User Plane (IUCS-IP) 1. 6.5 Configuration Specifications of Control Plane (IUR-IP) 1. The work mode must be negotiated with the peer system.6. Configure the bandwidth for the IP PATH. If the middle transport bandwidth is smaller than the port bandwidth. That is. 6. specify who originates the link establishment. that is. If the transport bandwidth is not limited.6. Note: For version earlier than V29C01B063. Each ETH PORT using the Iur interface is configured with one IP PATH. 4. If the transport bandwidth is not limited. 2.6 Configuration Specifications of User Plane (IUR-IP) 1. The type is QoS PATH.INTERNAL IPRAN Deployment Guide set to the transport bandwidth. The port controller should distribute ports used in each subrack to all SPU subsystems on average. 6.7 Relevant Knowledge Points 6. the work mode is applicable to only the linkset mode. 4. 3. the IP PATH bandwidth is configured to the port bandwidth. the link establishment is originated in the IPSP client and ASP mode. the IP PATH bandwidth is set to the transport bandwidth.  Traffic Mode 2008-09-14 Huawei Confidential Page 110 of 133 . The M3UA configuration specifications are the same as the Iu-PS. configure the IP PATH for each NRNC user plane IP. If the peer device supports the function. At present. The SCCP timer configuration specification is the same as that of the IuCS. enable the PING detection function of the IP PATH.1 Two Modes  Work Mode The concept is used in the M3UA linkset.7. 2. At present. the IP PATH bandwidth is configured to the port bandwidth. The port controller should distribute ports used in each subrack to all SPU subsystems on average. the network segment configuration of the user plane IP is not supported. for example. 6. The bearer should be distributed on all ports of the Iu-CS on average. The number of configured M3UA links must be smaller than or equal to 2^n. the system compares Traffic Mode with Traffic Mode configured at the peer system. the system discards this message and returns one ERROR (AS traffic mode is not matched). 6. The information is carried in the ASP Active message. AS.7. The highest state of the AS can be only INACTIVE.INTERNAL IPRAN Deployment Guide The traffic mode requires the negotiation with the peer system. If both are inconsistent. t xt For the IUPS/IUR example of Singapore M1.2 Relation between Signaling Link and Mask The signaling link mask of the M3UA linkset should meet the following two conditions: 1) The number (n) of 1 in the mask determines the maximum number of links (2^n) for the load sharing. Number of Subracks Number of M3UA Links Signaling Mask 1 2 B0001 2 4 B0011 3 4 B0011 4 8 B0111 5 8 B0111 6 8 B0111 Link Remark The SPU subsystem terminated in the M3UA should be distributed in subracks and SPMs on average. 2) The AND operation between this value and Signaling Route Mask configured in the N7DPC must be 0. At the end where the ASP Active message is received. The traffic mode cannot serve the SCCP.8 Configuration Example of Current Network For the IUCS example in Paraguay.20080712050252(巴拉圭V21052). see the following attachment: 2008-09-14 Huawei Confidential Page 111 of 133 . see the following attachment: C: \ Document s and Set t i ngs\ user\ 桌面\ I PRAN开局指导书\ CFGMML. INTERNAL IPRAN Deployment Guide C: \ Document s and Set t i ngs\ user\ 桌面\ I PRAN开局指导书\ 新加坡——CFGMML. t xt 2008-09-14 Huawei Confidential Page 112 of 133 .20080611134355. 1 Principles and Basic Configuration Procedures Figure 7-1 shows the maintenance of the NodeB through the O&M channel of the RNC.1. packets are forwarded to the NodeB through the PPP/MLPPP/FE/GE. If the transport type of the NodeB is IUB-ATM. General configuration procedures:  ADD EMSIP: Configure the EMS IP address.32 Maintaining NodeB by the M2000 Through the RNC Principles of maintaining NodeB through RNC O&M packets are routed to the RNC from the M2000 directly.INTERNAL IPRAN Deployment Guide Chapter 7 Remote O&M Channel 7. After the arrival at the interface board. Next hop IP address must be the peer IP address of the IPOA PVC. Figure 1. If the transport type of the NodeB is IUB-IP.  ADD NODEBIP: Configure the NodeB O&M IP.1 Maintaining the NodeB through the O&M Channel of the RNC 7. Next hop IP 2008-09-14 Huawei Confidential Page 113 of 133 . Data packets are forwarded through the OMU and interface board in the RNC. the network segment route to the M2000 is added to the FG2a interface board.0.11 ADD EMSIP: Configure the EMS IP address.161.8. you should run SET ETHPORT to enable the ARP proxy function of the port.161.230 OMU external network address 10.161.0. The value of the network segment route is the result with the AND operation between the address by running the command ADD EMSIP and the mask.255.0".2 NodeB OM address 12.12.40 FG2a internal address 80. SN=18.0.0 80.  Name Address M2000 address 10.INTERNAL IPRAN Deployment Guide address must be one of the following configured addresses:   PPP link peer IP address  MLPPP group peer IP address  IP address with the same network segment of the FE/GE port ADD NODEBESN: If the DHCP function is used between the RNC and the NodeB.0 Huawei Confidential Page 114 of 133 .211 OMU internal network address 80.  Command: ADD EMSIP: EMSIP="10.1 NodeB interface address 12.%% Destination address Address mask Next hop address 10.8.12.230".161.40 2008-09-14 255.1. add the NodeB electronic serial number to respond to DHCP requests reported by the NodeB (Optional).215.168. The OM address of the NodeB and the NodeB interface address are on the same network segment Note: The OM address and interface address of the NodeB are on the same network segment.6. MASK="255.  After the running of this command.6. The results are as follows: %%DSP IPRT: SRN=0.64 FG2a interface address 12.8.215.168.12.215.2 Configuration Example 1. At the NodeB side.255.6.168. 7. 10.10.2". the route to the NodeB is automatically added in the FG2a by running the command ADD NODEBIP. In the NodeB.6. the service from the FG2a to NodeB interface address is normal. The results (the network segment route added to the NodeB on the FG2a) are as follows: %%DSP IPRT: SRN=0. IPSN=18.2". NBIPOAMIP="12. the route to the M2000 must be added. 2008-09-14 Huawei Confidential Page 115 of 133 .255.0. IPLOGPORTFLAG=NO. IPGATEWAYIP="12.%% Destination network address Destination address mask Forward route address 12.8. Assume that the OM address of the NodeB is changed to 10. You need not to configure any route in the RNC manually. IPSRN=0.8. IPSRN=0.0.255. After the running of this command. Note: In the EMS system.255 80.255.10/24 1) The service is available.12.255. NBIPOAMMASK="255. NBTRANTP=IPTRANS_IP.12.8.10.12.10. Through the preceding configuration.255.10". ADD NODEBIP: NODEBID=1. One host route is added. therefore.168. IPSN=18.0 Next hop address 12. Command: ADD NODEBIP: NODEBID=1.INTERNAL IPRAN Deployment Guide  ADD NODEBIP: Configure the NodeB O&M IP. therefore.11".10. the route to the NodeB must be added. therefore. IPLOGPORTFLAG=NO.10. the RNC automatically adds the route to the NodeB in the OMU.8. IPGATEWAYIP="12. 2. the path from the M2000 to the OMU is normal. The OM address of the NodeB and the NodeB interface address are not on the same network segment. The OM address of the NodeB and the interface address are not on the same network segment. The results are as follows: %%LST BAMIPRT:. SN=18.0 255.0". NBIPOAMMASK="255. NBIPOAMIP="10.12.12.11  255.255. NBTRANTP=IPTRANS_IP.64 ADD NODEBESN: Add the electronic serial number of the NodeB to respond to DHCP requests reported by the NodeB (optional).2 2) The M2000 can normally maintain the OMU.%% Destination address Address mask 10.0".8. the NodeB O&M channel in the RNC is normal. The configurations are as follows:  Add the NodeB IP in the RNC: Add the NodeB IP for the M2000 to provide the automatic search function (for the automatic search function of the M2000.  The architecture is clear. The next hop is the FE port address. see the V8 IPRAN Deployment Guide).  Synchronize the M2000 to the RNC: Read the OMIP to the NodeB from the BAM database and establish the OM channel with the NodeB.3 Comparison between the Maintenance through the RNC and Maintenance by the M2000 directly Maintenance through the RNC Benefits 2008-09-14  It does not depend on the transport network. 7. Huawei Confidential Maintenance directly by the M2000  OM packets of the NodeB do not cause extra burden for the RNC. one route to the NodeB OMIP must be added to Router2. Page 116 of 133 .1 Principles and Basic Configuration Procedures Figure 1.  If the OMIP of the NodeB and FE port are on the same network segment. run SET ETHPORT to enable the ARP proxy function of the port.INTERNAL IPRAN Deployment Guide 7.2.33 Maintaining the NodeB directly by the M2000 The OM channel from the M2000 to the NodeB does not pass the RNC. A fault can be located quickly. In the NodeB LMT. Otherwise.2 Maintaining the NodeB directly by the M2000 7. The maintenance through the RNC is not recommended. Otherwise. and IP of each interface (except the FE interface) should not be on the same network segment.  In special cases. the corresponding binding route is invalid when the maintenance channel is switched over to the deactivation channel. The ATM scenario does not support the active/standby configuration. To ensure that the binding route of the maintenance channel 2008-09-14 Huawei Confidential Page 117 of 133 . the results are null by running the command DSP OMCH. Thus. The load traffic between the RNC board decreases.INTERNAL IPRAN Deployment Guide Limitations  The load of the RNC increases.4 Active/Standby OMCH Configurations at the NodeB Side 7. Two channels reach the peer ends through different routes. At this time. The local IP of two remote maintenance channels should not be on the same network segment. The IP scenario supports the active/standby OMCH channel.4. Note: 1. one active OMCH channel must be configured. In the IP scenario. local maintenance channel IP.1 Basic Principles The V210 is applicable to the dual stack. the direct maintenance of the NodeB by the M2000 is recommended. After the NodeB starts. Only the binding route of the activation channel is valid. Recommendation: In the IP networking. the maintenance of the NodeB through the RNC is used. label the VLAN). the IUB interface has the VLAN and a route device is unavailable for labeling the VLAN. the standby channel does not function as the activation channel automatically. a router is required (for example. two remote maintenance channels can be configured. For example. If the active channel is not available. In special cases. the binding route is used for this maintenance channel. you should run ADD OMCH to bind the route. channels using the route are interrupted. As a result. 7. 2. The remote maintenance channel IP.  The RNC cannot be isolated in the location of a fault related to the NodeB OM. Hence. If the peer IP and local IP of the maintenance channel are not on the same network segment. The binding route of deactivation channel is not valid. the occupation of the IUB transport resources decreases. the active channel is selected fixedly as the activation channel. In the initial configuration. 255.161. PREF=60. If the local IP of the OMCH and the FE address are on the same network segment. PEERIP="10.14. PREF=60. SBT=E1_COVERBOARD.14". RT=NEXTHOP.255.161. ST=UBR+.255. the active/standby configuration is not supported.0". 2. SBT=BASE_BOARD. BRT=YES.255.0". and the other is over the PPP. PEERMASK="255.0".255. the other OMCH is over ATM. MASK="255.0". 3. IFNO=0. two OMCHs are configured: one is over the ETH. ADD OMCH: FLAG=MASTER.11". SBT=BASE_BOARD. RT=NEXTHOP. MCR=32.8.161. JNRSCGRP=DISABLE. VPI=1. PCR=144. SBT=BASE_BOARD.12.230". PEERMASK="255.14.255. Dual-stack scenario In the case of the dual-stack.255. DSTIP="10. DSTMASK="255.215. PEERIP="10. SRN=0.11".255.8.8.0". MASK="255. NEXTHOP="12.255.255.255. BEAR=ATM. SN=6. the destination network segment of the binding route should be different from any route destination network segment added by running the command ADD IPRT.255.161.255. DSTIP="10.215.161. DSTMASK="255.8. BRT=YES.4.215. PEERMASK="255.1".255.1".0". BEAR=IPV4. PEERMASK="255. PREF=60. SN=6.255. PN=0. DSTIP="10. 7. ADD OMCH: FLAG=MASTER. To query the configured route.0".255. BRT=YES.0".14.INTERNAL IPRAN Deployment Guide is used for this maintenance channel only.161. SN=6.230".0". PT=IMA. DSTMASK="255.215. 2008-09-14 Huawei Confidential Page 118 of 133 . SRN=0.0".255.12.2 Configuration Example 1. 3. PEERIP="10. MASK="255.0". run SET ETHPORT to enable the ARP proxy. MASK="255.230". PEERIP="10. SRN=0.0".255.215.0". Hybrid transport scenario In the case of the hybrid transport. IP="12. IP="12.230".255. VCI=33.0".255. run LST IPRT. SRN=0.215. BEAR=IPV4. ATM scenario In the ATM scenario. ADD OMCH: FLAG=SLAVE. IP="14.255.12.161. BEAR=IPV4. IP="14. Only one remote maintenance channel is configured. two OMCHs are configured: one OMCH is over IP and the configurations are the same as the previous IP scenario.255.14.12.215. SN=5. IFT=PPP. ADD OMCH: FLAG=SLAVE. RT=IF. NEXTHOP="12.14". IP="14.255. PEERIP="10.255. VPI=1.INTERNAL IPRAN Deployment Guide ADD OMCH: FLAG=MASTER.255. 2008-09-14 Huawei Confidential Page 119 of 133 . MASK="255. MCR=32.14. PCR=144. PEERMASK="255.230". VCI=33.161. SRN=0. BEAR=ATM.0". ST=UBR+. SBT=BASE_BOARD.0". SN=6.14.14".215. PT=IMA. JNRSCGRP=DISABLE.255. PN=0. 2. Benefits: 1. After the hardware of NodeB is installed. This section describes the remote debug of a NodeB related to Iub interface in the IPRAN networking. This mode can replace the debug at the local NodeB.1 NodeB Remote Software Debug Usually. The fee of the NodeB software debug ranges from 1500 RMB to 7000 RMB. Maintenance personnel use the M2000 or LMT debug a NodeB in the remote OMC equipment room through the NodeB remote maintenance channel. 2008-09-14 Huawei Confidential Page 120 of 133 . the NodeB software debug is subcontracted to a local cooperation partner. The software debug is implemented at the local NodeB.  The DHCP is used to activate the NodeB remote OM channel when correct data configuration files cannot be downloaded to the NodeB. engineers need not enter the site again. the remote debug for a NodeB is implemented in the equipment room in the centralized mode.INTERNAL IPRAN Deployment Guide Chapter 8 Remote Debug of NodeB 8. The construction speed of a NodeB is quicker. two modes are available for activating the NodeB remote maintenance channel:  Correct data configuration files are downloaded to the NodeB to ensure the successful interconnection between the RNC and the NodeB OM channel. The cost of the software debug is saved. To save this engineering cost. After the transport of the Iub interface in the IPRAN is ready. 3. 8. NodeB. RNC DHCP Relay: It is the device transferring DHCP packets between the DHCP Server and the DHCP Client.2. The DHCP Server is the address of the RNC interface board. for example. options are added. In packets. devices between them need not support the DHCP Relay. DHCP Server: It is the host in the network returning configuration parameters to the DHCP Client.34 Initial address application in the scenario without using DHCP Relay 2008-09-14 Huawei Confidential Page 121 of 133 . Concepts: DHCP Client: It is the host in the network using the DHCP obtain configuration parameters. The DHCP Relay can be a router or specific host.2 Introduction to the DHCP 8. The L2 network exists between the NodeB and RNC interface board. The DHCP is encapsulated through the UDP. for example. DISCOVER (Broadcast) RNC interfaceboard Server Activeboard electronic serial number NodeB FE IP and mask NodeB OMIP and mask NodeB peer OMIP and mask REQUEST (Broadcast) Figure 1. Figure 8-1 shows the DHCP procedure. and default gateway) for a host in the network. Based on the BOOTP protocol. the function of dynamically obtaining the IP address is added.1 Basic Principles The dynamic host configuration protocol (DHCP) transfers configuration information (including allocated IP address.INTERNAL IPRAN Deployment Guide 8.2 Scenario without Using the DHCP Relay When the L2 network exists between the NodeB (DHCP Client) and DHCP Server.2. subnet mask. dhcp client 0 network 1 dhcp relay network 0 network 2 dhcp server network n NETWORK n-1 dhcp client n Figure 1. Broadcast Unicast Unicast Broadcast Unicast Unicast Figure 1.INTERNAL IPRAN Deployment Guide 8. The L3 network exists between the NodeB and RNC interface board.35 Server-Client networking with using the Relay The DHCP Server is the address of the RNC interface board. the gateway router of the NodeB must support the DHCP Relay. Figure 8-3 shows the DHCP procedure.3 Scenario with Using the DHCP Relay When the L3 network exists between the NodeB (DHCP Client) and DHCP Server. The gateway router of the NodeB starts the DHCP Relay.2.36 Initial address application in the scenario using the DHCP Relay 2008-09-14 Huawei Confidential Page 122 of 133 . 1 M2000 address 11. 2008-09-14 Huawei Confidential Page 123 of 133 .10". PTIP="10.11.0".12 .11.37 General process of NodeB remote software debug 8.1".12 .10 .3 General Process of NodeB Remote Software Debug NodeB RemoteSoftwareDebugFlowchart Performthe integrated selftest for hardware Is the NodeB pinged successfully? Cut over the transport and antennafeeder Download data configuration files Ping the NodeB to be debugged remotely Upgrade BOOTROM Upgrade Flash software OMSTAR hardwareinstallationandinspection Check the power-on Power on the NodeB Install hardware Hardwareinstallation Debug the transport Is thecutover of thetransport over? Performthe remote debug Start the NodeB remote debugtool Download scripts at theRNC side of NodeB to be debugged Personnel inOMC remoteequipment room Prepare data Handle faults of the NodeB Informof theactiveboard electronic serial number Is theremote debug successful? End M2000/LMT remote debug Figure 1. FEDHCPSVRIP="12. USEMP=Disable.10. Name RNC address Value interface 12 .12. USEPPP=Disable.255.1 NodeB address 10 .4 Configuration Example The following table lists the configuration of the RNC through an example of NodeB using the FE interface. PTIPMASK="255.INTERNAL IPRAN Deployment Guide 8. NBLB1="111222222222222222222222222222". USEFE=Enable. USENBLB2=Disable.10.10 .12.10 interface NodeB electronic serial number 222222222222222222222 ADD NODEBESN: NODEBID=111.255. 255.255. GOU. The IP address of the DHCP Server must be one of the following addresses configured in the FG2.INTERNAL IPRAN Deployment Guide ADD EMSIP: EMSIP="11. For the software debug. 2. and PEU: device IP address.11. Ethernet port IP address. MASK="255. and MLPP group local IP address. The electronic serial number of the NodeB can be queried directly from the main control board of the NodeB.1". see the WCDMA Iub IPRAN Networking NodeB Remote Software Debug Guide.11. 2008-09-14 Huawei Confidential Page 124 of 133 . PPP link local IP address. Note: 1.0". 共 133 页 . analyze the path of packets to be pinged by using the Tracert.  DSP IPRT: Query the board route table 2008-09-14 华为机密,未经许可不得扩散 第 1 页. see the V18 IPRAN Deployment Guide. 2) On the RNC: TRC IPADDR: SRN=0. DESTIP="10.内部公开 IPRAN 开局指导书 Chapter 9 Troubleshooting 9.1 Troubleshooting related to the RNC 9.1. SN=18. Application scenario When packets failed to be pinged or the delay is large. The information is helpful for locating the fault. Description 1) Run Tracert to query all path information from the PC to the peer device.10".1 Using the Tracert for Analysis in the case of Failure to Ping Packets 1. Commands on the RNC  DSP ARP: Query the port ARP table. For the Trace principles. For example.10. 2. and the delay time. 3.10. The displayed information indicates in which gateway or path packets are delayed. Then. The peer end transmits the INIT. This principle applies to the location of a SCTP problem or other problems. you should perform the following: As shown in the dotted line in the preceding figure.1. 共 133 页 .2 Problems related to the SCTP 1. and check whether packets exist in the network. the source end does not send packets.内部公开 IPRAN 开局指导书  DSP ETHPORT: Query the port state and packet receiving and transmitting 9. Principles RNC SPU Debugdevice PIU HUB Bearer network Peer NE Capture packets by the Ethreal The data channel of the SCTP: SPU <--> PIU <--> Bearer network <--> Peer NE When you locate the fault of the connection failure or one-way connection. If packets are unavailable in the network. 2. use the Ethereal to catch packets between the bearer network and RNC. One-way connection due to incorrect configuration in the upper layer The tracing is performed on site. Both ends start to 2008-09-14 华为机密,未经许可不得扩散 第 2 页. check whether the problem results from the RNC side or nonRNC side. The following figure shows trace results. The local end returns INITACK. Connection failure due to the loss of Cookie packets In a test. the RNC sends an ABORT. because the protocol is processed on the SPU. Interconnection parameters of the SCTP: Check whether the IP address and port are consistent with the negotiation. the signaling interaction is as follows (results traced at the RNC side): NodeB RNC I NI T I NI TACK I NI T I NI TACK I NI T I NI TACK ABORT According to the signaling tracing. Packets exist in the network. 共 133 页 . and M3UA are not configured. the symptom is as follows: 2008-09-14 华为机密,未经许可不得扩散 第 3 页. CCP. The peer end continues to transmit the INIT. The causes are as follows: Use the Ethereal to catch packets.内部公开 IPRAN 开局指导书 interact with Cookie. the NodeB correctly sends the INIT and the RNC also correctly returns the INITACK. The NodeB does not send COOKIE. the NCP. The causes are as follows: The data receiving and transmitting are normal. In the initial link establishment. the RNC transmits the ABORT. No configuration of the upper layer application of the SCTP: For example. 2. At the NodeB side. the system prints that the upper layer link is not configured. The processing of protocol messages is abnormal. Location principle Check the following: 1. Then. 3. After the start of the SPU. this type of problem results from incorrect configurations. The comparison of two packets (including quintuple. The COOKIE packet is longer than the INIT packet. Note: Usually. Analyze whether each field of each protocol message is correct. Hence. The INIT and INITACK packets can be received and transmitted normally. Check the MTU and find that it is too small. 3. 2.内部公开 IPRAN 开局指导书 NodeB RNC INIT INITACK COOKIE Timeout INIT INITACK COOKIE Timeout INIT INITACK According to the tracing on the SPU. Analyze the tracing on the SPU. The PIU loses the MTU. The RNC cannot receive COOKIE packets. Locate the problem on the SPU according to the information corresponding to the serial port redirection. The problem is solved. Location of faults related to the SCTP Handlings of a problem that does not comply with the protocol: 1. engineers should check configurations. 4. and IP header) indicates that no error is found. 2008-09-14 华为机密,未经许可不得扩散 第 4 页. It indicates that the channel is normal. Run SET ETHPORT to set the MTU to a larger value. Start the redirection of the SPU serial port and analyze the printing information on the SPU. The packet may be lost in the PIU. the packet does not reach the SPU. VLAN. The INIT packets can be received. 共 133 页 . engineers should ensure the correctness of the data. In the case of the data configuration. 2. It is found that the configurations of the OPC and DPC at both ends are not matched.3 Cases of M3UA Common Problems 1. Analyze the codes. Analyze configuration data. with carrying the error information in the Info field. During the link establishment. The product personnel do not know whether the ID in the previous links exists. it is found that the link is added in the case of the online operations. Comments: 2008-09-14 华为机密,未经许可不得扩散 第 5 页. engineers should check configuration data at the peer end. After receiving of the ACK. The link fails to be established.内部公开 IPRAN 开局指导书 9. Analyze codes. After the timeout of the UP timer. A link fails to be established due to the repeated configuration of the ASPID Symptom: At the ASP side. The link establishment fails due to inconsistent configurations at both ends Symptom: One end of the link is DOWN and the other end is INACTIVE. the SGP returns the ACK after the receive of the UP message. After the replacement of the ASP ID. When configuration at both ends are inconsistent. Comments: In the case of the data configuration. without any processing. ASP ID is 65536. During the link establishment. 2. The data check mechanism is available in the M3UA. 2. Handling: 1. the problem is solved. the ASP discards the message. The ASP end sends UP messages to the SGP periodically. the system judges whether the link with the ID is recorded in the linkset when the UP message is received. Engineers guess that the possibility is high. it is found that the SGP side returns Error (ASP illegal flag). it indicates that the link is established and the system returns Error. Handling: 1. This is the cause. the ASP sends the UP message again. 共 133 页 .1. 3. one link is configured. and the mechanism cannot check the configuration of the peer end. If yes. After the communications with the product line. The link is not established. 共 133 页 .1 Alarms at the RNC Side (V210)  ALM-1711 PATH Fault  ALM-1712 PATH Forward Congestion  ALM-1713 PATH Backward Congestion  ALM-1714 Port Forward Congestion  ALM-1715 Port Backward Congestion  ALM-1721 Logical Port Forward Congestion  ALM-1722 Logical Port Backward Congestion  ALM-1851  ALM-1852 SCTP Link Congested  ALM-1853 Link Destination IP Changeover  ALM-1861 M3UA Link Fault  ALM-1862 M3UA Link Congestion  ALM-1863 M3UA destination entity route invalid  ALM-1864 M3UA route unavailable  ALM-1865 M3UA destination entity inaccessible  ALM-2602 PPP/MLPPP Link Down  ALM-2604 MLPPP Group Down  ALM-2606 IP PATH Down  ALM-2609 FE Port Active/Standby Switchover  ALM-2612 interface board bottom GE link fault alarm  ALM-2613 Ethernet port work mode change alarm  ALM-2622 MLPPP group link bandwidth change alarm  ALM-2623 Ethernet port bandwidth change alarm  ALM-2624 L3 detection failure alarm  ALM-2625 IP address conflict detection alarm 2008-09-14 SAAL Link Unavailable 华为机密,未经许可不得扩散 第 6 页. engineers should familiar with the previous configurations to avoid the conflict between the new data and old data.内部公开 IPRAN 开局指导书 When data is dynamically added. Chapter 10 Alarms 10. 共 133 页 .内部公开 IPRAN 开局指导书  ALM-420 IP PM detection start failure  ALM-421 IP PM detection failure  ALM-422 logical port bandwidth adjustment exceeding threshold  ALM-851 FE Link Down  ALM-852 FE Link Send Defect Indication  ALM-853 FE Link Receive Defect Indication  ALM-854 FE Link Loop 10.2 Alarms at the NodeB Side  ALM-2750 FE Chip Initialization Failure  ALM-2751 IP Transmission Network FE Interface Abnormal  ALM-2752 IP Transmission Network PPP Interface Abnormal  ALM-2753 IP Transmission Network ML PPP Interface Abnormal  ALM-2754 PPPoE Interface Fault  ALM-2755 IP RAN NCP Abnormal  ALM-2756 IP RAN CCP Abnormal 2008-09-14 华为机密,未经许可不得扩散 第 7 页.
Copyright © 2024 DOKUMEN.SITE Inc.