Opticalink G1000 GPON OLT Operation ManualV2.2

Opticalink G1000
GPON OLT
Operation Manual
Manual Version：V2.2
Product Version：V300
Opticalink G1000 GPON OLT Operation Manual
About This Manual

Related Manual
Manual Description
"Opticalink G1000 GPON OLT It introduces G1000 OLT devices basics,

Command Manual" system and device, VLAN, port, port
isolation, OLT, ONU, RSTP,
Link-Aggregation, Mirror, MAC address
table, QoS, ACL, IGMP, performance,
alarms and inband network management
modules.
"Opticalink G1000 GPON OLT It introduces the product, service boards,
Installation Manual" pre-installation preparation, installation,
hardware maintenance, software
maintenance, and troubleshooting of the
G1000 OLT.
Brief introduction to this manual
“Opticalink G1000 GPON OLT Operation Manual” mainly introduces the overview,
login, command line interface and view, system and equipment operation, VLAN,
OLT port, port isolation, PON, ONU, RSTP, Trunk , Mirror, MAC, QoS, ACL address
table, IGMP, performance, alarm, network management, L3, ONU upgrade, log. In
the operation process, in order to avoid the possibility of operation problems or loss
of configuration, business failure, please read this manual carefully. This manual
contains the following chapters:
 Chapter 1 Overview: Describes the way in which data are obtained, the
relationship between the data and the version, and a brief description of the
product.
 Chapter 2 Logging In to an OLT Device: This topic describes how to log in to
an OLT locally or remotely.
 Chapter 3 Command Line Interface and View: It describes system view and
command line interface operations.
 Chapter 4 Upgrading an OLT System: it describes the configuration related to
system management, including upgrading and configuration files, network tools,
and restarting operations.
 Chapter 5, Device Configuration Management: This chapter describes the
device configuration management, including system date and time, time zone
and host name management, and slot management configuration.
 Chapter 6 VLAN Configuration Management: It introduces VLAN
configuration.
 Chapter 7 OLT Port Configuration Management: This chapter describes the
configuration of OLT ports, including port basic configuration, broadcast,
multicast and unknown unicast suppression, loopback, and basic port
configuration.
 Chapter 8 Port Isolation Configuration Management: This topic describes
how to isolate PON ports.
 Chapter 9 PON Configuration Management: This chapter describes the PON
configuration management operations.
 Chapter 10 ONU Configuration Management: it describes ONU device
configuration management, ONU port configuration management and other
operations.
 Chapter 11 GPON Service Management: Introduce GPON service

management operations.
 Chapter 12 RSTP Configuration Management: This topic describes how to
configure RSTP for fast spanning tree configuration.
 Chapter 13 Link Aggregation Configuration Management: This chapter
describes the management operations of link aggregation configuration.
 Chapter 14 Port Mirroring Configuration Management: This chapter
describes the operations related to port mirroring.
 Chapter 15 MAC Address Table Configuration Management: This chapter
describes the Layer 2 MAC address table configuration management
operations.
 Chapter 16 QoS Configuration Management: It introduces the QoS-related
 Chapter 17 ACL Configuration Management: This chapter describes ACL
 Chapter 18 Multicast Configuration Management: It introduces IGMP and
MLD configuration management.
 Chapter 19 Performance Configuration Management: it describes the
related operations of performance configuration management.
 Chapter 20 Alarm Configuration Management: This chapter describes the
operations related to alarm configuration management.
 Chapter 21 Network Management Configuration (NMS): it describes the
operations related to NMS configuration.
 Chapter 22, Layer 3 Configuration Management: This chapter describes the
configuration management operations such as Layer 3 static routes.
 Chapter 23 ONU Upgrade Management: This chapter describes the
operations related to the OAM upgrade and the FTP upgrade configuration of
the ONU.
 Chapter 24, Log Configuration Management: it describes the related
operations of log configuration.
 Chapter 25 Traffic Threshold Alarm Configuration Management: This
chapter describes the alarm thresholds for OLT and ONU traffic thresholds.
 Chapter 26 Revision History: Record the main content of this manual update.
The Agreement
1.CLI Agreement
Format Description
The command line keyword (part of the
Bold command that remains unchanged
and must be input) is in boldface.
The command line parameters (part of
Italic the command that must be replaced
by the actual value) are in italics
The part placed in [ ] is optional when in
[]
use.
Indicates to select one of two or more
(x | y | ... )
options.
Indicates to select one or none of the two
[x|y|…]
or more options.
Indicates that one of the numbers from x
<x-y>
to y is selected
$ Indicates a comment
2.Keyboard Agreement
Format Description
Characters Indicates the key name. Such as
with <Enter>, <Tab>, <Backspace>, <a>,
angle <?>, Respectively, said carriage
brackets return, tabulation, backspace,
lowercase a, .
<Key1 + Indicates that several keys are pressed
Key2> simultaneously on the
keyboard. Such as <Ctrl + Alt + A>
that press the "Ctrl", "Alt", "A" the
three keys.
Press the first button, release, then press
<Key1, the second key. Such as <Alt, F>,
Key2> press <Alt>, then press <F>.
3.Various Types of Signs
The book also uses a variety of eye-catching signs to indicate that in the course of
the operation users should pay special attention to various types of signs, the
meaning of these signs are as follows:
CAUTION: Caution should be noted in the operation. Improper operation

may result in data loss or damage to the equipment.
WARNING: Comments after this symbol must be given special attention.

Improper handling may result in personal injury.
Description, Tips, Tricks, Thinking: The description of the operation content is

necessary to be added and explained.
4.Nouns
OLT: indicates the G1000 system, which includes the uplink port and master
switch processing module connected to the uplink equipment such as the switch.
PON: Indicates the PON protocol processing module and the PON port connected
to the ONU.
5.Tips
The system command-line input is case-sensitive.
Abbreviation
Abbreviation Full expression

ACL Access Control List
C&M Classification&Marking
CATV Cable Television
CDR Call Detail Record
CVLAN Customer VLAN
DA Destination Address
DBA Dynamic Bandwidth Allocation
EPON Ethernet Passive Optical Network
FEC Forward Error Correction
GEM GPON Encapsulation Method
GPON Gigabit-Capable Passive Optical Network
GPUHA GPON Process Unit
IGMP Internet Group Management Protocol
LLID Logical Link Identifier
LOID Logical ONU ID
MAC Medium Access Control
OLT Optical Line Terminal
OMCI ONT Management and Control Interface
ONT Optical Network Termination
ONU Optical Network Unit
QoS Quality of Service
RSTP Rapid Spanning Tree Protocol
RTT Round Trip Time
SA Source Address
SCU Switch Control Unit
SFU Single Family Unit
SLA Service Level Agreement
SNI Service Network Interface
SNMP Simple Network Management Protocol
T-Cont Transmission Container
UNI User Network Interface
VLAN Virtual Local Area Network
VoIP Voice over IP
CONTENTS
CONTENTS................................................................................................................................................................. 4
1 OVERVIEW............................................................................................................................................................11
1.1 THE RELATIONSHIP BETWEEN DATA AND VERSION...................................................................................................11
1.1.1 Software version corresponding to the manual................................................................................... 11
1.1.2 The Supporting Information List........................................................................................................... 11
1.2 PRODUCT INTRODUCTION................................................................................................................................... 11
1.3 HOW TO MANAGE ONU...................................................................................................................................... 12
2 LOGIN TO THE OLT................................................................................................................................................13
2.1 LOGGING IN THROUGH THE CONSOLE PORT...........................................................................................................13
2.1.1 Configuring the Cable Connection........................................................................................................13
2.1.2 Configuration of Terminal Parameters..................................................................................................13
2.1.3 Startup Interface...................................................................................................................................16
2.2 LOG IN LOCALLY THROUGH TELNET........................................................................................................................17
2.2.1 Network Cable Connection...................................................................................................................17
2.2.2 Setting the Outside Management Interface Parameters......................................................................18
2.2.3 Set Terminal PC Card Parameters......................................................................................................... 18
2.2.4 Set Telnet Terminal Parameters............................................................................................................ 18
2.2.5 Telnet Connection Interface................................................................................................................. 18
2.2.6 Connecting the PC Cable.......................................................................................................................19
2.2.7 Set the In-band Management Interface PRM for Local-end G1000..................................................... 19
2.2.8 Set the Terminal PC Card Parameters................................................................................................... 19
2.2.9 Set Telnet Terminal Parameters............................................................................................................ 19
2.2.10 Telnet Connection Interface............................................................................................................... 19
2.3 REMOTE LOGIN VIA WIFI INTERFACE.....................................................................................................................19
2.3.1 WIFI connection....................................................................................................................................20
2.3.2 Setting PC WIFI Network Card Parameters...........................................................................................20
2.3.3 Setting Telnet Terminal Parameters......................................................................................................20
2.3.4 Telnet connection interface.................................................................................................................. 20
3 COMMAND LINE INTERFACE AND VIEW............................................................................................................. 21
3.1 INTRODUCTION TO THE COMMAND LINE INTERFACE................................................................................................ 21
3.2 COMMAND LINE HIERARCHY AND COMMAND LINE VIEW.........................................................................................21
3.3 COMMAND LINE VIEW....................................................................................................................................... 21
3.4 COMMAND LINE FEATURES................................................................................................................................. 24
3.4.1 On-line Help of Command Lines........................................................................................................... 24
3.4.2 Command Line History Commands...................................................................................................... 25
3.4.3 Command Line Error Messages............................................................................................................ 26
3.4.4 Editing Features of Command Lines..................................................................................................... 26
4 OLT SYSTEM UPGRADE........................................................................................................................................ 28
4.1 INTRODUCTION TO OLT SOFTWARE UPGRADE........................................................................................................ 28
4.1.1 Software Upgrade Operation................................................................................................................28
4.1.2 Software Upgrade Operation Example................................................................................................. 30
4.2 XML UPGRADE OPERATIONS...............................................................................................................................31
4.2.1 Introduction to XML..............................................................................................................................31
4.2.2 XML Upgrade Operations..................................................................................................................... 32
4.2.3 XML Upgrade Operation Example........................................................................................................ 32
4.3 CONFIGURATION FILE OPERATIONS....................................................................................................................... 33
4
4.4 NETWORK TOOL OPERATIONS..............................................................................................................................34

4.4.1 Introduction to Network Tools..............................................................................................................34
4.4.2 Introduction to FTP............................................................................................................................... 34
4.4.3 Introduction to Telnet........................................................................................................................... 34
4.4.4 Introduction to Ping..............................................................................................................................34
4.4.5 Network Tool Operation Example.........................................................................................................35
4.5 RESTART OPERATIONS.........................................................................................................................................37
5 DEVICE CONFIGURATION MANAGEMENT.......................................................................................................... 37
5.1 TIME AND TIME ZONE MANAGEMENT.................................................................................................................. 37
5.2 DEVICE INFORMATION MANAGEMENT...................................................................................................................37
5.3 SYSTEM MONITORING........................................................................................................................................ 38
5.3.1 Introduction to System Monitoring...................................................................................................... 38
5.3.2 System Monitoring Operation.............................................................................................................. 38
5.4 BOARD MANAGEMENT.......................................................................................................................................39
5.4.1 Introduction to Slot Management........................................................................................................ 39
5.4.2 Board Management Operations........................................................................................................... 39
5.4.3 Board Management Operation Example.............................................................................................. 39
5.5 COMMAND TIMEOUT SETTING AND SPLIT SCREEN SETTING........................................................................................40
5.5.1 Command timeout setting and split screen setting operation example.............................................. 40
5.6 OLT WIFI INTERFACE MANAGEMENT................................................................................................................... 41
5.6.1 Introduction to OLT WIFI Interface....................................................................................................... 41
5.6.2 OLT WIFI interface operation................................................................................................................41
5.6.3 Example of OLT WIFI Interface Operation............................................................................................ 41
6 VLAN CONFIGURATION MANAGMENT............................................................................................................... 42
6.1 VLAN CONFIGURATION MANAGEMENT................................................................................................................ 42
6.1.1 Introduction to VLAN Knowledge......................................................................................................... 42
6.1.2 OLT Port-based VLAN............................................................................................................................ 45
6.1.3 VLAN Based on ONU Port..................................................................................................................... 47
6.2 OLT VLAN CONFIGURATION AND APPLICATION......................................................................................................49
6.2.1 OLT VLAN Configuration........................................................................................................................50
6.2.2 Basic Configuration Example of VLAN.................................................................................................. 50
6.2.3 Examples of Applications Based on Hybrid.......................................................................................... 51
6.2.4 Example of Application Based on Transparent..................................................................................... 52
6.3 ONU VLAN CONFIGURATION AND APPLICATION..................................................................................................... 56
6.3.1 Onu VLAN Configuration Procedure..................................................................................................... 56
6.3.2 VLAN Transparent Transmission Example.............................................................................................57
6.3.3 Example of VLAN Tagging..................................................................................................................... 59
6.3.4 VLAN Conversion Example....................................................................................................................61
6.3.5 VLAN Trunk Example.............................................................................................................................63
7 OLT PORT CONFIGURATION MANAGEMENT...................................................................................................... 65
7.1 BASIC CONFIGURATION OF OLT PORT................................................................................................................... 65
7.1.1 Introduction to Basic Configuration......................................................................................................65
7.1.2 Basic Configuration Command............................................................................................................. 66
7.1.3 Basic Configuration Example................................................................................................................ 66
7.2 OLT PORT PACKET SUPPRESSION..........................................................................................................................66
7.2.1 Introduction to Packet Suppression Configuration...............................................................................66
7.2.2 Packet Suppression Configuration Commands.....................................................................................67
7.2.3 Example for Packet Suppression Configuration....................................................................................67
8 PORT ISOLATION CONFIGURATION MANAGEMENT...........................................................................................68
8.1 PON PORT ISOLATION MANAGEMENT.................................................................................................................. 68
8.1.1 Introduction to PON Port Isolation....................................................................................................... 68
5
8.1.2 PON Port Isolation Configuration......................................................................................................... 69

8.1.3 PON Port Isolation Configuration Example...........................................................................................69
9 PON CONFIGURATION MANAGEMENT............................................................................................................... 70
9.1 BASIC INFORMATION ABOUT PON....................................................................................................................... 70
9.1.1 PON Port Basic Information Query....................................................................................................... 70
9.1.2 Examples of PON Port Basic Information............................................................................................. 70
9.2 DOWNSTREAM ENCRYPTION MANAGEMENT.......................................................................................................... 70
9.2.1 Downstream Encryption Configuration................................................................................................ 70
9.2.2 Example of Downstream Encryption.................................................................................................... 71
9.3 OPTICAL POWER DETECTION............................................................................................................................... 71
9.3.1 Optical Power Detection Configuration................................................................................................71
9.3.2 Example of Optical Power Detection.................................................................................................... 71
9.4 LONG-DISTANCE CONFIGURATION MANAGEMENT................................................................................................... 72
9.4.1 Long-distance Configuration.................................................................................................................72
9.4.2 Example of Long-distance.....................................................................................................................72
9.5 DETECTION AND PROCESSING OF THE ROGUE-ONU.................................................................................................73
9.5.1 Introduction of detection and processing of the rogue- ONU............................................................. 73
9.5.2 Configuration of the rogue-ONU.......................................................................................................... 73
9.5.3 Example of detection and treatment of l rogue-ONU.......................................................................... 75
10 ONU CONFIGURATION MANAGEMENT............................................................................................................ 76
10.1 ONU BASIC INFORMATION............................................................................................................................... 76
10.1.1 Basic information Query on the ONU.................................................................................................77
10.1.2 ONU Basic Information Example........................................................................................................ 77
10.2 ONU AUTHORIZATION MANAGEMENT................................................................................................................78
10.2.1 Introduction to ONU Authorization Management............................................................................. 78
10.2.2 ONU Authorization management....................................................................................................... 79
10.2.3 Examples for ONU Authorization Management................................................................................. 80
10.3 ONU RESTART AND DEREGISTER........................................................................................................................81
10.3.1 Introduction to Restart and Deregister...............................................................................................81
10.3.2 Restart and Deregister Example......................................................................................................... 82
10.4 ONU ACTIVATION / DEACTIVATION..................................................................................................................... 83
10.5 ONU PORT CONFIGURATION MANAGEMENT....................................................................................................... 84
10.5.1 Basic Configuration of the ONU port..................................................................................................84
10.5.2 Flow Control Configuration of the ONU port......................................................................................86
10.5.3 Rate Limit Configuration of the ONU port..........................................................................................88
10.6 FEC CONFIGURATION MANAGEMENT................................................................................................................. 90
10.6.1 Introduction to FEC Configuration...................................................................................................... 90
10.6.2 Example of FEC Configuration............................................................................................................ 90
10.7 ONU ALARM CONFIGURATION MANAGEMENTS................................................................................................... 90
10.7.1 Introduction to ONU Alarm................................................................................................................ 91
10.7.2 Introduction to Alarm ID.....................................................................................................................91
10.7.3 ONU Introduction to ONU alarm configuration................................................................................103
10.7.4 ONU Alarm Configuration Example.................................................................................................. 107
11 GPON BUSINESS MANAGEMENT.................................................................................................................... 109
11.1 OVERVIEW OF GPON ACCESS SERVICE............................................................................................................. 109
11.2 GPON ONU TERMINAL OVERVIEW.................................................................................................................. 109
11.3 GPON DBA CONFIGURATION......................................................................................................................... 109
11.3.1 GPON DBA introduction....................................................................................................................109
11.3.2 GPON DBA Configuration example................................................................................................... 112
11.4 GPON GEMPORT CONFIGURATION............................................................................................................... 112
11.4.1 GEM Port Mapping introduction...................................................................................................... 112
11.4.2 Introduction to binding of T-CONT and GEM port........................................................................... 113
6
11.4.3 GPON GEMPORT Configuration example......................................................................................... 116

11.5 ONU SERVICE-PROFILE...................................................................................................................................116
11.5.1 Introduction to ONU Service-profile.................................................................................................116
11.5.2 ONU service profile configuration example..................................................................................... 119
11.6 ONU LINE PROFILE........................................................................................................................................119
11.6.1 Introduction to ONU Line profile...................................................................................................... 119
11.6.2 ONU line profile configuration example........................................................................................... 121
11.7 ONU TRAFFIC PROFILE................................................................................................................................... 122
11.7.1 Introduction to ONU Traffic profile...................................................................................................122
11.7.2 ONU traffic profile configuration example....................................................................................... 123
12 RSTP CONFIGURATION MANAGEMENT.......................................................................................................... 123
12.1 INTRODUCTION TO RSTP PROTOCOL.................................................................................................................123
12.2 OLT RSTP CONFIGURATION MANAGEMENT...................................................................................................... 128
12.2.1 RSTP Configuration Task................................................................................................................... 128
12.2.2 Introduction to RSTP Configuration..................................................................................................129
12.2.3 RSTP Configuration Example.............................................................................................................133
13 LINK AGGREGATION CONFIGURATION MANAGEMENT................................................................................. 134
13.1 BRIEF INTRODUCTION TO LINK AGGREGATION..................................................................................................... 134
13.1.1 basic principles of LACP.................................................................................................................... 135
13.1.2 Introduction to manual link aggregation group............................................................................... 135
13.1.3 An introduction to the static link aggregation group....................................................................... 136
13.1.4 introduction to dynamic link aggregation group.............................................................................. 136
13.2 LINK AGGREGATION CONFIGURATION................................................................................................................ 137
13.2.1 Configure Manual Link Aggregation Group...................................................................................... 137
13.2.2 Configure Static Link Aggregation Group..........................................................................................138
13.2.3 Configure Dynamic Link Aggregation Group.................................................................................... 138
13.2.4 Descriptor configuration aggregation group.................................................................................... 139
13.3 LINK AGGREGATION CONFIGURATION EXAMPLE.................................................................................................. 140
13.3.1 Networking Requirements................................................................................................................140
13.3.2 Networking Figure............................................................................................................................ 140
13.3.3 Configuration Procedure.................................................................................................................. 140
14 PORT MIRRORING CONFIGURATION MANAGEMENT.................................................................................... 142
14.1 INTRODUCTION TO PORT MIRRORING............................................................................................................... 142
14.2 PORT MIRRORING CONFIGURATION.................................................................................................................. 142
14.3 PORT MIRRORING CONFIGURATION EXAMPLE.................................................................................................... 143
15 MAC ADDRESS TABLE CONFIGURATION MANAGEMENT............................................................................... 144
15.1 INTRODUCTION TO MAC ADDRESS TABLE...........................................................................................................144
15.2 OLT MAC ADDRESS MANAGEMENT CONFIGURATION......................................................................................... 147
15.2.1 Configure the MAC Address Aging Time...........................................................................................147
15.2.2 Configure Port-bound Static MAC Address Table............................................................................. 148
15.2.3 Clear and Query MAC Address Table................................................................................................148
15.2.4 Configure MAC Address Limitation...................................................................................................149
15.2.5 MAC Address Movement..................................................................................................................149
15.3 OLT MAC ADDRESS CONFIGURATION EXAMPLE................................................................................................. 149
15.4 OLT MAC ADDRESS TABLE QUERY EXAMPLE.....................................................................................................151
7

15.5 ONU MAC ADDRESS TABLE CONFIGURATION MANAGEMENT.............................................................................. 152
15.5.1 Configure the Aging Time of MAC Address...................................................................................... 152
15.5.2 Configure the onu port MAC address limit.......................................................................................152
15.5.3 configure the number of MAC address limits based on onuid.........................................................152
15.6 EXAMPLE OF ONU MAC ADDRESS TABLE CONFIGURATION MANAGEMENT............................................................ 153
16 QOS CONFIGURATION MANAGEMENT........................................................................................................... 154
16.1 INTRODUCTION TO QOS................................................................................................................................. 154
16.1.1 Traffic................................................................................................................................................ 154
16.1.2 Traffic Classification.......................................................................................................................... 155
16.1.3 Priority.............................................................................................................................................. 155
16.1.4 Priority Marking................................................................................................................................ 155
16.1.5 Packet Filtering................................................................................................................................. 155
16.1.6 Traffic Policing...................................................................................................................................156
16.2 QUEUE SCHEDULING......................................................................................................................................156
16.2.1 Strict Priority (SP) Scheduling........................................................................................................... 156
16.2.2 Polling Scheduling (RR)..................................................................................................................... 157
16.2.3 Scheduling by Weight Polling (WRR)................................................................................................ 157
16.2.4 Scheduling of Strict Priority Plus Weight Polling (SP+WRR)............................................................. 158
16.3 CONFIGURE QOS...........................................................................................................................................158
16.3.1 Queue Priority Mapping Operation..................................................................................................158
16.3.2 Queue Priority Scheduling Operation...............................................................................................159
16.3.3 Congestion Control........................................................................................................................... 160
16.4 OLT CONFIGURATION EXAMPLE....................................................................................................................... 160
16.4.3 Configuration Procedures................................................................................................................. 161
17 ACL CONFIGURATION MANAGEMENT............................................................................................................ 161
17.1 INTRODUCTION TO ACL..................................................................................................................................161
17.1.1 ACL Matching Sequence................................................................................................................... 162
17.1.2 How ACLs Are Applied on the OLT.................................................................................................... 162
17.2 ACL CONFIGURATION.....................................................................................................................................163
17.2.1 ACL Rule Group Configuration.......................................................................................................... 163
17.2.2 ACL Rule Configuration..................................................................................................................... 164
17.2.3 Apply the ACL Rule Group to Ports...................................................................................................167
17.3 EXAMPLE OF STANDARD, LINK LAYER AND ADVANCE ACL CONFIGURATION............................................................. 168
17.3.3 Configuration Procedures................................................................................................................. 168
18 MULTICAST CONFIGURATION MANAGEMENT............................................................................................... 169
18.1 INTRODUCTION TO MULTICAST........................................................................................................................ 169
18.2 IGMP PROTOCOL AND CONFIGURATION............................................................................................................171
18.2.1 Introduction to IGMP Protocol......................................................................................................... 171
18.2.2 IGMP Multicast Configuration.......................................................................................................... 175
18.2.3 IGMP Multicast Configuration Example............................................................................................179
19 PERFORMANCE STATISTICS CONFIGURATION MANAGEMENT...................................................................... 181
8
19.1 INTRODUCTION TO PERFORMANCE STATISTICS CONFIGURATION.............................................................................. 181

19.2 PERFORMANCE STATISTICS CONFIGURATION........................................................................................................ 184
19.2.1 OLT performance statistics configuration.........................................................................................184
19.2.2 onu performance statistics configuration.........................................................................................185
19.3 PERFORMANCE STATISTICS CONFIGURATION EXAMPLE...........................................................................................186
19.3.1 Networking requirements................................................................................................................ 186
19.3.2 Network diagram.............................................................................................................................. 186
19.3.3 Configuration steps...........................................................................................................................186
20 ALARM CONFIGURATION MANAGEMENT...................................................................................................... 188
20.1 INTRODUCTION TO ALARM CONFIGURATION....................................................................................................... 188
20.2 ALARM CONFIGURATION OPERATION................................................................................................................. 189
20.3 ALARM CONFIGURATION EXAMPLE....................................................................................................................191
20.3.1 Networking requirements................................................................................................................ 191
20.3.2 Network diagram.............................................................................................................................. 192
20.3.3 Configuration steps...........................................................................................................................192
21 NETWORK MANAGEMENT CONFIGURATION................................................................................................. 192
21.1 INTRODUCTION TO NETWORK MANAGEMENT MODE.......................................................................................... 192
21.2 MANAGEMENT NETWORK DIAGRAM................................................................................................................ 195
21.3 DEFAULT GATEWAY CONFIGURATION.................................................................................................................. 195
21.4 OUT-OF-BAND MANAGEMENT CONFIGURATION.................................................................................................. 195
21.5 IN-BAND MANAGEMENT CONFIGURATION.......................................................................................................... 196
22 L3 CONFIGURATION MANAGEMENT...............................................................................................................197
22.1 OVERVIEW OF IP ROUTING..............................................................................................................................197
22.1.1 Routing and routing tables............................................................................................................... 197
22.1.2 Static and dynamic routing............................................................................................................... 197
22.1.3 Layer 3 interface introduction.......................................................................................................... 197
22.2 INTERCOMMUNICATION WITH L3 IN ONE PON PORT...........................................................................................198
22.2.1 Introduction...................................................................................................................................... 198
22.2.2 arp proxy and nd proxy configuration.............................................................................................. 198
22.2.3 arp proxy and nd proxy examples.....................................................................................................199
22.3 STATIC ROUTE CONFIGURATION.........................................................................................................................201
22.3.1 Introduction to static routing........................................................................................................... 201
22.3.2 Static Route Configuration................................................................................................................201
22.3.3 Example of Static Route Configuration............................................................................................. 203
23 ONU UPGRADE MANAGEMENT...................................................................................................................... 205
23.1 OMCI UPGRADE...........................................................................................................................................205
23.1.1 Introduction to OMCI Upgrade.........................................................................................................205
23.1.2 OMCI Upgrade Example....................................................................................................................206
24 LOG CONFIGURATION MANAGEMENT........................................................................................................... 206
24.1 INTRODUCTION TO LOG CONFIGURATION...........................................................................................................206
24.1.1 Types of Logs.....................................................................................................................................206
24.1.2 Log Level........................................................................................................................................... 207
24.1.3 Log Output Mode............................................................................................................................. 207
24.1.4 Log Function Module........................................................................................................................ 208
24.2 LOG CONFIGURATION OPERATIONS...................................................................................................................208
24.3 EXAMPLE OF LOG CONFIGURATION...................................................................................................................210
24.3.2 Configuration Steps.......................................................................................................................... 210
25 TRAFFIC THRESHOLD ALARM CONFIGURATION MANAGEMENT...................................................................211
9
25.1 INTRODUCTION TO TRAFFIC THRESHOLD ALARM CONFIGURATION..........................................................................211

25.2 TRAFFIC THRESHOLD ALARM CONFIGURATION....................................................................................................211
25.2.1 Traffic Threshold Alarm Configuration Example............................................................................... 211
26 APPENDIX:REVISION HISTORY.........................................................................................................................213
10
1 Overview
1.1 The Relationship Between Data and Version
Due to the upgrade of product software version, the latest version may include some new software
features. Users can use the released supporting information from the latest software version to
obtain these additional features related to the use of documents.
1.1.1 Software version corresponding to the manual
"Opticalink G1000 GPON OLT Operation Manual" and "Opticalink G1000 GPON OLT Command
Line Manual" correspond to the V300 series version of G1000 products.
1.1.2 The Supporting Information List
Table 1- 1 The supporting Information List
Manual Name Version
"Opticalink G1000 GPON OLT Installation Manual" V2.1
"Opticalink G1000 GPON OLT Operation Manual" V2.2
"Opticalink G1000 GPON OLT Command Line Manual" V2.0
1.2 Product introduction
The GPON (Gigabit-Capable Passive Optical Network) series products launched by our company
include OLT (Optical Line Terminal) equipment and onu (Optical Network Termination) equipment,
which can provide users with Provide complete optical access solutions such as Fiber To The
Home (FTTH) and Fiber To The Building (FTTB).
The Opticalink G1000 product introduced in this manual is our carrier-grade GPON OLT
equipment for large-scale access applications. This product complies with the IEEE802.3 standard
and meets China Telecom's GPON technical requirements. It has rich user interfaces and card
types, and also provides powerful network management functions. It can realize flexible
networking and management of the system. The access layer of the network and the convergence
/ access layer of the enterprise network. G1000 products have powerful switching functions, and
have excellent network availability, scalability, high performance and powerful network control
capabilities. G1000 products provide 1 internal integrated service interface unit, collectively
referred to as GPU below, 1 main control switching unit, hereinafter collectively referred to as SCU,
and also provides a USB 2.0 WIFI interface to support hot plug function.
The G1000 device is a box-type OLT device that meets the specifications of a standard 19-inch
cabinet and has a height of 1U, which is an OLT product independently developed by our
company.
There are 4 types of this device, and the differences are shown in the following table. Except for
differences in port number and label, other software and hardware functions are basically the
same
1-11
The G1000 series has the following product variants:

Table 1 - 1 G1000 product model
Model Main control board G1000-SCU
G1022 AC220V Power module + AC Power converter
Support 8 GE uplink ports and 8 10GE/GE uplink optical ports
Support 16 GPON ports
G1022-D AC220V Power module + AC220V Power module
G1012 AC220V Power module + AC Power converter
G1012-D AC220V Power module + AC220V Power module
1.3 How to manage onu
At present, the management of the ONU by the OLT is managed through the OMCI (ONT
Management and Control Interface)
1-12
2 Login To the OLT
The Opticalink G1000 device supports local and remote login configuration. Login can be
achieved through the following methods:
2.1 Logging In Through the Console Port
The terminal (in this example, a PC) is connected to the console port of the switching control board
of the OLT through the console cable.
Figure 2- 1 G1000 Diagram for setting the connection to the Console port
2.1.1 Configuring the Cable Connection
Step 1: Connect the DB-9 female connector of the console cable to the serial port of the PC or
terminal on which the G1000 is to be configured.
Step 2: Connect the RJ-45 end of the console cable to the SCU console port on the G1000 switch.
2.1.2 Configuration of Terminal Parameters
Parameter Requirement: The device baud rate is 9600, the data bit is 8 bits, the parity is none, the
stop bit is 1, the flow control is none, and the terminal emulation is VT100.
The following describes how to set the terminal parameters by running Windows XP Hyper
Terminal on the PC.
Step 1: Turn on the PC and run the terminal emulation program on the PC (such as
Windows 3.1 Terminal, Windows 95 / Windows 98 / Windows ME / Windows 2000 /
Windows NT / Windows XP / Windows 2003 Hyper Terminal).
Note :
In other computer operating systems, Hyper Terminal tools may not be supported by default.
Users can choose to install other tools with similar functions to manage the devices through
‘Console’ port connection.
2-13
you can now perform local upgrade and management port upgrade through the console port.
Don’t power off during the upgrade to prevent the boot file from missing, and the system can not
start now.
Step 2: Set Windows XP Hyper Terminal parameters.

Parameter Requirement: The baud rate is 9600, the data bit is 8, the parity bit is none, the
stop bit is 1, the flow control is none, and the terminal emulation is VT100. Specific methods
are as follows:
1） Click "Start" - "Programs" - "Accessories" - "Communication" - "Hyper Terminal" to
enter the Hyper Terminal window and create a new connection. The following dialog
box is displayed.
Figure 2- 2 Hyper Terminal connection interface
2） Type the name of the new connection in the Connection Description dialog box, and
then click OK. The interface shown in the following figure is displayed. Select the serial
port to be used in the Connect using box.
2-14
Figure 2- 3 Hyper Terminal connection using serial port settings
3） When the serial port selection is complete, click the [OK] button. The following
interface will pop up: The flow control is none.
2-15
Figure 2- 4 Serial port settings
4） After setting serial port parameters, click the [OK] button.

5） In the Hyper Terminal Properties dialog box, select the [Attribute] (hand icon) item to
enter the Properties window. Click the "Settings" tab in the Properties window, enter
the property settings window (shown below), select VT100 as the terminal emulation,
and click OK when finished.
2.1.3 Startup Interface
When the OLT is powered on, the configuration terminal will output the following information
***********************************************************************
* *
* PON-OS (version 1.00) *
* *
* Copyright 2006-2020, All Rights Reserved. *
* *
2-16
***********************************************************************
User Access Verification
Password:
After the above prompt message appears, it marks the completion of the automatic startup
of the OLT device and requires the user to enter the password. The default password is yotc.
After entering the password, the terminal screen is displayed as shown below. You can start
to configure the G1000.
G1000>
2.2 Log in locally through Telnet
Connect the management network port (MGMT on the SCU) of the G1000 to the PC
network cable (out-band management).
Figure 2- 5 Log in locally through Telnet
2.2.1 Network Cable Connection
Connect the two RJ-45 connectors of the network cable to the management network port of
the SCU of the G1000 and the other end to the network port of the PC.
2-17
2.2.2 Setting the Outside Management Interface Parameters
For details, read Chapter 21.4 Out-band Management Configuration.
2.2.3 Set Terminal PC Card Parameters
The following PC to run Windows XP, for example, describes the terminal PC parameters
settings.
Step 1: open the PC, open the network connection on the PC.
Step 2: set Windows XP network card TCP / IP parameters.
Parameter Requirement: The IP address and IP address of the G1000 are in the same network
segment, but different IP addresses and subnet masks are set to the same mask as the G1000
out-band NMS. Because it is in the LAN, you cannot set the gateway.
Specific methods are as follows:
1) Click "Start" - "Settings" - "Network Connections" - "Local Area Connection". The following
interface will pop up.
2) Click [Properties] in the above interface the following interface pop up
3) Double-click "Internet Protocol (TCP / IP)", and then fill in IP, subnet mask and other
information. Note that the IP address must be the same as that of the out-band
management port of the G1000 and the subnet mask must be the same. Because
only in the LAN connection, so the default gateway and DNS cannot be filled.
4) When TCP/IP parameter setting is complete, click [OK]
2.2.4 Set Telnet Terminal Parameters
1） Click "Start" - "Programs" - "Accessories" - "Communication" - "Hyper Terminal" to

enter the Hyper Terminal window and create a new connection. The following dialog
box is displayed.
2） In the Connection Description dialog box, type the name of the new connection, and
then click OK. The following figure shows the interface diagram. Select "TCP / IP
(Winsock)" in the "Connect using" field.
3） Input the IP address of the out-band network management interface of the G1000
configured with the console port on the G1000.
4） Click OK to enter the following interface (if connected, it automatically into the CLI
command line interface).
5） In the Hyper Terminal Properties dialog box, select the [Attribute] (hand icon) item to
enter the Properties window. Click the "Settings" tab in the Properties window, enter
the property settings window (shown below), select VT100 as the terminal emulation,
and click OK when finished.
2.2.5 Telnet Connection Interface
After the connection, the configuration terminal will have the following information output:
The above prompt message appears, marking the connection is successful, and requiring
2-18
the user to enter the password, the default password is yotc. After entering the password,
the terminal screen is displayed as shown below. You can start to configure the G1000.
G1000>
The PC can access the network up to the IP address of the G1000 and perform remote
login.
2.2.6 Connecting the PC Cable
Connect the two RJ-45 connectors of the crossover cable to the nearest switch or network socket
and the other end to the network port on the computer.
2.2.7 Set the In-band Management Interface PRM for Local-end

G1000
For details, Read "21.5 In-band Management Configuration".
2.2.8 Set the Terminal PC Card Parameters
Read “Section 2.2.3, Setting the Terminal PC Card Parameters". It should be noted that
TCP / IP parameters should be configured according to the advice of the network
administrator. Such as IP address, subnet mask and default gateway that must be set in
accordance with the views of the network administrator, and all blanks must be filled. After
filling out, you can try to ping the G1000 PC in-band network management interface IP, if
passing you can go to the next operation.
2.2.9 Set Telnet Terminal Parameters
Read "2.2.4 Setting Telnet Terminal Parameters", but note that "Host Address" is the IP
address of the in-band network management interface of the G1000, not the IP address of
the out-band network management interface.
2.2.10 Telnet Connection Interface
Read “Telnet Connection Interface” view.
2.3 Remote login via WIFI interface
Use PC WIFI network card to connect to the network of G1000 WIFI interface for remote
login.
2-19
2.3.1 WIFI connection
Use a PC WIFI network card, enter the SSID and password of the G1000 WIFI interface,
and connect to the network of the G1000 WIFI interface.
2.3.2 Setting PC WIFI Network Card Parameters
Set PC WIFI network card parameters to DHCP to obtain IP automatically.
2.3.3 Setting Telnet Terminal Parameters
Read "2.2.4 Setting Telnet Terminal Parameters", but note that "Host Address" fills in the IP
address of the G1000 WIFI interface, not the IP address of the out-band \ in-band network
management interface.
2.3.4 Telnet connection interface
Read "2.2.5 Telnet connection interface".
2-20
3 Command Line Interface and View

3.1 Introduction to the Command Line Interface
Opticalink G1000 OLT provides users with a series of configuration commands and command
line interfaces to configure and manage EPON system. The command line interface has the
following features:
 Local configuration through the Console port.

 Local or remote configuration through Telnet.
 Configure the hierarchical protection to ensure that unauthorized users cannot enter the
G1000.
 The user can enter <?> at any time for online help.
 Provide History function, you can view the history command.
 The command-line keyword is not exactly match the search method, the user simply type
the conflict-free keywords to the correct implementation, e.g., If the “Show” command is
needed, you can only enter “sh”.
3.2 Command Line Hierarchy and Command Line View
The command line of the G1000 OLT adopts the hierarchical protection mode to prevent illegal
ingress of unauthorized users.
The command line is divided into three levels: access level, system level, and management
level. The brief introduction is as follows:
 Access level: Contains commands for the user interface language mode switch, the
terminal control parameters settings, and system settings and associated view etc.
 System level: Contains commands for file operations, network diagnosis, system upgrade,
and device reboot and associated view, etc.
 Management level: Contains commands related to the global configuration of the system
and interfaces, configuration of some services, config view, xe, ge, pon, onu, and vlan, acl,
blacklist, multicast and other global configuration views.
The users logging in to the system are classified into two levels, corresponding to the command
level. The users at the access level can use the commands at the access level. All the
commands can be used by privileged users.
3.3 Command Line View
The view of each command line is based on different configuration requirements, and there are
differences between them. For example, to establish a connection with the OLT, after entering
the user account and password, you immediately enter the "view" view, it can only complete a
simple function of viewing running status and statistical information. If you type "enable" here,
you enter the "enable" view. In the enable view, you can type the configuration terminal
command to enter the configuration view. In the configuration view, you can type different
commands to enter the corresponding view.
The command line provides the following 18 views: view, enable, config, xe port, ge port, pon
3-21
port, onu, vlan, mvlan, blacklist, whitelist, acl-basic, acl-link, acl-advance, acl-user, cpuFirewall,
ip-filter and mac-filter.
 Enter / exit the “view” view : After connecting to the OLT, input the password to view the
system running status in the “view” view. The default password is “yotc”; input the exit
command to disconnect the OLT.
User Access Verification
Password: ****
G1000> exit
 Enter / exit "enable" view: Input “en” or "enable" in the "view" view, then input the password
to enter the "enable" view for the system configuration and operation. Exit Disconnect from
the OLT, and input disable to exit the “view” view.
G1000> enable
Enable Password: ****
G1000# disable
G1000>
 Enter / exit the “config” view: Input "cont" or "configure terminal" in the “enable” view to
enter the “config” view. To do so, run the exit or end command in the “enable” view.
G1000# configure terminal
G1000(config)# exit
G1000#
 Enter / exit the "xe port" view: Input "interface olt slotid / portid" in the “config” view (slotid is
1 and portid is 9-16) to enter the “xe” view. ; Input exit to exit the “config” view and input
end to the “enable” view.
G1000 (config)# interface olt 1/9
%Enter configuration commands. End with Ctrl+Z or command "exit" & "end"
G1000 (config-if-xgigabit-ethernet-1/9)#exit
G1000 (config)#
 Enter / exit the "GE port" view: Input "interface olt slotid / portid" in the “config” view (slotid
is 1 and portid is 1-8) to enter “GE view”. Input the exit to exit the “config” view and input
end to the “enable” view.
G1000(config-if-gigabit-ethernet-1/1)#exit
G1000 (config)#
 Enter / exit the "pon" view: Input "interface olt slotid / portid" in the "config" view (slotid is
12 and portid is 1-16) to enter “PON” view. Enter exit to the “config” view and input end to
the “enable” view.
G1000 (config-if-gpon-2/1)#exit
G1000 (config)#
 Enter / exit the “onu” view: Input the “interface onu slotid / portid / branched”(slotid / portid /
branchid: <2 /1-16> / <1-64>) in the “config” view to configure ONU. Input exit to exit the
“config” view and input end to the “enable” view.
3-22
G1000 (config)# interface onu 2/1/1

G1000 (config-if-ont-2/1/1)#exit
G1000 (config)#
 Enter / exit the “vlan” view: Input “vlan vlanid” in the “config” view and enter “vlan” view to
globally configure vlan. Input exit to exit the “config” view and input end to the “enable”
view. .
G1000(config) # vlan 1
G1000(config-vlan-1) #
G1000(config-vlan-1) #exit
G1000(config) #
 Enter / exit the “mvlan” view: Input “multicast-vlan mvlanid” in the “config” view to globally
configure mvlan in the “mvlan” view . Input exit to exit the config view and input end to the
enable view.
G1000(config)# multicast-vlan 4001
G1000(config-mvlan-4001)#exit
G1000(config)#
 Enter / exit “acl-basic” view: Input “acl basic aclid” in the “config” view to enter “basic acl
global” view to configure acl-basic. Input exit to exit “config” view and input end to “enable”
view.
G1000(config)# acl basic 1
Create 1 ACL(s) success
G1000(config-acl-basic-1)#exit
G1000(config)#
 Enter / exit the “acl-link” view: Input “acl link aclid” in the “config” view, and then enter the
“acl-link” view to configure it globally. Input exit to return to the “config” view and input end
to the “enable” view.
G1000(config)# acl link 2000
G1000(config-acl-link-2000)#exit
G1000(config)#
 Enter / exit the “acl-advance” view: Input “acl advance aclid” in the “config” view, and enter
“acl-advance” view to globally configure it. Input exit to exit the “config” view and input end
to the “enable” view.
G1000 (config)# acl advance 4000
G1000 (config-acl-adv-4000)#exit
 Enter / exit onu service-profile gpon view: Enter onu service-profile gpon profileId in config
view to enter onu service-profile gpon view to configure onu service profile; enter exit to
return to config view, enter end to return to enable view.
G1000 (config) # onu service-profile gpon 1
G1000 (config-gpon-srvprofile-1) #exit
3-23
G1000 (config) #
 Enter / exit onu line-profile view: Enter onu line-profile profileId in config view to enter onu
line-profile view to configure onu line-profile profile; enter exit to return to config view, enter
end to return to enable view.
G1000 (config) # onu line-profile 1
G1000 (config-line-profile-1) #exit
G1000 (config) #
3.4 Command Line Features

3.4.1 On-line Help of Command Lines
The command line interface provides two on-line help: full help and partial help. The on-line help
allows the user to obtain the relevant help information that is in need during the configuration of
the device.
3.4.1.1 Full help
1） In any view, type <?>, then, the terminal displays all the commands in the view and their
brief descriptions.
G1000(config-vlan-1)#
cls Clear screen
end End current mode and change to enable mode
exit Exit current mode and down to previous mode
help Description of the interactive help system
inband Inband interface
interface Interface information
l3-interface l3 interface
list Print commands list for current mode
no Negate a command or set it to its defaults
port Add member port(s)
show Show running system information
2） Type a command followed by a space-separated <?>. If there are the keywords in this
place, all the keywords and their brief descriptions are displayed on the terminal screen.
G1000(config-vlan-1)#show
vlan Show system VLAN information
3） Type a command followed by a space-separated <?>. If a parameters is in the place, a
description of the parameters will be displayed on the terminal screen.
G1000 (config) # vlan
G1000(config)# vlan
<1-4094> Vlan ID start
3-24
3.4.1.2 HELP
1） Type a character string followed by <?>, then all the commands starting with the character
string are listed on the screen of the user terminal.
G1000(config)# out
outband Set outband interface ip information
outer-tpid Set system outer tpid
2） Type a command followed by a string followed by <?>, then all the keywords starting with
the character string are listed on the screen of the user terminal.
3）
G1000(config)# show l
l3-interface l3 interface
legal-onu-info All legal onu information
legal-onu-label Legal onu userlabel
legal-onu-version All legal onu version
link-aggregation System trunk management
log Log information
4） Type the first few letters of a keyword in the command and press <Tab>. If the keyword
beginning with the input letter is unique, the complete keyword will be displayed on the
user terminal screen. If the keyword matches the input letter Not unique, the terminal
screen displays alphabetically matched keywords in turn.
G1000(config)# outb
G1000(config)# outband
G1000(config)# o
onu
onu-upgrade-server
outband
outer-tpid
3.4.2 Command Line History Commands
The command line interface provides the Doskey function. It automatically saves the history
commands that the user typed. The user can call the history commands saved in the command
line interface at any time and repeat them. When a user enters multiple commands in
succession, only the first command is saved as a history command on the command line
interface. As shown in Table 3.1.
Table 3- 1 Access history commands
Operation Key or command Result

Displays the history
Displays the valid history
command show history
commands entered by the user
If there is an earlier history

Access the previous Up cursor key ↑ or <Ctrl +
command, the previous history
history command P>
command is fetched
3-25
Access the next Down cursor key ↓ or <Ctrl +

If there is a later history command,
history command N>
the next history command is fetched
3.4.3 Command Line Error Messages
All commands entered by the user and checked by syntax will be executed correctly.
Otherwise, error messages will be reported to the user. The common error messages are
shown in Table 3-2.
Table 3- 2 Common command line error message table
Errors in English Possible causes
No command found
No keywords found
% Unknown command. The parameter type wrong
parameters values out of range
Too many input parameters
%Command incomplete. The input command incomplete
%Ambiguous command. The input command ambiguous
3.4.4 Editing Features of Command Lines
The command line interface provides the basic command editing function, supporting
multi-line editing. The maximum length of each command is 256 characters, as shown in
Table 3-3.
Table 3- 3 Editing functions table
Keys Functions
If the edit buffer is not full, insert it into the current cursor
Ordinary keys
position and move the cursor to the right
Deletes the previous character at the cursor position and
BackSpace
advances the cursor
Left cursor key←or
The cursor moves to the left by one character position
<Ctrl+B>
Right cursor key→or
The cursor moves to the right by one character position
<Ctrl+F>
Up cursor key ↑ or <Ctrl +
P>; Down cursor key ↓ or
Displays the history command
<Ctrl + N>
3-26
When a display of information is more than one screen, a

Press <Ctrl+C> pause is provided. Then the user can type Ctrl + C to pause
the display and pause the command execution.
If you enter an incomplete keyword and press the Tab key, the
system automatically performs part of the help: If the
matching keyword is unique, the system replaces the original
input with this complete keyword; If the keywords that match
Tab key
the input letters are not unique, the terminal screen displays
the keywords that match the letters in alphabetical order and
displays them in a new line. If the parameters of the
command word do not match, the system does not make any
changes and rewraps the original input.
3-27
4 OLT System Upgrade

4.1 Introduction to OLT Software Upgrade
The G1000 OLT supports the system software upgrade and the Boot ROM software
upgrade. LPU uses network load mode and cannot be upgraded with the command line.
The upgrade of the SCU application software and Bootrom software is three steps, first
download the bin file to be downloaded to the SCU board ramdisk, and then upgrade the file in
the SCU board ramdisk to the targeted SCU inactive work area, and finally restart the SCU (that
is, to restart the entire system) which makes the upgrade file go effective. In short, these three
steps are download, update and restart.
CAUTION: Before downloading, make sure that the G1000 management channel and the FTP
server are connected. You can use the ping command to check the diagnosis. You must also
pay attention to checking if the server-side ftp service is turned on, if the user name and
password are correct ad if the targeted file exists.
G1000 supports ipv4 and ipv6 address download files.

The types of software running on the boards of the G1000 OLT are different. The following
information is displayed:
Table 4- 1 Board type, or backup software file type
Board type Board type

SCU application software
SCU scu-fw
files
4.1.1 Software Upgrade Operation

4.1.1.1 Environment Construction
FTP Server Setup Example: Use xlight.exe as the ftp server software.
4-28
Figure 4- 1 xlight.exe Software interface
Configure the IPv4 or IPv6 address and port number of the FTP server. Select the default
one:
Add a user and configure user name, password and file file path to ensure the file to be upgraded
in the file path.
Next Start up the server：
Up to now the FTP server is completely set up.
4.1.1.2 Software upgrade
Please upgrade the system in the “enable” view, using the IPv4 or IPv6 address to connect
the server.to download files.
Table 4- 2 System upgrade
Operations Commands Descriptions
Enter enable view enable

Use ipv4 address to ftp download host-ipv4 Required.
download the files to ipv4-address username password
be upgraded. filename (scu-fw|config|onu-app)
Use ipv6 address to ftp download host-ipv6 Optional.
download the files to ipv6-address username password
be upgraded. filename (scu-fw|config|onu-app)
Query the downloaded enable view.
show download-image
files.
4-29
Required
Scu-fw: special file
type
Config: System
Upgrade scu configuration file
update (scu-fw|config) type;
Query scu workarea show work-space

Required
Range: 1-2
workspaceid ：
Switch the workarea of
active workspaceid partition No., scu
scu
divided into 2
partitions
Enter config view configure terminal

Reset the system system reset
4.1.2 Software Upgrade Operation Example

4.1.2.1 Networking Requirements
 OLT out-band connection with PC, making the PC ipv4 and ipv6 ftp server. The
server user name is ver, and the password ver.
4.1.2.2 Networking Figure
Figure 4- 2 Software Upgrade
4.1.2.3 Configuration procedure
Mainly three steps:

(1) Use ipv4 or ipv6 address to establish a connection with the server, download the
4-30
software version to the device

(2) Upgrade the software version to the corresponding board
(3) After the upgrade is prompted successful, switch the partition of the SCU and restart the
system
upgrade SCU software version
The system can use ipv4 or ipv6 address to download files, select one of them.
Use ipv4 address to download the files to the device. There is successful download prompt
indicating that the download is successful.
G1000# ftp download 192.168.85.193 ver ver
603_V300R003B030.bin scu-fw
%SYS-49 04:40:13 09/2/2020 Start Download file 01/0:00 port-00
00:bb:85:07:27:06 value(0)
%SYS-50 04:40:16 09/2/2020 Download file success 01/0:00 port-00
00:bb:85:07:27:06 value(0)
$ Use ipv6 address to download the files to the device. There is successful download
prompt indicating that the download is successful.
G1000# ftp download host-ipv6 2001:da8:207::9458 ver ver 603_V300R003B030.bin
scu-fw
%SYS-49 04:40:13 09/2/2020 Start Download file 01/0:00 port-00
00:bb:85:07:27:06 value(0)
%SYS-50 04:40:16 09/2/2020 Download file success 01/0:00 port-00
00:bb:85:07:27:06 value(0)
$ Query pre-upgrade workspace files
G1000# show workspace
Work Space 1:Active (Expected)
|-Service Card FW: 603_V300R003B030
Work Space 2:Inactive
$ Upgrade SCU APP software
G1000# update scu-fw
%SYS-51 04:40:25 09/2/2020 Start upgrade file 01/0:00 port-00
00:bb:85:07:27:06 value(0)
%SYS-52 04:41:02 09/2/2020 Upgrade file success 01/0:00 port-00
00:bb:85:07:27:06 value(0)
$ Query post-upgrade workspace files
G1000# show workspace
Work Space 1:Inactive (Expected)
Work Space 2:Active
$ After the update is complete, reset the system and the files take effect.
G1000(config)# system reset
4.2 XML Upgrade Operations

4.2.1 Introduction to XML
G100000 OLT's XML configuration file (DevOem_info.xml) mainly has two aspects: First,
suitable for customers’ need for to customized products, which can be flexible to modify the
product model and ONU models; Second, to increase the ONU support type, the customers do
not need to upgrade the system software, but directly upgrade XML file to complete the new
ONU model support.
4-31
In actual operation, the XML file is not required. If no XML file is to be started, the system will run
with the default device type and description information, the default ONU support type.
If an XML file exists (directory /tffs0/oem/DevOem_info.xml), the system will run with the device
type, description information, and supported ONU type defined in the XML file as configuration
Parameters.
XML will only be read once when the system is initialized. Updating XML during runtime will not
take effect immediately. You must restart the OLT to take effect.
4.2.2 XML Upgrade Operations
Table 4- 3 System upgrade
Enter enable view. Enable

The current XML is named
Use ipv4 address to ftp get host-ipv4 ipv4-address
DevOem_info.xml
download XML file from username password
server to the device. xml-fname1[xml-fname2]
ftp get host-ipv6

Use ipv6 address to
ipv6-addressusername
download XML file from
password
server to the device.
xml-fname1[xml-fname2
Reboot the system SCU is rebooted and take
system reset
effect.
4.2.3 XML Upgrade Operation Example

4.2.3.1 Networking requirements
Upgrade XML file named DevOem_info.xml to the device, with user name and password
G1000.
4-32
Figure 4- 3 xml file upgrade
$ Download the file to the directory from FTP.

G1000# ftp get 192.168.85.193 ver ver DevOem_info.xml
Getting DevOem_info.xml from 192.168.85.193.......
File transfer finished ,4728 bytes received at 0 s.
4.3 Configuration File Operations
The G1000 supports the configuration file to save and restore the factory configuration.
Perform the following configuration in the “enable” view.
Table 4- 4 Configuration file operations
Enter enable view. Enable

Save current configuration Write
Restore the factory
erase startup-config
configuration
Backup “startup.cfg” in the
Backup the configuration active workspace to
startup-config backup
file “startup.backup” in the
active workspace.
Interchange two files
(startup.cfg” and
Switch the configuration file switch-config-file
“startup.backup) in the
inactive workspace.
Synchronize the files of
Synchronize the configuration and system
sync-file(config|scu-fw)
configuration file in the active workspace to
the inactive workspace.
Query the current running-config is the current
show running-config
configuration fail configuration file.
4-33
Query the saved Startup-config is the startup

show startup-config
configuration file configuration file
Note :
Related to the boot upgrade ?, you can now perform local upgrade and management port
upgrade through the console port. Don’t power off during the upgrade to prevent the boot file
from missing, and the system can not start now.
After the factory configuration is restored, it takes effect after the device is rebooted.
After the configuration save command is issued, the running-config and startup-config files are
consistent.
4.4 Network Tool Operations

4.4.1 Introduction to Network Tools
The G100000 supports both IPv4 and IPv6 FTP, Telnet client tools, and Ping tools at the same
time.
4.4.2 Introduction to FTP
FTP protocol is an application layer protocol in the TCP / IP protocol suite, mainly used to
provide file transfer between hosts. The FTP protocol is based on the corresponding file system.
The G100000 supports the FTP client / server function. After the user sets up a connection with
the G100000 through the terminal emulation program or the Telnet program on the host, enter
the ftp command to establish a connection with the remote FTP server and access the files on
the remote server.
4.4.3 Introduction to Telnet
The Telnet protocol is a member of the TCP / IP protocol suite and is the standard protocol for
the Internet remote login service. Telnet protocol can be used by local users into a remote host
computer system, a terminal. The G100000 supports the Telnet service. After the user
establishes a connection with the G100000 through the terminal emulation program or the
Telnet program on the host, enter the telnet command to log in to the remote host system. It
provides convenience for the user.
4.4.4 Introduction to Ping
Ping is a computer network tool used to test whether a particular host to reach through IP. The
G100000 supports the Ping diagnostic command. Enter the command ping or ping6 in the
4-34
command line “enable” to check whether the host can reach the specified IP address through IP.
You can also set the number of ping packets by ping-c.
4.4.5 Network Tool Operation Example

4.4.5.1 Configuration commands
Perform the following operation in the “enable” view.

Table 4-5 Network tool operations
Filename1 is the name of the

file in the ftp server;
Use the ipv4 address to ftp get host-ipv4 ipv4-address
filename2 is the name of the
download files from the ftp username password
file downloaded to the device.
server to the device filename1[ filename2]
The two file names can be
the same.
ftp get host-ipv6 file in the ftp server;
Use the ipv6 address to
ipv6-addressusername filename2 is the name of the
download the file from the
password file downloaded to the device.
ftp server to the device
filename1[ filename2] The two file names can be
the same.
file to be uploaded, and
Use the ipv4 address to ftp put host-ipv4 ipv4-address
upload the files on the username password
file uploaded to the server.
device to the ftp server filename1[ filename2]
the same.
file to be uploaded, and
Use the ipv6 address to ftp put host-ipv6 ipv6-address
upload the files on the username password
file uploaded to the server.
device to the ftp server filename1 [ filename2]
the same.
Telnet remote login ipv4 telnet ipv4 ipv4-address Optional, portid: Port number.
address [portid]
Telnet remote login ipv6 telnet ipv6 ipv6-address Optional, portid: Port number.
address [portid]
Required, count: number of
ping packets, in the range of
ping ipv4-address
The ping tool 1-4. Ipv4-address: ipv4
ping -c count ipv4-address
address, ipv6-address: ipv6
address.
4-35
4.4.5.2 Command example
(1)ipv6 Address Configure：

$ Download startup.backup from the remote FTP server to the device and rename it
startup1.cfg：
G1000# ftp get host-ipv6 2001::3 ver ver startup.backupstartup1.cfg
Getting startup.backup from 2001::3
$ Upload startup.cfg to the remote FTP server and rename it startup1.cfg：
G1000#ftp put host-ipv6 2001::3 ver ver startup.cfgstartup1.cfg
File transfer finished successfully,3661 bytes sent at 0 s.
$ telnet to other devices：
G1000# telnet ipv6 2001::2
*******************************************************
* *
* *
* *
*******************************************************
(2)ipv4 Address configure：

$ Download startup.backup from the remote FTP server to the device and rename it
startup1.cfg：
G1000# ftp get host-ipv4 192.168.85.193 ver ver startup.backupstartup1.cfg
Getting startup.backup from 192.168.85.193....
$ Upload startup.cfg to the remote FTP server and rename it startup1.cfg：
G1000# ftp put host-ipv4 192.168.85.193 ver ver startup.cfgstartup1.cfg
File transfer finished successfully,3661 bytes sent at 0 s.
$ telnet to other devices：
G1000# telnet ipv4 192.168.7.14
*************************************************************************
* *
* *
* *
*************************************************************************
$ ping the specific host：
G1000# ping 192.168.7.14
PING 192.168.7.14: 56 data bytes
Reply from 192.168.7.14: time=0ms TTL=64
----192.168.7.14 PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
$ Set the number of ping specific hosts:

G1000# ping -c 10 192.168.86.10
PING 192.168.86.10: 56 data bytes
4-36

----192.168.86.10 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/2/64
4.5 Restart Operations
The G1000 supports the restart of the system and the specific board.
Table 4-6 Restart operations

Enter config view. configure terminal
Reset he entire system system reset
5 Device Configuration Management
The device configuration management function can display the basic information of some devices,
including the system time zone, time, host name, serial number, and status of each board, and can
support the board and time parameters configuration.
5.1 Time and Time Zone Management
Perform the following operation in the “config” view.

Table 5- 1 Time and time zone management
Set the current time of the datetime year month day hour
system minute second deci-second
Set the current time zone timezone(+ | -) hours minutes
of the system
Restore the time zone no timezone The default time zone is
default configuration the East eight area, the
Beijing time zone.
Query the time and time show system-time
zone configuration.
5.2 Device Information Management

Table 5- 2 Time and time zone management
5-37
Set the host name hostname hostname

Restore the host name no hostname The default host name is
to the default OPLINK.
Configure the device's device (contact|description|location)
contact information, text
description, and location
Configure the device Device resource-locator location-id
resource information rack-id shelf-id
Configure the view password loginword Word: 4-63 bytes
password no password login Reverts to the default value
of yotc.
Configure the enable password privilegeword Word: 4-63 bytes

view password no password privilege Reverts to the default value
of yotc.
word：4-63 bytes
Query the device info show system-info Including device model,

device serial number,
device description, system
uptime and so on.
5.3 System Monitoring

5.3.1 Introduction to System Monitoring
The G1000 contains two 1 + 1 protected power modules to monitor the in-position information of
the power module.
G1000 can monitor the CPU utilization, memory, flash use status.
The G1000 can monitor the temperature of each SCU.
5.3.2 System Monitoring Operation
Perform the following configuration in the “config” view.
Table 5- 3 system monitor
Display the power status. show power-info
Display the CPU show cpu statistics

utilization.
Display the memory, flash show memory statistics
use status.
5-38
Display the temperature show temperature

of each SCU.
Display the fan show fan-info
5.4 Board Management

5.4.1 Introduction to Slot Management
The G1000 system has two single board slot areas:

Slot 1 is fixed to the main control SCU board slot, and the uplink port is in slot 1.
Slot 2 is fixed to the service board GPUHA slot, and the PON port is in slot 2.
If the slot parameter all is specified, all board information in 2 slots is displayed regardless
of whether the board is in place.
At the same time, you can also query the board information for a specific slot number. It can
display the slot ID, board hardware serial number, board hardware version, and board
software version.
5.4.2 Board Management Operations

Table 5- 4 Board management

Displays the information of show slot-info [all]
the boards in slot or all
boards
Display the info of the show board-info
specified boards
5.4.3 Board Management Operation Example
$ Query the information of the in-slot board.

G1000(config)# show slot-info
Slot Id Install Type Expect Type Install Status Run Status
-------------------------------------------------------------------------------
1 scu scu Install Normal
-------------------------------------------------------------------------------
2 gpuha gpuha Install Normal
$ Query the information of the in-slot board.
G1000(config)# show board-info
Board sn :202010100001
Board pn :321654741
5-39
Board hardware version :A

Board software version :603_V300R003B030
Board bootrom version :G1000_gpu_bootrom_V102
Board bootrom date :2020-10-30 10:36:41
5.5 Command timeout setting and split screen setting
The command line will exit overtime if no one operates for a period of time; if the contents of the
display exceed a certain number of lines, the screen will be displayed separately, and you need to
hit the return key again, you can use command timeout settings and screen splitting to control.
For the following operations, please proceed under the config view.
Table 5- 5
Command timeout command timeout <5-60> Unit: Second

settings Default value：20s
Restore the default value no command timeout Unit: Second

of the command timeout.
Default value：20s
Query command timeout show command timeout

settings
Command split screen command max-lines <10-1000> Unit: line

setup
Default value：60
Command split screen no command max-lines Unit: line

settings to restore default Default value：60
values
Query command split show command max-lines

screen settings
5.5.1 Command timeout setting and split screen setting operation

example
$ Setting the configuration of command timeout to 30s：

G1000(config)# command timeout 30
$ Configuring split screen for 100 rows：
G1000(config)# command max-lines 100
5-40
5.6 OLT WIFI Interface Management

5.6.1 Introduction to OLT WIFI Interface
G1000 provides a USB2.0 interface, external USB WIFI network card, and supports other
WIFI terminals to log in to access the OLT WIFI interface to achieve device operation
management.
5.6.2 OLT WIFI interface operation
Perform the following operations in the config view.

Table 5- 6 OLT WIFI interface management
Configure WIFI wifi ssid ssid ssid: 1-32 length

interface ssid characters.
Configure WIFI wifi password password password: 8-64

interface password characters, the
default password is
password
Configure WIFI wifi ipv4 ip mask ip: ipv4 address,

interface ip the default value is
192.168.0.1
mask: mask, the

default value is
255.255.255.0
Display WIFI interface show wifi-info

information
5.6.3 Example of OLT WIFI Interface Operation
$ Configure WIFI interface ssid

G1000(config)# wifi ssid YOTC-02468C
$ Configure WIFI interface password：
G1000(config)# wifi password 987654321
$ Configure WIFI interface ip：
G1000(config)# wifi ipv4 192.168.1.1 255.255.255.0
$ Display WIFI interface：
G1000(config)# show wifi-info
5-41
IP : 192.168.0.1
MASK : 255.255.255.0
SSID : YOTC-02468C
PASSWORD : password
MAC : 00:1a:69:02:46:8c
6 VLAN Configuration Managment

6.1 VLAN Configuration Management
6.1.1 Introduction to VLAN Knowledge
6.1.1.1 VLAN overview
The traditional Ethernet is a planar network; all the hosts in the network are connected by HUB or
switch devices, and are in the same broadcast domain. HUB is a physical layer device, no
exchange function, and the received packet will be forwarded to all ports; the switching device is a
link layer device. It has the ability to forward packets based on the MAC address of the packets.
When receiving a broadcast packet or an unknown unicast packet (The destination MAC address
of the packet does not exist in the MAC address table of the switch) , the switching device uses the
MAC address of the packet to transmit the packet to all ports except the inbound interface
In this case, the host in the network receives a large number of packets that are not destined for it.
This wastes a large amount of bandwidth resources and causes serious security risks. The
isolated broadcast domain of the traditional method is to use the router, but the router cost is
higher, and the port is small, cannot be divided into detailed network. VLAN (Virtual Local Area
Network) technology has emerged in order to solve the problem that the Ethernet switching
equipment cannot restrict broadcasting in the LAN.
A VLAN divides a physical LAN into logical LANs, each of which is a broadcast
domain. Host-to-host communication within a VLAN is the same as within a LAN, and hosts
between different VLANs cannot communicate directly.
The composition of a VLAN is not limited by the physical location. A VLAN can be in a switching
device, can also cross the exchange of equipment, or even cross the router. Computers in the
same VLAN do not need to be placed in the same physical space, that is, they do not necessarily
belong to the same physical network. As shown in Figure 6 1.
6-42
Figure 6- 1 VLAN division
6.1.1.2 VLAN principle
To enable the network device to distinguish packets of different VLANs, you need to add the fields
that identify the VLANs in the packets. As the switching equipment in the second layer (Layer 3
functions not discussed), can only identify the data packet’s data link layer
encapsulation. Therefore, the identification field needs to be added to the data link layer
encapsulation.
In 1999, the IEEE published a draft of the IEEE 802.1Q protocol standard for standardizing VLAN
implementation, which defined the message structure with VLAN identification.
The traditional Ethernet data frame encapsulates the upper layer protocol type field after the
destination MAC address and the source MAC address field, as shown in Figure 6-2.
Figure 6- 2 traditional Ethernet data frame format
In Fig 6-2, DA is the destination MAC address, SA is the source MAC address, and Type is the
protocol type of the packet. Normally, the value of this field is 0x0800 in the Ethernet frame.
IEEE 802.1Q specifies that the destination MAC address and source MAC address are
encapsulated with 4-byte VLAN tags to identify VLAN-related information. As shown in Figure 6-3.
6-43
Figure 6- 3 802.1Q data frame format
Tag VLAN contains 4 fields, namely, TPID, Priority, CFI, ID VLAN, total length of 4 bytes
 The TPID is used to indicate the data frame with VLAN Tag, length 16 bits, the default value is
0x8100.
 Priority said 802.1P priority, the length of 3bit. For specific uses, see"16.1.3 Priority" of the
Manual.
 The CFI field indicates whether the MAC address is encapsulated in a standard format in
different transmission media. The length of the CFID field is 1 bit.
 The VLAN ID identifies the VLAN to which the packet belongs. The length of the packet is 12
bits, in the range 0 to 4095. Because 0 and 4095 are not used, the VLAN ID ranges from 1 to
4094.
6.1.1.3 Introduction to general and flexible QinQ
QinQ, also known as VLAN stacking, encapsulates a customer network CVLAN tag in a service
provider network or a metropolitan area network (SVLAN) tag. The packet carries a two-layer tag
through the service provider backbone network. In the public network, packets are propagated
based on the outer VLAN tag and the CVLAN tag of the user network is masked. In this way, not
only the data flow is differentiated, but also the user VLAN tag is transparently transmitted.
Different user VLAN tags can be reused. Only the outer VLAN tag can be used on the public
network. The usual 802.1Q data frame format and the data frame format with two layers of tags
are shown in Figure 6-4, from which you can see the difference.
Figure 6- 4 802.1Q data frame and QinQ data frame format comparison...
QinQ is originally created for expanding VLAN capacity. Adding 802.1Q tags to the original 802.1Q
packets can increase the VLAN capacity to 4094 * 4094.
With the development of metro Ethernet and the requirement of operators' fine operation, QinQ
6-44
double-layer tag has a further use scenario. Its inner and outer tags can represent different
information, such as inner CVLAN tag for distinguishing users , And the outer SVLAN tag is used
to represent the service.
There are two methods for encapsulating outer VLAN tags. One is an ordinary QinQ encapsulation.
That is, an outer VLAN tag is based on a port. All user data under the same port encapsulate a
common VLAN tag, which is too restrictive in practical applications. . The other is selective QinQ
encapsulation. That is, you can classify user data according to some features, and then
encapsulate different outer VLAN tags in different classes. YOTC implements the classification of
traffic by ACL according to the information such as user VLAN TAG, MAC address, IP protocol,
source address, and destination address and application port number. This allows different types
of traffic to be tagged with different outer VLAN tags to implement selective QinQ (depending on
the hardware chip type).
802.1ad standard was supplement to in the 802.1Q. The IEEE 802.1ad (QinQ) standard describes
how Ethernet implements S + C and expands VLAN capacity. 802.1ad describes two types of
interfaces: port-based service interface and C-tagged service interface. The port-based mode tags
a port uniformly with an outer Q (common QinQ), and a customer-based mode tag uses with a
different QinQ（flexible QinQ）according to different user tags. Please refer to the relevant
standards for more information.
6.1.2 OLT Port-based VLAN
G1000 OLT port includes the uplink ports and the PON ports on the EPU8A board. OLT port-based
VLAN is to divide the OLT ports of the device into different VLANs, thus isolating users and
dividing virtual workgroups.
6.1.2.1 Introduction to different OLT port types
After the G1000 OLT device is powered on and initialized, all ports default to hybrid mode.
The port can be set to both transparent and hybrid.

The transparent port is user-oriented and supports VLAN transparent transmission. It supports
VLAN switching (1: 1), and supports QinQ and Vlan-based QinQ applications.
In practice, the configuration of the VLAN mode on the G1000 OLT port is as follows:
Transparent port: Normally, the transparent mode is configured on the lower port (for example,
PON port). In this mode, the port can perform VLAN translation and QinQ functions.
Hybrid port: Normally, the uplink port is configured as hybrid mode. In this mode, the port cannot
perform the VLAN translation or QinQ operation, or the QinQ / translation entry cannot be
configured on the port.
6.1.2.1.1 Port VLAN based on hybrid mode
Hybrid: A port can belong to multiple VLANs. It can receive and send packets of multiple VLANs,
and implement transparent transmission of specified VLANs. It determines whether to strip tags
based on the export mode. It can be used to connect a G1000 to a switch, router, or server PC, or
6-45
to an ONU. By default, all OLT ports are hybrid.

In this mode, the data packets processed by the port pair of this type are processed as follows:
Table 6- 1 process of Hybrid port receiving and sending packets
Ingress of packets
Egress of packets
Packets without Tag Packets with Tag

 If the port is in the VLAN
 If the port is in the
specified by the tag of the packet,
VLAN specified by the
the port will be sent, and the port
Because the port must tag of the packet, it will
will be configured according to the
be in the VLAN specified be forwarded.
egress ? to determine whether to
by its PVID, the packet is
strip the tag.
tagged with the default If the port is not in
 If the port is not in the VLAN
tag and forwarded. the VLAN specified by
specified by the tag of the packet,
the tag of the packet, the
the port will be discarded.
port will be discarded.
6.1.2.1.2 Port VLAN based on Transparent mode
If the packet carries a tag, check the VLAN translation table of the port. Only the CVLAN in the
conversion table is used for QinQ (Add SVLAN beside CVLAN) or translation (Replace CVLAN by
SVLAN). All other packets outside the table are tagged with the outer_tpid, PVID, and priority of
the port, assuming that the port allows Svlan to pass through.
Translation: For G1000, one side connects to the customer network and the other side
connects to the service provider network. The tag provided by the customer network is not trusted
by the network. The port connecting the two networks needs to be set to translation mode. The
port connecting to the user network replaces the user network tag in the uplink data with the VLAN
tag trusted by the provider network. The port connecting to the service provider network converts
the VLAN tag in the downlink data to the user network Tag.
QinQ: applies to the G1000, where one side connects to the customer network and the other
side connects to the service provider network. The service provider network uses SVLAN tags to
differentiate services, while the customer network uses CVLAN tags to differentiate users. In this
case, the port connected to the user network needs to be set to transparent mode and the nested
table is configured. The service provider network SVLAN tag is added to the outer layer of the
customer network CVLAN tag for the upstream packet. For the downlink packet, the outer VLAN
tag is removed and the packet is forwarded to the user network.
The egress direction of the Transparent port will strip the SVLAN, and the egress direction will
use the SVLAN index to find the corresponding CVLAN. The CVLAN replaces the CVLAN of the
original packet.
6.1.2.2 Adding a port to a specified VLAN
You can add an OLT port to a specified VLAN. After the configuration, the OLT port can forward the
6-46
packets of the specified VLAN, thus enabling the VLAN on the local device to communicate with
the same VLAN on the peer switch.
When adding a port to a VLAN egress, you need to specify the mode of the port in the VLAN, that
is, whether the port strips the tag when sending the VLAN packet. Tagged means not to strip the
tag, and untagged to strip the tag.
Note:
 Hybrid application: According to networking requirements, ports can be added to multiple

VLANs.
 Transparent application: ? Must be added to the VLAN specified by port PVID (default VLAN
ID), and set the egress mode to untagged.
 Translation application: The ports connected to the network side and the service provider
network side must be added to the VLAN (s) specified by CVLAN (s), SVLAN (s), and the
egress mode is set to tagged.
 QinQ: The port connected to the user network side must be added to the VLAN (s) specified
by SVLAN (s), and the egress mode is set to untagged. Accordingly, the port on the service
provider network side needs to be set to hybrid port and added to the VLAN (s) specified by
SVLAN (s), and the egress mode is set to tagged.
In addition, translation applications need to configure VLAN translation table for CVLAN (s) ->
SVLAN (s) and SVLAN (s) -> CVLAN (s) conversion; QinQ applications need to configure VLAN
nested table, CVLAN (s) Layer to add SVLANs.
6.1.2.3 Configuring the Default VLAN of a Port
The G1000 depends on the VLAN tag and MAC address (SA & DA) for Layer 2
forwarding. Packets with untagged VLAN tags are sent to the G1000 as untagged packets. A
default VLAN tag is set, including the default VLAN ID (PVID) and default priority.
Note that a Hybrid port can belong to multiple VLANs in a hybrid application. The default VLAN ID
needs to be specified. By default, the hybrid port belongs to multiple VLANs. It is proposed that the
default VLAN ID of the hybrid port on the G1000 and the default VLAN ID of the hybrid port on the
peer device are the same. Otherwise, the port may not forward the packets of the default VLAN
correctly.
6.1.3 VLAN Based on ONU Port

6.1.3.1 VLAN types of ONU port
Currently, the ONU ports supported by the G1000 are supported by the following types of
VLANs:
 Transparent type: The home gateway or switch that is applied to the user terminal is provided
and managed by the service provider. The VLAN tag generated by the home gateway or the
switch is trustworthy. This type of ONU port does not process any incoming Ethernet frames,
6-47
regardless of whether the Ethernet frame carries a VLAN tag or not, and transparently
forwards the packets upwards. The downstream Ethernet frames are also transparently
forwarded.
 Tag type: VLAN tags tagged by home gateways or switches of the clients are not trusted. In
order to implement the unified management and control of the VLANs of the services
entering the network, the service provider needs to add a VLAN tag to the network.
 Translation Type: An ONU port translates a user-supplied VLAN Tag (whose VID may not be
used by the user uniquely, other users may use the same VID in the same system) to a
unique network-side VLAN tag.
 Trunk type: The ONU port tags the received untagged packets as port pvid. For a VLAN
tagged packet in the trunk list, packets that are not in the trunk list are not allowed to pass
through.
Description
ONU's translation port has a VLAN Translation (UniVlan-> CniVlan) table which is
queried by both uplink and downlink business. The difference is the lookup directions,
that is, the former VLAN tag UniVlan is used as forward lookup, while the latter VLAN tag
tag CniVlan is used as reverse lookup.
6.1.3.2 Packet processing by ONU port
After the ONU registers normally, the four types of ONU ports have different processing modes for
the uplink and downlink data. The details are described in the following table.
Table 6- 2 Processing the uplink and downlink services on the ONU Transparent port
Directions VLAN tag or not Processing mode

Y Forward the packet without any processing
Uplink
N Forward the packet without any processing
Y Forward the packet without any processing
Downlink
N Forward the packet without any processing
Table 6- 3 Processing the uplink and downlink services on the ONU Tag port
Directions VLAN tag or not Processing mode

Y Discard
Uplink
N Tag the specified VLAN Tag and and forwarding
Only packets with the specified VLAN are
Y
Downlink received and the tag is removed.
N
Table 6- 4 Processing the uplink and downlink services on the ONU translation port
Processing mode
Directions VLAN tag or not
6-48
If an entry exists in the VLAN Translation table,

the original tag is replaced with a new one and
forwarded. If the VLAN Translation default tag
Y
Uplink entry exists, the packet with this tag is forwarded;
otherwise, the packet is discarded.
N Packets with the default VLAN tag are forwarded
If an entry exists in the VLAN Translation table,

the original tag is replaced with a new one and
forwarded. If the VLAN Translation default tag
Y
Downlink entry exists, the downstream packet with this tag
is stripped at the ONU egress. Otherwise, the
packet is discarded.
N Discard
Table 6- 5 Processing the uplink and downlink services on the ONU trunk port
Processing mode
Directions VLAN tag or not
If the VLAN of the packets belongs to the

With tag permitted trunk VLAN of the port, the packets are
forwarded upstream. If not the packets are
Uplink
discarded.
Without tag Tag the packet with default VLAN Tag and
forward it.
If the VLANs of the packets belong to the
permitted trunk VLAN of the port, the packets are
forwarded downstream.
If the VLAN is the default VLAN (port PVID), the
With tag VLAN tag is removed and the packet is
forwarded.
Downlink
If the VLANs of the packets doesn’t belong to the
permitted trunk VLAN of the port, the packets are
discarded.
Without tag
Discard
6.2 OLT VLAN Configuration and Application
Description
Before configuring the default VLAN ID for each port, the VLAN must be created first.
When the default VLAN ID of each port is configured, the port automatically adds the port
6-49
to the VLAN of its default VLAN.
6.2.1 OLT VLAN Configuration
Table 6- 6 OLT VLAN configuration Command line

Enter config view. configure terminal -
Configure global tpid. outer-tpid tpid Tpid: hexadecimal
no outer-tpid format beginning
with 0x.
Query global tpid. show tpid
Create/Delete vlan. vlan start-id [end-id] Create a vlan, if
no vlan start-id [end-id] there is only one
parameters, enter
the vlan view.
Add/Delete ports in port interface-number(tagged | untagged) Enter “VLAN” view
“vlan” view. no port interface-number first.
Query vlan. show vlan（all | vlanid）
Query the specified show port vlan olt x/y x/y：OLT port.
port vlan configuration.
Enter OLT port view. interface olt interface-number
Configure the port priority pri pri：0-7
priority. no priority
Configure the port port pvid pvid pvid：1-4094
pvid. no port pvid
Configure the port vlan port type (hybrid | transparent)
type.
Configure the port to port vlan vlan-id (tagged | untagged )
join / leave the vlan. no port vlan vlan-id
port vlan start-id to end-id(tagged | untagged)
no port vlan start-id to end-id
Configure the port modified-vlan old-vlanid modified-vlanid Use it in PON
conversion table. modified-pri interface’s
. port nested-vlan < cvlan start-id > to < cvlan Transparent mode.
end -id > < nested-vlanid > <0-7>
no port modified-vlan （old-vlanid|all）
Delete the conversion no port nested-vlan（cvlanid|all） Use it in PON
Table no port nested-vlan < cvlan start-id > to < cvlan interface’s
end -id > Transparent mode.
Query the port vlan show port vlan
configuration.
6.2.2 Basic Configuration Example of VLAN
6-50
Enter “config” view.

G1000(config)#
Create VLAN and enter “VLAN” view.

G1000(config)# vlan 20
G1000(config-vlan-20)#
Add the port to the VLAN, and the egress mode is tagged and untagged.
G1000(config-vlan-20)#port 1/1 tagged
G1000(config-vlan-20)#port 2/1 untagged
Delete the existing VLAN.

G1000(config)# no vlan 20
6.2.3 Examples of Applications Based on Hybrid
The hybrid port allows multiple VLANs to pass through. For details on how to process packets, see
6.1.2.1.1.
Description
Before setting a VLAN to allow the specified VLAN to pass through the hybrid port, the
allowed VLAN must already exist. The default VLAN ID of the hybrid port of the local
device must be the same as the default VLAN ID of the hybrid port of the peer device.
Otherwise, packets cannot be transmitted correctly.
 Create VLAN10 and VLAN20

 Configure PON port 2/1 and add it to VLAN10, in tagged egress mode; add PON port 2/4
to VLAN20, in untagged egress mode, and PVID port is 20; configure the uplink port 1/1
and add it to VLAN10 and VLAN20, in tagged egress mode.
6-51
Figure 6- 5 CVLAN example of Hybrid port
$ Create VLAN10：
G1000#configure terminal
G1000 (config-vlan-10)# exit
$ Create VLAN20：
$ Configure PON port 2/1 as hybrid port and add it to VLAN10, in tagged egress mode;：
G1000(config)# interface olt 2/1
G1000(config-if-gpon-2/1)#port type hybrid
G1000(config-if-gpon-2/1)#port vlan 10 tagged
$ Add PON port 2/4 to VLAN20, in untagged egress mode and PVID port is 20:
G1000 (config-if-gpon-2/4)#port type hybrid
G1000 (config-if-gpon-2/4)#port vlan 20 untagged
G1000 (config-if-gpon-2/4)#port pvid 20
$ Configure the uplink port 1/1 as hybrid port and add it to VLAN 10 and 20, in tagged
egress mode.
G1000(config)#interface olt 1/1
G1000(config-if-gigabit-ethernet-1/1)#port type hybrid
G1000(config-if-gigabit-ethernet-1/1)#port vlan 10 tagged
6.2.4 Example of Application Based on Transparent

6.2.4.1 VLAN transparent application
Transparent application: a port can receive and send arbitrary packets regardless of whether
the packet carries a VLAN tag or not. Effect: completely transparent, from the transparent port
into / out, transparent port out / into. Any package can go in and out intact.
6-52
6.2.4.1.1 Networking requirements
 Transparent transmission of packets between PON port 2/1 and uplink port 1/1.
 PON port configuration: transparent mode, pvid 1, join VLAN 1 in untagged mode.
 Uplink port configuration: transparent mode, pvid 1, join VLAN 1 in untagged mode.
6.2.4.1.2 Networking Figure
Figure 6- 6 VLAN transparent figure
6.2.4.1.3 Configuration procedure
$ Configure PON port 2/1 as transparent port:

G1000 (config-if-gpon-2/1)#port type transparent
$ Configure the uplink port 1/1 as transparent port:
G1000 (config-if-gigabit-ethernet-1/1)#port type transparent
G1000 (config-if-gigabit-ethernet-1/1)# port vlan 1 untagged
6.2.4.2 VLAN Translate application
Translate Application: This mode is used when the G1000 side is connected to the customer
network and the other side is connected to the service provider network. The tag provided by the
user network is not trusted by the network of the service provider. The port connecting to the
customer network replaces the user network tag in the upstream data with the VLAN tag trusted by
the provider network. The port connecting to the service provider network converts the VLAN tag in
the downlink data into the user network tag.
 1：1 VLAN conversion
Effect: Get in from the transparent port and out from the hybrid port. In the upstream direction,
different CVLANs in the ingress VLAN conversion table are replaced with different SVLANs
according to the entries in the translation table. In the downstream direction, use the SVLAN index
in the egress vlan conversion table and replace it with the required CVLAN according to the entries
in the conversion table. The original priority can be modified or retained.
The transparent port is set to 1:1 conversion. And add the mapping table to the ingress VLAN
conversion table; priority can be modified or retained. The corresponding egress VLAN mapping
table is automatically added to the ingress reverse mapping table, and the same priority handling
policy is adopted.
6-53
 Create VLAN 100, VLAN 2000, VLAN 10, and VLAN 200, where VLAN 10 and VLAN 200 are
configured as customer network CVLAN tags and VLANs 100 and 2000 as service provider
SVLAN tags.
 In upstream, PON port 2/1 converts CVLAN 10 to SVLAN 100, priority becomes 1;
correspondingly in downstream, the uplink port 1/1 converts SVLAN 100 to CVLAN 10.
 In upstream, PON port 2/4 converts CVLAN 200 to SVLAN 2000, the
priority becomes 7, correspondingly in downstream, the uplink port 1/1 conversion SVLAN
2000 to CVLAN 200. Note: The uplink port and the PON port are added to the SVLAN. If they
are added to the SVLAN in the tagged mode, the upstream and downstream packets are
tagged. If the upstream is tagged, the downstream is untagged, then the downstream
receives the packets without the tag, while the upstream is packets with the tag; If the
upstream is untagged and the downstream is tagged, the the upstream receives the packets
without tags and the downstream packets with tags.
Figure 6- 7 VLAN Conversion figure
$ Create VLAN 200:

G1000(config-vlan-200)# exit
$ Create VLAN 2000:
$ Create VLAN 10:
$ Create VLAN 100:
$ Configure PON port 2/1 as a transparent port, convert 10 to 100, and change the
priority to 1:
G1000(config-if-gpon-2/1)#port type transparent
G1000(config-if-gpon-2/1)#port vlan 100 tagged
G1000(config-if-gpon-2/1)#port modified-vlan 10 100 1
$ Configure PON port 2/4 as a transparent port, convert 200 to 2000, and change the
6-54
priority to 7:
G1000(config-if-gpon-2/4)# port type transparent
G1000(config-if-gpon-2/4)# port vlan 2000 tagged
G1000(config-if-gpon-2/4)# port modified-vlan 200 2000 7
$ Configure the uplink 1/1 as hybrid port and be added to SVLAN：
G1000(config)# interface olt1/1
G1000 (config-if-gigabit-ethernet-1/1)#port type hybrid
G1000 (config-if-gigabit-ethernet-1/1)#port vlan 2000 tagged
6.2.4.3 VLAN QinQ application
QinQ: applies to the G1000, where one side connects to the customer network and the other
side connects to the service provider network. The service provider network uses SVLAN tags
to differentiate services, while the customer network uses CVLAN tags to differentiate users.
In this case, the port connected to the user network needs to be set to transparent mode and
the nested table is configured. The service provider network SVLAN tag is added to the outer
layer of the customer network CVLAN tag for the upstream packet. For the downlink packet,
the outer VLAN tag is removed and the packet is forwarded to the user network.
 Create VLAN 200, 300, and VLAN 2 , where VLAN 200, 300 are configured as customer
network CVLAN tag to differentiate customers, and VLAN 2 as service provider network
SVLAN tags to tag data service.
 For upstream data PON port 2/1 tags CVLAN 200 with SVLAN 2, and change the priority to 5;
and strips SVLAN for downstream data.
 For upstream data PON port 2/4 tags CVLAN 300 with SVLAN 2, and change the priority to 1;
and strips SVLAN for downstream data.
Figure 6- 8 Example of a VLAN stack
$ Create VLAN 200：

$ Create VLAN 300：
6-55

$ Create VLAN 2：
$ Configure PON port 2/1 as transparent mode and configure nested table entries to tag
CVLAN200 with SVLAN2, and change priority to 5.
G1000 (config-if-gpon-2/1)#port nested-vlan 200 2 5
$ Configure PON port 2/4 as transparent mode and configure nested table entries to tag
CVLAN300 with SVLAN2, and change priority to 1.
G1000 (config-if-gpon-2/4)#port nested-vlan 300 2 1
$ Configure the uplink port 1/1 as hybrid port：
G1000 (config-if-gigabit-ethernet-1/1)#port type hybrid
6.3 Onu VLAN Configuration and Application
Description:
Assume that the ONUs in all the configuration examples below are registered and authorized,
and will not be described again.
By default, the ONU port VLAN configuration is transparent
ONU port, in translation mode, cannot convert a number of different vid into the same
vid, and vice versa.
6.3.1 Onu VLAN Configuration Procedure
Table 6- 7 ONU VLAN configuration command line

Enter “ONU” view interface onu onuid -
Configuration port in port vlan mode (uniid | all)tag Required, uniid:
tag mode port vlan default-vlan uniid vlanid pri ONU port
number, in the
range of 1-4, pri:
Priority.
Configuration port in port vlan mode (uniid | all) translation Required, oldtag:
translation mode port vlan default-vlan uniid vlanid pri vlan before
port vlan translation uniidlist oldtag conversion,
newtag pri newtag:
converted vlan
value.
Configuration port in port vlan mode (uniid | all) transparent Required.
6-56
transparent mode
Configuration port in port vlan mode (uniid | all) trunk Required.
trunk mode port vlan default-vlan uniid vlanid pri
port vlan trunk uniid vlanid
Query ONU port VLAN show port vlan (uniid | all)
Exit “ONU” view and exit
enter “config” view
Query the port VLAN show port vlan onu x/y/z(portid|all) x/y/z: onu ID.
configuration of the portid ： the
specified ONU interface number
of ONU, value
range: 1-4.
6.3.2 VLAN Transparent Transmission Example

 Add VLAN 10, connect the GE 1/1 port of the OLT to the user PC1, add the port to VLAN
10, egress mode is the untagged, and set the PVID to 10.
 Add the PON 2/1 port of the OLT to VLAN 10, and egress mode is the tagged.
 Connect the user PC2 to the Layer 2 switch connected to the ONU2/1/1, and the ONU
port is set to transparent mode.
 Add the Layer 2 switch user port connected to ONU2/1/1 to VLAN 10, and the egress
mode is untagged.
6-57
Figure 6- 9 Configuration of ONU port transparent transmission
$Create VLAN 10:

G1000(config-vlan-10)#exit
$Add GE port 1/1 to VLAN 10, egress mode is untagged and PVID is 10:
G1000(config-if-gigabit-ethernet-1/1)#port vlan 10 untagged
G1000(config-if-gigabit-ethernet-1/1)#port pvid 10
$Add PON port 2/1 to VLAN 10, and egress mode is tagged:
G1000(config-if-pon-2/1)#port vlan 10 tagged
$Configure all ONU ports as transparent transmission mode:
G1000(config)# interface onu 2/1/1
G1000(config-if-onu-2/1/1)#port vlan mode all transparent
6-58
6.3.3 Example of VLAN Tagging

 Add VLAN 10, connect the GE 1/1 port of OLT to the user PC1, add the port to VLAN 10,
egress mode is untagged, and set PVID to 10.
 Add the PON 2/1 port of OLT to VLAN 10, and egress mode is the tagged.
 Connect ONU2/1/1 to the user PC2
 Set the port that connects ONU2/1/1 with PC2 to tag mode, set VID to 10 and set priority
to 0.
6-59
Figure 6- 10 Configuration of ONU port tagging
$Create VLAN10:
$Add GE port 1/1 to VLAN 10, egress mode is untagged and PVID is 10:
$Add PON port 1/1 to VLAN and egress mode is tagged:
$Configure all ports of ONU as tag mode:
6-60

G1000(config-if-ont-2/1/1)#port vlan mode all tag
G1000(config-if-ont-2/1/1)#port vlan mode 1 tag
G1000(config-if-ont-2/1/1)#port vlan default-vlan 1 10 0
6.3.4 VLAN Conversion Example

 Add PON 2/1 port of OLT to VLAN 10 and 20, and egress mode is tagged.
 Connect PC3 and PC4 to L2 switch connecting to ONU 2/1/1.
 Configure VLAN of ONU 2/1/1 port connecting to L2 switch as translation. Configure two
conversion entries, converting 101 to 10 and converting 102 to 20.
 Connect the Layer 2 switch user port connecting to ONU 2/1/1 with PC3 and add to VLAN
101, connect to PC4 and add to VLAN 102, and the egress mode is untagged. The uplink
port of the switch is added to VLAN 101 and 102, and the egress mode is tagged.
6-61
Figure 6- 11 Configuration of ONU port conversion
$Create VLAN 10:

$Create VLAN 20:
$Add GE port 1/1 to VLAN 10, the egress mode is untagged and PVID is 10:
6-62
$Add PON port 2/1 to VLAN10 and 20, the egress mode is tagged：
$Configure port 1 of ONU 2/1/1 as translation mode, and configure two conversion
entries to convert 101 to 10, and convert 102 to 20:
G1000(config)#interface onu 2/1/1
G1000(config-if-onu-2/1/1)#port vlan mode 1 translation（This step must be done first,
otherwise the conversion table can not be configured.）
G1000(config-if-onu-2/1/1)#port vlan mode 1 translation
G1000(config-if-onu-2/1/1)#port vlan translation 1 list 101 10 0
G1000(config-if-onu-2/1/1)#port vlan translation 1 list 102 20 0
6.3.5 VLAN Trunk Example

 Add VLAN 10, connect the GE 1/1 port of OLT to the user PC1, add the port to VLAN
10, egress mode is untagged, and set PVID to 10.
 Add VLAN 20, connect the GE 1/2 port of OLT to the user PC2, add the port to
VLAN 20, egress mode is untagged, and set PVID to 20.
 Add PON 2/1 port of OLT to VLAN 10 and 20, and egress mode is tagged.
 Connect PC3 and PC4 to L2 switch connecting to ONU 2/1/1.
 Configure VLAN of ONU 2/1/1 port connecting to L2 switch as trunk mode, and
configure trunk VLAN 10 and 20.
 Connect with PC3 the Layer 2 switch user port connecting to ONU 2/1/1 and add to
VLAN 10, connect to PC4 and add to VLAN 20, and the egress mode is
untagged.The uplink port of the switch is added to VLAN 10 and 20, and the egress
mode is tagged.
6-63
Figure 6- 12 ONU port trunk configuration
$Create VLAN10:
$Create VLAN20:
6-64
$Add PON port 2/1 to VLAN 10 and 20, the egress mode is tagged:
$Configure port 1 of ONU 2/1/1 as trunk mode, configure port pvid as 100 and add two
trunk vlan 10 and 20:
G1000(config-if-onu-2/1/1)# port vlan mode 1 trunk （ This step must be done first,
otherwise the conversion table can not be configured.）
G1000(config-if-onu-2/1/1)#port vlan default-vlan 1 100 1
G1000(config-if-onu-2/1/1)port vlan trunk 1 10
G1000(config-if-onu-2/1/1)port vlan trunk 1 20
7 OLT Port Configuration Management

7.1 Basic Configuration of OLT Port
7.1.1 Introduction to Basic Configuration
The OLT port here refers to the PON ports and the uplink ports on G1000.
The basic configuration of the OLT port includes the settings of port on/off and port rate duplex
mode.
The OLT port of G1000 has Gigabit ports and 10 Gigabit ports. The uplink ports on the uplink
board can be configured with rate duplex mode.
For the uplink Gigabit port, only 1Gfdx and auto settings are supported, and for the uplink 10
Gigabit port, only 10Gfdx and 1Gfdx settings are supported. The MDI / MDIX type of the port
means the port jumper type. The MDI is called the parallel mode media interface and the
MDIX is called the cross-mode media interface.
Figure 7- 1 Connection of MDI and MDIX interfaces

Generally, the port of the router and the PC is the MDI interface, and the port of the switch is
MDIX. The MDI interface is connected to the MDIX interface with direct cable, and the two
MDI interfaces are connected with crossover cable.
7-65
7.1.2 Basic Configuration Command
Table 7- 1 Basic configuration command

Enter OLT port view. interface olt interface-number
Configure port port admin (enable|disable)
enable/disable
Query port show interface-config Only for GE and
configuration. XE ports
Query port info. show port-info
Query port flow-control show flow-control Only for GE and
info. XE ports
Configure port rate speed-duplex Only for GE and
duplex mode. (auto|10hdx|10fdx|100hdx|100fdx|1Ghdx| XE ports
1Gfdx|10Gfdx)
no speed-duplex
7.1.3 Basic Configuration Example
$Enter olt port view after entering config view:

G1000(config-if-gigabit-ethernet-1/1)#
$ Enable/disable port:
G1000(config-if-gigabit-ethernet-1/1)#port admin disable
G1000(config-if-gigabit-ethernet-1/1)#port admin enable
$ Set port duplex mode:
G1000(config-if-xgigabit-ethernet-1/9)#speed-duplex 1Gfdx
$ View port status:
G1000(config-if-xgigabit-ethernet-1/9)#show port-info
Port Admin State : enable
Port Description :
Physical Interface : A-Hot Swap
Port Working Type : 10GBASE-R
Work state : 1Gfdx
Real work state : 1Gfdx
Link Status : Link Up
7.2 OLT Port Packet Suppression

7.2.1 Introduction to Packet Suppression Configuration
By configuring packet suppression, the user can limit the size of broadcast / multicast / unknown
unicast traffic that is allowed on the port.
When the broadcast / multicast / unknown unicast traffic exceeds the threshold set by the user,
the system will discard packets that exceed the traffic limit so that the traffic rate of broadcast /
multicast / unknown unicast traffic is reduced to a reasonable range to ensure the normal
7-66
operation of the network business.
7.2.2 Packet Suppression Configuration Commands
Table 7- 2 Packet suppression configuration command

Enter olt port view. interface olt interface-number
Enable/disable broadcast-suppression rate rate：1-14881000，
broadcast packet no broadcast-suppression unit: pps.
suppression on uplink
port.
Enable/disable mcast-suppression rate rate：1-14881000，
multicast packet no mcast-suppression unit: pps.
port.
Enable/disable unicast-suppression rate rate：1-14881000，
unknown unicast no unicast-suppression unit: pps.
packet suppression on
uplink port.
Query packet show storm-control
port.
Enable/disable gpon storm-control Default: not limited.
broadcast packet broadcast-suppression rate rate：2-1860125
suppression on PON no gpon storm-control
port. broadcast-suppression
multicast packet mcast-suppression rate rate：2-1860125
suppression on PON no gpon storm-control
port. mcast-suppression

unknown unicast unicast-suppression rate rate：2-1860125
packet suppression on no gpon storm-control
PON port. unicast-suppression
Query packet show gpon storm-control

suppression on PON
port.
7.2.3 Example for Packet Suppression Configuration
$Enter olt port view after entering config view:

G1000(config-if-gpon-2/1)#
$Limit broadcast traffic allowed on the current port to 100 pps (optional. By default, the port
does not limit the broadcast traffic), and then cancel the limit (“no” command):
G1000(config-if-gpon-2/1)# gpon storm-control broadcast-suppression 100
7-67
G1000(config-if-gpon-2/1)#show gpon storm-control

Port : 2/1
Broadcast suppression : 100pps
Unicast suppression : 1488100pps
Mcast suppression : 1488100pps
G1000(config-if-gpon-2/1)#no gpon storm-control broadcast-suppression
Port : 2/1
$Limit multicast traffic allowed on the current port to 200 pps (optional. By default, the
port does not limit the multicast traffic), and then cancel the limit (“no” command):
G1000(config-if-gpon-2/1)# gpon storm-control mcast-suppression 200

Port : 2/1
G1000(config-if-gpon-2/1)#no gpon storm-control mcast-suppression
Port : 2/1
$Limit unknown unicast traffic allowed on the current port to 300pps, (optional. By default, the
port doesn’t limit the unknown unicast traffic), and cancel the limit (“no” command):
G1000(config-if-gpon-2/1)# gpon storm-control unicast-suppression 300

Port : 2/1
G1000(config-if-gpon-2/1)#no gpon storm-control unicast-suppression
Port : 2/1
8 Port Isolation Configuration Management

8.1 PON Port Isolation Management
8.1.1 Introduction to PON Port Isolation
By configuring PON port isolation, users can isolate Layer 2 data between the PON ports and the
downlink ONUs on different PON ports. This enhances the network security and facilitates the
management of the carrier.
Note:
8-68
 After PON port isolation is configured, only the packets between PON ports cannot
communicate with each other. The communication between the PON port and the
uplink port and between the uplink ports is not affected.
 PON port isolation is independent of the VLAN to which the PON port belongs. Even if the
PON ports belong to the same VLAN, the PON ports cannot communicate after they are
isolated.
8.1.2 PON Port Isolation Configuration
Table 8- 1 PON port isolation Configuration

Enter “config” view. config terminal -

Enable/disable PON isolation. isolate (enable | disable) Required.
Query PON isolation. show isolate Optional
8.1.3 PON Port Isolation Configuration Example

 The ONU registered to PON port 2/1 and the ONU registered to PON port 2/4 can’t
communicate with each other.
 The communication between the ONU and the uplink port is not affected.
8.1.3.2 Network topology
Figure 8- 1 PON port isolation configuration
8.1.3.3 Configuration steps
$ Enable PON port isolation (No communications between ONUs under PON are enabled):
G1000(config)#isolate enable
G1000(config)# show isolate
Isolate state: enable
$ Disable PON port isolation (Communications between ONUs under PON are enabled):
G1000(config)# isolate disable
G1000(config)# show isolate
Isolate state: disable
8-69
9 PON Configuration Management

9.1 Basic Information About PON
9.1.1 PON Port Basic Information Query
Table 9- 1 PON port basic information query

Show PON port basic show basic-info PON view command
information
9.1.2 Examples of PON Port Basic Information
$Query PON port basic information:

G1000(config-if-gpon-2/1)#show basic-info
Pon type description : BCM-OLT-68620
Pon max distance : 20km
Pon hardware version : BCM68620
Pon firmware version : 2.6.0.2
Pon dba name : BCM DBA
Pon dba version : 1.0.0
Max llid : 64
9.2 Downstream Encryption Management

9.2.1 Downstream Encryption Configuration
As the GPON system in the downlink data transmission using broadcast form, a malicious user is
very easy to intercept other users’ information. In order to improve the confidentiality of data, it is
necessary to provide the data encryption function for the information in the downstream
direction. Encryption algorithm is triple agitation, cannot be allocated, unconfigurable. Only can
encryption time parameters and enable/disable be configured.
For encryption switch configuration, refer to 10.11 Downstream Encryption Management.
Table 9- 2 Downstream encryption configuration management
Configure encryption time encrypt time interval timeout Global command in
parameters. “config” view .
Restore time parameters to no encrypt time “config” view command.
default.
Query global encryption show encrypt time “config” view command.
parameters
9-70
9.2.2 Example of Downstream Encryption
$ Configure downstream encryption time parameters:

G1000(config)# encrypt time 100 200
G1000(config)# show encrypt time
Update key time : 100 s
No reply timeout : 200 s
$ Restore encryption time parameters to default:
G1000(config)# no encrypt time
G1000(config)# show encrypt time
Update key time : 10 s
No reply timeout : 30 s
9.3 Optical Power Detection

9.3.1 Optical Power Detection Configuration
Table 9- 3 Optical power detection configuration

Query optical power detection show optics-power “pon” view command.
information of PON port or “onu” view command.
ONU.
Query the optical power show optics-power “config” view command.
detection information of all attenuation olt X/Y X/Y：PON ID
ONU under the specified
PON port.
Query to optical power show optics-power “config” view command.
detection information of attenuation onu X/Y/Z X/Y/Z：onu ID
specify ONU
9.3.2 Example of Optical Power Detection
$ Query optical power detection information of PON port:

G1000(config-if-gpon-2/1)#show optics-power
Pon transmitted power(dBm) : 3.96
Pon operation temperature(C) : 45.36
Pon supply voltage(V) : 3.26
Pon bias current(uA) : 14268.00
$ Query the optical power detection information for the specified PON port.
G1000(config)# show optics-power attenuation olt 2/1
onu-Id Direction OLT(dBm) onu(dBm) Attenuation(dB)
---------------------------------------------------------------------
1 up Rx:-6.50 Tx:1.95 8.45
down Tx:3.96 Rx:-13.91 17.87
---------------------------------------------------------------------
2 up Rx:-6.35 Tx:1.58 7.94
down Tx:3.96 Rx:-13.88 17.84
---------------------------------------------------------------------
9-71
3 up Rx:-6.58 Tx:1.65 8.23

down Tx:3.96 Rx:-14.38 18.34
$ Query the optical power detection information of specify ONU

G1000(config)# show optics-power attenuation onu 2/1/1
onu-Id Direction OLT(dBm) onu(dBm) Attenuation(dB)
---------------------------------------------------------------------
1 up Rx:-6.51 Tx:1.95 8.46
down Tx:3.96 Rx:-13.91 17.87
9.4 Long-distance Configuration Management

9.4.1 Long-distance Configuration
The current GPON protocol stipulates that the maximum transmission distance and
differential distance of GPON shall not exceed 20km, The main task of long-distance
switch configuration is when the maximum transmission distance and differential
distance exceed 20km, If the long-distance switch is enabled, the ONU under each
PON port can be successfully registered.
Table 9- 4 long-distance configuration
to enable, enable long-distance-register （ disable| “pon” view
long-distance switch enable） command.
Default: disabled
Query long-distance switch Show long-distance-register-status “pon” view
enable results command.
9.4.2 Example of Long-distance
$ Turn on Long-distance switch of PON port:

G1000(config-if-gpon-2/1)#long-distance-register enable
$ Turn off Long-distance switch of PON port:

G1000(config-if-gpon-2/1)#long-distance-register disable
$ Query the Long-distance switch of PON port:

G1000(config-if-gpon-2/1)#show long-distance-register-status
long distance register: enable
9-72
9.5 Detection and processing of the rogue-ONU

9.5.1 Introduction of detection and processing of the rogue- ONU
Because the uplink of PON is TDMA mode, each ONU can only orderly light in different time
slots under the scheduling of OLT DBA, and ONU cannot send data in the non authorized time
slots. However, when the optical transmitter of an ONU is abnormal and cannot be turned off,
the ONU is in a long light-emitting state. The long emitting ONU will emit light in the
transmission time slot that does not belong to itself, thus interfering with the uplink light signals
of other onus, The uplink data signal of other onus may be disordered and cannot be parsed
by OLT normally. In this case, OLT will deregister such onus due to the timeout of MPCP
protocol timer.
Therefore, once one or more ONU long lights appear, it will cause other onus under the PON
port to be disconnected, which will seriously affect the operation of the system.
Therefore, it is up to OLT to detect whether there is a long emitting ONU, and carry out
corresponding processing after detection, so as to avoid affecting the business of the whole
PON port.
The design of long light detection mechanism includes detection mechanism and location
processing mechanism.
The detection mechanism configures a switch on the command line. After the switch is turned
on, the OLT can automatically poll to detect whether there is a long light. If there is a long light,
an alarm will be reported and an alarm will be polled and reported, but no exception will be
handled.
When there is a long light, the user can choose whether to handle the exception manually or
automatically through the command line configuration.
9.5.2 Configuration of the rogue-ONU
Table 9- 5 Configuration of the rogue-ONU

Turn on and off the rogue-onu detect (enable|disable) “pon” view
detection of rogue-onu command.
Default: disabled
Turn on and off the rogue-onu manage (auto | manual) “pon” view
management of rogue-onu command.
Query the long show rogue-onu config “pon” view
luminescence detection command.
switch status and treatment
switch status
Query the long show rogue-onu status Manage status
luminescence treatment The status
status and result of PON description is as
port follows：
processing：OLT is
in the process of
automatic
processing
completed ： OLT
has been
processed
completely
9-73
manual ：
rogue-onu
manage switch is
manual
Rogue-onu status
description is as
follows：
-- ： No long
luminescence
ONU under PON
1/1/0 ： OLT
detected long
luminescent ONU
under 1/1, but the
specific ONUID
was unknown
1/1/3：1/1/3 is the
long luminescent
ONU ONU
completeTime：the
last time stamp
information
processing
Enable / Disable the long rogue-onu detect (enable|disable) enable：Open the
luminescence detection slot slotid pon start-ponid long
function for batch PON port [end-ponid] luminescence
rogue-onu detect (enable|disable) detection function
slot slotid pon all of the specified
OLT PON port
disable：Close the
long
luminescence
detection function
of the specified
OLT PON port
Default：disable
slotid ： The slot
number of OLT
business card,
The range of
values varies with
OLT
start-ponid ： Start
PON port No.，the
range of values
varies with OLT
end-ponid ： End
PON port No.，the
range of values
varies with OLT ，
This parameter is
optional
all：All PON ports
9-74
of the specified
slot
Enable / Disable the batch rogue-onu manage (auto|manual) It can be set auto
PON port to handle the long slot slotid pon start-ponid after the
luminescent ONU switch [end-ponid] rogue-onu detect
rogue-onu manage (auto|manual) is configured
slot slotid pon all Enable
auto：OLT will take
the initiative to
process long
luminescent ONU
to avoid affecting
other ONU
manual ： will not
take the initiative
to process long
luminescent
ONU，users need
to handle it
themselves
Default：manual
Query the detection and show rogue-onu config slot slotid “config” view
treatment switch status of command.
long luminescent by slot
Query the treatment status show rogue-onu status slot slotid “config” view
and result of long command.
luminescent ONU by slot
9.5.3 Example of detection and treatment of l rogue-ONU
$Enable the detection of long luminescent ONU:

G1000(config-if-gpon-2/8)#rogue-onu detect enable
$ Enable the switch of dealing with long luminescence ONU of PON port:
G1000(config-if-gpon-2/8)#rogue-onu manage auto
warning:rogue-onu manage auto mode(slot/pon:2/8) will interrupt the business.
$ Query the detection and treatment switch status of long luminescent:

G1000(config-if-gpon-2/8)# show rogue-onu config
Rogue-onu detect: enable
Rogue-onu manage: manual
$ Query the treatment result of long luminescent ONU:

G1000(config-if-gpon-2/8)#show rogue-onu status
Rogue-onu Manage-status completeTime
--------------------------------------------------------------------------------------------------
2/8/03 completed 2020/2/07 14:41:50
2/8/04 completed 2020/2/07 14:33:48
$ Enable the long luminescence ONU detection function for 1 to 4 PON port of 13 slot：
G1000(config)# rogue-onu detect enable slot 13 pon 1 4
$ Enable the switch for processing long luminescent ONU for 1 to 4 PON port of 13
9-75
slot：
G1000(config)# rogue-onu manage auto slot 13 pon 1 4
warning:rogue-onu manage auto mode(slot/pon:2/1) will interrupt the business.
$ Query the long luminescent detection switch status and treatment switch status of
pon port of slot 13：
G1000(config)# show rogue-onu config slot 2
slot/port rogue-onu detect rogue-onu manage
--------------------------------------------------------------------------------------------------
2/01 enable auto
2/02 enable auto
2/03 enable auto
2/04 enable auto
2/05 disable manual
2/06 disable manual
2/07 disable manual
2/08 disable manual
$ Query the treatment status and result of long luminescent ONU by slot：
G1000(config)# show rogue-onu status slot 2
slot/port manage-status rogue-onu completeTime
--------------------------------------------------------------------------------------------------
2/01 completed --------
2/02 completed --------
2/03 completed --------
2/04 completed 2/02/01 2020/2/07 14:41:50
2/05 manual --------
2/06 manual --------
2/07 manual --------
2/08 manual --------
10 ONU Configuration Management
The ONU is located on the user side and provides the interface to the PON. The ONU can be
connected to the user through Ethernet. The main function of the ONU device is to receive the
optical signal of the OLT and convert it into an Ethernet packet and transmit it to the user. At the
same time, the Ethernet message of the user is converted into optical signal and sent to the OLT
device.
Before configuring an ONU, you need to enable the ONU to authenticate and make it an ONU.
10.1 ONU Basic Information
ONU basic information includes ONU SN, hardware version, chip version, capacity, user labels,
power information, optical power, ONU type, operating status.
10-76
10.1.1 Basic information Query on the ONU
Table 10- 1 Basic information query on the ONU

Enter onu view. interface onu onuid -
Configure ONU user onu-userlabel label
label. no onu-userlabel
Query ONU user label. show onu-userlabel
Query ONU basic show gpon basic-info GPON onu
information.
Query ONU capacity Show gpon capabilities GPON onu
Query ONU capacity-2 Show gpon capabilities-2 GPON onu
Query ONU type show onu-info
information.
Query ONU power show power-info
information
Query ONU memory show memory statistics
usage.
Query ONU optical show optical-power
power.
10.1.2 ONU Basic Information Example
$ Configure user label for legal ONU:

G1000 (config-if-ont-2/1/1)#onu-userlabel test
G1000 (config-if-ont-2/1/1)#show onu-userlabel
ONU-ID Status SN SN-Password Type Userlabel
------------------------------------------------------------------------------------------------
02/01/02 online YOTC69468ACE 123456 test
$ Query basic information on ONU:
G1000 (config-if-ont-2/1/1)#show gpon basic-info
ONU-ID :1
Vendor-ID :YOTC
Equipment ID :M2-0400H
SN :YOTC694F6096
SN-Password :1a694f6096
Loid :yotc-pon-4f6096
Password :12345678
Main-software version :7_V100R001B022
Secondary-software version :7_V100R001B022
Distance :3m
System Uptime :0 days 05:34:04
$ Query ONU capabilities :
G1000-A5(config-if-ont-2/1/1)#show gpon capabilities
OMCC version :0x80
PON number :1
ETH number :4
WiFi number :0
POTS number :0
IP host number :0
VEIP number :0
10-77
GEM port number :127

T-CONT number :0
Priority queue number :103
Traffic management option :Priority controlled
Traffic scheduler number :31
$ Query ONU capabilities-2：
G1000 (config-if-ont-2/1/1)#show gpon capabilities-2
Operator :CTC
CTC version :0
onu type :SFU
onu power supply control ability :Only Tx power control
10.2 ONU Authorization Management

10.2.1 Introduction to ONU Authorization Management
GPON downstream data channel uses the broadcast mode, the upstream data channel applying
time division multiplexing technology, through the OLT ONU control in different time slots to send
upstream data. If the ONU is not authorized, the OLT does not assign time slots to the ONUs to
send upstream data.
The GPON system is authorized by five authentication modes,namely hybrid,
loid ,loid+password,sn,sn+password.The type of authentication can be divided into automatic
and manual.
10.2.1.1 ONU Authorization Mode
GPON OLT system supports five authentication modes: hybrid,

loid ,loid+password,sn,sn+password, default to sn mode. At the same time, the authentication
mode can be flexibly configured.
● hybrid mode:In this mode, an ONU can be authenticated compatibly based on a physical
address and based on a logical ID. The OLT uses one of these two modes for different Onus.
In this mode, the OLT starts authentication of the ONU based on the SN. When it fails, the OLT
initiates the authentication of the ONU based on the logical ID.
● loid mode: Use the logical ID of the ONU as the authentication method. The logical ID
identifies only the LOID. For the register-refused ONUs, the silence mechanism should be
adopted.
● loid+password mode: Use the logical ID of the ONU as the authentication method. The
logical ID identifies the LOID + password, where password is used to check the LOID. For the
register-refused ONUs, the silence mechanism should be adopted.
● sn mode:SN authentication refers to an authentication method that OLT only matches the
sequence code of ONU. OLT detects the SN reported by ONU. If it is consistent with OLT
configuration, it will pass the authentication and ONU will go online normally.
● sn+password mode: This authentication method should match Sn and password at the
same time.
10.2.1.2 ONU Authentication type
GPON OLT system supports two authentication types: manual and automatic, the default is the
automatic type. At the same time, the type can be flexibly configured.
10-78
● Manual: When the ONU registers to the OLT, it enters the illegal ONU list and then sends the
authorization command to the ONU or the entire ONUs. When a single ONU is authorized, it
can be based on mac, loid, or loid + password respectively.
● Auto: an automatic authorization policy is that when the ONU is registered on OLT ,the
OLT automatically adds ONU to the legitimate ONU list based on the resources that
authorize ONU.
10.2.2 ONU Authorization management
Table 10- 2 ONU authorization management

Enter olt view. interface olt x/y “pon” view
command.
Configure onu-authorize mode
authentication mode (hybrid|loid|loid+password|sn|sn+pass
word)
Configure onu-authorize type (auto|manual)
authentication type
Query authentication show onu-authorize config
configuration
Authorize an bind onuid onuid loid loid password The specific type of
individual ONU password type (WORD|unknown) ONU can be
based on queried by the
loid+password. command show onu
type info. onuid：
1-64.
Authorize an bind onuid onuid loid loid type
individual ONU (WORD|unknown)
based on loid
Authorize an bind onuid <1-64> sn WORD type
individual ONU (WORD|unknown)
based on sn.
Authorize an bind onuid <1-64> sn WORD password
individual ONU PASSWORD type (WORD|unknown)
based on
sn+password.
Authorize all ONUs bind onuid all
under the PON.
Deauthorize the no bind onuid startonuid[endonuid] Starton uid: the start
specified ONU or all no bind onuid all on uid number of
ONUs. no bind onuid (online|offline|power off) the authorization
ONU.
End on uid: the end

on uid number of
the authorization
ONU.
Online: all online

onus.
Offline: all online

offline onus and pre
authorized onus
10-79
Poweroff: all onus

that are powered
off.
Query unauthorized Show gpon illegal-onu-info（ x/y|all) Query all PON ports
specified ONU or specify PON port
information. X / Y: specify PON
port
Query unauthorized Show gpon illegal-onu-info Can query the
ONU information. current PON port
Query authorized show gpon legal-onu-info
ONU information. (online|offline|poweroff|x/y|all)
Query authorized show gpon legal-onu-info
ONU information. (online|offline|poweroff|all)
Query the user show gpon legal-onu-label （x/y|all) Query all PON ports
labels of all or specify PON port
authorized PON X / Y: specify PON
ports or ONU of the
specified PON port
Query the user label show gpon legal-onu-label Query the current
of the authorized GPON port
ONU
Query the version of show gpon legal-onu-version （x/y|all) Query all PON ports
ONU of all or specify PON port
authorized PON X / Y: specify PON
ports or specified
PON ports
Query authorized show gpon legal-onu-version Query the current
ONU version GPON port
10.2.3 Examples for ONU Authorization Management

 32ONUs are connected to PON port 2/1, and its SN is different;

 The authentication type is manual
 The authentication mode is based on the sn mode
10-80
Figure 10- 1 ONU authorization management configuration
10.2.3.3 Configuration Steps
$ Configure ONU of PON 2/1, and authentication type is manual:

G1000(config-if-gpon-2/1)#onu-authorize type manual
$ Configure the authorization mode of PON 2/1 based on loid + password mode:
G1000(config-if-gpon-2/1)#onu-authorize mode loid+password
$ Authorize an ONU of PON 2/1, its loid is loid-yotc, and password is psw-yotc:
G1000(config-if-gpon-2/1)#bind onuid 1 loid loid-yotc password psw-yotc type m2-0400h
$ Authorize all ONUs of PON 2/1
G1000(config-if-gpon-2/1)#bind onuid all
10.3 ONU Restart and Deregister

10.3.1 Introduction to Restart and Deregister
Users can reboot or deregister all ONUs in ONU or PON view. Because the ONU is classified into
two types: legal ONU and illegal ONU, the operation of rebooting or deregistering the ONU is
slightly different. For illegal ONUs, restart or deregister by specifying the ONU's llid, and for a legal
ONU, specify the ONU ID to complete the operation.
The operations involved in restarting and deregistering are as follows:
10-81
Table 10- 3 Restart and deregister operations

Restart the current legal reset ONU view command,

ONU. which can only operate on
the legal ONU.
Restart the specified or reset illegal-onu（llid|all）
the entire unauthorized
ONUs under the PON.
Restart the designated or reset legal-onu（onuid|all）
the entire authorized
ONUs under the PON.
Deregister the current deregister ONU view command,
legal ONU. which can only operate on
the legal ONU.
De-register the specified deregister illegal-onu（llid|all）
or the entire unauthorized
ONUs under the PON.
De-register the deregister legal-onu（onuid|all） onuid：1-64
designated or the entire
authorized ONUs under
the PON.
10.3.2 Restart and Deregister Example

 Restart the legal ONU 2/1/1 in the GPON system.

 Unregister the legal ONU 2/1/2 in the GPON system.
 Reboot the illegal ONU whose LLID is 0x3103 in the GPON system.
 Deregister the illegal ONU whose LLID is 0x3104 in the GPON system.
10-82
Figure 10- 2 ONU restart and unregister
$Enter PON view and restart legal ONU2/1/1:

G1000(config-if-pon-3/1)#reset legal-onu 1
$Enter ONU view and deregister legal ONU2/1/2:
G1000(config-if-pon-2/1)#interface onu 2/1/2
G1000(config-if-onu-2/1/2)#deregister
$Enter PON view and restart illegal ONU whose LLID is 0x3103:
G1000(config-if-onu-2/1/2)#interface olt 2/1
G1000(config-if-pon-2/1)#reset illegal-onu 0x3103
$Enter PON view and deregister illegal ONU whose LLID is 0x3104:
G1000(config-if-pon-2/1)#deregister illegal-onu 0x3104
10.4 ONU activation / deactivation
The ONU can work normally only when it is in the active state. If the ONU needs to work normally, the
ONU must be activated first
Table 10- 4 ONU activation / deactivation
10-83
Enter ONU view interface onu Xinterface-num
Activate ONU activate
Deactivate ONU deactivate
10.5 ONU Port Configuration Management
The port configuration management of ONU is mainly to configure the ONU Ethernet port.
Port configuration includes basic configuration,port traffic control,port speed limit,loop
detection,etc.
10.5.1 Basic Configuration of the ONU port

10.5.1.1 Introduction to basic configuration of the ONU port
Before the configuration, ONU will necessarily be legalized by authentication and authorization.
The operates for ONU port basic configuration are as follows:
Table 10- 5 ONU port basic configuration operations
Enable or disable ONU port admin uniid(enable | disable) Uniid:1-26,

port the same below
Configure ONU port port mode (uniid | all)
working mode (auto|10hdx|10fdx|100hdx|100fdx|1
Ghdx|1Gfdx |10Gfdx)
Query ONU port show port-info
information.
Query the working status show port eth-state (uniid | all)
of the Ethernet port on the
ONU
Query the port link status show port link-status
of the onu
Query the configuration show running-config onu interface-num:for
information of the interface-num ONU interface,it is
specified ONU like 1/1/1.which
represents first ONU
under first PON port
of the first slot.
Batch query ONU show running-config onuid start-onuid:starting
configuration information start-onuid [end-onuid] onuid,the range is
int the PON view 1-64.
[end-onuid]:ending
onuid,the range is
10-84
1-64.(option)
Query all ONU show running-config onuid all

configuration information
in the PON view
10.5.1.2 Example of basic configuration of the ONU port
 Configure port 1 on ONU 2/1/1 in PON 2/1 to be disabled.

 Configure the working mode of port 2 on ONU 2/1/1 in PON 2/1 as 100 Mbps full duplex
 Query the port information of ONU2/1/1 in PON 2/1.
 Query the working status of Ethernet ports on ONU2/1/1 in PON 2/1.
 Query the link status of Ethernet ports on ONU2/1/1 in PON 2/1.
Figure 10- 3
$Enter ONU 2/1/1 view:

G1000(config-if-ont-2/1/1)#
10-85
$Configure port 1 on ONU2/1/1 in PON 2/1 to be disabled:

G1000(config-if-ont-2/1/1)#port admin 1 disable
$Configure the working mode of port 2 on ONU2/1/1 in PON 2/1 as 100M full
G1000(config-if-ont-2/1/1)#port mode 2 100fdx
$Query port information on ONU 2/1/1 in PON 3/1
G1000(config-if-ont-3/1/1)#show port-info
Port ID Port Type Current Side A Admin-Mode Current-Mode Link-Status
-------- --------------- -------- ------------ -------- -------- ----------
UNI-1 A-Fixed a 10-1000 BASE-T auto auto down
UNI-2 A-Fixed a 10/100BASE-TX auto auto down
UNI-3 A-Fixed a 10/100BASE-TX auto auto down
UNI-4 A-Fixed a 10/100BASE-TX auto auto up
$Query the working status of the Ethernet port on ONU 2/1/1 in PON 2/1
G1000(config-if-ont-2/1/1)#show port eth-state all
Port Id Admin Work Mode Current Work Mode Flow Control State
-------------------------------------------------------------------------
1 auto auto disable
2 auto auto disable
3 auto auto disable
4 auto auto disable
$Query port link status on ONU 2/1/1 in PON 2/1
G1000(config-if-ont-2/1/1)#show port link-status
Port ID Link Status
-------- ---------------
UNI-1 link down
UNI-2 link down
UNI-3 link down
UNI-4 up
10.5.2 Flow Control Configuration of the ONU port

10.5.2.1 Introduction to flow control of the ONU port
When the UNI of the ONU and the peer device both have the flow control function enabled, if the
ONU is congested, it sends a message to the peer device to notify the peer device to stop sending
packets temporarily. After receiving this message, the peer switch will temporarily stop sending
packets to the local switch, thus avoiding packet loss.
Before the configuration, ONU will necessarily be legalized by authentication and authorization.
The flow control configuration of an ONU port mainly includes the following operations:
10-86
Table 10- 6 The operations of ONU flow control configuration

Configure the flow control port flow-control (uniid | all)(enable Configuration

status of ONU port | disable) commands
Query the working status show port eth-state (uniid | all) Query the commands
of ONU Ethernet port.
10.5.2.2 Example of the ONU port flow control
● Turn on the flow control switch of port 1 on ONU 2/1/1
Figure 10- 4 ONU port flow control
10.5.2.2.3 Configure procedure
$Enter ONU 2/1/1 view

$Turn on the flow control switch of port 1,and query it:
10-87
G1000(config-if-ont-2/1/1)#port flow-control 1 enable

G1000(config-if-ont-2/1/1)# show port eth-state all
onu Id Port Id Admin Work Mode Current Work Mode Flow Control State
------------------------------------------------------------------------------------------------------
1 1 auto auto enable
1 2 auto auto disable
10.5.3 Rate Limit Configuration of the ONU port

10.5.3.1 Introduction to rate limit of the ONU port
The rate limit function of the ONU is to limit the rate of upstream and downstream data of ONU.
The rate of upstream and downstream data can be set respectively. Before the configuration,
ONU will necessarily be legalized by authentication and authorization.
The rate limit configuration on an ONU port mainly includes the following operations:
Table 10- 7 The operation of rate limit configuration of ONU port
Configure downstream port rate-limit downstream (uniid |

rate limit of ONU port. all) CIR PIR
Cancel downstream rate no port rate-limit downstream Restore the default
limit of ONU port. (uniid | all) value. No rate limit.
Configure upstream rate port rate-limit upstream (uniid | all)
limit of ONU port. PIR CBS EBS
Cancel upstream rate limit no port rate-limit upstream (uniid | Restore the default
of ONU port. all) value. No rate limit.
Query rate limit show port rate-limit (uniid | all)
information of ONU port.
Note:
The rate limit is in kbps. If you want to configure 50 Mbps, the rate is 50000 kbps.
10-88
10.5.3.2 Example of Rate limit on an Onu port
● Set the upstream rate limit of port 1 on ONU 2/1/1 to 50 Mbps.

● Set the downstream rate limit of port 1 on ONU 21/1 to 80 Mbps.
Figure 10- 5 Rate limit on an Onu port
$Enter ONU 2/1/1 view

$Configure upstream rate limit of port 1 on ONU 2/1/1 to 50Mbps：
G1000(config-if-ont-2/1/1)#port rate-limit upstream 1 50000 1523 1522
$Configure downstream rate limit of port 1 on ONU 2/1/1 to 80Mbps:
G1000(config-if-ont-2/1/1)#port rate-limit downstream 1 80000 80000
$Query rate limit configuration of ONU 2/1/1:
10-89
G1000(config-if-ont-2/1/1)#show port rate-limit all

onu Id Port Id Up~Cir Up~Cbs Up~Ebs Down~Cir Down~Pir
-----------------------------------------------------------------------------------------------
1 1 50000 1523 1522 80000 80000
1 2 0 0 0 0 0
1 3 0 0 0 0 0
1 4 0 0 0 0 0
10.6 FEC Configuration Management

10.6.1 Introduction to FEC Configuration
FEC (Forward Error Correction) is an important technology in the PON system. The FEC can
correct errors caused by transmission and reduce the BER (Bit Error Rate). FEC technology can
raise the optical power budget, which can increase the distance between OLT and ONU, or
increase the PON split ratio, or improve the reliability of digital channels in a simple way. The
operation of the FEC is as follows.
Table 10- 8 FEC Operations
Enter ONU view. interface onu interface-num
Configure FEC mode of ONU. gpon fec (upstream | disable)
Query FEC enable/disable show gpon fec

status of ONU.
10.6.2 Example of FEC Configuration
$Enter onu view:

$ Enable FEC mode:
G1000(config-if-ont-2/1/1)# gpon fec upstream
$Query the FEC status
G1000(config-if-ont-2/1/1)# show gpon fec
Fec mode: enable
10.7 ONU Alarm Configuration Managements
GPON equipment should support the functions of Event Notification specified by Clause57 in
IEEE802.3-2005, and should support the mechanism based on Organization Specific Event
Notification to implement various alarm and warning functions.
10-90
10.7.1 Introduction to ONU Alarm
ONU alarm specifies two alarms: Alarm switch (AlarmAdminState) and alarm threshold
(AlarmThreshold):
● AlarmAdminState: Used to enable or disable the alarm function of the ONU. By default, all
alarms / warnings are turned off.
● AlarmThreshold: Used to configure / query the threshold for generating / clearing alarms /
warnings. The default value for these two thresholds is 0xFFFFFFFF (upper limit alarm for
unsigned parameters or lower limit alarm for signed parameters), or 0xEFFFFFFF (upper limit
alarm for signed parameters), or 0x00000000 (lower limit alarm for unsigned parameters), To
ensure that there are no alarms / warnings reported by default (even if the alarm / alarm
function is on).
Note:
not all alarms have a threshold attribute. Only the Alarm ID field of the Alarm Info domain has
the alarm threshold of 4 bytes (measured value).
However, regardless of whether the ONU's AlarmAdminState attribute is on or off, the ONU
should be able to receive commands from the OLT to configure and query the AlarmThreshold
attribute and respond correctly.
10.7.2 Introduction to Alarm ID
Table 10- 10 Alarm / Warning Type Code Table

Alarm Name of the Ala Alarm Info Requir Descriptions CTC Version
object Alarm rm ement
ID s
EquipmentAl 0x00 4 bytes Requir A functional failure on
arm 01 (Failure ed. an internal interface
Code).
PowerAlarm 0x00 4 bytes Requir Power supply alarm
02 (Failure ed. type.
Code).
BatteryMissin 0x00 No. Requir Battery is provisioned
g 03 ed. but missing
BatteryFailur 0x00 No. Requir Battery is provisioned
e 04 ed. and current but
ONU
cannot recharge
BatteryVoltLo 0x00 4 bytes Requir Battery is provisioned
w 05 (measure ed. and current but its
d. voltage is too low
Recomme
nded ).
PhysicalIntru 0x00 No Requir Applies if the ONT is
sionAlarm 06 ed. supported with
detection such as
door or boxopen
10-91
ONUSelfTest 0x00 4 bytes Requir ONT has failed .

Failure 07 (Failure ed. autonomous self test
Code).
ONUTempHi 0x00 4 bytes Requir Set when ONU
ghAlarm 09 (measure ed internal temperature
d). exceeds high alarm
level.
ONUTempLo 0x00 4 bytes Requir Set when ONU
wAlarm 0A (measure ed. internal temperature
d). is below low alarm
level.
IADConnecti 0x00 4 bytes Requir Failure of Connection
onFailure 0B (Failure ed for between inner IAD
Code). SFU / and SS platform，
SBU such as Lose of SS，
with no keepalive
VoIP packets，etc
interfa
ce
PON_IF 0x00 4 bytes Requir After the ONU
Switch 0C (Failure ed for detects a link fault,
Code) ONU the ONU's PON
with port is switched, and
optical reports the event to
link the OLT to notify the
protect OLT of the handover
ion of the PON port of
types c the ONU and the
and d. reason for the
handover.
Requir
ed for
the
ONU
The ONU reports the
of
alarm to the OLT
4 bytes power
Sleep Status 0x00 when it leaves the
(Failure saving
Update 0D power saving state
Code). mecha
and enters the
nism
normal working state.
specifi
ed in
Chapt
er 18
Reserved 0x00
0D~0
x00F
F
RXPowerHig 0x01 4 bytes Requir Set when Received
PON IF
h Alarm 01 (measure ed. Power exceeds high
10-92
d). alarm level.

RXPowerLow 0x01 4 bytes Requir Set when Received
Alarm 02 (measure ed. Power is below low
d). alarm level.
TXPowerHig 0x01 4 bytes Requir Set when TX output
hAlarm 03 (measure ed. power exceeds high
d). alarm level.
TXPowerLow 0x01 4 bytes Requir Set when TX output
Alarm 04 (measure ed. power is below low
d). alarm level.
TXBiasHighA 0x01 4 bytes Requir Set when TX Bias
larm 05 (measure ed. current exceeds high
d). alarm level.
TXBiasLowAl 0x01 4 bytes Requir Set when TX Bias
arm 06 (measure ed. current is below low
d). alarm level.
VccHighAlar 0x01 4 bytes Requir Set when internal
m 07 (measure ed. supply voltage
d). exceeds high alarm
level.
VccLowAlar 0x01 4 bytes Requir Set when internal
m 08 (measure ed. supply voltage is
d). below low alarm
level.
TempHighAla 0x01 4 bytes Requir Set when internal
rm 09 (measure ed. temperature exceeds
d). high alarm level.
TempLowAlar 0x01 4 bytes Requir Set when internal
m 0a (measure ed. temperature is below
d). low alarm level.
RXPowerHig 0x01 4 bytes Requir Set when Received
hWarning 0b (measure ed. Power exceeds high
d). warning level.
RXPowerLow 0x01 4 bytes Requir Set when Received
Warning 0c (measure ed. Power is below low
d). warning level.
TXPowerHig 0x01 4 bytes Requir Set when TX output
hWarning 0d (measure ed power exceeds high
d). warning level.
TXPowerLow 0x01 4 bytes Requir Set when TX output
Warning 0e (measure ed. power is below low
d). warning level.
TXBiasHigh 0x01 4 bytes Requir Set when TX Bias
Warning 0f (measure ed. current exceeds high
d). warning level.
TXBiasLowW 0x01 4 bytes Requir Set when TX Bias
arning 10 (measure ed. current is below low
d). warning level.
10-93
VccHighWarn 0x01 4 bytes Requir Set when internal

ing 11 (measure ed. supply voltage
d). exceeds high
warning level.
VccLowWarni 0x01 4 bytes Requir Set when internal
ng 12 (measure ed. supply voltage is
d). below low warning
level.
TempHighWa 0x01 4 bytes Requir Set when internal
rning 13 (measure ed. temperature exceeds
d). high warning level.
TempLowWar 0x01 4 bytes Requir Set when internal
ning 14 (measure ed. temperature is below
d). low warning level.
If the number of
downstream packet
Downstream 8 bytes
0x01 Requir loss events exceeds
DropEventsA (measure
15 ed. the configured alarm
larm d).
threshold, an alarm is
reported.
If the number of
upstream packet loss
UpstreamDro 8 bytes
0x01 Requir events exceeds the
pEventsAlar (measure
16 ed. configured alarm
m d).
reported.
If the number of
Downstream 8 bytes downstream CRC
0x01 Requir
CRCErrorFra (measure errors exceeds the
17 ed.
mesAlarm d). threshold, an alarm is
reported.
If the number of
UpstreamCR 8 bytes upstream CRC errors
0x01 Requir
CErrorFrame (measure exceeds the
18 ed
sAlarm d). threshold, an alarm is
reported.
If the number of
downstream
Downstream 8 bytes ultrashort packets
0x01 Requir
UndersizeFra (measure exceeds the set
19 ed.
mesAlarm d). alarm threshold, the
device reports an
alarm.
If the number of
upstream ultrashort
UpstreamUn 8 bytes
0x01 Requir packets exceeds the
dersizeFram (measure
1A ed. set alarm threshold,
esAlarm d).
the device reports an
alarm.
10-94
If the number of
downstream ultralong
Downstream 8 bytes
OversizeFra (measure
1B ed. set alarm threshold,
mesAlarm d).
alarm.
If the number of
upstream ultralong
UpstreamOv 8 bytes
ersizeFrames (measure
1C ed. set alarm threshold,
Alarm d).
alarm.
When the number of
downstream
Downstream 8 bytes
0x01 Requir Fragments exceeds
FragmentsAl (measure
1D ed. the set alarm
arm d).
threshold, the device
reports an alarm.
When the number of
upstream Fragments
8 bytes
UpstreamFra 0x01 Requir exceeds the set
(measure
gmentsAlarm 1E ed. alarm threshold, the
d).
device reports an
alarm.
When the number of
downstream Jabbers
Downstream 8 bytes
0x01 Requir exceeds the set
JabbersAlar (measure
1F ed. alarm threshold, the
m d).
device reports an
alarm.
When the number of
upstream Jabbers
Downstream 8 bytes
0x01 Requir exceeds the set
JabbersAlar (measure
20 ed. alarm threshold, the
m d).
device reports an
alarm.
If the number of
downstream packet
Downstream 8 bytes
DiscardsAlar (measure
21 ed. the configured alarm
m d).
reports an alarm.
If the number of
upstream packet loss
8 bytes
UpstreamDis 0x01 Requir events exceeds the
(measure
cardsAlarm 22 ed. configured alarm
d).
reports an alarm.
Downstream 0x01 8 bytes Requir When the number of
10-95
ErrorsAlarm 23 (measure ed. downstream error

d). packets exceeds the
set alarm threshold,
an alarm is reported.
When the number of
8 bytes upstream error
UpstreamErr 0x01 Requir
(measure packets exceeds the
orsAlarm 24 ed.
d). set alarm threshold,
an alarm is reported
When the number of
downstream packet
Downstream 8 bytes
DropEvents (measure
25 ed. the set alarm
Warning d).
threshold, it is
reported.
When the number of
UpstreamDro 8 bytes upstream packet loss
0x01 Requir
pEventsWarn (measure events exceeds the
26 ed.
ing d). set alarm threshold, it
is reported.
When the number of
downstream CRC
Downstream 8 bytes
0x01 Requir error packets
CRCErrorFra (measure
27 ed. exceeds the set
mesWarning d).
alarm threshold, an
alarm is reported.
When the number of
UpstreamCR 8 bytes upstream CRC error
0x01 Requir
CErrorFrame (measure packets exceeds the
28 ed.
sWarning d). set alarm threshold,
If the number of
downstream
Downstream 8 bytes
0x01 Requir ultrashort packets
UndersizeFra (measure
29 ed exceeds the set
mesWarning d).
alarm threshold,
If the number of
upstream ultra-shot
UpstreamUn 8 bytes
0x01 Requir packets exceeds
2A ed. the set alarm
esWarning d).
threshold, an alarm
is reported.
If the number of
downstream
Downstream 8 bytes
0x01 Requir ultralong packets
2B ed. exceeds the set
mesWarning d).
alarm threshold, an
alarm is reported.
10-96
If the number of
upstream ultralong
UpstreamOv 8 bytes
0x01 Requir packets exceeds
2C ed. the set alarm
Warning d).
threshold, an alarm
is reported.
If the number of
downstream
Downstream 8 bytes
0x01 Requir Fragments
FragmentsW (measure
2D ed. exceeds the set
arning d).
alarm threshold, an
alarm is reported.
If the number of
downstream
UpstreamFra 8 bytes
0x01 Requir Fragments exceeds
gmentsWarni (measure
2E ed. the set alarm
ng d).
reported.
If the number of
Downstream 8 bytes downstream Jabbers
0x01 Requir
JabbersWarn (measure exceeds the set
2F ed.
ing d). alarm threshold, an
alarm is reported.
If the number of
8 bytes upstream Jabbers
UpstreamJab 0x01 Requir
(measure exceeds the set
bersWarning 30 ed.
d). alarm threshold, an
alarm is reported.
If the number of
Downstream 8 bytes downstream packet
0x01 Requir
DiscardsWar (measure loss exceeds the set
31 ed
ning d). alarm threshold, an
alarm is reported.
If the number of
UpstreamDis 8 bytes upstream packet loss
0x01 Requir
cardsWarnin (measure exceeds the set
32 ed.
g d). alarm threshold, an
alarm is reported.
When the number of
Downstream 8 bytes downstream error
0x01 Requir
ErrorsWarnin (measure packets exceeds the
33 ed.
g d). set alarm threshold,
When the number of
8 bytes upstream error
UpstreamErr 0x01 Requir
orsWarning 34 ed.
reserved 0x01
10-97
35～
0x01
FF
CardAlarm 0x02 4 bytes Option A functional failure on
01 (Failure al an user interface
Code) card.
SelfTestFailur 0x02 4 bytes Option Failure of Line Card
Card
e 02 (Failure al. autonomous self test
（optional
Code)
）
Reserved 0x02
03～
0x02
FF
EthPortAuto 0x03 No. Requir Failure of auto
NegFailure 01 ed for negotiation for
SFU/S specific Ethernet port
BU.
EthPortLOS 0x03 No. Requir Loss of signal for
02 ed for specific Ethernet port
SFU/S
BU.
EthPortFailur 0x03 No. Requir Failure of specific
e 03 ed for Ethernet port
SFU/S
BU.
EthPortLoop 0x03 No. Requir Loopback of Ethernet
back 04 ed for port is detected.
SFU/S
BU.
EthPortCong 0x03 No. Requir Congestion of
estion 05 ed for Ethernet port is
Port
SFU/S detected.
BU.
If the number of
Requir
0x03 ed for
DropEventsA (measure loss exceeds the set
06 SFU/H
larm d). alarm threshold, an
GU.
alarm is reported.
If the number of
Requir
0x03 ed for
pEventsAlar (measure exceeds the set
07 SFU/H
m d). alarm threshold, an
GU.
alarm is reported.
If the number of
Requir downstream CRC
Downstream 8 bytes
0x03 ed for error packets
08 SFU/H exceeds the set
mesAlarm d).
GU. alarm threshold, an
alarm is reported.
10-98
If the number of
Requir upstream CRC
UpstreamCR 8 bytes
CErrorFrame (measure
sAlarm d).
alarm is reported.
If the number of
Requir downstream
Downstream 8 bytes
0x03 ed for ultrashort packets
0A SFU/H exceeds the set
mesAlarm d).
alarm is reported.
If the number of
Requir upstream ultrashort
UpstreamUn 8 bytes
0x03 ed for packets exceeds
0B SFU/H the set alarm
esAlarm d).
GU threshold, an alarm is
reported.
If the number of
Requir downstream
Downstream 8 bytes
0x03 ed for ultralong packets
0C SFU/H exceeds the set
mesAlarm d).
alarm is reported.
If the number of
Requir upstream ultralong
UpstreamOv 8 bytes
0D SFU/H the set alarm
Alarm d).
GU. threshold, an alarm is
reported.
If the number of
Requir downstream
Downstream 8 bytes
0x03 ed for Fragments exceeds
FragmentsAl (measure
0E SFU/H the set alarm
arm d).
reported.
If the number of
Requir upstream
8 bytes
UpstreamFra 0x03 ed for Fragments exceeds
(measure
gmentsAlarm 0F SFU/H the set alarm
d).
reported.
If the number of
Requir
Downstream 8 bytes downstream
0x03 ed for
JabbersAlar (measure Jabbers exceeds the
10 SFU/H
m d). set alarm threshold,
GU.
UpstreamJab 0x03 8 bytes Requir If the number of
bersAlarm 11 (measure ed for upstream Jabbers
10-99
d). SFU/H exceeds the set

alarm is reported.
If the number of
Requir
0x03 ed for
DiscardsAlar (measure loss exceeds the set
12 SFU/H
m d). alarm threshold, an
GU.
alarm is reported.
If the number of
Requir
8 bytes upstream packet
UpstreamDis 0x03 ed for
(measure loss exceeds the set
cardsAlarm 13 SFU/H
GU.
alarm is reported.
If the number of
Requir downstream error
8 bytes
Downstream 0x03 ed for packets exceeds
(measure
ErrorsAlarm 14 SFU/H the set alarm
d).
reported.
If the number of
Requir upstream error
8 bytes
UpstreamErr 0x03 ed for packets exceeds
(measure
orsAlarm 15 SFU/H the set alarm
d).
reported.
If the number of port
Requir
8 bytes status changes
StatusChang 0x03 ed for
(measure exceeds the set
eTimesAlarm 16 SFU/H
GU.
alarm is reported.
If the number of
Requir
0x03 ed for
DropEvents (measure loss exceeds the set
17 SFU/H
Warning d). alarm threshold, an
GU.
alarm is reported.
If the number of
Requir
0x03 ed for
pEventsWarn (measure exceeds the set
18 SFU/H
ing d). alarm threshold, an
GU.
alarm is reported.
If the number of
Requir downstream CRC
Downstream 8 bytes
mesWarning d).
alarm is reported.
UpstreamCR 8 bytes Requir If the number of
0x03
CErrorFrame (measure ed for upstream CRC error
1A
sWarning d). SFU/H packets exceeds the
10-100
GU. set alarm threshold,

If the number of
Requir downstream
Downstream 8 bytes
0x03 ed for ultrashort packets
1B SFU/H exceeds the set
mesWarning d).
alarm is reported.
If the number of
Requir
UpstreamUn 8 bytes upstream ultrashort
0x03 ed for
dersizeFram (measure packets exceeds the
1C SFU/H
esWarning d). set alarm threshold,
GU.
If the number of
Requir
Downstream 8 bytes downstream ultralong
0x03 ed for
OversizeFra (measure packets exceeds the
1D SFU/H
mesWarning d). set alarm threshold,
GU.
If the number of
Requir
UpstreamOv 8 bytes upstream ultralong
0x03 ed for
ersizeFrames (measure packets exceeds the
1E SFU/H
Warning d). set alarm threshold,
GU.
If the number of
Requir downstream
Downstream 8 bytes
0x03 ed for Fragments packets
FragmentsW (measure
1F SFU/H exceeds the set
arning d).
alarm is reported.
If the number of
Requir
UpstreamFra 8 bytes upstream Fragments
0x03 ed for
gmentsWarni (measure packets exceeds the
20 SFU/H
ng d). set alarm threshold,
GU.
If the number of
Requir
Downstream 8 bytes downstream Jabbers
0x03 ed for
JabbersWarn (measure packets exceeds the
21 SFU/H
ing d). set alarm threshold,
GU.
If the number of
Requir
8 bytes upstream Jabbers
UpstreamJab 0x03 ed for
bersWarning 22 SFU/H
GU.
If the number of
Requir
0x03 ed for
DiscardsWar (measure loss exceeds the
23 SFU/H
ning d). set alarm threshold,
GU.
10-101
If the number of
Requir
UpstreamDis 8 bytes upstream packet loss
0x03 ed for
cardsWarnin (measure exceeds the set
24 SFU/H
g d). alarm threshold, an
GU.
alarm is reported.
If the number of
Requir downstream error
Downstream 8 bytes
ErrorsWarnin (measure
25 SFU/H the set alarm
g d).
reported.
If the number of
Requir upstream error
8 bytes
UpstreamErr 0x03 ed for packets exceeds
(measure
orsWarning 26 SFU/H the set alarm
d).
reported.
If the number of port
Requir
StatusChang 8 bytes status changes
0x03 ed for
eTimesWarni (measure exceeds the set
27 SFU/H
ng d). alarm threshold, an
GU.
alarm is reported.
0x03
28～
reserved
0x03
FF
POTSPortFai 0x04 4 bytes Requir
lure 01 (Failure ed for
Code). SFU/H
GU of
VoIP
interfa
ce..
reserved 0x04
02～
0x04
FF
E1PortFailur 0x05 4 bytes Requir E1
e 01 (Failure ed for
Code) SBU
E1TimingUnl 0x05 No. Requir
ock 02 ed for
SBU.
E1 LOS 0x05 No. Requir
03 ed for
SBU.
reserved 0x05
04～
0x05
10-102
FF
10.7.3 ONU Introduction to ONU alarm configuration
The operations for ONU alarm are as follows:

Table 10- 11 ONU alarm operations
Operations Commands Descri
ptions
Enter ONU view. interface onu interface-num
Enable/disable the onu alarm

switch of the (equipment-alarm|power-alarm|battery-missing|batt
specified ONU alarm. ery-failure|battery-volt-low|physical-intrusion-alarm
|onu-self-test-failure|onu-temp-high-alarm|onu-tem
p-low-alarm|iad-connection-failure|pon-if-switch)
alarm-state (enable|disable)
Configure the alarm onu alarm
threshold and the (battery-volt-low|onu-temp-high-alarm|onu-temp-lo
clear threshold for w-alarm) alarm-threshold
ONU alarms. alarm-thresholdclear-threshold clear-threshold
Enable/disable the pon-if alarm ponid
switch of the (rx-power-high-alarm|rx-power-low-alarm|
specified PON-if tx-power-high-alarm|tx-power-low-alarm|tx-bias-hig
alarm. h-alarm|tx-bias-low-alarm|vcc-high-alarm|vcc-low-a
larm|temp-high-alarm|temp-low-alarm|rx-power-hig
h-warning|rx-power-low-warning|tx-power-high-war
ning|tx-power-low-warning|tx-bias-high-warning|tx-
bias-low-warning|vcc-high-warning|vcc-low-warnin
g|temp-high-warning|temp-low-warning)
pon-if alarm ponid (pon-ds-dropevent-alarm |

pon-us-dropevent-alarm | pon-ds-crcerror-alarm |
pon-us-crcerror-alarm | pon-ds-undersize-alarm |
pon-us-undersize-alarm | pon-ds-oversize-alarm |
pon-us-oversize-alarm | pon-ds-fragments-alarm |
pon-us-fragments-alarm | pon-ds-jabbers-alarm |
pon-us-jabbers-alarm | pon-ds-discards-alarm |
pon-us-discards-alarm | pon-ds-errors-alarm |
pon-us-errors-alarm) alarm-state (enable|disable)
pon-if alarm ponid (pon-ds-dropevent-warning |

pon-us-dropevent-warning |
pon-ds-crcerror-warning | pon-us-crcerror-warning
| pon-ds-undersize-warning |
pon-us-undersize-warning |
pon-ds-oversize-warning | pon-us-oversize-warning
| pon-ds-fragments-warning |
pon-us-fragments-warning |
pon-ds-jabbers-warning | pon-us-jabbers-warning |
pon-ds-discards-warning |
10-103
pon-us-discards-warning | pon-ds-errors-warning |
pon-us-errors-warning) alarm-state (enable|disable)
Enable/disable the pon-if alarm ponid
switch of the (rx-power-high-alarm|rx-power-low-alarm|
specified ONU port tx-power-high-alarm|tx-power-low-alarm|tx-bias-hig
g|temp-high-warning|temp-low-warning|pon-ds-dro
pevent-alarm | pon-us-dropevent-alarm |
pon-ds-crcerror-alarm | pon-us-crcerror-alarm |
pon-ds-undersize-alarm | pon-us-undersize-alarm |
pon-ds-oversize-alarm | pon-us-oversize-alarm |
pon-ds-fragments-alarm | pon-us-fragments-alarm |
pon-ds-jabbers-alarm | pon-us-jabbers-alarm |
pon-ds-discards-alarm | pon-us-discards-alarm |
pon-ds-errors-alarm |
pon-us-errors-alarm|pon-ds-dropevent-alarm |
pon-us-errors-alarm|pon-ds-dropevent-warning |
pon-us-errors-warning) alarm-threshold
alarm-threshold clear-threshold clear-threshold
Configure the alarm port alarm uniid u

threshold and the (eth-port-auto-neg-failure|eth-port-los| n
clear alarm of the eth-port-failure|eth-port-loopback|eth-porT-CONTes i
specified ONU port tion|pots-port-failure|e1-port-failure|e1-timing-unloc i
alarm. k|e1-los) alarm-state (enable|disable) d
：
port alarm uniid (ds-dropevent-alarm | O
us-dropevent-alarm | ds-crcerror-alarm | N
us-crcerror-alarm | ds-undersize-alarm |
us-undersize-alarm | ds-oversize-alarm |
us-oversize-alarm | ds-fragments-alarm |
us-fragments-alarm | ds-jabbers-alarm |
us-jabbers-alarm | ds-discards-alarm |
us-discards-alarm | ds-errors-alarm |
10-104
us-errors-alarm | status-change-times-alarm)
port alarm uniid (ds-dropevent-warning |

us-dropevent-warning | ds-crcerror-warning |
us-crcerror-warning | ds-undersize-warning |
us-undersize-warning | ds-oversize-warning |
us-oversize-warning | ds-fragments-warning |
us-fragments-warning | ds-jabbers-warning |
us-jabbers-warning | ds-discards-warning |
us-discards-warning | ds-errors-warning |
us-errors-warning | status-change-times-warning)
Query the switch port alarm uniid (ds-dropevent-alarm |
status of the us-dropevent-alarm | ds-crcerror-alarm |
specified ONU alarm. us-crcerror-alarm | ds-undersize-alarm |
us-errors-alarm | status-change-times-alarm)
alarm-threshold alarm-threshold clear-threshold
clear-threshold
port alarm uniid(ds-dropevent-warning |

alarm-threshold alarm-threshold clear-threshold
clear-threshold
Query the switch show onu alarm-admin-state

status of the (equipment-alarm|powering-alarm|
specified ONU alarm. battery-missing|battery-failure|battery-volt-low|phy
sical-intrusion-alarm|onu-self-test-failure|onu-temp-
high-alarm|onu-temp-low-alarm|iad-connection-fail
ure|pon-if-switch)
Query the alarm show onu alarm-threshold
threshold and the (battery-volt-low|onu-temp-high-alarm|onu-temp-lo
clear alarm of the w-alarm)
specified ONU alarm.
Query the switch show pon-if alarm-admin-state ponid
status of the (rx-power-high-alarm|
specified pon-if rx-power-low-alarm|tx-power-high-alarm|tx-power-l
alarm. ow-alarm|tx-bias-high-alarm|tx-bias-low-alarm|vcc-
high-alarm|vcc-low-alarm|temp-high-alarm|temp-lo
w-alarm|rx-power-high-warning|rx-power-low-warni
ng|tx-power-high-warning|tx-power-low-warning|tx-
bias-high-warning|tx-bias-low-warning|vcc-high-wa
10-105
rning|vcc-low-warning|temp-high-warning|temp-low
-warning|pon-ds-dropevent-alarm |
pon-us-errors-warning)
Query the switch show pon-if alarm-threshold ponid
status of the (rx-power-high-alarm|rx-power-low-alarm|
specified ONU port tx-power-high-alarm|tx-power-low-alarm|tx-bias-hig
g|temp-high-warning|temp-low-warning|pon-ds-dro
pevent-alarm | pon-us-dropevent-alarm |
pon-ds-crcerror-alarm | pon-us-crcerror-alarm |
pon-ds-undersize-alarm | pon-us-undersize-alarm |
pon-ds-oversize-alarm | pon-us-oversize-alarm |
pon-ds-fragments-alarm | pon-us-fragments-alarm |
pon-ds-jabbers-alarm | pon-us-jabbers-alarm |
pon-ds-discards-alarm | pon-us-discards-alarm |
pon-ds-errors-alarm |
pon-us-errors-warning)
Query the switch show port alarm-admin-state uniid
status of the (eth-port-auto-neg-failure|
specified ONU port eth-port-los|eth-port-failure|eth-port-loopback|eth-p
alarm. orT-CONTestion|pots-port-failure|e1-port-failure|e1-
timing-unlock|e1-los|ds-dropevent-alarm |
10-106
us-dropevent-alarm | ds-crcerror-alarm |
us-crcerror-alarm | ds-undersize-alarm |
us-errors-alarm |
status-change-times-alarm|ds-dropevent-warning |
Query the alarm show port alarm-thresholduniid（ds-dropevent-alarm
threshold and the | us-dropevent-alarm | ds-crcerror-alarm |
clear threshold of the us-crcerror-alarm | ds-undersize-alarm |
specified ONU port us-undersize-alarm | ds-oversize-alarm |
alarm. us-oversize-alarm | ds-fragments-alarm |
us-errors-alarm |
status-change-times-alarm|ds-dropevent-warning |
us-errors-warning | status-change-times-warning）
10.7.4 ONU Alarm Configuration Example

 Turn on the swich of pon-if alarm rx-power-high-alarm of ONU2/1/1

 Configure the alarm threshold and the clear threshold of pon-if alarm rx-power-high-alarm
of ONU 2/1/1.
10-107
Figure 10- 6
$Enter ONU view:

$Turn on the switch of rx-power-high-alarm pon-if alarm:
G1000(config-if-ont-2/1/1)#pon-if alarm 1 rx-power-high-alarm alarm-state enable
$Query the switch status of rx-power-high-alarm pon-if alarm:
G1000(config-if-ont-2/1/1)#show pon-if alarm-admin-state 1 rx-power-high-alarm
onu alarm status :enable
$Configure the alarm threshold and the clear threshold of rx-power-high-alarm pon-if alarm:
G1000(config-if-ont-2/1/1)#pon-if alarm 1 rx-power-high-alarm alarm-threshold 3
clear-threshold 5
$Query the alarm threshold and the clear threshold of rx-power-high-alarm pon-if alarm:
G1000(config-if-ont-2/1/1)#show pon-if alarm-threshold 1 rx-power-high-alarm
Alarm Threshold :3.00
Clearing Alarm Threshold :5.00
10-108
11 GPON Business Management

11.1 Overview of GPON Access Service
GPON is a single fiber two-way optical access network with point to multipoint p2mp structure. Its
typical topology is tree.
The typical structure of GPON system is composed of OLT at local side, ONU at user side and
ODN connecting devices at both ends, which is a single fiber bidirectional system. In the downlink
direction (OLT to ONU), the signals sent by OLT reach each ONU through ODN. In the uplink
direction (ONU to OLT), the signal sent by ONU will only reach OLT, but not other onus. ODN is
composed of optical fiber and one or more passive optical devices such as passive optical splitter,
which provides optical channel between OLT and ONU. GPON access, as an access technology
that can provide flexible access capability in broadband and narrowband business environment,
can provide ultra-high bandwidth access, and support multiple rate modes, using a single fiber to
provide users with voice, data, video and other business services.
G1000 V100 supports GPON access service through GPUHA service board. GPUHA
provides 16 GPON ports and supports 1:64 optical ratio. Each board can provide up to 1024 ONU
accesses
11.2 GPON ONU terminal overview
GPON embedded software is developed based on G1000 software platform and code. It is
supported by GPON's command line and board management. GPON's business board name is
GPUHA.
ONU management of GPON system is managed by PLOAM (physical layer OAM) and OMCI
messages. PLOAM messages are mainly used to interact with management and maintenance
information of GPON physical layer and TC layer, such as DBA information, DBRu and other
information. OMCI message is mainly used for management and maintenance of business level,
such as hardware capability discovery, various alarm maintenance information, business
capability configuration, etc.
OMCI（onu Management and Control Interface）is a kind of configuration transmission channel
defined in GPON standard, which transmits OMCI messages by establishing a proprietary gem
port between OLT and ONU. After the ONU completes the registration process, the OMCI channel
is established. The OLT controls multiple ONU devices connected under the OLT through the
OMCI channel.
See 10.2 ONU authorization management for details of ONU authorization.
11.3 GPON DBA Configuration

11.3.1 GPON DBA introduction
In GPON system, OLT controls the uplink data flow by sending authorization signal to ONU.
PON structure needs an effective TDMA mechanism to control the upstream traffic, so that
packets from multiple onus will not collide during the upstream process. However, using collision
based mechanism needs to manage QoS in PON passive ODN, which is physically impossible to
achieve, or needs to bear the serious loss of efficiency. In view of these problems, the mechanism
of managing upstream GPON traffic has always been the primary focus in the process of GPON
traffic management standardization. This has led to the development of ITU-T G.984.3
11-109
recommendation standard, which defines a dynamic bandwidth allocation (DBA) protocol for the
management of uplink PON traffic.
OLT dynamically allocates uplink transmission timeslot to ONU according to the occupancy of
transmission buffer on ONU.
In GPON access network, the number of users on each PON link is not very large. As users
turn on / off the corresponding services, there will be a lot of burst traffic on the link. DBA algorithm
can automatically detect the changes of user traffic and adjust the corresponding bandwidth, so as
to provide users with better services.
DBA have the following characteristics:
(1) it can improve the uplink bandwidth utilization of PON port
(2) more users can be added to PON port
(3) users can enjoy higher bandwidth services, especially those services with large bandwidth
mutation
Type of uplink bandwidth:

(1) after T-CONT is activated, OLT allocates the fixed bandwidth to it, regardless of T-CONT
Whether there is upstream traffic on.
(2) guaranteed bandwidth when T-CONT has bandwidth requirements, it must be allocated to
its bandwidth. If the bandwidth requirement of T-CONT is less than the configured guaranteed
bandwidth, the extra configured bandwidth can be used by other T-CONT.
(3) non assured bandwidth when T-CONT has bandwidth requirements, it is not necessarily
allocated to its bandwidth. Only after all the fixed bandwidth and guaranteed bandwidth are
allocated, can the non guaranteed bandwidth be allocated.
(4) the best effort bandwidth is the lowest priority bandwidth type. After the allocation of fixed
bandwidth, guaranteed bandwidth and non guaranteed bandwidth, if there is still bandwidth left,
the allocation of best effort bandwidth will be carried out.
(5) maximum bandwidth no matter how large the actual uplink traffic on the T-CONT is, the
allocated bandwidth value cannot be greater than the maximum bandwidth. The maximum
bandwidth needs to be greater than or equal to the fixed bandwidth + guaranteed bandwidth.
DBA(Dynamically Bandwidth Assignment) is to monitor the congestion of PON. OLT adjusts
the dynamic bandwidth according to congestion, current bandwidth utilization and configuration.
Static bandwidth allocation method: static bandwidth allocation, also known as fixed
bandwidth allocation, means that the bandwidth occupied by each ONU is fixed, and OLT will
periodically allocate fixed length authorization for each ONU according to the SLA of each ONU
(including bandwidth and delay indicators).
Generally speaking, OLT adopts polling mechanism. In each polling cycle, the fixed
bandwidth of each ONU may be different, but the fixed bandwidth of the same ONU in different
cycles is the same. The authorization size is only related to the SLA of ONU, and has nothing to do
with the upstream traffic of ONU. Even if there is no traffic in the upstream of ONU, this part of
bandwidth will be allocated to ONU.
Five types of DBA:
(1) type1 is a fixed bandwidth DBA profile, which is reserved for specific ONU or ONU specific
services. Even if ONU has no upstream traffic flow, this bandwidth cannot be used by other onus.
Fixed bandwidth is mainly used for services that are very sensitive to service quality, such as TDM,
VoIP, etc.
(2) type2 is the DBA profile to ensure bandwidth. Guaranteed bandwidth is the bandwidth that
can be obtained when the ONU needs to use bandwidth. When the actual traffic of ONU does not
reach the guaranteed bandwidth, the DBA mechanism of the device should be able to allocate the
remaining bandwidth to other ONU services.
(3) type3 is to ensure the combination type of bandwidth + maximum bandwidth. While
ensuring that users have a certain bandwidth, it also allows users to have a certain bandwidth
preemption, but the total is not more than the maximum bandwidth configured by users. This
bandwidth type is mainly applied to VoIP and IPTV services.
(4) type4 is the DBA profile with the maximum bandwidth. The maximum bandwidth is the
upper limit of the bandwidth that can be obtained when the ONU uses the bandwidth, which can
11-110
meet the bandwidth resources used by the ONU to the greatest extent. The maximum bandwidth
type is commonly used in general Internet services.
(5) type5 is a combination type of fixed bandwidth + guaranteed bandwidth + maximum
bandwidth. It not only reserves fixed bandwidth resources that other users cannot seize, but also
ensures the guaranteed bandwidth that can be obtained when bandwidth is needed. At the same
time, it allows users to seize a certain bandwidth, but the total bandwidth will not exceed the
maximum bandwidth configured by users.
The relationship between uplink bandwidth type and T-CONT type.
Figure 11- 1
If T-CONT is not activated (for example, the ONU where the T-CONT is located is in shutdown
state), the configured bandwidth can be used by other T-CONT.
The DBA profile describes the flow parameters of T-CONT. By binding a T-CONT with the
specified DBA profile, the traffic control of the T-CONT is performed. Default is the default DBA
profile of the system, and gives the typical traffic parameter values. You can query and modify the
default DBA profile, but you cannot add or delete it. You can create up to 16 DBA templates
(including the default profile)
Bind the DBA profile for single or multiple T-CONTs. After the DBA profile is bound
successfully, the system will control the flow of T-CONT according to the flow parameters
described in the profile.
Table 11- 1 DBA profile operation
Enter config view configure terminal -
gpon dba NAME type 1 fix/max
Name: DBA profile
<128-1000000>
name, 1-63 characters,
gpon dba NAME type 2 assure/max
Chinese is not supported
<128-1000000>
Support up to 16 DBA
gpon dba NAME type 3 assure
templates (including
Create DBA profile <128-1000000> max <256-1000000>
default profile)
gpon dba NAME type 4 max
< 128-1000000 > / <
<128-1000000>
256-1000000 >:
gpon dba NAME type 5 fix
allocated bandwidth, in
<128-1000000> assure <128-1000000>
Kbps;
max <256-1000000>
Show GPON DBA
displays all DBA profile
information
show gpon dba NAME
Query the created show gpon dba Display the DBA profile
DBA profile show gpon dba NAME information for the profile
name
Name: DBA profile
name, 1-63 characters,
Chinese is not supported
11-111
Word: DBA profile name,

1-63 characters, Chinese
is not supported
Delete the created no gpon dba WORD
All: all DBA templates
DnaB profile no gpon dba all
Note: the DBA profile that
has been bound cannot
be deleted
The following commands operate in the ONU view:
int onu X/Y/Z Interface number, [x/y/z]
Enter ONU view -
x slot, y port, z onu
T-CONT binding DBA
T-CONT <1-8> dba WORD| default
profile
< 1-8 >: T-CONT index,
Delete T-CONT no T-CONT (<1-8>|all) value range is < 1-8 >
All: all T-CONTs
If T-CONT is not bound
to GEMport, show
Querying the binding
T-CONT info will not
relationship between
show T-CONT info display the information of
DBA profile and
the T-CONT. At this time,
T-CONT
you can view it through
show running
11.3.2 GPON DBA Configuration example
$ Create a type 4 DBA profile named test4

G1000(config)# gpon dba test4 type 4 max 10240
$ Delete DBA template123
G1000(config)# no gpon dba 123
$ Delete all DBA templates
G1000(config)# no gpon dba all
$ Create T-CONT and bind DBA profile test
G1000 (config-if-ont-2/5/1)# T-CONT 1 dba test
$ Delete T-CONT
G1000 (config-if-ont-2/5/1)# no T-CONT 1
11.4 GPON GEMPORT Configuration

11.4.1 GEM Port Mapping introduction
GPON system parses Ethernet frame and directly maps data to GEM payload for
transmission.
GPON's GEM is similar to ATM's in virtual connection. A virtual connection must be
established between OLT and ONU to forward data. Each GEMport is identified by a unique port
ID and assigned globally by OLT. When data downlink is sent to ONU for unpacking, the ONU will
receive the GEM frame when it belongs to the ONU, and the GEM port ID we mentioned is used to
identify the GEM frame. Therefore, the GEM port ID used by each ONU under each GPON port
must be unique. If it is not unique, the ONU cannot receive its own GEM frame.
11-112
Use this task to configure the mapping relationship between ONU service and GEM port, so
that ONU service can be hosted to the specified GEM port up.
Table 11- 2GEM port mapping operation
interface onu
Enter ONU view X/Y/Z Interface number, [x/y/z] x -
slot, y port, z onu
When creating a GEM
port, you need to set the
matching type of the
GEM port first:
Port: map GEMport
based on ONU port
GEMport <1-16> type
VLAN: mapping
Add GEM Port (port|vlan|cos|vlan+cos)
GEMport based on
VLAN ID
Cos: mapping GEMport
based on cos priority
VLAN + cos: mapping
GEMport based on
vlanid and COS priority
WORD:Port ID, support
Set the ONU port
gemport mapping type to input multiple port
gem port mapping
(port|vlan|cos|vlan+cos) (WORD|all) numbers, such as 1,3-4
type
All: all ports
Set to map gemport gemport mapping port <1-16>
based on port (WROD|all)
gemport mapping cos <1-16> WORD
Set to map gemport
(WROD|all)
based on cos priority
gemport mapping vlan <1-16> WORD
Set to map gemport
(WROD|all)
based on vlan ID
Set to map gemport
gemport mapping vlan+cos <1-16>
based on vlanID
WORD WORD (WROD|all)
and cos
There is no separate
Query ONU command to view the
show running-config
information created GEM port
information
Delete created gem
no gemport <1-16>
ports
Delete the mapping
between gem port no gemport mapping <1-16>
and port
Configuration
gpon flow commit
submission
11.4.2 Introduction to binding of T-CONT and GEM port
GEM frame is the smallest service carrying unit in GPON technology and the most basic data
structure. T-CONT (transmission container) is the carrier of GPON uplink service, and all GEM
11-113
ports should be mapped to T-CONT.
(1)T-CONT （Transmission Containers）

A T-CONT corresponds to a kind of bandwidth traffic flow, which has its own QoS
characteristics. The QoS characteristics are mainly reflected in the bandwidth assurance. T-CONT
is mainly divided from the perspective of bandwidth assurance rather than from the types of
services (such as CBR, UBR, etc., which includes the consideration of bandwidth, delay, jitter,
etc.).
Each T-CONT is identified with an Alloc-ID. T-CONT is the aggregation of business traffic. Through
Alloc-ID identification, a T-CONT can only carry one data type.
The uplink frame is multiple GEM frames encapsulated in the corresponding t-con, then the t-con
is packaged and the GTC (GPON transmission conversion) frame header information is uploaded
to the OLT. That is, a T-CONT contains information of multiple GEM frames. GTC frame composed
of T-CONT is uploaded to OLT. OLT takes out the encapsulated GEM frame for service
identification and matching.The uplink data seems to be in the GEM port, which has little to do with
T-CONT. Why export T-CONT? And it's just going up.
Here T-CONT is used for uplink data scheduling, which can be understood as QoS. In GPON, we
call it DBA (dynamic bandwidth allocation). T-CONT is the foundation of DBA and the most basic
control unit of uplink bandwidth in GPON system. Through the bandwidth application of ONU to
T-CONT and the authorization of OLT to T-CONT, the dynamic bandwidth allocation of the
upstream traffic flow of the whole GPON system is realized.
T-CONT, each T-CONT is uniquely identified by Alloc-ID. Alloc-ID is allocated by each GPON port
of OLT, that is, there is no T-CONT with the same Alloc-ID in ONU of the same PON port of OLT.
For the convenience of business planning and implementation. We assign ONU ID and T-CONT
ID to each ONU and each uplink service. Then we use Alloc-ID to uniquely identify this uplink
service flow under the PON port and allocate bandwidth in the uplink direction.
 A GEM port can carry one service or multiple services. After the GEM port carries the services,
it needs to map to the t – Cont unit to schedule the uplink services. Each ONU supports
multiple T-cons, and different types of T-cons can be selected according to different
business types.
 A T-CONT can host multiple GEM ports or one GEM port, depending on the user's specific
planning.
 A T-CONT can correspond to only one ONU, or multiple T-CONTs can correspond to one
ONU.
 A GEM port can correspond to only one T-CONT, or multiple GEM ports can correspond to
one T-CONT.
(2)Business mapping relationship:
Up direction:
According to the configured traffic flow and GEM port mapping rules, the Ethernet frame is sent to
the corresponding GEM port, which encapsulates the Ethernet frame into the GEM frame, and
puts the GEM frame into the corresponding T-CONT queue according to the GEM port and
T-CONT queue mapping rules. T-CONT queue sends GEM frame to OLT in its upload slot
OLT extracts the Ethernet frame after receiving the GEM frame, and sends the Ethernet frame
from the specified uplink port according to the configured traffic flow mapping rules.
Down direction:
The data is sent to ONU through broadcast. ONU filters the data according to the GEM port ID of
the frame head of the GEM. Only the GEM port belonging to the ONU is reserved and unpacked,
and then the Ethernet frame is sent to the user equipment from the business interface of ONU
11-114
Figure 11- 2
T-CONT identifies various types of business flows from the perspective of bandwidth, while port ID
identifies the business virtual port (virtual connection) of ONU, that is, the channel that the specific
business flow carries. This channel is virtual, and PortId can play the role of address, just like
VP.(3)GPON address
OLT does not need an address, but it needs to know the Alloc-ID of the user stream. There are
three IDS in each ONU, which can play the role of address: ONU ID, Alloc-ID and port ID.
onu ID：One per ONU;
Alloc-ID：There can be multiple T-CONTs on each ONU. Each T-CONT corresponds to an Alloc-ID
automatically generated by the system.（Alloc-ID＝256×T-CONT ID+onu ID）, Each Alloc-ID of
each ONU is different.
PORT ID：Each T-CONT on each ONU can have multiple port IDs. Each port ID can only belong to
one T-CONT, and the port ID under the same PON port cannot be duplicate.
GPON Multiplexing structure
Figure 11- 3
11-115
Table 11- 3 Binding operation between T-CONT and GEM port

interface onu
Enter ONU view X/Y/Z Interface number, [x/y/z] x -
slot, y port, z onu
Configure T-CONT <1-8>：T-CONT ID
binding gem port
T-CONT <1-8> gemport <1-16>
<1-16>：gemport ID
Remove the binding
between T-CONT and no T-CONT <1-8> gemport (<1-16>|all)
gem port
11.4.3 GPON GEMPORT Configuration example
Taking cos mapping as an example, the configuration steps are as follows:

(1)Create gemport 16 with type set to cos
G1000 (config-if-ont-2/1/1)#gemport 16 type cos
(2)Set the mapping type of ONU port 3 to Cos
G1000 (config-if-ont-2/1/1)#gemport mapping type cos 3
(3)Map gemport 16 to port 3 with a cos value of 5
G1000 (config-if-ont-2/1/1)#gemport mapping cos 16 5 3
(4)Configuration submission
G1000 (config-if-ont-2/1/1)# gpon flow commit
Remarks:
(1) A gemport can only be set to one type, and an ONU port can only be set to one type
(2) When gemport and port are mapped, the port type and gemport type must be set to be
the same. Otherwise, they cannot be configured. The prompt "the gemport and ONU port
gemport mapping type mismatch!"
(3) When matching the cos type, the last configured port shall prevail, and the cos value of
each configuration will be mapped to the last configured port
11.5 ONU Service-profile

11.5.1 Introduction to ONU Service-profile
ONU service profile is identified by profile name, It also supports the profile configuration description
information, as well as the profile creation, modification, deletion, application, uninstallation and viewing
functions.
Through the business profile, the ONU can be pre configured, and the association with the ONU
type can be canceled, so that it can be used more flexibly, realize the pre configuration function of ONU,
and achieve the effect of ONU ready to install and use.
onu service profile is mainly used to configure the related information of ONU MAC aging time, port
flow control, port VLAN, etc.
Table 11- 4ONU service profile
11-116
Enter config view configure terminal
Up to 128 can be
configured, and
Create ONU service profile onu service-profile gpon NAME
enter the profile
view after creation
Delete ONU service profile no onu service-profile gpon (NAME| all)
Query ONU service profile

show onu service-profile gpon (NAME| all)
Seconds: the aging

time of the dynamic
table item in the
MAC address table.
The value range is
< 1-3600 > and the
unit is seconds. By
default, the aging
Configure the MAC mac-address aging
time is 300s.
address aging time of ONU (seconds|default|no-aging)
Default: the
recovery aging time
is the default value,
i.e. 300s.
No aging: dynamic
table entries in
MAC address table
are not aged.
Activate ONU port,
activate N ports,
which means that
you can manage
port eth-number portid the first N ports.
Activate ONU port
When you issue the
profile, you will
issue the
configuration of the
first N ports.
Enable the adaptation of
the number of ONU ports, port eth-number adaptive
i.e. the actual number of
ONU ports shall prevail
PortId: the port
number of ONU in
the range of 1-32.
Enable / disable the flow port flow-control (portid |all) All: onu all ports.
control function of ONU (enable|disable) Enable: enable flow
port control.
Disable: disable
flow control. The
default is disable.
Inbound: port entry.
Configure the traffic profile port traffic-profile (inbound|outbound)
Outbound: Port
of the application ONU port portid NAME
exit.
11-117
PortId: the port

number of ONU in
the range of 1-32.
Name: traffic profile
name of traffic
profile.
PortId: the port
number of ONU in
the range of 1-32.
Transparent: ONU
port is in
port vlan mode portid transparent mode
Configure ONU port VLAN
(transparent|tag|translation|trunk|aggreg Tag: ONU port is in
mode
ation) tag mode
Translation:
conversion mode.
Trunk: trunk mode.
Aggregation:
aggregation mode.
PortId: the port
number of ONU,
ranging from 1-32
Pri: priority of the
Configure the tag VLAN
port vlan default-vlan portid vlanid pri tag VLAN of ONU
and priority of ONU port
port, value range <
0-7 >
Vlanid: range
1-4094
PortId: the port
number of ONU,
ranging from 1-32
Configure the translation port vlan translation portid list oldnid
Oldnid: range
VLAN of ONU port newnid
1-4094
Newnid: range
1-4094
PortId: the port
number of ONU,
ranging from 1-32
Configure trunk VLAN of Vlanlist: trunk VLAN
port vlan trunk portid VLANLIST
ONU port list, such as
101102103 or 101,
ranging from
1-4094
PortId: the port
number of ONU in
the range of 1-32.
Vlanlist: an
aggregate VLAN
Configure VLAN
port vlan aggregation portid VLANLIST list, such as
aggregation mode of ONU
vlan id 101102103 or 101,
port
with a range of
1-4094.
VLAN ID: VLAN
after aggregation,
range 1-4094
11-118
ONU service profile cls、end、exit、help、list、interface olt X/Y、

general operation interface onu X/Y/Z
View all current show running-config
11.5.2 ONU service profile configuration example
$Create GPON ONU service profile”test”：

G1000(config)# onu service-profile gpon test
$ Configure the VLAN mode of ONU port 1 as tag:
G1000(config-gpon-srvprofile-1)#port vlan mode 1 tag
$ Configure the tag VLAN and priority of ONU port 1:
G1000(config-gpon-srvprofile-1)#port vlan default-vlan 1 100 1
$ Apply the service profile”test” to the current ONU:
G1000 (config-if-ont-2/16/1)#onu service -profile gpon test
$ Delete GPON ONU service profile”test”:
G1000(config)# no onu service-profile gpon test
$ Delete the current ONU application service profile”test”:
G1000 (config-if-ont-2/16/1)#no onu service-profile gpon
11.6 ONU Line profile

11.6.1 Introduction to ONU Line profile
GPON ONU line profile is mainly used to configure DBA, T-CONT and GEM port related information.
Table 11- 5ONU Line profile
Enter config view -
Create ONU circuit profile onu line-profile NAME Up to 128 can be configured
Delete ONU line
no onu line-profile (NAME| all)
profile
View ONU line profile
configuration
show onu line-profile (NAME| all)
Enter the ONU line profile
view
-
Add gemport gemport <1-16>
Configure the gemport gemport mapping-type
mapping type (vlan|cos|vlan+cos|port)
<1-16>: gemport ID
cos: cos priority, range 0 ~ 7,
Gemport based on cos gemport <1-16> mapping <1-8> cos
support for inputting multiple
mapping <0-7> cos values, Range
configuration is not supported
11-119
<1-16>：gemport ID
PortId: the port number of
ONU, which supports the
input of multiple ports and the
Gemport based on port gemport <1-16> mapping port <portid | input port range, such as
mapping all> 1,3-4.
All: all ports
Note: parameters are
required under any mapping
type.
<1-16>: gemport ID
vlanlist: vlanID list, supports
Mapping gemport based gemport <1-16> mapping <1-8> vlan
multiple vlanIDs. Range
on VLAN <1-4094> configuration is not
supported.
<1-16>: gemport ID
vlanlist: vlanID list, supports
multiple vlanIDs . Range
Mapping gemport based gemport <1-16> mapping <1-8> vlan configuration is not supported
on VLAN + cos <1-4094> cos <0-7> cos: cos priority, range 0 ~ 7,
support for inputting multiple
cos values, Range
configuration is not supported
name: profile name, 1-63
Create T-CONT and bind T-CONT <1-8> dba NAME| default characters, does not support
DBA profile Chinese
default: default profile
1. One T-CONT can bind
T-CONT binding T-CONT <1-8> gemport <1-16> multiple gemports;
gemport 2. A gemport can only be
bound to 1 T-CONT;
Up FEC enable upstream-fec-mode (enable|disable)
Delete gemport no gemport <1-16>
Delete mapping for
gemport
no gemport <1-16> mapping <1-8>
Delete all mapping of
gemport
no gemport <1-16> mapping all
Delete ONU port mapped
by gemport
no gemport <1-16> mapping port
Delete T-CONT no T-CONT <1-8>
Querying DBA templates show gpon dba
Querying DBA templates
by profile name
show gpon dba NAME
Query line profile show onu line-profile
Query line profile by
show onu line-profile NAME
name
Display all line profile
show onu line-profile all
information
Display configuration
information of line show running-config
profile
11-120
1、 1. The applied circuit

profile must have
T-CONT and
gemport, and
gemport is bound to
T-CONT, otherwise it
cannot be applied
Apply line profile on successfully
onu line-profile NAME
ONU 2、 2. After applying the
line profile, the
previous
configuration
information related to
gemport and
T-CONT will be
cleared on ONU
Query line profile show onu line-profile
information show onu line-profile NAME
configured on ONU show onu line-profile all
Application of deleting
no onu line-profile
line profile on ONU
11.6.2 ONU line profile configuration example
(1) Basic configuration steps:

$ Create the line profile “123” and enter the line profile view:
G1000(config)#onu line-profile 123
$ Set the mapping type of gemport as VLAN. There are four mapping types, cos, port,
VLAN, VLAN + cos. Each line profile can only set one mapping type:
G1000(config-line-profile-1)#gemport mapping-type vlan
$Add gemport 1
G1000(config-line-profile-1)#gemport 1
$ Set the mapping values of gemport. Each gemport can be configured with up to 8
mapping values
G1000(config-line-profile-1)#gemport 1 mapping 1 vlan 200
$sets the mapping between gemport and port, such as gemport 1 and port 1 (required
under any mapping type)
G1000(config-line-profile-1)# gemport 1 mapping port 1
$ To create T-CONT 1, you must bind the DBA profile when creating T-CONT, so you need
to create the DBA profile first or use the default DBA profile, default.
G1000(config-line-profile-1)#T-CONT 1 dba 123
$ T-CONT binding to gemport
G1000(config-line-profile-1)#T-CONT 1 gemport 2
$ Set the uplink FEC mode. The default value is disable:
G1000(config-line-profile-1)#upstream-fec-mode enable
$ The line profile is applied to ONU:

G1000(config-if-ont-2/16/1)# onu line-profile 123
11-121
-- ----
(2) Possible exceptions during configuration:
$ When deleting ONU line business profile
1） If the profile does not exist, you will be prompted:The profile does not exist..
2） If the profile has been applied to ONU, prompt:Profile is bound ,can not be deleted
$ When applying the specified circuit profile to ONU
1） If the line profile does not exist, prompt:The data doesn't exist.
2） If the profile exists, but there is no configuration information related to T-CONT, it will
prompt:onu line-profile T-CONT does not exist.
3） If the profile exists, but there is no configuration information related to gemport, you
will be prompted:onu line-profile gemport does not exist!
4）If there is a line profile applied on ONU, it will prompt:onu has bound profile, please
unbind first!
11.7 ONU traffic profile

11.7.1 Introduction to ONU Traffic profile
This section introduces the configuration of ONU traffic profile. The ONU traffic profile defines
the traffic parameters. When configuring the business profile, you need to use the traffic profile to
speed limit the port. Please refer to 10.7.3 ONU port speed limit configuration
Table 11- 6ONU Traffic profile
Enter config view -
Up to 128 can be
configured
CIR: committed
information rate.
traffic-profile NAME cir <0-10240000>
CBS: committed burst
Create ONU traffic profile cbs <0-1024000000> pir <64-10240000>
size.
pbs <2000-1024000000> priority <0-7>
PIR: peak information
rate.
PBS: peak burst size.
Priority: priority
Delete ONU traffic
no traffic-profile (NAME| all)
profile
show traffic-profile View all traffic templates
Query ONU traffic profile
show traffic-profile NAME and by profile name
In the service profile
view, set the inbound and
outbound traffic
Service profile binding port traffic-profile (inbound|outbound)
templates respectively
traffic profile <1-32> NAME
< 1-32 >: port number
Name: traffic profile
name
11-122
11.7.2 ONU traffic profile configuration example
(1)Basic configuration steps:

$ To create a traffic profile:
G1000(config)# traffic-profile 123 cir 1024 cbs 2048 pir 204800 pbs 10000 priority 3
$ In the business profile view, bind the traffic profile to the upstream and downstream
respectively
G1000(config-gpon-srvprofile-1)#port traffic-profile inbound 1 123
$Query traffic profile
G1000(config)# show traffic-profile
ID Cir(kbps) Cbs(byte) Pir(kbps) Pbs(byte) Priority Name
----------------------------------------------------------------------------------------------------------------------
1 1024 2048 204800 10000 3 123
----------------------------------------------------------------------------------------------------------------------
(2)Possible exceptions during configuration:

$ When deleting ONU traffic profile
1）If the profile does not exist, you will be prompted: the profile does not exist
2）If the profile has been applied to ONU, it will prompt: profile is bound, can not be
deleted
12 RSTP Configuration Management

12.1 Introduction to RSTP Protocol
The concept and principle of RSTP on the OLT are the same as those on the Ethernet switch.
Therefore, the RSTP is described by taking the Ethernet switch as an example.
STP is the abbreviation of Spanning Tree Protocol. This protocol can be applied to the loop
network. It can block certain redundant paths by some algorithms, and prune the loop network into
a non-loop tree network, which avoids proliferation and infinite loop in the loop network.
The basic principle of STP is to determine the topology of a network by passing a special protocol
packet between switches, which is called a configuration message by the IEEE 802.1D
protocol. The configuration message contains enough information to ensure that the switch
performs spanning tree calculation.
The configuration message includes the following:
(1)The ID of the tree root, made up of the combination of the root priority and the MAC address.
(2) The shortest path overhead to the root;
(3)The specified switch ID, made up of the combination of the priority and MAC address of the
specified switch.
(4) The ID of the specified port, made up of the priority and port number of the specified port;
(5) Configure the lifetime of the message;
(6) Configure the maximum lifetime of messages;
(7) Configure the interval HelloTime for message transmission;
(8) Delay of port state transition ForwardDelay;
12-123
The following is the description of the specified port and switch.
Figure 12- 1The specified switch and port
For a switch, the designated switch is the switch directly connected to this switch and is responsible
for forwarding the packet this switch. The specified port is the port through which the specified switch
forwards data to this switch.For a LAN, the specified switch is one responsible for forwarding packets
to this segment of the network. The specified port is the data forwarding port of the specified switch.
As shown in the figure, Lanswitch A forwards data to Lanswitch B through Ethernet 0/1. In Lanswitch
B configuration, the designated switch is Lanswitch A, and the designated port is the port Ethernet0 /
1 of Lanswitch A. There are two switches connected to the LAN LAN: Lanswitch B and Lanswitch
C. Lanswitch B is responsible for forwarding packets to the LAN, the designated LAN switch is
Lanswitch B, designated port is Lanswitch B Ethernet 0/4.
Figure 12- 2Ethernet switch networking
For ease of description, only the first four entries of the configuration message are given in the
example: the root ID (expressed as the priority of the Ethernet switch), the root path cost, the
designated switch ID (expressed as the priority of the Ethernet switch), and the specific port ID
12-124
(represented by the port number).As shown in the above figure, Lanswitch A has the priority 0,
Lanswitch B has priority 1, Lanswitch C has priority 2. The path cost of each link is shown in the
figure, 5, 10 and 4 respectively.
(1)Initial state: Each port of each switch initially generates its own root configuration message with
the root path cost as 0. The specified switch ID is its own switch ID and the designated port is the
current port.
Lanswitch A：
Port Ethernet 0/1 configuration message：{0，0，0，e0/1}
Lanswitch B：
Lanswitch C：
(2) The optimal configuration message is selected.
Each switch sends out its own configuration message. When a port receives a configuration
message with a lower priority than that of configuration message of the port, the port discards
the received configuration message and does not process the configuration message of the
port.When a port receives a configuration message with a higher priority than that of
configuration message of the port, it updates the configuration message of the port with the
received configuration message. That is, it replaces the configuration message of the port
with the contents of the received configuration message. And then the port compares with the
configuration message of the other ports on the device to select the optimal configuration
message.
The comparison principle is that a configuration message with a smaller root ID has a higher
priority. If the root IDs are the same, the root path cost is compared. If the root path cost in the
configuration message plus the path cost of the current port is set to S, the smaller
configuration message in S has a higher priority. If the root path cost is the same, the
specified switch ID, the specified port ID and the port ID receiving the configuration message
are compared in turn. For ease of description, this example assumes that only the root IDsare
compared to select the optimal configuration message.
(3)Determine the root port and block the redundant link accordingly, and update the configuration
message of the specified port.
The port receiving the optimal configuration message is set as the root port, the port configuration
message is not changed; In other ports, if the configuration message of a port is updated in the
process (2), the port will be blocked and the port configuration message will not be changed. The
port will not forward data again, but will only receive the configuration message. If the configuration
message of a port is not updated in process (2), the configuration message for the specified port is
changed as follows: The root ID is replaced with the root ID of the configuration message of the
root port; the root path cost is replaced by the root path cost of the configuration message of the
root port plus the path cost corresponding to the root port; the specified switch ID is replaced
with its own switch ID, and the designated port ID is replaced with its own port ID.
12-125
The comparison process of each switch is as follows:

Lanswitch A：
Port Ethernet 0/1 receives the configuration message of Lanswitch B and finds that the priority of
configuration message of the port (Ethernet 0/1) is higher than the priority of the received
configuration message. Therefore, the received configuration message is discarded. Port Ethernet
0/2 is the similar.Lanswitch A discovers that, in the configuration message of each port, the root
and the specified switch are itself.Therefore, since it thinks itself as the tree root, it doesn’t make
any modification on the configuration message of each port and sends configuration messages out
periodically.
The configuration messages of the two ports are as follows:

Port Ethernet 0/1 configuration message {0，0，0，e0/1}.
Port Ethernet 0/2 configuration message {0，0，0，e0/2}.
Lanswitch B：
Port Ethernet 0/7 receives configuration message from Lanswitch A and, after the comparison,
finds that the priority of the received configuration message is higher than that of its own, then it
updates configuration message of its own port. Port Ethernet 0/4 receives configuration message
from Lanswitch C and discovers that the priority of its own port configuration message is higher
than that of the received configuration message, then it discards the received one
The configuration messages of the two ports are as follows:
Port Ethernet 0/7configuration message {0，0，0，e0/1} ;
Port Ethernet 0/4configuration message {1，0，1，e0/4}.
Lanswitch B compares configuration message from all ports and selects the configuration
message from Port Ethernet 0/7 as optimal configuration message. Then Port Ethernet 0/7is
determined as root port and the configuration messages of all ports of the switch are updated as
follows:
The root port Ethernet 0/7 configuration message is unchanged: {0, 0, 0, e0 / 1}. Port Ethernet 0/4
will update the root ID to root ID0 in the optimal configuration message, update the root path cost
to 5, set the specified switch ID as the switch ID, set the specified port ID as the local port ID, and
configure the configuration message Becomes: {0, 5, 1, e0 / 4}.
Afterwards, the specified ports of Lanswitch B send out its configuration message periodically.
Lanswitch C：
Port Ethernet 0/1 receives the configuration message {1, 0, 1, e0 / 4} from Port Ethernet 0/4 of
Lanswitch B to trigger the update process. The updated configuration message is as follows:
{1,0, 1, e0 / 4}.
Port Ethernet 0/5 receives the configuration message {0，0，0，e0/2} from Lanswitch A to trigger the
update process. The updated configuration message is as follws: {0，0，0，e0/2}
After comparison, the configuration message of Port Ethernet 0/5 is selected as optimal one. Then
Port Ethernet 0/5 is determined as root port and its configuration message is unchanged. Port
Ethernet0/1 will be blocked with its configuration message unchanged. Meanwhile, it will not
receive the data forwarded from Lanswitch B (excluding STP protocol packets) until the new case
triggers the spanning tree calculation. For example, the link from Lanswitch B to Lanswitch C goes
down, or the port receives a better configuration message.
12-126
Afterwards, Port Ethernet 0/1 will receive the updated configuration message {0，5，1，e0/4} from
Lanswitch B. Since the priority of the received configuration message is higher than that of the
original one, the updated configuration message is triggered to be further updated to be {0，5，1，
e0/4}.
Meanwhile, Port Ethernet 0/5 receives configuration message from Lanswitch A, which will not
trigger update, and the configuration message is still {0，0，0，e0/2}. After comparison, the
configuration message of Port Ethernet 0/1 is selected as the optimal one. Then Port Ethernet 0/1
is determined as root port and its configuration message is unchanged, while Ethernet0/5 will be
blocked with its configuration message unchanged. Meanwhile, it will not receive the data
forwarded from Lanswitch A until the new case triggers the spanning tree calculation, e.g.the link
from Lanswitch B to Lanswitch C goes down.
At this time the spanning tree becomes stable with its shape as following figure (the root is
Lanswitch A ):
Figure 12- 3Final spanning tree
In the actual calculation, the root ID and the specified switch ID should consist of the priority and
MAC address of the switch together. The port ID is composed of port priority and port MAC
address. During the update process of configuration message, other configuration messages will
be changed according to certain rules besides the first four items. But the calculation process is
basically the case.
The delivery mechanism of spanning tree protocol configuration message:

When the network is initialized, all the switches will serve as the tree root, and the designated port
of the switch will send its configuration message periodically with HelloTime for the cycle. If the
port receiving the configuration message is the root port, it increments the MessageAge carried in
the configuration message according to certain rules and starts the timer to give the configuration
message time. If a path fails, the root port on the path no longer receives new configuration
message and the old configuration message will be discarded due to timeout. This will cause the
spanning tree to be recalculated to get a new path substitution to restore network connectivity.
However, the recalculated new configuration BPDU does not immediately propagate throughout
the network, so the old root and designated ports that do not discover the change of topology will
12-127
continue to forward the data according to the original path. If the newly selected root port and the
specified port immediately start data forwarding, it may cause a temporary loopback. So, the
protocol adopts a state transition mechanism. That is, the root port and the designated port go
through an intermediate state before resuming data forwarding. The intermediate state can turn
into the forwarding state only after the ForwardDelay is operated. This delay ensures the new
configuration message has spread throughout the network.
The RSTP implemented by device is an optimized version of the spanning tree protocol. The "fast"
is reflected in the delay when the root port and the designated port go into the forwarding state is,
on some conditions, greatly shortened, thereby reducing the time required for network topology
stability. The convergence time of the network change is important for high latency sensitivity
applications such as voice and video.
The fast transition condition of the root port status is that the old root port on the switch has
stopped forwarding data, and the upstream designated port has started to forward data:
The fast transition condition of the designated port status is as follows:
 An edge port, which is not directly or indirectly connected to any switch. If the specified port is
an edge port, it can directly enter the forwarding state.
 A port connected to a point-to-point link, that is, the port is the master port of the
aggregation ports or full-duplex port. Users can also configure the port as a point-to-point
connection. If the specified port is connected to a point-to-point link, it can enter the
forwarding state immediately after receiving a response by handshaking with the downstream
switch.
The switch using the Rapid Spanning Tree Protocol (STP) is compatible with the switch that
uses the spanning tree protocol. Both protocol messages can be identified and applied to
spanning tree computing.
12.2 OLT RSTP Configuration Management

12.2.1 RSTP Configuration Task
Only after the RSTP is stared the configuration tasks can take effect. Before enabling RSTP, you
can configure the parameters of the device or Ethernet port. After RSTP is disabled, these
configuration parameters are retained and will take effect when RSTP is restarted.
The main configuration tasks of RSTP are as follows:

 enable/disable device RSTP feature;
 enable/disable port RSTP feature;
 configure the working mode of RSTP
 configure the Bridge priority of the device
 configure the Forward Delay feature of the device
 configure the hello-time feature of the device
 configure the Max Age feature of the device
 configure the max forwarding rate of the specified port
 configure whether a specific port can be used as EdgePort
 configure the path cost of the specified port
 configure the priority of the specified port
 configure whether the specific port is connected to the point-to-point link.
12-128
Generally, RSTP features can be implemented by enabling RSTP on the device. If users have
special requirements, they can configure the RSTP parameters.
12.2.2 Introduction to RSTP Configuration

12.2.2.1 RSTP feature of enabling/disenabling the device
Table 12- 1 STP features of enabling/disabling the device

Enable/disable RSTP of the rstp（enable| disable） Control the global RSTP on

device. and off. By default it is
disabled.
Note that enabling the RSTP features of the device will take up some network resources.
12.2.2.2 Configure Bridge priority of a device
The bridge priority of a device determines whether the device can be selected as the root of the
entire spanning tree. You can specify a device as the root of the spanning tree by configuring a
smaller priority.
Table 12- 2Configure Bridge priority of the device
Configure Bridge priority. rstp priority pri Pri is the bridge priority,
ranging from 0 to 61440, with
4096 as the mini particle.
Restore the Bridge priority to no rstp priority The command restores the
default. Bridge priority to default value
32768.
Note that if all the Bridge priorities in the entire switching network use the same value then the
smallest MAC address will be selected as the root. In the case of RSTP enabled, the configuration
of the Bridge priority will trigger recalculation of the spanning tree.
12.2.2.3 Configure Forward Delay of the device
The path failure will trigger recalculation of spanning tree structure. However, the recalculated new
configuration BPDU does not immediately propagate throughout the network, so the old root and
designated ports that do not discover the change of topology will continue to forward the data
according to the original path. If the newly selected root port and the specified port immediately
start data forwarding, it may cause a temporary loopback. So, the protocol adopts a state transition
mechanism. That is, the root port and the designated port go through an intermediate state before
resuming data forwarding. The intermediate state can turn into the forwarding state only after the
ForwardDelay is operated. This delay ensures the new configuration message has spread
throughout the network. The forward delay of the bridge depends on the network diameter of the
switching network. In general, the larger the network diameter is, the longer the forward delay time
12-129
should be configured.
Table 12- 3 Configure Forward Delay features of the device
Configure Forward rstp timer forward-delay seconds Seconds is forward-delay
Delay. timer, in the range of 4 to
30s.
Restore Forward Delay no rstp timer forward-delay Restore to the default of
to default. 15s.
Note that if the Forward Delay is too small,a temporary redundant path may be introduced; if it is
too large, the network connection can’t be recovered for a long time. The users are suggested to
use the default value.
.
12.2.2.4 Configure Hello Time of the device
An appropriate hello time value ensures that the bridge can detect link failures in the network
without taking up too much network resources.
Table 12- 4Configure Hello Time features of the device

Configure Hello Time. rstp timer hello seconds Seconds is Hello Time
timer, in the range of 1 to
10s.
Restore Hello Time to no rstp timer hello Restore to the default of
default. 2s.
Note that excessively long Hello Time value will lead to the link losing packets, so that the bridge
regards it as path failure and starts to recalculation of the spanning tree. Too short Hello Time
value will lead to the bridge frequently forwarding configuration messages, which burdens the
network and CPU. The users are suggested to use the default value.
12.2.2.5 Configure Max Age of the device
Max Age parameters is used to determine whether a configuration message is out of date. Users
can configure it according to the actual network conditions.
Table 12- 5Configure Max Age features of the device
Enter config configure terminal
view.
Configure Max rstp timer max-age seconds Seconds is max-age, in the range of 6 to
Age. 40s. The value of Max-Age is related
to Hello and Forward-Delay. The specific
relationship is: 2 × (Forward-Delay-1)> =
Max-Age> = 2 × (Hello + 1).
Restore Max no rstp timer max-age Restore to the default of 20s.
Age to default
12-130
Note that if Max Age value is too small the spanning tree calculation will be frequent and the
network congestion may be mistaken for a link failure. If Max Age value is too large the link failure
may not be detected and the network’s self adaptability is reduced. The users are suggested to
use the default value.
12.2.2.6 Configure the max transmission rate of the specified port
The max transmission rate of an Ethernet port depends on the physical status and network
structure of the port. Users can configure it according to the actual network conditions.
Table 12- 6Configure the maximum transmission rate for a specific port
Configure the max rstp transmit-limit rate-limit Rate-limit specifies the rate limit
transmission rate of the for sending packets, ranging
port. from 1 to 255.
Restore the max no rstp transmit-limit Restore to the default value 3.
transmission rate of the
port to the default.
Note that too large value will take up so much network resources. Users are suggested to use the
default value.
12.2.2.7 Configure whether the specified port can be an EdgePort
If the current Ethernet port is not connected to the Ethernet port of any other Bridge, the port should
be configured as an edge port so that the port can directly enter the forwarding state, which
reduces the unnecessary transition time. If a specific port is configured as an edge port but the port
is connected to a port on another bridge, the RSTP protocol can automatically detect and
reconfigure it as a non-edge port.
Table 12- 7Configure whether the specified port can be an EdgePort
Enter port view. interface olt interface-num
Configure the port as rstp edged-port (enable|disable)
edge/non-egde port.
Note that If the current Ethernet port changes from a non-edge port to an edge port, users are
recommended to configure the port as an edge port manually. The RSTP protocol cannot detect
whether a non-edge port is changed to an edge port. For a port directly connected to a user
terminal, set it as an edge port. This allows the port to be quickly transited to the forwarding
state to avoid unnecessary waiting when the user is powered on.
12.2.2.8 Configure the path cost of the specified port
The path cost of the Ethernet port is related to the link rate. The higher the rate is the smaller the
configuration value should be. RSTP can automatically detect the current link rate of the Ethernet
port and convert it into the corresponding path cost.
Table 12- 8Configure the PathCosr of a specified port
12-131
Configure the Path Cost. rstp cost cost
Restore the Path Cost to no rstp cost By default, the device

the default. can have the PathCost
directly from the link
rate the port.
Note that the configuration of the pathCost will cause recalculation of the Spanning Tree. Users
are suggested to adopt default value to let RSTP compute the pathCost of the current Ethernet
port.
12.2.2.9 Configure the priority of the specified port
By setting the priority of an Ethernet port, users can specify that a specific Ethernet port is included
in the spanning tree. Generally, the lower the configured value is, the higher the port priority is, and
the more likely the Ethernet port is included in the spanning tree. If all the Ethernet ports of a bridge
share the same priority, the priority of the Ethernet port depends on the index of the Ethernet port.
Table 12- 9Configure the priority of a specified port
Configure the priority rstp port-priority port-priority Port-priority: Port
of the port. priority, in the range of 0
to 240, with 16 being the
smallest particles.
Restore the priority of no rstp port-priority Restore the priority of all
the port to default. Ethernet ports in the
Bridge to the default
value 128.
Note that the change of the Ethernet port priority will trigger the recalculation of the Spanning Tree.
12.2.2.10 Configure whether the specified port is connected to point-to-point

link
The two ports connected to the point-to-point link can be quickly transited to the forwarding state by
sending synchronization packets, thus reducing the unnecessary forwarding delay time. If this
parameters is configured in automatic mode, the RSTP protocol automatically detects whether the
current Ethernet port is connected to a point-to-point link.
Table 12- 10Configure connectivity of a specified port to point-to-point link

Configure the port to rstp point-to-point Auto, force-false, and
connect to the (auto|force-false|force-true) force-true
point-to-point link. respectively are the
auto mode of
configuration, the
port unconnected to
12-132
the point-to-point link

and the port
connected to the
point-to-point link.
Restore the parameters to no rstp point-to-point Restore the default
default. configuration to auto.
Note that the current Ethernnet port must be a master port of the aggregation port and is in full
dulex mode before it is configured as a point-to-point link. Otherwise, the configuration is invalid.
Users can manually configure whether the current Ethernnet port is connected with the
point-to-point link but are suggested to set it to auto mode.
12.2.2.11 OLT RSTP monitoring and maintenance
The following operations are only used for RSTP monitoring and maintenance, and for command
application, pls. refer to “Command Line Manual”.
Table 12- 11RSTP monitoring and maintenance

Display the Bridge-info of show rstp bridge-info
RSTP.
Display RSTP info of all ports. show rstp interface-info all
Query the RSTP info of the show rstp trunk-port-infotrunkid
ports in the link aggregation
group.
Enter “port” view. interface olt interface-num
Display the detailed RSTP show rstp interface-info The command is

info of the specific port. implemented in “xe” or
“ge” view.
12.2.3 RSTP Configuration Example

 OLT uplink port 1/1,1/2and 1/3 are connected respectively with one of the switch ports.
 Enable global and RSTP of the port.
 Configure the tasks respectively on the global and the uplink port.
 Enable RSTP of the switch (the switch configuration omitted).
12-133
12.2.3.2 Networking Fig
Figure 12- 4RSTP networking application
$Enable the global RSTP:

G1000(config)# rstp enable
$Configure OLT Bridge priority as 4096:
G1000(config)# rstp priority 4096
$Configure Forward Delay timer value as 20s (note: the value of max-age is related to Hello and
Forward-Delay as followed: 2* （ forward-delay-1 ） >=max-age >=2* （ hello +1 ） ). If some
configurations don’t meet the relationship the conflict will be prompted:
G1000(config)# rstp timer forward-delay 20
$Configure OLT Hello timer value as 5s:
G1000(config)#rstp timer hello 5
$Configure OLT max-agetimer value as 18s:
G1000 (config)#rstp timer max-age 18
$Configure OLT transmission rate as 30packets/s：
G1000 (config)# rstp transmit-limit 30
$Configure RSTP path cost of OLT uplink port 1/1 as 200000：
G1000 (config)# interface olt1/1
G1000 (config-if-gigabit-ethernet-1/1)#rstp cost 200000
$Set OLT uplink port 9/1 as edge port:
G1000 (config-if-gigabit-ethernet-1/1)#rstp edged-port enable
$Enable/disable the point-to-point mode of OLT uplink port 1/1:
G1000 (config-if-gigabit-ethernet-1/1)#rstp point-to-point force-true
G1000 (config-if-gigabit-ethernet-1/1)#rstp point-to-point force-false
$Set the priority of OLT uplink port 1/1:
G1000 (config-if-gigabit-ethernet-1/1)#rstp port-priority 14
13 Link Aggregation Configuration Management

13.1 Brief introduction to link aggregation
Link aggregation, also known as port aggregation, is the aggregation of multiple ports to form an
aggregation group, so as to realize the sharing of out/in load in each member port in the
aggregation group and also provide higher connection reliability. If you connect multiple links
13-134
directly between two devices without opening the STP without using link aggregation, you will
cause a broadcast storm.
Member ports capable of load sharing in the same sink group must have the same rate, duplex,
and base configuration. Basic configuration includes:
(1)VLAN configuration: the VLAN allowed to pass on the port, the port default VLAN ID.
(2)QoS configuration includes: priority tag, default 802.1p priority, queue mapping, scheduling
mode, etc.
(3)Port properties configuration: VLAN type (Hybrid port or Transparent port, etc.) is consistent.
(4)ACL configuration: the applied ACL list.
There are three ways of link aggregation:
Manual aggregation: the administrator can configure which ports to join an aggregation group by
manual command.
Dynamic Aggregation: the Protocol dynamically determines which ports join which Aggregation
group. This method is called dynamic LACP Aggregation. The LACP Protocol (Link Aggregation
Control Protocol) dynamically determines which ports join or leave the Aggregation group.
Static LACP aggregation: the administrator manually specifies which ports belong to the same
aggregation group, but LACP protocol is still started on these ports and LACP messages are
received and processed. Once the static aggregation group is deleted, these ports can be
dynamically determined to join another aggregation group through LACP.
13.1.1 basic principles of LACP
LACP (Link Aggregation Control Protocol) is a Protocol based on IEEE 802.3ad standard. The
LACP protocol interacts with the other side through LACPDU (Link Aggregation Control Protocol
Data Unit).
The two parties using LACP aggregation (called Actor and Partner, respectively) interact with the
aggregation information of the Actor and Partner through a protocol message called
LACPDU(LACP Data Unit) to reach an agreement on the whole link aggregation. The protocol
message mainly contains the following information: local and opposite system priority, local and
opposite system ID, local and opposite port operation key, local and opposite port priority, local and
opposite port ID, local and opposite port status. According to these information, both sides of the
aggregation select the appropriate link according to a certain selection algorithm and control the
state of the aggregation. Selected member links can normally forward traffic, while unselected
member links will be placed in the blocked state and cannot forward any traffic. Aggregation link
the total bandwidth is equal to the selected members of the link bandwidth, the sum and aggregate
traffic on the link will be according to certain rules to share to all members of the selected link,
because the LACPDU is cyclical interaction, namely the aggregation of both sides every once in a
while and mutual agreement on to send a message, so when you have selected members link
does not work for some reason, link aggregation can perceive, and link-state, this link for blocking
and heavy traffic is assigned to other members of the selected link. This will increase the
bandwidth, link dynamic backup function.
The operation Key is a configuration combination automatically generated by the aggregation
control according to some configuration of member ports during link aggregation, including port
attribute configuration (including port rate, duplex mode and link state configuration), port isolation,
QinQ configuration, VLAN configuration, MAC address learning configuration, etc.
13.1.2 Introduction to manual link aggregation group
The manual link aggregation group is manually configured by the user and does not allow the
system to automatically add or remove ports from the aggregation group. The sink group must
contain at least one port. Users can delete any port sink group that has been formed, and all ports
of the sink group will leave the sink group. After creating a port sink group, users can manually
add/remove member ports.
LACP protocol of manual sink port is closed, and users are forbidden to open LACP protocol of
13-135
manual sink port.
13.1.3 An introduction to the static link aggregation group
Static lacp aggregation is manually configured by the user and does not allow the system to
automatically add or remove ports from the aggregation group. The aggregation group must
contain at least one port. The lacp protocol for static aggregation ports is active, and when a static
aggregation group is removed, its member ports will form one or more dynamic lacp aggregations
and keep lacp active. Lacp protocol that prevents users from closing static aggregation ports.
In a static aggregation group, the port can be in one of two states: selected or unselected. Both the
selected and unselected ports can send and receive lacp protocols, but the unselected ports
cannot forward user messages.
In a static aggregation group, the system sets the port to be either selected or unselected as
follows:
 The port with the highest priority is selected and the other ports are in the unselected state
according to the priority of the port in full duplex / high rate, full duplex / low rate, half duplex
/ high rate, half duplex / low rate.
 If a port is different from the peer device connected to the selected smallest port or if it is
connected to the same peer device but with its ports in a different AGG group, the port will
be in unselective state.
 Ports cannot be aggregated due to hardware limitations (such as cross-board AGG). A port
that cannot be aggregated with the smallest port in the selected state will be unselected.
 A port that is different from the basic configuration of the smallest port in the selected state will
be unselected.
 The number of selected ports in the AGG group supported by the device is limited. If the
number of the current member ports exceeds the maximum number of selected ports, the
system selects the selected ports according to the port number from small to large
order, the other was unselected port.
13.1.4 introduction to dynamic link aggregation group
Dynamic lacp is an automatically created / Deleted AGG. Users are not allowed to add or remove
member ports in dynamic lacp AGG. Only the port with the same speed and duplex attributes, the
same basic configuration and in connection to the same device can be dynamically aggregated
together. Even if there is only one port the dynamic AGG can also be created, that is single-port
AGG. Lacp is enabled on a port in dynamic AGG.
In a static AGG group, a port may be in two states: selected or unselected. Selected ports and
unselected ports can send and receive lacp protocol, but unselected port cannot forward user
packets.
The number of selected ports in the AGG group supported by the device is limited. If the current
number of member ports exceeds the maximum number of ports, the local system and the peer
system will negotiate. The status of the port is determined based on the size of the port ID of the
superior device ID. The detailed negotiation steps are as follows:
Compare the device ID (system priority + system mac address). First compare the system priority,
if the same, then compare the system mac address. The small end device ID end is considered
superior.
Compare the port ID (port priority + port number). For each port at the end of the superior device ID,
the port priority is compared first and then the port number is compared if the priority is the
same. The ports with small port IDs are selected ports and the remaining ports are unselected
ports.
13-136
In an AGG group, the port with the lowest port number in the selected group is the master port of
the AGG group, and the other ports in the selected group are the member ports of the AGG group.
When a LACP protocol is enabled on a dynamic AGG port, the management key defaults are
zero. When the LACP protocol is enabled on a static AGG port, the management key of the port is
the same as the AGG group ID.
For a dynamic AGG group, the group members must have the same operation key. In a manual or
static AGG group, the ports in Active status have the same operation key.
The interface in the dynamic AGG group automatically enables the LACP protocol. The interface
sends LACPDUs to the peer on the LACP priority, system MAC address, LACP priority, port
number, and operation key of the system. After receiving the LACPDU, the peer compares the
received information with the information received from other interfaces to select the interfaces that
can be in the selected state, so that the two ends can agree on the selected interfaces.
13.2 Link Aggregation Configuration

13.2.1 Configure Manual Link Aggregation Group
Table 13- 1

Enter “config” view. configure terminal -
Required.
Configure up to 8 AGG
Create manual link-aggregation group trunk-groupid
groups in a system. Each
AGG group. psc psc
AGG group contains up to 8
member ports.
Modify the traffic
distribution policy of link-aggregation group trunk-groupid
Optional.
manual AGG new-psc psc
group.
Query configuration show link-aggregation group
Optional.
of the AGG group. (trunk-groupid | all)
Enter port view. interface olt interface-num -
Add the current

port link-aggregation group
port to an AGG Required.
trunk-groupid
group.
Removes the
current port from no port link-aggregation group
the specified trunk trunk-group
group
Deletes the
no link-aggregation group (trunk-group|
specified or all link Required.
all)
aggregation groups
13-137
13.2.2 Configure Static Link Aggregation Group
Table 13- 2
Required.
Configure up to 8 AGG
Create a static link-aggregation group trunk-groupid
groups in a system. Each
AGG group. psc trunk-psc static
AGG group contains up to 8
member ports
Modify the traffic
link-aggregation group trunk-groupid
distribution policy of Optional.
new-psc psc
static AGG group.

Optional.
Add the current

port link-aggregation group
port to an AGG Required.
trunk-groupid
group.
Display
configuration of the show port link-aggregation-info Optional.
port AGG group.
Deletes the Port automatically enables

no link-aggregation group (trunk-group|
specified or all link lacp after removing static
all)
aggregation groups link aggregation group
Deletes the Port automatically enables

no port link-aggregation group
specified or all link lacp after removing static
trunk-group
aggregation groups link aggregation group
13.2.3 Configure Dynamic Link Aggregation Group
Table 13- 3

Enter “config” view. configure terminal
Optional.
13-138
Configure the system

Configure priority of link-aggregation system-priority
priority, in the range of 0 to
the system. system-priority-value
65535.
Required.
Port lacp is enabled to
automatically join the
aggregation group instead
Add the port to the of creating an aggregation
dynamic AGG lacp enable group in the config view and
group. then adding the port.
Dynamic aggregation
groups currently support
only SA+DA based traffic
distribution strategies.
Configure the port Value in the range of 0 to
lacp port-priority port-priority-value
priority. 65535.
After lacp of port is enabled,

Remove dynamic
lacp disable dynamic aggregation
aggregation groups
group is removed.
Display
configuration of the show port link-aggregation group Optional.
port AGG group.
13.2.4 Descriptor configuration aggregation group
Table 13- 4

Enter “view” view. configure terminal -
Optional.
Create AGG group link-aggregation group trunk-groupid Descriptors can’t be
descriptors. description description conjured for a dynamic link
AGG group.
13-139
13.3 Link Aggregation Configuration Example

13.3.1 Networking Requirements
OLT G1000 aggregates three ports (GE 1/1, GE 1/2 and GE 1/3 ) to access the peer Switch A to
implement load balancing between the ingress and the egress of all group member ports.
13.3.2 Networking Figure
Figure 13- 1 Example for port AGG configuration
13.3.3 Configuration Procedure
（1） Create a manual AGG group

Create port aggregation group 1. The traffic distribution policy is based on the source MAC
address and the value is 1:
G1000(config)# link-aggregation group 1 psc 1
Add Port GE 1/1, GE 1/2 and GE 1/3 to AGG group 1:
G1000(config-if-gigabit-ethernet-1/1)#port link-aggregation group 1
G1000(config-if-gigabit-ethernet-1/1)#interface olt 1/2
Query info of link AGG group:
G1000(config)# show link-aggregation group all
Aggregation Description:
System ID: 2500, 00:1a:69:01:3c:c7
Group-ID Aggregator-Type Port-Selection-Criteria Description port
-----------------------------------------------------------------------------------------------------
1 manual srcmac 1/1 1/2 1/3
(2)Create a static link AGG group
Create port AGG group 1. The traffic distribution policy is based on the source MAC address and
13-140
the value is 1:
G1000(config)# link-aggregation group 1 psc 1 static
Add Port GE 1/1, GE 1/2 and GE 1/3 to AGG group 1:
G1000(config-if-gigabit-ethernet-1/1)#interface olt 1/2
Query info of link AGG group:
Aggregation Description:
System ID: 2500, 00:1a:69:01:3c:c7
-----------------------------------------------------------------------------------------------------
1 static srcmac 1/1 1/2 1/3
(3)Create a dynamic link AGG group
Add Port GE 1/1, GE 1/2 and GE 1/3 to the dynamic link AGG group:
G1000(config)# int olt 1/1
G1000(config-if-gigabit-ethernet-1/1)#lacp enable
Query info of the link AGG group. The current dynamic link AGG only supports srcdestmac traffic
distribution policy:
System ID: 32768, 00:1a:69:01:42:44
-------------------------------------------------------------------------------------------------------
1dynamic srcdestmac 1/1 1/2 1/3
13-141
14 Port Mirroring Configuration Management

14.1 Introduction to Port Mirroring
Port mirroring is to duplicate the data on the monitored port to the specified monitoring port, and
the data are analyzed and monitored. Generally, a monitoring device is connected to the
monitoring port. The administrator can analyze the mirrored packets and perform network
monitoring and troubleshooting.
Figure 14- 1 Port mirror

You can specify the direction of packets to be monitored, as follows:
 Only monitor the packets received by the port (ingress packet mirroring);
 Only monitor the packets sent by the port (egress packet mirroring);
 Monitor the packets received and sent on the port (bidirectional packet mirroring).
14.2 Port Mirroring Configuration
G1000 supports 1 mirror group configuration, and the user can specify the direction of the
monitored message. It should be noted that packet loss will occur if the flow of the monitored
stream exceeds the maximum rate of the monitored port. For example, when using 1G port to
monitor the flow in and out of 10G port, pay attention to this situation.
Table 14- 1 Port mirroring configuration

Enter config configure terminal -
view.
Create/Delete mirror-group1 Required.
port mirroring no mirror-group 1
group.
14-142
Configure the mirror-port 1 (ingress | egress | ingress-egress) Required, ingress

monitored port means monitor
and specify the entry, egress
direction of the means monitor
monitored exit,
message ingress-egress
means monitor
two-way
message.
Delete the no mirror-group 1 Optional.
monitored port
Enter the upper interface olt interface-num Required,
port view This command
modifies the
monitor port if it
already exists for
the mirror group
Configure monitor-port 1 Monitor ports can
monitor port only be
configured with
up to 1G or 10G
ports
Query for port show mirror-group Config and
mirror group enable views
information
Description:
G1000 supports cross-board mirroring, that is, monitoring ports and monitored ports can be located
on separate business disks.
The mirror group can only be configured with one monitor port.
The monitoring of the monitoring port to the message is not affected by the VLAN.
14.3 Port Mirroring Configuration Example

 PON port 2/4 is a monitored port. The packets received and sent on the port are
monitored.
 PON port 2/1 is a monitored port. The packets received on the port are monitored.
 the uplink port 1/1 is a monitoring port, monitoring the packets on port 2/1 and 2/4.
14-143
Figure 14- 2 Port mirroring configuration example
Create port mirroring group 1:

G1000(config)# mirror-group 1
Specify PON port 2/4 as a monitored port of group 1:
G1000(config-if-pon-2/4)#mirror-port 1 ingress-egress
Specify PON port 2/1 as a monitored port of group 1:
G1000(config-if-pon-2/4)#mirror-port 1 ingress
Specify GE 1/1 as monitoring port:
G1000(config-if-gigabit-ethernet-1/1)#monitor-port 1
Query configuration results:
G1000(config)# show mirror-group
---------------------------------------------------
Mirror Group ID: 1
Monitor port: 1/1
Mirror ports:
2/1 both, 2/4 ingress,
15 Mac Address Table Configuration

Management
15.1 Introduction to Mac Address Table
For fast forwarding of packets, the switching device needs to maintain the MAC address
forwarding table. The MAC address forwarding table is a port-based Layer 2 forwarding table, which is
15-144
used by the switch to implement Layer 2 packet forwarding. The entries in the MAC address forwarding
table include:
 Destination MAC address
 The VLAN ID of the port
 Forward port number
The switching device obtains the forwarding port number of the Layer 2 packets by searching the
MAC address forwarding table to implement Layer 2 packet forwarding.
The dynamic entries in the MAC address table are learned by the switching device. The process of
learning MAC addresses is as follows:
If a data frame is received from a port (suppose port 1), the switch will analyze the source MAC
address of the data frame (assuming SA1) and assume that the packet with the destination MAC
address of SA1 can be forwarded through port1.
If SA1 is included in the MAC address forwarding table the switch will update the according
entries.
If SA1 is not included in the MAC address forwarding table the switch will add this new MAC
address, including the forwarding port corresponding to the MAC address, to the MAC address
forwarding table as a new entry.
After the process of learning source MAC address is complete the switch starts forwarding
packets.
The packets whose destination Mac address already exists in the Mac address forwarding table
will be forwarded directly by the hardware.
For a packet whose destination MAC address does not exist in the MAC address forwarding table,
the system forwards the packet to all ports except the receiving port in the same VLAN as the receiving
port. This is usually called broadcasting the packet.
15-145
Figure 15- 1
After broadcasting the packet the switch, the switching device takes the following actions based
on whether the packet is received:
 If the current device receives a response to the broadcast packet from the destination
device, it indicates that the packet is normally sent to the destination device. The MAC
address of the destination device will be included in the reply packet, and the current
device learns to add the MAC address of the destination device to the MAC address
forwarding table. And then the packets to the same destination MAC address can be
forwarded with the newly added MAC address entry.
 If the current device does not receive the response from the destination device, it indicates
that the destination device is unreachable or the destination device receives the packet
but does not reply. In this case, the current device cannot learn the MAC address of the
destination device. Therefore, when the current device forwards packets with the
destination MAC address the next time, it continues to transmit the packets in broadcast
mode.
The MAC address forwarding table is limited in capacity. To maximize the use of the resources
the switching device updates the table with the help of aging mechanism. If no packets from
some network devices are received within the aging time, the MAC address entries related to
the devices will be Deleted. MAC address aging doesn’t take effect on static MAC address
entries.
Users can manually configure (add or modify) MAC address entries according to the actual
network conditions. The entries added or modified can be either static entries or dynamic ones.
15-146
Description:
Only unicast addresses can be learn through the MAC address learning mechanism.
Packets with source MAC addresses as broadcast addresses are discarded.
MAC address entries can be classified into two type according their characteristics and
configuration modes.
 Static MAC address entries: they are manually added and Deleted by users and won’t be
aged out. For a network with little device changes, they can reduce the broadcast traffic on
the network.
 Dynamic MAC address entries: they can be aged out according to the aging time
configured by users. The switch can add dynamic MAC address entries by using the MAC
address learning mechanism or manually created by users.
15.2 OLT MAC Address Management Configuration

15.2.1 Configure the MAC Address Aging Time
Setting the appropriate aging time can effectively implement the MAC address aging
function. The aging time set by the user is too long or too short, which may affect the Layer 2
switching performance of the G1000.
 If the aging time is too long, the system may accumulate many out-of-date MAC address
entries and exhaust the resources of the MAC address forwarding table. As a result, the
system cannot update the MAC address forwarding table based on network changes.
 If the aging time is too short, the system may Delete the valid MAC address entries and
reduce the forwarding efficiency.
Table 15- 1 MAC address aging time configuration

Seconds: in seconds, in
Set the aging
mac-address aging the range of 1-3600. By
time of MAC
(seconds|default|no-aging) default, the aging time is
address entries.
300 seconds.
Display the aging
time of dynamic show mac-address aging Config view.
address entries.
This command is a system configuration command that applies to all ports. The aging
mechanism works only on dynamic (learned or aging) MAC address entries.
In general, the default aging time of 300 seconds is recommended. Use the no-aging command
to disable MAC address entry aging.
Descriptions:
By learning the MAC address added to the MAC address table, aging is completed in
the second cycle of its aging cycles.
15-147
15.2.2 Configure Port-bound Static MAC Address Table
The device supports static MAC address bound to a specific uplink port and to a specific link
AGG group. Before a static MAC address is bound to a link aggregation group, users must
create a link AGG group.
Table 15- 2 MAC address table entries configuration

Bind static MAC Required.
mac-address static mac mac-address port portid
address to the Portid must be
vlan vlan-id
port. uplink port.
Bind the static Required.
MAC address to mac-address static mac mac-address trunk trunk trunkgroupid：
the link AGG groupid vlan vlanid 1-8,the No. of link
group. AGG group.
Unbind the port or
the link AGG
no mac-address static mac mac-address vlan
group to the -
vlanid
static MAC
group.
Clear the static
no mac-address static all -
MAC group.
Display the static show mac-address static
MAC group. show mac-address all
15.2.3 Clear and Query MAC Address Table
G1000 is able to clear and query dynamic MAC address table as follows:
Table 15- 3

Clear dynamic
Only clear dynamic MAC
MAC address mac-address flush
address table.
table.
show mac-address mac
mac-address
Vlanid: Specifies the VLAN ID,
show mac-address port (portid|all)
Query dynamic in the range of 1 to 4094.
vlan (vlanid|all)
MAC address Portid: OLT port number.
show mac-address vlan vlanid
entries. Onuid: indexed by the ONU ID
show mac-address all
index.
show mac-address onu onuid
vlan (vlanid|all)
15-148
15.2.4 Configure MAC Address Limitation
The G1000 supports the limitation of the MAC address learned by each port. After entering the
OLT port view, users can set the MAC address limit of the port, in the range of 0 to 4096. The
port will not learn MAC addresses beyond the MAC limit. If it is set to 0, no MAC address is
bounded.
Table 15- 4 OLT MAC Address Limitation Configuration

Enter “OLT port”
interface olt interface-num “xe,ge,pon” view.
view.
Configure OLT MAC Required, in the
mac-limit mac-limit
address limitation. range of 0-4096.
Delete OLT MAC Restore to the
no mac-limit
address limitation. default 0.
Display OLT MAC
show mac-limit -
address limitation.
15.2.5 MAC Address Movement
The MAC address movement check function implemented on the OLT mainly utilizes the control
function of the switch chip to learn the MAC address. When the movement is set to be disabled,
before the MAC address is aged out, if the MAC address is changed from one port to the other,
or if the packets are received from another port then the chip will not update the MAC address of
the port, and not forward the message, while the corresponding MAC address migration alarm
occurs, alarming once per minute.
Table 15- 5

Enable/disable MAC
mac-address movement (enable|disable)
address movement.
Query MAC address
show mac-address movement
movement configuration.
15.3 OLT MAC Address Configuration Example

 The aging time of the dynamic MAC address entries on the G1000 OLT port is set to 500
seconds, and the static address 00: 1f: a2: 70: dc: 81 is bound to the uplink port 1/1 in
15-149
VLAN10.
 The uplink ports 1/2 and 1/3 are aggregated into a link group. And bind static MACs 00: 1f:
a2: 70: dc: 82 on the link aggregation group.
 Set MAC address movement to be disabled and check whether the configuration is
successfully forwarded.
Figure 15- 2 OLT MAC address configuration Example
Configure the aging time of MAC address entries to be 500s:

G1000(config)# mac-address aging 500
G1000(config)# show mac-address aging
Mac address aging time: 500
Add static MAC address 00:1f:a2:70:dc:81 to the uplink GE 1/1 in VLAN 10:
G1000(config)# mac-addr static mac 00:1f:a2:70:dc:81 port 1/1 vlan 10
G1000(config)# show mac-address static
Index MacAddr VLAN State Dest-port
----------------------------------------------------
1 00:1f:a2:70:dc:81 10 static 1/1
The count of static mac is 1.
Create link AGG group as groupid 1, and add the group to vlan100:
G1000(config)# link-aggregation group 1 psc 1
G1000(config-if-gigabit-ethernet-1/2)# int olt 1/3
Trunk ID: 1
PSC: srcmac
Port member: (9,2) (9,3)
Bind static mac 00:1f:a2:70:dc:82 in link AGG group1:
G1000(config)# mac-address static mac 00:1f:a2:70:dc:82 trunk 1 vlan 100
15-150
G1000(config)# show mac-address static

Index MacAddr VLAN State Dest-port
----------------------------------------------------
1 00:1f:a2:70:dc:81 10 static 1/1
2 00:1f:a2:70:dc:82 100 static TrunkID:1
Configure MAC address movement to be disabled:
G1000(config)# mac-address movement disable
Check MAC address movement configuration:
G1000(config)# show mac-address movement
mac-address movement state： disable
15.4 OLT MAC Address Table Query Example

 Use the port, vlan, and onu as index to query the learned MAC addresses on the OLT.
Figure 15- 3 OLT MAC address configuration example
Use PON port 2/1 as index to query the corresponding MAC address on OLT:
G1000(config)# show mac-address port 2/1 vlan all
Index MacAddr VLAN State Port-onuId
------------------------------------------------------------
1 00:00:00:00:00:12 2002 Dynamic 2/1
Use VLAN 2002 as index to query the corresponding MAC address on OLT:
G1000(config)# show mac-address vlan 2002
------------------------------------------------------------
1 00:00:00:00:00:12 2002 Dynamic 2/1
15-151
2 00:00:00:00:00:15 2002 Dynamic 2/4

Use ONU 2/7/3 as index to query the corresponding MAC address on OLT:
G1000(config)# show mac-address onu 2/7/3 vlan all
------------------------------------------------------------
1 00:1a:69:05:05:05 1 Dynamic 2/7/3
15.5 ONU MAC Address Table Configuration Management

15.5.1 Configure the Aging Time of MAC Address
Table 15- 6 Configure the aging time of OUN MAC address

Enter “onu” view. interface onu interface-num Required.
Configure the aging mac-address aging Required.
time of ONU MAC. (seconds|default|no-aging) seconds：in the range of 1-3600s;
1-3600:aging time;
Default: 300s;
No-aging: not age.
Display the aging show mac-address aging Optional for query configuration.
time of ONU MAC.
15.5.2 Configure the onu port MAC address limit
Table 15- 7 Port MAC address limit configuration

Enter “onu” view. interface onu interface-num Required.
Required
Configure the onu port max-mac-number uniid num Uniid: range 1-26, num:
port MAC address
port max-mac-number uniid disable range 1-255, unlimited by
limit
default
Query for MAC
address limit on show port max-mac-number
onu port
15.5.3 configure the number of MAC address limits based on onuid
Table 15- 8 MAC address limit number configuration based on onuid

15-152
Enter “onu” view. interface onu interface-num Required

Required.
Configure the Limit-num: number of
number of MAC MAC address limits based
mac-limit(enable | disable)limit-num
address limits
based on onuid on onuid, range 1-1024,
disable by default
Query the number
of MAC address
show mac-limit
limits based on
onuid
15.6 Example of ONU MAC Address Table Configuration

Management
 Set the aging time of ONU address to 150s, and query the result.
 Configure the blacklist on ONU, adding the Mac address 00:00:00:00:00:01 to the blacklist.
And query the result.
 Configure the whitelist on ONU, binding 00：00：00：00：00：11 to port 1, binding
00:00:01:00:00:12 to port 2. And query the result.
 Configure the max no of addresses that can be learned on ONU port 1 as 10 and query
the configuration results.
Figure 15- 4 Example MAC address configuration diagram
Set the aging time of ONU Mac address table to 150s:

G1000(config-if-ont-2/1/1)#mac-address aging 150
15-153
Query the aging time of ONU Mac address table:

G1000(config-if-ont-2/1/1)#show mac-address aging
Mac address table aging time : 150
Set the max no of Mac address on ONU port 1 to 10:
G1000(config-if-ont-2/1/1)#port max-mac-number 1 10
G1000(config-if-ont-2/1/1)#show port max-mac-number
PORT MAX MAC NUMBER
--------- ------------------
1 10
2 disable
3 disable
4 disable
16 QoS Configuration Management

16.1 Introduction to QoS
In data communication networks, services such as data, voice, video, and TV have gradually
become a trend, and real-time services such as voice and video have higher requirements for
data network QoS.
QoS, or Quality of Service, is used to assess the ability of a service provider to meet customer
service needs. In the Internet, QoS is assessed on the network delivery of packet service
capabilities. Commonly referred to as QoS, several important indicators are evaluated in the
packet delivery process: packet loss, transmission delay, delay jitter and bandwidth.
QoS requirements of each service is not the same, so the configuration of the service QoS
management is not the same, usually voice and video services on the more stringent QoS
requirements. For example, language business requirements are as follows:
 Packet loss rate can’t exceed 1%;
 One-way delay can’t exceed 150ms to 200ms;
 Average delay jitter can’t exceed 30ms;
 Each call needs 21 ~ 106kb / s guaranteed bandwidth;
The requirements for video service are as follows:

 Packet loss rate can’t exceed 2%;
 One-way delay can’t exceed 1s;
 Average delay jitter can’t exceed 1s;
 Bandwidth requirement depends on the coding and rate of video stream;
Data services have TCP / IP protocol stack error mechanism and re-transmission mechanism
and other security measures, the QoS requirements are relatively low.
Here are some important concepts related to QoS.
16.1.1 Traffic
Stream, or service traffic, refers to all the packets passing through the current device.
16-154
16.1.2 Traffic Classification
Traffic classification refers to the use of certain rules to identify packets that meet certain
characteristics. The classification rules can be as simple as identifying the traffic with
different priority characteristics based on the TOS field in the IP packet header. It can also
be complex, such as the integrated data link layer (L2), network layer (L3), transport
layer(L4) information such as MAC address, IP protocol, source address, destination
address, source port number, destination port number, and so on. For more information,
see ACL Configuration Management.
16.1.3 Priority
The priority in the packets provides the basis for QoS management of network devices. The
priority includes 802.1p priority, IP precedence, TOS, DSCP, and so on. This chapter only
describes the concept of 802.1p precedence.
The 802.1p priority is in the Layer 2 packet header, applicable to Layer 2 QoS. The structure
of the Ethernet data frame with 802.1Q tag is shown below:
Figure 16- 1 Ethernet frame with 802.1Q tag
The 4-byte 802.1Q tag header contains a 2-byte Tag Protocol Identifier (TPID) and 2-byte Tag
Control Information (TCI). The priority field in the TCI byte is the 802.1p priority, which consists
of three bits, in the range 0 to 7. These three bits indicate the priority of the frame. There are 8
priorities, mainly used for QoS management when the switching equipment is congested.
This is called the 802.1p priority because the application of these priorities is defined in the
802.1p specification.
In addition, there is a common concept is the current priority. The current priority is the priority
of each output queue on the port, which ranges from 0 to 7 and corresponds to the output
queue of a port.
16.1.4 Priority Marking
The priority re-marking function re-specifies the matched packets by referencing ACL for traffic
identification. For more information, see “ACL Configuration Management”.
16.1.5 Packet Filtering
Packet filtering is to filter traffic, such as discarding traffic. This operation will discard the traffic
flow matching the traffic classification rules and allow all other traffic to pass through. The
G1000 enhances the security of the network by filtering out various types of traffic, discarding
services that are useless, unreliable, and doubtful.
16-155
Users can apply ACLs on a port to implement packet filtering. For more information, see ACL
Configuration Management.
16.1.6 Traffic Policing
If the amount of traffic that users send is not limited, a large number of users' bursts of data
will only make the network more crowded. In order to make the limited network resources
more effective, and better serve more users, the flow of users must be limited. For example,
limit a flow of each time interval to having certain amount of resources committed to it, to
prevent excessive congestion caused by the network congestion. Traffic policing is a flow
control policy that limits traffic and resource usage by monitoring traffic specifications. One of
the prerequisites for traffic policing is to know whether the traffic is out of specification and
then implement a policy based on the assessment. Token Bucket is generally used to
evaluate traffic specifications.
A token bucket can be thought of as a container for tokens that have a certain capacity. The
system puts the tokens in the bucket at the set speed. When the bucket is full of tokens, the
extra tokens overflow and the token no longer increases in the bucket.
The parameters for the token bucket when evaluating traffic include:
Average Rate: The rate at which tokens are placed in the bucket, which is the average speed
of the allowed flows. It is usually set to Committed Information Rate (CIR).
Burst Size: The capacity of the token bucket, that is, the maximum traffic size allowed for each
burst, is usually set to CBS (Committed Burst Size). The burst size set must be greater than
the maximum packet size.
Evaluate each packet as it arrives. If there are enough tokens in the bucket for each
evaluation, the traffic control is within the allowable range. In this case, the number of tokens
corresponding to the packet forwarding right is removed from the bucket. Otherwise, the token
consumption is too high, and the traffic exceeds the requirements.
16.2 Queue Scheduling
When the network is congested, it is necessary to solve the problem that multiple packets
compete for the resources of a certain port. Usually, queue scheduling is used to solve the
problem.
16.2.1 Strict Priority (SP) Scheduling
SP queue scheduling algorithm is designed for mission-critical applications, especially suitable

for delay, delay jitter-sensitive applications. One important feature of mission-critical services is
that they require prioritized service to reduce the latency of the response when congestion
occurs. Taking eight output queues as an example, the priority queue divides the eight output
queues of the port into eight classes, in order of 7, 6, 5, 4, 4, 2, 1, and 0, and their priorities are
decreased.
16-156
Figure 16- 2 SP scheduling diagram
The SP algorithm preferentially sends the packets in the higher priority queue according to the
order of priority from the highest to the lower, and then sends the packets in the lower priority
queue when the higher priority queue is empty. Grouping non-critical services such as E-Mail
into lower-priority queues ensures that packets of critical services are prioritized and packets of
non-critical services are transmitted in idle slots that handle critical traffic.
The disadvantage of the SP is that if packets are queued for a long time in a higher priority
queue, the packets in the low priority queue are "starved" because they cannot get services.
16.2.2 Polling Scheduling (RR)
RR (Round Robin) queue scheduling allocates the available bandwidth resources evenly among
the output queues of the port. Because of the equal opportunity of each sending queue, the
scheduling method cannot achieve the priority service for higher priority.
Figure 16- 3 Schematic diagram of RR scheduling
16.2.3 Scheduling by Weight Polling (WRR)
WRR queue scheduling algorithm performs scheduling in turn among the queues to ensure that
each queue has been a certain service time. WRR can configure a weighted value (w7, w6, w5,
w4, w3, w2, w1, w0) for each queue. The weighted value represents the weight of the resource.
For example, a 100M port can be configured by WRR queue scheduling algorithm with a weight
of 50, 50, 30, 30, 10, 10, and 10 (corresponding to w7, w6, w5, w4, w3, w2, w1, w0 ).This
16-157
ensures that the lowest priority queue can obtain at least 5 Mbit / s bandwidth and avoids the
disadvantage that packets in low priority queues may not receive services for a long time when
SP scheduling is adopted.
Figure 16- 4 WRR scheduling diagram
16.2.4 Scheduling of Strict Priority Plus Weight Polling (SP+WRR)
The SP + WRR scheduling algorithm combines the advantages of SP algorithm and WRR
algorithm, and adopts SP scheduling for some output queues (such as network control
protocol packets and TDM services) to ensure QoS features such as delay and jitter of key
services. , And for other priorities, the WRR scheduling mechanism is adopted to make full
use of bandwidth resources.
16.3 Configure QoS
This section covers only the three parts: Queue Priority Mapping, Queue Scheduling, and
Congestion Control. For other configurations, refer to OLT Port Configuration Management,
ONU Configuration Management, and ACL Configuration Management.
The OLT port of the G1000 supports eight output queues, and performs queue mapping and
queue scheduling based on the 802.1p priority of packets. The queue scheduling algorithms
supported by the G1000 OLT include SP, WRR, and SP + WRR.
16.3.1 Queue Priority Mapping Operation
Before entering the output port, the packets are classified into different priority queues according
to their classifications. In a G1000 system, packets are classified according to 802.1p priority
(hereinafter also referred to as cos). The output queue to which packets of a certain priority are
sent is specified by the queue priority mapping. By default, the cos and queue priorities are
one-to-one, that is, cos 0 corresponds to queue 0, cos 1 corresponds to queue 1, and so on.
Note that the system does not carry, that is, for the packets without 802.1Q tags, that is the
packets on the output port with no VLAN tags, the system will add the default VLAN Tags to
them, using the default VLAN ID of the port as the value of the VID field, and using the port
default priority field as the value of the 802.1p priority field (refer to the relevant part of the OLT
16-158
VLAN configuration). The default priority of a packet in a system depends on its scheduling
priority.
With the following configuration, you can configure the queue priority mapping:
Table 16- 1 The queue priority mapping configuration

Enter “port” view. Interface olt interface-num Optional.
qos map-queue pri0-queue Required.
Configure
pri1-queue pri2-queue pri3-queue PRM prii-queue: the output
“cos->output queue”
pri4-queue pri5-queue pri6-queue queue number to which
mapping list.
pri7-queue COS packets are mapped.
Restore default
no qos map-queue -
configuration.
Query configuration
result. show qos map-queue -
Description
Command qos map-queue is used in “port” view and valid only on the current port.
By default, packets with COS 0 are mapped to queue 0, packets with COS 1 are
mapped to queue 1, and packets with COS 7 are mapped to queue 7 and so on.
The command only functions on the packet-received ports, that is at the ingress and the
scheduling algorithm is executed at the egress.
16.3.2 Queue Priority Scheduling Operation
G1000 OLT support the modes of queue scheduling are SP, RR, WRR and SP+WRR. For
detailed information, see Chapter 16.2.
Table 16- 2 Queue scheduling configuration

Enter port view. interface olt interface-num Optional .
Configure the queue
qos sched (sp|sp-wrr|wrr) Required.
scheduling mode.
qos weight queue0-weight queue1-weight Optional.
Configure the weight queue2-weight queue3-weight queuei-weight is the
of WRR. queue4-weight queue5-weight weight of Queue i, in
queue6-weight queue7-weight the range of 0-15.
Display the
show qos sched -
configuration
Description
16-159
1、 Command qos sched is used in the port view and is valid only on the current port; when
used in the “config ” view it works on all OLT ports of the system.
2、 Command qos sched will take effect on packet- sending ports, namely, on the egress of the
packets.
3、 When the scheduling mode is WRR, if the weight value of an output queue is 0, it means
that the strict scheduling is performed on the queue. In this case, the scheduling mode is SP
+ WRR.
4、 The weight ratio of each queue is the queue weight divided by the sum of all queue weight.
5、 By default, the queue scheduling mode is SP+WRR.
6、 By default, the weights of queue 0—5 are 1,1,1,2,2 and 3 with respective ratio of
10%,10%,10%,20%,20% and 30%; the weight value of queue 6-7 is 0, meaning that strict
scheduling is executed. When packets are queued in queues 6 and 7, packets of these two
queues are sent first, and then the other 6 queues are scheduled for WRR.
16.3.3 Congestion Control
G1000 supports congestion control required by ctc2.1. The optional strategies of congestion
control are traildrop, red and wred.
Table 16- 3 Queue scheduling configuration

Limited to ex and ge
views.
Configure mechanism of congestion mode (traildrop|red|wred)
Required.
port congestion control. threshold min-value max-value
Display configuration
show congestion -
results.
16.4 OLT Configuration Example

Classify the packets that enter pon port 2/1. The mapping relationship between the 802.1p
priority (cos) and the output queue is: 0-> 2,1-> 0,2-> 1,3-> 3,4-> 4,5-> 5,6-> 6,7-> 7.Set the
uplink port 1/1 scheduling mode to WRR. The weight of the queue is 10, 5, 10, 10, 5, 10
16-160
Figure 16- 6 Sample QoS configuration diagram
16.4.3 Configuration Procedures
Set the queue priority mapping for the ingress of PON port:
G1000(config-if-gpon-2/1)#qos map-queue 2 0 1 3 4 5 6 7
Display the queue priority mapping on the ingress of PON port:
G1000(config-if-gpon- 2/1)#show qos map-queue
Current port qos mapping parameter is 2 0 1 3 4 5 6 7
Configure queue scheduling for message exits:
G1000(config-if-gigabit-ethernet-1/1)#qos sched wrr
G1000(config-if-gigabit-ethernet-1/1)#qos weight 10 5 10 10 5 10 5 10
shows the queue scheduling configuration of the upper port:
G1000(config-if-gigabit-ethernet-1/1)#sho qos sched
Current port schedule is weighted round robin.
Current port weight : 10 5 10 10 5 10 5 10
Configure the upper port 1/1 congestion control algorithm for tail discard, the minimum
threshold is 80%, the maximum threshold is 90%：
G1000(config-if-gigabit-ethernet-1/1)#congestion mode taildrop threshold 80 90
Display current port congestion control status:
G1000(config-if-gigabit-ethernet-1/1)#show congestion
Port : 1/1
Congestion mode : tail-drop
Congestion low level(%) : 80
Congestion high level(%) : 90
17 ACL Configuration Management

17.1 Introduction to ACL
An access control list (ACL) is used to implement packet filtering by configuring packet matching
rules and processing operations. To filter packets, a network device needs to configure a series of
matching rules to identify packets that need to be filtered. In the identification and classification of
a specific message, according to the pre-set processing methods the corresponding data packets
can be processed, prohibiting from or allowing the data packets passing through.
The data packet matching rule defined by the ACL can also be used by other functions that need to
17-161
differentiate traffic, such as the definition of traffic classification rules in QoS.
According to the purpose of application, ACL is divided into the following categories:
 Standard ACL, in the range 1-1999. The standard ACL can match all the packet fields,
including source / destination MAC address, source / destination IP address, source /
destination port number, IP priority and so on. The process action is only deny and permit.
 Link layer ACL, in the range of 2000-3999. The ACL of the link layer can be matched
 according to the source MAC address, destination MAC address, inner and outer VLAN
priority (ccos, scos), inner and outer VLAN (svlan, cvlan) and Ethernet type of the data
packet. The action is all except deny and permit.
 Advanced ACL, ranging from 4000 to 5999. The advanced ACLs are matched according to
the source IP address, destination IP address, source port number, destination port
number, and IP precedence (ip-precedence, dscp, tos) of the packet. The process action
is all except deny and permit.
 When creating an ACL, users need to specify the type, which determines the scope of the
ACL.
The ACL does not take effect until the ACL has been applied to the port.
For convenience, the rules we use to configure the wildcards in the ACL, whether MAC
addresses or IP addresses, are consistent with the IP subnet mask we are accustomed to. A
wildcard is a bit sequence of the specified length, where the value of the bit is 1 and the value of
0 indicates that no match is required.
17.1.1 ACL Matching Sequence
An ACL may contain multiple rules, each of which specifies a different message range. As a
result, there is a problem of the order of matching between packets when matching packets.
In order to facilitate the management and matching order of ACL rules, ACL rules are organized
into groups. Each group of ACL rules has a relative priority. The smaller the value is, the higher
the priority is. The higher priority rule group is matched first. If there is a rule group with the
same priority, the rule group number (ID) is matched in ascending order.
An ACL rule group can contain up to eight rules. They are matched according to the rule IDs (IDs)
in ascending order.
The ACL rule group is called ACL list, and the ACL rule is called rule.
17.1.2 How ACLs Are Applied on the OLT
The descriptions on standard ACLs, link layer ACLs and advanced ACLS are as follows:
On the OLT, users can apply ACL rules to ge and pon interfaces to implement packet
splitting and processing.
For rule definitions of an ACL a rule group must be first created and defined, ACL list, and
then a rule in a rule group be created. Afterwards, one or more matching conditions of the rule
are defined and the corresponding action is processed.
The port to which the ACL rule applies is applied in the ACL group.
An ACL only applies to the incoming packets of a port, that is, it matches only the incoming
packets, and then performs the corresponding action.
Use packet-filter command to apply ACL to the interface.
17-162
17.2 ACL Configuration

17.2.1 ACL Rule Group Configuration
There are at most 5999 rule groups, each of which has the following attributions:
 Group No.: used to uniquely identify a rule group, ranging from 1 to 5999. When the
priority of multiple rule groups is the same the group number can be used to determine
matching order, in ascending order. The group number is specified at the time of rule
group creation, and can’t be changed.
 Rule No.: rule numbers included in the rule groups.
 Priority: when multiple rule groups are applied to a port the priority determines their
matching order.
 Name: used to describe rule groups.
 Apply or not: Indicates whether the rule group has been applied to the interface.
 Application interface list: The list of interfaces to which the rule group has been applied. If
the rule group is not applied, the list is empty. The priority and the name can be configured
after the rule group is created, but the priority can be modified only when the rule group is
not applied to any interface.
17.2.1.1 Configure an ACL Rule Group
Table 17- 1 configurations for ACL rules
The second PRM is an optional

PRM and is not less than the first
acl advance listid [greater-listid]
PRM.
Create an ACL rule acl basic listid [greater-listid]
When two PRM are entered, the
group. acl link listid [greater-listid]
rule group is created in bulk.
acl user listid [greater-listid]
If only one PRM or two PRM are
equal, the ACL view is displayed.
A rule group already applied to a
port cannot be Deleted.
Delete an ACL rule no acl all The second PRM is optional and is
group. no acl listid [greater- listid] not less than the first argument.
When two parameters are
entered, the rule group is Deleted.
A rule group that has already been
Set the priority of priority priority
applied to a port cannot set a
the ACL rule group. no priority
priority. The default priority is 1.
The name contains up to 63
Set the name of the description description
characters. The default name is
ACL rule group. no description
ACL_xxxx, where xxxx is the rule
17-163
group ID.
Display the rule Display the current rule group.

show list
group in acl view.
Display the ACL Display all the rule groups and the
rule group in “view”, specific ones.
show acl (listid | all)
“enable” and
“config” views.
17.2.2 ACL Rule Configuration
The ACL rule is created and configured in ACL view. An ACL view corresponds to an ACL rule
group. The configuration commands in ACL view are for the current ACL rule group.
An ACL rule group can have up to 8 rules. Each rule has the following attributes:
 Rule ID (ID): Used to uniquely identify rules in a rule group, ranging from 1 to 8. In a rule
group, the matching order of the rule is determined by the number, in ascending order. The
rule ID is specified when the rule is created and cannot be modified.
 Matching conditions: A rule can contain up to four matching conditions. A packet must
match all conditions before it can be considered to match the rule. If no matching condition
is defined, a matching action will be performed on all incoming packets. The matching
conditions in the user-defined ACL rule must be with the ONUID.
 Matching Action: The handling of packets that meet all the conditions of the rule is that a
rule corresponds to a processing action. If no matching action is defined for the rule, the
rule will not affect the processing of the packet. Note that the action of user-defined ACLs
is not configured in the rule group, but in the PON view.
When an ACL rule group has been applied to a port, users cannot configure rules in the rule
group, such as creating a rule, modifying the matching condition and matching action for a rule
that has already been created.
The precondition for rule configuration is the creation of rules first and then set matching
conditions and actions. The matching conditions that can be set are: source MAC address,
destination MAC address, Ethernet types (such as ARP, PPP, RARP and so on), destination IP
address, source IP address, IP types(such as ipv4、ipv6 and so on), IP packet protocol
types(TCP、UDP、ICMP and so on), VLAN ID, 802.1P priority, IP priority, DSCP, L4 source
protocol port, L4 destination protocol port, source ipv6 address, destination ipv6 address,
ipv6-flow-label、ipv6-next-header、ipv6-traffic-class, etc. The available matching actions are as
follows: Enter the specified output queue, modify the 802.1p priority, modify the IP precedence,
modify the DSCP, discard the packets, and allow the packets to pass, and so on.
17.2.2.1.1 Configure an ACL rules
Table 17- 2 Operations for creation and deletion rules

The aclistid value ranges from
Enter ACL view. acl(advance|basic|link|user) acllistid
different ACL views.
17-164
The second parameter is

optional and is not less than
the first argument.
Create rules. rule ruleid [greater-ruleid]
When you enter two
parameters, it indicates the
batch creation rule.
no rule all -
Delete rules.
no rule ruleid [greater-ruleid]
17.2.2.1.2 Configure matching conditions for ACL Rule
The operation for matching conditions of ACL rule

Table 17- 3 Configuration for rule matching conditions

acl The aclistid value ranges from
Enter ACL view. (advance|basic|link|user) different ACL views.
acllistid
Standard ACL view, link layer ACL
view mac Indicates the MAC address
Match source MAC rule ruleid match src-mac
to be matched. Mask is a MAC mask
address. mac mask
that can match a range of MAC
addresses.
Match destination rule ruleid match dst-mac The same as above.
MAC address. mac mask
rule ruleid match cvlan view.The second parameter is
Match inner VLAN.
vlanid [greater-vlanid] optional and is not less than the first
parameter.
rule ruleid match svlan The same as above.
Match outer VLAN.
vlanid [greater-vlanid]
Match inner VLAN Standard ACL view, link layer ACL
rule ruleid match ccos ccos
priority. view, The ccos range is 0-7.
Match outer VLAN Standard ACL view, link layer ACL
rule ruleid match scos scos
priority. view. The scos range is 0-7.
rule ruleid match eth-type All the ACL views can be matched to
Match Ethernet
(arp|ip|ipv6|ppp|pppoe-disc different Ethernet types.
type.
|pppoe-session|rarp|snmp)
All ACL views. Type-value is the value
Match Ethernet rule ruleid match eth-type of the Ethernet length type field, such
type (user-defined). userdefined type-value as 0x0800, which is user-defined.
Standard ACL view, and advanced

ACL view. IP-address refers to the IP
Match source IP rule ruleid match src-ipv4
number to be matched. IP-mask is an
address. IP-address IP-mask
IP mask that can match a range of IP
addresses.
Match destination rule ruleid match The same as above.
IP address. dst-ipv4 IP-address
17-165
IP-mask

Match source port rule ruleid match src-port view.The second parameter is
number. port-start [port-end] optional and is not less than the first
parameter.
Match destination rule ruleid match dst –port The same as above.
port number. port-start [port-end]
rule ruleid match ip-protocol Standard ACL view, and advanced
Match the protocol
(icmp | igmp | tcp | egp | ACL view.
type carried by IP.
udp)
Match 802.1P Standard ACL view, and advanced
rule ruleid match tos tos
priority. ACL view. Tos ranges from 0 to 7.
rule ruleid match Standard ACL view, and advanced
Match IP priority. ip-precedence ACL view. ip-precedence ranges from
ip-precedence 0 to 7.
Match DSCP Standard ACL view, and advanced
rule ruleid match dscp dscp
priority. ACL view. Dscp ranges from 0 to 63.
rule ruleid match vlan vlanid User-defined ACL view. The VLAN
Match VLAN.
[greater-vlanid] ranges from 1-4094.
Match VLAN User-defined ACL view. Cos ranges
rule ruleid match cos cos
priority. from 0-7.
Match ONUID rule ruleid match onuid User-defined ACL view. onuid ranges
Number. onuid from 1-64.
ACL view. IPv6-address refers to IPv6
Match destination rule ruleid match dst-ipv6
address to be matched. Prefix is the
ipv6 address. ipv6-addressprefix
prefix length of the ipv6 address. It
can match a range of IPv6 addresses.
ACL view. IPv6-address refers to IPv6
Match source ipv6 rule ruleid match src-ipv6
address to be matched. Prefix is the
address. ipv6-addressprefix
prefix length of the ipv6 address. It
can match a range of IPv6 addresses.
Match
ipv6-flow-label ACL view. ipv6-flow-labe ranges from
ipv6-flow-label.
ipv6-flow-label 0 to 1048575.
Match
ipv6-next-header ACL view. ipv6-next-header ranges
ipv6-next-header.
ipv6-next-header from 0 to 255.
Match
ipv6-traffic-class ACL view. ipv6-traffic-class ranges
ipv6-traffic-class.
ipv6-traffic-class from 0 to 255.
17.2.2.1.3 Configure ACL rule processing
Table 17-4 doesn’t include user-defined view processing that is configured when the rule is
applied to the port.
17-166
Table 17- 4 Operations for rule matching configuration

acl(advance|basic|link| The aclistid value ranges from different
Enter ACL view.
user) acllistid ACL views.
Enable/disable data rule ruleid
Basic ACL view.
packets to pass. action(permit | deny)
Link layer ACL view, and advanced ACL
rule ruleid action
Add outer VLAN to view. Vlanid ranges from 1 to 4094, and
add-vlan vlanid
the data packets. cos ranges from 0 to 7. Default indicates
(cos|default)
the default port priority.
Modify the outer rule ruleid action
VLAN of the data mod-vlan vlanid The same as above.
packets. (cos|default)
Modify VLAN
rule ruleid action Link layer ACL view, and advanced ACL
priority of the data
mod-cos new-cos view. new-cos ranges from 0 to 7.
packets.
rule ruleid action mirror Link layer ACL view, and advanced ACL
Port mirroring.
interface-port view.
Redirection of the rule ruleid action Link layer ACL view, and advanced ACL
data packets. redirect interface-port view.
17.2.2.1.4 Query ACL rule
When ACL rule is querred all rules in the rule group will be displayed.
Table 17- 5 Query all rules in the rule group

Display the rule group in ACL view. show list Display the current rule group
Display ACL rule group in view, Display all rule groups and all
show acl (listid | all)
enable and config view. specific rule group.
17.2.3 Apply the ACL Rule Group to Ports
After an ACL rule is defined and applied to a port, traffic can be classified and packets can be
processed accordingly. The ACL rule applies to ports in the rule group. Any rule group without
the defined rules cannot be applied to the port. A rule group can be applied to more than one
port, a port can also apply multiple rule groups. The matching order of rules is described in
Section 17.1.1. Applicable to standard ACLs, link-layer ACLs, and advanced ACLs:
Table 17- 6 Operations for ACL application and application lifted

configure
Enter “config” view. -
terminal
Interface olt
Enter “port” view. Pon, ge and xe view.
interface-num
17-167
The precondition for the application is

Apply ACL rule group to the
packet-filter listid that the VLAN mode of pon view is
current port.
transparent.
Lift application of the ACL rule no packet-filter -
group to the current port. (all | listid)
Display the ACL rule group show -
applied to the port. packet-filter
17.3 Example of Standard, Link Layer and Advance ACL

Configuration
There is a user on PON2/1 with the IP: 192.168.12.1. Modify, through the ACL, the VLAN ID of
the packets sent by the user to implement the VLAN translation function.
Figure 17- 1 Example for typical ACL configuration
17.3.3 Configuration Procedures
Configure an advanced ACL list to match source IP address:

G1000(config)# acl advance 4000
Create a rule with the matching source IP address 192.168.12.1 and match only one IP
address.The process action is to modify the VLAN. The original VLAN tag is replaced with VLAN
100 and the priority is the same:
G1000(config-acl-adv-4000)#rule 1
Create 1 rule(s) success
G1000(config-acl-adv-4000)#rule 1 match src-ip 192.168.12.1 255.255.255.255
G1000(config-acl-adv-4000)#rule 1 action mod-vlan 100 default
Query the configuration result:
17-168
G1000(config-acl-adv-4000)#show list
ACL: 4000
Description:
Installed on: no port install
Priority: 1
Rule 1 action: mod-vlan 100 default
Match: source ip address :192.168.12.1
wild card ip address :255.255.255.255
Apply the ACL to PON port 2/1：
G1000(config-if-gpon-2/1)#packet-filter 4000
Start install ACL 4000 to 4000 in port 2/1.
. Install end.
Query the application result:
G1000(config-if-gpon-2/1)#show packet-filter
ACL install on port 2/1 :
4000,
18 Multicast Configuration Management

18.1 Introduction to Multicast
In the network, there are three ways to send packets: unicast, broadcast, multicast.
The unicast mode is suitable for users 'rare networks, and the broadcast mode is suitable for
users' dense networks. Unicast and broadcast modes are inefficient when the amount of users
in a network is uncertain. The multicast technology appears to solve this problem in time. When
certain users in a network need specific information, the multicast sender (that is, the multicast
source) sends only one message. Multicast routing protocols are used to establish tree-based
routing for multicast packets. The information that is delivered is copied and distributed at nodes
as close as possible to the client.
EPON network is a point to multi-point structure, supporting for multicast protocol. Video
multicast service is the best means of access. Therefore, in the EPON system, some new
value-added services can be easily provided by the multicast characteristics of the network,
including the online services such as online broadcast, network TV, distance education,
telemedicine, internet radio and real-time video conference.
various parts of the network into the following roles:

Multicast source: The sender of information is called a multicast source.
Multicast group: Multiple receivers that receive the same information form a Multicast Group,
which has no geographical restrictions.
Multicast group members: Each multicast receiver is a member of a multicast group.
Multicast router: A router that can provide multicast routing is called a multicast router. A
multicast router can manage the members of a multicast group in addition to the receivers of
one or more multicast groups.
Multicast technology is complex, but its fundamental purpose is to multicast information from the
multicast source to the receiver, while meeting the needs of the recipient of the information.
Multicast is an end-to-end service. According to the agreement layer from bottom to top division,
multicast mechanism includes the following four parts:
Addressing mechanism: With the multicast address, the information is sent from the multicast
source sent to a group of recipients.
18-169
Host Registration: The receiving host dynamically joins and leaves a multicast group to
implement multicast member registration.
Multicast routing: constructs a packet distribution tree for multicast routing, and transmits
packets from the multicast source to the receivers.
Multicast applications: Multicast source must support multicast applications such as video
conferencing. TCP / IP protocol stack must support the sending and receiving of multicast
information.
The digital TV system is composed of video multicast server, IP MAN, access network and home
network, as shown in the following figure:
Figure 18- 1 GPON system multicast architecture
The general process where GPON system achieves video on demand are as follows:
Step 1: The user IP STB (Set-top Box) or the PC obtains an IP address from the DHCP server
by sending a DHCP request.
Step 2: The authentication server verifies the user name and password reported by the STB /
PC. After authentication, the authentication server can obtain the TV and video on demand
program list provided by the video server on the specific video service website;
Step 3: The user selects a TV or VOD program using the remote control;
Step 4: After the user selects the program, the STB / PC sends an IGMP multicast join request
to the multicast router.
Step 5: When the IGMP join request packet passes through the ONU, the ONU listens and
records the packet. At the same time, the ONU generates the association between the member
port and the ONU port, and forms a multicast filter table.
Step 6: When the IGMP join request packet passes through the OLT, the OLT listens for this
message and records it. The OLT generates the mapping between the broadcast ID and the
corresponding ONU ID of the multicast group member, and forms a multicast mapping table by
combining ONU multicast application right. Then OLT forwards the table to the ONU through the
management channel. The IGMP Join request packet is then transmitted to the multicast router.
Step 7: Upon receiving an IGMP join request, the multicast router creates a multicast mapping
table (group-to-VLAN mapping) and forwards the multicast stream.
18-170
Step 8: After receiving the multicast stream, the OLT populates the LLID field in the preamble of
the multicast packet as the broadcast ID and broadcasts the multicast stream to the ONU.
Step 9: Upon receipt of a packet with a broadcast ID, the ONU receives the corresponding
multicast stream based on the multicast mapping table delivered by the OLT, checks the
multicast filtering table, and forwards the multicast packet to the user port initiating the IGMP
request message flow;
Step 10: The user watches the multicast program.
The key is to set up a multicast mapping table in the multicast router and set up a multicast
forwarding table on the OLT and copy the video stream.
18.2 IGMP Protocol and Configuration

18.2.1 Introduction to IGMP Protocol
18.2.1.1 Multicast Address
18.2.1.1.1 Multicast IPv4 Address
According to the IANA (Internet Assigned Numbers Authority), IP addresses are classified into
Class A, Class B, Class C, Class D and Class E. Unicast packets use three types of IP
addresses according to the network size. The destination address of a multicast packet uses a
class-D IP address. Therefore, a class-D address cannot appear in the source IP address field
of an IP packet. The class-E address is reserved for future use.
In the IP multicast environment, the packet destination address is not one, but a group, or a
group address. All the information receivers are added to a group, and since then, the data
flowing to the group address immediately began to be transmitted to the receiver, and all
members of the group can receive data packets. This group is the "multicast group”.
A multicast group features the following:
A member of a multicast group is dynamic. The host can join and leave a multicast group at any
time.
Multicast groups can be permanent or temporary.
A multicast group where IANA assigns a multicast address is called a permanent multicast group
(or a reserved multicast group).
For a permanent multicast group, note that:
The IP address of the permanent multicast group remains unchanged, but the member
composition of the group can be changed.
The number of members in a permanent multicast group can be arbitrary, or even zero.
IP multicast addresses that are not reserved for permanent multicast groups can be used by the
temporary multicast group.
The Class-D multicast addresses ranges from 224.0.0.0 to 239.255.255.255. For the scope and
meaning, please see Table 18-1.
Table 18- 1 The scope and meaning of the D-class address
Scope Meaning
Reserved multicast address (permanent group address). The
224.0.0.0～224.0.0.255 address 224.0.0.0 is reserved, and the other addresses are
used by the routing protocol.
224.0.1.0～ Any-Source Multicast (ASM) addresses (temporary group
18-171
231.255.255.255 addresses) that are available to users are valid in the entire
233.0.0.0～ network.
238.255.255.255
232.0.0.0～ SSM (Source-Specific Multicast) multicast group address is
232.255.255.255 available to users.
239.0.0.0～ Local management multicast addresses are only valid for a
239.255.255.255 specific local scope.
According to the IANA conventions, 224.0.0.0 to 224.0.0.255 are reserved for routing protocols
on the local network. The list of commonly reserved IP multicast addresses is as follows:
Table 18- 2 Reserved IP multicast address list
Scope Meaning
224.0.0.1 The address of all hosts.
224.0.0.2 The address of all multicast routers.
224.0.0.3 Not assigned.
224.0.0.4 DVMRP (Distance Vector Multicast Routing Protocol) router.
224.0.0.5 OSPF（Open Shortest Path First）router.
224.0.0.6 OSPF DR（Open Shortest Path First Designated Router）
224.0.0.7 ST（Shared Tree）router.
224.0.0.8 ST（Shared Tree）host.
224.0.0.9 RIP-2 router.
224.0.0.11 Activity agent.
224.0.0.12 DHCP server / relay agent .
224.0.0.13 All PIM (Protocol Independent Multicast) routers.
224.0.0.14 RSVP (Resource Reservation Protocol) package
224.0.0.15 All CBT (Core-Based Tree) routers.
224.0.0.16 Specific SBM （Sub network Bandwidth Management）.
224.0.0.17 All SBMS.
224.0.0.18 VRRP（Virtual Router Redundancy Protocol）
224.0.0.19-224.0.0.255 Unspecified.
Description ：
Similar to IANA reserving private address segment 10.0.0.0/8 for IP unicast
transmission, IANA also reserved private addresses for IP multicast segments
239.0.0.0 to 239.255.255.255, which belong to the management range address.
Through the management of the management address, users can flexibly define
the range of multicast domains to achieve address isolation between different
multicast domains. This helps to reuse the same multicast address in different
multicast domains without conflict.
18.2.1.1.2 Multicast MAC Address
When the Ethernet transmits unicast IP packets, the destination MAC address uses the
MAC address of the receiver. However, when a multicast packet is transmitted, the
multicast destination is not a specific receiver but a multicast group with unknown
membership. Therefore, a multicast MAC address is used.
Normally, the lowest bit of the highest byte of the unicast MAC address is 0, and the lowest
18-172
bit of the highest byte of the multicast MAC address is 1, as follows:
Figure 18- 2 Multicast address and unicast address comparison
So based on the bit, the data link layer can determine whether the received data frame is a
multicast data frame.
18.2.1.1.3 Mapping relationship between multicast IP address and multicast MAC address
IANA specifies that the upper 24 bits of the multicast MAC address are 0x01005e and the lower
23 bits of the MAC address are the lower 23 bits of the multicast IP address. The mapping
relationship is shown in Figure 18-3.
Figure 18- 3 Mapping relationship between multicast IP address and multicast MAC address
Because the upper 4 bits of multicast IP address are 1110, as multicast ID, while only 23 bits out
of its lower 28 bits are mapped to the MAC address. So, 5-bit information in the IP address will
be lost which directly leads to 32 multicast IP addresses being mapped to the same MAC
address.
As can be seen that the MAC address and IP address of the lower 23-bit is the
corresponding. For example, if the IP module informs the data link layer software to join a
multicast group 224.10.10.10, the data link layer will form a MAC address 01--00--5E - 0A - 0A -
0A. taking the lower 23 of multicast IP address; the upper is as introduced above,
18.2.1.2 Multicast Group Management Protocol IGMP
Multicast Group Management Protocol (IGMP), which runs between hosts and multicast routers,
defines the mechanism for establishing and maintaining multicast memberships between hosts
and multicast routers.
18-173
18.2.1.2.1 Introduction to IGMP
According to the working mechanism, IGMP is divided into two mechanisms: IGMP Proxy and
IGMP Snooping.
Mechanism of IGMP Proxy: The switch establishes the multicast table by intercepting IGMP
packets between the user and the router. The uplink port of the proxy device performs the role of
the host and the downstream port performs the role of the router.
Mechanism of IGMP Snooping: The switch forms the correspondence between the group
members and the switch interfaces by listening to the host reporting the messages to the IGMP
members of the router. The switch forwards the received multicast packets only to the interfaces
with group memberships according to the corresponding relationship.
It can be seen that IGMP proxy functions the same as IGMP snooping, but the mechanism is
different. IGMP Snooping only obtains information by listening to IGMP messages while GMP
proxy intercepts the IGMP request from the end user and processes it, and then forwards it to
the upper router.
The OLT of the G1000 system uses the IGMP proxy protocol to implement multicast. The
specific implementation process is as follows: When the OLT receives the IGMP Join packet, the
OLT starts the IGMP proxy function, intercepting the Join packet, and then authenticating it. After
the authentication passes the following logic judgement are performed: if the applied multicast
group has not existed in the OLT, the OLT will forward an IGMP Join request to the upper-layer
router and set up a multicast forwarding table; if the applied multicast group is already in the OLT
then the user can directly be added to the multicast forwarding table of the OLT, and meanwhile,
the multicast service and the corresponding user table are established and IGMP Join packet is
no longer sent to the upper-layer router.
The ONU of the G1000 system uses the IGMP Snooping mechanism. When receiving the IGMP
Join packet, the ONU receives the multicast forwarding table packet by listening, but the IGMP
packet is transparently transmitted through the ONU.
18.2.1.2.2 IGMP Packet
The IGMP protocol is developed by the host membership protocol. Currently, there are two
versions: IGMPv1 (RFC1112) and IGMPv2 (RFC2326). The host uses IGMP messages to
advertise the host group address of the local multicast router that it wants to receive multicast
traffic. If the host supports IGMPv2, it can also notify the multicast router that it exits a host
group. A multicast router maintains a host group membership table for each port through the
IGMP protocol and periodically probes the members of the host group in the table to determine
whether the host group is alive or not.
IGMP messages are sent in IP packets. Figure 18-1-4 shows the IGMPv1 messages. There are
two message types defined in IGMPv1: Host Member Query and Host Member Report. IGMP
messages are sent in IP packets. Figure 18-1-4 shows the IGMPv1 messages. There are two
message types defined in IGMPv1: Host Member Query and Host Member Report. When a host
wants to receive a multicast group, it sends an IGMP Report message to the local multicast router
to inform the multicast address to be received. After receiving the IGMP Report message, the
multicast router adds the host to the specified multicast group and sends the IGMP Query
message to the multicast address 224.0.0.1 (for all hosts that support multicast) within the set
18-174
period. If the host wants to receive multicast traffic, it must send an IGMP Report message.
Figure 18- 4 IGMPv1 protocol packet
The IGMPv2 messages are shown in Figure 18-5. Unlike IGMPv1, it merges the version field
with the message type field and makes the unused field the Maximum Response Time field. The
message type field of IGMPv2 messages defines four types of messages:
0x11 - member query
0x12 - IGMPv1 member report
0x16 - IGMPv2 member report
0x17 - Exit the host group
Figure 18- 5 IGMPv2 protocol packet
IGMPv2 is forward-compatible with the IGMPv1 protocol, and IGMPv1devices can receive
IGMPv2 packets. IGMPv2 allows a router to perform member query on a specified multicast
group address. A host other than the group does not need to respond. If a host wants to exit, it
can actively send IGMPLeave messages to the router, rather than just as in IGMPv1 passive
exit.
18.2.2 IGMP Multicast Configuration

18.2.2.1 Multicast VLAN Configuration
Table 18- 3 Multicast VLAN configuration

Create multicast VLAN Required.
multicast-vlan vlan-id
and enter VLAN view. By default, all PON ports are add.
Delete multicast VLASN. no multicast-vlan vlan-id Optional.
Required.
Configure the uplink port slotid：slot number
router-port slotid/ port
as router port. port：port number, ranging from
1-16.
Delete the router port of
no router-port slotid/ port Optional.
multicast VLASN.
Configure the router IP Optional.
router-ipv4 ip-address
of multicast VLASN. Be default, 192.168.0.1.
18-175
Configure the proxy host Optional.

host-ipv4 ip-address
IP of multicast VLASN. Be default, 192.168.0.1.
Optional. Reserved by default.
remove：remove vlan tag of igmp
report packet.
protocol-tag （remove
Set VLAN tag mode of reserve：reserve vlan tag of igmp
|reserve|translate
multicast packets. report packet.
new-vid）
translate：translate vlan tag of igmp
report packet into new vid.
new-vid：new vlan id value.
Query the configuration
show multicast-vlan
result of multicast Config view or mvlan view. config
（vlanid|all）
VLASN.
18.2.2.2 Global configuration of OLT multicast
Table 18- 4 Global configuration of OLT multicast

Required
Enable/disable
igmp proxy（enable | Enable: Enables the igmp proxy function.
multicast proxy
disable） Disable: Disable the igmp proxy function
functions.
and enable multicast flooding.
Required.
Channelid: Channel number, in the range of
1 to 1024.
Configure igmp multicast ip-list Startip: Channel start ip address, expressed
multicast channel channelid startip endip as A.B.C.D.
list. vlan-id Endip: End IP address of the channel,
expressed as A.B.C.D.
Vlan-id: Multicast VLAN ID corresponding to
the channel, in the range of <1-4094>.
Delete igmp
no multicast ip-list (all
multicast channel Optional.
|channelid)
list.
Query configuration
PRMs of igmp show igmp-proxy Optional.
proxy.
Query igmp
multicast channel show multicast ip-list Optional.
list.
Display the
multicast address
show igmp addr Optional.
table of current
system.
18-176
18.2.2.3 Igmp proxy protocol parameters configuration
Table 18- 5 igmp proxy protocol parameter configuration

Set the interval of
igmp proxy Optional,
the igmp proxy
query-interval Set the interval at which the igmp proxy sends
sending query
interval-time query packets. In the range of 1s to 1000s.
packets.
Optional.
Restore the interval
After the igmp proxy receives a leave packet
for sending query no igmp proxy
from a member of the group, the number of
packets to the query interval
query packets sent to the specified group is
default.
125s by default.
Configure the igmp
Optional.
proxy to allow the igmp proxy
Configure the interval response-time at which
host to query the query-response
igmp proxy allows the host to respond to the
interval between response-time
query packets, in the range of 1s to 25s.
packets.
Restore the default
Optional.
interval of allowing
no igmp proxy Configure the interval as 10s at which igmp
the host to query
query response proxy allows the host to respond to the query
the corresponding
packets.
packets.
Optional.
Configure the Configure the number count of query packets
igmp proxy
number of query that the igmp proxy sends out to a specific
lastmember-query
packets sent to a group after receiving a leave packet from a
count count
specific group. member of the group. The value ranges from
1 to 5.
Optional.
Restore the number
no igmp proxy After the igmp proxy receives a leave packet
of query packets
lastmember-query from a member of a group, the number of query
sent to a specific
count packets sent to the specified group is 2 by
group to the default.
default.
Optional.
Set the interval for
igmp proxy Configure the interval last-interval for query
sending query
lastmember-query packets sent to the specific group after igmp
packets to a
interval last-interval proxy receives a leave packet from a member
specific group.
of a group. The value ranges from 1s to 3s.
Restore the interval Optional.
no igmp proxy
for query packets After the igmp proxy receives a leave packet
lastmember-query
sent to a specific from a member of a group, the interval for the
interval
group to the default. query packets sent to the specific group is 1s.
Configure the igmp proxy Optional.
robust variable of robust-variant Configure the robust variable of igmp proxy
gimp proxy. robust-variant as robust-variant， in the range of 1 to 5.
Restore the robust no igmp proxy Optional.
18-177
variable of the igmp robust-variant Configure the robust variable of igmp proxy
proxy to the default. as 2.
18.2.2.4 Basic configuration for ONU MC
Table 18- 6 Basic configuration for ONU multicast

Enter ONU view. interface onu interface-num -
Required.
Set the multicast mode for ONU,
Set the multicast multicast mode ctc：igmp controllable MC mode;
mode for ONU. (snooping|ctc|disable)
snooping：igmp-snooping mode;
disable：MC flooding.
Optional.
Set a fast leave
fast leave (enable|disable) enable：enable fast leave function;
mode.
disable：disable fast leave function
Required.
Configure MC vlan port multicast-vlan (all | uniid)
The command is applied only in
on ONU ports. (add | Delete)vlan-id
snooping mode.
Optional.
Configure the max multicast-group-num：the max MC
port multicast-group-num (all |
MC number on number, in the range of 0-80, 0
uniid) multicast-group-num
ONU ports. indicating
unlimited.multicast-group-num
Configure the MC
port multicast-tag-strip (all |
tag stripping status Optional.
uniid) (no-strip| strip)
on ONU ports.
Configure the MC
port multicast-tag-strip (uniid|all)
tag conversion
translation (add|del) old-vid
status on ONU
new-vid
ports.
Optional.
Display igmp mode. show igmp mode Query current igmp configuration
mode.
Query the fast
show fast leave Optional.
leave mode.
Display the MC Optional.
show port multicast-vlan (all |
Vlan list on ONU Display the MC Vlan list on ONU
uniid)
ports. ports.
Display the max
show port multicast-group-num
MC numbers on Optional.
(all | uniid)
ONU ports.
Display the port MC
show port multicast-tag-strip
stripping operation Optional.
(all | uniid)
status of the ONU.
18-178
18.2.2.5 MC profile configuration
Table 18- 7 MC profile configuration
Required.
profile-id: ONU MC
Create MC configuration
multicast profile-cfg profile-id configuration profile index,
profile.
in the range of 2-32.(Profile
ID 1 as the default profile)
Delete MC configuration no multicast profile-cfg (all Optional.
profile. |profile-id) The same range as above.
Required, and applied in
“pon” view.
If templateid is 1, ONU MC
multicast attach profile-cfg
Apply MC configuration configuration profile is
templateid (onuid-start|loid)
profile. restored to the default; if
[onuid-end]
templateid is 2-32, the
corresponding profile is
applied.
Query MC configuration show multicast profile-cfg
-
profile. （profile-id|all）
18.2.3 IGMP Multicast Configuration Example

18.2.3.1 IGMP Snooping MC configuration example
Configure the igmp proxy (OLT) + igmp snooping (ONU) MC function.
To implement the igmp proxy MC function on the G1000, the igmp proxy on the central office
device and igmp snooping on the ONU should be enabled. (ONU is the default snooping)
Connect the router port on G1000 to the router or MC server, enable the MC routing protocol on
the router, connect the ONU port with the user’s PC and start igmp client on the PC.
18-179
Figure 18- 6 igmp snooping MC networking topology
18.2.3.1.3 Configuration procedures
Enable igmp proxy function on OLT:

G1000(config)# igmp proxy enable
Create 4 MC VLAN, namely 4001～4004 (they can’t be created in batches):
Create 4 MC channels, respectively numbered 1—4, and the corresponding vid are 4001 ～
4004：
G1000(config)#multicast ip-list 1 224.1.1.1 224.1.1.1 4001
G1000(config)# multicast ip-list 1 224.1.1.2 224.1.1.2 4002
Enter vlan4001, and configure uplink port 1/1 as routing port:
G1000(config)#multicast-vlan 4001
18-180
G1000(config-mvlan-4001)#router-port 1/1
PON port 2/2 has been added by the default when MC VLAN was created, so don’t add it
manually.
Configure igmp mode of ONU as igmp-snooping：
G1000(config-if-ont-2/2/13)# multicast mode snooping
Configure ONU MC vlan:
G1000(config-if-ont-2/2/13)#port multicast-vlan 1 add 4001
Configure the downstream MC data of the ONU as tag-stripped (optional):
G1000(config-if-ont-2/2/13)#port multicast-tag-strip 1 strip
Desc:
 The mode set by igmp mode only refers to the MC mode of G1000 and the default mode
of ONU is igmp snooping.
 After OLT receives the igmp join packet sent by the downlink ONU it will automatically add
the PON port connecting with the ONU to MC Vlan.
 By the default ONU is igmp snooping. Command igmp mode is used to switch between
igmp snooping and igmp ctc.
19Performance Statistics Configuration Management

19.1 Introduction to performance statistics configuration
This device can count and record the data received / sent by each interface of OLT and
ONU. Users can view the network data statistics information of each interface of OLT and
ONU through command line and network management, which is convenient for network
and equipment optimization and problem diagnosis.
Performance statistics include: real-time performance statistics, current 15-minute
performance statistics, historical 15-minute performance statistics, current 24-hour
performance statistics, and historical 24-hour performance statistics query.
The performance statistics of the collection object will be counted from the moment of
enabling. Turning off collection object performance collection triggers will clear real-time
performance cumulative values and historical performance statistics.
 Real-time performance statistics：
The statistics value from the system startup to the current moment is accumulated after
19-181
being enabled.
 Current 15-minute performance statistics：
In the current 15 minutes (started after the last 15 minutes have been counted), all
accumulated values from the beginning to the current.
When the current 15-minute statistical value is displayed, the total time of the statistical
sampling is also displayed, in seconds. For example, if the statistics period is collected
twice, each time is 30s, then the total time is 60s.
 Historical 15-minute performance statistics：
After the current 15 minutes arrive, its statistics enter the historical 15-minute performance
statistics and start a new current 15-minute statistics.
There are 96 historical 15-minute performance statistics. The first historical 15-minute
statistics is the latest historical performance statistics, and the 96th statistics is the oldest.
After the 96 are filled, when the 97th arrives, the 96th is deleted, 1-95 items are shifted back,
and then inserted as the first one. Historical 24-hour statistics are handled the same.
 Current 24-hour performance statistics
In the current 24 hours, all accumulated values from the beginning to the current.
 Historical 24-hour performance statistics
After the current 24 hours arrive, its statistics enter the historical 24-hour performance
statistics. There are 7 historical 24-hour performance statistics. The first historical 24-hour
statistic is the latest historical performance statistics, and the seventh is the oldest statistics.
Table 19- 1 OLT port performance statistics
No. Item
1 Downstream bytes
2 Upstream bytes
3 Number of downlink data packets
4 Number of upstream data packets
5 Number of downlink broadcast packets
6 Number of upstream broadcast packets
7 Number of downstream multicast packets
8 Number of upstream multicast packets
9 Number of downlink CRC error packets
10 Number of upstream CRC error packets
11 Number of downlink ultra short packets
12 Number of uplink ultra short packets
13 Number of downlink extra long packets
14 Number of uplink super long packets
15 Downward Fragment Number
16 Upstream Fragment Number
17 Downstream Jabber number
18 Upstream Jabber number
Number of packets with a downstream length of 64
19 bytes
20 Number of packets with an upstream length of 64 bytes
Number of packets with a downstream length of 65 to
21 127 bytes
Number of packets with an upstream length of 65 to
22 127 bytes
23 Number of packets with a downstream length of 128 to
19-182
255 bytes
24 255 bytes
25 511 bytes
26 511 bytes
27 1023 bytes
28 1023 bytes
Number of packets with a downstream length of 1024
29 to 1518 bytes
30 1518 bytes
31 Number of downstream dropped packets
32 Number of upstream dropped packets
33 Number of downlink error packets
34 Number of upstream error packets
35 Downlink rate
36 Upstream rate
Table 19- 2 onu port performance statistics
No. Item
1 Number of bytes received on the port
2 Number of received packets on the port
3 Number of unicast packets received on the port
4 Number of multicast packets received by the port
5 Number of broadcast packets received by the port
6 Number of discarded packets received on the port
7 Number of received error packets on the port
8 Number of ultra short packets received by the port
9 Number of oversized packets received by the port
10 Port receives unknown protocol packets
11 Number of CRC error packets received by the port
12 Number of bytes sent by the port
13 Number of packets sent by the port
14 Number of unicast packets sent by the port
15 Number of multicast packets sent by the port
16 Number of broadcast packets sent by the port
17 Port receive rate
18 Port send rate
19-183
19.2 Performance statistics configuration

19.2.1 OLT performance statistics configuration
Table 19- 3 OLT performance enable / disable / clear / display
Operation Command Description

Enter OLT port configure terminal
-
view int olt sloid/portid
Turn performance statistics on
Enable or off
performance perf (enable| disable)
slotid：Slot number
switch
portid：Port number
Clear current and Optional.
historical This command is valid only
perf clear
performance when the performance switch
statistics is on.
Performance data can only be
Query real-time
show perf current displayed when the
statistics
performance switch is on.
Query the current Performance data can only be
15-minute sex show perf current15 displayed when the
statistics performance switch is on.
Query historical
performance Index ： Index number ， Value
Show perf history15index
statistics for 15 range: 1-96
minutes.
Query the current
Performance data can only be
24-hour
show perf current24 displayed when the
performance
performance switch is on.
statistics
Query historical
24-hour Index ： Index number ， Value
show perf history24index
performance range: 1-7
statistics
Query
performance Display port performance
statistics show perf config statistics configuration
information
Exit port view and
exit
enter config view
Query the
performance
show perf enable olt all
statistics switch of
all ports of the OLT
19-184
19.2.2 onu performance statistics configuration
Table 19- 4 onu UNI and gemport port performance enable/disable/clear/ display

Enter onu view interface onu interface-num
Enable or disable the onu port
Enable onu port performance statistics switch.
port portid：Port number
performance
perf(enable|disable)(portid|all)
switch all：Querying the performance
of all ports
Clear current Optional. Clear current and
performance port perf clear (portid|all) historical statistics, not
statistics real-time statistics.
Query onu port
performance show port perf config
statistics (portid|all)
configuration
Query onu port
real-time show port perf
performance current(portid|all)
statistics
Query the current
15-minute show port perf current15
statistics of the (portid|all)
onu port
Query onu port
show port perf index ： Index number ， Value
history for 15
history15(portid|all)index range: 1-96
minutes
Query the current
24-hour data show port perf
statistics of the current24(portid|all)
onu port
Query onu port
show port perf history24 index ： Index number ， Value
history 24-hour
(portid|all)index range: 1-7
data statistics
Exit port view and
exit
enter config view
Query the
performance
statistics switch of show perf enable onu all
all onu ports of the
whole machine
Turn onu gemport performance
Enable onu statistics on or off.
gemport
gemport gemportid：Port number，Value
perf(enable|disable)( gemportid
performance range: 1-16
|all)
switch all：Querying the performance
of all ports
Clear current
Optional. Clear current and
gemport
gemport perf clear (portid|all) historical statistics, not
performance
real-time statistics.
statistics
19-185
Query onu
gemport
show gemport perf config
performance
(gemport id|all)
statistics
configuration
Query onu
gemport real-time show gemport perf
performance current(gemport id|all)
statistics
Query onu
gemport's current show gemport perf current15
15-minute (gemport id|all)
statistics
Query onu
show gemport perf index ： Index number ， Value
gemport history 15
history15(gemport id|all)index range: 1-96
minutes statistics
Query onu
show gemport perf
gemport's current
current24(gemport id|all)
24-hour statistics
Query onu
show gemport perf history24 index ： Index number ， Value
gemport historical
(gemport id|all)index range: 1-7
24-hour statistics
19.3 Performance statistics configuration example

19.3.1 Networking requirements
Enable the performance switch to query the performance data of GE1 / 1 and onu2 / 1/1
port 1.
19.3.2 Network diagram
Figure 19- 1 Performance configuration example diagram
19.3.3 Configuration steps
OLT performance statistics configuration example：

$ Enable performance switch
G1000(config-if-gigabit-ethernet-1/1)#perf enable
19-186
$ Display the current 15-minute performance statistics of PON 1/1

G1000(config-if-gigabit-ethernet-1/1)#show perf current15
Performance : enable
Location : 1/1
Lapse Time : 150 s
DS DropEvents : 500
DS Octets : 0
DS UcFrames : 0
DS BcFrames : 0
DS McFrames : 0
DS CrcErrFrames : 0
DS UnderSizeFrames : 0
DS OverSizeFrames : 0
DS FragmentsFrames : 0
DS JabbersFrames : 0
DS 64OctetsFrames : 0
DS ErrorPkt : 0
US DropEvents : 0
US Octets : 0
US UcFrames : 0
US BcFrames : 0
US McFrames : 0
US CrcErrFrames : 0
US UnderSizeFrames : 0
US OverSizeFrames : 0
US FragmentsFrames : 0
US JabbersFrames : 0
US 64OctetsFrames : 0
US ErrorPkt : 0
Onu performance statistics configuration example：
$ Enable the performance statistics switch of onu port 1
G1000(config-if-ont-2/8/1)#port perf enable 1
$ Query performance statistics of onu 2/8/1 port 1
G1000(config-if-ont-2/8/1)#show port perf current 1
Perf State :enable
Perf Lapse Time :0 s
Port Id : 1
DS DropEvents : 0
DS TotalOctets : 0
DS UcFrames : 0
DS BcFrames : 0
DS McFrames : 0
DS CrcErrFrames : 0
DS UnderSizeFrames : 0
DS OverSizeFrames : 0
19-187
DS FragmentsFrames : 0
DS JabbersFrames : 0
DS 65to127OctetsFrames : 0
DS DiscardFrames : 0
DS ErrorFrames : 0
PortStatusChangeTimes : 0
US DropEvents : 0
US TotalOctets : 0
US UcFrames : 0
US BcFrames : 0
US McFrames : 0
US CrcErrFrames : 0
US UnderSizeFrames : 0
US OverSizeFrames : 0
US FragmentsFrames : 0
US JabbersFrames : 0
US 65to127OctetsFrames : 0
US DiscardFrames : 0
US ErrorFrames : 0
$ Clear onu port 1 performance statistics
G1000(config-if-ont-2/8/1)#port perf clear 1
20 Alarm Configuration Management

20.1 Introduction to alarm configuration
After the alarm is enabled, an error or an important operation performed on the system
triggers the OLT alarm event. The OLT stores the alarm information in the alarm buffer. You
can view the current system activity alarms and historical alarms by using the show alarm
active or show alarm history command. All alarm messages can be sent to the server by
snmp traps, or they can be blocked.
Alarms are notifications generated when the system detects a fault, including fault alarms
and recovery alarms. A fault alarm persists after it is generated until the fault is repaired and
the alarm is cleared. Not every alarm is cleared.
Events are notifications that are generated under the normal operating state of the system
and need to actively prompt the user, including running events and security events.
The difference between an event and an alarm is that an alarm is a notification that is
reported under abnormal conditions of the system or may cause an abnormal situation, and
an event is a notification that is reported under normal operating conditions of the system.
In this context, unless specifically distinguished, the alarms mentioned in this article include
alarms and events.
The alarm module is a sub-module of the log module. Under the default configuration, only
20-188
alarms with severity levels such as system restart can be automatically printed on the user
interface. If you want events such as onu registration and onu authorization success to be
printed on the user interface, you need to configure the alarm module in the log: unblock
and set the output mode, for example:
no log mask alarm all，Cancel all level alarms of the alarm module;
log output alarm all tty，Configure all alarms of the alarm module to be output to the tty, that
is, the user interface.
20.2 Alarm configuration operation
Table 20- 1 Alarm configuration

Set the level of
alarms and events. alarm alarm-id
Enable or disable （critical|major|minor|warning|defaul Optional
alarms and events alarm-id
t|enable|disable）
according to the
alarm ID.
Enable or disable
alarm level
alarms and events
(critical|major|minor|warning) Optional
according to the
(enable|disable)
alarm level.
slotid ： Set whether to
block alarms and
events according to the
slot number. The value
range is <1-2>.
portid ： Set whether to
block alarms and
Enable or disable port number. The value
alarms and events alarm location slotid [portid] [onuid] range is <1-16>.
according to the [uniid] (enable | disable) onuid ： Set whether to
slot port position. block alarms and
onu id. The value range
is <1-64>.
uniid ： Set whether to
block alarms and
onu port number. The
value range is <1-32>.
Enable or disable alarm type
alarms and events (communication|service|process|equ
Optional
according to alarm ipment|environment|tca|notify)
types. (enable|disable)
Configure SNMP
snmp community (read|write)
Read and Write Optional
community
Community
20-189
community：Community
name. The value is
usually public or
private.
v1：The snmp version
is the first version.
v2：The snmp version
is the second version.
Set snmp server snmp trap server community (v1| v3：The snmp version
parameters for v2c|v3)(ipv4|ipv6)(ip-address is the third version.
alarm reporting |ipv6-address) ip-address ： The ip
address of the snmp
trap server.It is usually
the IP address of the
network management
server,expressed as
A.B.C.D.
ipv6-address ： ipv6
address of snmp trap
server.
Delete snmp
no snmp trap server(ipv4|ipv6)
server parameters Optional
(ip-address |ipv6-address)
for alarm reporting
Clear active alarm Optional. Clears all
no alarm active all
records active alarms.
Clear all historical
no alarm history all Optional
alarm records
Show all active
show alarm active Optional
alarm records
Display the mask
information of show alarm config Optional
alarms and events.
show alarm history all
show alarm history id alarmid
show alarm history level（critical| Optional.
major| minor| warning） You can query the
Display historical show alarm history time from year corresponding
alarm records month day hour minute second to year historical alarm records
month day hour minute second according to different
show alarm history type conditions.
(communication|service|process
|equipment | environment |notify）
Displays whether
alarms or events
of various levels show alarm config level Optional
are output to the
terminal.
Display a list of
alarm and event show alarmid info ( id alarmid|all) Optional
information
20-190
slotid ： Set whether to

block alarms and
slot number. The value
range is <1-2>.
portid ： Set whether to
block alarms and
Display historical
port number. The value
alarms and event
show alarm history location slotid range is <1-16>.
records generated
[portid] [onuid] [uniid] onuid ： Set whether to
at specified
locations. block alarms and
onu id. The value range
is <1-64>.
uniid ： Set whether to
block alarms and
onu port number. The
value range is <1-32>.
Display the snmp
server information
show snmp trap server Optional
reported by the
alarm.
Display all TCA
historical alarms show alarm tca Optional
and events.
Enables the output
of alarms and
show alarm config type Optional
events to the
terminal by type.
Display the
relevant settings of
historical alarm show alarm config location Optional
generated at the
designated place
Display alarm
output related show alarm output config Optional
settings
Delete all TCA
historical alarms no alarm tca all Optional
and events
20.3 Alarm configuration example

20.3.1 Networking requirements
 Configure the SNMP server and shield all the alarm information of PON2 / 1.
 Connect the OLT and the snmp server (both in-band and out-of-band), and configure
the IP address of the OLT and the IP address of the snmp server to the same network
segment.
20-191
20.3.2 Network diagram
Figure 20- 1 Topology diagram of alarm configuration
20.3.3 Configuration steps
$ Configure the SNMP community attribute as public, version number v2c, and server
address as 192.168.7.111：
G1000(config)# snmp trap server public v2c ipv4 192.168.7.111
$ Shield all alarm TRAP of PON 2/1：
G1000(config)# alarm location 2 1 disable
21 Network Management Configuration

21.1 Introduction to Network Management Mode
G1000 OLT equipment supports access control with three management methods at the
same time:
21-192
Table 21- 1 G1000 Summary of network management methods
Management
Protocol Description
style
Serial ports support CLI
Console port control CLI
management mode
Support CLI mode and Snmp
network management mode
for Telnet at the same time
Through the snmp
CLI(telnet) management, you can
In-band management
SNMP connect to the network
management server and
manage the G1000 through
the graphical network
management.
Out-of-band supports both
Telnet CLI mode and Snmp
network management mode.
Through the snmp
Out-of-band CLI(telnet) management, you can
management SNMP connect to the network
management server and
manage the G1000 through
the graphical network
management.
Out-of-band management mainly provides a management interface through a dedicated
physical channel. On G1000 devices, management and maintenance are performed
through the management interface on SCUF. Generally, it can be directly connected
through a PC or through a network management channel (a separate management network)
to implement network management, separate network management data from business
data, and establish independent channels for network management data. In this channel,
only important management data, sensitive statistical information, and real-time billing
information are transmitted. Separation of network management data from service data can
improve the efficiency and reliability of network management and also improve the security
of network management data.
For smaller network structures, in-band management can be used. In-band management
enables network management data and service data in the network to be transmitted on the
same physical link. When there is a lot of management data (including SNMP data, Netflow
data, Radius data, accounting data, etc.), it may affect the performance of the entire
network, and business data flows may also affect management data flows; However, for
smaller networks, there is less traffic for management data and the performance of the
entire network is not significantly affected. In-band management can be used. The G1000's
in-band network management channel is mainly implemented through the uplink port. In
general, in order to maintain security, a dedicated VLAN is required as a management
channel to isolate it from other business channels.
The G1000 supports dual IPv4 and IPv6 protocol stacks, and can manage devices in both
ways.
Description：
The in-band IP address and out-of-band IP address of the device cannot be configured on
the same network segment.
Table 21- 2 Network Management Related Configuration Commands
21-193
first-id、 last-id：The range of

VLANs to be created, ranging
from 1 to 4094.
Create and enter vlan first-id [last-id]
vlan view no vlan first-id [last-id] If last-id is not specified,
create the VLAN first-id and
enter its view or directly enter
the existing VLAN view.
ip-address ： In-band
management interface IP
Configure in-band inband ipv4 ip-address address, dotted decimal
management IPv4 netmask format
addresses netmask：The corresponding
subnet mask, in dotted
decimal format
Ipv6-address ： IPv6 address
of in-band management
Configure in-band
interface ， a hexadecimal
management IPV6 inband ipv6 ipv6-addressprefix
address number separated by a
colonprefix ： IPv6 address
network prefix
Delete in-band
management IP no inband (ipv4|ipv6) Optional
address
Ip-address ： The gateway
Configure gateway gatewayipv4ip-address
address of this system is
IPv4 address
expressed as A.B.C.D.
ipv6-address ： The gateway
Configure gateway
gatewayipv6 ipv6-address address of this system,
IPv6 address
expressed as 2001 :: 1.
Configure ipaddress ： IP address,
outband ipv4ip-address
out-of-band expressed as A.B.C.D.
netmask
management IPv4 netmask ： Subnet mask,
addresses expressed as A.B.C.D.
Ipv6-address ： IPv6 address
Configure of in-band management
out-of-band outband interface ， a hexadecimal
management IPv6 ipv6ipv6-addressprefix number separated by a colon
addresses prefix：IPv6 address network
prefix
Display in-band
management IP show inband-info enable view, config view
address
Display gateway IP
show gateway-info Config view
address
view 、 enable view 、 config
view
Display out-of-band
Outband interface link status:
management IP show outband-info
address DOWN means not
connected, and UP means
connected.
21-194
21.2 Management Network Diagram
Figure 21- 1 Management Network Diagram
21.3 Default gateway configuration
When the G1000 OLT device and the gateway server are not on the same network segment,
that is, when our equipment maintenance needs to cross network segments, we need to set
up a gateway. The role of the default gateway is that when the G1000 device is not on a
network segment, all data is forwarded to the default gateway by default, and the default
gateway forwards it again.
$ Configure the gateway：
G1000(config)# gateway ipv4 192.168.85.99
G1000(config)# gateway ipv6 2001::e1:2:1:1:2
G1000(config)# show gateway-info
Gateway ipv4 address is:192.168.85.99.
Gateway ipv6 address is: 2001::e1:2:1:1:2.
21.4 Out-of-band management configuration
The configuration of out-of-band management only needs to configure the IP address and
subnet mask.
The configuration method of the out-of-band management IP address is as follows:
G1000(config)# outband ipv4 192.168.8.100 255.255.255.0
G1000(config)# outband ipv6 2001::a:b:c:100 64
G1000(config)# show outband-info
Outband ipv4 address: 192.168.8.100 , netmask is: 255.255.255.0.
Outband ipv6 address: 2001::a:b:c:100/64.
Outband mac address:00:1a:69:01:3d:2b.
21-195
Outband interface link status: UP.
Description：
After the out-of-band management IP address is configured, you can connect the
management port of the G1000 to the PC through a directly connected network cable, and
check whether the network port works normally by pinging.
21.5 In-band management configuration
The G1000 device provides on-band management through the onu of the uplink port or the
PON port. The configuration requires the configuration of the IP address, subnet mask, and
VLAN.
Step 1：Create a VLAN for in-band management to 1000
Step 2 ： Add uplink port 1/4 to VLAN 1000, and VLAN is untag mode. The port pvid is
changed to 1000.
G1000(config-if-gigabit-ethernet-1/4)#show port vlan
Port vlan-type: hybrid
PVID: 1000
Outer TPID : 0x8100
Inner TPID : 0x8100
Tagged VLAN ID:
none
Untagged VLAN ID:
1,1000
Step 3：Configure the in-band managed IPv4 address as 192.168.9.100 and the mask as
255.255.255.0
Configure the in-band managed IPv6 address to 2001:: e1: 2: 1: 1: 1 and the prefix to 64
G1000(config-vlan-1000)#inband ipv4 192.168.9.100 255.255.255.0
G1000(config-vlan-1000)#inband ipv62001::e1:2:1:1:1 64
G1000(config)# show inband-info
VLAN interface : 1000
IPV4 address : 192.168.9.100
IPV4 netmask : 255.255.255.0
IPV6 address : 2001::e1:2:1:1:1
IPV6 prefix : 64
Mac address : 08:00:3e:33:02:02
Description：
The VLAN of the in-band management channel must be distinguished from the service
VLAN to prevent the service from broadcasting data to the CPU of the SCU；
21-196
22 L3 Configuration Management
22.1 Overview of IP routing
In the IP network scenario, there are situations where the two communicating parties are
not on the same network segment. In this case, routing is required to solve the problem that
the two parties cannot communicate with each other.
22.1.1 Routing and routing tables
A router is used for routing in the Internet. The router selects an appropriate route (through
a network) according to the destination address of the received message, and transmits the
message to the next router. The last router in the path is responsible for sending the packet
to the destination host.
The key to routers forwarding packets is the routing table. Each router maintains a routing
table, and each routing entry in the table indicates which physical port of the router the
packet should be sent to a subnet or a host. Then you can reach the next router in the path,
or you can pass it to the destination host in the directly connected network without passing
through other routers.
 According to different sources, the routes in the routing table can be divided into the
following three categories:
 Routes discovered by link layer protocols (also known as interface routes or direct
routes)
 Manually configured static routes.
 Routes discovered by dynamic routing protocols.
22.1.2 Static and dynamic routing
Static routing is easy to configure and has low system requirements. It is suitable for small
networks with simple and stable topology. The disadvantage is that it cannot automatically
adapt to changes in the network topology. When the network topology changes,you need to
manually reconfigure static routes.
The dynamic routing protocol has its own routing algorithm, which can automatically adapt
to changes in the network topology and is suitable for a network topology with a certain
scale. The disadvantage is that the configuration is more complicated, the system
requirements are higher than static routing, and it will occupy a certain amount of network
resources.
G1000 devices currently support IPv4 and IPv6 static routing protocols.
22.1.3 Layer 3 interface introduction
The Layer 3 interface of the G1000 is not a physical port but a virtual interface implemented
based on a VLAN. After an interface IP address is configured in the VLAN view, this VLAN
becomes a Layer 3 interface.
The G1000 supports a total of 50 Layer 3 interfaces. In addition to the in-band and
out-of-band interfaces, you can configure 48 Layer 3 interfaces.
22-197
Currently, a primary Layer 3 interface can be configured with one primary IPv4 address and
four secondary IPv4 addresses. When the primary ipv4 address does not exist, the
secondary ipv4 address cannot be created. The dhcp server function can only take effect
using the primary IP. The arp proxy and dhcp relay can use the primary and secondary IP
addresses. After these switches are enabled, the secondary IPv4 address cannot be added.
You must disable these switches to add the secondary IP address.
22.2 Intercommunication with L3 in one PON port

22.2.1 Introduction
In GPON system, the data under the same PON port is naturally isolated, In the actual
networking application process, services under the same PON interface need to be able to
communicate with each other. This requires that the system must provide a method to
complete the problem of service interconnection with the same PON interface.
G1000 uses two methods to achieve data communication under the same PON port, The
first method is P2P. For details, see section 8.2. P2P belongs to two-layer message
interworking. After the switch is turned on, all layer-2 messages under the same PON port
can communicate. Therefore, it cannot isolate the broadcast domain and has certain
security risks.
The second method is implemented using an arp proxy or an nd proxy. The arp proxy
implements the interworking of IPv4 packets, and the nd proxy implements the interworking
of IPv6 packets. Using this method, it is possible to implement intercommunication between
Layer 3 packets on the same network segment under the same PON port. Layer 3 packets
under the same PON port use the VLAN layer 3 interface as a proxy to forward packets.
The configuration method is to enable the arp proxy switch or the nd proxy switch on the
layer 3 interface. Because Layer 3 packets can isolate the broadcast domain, they are more
secure in use than P2P.
22.2.2 arp proxy and nd proxy configuration
Table 22- 1

Enable/disable L3
l3-interface（enable|disable） Required
interface
Optional
Configure routing l3-interface age-time seconds ： Time value,
table update time （default|seconds） ranging from 10-3600,
default is 600s
Query L3 interface
show l3-interface
configuration
Enter vlan view vlan start-id [end-id]
22-198
Required
ipv4-address：Configure the
primary and secondary IP
addresses of the L3
interface. When configuring
an alternate address, you
need to enter the slave
Configure the IPv4 l3-interface ipv4ipv4-address
keyword after the IP
address and mask mask[slave]
address.
of the L3 interface
mask：Configure the subnet
mask of the IPv3 address of
the L3 interface.
One Layer 3 interface can
be configured with one
active ipv4 address and four
standby ipv4 addresses.
Configure the IPv6 Required
address and prefix l3-interface ipv6ipv6-address Ipv6-address ： ipv6 address
length of the L3 ipv6-prefix value
interface ipv6-prefix：Prefix length
Enable arp proxy l3-interface arp-proxy
Required
for IPv4 interface (enable|disable)
Enable the nd
l3-interface nd-proxy
proxy function of Required
(enable|disable)
the IPv6 interface
Note two points:
It is not allowed to delete the
primary IP when the
Delete VLAN ipv4 no l3-interface secondary IP exists. The arp
L3 interface ip ipv4(ipv4-address|all) proxy, dhcp server, and
dhcp relay are not allowed
to delete the interface IP
address.
When the nd proxy switch is
Delete VLAN
no l3-interface ipv6 enabled, the interface IP
ipv6L3 interface ip
cannot be deleted.
Querying L3
Interface
Display both IPv4 and IPv6
Configuration show vlan l3-interface
configuration information.
Information for a
VLAN
22.2.3 arp proxy and nd proxy examples

Connect 4 onu under PON2 / 1. The IPs of PC1 and PC2 connected to onu 2/1/1 and onu2 /
1/2 are 192.168.15.2 and 192.168.15.3, the mask is 255.255.255.0, and the gateway is
192.168.15.1. The IPs of PC3 and PC4 connected to onu2 / 1/3 and onu2 / 1/4 are 2001 :: 2
and 2001 :: 3, the gateway is 2001 :: 1, and the prefix length is 64 bits. PC1 and PC2 can
ping each other, and PC3 and PC4 can ping each other.
22-199
22.2.3.2 Network diagram
Figure 22- 1 arp proxy
$ Set the L3 global switch to enable：

G1000(config)# l3-interface enable
$ Configure the primary IPv4 address and mask of L3 interface vlan101 and enable the arp
proxy function：
G1000(config-vlan-101)#l3-interface ipv4 192.168.15.1 255.255.255.0
G1000(config-vlan-101)#l3-interface arp-proxy enable
$ Configure the IPv3 address and prefix length of L3 interface vlan101, and enable the nd
proxy：
G1000(config-vlan-101)#l3-interface ipv6 2001::1 64
G1000(config-vlan-101)#l3-interface nd-proxy enable
$ Query the configuration of interface vlan101：
G1000(config-vlan-101)#show vlan l3-interface
Vlan interface : 101

IPv4 address/netmask(master) : 192.168.15.1/24
IPv4 address/netmask(slave) : none
IPv6 address : 2001::1
IPv6 prefix : 64
ARP proxy : enable
ND proxy : enable
DHCP relay : disable
DHCP relay server(master) : none
DHCP relay server(slave) : none
DHCP server : disable
$ Configure the VLAN mode of pon2 / 1 so that the packets entering the pon interface are
tagged with tag101, and the packets exiting the pon interface are tagged with tag101：
22-200
G1000(config-if-gpon-2/1)#port type hybrid

G1000(config-if-gpon-2/1)#port pvid 101
G1000(config-if-gpon-2/1)#port vlan 101 untagged
22.3 Static route configuration

22.3.1 Introduction to static routing
A static route is a special route that is manually configured by the administrator. On a

network with a simple network structure, you only need to configure static routes to
implement network interworking. Properly setting and using static routes can improve
network performance and guarantee bandwidth for important network applications. The
disadvantage is that it cannot automatically adapt to changes in the network topology.
When the network topology changes, routes may become unreachable, resulting in network
interruption. At this time, the network administrator needs to manually modify the
configuration of static routes.
G1000 devices support IPv4 and IPv6 static routes. For details, see the next section.
22.3.2 Static Route Configuration

22.3.2.1 L3 Interface Configuration
Table 22- 2 L3 interface configuration

Enable / disable
l3-interface（enable|disable） Required
L3 interface
Enter vlan view vlan start-id [end-id]
Required
ipv4-address ： Configure
the primary and secondary
IP addresses of the L3
interface. When
configuring an alternate
address, you need to enter
the slave keyword after the
Configure the IPv4 l3-interface ipv4ipv4-address
IP address.
address and mask mask[slave]
of the L3 interface mask ： Configure the
subnet mask of the IPv3
address of the L3
interface.
One Layer 3 interface can
be configured with one
primary IPv4 address and
four secondary IPv4
addresses.
22-201
Configure the IPv6 Required

address and prefix l3-interface ipv6ipv6-address Ipv6-address ： ipv6
length of the L3 ipv6-prefix address value，ipv6-prefix：
interface Prefix length
Note two points:
It is not allowed to delete
the primary IP when the
Delete VLAN ipv4 no l3-interface secondary IP exists. The
L3 interface ip ipv4(ipv4-address|all) arp proxy, dhcp server,
and dhcp relay are not
allowed to delete the
interface IP address.
When the nd proxy switch
Delete VLAN
no l3-interface ipv6 is enabled, the interface IP
ipv6L3 interface ip
cannot be deleted.
Querying L3
Interface Display both IPv4 and
Configuration show vlan l3-interface IPv6 configuration
Information for a information.
VLAN
22.3.2.2 Static Route Configuration
Table 22- 3 Static Route Configuration

Required
Ipv4-address: Destination
network ip address
ipv4-mask: Destination network
subnet mask
iproute-static ipv4-address
Add an IPv4 static next-ipv4-address: Next hop IP
ipv4-masknexthop-ipnext-ipv4
routing entry address. The next hop address
-address
must be on the same network
segment as the IP address of the
L3 interface, and the L3 interface
address must be created
successfully.
Required
Ipv6-address: Destination
network ip address
Ipv6-mask: Destination network
subnet mask
route-static ipv6
Add IPv6 static next-ipv6-address: Next hop IP
ipv6-addressipv6-prefixnextho
routing entries address. The next hop address
p-ip next-ipv6-address
must be on the same network
segment as the IP address of the
L3 interface, and the L3 interface
address must be created
successfully.
22-202
Delete ipv4 static no route-static ipv4

routing entries (ipv4-address ipv4-mask| all)
no route-static
Delete IPv6 static
ipv6(ipv6-address ipv6-prefix|
routing entries
all)
Display IPv4 and
IPv6 static routing show ip route-static
table entries
22.3.3 Example of Static Route Configuration
This example uses an IPv4 address as an example. The IPv6 address configuration is
basically the same as that of IPv4.
Host A and host B are on different network segments. Host A is connected to G1000
through onu, and the G1000 uplink port is connected to the router. Through the router, it is
routed to the network segment 189.40.35.0. Connection instructions：
1) Set the IP of host A to 192.168.80.88/24 and connect to Lan 1 port of 0400 onu.
2) Onu's Lan port is set to transparent mode and connected to 2/1 PON port of G1000.
3) G1000 is connected to port1 of the router through 1/1.
4) The router is connected to the 189.40.35.0/24 device network segment through port2.
22.3.3.2 Network Diagram
Figure 22- 2 Typical Layer 3 routing scenario
Configuration step description：

（1）Set the onu VLAN mode to transparent mode, the purpose is to transparently
transmit all PC and G1000 data.
（2）Turn on the L3 switch of the G1000.
22-203
（3）Add VLAN 5 to G1000, the primary IP address of the L3 interface is 192.168.80.1/24,

and add PON port 1/1 to the VLAN. The VLAN mode of the VLAN is untag and pvid is
5. The purpose is to allow onu pass-through data from the PC without vlan to enter the
G1000.
（4）Add VLAN 6 to the G1000 again. The primary IP address of the L3 interface is
192.168.70.1/24. At the same time, add uplink port 1/1 to the VLAN. The VLAN mode
of the VLAN is untag and pvid is 6. The purpose is to allow the data from the router
without vlan to enter the G1000.
（5）Set the IP of port 1 of the router to 192.168.70.2/24 and the IP of port 2 to
189.40.35.1/24.
（6）Add a static route to G1000 and set the address of the next hop device accessing
the 189.40.35.0 network segment to 192.168.70.2/24, that is, when the destination
address is 189.40.35.0 network segment, it will be forwarded to 192.168.70.2 / 24
port.
（7）Add a static route on the router and set the address of the next hop device accessing
the 192.168.80.0 network segment to 192.168.70.1/24, that is, when the destination
address is the 192.168.80.0 network segment, it is handed over to 192.168.70.1 / 24
port. At the same time, configure a translation rule for the network segment
189.40.35.0 and the network segment 192.168.70.0 on the router.
（8）In this way, HOST A and HOST B can communicate. Through the two routes in the
G1000 and the router, the data on both sides can communicate.
Configuration steps on the OLT：
$ Enable L3 global switch：
G1000(config)# l3-interface enable
$ Configure the primary IP address of interface l3 as 192.168.80.1 and the mask as
255.255.255.0：
G1000(config-vlan-5)#l3-interface ip-address 192.168.80.1 255.255.255.0
$ Create vlan 6 as the l3 interface, configure the primary IP address of the l3 interface as
192.168.70.1, and the mask as 255.255.255.0：
G1000(config-vlan-6)#l3-interface ip-address 192.168.70.1 255.255.255.0
$ Add a static routing entry. The IP address of the next hop is 192.168.70.2 and the
destination network address is 189.40.35.0.：
G1000(config)# ip route-static 189.40.35.0 255.255.255.0 nexthop-ip 192.168.70.2
$ Configure GE 1/1 port：
$ Configure PON 1/1 port：
G1000(config-if-gpon-2/1)#port pvid 6
G1000(config-if-gpon-2/1)#port vlan 6 untagged
G1000(config-if-gpon-2/1)#exit
22-204
23 ONU upgrade management
This chapter mainly introduces the commands and configuration steps of the onu upgrade
mode.
23.1 OMCI Upgrade
In the OMCI mode, the version file is delivered to the onu in the OMCI mode, and the main
operations are completed on the OLT.
First you need to download the onu version file from the host to the flash of the main control
board SCUF by ftp, and then upgrade the file to onu through OMCI.
23.1.1 Introduction to OMCI Upgrade
Table 23- 1 OMCI upgrade configuration

Enter enable view enable -
ip-address ： The IP
address of the ftp server,
in the form of A.B.C.D
ftp download ip-address username ipv6-address ： IPV6
Download onu
password filename onu-app address of the ftp server,
version file to SCU
ftp download ipv6-address username in the form of X: X :: X: X
flash
password filename onu-app username：ftp username
password：ftp password
filename：File name to be
downloaded
Query file
information
show downloaded-image
downloaded to
SCU
Enter PON
interface olt interface-num -
interface view
startonuid : Starting
onuid
endonuid: Terminated
onu image update startonuid
Use OMCI to onuid
endonuid (WORD|unknown)
upgrade the auto-commit: Auto
(auto-commit|<cr>)
version file to onu commit after upgrade
(auto-reboot|<cr>)
auto-reboot: Auto reboot
after upgrade
The status is success

Query onu
show onu update-state when the upgrade is
upgrade status
successful.
23-205
Change the
software of the
This software is loaded
spare storage area onu image commit startonuid
and executed by default
to the software of endonuid (WORD|unknown)
when onu is started.
the main storage
area
Activate the onu
onu image active startonuid endonuid
software image
(WORD|unknown)
file.
23.1.2 OMCI Upgrade Example

Use OMCI to upgrade onu under PON 2/2
$ Download the onu version 501_V100R004B020.bin from the ftp server to the memory of
the SCU.：
G1000# ftp download 192.168.1.123 2 2 501_V100R004B020.bin onu-app
$ Use OMCI to upgrade the version file to onu：
G1000(config-if-gpon-2/2)#onu image update 1 32 m2-0400h
$ View onu upgrade status：
G1000(config-if-gpon-2/1)#show onu update-state
--------------------------------------------------------------------------------
ONU ID SN PASSWORD Type Status
--------------------------------------------------------------------------------
1 YOTC694F6096 1a694f6096 m2-0400h Ready
$ Batch switch the active and standby storage areas of all types of onu under pon 2/2：
G1000(config-if-gpon-2/2)#onu image commit 1 32 m2-0400h
$ Activate the onus software image file from 1 to 32 under pon2 / 2：
G1000(config-if-gpon-2/2)#onu image active 1 32 m2-0400h
24 Log Configuration Management

24.1 Introduction to Log Configuration
The main functions of the log are to monitor the running status of the device and debug and
locate problems. Can help us with fault location, troubleshooting and network security
management.
24.1.1 Types of Logs
Log types can be divided into the following 4 categories:
24-206
（1） Exception log

The exception log is a process record when an exception occurs inside the software
module. For example: the function return value is abnormal, or the internal state machine
jumps to an abnormal state, and key process execution errors;
（2） Alarm log
Record the log information generated by the alarm module; When an alarm is output to a
log, an alarm of the alarm type corresponds to an error level log, and an event of the alarm
corresponds to a notice level log.
（3） Operation log
Records operation logs generated by the CLI or SNMP；
（4） Debug Log
Used for logs generated during device debugging, such as: received IGMP protocol packets,
RSTP BPDU packets, and state machine jumps in the protocol stack.；
24.1.2 Log Level
There are 5 levels of log information: ERROR, WARNING, NOTICE, INFORMATION, and
DEBUG.
The correspondence with specific log types is:
Table 24- 1 Log type and level
ERROR WARNING NOTICE INFO DEBUG

Exception / Alarm Log Exception log Alarm log Operation log Debug log
You can set whether to block according to the log level. When the log is blocked, it will not
be output to any channel.
When the log is output to file, the operation level logs are recorded in the "/ mnt / info /"
directory in the flash, and other levels are recorded under the "/ mnt / log /" directory. You
can use the more command to view or upload the file to the server for viewing.
24.1.3 Log Output Mode
After the log module receives the input of the original log information, it needs to
automatically add the log generation time (the hour uses the 24-hour format). The output of
the log module mainly includes tty, buffer, syslog and file.
 TTY
Print the log information on the console and VTY.
The format is:HH:MM:SS MM/DD/YY[MODULE] [LEVEL] ConuENT
E.g:10:24:09 01/17/2020[pon] [DEBUG] 0x00001009 02/01/01-00 Step-1 Success
 BUFFER
Log information is recorded into the memory buffer, and a total of 512 log buffers are
supported.
In order to prevent the impact of log records after a DB crash, log information is not stored
in the database, but is stored in a sequential linked list, using logTime as the index sort.
 SYSLOG
Send log information to the SYSLOG server.
SYSLOG defines 8 log levels（LOG_EMERG、LOG_ALERT、LOG_CRIT、LOG_ERR、
LOG_WARNING、LOG_NOTICE、LOG_INFO、LOG_DEBUG），S The correspondence
between the YSLOG level and the log module is:
LOG_EMERG ╳
LOG_ALERT ╳
24-207
LOG_CRIT ╳
LOG_ERR ERROR
LOG_WARNING WARNING
LOG_NOTICE NOTICE
LOG_INFO INFO
LOG_DEBUG DEBUG
The SYSLOG report includes: level and content, The report format is:（SYSLOG_LEVEL ,
YY/MM/DD HH:MM:SS ConuENT）.Such as:（LOG_ERR ，“2020/02/09 13:15:00 PON
interface 2/1 add error.”）
 FILE
Log information to the Flash file system; The naming rule of the log file is: log-YY / MM / DD
/ SEQ.txt (SEQ is the serial number),log-2020019601.txt；Support a total of 5 log files, each
log file records 128k. The log files are recorded in turn. When the first log file is filled with
128k, the next log file is generated for recording based on the current time. When all 5 log
files are filled, the oldest log file is deleted.
The format of the log record is:YY/MM/DD HH:MM:SS [LEVEL] ConuENT
Such as:2020/02/09 13:15:00 [ERROR] PON interface 2/1 add error.
24.1.4 Log Function Module
The log module can configure log shielding and log output mode according to the function
modules of the system. It can be configured for only one function module, or all function
modules can be configured at the same time. The general log function is used to debug the
problem. It is recommended to open the log of the corresponding module when debugging,
otherwise too much log information will affect the viewing of the problem. As there are many
functional modules involved in the log, the device adds the log mask all default and log
output all all default commands to facilitate the restoration of the default configuration of the
log function.
The functional modules are:agent、cmd、monitor、alarm、cfg、perf、upgrade、sha、dev、
igmp、rstp、ntp、ipc、xml、db、switch、pon、cfgmgr，Among them, cfg refers to the configuration
config, and sha refers to the active and standby SCU functions of the system.
24.2 Log Configuration Operations
Table 24- 2 Log configuration

log mask
After the logs of a certain
Mask a certain (agent|cmd|monitor|alarm|cfg|perf|u
level are masked, the log
level of function pgrade|sha|dev|igmp|mld|rstp|ntp|i
information of that level
module logs pc|xml|db|switch|pon|cfgmgr|rip|all)
is no longer reported.
(error|warning|notice|info|debug|all)
no log mask
Unblock logs of a (agent|cmd|monitor|alarm|cfg|perf|u
certain level from a pgrade|sha|dev|igmp|mld|rstp|ntp|i
module. pc|xml|db|switch|pon|cfgmgr|rip|all)
24-208
log output
Set a certain level (agent|cmd|monitor|alarm|cfg|perf|u
of log of a module pgrade|sha|dev|igmp|mld|rstp|ntp|i
to the specified pc|xml|db|switch|pon|cfgmgr|rip|all)
output mode. (error|warning|notice|info|debug|all)
(tty|buffer|syslog|file|all)
no log output
Cancel the
(agent|cmd|monitor|alarm|cfg|perf|u
specified output
pgrade|sha|dev|igmp|mld|rstp|ntp|i
mode of a certain
pc|xml|db|switch|pon|cfgmgr|rip|all)
level of logs for a
module.
(tty|buffer|syslog|file|all)
Configure the
destination IP
log syslog ip ip-address/ipv6-address
address reported
by the syslog.
Restore the syslog
Delete syslog
no log syslog ip server IP to the default
server address
value.
Last- N- record ： Delete
Delete the earliest
N log records the earliest N log records
according to the time
according to the no log buf-record Last- N- record
log generation when the log was
generated. The value
time.
range is <1-512>.
show log
Query the log (buf-debug|buf-error|buf-info|buf-no
information in the tice|buf-record|buf-warning)(agent|c
buffer according to md|monitor|alarm|cfg|perf|upgrade|
the level. sha|dev|igmp|mld|rstp|ntp|ipc|xml|d
b|switch|pon|cfgmgr|rip|all)
Query the log
information in the
flow-id ： PON process
buffer according to show log flow-id flow-id
number
the PON process
number.
Query the log
information in the
show log location slotid [ponid]
buffer according to
[onuid] [uniid]
the log generation
source.
Query the log
show log mask
mask information
(agent|cmd|monitor|alarm|cfg|perf|u
of the specified
pgrade|sha|dev|igmp|mld|rstp|ntp|i
module or all
pc|xml|db|switch|pon|cfgmgr|rip|all)
modules.
Query the log show log output
output mode of the (agent|cmd|monitor|alarm|cfg|perf|u
specified module pgrade|sha|dev|igmp|mld|rstp|ntp|i
or all modules. pc|xml|db|switch|pon|cfgmgr|rip|all)
Querying the
syslog server IP show log syslog ip
address
24-209
Restore the default

value of the mask
log mask all default
log function
module
Restore log output
configuration log output all all default
defaults
24.3 Example of Log Configuration

 Cancel the log shielding of the alarm module and query the configuration result.
 Configure the alarm module logs to be output to the tty user interface to query the
configuration results.
 Configure the syslog server IP address as 192.168.85.188 and query the configuration
result.
24.3.2 Configuration Steps
$ Enter the config view:

$ View the log mask configuration of the alarm module by default:
G1000(config)# show log mask alarm
alarm
--------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------
Disable Disable Enable Enable Enable
--------------------------------------------------------------------------------------------
$ Cancel the log shielding of the alarm module and view the configuration results:
G1000(config)# no log mask alarm all
G1000(config)# show log mask alarm
alarm
--------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------
Disable Disable Disable Disable Disable
--------------------------------------------------------------------------------------------
$ View the log output configuration of the alarm module by default:
G1000(config)# show log output alarm
alarm
-----------------------------------------------------------------------------------------
Error: ----- buffer ----- file
Warning: ----- buffer syslog -----
Notice: ----- ----- ----- -----
Info: ----- buffer syslog -----
Debug: ----- ----- syslog -----
-----------------------------------------------------------------------------------------
$ Configure the alarm module log to output to the tty user interface and query the
24-210
configuration result:
G1000(config)# log output alarm all tty
G1000(config)# show log output alarm
alarm
-------------------------------------------------------------------------------------------------
Error: tty buffer ----- file
Warning: tty buffer syslog -----
Notice: tty ----- ----- -----
Info: tty buffer syslog -----
Debug: tty ----- syslog -----
-------------------------------------------------------------------------------------------------
$ Query the configuration of log syslog by default:
G1000(config)# show log syslog ip
Syslog server ip address :0.0.0.0
$ Set the syslog server IP address to 192.168.85.188 and query the configuration results:
G1000(config)# log syslog ip 192.168.85.188
G1000(config)# show log syslog ip
Syslog server ip address :192.168.85.188
25 Traffic Threshold Alarm Configuration

Management
25.1 Introduction to Traffic Threshold Alarm Configuration
The traffic threshold alarm is a system port alarm. When the port traffic of the OLT or onu
exceeds the set threshold, an alarm message is generated. The alarm information includes
port information and the current actual traffic rate. It should be noted that in addition to the
onu data port, the uplink port and the PON port of the OLT also need to support the traffic
threshold alarm notification.
The traffic monitored by the traffic threshold alarm is only for downstream traffic. The alarm
is reported once after it is generated. When the port traffic drops below 90% of the
threshold, the alarm is cleared. After reporting a threshold exceeding alarm, it will continue
to monitor the traffic value of the port.
The traffic threshold alarm can be masked and turned on, and the corresponding alarm
information is not sent after masking.
The traffic threshold alarm can set the traffic threshold or clear the threshold setting.
25.2 Traffic Threshold Alarm Configuration

25.2.1 Traffic Threshold Alarm Configuration Example
Enable the traffic threshold alarm switch and configure the OLT or onu port traffic threshold.
25-211
25.2.1.2 Network Diagram
Figure 25- 1 Traffic threshold alarm configuration example diagram
25.2.1.3 Configuration Steps
OLT port traffic threshold alarm configuration:

$ Enable the OLT traffic threshold alarm switch
G1000(config-if-gpon-2/4)#alarm-admin traffic-threshold enable
$ Configure OLT port traffic threshold
G1000(config-if-gpon-2/4)#port traffic-threshold 10000
$ Querying the OLT Port Traffic Threshold Configuration in the Port View
G1000(config-if-gpon-2/4)#show port traffic-threshold config
traffic admin PortTrafficThreshold AlarmFlag
----------------------------------------------------------------
enable 0 no alarm
$ Query the traffic threshold configuration of all OLT ports in the global view
G1000(config)# show olt port traffic-threshold config
slot/port admin threshold alarmFlag
-------------------------------------------------------------------------------------------------------------------------
1/1 disable 0 no alarm
2/7 enable 0 no alarm
2/8 enable 0 no alarm
$ Clear the OLT port traffic threshold
G1000(config-if-gpon-2/4)#port traffic-threshold clear
Onu port traffic threshold alarm configuration：

$ Enable the onu traffic threshold alarm switch
G1000(config-if-ont-2/4/1)#alarm-admin traffic-threshold 1 4 enable
$ Configure onu port traffic threshold
G1000(config-if-ont-2/4/1)#port traffic-threshold 1 4 10000
$ Query the onu port traffic threshold configuration
G1000(config-if-ont-2/4/1)#show port traffic-threshold config
25-212
port index traffic admin PortTrafficThreshold

------------------------------------------------------------------------------
1 enable 0
2 enable 0
3 enable 0
4 enable 0
$ Query the traffic threshold configuration of all onu ports in the global view
G1000(config)# show onu port traffic-threshold config
slot/pon/onuid portid traffic admin PortTrafficThreshold
------------------------------------------------------------------------------
1/1/1 1 enable 0
1/1/1 2 enable 0
1/1/1 3 enable 0
1/1/1 4 enable 0
------------------------------------------------------------------------------
$ Clear the OLT port traffic threshold
G1000(config-if-ont-2/4/1)#port traffic-threshold 1 4 clear
26 Appendix:Revision History
Date Revision Edit description Author

2020-01-14 V0.1 Initial creation
2020-05-29 V1.0 Update some commands
Update description of G1022 and G1012, update version
2020-08-30 V2.0
number
Modified the figures involved Chinese, modified some
2020-10-23 V2.1
spelling problems
2020-10-23 V2.2 Deleted some functions’ description
26-213

Opticalink G1000 GPON OLT Operation ManualV2.2

Uploaded by

Document Information

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

Opticalink G1000 GPON OLT Operation ManualV2.2

Uploaded by

Copyright:

Available Formats

Opticalink G1000

About This Manual

"Opticalink G1000 GPON OLT It introduces G1000 OLT devices basics,

 Chapter 11 GPON Service Management: Introduce GPON service

CAUTION: Caution should be noted in the operation. Improper operation

WARNING: Comments after this symbol must be given special attention.

Description, Tips, Tricks, Thinking: The description of the operation content is

Abbreviation Full expression

4.4 NETWORK TOOL OPERATIONS..............................................................................................................................34

8.1.2 PON Port Isolation Configuration......................................................................................................... 69

11.4.3 GPON GEMPORT Configuration example......................................................................................... 116

15.4.1 Networking Requirements................................................................................................................151

19.1 INTRODUCTION TO PERFORMANCE STATISTICS CONFIGURATION.............................................................................. 181

25.1 INTRODUCTION TO TRAFFIC THRESHOLD ALARM CONFIGURATION..........................................................................211

1.1.1 Software version corresponding to the manual

1.1.2 The Supporting Information List

Table 1- 1 The supporting Information List

Manual Name Version

"Opticalink G1000 GPON OLT Installation Manual" V2.1

"Opticalink G1000 GPON OLT Operation Manual" V2.2

"Opticalink G1000 GPON OLT Command Line Manual" V2.0

1.2 Product introduction

The G1000 series has the following product variants:

1.3 How to manage onu

2 Login To the OLT

2.1 Logging In Through the Console Port

2.1.1 Configuring the Cable Connection

2.1.2 Configuration of Terminal Parameters

Step 2: Set Windows XP Hyper Terminal parameters.

Figure 2- 2 Hyper Terminal connection interface

Figure 2- 3 Hyper Terminal connection using serial port settings

Figure 2- 4 Serial port settings

4） After setting serial port parameters, click the [OK] button.

2.1.3 Startup Interface

User Access Verification

2.2 Log in locally through Telnet

Figure 2- 5 Log in locally through Telnet

2.2.1 Network Cable Connection

2.2.2 Setting the Outside Management Interface Parameters

For details, read Chapter 21.4 Out-band Management Configuration.

2.2.3 Set Terminal PC Card Parameters

Specific methods are as follows:

2.2.4 Set Telnet Terminal Parameters

1） Click "Start" - "Programs" - "Accessories" - "Communication" - "Hyper Terminal" to

2.2.5 Telnet Connection Interface

2.2.6 Connecting the PC Cable

2.2.7 Set the In-band Management Interface PRM for Local-end

For details, Read "21.5 In-band Management Configuration".

2.2.8 Set the Terminal PC Card Parameters

2.2.9 Set Telnet Terminal Parameters

2.2.10 Telnet Connection Interface

Read “Telnet Connection Interface” view.

2.3 Remote login via WIFI interface

2.3.1 WIFI connection

2.3.2 Setting PC WIFI Network Card Parameters

Set PC WIFI network card parameters to DHCP to obtain IP automatically.

2.3.3 Setting Telnet Terminal Parameters

2.3.4 Telnet connection interface

Read "2.2.5 Telnet connection interface".

3 Command Line Interface and View

 Local configuration through the Console port.

3.2 Command Line Hierarchy and Command Line View

3.3 Command Line View

G1000 (config)# interface onu 2/1/1