Optical line terminals LTP-16N, LTP-16NT

User Manual
Firmware version 1.2.0 (28.05.2021)



|| DeviceType | Optical line terminals |
|| DeviceName1 | LTP-16N, LTP-16NT |
|| DocTitleAdditional | User Manual, Issue 2 (28.05.2021) |
|| fwversion | 1.2.0 |



Terms and Definitions

CBR            Constant bitrate

DBA           Dynamic bandwidth allocation

DHCP         Dynamic Host Configuration Protocol

ERPS          Ethernet Ring Protection Switching

FTP            File Transfer Protocol

FW             Firmware

GPON        Gigabit PON

HSI            High Speed Internet

IGMP         Internet Group Management Protocol

IP              Internet protocol

MLD          Multicast Listener Discovery

OLT           Optical Line Terminal

ONT         Optical Network Terminal

ONU         Optical Network Unit

PCB           Printed Circuit Board

PPPOE       Point-to-point protocol over Ethernet

SLA            Service Level Agreement

SNTP         Simple Network time protocol

SNMP        Simple Network Management Protocol

SFP            Small Form-factor Pluggable

TFTP          Trivial File Transfer Protocol

URI            Uniform Resource Identifier

VEIP           Virtual Ethernet Interface Point

Notes and warnings

Notes contain important information, tips or recommendations on device operation and configuration.


Warnings are used to inform the user about harmful situations for the device and the user alike, which could cause malfunction or data loss.

General information

Introduction

A GPON is a network of passive optical networks (PON) type. It is one of the most effective state-of-the-art solutions for the 'last mile' issue that significantly reduces the required amount of cable and provides data transfer with downstream rate up to 2.5 Gbps and upstream rate up to 1.25 Gbps. Being used in access networks, GPON-based solutions allow end users to have access to new services based on IP protocol in addition to more common ones.

The key GPON advantage is the use of one optical line terminal (OLT) for multiple optical network terminals (ONT). OLT converts Gigabit Ethernet and GPON interfaces and is used to connect a PON network with data communication networks of a higher level.

The range of OLT GPON equipment produced by Eltex comprises of LTP-16N and LTP-16NT terminals with internal Ethernet switch with RSSI function and 16 GPON ports.

This user manual describes purpose, main technical specifications, installation order, rules of configuration, monitoring, and software update for the devices.

Purpose

The LTP-16N(T) optical line terminal is designed to establish connection with upstream equipment and provide broadband access across passive optical networks. Ethernet connection is established through Gigabit uplink and 10G Base-X interfaces; GPON interfaces are used to connect to optical networks. Each PON interface allows connection of up to 128 subscriber optical terminals through one fibre and supports dynamic bandwidth allocation (DBA).

The following services are provided to end users:

The device supports the following functions:

Delivery Package

The standard delivery package includes:

  1. LTP-16N/16NT optical line terminal;
  2. Mounting set for 19'' rack.
  3. RJ-45 – DB9(F) console cable;
  4. CD with Operation Manual and Quick Configuration Guide (optional);
  5. Power cable (if equipped with 220V power supply);
  6. Informational leaflet;
  7. Declaration of conformity;
  8. Technical passport.

Technical specifications

Table 1 – Main specifications of the line terminal

Interfaces

Number of Ethernet interfaces

LTP-16N/LTP-16NT

9

Connector

RJ-45 - 1

SFP - 8

Data rate, Mbps

10/100/1000

duplex/half-duplex

1000/10000

duplex

Standards

1GBase-X

10GBase-X

Standards

IEEE 802.1D, IEEE 802.1p, IEEE 802.1Q

Number of PON interfaces

LTP-16N/LTP-16NT

16

Connector type

SC/UPC (socket)
in accordance with ITU-T G.984.2, FSAN Class B+, FSAN Class C++, SFF-8472

Transmission medium

SMF – 9/125, G.652 fibre optical cable

Standards

Digital RSSI (Received Signal Strenght Indication)

Splitting ratio

1:4, 1:8, 1:16, 1:32, 1:64, 1:128


Class B+

Class C++

Range of coverage

20 km

40 km

Transmitter

1490 nm DFB Laser

1490 nm DFB Laser

Data rate

2488 Mbps

2488 Mbps

Average output power

+1,5..+5 dBm

+7..+10 dBm

Spectral line width with -20dB

1.0 nm

1.0 nm

Receiver:

1310 nm APD/TIA

1310 nm APD/TIA

Data rate

1244 Mbps

1244 Mbps

Receiver sensitivity

-28 dBm

-32 dBm

Receiver optical congestion

-8 dBm

-12 dBm

Synchronization ports

Only for LTP-16NT

Processor

Clock frequency

2.1 GHz

Core quantity

4

RAM

LTP-16N/LTP-16NT

8 GB

Non-volatile memory

LTP-16N/LTP-16NT

8 GB

Switch

Switch performance

120 Gbps

MAC table

64K entries

VLAN support

up to 4K in accordance with 802.1Q

Control

Local control

CLI – command line interface

Remote management

CLI (SSH, Telnet), SNMP

Monitoring

CLI, SNMP

Access restriction

by password, by privelege level

General parameters

Power supply

AC: 150..250V, 50 Hz
DC: -36..-72V

Maximum power consumption

LTP-16N/LTP-16NT

75 W

Operating temperature range

from -5 to +40°C

Relative humidity

Up to 80%

Dimensions (WxHxD)

19", 1U

Dimensions with an installed power module:

430x42x305 mm

Weight

Complete set

LTP-16N/LTP-16NT

3.5 kg

Modules

Power module

0.5 kg

Compatible SFP transceivers

Correct and error-free operation of GPON interface requires exact parameters to be chosen and set for each transceiver type. This can be done only under laboratory conditions by the terminal vendor.  Table 2 lists SFP transceivers for which seamless terminal operation is guaranteed.

DDMI (Digital Diagnostic Monitoring Interface) provides information on transceiver parameters, such as temperature, power voltage, etc. DDMI also measures the level of ONT signal (RSSI). All compatible transceivers support this function.

Table 2 – List of compatible SFP transceivers

Vendor

SFP transceiver module

Class

DDMI

NEOPHOTONICS

PTB38J0-6538E-SC

B+

+

NEOPHOTONICS

38J0-6537E-STH1+

C+ HP

+

NEOPHOTONICS

38J0-6537E-STH2+

C+ HP

+

NEOPHOTONICS

38J0-6537E-STH3+

C+ HP

+

Ligent Photonics

LTE3680M-BC

B+

+

Ligent Photonics

LTE3680M-BH

B+

+

Ligent Photonics

LTE3680P-BC

C+

+

Ligent PhotonicsLTE3680P-BC+1C++

Ligent Photonics

LTE3680P-BH

C+

+

Ligent Photonics

LTE3680P-BC2

C+ HP

+

HisenseLTE3680M-BC+B++
HisenseLTE3680M-BC+2C++

Design

Front panel

The devices have a metal housing available for 19” form-factor rack mount; housing size is 1U. The front panel layout is shown in figures 1 and 2. Tables 3 and 4 list connectors, LEDs and controls located on the front panel of the terminal.

Figure 1 – LTP-16N front panel layout

Table 3 – Description of the connectors, LEDs, and controls located on the front panel of LTP-16N

#

Front panel element

Description

1

PS2

Redundant power supply indicator 

2

PS1

Primary power supply indicator 

3

Status

Device operation indicator

4

Power

Device power indicator

5

SSD

SSD operation indicator

6

FAN

Ventilation panels operation indicator

7

F

Functional key that reboots the device and resets it to factory default configuration:

  • pressing the key for less than 15 seconds reboots the device;
  • pressing the key for more than 15 seconds resets the device to factory default configuration. 

8

USB

USB port

9

Console

DB9F — RJ45 console port

10

Alarm

Alarm indicator

11

OOB

Port for connection the board via network

12

PON 1..16

GPON interfaces. 16 chassis for installing xPON 2.5G SFP modules 

13

10/1GE

Uplink interfaces. 8 chassis for installing 10G-BASE-X SFP modules


 
Figure 2 – LTP-16NT front panel layout


Table 4 – Description of the connectors, LEDs, and controls located on the front panel of LTP-16NT

#

Front panel element

Description

1

PS2

Redundant power supply indicator 

2

PS1

Primary power supply indicator 

3

Status

Device operation indicator

4

Power

Device power indicator

5

SSD

SSD operation indicator

6

FAN

Ventilation panels operation indicator

7

F

Functional key that reboots the device and resets it to factory default configuration:

  • pressing the key for less than 15 seconds reboots the device;
  • pressing the key for more than 15 seconds resets the device to factory default configuration. 

8

Console

DB9F — RJ45 console port

9

Sync

Synchronization operation indicator

10

Alarm

Alarm indicator

11

Sync ports

Synchronization interfaces

12

USB

USB port

13

OOB

Port for connection the board via network

14

PON 1..16

GPON interfaces. 16 chassis for installing xPON 2.5G SFP modules 

15

10/1GE

Uplink interfaces. 8 chassis for installing 10G-BASE-X SFP modules

Rear panel

The rear panel of the device is shown in Figure 3.

Table below lists rear panel connectors.

Figure 3 – LTP-16N/16NT optical line terminal rear panel

Table 5 – Rear panel connectors description

Rear panel element

Description

160..250 VAC, 50Hz, max 1A; 36..72 VDC, max 5A

Connectors for AC/DC power supply

Earth bonding point

Earth bonding point

Fan1, Fan2

Ventilation units

LED Indication

The indicators located on the front panel show the status of the terminal. Table 6 provides possible statuses of the LEDs.

Table 6 – LTP-16N/16NT status light indication

LED name

Indicator State

Device state

Power

Solid green

Power is on, normal device operation

Off

Power is off

Red

Primary power supply failure

Status

Solid green

Normal operation

Solid red

Operation failures

Fan

Solid green

All fans are operational

Flashing red

One or more fans are failed

PS1

Solid green

Primary power supply is connected and operates correctly

Disabled

Primary power supply is not connected

Red

Primary power supply is missing or failed.

PS2

Solid green

Redundant power supply is connected and operates correctly

Disabled

Redundant power supply is not connected

Red

The primary source of the redundant power supply is unavailable or the redundant power supply failed

Alarm

Green

Correct device operation

Flashing red

Alarm

SSD

Disabled

Cannot reach the drive

Flashing green

The drive is being accessed

Sync

Solid green

Synchronization is in process

Disabled

Synchronization is disabled

Temperature sensors

4 temperature sensors are used to measure temperature inside the terminal case: 3 external and 1 into switch.

Figure 4 shows the sensor location on PCB.

Figure 4 – Temperature sensors allocation

Table 7 – Temperature sensors description

Rear panel element

Description

Temperature sensor 1

PON-ports SFP 1

Temperature sensor 2

PON-ports SFP 2

Temperature sensor 3

Front-ports SFP

Temperature sensor 4

Switch

Ventilation system

There are ventilation openings on the device rear, front and side panels that serve to remove heat. There are two ventilation units on the rear panel (Figure 3).

Air flows in through the perforated front and side panels, circulates through all internal components, cools them down, and then is removed by fans located on the perforated rear panel.

The device contains two blocks of two fans each. The ventilation units are detachable. The procedure for dismantlement and installation is described in Ventilation Units Replacement.

Safety rules and Installation procedure

Introduction

This section describes safety measures and installation of the terminal into a rack and connection to a power supply.

Safety requirements

General requirements
Any operations with the equipment should comply to the Safety Rules for Operation of Customers' Electrical Installations.

Operations with the terminal should be carried out only by personnel authorised in accordance with the safety requirements.

  1. Before operating the device, all engineers should undergo special training.
  2. Connect only serviceable and compatible accessories to the terminal.
    To avoid overheating and provide necessary ventilation of the terminal, sufficient space should be provided above and below the terminal.
  3. The device could be permanently used provided the following requirements are met:
  4. The terminal should be not be exposed to mechanical shock, vibration, smoke, dust, water, and chemicals.
  5. To avoid components overheating which may result in device malfunction, do not block air vents or place objects on the equipment.

Electrical Safety Requirements

  1. Prior to connecting the device to a power source, ensure that the equipment case is grounded with an earth bonding point. The earthing wire should be securely connected to the earth bonding point. The resistance between the earth bonding point and earthing busbar should be less than 0,1 Ω. PC and measurement instruments should be grounded prior to connection to the terminal. The potential difference between the equipment case and the cases of the instruments should be less than 1V.
  2. Prior to turning the device on, ensure that all cables are undamaged and securely connected.
  3. Make sure the device is off, when installing or removing the case.
  4. Follow the instructions given in SFP transceivers replacement to install or remove SFP transceivers. This operation does not require the terminal to be turned off.

Terminal installation

Check the device for visible mechanical damage before installing and turning it on. In case of any damage, stop the installation, fill in a corresponding document and contact your supplier. If the terminal was exposed to low temperatures for a long time before installation, leave it for 2 hours at ambient temperature prior to operation. If the device was exposed to high humidity for a long time, leave it for at least 12 hours in normal conditions prior to turning it on.

Support brackets mounting
The delivery package includes support brackets for rack installation and mounting screws to fix the terminal case on the brackets. To install the support brackets:

Figure 5 – Support brackets mounting

Terminal rack installation
To install the terminal to the rack:

Figure 6 – Device rack installation

The terminal is horizontally ventilated. The side panels have air vents. Do not block the air vents to avoid components overheating and subsequent terminal malfunction.

To avoid overheating and provide necessary ventilation of the terminal, sufficient space should be provided above and below the terminal, not less than 10 cm.

Power module installation

Depending on power supply requirements, terminals can be supplemented with either an AC power module, 220V, 50 Hz, or a DC power supply module, 48 V. Location of the power module is shown in Figure 7.


Figure 7 – Power module installation

Terminals can operate with one or two power modules. The second power module installation is necessary when greater reliability is required. In case of using two power supply modules, it is allowed to use different power plants for supplying (with different voltage).


Figure 8 – Power module installation

From the electric point of view, both places for power module installation are identical. In the terms of device operation, the power module located closer to the edge is considered as the main module, and the one closer to the centre — as the backup module. Power modules can be inserted and removed without powering the device off. When an additional power module is inserted or removed, the device continues to operate without reboot.

To install a power module:

The device installation order:

Getting Started with the terminal

Connecting to the Terminal CLI

Introduction

This section describes various connection methods for Command Line Interface (CLI) of the terminal.

A serial port (hereafter – COM port) is recommended for preliminary adjustment of the terminal.

Connecting to CLI via COM port

This type of connection requires PC either to have an integrated COM port or to be supplied with an USB-COM adapter cable. The PC should also have a terminal program installed, e. g. Hyperterminal.

Figure 9 – Connecting the terminal to a PC via COM port

Connecting to CLI via Telnet protocol

The Telnet protocol connection is more flexible than the connection via COM port. Connection to CLI can be established directly at the terminal location or via an IP network with the help of a remote desktop.

This section considers direct connection to CLI at the terminal location. Remote connection is similar, but requires changes in the terminal IP address that will be considered in detail in the Network Settings section.

In order to be connected to the terminal, a PC should have a Network Interface Card (NIC). The connection will additionally require the sufficient amount of network cable (Patching Cord RJ45) as it is not included in the delivery package.

 

Figure 10 – Connecting the terminal to a PC via network cable

Figure 11 – Network connection configuration

Figure 12 – Telnet client startup

Connecting to CLI via Secure Shell protocol

Secure Shell connection (SSH) has functionality similar to the Telnet protocol. However, as opposed to Telnet, Secure Shell encrypts all traffic data, including passwords. This enables secure remote connection via public IP networks.

This section considers direct connection to CLI at the terminal location. Remote connection is similar, but requires changes in the terminal IP address that will be considered in detail in the Network Settings section.

In order to be connected to the terminal, a PC should have a Network Interface Card (NIC). The PC should have an SSH client installed, e. g. PuTTY. The connection will additionally require the sufficient amount of network cable (Patch Cord RJ-45) as it is not included in the delivery package.

Getting Started with terminal CLI

Introduction

CLI is the main means of communication between user and the terminal. This section describes general CLI procedures, with information on grouping, autocomplete options, and command history.

CLI views hierarchy

The command system of the LTP-16N command line interface is divided into view sections. The transition between sections is performed by commands. The exit command is used to return to the previous level. Some views are an array where a unique index must be used to access a specific object.

Figure 13 shows a graphic chart of main views and the commands to switch between them.

  
Figure 13 – CLI views hierarchy

CLI hotkeys

In order to speed up the operations with the command line, the following hotkeys have been added:

Table 9 – Command line hotkeys

Hotkey

Result

Ctrl+A

Transition to the beginning of line

Ctrl+D

In a nested command mode – exit to the previous command mode (exit command), in a root command mode – exit from CLI

Ctrl+E

Transition to the end of line

Ctrl+L

Screen clearing

Ctrl+U

Removal of characters to the left of a cursor

Ctrl+W

Removal of a word to the left of a cursor

Ctrl+K

Removal of characters to the right of a cursor

Ctrl+C

Line clearing, command execution interruption

CLI automatic code completion

To simplify the use of the command line, the interface supports automatic command completion. This function is activated when the command is incomplete and the <Tab> character is entered.

For example, enter the ex command in the Top view and press <Tab>:

LTP-16N# ex<Tab> 
LTP-16N# exit

As this view has only one command with the ex prefix, CLI automatically completes it.

If there are several commands with this prefix, CLI shows hints with possible options:

LTP-16N# co<Tab> 
commit configure copy 
LTP-16N# con<Tab> 
LTP-16N# configure

Group operations

Group operations can be performed on such terminal configuration objects as interfaces and ONT. It is especially convenient, when you have to apply the same actions to multiple objects.

To perform a group operation, select the range of object IDs instead of one object ID. This feature is supported by a majority of CLI commands.

For example, enable broadcast-filter for all ONTs in a certain channel.

LTP-16N# configure
LTP-16N(configure)# interface ont 1/1-128
LTP-16N(config)(if-ont-1/1-128)# broadcast-filter 
LTP-16N(config)(if-ont-1/1-128)#

Or view the list of active ones in the first 3 GPON channels:

LTP-16N# show interface ont 1-3 online 
GPON-port 1 has no online ONTs
GPON-port 2 has no online ONTs
GPON-port 3 has no online ONTs
Total ONT count: 0

Configuring the terminal

Terminal configuration

Introduction

A collection of all terminal settings is referred to as configuration. This section provides information on the parts which configuration consists of. It also defines lifecycle of configuration and describes main operations, which can be performed.

Configuration lifecycle

The terminal configuration may have the following states:

The Running configuration is loaded to a new CLI session and becomes available for review (Candidate). A different copy of the Candidate configuration is used for each session. After a configuration (Candidate) change in a CLI session, the user can issue a command to apply the changed configuration (the commit command). The save command saves the Running configuration into NVRAM of the terminal.
Figure 14 shows a chart of configuration lifecycle.


Figure 14 – Configuration lifecycle of the terminal chart

Creating a configuration backup

Configuration backups allow the terminal operation to be quickly restored after abnormal situations or replacement. Regular manual backups of the configuration are recommended.

Terminal configuration is uploaded to a TFTP server which is available in the management network. The copy command is used to upload the data. Pass the uploaded terminal configuration fs://config and destination URI as parameters.

LTP-16N# copy fs://config tftp://192.168.1.1/config 
Upload backup file to TFTP-server..

Configuration restore

The terminal configuration is restored from a TFTP server which is available in the management network. The copy command is used to restore the data. Define source URI as parameter and fs://config as restored configuration.

LTP-16N# copy tftp://10.0.105.1/config fs://config 
	Download file from TFTP-server.. 
	Reading of the configuration file.. 
	Configuration have been successfully restored (all not saved changes was lost)

Configuration reset

To reset a terminal configuration to factory settings, use the default command. After running the command, the default configuration is applied as a Candidate and must be applied using the commit command.

LTP-16N# default 
    Do you really want to do it? (y/N)  y
    Configuration has been reset to default
LTP-16N# commit


Resetting a configuration of a remote terminal also resets network settings. The terminal will not be available for operation until the network settings are reconfigured.

Network settings

Introduction

This section describes adjustment of network settings for the terminal. Adjusting network settings enables remote control and integration with OSS/BSS systems.

Network parameters configuration

It is recommended to adjust network settings via COM port connection. This will prevent issues with connection loss upstream the terminal being adjusted. Be very careful when using remote adjustment.

User management

Introduction

This section is devoted to management of the terminal users.

The factory settings provide only one user, i. e. the device administrator.

login: admin
password: password

When you start to configure the terminal, we recommend you to change the password of the 'admin' user.

For security reasons, there is a strictly defined set of permissions, which can be delegated to terminal users. For these purposes, each user gets his own privilege level. Level 0 corresponds to a minimum set of permissions, Level 15 — to a maximum set of permissions. Levels 1 to 14 are fully configurable. For ease of use, these levels are filled with default privileges.

The CLI commands are divided into access levels according to the block they change or let you view. Commands without access level (exit, !) are available to all users. Level 15 commands are available only to Level 15 users. Thus, the level of commands available to a user does not exceed the user's level.

Privilege configuration

User list preview

To view the list of terminal users, enter the show running-config user all command:

LTP-16N# show running-config user all
 user root encrypted_password $6$FbafrxAp$vY6mRGiEff9zGhaClnJ8muzM.1K1g86.GfW8rDv7mjOpcQcRptx7ZY//WTQDi9QxZSZUkOk02L5IHIZqDX0nL.
 user root privilege 15
 user admin encrypted_password $6$lZBYels7$1sd.B2eherdxsFRFmzIWajADSMNbsL1fjO7PsVCTJJmpDHpz0gZmkX2rZlJhLgRzTvkDwQ1eqF3MwNQiKGwPz/
 user admin privilege 15

The admin and root users always exist and cannot be deleted or duplicated. The terminal supports up to 16 users.

Adding a new user

In order to operate effectively and safely, the terminal, as a rule, requires one or several additional users. To add a new user, enter the user command in the configure view:

LTP-16N# configure terminal
LTP-16N(configure)# user operator
    User operator successfully created

Pass the name of the new user as a parameter to the user command. The name should not be longer than 32 characters. The name should not contain special characters.

Changing user password

To change user password, enter the user command. Pass the user name and a new password as parameters. Default password is password.In the configuration, the password is stored in encrypted form.

LTP-16N(configure)# user operator password newpassword
    User operator successfully changed password
LTP-16N(configure)#

The password should not be longer than 31 characters and shorter than 8 characters. If the password contains a space, use quotations for the password.

Viewing and changing user access rights

To manage user access rights, a user priority system is implemented. A newly created user is granted with a minimal set of permissions:

LTP-16N(configure)# do show running-config user 
 user operator encrypted_password $6$mIwyhgRA$jaxkx6dATExGeT82pzqJME/eEbZI6c9rKWJoXfxLmWXx7mQYiRY0pRNdCupFsg/1gqPfWmqgc1yuR8J1g.IH20
 user operator privilege 0

To change the user priority level, enter the user command. Pass the user name and a new priority as parameters.

LTP-16N(configure)# user operator privilege 15
    User operator successfully changed privilege
LTP-16N(configure)# do show running-config user 
 user operator encrypted_password $6$mIwyhgRA$jaxkx6dATExGeT82pzqJME/eEbZI6c9rKWJoXfxLmWXx7mQYiRY0pRNdCupFsg/1gqPfWmqgc1yuR8J1g.IH20
 user operator privilege 15

Deleting a user

To delete a user, enter the no user command in the configure view. Pass the user name as a parameter:

LTP-16N# configure terminal
LTP-16N(configure)# no user operator
    User operator successfully deleted

Services configuration

Introduction

This section describes configuration of integrated terminal services.

SNMPD configuration

For the terminal to work via SNMP, the appropriate service should be enabled.

You need to configure users to operate with SNMPv3.

The SNMPv3 agent supports authNoPriv and authPriv methods. The encryption of the password performs according to the MD5 algorithm.

The types and purpose of SNMP traps are closely connected with the log of active alarms.

LOGD configuration

System log collects terminal history data and allows its further display. Adjustment of system log operates with such terms as module, filter level, and output device.


Figure 15 – Terminal system log

Messages of the system log are grouped into modules according to their functions. Configuration of the following modules is possible:

Table 10 – System log modules

Module

Description

cli

CLI module service messages

snmp

Messages from the SNMP agent

dna

Primary network module messages 

fsm-pon

PON state machine messages

igmp

Messages from IGMP operation module

logmgr

Log control module service messages

usermgr

Log control module service messages

For each module, you can select the level of filtering, as well as sub-module settings, for more flexible logging configuration.
The filtering level sets the minimum importance level of the messages to be displayed in the log. The used filtering levels are listed in Table 11.

Table 11 – System log filtering levels

Level

Description

critical

Critical events

error

Operation errors

warning

Warnings

notice

Important events during normal operation. Default values for all modules

info

Information messages

debug

Debug messages


The critical level is the maximum level, the debug level is the minimum one.

The log subsystem allows display of the terminal operation log on different devices. All output devices can be used simultaneously.

Table 12 – System log output devices

Output device

Name

Description

System log

system

The system log allows the log to be displayed locally or with the help of the syslog server.

Console

console

Being used for log display, the console allows system messages to be visible as soon as they are received in the terminal connected to the Console port.

File

file

Logging into a file allows system messages to be written directly to the file, which can be sent to support specialists for further analysis.

The log is saved in non-volatile memory by default. The system has 3 log rotated files of 1M each. 

Module configuration

Consider the configuration using the dna module and the ont sub-module, which is responsible for displaying logs for the ONT. Other modules have similar configuration process.

Configuring the log storage

Use the following command to record logs to non-volatile memory:

LTP-16N(config)(logging)# permanent

If you enter «no» before the command, the logs will be recorded to RAM. In this case, the logs will be erased after reboot.

System log configuration

ALARMD configuration

ALARMD is a terminal alarms manager. Alarms manager enables troubleshooting and provides information about important events related to terminal operation.

A record in active alarms log (an event) corresponds to an event, which happened in the terminal. Types of events and their descriptions are provided in the following table.

Table 13 – Types of events in the active alarms log

Event

Description

Threshold

system-ram

Free RAM size decreased to the threshold

12% *

system-login

User tried to log in or logged in using their credentials

-

system-logout

User logged out

-

config-save

User saved the configuration

-

config-change

OLT configuration changed

-

system-load-average

Average CPU load reached the threshold, estimated time is 1 minute

0*

system-temperature

Temperature of one of the four temperature sensors has exceeded the threshold

70*

system-fan

Fan rotation speed exceeded the safe operating limits

2000 < X
< 12000*

pon-alarm-los

Translation of Loss of Signal PLOAM alarms

-

pon-alarm-lofi

Translation of Loss of Frame PLOAM alarms from ONT

-

pon-alarm-loami

Translation of PLOAM loss PLOAM alarms from ONT

-

pon-alarm-dowi

Translation of Drift of Window PLOAM alarms from ONT

-

pon-alarm-sdi

Translation of Signal Degraded PLOAM alarms from ONT

-

pon-alarm-sufi

Translation of Start-up Failure PLOAM alarms from ONT

-

pon-alarm-loai

Translation of Loss of Acknowledge PLOAM alarms from ONT

-

pon-alarm-dgi

Translation of Dying-Gasp PLOAM alarms from ONT

-

pon-alarm-dfi

Translation of Deactivate Failure PLOAM alarms from ONT

-

pon-alarm-tiwi

Translation of Transmission Interference Warning PLOAM alarms from ONT

-

pon-alarm-loki

Translation of Loss of Key PLOAM alarms from ONT

-

pon-alarm-lcdgi

Translation of Loss of GEM Channel Delineation PLOAM alarms from ONT

-

pon-alarm-rdii

Translation of Remote Defect Indication PLOAM alarms from ONT

-


* The value can be adjusted.

Every record in the active alarms log has the parameters specified in Table 14 that are specified for each event type.

Table 14 – Parameters of events in the active alarms log

Token

Description

severity

Describes event severity. Has four states:
(info, minor, major, critical)

in

Specifies whether an SNMP trap should be sent when an event is added to the log. Has two states:
(true/false)

out

Specifies whether an SNMP trap should be sent when an event is deleted from the log (normalization). Has two states:
(true/false)

Active alarms log configuration

VLAN Configuration

Introduction

This section describes VLAN configuration.

VLAN ( Virtual Local Area Network) is a group of devices, which communicate on the channel level and are combined into a virtual network, connected to one or more network devices (GPON terminals or switches). VLAN is a very important tool for creating a flexible and configurable logical network topology over the physical topology of a GPON network.

VLAN Configuration

VLAN Configuration

To configure VLAN permission on interfaces, see Interface configuration.


VLAN Deletion

IGMP configuration 

Introduction

This section describes general IGMP configuration.

Enabling snooping

Report proxying

On LTP-16N proxying report is always based on ONT services.

DHCP Configuration

Introduction

This section describes the procedure for operating the terminal with the DHCP. The operation of the protocol can be divided into two blocks:

DHCP snooping

This functionality is used to intercept and process traffic on the terminal CPU.

Currently, this functionality must be enabled if you want to control and monitor DHCP sessions and to operate with option 82 in DHCP packets. 

DHCP snooping enabling 

DHCP option 82

DHCP opt82 is used to provide a DHCP server with additional information about a received DHCP request. This may include information about the terminal running DHCP opt82 as well as information about the ONT, which sent the DHCP request. DHCP packets are modified by interception and further processing in the terminal CPU, i.e. DHCP snooping must be enabled.

The DHCP server analyses DHCP option 82 and identifies the ONT. Terminal allows the option to be both transparently transmitted from the ONT and formed/rewritten according to a specified format. DHCP option 82 is especially useful for networks, which have no private VLANs dedicated for each user.

DHCP opt82 supports configurable formats for both Circuit ID and Remote ID. The format of the suboptions is configured with the help of the tokens listed in Table 15. The placeholders will be replaced with corresponding values, while the rest of the words will be passed as is.

Table 15 – List of tokens for configuring the DHCP option 82 suboption format

Token

Description

%HOSTNAME%

Terminal network name

%MNGIP%

Terminal IP address

%GPON-PORT%

Number of the OLT channel the DHCP request arrived from

%ONTID%

ID of the ONT, which sent the DHCP request

%PONSERIAL%

Serial number of the ONT, which sent the DHCP request

%GEMID%

ID of the GEM port the DHCP request arrived to

%VLAN0%

External VID

%VLAN1%

Internal VID

%MAC%

MAC address of the ONT, which sent the request

%OLTMAC%

OLT`s MAC address

%OPT60%

DHCP option 60 received from the ONT

%OPT82_CID%

Circuit ID received from the ONT

%OPT82_RID%

Remote ID received from the ONT

%DESCR%

First 20 characters of ONT description

DHCP option 82 management

The DHCP option 82 is configured via the profile system – profile dhcp-opt82. The system allows to create several different profiles and assign them not only globally to all DHCP packets in general, but also to separate profiles by VLAN. 

DHCP option 82 profile configuration

Active DHCP leases monitoring

When enabled, DHCP snooping allows monitoring of DHCP leases. To view the list of sessions use the show ip dhcp sessions command:

LTP-16N# show ip dhcp sessions 
    DHCP sessions (2):
##     Serial         GPON-port   ONT-ID   Service   IP                MAC                 Vid   GEM    Life time
----   ------------   ---------   ------   -------   ---------------   -----------------   ---   ----   ---------
1      ELTX6C000090   1           1        1         192.168.101.75    E0:D9:E3:6A:28:F0   100   129    3503     
2      ELTX71000030   1           3        1         192.168.101.143   70:8B:CD:BD:A5:32   100   189    3597     
LTP-16N#


PPPoE configuration

Introduction

This section describes the procedure for operating the terminal with the PPPoE. The operation of the protocol can be divided into two blocks:

PPPoE snooping

This functionality is used to intercept and process traffic on the terminal CPU.

Currently, this functionality must be enabled if you want to control and monitor PPPoE sessions and to operate with option 82 in packets. 

PPPoE snooping enabling 

PPPoE intermediate agent

PPPoE Intermediate Agent is used to provide BRAS with additional information about a received PADI request. This may include information about the terminal running PPPoE Intermediate Agent as well as information about the ONT, which sent the PADI request. PADI packets are modified by interception and further processing in the terminal CPU.

BRAS analyses the Vendor Specific tag and identifies the ONT. PPPoE Intermediate Agent forms or rewrites the Vendor Specific tag using a specified format. Vendor Specific tags are especially useful for networks, which have no private VLANs dedicated for each user. PPPoE Intermediate Agent supports configurable formats for Circuit ID and Remote ID. The format of the suboptions is configured with the help of the tokens listed in Table 16. The placeholders will be replaced with corresponding values, while the rest of the words will be passed as is.

Table 16 – List of tokens to configure the PPPoE Intermediate Agent suboption format

Token

Description

%HOSTNAME%

Terminal network name

%MNGIP%

Terminal IP address

%GPON-PORT%

Number of the OLT channel the PADI request arrived

%ONTID%

ID of the ONT, which sent the PADI request

%PONSERIAL%

Serial number of the ONT, which sent the PADI

%GEMID%

ID of the GEM port the PADI request arrived to

%VLAN0%

External VID

%VLAN1%

Internal VID

%MAC%

MAC address of the ONT, which sent the request

%OLTMAC%

OLT`s MAC address

%DESCR%

First 20 characters of ONT description

PPPoE Intermediate Agent management

The PPPoE Intermediate Agent is configured through the profile system – profile pppoe-ia. The system allows to create several different profiles and assign them globally to all PPPoE traffic. 

PPPoE Intermediate Agent profile configuration

Active PPPoE sessions monitoring

When PPPoE snooping is enabled, sessions can be monitored. To view the list of sessions use the show ip pppoe sessions command:

LTP-16N(config)(pppoe)# do show ip pppoe sessions
   PPPoE sessions (1):
##     Serial         GPON-port   ONT ID   GEM    Client MAC          Session ID   Duration    Unblock  
----   ------------   ---------   ------   ----   -----------------   ----------   ---------   ---------
1      ELTX6C000090           1        1    129   E0:D9:E3:6A:28:F0       0x0001     0:06:00     0:00:00


Interface configuration

Introduction

This section describes configuration of terminal interfaces.

Terminal interfaces can be divided into three groups:

Figure 16 – Set of terminal interfaces

Table 17 shows types of terminal switch interfaces.

Table 17 – Interfaces types and numbers

Interface

Quantity

Range

10G-front-port

8

[1..8]

gpon-port

16

[1..16]

oob

1

-

10G-front-ports configuration

GPON interface configuration

LAG configuration

Introduction

This section describes configuration of uplink interfaces aggregation. Link aggregation (IEEE 802.3ad) is a technology that allows multiple physical links to be combined into one logical link (aggregation group). Aggregation group has a higher throughput and is very reliable. 

The terminal supports one mode of interface aggregation – static. All communication channels in the group are always active.

LAG configuration

Balancing configuration

To improve balance 

It is possible to configure parameters for traffic balancing functions in port-channel. It is possible to configure the polynomial to be used in the interface selection function with the interface port-channel load-balance polynomial command.You can also configure which of the header fields will be used in calculations. Possible options: src-mac, dst-mac, vlan, ether-type. It is allowed to use a combination of up to 3 fields.

LTP-16N# configure terminal
LTP-16N(configure)# interface port-channel load-balance hash src-mac dst-mac vlan
LTP-16N(configure)# interface port-channel load-balance polynomial 0x9019

Port-channel configuration

Adding ports to port-channel

ONT configuration

Service Models

This section considers main terms and classification of service models.

Introduction

The service model can generally be based on one of the service principles: N-to-1, 1-to-1 and multicast. The «VLAN for Service» (N-to-1) architecture means that a service VLAN (S-VLAN) is used to provide all users with a certain service. The «VLAN for Subscriber» (1-to-1) architecture implies that a client VLAN (C-VLAN) is used to provide a user with multiple services. These methods are often combined in practice and form a hybrid model, which uses S-VLAN and C-VLAN simultaneously.

1-to-1 architecture

A separate VLAN is used for each subscriber in the C-VLAN model. In this operation scheme a channel from the uplink port to the GEM port of the ONT, in a given S-VLAN is built for the subscriber. And all traffic (including broadcast), goes to this GEM-port.

N-to-1 architecture

The S-VLAN model has dedicated S-VLANs for each service. Traffic is distributed among the GEM ports of the clients, based on the MAC table. If the MAC address is not learnt, the packet is sent to the broadcast GEM-port and replicated to all subscribers.

Multicast architecture

This architecture is similar to N-to-1, except that a dedicated multicast GEM port is used.

VLAN ID replacement; The concept of pon vid

The transfer of traffic from the service S-VLAN to the client C-VLAN can be done either on the OLT or on the ONT. To configure the replacement place, use the concept of pon vid. Setting this parameter, equal to outer vid or user vid, defines where the label replacement will take place – on OLT or ONT. The table below describes at what stage the replacement will take place, depending on the value of pon vid.

Table 18 – VID replacement stages

The meanuing of pon vid

Where the tag is replaced

outer vid = pon vid

Replacement occurs on the ONT

user vid = pon vid

Replacement occurs on the OLT

pon vid ≠ user vid ≠  outer vid

Replacement occurs on the ONT and the OLT

Pon vid is configured in the cross-connect profile, which allows you to customize the label replacement scheme for each service. By default, the replacement is performed on the ONT.

Operating principle

The model traffic concept is used for implementation of different service models in the terminal. The model is configured in a cross-connect profile, which allows the configuration of combined circuits within a single ONT Consider each scheme in more detail.

1-to-1

Consider the operation of the service configured according to the 1-to-1 model.
The scheme of this service model is shown in the Figure 17.

 
Figure 17 – 1-to-1 traffic model operation scheme 

A C-VLAN is used between an ONT and service routers (BRAS, VoIP SR) that encapsulate services for one subscriber (one ONT service), such as VoIP, Internet, and IPTV. In this case, all traffic is routed to one common GEM port. 

N-to-1

Consider an example of N-to-1 implementation. It is better to consider this scheme on the example of two ONTs.

The chart of this service model is shown in the following figure.

 
Figure 18 – Service Model 2 chart

Dedicated S-VLANs are used between the OLT and service routers (BRAS, VoIP SR) for each of the following services (here – Internet). The destination of the packet is defined by the MAC table, which explicitly stores the MAC address and GEM port correspondence. If no entry is found, the packet is sent to the broadcast GEM port and replicated to all ONTs using the service.


Multicast

The multicast scheme is similar to the N-to-1 scheme, except that a multicast GEM port is used and the MAC table is involved only for IGMP exchange. Multicast is sent directly to the multicast GEM port. This mechanism is closely related to IGMP snooping.

ONT licensing

Introduction

By default, OLT supports only Eltex ONTs operation. To enable any third-party ONTs, OLT requires a license. To purchase the license, contact Eltex Marketing Department.

Loading a license file to OLT

A license is a text file of the following format:

{
"version":"<VER>",
"type":"all",
"count":"<count>",
"sn":"<SN>",
"mac":"<MAC>",
"sign":"<hash>"
}

Where:

VER – license file version number;
count – number of third-party ONTs enabled on the OLT;
SN – LTP serial number;
MAC – LTP MAC address;
hash – license file digital signature.
There are two ways to load a license to OLT:

  1. Use the copy command:

    LTP-16N# copy tftp://<IP>/<PATH> fs://license 
    Download file from TFTP-server.. 
    License successfully installed.

    Where:

    IP – IP address of the TFTP server;
    PATH – path to the license file on the TFTP server.

  2. Use CLI:

    LTP-16N# license set """<license>""" 
    License saved. 
    License successfully installed.

    Where:

    <license> – full content of the license file including curly brackets.
    To view information about the license on the device, use the show command.

    LTP-16N# show license 
Active license information:
    License valid:              yes
    Version:                    1.2
    Board SN:                   GP2B000022
    Licensed vendor:            all
    Licensed ONT count:         10
    Licensed ONT online:        3

    The license file remains after device reload, firmware update, and configuration load. If OLT is reset to factory settings, the license is also deleted.

Deleting a license file from OLT

If necessary, you can delete a previously installed license using the no license command.

LTP-16N# no license 
License file removed. 
License successfully deleted from system. 
LTP-16N# show license 
Active license information: 
	No license installed

ONT configuration

Introduction

This section describes general principles of ONT configuration. It also defines configuration profiles.

ONT is configured with the help of a profile, which defines high-level expression of data communication channels. All operations related to channel creation are performed automatically. The way data communication channels are created depends on the selected service model.

ONT configuration includes assignment of configuration profiles and specification of ONT specific parameters. Configuration profiles allow general parameters to be set for all or for a range of ONTs. Profile parameters may include, for instance, DBA settings, configuration of VLAN operations in OLT and ONT, settings of Ethernet ports in ONT. Specific ONT parameters allow each separate ONT to have its own settings specified. Such settings include, for example, GPON password, subscriber's VLAN, etc.

ONT operation modes

Introduce the concept of Bridged and Routed services. For this, consider the concept of OMCI and RG management domains. These terms are determined in TR-142 Issue 2. In terms of management domains, an ONT is considered as a device, which operates in the OMCI domain only. The devices, which operate in both management domains (i. e. have an integrated router), are denoted as ONT/RG.

Everything that refers to the OMCI domain can be applied to both ONT and ONT/RG devices. For this reason, we will further denote ONT/RG as ONT. If an ONT is configured without the RG domain (without a router), skip all steps concerning RG.

Bridged service is a service, which configuration requires the OMCI management domain only, i. e. it can be completely configured with the help of the OMCI protocol in ONT. Routed service is a service, which configuration requires both the OMCI and RG management domains.

In addition to configuration in terminal, a routed service requires the RG domain to be configured by using one of the following methods:

  1. Pre-defined configuration – subscriber is provided with an ONT having fixed configuration.
  2. Local ONT configuration using WEB interface.
  3. ONT configuration using the TR-069 protocol and auto configuration server (ACS).

ONT is connected to RG using a Virtual Ethernet interface point (VEIP), which corresponds to the TR-069 WAN interface (described in TR-098) on the RG side. VEIP is represented by a virtual port in terminal parameters. The port has the same configuration procedure as Ethernet ports in the ports profile.

General principles of configuration

Service is the key term of ONT configuration. This term completely includes a communication channel, through which data is transferred from the interfaces located on the front panel of the terminal (see section Interface configuration) to users' ONT ports. There are two service profiles: cross-connect and dba. The cross-connect profile creates a GEM service port, the dba profile allocates an Alloc-ID for this ONT and associates a corresponding GEM port to the Alloc-ID.

Table 19 – ONT profiles

Profile

Description

cross-connect

Defines VLAN transformation in OLT and ONT. Defines service model. Defines ONT operation mode.

dba

Defines upstream traffic parameters

ports

Defines user port groups in ONT as well as IGMP and multicast parameters for user ports

management

Defines TR-69 management service parameters.

ONT profiles configuration

Cross-connect profile configuration

DBA profile configuration

This profile configures dynamic bandwidth allocation (DBA). These parameters allow specification of any T-CONT type described in G.984.3.

Ports profile configuration

The ports profile allows to group ports in ONT. The profile also contains IGMP and multicast setting as they are separately adjusted for each port.
Up to 4 Ethernet ports can be configured.

Management profile configuration

In the management profile it is possible to configure parameters to control a device configured in the RG domain. There are two options for transmitting the configuration for ACS settings – via OMCI; receive in other ways (for example via DHCP opt43).

ONT configuration procedure

Figure below shows a step-by-step procedure of ONT configuration.

Figure 19 – ONT configuration procedure

Service configuration in the ont-mode bridge mode

Consider configuring a mixed scheme of services built on different traffic-model. ONT will be configured in the bridge mode.

Configure 3 services:

  1. HSI and IPTV unicast, by traffic model N-to-1, the service VLAN is 200, the tag will be taken on the ONT, untagged traffic will come from the ONT port.
  2. Multicast, packets will come on OLT with tag 98. From the ONT port is also not tagged.
  3. Under the 1-to-1 model, with a service VLAN 100, in a separate bridge group, the ONT port will come out with a tag 10. Tag replacement will take place on the OLT.

Figure 20 – Abstract representation of the test configuration

Service configuration in the ont-mode router mode

Consider a typical configuration of services for ONT configured the in router mode: HSI, IPTV, VoIP and ACS.

To do this, configure 5 services:

  1. HSI service. N-to-1 model traffic, the service VLAN is 200, there will be a tag replacement on the OLT and it will arrive at 10 on the OLT.
  2. IPTV service. Service for multicast traffic. Traffic model multicast. The stream passes without changing the VLAN 30 tag.
  3. STB service. The service is required for unicast traffic for STBs. The tag is replaced to ONT. VLAN 250.
  4. VoIP service. Service for telephony, similar in settings to HSI. VLAN 100.
  5. ACS service. This service is used to control the ONT via ACS. Service VLAN 2000.

Terminal monitoring

General information

Information on current terminal firmware version

To view information on the current version of terminal firmware, use the show version command.

LTP-16N# show version 
    Eltex LTP-16N: software version 1.0.0 build 1699 on 05.11.2020 11:59

Terminal information preview

To view information about the terminal, use the show system environment command.

LTP-16N# show system environment
    System information:
        CPU load average (1m, 5m, 15m):        2.680 1.350 0.540
        Free RAM/Total RAM (Gb):               4.58/7.76
        Free disk space/Total disk space(Gb)): 5.77/6.13

        Temperature:
            Sensor PON SFP 1 (*C):             33
            Sensor PON SFP 2 (*C):             32
            Sensor Front SFP (*C):             31
            Sensor Switch    (*C):             39

        Fan state:
            Fan configured speed:              auto
            Fan minimum speed (%):             15
            Fan speed levels (%):              15-100
            Fan 1 (rpm):                       6360
            Fan 2 (rpm):                       6420
            Fan 3 (rpm):                       6420
            Fan 4 (rpm):                       6420

        Power supply information:
            Module 1:                          PM160 220/12 1vX
                Type:                          AC
                Intact:                        true
            Module 2:                          offline

        HW information
            FPGA version:                      2.0
            PLD version:                       2.0

        Factory
            Type:                              LTP-16N
            Revision:                          1v2
            SN:                                GP3D000032
            MAC:                               E8:28:C1:88:05:20

Table 20 – Terminal parameters

Parameter

Description

CPU load average

Average processor load

Free RAM/Total RAM

Free/total RAM

Free disk space/Total disk space

Free/total non-volatile memory

Temperature

Temperature from sensors

Fan configured speed

Set fan rotation speed

Fan minimum speed

Minimum fan rotation speed

Fan speed levels

Set fan rotation speed for each level

Fan state

Fans state and rpm value

FPGA version

FPGA firmware version

PLD version

PLD firmware version

Power supply information

Information about installed power modules

Factory

Device unique information

Network connection check

To check network connection, use the ping command. As a parameter, pass the IP address of the node to be checked.

LTP-16N# ping 192.168.1.5
PING 192.168.1.5 (192.168.1.5): 56 data bytes
64 bytes from 192.168.1.5: seq=0 ttl=64 time=0.311 ms
64 bytes from 192.168.1.5: seq=1 ttl=64 time=0.223 ms
64 bytes from 192.168.1.5: seq=2 ttl=64 time=0.276 ms

--- 192.168.1.5 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.223/0.270/0.311 ms

Terminal operation log

Use the show log command to view log files.

LTP-16N# show log files 
    
##    Name          Size in bytes       Date of last modification
1   LTP.log          4073                Mon Nov 16 15:57:04 2020
Total files: 1

Use the show log buffer command to view a local terminal operation log buffer.

LTP-16N# show log buffer 
syslog-ng starting up; version='3.20.1'
16 Nov 15:55:41 NOTICE USRMGR         - User-manager started. 
16 Nov 15:55:41 NOTICE NETWORK-MGR    - Network-manager started. 
16 Nov 15:55:41 NOTICE LOGMGR         - Log-manager started. 
16 Nov 15:56:20 NOTICE DNA            - DNA start 
16 Nov 15:56:51 NOTICE DNA            - 10G-front-port 4 changed state to active_working 
...


When a remote syslog server is used, use the log display tools provided by the syslog server.

Enter show log <filename> command to view the files.

LTP-16N# show log LTP.log


Active alarms log

To view the active alarms log, use the show alarms command. Pass the type of events and/or their importance as parameters. You can view all active alarms by using the show alarm active all command.

LTP-16N# show alarms active all
    Active alarms (2):
     ## type           severity            description
     1 fan            critical            fan slot 1
     2 fan            critical            fan slot 2


10G-front-port monitoring

View port statistics

For 10G-front-port statistics, use the show interface 10G-front-port 1 counters command. If you want advanced statistics, enter the verbose parameter.

LTP-16N# show interface 10G-front-port 1 counters 
Port   UC packet recv   MC packet recv   BC packet recv   Octets recv      UC packet sent   MC packet sent   BC packet sent   Octets sent   
----   --------------   --------------   --------------   --------------   --------------   --------------   --------------   --------------
1                   0                0                0                0                0             3828                0           806192

View port state

To view port information such as status and SFP type, use the show interface 10G-front-port <id> state command.

LTP-16N# show interface 10G-front-port 1 state
    
Front-port             Status                 Speed                  Media               
--------------------   --------------------   --------------------   --------------------
1                      up                     1G                     copper

gpon-port monitoring

View port state

To view information about the gpon-port and SFP state for this port, use the show interface gpon-port <id> state command.

LTP-16N#  show interface gpon-port 1 state
Port   State      ONT count   SFP vendor           SFP product number   SFP vendor revision   SFP temperature [C]   SFP voltage [V]   SFP tx bias current [mA]   SFP tx power [dBm]
----   --------   ---------   ------------------   ------------------   -------------------   -------------------   ---------------   ------------------------   ------------------
1      OK         3           Ligent               LTE3680M-BC          1.0                   45                    3.27              16.84                      3.72

MAC table monitoring

LTP-16N# show mac
    Loading MAC table...

                  MAC                   port   VLAN
    00:15:17:E4:27:CA        port-channel 32   1213
    92:71:65:9C:32:5D           gpon-port 16   1213
    92:07:E6:D4:58:DC           gpon-port 16   1031
    B6:F4:D0:ED:3A:2E        port-channel 32   1031

    4 MAC entries

ONT monitoring

ONT configurations list

List of empty ONT configurations

View the list of unactivated ONTs

List of connected ONTs

List of disconnected ONTs

ONT statistics

To view ONT statistics, use the show interface ont 0/0 counters command. As parameters, specify the ONT ID and the type of requested statistics. Two types of gpon and gem-ports counters outputs are available. Gpon – shows total ONT packet statistics, including service packets. Gem-ports – statistics on user traffic within each gem-port.

LTP-16N# show interface ont 2/1 counters gem-port 
  ONT [2/1] GEM port statistics

    GEM port id            Rx Packet             Rx Bytes            Tx Packet             Tx Bytes
    129                          985                66980                    0                    0
    Broadcast                      0                    0                    0                    0
    Multicast                      0                    0               186912            255316584
LTP-16N# show interface ont 2/1 counters gpon 
  [ONT 2/1] GPON statistics


    Drift Positive:            0
    Drift Negative:            0
    Delimiter Miss Detection:  0
    BIP Errors:                0
    BIP Units:                 284296791264
    FEC Corrected symbols:     0
    FEC Codewords Uncorrected: 0
    FEC Codewords Uncorrected: 0
    FEC Codewords:             0
    FEC Corrected Units:       0
    Rx PLOAMs Errors:          0
    Rx PLOAMs Non Idle:        74
    Rx OMCI:                   292
    Rx OMCI Packets CRC Error: 0
    Rx Bytes:                  128484
    Rx Packets:                2233
    Tx Bytes:                  45504
    Tx Packets:                948
    BER Reported:              2

System environment configuration

The system has the ability to configure the fans.

Enter show system environment to view the system status.

Fans configuration

Terminal maintenance

SFP transceivers replacement

SFP transceivers can be installed when the terminal is turned on or off. The front panel has pairs of slots: even slots in the upper line, odd slots at the bottom. SFP transceivers are symmetrically installed for each pair of slots. 

                             
Figure 21 – SFP transceivers installation


Figure 22 – installed SFP transceivers

To remove a transceiver:


Figure 23 – Opening SFP transceiver latch



Figure 24 – SFP transceivers removal

Ventilation units replacement

The terminal design allows ventilation units replacement even when the terminal is on.



Figure 25 – Ventilation unit. Installation to the case


To remove a ventilation unit:


To install a ventilation unit, perform the following actions:


Power module replacement

The design of the terminal provides the possibility of replacing one of the power supply units without disconnecting power to the second.

To remove a ventilation unit:

To install a ventilation unit, perform the following actions:

OLT firmware update

This section describes the terminal firmware update procedure. To download a firmware file, use the TFTP server available in the terminal management network. The device has two areas for firmware files, with the ability to boot from the selected one.

LTP-16N# show firmware 

Select   Type     Version    Build   Date            
------   ------   --------   -----   ----------------
*        master   1.2.0      359     06.04.2021 11:36
-----------------------------------------------------
         slave    1.1.0      1519    05.11.2020 10:54
"*" designates that the image was selected for the next boot

The list of changes

Firmware version

Document version

Issue date

Revisions

1.2.0

Issue 2

28.05.2021

Synchronization with frimware version 1.2.0

1.0.0

Issue 1

30.11.2020

First issue