cfip_phoenix_td_en_v 1 4 copy.pdf

CFIPPhoeniXSeriesTDM/IPSplitMountSystem

TechnicalDescription&ConfigurationGuide

Productcode:S0DRFMD1

SAFTehnikaJSC2011

CFIP PhoeniX Series TDM/IP Split Mount System Technical Description and Configuration Guide Rev. 1.4

SAF Tehnika JSC 2011

2

TableofContents 1 Overview .................................................................................................................................... 5 1.1 CFIPPhoeniXTDM/IPsplitmountsystem ....................................................................................... 5 1.2 CFIPPhoeniXfeatureSummary ....................................................................................................... 5

1.2.1 MainFeatures ........................................................................................................................................... 6 1.2.2 IDUmechanicalfeatures ........................................................................................................................... 6 1.2.3 ODUmechanicalfeatures ......................................................................................................................... 6 1.2.4 Interfaces/Management ........................................................................................................................... 7

1.3 CFIPPhoeniXODUParameters ........................................................................................................ 8 1.4 ApplicationExamples ...................................................................................................................... 8

1.4.1 CFIPPhoeniX1+0configuration ................................................................................................................ 8 1.4.2 CFIPPhoeniX1+1HotStandby(HSB) ....................................................................................................... 8 1.4.3 CFIPPhoeniX1+1SpaceDiversity ............................................................................................................. 9 1.4.4 CFIPPhoeniXRingTopology ...................................................................................................................... 9

1.5 Technicalspecification .................................................................................................................. 11 1.6 CableRequirements ...................................................................................................................... 14 1.7 Labelling ........................................................................................................................................ 15

2 ConfigurationandManagement ................................................................................................. 17 2.1 ConnectingCFIPPhoeniXIDUtopowersource ............................................................................. 17 2.2 ResettingtheCFIPPhoeniX ........................................................................................................... 18 2.3 WebInterface ................................................................................................................................ 18

2.3.1 10/100/1000BaseTPorts ....................................................................................................................... 18 2.3.2 EthernetManagementConnectionConfiguration .................................................................................. 18 2.3.3 ConnectingtoWebInterface .................................................................................................................. 21 2.3.4 InterfaceDescription ............................................................................................................................... 22 2.3.5 CommandExecution ............................................................................................................................... 23 2.3.6 InitialConfigurationwithWebGUI ......................................................................................................... 25

2.4 CommandPromptInterface .......................................................................................................... 28 2.4.1 RS232SerialManagementPort ............................................................................................................. 29 2.4.2 Telnetconnection ................................................................................................................................... 31 2.4.3 InitialConfigurationwithCommandPrompt .......................................................................................... 33

2.5 LEDindications .............................................................................................................................. 33 2.5.1 CFIPPhoeniXIDUalarmLEDindications ................................................................................................. 33 2.5.2 EthernetRJ45connectorLEDindications .............................................................................................. 34 2.5.3 E1RJ45connectorLEDindications ........................................................................................................ 34

3 StatusWindow .......................................................................................................................... 35 3.1 RadialMSE .................................................................................................................................... 37 3.2 LDPC .............................................................................................................................................. 37

4 DetailedConfigurationinWebGraphicUserInterface ................................................................. 39 4.1 ODUConfiguration ........................................................................................................................ 39

4.1.1 RadioConfiguration ................................................................................................................................ 39 4.1.2 ATPCConfiguration ................................................................................................................................. 39 ATPCAlgorithm ...................................................................................................................................................... 41

4.2 IDUConfiguration ......................................................................................................................... 42 4.2.1 ModemConfiguration ............................................................................................................................. 42 4.2.2 LoopbackConfiguration .......................................................................................................................... 44

4.3 Protectionconfiguration ............................................................................................................... 46 4.3.1 FrequencyDiversityMode ...................................................................................................................... 46 4.3.2 HotStandby/SpaceDiversitymode ........................................................................................................ 48 4.3.3 ProtectionStatus ..................................................................................................................................... 52 4.3.4 ProtectionConfiguration ......................................................................................................................... 52 4.3.5 AdvancedProtectionConfiguration ........................................................................................................ 53

4.4 SystemConfiguration .................................................................................................................... 54 4.4.1 UserConfiguration .................................................................................................................................. 54 4.4.2 NamesConfiguration .............................................................................................................................. 56 4.4.3 Otherconfiguration ................................................................................................................................ 56


SAF Tehnika JSC 2011 3

4.4.4 UpgradeSoftware ................................................................................................................................... 56 4.4.5 Serviceinformation ................................................................................................................................. 57

4.5 IPConfigurationWindow .............................................................................................................. 58 4.5.1 EthernetmanagementportIPconfiguration .......................................................................................... 58 4.5.2 IPServices ............................................................................................................................................... 58 4.5.3 StaticRouteConfiguration ...................................................................................................................... 58

4.6 EthernetConfiguration .................................................................................................................. 61 4.7 Aggregationconfiguration ............................................................................................................ 62

4.7.1 Linkaggregationn+0 ............................................................................................................................... 62 4.7.2 Aggregationstatus .................................................................................................................................. 64

4.8 VLANConfiguration ....................................................................................................................... 64 4.8.1 EthernetSwitchPortStatusandSettings................................................................................................ 66 4.8.2 EthernetSwitchVLANStatusandSettings .............................................................................................. 66

4.9 QoS ................................................................................................................................................ 69 4.9.1 GeneralConfiguration ............................................................................................................................. 69 4.9.2 QoS802.1pConfiguration ....................................................................................................................... 71 4.9.3 DSCPConfiguration ................................................................................................................................. 72

4.10 SpanningTreeConfiguration ......................................................................................................... 73 4.10.1 SpanningTreeConfiguration ................................................................................................................... 74 4.10.2 Region,mappingconfigurationforMSTP ............................................................................................... 76 4.10.3 SpanningTreeProtocolstatistics ............................................................................................................ 76

4.11 SNMPConfiguration ...................................................................................................................... 77 4.11.1 SNMPcommunityconfiguration ............................................................................................................. 78 4.11.2 SNMPAllowedHostsConfiguration ........................................................................................................ 78

5 PerformanceandAlarmManagement ........................................................................................ 79 5.1 AlarmManagement ...................................................................................................................... 79

5.1.1 AlarmsandEventsStructure ................................................................................................................... 79 5.1.2 AlarmsEventsandGroupsTables ........................................................................................................... 79 5.1.3 AlarmStatusWindow ............................................................................................................................. 82 5.1.4 AlarmLog ................................................................................................................................................ 82 5.1.5 AlarmandAlarmThresholdConfiguration ............................................................................................. 83 5.1.6 AlarmManagementCommands ............................................................................................................. 85

5.2 PerformanceManagement ........................................................................................................... 86 5.2.1 PerformanceManagementDataCollection ............................................................................................ 86 5.2.2 PerformanceValues ................................................................................................................................ 87 ThresholdSeconds(TS) .......................................................................................................................................... 87 TideMark(TM) ...................................................................................................................................................... 87 5.2.3 PerformanceManagementinWebGUI .................................................................................................. 87 5.2.4 ConstellationDiagram ............................................................................................................................. 90 5.2.5 AdaptiveEqualizer .................................................................................................................................. 92 5.2.6 PerformanceManagementCommands .................................................................................................. 93

5.3 Ethernetmodemstatistics ............................................................................................................ 94 5.4 Ethernetswitchstatistics .............................................................................................................. 97

6 MiscellaneousControlsinWebGraphicUserInterface .............................................................. 101 6.1 ConfigurationFile ........................................................................................................................ 101 6.2 LicenseManagement .................................................................................................................. 102 6.3 CommandLine............................................................................................................................. 103 6.4 FileSystem ................................................................................................................................... 104 6.5 SecurityCommands ..................................................................................................................... 105

7 SoftwareUpdate ..................................................................................................................... 107 7.1 UpdateSoftwarewithUpdatePack ............................................................................................ 107 7.2 FileUploadviaEthernetManagementPort(TFTP) ..................................................................... 108 7.3 UploadingFileviaEthernetManagementPort(FTP).................................................................. 109 7.4 UploadingFileviaSerialPort(Xmodem) ..................................................................................... 110

8 CFIPDiscoveryProtocol ........................................................................................................... 112 8.1 CFIPUnitDiscoveryProcedure .................................................................................................... 112 8.2 DiscoveryProtocolPerformanceExamples ................................................................................. 113



8.2.1 DiscoveryofIPAddressandFirmwareVersioninCaseTheSubnetofCFIPUnitisUnknown .............. 113 8.2.2 DiscoveryofIPAddressandFirmwareVersioninCaseTheSubnetofCFIPUnitisKnown .................. 114 8.2.3 DiscoveryofIPAddressandFirmwareVersionofRemoteCFIPUnitConnectedtoRouterInCaseone

IPaddressofRemoteUnitsisKnown ................................................................................................... 115 9 RSSIPort ................................................................................................................................. 116 10 Pinouts ................................................................................................................................... 117 10.1 SealedRJ45socket ..................................................................................................................... 117 10.2 E1port ......................................................................................................................................... 117 10.3 Alarmport(26pinDSUB) .......................................................................................................... 117

11 AvailableAccessories ............................................................................................................... 119 11.1 OtherAvailableAccessories ........................................................................................................ 120

12 ListofAbbreviations ................................................................................................................ 122 13 SAFTehnikaJSCContacts ......................................................................................................... 124



5

Proprietarynotice

TheinformationpresentedinthisguideisthepropertyofSAFTehnika,JSC.NopartofthisdocumentmaybereproducedortransmittedwithoutproperpermissionfromSAFTehnika,JSC.

Thespecificationsorinformationcontainedinthisdocumentaresubjecttochangewithoutnoticeduetocontinuingintroductionofdesignimprovements.Ifthereisanyconflictbetweenthisdocumentandcompliancestatements,thelatterwillsupersedethisdocument.

SAFTehnika,JSChasnoliabilityfortypingerrorsinthisdocumentordamagesofanykindthatresultfromtheuseofthisdocument.

Togetuptodateinformationaboutaccessoriesandtheiravailability,pleasecontactsalesrepresentative.

Note:FODU/ODUdoesnotcontainserviceableparts.WarrantywillnotbeapplicableintheeventFODU/ODUhasbeenhermeticallyunsealed.

Note:SAFTehnika,JSCisnotresponsibleforanyradioorTVinterferencecausedbyunauthorizedmodificationstothisequipment.Suchmodificationscouldvoidtheuser'sauthoritytooperatetheequipment.

CopyrightNotice

Copyright2011SAFTehnika,JSC.Allrightsreserved.1 OverviewThisdocumentbrieflydescribestheCFIPPhoeniXseriesTDM/IPsplitmountsystem(IDU+ODU)coveringthebuiltinmanagementsystem,configurationfunctionality,hardwarefeatures,etc.1.1 CFIPPhoeniXTDM/IPsplitmountsystemCFIPproduct family is thenewnextgenerationproduct linewhich is targetinggrowingdemands fordatatransmissionovermicrowaveradio.As a result the primary traffic interface for CFIP splitmount system is Gigabit Ethernet. As CFIP iscapableofprovidingbitrateofupto366Mbps, it isagreataddition toSAFportfolio.CFIPradioandmodem performance allows achieving high system capacity by employing 256decision statesmodulationschemebyuserschoice.Apartfromthefullsystemcapacityof366Mbps,itispossibletoconfiguretheradiotoanyof3.5,7,14,28,40and56MHzchannelsaswellastoanyofQPSK,16APSK,32APSK, 64QAM, 128QAM and 256QAM modulations, thus providing various capacities to suitparticularneeds.SAFTehnikahasemployedmostmoderndesignsolutionsandcomponentstocreatehighperformancesplitmountsystemwithlowpowerconsumption3369Wpersystem.CFIPisaperfectbuildingblockforanymodernfutureproofwirelessnetwork,includingmobileserviceproviders, fixeddata serviceoperators, enterprise customers,municipal and governmentalnetworksamongothers.1.2 CFIPPhoeniXfeatureSummary



1.2.1 MainFeatures Splitmountsystemsolution Capacity:upto366Mbps ChannelBandwidth:3.5/7/14/28/40/56MHz Modulations:QPSK/16APSK/32APSK/64QAM/128QAM/256QAM Interfaces:10/100/1000Eth+20E1/T1 Traffic:Ethernetonly,Eth+1E1/T1toEth+20E1/T1 Frequencybands:6/7/8/10/11/13/15/18/23/26/38GHz ACMandATPCwithQoSfourpriorityqueues 802.1QVLANsupport

1.2.2 IDUmechanicalfeatures 1Uhigh Powerconsumption:2030W Dimensions45x430x240mm,weight3kg.

Figure1.1:CFIPPhoeniXIDU

1.2.3 ODUmechanicalfeatures Compactunit,285x285x80mm,3.9kg,antennaadaptionbackwardscompatiblewithallCFM

andCFQseriesunits 3handlesforuserconvenience Safeandeasytouse4sidelockingarrangement Allconnectorsonthesideoftheunit,alwaysat45regardingverticalaxisforbothVandH

polarization Powerconsumption:1339W



Figure1.2:CFIPPhoeniXODU

1.2.4 Interfaces/Management CFIPPhoeniXIDUunitprovidesEthernet,E1,power,EOW,alarm,serial,1+1,ODUconnectors

andagroundingscrew 4GigabitEthernetportsforuserandmanagementtraffic EthernettrafficsupportsQoSand4priorityqueues,essentialforACMuse UserandNMS trafficcouldbe treatedasa singledata streamor separatedby taggingwith

differentVLANtags DB9connectoroftheunitenablesserialaccessintotheunit 1+1RJ45connectorallowstointerconnect2CFIPPhoeniXIDUsfor1+1configuration Web,TelnetandSNMPareavailableasNMSinterfacesintotheunit

Figure1.3:CFIPPhoeniXIDUconnectors



1.3 CFIPPhoeniXODUParameters

CFIP PhoeniX is a good example of latest achievements in modem and transceiverdevelopment,providingbothexcellent radioparameters (SystemGain),due touseofAPSKandQAMmodulationsandefficientdespiteitconsumessmallamountofpowerTx/Rxpartofthesystem.

RSLThresholdatfor6GHzODUBER106,56MHz,256QAM,366Mbps:64dBm. SystemGainwithguaranteedmaxTxpowerandRxsensitivityis76dB(SP)and84dB(HP) ACM (Adaptive Coding andModulation), hitlessACM opens new possibilities depending on

networkdesignersstrategy ATPC,AutomaticTransmitterPowerControl,forincreaseddeploymentdensitycapability. Veryhighflexibilityallowsconfiguringthesystemtovariouschannelbandwidths,modulation

schemesandcapacitysettings

1.4 ApplicationExamples1.4.1 CFIPPhoeniX1+0configuration

Basicsplitmount1+0systemwithupto20E1/T1orupto366MbpsEthernet

Figure1.4CFIPPhoeniX1+0configuration

1.4.2 CFIPPhoeniX1+1HotStandby(HSB) HSBprotected(1+1)configurationisusedwithsingleantennaandacoupler 1+1configurationprotectsmodemandradiofromfailure Txswitching



Figure1.5CFIPPhoenixHSB1+1configuration

1.4.3 CFIPPhoeniX1+1SpaceDiversity InSpaceDiversitymodeantennasarelocated1012metersaparthenceallows

avoidingfrequencyselectivefadingmultipath(e.g.reflectionoverwater,airrefraction,etc.)

Hitless,errorlessswitching

Figure1.6CFIPPhoeniX1+1spacediversityconfiguration

1.4.4 CFIPPhoeniXRingTopology UtilizationofSTPprotocolallowsCFIPPhoeniXoperationinringtoplogy



Figure1.7CFIPPhoeniXringtopologyconfiguration



1.5 TechnicalspecificationCFIPPhoeniXIDU

Modem

Channel Bandwidths 3.5, 7, 14, 28, 40, 56 MHz

Modulations QPSK, 16APSK, 32APSK, 64QAM, 128QAM, 256QAM

Capacity 9 - 366 Mbps

Supported ODUs CFIP ODU

Applications

Configuration 1+0, 1+1 (HSB, SD, FD), Ring/Mesh (with RSTP),

2+0, 3+0, 4+0 (built-in Ethernet aggregation)

Protection switching Hot Stand-by (



12

CFIPPhoeniXODUCFIP ODU RSL at 10-6 (dBm) and Total Payload Capacity (Mbps)

BW***, MHz Modulation FEC**** 6 GHz 7 GHz 8 GHz 10 GHz 11 GHz 13 GHz 15 GHz 18 GHz 23 GHz 26 GHz 38* GHz Bit rate, Mbps

3.5

QPSK Strong -98 -98 -98 -98 -98 -98 -98 -98 -98 -98 -98 4

16APSK Strong -90 -90 -90 -90 -90 -90 -90 -90 -90 -90 -90 8.1

32APSK Strong -86 -86 -86 -86 -86 -86 -86 -86 -86 -86 -86 10.1

64QAM Strong -84 -84 -84 -84 -84 -84 -84 -84 -84 -84 -84 13.5

7

QPSK Strong -96 -96 -96 -96 -96 -96 -96 -96 -96 -96 -96 8

16APSK Strong -89 -89 -89 -89 -89 -89 -89 -89 -89 -89 -89 17

32APSK Strong -86 -86 -86 -86 -86 -86 -86 -86 -86 -86 -86 21

64QAM Strong -83 -83 -83 -83 -83 -83 -83 -83 -83 -83 -83 28

128QAM Strong -79 -79 -79 -79 -79 -79 -79 -79 -79 -79 -79 34

Weak -77 -77 -77 -77 -77 -77 -77 -77 -77 -77 -77 36

14

QPSK Strong -91 -91 -91 -91 -91 -91 -91 -91 -91 -91 -91 17

16APSK Strong -84 -84 -84 -84 -84 -84 -84 -84 -84 -84 -84 34

32APSK Strong -81 -81 -81 -81 -81 -81 -81 -81 -81 -81 -81 45

64QAM Strong -79 -79 -79 -79 -79 -79 -79 -79 -79 -79 -79 57

128QAM Strong -76 -76 -76 -76 -76 -76 -76 -76 -76 -76 -76 68

256QAM Strong -72 -72 -72 -72 -72 -72 -72 -72 -72 -72 -72 79

Weak -69 -69 -69 -69 -69 -69 -69 -69 -69 -69 -69 86

28

QPSK Strong -90.5 -89.5 -89 -88.5 -89.5 -89.5 -89 -90 -89 -91.5 -85 35

16APSK Strong -84.5 -83 -83 -82.5 -83.5 -83.5 -83 -84 -83 -85 -79 69

32APSK Strong -81.5 -80 -80 -80 -80.5 -80.5 -80.5 -80.5 -80 -82 -76 88

64QAM Strong -79 -77.5 -77.5 -77 -78 -77.5 -77 -78 -77.5 -79.5 -73.5 115

128QAM Strong -75.5 -74.5 -74 -73.5 -74.5 -74.5 -74 -75.5 -74 -76.5 -70 139

256QAM Strong -72.5 -71 -70.5 -70.5 -71 -71 -70.5 -72 -71 -73 -67 162

Weak -69 -67 -66 -66 -67 -67 -66.5 -69 -67.5 -70 -63.5 175



CFIP ODU RSL at 10-6 (dBm) and Total Payload Capacity (Mbps)

BW***, MHz Modulation FEC**** 6 GHz 7 GHz 8 GHz 10 GHz 11 GHz 13 GHz 15 GHz 18 GHz 23 GHz 26 GHz 38* GHz Bit rate, Mbps

40

QPSK Strong -89 -87.5 -88 -87.5 -88 -88 -88 -88 -87.5 -89.5 -83.5 50

16APSK Strong -82.5 -81.5 -81.5 -81 -82 -82 -81.5 -82.5 -81 -83.5 -77 98

32APSK Strong -80 -78.5 -79 -78.5 -79.5 -79.5 -79 -79.5 -78.5 -80.5 -74.5 127

64QAM Strong -77 -76 -75.5 -75.5 -76.5 -76 -76 -77 -75.5 -78 -71.5 164

128QAM Strong -74 -73 -72.5 -72.5 -73.5 -73 -72.5 -73.5 -72.5 -74.5 -68.5 196

256QAM Strong -70.5 -69.5 -69 -68.5 -69.5 -69.5 -69 -70.5 -69 -71 -65 229

Weak -68 -67 -64.5 -64.5 -65.5 -65 -65 -67.5 -66.5 -68.5 -62.5 245

56

QPSK Strong -87 -85.5 -86 -85.5 -87 -86.5 -86 -87 -85.5 -88 -81.5 72/67**

16APSK Strong -81 -80 -79.5 -79.5 -80.5 -80 -79.5 -80.5 -79.5 -82 -75.5 145/136**

32APSK Strong -78 -77 -77.5 -77 -78 -77.5 -77 -77.5 -76.5 -79 -72.5 186

64QAM Strong -75.5 -74.5 -74 -73.5 -74.5 -74.5 -74 -75.5 -74 -76 -70 241

128QAM Strong -72 -71 -71 -70.5 -71.5 -71.5 -71 -72 -70.5 -73 -66.5 289

256QAM Strong -68.5 -67.5 -67 -66.5 -68 -67.5 -67 -68.5 -67 -69.5 -63 337

Weak -64 -63 -63 -62.5 -63.5 -63 -62.5 -64.5 -62.5 -65 -58.5 366



14

*Preliminarydata**Withspectrummaskfor128QAMinACMmodehavehighercapacityin16APSKandQPSK***AccordingtoETSIchannelplan****ForwardErrorCorrection(FEC)canbeoptimizedeitherforsensitivity(StrongFEC)orforcapacity(WeakFEC)

1.6 CableRequirementsIDUODUcable

IDUODUcableisa50coaxialcableintendedtointerconnecttheIndoorUnitwiththeOutdoorUnit.Any typeof50cableofgoodqualitycanbeused; thecableshouldbeequippedwithNtypemale connectors on each end. There are two Ntypemale connectors included in each radio unitdeliverythatfitRG213cablesorothercableswithasurfacediameterof10mm.Astheattenuationofthecableisessentialparticularlyat350MHzfrequency,itsusageisrestricted,theattenuationofthesignalshouldnotexceed20dBat350MHz.CommonlyemployingRG213typecoaxialcable,itslengthmayreach100m,LMR400typecablemayusuallyreachupto300minlength.

Figure1.8:CFIPPhoeniXIDUODUcable

DCpowercable

Due to low power consumption of the CFIP PhoeniX splitmount system, there are no specialrequirementsforthecableusedtoconnecttheIDUtotheDCpowersource.Any2wirepowercableof

CFIP ODU Tx Power

Modulation

Standard/High Tx Power, dBm 6, 7, 8 GHz

10, 11, 13, 15 GHz

18, 23, 26 GHz

38* GHz

QPSK +19 / +27 +19 / +25 +19 +12

16APSK +18 / +26 +18 / +24 +18 +11

32APSK +17 / +25 +17 / +23 +17 +10

64QAM +15 / +23 +15 / +21 +15 +8

128QAM +15 / +23 +15 / +21 +15 +8

256QAM +12 / +20 +12 / +18 +12 +5

CFIP ODU waveguide flange sizes 6 GHz 7, 8 GHz 10, 11 GHz 13, 15 GHz 18, 23 GHz 26 GHz 38* GHz

N-type UBR84 UBR100 UBR140 UBR220 UBR260 UBR320

Max. Power consumption SP: 13-27 W; HP: 21-39 W



goodqualitywhichfitswellinSAFTehnikassupplied2polescrewonpowerconnectorcouldbeused.Thepowerconnectoris2pole,type2ESDV02.RS232SerialConnection

TheASCIIconsolemustbe connected to theRS232 serialport.This requiresa twistedpair (TP)cablewithcommonshield(foilandplaitedshield);thecablemustbesuitableforDB9connector.

Usingapropercable,theoperationisguaranteedforupto10mofcable.RSSIBNC

ToconnectthedigitalmultimetertotheCFIPPhoeniXODURSSIportinordertoadjusttheantennaalignment,acoaxialcablewithBNCconnectorononeendandappropriateterminationonotherendcanbeused(seeexampleinFigure1.9).

Figure1.9.CableforconnectingthevoltmetertotheCFIPPhoeniXODURSSIport

1.7 LabellingThelabelcanbefoundonthefrontsideoftheunit.Thelabelcontainsthefollowinginformation(seesamplesinthepicturebelow):

- Modelname.Themodelnameexampleis:- CFIPIDUPhoeniXforCFIPPhoeniXIndoorUnit(IDU),- CFIP13PhoeniXfor13GHzOutdoorUnit(ODU),etc

- ProductNumber (S0GIPK01, S13RFK01LA):productnumber contains informationofproductversion (01), in caseofODU inwhich frequencyband (13) andband side (L,H) theODUoperates.LettersA,B,CorDindicatespecificsubband.

- UnitSerialNumber(320500100011);theserialnumberuniquelyidentifiestheunit.

Figure1.10.LabeloftheCFIPPhoeniXIndoorUnit



Figure1.11LabeloftheCFIPPhoeniXODULowbandside,operatingin13GHzband

P/NTranslationforCFIPPhoeniXODU:SdesignatesCFIPsplitmountseriesproduct;13designatesFrequencyrange(13GHz)oftheUnit;RFdesignatesstandardpowerradio;Udesignateslimitedproductto180Mbps; 01designatestheversionnumberoftheUnit;LdesignatesthebandsideinwhichODUoperates(H,L);AdesignatesthesubbandinwhichODUoperates(A,B,C).

Pleasenotethatfrequencyrangeissetfromthecentralfrequencyofthefirst14MHzchanneltothe

centralfrequencyofthelast14MHzchannel(seetheFigurebelow).

Figure1.12.FrequencyrangeofthelowsideCFIPPhoeniX13GHzODU

TheFigureexplainsTxfrequencyrangeoflowsideCFIPPhoeniX13GHzradio.



2 ConfigurationandManagement2.1 ConnectingCFIPPhoeniXIDUtopowersource

IncaseAC/DCPowersupply,48VDC,80W(EUP/NI0AB4810,USP/NI0AB4811,AUSI0AB4818)providedbySAFTehnikaJSCisusedtopowerupCFIPPhoeniXIDU,interconnectIDUandpowersourcethroughappropriateconnectors.OtherwiseperformthefollowingstepstoensurethatCFIPPhoeniXIDUispoweredupcorrectly:1. ItisnecessarytointerconnectCFIPPhoeniXIDUDCpowerconnector(locatedonleftsideoffront

panel)withpowersource.Forthispurposepowercableisrequired.Any2wirepowercableofgoodqualitywhichfitswellinSAFTehnikassupplied2polescrewonpowerconnectorcouldbeused.Thepowercableconnectoris2pole,type2ESDV02.Thisconnectorhasscrewclampterminalsthataccommodate24AWG to12AWGwire. The recommendedwire size forconstructionofpowercablesunder3meters in length,supplying 48VDC, is18AWG.Theoppositeendof thepowercableshouldhavea terminationappropriate for thepowersupplybeingused. Thepowercableshould be of sufficient length to avoid tension in the cable and provide a service loop forconnection,butnotbeofexcessivelength.Usingthepowercableconnectoroftype2ESDV02,pin1 (labeled )shouldbeconnected to thepowersupply terminalsupplying 48VDC,whilepin2(labeled+)shouldbegrounded.RefertoFigure2.1.

2. Connect thepower cable to the 48VDCpower supply, andplace the voltmeterprobes at theunconnectedendsofthepowercable,withthepositivevoltmeterprobeonpin1()ofthecableconnectorandthenegativeprobeonpin2(+).Theconnectorscrewterminalscrewheadsmaybeusedasconvenientmonitorpoints.RefertoFigure2.1.

3. Turnonthe48VDCsupply.Verifythatthedigitalvoltmeterreadsbetween36VDCand57VDCwhenmonitoringthecablepointsspecifiedabove.Adjustthepowersupplyoutputvoltageand/orchangetheconnectionsofthepowersupplytoachievethisreading.

4. Withthenegativevoltmeterprobestillonpin2(+)ofthepowercableconnector(andthepowersupply still on), put the positive voltmeter probe to the CFIP PhoeniX IDU chassis and verify apotentialofzerovoltsbetweenthe IDUchassisandcablepin2(+). Ifthemeasuredpotential isnotzero,thepowersupplymaybegroundedincorrectlyandshouldnotbeusedforCFIPPhoeniXIDU powering. Note that this measurement assumes that CFIP PhoeniX IDU is installed andproperlygrounded.Ifthatisnotthecase,thesamemeasurementcanbemadebetweencablepin2(+)andaconvenientground(suchasanacoutletthirdwireground).

5. Turnthe48VDCsupplyoff.6. PlugthepowercableintoCFIPPhoeniXIDUfrontpanelDCPowerconnector(DCInput).Placethe

voltmeterprobesonthecableconnectorscrewterminalscrewheadsasdescribedinstep2above.RefertoFigure2.1.NotethatCFIPPhoeniX IDUdoesnothaveapoweron/offswitch. WhenDCpowerisconnected,thedigitalradiopowersupandisoperational.Therecanbeupto500mWofRF power present at the antenna port. The antenna should be directed safelywhen power isapplied.

7. Turn on the 48 VDC power supply, and verify that the reading on the digital voltmeter is asspecifiedinstep3above.

(!) Notethatpin2(+)oftheCFIPPhoeniX IDUDCPowerconnector isconnectedtothe IDUchassis ground internal to the IDU. Use of a power supply with an inappropriate groundreferencemaycausedamagetoCFIPPhoeniXIDUand/orthepowersupply.



Figure2.1.CFIPPhoenixIDUDCPowerCableConnectoroftype2ESDV02

AftersuccessfulpoweringofPhoeniXIDUtherearefourwaystoadjustandreadsettingsandoperationparametersoftheCFIPPhoeniXequipment:1. usingWebterminalconnectedtothe10/100/1000BaseTPort,2. usingTelnetterminalconnectedtothe10/100/1000BaseTPort,3. usingNMSorSNMPterminal,connectedtothe10/100/1000BaseTPort,or4. usingASCIIconsoleconnectedtotheserialport.

2.2 ResettingtheCFIPPhoeniXDependingonthemethodused,theusermayresetthewholeterminalorthemanagement

controllerindividually,seetablebelowfordetails.Resetactionunpluggingpowersource. Restartsboththemultiplexermoduleandthemanagement

module.Resetsallmanagementcounters.

Resettingwith buttoninWebGUIConfigurationSystemconfigurationwindoworusingcommandpromptcommandsystemreset

RestartsCPUofthemanagementcontroller.Resetsallmanagementcounters.

Resettingwithcommandpromptcommandsystemresetcold

RestartsmodemandCPUofthemanagementcontroller.Resetsallmanagementcounters.

2.3 WebInterfaceThissectiondescribesoperationofWebinterface.

2.3.1 10/100/1000BaseTPorts10/100/1000BaseTportisusedtoconnectCFIPPhoeniXtoaPCorEthernetnetworkforWeb,

SNMPandTelnetmanagement.(!)Thelengthof10/100/1000BaseTPortcableshouldnotexceed100m.

2.3.2 EthernetManagementConnectionConfigurationBeforeyouproceedtoinitiallinksetupwithWebGUI,youmustperformEthernetconnection

configurationbyfollowingthesesteps:



1) InMSWindowsoperationalsystemgotoStartSettingsNetworkconnections(orStartSettingsControlpanelNetworkconnections)

Figure2.2.

2) FindLocalAreaConnection,clickrightmousebuttononitandchooseProperties

Figure2.3.

3) ClickonInternetProtocol(TCP/IP)fromthelistinthedialogboxandthenclickon

Properties



Figure2.4.

4) Inthedialogboxenterthefollowingvalues(sothatyourPChasthesamesubnetasdefault

CFIPPhoeniXaddresses):

Figure2.5.



NowyouarereadytoconnecttoWebGUIorestablishTelnetconnection.

2.3.3 ConnectingtoWebInterfaceItisrecommendedtousethefollowingwebbrowsers(andalllaterversions): IEv.6.0 MozillaFirefoxv.2.0.0.11 Safariv.3.0 Operav.9.50 GoogleChrome

Afterwebbrowsersselection,openitandenteraddressofCFIPPhoeniX(Figure2.6).(!)TheIPaddressofCFIPPhoeniXIDUis192.168.205.10

Figure2.6.CFIPPhoeniXIPaddress

(!)ThedefaultusernameandpasswordforWebaccessare: username:admin password:changeme

Ifthe IPaddress iscorrectandyouhavesuitablebrowserversion,youwillseeconfirmationtext.

AfterconfirmationyouwillberedirectedtoWebinterfacepage.IncaseofnotvalidIPaddressyouwillnot obtain the configuration interface. In case your browser is not accepted, youwill see the textinformingaboutthat.YoucanpushthebuttonContinueAnywaytoberedirectedtoWeb interfacepage.

AtfirstConfigurationConfigurationwizardshouldberuninordertoperformbasiclinkconfiguration(bydefaultTxpowerisdisabledandparametersofremotesidewillnotbeseen).

Ifconfigurationwasmadecorrectly,youwillseethemainwindowoftheWEB Interface. If inthefielddisplayingLocaland/orRemotesystemvaluesthereareproblems(configuredvaluesarenotthesame forLocalandRemote,or there isaproblemwithparametervalue), theappropriatecellwillbehighlightedinredcolour.

(!)IfyouarenotobtainingthecorrectWebpage,trytoclearbrowsercookies,cacheandofflinedataandrestartthebrowser.

(!)AllthecommandsexecutedfromWebGUIwillbeinterpretedCLIcommandsandwillbeexecutedasinCLI.



Figure2.7.WebInterfacemainwindow

2.3.4 InterfaceDescriptionWEBinterfaceconsistsoffourparts,theyare:1. Toppanel, thatallows to logoutandgives informationaboutdevice type,softwareversion,

devicename,IP,serialnumberanduptime;2. Menupanelthatisusedtoopenlinkstootherpages;3. Status summary for local and remotedevices: this section is availablewhilebrowsingother

pages.4. Themainpanelwherethenewpagesselectedfromthemenupanelaredisplayed;

Also,specialmarksareused:



Entrieshighlighted in red indicate thatspecificparametersdonotcomplywith thenormsofstandardoperation.Forexample:value isoutofrange; localvalue isnotequaltotheremotevalueandviceversa(onlyinsomeplaces);novaluedata(N/D).

Entryhighlightedinyellowindicateswarning. N/DinvalueplacecorrespondstoNoData.. N/AinvalueplacecorrespondstoNotAvailable.

Figure2.8.WebInterfacemainwindowwithsectionnumbering

2.3.5 CommandExecutionThereisIPconfigurationpageshowninFigure2.9.Theentirepageisdividedintosmaller

fragments:1. Theheaderofpage;



2. Subheaderofsingletypeconfigurationparameters;3. Executioncontrolsrelatedtoasingletypeconfigurationparameters.4. Execute configuration button executes configuration changes only on the local side CFIP

PhoeniX,butExecuteforbothexecutesconfigurationchangesonbothremoteandlocalsideofCFIPPhoeniX link.Enablingrollback featureallowsgoingback topreviousconfiguration incaseofmanagementconnectivityloss.

5. Write to config filebutton,whichgenerates cfgwriteCLI command,which saveschangedconfiguration;

6. Configurationparametername;7. Configurationparametercurrentvalue;8. Comments(notoneverypage).

ExecuteforbothisavailableinMainconfigurationsectionduringconfigurationofmodemor

ATPCparametersforlocalandremoteradiosidessimultaneously..ConnectionbetweenbothmanagementCPUsmustbeestablishedinordertocompletesuccessfullyconfigurationexecutionforbothsides.

RollbackonfeatureisintendedtomaintainconnectivityoftheCFIPlinkbycancellinglasterroneousconfigurationchangesandrevertingtoprevioussuccessfulconfigurationused.RollbackwillactivateonlyifyouloseconnectiontoWEBinterfaceofCFIPPhoeniXafterconfigurationchangesapplied,andrevertingprocesswilltakeapprox.3minutes.

Afterparametervalueediting,whenthefocusfromthisobjectisremoved,thisparametervalue

editboxmaybehighlightedinred,meaningthatenteredvalueisnotvalid.IfExecuteconfigurationorExecuteforbothbuttonsarepressed,andoneorseveral

configurationvalueseditboxesis/arehighlightedinred,theuserwillseeerrormessagewiththeexplanationtext.

Figure2.9.WebInterfaceIPconfigurationpagewithnumbering



2.3.6 InitialConfigurationwithWebGUIYour connected laptop shouldhave the same subnetasmanageableCFIP inorder toobserve it.

ThereforelaptopEthernetportsettingsshouldbesetasfollows:(inMicrosoftWindowsgotoControlpanelNetworkConnectionsLocalAreaConnectionProperties InternetProtocol(TCP/IP)Properties):

IPaddress192.168.205.1; netmask255.255.255.0; everythingelseisblank.

Figure2.10.

ThenextstepistoconnecttoCFIPPhoeniXbyenteringIPinthebrowseraddresslinewhichisby

default192.168.205.10.Incaseyouarenotsurewhichsideyouaremanagingatthemoment,youcantrybothdefaultIPaddresses.

CurrentlysupportedbrowsersyoucanuseareInternetExplorer,MozillaFirefox,AppleSafari,OperaandGoogleChrome.

Figure2.11.Supportedbrowsers:InternetExplorer,MozillaFirefox,AppleSafari,Operaand

GoogleChrome

(!)CFIPPhoeniXmustbepoweredupusingdedicatedpowersupplywithloadpoweratleast35W.SeeChapter2.2.4fordetails.



WhenyouareconnectedtotheCFIPPhoeniX,youwillseethewindowsimilartotheoneshown in

Figure2.7.Tostartsimpleconfigurationprocess,youmustproceedwiththeconfigurationwizardwhichwillset

up themainparametersof the link tomake itwork. So, the first step is to go to ConfigurationConfigurationwizardasshownbelowintheFigure2.12.

Figure2.12.Startingconfigurationwizard.

Initially,youcanspecifypreferablesystemname,passwordsforguestandadminaccounts.

ThenexttimeyouwilltrytoaccesstheWebGUImanagement,youwillbeaskedtoentertheuser

name(guestoradmin)anduserpassword.

Bydefault,systemnameisSAF.Itispossibletoperformconfigurationforlocalandremoteendsofthelinksimultaneously.Please

notethatitrequiresmodemsynchronizationbetweenbothsidesofthelink.

Figure2.13.STEP1.Definingsystemnameandpasswordsforguestandadminaccounts.

(!)Defaultpasswordforadminaccountischangeme.guestaccountisdisabledbydefault!

(!)Itishighlyrecommendedtonamethesystemafteritsgeographicallocation.



After accepting and pressing Next step >> button, you will be redirected to the secondconfigurationwizardscreen,whereyouwillbeaskedtodefinethenetwork IPsettingsbyentering IPaddress,IPmask,defaultgatewayandremotelinksideIPaddress.

Figure2.14.STEP2.DefiningIPaddress,mask,defaultgatewayandremoteIPaddress

The third screen of thewizard is devoted to themodem and radio configuration and requires

specifyingutilizedbandwidth (from7 to56MHz),modulation type (QPSK,16APSK,32APSK,64QAM,128QAMor256QAM),E1channelportnumbers,Txpower(rangedependsonmodulationchosen)andTxfrequency;besides,themodemandradiodatastatusisbeingshown.

Figure2.15.STEP3.Definingmodembandwidthandmodulation

Thefinalscreenallowscheckingtheselectedsettingsandapplyingthem.Theoptionalsettingsare

asfollows: Clearcfg filebefore thenew settingswill takeplace resettingorkeepingall theother

parameters,notmentionedhere,afterconfigurationexecution Setlocalmachinetimeusesthetimeofyourlaptop Write thisconfiguration intocfg fileconfiguration isautomaticallywritten inconfigure

tionfile



Figure2.16.STEP4Checkingsettingsandexecutingconfiguration

To verify the settings,we can go to Statusor themain screen,which is the firstoption in the

navigationpanel.Iftherearenoredfields,everythingissetcorrectlyandthelinkisup.

2.4 CommandPromptInterfaceCFIPequipment canbemonitoredand configuredbyusing command interfacedescribed in this

chapter.Thisprocess isperformedbyconnecting toTelnet terminalviaEthernetmanagmentport;Telnet

managementsupportsonlyoneclient.Command linemanagement interfaceoffersthewiderconfigurationandmonitoringfunctionality.

The available commands for Telnet management are found in detailed explanation of Web GUIwindows,aswellasintablesofadditionalcommands.

(!)ToendTelnetsessionpressCtrl+D.Openingthesessionagain,thepromptwillappeartoenterusernameandpassword.Fordefault(factory)usernamesandpasswordspleaserefertoChapter6.1.



2.4.1 RS232SerialManagementPortRS232 serialmanagement port provides terminalmanagement via a connected PC or another

terminaldeviceormodem.Theterminalconnectedtoserialmanagementportprovidesthesamemanagementfunctionalityas

Telnet interfaces (refer to Chapter 2.3.2). In order to interconnect the CFIP PhoeniX and themanagementterminaldirectlythroughserialports,astraightthroughmodemcableisrequired.

Figure2.17.SerialconnectiontoCFIPPhoeniX

To connect the PC to the RS232management port using Hyper Terminal program (program isincludedinanyWindowsversion),proceedasdescribedbelow. 1.ConnectthePCtotheRS232serialportbymeansofstraightthroughormodemserialcable

(nullcable). 2.RunHyperTerminalprogram. 3.MakeaNewconnectionandentertheconnectionname.

(!)Syntacticnotesforcommandpromptcommands Commandsareinboldfont. Allarguments(variables)areinitalicfont. Subcommandsandkeywordsareinregularfont. Argumentsinsquarebrackets([])areoptionalbutrequiredargumentsareinanglebrackets

(). Alternativekeywordsaregroupedinbraces({})andseparatedbyverticalbars

(|). Thepurposeofeachcommandwillbedisplayedifcommandistypedwith?attheend(or

anyunrecognizablestring)isentered,e.g.,radio?Themanagementsystemisautomaticallyrestartedifitfreezes.Thisisperformedbythewatchdogtimer.Restartofthemanagementsystemisnotaffecting(interrupting)theEthernettraffic.



Figure2.18.

4.Chooseport(COM1orCOM2).

Figure2.19.

5.Setportsettings(bitspersecond:19200,databits:8,parity:none,stopbits:1,dataflowcontrol:

none).



Figure2.20.

6.PressOK 7.PressEnter.Passwordisdisabledbydefault.

Ifsuccessfullyconnected,thepromptshouldappearasinthepicturebelow.SeeChapters37foravailablecommands.

Figure2.21.

2.4.2 TelnetconnectionThe Telnet connection to the CFIP PhoeniX is carried out using the Ethernet management

connection.PleaserefertoChapter2.2.2forEthernetmanagementportconnectiondetails.



WhenyouarereadytoconnecttoTelnetinterface,pleasefollowthesesteps:

1) GotoStartRun

2) Type in telnet,where is IP addressof theCFIPPhoeniX youwanttoconnectto(refertoCFIPPhoeniXlabelexplanationinChapter1.8)

3) IftheEthernetmanagementconnectionisconfiguredproperly,youwillseeawindowsimilartotheoneshownbelow,whereyouwillbeaskedtoenterloginandpassword.Default login is identical toWEB loginnameusername isadminandpasswordchangeme.



Figure2.22.

After you have correctly entered the login and password, you are ready to work with all the

availablecommandpromptcommands.

2.4.3 InitialConfigurationwithCommandPromptConfigurationstepsusingcommandpromptareasfollows:1. Checkthesystemsettingswithcommandstatus2. Configurationrequiredparameters:

Txpowerwiththecommandradiotxpower[]; Txfrequencywiththecommandradiofreq[]; Channelbandwidth,modulation,FECmodeandchannelmaskwiththecommand

modemset,whereyoucanchooseamong3.556MHzvaluesandmodulationsQPSK256QAM;

NameofCFIPPhoeniXwiththecommandsystemname.DefaultnameisSAF; IPaddresswiththecommandnetipaddr,ifitisnecessary; IPmaskwiththecommandnetipmask,ifitisnecessary; IPdefaultgatewaywiththecommandnetipgw,ifitisnecessary;

3. Savesettingswiththecommandcfgwrite;restartingwiththecommandsystemreset;4. Checkthesettingsmade,modemandradiostatuswiththecommandsstatus,modemstatus

andradiostatusrespectively.

2.5 LEDindications2.5.1 CFIPPhoeniXIDUalarmLEDindications

BelowyoucanseetablesummarizingwhichalarmseachofCFIPPhoeniXIDULEDsrepresents.

(!)Beforeyousettheparameterslistedbelow,youmustknowwhatfrequencyandbandwidthyouareallowedtouseandatwhatpoweryouareallowedtotransmit.



LEDname Description

ODU

GreenOKYellowblinksODUTxmute.YellowRxlevelalarm;ODUTemperaturefailure;IDUPSUtoODUstatealarm.RedTxPLLerroralarm;RxPLLerroralarm;ODURXLOS;ODUTXLOS;ODURXfailure;ODUTXfailure;ODUFrequencyfailure.RedblinksNodatafromODU.

IDU

GreenOKYellowIDUtemperaturefault;Mainsupply48Vfailure;IDUPSUstatealarm;PSUtemperaturefault;Powersupplyvoltagefailure.RedblinksNodatafromIDUtemperaturesensor;NodatafrommainPSUIDUADC;NodatafrommainPSUODUADC;NodatafromPSUtemperaturesensor;NodatafrompowersupplyADC.

ModemGreenOKYellowRadialMSE;LDPCdecoderstress;RXcarrieroffset.RedAcquirestatusalarm;Lastacquireerrorstatus.RedblinksNodatafromMODEM.

SystemGreenOKaftersuccessfulboot.GreenblinksSystembooting.YellowLicenseexpired.YellowblinksInvaliddevicelicense.RedBootfailureorselftestfailure.

2.5.2 EthernetRJ45connectorLEDindications2.5.3 E1RJ45connectorLEDindications

E1 port LED (highlighted) Color Description

Green (loop-back LED yellow or off)

Indicates normal operation of the channel, no problems with signal reception.

Red (loop-back LED yellow or off)

Constant red indicates that E1 signal is lost. If red flashes momentarily, the bipolar violation (line code error) was received from user equipment.

Blinking green and red (loop-back LED yellow or off)

AIS signal is being received from user equipment.

Yellow loop-back LED (loop-back switched on)

When loopback LED is switched on, analog, digital or remote loop-back mode is active for that channel.

No LED is lit Channel is switched off.



3 StatusWindowThemainwindowintheWebGUIisstatuswindowthatshowsallmainsystemparameters,and,in

caseoffailureoranyotherproblems,ittintsaspecificparameterinred.Tohaveabetterunderstandingonstatuswindow,wewillgothrougheveryfield.

Figure3.1.

1. ShowsthenameofthisCFIPPhoeniX, itsIPaddress,serialnumberanduptimesince

thelastrestart.Ifuptimeisdisplayedinred,theconnectiontoCFIPmanagementportwaslost;

2. ShowsthefirmwareversionthisCFIPPhoeniXiscurrentlyusing;3. LogoutbuttonallowsendingthecurrentWebGUImanagementsessionandloggingin

as a different user if necessary. After pressing the button, you are automaticallyredirectedtotheloginpage;

4. ThetreeofWebGUIsections;



5. Shows short summary of the main operational parameters of local and remotesystem.

Rxlevel(orRSL)atbothendsmustnotdiffersignificantlyfromthepreviouslycalculatedvalue.

Modulation indicateswhichmodulationmode isused.Forbetteroperationthesamemodulationmustbesetatbothends.

RadialMSEisexplainedbelowintheChapter3.1. LDPCisexplainedbelowintheChapter3.2.

6. ODUdatastatusshowsifmanagementCPUwasabletoreaddatafromradio;7. ODUsideshowstheradiosideoflocalandremoteCFIP(commandlineradioside);8. Txmuteshowsiftransmitteriscurrentlymuted;9. Txpowershowscurrenttransmitterpower indBm.Factorydefaultsetting isOff

(commandlineradiostatusorstatus);10. ATPCshowsifATPCisenabledordisabled(commandlineatpcstatus);11. Rx levelshowscurrent levelofreceivedsignal. Itmustnotdiffersignificantly from

thepreviouslycalculatedvalue(commandlineradiostatusorstatus);12. Duplexshiftshowsthemarginbetweenthetransmittingandreceivingfrequencies

(commandlineradiostatus);13. Txfrequencyshowsthetransmittingfrequency(commandlineradiostatus);14. Rxfrequencyshowsthereceivingfrequency(commandlineradiostatus);15. Configurationfileshowswhichconfigurationthemodemiscurrentlyusing.Itshould

matchonbothsidesofthelink(commandlinemodemconfiguration);16. Bandwidth showswidthof currentlyutilizedbandwidth inMHz (command line

modemstatusorstatus);17. Modulationshowsmodulationmodeset(commandlinemodemstatusorstatus);18. Totalcapacityshowstotalcapacityset(commandlinemodemstatus);19. Ethernet capacity showsEthernet capacity set (command linemodem statusor

status);20. E1channelsshowsnumberofE1channelsset.Thenumbermustbeequalatboth

ends(commandlinemodemstatusorstatus);21. IDUdatastatusshowsifmanagementCPUwasabletoreaddatafrommodem;22. IDUstatusindicatestheacquirestatusofthemodem.ACQUIRE_IN_PROGRESSwill

appear during startup,whenmodem acquires required parameters, but in normaloperationmodeACQUIRE_LOCKEDwillbeseen.Anyotheroptionsdesignatefailure(commandlinemodemstatusorstatus);

23. RadialMSEshowsradialmeansquareerrorvalue.RefertoChapter3.1.fordetaileddescription(commandlinemodemstatusorstatus);

24. LDPC decoder stress shows the load of LDPC (lowdensity paritycheck code)decoder. Refer to Chapter 3.2. for detailed description (command line modemstatusorstatus);

25. ACM engine shows if ACM (Adaptive Coding andModulation) engine is running(commandlinemodemstatusorstatus);

26. Current modulation Rx / Tx shows the modulation modes currently utilized(commandlinemodemstatus);

27. Current total capacity Rx / Tx shows the current capacities in both directions(commandlinemodemstatus);

28. Current Ethernet capacity Rx / Tx shows the current Ethernet capacities in bothdirections(commandlinemodemstatus);



29. E1statusshowsiftheE1channelisconnectedornotandshowsstatusofLOSandAISindications.Toseethestatus,clickonthetext(commandlinee1status);

30. Diagnostics data status shows if system parameters are in acceptable margins(commandlinediagnostics);

31. IDU temperature shows the IDU internal temperature in degrees by Celsius andFahrenheit(commandlinediagnosticsorstatus);

32. ODU temperature shows theODU internal temperature indegreesbyCelsiusandFahrenheit(commandlinediagnosticsorstatus);

33. ModemtemperatureshowsthetemperatureonmodemchipindegreesbyCelsiusandFahrenheit(commandlinediagnosticsorstatus);

34. IDU input voltage shows the input voltage of IDU PSU in volts (command line diagnostics);

35. IDU input current shows the current of IDU PSU in amperes (command line diagnostics);

36. IDUpowerconsumptionshowstheamountofpowerconsumedbyIDUPSUinwatts(commandlinediagnostics);

37. ODUPSUstateshowswhetherODUPSUisoperating;38. IDUoutputvoltagetoODUshowstheinputvoltageofODUPSUinvolts(command

linediagnostics);39. IDUoutputcurrent toODU shows thecurrentofODUPSU inamperes (command

linediagnostics);40. ODU power consumption shows the amountofpower consumedbyODU PSU in

watts(commandlinediagnostics);41. AUXalarminputshowswhichinputsfromfouravailableareactive;42. AUXalarmoutputshowswhichoutputsfromfouravailableareactive;43. Tx polarization shows transmission polarization and position of connectors and

cables(commandlinediagnostics);44. Name (serial number) shows system name and serial number (command line

systemnameandsysteminventory);45. Firmwareversionshowscurrentfirmwareversion.Makesureitisthesameonboth

endsofthelink(commandlinever)

3.1 RadialMSERadialMSEisamethodforestimatingthesignaltonoiseratio.ACMengineusesnormalizedMSE,

whichistheinverseofSNR.ItiscalculatedbydividingtheestimatedMSElevelwiththeenergyofthereceived constellation.RadialMSEpeak value threshold isdependentonmodulationusedand LDPCcoderate.

IftheRadialMSEvaluetrespassesfollowingthresholds,BERattheoutputofLDPCdecoderwillreachthevalueof1.0106:

QPSK 16APSK 32APSK 64QAM 128QAM 256QAMStrongFEC 8.7dB 13.9dB 16.1dB 19.3dB 22.3dB 25.6dBWeakFEC 11.6dB 16.1dB 18.6dB 21.0dB 24.4dB 27.1dB

3.2 LDPCTheLDPCismonitoredforthenumberoferrorsbeingcorrectedontheinputofLDPCdecoder(see

Figure3.1).



Figure3.2LDPCdecoderstructure

[email protected]:forStrongFECmode~4.0102;forWeakFECmode~1.0103AslongasLDPCstressvalueisunderthespecifiedthresholds,theamountoferrors(andBERitself)

ontheoutputofLDPCremainsatzerolevel.



4 DetailedConfigurationinWebGraphicUserInterfaceConfigurationsectioninWebinterfaceallowscustomizingyoursystemtosuityourspecificneeds.

4.1 ODUConfigurationTheODUconfigurationwindowprovidestheconfigurationofCFIPPhoeniXradiopartparameters.

Belowisashortexplanationofprovidedcustomizationfields.

4.1.1 RadioConfiguration

1. ODUdatastatusshowsifmanagementCPUwasabletoreaddatafromtheradio;2. Radiosideshowsifradiosideyouarecurrentlyviewingisloworhigh(commandline

radioside);3. Txpowerallowsyoutodefinetransmitterpower.IftheRSListoohigh(muchhigher

thannormal50dBm),youmightwantto lowertransmitterpower.ToohighRx level(>20dBm)mayevenresultinsynchronizationloss.Theminimumandmaximalvaluesyou can choose are dependent onmodulation type and CFIPmodel.Maximal andminimalTxpowervaluesareshown inthebrackets. (command line radiotxpower[]);

4. Tx frequencyallowsyou toenterpreferable transmitter frequency,hencedefiningutilizedchannel(commandlineradiotxfreq[]);

5. Rx frequency shows thecurrent receiverutilized frequency (command line radiofreq);

6. Duplexshiftshowstheduplexshiftbetweenthetransmitterfrequencyandreceiverfrequency(commandlineradioduplexshift);

7. Txmuteallowsturningtransmitterpoweroff. Itmaybeeffectivewhendiagnosingoninterferenceexistencewhentransmitterpowerofonesideisoff,youshouldnotexperiencesignificantRSLontheotherside(commandlineradiotxmute[on|off]);

8. BypressingExecuteconfigurationchangesmadetothecorrespondingsectionapplyonlyforthelocalsideCFIPPhoeniX.IfRollbackonisselected,configurationwillberevertedincaseerroneousconfigurationchangesareapplied.

9. PressingExecuteforbothapplieschangesmadetothecorrespondingsectionbothforlocalandremotesideCFIPPhoeniX.

4.1.2 ATPCConfigurationToconfigureATPC,itisnecessarytosetRx(remote)minandmaxvaluesandenabletheATPC

feature.



ATPCupdateperiodandATPCdeltaarerecommendedtobeleftunchanged.ItisalsopossibletochangethelimitofTxpowercorrection.

1. ATPC function allows enabling or disabling ATPC (Automatic Transmit Power

Control).Bydefaultthisfeatureisdisabled(commandlineatpc[enable|disable]);2. ATPC update period (1..5) allows defining the period in seconds in which ATPC

parametersarebeingupdated.Bydefault theupdateperiod is1second (commandlineatpcdelay);

3. TxpowercorrectiondisplaystheamountoftransmitterpowerindecibelsATPChascurrentlycorrected(commandlineatpcstatus);

4. Tx power correction limit allows defining the amount of dBATPCwill be able tocorrect regarding initial Tx power value (command line atpc limit );

5. RemotedevicestatusshowsifmanagementCPUwasabletoreaddatafromremotemanagementCPU;

6. Rx (remote) level (90..20 dBm) allows defining themaximum andminimum Rxlevel.ATPC Txpower correctionwillbeperformedonly in caseof exceeding thesedefinedthresholdsRxlevel(commandlineatpcrxminmax);

7. Rx (remote) level shows current Rx level of remote end (command line atpcstatus);


9. PressingExecuteforbothapplieschangesmadetothecorrespondingsectionbothforlocalandremotesideCFIPPhoeniX.

10. Pressing Write to config file saves all the changes made on the whole page(commandlinecfgwrite);

11. PressingWritetoconfigfileforbothsavesallthechangesmadeonthewholepageforbothendsofthelinksimultaneously(commandlinecfgwrite);

12. Execution status in caseoferroror incorrectlyenteredparameter value,orotherproblemsonthewholepagetheinfomessageisbeingshownhere.OtherwiseitsaysOk.

(!)Note,thatATPCismechanismforreducingTxpower,thatswhytomakeproperuseofATPC,transmitterpower(Txpower)mustbesettothemaximumvalue.



ATPCAlgorithm

ACMcanbeimplementedtogetherwithautomatictransmitpowercontrol(ATPC),complimentaryfeatures that enhanceoverall systemperformance.ATPC reduces the average transmittedpower aswellasCCIandadjacentchannelinterference(ACI),whichiscausedbyextraneouspowerfromasignalinanadjacentchannel.Italsoenablesamoreefficientandcosteffectivenetworkfrequencyplananddeployment, as well as eliminating some of the receivers upfade problems by changing thetransmitted power according to the linkmomentary conditions. The lower average Tx power alsoextendstheequipmentsmeantimebetweenfailures.

ATPCcanbeusedtogetherwithACMtocontrolthetransmittedpower inanygivenACMprofile.Differentalgorithmscanbeimplementedtoachievemaximalspectralefficiencyorminimaltransmittedpowerusingbothfeaturesincombination.Oneimplementationcouldtargetmaximalspectralefficacyby trying to reach thehighestACMprofile,while theother iswilling to compromiseon someof thespectralefficiencyenablingCCIandACIreduction.Inanychosenalgorithm,ATPCreducestheaveragetransmittedpower,benefitingeachACMprofileandanylinkcondition.

The localCFIPPhoeniX receives information (each second) aboutRx level from the farendCFIPPhoeniX through the service channel; depending on the received Rx level parameter, the local CFIPPhoeniXadjuststhetransmitterpowerinaccordancewiththealgorithmshownbelow.

Figure4.1.ATPCalgorithm



4.2 IDUConfiguration4.2.1 ModemConfiguration

1. ModemdatastatusshowsifmanagementCPUwasabletoreaddatafrommodem;2. Bandwidthallowschoosingbetween7,10,14MHz(narrowbandCFIPPhoeniXODU)

and 20, 28, 30, 40, 50 and 56 MHz (wide band CFIP PhoeniX ODU) bandwidthsavailable.Thedefaultvalueis7MHzfornarrowbandODUand20MHzforwidebandODU.Thisoptiondependsonbandwidthyouhavepurchased.Thewiderbandwidthyouhave,thehigherwillbetheoveralllinkbitrate.Themaximumbitrateof366Mbpsis available using 56 MHz bandwidth (command line modem set );

3. Modulationallowschoosingbetween256QAM,128QAM,64QAM,32APSK,16APSKandQPSKmodulations.ThedefaultvalueisQPSK.Thehigheristhemodulationorder,thehigheristheoveralllinkbitrate,butworseRSLthreshold.Themaximumbitrateof366 Mbps is available using 256QAM modulation (command line modem set). See below the explanation for Adaptive Coding andModulation and FECmodes;

4. E1channelsallows tochoosepreferableE1channels tobeused.EachE1channelactivated detracts 2.048Mbps from Ethernet capacity. By default E1 channels areturned off (command line modem set );


6. PressingExecuteforbothapplieschangesmadetothecorrespondingsectionbothforlocalandremotesideCFIPPhoeniXlink.

Adaptivecodeandmodulation (ACM) technologyallowsoperators toachievehighcapacitydata

transmissionovermicrowave linksand improvethe linkutilization.Thisreducesbothoperationalandcapital expenditures formaintaining highcapacity links. ACM canmaintain the highest link spectralefficiencypossibleatanygiventimeinanylinkcondition.

Intraditionalvoicedominatedwirelessbackhaultransmissionnetworks,serviceavailabilitylevelsof99.995%arethenorm.

However,newerservicessuchas Internetbrowsing,videostreamingandvideoconferencingcanoperateatmorerelaxedavailability levels.WithuseofQoSprioritizingACMcanallocatetherequiredavailability based on the priority. As a result, highpriority services such as voice enjoy 99.995%availability,whilelowpriorityserviceslikevideostreamingareallocatedlowerpriorities.



UseofQoSprioritizingdefineswhichservicesshouldbetransmittedunderany linkconditionandwhich services should be adaptedwhenever the link condition is degraded and the link payload isdecreased.

Forexample,whenbadweatherhasdecreasedthechannelcapacityofalink,ACMmaintainshighpriority services such as voice data with full bandwidth capacitywhile adapting the bandwidthcapacityoflowandmidpriorityservicessuchasInternetbrowsing(seeFigure4.2).

Figure4.2.ACMbandwidthcapacityadaptation

Fullmodulationrange:256QAM,128QAM,64QAM,32APSK,16APSK,QPSKTraffic can be mapped into different priorities, which define the level of service for each

application.Figure4.3 illustrateshowdifferentservicessuchas richvoiceandvideoaremappedintodifferentclassesofavailability(CoA)suchas99.995%or99.687%.

The implementationofmultiplepriorities increases theavailable capacityup to10 times thatofstandardlinks.Whenconditionsareclear,thewirelesslinkoperatesatmaximumcapacityandprovidesall serviceswith the fulldata rate.When link conditionsarepoorduringharsh rain, forexamplepredefined highavailability services such as voice are not affected. However, the capacity of lowpriority services is adapteddynamically to the changing link conditions. This isdonebyprovisioningbandwidthaccordingtothelinkconditionsandtrafficpriority.

AnACMprofiledefinesthelinkparameters(modulation)foragivenrangeoftheRadialMSE.TheRadialMSErangeofeachprofiledefinesthethresholdforswitchingfromoneACMprofiletoanother.EachACMprofilehasadifferentspectralefficiency,derivedfromitsmodulation.

ThereceivercontinuouslymonitorsthelinkconditionbasedonRadialMSEvalue.Once the estimators at the receiver side show that the linkperformance isnot suitable for the

current ACM profile, an ACM switching processwill be initiated. In case of degradation in the linkperformance,thenewACMprofilewillincludelowermodulation,decreasingthelinkbitrate.TheACMswitchingrateismeasuredindB/sandisakeyfeatureofACMsystems.

In general, thehigher the switching rate, thebetter the systems immunity to rapidRadialMSEchanges.Whentheswitchingisbeingexecuted,thepayloadrateisbeingmodifiedtofittheaggregateddataratetothenewavailablelinkdatarate.

Alternatively,ACMcanalsobeused to increase the linkdistance,resulting inadded linkspectralefficiency.Thesameconceptisimplementedaspreviously,withthemarginsthatwerekeptfor99.995percentbandwidthavailabilitynowusedtoincreasethelinkdistance.Wheneverthelinkconditionsaredegraded,thesystemwillswitchtoanACMprofilewithlowerspectralefficiencytoenablemaintainingthelink.



ThefollowingrealworldexampleillustratesthebenefitsofACM.ConsideraCFIPlinkoperatingat23GHzwith56MHz channel spacing and45.9dB (120 cm) antenna gain.The link isoperating in amoderaterainregionsimilartocentralEuropewithadistanceof15kilometers.

Thesystemoperationissettoaminimalpayloadof69MbpsEthernetfor99.995%availability.Most of the time system would support 366Mbps Ethernet connection instead of a 69Mbps

connection.The systemautomaticallymonitors the link conditionsand changes the capacitywithoutinterruptingthedatatransmission(hitlesschanges),asshowninFigure4.3.

Figure4.3.Linkavailabilityandclassesofservices

In comparison similar system using 256QAM and providing similar capacitywould provide only99,687%ofavailability.Besides, lackofACMwouldnotprovidehigheravailability.Youwouldhavetodecrease thedistance,decreasemodulationor increaseantennasizes toachieve99,995%availabilityforthegivenlink.

Thisexampledemonstrateshowthenewtechnology,basedonanACMmechanism,canplayakeyroleinthedevelopmentofcosteffectivenextgenerationwirelessaccessnetworks,bytakingadvantageoftrafficevolutionfromsynchronousTDMtraffictopacketIPbasedtraffic.

The FEC mode (Weak or Strong) allows increasing overall capacity of the link in terms of

deterioratingRSLsensitivitythreshold.FormoredetailsrefertotableinSection1.6.

4.2.2 LoopbackConfigurationLoopbacktestsareaccessibleusinglocalorremotemanagementmethods.Forsafetypurposesallloopbacks(localandremote)canbesetonafixedtimeintervalonly.Ifno

timeintervalisspecified,thedefaultvalueis60seconds(1minute).



Figure4.4.Loopbackmodes

E1loopbackmodeloopssignalbacktolocalendinboundsofE1interface.E1loopbackmode

must be set on theparticular channel you need to test. If no E1 channels are selected, E1loopbackmodeisnotavailable;

MODEMloopbackmodeloopssignalbacktolocalendafterthemodem; IFloopbackmodeloopssignalbacktolocalendbylinkingintermediatefrequencies.

1. Loopbacknameallowschoosingloopbackmode(commandlineloopback{status|

none|if|modem|e1[far]|e1mask[far]}[]);2. Loopback timeout allows specifying activity time of chosen loopback mode in

seconds(commandlineloopback{status|none|if|modem|e1[far]|e1mask[far]}[]);


4. PressingWrite toconfig filesavesallchangesmade in thewholepage (commandlinecfgwrite);

5. PressingWritetoconfigfileforbothsavesallchangesmade inthewholepageforbothsidesofthelinksimultaneously(commandlinecfgwrite);

6. System returned in caseoferroror incorrectlyenteredparameter value,orotherproblems inthewholepage infomessagewillbedisplayedhere.Otherwise itsaysOk.



4.3 Protectionconfiguration This section describes 1+1 protection implementation for PhoeniX IDU. The possible 1+1configurationmodesareFrequencydiversity(FD),HotStandby(HSB)andSpacediversity(SD).

4.3.1 FrequencyDiversityMode ForFDmodeperformancetwolinksdifferentiatedbyfrequenciesareworkinginparallel.Eachlink uses different frequency pair. One of the links is marked as working and the other one asprotectionlink.Attransmittersidethedataisduplicatedandtransmittedinbothlinks.Atreceiversidedataisreceivedfrombothtransmitters.Thedecoderofworkinglinkthenselectsthepreferredreceiveddata.

AdditionalradioandmodemconfigurationcommandsinTelnet/serialinterfaceCommand Descriptionmodemstatus Showsallthemodemparameters.modemconfigurationshow Displayscurrentconfigurationfile.modemconfiguration Usesseparateconfigurationfile.modemconfigurationembedded Switchesbacktotheembeddedconfigurationlastused.modemfactory[max] Resetsmodemsettingstofactorydefaults(minimumbandwidth,

minimummodulation).maxoptionwillsetmaximumconfiguration(maximumbandwidth,maximummodulation+ACM).

modemipremote[on|off] AllowsenablingmanualremoteIPspecifying(modemipremoteoff).BydefaultremoteIPisbeingobtainedautomatically(modemipremoteon).

modemstandard[etsi|ansi] AllowsswitchingbetweenETSIandANSI(FCC)standards,allowingtoutilizeE1channelsorT1channelsrespectively.

modemcounters[show|clear] ShowsmodemperformancecountersaccordingtoG.826standard.radiofactory[max] Resetsradiosettingstofactorydefaults.BydefaultTxpowerwillbe

turnedoff.maxoptionwillswitchTxpowertothemaximumvalueafterrestart.

radioduplexshift[] Allowsswitchingtodifferentduplexshiftifsupported.radioside[L|H] Allowsswitchingradiosideifsupported.



Setupfor1+1FDProtectionMode

Figure4.5CFIPPhoeniXsetupfor1+1FDmode

1. Connecteach IDU toappropriateODU.Note thatHighODUs shouldbeatone siteandLowODUsatremotesite.

2. IDU pairsmust be interconnected as shown in Figure 4.5. Note that switches of IDU pair(working and protection) are connected through one of the 1000BaseT user data andmanagementportsviaEthernetcable,andmodemsareconnectedthroughspecialextensionportfor1+1protectionviaprotectioncableCAT6(availablefromSAFTehnikaP/NS0ACPP1).

3. ChoosedifferentfrequenciesforworkingandprotectionlinksasshowninFigure4.5:F1andF2.

4. Beforepowerissuppliedtoequipment:- bothIDUsoneachsideofthelinkshouldbegrounded;- switchesof IDUsmustbesettocorrectstate.Forworking linkprotectionmodeswitch

onCFIPPhoeniXIDUfrontpanelshouldbesetto1+0positionandforprotectionlinkprotectionswitchshouldbeto1+1positionasshowninFigure4.5.

5. SupplytheIDUswithpowerandproceedwithconfiguration.

Figure4.6CFIPPhoeniXIDUfrontpanel

Configurationof1+1FDProtectionMode ItispossibletoperformconfigurationinWebGUIorthroughCLI(serialortelnetconnection).Fordetaileddescriptionofcommandsnecessaryfor1+1configurationrefertosection4.3.5.



For1+1FDmodeitisnecessaryto:

AssigndifferentIPaddressesforeachIDU.NotethatIPaddressesshouldbewithinthesamesubnet;

Setdifferentfrequencypairsforworkingandprotectionlinks; Setappropriatestate(working/protection)foreachIDU; Set appropriate remote site IP address for each IDU: Localworking IDU is interconnected

withremoteworkingIDUandlocalprotectionIDUisinterconnectedwithremoteprotectionIDU.

ExampleofconfigurationforFDmode:

Pleaserefertosection4.3.5fordetailsof1+1configurationparametersandconfiguration

possibilitesviaCLI.Aftersuccessful1+1FDconfiguration,thescreenofProtectionconfigurationinWebGUIshouldlookasfollows:

Figure4.7ProtectionconfigurationwindowaftersuccessfulFDconfiguration

4.3.2 HotStandby/SpaceDiversitymode ForHSBmodetwotransmittersareoperatingatthesamefrequency.OneofthetransmittersisinoperationActivewhiletheotheroneisinStandbymode(Txpowerismuted).Thedataisduplicated



at the transmitter side of the working link and sent towards receivers of both links (working andprotection).Thedecoderofworkingunitselectsthepreferredlink. In SDmode a single transmitter is transmitting data to both receivers at the other side. Thepreferredlinkisselectedbythedecoderofworkinglink.Setupfor1+1HSBandSDmodes

Figure4.8CFIPPhoeniXsetupfor1+1HSB/SDmode

1. Connecteach IDU toappropriateODU.Note thatHighODUsshouldbeatonesideandLowODUsatremoteside.NotethatforHSBmodeODUsshouldbeinterconnectedthroughcouplerateachsite.

2. IDUpairsmustbeconnectedasshowninfigure3.NotethatswitchesofIDUpair(workingandprotection)areconnectedthroughoneofthe1000BaseTuserdataandmanagementportsvia Ethernet cable, and modems are connected through special extension port for 1+1protectionviaprotectioncableCAT6(availablefromSAFTehnikaP/NS0ACPP1).

3. Choosesamefrequenciesforworkingandprotectionlinks.4. Beforepowerissuppliedtoequipment:

- bothIDUsoneachsideofthelinkshouldbegrounded;- switchesof IDUsmustbesettocorrectstate.Forworking linkprotectionmodeswitch

onCFIPPhoeniXIDUfrontpanelshouldbesetto1+0positionandforprotectionlinkprotectionswitchshouldbeto1+1positionasshowninFigure4.5.

5. SupplytheIDUswithpowerandproceedwithconfiguration.Configurationfor1+1HSBProtectionMode ItispossibletoperformconfigurationinWebGUIorthroughCLI(serialortelnetconnection).Fordetaileddescriptionofcommandsnecessaryfor1+1configurationrefertosection4.3.5. For1+1HSBmodeitisnecessaryto:

AssigndifferentIPaddressesforeachIDU.NotethatIPaddressesshouldbewithinthesamesubnet;



Setthesamefrequencypairforworkingandprotectionlinks; Setappropriatestate(working/protection)foreachIDU; Set appropriate remote site IP address for each IDU: Localworking IDU is interconnected

withremoteworkingIDUandlocalprotectionIDUisinterconnectedwithremoteprotectionIDU;

Settheprotectiontimesfor Standbyand Activetrystates. IDUwillremain inappropriatestateduringforcingittoanotherstateforthisspecifiedtime.

ExampleofconfigurationforHSBmode:

After successful 1+1 HSB configuration, the screen of Protection configuration inWeb GUIshouldlookasfollows:

Figure4.9ProtectionconfigurationwindowaftersuccessfulHSBconfiguration



Configurationfor1+1SDProtectionMode

ThismodecanbeconfiguredasasubmodeofHSBmodebyforcingActivestateforoneofthelinks(workingorprotection).TheforcingwillnotallowchangingtheActivestatetoStandby.For1+1SDmodeitisnecessaryto:

Assigndifferent IP addresses for each IDU.Note that IP addresses shouldhave the samesubnet;

SetthesameTxfrequencypairforworkingandprotectionlink; Setappropriatestate(working/protection)foreachIDU; Set appropriate remote site IP address for each IDU: Localworking IDU is interconnected

withremoteworkingIDUandlocalprotectionIDUisinterconnectedwithremoteprotectionIDU;

SwitchtheforcestatetoActiveforoneofthelinks(workingorprotection).IntheexamplebelowtheActivestateisforcedforworkinglink.

ExampleofconfigurationforSDmode:



ThesamecommandscanbeexecutedusingWebGUI.Pleaserefertosection4.3.5fordetails.Aftersuccessful1+1SDconfiguration,thescreenofProtectionconfigurationinWebGUIshouldlookasfollows:

Figure4.10ProtectionconfigurationwindowaftersuccessfulSDconfiguration

ThefollowingsubsectionsaregivingdetaileddescriptionofWebGUIProtectionconfiguration

window.

4.3.3 ProtectionStatusYouwillseethefollowingProtectionStatuswindowwhen1+1modeisdisabled:

1. ValuedenotesthenamesofCFIPPhoeniXunitsin1+1configuration.LocalandLocalalternatedesignatesbothunits(workingandprotection)atthelocalsideandRemoteandRemotealternatedesignatesbothunitsofremoteside.

2. ProtectionstatusdenotesthatCFIPPhoeniX1+1protectionisdisabled.Incase1+1HotStandbymodeisenabledtheProtectionStatuswindowmightlookasfollows:

1. Statusforenabled1+1protectionmodedesignatesthestatusofeachCFIPPhoenixunitin1+1protectionmode.WorkingdenotesthatparticularunitisusedformainworkinglinkandProtectiondesignatesthatparticularunitisusedforprotectionpurpose.

2. Modespecifiesthe1+1protectionmode.PossiblemodesareHotStandbyorFrequencyStandby

3. StatedesignatesthestateofeachunitspecificallyforHotStandbymode.ActivedesignatesthatCFIPPhoeniXunitisactivepartof1+1HotStandbymodeandStandbystatedenotesthatunitisonstandby.

4. PreviousstatedenotesthepreviousstateofeachCFIPPhoeniXunitin1+1protectionmode

4.3.4 ProtectionConfiguration



1. IDUprotectionroleallowsspecifyingtheprotectionroleofCFIPPhoeniXIDUfromdropdown

menu.AvailablerolesareWorking,ProtectionorDisablethatallowsdisabletheprotectionroleofIDU.

2. ProtectionmodegivesthepossibilitytochooseHotStandbyorFrequencyDiversityprotectionmodefromthedropdownmenu.


4.3.5 AdvancedProtectionConfigurationThefollowingsectionwillappearinWebGUIonlyifprotectionisenabledfor1+1HotStandby

mode.

1. ProtectionswitchspecifieswhethertheprotectionswitchisActiveoronStandby.2. ForcestatethisfunctionenabledwillkeepCFIPPhoeniXinselectedstateuntilitisdisabled

withOff3. StandbytimeallowsspecifyingStandbytime(inrange115sec)forStandbystate.IDUwill

remainforthistimeslotinStandbystateduringforcingittoanotherstate.4. ActivetrytimeallowsspecifyingActivetrytime(inrange115sec)forActivetrystate.IDUwill

remainforthistimeslotinActivetrystateduringforcingittoanotherstate.5. BypressingExecuteconfigurationchangesmadetothecorrespondingsectionapplyonlyfor

thelocalsideCFIPPhoeniX.IfRollbackonisselected,configurationwillberevertedincaseerroneousconfigurationchangesareapplied.

6. Writes to configuration file all the changesmade on thewhole page (command line cfgwrite);

7. Systemreturnedincaseoferrororincorrectlyenteredparametervalue,orotherproblemsonthewholepageinfomessagewillbedisplayedhere.OtherwiseitsaysOk.



4.4 SystemConfigurationThe system configuration window provides the configuration of web access, telnet and FTP

interfaces;allowschangingsystemname,webdatarefreshtimeandsystemtime.

4.4.1 UserConfiguration

AdditionalusermanagementcommandsinTelnet/serialinterfaceCommand Descriptionprotstatus ShowsprotectionstatusofparticularIDUprotstatusall Shows protection status of all units involved in 1+1

configurationprotset{hsb|fd}{working|protection|disable} AllowssettingHotStandby/Frequencydiversitymodeand

theprotectionroleofparticularunitprot{active|standby} SwitchestodesiredIDUstateActiveorStandby

protforce{active|standby|off} Forces Active or Standby state or switches offforcingfunction

prottime{disabled|start|standby|active|activecmd|activetry|}[]

AllowsspecifyingStandbyandActivetrytime

protalarms Showsprotectionalarmstatusprottrace Tracesprotectionstatechangesbyprintoutsonterminalprotextstatistics Shows protection information exchange quality statistics

betweenlocalandalternateIDUprotextstatisticsclear Clearsallpreviousexchangequalitystatistics



1. guest Enternew password (length: 4..30 characters) allows enteringpreferable

guest account password and enabling the account. By default guest account isdisabled.Maximal lengthofthepasswordcannotexceed30symbols.Guestaccounthasonlymonitoringprivileges.ThefollowingWebGUIsectionsareavailable:

2. adminEnternewpassword (length:4..30 characters)allows toenterpreferable

adminaccountpassword.Maximal lengthofusernamecannotexceed30symbols.Bydefaultpasswordforadminaccountischangeme.AdminaccounthasfullcontroloftheCFIPconfigurationprocess.

3. Hidepassword(s)Hidestypedinpassword.Thisoptionuncheckedwilldisplaytypedinpasswordinplaintext.


Moredetailedstatuscontrolsareavailableincommandprompt,whichinclude:

AdditionalusermanagementcommandsinTelnet/serialinterfaceCommand Descriptionaccesslogin Logsonasauserspecifiedbyand.accesslogout Logscurrentuserout.accessset[plaintext]

Allowsspecifyinganewpasswordforaspecificaccount(adminorguest).plaintextoptionwillsavethepasswordinplaintextinconfigurationscriptwithoutencryptingit(bydefaultsavedpasswordsinconfigurationfileareencrypted).

accessshow Showsusernameandpasswordofausercurrentlyloggedon.

accesslist Showsthelistofusernamesandpasswordsthecurrentaccountisabletomanage(ifloggedonasadmin,guestandadminaccountpasswordswillbeseen).



4.4.2 NamesConfiguration

1. Systemname(Maxlength:16characters)allowsenteringpreferablesystemname.It

isrecommendedtonamethesystemafteritsgeographiclocation.Maximumlengthofthe user name cannot exceed 16 symbols.Default name is SAF (command line systemname);


4.4.3 Otherconfiguration

1. Webrefresh(2..600sec)allowsspecifyingtimeintervalofWebdatarefreshing.The

defaultvalue is5seconds.Youcanchoosebetween

cfip_phoenix_td_en_v 1 4 copy.pdf

Documents

configuration guide

saf tehnika jsc