...
Scroll pdf ignore |
---|
LTP-8X, LTP-4X optical line terminals User manual |
A Shared Block | |||||
---|---|---|---|---|---|
| |||||
|
Scroll pdf ignore | ||||||
---|---|---|---|---|---|---|
|
Terms and definitions
CBR — Constant bitrate
DBA — Dynamic bandwidth allocation
...
Информация |
---|
Additional information, clarifications. |
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.
...
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).
...
- 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 |
---|
The standard delivery package includes:
- LTP-4X/8X optical line terminal;
- Mounting set for 19'' rack;
- RS-232 DB9(F) — DB9(F) console cable for LTP rev.B; RJ-45 — DB9(F) console cable for LTP rev.С and rev.D;
- CD with User Manual and Quick Configuration Manual (optionally);
- Power cable (if equipped with 220 V power module);
- Passport.
Technical specifications
Table 1 — Main specifications of the line terminal
Interfaces | ||
Number of Ethernet interfaces | LTP-8X | 10 |
LTP-4X | 6 | |
Connector | RJ-45 | SFP |
Data rate | 10/100/1000 Mbps duplex/half-duplex | 1000/10000 Mbps duplex |
Standards | 10/100BASE-TХ, 1000BASE-T | 1000BASE-X, 10GBASE-X |
Standards | IEEE 802.1D, IEEE 802.1p, IEEE 802.1Q | |
Number of PON interfaces | LTP-8X | 8 |
LTP-4X | 4 | |
Connector type | SC/UPC (socket) in accordance with ITU-T G.984.2, FSAN Class B+, FSAN Class С++, SFF-8472 | |
Transmission medium | Fibre optical cable SMF — 9/125, G.652 | |
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 linewidth 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 overload | -8 dBm | -12 dBm |
Processor | ||
Clock frequency | 800 MHz | |
Core quantity | 1 | |
RAM | LTP-4X/8Х rev.B | 512 MB |
LTP-4X/8Х rev.С | 512 MB | |
LTP-4X/8Х rev.D | 512 MB | |
Non-volatile memory | LTP-4X/8Х rev.B | 512 MB |
LTP-4X/8Х rev.С | 512 MB | |
LTP–4X/8Х rev.D | 512 MB | |
Switch | ||
Bandwidth | 128 Gbps | |
MAC table | 16К entries | |
VLAN support | up to 4K in accordance with 802.1Q | |
Quality of Service (QoS) | 8 prioritized egress queues per port | |
Control | ||
Local control | CLI — Command Line Interface | |
Remote control | CLI (SSH2, Telnet), SNMP | |
Monitoring | СLI, SNMP | |
Access restriction | by password, IP address, MAC address, privilege level | |
General parameters | ||
---|---|---|
Power supply | AC: 150–250 V, 50 Hz
| |
Maximum power consumption | LTP-8X rev.B | no more than 50 W |
LTP-8X rev.C/rev.D | no more than 55 W | |
LTP-4X rev.B | no more than 40 W | |
LTP-4X rev.C/rev.D | no more than 50 W | |
Operating temperature range | from -5 to +40 °C | |
Relative humidity | up to 80 % | |
Dimensions (W ×H × D) | 19", 1U | |
Dimensions with installed power module: | ||
LTP-4X/8Х rev.B | 430 × 44 × 259 mm | |
LTP-4X/8Х rev.С | 430 × 44 × 317 mm | |
LTP-4X/8Х rev.D | 430 × 44 × 317 mm | |
Weight | Complete set | |
LTP-4X/8Х rev.B | no more than 3.5 kg | |
LTP-4X/8Х rev.С | no more than 5 kg | |
LTP-4X/8Х rev.D | no more than 5 kg | |
Modules | ||
Power module | 0.5 kg |
Scroll Pagebreak |
---|
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.
...
Vendor | SFP transceiver model | Class | DDMI |
---|---|---|---|
NEOPHOTONICS | PTB38J0-6538E-SC | B+ | + |
NEOPHOTONICS | 38J0-6537E-STH1+ | C++ | + |
NEOPHOTONICS | 38J0-6537E-STH2+ | C++ | + |
NEOPHOTONICS | 38J0-6537E-STH3+ | C++ | + |
Ligent Photonics | LTE3680M-BC | B+ | + |
Ligent Photonics | LTE3680M-BH | B+ | + |
Ligent Photonics | LTE3680P-BC | C+ | + |
Ligent Photonics | LTE3680P-BC+1 | C+ | + |
Ligent Photonics | LTE3680P-BH | C+ | + |
Ligent Photonics | LTE3680P-BC2 | C++ | + |
Fanghang | DLOLT43BCDS20 | B+ | + |
Fanghang | DLOLT43CCDS20 | C+ | + |
Fanghang | FH-DLT43CCDS20 | C+ | + |
Hisense | LTE3680M-BC+ | B+ | + |
Hisense | LTE3680P-BC+1 | C+ | + |
Hisense | LTE3680P-BC+2 | C++ | + |
Scroll Pagebreak |
---|
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.
...
# | Front panel element | Description | |
---|---|---|---|
1 | Console | RS-232 console port for local control of the device | |
2 | GE Port 0..3 | 4 RJ-45 connectors of 10/100/1000BASE-T Gigabit uplink interfaces for connection to IP networks (for LTP-8X) | |
3 | Combo GE | 0..3 | 4 chassis for SFP modules of 1000BASE-X uplink interface for connection to IP networks (for LTP-4X) |
4 RJ-45 connectors of 10/100/1000BASE-T Gigabit uplink interfaces for connection to IP networks (for LTP-4X) | |||
4..7 | 4 chassis for SFP modules of 1000BASE-X uplink interface for connection to IP networks (for LTP-8X) | ||
4 RJ-45 connectors of 10/100/1000BASE-T Gigabit uplink interfaces for connection to IP networks (for LTP-8X) | |||
4 | 10G/1G 0..1 | 2 chassis for SFP modules of 10GBase/1000BASE-X uplink interface for connection to IP networks | |
5 | PON | 4 chassis for SFP modules of xPON 2.5 G (for LTP-4X) | |
8 chassis for SFP modules of xPON 2.5 G (for LTP-8X) | |||
6 | Power | Device power indicator | |
7 | Status | Device operation indicator | |
8 | F | Functional key that reboots the device and resets it to factory default configuration:
Configuring the response to a button click performs in the terminal CLI, for detailed description see Section System environment configuration. |
Scroll Pagebreak |
---|
# | Front panel element | Description | |
---|---|---|---|
1 | Power | Device power indicator | |
2 | Status | Device operation indicator | |
3 | Fan | Fan operation LED | |
4 | RPS | Redundant power supply LED | |
5 | Console | Console port for local management of the device Console cable pin assignment is shown in APPENDIX A. RS-232 NULL-MODEM CABLE PIN DESIGNATION | |
6 | F | Functional key that reboots the device and resets it to factory default configuration:
| |
7 | GE Port 0..3 | 4 RJ-45 connectors of 10/100/1000BASE-T Gigabit uplink interfaces for connection to IP networks (for LTP-8X) | |
8 | Combo GE | 0..3 | 4 chassis for SFP modules of 1000BASE-X uplink interface for connection to IP networks (for LTP-4X) |
4 RJ-45 connectors of 10/100/1000BASE-T Gigabit uplink interfaces for connection to IP networks (for LTP-4X) | |||
4..7 | 4 chassis for SFP modules of 1000BASE-X uplink interface for connection to IP networks (for LTP-8X) | ||
4 RJ-45 connectors of 10/100/1000BASE-T Gigabit uplink interfaces for connection to IP networks (for LTP-8X) | |||
9 | 10G/1G 0..1 | 2 chassis for SFP modules of 10GBase/1000BASE-X uplink interface for connection to IP networks | |
10 | PON | 4 chassis for SFP modules of xPON 2.5 G (for LTP-4X) | |
8 chassis for SFP modules of xPON 2.5 G (for LTP-8X) |
...
Примечание |
---|
4 electrical Ethernet and 4 optical interfaces are combined (Combo GE 4..7). The combo ports may have only one active interface at the same time. |
Scroll Pagebreak |
---|
The rear panel layout of the device is depicted in Fig. 5, 6, 7.
...
Rear panel element | Description |
---|---|
36 .. 72 VDC, max 5A | Connector for DC power supply |
160–250 VAC, 50 Hz, max 1A | Connector for AC power supply |
Fan0, Fan1 | Ventilation units |
Earth bonding point | Earth bonding point |
Scroll Pagebreak |
---|
The indicators located on the front panel show the status of the terminal. Indicator states are listed in Tables 6 and 7.
...
LED name | Indicator state | Device state |
---|---|---|
Power | Solid green | Power is on, normal device operation |
Off | Power is off | |
Red | The primary source of the main power supply is unavailable (in case the device is connected to a redundant power supply) or the main power supply failed | |
Status | Flashes green | Normal operation |
Flashes red | Critical failure | |
Fan | Solid green | All fans are operational |
Solid red | One or more fans are failed | |
RPS | 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 |
Scroll Pagebreak |
---|
Temperature sensors
2 temperature sensors are used to measure temperature inside the terminal case.
...
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.
Scroll Pagebreak |
---|
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".
...
- 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.
- Prior to turning the device on, ensure that all cables are undamaged and securely connected.
- Make sure the device is off, when installing or removing the case.
- 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.
- 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.
Scroll Pagebreak |
---|
Якорь | ||||
---|---|---|---|---|
|
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.
...
- 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.
...
Якорь | ||||
---|---|---|---|---|
|
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 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 specificationsParameter 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 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
Scroll Pagebreak |
---|
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>.
...
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.
...
- 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:
Hotkey | Result |
---|---|
Ctrl+C | Termination of the current operation; clear line |
Ctrl+D | Transition up one level |
Ctrl+Z | Transition to root section |
Ctrl+A | Transition to the beginning of line |
Ctrl+E | Transition to the end of line |
Ctrl+U | Removal of characters to the left of a cursor |
Ctrl+К | Removal of characters to the right of a cursor |
Ctrl+W | Remove a word |
Ctrl+B | Transition of a cursor one position backwards |
Ctrl+F | Transition of a cursor one position ahead |
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.
...
Блок кода | ||
---|---|---|
| ||
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.
...
Блок кода | ||
---|---|---|
| ||
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 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.
...
Блок кода | ||
---|---|---|
| ||
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.
...
- 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:
...
Якорь | ||||
---|---|---|---|---|
|
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.
...
Блок кода | ||
---|---|---|
| ||
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.
...
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.
...
Якорь | ||||
---|---|---|---|---|
|
Scroll Pagebreak |
---|
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.
...
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.
Table 9 — Permissions and the required level of privilegesScroll Pagebreak 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.
...
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.
...
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.
...
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.
Scroll Pagebreak |
---|
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 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 |
Scroll Pagebreak
ААА configuration
This chapter describes configuring of services and protocols related to authentication, authorization and accounting.
...
Function and protocol | Tacacs+ | Radius |
---|---|---|
Authentication | + | + |
Authorization | + | - |
Accounting start-stop | + | + |
Accounting commands | + | - |
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.
...
Примечание |
---|
In case server configured for a function unavailable or key is not defined properly, the function will be implemented locally. |
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).
...
Примечание |
---|
The SNMPv3 agent supports authNoPriv and authPriv methods. The encryption of the password performs according to the MD5 algorithm. |
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
ACSD and DHCPD configuration
The terminal has an integrated auto configuration server (ACS). To ensure interaction between ONTs and ACS, ONTs should obtain IP addresses for their management interfaces. The terminal has an integrated DHCP server to solve this task. These two servers are interconnected and cannot work separately.
ACSD configuration
Step 1. Switch to the configure view.
Блок кода | ||
---|---|---|
| ||
LTP-8X# configure terminal |
Step 2. Turn on the ACS server by using the ip acs server enable command.
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# ip acs server enable |
Step 3. If necessary, set the IP address, server mask, and identifier of the management VLAN, which will be used to send packets between ACS and ONTs. By default, mask 21 is set, which enables 2046 hosts per network.
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# ip acs server ip 192.168.200.9
LTP-8X(config)# ip acs server mask 255.255.255.0
LTP-8X(config)# ip acs server vid 200 |
...
Step 4. In addition to HTTP, ACS can also use an extended version of this protocol that supports encryption — HTTPS. This is configured by the ip acs server scheme command.
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# ip acs server scheme http |
Scroll Pagebreak |
---|
Step 5. If necessary, configure the login and password to be used by ONTs to access the ACS server.
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# ip acs server login acs
LTP-8X(config)# ip acs server password acsacs |
DHCPD configuration
Step 1. Start the DHCP server by using the ip dhcp server enable command.
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# ip dhcp server enable |
Step 2. Configure the range of IP addresses to be assigned by the server with the ip dhcp server range command and specify the first and the last addresses of the range.
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# ip dhcp server range 192.168.200.10 192.168.200.150 |
Step 3. Set the maximum lease time in seconds, during which the server allows clients to use the addresses, by using the ip dhcp server lease-time command.
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# ip dhcp server lease-time 600 |
Step 4. Use the ip dhcp server option-43 command to configure output of option 43 in the DHCP offer packet for correct connection of ONTs to the ACS server. View general settings of ACSD and DHCPD to check the format of the option.
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# ip dhcp server option-43 |
...
Step 5. If necessary, configure the delivery of static routes to the network to the ONT TR-interface (option 121).
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# ip dhcp server static-route net 172.20.240.0 mask 255.255.255.0 gateway 172.20.40.1 |
Scroll Pagebreak |
---|
Step 6. Check the changes by using the do show ip acs server command.
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# do show ip acs server
ACS server:
Enabled: true
Ip: 192.168.200.9
Port: 9595
Mask: 255.255.255.0
Vid: 200
Scheme: 'http'
Login: 'acs'
Password: 'acsacs'
External fw ip: 0.0.0.0
External fw port: 9595
Local fw port: 9696
ACS DHCP server:
Enabled: true
Max lease time: 600
Insert option 43: true
First IP: 192.168.200.10
Last IP: 192.168.200.150
DHCP option 43 (will be generated automatically):
URL: 'http://192.168.200.9:9595'
Login: 'acs'
Password: 'acsacs' |
Step 7. Apply the configuration by using the commit command.
Блок кода | ||
---|---|---|
| ||
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.
...
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.
...
Блок кода | ||
---|---|---|
| ||
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.
...
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.
...
Token | Description |
---|---|
severity | Describes event severity. Has four statuses (info, minor, major, critical) |
send-on-in | Specifies whether an SNMP trap should be sent when an event is added to the log. Has two states (true/false) |
send-on-out | Specifies whether an SNMP trap should be sent when an event is deleted from the log. Has two states (true/false) |
ttl | The time an event exists in the active alarms log (from 1 to 2,147,483,647). Specified in seconds. The parameter has several special values. 0 — the event exists in the log until a normalising event is received. –1 — an SNMP trap is sent (if specified), but the event is not recorded in the alarms log |
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
Настройка 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 548930003. 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 |
---|
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:
...
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
...
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.
...
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
...
Якорь | ||||
---|---|---|---|---|
|
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
Примечание |
---|
To enable proxy from all VLANs, use the "from all to <VLAN>" structure. |
Scroll Pagebreak |
---|
Якорь | ||||
---|---|---|---|---|
|
This chapter describes configuration of terminal interfaces.
...
Interface | Note | Quantity | Range |
---|---|---|---|
10G-front-port | 2 | [0..1] | |
front-port | for LTP-4X | 4 | [0..3] |
for LTP-8X | 8 | [0..7] | |
pon-port | for LTP-4X | 4 | [0..3] |
for LTP-8X | 8 | [0..7] |
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.
...
Блок кода | ||
---|---|---|
| ||
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
It is possible to receive a PON password of non-configured ONTs in an ALARM trap.Scroll Pagebreak Блок кода 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
...
Примечание |
---|
The force-mode command stops if the device is reconfigured or rebooted, because it is not saved in the configuration. |
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.
...
Примечание |
---|
This functionality is required for some protocols, such as IS-IS. After applying the settings, the specified GPON port will be reconfigured, which will lead to the reconfiguration of all ONTs on the port. |
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
...
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).
Якорь | ||||
---|---|---|---|---|
|
...
Примечание |
---|
Once the communication line is restored, there will be no switching back. The next switch will only occur if there is a malfunction on the current main channel. |
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 |
---|
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)# 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
ARP-Inspection configuration
The ARP Inspection function is dedicated to defense against attacks which use ARP (for instance, ARP-spoofing — ARP traffic interception). ARP Inspection is implemented on the basis of static correspondence between IP and MAC addresses defined for VLAN.
ARP-Inspection configuration
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. Enable arp inspection, add static entries.
Блок кода language xml LTP-8X(switch)(config)# ip arp inspection LTP-8X(switch)(config)# ip arp inspection static-table 1.1.1.1 A8:F9:4B:11:11:01 LTP-8X(switch)(config)# ip arp inspection static-table 1.1.1.2 A8:F9:4B:11:11:10 vlan 10
Step 3. Configure trusted and untrusted interfaces.
Блок кода language xml LTP-8X(switch)(config)# interface front-port 7 LTP-8X(switch)(config-if)# no ip arp inspection trusted LTP-8X(switch)(config)# interface front-port 0 — 6 LTP-8X(switch)(config-if)# ip arp inspection trusted
Scroll Pagebreak Step 4. Apply the configuration by using the commit command.
Блок кода language xml LTP-8X(switch)(config)# commit
QoS rules configuration
The traffic prioritization and allocation by hardware queues (IEEE 802.1p/DSCP) are implemented on the basis of set rules in the system.
...
Step 1. Set a queue on which packets will be transmitted without preset rules. The 0 queue has the least priority.
Блок кода language xml LTP-8X(switch)(config)# qos default 0
Step 2. Set a traffic prioritization method by using the qos type command. Send a type of prioritization as an argument.
Блок кода language xml LTP-8X(switch)(config)# qos type 1
Scroll Pagebreak Step 3. Using qos map command, set rules for translation of 802.1p and DSCP/TOS to a queue number. Send field type and priorities lists as parameters.
Блок кода language xml LTP-8X(switch)(config)# qos map 1 0-4,15,63 to 6 LTP-8X(switch)(config)# commit LTP-8X(switch)(config)# exit LTP-8X(switch)# show qos Priority assignment by 802.1p packet field Default priority queue is 0 DSCP queues: 7: 63 6: 5: 4: 3: 2: 1: 0: 802.1p queues: 7: 7 6: 6 5: 5 4: 4 3: 3 2: 2 1: 1 0: 0 WRR queues disabled WRR values for queues 7..0: 8 7 6 5 4 3 2 1
Weighted Round Robin (WRR) configuration
Weighted Round Robin (WRR) — an algorithm which distribute throughput by classes, using a scheme of weighted round robin. The OLT has 8 hardware queues.
Step 1. Enable WRR and set 4 queues (0, 1, 2, 3) which will be processed by the algorithm. The other queues will be strict. The WRR queues are enumerated from 0.
Блок кода language xml LTP-8X(switch)(config)# qos wrr enable 4
Step 2. The weight of each queue, starting with the 7th.
Блок кода language xml LTP-8X(switch)(config)# qos wrr queues 1 1 1 1 60 20 15 5
Step 3. Save the configuration.
Блок кода language xml LTP-8X(switch)(config)# commit LTP-8X(switch)(config)# exit LTP-8X(switch)# exit LTP-8X# save
LAG configuration
This chapter 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 two LACP modes. Passive — the terminal does not initiate creation of a logical link, but processes incoming LACP packets. Active — the terminal creates an aggregated communication link and initiates parameters conformance. The parameters are coordinated if equipment operates in active or passive LACP modes.
Scroll Pagebreak |
---|
LAG configuration
LAG configuration represents configuration of static aggregation and LACP. To configure LAG, perform the steps marked blue in Figure 28. LACP configuration requires all steps to be performed.
...
Step 1. LAG 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. Create a port-channel logical interface by using the interface port-channel command.
As a parameter, pass the number of the interface being created. Up to ten logical interfaces can be created.
Блок кода language xml LTP-8X(switch)(config)# interface port-channel 3 LTP-8X(switch)(config-if)#
- Step 3. Set general interface parameters: speed, duplex, flow-control, etc. Interfaces configuration is described in detail in the Interface configuration section.
Step 4. Configure aggregation by using the mode command. Pass the operation mode as a parameter. Operation modes are specified in Table 22.
Блок кода language xml LTP-8X(switch)(config-if)# mode lacp
Step 5. This step should only be performed for LACP configuration. Set a LACP system priority by using the lacp system-priority command. The no lacp system-priority command returns 32768 (default value).
Блок кода language xml LTP-8X(switch)(config-if)# exit LTP-8X(switch)(config)# lacp system-priority 32541
Примечание The lacp system-priority command can be executed in the configure view of the terminal switch.
Step 6. Specify load balancing rules by using the port-channel load-balance command if needed. Pass the load balancing mode as a parameter. Balance modes are specified in Table 23.
Блок кода language xml LTP-8X(switch)(config)# port-channel load-balance ip
Примечание The port-channel load-balance command can be executed in the configure view of the terminal switch.
Step 7. When used for load balancing, L4 parameters require a long hash. Enable the long hash by using the port-channel l4-long-hash enable command.
Блок кода language xml LTP-8X(switch)(config)# port-channel l4-long-hash enable
Примечание The port-channel l4-long-hash command can be executed in the configure view of the terminal switch.
Step 8. Add physical interfaces into the logical one by using the channel-group command. As a parameter, pass the number of the logical interface.
Блок кода language xml LTP-8X(switch)(config)# interface front-port 0 — 4 LTP-8X(switch)(config-if-range)# channel-group port-channel 3
Примечание The channel-group command can be executed in the configure view of an interface (a range) of the switch.
Step 9. This step should only be performed for LACP configuration. Set a priority for a physical interface by using the lacp port-priority command if necessary. The no lacp port-priority command resets port priority to the default value of 32768; 1 is the highest priority.
Блок кода language xml LTP-8X(switch)(config-if-range)# no lacp port-priority LTP-8X(switch)(config-if-range)# exit LTP-8X(switch)(config)# interface front-port 0 LTP-8X(switch)(config-if)# lacp port-priority 256
Примечание The lacp port-priority command can be executed in the configure view of a switch interface.
Step 10. This step should only be performed for LACP configuration. Use the lacp mode command to set an active or passive LACP mode.
Блок кода language xml LTP-8X(switch)(config-if)# exit LTP-8X(switch)(config)# interface port-channel 3 LTP-8X(switch)(config-if)# lacp mode active
Step 11. This step should only be performed for LACP configuration. In case of the active LACP mode, set an interval for transmission of LACP control packets by using the lacp rate command. Pass slow (30 seconds) or fast (1 second) as a parameter.
Блок кода language xml LTP-8X(switch)(config-if)# lacp rate slow
Step 12. Apply the configuration by using the commit command.
Блок кода language xml LTP-8X(switch)(config-if)# exit LTP-8X(switch)(config)# commit
Scroll Pagebreak
Якорь Настройка DHCP Relay Agent Настройка DHCP Relay Agent
DHCP Relay Agent configuration
This chapter describes configuration of DHCP Relay Agent in the terminal.
...
It also protects from illegal DHCP servers by controlling the source IP address of DHCP responses. Transmitted are only the DHCP responses, which arrived from IP addresses of trusted DHCP servers.
DHCP Relay Agent profiles management
A set of profiles is used for DHCP Relay Agent configuration. All VLANs use dhcp-ra-00 profile by default.
...
Step 1. Assign the default profile for all VLANs with the help of the gpon olt profile dhcp-ra dhcp-ra-00 command.
Блок кода language xml LTP-8X# configure terminal LTP-8X(config)# gpon olt profile dhcp-ra dhcp-ra-00
Step 2. Create a new DHCP Relay Agent profile with the help of the profile dhcp-ra command if necessary. Pass profile name as a parameter.
Блок кода language xml LTP-8X(config)# profile dhcp-ra dhcp-ra-01 LTP-8X(config-dhcp-ra)("dhcp-ra-01")# exit
Step 3. Assign the newly created profile to a selected VLAN with the gpon olt profile dhcp-ra dhcp-ra-01 command. As a parameter, pass the VID, which requires individual configuration.
Блок кода language xml LTP-8X(config)# gpon olt profile dhcp-ra dhcp-ra-01 vid 1000
Step 4. Check the changes by using the show gpon olt configuration command.
Блок кода language xml LTP-8X(config)# do show gpon olt configuration Profile dhcp-ra: dhcp-ra-00 OLT Profile DHCP Relay Agent 0
Блок кода language xml Profile dhcp-ra per VLAN 1000 [0]: Profile: dhcp-ra-01 OLT Profile DHCP Relay Agent 1
Step 5. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config)# do commit
Примечание To apply the changes, the OLT should be reconfigured.
DHCP Relay Agent profiles configuration
Step 1. Switch to the corresponding DHCP Relay Agent profile.
Блок кода language xml LTP-8X(config)# profile dhcp-ra dhcp-ra-01
Step 2. Enable DHCP traffic processing with the enable command.
Блок кода language xml LTP-8X(config-dhcp-ra)("dhcp-ra-01")# enable
Step 3. Enable insert/overwrite of DHCP option 82 with the help of the overwrite-option82 command if needed.
Блок кода language xml LTP-8X(config-dhcp-ra)("dhcp-ra-01")# overwrite-option82
Step 4. Specify the DHCP option 82 format with the help of the overwrite-option82 circuit-id and overwrite-option82 remote-id commands if needed. A list of possible tokens is given in Table 24.
Блок кода language xml LTP-8X(config-dhcp-ra)("dhcp-ra-01")# overwrite-option82 circuit-id "%HOSTNAME% %MAC% %OPT82_CID%" LTP-8X(config-dhcp-ra)("dhcp-ra-01")# overwrite-option82 remote-id "%OPT82_RID%"
Step 5. Enable DoS attack protection with the help of the dos-block command if needed. Specify a threshold for the number of DHCP queries per second that will block queries when exceeded. Use the dos-block packet-limit command for it. Use the dos-block block-time command to specify the blocking time in seconds.
Блок кода language xml LTP-8X(config-dhcp-ra)("dhcp-ra-01")# dos-block LTP-8X(config-dhcp-ra)("dhcp-ra-01")# dos-block packet-limit 200 LTP-8X(config-dhcp-ra)("dhcp-ra-01")# dos-block block-time 300
Step 6. Set a list of trusted DHCP servers with the help of the trusted primary and trusted secondary commands. Specify a response timeout for DHCP servers by using the trusted timeout command. Activate filters with the help of the trusted command.
Блок кода language xml LTP-8X(config-dhcp-ra)("dhcp-ra-01")# trusted primary 10.0.0.1 LTP-8X(config-dhcp-ra)("dhcp-ra-01")# trusted secondary 10.0.0.2 LTP-8X(config-dhcp-ra)("dhcp-ra-01")# trusted timeout 100 LTP-8X(config-dhcp-ra)("dhcp-ra-01")# trusted
Step 7. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config-dhcp-ra)("dhcp-ra-01")# do commit
Примечание To apply the changes, the OLT should be reconfigured.
Active DHCP leases monitoring
When enabled, DHCP-RA allows monitoring of DHCP leases. To view the list of sessions, use the do show interface gpon-port 0 dhcp sessions command.
...
Блок кода | ||
---|---|---|
| ||
LTP-8X# clear dhcp-sessions interface ont <0-7>[/0-127] |
Broadcast-unicast relay configuration
To reduce the broadcast traffic and avoid responses from illegal DHCP-servers, unicast messages can be configured to interact with the specified DHCP Relay Agent. Relay Agent can be individually started for each separate VLAN. The service allows processing only for the packets, which have only one 802.1q tag.
Step 1. Create an L3 interface by specifying the IP address of the VLAN the service is provided for. If the address of the DHCP server is in the same network as the management interface, skip Step 3. If the DHCP server is in the VLAN, which is specified in cross-connect, the IP address of the interface being created should be in the same network as the DHCP server, and you should skip Step 3.
Блок кода language xml LTP-8X(switch)(config)# vlan 2000 LTP-8X(switch)(config-vlan)# ip address 10.10.10.1/32
Step 2. Specify up to 3 addresses of DHCP servers.
Блок кода language xml LTP-8X(switch)(config-vlan)# ip dhcp relay 192.168.56.1 LTP-8X(switch)(config-vlan)# ip dhcp relay 192.168.56.2
Step 3. Create an L3 interface by specifying the IP address of the VLAN, which is used for switching in the network where the DHCP server is located.
Блок кода language xml LTP-8X(switch)(config)# vlan 1209 LTP-8X(switch)(config-vlan)# ip address 192.168.209.240/24
Step 4. If the addresses of the DHCP servers are located after the router available after the specified L3 interface, configure a static route.
Блок кода language xml LTP-8X# configure terminal LTP-8X(config)# ip route prefix 192.168.56.0 mask 24 gateway 192.168.209.5 LTP-8X(config)# do commit
Step 5. If VLAN in which interception of DHCP requests is implemented is the same as management VLAN of OLT (e.g. OLT connects to only one VLAN or traffic untagged), you need to explicitly enable redirection of DHCP requests on the VLAN.
Блок кода language xml LTP-8X(switch)(config)# vlan 1209 LTP-8X(switch)(config-vlan)# ip dhcp relaying
PPPoE Intermediate Agent configuration
This chapter describes configuration of PPPoE Intermediate Agent of the terminal.
...
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 25. The placeholders will be replaced with corresponding values, while the rest of the words will be passed as is.
...
PPPoE Intermediate Agent also limits the number of simultaneous PPPoE sessions. The restriction can be set for both the total number of terminal sessions and for every ONT separately.
PPPoE Intermediate Agent profile configuration
To configure a PPPoE Intermediate Agent profile, the following steps should be taken.
Step 1. Switch to the PPPoE Intermediate Agent profile.
Блок кода language xml LTP-8X# configure terminal LTP-8X(config)# profile pppoe-ia pppoe-ia-00 LTP-8X(config-pppoe-ia)("pppoe-ia-00")#
Step 2. Enable PPPoE traffic processing with the enable command.
Блок кода language xml LTP-8X(config-pppoe-ia)("pppoe-ia-00")# enable
Step 3. Specify the vendor specific tag format with the help of the format circuit-id and format remote-id commands. A list of possible tokens is given in Table 25.
Блок кода language xml LTP-8X(config-pppoe-ia)("pppoe-ia-00")# format circuit-id "%HOSTNAME%" LTP-8X(config-pppoe-ia)("pppoe-ia-00")# format remote-id "%PONSERIAL%:%GEMID%"
Step 4. Enable DoS attack protection with the help of the dos-block command if needed. Specify a threshold for the number of DHCP queries per second that will block queries when exceeded. Use the dos-block packet-limit command for it. Use the dos-block block-time command to specify the blocking time in seconds.
Блок кода language xml LTP-8X(config-pppoe-ia)("pppoe-ia-00")# dos-block LTP-8X(config-pppoe-ia)("pppoe-ia-00")# dos-block packet-limit 200 LTP-8X(config-pppoe-ia)("pppoe-ia-00")# dos-block block-time 300
Step 5. Set the limits of PPPoE sessions by using the sessions-limit command.
Блок кода language xml LTP-8X(config-pppoe-ia)("pppoe-ia-00")# sessions-limit 128 per-user 2
If there is no need to limit sessions for all ONTs, pass unlimited parameter in session-limit per-user command.
Блок кода language xml LTP-8X(config-pppoe-ia)("pppoe-ia-00")# sessions-limit per-user unlimited
If you need to disable limiting session for specified ONT (might be useful for SFP-ONU) and save limiting for others, define limiting globally in the profile and disable it in the interface ont settings.Scroll Pagebreak Блок кода language xml LTP-8X(config-pppoe-ia)("pppoe-ia-00")# sessions-limit 8192 per-user 2 LTP-8X(config-pppoe-ia)("pppoe-ia-00")# exit LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# pppoe-sessions-unlimit
Step 6. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config-pppoe-ia)("pppoe-ia-00")# do commit
Примечание To apply the changes, the OLT should be reconfigured.
Active PPPoE sessions monitoring
Enabling PPPoE-IA allows active PPPoE sessions to be monitored. To view the list of sessions, use the following command.
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)(if-ont-0/4)# do show interface gpon-port 0 pppoe session PPPoE sessions (1): ## Serial GPON-port Ont ID Port Client Session ID Duration Unblock 1 454C54586700008C 0 4 353 A8:F9:4B:E3:16:5C 0x0003 0:00:27 0:00:00 |
Disabling session monitoring
The session monitoring is enabled in PPPoE-IA by default. Due to the fact that system resources are used for each session, in this mode, there are 8192 sessions to be initialized through the OLT (the maximum session-limit value).
...
Примечание |
---|
PPPoE-IA is capable to detect sessions which are established while session monitoring is enabled. If a session was established before monitoring being enabled, re-initiate the session. |
Scroll Pagebreak |
---|
The IP Source Guard function allows restriction of unauthorised usage of IP addresses in the network by linking IP and MAC addresses of the source to a specific service on a specific ONT. There are two operation modes:
...
Примечание |
---|
To enable the IP Source Guard functions, enable DHCP-RA. For more information on DHCP-RA, see DHCP Relay Agent configuration. When IP Source Guard is enabled, any non-IP traffic is forbidden. |
IP Source Guard configuration
Step 1. Switch to the configure view.
Блок кода language xml LTP-8X# configure terminal
Step 2. Enable IP Source Guard and specify the mode.
Блок кода language xml LTP-8X(config)# ip source-guard enable LTP-8X(config)# ip source-guard mode dynamic
Step 3. Apply the changes by using the do commit command.
Блок кода language xml LTP-8X(config)# do commit
...
Примечание |
---|
IP Source Guard Database will work only if automatic time synchronization is implemented via NTP. |
Configuring multicast traffic between ONTs within the same tree
The functionality allows you to turn multicast traffic to the same port from which it been received. The configuration consists of two parts: vlan configuration, multicast in which pon-port should be deployed, and on which the functional will operate.
...
Якорь Настройка ONT Настройка ONT
ONT configuration
Якорь Сервисные модели предоставления услуг Сервисные модели предоставления услуг
Service Models
This chapter considers main terms and classification of service models.
...
Figure 30 — "VLAN for Service" service model architecture
Operating principle
The configuration model concept is used for implementation of different service models in the terminal. A configuration model defines general principles for data communication channelling for both OLT and ONTs.
...
VLAN for Service | VLAN for Subscriber | Broadcast to Unicast GEM | Dedicated Broadcast GEM | |
---|---|---|---|---|
Model 1 | - | + | + | - |
Model 2 | + | - | - | + |
Model 3 | + | - | - | + |
Model 1
Consider an example of Model 1 implementation.
The scheme of this service model is shown in the Figure 31.
...
Broadcast and unknown unicast traffic is transmitted in this model by replicating a corresponding packet (broadcast or unknown unicast) to the OLT. C-VLAN replicates services to all associated GEM ports and at the same time translates data to the corresponding U-VLAN for each service. The TR-069 service is replicated between the corresponding GEM ports of all subscribers (ONTs). Thus, the model implements "VLAN for Subscriber" for the VoIP, Internet, and IPTV unicast services, but uses "VLAN for Service" for the TR-069 service.
Scroll Pagebreak |
---|
Model 2
Consider an example of Model 2 implementation.
...
Thus, the model implements "VLAN for Service" for the VoIP, Internet, IPTV unicast, and TR-069 services.
Scroll Pagebreak |
---|
Model 3
Consider an example of Model 3 implementation.
...
Thus, the model implements "VLAN for Service".
Scroll Pagebreak |
---|
Model configuration
Step 1. Check the current configuration with the help of the show gpon olt configuration command.
Блок кода language xml LTP-8X# show gpon olt configuration: . . . Datapath: Model: model2 Broadcast gem port: 4095 Multicast gem port: 4094 . . .
Step 2. Set the model by using the gpon olt model command.
Блок кода language xml LTP-8X# configure terminal LTP-8X(config)# gpon olt model 3
Step 3. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config)# do commit
Scroll Pagebreak |
---|
ONT licensing
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.
Примечание |
---|
If a third-party ONT is connected to OLT without a license, the following entry will be made in the log file: |
Loading a license file to OLT
A license is a text file of the following format:
...
Use the copy command:
LTP-8X# copy tftp://<IP>/<PATH> fs://license
Download file from TFTP-server..
License successfully installed. Please reboot device for changes to make effectWhere:
- IP — TFTP server IP address;
- PATH — license file path on TFTP server.
Scroll Pagebreak
Use CLI:
LTP-8X# 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.Блок кода language xml LTP-8X# 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-8X# no license License file removed. License successfully deleted from system. LTP-8X# show license Active license information: No license installed |
Scroll Pagebreak |
---|
EasyСonfig. EasyMode
LTP-X EasyMode
EasyMode is a function set of LTP optical terminals. EasyMode is dedicated to fast GPON deployment according to realized service model. EasyMode allows providers to configure Triple Play services promptly.
...
- Acquaintance with GPON technology and ELTEX equipment;
- Fast testing of the main capabilities of the equipment;
- Automatic configuring of the equipment on a network.
Software and hardware requirements
The EasyMode is supported by the hardware of B and C revisions and by NTU terminals. For EasyMode operation, it is necessary to use the software no below than:
...
Detailed information about the easy configuration mode is contained in the LTP EasyMode manual document, which can be found in the Download Center.
Scroll Pagebreak |
---|
Automatic ONT activation
Automatic activation speeds up the process of adding new ONTs to an existing configuration with the necessary profiles.
Automatic ONT activation configuration
Step 1. Enable automatic ONT activation.
Блок кода language xml LTP-8X(config)# gpon olt auto-activation ont enable
Step 2. If necessary, specify a template that will be assigned to all auto-activated ONTs by default.
Блок кода language xml LTP-8X(config)# gpon olt auto-activation ont default template template-00
Step 3. If necessary, specify a template that will be assigned to ONT depending on their type (EquipmentID), during automatic activation.
Блок кода language xml LTP-8X(config)# gpon olt auto-activation ont type NTU-1 template NTU1_2149
Step 4. If necessary, specify the gpon-port on which this auto-activation rule will trigger.
Блок кода language xml TP-8X(config)# gpon olt auto-activation ont type NTU-1 template template-00 gpon-port 0-2
Step 5. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config)# do commit
Примечание |
---|
After applying the changes, the OLT will reconfigure. |
ONT configuration
This chapter describes general principles of ONT configuration. It also defines configuration profiles.
...
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.
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.
...
Figure 34 — ONT scope of operation
ONT profiles configuration
Cross-connect profile configuration
- Step 1. To configure a cross-connect profile, first you need to specify whether the service will be routed (transmitted through an ONT router) or bridged (use bridge connection). This can be done by changing the model parameter.
- Step 2. Then, you need to specify a service type in the type parameter. Some service types require the iphost parameter to be set that allows you to choose a definite instance of IP interface in the ONT.
- Step 3. A VLAN is configured in a cross-connect profile with the help of the following parameters: tag mode, outer vid, outer cos, inner vid, user vid, and user cos.
- Step 4. Tag mode enables upstream Q-in-Q mode; outer vid, outer cos, and inner vid specify internal and external Q-in-Q tags correspondingly. The CoS value of the internal tag is copied from the external one in this case. If the Q-in-Q mode is not used, only the outer vid and outer cos parameters are valid. The user vid and user cos parameters allow a tag to be specified, which will be used on the ONT side.
- Step 5. The mac-table-limit parameter allows restriction of records number in the MAC table of the OLT for this service.
- Step 6. The priority parameter allows allocation of all services of one T-CONT into queues with priorities (if ONT supports this method).
DBA profile configuration
This profile configures dynamic bandwidth allocation (DBA). These parameters allow specification of any T-CONT type described in G.984.3.
...
DBA configuration is described in details in DBA configuration.
Shaping profile configuration
Configuration of this profile allows restriction of upstream and downstream services.
...
The configuration of shaping profile represented detailed in Shaping configuration.
Ports profile configuration
The ports profile allows you to group ports in ONT. The profile also contains IGMP and multicast setting as they are separately adjusted for each port.
You can adjust up to 4 Ethernet ports and a VEIP virtual port, which will serve as a link between the OMCI and RG domains in ONT.
- Step 1. Ethernet ports are grouped with the help of the bridge-group parameter. Value 0 means that the port is associated with the RG domain (router). Other values mean port association with the OMCI domain, i. e. the port can be directly used in OLT to establish a data communication channel.
- Step 2. IGMP and multicast configuration is described in detail in IGMP and MLD configuration in terminal switch.
Management profile configuration
The management profile enables specific configuration of the TR-069 management protocol, namely configuration of a TR-client in ONT.
...
The TR-069 protocol configuration is described in detail in VoIP configuration.
Re-defining the parameters set in the cross-connect profile. Custom parameters
In some cases, it is necessary to define unique VLAN ID/802.1p tags for ONT. For solving this problem, you can use custom parameters instead of creating a profile.
Custom svid
Блок кода | ||
---|---|---|
| ||
LTP-8X# configure terminal LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# service 0 custom svid 1234 |
If cross-connect profile defined in the specified service has tag-mode double-tagged, VLAN ID of the external tag will be replaced. For single-tagged service, VLAN ID of the single tag will be replaced.
Custom cvid
Блок кода | ||
---|---|---|
| ||
LTP-8X# configure terminal LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# service 0 custom cvid 1234 |
...
Примечание |
---|
If you set custom svid and cvid simultaneously for single-tagged service, svid will be used for replacing the VLAN ID. |
Scroll Pagebreak |
---|
Блок кода | ||
---|---|---|
| ||
LTP-8X# configure terminal LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# service 0 custom cos 3 |
Replaces 802.1p field in a tag.
ONT configuration procedure
Figure below shows a step-by-step procedure of ONT configuration.
...
Step 1. Prior to proceed to ONT configuration, add an ONT into the OLT configuration. For an ONT to be added and configured, it does not need to be physically connected to the OLT. You can view the list of inactive ONTs with the help of the show interface ont <gpon-port> unactivated command.
Блок кода language xml LTP-8X# show interface ont 0 unactivated ----------------------------------- GPON-port 0 ONT unactivated list ----------------------------------- ## Serial ONT ID Channel Status RSSI[dBm] Version EquipmentID 1 ELTX5C00008C n/a 0 UNACTIVATED n/a n/a n/a 2 ELTX1A00001A n/a 0 UNACTIVATED n/a n/a n/a Total ONT count: 2
Step 2. To specify ONT settings, go to the corresponding view with the help of the interface ont command. Specify ONT serial number, password, or their combination.
Блок кода language xml LTP-8X# configure terminal LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# serial ELTX5C00008C LTP-8X(config)(if-ont-0/0)# password 0000000000
Примечание NTU-SFP-100 uses PON-Password «default» by default.
Step 3. Apply the configuration by using the commit command.
Блок кода language xml LTP-8X(config)(if-ont-0/0)# do commit
Step 4. View the ONT configuration by using the do show interface ont 0/0 configuration command.
Блок кода language xml LTP-8X(config)(if-ont-0/0)# do show interface ont 0/0 configuration ----------------------------------- [ONT0/0] configuration ----------------------------------- Description: ’’ Status: UP Serial: ELTX5C00008C Password: ’0000000000’ Fec up: false Downstream broadcast: true Downstream broadcast filter: true Ber interval: none Ber update period: 60 Rf port state: disabled Omci error tolerant: false Profile shaping: shaping-00 ONT Profile Shaping 0 Profile ports: ports-00 ONT Profile Ports 0 Profile management: unassigned Custom model: none Template: unassigned
Scroll Pagebreak |
---|
Consider configuration of a data communication channel, which is based on Model 1 and implements "VLAN for Subscriber" (except for the control service, which is implemented in S-VLAN).
...
Step 1. Assign a service model.
Блок кода language xml LTP-8X# configure terminal LTP-8X(config)# gpon olt model 1
Step 2. Create an Internet cross-connect profile for the configuration. By default, the profile uses a routed service. Configure a U-VLAN with the help of the user vid command (it equals 10 for the first service in this case).
Блок кода language xml LTP-8X(config)# profile cross-connect Internet LTP-8X(config-cross-connect)("Internet")# user vid 10
Scroll Pagebreak Step 3. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("Internet")# do show profile cross-connect Internet Name: ’Internet’ Description: ’ONT Profile Cross Connect 1’ Model: ont-rg Bridge group: - Tag mode: single-tagged Outer vid: 1 Outer cos: unused Inner vid: - U vid: 10 U cos: unused Mac table entry limit: unlimited Type: general Iphost eid: 0 Priority queue: 0
Step 4. By analogy with the described above, create another cross-connect profile (UC_IPTV) for the second service and configure it with U-VLAN 11.
Блок кода language xml LTP-8X(config)# profile cross-connect UC_IPTV LTP-8X(config-cross-connect)("UC_IPTV")# user vid 11
Step 5. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("UC_IPTV")# do show profile cross-connect UC_IPTV Name: ’UC_IPTV’ Description: ’ONT Profile Cross Connect 2’ Model: ont-rg Bridge group: - Tag mode: single-tagged Outer vid: 1 Outer cos: unused Inner vid: - U vid: 11 U cos: unused Mac table entry limit: unlimited Type: general Iphost eid: 0 Priority queue: 0
Примечание Use web configurator or ACS to adjust necessary settings for these services in the ONT.
Step 6. Specify DBA parameters. To do this, create a dba profile and adjust the corresponding settings. We set a value of a guaranteed bandwidth in this example.
Блок кода language xml LTP-8X(config)# profile dba AllServices LTP-8X(config-dba)("AllServices")# bandwidth guaranteed 500
Scroll Pagebreak Step 7. Check the changes made.
Блок кода language xml LTP-8X(config-dba)("AllServices")# do show profile dba AllServices Name: 'AllServices' Description: 'ONT Profile DBA 1' Dba: Sla data: Service class: type5 Status reporting: nsr Alloc size: 0 Alloc period: 0 Fixed bandwidth: 0 Guaranteed bandwidth: 500 Besteffort bandwidth: 1244000 T-CONT allocation scheme: share T-CONT with same profile
Step 8. To configure multicast traffic, create a ports profile, specify groups allowed for viewing, a VLAN to send IGMP packets, and the rules for relaying multicast traffic in the downstream direction across the VLAN for the UC_IPTV service.
Блок кода language xml LTP-8X(config)# profile ports Ports1 LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 vid 98 LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 group 224.0.0.1 239.255.255.255 LTP-8X(config-ports)("Ports1")# veip upstream vid 11 LTP-8X(config-ports)("Ports1")# veip upstream tag-control replace-tag LTP-8X(config-ports)("Ports1")# veip downstream vid 11 LTP-8X(config-ports)("Ports1")# veip downstream tag-control replace-tag
Step 9. Check the changes made.
Блок кода language xml LTP-8X(config-ports)("Ports1")# do show profile ports Ports1 ... Multicast dynamic entry [0]: Vlan id: 98 First group ip: 224.0.0.1 Last group ip: 239.255.255.255 Veip: Multicast enable: true Multicast port settings: Upstream igmp vid: 11 Upstream igmp prio: 0 Upstream igmp tag control: replace tag Downstream multicast vid: 11 Downstream multicast prio: 0 Downstream multicast tag control: replace tag Max groups: 0 Max multicast bandwidth: 0
Scroll Pagebreak Step 10. Configure a management profile. To do this, create a cross-connect profile and assign it with the management type.
Блок кода language xml LTP-8X(config)# profile cross-connect management LTP-8X(config-cross-connect)("management")# outer vid 9 LTP-8X(config-cross-connect)("management")# type management
Step 11. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("management")# do show profile cross-connect management Name: 'management' Description: 'ONT Profile Cross Connect 2' Model: ont-rg Bridge group: - Tag mode: single-tagged Outer vid: 9 Outer cos: unused Inner vid: - U vid: untagged U cos: unused Mac table entry limit: unlimited Type: management IP host index: 0 Priority queue: 0
Scroll Pagebreak Step 12. Assign the created profiles in the ONT.
Блок кода language xml LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# service 0 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 0 profile cross-connect Internet LTP-8X(config)(if-ont-0/0)# service 1 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 1 profile cross-connect UC_IPTV LTP-8X(config)(if-ont-0/0)# profile ports Ports1 LTP-8X(config)(if-ont-0/0)# service 2 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 2 profile cross-connect management LTP-8X(config)(if-ont-0/0)# do show interface ont 0/0 configuration ----------------------------------- [ONT0/0] configuration ----------------------------------- Description: '' Status: UP Serial: ELTX5C00008C ... Service [0]: Profile cross connect: Internet ONT Profile Cross Connect 1 Profile dba: AllServices ONT Profile DBA 1 Service [1]: Profile cross connect: UC_IPTV ONT Profile Cross Connect 2 Profile dba: AllServices ONT Profile DBA 1 Service [2]: Profile cross connect: management ONT Profile Cross Connect 3 Profile dba: AllServices ONT Profile DBA 1 ... Profile ports: Ports1 ONT Profile Ports 1
Step 13. VLAN for Subscriber requires a C-VLAN to be assigned for this ONT (subscriber). Assign S-VLAN 200 for the Internet and IPTV services by using the service X custom command (where X – service number). The management service operates in an S-VLAN, therefore no C-VLAN is defined for this service.
Блок кода language xml LTP-8X(config)(if-ont-0/0)# service 0 custom cvid 200 LTP-8X(config)(if-ont-0/0)# service 1 custom cvid 200 LTP-8X(config)(if-ont-0/0)# do show interface ont 0/0 configuration ... Service [0]: Profile cross connect: Internet ONT Profile Cross Connect 1 Profile dba: AllServices ONT Profile DBA 1 Custom svlan: 200 Custom CoS: unused Service [1]: Profile cross connect: UC_IPTV Profile dba: AllServices ONT Profile DBA 1 Custom svlan: 200 Custom CoS: Unused
Scroll Pagebreak Step 14. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config)(if-ont-0/0)# do commit
Step 15. Configure VLAN 200, 201, 9, and 98 in the switch view (see VLAN configuration).
Блок кода language xml LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# vlan 200,201,98,9 LTP-8X(switch)(config-vlan-range)# tagged front-port 0 LTP-8X(switch)(config-vlan-range)# tagged pon-port 0 – 7 LTP-8X(switch)(config-vlan-range)# exit LTP-8X(switch)(config)# commit LTP-8X(switch)(config)# exit
Step 16. Configure IGMP Proxy in the switch view for VLAN 98, enable the IGMP Proxy mode globally, and set the range of allowed IGMP groups. Also, enable IGMP snooping globally.
Блок кода language xml LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# ip igmp snooping LTP-8X(switch)(config)# ip igmp proxy report range 232.1.0.1 232.1.0.100 from all to 98 LTP-8X(switch)(config)# ip igmp proxy report enable LTP-8X(switch)(config)# commit LTP-8X(switch)(config)# exit
...
Step 1. Create an Internet cross-connect profile to configure PPPoE in the bridge. Configure the bridged service specifying the bridge group the ONT port will be connected to (in this case, it is equal to 10 for the first service), define a U-VLAN for transmission of tagged traffic to the port.
Блок кода language xml LTP-8X(config)# profile cross-connect Internet LTP-8X(config-cross-connect)("Internet")# bridge LTP-8X(config-cross-connect)("Internet")# bridge group 10 LTP-8X(config-cross-connect)("Internet")# user vid 10
Step 2. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("Internet")# do show profile cross-connect Internet Name: 'Internet' Description: 'ONT Profile Cross Connect 1' Model: ont Bridge group: 10 Tag mode: single-tagged Outer vid: 1 Outer cos: unused Inner vid: - U vid: untagged U cos: unused Mac table entry limit: unlimited Type: general IP host index: 0 Priority queue: 0
Step 3. By analogy with the described above, create another cross-connect profile (UC_IPTV) for the second service and configure it with bridge group 11.
Блок кода language xml LTP-8X(config)# profile cross-connect UC_IPTV LTP-8X(config-cross-connect)("UC_IPTV")# bridge LTP-8X(config-cross-connect)("UC_IPTV")# bridge group 11
Step 4. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("UC_IPTV")# do show profile cross-connect UC_IPTV Name: 'UC_UPTV' Description: 'ONT Profile Cross Connect 2' Model: ont Bridge group: 11 Tag mode: single-tagged Outer vid: 1 Outer cos: unused Inner vid: - U vid: untagged U cos: unused Mac table entry limit: unlimited Type: general IP host index: 0 Priority queue: 0
Scroll Pagebreak Step 5. Specify DBA parameters. To do this, create a dba profile and adjust the corresponding settings. We set a value of a guaranteed bandwidth in this example.
Блок кода language xml LTP-8X(config)# profile dba AllServices LTP-8X(config-dba)("AllServices")# bandwidth guaranteed 500
Step 6. Check the changes made.
Блок кода language xml LTP-8X(config-dba)("AllServices")# do show profile dba AllServices Name: 'AllServices' Description: 'ONT Profile DBA 1' Dba: Sla data: Service class: type5 Status reporting: nsr Alloc size: 0 Alloc period: 0 Fixed bandwidth: 0 Guaranteed bandwidth: 500 Besteffort bandwidth: 1244000 T-CONT allocation scheme: share T-CONT with same profile
Step 7. Associate the bridge group with an ONT port. To do this, create a ports profile and set the bridge group parameter to 10 for the eth0 port and to 11 for the eth1 port. Set the rules of multicast traffic processing for port 1.
Блок кода language xml LTP-8X(config)# profile ports Ports1 LTP-8X(config-ports)("Ports1")# port 0 bridge group 10 LTP-8X(config-ports)("Ports1")# port 1 bridge group 11 LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 vid 98 LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 group 224.0.0.1 239.255.255.255 LTP-8X(config-ports)("Ports1")# port 1 multicast LTP-8X(config-ports)("Ports1")# port 1 igmp downstream vid 98 LTP-8X(config-ports)("Ports1")# port 1 igmp downstream tag-control remove-tag
Scroll Pagebreak Step 8. Check the changes made.
Блок кода LTP-8X(config-ports)("Ports1")# do show profile ports Ports1 ... Igmp settings: ... Multicast dynamic entry [0]: Vlan id: 98 First group ip: 224.0.0.1 Last group ip: 239.255.255.255 ... Port [0]: Speed: auto Duplex: auto Bridge group: 10 Spanning tree for bridge group: false Multicast enable: true Multicast port settings: Upstream igmp vid: 1 Upstream igmp prio: 0 Upstream igmp tag control: pass Downstream multicast vid: 1 Downstream multicast prio: 0 Downstream multicast tag control: pass Max groups: 0 Max multicast bandwidth: 0 Shaper downstream: Enable: false Commited rate: 1000000 Shaper upstream: Enable: false Commited rate: 1000000 Port [1]: Speed: auto Duplex: auto Bridge group: 11 Spanning tree for bridge group: false Multicast enable: false Multicast port settings: Upstream igmp vid: 1 Upstream igmp prio: 0 Upstream igmp tag control: pass Downstream multicast vid: 98 Downstream multicast prio: 0 Downstream multicast tag control: remove-tag Max groups: 0 Max multicast bandwidth: 0 Shaper downstream: Enable: false Commited rate: 1000000 Shaper upstream: Enable: false Commited rate: 1000000
Scroll Pagebreak Step 9. Configure a management profile. To do this, create a cross-connect profile and assign it with the management type and the bridge model.
Блок кода language xml LTP-8X(config)# profile cross-connect management LTP-8X(config-cross-connect)("management")# bridge LTP-8X(config-cross-connect)("management")# outer vid 9 LTP-8X(config-cross-connect)("management")# type management
Step 10. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("management")# do show profile cross-connect management Name: 'management' Description: 'ONT Profile Cross Connect 2' Model: ont Bridge group: 255 Tag mode: single-tagged Outer vid: 9 Outer cos: unused Inner vid: - U vid: untagged U cos: unused Mac table entry limit: unlimited Type: management IP host index: 0 Priority queue: 0
Step 11. Assign the created profiles in the ONT.
Блок кода language xml LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# service 0 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 0 profile cross-connect Internet LTP-8X(config)(if-ont-0/0)# service 1 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 1 profile cross-connect UC_IPTV LTP-8X(config)(if-ont-0/0)# service 2 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 2 profile cross-connect management LTP-8X(config)(if-ont-0/0)# profile ports Ports1 LTP-8X(config)(if-ont-0/0)# do show interface ont 0/0 configuration ----------------------------------- [ONT0/0] configuration ----------------------------------- Description: '' Enabled: true Serial: ELTX5C00008C Password: '0000000000' Fec up: false Easy mode: false Downstream broadcast: true Downstream broadcast filter: true Ber interval: none Ber update period: 60 Rf port state: disabled Omci error tolerant: false
Блок кода Service [0]: Profile cross connect: Internet ONT Profile Cross Connect 1 Profile dba: AllServices ONT Profile DBA 1 Custom cross connect: disabled Service [1]: Profile cross connect: UC_IPTV ONT Profile Cross Connect 2 Profile dba: AllServices ONT Profile DBA 1 Custom cross connect: disabled Service [2]: Profile cross connect: management ONT Profile Cross Connect 3 Profile dba: AllServices ONT Profile DBA 1 Custom cross connect: disabled Profile shaping: shaping-00 ONT Profile Shaping 0 Profile ports: Ports1 ONT Profile Ports 1 Profile management: unassigned Template: unassigned Pppoe sessions unlimited: false
Step 12. VLAN for Subscriber requires a C-VLAN to be assigned for this ONT (subscriber). Assign unique VLAN ID 200 for the Internet and IPTV services by using the service X custom command (where X — service number). The management service operates in an S-VLAN, therefore, settings from the profile are used for the service.
Блок кода language xml LTP-8X(config)(if-ont-0/0)# service 0 custom svid 200 LTP-8X(config)(if-ont-0/0)# service 1 custom svid 200 LTP-8X(config)(if-ont-0/0)# do show interface ont 0/0 configuration ... Service [0]: Profile cross connect: Service1sh ONT Profile Cross Connect 1 Profile dba: AllServices ONT Profile DBA 1 Custom cross connect: enabled Custom s-vid: 200 Custom c-vid: unused Custom CoS: unused
Step 13. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config)(if-ont-0/0)# do commit
Step 14. Configure VLAN 200 in the switch view (see VLAN configuration).
Блок кода language xml LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# vlan 200 LTP-8X(switch)(config-vlan)# tagged front-port 0 LTP-8X(switch)(config-vlan)# tagged pon-port 0 – 7 LTP-8X(switch)(config-vlan)# exit LTP-8X(switch)(config)# commit LTP-8X(switch)(config)# exit
Scroll Pagebreak Step 15. Configure IGMP Proxy in the switch view for VLAN 98, enable the IGMP Proxy mode globally, and set the range of allowed IGMP groups. Also, enable IGMP snooping globally.
Блок кода language xml LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# ip igmp proxy report enable LTP-8X(switch)(config)# ip igmp proxy report range 232.1.0.1 232.1.0.100 from all to 98 LTP-8X(switch)(config)# ip igmp snooping LTP-8X(switch)(config)# commit LTP-8X(switch)(config)# exit
Model 2
Model 2 is a hybrid of Model 1 and Model 3. It is based on «VLAN for Service». Model 2 services configuration is similar to Model 3.
Model 3
Consider configuration of ONT data communication for Model 3, which implements the «VLAN for Service» principle.
...
Step 1. Assign a service model.
Блок кода language xml LTP-8X# configure terminal LTP-8X(config)# gpon olt model 3
Scroll Pagebreak Step 2. Create an Internet cross-connect profile for the configuration. By default, the profile uses a routed service. Configure a U-VLAN with the help of the u-vid command (it equals 200 for the first service in this case). To assign an S-VLAN, use the outer vid 200 command.
Блок кода language xml LTP-8X(config)# profile cross-connect Internet LTP-8X(config-cross-connect)("Internet")# user vid 200 LTP-8X(config-cross-connect)("Internet")# outer vid 200
Step 3. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("Internet")# do show profile cross-connect Internet Name: 'Internet' Description: 'ONT Profile Cross Connect 1' Model: ont-rg Bridge group: - Tag mode: single-tagged Outer vid: 200 Outer cos: unused Inner vid: - U vid: 200 U cos: unused Mac table entry limit: unlimited Type: general IP host index: 0 Priority queue: 0
Step 4. By analogy with the described above, create another cross-connect profile (UC_IPTV) for the second service and configure it with U-VLAN 201, S-VLAN 201.
Блок кода language xml LTP-8X(config)# profile cross-connect UC_IPTV LTP-8X(config-cross-connect)("UC_IPTV")# user vid 201 LTP-8X(config-cross-connect)("UC_IPTV")# outer vid 201
Step 5. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("UC_IPTV")# do show profile cross-connect UC_IPTV Name: 'UC_IPTV' Description: 'ONT Profile Cross Connect 2' Model: ont-rg Bridge group: - Tag mode: single-tagged Outer vid: 201 Outer cos: unused Inner vid: - U vid: 201 U cos: unused Mac table entry limit: unlimited Type: general IP host index: 0 Priority queue: 0
Scroll Pagebreak Step 6. Specify DBA parameters. To do this, create a dba profile and adjust the corresponding settings. We set a value of a guaranteed bandwidth in this example.
Блок кода language xml LTP-8X(config)# profile dba AllServices LTP-8X(config-dba)("AllServices")# bandwidth guaranteed 500
Step 7. Check the changes made.
Блок кода language xml LTP-8X(config-dba)("AllServices")# do show profile dba AllServices Name: 'AllServices' Description: 'ONT Profile DBA 1' Dba: Sla data: Service class: type5 Status reporting: nsr Alloc size: 0 Alloc period: 0 Fixed bandwidth: 0
Step 8. To configure multicast traffic, create a cross-connect profile and set the VLAN intended for multicast transmission as an S-VLAN and U-VLAN.
Блок кода language xml LTP-8X(config)# profile cross-connect MC_IPTV LTP-8X(config-cross-connect)("MC_IPTV")# user vid 98 LTP-8X(config-cross-connect)("MC_IPTV")# outer vid 98
Step 9. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("MC_IPTV")# do show profile cross-connect MC_IPTV Name: 'MC_IPTV' Description: 'ONT Profile Cross Connect 3' Model: ont-rg Bridge group: - Tag mode: single-tagged Outer vid: 98 Outer cos: unused Inner vid: - U vid: 98 U cos: unused Mac table entry limit: unlimited Type: general IP host index: 0 Priority queue: 0
Примечание Use web configurator or ACS to adjust necessary settings for these services in the ONT.
Scroll Pagebreak Step 10. After that, to configure multicast traffic, create a ports profile, specify groups allowed for viewing, a VLAN to send IGMP packets, and the rules for relaying multicast traffic in the downstream direction across the VLAN for the UC_IPTV service.
Блок кода language xml LTP-8X(config)# profile ports Ports1 LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 vid 98 LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 group 224.0.0.1 239.255.255.255 LTP-8X(config-ports)("Ports1")# veip upstream vid 98 LTP-8X(config-ports)("Ports1")# veip upstream tag-control replace-tag LTP-8X(config-ports)("Ports1")# veip downstream vid 98 LTP-8X(config-ports)("Ports1")# veip downstream tag-control replace-tag
Step 11. Check the changes made.
Блок кода LTP-8X(config-ports)("Ports1")# do show profile ports Ports1 ... Igmp settings: Multicast dynamic entry [0]: Vlan id: 98 First group ip: 224.0.0.1 Last group ip: 239.255.255.255 ... Veip: Multicast enable: false Multicast port settings: Upstream igmp vid: 98 Upstream igmp prio: 0 Upstream igmp tag control: replace-tag Downstream multicast vid: 98 Downstream multicast prio: 0 Downstream multicast tag control: replace-tag Max groups: 0 Max multicast bandwidth: 0 ...
Step 12. Configure a management profile. To do this, create a cross-connect profile and assign it with the management type.
Блок кода language xml LTP-8X(config)# profile cross-connect management LTP-8X(config-cross-connect)("management")# outer vid 9 LTP-8X(config-cross-connect)("management")# type management
Scroll Pagebreak Step 13. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("management")# do show profile cross-connect management Name: 'management' Description: 'ONT Profile Cross Connect 4' Model: ont-rg Bridge group: - Tag mode: single-tagged Outer vid: 9 Outer cos: unused Inner vid: - U vid: untagged U cos: unused Mac table entry limit: unlimited Type: management IP host index: 0 Priority queue: 0
Step 14. Assign the created profiles in the ONT.
Блок кода LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# service 0 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 0 profile cross-connect Internet LTP-8X(config)(if-ont-0/0)# service 1 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 1 profile cross-connect UC_IPTV LTP-8X(config)(if-ont-0/0)# profile ports Ports1 LTP-8X(config)(if-ont-0/0)# service 2 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 2 profile cross-connect management LTP-8X(config)(if-ont-0/0)# service 3 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 3 profile cross-connect MC_IPTV
Step 15. Check the changes made.
Блок кода language xml LTP-8X(config)(if-ont-0/0)# do show interface ont 0/0 configuration ----------------------------------- [ONT0/0] configuration ----------------------------------- Description: '' Enabled: true Serial: ELTX5C00008C Password: '0000000000' Fec up: false Easy mode: false Downstream broadcast: true Downstream broadcast filter: true Ber interval: none Ber update period: 60 Rf port state: disabled Omci error tolerant: false Service [0]: Profile cross connect: Internet ONT Profile Cross Connect 1 Profile dba: AllServices ONT Profile DBA 1 Custom cross connect: disabled
Блок кода Service [1]: Profile cross connect: UC_IPTV ONT Profile Cross Connect 2 Profile dba: AllServices ONT Profile DBA 1 Custom cross connect: disabled Service [2]: Profile cross connect: management ONT Profile Cross Connect 3 Profile dba: AllServices ONT Profile DBA 1 Custom cross connect: disabled Profile shaping: shaping-00 ONT Profile Shaping 0 Profile ports: Ports1 ONT Profile Ports 1 Profile management: unassigned Template: unassigned Pppoe sessions unlimited: false LTP-8X(config)(if-ont-0/0)# do show interface ont 0/0 configuration
Step 16. Configure VLAN 200, 201, 9 and 98 in the switch view (see VLAN configuration).
Блок кода language xml LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# vlan 200,201,98,9 LTP-8X(switch)(config-vlan-range)# tagged front-port 0 LTP-8X(switch)(config-vlan-range)# tagged pon-port 0 – 7 LTP-8X(switch)(config-vlan-range)# exit LTP-8X(switch)(config)# commit LTP-8X(switch)(config)# exit
Step 17. Configure IGMP Proxy in the switch view for VLAN 98, enable the IGMP Snooping and IGMP Proxy mode globally, and set the range of allowed IGMP groups.
Блок кода language xml LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# ip igmp proxy report enable LTP-8X(switch)(config)# ip igmp proxy report range 232.1.0.1 232.1.0.100 from all to 98 LTP-8X(switch)(config)# ip igmp snooping LTP-8X(switch)(config)# commit LTP-8X(switch)(config)# exit
Scroll Pagebreak
...
Step 1. Create an Internet cross-connect profile to configure PPPoE in the bridge. Configure the bridged service specifying the bridge group the ONT port will be connected to (in this case, it is equal to 10 for the first service).
Блок кода language xml LTP-8X(config)# profile cross-connect Internet LTP-8X(config-cross-connect)("Internet")# bridge LTP-8X(config-cross-connect)("Internet")# bridge group 10
Step 2. To assign an S-VLAN, use the outer vid 200 command: The LAN port of the ONT will send tagged traffic. To enable this, set U-VLAN equal to S-VLAN.
Блок кода language xml LTP-8X(config-cross-connect)("Internet")# outer vid 200 LTP-8X(config-cross-connect)("Internet")# user vid 200
Step 3. Check the changes made.
Блок кода LTP-8X(config-cross-connect)("Internet")# do show profile cross-connect Internet Name: 'Internet' Description: 'ONT Profile Cross Connect 1' Model: ont Bridge group: 10 Tag mode: single-tagged Outer vid: 200 Outer cos: unused
Блок кода language xml Inner vid: - U vid: 200 U cos: unused Mac table entry limit: unlimited Type: general IP host index: 0 Priority queue: 0
Step 4. By analogy with the described above, create another cross-connect profile (UC_IPTV) for the second service and configure it with bridge group 11 and S-VLAN 201.
Блок кода language xml LTP-8X(config)# profile cross-connect UC_IPTV LTP-8X(config-cross-connect)("UC_IPTV")# bridge LTP-8X(config-cross-connect)("UC_IPTV")# bridge group 11 LTP-8X(config-cross-connect)("UC_IPTV")# outer vid 201
Step 5. Set U-VID to untagged to have untagged traffic outgoing from the ONT port.
Блок кода language xml LTP-8X(config-cross-connect)("UC_IPTV")# user vid untagged
Step 6. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("UC_IPTV")# do show profile cross-connect UC_IPTV Name: 'UC_IPTV' Description: 'ONT Profile Cross Connect 2' Model: ont Bridge group: 10 Tag mode: single-tagged Outer vid: 201 Outer cos: unused Inner vid: - U vid: untagged U cos: unused Mac table entry limit: unlimited Type: general IP host index: 0 Priority queue: 0
Step 7. Specify DBA parameters. To do this, create a dba profile and adjust the corresponding settings. We set a value of a guaranteed bandwidth in this example.
Блок кода language xml LTP-8X(config)# profile dba AllServices LTP-8X(config-dba)("AllServices")# bandwidth guaranteed 500
Scroll Pagebreak Step 8. Check the changes made.
Блок кода LTP-8X(config-dba)("AllServices")# do show profile dba AllServices Name: 'AllServices' Description: 'ONT Profile DBA 1' Dba: Sla data:
Блок кода language xml Service class: type5 Status reporting: nsr Alloc size: 0 Alloc period: 0 Fixed bandwidth: 0 Guaranteed bandwidth: 500 Besteffort bandwidth: 1244000 T-CONT allocation scheme: share T-CONT with same profile
Step 9. Associate the bridge group with an ONT port. To do this, create a ports profile and set the bridge group parameter to 10 for the eth0 port and to 11 for the eth1 port. Set the rules of multicast traffic processing for port 1.
Блок кода language xml LTP-8X(config)# profile ports Ports1 LTP-8X(config-ports)("Ports1")# port 0 bridge group 10 LTP-8X(config-ports)("Ports1")# port 1 bridge group 11 LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 vid 98 LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 group 224.0.0.1 239.255.255.255 LTP-8X(config-ports)("Ports1")# port 1 multicast LTP-8X(config-ports)("Ports1")# port 1 igmp downstream vid 98 LTP-8X(config-ports)("Ports1")# port 1 igmp downstream tag-control remove-tag
Scroll Pagebreak Step 10. Check the changes made.
Блок кода language xml LTP-8X(config-ports)("Ports1")# do show profile ports Ports1 ... Igmp settings: ... Multicast dynamic entry [0]: Vlan id: 98 First group ip: 224.0.0.1 Last group ip: 239.255.255.255 ... Port [0]: Speed: auto Duplex: auto Bridge group: 10 Spanning tree for bridge group: false Multicast enable: true Multicast port settings: Upstream igmp vid: 1 Upstream igmp prio: 0 Upstream igmp tag control: pass Downstream multicast vid: 1 Downstream multicast prio: 0 Downstream multicast tag control: pass Max groups: 0 Max multicast bandwidth: 0 Shaper downstream: Enable: false Commited rate: 1000000 Shaper upstream: Enable: false Commited rate: 1000000
Блок кода language xml Port [1]: Speed: auto Duplex: auto Bridge group: 11 Spanning tree for bridge group: false Multicast enable: false Multicast port settings: Upstream igmp vid: 1 Upstream igmp prio: 0 Upstream igmp tag control: pass Downstream multicast vid: 98 Downstream multicast prio: 0 Downstream multicast tag control: remove-tag Max groups: 0 Max multicast bandwidth: 0 Shaper downstream: Enable: false Commited rate: 1000000 Shaper upstream: Enable: false Commited rate: 1000000 ...
Scroll Pagebreak Step 11. Configure a management profile. To do this, create a cross-connect profile and assign it with the management type and the bridge model.
Блок кода language xml LTP-8X(config)# profile cross-connect management LTP-8X(config-cross-connect)("management")# bridge LTP-8X(config-cross-connect)("management")# outer vid 9 LTP-8X(config-cross-connect)("management")# type management
Step 12. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("management")# do show profile cross-connect management Name: 'management' Description: 'ONT Profile Cross Connect 3' Model: ont Bridge group: 255 Tag mode: single-tagged Outer vid: 9 Outer cos: unused Inner vid: - U vid: untagged U cos: unused Mac table entry limit: unlimited Type: management IP host index: 0 Priority queue: 0
Scroll Pagebreak Step 13. Assign the created profiles in the ONT.
Блок кода language xml LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# service 0 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 0 profile cross-connect Internet LTP-8X(config)(if-ont-0/0)# service 1 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 1 profile cross-connect UC_IPTV LTP-8X(config)(if-ont-0/0)# service 2 profile dba AllServices LTP-8X(config)(if-ont-0/0)# service 2 profile cross-connect management LTP-8X(config)(if-ont-0/0)# profile ports Ports1 LTP-8X(config)(if-ont-0/0)# do show interface ont 0/0 configuration ----------------------------------- [ONT0/0] configuration ----------------------------------- Description: '' Enabled: true Serial: ELTX5C00008C Password: '0000000000' Fec up: false Easy mode: false Downstream broadcast: true Downstream broadcast filter: true Ber interval: none Ber update period: 60 Rf port state: disabled Omci error tolerant: false Service [0]: Profile cross connect: Internet ONT Profile Cross Connect 1 Profile dba: AllServices ONT Profile DBA 1 Custom cross connect: disabled Service [1]: Profile cross connect: UC_IPTV ONT Profile Cross Connect 2 Profile dba: AllServices ONT Profile DBA 1 Custom cross connect: disabled Service [2]: Profile cross connect: management ONT Profile Cross Connect 3 Profile dba: AllServices ONT Profile DBA 1 Custom cross connect: disabled Profile shaping: shaping-00 ONT Profile Shaping 0 Profile ports: Ports1 ONT Profile Ports 1 Profile management: unassigned Template: unassigned Pppoe sessions unlimited: false
Step 14. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config)(if-ont-0/1)# do commit
Scroll Pagebreak Step 15. Configure VLAN 200, 201, 9 and 98 in the switch view (see VLAN configuration).
Блок кода language xml LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# vlan 200,201,98,9 LTP-8X(switch)(config-vlan-range)# tagged front-port 0 LTP-8X(switch)(config-vlan-range)# tagged pon-port 0 – 7 LTP-8X(switch)(config-vlan-range)# exit LTP-8X(switch)(config)# commit LTP-8X(switch)(config)# exit
Step 16. Configure IGMP Proxy in the switch view for VLAN 98, enable the IGMP Snooping and IGMP Proxy mode globally, and set the range of allowed IGMP groups.
Блок кода language xml LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# ip igmp proxy report enable LTP-8X(switch)(config)# ip igmp proxy report range 232.1.0.1 232.1.0.100 from all to 98 LTP-8X(switch)(config)# ip igmp snooping LTP-8X(switch)(config)# commit LTP-8X(switch)(config)# exit
Scroll Pagebreak
Tunnelling configuration
Usual profiles in the tag-mode, single-tag or double-tag modes are aimed at mapping the traffic, which is transmitted to the gem port and tagged as user vid or untagged, into the traffic tagged outer vid or outer:inner vid respectively.
...
Scroll Pagebreak |
---|
Якорь | ||||
---|---|---|---|---|
|
DBA configuration
This chapter considers DBA configuration for ONT.
...
The terminal allows configuration of up to 256 default allocations per channel. When one ONT is connected, at least one default allocation will be provided. Thus, when 128 subscribers are connected to a channel, 128 service allocations will be provided. The remaining 128 allocations will be enough to process data, but not enough to process more than one service in its own allocation. You need to follow the rule: Amax = 256/N – 1, where Amax — the maximum quantity of allocations for user data of an ONT, N — the quantity of ONTs on a channel. If the calculated amount of services exceeds ONT Amax, configure a combination of multiple services into a single allocation. For more detailed information, see Services in one T-CONT.
DBA parameters are configured in the dba profile. These parameters allow specification of any T-CONT type described in G.984.3. First of all, choose service-class to define the basic DBA algorithm. After that, configure status-reporting to define the type of ONT queues status report. The fixed-bandwidth, guaranteed-bandwidth, and besteffort-bandwidth parameters define the fixed, guaranteed, and best-effort bandwidth correspondingly. Table 28 shows the correspondence between the dba profile settings and T-CONT types.
...
- when an ONT service is assigned a dba profile, an Alloc-ID is created for the ONT on the OLT side, and a corresponding T-CONT is configured on the ONT side.
- if different ONTs are assigned the same profile, they will each have a separate Alloc-ID created with the same allocation parameters.
- if the same dba profiles are assigned to different services of the same ONT with allocation-scheme share-t-cont, these services will work in the same allocation and have the same allocation parameters.
- if the same dba profiles are assigned to different services of the same ONT with allocation-new-t-cont, these services will work in different allocations, and the number of Alloc-IDs created for the ONT equals the number of assigned dba profiles.
DBA global settings
Latency reduction mode
Enabling DBA latency reduction mode corrects the procedure of polling active allocations and activates redistribution of the fixed bandwidth between connected ONTs. The function is available for use on trees with any number of ONTs.
...
Примечание |
---|
Enabling this mode can lead to GPON port bandwidth reduction to 5–10 %. |
DBA short cycle mode
Enabling this mode reduces DBA cycle for the indicated interfaces, which allows to optimize bandwidth allocation for trees with a small number of connected ONTs.
...
Примечание |
---|
Enabling this mode is not recommended for trees with more than 32 connected ONTs. |
Scroll Pagebreak |
---|
DBA profiles assignment
Services in different T-CONTs
Two Alloc-IDs will be allocated for ONTs in the OLT. Each service will operate in its allocation. There will be two T-CONTs on the ONT side corresponding to the allocations.
Step 1. Each ONT should have two services in different T-CONTs. To do this, assign two dba profiles by using the profile dba command.
Блок кода language xml LTP-8X(config)# profile dba ServiceInternet LTP-8X(config-dba)("ServiceInternet")# exit LTP-8X(config)# profile dba ServiceVoIP LTP-8X(config-dba)("ServiceVoIP")# exit
Step 2. Specify an individual allocations distribution scheme by using the allocation-scheme command.
Блок кода language xml LTP-8X(config)# profile dba ServiceInternet LTP-8X(config-dba)("ServiceInternet")#allocation-scheme allocate-new-t-cont LTP-8X(config-dba)("ServiceInternet")# exit LTP-8X(config)# profile dba ServiceVoIP LTP-8X(config-dba)("ServiceVoIP")# allocation-scheme allocate-new-t-cont LTP-8X(config-dba)("ServiceVoIP")# exit
Step 3. Assign the profiles to services by using the service <id> profile dba command.
Блок кода language xml LTP-8X(config)(if-ont-0/0)# service 0 profile dba ServiceInternet LTP-8X(config)(if-ont-0/0)# service 1 profile dba ServiceVoIP
The configuration will be as follows:
Блок кода LTP-8X(config)(if-ont-0/0)# do show interface ont 0/0 configuration ... Service [0]: Profile cross connect: ServiceInternet ONT Profile Cross Connect 0 Profile dba: AllServices ONT Profile DBA 3 Custom cross connect: disabled Service [1]: Profile cross connect: ServiceVoIP ONT Profile Cross Connect 1 Profile dba: AllServices ONT Profile DBA 3 Custom cross connect: disabled ...
Step 4. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config)(if-ont-0/0)# do commit
Якорь Услуги в одном T-CONT Услуги в одном T-CONT
Services in one T-CONT
One Alloc-ID will be allocated for ONTs in the OLT. Each ONT will have one T-CONT configured. The T-CONT will be used to transfer traffic from multiple services. Traffic priority will be based on the value of the priority queue field of the corresponding cross-connect profiles.
Step 1. Each ONT should have three services in one T-CONT. To do this, assign a dba profile by using the profile dba command.
Блок кода language xml LTP-8X(config)# profile dba AllServices
Step 2. Each ONT should have all services in one T-CONT. To do this, specify an allocation scheme by using the allocation-scheme command.
Блок кода language xml LTP-8X(config-dba)("AllServices")# allocation-scheme share-t-cont
Step 3. Assign the profile to three services by using the service <id> profile dba command.
Блок кода language xml LTP-8X(config)(if-ont-0/1)# service 0 profile dba AllServices LTP-8X(config)(if-ont-0/1)# service 1 profile dba AllServices LTP-8X(config)(if-ont-0/1)# service 2 profile dba AllServices
The configuration will be as follows:
Блок кода language xml LTP-8X(config)(if-ont-0/1)# do show interface ont 0/1 configuration ... Service [0]: Profile cross connect: ServiceInternet ONT Profile Cross Connect 0
Блок кода Profile dba: AllServices ONT Profile DBA 3 Custom cross connect: disabled Service [1]: Profile cross connect: ServiceVoIP ONT Profile Cross Connect 1 Profile dba: AllServices ONT Profile DBA 3 Custom cross connect: disabled Service [2]: Profile cross connect: ServiceIPTV ONT Profile Cross Connect 2 Profile dba: AllServices ONT Profile DBA 3 Custom cross connect: disabled ...
Step 4. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config)(if-ont-0/1)# do commit
Scroll Pagebreak
One profile for multiple ONTs
This is a typical scenario in most cases, when similar services require the same DBA parameters on different ONTs.
...
For more information about SLA parameters, see DBA parameters configuration.
Step 1. Define two dba profiles by using the profile dba command.
Блок кода language xml LTP-8X(config)# profile dba ServiceVoIP LTP-8X(config-dba)("ServiceVoIP")# exit LTP-8X(config)# profile dba OtherServices
Step 2. Specify an individual allocations distribution scheme by using the allocation-scheme command.
Блок кода language xml LTP-8X(config)# profile dba ServiceVoIP LTP-8X(config-dba)("ServiceVoIP")# allocation-scheme allocate-new-t-cont LTP-8X(config-dba)("ServiceVoIP")# exit LTP-8X(config)# profile dba OtherServices LTP-8X(config-dba)("OtherServices")# exit
Step 3. Assign the profiles to the corresponding services of every ONT by using the service <id> profile dba command.
Блок кода language xml LTP-8X(config)# interface ont 0/0-1 LTP-8X(config)(if-ont-0/0-1)# service 0 profile dba OtherServices LTP-8X(config)(if-ont-0/0-1)# service 1 profile dba ServiceVoIP LTP-8X(config)(if-ont-0/0-1)# service 2 profile dba OtherServices
ONT configurations will be as follows:Scroll Pagebreak Блок кода language xml LTP-8X(config)(if-ont-0/0-1)# do show interface ont 0/0-1 configuration ----------------------------------- [ONT0/0] configuration ----------------------------------- ... Service [0]: Profile cross connect: ServiceInternet ONT Profile Cross Connect 0 Profile dba: OtherServices ONT Profile DBA 4 Custom cross connect: disabled Service [1]: Profile cross connect: ServiceVoIP ONT Profile Cross Connect 0 Profile dba: ServiceVoIP ONT Profile DBA 2 Custom cross connect: disabled Service [2]: Profile cross connect: SecurityiAlarm ONT Profile Cross Connect 0 Profile dba: OtherServices ONT Profile DBA 4 Custom cross connect: disabled ... ----------------------------------- [ONT0/1] configuration ----------------------------------- ... Service [0]: Profile cross connect: ServiceInternet ONT Profile Cross Connect 0 Profile dba: OtherServices ONT Profile DBA 4 Custom cross connect: disabled Service [1]: Profile cross connect: ServiceVoIP ONT Profile Cross Connect 0 Profile dba: ServiceVoIP ONT Profile DBA 2 Custom cross connect: disabled Service [2]: Profile cross connect: SecurityiAlarm ONT Profile Cross Connect 0 Profile dba: OtherServices ONT Profile DBA 4 Custom cross connect: disabled
Step 4. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config)(if-ont-0/0-1)# do commit
Якорь Настройка параметров DBA Настройка параметров DBA
Scroll Pagebreak |
---|
DBA parameters configuration
T-CONT type 1 configuration
Consider configuration of a 100 Mbps fixed bandwidth.
Step 1. Specify a T-CONT type by using the sla class command.
Блок кода language xml LTP-8X(config)# profile dba dba-00 LTP-8X(config-dba)("dba-00")# sla class cbr
Step 2. Specify a type of status reports for ONT queues by using the sla status-reporting command.
Блок кода language xml LTP-8X(config-dba)("dba-00")# sla status-reporting nsr
Step 3. Set fixed bandwidth parameters by using the bandwidth fixed command. Set other bandwidth parameters to 0.
Примечание The bandwidth has a throughput in Kbps (1000 bps), which is rounded down to 64 Kbps.
Блок кода language xml LTP-8X(config-dba)("dba-00")# bandwidth fixed 100000 LTP-8X(config-dba)("dba-00")# bandwidth guaranteed 0 LTP-8X(config-dba)("dba-00")# bandwidth besteffort 0
Step 4. Check the set parameters.
Блок кода language xml LTP-8X(config-dba)("dba-00")# do show profile dba dba-00 Name: 'dba-00' Description: 'ONT Profile DBA 0' Dba: Sla data: Service class: cbr Status reporting: nsr Alloc size: 0 Alloc period: 0 Fixed bandwidth: 100000 Guaranteed bandwidth: 0 Besteffort bandwidth: 0 T-CONT allocation scheme: share T-CONT with same profile
Step 5. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config-dba)("dba-00")# do commit
Scroll Pagebreak
T-CONT type 2 configuration
Consider configuration of a 100 Mbps guaranteed bandwidth.
Step 1. Specify a T-CONT type by using the sla class command.
Блок кода language xml LTP-8X(config)# profile dba dba-00 LTP-8X(config-dba)("dba-00")# sla class voip
Step 2. Specify a type of status reports for ONT queues by using the sla status-reporting command.
Блок кода language xml LTP-8X(config-dba)("dba-00")# sla status-reporting nsr
Step 3. Set guaranteed bandwidth parameters by using the bandwidth guaranteed command.
Set other bandwidth parameters to 0.
Примечание The bandwidth has a throughput in Kbps (1000 bps), which is rounded down to 64 Kbps.
Блок кода language xml LTP-8X(config-dba)("dba-00")# bandwidth guaranteed 100000 LTP-8X(config-dba)("dba-00")# bandwidth fixed 0 LTP-8X(config-dba)("dba-00")# bandwidth besteffort 0
Step 4. Check the set parameters.
Блок кода language xml LTP-8X(config-dba)("dba-00")# do show profile dba dba-00 Name: 'dba-00' Description: 'ONT Profile DBA 0' Dba: Sla data: Service class: voip Status reporting: nsr Alloc size: 0 Alloc period: 0 Fixed bandwidth: 100000 Guaranteed bandwidth: 0 Besteffort bandwidth: 0 T-CONT allocation scheme: share T-CONT with same profile
Step 5. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config-dba)("dba-00")# do commit
Scroll Pagebreak
T-CONT type 3 configuration
Consider configuration of a 100 Mbps guaranteed bandwidth with a possibility of allocation of a 200 Mbps best-effort bandwidth.
Step 1. Specify a T-CONT type by using the sla class command.
Блок кода language xml LTP-8X(config)# profile dba dba-00 LTP-8X(config-dba)("dba-00")# sla class type5
Step 2. Specify a type of status reports for ONT queues by using the sla status-reporting command.
Блок кода language xml LTP-8X(config-dba)("dba-00")# sla status-reporting nsr
Step 3. Set guaranteed bandwidth parameters by using the bandwidth guaranteed command.
Set best-effort bandwidth parameters by using the bandwidth besteffort command. Set other bandwidth parameters to 0.
Примечание The bandwidth has a throughput in Kbps (1000 bps), which is rounded down to 64 Kbps.
Блок кода language xml LTP-8X(config-dba)("dba-00")# bandwidth fixed 0 LTP-8X(config-dba)("dba-00")# bandwidth guaranteed 100000 LTP-8X(config-dba)("dba-00")# bandwidth besteffort 200000
Step 4. Check the set parameters.
Блок кода language xml LTP-8X(config-dba)("dba-00")# do show profile dba dba-00 Name: 'dba-00' Description: 'ONT Profile DBA 0' Dba: Sla data: Service class: type5 Status reporting: nsr Alloc size: 0 Alloc period: 0 Fixed bandwidth: 100000 Guaranteed bandwidth: 0 Besteffort bandwidth: 200000 T-CONT allocation scheme: share T-CONT with same profile
Step 5. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config-dba)("dba-00")# do commit
Scroll Pagebreak
T-CONT type 4 configuration
Consider configuration of a 200 Mbps best-effort bandwidth without allocation of a guaranteed bandwidth.
Step 1. Specify a T-CONT type by using the sla class command.
Блок кода language xml LTP-8X(config)# profile dba dba-00 LTP-8X(config-dba)("dba-00")# sla class type5
Step 2. Specify a type of status reports for ONT queues by using the sla status-reporting command.
Блок кода language xml LTP-8X(config-dba)("dba-00")# sla status-reporting nsr
Step 3. Set best-effort bandwidth parameters by using the bandwidth besteffort command.
Set other bandwidth parameters to 0.
Примечание The bandwidth has a throughput in Kbps (1000 bps), which is rounded down to 64 Kbps.
Блок кода language xml LTP-8X(config-dba)("dba-00")# bandwidth fixed 0 LTP-8X(config-dba)("dba-00")# bandwidth guaranteed 0 LTP-8X(config-dba)("dba-00")# bandwidth besteffort 200000
Step 4. Check the set parameters.
Блок кода language xml LTP-8X(config-dba)("dba-00")# do show profile dba dba-00 Name: 'dba-00' Description: 'ONT Profile DBA 0' Dba: Sla data: Service class: type5 Status reporting: nsr Alloc size: 0 Alloc period: 0 Fixed bandwidth: 0 Guaranteed bandwidth: 0 Besteffort bandwidth: 200000 T-CONT allocation scheme: share T-CONT with same profile
Step 5. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config-dba)("dba-00")# do commit
Scroll Pagebreak
T-CONT type 5 configuration
Consider configuration of a 100 Mbps fixed bandwidth and a 200 Mbps guaranteed bandwidth with a possibility of allocation of a 1244 Mbps best-effort bandwidth.
...
Scroll Pagebreak |
---|
Якорь | ||||
---|---|---|---|---|
|
Shaping configuration
This chapter describes how to configure Shaping profile for an ONT.
...
Upstream restriction in ONT uses the upstream shaping algorithm. It is possible to use either a single policer for all services simultaneously or different policers for each service separately.
Shaping parameters configuration
Downstream policer configuration
You need to configure a bandwidth limit of 100 Mbps for all services.
...
Step 1. Enable one-policer.
Блок кода language xml LTP-8X(config)# profile shaping shaping-00 LTP-8X(config-shaping)("shaping-00")# downstream one-policer
Step 2. Enable policer for necessary services.
Блок кода language xml LTP-8X(config-shaping)("shaping-00")# downstream policer 0 enable LTP-8X(config-shaping)("shaping-00")# downstream policer 1 enable LTP-8X(config-shaping)("shaping-00")# downstream policer 2 enable LTP-8X(config-shaping)("shaping-00")# downstream policer 3 enable
Step 3. Specify parameters of a fixed band for service 0.
Блок кода language xml LTP-8X(config-shaping)("shaping-00")# downstream policer 0 peak-rate 100000
Примечание For disabling limiting of bandwidth for all services and enable limiting separately, disable downstream one-police and set downstream policer peak-rate for required services.
Scroll Pagebreak |
---|
Shaping allows limiting all types of traffic for services by bandwidth or set different values of bandwidth for each type separately.
...
Step 1. Enable shaping for required services and set commited-rate and peak-rate values for global limiting.
Блок кода language xml LTP-8X(config-shaping)("shaping-00")# upstream 0 enable LTP-8X(config-shaping)("shaping-00")# upstream 0 commited-rate 100000 LTP-8X(config-shaping)("shaping-00")# upstream 0 peak-rate 110000
If you stop configuring on this step, all the traffic of service 0 will be limited by the commited-rate value.
Step 2. Enable shaping for different traffic types.
Блок кода language xml LTP-8X(config-shaping)("shaping-00")# upstream multicast 0 enable LTP-8X(config-shaping)("shaping-00")# upstream broadcast 0 enable LTP-8X(config-shaping)("shaping-00")# upstream unicast 0 enable
Step 3. Specify parameters of fixed bandwidth for each traffic type for service 0.
Блок кода language xml LTP-8X(config-shaping)("shaping-00")# upstream multicast 0 commited-rate 500 LTP-8X(config-shaping)("shaping-00")# upstream multicast 0 peak-rate 600 LTP-8X(config-shaping)("shaping-00")# upstream broadcast 0 commited-rate 500 LTP-8X(config-shaping)("shaping-00")# upstream broadcast 0 peak-rate 600 LTP-8X(config-shaping)("shaping-00")# upstream unicast 0 commited-rate 100000 LTP-8X(config-shaping)("shaping-00")# upstream unicast 0 peak-rate 100000
Примечание The bandwidth has a throughput in Kbps (1000 bps), which is rounded down to 64 Kbps.
For NTU-1, the algorithm of bandwidth limiting in upstream is different:
- traffic types are independent: if the limit of unicast traffic is set, multicast and broadcast traffic will be limited by the global value;
- in case the global value is specified as well as values for different traffic types, the limit for different traffic types will be implemented first, then limiting by the global value;
- the traffic for all services is limited by the value set for service 0.
Similarly, you can configure the bandwidth for other services.
Scroll Pagebreak
Configuration of Storm-control in the upsteram direction
To protect against «storms» arising in the pon part of the OLT, you can use the advanced functionality of the shaping profile.
...
The time is specified in minutes.
Scroll Pagebreak |
---|
RG ONT
This chapter considers issues related to configuration of Residential Gateway (RG) ONTs. The chapter introduces the notion of Bridged and Routed services.
...
Figure above shows two services (each with a corresponding GEM port on the ONT side), with one of them being routed and using both the OMCI and RG management domains and the other one being bridged and using only OMCI for configuration. Terminal configuration includes configuration of bridge interfaces (green areas in the figure) and distribution of LAN ports between the management domains.
The bridge parameter of the cross-connect profile is responsible for association of a service with a management domain. Being set, the bridge parameter creates a bridged service (the bridge group parameter is the bridge number in this case). When no bridge is set, a routed service is created (there is only one bridge associated with RG; it has a special bridge number—0).
Mixed configuration
Consider an example of ONT configuration, which simultaneously uses both management domains. Port numbers and the internal structure are shown in Figure 42.
Step 1. Create a VLAN for services on the switch. VLAN configuration is described in detail in VLAN configuration.
Блок кода language xml LTP-8X(switch)(config)# vlan 20 LTP-8X(switch)(config-vlan)# tagged front-port 0 LTP-8X(switch)(config-vlan)# tagged pon-port 0 – 1 LTP-8X(switch)(config-vlan)# exit LTP-8X(switch)(config)# vlan 30 LTP-8X(switch)(config-vlan)# tagged front-port 0 LTP-8X(switch)(config-vlan)# tagged pon-port 0 – 1
Step 2. Specify 3 as a service model value corresponding to the «VLAN for Service» model by using the gpon olt model command.
Блок кода language xml LTP-8X# configure terminal LTP-8X(config)# gpon olt model 3
Scroll Pagebreak Step 3. Define cross-connect profiles for services.
Блок кода language xml LTP-8X(config)# profile cross-connect RG-service LTP-8X(config-cross-connect)("RG-service")# exit LTP-8X(config)# profile cross-connect OMCI-service
Step 4. Define a dba profile. DBA parameters are not important for the purposes of this chapter. Thus, we will not configure these parameters, just use the default values. We will also assign one profile to both services that means that upstream services will operate with one T-CONT. DBA configuration is described in detail in DBA configuration.
Блок кода language xml LTP-8X(config)# profile dba basic LTP-8X(config-dba)("basic")# exit
Step 5. Create ports profile.
Блок кода language xml LTP-8X(config)# profile ports 2RG-2OMCI LTP-8X(config-ports)("2RG-2OMCI")# exit
Step 6. Configure a routed service. Use one VLAN 20 on both the OLT and ONT sides. Specify a routed service by using the no bridge command. Configure a cross-connect profile for the routed service.
Блок кода language xml LTP-8X(config)# profile cross-connect RG-service LTP-8X(config-cross-connect)("RG-service")# no bridge LTP-8X(config-cross-connect)("RG-service")# type general LTP-8X(config-cross-connect)("RG-service")# tag-mode single-tagged LTP-8X(config-cross-connect)("RG-service")# outer vid 20 LTP-8X(config-cross-connect)("RG-service")# outer cos unused LTP-8X(config-cross-connect)("RG-service")# user vid untagged LTP-8X(config-cross-connect)("RG-service")# mac-table-limit unlimited LTP-8X(config-cross-connect)("RG-service")# priority 0
Step 7. Configure a bridged service. Use one VLAN 30 on both the OLT and ONT sides. Specify a bridged service by using the bridge command. Set 1 as the OMCI bridge number. Configure a cross-connect profile for the bridged service.
Блок кода language xml LTP-8X(config)# profile cross-connect OMCI-service LTP-8X(config-cross-connect)("OMCI-service")# bridge LTP-8X(config-cross-connect)("OMCI-service")# bridge group 1 LTP-8X(config-cross-connect)("OMCI-service")# type general LTP-8X(config-cross-connect)("OMCI-service")# tag-mode single-tagged LTP-8X(config-cross-connect)("OMCI-service")# outer vid 30 LTP-8X(config-cross-connect)("OMCI-service")# outer cos unused LTP-8X(config-cross-connect)("OMCI-service")# user vid untagged LTP-8X(config-cross-connect)("OMCI-service")# mac-table-limit unlimited LTP-8X(config-cross-connect)("OMCI-service")# priority 1
You specified different priority queue values for the services. The routed service will have a higher priority than the bridged service as they work with one T-CONT.
Scroll Pagebreak Step 8. Configure a ports profile. According to Figure 41, we need to associate the first two LAN ports with the RG management domain, while the other two should be associated with the OMCI domain and bound to bridge 1.
Блок кода language xml LTP-8X(config)# profile ports 2RG-2OMCI LTP-8X(config-ports)("2RG-2OMCI")# port 0 bridge group 0 LTP-8X(config-ports)("2RG-2OMCI")# port 1 bridge group 0 LTP-8X(config-ports)("2RG-2OMCI")# port 2 bridge group 1 LTP-8X(config-ports)("2RG-2OMCI")# port 3 bridge group 1
Step 9. Set the ONT configuration. ONT management is described in detail in Service Models.
Блок кода language xml LTP-8X(config)# interface ont 0/0
Step 10. Assign the created profiles. Assign the cross-connect RG-service profile to service 0 and the cross-connect OMCI-service profile to service 1.
Блок кода language xml LTP-8X(config)# serial ELTX10203040 LTP-8X(config)(if-ont-0/0)# service 0 profile cross-connect RG-service LTP-8X(config)(if-ont-0/0)# service 0 profile dba basic LTP-8X(config)(if-ont-0/0)# service 1 profile cross-connect OMCI-service LTP-8X(config)(if-ont-0/0)# service 1 profile dba basic LTP-8X(config)(if-ont-0/0)# profile ports 2RG-2OMCI
Step 11. Use the show interface ont <id> configuration command to check the created configuration.
Блок кода language xml LTP-8X(config)(if-ont-0/0-1)# do show interface ont 0/0-1 configuration ----------------------------------- [ONT0/0] configuration ----------------------------------- Description: '' Enabled: true Serial: ELTX10203040 ... Service [0]: Profile cross connect: RG-service ONT Profile Cross Connect 1 Profile dba: basic ONT Profile DBA 2 Custom cross connect: disabled Service [1]: Profile cross connect: RG-service ONT Profile Cross Connect 0 Profile dba: basic ONT Profile DBA 2 Custom cross connect: disabled Service [2]: Profile cross connect: SecurityiAlarm ONT Profile Cross Connect 0 Profile dba: OtherServices ONT Profile DBA 4 Custom cross connect: disabled Profile ports: 2RG-2OMCI ONT Profile Ports 1
Scroll Pagebreak Step 12. Apply changes by the commit command.
Блок кода language xml LTP-8X(config)(if-ont-0/0)# do commit
As a result, you will have the mixed configuration of the ONT. One of the services is managed completely by the OMCI domain (the bridged service), LAN2 and LAN3 ports on the ONT are connected as bridges. The second service is managed by both OMCI and RG (the routed service; the RG domain can be configured, for instance, through the WEB interface on the ONT). LAN0 and LAN1 ports are connected to RG ONT.
High Speed Internet configuration
Configuration of High Speed Internet (HSI) does not have any peculiarities and can be easily performed as described in Service Models.
Correct operation of IPv6 requires to do the following:
...
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# profile cross-connect ipv6_br LTP-8X(config-cross-connect)("ipv6_br")# bridge LTP-8X(config-cross-connect)("ipv6_br")# bridge group 10 LTP-8X(config-cross-connect)("ipv6_br")# outer vid 300 LTP-8X(config-cross-connect)("ipv6_br")# user vid 300 LTP-8X(config-cross-connect)("ipv6_br")# type multicast LTP-8X(config-cross-connect)("ipv6_br")# exit LTP-8X(config)# profile ports ipv6_br LTP-8X(config-ports)("ipv6_br")# port 0 multicast LTP-8X(config-ports)("ipv6_br")# port 0 bridge group 10 LTP-8X(config-ports)("ipv6_br")# exit LTP-8X(config)# exit LTP-8X# commit |
Scroll Pagebreak |
---|
Multicast configuration
The chapter describes peculiarities of IPTV service configuration.
...
As you can see from the Figure 44, LTP-8X with enabled IGMP snooping translates multicast traffic only to the hosts, which are members of the IGMP group.
IGMP proxy is an IGMP client and group router at the same time (IGMP router). On the one hand, proxy requests an upstream router for group channels; on the other hand, it receives join/leave requests from hosts and replicates upstream traffic to the corresponding interfaces.
Model 1 Multicast configuration
Consider configuration of a multicast service for Model 1.
An STB, which works in VLAN 14, is connected to an ONT port in this example. Upstream IGMP packets arrive to VLAN 14 though a GEM port and the OLT changes VLAN 14 to subscriber's VLAN 200.
As we have a multicast server in VLAN 98 in our example, we need to configure a proxy on the switch to translate IGMP packets from VLAN 200 to VLAN 98 (for more information, see VLAN configuration). The multicast service comes downstream to the ONT port in VLAN 98 and changes to VLAN 14.
For more information on general configuration principles of data communication channels, see Service Models.
Figure 45 — Model 1 Multicast
...
Step 1. Specify the ONT serial number in the configuration.
Блок кода language xml LTP-8X# configure terminal LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# serial ELTX01234567 LTP-8X(config)(if-ont-0/0)# exit
Step 2. Assign a service model.
Блок кода language xml LTP-8X(config)# gpon olt model 1
Step 3. Create an UsIGMP cross-connect profile to configure the service, which will be used to send IGMP requests upstream. Configure a bridged service and specify the bridge group (it equals 1 in our example) the ONT port will be associated with; specify U-VLAN 14.
Блок кода language xml LTP-8X(config)# profile cross-connect UsIGMP LTP-8X(config-cross-connect)("UsIGMP")# bridge LTP-8X(config-cross-connect)("UsIGMP")# bridge group 1 LTP-8X(config-cross-connect)("UsIGMP")# user vid 14 LTP-8X(config-cross-connect)("UsIGMP")# do show profile cross-connect UsIGMP Name: 'UsIGMP' Description: 'ONT Profile Cross Connect 1' Model: ont Bridge group: 1 Tag mode: single-tagged Outer vid: 1 Outer cos: unused Inner vid: - U vid: 14 U cos: unused Mac table entry limit: unlimited Type: general IP host index: 0 Priority queue: 0
Step 4. Associate the bridge group with an ONT port. To do this, create a ports profile and assign value 1 to the bridge group parameter for the LAN1 port.
Блок кода language xml LTP-8X(config)# profile ports Ports1 LTP-8X(config-ports)("Ports1")# port 1 bridge group 1
Step 5. Enable multicasting and configure VLAN replacement rules for the ONT port.
Блок кода language xml LTP-8X(config-ports)("Ports1")# port 1 multicast LTP-8X(config-ports)("Ports1")# port 1 igmp downstream vid 14 LTP-8X(config-ports)("Ports1")# port 1 igmp downstream tag-control replace-vid LTP-8X(config-ports)("Ports1")# port 1 igmp upstream vid 14 LTP-8X(config-ports)("Ports1")# port 1 igmp upstream tag-control replace-vid
Scroll Pagebreak Step 6. You also need to configure VLAN 98 multicasting and specify the group range.
Блок кода language xml LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 vid 98 LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 group 224.0.0.0 239.255.255.255 LTP-8X(config-ports)("Ports1")# do show profile ports Ports1 Name: 'Ports1' Description: 'ONT Profile Ports 7' Multicast IP version: IPv4 Igmp settings: Version: IGMP v3 Mode: snooping Immediate leave: false Robustness: 2 Querier ip: 0.0.0.0 Query interval: 125 Query response interval: 100 Last member query interval: 10 Mld settings: Version: MLD v2 Mode: snooping Immediate leave: false Robustness: 2 Querier ipv6: :: Query interval: 125 Query response interval: 100 Last member query interval: 10 ... Port [1]: Speed: auto Duplex: auto Bridge group: 1 Spanning tree for bridge group: false Multicast enable: true Multicast port settings: Upstream igmp vid: 14 Upstream igmp prio: 0 Upstream igmp tag control: replace vid Downstream multicast vid: 14 Downstream multicast prio: 0 Downstream multicast tag control: replace vid Max groups: 0 Max multicast bandwidth: 0 Shaper downstream: Enable: false Commited rate: 1000000 Shaper upstream: Enable: false Commited rate: 1000000 ...
Scroll Pagebreak Step 7. Assign the created profiles in the ONT. Configure a custom cross-connect profile, specify S-VLAN 200, and apply the configuration.
Блок кода language xml LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# service 0 profile cross-connect UsIGMP LTP-8X(config)(if-ont-0/0)# profile ports Ports1 LTP-8X(config)(if-ont-0/0)# service 0 custom svid 200 LTP-8X(config)(if-ont-0/0)# do commit
Step 8. Add VLAN 98 and VLAN 200 in the switch view. Enable IGMP snooping.
Блок кода language xml LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# vlan 200 LTP-8X(switch)(config-vlan)# tagged front-port 0 LTP-8X(switch)(config-vlan)# tagged pon-port 0 – 7 LTP-8X(switch)(config-vlan)# ip igmp snooping enable LTP-8X(switch)(config-vlan)# exit LTP-8X(switch)(config)# vlan 98 LTP-8X(switch)(config-vlan)# tagged front-port 0 LTP-8X(switch)(config-vlan)# tagged pon-port 0 – 7 LTP-8X(switch)(config-vlan)# ip igmp snooping enable LTP-8X(switch)(config-vlan)# exit
Step 9. Configure IGMP proxy for IGMP packets transmission from VLAN 200 to VLAN 98. Apply the configuration.
Блок кода language xml LTP-8X(switch)(config)# ip igmp proxy report enable LTP-8X(switch)(config)# ip igmp proxy report range 224.0.0.0 239.255.255.255 from 200 to 98 LTP-8X(switch)(config)# ip igmp snooping LTP-8X(switch)(config)# commit
Model 3 Multicast configuration
Consider configuration of a multicast service for Model 3.
The multicast service operates in VLAN 98 in the example below, an STB operating in VLAN 14 is connected to an ONT port. Upstream IGMP packets come to VLAN 14 in the ONT, where VLAN 14 is replaced with the service VLAN 98, and then the data is further transferred upstream through the GEM port. The multicast service comes downstream to the ONT port in VLAN 98 and changes to VLAN 14. For more information on general configuration principles of data communication channels, see Service Models.
Figure 46 — Model 3 Multicast
Step 1. Specify the ONT serial number in the configuration.
Блок кода language xml LTP-8X# configure terminal LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# serial ELTX01234567 LTP-8X(config)(if-ont-0/0)# exit
Step 2. Assign a service model.
Блок кода language xml LTP-8X(config)# gpon olt model 3
Step 3. Create an UsIGMP cross-connect profile to transfer IGMP requests upstream. Configure a bridged service and specify the bridged group (it equals 1 in the example below) the ONT port will be associated with. Specify U-VLAN 14 and S-VLAN 98.
Блок кода language xml LTP-8X(config)# profile cross-connect UsIGMP LTP-8X(config-cross-connect)("UsIGMP")# bridge LTP-8X(config-cross-connect)("UsIGMP")# bridge group 1 LTP-8X(config-cross-connect)("UsIGMP")# outer vid 98 LTP-8X(config-cross-connect)("UsIGMP")# user vid 14 LTP-8X(config-cross-connect)("UsIGMP")# do show profile cross-connect UsIGMP Name: 'UsIGMP' Description: 'ONT Profile Cross Connect 1' Model: ont Bridge group: 1 Tag mode: single-tagged Outer vid: 98 Outer cos: unused Inner vid: - U vid: 14 U cos: unused Mac table entry limit: unlimited Type: general IP host index: 0 Priority queue: 0
Scroll Pagebreak Step 4. Associate the bridge group with an ONT port. To do this, create a ports profile and assign value 1 to the bridge group parameter for the LAN1 port.
Блок кода language xml LTP-8X(config)# profile ports Ports1 LTP-8X(config-ports)("Ports1")# port 1 bridge group 1
Step 5. Enable multicasting and configure VLAN replacement rules for the ONT port.
Блок кода language xml LTP-8X(config-ports)("Ports1")# port 1 multicast LTP-8X(config-ports)("Ports1")# port 1 igmp downstream vid 14 LTP-8X(config-ports)("Ports1")# port 1 igmp downstream tag-control replace-vid LTP-8X(config-ports)("Ports1")# port 1 igmp upstream vid 98 LTP-8X(config-ports)("Ports1")# port 1 igmp upstream tag-control replace-vid
Step 6. You also need to configure VLAN 98 multicasting and specify the group range.
Блок кода language xml LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 vid 98 LTP-8X(config-ports)("Ports1")# igmp multicast dynamic-entry 0 group 224.0.0.0 239.255.255.255 LTP-8X(config-ports)("Ports1")# do show profile ports Ports1 ... Igmp settings: ... Multicast dynamic entry [0]: Vlan id: 98 First group ip: 224.0.0.1 Last group ip: 239.255.255.255 ... Port [1]: Speed: auto Duplex: auto Bridge group: 0 Spanning tree for bridge group: false Multicast enable: false Multicast port settings: Upstream igmp vid: 98 Upstream igmp prio: 0 Upstream igmp tag control: replace-vid Downstream multicast vid: 14 Downstream multicast prio: 0 Downstream multicast tag control: replace-vid Max groups: 0 Max multicast bandwidth: 0 Shaper downstream: Enable: false Commited rate: 1000000 Shaper upstream: Enable: false Commited rate: 1000000 ...
Scroll Pagebreak Step 7. Assign the created profiles in the ONT and apply the configuration.
Блок кода language xml LTP-8X(config)# interface ont 0/0 LTP-8X(config)(if-ont-0/0)# service 0 profile cross-connect UsIGMP LTP-8X(config)(if-ont-0/0)# profile ports Ports1 LTP-8X(config)(if-ont-0/0)# do commit
Step 8. Add VLAN 98 in the switch view and enable IGMP snooping.
Блок кода language xml LTP-8X# switch LTP-8X(switch)# configure terminal LTP-8X(switch)(config)# vlan 98 LTP-8X(switch)(config-vlan)# tagged front-port 0 LTP-8X(switch)(config-vlan)# tagged pon-port 0 – 7 LTP-8X(switch)(config-vlan)# ip igmp snooping enable LTP-8X(switch)(config-vlan)# exit LTP-8X(switch)(config)# ip igmp snooping LTP-8X(switch)(config)# commit
IPv6 Multicast configuration
IPv6 multicast is configured the same way as shown above. However, there are some differences in configuration.
...
Scroll Pagebreak Якорь Настройка VoIP Настройка VoIP
VoIP configuration
The chapter describes peculiarities of VoIP service configuration. The terminal supports several methods of VoIP configuration:
...
A method is chosen based on service model and ONT functionality.
VoIP Configuration in OMCI management domain
VoIP is a special bridged service. It has all general properties of a bridged service. Operator's actions required for services configuration are described in detail in ONT configuration.
As opposed to other bridge services, VoIP requires the iphost type in the cross-connect profile to terminate traffic in internal virtual IP interface. That also requires the Iphost eid parameter to be specified. As a rule, it should equal 1. Contact your ONT vendor for information about the Iphost eid value for the VoIP.
Step 1. Configure a cross-connect profile to be used as VoIP.
Блок кода language xml LTP-8X(config)# profile cross-connect VoIP LTP-8X(config-cross-connect)("VoIP")# bridge LTP-8X(config-cross-connect)("VoIP")# type iphost LTP-8X(config-cross-connect)("VoIP")# bridge group 2 LTP-8X(config-cross-connect)("VoIP")# iphost eid 1
Step 2. Check the changes made.
Блок кода language xml LTP-8X(config-cross-connect)("VoIP")# do show profile cross-connect VoIP ... Type: iphost IP host index: 1 Priority queue: 0
Step 3. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config-cross-connect)("VoIP")# do commit
VoIP configuration in RG management domain
In case the VoIP client is located after the U point (i. e. in the RG management domain), the VoIP service has the same configuration procedure as all other routed services. The procedure is described in detail in ONT configuration. All the general steps of service configuration are applied to VoIP as well. Scroll Pagebreak
Configuration of management via TR-069
This chapter describes configuration of a data communication channel for the CPE management service via the TR-069 protocol.
...
ONT management via TR-069 is a special service. All general steps of service configuration apply to TR-069 management. Operator's actions required for services configuration are described in detail in ONT configuration.
As opposed to other services, the management service requires the management type in the cross-connect profile. You also need to specify the Iphost eid parameter. As a rule, it should equal 0.
Configuration of a TR-069 Inband management
This mode is characterised by its simple implementation. Management traffic goes through the same bridge as user traffic. Figure below shows a part of the OMCI layout. Arrows show the traffic flow.
...
Step 1. Set the management type in the cross-connect profile.
Блок кода language xml LTP-8X(config)# profile cross-connect TR069 LTP-8X(config-cross-connect)("TR069")# type management
Step 2. Set the ont-rg model in the cross-connect profile.
Блок кода language xml LTP-8X(config-cross-connect)("TR069")# no bridge
Step 3. Set the IP Host identifier to 0.
Блок кода language xml LTP-8X(config-cross-connect)("TR069")# iphost eid 0
Step 4. Check the changes made with the show profile cross-connect command.
Блок кода language xml LTP-8X(config-cross-connect)("TR069")# do show profile cross-connect TR069 Name: 'TR069' Description: 'ONT Profile Cross Connect 1' Model: ont-rg Bridge group: - Tag mode: single-tagged Outer vid: 1 Outer cos: unused Inner vid: - U vid: untagged U cos: unused Mac table entry limit: unlimited Type: management IP host index: 0
Step 5. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config-cross-connect)("TR069")# do commit
Scroll Pagebreak
Configuration of a TR-069 OOB management channel
Not all ONT vendors support creation of Inband management channels via TR-069. To solve this, a capability to create an OutOfBand management channel was developed as an alternative. The main peculiarity of the mode is the use of a separate bridge for management. See a part of the OMCI layout below. Arrows show the traffic flow.
...
Step 1. Set the management type in the cross-connect profile.
Блок кода language xml LTP-8X(config)# profile cross-connect TR069 LTP-8X(config-cross-connect)("TR069")# type management
Step 2. Set the ont model in the cross-connect profile. Specify a separate bridge-group.
Блок кода language xml LTP-8X(config-cross-connect)("TR069")# bridge LTP-8X(config-cross-connect)("TR069")# bridge group 20
Step 3. Set the IP Host identifier to 0.
Блок кода language xml LTP-8X(config-cross-connect)("TR069")# iphost eid 0
Scroll Pagebreak Step 4. Check the changes by using the show profile cross-connect command.
Блок кода language xml LTP-8X(config-cross-connect)("TR069")# do show profile cross-connect TR069 Name: ’TR069’ Description: ’ONT Profile Cross Connect 1’ Model: ont Bridge group: 20 Tag mode: single-tagged Outer vid: 1 Outer cos: unused Inner vid: - U vid: untagged U cos: unused Mac table entry limit: unlimited Type: management Iphost eid: 0 Priority queue: 0 LTP-8X(pon/profiles-ont/cross-connect-6)
Step 5. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config-cross-connect)("TR069")# do commit
TR-069 client parameters configuration
To configure TR-069 client parameters, use the management profile.
...
Step 1. Enable TR-069 configuration.
Блок кода language xml LTP-8X(config)# profile management management-00 LTP-8X(config-management)("management-00")# omci-configuration
Step 2. Specify the connection parameters.
Блок кода language xml LTP-8X(config-management)("management-00")# url http://acs.tele.com:9595/acs LTP-8X(config-management)("management-00")# username acs LTP-8X(config-management)("management-00")# password acsacs
Scroll Pagebreak Step 3. Check the changes made.
Блок кода language xml LTP-8X(config-management)("management-00")# do show profile management management-00 Name: 'management-00' Description: 'ONT Profile Management 0' Enable omci configuration: true Url: 'http://acs.tele.com:9595/acs' Username: 'acs' Password: 'acsacs'
Step 4. Apply the changes by using the commit command.
Блок кода language xml LTP-8X(config-management)("management-00")# do commit
ONT configuration templates
It is not always convenient, especially for large-scale operators, to build ONT configuration from separate profiles for each subscriber. This process is painstaking and risky in a certain sense, as it is highly prone to operator error.
...
The essence of configuration templates is simple. Network administrator prepares required quantity of templates for the quantity of service plans. Configuration template contains detailed profile list and a set of ONT parameters. Subscriber service specialist or OSS/BSS system assigns the template to an ONT and identifies additional configuration parameters if necessary. As a rule, configuration assignment is performed in "one click" or by using one command.
Preparing ONT configuration template
Step 1. Define an ONT configuration template.
Блок кода language xml LTP-8X(config)# template HSI-100-CaTV LTP-8X(ont-template)("HSI-100-CaTV")#
Step 2. Set the ONT configuration. Template configuration does not have any peculiarities and exactly follows the ONT configuration process described in ONT configuration.
Блок кода language xml LTP-8X(ont-template)("HSI-100-CaTV")# service 0 profile dba AllServices LTP-8X(ont-template)("HSI-100-CaTV")# service 0 profile cross-connect Service1 LTP-8X(ont-template)("HSI-100-CaTV")# service 1 profile dba AllServices LTP-8X(ont-template)("HSI-100-CaTV")# service 1 profile cross-connect Service2 LTP-8X(ont-template)("HSI-100-CaTV")# profile ports Ports1
Scroll Pagebreak Step 3. Disable all configuration parameters that should be specified explicitly for the ONT with the undefine command, if necessary.
Блок кода language xml LTP-8X(ont-template)("HSI-100-CaTV")# undefine rf-port-state
Step 4. Apply the changes.
Блок кода language xml LTP-8X(ont-template)("HSI-100-CaTV")# do commit
ONT configuration template assignment
Step 1. Switch to the ONT view. You can use a range of ONT IDs for group operations if necessary.
Блок кода language xml LTP-8X(config)# interface ont 0/0-10 LTP-8X(config)(if-ont-0/0-10)#
Step 2. Assign an ONT configuration template by using the template command.
Блок кода language xml LTP-8X(config)(if-ont-0/0-10)# template HSI-100-CaTV
Step 3. Define individual ONT parameters not specified in the template if necessary.
Блок кода language xml LTP-8X(config)(if-ont-0/0-10)# rf-port-state enabled
Step 4. Apply the changes.
Блок кода language xml LTP-8X(config)(if-ont-0/0-10)# do commit
Scroll Pagebreak |
---|
You can view the ONT configuration using the same command: show interface ont <id> configuration. You can distinguish the template parameters from the general ones by [T](Template) markers. In this example, Rf port state is the only general parameter.
...
Блок кода |
---|
[T] Omci error tolerant: false Service [0]: [T] Profile cross connect: Service1 NT Profile Cross Connect 1 [T] Profile dba: dba-00 ONT Profile DBA 0 Custom cross connect: disabled Service [1]: [T] Profile cross connect: Service2 NT Profile Cross Connect 2 [T] Profile dba: dba-00 ONT Profile DBA 0 Custom cross connect: disabled [T] Profile shaping: shaping-00 ONT Profile Shaping 0 [T] Profile ports: ports-00 ONT Profile Ports 0 [T] Profile management: unassigned Template: test ONT Template 1 |
Scroll Pagebreak |
---|
This chapter describes Ethernet ports management via OMCI.
...
All these attributes are transmitted via OMCI (ITU-T G.988 ME 11 "PPTP Ethernet UNI").
Ethernet ports management on ONT
Ethernet ports management on ONT means enabling/disabling the port and performed by [no] port <port number> shutdown command, where <port number> is the number of "0-3" port.
...
Блок кода |
---|
LTP-8X(config)(if-ont-0/0)# no port 0 shutdown LTP-8X(config)(if-ont-0/0)# do commit |
PoE management on ONT ports
PoE management on ONT ports is performed using port <port number> poe enable pseclass-control <class> power-priority <level> command, where
- <port number> –"0–3" port number,
- <class> – "0–5" power class,
- <level> – "critical/high/low" priority level.
Enabling PoE on ONT ports
To enable PoE on ONT ports, do the following:
Блок кода |
---|
LTP-8X(config)(if-ont-0/0)# port 0 poe enable LTP-8X(config)(if-ont-0/0)# do commit |
Power class control
This attribute can be used to set specific limits on the power class.
Valid values for this attribute:
...
Блок кода |
---|
LTP-8X(config)(if-ont-0/0)# port 0 poe pse-class-control 0 LTP-8X(config)(if-ont-0/0)# do commit |
PoE priority settings
This attribute controls port priority in terms of the power management algorithm. Priority set by this attribute can be used by control mechanism which prevents overcurrent situations by disabling ports with lower power priority.
...
Блок кода |
---|
LTP-8X(config)(if-ont-0/0)# port 0 poe power-priority low LTP-8X(config)(if-ont-0/0)# do commit |
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-8X# show version Eltex LTP-8X:rev.C software version 3.40.0 build ХХХХ on ХХ.ХХ.2020 ХХ:ХХ |
Terminal information preview
To view information about the terminal, use the show system environment command.
...
Parameter | Description |
---|---|
CPU load average | Average processor load |
Free RAM/Total RAM | Free/total RAM |
Temperature | Temperature from sensors 1 and 2 |
Reset button | The action depends on the reset button configuration |
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 |
PLD FW Version | PLD firmware version |
Power supply information | Information about installed power modules |
Information on terminal operation time
To view terminal operating time, use the show uptime command.
Блок кода | ||
---|---|---|
| ||
LTP-8X# show uptime up 7 days, 20:11 |
Scroll Pagebreak |
---|
To check network connection, use the ping command. As a parameter, pass the IP address of the node to be checked.
Блок кода | ||
---|---|---|
| ||
LTP-8X# ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254): 56 data bytes 64 bytes from 192.168.1.254: seq=0 ttl=64 time=0.422 ms 64 bytes from 192.168.1.254: seq=1 ttl=64 time=0.426 ms 64 bytes from 192.168.1.254: seq=2 ttl=64 time=0.360 ms 64 bytes from 192.168.1.254: seq=3 ttl=64 time=0.397 ms 64 bytes from 192.168.1.254: seq=4 ttl=64 time=0.404 ms --- 192.168.1.254 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 0.360/0.401/0.426 ms |
Terminal operation log
Use show log command to view log files.
...
Блок кода | ||
---|---|---|
| ||
LTP-8X# show log ltp.1.gz |
Scroll Pagebreak
Active alarms log
To view the active alarms log, use the show alarms command. Pass an event type as a parameter (see Table 14) and/or their severity (see Table 15). You can view all active alarms by using the show alarm active all command.
Блок кода | ||
---|---|---|
| ||
LTP-8X# show alarm active all Active alarms (1): ## Type Severity Description 0 Fan Critical FAN1 0 rpm LTP-8X# |
GPON monitoring
GPON OLT state
Step 1. To view the state of GPON OLT, use the show gpon olt state command.
Блок кода language xml LTP-8X# show gpon olt state Device count: 2 Gpon-ports per device: 4 Driver version: 1.2.119 Device 0: Firmware version: 2.3.37.1036 Hardware version: 5211.2 Device 1: Firmware version: 2.3.37.1036 Hardware version: 5211.2 LTP-8X#
...
Parameter | Description |
---|---|
Device count | The number of OLT chips |
Gpon-ports per device | The number of channels in one OLT chip |
Firmware version | OLT chip firmware version |
Hardware version | OLT chip hardware version |
Scroll Pagebreak |
---|
GPON interface state
Step 1. To view the state of GPON interfaces, use the show interface gpon-port <ID> state command.
Блок кода language xml LTP-8X# show interface gpon-port 0-3 state Reading: .... Gpon-ports status information: Gpon-port: 0 1 2 3 State: OK OK OK OK ONT count: 1 0 29 0 Force-mode: enabled disabled disabled disabled ONT autofind: enabled enabled enabled enabled SFP vendor: Ligent n/a Ligent n/a SFP product number: LTE3680M-BC n/a LTE3680M-BC n/a SFP vendor revision: 1.0 n/a 1.0 n/a SFP temperature [C]: 71 n/a 74 n/a SFP voltage [V]: 3.19 n/a 3.23 n/a SFP tx bias current [mA]: 17.61 n/a 21.16 n/a SFP tx power [dBm]: 3.54 n/a 3.75 n/a
Table 32 — GPON interface parameters
Parameter
Description
Gpon-port
Channel number
State
Channel state
ONT count
The number of ONTs in the channel
SFP vendor
SFP vendor
SFP product number
SFP model
SFP vendor revision
SFP revision
SFP temperature
SFP temperature in Celsius degrees
SFP voltage
SFP voltage in Volts
SFP tx bias current
Bias current in mA
SFP tx power
Transmission power in dBm
Table 33 — GPON interface statesScroll Pagebreak Value
Description
INITED
The channel is initialised
CFGINPROGRESS
The channel configuration is in progress
CFGFAILED
The channel configuration completed with error
OK
The channel is in operation
FAILED
The channel is out of operation
DISABLED
The channel is disabled
Step 2. To view the state of only one GPON interface, use the show interface gpon-port <ID> state command. That means you need to specify the interface number.
Блок кода language xml LTP-8X# show interface gpon-port 0 state Reading: . Gpon-port status information: Gpon-port: 0 State: OK ONT count: 1 Force-mode: enabled ONT autofind: enabled SFP vendor: Ligent SFP product number: LTE3680M-BC SFP vendor revision: 1.0 SFP temperature [C]: 71 SFP voltage [V]: 3.19 SFP tx bias current [mA]: 17.61 SFP tx power [dBm]: 3.54
MAC table preview
Step 1. To view the table of MAC addresses on the fourth port of the GPON interface, use the show mac interface gpon-port 4 command.
Блок кода language xml LTP-8X# show mac interface gpon-port 4 ## ONT Serial ONT ID GPON-port GEM UVID CVID SVID MAC 1 ELTX06000022 74 4 912 1214 A8:F9:4B:40:05:1B 2 ELTX06000060 86 4 1008 1214 A8:F9:4B:40:07:0B 3 ELTX06001B70 88 4 1024 1214 A8:F9:4B:41:1F:9B Total records: 3 of 3
Statistics for GPON interfaces
Step 1. To view statistics on GPON interfaces, use the show interface gpon-port <ID> counters command. ID means the GPON interface number. You can specify several interfaces at once.
Блок кода language xml LTP-8X# show interface gpon-port 0-3 counters ## Downstream counters for channels: 0 1 2 3 2 RX DS octets 128548 128548 128548 128548 3 RX DS packets 1867 1867 1867 1867 5 RX DS octets for channel 128548 18556 18556 18556 6 RX DS packets for channel 1867 202 202 202 8 TX DS octets 128548 18556 18556 18556 9 TX DS packets 1867 202 202 202 11 DS octets 28870 17596 17596 17596 12 DS packets 334 187 187 187 13 DS unicast packets 0 0 0 0 14 DS multicast packets 334 187 187 187 15 DS broadcast packets 0 0 0 0 16 DS packet dropped 1533 15 15 15 ## Upstream counters for channels: 0 1 2 3 2 TX US octets 0 0 0 0 3 TX US packets 0 0 0 0 5 US octets 0 0 0 0 6 US packets 0 0 0 0 7 US unicast packets 0 0 0 0 8 US multicast packets 0 0 0 0 9 US broadcast packets 0 0 0 0 10 US packed dropped 0 0 0 0 11 Packet dropped (CRC) 0 0 0 0 13 TX US octets reassembly 0 0 0 0 14 TX US packets reassembly 0 0 0 0
Scroll Pagebreak
Statistics for OLT Ethernet interfaces
Step 1. To view statistics on Ethernet interfaces of the OLT (connected to the terminal switch), use the show interface gpon-port <ID> counters v-interface command.
Блок кода language xml LTP-8X# show interface gpon-port 0 counters v-interface ## Downstream counters for channels: 0 1 RX Alignment errors 0 2 RX Pause frames 0 3 RX CRC-32 errors 0 4 RX Oversize errors 0 5 RX Bad FCS 0 6 RX Too long frames 0 7 RX Undersize errors 0 8 RX Range errors 0 9 RX Ok frames 3965150 10 RX total frames 3965150 11 RX 64 octets frames 314 12 RX 65-127 octets frames 3964297 13 RX 128-255 octets frames 59 14 RX 256-511 octets frames 480 15 RX 512-1023 octets frames 0 16 RX 1024-1518 octets frames 0 17 RX 1519-MAX octets frames 0 18 RX Total unicast packets 83 19 RX Total multicast packets 3679683 20 RX Total broadcast packets 285384 22 RX Total octets 269746879 24 RX Ok octets 269746879 25 RX FIFO overflow errors 0 26 RX Bad FCS and <64 octets 0 27 RX Frame errors 0 ## Upstream counters for channels: 0 1 TX frames without errors 0 2 TX valid pause frames 0 3 TX frames with errors 0 4 TX good unicast packets 0 5 TX good multicast packets 0 6 TX good broadcast packets 0 8 TX octets 0
Scroll Pagebreak
Multicast statistics
Step 1. To view statistics on MC streams, use the show interface gpon-port <ID> igmp groups command. As a parameter, pass the channel number or a range of channels.
Блок кода language xml LTP-8X# show interface gpon-port 0-7 igmp groups All IGMP groups (104): ## GPON-port Serial Multicast address Start Stop 1 4 ELTX66000074 239.1.128.43 2017.11.21 09:58:02 2017.11.21 11:25:21 2 4 ELTX67000050 239.1.128.43 2017.11.21 09:58:02 2017.11.21 11:25:21 3 4 ELTX6700007C 239.1.128.43 2017.11.21 09:58:02 ---
ONT monitoring
ONT configurations list
Step 1. To view active ONT configurations, use the show interface ont <ID> configured command. As an ID, pass the GPON port number or a range of numbers.
Блок кода language xml LTP-8X# show interface gpon-port ont 2 configured ----------------------------------- GPON-port 0 ONT configured list ----------------------------------- ## Serial ONT ID GPON-PORT Status RSSI[dBm] Version EquipmentID Description 1 454C54581A000021 0 2 OFFLINE n/a n/a n/a 2 444C4E4B8713F000 1 2 OFFLINE n/a n/a n/a 3 48575443904D6425 2 2 OFFLINE n/a n/a n/a 4 454C545806000024 3 2 OFFLINE n/a n/a n/a 5 454C54585D000048 4 2 OFFLINE n/a n/a n/a 6 454C54585F0009E8 10 2 OK -8.16 3.22.0.1669 NTU-2V Total ONT count: 6
Scroll Pagebreak
List of empty ONT configurations
Step 1. To view empty ONT configurations (vacant ONT IDs), use the show interface ont <ID> unconfigured command.
Блок кода language xml LTP-8X# show interface ont 0-7 unconfigured GPON-port 0 ONT unconfigured list: 3,5-49,51-127 GPON-port 1 ONT unconfigured list: 0-127 GPON-port 2 ONT unconfigured list: 5-9, 11-127 GPON-port 3 ONT unconfigured list: 0-127 GPON-port 4 ONT unconfigured list: 32-127 GPON-port 5 ONT unconfigured list: 0-127 GPON-port 6 ONT unconfigured list: 0,2-127 GPON-port 7 ONT unconfigured list: 3,22,35127 Total ONT count: 947
List of connected ONTs
Step 1. To view the list of online ONTs, use the following command: show interface ont <ID> online. As an argument, specify the GPON interface number or a range of numbers.
Блок кода language xml LTP-8X# show interface ont 0 online ----------------------------------- GPON-port 0 ONT online list ----------------------------------- ## Serial ONT ID GPON-PORT Status RSSI[dBm] Version EquipmentID 1 ELTX5C00008C 3 0 OK -23.19 3.50.2.1157 NTU-RG-1402G-W 2 ELTX1A00001A 2 0 OK -24.44 3.21.1.1928 NTP-RG-1402G-W:rev.C GPON-port 1 has no online ONTs GPON-port 2 has no online ONTs GPON-port 3 has no online ONTs
Блок кода language xml GPON-port 4 has no online ONTs GPON-port 5 has no online ONTs GPON-port 6 has no online ONTs GPON-port 7 has no online ONTs Total ONT count: 2
Table 34 — ONT status description
ONT status
Description
UNACTIVATED
ONT has no configurations
ALLOCATED
ONT detected
AUTHINPROGRESS
ONT authentication is in progress
AUTHFAILED
Authentication failed
AUTHOK
Authentication successfully completed
PRECONFIG
Preparing ONT for configuration
CFGINPROGRESS
ONT configuration is in progress
CFGFAILED
Configuration failed
OK
ONT is in operation
BLOCKED
ONT is blocked
MIBRESET
ONT MIB reset
FAILED
ONT has a critical failure
FWUPDATING
ONT firmware update is in progress
DISABLED
ONT is disabled (technically blocked)
Блок кода language xml ## Serial ONT ID GPON-PORT Status RSSI[dBm] Version EquipmentID 1 ELTX5C00008C 3 0 OK -23.19 3.50.2.1157 NTU-RG-1402G-W 2 ELTX1A00001A 2 0 OK -24.44 3.21.1.1928 NTP-RG-1402G-W:rev.C GPON-port 1 has no online ONTs GPON-port 2 has no online ONTs GPON-port 3 has no online ONTs
List of disconnected ONTs
Step 1. To view the list of offline ONTs, use the show interface ont <ID> offline command. As an argument, specify the GPON interface number or a range of numbers.
Блок кода language xml LTP-8X# show interface ont 0-7 offline ----------------------------------- GPON-port 0 ONT offline list ----------------------------------- ## Serial ONT ID GPON-port Description 1 454C54585C0908B4 0 0 GPON-port 1 has no offline ONTs GPON-port 2 has no offline ONTs
Блок кода language xml GPON-port 3 has no offline ONTs GPON-port 4 has no offline ONTs GPON-port 5 has no offline ONTs GPON-port 6 has no offline ONTs GPON-port 7 has no offline ONTs Total ONT count: 1
ONT statistics
To view ONT statistics, use the show interface ont <ID> counters <type> command. As an argument, pass the ONT ID and the type of requested statistics (see Table 35).
...
Statistics type |
---|
gem-port-performance-monitoring |
gem-port-nctp-performance-monitoring |
ethernet-performance-monitoring-history-data |
ethernet-performance-monitoring-history-data2 |
ethernet-performance-monitoring-history-data3 |
gal-ethernet-performance-monitoring-history-data |
fec-performance-monitoring-history-data |
ethernet-frame-extended-performance-monitoring |
multicast-subscriber-monitor |
ONT bit error rate
Bit error rate (BER) is the rate of errors in data transmission.
...
Блок кода | ||
---|---|---|
| ||
LTP-8X# show interface gpon-port 0 downstream-ber ----------------------------------- GPON-port 0 BER table ----------------------------------- ## Ch/ Id Errors Intervals BER Interval BER 1 0/ 2 0 0 100000 0 2 0/ 3 0 0 100000 0 |
Viewing the status of ONT ports
To view the status of the ONT ports, run the show interface ont <ID> ports command. Pass the ONT identifier as an argument.
...
Якорь | ||||
---|---|---|---|---|
|
System environment configuration
You can adjust fans and configure reset button of the device.
...
Блок кода | ||
---|---|---|
| ||
LTP-8X(config)# system reset-button disabled |
Terminal maintenance
Якорь Замена SFP-трансиверов Замена SFP-трансиверов
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.
...
Якорь | ||||
---|---|---|---|---|
|
Ventilation units replacement
The terminal design allows ventilation units replacement even when the terminal is on.
...
- Step 1. Connect the pins of the unit with the connector in the device (see Figure 54).
- Step 2. Lay the connection cable in a special tray on the inner side of the unit.
- Step 3. Insert the unit into the terminal case.
- Step 4. Screw the ventilation unit to the rear panel (see Figure 53).
OLT firmware update
This chapter describes the terminal firmware update procedure. To download a firmware file, use the TFTP server available in the terminal management network.
- Step 1. Copy the firmware file into the root folder (or any other known folder) of the TFTP server.
Step 2. Update the firmware by using the copy command.
Блок кода language xml LTP-8X# copy ftp://user:pass@10.54.16.1/ltp-8x-revc-revd-3.40.0-buildXXXX.fw.bin fs://firmware Downloading system firmware.. ............................................................ ............................................................ .................................................. Download successfully - speed: 3160145.000 bytes/sec during 5.027 seconds, total size 15885504 System firmware successfully downloaded Updating system firmware.. Current board version: 6 Current firmware version: 3.26.1.1349 New firmware version: 3.32.0.XXXX Update device mtd7 Erase flash... Done. Write data... Done. Done. Success Update device mtd5 Erase flash...Done. Write data... Done. Done. Success System firmware successfully updated
Step 3. Reboot the terminal to start the new firmware.
Блок кода language xml LTP-8X# reboot Do you really want to reboot the system now? (y/n) y
Scroll Pagebreak
ONT firmware update
This chapter describes different methods of ONT firmware update using the OMCI protocol.
ONT firmware update download
ONT firmware update can run automatically for all ONTs or for a specified ONT. To start the update, download a firmware update file to the line terminal. To download the file, use the copy command and specify the file name and the address of the TFTP server as arguments.
Блок кода | ||
---|---|---|
| ||
LTP-8X# copy ftp://user:pass@10.54.16.1/ntp-rg-r3.24.1.854.fw.bin.bin fs://ont-firmware Download file from FTP-server Download successfully - speed: 2906533.000 bytes/sec during 1.008 seconds, total size 2929684 .......................................... .......................................... ONT firmware vendor is Eltex Corporation, version 3.24.1.854 Write downloaded file to flash memory. .......................................... .......................................... |
ONT firmware custom update
To update firmware of a specified ONT, you need to create a corresponding task and specify the ONT ID and the firmware file name. There are two types of ONT firmware update tasks: single try or multiple tries.
...
The tasks created in the scheduler will continue running until the update completes successfully or the number of tries is reached (the Tries remained parameter).
ONT firmware autoupdate
To enable firmware autoupdate for all ONTs, use the auto-update ont command and specify the update mode (immediate or postpone).
...
Якорь A СХЕМА РАСПАЙКИ НУЛЬ-МОДЕМНОГО КАБЕЛЯ RS-232 A СХЕМА РАСПАЙКИ НУЛЬ-МОДЕМНОГО КАБЕЛЯ RS-232
APPENDIX A. RS-232 NULL-MODEM CABLE PIN DESIGNATION
LTP-4/8X rev.B
DB-9 Socket DB-9 Socket
...
- not used
- not used
- RX
- GND
- GND
- TX
- not used
- not used
- not used
APPENDIX B. Configuring services on ONT Ericsson, Atron, CIG
Starting with version 3.36, ONT support has been added for Ericsson T063G, Ericsson T073G, Atron RFT620, Atron PSG590, CIG G-25A-J80. In service configuration on these ONTs, there are some features presented below.
VoIP configuration
To configure VoIP, you need to create two new profiles: cross-connect type voice, profile voice.
Step 1. Create required profiles.
Блок кода language xml LTP-8X(config)# profile cross-connect "VOICE-ERCS" LTP-8X(config-cross-connect)("VOICE-ERCS")# description "For VOICE ont Ericsson" LTP-8X(config-cross-connect)("VOICE-ERCS")# bridge LTP-8X(config-cross-connect)("VOICE-ERCS")# bridge group "5" LTP-8X(config-cross-connect)("VOICE-ERCS")# outer vid 354 LTP-8X(config-cross-connect)("VOICE-ERCS")# user vid 354 LTP-8X(config-cross-connect)("VOICE-ERCS")# type "voice" LTP-8X(config-cross-connect)("VOICE-ERCS")# exit LTP-8X(config)# profile voice "voice-00-ERCS" LTP-8X(config-voice)("voice-00-ERCS")# sip proxy "123.test.ru" LTP-8X(config-voice)("voice-00-ERCS")# sip outbound-proxy "172.20.20.201" LTP-8X(config-voice)("voice-00-ERCS")# sip domain "123.test.ru" LTP-8X(config-voice)("voice-00-ERCS")# exit
Step 2. Assign profiles to ONT and configure additional VoIP data.
Блок кода language xml LTP-8X(config)# interface ont 0/2 LTP-8X(config)(if-ont-0/2)# service 0 profile cross-connect "VOICE-ERCS" dba "dba-00" LTP-8X(config)(if-ont-0/2)# profile voice "voice-00-ERCS" LTP-8X(config)(if-ont-0/2)# voice port 0 number "402153" LTP-8X(config)(if-ont-0/2)# voice port 0 authentication username "402153" LTP-8X(config)(if-ont-0/2)# voice port 0 authentication password "QFxy2EzfVdrL1"
Step 3. If necessary, configure Value Added Services for the ONT.
Блок кода language xml LTP-8X(config)(if-ont-0/2)# voice fax-mode t38 LTP-8X(config)(if-ont-0/2)# voice features call-presentation special-dialtone LTP-8X(config)(if-ont-0/2)# voice features call-presentation visual LTP-8X(config)(if-ont-0/2)# voice features call-presentation call-forward LTP-8X(config)(if-ont-0/2)# voice features call-progress 3way LTP-8X(config)(if-ont-0/2)# voice features call-progress transfer LTP-8X(config)(if-ont-0/2)# voice features call-progress hold LTP-8X(config)(if-ont-0/2)# voice features call-progress park LTP-8X(config)(if-ont-0/2)# voice features call-progress emergency-hold LTP-8X(config)(if-ont-0/2)# voice features call-progress 6way LTP-8X(config)(if-ont-0/2)# voice features call-wait enable LTP-8X(config)(if-ont-0/2)# voice features call-wait call-id-annonce LTP-8X(config)(if-ont-0/2)# voice features cid call-number LTP-8X(config)(if-ont-0/2)# voice features cid call-name
Блок кода language xml LTP-8X(config)(if-ont-0/2)# voice features cid cid-number LTP-8X(config)(if-ont-0/2)# voice features cid cid-name
Step 4. Apply the changes.
Блок кода language xml LTP-8X(config)(if-ont-0/2)# do commit
Internet and IPTV services configuration
These services are configured similarly to ONT ELTEX.
The list of changes
...
Firmware version
...
Document version
...
Issue date
...
Revisions
...
Added:
- Poe support for ONT;
- Alarm PSE overload support;
- PoE support for ONT in SNMP;
- Ability to set timezone accurate to minutes;
- OMCI alarm PSE overload support;
- OMCI LAN port control;
- NTU-MD500P support.
Added sections:
Fixed:
- Application of backup-configuration when using ACLs;
- Removal of ip source-guard database after LTP restart;
- ONT hanging in CFGFAIL status.
...
Added:
- Redundancy functionality for gpon ports;
- CaTV signal level acquisition;
- Option to disable VLAN filtering for multicast GEM;
- Functionality for forced activation of GPON port, without taking into account the configuration;
- A command to remove dynamic entries from the DHCP Snooping table;
- Possibility to set ONT auto-activation by GPON ports;
- Possibility to auto complete the list of log files;
- Support for PM-DC12 power supply;
- Alarms for exceeding the CaTV thresholds;
- Support for LTP-X rev.D boards.
Sections added:
- GPON port redundancy.
Fixed:
- UNACTIVATED ONT reload;
- ONT reloading in case of authorization error;
- ONT activation bug after mass link crash;
- ONT activation error after quick reconfiguration;
- OLT chip reload, during mass ONT power off;
- Multicast passing through broadcast GEM with unknown-multicast-forward enabled;
- Supported EqID output for NTU-1 rev.B and NTU-RG-5440G-WZ;
- pmchal crash when requesting ONT status;
- Loss of private parameters when updating LTP;
- Operation with configuration that contains null in the fields;
- Saving LLDP settings for 10G-front-port;
- Fixed bug when deleting entries from DHCP Snooping table;
- Stabilized operation with broken blocks on NAND flash;
- Possibility to re-prescribe ONT when auto-activation is enabled;
- Loss of ip arp inspection configuration;
- pmchal crash when using IPSG;
- CLI crash when naming interfaces with capital letters;
- ACL with ARP packets when filtering by ports;
- Removed duplicate events of front-ports state changes;
- Isolation for pon ports that related to different chips.
...
Synchronization with firmware version 3.38.2.
...
Synchronization with firmware version 3.38.1.
...
Synchronization with firmware version 3.38.0.
Sections added:
- CLI hotkeys;
- Origin parameter configuration.
Changes:
- Compatible SFP transceivers;
- User list preview;
- SNMPD configuration;
- GPON interface configuration;
- DHCP Relay Agent profiles management;
- IP Source Guard configuration;
- Tunnelling configuration.
...
Synchronization with firmware version 3.36.2.
...
Added:
- Manual supplemented by LTP R3.36.0 commands.
Sections added:
- Configuring multicast traffic between ONTs within the same tree;
- APPENDIX B. Configuring services on ONT Ericsson, Atron, CIG.
Added description:
- Configuring DHCPD issuing static routes to the network on the ONT TR-interface (option 121).
...
Version 3.32.0
...
Issue 10
...
03.07.2018
...
Added:
- Manual supplemented by LTP R3.32.0 commands.
Sections added:
- ERPS configuration;
- Deleting a license file from OLT
- Automatic ONT activation.
Added description:
- GPON interface configuration;
Changes:
- Active DHCP leases monitoring command;
- IGMP Snooping enabling command.
...
Version 3.30.0
...
Issue 9
...
30.11.2017
...
Added:
- Manual supplemented by LTP R3.30.0 commands.
Sections added:
- LLDP configuration;
- QoS WRR;
- ARP-Inspection;
- Storm Control in PON;
- Configuring Access List Control and policies.
Added description:
- Collaboration of various types of cross-connect;
- Upstream shaping configuration;
- SNMPv3 users configuration;
- SNMPv3 encryption configuration;
- Additional RADIUS servers configuration;
- Configuration of syslog entries for entered commands;
- Updated logging system;
- Configuration of description for the interface in switch;
- Storm Control in switch;
- Fan configuration;
- Reset button configuration;
- MAC Notification trap configuration;
- %OLTMAC% parameter in option 82.
Changes:
- PPPoE sessions view command;
- DHCP sessions view command.
...
Version 3.26.1
...
Issue 8
...
13.12.2016
...
Added:
- Manual supplemented by LTP R3.26.1 commands;
- AAA (radius/tacacs+) functionality description;
- Extended custom parameters description.
...
Version 3.26.0
...
Issue 7
...
09.07.2016
...
Added:
- Manual supplemented by LTP R3.26.0 commands;
- Information about LTP rev.C;
- IP Source Guard functionality description;
- DHCP Relay (broadcast-unicast relay) functionality description;
- Tunnel configuration description;
- ONT licensing description;
- Description of configuring services over IPv6;
- RS-232 null-modem cable pin designation.
Changes:
- OLT. 6.3 firmware update command.
...
Version 3.24.3
...
Issue 6
...
25.04.2016
...
Added:
- Manual supplemented by LTP R3.24.3 commands.
...
Version 3.24.1
...
Issue 5
...
17.12.2015
...
Added:
- Manual supplemented by LTP R3.24.1 commands.
...
Version 3.24.0
...
Issue 4
...
02.09.2015
...
Added:
- Manual supplemented by LTP R3.24.0 commands.
...
Version 3.20.2
...
Issue 3
...
25.07.2014
...
Added:
- The manual is given to the LTP-8X R3.20.2 command system;
- Section 3.2.5 for group operations;
- 5.13, describing operation with ONT configuration templates.
...
Issue 2
...
24.04.2014
...
Changes:
- Errors corrected.
...
Issue 1
...
21.04.2014
...
Added:
- Section 4.1.2, describing the Configuration structure;
- Section 4.1.4, which describes the Configuration autosave;
- Step 7 in the MAC address lifetime configuration;
- Added an application with an example of setting up Triple Play in the VLAN for Subscriber model;
- Parameters of optical interfaces in table 4.1.
Changes:
- Fixed table 24 name;
- Section 6.4.6 is renamed to Multicast statistics.
Scroll Pagebreak
TECHNICAL SUPPORT
For technical assistance in issues related to handling Eltex Ltd. equipment, please, address to Service Center of the company:
Feedback form on the website: https://eltex-co.com/support/
Servicedesk: https://servicedesk.eltex-co.ru
Visit Eltex official website to get the relevant technical documentation and software, benefit from our knowledge base, send us online request or consult a Service Centre Specialist in our technical forum.
Official website: https://eltex-co.com/
Download center: https://eltex-co.com/support/downloads