Download IPRAN Deployment Guide V210-20090303 PDF

TitleIPRAN Deployment Guide V210-20090303
TagsComputer Network Ip Address Quality Of Service Port (Computer Networking) Gateway (Telecommunications)
File Size1.3 MB
Total Pages132
Table of Contents
                            Chapter 1   Overview
	1.1   Introduction to the V210 IPRAN
		1.1.1   FP MUX
			1.  Principles
			2.  Protocol
			3.  Command
		1.1.2   IPRAN Header Compression
			1.  Principles
			2.  Protocol
			3.  Command
		1.1.3   IPRAN Fault Detection
			1.  Principles
			2.  Protocol
			3.  Commands
	1.2   Availability
		1.2.1   Requirements for NEs
		1.2.2   Supporting Versions
		1.2.3   Other Support
			1.  RNC side
			2.  At the NodeB side:
Chapter 2   Introduction to Basic Protocols
	2.1   M3UA
		2.1.1   Principles and Relevant Concepts
		2.1.2   Functions of the M3UA
		2.1.3   Protocol
		2.1.4   Configuration Sequence at the RNC Side
	2.2   SCTP
		2.2.1   Principles of Multi-Homed SCTP
		2.2.2   SCTP Dual-Homed Mechanism Supported by the RNC
		2.2.3   Protocol
	2.3   Others
Chapter 3   Introduction to the Networking
	3.1    V2 Backup Policy
		3.1.1   Backup Mode at the RNC Side
			1.  Board backup mode
			2.  Port backup mode
			3.  Impact on the system by the switchover
		3.1.2   NodeB Side
			1.  NodeB supports only the board backup mode, without supporting the port backup mode
	3.2   Common Networking Modes
		3.2.1   Layer-2 Networking Mode
			1.  IP over E1/T1 over PDH/SDH (Iub interface)
			2.  IP over SDH (Iub interface)
			3.  MSTP-based IP networking (Iub interface)
			4.  Data network-based IP networking (IUB/IUR/IUCS/IUPS)
		3.2.2   Layer-3 Networking Modes
			1.  RNC directly connecting to one router
			2.  RNC directly connecting to two routers
			3.  Load sharing
		3.2.3   Hybrid Transport Networking
		3.2.4   ATM/IP Dual-Stack Transport Networking
	3.3   Backup Constraint
		3.3.1   RNC
			1) In the separate mode, the route must be configured in even slots.
			2) The backup mode should not be configured in odd slots.
			3) After the active/standby Ethernet ports are configured, the corresponding ports of the active/standby boards function as the active/standby ports.
			4) The backup port should not be used. The gateway continuity check can be started.
			5) When at least either of the active and standby ports is configured with IP or port control, two ports are not allowed to be configured as the active and standby ports.
		3.3.2   NodeB:
			1) Boards supporting the board backup:
			V210: WMPT/UTRP
			V110: NUTI/HBBU. NDTI does not support.
			2) The code backup is performed in the NodeB. Hence, the service is interrupted in the case of the switchover.
			3) In the backup mode, data is configured only in the active board. By default, the slot with the smaller ID in the backup group is the active board in the initial configuration.
Chapter 4   V210 IPRAN Key Configurations
	4.1   Relevant Settings of the IPRAN
		4.1.1   RNC Side
			1.  Set the Ethernet port attribute.
			2.  Set the mapping between the DSCP and VLAN PRI.
			3.  Set the mapping between the queue of the IP type port and the DSCP
			4.  Set the DSCP value of the OAM flow
			5.  Set the corresponding DSCP of the SCTP link and whether to enable the VLAN.
			6.  Set the corresponding DSCP of the IPPATH and whether to enable the VLAN.
			7.  Add the mapping between the destination IP and VLANID
			8.  Set the mapping between the PHB and DSCP
		4.1.2   NodeB Side
			1.  Set the Ethernet port attribute
			2.  Set the priority of the signaling and OM
			3.  Set the configuration between the DSCP and VLAN
			4.  Set the VLAN based on the next hop (V210)
			5.  Example
	4.2   Constraint and Restrictions of IP Address and Configuration
		4.2.1   Constraints of RNC IP Address
		4.2.2   Constraints of NodeB IP Address
Chapter 5   Example of Iub Interface Configuration
	5.1   Version Description
	5.2   IUB Interface Protocol Stack
	5.3   Data Planning
		5.3.1   Data Planning in L2 Networking
			1.  Data planning of physical layer and data link layer
			2.  Data planning of control plane
			3.  Data planning of user plane
			4.  Data planning of management plane
		5.3.2   Data Planning in L3 Networking
			1.  IP addresses planning
			2.  Data planning of physical layer and data link layer
			3.  Data planning of control plane
			4.  Data planning of user plane
			5.  Data planning of management plane
		5.3.3   Data Planning of Hybrid Transport Networking
			1.  IP addresses planning
			2.  Data planning of physical layer and data link layer
			3.  Data planning of control plane
			4.  Data planning of user plane
			5.  Data planning of management plane
		5.3.4   Data Planning of Dual Stack Transport Networking
			1.  Networking Description
			2.  Networking Planning
	5.4   Configuration Procedures at RNC Side
		5.4.1   Configuration of Layer-2 Networking
			1.  Connect the network cable.
			2.  Perform the configuration in the RNC in the MML
		5.4.2   Configuration of Layer-3 Networking
			1.  Connect E1 cable or Ethernet cables.
			2.  Perform the configuration in the RNC in the MML.
		5.4.3   Configuration of Hybrid Transport Networking
			1.  Connect E1 cables or Ethernet cables.
			2.  Perform the configuration in the RNC in the MML.
		5.4.4   Configuration of Dual Stack Transport Networking
			1.  Connecting E1 Cables and Ethernet Cables
			2.  Perform the configuration in the RNC in the MML.
	5.5   Configuration Procedures at NodeB Side
		5.5.1   Configuration of Layer-2 Networking
		5.5.2   Configuration of Layer-3 Networking
		5.5.3   Configuration of Hybrid Transport Networking
		5.5.4   Configuration of Dual Stack Transport Networking
			1.  Configure the Parameters Related to ATM Transport
			2.  Configure the Parameters Related to IP Transport
Chapter 6   Example of IU/IUR Interface Configuration
	6.1   Version Description
	6.2   IU/IUR Interface Protocol Stack
	6.3   Procedures of IU PS Configuration (IP)
		6.3.1   IP Addresses Planning
		6.3.2   Configuring Physical Layer Data
		6.3.3   Adding Control Plane Data of Iu-PS Interface
		6.3.4   Adding the Mapping Relation of Transport Resources of Neighbor Nodes
		6.3.5   Adding User Plane Data of Iu-PS Interface
	6.4   Procedures of IU CS Configuration (IP)
		6.4.1   IP Addresses Planning
		6.4.2   Configuration of Physical Layer Data
		6.4.3   Adding Control Plane Data of Iu-CS Interface
		6.4.4   Adding the Mapping Relation of Transport Resources of Neighbor Nodes
		6.4.5   Adding User Plane Data of Iu-CS Interface
	6.5   Procedures of IUR Configuration (IP)
		6.5.1   IP Addresses Planning
		6.5.2   Configuration of Physical Layer Data
		6.5.3   Adding Control Plane Data of Iur Interface
		6.5.4   Adding the Mapping Relation of Transport Resources of Neighbor Nodes
		6.5.5   Adding User Plane Data of Iur Interface
	6.6   IU/IUR Configuration Specifications
		6.6.1   Configuration Specifications of Control Plane (IUPS-IP)
		6.6.2   Configuration Specifications of User Plane (IUPS-IP)
		6.6.3   Configuration Specifications of Control Plane (IUCS-IP)
		6.6.4   Configuration Specifications of User Plane (IUCS-IP)
		6.6.5   Configuration Specifications of Control Plane (IUR-IP)
		6.6.6   Configuration Specifications of User Plane (IUR-IP)
	6.7   Relevant Knowledge Points
		6.7.1   Two Modes
		6.7.2   Relation between Signaling Link and Mask
	6.8   Configuration Example of Current Network
Chapter 7   Remote O&M Channel
	7.1   Maintaining the NodeB through the O&M Channel of the RNC
		7.1.1   Principles and Basic Configuration Procedures
		7.1.2   Configuration Example
			1.  The OM address of the NodeB and the NodeB interface address are on the same network segment
			2.  The OM address of the NodeB and the NodeB interface address are not on the same network segment.
	7.2   Maintaining the NodeB directly by the M2000
		7.2.1   Principles and Basic Configuration Procedures
	7.3   Comparison between the Maintenance through the RNC and Maintenance by the M2000 directly
	7.4   Active/Standby OMCH Configurations at the NodeB Side
		7.4.1   Basic Principles
		7.4.2   Configuration Example
			1.  Hybrid transport scenario
			2.  Dual-stack scenario
			3.  ATM scenario
Chapter 8   Remote Debug of NodeB
	8.1   NodeB Remote Software Debug
	8.2   Introduction to the DHCP
		8.2.1   Basic Principles
		8.2.2   Scenario without Using the DHCP Relay
		8.2.3   Scenario with Using the DHCP Relay
	8.3   General Process of NodeB Remote Software Debug
	8.4   Configuration Example
Chapter 9   Troubleshooting
	9.1   Troubleshooting related to the RNC
		9.1.1   Using the Tracert for Analysis in the case of Failure to Ping Packets
			1.  Application scenario
			2.  Description
			3.  Commands on the RNC
		9.1.2   Problems related to the SCTP
			1.  Principles
			2.  One-way connection due to incorrect configuration in the upper layer
			3.  	Connection failure due to the loss of Cookie packets
			4.  Location of faults related to the SCTP
		9.1.3   Cases of M3UA Common Problems
			1.  The link establishment fails due to inconsistent configurations at both ends
			2.  A link fails to be established due to the repeated configuration of the ASPID
Chapter 10   Alarms
	10.1   Alarms at the RNC Side (V210)
	10.2   Alarms at the NodeB Side
                        
Document Text Contents
Page 1

Ehu

Document

Code

Product

Name

WCDMA RNC&NodeB

Intended

Audience

INTERNAL Product

Version

V200R0010

Department WCDMA UMTS

Maintenance Dept

Document

Version

IPRAN Deployment Guide V210

Prepared by Transport Team of UMTS

Maintenance Dept

Date 2008-08-25

Reviewed by Transport Team of UMTS

Maintenance Dept

Date 2008-08-25

Reviewed by Transport Team of UMTS

Maintenance Dept

Date 2008-08-25

Approved by Date

Huawei Technologies Co., Ltd.

All rights reserved

Page 2

IPRAN Deployment Guide

INTERNAL

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

Page 67

IPRAN Deployment Guide

INTERNAL

5.4 Configuration Procedures at RNC Side

Version in the configuration example: RNC uses V210060

5.4.1 Configuration of Layer-2 Networking

In the case of the L2 networking, the port IP f the RNC interface board and the NodeB IP are on
the same network segment. For the configuration of PPP link, see section 7.4.3.

1. Connect the network cable.

Label of hardware connection: The FG2 board of the RNC is in slot 18/19 in subrack 0. The FE
port is 0. The binding between the board backup and port backup is used.

2. Perform the configuration in the RNC in the MML

 Configure the physical layer data.

//Set the Ethernet port attributes. The FE port of the RNC and the FE port interconnected to the

RNC must be set to 100M/FULL.

SET ETHPORT: SRN=0, SN=18, BRDTYPE=FG2, PTYPE=FE, PN=0, MTU=1500,

AUTO=DISABLE, FESPEED=100M, DUPLEX=Full, FC=ON, OAMFLOWBW=1,
FLOWCTRLSWITCH=ON, FCINDEX=1;

Parameter Description:

AUTO Auto
negotiation
or not

This parameter is determined according to the device
interconnected to the RNC. If the interconnected device is in the
auto negotiation mode, the RNC port is also in the auto negotiation
mode. Otherwise, the RNC port is set to non auto negotiation
mode. The GE port must be in the auto negotiation mode.

FESPEED FE port rate This parameter is designated according to the rate of the peer

2008-09-14 Huawei Confidential Page 66 of 133

Page 131

IPRAN开局指导书

内部公开

When data is dynamically added, engineers should familiar with the previous

configurations to avoid the conflict between the new data and old data.

Chapter 10 Alarms

10.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 SAAL Link Unavailable

 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 华为机密,未经许可不得扩散 第 6页, 共 133页

Similer Documents