AN5116-06B AN5516-06 AN5516-04 Optical Line Terminal Equipment CLI Configuration Guide (Version A) PDF

AN5116-06B/AN5516-06/
AN5516-04
Optical Line Terminal Equipment
CLI Configuration Guide

Version: A
Code: MN000003436
FiberHome Telecommunication Technologies Co., Ltd.
December 2017
Thank you for choosing our products.
We appreciate your business. Your satisfaction is our goal.

We will provide you with comprehensive technical support
and after-sales service. Please contact your local sales
representative, service representative or distributor for any
help needed at the contact information shown below.
Fiberhome Telecommunication Technologies Co., Ltd.
Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

Zip code: 430073
Tel: +6 03 7960 0860/0884 (for Malaysia)
+91 98 9985 5448 (for South Asia)
+593 4 501 4529 (for South America)
Fax: +86 27 8717 8521
Website: http://www.fiberhomegroup.com
Legal Notice
are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

(Hereinafter referred to as FiberHome)
All brand names and product names used in this document are used for
identification purposes only and are trademarks or registered trademarks
of their respective holders.
All rights reserved
No part of this document (including the electronic version) may be

reproduced or transmitted in any form or by any means without prior
written permission from FiberHome.
Information in this document is subject to change without notice.
Contents
1 Documentation Guide .....................................................................................1
2 Overview of the Configuration Flow .................................................................2
3 Logging into the Device...................................................................................3
3.1 Introduction to the Login Mode ..........................................................4
3.2 Logging into Hyper Terminal..............................................................4
3.3 Login Through Telnet ........................................................................6
4 Configuring the Management Channel ............................................................9
4.1 Network Planning ...........................................................................10
4.2 Planning Data ................................................................................. 11
4.3 Configuring the IP Address for In-Band Management.......................12
4.4 Configuring the IP Address for Out-of-Band Management ................12
4.5 Configuring Static Routing...............................................................12
5 Authorizing Card and ONU............................................................................14
5.1 Authorizing a Card ..........................................................................15
5.2 Authorizing an ONU ........................................................................15
6 Service Configuration....................................................................................18
6.1 Configuring Voice Services Based on H.248....................................19
6.1.1 Configuration Rules ..........................................................19

6.1.2 Network Planning .............................................................19
6.1.3 Configuration Flow............................................................20
6.1.4 Planning Data for the OLT .................................................21
6.1.5 Planning Data for the ONU................................................24
6.1.6 Procedures of Configuring Voice Services Based on
H.248 ...............................................................................25
6.2 Configuring Voice Services Based on SIP .......................................26

6.2.6 Procedures of Configuring Voice Services Based on SIP ...31
6.3 Configuring Data Services ..............................................................32

6.3.6 Procedures of Configuring Data Services ..........................40
6.4 Configuring Multicast Services ........................................................41

6.4.6 Procedures of Configuring Multicast Services....................47
6.5 Configuring the Wi-Fi Access Service..............................................48

6.5.5 Procedures of Configuring the Wi-Fi Access Service .........54
7 Function Configuration..................................................................................55
7.1 Configuring the VEIP Function ........................................................56

7.1.5 Procedures of Configuring the VEIP Service......................61
7.2 Configuring the DHCP Function ......................................................64

7.2.2 Configuring DHCP Relay with OLT Equipment Serving as
Proxy................................................................................65
7.2.3 Configuring DHCP Relay with OLT Equipment Serving as
Both Proxy and Gateway ..................................................70
7.2.4 Configuring DHCP Option60 .............................................75
7.2.5 Configuring DHCP Server .................................................82
7.2.6 Configuring DHCP Snooping.............................................87
7.3 Configuring the ARP Proxy Function ...............................................91

7.3.2 Configuring ARP Proxy in the Same-VLAN and Same-
network Segment Application............................................91
7.3.3 Configuring ARP Proxy in the Cross-VLAN and Same-
network Segment Application............................................95
7.3.4 Configuring ARP Proxy in the Same-VLAN and Multi-network
Segment Application.........................................................98
7.3.5 Configuring ARP Proxy in the Cross-VLAN and Multi-network
Segment Application.......................................................102
7.4 Configuring QoS Functions ...........................................................106
7.4.1 Configuration Rules ........................................................106

7.4.2 Network Planning ...........................................................106
7.4.3 Configuration Flow..........................................................107
7.4.4 Planning Data .................................................................108
7.4.5 Procedures of Configuring QoS Functions....................... 110
7.5 Configuring the LACP Function ..................................................... 111
7.5.1 Network Planning ........................................................... 111

7.5.2 Configuration Flow.......................................................... 112
7.5.3 Planning Data ................................................................. 113
7.5.4 Procedures of Configuring the LACP Function................. 114
7.6 Configuring the MSTP Function..................................................... 115
7.6.1 Network Planning ........................................................... 115

7.6.2 Configuration Flow.......................................................... 116
7.6.3 Planning Data ................................................................. 117
7.6.4 Procedures of Configuring the MSTP Function ................ 119
7.7 Configuring the RADIUS Function .................................................120

7.7.2 Planning Data .................................................................121
7.7.3 Procedures of Configuring the RADIUS Function.............122
7.8 Configuring the Tacacs+ Function .................................................122

7.8.2 Network Planning ...........................................................123
7.8.4 Planning Data .................................................................125
7.8.5 Procedures of Configuring the Tacacs Function ...............125
7.9 Configuring the Subscriber Line Identification Function ..................127

7.9.3 Planning Data .................................................................129
7.9.4 Procedures of Configuring the Subscriber Line Identification
Function .........................................................................129
1 Documentation Guide
Document Orientation
The CLI Configuration Guide mainly introduces how to start and configure services
for the AN5116-06B/AN5516-06/AN5516-04 in the CLI mode.
Intended Readers
u Commissioning engineers
u Operation and maintenance engineers
Version Information
Version Description
Matching with the command line system of version 2016

A Q1, and applicable to the OLT equipment of the version V4.
0 or above.
Related Documentation
Document Description
This manual introduces the commonly used commands for

AN5116-06B/AN5516-
the AN5116-06B/AN5516-06/AN5516-04, covering
06/AN5516-04 Command Line
command functions, command formats, parameter
Reference
descriptions, command examples, and result descriptions.
Version: A 1
2 Overview of the Configuration Flow
The AN5116-06B/AN5516-06/AN5516-04 can provide voice, data and multicast

services and functions such as VEIP and DHCP. Figure 2-1 shows the configuration
flow.
Figure 2-1 Overview of the Configuration Flow
2 Version: A
3 Logging into the Device
Introduction to the Login Mode
Logging into Hyper Terminal
Login Through Telnet
Version: A 3
AN5116-06B/AN5516-06/AN5516-04 Optical Line Terminal Equipment CLI Configuration Guide
3.1 Introduction to the Login Mode
Users can log into the CLI network management system either by Hyper Terminal or
by Telnet.
3.2 Logging into Hyper Terminal
Connect the PC to the CONSOLE port of the core switch card properly with the
serial port line. Log into the AN5116-06B/AN5516-06/AN5516-04 through the hyper
terminal. The login operation is implemented on the PC as follows:
1. Click the Start menu on the desktop, and select All Programs→Accessories
→Telecom→Hyper Terminal to bring up the Connection Description dialog
box.
Note:
The Windows XP operating system is used as an example here.
2. In the Connection Description dialog box, enter the name of the object to be
connected and select an icon for it.
3. Click OK, and the Connect To dialog box appears.
4. In the Connect To dialog box, select the computer's COM1 port to be

connected to the CONSOLE port of the core switch card through the serial port
line.
4 Version: A
5. Click OK, and the COM1 Properties dialog box appears.
6. In the COM1 Properties dialog box, click the Restore Defaults button.
7. Click OK to start up the CONSOLE.
Version: A 5
8. Press the <Enter> key, and enter the user name and password to log into the
CLI network management system.
Login:GEPON
// The default user is administrator, and the user name is "GEPON".
Password:*****
// The initial password is always "GEPON".
User>enable
// In the read-only mode, users can enter the management mode via the command "enable".
Password:*****
// The initial password of the administrator account is "GEPON".
Admin#
// After the prompt "Admin＃" appears, users can type command lines to operate on the AN5116-06B/
AN5516-06/AN5516-04.
Note:
u If the command prompt is User, the system is in the common user

mode; if the command prompt is Admin#, the system is in the
administrator mode.
u The user name is case insensitive, while the password is case

sensitive.
Caution:
Users should memorize their passwords and keep them secret. Regularly
changing passwords is recommended.
9. Select File→Save from the menu bar of the CONSOLE window to save the
configurations for the CONSOLE.
3.3 Login Through Telnet
When logging into the equipment through a hyper terminal, you can configure the
out-of-band management IP address and in-band management IP address for the
equipment. After the aforesaid configuration, you can log into the equipment though
Telnet. The operation procedures are described as follows:
1. Click the Start menu on the desktop, and select Run to bring up the Run dialog
box.
6 Version: A
Note:
The Windows XP operating system is used as an example here.
2. Enter telnet x.x.x.x in the Run dialog box.
Note:
x.x.x.x is the out-of-band management IP address for the equipment

(configured under the directory of Admin) or the in-band management IP
address (configured as the IP address of the management VLAN under
the directory of Service).
3. Click OK to bring up the Telnet x.x.x.x window.
4. Enter the user name and the password to log into the CLI network management
system.
Version: A 7
Login:GEPON
// The default user is administrator, and the user name is "GEPON".
Password:*****
// The initial password is always "GEPON".
User>enable
// In the read-only mode, users can enter the management mode via the command "enable".
Password:*****
// The initial password of the administrator account is "GEPON".
Admin#
// After the prompt "Admin＃" appears, users can type command lines to operate on the AN5116-06B/
AN5516-06/AN5516-04.
Note:
u If the command prompt is User, the system is in the common user

mode; if the command prompt is Admin#, the system is in the
administrator mode.
u The user name is case insensitive, while the password is case

sensitive.
Caution:
Users should memorize their passwords and keep them secret. Regularly
changing passwords is recommended.
8 Version: A
4 Configuring the Management
Channel
After logging into the AN5116-06B/AN5516-06/AN5516-04 through the Console,

you need to configure the management channel for the equipment, so that the
equipment can be configured and managed remotely.
Network Planning
Planning Data
Configuring the IP Address for In-Band Management
Configuring the IP Address for Out-of-Band Management
Configuring Static Routing
Version: A 9
4.1 Network Planning

Service Planning
Assign the IP address 111.111.111.222/255.255.255.0 to the AN5116-06B/AN5516-

06/AN5516-04. The IP address of the network management server is
111.111.111.100/255.255.255.0. The network management server needs to be
connected with the to-be-managed AN5116-06B/AN5516-06/AN5516-04 through
the gateway with the IP address 111.111.111.111 to enable in-band management.
Network Scenario
Figure 4-1 shows the network diagram. The AN5116-06B/AN5516-06/AN5516-04

and the network management server are connected respectively to different ports of
the same gateway device. The management information is forwarded via the
gateway device to achieve in-band management.
Figure 4-1 Network Diagram for In-band Management
10 Version: A
4 Configuring the Management Channel
Hardware Configuration
Below are the hardware components required for configuring the management
channel of the AN5116-06B/AN5516-06/AN5516-04:
u Fan card
u Core switch card and uplink card (AN5116-06B/ AN5516-06)
u Switch uplink card (AN5516-04)
u Matching PDP
4.2 Planning Data
Table 4-1 lists the planning data for configuring the in-band management IP
address.
Table 4-1 Configuring the IP Address for In-Band Management
Procedure Parameter Parameter Description Example
Name of the management

name <name> ccs
VLAN
vid <1-4085> VLAN ID 888
Configuring the <portlist> Uplink port 19:2
management VLAN and Tag processing mode for the
port port
u Untagged: tags are
[untagged|tagged] tagged
stripped.
u Tagged: tags are not
stripped.
Configuring the <A.B.C.D/M> IP address and mask bits 111.111.111.222/24

management IP address Gateway. This parameter is
{<A.B.C.D>}*1 111.111.111.111
and gateway optional.
Table 4-2 lists the planning data for configuring the out-of-band management IP
address.
Version: A 11
Table 4-2 Configuring the IP Address for Out-of-Band Management
Configuring the IP debugip <A.B.C.D> Out-of-band IP address 10.190.40.15

address for out-of-band
mask <A.B.C.D> Mask 255.255.255.0
management
Table 4-3 lists the planning data for configuring static routing.
Table 4-3 Configuring Static Routing
destination <A.B.C.D> Destination network segment 10.190.40.15

Configuring static
gateway <A.B.C.D> Gateway 10.190.40.1
routing
mask <A.B.C.D> Mask 255.255.255.0
4.3 Configuring the IP Address for In-Band

Management
Configure the command parameters according to Planning Data.
1. Configure the IP address for in-band management.

Admin\service#set manage vlan name ccs vid 888 inputport 19:2 tagged
Admin\service#set manage vlan name ccs ip 111.111.111.222/24 111.111.111.111
Admin\service#
4.4 Configuring the IP Address for Out-of-Band

Management
1. Configure the IP address for out-of-band management.

Admin#set debugip 10.190.40.15 mask 255.255.255.0
Admin#
4.5 Configuring Static Routing
12 Version: A
4 Configuring the Management Channel
1. Configure the static routing.

Admin\protocol#set static–route destination–ip 10.190.40.15 mask 255.255.255.0 nexthop
10.190.40.1 metric 0
Admin\protocol#
Version: A 13
5 Authorizing Card and ONU
Authorizing a Card
Authorizing an ONU
14 Version: A
5.1 Authorizing a Card
1. Authorize a card.
Authorize all the cards.

Admin#set card_all_auth
Admin#
2. Authorize a specified card.
Authorize the GC8B card in Slot 14.

Admin#set card_auth slot 14 type gc8b
Success to set 14 slot as type gc8b
Admin#
3. Authorize a specified card.
Authorize the EC8B card in Slot 15.

Admin#set card_auth slot 15 type ec8b
Success to set 15 slot as type ec8b
Admin#
5.2 Authorizing an ONU
1. Configure the authentication mode for a PON port.
Set the authorization mode for PON port 1 in Slot 13, so that the port is
authenticated by physical identifier / logical identifier (with password) / physical
identifier and password.
Admin\card#set pon_auth slot 13 pon 1 mode phy_id
set pon authorizable mode ok!
Admin\card#
Table 5-1 Authentication Modes for PON Ports
Parameter Description
phy_id Physical identifier authorization
phy_id+psw Physical identifier plus password authentication
password Password authentication
loid+psw Logical identifier plus password authentication
Version: A 15
Table 5-1 Authentication Modes for PON Ports (Continued)
Parameter Description
no_auth No authentication
loid Logical identifier authentication (without password)
Physical / logical identifier (without password) hybrid

phy_id/loid
authentication
phy_id/psw Physical identifier / password hybrid authentication
2. Query the authentication mode for the PON port.
View the authentication mode for PON Port 1 of Slot 13.

Admin\card#show pon_auth select slot 13 pon 1
slot 13 pon 1 auth mode is physical id or logical id or physical password.
Admin\card#
3. Configure the ONU white list.
Configure the ONU white list for PON port 1 of Slot 13. The logical SN of the
ONU is loid13010003, the password is null, and the ONU type is 5506-04-b2.
Admin\onu#set whitelist logic_sn sn loid13010003 password null action add slot 13 pon 1
onu null type 5506-04-b2
set onu whitelist ok!
Admin\onu#
4. Delete the ONU white list.
Delete the ONU under PON port 1 of Slot 13. The logical SN of the ONU is
loid13010003, and the password is null.
Admin\onu#set whitelist logic_sn sn loid13010003 password null action del
Admin\onu#
5. Delete the ONU authorization table. This operation is supported only

when the ONU is in the non-authorization mode or reserved authorization
state.
In the non-authorization mode, delete the ONU5 under PON port 1 of Slot 13.
Admin\onu#set unauthorization slot 13 pon 1 ONU 5
Admin\onu#
6. Query the ONU authorization state.
16 Version: A
Query the authorization state of the ONU under PON Port 1 of Slot 13.
Admin\onu#show authorization slot 13 pon 1
----- ONU Auth Table, Total ITEM = 1 -----

A: Authorized P: Preauthorized R: System Reserved
Command execute success.
Admin\onu#
7. Query the unauthorized ONU.
Query the unauthorized ONU under PON Port 1 of Slot 13.

Admin\onu#show discovery slot 13 pon 1
Command execute success.
Admin\onu#
Version: A 17
6 Service Configuration
Configuring Voice Services Based on H.248
Configuring Voice Services Based on SIP
Configuring Data Services
Configuring Multicast Services
Configuring the Wi-Fi Access Service
18 Version: A
6.1 Configuring Voice Services Based on H.248
The following introduces how to configure the voice service based on the H.248
protocol.
6.1.1 Configuration Rules
u Parameters related to the softswitch platform
When the softswitch platform uses the H.248 protocol to control the access
terminals, set the MGC protocol type to H.248 and the protocol port No. to 2944
for VoIP services.
u Configuration rules for QinQ parameters of voice services
4 The AN5116-06B/AN5516-06/AN5516-04 supports QinQ voice service

which uses the VLAN Stacking technology. In this application, SVLAN is
added to IAD.
4 When you are configuring the VoIP service VLAN and a single-tagged
VLAN is used, make sure that the VLAN ID is within the range of the
service VLAN ID for the uplink port. When stacked VLANs are used, make
sure that the SVLAN ID is within the range of the service VLAN ID for the
uplink port.
6.1.2 Network Planning
Service Planning
Use a GPON ONU (the AN5506-04 is used in this example) to enable calls between
the ONU and telephones outside the system. The H.248 voice protocol is used.
Network Scenario
Figure 6-1 shows the network diagram for the voice service based on the H.248
protocol.
Version: A 19
Figure 6-1 Network Diagram for the Voice Service Based on the H.248 Protocol
Below are the hardware items needed for service configuration.
u Fan card
u Core switch card and uplink card (AN5116-06B / AN5516-06)
u PON service card
u Matching PDP
6.1.3 Configuration Flow
Figure 6-2 shows the flow of configuring voice services based on the H.248 protocol.
20 Version: A
Figure 6-2 Flow of Configuring the Voice Service Based on the H.248 Protocol
6.1.4 Planning Data for the OLT
Table 6-1 shows the planning data on the OLT side for the voice service based on
the H.248 protocol.
Version: A 21
Table 6-1 Planning Data on the OLT Side for the Voice Service Based on H.248 Protocol
service<name> Name of the service VLAN ngn1
Starting VLAN ID of the service

vid_ begin<vid> 3000
VLAN
Ending VLAN ID of the service
vid_ end<vid> 3000
VLAN
uplink<port-No> Port of the uplink service VLAN 20:1
Tag processing mode
Configuring the u In the "tagged" mode, the
service VLAN for VLAN tags of the uplink
the uplink port data packets will not be

stripped when they pass
[untagged| tagged] the uplink port. tagged
u In the "untagged" mode,
the VLAN tags of the
uplink data packets will be
the uplink port.
{service_type <1-8>}*1 Type of service VLAN 3 (NGN service)
ngn_uplink_ interface Name of the uplink port for the
ngn1
name<name> NGN voice service
<1-3>: MGC sequence number 1
Configuring the H. {[mgc] <1-3><addr><1– <addr>: MGC address 192.168.1.101
248 uplink port 65535>}*3 <1-65535>: Number of the
parameters MGC port using the MGCP 2944
protocol.
{[keepalive] [enable|
Heartbeat function enable
disable]}*1
Name of the uplink port for the
servicename<name> ngn1
NGN voice service
phone<value> Telephone number 88880124 88880125
{[public_ip] <A.B.C.D>}*1 Public IP address for the ONU 10.90.60.2
Configuring the
{public_subnet<A.B.C.D>}
NGN uplink Public IP mask for the ONU 255.255.0.0
*1
subscriber
{[public_ gate]<A.B.C.D>}
parameters Public IP gateway for the ONU 10.90.1.254
*1
{[domainnam]<name>}*1 Endpoint domain name 10.90.60.2
{[protocol_ port]<1–
ONU protocol port No. 2944
65535>}*1
22 Version: A
(Continued)

{[username]<name>}*1 Endpoint user name test3 test4
Name of the NGN softswitch
<profileName> ngn1
platform interconnection profile
Fixed part of the RTP resource

fixed <value> RTP/000
name
Starting value of the variable
varB <value> 0
part of the RTP resource name
Ending value of the variable

varE <value> 15
part of the RTP resource name
Step of the variable part of the

step <value> 1
RTP resource name
fixedLen [unfixed|fixed] Fixed length of the RTP name unfixed
beginT <value> Beginning timer of Digitmap 16
shortT <value> Short timer of Digitmap 4
longT <value> Long timer of Digitmap 16
Reporting the matching result
Configuring the matchEM [exclusive|
immediately when match with immediately
NGN softswitch immediately]
any scheme is found
platform
switch [disable| enable] VBD function disable
interconnection
profile (optional) txI <value> VBD Tx interval (ms) 20
rxI <value> VBD Rx interval (ms) 10
voiceC[G711U| G711A|
VBD code type nochange
nochange]
offhkWT [unregiste| Howler tone timeout
unregiste
registe] processing
flashThd <value> Flash duration 90
2833N [disable| enabl] RFC2833 negotiation disable
2833D <value> Default RFC2833 PT 97
2198D <value> Default RFC2198 PT 96
t38EDM [default|V21| all] T.38 event detection mode default
callerIdM [fsk|dtmf] Caller ID mode fsk
Minimum onhook detection
onHKDT <value> 600
time
dailToneTt <value> Dial tone time 60
NoAnsTt <value> No-answer tone time 60
Version: A 23
(Continued)

BusyToneTt <value> Busy tone time 60
ROHTt <value> Howler tone time 60
RetranTt <value> Retransmission timer 25
ECM [disable| enable] Error correction switch disable
L [chinese| english] IAD command line language chinese
{[id] <0-64>} *1 Profile ID 1
slot<value> Slot number 14
Binding the
pon <value> PON port 1
softswitch
onu <value> ONU authorization 1
platform
interconnection qinq_IAD_ softswitch_
Name of the softswitch
profile (optional) binding_ profile ngn1
platform interconnection profile
<profileName>
6.1.5 Planning Data for the ONU
The planning data on the ONU side for the voice service based on the H.248
protocol are shown in Table 6-2.
Table 6-2 Planning Data on the ONU Side for the Voice Service Based on the H.248 Protocol
Parameter
Procedure Parameter Example
Description
slot <value> Slot number 14 14
pon <value> PON port number 1 1
ONU authorization
onu <value> 1 1
number
pots <portno> POTS port number 1 2
Configuring voice phonenum <num> Telephone number 88880003 88880004

service vid <vid> VLAN ID 300 300
parameters of the code_mode [G.711M|G.711A| G. Speech encoding
ONU G.711A G.711A
723|G.729] mode
fax_mode [transparent|t.38] Fax mode transparent transparent
Silence compression
slience [enable| disable] enable enable
switch
Echo suppression
echo_cancel [enable| disable] enable enable
switch
24 Version: A
Table 6-2 Planning Data on the ONU Side for the Voice Service Based on the H.248 Protocol
(Continued)
Parameter
Description
input_gain <num> Input gain 0 0
voice_value <value> Output gain 0 0
dtmf [transparent| rfc2833] DTMF mode transparent transparent
[potsqinqstate] [enable| Voice QinQ function
enable enable
disable] switch
svlanid <0- 4085> Service VLAN ID 3000 3000

H.248
Configure the command parameters according to Planning Data for the OLT and
Planning Data for the ONU.
1. Configure the service VLAN for the uplink port.

Admin\vlan#create service_vlan 101
Admin\vlan#set service_vlan 101 ngn1 type ngn
Admin\vlan#set service_vlan 101 vlan_begin 3000 vlan_end 3000
Admin\vlan#add vlan vlan_begin 3000 vlan_end 3000 tag uplink slot 20 port 1
Admin\vlan#add vlan vlan_begin 3000 vlan_end 3000 tag allslot 0
Admin\vlan#
2. Configure parameters of the H.248 protocol uplink port.

Admin\onu\ngn#set new_ngn_uplink_interface name ngn1 protocol_type h.248 mgc 1
192.168.1.101 2944 keepalive enable
Admin\onu\ngn#
3. Configure the NGN uplink user parameters.

Admin\onu\ngn#set new_ngn_uplink_user servicename ngn1 vid 300 public_ip ipv4
10.90.60.2/16 public_gate ipv4 10.190.1.254 domainname 10.90.60.2 protocol_port 2944
user_index 1
Admin\onu\ngn#set new_ngn_uplink_user servicename ngn1 vid 300 public_ip ipv4

10.90.60.2/16 public_gate ipv4 10.190.1.254 domainname 10.90.60.2 protocol_port 2944
user_index 2
Version: A 25
Admin\onu\ngn#
4. Configure the user telephone numbers.

Admin\onu\ngn#set ngn_uplink_user_port phone 88880003 username a1 user_index 1
Admin\onu\ngn#set ngn_uplink_user_port phone 88880004 username a2 user_index 2
5. Configure the NGN softswitch platform interconnection profile (optional),

Admin\onu\ngn#set ngn_softswitch_para ngn1 fixed RTP/000 varb 0 vare 15 step 1
fixedlen unfixed begint 16 shortt 4 longt 16 matchem immediately switch disable txi 20 rxi
10 voicec nochange offhkwt unregiste flashthd 90 2833n disable 2833d 97 2198d 96 t38edm
default calleridm fsk onhkdt 600 dailtonett 60 noanstt 60 busytonett 60 rohtt 60 retrantt 25
ecm disable l chinese id 1
Admin\onu\ngn#
6. Bind the softswitch platform interconnection profile (optional).

Admin\onu\ngn#set ngn_iad_ss_binding slot 14 pon 1 onu 1
qinq_iad_softswitch_binding_profile ngn1
Admin\onu\ngn#
7. Configure voice service parameters of the ONU.

Admin\onu\ngn#set ngn_voice_service slot 14 pon 1 onu 1 pots 1 phonenum 88880003
code_mode g.711a fax_mode transparent slience enable

8. Save the configuration data.

Admin#save
Trying save configuration to flash, please wait ......

Preparing configuration data to save...Done.
Starting write configuration data to flash...Done.
Configuration save to flash successfully.
Admin#
6.2 Configuring Voice Services Based on SIP
The following introduces how to configure voice services based on SIP.
26 Version: A
u Parameters related to the softswitch platform
When the softswitch platform uses the SIP protocol to control the access
terminals, you should set the MGC protocol type to SIP, and set the protocol
port number of the register server and proxy server to 5060 for VoIP services.
u Configuration rules for QinQ parameters of voice services
4 The AN5116-06B/AN5516-06/AN5516-04 supports QinQ voice service

which uses the VLAN Stacking technology. In this application, SVLAN is
added to IAD.
4 In the configuration of the VoIP service VLAN, when single-tagged VLAN is

used, make sure that the VLAN ID is within the range of the service VLAN
ID for the uplink port. When stacked VLANs are used, make sure that the
SVLAN ID is within the range of the service VLAN ID for the uplink port.
Service Planning
Use a GPON ONU (the AN5506-04 is used in this example) to enable calls between
the ONU and telephones outside the system. The SIP voice protocol is used.
Network Scenario
Figure 6-3 shows the network diagram for the voice service based on SIP.
Figure 6-3 Network Diagram for Configuring the Voice Service Based on SIP
Version: A 27
Below are the hardware items needed for service configuration in this example.
u Fan card
u PON service card
u Matching PDP
Figure 6-4 shows the flow of configuring voice services based on SIP.
Figure 6-4 Flow of Configuring the Voice Service Based on SIP
28 Version: A
The planning data on the OLT side for the voice service based on SIP are shown in
Table 6-3.
Table 6-3 Planning Data on the OLT Side for the Voice Service Based on SIP
service<name> Name of the service VLAN ngn1

vid_begin<vid> 3000
VLAN
vid_end<vid> 3000
VLAN
uplink<port-No> Port of the uplink service VLAN 20:1
Tag processing mode
Configuring the u In the "tagged" mode, the
service VLAN for VLAN tags of the uplink
the uplink port data packets will not be

stripped when they pass the
[untagged| tagged] uplink port. tagged
u In the "untagged" mode, the
VLAN tags of the uplink
data packets will be
uplink port.
{service_type<1-8>}*1 The service VLAN type 3
ngn_uplink_ interface Name of the uplink port for the
ngn1
name<name> NGN voice service
{[sip_reg_ addr]<addr>}
IP address of the SIP server 10.80.20.3
*1
{[sip_reg_ port]<0-
Configuring Number of the SIP protocol port 5060
65535>}*1
parameters of the
{[sip_proxy_ addr]
SIP uplink port Address of the SIP proxy server 10.80.20.3
<addr>}*1
{[sip_proxy_ port]<0- Port number of the SIP proxy
5060
65535>}*1 server
{[sip_ expires]<0-
SIP register expiration time 3600
4294967294>}*1
Configuring the Name of the uplink port for the

servicename<name> ngn1
NGN uplink user NGN voice service
parameters phone<value> Telephone number 88880003 88880004
Version: A 29
Table 6-3 Planning Data on the OLT Side for the Voice Service Based on SIP (Continued)

{[public_ip]<A.B.C.D> Public IP address for the ONU 10.90.60.2
{public_ subnet<A.B.C.
Public IP mask for the ONU 255.255.0.0
D>}*1
{[public_ gate]<A.B.C.
Public IP gateway for the ONU 10.90.1.254
D>}*1
{[username]<name>}*1 SIP telephone number 88880003 88880004
{[sip_user_ name]<name>}
Authorized SIP user name test3 test4
*1
{[sip_user_ password]
Authorized SIP user password test3 test4
<password>}*1
The planning data on the ONU side for the voice service based on SIP are shown in
Table 6-4.
Table 6-4 Planning Data on the ONU Side for the Voice Service Based on SIP

slot <value> Slot number 14 14
pon <value> PON port number 1 1
ONU authorization
onu <value> 1 1
number
pots <portno> POTS port number 1 2
phonenum <num> Telephone number 88880003 88880004
vid <vid> VLAN ID 300 300
Configuring voice code_mode [G.711M|G.711A| G.
Speech encoding mode G.711A G.711A
service parameters 723|G.729]
of the ONU fax_mode [transparent|t.38] Fax mode transparent transparent
Silence compression
slience [enable| disable] enable enable
switch
Echo suppression
echo_cancel [enable| disable] enable enable
switch
input_gain <num> Input gain 0 0
voice_value <value> Output gain 0 0
dtmf [transparent| rfc2833] DTMF Mode transparent transparent
30 Version: A
Table 6-4 Planning Data on the ONU Side for the Voice Service Based on SIP (Continued)

[potsqinqstate] [enable| Voice QinQ function
enable enable
disable] switch
svlanid <0- 4085> Service VLAN ID 3000 3000

SIP
1. Configure the service VLAN for the uplink port.

Admin\vlan#set service_vlan 101 ngn1 type ngn
Admin\vlan#
2. Configure parameters of the SIP uplink port.

Admin\onu\ngn#set new_ngn_uplink_interface name ngn1 protocol_type sip
sip_reg_addr 10.80.20.3 sip_reg_port 5060 sip_proxy_addr 10.80.20.3 sip_proxy_port 5060
sip_expires 3600
Admin\onu\ngn#
3. Configure the NGN uplink user parameters.

Admin\onu\ngn#set new_ngn_uplink_user servicename ngn1 vid 300 ip_mode static
public_ip ipv4 10.80.20.3/16 public_gate ipv4 10.80.1.254 domainname 10.80.20.3
protocol_port 5060 user_index 1
Admin\onu\ngn#set new_ngn_uplink_user servicename ngn1 vid 300 ip_mode static

public_ip ipv4 10.80.20.3/16 public_gate ipv4 10.80.1.254 domainname 10.80.20.3
protocol_port 5060 user_index 2
Admin\onu\ngn#
4. Configure the user telephone numbers.

Admin\onu\ngn#set ngn_uplink_user_port phone 88880003 username 88882211
sip_user_name test3 sip_user_password test3 user_index 1
Version: A 31
Admin\onu\ngn#set ngn_uplink_user_port phone 88880004 username 88882212

sip_user_name test4 sip_user_password test4 user_index 2
Admin\onu\ngn#
5. Configure voice service parameters of the ONU.


Admin\onu\ngn#

Admin#save

Admin#
6.3 Configuring Data Services
The following introduces how to configure data services.
u Rules for configuring services in the transparent transmission mode. The

Ethernet data uploaded from the subscriber side are added with a VLAN ID by
the home gateway and uplinked to the ONU. After that, the data will be
processed in either of the two ways as follows:
4 The ONU transparently transmits the CVLAN ID and adds SVLAN ID to it,
and then uplinks the data service to the AN5116-06B/AN5516-06/AN5516-
04. Without processing the data, the AN5116-06B/AN5516-06/AN5516-04
transparently transmits the data service to the equipment in the providers
network.
32 Version: A
4 The ONU transparently transmits the CVLAN ID and uplinks the data
service to the AN5116-06B/AN5516-06/AN5516-04. After adding the
SVLAN ID to the data, the AN5116-06B/AN5516-06/AN5516-04 transmits
the data service to the equipment in the providers network.
u Rules for configuring services in the TAG mode.
4 The ONU adds the VLAN ID and SVLAN ID to the Ethernet data on the
subscriber side, and then transmits the data to the AN5116-06B/AN5516-
06/AN5516-04. The AN5116-06B/AN5516-06/AN5516-04 does not
process the data service but transparently transmits it to the equipment in
the providers network.
4 The ONU adds the VLAN ID to the Ethernet data on the subscriber side,
and then transmits the data to the AN5116-06B/AN5516-06/AN5516-04.
The AN5116-06B/AN5516-06/AN5516-04 adds the SVLAN ID to the data
received and then transmits the data service to the equipment in the
providers network.
u Rules for configuring services in the translation mode. The Ethernet data
uploaded from the subscriber side are added with a VLAN ID by the home
gateway and uplinked to the ONU. After that, the data will be processed in one
of the three ways as follows:
4 The ONU converts the VLAN ID to one meeting the operator's

requirements, adds the SVLAN ID to it, and then uploads the data to the
AN5116-06B/AN5516-06/AN5516-04. Without processing the data, the
AN5116-06B/AN5516-06/AN5516-04 transparently transmits the data
service to the equipment in the providers network.
4 The ONU converts the VLAN ID to one meeting the operator's

requirements and then uploads the data to the AN5116-06B/AN5516-06/
AN5516-04. The AN5116-06B/AN5516-06/AN5516-04 adds the SVLAN ID
to the data received and then transmits the data service to the equipment
in the providers network.
4 The ONU transparently transmits the CVLAN ID to the AN5116-06B/

AN5516-06/AN5516-04. The AN5116-06B/AN5516-06/AN5516-04
converts the VLAN ID to one meeting the operator's requirements, adds
the SVLAN ID to the data, and then transmits the data service to the
equipment in the providers network.
u Rules for configuring services in the QinQ mode.
Version: A 33
4 The system can process the CVLAN and SVLAN of the service based on
the source MAC address, destination MAC address, source IP address,
destination IP address, L4 source port number, L4 destination port number,
Ethernet type, inner VLAN, outer VLAN, service type, Time to Live,
protocol type, Layer 1 CoS, Layer 2 CoS and other conditions.
4 In the configuration of the data service VLAN, when a single-tagged VLAN

is used, make sure that the VLAN ID is within the range of the service
VLAN ID for the uplink port. When stacked VLANs are used, make sure
that the SVLAN ID is within the range of the service VLAN ID for the uplink
port.
u Rules for bandwidth allocation. While allocating bandwidth, make sure that the
sum of the fixed bandwidth and assured bandwidth of the service is no larger
than the maximum bandwidth.
Service Planning
Two PCs are connected to the same AN5506-04. The ONU transparently transmits
users' packets to the OLT. The OLT adds SVLAN to the packets according to the
QinQ rule, and then forwards the packets to the uplink port.
Network Scenario
Figure 6-5 shows the network diagram for the data service.
Figure 6-5 Network Diagram for Data Services
34 Version: A
Below are the hardware items needed for service configuration in this example:
u Fan card
u PON service card
u Matching PDP
Figure 6-6 shows the flow of configuring data services.
Version: A 35
Figure 6-6 Flow of Configuring Data Services
36 Version: A
Table 6-5 shows the planning data on the OLT side for the data service.
Table 6-5 Planning Data for the OLT
The service VLAN index, ranging from

<id> 101
Creating the 101 to 4095.
service VLAN <name> Name of the service VLAN data1

vid_begin<vid> Starting VLAN ID of the service VLAN 3000
vid_end<vid> Ending VLAN ID of the service VLAN 3001
vid_begin<vid> Starting VLAN ID 3000
vid_end<vid> Ending VLAN ID 3001
Tag processing mode
u In the "tag" mode, the VLAN tags of
the uplink data packets are not
stripped when they pass the uplink
[untag|tag] port. tag
u In the "untag" mode, the VLAN tags
of the uplink data packets are
stripped when they pass the uplink
port.
Adding ports to the
[uplink|trunk|
VLAN Type of port to be added uplink
upbak|allslot]
Number of the slot for the uplink port (you

slot <slotno> need not configure this item for ports of 19
other types)
Port number
u The number of an uplink port is
expressed as port <portno>.
port <portno> u The number of other ports is 1
expressed as <portno>.
u If you want to select the ports of all
slots, set the port number to 0.
Creating the OLT oltqinq_domain

Name of QinQ domain aa
QinQ domain <name>
Configuring the service_num <1-8> Quantity of services 2
quantity of services
in the QinQ domain <1-8> 1 single Index of service 1
Version: A 37
Table 6-5 Planning Data for the OLT (Continued)
Configuring service type[single|share] Service type single

type of the QinQ
oltqinq_domain
domain Name of QinQ domain aa
<name>
<1-8> Index of service 1
Configuring uplink 7 (VLAN1, i.e., VLAN

<1-27> Uplink rule type
rules for the OLT of the first layer)
QinQ domain <value> Value of the selected uplink domain 500

5 (exist: exist then
<op> Uplink operator
match)
oltqinq_domain
<name>
Configuring <1-8> Index of service 1
downlink rules for 7 (VLAN1, i.e., VLAN

<1–27> Type of downlink rules
the OLT QinQ of the first layer)
domain <value> Value of the selected downlink domain 500
<op> Downlink operator
match)
oltqinq_domain
<name>
vlan <laper> VLAN of the selected layer 1 2
Configuring VLAN <oldvid> The original VLAN ID 500 null

service rules for the [<oldcos>|null] The original COS value 0 null
QinQ domain [add|translation|
Action of the VLAN at the selected layer transparent add
transparent]
<tpid> The TPID value 33024 33024
[<cos>|null] The COS value 0 0
[<newvid>|null] The new VLAN ID null 3000
slot <1-18> Slot number 14
pon <1-8> PON port No. 2
Binding the ONU to
onu <1-128> ONU authorization number 1
the QinQ domain
[attach|detach] Binding / unbinding operations attach
domain <name> Name of QinQ domain aa
38 Version: A
Table 6-6 shows the planning data on the ONU side.
Table 6-6 Planning Data for the ONU
ID of the service
id <1-256> 1
bandwidth profile
Name of the service

name <profile_name> data1
Configuring the ONU bandwidth profile
service bandwidth profile type[iptv|data|voi|tdm|inte|
Service type data
data2|data3|data4|com]
fix <16-128000> Fixed bandwidth 16
assure <0-128000> Assured bandwidth 0
max <48-128000> Maximum bandwidth 1280
slot <slotNo> Slot number 14
Configuring quantity of pon <ponNo> PON port number 2

services at the ONU port onu <onulist> ONU number 1
port <port> Port number 1
service number <0-16> Quantity of services 1
slot <slotNo> Slot number 14
pon <ponNo> PON port number 2
Configuring services at the onu <onulist> ONU number 1
ONU port port <port> Port number 1
service <1-16> Service number 1
type [multicast|unicast] Service type unicast
Configuring the ONU slot <slotNo> Slot number 14

pon <ponNo> PON port number 2
onu <onulist> ONU number 1
port <port> Port number 1
service <1-16> Service number 1
vlan_mode [tag|transparent] VLAN mode tag
VLAN mode for service at The CoS value, ranging
the port from 0 to 7. 0 stands for
<cos> 0
the lowest priority level,
and 7 the highest one.
<tpid> CVLAN TPID 33024
<c_vlanlist> CVLAN ID 500
Version: A 39
6.3.6 Procedures of Configuring Data Services
1. Configure the service VLAN.

Admin\vlan#set service_vlan 102 data1 type data
2. Add service VLAN to the uplink port and all slots.

Admin\vlan#
3. Configure quantity of services at the ONU port.

Admin\onu\lan#set epon slot 14 pon 2 onu 1 port 1 service number 1
Admin\onu\lan#
4. Configure type of service at the ONU port.

Admin\onu\lan#set epon slot 14 pon 2 onu 1 port 1 service 1 type unicast
Admin\onu\lan#
5. Configure the VLAN mode for the service at the ONU port.
Admin\onu\lan#set epon slot 14 pon 2 onu 1 port 1 service 1 vlan_mode tag 0 33024 500
Admin\onu\lan#
6. Deliver service configuration to the ONU to validate the configuration.

Admin\onu\lan#apply onu 14 2 1 vlan
Admin\onu\lan#
7. Create a QinQ domain.

Admin\qinq#create oltqinq_domain aa
Admin\onu\lan#
8. Configure the quantity of services in the QinQ domain.

Admin\qinq#set oltqinq_domain aa service_num 1
Admin\qinq#
9. Configure uplink rules for the OLT QinQ domain.
40 Version: A
Admin\qinq#set oltqinq_domain aa 1 uprule 7 500 5 serv_id 1
Admin\qinq#
10. Configure downlink rules for the OLT QinQ domain.

Admin\qinq#set oltqinq_domain aa 1 downrule 7 500 5
Admin\qinq#
11. Configure VLAN service rules for the QinQ domain.

Admin\qinq#set oltqinq aa 1 vlan 1 500 0 transparent 33024 0 null vlan 2 null null add
33024 0 3000
Admin\qinq#
12. Bind the ONU to the QinQ domain.

Admin\qinq#set onu attach slot 14 pon 2 onu 1 attach domain aa
Admin\qinq#

Admin#save

Admin#
6.4 Configuring Multicast Services
The following introduces how to configure the multicast services
u The three multicast modes for the AN5116-06B/AN5516-06/AN5516-04 are

described as follows:
4 In the proxy mode, both the core switch card and the GPON interface card
work in the proxy mode, and the system manages the statuses of multicast
group members proactively. This can effectively reduce the protocol
processing load on the uplink equipment.
Version: A 41
4 In the snooping mode, both the core switch card and GPON interface card
work in the snooping mode, and they only snoop and forward IGMP
messages. This mode has the smallest influence on system load, but
increases the protocol processing load on the uplink equipment.
4 In the proxy-snooping mode, the core switch card works in the proxy mode,
while the GPON interface card works in the snooping mode. In this way,
the proxy mode and the snooping mode are combined.
u Bandwidth is allocated as follows:
4 If data services are not started for the ONU, configure a bandwidth for the
"IPTV service" and a bandwidth for the "broadband Internet access
service" for an FTTH ONU, and configure a bandwidth for the "IPTV
service" and a bandwidth for the "integrated service" for an FTTB ONU
4 If data services are started for the ONU, you need only to configure a
bandwidth for the "IPTV service" for all ONUs.
u For an FTTH ONU, you need to add a unicast service as well as a multicast
service to the ONU port to provide channels for the uplink and downlink
multicast protocol packets. For the ONU in this example, you need only to add
a multicast service to the ONU port.
u You need not configure VLAN CoS for multicast services. The CoS of the
downlink multicast stream is carried by the multicast stream and cannot be
modified on the OLT or ONU. The CoS of the uplink / downlink multicast
protocol packets is 0 by default.
u A multicast program can belong to only one multicast VLAN, while a multicast
VLAN can contain a multicast program or a multicast program group (a
collection of multicast programs subject to the same management authority).
u If the set top box or PC acquires the IP address in the DHCP mode, you need
to configure a unicast service as well as a multicast service for the port.
42 Version: A
Service Planning
Two subscribers are connected to the AN5506-04-FG, and they can use the set top
boxes (STB) to watch IPTV programs. The service in this case is the multicast
service in the proxy-snooping mode. Accordingly, the OLT should work in the proxy-
snooping mode.
Network Scenario
Figure 6-7 shows the network diagram for the multicast service carried by the
AN5116-06B/AN5516-06/AN5516-04 in the proxy-snooping mode.
Figure 6-7 Network Diagram for the Multicast Service in the Proxy-snooping Mode
u Fan card
u PON service card
u Matching PDP
The flow of configuring multicast services is shown in Figure 6-8.
Version: A 43
Figure 6-8 Flow of Configuring Multicast Services
Table 6-7 shows the planning data on the OLT side for the multicast service in the
proxy-snooping mode.
44 Version: A

service_vlan<id> Service VLAN ID, ranging from 101 to 4195. 101
service<name> Name of the service VLAN iptv1
type[data|iptv|ngn|
Configuring the
voip|void|cnc|system| Service type iptv
VLAN service
uplinksub]
vlan_begin <1-4085> Starting VLAN ID of the service VLAN 100
vlan_end <1-4085> Ending VLAN ID of the service VLAN 100
vlan_begin <1-4085> Starting VLAN ID of the service VLAN 100
vlan_end<1-4085> Ending VLAN ID of the service VLAN 100
Tag processing mode
u In the "tagged" mode, the VLAN tags of
the uplink data packets will not be
Adding the
[untagged|tagged] stripped when they pass the uplink port. tagged
service VLAN to
u In the "untagged" mode, the VLAN tags
the uplink port
of the uplink data packets will be stripped
when they pass the uplink port.
Number of the slot accommodating the uplink

slot <slotno> 20
port
port <portno> Uplink port number 2
Number of the slot accommodating the uplink
slot <slotno> 20
port
Disabling
port <portno> Uplink port number 2
suppression of
Packet classification. When provisioning the
multicast
[broadcast|multicast| multicast service, you need to disable
packets at the multicast
unknown|all] suppression of multicast packets for the
uplink port
uplink port.
[enable|disable] Enable or disable packet suppression. disable

Multicast modes
u control: controlled mode
[control|proxy-proxy|
Configuring the u proxy-proxy: proxy-proxy mode
snooping|proxy- proxy-snooping
multicast mode u snooping: snooping mode
snooping|disable]
u proxy-snooping: proxy-snooping mode
u disable: disabled mode
Configuring the
vlan{[default]}*1
default multicast Multicast VLAN 100
{<1-4088>}*1
VLAN
Version: A 45
Table 6-8 shows the planning data on the ONU side for the multicast service in the
proxy-snooping mode.
Parameter
Description
ID of the service
id <1-256> 1 2
bandwidth profile
Name of the service

Configuring the name<profile_name> test1 test2
bandwidth profile
ONU service
type[iptv|data|voice|tdm|
bandwidth
integrated|data2|data3|data4| Service type iptv integrated
profile
com]
fix <16-128000> Fixed bandwidth 2400 128
assure <0-128000> Assured bandwidth 0 0
max <48-128000> Maximum bandwidth 6400 1280
slot<slotNo> Slot number 14
pon<portNo> PON port number 2
ONU authorization
Configuring onu<onulist> 1
number
services at the
port<portno> ONU port number 1
ONU port
Sequence number of
service<1-16> 1
service
type[multicast|unicast] Service type multicast
slot<slotNo> Slot number 14
pon<ponNo> PON port number 1
ONU authorization
onu<onulist> 1
number
port<port> ONU port number 1
Configuring
Sequence number of
VLAN mode for service<1-16> 1
service
the service at
the ONU port vlan_mode[tag|transparent] VLAN mode tag
The CoS value,

ranging from 0 to 7. 0
<cos> stands for the lowest 0
priority level, and 7 the
highest one.
46 Version: A
Table 6-8 Planning Data for the ONU (Continued)
Parameter
Description
<tpid> CVLAN TPID 33024
<c_vlanlist> CVLAN ID 100
6.4.6 Procedures of Configuring Multicast Services
1. Configure the service VLAN.

Admin\vlan#set service_vlan 101 iptv1 type iptv
servicevlan 101 :
name : iptv1, type : iptv
vlan range: 101 #####end.
Admin\vlan#
2. Add service VLAN to the uplink port.

Admin\vlan#
3. Disable suppression of multicast packets at the uplink port.

Admin\interface#set control uplink slot 20 port 2 multicast disable
Admin\interface#
4. Configure the multicast mode.

Admin\protocol\igmp#set igmp mode proxy-snooping
Admin\protocol\igmp#
5. Configure the default multicast VLAN.

Admin\protocol\igmp#set igmp vlan 100
Admin\protocol\igmp#
6. Configure the number of service at the ONU port.
Version: A 47
Admin\onu\lan#set epon slot 14 pon 1 onu 1 port 1 service number 1
Admin\onu\lan#
7. Configure type of service at the ONU port.

Admin\onu\lan#set epon slot 14 pon 1 onu 1 port 1 service 1 type multicast
Admin\onu\lan#
8. Configure the VLAN mode for the service at the ONU port.
Admin\onu\lan#set epon slot 14 pon 1 onu 1 port 1 service 1 vlan_mode tag 0 33024 100
Admin\onu\lan#

Admin#save

Admin#
6.5 Configuring the Wi-Fi Access Service
The following introduces how to configure the ONU Wi-Fi access service.
Service Planning
Use the ONU supporting the Wi-Fi function to cater for the demand of wireless
access service.
Network Scenario
Figure 6-9 shows the network diagram for the Wi-Fi service of the ONU.
48 Version: A
Figure 6-9 Network Diagram for the ONU Wi-Fi Service
u Fan card
u PON service card
u Matching PDP
Other hardware items needed include the ONU supporting the Wi-Fi function (e.g.
AN5506-04-FG), network cables, optical fibers, and so on.
Figure 6-10 shows the flow of configuring the ONU Wi-Fi service.
Version: A 49
Figure 6-10 Flow of Configuring the Wi-Fi Function of ONU
Table 6-9 shows the planning data on the OLT side for the Wi-Fi access service.
Number of the slot accommodating the GC8B

slot <slotno> 2
card connected to the ONU
pon <ponno> Number of the PON port connected to the ONU 3
ONU authorization number. Configure this item
ONU information
onu <onuno> according to the network planning of the 1
operator.
[onutype] <onu_ type_
ONU type AN5506-04-FG
str>
Service name. Configure this item according to
<name> data
Configuring the the network planning of the operator.
local end data of Starting ID of the uplink port service VLAN.
service VLAN vlan_begin <1-4085> Configure this item according to the network 200
planning of the operator.
50 Version: A
Ending ID of the uplink port service VLAN.

vlan_end <1-4085> Configure this item according to the network 200
type [data|iptv| ngn|
voip|void| cnc| Service type. Select data for the Wi-Fi service. Data
system| uplinksub]
service_vlan <id> - 200
uplink <portno> Number of the uplink port actually used 19:SFP1
Configure the tag processing mode for the uplink
service VLAN. Two options are available: "tag"
and "untag".
u In the "untag" mode, the tags of the uplink
Adding ports to packets will be stripped automatically when
the VLAN they pass the port and the packets will be
[untag|tag] tag
further transmitted in the untagged mode,
while the downlink untagged packets will be
added with tags when they pass the port.
u In the "tag" mode, the tags of the uplink /
downlink data packets will not be processed
when they pass the port.
The planning data here are only applicable to single-VLAN services commonly used
in a project. To use double VLANs, QinQ planning data are needed.
Table 6-10 shows the planning data on the ONU side for the Wi-Fi access service.

mode[tr069|internet| tr069_
WAN connection mode. Select
Configuring the internet|other| multi|voip|
the internet mode or other modes
WAN connection voip_ internet|iptv|radius| internet
containing the word internet for
service radius_internet| unicast_
the Wi-Fi service.
iptv| multicast_iptv]
Version: A 51
WAN connection type. Select

"bridge" or "route" according to
the requirement of Internet
service providers (ISP). "Bridge"
type[bridge|route] route
stands for the L2 bridge
connection mode, while "route"
stands for the L3 route
connection mode.
Set the VLAN ID (within the range
of 1 to 4085) of WAN connection
according to the requirement of
ISP. The VLAN ID should not be
<vid> 200
occupied by other connections,
and should be within the local
VLAN ID range of the Wi-Fi
service on the OLT side.
The 802.1p priority of WAN
connection. The value ranges
<cos> from 0 to 7. 7 stands for the 1
highest priority level, and 0 the
lowest one.
Set whether to enable NAT for the
WAN connection. That is, select
whether to enable the network
address translation function to
nat [enable|disable] enable
convert the private network IP
address to the public network IP
address according to the
requirement of ISP.
The way to acquire the address

for WAN connection. Select the
[pppoe] IP address obtaining mode for pppoe
WAN connection according to the
requirement of ISP.
[fe1|fe2|fe3|fe4| ssid1| Select the Ethernet port or SSID
fe1
ssid2|ssid3| ssid4] bound with the WAN connection.
Configuring the Wi- Select to enable the Wi-Fi
wifi [enable| disable] enable
Fi service function.
52 Version: A

district[etsi| fcc|thailand|
philippines| indonesia|
brazil|india| armenia|
malaysia| pakistan| russian| Wireless area. Set the range of
etsi
china| chile|usa| myanmar| wireless channels.
ecuador| colombia| argentina|
stilanka|iran| yemen|
saudiarabia| kuwait|iraq]
Sequence number of the wireless

channel <0-13> 0
channel
The wireless network standards
[standard] [802. 11b|802.11g| that the equipment complies with.
802.11bgn
802. 11b/g|802.11n| 802.11bgn] Configure this item according to
the operator’s network planning.
The wireless network identifier.

[<ssid> |null] Configure this item according to abc
the operator’s network planning.
Select to enable the SSID

ssid [enable|disable] enable
function.
hide [enable|disable] Select whether to hide the SSID. disable
authmode [open|shared|
WAN authentication mode.
wepauto|wpa_psk|wpa| wpa2psk|
Configure this item according to
wpa2|wpa/wpa2| wpa_ wpa_psk
the network planning of the
psk/wpa2psk|wpa_ psk/wpapsk2|
operator.
waipsk| wai]
WAN encryption mode. Configure

encrypt_type [none| wep|tkip|
this item according to the network tkip
aes|tkipaes| wpi]
The WPA pre-shared and

wpakey[<wpakey>|null] encrypted key, containing no 12345678
more than 64 characters.
The WPA key refreshing interval;
interval <0-4194303> 86400
the unit is second.
Version: A 53
6.5.5 Procedures of Configuring the Wi-Fi Access Service
1. Configure local end outer VLAN data.

Admin\vlan#set service_vlan 200 uplink type data
Admin\vlan#
2. Add VLAN to the uplink port and all slots.

3. Configure the WAN connection service.

Admin\onu\lan#set wancfg slot 2 3 1 index 1 mode internet type route 200 1 nat enable
qos enable dsp pppoe proxy disable 131182110208@telkom.net key:X]SXGKjkEY
131182110208 auto active enable entries 1 fe1
Admin\onu\lan#
4. Configure parameters of the ONU Wi-Fi service.

Admin\onu\lan#set wifi_serv_cfg slot 2 pon 3 onu 1 wifi enable district etsi channel 0
standard 802.11bgn txpower 32 frequency 2.4ghz freq_bandwidth 20mhz/40mhz
Admin\onu\lan#set wifi_serv_wlan slot 2 pon 3 onu 1 index 1 ssid enable abc hide disable
authmode wpa_psk encrypt_type tkip wpakey 12345678 interval 86400 radius_serv ipv4
0.0.0.0 port 1812 pswd null wapi_serv_addr 0.0.0.0 0 wifi_connect_num 0
Admin\onu\lan#

Admin#save
Admin#
54 Version: A
7 Function Configuration
Configuring the VEIP Function
Configuring the DHCP Function
Configuring the ARP Proxy Function
Configuring QoS Functions
Configuring the LACP Function
Configuring the MSTP Function
Configuring the RADIUS Function
Configuring the Tacacs+ Function
Configuring the Subscriber Line Identification Function
Version: A 55
7.1 Configuring the VEIP Function
The following introduces how to configure the VEIP management function.
Service Planning
Figure 7-1 shows the dual-stack management mode for home gateway devices.
Figure 7-1 Dual-stack Management Mode for Home Gateway Devices
Transparent transmission from the vUNI interface to the PON port is enabled for the
ONU based on the OMCI protocol. By configuring the parameter "IP host config
data ME" according to the OMCI protocol, you can select the way to obtain the
remote management IP address (i.e., the IP address for TR-069 WAN connection).
The IP address can be configured as a static one or obtained dynamically based on
DHCP. The default setting is dynamic obtaining.
Network Scenario
Figure 7-2 shows the network diagram for the ONU's VEIP function.
Figure 7-2 Network Diagram for the VEIP Function of ONU
56 Version: A
u Fan card
u PON service card
u Matching PDP
Other hardware items needed include the ONU supporting the VEIP function (e.g.
AN5506-04-F1), network cables, optical fibers, and so on.
Figure 7-3 shows the flow of configuring the MSTP service.
Figure 7-3 Flow of Configuring the VEIP Function
The planning data on the OLT side for the VEIP function are shown in Table 7-1.
Version: A 57
Number of the slot accommodating

slot <slotno> the GC8B card connected to the 17
ONU
Number of the PON port connected
pon <ponno> 1
ONU information to the ONU
Configure this item according to the
onu <onuno> 8
network planning of the operator.
[onutype] <onu_ type_
ONU type AN5506-04-B2
str>
Service name. Configure this item
<name> according to the network planning VEIP
of the operator.
Starting ID of the uplink port service

VLAN. Configure this item
vlan_begin <1-4085> 3638
according to the network planning
Configuring the local
of the operator.
end data of service
Ending ID of the uplink port service
VLAN
VLAN. Configure this item
vlan_end <1-4085> 3638
according to the network planning
of the operator.
type [data|iptv| ngn|
Service type. Select data for the
voip|void| cnc|system| Data
VEIP service.
uplinksub]
service_vlan <id> - 3638
Adding ports to the
Number of the uplink port actually
VLAN uplink<portno> 19:1
used
58 Version: A
Configure the tag processing mode

for the uplink service VLAN. Two
options are available: "tag" and
"untag".
u In the "untag" mode, the VLAN
tags of the uplink packets will
be stripped automatically when
they pass the port, while the
[untag|tag] tag
downlink untagged packets will
be added with corresponding
tags when they pass the port.
u In the "tag" mode, the VLAN
tags of the uplink / downlink
data packets will not be
processed when they pass the
port.
Service type. Configure this item

type[unicast|
according to the network planning unicast
muliticast|multiup]
of the operator.
CVLAN mode. Configure this item

cvlan[tag|transparent] according to the network planning transparent
of the operator.
Service model profile Translation enabling state.
translate[enable|
Configure this item according to the disable
disable]
QinQ enabling state. The QinQ

function cannot be enabled now
qinq [enable|disable] disable
(configuration is available but does
not take effect).
Creating the OLT

oltqinq_domain <name> Name of QinQ domain aa
QinQ domain
Configuring the service_num <1-8> Quantity of services 3
quantity of services in
the QinQ domain <1-8> 1 single Index of service 1
Configuring service type[single|share] Service type single

type for the QinQ
domain oltqinq_domain <name> Name of QinQ domain aa
Version: A 59

7 (VLAN1, i.e.,
Configuring uplink <1-27> Uplink rule type VLAN of the first
rules for the OLT layer)
QinQ domain
<value> Value of the selected uplink domain 000000000002
<op> Uplink operator
match)
7 (VLAN1, i.e.,
Configuring downlink <1-27> Type of downlink rules VLAN of the first
rules for the OLT layer)
QinQ domain Value of the selected downlink
<value> 000000000001
domain
<op> Downlink operator
match)
vlan <laper> VLAN of the selected layer 1
<oldvid> The original VLAN ID 500
Configuring VLAN
[<oldcos>|null] The original COS value 0
service rules for the
QinQ domain [add|translation| Action of the VLAN at the selected
transparent
transparent] layer
<tpid> The TPID value 33024
[<cos>|null] The COS value 0
[<newvid>|null] The new VLAN ID null
slot <1-18> Slot number 14
pon <1-8> PON port number 2
Binding the ONU to
onu <1-128> ONU authorization number 1
the QinQ domain
[attach|dettach] Binding / unbinding operations attach
domain <name> Name of QinQ domain aa
The planning data here are only applicable to single-VLAN services. To use double
VLANs, you need to plan data for the QinQ domain.
60 Version: A
The planning data on the ONU side for the VEIP function are shown in Table 7-2.
The number of the slot accommodating the GC8B

<slotno> 17
card connected to the ONU.
The number of the PON port connected to the
<ponno> 1
ONU.
Configure this item according to the network
<onuno> 8
<veip_port> The only option available now is 1. 1
port_type The only option available now is VEIP. VEIP
Configuring the
management Enable or disable a non-OMCI management
[enable|disable] disable
channel channel.
{model [tr069|snmp] } The only option available now is TR-069. TR-069
<item> The only option available now is 1. 1
<mgr_id> The only option available now is 1. 1
[name] <mgr_name> The default setting is manage. manage
Configure this item according to the network

[ip_type] [static|
planning of the operator. Two options are dhcp
dhcp]
available: dhcp and static.
Service model profile. Configure this item

<servmode> 2
according to the network planning of the operator.
Configure the management VLAN according to

<cvid> 146
VEIP data the network planning of the operator.
service Configure the VoIP service VLAN according to the
<cvid> 176
Configure the data service VLAN according to the

<cvid> 3638
7.1.5 Procedures of Configuring the VEIP Service
Version: A 61
Admin\vlan#set service_vlan 3638 VEIP type data
Admin\vlan#set service_vlan 146 MANAGE type cnc
Admin\vlan#set service_vlan 176 VOIP type voip
Admin\vlan#
2. Add service VLAN to the uplink port and all slots.

Admin\vlan#
3. Create a QinQ domain.

Admin\qinq#create oltqinq_domain aa
Admin\onu\lan#
4. Configure the quantity of services in the QinQ domain.

Admin\qinq#set oltqinq_domain aa service_num 3
Admin\qinq#
5. Configure uplink rules for the OLT QinQ domain.

Admin\qinq#
6. Configure downlink rules for the OLT QinQ domain.

62 Version: A
Admin\qinq#
7. Configure VLAN service rules for the QinQ domain.

Admin\qinq#set oltqinq aa 1 vlan 1 146 0 transparent 33024 null null vlan 2 0 0 transp
33024 null null
Admin\qinq#set oltqinq aa 2 vlan 1 755 0 transparent 33024 null null vlan 2 null 0 add
33024 null 3638
Admin\qinq#set oltqinq aa 1 vlan 1 176 0 transparent 33024 null null vlan 2 0 0 transp
33024 null null
Admin\qinq#
8. Bind the ONU to the QinQ domain.

Admin\qinq#set onu attach slot 17 pon 1 onu 8 attach domain aa
Admin\qinq#
9. Configure the service model profile.

Admin\profile#add servmode profile index 2 name 2 type unicast cvlan transparent
translate disable qinq disable null
Admin\profile#
10. Configure the VEIP management channel.

Admin\onu\lan#set veip_mgr_par slot 17 pon 1 onu 8 veip_port 1 port_type veip
mgr_channel enable model tr069 item 1
Admin\onu\lan#set veip_mgr_vlan slot 17 pon 1 onu 8 veip_port 1 mgr_id 1 name

manage ip_type dhcp ip_addr ipv4 0.0.0.0 0 gateway ipv4 0.0.0.0 0 pri_dns ipv4 0.0.0.0 0
sec_dns ipv4 0.0.0.0 0 protocol udp port 0 priority 0 tag_type untag svlan_label 0x8100
svlanid null svlan_cos null cvlan_label 0x8100 cvlanid null cvlan_cos null
Admin\onu\lan#
11. Configure the VEIP data service.

Admin\onu\lan#set epon slot 17 pon 1 onu 8 port 1 onuveip 1 33024 46 65535 33024 65535
65535 33024 65535 65535 0 2 65535 servname null
Admin\onu\lan#set epon slot 17 pon 1 onu 8 port 1 onuveip 2 33024 755 65535 33024
65535 65535 33024 65535 65535 0 2 65535 servname null
Admin\onu\lan#set epon slot 17 pon 1 onu 8 port 1 onuveip 3 33024 76 65535 33024 65535
65535 33024 65535 65535 0 2 65535 servname null
Admin\onu\lan#
Version: A 63

Admin#save
Admin#
7.2 Configuring the DHCP Function
The following introduces how to configure the DHCP function for the AN5116-06B/
AN5516-06/AN5516-04.
u When serving as DHCP Relay, the AN5116-06B/AN5516-06/AN5516-04 can

either be DHCP proxy only or be both DHCP proxy and gateway. Under both
conditions, the Super VLAN interface should be added as the Layer 3 interface
to convert the users' DHCP broadcast messages to unicast messages and
forward the messages to the designated DHCP server.
4 Super VLAN: a virtual routing interface, also known as VLAN aggregation.

A Super VLAN contains multiple Sub VLANs.
4 Sub VLAN: the subsidiary VLAN of the Super VLAN. The relationship
between Super VLAN and Slave VLAN is master and slave.
u The AN5116-06B/AN5516-06/AN5516-04 can be configured with up to 16

Super VLANs. Each Super VLAN can be added with four Sub VLANs at most.
u The IP address bound to the downlink Super VLAN should be in the same
network segment with the IP address of the DHCP Client which uses the DHCP
proxy function of this Super VLAN.
u The VLAN IDs set for the Super VLANs and the Sub VLANs range from 1 to
4085.
u When the AN5116-06B/AN5516-06/AN5516-04 serves as DHCP proxy only,

you need to configure static routing so that DHCP request is forwarded to the
DHCP server via the gateway.
64 Version: A
u When DHCP Snooping function is enabled for the AN5116-06B/AN5516-06/

AN5516-04, DHCP broadcast packets need not be processed. However, when
trusted ports have been configured for the DHCP Snooping, only the trusted
ports can normally receive and forward the DHCP request messages, while the
DHCP response messages from the untrusted ports and the untrusted DHCP
request messages from users will be filtered, so as to ensure that the client end
can obtain the IP address from a legal DHCP server.
u When serving as the DHCP server, the AN5116-06B/AN5516-06/AN5516-04

will search for undistributed IP addresses from the address pool after it receives
DHCP broadcast messages from users, and then transmit PING packets to
check whether these IP addresses have been occupied. After confirming that
the IP addresses are available, the AN5116-06B/AN5516-06/AN5516-04 will
allocate them to the users.
7.2.2 Configuring DHCP Relay with OLT Equipment Serving

as Proxy
The following introduces how to configure DHCP Relay when the AN5116-06B/
AN5516-06/AN5516-04 only serves as proxy.
7.2.2.1 Network Planning
Figure 7-4 shows the network diagram for configuring the OLT as DHCP proxy.
Figure 7-4 Network Diagram for Configuring the OLT as DHCP Proxy Only
Version: A 65
When serving as DHCP proxy only, the OLT will translate the broadcast DHCP
request messages received from the DHCP Client into unicast messages, and
modify the parameters such as source MAC address, destination MAC address,
source IP address and destination IP address. After that, it will forward the
messages to the DHCP Server via an external gateway.
u Fan card
u PON service card
u Matching PDP
The other hardware items needed include the ONUs supporting this function,
network cables, optical fibers, and so on.
7.2.2.2 Configuration Flow
Figure 7-5 shows the configuration flow when the OLT serves as DHCP proxy only.
66 Version: A
Figure 7-5 Flow of Configuring the OLT as DHCP Proxy Only
7.2.2.3 Planning Data
The planning data for configuring the OLT as the DHCP proxy only are shown in
Table 7-3.
Version: A 67
Table 7-3 Configuring the OLT as the DHCP Proxy Only
service<name> Name of the service VLAN uplink

vid_ begin<vid> Starting VLAN ID of the service VLAN 100
vid_ end<vid> Ending VLAN ID of the service VLAN 100
uplink<port-No> Port of the uplink service VLAN 19:SFP1
Configuring Tag processing mode
the local end u In the "tagged" mode, the VLAN tags of the
VLAN service uplink data packets will not be stripped when

[untagged| tagged] they pass the uplink port. untagged
u In the "untagged" mode, the VLAN tags of
the uplink data packets will be stripped when
they pass the uplink port.
{service_type <1-8>}*1 Type of service VLAN Data
super_vlan <1-4095> Super VLAN ID 1
Binding
Starting value of the Sub VLAN ID range. The
service VLAN psub-vlan <vid_begin> 100
value ranges from 1 to 4085.
to Super
Ending value of the Sub VLAN ID range. The
VLAN {<vid_end>}*1 100
value ranges from 1 to 4085.
The destination IP address. It is usually in the

destination <A.B.C.D> 10.98.20.2
Configuring format of network segment.
static routing gateway <A.B.C.D> Gateway address 192.168.1.254
mask <A.B.C.D> Subnet mask 255.255.255.0
global [enable|
Enable or disable the DHCP function globally. enable
disable]
Switch for the Ping function or the times of Ping
DHCP global test. The default value is 2. When the parameter
ping-function <0-3> 2
switch is set to 0, the Ping function is disabled, and the
second parameter becomes invalid.
ping-interval <500- The Ping interval (unit: ms). The default value is
500
5000> 500 ms.
Configuring super-vlan <1–4095> Super VLAN ID 1

DHCP Set the DHCP mode of the Super VLAN to
mode [server|relay|
interface "server", "relay" or "disable". The default setting relay
disable]
mode is "disable".
Configuring super-vlan <1–4095> Super VLAN ID 1

the interface Configure the DHCP server IP addresses for the
server server-ip <A.B.C.D> Super VLAN. Up to 16 IP addresses can be 10.98.20.2
address configured.
68 Version: A
7.2.2.4 Procedures of Configuring DHCP Relay with OLT

Equipment Serving as Proxy

Admin\vlan#set service_vlan uplink vlan_begin 100 vlan_end 100
Admin\vlan#
2. Add ports to the VLAN.

Admin\vlan#add vlan vlan_begin 100 vlan_end 100 untag uplink slot 19 port 1
Admin\vlan#
3. Create Super VLANs.

Admin\interface#create super_vlan 1
Admin\interface#
4. Bind service VLANs to Super VLANs.

Admin\interface#set super-vlan 1 add sub-vlan 100
Admin\interface#
5. Configure the VLAN IP address.

Admin\interface#set super-vlan 1 ip 192.168.1.100 mask 255.255.255.0
Admin\interface#
6. Configure the static routing.

Admin\protocol#set static–route destination–ip 10.98.20.2 mask 255.255.255.0 nexthop
192.168.1.254 metric 0
Admin\protocol#
7. Enable DHCP function globally.

Admin\protocol\dhcp#set dhcp global enable
Admin\protocol\dhcp#set dhcp global ping-function 2 ping-interval 500
Admin\protocol\dhcp#
8. Configure the DHCP interface mode.
Version: A 69
Admin\protocol\dhcp#set dhcp super-vlan 1 mode relay
9. Configure the interface server address.

Admin\protocol\dhcp#set dhcp relay super-vlan 1 server-ip 10.98.20.2
10. Configuration result.
The AN5116-06B/AN5516-06/AN5516-04 converts the DHCP broadcast

messages of the DHCP Client into the unicast messages and forcibly forwards
the DHCP request to the designated DHCP server.
7.2.3 Configuring DHCP Relay with OLT Equipment Serving

as Both Proxy and Gateway
The following introduces how to configure DHCP Relay when the AN5116-06B/
AN5516-06/AN5516-04 serves as both proxy and gateway.
Figure 7-6 shows the network diagram for configuring the OLT as DHCP proxy and
gateway.
Figure 7-6 Network Diagram for Configuring the OLT as DHCP Proxy and Gateway
70 Version: A
When the OLT serves as DHCP proxy, it converts the broadcast DHCP request
messages received from the DHCP Client to the unicast messages, and replaces
the gateway IP address in the messages with the IP address of the downlink Super
VLAN. By configuring the IP address of the Super VLAN, the OLT can also function
as the gateway and forward the unicast messages to the DHCP server in a different
network segment.
u Fan card
u PON service card
u Matching PDP
Figure 7-7 shows the flow of configuring the OLT as both DHCP proxy and gateway.
Version: A 71
Figure 7-7 Flow of Configuring the OLT as DHCP Proxy and Gateway
Table 7-4 shows the planning data for configuring the OLT as both DHCP proxy and
gateway.
Table 7-4 Configuring the OLT as Both DHCP Proxy and Gateway
service<name> Name of the service VLAN uplink downlink

Configuring the Starting VLAN ID of the service
vid_ begin<vid> 100 200
local end outer VLAN
VLAN data Ending VLAN ID of the service
vid_ end<vid> 100 200
VLAN
72 Version: A
Table 7-4 Configuring the OLT as Both DHCP Proxy and Gateway (Continued)

{service_type <1-
Type of service VLAN Data
8>}*1
The tag processing mode
u In the "tagged" mode, the
data packets will not be
[untagged| tagged] uplink port. untagged tagged
Adding ports to VLAN tags of the uplink
the VLAN data packets will be
uplink port.
Number of the slot

uplink<port-No> 19:SFP1 All slots
accommodating the uplink port
super_vlan <1-
Super VLAN ID 1 2
4095>
Starting value of the Sub VLAN
psub-vlan <vid_
ID range. The value ranges from 100
Binding Super begin>
1 to 4085.
VLAN to service
Ending value of the Sub VLAN
VLAN
{<vid_end>}*1 ID range. The value ranges from 200
1 to 4085.
vid_<vid> Super VLAN ID 1 2
Configuring the
192.168.1.
VLAN IP The IP address added to the 10.98.20.1/255.
IP <A.B.C.D> 254/255.255.
address Super VLAN 255.255.0
255.0
global [enable| Enable or disable the DHCP
enable
disable] function globally.
Switch for the Ping function or

the times of Ping test. The
default value is 2. When the
ping-function <0-
DHCP global parameter is set to 0, the Ping 2
3>
switch function is disabled, and the
second parameter becomes
invalid.
ping-
The Ping interval (unit: ms). The
interval <500- 500
default value is 500 ms.
5000>
Version: A 73
Table 7-4 Configuring the OLT as Both DHCP Proxy and Gateway (Continued)

super-vlan <1–
Super VLAN ID 2
4095>
Configuring
Set the DHCP mode of the
DHCP interface
mode [server| Super VLAN to "server", "relay"
mode Relay
relay|disable] or "disable". The default setting
is "disable".
super-vlan <1–
Super VLAN ID 2
4095>
Configuring the
Configure the DHCP server IP
interface server
server-ip <A.B.C. addresses for the Super VLAN.
address 10.98.20.2
D> Up to 16 IP addresses can be
configured.
7.2.3.4 Procedures of Configuring DHCP Relay with the OLT

Equipment Serving as Both Proxy and Gateway

Admin\vlan#
Admin\vlan#set service_vlan 200 downlink type data
Admin\vlan#set service_vlan downlink vlan_begin 200 vlan_end 200
Admin\vlan#

Admin\vlan#add vlan vlan_begin 100 vlan_end 200 untag slot 19 port 1
Admin\vlan#

74 Version: A
Admin\interface#

Admin\interface#
Admin\interface#

Admin\interface#
Admin\interface#
6. Enable DHCP function globally.



The OLT converts the DHCP broadcast messages of the DHCP Client into the
unicast messages and forwards the DHCP request to the designated DHCP
server.
7.2.4 Configuring DHCP Option60
The following introduces how to configure the DHCP Option60 function for the
AN5116-06B/AN5516-06/AN5516-04.
Version: A 75
The following introduces how to configure and implement the DHCP Option60
authentication function.
Service Planning
The AN5116-06B/AN5516-06/AN5516-04 provides DHCP Option 60 authentication

function. Thus, the Option 60 character authentication can be implemented for PC1
and PC2 users. Two Super VLANs are provided at the AN5116-06B/AN5516-06/
AN5516-04 and bound to Sub VLAN. Then, the authentication service can be
provided by proxy forwarding and character identification.
Network Scenario
Figure 7-8 shows the network for the DHCP Option 60 authentication scenario.
Figure 7-8 Network Diagram for the DHCP Option 60 Function
u Fan card
u PON service card
u Matching PDP
76 Version: A
Figure 7-9 shows the flow of configuring DHCP Option 60 function.
Figure 7-9 Flow of Configuring the DHCP Option60 Function
Version: A 77
Table 7-5 describes the planning data for configuring the DHCP Option 60 function
for the AN5116-06B/AN5516-06/AN5516-04.
Table 7-5 Planning Data for Configuring the DHCP Option60 Function
service<name> Name of the service VLAN downlink uplink
Starting VLAN ID of the

vid_ begin<vid> 10 20
Configuring the local service VLAN
end outer VLAN Ending VLAN ID of the
vid_ end<vid> 10 20
data service VLAN
{service_type <1-
Type of the service VLAN Data
8>}*1
Tag processing mode
u In the "tagged" mode,
the VLAN tags of the
uplink data packets will
not be stripped when
they pass the uplink
[untagged| tagged] tagged tagged
port.
u In the "untagged" mode,
Adding ports to the the VLAN tags of the
VLAN uplink data packets will
be stripped when they
pass the uplink port.
Number of the slot

uplink<port-No> accommodating the uplink All slots 19:4
port
super_vlan <1-
Super VLAN ID 1 2
4095>
Starting value of the Sub
psub-vlan <vid_
VLAN ID range. The value 10
begin>
Binding Super VLAN ranges from 1 to 4085.
to service VLAN Ending value of the Sub
{<vid_end>}*1 VLAN ID range. The value 20
ranges from 1 to 4085.
vid_<vid> Super VLAN ID 1 2
Configuring the The IP address added to the
IP <A.B.C.D> 1.1.1.1 2.2.2.2
VLAN IP address Super VLAN
mask <A.B.C.D> Subnet mask 255.255.255.0 255.255.255.0
78 Version: A
Table 7-5 Planning Data for Configuring the DHCP Option60 Function (Continued)
The IP address added to the

IP <A.B.C.D> second 8.8.8.1 -
Super VLAN
mask <A.B.C.D> Subnet mask 255.255.255.0 -
global [enable| Enable or disable the DHCP
enable
disable] function globally.
Switch for the Ping function

or the times of Ping test. The
ping-function <0-
parameter is set to 0, the 2
DHCP global switch 3>
Ping function is disabled,
and the second parameter
becomes invalid.
ping-
The Ping interval (unit: ms).
interval <500- 500
The default value is 500 ms.
5000>
super-vlan <1–
Super VLAN ID 1 -
4095>
Configuring DHCP Set the DHCP mode of the
interface mode mode [server| Super VLAN to "server",
Relay -
relay|disable] "relay" or "disable". The
default setting is "disable".
Configure the DHCP server

Configuring the IP addresses for the Super
server-ip <A.B.C.
interface server VLAN. Up to 16 IP 2.2.2.5
D>
address addresses can be
configured.

IP addresses for the Super
server-ip <A.B.C.
VLAN. Up to 16 IP 1.1.1.1
D>
addresses can be
Configuring Option
configured.
60 Information for
Enter the Option 60
the Interface
information for the DHCP
option60 <> Client end. The text entered aaaa
can contain 128 characters
at most.
Version: A 79
Table 7-5 Planning Data for Configuring the DHCP Option60 Function (Continued)
Available operation types

include "Set" and "Delete".
Type u "Set" means adding. Set
u "Delete" means
deleting.

IP addresses for the Super
server-ip <A.B.C.
VLAN. Up to 16 IP 8.8.8.1
D>
addresses can be
configured.
Enter the Option 60

information for the DHCP
option60 <> Client end. The text entered bbbb
can contain 128 characters
at most.
Available operation types
include "Set" and "Delete".
Type u "Set" means adding. Set
u "Delete" means
deleting.
7.2.4.4 Procedures of Configuring DHCP Option60

Admin\vlan#set service_vlan 10 downlink type data
Admin\vlan#set service_vlan downlink vlan_begin 10 vlan_end 10
Admin\vlan#
Admin\vlan#
80 Version: A
Admin\vlan#
Admin\vlan#add vlan vlan_begin 10 vlan_end 20 tag slot 19 port 4
Admin\vlan#

Admin\interface#

Admin\interface#
Admin\interface#
5. Configure VLAN IP addresses.

Admin\interface#
Admin\interface#
6. Enable the DHCP function globally.



9. Configure the Option 60 information for the interface.
Version: A 81
Admin\protocol\dhcp#set dhcp super-vlan 1 relay-ip 1.1.1.1 option60 aaaa
Admin\protocol\dhcp#set dhcp super-vlan 1 relay-ip 8.8.8.1 option60 bbbb
The OLT converts the DHCP broadcast messages received from DHCP Client
into unicast messages and forwards the DHCP Option 60 information to the
designated DHCP server for authentication.
7.2.5 Configuring DHCP Server
The following introduces how to configure the AN5116-06B/AN5516-06/AN5516-04

as DHCP Server.
Service Planning
Use the OLT equipment to provide DHCP Server service for the accessing
subscribers directly.
Network Scenario
Figure 7-10 shows the network diagram when the OLT serves as DHCP Server.
Figure 7-10 Network Diagram for Configuring the OLT as DHCP Server
82 Version: A
When serving as DHCP Server and having received the broadcast DHCP request
messages from DHCP Client, the OLT directly allocates the IP address in the IP
address pool to the user.
u Fan card
u PON service card
u Matching PDP
Figure 7-11 shows the flow of configuring the OLT as DHCP Server.
Version: A 83
Figure 7-11 Flow of Configuring the OLT as DHCP Server
Table 7-6 shows the planning data for the OLT serving as DHCP server.
Table 7-6 Configuring the OLT as DHCP Server
Configuring the local service<name> Name of the service VLAN uplink

end outer VLAN Starting VLAN ID of the service
vid_ begin<vid> 100
data VLAN
84 Version: A
Table 7-6 Configuring the OLT as DHCP Server (Continued)

vid_ end<vid> 100
VLAN
{service_type <1-8>}*1 Type of the service VLAN Data
Number of the slot
uplink<port-No> 19:SFP1
Tag processing mode

Adding ports to the data packets will not be
VLAN stripped when they pass
[untagged| tagged] the uplink port. UNTAG
data packets will be
the uplink port.
Binding Super VLAN {service_ type<1-8>}*1 Select the VLAN type. supervlan
to service VLAN ID of the Sub VLAN bound to
sub_vlan <1-4095> 100
the Super VLAN
vid_<vid> Super VLAN ID 1
Configuring the
The IP address added to the 192.168.1.100/255.
VLAN IP address IP <A.B.C.D>
Super VLAN 255.255.0
Enable or disable the DHCP
global [enable|disable] enable
function globally.
Switch for the Ping function or

the times of Ping test. The
DHCP global switch ping-function <0-3> parameter is set to 0, the Ping 2
function is disabled, and the
second parameter becomes
invalid.
The Ping interval (unit: ms). The
ping-interval <500-5000> 500
default value is 500 ms.
Configuring DHCP
super-vlan <1–4095> Super VLAN ID 1
interface mode
Version: A 85
Table 7-6 Configuring the OLT as DHCP Server (Continued)
Set the DHCP mode of the

mode [server|relay| Super VLAN to "server", "relay"
Server
disable] or "disable". The default setting
is "disable".
pool-id ID of the address pool 1
Starting address of the address 192.168.1.1/255.255.
begin-ip
pool 255.0
Configuring the IP Ending address of the address 192.168.1.20/255.255.
end-ip
address pool pool 255.0
gateway Gateway address 192.168.1.254
Leasing term of the address
lease 00100:00:00
pool
ip-pool <1-16> Number of the address pool 1
Configuring the DNS
dns-server <A.B.C.D> Address of the DNS server 10.19.8.10
server list
Type Select "set". set
7.2.5.4 Procedures of Configuring DHCP Server

Admin\vlan#

Admin\vlan#add vlan vlan_begin 100 vlan_end 100 untag uplink slot 19 port 1
Admin\vlan#
3. Create a Super VLAN.

Admin\interface#
4. Bind the service VLAN to the Super VLAN.
86 Version: A
Admin\interface#

Admin\interface#
6. Enable the DHCP function globally.


Admin\protocol\dhcp#set dhcp super-vlan 1 mode server
8. Configure the IP address pool.

Admin\protocol\dhcp#set dhcp server ip-pool 1 begin-ip 192.168.1.1 end-ip 192.168.1.20
mask 255.255.255.0 gateway 192.168.1.254
Admin\protocol\dhcp#set dhcp server ip-pool 1 lease 86400
9. Configure the DNS server list.

Admin\protocol\dhcp# set dhcp server ip-pool 1 dns-server 10.19.8.10
7.2.6 Configuring DHCP Snooping
The following introduces how to configure the DHCP Snooping function for the
AN5116-06B/AN5516-06/AN5516-04.
Figure 7-12 shows the network diagram for the OLT serving as DHCP Snooping.
Version: A 87
Figure 7-12 Network Diagram for Configuring the DHCP Snooping Function for the OLT
After the DHCP Snooping function is enabled for it, the OLT will transmit the
broadcast DHCP request message received from the DHCP Client to the DHCP
Server, and prevent the DHCP Server spoofing by filtering the response packets
transmitted by the DHCP Server.
u Fan card
u PON service card
u Matching PDP
The flow of configuring the DHCP Snooping function for the OLT is shown in
Figure 7-13.
88 Version: A
Figure 7-13 Flow of Configuring the DHCP Snooping Function for the OLT
Table 7-7 shows the planning data for configuring the DHCP Snooping function for
the OLT.
Table 7-7 Planning Data for Configuring the DHCP Snooping Function for the OLT

service<name> Name of the service VLAN Data
vid_ begin<vid> 300
Configuring the local end VLAN
outer VLAN data Ending VLAN ID of the service
vid_ end<vid> 300
VLAN
{service_type <1-8>}*1 Type of the service VLAN Data
Adding ports to the VLAN Number of the slot
Version: A 89
Table 7-7 Planning Data for Configuring the DHCP Snooping Function for the OLT (Continued)
Tag processing mode

VLAN tags of the uplink data
packets will not be stripped
when they pass the uplink
[untagged| tagged] port. untagged
VLAN tags of the uplink data
packets will be stripped
when they pass the uplink
port.
DHCP Snooping switch [enable|disable] DHCP Snooping function switch enable

DHCP Snooping trusted Number of the slot
ports accommodating the uplink port
7.2.6.4 Procedures of Configuring DHCP Snooping

Admin\vlan#set service_vlan 300 data type data
Admin\vlan#set service_vlan data vlan_begin 300 vlan_end 300
Admin\vlan#

Admin\vlan#
3. Enable the DHCP Snooping function.

Admin\service#set dhcp snooping enable
Admin\service#
4. Configure the DHCP Snooping trusted port.

Admin\service#set dhcp snooping port 19:1 trust
90 Version: A
Admin\service#
The OLT does not process user messages. Instead, it allocates to users only
the IP addresses assigned by the DHCP Server connected to the trusted port.
7.3 Configuring the ARP Proxy Function
The following introduces how to configure the ARP proxy function for the AN5116-
06B/AN5516-06/AN5516-04.
ARP proxy can be configured flexibly, and different configuration methods can be
applied to different network plans.
The configuration planning for ARP proxy mainly covers the following aspects:
u How many user service VLANs are there? How many Sub VLANs are needed
to correspond to the user service VLANs? And how many Super VLANs need
to be bound?
u Is the VLAN IP address configured on the Sub VLAN or Super VLAN?
u How to bind multiple Sub VLANs and Super VLANs?
Different combinations of configuration modes can be applied to the aspects

mentioned above to cater for network demands. In practice, prior to configuration,
users need to learn of network environment and features, collecting information
such as VLAN allocation and the network segment where the users are located.
7.3.2 Configuring ARP Proxy in the Same-VLAN and Same-

network Segment Application
The following introduces how to configure and implement the ARP proxy function
among user devices in the same-VLAN and same-network segment application.
Version: A 91
Service Planning
The AN5116-06B/AN5516-06/AN5516-04 serves as ARP proxy to allow

internetworking among users in the same network segment (10.90.10.0/24) in the
same VLAN. A Super VLAN is provided at the AN5116-06B/AN5516-06/AN5516-04
and bound with Sub VLAN. The ARP proxy service is then provided through L3
forwarding.
Network Scenario
Figure 7-14 shows the network diagram for ARP proxy in the same-VLAN and
same-network segment application.
Figure 7-14 Network Diagram for the ARP Proxy in the Same-VLAN and Same-Network
Segment Application
Two subscriber PCs, both of which belong to the VLAN with the ID 1000, are
connected to the AN5116-06B/AN5516-06/AN5516-04 via ONUs.
The IP addresses of the two PCs are 10.90.10.1 and 10.90.10.2 respectively.
Configure a Super VLAN and a Sub VLAN at the AN5116-06B/AN5516-06/AN5516-
04, and bind them together. After the VLAN IP address is set for the Super VLAN,
the ARP proxy service can be provided by means of L3 forwarding.
u Fan card
92 Version: A
u PON service card
u Matching PDP
Figure 7-15 shows the flow of configuring ARP proxy in the same-VLAN and same-
network segment application.
Figure 7-15 Flow of Configuring the ARP Proxy
Table 7-8 shows the planning data for configuring the ARP proxy function for the
AN5116-06B/AN5516-06/AN5516-04 in the same-VLAN and same-network
segment application.
Version: A 93
Table 7-8 Planning Data for Configuring ARP Proxy in the Same-VLAN and Same-network
Segment Application

super vlan vid Super VLAN ID 10
Binding Sub VLAN to Super
sub vlan begin id Starting Sub VLAN ID 1000
VLAN
sub vlan end id Ending Sub VLAN ID 1000
Enter the ID of the VLAN to
Vlan vid be configured with an IP 10
Configuring the VLAN IP
address.
address
Set the primary IP address of
ipv4 <A.B.C.D> 10.90.10.10/255.255.255.0
the VLAN.
routeArp State of the Route ARP
enable
proxy switch
Enabling the ARP proxy interVlanArp State of the inter-VLAN ARP

enable
function in the VLAN proxy switch
innerVlanArp State of the intra-VLAN ARP
enable
proxy switch
7.3.2.4 Procedures of Configuring ARP Proxy in the Same-VLAN

and Same-network Segment Application
1. Bind Sub VLAN to Super VLAN.
1) Create the Super VLAN.

Admin\interface#
2) Bind the Sub VLAN to the Super VLAN.

Admin\interface#

Admin\interface#set vlan 10 ipv4 10.90.10.10 mask 255.255.255.0
Admin\interface#
3. Enable the ARP proxy function in the VLAN.
94 Version: A
Admin\interface#set arp-switch 10 route enable inner-subvlan enable among-subvlan

enable
Admin\interface#
After the configuration is completed, the two subscribers' PCs can access each
other normally.
7.3.3 Configuring ARP Proxy in the Cross-VLAN and Same-

among user devices in the cross-VLAN and same-network segment application.
Service Planning
Enable internetworking among subscribers in different VLANs but same network

segment (10.90.10.0/24) via the ARP proxy function provided by the .
Network Scenario
Figure 7-16 shows the network diagram for the ARP proxy in the cross-VLAN and
same-network segment application.
Figure 7-16 Network Diagram for the ARP Proxy in the Cross-VLAN and Same-Network
Segment Application
Version: A 95
Two subscriber PCs are connected to the AN5116-06B/AN5516-06/AN5516-04

through ONUs. The two PCs belong to the VLANs with the IDs 1000 and 2000
respectively, and their IP addresses are 10.90.10.1 and 10.90.10.2 respectively. You
need to configure a Super VLAN at the AN5116-06B/AN5516-06/AN5516-04 and
bind it with two Sub VLANs to provide the ARP proxy service.
u Fan card
u PON service card
u Matching PDP
Figure 7-17 shows the flow of configuring ARP proxy in the cross-VLAN and same-
96 Version: A
AN5116-06B/AN5516-06/AN5516-04 in the cross-VLAN and same-network
segment application.
Table 7-9 Planning Data for Configuring the ARP Proxy Function in the Cross-VLAN and
Same-network Segment Application

Binding Sub VLAN to Super
VLAN
Enter the ID of the VLAN to be
Vlan vid 10
Configuring the VLAN IP configured with an IP address.
address Set the primary IP address of
ipv4 <A.B.C.D> 10.90.10.10/255.255.255.0
the VLAN.
State of the Route ARP proxy
routeArp enable
switch
Enabling the ARP proxy State of the inter-VLAN ARP

interVlanArp enable
function in the VLAN proxy switch
State of the intra-VLAN ARP

innerVlanArp enable
proxy switch
7.3.3.4 Procedures of Configuring ARP Proxy in the Cross-VLAN

and Same-network Segment Application
1. Bind Sub VLANs to Super VLAN.

Admin\interface#
2) Bind Sub VLANs to the Super VLAN.

Admin\interface#
Version: A 97

Admin\interface#

enable
Admin\interface#
After the configuration is completed, two subscribers' PCs can access each
other normally.
7.3.4 Configuring ARP Proxy in the Same-VLAN and Multi-

among user devices in the same-VLAN and multi-network segment application.
Service Planning
Enable internetworking among subscribers in different network segments of the

same VLAN via the ARP proxy function provided by the AN5116-06B/AN5516-06/
AN5516-04.
Network Scenario
Figure 7-18 shows the network diagram for the ARP proxy function in the same-
VLAN and multi-network segment application.
98 Version: A
Figure 7-18 Network Diagram for the ARP Proxy in the Same-VLAN and Multi-Network
Segment Application

through ONUs. The two PCs belong to the same VLAN with the ID 1000, but they
are in different network segments. Their IP addresses are 10.90.10.1 and
10.98.20.2 respectively. You need to configure a Super VLAN and a Sub VLAN at
the AN5116-06B/AN5516-06/AN5516-04 and bind them together, and then
configure two VLAN IP addresses for the Super VLAN to provide ARP proxy service
crossing network segments.
u Fan card
u PON service card
u Matching PDP
Version: A 99
Figure 7-19 shows the flow of configuring ARP proxy in the same-VLAN and multi-
AN5116-06B/AN5516-06/AN5516-04 in the same-VLAN and multi-network segment
application.
Table 7-10 Planning Data for Configuring the ARP Proxy Function in the Same-VLAN and
Multi-network Segment Application

Binding Sub VLAN
to Super VLAN
Vlan vid 10
Configuring the configured with IP addresses.
VLAN IP address Set the primary IP address of the
ipv4 <A.B.C.D> 10.90.10.10/255.255.255.0
VLAN.
100 Version: A
Table 7-10 Planning Data for Configuring the ARP Proxy Function in the Same-VLAN and
Multi-network Segment Application (Continued)
Configure the secondary IP

address for the VLAN. In this
{[secondary]}*1 example, the secondary IP 10.98.20.10/255.255.255.0
address is used for another
network segment.
State of the Route ARP proxy

routeArp enable
switch
Enabling the ARP
State of the inter-VLAN ARP
proxy function in the interVlanArp enable
proxy switch
VLAN
State of the intra-VLAN ARP
innerVlanArp enable
proxy switch
7.3.4.4 Procedures of Configuring ARP Proxy in the Same-VLAN

and Multi-network Segment Application
1. Bind Sub VLAN to Super VLAN.

Admin\interface#
2) Bind Sub VLAN to Super VLAN.

Admin\interface#

Admin\interface#set vlan 10 ipv4 10.98.20.10 mask 255.255.255.0 secondary
Admin\interface#

enable
Admin\interface#
Version: A 101
other normally.
7.3.5 Configuring ARP Proxy in the Cross-VLAN and Multi-

among user devices in the cross-VLAN and multi-network segment application.
Service Planning
Enable internetworking between two subscribers in different VLANs and different

network segments via the ARP proxy function provided by the AN5116-06B/
AN5516-06/AN5516-04.
Network Scenario
Figure 7-20 shows the network diagram for the ARP proxy in the cross-VLAN and
multi-network segment application.
Figure 7-20 Network Diagram for the ARP Proxy in the Cross-VLAN and Multi-Network
Segment Application
102 Version: A

through ONUs. The two PCs are in different VLANs and different network segments.
To enable internetworking, you need to configure two Super VLANs at the AN5116-
06B/AN5516-06/AN5516-04, and bind them with two Sub VLANs. Meanwhile, you
need to configure IP addresses corresponding to different network segments for the
two Super VLANs respectively to enable data forwarding crossing network
segments and VLANs.
u Fan card
u PON service card
u Matching PDP
Figure 7-21 shows the flow of configuring the ARP proxy in the cross-VLAN and
multi-network segment application.
Version: A 103
AN5116-06B/AN5516-06/AN5516-04 in the cross-VLAN and multi-network segment
application.
Multi-network Segment Application

super vlan vid Super VLAN ID 10 20
Binding Sub VLAN
sub vlan begin id Starting Sub VLAN ID 1000 2000
to Super VLAN
sub vlan end id Ending Sub VLAN ID 1000 2000
Vlan vid 10 20
configured with IP addresses.
Set the primary IP address of the

ipv4 <A.B.C.D> 10.90.10.10/255.255.255.0
VLAN.
Configuring the
Configure the secondary IP
VLAN IP address
address for the VLAN. In this
{[secondary]}*1 example, the secondary IP address 10.98.20.10/255.255.255.0
is used for another network
segment.
104 Version: A
Multi-network Segment Application (Continued)

routeArp State of the Route ARP proxy
enable
switch
Enabling the ARP
interVlanArp State of the inter-VLAN ARP proxy
proxy function in the enable
switch
VLAN
innerVlanArp State of the intra-VLAN ARP proxy
enable
switch
7.3.5.4 Procedures of Configuring ARP Proxy in the Cross-VLAN

and Multi-network Segment Application
1. Bind Sub VLANs to Super VLANs.
1) Create Super VLANs.

Admin\interface#
2) Bind Sub VLANs to Super VLANs.

Admin\interface#

Admin\interface#

enable

enable
Admin\interface#
Version: A 105
other normally.
7.4 Configuring QoS Functions
The following introduces how to configure QoS functions for the OLT equipment.
u Filter service flows meeting the conditions defined in the traffic rules to prepare
for QoS processing. The rule types include source MAC address, destination
MAC address, source IP address, destination IP address, L4 source port No.,
L4 destination port No. and Ethernet type, etc.
u Perform QoS functions, including enabling ACL, remarking CoS, DSCP, TC and
SVLAN, port re-direction, flow mirroring, rate control, and so on, on the packets
filtered out according to users' demands.
u Limit for application:
4 When port mirroring is configured, flow mirroring cannot be enabled.
4 SVLAN remarking cannot be configured together with COS remarking,

DSCP remarking, TC remarking, port re-direction, and flow mirroring.
4 Rate control cannot be configured when ACL is enabled.
Service Planning
Bind a QoS profile to a slot or an uplink port, so that QoS processing can be
implemented on the uplink and downlink traffic according to the rules defined in the
QoS profile.
106 Version: A
Network Scenario
Bind a QoS profile to a slot or an uplink port, so that QoS processing can be
implemented on the uplink and downlink traffic according to the rules defined in the
QoS profile. The uplink traffic is transmitted from a line card to an uplink port, while
the downlink traffic is transmitted from an uplink port to a line card.
u Fan card
u PON service card
u Matching PDP
The other hardware items needed include the ONUs, network cables, optical fibers,
and so on.
Figure 7-22 shows the flow of configuring QoS.
Version: A 107
Figure 7-22 Flow of Configuring QoS
7.4.4 Planning Data
The planning data for configuring QoS are shown in Table 7-12.
Table 7-12 Planning Data for Configuring QoS
User-defined traffic rule profile ID, starting

flow_rule_profile <id> 4
from 4.
Traffic rules
<name> Name of traffic rule profile acc_0
<itemNum> Quantity of rule items 1
108 Version: A
Table 7-12 Planning Data for Configuring QoS (Continued)
Rule IDs:
u 0-sMac
u 1-dMac
u 2-sIp
u 3-dIp
u 4-svlan
u 5-ethType
u 6-ipProType
u 7-cos
u 8-dscp
<rulefiled> 10
u 9-L4SrcPort
u 10-L4DesPort
u 11-ttc
u 12-cvlan
u 13-dIPPre
u 14-sIpPre
u 15-ipVersion
u 16-traffic Class
u 17-traffic Lable
u 18-nPktHd
[range|value_mask|equal|
Only "value_mask" and "equal" are
not_equal|exist_match|not_ equa
supported.
exist_match]
<value1> Value set for Rulefield 5101

When rulefiled is set to "value_mask",
<value2> enter the mask actually used; otherwise, null
enter null.
low_policy_profile <prfId> Policy ID 1
[name] <prfName> Policy name acc_0
The policy priority level, ranging from 1 to

[pri] <1-12> 12. 1 stands for the lowest priority level, 1
and 12 the highest one.
Traffic policy [acl] [enable|disable] The ACL function switch enable

[forward] [enable|disable] The forwarding function switch enable
[re_cos] [enable|disable] The remarking function switch enable
[cos] <0-7> Priority label 5
[re_dscp] [enable|disable] The DSCP remarking function switch enable
[dscp] <0-63> The DSCP value 7
Version: A 109
Table 7-12 Planning Data for Configuring QoS (Continued)

[re_traff] [enable|disable] The remarking function switch disable
[traff] <traff> The traffic class value 0
[re_queue] [enable|disable] The queue mapping function switch disable
[queue] <0-7> The queue mapped 0
[re_port] [enable|disable] The port re-direction function switch disable
Number of the re-directed port. The uplink
[rdport] <port> 0
ports are numbered from 1 to 12.
[flow_mirr] [enable|
The flow mirroring function switch disable
disable]
Number of the mirror port. The uplink ports
[mirrport] <port> 0
are numbered from 1 to 12.
[rate_limit] [enable|
The rate limiting function switch disable
disable]
[cir] <cir> Committed information rate (kbit/s) 0
[cbs] <cbs> Committed burst size (Byte) 0
[ebs] <ebs> Excess burst size (Byte) 0
[pir] <pir> Peak information rate (kbit/s) 0
[re_vlan] [enable|disable] The VLAN remarking function switch enable
VLAN actions, including adding and
[vlanact][add|tras] tras
translation.
[vid] <1-4095> 1 to 4095 100
slot <slotno> Slot number 19
Binding the
port <portno> Port number 6
traffic policy to
<policyId> ID of traffic policy 2
the port
<ruleId> ID of traffic rule 5
7.4.5 Procedures of Configuring QoS Functions
1. Configure traffic rules.

Admin\qos#set flow_rule_profile 4 dis_5101 1 10 equal 5101 null
Admin\qos#set flow_rule_profile 5 mac1 1 0 equal 011a88888801 null
Admin\qos#set flow_rule_profile 6 IPV6 1 5 equal 34525 null
110 Version: A
Admin\qos#set flow_rule_profile 7 Discard_4005 1 4 equal 4005 null
Admin\qos#
2. Configure traffic policies.

Admin\qos#set flow_policy_profile 1 name IPV6 pri 1 acl enable forward disable
Admin\qos#set flow_policy_profile 2 name Discard_4005 pri 1 acl enable forward disable
Admin\qos# set flow_policy_profile 3 name dis_5101 pri 1 acl enable forward disable
Admin\qos#set flow_policy_profile 13 name mac1 pri 1 acl enable forward disable
Admin\qos#
3. Bind ports to profiles for traffic rules and policies.

Admin\qos#set slot 19 port 1 attach 1 6 2 7
Admin\qos# set slot 19 port 6 attach 3 4
Admin\qos#set slot 12 port 0 attach 13 5
Admin\qos#

Admin#save
Admin#
7.5 Configuring the LACP Function
The following introduces how to configure the LACP function for the AN5116-06B/
AN5516-06/AN5516-04.
Service Planning
Set the three uplink ports of the AN5116-06B/AN5516-06/AN5516-04 as the

member ports of the LACP protection group to enable link backup. Port 1 is used as
the master port, and the other two ports as the slave ports.
Network Scenario
The network diagram for the LACP function is shown in Figure 7-23.
Version: A 111
Figure 7-23 Network Diagram for Configuring the LACP Function
u Fan card
u PON service card
u Matching PDP
Figure 7-24 shows the flow of configuring the LACP function.
112 Version: A
Figure 7-24 Flow of Configuring LACP
7.5.3 Planning Data
In the following example of LACP configuration, the HU1A card is used as the uplink
card. Table 7-13 shows the planning data.
Table 7-13 Planning Data for LACP Configuration

Group Id Aggregation group ID 1
mode [manual|lacp] Aggregation mode LACP
Configure the load balancing mode. The
options available are as follows:
u SA: source MAC address
Configuring the u DA: destination MAC address
aggregation mode load_balance [SA|
u SDA: source and destination MAC
DA|SDA|SIP|DIP| SDA
addresses
SDIP]
u SIP: source IP address
u DIP: destination IP address
u SDIP: source and destination IP
addresses
trunk <1–64> Trunk group number 1
Configuring Trunk port
master_port Configure the slot number and port
link aggregation 19:SFP1
<slotid> <portid> number of the master port.
Version: A 113
Table 7-13 Planning Data for LACP Configuration (Continued)

mem_
Configure the slot numbers and port
port {<slotid> <por- 19:SFP2, 19:SFP3
numbers of member ports.
tid>}*8
Enable or disable the LACP function.
[enable|disable] u enable: Enable the function. enable
Configuring LACP
u disable: Disable the function.
System Priority System priority 32768
7.5.4 Procedures of Configuring the LACP Function
1. Configure the aggregation mode.

Admin\interface#create trunk 1
Admin\interface#set trunking groupno 1 mode lacp
Admin\interface#set trunking groupno 1 criteria sdmac
Admin\interface#
2. Configure the trunk port link aggregation.

Admin\interface#add trunk 1 slot 19 port 1
Admin\interface#
3. Configure the LACP.

Admin\protocol\lacp#set lacp enable
Admin\protocol\lacp#set lacp system-priority 32768
Admin\protocol\lacp#
The LACP function is configured. The ports 19:SFP1, 19:SFP2 and 19:SFP3
constitute a static LACP aggregation group to balance load among member
ports in the group and provide more reliable connection in the system.
114 Version: A
7.6 Configuring the MSTP Function
The following introduces how to configure the MSTP function for the AN5116-06B/
AN5516-06/AN5516-04.
Service Planning
The AN5116-06B/AN5516-06/AN5516-04 and two switches make up an MSTP

network. Two spanning trees corresponding to different VLAN IDs are configured.
Network Scenario
Figure 7-25 shows the network diagram for the MSTP function.
Figure 7-25 Network Diagram for the MSTP Function
Equipment A in the MST region is the AN5116-06B/AN5516-06/AN5516-04 with the

MSTP function enabled; Equipment B and C are switches, with C serving as the
region root.
Version: A 115
Each MST region can have multiple spanning trees (MST), and each spanning tree
corresponds to a spanning tree instance. Accordingly, an MST region may have
multiple spanning tree instances (MSTI). In this example, VLAN 10 is mapped to
MST1, while other VLANs are mapped to MST0.
Figure 7-26 Mappings Between Spanning Trees and VLANs
u Fan card
u PON service card
u Matching PDP
Figure 7-27 shows the flow of configuring the MSTP function.
116 Version: A
Figure 7-27 Flow of Configuring the MSTP Function
7.6.3 Planning Data
To meet the requirements of networking for the MSTP function, users need to
configure MSTP on the three equipment sets A, B and C.
The following describes how to configure the MSTP service on the AN5116-06B/
AN5516-06/AN5516-04 (Equipment A) as an example. In this example, the HU1A
card in Slot 19 serves as the uplink card. Table 7-14 lists the planning data.
Version: A 117
Table 7-14 Planning Data for Configuring the MSTP Function
Configuring basic stp [enable|disable] Enabling/disabling STP enable

properties of bridge stp mode [mstp|rstp| stp] Protocol type MSTP
The forward_time value. The default
[default|<4-30>] 15
value is 15.
The hello_time value. The default value is
[default|<1-10>] 2
Configuring the 2.
bridge parameters The max-age value. The default value is
[default|<6-40>] 20
20.
The max-hops value. The default value is
[default|<1-40>] 20
20.
The bridge priority value, which is 32768
Configuring the priority [default|<0-
by default. The value entered must be a 32768
bridge priority 61440>]
multiple of 4096.
slotno Slot number 19
<portno> Port number 1
Set the port to autoedge or edgeport.
Configuring port [autoedge|edgeport] autoedge
The default setting is auto-autoedge.
parameters
Set the type of link where the port resides
point-to-point in the network. "Point-to-point" and point-to-point
"shared" are supported.
The revision level of the MSTP spanning

Revision 0
tree
Configuring the The domain name of the MSTP spanning
MST region tree. The value contains 1 to 32
region <name> MST1
characters. The default setting is the
MAC address of the current equipment.
Configuring basic
properties of the instance <0-64> Instance ID 1
instance
Configuring the The priority value of the instance. The
priority [default|<0-
priority of the bridge default setting is 32768, and the value 1
61440>]
instance entered must be a multiple of 4096.
Configuring the instance <0-64> Instance ID 1

instance tree <slotno> Slot number 19
parameters for the
<portno> Port number 1
port
118 Version: A
Table 7-14 Planning Data for Configuring the MSTP Function (Continued)
Set the path cost of the port in the

instance. The value ranges between 1
MSTI RegRoot/IRPC and 20000000000. The default value is 2000
20000000000/port rate (the rate unit is
kbps).
Set the port priority in the instance. The

value should be an integral multiplex of
Port Priority 128
16, and range between 0 and 240. The
default value is 128.
7.6.4 Procedures of Configuring the MSTP Function
1. Configure basic properties of the bridge.

Admin\protocol\stp#set stp enable
Admin\protocol\stp#set stp mode mstp
Admin\protocol\stp#set stp slot 19 port 1 enable
Admin\protocol\stp#
2. Configure the bridge parameters.

Admin\protocol\stp#set stp timer forward_time default
Admin\protocol\stp#set stp timer hello_time default
Admin\protocol\stp#set stp timer max_age default
Admin\protocol\stp#set stp timer max_hops default
Admin\protocol\stp#
3. Configuring the bridge priority.

Admin\protocol\stp#set stp priority default
Admin\protocol\stp#
4. Configure the MST region.

Admin\protocol\stp#set stp region_configuration region MST1
Admin\protocol\stp#set stp region_configuration revision default
Admin\protocol\stp#
Version: A 119
5. Configure basic properties of the instance.

Admin\protocol\stp#set stp region_configuration instance 1 vlan_id 10
Admin\protocol\stp#
6. Configuring parameters of the bridge instance.

Admin\protocol\stp#set stp instance 1 priority default
Admin\protocol\stp#
7. Configure instance tree parameters for the port.

Admin\protocol\stp#set stp instance 1 slot 19 port 1 priority default
Admin\protocol\stp#set stp instance 1 slot 19 port 1 pathcost default
Admin\protocol\stp#
4 In the physical loop composed of equipment sets A, B, and C, multiple

logical tree links are formed based on MSTP, so as to avoid infinite loop of
packets in the loop network.
4 The data from VLAN 10 and other VLANs are transmitted via different links
to share data load.
7.7 Configuring the RADIUS Function
The following introduces how to configure the RADIUS function for the AN5116-06B/
AN5516-06/AN5516-04.
Figure 7-28 shows the flow of configuring RADIUS.
120 Version: A
Figure 7-28 Flow of Configuring RADIUS
7.7.2 Planning Data
The AN5116-06B/AN5516-06/AN5516-04 serves as RADIUS client end. It encrypts

all the IP addresses and keys of connected PC users, and then forwards them to the
uplink RADIUS server for authentication. Table 7-15 shows the planning data for
configuring RADIUS.
Table 7-15 Planning Data for RADIUS Configuration

authentication-mode [local
Authentication Select RADIUS mode. RADIUS
| radius | tacacs]
The destination IP address of IP
ip-address <A.B.C.D> 10.190.44.19
messages.
Encrypted key for interacting with

key 123
the server
The authorized port for interacting
auth-port 1812
Radius server with the server
information The accounting port for interacting
acct-port 1813
with the server
The timeout period for connecting
timeout 3
to the server
retransmit Retransmission times 3
NAS-IP-Address OLT management IP address 10.1.2.220
Version: A 121
7.7.3 Procedures of Configuring the RADIUS Function
1. Configure the RADIUS authentication mode.

Admin\aaa#aaa authentication-mode radius
Admin\aaa#radius server bind 10.1.2.220
2. Configure RADIUS authentication information.

Admin\aaa#radius server ip-address 10.190.44.19 key 123
Admin\aaa#radius server ip-address 10.190.44.19 auth-port 1812
Admin\aaa#radius server ip-address 10.190.44.19 acct-port 1813
Admin\aaa#radius server ip-address 10.190.44.19 timeout 3
Admin\aaa#radius server ip-address 10.190.44.19 retransmit 3
Admin\aaa#
After RADIUS configuration is completed, users can log into the RADIUS
server by entering correct user name and password.
7.8 Configuring the Tacacs+ Function
The following introduces how to configure the Tacacs+ function for the AN5116-06B/
AN5516-06/AN5516-04.
The rules for configuring the Tacacs+ function on the AN5116-06B/AN5516-06/

AN5516-04 are described as follows:
u When configuring information about Tacacs+ server, you can save at most two
configuration items, corresponding to active and standby Tacacs+ servers
respectively. If there are already two configuration items, you cannot create
more items.
u If the Tacacs+ authentication service is invalid (e.g., as a result of

communication interruption), the local authentication mode will be used.
122 Version: A
u The Tacacs+ authentication mode has higher priority than other authentication
modes. A user who has already been authenticated in the Tacacs+ mode
cannot be further authenticated in the Local mode.
Service Planning
The user PC is directly connected to the AN5116-06B/AN5516-06/AN5516-04.

Authentication and login in the Tacacs+ mode are performed by command lines.
After logging into the Tacacs+ server successfully, the user can use the command
lines within the range of his/her authority.
Network Scenario
The network diagram for the AN5116-06B/AN5516-06/AN5516-04 to perform the

Tacacs+ function is shown in Figure 7-29.
Figure 7-29 Network Diagram for the Tacacs+ Authentication Function
The AN5116-06B/AN5516-06/AN5516-04 connects to the Tacacs+ server and

user's PC via the uplink card.
When the user tries to log in, the AN5116-06B/AN5516-06/AN5516-04 will receive
the request and query the user's login password and authority from the Tacacs+
server.
Version: A 123
u If the password is correct, the user can log into the OLT and can perform
operations within his/her authority using command lines. The Tacacs+ server
will record the user operations and keep account.
u If the password is incorrect, the user will receive a prompt message for login
failure.
Below are the hardware requirements for the above example.
u Fan card
u PON service card
u Matching PDP
The flow of configuring the Tacacs+ authentication function is shown in Figure 7-30.
Figure 7-30 Flow of Configuring Tacacs+
124 Version: A
7.8.4 Planning Data
Table 7-16 shows the planning data for configuring the Tacacs+ function for the
AN5116-06B/AN5516-06/AN5516-04.
Table 7-16 Planning Data for Configuring the Tacacs+ Function
host <A.B.C.D> The destination IP address of IP messages. 10.99.110.10 10.99.110.11

The encrypted key for interacting with the
Configuring key server. The key contains 0 to 255 49
information characters.
about the The port for interacting with the server. The
port 123
Tacacs+ value ranges from 1 to 65535.
server The timeout period for connecting to the
timeout server. The value ranges from 3 to 10 10
seconds.
Configuring
the authentication
Authentication mode Tacacs
authentication mode
mode
Configuring authorization
Authorization mode Tacacs
the mode
authorization authorization
The authorization command line mode Tacacs
mode command mode
Configuring accounting mode Accounting mode Tacacs
the accounting accounting
Accounting command line mode Tacacs
mode command mode
7.8.5 Procedures of Configuring the Tacacs Function
1. Configure information about the Tacacs+ server.

Admin\aaa#tacacs-server host 10.99.110.10 port 49
Admin\aaa#tacacs-server host 10.99.110.10 key 123
Admin\aaa#tacacs-server host 10.99.110.10 timeout 10
Admin\aaa#tacacs-server host 10.99.110.11 port 49
Admin\aaa#tacacs-server host 10.99.110.11 key 123
Version: A 125
Admin\aaa#tacacs-server host 10.99.110.11 timeout 10
Admin\aaa#
2. Configure the authentication mode.

Admin\aaa#aaa authentication-mode tacacs
Admin\aaa#
3. Configure the authorization mode.

Admin\aaa#aaa authorization-mode tacacs
Admin\aaa#aaa authorization-mode command tacacs
Admin\aaa#
4. Configure the accounting mode.

Admin\aaa#aaa accounting-mode tacacs
Admin\aaa#aaa accounting-mode command tacacs
Admin\aaa#
After completing the configuration, users can log in with the configured key.
Since authentication is implemented in the Tacacs+ mode, users cannot log in
with local user name and password.
4 Below is the echo information when the login fails.

Login:GEPON
Password:*****
BadUserNameorBadPassword,LoginFailed
Pleaseretry
Login
4 Below is the echo information when the login succeeds.

Login:admin
Password:*****
Admin#
After logging into the system successfully, users can perform the command line
operations in the allowed range of their authority. The users' operations will be
recorded and accounted by the Tacacs+ server.
126 Version: A
7.9 Configuring the Subscriber Line

Identification Function
The following introduces how to configure the subscriber line identifiers for the
AN5116-06B/AN5516-06/AN5516-04.
See below for details about custom line identifiers.
u The system defines some custom identifier variables. You can use these
variables in different combinations to enhance flexibility of the identification
function. Table 7-17 lists the custom identifier variables defined by the system.
Table 7-17 Custom Identifier Variables
Identifier Meaning Identifier Meaning
%s User outer VLAN %o ONU authorization number
%c User inner VLAN %n ONU type
%a Access node identifier %T Slot number of the MDU ONU

Rack number of the access Sub-slot number of the MDU
%r %M
node ONU
Subrack number of the access Number of UNI port on the
%f %P
node MDU ONU
%S Slot number of the access node %t Type of ONU user port
PON port No. of the access Port VPI or SVLAN

%p %X
node
Identifier (MAC) of ONU at the
%m %x Port VCI or CVLAN
access node
%u Uplink port type %l IAD IP address
%L Service card type %A IAD MAC address

IP address of OLT management
%O %B Access type: OTL, DSL or LAN
VLAN
u The custom format is subject to the following restrictions.
4 In the custom format, a variable identifier must be separated from the

subsequent character string or variable using a delimiter. The delimiter
used should be one of the characters listed in Table 7-18.
Version: A 127
Table 7-18 List of Delimiters
Separator Meaning
Space
. Decimal point
/ Slash
; Semicolon
: Colon
{ Open curly bracket
} Close curly bracket
< Open angle bracket
> Close angle bracket
[ Open square bracket
] Close square bracket
4 The character string in the custom format should contain no more than 256
characters.
4 The aforesaid delimiters are not allowed in the values of variables.
Figure 7-31 shows the flow of configuring the subscriber line identifier.
Figure 7-31 Flow of Configuring the Subscriber Line Identifier Management
128 Version: A
7.9.3 Planning Data
The planning data for the subscriber line identifier management are shown in
Table 7-19.
Table 7-19 Planning Data for the Subscriber Line Identifier Management
u enable: Enable the function.

[enable|disable] enable
u disable: Disable the function.
Format of the access node identifier
accessNodeIdentifier
A character string containing no more than AN5116-06B
Parameters for <identifier>
50 characters without spaces
subscriber line
Rack number of the access node. The value
identifier
ani_rack <0-15> range is 0 to 15. However, the valid value 1
management
range may vary with operators.
Frame number of the access node. The

ani_frame <0-31> value range is 0 to 31. However, the valid 1
value range may vary with operators.
u circuit_id: the line identifier format.

[circuit_id|remote_id] u remote_id: the remote end identifier circuit_id
format.
u <format_str>: the customized format
Line identifier
u ctc: the CTC format, which means the
format
standard of China Telecom
[<format_str>|ctc|cnc] ctc
Corporation.
u cnc: the CNC format, which means the
standard of China Netcom Corporation.
7.9.4 Procedures of Configuring the Subscriber Line

Identification Function
1. Configure the line identifier switch.

Admin\device\circuitid#set dhcp option82 enable
Admin\device\circuitid#set dhcp option18 enable
Admin\device\circuitid#set pppoe_plus enable
Admin\device\circuitid#
Version: A 129
Admin\device\circuitid#set dhcp option82 disable
Admin\device\circuitid#set dhcp option18 disable
Admin\device\circuitid#set pppoe_plus disable
2. Configure the line identifier format.

Admin\device\circuitid#set circuit_id format ctc
Admin\device\circuitid#set circuit_id format cnc
Admin\device\circuitid#set circuit_id format “scrafm”
The line identifier of the user equipment can be resolved successfully by the
packet capture software.
130 Version: A
Product Documentation Customer Satisfaction Survey
Thank you for reading and using the product documentation provided by FiberHome. Please take a moment to
complete this survey. Your answers will help us to improve the documentation and better suit your needs. Your
responses will be confidential and given serious consideration. The personal information requested is used for
no other purposes than to respond to your feedback.
Name
Phone Number
Email Address
Company
To help us better understand your needs, please focus your answers on a single documentation or a complete
documentation set.
Documentation Name
Code and Version
Usage of the product documentation:

1. How often do you use the documentation?
□ Frequently □ Rarely □ Never □ Other (please specify)
2. When do you use the documentation?
□ in starting up a project □ in installing the product □ in daily maintenance □ in trouble
shooting □ Other (please specify)
3. What is the percentage of the operations on the product for which you can get instruction from the
documentation?
□ 100% □ 80% □ 50% □ 0% □ Other (please specify)
4. Are you satisfied with the promptness with which we update the documentation?
□ Satisfied □ Unsatisfied (your advice)
5. Which documentation form do you prefer?
□ Print edition □ Electronic edition □ Other (please specify)
Quality of the product documentation:
1. Is the information organized and presented clearly?
□ Very □ Somewhat □ Not at all (your advice)
2. How do you like the language style of the documentation?
□ Good □ Normal □ Poor (please specify)
3. Are any contents in the documentation inconsistent with the product?
4. Is the information complete in the documentation?
□ Yes
□ No (Please specify)
5. Are the product working principles and the relevant technologies covered in the documentation sufficient for
you to get known and use the product?
□ Yes
□ No (Please specify)
6. Can you successfully implement a task following the operation steps given in the documentation?
□ Yes (Please give an example)
□ No (Please specify the reason)
7. Which parts of the documentation are you satisfied with?
8. Which parts of the documentation are you unsatisfied with?Why?
9. What is your opinion on the Figures in the documentation?
□ Beautiful □ Unbeautiful (your advice)
□ Practical □ Unpractical (your advice)
10. What is your opinion on the layout of the documentation?

□ Beautiful □ Unbeautiful (your advice)
11. Thinking of the documentations you have ever read offered by other companies, how would you compare
our documentation to them?
Product documentations from other companies:
Satisfied (please specify)
Unsatisfied (please specify)
12. Additional comments about our documentation or suggestions on how we can improve:
Thank you for your assistance. Please fax or send the completed survey to us at the contact information
included in the documentation. If you have any questions or concerns about this survey please email at
edit@fiberhome.com

AN5116-06B AN5516-06 AN5516-04 Optical Line Terminal Equipment CLI Configuration Guide (Version A) PDF

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

AN5116-06B AN5516-06 AN5516-04 Optical Line Terminal Equipment CLI Configuration Guide (Version A) PDF

Uploaded by

Copyright:

Available Formats

AN5116-06B/AN5516-06/

Optical Line Terminal Equipment

CLI Configuration Guide

FiberHome Telecommunication Technologies Co., Ltd.

We appreciate your business. Your satisfaction is our goal.

Fiberhome Telecommunication Technologies Co., Ltd.

Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

All rights reserved

No part of this document (including the electronic version) may be

1 Documentation Guide .....................................................................................1

2 Overview of the Configuration Flow .................................................................2

3 Logging into the Device...................................................................................3

3.1 Introduction to the Login Mode ..........................................................4

3.2 Logging into Hyper Terminal..............................................................4

3.3 Login Through Telnet ........................................................................6

4 Configuring the Management Channel ............................................................9

4.1 Network Planning ...........................................................................10

4.2 Planning Data ................................................................................. 11

4.3 Configuring the IP Address for In-Band Management.......................12

4.4 Configuring the IP Address for Out-of-Band Management ................12

4.5 Configuring Static Routing...............................................................12

5 Authorizing Card and ONU............................................................................14

5.1 Authorizing a Card ..........................................................................15

5.2 Authorizing an ONU ........................................................................15

6.1 Configuring Voice Services Based on H.248....................................19

6.1.1 Configuration Rules ..........................................................19

6.2 Configuring Voice Services Based on SIP .......................................26

6.2.1 Configuration Rules ..........................................................27

6.3 Configuring Data Services ..............................................................32

6.3.1 Configuration Rules ..........................................................32

6.4 Configuring Multicast Services ........................................................41

6.4.1 Configuration Rules ..........................................................41

6.5 Configuring the Wi-Fi Access Service..............................................48

6.5.1 Network Planning .............................................................48

7.1 Configuring the VEIP Function ........................................................56

7.1.1 Network Planning .............................................................56

7.2 Configuring the DHCP Function ......................................................64

7.2.1 Configuration Rules ..........................................................64

7.3 Configuring the ARP Proxy Function ...............................................91

7.3.1 Configuration Rules ..........................................................91

7.4 Configuring QoS Functions ...........................................................106

7.4.1 Configuration Rules ........................................................106

7.5 Configuring the LACP Function ..................................................... 111

7.5.1 Network Planning ........................................................... 111

7.6 Configuring the MSTP Function..................................................... 115

7.6.1 Network Planning ........................................................... 115

7.7 Configuring the RADIUS Function .................................................120

7.7.1 Configuration Flow..........................................................120

7.8.1 Configuration Rules ........................................................122

7.9 Configuring the Subscriber Line Identification Function ..................127

7.9.1 Configuration Rules ........................................................127

u Operation and maintenance engineers

Matching with the command line system of version 2016

This manual introduces the commonly used commands for

The AN5116-06B/AN5516-06/AN5516-04 can provide voice, data and multicast

Figure 2-1 Overview of the Configuration Flow

Introduction to the Login Mode

Logging into Hyper Terminal

Login Through Telnet

3.1 Introduction to the Login Mode

3.2 Logging into Hyper Terminal

The Windows XP operating system is used as an example here.