Huawei OLT General Config

SingleFAN Solution
FTTO Configuration Guide (Large-

sized Enterprise Access)
Issue 01
Date 2016-12-16
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2016. 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 01 (2016-12-16) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
SingleFAN Solution
FTTO Configuration Guide (Large-sized Enterprise Access) About This Document
About This Document
Purpose
This document mainly describes the networking, data planning, and configuration of the
FTTO solution (large-sized enterprise access).
Intended Audience
The intended audience of this product description are as follows:
l Network planning engineers
l Installation and commissioning engineers
l Field maintenance engineers
l Network monitoring engineers
l System maintenance engineers
l Data configuration engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
DANGER
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.
WARNING

avoided, may result in minor or moderate injury.
Issue 01 (2016-12-16) Huawei Proprietary and Confidential ii

SingleFAN Solution
FTTO Configuration Guide (Large-sized Enterprise Access) About This Document
Symbol Description

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.
NOTE Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
Change History
Updates between document versions are cumulative. Therefore, the latest issue contains all
updates made in previous issues.
Updates in Issue 01 (2016-12-16)

This is the first release.
Issue 01 (2016-12-16) Huawei Proprietary and Confidential iii

SingleFAN Solution
FTTO Configuration Guide (Large-sized Enterprise Access) Contents
Contents
About This Document.....................................................................................................................ii

1 FTTO Configuration (Large-sized Enterprise Access)........................................................... 1
1.1 FTTO (Large-sized Enterprise Access) Configuration Summary.................................................................................. 3
1.2 Overview of Enterprise Access Service......................................................................................................................... 3
1.3 Principle of Planning Data for Enterprise Access Service............................................................................................. 6
1.3.1 Principle of Equipment Management Data Plan......................................................................................................... 6
1.3.2 Principle of VLAN Data Plan......................................................................................................................................7
1.3.3 Principle of QoS Data Plan..........................................................................................................................................9
1.3.4 Principle of Protocol Transparent Transmission Data Plan.......................................................................................12
1.3.5 Principle of Security Data Plan................................................................................................................................. 13
1.3.6 Principle of Reliability Data Plan.............................................................................................................................. 15
1.4 Configuring Layer 2 Interoperation Service Between Enterprise Branches (GPON)..................................................17
1.4.1 Service Requirement and Application Scenario........................................................................................................ 17
1.4.2 Configuration Process................................................................................................................................................18
1.4.3 Adding ONUs to OLT................................................................................................................................................19
1.4.4 Configuring Management Service Ports on OLT and ONUs.................................................................................... 23
1.4.5 Configuring Layer 2 Interoperation Service Ports on OLT....................................................................................... 24
1.4.6 Configuring Ethernet Access Service Ports on ONUs.............................................................................................. 26
1.4.7 Configuring Congestion Control and Security Policies............................................................................................ 27
1.4.8 Configuring E2E Reliability...................................................................................................................................... 29
1.4.9 Verifying Services......................................................................................................................................................33
1.5 Configuring Enterprise DDN Private Line Access Service (GPON)........................................................................... 35
1.5.5 Configuring TDM Connections.................................................................................................................................40
1.5.6 Configuring Clock Synchronization.......................................................................................................................... 41
1.6 Configuring Enterprise IP PBX Private Line Access Service (GPON)....................................................................... 46
Issue 01 (2016-12-16) Huawei Proprietary and Confidential iv

SingleFAN Solution
FTTO Configuration Guide (Large-sized Enterprise Access) Contents

1.6.5 Configuring OLT QinQ Service Ports....................................................................................................................... 52
1.6.6 Configuring Ethernet Access Service Ports on ONUs.............................................................................................. 53
1.7 Configuring Enterprise PRA PBX Private Line Access Service (GPON)................................................................... 60
1.7.5 Configuring Service Ports for Voice Transparent Transmission............................................................................... 66
1.7.6 Configuring VoIP PRA Access..................................................................................................................................67
1.8 Configuring Enterprise E1 Unified Access Service (GPON).......................................................................................76
1.8.5 Configuring SAToP Connections and Service Ports..................................................................................................81
1.8.6 Configuring ONU SAToP Connections..................................................................................................................... 83
1.8.7 Configuring Clock Synchronization.......................................................................................................................... 85
1.8.9 Configuring Network Protectio................................................................................................................................. 88
1.8.10 Verifying Services....................................................................................................................................................90
1.9 Configuring Enterprise E1 Unified Access Service (OLT Cascading, GPON)............................................................93
1.9.3 Configure OLT_A cascading with OLT_B................................................................................................................95
1.9.4 Configuring SAToP Connections between OLT_A and ONU...................................................................................96
1.9.5 Adding ONUs to OLT_B...........................................................................................................................................97
1.9.6 Configuring Management and Service Channel on OLT_B and ONU................................................................... 100
1.9.7 Configuring ONU SAToP Connections................................................................................................................... 101
1.9.8 Configuring Clock Synchronization........................................................................................................................ 103
1.9.9 Verifying Services....................................................................................................................................................105
Issue 01 (2016-12-16) Huawei Proprietary and Confidential v

SingleFAN Solution
FTTO Configuration Guide (Large-sized Enterprise Access) 1 FTTO Configuration (Large-sized Enterprise Access)
1 FTTO Configuration (Large-sized

Enterprise Access)
About This Chapter
Large-sized enterprises generally adopt private line access service. Compared with individual
services, this service features various access methods, large number of access users, high
security requirement, and cross-region deployment.
NOTE
In this document, the FTTO large-sized enterprise private line access service is written as enterprise access
service for short.
1.1 FTTO (Large-sized Enterprise Access) Configuration Summary

FTTO (Large-sized Enterprise Access) Configuration Guide is written based on solution
scenarios, covering the entire E2E service configuration process for the OLT and ONU. This
guide provides guidance for service configuration in FTTO (Large-sized Enterprise Access)
involving the OLT and ONUs of different models. The OLT is used in all service scenarios for
FTTO (Large-sized Enterprise Access). Therefore, OLT users can select the concerned
scenarios. Different ONUs may be used in service scenarios for FTTO (Large-sized Enterprise
Access). Therefore, ONU users can see the following table to select the concerned scenarios.
1.2 Overview of Enterprise Access Service
This topic describes the basic knowledge about the enterprise access service. Before
configuring the enterprise access service, you are advised to learn about the basic knowledge.
1.3 Principle of Planning Data for Enterprise Access Service
This topic plans data for the enterprise access service from multiple dimensions. The data plan
guides configuration and optimization of the enterprise service in different scenarios.
1.4 Configuring Layer 2 Interoperation Service Between Enterprise Branches (GPON)
Different branches of an enterprise can achieve Layer 2 interoperation through ONUs. Then,
different branches can transmit service traffic to each other just like in the same LAN, which
can improve coordination work efficiency.
1.5 Configuring Enterprise DDN Private Line Access Service (GPON)
Enterprise DDN private line service is converted to E1 signals. ONUs access the E1 signals
and transmit them in Native TDM mode.
1.6 Configuring Enterprise IP PBX Private Line Access Service (GPON)
Issue 01 (2016-12-16) Huawei Proprietary and Confidential 1

SingleFAN Solution
ONUs provide GE/FE ports to access IP private branch exchange (PBX) services of an
enterprise and transmit them to an OLT. Then, the OLT forwards the service data upstream to
the packet switched network (PSN). This achieves unified carrying of voice, data, and video
services.
1.7 Configuring Enterprise PRA PBX Private Line Access Service (GPON)
ONUs provide PRA E1 ports to access PRA private branch exchange (PBX) services of an
the packet switched network (PSN). This achieves voice-to-IP conversion, simplifying the
network architecture.
1.8 Configuring Enterprise E1 Unified Access Service (GPON)
ONUs transmit E1 signals of enterprises to OLTs in SAToP mode and OLTs are
interconnected with transmission equipment through E1 ports. In this manner, traditional
circuit switching services can be carried over GPON networks.
1.9 Configuring Enterprise E1 Unified Access Service (OLT Cascading, GPON)
ONUs access enterprise TDM service in E1 access mode, and transmits the data to the SDH
network in OLT cascading mode over the GPON network which supports long-distance
transmission and high bandwidth. In this way, uniform deployment of E1 service is achieved.

SingleFAN Solution
1.1 FTTO (Large-sized Enterprise Access) Configuration

Summary
FTTO (Large-sized Enterprise Access) Configuration Guide is written based on solution
scenarios, covering the entire E2E service configuration process for the OLT and ONU. This
guide provides guidance for service configuration in FTTO (Large-sized Enterprise Access)
involving the OLT and ONUs of different models. The OLT is used in all service scenarios for
FTTO (Large-sized Enterprise Access). Therefore, OLT users can select the concerned
scenarios. Different ONUs may be used in service scenarios for FTTO (Large-sized Enterprise
Access). Therefore, ONU users can see the following table to select the concerned scenarios.
All OLT and ONU commands described in this document use V800R016C00 as examples.
Commands may be slightly different in versions. For detailed commands, see the OLT and
ONU Command Reference of the corresponding version.
Service Scenario ONU Supported Service

Interface of
ONU
Layer 2 Interoperation Service Between MA5612, MA5694, LAN

Enterprise Branches MA5698, MA5898
Enterprise DDN Private Line Access MA5612, MA5698, E1

Service MA5898
Enterprise IP PBX Private Line Access MA5612, MA5694, LAN

Service MA5698, MA5898
Enterprise PRA PBX Private Line Access MA5612 PRA E1

Service
Enterprise E1 Unified Access Service MA5612 E1
Enterprise E1 Unified Access Service MA5612 E1

(OLT Cascading)
1.2 Overview of Enterprise Access Service

This topic describes the basic knowledge about the enterprise access service. Before
configuring the enterprise access service, you are advised to learn about the basic knowledge.

SingleFAN Solution
Network Diagram of Enterprise Access Service
PRA PBX
ONU
OLT SDH
Switch
Switch E1/STM-1
IP PBX Splitter GE
/10
Digital Terminal DDN Node Protocol GE
Machine Converter IP network
DDN
E1 NGN/IMS
V.24/V.35 ONU
Enterprise Side Access Side Network Side
User Side
Concept Description
IP PBX IP private branch exchange (PBX) is an IP-based enterprise telephone

exchange system. IP PBX uses ICT technology to seamlessly
integrate voice communication into the data communication network
of an enterprise, simply network architecture, and provide better voice
communication between branches of the enterprise.
PRA PBX PRA PBX, that is, TDM PBX, also called a switch, is a telephone
exchange used within an enterprise. With the PRA PBX, staff in the
enterprise can use internal telephones to make free calls by dialing
short numbers. Outgoing calls are made through a unified trunk. PRA
PBX can lower costs and improve work efficiency for the enterprise.
DDN Digital data network (DDN) is a network that uses digital channels to
transmit data signals. It provides permanent and semi-permanent
connections for users. Compared with traditional analog channels,
DDN channels have a higher transmission quality, transmission rate,
and bandwidth use rate. DDN is widely used in financial departments,
governments, and enterprise groups that require high real-time data
switching
DDN node A DDN network consists of backbone node machines and access node
machine machines.
A backbone node machine (2M node) implements network service
conversion. It provides interfaces and cross-connections for 2 Mbit/s
(E1) digital channels, multiplexes and cross-connects Nx64 kbit/s
circuit signals, and supports cables reconnection for frame relay
services.
An access node machine accesses various services for DDN. It
provides interfaces for Nx64 kbit/s and 2048 kbit/s digital channels,
multiplexes Nx64 kbit/s (N=1–31) signals, and accesses voice and
fax users.

SingleFAN Solution
Concept Description
Protocol converter Protocol converter is a device used to convert standard or proprietary

protocol of one device to the protocol suitable for the other device or
tools to achieve the interoperability. In this document, it implements
protocol conversion between V.24/V.35 and E1.
Access Side
Concept Description
PON A passive optical network (PON) uses a point-to-multipoint (P2MP)

network architecture. A PON network consists of three parts: optical
line terminal (OLT), optical distribution network (ODN), and optical
network units (ONUs). A PON network uses optical fibers for data
transmission, supports more users with less optical fiber resources,
and provides a higher access rate.
Mainstream PON technologies include broadband passive optical
network (BPON), Ethernet passive optical network (EPON), and
gigabit passive optical network (GPON).
ODN The ODN is composed of passive optical components, such as optical

fibers and one or more passive optical splitters. The ODN provides
highly reliable optical channels between the OLT and ONUs.
OLT The OLT is an aggregation device located at the central office (CO),
which terminates PON protocols. OLTs in this document are
MA5600T/MA5603T/MA5608T.
ONU ONUs are located on the user side, providing various types of ports
for connecting to user terminals. The ONUs communicate with the
OLT through a passive ODN.
Network Side
Concept Description
SDH Synchronous digital hierarchy (SDH) is a transmission scheme that

follows ITU-T G.707, G.708, and G.709. It defines the transmission
features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part
of ISDN and B-ISDN. It interleaves the bytes of low-speed signals to
multiplex the signals to high-speed counterparts, and the line coding
of scrambling is used only for signals. SDH is suitable for the fiber
communications system with high speed and a large capacity since it
uses synchronous multiplexing and flexible mapping structure.

SingleFAN Solution
Concept Description
NGN/IMS A next generation network (NGN) is a network that uses softswitches

as its core and uses open and standardized architectures to provide
abundant services such as VoIP, video, and data.
The IP multimedia subsystem (IMS) uses SIP signaling as its call
control signaling to provide services such as VoIP, data, and
multimedia services.
NOTE
NGN/IMS in this document refers to softswitches that support H.248 and SIP.
1.3 Principle of Planning Data for Enterprise Access

Service
This topic plans data for the enterprise access service from multiple dimensions. The data plan
guides configuration and optimization of the enterprise service in different scenarios.
1.3.1 Principle of Equipment Management Data Plan

Data planning for equipment management covers planning of management VLANs and IP
addresses.
Management VLAN Planning

l The OLT and ONUs use the same management VLAN.
l The OLT and ONUs use a single S-VLAN as the equipment management VLAN.
IP Address Planning
Scenario IP Address Planning
Equipment A management IP address is allocated to each OLT/ONU.

management Management IP addresses of ONUs connected to the same OLT are
usually in the same network segment. Private IP addresses planned
by the carrier are used for the purpose of security.
Layer 2 Enterprise service flows are forwarded at Layer 2 within the FTTx
interoperation network. Therefore, no IP addresses need to be planned on the OLT
between different and ONUs for enterprise users.
enterprise branches
Enterprises DDN No IP addresses need to be planned because ONUs access the

private line access private line service through E1.
Enterprise IP PBX No IP addresses need to be planned because the OLT and ONUs
access provide Layer 2 transparent channels.

SingleFAN Solution
Scenario IP Address Planning
Enterprise PRA ONUs convert PRA voice signals to H.248 or SIP voice signals.
PBX access Therefore, the following IP addresses need to be planned:
l Media IP address
l Signaling IP address
l Default gateway IP address
Enterprise E1/T1 IP addresses are planned as follows:

unified access l On OLTs, source IP addresses of SAToP connections must be
Enterprise E1/T1 planned for E1 boards.
unified access (OLT l On ONUs, source IP addresses of SAToP connections must be
Cascading) planned for E1 boards.
These IP addresses are valid only between OLTs and ONUs and
therefore can be planned as private IP addresses.
1.3.2 Principle of VLAN Data Plan

VLAN planning for the enterprise access service covers planning of VLANs and VLAN
translation policies in different networking scenarios.
VLAN and VLAN Translation Policy

Scenario VLAN Planning VLAN Translation
ONU OLT
Layer 2 l ONUs and the OLT l The same C- The OLT allocates
interoperation must use single VLAN VLAN is a global S-VLAN
between tags. planned for to each enterprise:
different l Service flows of the different C-VLAN<->S-
enterprise same enterprise have the branches of an VLAN.
branches same VLAN on the enterprise. NOTICE
OLT. l Different C- Packets must be
forwarded based on
l Service flows of the VLANs are
VLAN+MAC at
same enterprise can planned for Layer 2 instead of
have different VLANs different S-VLAN+C-
on ONUs but the enterprises. VLAN.
VLANs must be
translated to the same
VLAN on the OLT.
Enterprises Use a reserved C-VLAN N/A N/A

DDN private (starts from 4000).
line access NOTICE
A reserved C-VLAN cannot
be used for Ethernet services
on ONUs.

SingleFAN Solution
ONU OLT
Enterprise IP Single VLAN tag: ONUs 1. Different user The OLT

PBX access and the OLT use single VLANs are transparently
VLAN tags. Service planned for transmits the
packets are forwarded different packets with C-
based on single VLAN tags services VLANs from
after being transmitted from (service ONUs.
the OLT upstream to the packets with
metro network. In this way, different
a large number of VLANs destination
for the metro network will addresses or
be occupied if there are paths) of the IP
many OLTs. PBX.
2. User VLANs
of packets sent
from the IP
PBX are
translated to a
specified C-
VLAN based
on service
types.
(Recommended) Double 1. Different user The OLT adds an

VLAN tags: Each OLT uses VLANs are S-VLAN tag: C-
double VLAN tags, an planned for VLAN<->S-
outer VLAN tag (S-VLAN) different VLAN+C-VLAN.
and inner VLAN tag (C- services
VLAN). S–VLANs are the (service
same but C–VLANs are packets with
different. In this way, the different
number of VLANs required destination
for the metro network is addresses or
significantly reduced. paths) of the IP
PBX.
2. User VLANs
of packets sent
from the IP
PBX are
translated to a
specified C-
VLAN based
on service
types.

SingleFAN Solution
ONU OLT
Enterprise PRA (Recommended) Single ONUs access the The OLT

PBX access VLAN tag PRA PBX through transparently
E1, provide the transmits packets.
VoIP PRA service,
and use the same
C-VLAN.
Double VLAN tags ONUs access the The OLT adds an

PRA PBX through S-VLAN tag: C-
E1, provide the VLAN<->S-
VoIP PRA service, VLAN+C-VLAN.
and use the same
C-VLAN.
Enterprise Plan a global VLAN on the N/A N/A

E1/T1 unified OLT and ONUs, which
access cannot conflict with other
service VLANs.
Enterprise
E1/T1 unified
access (OLT
Cascading)
1.3.3 Principle of QoS Data Plan

QoS planning for the enterprise access service is end-to-end. QoS policies include traffic
classification, marking and scheduling, traffic monitoring, and DBA policies. QoS policies for
different scenarios are different. This topic provides QoS policies in the following scenarios.
Layer 2 interoperation Between Different Enterprise Branches

Parameter Value
Traffic 802.1p priority 4

classification,
marking, and Queue scheduling PQ
scheduling policies mode
OLT queue ID 4
(eight queues)
Traffic OLT T-CONT (only for An independent T-CONT is used.

monitorin GPON)
g and
DBA
policies

SingleFAN Solution
Parameter Value
DBA Type Type 3 ("Assured bandwidth+maximum

bandwidth" DBA profile. This type of DBA
not only ensures a fixed bandwidth for users
but also enables users to preempt a certain
amount of bandwidth, but the total bandwidth
cannot exceed the maximum bandwidth.)
DBA bandwidth Plan the bandwidth according to users'

requirements.
Downstream traffic Configure the profile according to users'

profile bandwidth requirements.
ONU Upstream port rate Rates of upstream ports are not limited.
limit
Downstream port Rates of downstream ports are not limited.

rate limit
Enterprise DDN Private Line Access

In this scenario, ONUs access services from the DDN through E1 lines. Therefore, the QoS
policies are mainly planned for traffic on PON lines.
Parameter Value Remarks
T-CONT It is recommended that the It is recommended that all E1

number of T-CONTs do not lines of the same ONU use the
exceed 3. The T-CONT ID ranges same T-CONT.
from 1 to 3.
DBA type Fixed bandwidth and minimum The DBA must be configured
delay properly to achieve low delay,
low jitter, and zero packet loss so
that the quality of the DDN
private line service can be
ensured.
DBA bandwidth Nx7232 kbit/s is recommended. It is recommended that the T-

(N is the number of E1 lines.) CONT ID be 1, 2, or 3 and all E1
lines of the same ONU use the
same T-CONT. This setting can
leverage bandwidth resources.
Each E1 line requires only 5440
kbit/s.

SingleFAN Solution
Enterprise PRA PBX Access

Parameter Value
Traffic 802.1p priority 5

classification,
marking, and Queue scheduling PQ
scheduling policies mode
OLT queue ID 5
(eight queues)
Traffic OLT T-CONT (only for All services share a T-CONT.

monitorin GPON)
g and
DBA DBA type Type 3 ("Assured bandwidth+maximum
policies bandwidth" DBA profile. This type of DBA
not only ensures a fixed bandwidth for users
but also enables users to preempt a certain
amount of bandwidth, but the total bandwidth
cannot exceed the maximum bandwidth.)
DBA bandwidth DBA bandwidth is configured based on the

bandwidth package selected by the user.
The assured bandwidth is the maximum
bandwidth required for transmitting
management packets and VoIP service packets.
The maximum bandwidth is equal to or higher
than the maximum bandwidth applied by the
user.
Downstream traffic Downstream traffic rate is not limited.

profile
ONU Upstream port rate Set this parameter based on requirements.

limit
Downstream port Set this parameter based on requirements.

rate limit
Enterprise IP PBX Access

The QoS policies for this scenario are the same as those for the Layer 2 interoperation
Between Different Enterprise Branches scenario.
Enterprise E1/T1 unified access

In this scenario, ONUs access services through E1/T1 lines. Therefore, the QoS policies are
mainly planned for traffic on PON lines.

SingleFAN Solution
Parameter Value Remarks
T-CONT It is recommended that the It is recommended that all E1

number of T-CONTs do not lines of the same ONU use the
exceed 3. The T-CONT ID ranges same T-CONT.
from 1 to 3.
DBA type Fixed bandwidth and minimum The DBA must be configured
delay properly to achieve low delay,
low jitter, and zero packet loss so
that the quality of the T1 base
station access service can be
ensured.
DBA bandwidth l E1 access: Nx8 Mbit/s is -

recommended. (N is the
number of E1 lines.)
l T1 access: Nx6 Mbit/s is
recommended. (N is the
number of E1 lines.)
Enterprise E1/T1 unified access (OLT Cascading)

The QoS policies for this scenario are the same as those for the Enterprise E1/T1 unified
access scenario.
1.3.4 Principle of Protocol Transparent Transmission Data Plan

The enterprise access service involves transparent transmission of protocol packets. Different
equipment configurations are required for transparently transmitting different protocol
packets.
Configurations for Protocol Transparent Transmission

Protocol Protocol Description Configuration (remarks 1)
Type
BPDU STP, MSTP, RSTP, IS- The function of transparently transmitting

IS BPDU packets must be enabled.
Configuration example:
huawei(config)#vlan service-profile
profile-id 1
huawei(config-vlan-srvprof-1)#bpdu
tunnel enable
ETH OAM IEEE 802.1ag No configuration is required because packets

are transparently transmitted by hardware.
Broadcast ARP No configuration is required because packets

are transparently transmitted by hardware.

SingleFAN Solution
Protocol Protocol Description Configuration (remarks 1)

Type
Layer 2/Layer NTP, BGP, LDP, RSVP, No configuration is required because packets
3 protocol IGMP, PIM are transparently transmitted by hardware.
OSPF The function of transparently transmitting

OSPF packets must be enabled.
profile-id 1
huawei(config-vlan-srvprof-1)#ospf
tunnel enable
RIP The function of transparently transmitting RIP

packets must be enabled.
profile-id 1
huawei(config-vlan-srvprof-1)#rip
tunnel enable
VTP/CDP VTP/CDP protocol is a The function of transparently transmitting

proprietary protocol of VTP/CDP packets must be enabled.
other vendors. It is used Configuration example:
to discover neighbors huawei(config)#vlan service-profile
and establish neighbor profile-id 1
huawei(config-vlan-srvprof-1)#vtp-cdp
relationship. tunnel enable
Unknown Planned by carriers for The function of transparently transmitting

multicast special purposes unknown multicast packets must be enabled.
huawei(config)#multicast-unknown policy
service-port 1 transparent
Remarks 1: The configurations take effect only after the configured VLAN service profile is
bound to a VLAN. Command: vlan bind service-profile vlan-id profile-id
1.3.5 Principle of Security Data Plan

Security planning covers planning of system security, user security, and service security data.
An appropriate security plan ensures normal running of services.
NOTE
l The device provides complete security measures, but not all security measures need to be deployed. Only
the security measures that meet the following requirements need to be deployed:
l The security measures can be used on the live network.
l The security measures are easy to deploy.
l The security measures are effective.
l Different ONUs support different security features. Select the security feature recommended in this topic
according to actual ONU capabilities.

SingleFAN Solution
System Security
Security Solution Description and Usage
Vulnerability Suggestion
DoS attack Enable the anti-DoS-attack After the anti-DoS-attack function is

function for OLT and enabled, control packets are
MDU. monitored and those exceeding the
number threshold are discarded.
Use this solution for new site
deployment.
IP attack Enable the anti-IP-attack After the anti-IP-attack function is

function for OLT and enabled, a device discards the IP
MDU. packets received from the user side
whose destination IP address is the
IP address of the device, and
therefore the system is protected.
deployment.
User Security
MAC spoofing Enable the anti-MAC- After anti-MAC-duplicate is

duplicate function for OLT enabled, the system records the first
and MDU. MAC address learned from the port
and binds the MAC address to the
port and VLAN. If receiving packets
sent from the host that has the same
MAC address with the port, the
system discards the packets directly.
In this case, it can prevent users from
forging MAC addresses to perform
malicious attacks.
deployment.
MAC attack Enable the anti-MAC After anti-MAC spoofing is enabled,

spoofing function for OLT the system can prevent users from
and MDU. forging IP addresses to perform
malicious attacks.
deployment.

SingleFAN Solution

IP spoofing Enable the anti-IP spoofing After anti-IP spoofing is enabled, the
function for MDU. system can prevent users from
forging IP addresses to perform
malicious attacks.
deployment.
1.3.6 Principle of Reliability Data Plan

Reliability planning covers planning of equipment reliability and upstream/downstream
networking protection. Reliability planning helps to achieve high reliability of private line
services.
Equipment Reliability
Protection Scheme Description Suggestion
Main control board The system uses two main control Mandatory
1+1 protection boards of the same model and
version. The two main control
boards work in the active/standby
mode by default. When the active
main control board fails, the system
switches to the standby main control
board to prevent service
interruption.
Power board 1+1 A subrack is configured with two Mandatory

protection power boards of the same model
and version, which back up each
other. When one of the power
boards fails, the other power board
can still provide power supply to the
device and so the system can still
work properly.
Upstream board 1+1 The system uses two upstream This protection scheme is
protection interface boards of the same model recommended when the
and version. Each GIU board GIU board is used to
provides one upstream port and two transmit traffic upstream.
upstream ports are bound together
using Link Aggregation Control
Protocol (LACP). When the active
upstream port fails, traffic will be
transmitted upstream through the
standby upstream port.

SingleFAN Solution
Upstream Networking Protection

Link aggregation Multiple Ethernet ports are bound This protection scheme is
group together as an aggregation group to mandatory when the GIU
increase the bandwidth and balance board is used to transmit
the inbound and outbound load of traffic upstream.
each member port. In addition, the
ports in an aggregation group back
up each other, which enhances the
reliability of links.
Protection group A protection group of upstream When the main control

(Ethernet/STM-1) ports contains a working port and a board is used to transmit
protection port. In normal state, the traffic upstream, this
working port carries services and protection scheme is
the protection port does not. When mandatory.
the link at the working port is faulty, This protection scheme is
the system automatically switches recommended when traffic
services from the working port to is transmitted upstream
the protection port to ensure normal through STM-1 ports.
service transmission and protect the
uplink.
NOTE
Link aggregation group and Ethernet protection group usually are not configured at the same time. You are
advised to configure only one of the two protection schemes.
Downstream Networking Protection

xPON Type B single Two PON ports on the same OLT It provides port-level
homing back up each other. When one of the protection and has a low
PON ports fails, the system cost. The inter-board
automatically switches to the other protection mode is
PON port. This protection scheme recommended.
provides port-level protection with
low costs. It protects services
against fiber failure at the working
port.
GPON Type C single Two PON ports on the same OLT, It provides link-level
homing two PON ports on an ONU, two protection.
backbone optical fibers, two optical
splitters, and two tributary optical
fibers are configured to provide
link-level protection.

SingleFAN Solution
GPON Type C dual Two PON ports on different OLTs, It provides full backup
homing two PON ports on an ONU, two protection, which is the
backbone optical fibers, two optical highest level of protection,
splitters, and two tributary optical at the same time, it has the
fibers are configured to implement highest cost.
this protection. The difference This protection scheme
between this protection scheme and can be configured for only
the GPON Type C single homing the Ethernet QinQ private
protection scheme is that the ONU line service. It does not
needs to be dual homed to two OLTs support TDM services,
in this protection scheme. This full- including Native TDM and
backup protection scheme provides SAToP.
the highest-level protection for links
and has the highest costs.
NOTE
The Type B single homing protection scheme, Type C single homing scheme, and Type C dual homing
protection scheme are mutually exclusive. Therefore, only one of these protection schemes can be configured
for an ONU.
1.4 Configuring Layer 2 Interoperation Service Between

Enterprise Branches (GPON)
Different branches of an enterprise can achieve Layer 2 interoperation through ONUs. Then,
different branches can transmit service traffic to each other just like in the same LAN, which
can improve coordination work efficiency.
1.4.1 Service Requirement and Application Scenario
Service Requirement
An enterprise that has multiple branches requires intercommunication between different
branches or between its headquarter and branches. Virtual private network (VPN) can achieve
secure interconnection but requires additional devices and complex management. It requires
high costs even if a leased VPN is used. In addition, the bandwidth provided by a VPN is
limited due to restricted VPN access modes and the bandwidth control is inflexible.
To address the preceding problems, the Layer 2 interoperation technology using fiber access
is put forward and becomes the main trend.
Application Scenario
As shown in Figure 1-1, ONUs are deployed in branches of an enterprise. The ONUs access
and converge Ethernet services of the enterprise through FE/GE ports and transmit the
services to the OLT. The OLT implements Layer 2 interoperation between different branches
of the enterprise.

SingleFAN Solution
Figure 1-1 Network diagram for Layer 2 interoperation between enterprise branches
IP/MPLS
ONU 1 ONU 2
GE FE FE
Headquarter Branch A Branch B

Service flows between
enterprise branches
Note: Because the bandwidth of upstream and downstream PON ports is fixed, the number of
enterprises connected to an OLT is limited when the enterprises require symmetric bandwidth.
When an enterprise requires 100 Mbit/s symmetric bandwidth:
1. The number of enterprises or branches connected to a PON port should not exceed eight.
2. The number of enterprises or branches connected to a PON board should not exceed 64.
3. The number of enterprises connected to an OLT cannot exceed 200 (20G/100M) if the
upstream bandwidth is 2x10GE. (The number of enterprises connected to an OLT is
mainly restricted by the upstream bandwidth.)
1.4.2 Configuration Process

The following figure shows the configuration process for Layer 2 interoperation between
branches of an enterprise.

SingleFAN Solution
Start
Adding ONUs to OLT
Configuring Management
Service Ports on OLT
and ONUs OLT Side
Configuring Layer 2
Interoperation Service
Service Ports
Configuring Congestion
Control and Security
Policies
Configuring E2E
Reliability
Configuring Ethernet
Access Service Ports ONU Side
Verifying Layer 2
Interoperation Service
End
NOTE
An OLT can connect to multiple ONUs (for enterprise branches). Configurations for different ONUs are
similar. Therefore, this document uses two ONUs (ONU1 and ONU2) as example to describe how to
configure Layer 2 interoperation.
1.4.3 Adding ONUs to OLT

This topic describes how to add ONUs to the OLT. ONUs can be configured only after they
are added to the OLT successfully.

SingleFAN Solution
Context
l When adding ONUs, you need to bind related profiles to the ONUs, including the DBA
profile, line profile, and alarm profile. For the functions of each profile and how to
configure profiles, see Table 1-1.
Table 1-1 ONU profile

Profile Function Command
Type
DBA Describes GPON traffic Query: display dba-profile

profile parameters. A T-CONT is Add: dba-profile add
bound to a DBA profile for
dynamic bandwidth allocation,
improving upstream bandwidth
utilization.
Line Describes the binding Query: display ont-lineprofile

profile relationship between T-CONTs Add: ont-lineprofile add
and DBA profiles, QoS mode
of service flows, and mapping
between GEM ports and
services on ONUs.
Alarm Provides a series of alarm Query: display gpon alarm-profile

profile threshold parameters that are Add: gpon alarm-profile add
used for performance
measurement and monitoring
of activated ONU lines.
l An ONU can be added in two modes. Select either mode as required.

Mode Application Scenario Command
Offline The password or serial number Run the ont add command to add the
addition of an ONU has been obtained. ONU.
Online The password and serial Run the port ont-auto-find command
confirmat number of an ONU are in the GPON mode to enable the
ion unknown. automatic discovery function for the
GPON port and run the ont confirm
command to add the ONU.

SingleFAN Solution
Data Planning
Table 1-2 Key data plan
Configuration Data
Item
DBA profile Profile ID: 20

Profile type: Type 3
Assured bandwidth: 100 Mbit/s
Maximum bandwidth: 120 Mbit/s
Line profile Profile ID: 10

T-CONT ID: 4
GEM port ID for management service: 11
GEM port ID for Layer 2 interoperation service: 12
Networking data For example, add two ONUs (ONU 1 and ONU 2) for carrying services
of different branches.
l ONU 1 is connected to PON port 0/3/1.
l ONU 2 is connected to PON port 0/4/1.
Procedure
Step 1 Configure GPON ONU profiles.
1. Configure a DBA profile.
huawei(config)#dba-profile add profile-id 20 type3 assure 102400 max 122880
2. Configure an ONU line profile.

a. Create GPON ONU line profile 10.
huawei(config)#ont-lineprofile gpon profile-id 10
NOTE
Create a line profile according to the data plan. The ID of the line profile to be created cannot
conflict with existing profile IDs in the system. In this example, the ID of the line profile is 10.
b. In the line profile configuration mode, bind T-CONT 4 to DBA profile 20.
huawei(config-gpon-lineprofile-10)#tcont 4 dba-profile-id 20
c. In the line profile configuration mode, bind GEM ports to T-CONTs.

n Add GEM port 11 for carrying the management service flow.
n Add GEM port 12 for carrying the Layer 2 interoperation service flow.
Both GEM port 11 and GEM port 12 are bound to T-CONT 4. During
configuration, set QoS policies for each service flow. For details on QoS data
planning, see 1.3.3 Principle of QoS Data Plan.
huawei(config-gpon-lineprofile-10)#gem add 11 eth tcont 4 cascade on
huawei(config-gpon-lineprofile-10)#gem add 12 eth tcont 4 cascade on
d. Configure mapping between GEM ports and ONU-side services.

SingleFAN Solution
Set the mapping mode to VLAN mode (the default mode). Map the management
service flow (C-VLAN 8) to GEM port 11, and map Layer 2 interoperation service
flow (C-VLAN 300) to GEM port 12.
huawei(config-gpon-lineprofile-10)#gem mapping 11 0 vlan 8
e. After the configuration is completed, run the commit command to make the
configured parameters take effect.
huawei(config-gpon-lineprofile-10)#commit
huawei(config-gpon-lineprofile-10)#quit
3. (Optional) Configure an alarm profile.

– The default GPON alarm profile ID is 1. The value of each alarm threshold is 0
which indicates that alarms are not reported.
– In this example, the default alarm profile is used and no configuration is required.
Step 2 Add ONUs to the OLT.

1. Add ONU 1 and ONU2 in offline mode.
Connect ONU 1 and ONU 2 to GPON ports 0/3/1 and 0/4/1 respectively through an
optical splitter. The serial numbers of the two ONUs are 3230313163902641 and
32303131B39FD642 respectively, and the management mode is SNMP. Both the ONUs
are bound to line profile 10.
huawei(config)#interface gpon 0/3
huawei(config-if-gpon-0/3)#ont add 1 ontid 1 sn-auth 3230313163902641
snmp ont-lineprofile-id 10
huawei(config-if-gpon-0/3)#quit
huawei(config-if-gpon-0/4)#ont add 1 ontid 2 sn-auth 32303131B39FD642
2. (Optional) Bind an alarm profile.

By default, an ONU will be automatically bound to alarm profile 1 (default profile). You
need to manually bind an alarm profile to an ONU only when the default alarm profile
does not meet requirements.
In this example, the default alarm profile is used. Therefore, you do not need to manually
bind an alarm profile.
Step 3 Confirm the ONU status.
After adding an ONU, run the display ont info command to query the current status of the
ONU. Ensure that Control flag is active, Run State is online, and Config state is normal.
The following uses ONU 1 as an example to describe how to confirm ONU status.
huawei(config-if-gpon-0/3)#display ont info 1 1
---------------------------------------------------------------------
F/S/P : 0/3/1
ONT-ID : 1
Control flag : active //Indicates that the ONU is
activated.
Run state : online //Indicates that the ONU is
online.
Config state : normal //Indicates that the ONU is in normal
state.
...//Other command output is omitted.
----End

SingleFAN Solution
Follow-up Procedure
When Config state is failed, Run state is offline, or Match state is mismatch:
l If Control flag is deactive, run the ont active command in GPON mode to activate the
ONU.
l If Run state is offline, a physical line may be broken or the optical module may be
damaged. Check the line and the optical module.
l If Config state is failed, the configured ONU capability exceeds the actual ONU
capability. In this case, run the display ont failed-configuration command in the
diagnose mode to check the failed configuration item and the failure cause. Then, rectify
the fault accordingly.
l If the ONU does not match, that is, Match state is mismatch, the port types and number
of ports undermatch the actual port types and number of ports supported by the ONU. In
this case, run the display ont capability command to query the actual capability of the
ONU, and then select one of the following modes to modify the ONU configuration:
– Create a proper ONU profile according to the actual capability of the ONU, and
then run the ont modify command to modify the configuration data of the ONU.
– Modify the ONU profile according to the actual capability of the ONU and save the
modification. Then, the ONU automatically recovers the configuration successfully.
1.4.4 Configuring Management Service Ports on OLT and ONUs

This topic describes how to configure management service ports (also called service flows) on
the OLT and ONUs. After the connections between the inband management service ports on
the OLT and ONUs are reachable, you can log in to the ONUs on the OLT and configure the
ONUs.
Data Plan
Configuration Data
Item
Management Management VLAN ID: 8

VLAN and Management VLAN type: smart
management IP
address for OLT Inband management IP address: 192.168.50.1/24
Management Management VLAN ID: 8

VLAN and Management VLAN type: smart
management IP
address for Inband management IP address for ONU 1: 192.168.50.2/24
ONU Inband management IP address for ONU 2: 192.168.50.3/24
NOTE
To log in to and configure an ONU remotely on the OLT, the management VLAN of the OLT must be the
same as that of the ONU, and the management IP address of the OLT and that of the ONU must be in the
same network segment.

SingleFAN Solution
Procedure
Step 1 Configure the inband management VLAN and IP address of the OLT.
Set the inband management VLAN to 8, VLAN priority to 6, and IP address to
192.168.50.1/24.
huawei(config)#vlan 8 smart
huawei(config)#port vlan 8 0/19 0
huawei(config)#vlan priority 8 6
huawei(config)#interface vlanif 8
huawei(config-if-vlanif8)#ip address 192.168.50.1 24
huawei(config-if-vlanif8)#quit
Step 2 Configure the inband management VLAN and IP address of the ONU.
Set the static IP address to 192.168.50.2/24 for ONU1, 192.168.50.3/24 for ONU2, the
gateway IP address to 192.168.50.1, and management VLAN to 8 (which is the same as that
of the OLT).
huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2 mask
255.255.255.0 gateway
192.168.50.1 vlan 8
255.255.255.0 gateway
192.168.50.1 vlan 8
Step 3 Configure an inband management service port.

Set the management VLAN to 8, GEM port ID to 11, and user VLAN to 8. The OLT does not
rate limit the inband management service port. Therefore, directly use the default traffic
profile 6.
huawei(config)#service-port vlan 8 gpon 0/3/1 ont 1 gemport 11 multi-service
user-vlan 8 rx-cttr 6 tx-cttr 6
Step 4 Confirm that the connections between the management service ports on the OLT and ONUs
are reachable.
l Run the ping ONU ip command on the OLT to verify the connectivity between the OLT
and ONUs. If the OLT receives ICMP ECHO-REPLY packets from the ONUs, the
connection is reachable.
l When the connection is reachable, you can remotely log in to the ONU from the OLT
and configure the ONUs.
----End
1.4.5 Configuring Layer 2 Interoperation Service Ports on OLT

This topic describes how to configure service ports on the OLT for Layer 2 interoperation so
that data packets sent from different ONUs can be forwarded based on the same VLAN at
Layer 2.
Prerequisites
1. The main control board on the device is an SCUN board.

SingleFAN Solution
2. The ARP proxy function is disabled using the arp proxy disable command. (The Layer
2 interoperation function and ARP proxy function are mutually exclusive.)
Data Plan
Configuratio Data
n Item
Layer 2 OLT VLAN ID (the OLT transparently transmits VLANs of ONU): 300
interoperation VLAN forwarding mode: vlan-mac (default)
S-VLAN
ONU VLAN ID: 300
Service flow ID: 301
Traffic profile Profile ID: 10

Priority source: user-cos
Default priority: 4
NOTE
For detailed data planning, see 1.3.2 Principle of VLAN Data Plan.
Procedure
Step 1 Configure an S-VLAN and add an upstream port to it.
Set the S-VLAN ID of the Layer 2 interoperation service to 300, VLAN type to smart VLAN,
and add upstream port 0/19/0 to the VLAN.
Step 2 Configure a traffic profile.
Add a new traffic profile 10 and set the assured rate to 100 Mbit/s. Packets transmitted
upstream use the priority (4 by default) copied from the user side. Packets transmitted
downstream use the priority carried by themselves.
huawei(config)#traffic table ip index 10 cir 102400 priority user-cos 4 priority-
policy tag-in-package
Step 3 Configure a service port to receive and transparently transmit the Layer 2 interoperation
service that is sent from ONU 1 and ONU 2.
Set the service attributes based on the data plan:
l For the OLT, set the S-VLAN ID to 300, C-VLAN ID to 300 which is the same as the
upstream VLAN ID of the ONU, and GEM port ID to 12 for the Layer 2 interoperation
service.
l For ONUs, set the upstream VLAN ID to 300.
huawei(config)#service-port 301 vlan 300 gpon 0/3/1 ont 1 gemport 12 multi-
service
huawei(config)#service-port 302 vlan 300 gpon 0/4/1 ont 2 gemport 12 multi-

SingleFAN Solution
service
Step 4 Configure attributes for protocol transparent transmission.

Create a VLAN service profile, enable the VLAN Layer 2 interoperation function, and
configure attributes for protocol transparent transmission. Then, bind the profile to VLAN
300. For details on data planning for protocol transparent transmission, see 1.3.4 Principle of
Protocol Transparent Transmission Data Plan.
huawei(config)#vlan service-profile profile-id 1
huawei(config-vlan-srvprof-1)#user-bridging enable //Mandatory
huawei(config-vlan-srvprof-1)#bpdu tunnel enable
huawei(config-vlan-srvprof-1)#ospf tunnel enable
huawei(config-vlan-srvprof-1)#rip tunnel enable
huawei(config-vlan-srvprof-1)#vtp-cdp tunnel enable
huawei(config-vlan-srvprof-1)#commit
huawei(config-vlan-srvprof-1)#quit
huawei(config)#multicast-unknown policy service-port 301 transparent
huawei(config)#multicast-unknown policy service-port 302 transparent
huawei(config)#vlan bind service-profile 300 profile-id 1
----End
1.4.6 Configuring Ethernet Access Service Ports on ONUs

This topic describes how to configure service ports on ONUs and configure upstream VLANs
to make the ONU-to-user connection reachable and create ONU-to-OLT upstream data
channels.
Data Planning
Configuration Data
Item
Port Upstream port: 0/0/1

Service port: 0/3/1
SVLAN VLAN ID: 300

VLAN type: smart
VLAN attribute: common

Assured rate: no rate limit
Default priority: 4
NOTE
Data plans for ONU1 and ONU 2 are the same. This topic uses one ONU as an example to describe how to
configure the ONU.
Procedure
Step 1 Remotely log in to an ONU to configure the ONU.

SingleFAN Solution
You can remote log in to the ONU from the OLT to perform the configuration. User name:
root (default); password: admin123 (default)
Step 2 Create an SVLAN and add an upstream port to the VLAN.

Configure traffic profile 8. The upstream and downstream rates are not limited. Packets
transmitted upstream use the priority (4 by default) copied from the user side. Packets
transmitted downstream use the priority carried by themselves.
huawei(config)#traffic table ip index 8 cir off priority user-cos 4 priority-
Step 4 Add a service port.

Add service port 301 and bind it to port 0/3/1. Set the user VLAN to untagged and bind it to
traffic profile 8.
huawei(config)#service-port 301 vlan 300 eth 0/3/1 multi-service user-vlan
untagged rx-cttr 8 tx-cttr 8
NOTE
Packets sent from the user side (enterprise branches) may be transmitted upstream with a VLAN tag. In this
case, change untagged to the VLAN tag when configuring a service port.
----End
1.4.7 Configuring Congestion Control and Security Policies

This topic describes how to configure global priority-based scheduling policies for queues to
ensure service reliability and configure global security policies to ensure service security.
Context
Congestion control uses queue scheduling technology to map packets sent from the same port
into multiple queues and process packets in each queue based on priority. Congestion control
is recommended.
Security policies cover system security, user security, and service security, which ensure
normal running of services.
NOTE
Enable security features based on service types. For details, see 1.3.5 Principle of Security Data Plan.
Procedure
l Configure queue scheduling.
Based on 1.3.3 Principle of QoS Data Plan, all packets use strict priorities for queue
scheduling and are mapped to queues based on priorities.
huawei(config)#queue-scheduler strict-priority
huawei(config)#cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6
cos7 7 //System default
l Configure system security.

– Enable deny of service (DoS) anti-attack on both the OLT and ONUs.
i. Run the security anti-dos enable command to globally enable DoS anti-
attack.

SingleFAN Solution
ii. Run the security anti-dos control-packet policy command to configure a

protocol packet processing policy that will be used when a DoS attack occurs.
iii. Run the security anti-dos control-packet rate command to configure the
threshold for the rate of sending protocol packets to the CPU.
– Enable IP address anti-attack on both the OLT and ONUs.
Run the security anti-ipattack enable command to enable IP address anti-attack.
l Configure user security.
– Enable MAC address anti-flapping on both the OLT and ONUs.
Run the security anti-macduplicate enable command to enable MAC address anti-
flapping.
– Enable MAC address anti-spoofing on both the OLT and ONUs.
i. In global config mode, run the security anti-macspoofing enable command to
globally enable MAC address anti-spoofing.
ii. Enable MAC address anti-spoofing at VLAN level in global config mode or
service profile mode:
1) In global config mode, run the security anti-macspoofing vlan
command to enable MAC address anti-spoofing.
2) Perform the following operations to enable MAC address anti-spoofing in
1) In global config mode, run the vlan service-profile command to
create a VLAN service profile.
2) Run the security anti-macspoofing enable command to enable
MAC address anti-spoofing at VLAN level.
3) Run the commit command to make the profile configuration take
effect.
4) Run the quit command to quit the VLAN service profile mode.
5) Run the vlan bind service-profile command to bind the created
VLAN service profile to a VLAN.
iii. (Optional) Run the security anti-macspoofing max-mac-count command to
set the maximum number of MAC addresses that can be bound to a service
flow.
iv. (Optional) Run the security anti-macspoofing exclude command to configure
the types of packets for which MAC address anti-spoofing does not take effect,
such as Internet Group Management Protocol (IGMP) packets.
– Enable IP address anti-spoofing on ONUs.
IP address anti-spoofing can be enabled or disabled at three levels: global, VLAN,
and service port levels. This function takes effect only after it is enabled at the three
levels. Among the three levels, IP address anti-spoofing is disabled only at the
global level by default.
i. In global config mode, run the security anti-ipspoofing enable command to
enable IP address anti-spoofing at the global level.
ii. In VLAN service profile mode, run the security anti-ipspoofing enable
command to enable IP address anti-spoofing at the VLAN level.

SingleFAN Solution
iii. Run the security anti-ipspoofing service-port serviceport-id enable

command to enable IP address anti-spoofing at the service port level.
----End
1.4.8 Configuring E2E Reliability

This topic describes how to configure end-to-end (E2E) protection schemes for the enterprise
private line service which has a high requirement on service reliability.
Context
Reliability covers equipment reliability, upstream networking protection, and downstream
networking protection. For details on reliability data planning, see 1.3.6 Principle of
Reliability Data Plan.
l Upstream networking protection includes link aggregation group and protection group.
Usually, link aggregation group is configured when the GIU board is used to transmit
traffic upstream; protection group is configured when the main control board is used to
transmit traffic upstream. The two protection schemes are not configured at the same
time.
l Downstream networking protection includes Type B, Type C single homing, and Type C
dual homing, which are used to protect service ports. Ports on the same ONU can be
configured only with the same protection scheme.
NOTE
This topic describes how to configure five mainstream protection schemes. Select required protection
schemes based on the carrier's requirement and actual networking scenario.
Procedure
l Configure a link aggregation group.
Bind upstream ports 0/19/0 and 0/19/1 together as an aggregation link group. Each
member port in the group transmits packets based on source MAC addresses. The
working mode is LACP static aggregation.
huawei(config)#link-aggregation 0/19 0-1 ingress workmode lacp-static
l Configure a protection group.

Configure upstream ports 0/19/0 and 0/19/1 on board GIU as a port protection group. Set
port 0/19/0 as the working port and port 0/19/1 as the protection port, set the working
mode to time delay detection, and enable the protection group.
huawei(config-protect)#protect-group first 0/19/0 second 0/19/1 eth workmode
timedelay enable
l Configure the Type B protection.

Figure 1-2 shows the Type B protection networking diagram.

SingleFAN Solution
Figure 1-2 Type B protection
ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
Configure redundancy backup for ports 0/3/1 and 0/3/2 on the same GPON board on
OLT. When port 0/3/1 fails, the system can automatically switch to port 0/3/2.
huawei(config)#protect-group 0 protect-target gpon-uni-port workmode timedelay
huawei(protect-group-0)#protect-group member port 0/3/1 role work
huawei(protect-group-0)#protect-group member port 0/3/2 role protect
huawei(protect-group-0)#protect-group enable
NOTE
The configurations of services accessed by the ONUs remain the same after the Type B protection is
configured. That is, the service configurations are applied only to the working GPON port.
l Configure the Type C single homing protection.
Figure 1-3 shows networking diagram for the Type C single homing protection.
Configure two 1:N optical splitters, one for connecting the working PON ports on the
OLT and ONUs, and one for connecting the protection PON ports on the OLT and
ONUs. This protection scheme protects both the backbone fibers and tributary fibers.
The configurations of services accessed by the ONUs remain the same after the Type C
single homing protection is configured. That is, the service configurations are applied
only to the working PON port on the OLT and working upstream PON ports on the
ONUs.
Figure 1-3 Type C single homing protection
ONU Splitter A
OLT
Splitter B
Tributary Fibers
Protection
Backbone Fibers
Protection
Active
Standby

SingleFAN Solution
As shown in the preceding figure, Type C single homing protecting is configured for
optical fiber links between the OLT and ONU.
– The ports on the GPON service board are 0/3/1 and 0/3/2.
– The link at port 0/3/1 is the working link.
– The link at port 0/3/2 is the protection link.
– The ONU ID is 1.
– The ONU is authenticated by serial number (SN). The SN of the ONU is
3230313163902641 and the management mode is SNMP.
– The ID of the line profile bound to the ONU is 10.
huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 3230313163902641 snmp ont-
lineprofile-id 10
huawei(config-if-gpon-0/3)#ont add 2 1 protect-side
huawei(config)#protect-group protect-target gpon-uni-ont workmode portstate
huawei(protect-group-1)#protect-group member port 0/3/1 ont 1 role work
huawei(protect-group-1)#protect-group member port 0/3/2 ont 1 role protect
huawei(protect-group-1)#quit
l Configure the Type C dual homing protection.

Figure 1-4 shows the networking diagram for the Type C dual homing protection. Two
PON ports on different OLTs, two PON ports on an ONU, two backbone optical fibers,
two optical splitters, and two tributary optical fibers are configured to implement this
protection. The difference between this protection scheme and the Type C single homing
protection scheme is that the ONU needs to be dual homed to two OLTs in this
protection scheme.
The models and versions of main control boards on the active and standby OLTs must be
the same. The models and versions of GPON boards on the active and standby OLTs also
must be the same. Data on the active OLT cannot be automatically synchronized with
that on the standby OLT. Therefore, data synchronization between the active and standby
OLTs must be manually ensured.
This protection scheme can be configured for only the Ethernet QinQ private line
service. It does not support TDM services, including Native TDM and SAToP.

SingleFAN Solution
Figure 1-4 Type C dual homing protection
Active OLT
Splitter A
ONU
Splitter B
Standby OLT
Active
Standby
As shown in the preceding figure, Type C dual homing protection is configured for two
OLTs (huawei_A and huawei_B).
– huawei_A is the active OLT while huawei_B is the standby OLT.
– The ports on the service boards on both OTLs are 0/3/1.
– The dual homing protection group ID is 1.
Configurations on the active OLT huawei_A:
huawei_A(config)#interface gpon 0/3
huawei_A(config-if-gpon-0/3)#ont add 1 1 sn-auth 3230313163902641 snmp ont-
lineprofile-id 10
huawei_A(config-if-gpon-0/3)#quit
huawei_A(config)#protect-group 1 protect-target gpon-uni-ont workmode dual-
parenting
huawei_A(protect-group-1)#protect-group member port 0/3/1 ont 1 role work
Configurations on the standby OLT huawei_B:
huawei_B(config)#interface gpon 0/3
huawei_B(config-if-gpon-0/3)#ont add 1 1 sn-auth 3230313163902641 snmp ont-
lineprofile-id 10
huawei_B(config-if-gpon-0/3)#quit
huawei_B(config)#protect-group 1 protect-target gpon-uni-ont workmode dual-
parenting
huawei_B(protect-group-1)#protect-group member port 0/3/1 ont 1 role protect
huawei_B(protect-group-1)#protect-group enable
----End

SingleFAN Solution
1.4.9 Verifying Services

This topic describes how to verify the Layer 2 interoperation service by checking the service
configurations, service port status, and connectivity between PCs in different branches of an
enterprise.
Prerequisites
PCs (with different MAC addresses) connected to different ONUs have been configured.
Ensure that the IP addresses of the PCs are in the same network segment or subnet segment.
Procedure
Step 1 Check whether the VLAN configurations are correct.
huawei(config)#display vlan 300
{ <cr>|inner-vlan<K>|to<K> }:
Command:
display vlan 300
VLAN ID: 300
VLAN type: smart
VLAN description:
VLAN forwarding mode in control board: VLAN-MAC
VLAN forwarding mode: VLAN-MAC
VLAN broadcast packet forwarding policy: forward
VLAN unknown multicast packet forwarding policy: forward
VLAN unknown unicast packet forwarding policy: forward
VLAN bind service profile ID: 1
VLAN bind RAIO profile index: -
VLAN priority: -
Standard port number: 0
---------------------------------------------------------
INDEX TYPE STATE F/ S/ P VPI VCI FLOWTYPE FLOWPARA
---------------------------------------------------------
10 gpon up 0/3 / 1 1 12 vlan 300
11 gpon up 0/3 / 1 2 12 vlan 300
---------------------------------------------------------
Service virtual port number: 2
Note: F--Frame, S--Slot, P--Port,
VPI indicates ONT ID for PON, VCI indicates GEM index for GPON,
v/e--vlan/encap, pri-tag--priority-tagged
huawei(config)#display vlan service-profile profile-id 1
Profile ID: 1
Profile Name: srvprof-1
---------------------------------------------------------------------
Parameter Committed Not Committed
---------------------------------------------------------------------
Forwarding mode NotConfig -
Anti-macspoofing NotConfig -
Anti-ipspoofing enable -
PPPoE MAC mode NotConfig -
BPDU tunnel enable -
RIP tunnel enable -
VTP-CDP tunnel enable -
DHCP mode n/a -
DHCP proxy enable -
DHCP option82 enable -
PITP enable -
Broadcast packet policy NotConfig -
Multicast packet policy NotConfig -
Unknown unicast packet policy NotConfig -
User-bridging enable -
IPoE VMAC NotConfig -

SingleFAN Solution
PPPoE VMAC NotConfig -

PPPoA VMAC NotConfig -
Mismatch IGMP packet policy discard -
VMAC aging mode MAC-learning -
OSPF tunnel enable -
Layer-3 protocol tunnel enable -
MAC-address learning fabric enable -
DHCPv6 mode n/a -
DHCPv6 option enable -
PPPoA MAC mode NotConfig -
Anti-IPv6spoofing enable -
IPv6 DAD proxy disable -
Bind route and ND disable -
NS-reply function disable -
ARP-reply function disable -
DHCP relay-interface relay-agent NotConfig -
Multicast packet policy fabric forward -
---------------------------------------------------------------------
Binding VLAN list : 300
---------------------------------------------------------------------
Step 2 Check whether the service port is normal.

huawei(config)#display service-port vlan 300
{ <cr>|autosense<K>|sort-by<K> }:
Command:
display service-port vlan 300
Switch-Oriented Flow List
----------------------------------------------------------------------------
INDEX VLAN VLAN PORT F/ S/ P VPI VCI FLOW FLOW RX TX STATE
ID ATTR TYPE TYPE PARA
----------------------------------------------------------------------------
10 300 common gpon 0/3 /1 1 12 vlan 300 - - up
11 300 common gpon 0/3 /1 2 12 vlan 300 - - up
----------------------------------------------------------------------------
Total : 2 (Up/Down : 2/0)
huawei(config)#display statistics service-port 10
Number of upstream bytes : 1044794
Number of upstream packets : 4522
Number of upstream discard packets : 200
Number of downstream bytes : 1351261
Number of downstream packets : 4677
Number of downstream discard packets : 0
Step 3 Check the connectivity between the PCs.

1. Use the PCs to ping each other. If the PCs can ping each other successfully, the PCs are
reachable to each other.
For example, the IP addresses of PC1 and PC2 are 192.168.1.10 and 192.168.1.30
respectively. Ping PC2 on PC1. The expected result is as follows:

SingleFAN Solution
2. You can see one PC in My Network Places on the other PC and the two PCs can share
data.
----End
1.5 Configuring Enterprise DDN Private Line Access

Service (GPON)
Enterprise DDN private line service is converted to E1 signals. ONUs access the E1 signals
and transmit them in Native TDM mode.
Service Requirement
The DDN private line service is widely used in financial departments, governments, and
enterprises that require highly real-time data switching. It provides a rate from 64 kbit/s to 2
Mbit/s. GPON access in OLT+ONU mode can access the DDN private line service along with
other data services and voice service. This access mode does not require independent
maintenance of the DDN network, simplifying network architecture.
As shown in Figure 1-5, a protocol converter is deployed between an ONU and DDN node
machine to convert DDN private line services to E1 services. The ONU accesses the E1
services and encapsulates the service packets in TDM over GEM mode and then transmits the
packets to the OLT. The OLT decapsulates the service packets to E1 data and transmits the
data to the SDH network through upstream E1/STM-1 ports, achieving transparent
transmission of DDN services.
Figure 1-5 Networking diagram of the DDN private line access service
DDN Node
Digital Terminal Protocol ONU
Machine
Converter
OLT
DDN V.24/ E1
V.35
SDH
E1/STM-1
DDN Node Splitter
Digital Terminal
Machine Protocol
Converter
E1
DDN V.24/ ONU
V.35

SingleFAN Solution
The following figure shows the configuration process for the DDN private line access service.
Start
Adding ONUs to OLT
Service Ports on OLT and
ONUs OLT Side
Configuring TDM E1
Connections
Policies
Configuring Clock
Synchronization
Verifying DDN Access

Services
End

Context
profile, line profile, and alarm profile.

SingleFAN Solution
l An ONU can be added in two modes: offline addition and online confirmation. Select
either mode as required.
Data Plan

Configurati Data
on Item
DBA profile DBA profile for management service: dba-profile_1 (system default)
DBA profile for private line service:
l Profile ID: 21
l Profile type: Fixed bandwidth and minimum delay
l DBA bandwidth: 28928 kbit/s (Each ONU accesses four E1 private
lines and each line has a recommended DBA bandwidth of 7232
kbit/s.)

T-CONT ID: 1 (for private line service) and 2 (for management service)
GEM port ID for DDN private line service: 13
Networking PON port: 0/3/1

data ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Procedure
1. Configure a DBA profile. Enable the bandwidth compensation function and set the DBA
bandwidth allocation mode for the GPON port to minimum bandwidth delay.
huawei(config)#dba-profile add profile-id 21 type1 fix 28928
bandwidth_compensate yes
huawei(config-if-gpon-0/3)#port dba bandwidth-assignment-mode 1 min-loop-delay

huawei(config-gpon-lineprofile-11)#tcont 1 dba-profile-id 21 //Bind T-CONT 1
to DBA profile 21
to DBA profile 1
huawei(config-gpon-lineprofile-11)#gem add 11 eth tcont 2
huawei(config-gpon-lineprofile-11)#gem add 13 tdm tcont 1 //Add GEM port 13
to T-CONT 1.
huawei(config-gpon-lineprofile-11)#gem mapping 13 1 e1 1 //Map GEM port 13 to
E1 port 1 on the ONU.

SingleFAN Solution

1. Add ONU 3 in offline mode.

---------------------------------------------------------------------
F/S/P : 0/3/1
ONT-ID : 1
activated.
online.
state.
----End
Follow-up Procedure
ONU.

SingleFAN Solution

ONUs.
Data Plan
Configuration Item Data
Management VLAN and management IP Management VLAN ID: 8

address for OLT Management VLAN type: smart
Inband management IP address:
192.168.50.1/24

address for ONU Management VLAN type: smart
Inband management IP address for ONU 3:
192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.
Step 4 Confirm that the connections between the management service ports on the OLT and ONU are
reachable.

SingleFAN Solution
and ONU. If the OLT receives ICMP ECHO-REPLY packets from the ONU, the
and configure the ONU.
----End
1.5.5 Configuring TDM Connections

This topic describes how to configure Native TDM connections between GPON ports and E1/
STM-1 upstream ports to transmit E1/STM-1 private line service data.
Prerequisites
Required hardware is available:
l TOPA+NH1A for upstream transmission through E1
l TOPA+O2CE for upstream transmission through STM-1
l GPON board: GPBC, GPBD
Context
The OLT can transmit data to the SDH network through E1 or STM-1 lines. Each E1 line
provides 2 Mbit/s bandwidth. After being mapped, aligned, and encapsulated, 63xE1 signals
are multiplexed into one STM-1 signal through VC12. One STM-1 line provides 155 Mbit/s.
When the OLT transmits data to SDH equipment through STM-1 lines, pay attention to the
VC12 mode and VC12 number.
l When the OLT is interconnected with Huawei SDH equipment, the VC12 mode is
huawei and the VC12 numbers on the OLT and the SDH equipment must be consistent.
l When the OLT is interconnected with Lucent SDH equipment, the VC12 mode is lucent.
The VC12 numbers has the following mapping relationships (which can be queried using
the display vc12-mode-table command):
Huawei: Mapping between the multiplexing number and VC12 number: VC12 number =
(TUG3–1) + (TUG2–1) x 3 + (TU12–1) x 21
Lucent: Mapping between the multiplexing number and VC12 number: VC12 number =
(TU12–1) + (TUG2–1) x 3 + (TUG3–1) x 21
Data Plan
Upstream Data
Transmissio
n Mode
Upstream Port on the TOPA board: 0/5/0

transmission Daughter board type: NH1A (provides E1 ports)
through E1

SingleFAN Solution
Upstream Data
Transmissio
n Mode
Upstream Port on the TOPA board: 0/5/0

transmission Daughter board type: O2CE (provides STM-1 ports)
through
STM-1 VC12 number: 0
NOTE
The VC12 parameter must match that on the interconnected SDH equipment.
Otherwise, services fail.
Procedure
l Configure a TDM E1 connection for E1 upstream transmission.
huawei(config)#tdm-connect connectid 1 tdm 0/5/0 gpon 0/3/1 ontid 3
gemportIndex 13
l Configure a TDM E1 connection for STM-1 upstream transmission.

huawei(config)#tdm-connect connectid 1 tdm 0/5/0 vc12 0 gpon 0/3/1 ontid 3
gemportIndex 13
----End
1.5.6 Configuring Clock Synchronization

In this scenario, the E1/STM-1 line clock can be used to achieve network-wide clock
synchronization.
Prerequisites
The clock daughter board CKMC/CKMD must be on the SCU main control board.
Context
Configuration roadmap for clock synchronization:
1. The OLT traces the upstream E1/STM-1 line clock of the TOPA board as the system
clock.
2. The system clock is delivered to an ONU through optical paths of the GPON board.
3. The ONU uses the line clock of the GPON upstream port as the system clock.
4. The ONU E1 transmit clock is synchronized with the system clock of the ONU.
Procedure
l Configure a clock on the OLT.
a. Add a system clock source.
Run the clock source command to configure the line clock of E1/STM-1 port 0/5/0
on the TOPA board as the system clock source. Set the ID of the clock source to 0.
The clock module automatically judges the type of the specified clock source (E1/
STM-1) and selects a reference source for phase lock based on priorities.
huawei(config)#clock source 0 0/5/0

SingleFAN Solution
b. Configure a priority for the system clock source.

Run the clock priority command to set the priority of clock source 0 to the highest
priority.
huawei(config)#clock priority system 0
c. Query configurations and the status of the system clock source.

Run the display clock source system command to query the configurations and the
status of the clock source. Ensure that configurations of the system clock source are
correct and the status is Normal.
huawei(config)#display clock source system
-------------------------------------------------------------------------
-----
Index Board Source Clk-type State Priority QL
Selected
-------------------------------------------------------------------------
-----
0 H801TOPA 0/5/0 E1 Normal 0 ---
YES
-------------------------------------------------------------------------
-----
Run the display clock mode command to query the clock working mode. Ensure
that the clock daughter board works in tracing mode.
huawei(config)#display clock mode
Clock manage-mode:Third-mode
Clock subboard work-mode:Tracing
l Configure a clock on the ONU.

a. Configure the GPON line clock as the system clock.
The system clock of the OLT is delivered to the ONU through the GPON port on
the OLT, achieving clock synchronization between the OLT and the ONU.
i. Run the clock source command to configure the clock recovered from the
GPON upstream port as the system clock of the ONU.
ii. Run the clock priority command to configure the priority of the clock source.
Clock source set succeeded
b. Configure the system clock as the transmit clock for an E1 port.

i. Run the interface tdm command to enter the E1 port configuration mode.
ii. Run the tx clock or port portid udt system command to configure the system
clock as the transmit clock of the port.
iii. Run the display port state command to query the transmit clock of the E1
port.
huawei(config)#interface tdm 0/1
huawei(config-if-tdm-0/1)#port 0 udt system
huawei(config-if-tdm-0/1)#display port state 0
---------------------------------------
Port : 0
State : normal
Mode : UDT
Code : HDB3
Looptype : -
Timeslot : -

SingleFAN Solution
Clock : system
CRC4 : -
Signaling : -
ESF : -
Impedance : 120 Ohm
---------------------------------------

Run the display clock source command to query configurations and the status of
the system clock source.
huawei(config-if-tdm-0/1)#quit
huawei(config)#display clock source
---------------------------------------------------------------
Index Config Type Source State Priority Output
---------------------------------------------------------------
0 YES line 0/0/1 Normal 0 YES
1 NO -- -/ -/ - --- --- ---
2 NO -- -/ -/ - --- --- ---
3 NO -- -/ -/ - --- --- ---
4 NO -- -/ -/ - --- --- ---
5 NO -- -/ -/ - --- --- ---
6 NO -- -/ -/ - --- --- ---
7 NO -- -/ -/ - --- --- ---
8 NO -- -/ -/ - --- --- ---
9 NO -- -/ -/ - --- --- ---
---------------------------------------------------------------
----End

This topic describes how to use the PDH/SDH tester to verify the private line access service.
Prerequisites
The private line service has been configured.
Networking
Figure 1-6 Test setup for E1 upstream service
ONU OLT
E1 port E1 line tester
loopback
E1
ONU trace OLT trace Internal

the clock of the clock of free-run
the OLT the tester clock

SingleFAN Solution
Figure 1-7 Test setup for STM-1 upstream service
E1 port ONU OLT

STM-1 line tester
loopback
STM-1

Procedure
Step 1 Set up network environment according to the preceding diagrams for service acceptance tests.
NOTE
Ensure clock synchronization for the test. It is recommended that the tester use the internal free-run clock, the
OLT trace the clock of the tester, and the ONU trace the clock of the OLT.
Step 2 Use the E1 or STM-1 line tester to send packets for the test.
The test duration must be 12 hours or longer. There should be no alarms on the tester and the
bit error rate must be less than 1E-9.
----End
Follow-up Procedure
When the test on service connectivity fails, you can check for the failure causes by
performing loopbacks. The following loopbacks are supported:
l Remote loopback on the OLT TOPA board
l Local loopback on the OLT TOPA board
l Local loopback on the ONU
l Remote loopback on the ONU

SingleFAN Solution
Loopb Function Networking Configuration

ack
Mode
Remote Loops back ONU OLT E1 line

tester
Enable/Disable the remote
loopba signals to the E1 loopback for the E1 port.
ck on network side on huawei(config)#interface
top 0/5
the the TOPA board Remote loopback
huawei(config-if-
TOPA on the OLT. This top-0/5)#loopback 0
board loopback checks remote
huawei(config-if-
whether the top-0/5)#undo loopback 0
service from the
TOPA board to Enable/Disable the remote
the network-side loopback for the STM-1 port.
huawei(config)#interface
channel is top-stm1 0/5
normal. huawei(config-if-top-
stm1-0/5)#loopback 0
remote
huawei(config-if-top-
stm1-0/5)#undo loopback 0
Local Loops back E1 line

tester
ONU OLT Enable/Disable the local
E1
loopba signals to the loopback for the E1 port.
ck on user side on the huawei(config)#interface
top 0/5
the TOPA board on Local loopback
huawei(config-if-
TOPA the OLT. This top-0/5)#loopback 0 local
board loopback checks huawei(config-if-
top-0/5)#undo loopback 0
whether the link
between the Enable/Disable the local
TOPA board and loopback for the STM-1 port.
huawei(config)#interface
the E1 port on
top-stm1 0/5
the ONU is huawei(config-if-top-
normal. stm1-0/5)#loopback 0
local
huawei(config-if-top-
stm1-0/5)#undo loopback 0
Local Loops back ONU OLT E1 line huawei(config)#interface

tester
tdm 0/1
loopba signals to the E1
huawei(config-if-
ck on network side on tdm-0/1)#loopback 0 local
the the ONU. This Local loopback huawei(config-if-
tdm-0/1)#undo loopback 0
ONU loopback checks
whether the link
between the E1
port on the ONU
and the TOPA
board on the
OLT is normal.

SingleFAN Solution

ack
Mode
Remote Loops back E1 line ONU OLT huawei(config)#interface

tester E1 tdm 0/1
loopba signals to the huawei(config-if-
ck on user side on the tdm-0/1)#loopback 0
Remote loopback
the ONU. This remote
huawei(config-if-
ONU loopback checks tdm-0/1)#undo loopback 0
whether the link
between the
ONU and user
terminal is
normal.
1.6 Configuring Enterprise IP PBX Private Line Access

Service (GPON)
ONUs provide GE/FE ports to access IP private branch exchange (PBX) services of an
the packet switched network (PSN). This achieves unified carrying of voice, data, and video
services.

Service Requirement
l The IP private branch exchange (PBX) data can be transparently transmitted on the PON
network.
l The operation method for end users connected to the IP PBX is not changed.
As shown in Figure 1-8, ONUs access IP PBX services through FE/GE ports. The OLT
transparently transmits the data to the IP network in QinQ mode.

SingleFAN Solution
Figure 1-8 Networking diagram of the IP PBX access service
IP PBX
ONU
FE/G
E OLT
IP network
GE/10GE
Splitter
E
FE/G NGN/IMS
ONU
IP PBX

The following figure shows the configuration process for the IP PBX access service.

SingleFAN Solution
Start
Adding ONUs to OLT
ONUs
OLT Side
Configuring OLT QinQ

Service Ports
Policies
Configuring E2E Reliability
Configuring Ethernet
ONU Side
Access Service Ports
Verifying IP PBX Services
End


SingleFAN Solution
Context
Data Planning
Configurati Data
on Item


T-CONT ID: 4
GEM port ID for other services: 12

l ONU ID: 1
l SN: 3230313163902641
Procedure

to DBA profile 20
huawei(config-gpon-lineprofile-10)#gem add 12 eth tcont 4 //Add GEM port 12
to T-CONT 4
huawei(config-gpon-lineprofile-10)#gem mapping 12 1 vlan 300 //Map GEM port
12 to CVLAN 300


SingleFAN Solution


---------------------------------------------------------------------
F/S/P : 0/3/1
ONT-ID : 1
activated.
online.
state.
----End
Follow-up Procedure
ONU.

SingleFAN Solution

ONUs.
Data Plan

192.168.50.1/24

192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.
reachable.

SingleFAN Solution
----End
1.6.5 Configuring OLT QinQ Service Ports

This topic describes how to configure QinQ service ports on the OLT to add an S-VLAN tag
to IP PBX packets sent from ONUs and transmit the packets to the upper-layer IP network.
Data Plan
For details on VLAN planning, see 1.3.2 Principle of VLAN Data Plan. VLAN translation
policies for the Enterprise IP private branch exchange (PBX) access service are shown in
Figure 1-9. Different data packets of the IP PBX carry different user VLANs (for example,
20, 21, ... in the following figure). The user VLANs are translated to C-VLAN 300 on the
ONU and then the OLT adds the outer VLAN 1300 to the packets before transmitting them
upstream. In this manner, only two VLANs are required on the MAN for the base station
access service, which significantly reduces the number of VLANs.
Figure 1-9 VLAN translation process
SVLAN VLAN ID: 1300

VLAN attribute: q-in-q
CVLAN (upstream 300

VALN of the ONU)

Default priority: 4
NOTE
Because packets transmitted from the OLT carry two VLAN tags, the interconnected equipment on the metro
network must be able to identify and restore packets with two VLAN tags.

SingleFAN Solution
Procedure
Set the S-VLAN ID of the IP PBX service to 1300, VLAN type to smart, VLAN attribute to
QinQ, and add upstream port 0/19/0 to the VLAN.
huawei(config)#vlan attrib 1300 q-in-q
Step 2 Configure a traffic profile for the service port.
Step 3 Configure a QinQ service port.
According to 1.3.2 Principle of VLAN Data Plan, VLANs of packets sent from the IP PBX
are all translated to CLVAN 300. Then, the OLT adds an S-VLAN tag to the packets: C-
VLAN<->S-VLAN+C-VLAN. Traffic profile 10 is used.
NOTE
If you need to transparently transmit the C-VLAN to S-VLAN, then user qinq S-VLAN, set S-VLAN=C-
VLAN, and create a service-port with "tag-transform transparent".
----End
1.6.6 Configuring Ethernet Access Service Ports on ONUs

This topic describes how to configure service ports on ONUs and upstream VLANs to make
the connections between ONUs and user terminals reachable and create upstream channels
between ONUs and the OLT, achieving access of IP PBX services through Ethernet ports.
Data Planning
Configuration Data
Item
Port Upstream port: 0/0/1

Service port: 0/3/1
SVLAN VLAN ID: 300

VLAN type: smart

Assured rate: no rate limit
Default priority: 4

SingleFAN Solution
Procedure
Step 1 Remotely log in to an ONU to configure the ONU.
You can remote log in to the ONU from the OLT to perform the configuration. User name:
root (default); password: admin123 (default)
Step 2 Create an SVLAN 300.
Step 3 Add upstream port 0/0/1 to the SVLAN.


Configure traffic profile 8. The upstream and downstream rates are not limited. Packets
transmitted upstream use the priority (4 by default) copied from the user side. Packets
transmitted downstream use the priority carried by themselves.
huawei(config)#traffic table ip index 8 cir off priority user-cos 4 priority-
Step 5 Add a service port.

Add a service port and bind it to port 0/3/1. Set the user VLAN to untagged and bind it to
traffic profile 8.
huawei(config)#service-port vlan 300 eth 0/3/1 multi-service user-vlan
untagged rx-cttr 8 tx-cttr 8
NOTE
Packets sent from the user side (IP PBX) may be transmitted upstream with a VLAN tag. In this case, change
untagged to the VLAN tag when configuring a service port.
----End

Context
is recommended.
NOTE
Procedure

SingleFAN Solution

attack.
flapping.
effect.
flow.

SingleFAN Solution

----End

Context
time.
NOTE
Procedure

timedelay enable


SingleFAN Solution
ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
NOTE
ONUs.
ONU Splitter A
OLT
Splitter B
Tributary Fibers
Protection
Backbone Fibers
Protection
Active
Standby

SingleFAN Solution
lineprofile-id 10

protection scheme.

SingleFAN Solution
Active OLT
Splitter A
ONU
Splitter B
Standby OLT
Active
Standby
lineprofile-id 10
parenting
lineprofile-id 10
parenting
----End

This topic describes how to verify the IP PBX access service by testing calls.

SingleFAN Solution
Prerequisites
The IP PBX access service has been deployed.
Procedure
Step 1 Test calls between users connected to the IP PBX according to table 1.
Step 2 Test calls from a user connected to the IP PBX to an IMS user according to table 1.
Step 3 Test calls from an IMS user to a user connected to the IP PBX according to table 1.
Table 1-5 IP PBX access service verification

Categ Test Calls Between Test Calls from a User Test Calls from an IMS
ory Users Connected to Connected to the IP User to a User
the IP PBX PBX to an IMS User Connected to the IP
PBX
Prereq 1. User A and user B 1. User A accesses the 1. User A is a common

uisites access the network network through the IP IMS user and has been
through the IP PBX and has been registered.
PBX and both registered. 2. User B accesses the
users have been 2. User B is a common network through the IP
registered. IMS user and has been PBX and has been
2. User A and user B registered. registered.
are idle. 3. User A and user B are 3. User A and user B are
idle. idle.
Test 1. User A calls user The same as that in the The same as that in the
proced B. "Test Calls Between Users "Test Calls Between Users
ure 2. User B answers Connected to the IP PBX" Connected to the IP PBX"
the call. Check the column column
call between user
A and user B.
3. User A releases
the call.
Expect 1. User B hears the The same as that in the The same as that in the
ed ringing tone. "Test Calls Between Users "Test Calls Between Users
result 2. The call is set up. Connected to the IP PBX" Connected to the IP PBX"
column column
3. The call is
released.
----End
1.7 Configuring Enterprise PRA PBX Private Line Access

Service (GPON)
ONUs provide PRA E1 ports to access PRA private branch exchange (PBX) services of an

SingleFAN Solution
the packet switched network (PSN). This achieves voice-to-IP conversion, simplifying the
network architecture.
Service Requirement
PRA PBX is a telephone exchange used in an enterprise. With the PRA PBX, staff in the
enterprise can use internal telephones to make free calls by dialing short numbers. Outgoing
calls are made through a unified trunk. After the PRA PBX service is accessed in PON mode
using "OLT+ONU", VoIP calls can be made. Compared with services provided by the PRA
PBX itself, the VoIP service has following advantages:
l Outgoing call data is carried over IP, which greatly lowers communication costs for
enterprises and retains good call quality.
l No extra investment is required because the voice service is deployed directly using the
PRA PBX.
l Free calls can be made between branches in different regions.
l More value-added services can be provided based on IP networks.
In addition, the operation method for end users connected to the PRA PBX is not changed.
As shown in Figure 1-13, ONUs access PRA PBX services through E1 lines. The OLT
transmits the data to the upper NGN/IMS, achieving the VoIP-based PRA voice service.
Figure 1-13 Networking diagram of the PRA PBX access service
PRA PBX
ONU
E1
OLT
IP network
GE/10GE
Splitter
E1 NGN/IMS
ONU
PRA PBX
The following figure shows the configuration process for the PRA PBX access service.

SingleFAN Solution
Start
Adding ONUs to OLT
ONUs
OLT Side
Configuring Transparently-
transmitted Voice Service
Ports
Policies
Configuring E2E Reliability
Configuring VoIP PRA

Services
ONU Side
Verifying PRA PBX

Services
End

Context

SingleFAN Solution
Data Planning

Configurati Data
on Item


T-CONT ID: 4
GEM port ID for other services: 12

l ONU ID: 1
l SN: 3230313163902641
Procedure

to DBA profile 20
to T-CONT 4
12 to CVLAN 300



SingleFAN Solution


---------------------------------------------------------------------
F/S/P : 0/3/1
ONT-ID : 1
activated.
online.
state.
----End
Follow-up Procedure
ONU.


SingleFAN Solution
ONUs.
Data Plan

192.168.50.1/24

192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.
reachable.
----End

SingleFAN Solution
1.7.5 Configuring Service Ports for Voice Transparent

Transmission
This topic describes how to create service ports on the OLT to transparently transmit VoIP
service data from ONUs to the upper-layer voice server.
Data Plan
SVLAN VLAN ID: 300

CVLAN (upstream VALN of 300

the ONU)

Default priority: 5
NOTE
The VoIP service is a self-operated service. The single S-VLAN is a mainstream application and is
recommended.
Procedure
Set the S-VLAN ID of the PRA PBX service to 300, VLAN type to smart, and add upstream
port 0/19/0 to the VLAN.
Step 2 Configure a traffic profile for the service port.

Step 3 Configure a service port.

According to 1.3.2 Principle of VLAN Data Plan, VLANs of packets sent from the PRA
PBX are all translated to CLVAN 300. The OLT transparently transmits the packets. The
traffic profile 10 is used.
----End

SingleFAN Solution
1.7.6 Configuring VoIP PRA Access

This topic describes how to configure VoIP PRA access. ONUs provide PRA E1 ports to
access the PRA PBX service and convert PRA signaling to ISDN Q.931-User Adaptation
Layer (IUA) signaling, achieving signaling exchange between ONUs and media gateway
controller (MGCs).
Prerequisites
The H.248 protocol is a master/slave protocol which is used by an MGC to control access
gateways (AGs) to implement call connections. The data, including media gateway (MG)
interface attributes and voice user attributes on AGs, must be consistent with those on the
MGC. Therefore, before configuring the VoIP voice service, plan data with the MGC.
Context
IUA is the ISDN Q.931-User Adaptation Layer protocol. IUA links carry signaling exchanged
between ONUs and MGCs.
Data Plan
Table 1-7 Data plan for VoIP PRA service
Configuration Data
Item
VLAN VLAN ID: 300

IP address of the Layer 3 interface: 10.10.10.10/24
MG interface MG ID: 0
Media/signaling IP address: 10.10.10.10/24
MGC IP address: 200.200.200.200
Gateway IP address: 10.10.10.1
Protocol port: 2944
IUA linkset IUA link set ID: 1

Working mode of the link set: override
Interface ID (IID) generation mode: 2
Service environment of the IUA link set: client
Interlocking function: enabled
IUA link IUA link ID: 0

Local port ID: 1402
Local IP address: 10.10.10.10
Remote port ID: 1404
Remote IP address for the primary MGC: 200.200.200.200
Interlocking policy: the link switches over with the primary MAC

SingleFAN Solution
Configuration Data
Item
PRA port Subrack ID/slot ID/port ID: 0/1/0

Terminal ID: 512
Procedure
Step 1 Configure an upstream VLAN and VLAN interface.
Specify an upstream VLAN interface for the media stream and signaling flow, and set the IP
addresses of the Layer 3 interface. These IP addresses are the sources of the media and
signaling IP address pools.
1. Create an upstream VLAN 300 and add upstream port 0/0/1 to the VLAN.
2. Configure the IP address of Layer 3 interface.

Enter the VLAN interface mode and set the IP address of the Layer 3 interface to
10.10.10.10.
Step 2 Configure the media and signaling IP address pools.

The media and signaling IP addresses are 10.10.10.10, and the media gateway IP address is
10.10.10.1.
huawei(config)#voip
huawei(config-voip)#ip address media 10.10.10.10 10.10.10.1
huawei(config-voip)#ip address signaling 10.10.10.10
huawei(config-voip)#quit
NOTE
The media IP address can be different from the signaling IP address. You can make data plan according
to the actual network situation.
Step 3 Configure a static route.

Because the IP address of the VLAN interface and the IP address of the MGC
(200.200.200.200/24) are in different network segments, a route from gateway 10.10.10.1 to
200.200.200.0 network segment must be configured.
huawei(config)#ip route-static 200.200.200.0 24 10.10.10.1
Step 4 Add an MG interface and configure interface attributes.

1. Add an MG interface.
Add an MG interface for the MG to communicate with the MGC, which ensures that the
MGC can control call connections through the MG interface. Add MG interface 0
according to the data plan.
huawei(config)#interface h248 0
Are you sure to add MG interface?(y/n)[n]:y
2. Configure MG interface attributes.
Configure MG interface attributes according to the data plan. When configuring the
attributes, note that:

SingleFAN Solution
– The registration mode of the MG interface must be consistent with that on the
MGC. Registration mode: by IP address (default) or by domain name
– H.248 version for negotiation: H.248v1, H.248v2, or H.248v3 (default). When H.
248v3 is used, interfaces fail to be registered if some softswitches do not support H.
248v3.
huawei(config-if-h248-0)#if-h248 attribute mgip 10.10.10.10 mgport
2944 code text transfer udp primary-mgc-ip1 200.200.200.200 primary-mgc-port
2944 mg-media-ip1 10.10.10.10 start-negotiate-version 1
3. Enable the MG interface.

huawei(config-if-h248-0)#reset coldstart
Are you sure to reset MG interface?(y/n)[n]:y
huawei(config-if-h248-0)#quit
NOTE
– After configuring the MG interface, you must perform a cold reset on the interface. Otherwise, the
interface cannot take effect.
– You can perform a cold reset on the MG interface only after the following parameters are correctly
configured: mgip, mgport, primary-mgc-ip1 (or mgc-domain-name1), mgcport_1, code,
transfer, and mg-media-ip.
4. Query the running status of the MG interface.
If the MG interface is interconnected with the MGC successfully, the MG interface is in
normal state which indicates that the interface is working properly.
huawei(config)#display if-h248 all
-------------------------------------------------------------------------
MGID Trans State MGPort MGIP MGCPort MGCIP/DomainName
-------------------------------------------------------------------------
0 UDP Normal 2944 10.10.10.10 2944 200.200.200.200
-------------------------------------------------------------------------
Step 5 Configure IUA links.

In the sigtran mode, configure the Signaling Transport protocol stack. Add an IUA link set
first and then add IUA links.
huawei(config)#sigtran
huawei(config-sigtran)#iua-linkset add 1 mgid 0 jointly-work enable trafficmode
override iid-map 2 cs-mode client
huawei(config-sigtran)#iua-link add 0 1 1402 10.10.10.10 1404 200.200.200.200
jointly-work-with primary-mgc
huawei(config-sigtran)#quit
Step 6 Add ISDN PRA user.

huawei(config)#esl user
huawei(config-esl-user)#mgprauser add 0/1/0 0 1 interfaceid 0 terminalid 512
----End

Context
is recommended.

SingleFAN Solution
NOTE
Procedure

attack.
flapping.
effect.
flow.

SingleFAN Solution

----End

Context
time.
NOTE
Procedure

timedelay enable

SingleFAN Solution

ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
NOTE
ONUs.

SingleFAN Solution
ONU Splitter A
OLT
Splitter B
Tributary Fibers
Protection
Backbone Fibers
Protection
Active
Standby
lineprofile-id 10
protection scheme.

SingleFAN Solution
Active OLT
Splitter A
ONU
Splitter B
Standby OLT
Active
Standby
lineprofile-id 10
parenting
lineprofile-id 10
parenting
----End

This topic describes how to verify the PRA PBX service by testing calls.

SingleFAN Solution
Prerequisites
The PRA PBX access service has been deployed.
Procedure
Step 1 Test calls between users connected to the PRA PBX according to table 1.
Step 2 Test calls from a user connected to the PRA PBX to an MGC user according to table 1.
Step 3 Test calls from an MGC user to a user connected to the PRA PBX according to table 1.
Table 1-8 PRA PBX access service verification

Categ Test Calls Between Test Calls from a User Test Calls from an
ory Users Connected to Connected to the PRA MGC User to a User
the PRA PBX PBX to an MGC User Connected to the PRA
PBX
Prereq 1. User A and user B 1. User A accesses the 1. User A is a common

uisites access the network network through the MGC user and has
through the PRA PRA PBX and has been been registered.
PBX and both registered. 2. User B accesses the
users have been 2. User B is a common network through the
registered. MGC user and has been PRA PBX and has
2. User A and user B registered. been registered.
are idle. 3. User A and user B are 3. User A and user B are
idle. idle.
Test 1. User A calls user The same as that in the The same as that in the
proced B. "Test Calls Between Users "Test Calls Between Users
ure 2. User B answers Connected to the PRA Connected to the PRA
the call. Check the PBX" column PBX" column
call between user
A and user B.
3. User A releases
the call.
Expect 1. User B hears the The same as that in the The same as that in the
ed ringing tone. "Test Calls Between Users "Test Calls Between Users
result 2. The call is set up. Connected to the PRA Connected to the PRA
PBX" column PBX" column
3. The call is
released.
----End

SingleFAN Solution
1.8 Configuring Enterprise E1 Unified Access Service

(GPON)
ONUs transmit E1 signals of enterprises to OLTs in SAToP mode and OLTs are
interconnected with transmission equipment through E1 ports. In this manner, traditional
circuit switching services can be carried over GPON networks.
Service Requirement
l Existing SDH resources are utilized efficiently. In this way, carriers' existing investments
are protected and enterprise users in different regions are won.
l Services are received over optical fibers, reducing investment in copper cables between
enterprises and the SDH network.
l The standardized user-side ports facilitate deployment and maintenance.
As shown in Figure 1-17, the ONU accesses enterprise E1 service through standardized
hardware ports, and transmits data to the OLT over the GPON line after performing structure-
agnostic time division multiplexing over packet (SAToP) encapsulation on the service. After
receiving the signals, the OLT restores E1 signals and transmits the signals to the SDH
network.
l For carriers, with this networking, they can win enterprise users with GPON lines which
support long-distance transmission and high bandwidth. With the trend of fiber-in and
copper-out, deployment of GPON lines can reduce deployment costs of copper cables
and support service expansion.
l For enterprise users, with GPON access, they can reduce fees spent in leasing lines.
Figure 1-17 E1 access in SAToP mode
Enterprise OLT
ONU
E1/
E1 STM-1 SDH
TDM Splitter
E1 SAToP E1/STM-1
The following figure shows the configuration process for E1 enterprise private line.

SingleFAN Solution
Start
Adding ONUs to OLT
Service Ports on OLT
OLT Side
and ONUs
Configuring SAToP
Connections and Service
Ports
Policies
Configuring Network
Protection
Configuring SAToP
Connections ONU Side
Configuring Clock
Synchronization
Verifying Services
End

SingleFAN Solution

ONUs can be configured only after they are added to the OLT successfully.
Context
Data Plan

Item Data

Profile type: Fixed bandwidth and minimum delay
DBA bandwidth:
E1 access: 32 Mbit/s is recommended. (Each ONU accesses four E1
private lines and each line has a recommended DBA bandwidth of 8
Mbit/s)

T-CONT ID: 1

l ONU ID: 1
l SN: 3230313163902641
Procedure
1. Configure a DBA profile, and set the DBA bandwidth allocation mode for the GPON
port to minimum bandwidth delay.
For example, configure the DBA profile for 4-channel E1 private line.

to DBA profile 20

SingleFAN Solution
to T-CONT 1
12 to CVLAN 300
---------------------------------------------------------------------
F/S/P : 0/3/1
ONT-ID : 1
activated.
online.
state.
----End
Follow-up Procedure
ONU.

SingleFAN Solution

ONUs.
Data Plan

192.168.50.1/24

192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.

SingleFAN Solution

reachable.
----End
1.8.5 Configuring SAToP Connections and Service Ports

This topic describes how to configure a SAToP connection of the IP+UDP encapsulation type
and a service port to enable packets of enterprise to be encapsulated on ONUs and restored on
OLTs.
Prerequisites
Required hardware is available:
l Main control boards on the OLT: SCUN+CKMC/CKMD
l Upstream board on the OLT: EDTB (for E1 upstream transmission)
Context
Figure 1-18 shows SAToP encapsulation for enterprise E1 unified access service. As shown
in the following figure, after TDM signals are encapsulated in the IP+UDP format, an outer
VLAN tag and an Ethernet header are added to the TDM signals. Then the TDM signals
become a standard Ethernet packet that is transmitted on the PON line between the ONU and
OLT.
Figure 1-18 SAToP encapsulation

Enterprise OLT
ONU
E1/T1
SDH
T1 SAToP T1
E1 SAToP E1/STM-1
TDM TDM TDM TDM

UDP1 UDP1
IP1 IP1
VLAN VLAN
ETH ETH

SingleFAN Solution
Data Plan
Configurati Data
on Item
EDTB (OLT) Port: 0/5/0

Board IP address: 10.10.50.10
Board MAC address: dynamically obtained (remark 1)
Local UDP port number: 50048 (remark 2)
E1 port Board IP address: 10.10.50.20

(ONU) Board MAC address: dynamically obtained (remark 1)
UDP port number: 50048 (remark 2)
VLAN S-VLAN: 300
Remark 1: MAC address configuration modes (statically configured or dynamically obtained)

at two ends must be consistent to establish a SAToP connection. It is recommended that MAC
addresses be dynamically obtained, which facilitates configuration and maintenance.
Remark 2: The UDP port cannot be a port that is widely used in the industry and for specific
services. For example, port 80 is used for HTTP service. The dynamic and private ports are
recommended.
Procedure
Step 1 Configure EDTB board attributes.
Set the board working mode to SAToP.
huawei(config)#interface edt 0/5
huawei(config-if-edt-0/5)#board workmode satop
Configure the access mode and frame format.

l E1 access:
huawei(config-if-edt-0/5)#tdm access-mode E1
Configure the IP address of the E1 port on the EDTB board.

huawei(config-if-edt-0/5)#set ip-address 10.10.50.10
huawei(config-if-edt-0/5)#quit
Step 2 Create a SAToP connection.

Create TDM VCL 10.
l For E1 access, set the TDM VCL type to SAToP.
huawei(config)#tdm-vcl tdm-vcl-id 10 satop 0/5/0
Create a SAToP connection at the E1 port 0/5/0. Set S-VLAN to 300, local UDP port number
to 50048, remote IP address (the IP address of the E1 access board on the ONU) to
10.10.50.20, and remote UDP port number to 50048. The remote MAC address is obtained
dynamically.

SingleFAN Solution
NOTE
To create a SAToP connection, the local UDP port number must be consistent with the remote UDP port
number, that is, [ local-udp = portid of EDTB + Cardinal number (50048) ].
huawei(config)#cesop-connect tdm 10 vlan 300 local-udp 50048 remote-ip
10.10.50.20 remote-udp 50048
You can also create a SAToP connection by configuring the MAC address statically. If the
remote MAC address (the MAC address of the E1 access board on the ONU, which can be
queried by running the display cesop-mac-address command on the ONU) is 00e0-
fc01-0450, create a SAToP connection in static mode as follows:
huawei(config)#cesop-connect tdm 10 vlan 300 local-udp 50048 remote-mac
00e0-fc01-0450 remote-ip 10.10.50.20 remote-udp 50048
Step 3 (Optional) Configure attributes of the SAToP connection.

NOTE
The attributes of the SAToP connection on the OLT must be consistent with those on the ONU. Generally, use
the system default values.
l Run the cesop rtp command to configure whether the SAToP packet carries the RTP
header. The SAToP packet carries the RTP header by default.
l Run the cesop encap command to configure SSRC, payload type, and SN of the SAToP
packet. The default value of these parameters is 0.
l Run the cesop jitter-buffer command to configure the buffer depth of the SAToP packet.
The default buffer depth is 2000 μs.
l Run the cesop loadtime command to configure the load time of the SAToP packet. The
default load time is 125 μs.
l Run the cesop priority command to configure the priority of the SAToP packet. The
default priority is 7.
Step 4 Configure a service port.
Set the service port ID to 1, S-VLAN ID to 300, GEM port ID to 12, and user VLAN ID to
300. The ONU limits upstream and downstream traffic rates but the OLT does not. Therefore,
use default traffic profile 6.
The user VLAN must be the same as the upstream VLAN of the ONU.
huawei(config)#service-port 1 vlan 300 gpon 0/3/1 ont 1 gemport 12 multi-service
----End
1.8.6 Configuring ONU SAToP Connections

and a service VLAN to enable packets of base stations to be encapsulated on ONUs as
Ethernet packets and then forwarded based on VLANs and MAC addresses.

SingleFAN Solution
Data Plan
Configurati Data
on Item


VLAN S-VLAN: 300

recommended.
Procedure
Step 1 Configure a VLAN and add an upstream port to the VLAN.
Create the upstream VLAN 300, and add upstream port 0/0/1 to VLAN 300.
Step 2 Configure E1 port attributes.

Configure the IP address of TDM service board 0/1 as 10.10.50.20.
huawei(config-if-tdm-0/1)#set ip-address 10.10.50.20
Configure the board and port working mode and transmit clock.
l For E1 access, set the working mode to UDT and configure the transmit clock as the
system clock.
huawei(config-if-tdm-0/1)#tdm access-mode E1

Create TDM VCL 10.
Create a SAToP connection at TDM port 0/1/0. Set S-VLAN to 300, local UDP port number
to 50048, remote IP address (the IP address of the EDTB board on the OLT) to 10.10.50.10,
and remote UDP port number to 50048. The remote MAC address is obtained dynamically.

SingleFAN Solution

10.10.50.10 remote-udp 50048
NOTE
You can also create a SAToP connection by configuring the MAC address statically. If the remote MAC
address (the MAC address of the EDTB board on the OLT) is 0800-3E32-5310, create a SAToP connection in
static mode as follows:
0800-3E32-5310 remote-ip 10.10.50.10 remote-udp 50048

NOTE
----End

In this scenario, the E1 line clock can be used to achieve network-wide clock synchronization.
Prerequisites
The CKMC/CKMD clock daughter board has been installed on the SCU main control board.
Context
Configuration roadmap for clock synchronization:
1. The OLT traces the upstream E1 line clock of the EDTB board as the system clock.
2. The system clock is delivered to an ONU through optical paths of the GPON board.
4. The ONU E1 transmit clock is synchronized with the system clock of the ONU.
Procedure
l Configure a clock on the OLT.
a. Add a system clock source.
Configure the E1 line clock input from port 0/5/0 on the EDTB board as the system
clock 0. Set the priority to 0 (highest priority).
b. Query configurations and the status of the system clock source.

SingleFAN Solution
-------------------------------------------------------------------------
-----
Selected
-------------------------------------------------------------------------
-----
0 H802EDTB 0/5/0 E1 Normal 0 ---
YES
-------------------------------------------------------------------------
-----
Run the display clock mode command to query the clock working mode. Ensure
that the clock daughter board works in tracing mode.
l Configure a clock on the ONU.

a. Configure the GPON line clock as the system clock.
The system clock of the OLT is delivered to the ONU through the GPON port on
the OLT, achieving clock synchronization between the OLT and the ONU.
i. Run the clock source command to configure the clock recovered from the
GPON upstream port as the system clock of the ONU.
ii. Run the clock priority command to configure the priority of the clock source.
b. Configure the system clock as the transmit clock for an E1 port.

i. Run the interface tdm command to enter the E1 port configuration mode.
ii. Run the tx clock or port portid udt system command to configure the system
clock as the transmit clock of the port.
iii. Run the display port state command to query the transmit clock of the E1
port.
---------------------------------------
Port : 0
State : normal
Mode : UDT
Code : HDB3
Looptype : -
Timeslot : -
Clock : system
CRC4 : -
Signaling : -
ESF : -
Impedance : 120 Ohm
---------------------------------------

SingleFAN Solution
Run the display clock source command to query configurations and the status of
the system clock source.
---------------------------------------------------------------
---------------------------------------------------------------
1 NO -- -/ -/ - --- --- ---
2 NO -- -/ -/ - --- --- ---
3 NO -- -/ -/ - --- --- ---
4 NO -- -/ -/ - --- --- ---
5 NO -- -/ -/ - --- --- ---
6 NO -- -/ -/ - --- --- ---
7 NO -- -/ -/ - --- --- ---
8 NO -- -/ -/ - --- --- ---
9 NO -- -/ -/ - --- --- ---
---------------------------------------------------------------
----End

Context
is recommended.
NOTE
Procedure

attack.

SingleFAN Solution

flapping.
effect.
flow.
----End
1.8.9 Configuring Network Protectio

The base station access service has high requirements on reliability. Therefore, network
protection solutions must be configured in the upstream and downstream directions.

SingleFAN Solution
Context
The protection solutions supported in this scenario are Type B protection and Type C single-
homing protection.
Procedure
ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
NOTE
ONUs.

SingleFAN Solution
ONU Splitter A
OLT
Splitter B
Tributary Fibers
Protection
Backbone Fibers
Protection
Active
Standby
lineprofile-id 10
----End

Prerequisites

SingleFAN Solution
Networking
ONU OLT
loopback
E1

Procedure
NOTE
Step 2 Use the E1 line tester to send packets for the test.
----End
Follow-up Procedure
l Remote loopback on the OLT EDTB board
l Local loopback on the OLT EDTB board

SingleFAN Solution

ack
Mode

tester
edt 0/5
the the EDTB board Remote loopback
huawei(config-if-
EDTB on the OLT. This edt-0/5)#loopback 0
huawei(config-if-
whether the edt-0/5)#undo loopback 0
service from the
EDTB board to
the network-side
channel is
normal.

tester
E1
edt 0/5
the EDTB board on Local loopback
huawei(config-if-
EDTB the OLT. This edt-0/5)#loopback 0 local
edt-0/5)#undo loopback 0
whether the link
between the
EDTB board
and the E1 port
on the ONU is
normal.

tester
tdm 0/1
huawei(config-if-
ONU loopback checks
whether the link
between the E1
port on the ONU
and the EDTB
board on the
OLT is normal.

tester E1 tdm 0/1
Remote loopback
huawei(config-if-
whether the link
between the
ONU and user
terminal is
normal.

SingleFAN Solution
1.9 Configuring Enterprise E1 Unified Access Service

(OLT Cascading, GPON)
ONUs access enterprise TDM service in E1 access mode, and transmits the data to the SDH
network in OLT cascading mode over the GPON network which supports long-distance
transmission and high bandwidth. In this way, uniform deployment of E1 service is achieved.
Service Requirement
l Existing SDH resources are utilized efficiently. In this way, carriers' existing investments
are protected and enterprise users in different regions are won.
l Services are received over optical fibers, reducing investment in copper cables between
enterprises and the SDH network.
l The standardized user-side ports facilitate deployment and maintenance.
As shown in Figure 1-22, a carrier's SDH network is migrated gradually. In a city, there are
only some nodes (for example, OLT_A in the following figure) can transmit signals upstream
to the SDH network through STM-1 ports, and other nodes (for example, OLT_B in the
following figure) must access SDH resources through GE/10GE ports. In this scenario,
ONU_B accesses the E1 service in SAToP mode, and transmits the service to the OLT at the
local site (OLT_B) over the GPON line. OLT_B transparently transmits the service to another
OLT with SDH resources (OLT_A) through GE/10GE ports.
l For carriers, with this networking, they can win enterprise users who have no SDH
resources with GPON lines which support long-distance transmission and high
bandwidth. With the trend of fiber-in and copper-out, deployment of GPON lines can
reduce deployment costs of copper cables and support service expansion.
l For enterprise users, with GPON access, they can reduce fees spent in leasing lines.
Figure 1-22 E1 access in SAToP mode (OLT cascading)

OLT_A
E1/
E1 STM-1 SDH
TDM Splitter
OLT_B L2
Enterprise
10 E/
GE
ONU
G
E1
TDM Splitter
E1/
E1 SAToP
STM-1

SingleFAN Solution

The following figure shows the configuration process for the E1 unified access service (OLT
cascading).
OLT_A OLT_B ONU
Start Start Start
Configure cascading Configuring ONU

Adding ONUs to OLT
with OLT_B SAToP Connections
Configuring SAToP Configuring

Connections between Management and
OLT_A and ONU Service Channel
Configuring Clock
Synchronization
End
Functions of different network element are listed in the table below.
Network Functions
element
OLT_A 1. In the downstream direction, creates SAToP connections with ONU_B; in

the upstream direction, restores E1 signals and transmits the signals to the
SDH network.
2. Cascaded with OLT_B and transmits clock synchronization information
downstream.
OLT_B 1. Transmits SAToP-encapsulated packets in GEM frames over the GPON

line.
2. Transmits SAToP packets to OLT_A in Ethernet mode for decapsulation.
3. Transmits clock synchronization information to ONU_B.
ONU_B 1. Access the E1 private line service.

2. Create the SAToP connection between ONU_B and OLT_A.
3. Transmits SAToP packets to OLT_B by PON line.
4. Transmits clock synchronization information to enterprise.

SingleFAN Solution
1.9.3 Configure OLT_A cascading with OLT_B
Prerequisites
Required hardware for OLT_A is ready.
l Control board: SCUN+CKMC/CKMD
l GPON service board: GPBD
l Upstream board: EDTB
l Cascaded service board:
– GE port: GICK or OPGD
– 10GE port: X2CS
Data Plan
Table 1-10 provides the key data plan.
Table 1-10 Key data plan for OLT_A
Item Data Remarks
OPGD Port: 0/2/1 Assume that OLT_A is cascaded with OLT_B using the
OPGD board. Then you need to set the network role of the
OPGD board to cascade.
VLA Inband management To telnet to another OLT or ONU from the OLT and then
N ID VLAN ID: 8 configure the OLT or ONU, you must configure the
and IP Inband management inband management VLANs and IP addresses of the OLT
addres IP address: on the OLT.
s 192.168.50.30/24 If the management IP address and the IP address of
OLT_B or ONU_B are not in the same network segment,
you also need to configure routes.
Procedure
Step 1 Configure the management VLAN and IP address.
Create management VLAN 8, and set the management IP address to 192.168.50.30 and
subnet mask to 255.255.255.0.
Step 2 Configure cascading with OLT_B.

Cascade OLT_A and OLT_B through GE port 0/2/1 on the OPGD board. Set the port attribute
to cascade, and add the cascading port to VLAN 300.
huawei(config)#interface opg 0/2
huawei(config-if-opg-0/2)#network-role cascade
huawei(config-if-opg-0/2)#quit

SingleFAN Solution

----End
1.9.4 Configuring SAToP Connections between OLT_A and ONU
Data Plan
Configurati Data
on Item


VLAN S-VLAN: 300

recommended.
Procedure
Step 1 Configure EDTB board attributes.
Set the board working mode to SAToP.

huawei(config-if-edt-0/5)#board workmode satop
Configure the access mode and frame format.

l E1 access:
huawei(config-if-edt-0/5)#tdm access-mode E1
Configure the IP address of the E1 port on the EDTB board.

huawei(config-if-edt-0/5)#set ip-address 10.10.50.10
huawei(config-if-edt-0/5)#quit
Create TDM VCL 10.

SingleFAN Solution

Create a SAToP connection at the E1 port 0/5/0. Set S-VLAN to 300, local UDP port number
to 50048, remote IP address (the IP address of the E1 access board on the ONU) to
10.10.50.20, and remote UDP port number to 50048. The remote MAC address is obtained
dynamically.
NOTE
To create a SAToP connection, the local UDP port number must be consistent with the remote UDP port
number, that is, [ local-udp = portid of EDTB + Cardinal number (50048) ].
10.10.50.20 remote-udp 50048
You can also create a SAToP connection by configuring the MAC address statically. If the
remote MAC address (the MAC address of the E1 access board on the ONU, which can be
queried by running the display cesop-mac-address command on the ONU) is 00e0-
fc01-0450, create a SAToP connection in static mode as follows:
00e0-fc01-0450 remote-ip 10.10.50.20 remote-udp 50048

NOTE
----End
1.9.5 Adding ONUs to OLT_B

ONUs can be configured only after they are added to the OLT successfully.

SingleFAN Solution
Data Plan
Item Data

Profile type: Fixed bandwidth and minimum delay
DBA bandwidth:
E1 access: 32 Mbit/s is recommended. (Each ONU accesses four E1
private lines and each line has a recommended DBA bandwidth of 8
Mbit/s)

T-CONT ID: 1

l ONU ID: 1
l SN: 3230313163902641
Procedure
1. Configure a DBA profile, and set the DBA bandwidth allocation mode for the GPON
port to minimum bandwidth delay.
For example, configure the DBA profile for 4-channel E1 private line.

to DBA profile 20
to T-CONT 1
12 to CVLAN 300


SingleFAN Solution


---------------------------------------------------------------------
F/S/P : 0/3/1
ONT-ID : 1
activated.
online.
state.
----End
Follow-up Procedure
ONU.

SingleFAN Solution
1.9.6 Configuring Management and Service Channel on OLT_B

and ONU
After the management service ports are added, you can log in to the ONUs on the OLT and
configure the ONUs. After the GPON service port is added, E1 traffic stream is able to
transmitted upstream to OLT_B.
Prerequisites
Required hardware for OLT_B (cascading) is ready.
l Control board: SCUN+CKMC/CKMD
l GPON service board: GPBD
l Upstream board:
– GE port: GICK
– 10GE port: X2CS
Data Plan
Item Data
Management VLAN and Management VLAN ID: 8

management IP address for OLT Management VLAN type: smart
In-band management IP address: 192.168.50.1/24
Service VLAN 300
Management VLAN and Management VLAN ID: 8

management IP address for ONU Management VLAN type: smart
In-band management IP address: 192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

SingleFAN Solution
profile 6.
reachable.
Step 5 Configure the upstream port.
Add upstream port 0/19/0 (on the GICK board) to VLAN 100.
Step 6 Configure the GPON service port.

Set S-VLAN ID to 300, GEM port ID to 12, and C-VLAN ID to 300. Rate limit for upstream
and downstream packets is performed on the ONU instead of on the OLT. Therefore, use
traffic profile 6 (default). To limit the rate of the service port, run the traffic table ip
command to add a traffic profile and bind it to the service port.
The C-VLAN must be the same as the upstream VLAN of the ONU.
----End
1.9.7 Configuring ONU SAToP Connections

and a service VLAN to enable packets of base stations to be encapsulated on ONUs as
Ethernet packets and then forwarded based on VLANs and MAC addresses.
Data Plan
Configurati Data
on Item


VLAN S-VLAN: 300

SingleFAN Solution

recommended.
Procedure
Step 1 Configure a VLAN and add an upstream port to the VLAN.
Create the upstream VLAN 300, and add upstream port 0/0/1 to VLAN 300.
Step 2 Configure E1 port attributes.
Configure the IP address of TDM service board 0/1 as 10.10.50.20.

huawei(config-if-tdm-0/1)#set ip-address 10.10.50.20
Configure the board and port working mode and transmit clock.
l For E1 access, set the working mode to UDT and configure the transmit clock as the
system clock.
huawei(config-if-tdm-0/1)#tdm access-mode E1
Create TDM VCL 10.

Create a SAToP connection at TDM port 0/1/0. Set S-VLAN to 300, local UDP port number
to 50048, remote IP address (the IP address of the EDTB board on the OLT) to 10.10.50.10,
and remote UDP port number to 50048. The remote MAC address is obtained dynamically.
10.10.50.10 remote-udp 50048
NOTE
You can also create a SAToP connection by configuring the MAC address statically. If the remote MAC
address (the MAC address of the EDTB board on the OLT) is 0800-3E32-5310, create a SAToP connection in
static mode as follows:
0800-3E32-5310 remote-ip 10.10.50.10 remote-udp 50048

NOTE

SingleFAN Solution
----End
Context
Configuration concept for clock synchronization:
1. OLT_A traces the upstream E1 line clock of the EDTB board as the system clock.
2. OLT_B Obtains the system clock by GICK/X2CS boards in synchronous Ethernet mode.
4. The Tx clock of ONU is synchronized to the system clock of the ONU.
Data Plan
System Clock source Description
clock
OLT_A E1 line clock: 0/5/0 OLT_A Obtains E1 line clock from SDH as the
system clock, and then transmits it to the cascading
OLT_B over GE/10GE interface.
OLT_B Synchronous Ethernet OLT_B Obtains the system clock in synchronous

line clock: 0/19/0 Ethernet mode. The clock is transmitted to the
ONU over the GPON line.
ONU GPON line clock: ONU uses the line clock of the GPON upstream
0/0/1 port as the system clock.
Procedure
Step 1 Configure a clock on OLT_A.
1. Add a system clock source.
Configure the E1 line clock input from port 0/5/0 on the EDTB board as the system
clock 0. Set the priority to 0 (highest priority).
2. Query configurations and the status of the system clock source.

SingleFAN Solution
------------------------------------------------------------------------------
Selected
------------------------------------------------------------------------------
0 H802EDTB 0/5/0 E1 Normal 0 ---
YES
------------------------------------------------------------------------------
Run the display clock mode command to query the clock working mode. Ensure that the
clock daughter board works in tracing mode.
Step 2 Configure a clock on OLT_B.

Obtain the system clock through the GICK board in synchronous Ethernet mode. The clock is
transmitted to the ONU over the GPON line.
Step 3 Configure a clock on the ONU.

1. Configure the GPON line clock as the system clock.
The system clock of the OLT is delivered to the ONU through the GPON port on the
OLT, achieving clock synchronization between the OLT and the ONU.
a. Run the clock source command to configure the clock recovered from the GPON
upstream port as the system clock of the ONU.
b. Run the clock priority command to configure the priority of the clock source.
2. Configure the system clock as the transmit clock for an E1 port.

a. Run the interface tdm command to enter the E1 port configuration mode.
b. Run the tx clock or port portid udt system command to configure the system clock
as the transmit clock of the port.
c. Run the display port state command to query the transmit clock of the E1 port.
---------------------------------------
Port : 0
State : normal
Mode : UDT
Code : HDB3
Looptype : -
Timeslot : -
Clock : system
CRC4 : -
Signaling : -
ESF : -
Impedance : 120 Ohm
---------------------------------------

SingleFAN Solution
3. Query configurations and the status of the system clock source.

Run the display clock source command to query configurations and the status of the
system clock source.
---------------------------------------------------------------
---------------------------------------------------------------
1 NO -- -/ -/ - --- --- ---
2 NO -- -/ -/ - --- --- ---
3 NO -- -/ -/ - --- --- ---
4 NO -- -/ -/ - --- --- ---
5 NO -- -/ -/ - --- --- ---
6 NO -- -/ -/ - --- --- ---
7 NO -- -/ -/ - --- --- ---
8 NO -- -/ -/ - --- --- ---
9 NO -- -/ -/ - --- --- ---
---------------------------------------------------------------
----End

Prerequisites
Networking
ONU OLT
loopback
E1

Procedure
NOTE
Step 2 Use the E1 line tester to send packets for the test.

SingleFAN Solution
----End
Follow-up Procedure
l Remote loopback on the OLT EDTB board
l Local loopback on the OLT EDTB board

ack
Mode

tester
edt 0/5
the the EDTB board Remote loopback
huawei(config-if-
EDTB on the OLT. This edt-0/5)#loopback 0
huawei(config-if-
whether the edt-0/5)#undo loopback 0
service from the
EDTB board to
the network-side
channel is
normal.

tester
E1
edt 0/5
the EDTB board on Local loopback
huawei(config-if-
EDTB the OLT. This edt-0/5)#loopback 0 local
edt-0/5)#undo loopback 0
whether the link
between the
EDTB board
and the E1 port
on the ONU is
normal.

SingleFAN Solution

ack
Mode

tester
tdm 0/1
huawei(config-if-
ONU loopback checks
whether the link
between the E1
port on the ONU
and the EDTB
board on the
OLT is normal.

tester E1 tdm 0/1
Remote loopback
huawei(config-if-
whether the link
between the
ONU and user
terminal is
normal.


Huawei OLT General Config

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei OLT General Config

Uploaded by

Copyright:

Available Formats

SingleFAN Solution

FTTO Configuration Guide (Large-

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2016-12-16) Huawei Proprietary and Confidential i

About This Document

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 01 (2016-12-16) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation which, if not

NOTE Calls attention to important information, best practices and

Updates in Issue 01 (2016-12-16)

Issue 01 (2016-12-16) Huawei Proprietary and Confidential iii

About This Document.....................................................................................................................ii

Issue 01 (2016-12-16) Huawei Proprietary and Confidential iv

1.6.4 Configuring Management Service Ports on OLT and ONUs.................................................................................... 51

Issue 01 (2016-12-16) Huawei Proprietary and Confidential v

1 FTTO Configuration (Large-sized

About This Chapter

1.1 FTTO (Large-sized Enterprise Access) Configuration Summary

Issue 01 (2016-12-16) Huawei Proprietary and Confidential 1

Issue 01 (2016-12-16) Huawei Proprietary and Confidential 2

1.1 FTTO (Large-sized Enterprise Access) Configuration

Service Scenario ONU Supported Service

Layer 2 Interoperation Service Between MA5612, MA5694, LAN

Enterprise DDN Private Line Access MA5612, MA5698, E1

Enterprise IP PBX Private Line Access MA5612, MA5694, LAN

Enterprise PRA PBX Private Line Access MA5612 PRA E1

Enterprise E1 Unified Access Service MA5612 E1

Enterprise E1 Unified Access Service MA5612 E1

1.2 Overview of Enterprise Access Service

Issue 01 (2016-12-16) Huawei Proprietary and Confidential 3

Network Diagram of Enterprise Access Service

Enterprise Side Access Side Network Side

IP PBX IP private branch exchange (PBX) is an IP-based enterprise telephone

Issue 01 (2016-12-16) Huawei Proprietary and Confidential 4

Protocol converter Protocol converter is a device used to convert standard or proprietary

PON A passive optical network (PON) uses a point-to-multipoint (P2MP)

ODN The ODN is composed of passive optical components, such as optical

SDH Synchronous digital hierarchy (SDH) is a transmission scheme that

Issue 01 (2016-12-16) Huawei Proprietary and Confidential 5

NGN/IMS A next generation network (NGN) is a network that uses softswitches

1.3 Principle of Planning Data for Enterprise Access

1.3.1 Principle of Equipment Management Data Plan

Management VLAN Planning

Equipment A management IP address is allocated to each OLT/ONU.

Enterprises DDN No IP addresses need to be planned because ONUs access the

Issue 01 (2016-12-16) Huawei Proprietary and Confidential 6

Scenario IP Address Planning

Enterprise E1/T1 IP addresses are planned as follows:

1.3.2 Principle of VLAN Data Plan

VLAN and VLAN Translation Policy

Enterprises Use a reserved C-VLAN N/A N/A

Issue 01 (2016-12-16) Huawei Proprietary and Confidential 7

Scenario VLAN Planning VLAN Translation

Enterprise IP Single VLAN tag: ONUs 1. Different user The OLT

(Recommended) Double 1. Different user The OLT adds an

Issue 01 (2016-12-16) Huawei Proprietary and Confidential 8

Scenario VLAN Planning VLAN Translation

Enterprise PRA (Recommended) Single ONUs access the The OLT

Double VLAN tags ONUs access the The OLT adds an