|| DeviceType | Optical Line Terminals |
|| DeviceName1 | LTP-8X, LTP-4X |
|| DocTitleAdditional | User manual, Issue 22 (02.11.2022) |
|| fwversion | 3.48.0 |

Terms and definitions

CBR — Constant bitrate

DBA — Dynamic bandwidth allocation

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

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

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-4X/LTP-8X terminals with internal Ethernet switch with RSSI function and 4/8 GPON ports respectively.

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

Purpose

The LTP-8X/4X 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 10GBASE-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:

• voice communications;
• HDTV;
• VoIP;
• high-speed access to the Internet;
• IPTV;
• video-on-demand (VoD);
• video conferencing;
• online educational and entertainment programs.

The device supports the following functions:

• dynamic bandwidth allocation (DBA);
• support for quality assurance mechanisms (QoS), Strict priority + WRR, GPON ports prioritisation for different types of traffic according to 802.1p;
• security functions;
• ONT remote control, automatic detection of new ONTs;
• FEC errors correction;
• power measurement support for signals received from each ONT (RSSI)1;
• VLAN organisation (VLAN ID range: 0–4094);
• MAC address filtering, 16000 entries in the MAC table;
• support for IGMP snooping v1/2/3, IGMP proxy;
• support for DHCP snooping, DHCP relay agent;
• support for PPPoE IA;
• support for Jumbo Frames up to 2000 bytes (supported on NTU-1 and SFP-NTU-100).

Scroll Pagebreak

Delivery package

The standard delivery package includes:

1. LTP-4X/8X optical line terminal;
2. Mounting set for 19'' rack;
3. RS-232 DB9(F) — DB9(F) console cable for LTP rev.B; RJ-45 — DB9(F) console cable for LTP rev.С and rev.D;
4. CD with User Manual and Quick Configuration Manual (optionally);
5. Power cable (if equipped with 220 V power module);
6. Passport.

Technical specifications

Table 1 — Main specifications of the line terminal

Scroll Pagebreak

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.  The following table lists SFP transceivers for which seamless terminal operation is guaranteed.

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

Table 2 — List of compatible SFP transceivers

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 the figures below. Tables 3 and 4 list connectors, LEDs and controls located on the front panel of the terminal.

Figure 1 — LTP-4X rev.B front panel layout

Figure 2 — LTP-8X rev.B front panel layout

Figure 3 – LTP-4X rev.C/rev.D front panel layout 

 
Figure 4 — LTP-8X rev.C/rev.D front panel layout

Table 3 — Description of the connectors, LEDs, and controls located on the front panel of LTP-4X/8X rev.B

Scroll Pagebreak

Rear panel

The rear panel layout of the device is depicted in Fig. 5, 6, 7.

Table below lists rear panel connectors. 

Figure 5 — LTP-4X/8X (DC) rear panel layout

Figure 7 — Rear panel layout of LTP-4X/8X rev.C, LTP-4X/8X rev.D with two power modules

Table 5 — Rear panel connectors description

Scroll Pagebreak

Light indication 

The indicators located on the front panel show the status of the terminal. Indicator states are listed in Tables 6 and 7.

Table 6 — LTP-4X/8X rev.B status light indication

Table 7 — LTP-4X/8X rev.C/rev.D status light indication

Temperature sensors

2 temperature sensors are used to measure temperature inside the terminal case.

Figure below shows the sensor location on PCB.

Figure 8 — Temperature sensors allocation

Ventilation system

There are ventilation openings on the device rear, front and side panels that serve to remove heat. The rear panel has two ventilation units installed (Figure 5, Figure 6 and Figure 7).

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

The device contains 2 fans. The ventilation units are detachable. The procedure for assembly and dismantling is described in Ventilation Units Replacement.

Safety rules and installation procedure

This chapter describes how to install the terminal in a rack and connect it to the power supply.

Safety requirements

General requirements
Any operations with the equipment should comply to the "Safety Regulations for Operation of Consumer's Electrical Installations".

1. Before operating the device, all engineers should undergo special training.
2. The terminal should be connected only to properly functioning supplementary equipment.
3. The device could be permanently used under the following conditions:
   • ambient temperature from -5 to +40 °C;
   • relative humidity up to 80 % at +25 °C;
   • atmosphere pressure from 6.0×10⁴ to 10.7×10⁴ Pa (from 450 to 800 mm Hg).
4. The terminal should 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 Ω. Any PC and measurement instruments should be properly grounded prior to their connection to the terminal. The potential difference between the equipment case and the cases of the instruments should be less than 1 V.
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. Power modules of LTP-X rev.B should be replaced only when the device is powered off. Follow the procedure in Terminal installation. Power modules of LTP-X rev.C/rev.D terminals can be installed and removed without powering the device off.
5. 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:

• Step 1. Align four mounting holes in the support bracket with the corresponding holes in the side panel of the device.
• Step 2. Use a screwdriver to screw the support bracket to the case.
• Step 3. Repeat steps 1 and 2 for the second support bracket.

Figure 9 — Support brackets mounting

Terminal rack installation
To install the terminal to the rack:

• Step 1. Attach the terminal to the vertical guides of the rack.
• Step 2. Align mounting holes in the support bracket with the corresponding holes in the rack guides. Use the holes of the same level on both sides of the guides to ensure the device horizontal installation.
• Step 3. Use a screwdriver to screw the terminal to the rack. 

Figure 10 — 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.

Power module installation

Depending on power supply requirements, the LTP-4X/8X rev.B terminals can be supplemented with either an AC power module, 220 V, 50 Hz, or a DC power module, 48 V. Location of the power module is shown in Figure 11.

Figure 11 — Power module installation

The LTP-4X rev.C/rev.D and LTP-8X rev.C/rev.D terminals can use one or two power modules. The second power module installation is necessary when greater reliability is required. In case of using two power modules, it is allowed to use different power plants for supplying (with different voltage).

Figure 12 — Power module installation for LTP rev.C/rev.D

From the electric point of view, both places for power module installation are identical. In the context 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 additional power module is inserted or removed, the terminal continues operation without reboot.
To install a power module:

• Step 1. Install the power module into the socket shown in Fig. 11 or Fig. 12.
• Step 2. Screw the module to the case.
• Step 3. Follow the instructions in Terminal installation to power on.

The device installation order:

• Step 1. Mount the device. In case of installation to a 19" form-factor rack, mount the support brackets from the delivery package to the rack.
• Step 2. Ground the case of the device. This should be done prior to connecting the device to the power supply. An insulated multiconductor wire should be used for earthing. The device grounding process and the earthing wire section should comply with Electric Installation Code. The earth bonding point is located on the rear panel, see Figure 5, Figure 6 and Figure 7.
• Step 3. If you intend to connect a PC or another device to the switch console port, the device must be properly grounded as well.
• Step 4. Connect the power supply cable to the device.
• Step 5. Turn the device on and check the front panel LEDs to make sure the terminal is in normal operating conditions.

Getting started with the terminal

Connecting to the terminal CLI

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

A serial port (hereafter — COM port) is recommended to use for the initial configuration 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.

• Step 1. Use the null modem cable from the delivery package to connect the console port of the terminal to the PC COM port as shown in figure below. 

Figure 13 — Connecting the terminal to a PC via COM port

• Step 2. Launch the terminal program and create a new connection. Select the corresponding COM port in the Connect to drop-down list. Assign the port settings according to the table below. Click <OK>.
  Table 8 — Port specifications

  Parameter	Value
  Speed	115200
  Data bits	8
  Parity	No
  Stop bits	1
  Flow control	None

  
  

• Step 3. Press <Enter>. Log into the terminal CLI.

  Примечание
  Factory authorization settings:  login: admin, password: password.

  
  

  Блок кода
  language xml
  ******************************************** * Optical line terminal LTP-8X rev.D * ******************************************** LTP-8X login: admin Password: ******** Eltex LTP-8X-rev.D software version 3.40.0 build 2358 on 10.12.2020 15:32 Technical support: https://eltex-co.ru/support Mon Dec 28 10:56:29 LOCAL 2020 LTP-8X#

  
  

Connecting to CLI via Telnet protocol

The Telnet protocol connection is more universal 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). Additionally you will need a network cable (Patching Cord RJ-45) of the required length, as it is not included in the
terminal delivery package.

• Step 1. Connect one end of the network cable to any "GE Port" or "Combo GE" port of the terminal. Connect another end to NIC on the PC as shown in the figure below.

Figure 14 — Connecting the terminal to a PC via network cable

• Step 2. Assign IP settings for network connections. Set 192.168.1.1 as an IP address and 255.255.255.0 as a subnet mask.

Figure 15 — Network connection configuration

• Step 3. On the PC, click Start > Run. Enter the telnet command and the terminal's IP address. The factory setting for the IP address is 192.168.1.2. Click <OK>.

Figure 16 — Telnet client startup

• Step 4. Log into the terminal CLI.

  Примечание
  Factory authorization settings: login: admin, password: password.

  
  

  Блок кода
  language xml
  Trying 192.168.1.2... Connected to 192.168.1.2. Escape character is ’^]’. ******************************************** * Optical line terminal LTP-8X rev.D * ******************************************** login: admin Password:******** Eltex LTP-8X-rev.D software version 3.40.0 build 2358 on 10.12.2020 15:32 Technical support: https://eltex-co.ru/support Mon Dec 28 10:56:29 LOCAL 2020

  
  

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. Additionally you will need a network cable (Patching Cord RJ-45) of the required length, as it is not included in the terminal delivery package.

• Step 1. Perform steps 1 and 2 from the Connecting to CLI via COM port section.
• Step 2. Run PuTTY. Enter IP address of the terminal. The factory setting for the IP address is 192.168.1.2. Select port 22 and SSH protocol type. Click <Open>.

Figure 17 — SSH client startup

• Step 3. Log into the terminal CLI. Factory authorization settings:
  login: admin, password: password.

  Блок кода
  language xml
  login: admin Password: ******** Eltex LTP-8X-rev.D software version 3.40.0 build 2358 on 10.12.2020 15:32 Technical support: https://eltex-co.ru/support Mon Dec 28 10:56:29 LOCAL 2020 LTP-8X#

  Scroll Pagebreak

Getting started with terminal CLI

CLI is the main means of communication between user and the terminal. This chapter considers general operations in CLI: commands grouping, automatic code completion, and history.

CLI views hierarchy

Views are used in the terminal CLI to group commands and optimize their length.

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

 
Figure 18 — CLI mode hierarchy

• The Top view includes general commands, which refer to the device in general. For example: view terminal parameters, firmware update, reboot, etc.;
• The Switch configure view groups commands related to the switch: VLAN, GE interfaces, LACP and others;
• The Configure view is a list of terminal configuration commands. E.g. user management, services configuration, GPON interface and ONT configuration, profile configuration, etc.

Figure 19 — Switch view hierarchy

 
Figure 20 — Configure view hierarchy

Figure 20 shows the Configure view, which consists of four parts:

• The GPON-port view is used to configure GPON interfaces;
• The ONT view is used to configure the ONT;
• ONT configuration templates are modified in the ONT template view;
• The profile of the terminal configuration is configured in the Profile view.

CLI hotkeys

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

CLI automatic command completion

In order to make work with CLI faster and easier, an automatic command completion is implemented. A good knowledge of CLI command system allows user to work with CLI as fast as with graphical interface.

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

LTP-8X# ex<Tab> 
LTP-8X# 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-8X# co<Tab> 
commit configure copy 
LTP-8X# con<Tab> 
LTP-8X# configure

CLI command history

Sometimes it might be necessary to execute the same set of operations several times. To make the work with repeating commands easier, the terminal CLI keeps the command history.

The list of previously entered commands can be displayed by using the show history command.

LTP-8X# show history 
Last CLI commands: 
show version 
configure terminal 
exit 
show history
LTP-8X#

Use the <Up> and <Down> cursor keys to scroll the command history and the <Enter> key to execute the selected command.

LTP-8X# <Up> 
LTP-8X# show management <Up> 
LTP-8X# switch <Up> 
LTP-8X# exit <Up> 
LTP-8X# show uptime <Enter> 
up 1 day, 23:44

Scroll Pagebreak

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 fec for all ONTs in a certain channel.

LTP-8X(config)# interface ont 0/0-127 
LTP-8X(config)(if-ont-0/0-127)# fec

Or view the list of active ones in the first 4 GPON channels.

LTP-8X# show interface ont 0-3 ont online 

GPON-port 0 has no online ONTs
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

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

Configuration structure

The terminal configuration can be conventionally divided into 3 parts. Figure below shows the configuration structure.

 
Figure 21 — Terminal configuration structure

System is a general system part. This group includes such settings as: network, service settings, user table, etc.
Switch represents a switch configuration. This group includes configuration parameters for Ethernet interfaces of the front panel, as well as VLAN settings.
GPON contains 5 subparts:

• OLT — GPON OLT and GPON interface settings;
• OLT profiles — OLT profile part consists of address table profiles, VLAN profiles, DHCP RA and PPPoE IA profiles;
• ONT — ONT configuration base;
• ONT templates — ONT templates;
• ONT profiles — ONT profiles.

Configuration lifecycle

The terminal configuration may have the following states:

• RUNNING— active configuration. It refers to the current configuration of the terminal;
• CANDIDATE— an edited configuration;
• NVRAM — a configuration stored in non-volatile memory. This configuration will be used as RUNNING after the device is loaded.

The RUNNING configuration is loaded to a new CLI session and becomes available for review (CANDIDATE). After changing the configuration (CANDIDATE) in the CLI session, user can either enter the commit command to accept the changes or use the rollback command to discard the changes and apply the current (RUNNING) configuration. The save command saves the RUNNING configuration into NVRAM of the terminal.
Figure below shows a chart of configuration lifecycle.

Figure 22 — Configuration lifecycle of the terminal diagram

Configuration autosave

In some cases, for example, when several operators are working on the terminal or the terminal is automatically configured through OSS/BSS, it may be convenient to organize a centralized saving of the configuration into NVRAM at a specified time or at a specified time interval. The terminal allows this with the help of a configuration autosave mechanism.

For daily autosave of the configuration, define a time when autosave should be implemented.

LTP-8X(config)# config autosave hour 3 minute 44

For autosave at specified time intervals, define the interval in seconds.

LTP-8X(config)# config autosave period 3600

Check the entered data by using the do show config command.

LTP-4X(config)# do show config 
	Config: 
		Daily autosave: at 03:44 
		Periodic autosave: every 3600 seconds 
	   LTP-4X(config)#

LTP-4X(config)# no config autosave hour 
LTP-4X(config)# no config autosave period

Apply the changes.

LTP-8X(config)# do commit

Creating a configuration backup

Configuration backups allow the terminal operation to be quickly restored after abnormal situations or replacement. Manual or triggered (on events) creation of backups is recommended at a regular basis.

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-8X# copy fs://config tftp://192.168.1.1/config 
Upload backup file to TFTP-server..

  Configure a triggered upload to create backups automatically.

• Step 1. Go to the configure view and select the URI of the configuration backup.

  Блок кода
  language xml
  LTP-8X# configure terminal LTP-8X(config)# backup uri tftp://192.168.1.1/config

  
  

• Step 2. The terminal can be adjusted to upload configuration every time the configuration is saved if necessary.

  Блок кода
  language xml
  LTP-8X(config)# backup on save

  
  

• Step 3. The terminal can be adjusted to use a timer for configuration upload if necessary. In this case, additionally set the timer period in seconds.

  Блок кода
  language xml
  LTP-8X(config)# backup on timer LTP-8X(config)# backup timer period 3600

  
  

• Step 4. Check the entered data by using the do show backup command. 
  

  Блок кода
  language xml
  LTP-8X(config)# do show backup Tftp: Backup on conf save: enabled Backup on timer: enabled Backup on timer period: 3600 Backup uri: ’tftp://192.168.1.1/config’

  Scroll Pagebreak

• Step 5. Apply the changes. 
  

  Блок кода
  language xml
  LTP-8X(config)# do commit

  
  

Configuration restore

The terminal configuration is restored from the TFTP/FTP/HTTP 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-8X# 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.

LTP-8X# default 
	Do you really want to set up default configuration? (y/n) y 
	Configuration have been reseted to default. 

	Terminal will be reloaded.

Scroll Pagebreak

Network settings

This chapter 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.

• Step 1. Use the show management command to view the current network settings.

  Блок кода
  language xml
  LTP-8X# show management Network: Hostname: ’LTP-8X’ Ipaddr: 192.168.1.2 Netmask: 255.255.255.0 Vlan management: 1 Gateway: 0.0.0.0 Vlan prio: 7 Dscp: 63 Additional vlan: <list is empty>

  
  

• Step 2. Switch to the configure view. Set the terminal name by using the hostname command.

  Блок кода
  language xml
  LTP-8X# configure terminal LTP-8X(config)# hostname LTP-8X-1

  
  

• Step 3. Set the terminal IP address by using the management ip command.

  Блок кода
  language xml
  LTP-8X(config)# management ip 10.0.0.1

  
  

• Step 4. Set the subnet mask by using the management mask command.

  Блок кода
  language xml
  LTP-8X(config)# management mask 255.0.0.0

  
  

• Step 5. Set the default gateway by using the management gateway command.

  Блок кода
  language xml
  LTP-8X(config)# management gateway 10.0.0.254

  
  

• Step 6. Set the management VLAN of the terminal by using the management vid command if necessary. Use the management cos command to set the P-bit parameter for the management VLAN.

  Блок кода
  language xml
  LTP-8X(config)# management vid 9 LTP-8X(config)# management cos 5

  
  

  Примечание
  Proper operation of the inband management function requires VLAN adjustment in the switch view as described in VLAN configuration.

  
  

• Step 7. Set MAC address aging time by using the gpon network mac-age-time command.

  Pass the time in seconds as a parameter.

  Блок кода
  language xml
  LTP-8X(config)# gpon network mac-age-time 7200

  
  

• Step 8. The network settings will change as soon as the configuration is applied. No terminal reboot is needed.

  Блок кода
  language xml
  LTP-8X(config)# do commit

  Scroll Pagebreak

User management

This chapter is devoted to management of the terminal users.

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 level of privileges. Level 0 corresponds to a minimum set of permissions, Level 15 — to a maximum set of permissions.

CLI commands are ranked by the level of privileges. Level 0 commands 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.

The levels of privileges can be modified as required.

• Step 1. Check the current settings of privileges by using the show privileges command.

  Блок кода
  language xml
  LTP-8X# show privileges Level Privileges 0 !, exit 1 view-ont 2 ont-operation 3 view-ont, ont-operation 4 view-ont, config-ont ont-operation 5 view-gpon, view-ont view-ont-profile, ont-operation 6 view-gpon, view-ont view-ont-profile, config-gpon ont-operation, config-ont-profile 7 view-switch, view-gpon view-ont, view-ont-profile view-switch-interfaces 8 view-switch, view-gpon view-ont, view-ont-profile view-switch-interfaces, config-switch config-switch-interfaces

  
  

  Блок кода
  language xml
  9 view-switch, view-gpon view-ont, view-ont-profile view-switch-interfaces, config-switch config-gpon, config-ont ont-operation, config-ont-profile config-switch-interfaces 10 view-switch, view-alarm view-system, view-general view-gpon, view-ont view-ont-profile, view-switch-interfaces 11 view-switch, view-alarm view-system, view-general view-gpon, view-ont view-ont-profile, view-switch-interfaces config-alarm, config-system config-general 12 view-switch, view-alarm view-system, view-general view-gpon, view-ont view-ont-profile, view-switch-interfaces config-switch, config-alarm config-system, config-general config-switch-interfaces 13 view-gpon, view-ont view-ont-profile 14 — 15 view-switch, view-alarm view-system, view-general view-gpon, view-ont view-ont-profile, view-switch-interfaces config-switch, config-alarm config-system, config-general config-gpon, config-ont ont-operation, config-ont-profile config-switch-interfaces

  
  

• Step 2. Switch to the configure view. Set the required permissions corresponding to the level by using the privilege command, e. g. set permissions allowing Level 1 to view configuration of the internal switch.

  Блок кода
  language xml
  LTP-8X# configure terminal LTP-8X(config)# privilege 1 view-switch

  
  

• Step 3. Settings of privileges will be applied immediately. No terminal reboot is needed.

  Блок кода
  language xml
  LTP-8X(config)# do commit

  The list of operations and the default levels are shown in the table below.

  Scroll Pagebreak

  Table 9 — Permissions and the required level of privileges

  Level	Privileges
  0	!, exit
  1	view-ont
  2	ont-operation
  3	view-ont, ont-operation
  4	view-ont, config-ont, ont-operation
  5	view-gpon, view-ont, view-ont-profile, ont-operation
  6	view-gpon, view-ont, view-ont-profile, config-gpon, ont-operation, config-ont-profile
  7	view-switch, view-gpon, view-ont, view-ont-profile, view-switch-interfaces
  8	view-switch, view-gpon, view-ont, view-ont-profile, view-switch-interfaces, config-switch, config-switch-interfaces
  9	view-switch, view-gpon, view-ont, view-ont-profile, view-switch-interfaces, config-switch, config-gpon, config-ont, ont-operation, config-ont-profile, config-switch-interfaces
  10	view-switch, view-alarm, view-system, view-general, view-gpon, view-ont, view-ont-profile, view-switch-interfaces,
  11	view-switch, view-alarm, view-system, view-general, view-gpon, view-ont, view-ont-profile, view-switch-interfaces, config-alarm, config-system, config-general
  12	view-switch, view-alarm, view-system, view-general, view-gpon, view-ont, view-ont-profile, view-switch-interfaces, config-switch, config-alarm, config-system, config-general, config-switch-interfaces
  13	view-gpon, view-ont, view-ont-profile
  14	—
  15	view-switch, view-alarm, view-system, view-general, view-gpon, view-ont, view-ont-profile, view-switch-interfaces, config-switch, config-alarm, config-system, config-general, config-gpon, config-ont, ont-operation, config-ont-profileconfig-switch-interfaces

  
  

User list preview

To view the list of terminal users, enter the show users config command.

LTP-8X(config)# do show users config 
    ##                Name      Privilege
     1                root           15
     2               admin           15
     3              remote           15

The admin, root and remote 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-8X(config)# user operator
LTP-8X(config)# do show users config 
    ##                Name      Privilege
     1                root           15
     2               admin           15
     3              remote           15
     4            operator            0
LTP-8X(config)#

Pass the name of the new user to the user command as a parameter. 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.

LTP-8X(config)# user operator password newpassword

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-8X(config)# user operator
LTP-8X(config)# do show users config 
    ##                Name      Privilege
     1                root           15
     2               admin           15
     3              remote           15
     4            operator            0
LTP-8X(config)#

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

LTP-8X(config)# user operator priviledge 15
LTP-8X(config)# do show users config 
    ##                Name      Privilege
     1                root           15
     2               admin           15
     3              remote           15
     4            operator           15
LTP-8X(config)#

Deleting a user

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

LTP-8X# configure terminal 
LTP-8X(config)# no user operator

ААА configuration

This chapter describes configuring of services and protocols related to authentication, authorization and accounting.

LTP-X supports radius and tacacs+ AAA protocols. Below is a table of the functionality of these protocols.

Table 10 — Permissions and the required level of privileges

Configuring servers

The principles of servers configuration are common for supported protocols. You can configure an IP address, key, response timeout and a data exchange port for each server. You can set up to 3 servers for the RADIUS. The LTP will apply to the servers according to their priorities. If the priority is not set, the 0 priority (the highest) will be used by default.

• Step 1. Configure IP address of radius/tacacs+ server.

  Блок кода
  language xml
  LTP-8X# configure terminal LTP-8X(config)# radius-server host 10.10.10.1 priority 0 LTP-8X(config)# radius-server host 10.10.10.2 priority 1 LTP-8X(config)# radius-server host 10.10.10.3 priority 2 LTP-8X(config)# tacacs-server host 10.10.10.4

  
  

• Step 2. Define an encryption key used while data exchange with the server.

  Блок кода
  language xml
  LTP-8X(config)# radius-server key 12345678-r0 LTP-8X(config)# radius-server key 12345678-r1 priority 1 LTP-8X(config)# radius-server key 12345678-r2 priority 2 LTP-8X(config)# tacacs-server key 12345678

  Scroll Pagebreak

• Step 3. Define server response timeout.

  Блок кода
  language xml
  LTP-8X(config)# radius-server timeout 3 LTP-8X(config)# radius-server timeout 3 priority 1 LTP-8X(config)# radius-server timeout 3 priority 2 LTP-8X(config)# tacacs-server timeout 3

  
  

• Step 4. Define a port for data exchange with the server (if necessary). 
  

  Блок кода
  language xml
  LTP-8X(config)# radius-server port 50005 LTP-8X(config)# radius-server port 50006 priority 1 LTP-8X(config)# radius-server port 50007 priority 2 LTP-8X(config)# tacacs-server port 50008

  
  

• Step 5. Apply the changes.
  

  Блок кода
  language xml
  LTP-8X(config)# do commit

  
  

AAA methods configuration

By default, every AAA function is implemented locally — local user data base is used for authentication and authorization, accounting via a remote server is disabled.

For using of configured in previous steps servers, define a method of a function performing.

• Step 1. Select an authentication method.

  Блок кода
  language xml
  LTP-8X# configure terminal LTP-8X(config)# aaa authentication radius

  
  

• Step 2. Select an authorization method.

  Блок кода
  language xml
  LTP-8X# configure terminal  LTP-8X(config)# aaa authorization tacacs+

  
  

• Step 3. Select a CLI session start/stop accounting method.

  Блок кода
  language xml
  LTP-8X# configure terminal LTP-8X(config)# aaa accounting start-stop radius

  
  

• Step 4. Select a method of commands accounting.
  

  Блок кода
  language xml
  LTP-8X# configure terminal LTP-8X(config)# aaa accounting commands tacacs+

  Scroll Pagebreak

• Step 5. Apply the changes.
  

  Блок кода
  language xml
  LTP-8X(config)# do commit

  In order to disable a function, use the no command.

  Блок кода
  language xml
  LTP-8X# configure terminal LTP-8X(config)# no aaa accounting commands

  
  

Services configuration

This chapter describes configuration of integrated terminal services.

SNMPD configuration

To work with the Eltex.EMS management system, the terminal should be configured to work with Simple Network Management Protocol (SNMP).

• Step 1. Switch to the configure view.

  Блок кода
  language xml
  LTP-8X# configure terminal

  
  

• Step 2. Enable the SNMP agent of the terminal by using the snmp enable command.

  Блок кода
  language xml
  LTP-8X(config)# ip snmp enable

  
  

• Step 3. Enable ACL check by using the snmp access-control command if necessary. Add the record into the whitelist by using the snmp allow command. Pass the IP address of the host which will be used to connect to the SNMP agent, as a parameter.

  Блок кода
  language xml
  LTP-8X(config)# ip snmp access-control LTP-8X(config)# ip snmp allow ip 192.168.1.13

  
  

• Step 4. Configure SNMP trap replication to allow the management system to receive the traps. For example, add 2 replicators and specify to send v2 SNMP traps to 192.168.1.13 and v1 traps to 192.168.1.113. To do this, use the ip snmp traps command. 
  

  Примечание
  It is possible to configure several receivers of SNMP traps of the same version.

  
  

  Блок кода
  language xml
  LTP-8X(config)# ip snmp traps 192.168.1.13 type v2 LTP-8X(config)# ip snmp traps 192.168.1.113 type v1

  Scroll Pagebreak

• Step 5. Check the entered data by using the show ip snmp command.

  Блок кода
  language xml
  LTP-8X(config)# do show ip snmp Snmp: Enabled: true Access control: false Allow ip: <list is empty> Traps [0]: Type: v2 Ipaddr: 192.168.1.13 Traps [1]: Type: v1 Ipaddr: 192.168.1.113 Version: v2 Community read-only [0]: 'QwYva0dvS3N' Community read-only [1]: 'QwYva0dvS3N' Community read-only [2]: 'QwYva0dvS3N' Community read-write [0]: 'LQtfx9v3m9+qA==' Community read-write [1]: 'LQtfx9v3m9+qA==' Community read-write [2]: 'LQtfx9v3m9+qA==' Trap community: '9qXUEDwUMAg' Location: 'admin' Contact: 'admin' Alias: <for showing use separate command> EngineID: 0x6C2A20B42CB28232FABEA8EE19 Users: <for showing use separate command>

  
  

• Step 6. The settings of the SNMP agent change as soon as the configuration is applied.

  No terminal reboot is needed.

  Блок кода
  language xml
  LTP-8X(config)# do commit

  
  

You need to configure users to operate with SNMPv3. 

• Step 1. Set the version of SNMP agent to 3.

  Блок кода
  language xml
  LTP-8X(config)# ip snmp version v3

  
  

• Step 2. Add users and set the privilege levels.

  Блок кода
  language xml
  LTP-8X(config)# ip snmp user "rwuser" auth-password "rwpass" enc-password "rwencr" access rw LTP-8X(config)# ip snmp user "rouser" auth-password "ropass" enc-password "roencr" access ro

  Scroll Pagebreak

• Step 3. Check the configuration.

  Блок кода
  language xml
  LTP-8X(config)# do show ip snmp users SNMP users ~~~~~~~~~~ User name permissions -------------------- --------------- rwuser read-write rouser read-only 2 SNMP users.

  
  

NTPD configuration

The terminal has no integrated real-time clocks with a battery. For the events in system log to show correct time and for automated operations to be performed in time, time synchronisation should be adjusted with the help of the NTP protocol.

• Step 1. Switch to the configure view.

  Блок кода
  language xml
  LTP-8X# configure terminal

  
  

• Step 2. Enable time synchronisation by using the ip ntp enable command. Specify the IP address to be used for synchronisation in the ip ntp ip command.

  Блок кода
  language xml
  LTP-8X(config)# ip ntp enable LTP-8X(config)# ip ntp ip 192.168.1.254

  
  

• Step 3. Specify the synchronisation interval in seconds by using the ip ntp interval command.

  Блок кода
  language xml
  LTP-8X(config)# ip ntp interval 3600

  
  

• Step 4. Use the ip ntp timezone and ip ntp daylightsaving commands to set the time zone of your region and indicate whether it should be switched to the daylight-saving time.

  Блок кода
  language xml
  LTP-8X(config)# ip ntp timezone 7 LTP-8X(config)# ip ntp daylightsaving

  Scroll Pagebreak

• Step 5. Check the entered data by using the do show ip ntp command. 
  

  Блок кода
  language xml
  LTP-8X(config)# do show ip ntp Ntp: Enabled: true Ntpserver: 192.168.1.254 Interval: 3600 Timezone: 7 Daylightsaving: true LTP-8X(config)#

  
  

• Step 6. Apply the configuration by using the commit command. 
  

  Блок кода
  language xml
  LTP-8X(config)# do commit

  
  

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 23 — Terminal system log

Table 11 — System log modules

Table 12 — System log filtering levels

Table 13 — System log output device

The log is saved in non-volatile memory by default. The system has 4 log rotated files of 1M each. The last 3 logs are archived to gzip.

Module configuration

Consider module configuration by the example of the pmchal-gpon module responsible for messages from the GPON subsystem. Other modules have similar configuration process.

• Step 1. Set the logging level using the logging module pmchal-gpon loglevel command.

  Блок кода
  language xml
  LTP-8X(config)# logging module pmchal-gpon loglevel info

  
  

• Step 2. To view information about modules, use the do show logging module pmchal-gpon command.

  Блок кода
  language xml
  LTP-8X(config)# do show logging module pmchal-gpon Log: Submodule [pmchal-gpon]: Log level: notice LTP-8X(config)#

  
  

• Step 3. Apply the configuration by using the commit command.

  Блок кода
  language xml
  LTP-8X(config)# do commit

  Scroll Pagebreak

Configuring command logging to syslog

The system is capable to record all the user's commands to syslog. Use the following command to activate the function.

LTP-8X(config)# logging commands

Configuring the Origin parameter

The system can add an additional origin-id parameter to messages sent to the Syslog server. It will be added to the beginning of the log message.

Only one additional parameter can be used at a time.

LTP-8X(config)# logging origin-id 
   hostname      The sysname will be used as the hostname field of a
                 syslog message
   string        The user defined string will be used as the hostname
                 field of syslog header
   ip            The IP address of the sending interface will be used
                 as the hostname field of a syslog message

Configuring the log storage

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

LTP-8X(config)# logging permanent

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

System log configuration

• Step 1. Use the logging buffer command to specify the memory size in bytes to be used for system log storage.

  Блок кода
  language xml
  LTP-8X(config)# logging buffer 262144

  
  

• Step 2. If necessary, use the logging remote command to specify the IP address of the remote Syslog server to be used to display system log.

  Блок кода
  language xml
  LTP-8X(config)# logging remote 192.168.1.43

  Scroll Pagebreak

• Step 3. Configure the output devices by using the logging command.

  Информация
  Every output device may have its own filtering level or have the output disabled.

  For example, it is possible to change the display level for the CLI sessions, which are not connected via the RS-232 console port, to "info" and disable output to file.

  Блок кода
  language xml
  LTP-8X(config)# logging rsh loglevel info LTP-8X(config)# logging file loglevel none

  
  

• Step 4. To view Syslog configuration, use the do show logging settings command.

  Блок кода
  language xml
  LTP-8X(config)# do show logging settings Log: Remote syslog: 192.168.1.30 Remote syslog: 192.168.1.31 Remote syslog: 192.168.1.55:520 Remote syslog: 192.168.1.33 Size: 16384 Save logs between boots: true Log input commands: false Destinations: System: notice Console: notice Remote shells: info File: none

  
  

• Step 5. Apply the configuration by using the commit command. 
  

  Блок кода
  language xml
  LTP-8X(config)# do commit

  
  

Scroll Pagebreak

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.

* The value can be adjusted.

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

Active alarms log configuration

• Step 1. To configure the active alarms log, switch to the configure view.

  Блок кода
  language xml
  LTP-8X# configure terminal

  
  

• Step 2. Use the alarm command to specify the necessary event parameters. Event types are listed in Table 14, the parameters and possible values are given in Table 15.

  Блок кода
  language xml
  LTP-8X(config)# alarm temperature severity critical LTP-8X(config)# alarm temperature in LTP-8X(config)# alarm temperature out LTP-8X(config)# alarm temperature ttl 0

  
  

• Step 3. Apply the changes by using the do commit command.

  Блок кода
  language xml
  LTP-8X(config)# do commit

  
  

VLAN Configuration

Якорь
Настройка VLAN Настройка VLAN

This chapter describes VLAN configuration in the terminal switch.

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 has two or more switch interfaces. A VLAN member interface can be either tagged or untagged. An outgoing packet of a tagged interface has a VLAN tag. An outgoing packet of an untagged interface has no VLAN tags. For more information about the configuration and rules of operation of interfaces, see the FW 3.48.0 OLT LTP-8X, LTP-4X. User manual#VLAN Configuration.

Adding VLAN

• Step 1. VLAN is configured in the terminal switch. Use the switch and configure commands consecutively to switch to the config view.

  Блок кода
  language xml
  LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)#

  
  

• Step 2. Add a VLAN by using the vlan command. Pass VID as a parameter.

  Блок кода
  language xml
  LTP-8X(switch)(config)# vlan 5 LTP-8X(switch)(config-vlan)#

  
  

VLAN Configuration

• Step 1. Add tagged interfaces by using the tagged command. Pass interface type and number (or a range) as parameters. The interface types and numbers are given in Table 19, in the Interface configuration section.

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# tagged pon-port 0 – 1

  
  

• Step 2. Add untagged interfaces by using the untagged command if needed. Pass interface type and number (or a range) as parameters.

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# untagged front-port 1

  
  

• Step 3. Delete all unnecessary interfaces from the VLAN by using the forbidden command. Pass interface type and number (or a range) as parameters.

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# forbidden 10G-front-port 0 – 1 LTP-8X(switch)(config-vlan)# forbidden front-port 0 , front-port 2 , front-port 3

  
  

• Step 4. Disable IGMP snooping by using the no ip igmp snooping enable command if needed. 
  

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# no ip igmp snooping enable

  
  

• Step 5. Configure the IGMP querier if needed. It can be enabled by using the ip igmp snooping querier enable command.

  The fast-leave mode is enabled by using the ip igmp snooping querier fast-leave command. By default, this mode is disabled.

  Scroll Pagebreak

  
  DSCP and 802.1P marking for IGMP query is configured by using the ip igmp snooping querier user-prio and ip igmp snooping querier dscp commands.
  The upstream IGMP packet source IP address spoofing is configured by using the ip igmp snooping replace source-ip command.

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ip igmp snooping querier enable LTP-8X(switch)(config-vlan)# ip igmp snooping querier fast-leave LTP-8X(switch)(config-vlan)# ip igmp snooping querier user-prio 4 LTP-8X(switch)(config-vlan)# ip igmp snooping querier dscp 40 LTP-8X(switch)(config-vlan)# ip igmp snooping replace source-ip 192.168.21.2

  
  

• Step 6. Configure IGMP if needed.

  Compatible versions (v1, v2, v3, or their combination):

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ip igmp version v2-v3

  Interval between queries:

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ip igmp query-interval 125

  Maximum query response time:

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ip igmp query-response-interval 10

  Interval between Group-Specific Queries:

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ip igmp last-member-query-interval 1

  Robustness:

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ip igmp robustness 2

  
  

• Step 7. Disable MLD snooping by using the no ipv6 mld snooping enable command if needed.

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# no ipv6 mld snooping enable

  
  

• Step 8. Configure the MLD querier if needed. It can be enabled by using the ipv6 mld snooping querier enable command.

  The fast-leave mode is enabled by using the ipv6 mld snooping querier fast-leave command. By default, this mode is disabled.
  DSCP and 802.1P marking for MLD query is configured by means of the ipv6 mld snooping querier user-prio and ipv6 mld snooping querier dscp commands.

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ipv6 mld snooping querier enable LTP-8X(switch)(config-vlan)# ipv6 mld snooping querier fast-leave LTP-8X(switch)(config-vlan)# ipv6 mld snooping querier user-prio 4 LTP-8X(switch)(config-vlan)# ipv6 mld snooping querier dscp 40

  
  

• Step 9. Configure MLD if needed.

  Compatible versions (v1, v2):

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ipv6 mld version v1-v2

  Interval between queries:

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ipv6 mld query-interval 125

  Maximum query response time:

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ipv6 mld query-response-interval 10

  Interval between Group-Specific Queries:

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ipv6 mld last-member-query-interval 1

  Robustness:

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# ipv6 mld robustness 2

  
  

• Step 10. For further convenience, specify a VLAN name by using the name command. To clear the name, use the no name command. The default name is VID.

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# name iptv

  
  

• Step 11. Apply the configuration by using the commit command. 
  

  Блок кода
  language xml
  LTP-8X(switch)(config-vlan)# exit LTP-8X(switch)(config)# commit

  
  

Scroll Pagebreak

VLAN Deletion

• Step 1. Delete a VLAN by using the no vlan command. Pass VID (or its range) as a parameter.

  Блок кода
  language xml
  LTP-8X(switch)(config)# no vlan 5

  
  

Configuring access control list and policy

ACL (Access Control List) — the table which defined filtering rules for incoming traffic according to data transmitted in the incoming packets: protocols, TCP/UDP ports, IP address or MAC address. The ACL based on IPv4 and MAC should have different names. You can set one type of the lists per interface. Each access list contains up to 20 rules.

Configuring MAC access-list

In a MAC access list, filtering is implemented according to the following criteria and a mask:

Table 16 — The list of MAC access-list criteria

• Step 1. Create a mac access-list.

LTP-8X# switch 
LTP-8X(switch)# configure terminal
LTP-8X(switch)(config)# mac access-list extended eltexsrc

• Step 2. Configure rules and assign the list to a port.

  Блок кода
  language xml
  LTP-8X(switch)(config-mac-al)# deny A8:f9:4B:00:AA:00 FF:FF:FF:FF:FF:00 any LTP-8X(switch)(config-mac-al)# deny any any vlan any cos 7 7 LTP-8X(switch)(config-mac-al)# permit A8:F9:4B:00:00:00 FF:FF:FF:00:00:00 any vlan 2 cos 4 4 LTP-8X(switch)(config-mac-al)# exit LTP-8X(switch)(config)# interface front-port 7 LTP-8X(switch)(config-if)# service-acl mac eltexsrc LTP-8X(switch)(config-if)# exit LTP-8X(switch)(config)# commit

  
  

• Step 3. Check the access list configuration.

  Блок кода
  language xml
  LTP-8X(switch)# show access-list Extended MAC access list "eltexsrc"(#0), filters count: 3 Rule 1 (deny): MAC SA A8:F9:4B:00:AA:00 [FF:FF:FF:FF:FF:00] Rule 2 (deny): COS 7 [7] Rule 3 (permit): MAC SA A8:F9:4B:00:00:00 [FF:FF:FF:00:00:00] Vlan 2 COS 4 [4]

  
  

• Step 4. Check the list assignment to the port.

  Блок кода
  language xml
  LTP-8X(switch)# show interfaces acl front-port 7 Interface MAC access-list IP access-list front-port 0 eltexsrc -

  Scroll Pagebreak

Configuring IP access-list

The rules of an IP access list support criteria that are available in a MAC access-list

Table 17 — The list of the IP access list-criteria

• Step 1. Create an ip access-list.

  Блок кода
  language xml
  LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# ip access-list extended filter5

  
  

• Step 2. Configure rules and assign the list to a port.

  Блок кода
  language xml
  LTP-8X(switch)(config-ip-al)# deny tcp 10.10.5.0 255.255.255.0 any any any LTP-8X(switch)(config-ip-al)# permit tcp 10.10.0.0 255.255.0.0 any any any LTP-8X(switch)(config-ip-al)# exit LTP-8X(switch)(config)# interface front-port 7 LTP-8X(switch)(config-if)# service-acl ip filter5 LTP-8X(switch)(config-if)# exit LTP-8X(switch)(config)# commit

  
  

• Step 3. Check the access-list configuration.

  Блок кода
  language xml
  LTP-8X(switch)# show access-list Extended IP access list "filter5"(#10), filters count: 2 Rule 1 (deny): IPv4 protocol 6 (TCP) IP SA 10.10.5.0 [255.255.255.0] Sport 8080 Rule 2 (permit): IPv4 protocol 6 (TCP) IP SA 10.10.0.0 [255.255.0.0]

  
  

• Step 4. Check the access-list assignment to the port.

  Блок кода
  language xml
  LTP-8X(switch)# show interfaces acl front-port 7 Interface MAC access-list IP access-list front-port 0 eltexsrc filter5

  Scroll Pagebreak

Configuring ACL based on a bit mask

The filtering based on a bit mask is available in MAC and IP access-lists. The configuration is implemented with the help of offset-list.

Command format:

offset-list list1 <offset-type> <offset> <byte-mask> <byte-value> ...

You can configure up to 5 unique offset-lists on the OLT.

Table 18 — The list of the available offset-lists

permit any any vlan any cos any ethertype any offset-list eltex1p

• Step 1. Create an access-list.

  Блок кода
  language xml
  LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# mac access-list extended EltexOUI

  Scroll Pagebreak

• Step 2. Configure rules and assign the access-list to a port.

  Блок кода
  language xml
  LTP-8X(switch)(config-mac-al)# offset-list e1 l2 0 FF A8 l2 1 FF F9 l2 2 FF 4B LTP-8X(switch)(config-mac-al)# offset-list e2 l2 0 FF E0 l2 1 FF D9 l2 2 FF E3 LTP-8X(switch)(config-mac-al)# permit any any vlan any cos any ethertype any offset-list e1 LTP-8X(switch)(config-mac-al)# permit any any vlan any cos any ethertype any offset-list e2 LTP-8X(switch)(config-mac-al)# exit LTP-8X(switch)(config)# interface pon-port 0 LTP-8X(switch)(config-if)# service-acl mac OUIfilter LTP-8X(switch)(config-if)# exit LTP-8X(switch)(config)# commit

  
  

• Step 3. Check the access-list configuration.

  Блок кода
  language xml
  LTP-8X(switch)# show access-list Extended MAC access list "EltexOUI"(#2), filters count: 2 Offset lists: e1 l2:0:FF:A8 l2:1:FF:F9 l2:2:FF:4B e2 l2:0:FF:E0 l2:1:FF:D9 l2:2:FF:E3 Rule 1 (permit): Offset-list e1 Rule 2 (permit): Offset-list e2

  
  

Configuring policies

Configuring policies allows you to perform various manipulations on classified traffic, such as cos, dscp, queue setting.

• Step 1. Create an access-list according to which the traffic will be classified.

  Блок кода
  language xml
  LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# ip access-list extended sip-dhcp-acl LTP-8X(switch)(config-ip-al)# permit udp any 68 any 67 LTP-8X(switch)(config-ip-al)# permit udp any any any 5060 LTP-8X(switch)(config-ip-al)# exit

  
  

• Step 2. Create a traffic class.

  Блок кода
  language xml
  LTP-8X(switch)(config)# class-map sip-dhcp-class LTP-8X(switch)(config-class 'sip-dhcp-class')# match access-group sip-dhcp-acl LTP-8X(switch)(config-class 'sip-dhcp-class')# exit

  Scroll Pagebreak

• Step 3. Set policy.

  Блок кода
  language xml
  LTP-8X(switch)(config)# policy-map cos7 LTP-8X(switch)(policy-class 'cos7')# class sip-dhcp-class LTP-8X(switch)(traffic-class 'sip-dhcp-class')# cos 7 LTP-8X(switch)(traffic-class 'sip-dhcp-class')# exit LTP-8X(switch)(policy-class 'cos7')# exit LTP-8X(switch)(config)# interface pon-port 0 LTP-8X(switch)(config-if)# service-policy cos7 LTP-8X(switch)(config-if)# exit LTP-8X(switch)(config)# commit

  
  

• Step 4. Check the configuration of the policy and classes.

  Блок кода
  language xml
  LTP-8X(switch)# show access-list Extended IP access list "sip-dhcp-acl"(#8), filters count: 2 Rule 1 (permit): IPv4 protocol 17 (UDP) Sport 68 Dport 67 Rule 2 (permit): IPv4 protocol 17 (UDP) Dport 5060 LTP-8X(switch)# show interfaces acl pon-port 0 Interface MAC access-list IP access-list Policy-map pon-port 0 - - cos7

  
  

While the configuration, you should remember that deny in an ACL rule exclude the traffic from processing according to policy.

IGMP and MLD configuration in terminal switch

This chapter describes IGMP and MLD configuration in the terminal switch.

Enabling snooping

• Step 1. Snooping is configured globally in the terminal switch. Execute the switch and configure commands consecutively to switch to the config view.

  Блок кода
  language xml
  LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)#

  
  

• Step 2. Enable IGMP snooping by using the ip igmp snooping command.

  Блок кода
  language xml
  LTP-8X(switch)(config)# ip igmp snooping

  Scroll Pagebreak

• Step 3. Enable MLD snooping by using the ipv6 mld snooping command.

  Блок кода
  language xml
  TP-8X(switch)(config)# ipv6 mld snooping

  
  

Enabling report proxy

• Step 1. Enable IGMP report proxy between VLANs by using the ip igmp proxy report enable command.

  Блок кода
  language xml
  LTP-8X(switch)(config)# ip igmp proxy report enable

  
  

• Step 2. Set IGMP report proxy rules by using the ip igmp proxy report range command. As parameters, pass a range of acceptable groups and the proxy direction as a VID pair.

  Блок кода
  language xml
  LTP-8X(switch)(config)# ip igmp proxy report range 224.0.0.0 239.255.255.255 from 200 to 98

  
  

• Step 3. Enable MLD report proxy between VLANs by using the ipv6 mld proxy report enable command.

  Блок кода
  language xml
  LTP-8X(switch)(config)# ipv6 mld proxy report enable

  
  

• Step 4. Set MLD report proxy rules by using the ipv6 mld proxy report range command. As parameters, pass a range of acceptable groups and the proxy direction as a VID pair. 
  

  Блок кода
  language xml
  LTP-8X(switch)(config)# ipv6 mld proxy report range ff15:0::1 ff15:0::ffff from 300 to 98

  
  

Scroll Pagebreak

Interface сonfiguration

Якорь
Настройка интерфейсов Настройка интерфейсов

This chapter describes configuration of terminal interfaces.

Terminal interfaces can be divided into two groups: Ethernet interfaces and GPON interfaces. Ethernet interfaces are used for terminal connection to operator's network core. GPON interfaces are used for ONT connections.

Figure 24 — Set of terminal interfaces

Table 19 shows types of terminal switch interfaces.

Scroll Pagebreak

Ethernet interface configuration

• Step 1. Switch to the view of the interface (of interface group), which settings should be changed.

  Блок кода
  language xml
  LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# interface front-port 0 LTP-8X(switch)(config-if)#

  
  

• Step 2. Enable the interface by using the no shutdown command. On the contrary, the shutdown command disables the interface.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# no shutdown

  
  

• Step 3. Enable or disable flow control (IEEE 802.3x PAUSE) by using the flow-control command.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# flow-control on

  
  

• Step 4. Enable or disable incoming packets filtering by using the ingress-filtering command. Only the packets of the VLANs, which have this interface, will pass the enabled filter. Other packets will be filtered out. If the filter is disabled, a packet will be processed regardless of its VID field.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# ingress-filtering

  
  

• Step 5. Specify a rule for VLAN tags processing for incoming packets by using the frame-types command. As a parameter, specify the packets to be allowed: either tagged (tagged only) or all (both tagged and untagged).

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# frame-types tagged

  
  

• Step 6. Specify the port pvid, i. e. the VLAN, which will accommodate untagged packets. Specify the pup value, which is the priority of untagged packets.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# pvid 100 LTP-8X(switch)(config-if)# pup 0

  
  

• Step 7. If necessary, enable or disable packets transfer from this interface to another one (or a range of interfaces) by using the bridging to command. Pass interface type and number (or a range) as parameters. The interface types and numbers are given in Table 19.

  All front-port interfaces are isolated by default, however data can be sent to any pon-port interface. The same is applicable to pon-port interfaces, which are isolated from each other, but can send data to any front-port interfaces.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# bridging to front-port 1

  Scroll Pagebreak

• Step 8. If needed, use the spanning-tree command group to adjust the STP protocol.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# spanning-tree enable LTP-8X(switch)(config-if)# spanning-tree priority 32 LTP-8X(switch)(config-if)# spanning-tree pathcost 0 LTP-8X(switch)(config-if)# spanning-tree admin-p2p auto LTP-8X(switch)(config-if)# spanning-tree admin-edge

  
  

• Step 9. If needed, set band limits for Broadcast, Multicast, Unknown Unicast and the whole traffic by using the rate-limit bc/mc/uu, and shaper commands correspondingly. As parameters, pass the maximum band width in kbps and the maximum length of uninterrupted transmission of packet batches in bytes.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# rate-limit bc 1000 2048 LTP-8X(switch)(config-if)# rate-limit mc 1000 2048 LTP-8X(switch)(config-if)# shaper 100000 4000

  
  

• Step 10. Set automatic determination of speed and duplex of the interface either by using the speed auto command or manually.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# speed auto

  
  

• Step 11. Set the interface description by the description command.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# description org-uplink

  
  

• Step 12. Enable mac notification trap if necessary. The device will send snmp-trap when learning new MAC or when deleting the old one.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# snmp trap mac-notification added LTP-8X(switch)(config-if)# snmp trap mac-notification removed

  
  

• Step 13. Apply the configuration by using the commit command. 
  

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# exit LTP-8X(switch)(config)# commit

  
  

Scroll Pagebreak

Configuring Storm Control

A storm appears due to excessive number of broadcast or/and multicast messages transmitted on the network via a single port simultaneously. It leads to an overload of the network resources and appearing of delays. A storm also can be caused by loopback segments of an Ethernet network. The switch evaluates the rate of incoming broadcast, multicast and unknown unicast traffic for port with enabled Storm Control and drops packets if the rate exceeds the set maximum value.

There is an opportunity to record a storm event to the log and disable the port for a specified time (in seconds).

LTP-8X(switch)(config-if)# rate-limit uu 1000 2048 
LTP-8X(switch)(config-if)# rate-limit mc 1000 2048 logging 
LTP-8X(switch)(config-if)# rate-limit bc 1000 2048 logging shutdown 30

For manual enabling of the port after blocking by Storm Control, use the clear storm command.

LTP-8X(switch)# clear storm front-port 0

GPON interface configuration

• Step 1. Switch to the configure view.

  Блок кода
  language xml
  LTP-8X# configure terminal

  
  

• Step 2. Activate traffic encryption with the gpon olt encryption command if necessary. Specify the encryption key renewal period with the gpon olt encryption key-update command. Pass time period in seconds as a parameter.

  Блок кода
  language xml
  LTP-8X(config)# gpon olt encryption LTP-8X(config)# gpon olt encryption key-update 60

  
  

• Step 3. Specify ONT authentication method with the gpon olt authentication command. ONTs can be authenticated by password, serial number, or both.

  Блок кода
  language xml
  LTP-8X(config)# gpon olt authentication both

  
  

• Step 4. Specify time of ONT blocking (in minutes) in case of MAC duplication or storm appearing. For details see the Configuring Storm Control section.
  

  Блок кода
  language xml
  LTP-8X(config)# gpon olt ont-block-time 1

  Scroll Pagebreak

  It is possible to receive a PON password of non-configured ONTs in an ALARM trap.

  Блок кода
  language xml
  LTP-8X(config)# gpon olt password-in-trap

  
  

• Step 5. Switch to GPON interface configuration. 
  

  Блок кода
  language xml
  LTP-8X(config)# interface gpon-port 0-7

  
  

• Step 6. Enable or disable interfaces with the no shutdown or shutdown command respectively if necessary.

  Блок кода
  language xml
  LTP-8X(config)(if-gpon-0-7)# no shutdown

  
  

• Step 7. Activate FEC for interfaces with the fec command if necessary. 
  

  Блок кода
  language xml
  LTP-8X(config)(if-gpon-0-7)# fec

  
  

  Примечание
  In case of using FEC, the real bandwidth decreases by ~10 %

  
  

• Step 8. If necessary, enable the ability to migrate MAC addresses for selected interfaces. 
  

  Блок кода
  language xml
  LTP-8X(config)(if-gpon-0-7)# mac-migration

  
  

• Step 9. Adjust time settings of optical transceivers if needed.
  

  Блок кода
  language xml
  LTP-8X(config)(if-gpon-0-7)# optics use-custom LTP-8X(config)(if-gpon-0-7)# optics ...

  
  

  Примечание
  Optical transceivers should be adjusted only by agreement with Eltex Service Center.

  
  

• Step 10. If necessary, enable unknown multicast with the following command.

  Блок кода
  language xml
  LTP-8x(config)(if-gpon-7)# unknown-multicast-forward enable

  
  

• Step 11. Apply the configuration by using the commit command.

  Блок кода
  language xml
  LTP-8X(config)(if-gpon-0-7)# exit LTP-8X(config)# do commit

  Scroll Pagebreak

GPON port force enable

LTP-X devices have the ability to forcibly enable GPON ports that are disabled in the configuration

LTP-8X# show interface gpon-port 7 state 
    Reading:  .
    Gpon-port status information:
        Gpon-port:                             7
        State:                          DISABLED
        ONT count:                             0
        Force-mode:                     disabled
        ONT autofind:                    enabled
        SFP vendor:                       Ligent
        SFP product number:          LTE3680M-BC
        SFP vendor revision:                 1.0
        SFP temperature [C]:                  67
        SFP voltage [V]:                    3.28
        SFP tx bias current [mA]:            n/a
        SFP tx power [dBm]:                  n/a

To forcibly enable the port, put it into the force mode. The command is applied without entering the commit command.

LTP-8X# force-mode interface gpon-port 7

As a result, the port will be enabled until the next reconfiguration or reboot.

LTP-8X# show interface gpon-port 7 state 
    Reading:  .
    Gpon-port status information:
        Gpon-port:                             7
        State:                                OK
        ONT count:                             0
        Force-mode:                      enabled
        ONT autofind:                    enabled
        SFP vendor:                       Ligent
        SFP product number:          LTE3680M-BC
        SFP vendor revision:                 1.0
        SFP temperature [C]:                  65
        SFP voltage [V]:                    3.25
        SFP tx bias current [mA]:          16.81
        SFP tx power [dBm]:                 3.34

Scroll Pagebreak

Unknown-multicast traffic forwarding

LTP-X devices have the ability to forward unknown-multicast to broadcast-gem-port. Configuration is performed for each GPON port separately.

LTP-8X# configure terminal
LTP-8X(config)# interface gpon-port 0
LTP-8X(config)(if-gpon-0)# unknown-multicast-forward enable
LTP-8X(config)(if-gpon-0)# unknown-multicast-forward to broadcast-gem

GPON ports redundancy configuration

GPON port redundancy is designed to increase the reliability of the PON network. There are several types of redundancy: Type-A, Type-B, Type-C and Type-D. LTP-X supports Type-B redundancy. Type-B redundancy provides the ability to automatically switch between channels by using an additional GPON port. There are several ONT connection schemes (Figure 25 and Figure 26).

Figure 25 — Type-B redundancy. Connection scheme 1

Figure 26 — Type-B redundancy. Connection scheme 2

• LTP-4X/8X-rev.C with PLD version 14 and higher;
• LTP-4X/8X rev.D.

The necessary information can be obtained by using the show system environment command.

LTP-8X# show system environment 
    System information:
        CPU load average (1m, 5m, 15m):   0.60  0.44  0.31
        Free RAM/Total RAM (Mbytes):      175/495
        Temperature (sensor1/sensor2):    40C/50C
        Reset button:                     enabled

        Fan configured speed, %:          auto
        Fan minimum speed, %:             15
        Fan speed levels, %:              16 27 39 51 64 76 88 100 

        Fan state (fan0/fan1):            8640rpm  8760rpm

        PLD FW version:                   14 

        TYPE:                             LTP-8X-rev.C 
        HW_revision:                      1v4 
        SN:                               GP2B000860 
        MAC:                              E0:D9:E3:DF:E4:D0 

        Power supply information:
                Module 1: PM160 220/12 1vX
                        Type: Alternate current(AC)
                        Intact: 1
                Module 2: PM150(75) 48/12 1vX
                        Type: Direct current(DC)
                        Intact: 0

Before connecting an ONT, check the list of supported ONTs (Table 20). For the proper redundancy operation, it is necessary to connect ONT to OLT according to one of the schemes (Figure 25 and Figure 26).

• Step 1. The redundancy configuration is performed with the gpon olt redundacy gpon-port command.

  Предупреждение
  Redundancy can only be configured on 4 pairs of ports — 0-1, 2-3, 4-5 and 6-7, other combinations are not supported.

  The gpon olt redundancy gpon-port command allows you to configure redundancy on one or more pairs at once.

  Блок кода
  language xml
  LTP-8X# configure terminal LTP-8X(config)# gpon olt redundancy gpon-port 0-1,2-3,4-5,6-7 LTP-8X(config)# do commit

  Once configured, the even-numbered port defaults to the primary channel and the odd-numbered port to the redundant channel.

  Блок кода
  language xml
  LTP-8X# show interface gpon-port 0-1 state Reading: .. Gpon-ports status information: Gpon-port: 0 1 State: OK REDUNDANT ONT count: 0 0 Force-mode: disabled disabled ONT autofind: enabled enabled SFP vendor: Ligent Ligent SFP product number: LTE3680M-BC LTE3680M-BC SFP vendor revision: 1.0 1.0 SFP temperature [C]: 70 39 SFP voltage [V]: 3.19 3.24 SFP tx bias current [mA]: 17.29 n/a SFP tx power [dBm]: 3.54 n/a

  
  

• Step 2. Configure the ONT on an even-numbered port.

  Предупреждение
  ONT configuration is performed only on even-numbered ports (0, 2, 4 and 6), odd-numbered ports use the configuration from even-numbered ports.

  
  

  Блок кода
  language xml
  LTP-8X# configure terminal LTP-8X(config)# interface ont 0/2 LTP-8X(config)(if-ont-0/2)# serial ELTX62108400 LTP-8X(config)(if-ont-0/2)# do commit

  Once configured, the ONT will appear in the OK state on the main channel and in the REDUNDANT state on the redundant channel.

• Step 3. To display ONT information on a pair of channels, use the show interface ont x-x redundant command.

  Блок кода
  language xml
  LTP-8X# show interface gpon-port 0-1 state Reading: .. Gpon-ports status information: Gpon-port: 0 1 State: OK REDUNDANT ONT count: 1 1 Force-mode: disabled disabled ONT autofind: enabled enabled SFP vendor: Ligent Ligent SFP product number: LTE3680M-BC LTE3680M-BC SFP vendor revision: 1.0 1.0 SFP temperature [C]: 78 67

  
  

  Блок кода
  language xml
  SFP voltage [V]: 3.18 3.23 SFP tx bias current [mA]: 18.94 n/a SFP tx power [dBm]: 3.54 n/a LTP-8X# show interface ont 0-1 redundant ----------------------------------- GPON-port 0 ONT redundant list ----------------------------------- ## Serial ONT ID GPON-port Status RSSI[dBm] Version EquipmentID 1 ELTX62108400 2 0 OK -10.71 3.28.1.69 NTU-1 ----------------------------------- GPON-port 1 ONT redundant list ----------------------------------- ## Serial ONT ID GPON-port Status RSSI[dBm] Version EquipmentID 1 ELTX62108400 2 1 REDUNDANT n/a 3.28.1.69 NTU-1 Total ONT count: 2

  
  

In case of malfunction on the main channel, such as line breakage, there will be a seamless channel change — the redundant channel will become the main channel, the main channel in this case will go to redundant state. Seamless channel change is the transition of all ONTs from the main channel to the redundant channel without interrupting client sessions.

LTP-8X# show interface ont 0-1 redundant

-----------------------------------
GPON-port 0 ONT redundant list
-----------------------------------

        ##         Serial   ONT ID   GPON-port      Status   RSSI[dBm]     Version   EquipmentID
         1   ELTX62108400        2           0   REDUNDANT         n/a   3.28.1.69         NTU-1

-----------------------------------
GPON-port 1 ONT redundant list
-----------------------------------

        ##         Serial   ONT ID   GPON-port   Status   RSSI[dBm]     Version   EquipmentID
         1   ELTX62108400        2           1       OK      -14.85   3.28.1.69         NTU-1

Total ONT count: 2

Port Mirroring configuration

Port mirroring is used to duplicate the traffic on monitored ports by sending ingress or and/or egress packets to the controlling port. Users can define a controlled port and controlling ports and select the type of the traffic (ingress or egress), which will be sent to the controlling port.

Configuration of the controlled port

• Step 1. Mirroring is configured in the terminal switch. Execute the switch and configure commands consecutively to switch to the config view.

  Блок кода
  language xml
  LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)#

  
  

• Step 2. Configure the pon-port mirroring for ingress and egress traffic.

  Блок кода
  language xml
  LTP-8X(switch)(config)# mirror rx interface pon-port 0 LTP-8X(switch)(config)# mirror tx interface pon-port 0

  
  

• Step 3. Apply the configuration by using the commit command.

  Блок кода
  language xml
  LTP-8X(switch)(config)# commit

  
  

Scroll Pagebreak

Configuration of the controlling port

• Step 1. Switch to the switch config view by using the switch and configure commands.

  Блок кода
  language xml
  LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)#

  
  

• Step 2. Configure mirroring and traffic analysis for any front-port.

  Блок кода
  language xml
  LTP-8X(switch)(config)# mirror rx analyzer front-port 7 LTP-8X(switch)(config)# mirror tx analyzer front-port 7

  
  

• Step 3. If necessary, add a VLAN tag to be used for all mirrored traffic and packet priority.

  Блок кода
  language xml
  LTP-8X(switch)(config)# mirror add-tag LTP-8X(switch)(config)# mirror rx added-tag-config vlan 1555 user-prio 0 LTP-8X(switch)(config)# mirror tx added-tag-config vlan 1555 user-prio 0

  
  

• Step 4. Apply the configuration by using the commit command.

  Блок кода
  language xml
  LTP-8X(switch)(config)# commit

  
  

LLDP configuration

Link Layer Discovery Protocol (LLDP) is a Data link layer protocol that allows network devices to announce information about themselves and their capabilities to the network, as well as to collect this information about neighboring devices. The standard RFC mib 1.0.8802 are supported by the SNMP agent.

LLDP configuration

• Step 1. Activate the LLDP.

  Блок кода
  language xml
  LTP-8X(switch)(config)# lldp enable

  
  

• Step 2. If necessary, configure LLDPDU transfer mode.

  Блок кода
  language xml
  LTP-8X(switch)(config)# interface front-port 0 LTP-8X(switch)(config-if)# lldp mode transmit-receive

  
  

• Step 3. Configure optional LLDP-TLVs for ports.

  Блок кода
  language xml
  LTP-8X(switch)(config-if)# lldp optional-tlv sys-desc LTP-8X(switch)(config-if)# lldp optional-tlv port-desc

  
  

• Step 4. Specify the amount of time for the receiver to keep LLDP packets before dropping them.
  

  Блок кода
  language xml
  LTP-8X(switch)(config)# lldp hold-multiplier 5

  This value will be transmitted to the receiving side in the LLDP update packets; and should be an increment for the LLDP timer. Thus, the lifetime of LLDP packets is calculated by the formula.

  Блок кода
  language xml
  TTL = min(65535,LLDP-Timer * LLDP-HoldMultiplier)

  
  

• Step 5. Set the reinitialization time of LLDP.

  Блок кода
  language xml
  LTP-8X(switch)(config)# lldp reinit 3

  
  

• Step 6. Specify how often the device will send LLDP information updates.

  Блок кода
  language xml
  LTP-8X(switch)(config)# lldp timer 60

  
  

• Step 7. Specify the delay between the subsequent LLDP packet transmissions caused by the changes of values or status in the local LLDP MIB database.

  Блок кода
  language xml
  LTP-8X(switch)(config)# lldp tx-delay 3

  It is recommended that this delay be less than 0.25* LLDP-Timer.

• Step 8. Specify the processing mode of LLDP packets.
  LLDP packet processing mode:

  • filtering — LLDP packets are filtered if LLDP is disabled on the switch;
  • flooding — LLDP packets are transmitted if LLDP is disabled on the switch.

LTP-8X(switch)(config)# lldp lldpdu flooding

• Step 9. Apply the configuration by using the commit command.

LTP-8X(switch)(config)# commit

ERPS configuration

ERPS (Ethernet Ring Protection Switсhing) — link layer protocol designed to increase the stability and reliability of a data network by creating a ring topology with logical blocking of interfaces. It is realized by reducing recovery network time in case of breakdown. Recovery time does not exceed 1 second. It is much less than network change over time in case of spanning tree protocols usage.

Scroll Pagebreak

ERPS configuration

• Step 1. Enable ERPS.

  Блок кода
  language xml
  LTP-8X(switch)(config)# erps enable

  
  

• Step 2. Create an ERPS ring with the R-APS VLAN identifier through which service traffic will be transmitted.

  Блок кода
  language xml
  LTP-8X(switch)(config)# erps vlan 700

  
  

• Step 3. Specify east/west port.

  Блок кода
  language xml
  LTP-8X(switch)(config-erps)# port east front-port 3 LTP-8X(switch)(config-erps)# port west port-channel 1

  
  

• Step 4. Set the range of secure VLANs.
  

  Блок кода
  language xml
  LTP-8X(switch)(config-erps)# protected vlan add 100-103

  
  

• Step 5. If necessary, assign the RPL port with the owner/neighbor command.

  Блок кода
  language xml
  LTP-8X(switch)(config-erps)# rpl east owner

  
  

• Step 6. Change the timers if necessary.
  

  Блок кода
  language xml
  LTP-8X(switch)(config-erps)# timer guard 10 LTP-8X(switch)(config-erps)# timer holdoff 100 LTP-8X(switch)(config-erps)# timer wtr 1

  
  

• Step 7. Specify a subring if necessary. 
  

  Блок кода
  language xml
  LTP-8X(switch)(config-erps)# sub-ring vlan 750

  
  

• Step 8. Enable the ring by the enable command. 
  

  Блок кода
  language xml
  LTP-8X(switch)(config-erps)# ring enable

  Scroll Pagebreak

• Step 9. View the status of the generated ERPS ring.

  Блок кода
  language xml
  LTP-8X(switch)# show erps vlan 700 R-APS VLAN : 700 Admin Status : Enabled West Port : port-channel 1 (Signal Fail) East Port : front-port 1 (Forwarding) RPL Port : East RPL Owner : Enabled (Active) Protected VLANs : 100-103 Ring MEL : 1 Holdoff Time : 100 msec Guard Time : 10 msec WTR Time : 1 min Current Ring State : Protection Revertive : Yes Compatibility with version : 2 Sub-Ring R-APS VLAN TC Propagation State ------------------- -------------------- 750 Disable