Beruflich Dokumente
Kultur Dokumente
V100R008C10
User Manual
Issue 01
Date 2015-12-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
1 Feature Description....................................................................................................................... 1
1.1 Introduction.................................................................................................................................................................... 2
1.2 Basic Concepts............................................................................................................................................................... 3
1.2.1 System Configuration.................................................................................................................................................. 3
1.2.1.1 System Architecture................................................................................................................................................. 3
1.2.1.2 Point-to-Point Transmission..................................................................................................................................... 5
1.2.1.3 Aggregation Transmission........................................................................................................................................6
1.2.1.4 Intra-board Relay Transmission................................................................................................................................8
1.2.1.5 Inter-board Relay Transmission................................................................................................................................9
1.2.2 Switching Conditions................................................................................................................................................ 10
1.3 Principles...................................................................................................................................................................... 11
1.4 Specifications................................................................................................................................................................13
1.5 Availability................................................................................................................................................................... 15
1.6 Feature Updates............................................................................................................................................................ 16
1.7 Feature Dependencies and Limitations.........................................................................................................................16
1.8 Planning Guidelines......................................................................................................................................................18
1.9 FAQs............................................................................................................................................................................. 18
2 Deployment Instructions........................................................................................................... 19
2.1 General Deployment Process........................................................................................................................................20
2.2 Configuration Process...................................................................................................................................................21
2.3 Configuration Example.................................................................................................................................................23
2.3.1 Networking Diagram................................................................................................................................................. 23
2.3.2 Configuration Procedure (RTN 950/950A)............................................................................................................... 24
2.3.3 Configuration Procedure (RTN 380)......................................................................................................................... 28
3 Maintenance Instructions.......................................................................................................... 33
3.1 RMON Performance.....................................................................................................................................................34
3.2 Troubleshooting............................................................................................................................................................ 38
3.3 Alarm Reference...........................................................................................................................................................40
3.3.1 PLA_CFG_MISMATCH...........................................................................................................................................40
3.3.2 PLA_DOWN............................................................................................................................................................. 44
3.3.3 PLA_MEMBER_DOWN_EXT................................................................................................................................ 45
3.3.4 PLA_PKT_ERR........................................................................................................................................................ 46
1 Feature Description
1.1 Introduction
This section defines Super Dual Band and describes its purpose.
1.2 Basic Concepts
This section describes the basic concepts of Super Dual Band.
1.3 Principles
Super Dual Band supports priority-based service scheduling, traffic adjustment, and link
protection.
1.4 Specifications
This section lists Super Dual Band specifications.
1.5 Availability
This section lists the hardware requirements that must be met to implement Super Dual Band.
1.6 Feature Updates
This section provides a history of Super Dual Band updates.
1.7 Feature Dependencies and Limitations
This section describes the dependencies and limitations of Super Dual Band.
1.8 Planning Guidelines
This section provides guidelines for planning Super Dual Band.
1.9 FAQs
This section answers FAQs about Super Dual Band.
1.1 Introduction
This section defines Super Dual Band and describes its purpose.
Definition
In the LTE era, traffic to be backhauled exponentially increases, posing great challenges on
LTE backhaul networks:
l Spectrum resources of common frequency bands are becoming insufficient and their
transmission bandwidth is limited, making capacity expansion increasingly difficult.
l Limited transmission distances of E-band microwave cannot meet medium-distance
backhaul requirements of macro base stations.
To tackle the challenges, Huawei launches the Super Dual Band solution, which delivers the
innovative cross-band link aggregation technology. By integrating physical link aggregation,
adaptive modulation (AM), and quality of service (QoS), this solution binds common-band
microwave (6-42 GHz) and E-band microwave (71-76 GHz and 81-86 GHz) to achieve large-
bandwidth and long-distance transmission.
Purpose
To meet LTE broadband backhaul requirements, Super Dual Band leverages the following
advantages of common-band microwave and E-band microwave:
l E-band microwave provides flexible large bandwidth. The air interface throughput
reaches 5 Gbit/s to 10 Gbit/s.
l Common-band microwave provides resistance against rain fade and ensures high
availability. Therefore, the availability requirement on E-band links can be reduced to
99.9% so that E-band microwave can achieve a transmission distance of up to 10 km.
l The physical link aggregation, AM, and QoS technologies together guarantee 99.999%
availability of core services.
Super Dual Band is the optimal solution for large-bandwidth and long-distance (10 km)
backhaul of wireless traffic. See Table 1-1.
Table 1-1 Comparison of Super Dual Band, common band, and E-band
Item Super Dual Band Common Band E-band
System Architecture
The Super Dual Band solution uses EM6D boards to implement Super EPLA. Figure 1-2
shows the system architecture of the Super Dual Band solution.
l The backplane buses transmit only signal flows between members in Super EPLA groups.
l On an EM6D board, the port that connects to an E-band link must be configured as the master port
in a Super EPLA group.
l On an EM6D board, an E-Line service can be configured only between the master ports in two
Super EPLA groups or between the master port in a Super EPLA group and a service access port.
l If the air-interface capacity of E-band links exceeds 2.5 Gbit/s, you can connect two 2.5GE optical
ports on an EM6D board to one RTN 380 to increase access capacity.
l When Ethernet services are transmitted/received through an EM6D board, service access ports on
the board can be configured in a link aggregation (LAG) group.
l Common-band links can form an XPIC group but cannot form a 1+1 protection group.
Typical Configurations
Super Dual Band supports the following typical configurations:
l 1.2.1.2 Point-to-Point Transmission
l 1.2.1.3 Aggregation Transmission
l 1.2.1.4 Intra-board Relay Transmission
l 1.2.1.5 Inter-board Relay Transmission
NOTE
l In this example, the EM6D board receives only one channel of services. Therefore, only one
transparently transmitted point-to-point E-Line service is configured. If the EM6D board receives
multiple channels of services and only one Super EPLA group is configured, different types of E-
Line services must be configured based on the types of received services.
l An EM6D board can be configured with two independent Super EPLA groups and receive multiple
channels of services.
l The two common-band links and the E-band link are bound in a Super EPLA group. Port
3 on the EM6D board is configured as the master port in the group.
l The EM6D board can also receive services from another device. In this example, E-Line
services are configured between Port 1 and Port 3 and between Port 2 and Port 3 on the
EM6D board.
This section uses a Super Dual Band solution consisting of 2+0 common-band links and 1+0
E-band link in both the east and west directions as an example.
1.3 Principles
Super Dual Band supports priority-based service scheduling, traffic adjustment, and link
protection.
Link Aggregation
Super Dual Band aggregates common-band and E-band links as a Super enhanced physical
link aggregation (EPLA) group, as shown in Figure 1-7.
l A Super EPLA group is configured on an EM6D board. Link 1 is the master link. Links
2 and 3 are slave links.
l A Super EPLA group is configured on an RTN 380.
1. The EM6D board encapsulates received services and distributes them to member links in
the Super EPLA group based on QoS policies. The following two scheduling modes are
supported:
– MODE A mode
Traffic Adjustment
IF boards and the RTN 380 report their available air-interface capacities to the EM6D board.
The EM6D board then adjusts traffic distributed to links accordingly.
Protection Switching
Each member in a Super EPLA group checks the link and hardware status in real time.
Switching occurs upon detection of a link or hardware fault.
After a link in a Super EPLA group fails, the EM6D board stops transmitting services to the
failed link and transmits services only to functional links. In this case, the Super EPLA group
provides lower Ethernet bandwidth because one link is unavailable.
As shown in Figure 1-8 and Figure 1-9, after link 3 fails, the EM6D board does not transmit
traffic to link 3 but only to links 1 and 2.
After link 3 recovers, the EM6D board automatically restarts to distribute traffic on all the
three links.
NOTE
Super EPLA protects only Ethernet service signals and does not protect TDM services.
1.4 Specifications
This section lists Super Dual Band specifications.
Item Specifications
Item Specifications
IF board l ISV3
l ISM6
Maximum number of 2
Super EPLA groups
supported by an EM6D
board
Maximum number of 8
members in a Super
EPLA group
Maximum number of 8
Super EPLA members
supported by an EM6D
board
Maximum number of 3
EM6D boards supported
by an NE
Maximum number of 6
Super EPLA groups
supported by an NE
Item Specifications
Threshold for BE, AF1, AF2, AF3, AF4, EF, CS6 and CS7
distinguishing between NOTE
high-priority and low- This threshold can be specified for a Super EPLA group in MODE B
priority services in a mode. The values 0 to 7 map to BE, AF1, AF2, AF3, AF4, EF, CS6, and
Super EPLA group CS7 of PHBs. Only an SP queue can be configured with a PHB.
Services in this SP queue and other queues with higher-priorities are
high-priority services.
1.5 Availability
This section lists the hardware requirements that must be met to implement Super Dual Band.
Hardware
Feature Hardware
NOTE
A Super Dual Band solution requires one RTN 900 that houses EM6D and IF boards and one or two
full-outdoor microwave devices.
Feature Updates
Version Description
l RTN 950/RTN 950A: Super Dual Band is first available in RTN 950/RTN 950A
V100R008C10 V100R008C10 and RTN 380 V100R006C00.
l RTN 380:
V100R006C00
Self-limitations
Item Description
RTN 380 l Ethernet ports connecting an EM6D board and an RTN 380 must be
of the same type and work in auto-negotiation mode.
l No services can be configured on the RTN 380 port that is connected
to an EM6D board.
l An RTN 380 supports only one Super EPLA group.
l If a Super EPLA group is configured on an RTN 380, the in-band
DCN function must be disabled on its IF port.
Interconnectio The ports at both ends of a link in a Super EPLA group must have the
n same ID.
Air-interface During link planning, 512 kbit Ethernet bandwidth must be reserved for
Ethernet each Super EPLA link to function as the protocol channel. Otherwise, the
bandwidth Super EPLA group cannot work stably.
Dependencies and Limitations Between Super Dual Band and Other Features
Table 1-5 Dependencies and limitations between super dual band and other features
Feature Description
Inband data All common-band links in a Super EPLA group must use the same
communicatio inband DCN protocol.
n network
(DCN)
RMON l Super EPLA groups support RMON statistics by group. Bytes are
count for RMON statistics by group.
l Super EPLA groups support RMON statistics by group. Segments are
count for RMON statistics by port.
l Air-interface LAG
l PLA/EPLA/EPLA+
l Frame header compression
l Payload compression
l AES-based encryption at air interfaces
l IF 1+1 protection
l IF N+1 protection
1.9 FAQs
This section answers FAQs about Super Dual Band.
None
2 Deployment Instructions
This section provides instructions on how to configure and commission Super Dual Band.
Table 2-2 Process of configuring Super Dual Band on the RTN 900
Step Operation Remarks
Table 2-3 Process of configuring Super Dual Band on the RTN 380
Figure 2-3 shows the networking consisting of 2+0 common-band links and a 1+0 E-band
link.
Data Preparation
Parameter Value in This Example Planning Principle
SFP type Port 3 and Port 4 on the l For an EM6D board, the
EM6D board: 2.5GE port default logical types are
10GE optical ports for
Ports 1 and 2, and GE
optical ports for Ports 3
to 6. If actually used SFP
modules provide other
types of ports, delete the
default GE optical ports
and add actual ports on
the NMS.
l EM6D boards and RTN
380 must interconnect
through the same type of
ports. If port types at
both the local and remote
ends need to be changed,
change the port type at
the remote end and then
at the local end.
Super EPLA group l PLA type: S-EPLA On an EM6D board, the port
l Scheduling mode: that connects to an E-band
MODE B link must be configured as
the master port in a Super
l Master port: 5- EPLA group.
EM6D-3(Port-3)-1
l Slave ports: 5-
EM6D-4(Port-4)-1, 1-
ISV3, and 2-ISV3
l Other parameters: default
values
Procedure
Step 1 Optical port type
l On an EM6D board, each port has two logical port IDs, for example, 1(PORT-1)-1 and 1(PORT-1)-2. The
logical port IDs are reserved for further expansion of Super Dual Band functions. In the current version,
configure the logical port ID consistently for the interconnected RTN 900 and RTN 380.
l MODE A and MODE B map Common and Hitless respectively on the NMS.
l When Scheduling Mode is Hitless, In hitless mode, E-band link bandwidth changes do not affect the
transmission of high-priority services. In this mode, high-priority services are transmitted on common-
band links, and low-priority services are transmitted on E-band links. However, if high-priority services
exceed the common-band link bandwidth upon a burst, the excessive traffic cannot be transmitted by E-
band links and is discarded.
l When Scheduling Mode is Common, In common mode, high-priority and low-priority services are
distributed to common-band and E-band links based on their link bandwidths, implementing inter-
frequency AM.
l When Scheduling Mode is Hitless, This threshold can be specified for a Super EPLA group in hitless
mode. The values 0 to 7 map to BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7 of PHBs. Only an SP queue
can be configured with a PHB. Services in this SP queue and other queues with higher-priorities are high-
priority services.
----End
Data Preparation
Parameter Value in This Example Planning Principle
Optical port type COMBO and GE(o) ports: l By default, logical ports
2.5GE ports for the RTN 380 are GE
optical ports. If actually
used SFP modules
provide other types of
ports, delete the default
GE optical ports and add
actual ports on the NMS.
l EM6D boards and RTN
380 must interconnect
through the same type of
ports. If port types at
both the local and remote
ends need to be changed,
change the port type at
the remote end and then
at the local end.
Procedure
Step 1 Delete E-LAN services.
Step 4 Configure the COMBO and GE(o) ports as 2.5GE optical ports.
On the GE(o) port, for example:
1. Delete the default GE port.
----End
3 Maintenance Instructions
NOTE
Users can monitor RMON performance statistics collected by Super EPLA group only on the U2000.
3.2 Troubleshooting
This section describes how to troubleshoot faults in the Super Dual Band solution.
NOTICE
Fault point 6, that is, a fault on a Super EPLA processing board, interrupts all services. The
other fault points trigger protection switching and interrupt some services.
NOTE
l If a fault causes a failure of a Super EPLA group or a member in a Super EPLA group,
PLA_MEMBER_DOWN_EXT and PLA_DOWN alarms are reported.
l For details about how to handle alarms reported on fault points, see Maintenance Guide of the RTN
900 and RTN 380.
3.3.1 PLA_CFG_MISMATCH
Description
The PLA_CFG_MISMATCH alarm indicates that physical link aggregation (PLA)
configurations are inconsistent at two ends of a microwave link.
Attribute
Alarm Severity Alarm Type
Critical Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Name Meaning
NOTE
If the value of Parameter 4 is 0x06-0x0D, 0x01 or 0x02, the enhanced compression configurations for
each queue, Layer 2 header compression configuration and Layer 3 header compression configuration in
the PLA protection group may not take effect.
Possible Causes
l Cause 1: The PLA group is configured on the local NE, but not configured on the peer
NE.
l Cause 2: Frame header compression is enabled for only one NE.
l Cause 3: The number of member links in the PLA group is different at both ends.
l Cause 4: Local member ports and peer member ports do not belong to the same PLA
group.
l Cause 5: Enhanced compression is enabled for only one NE.
l Cause 6: The Super EPLA configurations are inconsistent at the two ends of the
microwave link.
Procedure
Step 1 Cause 1: The PLA group is configured on the local NE, but not configured on the peer NE.
1. Configure the PLA group on the peer NE by referring to Creating a PLA/EPLA/EPLA+/
Super EPLA Group.
Step 2 Cause 2: Frame header compression is enabled for only one NE.
1. Determine the port that needs to be re-configured. For details, see Querying the Status of
a PLA/EPLA/EPLA+/Super EPLA Group and the network plan.
2. Enable or disable frame header compression on the port to ensure configuration
consistency at both ends. For details, see Configuring Ethernet Frame Header
Compression and Error Frame Discarding over Air Interfaces.
Step 3 Cause 3: The number of member links in the PLA group is different at both ends.
1. Set the number of member links consistently at both ends by referring to Creating a
PLA/EPLA/EPLA+/Super EPLA Group.
Step 4 Cause 4: Local member ports and peer member ports do not belong to the same PLA group.
1. Check whether PLA configurations of the interconnected IF boards comply with the
network plan. For details, see Creating a PLA/EPLA/EPLA+/Super EPLA Group.
Option Description
If... Then...
The configurations do not comply Re-configure the PLA group according to the
with the network plan network plan.
The configurations comply with Verify the IF cable connections between the IF
the network plan boards and ODUs to make sure the radio links
are correctly established.
Step 6 Cause 6: The Super EPLA configurations are inconsistent at the two ends of the microwave
link.
1. If the NE reports the parameters 0x0E to 0x14, the Super EPLA configurations are
inconsistent at the two ends. Modify the Super EPLA configurations to ensure consistent
configurations at the two ends. For details, see Creating a Super EPLA Group.
Step 7 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
3.3.2 PLA_DOWN
Description
The PLA_DOWN alarm indicates that a PLA group is faulty. This alarm is reported when the
number of active member links in a PLA group is 0 or smaller than the preset minimum
number of active member links.
NOTE
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
Name Meaning
Possible Causes
The number of active member links in the PLA group is 0 or smaller than the preset minimum
number of active member links.
Procedure
Step 1 Check whether the specified minimum number of active links is consistent with the network
plan. If not, re-configure the minimum number of active links. For details, see querying PLA
group status.
----End
Related Information
None
3.3.3 PLA_MEMBER_DOWN_EXT
Description
The PLA_MEMBER_DOWN_EXT alarm is reported when a member link of a Super EPLA
group is faulty.
Attribute
Parameters
Name Meaning
Possible Causes
l Cause 1: The general-band microwave link in the super EPLA group at the local end is
faulty.
l Cause 2: An IF board in the super EPLA group at the local end is faulty.
l Cause 3: The E-band microwave link in the super EPLA group at the local end is faulty.
l Cause 4: The E-band device in the super EPLA group at the local end is faulty.
Procedure
Step 1 Cause 1: The general-band microwave link in the super EPLA group at the local end is faulty.
1. Determine the faulty IF board and microwave link based on the ID of the Super EPLA
group. For details, see querying the status of a Super EPLA group.
2. Check whether a member link of the Super EPLA group reports MW_LOF, MW_LIM,
MW_RDI, R_LOC, or R_LOF alarms. If any of the preceding alarms is reported, clear
it.
Step 2 Cause 2: An IF board in the super EPLA group at the local end is faulty.
1. Determine the faulty IF board based on the ID of the Super EPLA group. For details, see
querying the status of a Super EPLA group.
2. Check whether any IF board in the Super EPLA group reports HARD_BAD,
BD_STATUS, VOLT_LOS, WRG_BD_TYPE, or RADIO_MUTE alarms. If any of the
preceding hardware-related alarms is reported, clear it.
Step 3 Cause 3: The E-band microwave link in the super EPLA group at the local end is faulty.
1. If the NMS can access the RTN 380, troubleshoot the E-band link fault by following
instructions in "Troubleshooting Microwave Link Faults of the OptiX RTN 380
Maintenance and Fault Management.
2. If the NMS cannot access the RTN 380, troubleshoot the fault by referring to the
troubleshooting steps for Cause 4.
Step 4 Cause 4: The E-band device in the super EPLA group at the local end is faulty.
1. Check whether an ETH_LOS alarm is reported at the local end. If yes, clear the alarm
immediately. If the RTN 380 is faulty, rectify the fault by following instructions in the
OptiX RTN 380 Maintenance and Fault Management.
----End
Related Information
None
3.3.4 PLA_PKT_ERR
Description
The PLA_PKT_ERR alarm indicates that packet reassembly fails in the receive direction.
Attribute
Alarm Severity Alarm Type
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 and 2 Indicate the ID of the PLA group.
Possible Causes
Cause 1: A member link in the PLA group is faulty.
Cause 2: The local or cascaded NE has a hardware fault.
Procedure
Step 1 Check for MW_LOF, MW_LIM, MW_RDI, and R_LOF alarms on links in the PLA group
and clear them if any. If no such alarm is reported, go to the next step.
Step 2 Check for the HARD_BAD alarm on the local and cascaded NEs. If the local or cascaded NE
reports the HARD_BAD alarm, replace the alarmed board by following instructions in
Replacing the System Control, Switching and Timing Board.
----End
Related Information
None