RTN Super Dual Band Solution

OptiX RTN Super Dual Band Solution
V100R010C00
Super Dual Band User Manual
Issue Draft 01
Date 2017-09-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the 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.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Super Dual Band User Manual Contents
Contents
1 Feature Description....................................................................................................................... 1
1.1 Introduction.................................................................................................................................................................... 2
1.2 Typical Applications.......................................................................................................................................................3
1.2.1 Tail Node Application..................................................................................................................................................3
1.2.2 Aggregation Transmission Application....................................................................................................................... 4
1.2.3 Back-to-Back Application........................................................................................................................................... 4
1.2.4 Large-Capacity Aggregation Upstream Application................................................................................................... 4
1.2.5 Optical Fiber Supplementing and Aggregation Application....................................................................................... 5
1.2.6 Hybrid Application with Third-Party Equipment........................................................................................................5
1.3 Feature Enhancement..................................................................................................................................................... 6
1.3.1 Super Dual Band Relay............................................................................................................................................... 6
1.3.2 Dual-Band Antenna..................................................................................................................................................... 7
1.4 Principles........................................................................................................................................................................ 8
1.4.1 Principles (Master Device Is an RTN 905 1E/2E).......................................................................................................8
1.4.2 Principles (Master Device Is an RTN 950/950A)........................................................................................................9
1.4.3 Principles (Master Device Is an RTN 980)................................................................................................................10
1.4.4 Principles (Master Device Is an RTN 380H)............................................................................................................. 11
1.4.5 Super EPLA............................................................................................................................................................... 12
1.5 Switching Conditions................................................................................................................................................... 15
1.6 Specifications................................................................................................................................................................16
1.7 Availability................................................................................................................................................................... 21
1.8 Feature Updates............................................................................................................................................................ 22
1.9 Feature Dependencies and Limitations.........................................................................................................................23
1.10 Planning Guidelines....................................................................................................................................................33
1.11 FAQs........................................................................................................................................................................... 33
2 Deployment Instructions........................................................................................................... 34
2.1 General Deployment Process........................................................................................................................................35
2.2 Configuration Process (Master Device Is an RTN IDU 900)....................................................................................... 37
2.3 Configuration Process (Master Device Is an RTN 380H)............................................................................................ 39
2.4 Configuration Example (Master Device Is an RTN 950/RTN 950A).......................................................................... 41
2.4.1 Networking Diagram................................................................................................................................................. 42
2.4.2 Configuration Procedure (RTN 950/950A)............................................................................................................... 43
2.4.3 Configuration Procedure (RTN 380)......................................................................................................................... 46
Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential ii

Super Dual Band User Manual Contents
2.5 Configuration Example (Master Device Is an RTN 380H).......................................................................................... 50

2.5.1 Networking Diagram................................................................................................................................................. 51
2.5.2 Configuration Procedure (RTN 380H)...................................................................................................................... 51
2.5.3 Configuration Procedure (RTN 320)......................................................................................................................... 55
3 Maintenance Instructions.......................................................................................................... 60
3.1 RMON Performance.....................................................................................................................................................61
3.2 Troubleshooting (the Master Device Is an RTN IDU 900).......................................................................................... 67
3.3 Alarm Reference...........................................................................................................................................................69
3.3.1 PLA_CFG_MISMATCH...........................................................................................................................................69
3.3.2 PLA_DOWN............................................................................................................................................................. 73
3.3.3 PLA_MEMBER_DOWN_EXT................................................................................................................................ 74
3.3.4 PLA_PKT_ERR........................................................................................................................................................ 77
Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential iii

Super Dual Band User Manual 1 Feature Description
1 Feature Description
About This Chapter
Super Dual Band is a large-bandwidth and long-distance microwave transmission solution

using a cross-band link aggregation technology.
1.1 Introduction
This section defines Super Dual Band and describes its purpose.
1.2 Typical Applications
This section describes five typical applications supported by Super Dual Band.
1.3 Feature Enhancement
This section describes the enhancement to Super Dual Band.
1.4 Principles
This section describes the principles of Super Dual Band.
1.5 Switching Conditions
Either a link fault or a hardware fault will trigger Super enhanced physical link aggregation
(EPLA) switching.
1.6 Specifications
This section lists Super Dual Band specifications.
1.7 Availability
This section lists the hardware requirements that must be met to implement Super Dual Band.
1.8 Feature Updates
This section provides a history of Super Dual Band updates.
1.9 Feature Dependencies and Limitations
This section describes the dependencies and limitations of Super Dual Band.
1.10 Planning Guidelines
This section provides guidelines for planning Super Dual Band.
1.11 FAQs
This section answers FAQs about Super Dual Band.
Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 1

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.
Figure 1-1 Super Dual Band solution
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 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 over 10
km. With Super Dual Band Relay, a three-fold transmission distance can be achieved.

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 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
Transmission Medium Long Short

distance (3 km to 10 km) (< 100 km) (< 3 km)
Bandwidth High Low High
Construction period Short Short Short
1.2 Typical Applications

This section describes five typical applications supported by Super Dual Band.
1.2.1 Tail Node Application

The RTN 905 1E/2E products and full-outdoor Super Dual Band solutions apply to tail nodes.
RTN 905 1E/2E

The RTN 905 1E supports one Super Dual Band group. The RTN 905 2E supports two Super
Dual Band groups, which can construct a Super Dual Band chain or ring networking.
Figure 1-2 Typical Super Dual Band networking
Full-Outdoor Super Dual Band Solution

The RTN 380H using the MXXI5 system control board can be used as the master device of
Super Dual Band, supports cascading with the RTN 320 device through a GE optical port or a
GE electrical port for a Super Dual Band group, and applies to tail nodes.

Figure 1-3 Typical networking of a full-outdoor Super Dual Band solution
1.2.2 Aggregation Transmission Application

The RTN 950/950A/980 support aggregation transmission application.
Aggregation transmission means that services from multiple IP microwave links are
aggregated on an NE and then transmitted through Super Dual Band links.
Figure 1-4 Typical aggregation transmission networking
1.2.3 Back-to-Back Application

The RTN 950/950A/980 supports Back-to-Back Application.
Back-to-back networking means that two hops of Super Dual Band links transmit services in
back-to-back mode. In this networking mode, NEs used for back-to-back networking can
access local services or services from other links.
Figure 1-5 Typical back-to-back networking
1.2.4 Large-Capacity Aggregation Upstream Application

The RTN 950/950A/980 supports large-capacity aggregation upstream application.
Services from four Super Dual Band link groups can be aggregated and forwarded. This
networking applies to dense convergence sites.

Figure 1-6 Large-capacity convergence upstream networking
1.2.5 Optical Fiber Supplementing and Aggregation Application

The RTN 950/950A/980 supports optical fiber supplementing and aggregation application.
This networking supports a maximum air-interface capacity of 10 Gbit/s and can be used to
form a microwave/optical hybrid ring network in places where optical fibers cannot be laid
out. While providing supplementary transmission to optical fibers, this networking can also
aggregate services from multiple links.
Figure 1-7 Optical fiber supplementing and aggregation networking
1.2.6 Hybrid Application with Third-Party Equipment

The RTN 380H using the MXXI5 system control board supports interworking third-party
common-band equipment to implement an unprotected Super Dual Band solution.

In the Super Dual Band solution of hybrid application with third-party common-band
equipment, the RTN 380H status is fixed to master and the third-party equipment status is
fixed to slave. The RTN 380H and third-party common-band equipment are cascaded through
the GE optical port or GE electrical port. The single–GE port cascading scenario is supported.
Figure 1-8 Typical networking of hybrid application with third-party common-band

equipment
1.3 Feature Enhancement

This section describes the enhancement to Super Dual Band.
1.3.1 Super Dual Band Relay

Super Dual Band Relay provides highly efficient and dedicated relay transmission for an E-
band link.
When Super Dual Band applies to the aggregation backhaul with a medium distance, the
transmission distance of E-band links generally cannot meet requirements. You can use the
Super Dual Band Relay solution to add relay sites to an E-band link to increase the
transmission distance of Super Dual Band without affecting the link bandwidth.
Figure 1-9 Super Dual Band Relay (two hops of relay)

Figure 1-10 Super Dual Band Relay (three hops of relay)
Figure 1-11 Super Dual Band Relay (multi-hop relay)
Super Dual Band Relay has the following features:
l Supports a maximum of three E-band relay hops, which triples the Super Dual Band
transmission distance.
l Supports bidirectional bandwidth notification. If the air-interface bandwidth of a relay
microwave link fluctuates, the bandwidth fluctuation will be bidirectionally reported to
the master devices of Super Dual Band at the two ends of the microwave link in real time
to guarantee real-time control and service QoS assurance for end-to-end traffic in the
microwave link of Super Dual Band.
l Supports multiple E-band relay hops but with the same E-band device type (that is, either
RTN 380 or RTN 380H).
l Supports AM and hitless switchover between multiple E-band trunk links.
1.3.2 Dual-Band Antenna

A dual-band antenna can carry common-band and E-band microwave links at the same time,
saving installation space and simplifying the installation procedure.
Traditionally, two antennas are used to transmit common-band and E-band signals
respectively. This poses high requirements for infrastructure construction, deployment, and
O&M at sites.
Dual-Band antennas supports the simultaneous transmission of signals carried by two

different frequencies. Dual-Band antennas reduce half the number of antennas required in a
Super Dual Band configuration and optimize the TCO for the configuration.

Figure 1-12 Dual-band antenna of Super Dual Band
The dual-band antenna of Super Dual Band has the following highlights:
l Reduced tower space and wind load, reduced infrastructure investments

With rapid network expansion, tower resources are becoming increasingly scarce. Using
only one dual-band antenna reduces not only tower wind load but also tower space lease
fees required for antenna installation. These benefits are especially apparent when the
traditional microwave evolves towards the SDB microwave. During the evolution,
legacy tower resources can be reused, greatly reducing maintenance costs.
l Easy installation and commissioning, shortened time to market
Only one dual-band antenna is required, simplifying antenna deployment and saving
50%+ installation time. Dual-band antennas are aligned based on the common band and
then E-band, greatly reducing antenna alignment difficulties.
l Reduced antennas and TCO
Only one antenna is required, greatly simplifying the E2E antenna delivery process
(including packaging, transportation, installation, and commissioning).
l Flexible application scenarios
The dual-band antenna uses two independent feed ports. Each port allows sufficient
space to install components such as the combiner and OMT, achieving flexible
combination of the RF configuration modes of the common-band and E-band in various
scenarios.
1.4 Principles
This section describes the principles of Super Dual Band.
1.4.1 Principles (Master Device Is an RTN 905 1E/2E)

This section describes the principles of the Super Dual Band solution where the master device
is the RTN 905 1E/2E.

The E-band link in the Super Dual Band solution where the master device is the RTN 905
1E/2E requires the RTN 380, not the RTN 380H. This solution has the following
characteristics:
l The RTN 905 1E supports one Super Dual Band group consisting of one common-band
link and one E-band link. The maximum capacity is 2.5 Gbit/s.
l The RTN 905 2E supports a maximum of two Super Dual Band groups. Either group
contains only one E-band link and provides a maximum capacity of 2.5 Gbit/s. The
maximum system capacity is also 2.5 Gbit/s.
l Super Dual Band services can be received/transmitted through ports GE1 to GE6 and
support Layer 2 switching.
The following figure shows the signal flow for the Super Dual Band solution where the
master device is the RTN 905 1E/2E.
Figure 1-13 Signal flow for the Super Dual Band (RTN 905 1E/2E) solution
1.4.2 Principles (Master Device Is an RTN 950/950A)

is the RTN 950/950A.
The Super Dual Band solution where the master device is the RTN 950/950A uses EM6D
boards to implement Super EPLA. In this solution:
l The EM6D board processes Super Dual Band services and aggregates links. It provides
six Ethernet ports: 2 x 10GE/2.5GE/GE (o) ports, 2 x 2.5GE/GE (o) ports, and 2 x GE
(e) ports.
l Each EM6D board supports two Super EPLA groups with a maximum of eight links.
Each Super Dual Band link aggregation group supports a maximum of eight member
links. The maximum capacity of each group is 10 Gbit/s, and the maximum system
capacity is also 10 Gbit/s.
l E-band devices (RTN 380s or RTN 380Hs) must be connected to the ports on the EM6D
boards.
l Services transmitted through Super EPLA groups must be accessed from the ports on the
EM6D boards. The EM6D boards support Layer 2 switching.

master device is the RTN 950/950A.
Figure 1-14 Signal flow for the Super Dual Band (RTN 950/950A) solution
1.4.3 Principles (Master Device Is an RTN 980)

is the RTN 980.
The Super Dual Band solution where the master device is the RTN 980 uses the packet
switching unit on the CSHNU board to implement Super EPLA, providing a larger capacity
and more flexible configurations. In this solution:
l CSHNU boards integrate EPLA/Super Dual Band processing modules to provide the
Super Dual Band service processing and link aggregation functions.
l A single NE supports four Super EPLA groups with a maximum of 16 links. The
maximum capacity of each group is 10 Gbit/s, and the maximum system capacity is 20
Gbit/s.
l RTN 380/380Hs supporting E-band links are connected to CSHNU or EX1 boards.
l Services transmitted through Super Dual Band can be accessed from any Ethernet
service ports or forwarded by other microwave links. Such services support Layer 2
switching.
master device is the RTN 980.

Figure 1-15 Signal flow for the Super Dual Band (RTN 980) solution
1.4.4 Principles (Master Device Is an RTN 380H)

is the RTN 380H.
Full-Outdoor Super Dual Band Solution

In the full-outdoor Super Dual Band solution, the RTN 380H using the MXXI5 system
control board is the master device. This solution has the following characteristics:
l It supports one Super Dual Band group consisting of a maximum of 4 member links. The
maximum capacity of Super Dual Band is 10 Gbit/s.
l The slave device can be an RTN 320 or an RTN 380H (using the MXXI5 system control
board).
l The master/slave device relationship of a Super Dual Band group is fixed, and device
switching is not supported.
l Services are accessed only from the master device RTN 380H, and a maximum of four
channels of services are supported.
l When the slave device is an RTN 320, the cascading rate can be 1 Gbit/s or 2.5 Gbit/s,
the cascading through an electrical or optical port is supported, and only single-port
cascading is supported. When the slave device is an RTN 380H, both single-port
cascading and dual-port cascading are supported, and the COMBO port must be
preferentially used as the cascade port.
l An XPIC group can be configured between common-band member links or E-band
member links of a Super Dual Band group.

Figure 1-16 Signal flow for the full-outdoor Super Dual Band solution
Super Dual Band Solution of Hybrid Application with Third-Party Common-

Band Equipment
This solution has the following characteristics:
l It supports one Super Dual Band group consisting of a maximum of 4 member links. The
maximum capacity of Super Dual Band is 10 Gbit/s.
l The master/slave device relationship of a Super Dual Band group is fixed, and device
switching is not supported.
l Services are accessed only from the master device RTN 380H, and a maximum of four
channels of services are supported.
l The RTN 380H and third-party common-band equipment are cascaded through the GE
optical port or GE electrical port, and only single-port cascading is supported.
l An XPIC group can be configured between common-band member links or E-band
member links of a Super Dual Band group on Huawei microwave devices. PLA/XPIC
can be configured on the third-party common-band device.
Figure 1-17 Signal flow for the Super Dual Band solution of hybrid application with third-
party common-band equipment
1.4.5 Super EPLA

Super Dual Band supports priority-based service scheduling, traffic adjustment, and link
protection.

NOTE
In this example, the principles of the Super Dual Band solution using EM6D boards are described.
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-18.
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/RTN 380H.
Figure 1-18 Super Dual Band principles
In the transmit direction:

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
In MODE A mode, high-priority and low-priority services are transmitted over both
common-band and E-band links.
n If the E-band link quality degrades, the modulation scheme downshifts step by
step, and link bandwidth decreases gradually. Services on E-band links are
switched to common-band links before E-band links are completely
unavailable. In this case, high-priority services within available bandwidth are
transmitted in hitless mode, and packet loss may occur in low-priority services.
n After E-band links recover, the EM6D board re-distributes high-priority and
low-priority services to both common-band and E-band links.
– MODE B mode
In MODE B mode, E-band link bandwidth changes do not affect the transmission of
high-priority services, ensuring hitless transmission of high-priority services.
Generally in this mode, high-priority services are transmitted on common-band
links, and low-priority services are transmitted on E-band links.
n If common-band links are normal and provide sufficient capacities for carrying
high-priority services, high-priority services are always transmitted on the
common-band links and therefore are not affected by any E-band link
bandwidth changes.
n If high-priority service traffic is higher than 90% of the total guaranteed
capacity provided by all common-band links, the system automatically
switches from the MODE B mode to the MODE A mode. After the high-

priority service traffic becomes lower than 70% of the total guaranteed
capacity provided by all common-band links, the system automatically
switches back to the MODE B mode after 1 minute.
n If common-band links have idle resources, they can transmit some low-priority
services.
n If common-band links are faulty, high-priority services are switched to E-band
links. In this case, high-priority services are transiently interrupted.
2. The EM6D board transmits services destined for the E-band link directly to the RTN
380. The EM6D board transmits services destined for common-band links to the
backplane, which then forwards the services to the corresponding IF boards.
3. The RTN 380 and IF boards/ODUs transparently transmit services to the peer end.
In the receive direction:
1. The master and slave links transmit the received Ethernet service signals to the EM6D
board.
2. The EM6D board combines the received Ethernet service signals into one channel and
transmits them to the service access port.
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-19 and Figure 1-20, 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.
Figure 1-19 Before switching

Figure 1-20 After switching
1.5 Switching Conditions

Either a link fault or a hardware fault will trigger Super enhanced physical link aggregation
(EPLA) switching.
Super EPLA switching triggered by a link fault and that by a hardware fault are executed in
the same way. Table 1-2 provides the trigger conditions for Super EPLA switching.
Table 1-2 Conditions for Super EPLA switching (Master Device Is an RTN IDU 900)
Switching Type Switching Condition
Super EPLA switching l MW_LOF

l R_LOF
l R_LOC
l MW_RDI
l MW_BER_EXC
l MW_BER_SD
l ETH_LOS
l PLA_CFG_MISMATCH
l HARD_BAD
l Board removal or a cold reset on a board
l BUS_ERR_0x3
l BUS_ERR_0x4
l BUS_ERR_0x5
l BUS_ERR_0x9
l POWER_ALM
l DEVICE_AUTH_FAIL

Table 1-3 Conditions for Super EPLA switching (Master Device Is an RTN 380H)
Switching Type Switching Condition
Super EPLA switching l MW_LOF

l R_LOF
l R_LOC
l MW_RDI
l MW_BER_EXC
l MW_BER_SD
l ETH_LOS
l PLA_CFG_MISMATCH
l HARD_BAD
l cold NE reset
l MW_FEC_EXC
l BUS_ERR_0x1
l BUS_ERR_0xa
1.6 Specifications
This section lists Super Dual Band specifications.
Table 1-4 Super Dual Band specifications (the master device is an RTN IDU 900)
Item Specifications
IDU type RTN 950 RTN 950A RTN 980 RTN 905 RTN 905
(CSHU/ (SLF2CSH (CSHNU 1E 2E
CSHUA O boards) boards)
boards)
IF board l ISV3 l ISV3 ISV3 (integrated IF unit)

l ISM6 l ISM6
l ISU2/ISX2 l ISU2/
l IFU2 ISX2
Full-outdoor l RTN 380 (MXUF4) RTN 380 (MXUF4)

microwave device l RTN 380H

Item Specifications
Super EPLA EM6D l CSHNU EG6e

processing board – SLB
2EX
1
– SLB
2EG
4
l EX1
(togethe
r with
CSHNU
)
Maximum 3×2b 3×2b 4 1 2

number of Super
EPLA groups a
Maximum 3×8b 3×8b 16 3 6

number of
members in all
Super EPLA
groups
Maximum 8 8 16 3 4
number of
members in a
Super EPLA
group
Service type Native E-LAN/E-Line Native E- Native E-LAN/E-Line

supported by service LAN/E- service
Super EPLA Line/
processing boards MPLS/
L3VPN
service
Maximum 10 Gbit/s 10 Gbit/s 10 Gbit/s 2.5 Gbit/s 2.5 Gbit/s

bandwidth of a
Super EPLA
group
Maximum total 3×10 3×10 20 Gbit/s 2.5 Gbit/s 2.5 Gbit/s

bandwidth of Gbit/sb Gbit/sb
Super EPLA
groups supported
by an NE

Item Specifications
Dynamic Supported
adjustment of
Super EPLA
group bandwidth
according to
Ethernet
bandwidth on
microwave links
Switching time < 500 ms
Super EPLA Two modesc: MODE A Access modec

scheduling mode
l MODE A mode (default value)
l MODE B mode
Priorities of Super Configurable Not supported

EPLA members l Automatic mode (default value)
l Low
l High
Threshold BE, AF1, AF2, AF3, AF4, EF, CS6, and Not supported
distinguishing CS7d
high-priority and
low-priority
services in a
Super EPLA
group
Super Dual Band Supported

Relay

Item Specifications
l a: The number of supported Super EPLA groups is restricted by the following factors:
– The number of Super EPLA groups supported by the RTN 950/950A is independent
of EPLA/EPLA+ groups.
– When the SCC board is CSHNU, EPLA, enhanced N+1 protection, and Super Dual
Band share EPLA group resources. When the PLA ID falls within the range of 1-20
or 21–40, at most any two of EPLA, enhanced N+1 protection, and Super Dual
Band can be configured.
l b: Super Dual Band is implemented based on EM6D boards:
– A single NE can house a maximum of three EM6D boards.
– An EM6D board supports a maximum of two Super EPLA groups. Each Super
EPLA group can contain a maximum of eight members, and its maximum
bandwidth is 10 Gbit/s. An EM6D board supports a maximum of eight members,
and its maximum total bandwidth is 10 Gbit/s.
l c: The Super EPLA scheduling modes are described as follows:
– In MODE A 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. Before E-band links are completely unavailable, services within
available bandwidth are switched to common-band links in hitless mode.
– In MODE B mode, E-band link bandwidth changes do not affect the transmission of
high-priority services, ensuring hitless transmission of high-priority services. In this
mode, high-priority services are transmitted on common-band links.
– The MODE A Access mode is specific only to the RTN 905 1E/2E, and its service
scheduling mode is similar to MODE A.
l d: In MODE B mode, a threshold can be specified to determine the priority of a service.
The buffer queue that maps to the configured PHB service level must be an SP queue.
The buffer queue and queues with higher priorities map to high-priority services.
l e: When the RTN 905 1E/2E uses optical ports of EG6 boards, the data rate of port 5
must be the same as that of port 6.
Table 1-5 Super Dual Band specifications (the master device is an RTN 380H)
Item Specifications
Type of the supported l RTN 380H (using MXXI5)

slave device l RTN 320
l Third-party common-band device
Cascade port l GE optical port (10GE1, 10GE2, or COMBO)f

l GE electrical port (COMBO(e) or P&E)
Maximum number of 1
Super EPLA groups

Item Specifications
Maximum number of 4g
members in a Super
EPLA group
Maximum number of 4
members in all Super
EPLA groups
Service type supported Native Ethernet/Native E-LAN/MPLS service

by Super EPLA
processing boards
Maximum bandwidth of 10 Gbit/s

a Super EPLA group
Maximum total 10 Gbit/s

bandwidth of Super
EPLA groups supported
by an NE
Dynamic adjustment of Supported

Super EPLA group
bandwidth according to
Ethernet bandwidth on
microwave links
Switching time < 500 ms
Super EPLA scheduling MODE A modeh

mode
Priorities of Super Not supported

EPLA members
Super Dual Band Relay Not supported
End-to-end delay Third-party common-band device < 900 µs
Cascading scenario l When the slave device is an RTN 320:

– One cascade port and one microwave channel
– One cascade port and two microwave channels
l When the slave device is an RTN 380H:
– One cascade port
– Two cascade ports
l When the slave device is a third-party common-band device:
– One cascade port and one microwave channel
Working mode l When the slave device is an RTN 320, the IS3/IS6 mode is
supported.
l When the slave device is an RTN 380H (using MXXI5), the
enhanced and common modes are supported.

Item Specifications
l f: When the slave device is an RTN 380H, the COMBO port must be preferentially used
as the cascade port.
l g: The maximum number of members in a Super EPLA group is limited as follows:
– When the slave device is an RTN 320 or RTN 380H, two-level cascading is not
supported.
– When the slave device is a third-party common-band device, RTN 380H or RTN 320
can be cascaded to the master device RTN 380H.
l h: The Super EPLA scheduling modes are described as follows:
– In MODE A 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. Before E-band links are completely unavailable, services within
available bandwidth are switched to common-band links in hitless mode.
1.7 Availability
This section lists the hardware requirements that must be met to implement Super Dual Band.
Hardware Requirements (the Master Device Is an RTN IDU 900)

Featur Hardware Requirements
e
Name
Super IDU type RTN 950 RTN 950A RTN 980 RTN 905 RTN 905
Dual (CSHU/ (SLF2CSH (CSHNU 1E 2E
Band CSHUA O boards) boards)
boards)
IF board ISV3/ISM6/ISU2/ISX2/ ISV3/ ISV3

IFU2 ISM6/
ISU2/ISX2
Super Dual EM6D CSHNU CSHP

Band
processing
board
Full- l RTN 380 (MXUF4) RTN 380 (MXUF4)

outdoor l RTN 380H
microwave
device

Hardware Requirements (the Master Device Is an RTN 380H)

Feature Name Hardware
Super Dual Band System control board MXXI5
Working mode Enhanced and common modes
Type of the slave device l RTN 320

l RTN 380H (using MXXI5)
l Third-party common-band device
1.8 Feature Updates

This section provides a history of Super Dual Band updates.
Feature Updates
Version Description
l RTN 950/RTN 950A: Super Dual Band is first available in RTN 950/RTN 950A
V100R008C10 or later V100R008C10 and RTN 380 V100R006C00.
l RTN 380:
V100R006C00
l RTN 950/RTN 950A: An EM6D supports intra-board E-LAN service

V100R009C00 configuration.
l RTN 380:
V100R007C00
l RTN 980/RTN 905 l The RTN 980 supports Super Dual Band through the
1E/RTN 905 2E: CSHNU board.
V100R009C10 l The RTN 905 1E/2E supports Super Dual Band through
l RTN 380H: a software upgrade.
V100R007C10 l The RTN 380H supports Super Dual Band.
l Super Dual Band Relay is supported.
l Common-band links are supported by the ISU2, ISX2,
and IFU2 boards.
l Super Dual Band is enhanced to support 1+1 protection.
l RTN 380H: l The full-outdoor Super Dual Band scenario where the
V100R008C00 master device is an RTN 380H is supported.
l RTN 320: l The Super Dual Band scenario where the master device
V100R008C00 RTN 380H interconnects with a third-party common-
band device is supported.
l Dual-band antennas are supported.
l When the RTN 900 serves as the master device, Super
Dual Band is enhanced to support 1588v2.

1.9 Feature Dependencies and Limitations

This section describes the dependencies and limitations of Super Dual Band.
Self-limitations
Table 1-6 Self-limitations (the master device is an RTN 950/RTN 950A)

Item Description
Members in a l Members cannot be dynamically added or deleted.

Super EPLA l Members can work in different IS modes.
group
l The upper threshold for the ratio of the maximum link bandwidth to
the minimum link bandwidth in a Super EPLA group is 100:1.
l The 3.5 MHz channel spacing is not supported.
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.
IF board l An IF port can be configured in only one Super EPLA group.

l Both IF ports on an ISM6 board can be configured in a Super EPLA
group. If only one IF port on an ISM6 board is a member in a Super
EPLA group, the other IF port on the board cannot use data services
or protocols.
l The total air-interface Ethernet bandwidth of a common band cannot
be higher than 1.5 Gbit/s.
l The air-interface Ethernet bandwidth of the ISM6 board in a single
slot cannot be higher than 1.5 Gbit/s.
Service type Only the Native E-LAN and E-Line services are supported. The services
can be accessed from Ethernet ports or transferred from IF ports.
EM6D board l Only the Native E-LAN and E-Line services are supported.
l You cannot directly configure a service from a service access port on
an EM6D board to another Ethernet board. Instead, you can use a
fiber jumper to connect the service access port on the EM6D board
and a port on another Ethernet board and configure an E-Line service
from the service access port to the master port in the Super EPLA
group on the EM6D board.
l An EM6D board must be housed in left-side slot 1/3/5.

Item Description
E-band link l The E-band device can be an RTN 380 or RTN 380H. A Super EPLA
group can support either the RTN 380 or RTN 380H but cannot
support both.
l Ethernet ports connecting an EM6D and an RTN 380/380H must be of
the same type.
l After the RTN 380/RTN 380H is connected to the EM6D board, the
Ethernet and IF ports on the RTN 380/RTN 380H can no longer be
configured with services.
l An RTN 380/380H supports only one Super EPLA group.
l One RTN 380/380H can be connected to an EM6D board through a
maximum of two Ethernet links. In addition, the RTN 380H must use
COMBO ports for connecting to the EM6D board.
l If a Super EPLA group is configured on an RTN 380/380H, the
inband DCN function must be disabled on its IF port.
l A Super EPLA group cannot be configured for the P&E port of the
RTN 380H.
l Air-interface Ethernet bandwidth of the RTN 380:
– The maximum air-interface Ethernet bandwidth for the GE
Ethernet port is 650 Mbit/s.
– The maximum air-interface Ethernet bandwidth for the 2.5GE
– The maximum air-interface Ethernet bandwidth for all Ethernet
ports on the RTN 380 is 3350 Mbit/s.
l Air-interface Ethernet bandwidth of the RTN 380H:
– The maximum air-interface Ethernet bandwidth for the 10GE
ports on the RTN 380H is 8250 Mbit/s.
Interconnectio l Super EPLA groups must be symmetrically deployed at two ends. To

n be specific, common-band links, E-band links, and the cable rate
between the RTN 380/380H and the EM6D board must be
consistently planned at two ends. Ports at both ends of a cable or link
must be configured as follows: The large port ID of one end maps to
the large port ID of the other end, and the small port ID of one end
maps to the small port ID of the other end. For example, if port IDs at
one end are ports 1 and 3 and port IDs at the other end are ports 2 and
5, port 1 is connected to port 2 and port 3 is connected to port 5.
l The Super Dual Bands for the RTN 950/950A/980 can interconnect
with each other.

Item Description
Service On an EM6D board or an RTN 380/380H, each port has two service
channel ID channel IDs, for example, 1(PORT-1)-1 and 1(PORT-1)-2. The service
channel IDs are reserved for further expansion of Super Dual Band. In
the current version, configure the service channel ID consistently for
corresponding ports on the EM6D boards and RTN 380/380H containing
a Super Dual Band link. You are advised to set the service channel ID to
1.
Reserved air- During link planning, 512 kbit/s Ethernet bandwidth must be reserved for
interface each Super EPLA link to function as the protocol channel. Otherwise, the
Ethernet Super EPLA group cannot work stably.
bandwidth
Super Dual l An E-band link supports a maximum of three hops of relay links or a
Band Relay maximum of two E-band relay sites.
l The types of devices on an E-band trunk link must be the same, and
the sequence numbers of cascade ports between back-to-back NEs
must be consistent.
l Super Dual Band Relay supports two or more E-band relay hops.
Each relay hop must contain devices of the same type and have the
same number of air-interface hops.
l If Super Dual Band Relay is deployed, E-band links do not support
62.5 MHz channel bandwidth, and common-band links using IFU2
boards do not support 7 MHz bandwidth.
Table 1-7 Self-limitations (the master device is an RTN 980)

Item Description

Super EPLA l Members can work in different IS modes.
group
l The 3.5 MHz channel spacing is not supported.
l An IF port or an Ethernet port connecting to an E-band link can
function as the main port.
IF board l An IF port can be configured in only one Super EPLA group.

l Both IF ports on an ISM6 board can be configured in a Super EPLA
group. If only one IF port on an ISM6 board is a member in a Super
EPLA group, the other IF port on the board cannot use data services
or protocols.
Service type The Native E-LAN, Native E-Line, MPLS, and L3VPN services are
supported. The services can be accessed from Ethernet ports or
transferred from IF ports.

Item Description
E-band link l The E-band device can be an RTN 380 or RTN 380H. A Super EPLA
group can support either the RTN 380 or RTN 380H but cannot
support both.
l Ethernet ports connecting a system control board and an RTN
380/380H must be of the same type.
l After the RTN 380/RTN 380H is connected to the CSHNU board, the
Ethernet and IF ports on the RTN 380/RTN 380H can no longer be
configured with services.
l An RTN 380/380H supports only one Super EPLA group.
l One RTN 380/380H can be connected to a system control board
(supporting Super Dual Band) through a maximum of two Ethernet
links. In addition, the RTN 380H must use COMBO ports for
connecting to the system control board.
l If a Super EPLA group is configured on an RTN 380/380H, the
inband DCN function must be disabled on its IF port.
l A Super EPLA group cannot be configured for the P&E port of the
RTN 380H.
l Air-interface Ethernet bandwidth of the RTN 380H:
– The maximum air-interface Ethernet bandwidth for the 10GE
ports on the RTN 380H is 8250 Mbit/s.

between the RTN 380/380H and the system control board must be
consistently planned at two ends. Ports at both ends of a cable or link
must be configured as follows: The large port ID of one end maps to
the large port ID of the other end, and the small port ID of one end
maps to the small port ID of the other end. For example, if port IDs at
one end are ports 1 and 3 and port IDs at the other end are ports 2 and
5, port 1 is connected to port 2 and port 3 is connected to port 5.
l The Super Dual Bands for the RTN 950/950A/980 can interconnect
with each other.

Item Description
Service On a CSHNU board or an RTN 380/380H, each port has two service
channel ID channel IDs, for example, 1(PORT-1)-1 and 1(PORT-1)-2. The service
channel IDs are reserved for further expansion of Super Dual Band. In
the current version, configure the service channel ID consistently for
corresponding ports on the CSHNU boards and RTN 380/380H
containing a Super Dual Band link. You are advised to set the service
channel ID to 1.
bandwidth
l If two ports between NEs cascaded in back-to-back mode are
connected using cascade cables, the port with the large port ID is
connected using one cable and the port with the small port ID is
connected using another cable. For example, if cascade ports of NE1
are ports 1 and 3 and cascade ports of NE2 are ports 2 and 5, port 1 is
connected to port 2 and port 3 is connected to port 5.
62.5 MHz channel bandwidth, and common-band links using IFU2
boards do not support 7 MHz bandwidth.
Table 1-8 Self-limitations (the master device is an RTN 905 1E/2E)

Item Description

Super EPLA l It is recommended that the common-band links use 14 MHz or higher
group channel bandwidth. Common-band links support 7 MHz channel
bandwidth if only one Super EPLA group is configured and the
capacity is no less than 1 Gbit/s.
l E-band links use 125 MHz or higher channel bandwidth.
l The master port must be an IF port.
Service type Only the Native E-LAN and E-Line services are supported. The services
can be accessed from Ethernet ports or transferred from IF ports.

Item Description
E-band link l The E-band devices can be RTN 380s.

l Ethernet ports connecting an IDU and an RTN 380 must be of the
same type.
l After the RTN 380 is connected to the IDU, the Ethernet and IF ports
on the RTN 380/RTN 380H can no longer be configured with
services.
l An RTN 380 supports only one Super EPLA group.
l One RTN 380 can be connected to an IDU through a maximum of two
Ethernet links.
l The inband DCN function must be disabled on IF ports.

between the RTN 380 and the RTN 905 1E/2E must be consistently
planned at two ends. Ports at both ends of a cable or link must be
configured as follows: The large port ID of one end maps to the large
port ID of the other end, and the small port ID of one end maps to the
small port ID of the other end. For example, if port IDs at one end are
ports 1 and 3 and port IDs at the other end are ports 2 and 5, port 1 is
connected to port 2 and port 3 is connected to port 5.
l The Super Dual Band for the RTN 905 1E/2E cannot interconnect
with that for the RTN 950/950A/980.
Service On an IDU or an RTN 380, each port has two service channel IDs, for
channel ID example, 1(PORT-1)-1 and 1(PORT-1)-2. The service channel IDs are
reserved for further expansion of Super Dual Band. In the current
version, configure the service channel ID consistently for corresponding
ports on the EM6D boards and RTN 380 containing a Super Dual Band
link. You are advised to set the service channel ID to 1.
bandwidth

Item Description
l The types of devices on an E-band trunk link must be the same, and
the sequence numbers of cascade ports between back-to-back NEs
must be consistent.
62.5 MHz channel bandwidth.
Table 1-9 Self-limitations (the master device is an RTN 380H)

Item Description

Super EPLA l If multiple RTN 320s work as slave devices, the IS running modes of
group RTN 320s can be different.
l When the slave device is a third-party common-band device:
– The upper threshold for the ratio of the E-band bandwidth to the
common-band bandwidth in a Super EPLA group is 100:1.
– If AM is configured on the third-party common-band device, the
master device must use the minimum bandwidth.
Cascade port l The cascade port can be a GE optical port or a GE electrical port.
When the slave device is an RTN 380H, the COMBO port must be
preferentially used as the cascade port.
l RTN 320 supports only one cascade port for RTN 380H cascading.
l When the slave NE uses the 1GE port to connect to an RTN 380H, the
port negotiation mode is Auto.
l When the slave NE uses the 2.5GE or 10GE port for interconnection
with an RTN 380H, you are advised to disable the unidirectional
operation capability of the port.
Service type l Native E-Line, Native E-LAN, and MPLS services are supported. The
services can only be accessed from Ethernet ports.
l When the slave device is a third-party common-band device, only
E2E transparent transmission services can be configured on the third-
party common-band device.
End-to-end l When the slave device is a third-party common-band device, the end-
delay to-end delay of third-party common-band device must be smaller than
900us.
Cascading l When the slave device is an RTN 320 or RTN 380H, two-level
mode cascading is not supported.

Item Description
Interconnectio l In the Super Dual Band solution using the combination of RTN 380H
n and a third-party common-band device, the DCN VLAN and
bandwidth of the third-party device must be configured on the port
that connects the RTN 380H to the third-party common-band device.
– This configuration must be performed based on the 256-byte
throughput that maps to the minimum modulation scheme of the
third-party device. If the throughput cannot be obtained, this
configuration must be performed based on the minimum value in
the third-party throughput range.
NOTE
The air-interface bandwidth must be higher than 20M.
– The DCN VLAN must be different from the service VLAN and
cannot be set to 0, 1, 2, 4094, or 4095.
l Super EPLA groups must be symmetrically deployed at two ends. To
be specific, the cable rate between common-band links and E-band
links must be consistently planned at two ends. Ports at both ends of a
cable or link must be configured as follows: The large port ID of one
end maps to the large port ID of the other end, and the small port ID
of one end maps to the small port ID of the other end. For example, if
port IDs at one end are ports 2 and 4 and port IDs at the other end are
ports 3 and 5, port 2 is connected to port 3 and port 4 is connected to
port 5.
l On an RTN 380H or an RTN 320, each port has two service channel
IDs, for example, 1(PORT-1)-1 and 1(PORT-1)-2. The service channel
IDs are reserved for further expansion of Super Dual Band functions.
In the current version, configure the service channel ID consistently
for all ports on the RTN 380Hs and RTN 380s consisting of a Super
Dual Band link. It is advised to set the service channel ID to 1.
l Channelized VLANs at the two ends of each member link in a Super
EPLA group must be the same.
l When the RTN 320 serves as the slave device, you are advised to use
the 2.5GE port when the air-interface bandwidth of microwave links
is larger than 500 Mbit/s.
bandwidth
Super Dual Not supported.

Band Relay
Device The master/slave device relationship of a Super Dual Band group is

switching fixed, and device switching is not supported.

Dependencies and Limitations Between Super Dual Band and Other Features
Table 1-10 Dependencies and limitations between super dual band and other features (the
master device is an RTN IDU 900)
Feature Description
Inband data l All common-band links in a Super EPLA group must use the same
communicatio inband DCN protocol.
n network l Air interfaces of E-band member links cannot use inband DCN.
(DCN)
XPIC Two common-band microwave links can form an XPIC group.
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.
1+1 protection l The Super Dual Band for the RTN 980 is compatible with 1+1
between active protection between active and standby system control, switching, and
and standby timing boards, but also with no protection for Ethernet ports on the
system control, boards.
switching, and l If 1+1 protection is configured between active and standby system
timing boards control, switching, and timing boards, it is recommended that the E-
band devices use two Ethernet links to connect Ethernet ports on the
active and standby system control, switching, and timing boards,
thereby minimizing hardware fault impacts.
1+1 l 1+1 SD couples only with the following modes of Super Dual Band:
HSB/FD/SD – MODE A mode (RTN 950/950A/980)
– MODE A Access mode (RTN 905 1E/2E)
l The main ports in 1+1 HSB/FD/SD protection groups of RTN
950/RTN 950A are allowed to form an EPLA/EPLA+ group, but a
1+1 IF protection group must be created prior to the EPLA/EPLA+
group. In this case, a main port is calculated as two EPLA/EPLA+
members.
l The main ports in 1+1 HSB/FD/SD protection groups of RTN
950/RTN 950A are allowed to form an EPLA/EPLA+ group, but a
1+1 IF protection group must be created prior to the EPLA/EPLA+
group. In this case, a main port is calculated as two EPLA/EPLA+
members.
l Only the same type of IF board can be used in 1+1 protection and
Super Dual Band coupling scenarios.

Table 1-11 Dependencies and limitations between super dual band and other features (the
master device is an RTN 380H)
Feature Description
Inband data l In-band DCN must be enabled on the master device but not on the
communicatio slave device.
n network
(DCN)
XPIC l In the full-outdoor Super Dual Band solution, an XPIC group can be
configured between common-band member links or E-band member
links of a Super Dual Band group. An XPIC group cannot be
configured between the member links of different frequency bands.
l In the Super Dual Band solution of hybrid networking with a third-
party common-band device, an XPIC group can be configured
between common-band member links or E-band member links of a
Super Dual Band group on Huawei microwave devices. An XPIC
group cannot be configured between the member links of different
frequency bands. XPIC can be configured on the third-party common-
band device.
PLA In the Super Dual Band solution of hybrid networking with a third-party
common-band device, PLA can be configured on the third-party
common-band device.
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.
Features That Conflict with Super Dual Band

This feature conflicts with the following features:
When the master device is an RTN IDU 900:
l Air-interface LAG
l PLA/EPLA/EPLA+
l Frame header compression
l Payload compression
l AES-based encryption at air interfaces
l IF N+1 protection
When the master device is an RTN 380H:
l IF 1+1 protection
l Air-interface LAG
l Frame header compression

1.10 Planning Guidelines

This section provides guidelines for planning Super Dual Band.
l When planning Super Dual Band, do as follows:
a. Learn the total volume of services to be transmitted, the proportion of high-priority
services and low-priority services, and the required availability.
b. Allocate the services to common-band and E-Band links:
n Ensure that the common-band links' total capacity is higher than the total
volume of high-priority services, and the E-band links' total capacity is higher
than the total volume of low-priority services.
n Allocate the to-be-transmitted services to member links according to the
service priorities.
c. Based on each member link's transmission capacity and link availability, perform
network planning and design.
1.11 FAQs
This section answers FAQs about Super Dual Band.
None

Super Dual Band User Manual 2 Deployment Instructions
2 Deployment Instructions
About This Chapter
This section provides instructions on how to configure and commission Super Dual Band.
2.1 General Deployment Process

The purpose of site commissioning is to set up microwave links and DCN connections.
2.2 Configuration Process (Master Device Is an RTN IDU 900)
This section describes the process for configuring Super Dual Band.
2.3 Configuration Process (Master Device Is an RTN 380H)
This section describes the process for configuring the full-outdoor Super Dual Band solution.
2.4 Configuration Example (Master Device Is an RTN 950/RTN 950A)
This section provides an example of how to configure Super Dual Band in point-to-point
mode.
2.5 Configuration Example (Master Device Is an RTN 380H)
mode.

2.1 General Deployment Process

The purpose of site commissioning is to set up microwave links and DCN connections.
The flowchart for deploying Super Dual Band is provided as follows.
Figure 2-1 Flowchart for deploying Super Dual Band (the master device is an RTN IDU 900)

Figure 2-2 Flowchart for deploying Super Dual Band (the master device is an RTN 380H)
The operations in the configuration flowchart are described as follows.
Table 2-1 General deployment process (the master device is an RTN IDU 900)
Step Operation Remarks
1 Performing site Perform basic NE

commissioning on the RTN configurations and
900 commission common-band
links by following
instructions in the
Commissioning and
Configuration of the RTN
900 product documentation.

380/RTN 380H commission E-band links by
following instructions in the
Commissioning and
380/RTN 380H product
documentation.

3 Configuring Super Dual Configure Super Dual Band

Band by following instructions in
2.2 Configuration Process
(Master Device Is an RTN
IDU 900).
Table 2-2 General deployment process (the master device is an RTN 380H)

380H commission E-band links by
following instructions in the
Commissioning and
380H product
documentation.
2 RTN 320/RTN 380H/Third- Perform basic NE

party common-band device configurations and
commission common-band
links by following
instructions in the
Commissioning and
Configuration of the product
documentations of the RTN
320/380H and third-party
common-band device.
3 Configuring Super Dual Configure Super Dual Band

Band by following instructions in
2.5 Configuration
Example (Master Device Is
an RTN 380H).
2.2 Configuration Process (Master Device Is an RTN IDU

900)
This section describes the process for configuring Super Dual Band.
The flowchart for configuring Super Dual Band on the RTN 900 and RTN 300 is provided as
follows.

Figure 2-3 Flowchart for configuring Super Dual Band
Table 2-3 Process of configuring Super Dual Band on the RTN 900
1 Configuring the SFP type For a port that supports

multiple types of SFP
modules, configure the type
of the SFP module actually
installed using the NMS.
2 Creating a Super EPLA Creating Super EPLA

group groups is the core of
configuring Super Dual
Band.

3 Creating Ethernet services After creating Super EPLA

groups, configure an E-Line
or E-LAN service between
the master ports in two
Super EPLA groups or
between the master port in a
Super EPLA group and a
service access port on an
EM6D board.
Table 2-4 Process of configuring Super Dual Band on the RTN 300
1 Deleting E-LAN services Before configuring Super

EPLA groups, delete default
2 Disabling the inband DCN E-LAN services, unbind
3 Unbinding QoS policies QoS policies, and disable
the inband DCN on the IF
ports on the RTN 300.

5 Creating a Super EPLA Creating Super EPLA

group groups is the core of
Band.
2.3 Configuration Process (Master Device Is an RTN 380H)

This section describes the process for configuring the full-outdoor Super Dual Band solution.
The flowchart for configuring Super Dual Band on the RTN 380H (master) and RTN
320/RTN 380H (slave) is provided as follows.
NOTE
The configuration procedure of a third-party device is similar to that of the slave device RTN 300.

Figure 2-4 Flowchart for configuring Super Dual Band
Table 2-5 Process of configuring Super Dual Band on the RTN 380H
1 Enabling the inband DCN Before configuring Super

EPLA groups, enable the
inband DCN on the IF ports
of the RTN 380H.
2 Unbinding QoS policies Before configuring Super

EPLA groups, unbind QoS
policies of the RTN 380H.


4 Creating a Super EPLA Creating a Super EPLA

group group is the core of
Band.
5 Creating Ethernet services After creating the Super

EPLA group, create
Ethernet services from the
IF ports on the RTN 380H to
service ports.
Table 2-6 Process of configuring Super Dual Band on the RTN 320/RTN 380H
1 Disabling the inband DCN Before configuring Super

EPLA groups, unbind QoS
2 Unbinding QoS policies policies and disable the
inband DCN on the IF ports
of the RTN 320/RTN 380H.

4 Creating a Super EPLA Creating a Super EPLA

group group is the core of
Band.
2.4 Configuration Example (Master Device Is an RTN

950/RTN 950A)
mode.
NOTE
This section uses the RTN 950/950A as an example to describe the configuration of Super Dual Band.

2.4.1 Networking Diagram

This section describes the networking of NEs.
NOTE
This section uses the RTN 950/950A as an example to describe the configuration of Super Dual Band.
Figure 2-5 shows the networking consisting of 2+0 common-band links and a 1+0 E-band
link.
l Port 1 on the EM6D board receives/transmits an Ethernet service carrying VLAN ID

100, and Port 2 on the board receives/transmits an Ethernet service carrying VLAN ID
200.
l Links 1 and 2 are common-band links, and Link 3 is an E-band link.
l Two 2.5GE ports on the EM6D board connect to the RTN 380 for increasing the link
capacity.
Figure 2-5 Networking diagram for Super Dual Band
Figure 2-6 Board configurations

2.4.2 Configuration Procedure (RTN 950/950A)

This section describes the procedure for configuring Super Dual Band on the RTN 950/950A.
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, GE optical
ports for Ports 3 to 4, and
GE electrical ports for
Ports 5 to 6. If actually
used SFP modules
provide other types of
Ports 1 to 4, 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

E-Line service Service from NodeB A On an EM6D board, an

l Source port: 5-EM6D-3 Ethernet service can be
configured only between the
l Sink port: 5-EM6D-1 master ports in two Super
l VLAN: 100 EPLA groups or between
Service from NodeB B the master port in a Super
EPLA group and a service
l Source port: 5-EM6D-3 access port.
l Sink port: 5-EM6D-2
l VLAN: 200
Procedure
Step 1 Optical port type
On Port 3, for example:
1. Delete the default GE port.

2. Add a 2.5GE port.
Step 2 Configure a Super EPLA group.

NOTE
l On an EM6D board or an RTN 380, each port has two service channel IDs, for example, 1(PORT-1)-1
and 1(PORT-1)-2. The service channel IDs are reserved for further expansion of Super Dual Band
functions. In the current version, configure the service channel ID consistently for all ports on the EM6D
boards and RTN 380s consisting of a Super Dual Band link. It is advised to set the service channel ID to
1.
l When Scheduling Mode is Mode B, 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 Mode A, 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 Mode B, This threshold can be specified for a Super EPLA group in hitless
mode. 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.

Step 3 Configure E-Line services on the EM6D board.
For example, create an E-Line service carrying VLAN ID 100:
----End
2.4.3 Configuration Procedure (RTN 380)

This section describes the procedure for configuring Super Dual Band on the RTN 380.

Data Preparation
Optical port type COMBO and GE(o) ports: l The default logical types
2.5GE ports are GE optical ports for
COMBO and GE(o)
ports, GE electrical ports
for other ports. If
actually used SFP
modules provide other
types of COMBO and
GE(o) ports, delete the
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,
the remote end and then
at the local end.
Super EPLA group Service channels Configure a Super EPLA

l 1-MXUF4-3(COMBO)-1 group according to the
network plan.
l 1-MXUF4-4(GE(o))-1
Procedure
Step 1 Delete E-LAN services.

Step 2 Disable the inband DCN function on an IF port.
Step 3 Unbind QoS policies.

NOTE
It is advised to unbind QoS policies on all ports.

Step 4 Configure the COMBO and GE(o) ports as 2.5GE optical ports.
On the GE(o) port, for example:

----End
2.5 Configuration Example (Master Device Is an RTN

380H)
mode.
NOTE
This section uses the full-outdoor Super Dual Band solution where the master device is an RTN 950/950A
and the slave device is an RTN 320 as an example to describe the configuration of Super Dual Band. The
method of configuring other Super Dual Band solutions is similar.

2.5.1 Networking Diagram

This section describes the networking of NEs.
Figure 2-7 shows the networking consisting of 2+0 common-band links and a 1+0 E-band
link. The RTN 380H and RTN 320 are cascaded through the GE port.
l The RTN 380H receives/transmits an Ethernet service carrying VLAN ID 100.
l Link 1 is an E-band link, and links 2 and 3 are common-band links.
l One 2.5GE port of the RTN 380H connect to the RTN 320 for increasing the link
capacity.
Figure 2-7 Networking diagram for Super Dual Band
2.5.2 Configuration Procedure (RTN 380H)

This section describes the procedure for configuring Super Dual Band on the RTN 380H.

Data Preparation
SFP type COMBO ports of the RTN l On the NMS, the

380H: 2.5GE ports COMBO, 10GE1, and
10GE2 ports of the RTN
380H are GE optical
ports by default, and
other ports are GE
electrical ports by
default. If the actually
used SFP modules of the
COMBO, 10GE1, and
10GE2 ports provide
other types of ports,
delete the default GE
optical ports and add
actual ports on the NMS.
l The port types of the
RTN 380H and RTN 320
must be the same. If they
are different, change the
port type at the remote
end first, and then
the local end.
Super EPLA group l PLA type: S-EPLA The IF port must be

l Master port: 1- configured as the master
MXXI5-1(IF) port in a Super EPLA group.
l Slave port:1-
MXXI5-3(COMBO)
l Other parameters: default
values
E-Line service Service from NodeB A On the RTN 380H, services

l Source port: 1- can be configured only
MXXI5-1(IF) between the IF port and the
GE port other than the
l Sink port: 1- cascade port in the Super
MXXI5-4(10GE2) EPLA group.
l VLAN: 100
Procedure
Step 1 Enable the inband DCN.

Step 2 Unbind QoS policies for ports.

NOTE
You are advised to unbind QoS policies for all ports.
Step 3 Configure the optical port type.



NOTE
l Each port of the RTN 380H and RTN 320 has two service channel IDs, for example, 1(PORT-1)-1 and
1(PORT-1)-2. The service channel IDs are reserved for subsequent expansion of the Super Dual Band
function. Currently, all RTN 380H and RTN 320 ports of one Super Dual Band link hop must use the
same service channel ID. You are advised to set the service channel ID to 1.

Step 5 Configure E-Line services.
----End
2.5.3 Configuration Procedure (RTN 320)

This section describes the procedure for configuring Super Dual Band on the RTN 320.

Data Preparation
Optical port type COMBO port of the RTN l On the NMS, the
320: 2.5GE port COMBO and GE3(o)
ports of the RTN 320 are
GE optical ports by
default, and other ports
are GE electrical ports by
default. If the actually
used SFP modules of the
COMBO and GE3(o)
ports provide other types
of ports, delete the
the NMS.
l The port types of the
RTN 380H and RTN 320
must be the same. If they
are different, change the
port type at the remote
end first, and then
the local end.
Super EPLA group Service channel: Configure a Super EPLA

l 1-DMC5-6(COMBO)-1 group according to the
network plan.
Procedure
Step 1 Disable the inband DCN function on an IF port.

Step 2 Unbind QoS policies for ports.

NOTE
You are advised to unbind QoS policies for all ports.

Step 3 Configure the COMBO port of the RTN 320 as a 2.5GE optical port.

----End

Super Dual Band User Manual 3 Maintenance Instructions
3 Maintenance Instructions
About This Chapter
This section provides maintenance instructions for Super Dual Band.
3.1 RMON Performance

Super Dual Band supports the collection of RMON performance statistics by Super EPLA
group and by port.
3.2 Troubleshooting (the Master Device Is an RTN IDU 900)
This section describes how to troubleshoot faults in the Super Dual Band solution.
3.3 Alarm Reference
This section describes the possible alarms for Super EPLA and how to handle them.

3.1 RMON Performance

Super Dual Band supports the collection of RMON performance statistics by Super EPLA
group and by port.
System control boards on the RTN 900 report RMON performance statistics collected by
Super EPLA group. Table 3-1 lists related performance events.
RTN 380/RTN 380H and ISU2/ISX2/ISV3/ISM6/EM6D/CSHNU/CSHP boards report

RMON performance statistics collected by port. Table 3-2 and Table 3-4 list related
performance events.
NOTE
Users can monitor RMON performance statistics collected by Super EPLA group only on the U2000.
Table 3-1 RMON performance events (Super EPLA group)
Performance Event Description
RXUNICAST Indicates the unicast packets received.
TXUNICAST Indicates the unicast packets transmitted.
TXBRDCAST Indicates the broadcast packets transmitted.
RXBGOOD Indicates the bytes in received good packets.
TXBGOOD Indicates the bytes in transmitted good packets.
RXGOODFULLFRAMESPEED Indicates the bit rate of good full-frame packets

received.
TXGOODFULLFRAMESPEED Indicates the bit rate of good full-frame packets

transmitted.
RXFULLBGOOD Indicates the count of good full-frame bytes received.
TXFULLBGOOD Indicates the count of good full-frame bytes

transmitted.
TXMULCAST Indicates the multicast packets transmitted.
TXPKT64 Indicates the count of transmitted 64-byte packets.
TXPKT65 Indicates the count of transmitted packets with a

length of 65 to 127 bytes.






length of from 1519 bytes to the MTU-specified bytes.
RXPKT1519 Indicates the count of received packets with a length

of from 1519 bytes to the MTU-specified bytes.
TXPKTS Indicates the packets transmitted.
TX_HS_TRAFF_BW_RATIO Indicates the ratio of the high-priority traffic to the

total bandwidth in the transmit direction.
TX_DROP_RATIO Indicates the packet loss ratio in the transmit direction.
TXBPS Indicates the bit rate in the transmit direction.
TXPPS Indicates the packet rate in the transmit direction.
TX_DROP_PKTS Indicates the packet loss count in the transmit

direction.
TXOCTETS Indicates the number of transmitted bytes.
RXBBAD Indicates the bytes in received bad packets.
RXOCTETS Indicates the number of received bytes.
RXPKTS Indicates the packets received.
RXBRDCAST Indicates the broadcast packets received.
RXMULCAST Indicates the multicast packets received.
RXPKT64 Indicates the count of received 64-byte packets.

of 65 to 127 bytes.

of 128 to 255 bytes.



ETHDROP Indicates the packet loss events.
PORT_RX_BW_UTILIZATION Indicates the current bandwidth usage on a port in the

receive direction.

PORT_TX_BW_UTILIZATION Indicates the current bandwidth usage on a port in the

transmit direction.
PORT_RX_BW_UTILIZATION_ Indicates the minimum bandwidth usage on a port in

MIN the receive direction.
PORT_TX_BW_UTILIZATION_ Indicates the minimum bandwidth usage on a port in

MIN the transmit direction.
PORT_RX_BW_UTILIZATION_ Indicates the maximum bandwidth usage on a port in

MAX the receive direction.
PORT_TX_BW_UTILIZATION_ Indicates the maximum bandwidth usage on a port in

MAX the transmit direction.
PORT_RX_BW_UTILIZATION_ Indicates the average bandwidth usage on a port in the

AVG receive direction.
PORT_TX_BW_UTILIZATION_ Indicates the average bandwidth usage on a port in the

AVG transmit direction.
ETHFCS Indicates the FCS errored frames (MAC_FCS).
Table 3-2 RMON performance events (Super EPLA group port: ISU2/ISX2/ISV3/ISM6/
EM6D/CSHNU/CSHP)
RXPPS Indicates the packet rate in the receive direction.
RXBPS Indicates the bit rate in the transmit direction.
TXBPS Indicates the bit rate in the receive direction.

receive direction.

transmit direction.







Table 3-3 RMON performance events (Super EPLA group port: IFU2)
RXBPS Indicates the bit rate in the transmit direction.
TXBPS Indicates the bit rate in the receive direction.
Table 3-4 RMON performance events (Super EPLA group port: RTN 380/RTN 380H)
RXUNICAST Indicates the unicast packets received.
TXUNICAST Indicates the unicast packets transmitted.
TXBRDCAST Indicates the broadcast packets transmitted.
RXPAUSE Indicates the pause frames received.

NOTE
Only Ethernet ports support this performance event.
TXPAUSE Indicates the pause frames transmitted.

NOTE

RXBGOOD Indicates the bytes in received good packets.
TXBGOOD Indicates the bytes in transmitted good packets.
RXGOODFULLFRAMESPEED Indicates the bit rate of good full-frame packets

received.
TXGOODFULLFRAMESPEED Indicates the bit rate of good full-frame packets

transmitted.
RXFULLBGOOD Indicates the count of good full-frame bytes received.
TXFULLBGOOD Indicates the count of good full-frame bytes

transmitted.
TXMULCAST Indicates the multicast packets transmitted.
RX_DROP_RATIO Indicates the packet loss ratio in the receive direction.
TX_DROP_RATIO Indicates the packet loss ratio in the transmit direction.
RXBPS Indicates the bit rate in the receive direction.
TXBPS Indicates the bit rate in the transmit direction.
RXBBAD Indicates the bytes in received bad packets.

NOTE
RXOCTETS Indicates the bytes received.
RXBRDCAST Indicates the broadcast packets received.
RXMULCAST Indicates the multicast packets received.
ETHDROP Indicates the packet loss events.
ETHUNDER Indicates the undersized packets received.

NOTE
ETHOVER Indicates the oversized packets received.

NOTE

ETHFRG Indicates the fragments received.

NOTE
ETHJAB Indicates the oversized error packets received.

NOTE

receive direction.

transmit direction.






ETHFCS Indicates the FCS errored frames (MAC_FCS).
ETH_RX_THROUGHPUT_MA Indicates the maximum throughput on a port in the

X receive direction.
ETH_RX_THROUGHPUT_MIN Indicates the minimum throughput on a port in the

receive direction.
ETH_RX_THROUGHPUT_AVG Indicates the average throughput on a port in the

receive direction.
ETH_TX_THROUGHPUT_MA Indicates the maximum throughput on a port in the

X transmit direction.
ETH_TX_THROUGHPUT_MIN Indicates the minimum throughput on a port in the

transmit direction.
ETH_TX_THROUGHPUT_AVG Indicates the average throughput on a port in the

transmit direction.
TX_DROP_PKTS Indicates the packet loss count in the transmit

direction.
RX_DROP_PKTS Indicates the packet loss count in the receive direction.

TXPKT64 Indicates the count of transmitted 64-byte packets.






length of from 1519 bytes to the MTU-specified bytes.

of from 1519 bytes to the MTU-specified bytes.
RXPKT64 Indicates the count of received 64-byte packets.

of 65 to 127 bytes.




3.2 Troubleshooting (the Master Device Is an RTN IDU

900)
This section describes how to troubleshoot faults in the Super Dual Band solution.
Fault Point Analysis

Figure 3-1 shows possible fault points in the Super Dual Band solution. Table 3-5 describes
analysis on these possible fault points.

Figure 3-1 Possible fault points
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.
In this example, the RTN 950 and RTN 380 are used. Fault points of other devices are similar.
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/RTN 380H.
Table 3-5 Analysis on possible fault points

Fa Description Fault Type Related Alarm
ult
Po
int
1 Fault on a common-band Link fault l R_LOF

link l R_LOC
l MW_LOF
l MW_RDI
l MW_CFG_MISMATC
H
l XPIC_LOS
l MW_LIM

Fa Description Fault Type Related Alarm

ult
Po
int
Link degrade l MW_BER_EXC

l MW_BER_SD
2 Fault on an IF board Board fault l HARD_BAD

connecting to a common- l BD_STATUS
band link
l BUS_ERR
3 Fault on an E-band link Link fault l R_LOF

l R_LOC
l MW_LOF
l MW_RDI
l MW_FEC_EXC
Link degrade l MW_BER_EXC

l MW_BER_SD
4 Fault on E-band Equipment fault HARD_BAD

equipment
5 Fault on ports Port fault or fiber/cable l ETH_LOS

interconnecting an EM6D/ fault l ETH_LINK_DOWN
CSHNU/CSHP board and
an RTN 380/RTN 380H
6 Fault on a Super EPLA Board fault l HARD_BAD

processing board l BD_STATUS
3.3 Alarm Reference

This section describes the possible alarms for Super EPLA and how to handle them.
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
Parameter 1, Indicate the ID of the PLA group.

Parameter 2

Name Meaning
Parameter 3, Indicate the error type.

Parameter 4
Parameter 3 has a fixed value of 0x00. Parameter 4 takes one of the
following values:
l 0x00: The PLA group is not configured on the IF board of the peer NE.
l 0x01: Layer 2 header compression is enabled for only one NE.
l 0x02: Layer 3 header compression is enabled for only one NE.
l 0x03: The number of member links in the PLA group is different at
both ends.
l 0x04: Local member ports and peer member ports do not belong to the
same PLA group.
l 0x06: Configurations of enhanced compression for CS7 queues in PLA
groups at both ends of a microwave link are inconsistent.
l 0x07: Configurations of enhanced compression for CS6 queues in PLA
l 0x08: Configurations of enhanced compression for EF queues in PLA
l 0x09: Configurations of enhanced compression for AF4 queues in PLA
l 0x0A: Configurations of enhanced compression for AF3 queues in PLA
l 0x0B: Configurations of enhanced compression for AF2 queues in PLA
l 0x0C: Configurations of enhanced compression for AF1 queues in PLA
l 0x0D: Configurations of enhanced compression for BE queues in PLA
l 0x0E: The PLA capacities are inconsistent at the two ends of a
microwave link.
l 0x0F: The PLA scheduling types are inconsistent at the two ends of a
microwave link.
l 0x10: The PLA priority thresholds are inconsistent at the two ends of a
microwave link.
l 0x11: The priorities of PLA members are inconsistent at the two ends
of a microwave link.
l 0x12: The local-end PLA member port and the remote-end PLA
member port have different port rates.
l 0x13: The channel configurations of PLA members are inconsistent at
the two ends of a link.
l 0x14: The channel configurations of the master and slave devices in a
PLA group are inconsistent.

Impact on the System

The services carried by the radio link are unavailable.
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 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 5 Cause 5: Enhanced compression is enabled for only one NE.

1. Ensure that the enhanced compression status is consistent on both NEs. For details, see
Managing Radio Links.
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
The PLA in this section refers to EPLA and Super EPLA.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the ID of the PLA group.

The services carried by the PLA group are interrupted.
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.
Step 2 Clear the PLA_MEMBER_DOWN alarm.
----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

Minor QoS alarm
Parameters
Name Meaning
Parameter 1 and Indicate the ID of the Super EPLA group. For example, 0x00 0x08
Parameter 2 indicates that the protection group ID is 8. For details, see
Parameter Examples.
Parameter 3 to Indicate the NE ID. For example, 0x00 0x09 0xac 0x02 indicates
Parameter 6 that the NE ID is 9-44034. That is, parameters 3 and 4 indicate the
extended ID, and parameters 5 and 6 indicate the basic ID.
Parameter 7 and Indicate the slot ID of the board. For example, 0x00 0x01 indicates
Parameter 8 that the slot ID is 1.
Parameter 9 Indicates the slot ID of the subboard. The parameter takes a fixed
value of 0xff.
Parameter 10 and
Indicate the port ID. For example, 0x00 0x05 indicates port 5.
Parameter 11
Parameter 12 and
Indicate the path ID. For example, 0x00 0x01 indicates path 1.
Parameter 13

Name Meaning
Parameter 14 Indicate the fault cause.
l 0x00: indicates connectivity loss.
l 0x01: indicates a remote fault.

Available bandwidth of the Super EPLA group decreases. If a PLA_DOWN alarm is also
reported, services are interrupted.
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.
l Cause 5: The cascaded NE is faulty.
l Cause 6: The cascade port is faulty.
l Cause 7: Loss of connectivity occurs on a member link of the Super EPLA group.
l Cause 8: Remote defect indication exists on a member link of the Super EPLA group.
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.
Step 5 Cause 5: The cascaded NE is faulty.

1. Replace the cascaded NE and re-configure the Super EPLA group. Ensure that Super
EPLA group configurations are consistent at both ends.
Step 6 Cause 6: The cascade port is faulty.

1. If the cascade port is faulty, for example, the port is disabled, rectify the fault.
Step 7 Cause 7: Loss of connectivity occurs on a member link of the Super EPLA group.
1. Check for and clear the MW_LOF alarm on the local NE.
Step 8 Cause 8: Remote defect indication exists on a member link of the Super EPLA group.
1. Check for and clear the MW_RDI alarm on the local NE.
----End
Related Information
Figure 3-2 Parameter Example 1
l Parameters 1 and 2 (0x00 0x08) indicate that the protection group ID is 8.

l Parameters 3 to 6 (0x00 0x09 0xac 0x02) indicate that the NE ID is 9-44034. That is,
parameters 3 and 4 indicate the extended ID, and parameters 5 and 6 indicate the basic
ID.
l Parameters 7 and 8 (0x00 0x01) indicate that the slot ID is 1.
l Parameter 9 takes a fixed value of 0xff.
l Parameters 10 and 11 (0x00 0x05) indicate that the port ID is 5.
l Parameters 12 and 13 (0x00 0x01) indicate that the path ID is 1.
l Parameter 14 (0x00) indicates that the fault cause is loss of connectivity.
Figure 3-3 Parameter Example 2

l Parameters 1 and 2 (0x00 0x01) indicate that the protection group ID is 1.

l Parameters 3 to 6 (0x00 0x09 0xac 0xe2) indicate that the NE ID is 9-44258. That is,
parameters 3 and 4 indicate the extended ID, and parameters 5 and 6 indicate the basic
ID.
l Parameters 7 and 8 (0x00 0x04) indicate that the slot ID is 4.
l Parameter 9 takes a fixed value of 0xff.
l Parameters 10 and 11 (0x00 0x01) indicate that the port ID is 1.
3.3.4 PLA_PKT_ERR
Description
The PLA_PKT_ERR alarm indicates that packet reassembly fails in the receive direction.
Attribute
Major 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
Parameters 1 and 2 Indicate the ID of the PLA group.

Services in the PLA group are unavailable.
Possible Causes
Cause 1: The clock tracing relationship is incorrectly configured for the active and standby
NEs.
Cause 2: A member link in the PLA group is faulty.
Cause 3: The local or cascaded NE has a hardware fault.
Procedure
Step 1 Check whether the clock tracing relationship is correctly configured for the active and standby
NEs. If the clock tracing relationship is incorrect, configure the clock sources again. If the
clock tracing relationship is correct, go to the next step.

Step 2 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 3 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


RTN Super Dual Band Solution

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

RTN Super Dual Band Solution

Încărcat de

Drepturi de autor:

Formate disponibile

OptiX RTN Super Dual Band Solution

Super Dual Band User Manual

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential i

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential ii

2.5 Configuration Example (Master Device Is an RTN 380H).......................................................................................... 50

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential iii

About This Chapter

Super Dual Band is a large-bandwidth and long-distance microwave transmission solution

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 1

Figure 1-1 Super Dual Band solution

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 2

Transmission Medium Long Short

Bandwidth High Low High

Construction period Short Short Short

1.2 Typical Applications

1.2.1 Tail Node Application

RTN 905 1E/2E

Figure 1-2 Typical Super Dual Band networking

Full-Outdoor Super Dual Band Solution

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 3

Figure 1-3 Typical networking of a full-outdoor Super Dual Band solution

1.2.2 Aggregation Transmission Application

Figure 1-4 Typical aggregation transmission networking

1.2.3 Back-to-Back Application

Figure 1-5 Typical back-to-back networking

1.2.4 Large-Capacity Aggregation Upstream Application

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 4

Figure 1-6 Large-capacity convergence upstream networking

1.2.5 Optical Fiber Supplementing and Aggregation Application

Figure 1-7 Optical fiber supplementing and aggregation networking

1.2.6 Hybrid Application with Third-Party Equipment

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 5

Figure 1-8 Typical networking of hybrid application with third-party common-band

1.3 Feature Enhancement

1.3.1 Super Dual Band Relay

Figure 1-9 Super Dual Band Relay (two hops of relay)

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 6

Figure 1-10 Super Dual Band Relay (three hops of relay)

Figure 1-11 Super Dual Band Relay (multi-hop relay)

Super Dual Band Relay has the following features:

1.3.2 Dual-Band Antenna

Dual-Band antennas supports the simultaneous transmission of signals carried by two

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 7

Figure 1-12 Dual-band antenna of Super Dual Band

l Reduced tower space and wind load, reduced infrastructure investments

1.4.1 Principles (Master Device Is an RTN 905 1E/2E)

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 8

1.4.2 Principles (Master Device Is an RTN 950/950A)

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 9

1.4.3 Principles (Master Device Is an RTN 980)

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 10

1.4.4 Principles (Master Device Is an RTN 380H)

Full-Outdoor Super Dual Band Solution

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 11

Super Dual Band Solution of Hybrid Application with Third-Party Common-

1.4.5 Super EPLA

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 12

Figure 1-18 Super Dual Band principles

In the transmit direction:

Issue Draft 01 (2017-09-15) Huawei Proprietary and Confidential 13

Figure 1-19 Before switching