Manual Corinex Low Voltage Access Gateway ENG

Low Voltage Access and GPON BPL Gateway
Released date: 6 October 2008 Page 1 Version 1.1.0

CORINEX User Guide
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
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 Coons
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 informon contained in this document is subject to change
without e.
Some features, s, and opons 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 restrions 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. D MS-DOS, MS; Windows are either
registered trademarks or trademarks of D Corporaon in the U.S.A. and/or other countries. All products or
company names ed herein may be the trademarks of their respece owners.
Copyright (c) 2001-2006 by Corinex Communions Corp.
LowVoltageAccessandGPONBPLGateway
Releaseddate:6October2008 Page3 Version1.1.0
RevisionHistory:
V1.0V1.1Oct09/2008
Minorchangestogrammerandspelling.
ENDUSERLICENSEAGREEMENT
This End User License Agreement (EULA) is a legal agreement between you and CORINEX COMMUNICATIONS
CORPORATION(CORINEX)withregardtothecopyrightedSoftwareprovidedwiththisEULA.
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
additionalordifferenttermsmayapply.IfyoudonotagreewiththetermsofthisEULA,donotdownload,install,
copyorusetheSoftware.
1. License Grant. CORINEX grants to you a personal, nontransferable and nonexclusive right to use the copy of
theSoftwareprovidedwiththisEULA.YouagreeyouwillnotcopytheSoftwareexceptasnecessarytouseitona
single hardware product system. You agree that you may not copy the written materials accompanying the
Software.Modifying,translating,renting,copying,transferringorassigningallorpartoftheSoftware,oranyrights
grantedhereunder,toanyotherpersons,andremovinganyproprietarynotices,labelsormarksfromtheSoftware
is strictly prohibited. Furthermore, you hereby agree not to create derivative works based on the Software. You
maypermanentlytransferallofyourrightsunderthisEULA,providedyouretainnocopies,youtransferallofthe
Software, and the recipient agrees to the terms of this EULA. If the Software is an upgrade, any transfer must
includeallpriorversionsoftheSoftware.
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
acquireanyrightstotheSoftware,exceptasexpresslysetforthabove.AllcopiesoftheSoftwarewillcontainthe
sameproprietarynoticesascontainedinorontheSoftware.
3. Reverse Engineering. You agree thatyou 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
conditionscontainedhereinwillresultintheautomaticterminationofthislicenseandthereversionoftherights
grantedhereundertoCORINEX.
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 noninfringement of thirdparty rights. The entire risk as to
the quality and performance of the Software is with you. Neither CORINEX nor its suppliers warrant that the
functions contained in the Software will meet your requirements or that the operation of the Software will be
uninterruptedorerrorfree.
5.LimitationofLiability.CorinexsentireliabilityandyourexclusiveremedyunderthisEULAshallnotexceedthe
pricepaidfortheSoftware,ifany.InnoeventshallCORINEXoritssuppliersbeliabletoyouforanyconsequential,
special, incidental or indirect damages of any kind arising out of the use or inability to use the software, even if
CORINEXoritssupplierhasbeenadvisedofthepossibilityofsuchdamages,oranyclaimbyathirdparty.
6.ApplicableLaws.ThisEULAwillbegovernedbythelawsofCanada,excludingitsconflictoflawprovisions.
7. Export Laws. This EULA involves products and/or technical data that may be controlled under any applicable
exportcontrollaws,andregulation,andmaybesubjecttoanyapprovalrequiredundersuchlawsandregulations.
8.Precedence.Exceptassetoutabove,whereseparatetermsareprovidedbythesoftwaresupplier,then,subject
tothisEULA,thosetermsalsoapplyandprevail,totheextentofanyinconsistencywiththisEULA.
TABLEOFCONTENTS
INTRODUCTION...............................................................................................................................7
FEATURESANDTECHNICALDATA...................................................................................................8
LVANDGPONBPLGATEWAYPRODUCTOPTIONS........................................................................9
LowVoltageAccessGateway(CXPLVAGWY)BasicModel......................................................9
HighDensityLowVoltageAccessGateway(CXPHDAGWY)....................................................9
GPONBPLGateway(CXPLVAGPON).......................................................................................9
GPONBPLHighDensityGateway(CXPHDAGPON)...............................................................10
GatewaywithIntegratedCoupler............................................................................................10
INSTALLATIONANDREQUIREMENTS............................................................................................11
CONNECTINGANDPOWERINGTHELVANDGPONBPLGATEWAY.............................................13
IntegratedCouplerConnector.................................................................................................14
FIRMWAREANDDEVICESTRUCTURE...........................................................................................16
CONFIGURATIONSANDSETTINGS................................................................................................18
PreparingDHCP/TFTPserver....................................................................................................18
Step1:TurningoffWindowsFirewallfromControlPanel...................................................18
Step2:InstallingDHCPserver...............................................................................................19
Step3:PreparingthenetworkinterfaceonthePC..............................................................19
Step4:SettingdefaultinterfaceforDHCPserver................................................................20
Step5:SettingstandardprofileforDHCPserver.................................................................21
PreparingTelnetPuTTYforcommandlineinterface(CLI)console.........................................21
Loadingautoconfigurationfile(*.conf)..................................................................................22
Step1:Preparinganautoconfigurationfile........................................................................22
Step2:PreparingaDHCPprofiletodownloadautoconfiguration.....................................24
Step3:BindingDHCPprofilewithstaticIPtable..................................................................25
Step4:Rebootingthemodemandcheckingtheloadingprocess.......................................26
Step5:Loadingautoconfigurationfilestoothermodems.................................................27
EXAMPLEOFDEPLOYMENT..........................................................................................................28
TECHNICALSPECIFICATIONS.........................................................................................................31
ANNEX1:CORINEXAV200ENTERPRISEFEATURES......................................................................32
Introduction.............................................................................................................................32
ApplicationDescription............................................................................................................32
CoreFeatures........................................................................................................................32
MACLayer.............................................................................................................................38
ApplicationLayer..................................................................................................................40
PLCApplicationDescription..................................................................................................46
BootProcess.........................................................................................................................52
ConstraintsforNetworkDesign...............................................................................................56
ANNEX2:AUTOCONFIGURATIONMANUAL................................................................................57
TranslationTable......................................................................................................................57
TransferringtheTranslationTable.......................................................................................57
ExampleofaTranslationTable.............................................................................................58
AdditionalInformationaboutTransferringPTTP.................................................................59
AV200Nodes............................................................................................................................60
AutoConfiguration&Networking............................................................................................60
VLANNetworks.....................................................................................................................60
NoVLANNetworks...............................................................................................................61
OVLANConfigurationandRootInterface.............................................................................61
AutoConfigurationFile............................................................................................................63
Introduction..........................................................................................................................63
ParameterTypes...................................................................................................................63
ParameterFormat.................................................................................................................63
SupportedParametersintheAutoConfigurationFile.........................................................64
GeneralParameters..............................................................................................................64
AGC(AutomaticGainControl)Parameters..........................................................................66
RADIUSParameters..............................................................................................................67
ClassofService(CoS)Parameters.........................................................................................67
QualityofService(QoS)Parameters....................................................................................68
ProfileParameters................................................................................................................69
TranslationTableParameters...............................................................................................71
VLANParameters..................................................................................................................71
OVLANParameters...............................................................................................................72
AccessProtocolParameters.................................................................................................72
STPParameters.....................................................................................................................73
MACIngressFilteringParameters........................................................................................74
CustomVLAN/OVLANParameters........................................................................................75
SNMPParameters.................................................................................................................78
MulticastProtocolParameters.............................................................................................78
CorinexMVG/LVGParameters.............................................................................................79
ANNEX3:EXAMPLEOFCONFIGURATIONFILES...........................................................................80
MasterAccessMode6(HE/LV6)outputtocoaxialport........................................................80
MasterAccessMode1(HE/LV1)outputtopin3and4.........................................................80
SlaveEndUser(CPE/EU)outputtopin3and4.......................................................................81
TDRepeater(TDR/LV)outputtopin3and4...........................................................................81
MasterAccessMode6(HE/LV6)withVLANandOVLANparameters....................................82
SlaveEndUser(CPE/EU)withVLAN101andOVLANparameters..........................................83
SlaveEndUser(CPE/EU)withVLAN102andOVLANparameters..........................................84
INTRODUCTION
Low Voltage Access Gateway (LV Gateway) and GPONBPL Gateway are Corinexs BPL access
productlineusing200MbpsAV200Technology.TheLVandGPONBPLGatewaysallowaneasy
installation to Multi Dwelling Units (MDUs) or last mile access neighborhoods where the
Gateway acts as a headend modem, extending an internet connection (optical fiber, DSL, or
wireless access) either to a power line or coaxial cable infrastructure, depending on the
customers 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
userscanconnecttheirEthernetenableddevicessuchasPC,VoIPphones,MediaCenters,etc.,
usingtheCorinexAV200seriesofPowerlineorCableLANEthernetAdapters,toanyelectricalor
coaxialsocketintheirpremisetoaccesstheInternet.
TheLVandGPONBPLGatewayscanservelargenetworks,upto1,024networkdevices.Andby
embedding threephase coupler inside the rugged enclosures, the Gateways provide easy
installationforthreephasepowersystemdeployment.AV200PowerlinetechnologybyCorinex
alsoprovidesnumerousnetworkingpossibilitieswithphysicallayertransferratesofupto200
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 GPONBPL Gateways also
supportotherexternalcouplersthatcanbeusedtoinjecttheBPLsignalbyconnectingthrough
thecoaxialcableport.
FEATURESANDTECHNICALDATA
Corinex Low Voltage Access Gateway and GPONBPL Gateway are high performance BPL
modem device designed for lowvoltage power line access networks in either single phase
threewireorthreephasefourwiresystem.TheGatewayisidealforuseasaHeadEndunitto
control a last mile lowvoltage access network as well as a large InBuilding distribution
network.UsingwithTimeDivisionRepeaterunits,itcanextendthecoverageofaPLCnetwork
beyond100users.
Figure1:LowVoltageAccessGateway
LVandGPONBPLGatewaysalwayscomewiththebasicfeaturesinclude:
x Specialhousingforinstallationsinroughenvironmentsliketransformerstationsandstreet
cabinets
x AbilitytoconfigureasaHeadEndMaster(HE),TimeDivisionRepeater(TDR),orSlave(CPE)
unitassameasotherAV200Enterpriseproductsbyloadingautoconfigurationsetting
x Physicalthroughputconnectivityofupto200Mbps
x 802.1QVLAN&OptimizedVLANs(OVLAN)
x DES/3DESencryption
x Integrated802.1DEthernetBridgewithRapidorCommonSpanningTreeProtocol
x Quality of Service (QoS) and 8level priority queues, with programmable priority
classificationEngine
x Priority classification according to 802.1P tags, IP coding (IPv4 or Ipv6) or TCP
source/destinationports
x 10/100BaseTFastEthernetinterfaceforconnectiontothenetworkpointofpresence
x CSMA/CARP (Carrier Sense Multiple Access with Collision Avoidance and Resolution using
prioritiesprotocol)
x Bridge Forwarding Table for 64 MAC addresses or 1,024 MAC addresses in High Density
model
x Optimizedsupportforbroadcastandmulticasttraffic
x SNMPagenttofacilitatemanagementoflargernetworks
x Integratedthreephasecoupler
LVANDGPONBPLGATEWAYPRODUCTOPTIONS
CorinexLVandGPONBPLGatewaycomewithavariationofmodelsthatuserscanchooseto
matchwiththeirrequirementanddeploymenttype.
LowVoltageAccessGateway(CXPLVAGWYC)BasicModel
TheLVGatewaybasicmodelcanrunasanHEmastermodemtoserveaBPLnetworkofupto
64 MAC addresses. It can connect to maximum 32 TDR or CPE modems directly. This basic
modem can be used in a smallsize network, typically up to 32 users. The following interfaces
andconnectorsareprovidedontheGateway:
x RJ45EthernetInterfaceforaccessingEthernetnetwork,
x FemaleFtypeconnectorforprovidingBPLaccessonacoaxialcable,
x 4pinpowersocketforpowerandprovidingBPLaccessonthepowerline.
Figure2:CXPLVAGWYBasicModel
HighDensityLowVoltageAccessGateway(CXPHDAGWYC)
TheHighDensityLowVoltageAccessGatewaycanserveasaHeadEndMastermodeminaBPL
networkcomprisingofthenetworkdevicesupto1,024MACaddressesintotal.HDAGWYhasa
capacitytoprovidedirectconnectiontomaximum64TDRorCPEmodems.EachofTDRmodem
canextendthedistancereachandanumberofconnectingCPEmodems.Itisrecommendedto
use HDAGWY in a medium or largesize network where there are more than 64 network
devices or MAC addresses in a broadcasting domain. The following interfaces and connectors
areprovidedontheGateway:
x RJ45EthernetInterfaceforaccessingEthernetnetwork,
x FtypefemaleconnectorforprovidingBPLaccessonacoaxialcable,
GPONBPLGateway(CXPLVAGPON)
The GPONBPL Gateway is an LV Gateway basic model with integration of ITUT G.984 GPON
ONTmoduleandopticalinterface.ItcanrunasanHEmastermodemtoserveaBPLnetworkof
up to 64 MAC addresses and connect to maximum 32 TDR or CPE modems directly. This basic
modem can be used in a smallsize 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
connectorsareprovidedontheGateway:
x SCAPCopticalconnectorforGPONONTmodule,
x RJ45EthernetInterfaceforlocalaccesstoONTandBPLmodule,
GPONBPLHighDensityGateway(CXPHDAGPON)
The GPONBPL High Density Gateway is an HDLV Gateway with integration of ITUT G.984
GPON ONT module and optical interface. It can serve as a HeadEnd Master modem in a BPL
networkcomprisingofthenetworkdevicesupto1,024MACaddressesintotal.HDAGPONhas
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
recommendedtouseHADGPONinamediumorlargesizenetworkwheretherearemorethan
64 network devices or MAC addresses in a broadcasting domain. Main application of HDA
GPONistoextendthelastmileGPONcoveragetoreachover32homeusersbythepowerline
media.ThefollowinginterfacesandconnectorsareprovidedontheGateway:
x SCAPCopticalconnectorforGPONONTmodule,
x RJ45EthernetInterfaceforlocalaccesstoONTandBPLmodule,
IntegratedCouplers
All models in the LV and GPONBPL Gateway product line are integrated with internal three
phase coupler which provides easy installation on the threephase power line system. The
integratedcouplerconnectionisa4pinsocketforcouplingthesignaltolineandneutralwires
ofthethreephasefourwirepowerline.Withthisfeature,CorinexLVandGPONBPLGateways
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
lossescausedbyanexternalcoupler.
Figure3:Gatewaywithintegratedcoupler
INSTALLATIONANDREQUIREMENTS
The LV and GPONBPL Gateways by Corinex are network devices mainly used for last mile
solutionsinbroadbandaccesstechnology.Deploymentcanbeontheelectricpowerpole,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
transformerstationsandstreetcabinets.Itcanbeeasilymountedonwallsorhangedonwires.
Grounding the case is recommended for safety, and should be done according to the local
electriccodeofconduct.Seefigurebelowforinstallationexample.
Figure4:InstallationofLVGatewayhangingfromasupportingwire
The LV and BPLGPON 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 MediumVoltage or any voltage higher than 270 Volts, a proper external coupler
mustbeused.TheEthernetportisprovidedinaprotectivewaterproofconnectorattachedto
thehousingcasetoaccessdirectlytothedevice.Seefigurebelow.
Figure5:WaterproofRJ45connectorforlocalEthernetaccess
CONNECTINGANDPOWERINGTHELVANDGPONBPLGATEWAY
The LV and GPONBPL Gateways come with a waterproof 4pin male connector for BPL signal
andfeedingpower.Amatchingfemalesocketconnectorisprovidedinthepackage.
Figure6:Fourpolepinandsocketconnectors
Figure7:PinconfigurationsontheGateway
Pin 1 2 3 4
Connectto
Power
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 thepower line. For a good reference, pin 3 can be
assignedforsignalLineandpin4forsignalNeutral.Theycanconnecttothesamelineneutral
pair used for the input power or different phase line. It is suggested to run 4 wires out of the
socketplugandtaponthepowerlines.
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
overline/linesandneutral.Belowfigureshowsanexampleofusingexternalinductivecouplers
onthreephasefourwiresystem.
N
A
B
C
Figure8:Exampleofusingexternalinductivecouplersfor3phaselines
Insomedeployments,theGatewaycancommunicatetotheothermodemoveracoaxialcable
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
powerline.However,toobtainamaximumperformance,highperformanceandlowlosscable
like RG6 type is preferred. Either 50ohm or 75ohm impedance can be used with the coaxial
interface.Impedancematchingbetweencoaxialcableandtheconnectorisinsignificantandthe
throughputimpairmentfrommismatchingimpedanceisnegligible.
IntegratedCouplerConnector
The LV and GPONBPL Gateways integrated coupler connection is on an additional 4pin
connectorforBPLsignal.Thedesignationofeachpinisasfollowed.
Pin 1 2 3 4
Connectto
Common
Neutral
PhaseA PhaseB PhaseC
1
4
3
2
Figure9:IntegratedCouplerConnector
TheinputpowerconnectoroftheGatewaywithintegratedcouplerhasonly2pinsasshownin
thefigurebelow.Pin1and2areforconnectingtoneutralandline.
1 2
Figure10:InputPowerConnectorfortheGatewaywithintegratedcoupler
3phaseLV
SignalOutput
Input
Power
Coaxial
Output
Figure11:Signaloutputportsandpowerconnector
FIRMWAREANDDEVICESTRUCTURE
Corinex Low Voltage Access Gateway and GPONBPL 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 HeadEnd Master (HE), Time Division
Repeater(TDR),orSlave(CPE)unitdependingontheconfigurationsetting.
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
coverageoverlongerdistanceorthenumberofendusers.TDRunitsbehaveasaSlaveforthe
Master unit and a Master for the Slave unit. Channel access on the BPL media is controlled
mainlyfromtheMasterunitbytokenpassing.TheTDRunitalsocontrolschannelaccessforits
SlaveunitsbyforwardingthetokenreceivedfromitsMasterunit.
InaBPLnetwork,thereshouldonlybeoneHEunit.TohavemorethanoneHEmastermodem
inthesamepowerlinecoverage,FrequencyDivisionschememustbeusedbysettingeachHE
unittorunadifferentfrequencymode.CorinexEnterprisefirmwareprovidesasolutiontouse
3differentequalfrequencybands;Mode1,Mode2,andMode3.
HE
LV lines
TDR TDR
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)
Figure12:TypicalBPLNetworkHierarchy
All Gateway models are running Corinex Enterprise firmware and are set to run the auto
configuration bootup process by default. This process requires DHCP and TFTP server to
providethenetworksettingsandconfigurationfiletothemodem.
The modem has a command line interface console for changing configuration and checking
statusofitsoperationorconnectivitywiththeothermodems.
AnumberofparameterscanbedefinedinanautoconfigurationfilestoredintheTFTPserver.
WhenthemodemrequestsanIPfromtheDHCPserver,itwillbeprovidedwithaninstruction
to download a configuration file from TFTP server together with the assigned IP address using
BOOTPprotocol.ThetextfilebelowshowsasimpleautoconfigurationfilefortheHEunit:
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
frequencymodesfortheBPLsignalfromtheconnectingline.IftheGatewayisrunningbythe
above configuration file and connecting to other modems on the same physical line, they
shouldmakeaconnectionandshowtheconnectivitystatusinthemastermodemsCLIconsole
similartothebelowfigure.
Figure13:CLIconsolefromTelnetshowingconnectivitystatus
CONFIGURATIONSANDSETTINGS
PreparingDHCP/TFTPserver
Thefollowingstepsareforinstalling andpreparingDHCPserveronaPC.Afterrunning
thisprocedure,theDHCP/TFTPserverwillbesetupproperlyinthePCandthereisnoneedto
runtheprocedureagain.
Step1:TurningoffWindowsFirewallfromtheControlPanel
ToconfigureanAV200modem,anumberofUDPandTCPportsinWindowsareusedby
the DHCP/TFTP server and other applications. Therefore, those ports must be allowed by
Windowsfirewallorthefirewallmustbeturnedoff.IfthePCisrunninganyantivirussoftware
and those ports are protected by antivirus, that feature should be disable according to anti
virusmanual.
If Window Firewall cannot be turned off, the following ports must be allowed for those
applications.
x UDPport68usedbyBOOTPC
x UDPport67usedbyBOOTPS
x UDPport69usedbyTFTP
Step2:InstallingDHCPserver
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.
LaterversionsupportsWindowsVista.
Step3:PreparingthenetworkinterfaceonthePC
The PC network interface must have a fix IP address set to 10.10.1.254 and subnet
255.255.255.0oranyclass.

This can also be done by the Windows command line (C:\WINDOWS\system32\cmd.exe) and
executingnetshwiththefollowingparameters.
>netshinterfaceipsetaddress"EthernetLAN"static10.10.1.254255.255.255.0
Network interface named EthernetLAN might be different. To check the correct name, the
usercanuseipconfigtodisplayallEthernetinterfacesinthePC.
Step4:SettingdefaultinterfaceforDHCPserver
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
theEthernetinterfaceisactive,itwillshowonthepreferencetab.Interface10.10.1.254must
be checked, other interface shown must be clear, and Use only selected interfaces must be
checkedtopreventtheothernetworkinterfacefromusingthisDHCPserver.
10.10.1.254
TheusercanuseTFTPserverthatcomeswithhaneWINDHCP.TFTPhasarootdirectorywhere
all autoconfiguration 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 wont be able
tofindtherequestedfile.
Step5:SettingstandardprofileforDHCPserver
DHCPserverwillsetadefaultstandardprofilefortheselectedIPinterfacefromstep3.
ThismustbecustomisedforthenetworktobeusedwithAV200modems.Thefollowingsetting
set this interface to provide IP addresses ranging from 10.10.1.100 to 10.10.1.250 to any
requestedclientwithsubnetmask255.0.0.0.AV200modemneedsadditionalsettingonOption
120tobebinary0000orunsigned32bitinteger0x0000.
x InterfaceIP=10.10.1.254
x DynamicIPaddresspoolfrom10.10.1.100to10.10.1.250
x AnyleasetimeandsubnetmaskisOK.
x Option120givesvalueofbinary0000.Makesurethatafteradding,itshows1204
0000.
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
PreparingTelnetPuTTYforcommandlineinterface(CLI)console
AV200modemneedsaTelnetclientrunningonaPCtointerface,monitor,andcontrol
all the functions available for command line interfaces (CLI). Telnet client should have the
followingsettings.
x Telnetport40000
x CR/LF
x Localechoonandlocallineeditingon
x BestforLinuxterminalandcompatiblewithVT100terminal
x Passive Telnet negotiation mode (send after CR allowing Backspace to correct the
mistype.)
x Loginadminmodeby/modeadminandpasswordmaxibon(PuTTYneedslogintwice.)
x CommoncommandsusedinCLIareIandls.
Loadingautoconfigurationfile(*.conf)
Step1:Preparinganautoconfigurationfile
In TFTPserversetup,therootdirectorymustbespecifiedandthisis thefolderforall
autoconfigurationfileswith.confextension.Autoconfigurationfileisasimpletextfileedited
byNotepadtosetupeachAV200modem.
A simple configuration for a master modem is as follows. In this example, it must be saved in
HE.LV.6.conf.
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_STP=YES
BelowisasimpleconfigurationforslavemodemusingCorinexAV200PowerlineAdapter.
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_STP=YES
The master modem needs to download a configuration file from TFTP server in order to work
properly. But the slave modem doesnt 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
configurationforexamplesignal_mode_list.
Step2:PreparingaDHCPprofiletodownloadautoconfiguration
To prepare a profile in DHCP server, the user must make sure that DHCP server is
running.InWindowsservices,DHCPservermustshowstatusasstarted.
InDHCPserver,underOptions,ManageProfiles,andAdd,itwillaskforaprofilename.
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
userschoice.
1
2
3
4
5
6
7
Tosetupaprofile,theusermustspecifythefollowingoptions.
1. Settingsubnetmaskto255.255.255.0oranysubnetdesignedbytheuser
2. SettinggatewayaddresstothisPC
3. SettingTFTPserveraddress
4. SettingTFTPname,mustbeaTFTPaddress
5. Settingoption66
6. Settingoption18toautoconfigurationfilenamewith.confextension(string)
7. Settingoption120to0000,4zerosand3spaces(binary)
Thenthisprofileisalreadyforthenextstep.
Step3:BindingDHCPprofilewithstaticIPtable
On this step, the modem must connect to PC and get an IP from DHCP server. It will
appearMACaddressofthemodem,1MACaddressforasinglemodemand3MACaddresses
forMDUorMVGateway,inDHCPdynamictable.
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),thentheremustbesomethingwrongwiththeserversetting.Theusermustcheck
BasicProcedure1again.
By selecting this MAC address and copying to static table, it will be transferred to the static
tablewhichallowstheusertobindwithanyIPandprofile.IftheuserchangesIPaddress,the
oldaddressmustbedeletedfromthedynamictabletoavoidduplication.Configurationprofile
istheprofiletoinstructthismodemtodownloadanautoconfigurationfilefromTFTPserver,in
thisexampleHE.LV.6.conf.
AftercompletelybindingaprofiletotheIPaddress,onthestaticIPtable,itshowsthecorrect
profiletobeused.
Step4:Rebootingthemodemandcheckingtheloadingprocess
As changing in the DHCP server is done after the modem gets IP address, the modem
wont reload the configuration until it is rebooted or reset or factory reset or end of IP lease
time.Theusermustrebootthemodembypoweroffandpoweronagain.Powerswitchonthe
MDUgatewaywillturnonandoffall3modulesatthesametime.Iftheuserwanttoresetonly
onemodem,theusemusttelnetandloginasanAdminandusecommand/hwrstforreset
or/frstfrstforfactoryreset.Inanolderfirmware(version3),factoryresetcommandis/hw
frst.
Afterreboot,themodemshallreceiveIPaddressfromDHCPserver,sendarequestfor
filedownloadtoTFTPserver,anddownload*.conffilefromtheserver.IntheEtherealcapture
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
inthemessage.Option3isagatewayIP.Option18istheconfigurationfilename.Option66is
TFTPserverIPaddress.AndOption120istoturnoffmanagementVLAN.Ifanyofthoseoptions
is missing, the modem wont properly loaded the configuration file from the server. It is
recommendedtokeeponmonitoringbyusingtheEtherealinordertopreventfromamistake.
Theusercancheckthecontentof*.conffileinthedatapackets.
On the Ethereal, the user must see packets containing Rapid Spanning Tree Protocol
(BPDU)sentoutfromthemodemthroughEhternetportfromtimetotime.Iftheusercannot
see RSTP BPDU or there is a VLAN tag on this packet, then there is something wrong with the
DHCPsettingormodem.
Step5:Loadingautoconfigurationfilestoothermodems
TheuserdoesntneedtoconnectPCtoalladaptersormodemsdirectlyinthenetwork
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 modems Ethernet port. The same process will be
takeninthesequentialorderuntilthelastmodem.
MV PLC
network
Gigabit Ethernet
Ring
RADIUS
server
DHCP
server
FTP
server
Router
Head-End
Repeater
Repeater
CPE CPE
DHCP
request
(Repeater MAC
address as a
parameter)
EXAMPLEOFDEPLOYMENT
Thefirstexampleofdeploymentshowsatypicalapplicationforthelastmileaccesstoservicing
housesfromGPONopticalfibercableendoranInternetaccessendpointviaUTPcable.
LVA-GWYC
HDA-GWYC
LVA-GPON
HDA-GPON
HE Unit
I I I I I I I I I I
Phase A, B, C, Neutral
Enterprise
Wallmount
adapter
meter
meter meter
Trans
former
Supporting wire
Coupling
points
Input power
Internet Access
CAT-5E or F/O
Figure14:LVGatewayinalastmiledeployment
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 3phase 4wire power system.
Corinex11+1couplerisusedforsignaldistributiontogetherwithinductivecouplerstoimprove
thesignalstrengthonall3phaselines.CoaxialoutputisselectedontheGateway.
LVA-GWY
HDA-GWY
HE Unit
I I I I I I I I I I
Phase A, B, C
Inductive
Coupler Mode 6
Tapping on one phase and neutral
lines. Using the inductive ferrite
coupler around all 3 phase lines,
excluding the neutral.
In electric room - basement
Cable Shaft / Vault
meter
11+1 Coupler
Wallmount
adapter
Figure15:MDUapplication
The number of servicing users in the above example is limited to 32 for LVAGWY and 64 for
HDAGWYaccordingtothemaximumofBPLportsthatcanprovideoneachGatewaymodel.To
extendthenumberofusers,HDAGWYmustbeusedfortheHEMasterunitwithanotherHDA
GWYasaTDRunit.TheHEunitconnectsto63CPEunitsand1TDRunit.TheTDRunitconnects
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
connectingtoonePConly.A2waysplitterusedinthisconfigurationwillprovideaseparation
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
increasedasthenumberofCPEunitsandactivityofusersapplication.
HDA-GWY
HE unit
HDA-GWY
TDR unit
I I I I I I I I I I
Phase A, B, C
Inductive
Coupler
Mode 13
Wallmount
adapter
Tapping on one phase and neutral
lines. Using the inductive ferrite
coupler around all 3 phase lines,
excluding the neutral.
In electric room - basement
Cable Shaft / Vault
meter
11+1 Coupler
Figure16:HighdensityMDUapplication
TECHNICALSPECIFICATIONS
Standards ITUTG.984.x,IEEE802.3u,802.1P
802.1Q,UPAAccessSpecification
SafetyandEMI EN55022ClassB,EN55024,EN50412
EN609501:2001IEC609501:2001
Backbonespeed GPONONT:2.488Gbpsdownstream,1.244Gbps
upstream
BPL:Upto200Mbps(PHY)
Ethernet:10/100MbpsFullDuplex(AUTO)
Threephasecouplertopowerline 110VAC/220VAC/240VAC
Interfaces SC/APCopticalconnector,
Powerlineconnector,
Ftypefemalecoaxialconnector,
10/100BaseTFastEthernetRJ45
Powerlinefrequencyrangeused 234MHz
Powerinput 85to265VAC,50/60Hz
Dimensions 230x185x80mm
Weight 2Kg
Transmittedpowerspectraldensity 50dBm/Hz
Powerconsumption Maximum20Watts
Operatingtemperature 20to70C(4Fto158F)
Operatinghumidity 10%to80%noncondensing
Environmentalclass IP68
ANNEX1:CORINEXAV200ENTERPRISEFEATURES
Introduction
ThisannexdescribesthefeaturesincludedinCorinexEnterprisefirmwareversion4.0.110oras
identifiedasac_sv4_0_110_0_0_3_0_8forAV200productfamily.
ApplicationDescription
Core Features: This section describes the core features, such as the protocols
relatedtothePLCphysicallayerandthelowlevelsupportforpacketmanagement;
MAC Layer: Describes the components that compose the Medium Access Control
layer;
ApplicationLayer:Adescriptionisgivenofthecomponentsthatrunabovethecore
andMAClayers;
PLC Application: This section describes some parameters specific to the PLC
application;
BootProcess:Thissectiondescribes,bywayofexample,thestartupprocess.
CoreFeatures
ThecorefeaturesaretheprotocolsrelatedtothePLCphysicallayerandthelowlevelsupport
forthepacketmanagement.
802.1DBridgeControl
The bridge implements learning, ageing, forwarding, and the Spanning Tree Protocol (STP) as
specifiedin802.1D.
BridgeMACTableCapacity
ThebridgeMACtablecapacityisthenumberofdifferentEthernetMACaddressesthatcanbe
stored in the bridge in order to perform forwarding. Packets addressed to MACs not stored in
thebridgetablearereplicatedthroughallinterfaces.Inthecurrentfirmwareimplementation,
thecapacityofthistableisvariedbythemodelasfollows:
Table1:MaximumMACsinBridge
AV200PRODUCTS MACs
PowerlineWallmountadapter 32
Alldesktopadapters,MVGateway,LVandGPONBPLGatewaybasicmodel 64
LVandGPONBPLHighDensityGateway 1024
LearningCapacity
ThelearningspeedisdefinedasthenumberofdifferentMACaddressespersecondreceivedin
thebridgeandlearned,withanunlearnedratiooflessthan1%ofthetotalMACsreceived.This
valuedoesnotdependontheinternalchipmodel.
Table2:LearningSpeed
750MACs/second
SpanningTreeProtocol(STP)
ThestandardSpanningTreeProtocolisimplementedinthecurrentversion,asdescribedinthe
IEEE802.1Dstandard(1998edition).Bydefault,themanagementVLANisusedtosendtheSTP
packetswhenVLANsareenabled.
Common Spanning Tiee Piotocol CSTP
TheCommonSpanningTree(CSTP)protocolcanbeconfiguredinthecurrentversion.Withthis
variationoftheSTP,theSTPpacketsareforwardedwithoutaVLANtagintheEthernet/Gigabit
EthernetinterfacesconnectingthePLCnetworkwiththebackbone.
Rapiu Spanning Tiee Piotocol RSTP
ThespanningtreeprotocolimplementedincludestheRapidSpanningTree,asdescribedinthe
IEEE 802.1w standard. Rapid Spanning Tree Protocol (RSTP; IEEE 802.1w) is an amendment to
802.1D.
NSTP Fiontiei
The administrator should be able to define STP boundaries, so that bridge messages cannot
pass through some predefined points. Therefore, topology changes would only be noticed
withinalimitedregionandhenceconvergenceisfaster.Onlyusersdirectlyaffectedbythelink
failureinthetreestructurewilldetectatemporary(short)trafficcutduringrecovery.
EncryptionControl
Corinex AV200 product family includes DES/3DES encryption feature. The current version of
firmwarehasencryptiondisabledbydefault.However,itispossibletoenableandconfigureit
through the console. The supported key length is 56 bit by default. The use of 168 bits is
availablebyspecialcustomizedorder.
AdaptiveBitLoadingControl
The Adaptive Bit Loading Protocol is the software component responsible for adapting the
modulationofeachOFDMcarrier,dependingontheSNRofthatcarrier.Thisallowsthehighest
possiblethroughputtobeachievedwiththecurrentlinkquality.Themainfunctionalityofthis
componentis:
Change carrier modulation when the carrier SNR changes, adapting to the new link
qualityandavoidinglineerrors(ifmodulationistoohighforthecurrentlinkquality)
orincreasingefficiency(ifthecurrentlinkqualitysupportsabettermodulation);
CarriermodulationdoesnotfollowlinearlyanySNRchange,butmustbefilteredin
timeinordertoreducetheprobabilityoferrorsduetoanunstablechannel.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
theyarenotsignificant(i.e.slightimprovementinonlyonecarrier),butalsowitha
smart algorithm that will learn from variations in SNR and modify the modulation
accordingly;
Allportsaretreatedfairly,thatis,theirBitsPerCarrier(BPC)areevaluatedwiththe
same frequency. The period of BPC evaluation depends on the number of nodes
visibleinthenetwork:themorenodes,thelessfrequentthemeasurementsare,in
ordertoavoidoverloadoftheCPU;
BPC measurements between a CPE and its master are interrupted when no data
trafficispresent,andthereforetheCPEbecomesidle;
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
resultinincreasedpacketloss.
ServiceClassifier
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
performedbymeansofagroupofrulesprogrammedbythefirmware.Therearetwodifferent
criteria for computing the priority. The selection of the criteria is based on the match of a
determinedfieldoftheEthernetframewithonepredefinedpattern.Onceacriterionischosen,
the priority is computed according to the parameters in that criterion. This method of
prioritizationallowsforcomputingthepriorityofdifferentpacketsusingdifferentfieldsandbit
patterns. For example, therecan be a difference in thecomputation 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
theautoconfigurationfile.
VLAN/OVLAN
Q vLAN Suppoit
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
classifiercanusethisfieldtoprioritizetraffic.
The basic VLAN configuration is service guided. Different VLANs are configured in the PLC
networkaccordingtothetypeofdata:
ReservedVLAN(usedforPLCprotocols);
ManagementVLAN;
DataVLANs;
VoIPVLANs.
EachoftheseVLANscanbeconfiguredwithadifferentpriority.ThereservedVLANsarefixedto
VLAN1andVLAN4094.VLAN0isnotsupported.
CustomVLAN
Corinex AV200 product allows enabling the custom VLAN/OVLAN. When you enable this
feature,youcancompletelyconfigurethedifferentportsinVLANterms.
WithacustomVLANyoucan:
x EnableVLANtagginginEthernetports;
x ChangetheVLANportfilteringbehaviour:
o Forbiddenlists:Packetswithtagsinthelistaredropped;
o Allowed lists: Packets with tags different from the ones in the list are
dropped;
x ChangetheVLANportfilteringtaglists;
x Enable/disabletheOutFormatoftheports:
o Enabled:PacketstransmittedwithaVLANtag;
o Disabled:PacketstransmittedwithoutaVLANtag;
x Enable/disabletheTaggedOnlyoftheports:
o Enabled:Inputuntaggedpacketsaredropped;
o Disabled:Allinputpacketsareaccepted;
x Enable/disable the ingress filtering (egress filtering is always performed when the
VLANisactive).
VLANTagTranslation
CorinexAV200productallowstagtranslationinEthernetinterfaces.PacketscomingwithtagA
from the Ethernet interface are retagged with tag B inside the PLC network. When a packet
withtagBexitsthePLCnetworkinthesameinterface,itisretaggedtotheAsourcetag.Only
onetagtranslationcanbeusedperEthernetport.
0vLAN
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
arenotpropagatedoutsidethePLCnetwork.
The basic OVLAN configuration is uses only one OVLAN tag (ROOTPATH) to allow the isolation
ofallendusersofanaccessnetwork.AnotherOVLANtag(0)isreservedforPLCprotocols.
CustomOVLAN
Corinex AV200 product allows enabling the custom VLAN/OVLAN. When you enable this
feature,youcantotallyconfigurethedifferentportsinOVLANterms,similartoVLANs.
WithacustomOVLANyoucan:
x EnableOVLANtagginginEthernetports;
x ChangetheOVLANportfilteringbehaviour:
o Forbiddenlists:Packetswithtagsinthelistaredropped;
o Allowed lists: Packets with tags different from the ones in the list are
dropped;
x ChangetheOVLANportfilteringtaglists;
x Enable/disabletheOutFormatoftheports:
o Enabled:PacketstransmittedwithaVLANtag;
o Disabled:PacketstransmittedwithoutaVLANtag;
x Enable/disabletheTaggedOnlyoftheports(onlyPLCports):
o Enabled:Inputuntaggedpacketsaredropped;
o Disabled:Allinputpacketsareaccepted;
x Enable/disabletheAcceptTaggedoftheports(onlyEthernetports).Thisisusefulin
implementingfrequencydivisionrepeaters:
o Enabled:Inputtaggedpacketsareaccepted;
o Disabled:Inputtaggedpacketsarenotaccepted.
x Enable/disable the ingress filtering (egress filtering is always performed when the
VLANisactive).
vLAN0vLAN Limitations
ThenumberofsupportedVLANsdependsonthemodemsconfiguration.Thehardwarehasan
internaltable,inwhichtheVLANinformationisstored.Thistableisuniqueandissharedbyall
interfaces in the modem. The elements in this table can be linked to create lists. This table is
usedtostoretheVLANandOVLANconfiguration(listoftags).
Theconfigurationforeachinterfaceisapointertoanentryinthistable.Thelistoftagscanbe
configured as allowed or forbidden tags. The forbidden tags can be used to allow all of the
possibleVLANtagsexceptareducedlistoftagsthatarenotallowed(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:
Thereisalsoalimitationperport,asdetailedinTable3.
Table3:MaximumVLAN/OVLANTags
MODELinAV200PRODUCT TOTALVLAN+OVLANTAGS VLANTAGSPERPORT OVLANTAGSPERPORT
Wallmountadapter 64 6 2
Alldesktopadapters,
MV,LV,andGPONBPL
Gatewaysbasicmodel
255 255 255
HighDensityGateway 255 255 255
MACFiltering
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.
Therearetwoworkingmodes:
1. FIXEDmode: TheallowedMACaddressesarespecifiedintheautoconfigurationfile;
2. AUTOmode: The allowed MAC addresses are the first ones learned by the Ethernet
interfaceuntilthemaximumnumberofallowedMACaddressesisreached.
SpatialReuse
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.
Powei Contiol
This feature only affects slaves. When enabled, the slaveswill try to reduce theirtransmission
gainmaintainingtheBPCvalueoftheirlinkwiththemasternodeoveracertainthreshold.
Submoues
The submodes are modes that share the same spectrum but are not mutually compatible. In
this way one modem in a submode sees a modem in another submode as white noise and
theydonotdisturbeachother.
PowerMaskControl
The Power Mask (PM) is a transmitted Power Spectral Density (PSD) frequency mask that is
usedtopreventordecrementtransmittedPowerinsomebandsgivingaparticularshapeto
thePSD.TherearethreedifferentPMconcepts;theModePM(PM),theRegulationPM(RPM)
andtheRawPM(RawPM).
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,soitistheonlyonesetintheHardwareifRPMandRawPMaredisabled;
Regulation Power Mask: The RPM is transmission mode independent and it is
definedbyasetofattenuatedbandscallednotches,eachofwhicharedefinedbyits
startfrequency,stopfrequencyanddeepwherethefrequenciesarespecifiedinKHz
andthedeepindB.Thecarriersinanotchareremovedfromtheoutputsignal,and
the deep is used to calculate the slope of the PSD frequency mask, so its value
affectsthecarriersadjacenttothenotch.TheobjectiveoftheRPMistocomplywith
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
deepdBunderthemaximumlevelofthePSDoutsideit;
RawPowerMask:TheRawPMisthecarrierdefinedmaskdownloadedintheauto
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,soparticularcarriersareattenuated.Careshouldbetakenwhenthere
are additional transmission modes as these can be removed. RawPM is only
recommendedwhenamodemusesonetransmissionmode.
ThethreetypesofPMarealwaysmergedtoobtainthemostrestrictivePSD,whichmeansthe
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,itscarriercoefficientsarecalculatedforeachtxmodeandmergedwithMPM.RawPM
ismergedwiththeMPMandtheRPM(ifenabled).
NOTE:CertainlimitationsmustbetakenintoaccountwhendefiningnewPowerMasks:
Theremustbeaminimumof20nonattenuatedcarriersbetweennotches;
Atleastonequarterofthebandmustbeunmasked.
Itmustbetakenintoaccountthattheselimitationsshouldbeusedasareferenceandnotasan
exactvalue.
MACLayer
LVAccessMAC&QoS
BandwidthLimitation
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,thetargetedlimitwillbeachievedwithinsomemarginoferror.
Forlowbandwidthlimits,thebandwidthobtainedafterlimitationisnotaccurate.However,itis
possible to predict the value that will be obtained by using the following graph. Anyway the
finalvalueandthemarginalerrorwilldependonthephysicallevel,theprotocolefficiency,the
latencystepconfiguredandthenumberamongotherfactors.
Figure17:ExpectedThroughputvs.MeasuredThroughput
This graph has been obtained considering a HECPE scenario with good physical level and the
entiredefaultconfiguration,exceptforthebandwidthlimitationthatisconfiguredineachcase
with a different test value. The traffic sent is a unidirectional UDP flow (upstream or
downstream)withahigherrate(atleastdouble)thanthebandwidthlimitationconfigured.
ThecharacteristicsofthealgorithmareshowninTable4.
Table4:BandwidthLimitation
PARAMETER VALUE
MinimumSpeed 512Kbps
MaximumSpeed 20000kbps
ConvergenceTime 30sec
SpeedFluctuation <10%
Latency management
The latencymanagement 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
desiredcriterion(TOS,VLANtagoranyotherconfigured)andeachofthePLCpriorities(from0
to 7) assigned by the Service Classifier has a Service Level Agreement (SLA1, SLA2, SLA4 and
SLA8)associated.
CSMA/CARPMAC
The CSMA/CARP MAC is implemented in the current firmware version. The CSMA/CARP MAC
canbeactivatedbyselectingGENERAL_MAC_MODE=INHOMEintheautoconfigurationfile.
Layer2ACKs
Itispossibletoconfigurelayer2ACKsaccordingtothepriorityofthetrafficbeingtransmitted.
TheACKpolicyisuniqueperconnection,andmustbethesameperpacket:ifseveralpriorities
aresniffedthepolicywillbefixedbythemaximumSLAdetected.Layer2ACKsareenabledby
defaultineverypowerlineconnection,foralldatapriorities.
ApplicationLayer
TCP/IPStack
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 highlevel protocols such as FTP, HTTP, etc. As a limitation,
thisTCP/IPstackdoesnotsupportIPfragmentation.Themaximumpacketsizeallowedis1514
bytes.
TFTPClient
ThefirmwareincludesaTrivialFileTransferProtocol(TFTP)clientthatallowsdownloadingfiles
from a TFTP server. This is the simplest way to transmit files. It is primarily used for
downloading new firmware versions, and downloading autoconfiguration files. The drawback
ofthisprotocolisthathasnoerrorcorrectionandusesUDP.
ThemaximumdownloadedfilesizeislistedinTable5.
Table5:MaximumDownloadedFileSize
OPERATION SIZE(KB)
Configurationfile 50
Otherfiledownloadedusingaconsolecommand 26.5
Thefilenamecanbeupto256characterslong.
FTPClient
ThefirmwareincludesaFileTransferProtocol(FTP)clientthatallowsdownloadingoruploading
filesfromanFTPserver.Thisisamorerobustprotocolfordownloadingfiles.TheFTPprotocol
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 autoconfiguration files. The limitations regarding file size and
namelengtharethesameasintheTFTPclient.
DHCPClient
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
extensionsandconfigurationfiledownloading.
LinkSearch
TheLinkSearchprotocolisthefirstprotocolthattakesplacewhenaCPEisstarted.Itsaimisto
select a link (or transmission mode) amongst a list of links in which an access network is
detected.EachlinkistestedforT
link
seconds.TheCPEwillselectthefirstlinkinthelistandwill
configure the transmission mode. After T
link
seconds, if no access network is detected, the
transmissionmodewillbechangedtothenextoneinthelist.Theworstcasetimetodetectan
accessnetworkifN
links
isthenumberoflinksinthelistis:
N
links
xT
link
xN
submodes
Thedefaultvaluesare:
T
links
= 5seconds
N
links
= 13links
N
submodes
= 4submodes
AccessProtocol/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
continuousinvitationoraccesstokens.TheCPEwillselectthebestmasteraccordingtocertain
criteria, and will answer this invitation token in order to access the network through this
master.ThemastermightdenyaccesstotheCPE,inwhichcasetheCPEwillselectadifferent
masterandwilltrytoaccessthenetworkthroughthatmaster.
Ifaccesstothenetworkisnotallowedthroughanyvisiblemasterinthenetwork,theCPEwill
restartthelinksearchprotocol,inordertofindanewlink.
OnceaCPEisconnectedtoamaster,itcanreevaluateitsstatusperiodically,andcanchange
itsconnectiontoanewmaster,accordingtocertaincriteria.Thisphaseisknownasthesecond
step.
The default configuration has been chosen in order to avoid instabilities: its frequency is very
low,andthechangeofmasterwillonlyoccurifthecurrentmasterhasverybadSNR.
x Thesecondsteptakesplaceaftertheautoconfigurationprocessandeverythreehours.
x The SNR threshold required to change masters is the equivalent to 2,150 bps (non
filteredreceptionvalue).
Autoconfiguration
The objective of the autoconfiguration process is the centralized management of a BPL
network using configuration files stored in a centralized database that are transferred to each
pieceofequipmentwhenitboots.Thesefilescontainalloftheinformationthatanodeneeds
inordertofunctioninacorrectmanner.
Belowisabriefdescriptionoftheprocesswhichisdiscussedinmoredetaillaterinthemanual:
1. Everynodestartswiththesamedefaultfactoryconfiguration:AccessCPE;
2. UsingPTTP(ParametricTranslationTableProtocol)themodemdiscoversifitisbooting
inanetworkwithVLANsornot.IfanetworkhasbeenbuiltusingVLANstoisolatetraffic
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
translationtable;
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
autoconfigurationfile;
4. Using TFTP protocol, the nodes download theautoconfiguration fileand configure the
firmwareaccordingly.
Inadditiontothemainstepsoutlinedabove,butthereisfurtherpointtoconsider:
Inordertoachieveasecurenetwork,powerline(PL)authenticationisintroduced.When
anewslaveistryingtoaccessthePLnetworkandconnectingtoamasterorarepeater,
the master or repeater may perform a RADIUS request to authenticate the user. The
RADIUS server will reply with information used to configure the masters interface to
the new user. However, autoconfiguration 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
autoconfigurationfileandusingthislistinsteadofRADIUStoauthenticatetheusers.
IfthenodeisthefirstmodeminthenetworkandconnecteddirectlythroughtheEthernetport
tothebackbone,theautoconfigurationprocessisdifferent:
1. Thisnodestartswiththesamedefaultfactoryconfiguration:AccessCPE;
2. Using DHCP protocol, each node gets its IP configuration (IP address, netmask and
gateway) and the name of its corresponding autoconfiguration file. There is also
anotherparametercalledPTTPcodethatindicatesifVLANisusedandthevalueof
the management VLAN if needed. Once this parameter is obtained the PTTP
protocolfinishes;
3. Using TFTP protocol, the nodes download the autoconfiguration file and configure
thefirmwareaccordingly.
When any node boots, there is a parameter stored in the NVRAM called GENERAL_USE_
AUTOCONF.Whenthisvalueisyes,thenodebootsinautoconfigurationmodeandwhenno,
it boots in NVRAM mode. There are two autoconfiguration possibilities inside the auto
configurationbootmodedependingonwhetherornotPTTPisperformed.
AutoconfiguiationPTTP Boot
Inthisautoconfigurationbootmodality,thenodealwaysinitiatesasaslave(CPE)andstartsto
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
DHCP request to get an IP configuration, and the name of the autoconfiguration file (option
18),aswell astheTFTP serverwherethefileislocated(option66). Itthendownloadsthefile
andconfiguresthefirmwareaccordingly.
AutoconfigurationnoPTTPBoot(default)
In this autoconfiguration boot modality, the modem has been already configured to
successfullyexecuteDHCPandTFTPsoitskipsPTTP.
NVRAMBoot
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
thatarealwaysconfiguredinthismode:
GENERAL_TYPE:Nodetype=HE,CPE,orTDREPEATER.
GENERAL_IP_USE_DHCP: Use DHCP = YES or NO. If this parameter is set to NO, the IP
configurationparametersareconfiguredfromNVRAM.
Alltheotherparametersareonlyconfigurediftheyhavebeendownloadedfromafilefirst,and
aGENERAL_USE_AUTOCONF=NOlinewasinthatautoconfigurationfile.Thisisequivalentto
performingaSaveasPermanent.
PTTPProtocol
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 autoconfiguration mode with the current firmware
version, it skips PTTP requests and doesnt 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
commandwillwriteabyteinNVRAMinorderthatthenextbootmodeofthemodemwillstart
withPTTPclient.
PTTP Booting
Whenamodembootsinautoconfigurationmode,itstartssendingPTTPrequests.Themodem
needstoknowifitis bootingina networkwithVLANsbeforerequestinganIPthroughDHCP.
For this reason, and because the LV node does not know if communication to the MV node is
throughPLCorEthernet,theFWtoFWprotocolusesaspecialPTTPMAC(01:80:C2:00:00:0E)
if communication is via Ethernet the LV node does not know the MAC of the MV node. The
PTTPpetitionsareperformedinthefollowingsteps:
Step1:APTTPrequestismadewithoutVLANsandwaitsforaresponse;
Step2:ItthenswitchestoVLANmodeandmakesaPTTPrequestusingtag#1(reserved
intheBPLnetwork)andwaitsforaresponse;
Step3:ReturnstoStep1.
When a node receives a packet with this PTTP MAC, the packet is sent to the FW. In
transmission,thisrequestisforwardedtoallactiveinterfaces.Finallyitwillconnecttoanode
thatwilltransferthetranslationtable.Themodemswitchesautomaticallytouseornottouse
VLANs with the same configuration as the node sending the translation table. In this way all
modemsconfigurethemselvestouseornottouseVLANs.Thisavoidshavingto writetheuse
or nonuse of VLANs in the NVRAM of all modems, a circumstance that can be extremely
convenientifanoperatorwantstochangetheentirenetworktouseVLANs.
AmodemmustnotperformPTTP(inAutoconfigurationnoPTTPBootmode)intheNVRAMin
thefollowingtwocases:
Ifitisthefirstnodeofthenetwork(directlyconnectedtothebackbone);
Ifitisgoingtoreceivethetranslationtableintheautoconfigurationfile.
In the first instance, this node will transfer the translation table (included in the auto
configurationfile)toothermodemswhenrequested,butinthiscasethereisnoothermodem
fromwhichtorequestthisinformationbecauseitwillbethefirstnodetoknowit.
ToavoidusingPTTPinthebootprocess,twomethodsareavailable:
1. UsingtheDHCPserver(mustbeaccessiblethroughVLAN#1orwithoutVLAN),thePTTP
protocolcanbeskipped.IntheDHCPreply,theservercansupplythemodemwiththe
management VLAN (in the event the modem boost in VLAN mode) or tell the modem
nottouseVLANs;
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),requestsanIPfromtheDHCPserverandfinallyreceivesitsautoconfiguration
fileviaTFTP.
Thesecondmethodisnotadvisable,becausetheaccesstotheconsoleispoorwhileusingPTTP
due to the change between VLAN and noVLAN modes. Method 1 should therefore be used if
possible.
TodisablePTTPthroughDHCP(method1),seethedetailaboutDHCPclient.
IfnoOVLANsorVLANsaregoingtobeusedinthenetwork,thePTTPprotocolcanbedisabled
inallofthemodems.TodisablePTTPmanuallyinthenextbootofamodem,followthesteps
below:
Using a DHCP server, give an IP to the modem; this may take some time because,
sometimes,themodemwillbesendingDHCPrequestswithVLAN#1andotherswithout
VLANactive;
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
fromtheconsoleandloginagain):
o ac stop: Stops the autoconfiguration process (and also PTTP) and disables the
VLANs. It is advisable to execute this command first to work comfortably with
the modem. This command does not write anything in the NVRAM, so it only
takeseffectwhenthemodemisreset;
o ac pttpmode set 0: Disables PTTP in the next boot, writing in the NVRAM. (ac
pttpmodeset1enablesPTTPinthenextboot,writingintheNVRAM);
o acpttpmodeget:ChecksthePTTPstateforthenextboot,readingtheNVRAM.
NOTE:DHCPshouldbeused(ifpossible)todisablePTTP.
SNMPAgent
ThisreleasesupportsSNMPv1,withoutsupporttovariablebindingsfortraps,andwithasingle
communityname.ThefollowingMIBsaresupported.
Table6:MIBTables
CORINEXMIB
MIBII RFC1213
CORINEXACCESSMIB
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
TelnetCLIcommandinadminmode.
FLASHUpgradeProtocol
TheFLASHupgradeprotocolallowsprovisionforanupgradeofanyofthebinariesincludedin
thefirmwarerelease.Asecureupgradeoftheapplicationandtheloaderbinariesisensuredby
the existence of a backup image. This however does not provide any protection from the
downloadwithanonrunningorincorrectapplicationorloader.
BIST
TheBuiltInSelfTest(BIST)providedinthisreleaseexecutesbydefaultthefollowingtests:
x Memories: The loader checks the data and address buses of the DRAM, as well as
theCRCofeveryFLASHsection;
x Ethernet: The Ethernet PHYs are set in loopback mode in order to test
communication.(disabledbydefaulttoreduceboottime);
RADIUSClient
TheRADIUSclientiscompliantwithRFC2865,exceptfortheaccountingfunctionalitiesthatare
notincluded.
Multicast
Therearetwopossibleoptionstoconfiguremulticastfeatures:
IuNP Packet Betection IuNP Awaie Nulticast Synuication
IfIGMPpacketdetectionfeatureisenabled,theendpointparsesallupstreampacketslooking
for IGMP join and IGMP leave datagrams. All upstream traffic must be sniffed by the
internalprocessorbypassingthesepacketsuptofirmwareandcheckingwhethertheycontain
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)toreconfigureallbridgestoensurethattheyaresyndicatedtothenewmulticaststream
andnotrafficreplicationismade.Thisfeaturecanbedynamicallyenabledordisabled.
Exteinal Nulticast Configuiation NPP
Itispossibletoconfiguremulticastbysendingspecialframestothemodems,communicating
thecreationofnewbindingsandthedeletionofoldones.Encapsulationisthegeneralmethod
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
configurethemulticastbindings.
FactoryReset
Users can restore the modem to a default state if any problem occurs by the factory reset
commandinTelnetCLIsession.
PLCApplicationDescription
ThePLCapplicationspecificationisdescribedinthefollowingsubsections.
ModesDefinition
Theparametersthatdefineamodeareasfollows:
x CentralFrequency:Indicateswherethemodeisplacedinthespectrum(inHertz);
x Bandwidth: This is the real bandwidth of the mode. It depends on the mode
bandwidthandpowermaskused;
x Mode Bandwidth: It can be 10, 20 or 30 MHz defines the maximum usable
bandwidthinthemode;
x 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
PSDatthelineafterAFEgain.Thefinalpoweronthelinedependsonthegainofthe
AFE;
x PowerMaskDefinition:Thisisthepowermaskdefinitionusedinthismode;
x MaximumPhysicalSpeed(achievableinthismode):Themaximumbpsdependson
thebandwidthmode,thepowermask,andsomeothersecondaryparameters,such
asBPCthresholds,configurationforBER,maximumallowedSNRintheRD,etc.The
value provided is the theoretical value for the default modem configuration and
includesalloverheadintroducedinthephysicallayer.
Mode1
Table7:Mode1
PARAMETER VALUE
CentralFrequency 7.968.750Hz
Bandwidth 10MHz
ModeBandwidth 10MHz
PSD 72dBm/Hz
PowerMaskDefinition FlatPM
MaximumPhysicalSpeed 84Mbps
Mode2(A1MVG)
Table8:Mode2
PARAMETER VALUE
Bandwidth 10MHz
ModeBandwidth 10MHz
PSD 72dBm/Hz
Mode3(A1MVG)
Table9:Mode3
PARAMETER VALUE
Bandwidth 10MHz
ModeBandwidth 10MHz
PSD 72dBm/Hz
Mode6
Table10:Mode6
PARAMETER VALUE
Bandwidth 30MHz
ModeBandwidth 30MHz
PSD 77dBm/Hz
Mode7
Table11:Mode7
PARAMETER VALUE
Bandwidth 5MHz
ModeBandwidth 10MHz
PSD 72dBm/Hz
PowerMaskDefinition LowerHalfBand
Mode8
Table12:Mode8
PARAMETER VALUE
Bandwidth 5MHz
ModeBandwidth 10MHz
PSD 72dBm/Hz
PowerMaskDefinition LowerHalfBand
Mode10
Table13:Mode10
PARAMETER VALUE
Bandwidth 10MHz
ModeBandwidth 10MHz
PSD 72dBm/Hz
Mode13
Table14:Mode13
PARAMETER VALUE
Bandwidth 30MHz
ModeBandwidth 30MHz
PSD 77dBm/Hz
Mode2(forA2MVGateway)
Table15:Mode2A2
PARAMETER VALUE
Bandwidth 7MHz
ModeBandwidth 10MHz
PSD 72dBm/Hz
PowerMaskDefinition M11PM
Mode3(forA2MVGateway)
Table16:Mode3A2
PARAMETER VALUE
Bandwidth 10MHz
ModeBandwidth 10MHz
PSD 72dBm/Hz
PowerMaskandNotches
Adynamicallyconfigurablepowermaskallowsthepossibilitytohavefullyconfigurablenotches
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
configurationprocess.
ThePowerMaskcanbedefinedaspartofthemodemdefinition,asaregulationPowerMask,
defining the frequency bands and the attenuation, or a raw Power Mask applied directly to
everycarrier.
ThefollowingdefaultPowerMaskdefinitionsareincluded,andusedinsomemodes.
Flat PN
Nocarrierisattenuated.
0ppei Balf Banu PN
This Power Mask uses the Upper half carriers. The lower half carriers are completely
attenuated.
Lowei Balf Banu PN
This Power Mask uses the lower half carriers. The upper half carriers are completely
attenuated.M11PM
This Power Mask uses all carriers except the first 96 and the last 149 carriers, which are
completelyattenuated.ItisusedforMode11.
0LB N PN
Thisissimilar(butslightlydifferent)tothepreviousone.Itisusedforbackwardcompatibility.
IAR0 PN
TheIARUpowermaskisdefinedasthedefaultvalueoftheregulationPowerMask.IARUPMin
MDU gateway is composed of 9 notches and 19 notches in the rest of Corinex products. The
settingsarelistedinTablesbelow.
Table17:IARUPowerMaskDescriptioninMDUGateway
NOTCHNUMBER STARTINGFREQENDINGFREQ NOTCHING(ATTENUATION/BW)
0 18002000 >30
1 35004000 >30
2 70007300 >30
3 1010010150 >30
4 1400014350 >30
5 1806818168 >30
6 2100021450 >30
7 2489024990 >30
8 2800029700 >30
Table18:IARUPowerMaskDescriptioninallotherproducts
0 18002000 >30
1 28503025 >30
2 34004000 >30
3 46504700 >30
4 53305405 >30
5 54505680 >30
6 65256685 >30
7 70007300 >30
8 88158965 >30
9 1000510150 >30
10 1127511400 >30
11 1326013360 >30
12 1400014350 >30
13 1790017970 >30
Table18:IARUPowerMaskDescriptioninallotherproducts
14 1806818168 >30
15 2100021450 >30
16 2192422000 >30
17 2489024990 >30
18 2800029700 >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
withoutchangingitsinitialdefinition.Itwillbeappliedtoallrelevanttransmissionmodes.Itis
configurablethroughTelnetCLI,autoconfiguration,andSNMPinterface.
PLCPorts
ThePLCportsareusedasanindextorefertoamodemthatisvisiblethroughthepowerline.
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 N
max_ports
, this means that a
modemcanseeuptoN
max_ports
modems,allofwhicharenotnecessarilyitsslaves.Theorderin
whichtheportsareassociatedtomodemsisfirstcomefirstserve.Also,everymulticastMAC
address uses one entry in this table. There is an additional broadcast port to those regular
ports.ThenumberofportsdependsonthechipmodelusedinCorinexproducts.Thefollowing
tableshowsthevaluesforthecurrentrelease.
Table19:MaximumPLCPorts
Corinexproductmodel Ports
Wallmountadapter 16
Alldesktopadapter,
MV,LV,andGPONBPLGateway
32
HighDensityGateway 64
BootProcess
The startup process of the modems is described, stepbystep, using the scenario shown in
Figure 2 one PC connected to a modem (modem 1, which will be the master) through the
Ethernet.Asecondmodem(modem2,CPE)isconnectedtothefirstmodemthroughthepower
line.
ThePCcontainsallofthenecessaryservers:DHCP,TFTP,RADIUS,etc.Thestepsaregoingtobe
describedconceptually,soadetailedconfigurationoftheserverisnotgoingtobeprovided.
The following tables describe the steps followed by the two modems; each row represents
someamountofelapsedtimealthoughthiselapsedtimecanbedifferentfromrowtorow.To
indicate coincidences of time in the two modems, the cells in the tables are marked with a
(number).Thetablesaredividedintotwocolumns,onerepresentingtheapplicationtasksand
theotherthePLClayer.
Both modems are powered on. The boot process described above is completed, the OS is
runningandthetasksarestarted.
Figure18:SetupConfiguration
Modem1:
Table20:MasterBootDescription(Modem1)
APPLICATIONS PLC
IfSTPisenabled,theportsmustbeintheforwarding
statebeforeanypacketcanbesentthroughtheport.
TheSTPtasksendsSTPpacketsthroughallports(PLCif
existsandEthernet)todetectloops.
Modemstartsasaslave.
TheDHCPtasksendsDHCPrequestthroughallports
(PLCifexistsandEthernet)askingforIPaddress.
LinkSearchstartslookingforsynchronization.
ThePTTPtasksendsPTTPqueriesthroughallports
(PLCifitexistsandEthernet).
Althoughthereisnomaster,Modem1is
continuouslychangingthelinktryingtosynchronize.
IfPTTPisenabled,DHCPmessagesaresentwithVLAN
(802.1Q)tag1andwithoutaVLANtagalternatively.
TheDHCPserverofthePCrespondswiththeIP,PTTP
parameter,IPoftheTFTPserver,andconfigurationfile
name.
TheDHCPtaskrespondswithDHCPACKtotheserver,
stopssendingDHCPrequestpacketsandpassesthe
parameterstothePTTPtask(PTTPparameter)andto
theautoconfigurationtask(TFTPserverIPand
configurationfilename).
ThePTTPtaskstopssendingpackets.
ThePTTPtaskactsaccordingtothePTTPparameter,
getstheDHCP,thusVLANconfigurationisset.
Table20:MasterBootDescription(Modem1)
APPLICATIONS PLC
ThemodemisnowaccessiblethroughTCP/IP,sotasks
liketheconsoleandSNMPareawaitinganyinputto
respond.
TheAutoconfigurationtaskdownloadsthe
configurationfileusingTFTP.
TheAutoconfigurationtaskusestheparametersto
configurethemodem.
Themodemchangestomaster.
Thelinkischangedtothatoftheautoconfiguration.
Autoconfigurationends. Themasterstartssendingaccesstokens,soslaves
canrequestaccess.

Oneslaveisdetected.
TheRADIUStasksendsaRADIUSqueryfortheMACof
theslave.
Portsolverprotocolstartsnegotiatingtheports.
TheRADIUStaskreceivestheauthorizationofthe
RADIUSserverwiththedesiredprofilefortheuser.
Portsolverprotocol(PSP)endstheportnegotiation.
QoSandnetworkparametersareconfiguredforthe
newuser:bandwidthlimitationinupstreamand
downstream,VLANs,OVLANs,etc.
Thetokenissharedbetweenthemasterandthe
slave,sotheslavecansenddatapackets.
ThePTTPtaskreceivesarequestfromtheslave.
ThePTTPtasksendsananswertotheslavewiththe
translationtableandthemanagementVLAN.
Modem2:
Table21:CPEBootDescription(Modem2)
APPLICATIONS PLC
IfSTPisenabled,theportsmustbeintheforwarding
statebeforeanypacketcanbesentthroughtheport.
TheSTPtasksendsSTPpacketsthroughallports(PLCif
existsandEthernet)todetectloops.
Modemstartsasaslave.
TheDHCPtasksendsDHCPrequestthroughallports
(PLCifexistsandEthernet)askingforIP.
LinkSearchstartslookingforsynchronization.
ThePTTPtasksendsPTTPqueriesthroughallports(PLC
ifexistsandEthernet).
Synchronizationisachievedinoneofthelinks.
Table21:CPEBootDescription(Modem2)
APPLICATIONS PLC
IfPTTPisenabled,theDHCPmessagesaresentwith
VLAN(802.1Q)tag1andwithoutaVLANtag
alternatively.
Accessprotocoldetectsamaster.
Accessprotocolanswersaccesstokenofthemaster.
Portsolverprotocolstartsnegotiatingports.
Mastergrantstheslaveaccess.
Portsolverprotocolendstheportnegotiation.
TheSTPtasksetstheportinforwarding,sopacketscan
gothroughPLC.
ThePTTPtaskreceivesthetranslationtableandthe
managementVLANfromthemaster.
ThePTTPtaskstopssendingpackets.
Networkparametersareconfiguredintheports
accordingtothePTTPinformation.
TheDHCPserverofthePCrespondswiththeIP,IPofthe
TFTPserverandconfigurationfilename.
TheDHCPtaskrespondswithDHCPACKtotheserver,
stopssendingDHCPrequestpacketsandpassesthe
parameterstotheautoconfigurationtask(TFTPserverIP
andconfigurationfilename).
ThemodemisnowaccessiblethroughTCP/IP,sotasks
liketheconsoleandSNMPareawaitinganyinputto
respond.
TheAutoconfigurationtaskdownloadstheconfiguration
fileusingTFTP.
TheAutoconfigurationtaskusestheparametersto
configurethemodem.
Autoconfigurationends.
Theseoperationsresultinanapproximatetimebetweenresetandpingof(forasinglepairof
modem):
Modem1:40seconds
Modem2:140seconds
ConstraintsforNetworkDesign
TwoMasterVisibility
Visibilitybetweenmastersatphysicallevelmustbeavoided.Itisrecommendedtousespatial
reuse procedures to avoid the direct visibility between HEs in the same mode (power control
andsubmode).
MaximumAllowedPLCPorts
ThecapacityofPLCportsis32inmostoftheproductsincludingMVGateway,MDUGateway,
LV and GPONBPL Gateway basic model, Powerline Adapter, and CableLAN Adapter. For High
DensityLVandGPONBPLGateway,thecapacityis64.
BridgeTableCapacity
ThemaximumnumberofMACaddressinthebridgetabledependsonthelearningspeed,the
ageing time, and the packet switch capacity. The data provided is measured with the default
configuration.Toobtainthemaximumcapacityinthebridgetable,increasingtheageingtimeis
recommended.
BandwidthLimitation
Therealbandwidthdiffersslightlyfromthespecifiedlimitanddependsonanumberoffactors,
liketraffictype,numberofusers,channelconditions,lineconditions,etc.
ReconfigurationTimeinMVMAC
Theprotocolsandalgorithmsthatallowthereconfigurationofringtopologiesinashorttime(a
fewseconds)whenaprobleminthenetworkappearsarenotincluded.
RegulationPowerMask
The regulation calculated power mask is slightly displaced to low frequencies. A correction to
highfrequenciesofaround20KHzmustbeintroducedineachnotchdefinitiontocompensate
thiseffect.ThenotchesoftheIARUpowermaskarealsocalculatedandtheyarealsodisplaced.
As a result of this displacement, two of the notches included in IARU regulation are a few dB
lessattenuatedthanrequired.
NumberofhopsinTimeDivisionDomains
Thenumberofhops supportedinaTimeDivisionDomainisten.Innetworksweremorehops
areneeded,itisrecommendedtouseseveralFrequencyDivisionDomains.
ANNEX2:AUTOCONFIGURATIONMANUAL
TranslationTable
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.Theautoconfigurationfileisaparametricfile,whichmeansthat,forexample,theHEor
TDRknows,usingtheautoconfigurationfile,thattheVLANDATAOPERATOR1isallowed,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 CPE TDR
CPE CPE
CPE
CPE CPE CPE
TDR CPE
HE
HE HE
A
B
C
D E
F G
Figure19:TranslationTableExample
Intheexample,NodeAdoesnotneedanyinformationabouttranslationsbecausenoLVnodes
arehangingfromNodeA.UsingTFTP,NodeBgetstheautoconfigurationfile.Inthefile,Node
B gets the translations used in all LV nodes hanging from it. This translation information is
differentfromthetranslationinformationusedbyNodeCandallLVnodeshangingfromit.The
translation file is usefulbecause Node D and Node F can have, if the network operator wants,
the same autoconfiguration 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
indicatesthatitisVLAN55.Fromthepointofviewofthenetworkoperator,thisiseasierthan
havingtwofiles,oneforNodeDandoneforNodeF.
TransferringtheTranslationTable
By a statusparameter in NVRAM (>ac pttpmode get),theMV node knows if it has to perform
PTTPornot.IfitdoesntneedtoperformPTTP,themodemdetermineswhetheritneedstouse
VLAN and the Management VLAN. Via DHCP, it knows the IP and the autoconfiguration file.
And,finally,usingTFTP,theMVnodegetstheautoconfigurationfilewiththetranslationtable
information. To run nodes in VLAN environment, the first node must have VLAN setting in
NVRAMandstoprunningPTTP.AllnodesexceptthefirstnodemustperformPTTPatboottime
(the default is PTTP off), but they do not have any VLAN information in the NVRAM. For this
reason,thesenodesneedVLANinformationbeforetheyrequestanIPthroughDHCP,andthey
alsohavetocheckiftheyareincludedinaVLANnetworkornot.Assuch,theyperformPTTPas
explainedbefore.PTTPisperformedinamixedstate(withVLAN#1andwithoutVLAN).Finally,
one of the requests will succeed and the nearest node will reply, transferring the translation
tablethatincludes:
x TheUSEVLANParametertofixtheVLANmode.
x Parametersrelated to VLAN (if needed), themain one being the Management VLAN. If
theparameterUSEVLAN=1,thenthemodemconfiguresitselftousetheManagement
VLANincludedinthetranslationtable.
x TheTRANSLATION_ROOTPATH_OVLANParameter.
NOTE:VLAN1isreservedinanAV200PLCnetwork.
ExampleofaTranslationTable
TRANSLATION_MNMT_VLAN=5
TRANSLATION_DATA_VLAN.1=10
TRANSLATION_VOIP_VLAN.1=30
TRANSLATION_ROOTPATH_OVLAN=77
TheHEorTDRmodemcanbeconfiguredusingthisinformationandtheautoconfigurationfile.
WhentheCPEmodemreceivesanautoconfigurationfilewiththefollowingparameter:
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
configurationfile:
USEVLAN=[0|1]
Ifthemodemisusing VLANs,thisparameterwillbesetto 1. Otherwisetheparameterwillbe
set to 0. This information will be transferred when it receives a PTTP request from the next
modemeitherthroughPLCorEthernetport.Thisparameteriswhatthemodemperformingthe
PTTPrequestusestoknowwhetherornotitneedstouseVLAN.
AdditionalInformationaboutTransferringPTTP
BecarefulwithPTTPinanynetworkwhereamodemcanconnectwithmodemsnotbelonging
to its network, because they can have different VLAN configurations (this may occur in MV
nodesorLVnodesthatcancommunicatewithMVnodes);thetranslationtabletransferredby
PTTPmightbeincompatiblewiththerealnetwork,inwhichthemodemmustremain.Tosolve
this situation (where a modem gets PTTP from a different master than it should), if the auto
configurationfiledownloadedbythemodemincludesthetranslationtable,thisinformationis
rewritten, 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
declaredwillremainunchangedfromthevaluesthatwerereceivedfromPTTP.Thisshouldnot
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
informationtomodemB:
#TranslationTableModemA
AfterPTTP,modemBdownloadsitsfile,includingthefollowingtranslationtableexplicitly:
#TranslationTableintheAutoconffileofModemB
Then the translation table that the modem will use (and the one that will transfer if it is
requestedfromanothernode)is:
#TranslationTableresultinginModemB
AV200Nodes
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,LVorEU):
x MVnetwork:theGENERAL_FW_TYPEinthiscaseshouldbeMV.
x LVnetwork:allofthemrunLVAccessMACbuttherearetwotypesdependingtherole
inthenetwork:GENERAL_FW_TYPEwillalsobeMV.
o LVnodes:thisisallmodemsinstalledintransformerstations,meterrooms,etc.
TheyshouldbeconfiguredwithGENERAL_FW_TYPEequaltoLV
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
equaltoEU.
ThemaindifferencesbetweenconfiguringaCPEmodemasEUorLVareasfollows:
x LocalVLANconfiguration:
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
insertthetag.
o TheLVnodewillconfiguretheEthernetportasTRUNKport,withalistofallowed
tagsandallthetagsinthetranslationtable.
x RemoteProfileconfiguration:alltheEUnodeshaveaprofileknownbytheirmaster,and
when a node enters the network, its master asks the RADIUS server for its own list, in
ordertogetthetypeofnodeandtheprofileassignedtothisuser.Ifthenodeisan:
o LV node: the profile is not taken into account. The configuration on the master
sideforthisnodeissettingthePLCportastrunkwithalltheallowedtagsinthe
translationtable
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.
AutoConfiguration&Networking
VLANNetworks
VLANNetworkDescription
Thenetworkmodelisdescribedasfollows:
x ThePLCnetworkisaswitchednetworkwithdifferentVLANtags.
x The firmware of all modems is inside the Management VLAN and VLAN 1. PLC
management protocols (PTTP, BPC, etc.) use VLAN 1, while highlevel management
protocols (DHCP, TFTP, HTTP, NTP, SNMP, etc.) use the management VLAN configured
by the auto configuration procedure. The Management VLAN may be different in
differentLVnetwork.
x The enduser modem receives untagged traffic from the external interface and this
traffic is tagged with the correct Data VLAN according to the customers ISP. So there
canbemorethanoneDataVLANperLVnetwork.
x The enduser modem generates traffic from VoIP, tagged with the correct VoIP VLAN
according to the customers VoIP operator. So there can be more than one VoIP VLAN
perLVcell.
x ItispossibletoaddprivateVLANsbetweenspecificcustomersthatdonotbelongtoany
ISP or voice operator. In this case, LAN trunks must be defined in the intermediary
equipmentinordertoallowallofthattaggedtraffic.
x All of the traffic is tagged inside the PLC network. Each Corinex AV200 modem must
receive its VLAN configuration in the autoconfiguration file. In addition to this, and in
order to reduce the number of autoconfiguration files for enduser (EU) modems (the
highest number), there will be a translation table transferred between modems which
containsinformationabouttheManagement,DataVLANsusedinanLVnetwork.
NoVLANNetworks
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
establishaLAN.
Inthiskindofnetwork,amodemwillnothavetheproblemsofaVLANnetwork.Bydefaultthe
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
regardingVLANs,itcancompletethefollowingsteps:DHCP,TFTPandconfiguration.
OVLANConfigurationandRootInterface
The basic OVLAN configuration in AV200 devices avoids the visibility between customers
connectedtotheendusernodesinasimpleway.Allofthecustomerdatapacketsinthesame
LVcellaretaggedwiththeRootpathOVLAN.Thistagistheonlyallowedtagintheentirepath
to the backbone. In the path from the backbone to the rest of the network, the packets are
taggedwiththeALL_VLANtag(4095)byequipmentthatisconnectedtothebackbone,andno
othertagisallowedinthispath.
However, packets with the ALL_VLAN tag are not filtered. An example of the basic OVLAN
configurationisshowninthefigurebelow.OVLANfilteringisdonewithegresslists.Thelistsare
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).Theresultisthatonlythedepicteddownstreamandupstreampathsareallowed.
Therootinterfaceisdiscoveredautomaticallyastherootportofthespanningtreeprotocol,so
itismandatorytohavetheSTPenabledfortheOVLANtowork.Whenanodeisgoingtobethe
root node (the HE in the figure for instance) the root interface must be specified inside the
autoconfigurationfile.Itwillalwaysbeoneoftheexternalinterfaces.
Figure20:BasicOVLANconfigurationexample
Inalloftheendusers,thefollowingconfigurationmustbeset:
OVLAN_ENABLE=yes
OVLAN_DATA_TAG=%ROOTPATH
Thenodethatconnectstothebackbonemusthave:
GENERAL_IFACE_ROOT=EXTA
OVLAN_ENABLE=yes
OVLAN_DATA_TAG=4095
AutoConfigurationFile
Introduction
Anautoconfigurationfilecontainstheconfigurationparametersneededbyeachnode.
In the case of MV nodes or module 1 and 2 in MV Gateway, parametric values are not
necessary.TheseMVautoconfigurationfilesareusuallyspecificforeachMVcircuit.Module3
orLVaccessmoduleinMVGatewayprovidesthetranslationtableforLVrepeaterandenduser
modems hanging from each MV Gateway. Each MV Gateway module 3 may need a particular
filedependingonthenetworkarchitectureofendpointdevices.
IncasethatallCPE/LVorCPE/EUnodesaredesignedtohaveagenericautoconfigurationfile
sameasothers,nospecificQualityofService,VLAN/OVLANconfiguration,orotherparameters
are included in the autoconfiguration file. Thus, the HE or TDR nodes those CPE nodes are
hanging from must have parametric autoconfiguration files and pass the value to its hanging
nodebyPTTPtransfer.
AllCPEnodescanalsobedesignedtousespecificconfigurationfileshangingfromnongeneric
HE or TDR node. In this case, the system must maintain quite a number of autoconfiguration
files as many as the number of modems there are in the network and PTTP transfer is not
necessary.
ParameterTypes
Therearethreetypesofparametersinsidetheautoconfigurationfile:
1. Scalar: PARAMETER=value
2. List: PARAMTER.index1=value
3. Table: PARAMETER.index1.index2=value
Thefirstvalidindexforlistsandtablesis1.
ParameterFormat
Theformatoftheparametersis:
x PARAMETER_LABEL[.x][.y]=valueforconcreteparametervalues
x PARAMETER_LABEL[.x][.y]=%parametric_valueforparametricparametervalues
Forexample,thefollowingparametercouldbeinsideanenduserautoconfigurationfile:
VLAN_DATA_TAG=452
or
In the second case, the parametric value must be translated to its correct value using the
translationtable.ThetranslationtablecanbelistedintheHEorTDRconfigurationitishanging
fromoreitherwithinitsownconfigurationfileincaseifPTTPmodeisoff.
SupportedParametersintheAutoConfigurationFile
Itisimportantthattheorderinwhichtheseparametersappearintheautoconfigurationfileis
preserved.Anyparametersthatdonotappearintheautoconfigurationfileskeeptheirdefault
values.Parsingisnotcasesensitiveforparametervalues(allvaluesexceptonesliketheRADIUS
sharedsecretwherethereisadifferencebetweencapitalandlowercaseletters).
GeneralParameters
GENERAL_USE_AUTOCONF=[yes|no]
Thisisthefirstparameterintheautoconfigurationfile.Whenthisparameterissettono,allof
theparametersinthefilearestoredintheNVRAMwhenthefileisdownloadedandthenode
bootsinNVRAMmodethenexttime.Defaultvalue:yes.
WARNING:whenthemodembootsinmodeNVRAM,PTTPisnotperformed,sotheTranslation
Tabledoesnotgetexchangedbetweendifferentnodes.Itismandatorytoaddthetranslation
tabletoallthefilesinthenetworktoconfigurethemodemforbootingfromNVRAM.
GENERAL_TYPE=[HE|CPE|TDREPEATER]
Configuresthetypeofnode.Defaultvalue:CPE.
GENERAL_FW_TYPE=[MV|LV|EU]
Configures the firmware type of the node. This parameter affects the QoS and VLAN/OVLAN
configuration.Defaultvalue:LV.
GENERAL_AUTHENTICATION=[RADIUS|AUTHLIST|NONE]
Authenticationmethod:
x IfRADIUSisselected,aRADIUSserverisinchargeofacceptingnewusersandassigning
theprofileandfw_type.
x If AUTHLIST is selected, authentication is done by checking a list provided in the auto
configurationfile.ThisoptionavoidstheinstallationofaRADIUSserver.
x IfNONEisselected,alloftheusersareaccepted.Defaultvalue:NONE.
GENERAL_STP=[yes|no]
Enables/disablestheSpanningTreeProtocolinthenode.Defaultvalue:yes.
GENERAL_COMMON_STP_EXTA=[yes|no]
Enables/disablestheCommonSTPfeatureinEthernetinterface(EXTA).
ItonlymakessensetousethisparameterifVLANsareenabled.Ifitissettoyes,STPpackets
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
throughEXTA.
GENERAL_IP_ADDRESS=<ddd.ddd.ddd.ddd>
IPaddressofthemodem(forthenextbootifDHCPisdisabled).
GENERAL_IP_NETMASK=<ddd.ddd.ddd.ddd>
IPnetmaskofthemodem(forthenextbootifDHCPisdisabled).
GENERAL_IP_GATEWAY=<ddd.ddd.ddd.ddd>
IPdefaultgatewayofthemodem(forthenextbootifDHCPisdisabled).
GENERAL_IP_USE_DHCP=[yesno]
Thenodedoes/doesnotuseDHCPforthenextbootifNVRAMmodeisused.
GENERAL_SIGNAL_MODE=[114]
In HE: Signal mode for transmitting. The signal modes that are predefined in the firmware are
mode1,2,3,6,7,8,10,and13.
GENERAL_SIGNAL_MODE_LIST.x=[114]
InCPEandTDREPEATER:ThelistrepresentstheallowedsignalmodesusedbytheSearchLink
to find a master. (x=114). CPE and TDEREPEATER nodes that do not implement Search Link
canusethisparameter,butonlythelastmodeintheautoconfigurationfilewillbetakeninto
consideration.Defaultvalue:allthemodes(1,2,3,6,7,8,10,and13)areallowed.
GENERAL_SIGNAL_POWER_MASK=00Ffa0()00FF
Thisparametersetsthepowermask.Eachpairoftwocharactersrepresentstheattenuationfor
acarrier,sothisparameteris1536x2characterslong.Defaultvalue:0Ainallthecarriers.
WARNING:thispowermaskisonlysetaftergettingthefile.Whenthemodemboots,itbegins
transmitting without powermask. Thus it is not a secure parameter for avoiding interference
withHAMandshortwaveradio.
GENERAL_SIGNAL_REG_POWERMASK_ENABLE=[yes|no]
This parameter enables or disables the use of the Regulation Power Mask (RPM). It is saved
alwaysinNVRAMtobeusedatthenextbootupwithoutrequiringtheautoconfigurationfile.
TheRPMnotchesshouldbepreviouslystoredinNVRAM.Bydefault,theNVRAMhasshortwave
radionotchesstoredinmemory.ThenotchconfigurationoftheRPMcanbechanged.
GENERAL_IFACE_ROOT=EXTA
Rootinterfaceassignment.Therootinterfaceistheinterfacewheretheautoconfigurationfile
isreceived.ThesystemautomaticallyobtainstherootinterfacefromtheSTProotport,butin
somecases,itmustbeassignedtoEXTA(forexamplewhenthenodeistheSTProot).TheSTP
bridgepriorityinAV200modemshasbeenmodifiedinthe2bytesreservedbythestandardin
thefollowingway:
0x9010MVMASTER
0x9020MVTDREPEATER
0x9030LVMASTER
0x9040LVTDREPEATER
0x9050LVCPE
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
bytesreservedwillchangeto:
((MVMASTER)0X8))=0X9008forMVnodes
((LVMASTER)0X8))=0X9028forLVnodes
Inthisway,astandalonemasterwillhavepreferenceoveramasterallocatedinaFDrepeater,
notdependentonaparticularMAC.
AGC(AutomaticGainControl)Parameters
Thefollowingparametersmustbehandledwithspecialcare.Apoorconfigurationcanproduce
lossofcommunicationwiththemodemthroughPLC.Normallyallofthesesettingsarerelated
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.
Defaultvalue:1.
WARNING: If the transmission gain is configured, it will remain configured, even if the mode
changes.
AGC_RX_ENABLE=[0|1]
Disable/enabletheHWAGC.Defaultvalue:1.
WARNING:IftheAGCisdisabled,itwillremaindisabled,evenifthesignalmodechanges.
AGC_RX_FIX_GAIN=[07]
Fixreceptiongain,onlyvalidiftheHWAGCisdisabled.Defaultvalue:7.
WARNING:Ifthereceptiongainisfixed,itwillremainfixed,evenifthesignalmodechanges.
AGC_MAX_RX_GAIN=[07]
FixthemaximumreceptiongainfortheHWAGC.Defaultvalue:7.
WARNING:Ifthemaximumreceptiongainisfixed,itwillremainfixed,evenifthesignalmode
changes.
AGC_MIN_RX_GAIN=[07]
FixtheminimumreceptiongainfortheHWAGC.Defaultvalue:0.
WARNING:Iftheminimumreceptiongainisfixed,itwillremainfixed,evenifthesignalmode
changes.
RADIUSParameters
RADIUS_SERVER_IP=<ddd.ddd.ddd.ddd>
RADIUSserverIPaddress.
RADIUS_SERVER_PORT=ddddd
RADIUSclientUDPport.
RADIUS_SHARED_SECRET=<string>
RADIUSsharedsecret.Itislimitedto16characters.
AllthreeparametersmustbesetinorderfortheRADIUSclienttoworkproperly.
ClassofService(CoS)Parameters
Usingtheautoconfigurationfile,2classesofservicecriteriacanbedefined,assigningpriorities
from0to7.
COS_CUSTOM_CRITERION_OFFSET.i=[1531]
Customicriterionframeoffset,inbytes(i=1,2).
COS_CUSTOM_CRITERION_PATTERN.i=0xXXXXXXXXXXXXXXXX
Customicriterion8bytepattern,inhexadecimaldigits(i=1,2).
COS_CUSTOM_CRITERION_BITMASK.i=0xXXXXXXXXXXXXXXX
Customicriterion8bytebitmask,inhexadecimaldigits(i=1,2).
COS_CUSTOM_CRITERION_CLASSES_OFFSET.i=[1531]
Customicriterionclassesframeoffset,inbytes(i=1,2).
COS_CUSTOM_CRITERION_CLASSES_BITMASK.i=0xXXXXXXXXXXXXXXX
Customicriterionclasses8bytebitmask,inhexadecimaldigits(i=1,2).
COS_CUSTOM_CRITERION_CLASS_PATTERN.i.j=0xXXXXXXXXXXXXXXX
Customicriterionjclass8bytepattern,inhexadecimaldigits(i=1,2;j=18).
COS_CUSTOM_CRITERION_CLASS_PRIO.i.j=[07]
Customicriterionjclasspriority(i=1,2;j=18).
COS_CRITERION.k=[CUSTOM1|CUSTOM2|8021p|TOS|ARP|TCP_8021p|TCP_TOS]
kcriteriondefinition(k=1,2).Assignsupto2criteriatoclassifytraffic.Therearetwocustom
criteria defined with the parameters above and some predefined criteria: 8021p is based on
VLANtagpriorityfield,TOSontheIPtypeofservicefield.ThecriteriaTCP_8021pandTCP_TOS
aremodificationsof8021pandTOStoprioritize,inaddition,dataTCPACKpacketstoimprove
the performance of bidirectional TCP flows; these two criteria are combined criteria that set
both criterion 1, 2 and the defaultpriority. 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
valuesdefinedbythesecriteria.ThedefaultcriteriaisTCP_8021p.Finally,thecriterionARPcan
beusedtoprioritizethetransmissionofARPpackets.
COS_DEFAULT_PRIO=[07]
ConfigurestheCoSdefaultpriority,thatis,thepriorityassignedtopacketsthatdonotmatcha
criterion.Defaultvalue:2.
QualityofService(QoS)Parameters
QOS_ENABLE=[yes/no]
Thisparameterenables/disablesthequalityofserviceinthenode.Ifthisparameterissettono,
thennootherparametersrelatedtoQoSareconfigured.
QOS_PRIOACK.prio+1=[0|1]
This list configures the Layer2 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
severalprioritiesaresniffed,thepolicywillbefixedbythemaximumprioritydetected.Default
value:1forallpriorities.
SlaveNodeParameters(CPE)
QOS_MAX_TXPUT_TX=xxxx(inkbps)
ConfiguresthemaximumtransmissionthroughputforthatCPE/TDREPEATER.
QOS_UPBWLIMIT=[YES|NO]
In a slave, limits its own transmission. Set to YES by default. If disabled, the user will transmit
dataconstantly.Everytimeitreceivesadatatoken,theslavewilltransmitlimitlessdatabackto
itsmaster.
MasterNodeParameters(HEorREPEATER)
QOS_LATENCY_STEP=[20400](inms)
ConfigurestheminimumlatencystepforthedifferentslaveswhenusingQoS.
Defaultvalue:30
QOS_BW_POLICY=[0|1]
ConfiguresthepolicyinwhichtheQoSmanagestheexcessofbandwidth.0isfairmodeand1is
prioritybasedmode.Defaultvalue:1.
QOS_LATENCY.prio+1=[1|2|4|8]
This list configures the latency for each priority level in QOS_LATENCY_STEP unities. Default
valuesareasfollows:
QOS_LATENCY.1=8
QOS_LATENCY.2=8
QOS_LATENCY.3=4
QOS_LATENCY.4=4
QOS_LATENCY.5=4
QOS_LATENCY.6=2
QOS_LATENCY.7=1
QOS_LATENCY.8=8
ProfileParameters
Todefineaprofile,atleastfiveparametersarerequired.Anythatarenotdefinedwillremainat
theirdefaultvalues:
PROFILE_MAX_TXPUT_TX.i=xxxx(inkbps)
Maximum transmission throughput (from the slave point of view: upstream) for users with
profilei.Defaultvalue:512.
PROFILE_MAX_TXPUT_RX.i=xxxx(inkbps)
Maximumreceptionthroughput(fromtheEUpointofview:downstream)foruserswithprofile
i.Defaultvalue:512.
PROFILE_PRIORITIES.i=[0x000xFF]
Prioritiesallowedforauserofprofilei.Eachbitrepresentsapriority.Thedefaultvalueis0x85,
so priorities 7,2 and 0 are allowed. To include another priority, set the appropriate bit in the
profileprioritiesflag.Themaximumandminimumprioritiesarealwaysseteveniftheyarenot
configured(0x81).
PROFILE_UPBWLIMIT.i=[YES|NO]
InamasteroraTDrepeater,limittheupstream(slavestransmission)foruserswithprofilei.if
disabled,theuserwillreceivetokensconstantly.Wheneverthemasternodehastransmittedall
requiredtokenstoalltheslaveswithupstreambandwidthlimited,thenitwilltransmittokens
to the slaves without upstream bandwidth limited until the other slaves can receive tokens
again.Defaultvalue:yes.
PROFILE_DWBWLIMIT.i=[YES|NO]
InamasteroraTDrepeater,limitthedownstream(slavesreception)foruserswithprofilei.If
disabled,themasternodewillneverstoptransmittingdatatothatuser.Wheneverthemaster
nodehastransmittedallrequireddatatoallslaveswithdownstreambandwidthlimited,thenit
will transmit data to the slaves without downstream bandwidth limited until the rest of the
slavescanreceiveagain.Defaultvalue:yes.
Thefollowingparameterscanbeaddedtotheprofiledefinitionbuttheyarenotmandatoryif
VLANorOVLANisnotenabled:
PROFILE_MNMT_VLAN.i=[24093]||%<PARAMETRICVALUE>
ManagementVLANforthatuser.
PROFILE_DATA_VLAN.i=[24093]||%<PARAMETRICVALUE>
DataVLANforthatuser.
PROFILE_VOIP_VLAN.i=[24093]||%<PARAMETRICVALUE>
VoIPVLANforthatuser.
PROFILE_VLAN_ADD_TAG.i.j=[24093]orparametric
Thisparameterisoftabletype.Fortheuserofprofilei,upto16 VLANs canbedefinedinthe
filterlist.WhenthelistisALLOWED,thesetagsareaddedtothebaseconfiguration.Otherwise,
if the list ischanged toFORBIDDEN, the base tags are removed and, for security reasons, only
thetagsdefinedhereareincluded.
PROFILE_VLAN_TAGGED_ONLY_IFACE_USER.i=[yes/no]
Fortheuserofprofilei,thisparameterindicateswhetherornottodropinputpacketswithout
aVLANtagfromtheuserwithprofilei(PLinterface).
PROFILE_VLAN_OUTFORMAT_TAG_IFACE_USER.i=[yes/no]
For the user of profile i, this parameter indicates whetheror not to send packets with a VLAN
tagtotheuserinterfacewiththisprofile.
PROFILE_VLAN_IS_ALLOWED_IFACE_USER.i=[yes/no]
Indicatesifthetagsonthelistareallowedorforbiddenfortheuserwithprofilei.Whenthelist
isALLOWEDthetagsareaddedtothebaseconfiguration;whenthelistisFORBIDDEN,thelistis
resetandonlytagsdefinedwithPROFILE_VLAN_ADD_TAGwillbeinthelist.
PROFILE_OVLAN_ADD_TAG.i.j=[24094]orparametric
Thisparameterisoftabletype.Fortheuserofprofilei,upto16OVLANscanbedefinedinthe
filterlist.WhenthelistisALLOWED,thesetagsareaddedtothebaseconfiguration.Otherwise,
if the list ischanged toFORBIDDEN, the base tags are removed and, for security reasons, only
thetagsdefinedhereareincluded.
PROFILE_OVLAN_TAGGED_ONLY_IFACE_USER.i=[yes/no]
Fortheuserofprofilei,thisparameterindicateswhetherornottodropinputpacketswithout
anOVLANtagfromtheuserwithprofilei(PLinterface).
PROFILE_OVLAN_OUTFORMAT_TAG_IFACE_USER.i=[yes/no]
For the user of profile i, this parameter indicates whetheror not to send packets with a VLAN
tagtotheuserinterfacewiththisprofile.
PROFILE_OVLAN_IS_ALLOWED_IFACE_USER.i=[yes/no]
Indicatesifthetagsonthelistareallowedorforbiddenfortheuserwithprofilei.Whenthelist
isALLOWED,thetagsareaddedtothebaseconfiguration;whenthelistisFORBIDDEN,thelist
isresetandonlytagsdefinedwithPROFILE_OVLAN_ADD_TAGwillbeinthelist.
ThemaximumnumberofprofilesisthemaximumnumberofPLCportsallowed.
TranslationTableParameters
TRANSLATION_MNMT_VLAN=[24093]
TranslationtablemanagementVLANtag.
TRANSLATION_DATA_VLAN.i=[24093]
TranslationtabledataoperatoriVLANtag.Upto16tags.
TRANSLATION_VOIP_VLAN.i=[24093]
TranslationtableVoIPoperatoriVLANtag.Upto16tags.
TRANSLATION_ROOTPATH_OVLAN=[24094]
TranslationtablerootpathOVLAN.
WARNING: When the modem boots in NVRAM mode, PTTP is not performed. The Translation
TableisnotexchangedbetweenthePLCnodes.Itismandatorytoaddthetranslationtableto
alltheconfigurationfiles(MV,LVandEU)toconfigureanymodemforbootingfromNVRAM.
VLANParameters
VLAN_ENABLE=[yes|no]
Enables/disablestheuseofVLAN.
WARNING:Normallythisparameterisnotneededbecausethemodemautomaticallydiscovers
theuseofVLAN,butitisnecessarywhenbootingfromNVRAM.
VLAN_MNMT_TAG=[24093]||%<PARAMETRICVALUE>
Management VLAN tag of highlevel FW management protocols. Often taken from the
translationtable.
WARNING:thisparametermustbeaddedtoallautoconfigurationfiles(MV,LVorEUmodems)
whenmodemsaresettobootupfromNVRAMonthenextreset.
VLAN_MNMT_PRIO=[07]
ConfigurestheVLANpriorityforthehighlevelmanagement(FW)packets.
VLAN_DATA_TAG=[24093]||%<PARAMETRICVALUE>
Parameter for EU nodes. Configures the VLAN tag for the data packets (packets coming from
theexternalinterfaces).
VLAN_DATA_PRIO=[06]
Parameter for EU nodes. Configures the VLAN priority for the data packets (packets coming
fromtheexternalinterfaces).
VLAN_TRUNK.i=[24093]
Parameter for LV and MV nodes. Configures a list of VLAN trunks, different from those in the
translationtable,andwhichmustbeallowedinthenodeinterfaces.Itisnecessarytoconfigure
thesetrunksforprivateVLANsbetweenEUsinallintermediaryequipment.
VLAN_RETAG_EXTA_SRC=[0|24095]
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_DSTparameter.With0,theretaggingisdisabledintheEXTAinterface.
VLAN_RETAG_EXTA_DST=[0|24095]
VLANretagging:External(Ethernet)interfaceA(EXTA)destinationtag.
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,
theretaggingisdisabledintheEXTAinterface.
OVLANParameters
The OVLAN parameters are used to configure the basic OVLAN configuration, which prevents
customersfromseeingeachotherintheaccessnetwork.
OVLAN_ENABLE=[yes|no]
Enables/disablestheuseofOVLANfiltering.
OVLAN_DATA_TAG=[24094]||%ROOTPATH_OVLAN
OVLANtagassignedtothepacketscomingfromtheexternalinterfaces.Itshouldbethesame
as in the translation table to perform the basic OVLAN operation in all equipment, except the
oneconnectedtothebackbone,whichwillhavetheALL_VLANtag(4095).
OVLAN_TRUNK.i=[24094]
Parameter for LV and MV nodes. Configures a list of OVLAN trunks, different from the one in
thetranslationtable,whichmustbeallowedinthenodeinterfaces.Itisnecessarytoconfigure
thesetrunksforprivateOVLANsbetweenEUsinallintermediaryequipment.
AccessProtocolParameters
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(ifpossible).
AP_FORBID_MASTER.i=0xXXXXXXXXXXXX
ListofforbiddenmastersforagivenslavebyMACaddress.
AP_PREFER_MASTER=0xXXXXXXXXXXXX
PreferredmasterforagivenslavebyMACaddress.Thisparameterisusefulbecausetheslave
will try to connect to the Preferred Master if it is present. If not, it will connect to any other
availablemaster.
AP_FIX_MASTER=0xXXXXXXXXXXXX
FixedmasterforagivenslavebyMACaddress.TheslavewillonlyconnecttothisFIXEDmaster.
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>
Configurestheperiodtimeofthebestmastercheck(inminutes).Defaultvalue:180.
AP_CURRENT_MASTER_MIN_BPS=<bps_thr>
Minimumbitspersymbolwiththecurrentmasterthatforcesachangeofmasterincheckbest
masterphase.Defaultvalue: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
masterphase.Defaultvalue:1750.
ACCESSP_AUTHLIST_MAC.i=0xXXXXXXXXXXXX
ListofallowedMACaddresses.Thelengthofthelistis128(i=1128).
ACCESSP_AUTHLIST_PROFILE.i=[116]
ListofprofilesassociatedwithaMACaddress.Thelengthofthelistis128(i=1128).Default
value:1.
ACCESSP_AUTHLIST_FWTYPE.i=[MV|LV|EU]
ListofFWTYPE.Thelengthofthelistis128(i=1128).Defaultvalue:LV.
STPParameters
STP_PRIO=[065535]
Configures the 2 bytes added to the MAC used by the STP standard to define the root path.
Defaultvalues:
0x9010MVMASTER
0x9010MVMASTER
0x9020MVTDREPEATER
0x9030LVMASTER
0x9040LVTDREPEATER
0x9050LVCPE
STP_PORT.i=[EXTA|EXTB|PLC]
The following two parameters will be configured depending on this one. For instance if
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
changedforallPLCports.
STP_PORT_PRIO.i=[0255]
Priorityoftheport(necessaryifcostsareequal).Defaultvalue(forETHAandPLC):80.
STP_PORT_COST.i=[065535]
Costoftheport.Defaultvalues:
ETHA=2000000
ETHB=2000000
PLC=4000000
STP_HELLO_TIME=[1040]
Hellotimeexpressedindecisecond.Defaultvalue:20decisecs.
STP_MAX_AGE=[60400]
Max.agetimeexpressedindecisecs.Defaultvalue:200decisecs.
STP_FORWARD_DELAY=[40300]
Forwarddelaytimeexpressedindecisecs.Defaultvalue:150decisecs.
STP_FRONTIER=[NONE|EXTA|EXTB]
DropsallSTPpacketsinanexternalport.Defaultvalue:NONE.
STP_MODE=[STP|RSTP]
STPprotocolversion:Common(802.1d)orRapid(802.1w).Defaultvalue:RSTP.
STP_PTP_EXTA=[0|1]
ConfiguretheEXTAinterfacetobetreatedaspointtopoint.
MACIngressFilteringParameters
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.Defaultvalue:no.
MAC_INGRESS_FILTERING_MAX_ALLOWED=[14]
Sets length of the MAC filtering ingress list. The maximum is 4 instead of 5 to allow the WISC
MACtobeintheFW;thisisdoneautomatically.
MAC_INGRESS_FILTERING_MODE=[FIXED|AUTO]
x 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.
x IfAUTO:DeletesallMACsregisteredinthebridgeassociatedtoETHports,andsetsthe
AUTOflag.WhenthebridgereceivesanewMACcomingfromETH,itregistersitinthe
INGRESS_MAC_FILTERINGlist.
x 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
MACsuntilthelengthofMAXiscompletedareregistered.
CustomVLAN/OVLANParameters
USE_CUSTOM_VLAN_OVLAN=[yes/no]
ThisparameterenablesotherVLAN/OVLANparameters.Defaultvalue:no.
Ifsettono,thepreviousconfigurationisused.Ifsettoyes,itwillconfiguretheparametersthat
are set in the autoconfiguration file. When set to yes, the connection will be lost if the new
parameters are not properly configured in the autoconfiguration file. It is necessary to
carefully specify several parameters, or else no connection will be possible between the
modems.
Asageneralrule,thisconfigurationoverridesthebasicVLAN/OVLANConfiguration.Inorderto
decreasetheriskoflosingtheconnection,theVLAN/OVLANfilteringfollowstheserules:
WhenthelistisALLOWED,thetagsspecifiedhereareaddedtotheexistingones.Thissolution
simplifiestheconfigurationanddecreasestheriskofmissconfiguration.
WhenthelistisFORBIDDEN,thelistsareresetbeforeinsertingthetagsspecifiedhere,forthe
samereasons.TheVLAN/OVLANcustomconfigurationmustbecomplementedwiththeprofile
parameters referring to VLAN/OVLAN to configure interfaces different from EXTA, ROOT and
OTHERS.
CustomVLANParameters
VLAN_FILTER_INGRESS=[yes/no]
VLAN filtering using input interface. By default only egress filtering (output interface) is
performed.Defaultvalue:no.
VLAN_TAGGED_ONLY_IFACE_ROOT=[yes/no]
DropspacketswithoutaVLANtagenteringtherootinterface(IFACE_ROOT).
Defaultvalue:no.
VLAN_TAGGED_ONLY_IFACE_EXTA=[yes/no]
DropspacketswithoutaVLANtagenteringexternal(Ethernet)interface.Defaultvalue:no.
VLAN_TAGGED_ONLY_IFACE_OTHER=[yes/no]
DropspacketswithoutaVLANtagenteringotherinterfaces(IFACE_OTHER).Defaultvalue:no.
VLAN_OUTFORMAT_TAG_IFACE_ROOT=[yes/no]
SendspacketswithaVLANtagtotherootinterface(IFACE_ROOT)Defaultvalue:yes.
VLAN_OUTFORMAT_TAG_IFACE_EXTA=[yes/no]
SendspacketswithaVLANtagtoexternal(Ethernet)interface.Defaultvalue:yes.
VLAN_OUTFORMAT_TAG_IFACE_OTHER=[yes/no]
SendspacketswithaVLANtagtootherinterfaces(IFACE_OTHER).Defaultvalue:yes.
VLAN_PVID_PL=[24095]
802.1QVLANtagfortagginguntaggedpacketsfromthepowerlineinterface(PL).Defaultvalue:
0.
VLAN_PVID_EXTA=[24095]
802.1QVLANtagfortagginguntaggedpacketsfromtheexternalinterface(EXTA).
IfEU,defaultvalue:VLAN_DATA_TAG.IfLVorMV,defaultvalue:0.
VLAN_PVID_FW=[24095]
802.1QVLANtagfortagginguntaggedpacketsfromthefirmwareinterface(FW).Defaultvalue:
1.
VLAN_DEFAULT_PRIO_PL=[07]
802.1ppriorityfortagginguntaggedpacketsfromthepowerlineinterface(PL).Defaultvalue:0.
VLAN_DEFAULT_PRIO_EXTA=[07]
802.1ppriorityfortagginguntaggedpacketsfromexternal(Ethernet)interfaceA(EXTA).
IfEU,defaultvalue:VLAN_DATA_PRIO.Defaultvalue:0.
VLAN_DEFAULT_PRIO_FW=[07]
802.1ppriorityfortagginguntaggedpacketsfromthefirmwareinterface(FW).
Defaultpriority: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.Defaultvalue:yes.
VLAN_LIST_IFACE_ROOT.i=[24095]
PrivateVLANslist:Rootinterface(IFACE_ROOT)taglist.Upto16valuescanbeconfigured.
VLAN_IS_ALLOWED_IFACE_EXTA=[yes/no]
PrivateVLANslist:External(Ethernet)interfacelistisanallowedtagifYESorforbiddenifNO.
Defaultvalue:yes.
VLAN_LIST_IFACE_EXTA.i=[24095]
PrivateVLANslist:External(Ethernet)interfacetaglist.Upto16valuescanbeconfigured.
CustomOVLANParameters
OVLAN_FILTER_INGRESS=[yes/no]
OVLAN filtering using input interface. By default only egress filtering (output interface) is
performed.Defaultvalue: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]
DropspacketswithoutanOVLANtagenteringtherootinterface(IFACE_ROOT).
OVLAN_TAGGED_ONLY_IFACE_EXTA=[yes/no]
Despitethenameofthisparameter,themeaningofitisdifferentforEthernetinterfaces.Ifset
toNO,itdropspacketswithanOVLANtagenteringexternal(Ethernet)interfaceA.IfsettoYES,
itacceptspacketstaggedwithanOVLANtag.Defaultvalue: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]
DropspacketswithoutanOVLANtagenteringotherinterfaces(IFACE_OTHER).
OVLAN_OUTFORMAT_TAG_IFACE_ROOT=[yes/no]
SendspacketswithanOVLANtagtotherootinterface(IFACE_ROOT).Defaultvalue:yes.
OVLAN_OUTFORMAT_TAG_IFACE_EXTA=[yes/no]
SendspacketswithanOVLANtagtoexternal(Ethernet)interface.Defaultvalue:no.
OVLAN_OUTFORMAT_TAG_IFACE_OTHER=[yes/no]
SendspacketswithanOVLANtagtootherinterfaces(IFACE_OTHER).Defaultvalue:yes.
OVLAN_PVID_PL=[24095]
OVLANtagfortagginguntaggedpacketsfromthepowerlineinterface(PL).Defaultvalue:0.
OVLAN_PVID_EXTA=[24095]
OVLANtagfortagginguntaggedpacketsfromexternalinterface(EXTA).IfEU,thedefaultvalue
isequaltoOVLAN_DATA_TAG.IfLVorMV,defaultvalueis0.
OVLAN_PVID_FW=[24095]
OVLANtagfortagginguntaggedpacketsfromthefirmwareinterface(FW).Defaultvalue: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.Defaultvalue:yes.
OVLAN_LIST_IFACE_ROOT.i=[24095]
PrivateOVLANslist:Rootinterface(IFACE_ROOT)taglist.Upto16valuescanbeconfigured.
OVLAN_IS_ALLOWED_IFACE_EXTA=[yes/no]
PrivateOVLANslist:External(Ethernet)interfacelistisanallowedtagifYES,orforbiddenifNO.
Defaultvalue:yes.
OVLAN_LIST_IFACE_EXTA.i=[24095]
PrivateOVLANslist:External(Ethernet)interfacetaglist.Upto16valuescanbeconfigured.
SNMPParameters
SNMP_TRAP_IP_ADDRESS=<ddd.ddd.ddd.ddd>
ConfigurestheIPaddresstowhichtrapsaresentwhenproduced.
SNMP_TRAP_COMMUNITY_NAME=<communityname>
Configures the trap community access. This parameter is a string with maximum length 23
characters.
MulticastProtocolParameters
MCAST_IGMP_SNOOPING=[yes/no]
ConfigurestheIGMPSNOOPINGfeatureinanode.IfenabledthenodeisabletotranslateIGMP
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
encapsulatedintoMPPframesandsentthroughthePLCnetworkandtherestareregenerated
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).
Defaultvalue: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
FrequencyDivisionRepeaters),leaveMCAST_MPP2IGMP_PORT=none.
CorinexMVG/LVGParameters
NODE_NUMBER=[199]
ForMVGatewayidentity.Thislinemustbeincludedinthesecondlineofautoconfigurationfile
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]
ToallowcouplingtheBPLsignalintocoaxial,lowvoltageline,orindependentport.Availablein
module3ofMVGatewayforCOAXorLV.AvailableinLowVoltageAccessGatewayandGPON
BPLGatewayforCOAXorIND.INDinbasicmodelisprovidedthroughpin3and4onthepower
socket.INDinthemodelwithintegratedcouplerisprovidedthroughanindividual4pinsignal
port.
ANNEX3:EXAMPLEOFCONFIGURATIONFILES
MasterAccessMode6(HE/LV6)outputtocoaxialport
GENERAL_TYPE=HE
GENERAL_FW_TYPE=LV
GENERAL_STP=YES
SIGNAL_SUB_MODE=0
PLC_SIGNAL_COUPLING=COAX
MasterAccessMode1(HE/LV1)outputtopin3and4
GENERAL_TYPE=HE
GENERAL_FW_TYPE=LV
GENERAL_STP=YES
SIGNAL_SUB_MODE=0
GENERAL_TYPE=HE
GENERAL_FW_TYPE=LV
GENERAL_STP=YES
SIGNAL_SUB_MODE=0
GENERAL_TYPE=HE
GENERAL_FW_TYPE=LV
GENERAL_STP=YES
SIGNAL_SUB_MODE=0
SlaveEndUser(CPE/EU)outputtopin3and4
GENERAL_TYPE=CPE
GENERAL_FW_TYPE=EU
GENERAL_STP=YES
GENERAL_SIGNAL_MODE_LIST.1=1
TDRepeater(TDR/LV)outputtopin3and4
GENERAL_TYPE=TDREPEATER
GENERAL_FW_TYPE=LV
GENERAL_STP=YES
MasterAccessMode6(HE/LV6)withVLANandOVLANparameters
GENERAL_TYPE=HE
GENERAL_FW_TYPE=LV
GENERAL_STP=YES
GENERAL_AUTHENTICATION=AUTHLIST
SIGNAL_SUB_MODE=0
QOS_ENABLE=YES
QOS_BW_POLICY=1
COS_CRITERION.1=TCP_8021p
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_DATA_VLAN.2=%DATA1
PROFILE_FWTYPE.2=EU
PROFILE_DATA_VLAN.3=%DATA2
PROFILE_FWTYPE.3=EU
#UsersmustplacetheMACaddressofCPEmodemshere.
ACCESSP_AUTHLIST_MAC.1=0x000BC2XXXXXX
ACCESSP_AUTHLIST_PROFILE.1=2
ACCESSP_AUTHLIST_MAC.2=0x000BC2XXXXXX
ACCESSP_AUTHLIST_PROFILE.2=3
SlaveEndUser(CPE/EU)withVLAN101andOVLANparameters
GENERAL_TYPE=CPE
GENERAL_FW_TYPE=EU
GENERAL_STP=YES
QOS_ENABLE=YES
QOS_MAX_TXPUT_TX=2048
VLAN_MNMT_TAG=%MNMT
VLAN_DATA_PRIO=4
OVLAN_ENABLE=YES
SlaveEndUser(CPE/EU)withVLAN102andOVLANparameters
GENERAL_TYPE=CPE
GENERAL_FW_TYPE=EU
GENERAL_STP=YES
QOS_ENABLE=YES
QOS_MAX_TXPUT_TX=2048
VLAN_MNMT_TAG=%MNMT
VLAN_DATA_PRIO=4
OVLAN_ENABLE=YES

Manual Corinex Low Voltage Access Gateway ENG

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Manual Corinex Low Voltage Access Gateway ENG

Загружено:

Авторское право:

Доступные форматы

Low Voltage Access and GPON BPL Gateway

Released date: 6 October 2008 Page 1 Version 1.1.0

Вам также может понравиться