Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 1 Version 1.1.0
CORINEX User Guide Low Voltage Access and GPON BPL Gateway for last mile solution
06 October 2008
CORPORATE HEADQUARTERS
CORINEX COMMUNICATIONS
1200-570 Granville St.
Vancouver BC V6C 3P1, Canada
Tel: +1 604 692 0520
Fax: +1 604 694 0061
URL: www.corinex.com
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 2 Version 1.1.0
COPYRIGH T
This document, as well as the so described in it, is furnished under license and may be used or copied only in
accordance with the terms of the license. The content of this document is furnished for in use only, it is
subject to change without ce and it does not represent a commitment on the part of Corinex Co ons
Corp.
Corinex Communica Corp. assumes no responsibility or liability for any errors or inaccuracies that may appear
in this document. It is our policy to enhance our products as new technologies, hardware components, so
and rmware become available; therefore, the inform on contained in this document is subject to change
without e.
Some features, s, and op ons described in this document may not be included and sold in certain
countries due to government or policies.
The use of the product or its features described in this document may be restricted or regulated by law in some
countries. If you are unsure which restri ons or ons apply, you should consult your regional Corinex
or the authorized reseller.
Published by:
Corinex Communica Corp.
1200-570 Granville St.
Vancouver, B.C. Canada V6C 3P1
Tel.:+1 604 692 0520
Fax: +1 604 694 0061
www.corinex.com
Corinex is a registered trademark of Corinex Communica Corp. MS-DOS, MS; Windows are either
registered trademarks or trademarks of Corpora on in the U.S.A. and/or other countries. All products or
company names ed herein may be the trademarks of their respec e owners.
Copyright (c) 2001-2006 by Corinex Communi ons Corp.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 3 Version 1.1.0
Revision History:
V1.0 – V1.1 – Oct 09/2008
Minor changes to grammer and spelling.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 4 Version 1.1.0
END USER LICENSE AGREEMENT
This End User License Agreement (EULA) is a legal agreement between you and CORINEX COMMUNICATIONS
CORPORATION (CORINEX) with regard to the copyrighted Software provided with this EULA.
Use of any software and related documentation (Software) provided with CORINEX hardware product, or made
available to you by CORINEX via download or otherwise, in whatever form or media, will constitute your
acceptance of these terms, unless separate terms are provided by the software supplier, in which case certain
additional or different terms may apply. If you do not agree with the terms of this EULA, do not download, install,
copy or use the Software.
1. License Grant. CORINEX grants to you a personal, non transferable and non exclusive right to use the copy of
the Software provided with this EULA. You agree you will not copy the Software except as necessary to use it on a
single hardware product system. You agree that you may not copy the written materials accompanying the
Software. Modifying, translating, renting, copying, transferring or assigning all or part of the Software, or any rights
granted hereunder, to any other persons, and removing any proprietary notices, labels or marks from the Software
is strictly prohibited. Furthermore, you hereby agree not to create derivative works based on the Software. You
may permanently transfer all of your rights under this EULA, provided you retain no copies, you transfer all of the
Software, and the recipient agrees to the terms of this EULA. If the Software is an upgrade, any transfer must
include all prior versions of the Software.
2. Copyright. The Software is licensed, not sold. You acknowledge that no title to the intellectual property in the
Software is transferred to you. You further acknowledge that title and full ownership rights to the Software will
remain the exclusive property of Corinex Communications Corporation and/or its suppliers, and you will not
acquire any rights to the Software, except as expressly set forth above. All copies of the Software will contain the
same proprietary notices as contained in or on the Software.
3. Reverse Engineering. You agree that you will not attempt, and if you are a corporation, you will use your best
efforts to prevent your employees and contractors from attempting to reverse compile, modify, translate or
disassemble the Software in whole or in part. Any failure to comply with the above or any other terms and
conditions contained herein will result in the automatic termination of this license and the reversion of the rights
granted hereunder to CORINEX.
4. Disclaimer of Warranty. The Software is provided “AS IS “without warranty of any kind. CORINEX and its
suppliers disclaim and make no express or implied warranties and specifically disclaim warranties of
merchantability, fitness for a particular purpose and non infringement of third party rights. The entire risk as to
the quality and performance of the Software is with you. Neither CORINEX nor its supplier’s warrant that the
functions contained in the Software will meet your requirements or that the operation of the Software will be
uninterrupted or error free.
5. Limitation of Liability. Corinex’s entire liability and your exclusive remedy under this EULA shall not exceed the
price paid for the Software, if any. In no event shall CORINEX or its suppliers be liable to you for any consequential,
special, incidental or indirect damages of any kind arising out of the use or inability to use the software, even if
CORINEX or its supplier has been advised of the possibility of such damages, or any claim by a third party.
6. Applicable Laws. This EULA will be governed by the laws of Canada, excluding its conflict of law provisions.
7. Export Laws. This EULA involves products and/or technical data that may be controlled under any applicable
export control laws, and regulation, and may be subject to any approval required under such laws and regulations.
8. Precedence. Except as set out above, where separate terms are provided by the software supplier, then, subject
to this EULA, those terms also apply and prevail, to the extent of any inconsistency with this EULA.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 5 Version 1.1.0
TABLE OF CONTENTS
INTRODUCTION............................................................................................................................... 7
FEATURES AND TECHNICAL DATA................................................................................................... 8
LV AND GPON BPL GATEWAY PRODUCT OPTIONS ........................................................................ 9
Low Voltage Access Gateway (CXP LVA GWY) Basic Model...................................................... 9
High Density Low Voltage Access Gateway (CXP HDA GWY) .................................................... 9
GPON BPL Gateway (CXP LVA GPON) ....................................................................................... 9
GPON BPL High Density Gateway (CXP HDA GPON) ............................................................... 10
Gateway with Integrated Coupler............................................................................................ 10
INSTALLATION AND REQUIREMENTS............................................................................................ 11
CONNECTING AND POWERING THE LV AND GPON BPL GATEWAY ............................................. 13
Integrated Coupler Connector ................................................................................................. 14
FIRMWARE AND DEVICE STRUCTURE........................................................................................... 16
CONFIGURATIONS AND SETTINGS................................................................................................ 18
Preparing DHCP/TFTP server.................................................................................................... 18
Step 1: Turning off Windows Firewall from Control Panel ................................................... 18
Step 2: Installing DHCP server............................................................................................... 19
Step 3: Preparing the network interface on the PC.............................................................. 19
Step 4: Setting default interface for DHCP server ................................................................ 20
Step 5: Setting standard profile for DHCP server ................................................................. 21
Preparing Telnet PuTTY for command line interface (CLI) console ......................................... 21
Loading auto configuration file (*.conf) .................................................................................. 22
Step 1: Preparing an auto configuration file ........................................................................ 22
Step 2: Preparing a DHCP profile to download auto configuration ..................................... 24
Step 3: Binding DHCP profile with static IP table.................................................................. 25
Step 4: Rebooting the modem and checking the loading process ....................................... 26
Step 5: Loading auto configuration files to other modems ................................................. 27
EXAMPLE OF DEPLOYMENT .......................................................................................................... 28
TECHNICAL SPECIFICATIONS ......................................................................................................... 31
ANNEX 1: CORINEX AV200 ENTERPRISE FEATURES...................................................................... 32
Introduction ............................................................................................................................. 32
Application Description............................................................................................................ 32
Core Features........................................................................................................................ 32
MAC Layer............................................................................................................................. 38
Application Layer .................................................................................................................. 40
PLC Application Description.................................................................................................. 46
Boot Process ......................................................................................................................... 52
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 6 Version 1.1.0
Constraints for Network Design............................................................................................... 56
ANNEX 2: AUTO CONFIGURATION MANUAL................................................................................ 57
Translation Table...................................................................................................................... 57
Transferring the Translation Table ....................................................................................... 57
Example of a Translation Table............................................................................................. 58
Additional Information about Transferring PTTP ................................................................. 59
AV200 Nodes............................................................................................................................ 60
Auto Configuration &Networking............................................................................................ 60
VLAN Networks ..................................................................................................................... 60
No VLAN Networks ............................................................................................................... 61
OVLAN Configuration and Root Interface............................................................................. 61
Auto Configuration File............................................................................................................ 63
Introduction .......................................................................................................................... 63
Parameter Types ................................................................................................................... 63
Parameter Format................................................................................................................. 63
Supported Parameters in the Auto Configuration File......................................................... 64
General Parameters .............................................................................................................. 64
AGC (Automatic Gain Control) Parameters .......................................................................... 66
RADIUS Parameters .............................................................................................................. 67
Class of Service (CoS) Parameters......................................................................................... 67
Quality of Service (QoS) Parameters .................................................................................... 68
Profile Parameters ................................................................................................................ 69
Translation Table Parameters............................................................................................... 71
VLAN Parameters .................................................................................................................. 71
OVLAN Parameters ............................................................................................................... 72
Access Protocol Parameters ................................................................................................. 72
STP Parameters ..................................................................................................................... 73
MAC Ingress Filtering Parameters ........................................................................................ 74
Custom VLAN/OVLAN Parameters........................................................................................ 75
SNMP Parameters................................................................................................................. 78
Multicast Protocol Parameters ............................................................................................. 78
Corinex MVG/LVG Parameters ............................................................................................. 79
ANNEX 3: EXAMPLE OF CONFIGURATION FILES ........................................................................... 80
Master Access Mode 6 (HE/LV 6) output to coaxial port ........................................................ 80
Master Access Mode 1 (HE/LV 1) output to pin 3 and 4 ......................................................... 80
Master Access Mode 2 (HE/LV 2) output to pin 3 and 4 ......................................................... 80
Master Access Mode 3 (HE/LV 3) output to pin 3 and 4 ......................................................... 81
Slave End User (CPE/EU) output to pin 3 and 4 ....................................................................... 81
TD Repeater (TDR/LV) output to pin 3 and 4........................................................................... 81
Master Access Mode 6 (HE/LV 6) with VLAN and OVLAN parameters.................................... 82
Slave End User (CPE/EU) with VLAN 101 and OVLAN parameters .......................................... 83
Slave End User (CPE/EU) with VLAN 102 and OVLAN parameters .......................................... 84
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 7 Version 1.1.0
INTRODUCTION
Low Voltage Access Gateway (LV Gateway) and GPON BPL Gateway are Corinex’s BPL access
product line using 200 Mbps AV200 Technology. The LV and GPON BPL Gateways allow an easy
installation to Multi Dwelling Units (MDUs) or last mile access neighborhoods where the
Gateway acts as a head end modem, extending an internet connection (optical fiber, DSL, or
wireless access) either to a power line or coaxial cable infrastructure, depending on the
customer’s requirements. The modem allows users to extend an internet connection to a
power line or cable network within an MDU, without the need for installing new wiring. End
users can connect their Ethernet enabled devices such as PC, VoIP phones, Media Centers, etc.,
using the Corinex AV200 series of Powerline or CableLAN Ethernet Adapters, to any electrical or
coaxial socket in their premise to access the Internet.
The LV and GPON BPL Gateways can serve large networks, up to 1,024 network devices. And by
embedding three phase coupler inside the rugged enclosures, the Gateways provide easy
installation for three phase power system deployment. AV200 Powerline technology by Corinex
also provides numerous networking possibilities with physical layer transfer rates of up to 200
Mbps depending on the characteristics of the power line media. OFDM technology and the
powerful error correction system used in AV200 technology allow for robust performance
under harsh conditions in electrical or coaxial networks. The LV and GPON BPL Gateways also
support other external couplers that can be used to inject the BPL signal by connecting through
the coaxial cable port.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 8 Version 1.1.0
FEATURES AND TECHNICAL DATA
Corinex Low Voltage Access Gateway and GPON BPL Gateway are high performance BPL
modem device designed for low voltage power line access networks in either single phase
three wire or three phase four wire system. The Gateway is ideal for use as a Head End unit to
control a last mile low voltage access network as well as a large In Building distribution
network. Using with Time Division Repeater units, it can extend the coverage of a PLC network
beyond 100 users.
Figure 1: Low Voltage Access Gateway
LV and GPON BPL Gateways always come with the basic features include:
Special housing for installations in rough environments like transformer stations and street
cabinets
Ability to configure as a Head End Master (HE), Time Division Repeater (TDR), or Slave (CPE)
unit as same as other AV200 Enterprise products by loading auto configuration setting
Physical throughput connectivity of up to 200 Mbps
802.1Q VLAN & Optimized VLANs (OVLAN)
DES/3DES encryption
Integrated 802.1D Ethernet Bridge with Rapid or Common Spanning Tree Protocol
Quality of Service (QoS) and 8 level priority queues, with programmable priority
classification Engine
Priority classification according to 802.1P tags, IP coding (IPv4 or Ipv6) or TCP
source/destination ports
10/100BaseT Fast Ethernet interface for connection to the network point of presence
CSMA/CARP (Carrier Sense Multiple Access with Collision Avoidance and Resolution using
priorities protocol)
Bridge Forwarding Table for 64 MAC addresses or 1,024 MAC addresses in High Density
model
Optimized support for broadcast and multicast traffic
SNMP agent to facilitate management of larger networks
Integrated three phase coupler
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 9 Version 1.1.0
LV AND GPON BPL GATEWAY PRODUCT OPTIONS
Corinex LV and GPON BPL Gateway come with a variation of models that users can choose to
match with their requirement and deployment type.
Low Voltage Access Gateway (CXP LVA GWYC) Basic Model
The LV Gateway basic model can run as an HE master modem to serve a BPL network of up to
64 MAC addresses. It can connect to maximum 32 TDR or CPE modems directly. This basic
modem can be used in a small size network, typically up to 32 users. The following interfaces
and connectors are provided on the Gateway:
RJ 45 Ethernet Interface for accessing Ethernet network,
Female F type connector for providing BPL access on a coaxial cable,
4 pin power socket for power and providing BPL access on the power line.
Figure 2: CXP LVA GWY Basic Model
High Density Low Voltage Access Gateway (CXP HDA GWYC)
The High Density Low Voltage Access Gateway can serve as a Head End Master modem in a BPL
network comprising of the network devices up to 1,024 MAC addresses in total. HDA GWY has a
capacity to provide direct connection to maximum 64 TDR or CPE modems. Each of TDR modem
can extend the distance reach and a number of connecting CPE modems. It is recommended to
use HDA GWY in a medium or large size network where there are more than 64 network
devices or MAC addresses in a broadcasting domain. The following interfaces and connectors
are provided on the Gateway:
RJ 45 Ethernet Interface for accessing Ethernet network,
F type female connector for providing BPL access on a coaxial cable,
4 pin power socket for power and providing BPL access on the power line.
GPON BPL Gateway (CXP LVA GPON)
The GPON BPL Gateway is an LV Gateway basic model with integration of ITU T G.984 GPON
ONT module and optical interface. It can run as an HE master modem to serve a BPL network of
up to 64 MAC addresses and connect to maximum 32 TDR or CPE modems directly. This basic
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 10 Version 1.1.0
modem can be used in a small size network, typically up to 32 users, extending the last mile
GPON coverage to reach home users by the power line media. The following interfaces and
connectors are provided on the Gateway:
SC APC optical connector for GPON ONT module,
RJ 45 Ethernet Interface for local access to ONT and BPL module,
F type female connector for providing BPL access on a coaxial cable,
4 pin power socket for power and providing BPL access on the power line.
GPON BPL High Density Gateway (CXP HDA GPON)
The GPON BPL High Density Gateway is an HD LV Gateway with integration of ITU T G.984
GPON ONT module and optical interface. It can serve as a Head End Master modem in a BPL
network comprising of the network devices up to 1,024 MAC addresses in total. HDA GPON has
a capacity to provide direct connection to maximum 64 TDR or CPE modems. Each of TDR
modem can extend the distance reach and a number of connecting CPE modems. It is
recommended to use HAD GPON in a medium or large size network where there are more than
64 network devices or MAC addresses in a broadcasting domain. Main application of HDA
GPON is to extend the last mile GPON coverage to reach over 32 home users by the power line
media. The following interfaces and connectors are provided on the Gateway:
SC APC optical connector for GPON ONT module,
RJ 45 Ethernet Interface for local access to ONT and BPL module,
F type female connector for providing BPL access on a coaxial cable,
4 pin power socket for power and providing BPL access on the power line.
Integrated Couplers
All models in the LV and GPON BPL Gateway product line are integrated with internal three
phase coupler which provides easy installation on the three phase power line system. The
integrated coupler connection is a 4 pin socket for coupling the signal to line and neutral wires
of the three phase four wire power line. With this feature, Corinex LV and GPON BPL Gateways
are capable to provide a last mile solution anywhere worldwide. Integration of the internal
coupler eliminates a need for external coupler and minimizes the insertion and connector
losses caused by an external coupler.
Figure 3: Gateway with integrated coupler
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 11 Version 1.1.0
INSTALLATION AND REQUIREMENTS
The LV and GPON BPL Gateways by Corinex are network devices mainly used for last mile
solutions in broadband access technology. Deployment can be on the electric power pole, pad
mount transformer station, street cabinet, or in the network room of an MDU building. The
device is equipped with a special housing for installations in rough outdoor environments like
transformer stations and street cabinets. It can be easily mounted on walls or hanged on wires.
Grounding the case is recommended for safety, and should be done according to the local
electric code of conduct. See figure below for installation example.
Figure 4: Installation of LV Gateway hanging from a supporting wire
The LV and BPL GPON Gateways have a waterproof connector interface to transfer the BPL
signal through the low voltage wire in the same socket as the feeding power. There is a
separated socket from the power plug providing interfaces to 4 wires (three phase lines and
one neutral line). There is also an alternative to use the provided coaxial interface to inject or
couple the BPL signal into the power line wires by an external coupler. To coupling the BPL
signal into a Medium Voltage or any voltage higher than 270 Volts, a proper external coupler
must be used. The Ethernet port is provided in a protective waterproof connector attached to
the housing case to access directly to the device. See figure below.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 12 Version 1.1.0
Figure 5: Waterproof RJ45 connector for local Ethernet access
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 13 Version 1.1.0
CONNECTING AND POWERING THE LV AND GPON BPL GATEWAY
The LV and GPON BPL Gateways come with a waterproof 4 pin male connector for BPL signal
and feeding power. A matching female socket connector is provided in the package.
Figure 6: Four pole pin and socket connectors
Figure 7: Pin configurations on the Gateway
Pin 1 2 3 4
Connect toPower
Neutral
Power
Line
Signal
Line
Signal
Neutral
Pin 1 and 2 are designated for connecting to the input power. For the best practice, pin 1 can
connect to Neutral and pin 2 to Line. Operating voltage is from 85 to 265 Volts AC type. Pin 3
and 4 are for BPL signal to be coupled into the power line. For a good reference, pin 3 can be
assigned for signal Line and pin 4 for signal Neutral. They can connect to the same line neutral
pair used for the input power or different phase line. It is suggested to run 4 wires out of the
socket plug and tap on the power lines.
Pin 3 and 4 can also be used for an external inductive type coupler. To use with inductive
coupler, both pins are connected to a proper loop wire going through the inductive couplers
over line/lines and neutral. Below figure shows an example of using external inductive couplers
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 14 Version 1.1.0
on three phase four wire system.
N
A
B
C
Figure 8: Example of using external inductive couplers for 3 phase lines
In some deployments, the Gateway can communicate to the other modem over a coaxial cable
or injecting the BPL signal into the power line by using an external coupler that comes with
coaxial interface, for example Corinex Coaxial to Powerline Coupler (…)or 11+1 Coupler (…). A
proper configuration setting file must be loaded into the Gateway to direct the BPL signal to
coaxial rather than LV output. Connectivity over the coaxial cable is always better than the
power line. However, to obtain a maximum performance, high performance and low loss cable
like RG 6 type is preferred. Either 50 ohm or 75 ohm impedance can be used with the coaxial
interface. Impedance matching between coaxial cable and the connector is insignificant and the
throughput impairment from mismatching impedance is negligible.
Integrated Coupler Connector
The LV and GPON BPL Gateways integrated coupler connection is on an additional 4 pin
connector for BPL signal. The designation of each pin is as followed.
Pin 1 2 3 4
Connect toCommon
NeutralPhase A Phase B Phase C
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 15 Version 1.1.0
1 4
32
Figure 9: Integrated Coupler Connector
The input power connector of the Gateway with integrated coupler has only 2 pins as shown in
the figure below. Pin 1 and 2 are for connecting to neutral and line.
12
Figure 10: Input Power Connector for the Gateway with integrated coupler
3 phase LV
Signal Output
Input
Power
Coaxial
Output
Figure 11: Signal output ports and power connector
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 16 Version 1.1.0
FIRMWARE AND DEVICE STRUCTURE
Corinex Low Voltage Access Gateway and GPON BPL Gateway are built on AV200 technology
which is capable to reach physical throughput of up to 200 Mbps. The line driver of the
Gateway is powerful and robust, and can be used as a Head End Master (HE), Time Division
Repeater (TDR), or Slave (CPE) unit depending on the configuration setting.
There are 3 functions of the BPL device in network hierarchy. HE unit is a Master modem in a
BPL network controlling traffic and connection negotiation from TDR or CPE units in the same
power line coverage. A CPE unit can connect directly to the HE unit or through TDR unit
depending on the configuration setting options. TDR units have a main function to extend the
coverage over longer distance or the number of end users. TDR units behave as a Slave for the
Master unit and a Master for the Slave unit. Channel access on the BPL media is controlled
mainly from the Master unit by token passing. The TDR unit also controls channel access for its
Slave units by forwarding the token received from its Master unit.
In a BPL network, there should only be one HE unit. To have more than one HE master modem
in the same power line coverage, Frequency Division scheme must be used by setting each HE
unit to run a different frequency mode. Corinex Enterprise firmware provides a solution to use
3 different equal frequency bands; Mode 1, Mode 2, and Mode 3.
HE
LV lines
TDRTDR
CPE CPE
CPE TDR
CPE CPE
CPE
CPE CPE
Head-End Master Unit(HE)
TD Repeater Unit (TDR) behaves as a Slave for
the Master and a Master for the Slave
Slave Unit(CPE)
Figure 12: Typical BPL Network Hierarchy
All Gateway models are running Corinex Enterprise firmware and are set to run the auto
configuration boot up process by default. This process requires DHCP and TFTP server to
provide the network settings and configuration file to the modem.
The modem has a command line interface console for changing configuration and checking
status of its operation or connectivity with the other modems.
A number of parameters can be defined in an auto configuration file stored in the TFTP server.
When the modem requests an IP from the DHCP server, it will be provided with an instruction
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 17 Version 1.1.0
to download a configuration file from TFTP server together with the assigned IP address using
BOOTP protocol. The text file below shows a simple auto configuration file for the HE unit:
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = HE
GENERAL_FW_TYPE = LV
GENERAL_IP_ADDRESS = 10.10.1.100
GENERAL_IP_NETMASK = 255.255.255.0
GENERAL_IP_GATEWAY = 10.10.1.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
GENERAL_AUTHENTICATION = NONE
GENERAL_SIGNAL_MODE = 6
SIGNAL_SUB_MODE = 0
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = IND
MCAST_MPP2IGMP_PORT = NONE
MCAST_IGMP_SNOOPING = NO
By default the modem with Enterprise firmware is running as a CPE unit searching all possible
frequency modes for the BPL signal from the connecting line. If the Gateway is running by the
above configuration file and connecting to other modems on the same physical line, they
should make a connection and show the connectivity status in the master modem’s CLI console
similar to the below figure.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 18 Version 1.1.0
Figure 13: CLI console from Telnet showing connectivity status
CONFIGURATIONS AND SETTINGS
Preparing DHCP/TFTP server
The following steps are for installing and preparing DHCP server on a PC. After running
this procedure, the DHCP/TFTP server will be set up properly in the PC and there is no need to
run the procedure again.
Step 1: Turning off Windows Firewall from the Control Panel
To configure an AV200 modem, a number of UDP and TCP ports in Windows are used by
the DHCP/TFTP server and other applications. Therefore, those ports must be allowed by
Windows firewall or the firewall must be turned off. If the PC is running any anti virus software
and those ports are protected by anti virus, that feature should be disable according to anti
virus’ manual.
If Window Firewall cannot be turned off, the following ports must be allowed for those
applications.
UDP port 68 used by BOOTPC
UDP port 67 used by BOOTPS
UDP port 69 used by TFTP
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 19 Version 1.1.0
Step 2: Installing DHCP server
This document is using haneWIN DHCP Server 3.0.18 for illustration. Any other DHCP
server or later version of haneWIN can also be used by following the instruction directed by
that DHCP server and applying the similar settings. DHCP servers that can be used with auto
configuration must support BOOTP protocol. The user can download DHCP server from
www.hanewin.de and install in the PC. The unregistered version can be used up to 30 days.
Later version supports Windows Vista™.
Step 3: Preparing the network interface on the PC
The PC network interface must have a fix IP address set to 10.10.1.254 and subnet
255.255.255.0 or any class.
This can also be done by the Windows command line (C:\WINDOWS\system32\cmd.exe) and
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 20 Version 1.1.0
executing “netsh” with the following parameters.
>netsh interface ip set address "Ethernet LAN" static 10.10.1.254 255.255.255.0
Network interface named “Ethernet LAN” might be different. To check the correct name, the
user can use “ipconfig” to display all Ethernet interfaces in the PC.
Step 4: Setting default interface for DHCP server
The user must activate DHCP server from File > Service > Activate. This will run DHCP
server as a Windows service. The user can check and verify that this service has been started
from Services in Administrative Tools. By default, haneWIN will start automatically after
Windows started. To prevent from automatic starting, the user can set it to start manually. If
the Ethernet interface is active, it will show on the preference tab. Interface 10.10.1.254 must
be checked, other interface shown must be clear, and ‘Use only selected interfaces’ must be
checked to prevent the other network interface from using this DHCP server.
10.10.1.254
The user can use TFTP server that comes with haneWIN DHCP. TFTP has a root directory where
all auto configuration files shall be located. Make sure that this root directory is customised
properly and all *.conf are copied to this root directory. Otherwise, TFTP server won’t be able
to find the requested file.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 21 Version 1.1.0
Step 5: Setting standard profile for DHCP server
DHCP server will set a default standard profile for the selected IP interface from step 3.
This must be customised for the network to be used with AV200 modems. The following setting
set this interface to provide IP addresses ranging from 10.10.1.100 to 10.10.1.250 to any
requested client with subnet mask 255.0.0.0. AV200 modem needs additional setting on Option
120 to be binary 0 0 0 0 or unsigned 32 bit integer 0x0000.
Interface IP = 10.10.1.254
Dynamic IP address pool from 10.10.1.100 to 10.10.1.250
Any lease time and subnet mask is OK.
Option 120 gives value of binary “0 0 0 0”. Make sure that after adding, it shows “120 4
0 0 0 0”.
Customise to your own Network Design
This must be set for all AV200 modems. Option 120 = 0 0 0 0 “Binary” (4 Bytes).
10.10.1.254
10.10.1.100
10.10.1.250
Preparing Telnet PuTTY for command line interface (CLI) console
AV200 modem needs a Telnet client running on a PC to interface, monitor, and control
all the functions available for command line interfaces (CLI). Telnet client should have the
following settings.
Telnet port 40000
CR/LF
Local echo on and local line editing on
Best for Linux terminal and compatible with VT100 terminal
Passive Telnet negotiation mode (send after CR allowing Backspace to correct the
mistype.)
Login admin mode by /mode admin and password “maxibon” (PuTTY needs login twice.)
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 22 Version 1.1.0
Common commands used in CLI are ‘I’ and ‘ls’.
Loading auto configuration file (*.conf)
Step 1: Preparing an auto configuration file
In TFTP server set up, the root directory must be specified and this is the folder for all
auto configuration files with .conf extension. Auto configuration file is a simple text file edited
by Notepad to set up each AV200 modem.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 23 Version 1.1.0
A simple configuration for a master modem is as follows. In this example, it must be saved in
HE.LV.6.conf.
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = HE
GENERAL_FW_TYPE = LV
#GENERAL_IP_ADDRESS = 10.10.1.105
#GENERAL_IP_NETMASK = 255.255.255.0
#GENERAL_IP_GATEWAY = 10.10.1.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
GENERAL_AUTHENTICATION = NONE
GENERAL_SIGNAL_MODE = 6
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = IND
Below is a simple configuration for slave modem using Corinex AV200 Powerline Adapter.
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = CPE
GENERAL_FW_TYPE = LV
#GENERAL_IP_ADDRESS = 10.10.1.105
#GENERAL_IP_NETMASK = 255.255.255.0
#GENERAL_IP_GATEWAY = 10.10.1.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
The master modem needs to download a configuration file from TFTP server in order to work
properly. But the slave modem doesn’t need a configuration file as it is set to CPE type by
default. If there is a special setting for the slave modem, it can be included in slave or CPE
configuration for example signal_mode_list.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 24 Version 1.1.0
Step 2: Preparing a DHCP profile to download auto configuration
To prepare a profile in DHCP server, the user must make sure that DHCP server is
running. In Windows services, DHCP server must show status as “started”.
In DHCP server, under Options, Manage Profiles, and Add, it will ask for a profile name.
Any name that can refer to the function of modem is applicable. For example, HE.LV.6 means
the function of master or HE on LV access MAC mode and running on mode 6. Name is the
user’s choice.
1
2
3
4
5
6
7
To set up a profile, the user must specify the following options.
1. Setting subnet mask to 255.255.255.0 or any subnet designed by the user
2. Setting gateway address to this PC
3. Setting TFTP server address
4. Setting TFTP name, must be a TFTP address
5. Setting option 66
6. Setting option 18 to auto configuration file name with .conf extension (string)
7. Setting option 120 to ‘0 0 0 0’, 4 zeros and 3 spaces (binary)
Then this profile is already for the next step.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 25 Version 1.1.0
Step 3: Binding DHCP profile with static IP table
On this step, the modem must connect to PC and get an IP from DHCP server. It will
appear MAC address of the modem, 1 MAC address for a single modem and 3 MAC addresses
for MDU or MV Gateway, in DHCP dynamic table.
The user can use Ethereal to capture Ethernet packets. There must be four (4) steps of DHCP
request; DHCP discover, offer, request, and ack. If there is no response from the server
(10.10.1.99), then there must be something wrong with the server setting. The user must check
Basic Procedure 1 again.
By selecting this MAC address and copying to static table, it will be transferred to the static
table which allows the user to bind with any IP and profile. If the user changes IP address, the
old address must be deleted from the dynamic table to avoid duplication. Configuration profile
is the profile to instruct this modem to download an auto configuration file from TFTP server, in
this example HE.LV.6.conf.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 26 Version 1.1.0
After completely binding a profile to the IP address, on the static IP table, it shows the correct
profile to be used.
Step 4: Rebooting the modem and checking the loading process
As changing in the DHCP server is done after the modem gets IP address, the modem
won’t reload the configuration until it is rebooted or reset or factory reset or end of IP lease
time. The user must reboot the modem by power off and power on again. Power switch on the
MDU gateway will turn on and off all 3 modules at the same time. If the user want to reset only
one modem, the use must telnet and log in as an Admin and use command “/hw rst” for reset
or “/frst frst” for factory reset. In an older firmware (version 3), factory reset command is “/hw
frst”.
After reboot, the modem shall receive IP address from DHCP server, send a request for
file download to TFTP server, and download *.conf file from the server. In the Ethereal capture
below, it shows the process of DHCP and TFTP download. There are 4 DHCP steps; discover,
offer, request, and acknowledge (ack). On offer and ack steps, DHCP server includes 4 options
in the message. Option 3 is a gateway IP. Option 18 is the configuration filename. Option 66 is
TFTP server IP address. And Option 120 is to turn off management VLAN. If any of those options
is missing, the modem won’t properly loaded the configuration file from the server. It is
recommended to keep on monitoring by using the Ethereal in order to prevent from a mistake.
The user can check the content of *.conf file in the data packets.
On the Ethereal, the user must see packets containing Rapid Spanning Tree Protocol
(BPDU) sent out from the modem through Ehternet port from time to time. If the user cannot
see RSTP BPDU or there is a VLAN tag on this packet, then there is something wrong with the
DHCP setting or modem.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 27 Version 1.1.0
Step 5: Loading auto configuration files to other modems
The user doesn’t need to connect PC to all adapters or modems directly in the network
to load a configuration file. After the first modem connected directly to the PC loaded its
configuration, it will restart and turn into a master modem which allows all other modems to
connect to. Then, the other connecting modem will broadcast DHCP offer and request IP
address through BPL channel to the master modem’s Ethernet port. The same process will be
taken in the sequential order until the last modem.
MV PLC
network
Gigabit Ethernet
Ring
RADIUS
server
DHCP
server
FTP
server
RouterHead-End
RepeaterRepeater
CPECPE
DHCP request(Repeater MAC address as a parameter)
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 28 Version 1.1.0
EXAMPLE OF DEPLOYMENT
The first example of deployment shows a typical application for the last mile access to servicing
houses from GPON optical fiber cable end or an Internet access end point via UTP cable.
LVA-GWYCHDA-GWYCLVA-GPONHDA-GPON
HE Unit
I I I I I I I I I I
Phase A, B, C, Neutral
EnterpriseWallmount
adapter
meter metermeter
Transformer
Supporting wire
Couplingpoints
Input power
Internet Access
CAT-5E or F/O
Figure 14: LV Gateway in a last mile deployment
The second example shows an application in an MDU building where the Gateway is used to
distribute the Internet access to multiple residential units using 3 phase 4 wire power system.
Corinex 11+1 coupler is used for signal distribution together with inductive couplers to improve
the signal strength on all 3 phase lines. Coaxial output is selected on the Gateway.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 29 Version 1.1.0
LVA-GWYHDA-GWY
HE Unit
I I I I I I I I I I
Phase A, B, C
InductiveCouplerMode 6
Tapping on one phase and neutral lines. Using the inductive ferrite coupler around all 3 phase lines, excluding the neutral.
In electric room - basementCable Shaft / Vault
meter
11+1 Coupler
Wallmountadapter
Figure 15: MDU application
The number of servicing users in the above example is limited to 32 for LVA GWY and 64 for
HDA GWY according to the maximum of BPL ports that can provide on each Gateway model. To
extend the number of users, HDA GWY must be used for the HE Master unit with another HDA
GWY as a TDR unit. The HE unit connects to 63 CPE units and 1 TDR unit. The TDR unit connects
to 64 CPE units. Total number of servicing users is 63+64 = 127. The number of all MAC
addresses in this network is 255 excluding the HE unit and assuming that one CPE unit is
connecting to one PC only. A 2 way splitter used in this configuration will provide a separation
between two Gateways enough to prevent from signal saturation. More TDR units can be
deployed in order to increase the number of users. However, the network latency will be
increased as the number of CPE units and activity of users’ application.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 30 Version 1.1.0
HDA-GWYHE unit
HDA-GWYTDR unit
I I I I I I I I I I
Phase A, B, C
InductiveCouplerMode 13
Wallmountadapter
Tapping on one phase and neutral lines. Using the inductive ferrite coupler around all 3 phase lines, excluding the neutral.
In electric room - basementCable Shaft / Vault
meter
11+1 Coupler
Figure 16: High density MDU application
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 31 Version 1.1.0
TECHNICAL SPECIFICATIONS
Standards ITU T G.984.x, IEEE 802.3u, 802.1P
802.1Q, UPA Access Specification
Safety and EMI EN 55022 Class B, EN 55024, EN 50412
EN 60950 1:2001 IEC 60950 1 :2001
Backbone speed GPON ONT: 2.488Gbps downstream, 1.244Gbps
upstream
BPL: Up to 200 Mbps (PHY)
Ethernet: 10/100 Mbps Full Duplex (AUTO)
Three phase coupler to power line 110VAC / 220VAC / 240VAC
Interfaces SC/APC optical connector,
Power line connector,
F type female coaxial connector,
10/100BaseT Fast Ethernet RJ 45
Powerline frequency range used 2 – 34 MHz
Power input 85 to 265 VAC, 50/60Hz
Dimensions 230 x 185 x 80 mm
Weight 2 Kg
Transmitted power spectral density 50 dBm/Hz
Power consumption Maximum 20 Watts
Operating temperature 20° to 70°C ( 4°F to 158°F)
Operating humidity 10% to 80% non condensing
Environmental class IP68
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 32 Version 1.1.0
ANNEX 1: CORINEX AV200 ENTERPRISE FEATURES
Introduction
This annex describes the features included in Corinex Enterprise firmware version 4.0.110 or as
identified as ac_sv4_0_110_0_0_3_0_8 for AV200 product family.
Application Description
• Core Features: This section describes the core features, such as the protocols
related to the PLC physical layer and the low level support for packet management;
• MAC Layer: Describes the components that compose the Medium Access Control
layer;
• Application Layer: A description is given of the components that run above the core
and MAC layers;
• PLC Application: This section describes some parameters specific to the PLC
application;
• Boot Process: This section describes, by way of example, the start up process.
Core Features
The core features are the protocols related to the PLC physical layer and the low level support
for the packet management.
802.1D Bridge Control
The bridge implements learning, ageing, forwarding, and the Spanning Tree Protocol (STP) as
specified in 802.1D.
Bridge MAC Table Capacity
The bridge MAC table capacity is the number of different Ethernet MAC addresses that can be
stored in the bridge in order to perform forwarding. Packets addressed to MACs not stored in
the bridge table are replicated through all interfaces. In the current firmware implementation,
the capacity of this table is varied by the model as follows:
Table 1: MaximumMACs in Bridge
AV200 PRODUCTS MACs
Powerline Wallmount adapter 32
All desktop adapters, MV Gateway, LV and GPON BPL Gateway basic model 64
LV and GPON BPL High Density Gateway 1024
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 33 Version 1.1.0
Learning Capacity
The learning speed is defined as the number of different MAC addresses per second received in
the bridge and learned, with an unlearned ratio of less than 1% of the total MACs received. This
value does not depend on the internal chip model.
Table 2: Learning Speed
750 MACs/second
Spanning Tree Protocol (STP)
The standard Spanning Tree Protocol is implemented in the current version, as described in the
IEEE 802.1D standard (1998 edition). By default, the management VLAN is used to send the STP
packets when VLANs are enabled.
The Common Spanning Tree (CSTP) protocol can be configured in the current version. With this
variation of the STP, the STP packets are forwarded without a VLAN tag in the Ethernet/Gigabit
Ethernet interfaces connecting the PLC network with the backbone.
The spanning tree protocol implemented includes the Rapid Spanning Tree, as described in the
IEEE 802.1w standard. Rapid Spanning Tree Protocol (RSTP; IEEE 802.1w) is an amendment to
802.1D.
The administrator should be able to define STP boundaries, so that bridge messages cannot
pass through some pre defined points. Therefore, topology changes would only be noticed
within a limited region and hence convergence is faster. Only users directly affected by the link
failure in the tree structure will detect a temporary (short) traffic cut during recovery.
Encryption Control
Corinex AV200 product family includes DES/3DES encryption feature. The current version of
firmware has encryption disabled by default. However, it is possible to enable and configure it
through the console. The supported key length is 56 bit by default. The use of 168 bits is
available by special customized order.
Adaptive Bit Loading Control
The Adaptive Bit Loading Protocol is the software component responsible for adapting the
modulation of each OFDM carrier, depending on the SNR of that carrier. This allows the highest
possible throughput to be achieved with the current link quality. The main functionality of this
component is:
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 34 Version 1.1.0
• Change carrier modulation when the carrier SNR changes, adapting to the new link
quality and avoiding line errors (if modulation is too high for the current link quality)
or increasing efficiency (if the current link quality supports a better modulation);
• Carrier modulation does not follow linearly any SNR change, but must be filtered in
time in order to reduce the probability of errors due to an unstable channel. Channel
overload due to adaptive bit loading protocol packets must also be minimized.
Therefore filters are included in both senses: not only to avoid any changes when
they are not significant (i.e. slight improvement in only one carrier), but also with a
smart algorithm that will learn from variations in SNR and modify the modulation
accordingly;
• All ports are treated fairly, that is, their Bits Per Carrier (BPC) are evaluated with the
same frequency. The period of BPC evaluation depends on the number of nodes
visible in the network: the more nodes, the less frequent the measurements are, in
order to avoid overload of the CPU;
• BPC measurements between a CPE and its master are interrupted when no data
traffic is present, and therefore the CPE becomes idle;
• HURTO mode is the most robust transmission mode and is used when the channel
condition is bad. Having connections in HURTO mode should be avoided in a
network. No more than four connections in HURTO mode (or with bits per symbol
below 875) on the reception side should be allowed. Increasing that number may
result in increased packet loss.
Service Classifier
The service classifier allows classifying the incoming packets from the input interfaces
(Ethernet, FW and PL interfaces) to the power line. The computation of the priority is
performed by means of a group of rules programmed by the firmware. There are two different
criteria for computing the priority. The selection of the criteria is based on the match of a
determined field of the Ethernet frame with one predefined pattern. Once a criterion is chosen,
the priority is computed according to the parameters in that criterion. This method of
prioritization allows for computing the priority of different packets using different fields and bit
patterns. For example, there can be a difference in the computation of the priority depending
on whether the packet is an IP packet or not. If the packet is an IP packet, then the priorities
assigned can match those of the TOS field. Service classifier configuration can be specified in
the auto configuration file.
VLAN/OVLAN
Corinex AV200 product supports the use of Virtual LAN (VLAN), specified in the IEEE 802.1Q
standard. It also keeps track of the priority field described in the 802.1p standard. The service
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 35 Version 1.1.0
classifier can use this field to prioritize traffic.
The basic VLAN configuration is service guided. Different VLANs are configured in the PLC
network according to the type of data:
• Reserved VLAN (used for PLC protocols);
• Management VLAN;
• Data VLANs;
• VoIP VLANs.
Each of these VLANs can be configured with a different priority. The reserved VLANs are fixed to
VLAN 1 and VLAN 4094. VLAN 0 is not supported.
Custom VLAN
Corinex AV200 product allows enabling the custom VLAN/OVLAN. When you enable this
feature, you can completely configure the different ports in VLAN terms.
With a custom VLAN you can:
Enable VLAN tagging in Ethernet ports;
Change the VLAN port filtering behaviour:
o Forbidden lists: Packets with tags in the list are dropped;
o Allowed lists: Packets with tags different from the ones in the list are
dropped;
Change the VLAN port filtering tag lists;
Enable/disable the Out Format of the ports:
o Enabled: Packets transmitted with a VLAN tag;
o Disabled: Packets transmitted without a VLAN tag;
Enable/disable the Tagged Only of the ports:
o Enabled: Input untagged packets are dropped;
o Disabled: All input packets are accepted;
Enable/disable the ingress filtering (egress filtering is always performed when the
VLAN is active).
VLAN Tag Translation
Corinex AV200 product allows tag translation in Ethernet interfaces. Packets coming with tag A
from the Ethernet interface are retagged with tag B inside the PLC network. When a packet
with tag B exits the PLC network in the same interface, it is retagged to the A source tag. Only
one tag translation can be used per Ethernet port.
Corinex AV200 product supports OVLAN, a mechanism independent from the VLAN. OVLAN
tagging is similar to VLAN tagging, but it is only used inside the PLC network. The OVLAN tags
are not propagated outside the PLC network.
The basic OVLAN configuration is uses only one OVLAN tag (ROOTPATH) to allow the isolation
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 36 Version 1.1.0
of all end users of an access network. Another OVLAN tag (0) is reserved for PLC protocols.
Custom OVLAN
Corinex AV200 product allows enabling the custom VLAN/OVLAN. When you enable this
feature, you can totally configure the different ports in OVLAN terms, similar to VLANs.
With a custom OVLAN you can:
Enable OVLAN tagging in Ethernet ports;
Change the OVLAN port filtering behaviour:
o Forbidden lists: Packets with tags in the list are dropped;
o Allowed lists: Packets with tags different from the ones in the list are
dropped;
Change the OVLAN port filtering tag lists;
Enable/disable the Out Format of the ports:
o Enabled: Packets transmitted with a VLAN tag;
o Disabled: Packets transmitted without a VLAN tag;
Enable/disable the Tagged Only of the ports (only PLC ports):
o Enabled: Input untagged packets are dropped;
o Disabled: All input packets are accepted;
Enable/disable the Accept Tagged of the ports (only Ethernet ports). This is useful in
implementing frequency division repeaters:
o Enabled: Input tagged packets are accepted;
o Disabled: Input tagged packets are not accepted.
Enable/disable the ingress filtering (egress filtering is always performed when the
VLAN is active).
The number of supported VLANs depends on the modem’s configuration. The hardware has an
internal table, in which the VLAN information is stored. This table is unique and is shared by all
interfaces in the modem. The elements in this table can be linked to create lists. This table is
used to store the VLAN and OVLAN configuration (list of tags).
The configuration for each interface is a pointer to an entry in this table. The list of tags can be
configured as allowed or forbidden tags. The ‘forbidden tags’ can be used to allow all of the
possible VLAN tags except a reduced list of tags that are not allowed (forbidden).
With the current implementation of the FW, it is not possible to share lists of tags between
different interfaces. The total number of tags that can be used is limited by the following
equation:
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 37 Version 1.1.0
There is also a limitation per port, as detailed in Table 3.
Table 3: Maximum VLAN/OVLAN Tags
MODEL in AV200 PRODUCT TOTAL VLAN + OVLAN TAGS VLAN TAGS PER PORT OVLAN TAGS PER PORT
Wallmount adapter 64 6 2
All desktop adapters,
MV, LV, and GPON BPL
Gateways basic model
255 255 255
High Density Gateway 255 255 255
MAC Filtering
MAC filtering allows limiting access to the PLC network through the Ethernet interface to a
certain number of source MAC addresses. The maximum number of allowed addresses is 4.
There are two working modes:
1. FIXED mode: The allowed MAC addresses are specified in the auto configuration file;
2. AUTO mode: The allowed MAC addresses are the first ones learned by the Ethernet
interface until the maximum number of allowed MAC addresses is reached.
Spatial Reuse
This feature tries to maximize the efficiency of the simultaneous use of the physical channel.
The spatial reuse relies on two basic tools to do its work, the Power Control and the Sub
modes.
This feature only affects slaves. When enabled, the slaves will try to reduce their transmission
gain maintaining the BPC value of their link with the master node over a certain threshold.
The sub modes are modes that share the same spectrum but are not mutually compatible. In
this way one modem in a sub mode sees a modem in another sub mode as white noise and
they do not disturb each other.
Power Mask Control
The Power Mask (PM) is a transmitted Power Spectral Density (PSD) frequency mask that is
used to prevent or decrement transmitted Power in some bands giving a particular “shape” to
the PSD. There are three different PM concepts; the Mode PM (PM), the Regulation PM (RPM)
and the Raw PM (RawPM).
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 38 Version 1.1.0
Mode Power Mask: The MPM is associated to a transmission mode (tx mode)
definition, this power mask is always merged with types of power mask if they are
configured, so it is the only one set in the Hardware if RPM and RawPM are disabled;
Regulation Power Mask: The RPM is transmission mode independent and it is
defined by a set of attenuated bands called notches, each of which are defined by its
start frequency, stop frequency and deep where the frequencies are specified in KHz
and the deep in dB. The carriers in a notch are removed from the output signal, and
the deep is used to calculate the slope of the PSD frequency mask, so its value
affects the carriers adjacent to the notch. The objective of the RPM is to comply with
PSD regulations that prohibit interference in certain bands such as those used for
amateur radio, and to guarantee that the PSD inside the notch has a level at least
“deep” dB under the maximum level of the PSD outside it;
Raw Power Mask: The RawPM is the carrier defined mask downloaded in the auto
configuration file and preceded by the identifier GENERAL_SIGNAL_POWER_MASK.
It is always applied when the download is correct and is transmission mode
independent, so particular carriers are attenuated. Care should be taken when there
are additional transmission modes as these can be removed. RawPM is only
recommended when a modem uses one transmission mode.
The three types of PM are always merged to obtain the most restrictive PSD, which means the
minimum transmitted PSD for each carrier or, in other words, the maximum value for PM for
each carrier. So, MPM is always applied and may be different for each tx mode. If RPM is
enabled, its carrier coefficients are calculated for each tx mode and merged with MPM. RawPM
is merged with the MPM and the RPM (if enabled).
NOTE: Certain limitations must be taken into account when defining new Power Masks:
• There must be a minimum of 20 non attenuated carriers between notches;
• At least one quarter of the band must be unmasked.
It must be taken into account that these limitations should be used as a reference and not as an
exact value.
MAC Layer
LV Access MAC & QoS
Bandwidth Limitation
Bandwidth limitation is a feature that limits the amount of data a node can transmit and
receive. It does not provide any guarantees on the obtained throughput, although, where
possible, the targeted limit will be achieved within some margin of error.
For low bandwidth limits, the bandwidth obtained after limitation is not accurate. However, it is
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 39 Version 1.1.0
possible to predict the value that will be obtained by using the following graph. Anyway the
final value and the marginal error will depend on the physical level, the protocol efficiency, the
latency step configured and the number among other factors.
Figure 17: Expected Throughput vs. Measured Throughput
This graph has been obtained considering a HE CPE scenario with good physical level and the
entire default configuration, except for the bandwidth limitation that is configured in each case
with a different test value. The traffic sent is a unidirectional UDP flow (upstream or
downstream) with a higher rate (at least double) than the bandwidth limitation configured.
The characteristics of the algorithm are shown in Table 4.
Table 4: Bandwidth Limitation
PARAMETER VALUE
Minimum Speed 512 Kbps
Maximum Speed 20000 kbps
Convergence Time 30 sec
Speed Fluctuation <10%
The latency management is achieved through a set of features, designed to guarantee Quality
of Service. The Service Classifier can be configured to prioritize the traffic according to the
desired criterion (TOS, VLAN tag or any other configured) and each of the PLC priorities (from 0
to 7) assigned by the Service Classifier has a Service Level Agreement (SLA1, SLA2, SLA4 and
SLA8) associated.
CSMA/CARP MAC
The CSMA/CARP MAC is implemented in the current firmware version. The CSMA/CARP MAC
can be activated by selecting GENERAL_MAC_MODE = INHOME in the auto configuration file.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 40 Version 1.1.0
Layer 2 ACKs
It is possible to configure layer 2 ACKs according to the priority of the traffic being transmitted.
The ACK policy is unique per connection, and must be the same per packet: if several priorities
are sniffed the policy will be fixed by the maximum SLA detected. Layer 2 ACKs are enabled by
default in every power line connection, for all data priorities.
Application Layer
TCP/IP Stack
The firmware includes a TCP/IPv4 stack supporting the IP, UDP, TCP, ARP and ICMP protocols.
The stack itself is not needed for the basic PLC modem functionalities, but it helps in remote
accessibility, mainly for configuration purposes. The UDP/TCP protocols allow creating sockets
with other IP machines and using high level protocols such as FTP, HTTP, etc. As a limitation,
this TCP/IP stack does not support IP fragmentation. The maximum packet size allowed is 1514
bytes.
TFTP Client
The firmware includes a Trivial File Transfer Protocol (TFTP) client that allows downloading files
from a TFTP server. This is the simplest way to transmit files. It is primarily used for
downloading new firmware versions, and downloading auto configuration files. The drawback
of this protocol is that has no error correction and uses UDP.
The maximum downloaded file size is listed in Table 5.
Table 5: Maximum Downloaded File Size
OPERATION SIZE (KB)
Configuration file 50
Other file downloaded using a console command 26.5
The file name can be up to 256 characters long.
FTP Client
The firmware includes a File Transfer Protocol (FTP) client that allows downloading or uploading
files from an FTP server. This is a more robust protocol for downloading files. The FTP protocol
uses a TCP connection and is able to confirm whether or not the file has been correctly
downloaded or uploaded. It is used primarily for downloading new firmware versions, and
downloading and uploading auto configuration files. The limitations regarding file size and
name length are the same as in the TFTP client.
DHCP Client
The modem includes a DHCP client to automatically configure the basic IP parameters (IP
Address, Subnet Mask and Default Gateway address). The system supports the DHCP
extensions and configuration file downloading.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 41 Version 1.1.0
Link Search
The Link Search protocol is the first protocol that takes place when a CPE is started. Its aim is to
select a link (or transmission mode) amongst a list of links in which an access network is
detected. Each link is tested for Tlink
seconds. The CPE will select the first link in the list and will
configure the transmission mode. After Tlink
seconds, if no access network is detected, the
transmission mode will be changed to the next one in the list. The worst case time to detect an
access network if Nlinks
is the number of links in the list is:
Nlinks x Tlink x Nsubmodes
The default values are:
Tlinks
= 5 seconds
Nlinks
= 13 links
Nsubmodes
= 4 submodes
Access Protocol/Roaming
When a CPE detects an access network, it will start the Access Protocol in order to obtain
access to the network. The master and the TD repeaters present in the network send
continuous invitation or access tokens. The CPE will select the best master according to certain
criteria, and will answer this invitation token in order to access the network through this
master. The master might deny access to the CPE, in which case the CPE will select a different
master and will try to access the network through that master.
If access to the network is not allowed through any visible master in the network, the CPE will
restart the link search protocol, in order to find a new link.
Once a CPE is connected to a master, it can re evaluate its status periodically, and can change
its connection to a new master, according to certain criteria. This phase is known as the second
step.
The default configuration has been chosen in order to avoid instabilities: its frequency is very
low, and the change of master will only occur if the current master has very bad SNR.
The second step takes place after the auto configuration process and every three hours.
The SNR threshold required to change masters is the equivalent to 2,150 bps (non
filtered reception value).
Auto configuration
The objective of the auto configuration process is the centralized management of a BPL
network using configuration files stored in a centralized database that are transferred to each
piece of equipment when it boots. These files contain all of the information that a node needs
in order to function in a correct manner.
Below is a brief description of the process which is discussed in more detail later in the manual:
1. Every node starts with the same default factory configuration: Access CPE;
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 42 Version 1.1.0
2. Using PTTP (Parametric Translation Table Protocol) the modem discovers if it is booting
in a network with VLANs or not. If a network has been built using VLANs to isolate traffic
between data, voice over IP or management traffic, it is necessary to know the
Management VLAN of that network segment for the DHCP request to reach the
backbone. The information passed between modems during PTTP is called the
translation table;
3. Using DHCP protocol, each node gets its IP configuration (IP address, netmask and
gateway), the phone number (in the case of CPEs) and the name of its corresponding
auto configuration file;
4. Using TFTP protocol, the nodes download the auto configuration file and configure the
firmware accordingly.
In addition to the main steps outlined above, but there is further point to consider:
In order to achieve a secure network, powerline (PL) authentication is introduced. When
a new slave is trying to access the PL network and connecting to a master or a repeater,
the master or repeater may perform a RADIUS request to authenticate the user. The
RADIUS server will reply with information used to configure the master’s interface to
the new user. However, auto configuration also has a way to avoid using the RADIUS
server if desired. This consists of declaring a list of MACs, profiles and FW type in the
auto configuration file and using this list instead of RADIUS to authenticate the users.
If the node is the first modem in the network and connected directly through the Ethernet port
to the backbone, the auto configuration process is different:
1. This node starts with the same default factory configuration: Access CPE;
2. Using DHCP protocol, each node gets its IP configuration (IP address, netmask and
gateway) and the name of its corresponding auto configuration file. There is also
another parameter called PTTP code that indicates if VLAN is used and the value of
the management VLAN if needed. Once this parameter is obtained the PTTP
protocol finishes;
3. Using TFTP protocol, the nodes download the auto configuration file and configure
the firmware accordingly.
When any node boots, there is a parameter stored in the NVRAM called GENERAL_USE_
AUTOCONF. When this value is ‘yes’, the node boots in auto configuration mode and when ‘no’,
it boots in NVRAM mode. There are two auto configuration possibilities inside the auto
configuration boot mode depending on whether or not PTTP is performed.
In this auto configuration boot modality, the node always initiates as a slave (CPE) and starts to
send PTTP requests. When this protocol ends, the modem has the minimum information to
successfully connect to the backbone and execute DHCP and TFTP. The node then performs a
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 43 Version 1.1.0
DHCP request to get an IP configuration, and the name of the auto configuration file (option
18), as well as the TFTP server where the file is located (option 66). It then downloads the file
and configures the firmware accordingly.
Auto configuration no PTTP Boot (default)
In this auto configuration boot modality, the modem has been already configured to
successfully execute DHCP and TFTP so it skips PTTP.
NVRAM Boot
When a node starts in NVRAM mode, it collects all of the configured parameters from the
NVRAM memory and configures the firmware accordingly. There are some basic parameters
that are always configured in this mode:
• GENERAL_TYPE: Node type = HE, CPE, or TDREPEATER.
• GENERAL_IP_USE_DHCP: Use DHCP = YES or NO. If this parameter is set to NO, the IP
configuration parameters are configured from NVRAM.
All the other parameters are only configured if they have been downloaded from a file first, and
a GENERAL_USE_AUTOCONF = NO line was in that auto configuration file. This is equivalent to
performing a Save as Permanent.
PTTP Protocol
The PTTP (Parametric Translation Table Protocol) is used to transfer the translation table
between modems at booting. The translation table is comprised mainly of VLAN and OVLAN
parameters. When a modem boots using auto configuration mode with the current firmware
version, it skips PTTP requests and doesn’t run PTTP client unless it is set by Telnet CLI
command. The Telnet CLI command to enable PTTP client is “>ac pttpmode set 1”. This
command will write a byte in NVRAM in order that the next boot mode of the modem will start
with PTTP client.
When a modem boots in auto configuration mode, it starts sending PTTP requests. The modem
needs to know if it is booting in a network with VLANs before requesting an IP through DHCP.
For this reason, and because the LV node does not know if communication to the MV node is
through PLC or Ethernet, the FW to FW protocol uses a special PTTP MAC (01:80:C2:00:00:0E)
if communication is via Ethernet the LV node does not know the MAC of the MV node. The
PTTP petitions are performed in the following steps:
Step 1: A PTTP request is made without VLANs and waits for a response;
Step 2: It then switches to VLAN mode and makes a PTTP request using tag #1 (reserved
in the BPL network) and waits for a response;
Step 3: Returns to Step1.
When a node receives a packet with this PTTP MAC, the packet is sent to the FW. In
transmission, this request is forwarded to all active interfaces. Finally it will connect to a node
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 44 Version 1.1.0
that will transfer the translation table. The modem switches automatically to use or not to use
VLANs with the same configuration as the node sending the translation table. In this way all
modems configure themselves to use or not to use VLANs. This avoids having to write the use
or non use of VLANs in the NVRAM of all modems, a circumstance that can be extremely
convenient if an operator wants to change the entire network to use VLANs.
A modem must not perform PTTP (in Auto configuration no PTTP Boot mode) in the NVRAM in
the following two cases:
• If it is the first node of the network (directly connected to the backbone);
• If it is going to receive the translation table in the auto configuration file.
In the first instance, this node will transfer the translation table (included in the auto
configuration file) to other modems when requested, but in this case there is no other modem
from which to request this information because it will be the first node to know it.
To avoid using PTTP in the boot process, two methods are available:
1. Using the DHCP server (must be accessible through VLAN #1 or without VLAN), the PTTP
protocol can be skipped. In the DHCP reply, the server can supply the modem with the
management VLAN (in the event the modem boost in VLAN mode) or tell the modem
not to use VLANs;
2. Write a byte in the NVRAM using console. In this type of boot the modem reads its
NVRAM to check if it has to use or not to use VLANs and the Management VLAN (if
needed), requests an IP from the DHCP server and finally receives its auto configuration
file via TFTP.
The second method is not advisable, because the access to the console is poor while using PTTP
due to the change between VLAN and no VLAN modes. Method 1 should therefore be used if
possible.
To disable PTTP through DHCP (method 1), see the detail about DHCP client.
If no OVLANs or VLANs are going to be used in the network, the PTTP protocol can be disabled
in all of the modems. To disable PTTP manually in the next boot of a modem, follow the steps
below:
• Using a DHCP server, give an IP to the modem; this may take some time because,
sometimes, the modem will be sending DHCP requests with VLAN #1 and others without
VLAN active;
• Once the modem has an IP, log in to the console and execute the commands below
(NOTE: Due to VLAN switching, the console may seem to hang; if this occurs, log out
from the console and log in again):
o ac stop: Stops the auto configuration process (and also PTTP) and disables the
VLANs. It is advisable to execute this command first to work comfortably with
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 45 Version 1.1.0
the modem. This command does not write anything in the NVRAM, so it only
takes effect when the modem is reset;
o ac pttpmode set 0: Disables PTTP in the next boot, writing in the NVRAM. (“ac
pttpmode set 1” enables PTTP in the next boot, writing in the NVRAM);
o ac pttpmode get: Checks the PTTP state for the next boot, reading the NVRAM.
NOTE: DHCP should be used (if possible) to disable PTTP.
SNMP Agent
This release supports SNMP v1, without support to variable bindings for traps, and with a single
community name. The following MIBs are supported.
Table 6: MIB Tables
CORINEX MIB
MIB II RFC 1213
CORINEX ACCESS MIB
The available OIDs included in MIB II have been extended to all interfaces in the modem. The
default community names for SNMP read and write are set to ‘public’ and can be changed by
Telnet CLI command in admin mode.
FLASH Upgrade Protocol
The FLASH upgrade protocol allows provision for an upgrade of any of the binaries included in
the firmware release. A secure upgrade of the application and the loader binaries is ensured by
the existence of a backup image. This however does not provide any protection from the
download with a non running or incorrect application or loader.
BIST
The Built In Self Test (BIST) provided in this release executes by default the following tests:
Memories: The loader checks the data and address buses of the DRAM, as well as
the CRC of every FLASH section;
Ethernet: The Ethernet PHYs are set in loopback mode in order to test
communication. (disabled by default to reduce boot time);
RADIUS Client
The RADIUS client is compliant with RFC2865, except for the accounting functionalities that are
not included.
Multicast
There are two possible options to configure multicast features:
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 46 Version 1.1.0
If IGMP packet detection feature is enabled, the end point parses all upstream packets looking
for IGMP “join” and IGMP “leave” datagrams. All upstream traffic must be “sniffed” by the
internal processor by passing these packets up to firmware and checking whether they contain
IGMP control messages. When an IGMP control message is detected, the end point sends
control messages to all PLC network elements in the transmission chain (end point and access
point) to reconfigure all bridges to ensure that they are syndicated to the new multicast stream
and no traffic replication is made. This feature can be dynamically enabled or disabled.
It is possible to configure multicast by sending “special” frames to the modems, communicating
the creation of new bindings and the deletion of old ones. Encapsulation is the general method
to exchange data between PLC nodes using the LLC layer. Customers can determine what
information is exchanged, build and send their own messages, and allow actions to be taken
when these messages are received, if necessary. With this method, the external devices (not
PLC) “translate” the IGMP join/leave frames to MPP frames relayed to the modems which
configure the multicast bindings.
Factory Reset
Users can restore the modem to a default state if any problem occurs by the factory reset
command in Telnet CLI session.
PLC Application Description
The PLC application specification is described in the following subsections.
Modes Definition
The parameters that define a mode are as follows:
Central Frequency: Indicates where the mode is placed in the spectrum (in Hertz);
Bandwidth: This is the real bandwidth of the mode. It depends on the mode
bandwidth and power mask used;
Mode Bandwidth: It can be 10, 20 or 30 MHz defines the maximum usable
bandwidth in the mode;
PSD at the DAC Output (theoretical): Depends on the configuration of the internal
digital amplifiers/attenuators. The real value can be slightly different depending on
the external AFE and their configuration. The value provided is the theoretical
configured by firmware. The device characterization has demonstrated that the
measured PSD is very close to this theoretical value and also can be checked with
PSD at the line after AFE gain. The final power on the line depends on the gain of the
AFE;
Power Mask Definition: This is the power mask definition used in this mode;
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 47 Version 1.1.0
Maximum Physical Speed (achievable in this mode): The maximum bps depends on
the bandwidth mode, the power mask, and some other secondary parameters, such
as BPC thresholds, configuration for BER, maximum allowed SNR in the RD, etc. The
value provided is the theoretical value for the default modem configuration and
includes all overhead introduced in the physical layer.
Mode 1
Table 7: Mode 1
PARAMETER VALUE
Central Frequency 7.968.750 Hz
Bandwidth 10 MHz
Mode Bandwidth 10 MHz
PSD 72 dBm/Hz
Power Mask Definition Flat PM
Maximum Physical Speed 84 Mbps
Mode 2 (A1 MVG)
Table 8: Mode 2
PARAMETER VALUE
Central Frequency 18.437.500 Hz
Bandwidth 10 MHz
Mode Bandwidth 10 MHz
PSD 72 dBm/Hz
Power Mask Definition Flat PM
Maximum Physical Speed 84 Mbps
Mode 3 (A1 MVG)
Table 9: Mode 3
PARAMETER VALUE
Central Frequency 29.062.500 Hz
Bandwidth 10 MHz
Mode Bandwidth 10 MHz
PSD 72 dBm/Hz
Power Mask Definition Flat PM
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 48 Version 1.1.0
Maximum Physical Speed 84 Mbps
Mode 6
Table 10: Mode 6
PARAMETER VALUE
Central Frequency 19.062.500 Hz
Bandwidth 30 MHz
Mode Bandwidth 30 MHz
PSD 77 dBm/Hz
Power Mask Definition Flat PM
Maximum Physical Speed 205 Mbps
Mode 7
Table 11: Mode 7
PARAMETER VALUE
Central Frequency 7.031.250 Hz
Bandwidth 5 MHz
Mode Bandwidth 10 MHz
PSD 72 dBm/Hz
Power Mask Definition Lower Half Band
Maximum Physical Speed 42 Mbps
Mode 8
Table 12: Mode 8
PARAMETER VALUE
Central Frequency 12.812.500 Hz
Bandwidth 5 MHz
Mode Bandwidth 10 MHz
PSD 72 dBm/Hz
Power Mask Definition Lower Half Band
Maximum Physical Speed 42 Mbps
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 49 Version 1.1.0
Mode 10
Table 13: Mode 10
PARAMETER VALUE
Central Frequency 7.031.250 Hz
Bandwidth 10 MHz
Mode Bandwidth 10 MHz
PSD 72 dBm/Hz
Power Mask Definition Flat PM
Maximum Physical Speed 84 Mbps
Mode 13
Table 14: Mode 13
PARAMETER VALUE
Central Frequency 17.031.250 Hz
Bandwidth 30 MHz
Mode Bandwidth 30 MHz
PSD 77 dBm/Hz
Power Mask Definition Flat PM
Maximum Physical Speed 231 Mbps
Mode 2 (for A2 MV Gateway)
Table 15: Mode 2 – A2
PARAMETER VALUE
Central Frequency 17.500.000 Hz
Bandwidth 7 MHz
Mode Bandwidth 10 MHz
PSD 72 dBm/Hz
Power Mask Definition M11 PM
Maximum Physical Speed 60 Mbps
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 50 Version 1.1.0
Mode 3 (for A2 MV Gateway)
Table 16: Mode 3 – A2
PARAMETER VALUE
Central Frequency 27.031.250 Hz
Bandwidth 10 MHz
Mode Bandwidth 10 MHz
PSD 72 dBm/Hz
Power Mask Definition Flat PM
Maximum Physical Speed 84 Mbps
Power Mask and Notches
A dynamically configurable power mask allows the possibility to have fully configurable notches
in the desired frequencies. By default, the power mask configured will depend on the mode
used as described above. A different power mask can be configured through the auto
configuration process.
The Power Mask can be defined as part of the modem definition, as a regulation Power Mask,
defining the frequency bands and the attenuation, or a raw Power Mask applied directly to
every carrier.
The following default Power Mask definitions are included, and used in some modes.
No carrier is attenuated.
This Power Mask uses the Upper half carriers. The lower half carriers are completely
attenuated.
This Power Mask uses the lower half carriers. The upper half carriers are completely
attenuated. M11 PM
This Power Mask uses all carriers except the first 96 and the last 149 carriers, which are
completely attenuated. It is used for Mode 11.
This is similar (but slightly different) to the previous one. It is used for backward compatibility.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 51 Version 1.1.0
The IARU power mask is defined as the default value of the regulation Power Mask. IARU PM in
MDU gateway is composed of 9 notches and 19 notches in the rest of Corinex products. The
settings are listed in Tables below.
Table 17: IARU Power Mask Description in MDU Gateway
NOTCH NUMBER STARTING FREQ – ENDING FREQ NOTCHING (ATTENUATION/BW)
0 1800 2000 >30
1 3500 4000 >30
2 7000 7300 >30
3 10100 10150 >30
4 14000 14350 >30
5 18068 18168 >30
6 21000 21450 >30
7 24890 24990 >30
8 28000 29700 >30
Table 18: IARU Power Mask Description in all other products
NOTCH NUMBER STARTING FREQ – ENDING FREQ NOTCHING (ATTENUATION/BW)
0 1800 2000 >30
1 2850 3025 >30
2 3400 4000 >30
3 4650 4700 >30
4 5330 5405 >30
5 5450 5680 >30
6 6525 6685 >30
7 7000 7300 >30
8 8815 8965 >30
9 10005 10150 >30
10 11275 11400 >30
11 13260 13360 >30
12 14000 14350 >30
13 17900 17970 >30
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 52 Version 1.1.0
Table 18: IARU Power Mask Description in all other products
NOTCH NUMBER STARTING FREQ – ENDING FREQ NOTCHING (ATTENUATION/BW)
14 18068 18168 >30
15 21000 21450 >30
16 21924 22000 >30
17 24890 24990 >30
18 28000 29700 >30
The purpose of the power mask is to avoid an injection of signal that may disturb other
technologies. The IARU power mask can be applied by enabling the regulation Power Mask
without changing its initial definition. It will be applied to all relevant transmission modes. It is
configurable through Telnet CLI, auto configuration, and SNMP interface.
PLC Ports
The PLC ports are used as an index to refer to a modem that is visible through the power line.
Therefore ports are not only used for the master and its slaves, but also for any other visible
modem. When the limit of the number of ports is established as Nmax_ports
, this means that a
modem can see up to Nmax_ports
modems, all of which are not necessarily its slaves. The order in
which the ports are associated to modems is “first come first serve”. Also, every multicast MAC
address uses one entry in this table. There is an additional broadcast port to those regular
ports. The number of ports depends on the chip model used in Corinex products. The following
table shows the values for the current release.
Table 19: Maximum PLC Ports
Corinex product model Ports
Wallmount adapter 16
All desktop adapter,
MV, LV, and GPON BPL Gateway32
High Density Gateway 64
Boot Process
The start up process of the modems is described, step by step, using the scenario shown in
Figure 2 – one PC connected to a modem (modem 1, which will be the master) through the
Ethernet. A second modem (modem 2, CPE) is connected to the first modem through the power
line.
The PC contains all of the necessary servers: DHCP, TFTP, RADIUS, etc. The steps are going to be
described conceptually, so a detailed configuration of the server is not going to be provided.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 53 Version 1.1.0
The following tables describe the steps followed by the two modems; each row represents
some amount of elapsed time although this elapsed time can be different from row to row. To
indicate coincidences of time in the two modems, the cells in the tables are marked with a
(number). The tables are divided into two columns, one representing the application tasks and
the other the PLC layer.
Both modems are powered on. The boot process described above is completed, the OS is
running and the tasks are started.
Figure 18: Setup Configuration
Modem 1:
Table 20: Master Boot Description (Modem 1)
APPLICATIONS PLC
If STP is enabled, the ports must be in the forwarding
state before any packet can be sent through the port.
The STP task sends STP packets through all ports (PLC if
exists and Ethernet) to detect loops.
Modem starts as a slave.
The DHCP task sends DHCP request through all ports
(PLC if exists and Ethernet) asking for IP address.
Link Search starts looking for synchronization.
The PTTP task sends PTTP queries through all ports
(PLC if it exists and Ethernet).
Although there is no master, Modem 1 is
continuously changing the link trying to synchronize.
If PTTP is enabled, DHCP messages are sent with VLAN
(802.1Q) tag 1 and without a VLAN tag alternatively.
The DHCP server of the PC responds with the IP, PTTP
parameter, IP of the TFTP server, and configuration file
name.
The DHCP task responds with DHCPACK to the server,
stops sending DHCP request packets and passes the
parameters to the PTTP task (PTTP parameter) and to
the autoconfiguration task (TFTP server IP and
configuration file name).
The PTTP task stops sending packets.
The PTTP task acts according to the PTTP parameter,
gets the DHCP, thus VLAN configuration is set.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 54 Version 1.1.0
Table 20: Master Boot Description (Modem 1)
APPLICATIONS PLC
The modem is now accessible through TCP/IP, so tasks
like the console and SNMP are awaiting any input to
respond.
The Autoconfiguration task downloads the
configuration file using TFTP.
The Autoconfiguration task uses the parameters to
configure the modem.
The modem changes to master.
The link is changed to that of the autoconfiguration.
Autoconfiguration ends. The master starts sending access tokens, so slaves
can request access.
……………… ………………
One slave is detected.
The RADIUS task sends a RADIUS query for the MAC of
the slave.
Port solver protocol starts negotiating the ports.
The RADIUS task receives the authorization of the
RADIUS server with the desired profile for the user.
Port solver protocol (PSP) ends the port negotiation.
QoS and network parameters are configured for the
new user: bandwidth limitation in upstream and
downstream, VLANs, OVLANs, etc.
The token is shared between the master and the
slave, so the slave can send data packets.
The PTTP task receives a request from the slave.
The PTTP task sends an answer to the slave with the
translation table and the management VLAN.
Modem 2:
Table 21: CPE Boot Description (Modem 2)
APPLICATIONS PLC
If STP is enabled, the ports must be in the forwarding
state before any packet can be sent through the port.
The STP task sends STP packets through all ports (PLC if
exists and Ethernet) to detect loops.
Modem starts as a slave.
The DHCP task sends DHCP request through all ports
(PLC if exists and Ethernet) asking for IP.
Link Search starts looking for synchronization.
The PTTP task sends PTTP queries through all ports (PLC
if exists and Ethernet).
Synchronization is achieved in one of the links.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 55 Version 1.1.0
Table 21: CPE Boot Description (Modem 2)
APPLICATIONS PLC
If PTTP is enabled, the DHCP messages are sent with
VLAN (802.1Q) tag 1 and without a VLAN tag
alternatively.
Access protocol detects a master.
Access protocol answers access token of the master.
Port solver protocol starts negotiating ports.
Master grants the slave access.
Port solver protocol ends the port negotiation.
The STP task sets the port in forwarding, so packets can
go through PLC.
The PTTP task receives the translation table and the
management VLAN from the master.
The PTTP task stops sending packets.
Network parameters are configured in the ports
according to the PTTP information.
The DHCP server of the PC responds with the IP, IP of the
TFTP server and configuration file name.
The DHCP task responds with DHCPACK to the server,
stops sending DHCP request packets and passes the
parameters to the autoconfiguration task (TFTP server IP
and configuration file name).
The modem is now accessible through TCP/IP, so tasks
like the console and SNMP are awaiting any input to
respond.
The Autoconfiguration task downloads the configuration
file using TFTP.
The Autoconfiguration task uses the parameters to
configure the modem.
Autoconfiguration ends.
These operations result in an approximate time between reset and ping of (for a single pair of
modem):
Modem 1: 40 seconds
Modem 2: 140 seconds
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 56 Version 1.1.0
Constraints for Network Design
Two Master Visibility
Visibility between masters at physical level must be avoided. It is recommended to use spatial
reuse procedures to avoid the direct visibility between HEs in the same mode (power control
and sub mode).
Maximum Allowed PLC Ports
The capacity of PLC ports is 32 in most of the products including MV Gateway, MDU Gateway,
LV and GPON BPL Gateway basic model, Powerline Adapter, and CableLAN Adapter. For High
Density LV and GPON BPL Gateway, the capacity is 64.
Bridge Table Capacity
The maximum number of MAC address in the bridge table depends on the learning speed, the
ageing time, and the packet switch capacity. The data provided is measured with the default
configuration. To obtain the maximum capacity in the bridge table, increasing the ageing time is
recommended.
Bandwidth Limitation
The real bandwidth differs slightly from the specified limit and depends on a number of factors,
like traffic type, number of users, channel conditions, line conditions, etc.
Reconfiguration Time in MV MAC
The protocols and algorithms that allow the reconfiguration of ring topologies in a short time (a
few seconds) when a problem in the network appears are not included.
Regulation Power Mask
The regulation calculated power mask is slightly displaced to low frequencies. A correction to
high frequencies of around 20 KHz must be introduced in each notch definition to compensate
this effect. The notches of the IARU power mask are also calculated and they are also displaced.
As a result of this displacement, two of the notches included in IARU regulation are a few dB
less attenuated than required.
Number of hops in Time Division Domains
The number of hops supported in a Time Division Domain is ten. In networks were more hops
are needed, it is recommended to use several Frequency Division Domains.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 57 Version 1.1.0
ANNEX 2: AUTO CONFIGURATION MANUAL
Translation Table
The translation table contains information about the VLAN/OVLANs (in future releases more
parameters can be added) used for all master (HE) and TD repeater (TDR) nodes on MV or LV
lines. The auto configuration file is a parametric file, which means that, for example, the HE or
TDR knows, using the auto configuration file, that the VLAN DATA OPERATOR 1 is allowed, but
the CPE needs to know what the number of this VLAN DATA OPERATOR 1 is in the LV
equipment.
HE CPE HE CPE HE CPE HE TDR CPE HE
MV Line
HE
LV Line
TDR CPE CPE CPETDR
CPE CPE CPE
CPE CPECPE
TDR CPE
HEHE HE
A
B
C
D E
F G
Figure 19: Translation Table Example
In the example, Node A does not need any information about translations because no LV nodes
are hanging from Node A. Using TFTP, Node B gets the auto configuration file. In the file, Node
B gets the translations used in all LV nodes hanging from it. This translation information is
different from the translation information used by Node C and all LV nodes hanging from it. The
translation file is useful because Node D and Node F can have, if the network operator wants,
the same auto configuration file. This means, for example, that the data VLAN of Node D and
Node F is DATA VLAN OPERATOR 2, but the translation table that Node D gets from Node B
indicates that DATA VLAN OPERATOR 2 is VLAN 34 and the translation table Node F gets
indicates that it is VLAN 55. From the point of view of the network operator, this is easier than
having two files, one for Node D and one for Node F.
Transferring the Translation Table
By a status parameter in NVRAM (>ac pttpmode get), the MV node knows if it has to perform
PTTP or not. If it doesn’t need to perform PTTP, the modem determines whether it needs to use
VLAN and the Management VLAN. Via DHCP, it knows the IP and the auto configuration file.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 58 Version 1.1.0
And, finally, using TFTP, the MV node gets the auto configuration file with the translation table
information. To run nodes in VLAN environment, the first node must have VLAN setting in
NVRAM and stop running PTTP. All nodes except the first node must perform PTTP at boot time
(the default is PTTP off), but they do not have any VLAN information in the NVRAM. For this
reason, these nodes need VLAN information before they request an IP through DHCP, and they
also have to check if they are included in a VLAN network or not. As such, they perform PTTP as
explained before. PTTP is performed in a mixed state (with VLAN #1 and without VLAN). Finally,
one of the requests will succeed and the nearest node will reply, transferring the translation
table that includes:
The “USE VLAN ” Parameter to fix the VLAN mode.
Parameters related to VLAN (if needed), the main one being the Management VLAN. If
the parameter USE VLAN = 1, then the modem configures itself to use the Management
VLAN included in the translation table.
The “TRANSLATION_ROOTPATH_OVLAN” Parameter.
NOTE: VLAN 1 is reserved in an AV200 PLC network.
Example of a Translation Table
TRANSLATION_MNMT_VLAN =5
TRANSLATION_DATA_VLAN.1 =10
TRANSLATION_DATA_VLAN.2 =11
TRANSLATION_DATA_VLAN.3 =12
TRANSLATION_DATA_VLAN.4 =13
TRANSLATION_DATA_VLAN.5 =25
TRANSLATION_VOIP_VLAN.1 =30
TRANSLATION_VOIP_VLAN.2 =31
TRANSLATION_VOIP_VLAN.3 =32
TRANSLATION_VOIP_VLAN.4 =33
TRANSLATION_VOIP_VLAN.5 =45
TRANSLATION_ROOTPATH_OVLAN =77
The HE or TDR modem can be configured using this information and the auto configuration file.
When the CPE modem receives an auto configuration file with the following parameter:
VLAN_DATA_TAG =%DATA2
The correct value (11) is obtained from the translation table. There is one mandatory
parameter included in the translation table that is not configurable by the user in the auto
configuration file:
USE VLAN = [0|1]
If the modem is using VLANs, this parameter will be set to 1. Otherwise the parameter will be
set to 0. This information will be transferred when it receives a PTTP request from the next
modem either through PLC or Ethernet port. This parameter is what the modem performing the
PTTP request uses to know whether or not it needs to use VLAN.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 59 Version 1.1.0
Additional Information about Transferring PTTP
Be careful with PTTP in any network where a modem can connect with modems not belonging
to its network, because they can have different VLAN configurations (this may occur in MV
nodes or LV nodes that can communicate with MV nodes); the translation table transferred by
PTTP might be incompatible with the real network, in which the modem must remain. To solve
this situation (where a modem gets PTTP from a different master than it should), if the auto
configuration file downloaded by the modem includes the translation table, this information is
re written, which solves the problem. That the modem temporarily has a wrong translation
table is not a problem because with this information, the modem should be able to reach the
backbone, and thus the file to download. Be careful with one issue: only the parameters
declared explicitly in the file are changed in the translation table; the information that is not
declared will remain unchanged from the values that were received from PTTP. This should not
be a problem because if the information is not declared explicitly, it will not be used in its
network.
For example, modem “A” has its translation table with the following values and transfers this
information to modem “B”:
#Translation Table Modem A
TRANSLATION_MNMT_VLAN =250
TRANSLATION_DATA_VLAN.1 =21
TRANSLATION_DATA_VLAN.2 =11
TRANSLATION_DATA_VLAN.3 =12
TRANSLATION_DATA_VLAN.4 =13
TRANSLATION_DATA_VLAN.16 =25
TRANSLATION_ROOTPATH_OVLAN =666
After PTTP, modem “B” downloads its file, including the following translation table explicitly:
#Translation Table in the Autoconf file of Modem B
TRANSLATION_MNMT_VLAN =254
TRANSLATION_DATA_VLAN.1 =21
TRANSLATION_DATA_VLAN.3 =19
TRANSLATION_DATA_VLAN.4 =1333
TRANSLATION_DATA_VLAN.16 =22
TRANSLATION_ROOTPATH_OVLAN =666
Then the translation table that the modem will use (and the one that will transfer if it is
requested from another node) is:
#Translation Table resulting in Modem B
TRANSLATION_MNMT_VLAN =254
TRANSLATION_DATA_VLAN.1 =21
TRANSLATION_DATA_VLAN.2 =11
TRANSLATION_DATA_VLAN.3 =19
TRANSLATION_DATA_VLAN.4 =1333
TRANSLATION_DATA_VLAN.16 =22
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 60 Version 1.1.0
TRANSLATION_ROOTPATH_OVLAN =666
AV200 Nodes
In a BPL network, there are several types of nodes, depending on its position in the line. The
type of node is described using GENERAL_FW_TYPE, indicating the role of the modem in the
network (MV, LV or EU):
MV network: the GENERAL_FW_TYPE in this case should be MV.
LV network: all of them run LV Access MAC but there are two types depending the role
in the network: GENERAL_FW_TYPE will also be MV.
o LV nodes: this is all modems installed in transformer stations, meter rooms, etc.
They should be configured with GENERAL_FW_TYPE equal to LV
o EU (End User) nodes: these are the terminal nodes installed in customers’
homes. The configuration of this modem is always oriented to be protected
against customer actions, and this node should be associated to a QoS profile
contracted by the customer. The configuration will be the GENERAL_FW_TYPE
equal to EU.
The main differences between configuring a CPE modem as EU or LV are as follows:
Local VLAN configuration:
o The EU node will configure the Ethernet port as an ACCESS port, which means
that all traffic coming into the PLC network is untagged and the EU modem will
insert the tag.
o The LV node will configure the Ethernet port as TRUNK port, with a list of allowed
tags and all the tags in the translation table.
Remote Profile configuration: all the EU nodes have a profile known by their master, and
when a node enters the network, its master asks the RADIUS server for its own list, in
order to get the type of node and the profile assigned to this user. If the node is an:
o LV node: the profile is not taken into account. The configuration on the master
side for this node is setting the PLC port as trunk with all the allowed tags in the
translation table
o EU node: The configuration on the master side for this node depends on the
profile that describes the VLAN and OVLAN allowed for this user and the QoS
configuration.
Auto Configuration &Networking
VLAN Networks
VLAN Network Description
The network model is described as follows:
The PLC network is a switched network with different VLAN tags.
The firmware of all modems is inside the Management VLAN and VLAN 1. PLC
management protocols (PTTP, BPC, etc.) use VLAN 1, while high level management
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 61 Version 1.1.0
protocols (DHCP, TFTP, HTTP, NTP, SNMP, etc.) use the management VLAN configured
by the auto configuration procedure. The Management VLAN may be different in
different LV network.
The end user modem receives untagged traffic from the external interface and this
traffic is tagged with the correct Data VLAN according to the customer’s ISP. So there
can be more than one Data VLAN per LV network.
The end user modem generates traffic from VoIP, tagged with the correct VoIP VLAN
according to the customer’s VoIP operator. So there can be more than one VoIP VLAN
per LV cell.
It is possible to add private VLANs between specific customers that do not belong to any
ISP or voice operator. In this case, LAN trunks must be defined in the intermediary
equipment in order to allow all of that tagged traffic.
All of the traffic is tagged inside the PLC network. Each Corinex AV200 modem must
receive its VLAN configuration in the auto configuration file. In addition to this, and in
order to reduce the number of auto configuration files for end user (EU) modems (the
highest number), there will be a translation table transferred between modems which
contains information about the Management, Data VLANs used in an LV network.
No VLAN Networks
The use of VLANs is not mandatory but is advisable for privacy and security reasons.
Nevertheless, this privacy and security can be implemented with different tools, or simply to
establish a LAN.
In this kind of network, a modem will not have the problems of a VLAN network. By default the
modem will work without using VLAN. If PTTP is set enable manually, it can perform its PTTP
requests, switching between VLAN #1 and not using VLAN, and finally, a master will answer
with the translation table which will, at a minimum, contain the parameter “USE VLAN”. Once
the modem has received the translation table and does not need to configure anything more
regarding VLANs, it can complete the following steps: DHCP, TFTP and configuration.
OVLAN Configuration and Root Interface
The basic OVLAN configuration in AV200 devices avoids the visibility between customers
connected to the end user nodes in a simple way. All of the customer data packets in the same
LV cell are tagged with the Root path OVLAN. This tag is the only allowed tag in the entire path
to the backbone. In the path from the backbone to the rest of the network, the packets are
tagged with the ALL_VLAN tag (4095) by equipment that is connected to the backbone, and no
other tag is allowed in this path.
However, packets with the ALL_VLAN tag are not filtered. An example of the basic OVLAN
configuration is shown in the figure below. OVLAN filtering is done with egress lists. The lists are
shown between {…}. The root interfaces lists are always filled with the ROOTPATH OVLAN,
while the other interfaces are void allowed lists (only packets with the ALL_VLAN tag are
allowed). The result is that only the depicted downstream and upstream paths are allowed.
The root interface is discovered automatically as the root port of the spanning tree protocol, so
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 62 Version 1.1.0
it is mandatory to have the STP enabled for the OVLAN to work. When a node is going to be the
root node (the HE in the figure for instance) the root interface must be specified inside the
auto configuration file. It will always be one of the external interfaces.
Figure 20: Basic OVLAN configuration example
In all of the end users, the following configuration must be set:
OVLAN_ENABLE =yes
OVLAN_DATA_TAG =%ROOTPATH
The node that connects to the backbone must have:
GENERAL_IFACE_ROOT =EXTA
…
OVLAN_ENABLE =yes
OVLAN_DATA_TAG =4095
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 63 Version 1.1.0
Auto Configuration File
Introduction
An auto configuration file contains the configuration parameters needed by each node.
In the case of MV nodes or module 1 and 2 in MV Gateway, parametric values are not
necessary. These MV auto configuration files are usually specific for each MV circuit. Module 3
or LV access module in MV Gateway provides the translation table for LV repeater and end user
modems hanging from each MV Gateway. Each MV Gateway module 3 may need a particular
file depending on the network architecture of end point devices.
In case that all CPE/LV or CPE/EU nodes are designed to have a generic auto configuration file
same as others, no specific Quality of Service, VLAN/OVLAN configuration, or other parameters
are included in the auto configuration file. Thus, the HE or TDR nodes those CPE nodes are
hanging from must have parametric auto configuration files and pass the value to its hanging
node by PTTP transfer.
All CPE nodes can also be designed to use specific configuration files hanging from non generic
HE or TDR node. In this case, the system must maintain quite a number of auto configuration
files as many as the number of modems there are in the network and PTTP transfer is not
necessary.
Parameter Types
There are three types of parameters inside the auto configuration file:
1. Scalar: PARAMETER = value
2. List: PARAMTER.index1 = value
3. Table: PARAMETER.index1.index2 = value
The first valid index for lists and tables is 1.
Parameter Format
The format of the parameters is:
PARAMETER_LABEL [.x ] [.y ] = value for concrete parameter values
PARAMETER_LABEL [.x ][.y ] = %parametric_value for parametric parameter values
For example, the following parameter could be inside an end user auto configuration file:
VLAN_DATA_TAG = 452
or
VLAN_DATA_TAG = %DATA3
In the second case, the parametric value must be translated to its correct value using the
translation table. The translation table can be listed in the HE or TDR configuration it is hanging
from or either within its own configuration file in case if PTTP mode is off.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 64 Version 1.1.0
Supported Parameters in the Auto Configuration File
It is important that the order in which these parameters appear in the auto configuration file is
preserved. Any parameters that do not appear in the auto configuration files keep their default
values. Parsing is not case sensitive for parameter values (all values except ones like the RADIUS
shared secret where there is a difference between capital and lowercase letters).
General Parameters
GENERAL_USE_AUTOCONF = [yes|no ]
This is the first parameter in the auto configuration file. When this parameter is set to no, all of
the parameters in the file are stored in the NVRAM when the file is downloaded and the node
boots in NVRAM mode the next time. Default value: yes.
WARNING: when the modem boots in mode NVRAM, PTTP is not performed, so the Translation
Table does not get exchanged between different nodes. It is mandatory to add the translation
table to all the files in the network to configure the modem for booting from NVRAM.
GENERAL_TYPE = [HE|CPE|TDREPEATER ]
Configures the type of node. Default value: CPE.
GENERAL_FW_TYPE = [MV|LV|EU ]
Configures the firmware type of the node. This parameter affects the QoS and VLAN/OVLAN
configuration. Default value: LV.
GENERAL_AUTHENTICATION = [RADIUS|AUTHLIST|NONE]
Authentication method:
If RADIUS is selected, a RADIUS server is in charge of accepting new users and assigning
the profile and fw_type.
If AUTHLIST is selected, authentication is done by checking a list provided in the auto
configuration file. This option avoids the installation of a RADIUS server.
If NONE is selected, all of the users are accepted. Default value: NONE.
GENERAL_STP =[yes|no]
Enables/disables the Spanning Tree Protocol in the node. Default value: yes.
GENERAL_COMMON_STP_EXTA = [yes | no]
Enables/disables the Common STP feature in Ethernet interface (EXTA).
It only makes sense to use this parameter if VLANs are enabled. If it is set to “yes”, STP packets
will be released and accepted through EXTA without VLAN tags (even if VLANs are enabled).If
its value is “no”, STP packets will be released with the management VLAN tag (if VLANs are
active).
WARNING: With this parameter enabled, all packets without VLAN tags will be accepted
through EXTA.
GENERAL_IP_ADDRESS = <ddd.ddd.ddd.ddd>
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 65 Version 1.1.0
IP address of the modem (for the next boot if DHCP is disabled).
GENERAL_IP_NETMASK = <ddd.ddd.ddd.ddd>
IP netmask of the modem (for the next boot if DHCP is disabled).
GENERAL_IP_GATEWAY = <ddd.ddd.ddd.ddd>
IP default gateway of the modem (for the next boot if DHCP is disabled).
GENERAL_IP_USE_DHCP = [yes no]
The node does/does not use DHCP for the next boot if NVRAM mode is used.
GENERAL_SIGNAL_MODE = [1 14]
In HE: Signal mode for transmitting. The signal modes that are predefined in the firmware are
mode 1, 2, 3, 6, 7, 8, 10, and 13.
GENERAL_SIGNAL_MODE_LIST.x = [1 14 ]
In CPE and TDREPEATER: The list represents the allowed signal modes used by the Search Link
to find a master. (x=1…14). CPE and TDEREPEATER nodes that do not implement Search Link
can use this parameter, but only the last mode in the auto configuration file will be taken into
consideration. Default value: all the modes (1, 2, 3, 6, 7, 8, 10, and 13) are allowed.
GENERAL_SIGNAL_POWER_MASK = 00Ffa0(…)00FF
This parameter sets the powermask. Each pair of two characters represents the attenuation for
a carrier, so this parameter is 1536x2 characters long. Default value: 0A in all the carriers.
WARNING: this powermask is only set after getting the file. When the modem boots, it begins
transmitting without powermask. Thus it is not a secure parameter for avoiding interference
with HAM and shortwave radio.
GENERAL_SIGNAL_REG_POWERMASK_ENABLE = [yes | no]
This parameter enables or disables the use of the Regulation Power Mask (RPM). It is saved
always in NVRAM to be used at the next boot up without requiring the auto configuration file.
The RPM notches should be previously stored in NVRAM. By default, the NVRAM has shortwave
radio notches stored in memory. The notch configuration of the RPM can be changed.
GENERAL_IFACE_ROOT = EXTA
Root interface assignment. The root interface is the interface where the auto configuration file
is received. The system automatically obtains the root interface from the STP root port, but in
some cases, it must be assigned to EXTA (for example when the node is the STP root). The STP
bridge priority in AV200 modems has been modified in the 2 bytes reserved by the standard in
the following way:
0x9010 MV MASTER
0x9020 MV TDREPEATER
0x9030 LV MASTER
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 66 Version 1.1.0
0x9040 LV TDREPEATER
0x9050 LV CPE
The tree topology of the STP can be affected by FD repeaters because it is compounded by a
master modem. To avoid this, when the parameter GENERAL_IFACE_ROOT is defined, the 2
bytes reserved will change to:
((MV MASTER)– 0X8))=0X9008 for MV nodes
((LV MASTER)– 0X8))=0X9028 for LV nodes
In this way, a stand alone master will have preference over a master allocated in a FD repeater,
not dependent on a particular MAC.
AGC (Automatic Gain Control) Parameters
The following parameters must be handled with special care. A poor configuration can produce
loss of communication with the modem through PLC. Normally all of these settings are related
to a SIGNAL_MODE. Correct setting in one mode does not necessarily mean it is correct in
others.
AGC_TX_GAIN = [0|1]
Configures the transmission gain of the AV200 devices. The gains are separated by 12 dB.
Default value: 1.
WARNING: If the transmission gain is configured, it will remain configured, even if the mode
changes.
AGC_RX_ENABLE = [0|1]
Disable/enable the HW AGC. Default value: 1.
WARNING: If the AGC is disabled, it will remain disabled, even if the signal mode changes.
AGC_RX_FIX_GAIN = [0 7]
Fix reception gain, only valid if the HW AGC is disabled. Default value: 7.
WARNING: If the reception gain is fixed, it will remain fixed, even if the signal mode changes.
AGC_MAX_RX_GAIN = [0 7]
Fix the maximum reception gain for the HW AGC. Default value: 7.
WARNING: If the maximum reception gain is fixed, it will remain fixed, even if the signal mode
changes.
AGC_MIN_RX_GAIN = [0 7]
Fix the minimum reception gain for the HW AGC. Default value: 0.
WARNING: If the minimum reception gain is fixed, it will remain fixed, even if the signal mode
changes.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 67 Version 1.1.0
RADIUS Parameters
RADIUS_SERVER_IP = <ddd.ddd.ddd.ddd>
RADIUS server IP address.
RADIUS_SERVER_PORT = ddddd
RADIUS client UDP port.
RADIUS_SHARED_SECRET = <string>
RADIUS shared secret. It is limited to 16 characters.
All three parameters must be set in order for the RADIUS client to work properly.
Class of Service (CoS) Parameters
Using the auto configuration file, 2 classes of service criteria can be defined, assigning priorities
from 0 to 7.
COS_CUSTOM_CRITERION_OFFSET.i = [1 531 ]
Custom i criterion frame offset, in bytes (i =1,2).
COS_CUSTOM_CRITERION_PATTERN.i = 0xXXXXXXXXXXXXXXXX
Custom i criterion 8 byte pattern, in hexadecimal digits (i =1,2).
COS_CUSTOM_CRITERION_BITMASK.i = 0xXXXXXXXXXXXXXXX
Custom i criterion 8 byte bitmask, in hexadecimal digits (i =1,2).
COS_CUSTOM_CRITERION_CLASSES_OFFSET.i = [1 531]
Custom i criterion classes frame offset,in bytes (i =1,2).
COS_CUSTOM_CRITERION_CLASSES_BITMASK.i = 0xXXXXXXXXXXXXXXX
Custom i criterion classes 8 byte bitmask, in hexadecimal digits (i =1,2).
COS_CUSTOM_CRITERION_CLASS_PATTERN.i.j = 0xXXXXXXXXXXXXXXX
Custom i criterion j class 8 byte pattern, in hexadecimal digits (i=1,2;j =1 …8).
COS_CUSTOM_CRITERION_CLASS_PRIO.i.j = [0 7]
Custom i criterion j class priority (i=1,2 ;j =1 …8).
COS_CRITERION.k = [CUSTOM1|CUSTOM2|8021p|TOS|ARP|TCP_8021p|TCP_TOS]
k criterion definition (k = 1, 2). Assigns up to 2 criteria to classify traffic. There are two custom
criteria defined with the parameters above and some predefined criteria: 8021p is based on
VLAN tag priority field, TOS on the IP type of service field. The criteria TCP_8021p and TCP_TOS
are modifications of 8021p and TOS to prioritize, in addition, data TCP ACK packets to improve
the performance of bidirectional TCP flows; these two criteria are combined criteria that set
both criterion 1, 2 and the default priority. This means that TCP_8021p and TCP_TOS can only
be set as criterion 1 and in that case, the criterion 2 and the default priority will take fixed
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 68 Version 1.1.0
values defined by these criteria. The default criteria is TCP_8021p. Finally, the criterion ARP can
be used to prioritize the transmission of ARP packets.
COS_DEFAULT_PRIO = [0 7]
Configures the CoS default priority, that is, the priority assigned to packets that do not match a
criterion. Default value: 2.
Quality of Service (QoS) Parameters
QOS_ENABLE =[yes/no ]
This parameter enables/disables the quality of service in the node. If this parameter is set to no,
then no other parameters related to QoS are configured.
QOS_PRIOACK.prio+1 =[0|1 ]
This list configures the Layer 2 ACK protocol depending on the priority transmitted by the
modem (can be useful for those applications with tough settings in latency but not in PLR).If
several priorities are sniffed, the policy will be fixed by the maximum priority detected. Default
value: 1 for all priorities.
Slave Node Parameters (CPE)
QOS_MAX_TXPUT_TX = xxxx (in kbps)
Configures the maximum transmission throughput for that CPE/TDREPEATER.
QOS_UPBWLIMIT = [YES|NO ]
In a slave, limits its own transmission. Set to YES by default. If disabled, the user will transmit
data constantly. Every time it receives a data token, the slave will transmit limitless data back to
its master.
Master Node Parameters (HE or REPEATER)
QOS_LATENCY_STEP = [20 400] (in ms)
Configures the minimum latency step for the different slaves when using QoS.
Default value: 30
QOS_BW_POLICY = [0|1 ]
Configures the policy in which the QoS manages the excess of bandwidth. 0 is fair mode and 1 is
priority based mode. Default value: 1.
QOS_LATENCY.prio+1 = [1|2|4|8 ]
This list configures the latency for each priority level in QOS_LATENCY_STEP unities. Default
values are as follows:
QOS_LATENCY.1 =8
QOS_LATENCY.2 =8
QOS_LATENCY.3 =4
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 69 Version 1.1.0
QOS_LATENCY.4 =4
QOS_LATENCY.5 =4
QOS_LATENCY.6 =2
QOS_LATENCY.7 =1
QOS_LATENCY.8 =8
Profile Parameters
To define a profile, at least five parameters are required. Any that are not defined will remain at
their default values:
PROFILE_MAX_TXPUT_TX.i = xxxx (in kbps)
Maximum transmission throughput (from the slave point of view: upstream) for users with
profile i. Default value: 512.
PROFILE_MAX_TXPUT_RX.i = xxxx (in kbps)
Maximum reception throughput (from the EU point of view: downstream) for users with profile
i. Default value: 512.
PROFILE_PRIORITIES.i = [0x00 0xFF]
Priorities allowed for a user of profile i. Each bit represents a priority. The default value is 0x85,
so priorities 7,2 and 0 are allowed. To include another priority, set the appropriate bit in the
profile priorities flag. The maximum and minimum priorities are always set even if they are not
configured (0x81).
PROFILE_UPBWLIMIT.i = [YES|NO]
In a master or a TD repeater, limit the upstream (slave’s transmission) for users with profile i. if
disabled, the user will receive tokens constantly. Whenever the master node has transmitted all
required tokens to all the slaves with upstream bandwidth limited, then it will transmit tokens
to the slaves without upstream bandwidth limited until the other slaves can receive tokens
again. Default value: yes.
PROFILE_DWBWLIMIT.i = [YES|NO]
In a master or a TD repeater, limit the downstream (slave’s reception)for users with profile i. If
disabled, the master node will never stop transmitting data to that user. Whenever the master
node has transmitted all required data to all slaves with downstream bandwidth limited, then it
will transmit data to the slaves without downstream bandwidth limited until the rest of the
slaves can receive again. Default value: yes.
The following parameters can be added to the profile definition but they are not mandatory if
VLAN or OVLAN is not enabled:
PROFILE_MNMT_VLAN.i = [2 4093] ||%<PARAMETRIC VALUE>
Management VLAN for that user.
PROFILE_DATA_VLAN.i = [2 4093] ||%<PARAMETRIC VALUE>
Data VLAN for that user.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 70 Version 1.1.0
PROFILE_VOIP_VLAN.i = [2 4093] ||%<PARAMETRIC VALUE>
VoIP VLAN for that user.
PROFILE_VLAN_ADD_TAG.i.j = [2 4093] or parametric
This parameter is of table type. For the user of profile i, up to 16 VLANs can be defined in the
filter list. When the list is ALLOWED, these tags are added to the base configuration. Otherwise,
if the list is changed to FORBIDDEN, the base tags are removed and, for security reasons, only
the tags defined here are included.
PROFILE_VLAN_TAGGED_ONLY_IFACE_USER.i = [yes/no]
For the user of profile i, this parameter indicates whether or not to drop input packets without
a VLAN tag from the user with profile i (PL interface).
PROFILE_VLAN_OUTFORMAT_TAG_IFACE_USER.i = [yes/ no]
For the user of profile i, this parameter indicates whether or not to send packets with a VLAN
tag to the user interface with this profile.
PROFILE_VLAN_IS_ALLOWED_IFACE_USER.i = [yes/no]
Indicates if the tags on the list are allowed or forbidden for the user with profile i. When the list
is ALLOWED the tags are added to the base configuration; when the list is FORBIDDEN, the list is
reset and only tags defined with PROFILE_VLAN_ADD_TAG will be in the list.
PROFILE_OVLAN_ADD_TAG.i.j = [2 4094] or parametric
This parameter is of table type. For the user of profile i, up to 16 OVLANs can be defined in the
filter list. When the list is ALLOWED, these tags are added to the base configuration. Otherwise,
if the list is changed to FORBIDDEN, the base tags are removed and, for security reasons, only
the tags defined here are included.
PROFILE_OVLAN_TAGGED_ONLY_IFACE_USER.i = [yes/no]
For the user of profile i, this parameter indicates whether or not to drop input packets without
an OVLAN tag from the user with profile i (PL interface).
PROFILE_OVLAN_OUTFORMAT_TAG_IFACE_USER.i = [yes/no]
For the user of profile i, this parameter indicates whether or not to send packets with a VLAN
tag to the user interface with this profile.
PROFILE_OVLAN_IS_ALLOWED_IFACE_USER.i = [yes/no]
Indicates if the tags on the list are allowed or forbidden for the user with profile i. When the list
is ALLOWED, the tags are added to the base configuration; when the list is FORBIDDEN, the list
is reset and only tags defined with PROFILE_OVLAN_ADD_TAG will be in the list.
The maximum number of profiles is the maximum number of PLC ports allowed.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 71 Version 1.1.0
Translation Table Parameters
TRANSLATION_MNMT_VLAN = [2 4093]
Translation table management VLAN tag.
TRANSLATION_DATA_VLAN.i = [2 4093]
Translation table data operator i VLAN tag. Up to 16 tags.
TRANSLATION_VOIP_VLAN.i = [2 4093]
Translation table VoIP operator i VLAN tag. Up to 16 tags.
TRANSLATION_ROOTPATH_OVLAN = [2 4094]
Translation table root path OVLAN.
WARNING: When the modem boots in NVRAM mode, PTTP is not performed. The Translation
Table is not exchanged between the PLC nodes. It is mandatory to add the translation table to
all the configuration files (MV, LV and EU) to configure any modem for booting from NVRAM.
VLAN Parameters
VLAN_ENABLE = [yes|no]
Enables/disables the use of VLAN.
WARNING: Normally this parameter is not needed because the modem automatically discovers
the use of VLAN, but it is necessary when booting from NVRAM.
VLAN_MNMT_TAG = [2 4093] ||%<PARAMETRIC VALUE>
Management VLAN tag of high level FW management protocols. Often taken from the
translation table.
WARNING: this parameter must be added to all auto configuration files (MV, LV or EU modems)
when modems are set to boot up from NVRAM on the next reset.
VLAN_MNMT_PRIO = [0 7]
Configures the VLAN priority for the high level management (FW) packets.
VLAN_DATA_TAG = [2 4093] ||%<PARAMETRIC VALUE>
Parameter for EU nodes. Configures the VLAN tag for the data packets (packets coming from
the external interfaces).
VLAN_DATA_PRIO = [0 6]
Parameter for EU nodes. Configures the VLAN priority for the data packets (packets coming
from the external interfaces).
VLAN_TRUNK.i = [2 4093]
Parameter for LV and MV nodes. Configures a list of VLAN trunks, different from those in the
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 72 Version 1.1.0
translation table, and which must be allowed in the node interfaces. It is necessary to configure
these trunks for private VLANs between EUs in all intermediary equipment.
VLAN_RETAG_EXTA_SRC = [0 |2 4095]
VLAN retagging: External (Ethernet) interface A (EXTA)source tag. When a packet comes from
the EXTA, with tag specified at this parameter, it is sent through PLC with tag specified at
VLAN_RETAG_EXTA_DST parameter. With 0, the retagging is disabled in the EXTA interface.
VLAN_RETAG_EXTA_DST = [0 |2 4095]
VLAN retagging:External (Ethernet)interface A (EXTA)destination tag.
When a packet comes from PLC, with tag specified at this parameter, may be sent through
EXTA, tag will be changed to match that indicated at VLAN_RETAG_EXTA_SRC. When set to 0,
the retagging is disabled in the EXTA interface.
OVLAN Parameters
The OVLAN parameters are used to configure the basic OVLAN configuration, which prevents
customers from seeing each other in the access network.
OVLAN_ENABLE = [yes|no]
Enables/disables the use of OVLAN filtering.
OVLAN_DATA_TAG = [2 4094] ||%ROOTPATH_OVLAN
OVLAN tag assigned to the packets coming from the external interfaces. It should be the same
as in the translation table to perform the basic OVLAN operation in all equipment, except the
one connected to the backbone, which will have the ALL_VLAN tag (4095).
OVLAN_TRUNK.i = [2 4094]
Parameter for LV and MV nodes. Configures a list of OVLAN trunks, different from the one in
the translation table, which must be allowed in the node interfaces. It is necessary to configure
these trunks for private OVLANs between EUs in all intermediary equipment.
Access Protocol Parameters
AP_MIN_NUMBER_HOPS = [0|1|…]
Configures the minimum number of hops to the HE from a slave.0 means that no extra hop
must be taken to reach the HE, so the slave always connects to the HE directly (if possible).1
means 1 extra hop is forced to reach the HE, that is, the equipment will connect to a TD
repeater (if possible).
AP_FORBID_MASTER.i = 0xXXXXXXXXXXXX
List of forbidden masters for a given slave by MAC address.
AP_PREFER_MASTER = 0xXXXXXXXXXXXX
Preferred master for a given slave by MAC address. This parameter is useful because the slave
will try to connect to the Preferred Master if it is present. If not, it will connect to any other
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 73 Version 1.1.0
available master.
AP_FIX_MASTER = 0xXXXXXXXXXXXX
Fixed master for a given slave by MAC address. The slave will only connect to this FIXED master.
WARNING: This parameter can be dangerous because the slave cannot then connect to other
masters.
AP_CHECK_BEST_MASTER_ENABLE = [yes | no]
Enables/disables a periodical check of the best master in the access protocol. Default value:
yes.
AP_CHECK_BEST_MASTER_PERIOD = <time>
Configures the period time of the best master check (in minutes).Default value: 180.
AP_CURRENT_MASTER_MIN_BPS = <bps_thr>
Minimum bits per symbol with the current master that forces a change of master in check best
master phase. Default value: 1750.
AP_NEW_MASTER_MIN_BPS = <bps_thr>
Minimum bits per symbol with the new master that allows a change of master in check best
master phase. Default value: 1750.
ACCESSP_AUTHLIST_MAC.i = 0xXXXXXXXXXXXX
List of allowed MAC addresses. The length of the list is 128 (i=1 …128).
ACCESSP_AUTHLIST_PROFILE.i = [1 16]
List of profiles associated with a MAC address. The length of the list is 128 (i=1 …128). Default
value: 1.
ACCESSP_AUTHLIST_FWTYPE.i = [MV| LV| EU]
List of FWTYPE. The length of the list is 128 (i=1 …128).Default value: LV.
STP Parameters
STP_PRIO = [0 65535 ]
Configures the 2 bytes added to the MAC used by the STP standard to define the root path.
Default values:
0x9010 MV MASTER
0x9010 MV MASTER
0x9020 MV TDREPEATER
0x9030 LV MASTER
0x9040 LV TDREPEATER
0x9050 LV CPE
STP_PORT.i = [EXTA|EXTB|PLC ]
The following two parameters will be configured depending on this one. For instance if
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 74 Version 1.1.0
STP_PORT.2 = EXTA, then STP_PORT_PRIO.2 =xx and STP_PORT_COST.2 =xxx are referred to
EXTA. Only EXTA and PLC can be configured. If PLC is selected, the priority and cost will be
changed for all PLC ports.
STP_PORT_PRIO.i = [0 255]
Priority of the port (necessary if costs are equal).Default value (for ETHA and PLC): 80.
STP_PORT_COST.i = [0 65535]
Cost of the port. Default values:
ETHA = 2000000
ETHB = 2000000
PLC = 4000000
STP_HELLO_TIME = [10 40]
Hello time expressed in decisecond. Default value: 20 decisecs.
STP_MAX_AGE = [60 400 ]
Max.age time expressed in decisecs. Default value: 200 decisecs.
STP_FORWARD_DELAY = [40 300]
Forward delay time expressed in decisecs. Default value: 150 decisecs.
STP_FRONTIER = [NONE|EXTA|EXTB]
Drops all STP packets in an external port. Default value: NONE.
STP_MODE = [STP|RSTP]
STP protocol version: Common (802.1d) or Rapid (802.1w).Default value: RSTP.
STP_PTP_EXTA = [0|1]
Configure the EXTA interface to be treated as point to point.
MAC Ingress Filtering Parameters
MAC_INGRESS_FILTERING_ENABLE = [yes | no]
Enables the use of MAC ingress filtering. If enabled, the modem filters by the source MAC
address. If the source MAC of the frame coming from Ethernet is not in the list, the frame is
discarded. Default value: no.
MAC_INGRESS_FILTERING_MAX_ALLOWED = [1 4]
Sets length of the MAC filtering ingress list. The maximum is 4 instead of 5 to allow the WISC
MAC to be in the FW; this is done automatically.
MAC_INGRESS_FILTERING_MODE = [FIXED|AUTO]
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 75 Version 1.1.0
If FIXED: Enables the INGRESS MAC FILTERING and registers the list of
MAC_INGRESS_FILTERING_FIXED_MAC (the following parameter) in the list, up to the
MAC_INGRESS_FILTERING_MAX_ALLOWED.
If AUTO: Deletes all MACs registered in the bridge associated to ETH ports, and sets the
AUTO flag. When the bridge receives a new MAC coming from ETH, it registers it in the
INGRESS_MAC_FILTERING list.
If the length of this list reaches the maximum allowed then it enables the
MAC_INGRESS_FILTERING.
MAC_INGRESS_FILTERING_FIXED_MAC.i = 0xXXXXXXXXXXXX
Only valid in FIXED mode, up to 4 MACs. If the MAX is set to lower than 4, then only the first
MACs until the length of MAX is completed are registered.
Custom VLAN/OVLAN Parameters
USE_CUSTOM_VLAN_OVLAN = [yes/no]
This parameter enables other VLAN/OVLAN parameters. Default value: no.
If set to no, the previous configuration is used. If set to yes, it will configure the parameters that
are set in the auto configuration file. When set to yes, the connection will be lost if the new
parameters are not properly configured in the auto configuration file. It is necessary to
carefully specify several parameters, or else no connection will be possible between the
modems.
As a general rule, this configuration overrides the basic VLAN/OVLAN Configuration. In order to
decrease the risk of losing the connection, the VLAN/OVLAN filtering follows these rules:
When the list is ALLOWED, the tags specified here are added to the existing ones. This solution
simplifies the configuration and decreases the risk of miss configuration.
When the list is FORBIDDEN, the lists are reset before inserting the tags specified here, for the
same reasons. The VLAN/OVLAN custom configuration must be complemented with the profile
parameters referring to VLAN/OVLAN to configure interfaces different from EXTA, ROOT and
OTHERS.
Custom VLAN Parameters
VLAN_FILTER_INGRESS =[yes/no]
VLAN filtering using input interface. By default only egress filtering (output interface) is
performed. Default value: no.
VLAN_TAGGED_ONLY_IFACE_ROOT = [yes/no]
Drops packets without a VLAN tag entering the root interface (IFACE_ROOT).
Default value: no.
VLAN_TAGGED_ONLY_IFACE_EXTA = [yes/no]
Drops packets without a VLAN tag entering external (Ethernet) interface. Default value: no.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 76 Version 1.1.0
VLAN_TAGGED_ONLY_IFACE_OTHER = [yes/no]
Drops packets without a VLAN tag entering other interfaces (IFACE_OTHER). Default value: no.
VLAN_OUTFORMAT_TAG_IFACE_ROOT = [yes/no]
Sends packets with a VLAN tag to the root interface (IFACE_ROOT) Default value: yes.
VLAN_OUTFORMAT_TAG_IFACE_EXTA = [yes / no]
Sends packets with a VLAN tag to external (Ethernet) interface. Default value: yes.
VLAN_OUTFORMAT_TAG_IFACE_OTHER = [yes/no]
Sends packets with a VLAN tag to other interfaces (IFACE_OTHER). Default value: yes.
VLAN_PVID_PL = [2 4095]
802.1Q VLAN tag for tagging untagged packets from the powerline interface (PL). Default value:
0.
VLAN_PVID_EXTA = [2 4095]
802.1Q VLAN tag for tagging untagged packets from the external interface (EXTA).
If EU, default value: VLAN_DATA_TAG. If LV or MV, default value: 0.
VLAN_PVID_FW = [2 4095]
802.1Q VLAN tag for tagging untagged packets from the firmware interface (FW). Default value:
1.
VLAN_DEFAULT_PRIO_PL = [0 7]
802.1p priority for tagging untagged packets from the powerline interface (PL). Default value: 0.
VLAN_DEFAULT_PRIO_EXTA = [0 7]
802.1p priority for tagging untagged packets from external (Ethernet) interface A (EXTA).
If EU, default value: VLAN_DATA_PRIO. Default value: 0.
VLAN_DEFAULT_PRIO_FW = [0 7]
802.1p priority for tagging untagged packets from the firmware interface (FW).
Default priority: 0.
VLAN_IS_ALLOWED_IFACE_ROOT = [yes/no]
Private VLANs list: Root interface (IFACE_ROOT) list is an allowed tag list if YES or forbidden if
NO. Default value: yes.
VLAN_LIST_IFACE_ROOT. i = [2 4095]
Private VLANs list: Root interface (IFACE_ROOT) tag list. Up to 16 values can be configured.
VLAN_IS_ALLOWED_IFACE_EXTA = [yes / no]
Private VLANs list: External (Ethernet) interface list is an allowed tag if YES or forbidden if NO.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 77 Version 1.1.0
Default value: yes.
VLAN_LIST_IFACE_EXTA. i = [2 4095 ]
Private VLANs list: External (Ethernet) interface tag list. Up to 16 values can be configured.
Custom OVLAN Parameters
OVLAN_FILTER_INGRESS = [yes/no ]
OVLAN filtering using input interface. By default only egress filtering (output interface) is
performed. Default value: no.
WARNING: Enabling the OVLAN ingress filtering is very dangerous because the basic OVLAN
configuration relies on avoiding ingress filtering. There are empty lists in the downstream
interfaces, which imply that no packet will pass if ingress filtering is activated and the OVLAN
root path tag is not allowed. Enabling ingress filtering requires a complete OVLAN
configuration.
OVLAN_TAGGED_ONLY_IFACE_ROOT = [yes/no]
Drops packets without an OVLAN tag entering the root interface (IFACE_ROOT).
OVLAN_TAGGED_ONLY_IFACE_EXTA = [yes/no]
Despite the name of this parameter, the meaning of it is different for Ethernet interfaces. If set
to NO, it drops packets with an OVLAN tag entering external (Ethernet) interface A. If set to YES,
it accepts packets tagged with an OVLAN tag. Default value: no.
Warning: if the root port is an Ethernet port, the meaning of the parameter
OVLAN_TAGGED_ONLY_IFACE_ROOT is the same as the parameters described earlier,
OVLAN_TAGGED_ONLY_IFACE_EXTA.
OVLAN_TAGGED_ONLY_IFACE_OTHER = [yes/no]
Drops packets without an OVLAN tag entering other interfaces (IFACE_OTHER).
OVLAN_OUTFORMAT_TAG_IFACE_ROOT = [yes/no]
Sends packets with an OVLAN tag to the root interface (IFACE_ROOT). Default value: yes.
OVLAN_OUTFORMAT_TAG_IFACE_EXTA = [yes/no]
Sends packets with an OVLAN tag to external (Ethernet) interface. Default value: no.
OVLAN_OUTFORMAT_TAG_IFACE_OTHER = [yes/no]
Sends packets with an OVLAN tag to other interfaces (IFACE_OTHER). Default value: yes.
OVLAN_PVID_PL = [2 4095]
OVLAN tag for tagging untagged packets from the powerline interface (PL). Default value: 0.
OVLAN_PVID_EXTA = [2 4095]
OVLAN tag for tagging untagged packets from external interface (EXTA). If EU, the default value
is equal to OVLAN_DATA_TAG. If LV or MV, default value is 0.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 78 Version 1.1.0
OVLAN_PVID_FW = [2 4095]
OVLAN tag for tagging untagged packets from the firmware interface (FW). Default value: 0.
OVLAN_IS_ALLOWED_IFACE_ROOT = [yes/no]
Private OVLANs list: Root interface (IFACE_ROOT) list is an allowed tag if YES, or forbidden if
NO. Default value: yes.
OVLAN_LIST_IFACE_ROOT.i = [2 4095]
Private OVLANs list: Root interface (IFACE_ROOT) tag list. Up to 16 values can be configured.
OVLAN_IS_ALLOWED_IFACE_EXTA = [yes/no]
Private OVLANs list: External (Ethernet) interface list is an allowed tag if YES, or forbidden if NO.
Default value: yes.
OVLAN_LIST_IFACE_EXTA.i = [2 4095]
Private OVLANs list: External (Ethernet) interface tag list. Up to 16 values can be configured.
SNMP Parameters
SNMP_TRAP_IP_ADDRESS = <ddd.ddd.ddd.ddd>
Configures the IP address to which traps are sent when produced.
SNMP_TRAP_COMMUNITY_NAME = <community name>
Configures the trap community access. This parameter is a string with maximum length 23
characters.
Multicast Protocol Parameters
MCAST_IGMP_SNOOPING = [yes / no]
Configures the IGMP SNOOPING feature in a node. If enabled the node is able to translate IGMP
messages to MPP SNAP messages that can be propagated through the PLC network. Default
value: no.
IMPORTANT: This parameter must be set to Yes ONLY in CPEs connected to a STB. Modems
with the IGMP Snooping feature enabled have the upstream throughput limited because all
frames incoming from the external interface are parsed by the firmware. IGMP frames are
encapsulated into MPP frames and sent through the PLC network and the rest are regenerated
and resent. The maximum upstream throughput (from the external interface to the PLC
network) measured is 120 packets/second with a 0% packet loss rate. (this is independent of
packet size). The bigger the packet size, the bigger the upstream throughput measured in
megabits/sec.
MCAST_MPP2IGMP_PORT = [NONE | EXTA | ROOT]
Configures the translation of MPP SNAP message to IGMP format. The destination of IGMP
messages is specified in the parameter. If “none” is configured no translation is performed,
otherwise the destination interface is the one specified (“root” means spanning tree root).
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 79 Version 1.1.0
Default value: none.
Example of use: In the HE that is connected to the network where the video server exists,
configure MCAST_MPP2IGMP_PORT = root. In intermediate nodes (including the HE of
Frequency Division Repeaters), leave MCAST_MPP2IGMP_PORT = none.
Corinex MVG/LVG Parameters
NODE_NUMBER = [1 … 99]
For MV Gateway identity. This line must be included in the second line of auto configuration file
to be loaded in the MV Gateway. If it is not included, the modem will not be successfully
configured.
PLC_SIGNAL_COUPLING = [COAX | LV | IND]
To allow coupling the BPL signal into coaxial, low voltage line, or independent port. Available in
module 3 of MV Gateway for COAX or LV. Available in Low Voltage Access Gateway and GPON
BPL Gateway for COAX or IND. IND in basic model is provided through pin 3 and 4 on the power
socket. IND in the model with integrated coupler is provided through an individual 4 pin signal
port.
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 80 Version 1.1.0
ANNEX 3: EXAMPLE OF CONFIGURATION FILES
Master Access Mode 6 (HE/LV 6) output to coaxial port
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = HE
GENERAL_FW_TYPE = LV
GENERAL_IP_ADDRESS = 192.168.0.100
GENERAL_IP_NETMASK = 255.255.255.0
GENERAL_IP_GATEWAY = 192.168.0.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
GENERAL_AUTHENTICATION = NONE
GENERAL_SIGNAL_MODE = 6
SIGNAL_SUB_MODE = 0
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = COAX
Master Access Mode 1 (HE/LV 1) output to pin 3 and 4
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = HE
GENERAL_FW_TYPE = LV
GENERAL_IP_ADDRESS = 192.168.0.100
GENERAL_IP_NETMASK = 255.255.255.0
GENERAL_IP_GATEWAY = 192.168.0.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
GENERAL_AUTHENTICATION = NONE
GENERAL_SIGNAL_MODE = 1
SIGNAL_SUB_MODE = 0
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = IND
Master Access Mode 2 (HE/LV 2) output to pin 3 and 4
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = HE
GENERAL_FW_TYPE = LV
GENERAL_IP_ADDRESS = 192.168.0.100
GENERAL_IP_NETMASK = 255.255.255.0
GENERAL_IP_GATEWAY = 192.168.0.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 81 Version 1.1.0
GENERAL_AUTHENTICATION = NONE
GENERAL_SIGNAL_MODE = 2
SIGNAL_SUB_MODE = 0
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = IND
Master Access Mode 3 (HE/LV 3) output to pin 3 and 4
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = HE
GENERAL_FW_TYPE = LV
GENERAL_IP_ADDRESS = 192.168.0.100
GENERAL_IP_NETMASK = 255.255.255.0
GENERAL_IP_GATEWAY = 192.168.0.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
GENERAL_AUTHENTICATION = NONE
GENERAL_SIGNAL_MODE = 3
SIGNAL_SUB_MODE = 0
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = IND
Slave End User (CPE/EU) output to pin 3 and 4
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = CPE
GENERAL_FW_TYPE = EU
GENERAL_IP_ADDRESS = 192.168.0.101
GENERAL_IP_NETMASK = 255.255.0.0
GENERAL_IP_GATEWAY = 192.168.0.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
GENERAL_SIGNAL_MODE_LIST.1 = 1
GENERAL_SIGNAL_MODE_LIST.2 = 2
GENERAL_SIGNAL_MODE_LIST.3 = 3
GENERAL_SIGNAL_MODE_LIST.4 = 6
GENERAL_SIGNAL_MODE_LIST.5 = 7
GENERAL_SIGNAL_MODE_LIST.6 = 8
GENERAL_SIGNAL_MODE_LIST.7 = 10
GENERAL_SIGNAL_MODE_LIST.8 = 13
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = IND
TD Repeater (TDR/LV) output to pin 3 and 4
GENERAL_USE_AUTOCONF = YES
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 82 Version 1.1.0
GENERAL_TYPE = TDREPEATER
GENERAL_FW_TYPE = LV
GENERAL_IP_ADDRESS = 192.168.0.103
GENERAL_IP_NETMASK = 255.255.0.0
GENERAL_IP_GATEWAY = 192.168.0.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
GENERAL_SIGNAL_MODE_LIST.1 = 1
GENERAL_SIGNAL_MODE_LIST.2 = 2
GENERAL_SIGNAL_MODE_LIST.3 = 3
GENERAL_SIGNAL_MODE_LIST.4 = 6
GENERAL_SIGNAL_MODE_LIST.5 = 7
GENERAL_SIGNAL_MODE_LIST.6 = 8
GENERAL_SIGNAL_MODE_LIST.7 = 10
GENERAL_SIGNAL_MODE_LIST.8 = 13
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = IND
Master Access Mode 6 (HE/LV 6) with VLAN and OVLAN parameters
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = HE
GENERAL_FW_TYPE = LV
GENERAL_IP_ADDRESS = 192.168.0.100
GENERAL_IP_NETMASK = 255.255.255.0
GENERAL_IP_GATEWAY = 192.168.0.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
GENERAL_AUTHENTICATION = AUTHLIST
GENERAL_SIGNAL_MODE = 6
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = IND
SIGNAL_SUB_MODE = 0
TRANSLATION_MNMT_VLAN = 5
TRANSLATION_DATA_VLAN.1 = 101
TRANSLATION_DATA_VLAN.2 = 102
TRANSLATION_ROOTPATH_OVLAN = 77
QOS_ENABLE = YES
QOS_BW_POLICY = 1
COS_CRITERION.1 = TCP_8021p
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 83 Version 1.1.0
OVLAN_ENABLE = YES
OVLAN_DATA_TAG = 4095
PROFILE_MAX_TXPUT_TX.1 = 4096
PROFILE_MAX_TXPUT_RX.1 = 4096
PROFILE_PRIORITIES.1 = 0xFF
PROFILE_UPBWLIMIT.1 = NO
PROFILE_DWBWLIMIT.1 = NO
PROFILE_MNMT_VLAN.1 = %MNMT
PROFILE_FWTYPE.1 = EU
PROFILE_MAX_TXPUT_TX.2 = 512
PROFILE_MAX_TXPUT_RX.2 = 1024
PROFILE_PRIORITIES.2 = 0xFF
PROFILE_UPBWLIMIT.2 = NO
PROFILE_DWBWLIMIT.2 = NO
PROFILE_MNMT_VLAN.2 = %MNMT
PROFILE_DATA_VLAN.2 = %DATA1
PROFILE_FWTYPE.2 = EU
PROFILE_MAX_TXPUT_TX.3 = 1024
PROFILE_MAX_TXPUT_RX.3 = 2048
PROFILE_PRIORITIES.3 = 0xFF
PROFILE_UPBWLIMIT.3 = NO
PROFILE_DWBWLIMIT.3 = NO
PROFILE_MNMT_VLAN.3 = %MNMT
PROFILE_DATA_VLAN.3 = %DATA2
PROFILE_FWTYPE.3 = EU
#Users must place the MAC address of CPE modems here.
ACCESSP_AUTHLIST_MAC.1 = 0x000BC2XXXXXX
ACCESSP_AUTHLIST_PROFILE.1 = 2
ACCESSP_AUTHLIST_MAC.2 = 0x000BC2XXXXXX
ACCESSP_AUTHLIST_PROFILE.2 = 3
Slave End User (CPE/EU) with VLAN 101 and OVLAN parameters
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = CPE
GENERAL_FW_TYPE = EU
GENERAL_IP_ADDRESS = 192.168.0.102
GENERAL_IP_NETMASK = 255.255.255.0
GENERAL_IP_GATEWAY = 192.168.0.1
GENERAL_IP_USE_DHCP = YES
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 84 Version 1.1.0
GENERAL_STP = YES
GENERAL_SIGNAL_MODE_LIST.1 = 1
GENERAL_SIGNAL_MODE_LIST.2 = 2
GENERAL_SIGNAL_MODE_LIST.3 = 3
GENERAL_SIGNAL_MODE_LIST.4 = 6
GENERAL_SIGNAL_MODE_LIST.5 = 7
GENERAL_SIGNAL_MODE_LIST.6 = 8
GENERAL_SIGNAL_MODE_LIST.7 = 10
GENERAL_SIGNAL_MODE_LIST.8 = 13
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = IND
QOS_ENABLE = YES
QOS_MAX_TXPUT_TX = 2048
VLAN_MNMT_TAG = %MNMT
VLAN_DATA_TAG = %DATA1
VLAN_DATA_PRIO = 4
OVLAN_ENABLE = YES
OVLAN_DATA_TAG = %ROOTPATH
Slave End User (CPE/EU) with VLAN 102 and OVLAN parameters
GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = CPE
GENERAL_FW_TYPE = EU
GENERAL_IP_ADDRESS = 192.168.0.102
GENERAL_IP_NETMASK = 255.255.255.0
GENERAL_IP_GATEWAY = 192.168.0.1
GENERAL_IP_USE_DHCP = YES
GENERAL_STP = YES
GENERAL_SIGNAL_MODE_LIST.1 = 1
GENERAL_SIGNAL_MODE_LIST.2 = 2
GENERAL_SIGNAL_MODE_LIST.3 = 3
GENERAL_SIGNAL_MODE_LIST.4 = 6
GENERAL_SIGNAL_MODE_LIST.5 = 7
GENERAL_SIGNAL_MODE_LIST.6 = 8
GENERAL_SIGNAL_MODE_LIST.7 = 10
GENERAL_SIGNAL_MODE_LIST.8 = 13
GENERAL_SIGNAL_REG_POWER_MASK_ENABLE = NO
PLC_SIGNAL_COUPLING = IND
Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 85 Version 1.1.0
QOS_ENABLE = YES
QOS_MAX_TXPUT_TX = 2048
VLAN_MNMT_TAG = %MNMT
VLAN_DATA_TAG = %DATA2
VLAN_DATA_PRIO = 4
OVLAN_ENABLE = YES
OVLAN_DATA_TAG = %ROOTPATH